diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000000..4f8075ffce --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,5 @@ +blank_issues_enabled: false +contact_links: + - name: New feedback experience + url: https://learn.microsoft.com/office/new-feedback + about: We’re transitioning our feedback experience away from GitHub Issues. For more information, select Open. \ No newline at end of file diff --git a/.github/workflows/AutoLabelAssign.yml b/.github/workflows/AutoLabelAssign.yml new file mode 100644 index 0000000000..65e87b3d4b --- /dev/null +++ b/.github/workflows/AutoLabelAssign.yml @@ -0,0 +1,37 @@ +name: Assign and label PR + +permissions: + pull-requests: write + contents: read + actions: read + +on: + workflow_run: + workflows: [Background tasks] + types: + - completed + +jobs: + download-payload: + name: Download and extract payload artifact + if: github.repository_owner == 'MicrosoftDocs' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-prod + with: + WorkflowId: ${{ github.event.workflow_run.id }} + OrgRepo: ${{ github.repository }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} + + label-assign: + name: Run assign and label + if: github.repository_owner == 'MicrosoftDocs' + needs: [download-payload] + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelAssign.yml@workflows-prod + with: + PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }} + AutoAssignUsers: 1 + AutoLabel: 1 + ExcludedUserList: '["user1", "user2"]' + ExcludedBranchList: '["branch1", "branch2"]' + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/.github/workflows/AutoLabelMsftContributor.yml b/.github/workflows/AutoLabelMsftContributor.yml new file mode 100644 index 0000000000..6fcfb6e43e --- /dev/null +++ b/.github/workflows/AutoLabelMsftContributor.yml @@ -0,0 +1,35 @@ +name: Auto label Microsoft contributors + +permissions: + pull-requests: write + contents: read + actions: read + +on: + workflow_run: + workflows: [Background tasks] + types: + - completed + +jobs: + download-payload: + if: github.repository_owner == 'MicrosoftDocs' && github.repository_visibility == 'public' + name: Download and extract payload artifact + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-prod + with: + WorkflowId: ${{ github.event.workflow_run.id }} + OrgRepo: ${{ github.repository }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} + + label-msft: + name: Label Microsoft contributors + if: github.repository_owner == 'MicrosoftDocs' && github.repository_visibility == 'public' + needs: [download-payload] + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelMsftContributor.yml@workflows-prod + with: + PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} + ClientId: ${{ secrets.M365_APP_CLIENT_ID }} + PrivateKey: ${{ secrets.M365_APP_PRIVATE_KEY }} \ No newline at end of file diff --git a/.github/workflows/AutoPublish.yml b/.github/workflows/AutoPublish.yml new file mode 100644 index 0000000000..c067d8f47b --- /dev/null +++ b/.github/workflows/AutoPublish.yml @@ -0,0 +1,27 @@ +name: (Scheduled) Publish to live + +permissions: + contents: write + pull-requests: write + checks: read + +on: + schedule: + - cron: "25 2,5,8,11,14,17,20,22 * * *" # Times are UTC based on Daylight Saving Time. Need to be adjusted for Standard Time. Scheduling at :25 to account for queuing lag. + + workflow_dispatch: + +jobs: + + auto-publish: + if: github.repository_owner == 'MicrosoftDocs' && contains(github.event.repository.topics, 'build') + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoPublishV2.yml@workflows-prod + with: + PayloadJson: ${{ toJSON(github) }} + EnableAutoPublish: true + EnableAutoMerge: true + + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} + PrivateKey: ${{ secrets.M365_APP_PRIVATE_KEY }} + ClientId: ${{ secrets.M365_APP_CLIENT_ID }} \ No newline at end of file diff --git a/.github/workflows/BackgroundTasks.yml b/.github/workflows/BackgroundTasks.yml new file mode 100644 index 0000000000..8dc3ceae0a --- /dev/null +++ b/.github/workflows/BackgroundTasks.yml @@ -0,0 +1,27 @@ +name: Background tasks + +permissions: + pull-requests: write + contents: read + +on: + pull_request_target: + +jobs: + upload: + if: github.repository_owner == 'MicrosoftDocs' + runs-on: ubuntu-latest + + steps: + - name: Save payload data + env: + PayloadJson: ${{ toJSON(github) }} + AccessToken: ${{ github.token }} + run: | + mkdir -p ./pr + echo $PayloadJson > ./pr/PayloadJson.json + sed -i -e "s/$AccessToken/XYZ/g" ./pr/PayloadJson.json + - uses: actions/upload-artifact@v4 + with: + name: PayloadJson + path: pr/ \ No newline at end of file diff --git a/.github/workflows/BuildValidation.yml b/.github/workflows/BuildValidation.yml new file mode 100644 index 0000000000..dadccacbef --- /dev/null +++ b/.github/workflows/BuildValidation.yml @@ -0,0 +1,19 @@ +name: PR has no warnings or errors + +permissions: + pull-requests: write + statuses: write + +on: + issue_comment: + types: [created] + +jobs: + + build-status: + if: github.repository_owner == 'MicrosoftDocs' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-BuildValidation.yml@workflows-prod + with: + PayloadJson: ${{ toJSON(github) }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/LiveMergeCheck.yml b/.github/workflows/LiveMergeCheck.yml new file mode 100644 index 0000000000..7db35548e9 --- /dev/null +++ b/.github/workflows/LiveMergeCheck.yml @@ -0,0 +1,20 @@ +name: PR can merge into branch + +permissions: + pull-requests: write + statuses: write + contents: read + +on: + pull_request_target: + types: [opened, reopened, synchronize, edited] + +jobs: + + live-merge: + if: github.repository_owner == 'MicrosoftDocs' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-LiveMergeCheck.yml@workflows-prod + with: + PayloadJson: ${{ toJSON(github) }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/.github/workflows/PrFileCount.yml b/.github/workflows/PrFileCount.yml new file mode 100644 index 0000000000..17faf7a211 --- /dev/null +++ b/.github/workflows/PrFileCount.yml @@ -0,0 +1,20 @@ +name: PR file count less than limit + +permissions: + pull-requests: write + statuses: write + contents: read + +on: + pull_request_target: + types: [opened, reopened, synchronize, labeled, unlabeled, edited] + +jobs: + + file-count: + if: github.repository_owner == 'MicrosoftDocs' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-PrFileCount.yml@workflows-prod + with: + PayloadJson: ${{ toJSON(github) }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/.github/workflows/ProtectedFiles.yml b/.github/workflows/ProtectedFiles.yml new file mode 100644 index 0000000000..bbdbbe2e40 --- /dev/null +++ b/.github/workflows/ProtectedFiles.yml @@ -0,0 +1,18 @@ +name: PR has no protected files + +permissions: + pull-requests: write + statuses: write + contents: read + +on: [pull_request_target] + +jobs: + + protected-files: + if: github.repository_owner == 'MicrosoftDocs' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ProtectedFiles.yml@workflows-prod + with: + PayloadJson: ${{ toJSON(github) }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/.github/workflows/Stale.yml b/.github/workflows/Stale.yml new file mode 100644 index 0000000000..7f262d325a --- /dev/null +++ b/.github/workflows/Stale.yml @@ -0,0 +1,20 @@ +name: (Scheduled) Mark stale pull requests + +permissions: + issues: write + pull-requests: write + +on: + schedule: + - cron: "0 */6 * * *" + workflow_dispatch: + +jobs: + stale: + if: github.repository_owner == 'MicrosoftDocs' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-Stale.yml@workflows-prod + with: + RunDebug: false + RepoVisibility: ${{ github.repository_visibility }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/.github/workflows/StaleBranch.yml b/.github/workflows/StaleBranch.yml new file mode 100644 index 0000000000..30212d1836 --- /dev/null +++ b/.github/workflows/StaleBranch.yml @@ -0,0 +1,32 @@ +name: (Scheduled) Stale branch removal + +permissions: + contents: write + pull-requests: read + +# This workflow is designed to be run in the days up to, and including, a "deletion day", specified by 'DeleteOnDayOfMonth' in env: in https://github.com/MicrosoftDocs/microsoft-365-docs/blob/workflows-prod/.github/workflows/Shared-StaleBranch.yml. +# On the days leading up to "deletion day", the workflow will report the branches to be deleted. This lets users see which branches will be deleted. On "deletion day", those branches are deleted. +# The workflow should not be configured to run after "deletion day" so that users can review the branches were deleted. +# Recommendation: configure cron to run on days 1,15-31 where 1 is what's configured in 'DeleteOnDayOfMonth'. If 'DeleteOnDayOfMonth' is set to something else, update cron to run the two weeks leading up to it. + +on: + schedule: + - cron: "0 9 1,15-31 * *" + + workflow_dispatch: + + +jobs: + + stale-branch: + if: github.repository_owner == 'MicrosoftDocs' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-StaleBranch.yml@workflows-prod + with: + PayloadJson: ${{ toJSON(github) }} + RepoBranchSkipList: '[ + "ExampleBranch1", + "ExampleBranch2" + ]' + ReportOnly: false + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/.github/workflows/TierManagement.yml b/.github/workflows/TierManagement.yml new file mode 100644 index 0000000000..47baf0be65 --- /dev/null +++ b/.github/workflows/TierManagement.yml @@ -0,0 +1,21 @@ +name: Tier management + +permissions: + pull-requests: write + contents: read + +on: + issue_comment: + types: [created, edited] + +jobs: + + tier-mgmt: + if: github.repository_owner == 'MicrosoftDocs' && github.repository_visibility == 'private' + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-TierManagement.yml@workflows-prod + with: + PayloadJson: ${{ toJSON(github) }} + EnableWriteSignOff: 1 + EnableReadOnlySignoff: 1 + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/.gitignore b/.gitignore index 6ff3476cd5..41b9a36fff 100644 --- a/.gitignore +++ b/.gitignore @@ -4,9 +4,13 @@ _site/ .optemp/ _themes*/ .vs/ +common/ +.vscode/ +*.ini +.DS_Store +*.db +\.idea/ .local/ .openpublishing.buildcore.ps1 **/node_modules - -\.idea/ diff --git a/.openpublishing.build.ps1 b/.openpublishing.build.ps1 deleted file mode 100644 index aadef76202..0000000000 --- a/.openpublishing.build.ps1 +++ /dev/null @@ -1,17 +0,0 @@ -param( - [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1", - [string]$parameters -) -# Main -$errorActionPreference = 'Stop' - -# Step-1: Download buildcore script to local -echo "download build core script to local with source url: $buildCorePowershellUrl" -$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition -$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1" -Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination" - -# Step-2: Run build core -echo "run build core script with parameters: $parameters" -& "$buildCorePowershellDestination" "$parameters" -exit $LASTEXITCODE diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json index cfd6ca48c5..72c839af99 100644 --- a/.openpublishing.publish.config.json +++ b/.openpublishing.publish.config.json @@ -12,21 +12,19 @@ "Conceptual": "Content", "ManagedReference": "Content", "RestApi": "Content", - "AzurePsModulePage": "Content" + "PowershellModule": "Content", + "PowershellCmdlet": "Content" }, "build_entry_point": "docs", "template_folder": "_themes", "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], "customized_tasks": { "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" + "_dependentPackages/MAML2Yaml/tools/Run.ps1" ] }, "monikerPath": [ - "mapping/monikerMapping.json" + "mapping/MAML2Yaml/monikerMapping.json" ] }, { @@ -41,50 +39,14 @@ "Conceptual": "Content", "ManagedReference": "Content", "RestApi": "Content", - "AzurePsModulePage": "Content" + "PowershellModule": "Content", + "PowershellCmdlet": "Content" }, "build_entry_point": "docs", "template_folder": "_themes", "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], - "customized_tasks": { - "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" - ] - }, "monikerPath": [ - "mapping/monikerMapping.json" - ] - }, - { - "docset_name": "sharepoint-ps", - "build_source_folder": "sharepoint", - "build_output_subfolder": "sharepoint-ps", - "locale": "en-us", - "monikers": [], - "moniker_ranges": [], - "open_to_public_contributors": true, - "type_mapping": { - "Conceptual": "Content", - "ManagedReference": "Content", - "RestApi": "Content", - "AzurePsModulePage": "Content" - }, - "build_entry_point": "docs", - "template_folder": "_themes", - "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], - "customized_tasks": { - "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" - ] - }, - "monikerPath": [ - "mapping/monikerMapping.json" + "mapping/MAML2Yaml/monikerMapping.json" ] }, { @@ -99,27 +61,25 @@ "Conceptual": "Content", "ManagedReference": "Content", "RestApi": "Content", - "AzurePsModulePage": "Content" + "PowershellModule": "Content", + "PowershellCmdlet": "Content" }, "build_entry_point": "docs", "template_folder": "_themes", "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], "customized_tasks": { "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" + "_dependentPackages/MAML2Yaml/tools/Run.ps1" ] }, "monikerPath": [ - "mapping/monikerMapping.json" + "mapping/MAML2Yaml/monikerMapping.json" ] }, { - "docset_name": "staffhub-ps", - "build_source_folder": "staffhub", - "build_output_subfolder": "staffhub-ps", + "docset_name": "spmt-ps", + "build_source_folder": "spmt", + "build_output_subfolder": "spmt-ps", "locale": "en-us", "monikers": [], "moniker_ranges": [], @@ -128,21 +88,14 @@ "Conceptual": "Content", "ManagedReference": "Content", "RestApi": "Content", - "AzurePsModulePage": "Content" + "PowershellModule": "Content", + "PowershellCmdlet": "Content" }, "build_entry_point": "docs", "template_folder": "_themes", "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], - "customized_tasks": { - "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" - ] - }, "monikerPath": [ - "mapping/monikerMapping.json" + "mapping/MAML2Yaml/monikerMapping.json" ] }, { @@ -157,50 +110,19 @@ "Conceptual": "Content", "ManagedReference": "Content", "RestApi": "Content", - "AzurePsModulePage": "Content" + "PowershellModule": "Content", + "PowershellCmdlet": "Content" }, "build_entry_point": "docs", "template_folder": "_themes", "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], "customized_tasks": { "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" + "_dependentPackages/MAML2Yaml/tools/Run.ps1" ] }, "monikerPath": [ - "mapping/monikerMapping.json" - ] - }, - { - "docset_name": "spmt-ps", - "build_source_folder": "spmt", - "build_output_subfolder": "spmt-ps", - "locale": "en-us", - "monikers": [], - "moniker_ranges": [], - "open_to_public_contributors": true, - "type_mapping": { - "Conceptual": "Content", - "ManagedReference": "Content", - "RestApi": "Content", - "AzurePsModulePage": "Content" - }, - "build_entry_point": "docs", - "template_folder": "_themes", - "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], - "customized_tasks": { - "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" - ] - }, - "monikerPath": [ - "mapping/monikerMapping.json" + "mapping/MAML2Yaml/monikerMapping.json" ] }, { @@ -215,71 +137,58 @@ "Conceptual": "Content", "ManagedReference": "Content", "RestApi": "Content", - "AzurePsModulePage": "Content" + "PowershellModule": "Content", + "PowershellCmdlet": "Content" }, "build_entry_point": "docs", "template_folder": "_themes", "version": 0, - "customized_template_paths": [ - "_dependentPackages/azurecli.plugins/azurecli" - ], "customized_tasks": { "docset_prebuild": [ - "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1" + "_dependentPackages/MAML2Yaml/tools/Run.ps1" ] }, "monikerPath": [ - "mapping/monikerMapping.json" + "mapping/MAML2Yaml/monikerMapping.json" ] } ], "notification_subscribers": [], + "sync_notification_subscribers": [], "branches_to_filter": [], - "git_repository_branch_open_to_public_contributors": "master", - "skip_source_output_uploading": false, + "git_repository_branch_open_to_public_contributors": "main", "need_preview_pull_request": true, - "contribution_branch_mappings": {}, "dependent_repositories": [ { "path_to_root": "_themes", "url": "https://github.com/Microsoft/templates.docs.msft", - "branch": "master", - "branch_mapping": {} - }, - { - "path_to_root": "_themes.pdf", - "url": "https://github.com/Microsoft/templates.docs.msft.pdf", - "branch": "master", + "branch": "main", "branch_mapping": {} } ], "branch_target_mapping": { "live": [ - "Publish", - "Pdf" + "Publish" ] }, - "need_generate_pdf_url_template": true, "targets": { "Pdf": { "template_folder": "_themes.pdf" } }, - "need_generate_intellisense": false, + "docs_build_engine": {}, + "skip_source_output_uploading": false, "enable_incremental_build": false, + "contribution_branch_mappings": {}, + "need_generate_pdf_url_template": false, + "need_generate_intellisense": false, "dependent_packages": [ { - "path_to_root": "_dependentPackages/azurecli.plugins", - "id": "opbuild.templates.azurecli", - "version": "latest", - "nuget_feed": "https://www.myget.org/F/op/api/v2" - }, - { - "path_to_root": "_dependentPackages/CommonPlugins", + "id": "Microsoft.DocAsCode.MAML2Yaml", + "nuget_feed": "https://www.myget.org/F/op/api/v2", + "path_to_root": "_dependentPackages/MAML2Yaml", "target_framework": "net45", - "version": "latest", - "id": "Microsoft.OpenPublishing.CommonPlugins", - "nuget_feed": "https://www.myget.org/F/op/api/v2" + "version": "latest" } ] -} +} \ No newline at end of file diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index bbca22b2c9..0c2327fa83 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -1,73 +1,73 @@ - { - "redirections": [ +{ + "redirections": [ { - "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpEdmSschema.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpedmschema", - "redirect_document_id": true + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpEdmSschema.md", + "redirect_url": "/powershell/module/exchange/new-dlpedmschema", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-TeamsRetentionCompliancePolicy.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-retentioncompliancepolicy", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/get-retentioncompliancepolicy", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-TeamsRetentionComplianceRule.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-retentioncompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/get-retentioncompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-TeamsRetentionCompliancePolicy.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-retentioncompliancepolicy", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/new-retentioncompliancepolicy", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-TeamsRetentionComplianceRule.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-retentioncompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/new-retentioncompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-TeamsRetentionCompliancePolicy.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-retentioncompliancepolicy", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/remove-retentioncompliancepolicy", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-TeamsRetentionComplianceRule.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-retentioncompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/remove-retentioncompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-TeamsRetentionCompliancePolicy.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-retentioncompliancepolicy", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/set-retentioncompliancepolicy", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-TeamsRetentionComplianceRule.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-retentioncompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/set-retentioncompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpComplianceRuleV2.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpcompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/get-dlpcompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpComplianceRuleV2.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpcompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/new-dlpcompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRuleV2.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlpcompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/remove-dlpcompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpComplianceRuleV2.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlpcompliancerule", - "redirect_document_id": true + "redirect_url": "/powershell/module/exchange/set-dlpcompliancerule", + "redirect_document_id": false }, { "source_path": "exchange/exchange-ps-v2-module/connect-exchangeonline.md", - "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/connect-exchangeonline", + "redirect_url": "/powershell/module/exchange/connect-exchangeonline", "redirect_document_id": true }, { @@ -162,8 +162,8865 @@ }, { "source_path": "sharepoint/docs-conceptual/overview.md", - "redirect_url": "https://docs.microsoft.com/powershell/sharepoint", - "redirect_document_id": true + "redirect_url": "/powershell/sharepoint", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Add-ADPermission.md", + "redirect_url": "/powershell/module/exchange/add-adpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Dump-ProvisioningCache.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADServerSettings.md", + "redirect_url": "/powershell/module/exchange/get-adserversettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADSite.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Get-DomainController.md", + "redirect_url": "/powershell/module/exchange/get-domaincontroller", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Get-OrganizationalUnit.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Get-UserPrincipalNamesSuffix.md", + "redirect_url": "/powershell/module/exchange/get-userprincipalnamessuffix", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Remove-ADPermission.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Set-ADServerSettings.md", + "redirect_url": "/powershell/module/exchange/set-adserversettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/active-directory/Set-ADSite.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-AntiPhishRule.md", + "redirect_url": "/powershell/module/exchange/disable-antiphishrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-SafeAttachmentRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-AntiPhishRule.md", + "redirect_url": "/powershell/module/exchange/enable-antiphishrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-SafeAttachmentRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentDetail.md", + "redirect_url": "/powershell/module/exchange/get-advancedthreatprotectiondocumentdetail", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentReport.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AntiPhishPolicy.md", + "redirect_url": "/powershell/module/exchange/get-antiphishpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AntiPhishRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-MailDetailATPReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-MailTrafficATPReport.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeAttachmentPolicy.md", + "redirect_url": "/powershell/module/exchange/get-safeattachmentpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeAttachmentRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeLinksRule.md", + "redirect_url": "/powershell/module/exchange/get-safelinksrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SpoofMailReport.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-AntiPhishPolicy.md", + "redirect_url": "/powershell/module/exchange/new-antiphishpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-AntiPhishRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeAttachmentRule.md", + "redirect_url": "/powershell/module/exchange/new-safeattachmentrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeLinksPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-AntiPhishPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-antiphishpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-AntiPhishRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeAttachmentRule.md", + "redirect_url": "/powershell/module/exchange/remove-safeattachmentrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeLinksPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md", + "redirect_url": "/powershell/module/exchange/set-antiphishpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AntiPhishRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeAttachmentPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeLinksPolicy.md", + "redirect_url": "/powershell/module/exchange/set-safelinkspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeLinksRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-ContentFilterPhrase.md", + "redirect_url": "/powershell/module/exchange/add-contentfilterphrase", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPAllowListEntry.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPBlockListEntry.md", + "redirect_url": "/powershell/module/exchange/add-ipblocklistentry", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPBlockListProvider.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-HostedContentFilterRule.md", + "redirect_url": "/powershell/module/exchange/disable-hostedcontentfilterrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-HostedOutboundSpamFilterRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-AntispamUpdates.md", + "redirect_url": "/powershell/module/exchange/enable-antispamupdates", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-HostedContentFilterRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-MalwareFilterRule.md", + "redirect_url": "/powershell/module/exchange/enable-malwarefilterrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Export-QuarantineMessage.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AttachmentFilterEntry.md", + "redirect_url": "/powershell/module/exchange/get-attachmentfilterentry", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AttachmentFilterListConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-ContentFilterConfig.md", + "redirect_url": "/powershell/module/exchange/get-contentfilterconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-ContentFilterPhrase.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedConnectionFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/get-hostedconnectionfilterpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedContentFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/get-hostedoutboundspamfilterpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListEntry.md", + "redirect_url": "/powershell/module/exchange/get-ipallowlistentry", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListProvider.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListConfig.md", + "redirect_url": "/powershell/module/exchange/get-ipblocklistconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListEntry.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListProvidersConfig.md", + "redirect_url": "/powershell/module/exchange/get-ipblocklistprovidersconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MailboxJunkEmailConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/get-malwarefilterpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilterRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-QuarantineMessageHeader.md", + "redirect_url": "/powershell/module/exchange/get-quarantinemessageheader", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-RecipientFilterConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderIdConfig.md", + "redirect_url": "/powershell/module/exchange/get-senderidconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderReputationConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/new-hostedcontentfilterpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedContentFilterRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedOutboundSpamFilterRule.md", + "redirect_url": "/powershell/module/exchange/new-hostedoutboundspamfilterrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-MalwareFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Preview-QuarantineMessage.md", + "redirect_url": "/powershell/module/exchange/preview-quarantinemessage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Release-QuarantineMessage.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-BlockedSenderAddress.md", + "redirect_url": "/powershell/module/exchange/remove-blockedsenderaddress", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-ContentFilterPhrase.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedContentFilterRule.md", + "redirect_url": "/powershell/module/exchange/remove-hostedcontentfilterrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPAllowListEntry.md", + "redirect_url": "/powershell/module/exchange/remove-ipallowlistentry", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPAllowListProvider.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPBlockListProvider.md", + "redirect_url": "/powershell/module/exchange/remove-ipblocklistprovider", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-MalwareFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Rotate-DkimSigningConfig.md", + "redirect_url": "/powershell/module/exchange/rotate-dkimsigningconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-AttachmentFilterListConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-DkimSigningConfig.md", + "redirect_url": "/powershell/module/exchange/set-dkimsigningconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedConnectionFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedContentFilterRule.md", + "redirect_url": "/powershell/module/exchange/set-hostedcontentfilterrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListConfig.md", + "redirect_url": "/powershell/module/exchange/set-ipallowlistconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListProvider.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListConfig.md", + "redirect_url": "/powershell/module/exchange/set-ipblocklistconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListProvider.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MailboxJunkEmailConfiguration.md", + "redirect_url": "/powershell/module/exchange/set-mailboxjunkemailconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilteringServer.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilterRule.md", + "redirect_url": "/powershell/module/exchange/set-malwarefilterrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-RecipientFilterConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderIdConfig.md", + "redirect_url": "/powershell/module/exchange/set-senderidconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderReputationConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-IPBlockListProvider.md", + "redirect_url": "/powershell/module/exchange/test-ipblocklistprovider", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-SenderId.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Clear-TextMessagingAccount.md", + "redirect_url": "/powershell/module/exchange/clear-textmessagingaccount", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Compare-TextMessagingVerificationCode.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Enable-PushNotificationProxy.md", + "redirect_url": "/powershell/module/exchange/enable-pushnotificationproxy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Export-AutoDiscoverConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-CASMailboxPlan.md", + "redirect_url": "/powershell/module/exchange/get-casmailboxplan", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-ClientAccessRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxCalendarConfiguration.md", + "redirect_url": "/powershell/module/exchange/get-mailboxcalendarconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxMessageConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxSpellingConfiguration.md", + "redirect_url": "/powershell/module/exchange/get-mailboxspellingconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-OutlookProvider.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-PopSettings.md", + "redirect_url": "/powershell/module/exchange/get-popsettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Get-TextMessagingAccount.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/New-OutlookProvider.md", + "redirect_url": "/powershell/module/exchange/new-outlookprovider", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/New-OwaMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Remove-OutlookProvider.md", + "redirect_url": "/powershell/module/exchange/remove-outlookprovider", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Remove-OwaMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Set-CASMailbox.md", + "redirect_url": "/powershell/module/exchange/set-casmailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/set-CASMailboxPlan.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Set-ImapSettings.md", + "redirect_url": "/powershell/module/exchange/set-imapsettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxCalendarConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxRegionalConfiguration.md", + "redirect_url": "/powershell/module/exchange/set-mailboxregionalconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxSpellingConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Set-OwaMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/set-owamailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Set-PopSettings.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Test-CalendarConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-calendarconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Test-ClientAccessRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Test-ImapConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-imapconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Test-OutlookConnectivity.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Test-OwaConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-owaconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Test-PopConnectivity.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access/Test-WebServicesConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-webservicesconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Disable-OutlookAnywhere.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ActiveSyncVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/get-activesyncvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-AuthRedirect.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessArray.md", + "redirect_url": "/powershell/module/exchange/get-clientaccessarray", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessServer.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-EcpVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/get-ecpvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-MapiVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-OwaVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/get-owavirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-PowerShellVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-WebServicesVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/get-webservicesvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-ActiveSyncVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-AutodiscoverVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/new-autodiscovervirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-ClientAccessArray.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-MapiVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/new-mapivirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-OwaVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-RpcClientAccess.md", + "redirect_url": "/powershell/module/exchange/new-rpcclientaccess", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-WebServicesVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-AuthRedirect.md", + "redirect_url": "/powershell/module/exchange/remove-authredirect", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-AutodiscoverVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-EcpVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/remove-ecpvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-MapiVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-PowerShellVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/remove-powershellvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-RpcClientAccess.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ActiveSyncVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/set-activesyncvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-AuthRedirect.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessArray.md", + "redirect_url": "/powershell/module/exchange/set-clientaccessarray", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessServer.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-EcpVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/set-ecpvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-MapiVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-OwaVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/set-owavirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-PowerShellVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-WebServicesVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/set-webservicesvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-DatabaseAvailabilityGroup.md", + "redirect_url": "/powershell/module/exchange/get-databaseavailabilitygroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-DatabaseAvailabilityGroupNetwork.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Move-ActiveMailboxDatabase.md", + "redirect_url": "/powershell/module/exchange/move-activemailboxdatabase", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/New-DatabaseAvailabilityGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroup.md", + "redirect_url": "/powershell/module/exchange/remove-databaseavailabilitygroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupNetwork.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-MailboxDatabaseCopy.md", + "redirect_url": "/powershell/module/exchange/remove-mailboxdatabasecopy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Restore-DatabaseAvailabilityGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md", + "redirect_url": "/powershell/module/exchange/set-databaseavailabilitygroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-DatabaseAvailabilityGroupNetwork.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Start-DatabaseAvailabilityGroup.md", + "redirect_url": "/powershell/module/exchange/start-databaseavailabilitygroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Stop-DatabaseAvailabilityGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Test-ReplicationHealth.md", + "redirect_url": "/powershell/module/exchange/test-replicationhealth", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Update-MailboxDatabaseCopy.md", + "redirect_url": "/powershell/module/exchange/update-mailboxdatabasecopy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Clear-ActiveSyncDevice.md", + "redirect_url": "/powershell/module/exchange/clear-activesyncdevice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Clear-MobileDevice.md", + "redirect_url": "/powershell/module/exchange/clear-mobiledevice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Export-ActiveSyncLog.md", + "redirect_url": "/powershell/module/exchange/export-activesynclog", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDevice.md", + "redirect_url": "/powershell/module/exchange/get-activesyncdevice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceAccessRule.md", + "redirect_url": "/powershell/module/exchange/get-activesyncdeviceaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceAutoblockThreshold.md", + "redirect_url": "/powershell/module/exchange/get-activesyncdeviceautoblockthreshold", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceClass.md", + "redirect_url": "/powershell/module/exchange/get-activesyncdeviceclass", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceStatistics.md", + "redirect_url": "/powershell/module/exchange/get-activesyncdevicestatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/get-activesyncmailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncOrganizationSettings.md", + "redirect_url": "/powershell/module/exchange/get-activesyncorganizationsettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConditionalAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/get-deviceconditionalaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConditionalAccessRule.md", + "redirect_url": "/powershell/module/exchange/get-deviceconditionalaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/get-deviceconfigurationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/get-deviceconfigurationrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-DevicePolicy.md", + "redirect_url": "/powershell/module/exchange/get-devicepolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceTenantPolicy.md", + "redirect_url": "/powershell/module/exchange/get-devicetenantpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceTenantRule.md", + "redirect_url": "/powershell/module/exchange/get-devicetenantrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDevice.md", + "redirect_url": "/powershell/module/exchange/get-mobiledevice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDeviceMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/get-mobiledevicemailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDeviceStatistics.md", + "redirect_url": "/powershell/module/exchange/get-mobiledevicestatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-ActiveSyncDeviceAccessRule.md", + "redirect_url": "/powershell/module/exchange/new-activesyncdeviceaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-ActiveSyncMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/new-activesyncmailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConditionalAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/new-deviceconditionalaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConditionalAccessRule.md", + "redirect_url": "/powershell/module/exchange/new-deviceconditionalaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/new-deviceconfigurationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/new-deviceconfigurationrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceTenantPolicy.md", + "redirect_url": "/powershell/module/exchange/new-devicetenantpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceTenantRule.md", + "redirect_url": "/powershell/module/exchange/new-devicetenantrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/New-MobileDeviceMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/new-mobiledevicemailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDevice.md", + "redirect_url": "/powershell/module/exchange/remove-activesyncdevice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDeviceAccessRule.md", + "redirect_url": "/powershell/module/exchange/remove-activesyncdeviceaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDeviceClass.md", + "redirect_url": "/powershell/module/exchange/remove-activesyncdeviceclass", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-activesyncmailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConditionalAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-deviceconditionalaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConditionalAccessRule.md", + "redirect_url": "/powershell/module/exchange/remove-deviceconditionalaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-deviceconfigurationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/remove-deviceconfigurationrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceTenantPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-devicetenantpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceTenantRule.md", + "redirect_url": "/powershell/module/exchange/remove-devicetenantrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-MobileDevice.md", + "redirect_url": "/powershell/module/exchange/remove-mobiledevice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Remove-MobileDeviceMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-mobiledevicemailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncDeviceAccessRule.md", + "redirect_url": "/powershell/module/exchange/set-activesyncdeviceaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncDeviceAutoblockThreshold.md", + "redirect_url": "/powershell/module/exchange/set-activesyncdeviceautoblockthreshold", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/set-activesyncmailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncOrganizationSettings.md", + "redirect_url": "/powershell/module/exchange/set-activesyncorganizationsettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConditionalAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/set-deviceconditionalaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConditionalAccessRule.md", + "redirect_url": "/powershell/module/exchange/set-deviceconditionalaccessrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/set-deviceconfigurationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/set-deviceconfigurationrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceTenantPolicy.md", + "redirect_url": "/powershell/module/exchange/set-devicetenantpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceTenantRule.md", + "redirect_url": "/powershell/module/exchange/set-devicetenantrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Set-MobileDeviceMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/set-mobiledevicemailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/devices/Test-ActiveSyncConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-activesyncconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Disable-AddressListPaging.md", + "redirect_url": "/powershell/module/exchange/disable-addresslistpaging", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Enable-AddressListPaging.md", + "redirect_url": "/powershell/module/exchange/enable-addresslistpaging", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-AddressBookPolicy.md", + "redirect_url": "/powershell/module/exchange/get-addressbookpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-AddressList.md", + "redirect_url": "/powershell/module/exchange/get-addresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-DetailsTemplate.md", + "redirect_url": "/powershell/module/exchange/get-detailstemplate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-EmailAddressPolicy.md", + "redirect_url": "/powershell/module/exchange/get-emailaddresspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-GlobalAddressList.md", + "redirect_url": "/powershell/module/exchange/get-globaladdresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-OabVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/get-oabvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-OfflineAddressBook.md", + "redirect_url": "/powershell/module/exchange/get-offlineaddressbook", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Move-AddressList.md", + "redirect_url": "/powershell/module/exchange/move-addresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Move-OfflineAddressBook.md", + "redirect_url": "/powershell/module/exchange/move-offlineaddressbook", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-AddressBookPolicy.md", + "redirect_url": "/powershell/module/exchange/new-addressbookpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-AddressList.md", + "redirect_url": "/powershell/module/exchange/new-addresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-EmailAddressPolicy.md", + "redirect_url": "/powershell/module/exchange/new-emailaddresspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-GlobalAddressList.md", + "redirect_url": "/powershell/module/exchange/new-globaladdresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-OabVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/new-oabvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-OfflineAddressBook.md", + "redirect_url": "/powershell/module/exchange/new-offlineaddressbook", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-AddressBookPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-addressbookpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-AddressList.md", + "redirect_url": "/powershell/module/exchange/remove-addresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-EmailAddressPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-emailaddresspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-GlobalAddressList.md", + "redirect_url": "/powershell/module/exchange/remove-globaladdresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-OabVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/remove-oabvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-OfflineAddressBook.md", + "redirect_url": "/powershell/module/exchange/remove-offlineaddressbook", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Restore-DetailsTemplate.md", + "redirect_url": "/powershell/module/exchange/restore-detailstemplate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-AddressBookPolicy.md", + "redirect_url": "/powershell/module/exchange/set-addressbookpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-AddressList.md", + "redirect_url": "/powershell/module/exchange/set-addresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-DetailsTemplate.md", + "redirect_url": "/powershell/module/exchange/set-detailstemplate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-EmailAddressPolicy.md", + "redirect_url": "/powershell/module/exchange/set-emailaddresspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-GlobalAddressList.md", + "redirect_url": "/powershell/module/exchange/set-globaladdresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-OabVirtualDirectory.md", + "redirect_url": "/powershell/module/exchange/set-oabvirtualdirectory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md", + "redirect_url": "/powershell/module/exchange/set-offlineaddressbook", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-AddressList.md", + "redirect_url": "/powershell/module/exchange/update-addresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-EmailAddressPolicy.md", + "redirect_url": "/powershell/module/exchange/update-emailaddresspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-GlobalAddressList.md", + "redirect_url": "/powershell/module/exchange/update-globaladdresslist", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-OfflineAddressBook.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Export-ExchangeCertificate.md", + "redirect_url": "/powershell/module/exchange/export-exchangecertificate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-DataEncryptionPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-IRMConfiguration.md", + "redirect_url": "/powershell/module/exchange/get-irmconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-OMEConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-RMSTemplate.md", + "redirect_url": "/powershell/module/exchange/get-rmstemplate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md", + "redirect_url": "/powershell/module/exchange/#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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Import-ExchangeCertificate.md", + "redirect_url": "/powershell/module/exchange/import-exchangecertificate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Import-RMSTrustedPublishingDomain.md", + "redirect_url": "/powershell/module/exchange/#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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-ExchangeCertificate.md", + "redirect_url": "/powershell/module/exchange/new-exchangecertificate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-OMEConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-OMEConfiguration.md", + "redirect_url": "/powershell/module/exchange/remove-omeconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md", + "redirect_url": "/powershell/module/exchange/#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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-IRMConfiguration.md", + "redirect_url": "/powershell/module/exchange/set-irmconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-OMEConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-RMSTemplate.md", + "redirect_url": "/powershell/module/exchange/set-rmstemplate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md", + "redirect_url": "/powershell/module/exchange/#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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Test-IRMConfiguration.md", + "redirect_url": "/powershell/module/exchange/test-irmconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Add-FederatedDomain.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Enable-RemoteMailbox.md", + "redirect_url": "/powershell/module/exchange/enable-remotemailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederatedDomainProof.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederationInformation.md", + "redirect_url": "/powershell/module/exchange/get-federationinformation", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederationTrust.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridMailflow.md", + "redirect_url": "/powershell/module/exchange/get-hybridmailflow", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridMailflowDatacenterIPs.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-IntraOrganizationConnector.md", + "redirect_url": "/powershell/module/exchange/get-intraorganizationconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-OnPremisesOrganization.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-RemoteMailbox.md", + "redirect_url": "/powershell/module/exchange/get-remotemailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-FederationTrust.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-IntraOrganizationConnector.md", + "redirect_url": "/powershell/module/exchange/new-intraorganizationconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-OnPremisesOrganization.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-FederatedDomain.md", + "redirect_url": "/powershell/module/exchange/remove-federateddomain", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-FederationTrust.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-IntraOrganizationConnector.md", + "redirect_url": "/powershell/module/exchange/remove-intraorganizationconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-OnPremisesOrganization.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-FederatedOrganizationIdentifier.md", + "redirect_url": "/powershell/module/exchange/set-federatedorganizationidentifier", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-FederationTrust.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-HybridMailflow.md", + "redirect_url": "/powershell/module/exchange/set-hybridmailflow", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-IntraOrganizationConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-PendingFederatedDomain.md", + "redirect_url": "/powershell/module/exchange/set-pendingfederateddomain", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-RemoteMailbox.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Test-FederationTrustCertificate.md", + "redirect_url": "/powershell/module/exchange/test-federationtrustcertificate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Update-HybridConfiguration.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Add-ResubmitRequest.md", + "redirect_url": "/powershell/module/exchange/add-resubmitrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Disable-TransportAgent.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Export-Message.md", + "redirect_url": "/powershell/module/exchange/export-message", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-AcceptedDomain.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-DeliveryAgentConnector.md", + "redirect_url": "/powershell/module/exchange/get-deliveryagentconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-EdgeSubscription.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ForeignConnector.md", + "redirect_url": "/powershell/module/exchange/get-foreignconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-FrontendTransportService.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MailboxTransportService.md", + "redirect_url": "/powershell/module/exchange/get-mailboxtransportservice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-Message.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTraceDetail.md", + "redirect_url": "/powershell/module/exchange/get-messagetracedetail", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTrackingLog.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-NetworkConnectionInfo.md", + "redirect_url": "/powershell/module/exchange/get-networkconnectioninfo", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-OutboundConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-QueueDigest.md", + "redirect_url": "/powershell/module/exchange/get-queuedigest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ReceiveConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ResubmitRequest.md", + "redirect_url": "/powershell/module/exchange/get-resubmitrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-RoutingGroupConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-SystemMessage.md", + "redirect_url": "/powershell/module/exchange/get-systemmessage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportAgent.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportPipeline.md", + "redirect_url": "/powershell/module/exchange/get-transportpipeline", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportServer.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-X400AuthoritativeDomain.md", + "redirect_url": "/powershell/module/exchange/get-x400authoritativedomain", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Install-TransportAgent.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-AddressRewriteEntry.md", + "redirect_url": "/powershell/module/exchange/new-addressrewriteentry", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-DeliveryAgentConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-EdgeSyncServiceConfig.md", + "redirect_url": "/powershell/module/exchange/new-edgesyncserviceconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-ForeignConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-OutboundConnector.md", + "redirect_url": "/powershell/module/exchange/new-outboundconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-ReceiveConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-RoutingGroupConnector.md", + "redirect_url": "/powershell/module/exchange/new-routinggroupconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-SendConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/New-X400AuthoritativeDomain.md", + "redirect_url": "/powershell/module/exchange/new-x400authoritativedomain", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Redirect-Message.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-AddressRewriteEntry.md", + "redirect_url": "/powershell/module/exchange/remove-addressrewriteentry", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-DeliveryAgentConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ForeignConnector.md", + "redirect_url": "/powershell/module/exchange/remove-foreignconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-InboundConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-OutboundConnector.md", + "redirect_url": "/powershell/module/exchange/remove-outboundconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ReceiveConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ResubmitRequest.md", + "redirect_url": "/powershell/module/exchange/remove-resubmitrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-RoutingGroupConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-SystemMessage.md", + "redirect_url": "/powershell/module/exchange/remove-systemmessage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-X400AuthoritativeDomain.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Resume-Queue.md", + "redirect_url": "/powershell/module/exchange/resume-queue", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Retry-Queue.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-AcceptedDomain.md", + "redirect_url": "/powershell/module/exchange/set-accepteddomain", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-AddressRewriteEntry.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-EdgeSyncServiceConfig.md", + "redirect_url": "/powershell/module/exchange/set-edgesyncserviceconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ForeignConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-InboundConnector.md", + "redirect_url": "/powershell/module/exchange/set-inboundconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-MailboxTransportService.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ReceiveConnector.md", + "redirect_url": "/powershell/module/exchange/set-receiveconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-RemoteDomain.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-RoutingGroupConnector.md", + "redirect_url": "/powershell/module/exchange/set-routinggroupconnector", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-SendConnector.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportAgent.md", + "redirect_url": "/powershell/module/exchange/set-transportagent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportService.md", + "redirect_url": "/powershell/module/exchange/set-transportservice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-X400AuthoritativeDomain.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Start-HistoricalSearch.md", + "redirect_url": "/powershell/module/exchange/start-historicalsearch", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Stop-HistoricalSearch.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Suspend-Queue.md", + "redirect_url": "/powershell/module/exchange/suspend-queue", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Test-EdgeSynchronization.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Test-SmtpConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-smtpconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mail-flow/Uninstall-TransportAgent.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Clean-MailboxDatabase.md", + "redirect_url": "/powershell/module/exchange/clean-mailboxdatabase", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Disable-MailboxQuarantine.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Dismount-Database.md", + "redirect_url": "/powershell/module/exchange/dismount-database", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Enable-MailboxQuarantine.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-FailedContentIndexDocuments.md", + "redirect_url": "/powershell/module/exchange/get-failedcontentindexdocuments", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxDatabase.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxServer.md", + "redirect_url": "/powershell/module/exchange/get-mailboxserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-SearchDocumentFormat.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Mount-Database.md", + "redirect_url": "/powershell/module/exchange/mount-database", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Move-DatabasePath.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-MailboxRepairRequest.md", + "redirect_url": "/powershell/module/exchange/new-mailboxrepairrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-SearchDocumentFormat.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-MailboxRepairRequest.md", + "redirect_url": "/powershell/module/exchange/remove-mailboxrepairrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-SearchDocumentFormat.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-MailboxDatabase.md", + "redirect_url": "/powershell/module/exchange/set-mailboxdatabase", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-MailboxServer.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-AssistantHealth.md", + "redirect_url": "/powershell/module/exchange/test-assistanthealth", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-ExchangeSearch.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-DatabaseSchema.md", + "redirect_url": "/powershell/module/exchange/update-databaseschema", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-FileDistributionService.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Add-MailboxFolderPermission.md", + "redirect_url": "/powershell/module/exchange/add-mailboxfolderpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Add-MailboxPermission.md", + "redirect_url": "/powershell/module/exchange/add-mailboxpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Add-RecipientPermission.md", + "redirect_url": "/powershell/module/exchange/add-recipientpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Connect-Mailbox.md", + "redirect_url": "/powershell/module/exchange/connect-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-App.md", + "redirect_url": "/powershell/module/exchange/disable-app", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-InboxRule.md", + "redirect_url": "/powershell/module/exchange/disable-inboxrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-Mailbox.md", + "redirect_url": "/powershell/module/exchange/disable-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-ServiceEmailChannel.md", + "redirect_url": "/powershell/module/exchange/disable-serviceemailchannel", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-SweepRule.md", + "redirect_url": "/powershell/module/exchange/disable-sweeprule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-App.md", + "redirect_url": "/powershell/module/exchange/enable-app", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-InboxRule.md", + "redirect_url": "/powershell/module/exchange/enable-inboxrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-Mailbox.md", + "redirect_url": "/powershell/module/exchange/enable-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-ServiceEmailChannel.md", + "redirect_url": "/powershell/module/exchange/enable-serviceemailchannel", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-SweepRule.md", + "redirect_url": "/powershell/module/exchange/enable-sweeprule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Export-MailboxDiagnosticLogs.md", + "redirect_url": "/powershell/module/exchange/export-mailboxdiagnosticlogs", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Export-RecipientDataProperty.md", + "redirect_url": "/powershell/module/exchange/export-recipientdataproperty", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-App.md", + "redirect_url": "/powershell/module/exchange/get-app", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticAnalysis.md", + "redirect_url": "/powershell/module/exchange/get-calendardiagnosticanalysis", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticLog.md", + "redirect_url": "/powershell/module/exchange/get-calendardiagnosticlog", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticObjects.md", + "redirect_url": "/powershell/module/exchange/get-calendardiagnosticobjects", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarNotification.md", + "redirect_url": "/powershell/module/exchange/get-calendarnotification", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarProcessing.md", + "redirect_url": "/powershell/module/exchange/get-calendarprocessing", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Clutter.md", + "redirect_url": "/powershell/module/exchange/get-clutter", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-FocusedInbox.md", + "redirect_url": "/powershell/module/exchange/get-focusedinbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-InboxRule.md", + "redirect_url": "/powershell/module/exchange/get-inboxrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Mailbox.md", + "redirect_url": "/powershell/module/exchange/get-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxAutoReplyConfiguration.md", + "redirect_url": "/powershell/module/exchange/get-mailboxautoreplyconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxCalendarFolder.md", + "redirect_url": "/powershell/module/exchange/get-mailboxcalendarfolder", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxExportRequest.md", + "redirect_url": "/powershell/module/exchange/get-mailboxexportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxExportRequestStatistics.md", + "redirect_url": "/powershell/module/exchange/get-mailboxexportrequeststatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolder.md", + "redirect_url": "/powershell/module/exchange/get-mailboxfolder", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolderPermission.md", + "redirect_url": "/powershell/module/exchange/get-mailboxfolderpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolderStatistics.md", + "redirect_url": "/powershell/module/exchange/get-mailboxfolderstatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxImportRequest.md", + "redirect_url": "/powershell/module/exchange/get-mailboximportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxImportRequestStatistics.md", + "redirect_url": "/powershell/module/exchange/get-mailboximportrequeststatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxLocation.md", + "redirect_url": "/powershell/module/exchange/get-mailboxlocation", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxPermission.md", + "redirect_url": "/powershell/module/exchange/get-mailboxpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxPlan.md", + "redirect_url": "/powershell/module/exchange/get-mailboxplan", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxRestoreRequest.md", + "redirect_url": "/powershell/module/exchange/get-mailboxrestorerequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxRestoreRequestStatistics.md", + "redirect_url": "/powershell/module/exchange/get-mailboxrestorerequeststatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxSentItemsConfiguration.md", + "redirect_url": "/powershell/module/exchange/get-mailboxsentitemsconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxStatistics.md", + "redirect_url": "/powershell/module/exchange/get-mailboxstatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxUserConfiguration.md", + "redirect_url": "/powershell/module/exchange/get-mailboxuserconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MessageCategory.md", + "redirect_url": "/powershell/module/exchange/get-messagecategory", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Place.md", + "redirect_url": "/powershell/module/exchange/get-place", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-RecipientPermission.md", + "redirect_url": "/powershell/module/exchange/get-recipientpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-RecoverableItems.md", + "redirect_url": "/powershell/module/exchange/get-recoverableitems", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-ResourceConfig.md", + "redirect_url": "/powershell/module/exchange/get-resourceconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-SweepRule.md", + "redirect_url": "/powershell/module/exchange/get-sweeprule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-UserPhoto.md", + "redirect_url": "/powershell/module/exchange/get-userphoto", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Import-ContactList.md", + "redirect_url": "https://support.microsoft.com/office/import-contacts-to-outlook-bb796340-b58a-46c1-90c7-b549b8f3c5f8", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Import-RecipientDataProperty.md", + "redirect_url": "/powershell/module/exchange/import-recipientdataproperty", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-App.md", + "redirect_url": "/powershell/module/exchange/new-app", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-InboxRule.md", + "redirect_url": "/powershell/module/exchange/new-inboxrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-Mailbox.md", + "redirect_url": "/powershell/module/exchange/new-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxExportRequest.md", + "redirect_url": "/powershell/module/exchange/new-mailboxexportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxFolder.md", + "redirect_url": "/powershell/module/exchange/new-mailboxfolder", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxImportRequest.md", + "redirect_url": "/powershell/module/exchange/new-mailboximportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxRestoreRequest.md", + "redirect_url": "/powershell/module/exchange/new-mailboxrestorerequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailMessage.md", + "redirect_url": "/powershell/module/exchange/new-mailmessage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-SiteMailbox.md", + "redirect_url": "/powershell/module/exchange/new-sitemailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/New-SweepRule.md", + "redirect_url": "/powershell/module/exchange/new-sweeprule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-App.md", + "redirect_url": "/powershell/module/exchange/remove-app", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-CalendarEvents.md", + "redirect_url": "/powershell/module/exchange/remove-calendarevents", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-InboxRule.md", + "redirect_url": "/powershell/module/exchange/remove-inboxrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-Mailbox.md", + "redirect_url": "/powershell/module/exchange/remove-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxExportRequest.md", + "redirect_url": "/powershell/module/exchange/remove-mailboxexportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxFolderPermission.md", + "redirect_url": "/powershell/module/exchange/remove-mailboxfolderpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxImportRequest.md", + "redirect_url": "/powershell/module/exchange/remove-mailboximportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxPermission.md", + "redirect_url": "/powershell/module/exchange/remove-mailboxpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxRestoreRequest.md", + "redirect_url": "/powershell/module/exchange/remove-mailboxrestorerequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxUserConfiguration.md", + "redirect_url": "/powershell/module/exchange/remove-mailboxuserconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-RecipientPermission.md", + "redirect_url": "/powershell/module/exchange/remove-recipientpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-SweepRule.md", + "redirect_url": "/powershell/module/exchange/remove-sweeprule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-UserPhoto.md", + "redirect_url": "/powershell/module/exchange/remove-userphoto", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Restore-Mailbox.md", + "redirect_url": "/powershell/module/exchange/restore-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Restore-RecoverableItems.md", + "redirect_url": "/powershell/module/exchange/restore-recoverableitems", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxExportRequest.md", + "redirect_url": "/powershell/module/exchange/resume-mailboxexportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxImportRequest.md", + "redirect_url": "/powershell/module/exchange/resume-mailboximportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxRestoreRequest.md", + "redirect_url": "/powershell/module/exchange/resume-mailboxrestorerequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Search-Mailbox.md", + "redirect_url": "/powershell/module/exchange/search-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-App.md", + "redirect_url": "/powershell/module/exchange/set-app", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-CalendarNotification.md", + "redirect_url": "/powershell/module/exchange/set-calendarnotification", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-CalendarProcessing.md", + "redirect_url": "/powershell/module/exchange/set-calendarprocessing", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Clutter.md", + "redirect_url": "/powershell/module/exchange/set-clutter", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-FocusedInbox.md", + "redirect_url": "/powershell/module/exchange/set-focusedinbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-InboxRule.md", + "redirect_url": "/powershell/module/exchange/set-inboxrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Mailbox.md", + "redirect_url": "/powershell/module/exchange/set-mailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxAutoReplyConfiguration.md", + "redirect_url": "/powershell/module/exchange/set-mailboxautoreplyconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxCalendarFolder.md", + "redirect_url": "/powershell/module/exchange/set-mailboxcalendarfolder", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxExportRequest.md", + "redirect_url": "/powershell/module/exchange/set-mailboxexportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxFolderPermission.md", + "redirect_url": "/powershell/module/exchange/set-mailboxfolderpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxImportRequest.md", + "redirect_url": "/powershell/module/exchange/set-mailboximportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxPlan.md", + "redirect_url": "/powershell/module/exchange/set-mailboxplan", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxRestoreRequest.md", + "redirect_url": "/powershell/module/exchange/set-mailboxrestorerequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxSentItemsConfiguration.md", + "redirect_url": "/powershell/module/exchange/set-mailboxsentitemsconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Place.md", + "redirect_url": "/powershell/module/exchange/set-place", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-ResourceConfig.md", + "redirect_url": "/powershell/module/exchange/set-resourceconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-SweepRule.md", + "redirect_url": "/powershell/module/exchange/set-sweeprule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-UserPhoto.md", + "redirect_url": "/powershell/module/exchange/set-userphoto", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxExportRequest.md", + "redirect_url": "/powershell/module/exchange/suspend-mailboxexportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxImportRequest.md", + "redirect_url": "/powershell/module/exchange/suspend-mailboximportrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxRestoreRequest.md", + "redirect_url": "/powershell/module/exchange/suspend-mailboxrestorerequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Test-MAPIConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-mapiconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/mailboxes/Undo-SoftDeletedMailbox.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Export-MigrationReport.md", + "redirect_url": "/powershell/module/exchange/export-migrationreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationBatch.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationEndpoint.md", + "redirect_url": "/powershell/module/exchange/get-migrationendpoint", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationStatistics.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationUserStatistics.md", + "redirect_url": "/powershell/module/exchange/get-migrationuserstatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MoveRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequest.md", + "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxmigrationrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequestStatistics.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMigrationRequestStatistics.md", + "redirect_url": "/powershell/module/exchange/get-publicfoldermigrationrequeststatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMoveRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MigrationBatch.md", + "redirect_url": "/powershell/module/exchange/new-migrationbatch", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MigrationEndpoint.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-PublicFolderMigrationRequest.md", + "redirect_url": "/powershell/module/exchange/new-publicfoldermigrationrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-PublicFolderMoveRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationEndpoint.md", + "redirect_url": "/powershell/module/exchange/remove-migrationendpoint", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMailboxMigrationRequest.md", + "redirect_url": "/powershell/module/exchange/remove-publicfoldermailboxmigrationrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMigrationRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-MoveRequest.md", + "redirect_url": "/powershell/module/exchange/resume-moverequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-PublicFolderMigrationRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationBatch.md", + "redirect_url": "/powershell/module/exchange/set-migrationbatch", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationUser.md", + "redirect_url": "/powershell/module/exchange/set-migrationuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MoveRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-PublicFolderMoveRequest.md", + "redirect_url": "/powershell/module/exchange/set-publicfoldermoverequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Start-MigrationBatch.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Stop-MigrationBatch.md", + "redirect_url": "/powershell/module/exchange/stop-migrationbatch", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Stop-MigrationUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMailboxMigrationRequest.md", + "redirect_url": "/powershell/module/exchange/suspend-publicfoldermailboxmigrationrequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMigrationRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/move-and-migration/Test-MigrationServerAvailability.md", + "redirect_url": "/powershell/module/exchange/test-migrationserveravailability", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Disable-CmdletExtensionAgent.md", + "redirect_url": "/powershell/module/exchange/disable-cmdletextensionagent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Enable-CmdletExtensionAgent.md", + "redirect_url": "/powershell/module/exchange/enable-cmdletextensionagent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Enable-OrganizationCustomization.md", + "redirect_url": "/powershell/module/exchange/enable-organizationcustomization", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-AccessToCustomerDataRequest.md", + "redirect_url": "/powershell/module/exchange/get-accesstocustomerdatarequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-ApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/get-applicationaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-AuthConfig.md", + "redirect_url": "/powershell/module/exchange/get-authconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-AuthenticationPolicy.md", + "redirect_url": "/powershell/module/exchange/get-authenticationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-AuthServer.md", + "redirect_url": "/powershell/module/exchange/get-authserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-CmdletExtensionAgent.md", + "redirect_url": "/powershell/module/exchange/get-cmdletextensionagent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeAssistanceConfig.md", + "redirect_url": "/powershell/module/exchange/get-exchangeassistanceconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeDiagnosticInfo.md", + "redirect_url": "/powershell/module/exchange/get-exchangediagnosticinfo", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServer.md", + "redirect_url": "/powershell/module/exchange/get-exchangeserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServerAccessLicense.md", + "redirect_url": "/powershell/module/exchange/get-exchangeserveraccesslicense", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServerAccessLicenseUser.md", + "redirect_url": "/powershell/module/exchange/get-exchangeserveraccesslicenseuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeSettings.md", + "redirect_url": "/powershell/module/exchange/get-exchangesettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-Notification.md", + "redirect_url": "/powershell/module/exchange/get-notification", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-OrganizationConfig.md", + "redirect_url": "/powershell/module/exchange/get-organizationconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-PartnerApplication.md", + "redirect_url": "/powershell/module/exchange/get-partnerapplication", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-PerimeterConfig.md", + "redirect_url": "/powershell/module/exchange/get-perimeterconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Get-SettingOverride.md", + "redirect_url": "/powershell/module/exchange/get-settingoverride", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/New-ApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/new-applicationaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/New-AuthenticationPolicy.md", + "redirect_url": "/powershell/module/exchange/new-authenticationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/New-AuthServer.md", + "redirect_url": "/powershell/module/exchange/new-authserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/New-ExchangeSettings.md", + "redirect_url": "/powershell/module/exchange/new-exchangesettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/New-PartnerApplication.md", + "redirect_url": "/powershell/module/exchange/new-partnerapplication", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/New-SettingOverride.md", + "redirect_url": "/powershell/module/exchange/new-settingoverride", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Remove-ApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-applicationaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Remove-AuthenticationPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-authenticationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Remove-AuthServer.md", + "redirect_url": "/powershell/module/exchange/remove-authserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Remove-PartnerApplication.md", + "redirect_url": "/powershell/module/exchange/remove-partnerapplication", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Remove-SettingOverride.md", + "redirect_url": "/powershell/module/exchange/remove-settingoverride", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-AccessToCustomerDataRequest.md", + "redirect_url": "/powershell/module/exchange/set-accesstocustomerdatarequest", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-ApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/set-applicationaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-AuthConfig.md", + "redirect_url": "/powershell/module/exchange/set-authconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-AuthenticationPolicy.md", + "redirect_url": "/powershell/module/exchange/set-authenticationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-AuthServer.md", + "redirect_url": "/powershell/module/exchange/set-authserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-CmdletExtensionAgent.md", + "redirect_url": "/powershell/module/exchange/set-cmdletextensionagent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeAssistanceConfig.md", + "redirect_url": "/powershell/module/exchange/set-exchangeassistanceconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeServer.md", + "redirect_url": "/powershell/module/exchange/set-exchangeserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeSettings.md", + "redirect_url": "/powershell/module/exchange/set-exchangesettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-Notification.md", + "redirect_url": "/powershell/module/exchange/set-notification", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-OrganizationConfig.md", + "redirect_url": "/powershell/module/exchange/set-organizationconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-PartnerApplication.md", + "redirect_url": "/powershell/module/exchange/set-partnerapplication", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-PerimeterConfig.md", + "redirect_url": "/powershell/module/exchange/set-perimeterconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Set-SettingOverride.md", + "redirect_url": "/powershell/module/exchange/set-settingoverride", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Test-ApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/exchange/test-applicationaccesspolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Test-OAuthConnectivity.md", + "redirect_url": "/powershell/module/exchange/test-oauthconnectivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Test-SystemHealth.md", + "redirect_url": "/powershell/module/exchange/test-systemhealth", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/organization/Update-ExchangeHelp.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-JournalRule.md", + "redirect_url": "/powershell/module/exchange/disable-journalrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-OutlookProtectionRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-JournalRule.md", + "redirect_url": "/powershell/module/exchange/enable-journalrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-OutlookProtectionRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Export-JournalRuleCollection.md", + "redirect_url": "/powershell/module/exchange/export-journalrulecollection", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Export-TransportRuleCollection.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-AdministrativeUnit.md", + "redirect_url": "/powershell/module/exchange/get-administrativeunit", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierPoliciesApplicationStatus.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierRecipientStatus.md", + "redirect_url": "/powershell/module/exchange/get-informationbarrierrecipientstatus", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-JournalRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-LabelPolicy.md", + "redirect_url": "/powershell/module/exchange/get-labelpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-MessageClassification.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-OutlookProtectionRule.md", + "redirect_url": "/powershell/module/exchange/get-outlookprotectionrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-ProtectionAlert.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-SupervisoryReviewRule.md", + "redirect_url": "/powershell/module/exchange/get-supervisoryreviewrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRulePredicate.md", + "redirect_url": "/powershell/module/exchange/get-transportrulepredicate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Import-JournalRuleCollection.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Install-UnifiedCompliancePrerequisite.md", + "redirect_url": "/powershell/module/exchange/install-unifiedcomplianceprerequisite", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-ActivityAlert.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-JournalRule.md", + "redirect_url": "/powershell/module/exchange/new-journalrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-Label.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-MessageClassification.md", + "redirect_url": "/powershell/module/exchange/new-messageclassification", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-OrganizationSegment.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-ProtectionAlert.md", + "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-SupervisoryReviewPolicyV2.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-TransportRule.md", + "redirect_url": "/powershell/module/exchange/new-transportrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-ActivityAlert.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-JournalRule.md", + "redirect_url": "/powershell/module/exchange/remove-journalrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-Label.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-MessageClassification.md", + "redirect_url": "/powershell/module/exchange/remove-messageclassification", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-OrganizationSegment.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-ProtectionAlert.md", + "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-SupervisoryReviewPolicyV2.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-ActivityAlert.md", + "redirect_url": "/powershell/module/exchange/set-activityalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-InformationBarrierPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-Label.md", + "redirect_url": "/powershell/module/exchange/set-label", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-LabelPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-OrganizationSegment.md", + "redirect_url": "/powershell/module/exchange/set-organizationsegment", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-OutlookProtectionRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-SupervisoryReviewPolicyV2.md", + "redirect_url": "/powershell/module/exchange/set-supervisoryreviewpolicyv2", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-SupervisoryReviewRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Start-InformationBarrierPoliciesApplication.md", + "redirect_url": "/powershell/module/exchange/start-informationbarrierpoliciesapplication", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Stop-InformationBarrierPoliciesApplication.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AdminAuditLogConfig.md", + "redirect_url": "/powershell/module/exchange/get-adminauditlogconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/get-auditconfigurationrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditLogSearch.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-UnifiedAuditLogRetentionPolicy.md", + "redirect_url": "/powershell/module/exchange/get-unifiedauditlogretentionpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AdminAuditLogSearch.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AuditConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/new-auditconfigurationrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-MailboxAuditLogSearch.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-AuditConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-auditconfigurationpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-AuditConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-AdminAuditLog.md", + "redirect_url": "/powershell/module/exchange/search-adminauditlog", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-MailboxAuditLog.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md", + "redirect_url": "/powershell/module/exchange/set-adminauditlogconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AuditConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-MailboxAuditBypassAssociation.md", + "redirect_url": "/powershell/module/exchange/set-mailboxauditbypassassociation", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-UnifiedAuditLogRetentionPolicy.md", + "redirect_url": "/powershell/module/exchange/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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Export-DlpPolicyCollection.md", + "redirect_url": "/powershell/module/exchange/export-dlppolicycollection", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-ClassificationRuleCollection.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DataClassificationConfig.md", + "redirect_url": "/powershell/module/exchange/get-dataclassificationconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpCompliancePolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpDetailReport.md", + "redirect_url": "/powershell/module/exchange/get-dlpdetailreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpDetectionsReport.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpKeywordDictionary.md", + "redirect_url": "/powershell/module/exchange/get-dlpkeyworddictionary", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationType.md", + "redirect_url": "/powershell/module/exchange/get-dlpsensitiveinformationtype", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationTypeRulePackage.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-PolicyTipConfig.md", + "redirect_url": "/powershell/module/exchange/get-policytipconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Import-DlpPolicyCollection.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-ClassificationRuleCollection.md", + "redirect_url": "/powershell/module/exchange/new-classificationrulecollection", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DataClassification.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md", + "redirect_url": "/powershell/module/exchange/new-dlpcompliancerule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpEdmSchema.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpKeywordDictionary.md", + "redirect_url": "/powershell/module/exchange/new-dlpkeyworddictionary", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage.md", + "redirect_url": "/powershell/module/exchange/new-dlpsensitiveinformationtyperulepackage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-Fingerprint.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-ClassificationRuleCollection.md", + "redirect_url": "/powershell/module/exchange/remove-classificationrulecollection", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DataClassification.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRule.md", + "redirect_url": "/powershell/module/exchange/remove-dlpcompliancerule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-dlppolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpPolicyTemplate.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationTypeRulePackage.md", + "redirect_url": "/powershell/module/exchange/remove-dlpsensitiveinformationtyperulepackage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-PolicyTipConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DataClassification.md", + "redirect_url": "/powershell/module/exchange/set-dataclassification", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpEdmSchema.md", + "redirect_url": "/powershell/module/exchange/set-dlpedmschema", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpKeywordDictionary.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationType.md", + "redirect_url": "/powershell/module/exchange/set-dlpsensitiveinformationtype", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationTypeRulePackage.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Add-ComplianceCaseMember.md", + "redirect_url": "/powershell/module/exchange/add-compliancecasemember", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Add-eDiscoveryCaseAdmin.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-CaseHoldRule.md", + "redirect_url": "/powershell/module/exchange/get-caseholdrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-ComplianceCase.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-eDiscoveryCaseAdmin.md", + "redirect_url": "/powershell/module/exchange/get-ediscoverycaseadmin", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-CaseHoldPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-ComplianceCase.md", + "redirect_url": "/powershell/module/exchange/new-compliancecase", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCase.md", + "redirect_url": "/powershell/module/exchange/remove-compliancecase", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCaseMember.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-CaseHoldPolicy.md", + "redirect_url": "/powershell/module/exchange/set-caseholdpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-CaseHoldRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Update-ComplianceCaseMember.md", + "redirect_url": "/powershell/module/exchange/update-compliancecasemember", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Update-eDiscoveryCaseAdmin.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEvent.md", + "redirect_url": "/powershell/module/exchange/get-complianceretentionevent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEventType.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceTagStorage.md", + "redirect_url": "/powershell/module/exchange/get-compliancetagstorage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-DataRetentionReport.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-HoldComplianceRule.md", + "redirect_url": "/powershell/module/exchange/get-holdcompliancerule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedContentSettings.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedFolderMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/get-managedfoldermailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionCompliancePolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionEvent.md", + "redirect_url": "/powershell/module/exchange/get-retentionevent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceRetentionEvent.md", + "redirect_url": "/powershell/module/exchange/new-complianceretentionevent", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceRetentionEventType.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-HoldCompliancePolicy.md", + "redirect_url": "/powershell/module/exchange/new-holdcompliancepolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-HoldComplianceRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedFolder.md", + "redirect_url": "/powershell/module/exchange/new-managedfolder", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedFolderMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionComplianceRule.md", + "redirect_url": "/powershell/module/exchange/new-retentioncompliancerule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ComplianceRetentionEventType.md", + "redirect_url": "/powershell/module/exchange/remove-complianceretentioneventtype", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ComplianceTag.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-HoldComplianceRule.md", + "redirect_url": "/powershell/module/exchange/remove-holdcompliancerule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedContentSettings.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedFolderMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-managedfoldermailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionCompliancePolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-retentionpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionPolicyTag.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ComplianceTag.md", + "redirect_url": "/powershell/module/exchange/set-compliancetag", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-HoldCompliancePolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedContentSettings.md", + "redirect_url": "/powershell/module/exchange/set-managedcontentsettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedFolder.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionCompliancePolicy.md", + "redirect_url": "/powershell/module/exchange/set-retentioncompliancepolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionComplianceRule.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionPolicyTag.md", + "redirect_url": "/powershell/module/exchange/set-retentionpolicytag", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Start-ManagedFolderAssistant.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Stop-ManagedFolderAssistant.md", + "redirect_url": "/powershell/module/exchange/stop-managedfolderassistant", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Validate-RetentionRuleQuery.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOCasMailbox.md", + "redirect_url": "/powershell/module/exchange/get-exocasmailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailbox.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxFolderStatistics.md", + "redirect_url": "/powershell/module/exchange/get-exomailboxfolderstatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxPermission.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMobileDeviceStatistics.md", + "redirect_url": "/powershell/module/exchange/get-exomobiledevicestatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXORecipient.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-ConnectionByClientTypeDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-ConnectionByClientTypeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsActiveUserReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsAVConferenceTimeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsClientDeviceDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsClientDeviceReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsConferenceReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsP2PAVTimeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsP2PSessionReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsPSTNConferenceTimeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsPSTNUsageDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsUserActivitiesReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-CsUsersBlockedReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-GroupActivityReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-HistoricalSearch.md", + "redirect_url": "/powershell/module/exchange/get-historicalsearch", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-LicenseVsUsageSummaryReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-LogonStatistics.md", + "redirect_url": "/powershell/module/exchange/get-logonstatistics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailboxActivityReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailboxUsageDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailboxUsageReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailDlpPolicyReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetaildlppolicyreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailMalwareReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailSpamReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailTransportRuleReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailtransportrulereport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailFilterListReport.md", + "redirect_url": "/powershell/module/exchange/get-mailfilterlistreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficPolicyReport.md", + "redirect_url": "/powershell/module/exchange/get-mailtrafficpolicyreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficReport.md", + "redirect_url": "/powershell/module/exchange/get-mailtrafficreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficSummaryReport.md", + "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficTopReport.md", + "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-MxRecordReport.md", + "redirect_url": "/powershell/module/exchange/get-mxrecordreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-O365ClientBrowserDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-O365ClientBrowserReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-O365ClientOSDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-O365ClientOSReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-OutboundConnectorReport.md", + "redirect_url": "/powershell/module/exchange/get-outboundconnectorreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-RecipientStatisticsReport.md", + "redirect_url": "/powershell/module/exchange/get-recipientstatisticsreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-ReportExecutionInstance.md", + "redirect_url": "/powershell/module/exchange/get-reportexecutioninstance", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SCInsights.md", + "redirect_url": "/powershell/module/exchange/get-scinsights", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-ServiceDeliveryReport.md", + "redirect_url": "/powershell/module/exchange/get-servicedeliveryreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SPOActiveUserReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SPOSkyDriveProDeployedReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SPOSkyDriveProStorageReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SPOTeamSiteDeployedReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SPOTeamSiteStorageReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SPOTenantStorageMetricReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-StaleMailboxDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-StaleMailboxReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewActivity.md", + "redirect_url": "/powershell/module/exchange/get-supervisoryreviewactivity", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewOverallProgressReport.md", + "redirect_url": "/powershell/module/exchange/get-supervisoryreviewoverallprogressreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewPolicyReport.md", + "redirect_url": "/powershell/module/exchange/get-supervisoryreviewpolicyreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewReport.md", + "redirect_url": "/powershell/module/exchange/get-supervisoryreviewreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewTopCasesReport.md", + "redirect_url": "/powershell/module/exchange/get-supervisoryreviewtopcasesreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-TenantAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Get-UserAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Set-TenantAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/reporting/Set-UserAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Add-ManagementRoleEntry.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRole.md", + "redirect_url": "/powershell/module/exchange/get-managementrole", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRoleAssignment.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementScope.md", + "redirect_url": "/powershell/module/exchange/get-managementscope", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleAssignmentPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleGroupMember.md", + "redirect_url": "/powershell/module/exchange/get-rolegroupmember", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementRole.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementScope.md", + "redirect_url": "/powershell/module/exchange/new-managementscope", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-RoleAssignmentPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRole.md", + "redirect_url": "/powershell/module/exchange/remove-managementrole", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRoleAssignment.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementScope.md", + "redirect_url": "/powershell/module/exchange/remove-managementscope", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleAssignmentPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleGroupMember.md", + "redirect_url": "/powershell/module/exchange/remove-rolegroupmember", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementRoleAssignment.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementScope.md", + "redirect_url": "/powershell/module/exchange/set-managementscope", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-RoleAssignmentPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Update-RoleGroupMember.md", + "redirect_url": "/powershell/module/exchange/update-rolegroupmember", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Add-GlobalMonitoringOverride.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-AvailabilityReportOutage.md", + "redirect_url": "/powershell/module/exchange/get-availabilityreportoutage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-EventLogLevel.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-HealthReport.md", + "redirect_url": "/powershell/module/exchange/get-healthreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-MonitoringItemHelp.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerComponentState.md", + "redirect_url": "/powershell/module/exchange/get-servercomponentstate", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerHealth.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ThrottlingPolicy.md", + "redirect_url": "/powershell/module/exchange/get-throttlingpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ThrottlingPolicyAssociation.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/New-AvailabilityReportOutage.md", + "redirect_url": "/powershell/module/exchange/new-availabilityreportoutage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/New-ThrottlingPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-GlobalMonitoringOverride.md", + "redirect_url": "/powershell/module/exchange/remove-globalmonitoringoverride", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-ServerMonitoringOverride.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-AvailabilityReportOutage.md", + "redirect_url": "/powershell/module/exchange/set-availabilityreportoutage", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-EventLogLevel.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ServerMonitor.md", + "redirect_url": "/powershell/module/exchange/set-servermonitor", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ThrottlingPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Test-ServiceHealth.md", + "redirect_url": "/powershell/module/exchange/test-servicehealth", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-AvailabilityAddressSpace.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-PublicFolderClientPermission.md", + "redirect_url": "/powershell/module/exchange/add-publicfolderclientpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Disable-MailPublicFolder.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-AvailabilityAddressSpace.md", + "redirect_url": "/powershell/module/exchange/get-availabilityaddressspace", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-AvailabilityConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-OrganizationRelationship.md", + "redirect_url": "/powershell/module/exchange/get-organizationrelationship", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolder.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderClientPermission.md", + "redirect_url": "/powershell/module/exchange/get-publicfolderclientpermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderDatabase.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderMailboxDiagnostics.md", + "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxdiagnostics", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderStatistics.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailbox.md", + "redirect_url": "/powershell/module/exchange/get-sitemailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailboxDiagnostics.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-AvailabilityConfig.md", + "redirect_url": "/powershell/module/exchange/new-availabilityconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-OrganizationRelationship.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolderDatabase.md", + "redirect_url": "/powershell/module/exchange/new-publicfolderdatabase", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolderDatabaseRepairRequest.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SiteMailboxProvisioningPolicy.md", + "redirect_url": "/powershell/module/exchange/new-sitemailboxprovisioningpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SyncMailPublicFolder.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-AvailabilityConfig.md", + "redirect_url": "/powershell/module/exchange/remove-availabilityconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-OrganizationRelationship.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderAdministrativePermission.md", + "redirect_url": "/powershell/module/exchange/remove-publicfolderadministrativepermission", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderClientPermission.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SharingPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-sharingpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SiteMailboxProvisioningPolicy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Resume-PublicFolderReplication.md", + "redirect_url": "/powershell/module/exchange/resume-publicfolderreplication", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-AvailabilityConfig.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-OrganizationRelationship.md", + "redirect_url": "/powershell/module/exchange/set-organizationrelationship", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-PublicFolder.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SharingPolicy.md", + "redirect_url": "/powershell/module/exchange/set-sharingpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SiteMailbox.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Suspend-PublicFolderReplication.md", + "redirect_url": "/powershell/module/exchange/suspend-publicfolderreplication", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Test-OrganizationRelationship.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolder.md", + "redirect_url": "/powershell/module/exchange/update-publicfolder", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolderHierarchy.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-SiteMailbox.md", + "redirect_url": "/powershell/module/exchange/update-sitemailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMAutoAttendant.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMIPGateway.md", + "redirect_url": "/powershell/module/exchange/disable-umipgateway", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMMailbox.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMService.md", + "redirect_url": "/powershell/module/exchange/disable-umservice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMAutoAttendant.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMIPGateway.md", + "redirect_url": "/powershell/module/exchange/enable-umipgateway", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMMailbox.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMService.md", + "redirect_url": "/powershell/module/exchange/enable-umservice", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Export-UMCallDataRecord.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-OnlineMeetingConfiguration.md", + "redirect_url": "/powershell/module/exchange/get-onlinemeetingconfiguration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMActiveCalls.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallAnsweringRule.md", + "redirect_url": "/powershell/module/exchange/get-umcallansweringrule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallDataRecord.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallSummaryReport.md", + "redirect_url": "/powershell/module/exchange/get-umcallsummaryreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMDialPlan.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMIPGateway.md", + "redirect_url": "/powershell/module/exchange/get-umipgateway", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailbox.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/get-ummailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UmServer.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Import-UMPrompt.md", + "redirect_url": "/powershell/module/exchange/import-umprompt", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMAutoAttendant.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMDialPlan.md", + "redirect_url": "/powershell/module/exchange/new-umdialplan", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMHuntGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/new-ummailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMAutoAttendant.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMDialPlan.md", + "redirect_url": "/powershell/module/exchange/remove-umdialplan", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMHuntGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMMailboxPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-ummailboxpolicy", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMAutoAttendant.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMCallRouterSettings.md", + "redirect_url": "/powershell/module/exchange/set-umcallroutersettings", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMDialPlan.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailbox.md", + "redirect_url": "/powershell/module/exchange/set-ummailbox", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailboxPIN.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UmServer.md", + "redirect_url": "/powershell/module/exchange/set-umserver", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMService.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Add-DistributionGroupMember.md", + "redirect_url": "/powershell/module/exchange/add-distributiongroupmember", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Add-UnifiedGroupLinks.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-MailContact.md", + "redirect_url": "/powershell/module/exchange/disable-mailcontact", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-MailUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-MailContact.md", + "redirect_url": "/powershell/module/exchange/enable-mailcontact", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-MailUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DistributionGroup.md", + "redirect_url": "/powershell/module/exchange/get-distributiongroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DistributionGroupMember.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-EligibleDistributionGroupForMigration.md", + "redirect_url": "/powershell/module/exchange/get-eligibledistributiongroupformigration", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-Group.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-MailContact.md", + "redirect_url": "/powershell/module/exchange/get-mailcontact", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-MailUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-SecurityPrincipal.md", + "redirect_url": "/powershell/module/exchange/get-securityprincipal", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-UnifiedGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-User.md", + "redirect_url": "/powershell/module/exchange/get-user", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-DistributionGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-EOPDistributionGroup.md", + "redirect_url": "/powershell/module/exchange/new-distributiongroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-EOPMailUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-MailUser.md", + "redirect_url": "/powershell/module/exchange/new-mailuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-UnifiedGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DistributionGroupMember.md", + "redirect_url": "/powershell/module/exchange/remove-distributiongroupmember", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DynamicDistributionGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-EOPMailUser.md", + "redirect_url": "/powershell/module/exchange/remove-mailuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-MailContact.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-UnifiedGroup.md", + "redirect_url": "/powershell/module/exchange/remove-unifiedgroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-UnifiedGroupLinks.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-DistributionGroup.md", + "redirect_url": "/powershell/module/exchange/set-distributiongroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-DynamicDistributionGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPGroup.md", + "redirect_url": "/powershell/module/exchange/set-group", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPMailUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-Group.md", + "redirect_url": "/powershell/module/exchange/set-group", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-LinkedUser.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-MailUser.md", + "redirect_url": "/powershell/module/exchange/set-mailuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-UnifiedGroup.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Undo-SoftDeletedUnifiedGroup.md", + "redirect_url": "/powershell/module/exchange/undo-softdeletedunifiedgroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Update-DistributionGroupMember.md", + "redirect_url": "/powershell/module/exchange/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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/users-and-groups/Upgrade-DistributionGroup.md", + "redirect_url": "/powershell/module/exchange/upgrade-distributiongroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/office-365-scc/office-365-scc-powershell.md", + "redirect_url": "/powershell/exchange/scc-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-scc-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-scc-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/connect-to-exchange-servers-using-remote-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-servers-using-remote-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/control-remote-powershell-access-to-exchange-servers.md", + "redirect_url": "/powershell/exchange/control-remote-powershell-access-to-exchange-servers", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md", + "redirect_url": "/powershell/exchange/exchange-cmdlet-syntax", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/exchange-management-shell.md", + "redirect_url": "/powershell/exchange/exchange-management-shell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/find-exchange-cmdlet-permissions.md", + "redirect_url": "/powershell/exchange/find-exchange-cmdlet-permissions", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/open-the-exchange-management-shell.md", + "redirect_url": "/powershell/exchange/open-the-exchange-management-shell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/use-update-exchangehelp.md", + "redirect_url": "/powershell/exchange/exchange-management-shell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md", + "redirect_url": "/powershell/exchange/filter-properties", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/recipient-filters/recipient-filters.md", + "redirect_url": "/powershell/exchange/recipient-filters", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md", + "redirect_url": "/powershell/exchange/recipientfilter-properties", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/disable-access-to-exchange-online-powershell.md", + "redirect_url": "/powershell/exchange/disable-access-to-exchange-online-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell.md", + "redirect_url": "/powershell/exchange/exchange-online-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/app-only-auth-powershell-v2.md", + "redirect_url": "/powershell/exchange/app-only-auth-powershell-v2", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets.md", + "redirect_url": "/powershell/exchange/cmdlet-property-sets", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md", + "redirect_url": "/powershell/exchange/exchange-online-powershell-v2", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/filters-v2.md", + "redirect_url": "/powershell/exchange/filters-v2", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-online-protection-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/exchange-eop/exchange-online-protection-powershell.md", + "redirect_url": "/powershell/exchange/exchange-online-protection-powershell", + "redirect_document_id": true + }, + { + "source_path": "exchange/docs-conceptual/mfa-connect-to-exchange-online-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/mfa-connect-to-scc-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-scc-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-TenantAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-TenantAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/set-myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-UserAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-UserAnalyticsConfig.md", + "redirect_url": "/powershell/module/exchange/set-myanalyticsfeatureconfig", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-MailDetailMalwareReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-MailDetailSpamReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionTrafficReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-UrlTrace.md", + "redirect_url": "/powershell/module/exchange/get-safelinksaggregatereport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-MailTrafficReport.md", + "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Import-ContactList.md", + "redirect_url": "https://support.microsoft.com/office/import-contacts-to-outlook-bb796340-b58a-46c1-90c7-b549b8f3c5f8", + "redirect_document_id": false + }, + { + "source_path": "staffhub/docs-conceptual/index.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/docs-conceptual/intro.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/docs-conceptual/overview.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Add-StaffHubMember.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Add-StaffHubShift.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Add-StaffHubTeam.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Connect-StaffHub.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Get-StaffHubMember.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Get-StaffHubShifts.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Get-StaffHubTeamsForTenant.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Get-StaffHubUsersForTenant.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Import-StaffHubMember.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Import-StaffHubShift.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Import-StaffHubTeam.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Remove-StaffHubMember.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/Remove-StaffHubUser.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "staffhub/staffhub-ps/staffhub/staffhub.md", + "redirect_url": "/microsoftteams/expand-teams-across-your-org/shifts-for-teams-landing-page", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-RMSTrustedPublishingDomain.md", + "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Import-RMSTrustedPublishingDomain.md", + "redirect_url": "/powershell/module/exchange/#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_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-RMSTrustedPublishingDomain.md", + "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_document_id": false + }, + { + "source_path": "teams/docs-conceptual/intro.md", + "redirect_url": "/powershell/teams", + "redirect_document_id": false + }, + { + "source_path": "spmt/spmt-ps/spmt/spmt.md", + "redirect_url": "/powershell/module/spmt", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CustomNudge.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CustomNudgeAssignment.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CustomNudgeSettings.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-CustomNudge.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-CustomNudgeAssignment.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-CustomNudge.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-CustomNudgeAssignment.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-CustomNudge.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-CustomNudgeAssignment.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-CustomNudgeSettings.md", + "redirect_url": "/powershell/module/exchange/", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-MailTrafficTopReport.md", + "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-PhishFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistspoofitems", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-PhishFilterPolicy.md", + "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/basic-auth-connect-to-eop-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-online-protection-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/basic-auth-connect-to-exo-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/basic-auth-connect-to-scc-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-scc-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/v1-module-mfa-connect-to-exo-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-EOPDistributionGroup.md", + "redirect_url": "/powershell/module/exchange/new-distributiongroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-EOPMailUser.md", + "redirect_url": "/powershell/module/exchange/new-mailuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-EOPDistributionGroup.md", + "redirect_url": "/powershell/module/exchange/remove-distributiongroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-EOPMailUser.md", + "redirect_url": "/powershell/module/exchange/remove-mailuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-EOPDistributionGroup.md", + "redirect_url": "/powershell/module/exchange/set-distributiongroup", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-EOPGroup.md", + "redirect_url": "/powershell/module/exchange/set-group", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-EOPMailUser.md", + "redirect_url": "/powershell/module/exchange/set-mailuser", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-EOPUser.md", + "redirect_url": "/powershell/module/exchange/set-user", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Update-EOPDistributionGroupMember.md", + "redirect_url": "/powershell/module/exchange/update-distributiongroupmember", + "redirect_document_id": false + }, + { + "source_path": "teams/teams-ps/teams/New-CsTeamsShiftsConnectionTeamMap.yml", + "redirect_url": "https://review.learn.microsoft.com/en-us/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/use-update-exchangehelp.md", + "redirect_url": "/powershell/exchange/exchange-management-shell", + "redirect_document_id": false + }, + { + "source_path": "exchange/docs-conceptual/v1-module-mfa-connect-to-scc-powershell.md", + "redirect_url": "/powershell/exchange/connect-to-scc-powershell", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionDocumentDetail.md", + "redirect_url": "/powershell/module/exchange/get-contentmalwaremdodetailreport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionDocumentReport.md", + "redirect_url": "/powershell/module/exchange/get-contentmalwaremdoaggregatereport", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-SecOpsOverrideRule.md", + "redirect_url": "/powershell/module/exchange/new-exosecopsoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-SecOpsOverrideRule.md", + "redirect_url": "/powershell/module/exchange/remove-exosecopsoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-SecOpsOverrideRule.md", + "redirect_url": "/powershell/module/exchange/set-exosecopsoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-PhishSimOverrideRule.md", + "redirect_url": "/powershell/module/exchange/new-exophishsimoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-PhishSimOverrideRule.md", + "redirect_url": "/powershell/module/exchange/remove-exophishsimoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-PhishSimOverrideRule.md", + "redirect_url": "/powershell/module/exchange/set-exophishsimoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-ConnectionByClientTypeDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-ConnectionByClientTypeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsActiveUserReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsAVConferenceTimeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsClientDeviceDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsClientDeviceReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsConferenceReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsP2PAVTimeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsP2PSessionReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsPSTNConferenceTimeReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsPSTNUsageDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsUserActivitiesReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-CsUsersBlockedReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-GroupActivityReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, { + "source_path": "exchange/virtual-folder/exchange/Get-LicenseVsUsageSummaryReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-MailboxActivityReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-MailboxUsageDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-MailboxUsageReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, { + "source_path": "exchange/virtual-folder/exchange/Get-O365ClientBrowserDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-O365ClientBrowserReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-O365ClientOSDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-O365ClientOSReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-SPOActiveUserReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-SPOSkyDriveProDeployedReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-SPOSkyDriveProStorageReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-SPOTeamSiteDeployedReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-SPOTeamSiteStorageReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-SPOTenantStorageMetricReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-StaleMailboxDetailReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-StaleMailboxReport.md", + "redirect_url": "/graph/api/resources/report", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-HybridMailflow.md", + "redirect_url": "/exchange/exchange-hybrid", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-HybridMailflow.md", + "redirect_url": "/exchange/exchange-hybrid", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-PhishSimOverrideRule.md", + "redirect_url": "/powershell/module/exchange/get-exophishsimoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-SecOpsOverrideRule.md", + "redirect_url": "/powershell/module/exchange/get-exosecopsoverriderule", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-VivaFeatureCategory.md", + "redirect_url": "/viva/feature-access-management", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-AuditConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/get-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-AuditConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-AuditConfigurationPolicy.md", + "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-AuditConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/get-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-AuditConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-AuditConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-AuditConfigurationRule.md", + "redirect_url": "/powershell/module/exchange/set-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Get-ActivityAlert.md", + "redirect_url": "/powershell/module/exchange/get-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/New-ActivityAlert.md", + "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-ActivityAlert.md", + "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Set-ActivityAlert.md", + "redirect_url": "/powershell/module/exchange/set-protectionalert", + "redirect_document_id": false + }, + { + "source_path": "exchange/virtual-folder/exchange/Remove-RecordLabel.md", + "redirect_url": "/powershell/module/exchange/remove-label", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Disable-CsOnlineSipDomain.md", + "redirect_url": "/powershell/module/teams/Disable-CsOnlineSipDomain", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Enable-CsOnlineSipDomain.md", + "redirect_url": "/powershell/module/teams/Enable-CsOnlineSipDomain", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Export-CsAutoAttendantHolidays.md", + "redirect_url": "/powershell/module/teams/Export-CsAutoAttendantHolidays", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/export-csonlineaudiofile.md", + "redirect_url": "/powershell/module/teams/export-csonlineaudiofile", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Find-CsGroup.md", + "redirect_url": "/powershell/module/teams/Find-CsGroup", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Find-CsOnlineApplicationInstance.md", + "redirect_url": "/powershell/module/teams/Find-CsOnlineApplicationInstance", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsApplicationAccessPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsApplicationMeetingConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsApplicationMeetingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsAutoAttendant.md", + "redirect_url": "/powershell/module/teams/Get-CsAutoAttendant", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantHolidays.md", + "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantHolidays", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantStatus.md", + "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantStatus", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantSupportedLanguage.md", + "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantSupportedLanguage", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantSupportedTimeZone.md", + "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantSupportedTimeZone", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantTenantInformation.md", + "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantTenantInformation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsCallingLineIdentity.md", + "redirect_url": "/powershell/module/teams/Get-CsCallingLineIdentity", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsCallQueue.md", + "redirect_url": "/powershell/module/teams/Get-CsCallQueue", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsEffectiveTenantDialPlan.md", + "redirect_url": "/powershell/module/teams/Get-CsEffectiveTenantDialPlan", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsInboundBlockedNumberPattern.md", + "redirect_url": "/powershell/module/teams/Get-CsInboundBlockedNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsInboundExemptNumberPattern.md", + "redirect_url": "/powershell/module/teams/Get-CsInboundExemptNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsMeetingMigrationStatus.md", + "redirect_url": "/powershell/module/teams/Get-CsMeetingMigrationStatus", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationInstance.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineApplicationInstance", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationInstanceAssociation.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineApplicationInstanceAssociation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationInstanceAssociationStatus.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineApplicationInstanceAssociationStatus", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineAudioFile.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineAudioFile", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingBridge.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingBridge", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingLanguagesSupported.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingLanguagesSupported", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialinConferencingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialinConferencingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingServiceNumber.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingServiceNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialinConferencingTenantConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialinConferencingTenantConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingTenantSettings.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingTenantSettings", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingUser.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingUser", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialOutPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDialOutPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDirectoryTenant.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineDirectoryTenant", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineEnhancedEmergencyServiceDisclaimer", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineLisCivicAddress.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineLisCivicAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineLisLocation.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineLisLocation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineLisPort.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineLisPort", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineLisSubnet.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineLisSubnet", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineLisSwitch.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineLisSwitch", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineLisWirelessAccessPoint.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineLisWirelessAccessPoint", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlinePSTNGateway.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlinePSTNGateway", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlinePstnUsage.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlinePstnUsage", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineSchedule.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineSchedule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineSipDomain.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineSipDomain", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumber.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineTelephoneNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineUser.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineUser", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineVoicemailPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineVoicemailPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineVoicemailUserSettings.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineVoicemailUserSettings", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineVoiceRoute.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineVoiceRoute", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineVoiceRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineVoiceRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineVoiceUser.md", + "redirect_url": "/powershell/module/teams/Get-CsOnlineVoiceUser", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsAppPermissionPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsAppPermissionPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsAppSetupPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsAppSetupPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsAudioConferencingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsAudioConferencingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsCallHoldPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsCallHoldPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsCallParkPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsCallParkPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsChannelsPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsChannelsPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsClientConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsClientConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsComplianceRecordingApplication.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsComplianceRecordingApplication", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsComplianceRecordingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsComplianceRecordingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsCortanaPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsCortanaPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsEducationAssignmentsAppPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsEducationAssignmentsAppPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsEmergencyCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsEmergencyCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsEmergencyCallRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsEmergencyCallRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsFeedbackPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsFeedbackPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsGuestCallingConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsGuestCallingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsGuestMeetingConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsGuestMeetingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsGuestMessagingConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsGuestMessagingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsIPPhonePolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsIPPhonePolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingBrandingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingBrandingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingBroadcastConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingBroadcastConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingBroadcastPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingBroadcastPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsMessagingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsMessagingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsMobilityPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsMobilityPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsNetworkRoamingPolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsNetworkRoamingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsTranslationRule.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsTranslationRule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsVideoInteropServicePolicy.md", + "redirect_url": "/powershell/module/teams/Get-CsTeamsVideoInteropServicePolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenant.md", + "redirect_url": "/powershell/module/teams/Get-CsTenant", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantBlockedCallingNumbers.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantBlockedCallingNumbers", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantDialPlan.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantDialPlan", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantFederationConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantFederationConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantLicensingConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantLicensingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantMigrationConfiguration.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantMigrationConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantNetworkRegion.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantNetworkRegion", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantNetworkSite.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantNetworkSite", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantNetworkSubnet.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantNetworkSubnet", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantTrustedIPAddress.md", + "redirect_url": "/powershell/module/teams/Get-CsTenantTrustedIPAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsVideoInteropServiceProvider.md", + "redirect_url": "/powershell/module/teams/Get-CsVideoInteropServiceProvider", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsApplicationAccessPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsCallingLineIdentity.md", + "redirect_url": "/powershell/module/teams/Grant-CsCallingLineIdentity", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsCloudMeetingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsCloudMeetingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsDialoutPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsDialoutPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsExternalUserCommunicationPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsExternalUserCommunicationPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsOnlineVoicemailPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsOnlineVoicemailPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsOnlineVoiceRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsOnlineVoiceRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsAppPermissionPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsAppPermissionPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsAppSetupPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsAppSetupPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsAudioConferencingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsAudioConferencingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsCallHoldPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsCallHoldPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsCallParkPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsCallParkPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsChannelsPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsChannelsPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsComplianceRecordingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsComplianceRecordingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsCortanaPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsCortanaPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsEmergencyCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsEmergencyCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsEmergencyCallRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsFeedbackPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsFeedbackPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsIPPhonePolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsIPPhonePolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsMeetingBrandingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsMeetingBrandingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsMeetingBroadcastPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsMeetingBroadcastPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsMeetingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsMeetingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsMessagingPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsMessagingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsMobilityPolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsMobilityPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTeamsVideoInteropServicePolicy.md", + "redirect_url": "/powershell/module/teams/Grant-CsTeamsVideoInteropServicePolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsTenantDialPlan.md", + "redirect_url": "/powershell/module/teams/Grant-CsTenantDialPlan", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Import-CsAutoAttendantHolidays.md", + "redirect_url": "/powershell/module/teams/Import-CsAutoAttendantHolidays", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Import-CsOnlineAudioFile.md", + "redirect_url": "/powershell/module/teams/Import-CsOnlineAudioFile", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsApplicationAccessPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendant.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendant", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendantCallableEntity.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendantCallableEntity", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendantCallFlow.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendantCallFlow", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendantCallHandlingAssociation.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendantCallHandlingAssociation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendantDialScope.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendantDialScope", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendantMenu.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendantMenu", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendantMenuOption.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendantMenuOption", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsAutoAttendantPrompt.md", + "redirect_url": "/powershell/module/teams/New-CsAutoAttendantPrompt", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsCallingLineIdentity.md", + "redirect_url": "/powershell/module/teams/New-CsCallingLineIdentity", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsCallQueue.md", + "redirect_url": "/powershell/module/teams/New-CsCallQueue", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsEdgeAllowAllKnownDomains.md", + "redirect_url": "/powershell/module/teams/New-CsEdgeAllowAllKnownDomains", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsEdgeAllowList.md", + "redirect_url": "/powershell/module/teams/New-CsEdgeAllowList", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsEdgeDomainPattern.md", + "redirect_url": "/powershell/module/teams/New-CsEdgeDomainPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsInboundBlockedNumberPattern.md", + "redirect_url": "/powershell/module/teams/New-CsInboundBlockedNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsInboundExemptNumberPattern.md", + "redirect_url": "/powershell/module/teams/New-CsInboundExemptNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineApplicationInstance.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineApplicationInstance", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineApplicationInstanceAssociation.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineApplicationInstanceAssociation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineDateTimeRange.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineDateTimeRange", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineLisCivicAddress.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineLisCivicAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineLisLocation.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineLisLocation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlinePSTNGateway.md", + "redirect_url": "/powershell/module/teams/New-CsOnlinePSTNGateway", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineSchedule.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineSchedule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineTimeRange.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineTimeRange", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineVoicemailPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineVoicemailPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineVoiceRoute.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineVoiceRoute", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineVoiceRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsOnlineVoiceRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsAppPermissionPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsAppPermissionPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsAppSetupPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsAppSetupPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsAudioConferencingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsAudioConferencingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsCallHoldPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsCallHoldPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsCallingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsCallParkPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsCallParkPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsChannelsPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsChannelsPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsComplianceRecordingApplication.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsComplianceRecordingApplication", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsComplianceRecordingPairedApplication.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsComplianceRecordingPairedApplication", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsComplianceRecordingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsComplianceRecordingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsCortanaPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsCortanaPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyCallingExtendedNotification.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyCallingExtendedNotification", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyCallingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyCallRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyCallRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyNumber.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsFeedbackPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsFeedbackPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsIPPhonePolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsIPPhonePolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsMeetingBrandingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsMeetingBrandingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsMeetingBroadcastPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsMeetingBroadcastPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsMeetingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsMeetingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsMessagingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsMessagingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsMobilityPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsMobilityPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsNetworkRoamingPolicy.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsNetworkRoamingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsPinnedApp.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsPinnedApp", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTeamsTranslationRule.md", + "redirect_url": "/powershell/module/teams/New-CsTeamsTranslationRule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTenantDialPlan.md", + "redirect_url": "/powershell/module/teams/New-CsTenantDialPlan", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTenantNetworkRegion.md", + "redirect_url": "/powershell/module/teams/New-CsTenantNetworkRegion", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTenantNetworkSite.md", + "redirect_url": "/powershell/module/teams/New-CsTenantNetworkSite", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTenantNetworkSubnet.md", + "redirect_url": "/powershell/module/teams/New-CsTenantNetworkSubnet", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsTenantTrustedIPAddress.md", + "redirect_url": "/powershell/module/teams/New-CsTenantTrustedIPAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsVideoInteropServiceProvider.md", + "redirect_url": "/powershell/module/teams/New-CsVideoInteropServiceProvider", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Register-CsOnlineDialInConferencingServiceNumber.md", + "redirect_url": "/powershell/module/teams/Register-CsOnlineDialInConferencingServiceNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsApplicationAccessPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsAutoAttendant.md", + "redirect_url": "/powershell/module/teams/Remove-CsAutoAttendant", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsCallingLineIdentity.md", + "redirect_url": "/powershell/module/teams/Remove-CsCallingLineIdentity", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsCallQueue.md", + "redirect_url": "/powershell/module/teams/Remove-CsCallQueue", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsInboundBlockedNumberPattern.md", + "redirect_url": "/powershell/module/teams/Remove-CsInboundBlockedNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsInboundExemptNumberPattern.md", + "redirect_url": "/powershell/module/teams/Remove-CsInboundExemptNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineApplicationInstanceAssociation.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineApplicationInstanceAssociation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineAudioFile.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineAudioFile", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineDialInConferencingTenantSettings.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineDialInConferencingTenantSettings", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisCivicAddress.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisCivicAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisLocation.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisLocation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisPort.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisPort", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisSubnet.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisSubnet", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisSwitch.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisSwitch", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisWirelessAccessPoint.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisWirelessAccessPoint", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlinePSTNGateway.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlinePSTNGateway", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineSchedule.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineSchedule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineTelephoneNumber.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineTelephoneNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineVoicemailPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineVoicemailPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineVoiceRoute.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineVoiceRoute", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineVoiceRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsOnlineVoiceRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsAppPermissionPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsAppPermissionPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsAppSetupPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsAppSetupPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsAudioConferencingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsAudioConferencingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsCallHoldPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsCallHoldPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsCallParkPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsCallParkPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsChannelsPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsChannelsPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsComplianceRecordingApplication.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsComplianceRecordingApplication", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsComplianceRecordingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsComplianceRecordingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsCortanaPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsCortanaPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsEmergencyCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsEmergencyCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsEmergencyCallRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsEmergencyCallRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsFeedbackPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsFeedbackPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsIPPhonePolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsIPPhonePolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsMeetingBrandingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsMeetingBrandingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsMeetingBroadcastPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsMeetingBroadcastPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsMeetingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsMeetingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsMessagingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsMessagingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsMobilityPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsMobilityPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsNetworkRoamingPolicy.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsNetworkRoamingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsPinnedApp.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsPinnedApp", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTeamsTranslationRule.md", + "redirect_url": "/powershell/module/teams/Remove-CsTeamsTranslationRule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTenantDialPlan.md", + "redirect_url": "/powershell/module/teams/Remove-CsTenantDialPlan", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTenantNetworkRegion.md", + "redirect_url": "/powershell/module/teams/Remove-CsTenantNetworkRegion", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTenantNetworkSite.md", + "redirect_url": "/powershell/module/teams/Remove-CsTenantNetworkSite", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTenantNetworkSubnet.md", + "redirect_url": "/powershell/module/teams/Remove-CsTenantNetworkSubnet", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsTenantTrustedIPAddress.md", + "redirect_url": "/powershell/module/teams/Remove-CsTenantTrustedIPAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsVideoInteropServiceProvider.md", + "redirect_url": "/powershell/module/teams/Remove-CsVideoInteropServiceProvider", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsApplicationAccessPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsApplicationAccessPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsApplicationMeetingConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsApplicationMeetingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsAutoAttendant.md", + "redirect_url": "/powershell/module/teams/Set-CsAutoAttendant", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsCallingLineIdentity.md", + "redirect_url": "/powershell/module/teams/Set-CsCallingLineIdentity", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsCallQueue.md", + "redirect_url": "/powershell/module/teams/Set-CsCallQueue", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsInboundBlockedNumberPattern.md", + "redirect_url": "/powershell/module/teams/Set-CsInboundBlockedNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsInboundExemptNumberPattern.md", + "redirect_url": "/powershell/module/teams/Set-CsInboundExemptNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineApplicationInstance.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineApplicationInstance", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingBridge.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingBridge", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingServiceNumber.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingServiceNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingTenantSettings.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingTenantSettings", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingUser.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingUser", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingUserDefaultNumber.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingUserDefaultNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineEnhancedEmergencyServiceDisclaimer", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineLisCivicAddress.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineLisCivicAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineLisLocation.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineLisLocation", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineLisPort.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineLisPort", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineLisSubnet.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineLisSubnet", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineLisSwitch.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineLisSwitch", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineLisWirelessAccessPoint.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineLisWirelessAccessPoint", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlinePSTNGateway.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlinePSTNGateway", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlinePstnUsage.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlinePstnUsage", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineSchedule.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineSchedule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceApplicationInstance.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceApplicationInstance", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineVoicemailPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineVoicemailPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineVoicemailUserSettings.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineVoicemailUserSettings", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceRoute.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceRoute", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceUser.md", + "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceUser", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsAppPermissionPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsAppPermissionPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsAppSetupPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsAppSetupPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsAudioConferencingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsAudioConferencingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsCallHoldPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsCallHoldPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsCallParkPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsCallParkPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsChannelsPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsChannelsPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsClientConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsClientConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsComplianceRecordingApplication.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsComplianceRecordingApplication", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsComplianceRecordingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsComplianceRecordingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsCortanaPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsCortanaPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsEducationAssignmentsAppPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsEducationAssignmentsAppPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsEmergencyCallingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsEmergencyCallingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsEmergencyCallRoutingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsEmergencyCallRoutingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsFeedbackPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsFeedbackPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsGuestCallingConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsGuestCallingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsGuestMeetingConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsGuestMeetingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsGuestMessagingConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsGuestMessagingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsIPPhonePolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsIPPhonePolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingBrandingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingBrandingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingBroadcastConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingBroadcastConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingBroadcastPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingBroadcastPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsMessagingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsMessagingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsMobilityPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsMobilityPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsNetworkRoamingPolicy.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsNetworkRoamingPolicy", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsPinnedApp.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsPinnedApp", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTeamsTranslationRule.md", + "redirect_url": "/powershell/module/teams/Set-CsTeamsTranslationRule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantBlockedCallingNumbers.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantBlockedCallingNumbers", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantDialPlan.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantDialPlan", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantFederationConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantFederationConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantMigrationConfiguration.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantMigrationConfiguration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantNetworkRegion.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantNetworkRegion", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantNetworkSite.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantNetworkSite", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantNetworkSubnet.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantNetworkSubnet", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantTrustedIPAddress.md", + "redirect_url": "/powershell/module/teams/Set-CsTenantTrustedIPAddress", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsVideoInteropServiceProvider.md", + "redirect_url": "/powershell/module/teams/Set-CsVideoInteropServiceProvider", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Start-CsExMeetingMigration.md", + "redirect_url": "/powershell/module/teams/Start-CsExMeetingMigration", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Sync-CsOnlineApplicationInstance.md", + "redirect_url": "/powershell/module/teams/Sync-CsOnlineApplicationInstance", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Test-CsEffectiveTenantDialPlan.md", + "redirect_url": "/powershell/module/teams/Test-CsEffectiveTenantDialPlan", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Test-CsInboundBlockedNumberPattern.md", + "redirect_url": "/powershell/module/teams/Test-CsInboundBlockedNumberPattern", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Test-CsTeamsTranslationRule.md", + "redirect_url": "/powershell/module/teams/Test-CsTeamsTranslationRule", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Unregister-CsOnlineDialInConferencingServiceNumber.md", + "redirect_url": "/powershell/module/teams/Unregister-CsOnlineDialInConferencingServiceNumber", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Update-CsAutoAttendant.md", + "redirect_url": "/powershell/module/teams/Update-CsAutoAttendant", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Clear-CsOnlineTelephoneNumberReservation.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Disable-CsOnlineDialInConferencingUser.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Enable-CsOnlineDialInConferencingUser.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Export-CsOrganizationalAutoAttendantHolidays.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsHuntGroup.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsHuntGroupTenantInformation.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationEndpoint.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingUserInfo.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingUserState.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineDirectoryTenantNumberCities.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineNumberPortInOrder.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineNumberPortOutOrderPin.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberAvailableCount.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryAreas.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryCities.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryCountries.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryRegions.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryTypes.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberReservationsInformation.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendant.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantHolidays.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantStatus.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantSupportedLanguage.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantSupportedTimeZone.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantTenantInformation.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTeamsUpgradeStatus.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Get-CsTenantPublicProvider.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Grant-CsBroadcastMeetingPolicy.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Import-CsOrganizationalAutoAttendantHolidays.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsHuntGroup.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineApplicationEndpoint.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineAudioFile.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineBulkAssignmentInput.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineNumberPortInOrder.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOnlineSession.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendant.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantCallableEntity.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantCallFlow.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantCallHandlingAssociation.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantDialScope.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantMenu.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantMenuOption.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantPrompt.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsHuntGroup.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineApplicationEndpoint.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOnlineNumberPortInOrder.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Remove-CsOrganizationalAutoAttendant.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Search-CsOnlineTelephoneNumberInventory.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Select-CsOnlineTelephoneNumberInventory.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsHuntGroup.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineApplicationEndpoint.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineDirectoryUser.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineNumberPortInOrder.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineNumberPortOutOrderPin.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceUserBulk.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsOrganizationalAutoAttendant.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Set-CsTenantPublicProvider.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Test-CsOnlineCarrierPortabilityIn.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Test-CsOnlineLisCivicAddress.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Test-CsOnlinePortabilityIn.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false + }, + { + "source_path": "skype/virtual-folder/skype/Update-CsOrganizationalAutoAttendant.md", + "redirect_url": "/powershell/module/teams/", + "redirect_document_id": false } - ] - } + ] } diff --git a/ContentOwners.txt b/ContentOwners.txt new file mode 100644 index 0000000000..95093fb98b --- /dev/null +++ b/ContentOwners.txt @@ -0,0 +1 @@ +* @tiburd @yogkumgit diff --git a/Get-TeamsApp.md b/Get-TeamsApp.md deleted file mode 100644 index a42dad75c1..0000000000 --- a/Get-TeamsApp.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml -Module Name: MicrosoftTeams -online version: -schema: 2.0.0 ---- - -# Get-TeamsApp - -## SYNOPSIS -Returns app information from the Teams tenant app store. - -## SYNTAX - -``` -Get-TeamsApp [-Id ] [-ExternalId ] [-DisplayName ] [-DistributionMethod ] - [] -``` - -## DESCRIPTION -Use any optional parameter to retrieve app information from the Teams tenant app store. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-TeamsApp -Id b9cc7986-dd56-4b57-ab7d-9c4e5288b775 -``` - -### Example 2 -```powershell -PS C:\> Get-TeamsApp -ExternalId b00080be-9b31-4927-9e3e-fa8024a7d98a -DisplayName ] [-DistributionMethod ] -``` - -### Example 3 -```powershell -PS C:\> Get-TeamsApp -DisplayName SampleApp -DistributionMethod organization -``` - -## PARAMETERS - -### -DisplayName -Name of the app visible to users - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionMethod -The type of app in Teams: global or organization. For LOB apps, use "organization" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalId -The external ID of the app, provided by the app developer and used by Azure Active Directory - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Id -The app's ID generated by Teams (different from the external ID) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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 (http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/README.md b/README.md index 22323d9efc..799d11a6c6 100644 --- a/README.md +++ b/README.md @@ -1,77 +1,93 @@ -**Short URL: aka.ms/office-powershell** +--- +ms.date: 05/16/2025 +--- # Overview -This repository holds reference content of Office PowerShell cmdlets for help purpose. The expert knowledge around Office PowerShell is distributed among customers, MVPs, partners, product teams, support, and other community members. Consumers have various preferences when consuming knowledge such as a website, PowerShell Get-Help, Windows app, iOS app, Android app, and others. The following diagram illustrates the point. -![Contribution and Consumption model for Office PowerShell reference content](images/contrib-consumption-model.png) +## Learn how to contribute -## Learn How To Contribute -Anyone who is interested can contribute to the Microsoft Office PowerShell reference topics. -Your contributions will go directly into the Microsoft Office products and show up in Get-Help for the given Office cmdlet. +Anyone who is interested can contribute to the articles. When you contribute, your work goes into the content set after it's been reviewed and merged. It's then published to [Microsoft Learn](https://learn.microsoft.com/), and you're listed as a contributor at: . -> Notice that if you are looking into contributing for the **PnP PowerShell cmdlets**, their documentation is automatically generated from the code, and you should be submitting your change towards the original code at https://github.com/SharePoint/PnP-powershell. See, for example, how the attributes are used in the code for the [Get-PnPList](https://github.com/SharePoint/PnP-PowerShell/blob/master/Commands/Lists/GetList.cs) cmdlet. +If you get stuck and are a Microsoft employee or vendor, post a message to [Ask an Admin](https://aka.ms/askanadmin). -## Quick Start +### Quickly update an article using GitHub.com -### Contribute using the GitHub website +Contributors who make infrequent or small updates can edit the file directly on GitHub.com without installing any software. This article shows you how. [This two-minute video](https://learn-video.azurefd.net/vod/player?id=b5167c5a-9c69-499b-99ac-e5467882bc92) also covers how to contribute. -[![Image of Quick Start video](images/edit_video_capture.jpg)](https://support.office.com/en-us/article/edit-powershell-cmdlet-in-github-dcd20227-3764-48ce-ad6e-763af8b48daf?ui=en-US&rs=en-US&ad=US) +> [!TIP] +> To edit an article, you need to get to it on the GitHub.com backend. If you're already on the GitHub.com page of the article, you're starting at step 4. +> +> Your permissions in the repo determine what you see in step 5 and later. People with no special privileges see the steps as described. People with permissions to approve their own pull requests see a similar experience with different button and page titles (for example, **Commit changes** instead of **Propose changes**), extra options for creating a new branch, and fewer confirmation pages. The point is: click any green buttons that are presented to you until there are no more. -1. Open your browser, log in to GitHub, and navigate to https://github.com/microsoftdocs/office-docs-powershell -2. Browse to the file you want to edit. In this example, we will edit https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/teams/teams-ps/teams/New-Team.md and add a link in the Related Links section. -3. Click the Edit icon which looks like a pencil in the upper right corner. -![Image of Edit button on Github](images/edit_icon.png) +1. Verify that you're signed in to GitHub.com with your GitHub account. +2. On learn.microsoft.com, find the article that you want to update. +3. Above the title of the article, select ![Edit this document icon.](images/m365-cc-sc-edit-icon.png) **Edit this document**. -4. Your browser will open the file in an edit window. To add a link, we scroll down to the Related Links section and add the link in the correct format. -![Image of Edit button on Github](images/add_related_link.png) + ![Screenshot of how to select the Edit this document button on a learn.microsoft.com article.](images/quick-update-edit-button-on-learn-page.png) -**Note** Since you are likely not a maintainer of the Git repository, GitHub will automatically 'Fork' the project into your personal GitHub account. A fork is a copy of the repository in your git account. By forking, you can freely make edits without affecting the original repository. You can always find it again by looking at your GitHub Repositories in your GitHub Profile (drop-down from your name in the top right). -![Image of Automatic Fork message on Github](images/auto_fork.png) +4. The corresponding article file opens on GitHub. Select ![Edit icon.](images/quick-update-github-edit-icon.png) **Edit**. -5. You can click the Preview changes link to see what the changes will look like. + ![Screenshot of how to select the Edit button on a GitHub article file.](images/quick-update-edit-button-on-github-page.png) - **IMPORTANT** The layout of headings and subheadings must follow a schema required for PowerShell Get-Help. - Any deviation will throw errors in the Pull Request. The schema can be found here: https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md +5. If a **You need to fork this repository to propose changes** page opens, select **Fork this repository**. -6. Once you are satisfied with your work, go to the **Propose file change** area at the bottom of the topic. Enter a title and other description information, and then click **Propose file change**. -![Image of Propose file change on Github](images/propose_file_change.png) + ![Screenshot of how to select Fork this repository on the You need to fork this repository to propose changes page.](images/quick-update-fork-this-repository-page.png) -7. On the next screen, click **Create pull request**. +6. The article file opens in a line-numbered editor page where you can make updates. -Looking for more in-depth content? Check out the following: -* [Frequently Asked Questions (FAQ)](repo_docs/FAQ.md) -* [Using more advanced tools with the PowerShell GitHub repo](repo_docs/ADVANCED.md) -* [Creating content for brand new cmdlets](repo_docs/NEW_CMDLETS.md) + Articles on learn.microsoft.com are formatted using the Markdown language. For help on using Markdown, see [Mastering Markdown](https://guides.github.com/features/mastering-markdown/). + + > [!TIP] + > Cmdlet reference articles follow a very strict schema with limited formatting options, because the articles are also converted and used for help at the command line (`Get-Help `). Use existing content as a guide. For more information, see [platyPS Schema](https://github.com/PowerShell/platyPS/blob/master/docs/developer/platyPS/platyPS.schema.md). + + Select **Preview** to view your changes as you go. Select **Edit** to go back to making updates. + + When you're finished making changes, select the green **Commit changes** button. + + ![Screenshot of how to select the green Commit changes button on the article editor page.](images/quick-update-editor-page.png) + +7. In the **Propose changes** dialog that opens, review and/or enter the following values: + - **Commit message**: This value is required. You can accept the default value ("Update \") or you can change it. + - **Extended description**: This value is optional. For example: + - An explanation of the changes. + - @ include the GitHub alias of someone to review and merge your changes. + + When you're finished on the **Propose changes** dialog, select the green **Propose changes** button. + + ![Screenshot of how to select the green Propose changes button in the Propose changes dialog.](images/quick-update-propose-changes-dialog.png) + +8. On the **Comparing changes** page that opens, select the green **Create pull request** button. + + ![Screenshot of how to select the green Create pull request button on the Comparing changes page.](images/quick-update-comparing-changes-page.png) + +9. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button. + + ![Screenshot of how to select the green Create pull request button on the Open a pull request page.](images/quick-update-open-a-pull-request-page.png) + +10. That's it. There's nothing more for you to do. + + The article owner (identified in metadata) is notified about the changes to the article. Eventually, the article owner or another party will review, possibly edit, and approve your changes. After your pull request is merged, the article is updated on learn.microsoft.com. ## Microsoft Open Source Code of Conduct +This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). + +For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any questions or comments. + ### Contributing -This project welcomes contributions and suggestions. Most contributions require you to agree to a -Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us -the rights to use your contribution. For details, visit https://cla.microsoft.com. +This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit . -When you submit a pull request, a CLA-bot will automatically determine whether you need to provide -a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions -provided by the bot. You will only need to do this once across all repos using our CLA. +When you submit a pull request, a CLA-bot automatically determines whether you need to provide a CLA and decorate the PR appropriately (for example, label, comment). Follow the instructions provided by the bot. You only need to do this step once across all repos using our CLA. -This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). -For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or -contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. +### Legal Notices -## Legal Notices +Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the [LICENSE-CODE](LICENSE-CODE) file. -Microsoft and any contributors grant you a license to the Microsoft documentation and other content -in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), -see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the -[LICENSE-CODE](LICENSE-CODE) file. +Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries/regions. -Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation -may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. -The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. -Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653. +The licenses for this project don't grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at . -Privacy information can be found at https://privacy.microsoft.com/en-us/ +Privacy information can be found at -Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, -or trademarks, whether by implication, estoppel or otherwise. +Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise. diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000000..e138ec5d6a --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,41 @@ + + +## Security + +Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). + +If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. + +## Reporting Security Issues + +**Please do not report security vulnerabilities through public GitHub issues.** + +Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). + +If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). + +You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). + +Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: + + * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) + * Full paths of source file(s) related to the manifestation of the issue + * The location of the affected source code (tag/branch/commit or direct URL) + * Any special configuration required to reproduce the issue + * Step-by-step instructions to reproduce the issue + * Proof-of-concept or exploit code (if possible) + * Impact of the issue, including how an attacker might exploit the issue + +This information will help us triage your report more quickly. + +If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. + +## Preferred Languages + +We prefer all communications to be in English. + +## Policy + +Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). + + diff --git a/cabgen-bootstrap.yml b/cabgen-bootstrap.yml new file mode 100644 index 0000000000..51843abfaa --- /dev/null +++ b/cabgen-bootstrap.yml @@ -0,0 +1,14 @@ +trigger: +- live + +pr: none # Disable pull request triggers. + +resources: + repositories: + - repository: templates + type: git + name: Content CI/ReferenceAutomation + ref: refs/heads/master + +extends: + template: PowerShell/cabgen.yml@templates \ No newline at end of file diff --git a/exchange/docfx.json b/exchange/docfx.json index b5ff9b5295..e0a0abf6b0 100644 --- a/exchange/docfx.json +++ b/exchange/docfx.json @@ -3,7 +3,8 @@ "content": [ { "files": [ - "**/*.md" + "**/*.md", + "**/*.yml" ], "src": "docs-conceptual", "version": "exchange-ps", @@ -27,7 +28,10 @@ }, { "files": [ - "**/*.md" + "**/*.yml" + ], + "exclude": [ + "toc.yml" ], "src": "exchange-ps", "version": "exchange-ps", @@ -71,20 +75,24 @@ "overwrite": [], "externalReference": [], "globalMetadata": { + "uhfHeaderId": "MSDocsHeader-M365-IT", "author": "chrisda", "ms.author": "chrisda", "manager": "serdars", "ms.date": "09/25/2017", "ms.topic": "reference", "ms.service": "exchange-powershell", + "products": [ + "https://authoring-docs-microsoft.poolparty.biz/devrel/0b654e73-5728-4af3-8c2e-17bfbf4c9f23", + "https://authoring-docs-microsoft.poolparty.biz/devrel/8bce367e-2e90-4b56-9ed5-5e4e9f3a2dc3" + ], "ms.devlang": "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" + "feedback_system": "Standard", + "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" }, "fileMetadata": { "apiPlatform": { - "exchange-ps/exchange/**/*.md": [ + "exchange-ps/exchange/**/*.yml": [ "powershell" ] } @@ -92,4 +100,4 @@ "template": [], "dest": "exchange-ps" } -} +} \ No newline at end of file diff --git a/exchange/docs-conceptual/app-only-auth-powershell-v2.md b/exchange/docs-conceptual/app-only-auth-powershell-v2.md new file mode 100644 index 0000000000..f23758f7ff --- /dev/null +++ b/exchange/docs-conceptual/app-only-auth-powershell-v2.md @@ -0,0 +1,540 @@ +--- +title: App-only authentication in Exchange Online PowerShell and Security & Compliance PowerShell +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 12/12/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-online +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn how to configure app-only authentication (also known as certificate based authentication or CBA) using the Exchange Online PowerShell V3 module in scripts and other long-running tasks." +--- + +# App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell + +Auditing and reporting scenarios in Microsoft 365 often involve unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell. In the past, unattended sign in required you to store the username and password in a local file or in a secret vault that's accessed at run-time. But, as we all know, storing user credentials locally isn't a good security practice. + +Certificate based authentication (CBA) or app-only authentication as described in this article supports unattended script and automation scenarios by using Microsoft Entra apps and self-signed certificates. + +> [!NOTE] +> +> - Did you know that you can connect to Exchange Online PowerShell using managed identities in Azure? Check out [Use Azure managed identities to connect to Exchange Online PowerShell](connect-exo-powershell-managed-identity.md). +> +> - The features and procedures described in this article require the following versions of the Exchange Online PowerShell module: +> - **Exchange Online PowerShell (Connect-ExchangeOnline)**: Version 2.0.3 or later. +> - **Security & Compliance PowerShell (Connect-IPPSSession)**: Version 3.0.0 or later. +> +> For instructions on how to install or update the module, see [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). For instructions on how to use the module in Azure automation, see [Manage modules in Azure Automation](/azure/automation/shared-resources/modules). +> +> - REST API connections in the Exchange Online PowerShell V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). +> +> If the procedures in this article don't work for you, verify that you don't have Beta versions of the PackageManagement or PowerShellGet modules installed by running the following command: `Get-InstalledModule PackageManagement -AllVersions; Get-InstalledModule PowerShellGet -AllVersions`. +> +> - In Exchange Online PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets: +> - [New-UnifiedGroup](/powershell/module/exchange/new-unifiedgroup) +> - [Remove-UnifiedGroup](/powershell/module/exchange/remove-unifiedgroup) +> - [Remove-UnifiedGroupLinks](/powershell/module/exchange/remove-unifiedgrouplinks) +> - [Add-UnifiedGroupLinks](/powershell/module/exchange/add-unifiedgrouplinks) +> +> You can use Microsoft Graph to replace most of the functionality from those cmdlets. For more information, see [Working with groups in Microsoft Graph](/graph/api/resources/groups-overview). +> +> - In Security & Compliance PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets: +> - [Get-ComplianceSearchAction](/powershell/module/exchange/get-compliancesearchaction) +> - [New-ComplianceSearch](/powershell/module/exchange/new-compliancesearch) +> - [Start-ComplianceSearch](/powershell/module/exchange/start-compliancesearch) +> +> - Delegated scenarios are supported in Exchange Online. The recommended method for connecting with delegation is using GDAP and App Consent. For more information, see [Use the Exchange Online PowerShell v3 Module with GDAP and App Consent](/powershell/partnercenter/exchange-online-gdap-app). You can also use multi-tenant applications when CSP relationships are not created with the customer. The required steps for using multi-tenant applications are called out within the regular instructions in this article. +> +> - Use the _SkipLoadingFormatData_ switch on the **Connect-ExchangeOnline** cmdlet if you get the following error when using the Windows PowerShell SDK to connect: `The term 'Update-ModuleManifest' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.` + +## How does it work? + +The Exchange Online PowerShell module uses the Active Directory Authentication Library to fetch an app-only token using the application ID, tenant ID (organization), and certificate thumbprint. The application object provisioned inside Microsoft Entra ID has a Directory Role assigned to it, which is returned in the access token. The session's role based access control (RBAC) is configured using the directory role information that's available in the token. + +## Connection examples + +The following examples show how to use the Exchange Online PowerShell module with app-only authentication: + +> [!IMPORTANT] +> In the following connection commands, use the primary `.onmicrosoft.com` domain for your organization as the value of the _Organization_ parameter. +> +> The following connection commands have many of the same options available as described in [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md) and [Connect to Security & Compliance PowerShell](connect-to-scc-powershell.md). For example: +> +> - Microsoft 365 GCC High or Microsoft 365 DoD environments require the following additional parameters and values: +> - **Connect-ExchangeOnline in GCC High**: `-ExchangeEnvironmentName O365USGovGCCHigh`. +> - **Connect-IPPSSession in GCC High**: `-ConnectionUri https://ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndpointUri https://login.microsoftonline.us/common`. +> - **Connect-ExchangeOnline in DoD**: `-ExchangeEnvironmentName O365USGovDoD`. +> - **Connect-IPPSSession in DoD**: `-ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndpointUri https://login.microsoftonline.us/common`. +> +> - If a **Connect-IPPSSession** command presents a login prompt, run the command: `$Global:IsWindows = $true` before the **Connect-IPPSSession** command. + +- **Connect using a certificate thumbprint**: + + > [!NOTE] + > The CertificateThumbprint parameter is supported only in Microsoft Windows. + + The certificate needs to be installed on the computer where you're running the command. The certificate should be installed in the user certificate store. + + - Exchange Online PowerShell: + + ```powershell + Connect-ExchangeOnline -CertificateThumbPrint "012THISISADEMOTHUMBPRINT" -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contosoelectronics.onmicrosoft.com" + ``` + + - Security & Compliance PowerShell: + + ```powershell + Connect-IPPSSession -CertificateThumbPrint "012THISISADEMOTHUMBPRINT" -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contosoelectronics.onmicrosoft.com" + ``` + +- **Connect using a certificate object**: + + The certificate doesn't need to be installed on the computer where you're running the command. You can store the certificate object remotely. The certificate is fetched when the script is run. + + - Exchange Online PowerShell: + + ```powershell + Connect-ExchangeOnline -Certificate <%X509Certificate2 Object%> -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contosoelectronics.onmicrosoft.com" + ``` + + - Security & Compliance PowerShell: + + ```powershell + Connect-IPPSSession -Certificate <%X509Certificate2 Object%> -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contosoelectronics.onmicrosoft.com" + ``` + +- **Connect using a local certificate**: + + > [!NOTE] + > Using a **ConvertTo-SecureString** command to store the password of the certificate locally defeats the purpose of a secure connection method for automation scenarios. Using a **Get-Credential** command to prompt you for the password of the certificate securely isn't ideal for automation scenarios. In other words, there's really no automated _and_ secure way to connect using a local certificate. + + - Exchange Online PowerShell: + + ```powershell + Connect-ExchangeOnline -CertificateFilePath "C:\Users\navin\Desktop\automation-cert.pfx" -CertificatePassword (Get-Credential).password -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contosoelectronics.onmicrosoft.com" + ``` + + - Security & Compliance PowerShell: + + ```powershell + Connect-IPPSSession -CertificateFilePath "C:\Users\navin\Desktop\automation-cert.pfx" -CertificatePassword (Get-Credential).password -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contosoelectronics.onmicrosoft.com" + ``` + +## Set up app-only authentication + +An initial onboarding is required for authentication using application objects. Application and service principal are used interchangeably, but an application is like a class object while a service principal is like an instance of the class. For more information, see [Application and service principal objects in Microsoft Entra ID](/entra/identity-platform/app-objects-and-service-principals). + +For a detailed visual flow about creating applications in Microsoft Entra ID, see . + +1. [Register the application in Microsoft Entra ID](#step-1-register-the-application-in-microsoft-entra-id). + +2. [Assign API permissions to the application](#step-2-assign-api-permissions-to-the-application). + + An application object has the **Delegated** API permission **Microsoft Graph** \> **User.Read** by default. For the application object to access resources in Exchange, it needs the **Application** API permission **Office 365 Exchange Online** \> **Exchange.ManageAsApp**. + +3. [Generate a self-signed certificate](#step-3-generate-a-self-signed-certificate) + + - For app-only authentication in Microsoft Entra ID, you typically use a certificate to request access. Anyone who has the certificate and its private key can use the app with the permissions granted to the app. + + - Create and configure a self-signed X.509 certificate, which is used to authenticate your Application against Microsoft Entra ID, while requesting the app-only access token. + + - This procedure is similar to generating a password for user accounts. The certificate can be self-signed as well. See [this section](#step-3-generate-a-self-signed-certificate) later in this article for instructions to generate certificates in PowerShell. + + > [!NOTE] + > Cryptography: Next Generation (CNG) certificates aren't supported for app-only authentication with Exchange. CNG certificates are created by default in modern versions of Windows. You must use a certificate from a CSP key provider. [This section](#step-3-generate-a-self-signed-certificate) section covers two supported methods to create a CSP certificate. + +4. [Attach the certificate to the Microsoft Entra application](#step-4-attach-the-certificate-to-the-microsoft-entra-application) + +5. [Assign Microsoft Entra roles to the application](#step-5-assign-microsoft-entra-roles-to-the-application) + + The application needs to have the appropriate RBAC roles assigned. Because the apps are provisioned in Microsoft Entra ID, you can use any of the supported built-in roles. + +### Step 1: Register the application in Microsoft Entra ID + +> [!NOTE] +> If you encounter problems, check the [required permissions](/entra/identity-platform/howto-create-service-principal-portal#permissions-required-for-registering-an-app) to verify that your account can create the identity. + +1. Open the Microsoft Entra admin center at . + +2. In the **Search** box at the top of the page, start typing **App registrations**, and then select **App registrations** from the results in the **Services** section. + + ![Screenshot that shows App registrations in the Search results on the home page of the Azure portal.](media/exo-app-only-auth-find-app-registrations.png) + + Or, to go directly to the **App registrations** page, use . + +3. On the **App registrations** page, select **New registration**. + + ![Select New registration on the App registrations page.](media/exo-app-only-auth-new-app-registration.png) + + On the **Register an application** page that opens, configure the following settings: + + - **Name**: Enter something descriptive. For example, ExO PowerShell CBA. + + - **Supported account types**: Verify that **Accounts in this organizational directory only (\ only - Single tenant)** is selected. + + > [!NOTE] + > To make the application multi-tenant for **Exchange Online** delegated scenarios, select the value **Accounts in any organizational directory (Any Microsoft Entra directory - Multitenant)**. + + - **Redirect URI (optional)**: This setting is optional. If you need to use it, configure the following settings: + - **Platform**: Select **Web**. + - **URI**: Enter the URI where the access token is sent. + + > [!NOTE] + > You can't create credentials for [native applications](/entra/identity/app-proxy/application-proxy-configure-native-client-application), because you can't use native applications for automated applications. + + ![Register an application.](media/exo-app-only-auth-register-app.png) + + When you're finished on the **App registrations** page, select **Register**. + +4. You're taken to the **Overview** page of the app you just registered. Leave this page open. You'll use it in the next step. + +### Step 2: Assign API permissions to the application + +Choose **one** of the following methods in this section to assign API permissions to the app: + +- Select and assign the API permissions from the portal. +- Modify the app manifest to assign API permissions. (Microsoft 365 GCC High and DoD organizations should use this method) + +#### Select and assign the API permissions from the portal + +1. On the app **Overview** page, select **API permissions** from the **Manage** section. + + ![Select API permissions on the application overview page.](media/exo-app-only-auth-select-manifest.png) + +2. On the app **API Permissions** page, select **Add a permission**. + + ![Select Add a permission on the API permissions page of the application.](media/exo-app-only-auth-api-permissions-add-a-permission.png) + +3. In the **Request API permissions** flyout that opens, select the **APIs my organization uses** tab, start typing **Office 365 Exchange Online** in the **Search** box, and then select it from the results. + + ![Find and select Office 365 Exchange Online on the APIs my organization uses tab.](media/exo-app-only-auth-api-permissions-select-o365-exo.png) + +4. On the **What type of permissions does your application require?** flyout that appears, select **Application permissions**. + +5. In the permissions list that appears, expand **Exchange**, select **Exchange.ManageAsApp**, and then select **Add permissions**. + + ![Find and select Exchange.ManageAsApp permissions from the Application permission tab.](media/exo-app-only-auth-api-permissions-select-exchange-manageasapp.png) + +6. Back on the app **API permissions** page, verify **Office 365 Exchange Online** \> **Exchange.ManageAsApp** is listed and contains the following values: + - **Type**: **Application**. + - **Admin consent required**: **Yes**. + + - **Status**: The current incorrect value is **Not granted for \**. + + Change this value by selecting **Grant admin consent for \**, reading the confirmation dialog that opens, and then selecting **Yes**. + + ![Admin consent required but not granted for Exchange.ManageAsApp permissions.](media/exo-app-only-auth-original-permissions.png) + + The **Status** value is now **Granted for \**. + + ![Admin consent granted for Exchange.ManageAsApp permissions.](media/exo-app-only-auth-admin-consent-granted.png) + +7. For the default **Microsoft Graph** \> **User.Read** entry, select **...** \> **Revoke admin consent**, and then select **Yes** in the confirmation dialog that opens to return **Status** back to the default blank value. + + ![Admin consent removed from default Microsoft Graph User.Read permissions.](media/exo-app-only-auth-admin-consent-removed-from-graph.png) + +8. Close the current **API permissions** page (not the browser tab) to return to the **App registrations** page. You use the **App registrations** page in an upcoming step. + +#### Modify the app manifest to assign API permissions + +> [!NOTE] +> The procedures in this section _append_ the existing default permissions on the app (delegated **User.Read** permissions in **Microsoft Graph**) with the required application **Exchange.ManageAsApp** permissions in **Office 365 Exchange Online**. + +1. On the app **Overview** page, select **Manifest** from the **Manage** section. + + ![Select Manifest on the application overview page.](media/exo-app-only-auth-select-manifest.png) + +2. On the app **Manifest** page, find the `requiredResourceAccess` entry (on or about line 42), and make the entry look like the following code snippet: + + ```json + "requiredResourceAccess": [ + { + "resourceAppId": "00000002-0000-0ff1-ce00-000000000000", + "resourceAccess": [ + { + "id": "dc50a0fb-09a3-484d-be87-e023b12c6440", + "type": "Role" + } + ] + }, + { + "resourceAppId": "00000003-0000-0000-c000-000000000000", + "resourceAccess": [ + { + "id": "e1fe6dd8-ba31-4d61-89e7-88639da4683d", + "type": "Scope" + } + ] + } + ], + ``` + + > [!NOTE] + > Microsoft 365 GCC High or DoD environments have access to Security & Compliance PowerShell only. Use the following values for the `requiredResourceAccess` entry: + > + > ```json + > "requiredResourceAccess": [ + > { + > "resourceAppId": "00000007-0000-0ff1-ce00-000000000000", + > "resourceAccess": [ + > { + > "id": "455e5cd2-84e8-4751-8344-5672145dfa17", + > "type": "Role" + > } + > ] + > }, + > { + > "resourceAppId": "00000003-0000-0000-c000-000000000000", + > "resourceAccess": [ + > { + > "id": "e1fe6dd8-ba31-4d61-89e7-88639da4683d", + > "type": "Scope" + > } + > ] + > } + > ], + > ``` + + When you're finished on the **Manifest** page, select **Save**. + +3. Still on the **Manifest** page, select **API permissions** from the **Manage** section. + + ![Select API permissions from the Manifest page.](media/exo-app-only-auth-manifest-select-api-permissions.png) + +4. On the **API permissions** page, verify **Office 365 Exchange Online** \> **Exchange.ManageAsApp** is listed and contains the following values: + - **Type**: **Application**. + - **Admin consent required**: **Yes**. + + - **Status**: The current incorrect value is **Not granted for \** for the **Office 365 Exchange Online** \> **Exchange.ManageAsApp** entry. + + Change the **Status** value by selecting **Grant admin consent for \**, reading the confirmation dialog that opens, and then selecting **Yes**. + + ![Admin consent required but not granted for Exchange.ManageAsApp permissions.](media/exo-app-only-auth-original-permissions.png) + + The **Status** value is now **Granted for \**. + + ![Admin consent granted for Exchange.ManageAsApp permissions.](media/exo-app-only-auth-admin-consent-granted.png) + +5. For the default **Microsoft Graph** \> **User.Read** entry, select **...** \> **Revoke admin consent**, and then select **Yes** in the confirmation dialog that opens to return **Status** back to the default blank value. + + ![Admin consent removed from default Microsoft Graph User.Read permissions.](media/exo-app-only-auth-admin-consent-removed-from-graph.png) + +6. Close the current **API permissions** page (not the browser tab) to return to the **App registrations** page. You use the **App registrations** page in an upcoming step. + +### Step 3: Generate a self-signed certificate + +Create a self-signed x.509 certificate using one of the following methods: + +- (Recommended) Use the [New-SelfSignedCertificate](/powershell/module/pki/new-selfsignedcertificate), [Export-Certificate](/powershell/module/pki/export-certificate) and [Export-PfxCertificate](/powershell/module/pki/export-pfxcertificate) cmdlets in an elevated (run as administrator) Windows PowerShell session to request a self-signed certificate and export it to `.cer` and `.pfx` (SHA1 by default). For example: + + ```powershell + # Create certificate + $mycert = New-SelfSignedCertificate -DnsName "contoso.org" -CertStoreLocation "cert:\CurrentUser\My" -NotAfter (Get-Date).AddYears(1) -KeySpec KeyExchange + + # Export certificate to .pfx file + $mycert | Export-PfxCertificate -FilePath mycert.pfx -Password (Get-Credential).password + + # Export certificate to .cer file + $mycert | Export-Certificate -FilePath mycert.cer + ``` + +- Use the [Create-SelfSignedCertificate script](https://github.com/SharePoint/PnP-Partner-Pack/blob/master/scripts/Create-SelfSignedCertificate.ps1) script to generate SHA1 certificates. + + ```powershell + .\Create-SelfSignedCertificate.ps1 -CommonName "MyCompanyName" -StartDate 2021-01-06 -EndDate 2022-01-06 + ``` + +### Step 4: Attach the certificate to the Microsoft Entra application + +After you register the certificate with your application, you can use the private key (`.pfx` file) or the thumbprint for authentication. + +1. On the **Owned applications** tab on the **Apps registration** page from the end of [Step 2](#step-2-assign-api-permissions-to-the-application), select your application. + + If you need to get back to **Apps registration** page, use , verify the **Owned applications** tab is selected, and then select your application. + + ![Apps registration page where you select your app.](media/exo-app-only-auth-app-registration-page.png) + +2. On the application page that opens, select **Certificates & secrets** from the **Manage** section. + + ![Select Certificates & Secrets on the application properties page.](media/exo-app-only-auth-select-certificates-and-secrets.png) + +3. On the **Certificates & secrets** page, select **Upload certificate**. + + ![Select Upload certificate on the Certificates & secrets page.](media/exo-app-only-auth-select-upload-certificate.png) + + In the dialog that opens, browse to the self-signed certificate (`.cer` file) that you created in [Step 3](#step-3-generate-a-self-signed-certificate). + + ![Browse to the certificate and then select Add.](media/exo-app-only-auth-upload-certificate-dialog.png) + + When you're finished, select **Add**. + + The certificate is now shown in the **Certificates** section. + + ![Application page showing that the certificate was added.](media/exo-app-only-auth-certificate-successfully-added.png) + +4. Close the current **Certificates & secrets** page, and then the **App registrations** page to return to the main page. You'll use it in the next step. + +### Step 4b: Exchange Online delegated scenarios only: Grant admin consent for the multi-tenant app + +If you made the application multi-tenant for **Exchange Online** delegated scenarios in [Step 1](#step-1-register-the-application-in-microsoft-entra-id), you need to grant admin consent to the Exchange.ManageAsApp permission so the application can run cmdlets in Exchange Online **in each tenant organization**. To do this, generate an admin consent URL for each customer tenant. Before anyone uses the multi-tenant application to connect to Exchange Online in the tenant organization, an admin in the customer tenant should open the following URL: + +`https://login.microsoftonline.com//adminconsent?client_id=&scope=https://outlook.office365.com/.default` + +- `` is the customer's tenant ID. +- `` is the ID of the multi-tenant application. +- The default scope is used to grant application permissions. + +For more information about the URL syntax, see [Request the permissions from a directory admin](/entra/identity-platform/v2-admin-consent#request-the-permissions-from-a-directory-admin). + +### Step 5: Assign Microsoft Entra roles to the application + +You have two options: + +- **Assign Microsoft Entra roles to the application** +- **Assign custom role groups to the application using service principals**: This method is supported only when you connect to Exchange Online PowerShell or Security & Compliance PowerShell in [REST API mode](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module). Security & Compliance PowerShell supports REST API mode in v3.2.0 or later. + +> [!NOTE] +> You can also combine both methods to assign permissions. For example, you can use Microsoft Entra roles for the "Exchange Recipient Administrator" role and also assign your custom RBAC role to extend the permissions. +> +> For multi-tenant applications in **Exchange Online** delegated scenarios, you need to assign permissions in each customer tenant. + +#### Assign Microsoft Entra roles to the application + +The supported Microsoft Entra roles are described in the following table: + +|Role|Exchange Online
PowerShell|Security & Compliance
PowerShell| +|---|:---:|:---:| +|[Compliance Administrator](/entra/identity/role-based-access-control/permissions-reference#compliance-administrator)|✔|✔| +|[Exchange Administrator](/entra/identity/role-based-access-control/permissions-reference#exchange-administrator)¹|✔|| +|[Exchange Recipient Administrator](/entra/identity/role-based-access-control/permissions-reference#exchange-recipient-administrator)|✔|| +|[Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator)¹ ²|✔|✔| +|[Global Reader](/entra/identity/role-based-access-control/permissions-reference#global-reader)|✔|✔| +|[Helpdesk Administrator](/entra/identity/role-based-access-control/permissions-reference#helpdesk-administrator)|✔|| +|[Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator)¹|✔|✔| +|[Security Reader](/entra/identity/role-based-access-control/permissions-reference#security-reader)|✔|✔| + +¹ The Global Administrator and Exchange Administrator roles provide the required permissions for any task in Exchange Online PowerShell. For example: + +- Recipient management. +- Security and protection features. For example, anti-spam, anti-malware, anti-phishing, and the associated reports. + +The Security Administrator role does not have the necessary permissions for those same tasks. + +² Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +For general instructions about assigning roles in Microsoft Entra ID, see [Assign Microsoft Entra roles to users](/entra/identity/role-based-access-control/manage-roles-portal). + +> [!NOTE] +> The following steps are slightly different for Exchange Online PowerShell vs. Security & Compliance PowerShell. The steps for both environments are shown. To configure roles for both environments, repeat the steps in this section. + +1. In Microsoft Entra admin center at , start typing **roles and administrators** in the **Search** box at the top of the page, and then select **Microsoft Entra roles and administrators** from the results in the **Services** section. + + ![Screenshot that shows Microsoft Entra roles and administrators in the Search results on the on the home page of the Azure portal.](media/exo-app-only-auth-find-roles-and-administrators.png) + + Or, to go directly to the **Microsoft Entra roles and administrators** page, use . + +2. On the **Roles and administrators** page that opens, find and select one of the supported roles by _clicking on the name of the role_ (not the check box) in the results. + + - **Exchange Online PowerShell**: For example, find and select the **Exchange administrator** role. + + ![Find and select a supported Exchange Online PowerShell role by clicking on the role name.](media/exo-app-only-auth-find-and-select-supported-role.png) + + - **Security & Compliance PowerShell**: For example, find and select the **Compliance Administrator** role. + + ![Find and select a supported Security & Compliance PowerShell role by clicking on the role name.](media/exo-app-only-auth-find-and-select-supported-role-scc.png) + +3. On the **Assignments** page that opens, select **Add assignments**. + + - **Exchange Online PowerShell**: + + ![Select Add assignments on the role assignments page for Exchange Online PowerShell.](media/exo-app-only-auth-role-assignments-click-add-assignments.png) + + - **Security & Compliance PowerShell**: + + ![Select Add assignments on the role assignments page for Security & Compliance PowerShell.](media/exo-app-only-auth-role-assignments-click-add-assignments-scc.png) + +4. In the **Add assignments** flyout that opens, find and select the app that you created in [Step 1](#step-1-register-the-application-in-microsoft-entra-id). + + ![Find and select your app on the Add assignments flyout.](media/exo-app-only-auth-find-add-select-app-for-assignment.png) + + When you're finished in the **Add assignments** flyout, select **Add**. + +5. Back on the **Assignments** page, verify that the role has been assigned to the app. + + - **Exchange Online PowerShell**: + + ![The role assignments page after to added the app to the role for Exchange Online PowerShell.](media/exo-app-only-auth-app-assigned-to-role.png) + + - **Security & Compliance PowerShell**: + + ![The role assignments page after to added the app to the role for Security & Compliance PowerShell.](media/exo-app-only-auth-app-assigned-to-role-scc.png) + +#### Assign custom role groups to the application using service principals + +> [!NOTE] +> You need to connect to Exchange Online PowerShell or Security & Compliance PowerShell _before_ completing steps to create a new service principal. Creating a new service principal without connecting to PowerShell won't work (your Azure App ID and Object ID are needed to create the new service principal). +> +> This method is supported only when you connect to Exchange Online PowerShell or Security & Compliance PowerShell in [REST API mode](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module). Security & Compliance PowerShell supports REST API mode in v3.2.0 or later. + +For information about creating custom role groups, see [Create role groups in Exchange Online](/exchange/permissions-exo/role-groups#create-role-groups) and [Create Email & collaboration role groups in the Microsoft Defender portal](/defender-office-365/mdo-portal-permissions#create-email--collaboration-role-groups-in-the-microsoft-defender-portal). The custom role group that you assign to the application can contain any combination of built-in and custom roles. + +To assign custom role groups to the application using service principals, do the following steps: + +1. In [Microsoft Graph PowerShell](/powershell/microsoftgraph/installation), run the following commands to store the details of the Microsoft Entra application that you registered in [Step 1](#step-1-register-the-application-in-microsoft-entra-id) in a variable: + + ```powershell + Connect-MgGraph -Scopes AppRoleAssignment.ReadWrite.All,Application.Read.All + + $ = Get-MgServicePrincipal -Filter "DisplayName eq ''" + ``` + + For example: + + ```powershell + Connect-MgGraph -Scopes AppRoleAssignment.ReadWrite.All,Application.Read.All + + $AzureADApp = Get-MgServicePrincipal -Filter "DisplayName eq 'ExO PowerShell CBA'" + ``` + + For detailed syntax and parameter information, see [Get-MgServicePrincipal](/powershell/module/microsoft.graph.applications/get-mgserviceprincipal). + +2. In the same PowerShell window, connect to [Exchange Online PowerShell](connect-to-exchange-online-powershell.md) or [Security & Compliance PowerShell](connect-to-scc-powershell.md) and run the following commands to: + - Create a service principal object for the Microsoft Entra application. + - Store the details of the service principal in a variable to use in the next step. + + ```powershell + New-ServicePrincipal -AppId $.AppId -ObjectId $.Id -DisplayName "" + + $ = Get-ServicePrincipal -Identity "" + ``` + + For example: + + ```powershell + New-ServicePrincipal -AppId $AzureADApp.AppId -ObjectId $AzureADApp.Id -DisplayName "SP for Azure AD App ExO PowerShell CBA" + + $SP = Get-ServicePrincipal -Identity "SP for Azure AD App ExO PowerShell CBA" + ``` + + For detailed syntax and parameter information, see [New-ServicePrincipal](/powershell/module/exchange/new-serviceprincipal). + +3. In Exchange Online PowerShell or Security & Compliance PowerShell, run the following command to add the service principal as a member of the custom role group: + + ```powershell + Add-RoleGroupMember -Identity "" -Member <$.Identity | $.ObjectId | $.Id> + ``` + + For example: + + ```powershell + Add-RoleGroupMember -Identity "Contoso View-Only Recipients" -Member $SP.Identity + ``` + + For detailed syntax and parameter information, see [Add-RoleGroupMember](/powershell/module/exchange/add-rolegroupmember). diff --git a/exchange/docs-conceptual/client-advanced-settings.md b/exchange/docs-conceptual/client-advanced-settings.md new file mode 100644 index 0000000000..dc5a85dd20 --- /dev/null +++ b/exchange/docs-conceptual/client-advanced-settings.md @@ -0,0 +1,436 @@ +--- +title: PowerShell advanced settings for Microsoft Purview Information Protection client +ms.author: yangczhang +author: zhang-yangchen +manager: aashishr +ms.date: 04/17/2024 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: purview +ms.reviewer: +ms.localizationpriority: high +ms.collection: +- tier3 +- purview-compliance +search.appverid: +description: "Security & Compliance PowerShell advanced settings for Microsoft Purview Information Protection client." +--- + +# Advanced settings for Microsoft Purview Information Protection client + +This article contains the [Security & Compliance PowerShell](/powershell/exchange/office-365-scc/office-365-scc-powershell) advanced settings that are supported by [Microsoft Purview Information Protection client](/purview/information-protection-client) when you use the following cmdlets: + +- [New-Label](/powershell/module/exchange/new-label) or [Set-Label](/powershell/module/exchange/set-label) +- [New-LabelPolicy](/powershell/module/exchange/new-labelpolicy) or [Set-LabelPolicy](/powershell/module/exchange/set-labelpolicy) + +The advanced settings that are supported by sensitivity labels built into Microsoft 365 apps and services are included on the cmdlet page itself. You might also find useful [PowerShell tips for specifying the advanced settings](/purview/create-sensitivity-labels#powershell-tips-for-specifying-the-advanced-settings). + +|Advanced settings for labels|Description| +|---|---| +|[Color](#color)|Specify a color for the label| +|[DefaultSubLabelId](#defaultsublabelid)|Specify a default sublabel for a parent label| + +|Advanced settings for label policies|Description| +|---|---| +|[AdditionalPPrefixExtensions](#additionalpprefixextensions)|Support for changing \.PFILE to P\| +|[EnableAudit](#enableaudit)|Prevent audit data from being sent to Microsoft Purview| +|[EnableContainerSupport](#enablecontainersupport)|Enable removal of encryption from PST, rar, 7zip, and MSG files| +|[EnableCustomPermissions](#enablecustompermissions)|Turn off custom permissions in File Explorer| +|[EnableCustomPermissionsForCustomProtectedFiles](#enablecustompermissionsforcustomprotectedfiles)|For files encrypted with custom permissions, always display custom permissions to users in File Explorer| +|[EnableGlobalization](#enableglobalization) |Turn on classification globalization features| +|[JustificationTextForUserText](#justificationtextforusertext) |Customize justification prompt texts for modified labels| +|[LogMatchedContent](#logmatchedcontent)|Send information type matches to Microsoft Purview| +|[OfficeContentExtractionTimeout](#officecontentextractiontimeout)|Configure the auto-labeling timeout for Office files| +|[PFileSupportedExtensions](#pfilesupportedextensions)|Change which file types to protect| +|[ReportAnIssueLink](#reportanissuelink) |Add "Report an Issue" for users| +|[ScannerMaxCPU](#scannermaxcpu) |Limit CPU consumption| +|[ScannerMinCPU](#scannermincpu) |Limit CPU consumption| +|[ScannerConcurrencyLevel](#scannerconcurrencylevel)|Limit the number of threads used by the scanner| +|[ScannerFSAttributesToSkip](#scannerfsattributestoskip) |Skip or ignore files during scans depending on file attributes) +|[SharepointWebRequestTimeout](#sharepointwebrequesttimeout)|Configure SharePoint timeouts| +|[SharepointFileWebRequestTimeout](#sharepointfilewebrequesttimeout )|Configure SharePoint timeouts| +|[UseCopyAndPreserveNTFSOwner](#usecopyandpreserventfsowner) |Preserve NTFS owners during labeling| + +## AdditionalPPrefixExtensions + +This advanced property to change \.PFILE to P\ is supported by File Explorer, PowerShell, and by the scanner. All apps have similar behavior. + +- Key: **AdditionalPPrefixExtensions** + +- Value: **\** + +Use the following table to identify the string value to specify: + +| String value| Client and scanner| +|---|---| +|\*|All PFile extensions become P\| +|\| Default value behaves like the default encryption value.| +|ConvertTo-Json(".dwg", ".zip")|In addition to the previous list, ".dwg" and ".zip" become P\| + +With this setting, the following extensions always become **P\**: ".txt", ".xml", ".bmp", ".jt", ".jpg", ".jpeg", ".jpe", ".jif", ".jfif", ".jfi", ".png", ".tif", ".tiff", ".gif"). Notable exclusion is that "ptxt" does not become "txt.pfile". + +This setting requires the advanced setting *PFileSupportedExtension* to be enabled. + +**Example 1**: PowerShell command to behave like the default behavior where Protect ".dwg" becomes ".dwg.pfile": + +```PowerShell +Set-LabelPolicy -AdvancedSettings @{ AdditionalPPrefixExtensions =""} +``` + +**Example 2**: PowerShell command to change all PFile extensions from generic encryption to native encryption when the files are labeled and encrypted: + +```PowerShell +Set-LabelPolicy -AdvancedSettings @{ AdditionalPPrefixExtensions ="*"} +``` + +**Example 3**: PowerShell command to change ".dwg" to ".pdwg" when using this service protect this file: + +```PowerShell +Set-LabelPolicy -AdvancedSettings @{ AdditionalPPrefixExtensions =ConvertTo-Json(".dwg")} +``` + +## Color + +Use this advanced setting to set a color for a label. To specify the color, enter a hex triplet code for the red, green, and blue (RGB) components of the color. For example, #40e0d0 is the RGB hex value for turquoise. + +If you need a reference for these codes, you'll find a helpful table from the [\](https://developer.mozilla.org/docs/Web/CSS/color_value) page from the MSDN web docs. You also find these codes in many applications that let you edit pictures. For example, Microsoft Paint lets you choose a custom color from a palette and the RGB values are automatically displayed, which you can then copy. + +To configure the advanced setting for a label's color, enter the following strings for the selected label: + +- Key: **color** + +- Value: **\** + +Example PowerShell command, where your label is named "Public": + +```PowerShell +Set-Label -Identity Public -AdvancedSettings @{color="#40e0d0"} +``` + +## DefaultSubLabelId + +When you add a sublabel to a label, users can no longer apply the parent label to a document or email. By default, users select the parent label to see the sublabels that they can apply, and then select one of those sublabels. If you configure this advanced setting, when users select the parent label, a sublabel is automatically selected and applied for them: + +- Key: **DefaultSubLabelId** + +- Value: **\** + +Example PowerShell command, where your parent label is named "Confidential" and the "All Employees" sublabel has a GUID of 8faca7b8-8d20-48a3-8ea2-0f96310a848e: + +```PowerShell +Set-Label -Identity "Confidential" -AdvancedSettings @{DefaultSubLabelId="8faca7b8-8d20-48a3-8ea2-0f96310a848e"} +``` + +## EnableAudit + +By default, the information protection client sends audit data to Microsoft Purview where you can view this data in [activity explorer](/purview/data-classification-activity-explorer). + +To change this behavior, use the following advanced setting: + +- Key: **EnableAudit** + +- Value: **False** + +For example, if your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableAudit="False"} +``` + +Then on local computers that run the information protection client, delete the following folder: **%localappdata%\Microsoft\MSIP\mip** + +To enable the client to send audit log data again, change the advanced setting value to **True**. You do not need to manually create the **%localappdata%\Microsoft\MSIP\mip** folder again on your client computers. + +## EnableContainerSupport + +This setting enables the information protection client to remove encryption from PST, rar, and 7zip files. + +- Key: **EnableContainerSupport** + +- Value: **True** + +For example, if your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableContainerSupport="True"} +``` + +## EnableCustomPermissions + +By default, users see an option named **Protect with custom permissions** when they right-click in File Explorer with the file labeler. This option lets them set their own encryption settings that can override any encryption settings that you might have included with a label configuration. Users can also see an option to remove encryption. When you configure this setting, users do not see these options. + +Use the following setting so users don't see these options: + +- Key: **EnableCustomPermissions** + +- Value: **False** + +Example PowerShell command, where your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableCustomPermissions="False"} +``` + +## EnableCustomPermissionsForCustomProtectedFiles + +When you configure the advanced client setting *EnableCustomPermissions* to turn off custom permissions in File Explorer, by default, users are not able to see or change custom permissions that are already set in an encrypted document. + +However, there's another advanced client setting that you can specify so that in this scenario, users can see and change custom permissions for an encrypted document when they use File Explorer and right-click the file. + +- Key: **EnableCustomPermissionsForCustomProtectedFiles** + +- Value: **True** + +Example PowerShell command, where your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableCustomPermissionsForCustomProtectedFiles="True"} +``` + +## EnableGlobalization + +Classification globalization features including increased accuracy for East Asian languages and support for double-byte characters. These enhancements are provided only for 64-bit processes, and are turned off by default. + +Turn on these features for your policy specify the following strings: + +- Key: **EnableGlobalization** + +- Value: `True` + +Example PowerShell command, where your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableGlobalization="True"} +``` + +To turn off support again and revert to the default, set the **EnableGlobalization** advanced setting to an empty string. + +## JustificationTextForUserText + +Customize the justification prompts that are displayed when end users change sensitivity labels on files. + +For example, as an administrator, you might want to remind your users not to add any customer identifying information into this field. + +To modify the default **Other** option that users can select in the dialog box, use the *JustificationTextForUserText* advanced setting. Set the value to the text you want to use instead. + +Example PowerShell command, where your label policy is named "Global": + +``` PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{JustificationTextForUserText="Other (please explain) - Do not enter sensitive info"} +``` + +## LogMatchedContent + +By default, the information protection client doesn't send content matches for sensitive info types to Microsoft Purview, which can then be displayed in [activity explorer](/purview/data-classification-activity-explorer). The scanner always sends this information. For more information about this additional information that can be sent, see [Content matches for deeper analysis](/azure/information-protection/reports-aip#content-matches-for-deeper-analysis). + +To send content matches when sensitive information types are sent, use the following advanced setting in a label policy: + +- Key: **LogMatchedContent** + +- Value: **True** + +Example PowerShell command, where your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{LogMatchedContent="True"} +``` + +## OfficeContentExtractionTimeout + +By default, the scanner's auto-labeling timeout on Office files is 3 seconds. + +If you have a complex Excel file with many sheets or rows, 3 seconds might not be enough to automatically apply labels. To increase this timeout for the selected label policy, specify the following strings: + +- Key: **OfficeContentExtractionTimeout** + +- Value: Seconds, in the following format: `hh:mm:ss`. + +> [!IMPORTANT] +> We recommend that you don't raise this timeout to higher than 15 seconds. + +Example PowerShell command, where your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{OfficeContentExtractionTimeout="00:00:15"} +``` + +The updated timeout applies to auto-labeling on all Office files. + +## PFileSupportedExtensions + +With this setting, you can change which file types are encrypted but you cannot change the default encryption level from native to generic. For example, for users running the file labeler, you can change the default setting so that only Office files and PDF files are encrypted instead of all file types. But you cannot change these file types to be generically encrypted with a .pfile file name extension. + +- Key: **PFileSupportedExtensions** + +- Value: **\** + +Use the following table to identify the string value to specify: + +| String value|Client|Scanner| +|---|---|---| +|\*|Default value: Apply encryption to all file types|Apply encryption to all file types| +|ConvertTo-Json(".jpg", ".png")|In addition to Office file types and PDF files, apply encryption to the specified file name extensions | In addition to Office file types and PDF files, apply encryption to the specified file name extensions + +**Example 1**: PowerShell command for the scanner to encrypt all file types, where your label policy is named "Scanner": + +```PowerShell +Set-LabelPolicy -Identity Scanner -AdvancedSettings @{PFileSupportedExtensions="*"} +``` + +**Example 2**: PowerShell command for the scanner to encrypt .txt files and .csv files in addition to Office files and PDF files, where your label policy is named "Scanner": + +```PowerShell +Set-LabelPolicy -Identity Scanner -AdvancedSettings @{PFileSupportedExtensions=ConvertTo-Json(".txt", ".csv")} +``` + +## ReportAnIssueLink + +When you specify the following advanced client setting, users see a **Report an Issue** option that they can select from the **Help and Feedback** client dialog box in the file labeler. Specify an HTTP string for the link. For example, a customized web page that you have for users to report issues, or an email address that goes to your help desk. + +To configure this advanced setting, enter the following strings for the selected label policy: + +- Key: **ReportAnIssueLink** + +- Value: **\** + +Example value for a website: `https://support.contoso.com` + +Example value for an email address: `mailto:helpdesk@contoso.com` + +Example PowerShell command, where your label policy is named "Global": + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{ReportAnIssueLink="mailto:helpdesk@contoso.com"} +``` + +## ScannerMaxCPU + +> [!IMPORTANT] +> We recommend limiting CPU consumption by using the advanced settings *ScannerMaxCPU* and *ScannerMinCPU* instead of *ScannerConcurrencyLevel* that's supported for backwards compatibility. +> +> If the older advanced setting is specified,*ScannerMaxCPU* and *ScannerMinCPU* advanced settings are ignored. + +Use this advanced setting in conjunction with *ScannerMinCPU* to limit CPU consumption on the scanner computer. + +- Key: **ScannerMaxCPU** + +- Value: \** + +The value is set to **100** by default, which means there is no limit of maximum CPU consumption. In this case, the scanner process will try to use all available CPU time to maximize your scan rates. + +If you set **ScannerMaxCPU** to less than 100, the scanner will monitor the CPU consumption over the last 30 minutes. If the average CPU crossed the limit you set, it will start to reduce the number of threads allocated for new files. + +The limit on the number of threads will continue as long as CPU consumption is higher than the limit set for **ScannerMaxCPU**. + +## ScannerMinCPU + +> [!IMPORTANT] +> We recommend limiting CPU consumption by using the advanced settings *ScannerMaxCPU* and *ScannerMinCPU* instead of *ScannerConcurrencyLevel* that's supported for backwards compatibility. +> +> If the older advanced setting is specified,*ScannerMaxCPU* and *ScannerMinCPU* advanced settings are ignored. + +Used only if *ScannerMaxCPU* is not equal to 100, and cannot be set to a number that is higher than the **ScannerMaxCPU** value. + +We recommend keeping **ScannerMinCPU** set at least 15 points lower than the value of *ScannerMaxCPU*. + +The value is set to **50** by default, which means that if CPU consumption in the last 30 minutes when lower than this value, the scanner will start adding new threads to scan more files in parallel, until the CPU consumption reaches the level you have set for *ScannerMaxCPU*-15. + +## ScannerConcurrencyLevel + +> [!IMPORTANT] +> We recommend limiting CPU consumption by using the advanced settings *ScannerMaxCPU* and *ScannerMinCPU* instead of *ScannerConcurrencyLevel* that's supported for backwards compatibility. +> +> When this older advanced setting is specified,*ScannerMaxCPU* and *ScannerMinCPU* advanced settings are ignored. + +By default, the scanner uses all available processor resources on the computer running the scanner service. If you need to limit the CPU consumption while this service is scanning, specify the number of concurrent threads that the scanner can run in parallel. The scanner uses a separate thread for each file that it scans, so this throttling configuration also defines the number of files that can be scanned in parallel. + +When you first configure the value for testing, we recommend you specify 2 per core, and then monitor the results. For example, if you run the scanner on a computer that has 4 cores, first set the value to 8. If necessary, increase or decrease that number, according to the resulting performance you require for the scanner computer and your scanning rates. + +- Key: **ScannerConcurrencyLevel** + +- Value: **\** + +Example PowerShell command, where your label policy is named "Scanner": + +```PowerShell +Set-LabelPolicy -Identity Scanner -AdvancedSettings @{ScannerConcurrencyLevel="8"} +``` + +## ScannerFSAttributesToSkip + +By default, the information protection scanner scans all relevant files. However, you might want to define specific files to be skipped, such as for archived files or files that have been moved. + +Enable the scanner to skip specific files based on their file attributes by using the **ScannerFSAttributesToSkip** advanced setting. In the setting value, list the file attributes that will enable the file to be skipped when they are all set to **true**. This list of file attributes uses the AND logic. + +Example PowerShell commands, where your label policy is named "Global". + +**Skip files that are both read-only and archived** + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{ ScannerFSAttributesToSkip =" FILE_ATTRIBUTE_READONLY, FILE_ATTRIBUTE_ARCHIVE"} +``` + +**Skip files that are either read-only or archived** + +To use an OR logic, run the same property multiple times. For example: + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{ ScannerFSAttributesToSkip =" FILE_ATTRIBUTE_READONLY"} +Set-LabelPolicy -Identity Global -AdvancedSettings @{ ScannerFSAttributesToSkip =" FILE_ATTRIBUTE_ARCHIVE"} +``` + +> [!TIP] +> We recommend that you consider enabling the scanner to skip files with the following attributes: +> +> - FILE_ATTRIBUTE_SYSTEM +> - FILE_ATTRIBUTE_HIDDEN +> - FILE_ATTRIBUTE_DEVICE +> - FILE_ATTRIBUTE_OFFLINE +> - FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS +> - FILE_ATTRIBUTE_RECALL_ON_OPEN +> - FILE_ATTRIBUTE_TEMPORARY + +For a list of all file attributes that can be defined in the **ScannerFSAttributesToSkip** advanced setting, see the [Win32 File Attribute Constants](/windows/win32/fileio/file-attribute-constants) + +## SharepointWebRequestTimeout + +By default, the timeout for SharePoint interactions is two minutes, after which the attempted information protection client operation fails. Control this timeout using the *SharepointWebRequestTimeout* and *SharepointFileWebRequestTimeout* advanced settings, using an **hh:mm:ss** syntax to define the timeouts. + +Specify a value to determine the timeout for all information protection client web requests to SharePoint. The default is minutes. + +For example, if your policy is named **Global**, the following sample PowerShell command updates the web request timeout to 5 minutes. + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{SharepointWebRequestTimeout="00:05:00"} +``` + +## SharepointFileWebRequestTimeout + +By default, the timeout for SharePoint interactions is two minutes, after which the attempted information protection client operation fails. Control this timeout using the *SharepointWebRequestTimeout* and *SharepointFileWebRequestTimeout* advanced settings, using an **hh:mm:ss** syntax to define the timeouts. + +Specify the timeout value for SharePoint files via information protection client web requests. The default is 15 minutes. + +For example, if your policy is named **Global**, the following sample PowerShell command updates the file web request timeout to 10 minutes. + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{SharepointFileWebRequestTimeout="00:10:00"} +``` + +## UseCopyAndPreserveNTFSOwner + +> [!NOTE] +> This feature is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. + +By default, the information protection client doesn't preserve the NTFS owner that was defined before applying a sensitivity label. + +To ensure that the NTFS owner value is preserved, set the *UseCopyAndPreserveNTFSOwner* advanced setting to **true** for the selected label policy. + +> [!CAUTION] +> For the scanner: Define this advanced setting only when you can ensure a low-latency, reliable network connection between the scanner and the scanned repository. A network failure during the automatic labeling process can cause the file to be lost. + +Example PowerShell command, where your label policy is named "Global" + +```PowerShell +Set-LabelPolicy -Identity Global -AdvancedSettings @{UseCopyAndPreserveNTFSOwner ="true"} +``` diff --git a/exchange/docs-conceptual/cmdlet-property-sets.md b/exchange/docs-conceptual/cmdlet-property-sets.md new file mode 100644 index 0000000000..bbd2cf89d9 --- /dev/null +++ b/exchange/docs-conceptual/cmdlet-property-sets.md @@ -0,0 +1,125 @@ +--- +title: Property sets in Exchange Online PowerShell module cmdlets +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/1/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Admins can lear about the property sets that are available in the nine exclusive Get-EXO cmdlets in the Exchange Online PowerShell V2 module and V3 module." +--- + +# Property sets in Exchange Online PowerShell module cmdlets + +This article describes the property sets that are available in the nine exclusive **Get-EXO\*** [cmdlets in the Exchange Online PowerShell module](exchange-online-powershell-v2.md#cmdlets-in-the-exchange-online-powershell-module). For more information about property sets, see [Properties and property sets in the Exchange Online PowerShell module](exchange-online-powershell-v2.md#properties-and-property-sets-in-the-exchange-online-powershell-module). + +For more information about filtering with cmdlets in the module, see [Filters in the Exchange Online PowerShell module](filters-v2.md). + + > [!TIP] + > Version 3.0.0 and later (2022) is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module). Version 2.0.5 and earlier (2021) was known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). + +## Get-EXOCasMailbox property sets + +The available property sets for the **Get-EXOCasMailbox** cmdlet and the properties they contain are described in the following table: + +|PropertySet|Properties| +|---|---| +|**Minimum**|ActiveSyncEnabled
DisplayName
ECPEnabled
EmailAddresses
EwsEnabled
ExchangeVersion
Guid
Identity
ImapEnabled
MAPIEnabled
Name
OWAEnabled
OrganizationId
PopEnabled
PrimarySmtpAddress
ServerLegacyDN| +|**ActiveSync**|ActiveSyncAllowedDeviceIDs
ActiveSyncBlockedDeviceIDs
ActiveSyncEnabled
ActiveSyncMailboxPolicy
ActiveSyncMailboxPolicyIsDefaulted
ActiveSyncSuppressReadReceipt
ExternalDirectoryObjectId
Guid
HasActiveSyncDevicePartnership
Identity
Name
OrganizationId| +|**Ews**|EwsAllowMacOutlook
EwsAllowOutlook
EwsEnabled
ExternalDirectoryObjectId
Guid
Identity
Name
OrganizationId| +|**Imap**|ExternalDirectoryObjectId
Guid
Identity
ImapEnableExactRFC822Size
ImapEnabled
ImapForceICalForCalendarRetrievalOption
ImapMessagesRetrievalMimeFormat
ImapSuppressReadReceipt
ImapUseProtocolDefaults
Name
OrganizationId| +|**Mapi**|ExternalDirectoryObjectId
Guid
Identity
MAPIBlockOutlookExternalConnectivity
MAPIBlockOutlookNonCachedMode
MAPIBlockOutlookRpcHttp
MAPIBlockOutlookVersions
MAPIEnabled
MapiHttpEnabled
Name
OrganizationId| +|**Pop**|ExternalDirectoryObjectId
Guid
Identity
Name
OrganizationId
PopEnableExactRFC822Size
PopEnabled
PopMessagesRetrievalMimeFormat
PopSuppressReadReceipt
PopUseProtocolDefaults| +|**ProtocolSettings**|ExternalDirectoryObjectId
ExternalImapSettings
ExternalPopSettings
ExternalSmtpSettings
Guid
Identity
InternalImapSettings
InternalPopSettings
InternalSmtpSettings
Name
OrganizationId| + +**Note**: The following **Get-CasMailbox** parameters aren't available on **Get-EXOCasMailbox**: + +- *ActiveSyncDebugLogging* +- *IgnoreDefaultScope* +- *ReadIsOptimizedForAccessibility* +- *SortBy* + +For more information, see: + +- [Get-EXOCASMailbox](/powershell/module/exchange/get-exocasmailbox) +- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox) + +## Get-EXOMailbox property sets + +The available property sets for the **Get-EXOMailbox** cmdlet and the properties they contain are described in the following table: + +|PropertySet|Properties| +|---|---| +|**Minimum**|Alias
DisplayName
DistinguishedName
EmailAddresses
ExchangeVersion
ExternalDirectoryObjectId
Guid
Id
Name
OrganizationId
PrimarySmtpAddress
RecipientType
RecipientTypeDetails
UserPrincipalName| +|**AddressList**|AddressBookPolicy
AddressListMembership
ExternalDirectoryObjectId
GeneratedOfflineAddressBooks
HiddenFromAddressListsEnabled
OfflineAddressBook| +|**Archive**|ArchiveDatabase
ArchiveDomain
ArchiveGuid
ArchiveName
ArchiveQuota
ArchiveRelease
ArchiveState
ArchiveStatus
ArchiveWarningQuota
AutoExpandingArchiveEnabled
DisabledArchiveDatabase
DisabledArchiveGuid
ExternalDirectoryObjectId
JournalArchiveAddress| +|**Audit**|AuditAdmin
AuditDelegate
AuditEnabled
AuditLogAgeLimit
AuditOwner
DefaultAuditSet
ExternalDirectoryObjectId| +|**Custom**|CustomAttribute1
CustomAttribute2
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute1
ExtensionCustomAttribute2
ExtensionCustomAttribute3
ExtensionCustomAttribute4
ExtensionCustomAttribute5
ExternalDirectoryObjectId| +|**Delivery**|AcceptMessagesOnlyFrom
AcceptMessagesOnlyFromDLMembers
AcceptMessagesOnlyFromSendersOrMembers
DeliverToMailboxAndForward
DowngradeHighPriorityMessagesEnabled
ExternalDirectoryObjectId
ForwardingAddress
ForwardingSmtpAddress
GrantSendOnBehalfTo
MaxBlockedSenders
MaxReceiveSize
MaxSafeSenders
MaxSendSize
MessageCopyForSendOnBehalfEnabled
MessageCopyForSentAsEnabled
MessageRecallProcessingEnabled
MessageTrackingReadStatusEnabled
RecipientLimits
RejectMessagesFrom
RejectMessagesFromDLMembers
RejectMessagesFromSendersOrMembers
RulesQuota| +|**Hold**|ComplianceTagHoldApplied
DelayHoldApplied
ExternalDirectoryObjectId
InPlaceHolds
InactiveMailboxRetireTime
LitigationHoldDate
LitigationHoldDuration
LitigationHoldEnabled
LitigationHoldOwner| +|**Moderation**|BypassModerationFromSendersOrMembers
ExternalDirectoryObjectId
ModeratedBy
ModerationEnabled
SendModerationNotifications| +|**Move**|ExternalDirectoryObjectId
MailboxMoveBatchName
MailboxMoveFlags
MailboxMoveRemoteHostName
MailboxMoveSourceMDB
MailboxMoveStatus
MailboxMoveTargetMDB| +|**Policy**|AddressBookPolicy
DataEncryptionPolicy
EmailAddressPolicyEnabled
ExternalDirectoryObjectId
ManagedFolderMailboxPolicy
PoliciesExcluded
PoliciesIncluded
RemoteAccountPolicy
RetentionPolicy
RetentionUrl
RoleAssignmentPolicy
SharingPolicy
ThrottlingPolicy| +|**PublicFolder**|DefaultPublicFolderMailbox
EffectivePublicFolderMailbox
ExternalDirectoryObjectId
IsExcludedFromServingHierarchy
IsHierarchyReady
IsHierarchySyncEnabled
IsRootPublicFolderMailbox| +|**Quota**|ArchiveQuota
ArchiveWarningQuota
CalendarLoggingQuota
ExternalDirectoryObjectId
IssueWarningQuota
ProhibitSendQuota
ProhibitSendReceiveQuota
RecoverableItemsQuota
RecoverableItemsWarningQuota
RulesQuota
UseDatabaseQuotaDefaults| +|**Resource**|ExternalDirectoryObjectId
IsResource
ResourceCapacity
ResourceCustom
ResourceType
RoomMailboxAccountEnabled| +|**Retention**|EndDateForRetentionHold
ExternalDirectoryObjectId
OrphanSoftDeleteTrackingTime
RetainDeletedItemsFor
RetainDeletedItemsUntilBackup
RetentionComment
RetentionHoldEnabled
RetentionPolicy
RetentionUrl
SingleItemRecoveryEnabled
StartDateForRetentionHold
UseDatabaseRetentionDefaults| +|**SCL**|AntispamBypassEnabled
ExternalDirectoryObjectId
SCLDeleteEnabled
SCLDeleteThreshold
SCLJunkEnabled
SCLJunkThreshold
SCLQuarantineEnabled
SCLQuarantineThreshold
SCLRejectEnabled
SCLRejectThreshold| +|**SoftDelete**|ExternalDirectoryObjectId
IncludeInGarbageCollection
IsInactiveMailbox
IsSoftDeletedByDisable
IsSoftDeletedByRemove
WhenSoftDeleted| +|**StatisticsSeed**|ArchiveDatabaseGuid
DatabaseGuid
ExchangeGuid
ExternalDirectoryObjectId| + +**Note**: The following **Get-Mailbox** parameters aren't available on **Get-EXOMailbox**: + +- *Async* +- *GroupMailbox* +- *Migration* +- *PublicFolder* +- *SortBy* + +For more information, see: + +- [Get-EXOMailbox](/powershell/module/exchange/get-exomailbox) +- [Get-Mailbox](/powershell/module/exchange/get-mailbox) + +## Get-EXOMailboxStatistics property sets + +The available property sets for the **Get-EXOMailboxStatistics** cmdlet and the properties they contain are described in the following table: + +|PropertySet|Properties| +|---|---| +|**Minimum**|DeletedItemCount
DisplayName
ItemCount
MailboxGuid
TotalDeletedItemSize
TotalItemSize| +|**All**|AssociatedItemCount
AttachmentTableAvailableSize
AttachmentTableTotalSize
DatabaseIssueWarningQuota
DatabaseName
DatabaseProhibitSendQuota
DatabaseProhibitSendReceiveQuota
DeletedItemCount
DisconnectDate
DisconnectReason
DisplayName
DumpsterMessagesPerFolderCountReceiveQuota
DumpsterMessagesPerFolderCountWarningQuota
ExternalDirectoryOrganizationId
FastIsEnabled
FolderHierarchyChildrenCountReceiveQuota
FolderHierarchyChildrenCountWarningQuota
FolderHierarchyDepthReceiveQuota
FolderHierarchyDepthWarningQuota
FoldersCountReceiveQuota
FoldersCountWarningQuota
IsAbandonedMoveDestination
IsArchiveMailbox
IsDatabaseCopyActive
IsHighDensityShard
IsMoveDestination
IsQuarantined
ItemCount
LastLoggedOnUserAccount
LastLogoffTime
LastLogonTime
LegacyDN
MailboxGuid
MailboxMessagesPerFolderCountReceiveQuota
MailboxMessagesPerFolderCountWarningQuota
MailboxType
MailboxTypeDetail
MessageTableAvailableSize
MessageTableTotalSize
NamedPropertiesCountQuota
NeedsToMove
OtherTablesAvailableSize
OtherTablesTotalSize
OwnerADGuid
QuarantineClients
QuarantineDescription
QuarantineEnd
QuarantineFileVersion
QuarantineLastCrash
ResourceUsageRollingAvgDatabaseReads
ResourceUsageRollingAvgRop
ResourceUsageRollingClientTypes
ServerName
StorageLimitStatus
SystemMessageCount
SystemMessageSize
SystemMessageSizeShutoffQuota
SystemMessageSizeWarningQuota
TotalDeletedItemSize
TotalItemSize| + +For more information, see: + +- [Get-EXOMailboxStatistics](/powershell/module/exchange/get-exomailboxstatistics) +- [Get-MailboxStatistics](/powershell/module/exchange/get-mailboxstatistics) + +## Get-EXORecipient property sets + +The available property sets for the **Get-EXORecipient** cmdlet and the properties they contain are described in the following table: + +|PropertySet|Properties| +|---|---| +|**Minimum**|ExchangeVersion
ExternalDirectoryObjectID
Name
OrganizationId
RecipientType
RecipientTypeDetails| +|**Archive**|ArchiveDatabase
ArchiveGuid
ArchiveRelease
ArchiveState
ArchiveStatus| +|**Custom**|CustomAttribute1
CustomAttribute2
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute1
ExtensionCustomAttribute2
ExtensionCustomAttribute3
ExtensionCustomAttribute4
ExtensionCustomAttribute5| +|**MailboxMove**|MailboxMoveBatchName
MailboxMoveFlags
MailboxMoveRemoteHostName
MailboxMoveSourceMDB
MailboxMoveStatus
MailboxMoveTargetMDB| +|**Policy**|ActiveSyncMailboxPolicy
ActiveSyncMailboxPolicyIsDefaulted
AddressBookPolicy
EmailAddressPolicyEnabled
ManagedFolderMailboxPolicy
OwaMailboxPolicy
PoliciesExcluded
PoliciesIncluded
RetentionPolicy
SharingPolicy
ShouldUseDefaultRetentionPolicy
UMMailboxPolicy| + +**Note**: The following **Get-Recipient** parameters aren't available on **Get-EXORecipient**: + +- *SortBy* + +For more information, see: + +- [Get-EXORecipient](/powershell/module/exchange/get-exorecipient) +- [Get-Recipient](/powershell/module/exchange/get-recipient) diff --git a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md new file mode 100644 index 0000000000..2f484fd336 --- /dev/null +++ b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md @@ -0,0 +1,595 @@ +--- +title: Use Azure managed identities to connect to Exchange Online PowerShell +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 8/24/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-online +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn about using the Exchange Online PowerShell V3 module and Azure managed identity to connect to Exchange Online PowerShell." +--- + +# Use Azure managed identities to connect to Exchange Online PowerShell + +Using the [Exchange Online PowerShell V3 module](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module), you can connect to Exchange Online PowerShell using a user-assigned or system assigned Azure managed identity. For more information about managed identities, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview). + +Unlike other connection methods using the Exchange Online PowerShell module, you can't run the connection commands in a Windows PowerShell session on your local computer. Instead, you connect in the context of the Azure resource that's associated with the managed identity (for example, an Azure automation account or an Azure Virtual Machine). + +The rest of this article explains how to connect using managed identity, and the requirements for creating and configuring the proper resources with managed identities in Azure. + +> [!NOTE] +> In Exchange Online PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets: +> +> - [New-UnifiedGroup](/powershell/module/exchange/new-unifiedgroup) +> - [Remove-UnifiedGroup](/powershell/module/exchange/remove-unifiedgroup) +> - [Remove-UnifiedGroupLinks](/powershell/module/exchange/remove-unifiedgrouplinks) +> - [Add-UnifiedGroupLinks](/powershell/module/exchange/add-unifiedgrouplinks) +> +> You can use Microsoft Graph to replace most of the functionality from those cmdlets. For more information, see [Working with groups in Microsoft Graph](/graph/api/resources/groups-overview). +> +> REST API connections in the V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + +## Connect to Exchange Online PowerShell using system-assigned managed identity + +After you've [Created and configured a system-assigned managed identity](#create-and-configure-a-system-assigned-managed-identity), use the following syntax to connect to Exchange Online PowerShell: + +```powershell +Connect-ExchangeOnline -ManagedIdentity -Organization .onmicrosoft.com +``` + +For example: + +```powershell +Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com +``` + +The rest of this section explains how to connect using supported Azure resources. For example: + +- A PowerShell runbook on the Azure Automation account with system-assigned managed identity. +- An Azure VM with a system-assigned managed identity. + +After the resource is connected, the Exchange Online PowerShell cmdlets and parameters are available based on the RBAC role you assigned in [Step 5: Assign Microsoft Entra roles to the managed identity](#step-5-assign-microsoft-entra-roles-to-the-managed-identity) + +### Connect to Exchange Online PowerShell using Azure Automation accounts with system-assigned managed identity + +Create a PowerShell runbook on the automation account. For instructions, see [Manage runbooks in Azure Automation](/azure/automation/manage-runbooks). + +The first command in the PowerShell runbook must be the `Connect-ExchangeOnline...` command as described in the beginning of this section. For example: + +```powershell +Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com +``` + +After that, as a test, you can start with as simple, low-impact command in the runbook before moving on to more complex commands or scripts. For example: + +```powershell +Get-AcceptedDomain | Format-Table Name +``` + +After you've successfully created, saved, and published the PowerShell runbook, do the following steps to run it in the future: + +1. On the **Automation accounts** page at , select the Automation account. +2. In the details flyout that opens, start typing "Runbooks" in the ![Search icon.](media/search-icon.png) **Search** box, and then select **Runbooks** from results. +3. On the **Runbooks** flyout that opens, select the runbook. +4. On the details page of the runbook, select **Start**. + +### Connect to Exchange Online PowerShell using Azure VMs with system-assigned managed identity + +In a Windows PowerShell window in the Azure VM, use the command as described in the beginning of this section. For example: + +```powershell +Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com +``` + +## Connect to Exchange Online PowerShell using user-assigned managed identity + +After you've [created and configured a user-assigned managed identity](#create-and-configure-a-user-assigned-managed-identity), use the following syntax to connect to Exchange Online PowerShell: + +```powershell +Connect-ExchangeOnline -ManagedIdentity -Organization .onmicrosoft.com -ManagedIdentityAccountId +``` + +You get the \ value from [Step 3: Store the user-assigned managed identity in a variable](#step-3-store-the-user-assigned-managed-identity-in-a-variable). + +The rest of this section explains how to connect using supported Azure resources. For example: + +- A PowerShell runbook on the Azure Automation account with user-assigned managed identity. +- An Azure VM with a user-assigned managed identity. + +After the resource is connected, the Exchange Online PowerShell cmdlets and parameters are available based on the RBAC role you assigned in [Step 6: Assign Microsoft Entra roles to the managed identity](#step-6-assign-microsoft-entra-roles-to-the-managed-identity). + +### Connect to Exchange Online PowerShell using Azure Automation accounts with user-assigned managed identities + +Create a PowerShell runbook on the automation account. For instructions, see [Manage runbooks in Azure Automation](/azure/automation/manage-runbooks). + +The first command in the PowerShell runbook must be the `Connect-ExchangeOnline...` command as described in the beginning of this section. For example: + +```powershell +Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com -ManagedIdentityAccountId bf6dcc76-4331-4942-8d50-87ea41d6e8a1 +``` + +You get the ManagedIdentityAccount value from [Step 3: Store the user-assigned managed identity in a variable](#step-3-store-the-user-assigned-managed-identity-in-a-variable). + +After that, as a test, you can start with as simple, low-impact command in the runbook before moving on to more complex commands or scripts. For example: + +```powershell +Get-AcceptedDomain | Format-Table Name +``` + +After you've successfully created the PowerShell runbook, do the following steps to run it in the future: + +1. On the **Automation accounts** page at , select the Automation account. +2. In the details flyout that opens, start typing "Runbooks" in the ![Search icon.](media/search-icon.png) **Search** box, and then select **Runbooks** from results. +3. On the **Runbooks** flyout that opens, select the runbook. +4. On the details page of the runbook, select **Start**. + +### Connect to Exchange Online PowerShell using Azure VMs with system-assigned managed identities + +In a Windows PowerShell window in the Azure VM, use the command as described in the beginning of this section. For example: + +```powershell +$MI_ID = (Get-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2").ClientId + +Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com -ManagedIdentityAccountId $MI_ID +``` + +## Create and configure a system-assigned managed identity + +The steps are: + +1. [(Optional) Create a resource with system-assigned managed identity](#step-1-create-a-resource-with-system-assigned-managed-identity) +2. [Store the system-assigned managed identity in a variable](#step-2-store-the-system-assigned-managed-identity-in-a-variable) +3. [Add the Exchange Online PowerShell module to the managed identity](#step-3-add-the-exchange-online-powershell-module-to-the-managed-identity) +4. [Grant the Exchange.ManageAsApp API permission for the managed identity to call Exchange Online](#step-4-grant-the-exchangemanageasapp-api-permission-for-the-managed-identity-to-call-exchange-online) +5. [Assign Microsoft Entra roles to the managed identity](#step-5-assign-microsoft-entra-roles-to-the-managed-identity) + +After you complete the steps, you're ready to [Connect to Exchange Online PowerShell using system-assigned managed identity](#connect-to-exchange-online-powershell-using-system-assigned-managed-identity). + +### Step 1: Create a resource with system-assigned managed identity + +If you're going to use an existing resource that's already configured with system-assigned managed identity, you can skip to the [next step](#step-2-store-the-system-assigned-managed-identity-in-a-variable). The following resource types are supported: + +- Azure Automation accounts +- Azure virtual machines (VMs) + +#### Create Azure Automation accounts with system-assigned managed identities + +Create an Automation account that's configured for system-assigned managed identity by using the instructions at [Quickstart: Create an Automation account using the Azure portal](/azure/automation/quickstarts/create-azure-automation-account-portal). + +- Automation accounts are available on the **Automation accounts** page at . + +- When you create the Automation account, system-assigned managed identity is selected by default on the **[Advanced](/azure/automation/quickstarts/create-azure-automation-account-portal#advanced)** tab of the details of the Automation account. + +- To enable the system-assigned managed identity on an existing Automation account, see [Enable system-assigned managed identity](/azure/automation/quickstarts/enable-managed-identity#enable-system-assigned-managed-identity). + +To create the Automation account with system-assigned managed identity in [Azure PowerShell](/powershell/azure/what-is-azure-powershell), do the following steps: + +1. Connect to [Azure Az PowerShell](/powershell/azure/install-az-ps) by running the following command: + + ```powershell + Connect-AzAccount + ``` + +2. If necessary, create an Azure resource group to use with the Automation account by running the following command: + + ```powershell + New-AzResourceGroup -Name "" -Location "" + ``` + + - \ is the unique name for the new resource group. + - \ is a valid value from the command: `Get-AzLocation | Format-Table Name`. + + For example: + + ```powershell + New-AzResourceGroup -Name "ContosoRG" -Location "West US" + ``` + + For complete instructions, see [Create resource groups](/azure/azure-resource-manager/management/manage-resource-groups-powershell#create-resource-groups). + +3. Use the following syntax to create an Automation account with system-assigned managed identity: + + ```powershell + New-AzAutomationAccount -Name "" -ResourceGroupName "" -Location "" -AssignSystemIdentity + ``` + + - \ is the unique name for the new Automation account. + - \ is the name of the existing resource group that you want to use. Valid values are visible in the output of the command: `Get-AzResourceGroup`. + - \ is a valid value from the command: `Get-AzLocation | Format-Table Name`. + + For example: + + ```powershell + New-AzAutomationAccount -Name "ContosoAzAuto1" -ResourceGroupName "ContosoRG" -Location "West US" -AssignSystemIdentity + ``` + + For detailed syntax and parameter information, see [New-AzAutomationAccount](/powershell/module/az.automation/new-azautomationaccount). + +#### Configure Azure VMs with system-assigned managed identities + +For instructions, see the following articles: + +- [System-assigned managed identity in the Azure portal](/entra/identity/managed-identities-azure-resources/qs-configure-portal-windows-vm#system-assigned-managed-identity) + +- [System-assigned managed identity in PowerShell](/entra/identity/managed-identities-azure-resources/qs-configure-powershell-windows-vm#system-assigned-managed-identity) + +### Step 2: Store the system-assigned managed identity in a variable + +Use the following syntax to store the Id (GUID) value of the managed identity in a variable that you'll use in the upcoming steps in [Azure Az PowerShell](/powershell/azure/install-az-ps). + +```powershell +$MI_ID = (Get-AzADServicePrincipal -DisplayName "").Id +``` + +Where \ is the name of the Azure Automation account or the Azure VM. For example: + +```powershell +$MI_ID = (Get-AzADServicePrincipal -DisplayName "ContosoAzAuto1").Id +``` + +To verify that the variable was captured successfully, run the command `$MI_ID`. The output should be a GUID value (for example, 9f164909-3007-466e-a1fe-28d20b16e2c2). + +For detailed syntax and parameter information, see [Get-AzADServicePrincipal](/powershell/module/az.resources/get-azadserviceprincipal). + +### Step 3: Add the Exchange Online PowerShell module to the managed identity + +#### Add the Exchange Online PowerShell module to Azure Automation accounts with system-assigned managed identities + +> [!TIP] +> If the following procedure in the Azure portal doesn't work for you, try the **New-AzAutomationModule** command in Azure PowerShell that's described after the Azure portal procedure. + +1. On the **Automation accounts** page at , select the Automation account. +2. In the details flyout that opens, start typing "Modules" in the ![Search icon.](media/search-icon.png) **Search** box, and then select **Modules** from results. +3. On the **Modules** flyout that opens, select ![Add module icon.](media/add-icon.png) **Add a module**. +4. On the **Add a module** page that opens, configure the following settings: + - **Upload a module file**: Select **Browse from gallery**. + - **PowerShell module file**: Select **Click here to browse from gallery**: + 1. In the **Browse Gallery** page that opens, start typing "ExchangeOnlineManagement" in the ![Search icon.](media/search-icon.png) **Search** box, press Enter, and then select **ExchangeOnlineManagement** from the results. + 2. On the details page that opens, select **Select** to return to the **Add a module** page. + - **Runtime version**: Select **5.1** or **7.1 (Preview)**. To add both versions, repeat the steps in this section to add and select the other runtime version for the module. + + When you're finished, select **Import**. + + ![Screenshot of adding a module to an Automation account in the Azure portal.](media/mi-add-exo-module.png) + +5. Back on the **Modules** flyout, start typing "ExchangeOnlineManagement" in the ![Search icon.](media/search-icon.png) **Search** box to see the **Status** value. When the module import is complete, the value is **Available**. + +To add the module to the Automation account in Azure PowerShell, use the following syntax: + +```powershell +New-AzAutomationModule -ResourceGroupName "" -AutomationAccountName "" -Name ExchangeOnlineManagement -ContentLinkUri https://www.powershellgallery.com/packages/ExchangeOnlineManagement/ +``` + +- \ is the name of the resource group that's already assigned to the Automation account. +- \ is the name of the Automation account. +- \ is the current version of the ExchangeOnlineManagement module. To see the latest General Availability (GA; non-Preview) version of the module, run the following command in Windows PowerShell: `Find-Module ExchangeOnlineManagement`. To see the latest Preview release, run the following command: `Find-Module ExchangeOnlineManagement -AllowPrerelease`. +- Currently, the PowerShell procedures don't give you a choice for the runtime version (it's 5.1). + +For example: + +```powershell +New-AzAutomationModule -ResourceGroupName "ContosoRG" -AutomationAccountName "ContosoAzAuto1" -Name ExchangeOnlineManagement -ContentLinkUri https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.1.0 +``` + +To verify that the module imported successfully, run the following command: + +```powershell +Get-AzAutomationModule -ResourceGroupName ContosoRG -AutomationAccountName ContosoAzAuto1 -Name ExchangeOnlineManagement +``` + +During the import, the ProvisioningState property will have the value Creating. When the module import is complete, the value will change to Succeeded. + +For detailed syntax and parameter information, see [New-AzAutomationModule](/powershell/module/az.automation/new-azautomationmodule). + +#### Add the Exchange Online PowerShell module to Azure VMs with system-assigned managed identities + +Install the Exchange Online PowerShell module in the Azure VM. For instructions, see [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). + +### Step 4: Grant the Exchange.ManageAsApp API permission for the managed identity to call Exchange Online + +The procedures in this step require the Microsoft Graph PowerShell SDK. For installation instructions, see [Install the Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation). + +1. Run the following command to connect to Microsoft Graph PowerShell with the required permissions: + + ```powershell + Connect-MgGraph -Scopes AppRoleAssignment.ReadWrite.All,Application.Read.All + ``` + + If a **Permissions requested** dialog opens, select **Consent on behalf of your organization**, and then click **Accept**. + +2. Run the following command to verify that the Office 365 Exchange Online resource is available in Microsoft Entra ID: + + ```powershell + Get-MgServicePrincipal -Filter "AppId eq '00000002-0000-0ff1-ce00-000000000000'" + ``` + + If the command returns no results, the next step won't work. See the subsection at the end of this section to fix the issue before you continue. + +3. Run the following commands to grant the Exchange.ManageAsApp API permission for the managed identity to call Exchange Online: + + ```powershell + $AppRoleID = "dc50a0fb-09a3-484d-be87-e023b12c6440" + + $ResourceID = (Get-MgServicePrincipal -Filter "AppId eq '00000002-0000-0ff1-ce00-000000000000'").Id + + New-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $MI_ID -PrincipalId $MI_ID -AppRoleId $AppRoleID -ResourceId $ResourceID + ``` + + - `$MI_ID` is the Id (GUID) value of the managed identity that you stored in a variable in [Step 2](#step-2-store-the-system-assigned-managed-identity-in-a-variable). + - `$AppRoleID` is the Id (GUID) value of the **Exchange.ManageAsApp** API permission that's the same in every organization. + - `$ResourceID` is the Id (GUID) value of the **Office 365 Exchange Online** resource in Microsoft Entra ID. The AppId value is the same in every organization, but the Id value is different in every organization. + +For detailed syntax and parameter information, see the following articles: + +- [Connect-MgGraph](/powershell/module/microsoft.graph.applications/new-mgserviceprincipalapproleassignment) +- [Get-MgServicePrincipal](/powershell/module/microsoft.graph.applications/get-mgserviceprincipal) +- [New-MgServicePrincipalAppRoleAssignment](/powershell/module/microsoft.graph.applications/new-mgserviceprincipalapproleassignment) + +#### What to do if the Office 365 Exchange Online resource is not available in Microsoft Entra ID + +If the following command returns no results: + +```powershell +Get-MgServicePrincipal -Filter "AppId eq '00000002-0000-0ff1-ce00-000000000000'" +``` + +Do the following steps: + +1. Register an application in Microsoft Entra ID as described in [Step 1: Register the application in Microsoft Entra ID](app-only-auth-powershell-v2.md#step-1-register-the-application-in-microsoft-entra-id). +2. Assign the Office 365 Exchange Online \> Exchange.ManageAsApp API permission to the application using the "Modify the app manifest" method as described in [Step 2: Assign API permissions to the application](app-only-auth-powershell-v2.md#step-2-assign-api-permissions-to-the-application). + +After you do these steps, run the **Get-MgServicePrincipal** command again to confirm that the Office 365 Exchange Online resource is available in Microsoft Entra ID. + +For even more information, run the following command to verify that the Exchange.ManageAsApp API permission (`dc50a0fb-09a3-484d-be87-e023b12c6440`) is available in the Office 365 Exchange Online resource: + +```powershell +Get-MgServicePrincipal -Filter "AppId eq '00000002-0000-0ff1-ce00-000000000000'" | Select-Object -ExpandProperty AppRoles | Format-Table Value,Id +``` + +Now that the Office 365 Exchange Online resource is available, return to Step 4.3 in this section. + +### Step 5: Assign Microsoft Entra roles to the managed identity + +The supported Microsoft Entra roles are described in the following list: + +- [Compliance Administrator](/entra/identity/role-based-access-control/permissions-reference#compliance-administrator) +- [Exchange Administrator](/entra/identity/role-based-access-control/permissions-reference#exchange-administrator)¹ +- [Exchange Recipient Administrator](/entra/identity/role-based-access-control/permissions-reference#exchange-recipient-administrator) +- [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator)¹ ² +- [Global Reader](/entra/identity/role-based-access-control/permissions-reference#global-reader) +- [Helpdesk Administrator](/entra/identity/role-based-access-control/permissions-reference#helpdesk-administrator) +- [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator)¹ +- [Security Reader](/entra/identity/role-based-access-control/permissions-reference#security-reader) + +¹ The Global Administrator and Exchange Administrator roles provide the required permissions for any task in Exchange Online PowerShell. For example: + +- Recipient management. +- Security and protection features. For example, anti-spam, anti-malware, anti-phishing, and the associated reports. + +The Security Administrator role does not have the necessary permissions for those same tasks. + +² Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +For general instructions about assigning roles in Microsoft Entra ID, see [Assign Microsoft Entra roles to users](/entra/identity/role-based-access-control/manage-roles-portal). + +1. In Microsoft Entra admin center at , start typing **roles and administrators** in the **Search** box at the top of the page, and then select **Microsoft Entra roles and administrators** from the results in the **Services** section. + + ![Screenshot that shows Microsoft Entra roles and administrators in the Search results on the on the home page of the Azure portal.](media/exo-app-only-auth-find-roles-and-administrators.png) + + Or, to go directly to the **Microsoft Entra roles and administrators** page, use . + +2. On the **Roles and administrators** page, find and select one of the supported roles by _clicking on the name of the role_ (not the check box) in the results. For example, find and select the **Exchange administrator** role. + + ![Find and select a supported Exchange Online PowerShell role by clicking on the role name.](media/exo-app-only-auth-find-and-select-supported-role.png) + +3. On the **Assignments** page that opens, select **Add assignments**. + + ![Select Add assignments on the role assignments page for Exchange Online PowerShell.](media/exo-app-only-auth-role-assignments-click-add-assignments.png) + +4. In the **Add assignments** flyout that opens, find and select the managed identity you created or identified in [Step 1](#step-1-create-a-resource-with-system-assigned-managed-identity). + + When you're finished, select **Add**. + +5. Back on the **Assignments** page, verify that the role has been assigned to the managed identity. + +To assign a role to the managed identity in Microsoft Graph PowerShell, do the following steps: + +1. Run the following command to connect to Microsoft Graph PowerShell with the required permissions: + + ```powershell + Connect-MgGraph -Scopes RoleManagement.ReadWrite.Directory + ``` + + If a **Permissions requested** dialog opens, select **Consent on behalf of your organization**, and then click **Accept**. + +2. Use the following syntax to assign the required Microsoft Entra role to the managed identity: + + ```powershell + $RoleID = (Get-MgRoleManagementDirectoryRoleDefinition -Filter "DisplayName eq ''").Id + + New-MgRoleManagementDirectoryRoleAssignment -PrincipalId $MI_ID -RoleDefinitionId $RoleID -DirectoryScopeId "/" + ``` + + - \ is the name of the Microsoft Entra role as listed earlier in this section. + - `$MI_ID` is the Id (GUID) value of the managed identity that you stored in a variable in [Step 2](#step-2-store-the-system-assigned-managed-identity-in-a-variable). + + For example: + + ```powershell + $RoleID = (Get-MgRoleManagementDirectoryRoleDefinition -Filter "DisplayName eq 'Exchange Administrator'").Id + + New-MgRoleManagementDirectoryRoleAssignment -PrincipalId $MI_ID -RoleDefinitionId $RoleID -DirectoryScopeId "/" + ``` + +For detailed syntax and parameter information, see the following articles: + +- [Connect-MgGraph](/powershell/module/microsoft.graph.applications/new-mgserviceprincipalapproleassignment). +- [New-MgRoleManagementDirectoryRoleAssignment](/powershell/module/microsoft.graph.identity.governance/new-mgrolemanagementdirectoryroleassignment) + +## Create and configure a user-assigned managed identity + +The steps are: + +1. [(Optional) Create a user-assigned managed identity](#step-1-create-a-user-assigned-managed-identity) +2. [(Optional) Create a resource with user-assigned managed identity](#step-2-create-a-resource-with-user-assigned-managed-identity) +3. [Store the user-assigned managed identity in a variable](#step-3-store-the-user-assigned-managed-identity-in-a-variable) +4. [Add the Exchange Online PowerShell module to the managed identity](#step-4-add-the-exchange-online-powershell-module-to-the-managed-identity) +5. [Grant the Exchange.ManageAsApp API permission for the managed identity to call Exchange Online](#step-5-grant-the-exchangemanageasapp-api-permission-for-the-managed-identity-to-call-exchange-online) +6. [Assign Microsoft Entra roles to the managed identity](#step-6-assign-microsoft-entra-roles-to-the-managed-identity) + +After you complete the steps, you're ready to [Connect to Exchange Online PowerShell using user-assigned managed identity](#connect-to-exchange-online-powershell-using-user-assigned-managed-identity). + +### Step 1: Create a user-assigned managed identity + +If you already have an existing user-assigned managed identity that you're going to use, you can skip to the [next step](#step-2-create-a-resource-with-user-assigned-managed-identity) to create a resource with the user-assigned managed identity. + +Otherwise, create the user-assigned managed identity in the Azure portal by using the instructions at [Create a user-assigned managed identity](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity). + +To create the user-assigned managed identity in [Azure PowerShell](/powershell/azure/what-is-azure-powershell), do the following steps: + +1. Connect to [Azure Az PowerShell](/powershell/azure/install-az-ps) by running the following command: + + ```powershell + Connect-AzAccount + ``` + +2. If necessary, create an Azure resource group to use with the user-assigned managed identity by running the following command: + + ```powershell + New-AzResourceGroup -Name "" -Location "" + ``` + + - \ is the unique name for the new resource group. + - \ is a valid value from the command: `Get-AzLocation | Format-Table Name`. + + For example: + + ```powershell + New-AzResourceGroup -Name "ContosoRG2" -Location "West US" + ``` + + For complete instructions, see [Create resource groups](/azure/azure-resource-manager/management/manage-resource-groups-powershell#create-resource-groups). + +3. Use the following syntax to create a user-assigned managed identity: + + ```powershell + New-AzUserAssignedIdentity -Name "" -ResourceGroupName "" -Location "" + ``` + + - \ is the unique name for the user-assigned managed identity. + - \ is the name of the existing resource group that you want to use. Valid values are visible in the output of the command: `Get-AzResourceGroup`. + - \ is a valid value from the command: `Get-AzLocation | Format-Table Name`. + + For example: + + ```powershell + New-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2" -Location "West US" + ``` + + For detailed syntax and parameter information, see [New-AzUserAssignedIdentity](/powershell/module/az.managedserviceidentity/new-azuserassignedidentity). + +### Step 2: Create a resource with user-assigned managed identity + +If you're going to use an existing resource that's already configured with user-assigned managed identity, you can skip to the [next step](#step-3-store-the-user-assigned-managed-identity-in-a-variable). The following resource types are supported: + +- Azure Automation accounts +- Azure Virtual Machines (VMs) + +#### Create Azure Automation accounts with user-assigned managed identities + +Create an Automation account that's configured for user-assigned managed identity by using the instructions at [Quickstart: Create an Automation account using the Azure portal](/azure/automation/quickstarts/create-azure-automation-account-portal). + +- Automation accounts are available on the **Automation accounts** page at . + +- Be sure to change the managed identity selection on the **[Advanced](/azure/automation/quickstarts/create-azure-automation-account-portal#advanced)** tab to **User assigned**. + +- To enable the user-assigned managed identity on an existing Automation account, see [Add user-assigned managed identity](/azure/automation/quickstarts/enable-managed-identity#add-user-assigned-managed-identity). + +To create the Automation account with user-assigned managed identity in [Azure PowerShell](/powershell/azure/what-is-azure-powershell), do the following steps: + +1. Connect to [Azure Az PowerShell](/powershell/azure/install-az-ps) by running the following command: + + ```powershell + Connect-AzAccount + ``` + +2. Use the following syntax to create an Automation account with user-assigned managed identity: + + ```powershell + $UAMI = (Get-AzUserAssignedIdentity -Name "" -ResourceGroupName "").Id + + New-AzAutomationAccount -Name "" -ResourceGroupName "" -Location "" -AssignUserIdentity $UAMI + ``` + + - \ is the name of the user-assigned managed identity that you want to use. + - \ is the name of the resource group that's assigned to the user-assigned managed identity. Valid values are visible in the output of the command: `Get-AzResourceGroup`. + - \ is the unique name for the new Automation account. + - \ is the name of the resource group that you want to use, which could be the same value as \. + - \ is a valid value from the command: `Get-AzLocation | Format-Table Name`. + + For example: + + ```powershell + $UAMI = (Get-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2").Id + + New-AzAutomationAccount -Name "ContosoAzAuto2" -ResourceGroupName "ContosoRG2" -Location "West US" -AssignUserIdentity $UAMI + ``` + + For detailed syntax and parameter information, see [New-AzAutomationAccount](/powershell/module/az.automation/new-azautomationaccount). + +#### Configure Azure VMs with user-assigned managed identities + +For instructions, see the following articles: + +- [User-assigned managed identity in the Azure portal](/entra/identity/managed-identities-azure-resources/qs-configure-portal-windows-vm#user-assigned-managed-identity) +- [User-assigned managed identity in PowerShell](/entra/identity/managed-identities-azure-resources/qs-configure-powershell-windows-vm#user-assigned-managed-identity) + +### Step 3: Store the user-assigned managed identity in a variable + +Use the following syntax in [Azure Az PowerShell](/powershell/azure/install-az-ps) to store the ClientId value of the user-assigned managed identity in variable that you'll use in the upcoming steps: + +```powershell +$MI_ID = (Get-AzUserAssignedIdentity -Name "" -ResourceGroupName "").ClientId +``` + +- \ is the name of the user-assigned managed identity. +- \ is the name of the resource group that's associated with the user-assigned managed identity. + +For example: + +```powershell +$MI_ID = (Get-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2").ClientId +``` + +To verify that the variable was captured successfully, run the command `$MI_ID`. The output should be a GUID value (for example, bf6dcc76-4331-4942-8d50-87ea41d6e8a1). + +For detailed syntax and parameter information, see [Get-AzUserAssignedIdentity](/powershell/module/az.managedserviceidentity/get-azuserassignedidentity). + +### Step 4: Add the Exchange Online PowerShell module to the managed identity + +The steps for user-assigned managed identity are the same as in [System-assigned managed identity Step 3](#step-3-add-the-exchange-online-powershell-module-to-the-managed-identity). + +> [!NOTE] +> Be sure to use the correct values for the resource group name and automation account name! + +### Step 5: Grant the Exchange.ManageAsApp API permission for the managed identity to call Exchange Online + +The steps for user-assigned managed identity are the same as in [System-assigned managed identity Step 4](#step-4-grant-the-exchangemanageasapp-api-permission-for-the-managed-identity-to-call-exchange-online). + +Although the managed identity values were obtained differently for user-assigned vs. system-assigned, we're using the same variable name in the command (`$MI_ID`), so the command works for both types of managed identities. + +### Step 6: Assign Microsoft Entra roles to the managed identity + +The steps for user-assigned managed identity are basically the same as in [System-assigned managed identity Step 5](#step-5-assign-microsoft-entra-roles-to-the-managed-identity). + +In the Azure portal, be sure to select the [user-assigned managed identity](#step-2-create-a-resource-with-user-assigned-managed-identity) as the managed identity to assign the Microsoft Entra role to (not the automation account itself). + +The PowerShell command works for both user-assigned and system-assigned managed identities. Although the managed identity values were obtained differently for user-assigned vs. system-assigned, we're using the same variable name in the command (`$MI_ID`). diff --git a/exchange/docs-conceptual/connect-to-exchange-online-powershell.md b/exchange/docs-conceptual/connect-to-exchange-online-powershell.md new file mode 100644 index 0000000000..75be6dcc6a --- /dev/null +++ b/exchange/docs-conceptual/connect-to-exchange-online-powershell.md @@ -0,0 +1,475 @@ +--- +title: Connect to Exchange Online PowerShell +author: chrisda +manager: deniseb +ms.date: 05/07/2025 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn how to use the Exchange Online PowerShell V3 module to connect to Exchange Online PowerShell with modern authentication and/or multi-factor authentication (MFA)." +--- + +# Connect to Exchange Online PowerShell + +This article contains instructions for how to connect to Exchange Online PowerShell using the Exchange Online PowerShell module with or without multi-factor authentication (MFA). + +The Exchange Online PowerShell module uses modern authentication for connecting to all Exchange-related PowerShell environments in Microsoft 365: Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. For more information about the Exchange Online PowerShell module, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). + +To connect to Exchange Online PowerShell for automation, see [App-only authentication for unattended scripts](app-only-auth-powershell-v2.md) and [Use Azure managed identities to connect to Exchange Online PowerShell](connect-exo-powershell-managed-identity.md). + +To connect to Exchange Online PowerShell from C#, see [Use C# to connect to Exchange Online PowerShell](connect-to-exo-powershell-c-sharp.md). + +## What do you need to know before you begin? + +- The requirements for installing and using the module are described in [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). + + > [!NOTE] + > Remote PowerShell connections are deprecated in Exchange Online PowerShell. 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). + > + > REST API connections in the Exchange Online PowerShell V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + +- After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Permissions in Exchange Online](/exchange/permissions-exo/permissions-exo). + + To find the permissions that are required to run specific Exchange Online cmdlets, see [Find the permissions required to run any Exchange cmdlet](find-exchange-cmdlet-permissions.md). + +> [!TIP] +> Having problems? Ask in the [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542) forum. + +## Step 1: Load the Exchange Online PowerShell module + +> [!NOTE] +> If the module is already installed, you can typically skip this step and run **Connect-ExchangeOnline** without manually loading the module first. + +After you've [installed the module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module), open a PowerShell window and load the module by running the following command: + +```powershell +Import-Module ExchangeOnlineManagement +``` + +## Step 2: Connect and authenticate + +> [!NOTE] +> Connect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, `$`). The workaround is to connect using a different account that doesn't have special characters in the profile path. + +The command that you need to run uses the following syntax: + +```powershell +Connect-ExchangeOnline -UserPrincipalName [-ExchangeEnvironmentName ] [-ShowBanner:$false] [-LoadCmdletHelp] [-DelegatedOrganization ] [-SkipLoadingFormatData] [-DisableWAM] + ``` + +For detailed syntax and parameter information, see [Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline). + +- _\_ is your account in user principal name format (for example, `navin@contoso.onmicrosoft.com`). + +- When you use the _ExchangeEnvironmentName_ parameter, you don't need use the _ConnectionUri_ or _AzureADAuthorizationEndPointUrl_ parameters. Common values for the _ExchangeEnvironmentName_ parameter are described in the following table: + + |Environment|Value| + |---|---| + |Microsoft 365 or Microsoft 365 GCC|n/a\*| + |Microsoft 365 GCC High|`O365USGovGCCHigh`| + |Microsoft 365 DoD|`O365USGovDoD`| + |Office 365 Germany|`O365GermanyCloud`| + |Office 365 operated by 21Vianet|`O365China`| + + \* The required value `O365Default` is also the default value, so you don't need to use the _ExchangeEnvironmentName_ parameter in Microsoft 365 or Microsoft 365 GCC environments. + +- In version 3.7.0 or later, command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ switch so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet. + +- The _DelegatedOrganization_ parameter specifies the customer organization that you want to manage as an authorized Microsoft Partner. For more information, see the [connection examples later in this article](#connect-to-exchange-online-powershell-in-customer-organizations). + +- Depending on the nature of your organization, you might be able to omit the _UserPrincipalName_ parameter in the connection command. Instead, you enter the username and password or select stored credentials after you run the **Connect-ExchangeOnline** command. If it doesn't work, then you need to use the _UserPrincipalName_ parameter. + +- If you aren't using MFA, you should be able to use the _Credential_ parameter instead of the _UserPrincipalName_ parameter. First, run the command `$Credential = Get-Credential`, enter your username and password, and then use the variable name for the _Credential_ parameter (`-Credential $Credential`). If it doesn't work, then you need to use the _UserPrincipalName_ parameter. + +- Use the _SkipLoadingFormatData_ switch to avoid errors when connecting to Exchange Online PowerShell from within a Windows service. + +- Using the module in PowerShell 7 requires version 2.0.4 or later. + +- In version 3.7.2 or later, the _DisableWAM_ switch is available to disable Web Account Manager (WAM) if you get WAM-related connection errors. + +The connection examples in the following sections use modern authentication, and are incapable of using Basic authentication. + +### Connect to Exchange Online PowerShell with an interactive login prompt + +1. The following examples work in Windows PowerShell 5.1 and PowerShell 7 for accounts with or without MFA: + + - **This example connects to Exchange Online PowerShell in a Microsoft 365 or Microsoft 365 GCC organization**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName navin@contoso.onmicrosoft.com + ``` + + - **This example connects to Exchange Online PowerShell in a Microsoft GCC High organization**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName laura@blueyonderairlines.us -ExchangeEnvironmentName O365USGovGCCHigh + ``` + + - **This example connects to Exchange Online PowerShell in a Microsoft 365 DoD organization**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName julia@adatum.mil -ExchangeEnvironmentName O365USGovDoD + ``` + + - **This example connects to Exchange Online PowerShell in an Office 365 Germany organization**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName lukas@fabrikam.de -ExchangeEnvironmentName O365GermanyCloud + ``` + +2. In the sign-in window that opens, enter your password, and then click **Sign in**. + + ![Enter your password in the Sign in to your account window.](media/connect-exo-password-prompt.png) + + > [!NOTE] + > In PowerShell 7, browser-based single sign-on (SSO) is used by default, so the sign-in prompt opens in your default web browser instead of a standalone dialog. + +3. **MFA only**: A verification code is generated and delivered based on the response option that's configured for your account (for example, a text message or the Microsoft Authenticator app on your device). + + In the verification window that opens, enter the verification code, and then click **Verify**. + + ![Enter your verification code in the Sign in to your account window.](media/connect-exo-mfa-verify-prompt.png) + +#### PowerShell 7 exclusive connection methods + +- In PowerShell 7 for **accounts without MFA**, this example prompts for credentials within the PowerShell window: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName navin@contoso.onmicrosoft.com -InlineCredential + ``` + +- In PowerShell 7 for accounts with or without MFA, this example uses another computer to authenticate and complete the connection. Typically, you use this method on computers that don't have web browsers (users are unable to enter their credentials in PowerShell 7): + + 1. Run the following command on the computer where you want to connect: + + ```powershell + Connect-ExchangeOnline -Device + ``` + + The connection command waits at following output: + + > To sign in, use a web browser to open the page and enter the code \ to authenticate. + + Note the \ code value. + + 2. On any other device with a web browser and internet access, open and enter the \ code value from the previous step. + + 3. Enter your credentials on the resulting pages. + + 4. In the confirmation prompt, click **Continue**. The next message should indicate success, and you can close the browser or tab. + + 5. The command from step 1 continues to connect you to Exchange Online PowerShell. + +### Connect to Exchange Online PowerShell without a login prompt (unattended scripts) + +For complete instructions, see [App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell](app-only-auth-powershell-v2.md). + +### Connect to Exchange Online PowerShell in customer organizations + +For more information about partners and customer organizations, see the following topics: + +- [What is the Cloud Solution Provider (CSP) program?](/partner-center/csp-overview). +- [Introduction to granular delegated admin privileges (GDAP)](/partner-center/gdap-introduction) + +This example connects to customer organizations in the following scenarios: + +- Connect to a customer organization using a CSP account. +- Connect to a customer organization using a GDAP. +- Connect to a customer organization as a guest user. + + ```powershell + Connect-ExchangeOnline -UserPrincipalName navin@contoso.onmicrosoft.com -DelegatedOrganization adatum.onmicrosoft.com + ``` + +### Connect to Exchange Online PowerShell using managed identity + +For more information, see [Use Azure managed identities to connect to Exchange Online PowerShell](connect-exo-powershell-managed-identity.md). + +- System-assigned managed identity: + + ```powershell + Connect-ExchangeOnline -ManagedIdentity -Organization "cohovinyard.onmicrosoft.com" + ``` + +- User-assigned assigned managed identity: + + ```powershell + Connect-ExchangeOnline -ManagedIdentity -Organization "constoso.onmicrosoft.com" -ManagedIdentityAccountId + ``` + +## Step 3: Disconnect when you're finished + +Be sure to disconnect the session when you're finished. If you close the PowerShell window without disconnecting the session, you could use up all the sessions available to you, and you need to wait for the sessions to expire. To disconnect the session, run the following command: + +```powershell +Disconnect-ExchangeOnline +``` + +To silently disconnect without a confirmation prompt, run the following command: + +```powershell +Disconnect-ExchangeOnline -Confirm:$false +``` + +> [!NOTE] +> The disconnect command will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, `$`). The workaround is to connect using a different account that doesn't have special characters in the profile path. + +## How do you know you've connected successfully? + +If you don't receive any errors, you've connected successfully. A quick test is to run an Exchange Online PowerShell cmdlet, for example, **Get-AcceptedDomain**, and see the results. + +If you receive errors, check the following requirements: + +- A common problem is an incorrect password. Run the connection steps again and pay close attention to the username and password that you use. + +- The account that you use to connect to must be enabled for PowerShell access. For more information, see [Enable or disable access to Exchange Online PowerShell](disable-access-to-exchange-online-powershell.md). + +- TCP port 80 traffic needs to be open between your local computer and Microsoft 365. It's probably open, but it's something to consider if your organization has a restrictive internet access policy. + +- If your organization uses federated authentication, and your identity provider (IDP) and/or security token service (STS) isn't publicly available, you can't use a federated account to connect to Exchange Online PowerShell. Instead, create and use a non-federated account in Microsoft 365 to connect to Exchange Online PowerShell. + +- REST-based connections to Exchange Online PowerShell require the PowerShellGet module, and by dependency, the PackageManagement module, so you'll receive errors if you try to connect without having them installed. For example, you might see the following error: + + > The term 'Update-ModuleManifest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. + + For more information about the PowerShellGet and PackageManagement module requirements, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + +- After you connect, you might received an error that looks like this: + + > Could not load file or assembly 'System.IdentityModel.Tokens.Jwt,Version=\, Culture=neutral, PublicKeyToken=\'. Could not find or load a specific file. + + This error happens when the Exchange Online PowerShell module conflicts with another module that's imported into the runspace. Try connecting in a new Windows PowerShell window before importing other modules. + +## Appendix: Comparison of old and new connection methods + +This section attempts to compare older connection methods that have been replaced by the Exchange Online PowerShell module. The Basic authentication and OAuth token procedures are included for historical reference only and are no longer supported. + +### Connect without multi-factor authentication + +- **Exchange Online PowerShell module with interactive credential prompt**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName admin@contoso.onmicrosoft.com + ``` + +- **Exchange Online PowerShell module without interactive credential prompt**: + + ```powershell + $secpasswd = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $secpasswd) + + Connect-ExchangeOnline -Credential $o365cred + ``` + +- **Basic authentication**: + + ```powershell + $secpasswd = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $secpasswd) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/ -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +- **New-PSSession with OAuth token**: + + ```powershell + $oauthTokenAsPassword = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $oauthTokenAsPassword) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/?BasicAuthToOAuthConversion=true -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +### Connect with multi-factor authentication + +- **Exchange Online PowerShell module with interactive credential prompt**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName admin@contoso.onmicrosoft.com + ``` + +- **Basic authentication**: Not available. + +- **New-PSSession with OAuth token**: Not available. + +### Connect to a customer organization with a CSP account + +- **Exchange Online PowerShell module**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName admin@contoso.onmicrosoft.com -DelegatedOrganization delegated.onmicrosoft.com + ``` + +- **Basic authentication**: + + ```powershell + $secpasswd = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $secpasswd) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/?DelegatedOrg=delegated.onmicrosoft.com&email=SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}@delegated.onmicrosoft.com -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +- **New-PSSession with OAuth token**: + + ```powershell + $oauthTokenAsPassword = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $oauthTokenAsPassword) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/? DelegatedOrg=delegated.onmicrosoft.com&BasicAuthToOAuthConversion=true&email=SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}@delegated.onmicrosoft.com -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +### Connect to a customer organization using GDAP + +- **Exchange Online PowerShell module**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName admin@contoso.onmicrosoft.com -DelegatedOrganization delegated.onmicrosoft.com + ``` + +- **Basic authentication**: + + ```powershell + $secpasswd = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $secpasswd) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/?DelegatedOrg=delegated.onmicrosoft.com&email=SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}@delegated.onmicrosoft.com -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +- **New-PSSession with OAuth token**: + + ```powershell + $oauthTokenAsPassword = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $oauthTokenAsPassword) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/?DelegatedOrg=delegated.onmicrosoft.com&BasicAuthToOAuthConversion=true&email=SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}@delegated.onmicrosoft.com -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +### Connect to a customer organization as a guest user + +- **Exchange Online PowerShell module**: + + ```powershell + Connect-ExchangeOnline -UserPrincipalName admin@contoso.onmicrosoft.com -DelegatedOrganization delegated.onmicrosoft.com + ``` + +- **Basic authentication**: + + ```powershell + $secpasswd = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $secpasswd) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/?DelegatedOrg=delegated.onmicrosoft.com&email=SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}@delegated.onmicrosoft.com -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +- **New-PSSession with OAuth token**: + + ```powershell + $oauthTokenAsPassword = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $oauthTokenAsPassword) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/?DelegatedOrg=delegated.onmicrosoft.com&BasicAuthToOAuthConversion=true&email=SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}@delegated.onmicrosoft.com -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +### Connect to run unattended scripts + +- **Exchange Online PowerShell module**: + + - **Certificate thumbprint**: + + > [!NOTE] + > The CertificateThumbprint parameter is supported only in Microsoft Windows. + + ```powershell + Connect-ExchangeOnline -CertificateThumbPrint "012THISISADEMOTHUMBPRINT" -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contoso.onmicrosoft.com" + ``` + + - **Certificate object**: + + ```powershell + Connect-ExchangeOnline -Certificate <%X509Certificate2Object%> -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contoso.onmicrosoft.com" + ``` + + - **Certificate file**: + + ```powershell + Connect-ExchangeOnline -CertificateFilePath "C:\Users\navin\Desktop\automation-cert.pfx" -CertificatePassword (ConvertTo-SecureString -String "" -AsPlainText -Force) -AppID "36ee4c6c-0812-40a2-b820-b22ebd02bce3" -Organization "contoso.onmicrosoft.com" + ``` + + For more information, see [App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell](app-only-auth-powershell-v2.md). + +- **Basic authentication**: + + ```powershell + $secpasswd = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $secpasswd) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/ -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +- **New-PSSession with OAuth token**: + + ```powershell + $oauthTokenAsPassword = ConvertTo-SecureString '' -AsPlainText -Force + + $o365cred = New-Object System.Management.Automation.PSCredential ("admin@contoso.onmicrosoft.com", $oauthTokenAsPassword) + + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-LiveID/?BasicAuthToOAuthConversion=true&email=SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}@contoso.onmicrosoft.com -Credential $o365cred -Authentication Basic -AllowRedirection + + Import-PSSession $Session + ``` + +### Connect using managed identity + +- **Exchange Online PowerShell module**: + + - **System-assigned managed identity**: + + ```powershell + Connect-ExchangeOnline -ManagedIdentity -Organization "contoso.onmicrosoft.com" + ``` + + - **User-assigned managed identity**: + + ```powershell + Connect-ExchangeOnline -ManagedIdentity -Organization "contoso.onmicrosoft.com" -ManagedIdentityAccountId + ``` + + For more information, see [Use Azure managed identities to connect to Exchange Online PowerShell](connect-exo-powershell-managed-identity.md). + +- **Basic authentication**: Not available. + +- **New-PSSession with OAuth token**: Not available. diff --git a/exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md b/exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md new file mode 100644 index 0000000000..7e28d7e8a7 --- /dev/null +++ b/exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md @@ -0,0 +1,111 @@ +--- +title: Connect to Exchange Online Protection PowerShell +author: chrisda +manager: deniseb +ms.date: 8/21/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn how to use the Exchange Online PowerShell V3 module to connect to standalone Exchange Online Protection PowerShell with modern authentication and/or multi-factor authentication (MFA)." +--- + +# Connect to Exchange Online Protection PowerShell + +This article contains instructions for how to connect to Exchange Online Protection PowerShell using the Exchange Online PowerShell module with or without using multi-factor authentication (MFA). + +The Exchange Online PowerShell module uses modern authentication for connecting to all Exchange-related PowerShell environments in Microsoft 365: Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. For more information about the module, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). + +For more information about Exchange Online Protection PowerShell, see [Exchange Online Protection PowerShell](exchange-online-protection-powershell.md). + +> [!NOTE] +> As of June 2020, the instructions for connecting to standalone Exchange Online Protection PowerShell and Exchange Online PowerShell are basically the same. If you use the **Connect-IPPSSession** cmdlet with the _ConnectionUri_ parameter value `https://ps.protection.outlook.com/powershell-liveid/`, you're redirected to the same `https://outlook.office365.com/powershell-liveid/` endpoint that's used by **Connect-ExchangeOnline** for Exchange Online PowerShell connections. +> +> Remote PowerShell connections in 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). +> +> REST API connections in the Exchange Online PowerShell V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + +## What do you need to know before you begin? + +- The requirements for installing and using the module are described in [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). + +- After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Permissions in standalone EOP](/exchange/standalone-eop/manage-admin-role-group-permissions-in-eop). + +> [!TIP] +> Having problems? Ask for help in the [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351) forum. + +## Connect to Exchange Online Protection PowerShell using modern authentication with or without MFA + +These connection instructions use modern authentication and work with or without multi-factor authentication (MFA). + +## Step 1: Load the Exchange Online PowerShell module + +> [!NOTE] +> If the module is already installed, you can typically skip this step and run **Connect-ExchangeOnline** without manually loading the module first. + +After you've [installed the module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module), open a PowerShell window and load the module by running the following command: + +```powershell +Import-Module ExchangeOnlineManagement +``` + +## Step 2: Connect and authenticate + +> [!NOTE] +> Connect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, `$`). The workaround is to connect using a different account that doesn't have special characters in the profile path. + +The command that you need to run uses the following syntax: + +```powershell +Connect-ExchangeOnline -UserPrincipalName [-ShowBanner:$false] +``` + +For detailed syntax and parameter information, see [Connect-IPPSSession](/powershell/module/exchange/connect-ippssession). + +- _\_ is your account in user principal name format (for example, `navin@contoso.onmicrosoft.com`). + +- With the EXO V3 module (v3.0.0 or later) and the [demise of Basic authentication (remote PowerShell) connections to Exchange Online](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432), you're using REST API cmdlets only. For more information, see [REST API connections in the EXO V3 module](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module). + +### Connect to Exchange Online Protection PowerShell with an interactive login prompt + +This example works in Windows PowerShell 5.1 and PowerShell 7 for accounts with or without MFA: + +```powershell +Connect-ExchangeOnline -UserPrincipalName navin@contoso.onmicrosoft.com +``` + +## Step 3: Disconnect when you're finished + +Be sure to disconnect the session when you're finished. If you close the PowerShell window without disconnecting the session, you could use up all the sessions available to you, and you need to wait for the sessions to expire. To disconnect the session, run the following command: + +```powershell +Disconnect-ExchangeOnline +``` + +To silently disconnect without a confirmation prompt, run the following command: + +```powershell +Disconnect-ExchangeOnline -Confirm:$false +``` + +## How do you know you've connected successfully? + +The Exchange Online Protection Protection cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you've connected successfully. A quick test is to run an Exchange Online Protection cmdlet, for example, **Get-AcceptedDomain**, and see the results. + +If you receive errors, check the following requirements: + +- A common problem is an incorrect password. Run the connection steps again and pay close attention to the username and password that you use. + +- TCP port 80 traffic needs to be open between your local computer and Microsoft 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy. + +- You might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this: + + > The request for the Windows Remote Shell with ShellId \ failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation. + + To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Exchange Online Protection PowerShell endpoint. diff --git a/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md b/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md new file mode 100644 index 0000000000..a43bdfc46f --- /dev/null +++ b/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md @@ -0,0 +1,112 @@ +--- +title: "Connect to Exchange servers using remote PowerShell" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/7/2023 +ms.audience: ITPro +audience: ITPro +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: 0b5987c3-8836-456d-99f7-abc2ffb57300 +description: "Use Windows PowerShell on a local computer to connect to an Exchange Server." +--- + +# Connect to Exchange servers using remote PowerShell + +If you don't have the Exchange management tools installed on your local computer, you can use Windows PowerShell to create a remote PowerShell session to an Exchange server. It's a simple three-step process, where you enter your credentials, provide the required connection settings, and then import the Exchange cmdlets into your local Windows PowerShell session. + +> [!NOTE] +> +> - We recommend that you use the Exchange Management Shell on any computer that you use to extensively administer Exchange servers. You get the Exchange Management Shell by installing the Exchange management tools. For more information, see [Install the Exchange Server Management Tools](/Exchange/plan-and-deploy/post-installation-tasks/install-management-tools) and [Open the Exchange Management Shell](open-the-exchange-management-shell.md). For more information about the Exchange Management Shell, see [Exchange Server PowerShell (Exchange Management Shell)](exchange-management-shell.md). +> +> - The **Get-ExchangeCertificate** cmdlet does not fully support remote PowerShell. We recommend that you use the Exchange Management Shell instead to see all properties of certificate objects. + +## What do you need to know before you begin? + +- Estimated time to complete: less than 5 minutes + +- After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Exchange Server permissions](/exchange/permissions/permissions). + +- You can use the following versions of Windows: + - Windows 11 + - Windows 10 + - Windows 8.1 + - Windows Server 2019 + - Windows Server 2016 + - Windows Server 2012 or Windows Server 2012 R2 + - Windows 7 Service Pack 1 (SP1)* + - Windows Server 2008 R2 SP1* + + \* This version of Windows has reached end of support, and is now supported only in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Install the .NET Framework](/dotnet/framework/install/on-windows-7), [Windows Management Framework 3.0](https://aka.ms/wmf3download), [Windows Management Framework 4.0](https://aka.ms/wmf4download), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). + +- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You get the following error when you try to connect: + + > Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files. + + To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**): + + ```powershell + Set-ExecutionPolicy RemoteSigned + ``` + + For more information about execution policies, see [About Execution Policies](/powershell/module/microsoft.powershell.core/about/about_execution_policies). + +> [!TIP] +> Having problems? Ask for help in the [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612) forum. + +## Connect to a remote Exchange server + +1. On your local computer, open Windows PowerShell, and run the following command: + + ```powershell + $UserCredential = Get-Credential + ``` + + In the **Windows PowerShell Credential Request** dialog box that opens, enter your user principal name (UPN) (for example, `chris@contoso.com`) and password, and then select **OK**. + +2. Replace `` with the fully qualified domain name of your Exchange server (for example, `mailbox01.contoso.com`) and run the following command: + + ```powershell + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http:///PowerShell/ -Authentication Kerberos -Credential $UserCredential + ``` + + **Note**: The _ConnectionUri_ value is `http`, not `https`. + +3. Run the following command: + + ```powershell + Import-PSSession $Session -DisableNameChecking + ``` + +> [!NOTE] +> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command: + +```powershell +Remove-PSSession $Session +``` + +## How do you know that you've successfully connected? + +After Step 3, the Exchange cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange cmdlet (for example, **Get-Mailbox**) and review the results. + +If you receive errors, check the following requirements: + +- A common problem is an incorrect password. Run the three steps again, and pay close attention to the user name and password you enter in Step 1. + +- The account you use to connect to the Exchange server needs to be enabled for remote PowerShell access. For more information, see [Control remote PowerShell access to Exchange servers](control-remote-powershell-access-to-exchange-servers.md). + +- TCP port 80 traffic needs to be open between your local computer and the Exchange server. It's probably open, but it's something to consider if your organization has a restrictive network access policy. + +## See also + +The cmdlets that you use in this article are Windows PowerShell cmdlets. For more information about these cmdlets, see the following articles. + +- [Get-Credential](/powershell/module/microsoft.powershell.security/get-credential) +- [New-PSSession](/powershell/module/microsoft.powershell.core/new-pssession) +- [Import-PSSession](/powershell/module/microsoft.powershell.utility/import-pssession) +- [Remove-PSSession](/powershell/module/microsoft.powershell.core/remove-pssession) +- [Set-ExecutionPolicy](/powershell/module/microsoft.powershell.security/set-executionpolicy) diff --git a/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md b/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md new file mode 100644 index 0000000000..f34a86b8d1 --- /dev/null +++ b/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md @@ -0,0 +1,347 @@ +--- +title: Use C# to connect to Exchange Online PowerShell +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 8/21/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-online +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn about using the Exchange Online PowerShell V3 module and C# to connect to Exchange Online." +--- + +# Use C# to connect to Exchange Online PowerShell + +The code samples in this article use the [Exchange Online PowerShell V3 module](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module) module to connect to Exchange Online from C#. + +To install the Exchange Online PowerShell module, see [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). + +> [!TIP] +> REST API connections in the Exchange Online PowerShell V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). +> +> If you get errors when you try to connect, use the _SkipLoadingFormatData_ switch on the **Connect-ExchangeOnline** cmdlet. + +## Sample 1: Create a single connection using a PowerShell runspace + +```csharp +using System.Collections.ObjectModel; + +using System.Management.Automation; + +using System.Management.Automation.Runspaces; + +using System.Security; + +void SingleConnectionToExchangeOnline() + +{ + + // Setup the Initial Session State of each runspace in the pool + + // Import the ExchangeOnlineManagement module. + + // Set the Execution Policy of the runspace. + + InitialSessionState iss = InitialSessionState.CreateDefault(); + + iss.ImportPSModule(new string[] { "ExchangeOnlineManagement" }); + + iss.ExecutionPolicy = Microsoft.PowerShell.ExecutionPolicy.RemoteSigned; + + iss.ThrowOnRunspaceOpenError = true; + + Runspace runspace = RunspaceFactory.CreateRunspace(iss); + + runspace.Open(); + + // Run the Connect-ExchangeOnline command in the runspace to create a connection with EXO. + + PowerShell ps = PowerShell.Create(runspace); + + ps.AddCommand("Connect-ExchangeOnline"); + + ps.AddParameters(new Dictionary + + { + + ["Organization"] = "contoso.onmicrosoft.com", + + ["CertificateFilePath"] = "C:\\Users\\Certificates\\mycert.pfx", + + ["CertificatePassword"] = GetPassword(), + + ["AppID"] = "a37927a4-1a1a-4162-aa29-e346d5324590" + + }); + + // Execute the script synchronously. + + Collection connectionResult = ps.Invoke(); + + // Clear the connection commands before running cmdlets. + + ps.Commands.Clear(); + + // Create a new command to execute an Exchange Online cmdlet. + + ps.AddCommand("Get-Mailbox"); + + ps.AddParameter("Identity", "ContosoUser1"); + + Collection results = ps.Invoke(); + + // Check if there were any errors. + + if (!ps.HadErrors) + + { + + // Write the results to console. + + foreach (PSObject result in results) + + { + + Console.WriteLine(result.ToString()); + + } + + } + + else + + { + + // Write the errors to console by accessing the error stream of the Powershell object. + + foreach (ErrorRecord error in ps.Streams.Error) + + { + + Console.WriteLine(error.ToString()); + + } + + } + +} + +SecureString GetPassword() + +{ + + // Return the Password as a SecureString + +} +``` + +## Sample 2: Create a multiple connections using PowerShell runspace pools + +Use this code sample to run multiple Exchange Online PowerShell cmdlets in parallel. + +```csharp +PowerShell CreateConnectionCommand(RunspacePool pool) + +{ + + PowerShell ps = PowerShell.Create(); + + ps.RunspacePool = pool; + + ps.AddCommand("Connect-ExchangeOnline"); + + ps.AddParameters(new Dictionary + + { + + ["Organization"] = "contoso.onmicrosoft.com", + + ["CertificateFilePath"] = "C:\\Users\\Certificates\\mycert.pfx", + + ["CertificatePassword"] = GetPassword(), + + ["AppID"] = "a37927a4-1a1a-4162-aa29-e346d5324590" + + }); + + return ps; + +} + +void ParallelConnectionsToExchangeOnline() + +{ + + // Setup the Initial Session State of each runspace in the pool + + // Import the ExchangeOnlineManagement module. + + // Set the Execution Policy of the runspace. + + InitialSessionState iss = InitialSessionState.CreateDefault(); + + iss.ImportPSModule(new string[] { "ExchangeOnlineManagement" }); + + iss.ExecutionPolicy = Microsoft.PowerShell.ExecutionPolicy.RemoteSigned; + + iss.ThrowOnRunspaceOpenError = true; + + // Create a RunspacePool initialized with the Initial Session State. + + using (RunspacePool pool = RunspaceFactory.CreateRunspacePool(iss)) + + { + + // Configure the number of runspaces to maintain in the RunspacePool. + + pool.SetMaxRunspaces(3); + + pool.SetMinRunspaces(3); + + // Set the ThreadOptions to reuse the same threads for the runspaces so that + + // the Exchange Online cmdlets will be available after running Connect-ExchangeOnline in each runspace. + + pool.ThreadOptions = PSThreadOptions.ReuseThread; + + pool.Open(); + + // Run the Connect-ExchangeOnline cmdlet in all the runspaces in the pool + + // so that any cmdlets can be run in them after that. + + PowerShell ps1 = CreateConnectionCommand(pool); + + PowerShell ps2 = CreateConnectionCommand(pool); + + PowerShell ps3 = CreateConnectionCommand(pool); + + // Execute each of the 3 Connect-ExchangeOnline commands asynchronously. + + IAsyncResult job1 = ps1.BeginInvoke(); + + IAsyncResult job2 = ps2.BeginInvoke(); + + IAsyncResult job3 = ps3.BeginInvoke(); + + // Get the results of the commands. + + PSDataCollection connectionResult = ps1.EndInvoke(job1); + + PSDataCollection connectionResult2 = ps2.EndInvoke(job2); + + PSDataCollection connectionResult3 = ps3.EndInvoke(job3); + + // Execute two Exchange-Online commands in parallel using the runspacepool. + + // All of them have an active connection to Exchange Online. + + // NOTE : Cmdlets that update the same object or can cause conflicting + // results should not be run in parallel as they can lead to an undefined + // outcome. + + PowerShell commandPS1 = PowerShell.Create(); + + commandPS1.RunspacePool = pool; + + commandPS1.AddCommand("Get-Mailbox"); + + commandPS1.AddParameter("Identity", "ContosoUser1"); + + PowerShell commandPS2 = PowerShell.Create(); + + commandPS2.RunspacePool = pool; + + commandPS2.AddCommand("Get-Mailbox"); + + commandPS2.AddParameter("Identity", "ContosoUser2"); + + IAsyncResult commandJob1 = commandPS1.BeginInvoke(); + + IAsyncResult commandJob2 = commandPS2.BeginInvoke(); + + // Wait for the commands to finish and return the results. + + PSDataCollection command1Result = commandPS1.EndInvoke(commandJob1); + + PSDataCollection command2Result = commandPS2.EndInvoke(commandJob2); + + // Check if there were any errors. + + if (!commandPS1.HadErrors) + + { + + // Write the results to console. + + foreach (PSObject result in command1Result) + + { + + Console.WriteLine(result.ToString()); + + } + + } + + else + + { + + // Write the errors to console by accessing the error stream of the Powershell object. + + foreach (ErrorRecord error in commandPS1.Streams.Error) + + { + + Console.WriteLine(error.ToString()); + + } + + } + + // Check if there were any errors. + + if (!commandPS2.HadErrors) + + { + + // Write the results to console. + + foreach (PSObject result in command2Result) + + { + + Console.WriteLine(result.ToString()); + + } + + } + + else + + { + + // Write the errors to console by accessing the error stream of the Powershell object. + + foreach (ErrorRecord error in commandPS2.Streams.Error) + + { + + Console.WriteLine(error.ToString()); + + } + + } + + } + +} +``` diff --git a/exchange/docs-conceptual/connect-to-scc-powershell.md b/exchange/docs-conceptual/connect-to-scc-powershell.md new file mode 100644 index 0000000000..b35779fdaf --- /dev/null +++ b/exchange/docs-conceptual/connect-to-scc-powershell.md @@ -0,0 +1,189 @@ +--- +title: Connect to Security & Compliance PowerShell +author: chrisda +manager: deniseb +ms.date: 05/07/2025 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn how to use the Exchange Online PowerShell V3 module to connect to Security & Compliance PowerShell with modern authentication and/or multi-factor authentication (MFA)." +--- + +# Connect to Security & Compliance PowerShell + +This article contains instructions for how to connect to Security & Compliance PowerShell using the Exchange Online PowerShell module with or without multi-factor authentication (MFA). + +The Exchange Online PowerShell module uses modern authentication for connecting to all Exchange-related PowerShell environments in Microsoft 365: Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. For more information about the Exchange Online PowerShell module, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). + +To connect to Security & Compliance PowerShell for automation, see [App-only authentication for unattended scripts](app-only-auth-powershell-v2.md). + +## What do you need to know before you begin? + +- The requirements for installing and using the module are described in [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). + + > [!NOTE] + > Remote PowerShell connections are deprecated in Security & Compliance PowerShell. For more information, see [Deprecation of Remote PowerShell (RPS) Protocol in Security & Compliance PowerShell](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432). + > + > REST API connections in the Exchange Online PowerShell V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + +- After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Permissions in the Microsoft Defender portal](/defender-office-365/mdo-portal-permissions) and [Permissions in the Microsoft Purview compliance portal](/purview/purview-compliance-portal-permissions). + +## Step 1: Load the Exchange Online PowerShell module + +> [!NOTE] +> If the module is already installed, you can typically skip this step and run **Connect-IPPSSession** without manually loading the module first. + +After you've [installed the module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module), open a PowerShell window and load the module by running the following command: + +```powershell +Import-Module ExchangeOnlineManagement +``` + +## Step 2: Connect and authenticate + +> [!NOTE] +> Connect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, `$`). The workaround is to connect using a different account that doesn't have special characters in the profile path. + +The command that you need to run uses the following syntax: + +```powershell +Connect-IPPSSession -UserPrincipalName [-ConnectionUri ] [-AzureADAuthorizationEndpointUri ] [-DelegatedOrganization ] [-PSSessionOption $ProxyOptions] +``` + +For detailed syntax and parameter information, see [Connect-IPPSSession](/powershell/module/exchange/connect-ippssession). + +- _\_ is your account in user principal name format (for example, `navin@contoso.onmicrosoft.com`). + +- The required _ConnectionUri_ and _AzureADAuthorizationEndpointUri_ values depend on the nature of your Microsoft 365 organization. Common values are described in the following list: + - **Microsoft 365 or Microsoft 365 GCC**: + - _ConnectionUri_: None. The required value `https://ps.compliance.protection.outlook.com/powershell-liveid/` is also the default value, so you don't need to use the _ConnectionUri_ parameter in Microsoft 365 or Microsoft 365 GCC environments. + - _AzureADAuthorizationEndpointUri_: None. The required value `https://login.microsoftonline.com/common` is also the default value, so you don't need to use the _AzureADAuthorizationEndpointUri_ parameter in Microsoft 365 or Microsoft 365 GCC environments. + - **Microsoft 365 GCC High**: + - _ConnectionUri_: `https://ps.compliance.protection.office365.us/powershell-liveid/` + - _AzureADAuthorizationEndpointUri_: `https://login.microsoftonline.us/common` + - **Microsoft 365 DoD**: + - _ConnectionUri_: `https://l5.ps.compliance.protection.office365.us/powershell-liveid/` + - _AzureADAuthorizationEndpointUri_: `https://login.microsoftonline.us/common` + - **Office 365 operated by 21Vianet**: + - _ConnectionUri_: `https://ps.compliance.protection.partner.outlook.cn/powershell-liveid` + - _AzureADAuthorizationEndpointUri_: `https://login.chinacloudapi.cn/common` + +- If you're behind a proxy server, you can use the _PSSessionOption_ parameter in the connection command. First, run this command: `$ProxyOptions = New-PSSessionOption -ProxyAccessType `, where \ is `IEConfig`, `WinHttpConfig`, or `AutoDetect`. Then, use the value `$ProxyOptions` for the _PSSessionOption_ parameter. For more information, see [New-PSSessionOption](/powershell/module/microsoft.powershell.core/new-pssessionoption). + +- Depending on the nature of your organization, you might be able to omit the _UserPrincipalName_ parameter in the next step. Instead, you enter the username and password or select stored credentials after you run the **Connect-IPPSSession** command. If it doesn't work, then you need to use the _UserPrincipalName_ parameter. + +- If you aren't using MFA, you should be able to use the _Credential_ parameter instead of the _UserPrincipalName_ parameter. First, run the command `$Credential = Get-Credential`, enter your username and password, and then use the variable name for the _Credential_ parameter (`-Credential $Credential`). If it doesn't work, then you need to use the _UserPrincipalName_ parameter. + +### Connect to Security & Compliance PowerShell with an interactive login prompt + +1. The following examples work in Windows PowerShell 5.1 and PowerShell 7 for accounts with or without MFA: + + - **This example connects to Security & Compliance PowerShell in a Microsoft 365 or Microsoft 365 GCC organization**: + + ```powershell + Connect-IPPSSession -UserPrincipalName navin@contoso.onmicrosoft.com + ``` + + - **This example connects to Security & Compliance PowerShell in a Microsoft GCC High organization**: + + ```powershell + Connect-IPPSSession -UserPrincipalName chris@govt.us -ConnectionUri https://ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndpointUri https://login.microsoftonline.us/common + ``` + + - **This example connects to Security & Compliance PowerShell in a Microsoft 365 DoD organization**: + + ```powershell + Connect-IPPSSession -UserPrincipalName michelle@govt.mil -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndpointUri https://login.microsoftonline.us/common + ``` + + - **This example connects to Security & Compliance PowerShell in an Office 365 operated by 21Vianet organization**: + + ```powershell + Connect-IPPSSession -UserPrincipalName li@fabrikam.cn -ConnectionUri https://ps.compliance.protection.partner.outlook.cn/powershell-liveid -AzureADAuthorizationEndpointUri https://login.chinacloudapi.cn/common + ``` + +2. In the sign-in window that opens, enter your password, and then click **Sign in**. + + ![Enter your password in the Sign in to your account window.](media/connect-exo-password-prompt.png) + + > [!NOTE] + > In PowerShell 7, browser-based single sign-on (SSO) is used by default, so the sign in prompt opens in your default web browser instead of a standalone dialog. + +3. **MFA only**: A verification code is generated and delivered based on the response option that's configured for your account (for example, a text message or the Microsoft Authenticator app on your device). + + In the verification window that opens, enter the verification code, and then click **Verify**. + + ![Enter your verification code in the Sign in to your account window.](media/connect-exo-mfa-verify-prompt.png) + +### Connect to Security & Compliance PowerShell without a login prompt (unattended scripts) + +For complete instructions, see [App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell](app-only-auth-powershell-v2.md). + +### Connect to Security & Compliance PowerShell in customer organizations + +The procedures in this section require version 3.0.0 or later of the module. + +In Security & Compliance PowerShell, you need to use the _AzureADAuthorizationEndpointUri_ with the _DelegatedOrganization_ parameter. + +For more information, about partners and customer organizations, see the following topics: + +- [What is the Cloud Solution Provider (CSP) program?](/partner-center/csp-overview). +- [Introduction to granular delegated admin privileges (GDAP)](/partner-center/gdap-introduction) + +This example connects to customer organizations in the following scenarios: + +- Connect to a customer organization using a CSP account. +- Connect to a customer organization using a GDAP. +- Connect to a customer organization as a guest user. + + ```powershell + Connect-IPPSSession -UserPrincipalName navin@contoso.onmicrosoft.com -DelegatedOrganization adatum.onmicrosoft.com -AzureADAuthorizationEndpointUri https://login.microsoftonline.com/adatum.onmicrosoft.com + ``` + +## Step 3: Disconnect when you're finished + +Be sure to disconnect the session when you're finished. If you close the PowerShell window without disconnecting the session, you could use up all the sessions available to you, and you need to wait for the sessions to expire. To disconnect the session, run the following command: + +```powershell +Disconnect-ExchangeOnline +``` + +To silently disconnect without a confirmation prompt, run the following command: + +```powershell +Disconnect-ExchangeOnline -Confirm:$false +``` + +> [!NOTE] +> The disconnect command will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, `$`). The workaround is to connect using a different account that doesn't have special characters in the profile path. + +## How do you know you've connected successfully? + +The Security & Compliance PowerShell cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you've connected successfully. A quick test is to run a Security & Compliance PowerShell cmdlet, for example, **Get-RetentionCompliancePolicy**, and see the results. + +If you receive errors, check the following requirements: + +- A common problem is an incorrect password. Run the three steps again and pay close attention to the username and password that you use. + +- The account that you use to connect must be enabled for PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](disable-access-to-exchange-online-powershell.md). + +- TCP port 80 traffic needs to be open between your local computer and Microsoft 365. It's probably open, but it's something to consider if your organization has a restrictive internet access policy. + +- REST-based connections to Security & Compliance PowerShell require the PowerShellGet module, and by dependency, the PackageManagement module, so you'll receive errors if you try to connect without having them installed. For example, you might see the following error: + + > The term 'Update-ModuleManifest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. + + For more information about the PowerShellGet and PackageManagement module requirements, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + +- You might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this: + + > The request for the Windows Remote Shell with ShellId \ failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation. + + To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Security & Compliance PowerShell endpoint. diff --git a/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md b/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md new file mode 100644 index 0000000000..eafad0e59b --- /dev/null +++ b/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md @@ -0,0 +1,130 @@ +--- +title: "Control remote PowerShell access to Exchange servers" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/7/2023 +ms.audience: ITPro +audience: ITPro +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: 064e3bb0-38bf-495e-9994-784f823b88dd +description: "Administrators can learn how to block or allow users' remote PowerShell access to Exchange servers." +--- + +# Control remote PowerShell access to Exchange servers + +Remote PowerShell in Microsoft Exchange allows you to manage your Exchange organization from a remote computer that's on your internal network or from the internet. You can disable or enable a user's ability to connect to an Exchange server using remote PowerShell and the Exchange Management Shell. For more information about remote PowerShell, see [Exchange Server PowerShell (Exchange Management Shell)](exchange-management-shell.md). + +For additional management tasks related to remote PowerShell, see [Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md). + +## What do you need to know before you begin? + +- Estimated time to complete each procedure: less than 5 minutes + +- By default, all user accounts have access to remote PowerShell. However, to actually use remote PowerShell to connect to an Exchange server, the user needs to be a member of a management role group, or be directly assigned a management role that enables the user to run Exchange cmdlets. For more information about role groups and management roles, see [Exchange Server permissions](/Exchange/permissions/permissions). + + > [!IMPORTANT] + > In your haste to quickly and globally disable remote PowerShell access in your organization, beware of commands like `Get-User | Set-User -RemotePowerShellEnabled $false` without considering administrator accounts, service accounts, or health monitoring mailboxes that need remote PowerShell access. Use the procedures in this article to selectively remove remote PowerShell access, or preserve access for those who need it by using the following syntax in your global removal command: `Get-User | Where-Object {$_.UserPrincipalName -ne 'admin1@contoso.com' -and $_.UserPrincipalName -ne 'admin2@contoso.com'...} | Set-User -RemotePowerShellEnabled $false`. + > + > If you accidentally lock yourself out of remote PowerShell access, you'll need to use the otherwise highly discouraged method of directly loading the Exchange Management Shell snap-in (`Add-PSSnapIn Microsoft.Exchange.Management.PowerShell.SnapIn`) to give yourself access. Minimize the time and changes you're using with this method. Fix one account and open the Exchange Management Shell to make any additional changes. + +- You can only use PowerShell to perform these procedures. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see [Open the Exchange Management Shell](open-the-exchange-management-shell.md). + +- For detailed information about OPATH filter syntax in Exchange, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information). + +- You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Remote PowerShell" entry in the [Exchange infrastructure and PowerShell permissions](/Exchange/permissions/feature-permissions/infrastructure-permissions) article. + +- If you're using third-party tools to customize email addresses of users, you need to disable email address policies on the affected users before you do the procedures in this article. If you don't, the **Set-User** commands change the email addresses of the users to match the applicable email address policy. To disable email address policies on users, set the value of the EmailAddressPolicyEnabled parameter to $false on the [Set-Mailbox](/powershell/module/exchange/set-mailbox) cmdlet. + +> [!TIP] +> Having problems? Ask for help in the [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612) forums. + +## View the remote PowerShell access for users + +To view the remote PowerShell access status for a specific user, replace \ with the name or user principal name (UPN) of the user, and then run the following command: + +```powershell +Get-User -Identity "" | Format-List RemotePowerShellEnabled +``` + +To display the remote PowerShell access status for all users, run the following command: + +```powershell +Get-User -ResultSize unlimited | Format-Table Name,DisplayName,RemotePowerShellEnabled -AutoSize +``` + +To display all users who don't have access to remote PowerShell, run the following command: + +```powershell +Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $false' +``` + +To display all users who have access to remote PowerShell, run the following command: + +```powershell +Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $true' +``` + +## Use the Exchange Management Shell to enable or disable remote PowerShell access for a user + +This example disables remote PowerShell access for the user named Therese Lindqvist. + +```powershell +Set-User "Therese Lindqvist" -RemotePowerShellEnabled $false +``` + +This example enables remote PowerShell access for the user named Sirirat Kitjakarn. + +```powershell +Set-User "Sirirat Kitjakarn" -RemotePowerShellEnabled $true +``` + +## Use the Exchange Management Shell to disable remote PowerShell access for many users + +To prevent remote PowerShell access for a specific group of existing users, you have the following options: + +- **Filter users based on an existing attribute**: This method assumes that the target user accounts all share a unique filterable attribute. Some attributes, such as Title, Department, address information, and telephone number, are visible only when you use the **Get-User** cmdlet. Other attributes, such as CustomAttribute1-15, are visible only when you use the **Get-Mailbox** cmdlet. + +- **Use a list of specific users**: After you generate the list of specific users, you can use that list to disable their access to remote PowerShell. + +### Filter users based on an existing attribute + +To disable access to remote PowerShell for any number of users based on an existing attribute, use the following syntax: + +```powershell +$ = -ResultSize unlimited -Filter + +$ | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false} +``` + +This example removes access to remote PowerShell for all users whose **Title** attribute contains the value "Sales Associate". + +```powershell +$DSA = Get-User -ResultSize unlimited -Filter "(RecipientType -eq 'UserMailbox') -and (Title -like '*Sales Associate*')" + +$DSA | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false} +``` + +### Use a list of specific users + +To disable access to remote PowerShell for a list of specific users, use the following syntax: + +```powershell +$ = Get-Content + +$ | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false} +``` + +This example uses the text file C:\My Documents\NoPowerShell.txt to identify the users by their user principal name (UPN). The text file must contain one UPN on each line like this: + +> akol@contoso.com
tjohnston@contoso.com
kakers@contoso.com + +After you populate the text file with the user accounts you want to update, run the following commands: + +```powershell +$NPS = Get-Content "C:\My Documents\NoPowerShell.txt" + +$NPS | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false} +``` diff --git a/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md b/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md new file mode 100644 index 0000000000..79a641ef08 --- /dev/null +++ b/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md @@ -0,0 +1,135 @@ +--- +title: "Enable or disable access to Exchange Online PowerShell" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 12/11/2024 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: f969816a-2607-4655-9d47-9e8767fb5633 +search.appverid: MET150 +description: "Admins can learn how to disable or enable access to Exchange Online PowerShell for users in their organization" +--- + +# Enable or disable access to Exchange Online PowerShell + +Exchange Online PowerShell is the administrative interface that enables admins to manage the Exchange Online part of a Microsoft 365 organization from the command line (including many security features in Exchange Online Protection and Microsoft Defender for Office 365). + +By default, all accounts in Microsoft 365 are allowed to use Exchange Online PowerShell. This access doesn't give users administrative capabilities. They're still limited by [role based access control (RBAC)](/exchange/permissions-exo/permissions-exo). For example, they can configure some settings on their own mailbox and manage distribution groups that they own, but not much else. + +Admins can use the procedures in this article to disable or enable a user's ability to connect to Exchange Online PowerShell. + +## What do you need to know before you begin? + +- Estimated time to complete each procedure: less than 5 minutes + +- The procedures in this article are available only in Exchange Online PowerShell. To connect to Exchange Online PowerShell, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md). + +- You need to be assigned permissions before you can do the procedures in this article. You have the following options: + - [Exchange Online RBAC](/exchange/permissions-exo/permissions-exo): Membership in the **Organization Management** or **Recipient Management** role groups. + - [Microsoft Entra RBAC](/microsoft-365/admin/add-users/about-admin-roles): Membership in the **Exchange Administrator** or **Global Administrator**\* roles gives users the required permissions *and* permissions for other features in Microsoft 365. + + > [!IMPORTANT] + > In your haste to quickly and globally disable PowerShell access in your cloud-based organization, beware of commands like `Get-User | Set-User -EXOModuleEnabled $false` without considering admin accounts. Use the procedures in this article to **selectively** remove PowerShell access, or **preserve access for those who need it** by using the following syntax in your global removal command: `Get-User | Where-Object {$_.UserPrincipalName -ne 'admin1@contoso.onmicrosoft.com' -and $_.UserPrincipalName -ne 'admin2@contoso.onmicrosoft.com'...} | Set-User -EXOModuleEnabled $false`. + > + > If you accidentally lock yourself out of PowerShell access, create a new admin account in the Microsoft 365 admin center, and then use that account to give yourself PowerShell access using the procedures in this article. + > + > \* Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +- For detailed information about OPATH filter syntax in Exchange Online, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information). + +> [!TIP] +> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). + +## Enable or disable access to Exchange Online PowerShell for a user + +This example disables access to Exchange Online PowerShell for the user `david@contoso.onmicrosoft.com`. + +```powershell +Set-User -Identity david@contoso.onmicrosoft.com -EXOModuleEnabled $false +``` + +This example enables access to Exchange Online PowerShell for the user `chris@contoso.onmicrosoft.com`. + +```powershell +Set-User -Identity chris@contoso.onmicrosoft.com -EXOModuleEnabled $true +``` + +## Disable access to Exchange Online PowerShell for many users + +To prevent access to Exchange Online PowerShell for a specific group of existing users, you have the following options: + +- **Filter users based on an existing attribute**: This method assumes that the target user accounts all share a unique filterable attribute. Some attributes (for example, Title, Department, address information, and telephone number) are available only from the **Get-User** cmdlet. Other attributes (for example, CustomAttribute1 to CustomAttribute15) are available only from the **Get-Mailbox** cmdlet. +- **Use a list of specific users**: After you generate the list of specific users, you can use that list to disable their access to Exchange Online PowerShell. + +### Filter users based on an existing attribute + +To disable access to Exchange Online PowerShell for any number of users based on an existing attribute, use the following syntax: + +```powershell +$ = -ResultSize unlimited -Filter + +$ | foreach {Set-User -Identity $_.WindowsEmailAddress -EXOModuleEnabled $false} +``` + +This example removes access to Exchange Online PowerShell for all users whose **Title** attribute contains the value "Sales Associate". + +```powershell +$DSA = Get-User -ResultSize unlimited -Filter "(RecipientType -eq 'UserMailbox') -and (Title -like 'Sales Associate*')" + +$DSA | foreach {Set-User -Identity $_.WindowsEmailAddress -EXOModuleEnabled $false} +``` + +### Use a list of specific users + +To disable access to Exchange Online PowerShell for a list of specific users, use the following syntax: + +```powershell +$ = Get-Content + +$ | foreach {Set-User -Identity $_ -EXOModuleEnabled $false} +``` + +The following example uses the text file C:\My Documents\NoPowerShell.txt to identify the users by their accounts. The text file must contain one account on each line as follows: + +> `akol@contoso.onmicrosoft.com`
`tjohnston@contoso.onmicrosoft.com`
`kakers@contoso.onmicrosoft.com` + +After you populate the text file with the user accounts you want to update, run the following commands: + +```powershell +$NoPS = Get-Content "C:\My Documents\NoPowerShell.txt" + +$NoPS | foreach {Set-User -Identity $_ -EXOModuleEnabled $false} +``` + +## View the Exchange Online PowerShell access status for users + +> [!TIP] +> The newer `EXOModuleEnabled` property isn't available to use with the *Filter* parameter on the **Get-User** cmdlet, but the values of the `EXOModuleEnabled` property and the older `RemotePowerShellEnabled` property are always the same, so use the `RemotePowerShellEnabled` property with the *Filter* parameter on the **Get-User** cmdlet. + +To view the PowerShell access status for a specific user, replace \ with the name or user principal name (UPN) of the user, and run the following command: + +```powershell +Get-User -Identity "" | Format-List EXOModuleEnabled +``` + +To display the Exchange Online PowerShell access status for all users, run the following command: + +```powershell +Get-User -ResultSize unlimited | Format-Table -Auto DisplayName,EXOModuleEnabled +``` + +To display all users who don't have access to Exchange Online PowerShell, run the following command: + +```powershell +Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $false' +``` + +To display all users who have access to Exchange Online PowerShell, run the following command: + +```powershell +Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $true' +``` diff --git a/exchange/docs-conceptual/exchange-cmdlet-syntax.md b/exchange/docs-conceptual/exchange-cmdlet-syntax.md new file mode 100644 index 0000000000..2d91c08839 --- /dev/null +++ b/exchange/docs-conceptual/exchange-cmdlet-syntax.md @@ -0,0 +1,141 @@ +--- +title: "Exchange cmdlet syntax" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/7/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-online +ms.localizationpriority: medium +ms.assetid: 85ffe9c8-7f03-4877-8e55-3cbd40228d84 +description: "Learn about the structure and syntax of cmdlets in Exchange PowerShell, Exchange Online PowerShell, standalone Exchange Online Protection (EOP) PowerShell, and Security & Compliance PowerShell." +--- + +# Exchange cmdlet syntax + +Exchange cmdlet reference articles use a standardized method that describes key aspects about the cmdlet. For example: + +- Parameters that are available on the cmdlet. +- Values that each parameter accepts. +- Parameters that can be used together, and parameters that need to be used separately. + +This article explains these conventions, and also the syntax that's required to run commands in Exchange PowerShell. + +## Command conventions in Exchange PowerShell + +Exchange PowerShell help follows conventions that indicate what's required or optional, and how to enter parameters and values when you run a command. These command conventions are listed in the following table. + +|Symbol|Description| +|---|---| +|`-`|A hyphen indicates a parameter. For example, `-Identity`.| +|`< >`|Angle brackets indicate the possible values for a parameter. For example, `-Location ` or -Enabled \<$true \| $false\>.| +|`[ ]`|Square brackets indicate optional parameters and their values. For example, `[-WhatIf]` or `[-ResultSize ]`.

Parameter-value pairs that aren't enclosed in square brackets are required. For example, `-Password `.

Square brackets around the parameter name itself indicates a _positional_ parameter (you can use the parameter value without specifying the parameter name), and positional parameters can be required or optional.

For example, `Get-Mailbox [[-Identity] ]` means the _Identity_ parameter is positional (because it's enclosed in square brackets) and optional (because the whole parameter-value pair is enclosed in square brackets), so you can use `Get-Mailbox -Identity ` or `Get-Mailbox `. Similarly, `Set-Mailbox [-Identity] ` means the _Identity_ parameter is positional (because it's enclosed in square brackets) and required (because the whole parameter-value pair isn't enclosed in square brackets), so you can use `Set-Mailbox -Identity ` or `Set-Mailbox `.| +|`|`|Pipe symbols in parameter values indicate a choice between values. For example, -Enabled \<$true \| $false\> indicates the _Enabled_ parameter can have the value `$true` or `$false`.| + +These command conventions help you understand how a command is constructed. Except for the hyphen that indicates a parameter, you don't use these symbols as they're described in the table when you run cmdlets in Exchange PowerShell. + +## Parameter sets in Exchange PowerShell + +Parameter sets are groups of parameters that can be used with each other in the same command. Each parameter set contains at least one parameter that isn't available in the other parameter sets, but parameter sets typically share some parameters.s. + +Many cmdlets have only one parameter set, which means that all parameters can be used with each other. Other cmdlets have several parameter sets, which means some parameters can't be used with other parameters. For example, suppose the following parameter sets are available on the **New-SystemMessage** cmdlet: + +`New-SystemMessage -DsnCode -Internal -Language -Text [-Confirm] [-DomainController ] [-WhatIf] ` + +`New-SystemMessage -QuotaMessageType -Language -Text [-Confirm] [-DomainController ] [-WhatIf] ` + +The following parameters are available in the first parameter set, so you can use them in the same command: + +- _DsnCode_ +- _Internal_ +- _Language_ +- _Text_ +- _Confirm_ +- _DomainController_ +- _WhatIf_ + +The following parameters are available in the second parameter set, so you can use them in the same command: + +- _QuotaMessageType_ +- _Language_ +- _Text_ +- _Confirm_ +- _DomainController_ +- _WhatIf_ + +The parameters _DsnCode_ and _Internal_ are available only in the first parameter set. The parameter _QuotaMessageType_ is available only in the second parameter set. So, you can't use the following parameters in the same command: + +- _DsnCode_ and _QuotaMessageType_. +- _Internal_ and _QuotaMessageType_. + +The following parameters are available in both parameter sets, so you can use them in any **New-SystemMessage** command: + +- _Language_ +- _Text_ +- _Confirm_ +- _DomainController_ +- _WhatIf_ + +The `` entry indicates the cmdlet supports the basic Windows PowerShell parameters that are available on virtually any cmdlet (for example, _Verbose_). You can use common parameters with parameters from any parameter set. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). + +## Quotation marks in Exchange PowerShell + +In Exchange PowerShell, you use single quotation marks ( ' ) or double quotation marks ( " ) to enclose parameter values that contain spaces. For example, the following commands behave the same: + +- `Get-ReceiveConnector -Identity "Contoso Receive Connector"` + +- `Get-ReceiveConnector -Identity 'Contoso Receive Connector'` + +In the previous examples, if you don't enclose the value in single or double quotation marks, the command fails because PowerShell treats each word as a new argument (it thinks `Contoso` is the value of the _Identity_ parameter, and `Receive` is the value of an unspecified positional parameter). In this example, the error looks like this: + +> A positional parameter cannot be found that accepts argument 'Receive' + +For plain text values, single quotation marks vs. double quotation marks don't really matter. But, the choice is important when variables are involved: + +- **Double quotation marks**: Variables are substituted with their actual values. +- **Single quotation marks**: Variables are treated literally. + +For example, `$Server = Mailbox01` results in the following output based on which quotation marks you use: + +- **"$Server Example"** results in `Mailbox01 Example`. +- **'$Server Example'** results in `$Server Example`. + +For more information about variables, see [about_Variables](/powershell/module/microsoft.powershell.core/about/about_variables) and [about_Automatic_Variables](/powershell/module/microsoft.powershell.core/about/about_automatic_variables). + +## Escape characters in Exchange PowerShell + +In any programming language, an _escape character_ is used to identify special characters literally, and not by their normal function in that language. In Exchange PowerShell, when you enclose a text string in double quotation marks, the escape character is the back quotation mark escape character ( ` ). + +For example, if you want the output `The price is $23`, enter the value **"The price is \`$23"**. The escape character is required on the dollar sign character ( $ ) because $ defines variables in PowerShell. + +If you enclose the string in single quotation marks, the only special character you need to worry about is the single quotation mark character itself, which requires two single quotation marks to escape ( `''` ). + + For example, if you want the output `Don't confuse two single quotation marks with a double quotation mark!`, enter the value **'Don''t confuse two single quotation marks with a double quotation mark!'**. + +## Command operators in Exchange PowerShell + +The following table shows the valid operators that you can use in an Exchange command. Some of these symbols were also described in the earlier [Command conventions in Exchange PowerShell](#command-conventions-in-exchange-powershell) section. However, these symbols have different meanings when they're used on the command line as operators. For example, the minus sign that's used to indicate a parameter can also be used in a command as a mathematical operator. + +|Operator|Description| +|---|---| +|`=`|The equal sign is an assignment character. The value on the right side of the equal sign is assigned to the variable on the left side of the equal sign (for example, `$x= Get-Mailbox`). You can also use other characters with the equal sign:
  • `+=`: Add the value on the right side of the equal sign to the current value that's contained in the variable on the left side of the equal sign.
  • `-=`: Subtract the value on the right side of the equal sign from the current value that's contained in the variable on the left side of the equal sign.
  • `*=`: Multiply the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.
  • `/=`: Divide the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.
  • `%=`: Modify the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.
| +|`:`|Use a colon to separate a parameter's name from the parameter's value. For example, `-Enabled:$True`. A colon separator works and is optional on virtually all parameter-value pairs. A colon separator is required on switch parameters. For more information about switch parameters, see [about_Parameters](/powershell/module/microsoft.powershell.core/about/about_parameters).| +|`!`|The exclamation point is the logical NOT operator. The combined pair `!=` means "not equal to."| +|`[ ]`|Brackets specify the index value of an array position. Index values are offsets that always start at zero. For example, in the array named `$Red`, the value of the tenth position in the array is `$Red[9]`.

Brackets can also assign a type to a variable. For example, to identify the variable named `$A` as XML, use `$A=[XML] "value"`. The following variable types are available: `Array`, `Bool`, `Byte`, `Char`, `Char[]`, `Decimal`, `Double`, `Float`, `Int`, `Int[]`, `Long`, `Long[]`, `RegEx`, `Single`, `ScriptBlock`, `String`, `Type`, and `XML.`| +|`{ }`|Use braces to include an expression in a command. For example, `Get-Process | Where {$_.HandleCount -gt 400}`| +|`|`|Use the pipe symbol to pipe the output of one command to another command. For example, `Get-Mailbox -Server SRV1 | Set-Mailbox -ProhibitSendQuota 2GB`.| +|`>`|Use the right-angle bracket to send the output of a command to a file. If the file already exists, the contents are overwritten. For example, `Get-TransportRule > "C:\My Documents\TransportRules.txt"`.| +|`>>`|Use double right-angle brackets to append the output of a command to an existing file. If the file doesn't exist, a new file is created. For example, `Get-TransportRule >> "C:\My Documents\TransportRules.txt"`.| +|`"`|Use double quotation marks to enclose text strings that contain spaces. As previously described, variables are replaced with their actual values.| +|`$`|The dollar sign indicates a variable. For example, to create a variable named `$Blue` with the value 10, use `$Blue = 10`. After you store the variable, you can use it as the value of a parameter.| +|`@`|The at symbol references an associative array. For more information, see [about_Arrays](/powershell/module/microsoft.powershell.core/about/about_arrays).| +|`$( )`|A dollar sign with parentheses indicates command substitution. You can use command substitution when you want to use the output of one command as an argument in another command. For example, `Get-ChildItem $(Read-Host -Prompt "Enter FileName: ")`.| +|`..`|Double-periods indicate a value range. For example, if an array contains several indexes, you can return the values of all indexes between the second and fifth indexes by running the command: `$Blue[2..5]`.| +|`+`|The plus sign operator adds two values together. For example, `6 + 6` equals `12`.| +|`-`|The minus sign operator subtracts one value from another value (for example, `12 - 6` equals `6`) or indicates a negative number (for example, `-6 * 6` equals `-36`).| +|`*`|You can use an asterisk to:
  • **Match strings**: For example, `Get-User | Where-Object {$_.Department -like 'Sales*'})`
  • **Multiply numeric values**: For example, `6 * 6` equals `36`
  • **Repeat the string value a specified number of times**: For example, `"Test" * 3` equals `TestTestTest`
| +|`/`|A forward slash divides one value by another. For example, `6 / 6` equals `1`.| +|`%`|The percent sign has the following uses:
  • In a numerical evaluation, it returns the remainder from a division operator. For example, `6 % 4` equals `2`.
  • In a [pipeline](/powershell/module/microsoft.powershell.core/about/about_pipelines), it's shorthand for the **ForEach-Object** cmdlet. For example, `Import-Csv C:\MyFile.csv | ForEach-Object {Set-Mailbox $_.Identity -Name $_.Name}` is the same as `Import-Csv C:\MyFile.csv | % {Set-Mailbox $_.Identity -Name $_.Name}`.
| +|`?`|The question mark character is shorthand for the **Where-Object** cmdlet. For example, `Get-Alias | Where-Object {$_.Definition -eq "Clear-Host"}` is the same as `Get-Alias | ? {$_.Definition -eq "Clear-Host"}`.| diff --git a/exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md b/exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md deleted file mode 100644 index e5b54891c0..0000000000 --- a/exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: "Connect to Exchange Online Protection PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: eop -localization_priority: Normal -ms.assetid: 054e0fd7-d465-4572-93f8-a00a9136e4d1 -description: "Use remote PowerShell to connect to an Exchange Online Protection organization" ---- - -# Connect to Exchange Online Protection PowerShell - -Exchange Online Protection PowerShell allows you to manage your Exchange Online Protection organization from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Exchange Online Protection. It's a simple three-step process where you enter your Office 365 credentials, provide the required connection settings, and then import the Exchange Online Protection cmdlets into your local Windows PowerShell session so that you can use them. - -## What do you need to know before you begin? - -- Estimated time to complete: 5 minutes - -- Exchange Online Protection PowerShell is only used in *standalone* EOP organizations (for example, you have a standalone EOP subscription to protect your on-premises email environment). If you have an Office 365 subscription that includes EOP (E3, E5, etc.), you don't use Exchange Online Protection PowerShell; the same features are available in [Exchange Online PowerShell](../exchange-online/exchange-online-powershell.md). - -- You can use the following versions of Windows: - - - Windows 10 - - - Windows 8.1 - - - Windows Server 2019 - - - Windows Server 2016 - - - Windows Server 2012 or Windows Server 2012 R2 - - - Windows 7 Service Pack 1 (SP1)* - - - Windows Server 2008 R2 SP1* - - \* This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868), [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757), [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). - - - Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You'll get the following error when you try to connect: - - > Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files. - - To require all scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**): - - ```PowerShell - Set-ExecutionPolicy RemoteSigned - ``` - - You need to configure this setting only once on your computer, not every time you connect. - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612), [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). - -## Connect to Exchange Online Protection - -1. On your local computer, open Windows PowerShell and run the following command: - - ```PowerShell - $UserCredential = Get-Credential - ``` - - In the **Windows PowerShell Credential Request** dialog box, type your work or school account and password, and then click **OK**. - -2. Run the following command: - - ```PowerShell - $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection - ``` - - **Notes**: - - - For Office 365 Germany, use the _ConnectionUri_ value: `https://ps.protection.outlook.de/powershell-liveid/` - - - For Exchange Online Protection subscriptions that are Exchange Enterprise CAL with Services (includes data loss prevention (DLP) and reporting using web services), use the _ConnectionUri_ value: `https://outlook.office365.com/powershell-liveid/` - -3. Run the following command: - - ```PowerShell - Import-PSSession $Session -DisableNameChecking - ``` - - > [!NOTE] - > Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command: - - ```PowerShell - Remove-PSSession $Session - ``` - -## How do you know this worked? - -After Step 3, the Exchange Online Protection cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange Online Protection cmdlet, for example, **Get-TransportRule**, and see the results. - -If you receive errors, check the following requirements: - -- A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1. - -- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online Protection organization. - -- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy. - -- The account you use to connect to Exchange Online Protection PowerShell must be represented as a [mail user in EOP](https://docs.microsoft.com/microsoft-365/security/office-365-security/manage-mail-users-in-eop) (created manually or by directory synchronization). If the account is not visible in the Exchange admin center (EAC) as a mail user at **Recipients** \> **Contacts**, you'll receive the following error when you try to connect: - - > Import-PSSession : Running the Get-Command command in a remote session reported the following error: Processing data for a remote command failed with the following error message: The request for the Windows Remote Shell with ShellId failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation. - -- The **New-PSSession** command (Step 2) might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this: - - > The request for the Windows Remote Shell with ShellId failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation. - - To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Exchange Online Protection PowerShell endpoint. - -## See also - -The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics. - -- [Get-Credential](https://go.microsoft.com/fwlink/p/?LinkId=389618) - -- [New-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389621) - -- [Import-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389619) - -- [Remove-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389620) - -- [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623) diff --git a/exchange/docs-conceptual/exchange-eop/exchange-online-protection-powershell.md b/exchange/docs-conceptual/exchange-eop/exchange-online-protection-powershell.md deleted file mode 100644 index 1a3dbf9177..0000000000 --- a/exchange/docs-conceptual/exchange-eop/exchange-online-protection-powershell.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: "Exchange Online Protection PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: 2/20/2018 -ms.audience: Admin -ms.topic: article -ms.service: eop -localization_priority: Normal -ms.assetid: f7918a88-774a-405e-945b-bc2f5ee9f748 -description: "Learn about using PowerShell in Exchange Online Protection" ---- - -# Exchange Online Protection PowerShell - -Exchange Online Protection PowerShell is the administrative interface that enables you to manage your Exchange Online Protection (EOP) organization from the command line. For example, you can use Exchange Online Protection PowerShell to configure mail flow rules (also known as transport rules) and connectors. - -> [!NOTE] -> Exchange Online Protection PowerShell is only used in *standalone* EOP organizations (for example, you have a standalone EOP subscription to protect your on-premises email environment). If you have an Office 365 subscription that includes EOP (E3, E5, etc.), you don't use Exchange Online Protection PowerShell; the same features are available in [Exchange Online PowerShell](../exchange-online/exchange-online-powershell.md). - -The following topics provide information about using Exchange Online Protection PowerShell: - -- To create a remote PowerShell session to your standalone Exchange Online Protection organization, see [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md). - -- For a sample script that lets admins who manage multiple tenants (companies) apply configuration settings to their tenants, see [Sample script for applying EOP settings to multiple tenants](https://docs.microsoft.com/microsoft-365/security/office-365-security/sample-script-for-applying-eop-settings-to-multiple-tenants). - -- The following introductory video shows you how to connect to and use Exchange Online Protection PowerShell. - - **Note:** This video applies to Exchange Online and standalone EOP organizations. When you connect to your organization, be sure to specify the correct URL (_ConnectionUri_ value). The required URL is different for Exchange Online and standalone EOP organizations. - - [Use Remote PowerShell in EOP](https://videoplayercdn.osi.office.net/hub/?csid=ux-cms-en-us-msoffice&uuid=9cb28006-c2cb-45b6-b72e-eeed8767dee7&AutoPlayVideo=false) diff --git a/exchange/docs-conceptual/exchange-eop/media/MSN_Video_Widget.gif b/exchange/docs-conceptual/exchange-eop/media/MSN_Video_Widget.gif deleted file mode 100644 index 852a7daa98..0000000000 Binary files a/exchange/docs-conceptual/exchange-eop/media/MSN_Video_Widget.gif and /dev/null differ diff --git a/exchange/docs-conceptual/exchange-management-shell.md b/exchange/docs-conceptual/exchange-management-shell.md new file mode 100644 index 0000000000..f10d3cc542 --- /dev/null +++ b/exchange/docs-conceptual/exchange-management-shell.md @@ -0,0 +1,82 @@ +--- +title: "Exchange Server PowerShell (Exchange Management Shell)" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/1/2023 +ms.audience: ITPro +audience: ITPro +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: 925ad66f-2f05-4269-9923-c353d9c19312 +description: "Learn about Exchange Server PowerShell, also known as the Exchange Management Shell. This article describes how PowerShell works on Exchange servers, and provides links to other articles that can help you learn how to use the Exchange Management Shell." +--- + +# Exchange Server PowerShell (Exchange Management Shell) + +The Exchange Management Shell is built on Windows PowerShell technology and provides a powerful command-line interface that enables the automation of Exchange administration tasks. You can use the Exchange Management Shell to manage every aspect of Exchange. For example, you can create email accounts, create Send connectors and Receive connectors, configure mailbox database properties, and manage distribution groups. + +You can use the Exchange Management Shell to perform every task that's available in the Exchange graphical management tools, plus things that you can't do there (for example, bulk operations). In fact, when you do something in the Exchange admin center (EAC), the Exchange Control Panel (ECP), or the Exchange Management Console (EMC), it's the Exchange Management Shell that does the work behind the scenes. + +The Exchange Management Shell also provides a robust and flexible scripting platform. You can often replace long, complex Visual Basic scripts with Exchange Management Shell commands that use as little as one line of code. The Exchange Management Shell offers this flexibility because it uses an object model that's based on the Microsoft .NET Framework. This object model enables Exchange cmdlets to apply the output from one command to subsequent commands. + +To start using the Exchange Management Shell immediately, see the [Exchange Management Shell documentation](#exchange-management-shell-documentation) section later in this article. + +> [!NOTE] +> There is no Microsoft-provided module in the PowerShell Gallery for Exchange Server PowerShell. Instead, to use PowerShell in Exchange Server, you have the following options: +> +> - Open the Exchange Management Shell on an Exchange server or that you've installed locally on your own computer using a **Management tools** only installation of Exchange server. For more information, see [Install the Exchange Server Management Tools](/Exchange/plan-and-deploy/post-installation-tasks/install-management-tools) and [Open the Exchange Management Shell](open-the-exchange-management-shell.md). +> - Open a remote PowerShell session from Windows PowerShell on your local computer. For more information, see [Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md). + +## How the Exchange Management Shell works on all Exchange server roles except Edge Transport + +Whether you use the Exchange Management Shell on a local Exchange server or on an Exchange server that's located across the country, remote PowerShell does the work. + +When you select the Exchange Management Shell shortcut on an Exchange server, the local instance of Windows PowerShell takes the following steps: + +1. Connects to the closest Exchange server (typically, the local Exchange server) using a required Windows PowerShell component called Windows Remote Management (WinRM). +2. Performs authentication checks. +3. Creates a remote PowerShell session for you to use. + +You only get access to the Exchange cmdlets and parameters that are associated with the Exchange management role groups and management roles you're assigned. For more information about how Exchange uses role groups and roles to manage who can do what tasks, see [Exchange Server permissions](/Exchange/permissions/permissions). + +A benefit of remote PowerShell is that you can use Windows PowerShell on a local computer to connect to an Exchange server remotely by importing the Exchange cmdlets into the PowerShell session. The only requirements for the computer are: + +- A supported operating system for Exchange Server. +- A supported version of the .NET Framework. +- A supported version of the Windows Management Framework (WMF), which includes WinRM and Windows PowerShell. + +For details, see the following articles: + +- [Exchange 2019 system requirements](/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019&preserve-view=true) +- [Exchange 2016 system requirements](/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016&preserve-view=true) +- [Exchange 2013 system requirements](/exchange/exchange-2013-system-requirements-exchange-2013-help) +- [Exchange 2010 system requirements](/previous-versions/office/exchange-server-2010/aa996719(v=exchg.141)) + +However, we recommend that you install the Exchange management tools (which includes the Exchange Management Shell) on any computer that you use to frequently manage Exchange Server. Without the Exchange management tools installed, you need to manually connect to the remote Exchange server, and you don't have access to the additional capabilities that the Exchange management tools provide. + +For more information about connecting to Exchange servers without the Exchange management tools installed, see [Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md). + +## How the Exchange Management Shell works on Edge Transport servers + +On Edge Transport servers, the Exchange Management Shell works differently. You typically deploy Edge Transport servers in your perimeter network, either as stand-alone servers or as members of a perimeter Active Directory domain. + +When you select the Exchange Management Shell shortcut on an Exchange Edge Transport server, the local instance of Windows PowerShell creates a local PowerShell session for you to use. + +Edge Transport servers don't use management roles or management role groups to control permissions. The local Administrators group controls who can configure the Exchange features on the local server. + +For more information about Edge Transport servers, see [Edge Transport Servers](/Exchange/architecture/edge-transport-servers/edge-transport-servers). + +## Exchange Management Shell documentation + +The following table provides links to articles that can help you learn about and use the Exchange Management Shell. + +|Article|Description| +|---|---| +|[Open the Exchange Management Shell](open-the-exchange-management-shell.md)|Find and open the Exchange Management Shell on an Exchange server or a computer that has the Exchange management tools installed.| +|[Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md)|Use Windows PowerShell on a local computer to connect to an Exchange server.| +|[Control remote PowerShell access to Exchange servers](control-remote-powershell-access-to-exchange-servers.md)|Learn how to block or allow users' remote PowerShell access to Exchange servers.| +|[Find the permissions required to run any Exchange cmdlet](find-exchange-cmdlet-permissions.md)|Find the permissions you need to run a specific cmdlet, or one or more parameters on the cmdlet.| +|[Exchange cmdlet syntax](exchange-cmdlet-syntax.md)|Learn about the structure and syntax of cmdlets in Exchange PowerShell.| +|[Recipient filters in Exchange Management Shell commands](recipient-filters.md)|Learn about recipient filters in the Exchange Management Shell.| diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md new file mode 100644 index 0000000000..5849e19153 --- /dev/null +++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md @@ -0,0 +1,786 @@ +--- +title: About the Exchange Online PowerShell V3 module +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 05/07/2025 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +keywords: Exchange Online PowerShell V2 module, Exchange Online PowerShell V3 module, EXO V2 module, EXO V3 module +description: "Admins can learn about the installation, maintenance, and design of the Exchange Online PowerShell V3 module that they use to connect to all Exchange-related PowerShell environments in Microsoft 365." +--- + +# About the Exchange Online PowerShell module + +The Exchange Online PowerShell module uses modern authentication and works with or without multi-factor authentication (MFA) for connecting to all Exchange-related PowerShell environments in Microsoft 365: Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. + +For connection instructions using the module, see the following articles: + +- [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md) +- [Connect to Security & Compliance PowerShell](connect-to-scc-powershell.md) +- [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md) +- [App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell](app-only-auth-powershell-v2.md) +- [Use Azure managed identities to connect to Exchange Online PowerShell](connect-exo-powershell-managed-identity.md) +- [Use C# to connect to Exchange Online PowerShell](connect-to-exo-powershell-c-sharp.md) + +The rest of this article explains how the module works, how to install and maintain the module, and the optimized Exchange Online cmdlets that are available in the module. + +> [!TIP] +> Version 3.0.0 and later (2022) is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module). Version 2.0.5 and earlier (2021) was known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). + +## REST API connections in the EXO V3 module + +Exchange Online PowerShell and Security & Compliance PowerShell now use REST API connections for all cmdlets: + +- **Exchange Online PowerShell**: EXO V3 module v3.0.0 or later. +- **Security & Compliance PowerShell**: EXO V3 module v3.2.0 or later. + +REST API connections require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](#powershellget-for-rest-api-connections-in-windows). + +Cmdlets in REST API connections have the following advantages over their historical counterparts: + +- **More secure**: Built-in support for modern authentication and no dependence on the remote PowerShell session. PowerShell on your client computer doesn't need [Basic authentication in WinRM](#turn-on-basic-authentication-in-winrm). +- **More reliable**: Transient failures use built-in retries, so failures or delays are minimized. For example: + - Failures due to network delays. + - Delays due to large queries that take a long time to complete. +- **Better performance**: REST API connections avoid setting up a PowerShell runspace. + +The benefits of cmdlets in REST API connections are described in the following table: + +| |Remote PowerShell cmdlets|Get-EXO\* cmdlets|REST API cmdlets| +|---|---|---|---| +|**Security**|Least secure|Highly secure|Highly secure| +|**Performance**|Low performance|High performance|Medium performance| +|**Reliability**|Least reliable|Highly reliable|Highly reliable| +|**Functionality**|All parameters and output properties available|Limited parameters and output properties available|All parameters and output properties available| + +REST API cmdlets have the same cmdlet names and work just like their remote PowerShell equivalents, so you don't need to update cmdlet names or parameters in older scripts. + +> [!TIP] +> The [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command) cmdlet doesn't work in REST API connections. For alternatives, see [Workarounds for Invoke-Command scenarios in REST API connections](invoke-command-workarounds-rest-api.md). + +Basic authentication (remote PowerShell) connections are deprecated in Exchange Online PowerShell and Security & Compliance PowerShell. For more information, see [here](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-in-exchange-online-re-enabling/ba-p/3779692) and [here](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432). + +A few cmdlets in Exchange Online PowerShell have been updated with the experimental _UseCustomRouting_ switch in REST API connections. This switch routes the command directly to the required Mailbox server, and might improve overall performance. Use the _UseCustomRouting_ switch experimentally. + +- When you use the _UseCustomRouting_ switch, you can use only the following values for identity of the mailbox: + - User principal name (UPN) + - Email address + - Mailbox GUID + +- The _UseCustomRouting_ switch is available only on the following Exchange Online PowerShell cmdlets in REST API connections: + - **Get-Clutter** + - **Get-FocusedInbox** + - **Get-InboxRule** + - **Get-MailboxAutoReplyConfiguration** + - **Get-MailboxCalendarFolder** + - **Get-MailboxFolderPermission** + - **Get-MailboxFolderStatistics** + - **Get-MailboxMessageConfiguration** + - **Get-MailboxPermission** + - **Get-MailboxRegionalConfiguration** + - **Get-MailboxStatistics** + - **Get-MobileDeviceStatistics** + - **Get-UserPhoto** + - **Remove-CalendarEvents** + - **Set-Clutter** + - **Set-FocusedInbox** + - **Set-MailboxRegionalConfiguration** + - **Set-UserPhoto** + +- Use the [Get-ConnectionInformation](/powershell/module/exchange/get-connectioninformation) cmdlet to get information about REST API connections to Exchange Online PowerShell and Security & Compliance PowerShell. This cmdlet is required because the [Get-PSSession](/powershell/module/microsoft.powershell.core/get-pssession) cmdlet in Windows PowerShell doesn't return information for REST API connections. + + Scenarios where you can use **Get-ConnectionInformation** are described in the following table: + + |Scenario|Expected output| + |---|---| + |Run after **Connect-ExchangeOnline** or **Connect-IPPSSession** commands for REST API connections.|Returns one connection information object.| + |Run after multiple **Connect-ExchangeOnline** or **Connect-IPPSSession** commands for REST API connections.|Returns a collection of connection information objects.| + +- Use the _SkipLoadingFormatData_ switch on the **Connect-ExchangeOnline** cmdlet to avoid loading format data and to run **Connect-ExchangeOnline** commands faster. + +- Cmdlets backed by the REST API have a 15-minute timeout, which can affect bulk operations. For example, the following **Update-DistributionGroupMember** command to update 10,000 members of a distribution group might time out: + + ```powershell + $Members = @("member1","member2",...,"member10000") + + Update-DistributionGroupMember -Identity DG01 -Members $Members + ``` + + Instead, use the **Update-DistributionGroupMember** command to update fewer members, and then add the remaining members individually using an **Add-DistributionGroupMember** command. For example: + + ```powershell + Update-DistributionGroupMember -Identity DG01 -Members $Members[0..4999] + + $Remaining = $Members[-5000..-1] + + foreach ($Member in $Remaining) + + { + Add-DistributionGroupMember -Identity DG01 -Member $Member + } + ``` + +For more information about what's new in the EXO V3 module, see the [Release notes](#release-notes) section later in this article. + +## Report bugs and issues for Preview versions of the Exchange Online PowerShell module + +> [!TIP] +> For General Availability (GA) versions of the module, don't use the following email address to report issues. Messages about GA versions of the module won't be answered. Instead, open a support ticket. + +For **Preview versions of the module**, use `exocmdletpreview[at]service[dot]microsoft[dot]com` to report any issues that you might encounter. Be sure to include the log files in your email message. To generate the log files, replace \ with an output folder, and then run the following command: + +```powershell +Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath -LogLevel All +``` + +## Cmdlets in the Exchange Online PowerShell module + +The EXO module contains nine exclusive **Get-EXO\*** cmdlets that are optimized for speed in bulk data retrieval scenarios (thousands and thousands of objects) in Exchange Online PowerShell. The improved cmdlets in the module are listed in the following table: + +|EXO module cmdlet|Older related cmdlet| +|---|---| +|[Get-EXOMailbox](/powershell/module/exchange/get-exomailbox)|[Get-Mailbox](/powershell/module/exchange/get-mailbox)| +|[Get-EXORecipient](/powershell/module/exchange/get-exorecipient)|[Get-Recipient](/powershell/module/exchange/get-recipient)| +|[Get-EXOCasMailbox](/powershell/module/exchange/get-exocasmailbox)|[Get-CASMailbox](/powershell/module/exchange/get-casmailbox)| +|[Get-EXOMailboxPermission](/powershell/module/exchange/get-exomailboxPermission)|[Get-MailboxPermission](/powershell/module/exchange/get-mailboxpermission)| +|[Get-EXORecipientPermission](/powershell/module/exchange/get-exorecipientpermission)|[Get-RecipientPermission](/powershell/module/exchange/get-recipientpermission)| +|[Get-EXOMailboxStatistics](/powershell/module/exchange/get-exomailboxstatistics)|[Get-MailboxStatistics](/powershell/module/exchange/get-mailboxstatistics)| +|[Get-EXOMailboxFolderStatistics](/powershell/module/exchange/get-exomailboxfolderstatistics)|[Get-MailboxFolderStatistics](/powershell/module/exchange/get-mailboxfolderstatistics)| +|[Get-EXOMailboxFolderPermission](/powershell/module/exchange/get-exomailboxfolderpermission)|[Get-MailboxFolderPermission](/powershell/module/exchange/get-mailboxfolderpermission)| +|[Get-EXOMobileDeviceStatistics](/powershell/module/exchange/get-exomobiledevicestatistics)|[Get-MobileDeviceStatistics](/powershell/module/exchange/get-mobiledevicestatistics)| + +> [!TIP] +> If you open multiple connections to Exchange Online PowerShell in the same window, the **Get-EXO\*** cmdlets are always associated with the last (most recent) Exchange Online PowerShell connection. Run the following command to find the REST API session where the **Get-EXO\*** cmdlets are run: `Get-ConnectionInformation | Where-Object {$_.ConnectionUsedForInbuiltCmdlets -eq $true}`. + +The connection-related cmdlets in the module are listed in the following table: + +|EXO module cmdlet|Older related cmdlet|Comments| +|---|---|---| +|[Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline)|**Connect-EXOPSSession** in V1 of the module
or
[New-PSSession](/powershell/module/microsoft.powershell.core/new-pssession)|| +|[Connect-IPPSSession](/powershell/module/exchange/connect-ippssession)|**Connect-IPPSSession** in V1 of the module|| +|[Disconnect-ExchangeOnline](/powershell/module/exchange/disconnect-exchangeonline)|[Remove-PSSession](/powershell/module/microsoft.powershell.core/remove-pssession)|| +|[Get-ConnectionInformation](/powershell/module/exchange/get-connectioninformation)|[Get-PSSession](/powershell/module/microsoft.powershell.core/get-pssession)|Available in v3.0.0 or later.| + +> [!TIP] +> Frequent use of the **Connect-ExchangeOnline** and **Disconnect-ExchangeOnline** cmdlets in a single PowerShell session or script might lead to a memory leak. The best way to avoid this issue is to use the _CommandName_ parameter on the **Connect-ExchangeOnline** cmdlet to limit the cmdlets that are used in the session. + +Miscellaneous Exchange Online cmdlets that happen to be in the module are listed in the following table: + +|Cmdlet|Comments| +|---|---| +|[Get-DefaultTenantBriefingConfig](/powershell/module/exchange/get-defaulttenantbriefingconfig)|Available in v3.2.0 or later.| +|[Set-DefaultTenantBriefingConfig](/powershell/module/exchange/set-defaulttenantbriefingconfig)|Available in v3.2.0 or later.| +|[Get-DefaultTenantMyAnalyticsFeatureConfig](/powershell/module/exchange/get-defaulttenantmyanalyticsfeatureconfig)|Available in v3.2.0 or later.| +|[Set-DefaultTenantMyAnalyticsFeatureConfig](/powershell/module/exchange/set-defaulttenantmyanalyticsfeatureconfig)|Available in v3.2.0 or later.| +|[Get-MyAnalyticsFeatureConfig](/powershell/module/exchange/get-myanalyticsfeatureconfig)|Available in v2.0.4 or later.| +|[Set-MyAnalyticsFeatureConfig](/powershell/module/exchange/set-myanalyticsfeatureconfig)|Available in v2.0.4 or later.| +|[Get-UserBriefingConfig](/powershell/module/exchange/get-userbriefingconfig)|Replaced by [Get-MyAnalyticsFeatureConfig](/powershell/module/exchange/get-myanalyticsfeatureconfig).| +|[Set-UserBriefingConfig](/powershell/module/exchange/set-userbriefingconfig)|Replaced by [Set-MyAnalyticsFeatureConfig](/powershell/module/exchange/set-myanalyticsfeatureconfig).| +|[Get-VivaInsightsSettings](/powershell/module/exchange/get-vivainsightssettings)|Available in v2.0.5 or later.| +|[Set-VivaInsightsSettings](/powershell/module/exchange/set-vivainsightssettings)|Available in v2.0.5 or later.| +|[Get-VivaModuleFeature](/powershell/module/exchange/get-vivamodulefeature)|Available in v3.2.0 or later.| +|[Get-VivaModuleFeatureEnablement](/powershell/module/exchange/get-vivamodulefeatureenablement)|Available in v3.2.0 or later.| +|[Add-VivaModuleFeaturePolicy](/powershell/module/exchange/add-vivamodulefeaturepolicy)|Available in v3.2.0 or later.| +|[Get-VivaModuleFeaturePolicy](/powershell/module/exchange/get-vivamodulefeaturepolicy)|Available in v3.2.0 or later.| +|[Remove-VivaModuleFeaturePolicy](/powershell/module/exchange/remove-vivamodulefeaturepolicy)|Available in v3.2.0 or later.| +|[Update-VivaModuleFeaturePolicy](/powershell/module/exchange/update-vivamodulefeaturepolicy)|Available in v3.2.0 or later.| +|[Add-VivaOrgInsightsDelegatedRole](/powershell/module/exchange/add-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.| +|[Get-VivaOrgInsightsDelegatedRole](/powershell/module/exchange/get-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.| +|[Remove-VivaOrgInsightsDelegatedRole](/powershell/module/exchange/remove-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.| + +## Install and maintain the Exchange Online PowerShell module + +You download the module from the PowerShell gallery at . + +The procedures in this section explain how to install, update, and uninstall the module. + +### Supported operating systems for the Exchange Online PowerShell module + +The latest versions of the module are officially supported in PowerShell 7 on Windows, Linux, and Apple macOS. + +Specifically, version **2.0.4 or later** is supported in **PowerShell 7.0.3 or later**. + +For more information about PowerShell 7, see [Announcing PowerShell 7.0](https://devblogs.microsoft.com/powershell/announcing-PowerShell-7-0/). + +#### Apple macOS + +The module is supported in the following versions of macOS: + +- macOS 11 Big Sur or later +- macOS 10.15 Catalina +- macOS 10.14 Mojave + +For instructions on installing PowerShell 7 on macOS, see [Installing PowerShell on macOS](/powershell/scripting/install/installing-powershell-core-on-macos). + +As described in the installation article, you need to install OpenSSL, which is required for WSMan. + +After you install PowerShell 7 and OpenSSL, do the following steps: + +1. Run PowerShell as superuser: `sudo pwsh` +2. In the PowerShell superuser session, run the following commands: + + ```powershell + Install-Module -Name PSWSMan + + Install-WSMan + ``` + + If prompted, accept PSGallery as the source for the cmdlets. + +Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exchange-online-powershell-module) and [install the Exchange Online PowerShell module](#install-the-exchange-online-powershell-module). + +#### Linux + +The module is officially supported in the following distributions of Linux: + +- Ubuntu 24.04 LTS +- Ubuntu 20.04 LTS +- Ubuntu 18.04 LTS + +For instructions on installing PowerShell 7 on Linux, see [Installing PowerShell on Linux](/powershell/scripting/install/installing-powershell-core-on-linux?view=powershell-7.1&preserve-view=true). + +After you install PowerShell 7, do the following steps: + +1. Run PowerShell as superuser: `sudo pwsh` +2. In the PowerShell superuser session, run the following commands: + + ```powershell + Install-Module -Name PSWSMan + + Install-WSMan + ``` + + If prompted, accept PSGallery as the source for the cmdlets. + +Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exchange-online-powershell-module) and [install the Exchange Online PowerShell module](#install-the-exchange-online-powershell-module). + +> [!NOTE] +> If you connect to Exchange Online PowerShell from a network that's behind a proxy server, the EXO V2 module (version v2.0.5 or earlier) doesn't work in Linux. You need to use the EXO V3 module (v3.0.0 or later) in Linux to connect from a network that's behind a proxy server. + +#### Windows + +All versions of the module are supported in Windows PowerShell 5.1. + +PowerShell 7 on Windows requires version 2.0.4 or later. + +Version 2.0.5 or later of the module requires the Microsoft .NET Framework 4.7.2 or later to connect. Otherwise, you get a `System.Runtime.InteropServices.OSPlatform` error. This requirement shouldn't be an issue in current versions of Windows. For more information about versions of Windows that support the .NET Framework 4.7.2, see [this article](/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-472). + +Windows PowerShell requirements and module support **in older versions of Windows** are described in the following list: + +- Windows 8.1¹ +- Windows Server 2012 or Windows Server 2012 R2¹ +- Windows 7 Service Pack 1 (SP1)² ³ ⁴ +- Windows Server 2008 R2 SP1² ³ ⁴ + +- ¹ PowerShell 7 on this version of Windows requires the [Windows 10 Universal C Runtime (CRT)](https://www.microsoft.com/download/details.aspx?id=50410). +- ² Support for this version of Windows has ended, and is now supported only in Azure virtual machines. +- ³ This version of Windows supports only v2.0.3 or earlier versions of the module. +- ⁴ Windows PowerShell 5.1 on this version of Windows requires the .NET Framework 4.5 or later and the Windows Management Framework 5.1. For more information, see [Windows Management Framework 5.1](https://aka.ms/wmf5download). + +### Prerequisites for the Exchange Online PowerShell module + +#### Set the PowerShell execution policy to RemoteSigned + +> [!TIP] +> The settings in this section apply to all versions of PowerShell on all operating systems. + +PowerShell needs to be configured to run scripts, and by default, it isn't. You get the following error when you try to connect: + +> Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files. + +To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated PowerShell window (a PowerShell window you open by selecting **Run as administrator**): + +```powershell +Set-ExecutionPolicy RemoteSigned +``` + +For more information about execution policies, see [About Execution Policies](/powershell/module/microsoft.powershell.core/about/about_execution_policies). + +#### Turn on Basic authentication in WinRM + +> [!IMPORTANT] +> REST API connections don't require Basic authentication in WinRM as described in this section. As described [earlier in this article](#rest-api-connections-in-the-exo-v3-module), Basic authentication (remote PowerShell) access to Exchange Online PowerShell and Security & Compliance PowerShell are deprecated. The information in this section is maintained for historical purposes. + +For remote PowerShell connections that don't use the REST API (which are now impossible), WinRM needs to allow Basic authentication. **We don't send the username and password combination**. The Basic authentication **header** is required to send the session's OAuth token, because the client-side implementation of WinRM doesn't support OAuth. + +To verify that Basic authentication is enabled for WinRM, run the following command in a **Command Prompt** or **Windows PowerShell**: + +> [!NOTE] +> The following commands require that WinRM is enabled. To enable WinRM, run the following command: `winrm quickconfig`. + +```DOS +winrm get winrm/config/client/auth +``` + +If you don't see the value `Basic = true`, you need to run **one** of the following commands to enable Basic authentication for WinRM: + +- **In a Command Prompt**: + + ```DOS + winrm set winrm/config/client/auth @{Basic="true"} + ``` + +- **In Windows PowerShell**: + + ```powershell + winrm set winrm/config/client/auth '@{Basic="true"}' + ``` + +- **In Windows PowerShell to modify the registry**: + + ```PowerShell + Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client' -Name 'AllowBasic' -Type DWord -Value '1' + ``` + +If Basic authentication for WinRM is disabled, you get one of the following errors when you try to connect using a Basic authentication (remote PowerShell) connection: + +> The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again. +> +> Create Powershell Session is failed using OAuth. + +### PowerShellGet for REST API connections in Windows + +[REST API connections](#rest-api-connections-in-the-exo-v3-module) in Windows require the PowerShellGet module, and by dependency, the PackageManagement module. Consideration for these modules is more for PowerShell 5.1 than PowerShell 7, but all versions of PowerShell benefit from having the latest versions of the modules installed. For installation and update instructions, see [Installing PowerShellGet on Windows](/powershell/scripting/gallery/installing-psget). + +> [!TIP] +> Beta versions of the PackageManagement or PowerShellGet modules might cause connection issues. If you have connection issues, verify that you don't have Beta versions of the modules installed by running the following command: `Get-InstalledModule PackageManagement -AllVersions; Get-InstalledModule PowerShellGet -AllVersions`. + +If you don't have PowerShellGet installed when you try to create a REST API connection, you get the following error when you try to connect: + +> Cannot find a cmdlet Update-Manifest + +### Install the Exchange Online PowerShell module + +To install the module for the first time, complete the following steps: + +1. Install or update the PowerShellGet module as described in [Installing PowerShellGet](/powershell/scripting/gallery/installing-psget). + +2. Close and re-open the Windows PowerShell window. + +3. Now you can use the **Install-Module** cmdlet to install the module from the PowerShell Gallery. Typically, you want the latest public version of the module, but you can also install a Preview version if any are available. + + - To install **the latest public version** of the module, run **one** of the following commands: + + - In an elevated PowerShell window (all users): + + ```powershell + Install-Module -Name ExchangeOnlineManagement + ``` + + - Only for the current user account: + + ```powershell + Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser + ``` + + - To see **the available Preview versions** of the module, run the following command: + + ```powershell + Find-Module ExchangeOnlineManagement -AllVersions -AllowPrerelease + ``` + + - To install **the latest available Preview version** of the module, run **one** of the following commands: + + - In an elevated PowerShell window (all users): + + ```powershell + Install-Module -Name ExchangeOnlineManagement -AllowPrerelease + ``` + + - Only for the current user account: + + ```powershell + Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser -AllowPrerelease + ``` + + - To install **a specific Preview version** of the module, replace \ with the necessary value, and run **one** of the following commands: + + - In an elevated PowerShell window (all users): + + ```powershell + Install-Module -Name ExchangeOnlineManagement -RequiredVersion -AllowPrerelease + ``` + + - Only for the current user account: + + ```powershell + Install-Module -Name ExchangeOnlineManagement -RequiredVersion -AllowPrerelease -Scope CurrentUser + ``` + + When you're finished, enter **Y** to accept the license agreement. + +For detailed syntax and parameter information, see [Install-Module](/powershell/module/powershellget/install-module). + +### Update the Exchange Online PowerShell module + +If the module is already installed on your computer, you can use the procedures in this section to update the module. + +1. To see the version of the module that's currently installed and where it's installed, run the following command: + + ```powershell + Get-InstalledModule ExchangeOnlineManagement | Format-List Name,Version,InstalledLocation + ``` + + If the module is installed in C:\Program Files\WindowsPowerShell\Modules\, it's installed for all users. If the module is installed in your Documents folder, it's installed only for the current user account. + +2. You can use the **Update-Module** cmdlet to update the module from the PowerShell Gallery. Typically, you want the latest public version of the module, but you can also upgrade to a Preview version if any are available. + + - To upgrade to **the latest public version** of the module, run **one** of the following commands based on how you originally installed the module (all users vs. only for the current user account): + + - In an elevated PowerShell window (all users): + + ```powershell + Update-Module -Name ExchangeOnlineManagement + ``` + + - Only for the current user account: + + ```powershell + Update-Module -Name ExchangeOnlineManagement -Scope CurrentUser + ``` + + - To upgrade to **a Preview version** of the module, you can upgrade to the latest available Preview version, or you can use the _RequiredVersion_ parameter to upgrade to a specific Preview version. + + - To see **the available Preview versions** of the module, run the following command: + + ```powershell + Find-Module ExchangeOnlineManagement -AllVersions -AllowPrerelease + ``` + + - To upgrade to **the latest available Preview version** of the module, run **one** of the following commands: + + - In an elevated PowerShell window (all users): + + ```powershell + Update-Module -Name ExchangeOnlineManagement -AllowPrerelease + ``` + + - Only for the current user account: + + ```powershell + Update-Module -Name ExchangeOnlineManagement -Scope CurrentUser -AllowPrerelease + ``` + + - To upgrade to **a specific Preview version** of the module, replace \ with the necessary value, and run **one** of the following commands: + + - In an elevated PowerShell window (all users): + + ```powershell + Update-Module -Name ExchangeOnlineManagement -RequiredVersion -AllowPrerelease + ``` + + - Only for the current user account: + + ```powershell + Update-Module -Name ExchangeOnlineManagement -Scope CurrentUser -RequiredVersion -AllowPrerelease + ``` + + When you're finished, enter **Y** to accept the license agreement. + +3. To confirm that the update was successful, run the following commands to check the version information of the module that's installed: + + ```powershell + Import-Module ExchangeOnlineManagement; Get-Module ExchangeOnlineManagement + ``` + +For detailed syntax and parameter information, see [Update-Module](/powershell/module/powershellget/update-module). + +### Troubleshoot installing the Exchange Online PowerShell module + +- You receive one of the following errors: + + > The specified module 'ExchangeOnlineManagement' with PowerShellGetFormatVersion '\' isn't supported by the current version of PowerShellGet. Get the latest version of the PowerShellGet module to install this module, 'ExchangeOnlineManagement'. + + > WARNING: Unable to download from URI 'https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409' to ''. + + > WARNING: Unable to download the list of available providers. Check your internet connection. + + Update your installation of the PowerShellGet module to the latest version as described in [Installing PowerShellGet](/powershell/scripting/gallery/installing-psget). Be sure to close and re-open the PowerShell window before you attempt to update the ExchangeOnlineManagement module again. + +- You receive the following error: + + > No match was found for the specified search criteria and module name 'ExchangeOnlineManagement'. Try running `Get-PSRepository` to see all available registered module repositories. + + The default repository for PowerShell modules isn't set to PSGallery. To fix this error, run the following command: + + ```powershell + Register-PSRepository -Default + ``` + +- As of April 2020, the PowerShell Gallery only supports connections using TLS 1.2 or later. For more information, see [PowerShell Gallery TLS Support](https://devblogs.microsoft.com/powershell/powershell-gallery-tls-support/). + + To check your current settings in the Microsoft .NET Framework, run the following command in Windows PowerShell: + + ```powershell + [Net.ServicePointManager]::SecurityProtocol + ``` + + As described in the PowerShell Gallery TLS Support article, to _temporarily_ change the security protocol to TLS 1.2 to install the PowerShellGet or ExchangeOnlineManagement modules, run the following command in Windows PowerShell _before_ you install the module: + + ```powershell + [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 + ``` + + To _permanently_ enable strong cryptography in the Microsoft .NET Framework version 4.x or later, run one of the following commands based on your Windows architecture: + + - x64: + + ```powershell + Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1' + ``` + + - x86: + + ```powershell + Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1' + ``` + + For more information, see [SchUseStrongCrypto](/dotnet/framework/network-programming/tls#schusestrongcrypto). + +### Uninstall the Exchange Online PowerShell module + +To see the version of the module that's currently installed and where it's installed, run the following command: + + ```powershell + Get-InstalledModule ExchangeOnlineManagement | Format-List Name,Version,InstalledLocation + ``` + + If the module is installed in C:\Program Files\WindowsPowerShell\Modules\, it was installed for all users. If the module is installed in your Documents folder, it was installed only for the current user account. + +To uninstall the module, run the following command in one of the following environments based on how you originally installed the module (all users vs. only for the current user account): + +- In an elevated PowerShell window (all users). +- In a normal PowerShell window (only for the current user account). + + ```powershell + Uninstall-Module -Name ExchangeOnlineManagement + ``` + +For detailed syntax and parameter information, see [Uninstall-Module](/powershell/module/powershellget/uninstall-module). + +## Properties and property sets in the Exchange Online PowerShell module + +Traditional Exchange Online cmdlets return all possible object properties, including many blank or uninteresting properties. This behavior causes degraded performance (more server computation and added network load). You rarely (if ever) need the full complement of properties in the cmdlet output. + +The **Get-EXO\*** cmdlets in the module have categorized output properties. Instead of giving all properties equal importance and returning them in all scenarios, we categorized specific related properties into _property sets_. These property sets are buckets of two or more related properties on the cmdlet. + +The biggest and most used **Get-EXO\*** cmdlets use property sets: + +- [Get-EXOCasMailbox](/powershell/module/exchange/get-exocasmailbox) +- [Get-EXOMailbox](/powershell/module/exchange/get-exomailbox) +- [Get-EXOMailboxStatistics](/powershell/module/exchange/get-exomailboxstatistics) +- [Get-EXORecipient](/powershell/module/exchange/get-exorecipient) + +In those cmdlets, property sets are controlled by the following parameters: + +- _PropertySets_: This parameter accepts one or more available property set names separated by commas. The available property sets are described in [Property sets in Exchange Online PowerShell module cmdlets](cmdlet-property-sets.md). +- _Properties_: This parameter accepts one or more property names separated by commas. + +You can use the _PropertySets_ and _Properties_ parameters together in the same command. + +We also included a Minimum property set that includes a bare minimum set of required properties for the cmdlet output (for example, identity properties). The properties in the Minimum property sets are also described in [Property sets in Exchange Online PowerShell module cmdlets](cmdlet-property-sets.md). + +- If you don't use the _PropertySets_ or _Properties_ parameters, you automatically get the properties in the Minimum property set. +- If you use the _PropertySets_ or _Properties_ parameters, you get the specified properties **and** the properties in the Minimum property set. + +Either way, the cmdlet output contains far fewer properties, and the results are returned much faster. + +For example, after you [connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md), the following example returns only the properties in the Minimum property set for the first 10 mailboxes. + +```powershell +Get-EXOMailbox -ResultSize 10 +``` + +In contrast, the output of the same **Get-Mailbox** command would return at least 230 properties for each of the first 10 mailboxes. + +> [!NOTE] +> Although the _PropertySets_ parameter accepts the value All, we highly discourage using this value to retrieve all properties, because it slows down the command and reduces reliability. Always use the _PropertySets_ and _Properties_ parameters to retrieve the minimum number of properties that are required for your scenario. + +For more information about filtering in the module, see [Filters in the Exchange Online PowerShell module](filters-v2.md). + +## Release notes + +Unless otherwise noted, the current release of the Exchange Online PowerShell module contains all features of previous releases. + +### Current release + +#### Version 3.7.2 + +- The _DisableWAM_ switch is available on the **Connect-ExchangeOnline** cmdlet to disable Web Account Manager (WAM) if you get WAM-related connection errors. + +### Previous releases + +#### Version 3.7.1 + +- Added a new property named `ExoExchangeSecurityDescriptor` to the output of **Get-EXOMailbox** that's similar to the `ExchangeSecurityDescriptor` property in the output of **Get-Mailbox**. +- Added new cmdlets to support the Viva Org Insights Delegation feature: + - **Add-VivaOrgInsightsDelegatedRole** + - **Get-VivaOrgInsightsDelegatedRole** + - **Remove-VivaOrgInsightsDelegatedRole** + +#### Version 3.7.0 + +- Integrated Web Account Manager (WAM) in authentication flows to enhance security. +- Command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ switch in the **Connect-ExchangeOnline** command so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet. +- Fixed connection issues with app only authentication in Security & Compliance PowerShell. + +#### Version 3.6.0 + +- **Get-VivaModuleFeature** now returns information about the kinds of identities that the feature supports creating policies for (for example, users, groups, or the entire tenant). +- Cmdlets for Viva feature access management now handle continuous access evaluation (CAE) claim challenges. +- Added fix for compatibility issue with the Microsoft.Graph module. + +#### Version 3.5.1 + +- Bug fixes in **Get-EXOMailboxPermission** and **Get-EXOMailbox**. +- The module has been upgraded to run on .NET 8, replacing the previous version based on .NET 6. +- Enhancements in **Add-VivaModuleFeaturePolicy**. + +#### Version 3.5.0 + +- New **Get-VivaFeatureCategory** cmdlet. +- Added support for policy operations at the category level in Viva Feature Access Management (VFAM). +- New IsFeatureEnabledByDefault property in the output of **Get-VivaModuleFeaturePolicy**. The value of this property shows the default enablement state for users in the tenant when no tenant or user/group policies were created. + +#### Version 3.4.0 + +- Bug fixes in **Connect-ExchangeOnline**, **Get-EXORecipientPermission**, and **Get-EXOMailboxFolderPermission**. +- The _SigningCertificate_ parameter in **Connect-ExchangeOnline** now supports [Constrained Language Mode (CLM)](/powershell/module/microsoft.powershell.core/about/about_language_modes#constrainedlanguage-mode). + +#### Version 3.3.0 + +- _SkipLoadingCmdletHelp_ parameter on **Connect-ExchangeOnline** to support skip loading cmdlet help files. +- Global variable `EXO_LastExecutionStatus` is available to check the status of the last cmdlet that was run. +- Bug fixes in **Connect-ExchangeOnline** and **Connect-IPPSSession**. +- _IsUserControlEnabled_ parameter on **Add-VivaModuleFeaturePolicy** and **Update-VivaModuleFeaturePolicy** to support the enablement of user controls by policy for features that are onboarded to Viva feature access management. + +#### Version 3.2.0 + +- New cmdlets: + - **Get-DefaultTenantBriefingConfig** and **Set-DefaultTenantBriefingConfig**. + - **Get-DefaultTenantMyAnalyticsFeatureConfig** and **Set-DefaultTenantMyAnalyticsFeatureConfig**. + - **Get-VivaModuleFeature**, **Get-VivaModuleFeatureEnablement**, **Add-VivaModuleFeaturePolicy**, **Get-VivaModuleFeaturePolicy**, **Remove-VivaModuleFeaturePolicy**, and **Update-VivaModuleFeaturePolicy**. +- REST API connection support for Security & Compliance PowerShell. +- _ConnectionId_ parameter on **Get-ConnectionInformation** and **Disconnect-ExchangeOnline**: + - Get connection information for specific REST API connections. + - Selective disconnect for REST API connections. +- _SigningCertificate_ parameter on **Connect-ExchangeOnline** allows you to sign the format files (\*.Format.ps1xml) or script module files (.psm1) in the temporary module that **Connect-ExchangeOnline** creates with a client certificate to use in all PowerShell execution policies. +- Bug fixes in **Connect-ExchangeOnline**. + +#### Version 3.1.0 + +- _AccessToken_ parameter available in **Connect-ExchangeOnline**. +- Bug fixes in **Connect-ExchangeOnline** and **Get-ConnectionInformation**. +- Bug fix in **Connect-IPPSSession** for connecting to Security & Compliance PowerShell using _CertificateThumbprint_. + +#### Version 3.0.0 (Preview versions known as v2.0.6-PreviewX) + +- Features already described in the [REST API connections in the EXO V3 module](#rest-api-connections-in-the-exo-v3-module) section: + - [Certificate based authentication](app-only-auth-powershell-v2.md) for Security & Compliance PowerShell (version 2.0.6-Preview5 or later). + - The [Get-ConnectionInformation](/powershell/module/exchange/get-connectioninformation) cmdlet for REST-based connections (version 2.0.6-Preview7 or later). + - The _SkipLoadingFormatData_ switch on the **Connect-ExchangeOnline** cmdlet for REST-based connections (version 2.0.6-Preview8 or later). +- The _DelegatedOrganization_ parameter works in the **Connect-IPPSSession** cmdlet as long as you also use the _AzureADAuthorizationEndpointUri_ parameter in the command. +- Certain cmdlets that used to prompt for confirmation in specific scenarios no longer do so. By default, the cmdlet runs to completion. +- The format of the error returned from failed cmdlet execution is slightly modified. The exception now contains more data (for example, the exception type), and the `FullyQualifiedErrorId` doesn't contain the `FailureCategory`. The format of the error is subject to further modification. + +#### Version 2.0.5 + +- New **Get-OwnerlessGroupPolicy** and **Set-OwnerlessGroupPolicy** cmdlets to manage ownerless Microsoft 365 groups. + + > [!NOTE] + > Although the _cmdlets_ are available in the module, the _feature_ is only available to members of a Private Preview. + +- New **Get-VivaInsightsSettings** and **Set-VivaInsightsSettings** cmdlets to control user access to Headspace features in Viva Insights. + +#### Version 2.0.4 + +- PowerShell 7 is officially supported in Windows, Linux, and Apple macOS as described in the [Prerequisites for the Exchange Online PowerShell module](#prerequisites-for-the-exchange-online-powershell-module) section in this article. + +- The module in PowerShell 7 supports browser-based single sign-on (SSO) and other sign in methods. For more information, see [PowerShell 7 exclusive connection methods](connect-to-exchange-online-powershell.md#powershell-7-exclusive-connection-methods). + +- The **Get-UserAnalyticsConfig** and **Set-UserAnalyticsConfig** cmdlets were replaced by the **Get-MyAnalyticsConfig** and **Set-MyAnalyticsConfig**. Additionally, you can configure access at feature level. For more information, see [Configure MyAnalytics](/workplace-analytics/myanalytics/setup/configure-myanalytics). + +- Real-time policy and security enforcement in all user based authentication. Continuous Access Evaluation (CAE) is enabled in the module. Read more about CAE [here](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/moving-towards-real-time-policy-and-security-enforcement/ba-p/1276933). + +- The _LastUserActionTime_ and _LastInteractionTime_ properties are now available in the output of the **Get-EXOMailboxStatistics** cmdlet. + +- The interactive sign-in process now uses a more secure method to fetch access tokens using safe reply URLs. + +#### Version 2.0.3 + +- General availability of certificate based authentication (CBA), which enables using modern authentication in unattended scripting or background automation scenarios. The available certificate storage locations are: + - Remote in the Azure Key Value (the _Certificate_) parameter. This option enhances security by fetching the certificate only at runtime. + - Local in the CurrentUser or LocalMachine certificate store (the _CertificateThumbprint_ parameter). + - Local in an exported certificate file (the _CertificateFilePath_ and _CertificatePassword_ parameters). + For more information, see the parameter descriptions in [Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline) and [App-only authentication for unattended scripts in the Exchange Online PowerShell module](app-only-auth-powershell-v2.md). +- Connect to Exchange Online PowerShell and Security & Compliance PowerShell simultaneously in a single PowerShell window. +- The new _CommandName_ parameter allows you to specify and restrict the Exchange Online PowerShell cmdlets that are imported in a session. This option reduces the memory footprint for high usage PowerShell applications. +- **Get-EXOMailboxFolderPermission** now supports ExternalDirectoryObjectID in the _Identity_ parameter. +- Optimized latency of the first V2 cmdlet call. Lab results show the first call latency has been reduced from 8 seconds to approximately 1 second. Actual results depend on the cmdlet result size and the tenant environment. + +#### Version 1.0.1 + +- General Availability (GA) version of the EXO V2 module. It's stable and ready for use in production environments. +- **Get-EXOMobileDeviceStatistics** cmdlet now supports the _Identity_ parameter. +- Improved reliability of session auto-reconnect in certain cases where a script was running for ~50 minutes and threw a "Cmdlet not found" error due to a bug in auto-reconnect logic. +- Fixed data-type issues of two commonly used "User" and "MailboxFolderUser" attributes for easy migration of scripts. +- Enhanced support for filters as it now supports four more operators: EndsWith, Contains, Not and NotLike support. Check [Filters in the Exchange Online PowerShell module](filters-v2.md) for attributes that aren't supported in filters. + +#### Version 0.4578.0 + +- Added support for configuring the Briefing Email for your organization at the user level with **Set-UserBriefingConfig** and **Get-UserBriefingConfig** cmdlets. +- Support for session cleanup using **Disconnect-ExchangeOnline** cmdlet. This cmdlet is the V2 equivalent of `Get-PSSession | Remove-PSSession`. In addition to cleaning up session object and local files, it also removes the access token from cache, which is used for authenticating against V2 cmdlets. +- You can now use `FolderId` as an identity parameter in **Get-EXOMailboxFolderPermission**. You can get the `FolderId` value using **Get-MailboxFolder**. For example: + `Get-MailboxFolderPermission -Identity :` + `Get-MailboxFolderPermission -Identity :\` +- Improved reliability of **Get-EXOMailboxStatistics** as certain request routing errors that led to failures have been resolved. +- Optimized memory usage when a session is created by re-using any existing module with a new session instead of creating a new one every time a session is imported. + +#### Version 0.4368.1 + +- Added support for Security & Compliance PowerShell cmdlets using the **Connect-IPPSSession** cmdlet. +- Hiding the announcement banner is available using the _ShowBanner_ switch (`-ShowBanner:$false`). +- Terminate cmdlet execution on client exception. +- Remote PowerShell contained various complex data types that were intentionally not supported in EXO cmdlets to improve performance. Differences in non-complex data types between remote PowerShell cmdlets and V2 cmdlets have been resolved to allow seamless migration of management scripts. + +#### Version 0.3582.0 + +- Support for prefix during session creation: + - You can create only one session at a time that contains prefixed cmdlets. + - EXO V2 cmdlets aren't prefixed because they already have the prefix EXO, so don't use `EXO` as a prefix. +- Use EXO V2 cmdlets even if WinRM Basic Auth is disabled on client machine. Remote PowerShell connections require WinRM Basic Auth, and remote PowerShell cmdlets aren't available if Basic Auth is disabled in WinRM. +- Identity parameter for V2 cmdlets now supports Name and Alias. Using Alias or Name slows down the performance of V2 cmdlets, so we don't recommend using them. +- Fixed issue where the data type of attributes returned by V2 cmdlet was different from remote PowerShell cmdlets. We still have few attributes with differing data types, and we plan to handle them in coming months. +- Fixed bug: Frequent sessions reconnect issue when Connect-ExchangeOnline was invoked with Credentials or UserPrincipalName + +#### Version 0.3555.1 + +- Fixed a bug where piped cmdlets were failing with the following error due to an authentication issue: + > Cannot invoke the pipeline because the runspace isn't in the Opened state. Current state of the runspace is 'Closed'. + +#### Version 0.3527.4 + +- Updated Get-Help content. +- Fixed an issue in **Get-Help** where the _Online_ parameter was redirecting to a nonexistent page with error code 400. + +#### Version 0.3527.3 + +- Added support for managing Exchange for a different tenant using delegation flow. +- Works in tandem with other PowerShell modules in a single PowerShell window. +- Added support for positional parameters. +- Date Time field now supports client locale. +- Bug fix: PSCredential empty when passed during Connect-ExchangeOnline. +- Bug fix: Client module error when filter contained $null. +- Sessions created internal to EXO V2 Module now have names (naming pattern: ExchangeOnlineInternalSession_%SomeNumber%). +- Bug fix: Remote PowerShell cmdlets intermittently failing due to time the difference between token expiry and the Session going idle. +- Major security update. +- Bug fixes and enhancements. diff --git a/exchange/docs-conceptual/exchange-online-powershell.md b/exchange/docs-conceptual/exchange-online-powershell.md new file mode 100644 index 0000000000..348084ae8d --- /dev/null +++ b/exchange/docs-conceptual/exchange-online-powershell.md @@ -0,0 +1,46 @@ +--- +title: "Exchange Online PowerShell" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 05/07/2025 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: 1cb603b0-2961-4afe-b879-b048fe0f64a2 +search.appverid: MET150 +description: "Learn about articles that are available for using PowerShell in Exchange Online." +--- + +# Exchange Online PowerShell + +Exchange Online PowerShell is the administrative interface that enables you to manage the Exchange Online part of your Microsoft 365 organization from the command line (including many security features in Exchange Online Protection and Microsoft Defender for Office 365). For example, you can use Exchange Online PowerShell to configure mail flow rules (also known as transport rules) and connectors. The following articles provide information about using Exchange Online PowerShell: + +- To learn about the ExchangeOnlineManagement module that's required to connect to Exchange Online PowerShell, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). + + > [!TIP] + > Version 3.0.0 and later (2022) is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module). Version 2.0.5 and earlier (2021) was known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). + + To learn about what's new in the Exchange Online PowerShell module, see [What's new in the Exchange Online PowerShell module](whats-new-in-the-exo-module.md). + +- To connect to Exchange Online PowerShell, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md). + + To learn about different methods to connect to Exchange Online PowerShell, see the following articles: + + - [App-only authentication for unattended scripts in the Exchange Online PowerShell module](app-only-auth-powershell-v2.md). + - [Use Azure managed identities to connect to Exchange Online PowerShell](connect-exo-powershell-managed-identity.md). + - [Use C# to connect to Exchange Online PowerShell](connect-to-exo-powershell-c-sharp.md) + +- To block or allow access to Exchange Online PowerShell in your organization, see [Enable or disable access to Exchange Online PowerShell](disable-access-to-exchange-online-powershell.md). + +- To learn about the structure and layout of the cmdlet reference articles in Exchange Online PowerShell, see [Exchange cmdlet syntax](exchange-cmdlet-syntax.md). + +- To find the permissions that you need to run a specific cmdlet, or one or more parameters on a cmdlet, see [Find the permissions required to run any Exchange cmdlet](find-exchange-cmdlet-permissions.md). + +- To learn about recipient filters in Exchange Online PowerShell, see [Recipient filters in Exchange Management Shell and Exchange Online PowerShell commands](recipient-filters.md). + +- To learn about recipient filters for the nine exclusive **Get-EXO\*** cmdlets in the Exchange Online PowerShell, see [Filters in the Exchange Online PowerShell module](filters-v2.md). + +- To learn about property sets in the nine exclusive **Get-EXO\*** cmdlets in the Exchange Online PowerShell module, see [Property sets in Exchange Online PowerShell module cmdlets](cmdlet-property-sets.md). diff --git a/exchange/docs-conceptual/exchange-online-protection-powershell.md b/exchange/docs-conceptual/exchange-online-protection-powershell.md new file mode 100644 index 0000000000..93e9dd4bf7 --- /dev/null +++ b/exchange/docs-conceptual/exchange-online-protection-powershell.md @@ -0,0 +1,39 @@ +--- +title: "Exchange Online Protection PowerShell" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/1/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: f7918a88-774a-405e-945b-bc2f5ee9f748 +description: "Learn about the articles that are available for using PowerShell in Exchange Online Protection (EOP) only organizations without cloud mailboxes." +--- + +# Exchange Online Protection PowerShell + +Exchange Online Protection PowerShell is the administrative interface that enables you to manage security features in Exchange Online Protection (EOP) organizations from the command line. For example, you can use Exchange Online Protection PowerShell to configure anti-spam policies, mail flow rules (also known as transport rules) and connectors. + +> [!TIP] +> Microsoft 365 organizations with cloud mailboxes (Microsoft 365 A3/E3/G3, A5/E5/G5, Microsoft 365 Business Premium, etc.) use [Exchange Online PowerShell](exchange-online-powershell.md) to manage these same features. + +Exchange Online Protection PowerShell includes the following environments: + +- **Standalone EOP organizations**: Your Microsoft 365 subscription includes no Exchange Online mailboxes, because you use EOP to protect your on-premises email environment. +- **Exchange Enterprise CAL with Services**: The licenses for your on-premises Exchange organization include Exchange Enterprise CAL with Services (EOP is one of the services). + +The following articles provide information about using Exchange Online Protection PowerShell: + +- To learn about the ExchangeOnlineManagement module that's required to connect to standalone Exchange Online Protection PowerShell, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). + + > [!TIP] + > Version 3.0.0 and later (2022) is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module). Version 2.0.5 and earlier (2021) was known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). + + To learn about what's new in the Exchange Online PowerShell module, see [What's new in the Exchange Online PowerShell module](whats-new-in-the-exo-module.md). + +- To connect to Exchange Online Protection PowerShell, see [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md). + +- To learn about the structure and layout of the cmdlet reference articles in Exchange Online Protection PowerShell, see [Exchange cmdlet syntax](exchange-cmdlet-syntax.md). diff --git a/exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md b/exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md deleted file mode 100644 index 64bc6170fb..0000000000 --- a/exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -title: "Connect to Exchange Online PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: 7/10/2017 -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -localization_priority: Priority -ms.collection: Strat_EX_Admin -ms.custom: -ms.assetid: c8bea338-6c1a-4bdf-8de0-7895d427ee5b -search.appverid: MET150 -description: "Learn how to use remote PowerShell to connect to Exchange Online." ---- - -# Connect to Exchange Online PowerShell - -Exchange Online PowerShell allows you to manage your Exchange Online settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Exchange Online. It's a simple three-step process where you enter your Office 365 credentials, provide the required connection settings, and then import the Exchange Online cmdlets into your local Windows PowerShell session so that you can use them. - -> [!IMPORTANT] -> If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you need to download and use the Exchange Online Remote PowerShell Module. For more information, see [Connect to Exchange Online PowerShell using multi-factor authentication](mfa-connect-to-exchange-online-powershell.md).

If you're a standalone Exchange Online Protection (EOP) customer (for example, you're using EOP to protect your on-premises email environment), use the connection instructions in [Connect to Exchange Online Protection PowerShell](../../exchange-eop/connect-to-exchange-online-protection-powershell.md). If your standalone EOP subscription is Exchange Enterprise CAL with Services (includes data loss prevention (DLP) and reporting using web services), the connection instructions in this topic will work for you. - -## What do you need to know before you begin? - -- Estimated time to complete: 5 minutes - -- You can use the following versions of Windows: - - - Windows 10 - - - Windows 8.1 - - - Windows Server 2019 - - - Windows Server 2016 - - - Windows Server 2012 or Windows Server 2012 R2 - - - Windows 7 Service Pack 1 (SP1)* - - - Windows Server 2008 R2 SP1* - - \* This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868), [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757), [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). - -- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You'll get the following error when you try to connect: - - `Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.` - - To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**): - - ```PowerShell - Set-ExecutionPolicy RemoteSigned - ``` - - You need to configure this setting only once on your computer, not every time you connect. - -- Windows Remote Management (WinRM) on your computer needs to allow Basic authentication (it's enabled by default). To verify that Basic authentication is enabled, run this command **in a Command Prompt**: - - ``` - winrm get winrm/config/client/auth - ``` - - If you don't see the value `Basic = true`, you need to run this command to enable Basic authentication for WinRM: - - ``` - winrm set winrm/config/client/auth @{Basic="true"} - ``` - - If Basic authentication is disabled, you'll get this error when you try to connect: - - `The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.` - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). - -> [!IMPORTANT] -> On October 13th, 2020 we will retire Basic Authentication for Remote PowerShell (RPS) in Exchange Online. - -## Connect to Exchange Online - -1. On your local computer, open Windows PowerShell and run the following command. - - ```PowerShell - $UserCredential = Get-Credential - ``` - - In the **Windows PowerShell Credential Request** dialog box, type your work or school account and password, and then click **OK**. - -2. Run the following command: - - ```PowerShell - $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection - ``` - - **Notes**: - - - For Office 365 operated by 21Vianet, use the _ConnectionUri_ value: `https://partner.outlook.cn/PowerShell` - - - For Office 365 Germany, use the _ConnectionUri_ value: `https://outlook.office.de/powershell-liveid/` - - - For Office 365 Government Community Cloud High (GCC High), use the _ConnectionUri_ value: `https://outlook.office365.us/powershell-liveid/` - - - If you're behind a proxy server, run this command first: `$ProxyOptions = New-PSSessionOption -ProxyAccessType `, where the _ProxyAccessType_ value is `IEConfig`, `WinHttpConfig`, or `AutoDetect`. - - Then, add the following parameter and value to the end of the $Session = ... command: `-SessionOption $ProxyOptions`. - - For more information, see [New-PSSessionOption](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/new-pssessionoption). - -3. Run the following command: - - ```PowerShell - Import-PSSession $Session -DisableNameChecking - ``` - -> [!NOTE] -> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command. - -```PowerShell -Remove-PSSession $Session -``` - -## How do you know this worked? - -After Step 3, the Exchange Online cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange Online cmdlet, for example, **Get-Mailbox**, and see the results. - -If you receive errors, check the following requirements: - -- A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1. - -- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online organization. - -- The account you use to connect to Exchange Online must be enabled for remote PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](../disable-access-to-exchange-online-powershell.md). - -- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive internet access policy. - -- If your organization uses federated authentication, and your identity provider (IDP) and/or security token service (STS) isn't publicly available, you can't use a federated account to connect to Exchange Online PowerShell. Instead, create and use a non-federated account in Office 365 to connect to Exchange Online PowerShell. - -## See also - -The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics. - -- [Get-Credential](https://go.microsoft.com/fwlink/p/?LinkId=389618) - -- [New-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389621) - -- [Import-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389619) - -- [Remove-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389620) - -- [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623) - -For more information about managing Office 365, see [Manage Office 365](https://docs.microsoft.com/Office365/). diff --git a/exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md b/exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md deleted file mode 100644 index b49619da98..0000000000 --- a/exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -title: "Connect to Exchange Online PowerShell using multi-factor authentication" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -localization_priority: Normal -ms.assetid: 04dae4ce-34a7-49c5-bf75-11e72452e04a -search.appverid: MET150 -description: "Learn how to connect to Exchange Online PowerShell by using multi-factor authentication (MFA)." ---- - -# Connect to Exchange Online PowerShell using multi-factor authentication - -If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you can't use the instructions at [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md) to use remote PowerShell to connect to Exchange Online. MFA requires you to install the Exchange Online Remote PowerShell Module, and use the **Connect-EXOPSSession** cmdlet to connect. - -> [!NOTE] -> The Exchange Online Remote PowerShell Module is not supported in PowerShell Core (macOS, Linux, or Windows Nano Server). As a workaround, you can install the module on a computer that's running a supported version of Windows (physical or virtual), and use remote desktop software to connect.

To use the new Exchange Online PowerShell V2 module (which also supports MFA), see [Use the Exchange Online PowerShell V2 module](../exchange-online-powershell-v2/exchange-online-powershell-v2.md).) - -## What do you need to know before you begin? - -- Estimated time to complete: 5 minutes - -- You can use the following versions of Windows: - - - Windows 10 - - - Windows 8.1 - - - Windows Server 2019 - - - Windows Server 2016 - - - Windows Server 2012 or Windows Server 2012 R2 - - - Windows 7 Service Pack 1 (SP1)* - - - Windows Server 2008 R2 SP1* - - \* This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868), [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757), [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). - -- The Exchange Online Remote PowerShell Module needs to be installed on your computer. You need to do the following steps in a browser that supports ClickOnce (for example, Internet Explorer or Edge): - - **Note**: ClickOnce support is available in the Chromium-based version of Edge at , and might not be enabled by default. - - 1. Open the Exchange admin center (EAC) for your Exchange Online organization. For instructions, see [Exchange admin center in Exchange Online](https://docs.microsoft.com/exchange/exchange-admin-center). - - 2. In the EAC, go to **Hybrid** > **Setup** and click the appropriate **Configure** button to download the Exchange Online Remote PowerShell Module for multi-factor authentication. - - ![Download the Exchange Online PowerShell Module from the Hybrid tab in the EAC](../../media/24645e56-8b11-4c0f-ace4-09bdb2703562.png) - - 3. In the **Application Install** window that opens, click **Install**. - - ![Click Install in the Exchange Online PowerShell Module window](../../media/0fd389a1-a32d-4e2f-bf5f-78e9b6407d4c.png) - -- Windows Remote Management (WinRM) on your computer needs to allow Basic authentication (it's enabled by default). To verify that Basic authentication is enabled, run this command **in a Command Prompt**: - - ``` - winrm get winrm/config/client/auth - ``` - - > [!NOTE] - > The Basic authentication header is required to transport the session's OAuth token, since the client-side WinRM implementation has no support for OAuth. - - If you don't see the value `Basic = true`, you need to run this command to enable Basic authentication for WinRM: - - ``` - winrm set winrm/config/client/auth @{Basic="true"} - ``` - - If Basic authentication is disabled, you'll get this error when you try to connect: - - > The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again. - -- When you use the Exchange Online Remote PowerShell Module, your session will end after one hour, which can be problematic for long-running scripts or processes. To avoid this issue, use [Trusted IPs](https://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-mfasettings#trusted-ips) to bypass MFA for connections from your intranet. Trusted IPs allow you to connect to Exchange Online PowerShell from your intranet using the old instructions at [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md). Also, if you have servers in a datacenter, be sure to add their public IP addresses to Trusted IPs as described [here](https://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-mfasettings#enable-the-trusted-ips-feature-by-using-service-settings). - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542) or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). - -## Connect to Exchange Online PowerShell by using MFA - -1. On your local computer, open the **Exchange Online Remote PowerShell Module** ( **Microsoft Corporation** > **Microsoft Exchange Online Remote PowerShell Module**). - -2. The command that you need to run uses the following syntax: - - ```PowerShell - Connect-EXOPSSession [-UserPrincipalName -ConnectionUri -AzureADAuthorizationEndPointUri -DelegatedOrganization ] - ``` - - - _\_ is your Office 365 work or school account. - - - The _\_ and _\_ values depend on the nature of your Office 365 organization as described in the following table: - - |**Office 365 offering**|**_ConnectionUri_ parameter value**|**_AzureADAuthorizationEndPointUri_ parameter value**| - |:-----|:-----|:-----| - |Office 365|Not used|Not used| - |Office 365 Germany|`https://outlook.office.de/PowerShell-LiveID`|`https://login.microsoftonline.de/common`| - |Office 365 GCC High|`https://outlook.office365.us/powershell-liveid`|`https://login.microsoftonline.us/common`| - |Office 365 DoD|`https://webmail.apps.mil/powershell-liveid`|`https://login.microsoftonline.us/common`| - - This example connects to Exchange Online in Office 365 using the account chris@contoso.com. - - ```PowerShell - Connect-EXOPSSession -UserPrincipalName chris@contoso.com - ``` - - This example connects to Exchange Online in Office 365 Germany using the account lukas@fabrikam.com. - - ```PowerShell - Connect-EXOPSSession -UserPrincipalName lukas@fabrikam.com -ConnectionUri https://outlook.office.de/PowerShell-LiveID -AzureADAuthorizationEndPointUri https://login.microsoftonline.de/common - ``` - - This example connects to Exchange Online to manage another tenant. - - ```PowerShell - Connect-EXOPSSession -UserPrincipalName chris@contoso.com -DelegatedOrganization fabrikam.onmicrosoft.com - ``` - -3. In the sign-in window that opens, enter your password, and then click **Sign in**. - - ![Enter your password in the Exchange Online Remote PowerShell window](../../media/b85d80d9-1043-4c7c-8f14-d87d8d56b188.png) - - A verification code is generated and delivered based on the verification response option that's configured for your account (for example, a text message or the Azure Authenticator app on your mobile phone). - -4. In the verification window that opens, enter the verification code, and then click **Sign in**. - - ![Enter your verification code in the Exchange Online Remote PowerShell window](../../media/d3a405ce-5364-4732-a7bb-2cc9c678da2d.png) - -> [!NOTE] -> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Exchange Online Remote PowerShell Module window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect all currently open PowerShell sessions in the current window, run the following command: - -```PowerShell -Get-PSSession | Remove-PSSession -``` - -## Single sign-on - -If your organization has single sign-on (SSO) enabled and you are logged on to a computer as a user in the SSO domain, then **Connect-EXOPSSession** may fail with the following error: - -> New-EXOPSSession : User 'loggedonuser@contoso.com' returned by service does not match user 'userprincipalname@contoso.com' in the request. - -This error occurs because single sign-on overrides the specified user principal name (UPN). As a work-around, use Connect-EXOPSSession without -UserPrincipalName parameter or use -Credential parameter instead. - -## How do you know this worked? - -After Step 4, the Exchange Online cmdlets are imported into your Exchange Online Remote PowerShell Module session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange Online cmdlet, for example, **Get-Mailbox**, and see the results. - -If you receive errors, check the following requirements: - -- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online organization. - -- The account you use to connect to Exchange Online must be enabled for remote PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](../disable-access-to-exchange-online-powershell.md). - -- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy. diff --git a/exchange/docs-conceptual/exchange-online/disable-access-to-exchange-online-powershell.md b/exchange/docs-conceptual/exchange-online/disable-access-to-exchange-online-powershell.md deleted file mode 100644 index 574c34c14d..0000000000 --- a/exchange/docs-conceptual/exchange-online/disable-access-to-exchange-online-powershell.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -title: "Enable or disable access to Exchange Online PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -localization_priority: Normal -ms.assetid: f969816a-2607-4655-9d47-9e8767fb5633 -search.appverid: MET150 -description: "Admins can learn how to enable or disable access to Exchange Online PowerShell for users in their organization" ---- - -# Enable or disable access to Exchange Online PowerShell - -Exchange Online PowerShell enables you to manage your Exchange Online organization from the command line. By default, all accounts you create in Office 365 are allowed to use Exchange Online PowerShell. Administrators can use Exchange Online PowerShell to enable or disable a user's ability to connect to Exchange Online PowerShell. Note that access to Exchange Online PowerShell doesn't give users extra administrative powers in your organization. A user's capabilities in Exchange Online PowerShell are still defined by role based access control (RBAC) and the roles that are assigned to them. - -## What do you need to know before you begin? - -- Estimated time to complete each procedure: less than 5 minutes - -- Office 365 global admins have access to Exchange Online PowerShell, and can use the procedures in this topic to configure Exchange Online PowerShell access for other users. For more information about permissions in Exchange Online, see [Feature Permissions in Exchange Online](https://docs.microsoft.com/exchange/permissions-exo/feature-permissions). - -- You can only use Exchange Online PowerShell to perform this procedure. To learn how to use Windows PowerShell to connect to Exchange Online, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md). - -- For detailed information about OPath filter syntax in Exchange Online, see [Additional OPATH syntax information](../exchange-server/recipient-filters/recipient-filters.md#additional-opath-syntax-information). - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). - -## Enable or disable access to Exchange Online PowerShell for a user - -This example disables access to Exchange Online PowerShell for the user david@contoso.com. - -```PowerShell -Set-User -Identity david@contoso.com -RemotePowerShellEnabled $false -``` - -This example enables access to Exchange Online PowerShell for the user david@contoso.com. - -```PowerShell -Set-User -Identity david@contoso.com -RemotePowerShellEnabled $true -``` - -## Disable access to Exchange Online PowerShell for many users - -To prevent access to Exchange Online PowerShell for a specific group of existing users, you have the following options: - -- **Filter users based on an existing attribute**: This method assumes that the target user accounts all share a unique filterable attribute. Some attributes, such as Title, Department, address information, and telephone number, are visible only when you use the **Get-User** cmdlet. Other attributes, such as CustomAttribute1-15, are visible only when you use the **Get-Mailbox** cmdlet. - -- **Use a list of specific users**: After you generate the list of specific users, you can use that list to disable their access to Exchange Online PowerShell. - -### Filter users based on an existing attribute - -To disable access to Exchange Online PowerShell for any number of users based on an existing attribute, use the following syntax: - -```PowerShell -$ = -ResultSize unlimited -Filter -``` - -```PowerShell -$ | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false} -``` - -This example removes access to Exchange Online PowerShell for all users whose **Title** attribute contains the value "Sales Associate". - -```PowerShell -$DSA = Get-User -ResultSize unlimited -Filter "(RecipientType -eq 'UserMailbox') -and (Title -like '*Sales Associate*')" -``` - -```PowerShell -$DSA | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false} -``` - -### Use a list of specific users - -To disable access to Exchange Online PowerShell for a list of specific users, use the following syntax: - -```PowerShell -$ = Get-Content -``` - -```PowerShell -$ | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false} -``` - -This example uses the text file C:\My Documents\NoPowerShell.txt to identify the users by their accounts. The text file must contain one account on each line as follows: - -> akol@contoso.com
tjohnston@contoso.com
kakers@contoso.com - -After you populate the text file with the user accounts you want to update, run the following commands: - -```PowerShell -$NPS = Get-Content "C:\My Documents\NoPowerShell.txt" -``` - -```PowerShell -$NPS | foreach {Set-User -Identity $_.MicrosoftOnlineServicesID -RemotePowerShellEnabled $false} -``` - -## View the Exchange Online PowerShell access for users - -To view the Exchange Online PowerShell access status for a specific user, use the following syntax: - -```PowerShell -Get-User -Identity | Format-List RemotePowerShellEnabled -``` - -This example displays the Exchange Online PowerShell access status of the user named Sarah Jones. - -```PowerShell -Get-User -Identity "Sarah Jones" | Format-List RemotePowerShellEnabled -``` - -To display the Exchange Online PowerShell access status for all users, run the following command: - -```PowerShell -Get-User -ResultSize unlimited | Format-Table -Auto Name,DisplayName,RemotePowerShellEnabled -``` - -To display only those users who don't have access to Exchange Online PowerShell, run the following command: - -```PowerShell -Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $false' -``` - -To display only those users who have access to Exchange Online PowerShell, run the following command: - -```PowerShell -Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $true' -``` diff --git a/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/app-only-auth-powershell-v2.md b/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/app-only-auth-powershell-v2.md deleted file mode 100644 index e59593ae30..0000000000 --- a/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/app-only-auth-powershell-v2.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -title: App-only authentication -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -ms.reviewer: navgupta -localization_priority: Priority -ms.collection: Strat_EX_Admin -ms.custom: -ms.assetid: -search.appverid: MET150 -robots: noindex,nofollow -description: "Learn about using the Exchange Online V2 module in scripts and other long-running tasks." ---- - -# Automate tasks in Exchange Online using PowerShell (Preview) - -> [!NOTE] -> The features described in this topic are in Preview, are not available to everyone, and are subject to change. - -Auditing and reporting scenarios in Exchange Online often involve scripts that run unattended. In most cases, these unattended scripts access Exchange Online PowerShell using Basic authentication (a username and password). Even when the connection to Exchange Online PowerShell uses Modern authentication, the credentials are stored in a local file or a secret vault that's access at run-time. - -Because storing user credentials locally is not a good security practice, we're releasing this feature to support authentication for app-only scenarios using AzureAD applications and self-signed certificates. - -The following examples show how to use the Exchange Online PowerShell V2 module with app-only authentication - -- Connect using a local certificate: - - ```powershell - Connect-ExchangeOnline -CertificateFilePath "C:\Users\johndoe\Desktop\automation-cert.pfx" -AppID "alpha-beta-gamma-123456" -TenantID "contosoelectronics.onmicrosoft.com" - ``` - -- Connect using a certificate thumbprint: - - ```powershell - Connect-ExchangeOnline -CertificateThumbPrint "012THISISADEMOTHUMBPRINT" -AppID "alpha-beta-gamma-123456" -TenantID "contosoelectronics.onmicrosoft.com" -RoutingHintUPN "admin_exo@contosoelectronics.com" - ``` - When you use the _CertificateThumbPrint_ parameter, the certificate needs to be installed on the computer where you are running the command. The certificate should be installed in the user certificate store. - -- Connect using an existing service principal and client-secret: - - 1. Get an OAuth access token using Active Directory Authentication Library (ADAL) PowerShell. - - 2. Use the access token and username to create a PSCredential object: - - ```powershell - $AppCredential = New-Object System.Management.Automation.PSCredential(,) - ``` - - 3. Silently pass the PSCredential object to the EXO V2 module: - - ```powershell - Connect-ExchangeOnline -Credential $AppCredential - ``` - -## How does it work? - -The EXO V2 module uses the Active Directory Authentication Library to fetch an app-only token using the application Id, tenant Id & certificate thumbprint. The application object provisioned inside Azure AD has a Directory Role assigned to it, which is returned in the access token. Exchange Online configures the session RBAC using the directory role information that's available in the token. - -## Setup app-only authentication - -An initial onboarding is required for authentication using application objects. Application and service principal are used interchangeably, but an application is like a class object while a service principal is like an instance of the class. You can learn more about this at [Application and service principal objects in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/develop/app-objects-and-service-principals). - -For a detailed visual flow bout creating applications in Azure AD, see . - -1. Register the application in Azure AD at . - -2. Assign permissions to access Exchange Online. - - An application object has the default permission `User.Read`. For the application object to access Exchange Online resources, it needs to have the Application permission `Exchange.ManageAsApp`. - -3. Attach a certificate. - - - For app-only authentication in Azure AD, you typically use a certificate to request access. Anyone who has the certificate and its private key can use the app, and the permissions granted to the app. - - - Create and configure a self-signed X.509 certificate, which will be used to authenticate your Application against Azure AD, while requesting the app-only access token. - - - This is similar to generating a password for user accounts. The certificate can be self-signed as well. See the [Appendix](#appendix) section later in this topic for instructions for generating certificates in PowerShell. - -4. Assign RBAC roles - - The application needs to have the appropriate RBAC roles assigned. Because the apps are provisioned in Azure AD, you can use any of the built-in roles. The following roles are supported: - - - Global administrator - - Compliance administrator - - Security reader - - Security administrator - - Helpdesk administrator - -## Appendix - -## Step 1: Application registration in Azure AD - -If you encounter problems, check the [required permssions](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#required-permissions) to verify that your account can create the identity. - -1. Go to the Azure AD portal at and sign in with your Azure AD account. - -2. Under **Manage Azure Active Directory**, click **View**. - -3. Under **Manage**, select **App registrations** and then click **New registration**. - -4. In the **Register an application** page that appears, configure the following settings: - - - **Name**: Enter something descriptive. - - - **Supported account types**: Select **Accounts in this organizational directory only (Microsoft)**. - - - **Redirect URI (optional)**: In the first box, select **Web**. In the second box, enter the URI where the access token is sent. - - Note that you can't create credentials for [native applications](https://docs.microsoft.com/azure/active-directory/manage-apps/application-proxy-configure-native-client-application), because you can't use that type for automated applications. - - ![Register an application](../../media/app-only-auth-register-app.png) - - When you're finished, click **Register**. - - Leave the page that appears open. You'll use it in the next step. - -## Step 2: Assign API permissions to the application - -You need to assign the API permission `Exchange.ManageAsApp` so the application can manage Exchange Online. API permissions are required because they have consent flow enabled, which allows auditing (directory roles don't have consent flow). - -1. Select **API permissions**. - -2. In the **Configured permissions** page that appears, click **Add permission**. - -3. In the flyout that appears, select **Exchange**. - - ![Select Exchange API permssions](../../media/app-only-auth-exchange-api-perms.png) - -4. In the flyout that appears, click **Application permissions**. - -5. In the **Select permissions** section that appears on the page, expand **Exchange** and select **Exchange.ManageAsApp** - - ![Select Exchange API permssions](../../media/app-only-auth-exchange-manageasapp.png) - - When you're finished, click **Add permissions**. - -6. Back on the **Configured permissions** page that appears, click **Grant admin consent for <\tenant name\>**, and select **Yes** in the dialog that appears. - -7. Close the flyout when you're finished. - -## Step 3: Generate a self-signed certificate - -Create a self-signed x.509 certificate using one of the following methods: - -- Use the [Create-SelfSignedCertificate script](https://github.com/SharePoint/PnP-Partner-Pack/blob/master/scripts/Create-SelfSignedCertificate.ps1): - - ```powershell - .\Create-SelfSignedCertificate.ps1 -CommonName "MyCompanyName" -StartDate 2020-04-01 -EndDate 2022-04-01 - ``` - -- Use the **makecert.exe** tool from the Windows SDK. - -## Step 4: Attach the certificate to the Azure AD application - -After you register the certificate with your application, you can use the public key (.pfx file) or the thumbprint for authentication. - -1. In the Azure AD portal under **Manage Azure Active Directory**, click **View**. - -2. Under **Manage**, select **App registrations**. - -3. On the **App registrations** page that appears, select your application. - -4. Under **Manage**, select **Certificates & secrets**. - -5. On the **Certificates & secrets** page that opens, click **Upload certificate**. - - ![Click Upload certificate](../../media/app-only-auth-upload-cert.png) - -6. In the dialog that appears, browse to the self-signed certificate you created in the previous Step, and then click **Add**. - -## Step 5: Assign a role to the application - -Azure AD has more than 50 admin roles available. For app-only authentication in Exchange Online, we currently support the previously mentioned roles: - -- Global administrator -- Compliance administrator -- Security reader -- Security administrator -- Helpdesk administrator - -1. In the Azure AD portal under **Manage Azure Active Directory**, click **View**. - -2. Under **Manage**, select **Roles and administrators**. - -3. Select one of the supported roles. On the **Assignments** page that appears, click **Add assignments** - -4. In the **Add assignments** flyout that appears, find and select the application, and then click **Add**. - - ![Add a role assignment](../../media/app-only-auth-role-assignment.png) diff --git a/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets.md b/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets.md deleted file mode 100644 index 153b931c39..0000000000 --- a/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Property sets in Exchange Online PowerShell V2 cmdlets -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -ms.reviewer: navgupta -localization_priority: Priority -ms.collection: Strat_EX_Admin -ms.custom: -ms.assetid: -search.appverid: MET150 -description: "Learn about the available property sets in the Exchange Online PowerShell V2 module." ---- - -# Property sets in Exchange Online PowerShell V2 cmdlets - -This topic describes the property sets that are available in the new cmdlets in the [Exchange Online PowerShell V2 module](exchange-online-powershell-v2.md). For more information about property sets, see [Properties and property sets in the EXO V2 module](exchange-online-powershell-v2.md#properties-and-property-sets-in-the-exo-v2-module). - -## Get-EXOCasMailbox property sets - -The available property sets for the **Get-EXOCasMailbox** cmdlet and the properties they contain are described in the following table: - -||| -|:-----|:-----| -|**PropertySet**|**Properties**| -|**Minimum**|ActiveSyncEnabled
DisplayName
ECPEnabled
EmailAddresses
EwsEnabled
ExchangeVersion
Guid
Identity
ImapEnabled
MAPIEnabled
Name
OWAEnabled
OrganizationId
PopEnabled
PrimarySmtpAddress
ServerLegacyDN| -|**ActiveSync**|ActiveSyncAllowedDeviceIDs
ActiveSyncBlockedDeviceIDs
ActiveSyncEnabled
ActiveSyncMailboxPolicy
ActiveSyncMailboxPolicyIsDefaulted
ActiveSyncSuppressReadReceipt
ExternalDirectoryObjectId
Guid
HasActiveSyncDevicePartnership
Identity
Name
OrganizationId| -|**Ews**|EwsAllowMacOutlook
EwsAllowOutlook
EwsEnabled
ExternalDirectoryObjectId
Guid
Identity
Name
OrganizationId| -|**Imap**|ExternalDirectoryObjectId
Guid
Identity
ImapEnableExactRFC822Size
ImapEnabled
ImapForceICalForCalendarRetrievalOption
ImapMessagesRetrievalMimeFormat
ImapSuppressReadReceipt
ImapUseProtocolDefaults
Name
OrganizationId| -|**Mapi**|ExternalDirectoryObjectId
Guid
Identity
MAPIBlockOutlookExternalConnectivity
MAPIBlockOutlookNonCachedMode
MAPIBlockOutlookRpcHttp
MAPIBlockOutlookVersions
MAPIEnabled
MapiHttpEnabled
Name
OrganizationId| -|**Pop**|ExternalDirectoryObjectId
Guid
Identity
Name
OrganizationId
PopEnableExactRFC822Size
PopEnabled
PopMessagesRetrievalMimeFormat
PopSuppressReadReceipt
PopUseProtocolDefaults| -|**ProtocolSettings**|ExternalDirectoryObjectId
ExternalImapSettings
ExternalPopSettings
ExternalSmtpSettings
Guid
Identity
InternalImapSettings
InternalPopSettings
InternalSmtpSettings
Name
OrganizationId| - -**Note**: The following **Get-CasMailbox** parameters aren't available on **Get-EXOCasMailbox**: - -- *ActiveSyncDebugLogging* - -- *IgnoreDefaultScope* - -- *ReadIsOptimizedForAccessibility* - -- *SortBy* - -For more information, see: - -- [Get-EXOCASMailbox](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exocasmailbox) - -- [Get-CASMailbox](https://docs.microsoft.com/powershell/module/exchange/client-access/get-casmailbox) - -## Get-EXOMailbox property sets - -The available property sets for the **Get-EXOMailbox** cmdlet and the properties they contain are described in the following table: - -||| -|:-----|:-----| -|**PropertySet**|**Properties**| -|**Minimum**|Alias
DisplayName
DistinguishedName
EmailAddresses
ExchangeVersion
ExternalDirectoryObjectId
Guid
Id
Name
OrganizationId
PrimarySmtpAddress
RecipientType
RecipientTypeDetails
UserPrincipalName| -|**AddressList**|AddressBookPolicy
AddressListMembership
ExternalDirectoryObjectId
GeneratedOfflineAddressBooks
HiddenFromAddressListsEnabled
OfflineAddressBook| -|**Archive**|ArchiveDatabase
ArchiveDomain
ArchiveGuid
ArchiveName
ArchiveQuota
ArchiveRelease
ArchiveState
ArchiveStatus
ArchiveWarningQuota
AutoExpandingArchiveEnabled
DisabledArchiveDatabase
DisabledArchiveGuid
ExternalDirectoryObjectId
JournalArchiveAddress| -|**Audit**|AuditAdmin
AuditDelegate
AuditEnabled
AuditLogAgeLimit
AuditOwner
DefaultAuditSet
ExternalDirectoryObjectId| -|**Custom**|CustomAttribute1
CustomAttribute2
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute1
ExtensionCustomAttribute2
ExtensionCustomAttribute3
ExtensionCustomAttribute4
ExtensionCustomAttribute5
ExternalDirectoryObjectId| -|**Delivery**|AcceptMessagesOnlyFrom
AcceptMessagesOnlyFromDLMembers
AcceptMessagesOnlyFromSendersOrMembers
DeliverToMailboxAndForward
DowngradeHighPriorityMessagesEnabled
ExternalDirectoryObjectId
ForwardingAddress
ForwardingSmtpAddress
GrantSendOnBehalfTo
MaxBlockedSenders
MaxReceiveSize
MaxSafeSenders
MaxSendSize
MessageCopyForSendOnBehalfEnabled
MessageCopyForSentAsEnabled
MessageRecallProcessingEnabled
MessageTrackingReadStatusEnabled
RecipientLimits
RejectMessagesFrom
RejectMessagesFromDLMembers
RejectMessagesFromSendersOrMembers
RulesQuota| -|**Hold**|ComplianceTagHoldApplied
DelayHoldApplied
ExternalDirectoryObjectId
InPlaceHolds
InactiveMailboxRetireTime
LitigationHoldDate
LitigationHoldDuration
LitigationHoldEnabled
LitigationHoldOwner| -|**Moderation**|BypassModerationFromSendersOrMembers
ExternalDirectoryObjectId
ModeratedBy
ModerationEnabled
SendModerationNotifications| -|**Move**|ExternalDirectoryObjectId
MailboxMoveBatchName
MailboxMoveFlags
MailboxMoveRemoteHostName
MailboxMoveSourceMDB
MailboxMoveStatus
MailboxMoveTargetMDB| -|**Policy**|AddressBookPolicy
DataEncryptionPolicy
EmailAddressPolicyEnabled
ExternalDirectoryObjectId
ManagedFolderMailboxPolicy
PoliciesExcluded
PoliciesIncluded
RemoteAccountPolicy
RetentionPolicy
RetentionUrl
RoleAssignmentPolicy
SharingPolicy
ThrottlingPolicy| -|**PublicFolder**|DefaultPublicFolderMailbox
EffectivePublicFolderMailbox
ExternalDirectoryObjectId
IsExcludedFromServingHierarchy
IsHierarchyReady
IsHierarchySyncEnabled
IsRootPublicFolderMailbox| -|**Quota**|ArchiveQuota
ArchiveWarningQuota
CalendarLoggingQuota
ExternalDirectoryObjectId
IssueWarningQuota
ProhibitSendQuota
ProhibitSendReceiveQuota
RecoverableItemsQuota
RecoverableItemsWarningQuota
RulesQuota
UseDatabaseQuotaDefaults| -|**Resource**|ExternalDirectoryObjectId
IsResource
ResourceCapacity
ResourceCustom
ResourceType
RoomMailboxAccountEnabled| -|**Retention**|EndDateForRetentionHold
ExternalDirectoryObjectId
OrphanSoftDeleteTrackingTime
RetainDeletedItemsFor
RetainDeletedItemsUntilBackup
RetentionComment
RetentionHoldEnabled
RetentionPolicy
RetentionUrl
SingleItemRecoveryEnabled
StartDateForRetentionHold
UseDatabaseRetentionDefaults| -|**SCL**|AntispamBypassEnabled
ExternalDirectoryObjectId
SCLDeleteEnabled
SCLDeleteThreshold
SCLJunkEnabled
SCLJunkThreshold
SCLQuarantineEnabled
SCLQuarantineThreshold
SCLRejectEnabled
SCLRejectThreshold| -|**SoftDelete**|ExternalDirectoryObjectId
IncludeInGarbageCollection
IsInactiveMailbox
IsSoftDeletedByDisable
IsSoftDeletedByRemove
WhenSoftDeleted| -|**StatisticsSeed**|ArchiveDatabaseGuid
DatabaseGuid
ExchangeGuid
ExternalDirectoryObjectId| - -**Note**: The following **Get-Mailbox** parameters aren't available on **Get-EXOMailbox**: - -- *Async* - -- *GroupMailbox* - -- *Migration* - -- *PublicFolder* - -- *SortBy* - -For more information, see: - -- [Get-EXOMailbox](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailbox) - -- [Get-Mailbox](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailbox) - -## Get-EXORecipient property sets - -The available property sets for the **Get-EXORecipient** cmdlet and the properties they contain are described in the following table: - -||| -|:-----|:-----| -|**PropertySet**|**Properties**| -|Minimum|ExchangeVersion
ExternalDirectoryObjectID
Name
OrganizationId
RecipientType
RecipientTypeDetails| -|Archive|ArchiveDatabase
ArchiveGuid
ArchiveRelease
ArchiveState
ArchiveStatus| -|Custom|CustomAttribute1
CustomAttribute2
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute1
ExtensionCustomAttribute2
ExtensionCustomAttribute3
ExtensionCustomAttribute4
ExtensionCustomAttribute5| -|MailboxMove|MailboxMoveBatchName
MailboxMoveFlags
MailboxMoveRemoteHostName
MailboxMoveSourceMDB
MailboxMoveStatus
MailboxMoveTargetMDB| -|Policy|ActiveSyncMailboxPolicy
ActiveSyncMailboxPolicyIsDefaulted
AddressBookPolicy
EmailAddressPolicyEnabled
ManagedFolderMailboxPolicy
OwaMailboxPolicy
PoliciesExcluded
PoliciesIncluded
RetentionPolicy
SharingPolicy
ShouldUseDefaultRetentionPolicy
UMMailboxPolicy| - -**Note**: The following **Get-Recipient** parameters aren't available on **Get-EXORecipient**: - -- *SortBy* - -For more information, see: - -- [Get-EXORecipient](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exorecipient) - -- [Get-Recipient](https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-recipient) - -### Get-EXOMailboxStatistics property sets - -The available property sets for the **Get-EXOMailboxStatistics** cmdlet and the properties they contain are described in the following table: - -||| -|:-----|:-----| -|**PropertySet**|**Properties**| -|Minimum|DeletedItemCount
DisplayName
ItemCount
MailboxGuid
TotalDeletedItemSize
TotalItemSize| -|All|AssociatedItemCount
AttachmentTableAvailableSize
AttachmentTableTotalSize
DatabaseIssueWarningQuota
DatabaseName
DatabaseProhibitSendQuota
DatabaseProhibitSendReceiveQuota
DeletedItemCount
DisconnectDate
DisconnectReason
DisplayName
DumpsterMessagesPerFolderCountReceiveQuota
DumpsterMessagesPerFolderCountWarningQuota
ExternalDirectoryOrganizationId
FastIsEnabled
FolderHierarchyChildrenCountReceiveQuota
FolderHierarchyChildrenCountWarningQuota
FolderHierarchyDepthReceiveQuota
FolderHierarchyDepthWarningQuota
FoldersCountReceiveQuota
FoldersCountWarningQuota
IsAbandonedMoveDestination
IsArchiveMailbox
IsDatabaseCopyActive
IsHighDensityShard
IsMoveDestination
IsQuarantined
ItemCount
LastLoggedOnUserAccount
LastLogoffTime
LastLogonTime
LegacyDN
MailboxGuid
MailboxMessagesPerFolderCountReceiveQuota
MailboxMessagesPerFolderCountWarningQuota
MailboxType
MailboxTypeDetail
MessageTableAvailableSize
MessageTableTotalSize
NamedPropertiesCountQuota
NeedsToMove
OtherTablesAvailableSize
OtherTablesTotalSize
OwnerADGuid
QuarantineClients
QuarantineDescription
QuarantineEnd
QuarantineFileVersion
QuarantineLastCrash
ResourceUsageRollingAvgDatabaseReads
ResourceUsageRollingAvgRop
ResourceUsageRollingClientTypes
ServerName
StorageLimitStatus
SystemMessageCount
SystemMessageSize
SystemMessageSizeShutoffQuota
SystemMessageSizeWarningQuota
TotalDeletedItemSize
TotalItemSize| - -For more information, see: - -- [Get-EXOMailboxStatistics](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxstatistics) - -- [Get-MailboxStatistics](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxstatistics) - diff --git a/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md deleted file mode 100644 index b6dd0b9d96..0000000000 --- a/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md +++ /dev/null @@ -1,364 +0,0 @@ ---- -title: Exchange Online PowerShell V2 -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -ms.reviewer: navgupta -localization_priority: Priority -ms.collection: Strat_EX_Admin -ms.custom: -ms.assetid: -search.appverid: MET150 -description: "Learn how to download and use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell." ---- - -# Use the Exchange Online PowerShell V2 module - -The Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module) enables admins to connect to their Exchange Online environment in Office 365 to retrieve data, create new objects, update existing objects, remove objects as well as configure Exchange Online and its features. - -## Report bugs and issues - -The Exchange Online PowerShell V2 module is currently in Preview. If you have any feedback, concerns, or are facing any issues with the EXO V2 module, contact us at exocmdletpreview[at]service[dot]microsoft[dot]com (email address intentionally obscured to help prevent spam). - -When you report an issue, be sure to include the log files in your email message. - -To generate the log files, replace \ with the output folder you want, and run the following command: - -```PowerShell -Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath -LogLevel All -``` - -## How the EXO V2 module works - -The Exchange Online PowerShell V2 module contains a small set of new cmdlets that are optimized for bulk data retrieval scenarios (think: thousands and thousands of objects). Until you create a session to connect to your Exchange Online organization, you'll only see these new cmdlets in the module. After you connect to your Exchange Online organization, you'll see all of the older remote PowerShell cmdlets. - -The EXO V2 module use Modern authentication for all cmdlets. You can't use Basic authentication in the EXO V2 module; however, you still need to configure the Basic authentication setting in WinRM as described later in this topic. - -The new cmdlets in the EXO V2 module are meant to replace their older, less efficient equivalents. However, the original cmdlets are still available in the EXO V2 module for backwards compatibility **after** you create a session to connect to your Exchange Online organization. - -The new cmdlets in the EXO V2 module are listed in the following table: - -|**New cmdlet in the EXO V2 module**|**Older related cmdlet**| -|:-----|:-----| -|[Connect-ExchangeOnline](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/connect-exchangeonline)|[Connect-EXOPSSession](https://docs.microsoft.com/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell)
or
[New-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389621)| -|[Get-EXOMailbox](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailbox)|[Get-Mailbox](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailbox)| -|[Get-EXORecipient](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exorecipient)|[Get-Recipient](https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-recipient)| -|[Get-EXOCASMailbox](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exocasmailbox)|[Get-CASMailbox](https://docs.microsoft.com/powershell/module/exchange/client-access/get-casmailbox)| -|[Get-EXOMailboxPermission](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxpermission)|[Get-MailboxPermission](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxpermission)| -|[Get-EXORecipientPermission](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exorecipientpermission)|[Get-RecipientPermission](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-recipientpermission)| -|[Get-EXOMailboxStatistics](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxstatistics)|[Get-MailboxStatistics](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxstatistics)| -|[Get-EXOMailboxFolderStatistics](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxfolderstatistics)|[Get-MailboxFolderStatistics](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxfolderstatistics)| -|[Get-EXOMailboxFolderPermission](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxfolderpermission)|[Get-MailboxFolderPermission](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxfolderpermission)| -|[Get-EXOMobileDeviceStatistics](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomobiledevicestatistics)|[Get-MobileDeviceStatistics](https://docs.microsoft.com/powershell/module/exchange/devices/get-mobiledevicestatistics)| - -## Install and maintain the Exchange Online PowerShell V2 module - -You can download the EXO V2 module from the PowerShell gallery [here](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/). - -> [!NOTE] -> The latest version of PowerShell that's currently supported for the EXO V2 module is PowerShell 5.1. Support for PowerShell 6.0 or later is currently a work in progress and will be released soon. This also implies that EXO PowerShell V2 module won't work in Linux or Mac as of now. Support for Linux and Mac is a work in progress and will be announced soon. - -### What do you need to know before you begin? - -- Estimated time to complete: 5 minutes - -- You can use the following versions of Windows: - - - Windows 10 - - - Windows 8.1 - - - Windows Server 2019 - - - Windows Server 2016 - - - Windows Server 2012 or Windows Server 2012 R2 - - - Windows 7 Service Pack 1 (SP1)* - - - Windows Server 2008 R2 SP1* - - \* This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868), [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757), [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). - -- Windows Remote Management (WinRM) on your computer needs to allow Basic authentication (it's enabled by default). To verify that Basic authentication is enabled, run this command **in a Command Prompt**: - - ``` - winrm get winrm/config/client/auth - ``` - - If you don't see the value `Basic = true`, you need to run this command to enable Basic authentication for WinRM: - - ``` - winrm set winrm/config/client/auth @{Basic="true"} - ``` - - If Basic authentication is disabled, you'll get this error when you try to connect: - - > The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again. - - > [!NOTE] - > We don't send the username and password combination here, but the Basic authentication header is required to transport the session's OAuth token, since the client-side WinRM implementation has no support for OAuth. - -### Install the EXO V2 module - -To install the EXO V2 module for the first time, run the following commands: - -1. On your local computer, run the **one** of the following commands from an elevated Windows PowerShell session (a Windows PowerShell window you open by selecting **Run as administrator**): - - - Install the PowerShellGet module for the first time *or* run your current version of the PowerShellGet module side-by-side with the latest version: - - ```PowerShell - Install-Module PowershellGet -Force - ``` - - - Update your existing version of the PowerShellGet module to the latest version: - - ```PowerShell - Update-Module PowershellGet - ``` - -2. Windows PowerShell needs to be configured to run scripts, and by default, it isn't. To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window: - - ```PowerShell - Set-ExecutionPolicy RemoteSigned - ``` - - **Notes**: - - - You need to configure this setting only once on your computer. Read more about execution policies [here](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies). - - - If you don't do this step, you'll receive the following error when you try to connect: - - > Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files. - -3. Close and re-open the elevated Windows PowerShell window to get the changes from the previous steps. - -4. Run the following command from an elevated Windows PowerShell window: - - ```PowerShell - Install-Module -Name ExchangeOnlineManagement - ``` - - Enter **Y** to accept the license agreement. - -### Update the EXO V2 module - -If the EXO V2 module is already installed on your computer, you can run the following commands to see the version that's currently installed and update it to the latest version. - -1. To see the version of the EXO V2 module that's currently installed, run the following commands: - - ```PowerShell - Import-Module ExchangeOnlineManagement; Get-Module ExchangeOnlineManagement - ``` - -2. Run the following command to update the EXO V2 module to latest version that's available in the PowerShell Gallery: - - ```PowerShell - Update-Module -Name ExchangeOnlineManagement - ``` - - Enter **Y** to accept the license agreement. - - **Note**: If you receive the following error related to the PowerShellGet module, see Step 1 in the previous [Install the EXO V2 module](#install-the-exo-v2-module) section to update the PowerShellGet module to the latest version. - - > The specified module 'ExchangeOnlineManagement' with PowerShellGetFormatVersion '\' is not supported by the current version of PowerShellGet. Get the latest version of the PowerShellGet module to install this module, 'ExchangeOnlineManagement'. - - If you need to update the PowerShellGet module, be sure to close and re-open the Windows PowerShell window before you attempt to update the ExchangeOnlineManagement module. - -3. To confirm that the update was successful, run the following commands: - - ```PowerShell - Import-Module ExchangeOnlineManagement; Get-Module ExchangeOnlineManagement - ``` - -### Uninstall the EXO V2 module - -To uninstall the module, run the following command: - -```PowerShell -Uninstall-Module -Name ExchangeOnlineManagement -``` - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). - -## Connect to Exchange Online using the EXO V2 module - -> [!NOTE] -> If your account uses multi-factor authentication (MFA), skip the first step (the **Get-Credential** cmdlet doesn't support MFA enabled accounts). - -1. On your local computer, open a Windows PowerShell window and run the following command: - - ```PowerShell - $UserCredential = Get-Credential - ``` - - In the **Windows PowerShell Credential Request** dialog box, type your work or school account and password, and then click **OK**. - -2. Run one of the following commands: - - - **Accounts without MFA enabled**: - - ```PowerShell - Connect-ExchangeOnline -Credential $UserCredential -ShowProgress $true - ``` - - - **Accounts with MFA enabled**: Replace `` with your account in user principal name format (for example, `navin@contoso.com`) and run the following command: - - ```PowerShell - Connect-ExchangeOnline -UserPrincipalName -ShowProgress $true - ``` - -For detailed syntax and parameter information, see [Connect-ExchangeOnline](https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/connect-exchangeonline). - -## Properties and property sets in the EXO V2 module - -The output of traditional Exchange Online cmdlets returns all possible object properties, including many properties that are often blank, or aren't even required in many scenarios. Returning a large number of blank and unnecessary properties causes degraded performance (more server computation and added network load). The full complement of properties are rarely required in the cmdlet output. - -The EXO V2 module cmdlets have categorized output properties. Instead of giving all properties equal importance and returning them in all scenarios, we've categorized specific related properties into *property sets*. Simply put, these property sets are buckets of two or more related properties on the cmdlet. - -Property sets are controlled by the following parameters on the EXO V2 module cmdlets: - -- *PropertySets*: This parameter accepts one or more available property set names separated by commas. - - This example returns the properties that are available in the Archive and Custom property sets: - - ```PowerShell - Get-EXOMailbox -PropertySets Archive,Custom - ``` - -- *Properties*: This parameter accepts one or more property names separated by commas. - - This example returns the specified properties: - - ```PowerShell - Get-EXOMailbox -Properties LitigationHoldEnabled,AuditEnabled - ``` - - **Note**: Cmdlets that only return a small number of output properties don't have the *PropertySet* or *Properties* parameters. - -You can use *PropertySets* and *Properties* in the same command. For example: - -```PowerShell -Get-EXOMailbox -Properties IsMailboxEnabled,SamAccountName -PropertySets Delivery -``` - -```PowerShell -Get-EXOCASMailbox -Properties EwsEnabled, MAPIBlockOutlookNonCachedMode -PropertySets ActiveSync -``` - -We've also included a Minimum property set (or *minset*) in the available property sets that includes a bare minimum set of properties for the cmdlet output. - -- If you don't use the *PropertySets* or *Properties* parameters, you automatically get the properties that are included in the Minimum property set. - -- If you use the *PropertySets* or *Properties* parameters, you you only get the specified properties. - -Either way, the cmdlet output will contain far fewer properties, and the time it takes to return those results will be much faster. - -This example returns the properties in the Minimum property set for the first ten mailboxes. - -```PowerShell -Get-EXOMailbox -ResultSize 10 -``` - -In contrast, the same **Get-Mailbox** cmdlet would return at least 230 properties for the same ten mailboxes. - -For details about the property sets that are available in EXO V2 module cmdlets, see [Property sets in Exchange Online PowerShell V2 cmdlets](cmdlet-property-sets.md) or the individual EXO V2 module cmdlet reference topics. - -EXO cmdlets also provide a way to retrieve all properties for an object by using the _ProperySets_ parameter with the value `All`. - -The following example returns all properties for the 10 mailboxes: - -```PowerShell -Get-EXOMailbox -ResultSize 10 -PropertySets All -``` - -> [!NOTE] -> We highly discourage using the _PropertySets_ parameter with the value `All` because it slows down the cmdlet and reduces reliability. Always use the _PropertySets_ and _Properties_ parameters to retrieve only the required properties. - -## Release notes - -### Current release: Version 0.4578.0 - -- Added support for configuring the Briefing Email for your organization at the user level with **Set-UserBriefingConfig** and **Get-UserBriefingConfig** cmdlets. - -- Support for session cleanup using **Disconnect-ExchangeOnline** cmdlet. This cmdlet is the V2 equivalent of `Get-PSSession | Remove-PSSession`. In addition to cleaning up session object and local files, it also removes the access token from cache, which is used for authenticating against V2 cmdlets. - -- You can now use `FolderId` as an identity parameter in **Get-EXOMailboxFolderPermission**. You can get the `FolderId` value using **Get-MailboxFolder**. For example: - - `Get-MailboxFolderPermission -Identity :` - - `Get-MailboxFolderPermission -Identity :\` - -- Improved reliability of **Get-EXOMailboxStatistics** as certain request routing errors which led to failures have been resolved. - -- Optimized memory usage when a session is created by re-using any existing module with a new session instead of creating a new one every time session is imported. - -### Previous releases - -#### Version 0.4368.1 - -- Added support for Office 365 Security & Compliance Center PowerShell cmdlets using the **Connect-IPPSSession** cmdlet. - -- Hide the announcement banner using the _ShowBanner_ switch. Run the following command to hide the banner: - - ```powershell - Connect-ExchangeOnline -ShowBanner:$false - ``` - -- Terminate cmdlet execution on client exception. - -- Remote PowerShell contained various complex data types which were intentionally not supported in EXO cmdlets to improve performance. Differences in non-complex data types between remote PowerShell cmdlets and V2 cmdlets have been resolved to allow seamless migration of management scripts. - -#### Version 0.3582.0 - -- Support for prefix during session creation. - - - You can create only 1 session at a time that contains prefixed cmdlets. - - Note that the EXO V2 cmdlets will not be prefixed as they already have the prefix EXO, so don't use `EXO` as a prefix. - -- Use EXO V2 cmdlets even if WinRM Basic Auth is disabled on client machine. Note that remote PowerShell cmdlets require WinRM Basic Auth, and they won't be available if it's disabled. - -- Identity parameter for V2 cmdlets now supports Name and Alias as well. Note that using Alias or Name slows down the performance of V2 cmdlets, so we don't recommend using them. - -- Fixed issue where the data type of attributes returned by V2 cmdlet was different from remote PowerShell cmdlets. We still have few attributes which have differing data types, and we plan to handle them in coming months. - -- Fixed bug: Frequent sessions reconnects issue when Connect-ExchangeOnline was invoked with Credentials or UserPrincipalName - -#### Version 0.3555.1 - -- Fixed a bug where piped cmdlets were failing with the following error due to an authentication issue: - - > Cannot invoke the pipeline because the runspace is not in the Opened state. Current state of the runspace is 'Closed'. - -#### Version 0.3527.4 - -- Updated Get-Help content. - -- Fixed an issue in **Get-Help** where the *-Online* parameter was redirecting to a non-existent page with error code 400. - -#### Version 0.3527.3 - -- Added support for managing Exchange for a different tenant using delegation flow. - -- Works in tandem with other PowerShell modules in a single PS window. - -- Added support for positional parameters. - -- Date Time field now supports client locale. - -- Bug fix: PSCredential empty when passed during Connect-ExchangeOnline. - -- Bug fix: Client module error when filter contained $null. - -- Sessions created internal to EXO V2 Module now have names (naming pattern: ExchangeOnlineInternalSession_%SomeNumber%). - -- Bug fix: Remote PowerShell cmdlets intermittently failing due to time the difference between token expiry and the PSSession going idle. - -- Major security update. - -- Bug fixes and enhancements. diff --git a/exchange/docs-conceptual/exchange-online/exchange-online-powershell.md b/exchange/docs-conceptual/exchange-online/exchange-online-powershell.md deleted file mode 100644 index 51da38c5a9..0000000000 --- a/exchange/docs-conceptual/exchange-online/exchange-online-powershell.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: "Exchange Online PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: 2/20/2018 -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -localization_priority: Normal -ms.assetid: 1cb603b0-2961-4afe-b879-b048fe0f64a2 -search.appverid: MET150 -description: "Learn about using PowerShell in Exchange Online" ---- - -# Exchange Online PowerShell - -Exchange Online PowerShell is the administrative interface that enables you to manage your Microsoft Exchange Online organization from the command line. For example, you can use Exchange Online PowerShell to configure mail flow rules (also known as transport rules) and connectors. The following topics provide information about using Exchange Online PowerShell: - -- To create a remote PowerShell session to your Exchange Online organization, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md). - -- To prevent or allow connections to connect to your Exchange Online organization using remote PowerShell, see [Enable or disable access to Exchange Online PowerShell](disable-access-to-exchange-online-powershell.md). - -- The following introductory video shows you how to connect to and use Exchange Online PowerShell. - - **Note:** This video applies to Exchange Online and standalone Exchange Online Protection (EOP) organizations. When you connect to your organization, be sure to specify the correct URL (*ConnectionUri* value). The required URL is different for Exchange Online and EOP organizations. - - [Use Remote PowerShell in EOP](https://videoplayercdn.osi.office.net/hub/?csid=ux-cms-en-us-msoffice&uuid=9cb28006-c2cb-45b6-b72e-eeed8767dee7&AutoPlayVideo=false) - -- To find the permissions you need to run a specific cmdlet, or one or more parameters on the cmdlet, see [Find the permissions required to run any Exchange cmdlet](../exchange-server/find-exchange-cmdlet-permissions.md). - -- To learn about recipient filters in Exchange Online PowerShell, see [Recipient filters in Exchange Management Shell and Exchange Online PowerShell commands](../exchange-server/recipient-filters/recipient-filters.md). diff --git a/exchange/docs-conceptual/exchange-server/connect-to-exchange-servers-using-remote-powershell.md b/exchange/docs-conceptual/exchange-server/connect-to-exchange-servers-using-remote-powershell.md deleted file mode 100644 index 9d586c000f..0000000000 --- a/exchange/docs-conceptual/exchange-server/connect-to-exchange-servers-using-remote-powershell.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: "Connect to Exchange servers using remote PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: 12/20/2016 -ms.audience: ITPro -ms.topic: article -ms.prod: exchange-server-itpro -localization_priority: Priority -ms.collection: Strat_EX_Admin -ms.custom: -ms.assetid: 0b5987c3-8836-456d-99f7-abc2ffb57300 -description: "Use Windows PowerShell on a local computer to connect to an Exchange Server." ---- - -# Connect to Exchange servers using remote PowerShell - -If you don't have the Exchange management tools installed on your local computer, you can use Windows PowerShell to create a remote PowerShell session to an Exchange server. It's a simple three-step process, where you enter your credentials, provide the required connection settings, and then import the Exchange cmdlets into your local Windows PowerShell session so that you can use them. - -> [!NOTE] -> We recommend that you use the Exchange Management Shell on any computer that you use to extensively administer Exchange servers. You'll get the Exchange Management Shell by installing the Exchange management tools. For more information, see [Install the Exchange Server Management Tools](https://docs.microsoft.com/Exchange/plan-and-deploy/post-installation-tasks/install-management-tools) and [Open the Exchange Management Shell](open-the-exchange-management-shell.md). For more information about the Exchange Management Shell, see [Exchange Server PowerShell (Exchange Management Shell)](exchange-management-shell.md).

Get-ExchangeCertificate does not fully support remote PowerShell. We recommend that you use the Exchange Management Shell instead to get all the properties of this cmdlet. - -## What do you need to know before you begin? - -- Estimated time to complete: less than 5 minutes - -- You can use the following versions of Windows: - - - Windows 10 - - - Windows 8.1 - - - Windows Server 2019 - - - Windows Server 2016 - - - Windows Server 2012 or Windows Server 2012 R2 - - - Windows 7 Service Pack 1 (SP1)* - - - Windows Server 2008 R2 SP1* - - \* This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868), [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757), [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). - -- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You'll get the following error when you try to connect: - - `Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.` - - To require all scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**): - - ```PowerShell - Set-ExecutionPolicy RemoteSigned - ``` - - You need to configure this setting only once on your computer, not every time you connect. - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612). - -## Connect to a remote Exchange server - -1. On your local computer, open Windows PowerShell, and run the following command: - - ```PowerShell - $UserCredential = Get-Credential - ``` - - In the **Windows PowerShell Credential Request** dialog box that opens, enter your user principal name (UPN) (for example, `chris@contoso.com`) and password, and then click **OK**. - -2. Replace `` with the fully qualified domain name of your Exchange server (for example, `mailbox01.contoso.com`) and run the following command: - - ```PowerShell - $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http:///PowerShell/ -Authentication Kerberos -Credential $UserCredential - ``` - - **Note**: The _ConnectionUri_ value is `http`, not `https`. - -3. Run the following command: - - ```PowerShell - Import-PSSession $Session -DisableNameChecking - ``` - -> [!NOTE] -> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command: - -```PowerShell -Remove-PSSession $Session -``` - -## How do you know this worked? - -After Step 3, the Exchange cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange cmdlet (for example, **Get-Mailbox**) and review the results. - -If you receive errors, check the following requirements: - -- A common problem is an incorrect password. Run the three steps again, and pay close attention to the user name and password you enter in Step 1. - -- The account you use to connect to the Exchange server needs to be enabled for remote PowerShell access. For more information, see [Control remote PowerShell access to Exchange servers](control-remote-powershell-access-to-exchange-servers.md). - -- TCP port 80 traffic needs to be open between your local computer and the Exchange server. It's probably open, but it's something to consider if your organization has a restrictive network access policy. - -## See also - -The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics. - -- [Get-Credential](https://go.microsoft.com/fwlink/p/?LinkId=389618) - -- [New-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389621) - -- [Import-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389619) - -- [Remove-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389620) - -- [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623) diff --git a/exchange/docs-conceptual/exchange-server/control-remote-powershell-access-to-exchange-servers.md b/exchange/docs-conceptual/exchange-server/control-remote-powershell-access-to-exchange-servers.md deleted file mode 100644 index 16398af89c..0000000000 --- a/exchange/docs-conceptual/exchange-server/control-remote-powershell-access-to-exchange-servers.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: "Control remote PowerShell access to Exchange servers" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: ITPro -ms.topic: article -ms.prod: exchange-server-itpro -localization_priority: Normal -ms.assetid: 064e3bb0-38bf-495e-9994-784f823b88dd -description: "Administrators can learn how to block or allow users' remote PowerShell access to Exchange servers." ---- - -# Control remote PowerShell access to Exchange servers - -Remote PowerShell in Microsoft Exchange allows you to manage your Exchange organization from a remote computer that's on your internal network or from the Internet. You can disable or enable a user's ability to connect to an Exchange server using remote PowerShell. For more information about remote PowerShell, see [Exchange Server PowerShell (Exchange Management Shell)](exchange-management-shell.md). - -For additional management tasks related to remote PowerShell, see [Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md). - -## What do you need to know before you begin? - -- Estimated time to complete each procedure: less than 5 minutes - -- You can only use PowerShell to perform this procedure. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see [Open the Exchange Management Shell](open-the-exchange-management-shell.md). - -- By default, all user accounts have access to remote PowerShell. However, to actually use remote PowerShell to connect to an Exchange server, the user needs to be a member of a management role group, or be directly assigned a management role that enables the user to run Exchange cmdlets. For more information about role groups and management roles, see [Exchange Server permissions](https://docs.microsoft.com/Exchange/permissions/permissions). - -- For detailed information about OPath filter syntax in Exchange, see [Additional OPATH syntax information](../exchange-server/recipient-filters/recipient-filters.md#additional-opath-syntax-information). - -- You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Remote PowerShell" entry in the [Exchange infrastructure and PowerShell permissions](https://docs.microsoft.com/Exchange/permissions/feature-permissions/infrastructure-permissions) topic. - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612). - -## Use the Exchange Management Shell to enable or disable remote PowerShell access for a user - -This example disables remote PowerShell access for the user named Therese Lindqvist. - -```PowerShell -Set-User "Therese Lindqvist" -RemotePowerShellEnabled $false -``` - -This example enables remote PowerShell access for the user named Sirirat Kitjakarn. - -```PowerShell -Set-User "Sirirat Kitjakarn" -RemotePowerShellEnabled $true -``` - -## Use the Exchange Management Shell to disable remote PowerShell access for many users - -To prevent remote PowerShell access for a specific group of existing users, you have the following options: - -- **Filter users based on an existing attribute**: This method assumes that the target user accounts all share a unique filterable attribute. Some attributes, such as Title, Department, address information, and telephone number, are visible only when you use the **Get-User** cmdlet. Other attributes, such as CustomAttribute1-15, are visible only when you use the **Get-Mailbox** cmdlet. - -- **Use a list of specific users**: After you generate the list of specific users, you can use that list to disable their access to remote PowerShell. - -### Filter users based on an existing attribute - -To disable access to remote PowerShell for any number of users based on an existing attribute, use the following syntax: - -```PowerShell -$ = -ResultSize unlimited -Filter -``` - -```PowerShell -$ | foreach {Set-User -RemotePowerShellEnabled $false} -``` - -This example removes access to remote PowerShell for all users whose **Title** attribute contains the value "Sales Associate". - -```PowerShell -$DSA = Get-User -ResultSize unlimited -Filter "(RecipientType -eq 'UserMailbox') -and (Title -like '*Sales Associate*')" -``` - -```PowerShell -$DSA | foreach {Set-User -RemotePowerShellEnabled $false} -``` - -### Use a list of specific users - -To disable access to remote PowerShell for a list of specific users, use the following syntax: - -```PowerShell -$ = Get-Content -``` - -```PowerShell -$ | foreach {Set-User -RemotePowerShellEnabled $false -``` - -This example uses the text file C:\My Documents\NoPowerShell.txt to identify the users by their user principal name (UPN). The text file must contain one UPN on each line like this: - -> akol@contoso.com
tjohnston@contoso.com
kakers@contoso.com - -After you populate the text file with the user accounts you want to update, run the following commands: - -```PowerShell -$NPS = Get-Content "C:\My Documents\NoPowerShell.txt" -``` - -```PowerShell -$NPS | foreach {Set-User -RemotePowerShellEnabled $false} -``` - -## View the remote PowerShell access for users - -To view the remote PowerShell access status for a specific user, use the following syntax: - -```PowerShell -Get-User -Identity | Format-List RemotePowerShellEnabled -``` - -This example displays the remote PowerShell access status of the user named Sarah Jones. - -```PowerShell -Get-User -Identity "Sarah Jones" | Format-List RemotePowerShellEnabled -``` - -To display the remote PowerShell access status for all users, run the following command: - -```PowerShell -Get-User -ResultSize unlimited | Format-Table -Auto Name,DisplayName,RemotePowerShellEnabled -``` - -To display only those users who don't have access to remote PowerShell, run the following command: - -```PowerShell -Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $false' -``` - -To display only those users who have access to remote PowerShell, run the following command: - -```PowerShell -Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $true' -``` diff --git a/exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md b/exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md deleted file mode 100644 index 0cf71a96c2..0000000000 --- a/exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: "Exchange cmdlet syntax" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: exchange-online -localization_priority: Normal -ms.assetid: 85ffe9c8-7f03-4877-8e55-3cbd40228d84 -description: "Learn about the structure and syntax of cmdlets in Exchange, Exchange Online, Exchange Online Protection, and the Office 365 Security & Compliance Center." ---- - -# Exchange cmdlet syntax - -Exchange cmdlet reference topics use a standardized method that describes key aspects about the cmdlet. For example: - -- Parameters that are available on the cmdlet. - -- Values that each parameter accepts. - -- Parameters that can be used together, and parameters that need to be used separately. - -This topic explains these conventions, and also the syntax that's required to run commands in Exchange PowerShell. - -## Command conventions in Exchange PowerShell - -Exchange PowerShell help follows conventions that indicate what's required or optional, and how to enter parameters and values when you run a command. These command conventions are listed in the following table. - -|**Symbol**|**Description**| -|:-----|:-----| -| - |A hyphen indicates a parameter. For example, `-Identity`.| -|\< \>|Angle brackets indicate the possible values for a parameter. For example, `-Location ` or -Enabled \<$true \| $false\>.| -|[ ]|Square brackets indicate optional parameters and their values. For example, `[-WhatIf]` or `[-ResultSize ]`.
Parameter-value pairs that aren't enclosed in square brackets are required. For example, `-Password `.
If the parameter name itself is enclosed in square brackets, that indicates the parameter is a _positional_ parameter (you can use the parameter value without specifying the parameter), and positional parameters can be required or optional.
For example, `Get-Mailbox [[-Identity] ]` means the _Identity_ parameter is positional (because it's enclosed in square brackets) and optional (because the whole parameter-value pair is enclosed in square brackets), so you can use `Get-Mailbox -Identity ` or `Get-Mailbox `. Similarly, `Set-Mailbox [-Identity] ` means the _Identity_ parameter is positional (because it's enclosed in square brackets) and required (because the whole parameter-value pair is not enclosed in square brackets), so you can use `Set-Mailbox -Identity ` or `Set-Mailbox `.| -|\||Pipe symbols in parameter values indicate a choice between values. For example, -Enabled \<$true \| $false\> indicates the _Enabled_ parameter can have the value `$true` or `$false`.| - -These command conventions help you understand how a command is constructed. With the exception of the hyphen that indicates a parameter, you don't use these symbols as they're described in the table when you run cmdlets in Exchange PowerShell. - -## Parameter sets in Exchange PowerShell - -Parameter sets are groups of parameters that can be used with each other in the same command. Although parameter sets typically share some parameters, each parameter set contains at least one parameter that isn't available in the other parameter sets, and can't be used with some of the parameters in different parameter sets. - -Many cmdlets have only one parameter set, which means that all available parameters can be used with each other. Other cmdlets have several parameter sets, which indicates some parameters perform functions that are incompatible with other parameters. For example, suppose the following parameter sets are available on the **New-SystemMessage** cmdlet: - -`New-SystemMessage -DsnCode -Internal -Language -Text [-Confirm] [-DomainController ] [-WhatIf] ` - -`New-SystemMessage -Language -QuotaMessageType -Text [-Confirm] [-DomainController ] [-WhatIf] ` - -This cmdlet has two separate parameter sets. Based on the entries, you can use these parameters together in the same command: - -- _DsnCode_ - -- _Internal_ - -- _Language_ - -- _Text_ - -- _Confirm_ - -- _DomainController_ - -- _WhatIf_ - -And you can use these parameters together in the same command: - -- _Language_ - -- _QuotaMessageType_ - -- _Text_ - -- _Confirm_ - -- _DomainController_ - -- _WhatIf_ - -But you can't use these parameters together in the same command: - -- _DsnCode_ and _QuotaMessageType_. - -- _Internal_ and _QuotaMessageType_. - -The `` entry indicates the cmdlet supports the basic Windows PowerShell parameters that are available on virtually any cmdlet (for example, _Debug_). You can use common parameters with parameters from any parameter set. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). - -## Quotation marks in Exchange PowerShell - -In Exchange PowerShell, you use single quotation marks ( ' ) or double quotation marks ( " ) to enclose parameter values that contain spaces. For example, the following commands behave the same: - -- `Get-ReceiveConnector -Identity "Contoso Receive Connector"` - -- `Get-ReceiveConnector -Identity 'Contoso Receive Connector'` - -If you don't enclose the value `Contoso Receive Connector` in quotes, Exchange PowerShell tries to treat each word as a new argument, and the command will fail. In this example, you'll receive an error that looks like this: - - `A positional parameter cannot be found that accepts argument 'Receive'` - -If the value contains variables, you need choose carefully between single quotes and double quotes. For example, suppose you have a variable named `$Server` that has the value `Mailbox01`. - -- **Double quotation marks**: Variables are substituted with their values. The input **"$Server Example"** results in the output `Mailbox01 Example`. - -- **Single quotation marks**: Variables are treated literally. The input **'$Server Example'** results in the output `$Server Example`. - -For more information about variables, see [about_Variables](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_variables) and [about_Automatic_Variables](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_automatic_variables). - -## Escape characters in Exchange PowerShell - -In any programming language, an escape character is used to identify special characters literally, and not by their normal function in that language. In Exchange PowerShell, when you enclose a text string in double quotation marks, the escape character is the back quotation mark escape character ( \` ). - -For example, if you want the output `The price is $23`, enter the value **"The price is \`$23"**. The escape character is required because the dollar sign character ( $ ) defines variables in Exchange PowerShell. - -If you enclose the string in single quotation marks, the only special character you need to worry about is the single quotation mark character itself, which requires two single quotation marks ( '' ). - - For example, if you want the output `Don't confuse two single quotation marks with a double quotation mark!`, enter the value **'Don''t confuse two single quotation marks with a double quotation mark!'**. - -## Command operators in Exchange PowerShell - -The following table shows the valid operators that you can use in an Exchange command. Some of these symbols were also described in the earlier [Command conventions in Exchange PowerShell](#command-conventions-in-exchange-powershell) section. However, these symbols have different meanings when they're used on the command line as operators. For example, the minus sign that's used to indicate a parameter can also be used in a command as a mathematical operator. - -|**Operator**|**Description**| -|:-----|:-----| -|**=**|The equal sign is used as an assignment character. The value on the right side of the equal sign is assigned to the variable on the left side of the equal sign. The following characters are also assignment characters:
• **+=**: Add the value on the right side of the equal sign to the current value that's contained in the variable on the left side of the equal sign.
• **-=**: Subtract the value on the right side of the equal sign from the current value that's contained in the variable on the left side of the equal sign.
• **\*=**: Multiply the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.
• **/=**: Divide the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.
• **%=**: Modify the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.| -|**:**|A colon can be used to separate a parameter's name from the parameter's value. For example, `-Enabled:$True`. Using a colon is optional with all parameter types except switch parameters. For more information about switch parameters, see [about_Parameters](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).| -|**!**|The exclamation point is a logical **NOT** operator. When it is used with the equal ( **=** ) sign, the combined pair means "not equal to."| -|**[ ]**|Brackets are used to specify the index value of an array position. Index values are offsets that start at zero. For example, `$Red[9]` refers to the tenth index position in the array, `$Red`.
Brackets can also be used to assign a type to a variable (for example, `$A=[XML] "value"`). The following variable types are available: `Array`, `Bool`, `Byte`, `Char`, `Char[]`, `Decimal`, `Double`, `Float`, `Int`, `Int[]`, `Long`, `Long[]`, `RegEx`, `Single`, `ScriptBlock`, `String`, `Type`, and `XML.`| -|**{ }**|Braces are used to include an expression in a command. For example, Get-Process \| Where {$\_.HandleCount -gt 400}| -|**\|**|The pipe symbol is used when one cmdlet pipes a result to another cmdlet. For example, Get-Mailbox -Server SRV1 \| Set-Mailbox -ProhibitSendQuota 2GB.| -|**\>**|The right-angle bracket is used to send the output of a command to a file, and the contents of the file are overwritten. For example, `Get-TransportRulePredicate > "C:\My Documents\Output.txt"`.| -|**\>\>**|Double right-angle brackets are used to append the output of a command to an existing file. If the file doesn't exist, a new file is created. For example, `Get-TransportRulePredicate >> "C:\My Documents\Output.txt"`.| -|**"**|Double quotation marks are used to enclose text strings that contains spaces.| -|**$**|A dollar sign indicates a variable. For example, `$Blue = 10` assigns the value `10` to the variable `$Blue`.| -|**@**|The @ symbol references an associative array. For more information, see [about_Arrays](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_arrays).| -|**$( )**|A dollar sign ( `$` ) with parentheses indicates command substitution. You can use command substitution when you want to use the output of one command as an argument in another command. For example, `Get-ChildItem $(Read-Host -Prompt "Enter FileName: ")`.| -|**..**|Double-periods indicate a value range. For example, if an array contains several indexes, you can return the values of all indexes between the second and fifth indexes by running the command: `$Blue[2..5]`.| -|**+**|The **+** operator adds two values together. For example, `6 + 6` equals `12`.| -|**-**|The **-** operator subtracts one value from another value (for example, `12 - 6` equals `6`) or indicates a negative number (for example, `-6 * 6` equals `-36`).| -|**\***|You can use the wildcard character to match strings (for example, Get-User \| Where-Object {$\_.Department -like 'Sales*'}), multiply numeric values (for example, `6 * 6` equals `36`), or repeat the string value the specified number of times (for example, `"Test" * 3` equals `TestTestTest`).| -|**/**|The **/** operator divides one value by another. For example, `6 / 6` equals `1`.| -|**%**|In a numerical evaluation, the **%** operator returns the remainder from a division operator. For example, `6 % 4` equals `2`.
In a pipeline, the percent character ( `%` ) is shorthand for the **ForEach-Object** cmdlet. For example, Import-Csv c:\MyFile.csv \| ForEach-Object {Set-Mailbox $\_.Identity -Name $\_.Name} is the same as Import-Csv c:\MyFile.csv \| % {Set-Mailbox $\_.Identity -Name $\_.Name}. For more information, see [about_Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines).| -|**?**|The question mark character ( **?** ) is shorthand for the **Where-Object** cmdlet. For example, Get-Alias \| Where-Object {$\_.Definition -eq "Clear-Host"} is the same as Get-Alias \| ? {$\_.Definition -eq "Clear-Host"}| diff --git a/exchange/docs-conceptual/exchange-server/exchange-management-shell.md b/exchange/docs-conceptual/exchange-server/exchange-management-shell.md deleted file mode 100644 index b8a8705c56..0000000000 --- a/exchange/docs-conceptual/exchange-server/exchange-management-shell.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: "Exchange Server PowerShell (Exchange Management Shell)" -ms.author: chrisda -author: chrisda -manager: sansimp -ms.date: -ms.audience: ITPro -ms.topic: article -ms.prod: exchange-server-itpro -localization_priority: Normal -ms.assetid: 925ad66f-2f05-4269-9923-c353d9c19312 -description: "Learn about Exchange Server PowerShell, also known as the Exchange Management Shell. This topic describes how PowerShell works on Exchange servers, and provides links to other topics that can help you learn how to use the Exchange Management Shell." ---- - -# Exchange Server PowerShell (Exchange Management Shell) - -The Exchange Management Shell is built on Windows PowerShell technology and provides a powerful command-line interface that enables the automation of Exchange administration tasks. You can use the Exchange Management Shell to manage every aspect of Exchange. For example, you can create email accounts, create Send connectors and Receive connectors, configure mailbox database properties, and manage distribution groups. You can use the Exchange Management Shell to perform every task that's available in the Exchange graphical management tools, plus things that you can't do there (for example, bulk operations). In fact, when you do something in the Exchange admin center (EAC), the Exchange Control Panel (ECP), or the Exchange Management Console (EMC), it's the Exchange Management Shell that does the work behind the scenes. - -The Exchange Management Shell also provides a robust and flexible scripting platform. Visual Basic scripts that required many lines of code can be replaced by Exchange Management Shell commands that use as little as one line of code. The Exchange Management Shell provides this flexibility because it uses an object model that's based on the Microsoft .NET Framework. This object model enables Exchange cmdlets to apply the output from one command to subsequent commands. - -To start using the Exchange Management Shell immediately, see the [Exchange Management Shell documentation](#exchange-management-shell-documentation) section later in this topic. - -## How the Exchange Management Shell works on all Exchange server roles except Edge Transport - -Whether you use the Exchange Management Shell on a local Exchange server or on an Exchange server that's located across the country, remote PowerShell does the work. - -When you click the Exchange Management Shell shortcut on an Exchange server, the local instance of Windows PowerShell performs the following steps: - -1. Connect to the closest Exchange server (most often, the local Exchange server) using a required Windows PowerShell component called Windows Remote Management (WinRM). - -2. Perform authentication checks. - -3. Create a remote PowerShell session for you to use. - -You only get access to the Exchange cmdlets and parameters that are associated with the Exchange management role groups and management roles you're assigned. For more information about how Exchange uses role groups and roles to manage who can do what tasks, see [Exchange Server permissions](https://docs.microsoft.com/Exchange/permissions/permissions). - -A benefit of remote PowerShell is that you can use Windows PowerShell on a local computer to connect to a remote Exchange server, and import the Exchange cmdlets in the Windows PowerShell session so you can administer Exchange. The only requirements for the computer are: - -- A supported operating system for Exchange Server. - -- A supported version of the .NET Framework. - -- A supported version of the Windows Management Framework (WMF), which includes WinRM and Windows PowerShell. - -For details, see the following topics: - -- [Exchange 2019 system requirements](https://docs.microsoft.com/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019) - -- [Exchange 2016 system requirements](https://docs.microsoft.com/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016) - -- [Exchange 2013 system requirements](https://docs.microsoft.com/exchange/exchange-2013-system-requirements-exchange-2013-help) - -- [Exchange 2010 system requirements](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/aa996719(v=exchg.141)) - -However, we recommend that you install the Exchange management tools (which includes the Exchange Management Shell) on any computer that you use to extensively manage Exchange Server. Without the Exchange management tools installed, you need to connect to the remote Exchange server manually, and you don't have access to the additional capabilities that the Exchange management tools provide. - -For more information about connecting to Exchange servers without the Exchange management tools installed, see [Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md). - -## How Exchange Management Shell works on Edge Transport servers - -On Edge Transport servers, the Exchange Management Shell works differently. You typically deploy Edge Transport servers in your perimeter network, either as stand-alone servers or as members of a perimeter Active Directory domain. - -When you click the Exchange Management Shell shortcut on an Exchange Edge Transport server, the local instance of Windows PowerShell creates a local PowerShell session for you to use. - -Edge Transport servers don't use management roles or management role groups to control permissions. The local Administrators group controls who can configure the Exchange features on the local server. - -For more information about Edge Transport servers, see [Edge Transport Servers](https://docs.microsoft.com/Exchange/architecture/edge-transport-servers/edge-transport-servers). - -## Exchange Management Shell documentation - -The following table provides links to topics that can help you learn about and use the Exchange Management Shell. - -|**Topic**|**Description**| -|:-----|:-----| -|[Open the Exchange Management Shell](open-the-exchange-management-shell.md)|Find and open the Exchange Management Shell on an Exchange server or a computer that has the Exchange management tools installed.| -|[Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md)|Use Windows PowerShell on a local computer to connect to an Exchange server.| -|[Control remote PowerShell access to Exchange servers](control-remote-powershell-access-to-exchange-servers.md)|Learn how to block or allow users' remote PowerShell access to Exchange servers.| -|[Find the permissions required to run any Exchange cmdlet](find-exchange-cmdlet-permissions.md)|Find the permissions you need to run a specific cmdlet, or one or more parameters on the cmdlet.| -|[Exchange cmdlet syntax](exchange-cmdlet-syntax.md)|Learn about the structure and syntax of cmdlets in Exchange PowerShell.| -|[Recipient filters in Exchange Management Shell commands](recipient-filters/recipient-filters.md)|Learn about recipient filters in the Exchange Management Shell.| -|[Use Update-ExchangeHelp to update Exchange PowerShell help topics on Exchange servers](use-update-exchangehelp.md)|Learn how to use Update-ExchangeHelp to update help for Exchange cmdlet reference topics on Exchange servers.| diff --git a/exchange/docs-conceptual/exchange-server/find-exchange-cmdlet-permissions.md b/exchange/docs-conceptual/exchange-server/find-exchange-cmdlet-permissions.md deleted file mode 100644 index caf21d3f38..0000000000 --- a/exchange/docs-conceptual/exchange-server/find-exchange-cmdlet-permissions.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -title: "Find the permissions required to run any Exchange cmdlet" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: ITPro -ms.topic: article -ms.service: exchange-online -localization_priority: Normal -ms.assetid: 5bcc46d3-8a07-4e9f-b1b0-e4cb0b0afc12 -description: "Admins can learn how to use PowerShell to find the permissions required to run any Exchange or Exchange Online cmdlet." ---- - -# Find the permissions required to run any Exchange cmdlet - -You can use PowerShell to find the permissions required to run any Exchange or Exchange Online cmdlet. This procedure shows the role-based access control (RBAC) management roles and role groups that give you access to a specified cmdlet—even if your organization has custom roles, custom role groups, or custom role assignments. - -## What do you need to know before you begin? - -- Estimated time to complete this procedure: less than 5 minutes. - -- You can only use PowerShell to perform this procedure. - -- Basically, you need to be an administrator to complete this procedure. Specifically, you need access to the **Get-ManagementRole** and **Get-ManagementRoleAssignment** cmdlets. By default, access to these cmdlets is granted by the View-Only Configuration or Role Management roles, which are assigned to the View-Only Organization Management and Organization Management role groups. - -- The procedures in this topic don't work in the Office 365 Security & Compliance Center. For more information about permissions in the Security & Compliance Center, see [Permissions in Office 365 Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -- The procedures in this topic don't work in Exchange Online Protection (EOP). For more information about permissions in EOP, see [Feature permissions in EOP](https://docs.microsoft.com/microsoft-365/security/office-365-security/feature-permissions-in-eop). - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612) or [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542). - -## Use PowerShell to find the permissions required to run a cmdlet - -1. Open the PowerShell environment where you want to run the cmdlet. - - - To learn how to use Windows PowerShell to connect to Exchange Online, see [Connect to Exchange Online PowerShell](../exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md). - - - To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see [Open the Exchange Management Shell](open-the-exchange-management-shell.md). - -2. Run the following command to identify the cmdlet and, optionally, one or more parameters on the cmdlet. Be sure to replace `` and optionally, `,,...` with the actual cmdlet and parameter names you are interested in. If you specify multiple parameters separated by commas, only the roles that include **all** of the parameters are returned. - - ```PowerShell - $Perms = Get-ManagementRole -Cmdlet [-CmdletParameters ,,...] - ``` - -3. Run the following command: - - ```PowerShell - $Perms | foreach {Get-ManagementRoleAssignment -Role $_.Name -Delegating $false | Format-Table -Auto Role,RoleAssigneeType,RoleAssigneeName} - ``` - -## Interpreting the results - -The results contain the following information: - -- **Role**: Indicates the role that gives access to the cmdlet or the combination of cmdlet and parameters. Note that role names that begin with "My" are user roles that allow regular users to operate on objects they own (for example, their own mailbox or their distribution groups). - -- **RoleAssigneeType** and **RoleAssigneeName**: These values are inter-related. **RoleAssigneeType** is the type of object that has the role assigned to it, and **RoleAssigneeName** is the name of the object. **RoleAssigneeType** can be a role group, role assignment policy, security group, or user. Typically, administrator roles are assigned to role groups. - -## Troubleshooting - -What if there are no results? - -- Verify that you entered the cmdlet and parameter names correctly. - -- You might have entered too many parameters, and all of the parameters on the cmdlet aren't defined in a single role. Try specifying only the cmdlet name in Step 2, and run Step 3 to verify that the cmdlet is available in your environment. Then, add parameters one at a time to Step 2 before running Step 3. - -- These possible causes have the same solution: - - - You might have entered a cmdlet or parameters that are defined in a role that isn't assigned to anyone by default. - - - You might have entered a cmdlet or parameter that isn't available in your environment. For example, when you enter an Exchange Online cmdlet or parameters in an on-premises Exchange 2016 environment. - - Run the following command to find the role that contains the cmdlet or parameters. Be sure to replace `` and optionally, `,,...` with the actual cmdlet and parameter names you are interested in. Note that you can use wildcard characters (*) in the cmdlet and parameter names (for example, `*-Mailbox*`). - - ```PowerShell - Get-ManagementRoleEntry -Identity *\ [-Parameters ,,... ] - ``` - - - If the command returns an error saying the object couldn't be found, the cmdlet or parameters aren't available in your environment. - - - If the command returns one or more entries for **Name**, **Role**, and **Parameters**, the cmdlet (or parameters on the cmdlet) is available in your environment, but the required role isn't assigned to anyone. To see all roles that aren't assigned to anyone, run the following command: - - ```PowerShell - $na = Get-ManagementRole ; $na | foreach {If ((Get-ManagementRoleAssignment -Role $_.Name -Delegating $false) -eq $null) {$_.Name}} - ``` - -## Related procedures - -- Management role scopes define where cmdlets can operate (in particular, write scopes). - - To include scope information in Step 2, substitute the following command: - - ```PowerShell - $Perms | foreach {Get-ManagementRoleAssignment -Role $_.Name -Delegating $false | Format-List Role,RoleAssigneeType,RoleAssigneeName,*Scope*} - ``` - -- To see all roles assigned to a specific user, run the following command: - - ```PowerShell - Get-ManagementRoleAssignment -RoleAssignee -Delegating $false | Format-Table -Auto Role,RoleAssigneeName,RoleAssigneeType - ``` - - For example: - - ```PowerShell - Get-ManagementRoleAssignment -RoleAssignee julia@contoso.com -Delegating $false | Format-Table -Auto Role,RoleAssigneeName,RoleAssigneeType - ``` - -- To see all users who are assigned a specific role, run the following command: - - ```PowerShell - Get-ManagementRoleAssignment -Role "" -GetEffectiveUsers -Delegating $false | Where-Object {$_.EffectiveUserName -ne "All Group Members"} | Format-Table -Auto EffectiveUserName,Role,RoleAssigneeName,AssignmentMethod - ``` - - For example: - - ```PowerShell - Get-ManagementRoleAssignment -Role "Mailbox Import Export" -GetEffectiveUsers -Delegating $false | Where-Object {$_.EffectiveUserName -ne "All Group Members"} | Format-Table -Auto EffectiveUserName,Role,RoleAssigneeName,AssignmentMethod - ``` - -- To see the members of a specific role group, run the following command: - - ```PowerShell - Get-RoleGroupMember "" - ``` - - For example: - - ```PowerShell - Get-RoleGroupMember "Organization Management" - ``` diff --git a/exchange/docs-conceptual/exchange-server/open-the-exchange-management-shell.md b/exchange/docs-conceptual/exchange-server/open-the-exchange-management-shell.md deleted file mode 100644 index 587cbfe5c0..0000000000 --- a/exchange/docs-conceptual/exchange-server/open-the-exchange-management-shell.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: "Open the Exchange Management Shell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: ITPro -ms.topic: article -ms.prod: exchange-server-itpro -localization_priority: Normal -ms.assetid: 63976059-25f8-4b4f-b597-633e78b803c0 -description: "Find and open the shortcut for Exchange PowerShell (also known as the Exchange Management Shell) on Exchange servers or computers that have the Exchange management tools installed." ---- - -# Open the Exchange Management Shell - -When you open the Exchange Management Shell you can perform administrative tasks on Exchange Server from the command line. You can open the Exchange Management Shell from the following locations: - -- On the Exchange server directly or in a Remote Desktop Connection session. - -- On a local computer after you install the Exchange management tools. For more information, see [Install the Exchange management tools](https://docs.microsoft.com/Exchange/plan-and-deploy/post-installation-tasks/install-management-tools). - -## What do you need to know before you begin? - -- Estimated time to complete this procedure: less than 1 minute. - -- The user must be assigned at least one management role. For detailed steps, see [Exchange Server permissions](https://docs.microsoft.com/Exchange/permissions/permissions). - -- If you want to run the Exchange Management Shell from a local installation of the Exchange management tools, you need to consider remote PowerShell access for your user account. By default, users are allowed to use remote PowerShell to connect to an Exchange server. However, you can block remote PowerShell access for a user account. For more information, see [Control remote PowerShell access to Exchange servers](control-remote-powershell-access-to-exchange-servers.md). - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612). - -## Open the Exchange Management Shell in Windows Server 2016 or Windows 10 - -Click **Start** > **Microsoft Exchange Server 2016 \>** **Exchange Management Shell**. - -## Open the Exchange Management Shell in Windows Server 2012 R2 or Windows 8.1 - -When you install Exchange on Windows Server 2012 R2 or the Exchange management tools on Windows 8.1, the Exchange Management Shell shortcut isn't automatically pinned to the Start screen. - -To pin the shortcut to the Start screen, do the following: - -1. On the Start screen, open the Apps view by clicking the down arrow near the lower-left corner or swiping up from the middle of the screen. - -2. The **Exchange Management Shell** shortcut is in a group named **Microsoft Exchange Server 2016**. When you find the shortcut, right-click it or press and hold it, and select **Pin to Start**. To pin it to the desktop taskbar, select **Pin to taskbar**. - -To use the Search charm to find and run the Exchange Management Shell, use one of the methods described in the next section. - -## Open the Exchange Management Shell in Windows Server 2012 - -When you install Exchange on Windows Server 2012, the Exchange Management Shell shortcut should automatically be pinned to the Start screen. - -If it's not, or if you just want to quickly find and run the Exchange Management Shell, use one of the following methods: - -- On the Start screen, click an empty area, and type Exchange Management Shell. When the shortcut appears in the search results, you can select it. - -- On the desktop or the Start screen, press Windows key + Q. In the Search charm, type Exchange Management Shell. When the shortcut appears in the results, you can select it. - -- On the desktop or the Start screen, move your cursor to the upper-right corner, or swipe left from the right edge of the screen to show the charms. Click the Search charm, and type Exchange Management Shell. When the shortcut appears in the results, you can select it. - -If you are using Remote Desktop Connection, you might need to use one of the following methods so the Search charm appears on the remote Exchange server and not on your local computer: - -- Open Remote Desktop Connection and click **Show Options** > **Local Resources** tab > **Apply Windows key combinations**. The default value is **Only when using the full screen**, but you can change it to **On the remote computer**. - -- While you're connected to the remote Exchange server, use the connection bar that appears at the top of the screen to open the Exchange server's Search charm or Start screen by clicking the down arrow and selecting **Charms** or **Start**. diff --git a/exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md b/exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md deleted file mode 100644 index e5c1177318..0000000000 --- a/exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md +++ /dev/null @@ -1,318 +0,0 @@ ---- -title: "Filterable properties for the Filter parameter" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: ITPro -ms.topic: article -ms.prod: exchange-server-itpro -localization_priority: Normal -ms.assetid: b02b0005-2fb6-4bc2-8815-305259fa5432 -description: "Learn about the filterable properties for the Filter parameter in Exchange Server and Exchange Online." ---- - -# Filterable properties for the Filter parameter - -You use the _Filter_ parameter to create OPATH filters based on the properties of user and group objects in Exchange Server and Exchange Online. The _Filter_ parameter is available on these recipient cmdlets: - -- [Get-CASMailbox](../../../exchange-ps/exchange/client-access/Get-CASMailbox.md) - -- [Get-Contact](../../../exchange-ps/exchange/users-and-groups/Get-Contact.md) - -- [Get-DistributionGroup](../../../exchange-ps/exchange/users-and-groups/Get-DistributionGroup.md) - -- [Get-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/Get-DynamicDistributionGroup.md) - -- [Get-Group](../../../exchange-ps/exchange/users-and-groups/Get-Group.md) - -- [Get-LinkedUser](../../../exchange-ps/exchange/users-and-groups/Get-LinkedUser.md) - -- [Get-Mailbox](../../../exchange-ps/exchange/mailboxes/Get-Mailbox.md) - -- [Get-MailContact](../../../exchange-ps/exchange/users-and-groups/Get-MailContact.md) - -- [Get-MailPublicFolder](../../../exchange-ps/exchange/sharing-and-collaboration/Get-MailPublicFolder.md) - -- [Get-MailUser](../../../exchange-ps/exchange/users-and-groups/Get-MailUser.md) - -- [Get-Recipient](../../../exchange-ps/exchange/users-and-groups/Get-Recipient.md) - -- [Get-RemoteMailbox](../../../exchange-ps/exchange/federation-and-hybrid/Get-RemoteMailbox.md) - -- [Get-SecurityPrincipal](../../../exchange-ps/exchange/users-and-groups/Get-SecurityPrincipal.md) - -- [Get-UMMailbox](../../../exchange-ps/exchange/unified-messaging/Get-UMMailbox.md) - -- [Get-User](../../../exchange-ps/exchange/users-and-groups/Get-User.md) - -- [Get-UnifiedGroup](../../../exchange-ps/exchange/users-and-groups/Get-UnifiedGroup.md) - -For more information, see [Recipient filters in Exchange PowerShell commands](recipient-filters.md). - -> [!NOTE] -> The _Filter_ parameter is also available on other cmdlets (for example, **Get-MailboxStatistics**, **Get-Queue**, and **Get-Message**). However, the property values that are accepted by the _Filter_ parameter on these cmdlets aren't similar to the user and group properties that are described in this topic. - -## Filterable properties - -The properties that have been _confirmed_ to work with the _Filter_ parameter in user and group cmdlets are described in the following table. - - **Notes**: - -- The list might include: - - - Properties that are only used in one type of environment: Microsoft Office 365, on-premises Exchange, or hybrid. The property might exist on recipient objects in all environments, but the value is only meaningful (a value other than blank or `None`) in one type of environment. - - - Properties that are present, but correspond to features that are no longer used in Exchange 2016 or later. - -- Not all recipient properties have a corresponding Active Directory property. The LDAP display name value in the table is "n/a" for these properties, which indicates that the property is calculated (likely by Exchange). - -- 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. For more information, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information). - -- Text string properties that accept wildcard characters require the `-like` operator (for example, `"Property -like '*abc'"`). - -- To look for blank or non-blank property values, use the value `$null` (for example, `'Property -eq $null'` or `'Property -ne $null'`). - -|**Property name**|**LDAP display name**|**Available on cmdlets**|**Value**|**Comments**| -|:-----|:-----|:-----|:-----|:-----| -|_AcceptMessagesOnlyFrom_|_authOrig_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|This filter requires the distinguished name of the individual recipient (a mailbox, mail user, or mail contact). For example, `Get-DistributionGroup -Filter "AcceptMessagesOnlyFrom -eq 'CN=Yuudai Uchida,CN=Users,DC=contoso,DC=com'"` or `Get-DistributionGroup -Filter "AcceptMessagesOnlyFrom -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of the individual recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_AcceptMessagesOnlyFromDLMembers_|_dLMemSubmitPerms_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the group (a distribution group, mail-enabled security group, or dynamic distribution group). For example, `Get-Mailbox -Filter "AcceptMessagesOnlyFromDLMembers -eq 'CN=Marketing Department,CN=Users,DC=contoso,DC=com'"`. or `Get-Mailbox -Filter "AcceptMessagesOnlyFromDLMembers -eq 'contoso.com/Users/Marketing Department'"`.
To find the distinguished name of the group, replace _\_ with the name, alias, or email address of the group, and run one of these commands: `Get-DistributionGroup -Identity "" | Format-List Name,DistinguishedName` or `Get-DynamicDistributionGroup -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_ActiveSyncAllowedDeviceIDs_|_msExchMobileAllowedDeviceIds_|**Get-CASMailbox**|String (wildcards accepted) or `$null`|A device ID is a text string that uniquely identifies the device. Use the **Get-MobileDevice** cmdlet to see the devices that have ActiveSync partnerships with a mailbox. To see the device IDs on a mailbox, replace _\_ with the name, alias, or email address of the mailbox, and run this command: `Get-MobileDevice -Mailbox | Format-List`.
After you have the device ID value, you can use it in the filter. For example, `Get-CasMailbox -Filter "(ActiveSyncAllowedDeviceIDs -like '*text1') -or (ActiveSyncAllowedDeviceIDs -eq 'text2'"`.| -|_ActiveSyncBlockedDeviceIDs_|_msExchMobileBlockedDeviceIds_|**Get-CASMailbox**|String (wildcards accepted) or `$null`|A device ID is a text string that uniquely identifies the device. Use the **Get-MobileDevice** cmdlet to see the devices that have ActiveSync partnerships with a mailbox. To see the device IDs on a mailbox, replace _\_ with the name, alias, or email address of the mailbox, and run this command: `Get-MobileDevice -Mailbox | Format-List`.
After you have the device ID value, you can use it in a filter. For example, `Get-CasMailbox -Filter "(ActiveSyncBlockedDeviceIDs -like '*text1') -or (ActiveSyncBlockedDeviceIDs -eq 'text2'"`.| -|_ActiveSyncEnabled_|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)|For example, `Get-CasMailbox -Filter 'ActiveSyncEnable -eq $false'`.| -|_ActiveSyncMailboxPolicy_|_msExchMobileMailboxPolicyLink_|**Get-CASMailbox**
**Get-Recipient**|String or `$null`|This filter requires the distinguished name of the ActiveSync mailbox policy. For example, `Get-CASMailbox -Filter "ActiveSyncMailboxPolicy -eq 'CN=Default,CN=Mobile Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of ActiveSync mailbox policies by running this command: `Get-MobileDeviceMailboxPolicy | Format-List Name,DistinguishedName`.
**Note**: For the default assignment of the default ActiveSync mailbox policy (named Default) to a mailbox, the value of the **ActiveSyncMailboxPolicy** property is blank (`$null`).| -|_ActiveSyncSuppressReadReceipt_|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)|For example, `Get-CasMailbox -Filter 'ActiveSyncSuppressReadReceipt -eq $true'`.| -|_AddressBookPolicy_|_msExchAddressBookPolicyLink_|**Get-Mailbox**
**Get-Recipient**|String or `$null`|This filter requires the distinguished name of the address book policy. For example, `Get-Mailbox -Filter "AddressBookPolicy -eq 'CN=Contoso ABP,CN=AddressBook Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of address book policies by running this command: `Get-AddressBookPolicy | Format-List Name,DistinguishedName`.| -|_AddressListMembership_|_showInAddressBook_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|This filter requires the distinguished name of the address list. For example, `Get-MailContact -Filter "AddressListMembership -eq 'CN=All Contacts,CN=All Address Lists,CN=Address Lists Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of address lists by running this command: `Get-AddressList | Format-List Name,DistinguishedName`.| -|_AdminDisplayName_|_adminDisplayName_|**Get-SecurityPrincipal**|String (wildcards accepted) or `$null`|For example, `Get-SecurityPrincipal -Filter 'AdminDisplayName -ne $null' | Format-Table -Auto Name,AdminDisplayName`.| -|_AdministrativeUnits_|_msExchAdministrativeUnitLink_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|String or `$null`|For example, `Get-User -Filter 'AdministrativeUnits -ne $null'`.| -|_AggregatedMailboxGuids_|_msExchAlternateMailboxes_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|For example, `Get-Mailbox -Filter 'AggregatedMailboxGuids -ne $null'`.| -|_Alias_|_mailNickname_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted)|For example, `Get-Recipient -Filter "Alias -like '*smith'"`.| -|_AllowUMCallsFromNonUsers_|_msExchUMListInDirectorySearch_|**Get-Contact**
**Get-LinkedUser**
**Get-UMMailbox**
**Get-User**|`None` (0) or `SearchEnabled` (1)|For example, `Get-User -Filter "AllowUMCallsFromNonUsers -ne 'SearchEnabled'"`.| -|_ArbitrationMailbox_|_msExchArbitrationMailbox_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|This filter requires the distinguished name of the arbitration mailbox. For example, `Get-DistributionGroup -Filter "ArbitrationMailbox -eq 'CN=SystemMailbox"1f05a927-2e8f-4cbb-9039-2cfb8b95e486",CN=Users,DC=contoso,DC=com'"`.
You can find the distinguished names of arbitration mailboxes by running this command: `Get-Mailbox -Arbitration | Format-List Name,DistinguishedName`.| -|_ArchiveDatabase_|_msExchArchiveDatabaseLink_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`|This filter requires the distinguished name of the archive mailbox database. For example, `Get-Mailbox -Filter "ArchiveMailbox -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`.| -|_ArchiveDomain_|_msExchArchiveAddress_|**Get-Mailbox**|String (wildcards accepted) or `$null`|This property is used in on-premises Exchange environments to identify the Office 365 organization that holds the archive mailbox. For example, `Get-Mailbox -Filter "ArchiveDomain -like '*contoso.onmicrosoft.com'"`.| -|_ArchiveGuid_|_msExchArchiveGUID_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`|This filter requires the GUID of the archive mailbox. For example, `Get-Mailbox -Filter "ArchiveMailbox -eq '6476f55e-e5eb-4462-a095-f2cb585d648d'"`.
You can find the GUID of archive mailboxes by running this command: `Get-Mailbox -Archive | Format-Table -Auto Name,ArchiveGUID`.| -|_ArchiveName_|_msExchArchiveName_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`|This filter requires the name of the archive mailbox. For example, `Get-Mailbox -Filter "ArchiveName -like 'In-Place Archive*'"`.
You can find the names of archive mailboxes by running this command: `Get-Mailbox -Archive | Format-Table -Auto Name,ArchiveName`.| -|_ArchiveQuota_|_msExchArchiveQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ArchiveQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ArchiveQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ArchiveQuota - ''"`. For example, `Get-Mailbox | where "$_.ArchiveQuota -gt '85GB'"`.| -|_ArchiveRelease_|_msExchArchiveRelease_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**|`None`, `E14`, `E15`, or `$null`.|For example, `Get-Recipient -Filter 'ArchiveRelease -ne $null'`.| -|_ArchiveState_|n/a|**Get-Mailbox**
**Get-Recipient**
**Get-RemoteMailbox**|`None` (0), `Local` (1), `HostedProvisioned` (2), `HostedPending` (3), or `OnPremise` (4).|For example, `Get-Recipient -Filter "ArchiveState -eq 'HostedProvisioned'"`.| -|_ArchiveStatus_|_msExchArchiveStatus_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|`None` (0) or `Active` (1).|For example, `Get-Recipient -Filter "ArchiveStatus -eq 'Active'"`.| -|_ArchiveWarningQuota_|_msExchArchiveWarnQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ArchiveWarningQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ArchiveWarningQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ArchiveWarningQuota - ''"`. For example, `Get-Mailbox | where "$_.ArchiveWarningQuota -gt '85GB'"`.| -|_AssistantName_|_msExchAssistantName_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "AssistantName -like 'Julia*'"`.| -|_AuditEnabled_|_msExchMailboxAuditEnable_|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'AuditEnabled -eq $true'`.| -|_AuditLogAgeLimit_|_msExchMailboxAuditLogAgeLimit_|**Get-Mailbox**
**Get-UnifiedGroup**|A time span value: _dd.hh:mm:ss_ where _dd_ = days, _hh_ = hours, _mm_ = minutes, and _ss_ = seconds.|You can't use the _Filter_ parameter to look for time span values for this property. Instead, use this syntax: `Get-Mailbox | where "$_.AuditLogAgeLimit - ''"`. For example, `Get-Mailbox | where "$_.AuditLogAgeLimit -gt '60.00:00:00'"`.| -|_AuthenticationPolicy_|_msExchAuthPolicyLink_|**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "AuthenticationPolicy -eq 'CN=Block Basic Auth,CN=Auth Policies,CN=Configuration,CN=contoso.onmicrosoft.com,CN=ConfigurationUnits,DC=NAMPR11B009,DC=PROD,DC=OUTLOOK,DC=COM'"`.| -|_BlockedSendersHash_|_msExchBlockedSendersHash_|**Get-Recipient**|Blank ( `$null`) or a hashed value.|Realistically, you can only use this value to filter on blank or non-blank values. For example, `Get-Recipient -Filter 'BlockedSendersHash -ne $null'.`| -|_c_|_c_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|String (wildcards accepted) or `$null`|This filter requires the ISO 3166-1 two-letter country code for the user (for example, `S` for the United States). This property is used together with the _co_ and _countryCode_ properties to define the user's country in Active Directory.
For example, `Get-User -Filter "c -eq 'US'"`.| -|_CalendarLoggingQuota_|_msExchCalendarLoggingQuota_|**Get-Mailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "CalendarLoggingQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "CalendarLoggingQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.CalendarLoggingQuota - ''"`. For example, `Get-Mailbox | where "$_.CalendarLoggingQuota -gt '10GB'"`.| -|_CalendarRepairDisabled_|_msExchCalendarRepairDisabled_|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'CalendarRepairDisabled -eq $true'`.| -|_CertificateSubject_|n/a|**Get-LinkedUser**
**Get-User**|String or `$null`|The X509 certificate that's published for the user account (visible on the **Published Certificates** tab in Active Directory Users and Computers).
For example, `Get-User -Filter "CertificateSubject -eq 'X509:C=US,O=InternetCA,CN=APublicCertificateAuthorityC=US,O=Fabrikam,OU=Sales,CN=Jeff Smith`')| -|_City_|_l_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "City -eq 'Redmond'"`.| -|_Company_|_company_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Company -like 'Contoso*'"`.| -|_ComplianceTagHoldApplied_|n/a|**Get-Mailbox**
**Get-MailUser**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'ComplianceTagHoldApplied -eq $true'`.| -|_ConsumerNetID_|n/a|**Get-LinkedUser**
**Get-User**|String or `$null`|For example, `Get-User -Filter 'ConsumerNetID -ne $null'`.| -|_CountryCode_|_countryCode_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|Integer|This filter requires the ISO 3166-1 three-digit country code for the user (for example, `840` for the United States). This property is used together with the _c_ and _co_ properties to define the user's country in Active Directory.
For example, `Get-User -Filter "countryCode -eq 796"`.| -|_CountryOrRegion_|_co_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|String|This filter requires the ISO 3166-1 country name for the user (for example, `United States`). You can select an available value in Active Directory Users and Computers ( **Address** tab > **Country/region** field), or the Exchange admin center (user properties > **Contact information** tab > **Country/Region** field).
When you select a user's country in Active Directory Users and Computers or the EAC, the corresponding values for the _co_ and _countryCode_ properties are automatically configured.
For example, `Get-User -Filter "CountryOrRegion -like 'United*'"`.| -|_CustomAttribute1_ to _CustomAttribute15_|_extensionAttribute1_ to _extensionAttribute15_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`|For example, `Get-Recipient -Filter "CustomAttribute8 -like '*audited*'"`.| -|_Database_|_homeMDB_|**Get-Mailbox**
**Get-Recipient**|String|This filter requires the distinguished name of the mailbox database. For example, `Get-Mailbox -Filter "Database -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`.| -|_DefaultPublicFolderMailbox_|_msExchPublicFolderMailbox_|**Get-Mailbox**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the public folder mailbox. For example, `Get-Mailbox -Filter "DefaultPublicFolderMailbox -eq 'CN=PF Mailbox01,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "DefaultPublicFolderMailbox -eq 'contoso.com/Users/PF Mailbox01'"`.
To find the distinguished names of public folder mailboxes, run this command: `Get-Mailbox -PublicFolder | Format-List Name,DistinguishedName`.| -|_DeletedItemFlags_|_deletedItemFlags_|**Get-Mailbox**
**Get-SecurityPrincipal**|`DatabaseDefault` (0), `RetainUntilBackupOrCustomPeriod` (3), or `RetainForCustomPeriod` (5).|For example, `Get-Mailbox -Filter "DeletedItemFlags -ne 'DatabaseDefault'"`.| -|_DeliverToMailboxAndForward_|_deliverAndRedirect_|**Get-Mailbox**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-MailPublicFolder**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'DeliverToMailboxAndForward -eq $true'`.| -|_Department_|_department_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-Recipient -Filter "Department -like 'Engineering*'"`.| -|_DirectReports_|_directReports_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the direct report. For example, `Get-User -Filter "DirectReports -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-User -Filter "DirectReports -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a direct report, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_DisabledArchiveDatabase_|_msExchDisabledArchiveDatabaseLink_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|This filter requires the distinguished name of the disabled archive mailbox database. For example, `Get-Mailbox -Filter "DisabledArchiveDatabase -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`.| -|_DisabledArchiveGuid_|_msExchDisabledArchiveDatabaseGUID_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|This filter requires the GUID of the disabled archive mailbox. For example, `Get-Mailbox -Filter "DisabledArchiveGuid -eq '6476f55e-e5eb-4462-a095-f2cb585d648d'"`.
You can find the GUID of archive mailboxes by running this command: `Get-Mailbox -Archive | Format-Table -Auto Name,ArchiveGUID`.| -|_DisplayName_|_displayName_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted)|For example, `Get-Recipient -Filter "DisplayName -like 'Julia*'"`.| -|_DistinguishedName_|_distinguishedName_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**
**Get-UnifiedGroup**|String|This filter requires the distinguished name of the recipient. For example, `Get-Mailbox -Filter "DistinguishedName -eq 'CN=Basho Kato,CN=Users,DC=contoso,DC=com'"`.
You can find the distinguished names of recipients by running this command: `Get-Recipient | Format-List Name,RecipientType,DistinguishedName`.| -|_EcpEnabled_|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)|For example, `Get-CASMailbox -Filter 'EcpEnabled -eq $false'`.| -|_EmailAddresses_|_proxyAddresses_|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-UnifiedGroup**|String (wildcards accepted)|For example, `Get-Recipient -Filter "EmailAddresses -like '*marketing*'"`.
When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"EmailAddresses -eq 'lila@fabrikam.com'"` returns a match, `"EmailAddresses -like 'lila*'"` won't return a match, but `"EmailAddresses -like '*lila*'"` or `"EmailAddresses -like 'smtp:lila*'"` will return a match.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_EmailAddressPolicyEnabled_|n/a|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-Recipient -Filter 'EmailAddressPolicyEnabled -eq $false'`.| -|_EntryId_|_msExchPublicFolderEntryId_|**Get-MailPublicFolder**|String (wildcards accepted)|For example, `Get-MailPublicFolder -Filter "EntryId -like '*60000'"`.
You can find the entry IDs of mail-enabled public folders by running this command: `Get-MailPublicFolder | Format-List Name,EntryId`.| -|_EwsApplicationAccessPolicy_|_msExchEwsApplicationAccessPolicy_|**Get-CASMailbox**|`EnforceAllowList`, `EnforceBlockList`. or `$null`|For example, `Get-CASMailbox -Filter 'EwsApplicationAccessPolicy -ne $null'`.| -|_EwsEnabled_|_msExchEwsEnabled_|**Get-CASMailbox**|0 (disabled), 1 (enabled) or `$null`.|For example, `Get-CASMailbox -Filter "EwsEnabled -eq 1"`.| -|_ExchangeGuid_|_msExchMailboxGuid_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String|For example, `Get-Mailbox -Filter "ExchangeGuid -eq 'c80a753d-bd4a-4e19-804a-6344d833ecd8'"`.
To find the Exchange GUID of a recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,ExchangeGuid`.
Note that an object's Exchange GUID value is different than its GUID value. Also, the Exchange GUID value for non-mailboxes (mail contacts, mail users, distribution groups, dynamic distribution groups, mail-enabled security groups, and mail-enabled public folders) is `00000000-0000-0000-0000-000000000000`.| -|_ExchangeUserAccountControl_|_msExchUserAccountControl_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|`None` (0) or `AccountDisabled` (2)|For example, `Get-Mailbox -Filter "ExchangeUserAccountControl -eq 'AccountDisabled'"`.| -|_ExchangeVersion_|_msExchVersion_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**|Integer|This property contains the earliest version of Exchange that you can use to manage the recipient. The property values that you see are different than the values that you need to use in the filter. To see the **ExchangeVersion** property values, run this command: `Get-Recipient | Format-Table Name,RecipientType,ExchangeVersion`.
For the Exchange 2010 value `0.10 (14.0.100.0)`, use the value 44220983382016 in the filter.
For the Exchange 2013 or Exchange 2016 value `0.20 (15.0.0.0)`, use the value 88218628259840 in the filter.
For example, `Get-Recipient -Filter "ExchangeVersion -lt 88218628259840"`.| -|_ExpansionServer_|_msExchExpansionServerName_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Recipient**|String (wildcards accepted) or `$null`|For example, `Get-Recipient -Filter "ExpansionServer -like '*Mailbox01'"`.
For an exact match, you need to use the **ExchangeLegacyDN** value of the server. For example, `Get-Recipient -Filter "ExpansionServer -eq '/o=Contoso Corporation/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01'"`
You can find the **ExchangeLegacyDN** value by running this command: `Get-ExchangeServer | Format-List Name,ExchangeLegacyDN`.| -|_ExtensionCustomAttribute1_ to _ExtensionCustomAttribute5_|_msExchExtensionCustomAttribute1_ to _msExchExtensionCustomAttribute5_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`|For example, `Get-Recipient -Filter "ExtensionCustomAttribute8 -like '*audited*'"`.| -|_ExternalDirectoryObjectId_|_msExchExternalDirectoryObjectId_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|String or `$null`|For example, `Get-Recipient -Filter 'ExternalDirectoryObjectId -ne $null'`.| -|_ExternalEmailAddress_|_targetAddress_|**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**|String (wildcards accepted) or `$null`|For example, `Get-Recipient -Filter "ExternalEmailAddress -like '*@fabrikam.com'"`.
When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ExternalEmailAddress -eq 'lila@fabrikam.com'"` returns a match, `"ExternalEmailAddress -like 'lila*'"` won't return a match, but `"ExternalEmailAddress -like '*lila*'"` or `"ExternalEmailAddress -like 'smtp:lila*'"` will return a match.| -|_ExternalOofOptions_|_msExchExternalOOFOptions_|**Get-Mailbox**|`External` (0) or `InternalOnly` (1)|For example, `Get-Mailbox -Filter "ExternalOofOptions -eq 'External'"`.| -|_Fax_|_facsimileTelephoneNumber_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Fax -like '206*'"`.| -|_FirstName_|_givenName_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "FirstName -like 'Chris*'"`.| -|_ForwardingAddress_|_altRecipient_|**Get-Mailbox**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the forwarding recipient. For example, `Get-Mailbox -Filter "ForwardingAddress -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "ForwardingAddress -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a forwarding recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.| -|_ForwardingSmtpAddress_|_msExchGenericForwardingAddress_|**Get-Mailbox**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter "ForwardingSmtpAddress -like '*@fabrikam.com'"`.
When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ForwardingSmtpAddress -eq 'lila@fabrikam.com'"` returns a match, `"ForwardingSmtpAddress -like 'lila*'"` won't return a match, but `"ForwardingSmtpAddress -like '*lila*'"` or `"ForwardingSmtpAddress -like 'smtp:lila*'"` will return a match.| -|_GeneratedOfflineAddressBooks_|_msExchOABGeneratingMailboxBL_|**Get-Mailbox**|String or `$null`|This property is only meaningful on arbitration mailboxes, so you need to use the _Arbitration_ switch in the filter command. Also, This filter requires the distinguished name of the offline address book. For example, `Get-Mailbox -Arbitration -Filter "GeneratedOfflineAddressBooks -eq 'CN=OAB 1,CN=Offline Address Lists,CN=Address Lists Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of offline address books by running this command: `Get-OfflineAddressBook | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_GrantSendOnBehalfTo_|_publicDelegates_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the mail-enabled security principal (mailbox, mail user, or mail-enabled security group). For example, `Get-Mailbox -Filter "GrantSendOnBehalfTo -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "GrantSendOnBehalfTo -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a mail-enabled security principal, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_GroupMemberCount_|_n/a_|**Get-UnifiedGroup**|Integer|For example, `Get-UnifiedGroup -Filter "GroupMemberCount -gt 100"`.| -|_GroupExternalMemberCount_|_n/a_|**Get-UnifiedGroup**|Integer|For example, `Get-UnifiedGroup -Filter "GroupExternalMemberCount -gt 0"`.| -|_GroupType_|_groupType_|**Get-DistributionGroup**
**Get-Group**
**Get-UnifiedGroup**|`None` (0), `Global` (2), `DomainLocal` (4), `BuiltinLocal` (5), `Universal` (8), or `SecurityEnabled` (-2147483648).|Distribution groups have the value `Universal`, and mail-enabled security groups have the value `Universal, SecurityEnabled`. You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-DistributionGroup -Filter "GroupType -eq 'Universal,SecurityEnabled'"` returns the same results as `Get-DistributionGroup -Filter "GroupType -eq 'SecurityEnabled,Universal'"`.
This multivalued property will only return a match if the property *equals* the specified value.| -|_Guid_|_objectGuid_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**
**Get-UnifiedGroup**|String|For example, `Get-Recipient -Filter "Guid -eq '8a68c198-be28-4a30-83e9-bffb760c65ba'"`.
You can find the GUIDs of recipients by running this command: `Get-Recipient | Format-List Name,RecipientType,Guid`.
Note that an object's GUID value is different than its Exchange GUID value.| -|_HasActiveSyncDevicePartnership_|n/a|**Get-CASMailbox**
**Get-Recipient**|Boolean (`$true` or `$false`)|For example, `Get-Recipient -Filter 'HasActiveSyncDevicePartnership -eq $true'`.| -|_HiddenFromAddressListsEnabled_|_msExchHideFromAddressLists_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-Recipient -Filter 'HiddenFromAddressListsEnabled -eq $true'`.| -|_HiddenGroupMembershipEnabled_|_hideDLMembership_|**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-UnifiedGroup -Filter 'HiddenGroupMembershipEnabled -eq $true'`.| -|_HomePhone_|_homePhone_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "HomePhone -like '206*'"`.| -|_Id_|_distinguishedName_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMMailbox**
**Get-User**
**Get-SecurityPrincipal**
**Get-UnifiedGroup**|String|This filter requires the distinguished name or canonical distinguished name of the recipient. For example, `Get-Mailbox -Filter "Id -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "Id -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.| -|_IgnoreMissingFolderLink_|n/a|**Get-MailPublicFolder**|Boolean (`$true` or `$false`)|For example, `Get-MailPublicFolder -Filter 'IgnoreMissingFolderLink -eq $true'`.| -|_ImapEnabled_|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)|For example, `Get-CASMailbox -Filter 'ImapEnabled -eq $false'`.| -|_ImmutableId_|_msExchGenericImmutableId_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|For example, `Get-Mailbox -Filter 'ImmutableId -ne $null'`.| -|_IncludeInGarbageCollection_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IncludeInGarbageCollection -eq $true'`.| -|_Initials_|_initials_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Initials -like 'B.'"`.| -|_InPlaceHolds_|_msExchUserHoldPolicies_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String|This filter requires the **InPlaceHoldIdentity** value of the mailbox search. For example, `Get-Mailbox -Filter "InPlaceHolds -eq '9d0f81154cc64c6b923ecc0be5ced0d7'"`.
To find the **InPlaceHoldIdentity** values of mailbox searches, run this command: `Get-MailboxSearch | Format-Table Name,InPlaceHoldIdentity`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_InPlaceHoldsRaw_|n/a|**Get-LinkedUser**
**Get-User**|String|This filter requires the **InPlaceHoldIdentity** value of the mailbox search. For example, `Get-Mailbox -Filter "InPlaceHoldsRaw -eq '9d0f81154cc64c6b923ecc0be5ced0d7'"`.
To find the **InPlaceHoldIdentity** values of mailbox searches, run this command: `Get-MailboxSearch | Format-Table Name,InPlaceHoldIdentity`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_IsDirSynced_|_msExchIsMSODirsynced_|**Get-Contact**
**Get-DistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-User -Filter 'IsDirSynced -eq $true'`.| -|_IsExcludedFromServingHierarchy_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsExcludedFromServingHierarchy -eq $true'`.| -|_IsHierarchyReady_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsHierarchyReady -eq $false'`.| -|_IsHierarchySyncEnabled_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsHierarchySyncEnabled -eq $false'`.| -|_IsInactiveMailbox_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsInactiveMailbox -eq $false'`.| -|_IsLinked_|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-User**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsLinked -eq $true'`.| -|_IsMailboxEnabled_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsMailboxEnabled -eq $false'`.| -|_IsResource_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsResource -eq $true'`.| -|_IsSecurityPrincipal_|n/a|**Get-LinkedUser**
**Get-User**|Boolean (`$true` or `$false`)|For example, `Get-User -Filter 'IsSecurityPrincipal -eq $false'`.| -|_IsShared_|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsShared -eq $true'`.| -|_IsSoftDeletedByDisable_|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsSoftDeletedByDisable -eq $true'`.| -|_IsSoftDeletedByRemove_|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'IsSoftDeletedByRemove -eq $true'`.| -|_IssueWarningQuota_|_mDBStorageQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "IssueWarningQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "IssueWarningQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.IssueWarningQuota - ''`". For example, `Get-Mailbox | where "$_.IssueWarningQuota -lt '50GB'"`.| -|_JournalArchiveAddress_|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String|This property uses an SMTP email address. For example, `Get-Mailbox -Filter "JournalArchiveAddress -eq 'michelle@contoso.com'"`.| -|_LanguagesRaw_|_msExchUserCulture_|**Get-Mailbox**|String (wildcards accepted) or `$null`|This property is named **Languages** in the properties of a mailbox, and it contains the language preference for the mailbox in the format `-`. For example, United States English is `en-US`. For more information, see [CultureInfo Class](https://go.microsoft.com/fwlink/p/?LinkID=255174).
You can specify multiple values separated by commas, but the order matters. For example, `Get-Mailbox -Filter "LanguagesRaw -eq 'en-US,es-MX'"` returns different results than `Get-Mailbox -Filter "LanguagesRaw -eq 'es-MX,en-US'"`.
For single values, this multivalued property will return a match if the property _contains_ the specified value.| -|_LastExchangeChangedTime_|_msExchLastExchangeChangedTime_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|`$null` or a date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-Mailbox -Filter 'LastExchangeChangedTime -ne $null'`.| -|_LegacyExchangeDN_|_legacyExchangeDN_|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted)|For example, `Get-User -Filter "LegacyExchangeDN -like '*-Osca'"`.
You can find LegacyExchangeDN values for users by running this command: `Get-User | Format-List Name,LegacyExchangeDN`| -|_LitigationHoldDate_|_msExchLitigationHoldDate_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|`$null` or a date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-Mailbox -Filter "LitigationHoldDate -gt '8/13/2017'"`.| -|_LitigationHoldEnabled_|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'LitigationHoldEnabled -eq $true'`.| -|_LitigationHoldOwner_|_msExchLitigationHoldOwner_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`|This property uses the user principal name of the litigation hold owner. For example, `Get-Mailbox -Filter "LitigationHoldOwner -eq 'agruber@contoso.com'"`.| -|_LastName_|_sn_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "LastName -like 'Martin*'"`.| -|_MailboxContainerGUID_|_msExchMailboxContainerGuid_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|For example, `Get-Mailbox -Filter 'MailboxContainerGUID -ne $null'`.| -|_MailboxMoveBatchName_|_msExchMailboxMoveBatchName_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`|This property includes the name of the migration batch. For example, `Get-Mailbox -Filter "MailboxMoveBatchName -like '*LocalMove 01*'"`.
You can find the names of migration batches by running the **Get-MigrationBatch** command. Note that migration batches that you create in the Exchange admin center use the naming convention `MigrationService:`.| -|_MailboxMoveFlags_|_msExchMailboxMoveFlags_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|For valid values, see the description of the _Flags_ parameter in[Get-MoveRequest](../../../exchange-ps/exchange/move-and-migration/get-moverequest.md).|For example, `Get-Mailbox -Filter "MailboxMoveFlags -ne 'None'"`.
You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-Recipient -Filter "MailboxMoveFlags -eq 'IntraOrg,Pull'"` returns the same results as `Get-Recipient -Filter "MailboxMoveFlags -eq 'Pull,IntraOrg'"`.
This multivalued property will only return a match if the property *equals* the specified value.| -|_MailboxMoveRemoteHostName_|_msExchMailboxMoveRemoteHostName_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`|For example, `Get-Mailbox -Filter 'MailboxMoveRemoteHostName -ne $null'`.| -|_MailboxMoveSourceMDB_|_msExchMailboxMoveSourceMDBLink_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`|This filter requires the distinguished name of the source mailbox database. For example, `Get-Mailbox -Filter "MailboxMoveSourceMDB -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`.| -|_MailboxMoveStatus_|_msExchMailboxMoveStatus_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|For valid values, see the description of the _MoveStatus_ parameter in[Get-MoveRequest](../../../exchange-ps/exchange/move-and-migration/get-moverequest.md).|For example, `Get-Mailbox -Filter "MailboxMoveStatus -eq 'Completed'"`.| -|_MailboxMoveTargetMDB_|_msExchMailboxMoveTargetMDBLink_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`|This filter requires the distinguished name of the target mailbox database. For example, `Get-Mailbox -Filter "MailboxMoveTargetMDB -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`.| -|_MailboxPlan_|_msExchParentPlanLink_|**Get-Mailbox**|String or `$null`|Mailbox plans correspond to Office 365 license types. The availability of a license plans is determined by the selections that you make when you enroll your domain.
For example, `Get-Mailbox -Filter 'MailboxPlan -ne $null'`.| -|_MailboxRelease_|_msExchMailboxRelease_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**|`None`, `E14`, `E15`, or `$null`.|For example, `Get-Recipient -Filter 'MailboxRelease -ne $null'`.| -|_MailTipTranslations_|_msExchSenderHintTranslations_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`|When you use this property in a filter, you need to account for the leading and trailing HTML tags. For example, `Get-DistributionGroup -Filter "MailTipTranslations -like '*is not monitored.*'"`.| -|_ManagedBy_|_managedBy_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-Recipient**
**Get-UnifiedGroup**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the group owner (a mail-enabled security principal, which is a mailbox, mail user, or mail-enabled security group). For example, `Get-Mailbox -Filter "ManagedBy -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "ManagedBy -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a mail-enabled security principal, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_ManagedFolderMailboxPolicy_|_msExchMailboxTemplateLink_|**Get-Mailbox**
**Get-Recipient**|String or `$null`|Managed folder mailbox policies aren't available in Exchange 2013 or later.
For example, `Get-Mailbox -Filter 'ManagedFolderMailboxPolicy -eq $null'`.
This filter requires the distinguished name of the managed folder mailbox policy. For example, `Get-Mailbox -Filter "ManagedFolderMailboxPolicy -eq 'CN=MFM Inbox Policy,CN=ELC Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
You can find the distinguished names of managed folder mailbox policies on Exchange 2010 servers by running this command: `Get-ManagedFolderMailboxPolicy | Format-List Name,DistinguishedName`.| -|_Manager_|_manager_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the manager (a mailbox or mail user). For example, `Get-User -Filter "Manager -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "Manager -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a manager, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName.`| -|_MAPIEnabled_|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)|For example, `Get-CASMailbox -Filter 'MAPIEnabled -eq $false'`.| -|_MasterAccountSid_|_msExchMasterAccountSid_|**Get-Mailbox**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|String or `$null`|For example, `Get-Mailbox -Filter 'MasterAccountSid -ne $null'`.
This value is blank ( `$null`) for mailboxes with associated user accounts, and `S-1-5-10` (Self) for mailboxes without associated user accounts (for example, shared mailboxes, resource mailboxes, discovery search mailboxes, arbitration mailboxes, and public folder mailboxes).| -|_MaxBlockedSenders_|_msExchMaxBlockedSenders_|**Get-Mailbox**|Integer or `$null`|For example, `Get-Mailbox -Filter "MaxBlockedSenders -gt 0"`.| -|_MaxReceiveSize_|_delivContLength_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|A byte quantified size value (for example, `75MB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "MaxReceiveSize -eq 'Unlimited'"` or `Get-Mailbox -Filter "MaxReceiveSize -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.MaxReceiveSize - ''"`. For example, `Get-Mailbox | where "$_.MaxReceiveSize -gt '50GB'"`.| -|_MaxSafeSenders_|_msExchMaxSafeSenders_|**Get-Mailbox**|Integer or `$null`|For example, `Get-Mailbox -Filter "MaxSafeSenders -gt 0"`.| -|_MaxSendSize_|_submissionContLength_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|A byte quantified size value (for example, `75MB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "MaxSendSize -eq 'Unlimited'"` or `Get-Mailbox -Filter "MaxSendSize -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.MaxReceiveSize - ''"`. For example, `Get-Mailbox | where "$_.MaxSendSize -gt '50GB'"`.| -|_MemberDepartRestriction_|_msExchGroupDepartRestriction_|**Get-DistributionGroup**|`Closed` (0), `Open` (1), or `ApprovalRequired` (2).|For example, `Get-DistributionGroup -Filter "MemberDepartRestriction -eq 'ApprovalRequired'"`.| -|_MemberJoinRestriction_|_msExchGroupDepartRestriction_|**Get-DistributionGroup**|`Closed` (0), `Open` (1), or `ApprovalRequired` (2).|For example, `Get-DistributionGroup -Filter "MemberJoinRestriction -eq 'ApprovalRequired'"`.| -|_MemberOfGroup_|_memberOf_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the distribution group or mail-enabled security group. For example, `Get-User -Filter "MemberOfGroup -eq 'CN=Marketing Department,CN=Users,DC=contoso,DC=com'"` or `Get-User -Filter "MemberOfGroup -eq 'contoso.com/Users/Marketing Group'"`.
To find the distinguished name of a group, replace _\_ with the name, alias, or email address of the group, and run this command: `Get-DistributionGroup -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_Members_|_member_|**Get-DistributionGroup**
**Get-Group**
**Get-Recipient**
**Get-SecurityPrincipal**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the group member. For example, `Get-Group -Filter "Members -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-User -Filter "Members -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a group member, replace _\_ with the name, alias, or email address of the group member, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_MobilePhone_|_mobile_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "MobilePhone -like '*5555'"`.| -|_ModeratedBy_|_msExchModeratedByLink_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String|This filter requires the distinguished name or canonical distinguished name of the group moderator (a mail-enabled security principal, which is a mailbox, mail-user, or mail-enabled security group). For example, `Get-DistributionGroup -Filter "ModeratedBy -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-DistributionGroup -Filter "ModeratedBy -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a mail-enabled security principal, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_ModerationEnabled_|_msExchEnableModeration_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-DistributionGroup -Filter 'ModerationEnabled -eq $true'`.| -|_Name_|_name_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted)|For example, `Get-User -Filter "Name -like 'Laura*'"`.| -|_NetID_|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-User**|String or `$null`|This property is populated for Office 365 mailboxes in hybrid environments. A sample value is `1003BFFD9A0CFA03`.
For example, `Get-User -Filter 'NetId -ne $null'`.| -|_Notes_|_info_|**Get-Contact**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Notes -like '*Events Team*'"`.| -|_ObjectCategory_|_objectCategory_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String|This filter requires the canonical distinguished name of the object. The value uses the syntax `/Configuration/Schema/`.
Valid _\_ values are: `Person` for mailboxes, mail users, and mail contacts, `Group` for distribution groups, mail-enabled security groups and Office 365 groups, `ms-Exch-Public-Folder` for mail-enabled public folders, and `ms-Exch-Dynamic-Distribution-List` for dynamic distribution groups.
For example, `Get-Recipient -Filter "ObjectCategory -eq 'contoso.com/Configuration/Schema/Group'"`.| -|_ObjectClass_|_objectClass_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String|The value of this property is `top, person, organizationalPerson, user` for mailboxes and mail users, `top, person, organizationalPerson, contact` for mail contacts, `top, group` for distribution groups, mail-enabled security groups and Office 365 groups, `msExchDynamicDistributionList` for dynamic distribution groups and `top, publicFolder` for mail-enabled public folders
For example, `Get-Recipient -Filter "ObjectClass -eq 'Contact'"`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_Office_|_physicalDeliveryOfficeName_|**Get-Contact**
**Get-LinkedUser**
**Get-Mailbox**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Office -like '22*'"`.| -|_OfflineAddressBook_|_msExchUseOAB_|**Get-Mailbox**|String or `$null`|This filter requires the distinguished name of the offline address book. For example, `Get-Mailbox -Arbitration -Filter "OfflineAddressBook -eq 'CN=OAB 1,CN=Offline Address Lists,CN=Address Lists Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`
You can find the distinguished names of offline address books by running this command: `Get-OfflineAddressBook | Format-List Name,DistinguishedName`.| -|_OnPremisesObjectId_|n/a|**Get-MailPublicFolder**|String or `$null`|For example, `Get-MailPublicFolder -Filter 'OnPremisesObjectId -ne $null'`.| -|_OperatorNumber_|_msExchUMOperatorNumber_|**Get-UMMailbox**|String (wildcards accepted) or `$null`|For example, `Get-UMMailbox -Filter "OperatorNumber -eq 5"`.| -|_OtherFax_|_otherFacsimileTelephoneNumber_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "OtherFax -like '206*'"`.| -|_OtherHomePhone_|_otherHomePhone_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "OtherHomePhone -like '206*'"`.| -|_OtherTelephone_|_otherTelephone_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "OtherTelephone -like '206*'"`.| -|_OWAEnabled_|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)|The filter operates backwards. For example, `Get-CASMailbox -Filter 'OWAEnabled -eq $true'` returns mailboxes where the **OWAEnabled** property is `False`, and `Get-CASMailbox -Filter 'OWAEnabled -eq $false'` returns mailboxes where the **OWAEnabled** property is `True`| -|_OWAforDevicesEnabled_|_msExchOmaAdminWirelessEnable_|**Get-CASMailbox**|Boolean (`$true` or `$false`)|For example, `Get-CASMailbox -Filter 'OWAForDevicesEnabled -eq $true'`.| -|_OWAMailboxPolicy_|_msExchOWAPolicy_|**Get-CASMailbox**
**Get-Recipient**|String or `$null`|This filter requires the distinguished name of the Outlook on the web mailbox policy (formerly known as an Outlook Web App mailbox policy). For example, `Get-CASMailbox -Filter "OWAMailboxPolicy -eq 'CN=Default,CN=OWA Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com`'".
You can find the distinguished names of Outlook on the web mailbox policies by running this command: `Get-OwaMailboxPolicy | Format-List Name,DistinguishedName`.| -|_Pager_|_pager_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Pager -like '206*'"`.| -|_PersistedCapabilities_|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`|Typically, the value of this property something other than `$null` (blank) for Office 365 accounts and mailboxes. For more information about the valid property values, see[Capability enumeration](https://go.microsoft.com/fwlink/p/?linkid=854610).
For example, `Get-Mailbox -Filter 'PersistedCapabilities -ne $null'`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_Phone_|_telephoneNumber_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Phone -like '206*'"`.| -|_PhoneProviderId_|_msExchUMPhoneProvider_|**Get-UMMailbox**|String (wildcards accepted) or `$null`|For example, `Get-UMMailbox -Filter "PhoneProviderId -like '*206*'"`.| -|_PhoneticDisplayName_|_msDS-PhoneticDisplayName_|**Get-Contact**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-MailPublicFolder**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "PhoneticDisplayName -like '*Lila*'"`.| -|_PoliciesExcluded_|_msExchPoliciesExcluded_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|For example, `Get-Recipient -Filter 'PoliciesExcluded -ne $null'`.| -|_PoliciesIncluded_|_msExchPoliciesIncluded_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|For example, `Get-Recipient -Filter 'PoliciesIncluded -eq $null'`.| -|_PopEnabled_|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)|For example, `Get-CASMailbox -Filter 'POPEnabled -eq $false'`.| -|_PostalCode_|_postalCode_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-Recipient -Filter "PostalCode -eq 90210"`.| -|_PostOfficeBox_|_postOfficeBox_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "PostOfficeBox -like '*555*'"`.| -|_PreviousRecipientTypeDetails_|_msExchPreviousRecipientTypeDetails_|**Get-LinkedUser**
**Get-User**|String or `$null`|For valid values, see the description of the _RecipientTypeDetails_ parameter in[Get-Recipient](../../../exchange-ps/exchange/users-and-groups/get-recipient.md).
For example, `Get-User -Filter 'PreviousRecipientTypeDetails -ne $null'`.| -|_PrimarySmtpAddress_|n/a|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-UnifiedGroup**|String (wildcards accepted)|For example, `Get-Recipient -Filter "PrimarySMTPAddress -like 'vasil*'"`.| -|_ProhibitSendQuota_|_mDBOverQuotaLimit_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ProhibitSendQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ProhibitSendQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ProhibitSendQuota - ''"`. For example, `Get-Mailbox | where "$_.ProhibitSendQuota -lt '70GB'"`.| -|_ProhibitSendReceiveQuota_|_mDBOverHardQuotaLimit_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ProhibitSendReceiveQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ProhibitSendReceiveQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ProhibitSendReceiveQuota - ''"`. For example, `Get-Mailbox | where "$_.ProhibitSendReceiveQuota -lt '70GB'"`.| -|_ProtocolSettings_|_protocolSettings_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`|The default value of this property on mailboxes is `RemotePowerShell§1`. This property is populated with additional values when you use Set-CASMailbox to disable protocols (for example, POP3 or IMAP4).
For example, `Get-Mailbox -Filter "ProtocolSettings -like '*POP3*'"`.| -|_PublicFolderContacts_|_pFContacts_|**Get-MailPublicFolder**|String or `$null`|This property is displayed as **Contacts** in the results of the command `Get-MailPublicFolder -Identity | Format-List`, but you need to use the property name **PublicFolderContacts** in the filter.
This filter requires the distinguished name or canonical distinguished name of the public folder contact. For example, `Get-MailPublicFolder -Filter "PublicFolderContacts -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-MailPublicFolder -Filter "PublicFolderContacts -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of a public folder contact, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_QueryBaseDN_|_msExchQueryBaseDN_|**Get-Mailbox**|String or `$null`|This property was used in Exchange 2007 global address list segregation to specify a location in Active Directory. This feature was replaced by address book policies in Exchange 2010 Service Pack 2, so the value of this property should always be blank ( `$null`).
For example, `Get-Mailbox -Filter 'QueryBaseDN -ne $null'`.| -|_RecipientContainer_|_msExchDynamicDLBaseDN_|**Get-DynamicDistributionGroup**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the organizational unit or container in Active Directory. For example, `Get-DynamicDistributionGroup -Filter "RecipientContainer -eq 'CN=Users,DC=contoso,DC=com'"` or `Get-DynamicDistributionGroup -Filter "RecipientContainer -eq 'contoso.com/Users'"`
To find the distinguished names or canonical distinguished names of organizational units and containers in Active Directory, run this command: `Get-OrganizationalUnit -IncludeContainers | Format-List Name,DistinguishedName,ID`.| -|_RecipientLimits_|_msExchRecipLimit_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|Integer or `Unlimited`|For example, `Get-Mailbox -Filter "RecipientLimits -ne 'Unlimited'"`.| -|_RecipientType_|n/a|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-User**
**Get-UnifiedGroup**|`DynamicDistributionGroup`, `MailContact`, `MailNonUniversalGroup`, `MailUniversalDistributionGroup`, `MailUniversalSecurityGroup`, `MailUser`, `PublicFolder` or `UserMailbox`|For example, `Get-Recipient -Filter "RecipientType -eq 'MailContact'"`.| -|_RecipientTypeDetails_|n/a|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-User**
**Get-UnifiedGroup**|String|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](../../../exchange-ps/exchange/users-and-groups/Get-Recipient.md).
For example, `Get-Recipient -Filter "RecipientTypeDetails -eq 'SharedMailbox'"`.| -|_RecoverableItemsQuota_|_msExchDumpsterQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "RecoverableItemsQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "RecoverableItemsQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.RecoverableItemsQuota - ''`. For example, `Get-Mailbox | where "$_.RecoverableItemsQuota -gt '35GB'"`.| -|_RecoverableItemsWarningQuota_|_msExchDumpsterWarningQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.|You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "RecoverableItemsWarningQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "RecoverableItemsWarningQuota -ne 'Unlimited'"`.
You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.RecoverableItemsWarningQuota - ''`". For example, `Get-Mailbox | where "$_.RecoverableItemsWarningQuota -gt '25GB'"`.| -|_RejectMessagesFrom_|_unauthOrig_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|This filter requires the distinguished name of the individual recipient (a mailbox, mail user, or mail contact). For example, `Get-DistributionGroup -Filter "RejectMessagesFrom -eq 'CN=Yuudai Uchida,CN=Users,DC=contoso,DC=com'"` or `Get-DistributionGroup -Filter "RejectMessagesFrom -eq 'contoso.com/Users/Angela Gruber'"`.
To find the distinguished name of the individual recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_RejectMessagesFromDLMembers_|_dLMemRejectPerms_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`|This filter requires the distinguished name or canonical distinguished name of the group (a distribution group, mail-enabled security group, or dynamic distribution group). For example, `Get-Mailbox -Filter "RejectMessagesFromDLMembers -eq 'CN=Marketing Department,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "RejectMessagesFromDLMembers -eq 'contoso.com/Users/Marketing Department'"`.
To find the distinguished name of the group, replace _\_ with the name, alias, or email address of the group, and run one of these commands: `Get-DistributionGroup -Identity "" | Format-List Name,DistinguishedName` or `Get-DynamicDistributionGroup -Identity "" | Format-List Name,DistinguishedName`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_RemoteAccountPolicy_|_msExchSyncAccountsPolicyDN_|**Get-Mailbox**|String or `$null`|This filter requires the distinguished name of the remote account policy. For example, `Get-Mailbox -Filter "RemoteAccountPolicy -eq 'CN=Contoso Remote Account Policy,CN=Remote Accounts Policies Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.| -|_RemotePowerShellEnabled_|n/a|**Get-User**|Boolean (`$true` or `$false`)|For example, `Get-User -Filter 'RemotePowerShellEnabled -eq $false'`.| -|_RemoteRecipientType_|_msExchRemoteRecipientType_|**Get-Mailbox**
**Get-RemoteMailbox**|`None` (0), `ProvisionMailbox` (1), `ProvisionArchive` (2), `Migrated` (4), `DeprovisionMailbox` (8), `DeprovisionArchive` (16), `RoomMailbox` (32), `EquipmentMailbox` (64), `SharedMailbox` (96), `TeamMailbox` (128), or `$null`.|For example, `Get-RemoteMailbox -Filter "RemoteRecipientType -eq 'ProvisionMailbox'"`.| -|_ReportToManagerEnabled_|_reportToOwner_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-DistributionGroup -Filter 'ReportToManagerEnabled -eq $true'`.| -|_ReportToOriginatorEnabled_|_reportToOriginator_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-DistributionGroup -Filter 'ReportToOriginatorEnabled -eq $false'`.| -|_RequireAllSendersAreAuthenticated_|_msExchRequireAuthToSendTo_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**|Boolean (`$true` or `$false`)|This property is displayed as **RequireSenderAuthenticationEnabled** in the results of the command `Get- -Identity | Format-List`, but you need to use the property name **RequireAllSendersAreAuthenticated** in the filter. For example, `Get-DistributionGroup -Filter 'RequireAllSendersAreAuthenticated -eq $false'`.| -|_ResourceBehaviorOptions_|n/a|**Get-UnifiedGroup**|`AllowOnlyMembersToPost`, `CalendarMemberReadOnly`, `ConnectorsEnabled`, `HideGroupInOutlook`, `NotebookForLearningCommunitiesEnabled`, `ReportToOriginator`, `SharePointReadonlyForMembers`, `SubscriptionEnabled`, `SubscribeMembersToCalendarEvents`, `SubscribeMembersToCalendarEventsDisabled`, `SubscribeNewGroupMembers`, `WelcomeEmailDisabled`, `WelcomeEmailEnabled`, or `$null`|For example, `Get-UnifiedGroup -Filter "ResourceBehaviorOptions -eq 'CalendarMemberReadOnly'"`| -|_ResourceCapacity_|_msExchResourceCapacity_|**Get-Mailbox**|Integer or `$null`|For example, `Get-Mailbox -Filter "ResourceCapacity -gt 15"`| -|_ResourceCustom_|n/a|**Get-Mailbox**|String or `$null`|You create custom resource properties by using the Set-ResourceConfig cmdlet. For example, `Set-ResourceConfig -ResourcePropertySchema Room/Whiteboard,Equipment/Van`. After you create the properties, you can assign them to room or equipment mailboxes. For example, `Set-Mailbox -Identity "Conference Room 1" -ResourceCustom Whiteboard`.
When you search for values, use the custom resource property that's assigned to the room or equipment mailbox. For example, `Get-Mailbox -Filter "ResourceCustom -eq 'Whiteboard'"`.| -|_ResourceProvisioningOptions_|n/a|**Get-UnifiedGroup**|`Team` or `$null`|For example, `Get-UnifiedGroup -Filter "ResourceProvisioningOptions -eq 'Team'"`| -|_ResourceType_|n/a|**Get-Mailbox**
**Get-Recipient**|`Room` (0), `Equipment` (1), or `$null`|For example, `Get-Mailbox -Filter "ResourceType -eq 'Equipment'"`| -|_RetainDeletedItemsFor_|_garbageCollPeriod_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A time span value: _dd.hh:mm:ss_ where _dd_ = days, _hh_ = hours, _mm_ = minutes, and _ss_ = seconds.|You can't use the _Filter_ parameter to look for time span values for this property. Instead, use this syntax: `Get-Mailbox | where "$_.RetainDeletedItemsFor - ''"`. For example, `Get-Mailbox | where "$_.RetainDeletedItemsFor -gt '14.00:00:00'"`.| -|_RetentionComment_|_msExchRetentionComment_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter "RetentionComment -like '*7 years*'"`| -|_RetentionPolicy_|n/a|**Get-Mailbox**
**Get-Recipient**|String or `$null`|This filter requires the distinguished name of the retention policy. For example, `Get-Mailbox -Filter "RetentionPolicy -eq 'CN=Default MRM Policy,CN=Retention Policies Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
To find the distinguished names of retention policies, run this command: `Get-RetentionPolicy | Format-List Name,DistinguishedName`.| -|_RetentionUrl_|_msExchRetentionURL_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter "RetentionUrl -like 'https://intranet.contoso.com/*'"`| -|_RoleAssignmentPolicy_|_msExchRBACPolicyLink_|**Get-Mailbox**|String (wildcards accepted) or `$null`|This filter requires the distinguished name of the role assignment policy in Exchange Online. For example, `Get-Mailbox -Filter "RoleAssignmentPolicy -eq 'CN=Default Role Assignment Policy,CN=Policies,CN=RBAC,CN=Configuration,CN=contoso.onmicrosoft.com,CN=ConfigurationUnits,DC=NAMPR10A001,DC=PROD,DC=OUTLOOK,DC=COM'"`.
To find the distinguished names of role assignment policies in Exchange Online, run this command: `Get-RoleAssignmentPolicy | Format-List Name,DistinguishedName`.| -|_RulesQuota_|_msExchMDBRulesQuota_|**Get-Mailbox**|A byte quantified size value (for example, `50B` or `128KB`). Unqualified values are treated as bytes.|You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.RulesQuota - ''"`. For example, `Get-Mailbox | where "$_.RulesQuota -lt '256KB'"`.| -|_SafeRecipientsHash_|_msExchSafeRecipientsHash_|**Get-Recipient**|Blank ( `$null`) or a hashed value.|Realistically, you can only use this value to filter on blank or non-blank values. For example, `Get-Recipient -Filter 'SafeRecipientsHash -ne $null'.`| -|_SafeSendersHash_|_msExchSafeSendersHash_|**Get-Recipient**|Blank ( `$null`) or a hashed value.|Realistically, you can only use this value to filter on blank or non-blank values. For example, `Get-Recipient -Filter 'SafeSendersHash -ne $null'.`| -|_SamAccountName_|_SamAccountName_|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-Recipient -Filter "SamAccountName -like '*laura*'"`| -|_SCLDeleteThresholdInt_|_msExchMessageHygieneSCLDeleteThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`|This property is displayed as **SCLDeleteThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLDeleteThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLDeleteThresholdInt -ge -2147483640"`.| -|_SCLJunkThresholdInt_|_msExchMessageHygieneSCLJunkThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`|This property is displayed as **SCLJunkThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLJunkThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLJunkThresholdInt -ge -2147483645"`.| -|_SCLQuarantineThresholdInt_|_msExchMessageHygieneSCLQuarantineThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`|This property is displayed as **SCLQuarantineThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLQuarantineThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLQuarantineThresholdInt -ge -2147483643"`.| -|_SCLRejectThresholdInt_|_msExchMessageHygieneSCLRejectThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`|This property is displayed as **SCLRejectThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLRejectThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLRejectThresholdInt -ge -2147483641"`.| -|_SendOofMessageToOriginatorEnabled_|_oOFReplyToOriginator_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)|For example, `Get-DistributionGroup -Filter 'SendOofMessageToOriginatorEnabled -eq $true'`.| -|_ServerLegacyDN_|_msExchHomeServerName_|**Get-CASMailbox**
**Get-Mailbox**
**Get-Recipient**
**Get-UMMailbox**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter "ServerLegacyDN -like '*Mailbox01'"`.
This is an example of a complete **ServerLegacyDN** value: `/o=Contoso Corporation/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01`.| -|_ServerName_|n/a|**Get-CASMailbox**
**Get-Mailbox**
**Get-Recipient**
**Get-UMMailbox**|String or `$null`|For example, `Get-Recipient -Filter "ServerName -eq 'Mailbox01'"`.| -|_SharingPolicy_|_msExchSharingPolicyLink_|**Get-Mailbox**
**Get-Recipient**|String or `$null`|This filter requires the distinguished name of the sharing policy. For example, `Get-Mailbox -Filter "SharingPolicy -eq 'CN=Custom Sharing Policy,CN=Federation,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
To find the distinguished names of sharing policies, run this command: `Get-SharingPolicy | Format-List Name,DistinguishedName`.
**Note**: For the default assignment of the default sharing policy (named Default Sharing Policy) to a mailbox, the value of the **SharingPolicy** property is blank (`$null`).| -|_Sid_|_objectSid_|**Get-Group**
**Get-LinkedUser**
**Get-SecurityPrincipal**
**Get-User**|String|For example, `Get-User -Filter "Sid -eq 's-1-5-21-3628364307-1600040346-819251021-2603'"`.| -|_SidHistory_|_SIDHistory_|**Get-Group**
**Get-LinkedUser**
**Get-User**|String or `$null`|For example, `Get-User -Filter "SidHistory -eq 's-1-5-21-3628364307-1600040346-819251021-2603'"`.| -|_SimpleDisplayName_|_displayNamePrintable_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "SimpleDisplayName -like '*lila*'"`.| -|_SingleItemrecoveryEnabled_|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'SingleItemRecoveryEnabled -eq $true'`.| -|_SKUAssigned_|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-User**|Boolean (`$true` or `$false`) or `$null`.|For example, `Get-User -Filter 'SKUAssigned -eq $true'`.| -|_SourceAnchor_|n/a|**Get-Mailbox**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter 'SourceAnchor -ne $null'`.| -|_StateOrProvince_|_st_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "StateOrProvince -like '*Carolina'"`.| -|_StreetAddress_|_streetAddress_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "StreetAddress -like '*36th Ave NE*'"`.| -|_StsRefreshTokensValidFrom_|_msExchStsRefreshTokensValidFrom_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|`$null` or a date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-User -Filter "StsRefreshTokensValidFrom -gt '8/1/2017'"`.| -|_TelephoneAssistant_|_telephoneAssistant_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "TelephoneAssistant -like '206*'"`.| -|_ThrottlingPolicy_|_msExchThrottlingPolicyDN_|**Get-Mailbox**|String or `$null`|This filter requires the distinguished name of the throttling policy. For example, `Get-Mailbox -Filter "ThrottlingPolicy -eq 'CN=Custom Throttling Policy,CN=Global Settings,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
To find the distinguished names of throttling policies, run this command: `Get-ThrottlingPolicy | Format-List Name,DistinguishedName`.| -|_Title_|_title_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "Title -eq 'Dr.'"`.| -|_UMAddresses_|_msExchUMAddresses_|**Get-UMMailbox**|String (wildcards accepted) or `$null`|For example, `Get-UMMailbox -Filter 'UMAddresses -ne $null'`.| -|_UMCallingLineIds_|_msExchUMCallingLineIds_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "UMCallingLineIds -like '123*'"`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_UMDtmfMap_|_msExchUMDtmfMap_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter "UMDtmfMap -like '*26297*'"`.
Although this is a multivalued property, the filter will return a match if the property _contains_ the specified value.| -|_UMEnabled_|n/a|**Get-Mailbox**
**Get-Recipient**
**Get-UMMailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'UMEnabled -eq $true'`.| -|_UMMailboxPolicy_|_msExchUMTemplateLink_|**Get-Recipient**
**Get-UMMailbox**|String or `$null`|This filter requires the distinguished name of the UM mailbox policy. For example, `Get-Recipient -Filter "UMMailboxPolicy -eq 'CN=Contoso Default Policy,CN=UM Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
To find the distinguished names of UM mailbox policies, run this command: `Get-UMMailboxPolicy | Format-List Name,DistinguishedName`.| -|_UMRecipientDialPlanId_|_msExchUMRecipientDialPlanLink_|**Get-Recipient**|String or `$null`|This filter requires the distinguished name of the UM dial plan. For example, `Get-Recipient -Filter "UMMailboxPolicy -eq 'CN=Contoso Dial Plan,CN=UM DialPlan Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`.
To find the distinguished names of UM dial plans, run this command: `Get-UMDialPlan | Format-List Name,DistinguishedName`.| -|_UpgradeRequest_|n/a|**Get-User**|`None` (0), `TenantUpgrade` (1), `PrestageUpgrade` (2), `CancelPrestageUpgrade` (3), `PilotUpgrade` (4), or `TenantUpgradeDryRun` (5),|For example, `Get-User -Filter "UpgradeRequest -ne 'None'"`.| -|_UpgradeStatus_|n/a|**Get-User**|`None` (0), `NotStarted` (1), `InProgress` (2), `Warning` (3), `Error` (4), `Cancelled` (5), `Complete` (6), or `ForceComplete` (7).|For example, `Get-User -Filter "UpgradeStatus -ne 'None'"`.| -|_UsageLocation_|_msExchUsageLocation_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**|String or `$null`|This filter requires the ISO 3166-1 country name (for example, `United States`), or two-letter country code (for example `US`) for the user in Office 365. For more information, see [Country Codes - ISO 3166](https://go.microsoft.com/fwlink/p/?linkid=213779).
For example, `Get-Recipient -Filter 'UsageLocation -ne $null'`.| -|_UseDatabaseQuotaDefaults_|_mDBUseDefaults_|**Get-Mailbox**|Boolean (`$true` or `$false`)|For example, `Get-Mailbox -Filter 'UseDatabaseQuotaDefaults -eq $false'`.| -|_UserAccountControl_|_userAccountControl_|**Get-LinkedUser**
**Get-User**|`AccountDisabled`, `DoNotExpirePassword`, or `NormalAccount`|For example, `Get-User -Filter "UserAccountControl -eq 'NormalAccount'"`.
You can specify multiple values separated by commas, but the order matters. For example, `Get-User -Filter "UserAccountControl -eq 'AccountDisabled,NormalAccount'"` returns different results than `Get-User -Filter "UserAccountControl -eq 'NormalAccount,AccountDisabled'"`.
This multivalued property will only return a match if the property *equals* the specified value.| -|_UserPrincipalName_|_userPrincipalName_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|String (wildcards accepted)|For example, `Get-User -Filter "UserPrincipalName -like 'julia@*'"`.| -|_VoiceMailSettings_|_msExchUCVoiceMailSettings_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String or `$null`|For example, `Get-User -Filter 'VoiceMailSettings -ne $null'`.| -|_WebPage_|_wWWHomePage_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-User -Filter "WebPage -like 'https://intranet.contoso.com/*'"`.| -|_WhenChanged_|_WhenChanged_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-Recipient -Filter "WhenChanged -gt '8/1/2017 2:00:00 PM'"`.| -|_WhenChangedUTC_|n/a|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-Recipient -Filter "WhenChangedUTC -gt '8/1/2017 2:00:00 PM'"`.| -|_WhenCreated_|_whenCreated_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-Recipient -Filter "WhenCreated -gt '8/1/2017 2:00:00 PM'"`.| -|_WhenCreatedUTC_|n/a|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-Recipient -Filter "WhenCreatedUTC -gt '8/1/2017 2:00:00 PM'"`.| -|_WhenMailboxCreated_|_msExchWhenMailboxCreated_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|For example, `Get-Recipient -Filter "WhenMailboxCreated -gt '8/1/2017 2:00:00 PM'"`.| -|_WhenSoftDeleted_|_msExchWhenSoftDeletedTime_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)|This filter requires the _SoftDeleted_ switch in the command for mailboxes.
For example, `Get-Mailbox -SoftDeleted -Filter "WhenSoftDeleted -gt '8/1/2017 2:00:00 PM'"`.| -|_WindowsEmailAddress_|_mail_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter "WindowsEmailAddress -like '*@fabrikam.com'"`.| -|_WindowsLiveID_|_msExchWindowsLiveID_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`|For example, `Get-Mailbox -Filter "WindowsEmailAddress -like '*@fabrikam.onmicrosoft.com'"`.| - -## For more information - -Exchange 2007 was the first version of Exchange that required OPATH filters instead of LDAP filters. For more information about converting LDAP filters to OPATH filters, see the Microsoft Exchange Team Blog article, [Need help converting your LDAP filters to OPATH?](https://go.microsoft.com/fwlink/p/?LinkId=88854). - -For more information about the syntax that can be used within OPATH filters, see [Exchange cmdlet syntax](../exchange-cmdlet-syntax.md). diff --git a/exchange/docs-conceptual/exchange-server/recipient-filters/recipient-filters.md b/exchange/docs-conceptual/exchange-server/recipient-filters/recipient-filters.md deleted file mode 100644 index 1eda7382d6..0000000000 --- a/exchange/docs-conceptual/exchange-server/recipient-filters/recipient-filters.md +++ /dev/null @@ -1,278 +0,0 @@ ---- -title: "Recipient filters in Exchange PowerShell commands" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: ITPro -ms.topic: reference -ms.prod: exchange-server-itpro -localization_priority: Normal -ms.assetid: fb4b1396-9aae-4037-be1a-b09e336b890e -description: "Learn about creating different kinds of recipient filters in the Exchange Management Shell and Exchange Online PowerShell." ---- - -# Recipient filters in Exchange PowerShell commands - -You can use several Exchange Management Shell and Exchange Online PowerShell commands to filter a set of recipients. You can create the following types of filters in an Exchange command: - -- Precanned filters - -- Custom filters using the _RecipientFilter_ parameter - -- Custom filters using the _Filter_ parameter - -- Custom filters using the _ContentFilter_ parameter - -Older versions of Exchange used LDAP filtering syntax to create custom address lists, global address lists (GALs), email address policies, and distribution groups. In Exchange Server 2007 and later versions, OPATH filtering syntax replaced LDAP filtering syntax. - -## Precanned filters - -A precanned filter is a commonly used Exchange filter that you can use to meet a variety of recipient-filtering criteria for creating dynamic distribution groups, email address policies, address lists, or GALs. With precanned filters, you can use either the Exchange PowerShell or the Exchange admin center (EAC). Using precanned filters, you can do the following: - -- Determine the scope of recipients. - -- Add conditional filtering based on properties such as company, department, and state or region. - -- Add custom attributes for recipients. For more information, see [Custom Attributes](https://docs.microsoft.com/Exchange/recipients/mailbox-custom-attributes). - -The following parameters are considered precanned filters: - -- _IncludedRecipients_ - -- _ConditionalCompany_ - -- _ConditionalDepartment_ - -- _ConditionalStateOrProvince_ - -- _ConditionalCustomAttribute1_ to _ConditionalCustomAttribute15_. - -Precanned filters are available for the following cmdlets: - -- [New-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/new-dynamicdistributiongroup.md) - -- [Set-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/set-dynamicdistributiongroup.md) - -- [New-EmailAddressPolicy](../../../exchange-ps/exchange/email-addresses-and-address-books/new-emailaddresspolicy.md) - -- [Set-EmailAddressPolicy](../../../exchange-ps/exchange/email-addresses-and-address-books/set-emailaddresspolicy.md) - -- [New-AddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/new-addresslist.md) - -- [Set-AddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/set-addresslist.md) - -- [New-GlobalAddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/new-globaladdresslist.md) - -- [Set-GlobalAddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/set-globaladdresslist.md) - -### Precanned filter example - -This example describes using precanned filters in the Exchange Management Shell to create a dynamic distribution group. The syntax in this example is similar but not identical to the syntax you would use to create an email address policy, address list, or GAL. When creating a precanned filter, you should ask the following questions: - -- From which organizational unit (OU) do you want to include recipients? (This question corresponds to the _RecipientContainer_ parameter.) - -> [!NOTE] -> Selecting the OU for this purpose applies only when creating dynamic distribution groups, and not when creating email address policies, address lists, or GALs. - -- What type of recipients do you want to include? (This question corresponds to the _IncludedRecipients_ parameter.) - -- What additional conditions do you want to include in the filter? (This question corresponds to the _ConditionalCompany_, _ConditionalDepartment_, _ConditionalStateOrProvince_, and _ConditionalCustomAttribute_ parameters.) - -This example creates the dynamic distribution group Contoso Finance for user mailboxes in the OU Contoso.com/Users and specifies the condition to include only recipients who have the **Department** attribute defined as Finance and the **Company** attribute defined as Contoso. - -```PowerShell -New-DynamicDistributionGroup -Name "Contoso Finance" -OrganizationalUnit Contoso.com/Users -RecipientContainer Contoso.com/Users -IncludedRecipients MailboxUsers -ConditionalDepartment "Finance" -ConditionalCompany "Contoso" -``` - -This example displays the properties of this new dynamic distribution group. - -```PowerShell -Get-DynamicDistributionGroup -Identity "Contoso Finance" | Format-List Recipient*,Included* -``` - -## Custom filters using the RecipientFilter parameter - -If precanned filters don't meet your needs for creating or modifying dynamic distribution groups, email address policies, and address lists, you can create a custom filter by using the _RecipientFilter_ parameter. - -The recipient filter parameter is available for the following cmdlets: - -- [New-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/new-dynamicdistributiongroup.md) - -- [Set-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/set-dynamicdistributiongroup.md) - -- [New-EmailAddressPolicy](../../../exchange-ps/exchange/email-addresses-and-address-books/new-emailaddresspolicy.md) - -- [Set-EmailAddressPolicy](../../../exchange-ps/exchange/email-addresses-and-address-books/set-emailaddresspolicy.md) - -- [New-AddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/new-addresslist.md) - -- [Set-AddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/set-addresslist.md) - -- [New-GlobalAddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/new-globaladdresslist.md) - -- [Set-GlobalAddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/set-globaladdresslist.md) - -For more information about the filterable properties you can use with the _RecipientFilter_ parameter, see [Filterable properties for the RecipientFilter parameter](recipientfilter-properties.md). - -### Custom filter example - -The following example uses the _RecipientFilter_ parameter to create a dynamic distribution group. The syntax in this example is similar but not identical to the syntax you use to create an email address policy, address list, or GAL. - -This example uses custom filters to create a dynamic distribution group for user mailboxes that have the **Company** attribute defined as Contoso and the **Office** attribute defined as North Building. - -```PowerShell -New-DynamicDistributionGroup -Name AllContosoNorth -OrganizationalUnit contoso.com/Users -RecipientFilter "((RecipientType -eq 'UserMailbox') -and (Company -eq 'Contoso') -and (Office -eq 'North Building'))" -``` - -## Custom filters using the Filter parameter - -You can use the _Filter_ parameter to filter the results of a command to specify which objects to retrieve. For example, instead of retrieving all users or groups, you can specify a set of users or groups by using a filter string. This type of filter doesn't modify any configuration or attributes of objects. It only modifies the set of objects that the command returns. - -Using the _Filter_ parameter to modify command results is known as server-side filtering. Server-side filtering submits the command and the filter to the server for processing. We also support client-side filtering, in which the command retrieves all objects from the server and then applies the filter in the local console window. To perform client-side filtering, use the **Where-Object** cmdlet. For more information about server-side and client-side filtering, see "How to Filter Data" in [Working with Command Output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). - -To find the filterable properties for cmdlets that have the _Filter_ parameter, you can run the **Get** command against an object and format the output by pipelining the **Format-List** parameter. Most of the returned values will be available for use in the _Filter_ parameter. The following example returns a detailed list for the mailbox Ayla. - -```PowerShell -Get-Mailbox -Identity Ayla | Format-List -``` - -The _Filter_ parameter is available for the following recipient cmdlets: - -- [Get-CASMailbox](../../../exchange-ps/exchange/client-access/get-casmailbox.md) - -- [Get-Contact](../../../exchange-ps/exchange/users-and-groups/get-contact.md) - -- [Get-DistributionGroup](../../../exchange-ps/exchange/users-and-groups/get-distributiongroup.md) - -- [Get-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/get-dynamicdistributiongroup.md) - -- [Get-Group](../../../exchange-ps/exchange/users-and-groups/get-group.md) - -- [Get-Mailbox](../../../exchange-ps/exchange/mailboxes/get-mailbox.md) - -- [Get-MailContact](../../../exchange-ps/exchange/users-and-groups/get-mailcontact.md) - -- [Get-MailPublicFolder](../../../exchange-ps/exchange/sharing-and-collaboration/get-mailpublicfolder.md) - -- [Get-MailUser](../../../exchange-ps/exchange/users-and-groups/get-mailuser.md) - -- [Get-Recipient](../../../exchange-ps/exchange/users-and-groups/get-recipient.md) - -- [Get-RemoteMailbox](../../../exchange-ps/exchange/federation-and-hybrid/get-remotemailbox.md) - -- [Get-SecurityPrincipal](../../../exchange-ps/exchange/users-and-groups/get-securityprincipal.md) - -- [Get-UMMailbox](../../../exchange-ps/exchange/unified-messaging/get-ummailbox.md) - -- [Get-User](../../../exchange-ps/exchange/users-and-groups/get-user.md) - -- [Get-UnifiedGroup](../../../exchange-ps/exchange/users-and-groups/Get-UnifiedGroup.md) - -For more information about the filterable properties you can use with the _Filter_ parameter, see [Filterable properties for the Filter parameter](filter-properties.md). - -### Example - -This example uses the _Filter_ parameter to return information about users whose title contains the word "manager". - -```PowerShell -Get-User -Filter "Title -like 'Manager*'" -``` - -## Custom filters using the ContentFilter parameter - -You can use the _ContentFilter_ parameter to select specific message content to export when using the [New-MailboxExportRequest](../../../exchange-ps/exchange/mailboxes/new-mailboxexportrequest.md) cmdlet. If the command finds a message that contains the match to the content filter, it exports the message to a .pst file. - -### ContentFilter parameter example - -This example creates an export request that searches Ayla's mailbox for messages where the body contains the phrase "company prospectus". If that phrase is found, the command exports all messages with that phrase to a .pst file. - -```PowerShell -New-MailboxExportRequest -Mailbox Ayla -ContentFilter "Body -like 'company prospectus*'" -``` - -For more information about the filterable properties that you can use with the _ContentFilter_ parameter, see [Filterable properties for the ContentFilter parameter](https://docs.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). - -## Additional OPATH syntax information - -When creating your own custom OPath filters, consider the following items: - -- Use the following syntax to identify the types of values that you're searching for: - - - **Text values**: Enclose the text in single quotation marks (for example, `'Value'` or `'Value with spaces'`). Or, you can enclose a text value in double quotation marks, but that limits the characters you can use to enclose the whole OPath filter. - - - **Variables**: Enclose variables that need to be expanded in single quotation marks (for example, `'$User'`). If the variable value itself contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. - - - **Integer values**: You don't need to enclose integers (for example, `500`). You can often enclose integers in single quotation marks or double quotation marks, but that limits the characters you can use to enclose the whole OPath filter. - - - **System values**: Don't enclose system values (for example, `$true`, `$false`, or `$null`). To enclose the whole OPath filter in double quotation marks, you need to escape the dollar sign in system value (for example, `` `$true``). - -- You need to enclose the whole OPath filter in double quotation marks " or " single quotation marks ' '. Although any OPath filter object is technically a string and not a script block, you can still use braces { }, but only if the filter doesn't contain variables that require expansion. The characters that you can use to enclose the whole OPath filter depend on types of values that you're searching for and the characters you used (or didn't use) to enclose those values: - - - **Text values**: Depends on how you enclosed the text to search for: - - - **Text enclosed in single quotation marks**: Enclose the whole OPath filter in double quotation marks or braces. - - - **Text enclosed in double quotation marks**: Enclose the whole OPath filter in braces. - - - **Variables**: Enclose the whole OPath filter in double quotation marks (for example, `"Name -eq '$User'"`). - - - **Integer values**: Depends on how you enclosed (or didn't enclose) the integer to search for: - - - **Integer not enclosed**: Enclose the whole OPath filter in double quotation marks, single quotation marks, or braces (for example `"CountryCode -eq 840"`). - - - **Integer enclosed in single quotation marks**: Enclose the whole OPath filter in double quotation marks or braces `"CountryCode -eq '840'"`. - - - **Integer enclosed in double quotation marks**: Enclose the whole OPath filter in braces (for example `{CountryCode -eq "840"}`). - - - **System values**: Enclose the whole OPath filter in single quotation marks or braces (for example `'HiddenFromAddressListsEnabled -eq $true'`). If you escape the dollar sign system value, you can also enclose the whole OPath filter in double quotation marks (for example, ``"HiddenFromAddressListsEnabled -eq `$true"``). - - The compatibility of search criteria and the valid characters that you can use to enclose the whole OPath filter are summarized in the following table: - - |**Search value**|**OPath filter enclosed
in double quotation marks**|**OPath filter enclosed
in single quotation marks**|**OPath filter enclosed
in braces**| - |:-----|:-----:|:-----:|:-----:| - |`'Text'`|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)||![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)| - |`"Text"`|||![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)| - |`'$Variable'`|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)||| - |`500`|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)| - |`'500'`|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)||![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)| - |`"500"`|||![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)| - |`$true`||![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)| - |`` `$true``|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)|![Check mark](../../media/f3b4c351-17d9-42d9-8540-e48e01779b31.png)| - -- Include the hyphen before all operators. The most common operators include: - - - **-and** - - - **-or** - - - **-not** - - - **-eq** (equals) - - - **-ne** (not equal) - - - **-lt** (less than) - - - **-gt** (greater than) - - - **-like** (string comparison) - - - **-notlike** (string comparison) - -- Many filterable properties accept wildcard characters. If you use a wildcard character, use the **-like** operator instead of the **-eq** operator. The **-like** operator is used to find pattern matches in rich types (for example, strings) whereas the **-eq** operator is used to find an exact match. - -- For more information about operators you can use, see: - - - [about_Logical_Operators](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_logical_operators) - - - [about_Comparison_Operators](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators) - -## Recipient filter documentation - -The following table contains links to topics that will help you learn more about the filterable properties that you can use with Exchange recipient commands. - -|**Topic**|**Description**| -|:-----|:-----| -|[Filterable properties for the RecipientFilter parameter](recipientfilter-properties.md)|Learn more about the filterable properties that are available for the _RecipientFilter_ parameter.| -|[Filterable properties for the Filter parameter](filter-properties.md) |Learn more about the filterable properties that are available for the _Filter_ parameter.| diff --git a/exchange/docs-conceptual/exchange-server/use-update-exchangehelp.md b/exchange/docs-conceptual/exchange-server/use-update-exchangehelp.md deleted file mode 100644 index 1a9a417180..0000000000 --- a/exchange/docs-conceptual/exchange-server/use-update-exchangehelp.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -title: "Use Update-ExchangeHelp to update Exchange PowerShell help topics on Exchange servers" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: ITPro -ms.topic: article -ms.prod: exchange-server-itpro -localization_priority: Normal -ms.assetid: 219f78a3-f0e5-4dc6-9787-9a0b9756ee09 -description: "Administrators can learn how to use Update-ExchangeHelp to update Exchange cmdlet reference topics that are available in Exchange Management Shell in Exchange 2016" ---- - -# Use Update-ExchangeHelp to update Exchange PowerShell help topics on Exchange servers - -Exchange cmdlet reference topics are created and updated all the time, but it's been difficult to get those updates into Exchange code in a timely manner so they're available in the Exchange Management Shell. Now, you can use the **Update-ExchangeHelp** cmdlet in the Exchange Management Shell to get the most up-to-date cmdlet reference topics for the command line in Exchange 2013 or later. - -The **Update-ExchangeHelp** cmdlet automatically connects to a predefined website, compares the version of the local Exchange server and the installed languages to what's available in the update packages, and then downloads and installed the updated Exchange Management Shell help. Typically, the cmdlet connects to the internet, but you can configure it to connect to an intranet source inside your organization. - -## What do you need to know before you begin? - -- Estimated time to complete: - - - Use **Update-ExchangeHelp** on a single Internet-connected Exchange server: less than 5 minutes. - - - Configure **Update-ExchangeHelp** to get updates from an internal web server: 30 minutes. - -- You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Exchange server configuration settings" entry in the [Exchange infrastructure and PowerShell permissions](https://docs.microsoft.com/Exchange/permissions/feature-permissions/infrastructure-permissions) topic. - -- You can only use PowerShell to perform this procedure. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see [Open the Exchange Management Shell](open-the-exchange-management-shell.md). - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612). - -## Use Update-ExchangeHelp on a single Internet-connected Exchange server - -This method requires that the Exchange server has direct access to the Internet. - -Run the following command in the Exchange Management Shell: - -```PowerShell -Update-ExchangeHelp -Verbose -``` - - **Notes:** - -- The _Verbose_ switch is important because it provides useful information. For example, it tells you if your Exchange server already has the latest version of help installed, or if you've run the command in the last 24 hours. - -- If you want to check for updates again within 24 hours, use the _Force_ switch. - -## Configure Update-ExchangeHelp to get updates from an internal web server - -In some organizations, internal servers don't have access to the Internet. If your internal Exchange servers don't have Internet access, you can configure **Update-ExchangeHelp** to point to an internal web server to get updates. The steps are as follows: - -1. Download and inspect the ExchangeHelpInfo.xml manifest file. - -2. Download the update packages, publish the update packages on an internal web server, and customize the ExchangeHelpInfo.xml manifest file. - -3. Publish the customized ExchangeHelpInfo.xml manifest file on an internal web server. - -4. Modify the registry of the Exchange servers to point to the customized ExchangeHelpInfo.xml manifest file. - -5. Use and maintenance of **Update-ExchangeHelp**. - -### Step 1. Download and inspect the ExchangeHelpInfo.xml manifest file - -On a computer that has Internet access, open [https://go.microsoft.com/fwlink/p/?LinkId=287244](https://go.microsoft.com/fwlink/p/?LinkId=287244), save the ExchangeHelpInfo.xml manifest file in a location that's easy to remember, and open the file in Notepad. - -Each available update package is defined in a **\** section, and each **\** section contains the following keys. - -- **\**: This key identifies the version Exchange that the update package applies to. `15.01.xxxx.xxx` is Exchange 2016. `15.00.xxxx.xxx` is Exchange 2013. Typically, this key specifies a range of versions. - -- **\**: This key identifies the language that the update package applies to. This key might specify only one language or multiple languages. - -- **\**: This key identifies the order that the updated packages were released for the major version of Exchange. In other words, the first update package released for Exchange 2016 is `001`, the second is `002`, etc. And, there's no relationship between the update packages and the order they were released in. For example, `001` might be an English only update, `002` might be an update for all other supported languages, and `003` might be a German-only update. - -- **\**: This key identifies the name and location of the update package for the **\** section. - -The update package that's defined in a **\** section applies to an Exchange server based on the combination of **\** and **\** values. - -You might find that multiple **\** sections apply to your Exchange servers for a given version of Exchange. For example, there might be multiple updates for the same language, or separate updates for different languages that both apply to your Exchange servers because you have multiple languages installed. Either way, you need only the most recent update for your Exchange server version and language based on the **\** key. - -For example, suppose your Exchange servers are running Exchange 2016 version `15.01.0225.040` with English and Spanish installed, and the ExchangeHelpInfo.xml manifest file looks like this: - -```xml - - - - - 15.01.0225.030-15.01.0225.050 - 001 - en - https://download.microsoft.com/download/8/7/0/870FC9AB-6D22-4478-BFBF-66CE775BCD18/ExchangePS_Update_En.cab - - - 15.01.0225.030-15.01.0225.050 - 002 - de, es, fr, it, ja, ko, pt, pu, ru, zh-HanS, zh-HanT - https://download.microsoft.com/download/8/7/0/870FC9AB-6D22-4478-BFBF-66CE775BCD18/ExchangePS_Update_Loc.cab - - - 15.01.0225.030-15.01.0225.050 - 003 - en - https://download.microsoft.com/download/8/7/0/870FC9AB-6D22-4478-BFBF-66CE775BCD18/ExchangePS_Update_En2.cab - - - -``` - -In this example, all the updates apply to you based on the version of Exchange. However, you need only revision `003` for English, and revision `002` for Spanish. You don't need revision `001` for English because revision `003` is newer. - -### Step 2. Download the update packages, publish the update packages on an internal web server, and customize the ExchangeHelpInfo.xml manifest file - -The easiest and least time-consuming approach might be to download every available update package that's defined in the ExchangeHelpInfo.xml manifest file. The benefits to this approach are: - -- **No analysis required**: It's difficult to make a mistake and accidentally miss an update that applies to you, because you're downloading every available update package. The **Update-ExchangeHelp** cmdlet ignores the update packages that don't apply to the Exchange server, so it doesn't hurt to download unneeded update packages. - -- **Easier maintenance**: Whenever a new update package is released, you don't need to spend time determining if the update package applies to you. You just download and customize the new ExchangeHelpInfo.xml manifest file, and download the new cabinet (.cab) file that's defined in it. - -To download all of the update packages, follow these steps: - -1. Download all of the .cab files that are defined in the ExchangeHelpInfo.xml manifest file by using the **\** values. Save the files in a location that's easy to remember. - -2. Publish the .cab files on an internal web server (for example `https://intranet.contoso.com/downloads/exchange`). - -3. Modify the URL values of the **\** keys to point to the internal web server where you published the .cab files. - - For example, change the value `https://download.microsoft.com/download/8/7/0/870FC9AB-6D22-4478-BFBF-66CE775BCD18/ExchangePS_Update_En.cab` to `https://intranet.contoso.com/downloads/exchange/ExchangePS_Update_En.cab`. - -4. Save the customized ExchangeHelpInfo.xml manifest file. - -The drawback to this approach is you download more .cab files than you actually need, and the unneeded .cab files consume space on your internal web server. - -If you want to identify only the update packages that apply to you, follow these steps. - -1. Find the version details for your Exchange servers. - - To find the version details on a single Exchange server, run the following command: - - ```PowerShell - Get-Command Exsetup.exe | ForEach {$_.FileVersionInfo} - ``` - - To find the version details for all Exchange servers in your organization, run the following command: - - ```PowerShell - Get-ExchangeServer | Sort-Object Name | ForEach {Invoke-Command -ComputerName $_.Name -ScriptBlock {Get-Command ExSetup.exe | ForEach{$_.FileVersionInfo}}} | Format-Table -Auto - ``` - - The result for **ProductVersion** will be in the format `15.01.0225.xxx`. - -2. Find the **\** sections in the ExchangeHelpInfo.xml manifest file that apply to your Exchange servers based on the values of the **\**, **\**, and **\** keys. The methodology was described in Step 1. - -After you identify the update packages that apply to you, follow these steps: - -1. Download the applicable .cab files by using the **\** values. Save the files in a location that's easy to remember. - -2. Publish the .cab files on an internal web server (for example `https://intranet.contoso.com/downloads/exchange`). - -3. Modify the URL values of the **\** keys to point to the internal web server where you published the .cab files. - - For example, change the value `https://download.microsoft.com/download/8/7/0/870FC9AB-6D22-4478-BFBF-66CE775BCD18/ExchangePS_Update_En.cab` to `https://intranet.contoso.com/downloads/exchange/ExchangePS_Update_En.cab`. - -4. Optionally, you can delete the **\** sections that don't apply to you. - -5. Save the customized ExchangeHelpInfo.xml manifest file. - -### Step 3. Publish the customized ExchangeHelpInfo.xml manifest file on an internal web server - -Publish the customized ExchangeHelpInfo.xml manifest file from Step 2 on an internal web server that's accessible to your internal Exchange servers. For example, `https://intranet.contoso.com/downloads/exchange/ExchangeHelpInfo.xml`. You'll use the URL value of this location in Step 4. - -Note that there's no relationship between the ExchangeHelpInfo.xml manifest file and .cab file locations. You can have them available at the same URL or on different servers. - -### Step 4. Modify the registry of your Exchange servers to point to the customized ExchangeHelpInfo.xml manifest file - -You need the download location of the customized ExchangeHelpInfo.xml manifest file that you configured in Step 3. This example uses the value `https://intranet.contoso.com/downloads/exchange/ExchangeHelpInfo.xml`. - -1. Copy and paste the following text into Notepad, customize the URL for your environment, and save the file as UpdateExchangeHelp.reg in a location that's easy to remember. - - ```text - Windows Registry Editor Version 5.00 - - [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\UpdateExchangeHelp] - "ManifestUrl"="https://intranet.contoso.com/downloads/exchange/ExchangeHelpInfo.xml" - ``` - -2. Run the UpdateExchangeHelp.reg file on your internal Exchange servers. - -### Step 5. Use and maintenance of Update-ExchangeHelp - -Now, when you run **Update-ExchangeHelp** in the Exchange Management Shell on your internal Exchange servers, the command gets download information and downloads files from the internal locations you specified. - -More interesting is the long-term maintenance of this customized configuration. Basically, you'll need to repeat Step 1 through Step 3 when you discover an update has been made available for Exchange cmdlet reference help, and you want to deploy that updated help to your Exchange servers. - -An easy way to find new update packages is to periodically run **Update-ExchangeHelp** on an Internet-connected Exchange server, or computer that has the Exchange management tools installed. - -## Details about Update-ExchangeHelp - -Windows PowerShell has the **Update-Help** and **Save-Help** cmdlets for online and offline updates of cmdlet reference topics. However, these cmdlets don't support Exchange cmdlet help, so a specific Exchange cmdlet is required to update cmdlet reference topics in the Exchange Management Shell. diff --git a/exchange/docs-conceptual/filter-properties.md b/exchange/docs-conceptual/filter-properties.md new file mode 100644 index 0000000000..acd6c6bdeb --- /dev/null +++ b/exchange/docs-conceptual/filter-properties.md @@ -0,0 +1,2182 @@ +--- +title: "Filterable properties for the Filter parameter" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 1/9/2024 +ms.audience: ITPro +audience: ITPro +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: b02b0005-2fb6-4bc2-8815-305259fa5432 +description: "Learn about the filterable properties for the Filter parameter in Exchange Server and Exchange Online." +--- + +# Filterable properties for the Filter parameter on Exchange cmdlets + +You use the _Filter_ parameter to create OPATH filters based on the properties of user and group objects in the Exchange Management Shell (Exchange Server PowerShell) and in Exchange Online PowerShell. The _Filter_ parameter is available on these recipient cmdlets: + +- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox) +- [Get-Contact](/powershell/module/exchange/get-contact) +- [Get-DistributionGroup](/powershell/module/exchange/get-distributiongroup) +- [Get-DynamicDistributionGroup](/powershell/module/exchange/get-dynamicdistributiongroup) +- [Get-Group](/powershell/module/exchange/get-group) +- [Get-LinkedUser](/powershell/module/exchange/get-linkeduser) +- [Get-Mailbox](/powershell/module/exchange/get-mailbox) +- [Get-MailContact](/powershell/module/exchange/get-mailcontact) +- [Get-MailPublicFolder](/powershell/module/exchange/get-mailpublicfolder) +- [Get-MailUser](/powershell/module/exchange/get-mailuser) +- [Get-Recipient](/powershell/module/exchange/get-recipient) +- [Get-RemoteMailbox](/powershell/module/exchange/get-remotemailbox) +- [Get-SecurityPrincipal](/powershell/module/exchange/get-securityprincipal) +- [Get-UMMailbox](/powershell/module/exchange/get-ummailbox) +- [Get-User](/powershell/module/exchange/get-user) +- [Get-UnifiedGroup](/powershell/module/exchange/get-unifiedgroup) + +For more information about _recipient_ filters in Exchange PowerShell, see [Recipient filters in Exchange PowerShell commands](recipient-filters.md). + +> [!NOTE] +> The _Filter_ parameter is also available on other cmdlets (for example, **Get-MailboxStatistics**, **Get-Queue**, and **Get-Message**). However, the property values that are accepted by the _Filter_ parameter on these cmdlets aren't similar to the user and group properties that are described in this article. + +The properties that have been _confirmed_ to work with the _Filter_ parameter in user and group cmdlets are described in this article. + + **Notes**: + +- The list might include: + - Properties that are used only in one type of environment: Microsoft 365, on-premises Exchange, or hybrid. The property might exist on recipient objects in all environments, but the value is meaningful (a value other than blank or `None`) only in one type of environment. + - Properties that are present, but correspond to features that are no longer used. + +- Not all recipient properties have a corresponding Active Directory property. The LDAP display name value is "n/a" for these properties, which indicates that the property is calculated (likely by Exchange). + +- 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 the _Filter_ parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables. For more information, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information). + +- Text string properties that accept wildcard characters require the `-like` operator (for example, `"Property -like 'abc*'"`). + +- To look for blank or non-blank property values, use the value `$null` (for example, `'Property -eq $null'` or `'Property -ne $null'`). + +- For filtering considerations for the nine exclusive **Get-EXO\*** cmdlets in the Exchange Online PowerShell module, see [Filters in the Exchange Online PowerShell module](filters-v2.md). + +## AcceptMessagesOnlyFrom + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_authOrig_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +This filter requires the distinguished name of the individual recipient (a mailbox, mail user, or mail contact). For example, `Get-DistributionGroup -Filter "AcceptMessagesOnlyFrom -eq 'CN=Yuudai Uchida,CN=Users,DC=contoso,DC=com'"` or `Get-DistributionGroup -Filter "AcceptMessagesOnlyFrom -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of the individual recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## AcceptMessagesOnlyFromDLMembers + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_dLMemSubmitPerms_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the group (a distribution group, mail-enabled security group, or dynamic distribution group). For example, `Get-Mailbox -Filter "AcceptMessagesOnlyFromDLMembers -eq 'CN=Marketing Department,CN=Users,DC=contoso,DC=com'"`. or `Get-Mailbox -Filter "AcceptMessagesOnlyFromDLMembers -eq 'contoso.com/Users/Marketing Department'"`. + +To find the distinguished name of the group, replace _\_ with the name, alias, or email address of the group, and run one of these commands: `Get-DistributionGroup -Identity "" | Format-List Name,DistinguishedName` or `Get-DynamicDistributionGroup -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## ActiveSyncAllowedDeviceIDs + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMobileAllowedDeviceIds_|**Get-CASMailbox**|String (wildcards accepted) or `$null`| + +A device ID is a text string that uniquely identifies the device. Use the **Get-MobileDevice** cmdlet to see the devices that have ActiveSync partnerships with a mailbox. To see the device IDs on a mailbox, replace _\_ with the name, alias, or email address of the mailbox, and run this command: `Get-MobileDevice -Mailbox | Format-List`. + +After you have the device ID value, you can use it in the filter. For example, `Get-CasMailbox -Filter "(ActiveSyncAllowedDeviceIDs -like 'text1*') -or (ActiveSyncAllowedDeviceIDs -eq 'text2'"`. + +## ActiveSyncBlockedDeviceIDs + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMobileBlockedDeviceIds_|**Get-CASMailbox**|String (wildcards accepted) or `$null`| + +A device ID is a text string that uniquely identifies the device. Use the **Get-MobileDevice** cmdlet to see the devices that have ActiveSync partnerships with a mailbox. To see the device IDs on a mailbox, replace _\_ with the name, alias, or email address of the mailbox, and run this command: `Get-MobileDevice -Mailbox | Format-List`. + +After you have the device ID value, you can use it in a filter. For example, `Get-CasMailbox -Filter "(ActiveSyncBlockedDeviceIDs -like 'text1*') -or (ActiveSyncBlockedDeviceIDs -eq 'text2'"`. + +## ActiveSyncEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-CasMailbox -Filter 'ActiveSyncEnable -eq $false'`. + +## ActiveSyncMailboxPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMobileMailboxPolicyLink_|**Get-CASMailbox**
**Get-Recipient**|String or `$null`| + +This filter requires the distinguished name of the ActiveSync mailbox policy. For example, `Get-CASMailbox -Filter "ActiveSyncMailboxPolicy -eq 'CN=Default,CN=Mobile Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of ActiveSync mailbox policies by running this command: `Get-MobileDeviceMailboxPolicy | Format-List Name,DistinguishedName`. + +> [!NOTE] +> For the default assignment of the default ActiveSync mailbox policy (named Default) to a mailbox, the value of the **ActiveSyncMailboxPolicy** property is blank (`$null`). + +## ActiveSyncSuppressReadReceipt + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-CasMailbox -Filter 'ActiveSyncSuppressReadReceipt -eq $true'`. + +## AddressBookPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchAddressBookPolicyLink_|**Get-Mailbox**
**Get-Recipient**|String or `$null`| + +This filter requires the distinguished name of the address book policy. For example, `Get-Mailbox -Filter "AddressBookPolicy -eq 'CN=Contoso ABP,CN=AddressBook Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of address book policies by running this command: `Get-AddressBookPolicy | Format-List Name,DistinguishedName`. + +## AddressListMembership + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_showInAddressBook_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +This filter requires the distinguished name of the address list. For example, `Get-MailContact -Filter "AddressListMembership -eq 'CN=All Contacts,CN=All Address Lists,CN=Address Lists Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of address lists by running this command: `Get-AddressList | Format-List Name,DistinguishedName`. + +## AdminDisplayName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_adminDisplayName_|**Get-SecurityPrincipal**|String (wildcards accepted) or `$null`| + +For example, `Get-SecurityPrincipal -Filter 'AdminDisplayName -ne $null' | Format-Table -Auto Name,AdminDisplayName`. + +## AdministrativeUnits + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchAdministrativeUnitLink_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|`$null`| + +For example, `Get-User -Filter 'AdministrativeUnits -ne $null'`. + +## AggregatedMailboxGuids + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchAlternateMailboxes_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +For example, `Get-Mailbox -Filter 'AggregatedMailboxGuids -ne $null'`. + +## Alias + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_mailNickname_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted)| + +For example, `Get-Recipient -Filter "Alias -like 'smith*'"`. + +## AllowUMCallsFromNonUsers + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMListInDirectorySearch_|**Get-Contact**
**Get-LinkedUser**
**Get-UMMailbox**
**Get-User**|`None` (0) or `SearchEnabled` (1)| + +For example, `Get-User -Filter "AllowUMCallsFromNonUsers -ne 'SearchEnabled'"`. + +## ArbitrationMailbox + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArbitrationMailbox_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the distinguished name of the arbitration mailbox. For example, `Get-DistributionGroup -Filter "ArbitrationMailbox -eq 'CN=SystemMailbox"1f05a927-2e8f-4cbb-9039-2cfb8b95e486",CN=Users,DC=contoso,DC=com'"`. + +You can find the distinguished names of arbitration mailboxes by running this command: `Get-Mailbox -Arbitration | Format-List Name,DistinguishedName`. + +## ArchiveDatabase + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveDatabaseLink_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the distinguished name of the archive mailbox database. For example, `Get-Mailbox -Filter "ArchiveMailbox -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`. + +## ArchiveDomain + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveAddress_|**Get-Mailbox**|String (wildcards accepted) or `$null`| + +This property is used in on-premises Exchange environments to identify the Exchange Online organization that holds the archive mailbox. For example, `Get-Mailbox -Filter "ArchiveDomain -like 'contoso.onmicrosoft.com*'"`. + +## ArchiveGuid + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveGUID_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the GUID of the archive mailbox. For example, `Get-Mailbox -Filter "ArchiveMailbox -eq '6476f55e-e5eb-4462-a095-f2cb585d648d'"`. + +You can find the GUID of archive mailboxes by running this command: `Get-Mailbox -Archive | Format-Table -Auto Name,ArchiveGUID`. + +## ArchiveName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveName_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`| + +This filter requires the name of the archive mailbox. For example, `Get-Mailbox -Filter "ArchiveName -like 'In-Place Archive*'"`. + +You can find the names of archive mailboxes by running this command: `Get-Mailbox -Archive | Format-Table -Auto Name,ArchiveName`. + +## ArchiveQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ArchiveQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ArchiveQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ArchiveQuota - ''"`. For example, `Get-Mailbox | where "$_.ArchiveQuota -gt '85GB'"`. + +## ArchiveRelease + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveRelease_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**|`None`, `E14`, `E15`, or `$null`.| + +For example, `Get-Recipient -Filter 'ArchiveRelease -ne $null'`. + +## ArchiveState + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-Recipient**
**Get-RemoteMailbox**|`None` (0), `Local` (1), `HostedProvisioned` (2), `HostedPending` (3), or `OnPremise` (4).| + +For example, `Get-Recipient -Filter "ArchiveState -eq 'HostedProvisioned'"`. + +## ArchiveStatus + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveStatus_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|`None` (0) or `Active` (1).| + +For example, `Get-Recipient -Filter "ArchiveStatus -eq 'Active'"`. + +## ArchiveWarningQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchArchiveWarnQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ArchiveWarningQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ArchiveWarningQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ArchiveWarningQuota - ''"`. For example, `Get-Mailbox | where "$_.ArchiveWarningQuota -gt '85GB'"`. + +## AssistantName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchAssistantName_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "AssistantName -like 'Julia*'"`. + +## AuditEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxAuditEnable_|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'AuditEnabled -eq $true'`. + +## AuditLogAgeLimit + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxAuditLogAgeLimit_|**Get-Mailbox**
**Get-UnifiedGroup**|A time span value: _dd.hh:mm:ss_ where _dd_ = days, _hh_ = hours, _mm_ = minutes, and _ss_ = seconds.| + +You can't use the _Filter_ parameter to look for time span values for this property. Instead, use this syntax: `Get-Mailbox | where "$_.AuditLogAgeLimit - ''"`. For example, `Get-Mailbox | where "$_.AuditLogAgeLimit -gt '60.00:00:00'"`. + +## AuthenticationPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchAuthPolicyLink_|**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "AuthenticationPolicy -eq 'CN=Block Basic Auth,CN=Auth Policies,CN=Configuration,CN=contoso.onmicrosoft.com,CN=ConfigurationUnits,DC=NAMPR11B009,DC=PROD,DC=OUTLOOK,DC=COM'"`. + +## BlockedSendersHash + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchBlockedSendersHash_|**Get-Recipient**|Blank ( `$null`) or a hashed value.| + +Realistically, you can only use this value to filter on blank or non-blank values. For example, `Get-Recipient -Filter 'BlockedSendersHash -ne $null'.` + +## c + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_c_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|String (wildcards accepted) or `$null`| + +This filter requires the ISO 3166-1 two-letter country code for the user (for example, `US` for the United States). This property is used together with the _co_ and _countryCode_ properties to define the user's country in Active Directory. + +For example, `Get-User -Filter "c -eq 'US'"`. + +## CalendarLoggingQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchCalendarLoggingQuota_|**Get-Mailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "CalendarLoggingQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "CalendarLoggingQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.CalendarLoggingQuota - ''"`. For example, `Get-Mailbox | where "$_.CalendarLoggingQuota -gt '10GB'"`. + +## CalendarRepairDisabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchCalendarRepairDisabled_|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'CalendarRepairDisabled -eq $true'`. + +## CertificateSubject + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-User**|String or `$null`| + +The X509 certificate that's published for the user account (visible on the **Published Certificates** tab in Active Directory Users and Computers). + +For example, `Get-User -Filter "CertificateSubject -eq 'X509:C=US,O=InternetCA,CN=APublicCertificateAuthorityC=US,O=Fabrikam,OU=Sales,CN=Jeff Smith`') + +## City + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_l_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "City -eq 'Redmond'"`. + +## Company + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_company_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Company -like 'Contoso*'"`. + +## ComplianceTagHoldApplied + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-MailUser**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'ComplianceTagHoldApplied -eq $true'`. + +## ConsumerNetID + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-User**|String or `$null`| + +For example, `Get-User -Filter 'ConsumerNetID -ne $null'`. + +## CountryCode + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_countryCode_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|Integer| + +This filter requires the ISO 3166-1 three-digit country code for the user (for example, `840` for the United States). This property is used together with the _c_ and _co_ properties to define the user's country in Active Directory. + +For example, `Get-User -Filter "countryCode -eq 796"`. + +## CountryOrRegion + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_co_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|String| + +This filter requires the ISO 3166-1 country name for the user (for example, `United States`). You can select an available value in Active Directory Users and Computers ( **Address** tab > **Country/region** field), or the Exchange admin center (user properties > **Contact information** tab > **Country/Region** field). + +When you select a user's country in Active Directory Users and Computers or the EAC, the corresponding values for the _co_ and _countryCode_ properties are automatically configured. + +For example, `Get-User -Filter "CountryOrRegion -like 'United*'"`. + +## CustomAttribute1 to CustomAttribute15 + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_extensionAttribute1_ to _extensionAttribute15_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`| + +For example, `Get-Recipient -Filter "CustomAttribute8 -like 'audited*'"`. + +## Database + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_homeMDB_|**Get-Mailbox**
**Get-Recipient**|String| + +This filter requires the distinguished name of the mailbox database. For example, `Get-Mailbox -Filter "Database -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`. + +## DefaultPublicFolderMailbox + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchPublicFolderMailbox_|**Get-Mailbox**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the public folder mailbox. For example, `Get-Mailbox -Filter "DefaultPublicFolderMailbox -eq 'CN=PF Mailbox01,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "DefaultPublicFolderMailbox -eq 'contoso.com/Users/PF Mailbox01'"`. + +To find the distinguished names of public folder mailboxes, run this command: `Get-Mailbox -PublicFolder | Format-List Name,DistinguishedName`. + +## DeletedItemFlags + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_deletedItemFlags_|**Get-Mailbox**
**Get-SecurityPrincipal**|`DatabaseDefault` (0), `RetainUntilBackupOrCustomPeriod` (3), or `RetainForCustomPeriod` (5).| + +For example, `Get-Mailbox -Filter "DeletedItemFlags -ne 'DatabaseDefault'"`. + +## DeliverToMailboxAndForward + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_deliverAndRedirect_|**Get-Mailbox**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-MailPublicFolder**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'DeliverToMailboxAndForward -eq $true'`. + +## Department + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_department_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-Recipient -Filter "Department -like 'Engineering*'"`. + +## DirectReports + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_directReports_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the direct report. For example, `Get-User -Filter "DirectReports -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-User -Filter "DirectReports -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a direct report, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## DisabledArchiveDatabase + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchDisabledArchiveDatabaseLink_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the distinguished name of the disabled archive mailbox database. For example, `Get-Mailbox -Filter "DisabledArchiveDatabase -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`. + +## DisabledArchiveGuid + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchDisabledArchiveDatabaseGUID_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the GUID of the disabled archive mailbox. For example, `Get-Mailbox -Filter "DisabledArchiveGuid -eq '6476f55e-e5eb-4462-a095-f2cb585d648d'"`. + +You can find the GUID of archive mailboxes by running this command: `Get-Mailbox -Archive | Format-Table -Auto Name,ArchiveGUID`. + +## DisplayName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_displayName_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted)| + +For example, `Get-Recipient -Filter "DisplayName -like 'Julia*'"`. + +## DistinguishedName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_distinguishedName_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**
**Get-UnifiedGroup**|String| + +This filter requires the distinguished name of the recipient. For example, `Get-Mailbox -Filter "DistinguishedName -eq 'CN=Basho Kato,CN=Users,DC=contoso,DC=com'"`. + +You can find the distinguished names of recipients by running this command: `Get-Recipient | Format-List Name,RecipientType,DistinguishedName`. + +## EcpEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-CASMailbox -Filter 'EcpEnabled -eq $false'`. + +## EmailAddresses + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_proxyAddresses_|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-UnifiedGroup**|String (wildcards accepted)| + +For example, `Get-Recipient -Filter "EmailAddresses -like 'marketing*'"`. + +When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"EmailAddresses -eq 'lila@fabrikam.com'"` returns a match, `"EmailAddresses -like 'lila*'"` won't return a match, but or `"EmailAddresses -like 'smtp:lila*'"` will return a match. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## EmailAddressPolicyEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-Recipient -Filter 'EmailAddressPolicyEnabled -eq $false'`. + +## EntryId + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchPublicFolderEntryId_|**Get-MailPublicFolder**|String (wildcards accepted)| + +For example, `Get-MailPublicFolder -Filter "EntryId -like '60000*'"`. + +You can find the entry IDs of mail-enabled public folders by running this command: `Get-MailPublicFolder | Format-List Name,EntryId`. + +## EwsApplicationAccessPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchEwsApplicationAccessPolicy_|**Get-CASMailbox**|`EnforceAllowList`, `EnforceBlockList`. or `$null`| + +For example, `Get-CASMailbox -Filter 'EwsApplicationAccessPolicy -ne $null'`. + +## EwsEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchEwsEnabled_|**Get-CASMailbox**|0 (disabled), 1 (enabled) or `$null`.| + +For example, `Get-CASMailbox -Filter "EwsEnabled -eq 1"`. + +## ExchangeGuid + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxGuid_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String| + +For example, `Get-Mailbox -Filter "ExchangeGuid -eq 'c80a753d-bd4a-4e19-804a-6344d833ecd8'"`. + +To find the Exchange GUID of a recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,ExchangeGuid`. + +Note that an object's Exchange GUID value is different than its GUID value. Also, the Exchange GUID value for non-mailboxes (mail contacts, mail users, distribution groups, dynamic distribution groups, mail-enabled security groups, and mail-enabled public folders) is `00000000-0000-0000-0000-000000000000`. + +## ExchangeUserAccountControl + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUserAccountControl_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|`None` (0) or `AccountDisabled` (2)| + +For example, `Get-Mailbox -Filter "ExchangeUserAccountControl -eq 'AccountDisabled'"`. + +## ExchangeVersion + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchVersion_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**|Integer| + +This property contains the earliest version of Exchange that you can use to manage the recipient. The property values that you see are different than the values that you need to use in the filter. To see the **ExchangeVersion** property values, run this command: `Get-Recipient | Format-Table Name,RecipientType,ExchangeVersion`. + +For the Exchange 2010 value `0.10 (14.0.100.0)`, use the value 44220983382016 in the filter. + +For the Exchange 2013 or Exchange 2016 value `0.20 (15.0.0.0)`, use the value 88218628259840 in the filter. + +For example, `Get-Recipient -Filter "ExchangeVersion -lt 88218628259840"`. + +## ExpansionServer + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchExpansionServerName_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Recipient**|String (wildcards accepted) or `$null`| + +For example, `Get-Recipient -Filter "ExpansionServer -like 'Mailbox01*'"`. + +For an exact match, you need to use the **ExchangeLegacyDN** value of the server. For example, `Get-Recipient -Filter "ExpansionServer -eq '/o=Contoso Corporation/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01'"` + +You can find the **ExchangeLegacyDN** value by running this command: `Get-ExchangeServer | Format-List Name,ExchangeLegacyDN`. + +## ExtensionCustomAttribute1 to ExtensionCustomAttribute5 + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchExtensionCustomAttribute1_ to _msExchExtensionCustomAttribute5_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`| + +For example, `Get-Recipient -Filter "ExtensionCustomAttribute8 -like 'audited*'"`. + +## ExternalDirectoryObjectId + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchExternalDirectoryObjectId_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|String or `$null`| + +For example, `Get-Recipient -Filter 'ExternalDirectoryObjectId -ne $null'`. + +## ExternalEmailAddress + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_targetAddress_|**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**|String (wildcards accepted) or `$null`| + +For example, `Get-Recipient -Filter "ExternalEmailAddress -like '@fabrikam.com*'"`. + +When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ExternalEmailAddress -eq 'lila@fabrikam.com'"` returns a match, `"ExternalEmailAddress -like 'lila*'"` won't return a match, but `"ExternalEmailAddress -like 'smtp:lila*'"` will return a match. + +## ExternalOofOptions + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchExternalOOFOptions_|**Get-Mailbox**|`External` (0) or `InternalOnly` (1)| + +For example, `Get-Mailbox -Filter "ExternalOofOptions -eq 'External'"`. + +## Fax + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_facsimileTelephoneNumber_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Fax -like '206*'"`. + +## FirstName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_givenName_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "FirstName -like 'Chris*'"`. + +## ForwardingAddress + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_altRecipient_|**Get-Mailbox**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the forwarding recipient. For example, `Get-Mailbox -Filter "ForwardingAddress -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "ForwardingAddress -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a forwarding recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +## ForwardingSmtpAddress + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchGenericForwardingAddress_|**Get-Mailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter "ForwardingSmtpAddress -like '@fabrikam.com*'"`. + +When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ForwardingSmtpAddress -eq 'lila@fabrikam.com'"` returns a match, `"ForwardingSmtpAddress -like 'lila*'"` won't return a match, but `"ForwardingSmtpAddress -like 'smtp:lila*'"` will return a match. + +## GeneratedOfflineAddressBooks + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchOABGeneratingMailboxBL_|**Get-Mailbox**|String or `$null`| + +This property is only meaningful on arbitration mailboxes, so you need to use the _Arbitration_ switch in the filter command. Also, This filter requires the distinguished name of the offline address book. For example, `Get-Mailbox -Arbitration -Filter "GeneratedOfflineAddressBooks -eq 'CN=OAB 1,CN=Offline Address Lists,CN=Address Lists Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of offline address books by running this command: `Get-OfflineAddressBook | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## GrantSendOnBehalfTo + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_publicDelegates_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the mail-enabled security principal (mailbox, mail user, or mail-enabled security group). For example, `Get-Mailbox -Filter "GrantSendOnBehalfTo -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "GrantSendOnBehalfTo -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a mail-enabled security principal, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## GroupMemberCount + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-UnifiedGroup**|Integer| + +For example, `Get-UnifiedGroup -Filter "GroupMemberCount -gt 100"`. + +## GroupExternalMemberCount + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-UnifiedGroup**|Integer| + +For example, `Get-UnifiedGroup -Filter "GroupExternalMemberCount -gt 0"`. + +## GroupType + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_groupType_|**Get-DistributionGroup**
**Get-Group**
**Get-UnifiedGroup**|`None` (0), `Global` (2), `DomainLocal` (4), `BuiltinLocal` (5), `Universal` (8), or `SecurityEnabled` (-2147483648).| + +Distribution groups have the value `Universal`, and mail-enabled security groups have the value `Universal, SecurityEnabled`. You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-DistributionGroup -Filter "GroupType -eq 'Universal,SecurityEnabled'"` returns the same results as `Get-DistributionGroup -Filter "GroupType -eq 'SecurityEnabled,Universal'"`. + +This multivalued property will only return a match if the property _equals_ the specified value. + +## Guid + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_objectGuid_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**
**Get-UnifiedGroup**|String| + +For example, `Get-Recipient -Filter "Guid -eq '8a68c198-be28-4a30-83e9-bffb760c65ba'"`. + +You can find the GUIDs of recipients by running this command: `Get-Recipient | Format-List Name,RecipientType,Guid`. + +Note that an object's GUID value is different than its Exchange GUID value. + +## HasActiveSyncDevicePartnership + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**
**Get-Recipient**|Boolean (`$true` or `$false`)| + +For example, `Get-Recipient -Filter 'HasActiveSyncDevicePartnership -eq $true'`. + +## HiddenFromAddressListsEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchHideFromAddressLists_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-Recipient -Filter 'HiddenFromAddressListsEnabled -eq $true'`. + +## HiddenGroupMembershipEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_hideDLMembership_|**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-UnifiedGroup -Filter 'HiddenGroupMembershipEnabled -eq $true'`. + +## HomePhone + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_homePhone_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "HomePhone -like '206*'"`. + +## Id + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_distinguishedName_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMMailbox**
**Get-User**
**Get-SecurityPrincipal**
**Get-UnifiedGroup**|String| + +This filter requires the distinguished name or canonical distinguished name of the recipient. For example, `Get-Mailbox -Filter "Id -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "Id -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +## IgnoreMissingFolderLink + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-MailPublicFolder**|Boolean (`$true` or `$false`)| + +For example, `Get-MailPublicFolder -Filter 'IgnoreMissingFolderLink -eq $true'`. + +## ImapEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-CASMailbox -Filter 'ImapEnabled -eq $false'`. + +## ImmutableId + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchGenericImmutableId_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +For example, `Get-Mailbox -Filter 'ImmutableId -ne $null'`. + +## IncludeInGarbageCollection + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IncludeInGarbageCollection -eq $true'`. + +## Initials + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_initials_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Initials -like 'B.'"`. + +## InPlaceHolds + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUserHoldPolicies_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String| + +This filter requires the **InPlaceHoldIdentity** value of the mailbox search. For example, `Get-Mailbox -Filter "InPlaceHolds -eq '9d0f81154cc64c6b923ecc0be5ced0d7'"`. + +To find the **InPlaceHoldIdentity** values of mailbox searches, run this command: `Get-MailboxSearch | Format-Table Name,InPlaceHoldIdentity`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## InPlaceHoldsRaw + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-User**|String| + +This filter requires the **InPlaceHoldIdentity** value of the mailbox search. For example, `Get-Mailbox -Filter "InPlaceHoldsRaw -eq '9d0f81154cc64c6b923ecc0be5ced0d7'"`. + +To find the **InPlaceHoldIdentity** values of mailbox searches, run this command: `Get-MailboxSearch | Format-Table Name,InPlaceHoldIdentity`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## IsDirSynced + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchIsMSODirsynced_|**Get-Contact**
**Get-DistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-User -Filter 'IsDirSynced -eq $true'`. + +## IsExcludedFromServingHierarchy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsExcludedFromServingHierarchy -eq $true'`. + +## IsHierarchyReady + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsHierarchyReady -eq $false'`. + +## IsHierarchySyncEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsHierarchySyncEnabled -eq $false'`. + +## IsInactiveMailbox + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsInactiveMailbox -eq $false'`. + +## IsLinked + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-User**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsLinked -eq $true'`. + +## IsMailboxEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsMailboxEnabled -eq $false'`. + +## IsResource + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsResource -eq $true'`. + +## IsSecurityPrincipal + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-User**|Boolean (`$true` or `$false`)| + +For example, `Get-User -Filter 'IsSecurityPrincipal -eq $false'`. + +## IsShared + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsShared -eq $true'`. + +## IsSoftDeletedByDisable + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsSoftDeletedByDisable -eq $true'`. + +## IsSoftDeletedByRemove + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'IsSoftDeletedByRemove -eq $true'`. + +## IssueWarningQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_mDBStorageQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "IssueWarningQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "IssueWarningQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.IssueWarningQuota - ''`". For example, `Get-Mailbox | where "$_.IssueWarningQuota -lt '50GB'"`. + +## JournalArchiveAddress + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String| + +This property uses an SMTP email address. For example, `Get-Mailbox -Filter "JournalArchiveAddress -eq 'michelle@contoso.com'"`. + +## LanguagesRaw + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUserCulture_|**Get-Mailbox**|String (wildcards accepted) or `$null`| + +This property is named **Languages** in the properties of a mailbox, and it contains the language preference for the mailbox in the format `-`. For example, United States English is `en-US`. For more information, see [CultureInfo Class](/dotnet/api/system.globalization.cultureinfo). + +You can specify multiple values separated by commas, but the order matters. For example, `Get-Mailbox -Filter "LanguagesRaw -eq 'en-US,es-MX'"` returns different results than `Get-Mailbox -Filter "LanguagesRaw -eq 'es-MX,en-US'"`. + +For single values, this multivalued property will return a match if the property _contains_ the specified value. + +## LastExchangeChangedTime + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchLastExchangeChangedTime_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|`$null` or a date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-Mailbox -Filter 'LastExchangeChangedTime -ne $null'`. + +## LegacyExchangeDN + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_legacyExchangeDN_|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted)| + +For example, `Get-User -Filter "LegacyExchangeDN -like 'Osca*'"`. + +You can find LegacyExchangeDN values for users by running this command: `Get-User | Format-List Name,LegacyExchangeDN` + +## LitigationHoldDate + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchLitigationHoldDate_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|`$null` or a date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-Mailbox -Filter "LitigationHoldDate -gt '8/13/2017'"`. + +## LitigationHoldEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'LitigationHoldEnabled -eq $true'`. + +## LitigationHoldOwner + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchLitigationHoldOwner_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`| + +This property uses the user principal name of the litigation hold owner. For example, `Get-Mailbox -Filter "LitigationHoldOwner -eq 'agruber@contoso.com'"`. + +## LastName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_sn_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "LastName -like 'Martin*'"`. + +## MailboxContainerGUID + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxContainerGuid_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +For example, `Get-Mailbox -Filter 'MailboxContainerGUID -ne $null'`. + +## MailboxMoveBatchName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxMoveBatchName_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`| + +This property includes the name of the migration batch. For example, `Get-Mailbox -Filter "MailboxMoveBatchName -like 'LocalMove 01*'"`. + +You can find the names of migration batches by running the **Get-MigrationBatch** command. Note that migration batches that you create in the Exchange admin center use the naming convention `MigrationService:`. + +## MailboxMoveFlags + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxMoveFlags_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|For valid values, see the description of the _Flags_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest#-flags).| + +For example, `Get-Mailbox -Filter "MailboxMoveFlags -ne 'None'"`. + +You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-Recipient -Filter "MailboxMoveFlags -eq 'IntraOrg,Pull'"` returns the same results as `Get-Recipient -Filter "MailboxMoveFlags -eq 'Pull,IntraOrg'"`. + +This multivalued property will only return a match if the property _equals_ the specified value. + +## MailboxMoveRemoteHostName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxMoveRemoteHostName_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`| + +For example, `Get-Mailbox -Filter 'MailboxMoveRemoteHostName -ne $null'`. + +## MailboxMoveSourceMDB + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxMoveSourceMDBLink_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the distinguished name of the source mailbox database. For example, `Get-Mailbox -Filter "MailboxMoveSourceMDB -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`. + +## MailboxMoveStatus + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxMoveStatus_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|For valid values, see the description of the _MoveStatus_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest#-movestatus).| + +For example, `Get-Mailbox -Filter "MailboxMoveStatus -eq 'Completed'"`. + +## MailboxMoveTargetMDB + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxMoveTargetMDBLink_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|String or `$null`| + +This filter requires the distinguished name of the target mailbox database. For example, `Get-Mailbox -Filter "MailboxMoveTargetMDB -eq 'CN=MBX DB02,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of mailbox databases by running this command: `Get-MailboxDatabase | Format-List Name,DistinguishedName`. + +## MailboxPlan + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchParentPlanLink_|**Get-Mailbox**|String or `$null`| + +Mailbox plans correspond to Microsoft 365 license types. The availability of a license plans is determined by the selections that you make when you enroll your domain. + +For example, `Get-Mailbox -Filter 'MailboxPlan -ne $null'`. + +## MailboxRelease + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxRelease_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-User**|`None`, `E14`, `E15`, or `$null`.| + +For example, `Get-Recipient -Filter 'MailboxRelease -ne $null'`. + +## MailTipTranslations + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchSenderHintTranslations_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`| + +When you use this property in a filter, you need to account for the leading and trailing HTML tags. For example, `Get-DistributionGroup -Filter "MailTipTranslations -like 'is not monitored.*'"`. + +## ManagedBy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_managedBy_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-Recipient**
**Get-UnifiedGroup**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the group owner (a mail-enabled security principal, which is a mailbox, mail user, or mail-enabled security group). For example, `Get-Mailbox -Filter "ManagedBy -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "ManagedBy -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a mail-enabled security principal, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## ManagedFolderMailboxPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMailboxTemplateLink_|**Get-Mailbox**
**Get-Recipient**|String or `$null`| + +Managed folder mailbox policies aren't available in Exchange 2013 or later. + +For example, `Get-Mailbox -Filter 'ManagedFolderMailboxPolicy -eq $null'`. + +This filter requires the distinguished name of the managed folder mailbox policy. For example, `Get-Mailbox -Filter "ManagedFolderMailboxPolicy -eq 'CN=MFM Inbox Policy,CN=ELC Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +You can find the distinguished names of managed folder mailbox policies on Exchange 2010 servers by running this command: `Get-ManagedFolderMailboxPolicy | Format-List Name,DistinguishedName`. + +## Manager + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_manager_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the manager (a mailbox or mail user). For example, `Get-User -Filter "Manager -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "Manager -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a manager, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName.` + +## MAPIEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-CASMailbox -Filter 'MAPIEnabled -eq $false'`. + +## MasterAccountSid + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMasterAccountSid_|**Get-Mailbox**
**Get-LinkedUser**
**Get-Recipient**
**Get-SecurityPrincipal**
**Get-User**|String or `$null`| + +For example, `Get-Mailbox -Filter 'MasterAccountSid -ne $null'`. + +This value is blank ( `$null`) for mailboxes with associated user accounts, and `S-1-5-10` (Self) for mailboxes without associated user accounts (for example, shared mailboxes, resource mailboxes, discovery search mailboxes, arbitration mailboxes, and public folder mailboxes). + +## MaxBlockedSenders + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMaxBlockedSenders_|**Get-Mailbox**|Integer or `$null`| + +For example, `Get-Mailbox -Filter "MaxBlockedSenders -gt 0"`. + +## MaxReceiveSize + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_delivContLength_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|A byte quantified size value (for example, `75MB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "MaxReceiveSize -eq 'Unlimited'"` or `Get-Mailbox -Filter "MaxReceiveSize -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.MaxReceiveSize - ''"`. For example, `Get-Mailbox | where "$_.MaxReceiveSize -gt '50GB'"`. + +## MaxSafeSenders + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMaxSafeSenders_|**Get-Mailbox**|Integer or `$null`| + +For example, `Get-Mailbox -Filter "MaxSafeSenders -gt 0"`. + +## MaxSendSize + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_submissionContLength_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|A byte quantified size value (for example, `75MB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "MaxSendSize -eq 'Unlimited'"` or `Get-Mailbox -Filter "MaxSendSize -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.MaxReceiveSize - ''"`. For example, `Get-Mailbox | where "$_.MaxSendSize -gt '50GB'"`. + +## MemberDepartRestriction + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchGroupDepartRestriction_|**Get-DistributionGroup**|`Closed` (0), `Open` (1), or `ApprovalRequired` (2).| + +For example, `Get-DistributionGroup -Filter "MemberDepartRestriction -eq 'ApprovalRequired'"`. + +## MemberJoinRestriction + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchGroupDepartRestriction_|**Get-DistributionGroup**|`Closed` (0), `Open` (1), or `ApprovalRequired` (2).| + +For example, `Get-DistributionGroup -Filter "MemberJoinRestriction -eq 'ApprovalRequired'"`. + +## MemberOfGroup + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_memberOf_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMMailbox**
**Get-User**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the distribution group or mail-enabled security group. For example, `Get-User -Filter "MemberOfGroup -eq 'CN=Marketing Department,CN=Users,DC=contoso,DC=com'"` or `Get-User -Filter "MemberOfGroup -eq 'contoso.com/Users/Marketing Group'"`. + +To find the distinguished name of a group, replace _\_ with the name, alias, or email address of the group, and run this command: `Get-DistributionGroup -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## Members + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_member_|**Get-DistributionGroup**
**Get-Group**
**Get-Recipient**
**Get-SecurityPrincipal**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the group member. For example, `Get-Group -Filter "Members -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-User -Filter "Members -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a group member, replace _\_ with the name, alias, or email address of the group member, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## MobilePhone + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_mobile_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "MobilePhone -like '555*'"`. + +## ModeratedBy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchModeratedByLink_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String| + +This filter requires the distinguished name or canonical distinguished name of the group moderator (a mail-enabled security principal, which is a mailbox, mail-user, or mail-enabled security group). For example, `Get-DistributionGroup -Filter "ModeratedBy -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-DistributionGroup -Filter "ModeratedBy -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a mail-enabled security principal, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## ModerationEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchEnableModeration_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-DistributionGroup -Filter 'ModerationEnabled -eq $true'`. + +## Name + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_name_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted)| + +For example, `Get-User -Filter "Name -like 'Laura*'"`. + +## NetID + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-User**|String or `$null`| + +This property is populated for Exchange Online mailboxes in hybrid environments. A sample value is `1003BFFD9A0CFA03`. + +For example, `Get-User -Filter 'NetId -ne $null'`. + +## Notes + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_info_|**Get-Contact**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**
**Get-UnifiedGroup**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Notes -like 'Events Team*'"`. + +## ObjectCategory + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_objectCategory_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String| + +This filter requires the canonical distinguished name of the object. The value uses the syntax `/Configuration/Schema/`. + +Valid _\_ values are: `Person` for mailboxes, mail users, and mail contacts, `Group` for distribution groups, mail-enabled security groups and Microsoft 365 Groups, `ms-Exch-Public-Folder` for mail-enabled public folders, and `ms-Exch-Dynamic-Distribution-List` for dynamic distribution groups. + +For example, `Get-Recipient -Filter "ObjectCategory -eq 'contoso.com/Configuration/Schema/Group'"`. + +## ObjectClass + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_objectClass_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|String| + +The value of this property is `top, person, organizationalPerson, user` for mailboxes and mail users, `top, person, organizationalPerson, contact` for mail contacts, `top, group` for distribution groups, mail-enabled security groups and Microsoft 365 Groups, `msExchDynamicDistributionList` for dynamic distribution groups and `top, publicFolder` for mail-enabled public folders + +For example, `Get-Recipient -Filter "ObjectClass -eq 'Contact'"`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## Office + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_physicalDeliveryOfficeName_|**Get-Contact**
**Get-LinkedUser**
**Get-Mailbox**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Office -like '22*'"`. + +## OfflineAddressBook + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUseOAB_|**Get-Mailbox**|String or `$null`| + +This filter requires the distinguished name of the offline address book. For example, `Get-Mailbox -Arbitration -Filter "OfflineAddressBook -eq 'CN=OAB 1,CN=Offline Address Lists,CN=Address Lists Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"` + +You can find the distinguished names of offline address books by running this command: `Get-OfflineAddressBook | Format-List Name,DistinguishedName`. + +## OnPremisesObjectId + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-MailPublicFolder**|String or `$null`| + +For example, `Get-MailPublicFolder -Filter 'OnPremisesObjectId -ne $null'`. + +## OperatorNumber + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMOperatorNumber_|**Get-UMMailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-UMMailbox -Filter "OperatorNumber -eq 5"`. + +## OtherFax + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_otherFacsimileTelephoneNumber_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "OtherFax -like '206*'"`. + +## OtherHomePhone + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_otherHomePhone_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "OtherHomePhone -like '206*'"`. + +## OtherTelephone + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_otherTelephone_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "OtherTelephone -like '206*'"`. + +## OWAEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +The filter operates backwards. For example, `Get-CASMailbox -Filter 'OWAEnabled -eq $true'` returns mailboxes where the **OWAEnabled** property is `False`, and `Get-CASMailbox -Filter 'OWAEnabled -eq $false'` returns mailboxes where the **OWAEnabled** property is `True` + +## OWAforDevicesEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchOmaAdminWirelessEnable_|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-CASMailbox -Filter 'OWAForDevicesEnabled -eq $true'`. + +## OWAMailboxPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchOWAPolicy_|**Get-CASMailbox**
**Get-Recipient**|String or `$null`| + +This filter requires the distinguished name of the Outlook on the web mailbox policy (formerly known as an Outlook Web App mailbox policy). For example, `Get-CASMailbox -Filter "OWAMailboxPolicy -eq 'CN=Default,CN=OWA Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com`'". + +You can find the distinguished names of Outlook on the web mailbox policies by running this command: `Get-OwaMailboxPolicy | Format-List Name,DistinguishedName`. + +## Pager + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_pager_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Pager -like '206*'"`. + +## PersistedCapabilities + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String or `$null`| + +Typically, the value of this property something other than `$null` (blank) for Microsoft 365 accounts and mailboxes. For more information about the valid property values, see [Capability enumeration](/previous-versions/office/exchange-server-api/ff441134(v=exchg.150)). + +For example, `Get-Mailbox -Filter 'PersistedCapabilities -ne $null'`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## Phone + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_telephoneNumber_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Phone -like '206*'"`. + +## PhoneProviderId + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMPhoneProvider_|**Get-UMMailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-UMMailbox -Filter "PhoneProviderId -like '206*'"`. + +## PhoneticDisplayName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msDS-PhoneticDisplayName_|**Get-Contact**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-MailPublicFolder**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "PhoneticDisplayName -like 'Lila*'"`. + +## PoliciesExcluded + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchPoliciesExcluded_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +For example, `Get-Recipient -Filter 'PoliciesExcluded -ne $null'`. + +## PoliciesIncluded + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchPoliciesIncluded_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +For example, `Get-Recipient -Filter 'PoliciesIncluded -eq $null'`. + +## PopEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-CASMailbox -Filter 'POPEnabled -eq $false'`. + +## PostalCode + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_postalCode_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-Recipient -Filter "PostalCode -eq 90210"`. + +## PostOfficeBox + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_postOfficeBox_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "PostOfficeBox -like '555*'"`. + +## PreviousRecipientTypeDetails + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchPreviousRecipientTypeDetails_|**Get-LinkedUser**
**Get-User**|String or `$null`| + +For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient#-recipienttypedetails). + +For example, `Get-User -Filter 'PreviousRecipientTypeDetails -ne $null'`. + +## PrimarySmtpAddress + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-UnifiedGroup**|String (wildcards accepted)| + +Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property will also search values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`. + +## ProhibitSendQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_mDBOverQuotaLimit_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ProhibitSendQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ProhibitSendQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ProhibitSendQuota - ''"`. For example, `Get-Mailbox | where "$_.ProhibitSendQuota -lt '70GB'"`. + +## ProhibitSendReceiveQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_mDBOverHardQuotaLimit_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "ProhibitSendReceiveQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "ProhibitSendReceiveQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.ProhibitSendReceiveQuota - ''"`. For example, `Get-Mailbox | where "$_.ProhibitSendReceiveQuota -lt '70GB'"`. + +## ProtocolSettings + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_protocolSettings_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`| + +The default value of this property on mailboxes is `RemotePowerShell§1`. This property is populated with additional values when you use Set-CASMailbox to disable protocols (for example, POP3 or IMAP4). + +For example, `Get-Mailbox -Filter "ProtocolSettings -like 'POP3*'"`. + +## PublicFolderContacts + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_pFContacts_|**Get-MailPublicFolder**|String or `$null`| + +This property is displayed as **Contacts** in the results of the command `Get-MailPublicFolder -Identity | Format-List`, but you need to use the property name **PublicFolderContacts** in the filter. + +This filter requires the distinguished name or canonical distinguished name of the public folder contact. For example, `Get-MailPublicFolder -Filter "PublicFolderContacts -eq 'CN=Angela Gruber,CN=Users,DC=contoso,DC=com'"` or `Get-MailPublicFolder -Filter "PublicFolderContacts -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of a public folder contact, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## QueryBaseDN + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchQueryBaseDN_|**Get-Mailbox**|String or `$null`| + +This property was used in Exchange 2007 global address list segregation to specify a location in Active Directory. This feature was replaced by address book policies in Exchange 2010 Service Pack 2, so the value of this property should always be blank ( `$null`). + +For example, `Get-Mailbox -Filter 'QueryBaseDN -ne $null'`. + +## RecipientContainer + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchDynamicDLBaseDN_|**Get-DynamicDistributionGroup**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the organizational unit or container in Active Directory. For example, `Get-DynamicDistributionGroup -Filter "RecipientContainer -eq 'CN=Users,DC=contoso,DC=com'"` or `Get-DynamicDistributionGroup -Filter "RecipientContainer -eq 'contoso.com/Users'"` + +To find the distinguished names or canonical distinguished names of organizational units and containers in Active Directory, run this command: `Get-OrganizationalUnit -IncludeContainers | Format-List Name,DistinguishedName,ID`. + +## RecipientLimits + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchRecipLimit_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|Integer or `Unlimited`| + +For example, `Get-Mailbox -Filter "RecipientLimits -ne 'Unlimited'"`. + +## RecipientType + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-User**
**Get-UnifiedGroup**|`DynamicDistributionGroup`, `MailContact`, `MailNonUniversalGroup`, `MailUniversalDistributionGroup`, `MailUniversalSecurityGroup`, `MailUser`, `PublicFolder` or `UserMailbox`| + +For example, `Get-Recipient -Filter "RecipientType -eq 'MailContact'"`. + +## RecipientTypeDetails + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-User**
**Get-UnifiedGroup**|String| + +For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient#-recipienttypedetails). + +For example, `Get-Recipient -Filter "RecipientTypeDetails -eq 'SharedMailbox'"`. + +## RecoverableItemsQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchDumpsterQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "RecoverableItemsQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "RecoverableItemsQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.RecoverableItemsQuota - ''`. For example, `Get-Mailbox | where "$_.RecoverableItemsQuota -gt '35GB'"`. + +## RecoverableItemsWarningQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchDumpsterWarningQuota_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A byte quantified size value (for example, `300MB` or `1.5GB`), or `Unlimited`. Unqualified values are treated as bytes.| + +You can only use the _Filter_ parameter to look for the value `Unlimited` for this property. For example, `Get-Mailbox -Filter "RecoverableItemsWarningQuota -eq 'Unlimited'"` or `Get-Mailbox -Filter "RecoverableItemsWarningQuota -ne 'Unlimited'"`. + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.RecoverableItemsWarningQuota - ''`". For example, `Get-Mailbox | where "$_.RecoverableItemsWarningQuota -gt '25GB'"`. + +## RejectMessagesFrom + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_unauthOrig_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +This filter requires the distinguished name of the individual recipient (a mailbox, mail user, or mail contact). For example, `Get-DistributionGroup -Filter "RejectMessagesFrom -eq 'CN=Yuudai Uchida,CN=Users,DC=contoso,DC=com'"` or `Get-DistributionGroup -Filter "RejectMessagesFrom -eq 'contoso.com/Users/Angela Gruber'"`. + +To find the distinguished name of the individual recipient, replace _\_ with the name, alias, or email address of the recipient, and run this command: `Get-Recipient -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## RejectMessagesFromDLMembers + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_dLMemRejectPerms_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UnifiedGroup**|String or `$null`| + +This filter requires the distinguished name or canonical distinguished name of the group (a distribution group, mail-enabled security group, or dynamic distribution group). For example, `Get-Mailbox -Filter "RejectMessagesFromDLMembers -eq 'CN=Marketing Department,CN=Users,DC=contoso,DC=com'"` or `Get-Mailbox -Filter "RejectMessagesFromDLMembers -eq 'contoso.com/Users/Marketing Department'"`. + +To find the distinguished name of the group, replace _\_ with the name, alias, or email address of the group, and run one of these commands: `Get-DistributionGroup -Identity "" | Format-List Name,DistinguishedName` or `Get-DynamicDistributionGroup -Identity "" | Format-List Name,DistinguishedName`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## RemoteAccountPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchSyncAccountsPolicyDN_|**Get-Mailbox**|String or `$null`| + +This filter requires the distinguished name of the remote account policy. For example, `Get-Mailbox -Filter "RemoteAccountPolicy -eq 'CN=Contoso Remote Account Policy,CN=Remote Accounts Policies Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +## RemotePowerShellEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-User**|Boolean (`$true` or `$false`)| + +For example, `Get-User -Filter 'RemotePowerShellEnabled -eq $false'`. + +## RemoteRecipientType + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchRemoteRecipientType_|**Get-Mailbox**
**Get-RemoteMailbox**|`None` (0), `ProvisionMailbox` (1), `ProvisionArchive` (2), `Migrated` (4), `DeprovisionMailbox` (8), `DeprovisionArchive` (16), `RoomMailbox` (32), `EquipmentMailbox` (64), `SharedMailbox` (96), `TeamMailbox` (128), or `$null`.| + +For example, `Get-RemoteMailbox -Filter "RemoteRecipientType -eq 'ProvisionMailbox'"`. + +## ReportToManagerEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_reportToOwner_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-DistributionGroup -Filter 'ReportToManagerEnabled -eq $true'`. + +## ReportToOriginatorEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_reportToOriginator_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-DistributionGroup -Filter 'ReportToOriginatorEnabled -eq $false'`. + +## RequireAllSendersAreAuthenticated + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchRequireAuthToSendTo_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**|Boolean (`$true` or `$false`)| + +This property is displayed as **RequireSenderAuthenticationEnabled** in the results of the command `Get- -Identity | Format-List`, but you need to use the property name **RequireAllSendersAreAuthenticated** in the filter. For example, `Get-DistributionGroup -Filter 'RequireAllSendersAreAuthenticated -eq $false'`. + +## ResourceBehaviorOptions + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-UnifiedGroup**|`AllowOnlyMembersToPost`, `CalendarMemberReadOnly`, `ConnectorsEnabled`, `HideGroupInOutlook`, `NotebookForLearningCommunitiesEnabled`, `ReportToOriginator`, `SharePointReadonlyForMembers`, `SubscriptionEnabled`, `SubscribeMembersToCalendarEvents`, `SubscribeMembersToCalendarEventsDisabled`, `SubscribeNewGroupMembers`, `WelcomeEmailDisabled`, `WelcomeEmailEnabled`, or `$null`| + +For example, `Get-UnifiedGroup -Filter "ResourceBehaviorOptions -eq 'CalendarMemberReadOnly'"` + +## ResourceCapacity + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchResourceCapacity_|**Get-Mailbox**|Integer or `$null`| + +For example, `Get-Mailbox -Filter "ResourceCapacity -gt 15"` + +## ResourceCustom + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|String or `$null`| + +You create custom resource properties by using the Set-ResourceConfig cmdlet. For example, `Set-ResourceConfig -ResourcePropertySchema Room/Whiteboard,Equipment/Van`. After you create the properties, you can assign them to room or equipment mailboxes. For example, `Set-Mailbox -Identity "Conference Room 1" -ResourceCustom Whiteboard`. + +When you search for values, use the custom resource property that's assigned to the room or equipment mailbox. For example, `Get-Mailbox -Filter "ResourceCustom -eq 'Whiteboard'"`. + +## ResourceProvisioningOptions + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-UnifiedGroup**|`Team` or `$null`| + +For example, `Get-UnifiedGroup -Filter "ResourceProvisioningOptions -eq 'Team'"` + +## ResourceType + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-Recipient**|`Room` (0), `Equipment` (1), or `$null`| + +For example, `Get-Mailbox -Filter "ResourceType -eq 'Equipment'"` + +## RetainDeletedItemsFor + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_garbageCollPeriod_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|A time span value: _dd.hh:mm:ss_ where _dd_ = days, _hh_ = hours, _mm_ = minutes, and _ss_ = seconds.| + +You can't use the _Filter_ parameter to look for time span values for this property. Instead, use this syntax: `Get-Mailbox | where "$_.RetainDeletedItemsFor - ''"`. For example, `Get-Mailbox | where "$_.RetainDeletedItemsFor -gt '14.00:00:00'"`. + +## RetentionComment + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchRetentionComment_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter "RetentionComment -like '7 years*'"` + +## RetentionPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-Recipient**|String or `$null`| + +This filter requires the distinguished name of the retention policy. For example, `Get-Mailbox -Filter "RetentionPolicy -eq 'CN=Default MRM Policy,CN=Retention Policies Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +To find the distinguished names of retention policies, run this command: `Get-RetentionPolicy | Format-List Name,DistinguishedName`. + +## RetentionUrl + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchRetentionURL_|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter "RetentionUrl -like 'https://intranet.contoso.com/*'"` + +## RoleAssignmentPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchRBACPolicyLink_|**Get-Mailbox**|String (wildcards accepted) or `$null`| + +This filter requires the distinguished name of the role assignment policy in Exchange Online. For example, `Get-Mailbox -Filter "RoleAssignmentPolicy -eq 'CN=Default Role Assignment Policy,CN=Policies,CN=RBAC,CN=Configuration,CN=contoso.onmicrosoft.com,CN=ConfigurationUnits,DC=NAMPR10A001,DC=PROD,DC=OUTLOOK,DC=COM'"`. + +To find the distinguished names of role assignment policies in Exchange Online, run this command: `Get-RoleAssignmentPolicy | Format-List Name,DistinguishedName`. + +## RulesQuota + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMDBRulesQuota_|**Get-Mailbox**|A byte quantified size value (for example, `50B` or `128KB`). Unqualified values are treated as bytes.| + +You can't use the _Filter_ parameter to look for size values of this property. Instead, use this syntax: `Get-Mailbox | where "$_.RulesQuota - ''"`. For example, `Get-Mailbox | where "$_.RulesQuota -lt '256KB'"`. + +## SafeRecipientsHash + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchSafeRecipientsHash_|**Get-Recipient**|Blank ( `$null`) or a hashed value.| + +Realistically, you can only use this value to filter on blank or non-blank values. For example, `Get-Recipient -Filter 'SafeRecipientsHash -ne $null'.` + +## SafeSendersHash + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchSafeSendersHash_|**Get-Recipient**|Blank ( `$null`) or a hashed value.| + +Realistically, you can only use this value to filter on blank or non-blank values. For example, `Get-Recipient -Filter 'SafeSendersHash -ne $null'.` + +## SamAccountName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_SamAccountName_|**Get-CASMailbox**
**Get-DistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-Recipient -Filter "SamAccountName -like 'laura*'"` + +## SCLDeleteThresholdInt + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMessageHygieneSCLDeleteThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`| + +This property is displayed as **SCLDeleteThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLDeleteThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLDeleteThresholdInt -ge -2147483640"`. + +## SCLJunkThresholdInt + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMessageHygieneSCLJunkThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`| + +This property is displayed as **SCLJunkThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLJunkThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLJunkThresholdInt -ge -2147483645"`. + +## SCLQuarantineThresholdInt + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMessageHygieneSCLQuarantineThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`| + +This property is displayed as **SCLQuarantineThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLQuarantineThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLQuarantineThresholdInt -ge -2147483643"`. + +## SCLRejectThresholdInt + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchMessageHygieneSCLRejectThreshold_|**Get-Mailbox**|-2147483648 (SCL value 0), -2147483647 (SCL value 1), -2147483646 (SCL value 2), -2147483645 (SCL value 3), -2147483644 (SCL value 4), -2147483643 (SCL value 5), -2147483642 (SCL value 6), -2147483641 (SCL value 7), -2147483640 (SCL value 8), -2147483639 (SCL value 9) or `$null`| + +This property is displayed as **SCLRejectThreshold** in the results of the command `Get-Mailbox -Identity | Format-List`, but you need to use the property name **SCLRejectThresholdInt** in the filter. For example, `Get-Mailbox -Filter "SCLRejectThresholdInt -ge -2147483641"`. + +## SendOofMessageToOriginatorEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_oOFReplyToOriginator_|**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-UnifiedGroup**|Boolean (`$true` or `$false`)| + +For example, `Get-DistributionGroup -Filter 'SendOofMessageToOriginatorEnabled -eq $true'`. + +## ServerLegacyDN + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchHomeServerName_|**Get-CASMailbox**
**Get-Mailbox**
**Get-Recipient**
**Get-UMMailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter "ServerLegacyDN -like 'Mailbox01'"`. + +This is an example of a complete **ServerLegacyDN** value: `/o=Contoso Corporation/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01`. + +## ServerName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**
**Get-Mailbox**
**Get-Recipient**
**Get-UMMailbox**|String or `$null`| + +For example, `Get-Recipient -Filter "ServerName -eq 'Mailbox01'"`. + +## SharingPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchSharingPolicyLink_|**Get-Mailbox**
**Get-Recipient**|String or `$null`| + +This filter requires the distinguished name of the sharing policy. For example, `Get-Mailbox -Filter "SharingPolicy -eq 'CN=Custom Sharing Policy,CN=Federation,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +To find the distinguished names of sharing policies, run this command: `Get-SharingPolicy | Format-List Name,DistinguishedName`. + +> [!NOTE] +> For the default assignment of the default sharing policy (named Default Sharing Policy) to a mailbox, the value of the **SharingPolicy** property is blank (`$null`). + +## Sid + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_objectSid_|**Get-Group**
**Get-LinkedUser**
**Get-SecurityPrincipal**
**Get-User**|String| + +For example, `Get-User -Filter "Sid -eq 's-1-5-21-3628364307-1600040346-819251021-2603'"`. + +## SidHistory + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_SIDHistory_|**Get-Group**
**Get-LinkedUser**
**Get-User**|String or `$null`| + +For example, `Get-User -Filter "SidHistory -eq 's-1-5-21-3628364307-1600040346-819251021-2603'"`. + +## SimpleDisplayName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_displayNamePrintable_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "SimpleDisplayName -like 'lila*'"`. + +## SingleItemrecoveryEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'SingleItemRecoveryEnabled -eq $true'`. + +## SKUAssigned + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-User**|Boolean (`$true` or `$false`) or `$null`.| + +For example, `Get-User -Filter 'SKUAssigned -eq $true'`. + +## SourceAnchor + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter 'SourceAnchor -ne $null'`. + +## StateOrProvince + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_st_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "StateOrProvince -like 'Carolina*'"`. + +## StreetAddress + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_streetAddress_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "StreetAddress -like '36th Ave NE*'"`. + +## StsRefreshTokensValidFrom + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchStsRefreshTokensValidFrom_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|`$null` or a date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-User -Filter "StsRefreshTokensValidFrom -gt '8/1/2017'"`. + +## TelephoneAssistant + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_telephoneAssistant_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "TelephoneAssistant -like '206*'"`. + +## ThrottlingPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchThrottlingPolicyDN_|**Get-Mailbox**|String or `$null`| + +This filter requires the distinguished name of the throttling policy. For example, `Get-Mailbox -Filter "ThrottlingPolicy -eq 'CN=Custom Throttling Policy,CN=Global Settings,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +To find the distinguished names of throttling policies, run this command: `Get-ThrottlingPolicy | Format-List Name,DistinguishedName`. + +## Title + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_title_|**Get-Contact**
**Get-LinkedUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "Title -eq 'Dr.'"`. + +## UMAddresses + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMAddresses_|**Get-UMMailbox**|String (wildcards accepted) or `$null`| + +For example, `Get-UMMailbox -Filter 'UMAddresses -ne $null'`. + +## UMCallingLineIds + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMCallingLineIds_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "UMCallingLineIds -like '123*'"`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## UMDtmfMap + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMDtmfMap_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-UMMailbox**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter "UMDtmfMap -like '26297*'"`. + +Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value. + +## UMEnabled + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-Mailbox**
**Get-Recipient**
**Get-UMMailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'UMEnabled -eq $true'`. + +## UMMailboxPolicy + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMTemplateLink_|**Get-Recipient**
**Get-UMMailbox**|String or `$null`| + +This filter requires the distinguished name of the UM mailbox policy. For example, `Get-Recipient -Filter "UMMailboxPolicy -eq 'CN=Contoso Default Policy,CN=UM Mailbox Policies,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +To find the distinguished names of UM mailbox policies, run this command: `Get-UMMailboxPolicy | Format-List Name,DistinguishedName`. + +## UMRecipientDialPlanId + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUMRecipientDialPlanLink_|**Get-Recipient**|String or `$null`| + +This filter requires the distinguished name of the UM dial plan. For example, `Get-Recipient -Filter "UMMailboxPolicy -eq 'CN=Contoso Dial Plan,CN=UM DialPlan Container,CN=Contoso Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com'"`. + +To find the distinguished names of UM dial plans, run this command: `Get-UMDialPlan | Format-List Name,DistinguishedName`. + +## UpgradeRequest + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-User**|`None` (0), `TenantUpgrade` (1), `PrestageUpgrade` (2), `CancelPrestageUpgrade` (3), `PilotUpgrade` (4), or `TenantUpgradeDryRun` (5),| + +For example, `Get-User -Filter "UpgradeRequest -ne 'None'"`. + +## UpgradeStatus + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-User**|`None` (0), `NotStarted` (1), `InProgress` (2), `Warning` (3), `Error` (4), `Cancelled` (5), `Complete` (6), or `ForceComplete` (7).| + +For example, `Get-User -Filter "UpgradeStatus -ne 'None'"`. + +## UsageLocation + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUsageLocation_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**|String or `$null`| + +This filter requires the ISO 3166-1 country name (for example, `United States`), or two-letter country code (for example `US`) for the user in Microsoft 365. For more information, see [Country Codes - ISO 3166](https://www.iso.org/iso-3166-country-codes.html). + +For example, `Get-Recipient -Filter 'UsageLocation -eq "US"'`. + +## UseDatabaseQuotaDefaults + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_mDBUseDefaults_|**Get-Mailbox**|Boolean (`$true` or `$false`)| + +For example, `Get-Mailbox -Filter 'UseDatabaseQuotaDefaults -eq $false'`. + +## UserAccountControl + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_userAccountControl_|**Get-LinkedUser**
**Get-User**|`AccountDisabled`, `DoNotExpirePassword`, or `NormalAccount`| + +For example, `Get-User -Filter "UserAccountControl -eq 'NormalAccount'"`. + +You can specify multiple values separated by commas, but the order matters. For example, `Get-User -Filter "UserAccountControl -eq 'AccountDisabled,NormalAccount'"` returns different results than `Get-User -Filter "UserAccountControl -eq 'NormalAccount,AccountDisabled'"`. + +This multivalued property will only return a match if the property _equals_ the specified value. + +## UserPrincipalName + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_userPrincipalName_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|String (wildcards accepted)| + +For example, `Get-User -Filter "UserPrincipalName -like 'julia@*'"`. + +## VoiceMailSettings + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchUCVoiceMailSettings_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String or `$null`| + +For example, `Get-User -Filter 'VoiceMailSettings -ne $null'`. + +## WebPage + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_wWWHomePage_|**Get-Contact**
**Get-LinkedUser**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-User -Filter "WebPage -like 'https://intranet.contoso.com/*'"`. + +## WhenChanged + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_WhenChanged_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-Recipient -Filter "WhenChanged -gt '8/1/2017 2:00:00 PM'"`. + +## WhenChangedUTC + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-Recipient -Filter "WhenChangedUTC -gt '8/1/2017 2:00:00 PM'"`. + +## WhenCreated + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_whenCreated_|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-Recipient -Filter "WhenCreated -gt '8/1/2017 2:00:00 PM'"`. + +## WhenCreatedUTC + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|n/a|**Get-CASMailbox**
**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-SecurityPrincipal**
**Get-UMMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-Recipient -Filter "WhenCreatedUTC -gt '8/1/2017 2:00:00 PM'"`. + +## WhenMailboxCreated + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchWhenMailboxCreated_|**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +For example, `Get-Recipient -Filter "WhenMailboxCreated -gt '8/1/2017 2:00:00 PM'"`. + +## WhenSoftDeleted + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchWhenSoftDeletedTime_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**
**Get-UnifiedGroup**|A date/time value: 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC)| + +This filter requires the _SoftDeleted_ switch in the command for mailboxes. + +For example, `Get-Mailbox -SoftDeletedMailbox -Filter "WhenSoftDeleted -gt '8/1/2017 2:00:00 PM'"`. + +## WindowsEmailAddress + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_mail_|**Get-Contact**
**Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Group**
**Get-LinkedUser**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-RemoteMailbox**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter "WindowsEmailAddress -like '@fabrikam.com*'"`. + +## WindowsLiveID + +|LDAP display name|Available on cmdlets|Value| +|---|---|---| +|_msExchWindowsLiveID_|**Get-LinkedUser**
**Get-Mailbox**
**Get-MailUser**
**Get-Recipient**
**Get-User**|String (wildcards accepted) or `$null`| + +For example, `Get-Mailbox -Filter "WindowsEmailAddress -like '@fabrikam.onmicrosoft.com*'"`.| + +## For more information + +Exchange 2007 was the first version of Exchange that required OPATH filters instead of LDAP filters. For more information about converting LDAP filters to OPATH filters, see the Microsoft Exchange Team Blog article, [Need help converting your LDAP filters to OPATH?](https://techcommunity.microsoft.com/t5/exchange-team-blog/need-help-converting-your-ldap-filters-to-opath/ba-p/595108). diff --git a/exchange/docs-conceptual/filters-v2.md b/exchange/docs-conceptual/filters-v2.md new file mode 100644 index 0000000000..aae21efdc2 --- /dev/null +++ b/exchange/docs-conceptual/filters-v2.md @@ -0,0 +1,72 @@ +--- +title: Filters in the Exchange Online PowerShell module +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/1/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn about how to use filtering for cmdlets in the Exchange Online V2 module and V3 module." +--- + +# Filters in the Exchange Online PowerShell module + +The Exchange Online PowerShell module contains nine exclusive **Get-EXO\*** cmdlets that are optimized for high speed, high volume operations, and (after you connect to your organization) gives you access to the hundreds of existing cmdlets in the service. For more information, see [Cmdlets in the Exchange Online PowerShell module](exchange-online-powershell-v2.md#cmdlets-in-the-exchange-online-powershell-module). + +In order to get the most out of filters in the nine exclusive **Get-EXO\*** cmdlets in the module, you need to follow the guidance in this article. + +> [!TIP] +> Version 3.0.0 and later (2022) is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module). Version 2.0.5 and earlier (2021) was known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). + +## Use client-side filtering for the best performance + +Server-side filtering uses the available _Filter_ or _RecipientFilter_ parameters on a cmdlet. + +Client-side filtering uses the [Where-Object](/powershell/module/microsoft.powershell.core/where-object) cmdlet (also known as **where** or **?**). + +Generally, you get much better performance in Exchange PowerShell cmdlets with server-side filtering. However, for the Exchange Online PowerShell module, you actually get better performance when you use client-side filtering. We're working on improving the performance of server-side filtering in the module. + +## Unsupported filterable properties + +The **Get-EXO\*** cmdlets in the module support the majority of [filterable properties](filter-properties.md) that are available in their older, equivalent cmdlets. But, there are currently some properties that don't work with filtering in the **Get-EXO\*** cmdlets. These properties are described in the following table: + +|Cmdlet|Unsupported filterable property|LDAP Display Name| +|---|---|---| +|[Get-EXOCASMailbox](/powershell/module/exchange/get-exocasmailbox)|MemberOfGroup

ExternalDirectoryObjectId|memberOf

msExchExternalDirectoryObjectId| +|[Get-EXOMailbox](/powershell/module/exchange/get-exomailbox)|DeletedItemFlags

LanguagesRaw

MasterAccountSid

MemberOfGroup

RequireAllSendersAreAuthenticated

SCLDeleteThresholdInt

SCLJunkThresholdInt

SCLQuarantineThresholdInt

SCLRejectThresholdInt|deletedItemFlags

msExchUserCulture

msExchMasterAccountSid

memberOf

msExchRequireAuthToSendTo

msExchMessageHygieneSCLDeleteThreshold

msExchMessageHygieneSCLJunkThreshold

msExchMessageHygieneSCLQuarantineThreshold

msExchMessageHygieneSCLRejectThreshold| +|[Get-EXORecipient](/powershell/module/exchange/get-exorecipient)|CountryCode

ExternalDirectoryObjectId

MasterAccountSid

MemberOfGroup

Members|countryCode

msExchExternalDirectoryObjectId

msExchMasterAccountSid

memberOf

member| + +## Supported operators + +The following operators are fully supported for all string formats in the **Get-EXO\*** cmdlets in the Exchange Online PowerShell module: + +- [Logical operators](/powershell/module/microsoft.powershell.core/about/about_logical_operators): + - `-and` + - `-not` + - `-or` + +- [Comparison operators](/powershell/module/microsoft.powershell.core/about/about_comparison_operators) + - `-eq` + - `-ne` + - `-lt` + - `-gt` + - `-like` + - `-notlike` + +The `-like` and `-notlike` operators are limited in using wildcards (*). Specifically, you can only use wildcards at the beginning of a string value, at the end of a string value, or both. + +For example, the following text search is not supported: + +`"UPN -like 'A*B*C'` + +However, the following searches are supported: + +`"UPN -like 'A*' -and UPN -like '*C' -and UPN like '*B*'"` diff --git a/exchange/docs-conceptual/find-exchange-cmdlet-permissions.md b/exchange/docs-conceptual/find-exchange-cmdlet-permissions.md new file mode 100644 index 0000000000..e19393384e --- /dev/null +++ b/exchange/docs-conceptual/find-exchange-cmdlet-permissions.md @@ -0,0 +1,174 @@ +--- +title: "Find the permissions required to run any Exchange cmdlet" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 06/06/2024 +ms.audience: ITPro +audience: ITPro +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: 5bcc46d3-8a07-4e9f-b1b0-e4cb0b0afc12 +description: "Admins can learn how to use PowerShell to find the permissions required to run any cmdlet in Exchange Server PowerShell or Exchange Online PowerShell." +--- + +# Find the permissions required to run any Exchange cmdlet + +You can use PowerShell to find the permissions required to run any Exchange or Exchange Online cmdlet. This procedure shows the role-based access control (RBAC) management roles and role groups that give you access to a specified cmdlet—even if your organization has custom roles, custom role groups, or custom role assignments. + +> [!TIP] +> Currently, the procedures in this article don't work with Microsoft 365 Group cmdlets (**\*-UnifiedGroup**) in Exchange Online PowerShell. + +## What do you need to know before you begin? + +- Estimated time to complete this procedure: less than 5 minutes. + +- You can only use PowerShell to perform these procedures. + +- The procedures in this article don't work in Security & Compliance PowerShell. For more information about Security & Compliance permissions, see the following articles: + - [Permissions in the Microsoft Defender portal](/defender-office-365/mdo-portal-permissions) + - [Permissions in the Microsoft Purview compliance portal](/purview/purview-compliance-portal-permissions) + +- You need to be assigned permissions before you can do the procedures in this article. You have the following options: + - [Exchange Server permissions](/exchange/permissions/permissions): Membership in one of the following role groups: + - **Compliance Management** + - **Hygiene Management** + - **Organization Management** + - **View-Only Organization Management** + - [Exchange Online permissions](/exchange/permissions-exo/permissions-exo): Membership in one of the following role groups: + - **Compliance Management** + - **Delegated Setup** + - **Hygiene Management** + - **Organization Management** + - **View-Only Organization Management** + - [Microsoft Entra permissions](/entra/identity/role-based-access-control/manage-roles-portal): Membership in the **Global Administrator**\* or **Global Reader** roles gives users the required permissions _and_ permissions for other features in Microsoft 365. + + > [!IMPORTANT] + > \* Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## Use PowerShell to find the permissions required to run a cmdlet + +1. If you haven't already, open the Exchange PowerShell environment that you're interested in: + - **Exchange Online**: [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md). + - **Exchange Online Protection** (Microsoft 365 organizations without Exchange Online mailboxes): [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md). + - **Exchange Server**: [Open the Exchange Management Shell](open-the-exchange-management-shell.md) or [Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md). + +2. Replace `` and optionally, `,,...` with the values that you want to use, and run the following command: + + ```powershell + $Perms = Get-ManagementRole -Cmdlet [-CmdletParameters ,,...] + ``` + + > [!TIP] + > If you specify multiple parameters, only roles that include _all_ of the specified parameters on the cmdlet are returned. + +3. Run the following command: + + ```powershell + $Perms | foreach {Get-ManagementRoleAssignment -Role $_.Name -Delegating $false | Format-Table -Auto Role,RoleAssigneeType,RoleAssigneeName} + ``` + +## Interpreting the results + +The results contain the following information: + +- **Role**: Indicates the role that gives access to the cmdlet or the combination of cmdlet and parameters. Role names that begin with "My" are user roles that allow regular users to operate on objects they own (for example, their own mailbox or their distribution groups). + +- **RoleAssigneeType** and **RoleAssigneeName**: These values are inter-related: + - **RoleAssigneeType** is the type of object that has the role assigned to it. For administrator roles, this value is typically a role group, but it can also be a role assignment policy, a security group, or a user. + - **RoleAssigneeName** is the name of the role group, role assignment policy, security group, or user. + +## Troubleshooting + +What if there are no results? + +- Verify that you entered the cmdlet and parameter names correctly. +- Multiple parameters for a cmdlet might not be defined in a single role (some parameters might be in one role, while the others are in a different role). Take it one step at a time: + - Run the first command with no parameters, and then run the second command. + - Add one parameter to the first command, and then run the second command. + - Repeat the previous step by adding other parameters to the first command before running the second command. + +Otherwise, no results are likely caused by one of the following conditions: + +- The cmdlet or parameters are defined in a role that isn't assigned to any role groups by default. +- The cmdlet or parameters aren't available in your environment. For example, you specified an Exchange Online cmdlet or Exchange Online parameters in an on-premises Exchange environment. + +To find the roles in your environment (if any) that contain the cmdlet or parameters, replace `` and optionally, `,,...` with the values that you want to use and run the following command: + +```powershell +Get-ManagementRoleEntry -Identity *\ [-Parameters ,,...] +``` + +> [!TIP] +> You can use wildcard characters (\*) in the cmdlet and parameter names (for example, `*-Mailbox*`). + +If the command returns an error saying the object couldn't be found, the cmdlet or parameters aren't available in your environment. + +If the command returns results, the cmdlet or parameters are available in your environment, but the required role isn't assigned to any role groups. To find roles that aren't assigned to any role groups, run the following command: + +```powershell +$na = Get-ManagementRole; $na | foreach {If ((Get-ManagementRoleAssignment -Role $_.Name -Delegating $false) -eq $null) {$_.Name}} +``` + +## Related procedures + +### Include management role scopes + +Management role scopes (in particular, write scopes) define where cmdlets can operate. For example, the entire organization or only on specific user objects. + +To include scope information in the [Use PowerShell to find the permissions required to run a cmdlet](#use-powershell-to-find-the-permissions-required-to-run-a-cmdlet) output, add `*Scope*` to the second command: + +```powershell +$Perms | foreach {Get-ManagementRoleAssignment -Role $_.Name -Delegating $false | Format-List Role,RoleAssigneeType,RoleAssigneeName,*Scope*} +``` + +For detailed information about management role scopes, see [Understanding management role scopes](/exchange/understanding-management-role-scopes-exchange-2013-help). + +### Find all roles assigned to a specific user + +To see all roles that are assigned to a specific user, replace `` with the name, alias, or email address of the user and run the following command: + +```powershell +Get-ManagementRoleAssignment -RoleAssignee -Delegating $false | Format-Table -Auto Role,RoleAssigneeName,RoleAssigneeType +``` + +For example: + +```powershell +Get-ManagementRoleAssignment -RoleAssignee julia@contoso.com -Delegating $false | Format-Table -Auto Role,RoleAssigneeName,RoleAssigneeType +``` + +> [!TIP] +> The _RoleAssignee_ parameter returns both direct role assignments to users (uncommon) and indirect role assignments granted to the user through their membership in role groups. + +### Find all users who have a specific role assigned + +To see all users who have a specific role assigned to them, replace `` with the name of the role and run the following command: + +```powershell +Get-ManagementRoleAssignment -Role "" -GetEffectiveUsers -Delegating $false | Where-Object {$_.EffectiveUserName -ne "All Group Members"} | Format-Table -Auto EffectiveUserName,Role,RoleAssigneeName,AssignmentMethod +``` + +For example: + +```powershell +Get-ManagementRoleAssignment -Role "Mailbox Import Export" -GetEffectiveUsers -Delegating $false | Where-Object {$_.EffectiveUserName -ne "All Group Members"} | Format-Table -Auto EffectiveUserName,Role,RoleAssigneeName,AssignmentMethod +``` + +### Find the members of a role group + +To see the members of a specific role group, replace `` with the name of the role group and run the following command: + +```powershell +Get-RoleGroupMember "" +``` + +For example: + +```powershell +Get-RoleGroupMember "Organization Management" +``` + +> [!TIP] +> To see the names of all available role groups, run `Get-RoleGroup`. diff --git a/exchange/docs-conceptual/index.md b/exchange/docs-conceptual/index.md deleted file mode 100644 index d47c4726db..0000000000 --- a/exchange/docs-conceptual/index.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: Exchange PowerShell -description: Learn about the Exchange PowerShell environments that are available in on-premises Exchange and Office 365. -services: exchange-online -author: chrisda -manager: dansimp -layout: LandingPage -ms.assetid: 9983a964-f642-4fcd-856b-452a172bcd4e -ms.service: exchange-online -ms.tgt_pltfrm: na -ms.devlang: na -ms.topic: landing-page -ms.date: 3/16/2018 -ms.author: chrisda ---- -# Exchange PowerShell - -Exchange PowerShell enables you to manage your Exchange Server and Office 365 organizations from the command line. For more information, select your environment: - -

diff --git a/exchange/docs-conceptual/index.yml b/exchange/docs-conceptual/index.yml new file mode 100644 index 0000000000..7fe140c922 --- /dev/null +++ b/exchange/docs-conceptual/index.yml @@ -0,0 +1,65 @@ +### YamlMime:Landing + +title: Exchange PowerShell documentation # < 60 chars +summary: Learn about the PowerShell environments that are available in on-premises Exchange Server and Microsoft 365. # < 160 chars + +metadata: + title: Exchange PowerShell documentation # Required; page title displayed in search results. Include the brand. < 60 chars. + description: Learn about the PowerShell environments that are available in on-premises Exchange and Microsoft 365. # Required; article description that is displayed in search results. < 160 chars. + services: exchange-online + ms.service: exchange-online #Required; service per approved list. service slug assigned to your service by ACOM. + ms.topic: landing-page # Required + ms.assetid: 9983a964-f642-4fcd-856b-452a172bcd4e + manager: deniseb + author: chrisda #Required; your GitHub user alias, with correct capitalization. + ms.author: chrisda #Required; microsoft alias of author; optional team alias. + ms.date: 9/1/2023 #Required; mm/dd/yyyy format. + +# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new + +landingContent: +# Cards and links should be based on top customer tasks or top subjects +# Start card title with a verb + # Card (optional) + - title: About + linkLists: + - linkListType: overview + links: + - text: Exchange Server PowerShell + url: /powershell/exchange/exchange-management-shell + - text: Exchange Online PowerShell + url: /powershell/exchange/exchange-online-powershell + - text: Security & Compliance PowerShell + url: /powershell/exchange/scc-powershell + - text: Exchange Online Protection PowerShell + url: /powershell/exchange/exchange-online-protection-powershell + - title: Connect + linkLists: + - linkListType: overview + links: + - text: Open the Exchange Management Shell + url: /powershell/exchange/open-the-exchange-management-shell + - text: Remotely connect to Exchange Server PowerShell + url: /powershell/exchange/connect-to-exchange-servers-using-remote-powershell + - text: Connect to Exchange Online PowerShell + url: /powershell/exchange/connect-to-exchange-online-powershell + - text: Connect to Security & Compliance PowerShell + url: /powershell/exchange/connect-to-scc-powershell + - text: Connect to Exchange Online Protection PowerShell + url: /powershell/exchange/connect-to-exchange-online-protection-powershell + - title: More + linkLists: + - linkListType: overview + links: + - text: Exchange cmdlet syntax + url: /powershell/exchange/exchange-cmdlet-syntax + - text: Find the permissions required to run any Exchange cmdlet + url: /powershell/exchange/find-exchange-cmdlet-permissions + - text: Control remote PowerShell access to Exchange servers + url: /powershell/exchange/control-remote-powershell-access-to-exchange-servers + - text: About the Exchange Online PowerShell module + url: /powershell/exchange/exchange-online-powershell-v2 + - text: What's new in the Exchange Online PowerShell module + url: /powershell/exchange/whats-new-in-the-exo-module + - text: Enable or disable access to Exchange Online PowerShell + url: /powershell/exchange/disable-access-to-exchange-online-powershell diff --git a/exchange/docs-conceptual/invoke-command-workarounds-rest-api.md b/exchange/docs-conceptual/invoke-command-workarounds-rest-api.md new file mode 100644 index 0000000000..50aba1763d --- /dev/null +++ b/exchange/docs-conceptual/invoke-command-workarounds-rest-api.md @@ -0,0 +1,127 @@ +--- +title: Workarounds for Invoke-Command scenarios in REST API connections +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 7/5/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.reviewer: +ms.localizationpriority: medium +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn about the alternatives to Invoke-Command commands in REST API connections using the EXO V3 module." +--- + +# Workarounds for Invoke-Command scenarios in REST API connections + +In multiple connections to Exchange Online or Security & Compliance PowerShell in the same window, you use the [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command) cmdlet to run scripts or commands in a specific remote PowerShell session. But, the **Invoke-Command** cmdlet doesn't work in [REST API connections](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module) to Exchange Online or Security & Compliance PowerShell. + +This article offers REST API alternatives for scenarios that that use **Invoke-Command** commands. + +## Scenario 1: Run Exchange Online cmdlets + +This example finds the identity of any other user (`$Us = $User.Identity`). + +> [!TIP] +> Other commands were required to get the values of `$User` and therefore `$Us`. Those commands aren't important. The overall approach that's being used is what's important. + +- **In a remote PowerShell session**: Use the **Get-PSSession** cmdlet to store the remote PowerShell session details in the variable named `$Session`, and then run the following command: + + ```powershell + Invoke-Command -Session $Session -ScriptBlock {Get-User $Using:Us | Select-Object DistinguishedName, ExternalDirectoryObjectId} -ErrorAction SilentlyContinue + ``` + +- **In a REST API session**: Run the following command: + + ```powershell + Get-User $Us | Format-List DistinguishedName, ExternalDirectoryObjectId + ``` + +This example finds the identity of a group member: + +- **In a remote PowerShell session**: Use the **Get-PSSession** cmdlet to store the remote PowerShell session details in the variable named `$Session`, and then run the following command: + + ```powershell + Invoke-Command -Session $Session -ScriptBlock {Get-Recipient -Filter "Members -eq '$($User.DistinguishedName)'" -RecipientTypeDetails MailUniversalDistributionGroup | Select-Object DisplayName, ExternalDirectoryObjectId, RecipientTypeDetails} -ErrorAction SilentlyContinue -HideComputerName + ``` + +- **In a REST API session**: Run the following command: + + ```powershell + Get-Recipient -Filter "Members -eq '$($User.DistinguishedName)'" -RecipientTypeDetails MailUniversalDistributionGroup | Format-List DisplayName, ExternalDirectoryObjectId, RecipientTypeDetails + ``` + +## Scenario 2: Run Exchange Online cmdlets and expand specific properties + +This example finds all mailboxes where the GrantSendOnBehalfTo permission is set, and then returns the users who have the permission on the mailbox. + +- **In a remote PowerShell session**: Use the **Get-PSSession** cmdlet to store the remote PowerShell session details in the variable named `$Session`, and then run the following command: + + ```powershell + Invoke-Command -Session $Session -ScriptBlock {Get-Mailbox -Filter "GrantSendOnBehalfTo -ne `$null" -ErrorAction SilentlyContinue | Select-Object ExternalDirectoryObjectId, GrantSendOnBehalfTo -ExpandProperty GrantSendOnBehalfTo} + ``` + +- **In a REST API session**: Run the following command: + + ```powershell + $mailboxes = Get-Mailbox -Filter "GrantSendOnBehalfTo -ne `$null" + + foreach ($mailbox in $mailboxes) + + { + $users = $mailbox | Select-Object GrantSendOnBehalfTo -ExpandProperty GrantSendOnBehalfTo | Get-User + + $users | Select-Object Name, Guid + } + ``` + +## Scenario 3: Run Exchange Online cmdlets in a specific PowerShell session when multiple sessions are present + +This example shows how to create two PowerShell sessions in the same window and run the **Get-Mailbox** cmdlet in each session. + +- **In a remote PowerShell session**: + 1. Use the **Get-PSSession** cmdlet to store the first remote PowerShell session details in the variable named `$Session1`. + 2. Use the **Get-PSSession** cmdlet to store the second remote PowerShell session details in the variable named `$Session2`. + 3. Run the following commands: + + ```powershell + Invoke-Command -Session $Session1 -ScriptBlock {Get-Mailbox -ResultSize 1} + + Invoke-Command -Session $Session2 -ScriptBlock {Get-Mailbox -ResultSize 1} + ``` + +- **In a REST API session**: + 1. In the first **Connect-ExchangeOnline** command, use the parameter _Prefix_ with the value C1. + 2. Store the first REST API connection details in the variable named `$ConnectionInfo1` by running the following command: + + ```powershell + $ConnectionInfo1 = Get-ConnectionInformation | Where-Object { $_.ModulePrefix -eq "C1"} + ``` + + 3. In the second **Connect-ExchangeOnline** command, use the parameter _Prefix_ with the value C2. + 4. Store the second REST API connection details in the variable named `$ConnectionInfo2` by running the following command: + + ```powershell + $ConnectionInfo1 = Get-ConnectionInformation | Where-Object { $_.ModulePrefix -eq "C2"} + ``` + + 5. Now you can run commands in either session. For example: + + ```powershell + $CommandStr1 = "Get-$($ConnectionInfo1.ModulePrefix)Mailbox -ResultSize 10" + + Invoke-Expression $CommandStr1 + ``` + + Or + + ```powershell + $CommandStr2 = "Get-$($ConnectionInfo2.ModulePrefix)Mailbox -ResultSize 10" + + Invoke-Expression $CommandStr2 + ``` diff --git a/exchange/docs-conceptual/media/0fd389a1-a32d-4e2f-bf5f-78e9b6407d4c.png b/exchange/docs-conceptual/media/0fd389a1-a32d-4e2f-bf5f-78e9b6407d4c.png deleted file mode 100644 index ab6fca6e9e..0000000000 Binary files a/exchange/docs-conceptual/media/0fd389a1-a32d-4e2f-bf5f-78e9b6407d4c.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/24645e56-8b11-4c0f-ace4-09bdb2703562.png b/exchange/docs-conceptual/media/24645e56-8b11-4c0f-ace4-09bdb2703562.png deleted file mode 100644 index e3bb7eb65a..0000000000 Binary files a/exchange/docs-conceptual/media/24645e56-8b11-4c0f-ace4-09bdb2703562.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/MSN_Video_Widget.gif b/exchange/docs-conceptual/media/MSN_Video_Widget.gif deleted file mode 100644 index 852a7daa98..0000000000 Binary files a/exchange/docs-conceptual/media/MSN_Video_Widget.gif and /dev/null differ diff --git a/exchange/docs-conceptual/media/add-icon.png b/exchange/docs-conceptual/media/add-icon.png new file mode 100644 index 0000000000..9a4d36acf7 Binary files /dev/null and b/exchange/docs-conceptual/media/add-icon.png differ diff --git a/exchange/docs-conceptual/media/app-only-auth-exchange-api-perms.png b/exchange/docs-conceptual/media/app-only-auth-exchange-api-perms.png deleted file mode 100644 index 03747a57d4..0000000000 Binary files a/exchange/docs-conceptual/media/app-only-auth-exchange-api-perms.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/app-only-auth-exchange-manageasapp.png b/exchange/docs-conceptual/media/app-only-auth-exchange-manageasapp.png deleted file mode 100644 index eddd6fc8da..0000000000 Binary files a/exchange/docs-conceptual/media/app-only-auth-exchange-manageasapp.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/app-only-auth-register-app.png b/exchange/docs-conceptual/media/app-only-auth-register-app.png deleted file mode 100644 index c70d779bd4..0000000000 Binary files a/exchange/docs-conceptual/media/app-only-auth-register-app.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/app-only-auth-role-assignment.png b/exchange/docs-conceptual/media/app-only-auth-role-assignment.png deleted file mode 100644 index db6f44f177..0000000000 Binary files a/exchange/docs-conceptual/media/app-only-auth-role-assignment.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/app-only-auth-upload-cert.png b/exchange/docs-conceptual/media/app-only-auth-upload-cert.png deleted file mode 100644 index e06831dc87..0000000000 Binary files a/exchange/docs-conceptual/media/app-only-auth-upload-cert.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/b85d80d9-1043-4c7c-8f14-d87d8d56b188.png b/exchange/docs-conceptual/media/b85d80d9-1043-4c7c-8f14-d87d8d56b188.png deleted file mode 100644 index 9973407fe0..0000000000 Binary files a/exchange/docs-conceptual/media/b85d80d9-1043-4c7c-8f14-d87d8d56b188.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/connect-exo-mfa-verify-prompt.png b/exchange/docs-conceptual/media/connect-exo-mfa-verify-prompt.png new file mode 100644 index 0000000000..9878357ce7 Binary files /dev/null and b/exchange/docs-conceptual/media/connect-exo-mfa-verify-prompt.png differ diff --git a/exchange/docs-conceptual/media/connect-exo-password-prompt.png b/exchange/docs-conceptual/media/connect-exo-password-prompt.png new file mode 100644 index 0000000000..0046efef70 Binary files /dev/null and b/exchange/docs-conceptual/media/connect-exo-password-prompt.png differ diff --git a/exchange/docs-conceptual/media/d3a405ce-5364-4732-a7bb-2cc9c678da2d.png b/exchange/docs-conceptual/media/d3a405ce-5364-4732-a7bb-2cc9c678da2d.png deleted file mode 100644 index 014a8d3165..0000000000 Binary files a/exchange/docs-conceptual/media/d3a405ce-5364-4732-a7bb-2cc9c678da2d.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-admin-consent-granted.png b/exchange/docs-conceptual/media/exo-app-only-auth-admin-consent-granted.png new file mode 100644 index 0000000000..75ff84fb7f Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-admin-consent-granted.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-admin-consent-removed-from-graph.png b/exchange/docs-conceptual/media/exo-app-only-auth-admin-consent-removed-from-graph.png new file mode 100644 index 0000000000..1da31d9437 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-admin-consent-removed-from-graph.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-add-a-permission.png b/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-add-a-permission.png new file mode 100644 index 0000000000..52056bb322 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-add-a-permission.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-select-exchange-manageasapp.png b/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-select-exchange-manageasapp.png new file mode 100644 index 0000000000..e39a40aaec Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-select-exchange-manageasapp.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-select-o365-exo.png b/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-select-o365-exo.png new file mode 100644 index 0000000000..5db4cced79 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-api-permissions-select-o365-exo.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-app-assigned-to-role-scc.png b/exchange/docs-conceptual/media/exo-app-only-auth-app-assigned-to-role-scc.png new file mode 100644 index 0000000000..4783aede58 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-app-assigned-to-role-scc.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-app-assigned-to-role.png b/exchange/docs-conceptual/media/exo-app-only-auth-app-assigned-to-role.png new file mode 100644 index 0000000000..5e05c99150 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-app-assigned-to-role.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-app-registration-page.png b/exchange/docs-conceptual/media/exo-app-only-auth-app-registration-page.png new file mode 100644 index 0000000000..c43cf46b86 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-app-registration-page.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-certificate-successfully-added.png b/exchange/docs-conceptual/media/exo-app-only-auth-certificate-successfully-added.png new file mode 100644 index 0000000000..27c2e1e65d Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-certificate-successfully-added.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-find-add-select-app-for-assignment.PNG b/exchange/docs-conceptual/media/exo-app-only-auth-find-add-select-app-for-assignment.PNG new file mode 100644 index 0000000000..09b7bcb514 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-find-add-select-app-for-assignment.PNG differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-find-and-select-supported-role-scc.png b/exchange/docs-conceptual/media/exo-app-only-auth-find-and-select-supported-role-scc.png new file mode 100644 index 0000000000..10075fff24 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-find-and-select-supported-role-scc.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-find-and-select-supported-role.png b/exchange/docs-conceptual/media/exo-app-only-auth-find-and-select-supported-role.png new file mode 100644 index 0000000000..2b4aa3aaf5 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-find-and-select-supported-role.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-find-app-registrations.png b/exchange/docs-conceptual/media/exo-app-only-auth-find-app-registrations.png new file mode 100644 index 0000000000..ebdbe372a5 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-find-app-registrations.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-find-roles-and-administrators.png b/exchange/docs-conceptual/media/exo-app-only-auth-find-roles-and-administrators.png new file mode 100644 index 0000000000..373d9995a9 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-find-roles-and-administrators.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-manifest-select-api-permissions.png b/exchange/docs-conceptual/media/exo-app-only-auth-manifest-select-api-permissions.png new file mode 100644 index 0000000000..da6ca1af65 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-manifest-select-api-permissions.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-new-app-registration.png b/exchange/docs-conceptual/media/exo-app-only-auth-new-app-registration.png new file mode 100644 index 0000000000..dc4154af4a Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-new-app-registration.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-original-permissions.png b/exchange/docs-conceptual/media/exo-app-only-auth-original-permissions.png new file mode 100644 index 0000000000..4d52b45e84 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-original-permissions.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-register-app.png b/exchange/docs-conceptual/media/exo-app-only-auth-register-app.png new file mode 100644 index 0000000000..d06da71669 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-register-app.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-role-assignments-click-add-assignments-scc.png b/exchange/docs-conceptual/media/exo-app-only-auth-role-assignments-click-add-assignments-scc.png new file mode 100644 index 0000000000..4fb99251c5 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-role-assignments-click-add-assignments-scc.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-role-assignments-click-add-assignments.png b/exchange/docs-conceptual/media/exo-app-only-auth-role-assignments-click-add-assignments.png new file mode 100644 index 0000000000..64f2025b8f Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-role-assignments-click-add-assignments.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-role-description-page-click-assignments.PNG b/exchange/docs-conceptual/media/exo-app-only-auth-role-description-page-click-assignments.PNG new file mode 100644 index 0000000000..4f7e9e97ab Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-role-description-page-click-assignments.PNG differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-select-certificates-and-secrets.png b/exchange/docs-conceptual/media/exo-app-only-auth-select-certificates-and-secrets.png new file mode 100644 index 0000000000..1c5f46f150 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-select-certificates-and-secrets.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-select-manifest.png b/exchange/docs-conceptual/media/exo-app-only-auth-select-manifest.png new file mode 100644 index 0000000000..89eb491ef9 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-select-manifest.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-select-upload-certificate.png b/exchange/docs-conceptual/media/exo-app-only-auth-select-upload-certificate.png new file mode 100644 index 0000000000..bf40ab47a3 Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-select-upload-certificate.png differ diff --git a/exchange/docs-conceptual/media/exo-app-only-auth-upload-certificate-dialog.png b/exchange/docs-conceptual/media/exo-app-only-auth-upload-certificate-dialog.png new file mode 100644 index 0000000000..77ef07a65a Binary files /dev/null and b/exchange/docs-conceptual/media/exo-app-only-auth-upload-certificate-dialog.png differ diff --git a/exchange/docs-conceptual/media/f3b4c351-17d9-42d9-8540-e48e01779b31.png b/exchange/docs-conceptual/media/f3b4c351-17d9-42d9-8540-e48e01779b31.png deleted file mode 100644 index f1c37dbfc8..0000000000 Binary files a/exchange/docs-conceptual/media/f3b4c351-17d9-42d9-8540-e48e01779b31.png and /dev/null differ diff --git a/exchange/docs-conceptual/media/mi-add-exo-module.png b/exchange/docs-conceptual/media/mi-add-exo-module.png new file mode 100644 index 0000000000..fa36117aa4 Binary files /dev/null and b/exchange/docs-conceptual/media/mi-add-exo-module.png differ diff --git a/exchange/docs-conceptual/media/search-icon.png b/exchange/docs-conceptual/media/search-icon.png new file mode 100644 index 0000000000..6241aea737 Binary files /dev/null and b/exchange/docs-conceptual/media/search-icon.png differ diff --git a/exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md b/exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md deleted file mode 100644 index f111138322..0000000000 --- a/exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: "Connect to Office 365 Security & Compliance Center PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: o365-security-and-compliance -localization_priority: Normal -ms.assetid: 45a5242d-95b7-4a6a-9794-095bb6d8d9d0 -search.appverid: MET150 -description: "Learn how to connect to Security & Compliance Center PowerShell." ---- - -# Connect to Office 365 Security & Compliance Center PowerShell - -Office 365 Security & Compliance Center PowerShell allows you to manage your Office 365 Security & Compliance Center settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to the Security & Compliance Center. It's a simple three-step process where you enter your Office 365 credentials, provide the required connection settings, and then import the Security & Compliance Center cmdlets into your local Windows PowerShell session so that you can use them. - -> [!NOTE] -> The procedures in this topic won't work if:
* Your account uses multi-factor authentication (MFA).
* Your organization uses federated authentication.
* A location condition in an Azure Active Directory conditional access policy restricts your access to trusted IPs.
In these scenarions, you need to download and use the Exchange Online Remote PowerShell Module to connect to Security & Compliance Center PowerShell. For instructions, see [Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication](mfa-connect-to-scc-powershell.md).

Some features in the Security & Compliance Center (for example, mailbox archiving) link to existing functionality in the Exchange admin center (EAC). To use PowerShell with these features, you need to connect to Exchange Online PowerShell instead of Security & Compliance Center PowerShell. For instructions, see [Connect to Exchange Online PowerShell](../../exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md). - -For more information about the Security & Compliance Center, see [Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=627054). - -## What do you need to know before you begin? - -- Estimated time to complete: 5 minutes - -- Office 365 global admins have access to the Security & Compliance Center, but everyone else needs to have their access configured for them. For details, see [Give users access to the Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=627057). - -- You can use the following versions of Windows: - - - Windows 10 - - - Windows 8.1 - - - Windows Server 2019 - - - Windows Server 2016 - - - Windows Server 2012 or Windows Server 2012 R2 - - - Windows 7 Service Pack 1 (SP1)* - - - Windows Server 2008 R2 SP1* - - \* This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868), [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757), [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). - -- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You'll get the following error when you try to connect: - - > Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files. - - To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**): - - ```PowerShell - Set-ExecutionPolicy RemoteSigned - ``` - - You need to configure this setting only once on your computer, not every time you connect. - -- Windows Remote Management (WinRM) on your computer needs to allow Basic authentication (it's enabled by default). To verify that Basic authentication is enabled, run this command **in a Command Prompt**: - - ``` - winrm get winrm/config/client/auth - ``` - - If you don't see the value `Basic = true`, you need to run this command to enable Basic authentication for WinRM: - - ``` - winrm set winrm/config/client/auth @{Basic="true"} - ``` - - If Basic authentication is disabled, you'll get this error when you try to connect: - - > The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.` - -## Connect to the Security & Compliance Center - -1. On your local computer, open Windows PowerShell and run the following command: - - ```PowerShell - $UserCredential = Get-Credential - ``` - - In the **Windows PowerShell Credential Request** dialog box that appears, type your work or school account and password, and then click **OK**. - -2. Run the following command: - - ```PowerShell - $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection - ``` - - **Notes**: - - - For Office 365 Germany, use the _ConnectionUri_ value: `https://ps.compliance.protection.outlook.de/powershell-liveid/`. - - - For Office 365 Government Community Cloud High (GCC High), use the _ConnectionUri_ value: `https://ps.compliance.protection.office365.us/powershell-liveid/`. - - - If you want to connect to Security & Compliance Center PowerShell in the same window as an active Exchange Online PowerShell connection, you need to add the Prefix parameter and value (for example, `-Prefix "CC"`) to the end of this command to prevent cmdlet name collisions (both environments share some cmdlets with the same names). - -3. Run the following command: - - ```PowerShell - Import-PSSession $Session -DisableNameChecking - ``` - -> [!NOTE] -> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command: - -```PowerShell -Remove-PSSession $Session -``` - -## How do you know this worked? - -After Step 3, the Security & Compliance Center cmdlets are imported into your local Windows PowerShell session as tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run a Security & Compliance Center cmdlet, for example, **Get-RetentionCompliancePolicy**, and see the results. - -If you receive errors, check the following requirements: - -- A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1. - -- Verify that your account has permission to access the Security & Compliance Center. For details, see [Give users access to the Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=627057). - -- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to the Security & Compliance Center. - -- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy. - -- The **New-PSSession** command (Step 2) might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this: - - > The request for the Windows Remote Shell with ShellId failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation. - - To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Security & Compliance Center PowerShell endpoint. - -## See also - -The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics. - -- [Get-Credential](https://go.microsoft.com/fwlink/p/?LinkId=389618) - -- [New-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389621) - -- [Import-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389619) - -- [Remove-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389620) - -- [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623) diff --git a/exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md b/exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md deleted file mode 100644 index a7d8665074..0000000000 --- a/exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: "Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: -ms.audience: Admin -ms.topic: article -ms.service: o365-security-and-compliance -localization_priority: Normal -ms.assetid: 8e11c808-e734-4874-ac94-e5251ea85c19 -search.appverid: MET150 -description: "Learn how to connect to Security & Compliance Center PowerShell by using multi-factor authentication (MFA) or federated authentication." ---- - -# Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication - -If your account uses multi-factor authentication (MFA) or federated authentication, you can't use the instructions at [Connect to Office 365 Security & Compliance Center PowerShell](connect-to-scc-powershell.md) to use remote PowerShell to connect to the Office 365 Security & Compliance Center. Instead, you need to install the Exchange Online Remote PowerShell Module, and use the **Connect-IPPSSession** cmdlet to connect to Security & Compliance Center PowerShell. - -> [!NOTE] -> Delegated Access Permission (DAP) partners can't use the procedures in this topic to connect to their customer tenant organizations in Security & Compliance Center PowerShell. MFA and the Exchange Online Remote PowerShell Module don't work with delegated authentication.

The Exchange Online Remote PowerShell Module is not supported in PowerShell Core (macOS, Linux, or Windows Nano Server). As a workaround, you can install the module on a computer that's running a supported version of Windows (physical or virtual), and use remote desktop software to connect. - -## What do you need to know before you begin? - -- Estimated time to complete: 5 minutes - -- You can use the following versions of Windows: - - - Windows 10 - - - Windows 8.1 - - - Windows Server 2019 - - - Windows Server 2016 - - - Windows Server 2012 or Windows Server 2012 R2 - - - Windows 7 Service Pack 1 (SP1)* - - - Windows Server 2008 R2 SP1* - - \* This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868), [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757), [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344), and [Windows Management Framework 5.1](https://aka.ms/wmf5download). - -- The Exchange Online Remote PowerShell Module needs to be installed on your computer. If your installed version of the Exchange Online Remote PowerShell Module doesn't have the **Connect-IPPSSession** cmdlet, you need to install the latest version of the module: - - 1. In a browser that supports ClickOnce (for example, Internet Explorer or Edge), open the Exchange admin center (EAC) for your Exchange Online organization. For instructions, see [Exchange admin center in Exchange Online](https://docs.microsoft.com/exchange/exchange-admin-center). - - **Note**: ClickOnce support is available in the Chromium-based version of Edge at , and might not be enabled by default. - - 2. In the EAC, go to **Hybrid** > **Setup** and click the appropriate **Configure** button to download the Exchange Online Remote PowerShell Module for multi-factor authentication. - - ![Download the Exchange Online PowerShell Module from the Hybrid tab in the EAC](../../media/24645e56-8b11-4c0f-ace4-09bdb2703562.png) - - 3. In the **Application Install** window that opens, click **Install**. - - ![Click Install in the Exchange Online PowerShell Module window](../../media/0fd389a1-a32d-4e2f-bf5f-78e9b6407d4c.png) - -- Windows Remote Management (WinRM) on your computer needs to allow Basic authentication (it's enabled by default). To verify that Basic authentication is enabled, run this command **in a Command Prompt**: - - ``` - winrm get winrm/config/client/auth - ``` - - > [!NOTE] - > The Basic authentication header is required to transport the session's OAuth token, since the client-side WinRM implementation has no support for OAuth. - - If you don't see the value `Basic = true`, you need to run this command from an elevated Command Prompt (a Command Prompt window you open by selecting **Run as administrator**) to enable Basic authentication for WinRM: - - ``` - winrm set winrm/config/client/auth @{Basic="true"} - ``` - - If Basic authentication is disabled, you'll get this error when you try to connect: - - `The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.` - -> [!TIP] -> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612), [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). - -## Connect to Security & Compliance Center PowerShell by using MFA or federated authentication - -1. On your local computer, open the **Exchange Online Remote PowerShell Module** (**Microsoft Corporation** > **Microsoft Exchange Online Remote PowerShell Module**). - -2. The command that you need to run uses the following syntax: - - ```PowerShell - Connect-IPPSSession -UserPrincipalName [-ConnectionUri -AzureADAuthorizationEndPointUri ] - ``` - - - _\_ is your Office 365 work or school account. - - - The _\_ and _\_ values depend on the location of your Office 365 organization as described in the following table: - - |**Office 365 offering**|**_ConnectionUri_ parameter value**|**_AzureADAuthorizationEndPointUri_ parameter value**| - |:-----|:-----|:-----| - |Office 365 |Not used |Not used | - |Office 365 Germany | `https://ps.compliance.protection.outlook.de/PowerShell-LiveID` | `https://login.microsoftonline.de/common` | - - This example connects to the Security & Compliance Center in Office 365 using the account chris@contoso.com. - - ```PowerShell - Connect-IPPSSession -UserPrincipalName chris@contoso.com - ``` - - This example connects to the Security & Compliance Center in Office 365 Germany using the account lukas@fabrikam.com. - - ```PowerShell - Connect-IPPSSession -UserPrincipalName lukas@fabrikam.com -ConnectionUri https://ps.compliance.protection.outlook.de/PowerShell-LiveID -AzureADAuthorizationEndPointUri https://login.microsoftonline.de/common - ``` - -3. In the sign-in window that opens, enter your password, and then click **Sign in**. - - ![Enter your password in the Exchange Online Remote PowerShell window](../../media/b85d80d9-1043-4c7c-8f14-d87d8d56b188.png) - - For MFA, a verification code is generated and delivered based on the verification response option that's configured for your account (for example, a text message or the Azure Authenticator app on your mobile phone). - -4. **(MFA only)**: In the verification window that opens, enter the verification code, and then click **Sign in**. - - ![Enter your verification code in the Exchange Online Remote PowerShell window](../../media/d3a405ce-5364-4732-a7bb-2cc9c678da2d.png) - -5. **(Optional)**: If you want to connect to an Exchange Online PowerShell module session in the same window, you need to run - - ```PowerShell - $EXOSession=New-ExoPSSession -UserPrincipalName [-ConnectionUri -AzureADAuthorizationEndPointUri ] - ``` - - and then import the Exchange Online session into the current one using an specific prefix - - ```PowerShell - Import-PSSession $EXOSession -Prefix EXO - ``` - -## How do you know this worked? - -After you sign in, the Security & Compliance Center cmdlets are imported into your Exchange Online Remote PowerShell Module session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Security & Compliance Center cmdlet, for example, **Get-RetentionCompliancePolicy**, and see the results. - -If you receive errors, check the following requirements: - -- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to the Security & Compliance Center. - -- The account you use to connect to the Security & Compliance Center must be enabled for remote PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](../../exchange-online/disable-access-to-exchange-online-powershell.md). - -- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy. - -- The **Connect-IPPSSession** command (Step 2) might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this: - - `The request for the Windows Remote Shell with ShellId failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.` - - To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Security & Compliance PowerShell endpoint. diff --git a/exchange/docs-conceptual/office-365-scc/office-365-scc-powershell.md b/exchange/docs-conceptual/office-365-scc/office-365-scc-powershell.md deleted file mode 100644 index 123f271370..0000000000 --- a/exchange/docs-conceptual/office-365-scc/office-365-scc-powershell.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "Office 365 Security & Compliance Center PowerShell" -ms.author: chrisda -author: chrisda -manager: dansimp -ms.date: 9/29/2015 -ms.audience: Admin -ms.topic: article -ms.service: o365-security-and-compliance -localization_priority: Normal -ms.assetid: 2f33bb84-cede-46f6-9d39-d246e8ce3543 -search.appverid: MET150 -description: "Learn about using PowerShell in the Office 365 Security & Compliance Center." ---- - -# Office 365 Security & Compliance Center PowerShell - -Security & Compliance Center PowerShell is the administrative interface that enables you to manage your Office 365 Security & Compliance Center settings from the command line. For example, you can use Security & Compliance Center PowerShell to perform Compliance Searches and configure access to the Security & Compliance Center. The following topics provide information about using Security & Compliance Center PowerShell: - -- To create a remote PowerShell session to the Security & Compliance Center, see [Connect to Office 365 Security & Compliance Center PowerShell](connect-to-scc-powershell/connect-to-scc-powershell.md). Note that the connection instructions are different from Exchange Online or Exchange Online Protection (the _ConnectionUri_ value is different). - -- A cmdlet is a lightweight command that is imported into your local Windows PowerShell session. Note that some cmdlets are available only in the Security & Compliance Center. Other cmdlets have the same names and functionality as those in Exchange Online, but they are also available in the Security & Compliance Center. diff --git a/exchange/docs-conceptual/open-the-exchange-management-shell.md b/exchange/docs-conceptual/open-the-exchange-management-shell.md new file mode 100644 index 0000000000..c097a3fc37 --- /dev/null +++ b/exchange/docs-conceptual/open-the-exchange-management-shell.md @@ -0,0 +1,80 @@ +--- +title: "Open the Exchange Management Shell" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/7/2023 +ms.audience: ITPro +audience: ITPro +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: 63976059-25f8-4b4f-b597-633e78b803c0 +description: "Find and open the shortcut for Exchange PowerShell (also known as the Exchange Management Shell) on Exchange servers or computers that have the Exchange management tools installed." +--- + +# Open the Exchange Management Shell + +The Exchange Management Shell enables you to do administrative tasks on Exchange servers from the command line. You can open the Exchange Management Shell from the following locations: + +- On the Exchange server directly or in a Remote Desktop Connection session. +- On a local computer after you install the Exchange management tools. For more information, see [Install the Exchange management tools](/Exchange/plan-and-deploy/post-installation-tasks/install-management-tools). + +## What do you need to know before you begin? + +- Estimated time to complete this procedure: less than 1 minute. + +- To do the procedures in this article, you need to be assigned at least one management role (typically, via membership in a role group). After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Exchange Server permissions](/exchange/permissions/permissions). + +- Running the Exchange Management Shell from a local installation of the Exchange management tools requires remote PowerShell access for your user account. By default, users are allowed to use remote PowerShell to connect to an Exchange server, but you can block remote PowerShell access for user accounts. For instructions, see [Control remote PowerShell access to Exchange servers](control-remote-powershell-access-to-exchange-servers.md). + +> [!TIP] +> Having problems? Ask for help in the [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612) forums. + +## Open the Exchange Management Shell in Windows Server 2019 Core + +- **Mailbox servers**: Run the following command from a Command Prompt: + + ```dos + LaunchEMS + ``` + +- **Edge Transport servers**: Run the following commands from a Command Prompt. These two separate commands are presented on one line for ease of copying and running: + + ```dos + exshell.psc1 & exchange.ps1 + ``` + +## Open the Exchange Management Shell in Windows Server 2016 or Windows 10 + +Select **Start** \> **Microsoft Exchange Server 2016 \>** **Exchange Management Shell**. + +## Open the Exchange Management Shell in Windows Server 2012 R2 or Windows 8.1 + +When you install Exchange on Windows Server 2012 R2 or the Exchange management tools on Windows 8.1, the Exchange Management Shell shortcut isn't automatically pinned to the Start screen. + +To pin the shortcut to the Start screen, do the following steps: + +1. On the Start screen, open the Apps view by selecting the down arrow near the lower-left corner or swiping up from the middle of the screen. + +2. The **Exchange Management Shell** shortcut is in a group named **Microsoft Exchange Server 2016**. When you find the shortcut, right-click it or press and hold it, and select **Pin to Start**. To pin it to the desktop taskbar, select **Pin to taskbar**. + +To use the Search charm to find and run the Exchange Management Shell, use one of the methods described in the next section. + +## Open the Exchange Management Shell in Windows Server 2012 + +When you install Exchange on Windows Server 2012, the Exchange Management Shell shortcut should automatically be pinned to the Start screen. + +If it's not, or if you just want to quickly find and run the Exchange Management Shell, use one of the following methods: + +- On the Start screen, click in an empty area, and type Exchange Management Shell. When the shortcut appears in the search results, you can select it. + +- On the desktop or the Start screen, press Windows key + Q. In the Search charm, type Exchange Management Shell. When the shortcut appears in the results, you can select it. + +- On the desktop or the Start screen, move your cursor to the upper-right corner, or swipe left from the right edge of the screen to show the charms. Select the Search charm, and type Exchange Management Shell. When the shortcut appears in the results, you can select it. + +If you're using Remote Desktop Connection, you might need to use one of the following methods so the Search charm appears on the remote Exchange server and not on your local computer: + +- Open Remote Desktop Connection and select **Show Options** \> **Local Resources** tab \> **Apply Windows key combinations**. The default value is **Only when using the full screen**, but you can change it to **On the remote computer**. + +- While you're connected to the remote Exchange server, use the connection bar that appears at the top of the screen to open the Exchange server's Search charm or Start screen by clicking the down arrow and selecting **Charms** or **Start**. diff --git a/exchange/docs-conceptual/recipient-filters.md b/exchange/docs-conceptual/recipient-filters.md new file mode 100644 index 0000000000..dc3ea8bf77 --- /dev/null +++ b/exchange/docs-conceptual/recipient-filters.md @@ -0,0 +1,249 @@ +--- +title: "Recipient filters in Exchange PowerShell commands" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 09/07/2023 +ms.audience: ITPro +audience: ITPro +ms.topic: reference +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: fb4b1396-9aae-4037-be1a-b09e336b890e +description: "Learn about creating different kinds of recipient filters in the Exchange Management Shell and Exchange Online PowerShell." +--- + +# Recipient filters in Exchange PowerShell commands + +The cmdlets in the [Exchange Management Shell](exchange-management-shell.md) and [Exchange Online PowerShell](exchange-online-powershell.md)l support different types of filters in recipient related cmdlets: + +- Precanned filters. +- Custom filters using the _RecipientFilter_ parameter. +- Custom filters using the _Filter_ parameter. +- Custom filters using the _ContentFilter_ parameter. + +Older versions of Exchange used LDAP filtering syntax to create custom address lists, global address lists (GALs), email address policies, and distribution groups. OPATH filtering syntax replaced LDAP filtering syntax starting in Exchange Server 2007. + +## Precanned filters + +A _precanned filter_ uses popular properties in Exchange to filter recipients for dynamic distribution groups, email address policies, address lists, or GALs. With precanned filters, you can use either the Exchange PowerShell or the Exchange admin center (EAC). Using precanned filters, you can do the following tasks: + +- Determine the scope of recipients. +- Add conditional filtering based on common properties such as company, department, and state or region. +- Add custom attributes for recipients. For more information, see [Custom Attributes](/Exchange/recipients/mailbox-custom-attributes). + +The following parameters are considered precanned filters: + +- _IncludedRecipients_ +- _ConditionalCompany_ +- _ConditionalDepartment_ +- _ConditionalStateOrProvince_ +- _ConditionalCustomAttribute1_ to _ConditionalCustomAttribute15_. + +Precanned filters are available on the following cmdlets: + +- [New-DynamicDistributionGroup](/powershell/module/exchange/new-dynamicdistributiongroup) +- [Set-DynamicDistributionGroup](/powershell/module/exchange/set-dynamicdistributiongroup) + +- [New-EmailAddressPolicy](/powershell/module/exchange/new-emailaddresspolicy) +- [Set-EmailAddressPolicy](/powershell/module/exchange/set-emailaddresspolicy) + +- [New-AddressList](/powershell/module/exchange/new-addresslist) +- [Set-AddressList](/powershell/module/exchange/set-addresslist) + +- [New-GlobalAddressList](/powershell/module/exchange/new-globaladdresslist) +- [Set-GlobalAddressList](/powershell/module/exchange/set-globaladdresslist) + +### Precanned filter example + +This example describes using precanned filters in the Exchange Management Shell to create a dynamic distribution group. The syntax in this example is similar but not identical to the syntax you would use to create an email address policy, address list, or GAL. When creating a precanned filter, you should ask the following questions: + +- From which organizational unit (OU) do you want to include recipients (the _RecipientContainer_ parameter)? + + > [!NOTE] + > Selecting the OU for this purpose applies only to creating dynamic distribution groups, and not to creating email address policies, address lists, or GALs. + +- What types of recipients do you want to include (the _IncludedRecipients_ parameter)? + +- What additional conditions do you want to include in the filter (the _ConditionalCompany_, _ConditionalDepartment_, _ConditionalStateOrProvince_, and _ConditionalCustomAttribute_ parameters)? + +This example creates a dynamic distribution group with the following properties: + +- **Name**: Contoso Finance. +- **Recipient types**: User mailboxes. +- **Recipient location**: The OU named Contoso.com/Users. +- **Filters** Include only recipients who have the **Department** attribute defined as Finance and the **Company** attribute defined as Contoso. + +```powershell +New-DynamicDistributionGroup -Name "Contoso Finance" -OrganizationalUnit Contoso.com/Users -RecipientContainer Contoso.com/Users -IncludedRecipients MailboxUsers -ConditionalDepartment "Finance" -ConditionalCompany "Contoso" +``` + +This example displays the properties of this new dynamic distribution group. + +```powershell +Get-DynamicDistributionGroup -Identity "Contoso Finance" | Format-List Recipient*,Included* +``` + +## Custom filters using the RecipientFilter parameter + +If precanned filters don't meet your needs, you can create custom filters by using the _RecipientFilter_ parameter. This parameter is available on the following cmdlets: + +- [New-DynamicDistributionGroup](/powershell/module/exchange/new-dynamicdistributiongroup) +- [Set-DynamicDistributionGroup](/powershell/module/exchange/set-dynamicdistributiongroup) + +- [New-EmailAddressPolicy](/powershell/module/exchange/new-emailaddresspolicy) +- [Set-EmailAddressPolicy](/powershell/module/exchange/set-emailaddresspolicy) + +- [New-AddressList](/powershell/module/exchange/new-addresslist) +- [Set-AddressList](/powershell/module/exchange/set-addresslist) + +- [New-GlobalAddressList](/powershell/module/exchange/new-globaladdresslist) +- [Set-GlobalAddressList](/powershell/module/exchange/set-globaladdresslist) + +For more information about the filterable properties you can use with the _RecipientFilter_ parameter, see [Filterable properties for the RecipientFilter parameter](recipientfilter-properties.md). + +### Custom filter example + +The following example uses the _RecipientFilter_ parameter to create a dynamic distribution group. The syntax in this example is similar but not identical to the syntax you use to create an email address policy, address list, or GAL. + +This example uses custom filters to create a dynamic distribution group with the following properties: + +- **Name**: AllContosoNorth. +- **Recipient types**: User mailboxes. +- **Recipient location**: The OU named Contoso.com/Users. +- **Filters** Include only recipients who have the **Company** attribute defined as Contoso and the **Office** attribute defined as North Building. + +```powershell +New-DynamicDistributionGroup -Name AllContosoNorth -OrganizationalUnit contoso.com/Users -RecipientFilter "((RecipientTypeDetails -eq 'UserMailbox') -and (Company -eq 'Contoso') -and (Office -eq 'North Building'))" +``` + +## Custom filters using the Filter parameter + +You can use the _Filter_ parameter to filter the results of a command to specify which objects to retrieve. For example, instead of retrieving all users or groups, you can specify a set of users or groups using a filter string. This type of filter doesn't modify any configuration or attributes of objects. It only modifies the set of objects that the command returns. + +Using the _Filter_ parameter to modify command results is known as _server-side filtering_. Server-side filtering submits the command and the filter to the server for processing. We also support client-side filtering, in which the command retrieves all objects from the server and then applies the filter in the local console window. To perform client-side filtering, use the **Where-Object** cmdlet. For more information about server-side and client-side filtering, see "How to Filter Data" in [Working with Command Output](/exchange/working-with-command-output-exchange-2013-help). + +To find the filterable properties for cmdlets that have the _Filter_ parameter, you can run the **Get** command against an object and format the output by pipelining the **Format-List** parameter. Most of the returned values are available for use in the _Filter_ parameter. + +The following example returns a detailed list for the mailbox Ayla. + +```powershell +Get-Mailbox -Identity Ayla | Format-List +``` + +The _Filter_ parameter is available for the following recipient cmdlets: + +- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox) +- [Get-Contact](/powershell/module/exchange/get-contact) +- [Get-DistributionGroup](/powershell/module/exchange/get-distributiongroup) +- [Get-DynamicDistributionGroup](/powershell/module/exchange/get-dynamicdistributiongroup) +- [Get-Group](/powershell/module/exchange/get-group) +- [Get-Mailbox](/powershell/module/exchange/get-mailbox) +- [Get-MailContact](/powershell/module/exchange/get-mailcontact) +- [Get-MailPublicFolder](/powershell/module/exchange/get-mailpublicfolder) +- [Get-MailUser](/powershell/module/exchange/get-mailuser) +- [Get-Recipient](/powershell/module/exchange/get-recipient) +- [Get-RemoteMailbox](/powershell/module/exchange/get-remotemailbox) +- [Get-SecurityPrincipal](/powershell/module/exchange/get-securityprincipal) +- [Get-UMMailbox](/powershell/module/exchange/get-ummailbox) +- [Get-User](/powershell/module/exchange/get-user) +- [Get-UnifiedGroup](/powershell/module/exchange/get-unifiedgroup) + +For more information about the filterable properties you can use with the _Filter_ parameter, see [Filterable properties for the Filter parameter](filter-properties.md). + +### Filter parameter example + +This example uses the _Filter_ parameter to return information about users whose title contains the word "manager." + +```powershell +Get-User -Filter "Title -like 'Manager*'" +``` + +## Custom filters using the ContentFilter parameter + +You can use the _ContentFilter_ parameter to select specific message content to export when using the [New-MailboxExportRequest](/powershell/module/exchange/new-mailboxexportrequest) cmdlet. If the command finds a message that contains the match to the content filter, it exports the message to a .pst file. + +### ContentFilter parameter example + +This example creates an export request that searches Ayla's mailbox for messages where the body contains the phrase "company prospectus." If that phrase is found, the command exports all messages with that phrase to a .pst file. + +```powershell +New-MailboxExportRequest -Mailbox Ayla -ContentFilter "Body -like 'company prospectus*'" +``` + +For more information about the filterable properties that you can use with the _ContentFilter_ parameter, see [Filterable properties for the ContentFilter parameter](/exchange/filterable-properties-for-the-contentfilter-parameter). + +## Additional OPATH syntax information + +When creating your own custom OPATH filters, consider the following items: + +- Use the following syntax to identify the types of values that you're searching for: + + - **Text values**: Enclose the text in single quotation marks (for example, `'Value'` or `'Value with spaces'`). Or, you can enclose a text value in double quotation marks, but that limits the characters you can use to enclose the whole OPATH filter. + + - **Variables**: Enclose variables that need to be expanded in single quotation marks (for example, `'$User'`). If the variable value itself contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. + + - **Integer values**: You don't need to enclose integers (for example, `500`). You can often enclose integers in single quotation marks or double quotation marks, but that limits the characters you can use to enclose the whole OPATH filter. + + - **System values**: Don't enclose system values (for example, `$true`, `$false`, or `$null`). To enclose the whole OPATH filter in double quotation marks, you need to escape the dollar sign in system value (for example, `` `$true``). + +- You need to enclose the whole OPATH filter in double quotation marks " " or single quotation marks ' '. Although any OPATH filter object is technically a string and not a script block, you can still use braces { }, but only if the filter doesn't contain variables that require expansion. The characters that you can use to enclose the whole OPATH filter depend on types of values that you're searching for and the characters you used (or didn't use) to enclose those values: + + - **Text values**: Depends on how you enclosed the text to search for: + - **Text enclosed in single quotation marks**: Enclose the whole OPATH filter in double quotation marks or braces. + - **Text enclosed in double quotation marks**: Enclose the whole OPATH filter in braces. + + - **Variables**: Enclose the whole OPATH filter in double quotation marks (for example, `"Name -eq '$User'"`). + + - **Integer values**: To ensure they work in all cases, enclose them in one of the following ways: + - **Integer enclosed in single quotation marks**: Enclose the whole OPATH filter in double quotation marks or braces `"CountryCode -eq '840'"`. + - **Integer enclosed in double quotation marks**: Enclose the whole OPATH filter in braces (for example `{CountryCode -eq "840"}`). + + - **System values**: Enclose the whole OPATH filter in single quotation marks or braces (for example `'HiddenFromAddressListsEnabled -eq $true'`). If you escape the dollar sign system value, you can also enclose the whole OPATH filter in double quotation marks (for example, ``"HiddenFromAddressListsEnabled -eq `$true"``). + + The compatibility of search criteria and the valid characters that you can use to enclose the whole OPATH filter are summarized in the following table: + + |Search value|OPATH filter
enclosed in
double quotation marks|OPATH filter
enclosed in
single quotation marks|OPATH filter enclosed in
braces| + |---|:---:|:---:|:---:| + |`'Text'`|✔||✔| + |`"Text"`|||✔| + |`'$Variable'`|✔||| + |`500`|✔|✔|✔| + |`'500'`|✔||✔| + |`"500"`|||✔| + |`$true`||✔|✔| + |`` `$true``|✔|✔|✔| + +- Include the hyphen before all logical or comparison operators. The most common operators include: + + - `-and` + - `-or` + - `-not` + - `-eq` (equals) + - `-ne` (not equal) + - `-lt` (less than) + - `-gt` (greater than) + - `-like` (string comparison) + - `-notlike` (string comparison) + +- Many filterable properties accept wildcard characters. If you use a wildcard character, use the **-like** operator instead of the **-eq** operator. Use the **-like** operator to find pattern matches in rich types (for example, strings). Use the **-eq** operator to find an exact match. + + When you use the **-like** operator in Exchange Online PowerShell, the wildcard character is supported only as a suffix in **most** parameters. For example, `"Department -like 'sales*'"` is allowed, but `"Department -like '*sales'"` isn't allowed. + + > [!TIP] + > Even if a wildcard prefix works in a filter parameter in Exchange Online PowerShell, we don't recommend using it due to low performance issues. + +- For more information about operators that you can use, see: + + - [about_Logical_Operators](/powershell/module/microsoft.powershell.core/about/about_logical_operators) + - [about_Comparison_Operators](/powershell/module/microsoft.powershell.core/about/about_comparison_operators) + +## Recipient filter documentation + +The following table contains links to articles to help you learn more about the filterable properties that you can use with Exchange recipient commands. + +|Article|Description| +|---|---| +|[Filterable properties for the RecipientFilter parameter on Exchange cmdlets](recipientfilter-properties.md)|Learn more about the filterable properties that are available for the _RecipientFilter_ parameter.| +|[Filterable properties for the Filter parameter on Exchange cmdlets](filter-properties.md) |Learn more about the filterable properties that are available for the _Filter_ parameter.| +|[Filters in the Exchange Online PowerShell module](filters-v2.md)|Learn about the considerations for filters in the nine exclusive **Get-EXO\*** cmdlets in the Exchange Online PowerShell module.| diff --git a/exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md b/exchange/docs-conceptual/recipientfilter-properties.md similarity index 76% rename from exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md rename to exchange/docs-conceptual/recipientfilter-properties.md index 3dc5a88824..0c75acd5b6 100644 --- a/exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md +++ b/exchange/docs-conceptual/recipientfilter-properties.md @@ -2,27 +2,25 @@ title: "Filterable properties for the RecipientFilter parameter" ms.author: chrisda author: chrisda -manager: dansimp -ms.date: +manager: deniseb +ms.date: 09/07/2023 ms.audience: ITPro +audience: ITPro ms.topic: article -ms.prod: exchange-server-itpro -localization_priority: Normal +ms.service: exchange-powershell +ms.localizationpriority: medium ms.assetid: cf78aca5-6699-485c-9b15-e0adba252176 description: "Learn about the recipient properties that you can use with the RecipientFilter parameter in Exchange Server and Exchange Online cmdlets." --- -# Filterable properties for the RecipientFilter parameter +# Filterable properties for the RecipientFilter parameter on Exchange cmdlets You use the _RecipientFilter_ parameter to create OPATH filters based on the properties of recipient objects in Exchange Server 2016 or later, and Exchange Online. The _RecipientFilter_ parameter is available in the following cmdlets: -- [New-AddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/new-addresslist.md) and [Set-AddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/set-addresslist.md) - -- [New-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/new-dynamicdistributiongroup.md) and [Set-DynamicDistributionGroup](../../../exchange-ps/exchange/users-and-groups/set-dynamicdistributiongroup.md) - -- [New-EmailAddressPolicy](../../../exchange-ps/exchange/email-addresses-and-address-books/new-emailaddresspolicy.md) and [Set-EmailAddressPolicy](../../../exchange-ps/exchange/email-addresses-and-address-books/set-emailaddresspolicy.md) - -- [New-GlobalAddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/new-globaladdresslist.md) and [Set-GlobalAddressList](../../../exchange-ps/exchange/email-addresses-and-address-books/set-globaladdresslist.md) +- [New-AddressList](/powershell/module/exchange/new-addresslist) and [Set-AddressList](/powershell/module/exchange/set-addresslist) +- [New-DynamicDistributionGroup](/powershell/module/exchange/new-dynamicdistributiongroup) and [Set-DynamicDistributionGroup](/powershell/module/exchange/set-dynamicdistributiongroup) +- [New-EmailAddressPolicy](/powershell/module/exchange/new-emailaddresspolicy) and [Set-EmailAddressPolicy](/powershell/module/exchange/set-emailaddresspolicy) +- [New-GlobalAddressList](/powershell/module/exchange/new-globaladdresslist) and [Set-GlobalAddressList](/powershell/module/exchange/set-globaladdresslist) ## Filterable recipient properties @@ -31,31 +29,34 @@ The recipient properties that have been *confirmed* to work with the _RecipientF **Notes**: - The list might include: - - - Properties that are only used in one type of environment: Microsoft Office 365, on-premises Exchange, or hybrid. The property might exist on recipient objects in all environments, but the value is only meaningful (a value other than blank or `None`) in one type of environment. - + - Properties that are only used in one type of environment: Microsoft 365, on-premises Exchange, or hybrid. The property might exist on recipient objects in all environments, but the value is only meaningful (a value other than blank or `None`) in one type of environment. - Properties that are present, but correspond to features that are no longer used in Exchange. - You can't use properties from other Active Directory schema extensions with the _RecipientFilter_ parameter. - Not all recipient properties have a corresponding Active Directory property. The LDAP display name value in the table is "n/a" for these properties, which indicates that the property is calculated (likely by Exchange). -- 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. For more information, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information). +- 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. For more information, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information). - You typically use the object's name for properties that require a valid object value (for example, a mailbox, a distribution group, or an email address policy, but the property might also accept the object's distinguished name (DN) or globally unique identifier (GUID). To find the object's DN or GUID, use the **Get-** cmdlet that corresponds to the object's type (for example, `Get-EmailAddressPolicy | Format-List Name,DistinguishedName,GUID`). -- Text string properties that accept wildcard characters require the `-like` operator (for example, `"Property -like '*abc'"`). +- Text string properties that accept wildcard characters require the `-like` operator (for example, `"Property -like 'abc*'"`). In Exchange Online PowerShell, you can't use the wildcard as a prefix in **most** parameters (for example, `"Property -like '*abc'"`) isn't allowed). + + > [!TIP] + > Even if a wildcard prefix works in a filter parameter in Exchange Online PowerShell, we don't recommend using it due to low performance issues. -- The Value column in the table describes the acceptable values for the *filter*, not necessarily for the property itself. For example, a property might obviously contain a date or numeric value, but when you use that property in a filter, it might be treated like a text string (no value check, and wildcards are supported). +- The Value column in the table describes the acceptable values for the _filter_, not necessarily for the property itself. For example, a property might obviously contain a date or numeric value, but when you use that property in a filter, it might be treated like a text string (no value check, and wildcards are supported). - To look for blank or non-blank property values, use the value `$null` (for example, `'Property -eq $null'` or `'Property -ne $null'`). -**** +- For filtering considerations for the nine exclusive **Get-EXO\*** cmdlets in the Exchange Online PowerShell module, see [Filters in the Exchange Online PowerShell module](filters-v2.md). -|**Property name**|**LDAP display name**|**Value**|**Comments**| -|:-----|:-----|:-----|:-----| -|_AcceptMessagesOnlyFrom_|_authOrig_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| -|_AcceptMessagesOnlyFromDLMembers_|_dLMemSubmitPerms_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| +- In Exchange Online, you can't use a wildcard character (*) as the first character in the search string. + +|Property name|LDAP display name|Value|Comments| +|---|---|---|---| +|_AcceptMessagesOnlyFrom_|_authOrig_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| +|_AcceptMessagesOnlyFromDLMembers_|_dLMemSubmitPerms_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| |_ActiveSyncAllowedDeviceIDs_|_msExchMobileAllowedDeviceIds_|String (wildcards accepted).|| |_ActiveSyncBlockedDeviceIDs_|_msExchMobileBlockedDeviceIds_|String (wildcards accepted).|| |_ActiveSyncEnabled_|n/a|Boolean (`$true` or `$false`)|| @@ -73,17 +74,17 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_ArchiveDomain_|_msExchArchiveAddress_|String (wildcards accepted).|| |_ArchiveGuid_|_msExchArchiveGUID_|String (wildcards accepted).|| |_ArchiveName_|_msExchArchiveName_|String (wildcards accepted).|| -|_ArchiveQuota_|_msExchArchiveQuota_|Dynamic distribution groups: A byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| -|_ArchiveWarningQuota_|_msExchArchiveWarnQuota_|Dynamic distribution groups: A byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_ArchiveQuota_|_msExchArchiveQuota_|Dynamic distribution groups: A byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_ArchiveWarningQuota_|_msExchArchiveWarnQuota_|Dynamic distribution groups: A byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| |_ArchiveRelease_|_msExchArchiveRelease_|String (wildcards accepted).|| |_ArchiveState_|n/a|`None` (0), `Local` (1), `HostedProvisioned` (2), `HostedPending` (3), or `OnPremise` (4).|| |_ArchiveStatus_|_msExchArchiveStatus_|`None` (0) or `Active` (1).|| |_AssistantName_|_msExchAssistantName_|String (wildcards accepted).|The name of the recipient's assistant.| |_AuditEnabled_|_msExchMailboxAuditEnable_|Boolean (`$true` or `$false`)|| -|_AuditLogAgeLimit_|_msExchMailboxAuditLogAgeLimit_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|The value of this property is a time span: `dd.hh:mm:ss` where `dd` = days, `hh` = hours, `mm` = minutes, and `ss` = seconds.| +|_AuditLogAgeLimit_|_msExchMailboxAuditLogAgeLimit_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|The value of this property is a time span: `dd.hh:mm:ss` where `dd` = days, `hh` = hours, `mm` = minutes, and `ss` = seconds.| |_AuthenticationPolicy_|_msExchAuthPolicyLink_|String (wildcards accepted in dynamic distribution groups).|| -|_C_|_C_|String (wildcards accepted).|This property contains the two-letter country/region designation from International Organization for Standardization (ISO) 3166. For more information, see [Country Codes - ISO 3166](https://go.microsoft.com/fwlink/p/?linkid=213779).| -|_CalendarLoggingQuota_|_msExchCalendarLoggingQuota_|Dynamic distribution groups: `Unlimited` or a byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: `Unlimited`, or blank/non-blank.|| +|_C_|_C_|String (wildcards accepted).|This property contains the two-letter country/region designation from International Organization for Standardization (ISO) 3166. For more information, see [Country Codes - ISO 3166](https://www.iso.org/iso-3166-country-codes.html).| +|_CalendarLoggingQuota_|_msExchCalendarLoggingQuota_|Dynamic distribution groups: `Unlimited` or a byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: `Unlimited`, or blank/non-blank.|| |_CalendarRepairDisabled_|_msExchCalendarRepairDisabled_|Boolean (`$true` or `$false`)|| |_Certificate_|_userCertificate_|`System.Byte[]`|This property contains the DER-encoded X509v3 certificates that are issued to the user.| |_CertificateSubject_|n/a|`X509:X500IssuerX500Subject` (for example, `X509:C=US,O=InternetCA,CN=APublicCertificateAuthorityC=US,O=Fabrikam,OU=Sales,CN=Jeff Smith`)|The X509 certificate that's published for the user account (visible on the **Published Certificates** tab in Active Directory Users and Computers).| @@ -92,7 +93,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_CommonName_|_cn_|String (wildcards accepted).|| |_ComplianceTagHoldApplied_|n/a|Boolean (`$true` or `$false`)|| |_Company_|_company_|String (wildcards accepted).|The recipient's company name.| -|_CountryOrRegion_|c|String (wildcards accepted).|This property contains the two-letter country/region designation from ISO 3166. For more information, see [Country Codes - ISO 3166](https://go.microsoft.com/fwlink/p/?linkid=213779).| +|_CountryOrRegion_|c|String (wildcards accepted).|This property contains the two-letter country/region designation from ISO 3166. For more information, see [Country Codes - ISO 3166](https://www.iso.org/iso-3166-country-codes.html).| |_CustomAttribute1_ to _CustomAttribute15_|_extensionAttribute1_ to _extensionAttribute15_|String (wildcards accepted).|These properties contain custom attributes that you can add to a recipient.| |_Database_|_homeMDB_|String (wildcards accepted).|The identity of the user's mailbox database.| |_Department_|_department_|String (wildcards accepted).|The recipient's department.| @@ -107,19 +108,19 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_DisplayName_|_displayName_|String (wildcards accepted).|| |_DistinguishedName_|_distinguishedName_|String (wildcards accepted).|| |_EcpEnabled_|n/a|Boolean (`$true` or `$false`)|| -|_ElcExpirationSuspensionEndDate_|_msExchELCExpirySuspensionEnd_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|This property contains a date-time value.| -|_ElcExpirationSuspensionStartDate_|_msExchELCExpirySuspensionStart_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|This property contains a date-time value.| +|_ElcExpirationSuspensionEndDate_|_msExchELCExpirySuspensionEnd_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|This property contains a date-time value.| +|_ElcExpirationSuspensionStartDate_|_msExchELCExpirySuspensionStart_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|This property contains a date-time value.| |_ElcMailboxFlags_|_msExchELCMailboxFlags_|`None` (0), `ExpirationSuspended` (1), `ElcV2` (2), `DisableCalendarLogging` (4),`LitigationHold` (8), `SingleItemRecovery` (16), `ValidArchiveDatabase` (32), `ShouldUseDefaultRetentionPolicy` (128), `EnableSiteMailboxMessageDedup` (256), `ElcProcessingDisabled` (512), or `ComplianceTagHold` (1024).|| -|_EmailAddresses_|_proxyAddresses_|String (wildcards accepted).|This property contains the recipient's email addresses (the primary email address and all proxy addresses).| +|_EmailAddresses_|_proxyAddresses_|String (wildcards accepted).|This property contains the recipient's email addresses (the primary email address and all proxy addresses). This is the property used to identify inactive mailboxes.| |_EmailAddressPolicyEnabled_|n/a|Boolean (`$true` or `$false`)|| |_EntryId_|_msExchPublicFolderEntryId_|String (wildcards accepted).|| |_EwsApplicationAccessPolicy_|_msExchEwsApplicationAccessPolicy_|`EnforceAllowList` or `EnforceBlockList`.|| |_EwsEnabled_|_msExchEwsEnabled_|Integer|| |_ExchangeGuid_|_msExchMailboxGuid_|String (wildcards accepted).|| -|_ExchangeUserAccountControl_|_msExchUserAccountControl_|For valid values, see [ADS_USER_FLAG_ENUM enumeration](https://go.microsoft.com/fwlink/p/?linkid=190424). The integer values will work as described. Most of the text values won't work as described (even if you remove `ADS_UF` and all underscores).|| -|_ExchangeVersion_|_msExchVersion_|Dynamic distribution groups: String (wildcards accepted).
Others: `ExchangeObjectVersion` values.|| +|_ExchangeUserAccountControl_|_msExchUserAccountControl_|For valid values, see [ADS_USER_FLAG_ENUM enumeration](/windows/win32/api/iads/ne-iads-ads_user_flag_enum). The integer values will work as described. Most of the text values won't work as described (even if you remove `ADS_UF` and all underscores).|| +|_ExchangeVersion_|_msExchVersion_|Dynamic distribution groups: String (wildcards accepted).
Others: `ExchangeObjectVersion` values.|| |_ExpansionServer_|_msExchExpansionServerName_|String (wildcards accepted).|| -|_ExtensionCustomAttribute1_ to _ExtensionCustomAttribute5_|_msExchExtensionCustomAttribute1_ to _msExchExtensionCustomAttribute5_|String (wildcards accepted).|| +|_ExtensionCustomAttribute1_ to _ExtensionCustomAttribute5_|_msExchExtensionCustomAttribute1_ to _msExchExtensionCustomAttribute5_|String (wildcards accepted).|Currently, these attributes aren't useable as filters in Exchange Online. For more information, see [Microsoft Entra Connect Sync: Attributes synchronized to Microsoft Entra ID](/entra/identity/hybrid/connect/reference-connect-sync-attributes-synchronized).| |_ExternalDirectoryObjectId_|_msExchExternalDirectoryObjectId_|String (wildcards accepted).|| |_ExternalEmailAddress_|_targetAddress_|String (wildcards accepted).|This property contains the external email address for mail contacts and mail users.| |_ExternalOofOptions_|_msExchExternalOOFOptions_|`External` (0) or `InternalOnly` (1).|| @@ -144,7 +145,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_Initials_|_initials_|String (wildcards accepted).|| |_InPlaceHolds_|_msExchUserHoldPolicies_|String|| |_InPlaceHoldsRaw_|n/a|String|| -|_InternetEncoding_|_internetEncoding_|Integer|For valid values, see the Remarks section in the topic, [Encoding Class](https://go.microsoft.com/fwlink/p/?linkid=184080).| +|_InternetEncoding_|_internetEncoding_|Integer|For valid values, see the Remarks section in the article, [Encoding Class](/dotnet/api/system.text.encoding).| |_IsDirSynced_|_msExchIsMSODirsynced_|Boolean (`$true` or `$false`)|| |_IsExcludedFromServingHierarchy_|n/a|Boolean (`$true` or `$false`)|| |_IsHierarchyReady_|n/a|Boolean (`$true` or `$false`)|| @@ -154,24 +155,24 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_IsSecurityPrincipal_|n/a|Boolean (`$true` or `$false`)|| |_IsSoftDeletedByDisable_|n/a|Boolean (`$true` or `$false`)|| |_IsSoftDeletedByRemove_|n/a|Boolean (`$true` or `$false`)|| -|_IssueWarningQuota_|_mDBStorageQuota_|Dynamic distribution groups: A byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_IssueWarningQuota_|_mDBStorageQuota_|Dynamic distribution groups: A byte quantified size value (for example, `300MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| |_JournalArchiveAddress_|n/a|An SMTP email address (for example, `julia@contoso.com`).|| -|_LanguagesRaw_|_msExchUserCulture_|String (wildcards accepted).|This property contains the language preference for this mailbox in the format `-`. For example, United States English is `en-US`. For more information, see [CultureInfo Class](https://go.microsoft.com/fwlink/p/?LinkID=255174).| -|_LastExchangeChangedTime_|_msExchLastExchangeChangedTime_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| +|_LanguagesRaw_|_msExchUserCulture_|String (wildcards accepted).|This property contains the language preference for this mailbox in the format `-`. For example, United States English is `en-US`. For more information, see [CultureInfo Class](/dotnet/api/system.globalization.cultureinfo).| +|_LastExchangeChangedTime_|_msExchLastExchangeChangedTime_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| |_LastName_|_sn_|String (wildcards accepted).|| |_LdapRecipientFilter_|_msExchDynamicDLFilter_|String (wildcards accepted).|| |_LegacyExchangeDN_|_legacyExchangeDN_|String (wildcards accepted).|| -|_LitigationHoldDate_|_msExchLitigationHoldDate_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| +|_LitigationHoldDate_|_msExchLitigationHoldDate_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| |_LitigationHoldEnabled_|n/a|Boolean (`$true` or `$false`)|| |_LitigationHoldOwner_|_msExchLitigationHoldOwner_|String (wildcards accepted).|| -|_LocaleID_|_localeID_|Integer|For valid values, [Microsoft Locale ID Values](https://go.microsoft.com/fwlink/p/?linkid=229656).| +|_LocaleID_|_localeID_|Integer|For valid values, [Microsoft Locale ID Values](/openspecs/office_standards/ms-oe376/6c085406-a698-4e12-9d4d-c3b0ee3dbc4a).| |_MailboxMoveBatchName_|_msExchMailboxMoveBatchName_|String (wildcards accepted).|| -|_MailboxMoveFlags_|_msExchMailboxMoveFlags_|For valid values, see the description of the _Flags_ parameter in[Get-MoveRequest](../../../exchange-ps/exchange/move-and-migration/get-moverequest.md).|| +|_MailboxMoveFlags_|_msExchMailboxMoveFlags_|For valid values, see the description of the _Flags_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest).|| |_MailboxMoveRemoteHostName_|_msExchMailboxMoveRemoteHostName_|String (wildcards accepted).|| |_MailboxMoveSourceMDB_|_msExchMailboxMoveSourceMDBLink_|String (wildcards accepted in dynamic distribution groups).|| -|_MailboxMoveStatus_|_msExchMailboxMoveStatus_|For valid values, see the description of the _MoveStatus_ parameter in[Get-MoveRequest](../../../exchange-ps/exchange/move-and-migration/get-moverequest.md).|| +|_MailboxMoveStatus_|_msExchMailboxMoveStatus_|For valid values, see the description of the _MoveStatus_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest).|| |_MailboxMoveTargetMDB_|_msExchMailboxMoveTargetMDBLink_|String (wildcards accepted in dynamic distribution groups).|| -|_MailboxPlan_|_msExchParentPlanLink_|String (wildcards accepted).|Mailbox plans correspond to Office 365 license types. The availability of a license plans is determined by the selections that you make when you enroll your domain.| +|_MailboxPlan_|_msExchParentPlanLink_|String (wildcards accepted).|Mailbox plans correspond to Microsoft 365 license types. The availability of a license plans is determined by the selections that you make when you enroll your domain.| |_MailboxRelease_|_msExchMailboxRelease_|String (wildcards accepted).|| |_MailTipTranslations_|_msExchSenderHintTranslations_|String (wildcards accepted).|| |_ManagedBy_|_managedBy_|String (wildcards accepted in dynamic distribution groups).|This property identifies the security principal that's the manager of the group.| @@ -180,11 +181,11 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_MapiRecipient_|_mAPIRecipient_|Boolean (`$true` or `$false`)|| |_MaxBlockedSenders_|_msExchMaxBlockedSenders_|`Unlimited` or an integer.|| |_MaxSafeSenders_|_msExchMaxSafeSenders_|`Unlimited` or an integer.|| -|_MaxReceiveSize_|_delivContLength_|Dynamic distribution groups: A byte quantified size value (for example, `50MB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| -|_MaxSendSize_|_submissionContLength_|Dynamic distribution groups: A byte quantified size value (for example, `50MB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_MaxReceiveSize_|_delivContLength_|Dynamic distribution groups: A byte quantified size value (for example, `50MB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_MaxSendSize_|_submissionContLength_|Dynamic distribution groups: A byte quantified size value (for example, `50MB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| |_MemberDepartRestriction_|_msExchGroupDepartRestriction_|`Closed` (0), `Open` (1), or `ApprovalRequired` (2).|| |_MemberJoinRestriction_|_msExchGroupDepartRestriction_|`Closed` (0), `Open` (1), or `ApprovalRequired` (2).|| -|_MemberOfGroup_|_memberOf_|String (wildcards accepted in dynamic distribution groups).|| +|_MemberOfGroup_|_memberOf_|String (wildcards accepted in dynamic distribution groups).|You must use the DistinguishedName. This property only works with groups recognized by Exchange, therefore Microsoft Entra security groups do not work.| |_Members_|_member_|String (wildcards accepted in dynamic distribution groups).|| |_MessageHygieneFlags_|_msExchMessageHygieneFlags_|`None` (0) or `AntispamBypass` (1).|| |_MobileAdminExtendedSettings_|_msExchOmaAdminExtendedSettings_|String (wildcards accepted).|| @@ -194,10 +195,10 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_ModeratedBy_|_msExchModeratedByLink_|String (wildcards accepted in dynamic distribution groups).|| |_ModerationEnabled_|_msExchEnableModeration_|Boolean (`$true` or `$false`)|| |_Name_|_name_|String (wildcards accepted).|The unique name value of the recipient.| -|_NetID_|n/a|A sample value is `1003BFFD9A0CFA03`.|This property is populated for Office 365 mailboxes in hybrid environments.| +|_NetID_|n/a|A sample value is `1003BFFD9A0CFA03`.|This property is populated for Exchange Online mailboxes in hybrid environments.| |_Notes_|_info_|String (wildcards accepted).|| -|_ObjectCategory_|_objectCategory_|Dynamic distribution groups: String (wildcards accepted).
Others: Valid Active Directory `ObjectCategory` values.|Valid values use the format `CN=,CN=Schema,CN=Configuration,DC=`, where _\_ is typically `Person` or `Group` for recipients. For example, `CN=Person,CN=Schema,CN=Configuration,DC=contoso,DC=com`.| -|_ObjectClass_|_objectClass_|Dynamic distribution groups: String (wildcards accepted).
Others: Valid Active Directory `ObjectCategory` values.|Common values for recipients are: `contact`, `organizationalPerson`, `person`, `top`, `group`, `msExchDynamicDistributionList`, and `user`.| +|_ObjectCategory_|_objectCategory_|Dynamic distribution groups: String (wildcards accepted).
Others: Valid Active Directory `ObjectCategory` values.|Valid values use the format `CN=,CN=Schema,CN=Configuration,DC=`, where _\_ is typically `Person` or `Group` for recipients. For example, `CN=Person,CN=Schema,CN=Configuration,DC=contoso,DC=com`.| +|_ObjectClass_|_objectClass_|Dynamic distribution groups: String (wildcards accepted).
Others: Valid Active Directory `ObjectCategory` values.|Common values for recipients are: `contact`, `organizationalPerson`, `person`, `top`, `group`, `msExchDynamicDistributionList`, and `user`.| |_Office_|_physicalDeliveryOfficeName_|String (wildcards accepted).|| |_OfflineAddressBook_|_msExchUseOAB_|String (wildcards accepted in dynamic distribution groups).|This property contains the offline address book (OAB) that's associated with this recipient.| |_OperatorNumber_|_msExchUMOperatorNumber_|String (wildcards accepted).|| @@ -220,28 +221,28 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_PopEnabled_|n/a|Boolean (`$true` or `$false`)|| |_PostalCode_|_postalCode_|String (wildcards accepted).|| |_PostOfficeBox_|_postOfficeBox_|String (wildcards accepted).|| -|_PreviousRecipientTypeDetails_|_msExchPreviousRecipientTypeDetails_|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](../../../exchange-ps/exchange/users-and-groups/get-recipient.md).|| +|_PreviousRecipientTypeDetails_|_msExchPreviousRecipientTypeDetails_|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient).|| |_PrimaryGroupId_|_primaryGroupId_|Integer|For domain users, the value of this property is typically 513, which corresponds to the Domain Users group.| -|_PrimarySmtpAddress_|n/a|String (wildcards accepted).|| -|_ProhibitSendQuota_|_mDBOverQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| -|_ProhibitSendReceiveQuota_|_mDBOverHardQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_PrimarySmtpAddress_|n/a|String (wildcards accepted).|Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property will also search values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.| +|_ProhibitSendQuota_|_mDBOverQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_ProhibitSendReceiveQuota_|_mDBOverHardQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| |_ProtocolSettings_|_protocolSettings_|String (wildcards accepted).|| |_PublicFolderContacts_|_pFContacts_|String (wildcards accepted in dynamic distribution groups).|| |_PurportedSearchUI_|_msExchPurportedSearchUI_|String (wildcards accepted).|| |_QueryBaseDN_|_msExchQueryBaseDN_|String (wildcards accepted in dynamic distribution groups).|| -|_RawCanonicalName_|_canonicalName_|String (wildcards accepted).|| +|_RawCanonicalName_|_canonicalName_|String (wildcards accepted).|This property is based on a constructed Active Directory attribute, and does not correctly resolve all members when used in `Get-Recipient -RecipientPreviewFilter`.| |_RawExternalEmailAddress_|_targetAddress_|String (wildcards accepted).|| |_RawName_|_name_|String (wildcards accepted).|| |_RecipientContainer_|_msExchDynamicDLBaseDN_|String (wildcards accepted).|The Active Directory container or organizational unit (OU) that holds the recipient object.| |_RecipientDisplayType_|_msExchRecipientDisplayType_|`MailboxUser` (0), `DistributionGroup` (1), `PublicFolder` (2), `DynamicDistributionGroup` (3), `Organization` (4), `PrivateDistributionList` (5), `RemoteMailUser` (6). `ConferenceRoomMailbox` (7), or `EquipmentMailbox` (8).|| |_RecipientFilter_|_msExchQueryFilter_|String (wildcards accepted).|| |_RecipientLimits_|_msExchRecipLimit_|`Unlimited` or an integer.|This property specifies the maximum number of recipients that are allowed in messages sent by the mailbox.| -|_RecipientType_|n/a|For valid values, see the description of the _RecipientType_ parameter in [Get-Recipient](../../../exchange-ps/exchange/users-and-groups/get-recipient.md).|| -|_RecipientTypeDetails_|n/a|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](../../../exchange-ps/exchange/users-and-groups/get-recipient.md).|| -|_RecoverableItemsQuota_|_msExchDumpsterQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| -|_RecoverableItemsWarningQuota_|_msExchDumpsterWarningQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| -|_RejectMessagesFrom_|_unauthOrig_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| -|_RejectMessagesFromDLMembers_|_dLMemRejectPerms_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| +|_RecipientType_|n/a|For valid values, see the description of the _RecipientType_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient).|| +|_RecipientTypeDetails_|n/a|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient).|| +|_RecoverableItemsQuota_|_msExchDumpsterQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_RecoverableItemsWarningQuota_|_msExchDumpsterWarningQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_RejectMessagesFrom_|_unauthOrig_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| +|_RejectMessagesFromDLMembers_|_dLMemRejectPerms_|Dynamic distribution groups: String (wildcards accepted).
Others: Blank or non-blank.|| |_RemoteAccountPolicy_|_msExchSyncAccountsPolicyDN_|String (wildcards accepted in dynamic distribution groups).|| |_RemotePowerShellEnabled_|n/a|Boolean (`$true` or `$false`)|| |_RemoteRecipientType_|_msExchRemoteRecipientType_|`None` (0), `ProvisionMailbox` (1), `ProvisionArchive` (2), `Migrated` (4), `DeprovisionMailbox` (8), `DeprovisionArchive` (16), `RoomMailbox` (32), `EquipmentMailbox` (64), `SharedMailbox` (96), or `TeamMailbox` (128).|| @@ -254,12 +255,12 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_ResourcePropertiesDisplay_|_msExchResourceDisplay_|String (wildcards accepted).|| |_ResourceSearchProperties_|_msExchResourceSearchProperties_|String (wildcards accepted).|| |_ResourceType_|n/a|`Room` (0) or `Equipment` (1).|| -|_RetainDeletedItemsFor_|_garbageCollPeriod_|Dynamic distribution groups: A time span: `dd.hh:mm:ss` where `dd` = days, `hh` = hours, `mm` = minutes, and `ss` = seconds.
Others: Blank or non-blank.|| +|_RetainDeletedItemsFor_|_garbageCollPeriod_|Dynamic distribution groups: A time span: `dd.hh:mm:ss` where `dd` = days, `hh` = hours, `mm` = minutes, and `ss` = seconds.
Others: Blank or non-blank.|| |_RetentionComment_|_msExchRetentionComment_|String (wildcards accepted).|| |_RetentionPolicy_|n/a|String|| |_RetentionUrl_|_msExchRetentionURL_|String (wildcards accepted).|| |_RoleAssignmentPolicy_|_msExchRBACPolicyLink_|String (wildcards accepted in dynamic distribution groups).|| -|_RulesQuota_|_msExchMDBRulesQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| +|_RulesQuota_|_msExchMDBRulesQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
Others: Blank or non-blank.|| |_SamAccountName_|_SamAccountName_|String (wildcards accepted in dynamic distribution groups).|This property specifies an identifier that's compatible with older versions of Microsoft Windows client and server operating systems (also known as the pre-Windows 2000 user account or group name)| |_SafeRecipientsHash_|_msExchSafeRecipientsHash_|`System.Byte[]`|A user's safe recipients list is hashed (SHA-256) one way before it's stored as a binary large object in Active Directory.| |_SafeSendersHash_|_msExchSafeSendersHash_|`System.Byte[]`|A user's safe senders list is hashed (SHA-256) one way before it's stored as a binary large object in Active Directory.| @@ -279,7 +280,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_SMimeCertificate_|_userSMIMECertificate_|`System.Byte[]`|This property contains the binary encoded S/MIME certificates that are issued to the user.| |_StateOrProvince_|_st_|String (wildcards accepted).|| |_StreetAddress_|_streetAddress_|String (wildcards accepted).|| -|_StsRefreshTokensValidFrom_|_msExchStsRefreshTokensValidFrom_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| +|_StsRefreshTokensValidFrom_|_msExchStsRefreshTokensValidFrom_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| |_TelephoneAssistant_|_telephoneAssistant_|String (wildcards accepted).|| |_TextEncodedORAddress_|_textEncodedORAddress_|String (wildcards accepted).|| |_ThrottlingPolicy_|_msExchThrottlingPolicyDN_|String (wildcards accepted in dynamic distribution groups).|| @@ -295,23 +296,21 @@ The recipient properties that have been *confirmed* to work with the _RecipientF |_UMServerWritableFlags_|_msExchUMServerWritableFlags_|`None` (0), `MissedCallNotificationEnabled` (1), `SMSVoiceMailNotificationEnabled` (2), `SMSMissedCallNotificationEnabled` (4), or `PinlessAccessToVoiceMailEnabled` (8).|| |_UMSpokenName_|_msExchUMSpokenName_|`System.Byte[]`|| |_UnicodePassword_|_unicodePwd_|`System.Byte[]`|| -|_UsageLocation_|_msExchUsageLocation_|A valid two-letter country/region ISO 3166 value, or the corresponding display name (for example, `US` or `UnitedStates`). For more information, see [Country Codes - ISO 3166](https://go.microsoft.com/fwlink/p/?linkid=213779).|| +|_UsageLocation_|_msExchUsageLocation_|A valid ISO 3166-1 two-letter country code value or the corresponding display name (for example, `US` or `UnitedStates`). For more information, see [Country Codes - ISO 3166](https://www.iso.org/iso-3166-country-codes.html).|| |_UseDatabaseQuotaDefaults_|_mDBUseDefaults_|Boolean (`$true` or `$false`)|If the value of this property is $true, the values of these properties are ignored for the mailbox: _IssueWarningQuota_, _ProhibitSendQuota_, _ProhibitSendReceiveQuota_, , _CalendarLoggingQuota_, _RecoverableItemsWarningQuota_, and _RecoverableItemsQuota_.| -|_UserAccountControl_|_userAccountControl_|For valid values, see the Remarks section in [User-Account-Control attribute](https://go.microsoft.com/fwlink/p/?linkid=183366). You need to convert the hexadecimal values to decimal. Most of the text values won't work as described (even if you remove `ADS_UF` and all underscores).|| -|_UserPrincipalName_|_userPrincipalName_|String (wildcards accepted).|This property contains the user principal name (UPN) for this recipient (for example, `kim@contoso.com`).| +|_UserAccountControl_|_userAccountControl_|For valid values, see the Remarks section in [User-Account-Control attribute](/windows/win32/adschema/a-useraccountcontrol). You need to convert the hexadecimal values to decimal. Most of the text values won't work as described (even if you remove `ADS_UF` and all underscores).|| +|_UserPrincipalName_|_userPrincipalName_|String (wildcards accepted).|This property contains the user principal name (UPN) for this recipient (for example, `kim@contoso.com`). This property is not supported to identify inactive mailboxes.| |_VoiceMailSettings_|_msExchUCVoiceMailSettings_|String (wildcards accepted).|Valid values for this property are: `ExchangeHostedVoiceMail=0`, `ExchangeHostedVoiceMail=1`, `CsHostedVoiceMail=0`, or `CsHostedVoiceMail=1`.| |_WebPage_|_wWWHomePage_|String (wildcards accepted).|| -|_WhenChanged_|_whenChanged_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| -|_WhenChangedUTC_|n/a|Dynamic distribution groups: A date/time value in Coordinated Universal Time (UTC).
Others: Blank or non-blank.|| -|_WhenCreated_|_whenCreated_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| -|_WhenCreatedUTC_|n/a|Dynamic distribution groups: A date/time value in UTC.
Others: Blank or non-blank.|| -|_WhenMailboxCreated_|_msExchWhenMailboxCreated_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| -|_WhenSoftDeleted_|_msExchWhenSoftDeletedTime_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| +|_WhenChanged_|_whenChanged_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| +|_WhenChangedUTC_|n/a|Dynamic distribution groups: A date/time value in Coordinated Universal Time (UTC).
Others: Blank or non-blank.|| +|_WhenCreated_|_whenCreated_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| +|_WhenCreatedUTC_|n/a|Dynamic distribution groups: A date/time value in UTC.
Others: Blank or non-blank.|| +|_WhenMailboxCreated_|_msExchWhenMailboxCreated_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| +|_WhenSoftDeleted_|_msExchWhenSoftDeletedTime_|Dynamic distribution groups: A date/time value using the time zone and regional settings of the Exchange server.
Others: Blank or non-blank.|| |_WindowsEmailAddress_|_mail_|String (wildcards accepted).|| |_WindowsLiveID_|_msExchWindowsLiveID_|String (wildcards accepted).|| ## For more information -Exchange 2007 was the first version of Exchange that required OPATH filters instead of LDAP filters. For more information about converting LDAP filters to OPATH filters, see the Microsoft Exchange Team Blog article, [Need help converting your LDAP filters to OPATH?](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Need-help-converting-your-LDAP-filters-to-OPATH/ba-p/595108). - -For more information about the syntax that can be used within OPATH filters, see [Exchange cmdlet syntax](../exchange-cmdlet-syntax.md). +Exchange Server 2007 was the first version of Exchange that required OPATH filters instead of LDAP filters. For more information about converting LDAP filters to OPATH filters, see the Microsoft Exchange Team Blog article, [Need help converting your LDAP filters to OPATH?](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Need-help-converting-your-LDAP-filters-to-OPATH/ba-p/595108). diff --git a/exchange/docs-conceptual/scc-powershell.md b/exchange/docs-conceptual/scc-powershell.md new file mode 100644 index 0000000000..e5ec203673 --- /dev/null +++ b/exchange/docs-conceptual/scc-powershell.md @@ -0,0 +1,42 @@ +--- +title: "Security & Compliance PowerShell" +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/1/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-powershell +ms.localizationpriority: medium +ms.assetid: 2f33bb84-cede-46f6-9d39-d246e8ce3543 +search.appverid: MET150 +description: "Learn about the articles that are available for using PowerShell for Microsoft Security & Compliance PowerShell." +--- + +# Security & Compliance PowerShell + +Security & Compliance PowerShell is the administrative interface that enables you to manage compliance and some security features of your Microsoft 365 organization from the command line (mostly Microsoft Purview risk and compliance features that were formerly part of Microsoft 365 compliance). For example, you can use Security & Compliance PowerShell to perform Compliance Searches. The following articles provide information about using Security & Compliance PowerShell: + +- To learn about the ExchangeOnlineManagement module that's required to connect to Security & Compliance PowerShell, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). + + > [!TIP] + > Version 3.0.0 and later (2022) is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module). Version 2.0.5 and earlier (2021) was known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). + + To learn about what's new in the Exchange Online PowerShell module, see [What's new in the Exchange Online PowerShell module](whats-new-in-the-exo-module.md). + +- To connect to Security & Compliance PowerShell, see [Connect to Security & Compliance PowerShell](connect-to-scc-powershell.md). The connection instructions are different from Exchange Online PowerShell or standalone Exchange Online Protection (EOP) PowerShell. + + To connect to Security & Compliance PowerShell for unattended scripts, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](app-only-auth-powershell-v2.md). + +- To learn about the structure and layout of the cmdlet reference articles in Security & Compliance PowerShell, see [Exchange cmdlet syntax](exchange-cmdlet-syntax.md). + +Security & Compliance PowerShell contains the following types of cmdlets: + +- Cmdlets that correspond to features available only in Purview compliance and the Microsoft Purview compliance portal. Most cmdlets in Security & Compliance PowerShell fall into this category. +- Basic cmdlets that are also available in Exchange Online PowerShell (for example, [Get-User](/powershell/module/exchange/get-user), and [Get-RoleGroup](/powershell/module/exchange/get-rolegroup)). +- A few cmdlets that correspond to security features available in Exchange Online Protection (EOP) and Microsoft Defender for Office 365 in the Microsoft Defender portal (for example, [Set-SecOpsOverridePolicy](/powershell/module/exchange/set-secopsoverridepolicy)). + + Cmdlets for most EOP and Defender for Office 365 security features (for example, [anti-spam policies](/defender-office-365/anti-spam-protection-about)) are available only in [Exchange Online PowerShell](exchange-online-powershell.md). + +Check the **Applies to** value in the cmdlet references article to verify the PowerShell environment where the cmdlet actually resides. diff --git a/exchange/docs-conceptual/toc.yml b/exchange/docs-conceptual/toc.yml index d1833a619e..b19c66c699 100644 --- a/exchange/docs-conceptual/toc.yml +++ b/exchange/docs-conceptual/toc.yml @@ -1,63 +1,85 @@ - - name: Home - href: index.md + href: index.yml items: - - name: Exchange Server PowerShell - href: exchange-server/exchange-management-shell.md - items: - - name: Open the Exchange Management Shell - href: exchange-server/open-the-exchange-management-shell.md - - name: Connect to Exchange servers using remote PowerShell - href: exchange-server/connect-to-exchange-servers-using-remote-powershell.md - - name: Control remote PowerShell access to Exchange servers - href: exchange-server/control-remote-powershell-access-to-exchange-servers.md - - name: Find the permissions required to run any Exchange cmdlet - href: exchange-server/find-exchange-cmdlet-permissions.md - - name: Exchange cmdlet syntax - href: exchange-server/exchange-cmdlet-syntax.md - - name: Use Update-ExchangeHelp to update Exchange PowerShell help topics on Exchange servers - href: exchange-server/use-update-exchangehelp.md - - name: Recipient filters in Exchange PowerShell commands - href: exchange-server/recipient-filters/recipient-filters.md + - name: Exchange Server PowerShell + href: exchange-management-shell.md items: - - name: Filterable properties for the Filter parameter - href: exchange-server/recipient-filters/filter-properties.md - - name: Filterable properties for the RecipientFilter parameter - href: exchange-server/recipient-filters/recipientfilter-properties.md - - name: Exchange Online PowerShell - href: exchange-online/exchange-online-powershell.md - items: - - name: Connect to Exchange Online PowerShell - href: exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md + - name: Open the Exchange Management Shell + href: open-the-exchange-management-shell.md + - name: Connect to Exchange servers using remote PowerShell + href: connect-to-exchange-servers-using-remote-powershell.md + - name: Control remote PowerShell access to Exchange servers + href: control-remote-powershell-access-to-exchange-servers.md + - name: Find the permissions required to run any Exchange cmdlet + href: find-exchange-cmdlet-permissions.md + - name: Exchange cmdlet syntax + href: exchange-cmdlet-syntax.md + - name: Recipient filters in Exchange Management Shell commands + href: recipient-filters.md + items: + - name: Filterable properties for the Filter parameter + href: filter-properties.md + - name: Filterable properties for the RecipientFilter parameter + href: recipientfilter-properties.md + - name: Values for the CustomPropertyNames parameter + href: values-for-custompropertynames-parameter.md + - name: Exchange Online PowerShell + href: exchange-online-powershell.md items: - - name: Connect to Exchange Online PowerShell using multi-factor authentication - href: exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md - - name: Find the permissions required to run any Exchange cmdlet - href: exchange-server/find-exchange-cmdlet-permissions.md - - name: Enable or disable access to Exchange Online PowerShell - href: exchange-online/disable-access-to-exchange-online-powershell.md - - name: Recipient filters in Exchange Management Shell commands - href: exchange-server/recipient-filters/recipient-filters.md + - name: About the Exchange Online PowerShell module + href: exchange-online-powershell-v2.md + - name: Connect to Exchange Online PowerShell - modern auth and MFA + href: connect-to-exchange-online-powershell.md + - name: Connect using app-only authentication for unattended scripts + href: app-only-auth-powershell-v2.md + - name: Connect using Azure managed identity + href: connect-exo-powershell-managed-identity.md + - name: Connect using C# + href: connect-to-exo-powershell-c-sharp.md + - name: Workarounds for Invoke-Command in REST API connections + href: invoke-command-workarounds-rest-api.md + - name: Enable or disable access to Exchange Online PowerShell + href: disable-access-to-exchange-online-powershell.md + - name: Exchange cmdlet syntax + href: exchange-cmdlet-syntax.md + - name: Find the permissions required to run any Exchange cmdlet + href: find-exchange-cmdlet-permissions.md + - name: What's new in the Exchange Online PowerShell module + href: whats-new-in-the-exo-module.md + - name: Recipient filters in Exchange PowerShell commands + href: recipient-filters.md + items: + - name: Filterable properties for the Filter parameter + href: filter-properties.md + - name: Filterable properties for the RecipientFilter parameter + href: recipientfilter-properties.md + - name: Filters in Exchange Online PowerShell module cmdlets + href: filters-v2.md + - name: Property sets in Exchange Online PowerShell module cmdlets + href: cmdlet-property-sets.md + - name: Security & Compliance PowerShell + href: scc-powershell.md items: - - name: Filterable properties for the Filter parameter - href: exchange-server/recipient-filters/filter-properties.md - - name: Filterable properties for the RecipientFilter parameter - href: exchange-server/recipient-filters/recipientfilter-properties.md - - name: Exchange Online PowerShell V2 - href: exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md - items: - - name: Property sets in cmdlets - href: exchange-online/exchange-online-powershell-v2/cmdlet-property-sets.md - - name: Office 365 Security & Compliance Center PowerShell - href: office-365-scc/office-365-scc-powershell.md - items: - - name: Connect to Office 365 Security & Compliance Center PowerShell - href: office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md + - name: About the Exchange Online PowerShell module + href: exchange-online-powershell-v2.md + - name: Connect to Security & Compliance PowerShell - modern auth and MFA + href: connect-to-scc-powershell.md + - name: App-only authentication for unattended scripts + href: app-only-auth-powershell-v2.md + - name: Exchange cmdlet syntax + href: exchange-cmdlet-syntax.md + - name: Information protection client advanced settings + href: client-advanced-settings.md + - name: What's new in the Exchange Online PowerShell module + href: whats-new-in-the-exo-module.md + - name: Exchange Online Protection PowerShell + href: exchange-online-protection-powershell.md items: - - name: Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication - href: office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md - - name: Exchange Online Protection PowerShell - href: exchange-eop/exchange-online-protection-powershell.md - items: - - name: Connect to Exchange Online Protection PowerShell - href: exchange-eop/connect-to-exchange-online-protection-powershell.md + - name: About the Exchange Online PowerShell module + href: exchange-online-powershell-v2.md + - name: Connect to Exchange Online Protection PowerShell - modern auth and MFA + href: connect-to-exchange-online-protection-powershell.md + - name: Exchange cmdlet syntax + href: exchange-cmdlet-syntax.md + - name: What's new in the Exchange Online PowerShell module + href: whats-new-in-the-exo-module.md diff --git a/exchange/docs-conceptual/values-for-custompropertynames-parameter.md b/exchange/docs-conceptual/values-for-custompropertynames-parameter.md new file mode 100644 index 0000000000..ea729cff90 --- /dev/null +++ b/exchange/docs-conceptual/values-for-custompropertynames-parameter.md @@ -0,0 +1,213 @@ +--- +title: Values for the CustomPropertyNames parameter +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 9/7/2023 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-online +ms.reviewer: +ms.localizationpriority: high +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +description: "Learn about the valid values for the CustomPropertyNames parameter on the Get-CalendarDiagnosticsLog cmdlet in Exchange Online PowerShell." +--- + +# Values for the CustomPropertyNames parameter in Exchange Online PowerShell + +The _CustomPropertyNames_ parameter on the [Get-CalendarDiagnosticObjects](/powershell/module/exchange/get-calendardiagnosticobjects) cmdlet returns the specified properties in the results. + +The article describes the valid values for the _CustomPropertyNames_ parameter. + +|CustomPropertyNames|Description| +|---|---| +|AddOnlineMeetingOnFinalize|Add online meeting on finalize flag.| +|AllAttachmentsHidden|Displays whether there are non-inline attachments inside a protected message.| +|AppointmentAuxiliaryFlags|Detect whether the meeting request is a forwarded meeting (for example, IsForwardedMeeting or AttendeeCount).| +|AppointmentClass|The MessageClass of the calendar that the meeting message is created from.| +|AppointmentCounterEndWhole|End time proposal.| +|AppointmentCounterProposalCount|Current counter proposal count.| +|AppointmentCounterProposal|Indicates whether a Meeting Response object is a counter proposal.| +|AppointmentCounterStartWhole|Start time proposal.| +|AppointmentLastSequenceNumber|If AppointmentSequenceNumber doesn't match, use AppointmentLastSequenceNumber to decide if this is a stale incoming request.| +|AppointmentProposedDuration|Proposed duration of the meeting in total minutes.| +|AppointmentRecurrenceBlob|Holds a copy of recurring information only from Recurring Masters.| +|AppointmentRecurring|Boolean value indicating whether an Appointment is recurring.| +|AppointmentReplyName|The calendar item appointment reply name.| +|AppointmentReplyTime|Gets the time when the attendee replied to the meeting request.| +|AppointmentSequenceNumber|Gets the sequence number of this appointment.| +|AppointmentSequenceTime|A sequence number that's incremented on every modification.| +|AppointmentStateInternal|The state of this appointment (for example, Meeting or Received).| +|AppointmentState|The state of this appointment (for example, Meeting or Received).| +|AttendeeCriticalChangeTime|The attendee's critical change time.| +|BirthdayContactAttributionDisplayName|Indicates the name of the contact that's associated with the birthday event.| +|BirthdayContactId|Represents the birthday contact ID property.| +|BirthdayPersonId|Represents the birthday person ID property that's used to associate multiple contact objects to a single, aggregate person.| +|Birthday|Birthday of the contact.| +|CalendarItemExperienceTypeInternal|Experience type for a calendar item. Used by the client to render custom user experiences for different types of calendar items.| +|CalendarItemType|The Calendar Item Type (for example, RecurringMaster).| +|CalendarLogTriggerAction|The action that's taken on the item (for example, Create or Update).| +|CalendarOriginatorId|Identification of the organizer to prevent unintentional takeover of a meeting by other users.| +|CalendarProcessed|Check if XSO has processed the meeting message.| +|CalendarProcessingSteps|A set of flags for the various steps that were completed in the stages of processing.| +|ChangeHighlight|Encapsulates information on the change highlights of a meeting request.| +|ChangeList|Add item to change list.| +|Charm|Charm on a calendar folder or item.| +|CleanGlobalObjectId|The GlobalObjectId with the Instance Date segment zeroed out. This property is the same for all meeting objects of all exceptions and masters belonging to the same series.| +|ClientBuildVersion|Outlook client build version.| +|ClientInfoString|The entity that made the change (for example, `Client=OWA;, Client=WebServices;;`, or `Client=TBA;Service=MSExchangeMailboxAssistants;Action=ELCAssistant;`).| +|ClientIntent|The intent of the client from any changes that are made to the item.| +|ClientProcessName|Client process name (for example, OUTLOOK.EXE).| +|ConferenceInfo|Used by legacy online meetings and by calling the UCWA APIs.| +|ConferenceTelURI|The conference telephone URI for online meeting.| +|ConferenceType|The type of conferencing that's used during the meeting.| +|ConnectedCalendarEventSourceData|Contains the data of a connected calendar event as received from the source.| +|CreationHash|A hash that identifies the original request to create an event.| +|CreationTime|Creation time of the item.| +|DisallowNewTimeProposal|Specifies whether recipients of the meeting request can propose a new time for the meeting.| +|DisplayAttendeesAll|List of all attendees.| +|DisplayAttendeesCc|Display the Attendees list in the Cc line.| +|DisplayAttendeesTo|Display the Attendees list in the To line.| +|DoNotForward|Organizer wants to prevent attendees from inviting others.| +|Duration|Duration in minutes.| +|EndTimeZoneId|Time zone of the end of the meeting.| +|EndTimeZone|Defines the EndTimeZone property.| +|EndTime|End time of a calendar item.| +|EndWallClock|The end time of the meeting expressed in the time zone of the meeting.| +|EnhancedLocation|Indicates that Enhanced Location data is present. Has value Microsoft.Exchange.Data.Storage.EnhancedLocation.| +|EntryId|The store entry ID or PR_ENTRYID (MAPI).| +|EstimatedAcceptCount|An estimated count of the number of attendees who accepted the meeting.| +|EstimatedAttendeeCount|An estimated count of the number of attendees of the meeting.| +|EstimatedDeclineCount|An estimated count of the number of attendees who declined the meeting.| +|EstimatedTentativeCount|An estimated count of the number of attendees who tentatively accepted the meeting.| +|EventClientId|Client-generated string representing the ID for a series of calendar events.| +|EventDraft|Indicates whether the calendar event is in the draft state.| +|EventResponseTrackingSource|Event response tracking status.| +|EventTimeBasedInboxRemindersState|Contains the state for time-based Inbox reminders pertaining to calendar events.| +|EventTimeBasedInboxReminders|Contains time-based Inbox reminders pertaining to calendar events.| +|ExceptionReplaceTime|The exception replace time.| +|ExceptionalAttendees|Boolean value indicating whether there are Exceptional Attendees.| +|ExceptionalBody|Boolean value indicating whether there are Exceptional Body is changed.| +|ExternalSharingMasterId|If a copy of a remote calendar in shared in the calendar, don't set the organizer, because the organizer isn't simply the owner of the current mailbox. It syncs back from master copy where it's properly evaluated when saved.| +|ForwardNotificationRecipients|List of Forwarded Recipients.| +|FreeBusyStatus|Free/busy status associated with the event.| +|From|From email address.| +|GlobalObjectId|A binary blob used to correlate the meeting requests/responses/cancellations in the Inbox with the meeting item in the Calendar.| +|HasAttachment|Indicates whether the item has attachments.| +|HasExceptionalInboxReminders|Whether a series has any exceptional Inbox reminders.| +|HijackedMeeting|Indicates whether the meeting request was hijacked. Useful to identify specific meetings that weren't processed because another user hijacked the meeting.| +|Importance|Importance status of the email (for example, Normal).| +|InboundICalStream|The contents of the iCalendar MIME part of the original MIME message.| +|InstanceCreationIndex|The index of this instance when the series was originally created.| +|IntendedFreeBusyStatus|The intended free/busy status of the meeting.| +|InternetMessageId|Internet Message ID of the e-mail message.| +|IsAllDayEvent|Indicates whether this appointment is an all day event.| +|IsBirthdayContactWritable|Indicates whether the contact that's associated with the birthday event is writable.| +|IsCancelled|Boolean value indicating whether the meeting is canceled.| +|IsCopyOnWriteItem|Indicator for Calendar Logging items.| +|IsDraft|Boolean value indicating whether the item is a draft. An item is a draft when it hasn't yet been sent.| +|IsEvent|Indicates if the meeting should be displayed in a banner for the event, not in the calendar grid area.| +|IsException|Indicates whether the calendar event is an exception in a recurring series.| +|IsHiddenFromLegacyClients|Decides whether the modern calendar item should be hidden for legacy clients.| +|IsMeetingPollEvent|Boolean value indicating whether the item is a meeting poll event.| +|IsMeeting|Boolean value indicating whether the calendar event is a meeting.| +|IsProcessed|Boolean value indicating whether the message was processed by XSO or by Outlook.| +|IsPublishedCalendarItem|Boolean value indicating whether a calendar event (schedule) has been published.| +|IsRecurring|Boolean value indicating whether the calendar event is recurring.| +|IsResponseRequested|Boolean value indicating whether responses are requested when invitations are sent for this meeting.| +|IsSeriesCancelled|Boolean value indicating whether the recurring master is canceled. Expected to be True for the attendee.| +|IsSilent|Boolean value indicating if the response doesn't contain message body text.| +|IsSingleBodyICal|Boolean value indicating that the original MIME message contained a single MIME part.| +|IsSoftDeleted|Boolean value indicating if the object is soft-deleted.| +|ItemClass|A text string that identifies the sender-defined message class (for example, IPM.Note).| +|ItemId|Object Store ItemId.| +|ItemVersion|Version of the item.| +|LastModifiedTime|The date/time that this item was last modified.| +|LocationAddressInternal|One of the properties that define the enhanced location and their corresponding default values.| +|Location|Gets the location of the calendar event.| +|MFNAddedRecipients|The list of recipients that were explicitly forwarded.| +|MailboxDatabaseName|The distinguished name (DN) of the mailbox database.| +|MapiEndTime|EndTime of Meeting.| +|MapiIsAllDayEvent|An all-day event is midnight to midnight.| +|MapiPREndDate|MapiPR(Pattern Recurrence) EndDate of Meeting.| +|MapiPRStartDate|MapiPR(Pattern Recurrence) StartDate of Meeting.| +|MapiStartTime|StartTime of Meeting.| +|MasterGlobalObjectId|The original GUID of the item if another process needs to change it.| +|MeetingRequestType|Defines the type of meeting request.| +|MeetingRequestWasSent|Indicates whether the meeting request has already been sent.| +|MeetingUniqueId|Unique meeting ID that's used to link meeting history to the master meeting item.| +|MeetingWorkspaceUrl|URL of the meeting workspace. A meeting workspace is a shared website for planning meetings and tracking results.| +|MiddleTierProcessName|ProcessName handling the request (for example, w3wp).| +|MiddleTierServerBuildVersion|EXO Build Version.| +|MiddleTierServerName|Backend Mailbox ServerName.| +|NormalizedSubject|Subject of the meeting.| +|OccurrencesExceptionalViewProperties|Blob representing the exceptional properties of instances of an NPR.| +|OldLocation|Saved old location before updating the new location.| +|OldStartWhole|Old time properties on the updated meeting request.| +|OnlineMeetingConfLink|The online meeting link.| +|OnlineMeetingExternalLink|The online meeting external link.| +|OnlineMeetingInformation|The online meeting information.| +|OnlineMeetingInternalLink|The HTTPS URI for joining the Lync online meeting. Deprecated.| +|OriginalClientInfoString|Some processes are touching the ClientInfoString, so we need to back up the original value for Calendar Logging items.| +|OriginalCreationTime|Creation time of the item.| +|OriginalEntryId|Original `PR_ENTRYID` (MAPI), unique ID identifier in store.| +|OriginalFolderId|Original `PR_FOLDERID` (MAPI), unique ID identifier in store.| +|OriginalGlobalObjectId|The original GUID of the item in case we have to change it.| +|OriginalICal|The original iCal of an imported item.| +|OriginalLastModifiedTime|Used as the primary sort field to order the events.| +|OriginalMeetingType|Retains the original MeetingType in case the original meeting type is reset.| +|OriginalStoreEntryId|Maintains a copy of the store entry ID if the original gets modified.| +|OwnerAppointmentID|A number that's unique to the sender's calendar. Outlook uses this number to correlate meeting messages with calendar items.| +|OwnerCriticalChangeTime|DateTime tracking value for Owner Critical Change Time.| +|ParentDisplayName|ParentDisplayName of the Folder.| +|ParkedCorrelationId|The correlation ID of parked message.| +|ParkedMessagesFolderEntryId|The entry ID of the ParkedMessages folder.| +|Preview|Preview of the email message.| +|PropertyChangeMetadataProcessingFlags|Flags representing property change metadata processing behavior.| +|PropertyChangeMetadataRaw|Blob representing property change metadata for Series exception management purposes.| +|PublishedCalendarItemUrl|The URL of a published calendar event (schedule).| +|RawAttendeeInformation|Raw attendee information provided by a client. Used to help troubleshoot and debug attendee translation issues.| +|ReceivedBy|The ReceivedBy property of the email message.| +|ReceivedRepresenting|Returns the received on behalf display name for delegate meeting message own meeting.| +|RecipientType|The recipient type of a recipient on the message.| +|RecurrencePattern|A date for which this pattern should be created.| +|ReminderIsSetInternal|Boolean value indicating whether the reminder is set internally.| +|ReminderMinutesBeforeStartInternal|Reminder in minutes before the meeting starts.| +|ResponseState|Values are Accepted, Tentative, or Declined.| +|ResponseType|Gets the type of response the attendee gave to the meeting invitation it received.| +|ResponsibleUserName|The LegacyExchangeDN value of the user who made the change (for example, `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BN6PR11MB1587/cn=Microsoft System Attendant` or `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=696eea97d3c449eab648920d03385efb-admin`).| +|SenderEmailAddress|SMTP address of who sent it.| +|Sensitivity|The sensitivity of an item.| +|SentRepresentingDisplayName|The display name of the sent representing person.| +|SentRepresentingEmailAddress|Represents sent representing email address.| +|SentRepresentingEntryId|The entry ID of the sent representing person.| +|SentRepresentingType|The address type of the sent representing person.| +|SeriesId|Representing ID for series of calendar events.| +|SeriesReminderIsSet|Flag indicating whether a reminder is set for the whole series.| +|Size|Size in bytes of the Meeting Message.| +|SkypeTeamsMeetingUrl|The meeting URL for a Teams meeting.| +|SkypeTeamsProperties|The relevant properties for a Teams meeting.| +|StartTimeZoneId|Time zone of the start of the meeting.| +|StartTimeZone|Start timezone of a calendar item.| +|StartTime|Start time of a calendar item.| +|StartWallClock|The start time of the meeting expressed in the time zone of the meeting.| +|SuggestionCategory|The suggestion category for the message.| +|TimeZoneBlob|Outlook time zone blob (from the registry) for recurrence.| +|TimeZoneDefinitionEnd|Legacy time zone (ExchangeTimeZoneTime) blob for end time.| +|TimeZoneDefinitionRecurring|Legacy time zone (ExchangeTimeZoneTime) blob for recurrence.| +|TimeZoneDefinitionStart|Legacy time zone (ExchangeTimeZoneTime) blob for start time.| +|TimeZone|TimeZone value.| +|TransportMessageHeaders|Transport Message Header Information.| +|UCCapabilities|The XML blob of OCS capabilities for the Lync online meeting.| +|UCInband|The XML blob of Inband data for the Lync online meeting.| +|UCMeetingSettingSent|The XML blob of all information related to the Lync online meeting.| +|UCMeetingSetting|The XML blob of all information related to the Lync online meeting.| +|UCOpenedConferenceID|RThe guid associated with this online meeting.| +|UnsendableRecipients|Recipient data for all unsendable recipients.| +|ViewEndTime|End time of a calendar item.| +|ViewStartTime|Start time of a calendar item.| +|When|Localized text using the Exchange Server culture or the culture specified in the PreferredCulture property of the ExchangeService object that this appointment is bound to.| diff --git a/exchange/docs-conceptual/whats-new-in-the-exo-module.md b/exchange/docs-conceptual/whats-new-in-the-exo-module.md new file mode 100644 index 0000000000..64e027b733 --- /dev/null +++ b/exchange/docs-conceptual/whats-new-in-the-exo-module.md @@ -0,0 +1,126 @@ +--- +title: What's new in the Exchange Online PowerShell module +ms.author: chrisda +author: chrisda +manager: deniseb +ms.date: 03/26/2025 +ms.audience: Admin +audience: Admin +ms.topic: article +ms.service: exchange-online +ms.reviewer: +ms.localizationpriority: medium +ms.collection: Strat_EX_Admin +ms.custom: +ms.assetid: +search.appverid: MET150 +keywords: what's new in exchange online powershell, what's new in security & compliance powershell, EXO V2 module, EXO V3 module +description: "Learn about the new features and functionality available in the latest release of the Exchange Online PowerShell module." +--- + +# What's new in the Exchange Online PowerShell module + +This article lists new features in the Exchange Online PowerShell module that's used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. Features that are currently in preview are denoted with **(preview)**. + +## March 2025 + +- [Version 3.7.2](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.1) + + For information about what's in this release, see [Version 3.7.2](exchange-online-powershell-v2.md#version-372). + +## January 2025 + +- [Version 3.7.1](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.1) + + For information about what's in this release, see [Version 3.7.1](exchange-online-powershell-v2.md#version-371). + +## December 2024 + +- [Version 3.7.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.0) + + Starting with this version of the module, command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ parameter in the **Connect-ExchangeOnline** command so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet. + + For information about what's in this release, see [Version 3.7.0](exchange-online-powershell-v2.md#version-370). + +## September 2024 + +- [Version 3.6.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.6.0) + + For information about what's in this release, see [Version 3.6.0](exchange-online-powershell-v2.md#version-360). + +## July 2024 + +- [Version 3.5.1](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.5.1) has been released. + + For information about what's in this release, see [Version 3.5.1](exchange-online-powershell-v2.md#version-351). + +## May 2024 + +- [Version 3.5.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.5.0) has been released. + + For information about what's in this release, see [Version 3.5.0](exchange-online-powershell-v2.md#version-350). + +## October 2023 + +- [Version 3.4.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.4.0) + + For information about what's in this release, see [Version 3.4.0](exchange-online-powershell-v2.md#version-340). + +## September 2023 + +- [Version 3.3.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.3.0) has been released. + + For information about what's in this release, see [Version 3.3.0](exchange-online-powershell-v2.md#version-330). + +## June 2023 + +- [Version 3.2.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.2.0) has been released. + +- [Virtually all](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432) Security & Compliance PowerShell cmdlets are now backed by the REST API, and REST API is used by default. To connect using remote PowerShell mode (which requires [Basic authentication in WinRM](exchange-online-powershell-v2.md#turn-on-basic-authentication-in-winrm)), use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. + + For information about what's in this release, see [Version 3.2.0](exchange-online-powershell-v2.md#version-320). + +## May 2023 + +- The end of support for remote PowerShell in Security & Compliance PowerShell has been announced. For more information, see [Announcing Deprecation of Remote PowerShell (RPS) Protocol in Exchange Online PowerShell](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432). + +- [Version 3.2.0-Preview4](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.2.0-Preview4) has been released. + + This version supports the Preview of Security & Compliance cmdlets backed by the REST API. Some, but not all cmdlets are supported. Basic authentication in WinRM is not required in Security & Compliance PowerShell for REST API cmdlets. + + > [!NOTE] + > The default value of the _UseRPSSession_ switch in **Connect-IPSSession** is now the same as **Connect-ExchangeOnline**. To connect in REST API mode, don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. To connect using remote PowerShell mode (which requires [Basic authentication in WinRM](exchange-online-powershell-v2.md#turn-on-basic-authentication-in-winrm)), use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. + > + > REST API connections in the EXO V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + +## April 2023 + +- [Version 3.2.0-Preview3](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.2.0-Preview3) has been released. + + This version supports the Preview of Security & Compliance cmdlets backed by the REST API. Some, but not all cmdlets are supported. Basic authentication in WinRM is not required in Security & Compliance PowerShell for REST API cmdlets. + + > [!NOTE] + > The default value of the _UseRPSSession_ switch in **Connect-IPSSession** is opposite of **Connect-ExchangeOnline**. To connect in REST API mode, use `-UseRPSSession:$false` in the **Connect-IPPSSession** command. To connect using remote PowerShell mode (which requires [Basic authentication in WinRM](exchange-online-powershell-v2.md#turn-on-basic-authentication-in-winrm)), don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. The default behavior will change in a later version of the module as more Security & Compliance cmdlets are available in REST API mode. + +## January 2023 + +- [Version 3.1.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.1.0) has been released. + + For information about what's in this release, see [Version 3.1.0](exchange-online-powershell-v2.md#version-310). + +## December 2022 + +- The end of support for remote PowerShell in Exchange Online PowerShell (not in Security & Compliance PowerShell) has been announced. For more information, see [Announcing Deprecation of Remote PowerShell (RPS) Protocol in Exchange Online PowerShell](https://aka.ms/RPSDeprecation). + +## September 2022 + +- Version 3.0.0 has been released, and is now known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module): + - Version 3.0.0 is the Generally Availability (GA) release of the 2.0.6-PreviewX versions of the module. + - All Exchange Online PowerShell cmdlets are now backed by the REST API. Basic authentication in WinRM is not required in Exchange Online PowerShell for REST API cmdlets. + + > [!TIP] + > REST API connections in the EXO V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). + + - Certificate based authentication (also known as CBA or app-only authentication) is available for Security & Compliance PowerShell. + + For more information, see [REST API connections in the EXO V3 module](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module) and [Version 3.0.0](exchange-online-powershell-v2.md#version-300-preview-versions-known-as-v206-previewx). diff --git a/exchange/exchange-ps/exchange/active-directory/Add-ADPermission.md b/exchange/exchange-ps/exchange/Add-ADPermission.md similarity index 77% rename from exchange/exchange-ps/exchange/active-directory/Add-ADPermission.md rename to exchange/exchange-ps/exchange/Add-ADPermission.md index b6c78f7601..c1daf4b98b 100644 --- a/exchange/exchange-ps/exchange/active-directory/Add-ADPermission.md +++ b/exchange/exchange-ps/exchange/Add-ADPermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/add-adpermission +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-ADPermission @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Add-ADPermission cmdlet to add permissions to an Active Directory object. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,7 +32,8 @@ Add-ADPermission [-Identity] -User ] [-InheritedObjectType ] [-Properties ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Owner @@ -41,30 +41,31 @@ Add-ADPermission [-Identity] -User -Owner [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Instance ``` -Add-ADPermission -Instance +Add-ADPermission [[-Identity] ] -Instance [-AccessRights ] [-ChildObjectTypes ] [-Confirm] [-Deny] [-DomainController ] [-ExtendedRights ] - [[-Identity] ] [-InheritanceType ] [-InheritedObjectType ] [-Properties ] [-User ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors) Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://docs.microsoft.com/Exchange/permissions/permissions). +The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -132,9 +133,26 @@ Accept wildcard characters: False ``` ### -Owner -The Owner parameter specifies the owner of the Active Directory object. If the name of the owner contains spaces, enclose the name in quotation marks ("). +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: -The Owner parameter can only be used with the Identity parameter and no other parameters. +- Mailbox users +- Mail users +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the AccessRights or User parameters. ```yaml Type: SecurityPrincipalIdParameter @@ -150,7 +168,31 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the user that the permissions are being granted to on the object. If the name contains spaces, enclose the name in quotation marks ("). +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 +- Mail users +- Security groups + +For the best results, we recommend using the following values: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Owner parameter. ```yaml Type: SecurityPrincipalIdParameter @@ -179,46 +221,32 @@ Accept wildcard characters: False ``` ### -AccessRights -The AccessRights parameter specifies the rights needed to perform the operation. Valid values include: +The AccessRights parameter specifies the rights that you want to add for the user on the Active Directory object. Valid values include: - AccessSystemSecurity - - CreateChild - - DeleteChild - - ListChildren - - Self - - ReadProperty - - WriteProperty - - DeleteTree - - ListObject - - ExtendedRight - - Delete - - ReadControl - - GenericExecute - - GenericWrite - - GenericRead - - WriteDacl - - WriteOwner - - GenericAll - - Synchronize +You can specify multiple values separated by commas. + +You can't use this parameter with the Owner parameter. + ```yaml Type: ActiveDirectoryRights[] Parameter Sets: AccessRights, Instance @@ -253,9 +281,8 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -271,7 +298,7 @@ Accept wildcard characters: False ``` ### -Deny -The Deny switch specifies whether to deny permissions to the user on the Active Directory object. +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 @@ -321,7 +348,13 @@ Accept wildcard characters: False ``` ### -InheritanceType -The InheritanceType parameter specifies whether permissions are inherited. +The InheritanceType parameter specifies how permissions are inherited. Valid values are: + +- None +- All (this is the default value) +- Children +- Descendents [sic] +- SelfAndChildren ```yaml Type: ActiveDirectorySecurityInheritance @@ -391,12 +424,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Add-AttachmentFilterEntry.md b/exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Add-AttachmentFilterEntry.md rename to exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md index 41d5b29163..000fae4281 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Add-AttachmentFilterEntry.md +++ b/exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/add-attachmentfilterentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-AttachmentFilterEntry @@ -17,7 +16,7 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Add-AttachmentFilterEntry cmdlet to add an entry to the attachment filter list that's used by the Attachment Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Add-AttachmentFilterEntry -Name -Type [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-attachmentfilterlistconfig). +On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://learn.microsoft.com/powershell/module/exchange/set-attachmentfilterlistconfig). On Edge Transport servers, you need to be a member of the local Administrators group to run this cmdlet. @@ -55,7 +55,6 @@ This example adds an attachment filter entry based on the MIME content type imag 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. - - A valid MIME content type (for example, application/javascript or text/scriplet). You need to use the value ContentType for the Type parameter. ```yaml @@ -75,7 +74,6 @@ Accept wildcard characters: False 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. - - FileName: This value matches the attachment filter entry against the simple file name that's specified in the Name parameter. ```yaml @@ -94,8 +92,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -150,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md new file mode 100644 index 0000000000..aedd7aee1a --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md @@ -0,0 +1,297 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-AvailabilityAddressSpace + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Add-AvailabilityAddressSpace cmdlet to create availability address space objects that are used to share free/busy data across Exchange organizations. + +The maximum number off Availability address spaces returned by Active Directory to Exchange is 100. We recommend using 100 or fewer address spaces in order for Availability lookups to work properly. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Add-AvailabilityAddressSpace -AccessMethod -ForestName + [-Confirm] + [-Credentials ] + [-DomainController ] + [-ProxyUrl ] + [-TargetAutodiscoverEpr ] + [-TargetServiceEpr ] + [-TargetTenantId ] + [-UseServiceAccount ] + [-WhatIf] + [] +``` + +## DESCRIPTION +In Exchange Online, you need to run the New-AvailabilityConfig cmdlet before you run the Add-AvailabilityAddressSpace cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Add-AvailabilityAddressSpace -ForestName contoso.com -AccessMethod OrgWideFB -Credentials (Get-Credential) +``` + +In on-premises Exchange, this example is useful with an untrusted cross-forest Availability service, or if detailed cross-forest free/busy service isn't desired. Enter a username and password when you're prompted by the command. For an untrusted cross-forest configuration, make sure that the user doesn't have a mailbox. + +### Example 2 +```powershell +Add-AvailabilityAddressSpace -ForestName contoso.com -AccessMethod PerUserFB -Credentials (Get-Credential) +``` + +In on-premises Exchange, this example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest, and the specified account connects to the contoso.com forest. The specified account must be an existing account in the contoso.com forest. + +### Example 3 +```powershell +Add-AvailabilityAddressSpace -ForestName contoso.com -AccessMethod PerUserFB -UseServiceAccount $true +``` + +In on-premises Exchange, this example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest and uses the service account (typically the local system account or the computer account) to connect to the contoso.com forest. Because the service is trusted, there is no issue with authorization when the current forest tries to retrieve free/busy information from contoso.com. + +### Example 4 +```powershell +Add-AvailabilityAddressSpace -ForestName contoso.onmicrosoft.com -AccessMethod OrgWideFBToken -TargetTenantId "9d341953-da1f-41b0-8810-76d6ef905273" -TargetServiceEpr "outlook.office.com" +``` + +In Exchange Online, this example sets up the sharing of free/busy information with contoso.onmicrosoft.com (tenant ID value 9d341953-da1f-41b0-8810-76d6ef905273), which is a regular Microsoft 365 organization. + +## PARAMETERS + +### -AccessMethod +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. +- OrgWideFB: Only default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter. +- OrgWideFBBasic: Free/busy sharing between tenants that are all in Exchange Online. +- InternalProxy: The request is proxied to an Exchange server in the site that's running a later version of Exchange. +- PublicFolder: This value was used to access free/busy data on Exchange Server 2003 servers. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForestName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credentials +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUrl +This parameter is available only in on-premises Exchange. + +The ProxyUrl parameter was used to specify the URL that directed an Exchange 2007 Client Access server to proxy free/busy requests through an Exchange 2010 or Exchange 2013 Client Access server when requesting federated free/busy data for a user in another organization. When you used this parameter, you needed to set the AccessMethod parameter value to InternalProxy. + +This parameter required that you created the proper trust relationships and sharing relationships between the Exchange organizations. For more information, see [New-FederationTrust](https://learn.microsoft.com/powershell/module/exchange/new-federationtrust). + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetAutodiscoverEpr +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetServiceEpr +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: + +- Microsoft 365 or Microsoft 365 GCC: outlook.office.com +- Office 365 operated by 21Vianet: partner.outlook.cn +- Microsoft 365 GCC High or DoD: outlook.office365.us + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetTenantId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseServiceAccount +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 + +- $true: The local Availability service account is used for authorization. +- $false: The local Availability service account isn't used for authorization. You need to use the Credentials 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Add-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md new file mode 100644 index 0000000000..ddec608aad --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md @@ -0,0 +1,135 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-ComplianceCaseMember + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Add-ComplianceCaseMember cmdlet to add an individual member to an eDiscovery case in the Microsoft Purview compliance portal. To replace all existing members, use the Update-ComplianceCaseMember cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Add-ComplianceCaseMember [-Case] -Member + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You use eDiscovery cases to control who can create, access, and manage compliance searches in your organization. You use the New-ComplianceCase cmdlet to create eDiscovery cases. The eDiscovery Manager who created the case is automatically added as a member of the case. + +To add a member of an eDiscovery case, the user needs to be a member of the Reviewer or eDiscovery Manager role groups. When a member of the eDiscovery Manager role group is a member of an eDiscovery case, the user can: + +- Add and remove case members. +- Create and edit compliance searches associated with a case. +- Perform compliance actions (for example, export) on the results of a compliance search. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Add-ComplianceCaseMember -Case "Case 2112" -Member johnevans@contoso.com +``` + +This example adds John Evans to the eDiscovery case named Case 2112. + +## PARAMETERS + +### -Case +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Member +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Add-ContentFilterPhrase.md b/exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Add-ContentFilterPhrase.md rename to exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md index 141f913942..72bcef12ec 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Add-ContentFilterPhrase.md +++ b/exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/add-contentfilterphrase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-ContentFilterPhrase @@ -15,21 +14,24 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Add-ContentFilterPhrase cmdlet to define custom words for the Content Filter agent. A custom word is a word or phrase that the administrator sets for the Content Filter agent to evaluate the content of an message and apply appropriate filter processing. +Use the Add-ContentFilterPhrase cmdlet to define custom words for the Content Filter agent. A custom word is a word or phrase that the administrator sets for the Content Filter agent to evaluate the content of an message and apply appropriate filter processing. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Add-ContentFilterPhrase [-Phrase] -Influence [-Confirm] - [-DomainController ] [-WhatIf] [] +Add-ContentFilterPhrase [-Phrase] -Influence + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Add-ContentFilterPhrase cmdlet adds phrases to the Allow or Block phrases list. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,35 +44,35 @@ This example adds the phrase Free credit report to the Block phrase list. Any me ## PARAMETERS -### -Influence -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. +### -Phrase +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: Influence +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -Phrase -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. +### -Influence +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. ```yaml -Type: String +Type: Influence Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False @@ -79,8 +81,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -135,12 +136,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md similarity index 92% rename from exchange/exchange-ps/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md rename to exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md index ce6c485f0b..d1e4a31542 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md +++ b/exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/add-databaseavailabilitygroupserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-DatabaseAvailabilityGroupServer @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Add-DatabaseAvailabilityGroupServer cmdlet to add a Mailbox server to a database availability group (DAG). A DAG is a set of Mailbox servers that use continuous replication and managed availability to provide automatic database-level recovery from database, server, or network failures. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ Add-DatabaseAvailabilityGroupServer [-Identity] ] [-SkipDagValidation] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -36,7 +36,7 @@ To add a Mailbox server to a DAG, the Mailbox server must be running the Windows To add the first server to a DAG and create a computer object for the DAG, the Exchange Windows Permissions security group must have the appropriate rights to add computer accounts to the domain. Alternatively, a computer account can be created and disabled prior to adding the server. Adding the first server to the DAG enables the computer account for the DAG. Thus, the account used for the task doesn't need permissions to add a computer account to the domain. If you're pre-creating the computer account, the name of the account must match the name for the DAG. For example, if the DAG is named DAG1, the computer account must be named DAG1. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,11 +69,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -92,8 +89,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,7 +122,7 @@ Accept wildcard characters: False ``` ### -SkipDagValidation -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. +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 @@ -162,12 +158,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Add-DistributionGroupMember.md b/exchange/exchange-ps/exchange/Add-DistributionGroupMember.md similarity index 87% rename from exchange/exchange-ps/exchange/users-and-groups/Add-DistributionGroupMember.md rename to exchange/exchange-ps/exchange/Add-DistributionGroupMember.md index a7817c8d07..90029ad72b 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Add-DistributionGroupMember.md +++ b/exchange/exchange-ps/exchange/Add-DistributionGroupMember.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/add-distributiongroupmember +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Add-DistributionGroupMember @@ -17,18 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Add-DistributionGroupMember cmdlet to add a single recipient to distribution groups and mail-enabled security groups. To replace all members, use the Update-DistributionGroupMember cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Add-DistributionGroupMember [-Identity] [-BypassSecurityGroupManagerCheck] - [-Confirm] [-DomainController ] [-Member ] [-WhatIf] +Add-DistributionGroupMember [-Identity] + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-DomainController ] + [-Member ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,15 +48,10 @@ This example adds John Evans to the distribution group named Staff. The Identity parameter specifies the group that you want to modify. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -70,14 +68,13 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. 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: +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. -- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +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: +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. - Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. -You don't need to specify a value with this switch. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -94,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -133,15 +129,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned. @@ -180,12 +171,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Add-FederatedDomain.md b/exchange/exchange-ps/exchange/Add-FederatedDomain.md similarity index 88% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Add-FederatedDomain.md rename to exchange/exchange-ps/exchange/Add-FederatedDomain.md index 868980d4ac..1a193dfead 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Add-FederatedDomain.md +++ b/exchange/exchange-ps/exchange/Add-FederatedDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/add-federateddomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-FederatedDomain @@ -19,21 +18,24 @@ Use the Add-FederatedDomain cmdlet to configure a secondary domain with the fede The domains being added to the federation trust must exist as accepted domains in the Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Add-FederatedDomain [[-Identity] ] -DomainName [-Confirm] - [-DomainController ] [-WhatIf] [] +Add-FederatedDomain [[-Identity] ] -DomainName + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION You can add any registered Internet domain to the federated organization identifier. You must prove domain ownership by creating a TXT record in the Domain Name System (DNS) zone of each domain you add. -For more details, see [Federation](https://docs.microsoft.com/exchange/federation-exchange-2013-help). +For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,6 +48,22 @@ This example adds the domain Contoso.co.uk to the existing federation trust. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DomainName The DomainName parameter specifies the secondary domain to be configured. @@ -65,8 +83,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -98,22 +115,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -135,12 +136,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/server-health-and-performance/Add-GlobalMonitoringOverride.md rename to exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md index 5bd49cfd2e..975a6bf632 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Add-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/add-globalmonitoringoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-GlobalMonitoringOverride @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Add-GlobalMonitoringOverride cmdlet to override the thresholds and parameters of the managed availability probes, monitors and responders on all Exchange 2013 or later servers in your organization. The cmdlet enables monitoring changes and threshold tuning to the environment. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,20 +26,24 @@ Add-GlobalMonitoringOverride [-Identity] -ApplyVersion -ItemT [-Confirm] [-DomainController ] [-Roles ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Duration ``` -Add-GlobalMonitoringOverride [-Identity] -ItemType -PropertyName -PropertyValue [-BuildRange ] [-Duration ] +Add-GlobalMonitoringOverride [-Identity] -ItemType -PropertyName -PropertyValue + [-BuildRange ] + [-Duration ] [-Confirm] [-DomainController ] [-Roles ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,37 +63,37 @@ This example adds a global monitoring override that disables the StorageLogicalD ## PARAMETERS -### -ApplyVersion -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. - -You can't use this parameter with the Duration parameter. +### -Identity +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: Version -Parameter Sets: ApplyVersion +Type: String +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identity of the probe, monitor, or responder. This parameter uses the syntax \\\\[\\\]. Note that the values are case sensitive. For example, use "AD\\ActiveDirectoryConnectivityServerReboot", not "ad\\activedirectoryconnectivityserverreboot". +### -ApplyVersion +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. + +You can't use this parameter with the Duration parameter. ```yaml -Type: String -Parameter Sets: (All) +Type: Version +Parameter Sets: ApplyVersion Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -100,9 +103,7 @@ Accept wildcard characters: False The ItemType parameter specifies the item type for the property that you want to override. Valid values are: - Probe - - Monitor - - Responder ```yaml @@ -153,8 +154,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -263,12 +263,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPAllowListEntry.md b/exchange/exchange-ps/exchange/Add-IPAllowListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Add-IPAllowListEntry.md rename to exchange/exchange-ps/exchange/Add-IPAllowListEntry.md index 247916a47b..d987ed4c56 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPAllowListEntry.md +++ b/exchange/exchange-ps/exchange/Add-IPAllowListEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/add-ipallowlistentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-IPAllowListEntry @@ -17,7 +16,7 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Add-IPAllowListEntry cmdlet to add IP Allow list entries to the IP Allow list that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,7 +27,8 @@ Add-IPAllowListEntry -IPAddress [-Confirm] [-ExpirationTime ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### IPRange @@ -38,7 +38,8 @@ Add-IPAllowListEntry -IPRange [-Confirm] [-ExpirationTime ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -56,10 +57,10 @@ This example adds the IP address 192.168.0.100 to the list of allowed IP address ### Example 2 ```powershell -Add-IPAllowListEntry -IPRange 192.168.0.1/24 -ExpirationTime "1/3/2013 23:59" +Add-IPAllowListEntry -IPRange 192.168.0.1/24 -ExpirationTime "1/3/2014 23:59" ``` -This example adds the IP address range 192.168.0.1/24 to the list of allowed IP addresses and configures the IP Allow list entry to expire at 23:59 on January 3, 2013. +This example adds the IP address range 192.168.0.1/24 to the list of allowed IP addresses and configures the IP Allow list entry to expire at 23:59 on January 3, 2014. ## PARAMETERS @@ -80,11 +81,10 @@ Accept wildcard characters: False ``` ### -IPRange -The IPRange parameter specifies a range of IP addresses to add to the IP Allow list. You can use the following formats: +The IPRange parameter specifies a range of IP addresses to add to the IP Allow list. Valid values are: -- CIDR IP:192.168.0.1/24 - -- IP address range:192.168.0.1-192.168.0.254. +- IP address range: 192.168.0.1-192.168.0.254. +- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.0.1/24. ```yaml Type: IPRange @@ -118,8 +118,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -138,7 +137,7 @@ Accept wildcard characters: False ### -ExpirationTime 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". +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". ```yaml Type: DateTime @@ -157,11 +156,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -202,12 +198,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPAllowListProvider.md b/exchange/exchange-ps/exchange/Add-IPAllowListProvider.md similarity index 93% rename from exchange/exchange-ps/exchange/antispam-antimalware/Add-IPAllowListProvider.md rename to exchange/exchange-ps/exchange/Add-IPAllowListProvider.md index 372de86ca9..9b528293bd 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPAllowListProvider.md +++ b/exchange/exchange-ps/exchange/Add-IPAllowListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/add-ipallowlistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-IPAllowListProvider @@ -17,14 +16,21 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Add-IPAllowListProvider cmdlet to create IP Allow list providers that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Add-IPAllowListProvider [-Name] -LookupDomain [-AnyMatch ] - [-BitmaskMatch ] [-Confirm] [-DomainController ] [-Enabled ] - [-IPAddressesMatch ] [-Priority ] [-WhatIf] [] +Add-IPAllowListProvider [-Name] -LookupDomain + [-AnyMatch ] + [-BitmaskMatch ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-IPAddressesMatch ] + [-Priority ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -48,33 +54,33 @@ This example adds an IP Allow list provider and configures a bitmask return valu ## PARAMETERS -### -LookupDomain -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. +### -Name +The Name parameter specifies a descriptive name for the IP Allow list provider. ```yaml -Type: SmtpDomain +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies a descriptive name for the IP Allow list provider. +### -LookupDomain +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: String +Type: SmtpDomain Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -115,8 +121,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -221,12 +226,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPBlockListEntry.md b/exchange/exchange-ps/exchange/Add-IPBlockListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Add-IPBlockListEntry.md rename to exchange/exchange-ps/exchange/Add-IPBlockListEntry.md index 28ba5a22bf..35072b31fd 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPBlockListEntry.md +++ b/exchange/exchange-ps/exchange/Add-IPBlockListEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/add-ipblocklistentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-IPBlockListEntry @@ -17,7 +16,7 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Add-IPBlockListEntry cmdlet to add IP Block list entries to the IP Block list that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,7 +27,8 @@ Add-IPBlockListEntry -IPAddress [-Confirm] [-ExpirationTime ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### IPRange @@ -38,7 +38,8 @@ Add-IPBlockListEntry -IPRange [-Confirm] [-ExpirationTime ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -55,10 +56,10 @@ This example adds the IP address 192.168.0.100 to the list of blocked IP address ### Example 2 ```powershell -Add-IPBlockListEntry -IPRange 192.168.0.1/24 -ExpirationTime "1/3/2013 23:59" +Add-IPBlockListEntry -IPRange 192.168.0.1/24 -ExpirationTime "1/3/2014 23:59" ``` -This example adds the IP address range 192.168.0.1/24 to the list of blocked IP addresses and configures the IP Block list entry to expire at 23:59 on January 3, 2013. +This example adds the IP address range 192.168.0.1/24 to the list of blocked IP addresses and configures the IP Block list entry to expire at 23:59 on January 3, 2014. ## PARAMETERS @@ -79,11 +80,10 @@ Accept wildcard characters: False ``` ### -IPRange -The IPRange parameter specifies a range of IP addresses to add to the IP Block list. You can use the following formats: +The IPRange parameter specifies a range of IP addresses to add to the IP Block list. Valid values are: -- CIDR IP:192.168.0.1/24 - -- IP address range:192.168.0.1-192.168.0.254. +- IP address range: 192.168.0.1-192.168.0.254. +- Classless Inter-Domain Routing (CIDR) IP address range: 192.168.0.1/24. ```yaml Type: IPRange @@ -117,8 +117,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -137,7 +136,7 @@ Accept wildcard characters: False ### -ExpirationTime 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". +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". ```yaml Type: DateTime @@ -156,11 +155,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -201,12 +197,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPBlockListProvider.md b/exchange/exchange-ps/exchange/Add-IPBlockListProvider.md similarity index 93% rename from exchange/exchange-ps/exchange/antispam-antimalware/Add-IPBlockListProvider.md rename to exchange/exchange-ps/exchange/Add-IPBlockListProvider.md index 785ded8beb..29ca57a584 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Add-IPBlockListProvider.md +++ b/exchange/exchange-ps/exchange/Add-IPBlockListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/add-ipblocklistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-IPBlockListProvider @@ -17,14 +16,21 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Add-IPBlockListProvider cmdlet to create IP Block list providers that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Add-IPBlockListProvider [-Name] -LookupDomain [-AnyMatch ] - [-BitmaskMatch ] [-Confirm] [-DomainController ] [-Enabled ] - [-IPAddressesMatch ] [-Priority ] [-RejectionResponse ] [-WhatIf] +Add-IPBlockListProvider [-Name] -LookupDomain + [-AnyMatch ] + [-BitmaskMatch ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-IPAddressesMatch ] + [-Priority ] + [-RejectionResponse ] + [-WhatIf] [] ``` @@ -49,33 +55,33 @@ This example adds an IP Block list provider and configures a bitmask return valu ## PARAMETERS -### -LookupDomain -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. +### -Name +The Name parameter specifies a descriptive name for the IP Block list provider. ```yaml -Type: SmtpDomain +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies a descriptive name for the IP Block list provider. +### -LookupDomain +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: String +Type: SmtpDomain Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -116,8 +122,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -240,12 +245,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Add-MailboxDatabaseCopy.md b/exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md similarity index 94% rename from exchange/exchange-ps/exchange/database-availability-groups/Add-MailboxDatabaseCopy.md rename to exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md index 893cdbcfe6..df90710452 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Add-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/add-mailboxdatabasecopy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-MailboxDatabaseCopy @@ -17,31 +16,35 @@ This cmdlet is available only in on-premises Exchange. Use the Add-MailboxDatabaseCopy cmdlet to create a passive copy of an existing active mailbox database. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Add-MailboxDatabaseCopy [-Identity] [-MailboxServer] - [-ActivationPreference ] [-Confirm] [-DomainController ] [-ReplayLagTime ] - [-SeedingPostponed] [-TruncationLagTime ] [-WhatIf] [-ConfigurationOnly] - [-ReplayLagMaxDelay ] [] + [-ActivationPreference ] + [-ConfigurationOnly] + [-Confirm] + [-DomainController ] + [-ReplayLagMaxDelay ] + [-ReplayLagTime ] + [-SeedingPostponed] + [-TruncationLagTime ] + [-WhatIf] + [] ``` ## DESCRIPTION To use the Add-MailboxDatabaseCopy cmdlet to add a mailbox database copy, the following criteria must be met: - The specified Mailbox server must be in the same database availability group (DAG), and the DAG must have quorum and be healthy. - - The specified Mailbox server must not already host a copy of the specified mailbox database. - - The database path used by the specified database must also be available on the specified Mailbox server, because all copies of a database must use the same path. - - If you're adding the second copy of a database (for example, adding the first passive copy of the database), circular logging must not be enabled for the specified mailbox database. If circular logging is enabled, you must first disable it. After the mailbox database copy has been added, circular logging can be enabled. After enabling circular logging for a replicated mailbox database, continuous replication circular logging (CRCL) is used instead of JET circular logging. If you're adding the third or subsequent copy of a database, CRCL can remain enabled. After running the Add-MailboxDatabaseCopy cmdlet, the new copy remains in a Suspended state if the SeedingPostponed parameter is specified. When the database copy status is set to Suspended, the SuspendMessage is set to "Replication is suspended for database copy '{0}' because database needs to be seeded." -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,9 +75,7 @@ This example adds a copy of mailbox database DB3 to the Mailbox server MBX4. Rep The Identity parameter specifies the mailbox database that's being copied. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -122,11 +123,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ConfigurationOnly +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -158,6 +176,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ReplayLagMaxDelay +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. + +The default value is 24:00:00 (24 hours). To disable deferred lagged copy play down, specify the value 00:00:00. + +Note that when the disk is running out of space, the value of this parameter is ignored and lagged copy play down occurs without delay. + +```yaml +Type: EnhancedTimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ReplayLagTime 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. @@ -230,57 +270,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ConfigurationOnly -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReplayLagMaxDelay -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. - -The default value is 24:00:00 (24 hours). To disable deferred lagged copy play down, specify the value 00:00:00. - -Note that when the disk is running out of space, the value of this parameter is ignored and lagged copy play down occurs without delay. - -```yaml -Type: EnhancedTimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Add-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md similarity index 80% rename from exchange/exchange-ps/exchange/mailboxes/Add-MailboxFolderPermission.md rename to exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md index 629b47253f..bda1bfce49 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Add-MailboxFolderPermission.md +++ b/exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/add-mailboxfolderpermission +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Add-MailboxFolderPermission @@ -17,19 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Add-MailboxFolderPermission cmdlet to add folder-level permissions for users in mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Add-MailboxFolderPermission [-Identity] -AccessRights - -User [-Confirm] [-DomainController ] [-WhatIf] [-SendNotificationToUser ] [-SharingPermissionFlags ] [] +Add-MailboxFolderPermission [-Identity] -AccessRights -User + [-Confirm] + [-DomainController ] + [-SendNotificationToUser ] + [-SharingPermissionFlags ] + [-WhatIf] + [] ``` ## DESCRIPTION To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet. To remove all permissions that are assigned to a user on a mailbox folder, use the Remove-MailboxFolderPermission cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,17 +49,48 @@ This example grants the Owner role to Ed on the Marketing folder in Ayla's mailb Add-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User julia@contoso.com -AccessRights Editor -SharingPermissionFlags Delegate ``` -In Office 365, this example adds Julia as a calendar delegate to Ayla's mailbox, but without access to private items. +In Exchange Online, this example adds Julia as a calendar delegate to Ayla's mailbox, but without access to private items. ### Example 3 ```powershell Add-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User laura@contoso.com -AccessRights Editor -SharingPermissionFlags Delegate,CanViewPrivateItems ``` -In Office 365, this example adds Laura as a calendar delegate to Ayla's mailbox with access to private items. +In Exchange Online, this example adds Laura as a calendar delegate to Ayla's mailbox with access to private items. ## PARAMETERS +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inbox\Reports`. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -AccessRights The AccessRights parameter specifies the permissions that you want to add for the user on the mailbox folder. @@ -63,52 +98,36 @@ You can specify individual folder permissions or roles, which are combinations o The following individual permissions are available: +- None: The user has no access to view or interact with the folder or its contents. - CreateItems: The user can create items within the specified folder. - - CreateSubfolders: The user can create subfolders in the specified folder. - - DeleteAllItems: The user can delete all items in the specified folder. - - DeleteOwnedItems: The user can only delete items that they created from the specified folder. - - EditAllItems: The user can edit all items in the specified folder. - - EditOwnedItems: The user can only edit items that they created in the specified folder. - - FolderContact: The user is the contact for the specified public folder. - - FolderOwner: The user is the owner of the specified folder. The user can view the folder, move the folder and create subfolders. The user can't read items, edit items, delete items or create items. - - FolderVisible: The user can view the specified folder, but can't read or edit items within the specified public folder. - - ReadItems: The user can read items within the specified folder. The roles that are available, along with the permissions that they assign, are described in the following list: - Author: CreateItems, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems - - Contributor: CreateItems, FolderVisible - - Editor: CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems - -- None: FolderVisible - -- NonEditingAuthor: CreateItems, FolderVisible, ReadItems - +- NonEditingAuthor: CreateItems, DeleteOwnedItems, FolderVisible, ReadItems - Owner: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderContact, FolderOwner, FolderVisible, ReadItems - -- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems - - PublishingAuthor: CreateItems, CreateSubfolders, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems - +- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems - Reviewer: FolderVisible, ReadItems The following roles apply specifically to calendar folders: - AvailabilityOnly: View only availability data - - LimitedDetails: View availability data with subject and location +When the Editor role is applied to calendar folders, delegates can accept or decline meetings by manually selecting the meeting request in the mailbox. In Exchange Online, to send meeting requests to delegates where they can accept or decline meetings, also use the SharingPermissionFlags parameter with the value Delegate. + ```yaml Type: MailboxFolderAccessRight[] Parameter Sets: (All) @@ -122,67 +141,25 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inbox\Reports`. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -User 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 - - Mail users +- Mail-enabled security groups (including nested mail-enabled security groups) -- Mail-enabled security groups +For the best results, we recommend using the following values: -You can use any value that uniquely identifies the user or group. For example: +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. -- Name +Otherwise, you can use any value that uniquely identifies the user or group. For example: +- Name - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -201,8 +178,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -236,39 +212,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -SendNotificationToUser 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: - $true: A sharing invitation is sent. - - $false: No sharing invitation is sent. This is the default value. This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values: - AvailabilityOnly - - LimitedDetails - - Reviewer - - Editor ```yaml @@ -290,13 +246,13 @@ 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: - None: Has no effect. This is the default value. - - Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. - - CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value. You can specify multiple values separated by commas. +**Note**: You can't configure the **Deliver meeting requests addressed to me and responses to meeting requests where I am the organizer to** Outlook setting in PowerShell. But, you can configure the setting using Exchange Web Services (EWS). For more information, see [MeetingRequestsDeliveryScope Enum](https://learn.microsoft.com/dotnet/api/microsoft.exchange.webservices.data.meetingrequestsdeliveryscope). + ```yaml Type: MailboxFolderPermissionFlags Parameter Sets: (All) @@ -310,19 +266,43 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 + +[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission) + +[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission) + +[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission) + +[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission) diff --git a/exchange/exchange-ps/exchange/Add-MailboxPermission.md b/exchange/exchange-ps/exchange/Add-MailboxPermission.md new file mode 100644 index 0000000000..07ab0e946e --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-MailboxPermission.md @@ -0,0 +1,459 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-MailboxPermission + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Add-MailboxPermission cmdlet to add permissions to a mailbox or to an Exchange Server 2016, Exchange Server 2019, or Exchange Online mail user. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AccessRights +``` +Add-MailboxPermission [-Identity] -AccessRights -User + [-AutoMapping ] + [-Confirm] + [-Deny] + [-DomainController ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-InheritanceType ] + [-WhatIf] + [] +``` + +### Owner +``` +Add-MailboxPermission [-Identity] -Owner + [-Confirm] + [-DomainController ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-WhatIf] + [] +``` + +### Instance +``` +Add-MailboxPermission [[-Identity] ] -Instance + [-AccessRights ] + [-User ] + [-AutoMapping ] + [-Confirm] + [-Deny] + [-DomainController ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-InheritanceType ] + [-WhatIf] + [] +``` + +## DESCRIPTION + +> [!NOTE] +> You can use this cmdlet to add a maximum of 500 permission entries (ACEs) to a mailbox. To grant permissions to more than 500 users, use security groups instead of individual users for the User parameter. Security groups contain many members, but only count as one entry. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Add-MailboxPermission -Identity "Terry Adams" -User "Kevin Kelly" -AccessRights FullAccess -InheritanceType All +``` + +This example assigns the user Kevin Kelly Full Access permission to Terry Adams's mailbox. + +### Example 2 +```powershell +Add-MailboxPermission -Identity "Room 222" -Owner "Tony Smith" +``` + +This example sets the user Tony Smith as the owner of the resource mailbox named Room 222. + +### Example 3 +```powershell +Add-MailboxPermission -Identity "Jeroen Cool" -User "Mark Steele" -AccessRights FullAccess -InheritanceType All -AutoMapping $false +``` + +This example assigns the user Mark Steele Full Access permission to Jeroen Cool's mailbox, prevents Outlook from opening Jeroen Cool's mailbox when Mark Steele opens Outlook. + +### Example 4 +```powershell +Get-Mailbox -ResultSize unlimited -Filter "(RecipientTypeDetails -eq 'UserMailbox') -and (Alias -ne 'Admin')" | Add-MailboxPermission -User admin@contoso.com -AccessRights FullAccess -InheritanceType All +``` + +In Exchange Online, this example assigns the administrator account admin@contoso.com Full Access permission to all user mailboxes in the contoso.com organization. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: AccessRights, Owner +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: 1 +Default value: None +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 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccessRights +The AccessRights parameter specifies the permission that you want to add for the user on the mailbox. Valid values are: + +- ChangeOwner +- ChangePermission +- DeleteItem +- ExternalAccount +- FullAccess +- ReadPermission + +You can specify multiple values separated by commas. + +You can't use this parameter with the Owner parameter. + +```yaml +Type: MailboxRights[] +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +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 +``` + +### -Instance +This parameter is available only in on-premises Exchange. + +This parameter has been deprecated and is no longer used. + +```yaml +Type: MailboxAcePresentationObject +Parameter Sets: Instance +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Owner +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 +- Mail users +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +The default mailbox owner is NT AUTHORITY\\SELF. + +You can't use this parameter with the AccessRights or User parameters. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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 +- Mail users +- Mail-enabled security groups (non-mail-enabled security groups are selectable, but they don't work) + +**Note**: When a mail-enabled security group is used to specify Full Access permissions, the auto-mapping feature won't automatically add the mailbox in Outlook for the group member. For more information, see [Mailboxes to which your account has full access aren't automapped to Outlook profile](https://learn.microsoft.com/outlook/troubleshoot/profiles-and-accounts/full-access-mailbox-not-automapped-outlook-profile). + +For the best results, we recommend using the following values: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Owner parameter. + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +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 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoMapping +The AutoMapping parameter includes or excludes the mailbox from the auto-mapping feature in Microsoft Outlook. Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. However, Autodiscover won't enumerate security groups that are given Full Access permission to the mailbox. Valid values are: + +- $true: The mailbox is automatically added to the user's Outlook profile if the user has Full Access permission. This is the default value. +- $false: The mailbox is not automatically added to the user's Outlook profile if the user has Full Access permission. + +**Note**: To disable auto-mapping for a mailbox where the user was already assigned Full Access permission, you need to remove the user's Full Access permission by using the Remove-MailboxPermission cmdlet, and then reassign the user Full Access permission on the mailbox using the AutoMapping parameter with the value $false. + +```yaml +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 +Default value: $true +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Deny +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +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. + +```yaml +Type: SwitchParameter +Parameter Sets: AccessRights, Owner, Instance +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InheritanceType +The InheritanceType parameter specifies how permissions are inherited by folders in the mailbox. Valid values are: + +- None +- All (this is the default value) +- Children +- Descendents [sic] +- SelfAndChildren + +```yaml +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 +Default value: All +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/role-based-access-control/Add-ManagementRoleEntry.md b/exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md similarity index 87% rename from exchange/exchange-ps/exchange/role-based-access-control/Add-ManagementRoleEntry.md rename to exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md index d934409ffd..6b98323cb7 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Add-ManagementRoleEntry.md +++ b/exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/add-managementroleentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Add-ManagementRoleEntry @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Add-ManagementRoleEntry cmdlet to add management role entries to an existing management role. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,7 +31,8 @@ Add-ManagementRoleEntry [-Identity] [-PSSnapinName ] [-Type ] [-UnScopedTopLevel] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ParentRoleEntry @@ -42,7 +42,8 @@ Add-ManagementRoleEntry [-ParentRoleEntry] -Role ] [-Force] [-Overwrite] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -50,9 +51,9 @@ The cmdlet and its parameters that you add to a role entry must exist in the par You can only add a role entry to a management role if the role entry exists in the role's parent role. For example, if you try to add the Search-Mailbox role entry to a role that's a child of the Mail Recipients role, you'll receive an error. This error occurs because the Search-Mailbox role entry doesn't exist in the Mail Recipients role. To add the Search-Mailbox role entry to a role, you need to create a role that's a child of the Mailbox Import Export role, which contains the Search-Mailbox role entry. Then you can use the Add-ManagementRoleEntry cmdlet to add the Search-Mailbox role entry to the new child role. -For more information about management role entries, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,9 +88,9 @@ In on-premises Exchange, this example adds the MailboxAudit script with the Depa ## PARAMETERS ### -Identity -The Identity parameter specifies the role entry to add. You must specify the value of the Identity parameter in the format: \\\\, for example, ExampleRole\\Set-Mailbox. +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://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about how management role entries work, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). The role entry you want to add must exist in the parent role. If the role entry name contains spaces, you must enclose the name in quotation marks ("). @@ -141,8 +142,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -179,7 +179,9 @@ Accept wildcard characters: False ### -Force This parameter is available only in the cloud-based service. -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. +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. ```yaml Type: SwitchParameter @@ -195,7 +197,7 @@ Accept wildcard characters: False ``` ### -Overwrite -The Overwrite parameter causes existing role entries to be overwritten by the role entries being added. +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 @@ -261,13 +263,13 @@ Accept wildcard characters: False ``` ### -UnScopedTopLevel -This parameter is available on in on-premises Exchange. +This parameter is available only in on-premises Exchange. -By default, this parameter is only available 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +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). The UnScopedTopLevel switch specifies that you're adding the role entry to an unscoped top-level management role. You don't need to specify a value with this switch. -Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. For more information, see [Create an unscoped role](https://docs.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). +Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. For more information, see [Create an unscoped role](https://learn.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). You can't use this switch with the ParentRoleEntry parameter. @@ -305,12 +307,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Add-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md similarity index 81% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Add-PublicFolderAdministrativePermission.md rename to exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md index 43a92dc37d..153ba0c086 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Add-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/add-publicfolderadministrativepermission +online version: https://learn.microsoft.com/powershell/module/exchange/add-publicfolderadministrativepermission applicable: Exchange Server 2010 title: Add-PublicFolderAdministrativePermission schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Add-PublicFolderAdministrativePermission @@ -17,32 +16,34 @@ This cmdlet is available only in Exchange Server 2010. Use the Add-PublicFolderAdministrativePermission cmdlet to add administrative permissions to a public folder or a public folder hierarchy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` Add-PublicFolderAdministrativePermission [-Identity] -AccessRights -User - [-Confirm] [-Deny] + [-Confirm] + [-Deny] [-DomainController ] [-InheritanceType ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Instance ``` -Add-PublicFolderAdministrativePermission -Instance +Add-PublicFolderAdministrativePermission [[-Identity] ] -Instance [-AccessRights ] [-User ] [-Confirm] [-Deny] [-DomainController ] - [[-Identity] ] [-InheritanceType ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Owner @@ -51,11 +52,12 @@ Add-PublicFolderAdministrativePermission [-Identity] - [-Confirm] [-DomainController ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -75,83 +77,78 @@ This example denies the user Chris the ViewInformationStore permission. ## PARAMETERS -### -AccessRights -The AccessRights parameter specifies the rights that are being added. Valid values include: - -- None The administrator has no rights to modify public folder attributes. - -- ModifyPublicFolderACL The administrator has the right to modify client access permissions for the specified folder. - -- ModifyPublicFolderAdminACL The administrator has the right to modify administrator permissions for the specified public folder. - -- ModifyPublicFolderDeletedItemRetention The administrator has the right to modify the Public Folder Deleted Item Retention attributes (RetainDeletedItemsFor and UseDatabaseRetentionDefaults). - -- ModifyPublicFolderExpiry The administrator has the right to modify the Public Folder Expiration attributes (AgeLimit and UseDatabaseAgeDefaults). - -- ModifyPublicFolderQuotas The administrator has the right to modify the Public Folder Quota attributes (MaxItemSize, PostQuota, PostWarningQuota, and UseDatabaseQuotaDefaults) - -- ModifyPublicFolderReplicaList The administrator has the right to modify the replica list attribute for the specified public folder (Replicas). - -- AdministerInformationStore The administrator has the right to modify all other public folder properties that aren't defined previously. - -- ViewInformationStore The administrator has the right to view public folder properties. +### -Identity +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. -- AllExtendedRights The administrator has the right to modify all public folder properties. +You can omit the parameter label so that only the public folder name or GUID is supplied. ```yaml -Type: MultiValuedProperty -Parameter Sets: Identity +Type: PublicFolderIdParameter +Parameter Sets: Identity, Owner Aliases: Applicable: Exchange Server 2010 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` ```yaml -Type: MultiValuedProperty +Type: PublicFolderIdParameter Parameter Sets: Instance Aliases: Applicable: Exchange Server 2010 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -AccessRights +The AccessRights parameter specifies the rights that you want to add for the administrator on the public folder. Valid values include: -You can omit the parameter label so that only the public folder name or GUID is supplied. +- None The administrator has no rights to modify public folder attributes. +- ModifyPublicFolderACL The administrator has the right to modify client access permissions for the specified folder. +- ModifyPublicFolderAdminACL The administrator has the right to modify administrator permissions for the specified public folder. +- ModifyPublicFolderDeletedItemRetention The administrator has the right to modify the Public Folder Deleted Item Retention attributes (RetainDeletedItemsFor and UseDatabaseRetentionDefaults). +- ModifyPublicFolderExpiry The administrator has the right to modify the Public Folder Expiration attributes (AgeLimit and UseDatabaseAgeDefaults). +- ModifyPublicFolderQuotas The administrator has the right to modify the Public Folder Quota attributes (MaxItemSize, PostQuota, PostWarningQuota, and UseDatabaseQuotaDefaults) +- ModifyPublicFolderReplicaList The administrator has the right to modify the replica list attribute for the specified public folder (Replicas). +- AdministerInformationStore The administrator has the right to modify all other public folder properties that aren't defined previously. +- ViewInformationStore The administrator has the right to view public folder properties. +- AllExtendedRights The administrator has the right to modify all public folder properties. + +You can specify multiple values separated by commas. + +You can't use this parameter with the Owner parameter. ```yaml -Type: PublicFolderIdParameter -Parameter Sets: Identity, Owner +Type: MultiValuedProperty +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ```yaml -Type: PublicFolderIdParameter +Type: MultiValuedProperty Parameter Sets: Instance Aliases: Applicable: Exchange Server 2010 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -172,7 +169,26 @@ Accept wildcard characters: False ``` ### -Owner -The Owner parameter specifies the NT Owner access control list (ACL) on the object. Valid values are the user principal name (UPN), domain\\user, or alias. +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 +- Mail users +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the AccessRights or User parameters. ```yaml Type: SecurityPrincipalIdParameter @@ -188,7 +204,26 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the UPN, domain\\user, or alias of the user for whom rights are being added. +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 +- Mail users +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Owner parameter. ```yaml Type: SecurityPrincipalIdParameter @@ -219,8 +254,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -237,7 +271,7 @@ Accept wildcard characters: False ``` ### -Deny -The Deny switch specifies whether to deny the permission specified. You don't need to specify a value with this switch. +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 @@ -269,17 +303,13 @@ Accept wildcard characters: False ``` ### -InheritanceType -The InheritanceType parameter specifies the type of inheritance. Valid values are: +The InheritanceType parameter specifies how permissions are inherited. Valid values are: - None - -- All - -- Descendents - -- SelfAndChildren - +- All (this is the default value) - Children +- Descendents [sic] +- SelfAndChildren ```yaml Type: ActiveDirectorySecurityInheritance @@ -298,11 +328,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -341,12 +368,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md similarity index 80% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Add-PublicFolderClientPermission.md rename to exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md index eb8ac7e15f..059bc10445 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Add-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/add-publicfolderclientpermission +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Add-PublicFolderClientPermission @@ -17,18 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Add-PublicFolderClientPermission cmdlet to add permissions to public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Add-PublicFolderClientPermission [-Identity] -AccessRights - -User [-Confirm] [-DomainController ] [-Server ] - [-WhatIf] [] +Add-PublicFolderClientPermission [-Identity] -AccessRights -User + [-Confirm] + [-DomainController ] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,48 +50,53 @@ This example adds permission for the user Chris to create items in the public fo ## PARAMETERS -### -AccessRights -The AccessRights parameter specifies the rights being added. This parameter accepts the following values: +### -Identity +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. -- ReadItems: The user has the right to read items within the specified public folder. +You can omit the parameter label so that only the public folder name or GUID is supplied. -- CreateItems: The user has the right to create items within the specified public folder. +```yaml +Type: PublicFolderIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -- EditOwnedItems: The user has the right to edit the items that the user owns in the specified public folder. +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` -- DeleteOwnedItems: The user has the right to delete items that the user owns in the specified public folder. +### -AccessRights +The AccessRights parameter specifies the rights that you want to add for the user on the public folder. -- EditAllItems: The user has the right to edit all items in the specified 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. -- DeleteAllItems: The user has the right to delete all items in the specified public folder. +The following individual permissions are available: +- CreateItems: The user has the right to create items within the specified public folder. - CreateSubfolders: The user has the right to create subfolders in the specified public folder. - -- FolderOwner: The user is the owner of the specified public folder. The user has the right to view and move the public folder and create subfolders. The user can't read items, edit items, delete items, or create items. - +- DeleteAllItems: The user has the right to delete all items in the specified public folder. +- DeleteOwnedItems: The user has the right to delete items that the user owns in the specified public folder. +- EditAllItems: The user has the right to edit all items in the specified public folder. +- EditOwnedItems: The user has the right to edit the items that the user owns in the specified public folder. - FolderContact: The user is the contact for the specified public folder. - +- FolderOwner: The user is the owner of the specified public folder. The user has the right to view and move the public folder and create subfolders. The user can't read items, edit items, delete items, or create items. - FolderVisible: The user can view the specified public folder, but can't read or edit items within the specified public folder. +- ReadItems: The user has the right to read items within the specified public folder. In addition to access rights, you can create rights based upon roles, which includes multiple access rights. This parameter accepts the following values for roles: -- None: FolderVisible - -- Owner: CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems - -- PublishingEditor: CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems - -- Editor: CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems - -- PublishingAuthor: CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems - -- Author: CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems - -- NonEditingAuthor: CreateItems, ReadItems, FolderVisible - -- Reviewer: ReadItems, FolderVisible - +- Author: CreateItems, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems - Contributor: CreateItems, FolderVisible +- Editor: CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems +- None: FolderVisible +- NonEditingAuthor: CreateItems, DeleteOwnedItems, FolderVisible, ReadItems +- Owner: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderContact, FolderOwner, FolderVisible, ReadItems +- PublishingAuthor: CreateItems, CreateSubfolders, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems +- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems +- Reviewer: FolderVisible, ReadItems ```yaml Type: MultiValuedProperty @@ -104,26 +111,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -User +The User parameter specifies the user for whom rights are being added. -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +For the best results, we recommend using the following values: -### -User -The User parameter specifies the user principal name (UPN), domain\\user, or alias of the user for whom rights are being added. +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. ```yaml Type: PublicFolderUserIdParameter @@ -141,8 +135,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -177,16 +170,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available only in on-premises Exchange 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -225,12 +215,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Add-RecipientPermission.md b/exchange/exchange-ps/exchange/Add-RecipientPermission.md new file mode 100644 index 0000000000..06dfc9280a --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-RecipientPermission.md @@ -0,0 +1,180 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-RecipientPermission + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Add-RecipientPermission cmdlet to add SendAs permission to users in a cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Add-RecipientPermission [-Identity] -AccessRights -Trustee + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +SendAs permission allows a user or group members to send messages that appear to come from the specified mailbox, mail contact, mail user, or group. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Add-RecipientPermission "Help Desk" -AccessRights SendAs -Trustee "Ayla Kol" +``` + +This example gives the user Ayla Kol SendAs permission for the mailbox Help Desk. Ayla can send messages that appear to come directly from the Help Desk mailbox. + +## PARAMETERS + +### -Identity +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: + +- Mailboxes +- Mail users +- External contacts +- Distribution groups +- Dynamic distribution groups + +You can use any value that uniquely identifies the recipient. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccessRights +The AccessRights parameter specifies the permission that you want to add for the 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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Trustee +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 +- Mail users with a Microsoft account +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mail-flow/Add-ResubmitRequest.md b/exchange/exchange-ps/exchange/Add-ResubmitRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/mail-flow/Add-ResubmitRequest.md rename to exchange/exchange-ps/exchange/Add-ResubmitRequest.md index fa8d1af08f..d1801a114d 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Add-ResubmitRequest.md +++ b/exchange/exchange-ps/exchange/Add-ResubmitRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/add-resubmitrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-ResubmitRequest @@ -17,34 +16,41 @@ This cmdlet is available only in on-premises Exchange. Use the Add-ResubmitRequest cmdlet to add requests to replay redundant copies of messages from Safety Net after a mailbox database recovery. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### MDBResubmit ``` -Add-ResubmitRequest -EndTime -StartTime [-Destination ] +Add-ResubmitRequest -EndTime -StartTime + [-Destination ] [-Confirm] [-CorrelationId ] [-Server ] [-TestOnly ] [-UnresponsivePrimaryServers ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ConditionalResubmit ``` -Add-ResubmitRequest -EndTime -StartTime [-MessageId ] [-Recipient ] [-ResubmitTo ] [-Sender ] +Add-ResubmitRequest -EndTime -StartTime + [-MessageId ] + [-Recipient ] + [-ResubmitTo ] + [-Sender ] [-Confirm] [-CorrelationId ] [-Server ] [-TestOnly ] [-UnresponsivePrimaryServers ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,7 +66,7 @@ This example replays the redundant copies of messages delivered from 6:00 PM Jun ### -EndTime 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". +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". The date and time specified by the EndTime parameter must be later than the date and time specified by the StartTime parameter. The date and time specified by both parameters must be in the past. @@ -80,7 +86,7 @@ Accept wildcard characters: False ### -StartTime 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". +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". The date and time specified by the StartTime parameter must be earlier than the date and time specified by the EndTime parameter. The date and time specified by both parameters must be in the past. @@ -100,8 +106,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -134,7 +139,7 @@ Accept wildcard characters: False ``` ### -Destination -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. +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. @@ -223,11 +228,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -298,12 +300,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Add-RoleGroupMember.md b/exchange/exchange-ps/exchange/Add-RoleGroupMember.md new file mode 100644 index 0000000000..5f64ff5636 --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-RoleGroupMember.md @@ -0,0 +1,216 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-RoleGroupMember + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Add-RoleGroupMember cmdlet to add members to a management role group. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Add-RoleGroupMember [-Identity] -Member + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +When you add a member to a role group, the member is given the effective permissions provided by the management roles assigned to the role group. + +If the ManagedBy property has been populated with role group managers, the user adding a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. + +In on-premises Exchange, if the role group is a linked role group, you can't use the Add-RoleGroupMember cmdlet to add members to the role group. Instead, you need to add members to the foreign universal security group (USG) that's linked to the linked role group. To find the foreign USG that's linked to a role group, use the Get-RoleGroup cmdlet. + +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Add-RoleGroupMember "Recipient Management" -Member David +``` + +This example adds the user David to the role group Recipient Management. + +### Example 2 +```powershell +Get-User -Filter "Department -eq 'Sales' -and RecipientType -eq 'UserMailbox'" | Get-Mailbox | Add-RoleGroupMember "Sales and Marketing Group" -WhatIf +``` + +This example finds all the mailboxes that are part of the Sales department and adds them to the Sales and Marketing Group role group. Because we're using the WhatIf switch, the changes aren't written to the role group, so you can verify that the correct members will be added. + +After you've verified that the correct members will be added to the role group, remove the WhatIf switch and run the command again. + +For more information about pipelining and the WhatIf parameter, see the following topics: + +- [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) +- [WhatIf, Confirm and ValidateOnly switches](https://learn.microsoft.com/exchange/whatif-confirm-and-validateonly-switches-exchange-2013-help) + +### Example 3 +```powershell +Add-RoleGroupMember "Training Administrators" -Member "Training Assistants" -BypassSecurityGroupManagerCheck +``` + +This example adds the Training Assistants USG to the Training Administrators role group. Because the user running the command wasn't added to the ManagedBy property of the role group, the BypassSecurityGroupManagerCheck switch must be used. The user is assigned the Role Management role, which enables the user to bypass the security group manager check. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Member +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 +- Mail users +- Mail-enabled security groups +- Security groups (on-premises Exchange only) + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BypassSecurityGroupManagerCheck +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: + +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +- Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/server-health-and-performance/Add-ServerMonitoringOverride.md b/exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md similarity index 89% rename from exchange/exchange-ps/exchange/server-health-and-performance/Add-ServerMonitoringOverride.md rename to exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md index 38edbb9b20..97858e26e8 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Add-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/add-servermonitoringoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Add-ServerMonitoringOverride @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Add-ServerMonitoringOverride cmdlet to override the thresholds and parameters of managed availability probes, monitors, and responders on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,18 +24,21 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Add-ServerMonitoringOverride [-Identity] -ApplyVersion -ItemType -PropertyName -PropertyValue -Server [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Duration ``` -Add-ServerMonitoringOverride [-Identity] -ItemType -PropertyName -PropertyValue -Server [-Duration ] +Add-ServerMonitoringOverride [-Identity] -ItemType -PropertyName -PropertyValue -Server + [-Duration ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,39 +51,39 @@ This example adds a server monitoring override that disables the responder Activ ## PARAMETERS -### -ApplyVersion -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. +### -Identity +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't use this parameter with the Duration parameter. +You can use Get-ServerHealth to find the correct object for the monitoring item you want to override. ```yaml -Type: Version -Parameter Sets: ApplyVersion +Type: String +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identity of the monitoring item that you want to override. This parameter uses the syntax \\\\[\\\]. Note that the values are case sensitive. For example, use "AD\\ActiveDirectoryConnectivityConfigDCServerReboot", not "ad\\activedirectoryconnectivityconfigdcserverreboot". +### -ApplyVersion +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. -You can use Get-ServerHealth to find the correct object for the monitoring item you want to override. +Valid input for this parameter is an Exchange version number in the format 15.01.xxxx.xxx. + +You can't use this parameter with the Duration parameter. ```yaml -Type: String -Parameter Sets: (All) +Type: Version +Parameter Sets: ApplyVersion Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -91,9 +93,7 @@ Accept wildcard characters: False The ItemType parameter specifies the server item type for the property that you want to override. Valid value are: - Probe - - Monitor - - Responder ```yaml @@ -145,11 +145,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use this parameter to configure other Edge Transport servers remotely. @@ -170,8 +167,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -230,12 +226,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md new file mode 100644 index 0000000000..e58e810aba --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md @@ -0,0 +1,184 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-UnifiedGroupLinks + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Add-UnifiedGroupLinks cmdlet to add members, owners and subscribers to Microsoft 365 Groups in your cloud-based organization. To remove members, owners, and subscribers, use the Remove-UnifiedGroupLinks cmdlet. To modify other properties of Microsoft 365 Groups, use the Set-UnifiedGroup cmdlet. + +> [!NOTE] +> You can't use this cmdlet to modify Microsoft 365 Group members, owners, or subscribers if you connect using certificate based authentication (also known as CBA or app-only authentication for unattended scripts) or Azure managed identity. You can use Microsoft Graph instead. For more information, see [Group resource type](https://learn.microsoft.com/graph/api/resources/group). +> +> Using this cmdlet, only group members can be owners of the group. Add users as members before you add them as owners. This limitation doesn't apply in web management portals where you can add non-members as group owners. Guest users can never be group owners. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Add-UnifiedGroupLinks [-Identity] -Links -LinkType + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +**Note**: Only members can be owners of a group, so you must first add a user as member before adding it as an owner. Guest users cannot be an owner of groups, even if the users are members of the groups. + +## EXAMPLES + +### Example 1 +```powershell +Add-UnifiedGroupLinks -Identity "Legal Department" -LinkType Members -Links chris@contoso.com,michelle@contoso.com +``` + +This example adds members `chris@contoso.com` and `michelle@contoso.com` to the Microsoft 365 Group named Legal Department. + +### Example 2 +```powershell +$users= Get-User -ResultSize unlimited | where {$_.Department -eq "Marketing" -AND $_.RecipientType -eq "UserMailbox"} + +Add-UnifiedGroupLinks -Identity Marketing -LinkType members -Links ($users.UserPrincipalName) +``` + +This example shows how to add bulk members to a Microsoft 365 Group. Mailboxes where the Department attribute is "Marketing" are added to Microsoft 365 Group named Marketing. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: UnifiedGroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Links +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +You must use this parameter with the LinkType parameter, which means the specified recipients receive the same role in the Microsoft 365 Group (you can't add recipients with different roles in the same command). + +**Note**: Using this cmdlet, only group members can be owners of the group. Add users as members before you add them as owners. This limitation doesn't apply in web management portals where you can add non-members as group owners. Guest users can never be group owners. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LinkType +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. +- Owners: Add or remove members, delete conversations, changes Team settings, delete the Team, and full control of the connected SharePoint site. A group must have at least one owner. +- Subscribers: Existing group members who receive conversation and calendar event notifications from the group. All subscribers are members of the group, but all members aren't necessarily subscribers (depending on the AutoSubscribeNewMembers property value of the group and when the member was added). + +You must use this parameter with the Links parameter. + +**Note**: Using this cmdlet, only group members can be owners of the group. Add users as members before you add them as owners. This limitation doesn't apply in web management portals where you can add non-members as group owners. Guest users can never be group owners. + +```yaml +Type: LinkType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md new file mode 100644 index 0000000000..340921a576 --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md @@ -0,0 +1,344 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-VivaModuleFeaturePolicy + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Add-VivaModuleFeaturePolicy cmdlet to add a new access policy for a specific feature in Viva. The attributes of the policy are defined using the cmdlet parameters. Policies are used to restrict or grant access to the specified feature for specific users, groups, or the entire tenant. + +- You can assign up to 10 policies per feature. An additional one policy per feature can be assigned to the entire tenant. +- Policies assigned to a specific user or group take priority over the policy assigned to the entire tenant when determining whether a feature is enabled. If a user has multiple policies assigned for a feature (directly as a user or member of a group), the most restrictive policy applies. +- Some features only support policies that apply to the entire tenant, not specific users or groups. You can refer to supported policy scopes for a feature using the [Get-VivaModuleFeature](https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeature) cmdlet. + +Some features include the option for user controls (user opt out). Refer to the feature documentation to see if user controls are available for the feature that you intend to set a policy for. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX +``` +Add-VivaModuleFeaturePolicy -FeatureId -IsFeatureEnabled -ModuleId -Name + [-Confirm] + [-Everyone] + [-GroupIds ] + [-IsUserControlEnabled ] + [-IsUserOptedInByDefault ] + [-ResultSize ] + [-UserIds ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the Add-VivaModuleFeaturePolicy cmdlet to add a new access policy for a specific feature in Viva. + +You need to use the Connect-ExchangeOnline cmdlet to authenticate. + +This cmdlet requires the .NET Framework 4.7.2 or later. + +Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. + +To learn more about assigned roles at the feature level, see [Features Available for Feature Access Management](https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Add-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -Name DisableFeatureForAll -IsFeatureEnabled $false -Everyone +``` + +This example adds a policy for the Reflection feature in Viva Insights. The policy disables the feature for all users in the organization. + +### Example 2 +```powershell +Add-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -Name MultipleGroups -IsFeatureEnabled $false -GroupIds group1@contoso.com,group2@contoso.com,57680382-61a5-4378-85ad-f72095d4e9c3 +``` + +This example adds a policy for the Reflection feature in Viva Insights. The policy disables the feature for all users in the specified groups. + +### Example 3 +```powershell +Add-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -Name MultipleUsers -IsFeatureEnabled $false -UserIds user1@contoso.com,user2@contoso.com +``` + +This example adds a policy for the Reflection feature in Viva Insights. The policy disables the feature for the specified users. + +### Example 4 +```powershell +Add-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -Name UsersAndGroups -IsFeatureEnabled $false -GroupIds group1@contoso.com,group2@contoso.com,57680382-61a5-4378-85ad-f72095d4e9c3 -UserIds user1@contoso.com,user2@contoso.com +``` + +This example adds a policy for the Reflection feature in Viva Insights. The policy disables the feature for the specified users and group members. + +### Example 5 +```powershell +Add-VivaModuleFeaturePolicy -ModuleId PeopleSkills -FeatureId ShowAISkills -Name SoftDisableShowAISkillsPolicy -IsFeatureEnabled $true -IsUserControlEnabled $true -IsUserOptedInByDefault $false -UserIds user1@contoso.com,user2@contoso.com +``` + +This example adds a policy for the ShowAISkills feature in Viva Skills. The policy enables the feature for the specified users, allows user controls, and opted out users by default (Soft Disable policy). + +## PARAMETERS + +### -FeatureId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsFeatureEnabled +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. +- $false: The feature is not enabled by the policy. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModuleId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Everyone +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupIds +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.). + +To have the policy apply to all users in the organization, use the Everyone switch. + +**Note**: In v3.5.1-Preview2 or later of the module, this parameter supports security group object IDs (GUIDs). Previous versions of the module accept only email addresses for this parameter. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsUserControlEnabled +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: + +- $true: User control is enabled by the policy. Users can opt out of the feature. +- $false: User control isn't enabled by the policy. Users can't opt of the feature. + +Only features that allow admins to enable and disable user controls by policy can use this parameter. If the feature doesn't support admins toggling user controls, the default value applies. See the feature documentation for more information. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsUserOptedInByDefault +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: + +- $true: By default, users are opted in by the policy if the user hasn't set a preference. +- $false: By default, users are opted out by the policy if the user hasn't set a preference. + +This parameter is optional and can be used to override the default user opt-in value set in the feature metadata. + +This parameter can be set only when the IsUserControlEnabled parameter is set to $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIds +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.). + +To have the policy apply to all users in the organization, use the Everyone switch. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Exchange PowerShell](https://learn.microsoft.com/powershell/module/exchange) + +[About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2) + +[Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids) diff --git a/exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md new file mode 100644 index 0000000000..0bd5527745 --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md @@ -0,0 +1,110 @@ +--- +external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml +Module Name: ExchangeOnlineManagement +online version: https://learn.microsoft.com/powershell/module/exchange/add-vivaorginsightsdelegatedrole +title: Add-VivaOrgInsightsDelegatedRole +schema: 2.0.0 +author: chrisda +ms.author: chrisda +ms.reviewer: +--- + +# Add-VivaOrgInsightsDelegatedRole + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.7.1 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Add-VivaOrgInsightsDelegatedRole cmdlet to add delegate access to the specified account (the delegate) so they can view organizational insights like the leader (the delegator). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Add-VivaOrgInsightsDelegatedRole -Delegate -Delegator + [-ResultSize ] + [] +``` + +## DESCRIPTION +To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: + +- Global Administrator +- Insights Administrator + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Add-VivaOrgInsightsDelegatedRole -Delegate 5eaf7164-f36f-5381-5546-dcaa1792f077 -Delegator 043f6d38-378b-7dcd-7cd8-c1a901881fa9 +``` + +This example adds the organization insights viewing capability of the specified delegator account to the specified delegate account. + +## PARAMETERS + +### -Delegate +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Delegator +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md new file mode 100644 index 0000000000..ddb6eb30ff --- /dev/null +++ b/exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md @@ -0,0 +1,113 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Add-eDiscoveryCaseAdmin + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Add-eDiscoveryCaseAdmin cmdlet to add an eDiscovery Administrator in the Microsoft Purview compliance portal. To replace all existing eDiscovery Administrators, use the Update-eDiscoveryCaseAdmin cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Add-eDiscoveryCaseAdmin -User + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +An eDiscovery Administrator is a member of the eDiscovery Manager role group who can view and access all eDiscovery cases in the organization. To make a user an eDiscovery Administrator, add them to the eDiscovery Manager role group by running the following command in Security & Compliance PowerShell: `Add-RoleGroupMember -Identity "eDiscovery Manager" -Member ""`. + +After the user is a member of the eDiscovery Manager role group, you can then use this cmdlet to add them to the list of eDiscovery Administrators. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Add-eDiscoveryCaseAdmin -User michelle@contoso.com +``` + +This example adds an eDiscovery Administrator. + +## PARAMETERS + +### -User +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Clean-MailboxDatabase.md b/exchange/exchange-ps/exchange/Clean-MailboxDatabase.md similarity index 91% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Clean-MailboxDatabase.md rename to exchange/exchange-ps/exchange/Clean-MailboxDatabase.md index be6fe8168f..9e3829eb4e 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Clean-MailboxDatabase.md +++ b/exchange/exchange-ps/exchange/Clean-MailboxDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/clean-mailboxdatabase +online version: https://learn.microsoft.com/powershell/module/exchange/clean-mailboxdatabase applicable: Exchange Server 2010 title: Clean-MailboxDatabase schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Clean-MailboxDatabase @@ -17,12 +16,15 @@ This cmdlet is available only in Exchange Server 2010. Use the Clean-MailboxDatabase cmdlet to scan Active Directory for disconnected mailboxes that aren't yet marked as disconnected in the Microsoft Exchange store and update the status of those mailboxes in the Exchange store. This cmdlet isn't able to update the Exchange store unless the Microsoft Exchange Information Store service is running and the database is mounted. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Clean-MailboxDatabase [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Clean-MailboxDatabase [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -33,7 +35,7 @@ If you want to reconnect a disconnected mailbox to an Active Directory user acco Under normal circumstances, it isn't necessary to run the Clean-MailboxDatabase cmdlet because a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. If you used the Disable-Mailbox cmdlet or the Remove-Mailbox cmdlet while the Microsoft Exchange Information Store service was stopped, or if a mailbox was disabled by an external means other than the Disable-Mailbox cmdlet or Remove-Mailbox cmdlet, you may want to use the Clean-MailboxDatabase cmdlet to scan for disconnected mailboxes. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,9 +52,7 @@ This example cleans the mailbox database MBD01. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -71,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -127,12 +126,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/devices/Clear-ActiveSyncDevice.md b/exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md similarity index 86% rename from exchange/exchange-ps/exchange/devices/Clear-ActiveSyncDevice.md rename to exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md index 76304c1224..f729195ad5 100644 --- a/exchange/exchange-ps/exchange/devices/Clear-ActiveSyncDevice.md +++ b/exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/clear-activesyncdevice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Clear-ActiveSyncDevice @@ -17,15 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Clear-ActiveSyncDevice cmdlet to delete all data from a mobile device. -Note: In Exchange 2013 or later, use the Clear-MobileDevice cmdlet instead. If you have scripts that use Clear-ActiveSyncDevice, update them to use Clear-MobileDevice. +**Note**: In Exchange 2013 or later, use the Clear-MobileDevice cmdlet instead. If you have scripts that use Clear-ActiveSyncDevice, update them to use Clear-MobileDevice. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Clear-ActiveSyncDevice [-Identity] [-Cancel] [-Confirm] - [-DomainController ] [-NotificationEmailAddresses ] [-WhatIf] [] +Clear-ActiveSyncDevice [-Identity] + [-Cancel] + [-Confirm] + [-DomainController ] + [-NotificationEmailAddresses ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -33,7 +37,7 @@ The Clear-ActiveSyncDevice cmdlet deletes all user data from a mobile device the After you run this cmdlet, you receive a warning that states: "This command will force all the data on the device to be permanently deleted. Do you want to continue?" You must respond to the warning for the cmdlet to run on the mobile phone. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,7 +81,7 @@ Accept wildcard characters: False ``` ### -Cancel -The Cancel switch specifies whether the command should be canceled. If you use the Cancel switch, a cancellation request is issued for the remote device wipe. +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 @@ -95,10 +99,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -131,7 +136,7 @@ Accept wildcard characters: False ``` ### -NotificationEmailAddresses -The NotificationEmailAddresses parameter specifies the notification email address for the remote device wipe confirmation. +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 @@ -167,12 +172,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Clear-MobileDevice.md b/exchange/exchange-ps/exchange/Clear-MobileDevice.md similarity index 77% rename from exchange/exchange-ps/exchange/devices/Clear-MobileDevice.md rename to exchange/exchange-ps/exchange/Clear-MobileDevice.md index 4b404fbdb3..9a5eda7425 100644 --- a/exchange/exchange-ps/exchange/devices/Clear-MobileDevice.md +++ b/exchange/exchange-ps/exchange/Clear-MobileDevice.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/clear-mobiledevice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Clear-MobileDevice @@ -17,13 +16,19 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Clear-MobileDevice cmdlet to delete all data from a mobile phone. This action is often called a remote device wipe. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Clear-MobileDevice [-Identity] [-Cancel] [-Confirm] [-DomainController ] - [-NotificationEmailAddresses ] [-WhatIf] [-AccountOnly] [] +Clear-MobileDevice [-Identity] + [-AccountOnly] + [-Cancel] + [-Confirm] + [-DomainController ] + [-NotificationEmailAddresses ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,39 +36,39 @@ The Clear-MobileDevice cmdlet deletes all user data from a mobile device the nex After you run this cmdlet, you receive a warning that states: "This command will force all the data on the device to be permanently deleted. Do you want to continue?" You must respond to the warning for the cmdlet to run on the mobile phone. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Clear-MobileDevice -Identity WM_JeffHay +Clear-MobileDevice -Identity TonySmith\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac ``` -This example clears all data from the mobile device with the Identity WM\_JeffHay. +This example clears all data from the specified mobile device. ### Example 2 ```powershell -Clear-MobileDevice -Identity WM_TonySmith -NotificationEmailAddresses "tony@contoso.com" +Clear-MobileDevice -Identity TonySmith\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac -NotificationEmailAddresses "chris@contoso.com" ``` -This example clears all data from the mobile device for Tony Smith and sends a confirmation email message to tony@contoso.com. +This example clears all data from the specified mobile device and sends a confirmation email message to chris@contoso.com. ### Example 3 ```powershell -Clear-MobileDevice -Identity WM_TonySmith -Cancel +Clear-MobileDevice -Identity TonySmith\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac -Cancel ``` -This example cancels a previously sent Clear-MobileDevice command request for Tony Smith's mobile device. +This example cancels a previously sent Clear-MobileDevice command request for the specified mobile device. ## PARAMETERS ### -Identity -The Identity parameter specifies the mobile device that you want to reset. You can use any value that uniquely identifies the mobile device. For example: +The Identity parameter specifies the mobile device that you want to reset. You can use the following values that uniquely identifies the mobile device: -- GUID - -- DeviceID +- Identity (`\ExchangeActiveSyncDevices\` for example, `CarlosM\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac`) +- Distinguished name (DN) +- GUID (same as ExchangeObjectId) ```yaml Type: MobileDeviceIdParameter @@ -78,8 +83,26 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -AccountOnly +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Cancel -The Cancel switch cancels a pending remote device wipe request. You don't need to specify a value with this switch. +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 @@ -97,10 +120,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -164,35 +188,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AccountOnly -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 devices wipe is the only type of wipe that's used on Outlook devices. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Clear-TextMessagingAccount.md b/exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access/Clear-TextMessagingAccount.md rename to exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md index 1dd905b510..0cfbdb03d1 100644 --- a/exchange/exchange-ps/exchange/client-access/Clear-TextMessagingAccount.md +++ b/exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/clear-textmessagingaccount +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Clear-TextMessagingAccount @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. The Clear-TextMessagingAccount cmdlet allows a user to remove the text messaging settings from their own mailbox. An administrator can't use this cmdlet to remove the text messaging settings from another user's mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,13 +25,14 @@ Clear-TextMessagingAccount [-Identity] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Clear-TextMessagingAccount cmdlet clears all of a user's text messaging settings, including communication and notification settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,23 +49,14 @@ This example clears the text messaging account settings and notification setting The Identity parameter specifies the target mailbox. You can any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -84,8 +75,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -120,12 +110,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -162,12 +151,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md similarity index 90% rename from exchange/exchange-ps/exchange/client-access/Compare-TextMessagingVerificationCode.md rename to exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md index 760597a845..c536c48908 100644 --- a/exchange/exchange-ps/exchange/client-access/Compare-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/compare-textmessagingverificationcode +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Compare-TextMessagingVerificationCode @@ -17,13 +16,16 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Compare-TextMessagingVerificationCode cmdlet to verify the text messaging verification code that the user specified as part of configuring text message notifications on the mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Compare-TextMessagingVerificationCode [[-Identity] ] -VerificationCode [-Confirm] - [-DomainController ] [-WhatIf] [] +Compare-TextMessagingVerificationCode [[-Identity] ] -VerificationCode + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ The Compare-TextMessagingVerificationCode cmdlet returns the value true if the c When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,6 +60,33 @@ This example compares the verification code 111555 to the code sent to Tony Smit ## PARAMETERS +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -VerificationCode The VerificationCode parameter contains the verification code that the user specified. @@ -77,8 +106,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -112,42 +140,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -169,12 +161,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Complete-MigrationBatch.md b/exchange/exchange-ps/exchange/Complete-MigrationBatch.md similarity index 86% rename from exchange/exchange-ps/exchange/move-and-migration/Complete-MigrationBatch.md rename to exchange/exchange-ps/exchange/Complete-MigrationBatch.md index fbf3f1aaac..922eeca5b8 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Complete-MigrationBatch.md +++ b/exchange/exchange-ps/exchange/Complete-MigrationBatch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/complete-migrationbatch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Complete-MigrationBatch @@ -17,36 +16,36 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Complete-MigrationBatch cmdlet to finalize a migration batch for a local move, cross-forest move, or remote move migration that has successfully finished initial synchronization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Complete-MigrationBatch [[-Identity] ] + [-CompletePublicFolderMigrationWithDataLoss] [-Confirm] [-DomainController ] [-NotificationEmails ] [-Partition ] [-SyncAndComplete] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION After a migration batch for a local or cross-forest move has successfully run and has a status state of Synced, use the Complete-MigrationBatch cmdlet to finalize the migration batch. Finalization is the last phase performed during a local or cross-forest move. When you finalize a migration batch, the cmdlet does the following for each mailbox in the migration batch: - Runs a final incremental synchronization. - - Configures the user's Microsoft Outlook profile to point to the new target domain. - - Converts the source mailbox to a mail-enabled user in the source domain. -In the cloud-based service, this cmdlet sets the value of CompleteAfter to the current time. It is important to remember that any CompleteAfter setting that has been applied to the individual users within the batch will override the setting on the batch, so the completion for some users may be delayed until their configured time. +In the cloud-based service, this cmdlet sets the value of CompleteAfter to the current time. It is important to remember that any CompleteAfter setting that has been applied to the individual users within the batch will override the setting on the batch, so the completion for some users may be delayed until their configured time. When the finalization process is complete, you can remove the batch by using the Remove-MigrationBatch cmdlet. If a migration batch has a status of Completed with Errors, you can re-attempt to finalize the failed users. In Exchange Online, use the Start-MigrationBatch cmdlet to retry migration for failed users. In Exchange 2013 or Exchange 2016, use the Complete-MigrationBatch to retry these failed users. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,18 +58,32 @@ This example completes the migration batch LocalMove1 and sends a notification e ## PARAMETERS -### -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. +### -Identity +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. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +```yaml +Type: MigrationBatchIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CompletePublicFolderMigrationWithDataLoss +This parameter is available only in the cloud-based service. + +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 +Aliases: +Applicable: Exchange Online Required: False Position: Named @@ -79,16 +92,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DomainController -This parameter is available only in on-premises Exchange. +### -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. -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. ```yaml -Type: Fqdn +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -97,19 +113,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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. +### -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. ```yaml -Type: MigrationBatchIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -188,12 +206,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md b/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md new file mode 100644 index 0000000000..96f0891ba3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md @@ -0,0 +1,857 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Connect-ExchangeOnline + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Connect-ExchangeOnline cmdlet in the Exchange Online PowerShell module to connect to Exchange Online PowerShell or standalone Exchange Online Protection PowerShell using modern authentication. This cmdlet works for accounts with or without multi-factor authentication (MFA). + +To connect to Security & Compliance PowerShell, use the [Connect-IPPSSession](https://learn.microsoft.com/powershell/module/exchange/connect-ippssession) cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Connect-ExchangeOnline + [[-ConnectionUri] ] + [[-AzureADAuthorizationEndpointUri] ] + [[-ExchangeEnvironmentName] ] + [[-PSSessionOption] ] + [[-DelegatedOrganization] ] + [[-Prefix] ] + [[-CommandName] ] + [[-FormatTypeName] ] + [-AccessToken ] + [-AppId ] + [-BypassMailboxAnchoring] + [-Certificate ] + [-CertificateFilePath ] + [-CertificatePassword ] + [-CertificateThumbprint ] + [-Credential ] + [-Device] + [-DisableWAM] + [-EnableErrorReporting] + [-InlineCredential] + [-LoadCmdletHelp] + [-LogDirectoryPath ] + [-LogLevel ] + [-ManagedIdentity] + [-ManagedIdentityAccountId ] + [-Organization ] + [-PageSize ] + [-ShowBanner] + [-ShowProgress ] + [-SigningCertificate ] + [-SkipLoadingCmdletHelp] + [-SkipLoadingFormatData] + [-TrackPerformance ] + [-UseMultithreading ] + [-UserPrincipalName ] + [-UseRPSSession] + [] +``` + +## DESCRIPTION +This cmdlet creates a PowerShell connection to your Exchange Online organization. + +Connect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, `$`). The workaround is to connect using a different account that doesn't have special characters in the profile path. + +## EXAMPLES + +### Example 1 +```powershell +Connect-ExchangeOnline -UserPrincipalName chris@contoso.com +``` + +This example connects to Exchange Online PowerShell using modern authentication, with or without multi-factor authentication (MFA). The connection uses REST API mode and doesn't require Basic authentication to be enabled in WinRM on the local computer. + +### Example 2 +```powershell +Connect-ExchangeOnline -AppId <%App_id%> -CertificateThumbprint <%Thumbprint string of certificate%> -Organization "contoso.onmicrosoft.com" +``` + +This example connects to Exchange Online PowerShell in an unattended scripting scenario using a certificate thumbprint. + +### Example 3 +```powershell +Connect-ExchangeOnline -AppId <%App_id%> -Certificate <%X509Certificate2 object%> -Organization "contoso.onmicrosoft.com" +``` + +This example connects to Exchange Online PowerShell in an unattended scripting scenario using a certificate file. This method is best suited for scenarios where the certificate is stored in remote machines and fetched at runtime. For example, the certificate is stored in the Azure Key Vault. + +### Example 4 +```powershell +Connect-ExchangeOnline -Device +``` + +In PowerShell 7.0.3 or later using version 2.0.4 or later of the module, this example connects to Exchange Online PowerShell in interactive scripting scenarios on computers that don't have web browsers. + +The command returns a URL and unique code that's tied to the session. You need to open the URL in a browser on any computer, and then enter the unique code. After you complete the login in the web browser, the session in the Powershell 7 window is authenticated via the regular Microsoft Entra authentication flow, and the Exchange Online cmdlets are imported after few seconds. + +### Example 6 +```powershell +Connect-ExchangeOnline -InlineCredential +``` + +In PowerShell 7.0.3 or later using version 2.0.4 or later of the module, this example connects to Exchange Online PowerShell in interactive scripting scenarios by passing credentials directly in the PowerShell window. + +## PARAMETERS + +### -ConnectionUri +**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: + +- Microsoft 365 or Microsoft 365 GCC: Don't use this parameter. The required value is `https://outlook.office365.com/powershell-liveid/`, but that's also the default value, so you don't need to use this parameter. +- Office 365 Germany: `https://outlook.office.de/PowerShell-LiveID` +- Office 365 operated by 21Vianet: `https://partner.outlook.cn/PowerShell` +- Microsoft 365 GCC High: `https://outlook.office365.us/powershell-liveID` +- Microsoft 365 DoD: `https://webmail.apps.mil/powershell-liveID` + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AzureADAuthorizationEndpointUri +**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: + +- 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. +- Office 365 Germany: `https://login.microsoftonline.de/common` +- Microsoft 365 GCC High or Microsoft 365 DoD: `https://login.microsoftonline.us/common` + +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). + +**Note**: MFA authentication or federated authentication isn't available in Office 365 operated by 21Vianet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeEnvironmentName +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. +- Office 365 Germany: `O365GermanyCloud` +- Office 365 operated by 21Vianet: `O365China` +- Microsoft 365 GCC High: `O365USGovGCCHigh` +- Microsoft 365 DoD: `O365USGovDoD` + +```yaml +Type: ExchangeEnvironment +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 2 +Default value: O365Default +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PSSessionOption +**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. + +Store the output of the [New-PSSessionOption](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/new-pssessionoption) command in a variable (for example, `$PSOptions = New-PSSessionOption `), and use the variable name as the value for this parameter (for example, `$PSOptions`). + +```yaml +Type: PSSessionOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DelegatedOrganization +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. + +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 4 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Prefix +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. +- You can't use the Prefix value EXO. That value is reserved for the nine exclusive **Get-EXO\*** cmdlets that are built into the module. +- The Prefix parameter affects only imported Exchange Online cmdlet names. It doesn't affect the names of cmdlets that are built into the module (for example, Disconnect-ExchangeOnline). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 5 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CommandName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FormatTypeName +The FormatTypeName parameter specifies the output format of the cmdlet. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 7 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessToken +**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. + +Depending on the type of access token, you need to use this parameter with the Organization, DelegatedOrganization, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppId +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassMailboxAnchoring +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 +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Certificate +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. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +```yaml +Type: X509Certificate2 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CertificateFilePath +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. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CertificatePassword +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: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +**Note**: Using a **ConvertTo-SecureString** command to store the password of the certificate locally defeats the purpose of a secure connection method for automation scenarios. Using a **Get-Credential** command to prompt you for the password of the certificate securely isn't ideal for automation scenarios. In other words, there's really no automated _and_ secure way to connect using a local certificate. + +```yaml +Type: SecureString +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CertificateThumbprint +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. + +**Note**: The CertificateThumbprint parameter is supported only in Microsoft Windows. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +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. + +After the Connect-ExchangeOnline command is complete, the password key in the variable is emptied. + +To specify the password for a certificate file, don't use this parameter; use the CertificatePassword parameter instead. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Device +**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. + +Using this switch results in an on-screen message that contains the URL and a unique code. On any other device with a web browser and internet access, open the URL, enter the unique code, and enter your credentials in the subsequent pages. + +If your login was successful, the PowerShell connection continues. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableWAM +**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. + +Starting in version 3.7.0, WAM is enabled by default when connecting to Exchange Online. If you encounter WAM-related issues during sign in, you can use this switch to disable WAM. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableErrorReporting +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InlineCredential +**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. + +This switch is similar to the Credential parameter, but with added security. The InlineCredential switch doesn't require you to store the credentials locally in the script, and you can enter credentials directly in an interactive PowerShell session. + +This switch does not work with accounts that use MFA. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LoadCmdletHelp +**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. + +Starting in v3.7.0-Preview1, help files for the command line aren't downloaded by default. Use this switch to download the files for cmdlet help at the command line. + +**Tip**: This parameter replaces the SkipLoadingCmdletHelp parameter. The SkipLoadingCmdletHelp parameter is no longer required and no longer works, because cmdlet help files are no longer downloaded by default. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LogDirectoryPath +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 ("). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LogLevel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedIdentity +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: + +- Azure Automation runbooks +- Azure Virtual Machines +- Azure Virtual Machine Scale Sets +- Azure Functions + +You must use this switch with the Organization parameter. + +For user-assigned managed identity, you must also use this switch with the ManagedIdentityAccountId parameter. + +For more information about connecting with managed identity, see [Use Azure managed identities to connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-exo-powershell-managed-identity). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedIdentityAccountId +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. + +For more information about connecting with managed identity, see [Use Azure managed identities to connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-exo-powershell-managed-identity). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +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). + +For more information about connecting with managed identity, see [Use Azure managed identities to connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-exo-powershell-managed-identity). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowBanner +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). +- To hide the banner, use this exact syntax: `-ShowBanner:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: $true +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowProgress +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. +- $false: Currently, this value has no effect. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SigningCertificate +**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. + +A valid value for this parameter is a variable that contains the certificate, or a command or expression that gets the certificate. + +To find the certificate, use the Get-PfxCertificate cmdlet in the Microsoft.PowerShell.Security module or use the Get-ChildItem cmdlet in the certificate (Cert:) drive. If the certificate isn't valid or doesn't have sufficient authority, the command will fail. + +```yaml +Type: X509Certificate2 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipLoadingCmdletHelp +**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. + +The SkipLoadingCmdletHelp switch prevents downloading the cmdlet help files for the Get-Help cmdlet in REST API connections. You don't need to specify a value with this switch. + +When you use this switch, you don't get local help files for any cmdlet at the command line. + +This switch doesn't work with the UseRPSSession switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipLoadingFormatData +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. + +Use this switch to avoid errors when connecting to Exchange Online PowerShell from within a Windows service or the Windows PowerShell SDK. + +This switch doesn't work with the UseRPSSession switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrackPerformance +The TrackPerformance parameter measures additional events (for example, CPU load and memory consumed). Valid values are: + +- $true: Performance tracking is enabled. +- $false: Performance tracking is disabled. This is the default value. + +This parameter works only when logging is enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseMultithreading +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. +- $false: Disable multi-threading. This value will degrade the performance of the nine exclusive **Get-EXO\*** cmdlets in the module. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseRPSSession +**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. + +This switch requires that Basic authentication is enabled in WinRM on the local computer. For more information, see [Turn on Basic authentication in WinRM](https://aka.ms/exov3-module#turn-on-basic-authentication-in-winrm). + +If you don't use this switch, REST API mode is used for the connection, so Basic authentication in WinRM isn't required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Connect-IPPSSession.md b/exchange/exchange-ps/exchange/Connect-IPPSSession.md new file mode 100644 index 0000000000..a260cad194 --- /dev/null +++ b/exchange/exchange-ps/exchange/Connect-IPPSSession.md @@ -0,0 +1,453 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Connect-IPPSSession + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Connect-IPPSSession cmdlet in the Exchange Online PowerShell module to connect to Security & Compliance PowerShell using modern authentication. The cmdlet works for MFA or non-MFA enabled accounts. + +**Note**: Version 3.2.0 or later of the module supports REST API mode for virtually all Security & Compliance PowerShell cmdlets (Basic authentication in WinRM on the local computer isn't required for REST API mode). For more information, see [Prerequisites for the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2#prerequisites-for-the-exchange-online-powershell-module). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Connect-IPPSSession + [[-ConnectionUri] ] + [[-AzureADAuthorizationEndpointUri] ] + [[-DelegatedOrganization] ] + [[-PSSessionOption] ] + [[-Prefix] ] + [[-CommandName] ] + [[-FormatTypeName] ] + [-AccessToken ] + [-AppId ] + [-BypassMailboxAnchoring] + [-Certificate ] + [-CertificateFilePath ] + [-CertificatePassword ] + [-CertificateThumbprint ] + [-Credential ] + [-Organization ] + [-UserPrincipalName ] + [-UseRPSSession] + [] +``` + +## DESCRIPTION +For detailed connection instructions, including prerequisites, see [Connect to Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-scc-powershell). + +## EXAMPLES + +### Example 1 +```powershell +Connect-IPPSSession -UserPrincipalName michelle@contoso.onmicrosoft.com +``` + +This example connects to Security & Compliance PowerShell using the specified account and modern authentication, with or without MFA. In v3.2.0 or later of the module, we're connecting in REST API mode, so Basic authentication in WinRM isn't required on the local computer. + +### Example 2 +```powershell +Connect-IPPSSession -UserPrincipalName michelle@contoso.onmicrosoft.com -UseRPSSession +``` + +This example connects to Security & Compliance PowerShell using the specified account and modern authentication, with or without MFA. In v3.2.0 or later of the module, we're connecting in remote PowerShell mode, so Basic authentication in WinRM is required on the local computer. + +### Example 3 +```powershell +Connect-IPPSSession -AppId <%App_id%> -CertificateThumbprint <%Thumbprint string of certificate%> -Organization "contoso.onmicrosoft.com" +``` + +This example connects to Security & Compliance PowerShell in an unattended scripting scenario using a certificate thumbprint. + +### Example 4 +```powershell +Connect-IPPSSession -AppId <%App_id%> -Certificate <%X509Certificate2 object%> -Organization "contoso.onmicrosoft.com" +``` + +This example connects to Security & Compliance PowerShell in an unattended scripting scenario using a certificate file. This method is best suited for scenarios where the certificate is stored in remote machines and fetched at runtime. For example, the certificate is stored in the Azure Key Vault. + +## PARAMETERS + +### -ConnectionUri +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. +- Security & Compliance PowerShell in Office 365 operated by 21Vianet: `https://ps.compliance.protection.partner.outlook.cn/powershell-liveid` +- Security & Compliance PowerShell in Microsoft GCC High: `https://ps.compliance.protection.office365.us/powershell-liveid/` +- Security & Compliance PowerShell in Microsoft DoD: `https://l5.ps.compliance.protection.office365.us/powershell-liveid/` + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AzureADAuthorizationEndpointUri +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. +- Security & Compliance PowerShell in Office 365 operated by 21Vianet: `https://login.chinacloudapi.cn/common` +- Security & Compliance PowerShell in Microsoft GCC High or Microsoft DoD: `https://login.microsoftonline.us/common` + +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DelegatedOrganization +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. + +**Notes**: + +- Use the primary .onmicrosoft.com domain of the delegated organization for the value of this parameter. +- You must use the AzureADAuthorizationEndpointUri parameter with this parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PSSessionOption +**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. + +Store the output of the [New-PSSessionOption](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/new-pssessionoption) command in a variable (for example, `$PSOptions = New-PSSessionOption `), and use the variable name as the value for this parameter (for example, `$PSOptions`). + +```yaml +Type: PSSessionOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Prefix +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. +- You can't use the Prefix value EXO. That value is reserved for the nine exclusive **Get-EXO\*** cmdlets that are built into the module. +- The Prefix parameter affects only imported Security & Compliance cmdlet names. It doesn't affect the names of cmdlets that are built into the module (for example, Disconnect-ExchangeOnline). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 4 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CommandName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FormatTypeName +The FormatTypeName parameter specifies the output format of the cmdlet. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 6 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessToken +**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. + +Depending on the type of access token, you need to use this parameter with the Organization, DelegatedOrganization, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppId +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassMailboxAnchoring +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Certificate +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. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +```yaml +Type: X509Certificate2 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CertificateFilePath +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. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CertificatePassword +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: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +**Note**: Using a **ConvertTo-SecureString** command to store the password of the certificate locally defeats the purpose of a secure connection method for automation scenarios. Using a **Get-Credential** command to prompt you for the password of the certificate securely isn't ideal for automation scenarios. In other words, there's really no automated _and_ secure way to connect using a local certificate. + +```yaml +Type: SecureString +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CertificateThumbprint +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. + +**Note**: The CertificateThumbprint parameter is supported only in Microsoft Windows. + +For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +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. + +After the Connect-IPPSSession command is complete, the password key in the variable is emptied. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseRPSSession +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). + +The UseRPSSession switch allows you to connect to Security & Compliance PowerShell using traditional remote PowerShell access to all cmdlets. You don't need to specify a value with this switch. + +This switch requires that Basic authentication is enabled in WinRM on the local computer. For more information, see [Turn on Basic authentication in WinRM](https://aka.ms/exov3-module#turn-on-basic-authentication-in-winrm). + +If you don't use this switch, Basic authentication in WinRM is not required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Connect-Mailbox.md b/exchange/exchange-ps/exchange/Connect-Mailbox.md similarity index 88% rename from exchange/exchange-ps/exchange/mailboxes/Connect-Mailbox.md rename to exchange/exchange-ps/exchange/Connect-Mailbox.md index 20302986f0..87bea6279a 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Connect-Mailbox.md +++ b/exchange/exchange-ps/exchange/Connect-Mailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/connect-mailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Connect-Mailbox @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Connect-Mailbox cmdlet to connect disconnected mailboxes to existing user accounts that don't already have mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,18 +38,18 @@ Connect-Mailbox [-Identity] [-Database] [-Database] -LinkedDomainController -LinkedMasterAccount +Connect-Mailbox [-Identity] [-Database] -LinkedDomainController -LinkedMasterAccount [-LinkedCredential ] [-ActiveSyncMailboxPolicy ] [-Alias ] [-Confirm] [-DomainController ] [-Force] - [-LinkedCredential ] [-ManagedFolderMailboxPolicy ] [-ManagedFolderMailboxPolicyAllowed] [-RetentionPolicy ] [-User ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Room @@ -65,7 +64,8 @@ Connect-Mailbox [-Identity] [-Database] ] [-User ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Shared @@ -80,7 +80,8 @@ Connect-Mailbox [-Identity] [-Database] ] [-User ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ValidateOnly @@ -89,12 +90,16 @@ Connect-Mailbox [-Identity] [-Database] ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### User ``` -Connect-Mailbox [-Identity] [-Database] [-AddressBookPolicy ] [-AllowLegacyDNMismatch] [-Archive] +Connect-Mailbox [-Identity] [-Database] [-User ] + [-AddressBookPolicy ] + [-AllowLegacyDNMismatch] + [-Archive] [-ActiveSyncMailboxPolicy ] [-Alias ] [-Confirm] @@ -103,8 +108,8 @@ Connect-Mailbox [-Identity] [-Database] ] [-ManagedFolderMailboxPolicyAllowed] [-RetentionPolicy ] - [-User ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -117,20 +122,16 @@ There is no Disconnect-Mailbox cmdlet. You can use the Disable-Mailbox or Remove Use the Disable-Mailbox cmdlet to: - Disconnect the mailbox from the user account. - - Keep the mailbox in the disabled state before it's permanently deleted, subject to the deleted mailbox retention period. - - Keep the user account, but remove the Exchange attributes from the account. Use the Remove-Mailbox cmdlet to: - Disconnect the mailbox from the user account. - - Keep the mailbox in the disabled state before it's permanently deleted, subject to the deleted mailbox retention period (except if you use the Permanent or StoreMailboxIdentity parameters, which immediately deletes the mailbox from the database). - - Remove the user account. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -168,9 +169,7 @@ This example connects a room mailbox. 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 - - GUID - - LegacyExchangeDN You use this parameter with the Database parameter to specify the mailbox that you want to connect. @@ -192,9 +191,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You use this parameter with the Identity parameter to specify the mailbox that you want to connect. @@ -249,14 +246,11 @@ Accept wildcard characters: False ``` ### -LinkedMasterAccount -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: For example: +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 - - Distinguished name (DN) - - Canonical DN - - GUID This parameter is required only if you're connecting a linked mailbox. @@ -311,7 +305,9 @@ Accept wildcard characters: False ``` ### -ValidateOnly -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. +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. ```yaml Type: SwitchParameter @@ -330,9 +326,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID If you don't use this parameter, the default mobile device mailbox policy is used. @@ -354,12 +348,10 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID -For more information about address book policies, see [Address book policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies). +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). ```yaml Type: AddressBookMailboxPolicyIdParameter @@ -375,16 +367,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -439,8 +435,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -473,7 +468,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -491,7 +488,7 @@ Accept wildcard characters: False ### -LinkedCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -542,9 +539,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID Retention policies consist of tags that are applied to mailbox folders and mail items to determine the period of time that the items should be retained. @@ -563,14 +558,18 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the user object in Active Directory that you want to connect the mailbox to. You can use any value that uniquely identifies the user. For example: For example: +The User parameter specifies the user object in Active Directory that you want to connect the mailbox to. -- Name +For the best results, we recommend using the following values: -- Distinguished name (DN) +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. -- Canonical DN +Otherwise, you can use any value that uniquely identifies the user. For example: +- Name +- Distinguished name (DN) +- Canonical DN - GUID If you don't use this parameter, the command uses the LegacyExchangeDN and DisplayName property values of the mailbox to find a user account that has those same values. If it can't find a unique match, it doesn't connect the mailbox. @@ -609,12 +608,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Delete-QuarantineMessage.md b/exchange/exchange-ps/exchange/Delete-QuarantineMessage.md new file mode 100644 index 0000000000..3dc21e421f --- /dev/null +++ b/exchange/exchange-ps/exchange/Delete-QuarantineMessage.md @@ -0,0 +1,228 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Delete-QuarantineMessage + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Delete-QuarantineMessage cmdlet to delete quarantine messages from your cloud-based organization + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identities +``` +Delete-QuarantineMessage -Identities + [-Identity ] + [-Confirm] + [-EntityType ] + [-HardDelete] + [-RecipientAddress ] + [-WhatIf] + [] +``` + +### IdentityOnly +``` +Delete-QuarantineMessage -Identity + [-Confirm] + [-EntityType ] + [-HardDelete] + [-RecipientAddress ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Delete-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 +``` + +This example deletes the quarantined message with the specified Identity value. + +### Example 2 +```powershell +$ids = Get-QuarantineMessage | select -ExpandProperty Identity + +Delete-QuarantineMessage -Identity $ids[4] +``` + +This example deletes the 5th quarantined message in the list of results from Get-QuarantineMessage. The first message has the index number 0, the second has the index number 1 and so on. + +### Example 3 +```powershell +$ids = Get-QuarantineMessage | select -ExpandProperty Identity + +Delete-QuarantineMessage -Identities $ids -Identity 000 +``` + +This example deletes all quarantined messages. The Identity parameter is required, but the value 000 is ignored. + +## PARAMETERS + +### -Identities +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. + +When you use this parameter, the Identity parameter is required, but the value is ignored. For example, use the value 000 for the Identity parameter. + +```yaml +Type: QuarantineMessageIdentity[] +Parameter Sets: Identities +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +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 +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +```yaml +Type: QuarantineMessageIdentity +Parameter Sets: IdentityOnly +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntityType +The EntityType parameter filters the results by EntityType. Valid values are: + +- Email +- SharePointOnline +- Teams (currently in Preview) +- DataLossPrevention + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HardDelete +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md new file mode 100644 index 0000000000..fe87141f2e --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md @@ -0,0 +1,114 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-ATPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-ATPProtectionPolicyRule and Disable-EOPProtectionPolicyRule cmdlets together to turn off the Standard preset security policy or the Strict preset security policy in organizations with Microsoft Defender for Office 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-ATPProtectionPolicyRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled. + +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Disable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +In organizations with Defender for Office 365, this example turns off the Standard preset security policy. The State property value of both rules is now Disabled. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Disable-AddressListPaging.md b/exchange/exchange-ps/exchange/Disable-AddressListPaging.md similarity index 87% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Disable-AddressListPaging.md rename to exchange/exchange-ps/exchange/Disable-AddressListPaging.md index 0f12f70a6f..45471267d2 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Disable-AddressListPaging.md +++ b/exchange/exchange-ps/exchange/Disable-AddressListPaging.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/disable-addresslistpaging +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-AddressListPaging @@ -17,17 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-AddressListPaging cmdlet to disable Active Directory virtual list view for address lists. Virtual list view displays address lists in your organization as pages instead of loading and viewing the entire directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-AddressListPaging [-Confirm] [-DomainController ] - [-WhatIf] [] +Disable-AddressListPaging [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,10 +44,11 @@ This example disables virtual list view for address lists in your organization. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -97,12 +99,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Disable-AntiPhishRule.md b/exchange/exchange-ps/exchange/Disable-AntiPhishRule.md new file mode 100644 index 0000000000..df08fecd4f --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-AntiPhishRule.md @@ -0,0 +1,110 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-AntiPhishRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-AntiPhishRule cmdlet to disable antiphish rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-AntiPhishRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-AntiPhishRule -Identity "Engineering Department Phishing Rule" +``` + +This example disables the antiphish rule named Engineering Department Phishing Rule. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Disable-App.md b/exchange/exchange-ps/exchange/Disable-App.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Disable-App.md rename to exchange/exchange-ps/exchange/Disable-App.md index 2d8f2e27ba..881f7f9195 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Disable-App.md +++ b/exchange/exchange-ps/exchange/Disable-App.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/disable-app +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-App @@ -17,21 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-App cmdlet to disable (turn off) a specific app for a specific user. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-App [-Identity] [-Confirm] [-DomainController ] [-Mailbox ] - [-WhatIf] [] +Disable-App [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION The Disable-App cmdlet requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook). -For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://docs.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of Office 365 add-ins in the Microsoft 365 admin center](https://docs.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). +For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,6 +52,13 @@ Disable-App -Identity -Mailbox Tony This example disables the administrator-installed app FinanceTestApp for user Tony. +### Example 3 +```powershell +Disable-App -Identity 545d8236-721a-468f-85d8-254eca7cb0da -Mailbox Tony +``` + +This example disables the Share to Teams app for user Tony. + ## PARAMETERS ### -Identity @@ -70,10 +80,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -109,23 +120,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the identity of the mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Identity parameter. @@ -164,12 +166,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md similarity index 89% rename from exchange/exchange-ps/exchange/organization/Disable-CmdletExtensionAgent.md rename to exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md index 1e82482adc..071e1f83ec 100644 --- a/exchange/exchange-ps/exchange/organization/Disable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/disable-cmdletextensionagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-CmdletExtensionAgent @@ -17,13 +16,16 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-CmdletExtensionAgent cmdlet to disable existing cmdlet extension agents. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-CmdletExtensionAgent [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Disable-CmdletExtensionAgent [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and When you disable a cmdlet extension agent, the agent is disabled for the entire organization. When an agent is disabled, it's not made available to cmdlets. Cmdlets can no longer use the agent to perform additional operations. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,9 +50,7 @@ This example disables the cmdlet extension agent named Scripting Agent. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -69,10 +69,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -123,12 +124,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Disable-DistributionGroup.md b/exchange/exchange-ps/exchange/Disable-DistributionGroup.md similarity index 86% rename from exchange/exchange-ps/exchange/users-and-groups/Disable-DistributionGroup.md rename to exchange/exchange-ps/exchange/Disable-DistributionGroup.md index 75ea8bd5e7..e773646d76 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Disable-DistributionGroup.md +++ b/exchange/exchange-ps/exchange/Disable-DistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/disable-distributiongroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-DistributionGroup @@ -17,19 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-DistributionGroup cmdlet to remove email capabilities from existing mail-enabled security groups and distribution groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-DistributionGroup [-Identity] [-Confirm] [-DomainController ] - [-IgnoreDefaultScope] [-WhatIf] [] +Disable-DistributionGroup [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-WhatIf] + [] ``` ## DESCRIPTION The Disable-DistributionGroup cmdlet mail-disables existing mail-enabled security groups and distribution groups by removing the email attributes that are required by Exchange. Mail-disabled groups are invisible to the \*-DistributionGroup cmdlets (with the exception of Enable-DistributionGroup). All groups (mail-enabled or not) are visible to the Get-Group and Set-Group cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,15 +49,10 @@ This example mail-disables the distribution group named Distribution Group1. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -73,10 +71,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -107,12 +106,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -149,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md new file mode 100644 index 0000000000..9b1751508e --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-DnssecForVerifiedDomain + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-DnssecForVerifiedDomain cmdlet to disable Domain Name System Security (DNSSEC) for inbound mail to accepted domains in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-DnssecForVerifiedDomain [-DomainName] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-DnssecForVerifiedDomain -DomainName contoso.com +``` + +This example disables DNSSEC for mail sent to contoso.com. + +## PARAMETERS + +### -DomainName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md new file mode 100644 index 0000000000..b611fc63b1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md @@ -0,0 +1,123 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-EOPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-EOPProtectionPolicyRule cmdlet to turn off the Standard preset security policy or the Strict preset security policy. If your organization has Defender for Office 365, you also need to use the Disable-ATPProtectionPolicyRule cmdlet to turn off the policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-EOPProtectionPolicyRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled. + +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +In organizations without Defender for Office 365, this example turns off the Standard preset security policy. The State property value of the rule is now Disabled. + +### Example 2 +```powershell +Disable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Disable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +In organizations with Defender for Office 365, this example turns off the Standard preset security policy. The State property value of both rules is now Disabled. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Disable-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md similarity index 81% rename from exchange/exchange-ps/exchange/antispam-antimalware/Disable-HostedContentFilterRule.md rename to exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md index 28562a4126..7adfa0cbae 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Disable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/disable-hostedcontentfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Disable-HostedContentFilterRule @@ -17,19 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Disable-HostedContentFilterRule cmdlet to disable spam filter rules (content filter rules) in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-HostedContentFilterRule [-Identity] [-Confirm] [-WhatIf] [] +Disable-HostedContentFilterRule [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +45,7 @@ This example disables the enabled spam filter rule named Contoso Recipients. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,10 +64,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -105,12 +103,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Disable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md similarity index 80% rename from exchange/exchange-ps/exchange/antispam-antimalware/Disable-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md index 67f4ae7890..442273d3c0 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Disable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/disable-hostedoutboundspamfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Disable-HostedOutboundSpamFilterRule @@ -17,19 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Disable-HostedOutboundSpamFilterRule cmdlet to disable outbound spam filter rules in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-HostedOutboundSpamFilterRule [-Identity] [-Confirm] [-WhatIf] [] +Disable-HostedOutboundSpamFilterRule [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +45,7 @@ This example disables the enabled outbound spam filter rule named Contoso Execut 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,10 +64,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -105,12 +103,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md new file mode 100644 index 0000000000..59ff3a79b1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md @@ -0,0 +1,105 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-IPv6ForAcceptedDomain + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-IPv6ForAcceptedDomain cmdlet to disable or opt-out of support for mail delivery to accepted domains in Exchange Online using IPv6. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-IPv6ForAcceptedDomain [[-Domain] ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Online organization to use with this cmdlet. + +If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-IPv6ForAcceptedDomain -Domain contoso.com +``` + +This example disables IPv6 support for mail sent to contoso.com. Mail can be delivered to the domain using IPv4 only. + +## PARAMETERS + +### -Domain +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Disable-InboxRule.md b/exchange/exchange-ps/exchange/Disable-InboxRule.md similarity index 83% rename from exchange/exchange-ps/exchange/mailboxes/Disable-InboxRule.md rename to exchange/exchange-ps/exchange/Disable-InboxRule.md index ad84de292a..7bc6e6bce3 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Disable-InboxRule.md +++ b/exchange/exchange-ps/exchange/Disable-InboxRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/disable-inboxrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-InboxRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-InboxRule cmdlet to disable existing Inbox rules in mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,13 +27,14 @@ Disable-InboxRule [-Identity] [-DomainController ] [-Force] [-Mailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,12 +51,9 @@ This example disables the Inbox rule MoveAnnouncements in the mailbox Joe@Contos 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 - - RuleIdentity property (for example, 16752869479666417665). - -- Exchange Online: `\` (for example, `rzaher\16752869479666417665`. - -- On-premises Exchange: `\` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). +- Exchange Online: `MailboxAlias\RuleIdentity` (for example, `rzaher\16752869479666417665`). +- On-premises Exchange: `MailboxCanonicalName\RuleIdentity` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). ```yaml Type: InboxRuleIdParameter @@ -72,7 +69,7 @@ Accept wildcard characters: False ``` ### -AlwaysDeleteOutlookRulesBlob -The AlwaysDeleteOutlookRulesBlob parameter suppresses a warning that end users or administrators get if they use Outlook Web App or Windows PowerShell to modify Inbox rules. +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 @@ -90,10 +87,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -126,7 +124,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. 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. @@ -147,23 +147,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -200,12 +191,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Disable-JournalArchiving.md b/exchange/exchange-ps/exchange/Disable-JournalArchiving.md new file mode 100644 index 0000000000..a1bf697510 --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-JournalArchiving.md @@ -0,0 +1,135 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-JournalArchiving + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-JournalArchiving cmdlet to disable journal archiving for specific users. Microsoft 365 journal archiving uses mailboxes in Exchange Online to record or journal messages for mailboxes in on-premises organizations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-JournalArchiving [-Identity] + [-Confirm] + [-PreserveMailUser] + [-WhatIf] + [] +``` + +## DESCRIPTION +For each on-premise mailbox that's configured for journal archiving in Microsoft 365, a mail user (also known as a mail-enabled user) and a journal archive mailbox are created in Exchange Online. The mail user routes the incoming journaled messages from the on-premises organization, and the journal archive mailbox stores the journaled messages in the cloud. + +The Disable-JournalArchiving cmdlet removes the mail user and converts the journal archive mailbox into an inactive mailbox. The inactive mailbox remains fully available for In-place eDiscovery. + +In hybrid organizations that use DirSync, this cmdlet doesn't remove the mail user. Removal of the mail user is handled by DirSync. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-JournalArchiving -Identity TimothyAmaral_Archive +``` + +This example disables the journal archiving for the user named Timothy Amaral. Timothy's journal archive mailbox in Exchange Online is named TimothyAmaral\_Archive. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreserveMailUser +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-JournalRule.md b/exchange/exchange-ps/exchange/Disable-JournalRule.md similarity index 88% rename from exchange/exchange-ps/exchange/policy-and-compliance/Disable-JournalRule.md rename to exchange/exchange-ps/exchange/Disable-JournalRule.md index a2da7aa2bd..f36f1eaaaa 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-JournalRule.md +++ b/exchange/exchange-ps/exchange/Disable-JournalRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/disable-journalrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-JournalRule @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-JournalRule cmdlet to disable a journal rule on a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-JournalRule -Identity [-Confirm] [-DomainController ] - [-WhatIf] [] +Disable-JournalRule -Identity + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION You can enable or disable specific journal rules in your organization at any time using the Disable-JournalRule and Enable-JournalRule cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,10 +70,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -124,12 +127,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Disable-MailContact.md b/exchange/exchange-ps/exchange/Disable-MailContact.md similarity index 85% rename from exchange/exchange-ps/exchange/users-and-groups/Disable-MailContact.md rename to exchange/exchange-ps/exchange/Disable-MailContact.md index ef8770e918..97902c5fd6 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Disable-MailContact.md +++ b/exchange/exchange-ps/exchange/Disable-MailContact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/disable-mailcontact +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-MailContact @@ -17,19 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-MailContact cmdlet to remove email capabilities from existing mail contacts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-MailContact [-Identity] [-Confirm] [-DomainController ] - [-IgnoreDefaultScope] [-WhatIf] [] +Disable-MailContact [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-WhatIf] + [] ``` ## DESCRIPTION The Disable-MailContact cmdlet mail-disables existing mail contacts by removing the email attributes that are required by Exchange. Mail-disabled contacts are invisible to the \*-MailContact cmdlets (with the exception of Enable-MailContact). All contacts (mail-enabled or not) are visible to the Get-Contact and Set-Contact cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,15 +49,10 @@ This example mail-disables the mail contact named Ed Meadows. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -73,10 +71,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -107,12 +106,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -149,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Disable-MailPublicFolder.md b/exchange/exchange-ps/exchange/Disable-MailPublicFolder.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Disable-MailPublicFolder.md rename to exchange/exchange-ps/exchange/Disable-MailPublicFolder.md index 40af2b8815..a4aadbbe70 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Disable-MailPublicFolder.md +++ b/exchange/exchange-ps/exchange/Disable-MailPublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/disable-mailpublicfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-MailPublicFolder @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-MailPublicFolder cmdlet to mail-disable a public folder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-MailPublicFolder [-Identity] [-Confirm] [-DomainController ] - [-Server ] [-WhatIf] [] +Disable-MailPublicFolder [-Identity] + [-Confirm] + [-DomainController ] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,10 +64,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -97,16 +101,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -145,12 +146,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Disable-MailUser.md b/exchange/exchange-ps/exchange/Disable-MailUser.md similarity index 83% rename from exchange/exchange-ps/exchange/users-and-groups/Disable-MailUser.md rename to exchange/exchange-ps/exchange/Disable-MailUser.md index a1538ad263..c0728ff91a 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Disable-MailUser.md +++ b/exchange/exchange-ps/exchange/Disable-MailUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/disable-mailuser +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-MailUser @@ -17,19 +16,24 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-MailUser cmdlet to remove email capabilities from existing mail users. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-MailUser [-Identity] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] - [-IgnoreLegalHold] [-WhatIf] [] +Disable-MailUser [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-IgnoreLegalHold] + [-WhatIf] + [] ``` ## DESCRIPTION The Disable-MailUser cmdlet mail-disables existing mail users by removing the email attributes that are required by Exchange. Mail-disabled users are invisible to the \*-MailUser cmdlets (with the exception of Enable-MailUser). All users (mail-enabled or not) are visible to the Get-User and Set-User cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,15 +50,10 @@ This example mail-disables an existing mail user. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -73,10 +72,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -107,12 +107,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -129,7 +128,9 @@ Accept wildcard characters: False ``` ### -IgnoreLegalHold -The IgnoreLegalHold switch specifies whether to ignore the legal hold status of the user. When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed. You don't need to specify a value with this switch. +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. After you disable or remove a mailbox, you can't include it in a discovery search. When you disable a mailbox, the mailbox is disconnected from the user account. Disconnected mailboxes and removed mailboxes are permanently deleted from the mailbox database after the deleted mailbox retention period expires. However, you can also remove a mailbox and purge it immediately from the mailbox database. Check with your organization's legal or Human Resources department before you disable or remove a mailbox that's on legal hold. @@ -167,12 +168,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Disable-Mailbox.md b/exchange/exchange-ps/exchange/Disable-Mailbox.md similarity index 82% rename from exchange/exchange-ps/exchange/mailboxes/Disable-Mailbox.md rename to exchange/exchange-ps/exchange/Disable-Mailbox.md index b20624a679..8997b03b35 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Disable-Mailbox.md +++ b/exchange/exchange-ps/exchange/Disable-Mailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/disable-mailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-Mailbox @@ -17,47 +16,59 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-Mailbox cmdlet to disable the mailbox of existing users who already have mailboxes. For this cmdlet, a user could also be a public folder mailbox or an InetOrgPerson object. The user account that's associated with the mailbox remains, but it's no longer associated with a mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Arbitration ``` -Disable-Mailbox [-Identity] [-Arbitration] [-DisableLastArbitrationMailboxAllowed] [-DisableArbitrationMailboxWithOABsAllowed] +Disable-Mailbox [-Identity] + [-Arbitration] + [-DisableLastArbitrationMailboxAllowed] + [-DisableArbitrationMailboxWithOABsAllowed] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] [-IgnoreLegalHold] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Archive ``` -Disable-Mailbox [-Identity] [-Archive] [-PermanentlyDisable] +Disable-Mailbox [-Identity] + [-Archive] + [-PermanentlyDisable] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] [-IgnoreLegalHold] - [-WhatIf] [] + [-WhatIf] + [] ``` ### PublicFolder ``` -Disable-Mailbox [-Identity] [-Confirm] [-PublicFolder] +Disable-Mailbox [-Identity] + [-Confirm] + [-PublicFolder] [-DomainController ] [-IgnoreDefaultScope] [-IgnoreLegalHold] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RemoteArchive ``` -Disable-Mailbox [-Identity] [-RemoteArchive] +Disable-Mailbox [-Identity] + [-RemoteArchive] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] [-IgnoreLegalHold] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -67,7 +78,7 @@ The Disable-Mailbox cmdlet also performs the clean-up task on the individual mai Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if the mailbox was disabled or removed while the Exchange Information Store service was stopped, or if it was disabled or removed by an external means other than Exchange management interfaces, the status of the mailbox object in the Exchange mailbox database won't be marked as disconnected. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,7 +87,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Disable-Mailbox -Identity "John Woods" ``` -This example disables the mailbox of the user named John Woods and removes all mailbox attributes from John's user account.. +This example disables the mailbox of the user named John Woods and removes all mailbox attributes from John's user account. ### Example 2 ```powershell @@ -88,33 +99,24 @@ This example disables the remote archive for the on-premises user named John Woo ## PARAMETERS ### -Identity -The Identity parameter specifies the mailbox that you want to mailbox-disable. You can use any value that uniquely identifies the mailbox. For example: For example: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -152,7 +154,7 @@ You can't use this switch with the RemoteArchive switch. Type: SwitchParameter Parameter Sets: Archive Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -164,15 +166,16 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -238,12 +241,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -260,7 +262,11 @@ Accept wildcard characters: False ``` ### -IgnoreLegalHold -The IgnoreLegalHold switch specifies whether to ignore the legal hold status of the user. When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed. You don't need to specify a value with this switch. +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. + +When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed. After you disable or remove a mailbox, you can't include it in a discovery search. When you disable a mailbox, the mailbox is disconnected from the user account. Disconnected mailboxes and removed mailboxes are permanently deleted from the mailbox database after the deleted mailbox retention period expires. However, you can also remove a mailbox and purge it immediately from the mailbox database. Check with your organization's legal or Human Resources department before you disable or remove a mailbox that's on legal hold. @@ -268,7 +274,7 @@ After you disable or remove a mailbox, you can't include it in a discovery searc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -282,7 +288,10 @@ 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. -You can only use this switch on user mailboxes that aren't licensed and aren't on hold. +**Notes**: + +- You can only use this switch on user mailboxes that aren't licensed and aren't on hold. +- When the Exchange Online license is removed from a mailbox without following other deprovisioning steps, this may leave the mailbox in a hard-deleted state. In this case, this parameter is not useful. You can use it, for example, in hybrid Exchange environments. ```yaml Type: SwitchParameter @@ -344,7 +353,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -358,12 +367,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Disable-MailboxQuarantine.md b/exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md similarity index 89% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Disable-MailboxQuarantine.md rename to exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md index acf4f14cde..98aaf73776 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Disable-MailboxQuarantine.md +++ b/exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/disable-mailboxquarantine +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-MailboxQuarantine @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-MailboxQuarantine cmdlet to release quarantined mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,41 +24,52 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Disable-MailboxQuarantine [-Identity] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MailboxOrMailUserIdentity ``` -Disable-MailboxQuarantine [-Identity] [-IncludePassive] +Disable-MailboxQuarantine [-Identity] + [-IncludePassive] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### StoreMailboxIdentity ``` -Disable-MailboxQuarantine -Database -StoreMailboxIdentity [-IncludePassive] +Disable-MailboxQuarantine -Database -StoreMailboxIdentity + [-IncludePassive] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### IncludeAllMailboxes ``` -Disable-MailboxQuarantine -Database [-IncludeAllMailboxes] [-IncludePassive] +Disable-MailboxQuarantine -Database + [-IncludeAllMailboxes] + [-IncludePassive] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### IncludeAllDatabases ``` -Disable-MailboxQuarantine -Server [-IncludeAllDatabases] [-IncludePassive] +Disable-MailboxQuarantine -Server + [-IncludeAllDatabases] + [-IncludePassive] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Mailboxes are quarantined when they affect the availability of the mailbox database. Typically a software fix from Microsoft is required before releasing a mailbox from quarantine. If a fix isn't deployed before releasing the mailbox, the quarantine on the mailbox will be re-enabled if the condition recurs. The default quarantine duration is 24 hours. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,23 +86,14 @@ This example releases the mailbox for the user Brian Johnson from quarantine. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Database or Server parameters. @@ -127,9 +128,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You identify the mailboxes by using the IncludeAllMailboxes switch or the StoreMailboxIdentity parameter. @@ -189,11 +188,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished Name (DN) - - Exchange Legacy DN You can't use this parameter with the Identity or Database parameters. @@ -234,10 +230,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -288,12 +285,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Disable-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md similarity index 88% rename from exchange/exchange-ps/exchange/antispam-antimalware/Disable-MalwareFilterRule.md rename to exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md index 29b93b051a..127a8f0542 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Disable-MalwareFilterRule.md +++ b/exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/disable-malwarefilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Disable-MalwareFilterRule @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-MalwareFilterRule cmdlet to disable malware filter rules in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-MalwareFilterRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Disable-MalwareFilterRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,10 +61,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -115,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md similarity index 87% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Disable-MetaCacheDatabase.md rename to exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md index c483a76eff..87451f2763 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Disable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/disable-metacachedatabase +online version: https://learn.microsoft.com/powershell/module/exchange/disable-metacachedatabase applicable: Exchange Server 2019 title: Disable-MetaCacheDatabase schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2019" --- # Disable-MetaCacheDatabase @@ -17,16 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-MetaCacheDatabase cmdlet to disable the metacache database on Exchange 2019 Mailbox servers. The metacache database stores mailbox database indexes and secondary copies of metadata on solid state drives (SSDs) to improve search latency and user logons. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-MetaCacheDatabase -Server [-Confirm] [-WhatIf] [] +Disable-MetaCacheDatabase -Server + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,11 +45,8 @@ This example disables the metacache database on the Exchange server named Mailbo 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks ("). For example, "Server1","Server2"..."ServerN". @@ -68,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -106,12 +104,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Disable-OutlookAnywhere.md b/exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md similarity index 83% rename from exchange/exchange-ps/exchange/client-access-servers/Disable-OutlookAnywhere.md rename to exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md index 14940fd3ed..30685164f7 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Disable-OutlookAnywhere.md +++ b/exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/disable-outlookanywhere +online version: https://learn.microsoft.com/powershell/module/exchange/disable-outlookanywhere applicable: Exchange Server 2010 title: Disable-OutlookAnywhere schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Disable-OutlookAnywhere @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Disable-OutlookAnywhere cmdlet to disable Outlook Anywhere on Exchange Server 2010 Client Access servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Disable-OutlookAnywhere [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Server @@ -34,7 +34,8 @@ Disable-OutlookAnywhere [-Identity] Disable-OutlookAnywhere [-Server ] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -44,7 +45,7 @@ When you run this cmdlet, it can take as long as an hour for the settings to bec After the Client Access server is disabled for Outlook Anywhere, you may want to remove the RPC over HTTP proxy Windows networking component. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,13 +68,11 @@ This example disables Outlook Anywhere on the specified virtual directory on the ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -93,8 +92,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,11 +128,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -171,13 +166,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### -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. +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md similarity index 86% rename from exchange/exchange-ps/exchange/policy-and-compliance/Disable-OutlookProtectionRule.md rename to exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md index 6e422c1a4d..6032b60587 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md @@ -1,37 +1,41 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/disable-outlookprotectionrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-OutlookProtectionRule ## SYNOPSIS +**Note**: This cmdlet is no longer supported in the cloud-based service. + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Disable-OutlookProtectionRule cmdlet to disable an existing Microsoft Outlook protection rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-OutlookProtectionRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Disable-OutlookProtectionRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION Outlook protection rules are administrator-created rules applied before a user sends a message using Outlook. Outlook protection rules are used to automatically Information Rights Management (IRM)-protect email messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. -For more information, see [Outlook protection rules](https://docs.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). +For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,10 +67,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -119,12 +124,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Disable-PushNotificationProxy.md b/exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md similarity index 83% rename from exchange/exchange-ps/exchange/client-access/Disable-PushNotificationProxy.md rename to exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md index 66fc73d91b..ade8f3935d 100644 --- a/exchange/exchange-ps/exchange/client-access/Disable-PushNotificationProxy.md +++ b/exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/disable-pushnotificationproxy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-PushNotificationProxy @@ -15,20 +14,22 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Disable-PushNotificationProxy cmdlet to disable the push notification proxy that's configured between an on-premises Microsoft Exchange organization and a Microsoft Office 365 organization. +Use the Disable-PushNotificationProxy cmdlet to disable the push notification proxy that's configured between an on-premises Microsoft Exchange organization and a Microsoft 365 organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-PushNotificationProxy [-Confirm] [-WhatIf] [] +Disable-PushNotificationProxy [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Office 365 to Outlook on the web for devices on the user's device. +The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,10 +45,11 @@ This example disables the push notification proxy in the on-premises Exchange or ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -82,12 +84,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Disable-RemoteMailbox.md b/exchange/exchange-ps/exchange/Disable-RemoteMailbox.md similarity index 78% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Disable-RemoteMailbox.md rename to exchange/exchange-ps/exchange/Disable-RemoteMailbox.md index 5b08a49136..8039e5d1fd 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Disable-RemoteMailbox.md +++ b/exchange/exchange-ps/exchange/Disable-RemoteMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/disable-remotemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-RemoteMailbox @@ -15,31 +14,39 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Disable-RemoteMailbox cmdlet to remove mailboxes from the cloud-based service but keep the associated user objects in the on-premises Active Directory. +Use the Disable-RemoteMailbox cmdlet to remove user mailboxes from the cloud-based service but keep the associated user objects in the on-premises Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-RemoteMailbox [-Identity] [-Archive] [-Confirm] [-DomainController ] - [-IgnoreDefaultScope] [-IgnoreLegalHold] [-WhatIf] [] +Disable-RemoteMailbox [-Identity] + [-Archive] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-IgnoreLegalHold] + [-WhatIf] + [] ``` ## DESCRIPTION Use the Disable-RemoteMailbox cmdlet to perform the following actions: - Remove a cloud-based mailbox but keep the associated on-premises user account. To do this, you first need to remove the Exchange Online license for the mailbox. Otherwise, the mailbox won't be removed. The on-premises mail user is automatically converted to a regular user object. You can mail-enable the on-premises user object using the Enable-MailUser cmdlet. - - Disconnect a cloud-based archive mailbox from a cloud-based mailbox. The cloud-based mailbox and the associated on-premises mail user are preserved. If you want to remove both the cloud-based mailbox and the associated on-premises mail user, use the Remove-RemoteMailbox cmdlet. Directory synchronization must be configured correctly for a mailbox to be removed from the cloud. Removal of the cloud-based mailbox isn't immediate and depends on the directory synchronization schedule. -Note: If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with Disable-RemoteMailbox \ -Archive and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them may result in an ArchiveGuid mismatch and validation error. +**Notes**: + +- If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with the command `Disable-RemoteMailbox -Archive` and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them may result in an ArchiveGuid mismatch and validation error. +- Due to the current service architecture, you need to convert shared mailboxes to user mailboxes prior to running the Disable-RemoteMailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,19 +70,12 @@ This example removes the cloud-based archive mailbox but keeps the cloud-based m The Identity parameter specifies the cloud-based mailbox. Valid values are: - ADObjectID - - GUID - - Distinguished name (DN) - -- Domain\\SamAccountName - +- Domain\\Username - User principal name (UPN) - - LegacyExchangeDN - - Email address - - User alias ```yaml @@ -112,10 +112,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -146,12 +147,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -168,9 +168,9 @@ Accept wildcard characters: False ``` ### -IgnoreLegalHold -The IgnoreLegalHold switch ignores the legal hold status of the mailbox user and allows you to disable a cloud-based mailbox that's on legal hold. +The IgnoreLegalHold switch ignores the legal hold status of the remote user. You don't need to specify a value with this switch. -When you disable a mailbox, the mailbox is disconnected from the user account. After you disable a mailbox, you can't include it in a discovery search. Disconnected mailboxes are permanently deleted from the mailbox database after the deleted mailbox retention period expires. Check with your organization's legal or Human Resources department before disabling a mailbox that's on legal hold. +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. ```yaml Type: SwitchParameter @@ -206,12 +206,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md new file mode 100644 index 0000000000..8e8073a184 --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md @@ -0,0 +1,106 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-ReportSubmissionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-ReportSubmissionRule cmdlet to disable the report submission rule in your cloud-based organization. The report submission rule identifies the reporting mailbox where user reported messages are delivered. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-ReportSubmissionRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-ReportSubmissionRule -Identity DefaultReportSubmissionRule. +``` + +This example disables the report submission rule if it's already enabled. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md new file mode 100644 index 0000000000..35ef4b854d --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md @@ -0,0 +1,114 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-SafeAttachmentRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-SafeAttachmentRule cmdlet to disable safe attachment rules in your cloud-based organization. This cmdlet is also responsible for disabling complete Safe Attachments policies in the admin center, which consist of the safe attachment rule and the corresponding assigned safe attachment policy in PowerShell. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-SafeAttachmentRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-SafeAttachmentRule -Identity "Engineering Department Attachment Rule" +``` + +This example disables the safe attachment rule named Engineering Department Attachment Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Disable-SafeLinksRule.md b/exchange/exchange-ps/exchange/Disable-SafeLinksRule.md new file mode 100644 index 0000000000..fa714bf72f --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-SafeLinksRule.md @@ -0,0 +1,114 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-SafeLinksRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-SafeLinksRule cmdlet to disable enabled Safe Links rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-SafeLinksRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-SafeLinksRule -Identity "Engineering Department URL Rule" +``` + +This example disables the enabled Safe Links rule named Engineering Department URL Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Disable-ServiceEmailChannel.md rename to exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md index 34e44d8dbe..13a29e56ed 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Disable-ServiceEmailChannel.md +++ b/exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/disable-serviceemailchannel +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-ServiceEmailChannel @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-ServiceEmailChannel cmdlet to disable the .NET service channel for a specific user. The .NET service channel enables Microsoft Exchange to store information that it later forwards to applications or devices that aren't permanently connected to the server running Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-ServiceEmailChannel [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Disable-ServiceEmailChannel [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The Disable-ServiceEmailChannel cmdlet deletes the receive folder in the user's mailbox under the root folder. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,23 +64,14 @@ The Identity parameter specifies the identity of the user for which you want to You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -97,10 +90,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -151,12 +145,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md b/exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md new file mode 100644 index 0000000000..927fd4cd53 --- /dev/null +++ b/exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disable-SmtpDaneInbound + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Disable-SMTPDaneInbound cmdlet to disable SMTP DNS-based Authentication of Named Entities (DANE) for inbound mail to accepted domains in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Disable-SmtpDaneInbound [-DomainName] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Disable-SmtpDaneInbound -DomainName contoso.com +``` + +This example disables SMTP DANE for mail sent to contoso.com. + +## PARAMETERS + +### -DomainName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Disable-SweepRule.md b/exchange/exchange-ps/exchange/Disable-SweepRule.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Disable-SweepRule.md rename to exchange/exchange-ps/exchange/Disable-SweepRule.md index a622136ff3..225c628693 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Disable-SweepRule.md +++ b/exchange/exchange-ps/exchange/Disable-SweepRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/disable-sweeprule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-SweepRule @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-SweepRule cmdlet to disable Sweep rules in mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-SweepRule [-Identity] [-Confirm] [-DomainController ] - [-Mailbox ] [-WhatIf] [] +Disable-SweepRule [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,10 +54,8 @@ This example disables all Sweep rules in the specified mailbox. 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==). - -- Exchange Online: \\\\ (for example, rzaher\\x2hlsdpGmUifjFgxxGIOJw==. - -- On-premises Exchange: \\\\ (for example, contoso.com/Users/Rick Zaher\\x2hlsdpGmUifjFgxxGIOJw==. +- Exchange Online: `MailboxAlias\RuleID` (for example, `rzaher\2hlsdpGmUifjFgxxGIOJw==`). +- On-premises Exchange: `MailboxCanonicalName\RuleID` (for example, `contoso.com/Users/Rick Zaher\x2hlsdpGmUifjFgxxGIOJw==`). ```yaml Type: SweepRuleIdParameter @@ -72,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -111,23 +111,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -164,12 +155,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Disable-TransportAgent.md b/exchange/exchange-ps/exchange/Disable-TransportAgent.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Disable-TransportAgent.md rename to exchange/exchange-ps/exchange/Disable-TransportAgent.md index cfc64ee5fd..5ccd3fab73 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Disable-TransportAgent.md +++ b/exchange/exchange-ps/exchange/Disable-TransportAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/disable-transportagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-TransportAgent @@ -17,17 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-TransportAgent cmdlet to disable a transport agent. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-TransportAgent [-Identity] [-Confirm] [-DomainController ] [-WhatIf] - [-TransportService ] [] +Disable-TransportAgent [-Identity] + [-Confirm] + [-DomainController ] + [-TransportService ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,10 +62,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -94,33 +98,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -TransportService 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. - - MailboxSubmission for the Mailbox Transport Submission service on Mailbox servers. - - MailboxDelivery for the Mailbox Transport Delivery service on Mailbox servers. - - FrontEnd for the Front End Transport service on Mailbox servers. - - Edge on Edge Transport servers. ```yaml @@ -136,17 +120,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-TransportRule.md b/exchange/exchange-ps/exchange/Disable-TransportRule.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance/Disable-TransportRule.md rename to exchange/exchange-ps/exchange/Disable-TransportRule.md index 129860dd0e..03d4189525 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-TransportRule.md +++ b/exchange/exchange-ps/exchange/Disable-TransportRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/disable-transportrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Disable-TransportRule @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Disable-TransportRule cmdlet to disable transport rules (mail flow rules) in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-TransportRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Disable-TransportRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION To enable rules that are disabled, use the Enable-TransportRule cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +48,7 @@ This example disables the rule named Sales Disclaimer. The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -67,10 +67,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -125,12 +126,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Disable-UMAutoAttendant.md rename to exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md index 937f282b44..9a332903c9 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMAutoAttendant.md +++ b/exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md @@ -1,29 +1,31 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/disable-umautoattendant -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-UMAutoAttendant ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Disable-UMAutoAttendant cmdlet to disable an existing Unified Messaging (UM) auto attendant that's enabled. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-UMAutoAttendant [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Disable-UMAutoAttendant [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ The Disable-UMAutoAttendant cmdlet disables an existing UM auto attendant that's After this task is completed, the UM auto attendant is disabled and won't accept incoming calls. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +53,7 @@ The Identity parameter specifies the identifier for the UM auto attendant that's Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,15 +65,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -81,15 +82,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -105,7 +104,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Disable-UMCallAnsweringRule.md rename to exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md index e201900efe..d9f8154eaf 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md @@ -1,29 +1,32 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/disable-umcallansweringrule -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-UMCallAnsweringRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Disable-UMCallAnsweringRule cmdlet to disable a call answering rule that has been created within a UM-enabled mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-UMCallAnsweringRule [-Identity] [-Confirm] [-DomainController ] - [-Mailbox ] [-WhatIf] [] +Disable-UMCallAnsweringRule [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +34,7 @@ The Disable-UMCallAnsweringRule cmdlet disables the call answering rule by modif When the call answering rule is created, you should disable the call answering rule when you're setting up conditions and actions. This prevents the call answering rule from being processed when an incoming call is received until you've correctly configured the call answering rule. After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,7 +68,7 @@ The Identity parameter specifies the UM call answering rule in a UM-enabled mail Type: UMCallAnsweringRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -77,15 +80,16 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -95,15 +99,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -116,23 +118,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the mailbox of the user who is running the command is used. @@ -141,7 +134,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -157,7 +150,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -171,12 +164,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMIPGateway.md b/exchange/exchange-ps/exchange/Disable-UMIPGateway.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Disable-UMIPGateway.md rename to exchange/exchange-ps/exchange/Disable-UMIPGateway.md index 551a4bfc02..f0738b7185 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMIPGateway.md +++ b/exchange/exchange-ps/exchange/Disable-UMIPGateway.md @@ -1,35 +1,38 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/disable-umipgateway -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-UMIPGateway ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Disable-UMIPGateway cmdlet to disable a Unified Messaging (UM) IP gateway. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-UMIPGateway [-Identity] [-Confirm] [-DomainController ] - [-Immediate ] [-WhatIf] [] +Disable-UMIPGateway [-Identity] + [-Confirm] + [-DomainController ] + [-Immediate ] + [-WhatIf] + [] ``` ## DESCRIPTION The status variable for a UM IP gateway can be used to enable or disable call answering destined for the IP gateway. The Disable-UMIPGateway cmdlet disables a UM IP gateway in Active Directory by modifying its status variable. After this task is completed, the UM IP gateway no longer answers incoming calls or makes outgoing calls. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,7 +59,7 @@ The Identity parameter specifies the identifier for the UM IP gateway being disa Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -68,15 +71,16 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -86,15 +90,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -110,7 +112,7 @@ The Immediate parameter specifies whether the Mailbox server running the Microso Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -126,7 +128,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -140,12 +142,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMMailbox.md b/exchange/exchange-ps/exchange/Disable-UMMailbox.md similarity index 78% rename from exchange/exchange-ps/exchange/unified-messaging/Disable-UMMailbox.md rename to exchange/exchange-ps/exchange/Disable-UMMailbox.md index 4b0894d509..f9ea3dd8ba 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMMailbox.md +++ b/exchange/exchange-ps/exchange/Disable-UMMailbox.md @@ -1,35 +1,39 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/disable-ummailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Disable-UMMailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Disable-UMMailbox cmdlet to disable Unified Messaging (UM) for UM-enabled mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-UMMailbox [-Identity] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] - [-KeepProperties ] [-WhatIf] [] +Disable-UMMailbox [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-KeepProperties ] + [-WhatIf] + [] ``` ## DESCRIPTION After the mailbox is disabled for Unified Messaging, the user can no longer use the UM features that are included in Microsoft Exchange and the Microsoft Exchange Unified Messaging service no longer handle calls for the associated extension number. The mailbox continues to function normally for all other operations that are unrelated to Unified Messaging. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,30 +50,21 @@ This example disables Unified Messaging on the mailbox for tonysmith@contoso.com 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -81,15 +76,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -99,15 +93,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -117,21 +109,18 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -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. -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -144,14 +133,13 @@ Accept wildcard characters: False 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. - - $false: The UM properties are removed from the mailbox. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -167,7 +155,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -181,12 +169,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMServer.md b/exchange/exchange-ps/exchange/Disable-UMServer.md similarity index 90% rename from exchange/exchange-ps/exchange/unified-messaging/Disable-UMServer.md rename to exchange/exchange-ps/exchange/Disable-UMServer.md index 9cc47b4d85..2b34bd0f25 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMServer.md +++ b/exchange/exchange-ps/exchange/Disable-UMServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/disable-umserver +online version: https://learn.microsoft.com/powershell/module/exchange/disable-umserver applicable: Exchange Server 2010 title: Disable-UMServer schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Disable-UMServer @@ -17,13 +16,17 @@ This cmdlet is available only in Exchange Server 2010. Use the Disable-UMServer cmdlet to set the status of an Exchange Server 2010 Unified Messaging (UM) server to disabled. This prevents the Unified Messaging server from processing UM calls. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-UMServer [-Identity] [-Confirm] [-DomainController ] - [-Immediate ] [-WhatIf] [] +Disable-UMServer [-Identity] + [-Confirm] + [-DomainController ] + [-Immediate ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -32,14 +35,11 @@ The Disable-UMServer cmdlet sets the status of a Unified Messaging server. A UM After this task is completed, the UM server can no longer: - Answer any incoming calls - - Respond to Play on Phone requests from a Client Access server - - Be used to manage UM-enabled mailboxes - - Be queried when a diagnostic task is used -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -78,8 +78,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -148,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMService.md b/exchange/exchange-ps/exchange/Disable-UMService.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Disable-UMService.md rename to exchange/exchange-ps/exchange/Disable-UMService.md index 7438d2335a..48cc82a85b 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Disable-UMService.md +++ b/exchange/exchange-ps/exchange/Disable-UMService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/disable-umservice -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Disable-UMService @@ -17,15 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Disable-UMService cmdlet to set the status of an Exchange Server 2010 Unified Messaging server to disabled. This prevents the UM server from processing UM incoming calls. -You can run this cmdlet on an Exchange Server 2016 Mailbox server, but the target server must be an Exchange 2010 UM server. You can't use this cmdlet to disable the UM service on an Exchange 2016 Mailbox server. +You can run this cmdlet in Exchange 2013 or Exchange 2016, but the target server must be an Exchange 2010 UM server. You can't use this cmdlet to disable the UM service on Exchange 2013 or Exchange 2016 Mailbox servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Disable-UMService [-Identity] [-Confirm] [-DomainController ] - [-Immediate ] [-WhatIf] [] +Disable-UMService [-Identity] + [-Confirm] + [-DomainController ] + [-Immediate ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -34,14 +37,11 @@ The Disable-UMService cmdlet sets the status of a UM server. A UM server has a l After this task is completed, the UM server can no longer: - Answer any incoming calls. - - Respond to Play on Phone requests from a UM server. - - Be used to manage UM-enabled mailboxes. - - Be queried when a diagnostic task is used. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,18 +65,15 @@ This example disables Unified Messaging on the UM server MyUMServer and disconne 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 - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml Type: UMServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -88,15 +85,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -112,7 +108,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -128,7 +124,7 @@ The Immediate parameter specifies whether the UM server drops all current calls Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -144,7 +140,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -158,12 +154,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md b/exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md new file mode 100644 index 0000000000..c2a6bb1153 --- /dev/null +++ b/exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md @@ -0,0 +1,171 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Disconnect-ExchangeOnline + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Disconnect-ExchangeOnline cmdlet in the Exchange Online PowerShell module to disconnect the connections that you created using the Connect-ExchangeOnline or Connect-IPPSSession cmdlets. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### DefaultParameterSet (Default) +``` +Disconnect-ExchangeOnline + [-Confirm] + [-WhatIf] + [] +``` + +### ConnectionId +``` +Disconnect-ExchangeOnline -ConnectionId + [-Confirm] + [-WhatIf] + [] +``` + +### ModulePrefix +``` +Disconnect-ExchangeOnline -ModulePrefix + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +This cmdlet is the counterpart to the Connect-ExchangeOnline and Connect-IPPSSession cmdlets. + +This cmdlet disconnects any connections and clears the cache. After a successful disconnect, you can't successfully run any cmdlets for your organization. + +Disconnect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, `$`). The workaround is to connect using a different account that doesn't have special characters in the profile path. + +## EXAMPLES + +### Example 1 +```powershell +Disconnect-ExchangeOnline +``` + +This example asks for confirmation before disconnecting from Exchange Online PowerShell or Security & Compliance PowerShell. + +### Example 2 +```powershell +Disconnect-ExchangeOnline -Confirm:$false +``` + +This example silently disconnects from Exchange Online PowerShell or Security & Compliance PowerShell without a confirmation prompt or any notification text. + +### Example 3 +```powershell +Disconnect-ExchangeOnline -ConnectionId 1a9e45e8-e7ec-498f-9ac3-0504e987fa85 +``` + +This example disconnects the REST-based Exchange Online PowerShell connection with the specified ConnectionId value. Any other remote PowerShell connections to Exchange Online PowerShell or Security & Compliance PowerShell in the same Windows PowerShell window are also disconnected. + +### Example 4 +```powershell +Disconnect-ExchangeOnline -ModulePrefix Contoso,Fabrikam +``` + +This example disconnects the REST-based Exchange Online PowerShell connections that are using the specified prefix values. Any other remote PowerShell connections to Exchange Online PowerShell or Security & Compliance PowerShell in the same Windows PowerShell window are also disconnected. + +## PARAMETERS + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId +**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. + +Don't use this parameter with the ModulePrefix parameter. + +```yaml +Type: String[] +Parameter Sets: ConnectionId +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModulePrefix +**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. + +Don't use this parameter with the ConnectionId parameter. + +```yaml +Type: String[] +Parameter Sets: ModulePrefix +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Dismount-Database.md b/exchange/exchange-ps/exchange/Dismount-Database.md similarity index 88% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Dismount-Database.md rename to exchange/exchange-ps/exchange/Dismount-Database.md index bfb42fd306..7159912a4e 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Dismount-Database.md +++ b/exchange/exchange-ps/exchange/Dismount-Database.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/dismount-database +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Dismount-Database @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Dismount-Database cmdlet to dismount databases. You can run this command only if the Microsoft Exchange Information Store service is running. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Dismount-Database [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Dismount-Database [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +48,7 @@ Regardless of where you run this cmdlet, it operates against the server hosting The Identity parameter specifies the database that you want to dismount. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Dump-ProvisioningCache.md b/exchange/exchange-ps/exchange/Dump-ProvisioningCache.md similarity index 89% rename from exchange/exchange-ps/exchange/active-directory/Dump-ProvisioningCache.md rename to exchange/exchange-ps/exchange/Dump-ProvisioningCache.md index 7a6c394f20..b16e9a249e 100644 --- a/exchange/exchange-ps/exchange/active-directory/Dump-ProvisioningCache.md +++ b/exchange/exchange-ps/exchange/Dump-ProvisioningCache.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/dump-provisioningcache +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Dump-ProvisioningCache @@ -17,24 +16,29 @@ This cmdlet is available only in on-premises Exchange. Use the Dump-ProvisioningCache cmdlet to return a list of the cached keys and values for the specified server and Windows PowerShell application. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### GlobalCache ``` -Dump-ProvisioningCache [-Server] -Application [-GlobalCache] +Dump-ProvisioningCache [-Server] -Application + [-GlobalCache] [-CacheKeys ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### OrganizationCache ``` -Dump-ProvisioningCache [-Server] -Application [-CurrentOrganization] [-Organizations ] +Dump-ProvisioningCache [-Server] -Application + [-CurrentOrganization] + [-Organizations ] [-CacheKeys ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -42,7 +46,7 @@ The Dump-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely The Dump-ProvisioningCache cmdlet displays a list of the Windows PowerShell provisioning cache keys. Use the value of these cache keys with the Reset-ProvisioningCache cmdlet to reset provisioning cache data. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,19 +59,30 @@ This example displays all cache keys for the specified server and Windows PowerS ## PARAMETERS +### -Server +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Application The Application parameter specifies the specific administrative application to reset the provisioning cache for. You can use the following values: - Powershell - - Powershell-LiveId - - Powershell-Proxy - - PowershellLiveId-Proxy - - Ecp - - Psws ```yaml @@ -84,7 +99,7 @@ Accept wildcard characters: False ``` ### -GlobalCache -The GlobalCache switch specifies that all cache keys are cleared. +The GlobalCache switch specifies that all cache keys are cleared. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -99,22 +114,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Server -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -CacheKeys 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 @@ -136,8 +135,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -154,7 +152,7 @@ Accept wildcard characters: False ``` ### -CurrentOrganization -The CurrentOrganization switch specifies that the provision cache is reset for this organization. +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 @@ -206,12 +204,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md new file mode 100644 index 0000000000..af887e025f --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md @@ -0,0 +1,114 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-ATPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-ATPProtectionPolicyRule and Enable-EOPProtectionPolicyRule cmdlets together to turn on the Standard preset security policy or the Strict preset security policy in organizations with Microsoft Defender for Office 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-ATPProtectionPolicyRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled. + +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Enable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +In organizations with Defender for Office 365, this example turns on the Standard preset security policy. The State value of both rules is now Enabled. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Enable-AddressListPaging.md b/exchange/exchange-ps/exchange/Enable-AddressListPaging.md similarity index 87% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Enable-AddressListPaging.md rename to exchange/exchange-ps/exchange/Enable-AddressListPaging.md index 16b34866eb..7bdc8deb33 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Enable-AddressListPaging.md +++ b/exchange/exchange-ps/exchange/Enable-AddressListPaging.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/enable-addresslistpaging +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-AddressListPaging @@ -17,18 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-AddressListPaging cmdlet to enable Active Directory virtual list view for address lists. Virtual list view allows you to display the address lists in your organization as pages instead of loading and viewing the entire directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-AddressListPaging [-Confirm] [-DomainController ] [-WhatIf] [] +Enable-AddressListPaging [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,8 +46,7 @@ This example enables virtual list view for your organization. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -98,12 +99,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Enable-AntiPhishRule.md b/exchange/exchange-ps/exchange/Enable-AntiPhishRule.md new file mode 100644 index 0000000000..55bc463ac2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-AntiPhishRule.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-AntiPhishRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-AntiPhishRule cmdlet to enable antiphish rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-AntiPhishRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-AntiPhishRule -Identity "Marketing Department Phishing Rule" +``` + +This example enables the antiphish rule named Marketing Department Phishing Rule. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-AntispamUpdates.md b/exchange/exchange-ps/exchange/Enable-AntispamUpdates.md similarity index 86% rename from exchange/exchange-ps/exchange/antispam-antimalware/Enable-AntispamUpdates.md rename to exchange/exchange-ps/exchange/Enable-AntispamUpdates.md index 5ef9e87784..40a8ec1a57 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-AntispamUpdates.md +++ b/exchange/exchange-ps/exchange/Enable-AntispamUpdates.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/enable-antispamupdates +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-AntispamUpdates @@ -15,13 +14,16 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS The Enable-AntispamUpdates cmdlet was deprecated in Microsoft Exchange Server 2010 Service Pack 1 and is no longer used. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-AntispamUpdates [[-Identity] ] [-Confirm] - [-SpamSignatureUpdatesEnabled ] [-WhatIf] [] +Enable-AntispamUpdates [[-Identity] ] + [-Confirm] + [-SpamSignatureUpdatesEnabled ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -38,35 +40,35 @@ This cmdlet was deprecated in Microsoft Exchange Server 2010 Service Pack 1 and ## PARAMETERS -### -Confirm +### -Identity This parameter is reserved for internal Microsoft use. ```yaml -Type: SwitchParameter +Type: ServerIdParameter Parameter Sets: (All) -Aliases: cf +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity +### -Confirm This parameter is reserved for internal Microsoft use. ```yaml -Type: ServerIdParameter +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -107,12 +109,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Enable-App.md b/exchange/exchange-ps/exchange/Enable-App.md similarity index 83% rename from exchange/exchange-ps/exchange/mailboxes/Enable-App.md rename to exchange/exchange-ps/exchange/Enable-App.md index 242b753c0b..788dc99c86 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Enable-App.md +++ b/exchange/exchange-ps/exchange/Enable-App.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/enable-app +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-App @@ -17,21 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-App cmdlet to enable (turn on) a specific app for a specific user. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-App [-Identity] [-Confirm] [-DomainController ] [-Mailbox ] - [-WhatIf] [] +Enable-App [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION The Enable-App cmdlet requires that the specified app has already been installed (for example, that it has been installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook). -For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://docs.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of Office 365 add-ins in the Microsoft 365 admin center](https://docs.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). +For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,6 +52,13 @@ Enable-App -Identity -Mailbox Tony This example enables the administrator-installed app FinanceTestApp for user Tony. +### Example 3 +```powershell +Enable-App -Identity 545d8236-721a-468f-85d8-254eca7cb0da -Mailbox Tony +``` + +This example enables the Share to Teams app for user Tony. + ## PARAMETERS ### -Identity @@ -70,8 +80,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -106,26 +115,17 @@ Accept wildcard characters: False ``` ### -Mailbox -The Mailbox parameter specifies the the mailbox. You can use any value that uniquely identifies the mailbox. For example: +The Mailbox parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -162,12 +162,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md similarity index 90% rename from exchange/exchange-ps/exchange/organization/Enable-CmdletExtensionAgent.md rename to exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md index daf4805927..588d8f1d9a 100644 --- a/exchange/exchange-ps/exchange/organization/Enable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/enable-cmdletextensionagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-CmdletExtensionAgent @@ -17,13 +16,16 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-CmdletExtensionAgent cmdlet to enable existing cmdlet extension agents. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-CmdletExtensionAgent [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Enable-CmdletExtensionAgent [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -33,7 +35,7 @@ When you enable a cmdlet extension agent, the agent is run on every Exchange ser Before you enable agents, be sure that you're aware of how the agent works and what impact the agent will have on your organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,9 +52,7 @@ This example enables the cmdlet extension agent named Scripting Agent. Before yo 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 - - Distinguished name (DN) - - GUID ```yaml @@ -71,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,12 +124,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md b/exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md new file mode 100644 index 0000000000..c2a69f5215 --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md @@ -0,0 +1,107 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-ComplianceTagStorage + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Enable-ComplianceTagStorage cmdlet to create the retention label policy in the Microsoft Purview compliance portal. This is a one-time operation. Retention labels apply retention settings to content. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-ComplianceTagStorage + [-Confirm] + [-RecordsManagementSecurityGroupEmail ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can check the status by running the following command: `Get-ComplianceTagStorage | Format-List Enabled,DistributionStatus`. The value True for the Enabled property and the value Success for the DistributionStatus property indicates the Enable-ComplianceTagStorage cmdlet has already been run in the organization, and you don't need to run it again. If you run the cmdlet unnecessarily, you'll get a warning, and the DistributionStatus property changes to the value Pending for a few minutes before returning to the value Success. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-ComplianceTagStorage +``` + +This example creates the label policy in the Microsoft Purview compliance portal. + +## PARAMETERS + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordsManagementSecurityGroupEmail +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Enable-DistributionGroup.md b/exchange/exchange-ps/exchange/Enable-DistributionGroup.md similarity index 82% rename from exchange/exchange-ps/exchange/users-and-groups/Enable-DistributionGroup.md rename to exchange/exchange-ps/exchange/Enable-DistributionGroup.md index 0ab8d2953c..cda305dfb4 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Enable-DistributionGroup.md +++ b/exchange/exchange-ps/exchange/Enable-DistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/enable-distributiongroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-DistributionGroup @@ -17,19 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-DistributionGroup cmdlet to mail-enable existing universal security groups and universal distribution groups that aren't already mail-enabled. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-DistributionGroup [-Identity] [-Alias ] [-Confirm] [-DisplayName ] - [-DomainController ] [-PrimarySmtpAddress ] [-WhatIf] [] +Enable-DistributionGroup [-Identity] + [-Alias ] + [-Confirm] + [-DisplayName ] + [-DomainController ] + [-PrimarySmtpAddress ] + [-WhatIf] + [] ``` ## DESCRIPTION The Enable-DistributionGroup cmdlet mail-enables existing universal security groups and universal distribution groups by adding the email attributes that are required by Exchange. Mail-enabled security groups and distribution groups are visible to the other \*-DistributionGroup cmdlets and to the \*-DistributionGroupMember cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. ## EXAMPLES @@ -46,11 +53,8 @@ This example mail-enables the universal distribution group named Distribution Gr 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 - - Distinguished name (DN) - - Canonical DN - - GUID ```yaml @@ -67,16 +71,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -99,8 +107,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -151,7 +158,7 @@ Accept wildcard characters: False ### -PrimarySmtpAddress 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 this group won't be automatically updated by email address policies. +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. ```yaml Type: SmtpAddress @@ -187,12 +194,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md new file mode 100644 index 0000000000..785b0029ab --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md @@ -0,0 +1,105 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-DnssecForVerifiedDomain + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-DnssecForVerifiedDomain cmdlet to enable Domain Name System Security (DNSSEC) for inbound mail to accepted domains in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-DnssecForVerifiedDomain [-DomainName] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The output of this cmdlet is an MX record value that you need to add to DNS for the specified domain. + +For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-DnssecForVerifiedDomain -DomainName contoso.com +``` + +This example enables DNSSEC for mail sent to contoso.com. + +## PARAMETERS + +### -DomainName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md new file mode 100644 index 0000000000..a73b54c47d --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md @@ -0,0 +1,121 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-EOPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-EOPProtectionPolicyRule cmdlet to turn on the Standard preset security policy or the Strict preset security policy. If your organization has Defender for Office 365, you also need to use the Enable-ATPProtectionPolicyRule cmdlet to turn on the policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-EOPProtectionPolicyRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled. + +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +In organizations without Defender for Office 365, this example turns off the Standard preset security policy. The State property value of the rule is now Enabled. + +### Example 2 +```powershell +Enable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Enable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +In organizations with Defender for Office 365, this example turns on the Standard preset security policy. The State property value of both rules is now Enabled. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Enable-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md similarity index 90% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Enable-ExchangeCertificate.md rename to exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md index 3512ece573..29cc1af6d3 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Enable-ExchangeCertificate.md +++ b/exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/enable-exchangecertificate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-ExchangeCertificate @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-ExchangeCertificate cmdlet to enable an existing certificate on the Exchange server for Exchange services such as Internet Information Services (IIS), SMTP, POP, IMAP and Unified Messaging (UM). Once you enable a certificate for a service, you can't disable it. -To see the existing certificates that are used for Exchange services, use [Get-ExchangeCertificate](https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-exchangecertificate). +To see the existing certificates that are used for Exchange services, use [Get-ExchangeCertificate](https://learn.microsoft.com/powershell/module/exchange/get-exchangecertificate). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,7 +31,8 @@ Enable-ExchangeCertificate [-Thumbprint] -Services [-Force] [-NetworkServiceAllowed] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity @@ -43,7 +43,8 @@ Enable-ExchangeCertificate [[-Identity] ] -Servi [-DoNotRequireSsl] [-Force] [-NetworkServiceAllowed] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -51,11 +52,11 @@ The Enable-ExchangeCertificate cmdlet enables certificates by updating the metad After you run the Enable-ExchangeCertificate cmdlet, you might need to restart Internet Information Services (IIS). In some scenarios, Exchange might continue to use the previous certificate for encrypting and decrypting the cookie that's used for Outlook on the web (formerly known as Outlook Web App) authentication. We recommend restarting IIS in environments that use Layer 4 load balancing. -There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://docs.microsoft.com/Exchange/architecture/client-access/certificates). +There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://learn.microsoft.com/Exchange/architecture/client-access/certificates). -Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://blogs.office.com/2014/10/29/protecting-ssl-3-0-vulnerability/). +Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,21 +69,58 @@ This example enables a certificate for POP, IMAP, SMTP and IIS services. ## PARAMETERS +### -Thumbprint +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. + +```yaml +Type: String +Parameter Sets: Thumbprint +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter specifies the certificate that you want to configure. Valid values are: + +- `ServerNameOrFQDN\Thumbprint` +- `Thumbprint` + +You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. + +You can't use this parameter with the Server parameter. + +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. + +```yaml +Type: ExchangeCertificateIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Services 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. - - IIS: By default, when you enable a certificate for IIS, the "require SSL" setting is configured on the default web site in IIS. To prevent this change, use the DoNotRequireSsl switch. - - IMAP: Don't enable a wildcard certificate for the IMAP4 service. Instead, use the Set-ImapSettings cmdlet to configure the FQDN that clients use to connect to the IMAP4 service. - - POP: Don't enable a wildcard certificate for the POP3 service. Instead, use the Set-PopSettings cmdlet to configure the FQDN that clients use to connect to the POP3 service. - - SMTP: When you enable a certificate for SMTP, you're prompted to replace the default Exchange self-signed certificate that's used to encrypt SMTP traffic between internal Exchange. Typically, you don't need to replace the default certificate with a certificate from a commercial CA for the purpose of encrypting internal SMTP traffic. If you want to replace the default certificate without the confirmation prompt, use the Force switch. - - UM: You can only enable a certificate for the UM service when the UMStartupMode parameter on the Set-UMService cmdlet is set to TLS or Dual. If the UMStartupMode parameter is set to the default value TCP, you can't enable the certificate for the UM service. - - UMCallRouter: You can only enable a certificate for the UM Call Router service when the UMStartupMode parameter on the Set-UMCallRouterService cmdlet is set to TLS or Dual. If the UMStartupMode parameter is set to the default value TCP, you can't enable the certificate for the UM Call Router service. You can specify multiple values separated by commas. @@ -104,29 +142,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Thumbprint -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. - -```yaml -Type: String -Parameter Sets: Thumbprint -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -179,7 +198,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. By default, when you enable a certificate for SMTP, the command prompts you to replace the existing certificate that's enabled for SMTP, which is likely the default Exchange self-signed certificate. @@ -196,32 +217,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the certificate that you want to configure. Valid values are: - -- \\\\ - -- \ - -You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. - -You can't use this parameter with the Server parameter. - -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. - -```yaml -Type: ExchangeCertificateIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -NetworkServiceAllowed 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. @@ -242,11 +237,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -287,12 +279,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md similarity index 81% rename from exchange/exchange-ps/exchange/antispam-antimalware/Enable-HostedContentFilterRule.md rename to exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md index 237b3922c8..8b49e06134 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/enable-hostedcontentfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Enable-HostedContentFilterRule @@ -17,19 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Enable-HostedContentFilterRule cmdlet to enable spam filter rules (content filter rules) in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-HostedContentFilterRule [-Identity] [-Confirm] [-WhatIf] [] +Enable-HostedContentFilterRule [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +45,7 @@ This example enables the disabled spam filter rule named Contoso Recipients. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -105,12 +101,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md similarity index 80% rename from exchange/exchange-ps/exchange/antispam-antimalware/Enable-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md index 47e74679a5..b0b6d2ea45 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/enable-hostedoutboundspamfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Enable-HostedOutboundSpamFilterRule @@ -17,19 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Enable-HostedOutboundSpamFilterRule cmdlet to enable outbound spam filter rules in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-HostedOutboundSpamFilterRule [-Identity] [-Confirm] [-WhatIf] [] +Enable-HostedOutboundSpamFilterRule [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +45,7 @@ This example enables the disabled outbound spam filter rule named Contoso Execut 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -105,12 +101,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md new file mode 100644 index 0000000000..1ce4f5db89 --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md @@ -0,0 +1,105 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-IPv6ForAcceptedDomain + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-IPv6ForAcceptedDomain cmdlet to enable support for mail delivery to accepted domains in Exchange Online using IPv6. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-IPv6ForAcceptedDomain [[-Domain] ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Online organization to use with this cmdlet + +If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-IPv6ForAcceptedDomain -Domain contoso.com +``` + +This example enables IPv6 support for mail sent to contoso.com. Mail can be delivered to the domain using IPv4 or IPv6. + +## PARAMETERS + +### -Domain +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Enable-InboxRule.md b/exchange/exchange-ps/exchange/Enable-InboxRule.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Enable-InboxRule.md rename to exchange/exchange-ps/exchange/Enable-InboxRule.md index 4ff58bca13..a4e38bdcbb 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Enable-InboxRule.md +++ b/exchange/exchange-ps/exchange/Enable-InboxRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/enable-inboxrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-InboxRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-InboxRule cmdlet to enable an Inbox rule. Inbox rules are used to process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,13 +27,14 @@ Enable-InboxRule [-Identity] [-DomainController ] [-Force] [-Mailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,12 +51,9 @@ This example enables the Inbox rule named Move To Junk Mail in the mailbox that 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 - - RuleIdentity property (for example, 16752869479666417665). - -- Exchange Online: `\` (for example, `rzaher\16752869479666417665`. - -- On-premises Exchange: `\` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). +- Exchange Online: `MailboxAlias\RuleIdentity` (for example, `rzaher\16752869479666417665`). +- On-premises Exchange: `MailboxCanonicalName\RuleIdentity` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). ```yaml Type: InboxRuleIdParameter @@ -72,7 +69,7 @@ Accept wildcard characters: False ``` ### -AlwaysDeleteOutlookRulesBlob -The AlwaysDeleteOutlookRulesBlob switch hides a warning message when end users or administrators use Outlook on the web or PowerShell to modify Inbox rules. You don't need to specify a value with this switch. +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 @@ -90,8 +87,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,7 +122,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. 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. @@ -147,23 +145,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -200,12 +189,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Enable-JournalRule.md b/exchange/exchange-ps/exchange/Enable-JournalRule.md similarity index 88% rename from exchange/exchange-ps/exchange/policy-and-compliance/Enable-JournalRule.md rename to exchange/exchange-ps/exchange/Enable-JournalRule.md index 35afc5007c..a642ee6b6f 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Enable-JournalRule.md +++ b/exchange/exchange-ps/exchange/Enable-JournalRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/enable-journalrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-JournalRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-JournalRule cmdlet to enable an existing journal rule on a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,13 +24,14 @@ For information about the parameter sets in the Syntax section below, see [Excha Enable-JournalRule [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You can enable or disable specific journal rules in your organization at any time using the Enable-JournalRule and Disable-JournalRule cmdlets. For more information, see [Journaling in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/journaling/journaling). +You can enable or disable specific journal rules in your organization at any time using the Enable-JournalRule and Disable-JournalRule cmdlets. For more information, see [Journaling in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/journaling/journaling). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Enable-MailContact.md b/exchange/exchange-ps/exchange/Enable-MailContact.md similarity index 88% rename from exchange/exchange-ps/exchange/users-and-groups/Enable-MailContact.md rename to exchange/exchange-ps/exchange/Enable-MailContact.md index 541015277d..32afb576cd 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Enable-MailContact.md +++ b/exchange/exchange-ps/exchange/Enable-MailContact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/enable-mailcontact +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-MailContact @@ -17,22 +16,29 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-MailContact cmdlet to add email capabilities to existing contacts that aren't already mail-enabled. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-MailContact [-Identity] -ExternalEmailAddress [-Alias ] - [-Confirm] [-DisplayName ] [-DomainController ] +Enable-MailContact [-Identity] -ExternalEmailAddress + [-Alias ] + [-Confirm] + [-DisplayName ] + [-DomainController ] [-MacAttachmentFormat ] - [-MessageBodyFormat ] [-MessageFormat ] - [-PrimarySmtpAddress ] [-UsePreferMessageFormat ] [-WhatIf] [] + [-MessageBodyFormat ] + [-MessageFormat ] + [-PrimarySmtpAddress ] + [-UsePreferMessageFormat ] + [-WhatIf] + [] ``` ## DESCRIPTION The Enable-MailContact cmdlet mail-enables existing contacts by adding the email attributes that are required by Exchange. Mail contacts are visible to the other \*-MailContact cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,59 +51,60 @@ This example mail-enables an existing contact that isn't mail-enabled. ## PARAMETERS -### -ExternalEmailAddress -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. +### -Identity +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: -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. +- Name +- Distinguished name (DN) +- Canonical DN +- GUID ```yaml -Type: ProxyAddress +Type: ContactIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- Canonical DN +### -ExternalEmailAddress +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. -- GUID +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: ContactIdParameter +Type: ProxyAddress Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -120,8 +127,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -173,17 +179,13 @@ Accept wildcard characters: False 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) - - UuEncode - - AppleSingle - - AppleDouble The MacAttachmentFormat and MessageFormat parameters are interdependent: - MessageFormat is Text: MacAttachmentFormat can be BinHex or UuEncode. - - MessageFormat is Mime: MacAttachmentFormat can be BinHex, AppleSingle, or AppleDouble. ```yaml @@ -203,15 +205,12 @@ Accept wildcard characters: False The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text - - Html - - TextAndHtml (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. ```yaml @@ -231,13 +230,11 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text - - Mime (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. Therefore, if you want to change the MessageFormat parameter from Mime to Text, you must also change the MessageBodyFormat parameter to Text. @@ -279,7 +276,6 @@ Accept wildcard characters: False 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. - - $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. ```yaml @@ -316,12 +312,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Enable-MailPublicFolder.md b/exchange/exchange-ps/exchange/Enable-MailPublicFolder.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Enable-MailPublicFolder.md rename to exchange/exchange-ps/exchange/Enable-MailPublicFolder.md index d82b291fc3..a029579014 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Enable-MailPublicFolder.md +++ b/exchange/exchange-ps/exchange/Enable-MailPublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/enable-mailpublicfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-MailPublicFolder @@ -17,18 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-MailPublicFolder cmdlet to mail-enable public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-MailPublicFolder [-Identity] [-Confirm] [-DomainController ] - [-HiddenFromAddressListsEnabled ] [-Server ] [-WhatIf] - [-OverrideRecipientQuotas] [] +Enable-MailPublicFolder [-Identity] + [-Confirm] + [-DomainController ] + [-HiddenFromAddressListsEnabled ] + [-OverrideRecipientQuotas] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -120,17 +123,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -OverrideRecipientQuotas +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -164,33 +182,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OverrideRecipientQuotas -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Enable-MailUser.md b/exchange/exchange-ps/exchange/Enable-MailUser.md similarity index 90% rename from exchange/exchange-ps/exchange/users-and-groups/Enable-MailUser.md rename to exchange/exchange-ps/exchange/Enable-MailUser.md index 5c9daa81c4..0a00e13f2c 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Enable-MailUser.md +++ b/exchange/exchange-ps/exchange/Enable-MailUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/enable-mailuser +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-MailUser @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-MailUser cmdlet to mail-enable existing users that aren't already mail-enabled. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,18 +32,21 @@ Enable-MailUser [-Identity] -ExternalEmailAddress ] [-PrimarySmtpAddress ] [-UsePreferMessageFormat ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### EnableGuestUser ``` -Enable-MailUser [-Identity] [-ExternalEmailAddress ] +Enable-MailUser [-Identity] + [-ExternalEmailAddress ] [-Alias ] [-Confirm] [-DisplayName ] [-DomainController ] [-PrimarySmtpAddress ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -52,7 +54,7 @@ The Enable-MailUser cmdlet mail-enables existing users by adding the email attri Mail users have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,11 +71,8 @@ This example mail-enables user John with the external email address john@contoso 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 - - Distinguished name (DN) - - Canonical DN - - GUID ```yaml @@ -119,16 +118,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -151,8 +154,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -204,17 +206,13 @@ Accept wildcard characters: False 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) - - UuEncode - - AppleSingle - - AppleDouble The MacAttachmentFormat and MessageFormat parameters are interdependent: - MessageFormat is Text: MacAttachmentFormat can be BinHex or UuEncode. - - MessageFormat is Mime: MacAttachmentFormat can be BinHex, AppleSingle or AppleDouble. ```yaml @@ -234,15 +232,12 @@ Accept wildcard characters: False The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text - - Html - - TextAndHtml (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. ```yaml @@ -262,13 +257,11 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text - - Mime (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. Therefore, if you want to change the MessageFormat parameter from Mime to Text, you must also change the MessageBodyFormat parameter to Text. @@ -310,7 +303,6 @@ Accept wildcard characters: False 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. - - $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. ```yaml @@ -347,12 +339,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Enable-Mailbox.md b/exchange/exchange-ps/exchange/Enable-Mailbox.md similarity index 83% rename from exchange/exchange-ps/exchange/mailboxes/Enable-Mailbox.md rename to exchange/exchange-ps/exchange/Enable-Mailbox.md index b60f0c4ee1..3a49c7ac0c 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Enable-Mailbox.md +++ b/exchange/exchange-ps/exchange/Enable-Mailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/enable-mailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-Mailbox @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-Mailbox cmdlet to create mailboxes for existing users who don't already have mailboxes. You can also use this cmdlet to create In-Place archives for existing mailboxes. -Note: In Exchange Online, this cmdlet doesn't activate/enable a mailbox the same way it does in on-premises Exchange. To add a mailbox for an existing Azure AD account, you can simply add a license to the account by using the Set-MsolUserLicense cmdlet. +**Note**: In Exchange Online, you use this cmdlet to add archive mailboxes for existing users and to enable auto-expanding archives. To add a mailbox for an existing Microsoft Entra account, you need to add a license to the account as described in [Assign licenses to user accounts](https://learn.microsoft.com/office365/enterprise/powershell/assign-licenses-to-user-accounts-with-office-365-powershell). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -38,7 +37,8 @@ Enable-Mailbox [-Identity] [-Arbitration] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RemoteArchive @@ -56,7 +56,8 @@ Enable-Mailbox [-Identity] -ArchiveDomain [-RemoteArchive] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Discovery @@ -74,7 +75,8 @@ Enable-Mailbox [-Identity] [-Discovery] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Equipment @@ -92,12 +94,15 @@ Enable-Mailbox [-Identity] [-Equipment] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### LinkedRoomMailbox ``` -Enable-Mailbox [-Identity] -LinkedDomainController -LinkedMasterAccount [-LinkedCredential ] [-LinkedRoom] +Enable-Mailbox [-Identity] -LinkedDomainController -LinkedMasterAccount + [-LinkedCredential ] + [-LinkedRoom] [-ActiveSyncMailboxPolicy ] [-Alias ] [-Archive] @@ -114,12 +119,14 @@ Enable-Mailbox [-Identity] -LinkedDomainController -L [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Linked ``` -Enable-Mailbox [-Identity] -LinkedDomainController -LinkedMasterAccount [-LinkedCredential ] +Enable-Mailbox [-Identity] -LinkedDomainController -LinkedMasterAccount + [-LinkedCredential ] [-ActiveSyncMailboxPolicy ] [-Alias ] [-Confirm] @@ -132,7 +139,8 @@ Enable-Mailbox [-Identity] -LinkedDomainController - [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### PublicFolder @@ -151,7 +159,8 @@ Enable-Mailbox [-Identity] [-PublicFolder] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Room @@ -169,7 +178,8 @@ Enable-Mailbox [-Identity] [-Room] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Shared @@ -187,7 +197,8 @@ Enable-Mailbox [-Identity] [-Shared] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### User @@ -206,14 +217,18 @@ Enable-Mailbox [-Identity] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Archive ``` -Enable-Mailbox [-Identity] ] [-Archive] [-ArchiveDatabase [-ArchiveGuid ] [-ArchiveName ] +Enable-Mailbox [-Identity] ] [-Archive] + [-ArchiveDatabase ] + [-ArchiveGuid ] + [-ArchiveName ] [-ActiveSyncMailboxPolicy ] - [-Alias + [-Alias ] [-Confirm] [-DisplayName ] [-DomainController ] @@ -221,12 +236,13 @@ Enable-Mailbox [-Identity] ] [-Archive] [-ArchiveDatabase ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AuditLog ``` -Enable-Mailbox [-Identity] [AuditLog] +Enable-Mailbox [-Identity] [-AuditLog] [-ActiveSyncMailboxPolicy ] [-Alias ] [-Confirm] @@ -237,7 +253,8 @@ Enable-Mailbox [-Identity] [AuditLog] [-PrimarySmtpAddress ] [-RetentionPolicy ] [-RoleAssignmentPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AutoExpandingArchive @@ -255,7 +272,9 @@ The Enable-Mailbox cmdlet mailbox-enables existing users, public folders, or Ine When mailbox-enabling an existing user, beware of non-supported characters in the user account or Name property. If you don't specify an Alias value when you mailbox-enable the user, Exchange converts all non-supported characters to question marks (?). To avoid question marks in the Alias, verify that the user account and Name properties have only supported ASCII or Unicode characters or specify an Alias value when you mailbox-enable the user. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. ## EXAMPLES @@ -286,18 +305,15 @@ This example creates a remote archive for the existing on-premises user named Ay 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 - - Distinguished name (DN) - - Canonical DN - - GUID ```yaml Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -347,15 +363,17 @@ Accept wildcard characters: False ``` ### -Discovery +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. -Discovery mailboxes are created as target mailboxes for Discovery searches. After being created or enabled, a Discovery mailbox can't be converted to another type of mailbox. For more information, see [In-Place eDiscovery in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). +Discovery mailboxes are created as target mailboxes for Discovery searches. After being created or enabled, a Discovery mailbox can't be 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). ```yaml Type: SwitchParameter Parameter Sets: Discovery Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -407,14 +425,11 @@ Accept wildcard characters: False ### -LinkedMasterAccount 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: For example: +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: - Name - - Distinguished name (DN) - - Canonical DN - - GUID This parameter is required only if you're enabling a linked mailbox. @@ -518,9 +533,7 @@ 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:. - Name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default mobile device mailbox policy is applied to the mailbox. @@ -544,12 +557,10 @@ 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: - Name - - Distinguished name (DN) - - GUID -For more information about address book policies, see [Address book policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies). +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). ```yaml Type: AddressBookMailboxPolicyIdParameter @@ -567,16 +578,20 @@ Accept wildcard characters: False ### -Alias 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 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -603,7 +618,7 @@ The Archive switch creates an archive mailbox for an existing user that already Type: SwitchParameter Parameter Sets: Archive Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -618,9 +633,7 @@ 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: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -637,13 +650,15 @@ Accept wildcard characters: False ``` ### -ArchiveGuid +This parameter is available only in on-premises Exchange. + This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: Archive Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -653,15 +668,23 @@ Accept wildcard characters: False ``` ### -ArchiveName -The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook and Outlook Web App. +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 default value is In-Place Archive - \. +In on-premises Exchange, if you don't use this parameter, the following default values are used based on the version of Exchange: + +- Exchange 2016 or later: `In-Place Archive -` +- Exchange 2013: `In-Place Archive - ` +- Exchange 2010: `Personal Archive - ` + +In Exchange Online, if you don't use this parameter, the default value is `In-Place Archive -`. + +In Outlook in Exchange Online, the value of this parameter is ignored. The name of the archive mailbox that's shown in the folder list is `Online Archive - `. ```yaml Type: MultiValuedProperty Parameter Sets: Archive Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -691,21 +714,20 @@ Accept wildcard characters: False ### -AutoExpandingArchive This parameter is available only in the cloud-based service. -The AutoExpandingArchive switch enables the unlimited archiving feature (called auto-expanding archiving) for the specified mailbox. You don't need to specify a value with this switch. +The AutoExpandingArchive switch enables the auto-expanding archiving feature for the specified mailbox. You don't need to specify a value with this switch. After you enable auto-expanding archiving, additional storage space is automatically added to the user's archive mailbox when it approaches the storage limit. -Notes: +**Notes**: - The user's archive mailbox has to be enabled before auto-expanding archiving can be enabled. - - After you enable auto-expanding archiving for the user's mailbox, it can't be disabled. ```yaml Type: SwitchParameter Parameter Sets: AutoExpandingArchive Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -717,15 +739,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -740,9 +761,7 @@ 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: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -759,6 +778,8 @@ Accept wildcard characters: False ``` ### -DisplayName +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 ("). If you don't use DisplayName parameter, the value of the Name property is used for the display name. @@ -767,7 +788,7 @@ If you don't use DisplayName parameter, the value of the Name property is used f Type: String Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, Archive, AuditLog Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -795,13 +816,15 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -815,9 +838,9 @@ 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. -You need to use this parameter when you create the first public folder, which is called the hierarchy mailbox, in your organization. +You need to use this switch when you create the first public folder, which is called the hierarchy mailbox, in your organization. -Use this parameter only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you won't be able to create any public folders. +Use this switch only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you won't be able to create any public folders. ```yaml Type: SwitchParameter @@ -837,7 +860,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -853,7 +876,7 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicy -This parameter is available or functional only in 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. @@ -871,9 +894,11 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicyAllowed -This parameter is available or functional only in 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. -The ManagedFolderMailboxPolicyAllowed parameter 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. When a managed folder mailbox policy is assigned to a mailbox using the ManagedFolderMailboxPolicy parameter, the warning appears by default unless the ManagedFolderMailboxPolicyAllowed parameter is used. +When a managed folder mailbox policy is assigned to a mailbox using the ManagedFolderMailboxPolicy parameter, the warning appears by default unless the ManagedFolderMailboxPolicyAllowed switch is used. Outlook 2003 Service Pack 3 clients are supported but are provided limited functionality for MRM. @@ -936,9 +961,7 @@ 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: - Name - - Distinguished name (DN) - - GUID Retention policies consist of tags that are applied to mailbox folders and mail items to determine the period of time that the items should be retained. @@ -957,21 +980,19 @@ Accept wildcard characters: False ``` ### -RoleAssignmentPolicy -The RoleAssignmentPolicy parameter specifies the management role assignment policy that's assign to the mailbox. You can use any value that uniquely identifies the policy. For example: +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 - - Distinguished name (DN) - - GUID -If you don't use this parameter, the default role assignment policy is used. If the assignment policy name contains spaces, enclose the name in quotation marks ("). If you don't want to assign an assignment policy when a mailbox is created or enabled, specify a value of $null. For more information about assignment policies, see [Understanding management role assignment policies](https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). +If you don't use this parameter, the default role assignment policy is used. If the assignment policy name contains spaces, enclose the name in quotation marks ("). If you don't want to assign an assignment policy when a mailbox is created or enabled, specify a value of $null. For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). ```yaml Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -987,7 +1008,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1001,12 +1022,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Enable-MailboxQuarantine.md b/exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md similarity index 90% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Enable-MailboxQuarantine.md rename to exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md index fdc5e33d2d..94f1b1b2d7 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Enable-MailboxQuarantine.md +++ b/exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/enable-mailboxquarantine +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-MailboxQuarantine @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-MailboxQuarantine cmdlet to quarantine mailboxes that affect the availability of the mailbox database. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,29 +26,34 @@ Enable-MailboxQuarantine [-Identity] [-AllowMigration] [-Confirm] [-Duration ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MailboxOrMailUserIdentity ``` -Enable-MailboxQuarantine [-Identity] [-QuarantineReason ] +Enable-MailboxQuarantine [-Identity] + [-QuarantineReason ] [-AllowMigration] [-Confirm] [-Duration ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### StoreMailboxIdentity ``` -Enable-MailboxQuarantine -Database -StoreMailboxIdentity [-QuarantineReason ] +Enable-MailboxQuarantine -Database -StoreMailboxIdentity + [-QuarantineReason ] [-AllowMigration] [-Confirm] [-Duration ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -66,23 +70,14 @@ This example quarantines the mailbox for the user Brian Johnson. The Identity parameter specifies the mailbox that you want to quarantine. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Database parameter. @@ -117,9 +112,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You identify the mailbox by using the StoreMailboxIdentity parameter. @@ -160,7 +153,7 @@ Accept wildcard characters: False ``` ### -AllowMigration -The AllowMigration switch allows a quarantined mailbox to be moved to another mailbox database or to the cloud. You don't have to specify a value with this switch. +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. @@ -180,10 +173,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -252,12 +246,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md similarity index 88% rename from exchange/exchange-ps/exchange/antispam-antimalware/Enable-MalwareFilterRule.md rename to exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md index 460f4a5d68..d671effeae 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Enable-MalwareFilterRule.md +++ b/exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/enable-malwarefilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Enable-MalwareFilterRule @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-MalwareFilterRule cmdlet to enable malware filter rules in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-MalwareFilterRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Enable-MalwareFilterRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +61,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md similarity index 87% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Enable-MetaCacheDatabase.md rename to exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md index 61f18a91c6..642a0ec9b8 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Enable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/enable-metacachedatabase +online version: https://learn.microsoft.com/powershell/module/exchange/enable-metacachedatabase applicable: Exchange Server 2019 title: Enable-MetaCacheDatabase schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2019" --- # Enable-MetaCacheDatabase @@ -17,16 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-MetaCacheDatabase cmdlet to enable the metacache database on Exchange 2019 Mailbox servers. The metacache database stores mailbox database indexes and secondary copies of metadata on solid state drives (SSDs) to improve search latency and user logons. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-MetaCacheDatabase -Server [-Confirm] [-WhatIf] [] +Enable-MetaCacheDatabase -Server + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,11 +45,8 @@ This example enables the metacache database on the Exchange server named Mailbox 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks ("). For example, "Server1","Server2"..."ServerN". @@ -68,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -106,12 +104,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Enable-OrganizationCustomization.md b/exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md similarity index 84% rename from exchange/exchange-ps/exchange/organization/Enable-OrganizationCustomization.md rename to exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md index 5cd59bd760..23f178be9e 100644 --- a/exchange/exchange-ps/exchange/organization/Enable-OrganizationCustomization.md +++ b/exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/enable-organizationcustomization +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Enable-OrganizationCustomization @@ -17,15 +16,14 @@ This cmdlet is available only in the cloud-based service. You may be prompted to run the EnableOrganizationCustomization cmdlet before you create or modify objects in your Exchange Online organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-OrganizationCustomization [-Confirm] [-WhatIf] [] +Enable-OrganizationCustomization [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -34,20 +32,17 @@ In the Microsoft datacenters, certain objects are consolidated to save space. Wh Here are some examples of when you might see this: - Creating a new role group or creating a new management role assignment. - - Creating a new role assignment policy or modifying a built-in role assignment policy. - - Creating a new Outlook on the web mailbox policy or modifying a built-in Outlook on the web mailbox policy. - - Creating a new sharing policy or modifying a built-in sharing policy. - - Creating a new retention policy or modifying a built-in retention policy. +- Enabling preset security policies in the Microsoft Defender portal. Note that you are only required to run the Enable-OrganizationCustomization cmdlet once in your Exchange Online organization. If you attempt to run the cmdlet again, you'll get an error. Whether or not this command has been previously run in an organization is available in the IsDehydrated property of the Get-OrganizationConfig cmdlet: False ($false) = the command has already been run; True ($true) = the command has never been run. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +58,7 @@ This example runs the command as required. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -101,12 +95,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Enable-OutlookAnywhere.md b/exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md similarity index 84% rename from exchange/exchange-ps/exchange/client-access-servers/Enable-OutlookAnywhere.md rename to exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md index fcdc65eb36..f2706fde72 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Enable-OutlookAnywhere.md +++ b/exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/enable-outlookanywhere +online version: https://learn.microsoft.com/powershell/module/exchange/enable-outlookanywhere applicable: Exchange Server 2010 title: Enable-OutlookAnywhere schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Enable-OutlookAnywhere @@ -17,34 +16,35 @@ This cmdlet is available only in Exchange Server 2010. Use the Enable-OutlookAnywhere cmdlet to enable Outlook Anywhere on a computer running Microsoft Exchange Server 2010 that has the Client Access server role installed. Running the Enable-OutlookAnywhere cmdlet enables the server to accept requests from Microsoft Office Outlook 2007 and Outlook 2003 client computers from the Internet by using Outlook Anywhere, also known as RPC over HTTP. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### CustomIdentity ``` -Enable-OutlookAnywhere -ClientAuthenticationMethod - -ExternalHostname -SSLOffloading [-IISAuthenticationMethods ] +Enable-OutlookAnywhere -ClientAuthenticationMethod -ExternalHostname -SSLOffloading + [-IISAuthenticationMethods ] [-Confirm] [-DomainController ] [-ExtendedProtectionFlags ] [-ExtendedProtectionSPNList ] [-ExtendedProtectionTokenChecking ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### DefaultIdentity ``` -Enable-OutlookAnywhere -DefaultAuthenticationMethod - -ExternalHostname -SSLOffloading +Enable-OutlookAnywhere -DefaultAuthenticationMethod -ExternalHostname -SSLOffloading [-Confirm] [-DomainController ] [-ExtendedProtectionFlags ] [-ExtendedProtectionSPNList ] [-ExtendedProtectionTokenChecking ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -54,7 +54,9 @@ This cmdlet can be successfully run only if the RPC over HTTP proxy Windows netw When you run this cmdlet, it can take as long as an hour for the settings to become effective, depending on how long it takes for Active Directory to replicate. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -85,7 +87,6 @@ This example enables the Exchange Client Access server for Outlook Anywhere. The 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 - - Ntlm This parameter must be specified if you don't use the DefaultAuthenticationMethod parameter. When you use this parameter without specifying the IISAuthenticationMethods parameter, IISAuthenticationMethods parameter is set to both NTLM and Basic. @@ -111,7 +112,6 @@ The DefaultAuthenticationMethod parameter specifies whether to set both the Clie 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: - Basic - - Ntlm If the DefaultAuthenticationMethod parameter is specified, neither the ClientAuthenticationMethod nor the IISAuthenticationMethods parameter can be used. @@ -164,8 +164,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -200,15 +199,11 @@ Accept wildcard characters: False ### -ExtendedProtectionFlags 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. - -- Proxy Specifies that a proxy is terminating the SSL channel. A Service Principal Name (SPN) must be registered in the ExtendedProtectionSPNList parameter if proxy mode is configured. - -- ProxyCoHosting Specifies that both HTTP and HTTPS traffic may be accessing the Client Access server and that a proxy is located between at least some of the clients and the Client Access server. - -- AllowDotlessSPN Specifies whether you want to support valid SPNs that aren't in the fully qualified domain name (FQDN) format, for example ContosoMail. You specify valid SPNs with the ExtendedProtectionSPNList parameter. This option makes extended protection less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - -- NoServiceNameCheck Specifies that the SPN list won't be checked to validate a channel binding token. This option makes Extended Protection for Authentication less secure. We generally don't recommend this setting. +- None: Default setting. +- Proxy: Specifies that a proxy is terminating the SSL channel. A Service Principal Name (SPN) must be registered in the ExtendedProtectionSPNList parameter if proxy mode is configured. +- ProxyCoHosting: Specifies that both HTTP and HTTPS traffic may be accessing the Client Access server and that a proxy is located between at least some of the clients and the Client Access server. +- AllowDotlessSPN: Specifies whether you want to support valid SPNs that aren't in the fully qualified domain name (FQDN) format, for example ContosoMail. You specify valid SPNs with the ExtendedProtectionSPNList parameter. This option makes extended protection less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. +- NoServiceNameCheck: Specifies that the SPN list won't be checked to validate a channel binding token. This option makes Extended Protection for Authentication less secure. We generally don't recommend this setting. ```yaml Type: MultiValuedProperty @@ -229,8 +224,7 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi The possible values are: - Null This is the default value. - -- Single SPN or comma delimited list of valid SPNs By default, you must specify the fully qualified domain name (FQDN) (for example mail.contoso.com) for each SPN. If you want to add an SPN that's not an FQDN (for example, ContosoMail), you must also use the ExtendedProtectionTokenChecking parameter with the AllowDotlessSPN value. You specify the domain in SPN format. The SPN format is \/\. For example, a valid entry could be HTTP/mail.contoso.com. +- Single SPN or comma delimited list of valid SPNs By default, you must specify the fully qualified domain name (FQDN) (for example mail.contoso.com) for each SPN. If you want to add an SPN that's not an FQDN (for example, ContosoMail), you must also use the ExtendedProtectionTokenChecking parameter with the AllowDotlessSPN value. You specify the domain in SPN format. The SPN format is `Protocol\FQDN` (for example, `HTTP/mail.contoso.com`). ```yaml Type: MultiValuedProperty @@ -249,7 +243,6 @@ Accept wildcard characters: False 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. - - Allow Extended Protection for Authentication will be used for connections between the client and Exchange on this virtual directory if both the client and server support Extended Protection for Authentication. Connections that don't support Extended Protection for Authentication on the client and server will work, but may not be as secure as a connection using Extended Protection for Authentication. If you have a proxy server between the client and the Client Access server that's configured to terminate the client-to-proxy SSL channel, you must also configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -258,7 +251,7 @@ If you have a proxy server between the client and the Client Access server that' If you have a proxy server between the client and the Client Access server that's configured to terminate the client-to-proxy SSL channel, you must also configure one or more SPNs using the parameter ExtendedProtectionSPNList. -To learn more about Extended Protection for Authentication, see [Understanding Extended Protection for Authentication](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/ff459225(v=exchg.141)). +To learn more about Extended Protection for Authentication, see [Understanding Extended Protection for Authentication](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ff459225(v=exchg.141)). ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -299,11 +292,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -340,13 +330,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### -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. +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md similarity index 87% rename from exchange/exchange-ps/exchange/policy-and-compliance/Enable-OutlookProtectionRule.md rename to exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md index 2955f5735f..63e2c39801 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Enable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md @@ -1,35 +1,39 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/enable-outlookprotectionrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-OutlookProtectionRule ## SYNOPSIS +**Note**: This cmdlet is no longer supported in the cloud-based service. + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Enable-OutlookProtectionRule cmdlet to enable an existing Outlook protection rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-OutlookProtectionRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Enable-OutlookProtectionRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -Outlook protection rules are used to automatically Information Rights Management (IRM)-protect messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://docs.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). +Outlook protection rules are used to automatically Information Rights Management (IRM)-protect messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Enable-PushNotificationProxy.md b/exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md similarity index 79% rename from exchange/exchange-ps/exchange/client-access/Enable-PushNotificationProxy.md rename to exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md index 660042a675..e23369448c 100644 --- a/exchange/exchange-ps/exchange/client-access/Enable-PushNotificationProxy.md +++ b/exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/enable-pushnotificationproxy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-PushNotificationProxy @@ -15,22 +14,26 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Enable-PushNotificationProxy cmdlet to enable a push notification proxy between an on-premises Microsoft Exchange organization and a Microsoft Office 365 organization. +Use the Enable-PushNotificationProxy cmdlet to enable a push notification proxy between an on-premises Microsoft Exchange organization and a Microsoft 365 organization. -In order for event notifications to be successfully delivered, you also need to configure OAuth authentication between your on-premises Exchange organization and your Office 365 organization. +In order for event notifications to be successfully delivered, you also need to configure OAuth authentication between your on-premises Exchange organization and your Microsoft 365 organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-PushNotificationProxy [-Confirm] [-Organization ] [-Uri ] [-WhatIf] [] +Enable-PushNotificationProxy [-Confirm] + [-Organization ] + [-Uri ] + [-WhatIf] + [] ``` ## DESCRIPTION -The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Office 365 to Outlook on the web for devices on the user's device. +The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,18 +46,17 @@ This example displays the status of the push notification proxy in the on-premis ### Example 2 ```powershell -Enable-PushNotificationProxy -Organization contoso.com +Enable-PushNotificationProxy -Organization contoso.onmicrosoft.com ``` -This example enables the push notification proxy in the on-premises Exchange organization by using the Office 365 organization contoso.com. +This example enables the push notification proxy in the on-premises Exchange organization by using the Microsoft 365 organization contoso.onmicrosoft.com. ## PARAMETERS ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -71,7 +73,7 @@ Accept wildcard characters: False ``` ### -Organization -The Organization parameter specifies the domain name of the Office 365 organization. For example, contoso.com. +The Organization parameter specifies the domain name of the Microsoft 365 organization. For example, contoso.onmicrosoft.com. ```yaml Type: String @@ -87,7 +89,7 @@ Accept wildcard characters: False ``` ### -Uri -The Uri parameter specifies the push notification service endpoint in Office 365. The default value is https://outlook.office365.com/PushNotifications. +The Uri parameter specifies the push notification service endpoint in Microsoft 365. The default value is . ```yaml Type: String @@ -123,12 +125,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Enable-RemoteMailbox.md b/exchange/exchange-ps/exchange/Enable-RemoteMailbox.md similarity index 83% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Enable-RemoteMailbox.md rename to exchange/exchange-ps/exchange/Enable-RemoteMailbox.md index b100b15d63..e2ca574784 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Enable-RemoteMailbox.md +++ b/exchange/exchange-ps/exchange/Enable-RemoteMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/enable-remotemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-RemoteMailbox @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service for an existing user in the on-premises Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,12 +30,14 @@ Enable-RemoteMailbox [-Identity] [-DisplayName ] [-DomainController ] [-PrimarySmtpAddress ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Room ``` -Enable-RemoteMailbox [-Identity] [-Room] +Enable-RemoteMailbox [-Identity] + [-Room] [-ACLableSyncedObjectEnabled] [-Alias ] [-Confirm] @@ -44,12 +45,14 @@ Enable-RemoteMailbox [-Identity] [-Room] [-DomainController ] [-PrimarySmtpAddress ] [-RemoteRoutingAddress ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Equipment ``` -Enable-RemoteMailbox [-Identity] [-Equipment] +Enable-RemoteMailbox [-Identity] + [-Equipment] [-ACLableSyncedObjectEnabled] [-Alias ] [-Confirm] @@ -57,31 +60,38 @@ Enable-RemoteMailbox [-Identity] [-Equipment] [-DomainController ] [-PrimarySmtpAddress ] [-RemoteRoutingAddress ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Archive ``` -Enable-RemoteMailbox [-Identity] [-Archive] [-ArchiveName ] +Enable-RemoteMailbox [-Identity] + [-Archive] + [-ArchiveName ] [-ACLableSyncedObjectEnabled] [-Alias ] [-Confirm] [-DisplayName ] [-DomainController ] [-PrimarySmtpAddress ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Shared ``` -Enable-RemoteMailbox [-Identity] [-Shared] - [-ACLableSyncedObjectEnabled [-Alias ] +Enable-RemoteMailbox [-Identity] + [-Shared] + [-ACLableSyncedObjectEnabled] + [-Alias ] [-Confirm] [-DisplayName ] [-DomainController ] [-PrimarySmtpAddress ] [-RemoteRoutingAddress ] - [-WhatIf]] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -91,7 +101,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -102,13 +112,12 @@ Enable-RemoteMailbox "Kim Akers" -RemoteRoutingAddress "kima@contoso.mail.onmicr This example mail-enables an existing on-premises user and creates an associated mailbox in the service. -To mail-enable an existing user and create an associated mailbox in the service, run the New-RemoteMailbox cmdlet and specify the identity of the existing user. - After the user is mail-enabled, directory synchronization synchronizes the mail-enabled user to the service and the associated mailbox is created. ### Example 2 ```powershell Enable-RemoteMailbox "Kim Akers" -RemoteRoutingAddress "kima@contoso.mail.onmicrosoft.com" + Enable-RemoteMailbox "Kim Akers" -Archive ``` @@ -128,17 +137,11 @@ To mail-enable an on-premises user, create the associated mailbox in the service 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 - - GUID - - Distinguished name (DN) - -- Domain\\SamAccountName - +- Domain\\Username - User principal name (UPN) - - LegacyExchangeDN - - User alias ```yaml @@ -193,7 +196,7 @@ Accept wildcard characters: False ``` ### -Shared -**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/cmdlets-to-create-modify-remote-shared-mailbox-in-on-premises-exchange). +**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. @@ -229,16 +232,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -259,7 +266,7 @@ Accept wildcard characters: False ``` ### -Archive -The Archive switch specifies whether to create an archive mailbox in the service in addition to the mailbox created in the service. You don't need to specify a value with this switch. +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 @@ -275,7 +282,15 @@ Accept wildcard characters: False ``` ### -ArchiveName -The ArchiveName parameter specifies the name of the archive mailbox. Use this parameter to change the name of the archive. +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: + +- Exchange 2016 or later: `In-Place Archive -` +- Exchange 2013: `In-Place Archive - ` +- Exchange 2010: `Personal Archive - ` + +In Outlook, the value of this parameter is ignored. The name of the archive mailbox that's shown in the folder list is `Online Archive - `. ```yaml Type: MultiValuedProperty @@ -293,8 +308,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -395,12 +409,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md new file mode 100644 index 0000000000..9bf1aa79ac --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md @@ -0,0 +1,104 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-ReportSubmissionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-ReportSubmissionRule cmdlet to enable the report submission rule in your cloud-based organization. The report submission rule identifies the reporting mailbox where user reported messages are delivered. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-ReportSubmissionRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-ReportSubmissionRule -Identity DefaultReportSubmissionRule. +``` + +This example enables the report submission rule if it's already disabled. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md new file mode 100644 index 0000000000..2642212149 --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-SafeAttachmentRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-SafeAttachmentRule cmdlet to enable safe attachment rules in your cloud-based organization. This cmdlet is also responsible for disabling complete Safe Attachments policies in the admin center, which consist of the safe attachment rule and the corresponding assigned safe attachment policy in PowerShell. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-SafeAttachmentRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-SafeAttachmentRule -Identity "Marketing Department Attachment Rule" +``` + +This example enables the disabled safe attachment rule named Marketing Department Attachment Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Enable-SafeLinksRule.md b/exchange/exchange-ps/exchange/Enable-SafeLinksRule.md new file mode 100644 index 0000000000..1314b22664 --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-SafeLinksRule.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-SafeLinksRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-SafeLinksRule cmdlet to enable disabled Safe Links rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-SafeLinksRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-SafeLinksRule -Identity "Marketing Department URL Rule" +``` + +This example enables the disabled Safe Links rule named Marketing Department URL Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Enable-ServiceEmailChannel.md b/exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Enable-ServiceEmailChannel.md rename to exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md index b6e131c191..206921ec6f 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Enable-ServiceEmailChannel.md +++ b/exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/enable-serviceemailchannel +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-ServiceEmailChannel @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-ServiceEmailChannel cmdlet to enable the .NET service channel for a specific user. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-ServiceEmailChannel [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Enable-ServiceEmailChannel [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The .NET service channel enables Microsoft Exchange to store information that it later forwards to applications or devices that aren't permanently connected to the server running Exchange. This cmdlet creates a receive folder in the user's mailbox under the root folder named Service E-mail. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,23 +64,14 @@ The Identity parameter specifies the identity of the user for which you want to You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -97,8 +90,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -151,12 +143,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md b/exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md new file mode 100644 index 0000000000..84502bb3b4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Enable-SmtpDaneInbound + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Enable-SMTPDaneInbound cmdlet to enable SMTP DNS-based Authentication of Named Entities (DANE) for inbound mail to accepted domains in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Enable-SmtpDaneInbound [-DomainName] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Enable-SmtpDaneInbound -DomainName contoso.com +``` + +This example enables SMTP DANE for mail sent to contoso.com. + +## PARAMETERS + +### -DomainName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Enable-SweepRule.md b/exchange/exchange-ps/exchange/Enable-SweepRule.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Enable-SweepRule.md rename to exchange/exchange-ps/exchange/Enable-SweepRule.md index 39f183a36a..a5d16d3d5f 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Enable-SweepRule.md +++ b/exchange/exchange-ps/exchange/Enable-SweepRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/enable-sweeprule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-SweepRule @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-SweepRule cmdlet to enable Sweep rules in mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-SweepRule [-Identity] [-Confirm] [-DomainController ] - [-Mailbox ] [-WhatIf] [] +Enable-SweepRule [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,10 +54,8 @@ This example enables all Sweep rules in the specified mailbox. 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==). - -- Exchange Online: \\\\ (for example, rzaher\\x2hlsdpGmUifjFgxxGIOJw==. - -- On-premises Exchange: \\\\ (for example, contoso.com/Users/Rick Zaher\\x2hlsdpGmUifjFgxxGIOJw==. +- Exchange Online: `MailboxAlias\RuleID` (for example, `rzaher\2hlsdpGmUifjFgxxGIOJw==`). +- On-premises Exchange: `MailboxCanonicalName\RuleID` (for example, `contoso.com/Users/Rick Zaher\x2hlsdpGmUifjFgxxGIOJw==`). ```yaml Type: SweepRuleIdParameter @@ -72,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -111,23 +111,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -164,12 +155,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Enable-TransportAgent.md b/exchange/exchange-ps/exchange/Enable-TransportAgent.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Enable-TransportAgent.md rename to exchange/exchange-ps/exchange/Enable-TransportAgent.md index 2cee95d27b..1985292cfa 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Enable-TransportAgent.md +++ b/exchange/exchange-ps/exchange/Enable-TransportAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/enable-transportagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-TransportAgent @@ -17,17 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-TransportAgent cmdlet to enable a transport agent. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-TransportAgent [-Identity] [-Confirm] [-DomainController ] [-WhatIf] - [-TransportService ] [] +Enable-TransportAgent [-Identity] + [-Confirm] + [-DomainController ] + [-TransportService ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +62,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -94,33 +96,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -TransportService 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. - - MailboxSubmission for the Mailbox Transport Submission service on Mailbox servers. - - MailboxDelivery for the Mailbox Transport Delivery service on Mailbox servers. - - FrontEnd for the Front End Transport service on Mailbox servers. - - Edge on Edge Transport servers. ```yaml @@ -136,17 +118,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Enable-TransportRule.md b/exchange/exchange-ps/exchange/Enable-TransportRule.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance/Enable-TransportRule.md rename to exchange/exchange-ps/exchange/Enable-TransportRule.md index dd8b9bf41d..4f9a620693 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Enable-TransportRule.md +++ b/exchange/exchange-ps/exchange/Enable-TransportRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/enable-transportrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Enable-TransportRule @@ -17,19 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-TransportRule cmdlet to enable transport rules (mail flow rules) in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-TransportRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] - [-Mode ] [] +Enable-TransportRule [-Identity] + [-Confirm] + [-DomainController ] + [-Mode ] + [-WhatIf] + [] ``` ## DESCRIPTION To disable rules that are enabled, use the Disable-TransportRule cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,9 +56,7 @@ This example enables the transport rule named "Require approval of messages to c The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -74,8 +75,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -111,14 +111,20 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -Mode +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. +- AuditAndNotify: The rule operates the same as in Audit mode, but notifications are also enabled. +- Enforce: All actions specified in the rule are taken. + +The value that has already been set in the rule will be persevered, unless -Mode parameter is specified. ```yaml -Type: SwitchParameter +Type: RuleMode Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -127,20 +133,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Mode -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. - -- AuditAndNotify: The rule operates the same as in Audit mode, but notifications are also enabled. - -- Enforce: All actions specified in the rule are taken. This is the default value. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: RuleMode +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -154,12 +154,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Enable-UMAutoAttendant.md rename to exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md index 459885c27f..b5a6029718 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMAutoAttendant.md +++ b/exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md @@ -1,35 +1,37 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/enable-umautoattendant -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-UMAutoAttendant ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Enable-UMAutoAttendant cmdlet to enable an existing Unified Messaging (UM) auto attendant that's disabled. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-UMAutoAttendant [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Enable-UMAutoAttendant [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The Enable-UMAutoAttendant cmdlet enables the UM auto attendant by modifying its status variable. When you create a UM auto attendant, it isn't enabled by default. For the auto attendant to answer incoming calls, you must first enable it. After this task is completed, the UM auto attendant answers incoming calls. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,7 +51,7 @@ The Identity parameter specifies the identifier for the UM auto attendant being Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -61,15 +63,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -79,15 +80,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -103,7 +102,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -117,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Enable-UMCallAnsweringRule.md rename to exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md index 531eca9ab6..871ebf54fd 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md @@ -1,29 +1,32 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/enable-umcallansweringrule -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-UMCallAnsweringRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Enable-UMCallAnsweringRule cmdlet to enable a call answering rule that has been created within a UM-enabled mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-UMCallAnsweringRule [-Identity] [-Confirm] [-DomainController ] - [-Mailbox ] [-WhatIf] [] +Enable-UMCallAnsweringRule [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +34,7 @@ The Enable-UMCallAnsweringRule cmdlet enables the call answering rule by modifyi After this task is completed, the cmdlet sets the parameters and values specified. When you enable a call answering rule, the call answering rule is processed when an incoming call is received. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,7 +68,7 @@ The Identity parameter specifies the UM call answering rule in a UM-enabled mail Type: UMCallAnsweringRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -77,15 +80,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -95,15 +97,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -116,23 +116,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the mailbox of the user who is running the command is used. @@ -141,7 +132,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -157,7 +148,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -171,12 +162,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMIPGateway.md b/exchange/exchange-ps/exchange/Enable-UMIPGateway.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Enable-UMIPGateway.md rename to exchange/exchange-ps/exchange/Enable-UMIPGateway.md index dee6f5b9d6..2b49427750 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMIPGateway.md +++ b/exchange/exchange-ps/exchange/Enable-UMIPGateway.md @@ -1,28 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/enable-umipgateway -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-UMIPGateway ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Enable-UMIPGateway cmdlet to enable a Unified Messaging (UM) IP gateway. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-UMIPGateway [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Enable-UMIPGateway [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ The status variable for a UM IP gateway can be used to enable or disable call an After this task is completed, the UM IP gateway answers incoming calls and makes outgoing calls through the IP gateway or IP Private Branch eXchange (PBX). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +53,7 @@ The Identity parameter specifies the identifier for the UM IP gateway being enab Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,15 +65,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -81,15 +82,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -105,7 +104,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMMailbox.md b/exchange/exchange-ps/exchange/Enable-UMMailbox.md similarity index 84% rename from exchange/exchange-ps/exchange/unified-messaging/Enable-UMMailbox.md rename to exchange/exchange-ps/exchange/Enable-UMMailbox.md index 8bd3d78d6e..64d7a8d5d7 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMMailbox.md +++ b/exchange/exchange-ps/exchange/Enable-UMMailbox.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/enable-ummailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Enable-UMMailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Enable-UMMailbox cmdlet to enable Unified Messaging (UM) for existing mailbox users. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -35,12 +34,14 @@ Enable-UMMailbox [-Identity] -UMMailboxPolicy ] [-SIPResourceIdentifier ] [-ValidateOnly] - [-WhatIf] [] + [-WhatIf] + [] ``` ### CloudVoiceMail ``` -Enable-UMMailbox [-Identity] [-EnableCloudVoiceMail] +Enable-UMMailbox [-Identity] + [-EnableCloudVoiceMail] [-AutomaticSpeechRecognitionEnabled ] [-Confirm] [-DomainController ] @@ -54,13 +55,14 @@ Enable-UMMailbox [-Identity] [-EnableCloudVoiceMail] [-SIPResourceIdentifier ] [-UMMailboxPolicy ] [-ValidateOnly] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION When the mailbox is enabled for Unified Messaging, the settings from a UM mailbox policy are applied to the mailbox. After the mailbox is enabled for Unified Messaging, the user can use the UM features that are included in Microsoft Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,30 +86,21 @@ This example enables Unified Messaging on a SIP-enabled mailbox for tonysmith@co 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -120,16 +113,14 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID ```yaml Type: MailboxPolicyIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -142,7 +133,7 @@ Accept wildcard characters: False Type: MailboxPolicyIdParameter Parameter Sets: CloudVoiceMail Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -155,14 +146,13 @@ Accept wildcard characters: False 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. - - $false: ASR is disabled for the mailbox. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -174,15 +164,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -192,15 +181,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -216,7 +203,7 @@ The EnableCloudVoiceMail switch specifies whether to enable the mailbox for UM i Type: SwitchParameter Parameter Sets: CloudVoiceMail Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016 Required: True Position: Named @@ -234,7 +221,7 @@ If you don't use this parameter, the command attempts to use a default telephone Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -244,21 +231,18 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -274,7 +258,7 @@ The NotifyEmail parameter specifies the email address where the Unified Messagin Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -290,7 +274,7 @@ The PilotNumber parameter specifies the subscriber access number users can dial Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -308,7 +292,7 @@ If you don't use this parameter, a system-generated PIN is sent to the user. By Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -321,14 +305,13 @@ Accept wildcard characters: False 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. - - $false: The user isn't required to reset their PIN the next time they log on. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -341,14 +324,13 @@ Accept wildcard characters: False 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. - - $false: Don't send the welcome to UM message. ```yaml Type: Boolean Parameter Sets: CloudVoiceMail Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016 Required: False Position: Named @@ -364,7 +346,7 @@ The SIPResourceIdentifier parameter specifies the SIP address or E.164 address f Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -374,13 +356,15 @@ Accept wildcard characters: False ``` ### -ValidateOnly -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. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -396,7 +380,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -410,12 +394,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMServer.md b/exchange/exchange-ps/exchange/Enable-UMServer.md similarity index 90% rename from exchange/exchange-ps/exchange/unified-messaging/Enable-UMServer.md rename to exchange/exchange-ps/exchange/Enable-UMServer.md index e85aebc24a..01417d0e76 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMServer.md +++ b/exchange/exchange-ps/exchange/Enable-UMServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/enable-umserver +online version: https://learn.microsoft.com/powershell/module/exchange/enable-umserver applicable: Exchange Server 2010 title: Enable-UMServer schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Enable-UMServer @@ -17,12 +16,15 @@ This cmdlet is available only in Exchange Server 2010. Use the Enable-UMServer cmdlet to set the status of a Unified Messaging (UM) server to enabled. This enables the Unified Messaging server to process UM calls. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-UMServer [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Enable-UMServer [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ The Enable-UMServer cmdlet sets the status of a Unified Messaging server. A UM s After this task is completed, the Unified Messaging server is available to answer incoming calls. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMService.md b/exchange/exchange-ps/exchange/Enable-UMService.md similarity index 79% rename from exchange/exchange-ps/exchange/unified-messaging/Enable-UMService.md rename to exchange/exchange-ps/exchange/Enable-UMService.md index e5e3f33cab..d0441b4357 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Enable-UMService.md +++ b/exchange/exchange-ps/exchange/Enable-UMService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/enable-umservice -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Enable-UMService @@ -17,14 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Enable-UMService cmdlet to set the status of an Exchange Server 2010 Unified Messaging (UM) server to enabled. This setting enables the Unified Messaging server to process UM calls. -You can run this cmdlet in Exchange 2013 or later, but the target server must be an Exchange 2010 UM server. You can't use this cmdlet to enable the UM service on Exchange 2013 or Exchange 2016 Mailbox servers. +You can run this cmdlet in Exchange 2013 or Exchange 2016, but the target server must be an Exchange 2010 UM server. You can't use this cmdlet to enable the UM service on Exchange 2013 or Exchange 2016 Mailbox servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Enable-UMService [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Enable-UMService [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -33,7 +35,7 @@ The Enable-UMService cmdlet sets the status of an Exchange server running the Un After this task is completed, the UM server is available to answer incoming calls. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,18 +52,15 @@ This example enables Unified Messaging on the UM server MyUMServer. 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 - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml Type: UMServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -73,15 +72,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -97,7 +95,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -113,7 +111,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -127,12 +125,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md b/exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md new file mode 100644 index 0000000000..8da13825b6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md @@ -0,0 +1,50 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Execute-AzureADLabelSync + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Execute-AzureADLabelSync cmdlet to start the synchronization of sensitivity labels into Microsoft Entra ID. This allows the application of sensitivity labels to Microsoft Teams sites, Microsoft 365 Groups, and SharePoint sites. This cmdlet is required if you were using sensitivity labels before September 2019. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Execute-AzureADLabelSync [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Execute-AzureADLabelSync +``` + +This example will initialize the synchronization of sensitivity labels into Microsoft Entra ID. + +## 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Expedite-Delicensing.md b/exchange/exchange-ps/exchange/Expedite-Delicensing.md new file mode 100644 index 0000000000..f5c2af5041 --- /dev/null +++ b/exchange/exchange-ps/exchange/Expedite-Delicensing.md @@ -0,0 +1,77 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Expedite-Delicensing + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Expedite-Delicensing cmdlet to end the delay for removing mailbox licenses from users. After you remove the delay, the licenses are removed from mailboxes within 24 hours. You configure delayed mailbox license removal using the DelayedDelicensingEnabled parameter on the Set-OrganizationConfig cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Expedite-Delicensing [-Identity] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Expedite-Delicensing -Identity yajvendra@contoso.onmicrosoft.com +``` + +This example ends the delay for the mailbox license removal request on the specified mailbox. Typically, the mailbox license is removed from the mailbox within 30 minutes after running the command, but it might take up to 24 hours. + +## PARAMETERS + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Email address +- GUID +- LegacyExchangeDN +- User ID or user principal name (UPN) + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Export-ActiveSyncLog.md b/exchange/exchange-ps/exchange/Export-ActiveSyncLog.md similarity index 87% rename from exchange/exchange-ps/exchange/devices/Export-ActiveSyncLog.md rename to exchange/exchange-ps/exchange/Export-ActiveSyncLog.md index 547258441f..2af091f5e0 100644 --- a/exchange/exchange-ps/exchange/devices/Export-ActiveSyncLog.md +++ b/exchange/exchange-ps/exchange/Export-ActiveSyncLog.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/export-activesynclog +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Export-ActiveSyncLog @@ -17,19 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Export-ActiveSyncLog cmdlet to parse the Internet Information Services (IIS) logs and return information about Microsoft Exchange ActiveSync usage, either on the screen or in an output file. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Export-ActiveSyncLog -Filename [-Confirm] [-EndDate ] [-Force] [-OutputPath ] - [-OutputPrefix ] [-StartDate ] [-UseGMT] [-WhatIf] [] +Export-ActiveSyncLog -Filename + [-Confirm] + [-EndDate ] + [-Force] + [-OutputPath ] + [-OutputPrefix ] + [-StartDate ] + [-UseGMT] + [-WhatIf] + [] ``` ## DESCRIPTION The Export-ActiveSyncLog cmdlet parses the IIS log files and returns information about Exchange ActiveSync usage. This cmdlet can export the output to a file or display it in the Exchange Management Shell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -75,8 +82,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -109,7 +115,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -173,7 +181,9 @@ Accept wildcard characters: False ``` ### -UseGMT -The UseGMT switch specifies that Coordinated Universal Time (Greenwich Mean Time) is used for the time in the report output. By default, if this parameter isn't specified, local time is used. +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. ```yaml Type: SwitchParameter @@ -209,12 +219,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Export-ActivityExplorerData.md b/exchange/exchange-ps/exchange/Export-ActivityExplorerData.md new file mode 100644 index 0000000000..8d5bf12471 --- /dev/null +++ b/exchange/exchange-ps/exchange/Export-ActivityExplorerData.md @@ -0,0 +1,413 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Export-ActivityExplorerData + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Export-ActivityExplorerData cmdlet to export activities from Data classification \> Activity Explorer in the Microsoft 365 Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Export-ActivityExplorerData -EndTime -OutputFormat -StartTime + [-Filter1 ] + [-Filter2 ] + [-Filter3 ] + [-Filter4 ] + [-Filter5 ] + [-PageCookie ] + [-PageSize ] + [] +``` + +## DESCRIPTION +This cmdlet supports following filters: + +- Activity +- Application +- ArtifactType +- ClientIP +- ColdScanPolicyId +- CopilotAppHost +- CopilotThreadId +- CopilotType +- CreationTime +- DataState +- DestinationFilePath +- DestinationLocationType +- DeviceName +- DLPPolicyId +- DLPPolicyRuleId +- EmailReceiver +- EmailSender +- EndpointOperation +- EnforcementMode +- FalsePositive +- FileExtension +- GeneralPurposeComparison +- HowApplied +- HowAppliedDetail +- IrmUrlCategory +- IsProtected +- IsProtectedBefore +- ItemName +- LabelEventType +- Location +- MDATPDeviceId +- OriginatingDomain +- PageSize +- ParentArchiveHash +- Platform +- PolicyId +- PolicyMode +- PolicyName +- PolicyRuleAction +- PolicyRuleId +- PolicyRuleName +- PreviousFileName +- PreviousProtectionOwner +- ProtectionEventType +- ProtectionOwner +- RemovableMediaDeviceManufacturer +- RemovableMediaDeviceModel +- RemovableMediaDeviceSerialNumber +- RetentionLabel +- RMSEncrypted +- SensitiveInfoTypeClassifierType +- SensitiveInfoTypeConfidence +- SensitiveInfoTypeCount +- SensitiveInfoTypeId +- SensitivityLabel +- SensitivityLabelPolicy +- Sha1 +- Sha256 +- SourceLocationType +- TargetDomain +- TargetPrinterName +- User +- UsersPerDay +- Workload + +Valid workload filters include the following values: + +- Copilot +- Endpoint +- Exchange +- OnPremisesFileShareScanner +- OnPremisesSharePointScanner +- OneDrive +- PowerBI +- PurviewDataMap +- SharePoint + +Valid activity filters include the following values: + +- AIAppInteraction +- ArchiveCreated +- AutoLabelingSimulation +- BrowseToUrl +- ChangeProtection +- ClassificationAdded +- ClassificationDeleted +- ClassificationUpdated +- CopilotInteraction +- DLPInfo +- DLPRuleEnforce +- DLPRuleMatch +- DLPRuleUndo +- DlpClassification +- DownloadFile +- DownloadText +- FileAccessedByUnallowedApp +- FileArchived +- FileCopiedToClipboard +- FileCopiedToNetworkShare +- FileCopiedToRemoteDesktopSession +- FileCopiedToRemovableMedia +- FileCreated +- FileCreatedOnNetworkShare +- FileCreatedOnRemovableMedia +- FileDeleted +- FileDiscovered +- FileModified +- FilePrinted +- FileRead +- FileRenamed +- FileTransferredByBluetooth +- FileUploadedToCloud +- LabelApplied +- LabelChanged +- LabelRecommended +- LabelRecommendedAndDismissed +- LabelRemoved +- NewProtection +- PastedToBrowser +- RemoveProtection +- ScreenCapture +- UploadFile +- UploadText +- WebpageCopiedToClipboard +- WebpagePrinted +- WebpageSavedToLocal + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Export-ActivityExplorerData -StartTime "07/08/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -PageSize 5000 -OutputFormat Json +``` + +This example exports a maximum of 5000 records for the specified date range in JSON format. + +### Example 2 +```powershell +Export-ActivityExplorerData -StartTime "07/08/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -OutputFormat Json +``` + +This example exports up to 100 records for the specified date range in Json format. If more than 100 records are available, the value of the LastPage property in the command output will be False. Use the value of the Watermark property as the value of the PageCookie parameter in a new query to get the next set of records. + +### Example 3 +```powershell +$res = Export-ActivityExplorerData -StartTime "07/08/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -PageSize 5000 -OutputFormat Json + +#Run the following steps in loop until all results are fetched + +while ($res.LastPage -ne $true) +{ + $pageCookie = $res.WaterMark + $res = Export-ActivityExplorerData -StartTime "07/08/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -PageSize 5000 -OutputFormat Json -PageCookie $pageCookie +} +``` + +This example is related to the previous example where more than 100 records were available (the value of the LastPage property from that command was False). We're using the same date range, but this time we're using the value of the Watermark property from the previous command for the PageCookie parameter in this command to get the remaining results in a loop. ResultData from each iteration can be used as needed. + +### Example 4 +```powershell +Export-ActivityExplorerData -StartTime "07/06/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -Filter1 @("Activity", "FileArchived") -OutputFormat Csv +``` + +This example exports up to 100 records for the specified date range in CSV format, and filters the output by the Activity value FileArchived. + +### Example 5 +```powershell +Export-ActivityExplorerData -StartTime "07/06/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -Filter1 @("Activity", "FileArchived", "ArchiveCreated") -OutputFormat Json +``` + +This example exports up to 100 records for the specified date range in JSON format, and filters the output by the Activity value FileArchived or ArchiveCreated. + +### Example 6 +```powershell +Export-ActivityExplorerData -StartTime "07/06/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -Filter1 @("Activity", "FileArchived", "ArchiveCreated") -Filter2 @("Workload","Endpoint") -OutputFormat Json +``` + +This example exports up to 100 records for the specified date range in JSON format, and filters the output by the Workload value Endpoint for FileArchived or ArchiveCreated activities. + +## PARAMETERS + +### -EndTime +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutputFormat +The OutputFormat parameter specifies the output format. Valid values are: + +- Csv +- Json + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Accepted values: csv, json +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartTime +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter1 +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`. + +If you use this parameter with other filter parameters, AND behavior is used across parameters. For example: + +`-Filter1 @("Activity", "LabelApplied", "LabelRemoved") -Filter2 = @("Workload", "Exchange")` returns records with the activity values `LabelApplied` or `LabelRemoved` for the `Exchange` workload. In other words, ((`Activity eq LabelApplied`) OR (`Activity eq LabelRemoved`)) AND (`Workload eq Exchange`). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter2 +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter3 +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter4 +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter5 +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageCookie +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES +- The date-time field exported via this cmdlet is in UTC timezone. + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access/Export-AutoDiscoverConfig.md b/exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access/Export-AutoDiscoverConfig.md rename to exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md index 2d100c586f..01b6148ebe 100644 --- a/exchange/exchange-ps/exchange/client-access/Export-AutoDiscoverConfig.md +++ b/exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/export-autodiscoverconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Export-AutoDiscoverConfig @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Export-AutoDiscoverConfig cmdlet to create or update a service connection point for an Autodiscover service pointer in a target Exchange forest. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` @@ -29,13 +28,14 @@ Export-AutoDiscoverConfig -TargetForestDomainController [-PreferredSourceFqdn ] [-SourceForestCredential ] [-TargetForestCredential ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Autodiscover Service Connection Point pointer resides Active Directory in the user account forest and includes the LDAP URL of the resource forest that the client will use to locate the Autodiscover service in the resource forest. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,8 +76,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,7 +125,10 @@ Accept wildcard characters: False ``` ### -MultipleExchangeDeployments -The MultipleExchangeDeployments parameter specifies whether multiple Exchange deployments exist. This setting should be set to $true only if Exchange 2016 is deployed in more than one Active Directory forest, and the forests are connected. If set to $true, the list of authoritative accepted domains for the source forest is written to the Autodiscover service connection point object. Outlook 2010 clients use this object to select the most appropriate forest to search for the Autodiscover service. +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. +- $False: Multiple Exchange deployments aren't used. This is the default value. ```yaml Type: Boolean @@ -160,7 +162,7 @@ Accept wildcard characters: False ### -SourceForestCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -178,7 +180,7 @@ Accept wildcard characters: False ### -TargetForestCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -214,12 +216,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Export-ContentExplorerData.md b/exchange/exchange-ps/exchange/Export-ContentExplorerData.md new file mode 100644 index 0000000000..85f8802e21 --- /dev/null +++ b/exchange/exchange-ps/exchange/Export-ContentExplorerData.md @@ -0,0 +1,242 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Export-ContentExplorerData + +## SYNOPSIS +**Note**: This cmdlet is currently in Preview and is subject to change. + +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Export-ContentExplorerData cmdlet to export data classification file details in Microsoft Purview compliance. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Export-ContentExplorerData [-TagName] [-TagType] + [-Aggregate] + [[-PageCookie] ] + [[-PageSize] ] + [[-SiteUrl] ] + [[-UserPrincipalName] ] + [[-Workload] ] + [] +``` + +## DESCRIPTION +The output of this cmdlet contains the following information: + +- TotalCount: Aggregate count. If only the TagName and TagType parameters are used, the value is the total aggregate count for that tag. If the Workload parameter is also used, the value is the aggregate count in the workload for that tag. If the UserPrincipalName or SiteUrl parameters are used, the value is the count for that specific folder. +- MorePagesAvailable: Shows whether there are more records left to export. The value is True or False. +- RecordsReturned: The number of records returned in the query. +- PageCookie: Used to get the next set of records when MorePagesAvailable is True. + +The following list describes best practices for scripts using this cmdlet: + +- We recommend not using a single script to export multiple SITs/Labels. Instead, create a script for one SIT/Label, and then re-use the same script for each SIT/Label in each workload as required. +- When retrying the script, make sure to reconnect to the session first. The session's token expires after about an hour, which can cause the cmdlet to fail. To fix this issue, reconnect to the session before retrying the script. If the script fails, restart it using the last page cookie returned to continue the export from where it left off. + + > [!TIP] + > To support unattended scripts that run for a long time, you can use [certificate-based authentication (CBA)](https://learn.microsoft.com/powershell/exchange/app-only-auth-powershell-v2). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Export-ContentExplorerData -TagType SensitiveInformationType -TagName "Credit Card Number" -Workload EXO -UserPrincipalName erika@contoso.onmicrosoft.com +``` + +This example exports records for the specified sensitive info type from Erika's mailbox. + +### Example 2 +```powershell +Export-ContentExplorerData -TagType SensitiveInformationType -TagName "Credit Card Number" -Workload ODB -SiteUrl https://contoso-my.sharepoint.com/personal/erika_contoso_onmicrosoft_com +``` + +This example exports records for the specified sensitive info type in Erika's OneDrive site. + +### Example 3 +```powershell +Export-ContentExplorerData -TagType SensitiveInformationType -TagName "All Full Names" +``` + +This example exports records for the specified sensitive info type for all workloads. + +## PARAMETERS + +### -TagType +The TagType parameter specifies the type of label to export file details from. Valid values are: + +- Retention +- SensitiveInformationType +- Sensitivity +- TrainableClassifier + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 5 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Aggregate +**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. + +Using this switch significantly reduces the export time. To download the items in a folder, run this cmdlet for specific folders. + +When you use this switch with the TagName, TagType, and Workload parameters, the command returns the following information: + +- SharePoint and OneDrive: The list of SiteUlrs. +- Exchange Online and Microsoft Teams: The list of UPNs. +- The count of items in the folders stamped with relevant tag. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageCookie +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 2 +Default value: 0 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteUrl +The SiteUrl parameter specifies the site URL to export file details from. + +You use this parameter for SharePoint and OneDrive workloads. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TagName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 6 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Workload +The Workload parameter specifies the location to export file details from. Valid values are: + +- EXO or Exchange +- ODB or OneDrive +- SPO or SharePoint +- Teams + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 7 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Export-DlpPolicyCollection.md b/exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md similarity index 81% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Export-DlpPolicyCollection.md rename to exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md index bf045820e9..0c2de21c86 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Export-DlpPolicyCollection.md +++ b/exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md @@ -1,52 +1,73 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/export-dlppolicycollection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Export-DlpPolicyCollection ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). -Use the Export-DlpPolicyCollection cmdlet to export data loss prevention (DLP) policy collections from your organization to a file. +This cmdlet is functional only in on-premises Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the Export-DlpPolicyCollection cmdlet to export data loss prevention (DLP) policy collections that are based on transport rules (mail flow rules) from your organization to a file. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Export-DlpPolicyCollection [[-Identity] ] [-Confirm] [-DomainController ] [-WhatIf] +Export-DlpPolicyCollection [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The Export-DlpPolicyCollection cmdlet exports the settings of the DLP policies and the associated transport rules. You use the Import-DlpPolicyCollection to import the DLP policy collection into your organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$file = Export-DlpPolicyCollection; Set-Content -Path "C:\My Documents\Contoso PII.xml" -Value $file.FileData -Encoding Byte +$DlpPol = Export-DlpPolicyCollection + +[System.IO.File]::WriteAllBytes('C:\My Documents\Contoso PII.xml', $DlpPol.FileData) ``` This example exports all the elements of the existing DLP policies to the file C:\\My Documents\\Contoso PII.xml. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -63,8 +84,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -80,22 +99,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -117,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Export-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Export-ExchangeCertificate.md new file mode 100644 index 0000000000..ec431d5516 --- /dev/null +++ b/exchange/exchange-ps/exchange/Export-ExchangeCertificate.md @@ -0,0 +1,306 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Export-ExchangeCertificate + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Export-ExchangeCertificate cmdlet to export existing certificates and pending certificate requests (also known as certificate signing requests or CSRs) from Exchange servers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Thumbprint +``` +Export-ExchangeCertificate [-Thumbprint] + [-Server ] + [-BinaryEncoded] + [-Confirm] + [-DomainController ] + [-FileName ] + [-Password ] + [-WhatIf] + [] +``` + +### Identity +``` +Export-ExchangeCertificate [[-Identity] ] + [-BinaryEncoded] + [-Confirm] + [-DomainController ] + [-FileName ] + [-Password ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Export-ExchangeCertificate cmdlet creates the following types of files: + +- Certificate files: When you export a certificate, the command creates a PKCS #12 file. PKCS #12 is the Personal Information Exchange Syntax standard specified by RSA Laboratories. For more information, see [PKCS #12: Personal Information Exchange Syntax Standard](https://www.emc.com/emc-plus/rsa-labs/standards-initiatives/pkcs12-personal-information-exchange-syntax-standard.htm). + + To export a certificate from an Exchange server, the certificate's PrivateKeyExportable property needs to have the value True. To import an exported certificate on another Exchange server, you need to export the certificate by using the Password parameter to include the private key or chain of trust in the certificate file. The default Microsoft Exchange self-signed certificate or new self-signed certificates that you create in the Exchange admin center or by using the default settings of the New-ExchangeCertificate cmdlet aren't exportable, because the private key isn't exportable (the default value of the PrivateKeyExportable parameter is $false). + +- Certificate request files: When you export a certificate request, the command creates a PKCS #10 file. PKCS #10 is the Certification Request Syntax standard specified by RFC 2314. For more information, see [PKCS #10: Certification Request Syntax](https://www.ietf.org/rfc/rfc2314.txt). + + Typically, you export a certificate request file if you need to resubmit the certificate request to the certification authority. You can't import an exported certificate request on another server. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Export-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e -FileName "C:\Data\HT cert.pfx" -BinaryEncoded -Password (Get-Credential).password +``` + +In **Exchange 2013**, this example exports a certificate from the local Exchange server to a file with the following settings: + +- The certificate to export has the thumbprint value 5113ae0233a72fccb75b1d0198628675333d010e. +- The exported certificate file is DER encoded (binary), not Base64. +- Enter the password when prompted. +- The certificate is exported to the file C:\\Data\\HT cert.pfx. + +**Note**: The FileName parameter is available only in Exchange 2013. To export the certificate in Exchange 2016 or Exchange 2019, see Example 2. + +### Example 2 +```powershell +$bincert = Export-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e -BinaryEncoded -Password (Get-Credential).password + +[System.IO.File]::WriteAllBytes('C:\Data\HT cert.pfx', $bincert.FileData) +``` + +This example exports the same certificate from Example 1. This method is required in Exchange 2016 and Exchange 2019 because the FileName parameter is not available. + +### Example 3 +```powershell +Export-ExchangeCertificate -Thumbprint 72570529B260E556349F3403F5CF5819D19B3B58 -Server Mailbox01 -FileName "\\FileServer01\Data\Fabrikam.req" +``` + +In **Exchange 2013**, this example exports a pending certificate request to a file with the following settings: + +- The certificate request to export has the thumbprint value 72570529B260E556349F3403F5CF5819D19B3B58 and is located on the Exchange server named Mailbox01. +- The exported certificate request file is Base64 encoded, so the information that's written to the file is also displayed onscreen. +- The certificate request is exported to the file \\\\FileServer01\\Data\\Fabrikam.req. + +**Note**: The FileName parameter is available only in Exchange 2013. To export the pending certificate request in Exchange 2016 or Exchange 2019, see Example 4. + +### Example 4 +```powershell +$txtcert = Export-ExchangeCertificate -Thumbprint 72570529B260E556349F3403F5CF5819D19B3B58 -Server Mailbox01 + +[System.IO.File]::WriteAllBytes('\\FileServer01\Data\Fabrikam.req', [System.Text.Encoding]::Unicode.GetBytes($txtcert)) +``` + +This example exports the same pending certificate request from Example 3. This method is required in Exchange 2016 and Exchange 2019 because the FileName parameter is not available. + +## PARAMETERS + +### -Thumbprint +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. + +```yaml +Type: String +Parameter Sets: Thumbprint +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter specifies the certificate or certificate request that you want to export. Valid values are: + +- `ServerNameOrFQDN\Thumbprint` +- `Thumbprint` + +You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. + +You can't use this parameter with the Server parameter. + +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. + +```yaml +Type: ExchangeCertificateIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BinaryEncoded +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileName +**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. + +The FileName parameter specifies the name and path of the exported certificate or certificate request file. You can use a local path if the certificate or certificate request is located on the same Exchange server where you're running the command. Otherwise, use a UNC path (`\\Server\Share`). If the value contains spaces, enclose the value in quotation marks ("). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Password +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: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +```yaml +Type: SecureString +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Server +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +If you don't use this parameter, the command is run on the local server. + +You can't use this parameter with the Identity parameter, but you can use it with the Thumbprint parameter. + +```yaml +Type: ServerIdParameter +Parameter Sets: Thumbprint +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Export-FilePlanProperty.md b/exchange/exchange-ps/exchange/Export-FilePlanProperty.md new file mode 100644 index 0000000000..91b4a41f26 --- /dev/null +++ b/exchange/exchange-ps/exchange/Export-FilePlanProperty.md @@ -0,0 +1,98 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/export-fileplanproperty +applicable: Security & Compliance +title: Export-FilePlanProperty +schema: 2.0.0 +--- + +# Export-FilePlanProperty + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Export-FilePlanProperty cmdlet to export file plan properties. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Export-FilePlanProperty [-Confirm] [-DomainController ] [-WhatIf] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Export-FilePlanProperty +``` + +The example exports the file plan properties. + +## PARAMETERS + +### -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. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Export-JournalRuleCollection.md b/exchange/exchange-ps/exchange/Export-JournalRuleCollection.md similarity index 79% rename from exchange/exchange-ps/exchange/policy-and-compliance/Export-JournalRuleCollection.md rename to exchange/exchange-ps/exchange/Export-JournalRuleCollection.md index 0d57029265..0b68ce68f7 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Export-JournalRuleCollection.md +++ b/exchange/exchange-ps/exchange/Export-JournalRuleCollection.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/export-journalrulecollection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Export-JournalRuleCollection @@ -17,43 +16,66 @@ This cmdlet is available only in on-premises Exchange. Use the Export-JournalRuleCollection cmdlet to export the journal rules in your organization to an XML file. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Export-JournalRuleCollection [[-Identity] ] [-Confirm] [-DomainController ] - [-ExportLegacyRules] [-WhatIf] [] +Export-JournalRuleCollection [[-Identity] ] + [-Confirm] + [-DomainController ] + [-ExportLegacyRules] + [-WhatIf] + [] ``` ## DESCRIPTION You can use the Export-JournalRuleCollection cmdlet to export journal rules in your organization to create a backup copy of your rules. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$file = Export-JournalRuleCollection; Set-Content -Path "C:\MyDocs\JournalRules.xml" -Value $file.FileData -Encoding Byte +$file = Export-JournalRuleCollection + +[System.IO.File]::WriteAllBytes('C:\MyDocs\JournalRules.xml', $file.FileData) ``` This example exports journal rules in a two-step process. In the first step, the Export-JournalRuleCollection cmdlet exports journal rules to the variable $file. In the second step, the Set-Content cmdlet saves the exported data to the XML file JournalRules.xml. ### Example 2 ```powershell -$file = Export-JournalRuleCollection -ExportLegacyRules; Set-Content -Path "C:\MyDocs\Ex2007-JournalRules.xml" -Value $file.FileData -Encoding Byte +$file = Export-JournalRuleCollection -ExportLegacyRules + +[System.IO.File]::WriteAllBytes('C:\MyDocs\LegacyJournalRules.xml', $file.FileData) ``` -In Exchange Server 2010, this example exports legacy journal rules to an XML file using the two-step process similar to the preceding example. In the first step, the Export-JournalRuleCollection cmdlet is used with the ExportLegacyRules switch to export legacy rules to the array $file. In the second step, the exported data is saved to the XML file Ex2007-JournallRules.xml. +In Exchange Server 2010, this example exports legacy journal rules that were created in Exchange 2007 to an XML file. The first command uses the ExportLegacyRules switch to export legacy journal rules to the variable named $file. The second step saves the exported data to the XML file named LegacyJournalRules.xml. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -86,9 +108,9 @@ Accept wildcard characters: False ``` ### -ExportLegacyRules -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. -The ExportLegacyRules switch specifies whether to export Exchange 2007 journal rules. +The ExportLegacyRules switch specifies whether to export Exchange 2007 journal rules. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -103,22 +125,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -140,12 +146,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Export-MailboxDiagnosticLogs.md b/exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md similarity index 83% rename from exchange/exchange-ps/exchange/mailboxes/Export-MailboxDiagnosticLogs.md rename to exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md index f91f043f3c..dada5fa300 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Export-MailboxDiagnosticLogs.md +++ b/exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/export-mailboxdiagnosticlogs +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Export-MailboxDiagnosticLogs @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Export-MailboxDiagnosticLogs cmdlet to export diagnostic data from user and system mailboxes in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,25 +27,30 @@ Export-MailboxDiagnosticLogs [-Identity] -ComponentN [-Confirm] [-Credential ] [-DomainController ] + [-IncludeInactiveMailboxes] [-ReadFromDomainController] [-ResultSize ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ExtendedProperties ``` -Export-MailboxDiagnosticLogs [-Identity] [-ExtendedProperties] +Export-MailboxDiagnosticLogs [-Identity] + [-ExtendedProperties] [-Archive] [-Confirm] [-Credential ] [-DomainController ] + [-IncludeInactiveMailboxes] [-ReadFromDomainController] [-ResultSize ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -66,40 +70,58 @@ This example retrieves the calendar permissions diagnostic log for the mailbox n ## PARAMETERS +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ComponentName 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 - ActionProcessingAgent - - BirthdayAssistant - - CalendarPermissions - +- CalendarSharingInvite - CalendarSharingLocalFolder - - DefaultViewIndexer - - FreeBusyPublishingAssistantQuickLog - - HoldTracking - - InternetCalendar - - InternalCalendarSharingMigration - - MRM - - OnlineMeetings - - OOFRules - +- RBA - RemindersAssistant - +- Sharing - SharingMigrationAssistant - - SharingSyncAssistant - +- SubstrateHoldTracking - SweepRules +- TimeProfile ```yaml Type: String @@ -130,42 +152,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Archive This parameter is available only in on-premises Exchange. @@ -187,8 +173,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -209,7 +194,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -242,10 +227,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IncludeInactiveMailboxes +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -299,12 +306,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Export-Message.md b/exchange/exchange-ps/exchange/Export-Message.md similarity index 83% rename from exchange/exchange-ps/exchange/mail-flow/Export-Message.md rename to exchange/exchange-ps/exchange/Export-Message.md index 780dc2da60..28b6f435c6 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Export-Message.md +++ b/exchange/exchange-ps/exchange/Export-Message.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/export-message +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Export-Message @@ -17,18 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Export-Message cmdlet to copy a message from a queue on a Mailbox server or an Edge Transport server to a specified file path in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Export-Message [-Identity] [-Confirm] [-WhatIf] [] +Export-Message [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION The Export-Message cmdlet copies messages from the Delivery queue, the Unreachable queue, or the poison message queue on Mailbox server or an Edge Transport server to a specified file path. Before you export a message, you must first suspend the message. Messages in the poison message queue are already suspended. You can use the Export-Message cmdlet to copy messages to the Replay directory of another Mailbox server for delivery. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,21 +43,27 @@ This example exports a single message to the specified file path. Because the Ex ### Example 2 ```powershell -Get-Message -Queue "Server1\contoso.com" -ResultSize Unlimited | ForEach-Object {Suspend-Message $_.Identity -Confirm:$False; $Temp="C:\ExportFolder\"+$_.InternetMessageID+".eml"; $Temp=$Temp.Replace("<","_"); $Temp=$Temp.Replace(">","_"); Export-Message $_.Identity | AssembleMessage -Path $Temp} +Get-Message -Queue "Server1\contoso.com" -ResultSize Unlimited | ForEach-Object {Suspend-Message $_.Identity -Confirm:$False + +$Temp="C:\ExportFolder\"+$_.InternetMessageID+".eml" + +$Temp=$Temp.Replace("<","_") + +$Temp=$Temp.Replace(">","_") + +Export-Message $_.Identity | AssembleMessage -Path $Temp} ``` This example retrieves all messages from the specified queue. The query results are then piped to the Export-Message command, and all the messages are copied to individual .eml files. The Internet Message IDs of each message are used as the file names. To accomplish this, the command does the following: - Retrieves all messages in a specific queue using the Get-Message cmdlet. - -- The result is pipelined into the ForEach-Object cmdlet, which prepares a file name including full path using the temporary variable $Temp that consists of the Internet Message ID with .eml extension. The Internet Message ID field contains angled brackets ("\>" and "\<") which need to be removed as they are invalid file names. This is done using the Replace method of the temporary variable. - +- The result is pipelined into the ForEach-Object cmdlet, which prepares a file name including full path using the temporary variable $Temp that consists of the Internet Message ID with .eml extension. The Internet Message ID field contains angled brackets (`<` and `>`) which need to be removed as they are invalid file names. This is done using the Replace method of the temporary variable. - The ForEach-Object cmdlet also exports the message using the file name prepared. ## PARAMETERS ### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity). +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 @@ -73,8 +81,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -111,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Export-MigrationReport.md b/exchange/exchange-ps/exchange/Export-MigrationReport.md similarity index 92% rename from exchange/exchange-ps/exchange/move-and-migration/Export-MigrationReport.md rename to exchange/exchange-ps/exchange/Export-MigrationReport.md index 141e52daa3..4610a82482 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Export-MigrationReport.md +++ b/exchange/exchange-ps/exchange/Export-MigrationReport.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/export-migrationreport +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Export-MigrationReport @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. The Export-MigrationReport is used by the Exchange migration process to enable an administrator to download a CSV file that contains migration errors for a selected migration batch. This cmdlet isn't run by an administrator in Windows PowerShell. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Export-MigrationReport [-Identity] -CsvStream ] [-Partition ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Paged @@ -36,11 +36,12 @@ Export-MigrationReport [-Identity] -RowCount ] [-Partition ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,35 +54,35 @@ There are no examples for using this cmdlet because the values used for the requ ## PARAMETERS -### -CsvStream +### -Identity This parameter is reserved for internal Microsoft use. ```yaml -Type: Stream -Parameter Sets: StreamBased +Type: MigrationReportIdParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity +### -CsvStream This parameter is reserved for internal Microsoft use. ```yaml -Type: MigrationReportIdParameter -Parameter Sets: (All) +Type: Stream +Parameter Sets: StreamBased Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -120,8 +121,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -194,12 +194,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Export-QuarantineMessage.md b/exchange/exchange-ps/exchange/Export-QuarantineMessage.md new file mode 100644 index 0000000000..f20bb9e7c2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Export-QuarantineMessage.md @@ -0,0 +1,279 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Export-QuarantineMessage + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Export-QuarantineMessage cmdlet to export quarantined messages and files from your cloud-based organization. Messages are exported to .eml message files so you can open them in Outlook. + +For files that were quarantined by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams, the files are exported in Base64 format. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identities +``` +Export-QuarantineMessage -Identities [-Identity ] + [-CompressOutput] + [-EntityType ] + [-ForceConversionToMime] + [-Password ] + [-PasswordV2 ] + [-ReasonForExport ] + [-RecipientAddress ] + [] +``` + +### IdentityOnly +``` +Export-QuarantineMessage -Identity + [-CompressOutput] + [-EntityType ] + [-ForceConversionToMime] + [-Password ] + [-PasswordV2 ] + [-ReasonForExport ] + [-RecipientAddress ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$e = Export-QuarantineMessage -Identity b28e0706-e50e-4c33-17e8-08daf2898d15\e939baaf-9dac-6126-2137-b82abf373159 + +$txt = [System.Text.Encoding]::Ascii.GetString([System.Convert]::FromBase64String($e.eml)) + +[IO.File]::WriteAllText("C:\My Documents\Quarantined Message.eml", $txt) +``` + +This example exports the specified message that was quarantined as spam: + +- The first command exports the quarantined message to the variable `$e`. The message is stored in the Eml property (the `$e.eml` value) as Base64 (based on the `$e.BodyEncoding` value). +- The second command converts the Eml property from Base64 to ASCII text and stores the result in the variable `$txt`. +- The third command writes the quarantined message to the specified .eml file. + +**Note**: Don't enclose the Identity value in quotation marks (you might get an error). + +### Example 2 +```powershell +$f = Export-QuarantineMessage -Identity 9c6bb3e8-db9e-4823-9759-08d594179bd3\7fec89fe-41b0-ae67-4887-5bede017d111 + +$bytes = [Convert]::FromBase64String($f.eml) + +[IO.File]::WriteAllBytes("C:\My Documents\Quarantined Message with Attachments.eml", $bytes) +``` + +This example exports the specified message with attachments that was quarantined as malware: + +- The first command exports the quarantined message and attachments to the variable `$f`. The message and attachments are stored in the Eml property (the `$f.eml` value) as Base64 (based on the `$f.BodyEncoding` value). +- The second command converts the Eml property from Base64 to bytes and stores the result in the variable `$bytes`. +- The third command writes the quarantined message and attachments to the specified .eml file. + +## PARAMETERS + +### -Identities +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. + +When you use this parameter, the Identity parameter is required, but the value is ignored. For example, use the value 000 for the Identity parameter. + +```yaml +Type: QuarantineMessageIdentity[] +Parameter Sets: Identities +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +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 +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +```yaml +Type: QuarantineMessageIdentity +Parameter Sets: IdentityOnly +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -CompressOutput +The CompressOutput switch exports the message as a compressed .zip file. You don't need to specify a value with this switch. + +For exported messages, including messages with attachments, the .zip file contains a folder that's named after the first GUID value in the Identity. The folder contains the .eml message that's named after the second GUID value in the Identity. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntityType +The EntityType parameter filters the results by EntityType. Valid values are: + +- Email +- SharePointOnline +- Teams (currently in Preview) +- DataLossPrevention + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceConversionToMime +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Password +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: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +To enter the password in plain text, use the PasswordV2 parameter. + +```yaml +Type: SecureString +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PasswordV2 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReasonForExport +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Export-RecipientDataProperty.md b/exchange/exchange-ps/exchange/Export-RecipientDataProperty.md similarity index 76% rename from exchange/exchange-ps/exchange/mailboxes/Export-RecipientDataProperty.md rename to exchange/exchange-ps/exchange/Export-RecipientDataProperty.md index bfbc00608f..79ca27c8bb 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Export-RecipientDataProperty.md +++ b/exchange/exchange-ps/exchange/Export-RecipientDataProperty.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/export-recipientdataproperty +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Export-RecipientDataProperty @@ -15,43 +14,51 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Export-RecipientDataProperty cmdlet to download a user's picture or spoken name sound file. The picture and audio files display in the Global Address List property dialog box, contact card, reading pane, and meeting requests in Microsoft Outlook and Outlook on the web. +Use the Export-RecipientDataProperty cmdlet to download the picture or spoken name audio file of a mailbox or mail contact. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### ExportPicture ``` -Export-RecipientDataProperty [-Identity] [-Picture] +Export-RecipientDataProperty [-Identity] + [-Picture] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ExportSpokenName ``` -Export-RecipientDataProperty [-Identity] [-SpokenName] +Export-RecipientDataProperty [-Identity] + [-SpokenName] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Export-RecipientDataProperty -Identity tony@contoso.com -SpokenName | ForEach { $_.FileData | Add-Content C:\tonysmith.wma -Encoding Byte} +$SN = Export-RecipientDataProperty -Identity tonys@contoso.com -SpokenName + +[System.IO.File]::WriteAllBytes('C:\tonysmith.wma', $SN.FileData) ``` This example exports Tony Smith's spoken name audio file and saves it to the local computer. ### Example 2 ```powershell -Export-RecipientDataProperty -Identity "Ayla" -Picture | ForEach { $_.FileData | Add-Content C:\aylakol.jpg -Encoding Byte} +$Pic = Export-RecipientDataProperty -Identity "Ayla Kol" -Picture + +[System.IO.File]::WriteAllBytes('C:\Data\aylakol.jpg', $Pic.FileData) ``` This example exports Ayla Kol's picture file to the local computer. @@ -62,15 +69,10 @@ This example exports Ayla Kol's picture file to the local computer. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -89,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,9 +124,11 @@ Accept wildcard characters: False ``` ### -Picture -The Picture switch specifies that the file you're exporting is the user's picture file. You don't need to specify a value with this switch. +The Picture switch specifies that you're exporting the user's picture. You don't need to specify a value with this switch. -You can't use this switch with the SpokenName switch. You can only export one file type at a time. +The user's picture is exported as a JPEG file. + +You can't use this switch with the SpokenName switch. ```yaml Type: SwitchParameter @@ -141,9 +144,11 @@ Accept wildcard characters: False ``` ### -SpokenName -The SpokenName switch specifies that the file you're exporting is the user's audio file. You don't need to specify a value with this switch. +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. -This cmdlet exports the WMA 9-voice format. You can't use this switch with the Picture switch. You can only export one file type at a time. +You can't use this switch with the Picture switch. ```yaml Type: SwitchParameter @@ -179,12 +184,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Export-TransportRuleCollection.md b/exchange/exchange-ps/exchange/Export-TransportRuleCollection.md new file mode 100644 index 0000000000..1996ade66b --- /dev/null +++ b/exchange/exchange-ps/exchange/Export-TransportRuleCollection.md @@ -0,0 +1,198 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Export-TransportRuleCollection + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Export-TransportRuleCollection cmdlet to export the transport rules in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Export-TransportRuleCollection [[-Identity] ] + [-Confirm] + [-DomainController ] + [-Format ] + [-ExportLegacyRules] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Export-TransportRuleCollection cmdlet can be used to export the transport rule collection in your organization. The format of the exported transport rule collection changed in Exchange Server 2013. The new format can't be imported into Exchange Server 2010. + +Exporting the rules collection is a two-step process. You first export the rules collection to a variable, and then use the Set-Content cmdlet to write the data to an XML file. For more information, see [Set-Content](https://learn.microsoft.com/powershell/module/microsoft.powershell.management/set-content). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$file = Export-TransportRuleCollection + +[System.IO.File]::WriteAllBytes('C:\My Docs\Rules.xml', $file.FileData) +``` + +This example exports transport rules. Rule data is first exported to the variable $file, and then written to the XML file Rules.xml in the C:\\My Docs folder. + +### Example 2 +```powershell +$file = Export-TransportRuleCollection -ExportLegacyRules + +[System.IO.File]::WriteAllBytes('C:\My Docs\LegacyRules.xml', $file.FileData) +``` + +In Exchange Server 2010, this example exports legacy transport rules that were created in Exchange 2007 to an XML file. The first command uses the ExportLegacyRules switch to export legacy transport rules to the variable named $file. The second step saves the exported data to the XML file named LegacyRules.xml. + +You can import the exported rules collection to Exchange 2010 using the Import-TransportRuleCollection cmdlet. + +You need to run these commands in this example on an Exchange 2010 Hub Transport server. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExportLegacyRules +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Format +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: + +- RuleCollectionXML +- InternalXML +- DlpMigrationRuleCollection + +```yaml +Type: RuleCollectionFormat +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/unified-messaging/Export-UMCallDataRecord.md b/exchange/exchange-ps/exchange/Export-UMCallDataRecord.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Export-UMCallDataRecord.md rename to exchange/exchange-ps/exchange/Export-UMCallDataRecord.md index a96e1a1d6c..29e7f3790d 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Export-UMCallDataRecord.md +++ b/exchange/exchange-ps/exchange/Export-UMCallDataRecord.md @@ -1,39 +1,41 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/export-umcalldatarecord -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Export-UMCallDataRecord ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Export-UMCallDataRecord cmdlet to export Unified Messaging (UM) call data records for UM dial plans and UM IP gateways for a date that you've specified. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Export-UMCallDataRecord -ClientStream -Date [-Confirm] [-DomainController ] - [-UMDialPlan ] [-UMIPGateway ] [-WhatIf] [] +Export-UMCallDataRecord -ClientStream -Date + [-Confirm] + [-DomainController ] + [-UMDialPlan ] + [-UMIPGateway ] + [-WhatIf] + [] ``` ## DESCRIPTION The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records for a specified date to a comma-separated value (CSV) file. You can filter call data records for specific UM dial plans or UM IP gateways. However, if you don't specify a UM IP gateway, all call data records are returned. -The Export-UMCallDataRecord cmdlet is available when you're using the Exchange Administration Center. You can't use the cmdlet from the Exchange Management Shell. - After this task is completed, a report is generated that contains Unified Messaging call data records. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,7 +62,7 @@ The ClientStream parameter specifies the .NET stream to use to output for the Un Type: Stream Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -76,7 +78,7 @@ The Date parameter specifies the date of Unified Messaging call data records to Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -88,15 +90,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -106,15 +107,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -130,7 +129,7 @@ The UMDialPlan parameter specifies the UM dial plan to export statistics for. If Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -146,7 +145,7 @@ The UMIPGateway parameter specifies the UM IP gateway to export statistics for. Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -162,7 +161,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -176,12 +175,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Export-UMPrompt.md b/exchange/exchange-ps/exchange/Export-UMPrompt.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Export-UMPrompt.md rename to exchange/exchange-ps/exchange/Export-UMPrompt.md index ffc334db99..02e8841d44 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Export-UMPrompt.md +++ b/exchange/exchange-ps/exchange/Export-UMPrompt.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/export-umprompt -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Export-UMPrompt ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Export-UMPrompt cmdlet to export an audio file being used as a greeting prompt for Unified Messaging (UM) dial plans and auto attendants. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Export-UMPrompt -PromptFileName -UMAutoAttendant [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### DPCustomGreeting @@ -34,7 +34,8 @@ Export-UMPrompt -PromptFileName -UMAutoAttendant -UMDialPlan [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -42,20 +43,24 @@ The Export-UMPrompt cmdlet exports prompts that belong to existing UM dial plan After this task is completed, the UM prompts are displayed or saved. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$prompt = Export-UMPrompt -PromptFileName "customgreeting.mp3" -UMDialPlan MyUMDialPlan; Set-Content -Path "d:\DialPlanPrompts\welcomegreeting.mp3" -Value $prompt.AudioData -Encoding Byte +$prompt = Export-UMPrompt -PromptFileName "customgreeting.mp3" -UMDialPlan MyUMDialPlan + +[System.IO.File]::WriteAllBytes('D:\DialPlanPrompts\welcomegreeting.mp3', $prompt.AudioData) ``` This example exports the welcome greeting for the UM dial plan MyUMDialPlan and saves it as the file welcomegreeting.mp3. ### Example 2 ```powershell -$prompt = Export-UMPrompt -PromptFileName "welcomegreeting.mp3" -UMAutoAttendant MyUMAutoAttendant; Set-Content -Path "e:\UMPromptsBackup\welcomegreetingbackup.mp3" -Value $prompt.AudioData -Encoding Byte +$prompt = Export-UMPrompt -PromptFileName "welcomegreeting.mp3" -UMAutoAttendant MyUMAutoAttendant + +[System.IO.File]::WriteAllBytes('E:\UMPromptsBackup\welcomegreetingbackup.mp3', $prompt.AudioData) ``` This example exports a custom greeting for the UM auto attendant MyUMAutoAttendant and saves it to the file welcomegreetingbackup.mp3. @@ -69,7 +74,7 @@ The PromptFileName parameter specifies the name of the custom prompt to export. Type: String Parameter Sets: AACustomGreeting, DPCustomGreeting Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -85,7 +90,7 @@ The UMAutoAttendant parameter specifies the UM auto attendant ID. This parameter Type: UMAutoAttendantIdParameter Parameter Sets: AACustomGreeting Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -101,7 +106,7 @@ The UMDialPlan parameter specifies the UM dial plan ID. This parameter specifies Type: UMDialPlanIdParameter Parameter Sets: DPCustomGreeting Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -113,15 +118,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -131,15 +135,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -155,7 +157,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -169,12 +171,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ADPermission.md b/exchange/exchange-ps/exchange/Get-ADPermission.md new file mode 100644 index 0000000000..773f0467b4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ADPermission.md @@ -0,0 +1,169 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ADPermission + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Get-ADPermission cmdlet to get permissions on an Active Directory object. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Owner +``` +Get-ADPermission [-Identity] + [-Owner] + [-DomainController ] + [] +``` + +### AccessRights +``` +Get-ADPermission [-Identity] + [-User ] + [-DomainController ] + [] +``` + +## DESCRIPTION +The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ADPermission -Identity Ed +``` + +This example returns the permissions that have been applied to the user Ed. + +### Example 2 +```powershell +Get-ADPermission "Contoso.com" -User Chris +``` + +This example returns the permissions that have been granted to the user Chris on the Contoso.com Receive connector. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Owner +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Owner +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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 +- Mail users +- Security groups + +For the best results, we recommend using the following values: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Owner parameter. + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/active-directory/Get-ADServerSettings.md b/exchange/exchange-ps/exchange/Get-ADServerSettings.md similarity index 77% rename from exchange/exchange-ps/exchange/active-directory/Get-ADServerSettings.md rename to exchange/exchange-ps/exchange/Get-ADServerSettings.md index e9f5cd773b..e44f8bd977 100644 --- a/exchange/exchange-ps/exchange/active-directory/Get-ADServerSettings.md +++ b/exchange/exchange-ps/exchange/Get-ADServerSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-adserversettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AdServerSettings @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-AdServerSettings cmdlet to view the Active Directory Domain Services (AD DS) environment settings in the current Exchange Management Shell session. The Get-AdServerSettings cmdlet replaces the AdminSessionADSettings session variable that was used in Exchange Server 2007. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,7 @@ Get-AdServerSettings [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -37,7 +36,7 @@ Get-AdServerSettings | Format-List This example displays the session settings for the current session. -For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ## PARAMETERS @@ -46,12 +45,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Get-ADSite.md b/exchange/exchange-ps/exchange/Get-ADSite.md similarity index 86% rename from exchange/exchange-ps/exchange/active-directory/Get-ADSite.md rename to exchange/exchange-ps/exchange/Get-ADSite.md index 54b426190f..507afd4a61 100644 --- a/exchange/exchange-ps/exchange/active-directory/Get-ADSite.md +++ b/exchange/exchange-ps/exchange/Get-ADSite.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-adsite +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AdSite @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-AdSite cmdlet to display configuration information about one or more Active Directory sites. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AdSite [[-Identity] ] [-DomainController ] [] +Get-AdSite [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION Exchange uses Active Directory sites and the costs assigned to the Active Directory site links to make message routing decisions. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,37 +42,37 @@ This example displays the configuration details for the Active Directory site na ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +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: Fqdn +Type: AdSiteIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 ("). +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: AdSiteIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -80,12 +81,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md new file mode 100644 index 0000000000..714d4981eb --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md @@ -0,0 +1,96 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ATPBuiltInProtectionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ATPBuiltInProtectionRule cmdlet to view the rule for the Built-in protection preset security policy that effectively provides default policies for Safe Links and Safe Attachments in Microsoft Defender for Office 365. The rule specifies exceptions to the policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ATPBuiltInProtectionRule [[-Identity] ] [-State ] [] +``` + +## DESCRIPTION +For more information about preset security policies, see [Preset security policies in EOP and Microsoft Defender for Office 365](https://learn.microsoft.com/defender-office-365/preset-security-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ATPBuiltInProtectionRule +``` + +This example shows the rule for the Built-in protection preset security policy. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +The name of the only rule is ATP Built-In Protection Rule. + +```yaml +Type: DehydrateableRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -State +The State parameter filters the results by the state of the rule. Valid values are: + +- Disabled +- Enabled + +The only rule is always enabled. + +```yaml +Type: RuleState +Parameter Sets: (All) +Aliases: +Accepted values: Enabled, Disabled +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md new file mode 100644 index 0000000000..f0a24d140f --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ATPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ATPProtectionPolicyRule cmdlet to view rules for Microsoft Defender for Office 365 protections in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ATPProtectionPolicyRule [[-Identity] ] + [-State ] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ATPProtectionPolicyRule | Format-Table Name,State +``` + +This example returns a summary list of the rules for Defender for Office 365 protections in preset security policies. + +### Example 2 +```powershell +Get-ATPProtectionPolicyRule -Identity "Strict Preset Security Policy" +``` + +This example returns detailed information about the rule named Strict Preset Security Policy. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -State +The State parameter filters the results by the state of the rule. Valid values are: + +- Enabled +- Disabled + +```yaml +Type: RuleState +Parameter Sets: (All) +Aliases: +Accepted values: Enabled, Disabled +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md b/exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md new file mode 100644 index 0000000000..754759eea3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md @@ -0,0 +1,260 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ATPTotalTrafficReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ATPTotalTrafficReport to view details about message traffic in your Microsoft Defender for Office 365 organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ATPTotalTrafficReport + [-Action ] + [-AggregateBy ] + [-Direction ] + [-Domain ] + [-EndDate ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-StartDate ] + [-SummarizeBy ] + [] +``` + +## DESCRIPTION +For the reporting period you specify, the cmdlet returns the following information: + +- EventType: TotalBulkCount, TotalMalwareCount, TotalMissedSafeAttachmentCount, TotalMissedSafeLinkCount, TotalPhishCount, TotalSafeAttachmentCount, TotalSafeLinkCount, TotalSpamCount +- Organization +- Date +- MessageCount +- StartDate +- EndDate +- AggregateBy +- Index + +TotalMissedSafeAttachmentCount is when the recipient or tenant is not included in a Safe Attachments policy, but a message with a detected attachment was removed by zero-hour auto purge (ZAP) after delivery. + +TotalMissedSafeLinkCount is when the recipient or tenant is not included in a Safe Links policy, but a message with a detected URL was removed by ZAP after delivery. + +If the tenant had Safe Attachments or Safe Links policies, the messages would have been blocked and not delivered. + +By default, the command returns data for the last 14 days. Data for the last 90 days is available. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ATPTotalTrafficReport -StartDate (get-date).AddDays(-5) -EndDate (get-date).AddDays(-1) +``` + +This example returns data for the last 5 days. + +## PARAMETERS + +### -Action +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AggregateBy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Direction +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SummarizeBy +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: + +- Action +- Direction +- Domain +- EventType + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-AcceptedDomain.md b/exchange/exchange-ps/exchange/Get-AcceptedDomain.md similarity index 78% rename from exchange/exchange-ps/exchange/mail-flow/Get-AcceptedDomain.md rename to exchange/exchange-ps/exchange/Get-AcceptedDomain.md index c85e34a083..7a46a55884 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-AcceptedDomain.md +++ b/exchange/exchange-ps/exchange/Get-AcceptedDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-accepteddomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-AcceptedDomain @@ -17,16 +16,19 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-AcceptedDomain cmdlet to view the configuration information for the accepted domains in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AcceptedDomain [[-Identity] ] [-DomainController ] [] +Get-AcceptedDomain [[-Identity] ] + [-DomainController ] + [-ResultSize ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,6 +48,22 @@ This example lists all the authoritative accepted domains in your organization. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DomainController This parameter is available only in on-premises Exchange. @@ -66,19 +84,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies a string value for the accepted domain. Enter either the GUID or the name of the accepted domain. +### -ResultSize +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. ```yaml -Type: AcceptedDomainIdParameter +Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Online, Exchange Online Protection Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -87,12 +107,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md b/exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md new file mode 100644 index 0000000000..c42017f450 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AccessToCustomerDataRequest + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-AccessToCustomerDataRequest cmdlet to view Microsoft 365 Customer Lockbox requests that control access to your data by Microsoft support engineers. + +**Note**: Customer Lockbox is included in Microsoft 365 E5, or you can buy a separate Customer Lockbox subscription with any Microsoft 365 Enterprise plan. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AccessToCustomerDataRequest [-ApprovalStatus ] + [-CreatedAfter ] + [-RequestId ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AccessToCustomerDataRequest +``` + +This example returns a summary list of all Customer Lockbox request. + +### Example 2 +```powershell +Get-AccessToCustomerDataRequest -ApprovalStatus Pending +``` + +This example returns a summary list of all Customer Lockbox requests that have the status value Pending. + +### Example 3 +```powershell +Get-AccessToCustomerDataRequest -RequestId EXSR123456 | Format-List +``` + +This example returns detailed information the Customer Lockbox request EXSR123456. + +## PARAMETERS + +### -ApprovalStatus +The ApprovalStatus parameter filters the results by approval status. Valid values are: + +- Approved +- Canceled +- Denied +- Pending + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CreatedAfter +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: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +```yaml +Type: ExDateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequestId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDevice.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md similarity index 80% rename from exchange/exchange-ps/exchange/devices/Get-ActiveSyncDevice.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md index 9b4283b82f..76afb95c32 100644 --- a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDevice.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-activesyncdevice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ActiveSyncDevice @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ActiveSyncDevice cmdlet to retrieve the list of devices in your organization that have active Exchange ActiveSync partnerships. -Note: In Exchange 2013 or later, use the Get-MobileDevice cmdlet instead. If you have scripts that use Get-ActiveSyncDevice, update them to use Get-MobileDevice. +**Note**: In Exchange 2013 or later, use the Get-MobileDevice cmdlet instead. If you have scripts that use Get-ActiveSyncDevice, update them to use Get-MobileDevice. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,7 +29,9 @@ Get-ActiveSyncDevice -Mailbox [-Filter ] [-OrganizationalUnit ] [-ResultSize ] - [-SortBy ] [-Monitoring] [] + [-SortBy ] + [-Monitoring] + [] ``` ### Identity @@ -40,53 +41,73 @@ Get-ActiveSyncDevice [[-Identity] ] [-Filter ] [-OrganizationalUnit ] [-ResultSize ] - [-SortBy ] [-Monitoring] [] + [-SortBy ] + [-Monitoring] + [] ``` ## DESCRIPTION The Get-ActiveSyncDevice cmdlet returns identification, configuration and status information for each device. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-ActiveSyncDevice -Identity "TonySmith" +Get-ActiveSyncDevice -Mailbox "TonySmith" ``` -This example returns all the Exchange ActiveSync mobile devices that Tony Smith has used that are associated with his mailbox. +This example returns all Exchange ActiveSync mobile devices that Tony Smith has used and that are associated with his mailbox. ### Example 2 ```powershell -Get-ActiveSyncDevice -Mailbox "Redmond\TonySmith" +Get-ActiveSyncDevice -ResultSize Unlimited | Where {$_.DeviceOS -eq "OutlookBasicAuth"} | Format-Table -Auto UserDisplayName,DeviceAccessState ``` -This example returns all the Exchange ActiveSync mobile devices that Tony Smith has used that are associated with his mailbox. +This example returns the owner names of all Exchange ActiveSync mobile devices that connect via the Outlook Mobile app using Basic Authentication. + +### Example 3 +```powershell +Get-ActiveSyncDevice -ResultSize Unlimited | Where {$_.DeviceType -eq "OutlookService"} | Format-Table -Auto UserDisplayName,FirstSyncTime +``` + +This example returns the owner names of all Outlook Mobile apps that synch via Hybrid Modern Authentication. ## PARAMETERS +### -Identity +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 +- DeviceIdentity +- Multi-TenantID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Mailbox 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -121,56 +142,36 @@ Accept wildcard characters: False ``` ### -Filter -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. +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. - Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can filter by the following properties: - ClientType - - DeviceAccessControlRule - - DeviceAccessState - - DeviceAccessStateReason - - DeviceActiveSyncVersion - - DeviceId - - DeviceImei - - DeviceMobileOperator - - DeviceModel - - DeviceOS - - DeviceOSLanguage - - DeviceTelephoneNumber - - DeviceType - - DeviceUserAgent - - FirstSyncTime - - FriendlyName - - ProvisioningFlags - - UserDisplayName ```yaml @@ -186,28 +187,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- DeviceIdentity - -- Multi-TenantID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Monitoring This parameter is available only in on-premises Exchange. @@ -232,11 +211,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -271,38 +247,24 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - DeviceAccessControlRule - - DeviceAccessState - - DeviceAccessStateReason - - DeviceId - - DeviceImei - - DeviceMobileOperator - - DeviceModel - - DeviceOS - - DeviceOSLanguage - - DeviceTelephoneNumber - - DeviceType - - DeviceUserAgent - - FirstSyncTime - - FriendlyName - - UserDisplayName ```yaml @@ -323,12 +285,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md similarity index 87% rename from exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md index 7d390dca87..d3a5a05c35 100644 --- a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-activesyncdeviceaccessrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ActiveSyncDeviceAccessRule @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ActiveSyncDeviceAccessRule cmdlet to retrieve an access group of Exchange mobile devices along with their access level. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ActiveSyncDeviceAccessRule [[-Identity] ] [-DomainController ] [] +Get-ActiveSyncDeviceAccessRule [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION You can create multiple groups of devices: allowed devices, blocked devices, and quarantined devices with the New-ActiveSyncDeviceAccessRule cmdlet. The Get-ActiveSyncDeviceAccessRule cmdlet retrieves the settings for any existing group. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,37 +49,37 @@ This example lists all device access rules set up on the server. ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the unique identifier for the device access rule. ```yaml -Type: Fqdn +Type: ActiveSyncDeviceAccessRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the unique identifier for the device access rule. +### -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. ```yaml -Type: ActiveSyncDeviceAccessRuleIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -87,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md similarity index 87% rename from exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceAutoblockThreshold.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md index 5c7ea628c7..0bb8724eba 100644 --- a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceAutoblockThreshold.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-activesyncdeviceautoblockthreshold +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ActiveSyncDeviceAutoblockThreshold @@ -15,21 +14,22 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Get-ActiveSyncDeviceAutoblockThreshold cmdlet to obtain the Autoblock settings for Microsoft Exchange ActiveSync mobile devices.. +Use the Get-ActiveSyncDeviceAutoblockThreshold cmdlet to obtain the Autoblock settings for Microsoft Exchange ActiveSync mobile devices. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-ActiveSyncDeviceAutoblockThreshold [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION Microsoft Exchange and Exchange ActiveSync have the capability to block Exchange ActiveSync mobile devices if these devices display any of a defined list of behaviors that have the capability to cause issues with the server. The Get-ActiveSyncDeviceAutoblockThreshold cmdlet returns the settings for the requested threshold rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,35 +42,35 @@ This example retrieves the threshold settings for the Autoblock threshold rule f ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the name of the Autoblock threshold rule. ```yaml -Type: Fqdn +Type: ActiveSyncDeviceAutoblockThresholdIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the Autoblock threshold rule. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: ActiveSyncDeviceAutoblockThresholdIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -79,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceClass.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md similarity index 81% rename from exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceClass.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md index 869b7c3135..56664b5b8c 100644 --- a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceClass.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-activesyncdeviceclass +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ActiveSyncDeviceClass @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ActiveSyncDeviceClass cmdlet to retrieve a list of ActiveSync devices that have connected to your organization. The cmdlet returns the mobile device type and model information. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ActiveSyncDeviceClass [[-Identity] ] [-DomainController ] - [-Filter ] [-SortBy ] [] +Get-ActiveSyncDeviceClass [[-Identity] ] + [-DomainController ] + [-Filter ] + [-SortBy ] + [] ``` ## DESCRIPTION You can use this cmdlet to view a list of mobile phones or devices by type. For example, you can return a list of all Android mobile digital devices in the organization or all Windows Phone devices in the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,6 +51,26 @@ This example lists all device types within the organization along with a count o ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DomainController This parameter is available only in on-premises Exchange. @@ -68,26 +90,21 @@ Accept wildcard characters: False ``` ### -Filter -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. +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. - Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can filter by the following properties: - DeviceModel - - DeviceType - - LastUpdateTime ```yaml @@ -103,39 +120,15 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - DeviceModel - - DeviceType - - LastUpdateTime ```yaml @@ -156,12 +149,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceStatistics.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md similarity index 79% rename from exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceStatistics.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md index 7c8b07c040..df60827dd4 100644 --- a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceStatistics.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-activesyncdevicestatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ActiveSyncDeviceStatistics @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ActiveSyncDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices. -**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange Server or Exchange Online, use the Get-MobileDeviceStatistics cmdlet instead. If you have scripts that use Get-ActiveSyncDeviceStatistics, update them to use Get-MobileDeviceStatistics. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange or Exchange Online, use the Get-MobileDeviceStatistics cmdlet instead. If you have scripts that use Get-ActiveSyncDeviceStatistics, update them to use Get-MobileDeviceStatistics. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ Get-ActiveSyncDeviceStatistics [-Identity] [-DomainController ] [-GetMailboxLog] [-NotificationEmailAddresses ] - [-ShowRecoveryPassword] [] + [-ShowRecoveryPassword] + [] ``` ### Mailbox @@ -38,13 +38,14 @@ Get-ActiveSyncDeviceStatistics -Mailbox [-DomainController ] [-GetMailboxLog] [-NotificationEmailAddresses ] - [-ShowRecoveryPassword] [] + [-ShowRecoveryPassword] + [] ``` ## DESCRIPTION The Get-ActiveSyncDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -57,16 +58,18 @@ This example retrieves the statistics for the mobile phone configured to synchro ### Example 2 ```powershell -$UserList = Get-CASMailbox -Filter "HasActiveSyncDevicePartnership -eq `$true -and -not DisplayName -like 'CAS_{*'"; Get-Mailbox $UserList | foreach {Get-ActiveSyncDeviceStatistics -Mailbox $_} +$UserList = Get-CASMailbox -Filter "HasActiveSyncDevicePartnership -eq `$true -and -not DisplayName -like 'CAS_{*'" + +Get-Mailbox $UserList | foreach {Get-ActiveSyncDeviceStatistics -Mailbox $_} ``` This example uses the Get-CASMailbox cmdlet to determine who in the organization has an Exchange ActiveSync mobile device. For each mobile device, the Exchange ActiveSync device statistics are retrieved. -**Note**: For more information about OPath filter syntax, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +**Note**: For more information about OPATH filter syntax, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ### Example 3 ```powershell -Get-ActiveSyncDeviceStatistics -Mailbox TonySmith -GetMailboxLog $true -NotificationEmailAddresses "admin@contoso.com" +Get-ActiveSyncDeviceStatistics -Mailbox TonySmith -GetMailboxLog -NotificationEmailAddresses "admin@contoso.com" ``` This example retrieves the statistics for the mobile phone configured to synchronize with the mailbox that belongs to the user Tony Smith. It also outputs the Exchange ActiveSync log file and sends it to the System Administrator at admin@contoso.com. @@ -93,23 +96,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -144,7 +138,7 @@ Accept wildcard characters: False ``` ### -GetMailboxLog -The GetMailboxLog parameter specifies whether to send the mailbox logs via email to the administrator running the task. If the parameter is set to $true, the command sends the mailbox logs via email to the administrator running the task. The default value of this parameter is $false. +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 @@ -160,7 +154,9 @@ Accept wildcard characters: False ``` ### -NotificationEmailAddresses -The NotificationEmailAddresses parameter specifies an optional list of comma-separated aliases or email addresses where the mailbox logs are sent. If the GetMailboxLog parameter is set to $false, this parameter is ignored. +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. ```yaml Type: MultiValuedProperty @@ -196,12 +192,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md similarity index 85% rename from exchange/exchange-ps/exchange/devices/Get-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md index 7a93889f3c..c43f7a04a7 100644 --- a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-activesyncmailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ActiveSyncMailboxPolicy @@ -17,20 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ActiveSyncMailboxPolicy cmdlet to retrieve the Mobile Device mailbox policy settings for a specific Mobile Device mailbox policy. -Note: In Exchange 2013 or later, use the Get-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use Get-ActiveSyncMailboxPolicy, update them to use Get-MobileDeviceMailboxPolicy. +**Note**: In Exchange 2013 or later, use the Get-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use Get-ActiveSyncMailboxPolicy, update them to use Get-MobileDeviceMailboxPolicy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ActiveSyncMailboxPolicy [[-Identity] ] [-DomainController ] [] +Get-ActiveSyncMailboxPolicy [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION A Mobile Device mailbox policy is a group of settings that specifies how mobile devices enabled for Microsoft Exchange ActiveSync connect to the computer running Exchange. Exchange supports multiple Mobile Device mailbox policies. The Get-ActiveSyncMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -57,37 +58,37 @@ This example returns the policy settings for the Mobile Device mailbox policy na ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the policy name. ```yaml -Type: Fqdn +Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the policy name. +### -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. ```yaml -Type: MailboxPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -96,12 +97,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md similarity index 86% rename from exchange/exchange-ps/exchange/devices/Get-ActiveSyncOrganizationSettings.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md index bbf5b4c58a..554ac124b7 100644 --- a/exchange/exchange-ps/exchange/devices/Get-ActiveSyncOrganizationSettings.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-activesyncorganizationsettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ActiveSyncOrganizationSettings @@ -17,17 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ActiveSyncOrganizationSettings cmdlet to view the Microsoft Exchange ActiveSync settings for your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-ActiveSyncOrganizationSettings [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -40,37 +40,37 @@ This example retrieves the ActiveSync organization settings. ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: ActiveSyncOrganizationSettingsIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the ActiveSync organization settings object that you want to view. The default name of this object is Mobile Mailbox Settings. +### -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. ```yaml -Type: ActiveSyncOrganizationSettingsIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -79,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Get-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md index 70dc7aad18..84a7bede86 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-activesyncvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ActiveSyncVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ActiveSyncVirtualDirectory cmdlet to view Exchange ActiveSync virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-ActiveSyncVirtualDirectory -Server [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ### Identity @@ -34,13 +34,14 @@ Get-ActiveSyncVirtualDirectory -Server Get-ActiveSyncVirtualDirectory [[-Identity] ] [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ## DESCRIPTION Microsoft Exchange servers have a default virtual directory that Exchange ActiveSync mobile devices use to synchronize with the server. You can create multiple virtual directories and assign different devices to different directories. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,13 +71,11 @@ This example returns a summary list of all Exchange ActiveSync virtual directori ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -97,11 +96,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -120,7 +116,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -176,12 +174,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Get-AdSiteLink.md b/exchange/exchange-ps/exchange/Get-AdSiteLink.md similarity index 86% rename from exchange/exchange-ps/exchange/active-directory/Get-AdSiteLink.md rename to exchange/exchange-ps/exchange/Get-AdSiteLink.md index 3eab998154..11565da45f 100644 --- a/exchange/exchange-ps/exchange/active-directory/Get-AdSiteLink.md +++ b/exchange/exchange-ps/exchange/Get-AdSiteLink.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-adsitelink +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AdSiteLink @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-AdSiteLink cmdlet to view configuration information about an Active Directory IP site link. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AdSiteLink [[-Identity] ] [-DomainController ] [] +Get-AdSiteLink [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,37 +47,37 @@ This example returns a list of all IP site links in your organization that have ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +The Identity parameter specifies the name or GUID of the IP site link for which you want to view configuration information. ```yaml -Type: Fqdn +Type: AdSiteLinkIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name or GUID of the IP site link for which you want to view configuration information. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: AdSiteLinkIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -85,12 +86,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AdaptiveScope.md b/exchange/exchange-ps/exchange/Get-AdaptiveScope.md new file mode 100644 index 0000000000..1444986464 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AdaptiveScope.md @@ -0,0 +1,111 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AdaptiveScope + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-AdaptiveScope cmdlet to view adaptive scopes in your organization. Adaptive scopes (or static scopes) are used in retention policies and retention label policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AdaptiveScope [[-Identity] ] + [-AdministrativeUnits ] + [-LocationTypes ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AdaptiveScope | Format-Table Name,Priority +``` + +This example returns a summary list of all adaptive scopes. +### Example 2 +```powershell +Get-AdaptiveScope -Identity "Project X" +``` + +This example returns detailed information about the adaptive scope named Project X. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AdministrativeUnits +{{ Fill AdministrativeUnits Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationTypes +{{ Fill LocationTypes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-AddressBookPolicy.md b/exchange/exchange-ps/exchange/Get-AddressBookPolicy.md similarity index 83% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-AddressBookPolicy.md rename to exchange/exchange-ps/exchange/Get-AddressBookPolicy.md index ce36e9da53..83e1de7f90 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-AddressBookPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AddressBookPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/get-addressbookpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-AddressBookPolicy @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-AddressBookPolicy cmdlet to return address book policies that match the specified conditions. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AddressBookPolicy [[-Identity] ] [-DomainController ] [] +Get-AddressBookPolicy [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +49,7 @@ This example returns default information about the address book policy All Fabri ### Example 3 ```powershell -Get-AddressBookPolicy | where {$_.OfflineAddressBook eq "\Fabrikam All OAB"} +Get-AddressBookPolicy | where {$_.OfflineAddressBook -eq "\Fabrikam All OAB"} ``` This example returns information about all address book policies for which the offline address book (OAB) that the address book policy uses is named Fabrikam All OAB. @@ -94,12 +95,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-AddressList.md b/exchange/exchange-ps/exchange/Get-AddressList.md similarity index 87% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-AddressList.md rename to exchange/exchange-ps/exchange/Get-AddressList.md index 1b73dc4118..cf62cd285e 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-AddressList.md +++ b/exchange/exchange-ps/exchange/Get-AddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/get-addresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-AddressList @@ -17,34 +16,37 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-AddressList cmdlet to view address lists. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Container ``` Get-AddressList -Container - [-DomainController ] [] + [-DomainController ] + [] ``` ### Identity ``` Get-AddressList [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ### SearchSet ``` Get-AddressList [-SearchText ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION You can pipe the output from the Get-AddressList cmdlet to the Remove-AddressList, Set-AddressList, Update-AddressList and Move-AddressList cmdlets instead of using the Identity parameter with each of those cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -64,16 +66,36 @@ This example returns detailed information for the address list named building4th ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) + +You can't use this parameter with the Container or SearchText parameters. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Container 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 - - Distinguished name (DN) - - GUID - -- Path: (\\\) or [\\\\) +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) You can't use this parameter with the Identity or SearchText parameters. @@ -108,32 +130,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -- Path: (\\\) or [\\\\) - -You can't use this parameter with the Container or SearchText parameters. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -SearchText 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 ("). @@ -157,12 +153,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-AddressRewriteEntry.md b/exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/mail-flow/Get-AddressRewriteEntry.md rename to exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md index 2cefc9d195..7faa2b133d 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-AddressRewriteEntry.md +++ b/exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-addressrewriteentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AddressRewriteEntry @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-AddressRewriteEntry cmdlet to view an existing address rewrite entry that rewrites sender and recipient email addresses in messages sent to or sent from your organization through an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AddressRewriteEntry [[-Identity] ] [-DomainController ] +Get-AddressRewriteEntry [[-Identity] ] + [-DomainController ] [] ``` @@ -47,37 +47,37 @@ This example returns the detailed configuration of a single address rewrite entr ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +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: Fqdn +Type: AddressRewriteEntryIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: AddressRewriteEntryIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -86,12 +86,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md new file mode 100644 index 0000000000..e9159a5432 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md @@ -0,0 +1,80 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AdminAuditLogConfig + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-AdminAuditLogConfig cmdlet to view the administrator audit logging configuration settings. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AdminAuditLogConfig [-DomainController ] + [] +``` + +## DESCRIPTION +To check the UnifiedAuditLogIngestionEnabled value in the output of this cmdlet, run the command in Exchange Online PowerShell. The value in Security & Compliance PowerShell is always False and the Set-AdminAuditLogConfig cmdlet (and the UnifiedAuditLogIngestionEnabled parameter) is not available to change it. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AdminAuditLogConfig | Format-List +``` + +This example displays the administrator audit logging settings. The output of the Get-AdminAuditLogConfig cmdlet is piped to the Format-List cmdlet. For more information about piping and the Format-List cmdlet, see the following topics: + +- [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) +- [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help) + +## PARAMETERS + +### -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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-AdministrativeUnit.md b/exchange/exchange-ps/exchange/Get-AdministrativeUnit.md new file mode 100644 index 0000000000..6a2753ab2d --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AdministrativeUnit.md @@ -0,0 +1,138 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AdministrativeUnit + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Get-AdministrativeUnit cmdlet to view administrative units, which are Microsoft Entra containers of resources. You can use administrative units to delegate administrative permissions and apply policies to different groups of users. + +**Note**: Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AdministrativeUnit [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AdministrativeUnit +``` + +This example returns a summary list of all Microsoft Entra administrative units. + +### Example 2 +```powershell +Get-AdministrativeUnit -Identity "West Coast" | Format-List +``` + +This example returns detailed information about the administrative unit with the display name West Coast. + +## PARAMETERS + +### -Identity +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) +- ExternalDirectoryObjectId (this GUID value is the same as the ObjectId property in Microsoft Graph PowerShell) +- Name (GUID value) +- Distinguished name (DN) +- GUID (different value than Name) + +```yaml +Type: AdministrativeUnitIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-AgentLog.md b/exchange/exchange-ps/exchange/Get-AgentLog.md similarity index 87% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-AgentLog.md rename to exchange/exchange-ps/exchange/Get-AgentLog.md index 4d305a88a8..90b89266d4 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-AgentLog.md +++ b/exchange/exchange-ps/exchange/Get-AgentLog.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-agentlog +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AgentLog @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-AgentLog cmdlet to parse log files that you specify as parameters and collect raw statistics from the filtering that anti-spam agents apply during a time period that you specify. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AgentLog [-EndDate ] [-Location ] [-StartDate ] - [-TransportService ] [] +Get-AgentLog [-EndDate ] + [-Location ] + [-StartDate ] + [-TransportService ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,7 +45,7 @@ This example returns a report that has statistics collected between 09:00 (9 A.M ### -EndDate 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". +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". ```yaml Type: DateTime @@ -77,7 +79,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: DateTime @@ -96,13 +98,9 @@ Accept wildcard characters: False 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. - - MailboxSubmission for the Mailbox Transport Submission service on Mailbox servers. - - MailboxDelivery for the Mailbox Transport Delivery service on Mailbox servers. - - FrontEnd for the Front End Transport service on Mailbox servers. - - Edge on Edge Transport servers. ```yaml @@ -123,12 +121,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AggregateZapReport.md b/exchange/exchange-ps/exchange/Get-AggregateZapReport.md new file mode 100644 index 0000000000..fd62052590 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AggregateZapReport.md @@ -0,0 +1,140 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AggregateZapReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-AggregateZapReport cmdlet to view aggregate information about zero-hour auto purge (ZAP) activity. By default, the cmdlet shows the last three days of activity, but you can specify up to ten days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AggregateZapReport + [[-EndDate] ] + [[-Page] ] + [[-PageSize] ] + [[-StartDate] ] + [] +``` + +## DESCRIPTION +For the reporting period you specify, the cmdlet returns the following information: + +- Date +- EventType +- ZapActionCount + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AggregateZapReport +``` + +This example retrieves information for the last 3 days. + +### Example 2 +```powershell +Get-AggregateZapReport -StartDate 7/1/2023 -EndDate 7/9/2023 +``` + +This example retrieves information for the specified date range. + +## PARAMETERS + +### -EndDate +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". + +If you use the EndDate parameter, you also need to use the StartDate parameter. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Page +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 +Default value: 0 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: 0 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +If you use this parameter, you also need to use the StartDate parameter. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 4 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md similarity index 85% rename from exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishPolicy.md rename to exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md index 8b2a4b1207..332d193a34 100644 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-antiphishpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-AntiPhishPolicy @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Get-AntiPhishPolicy cmdlet to view antiphish policies in your cloud-based organization. This cmdlet returns results only in Exchange Online PowerShell. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,7 +29,7 @@ Get-AntiPhishPolicy [-Identity ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -57,9 +53,7 @@ This example shows detailed information about the antiphish policy named Office 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 - - Distinguished name (DN) - - GUID ```yaml @@ -83,6 +77,8 @@ The Advanced switch filters the properties that are returned to the advanced set You don't need to specify a value with this switch. +Advanced settings are available only in anti-phishing policies in Microsoft Defender for Office 365. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -121,6 +117,8 @@ The Impersonation switch filters the properties that are returned to the imperso You don't need to specify a value with this switch. +Impersonation settings are available only in anti-phishing policies in Microsoft Defender for Office 365. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -160,12 +158,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-AntiPhishRule.md b/exchange/exchange-ps/exchange/Get-AntiPhishRule.md new file mode 100644 index 0000000000..9593dd004c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AntiPhishRule.md @@ -0,0 +1,95 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AntiPhishRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-AntiPhishRule cmdlet to view antiphish rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AntiPhishRule [[-Identity] ] + [-State ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AntiPhishRule | Format-Table Name,Priority,State +``` + +This example returns a summary list of all antiphish rules in your organization. + +### Example 2 +```powershell +Get-AntiPhishRule -Identity "Research Department Phishing Rule" +``` + +This example returns detailed information about the antiphish rule named Research Department Phishing Rule. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-App.md b/exchange/exchange-ps/exchange/Get-App.md similarity index 87% rename from exchange/exchange-ps/exchange/mailboxes/Get-App.md rename to exchange/exchange-ps/exchange/Get-App.md index 768e63b9c1..4d63102688 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-App.md +++ b/exchange/exchange-ps/exchange/Get-App.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-app +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-App @@ -17,19 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-App cmdlet to view installed apps. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-App [[-Identity] ] [-DomainController ] [-Mailbox ] - [-OrganizationApp] [-PrivateCatalog] [] +Get-App [[-Identity] ] + [-DomainController ] + [-Mailbox ] + [-OrganizationApp] + [-PrivateCatalog] + [] ``` ## DESCRIPTION The Get-App cmdlet returns information about all installed apps or the details of a specific installed app. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,37 +59,37 @@ This example displays the summary list of apps installed by administrators for t ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: AppIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -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. ```yaml -Type: AppIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -94,27 +97,20 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Identity parameter. +**Note**: This parameter only returns user installed and default add-ins. It doesn't return add-ins installed by admins from Integrated Apps. For more information, see [Deploy and manage Office Add-ins](https://learn.microsoft.com/microsoft-365/admin/manage/office-addins). + ```yaml Type: MailboxIdParameter Parameter Sets: (All) @@ -167,12 +163,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md new file mode 100644 index 0000000000..1feb6b2100 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md @@ -0,0 +1,133 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AppRetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-AppRetentionCompliancePolicy to view app retention compliance policies. App retention & labeling policies target new ways to scope and manage policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AppRetentionCompliancePolicy [[-Identity] ] + [-DistributionDetail] + [-ErrorPolicyOnly] + [-RetentionRuleTypes] + [] +``` + +## DESCRIPTION +\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AppRetentionCompliancePolicy | Format-Table Name,GUID +``` + +This example returns a summary list of all app retention compliance policies. + +### Example 1 +```powershell +Get-AppRetentionCompliancePolicy -Identity "Contoso Viva Engage" +``` + +This example returns detailed information for the app retention compliance policy named Contoso Viva Engage. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -DistributionDetail +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ErrorPolicyOnly +{{ Fill ErrorPolicyOnly Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionRuleTypes +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md b/exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md new file mode 100644 index 0000000000..b61fb71ac0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md @@ -0,0 +1,97 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AppRetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-AppRetentionComplianceRule to view app retention compliance rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AppRetentionComplianceRule [[-Identity] ] [-Policy ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AppRetentionComplianceRule | Format-Table Name,Policy +``` + +This example returns a summary list of all app retention compliance rules. + +### Example 1 +```powershell +Get-AppRetentionComplianceRule -Identity "Contoso Viva Engage" +``` + +This example returns detailed information for the app retention compliance rule named Contoso Viva Engage. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md similarity index 75% rename from exchange/exchange-ps/exchange/organization/Get-ApplicationAccessPolicy.md rename to exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md index fc59cb411d..60e3070aa4 100644 --- a/exchange/exchange-ps/exchange/organization/Get-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-applicationaccesspolicy -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-ApplicationAccessPolicy @@ -17,22 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Get-ApplicationAccessPolicy cmdlet to view the list of application access policies. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX -### Set1 ``` -Get-ApplicationAccessPolicy [[-Identity] ] [] +Get-ApplicationAccessPolicy [[-Identity] ] + [] ``` ## DESCRIPTION This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,7 +55,7 @@ The Identity parameter specifies the application access policy that you want to Type: ApplicationAccessPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -73,12 +69,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ArcConfig.md b/exchange/exchange-ps/exchange/Get-ArcConfig.md new file mode 100644 index 0000000000..84df4c911e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ArcConfig.md @@ -0,0 +1,52 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ArcConfig + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ArcConfig cmdlet to view the list of trusted Authenticated Received Chain (ARC) sealers that are configured in the cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ArcConfig [] +``` + +## DESCRIPTION +Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ArcConfig +``` + +This example returns the trusted ARC sealers that are configured for the organization + +## 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md b/exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md new file mode 100644 index 0000000000..31818f3779 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md @@ -0,0 +1,77 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AtpPolicyForO365 + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-AtpPolicyForO365 cmdlet to view the settings for the following features in Microsoft Defender for Office 365: + +- Safe Links protection for supported Office 365 apps. +- Safe Documents: Uses Microsoft Defender for Endpoint to scan documents and files that are opened in Protected View in Microsoft 365 apps for enterprise. +- Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AtpPolicyForO365 [[-Identity] ] + [] +``` + +## DESCRIPTION +Safe Links protection for Office 365 apps checks links in Office documents, not links in email messages. For more information, see [Safe Links settings for Office 365 apps](https://learn.microsoft.com/defender-office-365/safe-links-about#safe-links-settings-for-office-apps). + +Safe Documents scans documents and files that are opened in Protected View. For more information, see [Safe Documents in Microsoft 365 E5](https://learn.microsoft.com/defender-office-365/safe-documents-in-e5-plus-security-about). + +Safe Attachments for SharePoint, OneDrive, and Microsoft Teams prevents users from opening and downloading files that are identified as malicious. For more information, see [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](https://learn.microsoft.com/defender-office-365/safe-attachments-for-spo-odfb-teams-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AtpPolicyForO365 +``` + +This example returns detailed information about the default policy. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-AttachmentFilterEntry.md b/exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md similarity index 87% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-AttachmentFilterEntry.md rename to exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md index 3e45782e95..f9144d58cd 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-AttachmentFilterEntry.md +++ b/exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-attachmentfilterentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AttachmentFilterEntry @@ -17,16 +16,18 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-AttachmentFilterEntry cmdlet to view the list of attachment filter entries that are used by the Attachment Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AttachmentFilterEntry [[-Identity] ] [-DomainController ] [] +Get-AttachmentFilterEntry [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-attachmentfilterlistconfig). +On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://learn.microsoft.com/powershell/module/exchange/set-attachmentfilterlistconfig). On Edge Transport servers, you need to be a member of the local Administrators group to run this cmdlet. @@ -55,39 +56,38 @@ This example returns only the attachment filter entries that filter attachments ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: -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. +- ContentType: This value matches the attachment filter entry against the MIME content type. +- FileName: This value matches the attachment filter entry against the simple file name. ```yaml -Type: Fqdn +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -- FileName: This value matches the attachment filter entry against the simple file name. +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. ```yaml -Type: String +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -98,12 +98,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-AttachmentFilterListConfig.md b/exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md similarity index 86% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-AttachmentFilterListConfig.md rename to exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md index ecac2adf2c..f05c82c01c 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-AttachmentFilterListConfig.md +++ b/exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-attachmentfilterlistconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AttachmentFilterListConfig @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-AttachmentFilterListConfig cmdlet to view the configuration of the Attachment Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AttachmentFilterListConfig [-DomainController ] [] +Get-AttachmentFilterListConfig [-DomainController ] + [] ``` ## DESCRIPTION @@ -64,12 +64,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AuditConfig.md b/exchange/exchange-ps/exchange/Get-AuditConfig.md new file mode 100644 index 0000000000..65476171dc --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AuditConfig.md @@ -0,0 +1,67 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AuditConfig + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-AuditConfig cmdlet to view the auditing configuration in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AuditConfig [-DomainController ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AuditConfig +``` + +This example shows the auditing configuration in the Microsoft Purview compliance portal. + +## PARAMETERS + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditLogSearch.md b/exchange/exchange-ps/exchange/Get-AuditLogSearch.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditLogSearch.md rename to exchange/exchange-ps/exchange/Get-AuditLogSearch.md index 239adccb7a..a77201fca0 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditLogSearch.md +++ b/exchange/exchange-ps/exchange/Get-AuditLogSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/get-auditlogsearch -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-AuditLogSearch @@ -17,25 +16,29 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-AuditLogSearch cmdlet to return a list of current audit log searches that were created with the New-AdminAuditLogSearch or New-MailboxAuditLogSearch cmdlets. The Get-AuditLogSearch cmdlet also returns audit log searches that are initiated whenever an administrator uses the Exchange admin center (EAC) to export audit logs. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AuditLogSearch [[-Identity] ] [-CreatedAfter ] - [-CreatedBefore ] [-ResultSize ] [-Type ] [] +Get-AuditLogSearch [[-Identity] ] + [-CreatedAfter ] + [-CreatedBefore ] + [-ResultSize ] + [-Type ] + [] ``` ## DESCRIPTION Run the Get-AuditLogSearch cmdlet to return a list of pending audit log searches. If an audit log search has been completed, it won't be displayed in the list of audit log searches. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-AuditLogSearch | FL +Get-AuditLogSearch | Format-List ``` This example displays detailed information for all current audit log searches. @@ -49,34 +52,32 @@ This example returns a list of current administrator audit log searches. ## PARAMETERS -### -CreatedAfter -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". +### -Identity +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: ExDateTime +Type: AuditLogSearchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -CreatedBefore -The CreatedBefore parameter filters the results to audit log searches that were created before the specified date. +### -CreatedAfter +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". +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". ```yaml Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -85,19 +86,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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. +### -CreatedBefore +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". ```yaml -Type: AuditLogSearchIdParameter +Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -108,7 +111,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -124,7 +127,7 @@ The Type parameter specifies the type of audit log searches to return. Use the v Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -138,12 +141,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-AuthConfig.md b/exchange/exchange-ps/exchange/Get-AuthConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/organization/Get-AuthConfig.md rename to exchange/exchange-ps/exchange/Get-AuthConfig.md index 81e2d0c3d0..7acbfbce8c 100644 --- a/exchange/exchange-ps/exchange/organization/Get-AuthConfig.md +++ b/exchange/exchange-ps/exchange/Get-AuthConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-authconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AuthConfig @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-AuthConfig cmdlet to get the authorization configuration for partner applications. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AuthConfig [-DomainController ] [] +Get-AuthConfig [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,12 +60,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-AuthRedirect.md b/exchange/exchange-ps/exchange/Get-AuthRedirect.md similarity index 82% rename from exchange/exchange-ps/exchange/client-access-servers/Get-AuthRedirect.md rename to exchange/exchange-ps/exchange/Get-AuthRedirect.md index 84ac205c83..a1e538e22c 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-AuthRedirect.md +++ b/exchange/exchange-ps/exchange/Get-AuthRedirect.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-authredirect +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AuthRedirect @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-AuthRedirect cmdlet to view OAuth redirection objects that are used for legacy Microsoft Exchange 2010 Client Access servers in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AuthRedirect [[-Identity] ] [-DomainController ] [] +Get-AuthRedirect [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION Exchange 2010 Client Access servers don't support OAuth authentication requests. OAuth redirection objects redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,42 +42,42 @@ This example shows a summary list of all the OAuth redirection objects. ### Example 2 ```powershell -Get-AuthRedirect AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE | Format-List +Get-AuthRedirect -Identity AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE | Format-List ``` This example shows detailed information about the OAuth redirection object named AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: Fqdn +Type: AuthRedirectIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the existing OAuth redirection object that you want to view. The object name uses the syntax AuthRedirect-Bearer-\. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: AuthRedirectIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -85,12 +86,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-AuthServer.md b/exchange/exchange-ps/exchange/Get-AuthServer.md similarity index 86% rename from exchange/exchange-ps/exchange/organization/Get-AuthServer.md rename to exchange/exchange-ps/exchange/Get-AuthServer.md index 58b25afdbb..ecf577d5a2 100644 --- a/exchange/exchange-ps/exchange/organization/Get-AuthServer.md +++ b/exchange/exchange-ps/exchange/Get-AuthServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-authserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-AuthServer @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-AuthServer cmdlet to view the settings of authorization servers in the Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AuthServer [[-Identity] ] [-DomainController ] [] +Get-AuthServer [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION An authorization server is a server or service that issues tokens trusted by Microsoft Exchange for access by partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,9 +53,7 @@ This example retrieves detailed information for the authorization server named W 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 - - Distinguished name (DN) - - GUID ```yaml @@ -93,12 +92,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md new file mode 100644 index 0000000000..b79c7d9b3c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md @@ -0,0 +1,129 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AuthenticationPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-AuthenticationPolicy cmdlet to view authentication policies in your organization. +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AuthenticationPolicy [[-Identity] ] + [-AllowLegacyExchangeTokens] + [-TenantId ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AuthenticationPolicy | Format-Table -Auto Name +``` + +This example returns a summary list of all authentication policies. + +### Example 2 +```powershell +Get-AuthenticationPolicy -Identity "Engineering Group" +``` + +This example returns detailed information for the authentication policy named Engineering Group. + +### Example 3 +```powershell +Get-AuthenticationPolicy -AllowLegacyExchangeTokens +``` + +In Exchange Online, this example specifies whether legacy Exchange tokens for Outlook add-ins are allowed in the organization. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the authentication policy you want to view. You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: AuthPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLegacyExchangeTokens +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. + +Legacy Exchange tokens include Exchange user identity and callback tokens. + +**Important**: + +- The AllowLegacyExchangeTokens switch returns `Not Set` if tokens haven't been explicitly allowed or blocked in your organization using the _AllowLegacyExchangeTokens_ or _BlockLegacyExchangeTokens_ parameters on the **Set-AuthenticationPolicy** cmdlet. For more information, see [Get the status of legacy Exchange Online tokens and add-ins that use them](https://learn.microsoft.com/office/dev/add-ins/outlook/turn-exchange-tokens-on-off#get-the-status-of-legacy-exchange-online-tokens-and-add-ins-that-use-them). +- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. Although tokens are blocked by default, the AllowLegacyExchangeTokens switch still returns `Not Set` if you haven't used the _AllowLegacyExchangeTokens_ or _BlockLegacyExchangeTokens_ parameters on the **Set-AuthenticationPolicy** cmdlet. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantId +This parameter is available only in the cloud-based service. + +{{ Fill TenantId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md new file mode 100644 index 0000000000..b60b6db4da --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md @@ -0,0 +1,147 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AutoSensitivityLabelPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-AutoSensitivityLabelPolicy cmdlet to view auto-labeling policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AutoSensitivityLabelPolicy [[-Identity] ] + [-DistributionDetail] + [-ForceValidate ] + [-IncludeProgressFeedback] + [-IncludeTestModeResults ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AutoSensitivityLabelPolicy -Identity "Employee Numbers" -IncludeTestModeResults $true +``` + +This example returns detailed information about the autosensitivity label policy named Employee Numbers. The IncludeTestModeResults parameter and value allows you to see the status of test mode. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -DistributionDetail +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceValidate +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. +- $false: The output doesn't contain the information. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeProgressFeedback +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeTestModeResults +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. +- $false: Don't include the status of test mode in the policy details. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md new file mode 100644 index 0000000000..ebaea6d9d6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md @@ -0,0 +1,183 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AutoSensitivityLabelRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-AutoSensitivityLabelPolicy cmdlet to view auto-labeling policy rules in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AutoSensitivityLabelRule [[-Identity] ] + [-Confirm] + [-ForceValidate] + [-IncludeExecutionRuleGuids ] + [-IncludeExecutionRuleInformation ] + [-Policy ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AutoSensitivityLabelRule +``` + +This example displays summary information for all autolabeling rules in the Microsoft Purview compliance portal. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceValidate +{{ Fill ForceValidate Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeExecutionRuleGuids +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. +- $false: Don't include the execution rule GUID in the rule details. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeExecutionRuleInformation +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. +- $false: Don't include the execution rule information in the rule details. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Get-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md index d166c8a852..e8c693c9bf 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-autodiscovervirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-AutodiscoverVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-AutodiscoverVirtualDirectory cmdlet to view Autodiscover virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-AutodiscoverVirtualDirectory -Server [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ### Identity @@ -34,11 +34,12 @@ Get-AutodiscoverVirtualDirectory -Server Get-AutodiscoverVirtualDirectory [[-Identity] ] [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,13 +69,11 @@ This example returns a summary list of all Autodiscover virtual directories in t ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -95,11 +94,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -118,7 +114,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -174,12 +172,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-AvailabilityAddressSpace.md b/exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md similarity index 85% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-AvailabilityAddressSpace.md rename to exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md index 3645014616..bfde6fcc4c 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-availabilityaddressspace -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-AvailabilityAddressSpace @@ -17,19 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-AvailabilityAddressSpace cmdlet to view existing availability address space objects that are used to share free/busy data across Exchange organizations. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AvailabilityAddressSpace [[-Identity] ] [-DomainController ] +Get-AvailabilityAddressSpace [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION In on-premises Exchange organizations, you run the Remove-AvailabilityAddressSpace cmdlet on Exchange servers that have the Client Access server role installed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,43 +49,41 @@ This example returns details information for the availability address space obje ## PARAMETERS -### -DomainController -This parameter is available only in on-premises Exchange. +### -Identity +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: -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +- Name +- Distinguished name (DN) +- GUID ```yaml -Type: Fqdn +Type: AvailabilityAddressSpaceIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) +### -DomainController +This parameter is available only in on-premises Exchange. -- GUID +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: AvailabilityAddressSpaceIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -94,12 +92,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-AvailabilityConfig.md b/exchange/exchange-ps/exchange/Get-AvailabilityConfig.md new file mode 100644 index 0000000000..7932aaed30 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-AvailabilityConfig.md @@ -0,0 +1,97 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-AvailabilityConfig + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-AvailabilityConfig cmdlet to view information about the sharing of free/busy information between organizations: + +- In on-premises Exchange, the cmdlet returns the accounts that are trusted in the cross-forest sharing of free/busy information. +- In Exchange Online, the cmdlet returns the tenant IDs of organizations that free/busy information is being shared with. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-AvailabilityConfig [[-Identity] ] + [-DomainController ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AvailabilityConfig +``` + +In on-premises Exchange, this example returns the accounts that are trusted in the cross-forest shared of free/busy information. + +In Exchange Online, this examples returns the tenant IDs that free/busy information is being shared with. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/server-health-and-performance/Get-AvailabilityReportOutage.md b/exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md similarity index 87% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-AvailabilityReportOutage.md rename to exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md index eb975f2a01..b73d3f29f3 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-availabilityreportoutage +online version: https://learn.microsoft.com/powershell/module/exchange/get-availabilityreportoutage applicable: Exchange Server 2010 title: Get-AvailabilityReportOutage schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Get-AvailabilityReportOutage @@ -17,17 +16,20 @@ This cmdlet is available only in Exchange Server 2010. Use the Get-AvailabilityReportOutage cmdlet to return the daily downtime (if any) for each service entity and its overridden value (if set) to the overall reported availability for the day. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-AvailabilityReportOutage [[-Identity] ] [-ReportDate ] - [-ReportingDatabase ] [-ReportingServer ] [] +Get-AvailabilityReportOutage [[-Identity] ] + [-ReportDate ] + [-ReportingDatabase ] + [-ReportingServer ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -116,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Get-BlockedConnector.md b/exchange/exchange-ps/exchange/Get-BlockedConnector.md new file mode 100644 index 0000000000..c6701d3230 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-BlockedConnector.md @@ -0,0 +1,73 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-BlockedConnector + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-BlockedConnector cmdlet to view inbound connectors that have been detected as potentially compromised. Blocked connectors are prevented from sending email. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-BlockedConnector [-ConnectorId ] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-BlockedConnector +``` + +This example returns a summary list of all blocked connectors. + +### Example 2 +```powershell +Get-BlockedConnector -ConnectorId 159eb7c4-75d7-43e2-95fe-ced44b3e0a56 | Format-List +``` + +This example returns detailed information for the specified blocked connector. + +## PARAMETERS + +### -ConnectorId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_commonparameters). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md b/exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md new file mode 100644 index 0000000000..4a14ad443b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md @@ -0,0 +1,80 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-BlockedSenderAddress + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-BlockedSenderAddress cmdlet to view users in your Microsoft 365 organization that are impacted by the protection system. These users sent multiple messages that were classified as spam, so they're blocked from sending messages. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-BlockedSenderAddress [-SenderAddress ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-BlockedSenderAddress +``` + +This example returns information about all blocked senders. + +### Example 2 +```powershell +Get-BlockedSenderAddress -SenderAddress laura@contoso.com +``` + +This example returns information about the blocked sender laura@contoso.com. + +## PARAMETERS + +### -SenderAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_commonparameters). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Exchange Management Shell cmdlet input and output types](https://learn.microsoft.com/exchange/client-developer/management/exchange-management-shell-cmdlet-input-and-output-types). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### Output types +To see the return types, which are also known as output types, that this cmdlet accepts, see [Exchange Management Shell cmdlet input and output types](https://learn.microsoft.com/exchange/client-developer/management/exchange-management-shell-cmdlet-input-and-output-types). If the Output Type field is blank, the cmdlet doesn't return data. + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access/Get-CASMailbox.md b/exchange/exchange-ps/exchange/Get-CASMailbox.md similarity index 77% rename from exchange/exchange-ps/exchange/client-access/Get-CASMailbox.md rename to exchange/exchange-ps/exchange/Get-CASMailbox.md index 36751f9103..00439ed122 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-CASMailbox.md +++ b/exchange/exchange-ps/exchange/Get-CASMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-casmailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-CASMailbox @@ -17,10 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-CASMailbox cmdlet to view the Client Access settings that are configured on mailboxes. -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXOCASMailbox cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXOCASMailbox cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -41,6 +39,7 @@ Get-CASMailbox [-Anr ] [-SortBy ] [-ReadIsOptimizedForAccessibility] [-RecalculateHasActiveSyncDevicePartnership] [] + [-RecipientTypeDetails ] ``` ### Identity @@ -60,12 +59,13 @@ Get-CASMailbox [[-Identity] ] [-SortBy ] [-ReadIsOptimizedForAccessibility] [-RecalculateHasActiveSyncDevicePartnership] [] + [-RecipientTypeDetails ] ``` ## DESCRIPTION This cmdlet returns a variety of client access settings for one or more mailboxes. These settings include options for Outlook on the web, Exchange ActiveSync, POP3, and IMAP4. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,13 +77,9 @@ Get-CASMailbox "Jeff Hay" This example returns the values of the following client access settings for the user named Jeff Hay. - ActiveSyncEnabled - - OWAEnabled - - PopEnabled - - ImapEnabled - - MapiEnabled ### Example 2 @@ -100,12 +96,48 @@ Get-CASMailbox chris@contoso.com | Format-List Ews* This example returns all Exchange Web Services settings for the user chris@contoso.com. +### Example 4 +```powershell +Get-CASMailbox -RecipientTypeDetails SharedMailbox | Select * +``` + +In Exchange Online, this example filters the cmdlet output to only include shared mailboxes. + ## PARAMETERS +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ActiveSyncDebugLogging -The ActiveSyncDebugLogging switch shows the actual value of the ActiveSyncDebugLogging property for the mailbox. If you don't use this switch, the value always appears as $false. +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. -To see this value, you need to use a formatting cmdlet. For example, Get-CasMailbox laura@contoso.com -ActiveSyncDebugLogging | Format-List. +If you don't use this switch, the value always appears as $false. + +To see this value, you need to use a formatting cmdlet. For example, `Get-CasMailbox laura@contoso.com -ActiveSyncDebugLogging | Format-List`. ```yaml Type: SwitchParameter @@ -140,13 +172,9 @@ Accept wildcard characters: False 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -165,7 +193,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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). ```yaml Type: PSCredential @@ -199,19 +227,16 @@ Accept wildcard characters: False ``` ### -Filter -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. +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'"`. -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -226,49 +251,12 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -308,11 +296,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -332,18 +317,15 @@ Accept wildcard characters: False The ProtocolSettings switch returns the server names, TCP ports and encryption methods for the following settings: - ExternalImapSettings - - InternalImapSettings - - ExternalPopSettings - - InternalPopSettings - - ExternalSmtpSettings - - InternalSmtpSettings -To see these values, you need to use a formatting cmdlet. For example, Get-CasMailbox laura@contoso.com -ProtocolSettings | Format-List. +You don't need to specify a value with this switch. + +To see these values, you need to use a formatting cmdlet. For example, `Get-CasMailbox laura@contoso.com -ProtocolSettings | Format-List`. ```yaml Type: SwitchParameter @@ -361,7 +343,9 @@ Accept wildcard characters: False ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -395,7 +379,9 @@ Accept wildcard characters: False ``` ### -RecalculateHasActiveSyncDevicePartnership -The RecalculateHasActiveSyncDevicePartnership switch recalculates the value of the HasActiveSyncDevicePartnership property on the mailbox. The value is automatically updated if it's found to be incorrect. You don't have to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -410,6 +396,37 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RecipientTypeDetails +This parameter is available only in the cloud-based service. + +The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are: + +- DiscoveryMailbox +- EquipmentMailbox +- LegacyMailbox +- LinkedMailbox +- LinkedRoomMailbox +- MailUser +- RoomMailbox +- SharedMailbox +- TeamMailbox +- UserMailbox + +You can specify multiple values separated by commas. + +```yaml +Type: RecipientTypeDetails[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ResultSize The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. @@ -429,14 +446,12 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName - - ServerLegacyDN ```yaml @@ -457,12 +472,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-CASMailboxPlan.md b/exchange/exchange-ps/exchange/Get-CASMailboxPlan.md new file mode 100644 index 0000000000..c825898743 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CASMailboxPlan.md @@ -0,0 +1,212 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CASMailboxPlan + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Get-CASMailboxPlan cmdlet to view Client Access services (CAS) mailbox plans in cloud-based organizations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-CASMailboxPlan [[-Identity] ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-ResultSize ] + [-SortBy ] + [] +``` + +## DESCRIPTION +A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-CASMailboxPlan | Format-Table -Auto DisplayName,ActiveSyncEnabled,ImapEnabled,PopEnabled,OwaMailboxPolicy +``` + +This example returns a summary list of all CAS mailbox plans in the organization. + +### Example 2 +```powershell +Get-CASMailboxPlan -Identity ExchangeOnlineEnterprise +``` + +This example returns detailed information about the specified CAS mailbox plan. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +The display name and name of the CAS mailbox plan is the same as the corresponding mailbox plan (for example, ExchangeOnlineEnterprise and `ExchangeOnlineEnterprise-GUID`). + +```yaml +Type: MailboxPlanIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following attributes: + +- DisplayName +- Name + +The results are sorted in ascending order. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md new file mode 100644 index 0000000000..497c465e12 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md @@ -0,0 +1,219 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CalendarDiagnosticAnalysis + +## SYNOPSIS +Although this cmdlet is available in on-premises Exchange and in the cloud-based service, it only works in on-premises Exchange. + +Use the Get-CalendarDiagnosticAnalysis cmdlet to troubleshoot calendar-related reliability issues. You can use this cmdlet to analyze calendar item data that's recorded in the Calendar Diagnostic logs. You provide the calendar item data to this cmdlet by using the Get-CalendarDiagnosticLog cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### DefaultSet +``` +Get-CalendarDiagnosticAnalysis -CalendarLogs + [-DetailLevel ] + [-GlobalObjectId ] + [-OutputAs ] + [] +``` + +### LocationSet +``` +Get-CalendarDiagnosticAnalysis -LogLocation + [-DetailLevel ] + [-GlobalObjectId ] + [-OutputAs ] + [] +``` + +## DESCRIPTION +The following properties of the calendar item are returned in the default output of the cmdlet (when the DetailLevel parameter is set to Basic): + +- Local Log Time +- ItemId +- NormalizedSubject +- StartTime +- EndTime +- CalendarLogTriggerAction +- ClientInfoString +- OriginalLastModifiedTime +- ClientIntent +- CleanGlobalObjectId +- ItemClass +- ParentDisplay +- Duration +- AppointmentRecurring +- SentRepresentingEmailAddress +- SenderEmailAddress +- SentRepresentingDisplayName + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$logs = Get-CalendarDiagnosticLog -Identity oevans -MeetingID 040000008200E00074C5B7101A82E008000000009421DCCD5046CD0100000000000000001000000010B0349F6B17454685E17D9F9512E71F + +Get-CalendarDiagnosticAnalysis -CalendarLogs $logs -DetailLevel Advanced | Set-Content -Path "C:\My Documents\Oscar Evans Analysis.csv" +``` + +This example gets the specified calendar item from Oscar Evans' mailbox, stores the item as a variable and writes the advanced analysis of the item to a CSV file. + +For basic analysis of the item, don't include the DetailLevel parameter, or use the value Basic instead of Advanced. + +### Example 2 +```powershell +Get-CalendarDiagnosticAnalysis -LogLocation "C:\My Documents\Exported Calendar Logs\jkozma@contoso.com" -DetailLevel Advanced -OutputAs HTML | Set-Content -Path "C:\My Documents\Jasen Kozma Analysis.html" +``` + +In **Exchange 2013**, this example analyzes the calendar items that were previously exported from Jasen Kozma's mailbox by using the Get-CalendarDiagnosticLog cmdlet with the LogLocation parameter and writes the advanced analysis of the items to an HTML file. + +**Note**: The LogLocation parameter is available only in Exchange 2013. To specify the location of exported calendar items in Exchange 2016 or Exchange 2019, see Example 3. + +For basic analysis of the items, don't include the DetailLevel parameter, or use the value Basic instead of Advanced. + +### Example 3 +```powershell +$calitems = Get-CalendarDiagnosticLog -Identity jkozma@contoso.com -Subject "Budget Meeting" + +ForEach($item in $calitems){$i++; Get-CalendarDiagnosticAnalysis -CalendarLogs $item -OutputAs HTML | Set-Content -Path ("\\FileServer01\Data\Jasen Kozma Analysis{0}.html" -f $i)} +``` + +This example analyzes the calendar items that were exported from Jasen Kozma's mailbox by using the Get-CalendarDiagnosticLog cmdlet and writes the advanced analysis for each item to an HTML file by using an UNC path. + +For basic analysis of the items, don't include the DetailLevel parameter, or use the value Basic instead of Advanced. + +## PARAMETERS + +### -CalendarLogs +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. + +The value that you use for this parameter must identify a single item. To identify multiple items, see Example 3. + +You can't use this parameter with the LogLocation parameter. + +```yaml +Type: CalendarLog[] +Parameter Sets: DefaultSet +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LogLocation +**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. + +The LogLocation parameter specifies the location of the exported calendar items that you want to analyze. You can specify a local path, or a UNC path (`\\Server\Share\User`). If the value contains spaces, enclose the value in quotation marks ("). + +You export the calendar items to .msg files by using the Get-CalendarDiagnosticLog cmdlet with the LogLocation parameter. If the path contains multiple .msg files, all of those files are analyzed when you run Get-CalendarDiagnosticAnalysis. + +You can't use this parameter with the CalendarLogs parameter. + +```yaml +Type: String[] +Parameter Sets: LocationSet +Aliases: +Applicable: Exchange Server 2013, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DetailLevel +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. +- Advanced: 37 additional calendar item properties are returned. You should use this value only for detailed debugging information. + +```yaml +Type: AnalysisDetailLevel +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GlobalObjectId +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutputAs +The OutputAs parameter specifies the output format of the command. Valid values are: + +- CSV (This is the default value) +- HTML +- XML + +```yaml +Type: OutputType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Get-CalendarDiagnosticLog.md b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md similarity index 85% rename from exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticLog.md rename to exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md index d1de0cea90..38b63df96c 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticLog.md +++ b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-calendardiagnosticlog +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-CalendarDiagnosticLog ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +Although this cmdlet is available in on-premises Exchange and in the cloud-based service, it only works in on-premises Exchange. In cloud-based service, use the Get-CalendarDiagnosticObjects cmdlet instead. Use the Get-CalendarDiagnosticLog cmdlet to collect a range of calendar logs. The Calendar Diagnostic logs track all calendar items and meeting requests in mailboxes. You can use this information to troubleshoot calendar issues that occur in mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -66,18 +65,14 @@ Get-CalendarDiagnosticLog [-Identity] -LogLocation The output of this cmdlet contains the following information: - IsFileLink: Indicates whether the calendar item has been exported to a .msg file by using the LogLocation parameter. Values are True or False. - - Identity: Identifies the mailbox that holds the calendar item. An example value is: excallog://laura@contoso.com/?id=RgAAAACF/h/dHTTkQbdPrk7z+G4SBwCoatc7EmnEQq1iF35p17stAAAAAAFEAACoatc7EmnEQq1iF35p17stAAAAABEIAAAP. - - LogDate: The date-time that the calendar item was logged. - - NormalizedSubject: The Subject field of the calendar item. - - CleanGlobalObjectId: The identifier that's constant throughout the lifetime of the calendar item. For example, 040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55. -After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see [Get-CalendarDiagnosticAnalysis](https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-calendardiagnosticanalysis). +After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see [Get-CalendarDiagnosticAnalysis](https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticanalysis). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -107,13 +102,13 @@ This example retrieves the Calendar Diagnostic log data only for the most recent Get-CalendarDiagnosticLog -Identity "Jasen Kozma" -Subject "Budget Meeting" -ExactMatch $true -LogLocation "C:\My Documents\Calendar Diagnostic Export" ``` -This example exports all calendar items in the Calendar Diagnostic log for Jasen Kozma's mailbox that have "Budget Meeting" anywhere in the subject to the specified folder. +In **Exchange 2013**, this example exports all calendar items in the Calendar Diagnostic log for Jasen Kozma's mailbox that have "Budget Meeting" anywhere in the subject to the specified folder. -Notes: +**Notes**: - In this example, the message files are written to C:\\My Documents\\Calendar Diagnostic Export\\jkozma@contoso.com. - -- In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAnalysis cmdlet with the LogLocation parameter to analyze the exported .msg files. +- In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAnalysis cmdlet to analyze the exported .msg files. +- This example doesn't work in Exchange 2016 or Exchange 2019 because the LogLocation parameter is not available. ## PARAMETERS @@ -121,23 +116,14 @@ Notes: The Identity parameter specifies the mailbox that contains the calendar items. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -154,19 +140,23 @@ Accept wildcard characters: False ``` ### -LogLocation -The LogLocation parameter specifies the location to export the calendar items to .msg files. You can specify a local path, or a UNC path (\\\\\\\\). If the value contains spaces, enclose the value in quotation marks ("). +**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. + +The LogLocation parameter specifies the location to export the calendar items to .msg files. You can specify a local path, or a UNC path (`\\Server\Share`). If the value contains spaces, enclose the value in quotation marks ("). In the location you specify, a subfolder is automatically created for the specified mailbox that holds the exported calendar items. For example, if you specify the value "C:\\My Documents\\Calendar Export" to export calendar items from the mailbox of Shannon Steele, the .msg files are actually stored in C:\\My Documents\\Calendar Export\\ssteele@contoso.com. -In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAnalysis cmdlet with the LogLocation parameter to analyze the exported .msg files. +In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAnalysis cmdlet to analyze the exported .msg files. -Note: Commands that use this parameter might fail if the calendar item doesn't have a title. If you receive errors when you use this parameter, run the command again and replace this parameter with redirection to a file (| Set-Content -Path "C:\\My Documents\\Calendar Export") or substitute the output to a PowerShell variable. +**Note**: Commands that use this parameter might fail if the calendar item doesn't have a title. If you receive errors when you use this parameter, run the command again and replace this parameter with redirection to a file (`| Set-Content -Path "C:\My Documents\Calendar Export"`) or substitute the output to a PowerShell variable. ```yaml Type: String Parameter Sets: ExportToMsg Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Online Required: True Position: Named @@ -179,7 +169,7 @@ Accept wildcard characters: False Type: String Parameter Sets: MeetingId, MeetingSubject Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Online Required: False Position: Named @@ -257,7 +247,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -293,7 +283,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". ```yaml Type: ExDateTime @@ -328,7 +318,6 @@ Accept wildcard characters: False 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". - - $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This is the default value. A partial subject match search may not return all of the relevant calendar items. Try using an exact subject match search for more accurate results. @@ -403,7 +392,9 @@ Accept wildcard characters: False ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -439,7 +430,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: ExDateTime @@ -459,12 +450,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md new file mode 100644 index 0000000000..e01ded63d5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md @@ -0,0 +1,472 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CalendarDiagnosticObjects + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-CalendarDiagnosticObjects cmdlet to collect a range of calendar logs. The calendar diagnostic logs track important calendar-related event data for each mailbox, and can be used to troubleshoot calendar issues that occur in mailboxes. The logs track all calendar items and meeting messages. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-CalendarDiagnosticObjects [-Identity] + [-AnalyzeExceptionWithOriginalStartDate ] + [-AutoRequeryOnMeetingId ] + [-ConfigurationName ] + [-CustomPropertyNames ] + [-EndDate ] + [-EntryId ] + [-EwsId ] + [-ExactMatch ] + [-ItemClass ] + [-ItemIds ] + [-MaxResults ] + [-MeetingId ] + [-ODataId ] + [-ResultSize ] + [-ShouldBindToItem ] + [-ShouldDecodeEnums ] + [-ShouldFetchAttendeeCollection ] + [-ShouldFetchRecurrenceExceptions ] + [-StartDate ] + [-Subject ] + [] +``` + +## DESCRIPTION +Some of the more interesting properties that are returned in the results are: + +- AppointmentState: 1 = The appointment is a meeting, 2 = The appointment has been received, 4 = The appointment has been cancelled, and 8 = the appointment is a forwarded appointment. +- CalendarLogTriggerAction: The action that's taken on the item (for example, Create or Update). +- ClientInfoString: The entity that made the change (for example, `Client=OWA;`, `Client=WebServices;`;, or `Client=TBA;Service=MSExchangeMailboxAssistants;Action=ELCAssistant;`). +- MeetingRequestType: 1 = The meeting message is a meeting request, 65536 = The meeting message is a full update to an existing meeting, 131072 = The meeting message is an informational update to an existing meeting, 262144 = The meeting message is a silent update, 524288 = The update is outdated, or 1048576 = The meeting message is forwarded to a delegate, and the copy is marked as informational. +- OriginalLastModifiedTime: Used as the primary sort field to order the events. +- ResponseType: 0 = The organizer hasn't received a response, 1 = The organizer's copy of the meeting, 2 = Tentative, 3 = Accept, 4 = Decline, or 5 = The attendee hasn't responded. +- ResponsibleUserName: The LegacyExchangeDN value of the user who made the change (for example, `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BN6PR11MB1587/cn=Microsoft System Attendant` or `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=696eea97d3c449eab648920d03385efb-admin`). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -Subject "Team Meeting" -ExactMatch $true +``` + +This example retrieves the calendar diagnostic logs from Pedro Pizarro's mailbox for all items where the Subject is an exact match for Team Meeting. + +### Example 2 +```powershell +$A = Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -Subject "Team Meeting" -ExactMatch $true + +$A | Select-Object *,@{n='OLMT'; e={[DateTime]::Parse($_.OriginalLastModifiedTime.ToString())}} | sort OLMT | Format-Table OriginalLastModifiedTime,CalendarLogTriggerAction,ItemClass,ClientInfoString +``` + +This is the same as the previous example, but now the results are sorted by original last modified time. + +### Example 3 +```powershell +Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -MeetingID 40000008200E00074C5B7101A82E00800000000693ADAA3B5FCD201000000000000000010000000FF760A70460EAA4096B879872DF24F49 +``` + +This example retrieves the calendar diagnostic logs for Pedro Pizarro's mailbox for a meeting with the specified unique global object ID (GOID). + +### Example 4 +```powershell +Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -Subject "Team Lunch" -StartDate 7/1/2018 -EndDate 7/31/2018 | Export-Csv "C:\My Documents\Team Lunch Meeting.csv" -NoTypeInformation +``` + +This example returns diagnostic information for meetings with the subject Team Lunch in Pedro Pizarro's mailbox that were modified in the month of July, 2018, and exports the results to the file C:\\My Documents\\Team Lunch Meeting.csv. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: UnifiedGroupOrUserMailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AnalyzeExceptionWithOriginalStartDate +{{ Fill AnalyzeExceptionWithOriginalStartDate Description }} + +```yaml +Type: ExDateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoRequeryOnMeetingId +{{ Fill AutoRequeryOnMeetingId Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConfigurationName +{{ Fill ConfigurationName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomPropertyNames +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: ExDateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntryId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsId +{{ Fill EwsId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExactMatch +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". +- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This is the default value. + +A partial subject match search may not return all of the relevant calendar items. Try using an exact subject match search for more accurate results. + +You only use this parameter with the Subject parameter. + +The value of this parameter is ignored when you use the MeetingId parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ItemClass +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ItemIds +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxResults +{{ Fill MaxResults Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingId +The MeetingId parameter filters the results by the globally unique identifier of the calendar item. The value is the CleanGlobalObjectId property of the calendar item that's available in the output of this cmdlet, or by using other MAPI examination tools. An example value is 040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55. This value is constant throughout the lifetime of the calendar item. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ODataId +{{ Fill ODataId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShouldBindToItem +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. +- $false: The values of large streamable properties are truncated. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShouldDecodeEnums +{{ Fill ShouldDecodeEnums Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShouldFetchAttendeeCollection +{{ Fill ShouldFetchAttendeeCollection Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShouldFetchRecurrenceExceptions +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. +- $false: Don't Include exceptions to recurring meetings. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: ExDateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Subject +The Subject parameter identifies the calendar items by the specified text in the Subject field. The text values that you specify aren't case sensitive. If the value contains spaces, enclose the value in quotation marks. You can control whether to use exact matching by using the ExactMatch parameter + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-CalendarNotification.md b/exchange/exchange-ps/exchange/Get-CalendarNotification.md new file mode 100644 index 0000000000..014d7e719e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CalendarNotification.md @@ -0,0 +1,162 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CalendarNotification + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Get-CalendarNotification cmdlet to view calendar text message notification settings for a mailbox. + +**Note**: This cmdlet has been deprecated in Exchange Online PowerShell. The text message notification service has been discontinued in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-CalendarNotification [-Identity] + [-Credential ] + [-DomainController ] + [-ReadFromDomainController] + [-ResultSize ] + [] +``` + +## DESCRIPTION +The Get-CalendarNotification cmdlet retrieves and displays the rules that trigger the calendar agenda notification, reminder notification, or update notification text messages. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-CalendarNotification -Identity tony@contoso.com +``` + +This example returns the calendar text message notification settings for Tony's mailbox. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Get-CalendarProcessing.md b/exchange/exchange-ps/exchange/Get-CalendarProcessing.md similarity index 78% rename from exchange/exchange-ps/exchange/mailboxes/Get-CalendarProcessing.md rename to exchange/exchange-ps/exchange/Get-CalendarProcessing.md index 17d2ecc629..a38f7b7958 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-CalendarProcessing.md +++ b/exchange/exchange-ps/exchange/Get-CalendarProcessing.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-calendarprocessing +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-CalendarProcessing @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-CalendarProcessing cmdlet to view the calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant and calendar configuration. Note that the settings returned by this cmdlet are editable only on resource mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-CalendarProcessing [-Identity] [-DomainController ] [-ReadFromDomainController] - [-ResultSize ] [] +Get-CalendarProcessing [-Identity] + [-DomainController ] + [-ReadFromDomainController] + [-ResultSize ] + [] ``` ## DESCRIPTION -For details about the properties that are returned in the output of this cmdlet, see [Set-CalendarProcessing](https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-calendarprocessing). +For details about the properties that are returned in the output of this cmdlet, see [Set-CalendarProcessing](https://learn.microsoft.com/powershell/module/exchange/set-calendarprocessing). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,23 +48,14 @@ This example shows the calendar processing options for the resource mailbox Room 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -99,7 +92,9 @@ Accept wildcard characters: False ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -137,12 +132,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md new file mode 100644 index 0000000000..54654c842b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md @@ -0,0 +1,162 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CaseHoldPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-CaseHoldPolicy to view existing case hold policies in the Microsoft Purview compliance portal. To get relevant information about how the hold was applied and the affected locations, you need to include the DistributionDetail switch. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-CaseHoldPolicy [[-Identity] ] + [-Case ] + [-DistributionDetail] + [-IncludeBindings] + [-IncludeBindingsOnly] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-CaseHoldPolicy -Case "Contoso Legal" +``` + +This example displays detailed information for the policy that's associated with the eDiscovery case named Contoso Legal. + +### Example 2 +```powershell +Get-CaseHoldPolicy -Identity "Regulation 123 Compliance" +``` + +This example displays detailed information for the policy named "Regulation 123 Compliance". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Case +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 +- Identity (GUID value). + +You can find these values by running the command: Get-ComplianceCase | Format-Table -Auto Name,Status,Identity. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DistributionDetail +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". + +The following properties are affected by this switch: + +- SharePointLocation +- ExchangeLocation +- PublicFolderLocation +- DistributionStatus +- DistributionResults +- LastStatusUpdateTime + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeBindings +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeBindingsOnly +{{ Fill IncludeBindingsOnly Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-CaseHoldRule.md b/exchange/exchange-ps/exchange/Get-CaseHoldRule.md new file mode 100644 index 0000000000..632e20fe65 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CaseHoldRule.md @@ -0,0 +1,98 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CaseHoldRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-CaseHoldRule to view case hold rules in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-CaseHoldRule [[-Identity] ] + [-Policy ] + [] +``` + +## DESCRIPTION +In large environments, running this cmdlet without any parameters results in a timeout. As a workaround, you can run the following command: + +`Get-ComplianceCase | foreach {Get-CaseHoldPolicy -Case $_.Identity | foreach {Get-CaseHoldRule -Policy $_.Guid}}` + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-CaseHoldRule -Identity "30 Day Rule" +``` + +This example displays detailed information for the case hold rule named "30 Day Rule". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +You can use this parameter with the Identity parameter in the same command. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-ClassificationRuleCollection.md b/exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md similarity index 86% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-ClassificationRuleCollection.md rename to exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md index ecc4802c6a..b246435ac5 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-classificationrulecollection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ClassificationRuleCollection @@ -17,19 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ClassificationRuleCollection cmdlet to view the classification rule collections in your organization. -In the Office 365 Security & Compliance Center, use the Get-DlpSensitiveInformationTypeRulePackage cmdlet. +In the Microsoft Purview compliance portal, use the Get-DlpSensitiveInformationTypeRulePackage cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-ClassificationRuleCollection [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,37 +49,37 @@ This example returns detailed information about the classification rule collecti ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: ClassificationRuleCollectionIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -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. ```yaml -Type: ClassificationRuleCollectionIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -88,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessArray.md b/exchange/exchange-ps/exchange/Get-ClientAccessArray.md similarity index 88% rename from exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessArray.md rename to exchange/exchange-ps/exchange/Get-ClientAccessArray.md index 02edc380e1..c879bde532 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessArray.md +++ b/exchange/exchange-ps/exchange/Get-ClientAccessArray.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-clientaccessarray +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ClientAccessArray @@ -17,13 +16,15 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ClientAccessArray cmdlet to view legacy RPC Client Access arrays (load-balanced arrays of Client Access servers within a single Active Directory site) that exist in your Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ClientAccessArray [[-Identity] ] [-DomainController ] - [-Site ] [] +Get-ClientAccessArray [[-Identity] ] + [-DomainController ] + [-Site ] + [] ``` ## DESCRIPTION @@ -32,10 +33,9 @@ Client Access arrays were introduced in Exchange Server 2010 so Outlook clients Changes in the Exchange server architecture that were introduced in Exchange Server 2013 removed the need for RPC Client Access arrays: - Outlook clients can't use RPC over TCP to access mailboxes on Exchange Server 2013 or later versions and RPC Client Access arrays only work with RPC over TCP. +- Because the Client Access server role is now a stateless proxy, you use different and less complex methods to configure load balancing and high availability for internal and external client connections. For more information, see [Load balancing in Exchange Server](https://learn.microsoft.com/Exchange/architecture/client-access/load-balancing). -- Because the Client Access server role is now a stateless proxy, you use different and less complex methods to configure load balancing and high availability for internal and external client connections. For more information, see [Load balancing in Exchange Server](https://docs.microsoft.com/Exchange/architecture/client-access/load-balancing). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,33 +55,13 @@ This example returns detailed information for the Client Access array named CASA ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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) - - Distinguished name (DN) - - ExchangeLegacyDN - - Fully qualified domain name (FQDN) - - GUID ```yaml @@ -97,15 +77,28 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Site The Site parameter filters the results by Active Directory site. You can use any value that uniquely identifies the site. For example: - Name - - Distinguished name (DN) - - GUID - - To see a list of available sites, use the Get-ADSite cmdlet. ```yaml @@ -126,12 +119,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ClientAccessRule.md b/exchange/exchange-ps/exchange/Get-ClientAccessRule.md new file mode 100644 index 0000000000..0e40aa0d98 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ClientAccessRule.md @@ -0,0 +1,145 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ClientAccessRule + +## SYNOPSIS +> [!NOTE] +> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). + +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-ClientAccessRule cmdlet to view client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ClientAccessRule [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ClientAccessRule +``` + +This example shows a summary list of all client access rules. + +### Example 2 +```powershell +Get-ClientAccessRule "Block Client Connections from 192.168.1.0/24" | Format-List +``` + +This example retrieves details about the client access rule named "Block Client Connections from 192.168.1.0/24". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/client-access-servers/Get-ClientAccessServer.md b/exchange/exchange-ps/exchange/Get-ClientAccessServer.md similarity index 84% rename from exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessServer.md rename to exchange/exchange-ps/exchange/Get-ClientAccessServer.md index eb97d38445..c3cb98eccc 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessServer.md +++ b/exchange/exchange-ps/exchange/Get-ClientAccessServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-clientaccessserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ClientAccessServer @@ -17,20 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ClientAccessServer cmdlet to view settings that are associated with the Client Access server role. -Note: In Exchange 2013 or later, use the Get-ClientAccessService cmdlet instead. If you have scripts that use Get-ClientAccessServer, update them to use Get-ClientAccessService. +**Note**: In Exchange 2013 or later, use the Get-ClientAccessService cmdlet instead. If you have scripts that use Get-ClientAccessServer, update them to use Get-ClientAccessService. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ClientAccessServer [[-Identity] ] [-DomainController ] - [-IncludeAlternateServiceAccountCredentialPassword] [-IncludeAlternateServiceAccountCredentialStatus] +Get-ClientAccessServer [[-Identity] ] + [-DomainController ] + [-IncludeAlternateServiceAccountCredentialPassword] + [-IncludeAlternateServiceAccountCredentialStatus] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,33 +51,14 @@ This example returns detailed information for the server mail.contoso.com. ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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: - Name (for example, Exchange01) - - Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com) - - Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01) - - GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942) ```yaml @@ -92,10 +74,26 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IncludeAlternateServiceAccountCredentialPassword 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. +The password is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessServer | Format-List AlternateServiceAccountConfiguration`. ```yaml Type: SwitchParameter @@ -113,7 +111,7 @@ Accept wildcard characters: False ### -IncludeAlternateServiceAccountCredentialStatus 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. +The status is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessServer | Format-List AlternateServiceAccountConfiguration`. ```yaml Type: SwitchParameter @@ -133,12 +131,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessService.md b/exchange/exchange-ps/exchange/Get-ClientAccessService.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessService.md rename to exchange/exchange-ps/exchange/Get-ClientAccessService.md index 639c1936ae..1f3d8c72e4 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessService.md +++ b/exchange/exchange-ps/exchange/Get-ClientAccessService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-clientaccessservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ClientAccessService @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ClientAccessService cmdlet to view settings that are associated with the Client Access server role. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ClientAccessService [[-Identity] ] [-DomainController ] - [-IncludeAlternateServiceAccountCredentialPassword] [-IncludeAlternateServiceAccountCredentialStatus] +Get-ClientAccessService [[-Identity] ] + [-DomainController ] + [-IncludeAlternateServiceAccountCredentialPassword] + [-IncludeAlternateServiceAccountCredentialStatus] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,33 +49,14 @@ This example returns detailed information for the server mail.contoso.com. ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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: - Name (for example, Exchange01) - - Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com) - - Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01) - - GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942) ```yaml @@ -90,10 +72,26 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IncludeAlternateServiceAccountCredentialPassword 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. +The password is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessService | Format-List AlternateServiceAccountConfiguration`. ```yaml Type: SwitchParameter @@ -111,7 +109,7 @@ Accept wildcard characters: False ### -IncludeAlternateServiceAccountCredentialStatus 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. +The status is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessService | Format-List AlternateServiceAccountConfiguration`. ```yaml Type: SwitchParameter @@ -131,12 +129,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-Clutter.md b/exchange/exchange-ps/exchange/Get-Clutter.md new file mode 100644 index 0000000000..abd9f70458 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-Clutter.md @@ -0,0 +1,95 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-Clutter + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-Clutter cmdlet to view Clutter settings for mailboxes in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-Clutter -Identity + [-UseCustomRouting] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-Clutter -Identity "Constancia Pena" +``` + +This example returns the Clutter settings for the user Constancia Pena. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-CmdletExtensionAgent.md b/exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md similarity index 88% rename from exchange/exchange-ps/exchange/organization/Get-CmdletExtensionAgent.md rename to exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md index b09722e953..79f88947ca 100644 --- a/exchange/exchange-ps/exchange/organization/Get-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-cmdletextensionagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-CmdletExtensionAgent @@ -17,26 +16,29 @@ This cmdlet is available only in on-premises Exchange. Use the Get-CmdletExtensionAgent cmdlet to view cmdlet extension agents. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Filters ``` -Get-CmdletExtensionAgent [-Assembly ] [-Enabled ] - [-DomainController ] [] +Get-CmdletExtensionAgent [-Assembly ] + [-Enabled ] + [-DomainController ] + [] ``` ### Identity ``` Get-CmdletExtensionAgent [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and later. Cmdlets provided by other Microsoft or third-party products can't use cmdlet extension agents. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,6 +58,26 @@ This example displays detailed information for the Exchange cmdlet extension age ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: CmdletExtensionAgentIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Assembly 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. @@ -92,7 +114,6 @@ Accept wildcard characters: False 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. - - $false: Only disabled agents are included in the results. If you don't use this parameter, enabled and disabled agents are included in the results. @@ -110,39 +131,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: CmdletExtensionAgentIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ComplianceCase.md b/exchange/exchange-ps/exchange/Get-ComplianceCase.md new file mode 100644 index 0000000000..74d35075bf --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceCase.md @@ -0,0 +1,171 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceCase + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ComplianceCase cmdlet to different types of compliance cases in the Microsoft Purview compliance portal. See the CaseType parameter for a list of these case types. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ComplianceCase [-Identity] ] + [-CaseType ] + [-DomainController ] + [-RecentOnly] + [-RoleGroup ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceCase +``` + +This example returns a summary list of all eDiscovery Standard cases in the organization. + +### Example 2 +```powershell +Get-ComplianceCase -Identity "Contoso Legal" | Format-List +``` + +This example returns detailed information for the eDiscovery Standard case named Contoso Legal. + +### Example 3 +```powershell +Get-ComplianceCase -CaseType AdvancedEdiscovery +``` + +This example returns a summary list of all eDiscovery Premium cases in the organization. + +### Example 4 +```powershell +Get-ComplianceCase -CaseType DSR -RoleGroup "DSR Administrators" +``` + +This example returns a summary list of all DSR cases that the custom role group "DSR Administrators" is a member of. + +## PARAMETERS + +### -Identity +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 +- Identity (GUID value) + +```yaml +Type: ComplianceCaseIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CaseType +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**. +- ComplianceClassifier: This type of case corresponds to a trainable classifier. In the Microsoft Purview compliance portal, trainable classifiers are displayed under **Data classification** \> **Trainable classifiers**. +- ComplianceWorkspace: This value is reserved for internal Microsoft use. +- DataInvestigation: Data investigation cases are used to investigate data spillage incidents. In the Microsoft Purview compliance portal, Data investigation cases are displayed on the **Data investigations** page. +- DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. In the Microsoft Purview compliance portal, DSR cases are displayed under **Data privacy** \> **Data subject requests**. +- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. In the Microsoft Purview compliance portal, eDiscovery Standard cases are displayed under **eDiscovery** \> **Standard**. This is the default value. +- InsiderRisk: Insider risk cases are used to manage insider risk management cases. In the Microsoft Purview compliance portal, insider risk cases are displayed under **Insider risk management** \> **Cases**. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert. +- InternalInvestigation: This value is reserved for internal Microsoft use. +- SupervisionPolicy: This type of case corresponds to communication compliance policy. In the Microsoft Purview compliance portal, communication compliance policies are displayed under **Communication compliance** \> **Policies**. + +```yaml +Type: ComplianceCaseType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: eDiscovery +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecentOnly +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoleGroup +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md new file mode 100644 index 0000000000..5588971c20 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceCaseMember + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ComplianceCaseMember cmdlet to view the members of eDiscovery cases in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Get-ComplianceCaseMember -Case + [-DomainController ] + [-ResultSize ] + [-ShowCaseAdmin] + [] +``` + +### AllCases +``` +Get-ComplianceCaseMember + [-DomainController ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceCaseMember -Case "Fabrikam Litigation" +``` + +This examples shows the members of the eDiscovery case named Fabrikam Litigation. + +## PARAMETERS + +### -Case +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowCaseAdmin +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md new file mode 100644 index 0000000000..4688db4274 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md @@ -0,0 +1,146 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceRetentionEvent + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ComplianceRetentionEvent cmdlet to view compliance retention events in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ComplianceRetentionEvent [-Identity ] + [-BeginDateTime ] + [-DomainController ] + [-EndDateTime ] + [-PreviewOnly] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceRetentionEvent | Format-Table Name,Description +``` + +The example returns a summary list of all compliance retention events. + +### Example 2 +```powershell +Get-ComplianceRetentionEvent -Identity "Case 1234" +``` + +This example returns detailed information about the compliance retention event named Case 1234. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BeginDateTime +{{ Fill BeginDateTime Description }} + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDateTime +{{ Fill EndDateTime Description }} + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreviewOnly +{{ Fill PreviewOnly Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md new file mode 100644 index 0000000000..413b3c7aa3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md @@ -0,0 +1,97 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceRetentionEventType + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ComplianceRetentionEventType cmdlet to view retention event types in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ComplianceRetentionEventType [-Identity ] + [-LoadTag] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceRetentionEventType | Format-Table Name,Priority +``` + +This example returns a summary list of all retention event types + +### Example 2 +```powershell +Get-ComplianceRetentionEventType -Identity "Fabrikam Project" -LoadTag +``` + +This example returns detailed information for the retention event type named Fabrikam Project, including the associated compliance tags. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -LoadTag +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceSearch.md b/exchange/exchange-ps/exchange/Get-ComplianceSearch.md new file mode 100644 index 0000000000..95ca1983f2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceSearch.md @@ -0,0 +1,156 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceSearch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-ComplianceSearch cmdlet to view estimate compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. After you use the New-ComplianceSearchAction cmdlet to define a preview action for the compliance search, use the Get-ComplianceSearchAction cmdlet to view the results of the compliance search. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ComplianceSearch [[-Identity] ] + [-Case ] + [-DomainController ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceSearch +``` + +This example shows a summary list of all compliance searches. + +### Example 2 +```powershell +Get-ComplianceSearch -Identity "Case 1234" | Format-List +``` + +This examples show details of the compliance search named Case 1234. + +## PARAMETERS + +### -Identity +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: + +- Name +- JobRunId (GUID) + +You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status + +To improve the performance of this cmdlet, some compliance search properties aren't returned if you don't specify the identity of the compliance search. These properties are: + +- Items +- Size +- SuccessResults +- NumBindings +- ExchangeLocation +- SharePointLocation +- OneDriveLocation + +To view these properties, you need to use the Identity parameter in the command. + +**Note**: The NumBindings property includes the primary mailbox, the main archive, and any additional archives for users included in the search. NumBindings is not the number of users included in the search, because each included user could have or not have a combination of a primary mailbox, a main archive, and additional archives. + +```yaml +Type: ComplianceSearchIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Case +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. + +You can't use this parameter to view compliance searches associated with eDiscovery Premium cases. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md new file mode 100644 index 0000000000..a0ca0a62b5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md @@ -0,0 +1,296 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceSearchAction + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-ComplianceSearchAction cmdlet to view information about compliance search actions. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Get-ComplianceSearchAction [[-Identity] ] + [-Case ] + [-Details] + [-DomainController ] + [-IncludeCredential] + [-Organization ] + [-ResultSize ] + [] +``` + +### Preview +``` +Get-ComplianceSearchAction [-Preview] + [-Case ] + [-Details] + [-DomainController ] + [-IncludeCredential] + [-Organization ] + [-ResultSize ] + [] +``` + +### Purge +``` +Get-ComplianceSearchAction [-Purge] + [-Case ] + [-Details] + [-DomainController ] + [-IncludeCredential] + [-Organization ] + [-ResultSize ] + [] +``` + +### Export +``` +Get-ComplianceSearchAction [-Export] + [-Case ] + [-Details] + [-DomainController ] + [-IncludeCredential] + [-Organization ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +After you create and run a compliance search using the New-ComplianceSearch cmdlet, and start the search using the Start-ComplianceSearch cmdlet, you assign a search action using the New-ComplianceSearchAction cmdlet. You use the Get-ComplianceSearchAction cmdlet to track the progress of the compliance search action. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceSearchAction +``` + +This example shows a summary list of all compliance search actions. + +### Example 2 +```powershell +Get-ComplianceSearchAction -Identity "Case 1234_Preview" | Format-List +``` + +This example shows details about the compliance search action named "Case 1234_Preview" + +## PARAMETERS + +### -Identity +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"`. +- JobRunId (GUID) + +You can't use this parameter with the Export, Preview, or Purge parameters. + +When you use the Identity parameter, more details are returned in the results. For example: + +- In the Results line, the values of the Item count, Total size, and Details properties are populated. +- Location lines are added to the results. +- The NumBindings property value is populated. This property includes the primary mailbox, the main archive, and any additional archives for users included in the search. NumBindings is not the number of users included in the search, because each included user could have or not have a combination of a primary mailbox, a main archive, and additional archives. +- The affected location properties (for example, ExchangeLocation) are populated. +- The CaseName property value is populated. + +```yaml +Type: ComplianceSearchActionIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Case +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Details +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Export +**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. + +You can't use this switch with the Identity, Preview, or Purge parameters. + +```yaml +Type: SwitchParameter +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeCredential +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Preview +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Preview +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Purge +**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. + +You can't use this switch with the Export, Identity, or Preview parameters. + +```yaml +Type: SwitchParameter +Parameter Sets: Purge +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md new file mode 100644 index 0000000000..0c3ff1f88a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md @@ -0,0 +1,157 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceSecurityFilter + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ComplianceSecurityFilter cmdlet to view compliance security filters in the Microsoft Purview compliance portal. These filters allow specified users to search only a subset of mailboxes and SharePoint or OneDrive sites in your Microsoft 365 organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ComplianceSecurityFilter [-Action ] + [-Confirm] + [-FilterName ] + [-User ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Compliance security filters work with compliance searches in the Microsoft Purview compliance portal (\*-ComplianceSearch cmdlets), not In-Place eDiscovery searches in Exchange Online (\*-MailboxSearch cmdlets). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceSecurityFilter | Format-Table -Auto FilterName,Action +``` + +This example returns a summary list of all compliance security filters. + +### Example 2 +```powershell +Get-ComplianceSecurityFilter -FilterName "HR Filter" +``` + +This example returns detailed information about the compliance security filter named HR Filter. + +## PARAMETERS + +### -Action +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. +- Preview: The filter is applied when previewing search results. +- Purge: The filter is applied when purging search results. How the items are deleted is controlled by the PurgeType parameter value on the New-ComplianceSearchAction cmdlet. The default value is SoftDelete, which means the purged items are recoverable by users until the deleted items retention period expires. +- Search: The filter is applied when running a search. +- All: The filter is applied to all search actions. + +```yaml +Type: ComplianceSecurityFilterActionType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FilterName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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. +- The value All. +- The name of a role group. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceTag.md b/exchange/exchange-ps/exchange/Get-ComplianceTag.md new file mode 100644 index 0000000000..2c704b8488 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceTag.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceTag + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ComplianceTag cmdlet to view retention labels in the Microsoft Purview compliance portal. Retention labels apply retention settings to content. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ComplianceTag [[-Identity] ] + [-IncludingLabelState] + [-PriorityCleanup] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceTag | Format-Table -Auto Name,Priority,RetentionAction,RetentionDuration,Workload +``` + +This example returns a summary list of all labels. + +### Example 2 +```powershell +Get-ComplianceTag -Identity "HR Content" +``` + +This example returns detailed information about the label named HR Content. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the label that you want to view. You can use any value that uniquely identifies the tag. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -IncludingLabelState +{{ Fill IncludingLabelState Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md b/exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md new file mode 100644 index 0000000000..c3aa8eaca3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md @@ -0,0 +1,90 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ComplianceTagStorage + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ComplianceTagStorage cmdlet to confirm that you've created the retention label policy by using the Enable-ComplianceTagStorage cmdlet. Retention labels apply retention settings to content. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ComplianceTagStorage [[-Identity] ] + [-Organization ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ComplianceTagStorage +``` + +This example confirms that you've created the label policy in your organization. + +## PARAMETERS + +### -Identity +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) +- Distinguished name (DN) +- GUID (a different value than Name) + +However, there can be only one label policy in your organization. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Organization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md b/exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md new file mode 100644 index 0000000000..d26e9e5e0d --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md @@ -0,0 +1,151 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CompromisedUserAggregateReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-CompromisedUserAggregateReport cmdlet to return general data about compromised users for the last 10 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-CompromisedUserAggregateReport + [-Action ] + [-EndDate ] + [-Page ] + [-PageSize ] + [-StartDate ] + [] +``` + +## DESCRIPTION +This cmdlet returns the following information: + +- Date +- UserCount +- Action + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-CompromisedUserAggregateReport -StartDate 06-01-2020 -EndDate 06-10-2020 -Action Restricted +``` + +This example returns all restricted user accounts for the specified date range. + +## PARAMETERS + +### -Action +The Action parameter filters the results by the compromised user status. Valid values are: + +- Restricted +- Suspicious + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md b/exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md new file mode 100644 index 0000000000..07d5d63148 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md @@ -0,0 +1,153 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-CompromisedUserDetailReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-CompromisedUserDetailReport cmdlet to return detailed information about compromised users for the last 10 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-CompromisedUserDetailReport + [-Action ] + [-EndDate ] + [-Page ] + [-PageSize ] + [-StartDate ] + [] +``` + +## DESCRIPTION +This cmdlet returns the following information: + +- Date +- UserCount +- Action + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-CompromisedUserDetailReport -StartDate 06-01-2020 -EndDate 06-10-2020 -Action Suspicious +``` + +This example returns all suspicious user accounts for the specified date range. + +## PARAMETERS + +### -Action +The Action parameter filters the results by the compromised user status. Valid values are: + +- Restricted +- Suspicious + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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. + +A value for this parameter can't be older than 30 days. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md b/exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md new file mode 100644 index 0000000000..ff118bc38d --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md @@ -0,0 +1,126 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ConfigAnalyzerPolicyRecommendation + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ConfigAnalyzerPolicyRecommendation cmdlet to compare the settings in your existing security policies to the settings that are used in the Standard or Strict preset security policies. Settings that are below the recommend value are returned in the results. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ConfigAnalyzerPolicyRecommendation -RecommendedPolicyType + [[-Identity] ] + [-IsAppliedToDisabled] + [] +``` + +## DESCRIPTION +For information about the policies and their recommended Standard and Strict values, see [Recommended settings for EOP and Microsoft Defender for Office 365 security](https://learn.microsoft.com/defender-office-365/recommended-settings-for-eop-and-office365). + +The output of this cmdlet only returns settings that fall below the value that you've specified as a baseline (Standard or Strict). + +The output contains the following information for each setting: + +- PolicyGroup: The type of policy. The value will be Anti-Spam, Anti-Phishing, Anti-Malware, ATP Safe Links, or ATP Safe Attachments +- SettingName: The name of the setting in the policy. +- SettingNameDescription: A description of the setting. +- Policy: The name of the policy. +- AppliedTo: The number of users or domains that the policy applies to. If the policy isn't applied to anyone (for example, it's disabled), this value will be blank. +- CurrentConfiguration: The current value of the setting. +- LastModified: When the policy was last modified. +- Recommendation: The recommended Standard or Strict value for the setting. +- SettingType: For example, Boolean, String, or Integer. + +If a setting is configured at or better than the Standard or Strict protection profile that you're comparing to, those settings/policies aren't returned in the results + +This cmdlet returns the following output for each setting in each policy that falls below the recommended value. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ConfigAnalyzerPolicyRecommendation -RecommendedPolicyType Strict +``` + +This example runs a comparison using the Strict preset security policy settings as a baseline. + +## PARAMETERS + +### -Identity +This parameter is reserved for internal Microsoft use. + +```yaml +Type: ConfigAnalyzerPolicyRecommendationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -RecommendedPolicyType +The RecommendedPolicyType parameter specifies the preset security policy that you want to use as a baseline. Valid values are: + +- Standard +- Strict + +```yaml +Type: RecommendedPolicyType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsAppliedToDisabled +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ConnectionInformation.md b/exchange/exchange-ps/exchange/Get-ConnectionInformation.md new file mode 100644 index 0000000000..97f9d3efd2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ConnectionInformation.md @@ -0,0 +1,140 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ConnectionInformation + +## SYNOPSIS +This cmdlet is available in the Exchange Online PowerShell module v3.0.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-ConnectionInformation cmdlet to get information about all REST-based connections in the current PowerShell instance with Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default (Default) +``` +Get-ConnectionInformation [] +``` + +### ConnectionId +``` +Get-ConnectionInformation -ConnectionId [] +``` + +### ModulePrefix +``` +Get-ConnectionInformation -ModulePrefix [] +``` + +## DESCRIPTION +The Get-ConnectionInformation cmdlet returns the information about all active REST-based connections with Exchange Online in the current PowerShell instance. This cmdlet is equivalent to the Get-PSSession cmdlet that's used with remote PowerShell sessions. + +The output of the cmdlet contains the following properties: + +- ConnectionId: A unique GUID value for the connection. For example, 8b632b3a-a2e2-8ff3-adcd-6d119d07694b. +- State: For example, Connected. +- Id: An integer that identifies the session in the PowerShell window. The first connection is 1, the second is 2, etc. +- Name: A unique name that's based on the PowerShell environment and Id value. For example, ExchangeOnline_1 for Exchange Online PowerShell or ExchangeOnlineProtection_1 for Security & Compliance PowerShell. +- UserPrincipalName: The account that was used to connect. For example, `laura@contoso.onmicrosoft.com`. +- ConnectionUri: The connection endpoint that was used. For example, `https://outlook.office365.com` for Exchange Online PowerShell or `https://nam12b.ps.compliance.protection.outlook.com` for Security & Compliance PowerShell. +- AzureAdAuthorizationEndpointUri : The Microsoft Entra authorization endpoint for the connection. For example, `https://login.microsoftonline.com/organizations` for Exchange Online PowerShell or `https://login.microsoftonline.com/organizations` for Security & Compliance PowerShell. +- TokenExpiryTimeUTC: When the connection token expires. For example, 9/30/2023 6:42:24 PM +00:00. +- CertificateAuthentication: Whether certificate based authentication (also known as CBA or app-only authentication) was used to connect. Values are True or False. +- ModuleName: The filename and path of the temporary data for the session. For example, C:\Users\laura\AppData\Local\Temp\tmpEXO_a54z135k.qgv +- ModulePrefix: The value specified using the Prefix parameter in the Connect-ExchangeOnline or Connect-IPPSSession command. +- Organization: The value specified using the Organization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA or managed identity connections. +- DelegatedOrganization: The value specified using the DelegatedOrganization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command. +- AppId: The value specified using the AppId parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA connections. +- PageSize: The default maximum number of entries per page in the connection. The default value is 1000, or you can use the PageSize parameter in the Connect-ExchangeOnline command to specify a lower number. Individual cmdlets might also have a PageSize parameter. +- TenantID: The tenant ID GUID value. For example, 3750b40b-a68b-4632-9fb3-5b1aff664079. +- TokenStatus: For example, Active. +- ConnectionUsedForInbuiltCmdlets +- IsEopSession: For Exchange Online PowerShell connections, the value is False. For Security & Compliance PowerShell connections, the value is True. + +## EXAMPLES + +### Example 1 +```powershell +Get-ConnectionInformation +``` + +This example returns a list of all active REST-based connections with Exchange Online in the current PowerShell instance. + +### Example 2 +```powershell +Get-ConnectionInformation -ConnectionId 1a9e45e8-e7ec-498f-9ac3-0504e987fa85 +``` + +This example returns the active REST-based connection with the specified ConnectionId value. + +### Example 3 +```powershell +Get-ConnectionInformation -ModulePrefix Contoso,Fabrikam +``` + +This example returns a list of active REST-based connections that are using the specified prefix values. + +## PARAMETERS + +### -ConnectionId +**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. + +Don't use this parameter with the ModulePrefix parameter. + +```yaml +Type: String[] +Parameter Sets: ConnectionId +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModulePrefix +**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. + +This parameter is meaningful only for connections that were created with the Prefix parameter. + +Don't use this parameter with the ConnectionId parameter. + +```yaml +Type: String[] +Parameter Sets: ModulePrefix +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-Contact.md b/exchange/exchange-ps/exchange/Get-Contact.md similarity index 83% rename from exchange/exchange-ps/exchange/users-and-groups/Get-Contact.md rename to exchange/exchange-ps/exchange/Get-Contact.md index 26026c2289..389fa44712 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-Contact.md +++ b/exchange/exchange-ps/exchange/Get-Contact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-contact +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-Contact @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-Contact cmdlet to view existing contact objects in your organization. This cmdlet returns contacts and mail contacts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -52,7 +51,7 @@ Get-Contact [[-Identity] ] ## DESCRIPTION The Get-Contact cmdlet returns no mail-related properties for mail contacts. Use the Get-MailContact to view mail-related properties for mail contacts. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,17 +78,34 @@ This example uses the Anr parameter to retrieve all mail-enabled contacts whose ## PARAMETERS +### -Identity +The Identity parameter specifies the contact that you want to view. You can use any value that uniquely identifies the contact. For example: + +- Name +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -110,7 +126,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -144,19 +160,16 @@ Accept wildcard characters: False ``` ### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). +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'"`. -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -171,39 +184,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the contact that you want to view. You can use any value that uniquely identifies the contact. For example: - -- Name - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -223,11 +211,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -246,7 +231,9 @@ Accept wildcard characters: False ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -267,9 +254,7 @@ Accept wildcard characters: False The RecipientTypeDetails parameter filters the results by the specified contact subtype. Valid values are: - Contact - - MailContact - - MailForestContact You can specify multiple values separated by commas. @@ -306,20 +291,15 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName - - City - - FirstName - - LastName - - Office ```yaml @@ -340,12 +320,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-ContentFilterConfig.md b/exchange/exchange-ps/exchange/Get-ContentFilterConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-ContentFilterConfig.md rename to exchange/exchange-ps/exchange/Get-ContentFilterConfig.md index 0c4698149b..8de0cb720d 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-ContentFilterConfig.md +++ b/exchange/exchange-ps/exchange/Get-ContentFilterConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-contentfilterconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ContentFilterConfig @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ContentFilterConfig cmdlet to view the content filter configuration for the computer on which the cmdlet is run. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ContentFilterConfig [-DomainController ] [] +Get-ContentFilterConfig [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,12 +62,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-ContentFilterPhrase.md b/exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md similarity index 88% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-ContentFilterPhrase.md rename to exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md index de80bdfcd8..1b1f47b29b 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-ContentFilterPhrase.md +++ b/exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-contentfilterphrase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ContentFilterPhrase @@ -17,24 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ContentFilterPhrase cmdlet to view one or all custom words that the Content Filter agent processes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` Get-ContentFilterPhrase [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ### Phrase ``` Get-ContentFilterPhrase [-Phrase ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,39 +62,39 @@ This example returns all custom words and phrases that contain the words free of ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies a custom word or phrase to display. You must enclose the value of the Identity parameter in quotation marks ("). -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. +The Identity and Phrase parameters are interchangeable. ```yaml -Type: Fqdn -Parameter Sets: (All) +Type: ContentFilterPhraseIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies a custom word or phrase to display. You must enclose the value of the Identity parameter in quotation marks ("). +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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 Identity and Phrase parameters are interchangeable. +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. ```yaml -Type: ContentFilterPhraseIdParameter -Parameter Sets: Identity +Type: Fqdn +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -120,12 +121,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md new file mode 100644 index 0000000000..2c884d0e2f --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md @@ -0,0 +1,178 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ContentMalwareMdoAggregateReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ContentMalwareMdoAggregateReport cmdlet to view a summary detections by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams in Microsoft Defender for Office 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ContentMalwareMdoAggregateReport + [-DetectionTechnology ] + [-EndDate ] + [-Page ] + [-PageSize ] + [-StartDate ] + [-Workload ] + [] +``` + +## DESCRIPTION +For the specified reporting period, the cmdlet returns the following information: + +- Date +- Detection Technology +- Workload +- Count + +By default, the command returns data for the last 14 days. Data for the last 90 days is available. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ContentMalwareMdoAggregateReport -StartDate 1/1/2022 -EndDate 1/4/2022 -Workload OneDriveForBusiness +``` + +This example returns the results for OneDrive detections for the specified date range. + +## PARAMETERS + +### -DetectionTechnology +The DetectionTechnology parameter filters the results by what classified the file as malware. Valid values are: + +- AntiMalware +- AtpSafeAttachment +- Reputation + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -EndDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Workload +The Workload parameter filters the results by where the detected file is located. Valid values are: + +- OneDriveForBusiness +- SharePoint +- Teams + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md new file mode 100644 index 0000000000..eb99b53c05 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md @@ -0,0 +1,180 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ContentMalwareMdoDetailReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the ContentMalwareMdoDetailReport cmdlet to view detection details by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams in Microsoft Defender for Office 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ContentMalwareMdoDetailReport + [-DetectionTechnology ] + [-EndDate ] + [-Page ] + [-PageSize ] + [-StartDate ] + [-Workload ] + [] +``` + +## DESCRIPTION +For the specified reporting period, the cmdlet returns the following information: + +- Date +- File Name +- Workload +- Detection Technology +- File Size +- Last modifying user + +By default, the command returns data for the last 14 days. Data for the last 30 days is available. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ContentMalwareMdoDetailReport -StartDate 1/1/2022 -EndDate 1/4/2022 -DetectionTechnology AtpSafeAttachment +``` + +This example returns the results for detections by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams for the specified date range. + +## PARAMETERS + +### -DetectionTechnology +The DetectionTechnology parameter filters the results by what classified the file as malware. Valid values are: + +- AntiMalware +- AtpSafeAttachment +- Reputation + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -EndDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Workload +The Workload parameter filters the results by where the detected file is located. Valid values are: + +- OneDriveForBusiness +- SharePoint +- Teams + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DataClassification.md b/exchange/exchange-ps/exchange/Get-DataClassification.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DataClassification.md rename to exchange/exchange-ps/exchange/Get-DataClassification.md index 86a4651fe5..9bfe9cc832 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DataClassification.md +++ b/exchange/exchange-ps/exchange/Get-DataClassification.md @@ -1,44 +1,45 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dataclassification -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-DataClassification ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [Get-DlpSensitiveInformationType](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpsensitiveinformationtype) cmdlet in Office 365 Security & Compliance Center PowerShell. +In Exchange Online, this cmdlet has been replaced by the [Get-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchange/get-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the Get-DataClassification cmdlet to view the data classification rules in your organization. This cmdlet shows built-in data classification rules and rules that you created that use document fingerprints. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### RuleCollectionIdentity ``` Get-DataClassification [[-ClassificationRuleCollectionIdentity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ### Identity ``` Get-DataClassification [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,7 +73,7 @@ The ClassificationRuleCollectionIdentity parameter filters the results by the na Type: ClassificationRuleCollectionIdParameter Parameter Sets: RuleCollectionIdentity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: 1 @@ -81,36 +82,18 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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 - - LocalizedName - - Identity GUID value ```yaml Type: DataClassificationIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: 1 @@ -119,17 +102,33 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-DataClassificationConfig.md b/exchange/exchange-ps/exchange/Get-DataClassificationConfig.md new file mode 100644 index 0000000000..03342c3e31 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DataClassificationConfig.md @@ -0,0 +1,56 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DataClassificationConfig + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-DataClassificationConfig cmdlet to view the data classification configuration for your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DataClassificationConfig [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DataClassificationConfig +``` + +This example returns the data classification configuration for your organization. + +## 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md new file mode 100644 index 0000000000..b58632caa0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md @@ -0,0 +1,136 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DataEncryptionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-DataEncryptionPolicy cmdlet to view data encryption policies in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DataEncryptionPolicy [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Data encryption policy cmdlets are the Exchange Online part of Customer Key. For more information, see [Controlling your data in Microsoft 365 using Customer Key](https://aka.ms/customerkey). + +You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DataEncryptionPolicy +``` + +This example returns a summary list of all data encryption policies in the organization. + +### Example 2 +```powershell +Get-DataEncryptionPolicy -Identity "Europe Mailboxes" +``` + +The example returns detailed information for the data encryption policy named Europe Mailboxes. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DataRetentionReport.md b/exchange/exchange-ps/exchange/Get-DataRetentionReport.md new file mode 100644 index 0000000000..1f38d8c687 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DataRetentionReport.md @@ -0,0 +1,133 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DataRetentionReport + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DataRetentionReport cmdlet to view information about data retention in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DataRetentionReport + [-EndDate ] + [-Page ] + [-PageSize ] + [-StartDate ] + [] +``` + +## DESCRIPTION +The following properties are returned by this cmdlet: + +- Organization +- Date +- Action +- DataSource +- MessageCount + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DataRetentionReport -StartDate 04/01/2018 -EndDate 04/30/2018 +``` + +This example lists the data detections for April, 2018. + +## PARAMETERS + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +The StartDate value can't be older than 92 days from today. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Get-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md similarity index 88% rename from exchange/exchange-ps/exchange/database-availability-groups/Get-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md index ed50333c2e..6f519626b5 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Get-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/get-databaseavailabilitygroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-DatabaseAvailabilityGroup @@ -17,31 +16,29 @@ This cmdlet is available only in on-premises Exchange. Use the Get-DatabaseAvailabilityGroup cmdlet to obtain a variety of configuration settings, status and other information about a database availability group (DAG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-DatabaseAvailabilityGroup [[-Identity] ] [-DomainController ] - [-Status] [] +Get-DatabaseAvailabilityGroup [[-Identity] ] + [-DomainController ] + [-Status] + [] ``` ## DESCRIPTION In addition to obtaining a list of DAG members, the Get-DatabaseAvailabilityGroup cmdlet can also be used to view real-time status information about a DAG, such as: - OperationalServers - - PrimaryActiveManager - - ReplicationPort - - NetworkNames - - WitnessShareInUse Use the Status parameter with the command to include the values for these listed properties. Without the Status parameter, the values returned for these properties are blank. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,40 +58,40 @@ This example displays the properties of the DAG DAG2. Because it includes the St ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the name of the DAG to query. ```yaml -Type: Fqdn +Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the DAG to query. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: DatabaseAvailabilityGroupIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Status -The Status parameter instructs the command to query Active Directory for additional information and to include real-time status information in the output. +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 @@ -114,12 +111,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Get-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md similarity index 91% rename from exchange/exchange-ps/exchange/database-availability-groups/Get-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md index 05b878af9e..deb02d5a8e 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Get-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/get-databaseavailabilitygroupnetwork +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-DatabaseAvailabilityGroupNetwork @@ -17,13 +16,15 @@ This cmdlet is available only in on-premises Exchange. Use the Get-DatabaseAvailabilityGroupNetwork cmdlet to display configuration and state information for a database availability group (DAG) network. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-DatabaseAvailabilityGroupNetwork [[-Identity] ] - [-DomainController ] [-Server ] [] + [-DomainController ] + [-Server ] + [] ``` ## DESCRIPTION @@ -32,30 +33,21 @@ State information is returned for subnets and for network interfaces, as describ Valid states for Internet Protocol version 4 (IPv4) subnets - Up: All defined network interfaces in the DAG are functional and available for communication. This is the expected and normal operational state. - - Down: All defined network interfaces in the DAG are nonfunctional and have lost communication with each other and all external hosts. All connected network interfaces are in a Failed or Unreachable state. - - Partitioned: One or more network interfaces in the DAG are in an Unreachable state, but at least two interfaces can communicate with each other or an external host. - - Misconfigured: All subnets for a specified DAG network must have the same values for ReplicationEnabled and IgnoreNetwork. If any one of the subnets isn't configured with the same values for these parameters as all other subnets on the network, all subnets are in a Misconfigured state. - - Unavailable: The network isn't enabled for replication or use by the DAG, or all DAG members attached to the network are inactive or unavailable. - - Unknown: The system was unable to determine the state of the subnet. Valid states for network interfaces - Up: The network interface is functional and can communicate with all other network interfaces. This is the expected and normal operational state. - - Failed: The network interface is unable to communicate with other network interfaces or external hosts, although other network interfaces on the local area network (LAN) are able to communicate with each other and external hosts. - - Unreachable: The system was unable to communicate with at least one network interface whose state is Up. - - Unavailable: The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable.The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable. - - Unknown: The system was unable to determine the state of the network interface. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,35 +74,35 @@ This example gets complete configuration and status information for the network ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the name of a DAG or a DAG network. ```yaml -Type: Fqdn +Type: DatabaseAvailabilityGroupNetworkIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of a DAG or a DAG network. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: DatabaseAvailabilityGroupNetworkIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -118,11 +110,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -143,12 +132,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md b/exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md new file mode 100644 index 0000000000..13ed2a7226 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md @@ -0,0 +1,84 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DefaultTenantBriefingConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module version 3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-DefaultTenantBriefingConfig cmdlet to view the default Briefing email configuration in cloud-based organizations. For details about configuring the Briefing email, see [Configure Briefing email](https://learn.microsoft.com/viva/insights/personal/Briefing/be-admin). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DefaultTenantBriefingConfig + [-ResultSize ] + [] +``` + +## DESCRIPTION +The default Briefing email configuration for the organization affects only new users and existing users who haven't already updated their user settings to opt-in or opt-out of the Briefing email. + +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +``` +Get-DefaultTenantBriefingConfig +``` + +This example returns the default Briefing email configuration for the organization. + +## PARAMETERS + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Deploy personal insights](https://learn.microsoft.com/viva/insights/personal/setup/deployment-guide) diff --git a/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md new file mode 100644 index 0000000000..76bb40fd28 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md @@ -0,0 +1,80 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DefaultTenantMyAnalyticsFeatureConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module version 3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-DefaultTenantMyAnalyticsFeatureConfig cmdlet to view the availability and status of Viva Insights features for the cloud-based organization: digest email, add-in, dashboard, meeting effectiveness survey, and schedule send suggestions. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DefaultTenantMyAnalyticsFeatureConfig [-ResultSize ] [] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Get-DefaultTenantMyAnalyticsFeatureConfig +``` + +This example returns the default opt-in or opt-out information for the various Viva Insights settings. + +## PARAMETERS + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Deploy personal insights](https://learn.microsoft.com/viva/insights/personal/setup/deployment-guide) diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-DeliveryAgentConnector.md b/exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md similarity index 86% rename from exchange/exchange-ps/exchange/mail-flow/Get-DeliveryAgentConnector.md rename to exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md index f641e0e9f4..363d35c76f 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-deliveryagentconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-DeliveryAgentConnector @@ -17,19 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-DeliveryAgentConnector cmdlet to retrieve information about a specific delivery agent connector in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-DeliveryAgentConnector [[-Identity] ] [-DomainController ] +Get-DeliveryAgentConnector [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION -Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://docs.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). +Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,37 +49,37 @@ This example retrieves a list of all delivery agent connectors in your organizat ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +The Identity parameter specifies the GUID or name of the delivery agent connector. ```yaml -Type: Fqdn +Type: DeliveryAgentConnectorIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the GUID or name of the delivery agent connector. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: DeliveryAgentConnectorIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -88,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-DetailZapReport.md b/exchange/exchange-ps/exchange/Get-DetailZapReport.md new file mode 100644 index 0000000000..e2332bf377 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DetailZapReport.md @@ -0,0 +1,151 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DetailZapReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-DetailZapReport cmdlet to view details about zero-hour auto purge (ZAP) activity. By default, the cmdlet shows the last three days of activity, but you can specify up to ten days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DetailZapReport + [[-EndDate] ] + [[-Page] ] + [[-PageSize] ] + [[-StartDate] ] + [] +``` + +## DESCRIPTION +For the reporting period you specify, the cmdlet returns the following default information: + +- Subject +- Received Time +- Sender + +If you append the command with ` | Format-List`, the following additional information is returned for each entry: + +- Recipient +- ZAP Time +- Original Threat +- Original Location +- Updated Threat +- Updated Delivery Location +- Delivery Status +- Detection Technology + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DetailZapReport +``` + +This example retrieves information for the last 3 days. + +### Example 2 +```powershell +Get-DetailZapReport -StartDate 7/1/2023 -EndDate 7/9/2023 +``` + +This example retrieves information for the specified date range. + +## PARAMETERS + +### -EndDate +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". + +If you use this parameter, you also need to use the StartDate parameter. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Page +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 +Default value: 0 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: 0 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +If you use this parameter, you also need to use the StartDate parameter. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 4 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-DetailsTemplate.md b/exchange/exchange-ps/exchange/Get-DetailsTemplate.md similarity index 89% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-DetailsTemplate.md rename to exchange/exchange-ps/exchange/Get-DetailsTemplate.md index a0ad61a17a..71900617a9 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-DetailsTemplate.md +++ b/exchange/exchange-ps/exchange/Get-DetailsTemplate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/get-detailstemplate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-DetailsTemplate @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Get-DetailsTemplate cmdlet to retrieve the attributes for details templates. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-DetailsTemplate [[-Identity] ] [-Confirm] [-DomainController ] [-WhatIf] +Get-DetailsTemplate [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The Get-DetailsTemplate cmdlet retrieves the attributes for one or more details templates. Wildcard characters can be used when specifying the type and language of the details templates. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,33 +58,39 @@ This example retrieves all attributes for all User details template types in all ## PARAMETERS -### -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. +### -Identity +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: -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- User +- Group +- PublicFolder +- SearchDialog +- MailboxAgent +- Contact ```yaml -Type: SwitchParameter +Type: DetailsTemplateIdParameter Parameter Sets: (All) -Aliases: cf +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: Fqdn +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -92,31 +100,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Group - -- PublicFolder - -- SearchDialog - -- MailboxAgent - -- Contact +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: DetailsTemplateIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -141,12 +137,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md new file mode 100644 index 0000000000..a79926c166 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md @@ -0,0 +1,87 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DeviceConditionalAccessPolicy + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DeviceConditionalAccessPolicy cmdlet to view mobile device conditional access policies in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DeviceConditionalAccessPolicy [[-Identity] ] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DeviceConditionalAccessPolicy | Format-Table Name,Enabled,Priority +``` + +This example shows summary information for all mobile device conditional access policies. + +### Example 2 +```powershell +Get-DeviceConditionalAccessPolicy -Identity "Human Resources" +``` + +This example shows details about the mobile device conditional access policy named Human Resources. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md new file mode 100644 index 0000000000..65fe845674 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DeviceConditionalAccessRule + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DeviceConditionalAccessRule cmdlet to view mobile device conditional access rules in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DeviceConditionalAccessRule [[-Identity] ] + [-CompareToWorkload] + [-DomainController ] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DeviceConditionalAccessRule | Format-List Name,Disabled,Priority +``` + +This example shows a summary list of all mobile device conditional access rules. + +### Example 2 +```powershell +Get-DeviceConditionalAccessRule -Identity "Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}" +``` + +This example shows details for the mobile device conditional access rule named Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CompareToWorkload +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md new file mode 100644 index 0000000000..34e6dc1ae0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md @@ -0,0 +1,87 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DeviceConfigurationPolicy + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DeviceConfigurationPolicy cmdlet to view mobile device configuration policies in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DeviceConfigurationPolicy [[-Identity] ] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DeviceConfigurationPolicy | Format-Table Name,Enabled,Priority +``` + +This example shows summary information for all mobile device configuration policies. + +### Example 2 +```powershell +Get-DeviceConfigurationPolicy -Identity "Engineering Group" +``` + +This example shows details about the mobile device configuration policy named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md new file mode 100644 index 0000000000..84afa08d75 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DeviceConfigurationRule + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DeviceConfigurationRule cmdlet to view mobile device configuration rules in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DeviceConfigurationRule [[-Identity] ] + [-CompareToWorkload] + [-DomainController ] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DeviceConfigurationRule | Format-List Name,Disabled,Priority +``` + +This example shows summary information for all mobile device configuration rules. + +### Example 2 +```powershell +Get-DeviceConfigurationRule -Identity "Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}" +``` + +This example shows details about the mobile device configuration rule named Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136} + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CompareToWorkload +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DevicePolicy.md b/exchange/exchange-ps/exchange/Get-DevicePolicy.md new file mode 100644 index 0000000000..f7cb5c1dce --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DevicePolicy.md @@ -0,0 +1,87 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DevicePolicy + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DevicePolicy cmdlet to view all types of Basic Mobility and Security policies in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DevicePolicy [[-Identity] ] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DevicePolicy | Format-Table Name,Type,Enabled,Priority +``` + +This example shows summary information for all mobile device policies. + +### Example 2 +```powershell +Get-DevicePolicy -Identity "Engineering Group" +``` + +This example shows details about the mobile device policy named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md new file mode 100644 index 0000000000..ce5c1c516e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md @@ -0,0 +1,76 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DeviceTenantPolicy + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DeviceTenantPolicy cmdlet to view your organization's mobile device tenant policy in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DeviceTenantPolicy [[-Identity] ] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DeviceTenantPolicy +``` + +This example shows information for your organization's mobile device tenant policy. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DeviceTenantRule.md b/exchange/exchange-ps/exchange/Get-DeviceTenantRule.md new file mode 100644 index 0000000000..3d61488bdc --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DeviceTenantRule.md @@ -0,0 +1,93 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DeviceTenantRule + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DeviceTenantRule cmdlet to view your organization's mobile device tenant rule in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DeviceTenantRule [[-Identity] ] + [-DomainController ] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DeviceTenantRule +``` + +This example shows information for your organization's mobile device tenant rule. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DistributionGroup.md b/exchange/exchange-ps/exchange/Get-DistributionGroup.md new file mode 100644 index 0000000000..601c6b2a36 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DistributionGroup.md @@ -0,0 +1,509 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DistributionGroup + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-DistributionGroup cmdlet to view existing distribution groups or mail-enabled security groups. To view the members of a group, use the Get-DistributionGroupMember cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AnrSet +``` +Get-DistributionGroup [-Anr ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SortBy ] [] +``` + +### Identity +``` +Get-DistributionGroup [[-Identity] ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SortBy ] [] +``` + +### ManagedBySet +``` +Get-DistributionGroup [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-ManagedBy ] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SortBy ] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DistributionGroup +``` + +This examples returns a summary list of all distribution groups and mail-enabled security groups in your organization. + +### Example 2 +```powershell +Get-DistributionGroup -Identity "Marketing Reports" | Format-List +``` + +This example returns detailed information about the distribution group named Marketing Reports. + +### Example 3 +```powershell +Get-DistributionGroup -Anr marketing | Format-Table Name, ManagedBy -Auto +``` + +This example returns all distribution groups and mail-enabled security groups whose names contain the string "marketing" and shows the group owners. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames +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. + +This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, AcceptMessagesOnlyFromDLMembers recipients are shown as GUIDs and the AcceptMessagesOnlyFromDLMembersWithDisplayNames property is empty. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromWithDisplayNames +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. + +This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, AcceptMessagesOnlyFrom recipients are shown as GUIDs and the AcceptMessagesOnlyFromWithDisplayNames property is empty. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeBypassModerationFromSendersOrMembersWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeGrantSendOnBehalfToWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeModeratedByWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedBy +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientTypeDetails +The RecipientTypeDetails parameter filters the results by the specified distribution group subtype. Valid values are: + +- MailNonUniversalGroup +- MailUniversalDistributionGroup +- MailUniversalSecurityGroup +- RoomList + +You can specify multiple values separated by commas. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName +- Alias +- City +- FirstName +- LastName +- Office +- ServerLegacyDN + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-DistributionGroupMember.md b/exchange/exchange-ps/exchange/Get-DistributionGroupMember.md new file mode 100644 index 0000000000..3113e769e2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DistributionGroupMember.md @@ -0,0 +1,231 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DistributionGroupMember + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-DistributionGroupMember cmdlet to view the members of distribution groups and mail-enabled security groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DistributionGroupMember [-Identity] + [-Credential ] + [-DomainController ] + [-IgnoreDefaultScope] + [-IncludeSoftDeletedObjects] + [-ReadFromDomainController] + [-ResultSize ] + [] +``` + +## DESCRIPTION +If your organization has multiple Active Directory domains, you may need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DistributionGroupMember -Identity "Marketing USA" +``` + +This example returns the existing distribution group members for the distribution group named Marketing USA. + +### Example 2 +```powershell +Set-ADServerSettings -ViewEntireForest $true + +Get-DistributionGroupMember -Identity "Marketing Worldwide" +``` + +This example sets the scope of the search to the entire forest by running the Set-ADServerSettings cmdlet, then the Get-DistributionGroupMember cmdlet searches the entire forest for the distribution group members in the Marketing Worldwide distribution group. + +### Example 3 +```powershell +$Groups = Get-UnifiedGroup -ResultSize Unlimited + +$Groups | ForEach-Object { +$group = $_ +Get-UnifiedGroupLinks -Identity $group.Name -LinkType Members -ResultSize Unlimited | ForEach-Object { + New-Object -TypeName PSObject -Property @{ + Group = $group.DisplayName + Member = $_.Name + EmailAddress = $_.PrimarySMTPAddress + RecipientType= $_.RecipientType +}}} | Export-CSV "$env:USERPROFILE\Desktop\Office365GroupMembers.csv" -NoTypeInformation -Encoding UTF8 +``` + +In the cloud-based service, this example downloads a comma-separated value (CSV) file named Office365GroupMembers.csv that contains all Microsoft 365 Groups and members to the current user's Desktop. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedObjects +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. + +Soft-deleted group members are deleted Microsoft 365 Groups or mailboxes that are still recoverable. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-DkimSigningConfig.md b/exchange/exchange-ps/exchange/Get-DkimSigningConfig.md new file mode 100644 index 0000000000..9fe8d4bfd8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DkimSigningConfig.md @@ -0,0 +1,80 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DkimSigningConfig + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-DkimSigningConfig cmdlet to view the DomainKeys Identified Mail (DKIM) signing policy settings for domains in a cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DkimSigningConfig [[-Identity] ] + [] +``` + +## DESCRIPTION +DKIM in Microsoft 365 is an email authentication method that uses a public key infrastructure (PKI), message headers and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DkimSigningConfig +``` + +This example shows a summary list of all DKIM signing policies in your organization. + +### Example 2 +```powershell +Get-DkimSigningConfig -Identity contoso.com | Format-List +``` + +This example shows detailed information for the DKIM signing policy for contoso.com. + +## PARAMETERS + +### -Identity +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). +- Distinguished name (DN) +- GUID + +```yaml +Type: DkimSigningConfigIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md new file mode 100644 index 0000000000..f5a379ed1b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md @@ -0,0 +1,231 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DlpCompliancePolicy to view data loss prevention (DLP) policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpCompliancePolicy [[-Identity] ] + [-DisplayName ] + [-DistributionDetail] + [-ForceValidate ] + [-IncludeExtendedProperties ] + [-IncludeRulesMetadata ] + [-IncludeSimulationResults ] + [-IRMUserRiskConfiguredAnyRule] + [-Summary] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpCompliancePolicy +``` + +This example displays summary information for all DLP policies in the Microsoft Purview compliance portal. + +### Example 2 +```powershell +Get-DlpCompliancePolicy -Identity "PII Limited" | Format-List +``` + +This example displays detailed information for the DLP policy named "PII Limited". + +### Example 3 +```powershell +Get-DlpCompliancePolicy -Identity "PII Limited" -DistributionDetail | Format-List DistributionStatus +``` + +This example displays distribution details for a DLP policy. + +### Example 4 +```powershell +$dlp = Get-DlpCompliancePolicy; ForEach ($d in $dlp){Get-DlpCompliancePolicy -DistributionDetail $d.name | Format-List Name,DistributionStatus} +``` + +This example gets all of the DLP policies in an environment and displays the distribution status for each. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DisplayName +{{ Fill DisplayName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DistributionDetail +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceValidate +{{ Fill ForceValidate Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeExtendedProperties +{{ Fill IncludeExtendedProperties Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeRulesMetadata +{{ Fill IncludeRulesMetadata Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IRMUserRiskConfiguredAnyRule +{{ Fill IRMUserRiskConfiguredAnyRule Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSimulationResults +{{ Fill IncludeSimulationResults Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Summary +{{ Fill Summary Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md b/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md new file mode 100644 index 0000000000..3ec06ed550 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md @@ -0,0 +1,142 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DlpComplianceRule to view data loss prevention (DLP) rules in the Microsoft Purview compliance portal. DLP rules identify and protect sensitive information. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpComplianceRule [[-Identity] ] + [-DisplayName ] + [-IncludeExecutionRuleGuids ] + [-Policy ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpComplianceRule +``` + +This example displays summary information for all DLP rules in the Microsoft Purview compliance portal. + +### Example 2 +```powershell +Get-DlpComplianceRule -Identity "PII SS# Custom" | Format-List +``` + +This example displays detailed information for the DLP rule named "PII SS# Custom". + +### Example 3 +```powershell +Get-DlpComplianceRule -Policy "PII Limited" +``` + +This example lists all the rules included in the DLP compliance policy named "PII Limited". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DisplayName +{{ Fill DisplayName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeExecutionRuleGuids +{{ Fill IncludeExecutionRuleGuids Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpDetailReport.md b/exchange/exchange-ps/exchange/Get-DlpDetailReport.md new file mode 100644 index 0000000000..ec4460246a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpDetailReport.md @@ -0,0 +1,279 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpDetailReport + +## SYNOPSIS +**Note**: This cmdlet has been retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet. + +This cmdlet is available only in the cloud-based service. + +Use the Get-DlpDetailReport cmdlet to list details about data loss prevention (DLP) rule matches for Exchange Online, SharePoint, and OneDrive in your cloud-based organization for the last 30 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpDetailReport [-Action ] + [-Actor ] + [-DlpCompliancePolicy ] + [-DlpComplianceRule ] + [-EndDate ] + [-EventType ] + [-Page ] + [-PageSize ] + [-Source ] + [-StartDate ] + [] +``` + +## DESCRIPTION +The Get-DlpDetailReport cmdlet returns detailed information about specific DLP rule matches for the last 7 days. Although the cmdlet accepts date ranges older than 7 days, only information about the last 7 days are returned. The properties returned include: + +- Date +- Title +- Location +- Severity +- Size +- Source +- Actor +- DLPPolicy +- UserAction +- Justification +- SensitiveInformationType +- SensitiveInformationCount +- SensitiveInformationConfidence +- EventType +- Action +- ObjectId +- Recipients +- AttachmentNames + +To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://learn.microsoft.com/powershell/module/exchange/get-dlpdetectionsreport) cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpDetailReport -StartDate 11/01/2018 -EndDate 11/07/2018 +``` + +The following example lists the details of all the DLP policy activities defined in your organization between the dates specified. + +## PARAMETERS + +### -Action +The Action parameter filters the report by the action taken by DLP policies. Valid values are: + +- BlockAccess +- GenerateIncidentReport +- NotifyUser + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Actor +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpCompliancePolicy +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpComplianceRule +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- DLPActionHits +- DLPActionUndo +- DLPMessages +- DLPPolicyFalsePositive +- DLPPolicyHits +- DLPPolicyOverride +- DLPRuleHits + +To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify DLP event types for DLP reports. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Source +The Source parameter filters the report by workload. Valid values are: + +- EXCH: Exchange Online +- ODB: OneDrive +- SPO: SharePoint + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md b/exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md new file mode 100644 index 0000000000..be1c5ba605 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md @@ -0,0 +1,318 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpDetectionsReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet. + +Use the Get-DlpDetectionsReport cmdlet to list a summary of data loss prevention (DLP) rule matches for Exchange Online, SharePoint and OneDrive in your cloud-based organization for the last 30 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpDetectionsReport [-Action ] + [-AggregateBy ] + [-DlpCompliancePolicy ] + [-DlpComplianceRule ] + [-EndDate ] + [-Expression ] + [-EventType ] + [-Page ] + [-PageSize ] + [-Source ] + [-StartDate ] + [-SummarizeBy ] + [] +``` + +## DESCRIPTION +The Get-DlpDetectionsReport cmdlet returns general DLP detection data that's aggregated per day. The properties returned include: + +- Date +- DLP Policy +- DLP Compliance Rule +- Event Type +- Source +- Message Count + +To see all of these columns (width issues), write the output to a file. For example, `Get-DlpDetectionsReport | Out-String -Width 4096 | Out-File "C:\Users\admin\Desktop\DLP Detections Report.txt"`. + +To see detailed information about each DLP rule match, use the Get-DlpDetailReport cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpDetectionsReport -StartDate 11/01/2018 -EndDate 11/30/2018 +``` + +This example lists the DLP activities for November, 2018. + +## PARAMETERS + +### -Action +The Action parameter filters the report by the action taken by DLP policies. Valid values are: + +- BlockAccess +- GenerateIncidentReport +- NotifyUser + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AggregateBy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpCompliancePolicy +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpComplianceRule +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- DataRetentions +- DLPActionHits +- DLPActionUndo +- DLPByIncidentIdActionHits +- DLPByIncidentIdMessages +- DLPByIncidentIdPolicyFalsePositive +- DLPByIncidentIdPolicyHits +- DLPByIncidentIdPolicyOverride +- DLPByIncidentIdRuleHits +- DLPMessages +- DLPPolicyFalsePositive +- DLPPolicyHits +- DLPPolicyOverride +- DLPRuleHits + +To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify DLP event types for DLP reports. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Expression +This parameter is available only in Security & Compliance PowerShell + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Expression +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Source +The Source parameter filters the report by workload. Valid values are: + +- EXCH: Exchange Online +- ODB: OneDrive +- SPO: SharePoint + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SummarizeBy +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: + +- DLPPolicy +- Domain +- EventType + +You can specify multiple values separated by commas. The values that you specify for this parameter are not displayed in the results (the values in the corresponding columns are blank). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpEdmSchema.md b/exchange/exchange-ps/exchange/Get-DlpEdmSchema.md new file mode 100644 index 0000000000..d9052762b8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpEdmSchema.md @@ -0,0 +1,79 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpEdmSchema + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DlpEdmSchema cmdlet to view exact data match (EDM) data loss prevention (DLP) schemas in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpEdmSchema [[-Identity] ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpEdmSchema +``` + +This example returns a summary list of all DLP EDM schemas in the organization. + +### Example 2 +```powershell +Get-DlpEdmSchema -Identity "Schema for Patient Records" +``` + +This example returns detailed information for the DLP EDM schema named Schema for patient Records. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) + +```yaml +Type: EdmStorageIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Learn about exact data match based sensitive information types](https://learn.microsoft.com/purview/sit-learn-about-exact-data-match-based-sits) diff --git a/exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md b/exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md new file mode 100644 index 0000000000..59707c5464 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md @@ -0,0 +1,284 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpIncidentDetailReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) instead. + +Use the Get-DlpIncidentDetailReport cmdlet to view the details of incidents that happened in the last 30 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpIncidentDetailReport + [-Action ] + [-Actor ] + [-DlpCompliancePolicy ] + [-DlpComplianceRule ] + [-EndDate ] + [-EventType ] + [-Page ] + [-PageSize ] + [-Source ] + [-StartDate ] + [] +``` + +## DESCRIPTION +The output of the Get-DlpIncidentDetailReport cmdlet includes the following properties: + +- Date +- Title +- Location +- Severity +- Size +- Source +- Actor +- DlpCompliancePolicy +- DlpComplianceRule +- UserAction +- Justification +- SensitiveInformationType +- SensitiveInformationCount +- SensitiveInformationConfidence +- EventType +- Action +- DistinctRuleCount +- DistinctPolicyCount +- RuleList +- PolicyList +- ActionList +- SensitiveInformationTypeList +- SensitiveInformationCountList +- SensitiveInformationConfidenceList + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpIncidentDetailReport -StartDate 2022/11 -EndDate 2022/11/30 +``` + +This example lists the details of the all incidents that occurred between the dates specified. + +## PARAMETERS + +### -Action +The Action parameter filters the report by the action taken by DLP policies. Valid values are: + +- BlockAccess +- GenerateIncidentReport +- NotifyUser + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Actor +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpCompliancePolicy +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpComplianceRule +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- DLPByIncidentIdActionHits +- DLPByIncidentIdMessages +- DLPByIncidentIdPolicyFalsePositive +- DLPByIncidentIdPolicyHits +- DLPByIncidentIdPolicyOverride +- DLPByIncidentIdRuleHits + +To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify DLP incident event types for DLP incident reports. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Source +The Source parameter filters the report by workload. Valid values are: + +- EXCH: Exchange Online +- ODB: OneDrive +- SPO: SharePoint +- TEAMS + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md new file mode 100644 index 0000000000..cf21bb85d5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md @@ -0,0 +1,74 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpKeywordDictionary + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DlpKeywordDictionary cmdlet to view data loss prevention (DLP) keyword dictionaries in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpKeywordDictionary [-Name ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpKeywordDictionary | Format-Table -Auto Name,Description +``` + +This example returns a summary list of all DLP keyword dictionaries. + +### Example 2 +```powershell +Get-DlpKeywordDictionary -Name "Financial Data" +``` + +This example returns detailed information about the DLP keyword dictionary named Financial Data. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpPolicy.md b/exchange/exchange-ps/exchange/Get-DlpPolicy.md new file mode 100644 index 0000000000..ef75ad1628 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpPolicy.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpPolicy + +## SYNOPSIS +**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Get-DlpCompliancePolicy and Get-DlpComplianceRule cmdlets instead. + +This cmdlet is functional only in on-premises Exchange. + +Use the Get-DlpPolicy cmdlet to view existing data loss prevention (DLP) policies that are based on transport rules (mail flow rules) in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpPolicy [[-Identity] ] + [-DomainController ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpPolicy +``` + +This example returns a summary list of all DLP policies. + +### Example 2 +```powershell +Get-DlpPolicy "Employee Numbers" | Format-List +``` + +This example returns detailed information about the DLP policy named Employee Numbers. The command is piped to the Format-List cmdlet to display the detailed configuration of the specified DLP policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: DlpPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/policy-and-compliance-dlp/Get-DlpPolicyTemplate.md b/exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md similarity index 79% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpPolicyTemplate.md rename to exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md index bdbd3279ef..bafb90d765 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md @@ -1,32 +1,35 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlppolicytemplate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-DlpPolicyTemplate ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). -Use the Get-DlpPolicyTemplate cmdlet to view existing data loss prevention (DLP) policy templates in your Exchange organization. +This cmdlet is functional only in on-premises Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the Get-DlpPolicyTemplate cmdlet to view existing data loss prevention (DLP) policy templates that are based on transport rules (mail flow rules) in your Exchange organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-DlpPolicyTemplate [[-Identity] ] [-DomainController ] [] +Get-DlpPolicyTemplate [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,37 +49,37 @@ This example returns detailed information about the DLP policy template named GL ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: DlpPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -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. ```yaml -Type: DlpPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -85,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md new file mode 100644 index 0000000000..99d0a14db7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md @@ -0,0 +1,147 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpSensitiveInformationType + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DlpSensitiveInformationType cmdlet to list the sensitive information types that are defined for your organization in the Microsoft Purview compliance portal. Sensitive information types are used by data loss prevention (DLP) rules to check for sensitive information such as social security, passport, or credit card numbers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpSensitiveInformationType [[-Identity] ] + [-Capability ] + [-IncludeDetails] + [-IncludeElements ] + [-Organization ] + [] +``` + +## DESCRIPTION +The RecommendedConfidence property of the returned objects contains a value that represents the default (or recommended) confidence level that should be used with the corresponding sensitive information type. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpSensitiveInformationType +``` + +This example lists all the sensitive information types defined for your organization. + +### Example 2 +```powershell +Get-DlpSensitiveInformationType -Identity "Credit Card Number" | Format-List +``` + +This example lists all the properties of the sensitive information type named "Credit Card Number". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the sensitive information type that you want to view. Valid values are: + +- Name +- Id (GUID value) + +```yaml +Type: SensitiveInformationTypeIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Capability +{{ Fill Capability Description }} + +```yaml +Type: ClassificationCapabilityType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeDetails +{{ Fill IncludeDetails Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeElements +{{ Fill IncludeElements Description }} + +```yaml +Type: ClassificationPrimitiveElementType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md new file mode 100644 index 0000000000..322925e01f --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md @@ -0,0 +1,97 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpSensitiveInformationTypeRulePackage + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-DlpSensitiveInformationTypeRulePackage cmdlet to view data loss prevention (DLP) sensitive information type rule packages in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpSensitiveInformationTypeRulePackage [[-Identity] ] + [-Capability ] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DlpSensitiveInformationTypeRulePackage +``` + +This example returns a summary list of all sensitive information type rule packages in the organization. + +### Example 2 +```powershell +Get-DlpSensitiveInformationTypeRulePackage -Identity "Microsoft Rule Package" | Format-List +``` + +This example returns detailed information for the sensitive information type rule package named Microsoft Rule Package. + +## PARAMETERS + +### -Identity +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 +- LocalizedName +- GUID (from the Identity value) + +```yaml +Type: SensitiveInformationTypeRuleCollectionIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Capability +{{ Fill Capability Description }} + +```yaml +Type: ClassificationCapabilityType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md b/exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md new file mode 100644 index 0000000000..b89d2416f2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md @@ -0,0 +1,106 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DlpSiDetectionsReport + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet. + +Use the Get-DlpSiDetectionsReport cmdlet to view information about data loss prevention (DLP) sensitive information type detections in the Microsoft Purview compliance portal for the last 90 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DlpSiDetectionsReport [-EndDate ] + [-SensitiveType ] + [] +``` + +## DESCRIPTION +For the reporting period you specify, the cmdlet returns the following information: + +- Organization +- Date +- SensitiveType: The GUID value of the DLP sensitive information type. To match the GUID value to the name of the sensitive information type, replace `` with the GUID value and run this command: `Get-DlpSensitiveInformationType -Identity `. +- DocumentCount: The number of documents that contain the detected sensitive information type. +- ProtectionStatus: Values are Unprotected (the sensitive information type is not defined in any DLP policy) or Protected (the sensitive information type is defined in a DLP policy). +- DlpComplianceRuleIds: The GUID value of the DLP compliance rule that detected the sensitive information type (for ProtectionStatus values of Protected). To match the GUID value to the name of the DLP compliance rule, replace `` with the GUID value and run this command: `Get-DlpComplianceRule -Identity `. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DLPSiDetectionsReport +``` + +This example returns all DLP sensitive information type detections. + +### Example 2 +```powershell +Get-DLPSiDetectionsReport -SensitiveType 0e9b3178-9678-47dd-a509-37222ca96b42 -EndDate 4/8/2019 +``` + +This example returns detections for the sensitive information type 0e9b3178-9678-47dd-a509-37222ca96b42 (EU Debit Card Number) during the specified date range. + +## PARAMETERS + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SensitiveType +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md b/exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md new file mode 100644 index 0000000000..05ddacb11c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md @@ -0,0 +1,204 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DnssecStatusForVerifiedDomain + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-DnssecStatusForVerifiedDomain cmdlet to view information about Domain Name System Security (DNSSEC) for accepted domains in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DnssecStatusForVerifiedDomain [-DomainName] + [-Confirm] + [-SkipDnsValidation] + [-SkipMtaStsValidation] + [-SkipMxValidation] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-DnssecStatusForVerifiedDomain -DomainName contoso.com + +DnssecFeatureStatus : Enabled +ExpectedMxRecord : Microsoft.Exchange.Management.ProvisioningTasks.ExpectedMxRecordInfo +Errors : {} +Warnings : {} +DnsValidation : Microsoft.Exchange.Management.ProvisioningTasks.DnsValidationResult +MxValidation : Microsoft.Exchange.Management.ProvisioningTasks.MxValidationResult +MtaStsValidation : Microsoft.Exchange.Management.ProvisioningTasks.MtaStsValidationResult +``` + +This example shows the basic output of the cmdlet for the domain contoso.com. + +### Example 2 +```powershell +PS C:\> $result = Get-DnssecStatusForVerifiedDomain -DomainName contoso.com; $result; "DNSSEC feature"; $result.DnssecFeatureStatus; "DNSSEC validation"; $result.DnsValidation; "Expected MX record: [$($result.ExpectedMxRecord.Record)]"; "", "MX validation"; $result.MxValidation; "MTA-STS validation"; $result.MtaStsValidation + +DnssecFeatureStatus : Enabled +ExpectedMxRecord : Microsoft.Exchange.Management.ProvisioningTasks.ExpectedMxRecordInfo +Errors : {} +Warnings : {} +DnsValidation : Microsoft.Exchange.Management.ProvisioningTasks.DnsValidationResult +MxValidation : Microsoft.Exchange.Management.ProvisioningTasks.MxValidationResult +MtaStsValidation : Microsoft.Exchange.Management.ProvisioningTasks.MtaStsValidationResult + +DNSSEC feature +Value : Enabled + +DNSSEC validation +DnssecSupport : Valid +Errors : {} +Warnings : {} + +Expected MX record: [@ 60 IN MX 10 contoso-com.e-v1.mx.microsoft] + +MX validation +Status : Valid +ActualMxRecords : {@ 60 IN MX 10 contoso-com.e-v1.mx.microsoft} +Errors : {} +Warnings : {} + +MTA-STS validation +Status : Valid +MtaStsAvailable : False +MtaStsMode : Unavailable +Errors : {} +Warnings : {} +``` + +This example contains the output from Example 1 and readable values for the DnsValidation, MxValidation, and MtaStsValidation properties. This command confirms the following information: + +- The DNSSEC-secured MX record is present in the domain. +- The priority of the MX record is 10. +- The MTA-STS Policy contains the DNSSEC-secured mail host (if MTA-STS present). + +## PARAMETERS + +### -DomainName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipDnsValidation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipMtaStsValidation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipMxValidation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/active-directory/Get-DomainController.md b/exchange/exchange-ps/exchange/Get-DomainController.md similarity index 82% rename from exchange/exchange-ps/exchange/active-directory/Get-DomainController.md rename to exchange/exchange-ps/exchange/Get-DomainController.md index f1f3f90b92..b36194819e 100644 --- a/exchange/exchange-ps/exchange/active-directory/Get-DomainController.md +++ b/exchange/exchange-ps/exchange/Get-DomainController.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-domaincontroller +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-DomainController @@ -17,40 +16,45 @@ This cmdlet is available only in on-premises Exchange. Use the Get-DomainController cmdlet to view a list of domain controllers that exist in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### GlobalCatalog ``` -Get-DomainController [-GlobalCatalog] [-Forest ] - [-Credential ] [] +Get-DomainController [-GlobalCatalog] + [-Forest ] + [-Credential ] + [] ``` ### DomainController ``` Get-DomainController [-DomainName ] - [-Credential ] [] + [-Credential ] + [] ``` ## DESCRIPTION The Get-DomainController cmdlet is used by the Exchange admin center to populate fields that display domain controller information. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$UserCredentials = Get-Credential; Get-DomainController -DomainName corp.contoso.com -Credential $UserCredentials | Format-Table -AutoSize Name, ADSite +$UserCredentials = Get-Credential + +Get-DomainController -DomainName corp.contoso.com -Credential $UserCredentials | Format-Table -AutoSize Name,ADSite ``` This example retrieves a list of global catalog servers in the corp.contoso.com domain. Because a different set of credentials are required to access this domain, the Get-Credential cmdlet is used to obtain the username and password from the user. The first command displays a prompt to the user that accepts the username and password. The credentials are then stored in the $UserCredentials variable. The second command uses the $UserCredentials variable for the Credential parameter value. To make the list more readable, the output is piped to the Format-Table cmdlet and only the Name and ADSite properties are displayed. -For more information about pipelining and the Format-Table cmdlet, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining and the Format-Table cmdlet, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ## PARAMETERS @@ -73,7 +77,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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). If you use the Forest parameter, the credentials are used to access the forest. @@ -127,12 +131,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md new file mode 100644 index 0000000000..d988b7788e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md @@ -0,0 +1,513 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DynamicDistributionGroup + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-DynamicDistributionGroup cmdlet to view existing dynamic distribution groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AnrSet +``` +Get-DynamicDistributionGroup [-Anr ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-IncludeSystemObjects] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-ResultSize ] + [-SortBy ] + [] +``` + +### Identity +``` +Get-DynamicDistributionGroup [[-Identity] ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-IncludeSystemObjects] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-ResultSize ] + [-SortBy ] + [] +``` + +### ManagedBySet +``` +Get-DynamicDistributionGroup [-ManagedBy ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-IncludeSystemObjects] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-ResultSize ] + [-SortBy ] + [] +``` + +## DESCRIPTION +A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DynamicDistributionGroup +``` + +This example returns a summary list of all dynamic distribution groups in your organization. + +### Example 2 +```powershell +Get-DynamicDistributionGroup -Identity "Marketing Department" | Format-List +``` + +This example returns detailed information about the dynamic distribution group named Marketing Department. + +### Example 3 +```powershell +Get-DynamicDistributionGroup -Anr *research* | Format-Table Name, ManagedBy -Auto +``` + +This example returns all dynamic distribution groups whose names contain the string "research" and shows the group owners. + +### Example 4 +```powershell +$FTE = Get-DynamicDistributionGroup "Full Time Employees" + +Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer +``` + +This example returns the members for the dynamic distribution group named Full Time Employees. The first command stores the dynamic distribution group object in the variable $FTE. The second command uses the Get-Recipient cmdlet to list the recipients that match the criteria defined for the dynamic distribution group. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames +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. + +This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, AcceptMessagesOnlyFromDLMembers recipients are shown as GUIDs and the AcceptMessagesOnlyFromDLMembersWithDisplayNames property is empty. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromWithDisplayNames +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. + +This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, AcceptMessagesOnlyFrom recipients are shown as GUIDs and the AcceptMessagesOnlyFromWithDisplayNames property is empty. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeBypassModerationFromSendersOrMembersWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeGrantSendOnBehalfToWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeModeratedByWithDisplayNames +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. + +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSystemObjects +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedBy +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName +- Alias + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-DynamicDistributionGroupMember.md b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md new file mode 100644 index 0000000000..d93483e17c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md @@ -0,0 +1,131 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-DynamicDistributionGroupMember + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-DynamicDistributionGroupMember cmdlet to view the calculated membership list that's stored on dynamic distribution group objects. The results from this cmdlet are updated every 24 hours. + +Use the Get-DistributionGroupMember cmdlet to view the members of distribution groups and mail-enabled security groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-DynamicDistributionGroupMember [-Identity] + [-Credential ] + [-IncludeSoftDeletedObjects] + [-ResultSize ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-DynamicDistributionGroupMember -Identity "Temporary Employees" +``` + +This example returns the existing members for the dynamic distribution group named Temporary Employees. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the dynamic distribution group. You can use any value that uniquely identifies the group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: DynamicDistributionGroupMemberIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedObjects +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md new file mode 100644 index 0000000000..6ca809c445 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EOPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-EOPProtectionPolicyRule cmdlet to view rules for Exchange Online Protection (EOP) protections in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EOPProtectionPolicyRule [[-Identity] ] + [-State ] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-EOPProtectionPolicyRule | Format-Table Name,State +``` + +This example returns a summary list of the rules for EOP protections in preset security policies. + +### Example 2 +```powershell +Get-EOPProtectionPolicyRule -Identity "Strict Preset Security Policy" +``` + +This example returns detailed information about the rule named Strict Preset Security Policy. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -State +The State parameter filters the results by the state of the rule. Valid values are: + +- Enabled +- Disabled. + +```yaml +Type: RuleState +Parameter Sets: (All) +Aliases: +Accepted values: Enabled, Disabled +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXOCasMailbox.md b/exchange/exchange-ps/exchange/Get-EXOCasMailbox.md new file mode 100644 index 0000000000..72e7aca6f2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXOCasMailbox.md @@ -0,0 +1,450 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXOCasMailbox + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXOCasMailbox cmdlet to view the Client Access settings that are configured on mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Get-EXOCasMailbox [[-Identity] ] + [-ActiveSyncDebugLogging] + [-ExternalDirectoryObjectId ] + [-Filter ] + [-GetImapProtocolLog] + [-GetPopProtocolLog] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-PrimarySmtpAddress ] + [-Properties ] + [-PropertySets ] + [-ProtocolSettings] + [-ReadIsOptimizedForAccessibility] + [-ResultSize ] + [-SendLogsTo ] + [-UserPrincipalName ] + [] +``` + +### Anr +``` +Get-EXOCasMailbox [-Anr ] + [-ActiveSyncDebugLogging] + [-Filter ] + [-GetImapProtocolLog] + [-GetPopProtocolLog] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-Properties ] + [-PropertySets ] + [-ProtocolSettings] + [-ReadIsOptimizedForAccessibility] + [-ResultSize ] + [-SendLogsTo ] + [] +``` + +## DESCRIPTION +This cmdlet returns a variety of client access settings for one or more mailboxes. These settings include options for Outlook on the web, Exchange ActiveSync, POP3, and IMAP4. + +## EXAMPLES + +### Example 1 +```powershell +Get-EXOCASMailbox -Identity "JeffHay@contoso.com" +``` + +This example returns the values of the following client access settings for the user with Identity Jeffhay@contoso.com: + +- ActiveSyncEnabled +- EwsEnabled +- OWAEnabled +- PopEnabled +- ImapEnabled +- MAPIEnabled +- ECPEnabled + +## PARAMETERS + +### -Identity +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) +- GUID + +Otherwise, you can use any other value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Domain\\Username +- Email address +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +You can't use this parameter with the ExternalDirectoryObjectId, Identity, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Anr +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActiveSyncDebugLogging +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties, see [Get-EXOCasMailbox property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exocasmailbox-property-sets) and [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GetImapProtocolLog +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GetPopProtocolLog +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Properties +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). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PropertySets +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) +- ActiveSync +- Ews +- Imap +- Mapi +- Pop +- ProtocolSettings +- All + +You can specify multiple values separated by commas. + +For more information about the properties that are included in each property set, see [Get-EXOCasMailbox property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exocasmailbox-property-sets). + +```yaml +Type: PropertySet[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProtocolSettings +The ProtocolSettings switch returns the server names, TCP ports and encryption methods for the following settings: + +- ExternalImapSettings +- InternalImapSettings +- ExternalPopSettings +- InternalPopSettings +- ExternalSmtpSettings +- InternalSmtpSettings + +You don't need to specify a value with this switch. + +To see these values, you need to use a formatting cmdlet. For example, `Get-CasMailbox laura@contoso.com -ProtocolSettings | Format-List`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadIsOptimizedForAccessibility +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendLogsTo +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +The following Get-CasMailbox parameters are not available or supported in Get-EXOCasMailbox: + +- IgnoreDefaultScope +- ReadIsOptimizedForAccessibility +- SortBy + +## OUTPUTS + +### Output types +The following properties are removed by design from Get-EXOCasMailbox output: + +- RunspaceId +- Servername +- OriginatingServer +- IsValid + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXOMailbox.md b/exchange/exchange-ps/exchange/Get-EXOMailbox.md new file mode 100644 index 0000000000..fb1295de5f --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXOMailbox.md @@ -0,0 +1,559 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXOMailbox + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXOMailbox cmdlet to view mailbox objects and attributes, populate property pages, or supply mailbox information to other tasks. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Get-EXOMailbox [[-Identity] ] + [-Archive] + [-Async] + [-ExternalDirectoryObjectId ] + [-Filter ] + [-GroupMailbox] + [-InactiveMailboxOnly] + [-IncludeInactiveMailbox] + [-MailboxPlan ] + [-Migration] + [-OrganizationalUnit ] + [-PrimarySmtpAddress ] + [-Properties ] + [-PropertySets ] + [-PublicFolder] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SoftDeletedMailbox] + [-UserPrincipalName ] + [] +``` + +### Anr +``` +Get-EXOMailbox [-Anr ] + [-Archive] + [-Async] + [-Filter ] + [-GroupMailbox] + [-InactiveMailboxOnly] + [-IncludeInactiveMailbox] + [-MailboxPlan ] + [-Migration] + [-OrganizationalUnit ] + [-Properties ] + [-PropertySets ] + [-PublicFolder] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SoftDeletedMailbox] + [] +``` + +## DESCRIPTION +By default, this cmdlet returns a summary list (a minimum set of properties) of all mailboxes in your organization. + +## EXAMPLES + +### Example 1 +```powershell +Get-EXOMailbox -ResultSize unlimited +``` + +This example returns a summary list of all mailboxes in the organization, and includes the default set of minimum output properties. To return additional properties, use the Properties and/or PropertySets parameters. + +### Example 2 +```powershell +Get-EXOMailbox -PropertySets Archive +``` + +This example returns the Properties that are defined in Archive property set. For a complete list of these properties, see [Get-EXOMailbox property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exomailbox-property-sets). + +### Example 3 +```powershell +Get-EXOMailbox -Properties Name,DistinguishedName,Guid -PropertySets Archive,Audit +``` + +This example returns a summary list of all mailboxes in the organization, and includes the following properties: + +- The properties in Archive and Audit property sets. +- The Name and DistinguishedName properties. + +### Example 4 +```powershell +Get-EXOMailbox -Identity John@contoso.com -Properties DisplayName,EmailAddresses,Alias +``` + +This example returns the specified properties for the mailbox John@contoso.com. + +## PARAMETERS + +### -Identity +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) +- GUID + +Otherwise, you can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Domain\\Username +- Email address +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +You can't use this parameter with the ExternalDirectoryObjectId, Identity, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Anr +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Archive +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Async +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties, see [Get-EXOMailbox property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exomailbox-property-sets) and [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InactiveMailboxOnly +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. + +To return both active mailboxes and inactive mailboxes in the results, don't use this switch. Instead, use the IncludeInactiveMailbox switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeInactiveMailbox +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. + +To return only inactive mailboxes in the results, don't use this switch. Instead, use the InactiveMailboxOnly switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxPlan +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 +- Alias +- Display name +- Distinguished name (DN) +- GUID + +A mailbox plan specifies the permissions and features available to a mailbox user in cloud-based organizations. You can see the available mailbox plans by using the Get-MailboxPlan cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Migration +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Properties +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). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PropertySets +The PropertySets parameter specifies a logical grouping of properties that are returned in the output of this cmdlet. Valid values are: + +- All +- Minimum (this is the default value) +- AddressList +- Archive +- Audit +- Custom +- Delivery +- Hold +- Moderation +- Move +- Policy +- PublicFolder +- Quota +- Resource +- Retention +- SCL +- SoftDelete +- StatisticsSeed + +You can specify multiple values separated by commas. + +For more information about the properties that are included in each property set, see [Get-EXOMailbox property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exomailbox-property-sets). + +```yaml +Type: PropertySet[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolder +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientTypeDetails +The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are: + +- DiscoveryMailbox +- EquipmentMailbox +- GroupMailbox +- LegacyMailbox +- LinkedMailbox +- LinkedRoomMailbox +- RoomMailbox +- SchedulingMailbox +- SharedMailbox +- TeamMailbox +- UserMailbox + +You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SoftDeletedMailbox +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types + +The following Get-Mailbox parameters aren't available or functional in Get-EXOMailbox: + +- Async +- GroupMailbox +- Migration +- PublicFolder +- SortBy + +## OUTPUTS + +### Output types +The following properties aren't included in the output of Get-EXOMailbox: + +- RunspaceId +- Servername +- AdminDisplayVersion +- DelayReleaseHoldApplied +- EnforcedTimestamps +- Description +- OriginatingServer +- IsValid +- ObjectState + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md new file mode 100644 index 0000000000..d15ff5ab3c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md @@ -0,0 +1,194 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXOMailboxFolderPermission + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-ExOMailboxFolderPermission cmdlet to view folder-level permissions in mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EXOMailboxFolderPermission [[-Identity] ] + [-ExternalDirectoryObjectId ] + [-GroupMailbox] + [-PrimarySmtpAddress ] + [-User ] + [-UserPrincipalName ] + [] +``` + +## DESCRIPTION +Use this cmdlet to retrieve folder level permission in the mailbox. + +## EXAMPLES + +### Example 1 +```powershell +Get-EXOMailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports +``` + +This example returns the current list of user permissions for the Reports subfolder in the Marketing folder in John's mailbox. + +### Example 2 +```powershell +Get-EXOMailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports -User Kim@contoso.com +``` + +This example returns the permissions for the same folder in John's mailbox, but only for the user Kim. + +## PARAMETERS + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Email address +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -GroupMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -User +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +**Note**: If you specify a user that doesn't have permission to access the mailbox folder, the command will throw an exception. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission) + +[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission) + +[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission) + +[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission) diff --git a/exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md new file mode 100644 index 0000000000..b6d21cf8d8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md @@ -0,0 +1,281 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXOMailboxFolderStatistics + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXOMailboxFolderStatistics cmdlet to retrieve information about the folders in a specified mailbox, including the number and size of items in the folder, the folder name and ID, and other information. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EXOMailboxFolderStatistics + [-Archive] + [-DiagnosticInfo ] + [-ExternalDirectoryObjectId ] + [-Folderscope ] + [-Identity ] + [-IncludeAnalysis] + [-IncludeOldestAndNewestItems] + [-IncludeSoftDeletedRecipients] + [-PrimarySmtpAddress ] + [-UserPrincipalName ] + [] +``` + +## DESCRIPTION +A mailbox can have hidden items that are never visible to the user and are only used by applications. The Get-EXOMailboxFolderStatistics cmdlet can return hidden items for the following values: FolderSize, FolderAndSubfolderSize, ItemsInFolder and ItemsInFolderAndSubfolders. + +Don't confuse Get-EXOMailboxFolderStatistics cmdlet (folders) with the Get-EXOMailboxStatistics cmdlet (mailboxes). + +## EXAMPLES + +### Example 1 +```powershell +Get-EXOMailboxFolderStatistics -Identity admin@contoso.com +``` + +This example returns statistics for all mailbox folders. Default is FolderScope All. + +### Example 2 +```powershell +Get-EXOMailboxFolderStatistics -Identity admin@contoso.com -FolderScope Calendar -IncludeOldestAndNewestItems +``` + +This example returns statistics only for calendar folders. + +### Example 3 +```powershell +Get-EXOMailbox -ResultSize Unlimited | Get-EXOMailboxFolderStatistics -FolderScope Inbox | Format-Table Identity,ItemsInFolderAndSubfolders,FolderAndSubfolderSize -AutoSize +``` + +This example uses the FolderScope parameter to view Inbox folder statistics for all mailboxes. + +## PARAMETERS + +### -Archive +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DiagnosticInfo +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Folderscope +The FolderScope parameter specifies the scope of the search by folder type. Valid values include: + +- All +- Archive +- Calendar +- Clutter +- Contacts +- ConversationHistory +- DeletedItems +- Drafts +- Inbox +- Journal +- JunkEmail +- LegacyArchiveJournals +- ManagedCustomFolder +- NonIpmRoot +- Notes +- Outbox +- Personal +- RecoverableItems +- RssSubscriptions +- SentItems +- SyncIssues +- Tasks + +```yaml +Type: ElcFolderType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -IncludeAnalysis +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeOldestAndNewestItems +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedRecipients +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md b/exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md new file mode 100644 index 0000000000..d008aa8f24 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md @@ -0,0 +1,238 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXOMailboxPermission + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXOMailboxPermission cmdlet to retrieve permissions on a mailbox. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default (Default) +``` +Get-EXOMailboxPermission [-ResultSize ] + [] +``` + +### Identity +``` +Get-EXOMailboxPermission + [-ExternalDirectoryObjectId ] + [-Identity ] + [-Owner] + [-PrimarySmtpAddress ] + [-ResultSize ] + [-SoftDeletedMailbox] + [-User ] + [-UserPrincipalName ] + [] +``` + +## DESCRIPTION +The output of this cmdlet shows the following information: + +- Identity: The mailbox in question. +- User: The security principal (user, security group, Exchange management role group, etc.) that has permission to the mailbox. +- AccessRights: The permission that the security principal has on the mailbox. The available values are ChangeOwner (change the owner of the mailbox), ChangePermission (change the permissions on the mailbox), DeleteItem (delete the mailbox), ExternalAccount (indicates the account isn't in the same domain), FullAccess (open the mailbox, access its contents, but can't send mail) and ReadPermission (read the permissions on the mailbox). Whether the permissions are allowed or denied is indicated in the Deny column. +- IsInherited: Whether the permission is inherited (True) or directly assigned to the mailbox (False). Permissions are inherited from the mailbox database and/or Active Directory. Typically, directly assigned permissions override inherited permissions. +- Deny: Whether the permission is allowed (False) or denied (True). Typically, deny permissions override allow permissions. + +By default, the following permissions are assigned to user mailboxes: + +- FullAccess and ReadPermission are directly assigned to NT AUTHORITY\SELF. This entry gives a user permission to their own mailbox. +- FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes. +- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. +- FullAccess is inherited by NT AUTHORITY\SYSTEM and ReadPermission is inherited by NT AUTHORITY\NETWORK. +- FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers. + +By default, other security groups and role groups inherit permissions to mailboxes based on their location (on-premises Exchange or Microsoft 365). + +## EXAMPLES + +### Example 1 +```powershell +Get-EXOMailboxPermission -Identity john@contoso.com +``` + +This example return the permission the user has on mailboxes + +## PARAMETERS + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Owner +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SoftDeletedMailbox +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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: + +- Name +- Distinguished name (DN) +- Canonical DN +- GUID + +**Note**: Currently, the value that you provide for this parameter is case sensitive. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md b/exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md new file mode 100644 index 0000000000..cbe03cc816 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md @@ -0,0 +1,275 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXOMailboxStatistics + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXOMailboxStatistics cmdlet to return information about a mailbox, such as the size of the mailbox, the number of messages it contains, and the last time it was accessed. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EXOMailboxStatistics + [-Archive] + [-DatabaseGuid ] + [-ExchangeGuid ] + [-Identity ] + [-IncludeMoveHistory] + [-IncludeMoveReport] + [-IncludeSoftDeletedRecipients] + [-PrimarySmtpAddress ] + [-Properties ] + [-PropertySets ] + [-UserPrincipalName ] + [] +``` + +## DESCRIPTION +You can use the detailed move history and a move report output from this cmdlet to troubleshoot a move request. To view the move history, you must pass this cmdlet as an object. Move histories are retained in the mailbox database, are numbered incrementally, and the last run move request is always numbered 0. + +You can only see move reports and move history for completed move requests. + +## EXAMPLES + +### Example 1 +```powershell +Get-EXOMailboxStatistics -Identity john@contoso.com +``` + +This example retrieves the mailbox statistics for the specified mailbox. Only the minimum set of properties are returned. + +### Example 2 +```powershell +Get-EXOMailboxStatistics -Identity john@contoso.com -Properties SystemMessageSize,SystemMessageSizeWarningQuota,SystemMessageCount +``` + +This example retrieves the minimum set of properties and the specified properties for the specified mailbox. + +## PARAMETERS + +### -Archive +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DatabaseGuid +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ExchangeGuid +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Domain\\Username +- Email address +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -IncludeMoveHistory +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeMoveReport +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedRecipients +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Properties +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). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PropertySets +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) +- All + +You can specify multiple values separated by commas. + +For more information about the properties that are included in each property set, see [Get-EXOMailboxStatistics property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exomailboxstatistics-property-sets). + +```yaml +Type: PropertySet[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md b/exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md new file mode 100644 index 0000000000..91b5ebab64 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md @@ -0,0 +1,291 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXOMobileDeviceStatistics + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXOMobileDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Get-EXOMobileDeviceStatistics [-Identity ] + [-ActiveSync] + [-ExternalDirectoryObjectId ] + [-GetMailboxLog] + [-NotificationEmailAddresses ] + [-OWAforDevices] + [-PrimarySmtpAddress ] + [-RestApi] + [-ShowRecoveryPassword] + [-UniversalOutlook] + [-UserPrincipalName ] + [] +``` + +### MobileDeviceIdentity +``` +Get-EXOMobileDeviceStatistics [-Mailbox ] + [-ActiveSync] + [-GetMailboxLog] + [-NotificationEmailAddresses ] + [-OWAforDevices] + [-RestApi] + [-ShowRecoveryPassword] + [-UniversalOutlook] + [] +``` + +## DESCRIPTION +This cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. + +## EXAMPLES + +### Example 1 +```powershell +Get-EXOMobileDeviceStatistics -Mailbox john.doe@contoso.com +``` + +This example returns the statistics of all devices linked to user with email john.doe@contoso.com + +### Example 2 +```powershell +Get-EXOMobileDeviceStatistics -Mailbox john.doe@contoso.com -ActiveSync +``` + +This example returns the statistics for active sync devices linked to user with email john.doe@contoso.com + +## PARAMETERS + +### -Identity +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 +- DeviceID + +You can't use this parameter with the ExternalDirectoryObjectId, Mailbox, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Mailbox +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 +- User ID or user principal name (UPN) + +You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: MobileDeviceIdentity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -ActiveSync +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -GetMailboxLog +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationEmailAddresses +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OWAforDevices +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -RestApi +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowRecoveryPassword +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UniversalOutlook +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXORecipient.md b/exchange/exchange-ps/exchange/Get-EXORecipient.md new file mode 100644 index 0000000000..fd34b10f9d --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXORecipient.md @@ -0,0 +1,410 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXORecipient + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXORecipient cmdlet to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Get-EXORecipient [[-Identity] ] + [-ExternalDirectoryObjectId ] + [-Filter ] + [-IncludeSoftDeletedRecipients] + [-OrganizationalUnit ] + [-PrimarySmtpAddress ] + [-Properties ] + [-PropertySets ] + [-RecipientPreviewFilter ] + [-RecipientType ] + [-RecipientTypeDetails ] + [-ResultSize ] + [-UserPrincipalName ] + [] +``` + +### Anr +``` +Get-EXORecipient [-Anr ] + [-Filter ] + [-IncludeSoftDeletedRecipients] + [-OrganizationalUnit ] + [-Properties ] + [-PropertySets ] + [-RecipientPreviewFilter ] + [-RecipientType ] + [-RecipientTypeDetails ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +Get-EXORecipient cmdlet can be used to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). + +## EXAMPLES + +### Example 1 +```powershell +Get-EXORecipient -ResultSize 100 +``` + +This example returns the first 100 recipient objects in name sorted order. + +### Example 2 +```powershell +Get-EXORecipient -Identity john@contosot.com +``` + +This example returns the recipient attribute details for the user john@contoso.com + +## PARAMETERS + +### -Identity +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) +- GUID + +Otherwise, you can use any value that uniquely identifies the recipient. For example: + +- Name +- Alias +- Distinguished name (DN) +- Domain\\Username +- Email address +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +You can't use this parameter with the ExternalDirectoryObjectId, Identity, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Anr +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties, see [Get-EXORecipient property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exorecipient-property-sets) and [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedRecipients +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Properties +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). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PropertySets +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) +- Archive +- Custom +- MailboxMove +- Policy + +For more information about the properties that are included in each property set, see [Get-EXORecipient property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exorecipient-property-sets). + +```yaml +Type: PropertySet[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientPreviewFilter +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientType +The RecipientType parameter filters the results by the specified recipient type. Valid values are: + +- DynamicDistributionGroup +- MailContact +- MailNonUniversalGroup +- MailUniversalDistributionGroup +- MailUniversalSecurityGroup +- MailUser +- PublicFolder +- UserMailbox + +You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientTypeDetails +The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are: + +- DiscoveryMailbox +- DynamicDistributionGroup +- EquipmentMailbox +- GroupMailbox +- GuestMailUser +- LegacyMailbox +- LinkedMailbox +- LinkedRoomMailbox +- MailContact +- MailForestContact +- MailNonUniversalGroup +- MailUniversalDistributionGroup +- MailUniversalSecurityGroup +- MailUser +- PublicFolder +- PublicFolderMailbox +- RemoteEquipmentMailbox +- RemoteRoomMailbox +- RemoteSharedMailbox +- RemoteTeamMailbox +- RemoteUserMailbox +- RoomList +- RoomMailbox +- SchedulingMailbox +- SharedMailbox +- SharedWithMailUser +- TeamMailbox +- UserMailbox + +You can specify multiple values separated by commas. + +The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EXORecipientPermission.md b/exchange/exchange-ps/exchange/Get-EXORecipientPermission.md new file mode 100644 index 0000000000..3ec37b7a9d --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EXORecipientPermission.md @@ -0,0 +1,224 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EXORecipientPermission + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-EXORecipientPermission cmdlet to view information about SendAs permissions that are configured for users in a cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default (Default) +``` +Get-EXORecipientPermission + [-AccessRights ] + [-ResultSize ] + [-Trustee ] + [] +``` + +### Identity +``` +Get-EXORecipientPermission [[-Identity] ] + [-AccessRights ] + [-ExternalDirectoryObjectId ] + [-PrimarySmtpAddress ] + [-ResultSize ] + [-Trustee ] + [-UserPrincipalName ] + [] +``` + +## DESCRIPTION +This cmdlet is used to view/manage information about SendAs permissions that are configured for users in a cloud-based organization. Send As permission allows delegates to use the mailbox to send messages. After this permission is assigned to a delegate, any message that the delegate sends from the mailbox will appear to have been sent by the mailbox owner. However, this permission doesn't allow a delegate to sign in to the user's mailbox. It only allows users to open the mailbox. If this permission is assigned to a group, a message sent by the delegate will appear to have been sent by the group. + +## EXAMPLES + +### Example 1 +```powershell +Get-EXORecipientPermission -ResultSize 100 +``` +Above example returns recipient permission for first 100 mailbox users in the name sorted order. + +## PARAMETERS + +### -Identity +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 +- Mail users +- Mail contacts +- Distribution groups +- Dynamic distribution groups + +For the best performance, we recommend using the following values to identify the recipient: + +- User ID or user principal name (UPN) +- GUID + +Otherwise, you can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Domain\\Username +- Email address +- LegacyExchangeDN +- SamAccountName + +You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddress, or UserPrincipalName parameters. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AccessRights +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalDirectoryObjectId +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. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Trustee +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 +- Mail users with a Microsoft account +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- User Principal name (UPN) + +You need to use this parameter with the Identity, PrimarySmtpAddress, UserPrincipalName, or ExternalDirectoryObjectId parameters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-EcpVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access-servers/Get-EcpVirtualDirectory.md rename to exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md index d4e0de1bea..1235c14ba1 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-ecpvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-EcpVirtualDirectory @@ -19,7 +18,7 @@ Use the Get-EcpVirtualDirectory cmdlet to view Exchange Control Panel (ECP) virt The ECP web management interface was introduced in Exchange Server 2010. In Exchange Server 2013 and Exchange Server 2016, the EAC virtual directories and the corresponding management cmdlets still use ECP in the name. You can use these cmdlets to manage ECP virtual directories on Exchange 2010, Exchange 2013 and Exchange 2016 servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,7 +27,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-EcpVirtualDirectory -Server [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ### Identity @@ -36,11 +36,12 @@ Get-EcpVirtualDirectory -Server Get-EcpVirtualDirectory [[-Identity] ] [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,13 +71,11 @@ This example returns a summary list of all Exchange Control Panel virtual direct ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -97,11 +96,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -120,7 +116,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -176,12 +174,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-EdgeSubscription.md b/exchange/exchange-ps/exchange/Get-EdgeSubscription.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Get-EdgeSubscription.md rename to exchange/exchange-ps/exchange/Get-EdgeSubscription.md index 4aaa9fcfe5..4e288d9293 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-EdgeSubscription.md +++ b/exchange/exchange-ps/exchange/Get-EdgeSubscription.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-edgesubscription +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-EdgeSubscription @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-EdgeSubscription cmdlet to retrieve information about Edge Subscriptions in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-EdgeSubscription [[-Identity] ] [-DomainController ] [] +Get-EdgeSubscription [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION Run the Get-EdgeSubscription cmdlet on an Exchange server in your organization. This cmdlet retrieves the list of Edge Subscriptions. Each Edge Transport server that's subscribed to the Exchange organization has a separate Edge Subscription. You can use this cmdlet to view the Edge Subscription information for a specific Edge Transport server. You can also use this cmdlet to view the Edge Subscription information for all Edge Transport servers subscribed to Active Directory sites. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,37 +49,37 @@ This example retrieves the Edge Subscription information for the Edge Transport ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +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: Fqdn +Type: TransportServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: TransportServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -87,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-EdgeSyncServiceConfig.md b/exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/Get-EdgeSyncServiceConfig.md rename to exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md index 0466ca5263..fa33987f4c 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-edgesyncserviceconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-EdgeSyncServiceConfig @@ -17,17 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Get-EdgeSyncServiceConfig cmdlet to retrieve the edge synchronization services settings that control the general synchronization behavior shared by all Microsoft Exchange EdgeSync services. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-EdgeSyncServiceConfig [[-Identity] ] [-DomainController ] - [-Site ] [] +Get-EdgeSyncServiceConfig [[-Identity] ] + [-DomainController ] + [-Site ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -93,12 +94,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md similarity index 75% rename from exchange/exchange-ps/exchange/users-and-groups/Get-EligibleDistributionGroupForMigration.md rename to exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md index aeb624ae91..fe9c386e7f 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-EligibleDistributionGroupForMigration.md +++ b/exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md @@ -1,26 +1,22 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-eligibledistributiongroupformigration -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-EligibleDistributionGroupForMigration ## SYNOPSIS -This cmdlet is available only in the cloud-based service. +This cmdlet is functional only in the cloud-based service. -Use the Get-EligibleDistributionGroupForMigration cmdlet to identify distribution groups that can be upgraded to Office 365 groups. You can't upgrade mail-enabled security groups to Office 365 groups. +Use the Get-EligibleDistributionGroupForMigration cmdlet to identify distribution groups that can be upgraded to Microsoft 365 Groups. You can't upgrade mail-enabled security groups to Microsoft 365 Groups. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,18 +24,20 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-EligibleDistributionGroupForMigration [[-Identity] ] [-OrganizationalUnit ] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ### ManagedBy ``` Get-EligibleDistributionGroupForMigration [-ManagedBy ] [-OrganizationalUnit ] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,12 +46,12 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Get-EligibleDistributionGroupForMigration -ResultSize unlimited ``` -This example returns a summary list of all distribution groups that can be upgraded to Office 365 groups. +This example returns a summary list of all distribution groups that can be upgraded to Microsoft 365 Groups. ## PARAMETERS ### -Identity -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 an Office 365 Group. +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. @@ -61,7 +59,7 @@ You can't use this parameter with the ManagedBy parameter. Type: DistributionGroupIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: 1 @@ -74,15 +72,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID You can't use this parameter with the Identity parameter. @@ -91,7 +84,7 @@ You can't use this parameter with the Identity parameter. Type: GeneralRecipientIdParameter Parameter Sets: ManagedBy Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -104,18 +97,15 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -131,7 +121,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -145,12 +135,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md new file mode 100644 index 0000000000..1cb8b5a7a3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md @@ -0,0 +1,126 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EmailAddressPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-EmailAddressPolicy cmdlet to view email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EmailAddressPolicy [[-Identity] ] + [-DomainController ] + [-IncludeMailboxSettingOnlyPolicy] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-EmailAddressPolicy +``` + +This example returns a summary list of all email address policies in the organization. + +### Example 2 +```powershell +Get-EmailAddressPolicy -Identity "Contoso Employees" +``` + +This example returns detailed information for the email address policy named Contoso Employees. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeMailboxSettingOnlyPolicy +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. + +Microsoft Exchange Server 2010 supports policies that contain only address policy settings and policies that contain address policy settings and mailbox management configuration. Exchange 2010 doesn't support policies that contain only mailbox management configuration, but Exchange 2003 policies that contain only mailbox management configuration are, by default, preserved and not upgraded. + +The attributes of address policies that contain only mailbox management configuration can't be modified in Exchange 2010. These policies can only be removed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-EmailTenantSettings.md b/exchange/exchange-ps/exchange/Get-EmailTenantSettings.md new file mode 100644 index 0000000000..025fdca73a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EmailTenantSettings.md @@ -0,0 +1,66 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EmailTenantSettings + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-EmailTenantSettings cmdlet to view whether priority account protection is enabled or disabled in your Microsoft Defender for Office 365 organization. For more information about priority accounts, see [Manage and monitor priority accounts](https://learn.microsoft.com/microsoft-365/admin/setup/priority-accounts). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EmailTenantSettings [[-Identity] ] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-EmailTenantSettings | Format-List Identity,EnablePriorityAccountProtection +``` + +This example shows whether priority account protection is enabled or disabled in the organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-EtrLimits.md b/exchange/exchange-ps/exchange/Get-EtrLimits.md new file mode 100644 index 0000000000..759a8d045c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EtrLimits.md @@ -0,0 +1,50 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EtrLimits + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-EtrLimits cmdlet to show information about [mail flow rule (also known as transport rule) limits in Exchange Online](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#journal-transport-and-inbox-rule-limits), as well the current usage and the largest rule IDs in terms of size and regular expression character count. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EtrLimits [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-EtrLimits +``` + +This example returns information about the number and size of mail flow rules in the organization, and the organizational limits for mail flow rules. + +## 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-EventLogLevel.md b/exchange/exchange-ps/exchange/Get-EventLogLevel.md similarity index 85% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-EventLogLevel.md rename to exchange/exchange-ps/exchange/Get-EventLogLevel.md index b33d06b3c6..cc925f4f3d 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-EventLogLevel.md +++ b/exchange/exchange-ps/exchange/Get-EventLogLevel.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-eventloglevel +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-EventLogLevel @@ -17,22 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Get-EventLogLevel cmdlet to display a list of Exchange event categories and the corresponding log levels on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Server ``` -Get-EventLogLevel -Server [-DomainController ] [] +Get-EventLogLevel -Server + [-DomainController ] + [] ``` ### Identity ``` -Get-EventLogLevel [[-Identity] ] [-DomainController ] [] +Get-EventLogLevel [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,15 +48,30 @@ This example displays the event categories and log levels for the server Exchang ## PARAMETERS +### -Identity +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. + +```yaml +Type: ECIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Server 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use this parameter with the Identity parameter. @@ -89,35 +107,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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. - -```yaml -Type: ECIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md b/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md new file mode 100644 index 0000000000..30df67b8a5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md @@ -0,0 +1,69 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-EventsFromEmailConfiguration + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-EventsFromEmailConfiguration cmdlet to view the events from email settings on a mailbox. These settings define whether Outlook or Outlook on the web (formerly known as Outlook Web App) automatically discovers events from email messages and adds them to the user's calendar. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-EventsFromEmailConfiguration [-Identity] + [] +``` + +## DESCRIPTION +**Note**: The following output properties have been deprecated: EventReservationProcessingLevel, FoodEstablishmentReservationProcessingLevel, InvoiceProcessingLevel, and ServiceReservationProcessingLevel. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-EventsFromEmailConfiguration -Identity peter@contoso.com +``` + +This example retrieves all events from email settings for peter@contoso.com's mailbox. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-ExchangeAssistanceConfig.md b/exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md similarity index 88% rename from exchange/exchange-ps/exchange/organization/Get-ExchangeAssistanceConfig.md rename to exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md index 2146104528..d2853de47a 100644 --- a/exchange/exchange-ps/exchange/organization/Get-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-exchangeassistanceconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ExchangeAssistanceConfig @@ -17,17 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ExchangeAssistanceConfig cmdlet to view the configuration information for the URLs that Microsoft Exchange Help uses to connect to the source of the documentation. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ExchangeAssistanceConfig [[-Identity] ] [-DomainController ] +Get-ExchangeAssistanceConfig [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,37 +47,37 @@ This example shows the configuration information for all organizations and forma ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +The Identity parameter specifies the identity of the organization. ```yaml -Type: Fqdn +Type: OrganizationIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identity of the organization. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: OrganizationIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -86,12 +86,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Get-ExchangeCertificate.md similarity index 91% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Get-ExchangeCertificate.md rename to exchange/exchange-ps/exchange/Get-ExchangeCertificate.md index 1fb4ffb137..eec9e123ff 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-ExchangeCertificate.md +++ b/exchange/exchange-ps/exchange/Get-ExchangeCertificate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-exchangecertificate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ExchangeCertificate @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ExchangeCertificate cmdlet to view Exchange certificates that are installed on Exchange servers. This cmdlet returns Exchange self-signed certificates, certificates that were issued by a certification authority and pending certificate requests (also known as certificate signing requests or CSRs). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -51,80 +50,48 @@ Get-ExchangeCertificate [[-Thumbprint] ] By default, this cmdlet returns the following certificate properties in the summary list view: - Thumbprint: The unique digest of the certificate data. An example thumbprint value is 78E1BE82F683EE6D8CB9B9266FC1185AE0890C41. - -- Services: The Exchange services that the certificate is assigned to by using the Enable-ExchangeCertificate cmdlet. Values are None, Federation, IIS, IMAP, POP, SMTP, UM, and UMCallRouter. You'll see the value None in certificates that aren't used with Exchange (for example, the WMSvc-\ certificate that's used for the IIS Web Management Service). - +- Services: The Exchange services that the certificate is assigned to by using the Enable-ExchangeCertificate cmdlet. Values are None, Federation, IIS, IMAP, POP, SMTP, UM, and UMCallRouter. You'll see the value None in certificates that aren't used with Exchange (for example, the `WMSvc-` certificate that's used for the IIS Web Management Service). - Subject: Contains the X.500 value in the certificate's Subject Name field. The important part is the CN= value. -If you append | Format-List to the command, the cmdlet returns these additional certificate properties: - -- AccessRules: The host names or FQDNs in the certificate's Subject Alternative Name field. +If you append ` | Format-List` to the command, the cmdlet returns these additional certificate properties: +- AccessRules: Typically, this value is multiple instances of the value System.Security.AccessControl.CryptoKeyAccessRule separated by commas. - CertificateDomains: The host names or FQDNs in the certificate's Subject Alternative Name field. - - HasPrivateKey: Whether or not the certificate contains a private key. - - IsSelfSigned: Whether or not the certificate is self-signed (not issued by a certification authority). - - Issuer: Who issued the certificate. - - NotAfter: The certificate expiration date. - - NotBefore: The certificate issue date. - - PublicKeySize: The size of the public key in bytes. - - RootCAType: The type of CA that signed the certificate. Values are None (this value is found on the Microsoft Exchange Server Auth Certificate, and also new self-signed certificates that you create), ThirdParty, Enterprise, Registry (this value is found on Exchange self-signed certificates), GroupPolicy, or Unknown (this value is found on pending certificate requests). - - SerialNumber: The unique serial number of the certificate. - - Status: The status of the certificate. Values are DateInvalid, Invalid, PendingRequest, RevocationCheckFailure, Revoked, Unknown, Untrusted or Valid -If you append | Format-List \* to the command, the cmdlet returns these additional certificate properties: +If you append ` | Format-List *` to the command, the cmdlet returns these additional certificate properties: - Archived - - CertificateRequest: This property contains the hash value of the certificate request. - - DnsNameList - - EnhancedKeyUsageList: Typically, this value is Server Authentication (1.3.6.1.5.5.7.3.1). - - Extensions - - FriendlyName - - Handle - -- Identity: This value is \\\\ - +- Identity: This value uses the syntax ServerFQDN\\Thumbprint. - IISServices - - IssuerName: Typically, this value is System.Security.Cryptography.X509Certificates.X500DistinguishedName. - - KeyIdentifier - - PrivateKey: Typically, this value is System.Security.Cryptography.RSACryptoServiceProvider. - - PrivateKeyExportable: If this value is True, you can export the certificate from the server. - - PublicKey: Typically, this value is System.Security.Cryptography.RSACryptoServiceProvider. - - RawData - - SendAsTrustedIssuer - - ServicesStringForm - - SignatureAlgorithm: Typically, this value is System.Security.Cryptography.Oid. - - SubjectKeyIdentifier - -- SubjectName: Typically, this value is System.Security.Cryptography.X509Certificates.X500DistinguishedName . - +- SubjectName: Typically, this value is System.Security.Cryptography.X509Certificates.X500DistinguishedName. - Version: Typically, this value is 3. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -158,59 +125,76 @@ This example shows which certificate Exchange will select for the domain name ma ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Thumbprint +The Thumbprint parameter specifies the thumbprint value of the certificate that you want to view. -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. +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. ```yaml -Type: Fqdn -Parameter Sets: (All) +Type: String +Parameter Sets: Thumbprint Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -DomainName -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. +### -Identity +The Identity parameter specifies the certificate that you want to view. Valid values are: + +- `ServerNameOrFQDN\Thumbprint` +- `Thumbprint` + +You can't use this parameter with the Server parameter. + +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. ```yaml -Type: MultiValuedProperty -Parameter Sets: (All) +Type: ExchangeCertificateIdParameter +Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the certificate that you want to view. Valid values are: +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. -- \ +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -You can't use this parameter with the Server parameter. +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` -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. +### -DomainName +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: ExchangeCertificateIdParameter -Parameter Sets: Identity +Type: MultiValuedProperty +Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -236,11 +220,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -260,35 +241,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Thumbprint -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. - -```yaml -Type: String -Parameter Sets: Thumbprint -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md similarity index 83% rename from exchange/exchange-ps/exchange/organization/Get-ExchangeDiagnosticInfo.md rename to exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md index 7d97677202..ca36c14478 100644 --- a/exchange/exchange-ps/exchange/organization/Get-ExchangeDiagnosticInfo.md +++ b/exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md @@ -1,12 +1,12 @@ --- external help file: Microsoft.Exchange.Management-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangediagnosticinfo applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 title: Get-ExchangeDiagnosticInfo schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ExchangeDiagnosticInfo @@ -16,17 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ExchangeDiagnosticInfo cmdlet to return information about processes that are running on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ExchangeDiagnosticInfo [-Argument ] [-Component ] [-Process ] - [-Server ] [-Unlimited] [] +Get-ExchangeDiagnosticInfo [-Argument ] + [-Component ] + [-Process ] + [-Server ] + [-Unlimited] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -39,7 +43,9 @@ This example returns a summary list of all Exchange processes that are running o ### Example 2 ```powershell -[xml]$edi = Get-ExchangeDiagnosticInfo; $edi.Diagnostics.Processlocator.Process | Format-Table -Auto Name,ID,Guid +[xml]$edi = Get-ExchangeDiagnosticInfo + +$edi.Diagnostics.Processlocator.Process | Format-Table -Auto Name,ID,Guid ``` This example display the XML output of the command in format that's easier to read. @@ -51,7 +57,7 @@ The Argument parameter specifies a valid argument to use with the specified Comp Common Argument values that you can use with virtually Component value are Help and Verbose. -To see the Argument values that are available for a given Component value, run the command Get-ExchangeDiagnosticInfo -Process \ -Component \ -Argument Help +To see the Argument values that are available for a given Component value, run the command `Get-ExchangeDiagnosticInfo -Process ProcessName -Component ComponentName -Argument Help`. ```yaml Type: String @@ -69,7 +75,7 @@ Accept wildcard characters: False ### -Component 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 \ -Argument Help. +To see the Component values that are available for a given Process value, run the command `Get-ExchangeDiagnosticInfo -Process ProcessName -Argument Help`. ```yaml Type: String @@ -106,11 +112,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -149,12 +152,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ExchangeFeature.md b/exchange/exchange-ps/exchange/Get-ExchangeFeature.md new file mode 100644 index 0000000000..6bf6bb29bf --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ExchangeFeature.md @@ -0,0 +1,132 @@ +--- +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 +ms.author: lusassl +ms.reviewer: srvar +--- + +# Get-ExchangeFeature + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Get-ExchangeFeature cmdlet to return information about features that are flighted on Exchange servers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ExchangeFeature [-Identity ] + [-FeatureID ] + [-RingLevel ] + [-Status ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExchangeFeature -Status "Enabled" +``` + +This example returns all enabled features. + +### Example 2 +```powershell +Get-ExchangeFeature -FeatureID "PING.1.0" +``` + +This example returns information about the feature with the feature id PING.1.0. + +## PARAMETERS + +### -Identity +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +If you don't use this parameter, the command returns information for all Exchange servers. + +```yaml +Type: ServerIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -FeatureID +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RingLevel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Status +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-ExchangeServer.md b/exchange/exchange-ps/exchange/Get-ExchangeServer.md similarity index 91% rename from exchange/exchange-ps/exchange/organization/Get-ExchangeServer.md rename to exchange/exchange-ps/exchange/Get-ExchangeServer.md index 1346d6171c..4331ccbb63 100644 --- a/exchange/exchange-ps/exchange/organization/Get-ExchangeServer.md +++ b/exchange/exchange-ps/exchange/Get-ExchangeServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-exchangeserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ExchangeServer @@ -19,7 +18,7 @@ Use the Get-ExchangeServer cmdlet to view the properties of Exchange servers. When you run the Get-ExchangeServer cmdlet with no parameters, it returns the attributes of all the servers in the Exchange organization. To return specific server properties (including domain controller information) where the Get-ExchangeServer cmdlet has to contact servers directly or perform a complex or slow calculation, make sure you use the Status parameter. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,20 +26,22 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-ExchangeServer -Domain [-DomainController ] - [-Status] [] + [-Status] + [] ``` ### Identity ``` Get-ExchangeServer [[-Identity] ] [-DomainController ] - [-Status] [] + [-Status] + [] ``` ## DESCRIPTION The ExchangeVersion attribute returned is the minimum version of Microsoft Exchange that you can use to manage the returned object. This attribute isn't the same as the version of Exchange displayed in the Exchange admin center when you select Server Configuration. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,6 +61,29 @@ This example returns detailed information about the Exchange server named Mailbo ## PARAMETERS +### -Identity +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 +- GUID +- Distinguished name (DN) +- ExchangeLegacyDN + +You can't use this parameter with the Domain parameter. + +```yaml +Type: ServerIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Domain The Domain parameter filters the results by the fully qualified domain name (FQDN) of the domain (for example, contoso.com). @@ -96,32 +120,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- GUID - -- Distinguished name (DN) - -- ExchangeLegacyDN - -You can't use this parameter with the Domain parameter. - -```yaml -Type: ServerIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Status 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. @@ -145,12 +143,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-ExchangeServerAccessLicense.md b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md similarity index 77% rename from exchange/exchange-ps/exchange/organization/Get-ExchangeServerAccessLicense.md rename to exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md index fea64ace6d..4d95f68bfd 100644 --- a/exchange/exchange-ps/exchange/organization/Get-ExchangeServerAccessLicense.md +++ b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-exchangeserveraccesslicense +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ExchangeServerAccessLicense @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ExchangeServerAccessLicense cmdlet to return a list of licenses in use in your Exchange organization. This refers to the specific legal name of the license, as defined in the Microsoft Product List and is representative of your licenses when you run this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,15 +27,12 @@ Get-ExchangeServerAccessLicense [] ## DESCRIPTION The Get-ExchangeServerAccessLicense cmdlet returns a collection of these license names: -- Exchange Server 2016 Standard CAL +- Exchange Server Standard CAL +- Exchange Server Enterprise CAL +- Exchange Server Standard Edition +- Exchange Server Enterprise Edition -- Exchange Server 2016 Enterprise CAL - -- Exchange Server 2016 Standard Edition - -- Exchange Server 2016 Enterprise Edition - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,7 +41,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Get-ExchangeServerAccessLicense ``` -This example retrieves a list of Exchange 2016 licenses in your organization. +This example retrieves a list of Exchange licenses in your organization. ## PARAMETERS @@ -54,12 +50,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md similarity index 81% rename from exchange/exchange-ps/exchange/organization/Get-ExchangeServerAccessLicenseUser.md rename to exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md index 031b0e265b..4c62c163e4 100644 --- a/exchange/exchange-ps/exchange/organization/Get-ExchangeServerAccessLicenseUser.md +++ b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-exchangeserveraccesslicenseuser +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ExchangeServerAccessLicenseUser @@ -17,18 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ExchangeServerAccessLicenseUser cmdlet to return a list of unique users for the specified license name. Each object contains the FQDN or primary SMTP address of the mailbox and the license that's associated with it. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ExchangeServerAccessLicenseUser -LicenseName [] +Get-ExchangeServerAccessLicenseUser -LicenseName + [] ``` ## DESCRIPTION The Get-ExchangeServerAccessLicenseUser cmdlet returns a collection of unique users for the specified license name. The list of unique users represents an estimate of your licenses when you run this cmdlet. Each object contains the FQDN or primary SMTP address of the mailbox and the license name to which it's associated. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,13 +44,12 @@ This example returns the unique users for the license named Exchange Server 2016 ### -LicenseName 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 2016 Standard CAL +- `Exchange Server Standard CAL` +- `Exchange Server Enterprise CAL` +- `Exchange Server Standard Edition` +- `Exchange Server Enterprise Edition` -- Exchange Server 2016 Enterprise CAL - -- Exchange Server 2016 Standard Edition - -- Exchange Server 2016 Enterprise Edition +The `` value is 2013, 2016, or 2019. ```yaml Type: String @@ -70,12 +69,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-ExchangeSettings.md b/exchange/exchange-ps/exchange/Get-ExchangeSettings.md similarity index 85% rename from exchange/exchange-ps/exchange/organization/Get-ExchangeSettings.md rename to exchange/exchange-ps/exchange/Get-ExchangeSettings.md index 65272ac357..9088353301 100644 --- a/exchange/exchange-ps/exchange/organization/Get-ExchangeSettings.md +++ b/exchange/exchange-ps/exchange/Get-ExchangeSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-exchangesettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ExchangeSettings @@ -17,20 +16,30 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ExchangeSettings cmdlet to view customized Exchange setting objects that are stored in Active Directory. Use the New-ExchangeSettings to create the settings object, and the Set-ExchangeSettings cmdlet to define the actual settings. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ExchangeSettings [[-Identity] ] [-ConfigName ] - [-Database ] [-Diagnostic] [-DiagnosticArgument ] [-DomainController ] - [-Force] [-GenericScopeName ] [-GenericScopes ] [-GenericScopeValue ] - [-Organization ] [-Process ] [-Server ] [-User ] +Get-ExchangeSettings [[-Identity] ] + [-ConfigName ] + [-Database ] + [-Diagnostic] + [-DiagnosticArgument ] + [-DomainController ] + [-Force] + [-GenericScopeName ] + [-GenericScopes ] + [-GenericScopeValue ] + [-Organization ] + [-Process ] + [-Server ] + [-User ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,6 +59,26 @@ This example returns a summary list of all Exchange setting objects. ## PARAMETERS +### -Identity +The Identity parameter specifies the name of the Exchange setting object. You can use any value that uniquely identifies the object. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: ExchangeSettingsIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ConfigName The ConfigName parameter filter the results by the specified property name. The value you specify is visible in the EffectiveSetting property. @@ -72,11 +101,8 @@ Accept wildcard characters: False The Database parameter filters the results by mailbox database. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml @@ -93,10 +119,12 @@ Accept wildcard characters: False ``` ### -Diagnostic -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. +Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -143,7 +171,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -175,7 +205,7 @@ Accept wildcard characters: False ``` ### -GenericScopes -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 "\=\","\=\"... +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[] @@ -206,28 +236,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the Exchange setting object. You can use any value that uniquely identifies the object. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ExchangeSettingsIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Organization This parameter is reserved for internal Microsoft use. @@ -264,11 +272,8 @@ Accept wildcard characters: False The Server parameter filters the results by Exchange server. You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml @@ -285,7 +290,7 @@ Accept wildcard characters: False ``` ### -User -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. +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 @@ -305,12 +310,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md new file mode 100644 index 0000000000..08f6210738 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md @@ -0,0 +1,99 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ExoInformationBarrierPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ExoInformationBarrierPolicy cmdlet to view information barrier policies in your Exchange Online organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ExoInformationBarrierPolicy [[-Identity] ] [-ShowFriendlyValues] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoInformationBarrierPolicy -ShowFriendlyValues| Format-List Name,FriendlyRecipientFilter,InformationBarrierSegmentName +``` + +This example shows a summary list of all Exchange Online information barrier policies in the organization. + +### Example 2 +```powershell +Get-ExoInformationBarrierPolicy -Identity bf542929-a8c4-4167-88fb-3e5ef68a1dca -ShowFriendlyValues +``` + +This example shows detailed information for the specified Exchange Online information barrier policy. + +## PARAMETERS + +### -Identity +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 +- Display name +- Distinguished name (DN) +- GUID + +```yaml +Type: MailboxPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -ShowFriendlyValues +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: + +- FriendlyRecipientFilter +- InformationBarrierSegmentName + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md new file mode 100644 index 0000000000..8e1ddb9d25 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md @@ -0,0 +1,97 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ExoInformationBarrierRelationship + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ExoInformationBarrierRelationship cmdlet to view information barrier relationships in your Exchange Online organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ExoInformationBarrierRelationship -RecipientId1 -RecipientId2 + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoInformationBarrierRelationship -RecipientId1 "Akia Al-Zuhairi" -RecipientId2 "Gabriela Laureano" +``` + +This example shows the Exchange Online information barrier relationship between the two specified recipients. + +## PARAMETERS + +### -RecipientId1 +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientId2 +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md new file mode 100644 index 0000000000..b0caf1efcb --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md @@ -0,0 +1,96 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ExoInformationBarrierSegment + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ExoInformationBarrierSegment to view information barrier segments in your Exchange Online organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ExoInformationBarrierSegment [[-Identity] ] [-ShowFriendlyValues] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoInformationBarrierSegment -ShowFriendlyValues| Format-List DisplayName,Name,FriendlyRecipientFilter,AssociatedPolicy +``` + +This example shows a summary list of all Exchange Online information barrier segments in the organization. + +### Example 2 +```powershell +Get-ExoInformationBarrierSegment -Identity "Investment Banking" -ShowFriendlyValues +``` + +This example shows detailed information for the specified Exchange Online information barrier segment. + +## PARAMETERS + +### -Identity +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 +- Display name +- Distinguished name (DN) +- GUID + +```yaml +Type: InformationBarrierSegmentIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -ShowFriendlyValues +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md new file mode 100644 index 0000000000..0baced66e2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md @@ -0,0 +1,156 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ExoPhishSimOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ExoPhishSimOverrideRule cmdlet to view third-party phishing simulation override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ExoPhishSimOverrideRule [[-Identity] ] + [-Confirm] + [-DomainController ] + [-Policy ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoPhishSimOverrideRule +``` + +This example returns detailed information about the phishing simulation override (there should be only one). + +### Example 2 +```powershell +Get-ExoPhishSimOverrideRule | Format-Table Name,Mode +``` + +This example identifies the valid rule (one) and any invalid rules. + +Although the previous command should return only one rule, a rule that's pending deletion might also be included in the results. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +The name of the rule uses the following syntax: `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +The Policy parameter filters the results by phishing simulator override policy. You can use any value that uniquely identifies the policy. For example: + +- Name +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md new file mode 100644 index 0000000000..4f8ca933c6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md @@ -0,0 +1,156 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ExoSecOpsOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ExoSecOpsOverrideRule cmdlet to view SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ExoSecOpsOverrideRule [[-Identity] ] + [-Confirm] + [-DomainController ] + [-Policy ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoSecOpsOverrideRule +``` + +This example returns detailed information about the SecOps mailbox override rule (there should be only one). + +### Example 2 +```powershell +Get-ExoSecOpsOverrideRule | Format-Table Name,Mode +``` + +This example identifies the valid rule (one) and any invalid rules. + +Although the previous command should return only one rule, a rule that's pending deletion might also be included in the results. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +The name of the rule uses the following syntax: `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +The Policy parameter filters the results by SecOps mailbox override policy. You can use any value that uniquely identifies the policy. For example: + +- Name +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ExternalInOutlook.md b/exchange/exchange-ps/exchange/Get-ExternalInOutlook.md new file mode 100644 index 0000000000..451de0b213 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ExternalInOutlook.md @@ -0,0 +1,71 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ExternalInOutlook + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ExternalInOutlook cmdlet to view the configuration of external sender identification that's available in Outlook, Outlook for Mac, Outlook on the web, and Outlook for iOS and Android. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ExternalInOutlook [[-Identity] ] [] +``` + +## DESCRIPTION +The important properties that are returned in the output of this cmdlet are: + +- Enabled: True means the feature is enabled; False means the feature is disabled. +- AllowList: The list of exceptions. Messages received from the specified senders or senders in the specified domains don't receive the External icon in the area of subject line. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExternalInOutlook +``` + +This example returns the settings of the external sender identification feature for the organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-FailedContentIndexDocuments.md b/exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md similarity index 90% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-FailedContentIndexDocuments.md rename to exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md index e0952d9f8f..14df25198f 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-FailedContentIndexDocuments.md +++ b/exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/get-failedcontentindexdocuments +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-FailedContentIndexDocuments ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in Exchange Server 2016 or earlier. Use the Get-FailedContentIndexDocuments cmdlet to retrieve a list of documents for a mailbox, mailbox database, or Mailbox server that couldn't be indexed by Exchange Search. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,7 +31,8 @@ Get-FailedContentIndexDocuments [-Identity] [-FailureMode ] [-ResultSize ] [-StartDate ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Database @@ -45,7 +45,8 @@ Get-FailedContentIndexDocuments -MailboxDatabase [-FailureMode ] [-ResultSize ] [-StartDate ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Server @@ -58,7 +59,8 @@ Get-FailedContentIndexDocuments -Server [-FailureMode ] [-ResultSize ] [-StartDate ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -68,7 +70,7 @@ After a new filter is installed, only new messages with attachments of the type The cmdlet output provides details about items in a mailbox that couldn't be indexed, including an error code and the reason for failure. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,7 +86,7 @@ This example retrieves a list of items that couldn't be indexed by Exchange Sear Get-FailedContentIndexDocuments -MailboxDatabase "Mailbox Database MDB2" ``` -This example retrieves a list of items that couldn't be indexed by Exchange Search from the mailbox database Mailbox Database MDB2. +This example retrieves a list of items that couldn't be indexed by Exchange Search from the mailbox database named Mailbox Database MDB2. ## PARAMETERS @@ -92,23 +94,14 @@ This example retrieves a list of items that couldn't be indexed by Exchange Sear The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -128,16 +121,14 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID ```yaml Type: DatabaseIdParameter Parameter Sets: Database Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -150,16 +141,14 @@ Accept wildcard characters: False The Server parameter specifies a Mailbox server. You can use the following values: - Name - - GUID - - DN ```yaml Type: ServerIdParameter Parameter Sets: Server Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -171,8 +160,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -195,7 +183,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -205,7 +193,9 @@ Accept wildcard characters: False ``` ### -Archive -The Archive switch restricts the scope of the cmdlet to the user's archive. When using the Archive switch, you must also specify the Identity parameter. +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. ```yaml Type: SwitchParameter @@ -223,7 +213,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". ```yaml Type: DateTime @@ -258,9 +248,7 @@ Accept wildcard characters: False 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. - - Permanent: Returns items that couldn't be indexed due to a permanent error. Exchange Search does not attempt to index these items again. - - All: Returns items that couldn't be indexed regardless of nature of failure. ```yaml @@ -295,7 +283,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: DateTime @@ -331,12 +319,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-FeatureConfiguration.md b/exchange/exchange-ps/exchange/Get-FeatureConfiguration.md new file mode 100644 index 0000000000..87063ff596 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FeatureConfiguration.md @@ -0,0 +1,133 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-featureconfiguration +applicable: Security & Compliance +title: Get-FeatureConfiguration +schema: 2.0.0 +--- + +# Get-FeatureConfiguration + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +> [!NOTE] +> This cmdlet is currently available in Public Preview, isn't available in all organizations, and is subject to change. + +Use the Get-FeatureConfiguration cmdlet to view Microsoft Purview feature configurations within your organization, including: + +- Collection policies. +- Advanced label based protection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FeatureConfiguration [[-Identity] ] [-FeatureScenario] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FeatureConfiguration -FeatureScenario KnowYourData | Format-Table Name,Mode +``` + +This example returns a summary list of all collection policies in the organization. + +### Example 2 +```powershell +Get-FeatureConfiguration -FeatureScenario KnowYourData -Identity "Engineering Group" +``` + +This example returns detailed information about the specified collection policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -FeatureScenario +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 + +```yaml +Type: PolicyScenario +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederatedDomainProof.md b/exchange/exchange-ps/exchange/Get-FederatedDomainProof.md similarity index 89% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederatedDomainProof.md rename to exchange/exchange-ps/exchange/Get-FederatedDomainProof.md index 0ffd5ffbbc..498c943b79 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederatedDomainProof.md +++ b/exchange/exchange-ps/exchange/Get-FederatedDomainProof.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-federateddomainproof +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-FederatedDomainProof @@ -17,19 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Get-FederatedDomainProof cmdlet to generate a cryptographically secure string for the domain used for federated sharing in your Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-FederatedDomainProof -DomainName [-DomainController ] [-Thumbprint ] +Get-FederatedDomainProof -DomainName + [-DomainController ] + [-Thumbprint ] [] ``` ## DESCRIPTION The Get-FederatedDomainProof cmdlet generates a cryptographically secure string for the domain used for federated sharing. The resulting string is used to manually configure a text (TXT) record in the Domain Name System (DNS) zone for the domain used by the administrator when running the cmdlet. A TXT record needs to be added to DNS for all accepted domains used for federated sharing. If the thumbprint of a certificate isn't provided, the task generates strings for all the certificates currently configured for the federation trust. Upon initial configuration of federated sharing, the proof string generated for the current certificate needs to be put into the TXT record for the federated domain in DNS. We recommend you update the TXT records whenever a new certificate is configured for the federation trust. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -102,12 +103,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md similarity index 80% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederatedOrganizationIdentifier.md rename to exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md index f19183dcaa..141f7f644a 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-federatedorganizationidentifier -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-FederatedOrganizationIdentifier @@ -17,19 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-FederatedOrganizationIdentifier cmdlet to retrieve the Exchange organization's federated organization identifier and related details, such as federated domains, organization contact and status. -For more information, see [Federation](https://docs.microsoft.com/exchange/federation-exchange-2013-help). +For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-FederatedOrganizationIdentifier [[-Identity] ] [-DomainController ] - [-IncludeExtendedDomainInfo] [] +Get-FederatedOrganizationIdentifier [[-Identity] ] + [-DomainController ] + [-IncludeExtendedDomainInfo] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,48 +50,50 @@ This example retrieves the Exchange organization's federated organization identi ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the organization ID. ```yaml -Type: Fqdn +Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the organization ID. +### -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. ```yaml -Type: OrganizationIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -IncludeExtendedDomainInfo -The IncludeExtendedDomainInfo switch specifies that the command query Microsoft Federation Gateway for the status of each accepted domain that's federated. The status is returned with each domain in the Domains property. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -104,12 +107,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederationInformation.md b/exchange/exchange-ps/exchange/Get-FederationInformation.md similarity index 80% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederationInformation.md rename to exchange/exchange-ps/exchange/Get-FederationInformation.md index 58fffc8cd7..53be62c5c2 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederationInformation.md +++ b/exchange/exchange-ps/exchange/Get-FederationInformation.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-federationinformation -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-FederationInformation @@ -17,13 +16,16 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-FederationInformation cmdlet to get federation information, including federated domain names and target URLs, from an external Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-FederationInformation -DomainName [-BypassAdditionalDomainValidation] [-Force] - [-TrustedHostnames ] [] +Get-FederationInformation -DomainName + [-BypassAdditionalDomainValidation] + [-Force] + [-TrustedHostnames ] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ The Get-FederationInformation cmdlet retrieves federation information from the d The domain specified should have federation enabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +53,7 @@ The DomainName parameter specifies the domain name for which federation informat Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -69,7 +71,7 @@ We recommend that you only use this switch to retrieve federation information in Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -79,7 +81,7 @@ Accept wildcard characters: False ``` ### -Force -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. +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. @@ -87,7 +89,7 @@ A confirmation prompt warns you if the host name in the Autodiscover endpoint of Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -103,7 +105,7 @@ The TrustedHostnames parameter specifies the fully qualified domain name (FQDN) Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -117,12 +119,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederationTrust.md b/exchange/exchange-ps/exchange/Get-FederationTrust.md similarity index 82% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederationTrust.md rename to exchange/exchange-ps/exchange/Get-FederationTrust.md index 2f49768a63..98175c1a29 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-FederationTrust.md +++ b/exchange/exchange-ps/exchange/Get-FederationTrust.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-federationtrust -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-FederationTrust @@ -17,16 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-FederationTrust cmdlet to view the federation trust configured for the Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-FederationTrust [[-Identity] ] [-DomainController ] [] +Get-FederationTrust [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -39,37 +40,37 @@ This example retrieves properties of the federation trust configured for the Exc ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies a federation trust ID. If not specified, the cmdlet returns all federation trusts configured for the Exchange organization. ```yaml -Type: Fqdn +Type: FederationTrustIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies a federation trust ID. If not specified, the cmdlet returns all federation trusts configured for the Exchange organization. +### -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. ```yaml -Type: FederationTrustIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -78,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md new file mode 100644 index 0000000000..023b70021a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md @@ -0,0 +1,74 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertyauthority +applicable: Security & Compliance +title: Get-FilePlanPropertyAuthority +schema: 2.0.0 +--- + +# Get-FilePlanPropertyAuthority + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-FilePlanPropertyAuthority cmdlet to view file plan property authorities. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FilePlanPropertyAuthority [[-Identity] ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FilePlanPropertyAuthority | Format-Table Name,Workload,Policy +``` + +This example returns a summary list of all file plan property authorities. + +### Example 2 +```powershell +Get-FilePlanPropertyAuthority -Identity "Contoso Authority" +``` + +This example returns detailed information about the custom file plan property authority named Contoso Authority. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md new file mode 100644 index 0000000000..c7b0bab4ef --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md @@ -0,0 +1,74 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertycategory +applicable: Security & Compliance +title: Get-FilePlanPropertyCategory +schema: 2.0.0 +--- + +# Get-FilePlanPropertyCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Fet-FilePlanPropertyCategory cmdlet to view file plan property categories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FilePlanPropertyCategory [[-Identity] ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FilePlanPropertyCategory | Format-Table Name,Workload,Policy +``` + +This example returns a summary list of all file plan property authorities. + +### Example 2 +```powershell +Get-FilePlanPropertyCategory -Identity "Contoso Category" +``` + +This example returns detailed information about the custom file plan property category named Contoso Category. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md new file mode 100644 index 0000000000..9080e6137a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md @@ -0,0 +1,74 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertycitation +applicable: Security & Compliance +title: Get-FilePlanPropertyCitation +schema: 2.0.0 +--- + +# Get-FilePlanPropertyCitation + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-FilePlanPropertyCitation cmdlet to view file plan property citations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FilePlanPropertyCitation [[-Identity] ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FilePlanPropertyCitation | Format-Table Name,Workload,Policy +``` + +This example returns a summary list of all file plan property authorities. + +### Example 2 +```powershell +Get-FilePlanPropertyCitation -Identity "Contoso Citation" +``` + +This example returns detailed information about the custom file plan property citation named Contoso Citation. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md new file mode 100644 index 0000000000..58fc2c7f5e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md @@ -0,0 +1,74 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertydepartment +applicable: Security & Compliance +title: Get-FilePlanPropertyDepartment +schema: 2.0.0 +--- + +# Get-FilePlanPropertyDepartment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-FilePlanPropertyDepartment cmdlet to view file plan property departments. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FilePlanPropertyDepartment [[-Identity] ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FilePlanPropertyDepartment | Format-Table Name,Workload,Policy +``` + +This example returns a summary list of all file plan property departments. + +### Example 2 +```powershell +Get-FilePlanPropertyDepartment -Identity "Contoso HR" +``` + +This example returns detailed information about the custom file plan property department named Contoso HR. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md new file mode 100644 index 0000000000..c1ec2f310a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md @@ -0,0 +1,74 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertyreferenceid +applicable: Security & Compliance +title: Get-FilePlanPropertyReferenceId +schema: 2.0.0 +--- + +# Get-FilePlanPropertyReferenceId + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-FilePlanPropertyReferenceId cmdlet to view file plan property reference IDs. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FilePlanPropertyReferenceId [[-Identity] ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FilePlanPropertyReferenceId | Format-Table Name,Workload,Policy +``` + +This example returns a summary list of all file plan property reference IDs. + +### Example 2 +```powershell +Get-FilePlanPropertyReferenceId -Identity "Contoso-0001" +``` + +This example returns detailed information about the custom file plan property reference ID named Contoso-0001. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md new file mode 100644 index 0000000000..f2e64f89a2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md @@ -0,0 +1,63 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertystructure +applicable: Security & Compliance +title: Get-FilePlanPropertyStructure +schema: 2.0.0 +--- + +# Get-FilePlanPropertyStructure + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-FilePlanPropertyStructure cmdlet to the view file plan property structure in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FilePlanPropertyStructure [-IncludeAdditionalInfo] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FilePlanPropertyStructure -IncludeAdditionalInfo +``` + +This example returns the file plan property structure. + +## PARAMETERS + +### -IncludeAdditionalInfo +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md new file mode 100644 index 0000000000..ed2bc3113e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md @@ -0,0 +1,74 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertysubcategory +applicable: Security & Compliance +title: Get-FilePlanPropertySubCategory +schema: 2.0.0 +--- + +# Get-FilePlanPropertySubCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-FilePlanPropertySubCategory cmdlet to view file plan property subcategories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FilePlanPropertySubCategory [[-Identity] ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Get-FilePlanPropertySubCategory | Format-Table Name,Workload,ParentCategory,Policy +``` + +This example returns a summary list of all file plan property subcategories. + +### Example 2 +```powershell +Get-FilePlanPropertySubCategory -Identity "US Tax" +``` + +This example returns detailed information about the custom file plan property subcategory named US Tax. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-FocusedInbox.md b/exchange/exchange-ps/exchange/Get-FocusedInbox.md new file mode 100644 index 0000000000..c7b5967c67 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-FocusedInbox.md @@ -0,0 +1,97 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-FocusedInbox + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-FocusedInbox cmdlet to view the Focused Inbox configuration for mailboxes in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-FocusedInbox -Identity + [-UseCustomRouting] + [] +``` + +## DESCRIPTION +Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-FocusedInbox -Identity julia@contoso.com +``` + +This example returns the Focused Inbox configuration for the mailbox of julia@contoso.com. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-ForeignConnector.md b/exchange/exchange-ps/exchange/Get-ForeignConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Get-ForeignConnector.md rename to exchange/exchange-ps/exchange/Get-ForeignConnector.md index 3dfe368e3d..1d19d0d26f 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-ForeignConnector.md +++ b/exchange/exchange-ps/exchange/Get-ForeignConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-foreignconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ForeignConnector @@ -17,17 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ForeignConnector cmdlet to view the configuration information for a Foreign connector in the Transport service of a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ForeignConnector [[-Identity] ] [-DomainController ] +Get-ForeignConnector [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,43 +47,41 @@ This example displays detailed configuration information for the Foreign connect ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: -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. +- GUID +- Connector name +- ServerName\\ConnectorName ```yaml -Type: Fqdn +Type: ForeignConnectorIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Connector name +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -- ServerName\\ConnectorName +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. ```yaml -Type: ForeignConnectorIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -92,12 +90,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-FrontendTransportService.md b/exchange/exchange-ps/exchange/Get-FrontendTransportService.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Get-FrontendTransportService.md rename to exchange/exchange-ps/exchange/Get-FrontendTransportService.md index 2f8b6e63d7..e768cd1838 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-FrontendTransportService.md +++ b/exchange/exchange-ps/exchange/Get-FrontendTransportService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-frontendtransportservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-FrontendTransportService @@ -17,19 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-FrontEndTransportService cmdlet to view the configuration of the Front End Transport service on Exchange 2013 or later servers that have the Client Access server role installed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-FrontendTransportService [[-Identity] ] [-DomainController ] +Get-FrontendTransportService [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION The Front End Transport service acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,33 +49,14 @@ This example retrieves the detailed configuration information for the Front End ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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: - Name (for example, Exchange01) - - Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com) - - Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01) - - GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942) ```yaml @@ -91,17 +72,33 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-GlobalAddressList.md b/exchange/exchange-ps/exchange/Get-GlobalAddressList.md similarity index 87% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-GlobalAddressList.md rename to exchange/exchange-ps/exchange/Get-GlobalAddressList.md index 90fbfccb2c..0a3a6daa60 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-GlobalAddressList.md +++ b/exchange/exchange-ps/exchange/Get-GlobalAddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/get-globaladdresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-GlobalAddressList @@ -17,28 +16,30 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-GlobalAddressList cmdlet to view a global address list (GAL) or a set of GALs. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### DefaultOnly ``` Get-GlobalAddressList [-DefaultOnly] - [-DomainController ] [] + [-DomainController ] + [] ``` ### Identity ``` Get-GlobalAddressList [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION The Get-GlobalAddressList cmdlet is mainly used to populate the GAL property pages in the Exchange admin center. This command doesn't provide a filtering capability. If filtering is required, you should use a WHERE clause with the command. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,6 +59,26 @@ This example returns detailed information about the GAL named GAL\_AgencyB. ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DefaultOnly The DefaultOnly switch filters the results so only the default GAL is returned. You don't need to use a value with this switch. @@ -92,39 +113,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-GlobalMonitoringOverride.md b/exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md similarity index 85% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-GlobalMonitoringOverride.md rename to exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md index 699e153614..24e4681b00 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-globalmonitoringoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-GlobalMonitoringOverride @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-GlobalMonitoringOverride cmdlet to view the overrides of the thresholds and parameters of the managed availability probes, monitors and responders that are configured for all Exchange 2013 or later servers in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-GlobalMonitoringOverride [-DomainController ] [] +Get-GlobalMonitoringOverride [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,12 +69,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-Group.md b/exchange/exchange-ps/exchange/Get-Group.md similarity index 75% rename from exchange/exchange-ps/exchange/users-and-groups/Get-Group.md rename to exchange/exchange-ps/exchange/Get-Group.md index a8d21b9f90..b940181519 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-Group.md +++ b/exchange/exchange-ps/exchange/Get-Group.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-group -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" --- # Get-Group @@ -15,9 +14,9 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the Get-Group cmdlet to view existing group objects in your organization. This cmdlet returns security groups, mail-enabled security groups, distribution groups, and role groups. +Use the Get-Group cmdlet to view existing group objects in your organization. In all environments, this cmdlet returns mail-enabled security groups, distribution groups, role groups, and room lists. For details about other supported group types in on-premises Exchange environments, see the RecipientTypeDetails parameter description. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,7 +31,8 @@ Get-Group [-Anr ] [-ReadFromDomainController] [-RecipientTypeDetails ] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ### Identity @@ -46,13 +46,14 @@ Get-Group [[-Identity] ] [-ReadFromDomainController] [-RecipientTypeDetails ] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ## DESCRIPTION The Get-Group cmdlet returns no mail-related properties for distribution groups or mail-enabled security groups, and no role group-related properties for role groups. To view the object-specific properties for a group, you need to use the corresponding cmdlet based on the object type (for example, Get-DistributionGroup or Get-RoleGroup). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,24 +80,41 @@ This example uses the Anr parameter to return all groups that begin with "Mar". ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml Type: String Parameter Sets: AnrSet Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -106,15 +124,17 @@ Accept wildcard characters: False ``` ### -Credential +This parameter is available only in on-premises Exchange. + The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -144,25 +164,22 @@ Accept wildcard characters: False ``` ### -Filter -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. +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'"`. -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -171,39 +188,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: GroupIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -223,18 +215,15 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -246,7 +235,9 @@ Accept wildcard characters: False ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -267,12 +258,12 @@ Accept wildcard characters: False The RecipientTypeDetails parameter filters the results by the specified group subtype. Valid values are: - MailNonUniversalGroup - - MailUniversalDistributionGroup - - MailUniversalSecurityGroup - +- NonUniversalGroup (on-premises Exchange Server only) - RoomList +- UniversalDistributionGroup (on-premises Exchange Server only) +- UniversalSecurityGroup (on-premises Exchange Server only) You can specify multiple values separated by commas. @@ -280,7 +271,7 @@ You can specify multiple values separated by commas. Type: RecipientTypeDetails[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -296,7 +287,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -308,19 +299,18 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -334,12 +324,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-HealthReport.md b/exchange/exchange-ps/exchange/Get-HealthReport.md similarity index 92% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-HealthReport.md rename to exchange/exchange-ps/exchange/Get-HealthReport.md index fe46d37dbc..fb4ff840c9 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-HealthReport.md +++ b/exchange/exchange-ps/exchange/Get-HealthReport.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-healthreport +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-HealthReport @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-HealthReport cmdlet to return health information for the Exchange server that you specify. You can use the health values to determine the state of the server. The cmdlet also returns an alert value that provides the specific state of your server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -35,18 +34,13 @@ Get-HealthReport [-Identity] The following list contains the health values that are returned: - Online - - Partially Online - - Offline - - Sidelined - - Functional - - Unavailable -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,11 +57,8 @@ This example retrieves health information for the server named Mailbox01. 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -168,12 +159,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/reporting/Get-HistoricalSearch.md b/exchange/exchange-ps/exchange/Get-HistoricalSearch.md similarity index 78% rename from exchange/exchange-ps/exchange/reporting/Get-HistoricalSearch.md rename to exchange/exchange-ps/exchange/Get-HistoricalSearch.md index de01837b2f..9aa5b5f171 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-HistoricalSearch.md +++ b/exchange/exchange-ps/exchange/Get-HistoricalSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-historicalsearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-HistoricalSearch @@ -17,21 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Get-HistoricalSearch cmdlet to view information about historical searches that have been performed within the last ten days. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-HistoricalSearch [-JobId ] [] +Get-HistoricalSearch [-JobId ] + [] ``` ## DESCRIPTION A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are less than 90 days old. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,12 +69,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md new file mode 100644 index 0000000000..ec353acb7a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md @@ -0,0 +1,104 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-HoldCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-HoldCompliancePolicy to view existing preservation policies in the Microsoft Purview compliance portal. + +**Note**: The Get-HoldCompliancePolicy cmdlet has been replaced by the Get-RetentionCompliancePolicy cmdlet. If you have scripts that use Get-HoldCompliancePolicy, update them to use Get-RetentionCompliancePolicy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-HoldCompliancePolicy [[-Identity] ] + [-DistributionDetail] + [] +``` + +## DESCRIPTION +This list describes the properties displayed by default. + +- Name: The unique name of the policy. +- Workload: Where the policy is applied. For example, SharePoint or Exchange. +- Enabled: The value True means the policy is enabled. +- Mode: The current operating mode of the policy. The possible values are Test (the content is tested, but no rules are enforced), AuditAndNotify (when content matches the conditions specified by the policy, the rule is not enforced, but notification emails are sent) or Enforce (all aspects of the policy are enabled and enforced). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-HoldCompliancePolicy +``` + +This example displays summary information for all preservation policies in your organization. + +### Example 2 +```powershell +Get-HoldCompliancePolicy -Identity "Regulation 123 Compliance" | Format-List +``` + +This example displays detailed information for the policy named "Regulation 123 Compliance". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DistributionDetail +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-HoldComplianceRule.md b/exchange/exchange-ps/exchange/Get-HoldComplianceRule.md new file mode 100644 index 0000000000..898c6c476a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-HoldComplianceRule.md @@ -0,0 +1,110 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-HoldComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-HoldComplianceRule to view preservation rules in the Microsoft Purview compliance portal. + +**Note**: The Get-HoldComplianceRule cmdlet has been replaced by the Get-RetentionComplianceRule cmdlet. If you have scripts that use Get-HoldComplianceRule, update them to use Get-RetentionComplianceRule. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-HoldComplianceRule [[-Identity] ] + [-Policy ] + [] +``` + +## DESCRIPTION +This list describes the properties that are displayed by default in the summary information. + +- Name: The unique name of the rule. +- Disabled: The enabled or disabled status of the rule. +- Mode: The current operating mode of the rule (for example, Enforce). +- Comment: An administrative comment. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-HoldComplianceRule +``` + +This example displays summary information for all preservation rules in your organization. + +### Example 2 +```powershell +Get-HoldComplianceRule -Identity "30DayRule" | Format-List +``` + +This example displays detailed information for the preservation rule named "30 Day Rule". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the preservation rule you want to view. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +You can use this parameter with the Identity parameter in the same command. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md similarity index 79% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedConnectionFilterPolicy.md rename to exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md index bab2ee2381..95c62d1b40 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-hostedconnectionfilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-HostedConnectionFilterPolicy @@ -17,19 +16,17 @@ This cmdlet is available only in the cloud-based service. Use the Get-HostedConnectionFilterPolicy cmdlet to view the settings of connection filter policies in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-HostedConnectionFilterPolicy [[-Identity] ] [] +Get-HostedConnectionFilterPolicy [[-Identity] ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,9 +50,7 @@ This example returns detailed information about the connection filter policy nam 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 - - Distinguished name (DN) - - GUID Typically, you only have one connection filter policy: the default policy named Default. @@ -78,12 +73,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md similarity index 75% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterPolicy.md rename to exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md index 5c4d59c267..855377d33a 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-hostedcontentfilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-HostedContentFilterPolicy @@ -17,19 +16,17 @@ This cmdlet is available only in the cloud-based service. Use the Get-HostedContentFilterPolicy cmdlet to view the settings of spam filter policies (content filter policies) in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-HostedContentFilterPolicy [[-Identity] ] [] +Get-HostedContentFilterPolicy [[-Identity] ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,15 +44,22 @@ Get-HostedContentFilterPolicy Default | Format-List This example retrieves details about the spam filter policy named Default. +### Example 3 +```powershell +$x = Get-HostedContentFilterPolicy + +$x | foreach {write-host ("`r`n"*3)$_.Name,`r`n,("="*79),`r`n,"Allowed Senders"`r`n,("-"*79),`r`n,$_.AllowedSenders,("`r`n"*2),"Allowed Sender Domains",`r`n,("-"*79),`r`n,$_.AllowedSenderDomains,("`r`n"*2),"Blocked Senders"`r`n,("-"*79),`r`n,$_.BlockedSenders,("`r`n"*2),"Blocked Sender Domains",`r`n,("-"*79),`r`n,$_.BlockedSenderDomains} +``` + +This example shows the allowed and blocked senders and domains in all spam filter policies. + ## PARAMETERS ### -Identity 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 - - Distinguished name (DN) - - GUID ```yaml @@ -76,12 +80,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md new file mode 100644 index 0000000000..0531374eab --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md @@ -0,0 +1,121 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-HostedContentFilterRule + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Get-HostedContentFilterRule cmdlet to view spam filter rules (content filter rules) in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-HostedContentFilterRule [[-Identity] ] + [-DomainController ] + [-State ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-HostedContentFilterRule +``` + +This example shows a summary list of all the spam filter rules in your cloud-based organization. + +### Example 2 +```powershell +Get-HostedContentFilterRule "Contoso Recipients" | Format-List +``` + +This example retrieves details about the spam filter rule named Contoso Recipients. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The State parameter filters the results by the state of the rule. Valid values are: + +- Enabled: The command returns only enabled rules. +- Disabled: The command returns only disabled rules. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/antispam-antimalware/Get-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md similarity index 78% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterPolicy.md rename to exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md index 797c86da40..1e40b52a4d 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-hostedoutboundspamfilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-HostedOutboundSpamFilterPolicy @@ -17,19 +16,17 @@ This cmdlet is available only in the cloud-based service. Use the Get-HostedOutboundSpamFilterPolicy cmdlet to view outbound spam filter policies in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-HostedOutboundSpamFilterPolicy [-Identity] [] +Get-HostedOutboundSpamFilterPolicy [-Identity] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,9 +50,7 @@ This example returns detailed information about the outbound spam filter policy 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 - - Distinguished name (DN) - - GUID ```yaml @@ -76,12 +71,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md similarity index 78% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md index 1c7f47a6e9..0a620cec54 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-hostedoutboundspamfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-HostedOutboundSpamFilterRule @@ -17,19 +16,18 @@ This cmdlet is available only in the cloud-based service. Use the Get-HostedOutboundSpamFilterRule cmdlet to view outbound spam filter rules in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-HostedOutboundSpamFilterRule [[-Identity] ] [-State ] [] +Get-HostedOutboundSpamFilterRule [[-Identity] ] + [-State ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,9 +51,7 @@ This example returns detailed information for the outbound spam filter rule name 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 - - Distinguished name (DN) - - GUID ```yaml @@ -75,7 +71,6 @@ Accept wildcard characters: False The State parameter filters the results by enabled or disabled rules. Valid values are: - Enabled: Only enabled rules are returned. - - Disabled: Only disabled rules are returned. ```yaml @@ -96,12 +91,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridConfiguration.md b/exchange/exchange-ps/exchange/Get-HybridConfiguration.md similarity index 83% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridConfiguration.md rename to exchange/exchange-ps/exchange/Get-HybridConfiguration.md index af763909c3..426766c54c 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-HybridConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-hybridconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-HybridConfiguration @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-HybridConfiguration cmdlet to view the hybrid configuration for the Microsoft Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-HybridConfiguration [-DomainController ] [] +Get-HybridConfiguration [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,12 +60,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md b/exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md new file mode 100644 index 0000000000..4f793be1a3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md @@ -0,0 +1,56 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-HybridMailflowDatacenterIPs + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +This cmdlet has been deprecated and is no longer used. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-HybridMailflowDatacenterIPs [] +``` + +## DESCRIPTION +This cmdlet has been deprecated and is no longer used. + +## EXAMPLES + +### Example 1 +```powershell +Get-HybridMailflowDatacenterIPs +``` + +This cmdlet has been deprecated and is no longer used. + +## 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/antispam-antimalware/Get-IPAllowListConfig.md b/exchange/exchange-ps/exchange/Get-IPAllowListConfig.md similarity index 86% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListConfig.md rename to exchange/exchange-ps/exchange/Get-IPAllowListConfig.md index 4699604689..0da96065e8 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListConfig.md +++ b/exchange/exchange-ps/exchange/Get-IPAllowListConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipallowlistconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPAllowListConfig @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPAllowListConfig cmdlet to view the configuration information for the IP Allow list that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IPAllowListConfig [-DomainController ] [] +Get-IPAllowListConfig [-DomainController ] + [] ``` ## DESCRIPTION @@ -64,12 +64,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListEntry.md b/exchange/exchange-ps/exchange/Get-IPAllowListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListEntry.md rename to exchange/exchange-ps/exchange/Get-IPAllowListEntry.md index d13312dbf8..7221b9e90b 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListEntry.md +++ b/exchange/exchange-ps/exchange/Get-IPAllowListEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipallowlistentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPAllowListEntry @@ -17,7 +16,7 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPAllowListEntry cmdlet to view the IP address entries in the IP Allow list that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,14 +24,16 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-IPAllowListEntry -IPAddress [-ResultSize ] - [-Server ] [] + [-Server ] + [] ``` ### Identity ``` Get-IPAllowListEntry [[-Identity] ] [-ResultSize ] - [-Server ] [] + [-Server ] + [] ``` ## DESCRIPTION @@ -56,35 +57,35 @@ This example returns an IP Allow list entry in which the specified IP address is ## PARAMETERS -### -IPAddress -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. +### -Identity +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: IPAddress -Parameter Sets: IPAddress +Type: IPListEntryIdentity +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -Required: True -Position: Named +Required: False +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -IPAddress +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: IPListEntryIdentity -Parameter Sets: Identity +Type: IPAddress +Parameter Sets: IPAddress Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -Required: False -Position: 1 +Required: True +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -108,11 +109,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -137,12 +135,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListProvider.md b/exchange/exchange-ps/exchange/Get-IPAllowListProvider.md similarity index 89% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListProvider.md rename to exchange/exchange-ps/exchange/Get-IPAllowListProvider.md index 4303f21919..1d17905936 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListProvider.md +++ b/exchange/exchange-ps/exchange/Get-IPAllowListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipallowlistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPAllowListProvider @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPAllowListProvider cmdlet to view IP Allow list providers that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IPAllowListProvider [[-Identity] ] [-DomainController ] +Get-IPAllowListProvider [[-Identity] ] + [-DomainController ] [] ``` @@ -47,43 +47,41 @@ This example returns detailed information for the IP Allow list provider named C ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: -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. +- Name +- Distinguished name (DN) +- GUID ```yaml -Type: Fqdn +Type: IPAllowListProviderIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -- GUID +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. ```yaml -Type: IPAllowListProviderIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -92,12 +90,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListProvidersConfig.md b/exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md similarity index 86% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListProvidersConfig.md rename to exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md index 3457a6dc98..b56f559df4 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPAllowListProvidersConfig.md +++ b/exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipallowlistprovidersconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPAllowListProvidersConfig @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPAllowListProvidersConfig cmdlet to view the settings that affect all IP Allow list providers that are configured on an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IPAllowListProvidersConfig [-DomainController ] [] +Get-IPAllowListProvidersConfig [-DomainController ] + [] ``` ## DESCRIPTION @@ -64,12 +64,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListConfig.md b/exchange/exchange-ps/exchange/Get-IPBlockListConfig.md similarity index 86% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListConfig.md rename to exchange/exchange-ps/exchange/Get-IPBlockListConfig.md index 0edb1d64a0..517988a7ae 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListConfig.md +++ b/exchange/exchange-ps/exchange/Get-IPBlockListConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipblocklistconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPBlockListConfig @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPBlockListConfig cmdlet to view the IP Block list configuration information that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IPBlockListConfig [-DomainController ] [] +Get-IPBlockListConfig [-DomainController ] + [] ``` ## DESCRIPTION @@ -64,12 +64,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListEntry.md b/exchange/exchange-ps/exchange/Get-IPBlockListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListEntry.md rename to exchange/exchange-ps/exchange/Get-IPBlockListEntry.md index 6791eea9df..d6a1d41ce8 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListEntry.md +++ b/exchange/exchange-ps/exchange/Get-IPBlockListEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipblocklistentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPBlockListEntry @@ -17,7 +16,7 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPBlockListEntry cmdlet to view the IP Block list entries that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,14 +24,16 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-IPBlockListEntry [[-Identity] ] [-ResultSize ] - [-Server ] [] + [-Server ] + [] ``` ### IPAddress ``` Get-IPBlockListEntry -IPAddress [-ResultSize ] - [-Server ] [] + [-Server ] + [] ``` ## DESCRIPTION @@ -108,11 +109,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -137,12 +135,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListProvider.md b/exchange/exchange-ps/exchange/Get-IPBlockListProvider.md similarity index 89% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListProvider.md rename to exchange/exchange-ps/exchange/Get-IPBlockListProvider.md index ef886bf128..f8849f592d 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListProvider.md +++ b/exchange/exchange-ps/exchange/Get-IPBlockListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipblocklistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPBlockListProvider @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPBlockListProvider cmdlet to view IP Block list providers that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IPBlockListProvider [[-Identity] ] [-DomainController ] +Get-IPBlockListProvider [[-Identity] ] + [-DomainController ] [] ``` @@ -47,43 +47,41 @@ This example returns detailed information for the existing IP Block list provide ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: -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. +- Name +- Distinguished name (DN) +- GUID ```yaml -Type: Fqdn +Type: IPBlockListProviderIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -- GUID +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. ```yaml -Type: IPBlockListProviderIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -92,12 +90,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListProvidersConfig.md b/exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md similarity index 86% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListProvidersConfig.md rename to exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md index b5534527cc..f7bcc606fa 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-IPBlockListProvidersConfig.md +++ b/exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-ipblocklistprovidersconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-IPBlockListProvidersConfig @@ -17,12 +16,13 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Get-IPBlockListProvidersConfig cmdlet to view the settings that affect all IP Block list providers that are configured on an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IPBlockListProvidersConfig [-DomainController ] [] +Get-IPBlockListProvidersConfig [-DomainController ] + [] ``` ## DESCRIPTION @@ -64,12 +64,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md b/exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md new file mode 100644 index 0000000000..e8d7109c9a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-IPv6StatusForAcceptedDomain + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-IPv6StatusForAcceptedDomain cmdlet to view the status of support for mail delivery to accepted domains in Exchange Online using IPv6. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-IPv6StatusForAcceptedDomain [[-Domain] ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Online organization to use with this cmdlet + +If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +> [!NOTE] +> +> - When you use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain cmdlets to update the IPv6 setting for an accepted domain, the updated status can take up to an hour to be visible using Get-IPv6StatusForAcceptedDomain due to caching. +> +> For example, Get-IPv6StatusForAcceptedDomain shows the status value Enabled for a domain. You run Disable-IPv6ForAcceptedDomain to disable IPv6 for the domain, you immediately run Get-IPv6StatusForAcceptedDomain to check the status of the domain, and the command erroneously returns the value Enabled. It might take up to an hour before Get-IPv6StatusForAcceptedDomain shows the correct value Disabled for the domain. +> +> - If you receive the following error when running Get-Ipv6StatusForAcceptedDomain: +> +> WARNING: DNS record has unexpected value... +> +> Explicitly enable or disable IPv6 using the Enable-Ipv6ForAcceptedDomain or Disable-Ipv6ForAcceptedDomain cmdlets. + +## EXAMPLES + +### Example 1 +```powershell +Get-IPv6StatusForAcceptedDomain -Domain contoso.com +``` + +This example returns the status of IPv6 support for mail sent to contoso.com. + +## PARAMETERS + +### -Domain +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-IRMConfiguration.md b/exchange/exchange-ps/exchange/Get-IRMConfiguration.md similarity index 84% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Get-IRMConfiguration.md rename to exchange/exchange-ps/exchange/Get-IRMConfiguration.md index 8ffce7bc12..377c44454f 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-IRMConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-IRMConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-irmconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-IRMConfiguration @@ -17,18 +16,19 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-IRMConfiguration cmdlet to view the Information Rights Management (IRM) configuration in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IRMConfiguration [-DomainController ] [] +Get-IRMConfiguration [-DomainController ] + [] ``` ## DESCRIPTION The Get-IRMConfiguration cmdlet provides details about the current IRM configuration, including whether individual IRM features are enabled or disabled and provides the URLs used for ServiceLocation, PublishingLocation and LicensingLocation. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -64,12 +64,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Get-ImapSettings.md b/exchange/exchange-ps/exchange/Get-ImapSettings.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access/Get-ImapSettings.md rename to exchange/exchange-ps/exchange/Get-ImapSettings.md index 522a6ed3db..78a0faa6d4 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-ImapSettings.md +++ b/exchange/exchange-ps/exchange/Get-ImapSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-imapsettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ImapSettings @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ImapSettings cmdlet to view the settings of the Microsoft Exchange IMAP4 service on Exchange servers. This is the client access (frontend) IMAP4 service that clients connect to. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ImapSettings [-DomainController ] [-Server ] [] +Get-ImapSettings [-DomainController ] + [-Server ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,11 +60,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -86,12 +84,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-InboundConnector.md b/exchange/exchange-ps/exchange/Get-InboundConnector.md similarity index 78% rename from exchange/exchange-ps/exchange/mail-flow/Get-InboundConnector.md rename to exchange/exchange-ps/exchange/Get-InboundConnector.md index 566daf3abc..2447b733ef 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-InboundConnector.md +++ b/exchange/exchange-ps/exchange/Get-InboundConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-inboundconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-InboundConnector @@ -17,21 +16,20 @@ This cmdlet is available only in the cloud-based service. Use the Get-InboundConnector cmdlet to view the settings for an Inbound connector in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-InboundConnector [[-Identity] ] [] +Get-InboundConnector [[-Identity] ] + [-ResultSize ] + [] ``` ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,17 +65,33 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-InboxRule.md b/exchange/exchange-ps/exchange/Get-InboxRule.md similarity index 78% rename from exchange/exchange-ps/exchange/mailboxes/Get-InboxRule.md rename to exchange/exchange-ps/exchange/Get-InboxRule.md index b52f924bc1..5ed6b13784 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-InboxRule.md +++ b/exchange/exchange-ps/exchange/Get-InboxRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-inboxrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-InboxRule @@ -17,26 +16,29 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-InboxRule cmdlet to view Inbox rule properties. Inbox rules are used to process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-InboxRule [[-Identity] ] + [-BypassScopeCheck] [-DescriptionTimeFormat ] [-DescriptionTimeZone ] [-DomainController ] - [-Mailbox ] [-IncludeHidden] - [-BypassScopeCheck] + [-Mailbox ] + [-ResultSize ] + [-SkipCount ] [-SweepRules] + [-UseCustomRouting] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). -**Note**: This cmdlet doesn't work for members of View-Only Organization Management role group in Exchange Online or the Global Reader role in Azure Active Directory. +**Note**: This cmdlet doesn't work for members of View-Only Organization Management role group in Exchange Online or the Global Reader role in Microsoft Entra ID. ## EXAMPLES @@ -49,17 +51,54 @@ This example retrieves all Inbox rules for the mailbox Joe@Contoso.com. ### Example 2 ```powershell -Get-InboxRule "ReceivedLastYear" -Mailbox joe@contoso.com -DescriptionTimeFormat "mm/dd/yyyy" -DescriptionTimeZone "Pacific Standard Time" +Get-InboxRule "ReceivedLastYear" -Mailbox joe@contoso.com -DescriptionTimeFormat "MM/dd/yyyy" -DescriptionTimeZone "Pacific Standard Time" ``` This example retrieves the Inbox rule ReceivedLastYear from the mailbox joe@contoso.com on which the ReceivedBeforeDate parameter was set when the rule was created. The DescriptionTimeFormat and DescriptionTimeZone parameters are used in this example to specify formatting of the time and the time zone used in the rule's Description property. ## PARAMETERS +### -Identity +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 +- RuleIdentity property (for example, 16752869479666417665). +- Exchange Online: `MailboxAlias\RuleIdentity` (for example, `rzaher\16752869479666417665`). +- On-premises Exchange: `MailboxCanonicalName\RuleIdentity` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BypassScopeCheck +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DescriptionTimeFormat 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. +MM/dd/yyyy, where MM is the 2-digit month, dd is the 2-digit day and yyyy is the 4-digit year. ```yaml Type: String @@ -114,27 +153,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- RuleIdentity property (for example, 16752869479666417665). - -- Exchange Online: `\` (for example, `rzaher\16752869479666417665`. - -- On-premises Exchange: `\` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). +### -IncludeHidden +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: InboxRuleIdParameter +Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -142,23 +173,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -174,16 +196,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -IncludeHidden -This parameter is available only in on-premises Exchange. +### -ResultSize +This parameter is available only in the cloud-based service. -The IncludeHidden switch specifies whether to include hidden Inbox rules in the results. You don't need to specify a value with this switch. +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: SwitchParameter +Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -192,14 +214,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -BypassScopeCheck -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. +### -SkipCount +This parameter is available only in the cloud-based service. + +{{ Fill SkipCount Description }} ```yaml -Type: SwitchParameter +Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -209,6 +233,8 @@ Accept wildcard characters: False ``` ### -SweepRules +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. Sweep rules run at regular intervals to help keep your Inbox clean. @@ -217,7 +243,25 @@ 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, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online Required: False Position: Named @@ -231,12 +275,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md b/exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md new file mode 100644 index 0000000000..4ba383b667 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md @@ -0,0 +1,104 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-InformationBarrierPoliciesApplicationStatus + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-InformationBarrierPoliciesApplicationStatus cmdlet to view the application status of information barrier policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default (Default) +``` +Get-InformationBarrierPoliciesApplicationStatus [-All] + [] +``` + +### Identity +``` +Get-InformationBarrierPoliciesApplicationStatus [[-Identity] ] + [-All] + [] +``` + +## DESCRIPTION + For more information, see [View status of information barrier policy application](https://learn.microsoft.com/purview/information-barriers-policies#view-status-of-user-accounts-segments-policies-or-policy-application). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-InformationBarrierPoliciesApplicationStatus +``` + +This example returns the most recent application of information barrier policies by the Start-InformationBarrierPoliciesApplication cmdlet. + +### Example 2 +```powershell +Get-InformationBarrierPoliciesApplicationStatus -All +``` + +This example returns all applications of information barrier policies by the Start-InformationBarrierPoliciesApplication cmdlet. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -All +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) diff --git a/exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md new file mode 100644 index 0000000000..32c2276297 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-InformationBarrierPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-InformationBarrierPolicy cmdlet to view information barrier policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### InformationBarrierDefault (Default) +``` +Get-InformationBarrierPolicy [-ExoPolicyId ] + [] +``` + +### Identity +``` +Get-InformationBarrierPolicy [[-Identity] ] + [-ExoPolicyId ] + [] +``` + +## DESCRIPTION +For more information, see [Information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-InformationBarrierPolicy | Format-Table Name,State,AssignedSegment,Segments* -Auto +``` + +This example displays a summary list of all information barrier policies. + +### Example 2 +```powershell +Get-InformationBarrierPolicy -Identity HR-Sales +``` + +This example displays detailed information for the information barrier policy named HR-Sales. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +You can't use this parameter with the ExOPolicyId parameter. + +```yaml +Type: PolicyIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -ExoPolicyId +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md b/exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md new file mode 100644 index 0000000000..862519808e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md @@ -0,0 +1,123 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-InformationBarrierRecipientStatus + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-InformationBarrierRecipientStatus cmdlet to return information about recipients and their relationship to information barrier policies. + +**Note**: This cmdlet doesn't work with information barriers in non-legacy mode. To determine your current mode, see [Check the IB mode for your organization](https://learn.microsoft.com/purview/information-barriers-multi-segment#check-the-ib-mode-for-your-organization). If you're in non-legacy mode, run the following command to get information about a single recipient: `Get-Recipient -Identity | Format-List Name,*segment*`. Similarly, to get the relationship information between two recipients, use the **Get-ExoInformationBarrierRelationship** cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-InformationBarrierRecipientStatus [-Identity] [[-Identity2] ] + [] +``` + +## DESCRIPTION +The following information is returned in the output of this cmdlet: + +- A warning message that indicates whether or not the recipient is included in an information barrier policy. +- If present, the GUID part in the ExOPolicyId property value identifies the information barrier policy that the recipient is included in. You can run the command `Get-InformationBarrierPolicy -ExOPolicyId ` to identify and view the details of the policy. +- Basic information about the recipient (display name, alias, and last name). +- Recipient properties that can be used in organization segments (Department, CustomAttributeN, etc.) and the current property values for the recipient. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-InformationBarrierRecipientStatus -Identity meganb +``` + +This example returns the information barrier policy information for the user meganb. + +### Example 2 +```powershell +Get-InformationBarrierRecipientStatus -Identity meganb -Identity2 alexw +``` + +This example returns the information barrier policy relationship for the users meganb and alexw. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Identity2 +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +When you include this parameter in a command, you get output for each recipient. + +You can only use this parameter with the Identity parameter; you can't use it by itself. + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes) + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md similarity index 86% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-IntraOrganizationConfiguration.md rename to exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md index d2c26dd3c9..3178fd949a 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-IntraOrganizationConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-intraorganizationconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-IntraOrganizationConfiguration @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-IntraOrganizationConfiguration cmdlet to view the component settings of a hybrid Exchange deployment. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,7 +30,7 @@ A hybrid Exchange deployment results in one logical organization made up of a nu Hybrid environments are enabled by Intra-Organization connectors. The connectors can be created and managed by cmdlets like New-IntraOrganizationConnector, but we strongly recommend that you use the Hybrid Configuration wizard when configuring a hybrid deployment with an Exchange Online organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,7 +52,7 @@ The OrganizationGuid parameter specifies the on-premises organization in a hybri Type: OnPremisesOrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: 2 @@ -67,12 +66,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-IntraOrganizationConnector.md b/exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md similarity index 88% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-IntraOrganizationConnector.md rename to exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md index 8a5ef4affc..d07a069726 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-intraorganizationconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-IntraOrganizationConnector @@ -17,19 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-IntraOrganizationConnector cmdlet to view the settings of Intra-Organization connectors. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-IntraOrganizationConnector [[-Identity] ] [-DomainController ] +Get-IntraOrganizationConnector [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION Intra-Organizational connectors enable features and services between divisions in your Exchange organization. It allows for the expansion of organizational boundaries for features and services across different hosts and network boundaries, such as between Active Directory forests, between on-premises and cloud-based organizations, or between tenants hosted in the same or different datacenters. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,43 +49,41 @@ This example returns details about the Intra-Organization connector named "MainC ## PARAMETERS -### -DomainController -This parameter is available only in on-premises Exchange. +### -Identity +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: -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +- Name +- Distinguished name (DN) +- GUID ```yaml -Type: Fqdn +Type: IntraOrganizationConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) +### -DomainController +This parameter is available only in on-premises Exchange. -- GUID +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: IntraOrganizationConnectorIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -94,12 +92,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-JournalRule.md b/exchange/exchange-ps/exchange/Get-JournalRule.md similarity index 86% rename from exchange/exchange-ps/exchange/policy-and-compliance/Get-JournalRule.md rename to exchange/exchange-ps/exchange/Get-JournalRule.md index 4c4e98c1b3..68b259f8f9 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-JournalRule.md +++ b/exchange/exchange-ps/exchange/Get-JournalRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-journalrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-JournalRule @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-JournalRule cmdlet to view the journal rules in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-JournalRule [[-Identity] ] [-DomainController ] [] +Get-JournalRule [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION The Get-JournalRule cmdlet displays journal rules configured in your organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,37 +49,37 @@ This example retrieves the specific journal rule Brokerage Communications and pi ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -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. ```yaml -Type: RuleIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -87,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-Label.md b/exchange/exchange-ps/exchange/Get-Label.md new file mode 100644 index 0000000000..b2cf3b4226 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-Label.md @@ -0,0 +1,129 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-Label + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-Label cmdlet to view sensitivity labels in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-Label [[-Identity] ] + [-IncludeDetailedLabelActions] + [-SkipValidations] + [-ValidateContentTypeRemoval] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-Label +``` + +This example returns a summary list of all sensitivity labels in the organization. + +### Example 2 +```powershell +Get-Label -Identity "Engineering Group" | Format-List +``` + +This example returns detailed information for the sensitivity label named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -IncludeDetailedLabelActions +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipValidations +{{ Fill SkipValidations Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidateContentTypeRemoval +{{ Fill ValidateContentTypeRemoval Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-LabelPolicy.md b/exchange/exchange-ps/exchange/Get-LabelPolicy.md new file mode 100644 index 0000000000..7a90fbaa71 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-LabelPolicy.md @@ -0,0 +1,95 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-LabelPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-LabelPolicy cmdlet to view sensitivity label policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-LabelPolicy [[-Identity] ] + [-ForceValidate ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-LabelPolicy | Format-Table Name +``` + +This example returns a summary list of all policies in the organization. + +### Example 2 +```powershell +Get-LabelPolicy -Identity "Engineering Group" | Format-List +``` + +This example returns detailed information for the policy named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ForceValidate +{{ Fill ForceValidate Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-LinkedUser.md b/exchange/exchange-ps/exchange/Get-LinkedUser.md similarity index 77% rename from exchange/exchange-ps/exchange/users-and-groups/Get-LinkedUser.md rename to exchange/exchange-ps/exchange/Get-LinkedUser.md index a2e53d7ed8..7407a5f12b 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-LinkedUser.md +++ b/exchange/exchange-ps/exchange/Get-LinkedUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-linkeduser +online version: https://learn.microsoft.com/powershell/module/exchange/get-linkeduser applicable: Exchange Online title: Get-LinkedUser schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-LinkedUser @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Get-LinkedUser cmdlet to view existing linked user accounts. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,21 +26,22 @@ Get-LinkedUser [-Anr ] [-Filter ] [-OrganizationalUnit ] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ### Identity ``` -Get-LinkedUser [[-Identity] - ] +Get-LinkedUser [[-Identity] ] [-Filter ] [-OrganizationalUnit ] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -64,17 +61,34 @@ This example returns a detailed information for the linked for the user laura@co ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -91,19 +105,16 @@ Accept wildcard characters: False ``` ### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). +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'"`. -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -118,30 +129,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -OrganizationalUnit This parameter is reserved for internal Microsoft use. @@ -177,20 +164,15 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName - - City - - FirstName - - LastName - - Office ```yaml @@ -211,12 +193,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/reporting/Get-LogonStatistics.md b/exchange/exchange-ps/exchange/Get-LogonStatistics.md similarity index 83% rename from exchange/exchange-ps/exchange/reporting/Get-LogonStatistics.md rename to exchange/exchange-ps/exchange/Get-LogonStatistics.md index 1b3a8d3800..bfdee00794 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-LogonStatistics.md +++ b/exchange/exchange-ps/exchange/Get-LogonStatistics.md @@ -1,42 +1,44 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-logonstatistics -applicable: Exchange Server 2010, Exchange Server 2013 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013" --- # Get-LogonStatistics ## SYNOPSIS -This cmdlet is available only in on-premises Exchange and is only functional in Exchange Server 2010. +This cmdlet is functional only in Exchange Server 2010. The Get-LogonStatistics cmdlet has been deprecated and is no longer used. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Database ``` Get-LogonStatistics -Database - [-DomainController ] [] + [-DomainController ] + [] ``` ### Identity ``` Get-LogonStatistics [-Identity] - [-DomainController ] [] + [-DomainController ] + [] ``` ### Server ``` Get-LogonStatistics -Server - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION @@ -57,61 +59,53 @@ This example returns logon statistics for all users connected to the server Serv ## PARAMETERS -### -Database -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 - -- Distinguished name (DN) +### -Identity +The Identity parameter specifies the mailbox to get logon statistics from. You can use one of the following values to identify the mailbox: - GUID +- Distinguished name (DN) +- Domain\\Account +- User principal name (UPN) +- Legacy Exchange DN +- SmtpAddress +- Alias -This parameter accepts pipeline input from the Get-MailboxDatabase command. +This parameter accepts pipeline input from the Get-Mailbox command. -You can't use this parameter with the Identity or Server parameters. +You can't use this parameter with the Database or Server parameters. ```yaml -Type: DatabaseIdParameter -Parameter Sets: Database +Type: LogonableObjectIdParameter +Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the mailbox to get logon statistics from. You can use one of the following values to identify the mailbox: - -- GUID +### -Database +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 - Distinguished name (DN) +- GUID -- Domain\\Account - -- User principal name (UPN) - -- Legacy Exchange DN - -- SmtpAddress - -- Alias - -This parameter accepts pipeline input from the Get-Mailbox command. +This parameter accepts pipeline input from the Get-MailboxDatabase command. -You can't use this parameter with the Database or Server parameters. +You can't use this parameter with the Identity or Server parameters. ```yaml -Type: LogonableObjectIdParameter -Parameter Sets: Identity +Type: DatabaseIdParameter +Parameter Sets: Database Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False @@ -121,7 +115,6 @@ Accept wildcard characters: False 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) - - NetBIOS name This parameter accepts pipeline input from the Get-ExchangeServer and Get-MailboxServer commands. @@ -132,7 +125,7 @@ You can't use this parameter with the Database or Identity parameters. Type: ServerIdParameter Parameter Sets: Server Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -148,7 +141,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -162,12 +155,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md new file mode 100644 index 0000000000..c7992e4955 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md @@ -0,0 +1,136 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-M365DataAtRestEncryptionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-M365DataAtRestEncryptionPolicy cmdlet to view existing Microsoft 365 data-at-rest encryption policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-M365DataAtRestEncryptionPolicy [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +M365 data-at-rest encryption policy cmdlets are accessible to compliance administrator role as part of the Exchange Online infrastructure. For more information, see [Service encryption with Microsoft Purview Customer Key](https://learn.microsoft.com/purview/customer-key-overview). + +You can create and assign a Microsoft 365 data-at-rest encryption policy at the tenant level by using the appropriate M365DataAtRestEncryptionPolicy cmdlets in Exchange Online PowerShell. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-M365DataAtRestEncryptionPolicy +``` + +This example returns a summary list of all Microsoft 365 data-at-rest encryption policies. + +### Example 2 +```powershell +Get-M365DataAtRestEncryptionPolicy -Identity "Contoso Corporate" | Format-List +``` + +This example returns detailed information about the policy named Contoso Corporate. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md new file mode 100644 index 0000000000..486e093215 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md @@ -0,0 +1,57 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-M365DataAtRestEncryptionPolicyAssignment + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-M365DataAtRestEncryptionPolicyAssignment cmdlet to view the currently assigned Microsoft 365 data-at-rest encryption policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-M365DataAtRestEncryptionPolicyAssignment [] +``` + +## DESCRIPTION +This cmdlet lists the Microsoft 365 data-at-rest encryption policy that's currently assigned to the tenant. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-M365DataAtRestEncryptionPolicyAssignment +``` + +This example returns a summary list of all Microsoft 365 data-at-rest encryption policy assignments. + +### Example 2 +```powershell +Get-M365DataAtRestEncryptionPolicyAssignment | Format-List +``` + +This example returns detailed information for all Microsoft 365 data-at-rest encryption policy assignments. + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-MailContact.md b/exchange/exchange-ps/exchange/Get-MailContact.md similarity index 82% rename from exchange/exchange-ps/exchange/users-and-groups/Get-MailContact.md rename to exchange/exchange-ps/exchange/Get-MailContact.md index 6cdd039950..aa00b27a06 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-MailContact.md +++ b/exchange/exchange-ps/exchange/Get-MailContact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-mailcontact +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-MailContact @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailContact cmdlet to view existing mail contacts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,7 +31,8 @@ Get-MailContact [-ANR ] [-ReadFromDomainController] [-RecipientTypeDetails ] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ### Identity @@ -46,13 +46,14 @@ Get-MailContact [[-Identity] ] [-ReadFromDomainController] [-RecipientTypeDetails ] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ## DESCRIPTION The Get-MailContact cmdlet retrieves all attributes of the specified contact. No parameters are required. If the cmdlet is run without a parameter, a complete list of contacts for the Exchange organization is returned. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,17 +73,36 @@ This example retrieves detailed information for the mail contact named Arlene. ## PARAMETERS +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ANR 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -103,7 +123,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -137,19 +157,16 @@ Accept wildcard characters: False ``` ### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). +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'"`. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -164,43 +181,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -220,11 +208,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -243,7 +228,9 @@ Accept wildcard characters: False ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -264,7 +251,6 @@ Accept wildcard characters: False The RecipientTypeDetails parameter filters the results by the specified mail contact subtype. Valid values are: - MailContact - - MailForestContact You can specify multiple values separated by commas. @@ -301,14 +287,12 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName - - Alias ```yaml @@ -329,12 +313,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md b/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md new file mode 100644 index 0000000000..910389aec2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md @@ -0,0 +1,368 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailDetailATPReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MailDetailATPReport cmdlet to list details about Exchange Online Protection and Microsoft Defender for Office 365 detections in your cloud-based organization for the last 10 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailDetailATPReport + [-DataSource ] + [-Direction ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-MalwareName ] + [-MessageId ] + [-MessageTraceId ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-RecipientAddress ] + [-SenderAddress ] + [-StartDate ] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. + +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +For the reporting period you specify, the cmdlet returns the following information: + +- Date +- Message ID +- Message Trace ID +- Domain +- Subject +- Message Size +- Direction: Values are Inbound, Outbound, IntraOrg Or Unknown. Unknown means the messages weren't processed by the filtering stack. In other words, the messages were dropped at the edge before they made it into our filtering stack, so we can't tell the direction for them. +- Sender Address +- Recipient Address +- Event Type +- Bulk complaint level +- Verdict Type +- Action +- File Name +- Malware Name + +This cmdlet is limited to 10,000 results. If you reach this limit, you can use the available parameters to filter the output. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailDetailATPReport -StartDate 7/22/2018 -EndDate 7/31/2018 +``` + +This example returns the actions for the last 10 days in July, 2018. (Note: Customers with Defender for Office 365 subscriptions will be able to get up to 30 days of data.) + +## PARAMETERS + +### -DataSource +{{ Fill DataSource Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Direction +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound +- IntraOrg + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- Advanced filter +- Anti-malware Engine +- Campaign +- File detonation +- File detonation reputation +- File reputation +- Fingerprint matching +- General filter +- Impersonation brand +- Impersonation domain +- Impersonation user +- Mailbox intelligence impersonation +- Message passed +- Mixed analysis detection +- Spoof DMARC +- Spoof external domain +- Spoof intra-org +- URL detonation +- URL detonation reputation +- URL malicious reputation + +**Note**: Some values correspond to features that are available only in Defender for Office 365 (plan 1 and plan 2 or plan 2 only). + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MalwareName +The MalwareName parameter filters the results by malware payload. Valid values are: + +- Excel +- EXE +- Flash +- Others +- PDF +- PowerPoint +- URL + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageTraceId +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. + +The MessageTraceId value is also available in the output of the following cmdlets: + +- Get-MailDetailDlpPolicyReport +- Get-MailDetailEncryptionReport +- Get-MailDetailTransportRuleReport +- Get-MessageTraceV2 +- Get-MessageTraceDetailV2 + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-MailDetailDlpPolicyReport.md b/exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md similarity index 76% rename from exchange/exchange-ps/exchange/reporting/Get-MailDetailDlpPolicyReport.md rename to exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md index 7617357067..213354eae3 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-MailDetailDlpPolicyReport.md +++ b/exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-maildetaildlppolicyreport +online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetaildlppolicyreport applicable: Exchange Online title: Get-MailDetailDlpPolicyReport schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-MailDetailDlpPolicyReport @@ -17,24 +16,31 @@ This cmdlet is available only in the cloud-based service. Use the Get-MailDetailDlpPolicyReport cmdlet to view the details of messages that matched the conditions defined by any data loss prevention (DLP) policies. This cmdlet works on messages that were sent within the last seven days. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailDetailDlpPolicyReport [-Action ] [-Direction ] - [-DlpPolicy ] [-Domain ] [-EndDate ] - [-EventType ] [-Expression ] [-MessageId ] - [-MessageTraceId ] [-Page ] [-PageSize ] [-ProbeTag ] - [-RecipientAddress ] [-SenderAddress ] [-StartDate ] - [-TransportRule ] [] +Get-MailDetailDlpPolicyReport [-Action ] + [-Direction ] + [-DlpPolicy ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-MessageId ] + [-MessageTraceId ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-RecipientAddress ] + [-SenderAddress ] + [-StartDate ] + [-TransportRule ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +54,7 @@ This example retrieves the details of messages sent by john@contoso.com that mat ## PARAMETERS ### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. +The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports. You can specify multiple values separated by commas. @@ -66,7 +72,12 @@ Accept wildcard characters: False ``` ### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound + +You can specify multiple values separated by commas. ```yaml Type: MultiValuedProperty @@ -116,7 +127,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". ```yaml Type: DateTime @@ -132,28 +143,20 @@ Accept wildcard characters: False ``` ### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. - -You can specify multiple values separated by commas. +The EventType parameter filters the report by the event type. Valid values are: -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online +- DLPActionHits +- DLPPolicyFalsePositive +- DLPPolicyHits +- DLPPolicyOverride +- DLPRuleHits -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify DLP event types for DLP reports. -### -Expression -This parameter is reserved for internal Microsoft use. +You can specify multiple values separated by commas. ```yaml -Type: Expression +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Online @@ -182,7 +185,17 @@ Accept wildcard characters: False ``` ### -MessageTraceId -The MessageTraceId parameter can be used with the recipient address to uniquely identify a message trace and obtain more details. A message trace ID is generated for every message that's processed by the system. +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. + +The MessageTraceId value is also available in the output of the following cmdlets: + +- Get-MailDetailATPReport +- Get-MailDetailEncryptionReport +- Get-MailDetailTransportRuleReport +- Get-MessageTraceV2 +- Get-MessageTraceDetailV2 ```yaml Type: MultiValuedProperty @@ -280,7 +293,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: DateTime @@ -316,12 +329,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md b/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md new file mode 100644 index 0000000000..62ff5f0f00 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md @@ -0,0 +1,298 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailDetailEncryptionReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MailDetailEncryptionReport cmdlet to view the details of encryption in your cloud-based organization for the last 10 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailDetailEncryptionReport [[-Organization] ] + [-AggregateBy ] + [-Direction ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-MessageId ] + [-MessageTraceId ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-StartDate ] + [] +``` + +## DESCRIPTION +For the reporting period you specify, the cmdlet returns the following default information: + +- DateTime +- Message ID +- Message Trace ID + +If you append the command with ` | Format-List`, the following additional information is returned: + +- Domain +- Direction +- Recipient Address +- Sender IP +- Sender Address +- Message Size +- Subject + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailDetailEncryptionReport -StartDate 12/13/2021 -EndDate 12/15/2021 +``` + +This example retrieves encryption details for messages between December 13, 2021 and December 15, 2021. + +## PARAMETERS + +### -Organization +{{ Fill Organization Description }} + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AggregateBy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Direction +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- EncryptionManual +- EncryptionPolicy + +To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type must correspond to the report. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageId +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageTraceId +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. + +The MessageTraceId value is also available in the output of the following cmdlets: + +- Get-MailDetailATPReport +- Get-MailDetailDlpPolicyReport +- Get-MailDetailTransportRuleReport +- Get-MessageTraceV2 +- Get-MessageTraceDetailV2 + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-MailDetailTransportRuleReport.md b/exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md similarity index 76% rename from exchange/exchange-ps/exchange/reporting/Get-MailDetailTransportRuleReport.md rename to exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md index 9dfd1888c4..ca463e1112 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-MailDetailTransportRuleReport.md +++ b/exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-maildetailtransportrulereport +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-MailDetailTransportRuleReport @@ -15,26 +14,32 @@ monikerRange: "exchonline-ps || eop-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-MailDetailTransportRuleReport cmdlet to view the details of messages that matched the conditions defined by any transport rules. +Use the Get-MailDetailTransportRuleReport cmdlet to view the details of messages that matched the conditions defined by any transport rules for the last 10 days. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailDetailTransportRuleReport [-Action ] [-Direction ] - [-Domain ] [-EndDate ] [-EventType ] - [-Expression ] [-MessageId ] [-MessageTraceId ] - [-Page ] [-PageSize ] [-ProbeTag ] [-RecipientAddress ] - [-SenderAddress ] [-StartDate ] [-TransportRule ] +Get-MailDetailTransportRuleReport [-Action ] + [-Direction ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-MessageId ] + [-MessageTraceId ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-RecipientAddress ] + [-SenderAddress ] + [-StartDate ] + [-TransportRule ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +53,7 @@ This example retrieves the details of messages sent by john@contoso.com that mat ## PARAMETERS ### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. +The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports. You can specify multiple values separated by commas. @@ -66,7 +71,12 @@ Accept wildcard characters: False ``` ### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound + +You can specify multiple values separated by commas. ```yaml Type: MultiValuedProperty @@ -100,7 +110,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". ```yaml Type: DateTime @@ -116,28 +126,19 @@ Accept wildcard characters: False ``` ### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. +The EventType parameter filters the report by the event type. Valid values are: -You can specify multiple values separated by commas. +- EncryptionManual +- EncryptionPolicy +- TransportRuleActionHits +- TransportRuleHits -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection + To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify rule event types for rule reports. -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. +You can specify multiple values separated by commas. ```yaml -Type: Expression +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Online, Exchange Online Protection @@ -166,7 +167,17 @@ Accept wildcard characters: False ``` ### -MessageTraceId -The MessageTraceId parameter can be used with the recipient address to uniquely identify a message trace and obtain more details. A message trace ID is generated for every message that's processed by the system. +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. + +The MessageTraceId value is also available in the output of the following cmdlets: + +- Get-MailDetailATPReport +- Get-MailDetailDlpPolicyReport +- Get-MailDetailEncryptionReport +- Get-MessageTraceV2 +- Get-MessageTraceDetailV2 ```yaml Type: MultiValuedProperty @@ -264,7 +275,9 @@ Accept wildcard characters: False ### -StartDate 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". +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". + +Although you can enter a date up to 30 days old, only data from the last 10 days is returned. ```yaml Type: DateTime @@ -300,12 +313,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MailFilterListReport.md b/exchange/exchange-ps/exchange/Get-MailFilterListReport.md new file mode 100644 index 0000000000..4fe3fbe363 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailFilterListReport.md @@ -0,0 +1,135 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailFilterListReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MailFilterListReport cmdlet to obtain values for various parameters that can be supplied to other reporting cmdlets. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailFilterListReport + [-Domain ] + [-Expression ] + [-ProbeTag ] + [-SelectionTarget ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailFilterListReport -SelectionTarget TransportRule +``` + +This example uses the Get-MailFilterListReport cmdlet to return information about transport rules. + +## PARAMETERS + +### -Domain +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Expression +This parameter is available only in Security & Compliance PowerShell. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Expression +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SelectionTarget +The SelectionTarget parameter filters the report information by object type. Valid values are: + +- Actions +- DlpPolicy +- DlpRule +- Domain +- EventTypes +- FindOnPremConnector +- TransportRule + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/sharing-and-collaboration/Get-MailPublicFolder.md b/exchange/exchange-ps/exchange/Get-MailPublicFolder.md similarity index 78% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-MailPublicFolder.md rename to exchange/exchange-ps/exchange/Get-MailPublicFolder.md index bc39afac43..eea8f2f7e7 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-MailPublicFolder.md +++ b/exchange/exchange-ps/exchange/Get-MailPublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-mailpublicfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailPublicFolder @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailPublicFolder cmdlet to retrieve mail-related information about mail-enabled public folders. If you want information about the basic (not mail-related) settings of mail-enabled public folders, use the Get-PublicFolder cmdlet instead. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,6 +27,7 @@ Get-MailPublicFolder [-Anr ] [-DomainController ] [-Filter ] [-IgnoreDefaultScope] + [-IncludeGrantSendOnBehalfToWithDisplayNames] [-ReadFromDomainController] [-ResultSize ] [-Server ] @@ -41,6 +41,7 @@ Get-MailPublicFolder [[-Identity] ] [-DomainController ] [-Filter ] [-IgnoreDefaultScope] + [-IncludeGrantSendOnBehalfToWithDisplayNames] [-ReadFromDomainController] [-ResultSize ] [-Server ] @@ -48,7 +49,7 @@ Get-MailPublicFolder [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -75,17 +76,31 @@ This example returns all mail-enabled public folders that begin with the word Ma ## PARAMETERS +### -Identity +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: MailPublicFolderIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -104,7 +119,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -138,19 +153,16 @@ Accept wildcard characters: False ``` ### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). +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'"`. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -165,38 +177,37 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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. +### -IgnoreDefaultScope +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. -You can omit the parameter label so that only the public folder name or GUID is supplied. +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml -Type: MailPublicFolderIdParameter -Parameter Sets: Identity +Type: SwitchParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` -### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: +### -IncludeGrantSendOnBehalfToWithDisplayNames +This parameter is available only in the cloud-based service. -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. +{{ Fill IncludeGrantSendOnBehalfToWithDisplayNames Description }} ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -208,7 +219,9 @@ Accept wildcard characters: False ### -ReadFromDomainController 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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -242,16 +255,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -270,16 +280,13 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName - - Alias - - Id ```yaml @@ -300,12 +307,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md new file mode 100644 index 0000000000..b18dc3f97a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md @@ -0,0 +1,364 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailTrafficATPReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MailTrafficATPReport cmdlet to view the results of Exchange Online Protection and Microsoft Defender for Office 365 detections in your cloud-based organization for the last 90 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailTrafficATPReport + [-Action ] + [-AggregateBy ] + [-Direction ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-NumberOfRows ] + [-Page ] + [-PageSize ] + [-PivotBy ] + [-ProbeTag ] + [-StartDate ] + [-SummarizeBy ] + [-ThreatClassification ] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. + +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +For the reporting period you specify, the cmdlet returns the following information: + +- Date +- Event Type +- Direction +- Verdict Source +- Message Count + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailTrafficATPReport +``` + +This example retrieves details for messages for the last 92 days. + +### Example 2 +```powershell +Get-MailTrafficATPReport -StartDate (Get-Date "12/25/2021 12:01 AM").ToUniversalTime() -EndDate (Get-Date "12/25/2021 11:59 PM").ToUniversalTime() -Direction Outbound +``` + +This example retrieves the statistics for outgoing messages on December 25, 2021 and displays the results in a table. + +## PARAMETERS + +### -Action +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AggregateBy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Direction +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound +- IntraOrg + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -EndDate +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: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +If you use this parameter, you also need to use the StartDate parameter. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- Advanced filter +- Anti-malware Engine +- Campaign +- File detonation +- File detonation reputation +- File reputation +- Fingerprint matching +- General filter +- Impersonation brand +- Impersonation domain +- Impersonation user +- Mailbox intelligence impersonation +- Message passed +- Mixed analysis detection +- Spoof DMARC +- Spoof external domain +- Spoof intra-org +- URL detonation +- URL detonation reputation +- URL malicious reputation + +**Note**: Some values correspond to features that are available only in Defender for Office 365 (plan 1 and plan 2 or plan 2 only). + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberOfRows +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PivotBy +{{ Fill PivotBy Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +If you use this parameter, you also need to use the EndDate parameter. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SummarizeBy +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: + +- Action +- Direction +- Domain +- EventType + +You can specify multiple values separated by commas. When you specify the values Action or Domain, the value is not displayed in the results (the values in the corresponding columns are blank). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThreatClassification +{{ Fill ThreatClassification Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md new file mode 100644 index 0000000000..8fe274f754 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md @@ -0,0 +1,273 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailTrafficEncryptionReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MailTrafficEncryptionReport cmdlet to view the results of encryption in your cloud-based organization for the last 92 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailTrafficEncryptionReport + [-Action ] + [-AggregateBy ] + [-Direction ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-StartDate ] + [-SummarizeBy ] + [] +``` + +## DESCRIPTION +For the reporting period you specify, the cmdlet returns the following information: + +- DateTime +- Event Type +- Direction +- Action +- Message Count +- Recipient Count + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailTrafficEncryptionReport -Direction Inbound -StartDate 12/13/2021 -EndDate 12/15/2021 +``` + +This example retrieves encryption information for incoming messages between December 13, 2021 and December 15, 2021. + +## PARAMETERS + +### -Action +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AggregateBy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Direction +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- EncryptionManual +- EncryptionPolicy + +To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type must correspond to the report. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SummarizeBy +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: + +- Action +- Domain +- EventType + +You can specify multiple values separated by commas. When you specify the values Action or Domain, the value is not displayed in the results (the values in the corresponding columns are blank). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-MailTrafficPolicyReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md similarity index 78% rename from exchange/exchange-ps/exchange/reporting/Get-MailTrafficPolicyReport.md rename to exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md index d2a8d34e88..f1ab603a7f 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-MailTrafficPolicyReport.md +++ b/exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailtrafficpolicyreport +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-MailTrafficPolicyReport @@ -15,25 +14,41 @@ monikerRange: "exchonline-ps || eop-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-MailTrafficPolicyReport cmdlet to view statistics about messages that were affected by data loss prevention (DLP) policies and transport rules. +Use the Get-MailTrafficPolicyReport cmdlet to view statistics about messages that were affected by data loss prevention (DLP) policies and transport rules for the last 90 days. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailTrafficPolicyReport [-Action ] [-AggregateBy ] - [-Direction ] [-DlpPolicy ] [-Domain ] - [-EndDate ] [-EventType ] [-Expression ] [-Page ] - [-PageSize ] [-ProbeTag ] [-StartDate ] [-SummarizeBy ] - [-TransportRule ] [] +Get-MailTrafficPolicyReport [-Action ] + [-AggregateBy ] + [-Direction ] + [-DlpPolicy ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-StartDate ] + [-SummarizeBy ] + [-TransportRule ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +For the reporting period you specify, the cmdlet returns the following information: + +- Domain +- Date +- DLP Policy +- Transport Rule +- Event Type +- Direction +- Message Count + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,7 +76,7 @@ This example is similar to the previous example, but now the results are summari ## PARAMETERS ### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. +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. @@ -95,7 +110,12 @@ Accept wildcard characters: False ``` ### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound + +You can specify multiple values separated by commas. ```yaml Type: MultiValuedProperty @@ -145,7 +165,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". ```yaml Type: DateTime @@ -161,28 +181,22 @@ Accept wildcard characters: False ``` ### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. +The EventType parameter filters the report by the event type. Valid values are: -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection +- DLPActionHits +- DLPPolicyFalsePositive +- DLPPolicyHits +- DLPPolicyOverride +- DLPRuleHits +- TransportRuleActionHits +- TransportRuleHits -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify policy event types for policy reports. -### -Expression -This parameter is reserved for internal Microsoft use. +You can specify multiple values separated by commas. ```yaml -Type: Expression +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Online, Exchange Online Protection @@ -245,7 +259,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: DateTime @@ -263,7 +277,16 @@ Accept wildcard characters: False ### -SummarizeBy 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 the Get-MailTrafficPolicyReport cmdlet, the SummarizeBy parameter accepts the values Action, DLPPolicy, Domain, EventType, and TransportRule. You can specify multiple values separated by commas. +For this cmdlet, valid values are: + +- Action +- Direction +- DLPPolicy +- Domain +- EventType +- TransportRule + +You can specify multiple values separated by commas. When you specify the values DLPPolicy, Domain, EventType, or TransportRule the value is not displayed in the results (the values in the corresponding columns are blank). ```yaml Type: MultiValuedProperty @@ -299,12 +322,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/reporting/Get-MailTrafficSummaryReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md similarity index 79% rename from exchange/exchange-ps/exchange/reporting/Get-MailTrafficSummaryReport.md rename to exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md index 2163d81bf2..5ef4d9692a 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-MailTrafficSummaryReport.md +++ b/exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailtrafficsummaryreport +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-MailTrafficSummaryReport @@ -15,19 +14,22 @@ monikerRange: "exchonline-ps || eop-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-MailTrafficSummaryReport cmdlet to view summary information about message traffic in your organization. +Use the Get-MailTrafficSummaryReport cmdlet to view summary information about message traffic in your organization for the last 90 days. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailTrafficSummaryReport [-Category ] [-DlpPolicy ] - [-Domain ] [-EndDate ] [-Expression ] [-Page ] - [-PageSize ] [-ProbeTag ] [-StartDate ] [-TransportRule ] +Get-MailTrafficSummaryReport [-Category ] + [-DlpPolicy ] + [-Domain ] + [-EndDate ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-StartDate ] + [-TransportRule ] [] ``` @@ -35,12 +37,10 @@ Get-MailTrafficSummaryReport [-Category ] [-DlpPolicy ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-ResultSize ] + [-SharedWithMailUser] + [-SoftDeletedMailUser] + [-SortBy ] + [] +``` + +### Identity +``` +Get-MailUser [[-Identity] ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-ResultSize ] + [-SharedWithMailUser] + [-SoftDeletedMailUser] + [-SortBy ] + [] +``` + +### LOBAppAccount +``` +Get-MailUser [-LOBAppAccount] + [-Filter ] + [-OrganizationalUnit ] + [-ProgressAction ] + [-ResultSize ] + [-SharedWithMailUser] + [-SoftDeletedMailUser] + [-SortBy ] + [] +``` + +### HVEAccount +``` +Get-MailUser [-HVEAccount] + [-Filter ] + [-OrganizationalUnit ] + [-ResultSize ] + [-SharedWithMailUser] + [-SortBy ] + [-SoftDeletedMailUser] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailUser +``` + +This example returns a summary list of all mail users in the organization. + +### Example 2 +```powershell +Get-MailUser -Identity Ed | Format-List +``` + +This example returns detailed information for the mail user named Ed. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +```yaml +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 +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -Credential +This parameter is available only in on-premises Exchange. + +The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. + +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). + +```yaml +Type: PSCredential +Parameter Sets: AnrSet, Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: Fqdn +Parameter Sets: AnrSet, Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -HVEAccount +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. + +```yaml +Type: SwitchParameter +Parameter Sets: LOBAppAccount +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Position: Named +Default value: None +Required: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -LOBAppAccount +This parameter is available only in the cloud-based service. + +{{ Fill LOBAppAccount Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: LOBAppAccount +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -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: (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 +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -SharedWithMailUser +This parameter is available only in the cloud-based service. + +{{ Fill SharedWithMailUser Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, Identity +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName +- Alias + +```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 +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -SoftDeletedMailUser +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. + +Soft-deleted mail users are deleted mail users that are still recoverable. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-Mailbox.md b/exchange/exchange-ps/exchange/Get-Mailbox.md new file mode 100644 index 0000000000..cae3773fe1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-Mailbox.md @@ -0,0 +1,923 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-Mailbox + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-Mailbox cmdlet to view mailbox objects and attributes, populate property pages, or supply mailbox information to other tasks. + +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXOMailbox cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AnrSet +``` +Get-Mailbox [-Anr ] + [-Arbitration] + [-Archive] + [-AuditLog] + [-AuxAuditLog] + [-Credential ] + [-DomainController ] + [-Filter ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-InactiveMailboxOnly] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeEmailAddressDisplayNames] + [-IncludeForwardingAddressWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeInactiveMailbox] + [-Migration] + [-Monitoring] + [-OrganizationalUnit ] + [-PublicFolder] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-RemoteArchive] + [-ResultSize ] + [-SoftDeletedMailbox] + [-SortBy ] + [-SupervisoryReviewPolicy] + [] +``` + +### DatabaseSet +``` +Get-Mailbox [-Database ] + [-Arbitration] + [-Archive] + [-AuditLog] + [-AuxAuditLog] + [-Credential ] + [-DomainController ] + [-Filter ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-Migration] + [-Monitoring] + [-OrganizationalUnit ] + [-PublicFolder] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-RemoteArchive] + [-ResultSize ] + [-SortBy ] + [-SupervisoryReviewPolicy] + [] +``` + +### Identity +``` +Get-Mailbox [[-Identity] ] + [-Arbitration] + [-Archive] + [-AuditLog] + [-AuxAuditLog] + [-Credential ] + [-DomainController ] + [-Filter ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-InactiveMailboxOnly] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeEmailAddressDisplayNames] + [-IncludeForwardingAddressWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeInactiveMailbox] + [-Migration] + [-Monitoring] + [-OrganizationalUnit ] + [-PublicFolder] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-RemoteArchive] + [-ResultSize ] + [-SoftDeletedMailbox] + [-SortBy ] + [-SupervisoryReviewPolicy] + [] +``` + +### ServerSet +``` +Get-Mailbox [-Server ] + [-Arbitration] + [-Archive] + [-AuditLog] + [-AuxAuditLog] + [-Credential ] + [-DomainController ] + [-Filter ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-Migration] + [-Monitoring] + [-OrganizationalUnit ] + [-PublicFolder] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-RemoteArchive] + [-ResultSize ] + [-SortBy ] + [-SupervisoryReviewPolicy] + [] +``` + +### MailboxPlanSet +``` +Get-Mailbox [-MailboxPlan ] + [-Archive] + [-Filter ] + [-GroupMailbox] + [-InactiveMailboxOnly] + [-IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAcceptMessagesOnlyFromWithDisplayNames] + [-IncludeEmailAddressDisplayNames] + [-IncludeForwardingAddressWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeInactiveMailbox] + [-Migration] + [-OrganizationalUnit ] + [-PublicFolder] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SoftDeletedMailbox] + [-SortBy ] + [] +``` + +## DESCRIPTION +When you use the Get-Mailbox cmdlet in on-premises Exchange environments to view the quota settings for a mailbox, you first need to check the value of the UseDatabaseQuotaDefaults property. The value True means per-mailbox quota settings are ignored, and you need to use the Get-MailboxDatabase cmdlet to see the actual values. If the UseDatabaseQuotaDefaults property is False, the per-mailbox quota settings are used, so what you see with the Get-Mailbox cmdlet are the actual quota values for the mailbox. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-Mailbox -ResultSize unlimited +``` + +This example returns a summary list of all the mailboxes in your organization. + +### Example 2 +```powershell +Get-Mailbox -OrganizationalUnit Users +``` + +This example returns a list of all the mailboxes in your organization in the Users OU. + +### Example 3 +```powershell +Get-Mailbox -Anr Chr +``` + +This example returns all the mailboxes that resolve from the ambiguous name resolution search on the string "Chr". This example returns mailboxes for users such as Chris Ashton, Christian Hess, and Christa Geller. + +### Example 4 +```powershell +Get-Mailbox -Archive -Database MBXDB01 +``` + +This example returns a summary list of all archive mailboxes in the database named MBXDB01. + +### Example 5 +```powershell +Get-Mailbox -Identity ed@contoso.com -RemoteArchive +``` + +This example returns information about the remote archive mailbox for the user ed@contoso.com. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Anr, Database, MailboxPlan or Server parameters. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Arbitration +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. + +Arbitration mailboxes are system mailboxes that are used for storing different types of system data and for managing messaging approval workflow. + +To return arbitration mailboxes that are used to store audit log settings or data, don't use this switch. Instead, use the AuditLog or AuxAuditLog switches. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Archive +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuditLog +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. + +Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. + +To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuxAuditLog +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. + +Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. + +To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +This parameter is available only in on-premises Exchange. + +The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. + +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: AnrSet, DatabaseSet, Identity, ServerSet +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Database +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: + +- Name +- Distinguished name (DN) +- GUID + +You can't use this parameter with the Anr, Identity, or Server parameters. + +```yaml +Type: DatabaseIdParameter +Parameter Sets: DatabaseSet +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InactiveMailboxOnly +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. + +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. + +To include active and inactive mailboxes in the results, don't use this switch. Instead, use the IncludeInactiveMailbox switch. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, Identity, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromWithDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill IncludeAcceptMessagesOnlyFromWithDisplayNames Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeEmailAddressDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill IncludeEmailAddressDisplayNames Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeForwardingAddressWithDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill IncludeForwardingAddressWithDisplayNames Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeGrantSendOnBehalfToWithDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill IncludeGrantSendOnBehalfToWithDisplayNames Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeInactiveMailbox +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. + +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. + +To return only inactive mailboxes in the results, don't use this switch. Instead, use the InactiveMailboxOnly switch. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, Identity, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxPlan +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: + +- Name +- Alias +- Display name +- Distinguished name (DN) +- GUID + +A mailbox plan specifies the permissions and features available to a mailbox user in cloud-based organizations. You can see the available mailbox plans by using the Get-MailboxPlan cmdlet. + +You can't use this parameter with the Anr or Identity parameters. + +```yaml +Type: MailboxPlanIdParameter +Parameter Sets: MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Migration +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Monitoring +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. + +Monitoring mailboxes are associated with managed availability and the Exchange Health Manager service, and have a RecipientTypeDetails property value of MonitoringMailbox. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolder +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientTypeDetails +The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are: + +- DiscoveryMailbox +- EquipmentMailbox +- GroupMailbox (Exchange 2013 or later and cloud) +- LegacyMailbox +- LinkedMailbox +- LinkedRoomMailbox (Exchange 2013 or later and cloud) +- RoomMailbox +- SchedulingMailbox (Exchange 2016 or later and cloud) +- SharedMailbox +- TeamMailbox (Exchange 2013 or later and cloud) +- UserMailbox + +You can specify multiple values separated by commas. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteArchive +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. + +Remote archive mailboxes are archive mailboxes in the cloud-based service that are associated with mailbox users in on-premises Exchange organizations. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +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 +``` + +### -Server +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. + +You can use any value that uniquely identifies the server. For example: + +- Name +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +You can't use this parameter with the Anr, Database, or Identity parameters. + +The ServerName and ServerLegacyDN properties for a mailbox may not be updated immediately after a mailbox move within a database availability group (DAG). To get the most up-to-date values for these mailbox properties, run the command `Get-Mailbox | Get-MailboxStatistics | Format-List Name,ServerName,ServerLegacyDN`. + +**Note**: The result from this parameter could be a legacy value before migration. For better results, use the Database parameter instead. + +```yaml +Type: ServerIdParameter +Parameter Sets: ServerSet +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -SoftDeletedMailbox +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. + +Soft-deleted mailboxes are deleted mailboxes that are still recoverable. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, Identity, MailboxPlanSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName +- Alias +- Office +- ServerLegacyDN + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SupervisoryReviewPolicy +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md new file mode 100644 index 0000000000..52e699b66f --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxAuditBypassAssociation + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve information about the AuditBypassEnabled property value for user accounts (on-premises Exchange and the cloud) and computer accounts (on-premises Exchange only). You use the [Set-MailboxAuditBypassAssociation](https://learn.microsoft.com/powershell/module/exchange/set-mailboxauditbypassassociation) cmdlet to enable this property to bypass mailbox audit logging. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailboxAuditBypassAssociation [[-Identity] ] + [-DomainController ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +When you configure a user or computer account to bypass mailbox audit logging, access or actions taken by the user account or computer account to any mailbox isn't logged. By bypassing trusted user accounts or computer accounts that need to access mailboxes frequently, you can reduce the noise in mailbox audit logs. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxAuditBypassAssociation -ResultSize unlimited | Format-Table Name,AuditBypassEnabled +``` + +This example returns all accounts and whether they are configured or not configured for mailbox audit logging bypass. + +### Example 2 +```powershell +Get-MailboxAuditBypassAssociation -Identity "Svc-MyApplication" +``` + +This example returns the status of the AuditBypassEnabled property for the Svc-MyApplication account. + +### Example 3 +```powershell +$MBX = Get-MailboxAuditBypassAssociation -ResultSize unlimited + +$MBX | where {$_.AuditBypassEnabled -eq $true} | Format-Table Name,AuditBypassEnabled +``` + +This example returns all accounts that are configured for mailbox audit logging bypass. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (All) +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 +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Get-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md similarity index 78% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxAutoReplyConfiguration.md rename to exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md index 64f1d895dd..2eaf391e3c 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxAutoReplyConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxautoreplyconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxAutoReplyConfiguration @@ -17,35 +16,36 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxAutoReplyConfiguration cmdlet to retrieve Automatic Replies settings for a specific mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailboxAutoReplyConfiguration [-Identity] [-Credential ] - [-DomainController ] [-ReadFromDomainController] [-ResultSize ] [] +Get-MailboxAutoReplyConfiguration [-Identity] + [-Credential ] + [-DomainController ] + [-ReadFromDomainController] + [-ResultSize ] + [-UseCustomRouting] + [] ``` ## DESCRIPTION You can use the Get-MailboxAutoReplyConfiguration cmdlet to retrieve all the mailboxes enabled for Automatic Replies. When run, the cmdlet returns Automatic Replies settings for the specified mailbox that include the following: - Mailbox identity value - - Whether Automatic Replies is enabled, scheduled, or disabled for the mailbox - - Start and end date, time during which Automatic Replies will be sent - - Whether external senders receive Automatic Replies (none, known senders, or all) - - Automatic Replies message to be sent to internal and external senders -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-Mailbox | Get-MailboxAutoReplyConfiguration +Get-Mailbox -ResultSize unlimited | Get-MailboxAutoReplyConfiguration ``` This example returns Automatic Replies settings for all mailboxes in the Exchange organization. @@ -57,36 +57,20 @@ Get-MailboxAutoReplyConfiguration -Identity 'contoso.com/Users/Tony Smith' This example retrieves Automatic Replies settings for Tony's mailbox at contoso.com. -### Example 3 -```powershell -Get-Mailbox | Get-MailboxAutoReplyConfiguration -ResultSize unlimited -``` - -This example retrieves all Automatic Replies settings for all mailboxes in the Exchange organization. - ## PARAMETERS ### -Identity The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -105,7 +89,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -139,9 +123,11 @@ Accept wildcard characters: False ``` ### -ReadFromDomainController -The ReadFromDomainController parameter specifies that the user information is read from a domain controller in the user's domain. If you set the recipient scope to include all recipients in the forest and if you don't use this parameter, it's possible that the user information is read from a global catalog with outdated information. If you use this parameter, multiple reads might be necessary to get the information. +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. -By default, the recipient scope is set to the domain that hosts your servers that run Microsoft Exchange. +By default, the recipient scope is set to the domain that hosts your Exchange servers. ```yaml Type: SwitchParameter @@ -172,17 +158,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Get-MailboxCalendarConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md similarity index 78% rename from exchange/exchange-ps/exchange/client-access/Get-MailboxCalendarConfiguration.md rename to exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md index 1a53deb8ad..d8966ce18e 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-MailboxCalendarConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-mailboxcalendarconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxCalendarConfiguration @@ -17,41 +16,43 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxCalendarConfiguration cmdlet to show the calendar settings for a specified mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX +### Default ``` Get-MailboxCalendarConfiguration [-Identity] [-DomainController ] [] ``` +### Identity +``` +Get-MailboxCalendarConfiguration [[-Identity] ] [] +``` + +### MailboxLocation +``` +Get-MailboxCalendarConfiguration [-MailboxLocation ] [] +``` + ## DESCRIPTION The Get-MailboxCalendarConfiguration cmdlet returns settings for the calendar of the specified mailbox, including the following: - Workdays: Days that appear in the calendar as work days in Outlook on the web - - WorkingHoursStartTime: Time that the calendar work day starts - - WorkingHoursEndTime: Time that the calendar work day ends - - WorkingHoursTimeZone: Time zone set on the mailbox for the working hours start and end times - - WeekStartDay: First day of the calendar work week - - ShowWeekNumbers: Number for each week ranging from 1 through 52 for the calendar while in month view in Outlook on the web - - TimeIncrement: Increments in minutes in which the calendar displays time in Outlook on the web - - RemindersEnabled: Whether Outlook on the web provides a visual cue when a calendar reminder is due - - ReminderSoundEnabled: Whether a sound is played when a calendar reminder is due - - DefaultReminderTime: Length of time before each meeting or appointment that the calendar in Outlook on the web shows the reminder To see all of the settings returned, pipeline the command to the Format-List command. To view a code sample, see "Example 1." -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,35 +83,39 @@ This example requests that the domain controller DC1 retrieves calendar settings The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter -Parameter Sets: (All) +Parameter Sets: Default Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 Default value: None -Accept pipeline input: True +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 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) Accept wildcard characters: False ``` @@ -121,7 +126,7 @@ The DomainController parameter specifies the domain controller that's used by th ```yaml Type: Fqdn -Parameter Sets: (All) +Parameter Sets: Default Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -132,17 +137,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MailboxLocation +This parameter is available only in the cloud-based service. + +{{ Fill MailboxLocation Description }} + +```yaml +Type: MailboxLocationIdParameter +Parameter Sets: MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxCalendarFolder.md b/exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md similarity index 87% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxCalendarFolder.md rename to exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md index fc9257bd66..075437cc2c 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxCalendarFolder.md +++ b/exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxcalendarfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxCalendarFolder @@ -17,19 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxCalendarFolder cmdlet to retrieve the publishing or sharing settings for a specified mailbox calendar folder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailboxCalendarFolder [-Identity] [-DomainController ] +Get-MailboxCalendarFolder [-Identity] + [-UseCustomRouting] + [-DomainController ] [] ``` ## DESCRIPTION The Get-MailboxCalendarFolder cmdlet retrieves information for the specified calendar folder. This information includes the calendar folder name, whether the folder is currently published or shared, the start and end range of calendar days published, the level of details published for the calendar, whether the published URL of the calendar can be searched on the web and the published URL for the calendar. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,23 +63,14 @@ The Identity parameter specifies the calendar folder that you want to view. The For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Calendar`. @@ -114,17 +106,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxDatabase.md b/exchange/exchange-ps/exchange/Get-MailboxDatabase.md similarity index 92% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxDatabase.md rename to exchange/exchange-ps/exchange/Get-MailboxDatabase.md index 134cb82930..82286a48e4 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxDatabase.md +++ b/exchange/exchange-ps/exchange/Get-MailboxDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/get-mailboxdatabase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MailboxDatabase @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MailboxDatabase cmdlet to retrieve one or more mailbox database objects from a server or organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ Get-MailboxDatabase -Server [-IncludeCorrupted] [-IncludePreExchange2010] [-IncludePreExchange2013] - [-Status] [] + [-Status] + [] ``` ### Identity @@ -40,7 +40,8 @@ Get-MailboxDatabase [[-Identity] ] [-IncludeCorrupted] [-IncludePreExchange2010] [-IncludePreExchange2013] - [-Status] [] + [-Status] + [] ``` ## DESCRIPTION @@ -49,14 +50,11 @@ If you use the Get-MailboxDatabase cmdlet with no parameters, it retrieves infor The following list describes the properties that are returned in the results. - Name: Name of the database. - - Server: Server hosting the database. - - Recovery: Specifies whether the new database is designated as a recovery database. - - ReplicationType: Replication type of the database. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,15 +72,34 @@ This example returns detailed information about the mailbox database named Mailb ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID + +If you have multiple databases with the same name, the command retrieves all databases with the same name in the specified scope. + +```yaml +Type: DatabaseIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Server The Server parameter filters the results by the specified Mailbox server. You can use any value that uniquely identifies the server. For example: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use this parameter with the Identity parameter. @@ -132,30 +149,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -If you have multiple databases with the same name, the command retrieves all databases with the same name in the specified scope. - -```yaml -Type: DatabaseIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IncludeCorrupted This parameter is reserved for internal Microsoft use. @@ -173,7 +166,7 @@ Accept wildcard characters: False ``` ### -IncludePreExchange2010 -This parameter is available or functional only in 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. @@ -210,9 +203,7 @@ Accept wildcard characters: False The Status switch specifies whether to retrieve the available free space in the database root and information about the following attributes: - BackupInProgress - - Mounted - - OnlineMaintenanceInProgress You don't need to specify a value with this switch. @@ -237,12 +228,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Get-MailboxDatabaseCopyStatus.md b/exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md similarity index 86% rename from exchange/exchange-ps/exchange/database-availability-groups/Get-MailboxDatabaseCopyStatus.md rename to exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md index a336f68e7a..d58b4dc67d 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Get-MailboxDatabaseCopyStatus.md +++ b/exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/get-mailboxdatabasecopystatus +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MailboxDatabaseCopyStatus @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MailboxDatabaseCopyStatus cmdlet to view health and status information about one or more mailbox database copies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,23 +27,26 @@ Get-MailboxDatabaseCopyStatus -Server [-ConnectionStatus] [-DomainController ] [-ExtendedErrorInfo] - [-UseServerCache] [] + [-UseServerCache] + [] ``` ### Identity ``` -Get-MailboxDatabaseCopyStatus [[-Identity] ] [-Local] +Get-MailboxDatabaseCopyStatus [[-Identity] ] + [-Local] [-Active] [-ConnectionStatus] [-DomainController ] [-ExtendedErrorInfo] - [-UseServerCache] [] + [-UseServerCache] + [] ``` ## DESCRIPTION If a database is specified by using the Identity parameter with the command, the status of all copies of the database is returned. If a server is specified by using the Server parameter with the command, information about all database copies on the server is returned. If neither parameter is specified with the command, information about all database copies in the organization is returned. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -71,6 +73,22 @@ This example returns the status for the copy of database DB1 on the Mailbox serv ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Server 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. @@ -88,7 +106,7 @@ Accept wildcard characters: False ``` ### -Active -The Active switch specifies whether to return mailbox database copy status for the active mailbox database copy only. +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 @@ -135,24 +153,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Local -The Local switch specifies whether to return mailbox database copy status information from only the local Mailbox server. +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 @@ -168,7 +170,7 @@ Accept wildcard characters: False ``` ### -ExtendedErrorInfo -The ExtendedErrorInfo switch specifies whether to return an output object containing any exception details. +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 @@ -184,7 +186,7 @@ Accept wildcard characters: False ``` ### -UseServerCache -The UseServerCache switch specifies whether to enable a server-side remote procedure call (RPC) caching of status information for 5 seconds. +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 @@ -204,12 +206,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxExportRequest.md b/exchange/exchange-ps/exchange/Get-MailboxExportRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxExportRequest.md rename to exchange/exchange-ps/exchange/Get-MailboxExportRequest.md index 9bd4bded01..106407e8e1 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxExportRequest.md +++ b/exchange/exchange-ps/exchange/Get-MailboxExportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxexportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MailboxExportRequest @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MailboxExportRequest cmdlet to view the detailed status of an ongoing export request that was initiated by using the New-MailboxExportRequest cmdlet. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-MailboxExportRequest [[-Identity] ] [-DomainController ] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ### MailboxFiltering @@ -41,7 +41,8 @@ Get-MailboxExportRequest [-Mailbox ] [-ResultSize ] [-Status ] [-Suspend ] - [-RequestQueue ] [] + [-RequestQueue ] + [] ``` ### MailboxLocationFiltering @@ -55,13 +56,14 @@ Get-MailboxExportRequest [-Mailbox ] [-ResultSize ] [-Status ] [-Suspend ] - [-RequestQueue ] [] + [-RequestQueue ] + [] ``` ## DESCRIPTION The search criteria for the Get-MailboxExportRequest cmdlet is a Boolean And statement. If you use multiple parameters, you narrow your search and reduce your search results. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -96,20 +98,15 @@ This example returns all export requests that have the name DB01toPST where the ## PARAMETERS ### -Identity -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: \\\\. Exchange automatically precedes the request with the mailbox's alias. +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: - BatchName - - Mailbox - - Name - - Status - - Suspend - - HighPriority ```yaml @@ -144,14 +141,12 @@ Accept wildcard characters: False ``` ### -Database -This parameter is available or functional only in 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -189,7 +184,6 @@ Accept wildcard characters: False 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. - - $false Returns requests that were created with the Priority value Normal, Low, Lower or Lowest. You can't use this parameter with the Identity parameter. @@ -215,23 +209,14 @@ In Exchange 2016 CU7 or later, this parameter is the type MailboxLocationIdParam In Exchange 2016 CU6 or earlier, this parameter is the type MailboxOrMailUserIdParameter, so you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Identity parameter. @@ -304,23 +289,14 @@ Accept wildcard characters: False The Status parameter filters the results based on status. You can use the following values: - AutoSuspended - - Completed - - CompletedWithWarning - - CompletionInProgress - - Failed - - InProgress - - Queued - - Retrying - - Suspended - - Synced You can't use this parameter with the Identity parameter. @@ -362,9 +338,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -387,12 +361,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxExportRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md similarity index 86% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxExportRequestStatistics.md rename to exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md index c54f5a86b7..27ef9ad06f 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxExportRequestStatistics.md +++ b/exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxexportrequeststatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MailboxExportRequestStatistics @@ -17,35 +16,48 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MailboxExportRequestStatistics cmdlet to view detailed information about export requests. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Get-MailboxExportRequestStatistics [-Identity] [-DomainController ] - [-IncludeReport] [-Diagnostic] [-DiagnosticArgument ] [-DiagnosticInfo ] [-ReportOnly] [] +Get-MailboxExportRequestStatistics [-Identity] + [-DomainController ] + [-IncludeReport] + [-Diagnostic] + [-DiagnosticArgument ] + [-DiagnosticInfo ] + [-ReportOnly] + [] ``` ### MRSInstance ``` -Get-MailboxExportRequestStatistics -MRSInstance [-DomainController ] [-RequestGuid ] +Get-MailboxExportRequestStatistics -MRSInstance + [-DomainController ] + [-RequestGuid ] [] ``` ### MigrationRequestQueue ``` -Get-MailboxExportRequestStatistics -RequestQueue [-DomainController ] - [-IncludeReport] [-RequestGuid ] [-Diagnostic] [-DiagnosticArgument ] [-ReportOnly] +Get-MailboxExportRequestStatistics -RequestQueue + [-DomainController ] + [-IncludeReport] + [-RequestGuid ] + [-Diagnostic] + [-DiagnosticArgument ] + [-ReportOnly] [] ``` ## DESCRIPTION You can pipeline the Get-MailboxExportRequestStatistics cmdlet from the Get-MailboxExportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -94,7 +106,7 @@ This example returns additional information for all the export requests that hav ## PARAMETERS ### -Identity -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: \\\\. +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. @@ -112,7 +124,7 @@ Accept wildcard characters: False ``` ### -MRSInstance -This parameter is available or functional only in 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. @@ -137,9 +149,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -158,7 +168,9 @@ Accept wildcard characters: False ``` ### -Diagnostic -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -224,7 +236,7 @@ Accept wildcard characters: False ``` ### -IncludeReport -The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. +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 @@ -276,12 +288,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolder.md b/exchange/exchange-ps/exchange/Get-MailboxFolder.md similarity index 80% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolder.md rename to exchange/exchange-ps/exchange/Get-MailboxFolder.md index e781b6bb3a..3e9a4e5383 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolder.md +++ b/exchange/exchange-ps/exchange/Get-MailboxFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxFolder @@ -17,70 +16,109 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxFolder cmdlet to view folders in your own mailbox. Administrators can't use this cmdlet to view folders in other mailboxes (the cmdlet is available only from the MyBaseOptions user role). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### GetChildren ``` -Get-MailboxFolder [[-Identity] ] [-GetChildren] +Get-MailboxFolder [[-Identity] ] + [-GetChildren] [-DomainController ] [-MailFolderOnly] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ### Recurse ``` -Get-MailboxFolder [[-Identity] ] [-Recurse] +Get-MailboxFolder [[-Identity] ] + [-Recurse] [-DomainController ] [-MailFolderOnly] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ## DESCRIPTION This command checks that the mailbox specified in the Identity parameter is a valid Exchange mailbox before retrieving the requested folders. The cmdlet returns all folders if the MailFolderOnly switch isn't specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-MailboxFolder -Identity Tony:\Inbox +Get-MailboxFolder -Identity :\Inbox | Format List ``` -This example retrieves the Inbox folder in Tony's mailbox. The Identity parameter is supplied in the format of \:\. +This example returns detailed information about the Inbox folder in your own mailbox. ### Example 2 ```powershell -Get-MailboxFolder -Identity Tony +Get-MailboxFolder ``` -This example returns the root folders in Tony's mailbox. The Identity parameter is supplied in the format of \. +This example returns a summary list of the root folders in your own mailbox. ### Example 3 ```powershell -Get-MailboxFolder -Identity Tony -GetChildren -MailFolderOnly +Get-MailboxFolder -GetChildren -MailFolderOnly ``` -This example returns the first level of mail folders in Tony's mailbox. +This example returns the first level of mail folders in your own mailbox. ### Example 4 ```powershell -Get-MailboxFolder -Identity Tony:\Inbox -GetChildren +Get-MailboxFolder -Identity :\Inbox -GetChildren ``` -This example returns information about all the subfolders under Inbox in Tony's mailbox. +This example returns information about all the subfolders under Inbox in your own mailbox. ### Example 5 ```powershell -Get-MailboxFolder -Identity Tony:\Inbox -Recurse +Get-MailboxFolder -Identity :\Inbox -Recurse ``` -This example returns all levels of folders under Inbox in Tony's mailbox. +This example returns a summary list of all levels of folders under Inbox in your own mailbox. ## PARAMETERS +### -Identity +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. + +For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +If you don't specify the folder, the command returns information about folders in the root hierarchy of the specified mailbox. + +Example values for this parameter are `john@contoso.com:`, `John:\Inbox`. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -GetChildren 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. @@ -135,48 +173,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -If you don't specify the folder, the command returns information about folders in the root hierarchy of the specified mailbox. - -Example values for this parameter are `john@contoso.com:`, `John:\Inbox`. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -MailFolderOnly 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. @@ -214,12 +210,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md new file mode 100644 index 0000000000..1873b6abc7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md @@ -0,0 +1,236 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxFolderPermission + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MailboxFolderPermission cmdlet to view folder-level permissions in mailboxes. + +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxFolderPermission cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailboxFolderPermission [-Identity] + [-DomainController ] + [-GroupMailbox] + [-ResultSize ] + [-SkipCount ] + [-UseCustomRouting] + [-User ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports +``` + +This example returns the current list of user permissions for the Reports subfolder in the Marketing folder in John's mailbox. + +### Example 2 +```powershell +Get-MailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports -User Ayla@contoso.com +``` + +This example returns the permissions for the same folder in John's mailbox, but only for the user Ayla. + +### Example 3 +```powershell +Get-MailboxFolderPermission -Identity john@contoso.com:\Calendar -User Ayla@contoso.com +``` + +This example returns the permissions for the Calendar folder in John's mailbox, but only for the user Ayla. + +## PARAMETERS + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inbox\Reports`. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipCount +This parameter is available only in the cloud-based service. + +{{ Fill SkipCount Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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 + +[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission) + +[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission) + +[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission) + +[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission) diff --git a/exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md new file mode 100644 index 0000000000..8b201910e4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md @@ -0,0 +1,424 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxFolderStatistics + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MailboxFolderStatistics cmdlet to retrieve information about the folders in a specified mailbox, including the number and size of items in the folder, the folder name and ID, and other information. + +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxFolderStatistics cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Get-MailboxFolderStatistics [-Identity] + [-Archive] + [-DiagnosticInfo ] + [-DomainController ] + [-FolderScope ] + [-IncludeAnalysis] + [-IncludeOldestAndNewestItems] + [-IncludeSoftDeletedRecipients] + [-ResultSize ] + [-SkipCount ] + [-UseCustomRouting] + [] +``` + +### AuditLog +``` +Get-MailboxFolderStatistics [[-Identity] ] + [-AuditLog] + [-DiagnosticInfo ] + [-DomainController ] + [-FolderScope ] + [-IncludeAnalysis] + [-IncludeOldestAndNewestItems] + [-IncludeSoftDeletedRecipients] + [-ResultSize ] + [-SkipCount ] + [] +``` + +### Database +``` +Get-MailboxFolderStatistics -Database -StoreMailboxIdentity + [-DiagnosticInfo ] + [-FolderScope ] + [-IncludeAnalysis] + [-IncludeOldestAndNewestItems] + [-IncludeSoftDeletedRecipients] + [-ResultSize ] + [-SkipCount ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +A mailbox can have hidden items that are never visible to the user and are only used by applications. The Get-MailboxFolderStatistics cmdlet can return hidden items for the following values: FolderSize, FolderAndSubfolderSize, ItemsInFolder and ItemsInFolderAndSubfolders. + +The Get-MailboxFolderStatistics cmdlet shouldn't be confused with the Get-MailboxStatistics cmdlet. + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxFolderStatistics -Identity contoso\chris +``` + +This example doesn't specify the FolderScope parameter and retrieves all the information about the user Chris in the Contoso domain. + +### Example 2 +```powershell +Get-MailboxFolderStatistics -Identity Chris -FolderScope Calendar +``` + +This example uses the FolderScope parameter to view the statistics for calendar folders for the user Chris. + +### Example 3 +```powershell +Get-MailboxFolderStatistics -Identity Ayla@contoso.com -Archive +``` + +This example uses the Archive switch to view the statistics for Ayla's archive. + +### Example 4 +```powershell +Get-MailboxFolderStatistics -Identity "Tony" -FolderScope RecoverableItems -IncludeAnalysis +``` + +This example uses the IncludeAnalysis switch to view the statistics of Tony's Recoverable Items folder. + +### Example 5 +```powershell +$All = Get-Mailbox -ResultSize Unlimited + +$All | foreach {Get-MailboxFolderStatistics -Identity $_.Identity -FolderScope Inbox | Format-Table Identity,ItemsInFolderAndSubfolders,FolderAndSubfolderSize -AutoSize} +``` + +This example uses the FolderScope parameter to view inbox folders statistics for all mailboxes. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +```yaml +Type: GeneralMailboxOrMailUserIdParameter +Parameter Sets: AuditLog +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Database +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: DatabaseIdParameter +Parameter Sets: Database +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StoreMailboxIdentity +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: StoreMailboxIdParameter +Parameter Sets: Database +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Archive +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuditLog +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: AuditLog +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DiagnosticInfo +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Identity, AuditLog +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FolderScope +The FolderScope parameter specifies the scope of the search by folder type. Valid parameter values include: + +- All +- Archive: Exchange 2016 or later. +- Calendar +- Contacts +- ConversationHistory +- DeletedItems +- Drafts +- Inbox +- JunkEmail +- Journal +- LegacyArchiveJournals: Exchange 2013 or later. +- ManagedCustomFolder: Returns output for all managed custom folders. +- NonIpmRoot: Exchange 2013 or later. +- Notes +- Outbox +- Personal +- RecoverableItems: Returns output for the Recoverable Items folder and the Deletions, DiscoveryHolds, Purges, and Versions subfolders. +- RssSubscriptions +- SentItems +- SyncIssues +- Tasks + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAnalysis +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeOldestAndNewestItems +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedRecipients +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. + +Soft-deleted mailboxes are deleted mailboxes that are still recoverable. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipCount +This parameter is available only in the cloud-based service. + +{{ Fill SkipCount Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-MailboxIRMAccess.md b/exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md new file mode 100644 index 0000000000..ca07bcdfd7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md @@ -0,0 +1,121 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxIRMAccess + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MailboxIRMAccess cmdlet to view delegate access to IRM-protected messages in other mailboxes (shared mailboxes or user mailboxes where delegates have Full Access permission). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailboxIRMAccess [[-Identity] ] + [-User ] + [] +``` + +## DESCRIPTION +> [!NOTE] +> This cmdlet works only for delegates who 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). +> +> Delegates with Full Access permission to the mailbox who don't appear in the results of this cmdlet have access to IRM-protected messages. Only Full Access delegates who are blocked from reading IRM-protected messages in the mailbox appear in the results. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxIRMAccess -Identity lynette@contoso.onmicrosoft.com +``` + +This example returns information about delegate access to IRM-protected messages in Lynette's mailbox: + +- Full Access delegates who appear in the results are blocked from reading IRM-protected messages in the mailbox. +- Full Access delegates who don't appear in the results can read IRM-protected messages in the mailbox. + +### Example 2 +```powershell +Get-MailboxIRMAccess -Identity lynette@contoso.onmicrosoft.com -User chris@contoso.onmicrosoft.com +``` + +This example returns information about delegate Chris' access to IRM-protected messages in Lynette's mailbox. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -User +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxImportRequest.md b/exchange/exchange-ps/exchange/Get-MailboxImportRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxImportRequest.md rename to exchange/exchange-ps/exchange/Get-MailboxImportRequest.md index 985aab594b..63f31df6ff 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxImportRequest.md +++ b/exchange/exchange-ps/exchange/Get-MailboxImportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboximportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxImportRequest @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxImportRequest cmdlet to view the detailed status of an ongoing import request that was initiated using the New-MailboxImportRequest cmdlet. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-MailboxImportRequest [[-Identity] ] [-DomainController ] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ### MailboxFiltering @@ -42,7 +42,8 @@ Get-MailboxImportRequest [-ResultSize ] [-Status ] [-Suspend ] - [-RequestQueue ] [] + [-RequestQueue ] + [] ``` ### MailboxLocationFiltering @@ -57,13 +58,14 @@ Get-MailboxImportRequest [-ResultSize ] [-Status ] [-Suspend ] - [-RequestQueue ] [] + [-RequestQueue ] + [] ``` ## DESCRIPTION The search criteria for the Get-MailboxImportRequest cmdlet is a Boolean And statement. If you use multiple parameters, you narrow your search and reduce your search results. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -98,20 +100,15 @@ This example returns all import requests that have the name Recovered where the ## PARAMETERS ### -Identity -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: \\\\. Microsoft Exchange automatically precedes the request with the mailbox's alias. +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: - BatchName - - Mailbox - - Name - - Status - - Suspend - - HighPriority ```yaml @@ -146,14 +143,12 @@ Accept wildcard characters: False ``` ### -Database -This parameter is available or functional only in 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -195,7 +190,6 @@ 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: - $true Returns requests that were created with the Priority value High, Higher, Highest or Emergency. - - $false Returns requests that were created with the Priority value Normal, Low, Lower or Lowest. You can't use this parameter with the Identity parameter. @@ -214,6 +208,8 @@ Accept wildcard characters: False ``` ### -Mailbox +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. 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. @@ -221,23 +217,14 @@ In Exchange 2016 CU7 or later, this parameter is the type MailboxLocationIdParam In Exchange 2016 CU6 or earlier, this parameter is the type MailboxOrMailUserIdParameter, so you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Identity parameter. @@ -259,7 +246,7 @@ Accept wildcard characters: False Type: MailboxLocationIdParameter Parameter Sets: MailboxLocationFiltering Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -308,23 +295,14 @@ Accept wildcard characters: False The Status parameter filters the results based on status. You can use the following values: - AutoSuspended - - Completed - - CompletedWithWarning - - CompletionInProgress - - Failed - - InProgress - - Queued - - Retrying - - Suspended - - Synced You can't use this parameter with the Identity parameter. @@ -368,9 +346,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -393,12 +369,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxImportRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md similarity index 86% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxImportRequestStatistics.md rename to exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md index 64f7a84d22..5803c36890 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxImportRequestStatistics.md +++ b/exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboximportrequeststatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxImportRequestStatistics @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxImportRequestStatistics cmdlet to view detailed information about import requests. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,6 +38,7 @@ Get-MailboxImportRequestStatistics [-Identity] Get-MailboxImportRequestStatistics [-Identity] [-DiagnosticInfo ] [-IncludeReport] + [-IncludeSkippedItems] [-ReportOnly] [] ``` @@ -66,7 +66,7 @@ Get-MailboxImportRequestStatistics -RequestQueue ## DESCRIPTION You can pipeline the Get-MailboxImportRequestStatistics cmdlet from the Get-MailboxImportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -108,7 +108,9 @@ This example returns additional information for all the import requests that hav ## PARAMETERS ### -Identity -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: \\\\. +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. ```yaml Type: MailboxImportRequestIdParameter @@ -124,7 +126,7 @@ Accept wildcard characters: False ``` ### -MRSInstance -This parameter is available or functional only in 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. @@ -151,9 +153,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -174,7 +174,9 @@ Accept wildcard characters: False ### -Diagnostic This parameter is available only in on-premises Exchange. -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -244,7 +246,7 @@ Accept wildcard characters: False ``` ### -IncludeReport -The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. +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 @@ -259,6 +261,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IncludeSkippedItems +This parameter is available only in the cloud-based service. + +{{ Fill IncludeSkippedItems Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: IdentityCloud +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RequestGuid This parameter is available only in on-premises Exchange. @@ -300,12 +320,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md new file mode 100644 index 0000000000..bc4b367757 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md @@ -0,0 +1,185 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxJunkEmailConfiguration + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MailboxJunkEmailConfiguration cmdlet to view the junk email settings on mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailboxJunkEmailConfiguration [-Identity] + [-Credential ] + [-DomainController ] + [-ReadFromDomainController] + [-ResultSize ] + [] +``` + +## DESCRIPTION +The junk email settings on the mailbox are: + +- Enable or disable the junk email rule: In on-premises Exchange, the junk email rule (a hidden Inbox rule named Junk E-mail Rule) controls the delivery of messages to the Junk Email folder or the Inbox based on the SCL Junk Email Folder threshold (for the organization or the mailbox) and the safelist collection on the mailbox. + + In the cloud-based service, the junk email rule has no effect on mail flow. Exchange Online Protection delivers messages to the Junk Email folder based on the actions set in anti-spam policies. The junk email rule on the mailbox still controls what happens to messages after delivery based on the safelist collection of the mailbox. + + Users can enable or disable the junk email rule in their own mailbox by using Outlook on the web. + +- Configure the safelist collection: The safelist collection is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list. Users can configure the safelist collection on their own mailbox by using Microsoft Outlook or Outlook on the web. + +Administrators can enable or disable the junk email rule, and configure the safelist collection on a mailbox by using the Set-MailboxJunkEmailConfiguration cmdlet. For more information, see [Configure Exchange antispam settings on mailboxes](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxJunkEmailConfiguration -Identity "David Pelton" +``` + +This example returns the junk email configuration for the user named David Pelton. + +### Example 2 +```powershell +$AllUsers = Get-Mailbox -ResultSize unlimited -RecipientTypeDetails UserMailbox + +$AllUsers | foreach {Get-MailboxJunkEmailConfiguration -Identity $_.UserPrincipalName} | Where {$_.Enabled -eq $false} | Format-Table -Auto Identity,Enabled +``` + +This example returns a summary list of all mailboxes in your organization where the junk email rule is disabled. The first command stores all user mailboxes in a variable. The second command parses through the mailboxes and returns the FQDN of the mailboxes where the junk email rule is disabled. + +To return all mailboxes where the junk email rule is enabled, change the value $false to $true. To return a mixed list of mailboxes where the junk email rule is enabled and disabled, remove the "| Where {$\_.Enabled -eq $false " part of the second command. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can use the wildcard character (\*) to identify multiple mailboxes. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: True +``` + +### -Credential +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +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 +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Get-MailboxLocation.md b/exchange/exchange-ps/exchange/Get-MailboxLocation.md similarity index 82% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxLocation.md rename to exchange/exchange-ps/exchange/Get-MailboxLocation.md index b36bc7ccc8..ea42b8a024 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxLocation.md +++ b/exchange/exchange-ps/exchange/Get-MailboxLocation.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxlocation -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-MailboxLocation @@ -17,10 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxLocation cmdlet to view mailbox location information in Exchange Online. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,7 +26,8 @@ Get-MailboxLocation -Database [-Confirm] [-MailboxLocationType ] [-ResultSize ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity @@ -39,20 +36,23 @@ Get-MailboxLocation -Identity [-Confirm] [-MailboxLocationType ] [-ResultSize ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### User ``` -Get-MailboxLocation -User [-IncludePreviousPrimary] +Get-MailboxLocation -User + [-IncludePreviousPrimary] [-Confirm] [-MailboxLocationType ] [-ResultSize ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,7 +68,7 @@ In Exchange Online, this example returns the mailbox location information for th Get-MailboxLocation -Identity e15664af-82ed-4635-b02a-df7c2e03d950 ``` -In Exchange Server or Exchange Online, this example returns the mailbox location information for the specified mailbox GUID (the ExchangeGuid property value from the results of Get-Mailbox -Identity \ | Format-List ExchangeGuid). +In Exchange Server or Exchange Online, this example returns the mailbox location information for the specified mailbox GUID (the ExchangeGuid property value from the results of `Get-Mailbox -Identity | Format-List ExchangeGuid`). ## PARAMETERS @@ -78,9 +78,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -101,13 +99,12 @@ Accept wildcard characters: False ### -Identity The Identity parameter specifies the mailbox location object that you want to view. The value uses the either of the following formats: -- \\\\ - -- \ +- TenantGUID\\MailboxGUID +- MailboxGUID -In Exchange Server or Exchange Online, you can run the following command to find and compare the \ values for the user: Get-Mailbox -Identity \ \| Format-List *GUID,MailboxLocations. +In Exchange Server or Exchange Online, you can run the following command to find and compare the MailboxGUID values for the user: `Get-Mailbox -Identity | Format-List *GUID,MailboxLocations`. -In Exchange Online, you can find the \ and \ values after you run Get-MailboxLocation with the User parameter. +In Exchange Online, you can find the TenantGUID and MailboxGUID values after you run Get-MailboxLocation with the User parameter. You can't use this parameter with the User parameter. @@ -130,11 +127,8 @@ 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: - Name - - Distinguished name (DN) - - Canonical DN - - GUID You can't use this parameter with the Identity parameter. @@ -155,8 +149,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -196,17 +189,11 @@ Accept wildcard characters: False The MailboxLocationType filters the results by the type of mailbox. Valid values are: - Aggregated - - AuxArchive - - AuxPrimary - - ComponentShared - - MainArchive - - PreviousPrimary (Exchange Online only) - - Primary ```yaml @@ -259,12 +246,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md new file mode 100644 index 0000000000..fff93d6e2a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md @@ -0,0 +1,210 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxMessageConfiguration + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MailboxMessageConfiguration cmdlet to view the Outlook on the web settings that are applied to specific mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailboxMessageConfiguration [-Identity] + [-Credential ] + [-DomainController ] + [-ReadFromDomainController] + [-ResultSize ] + [-SignatureName ] + [-UseCustomRouting] + [] +``` + +## DESCRIPTION +The Get-MailboxMessageConfiguration cmdlet shows Outlook on the web settings for the specified mailbox. These settings are not used in Microsoft Outlook, Microsoft Exchange ActiveSync, or other email clients. These settings are applied in Outlook on the web only. Settings that contain the word Mobile are applied in Microsoft Outlook on the web for devices only. + +> [!NOTE] +> The SignatureHtml and SignatureText parameters don't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Currently, the only way to make these parameters work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxMessageConfiguration tony@contoso.com +``` + +This example returns the Outlook on the web settings for Tony's mailbox. + +### Example 2 +```powershell +Get-MailboxMessageConfiguration tony@contoso.com -DomainController DC1 +``` + +This example returns the Outlook on the web settings for Tony's mailbox and specifies the domain controller that's used to get those settings. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +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 +``` + +### -SignatureName +This parameter is available only in the cloud-based service. + +{{ Fill SignatureName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-MailboxPermission.md b/exchange/exchange-ps/exchange/Get-MailboxPermission.md new file mode 100644 index 0000000000..80fc4e6f73 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxPermission.md @@ -0,0 +1,383 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxPermission + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MailboxPermission cmdlet to retrieve permissions on a mailbox. + +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxPermission cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Owner +``` +Get-MailboxPermission [-Identity] [-Owner] + [-Credential ] + [-DomainController ] + [-GroupMailbox] + [-IncludeUserWithDisplayName] + [-ReadFromDomainController] + [-ResultSize ] + [-UseCustomRouting] + [] +``` + +### AccessRights +``` +Get-MailboxPermission [-Identity] [-User ] [-SoftDeletedMailbox] + [-Credential ] + [-DomainController ] + [-GroupMailbox] + [-IncludeSoftDeletedUserPermissions] + [-IncludeUnresolvedPermissions] + [-IncludeUserWithDisplayName] + [-ReadFromDomainController] + [-ResultSize ] + [-UseCustomRouting] + [] +``` + +## DESCRIPTION +The output of this cmdlet shows the following information: + +- Identity: The mailbox in question. +- User: The security principal (user, security group, Exchange management role group, etc.) that has permission to the mailbox. +- AccessRights: The permission that the security principal has on the mailbox. The available values are ChangeOwner (change the owner of the mailbox), ChangePermission (change the permissions on the mailbox), DeleteItem (delete the mailbox), ExternalAccount (indicates the account isn't in the same domain), FullAccess (open the mailbox, access its contents, but can't send mail) and ReadPermission (read the permissions on the mailbox). Whether the permissions are allowed or denied is indicated in the Deny column. +- IsInherited: Whether the permission is inherited (True) or directly assigned to the mailbox (False). Permissions are inherited from the mailbox database and/or Active Directory. Typically, directly assigned permissions override inherited permissions. +- Deny: Whether the permission is allowed (False) or denied (True). Typically, deny permissions override allow permissions. + +By default, the following permissions are assigned to user mailboxes: + +- FullAccess and ReadPermission are directly assigned to NT AUTHORITY\\SELF. This entry gives a user permission to their own mailbox. +- FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes. +- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. +- FullAccess is inherited by NT AUTHORITY\\SYSTEM and ReadPermission is inherited by NT AUTHORITY\\NETWORK. +- FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers. + +By default, other security groups and role groups inherit permissions to mailboxes based on their location (on-premises Exchange or Microsoft 365). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxPermission -Identity john@contoso.com | Format-List +``` + +This example returns permissions on the mailbox by its SMTP address john@contoso.com. + +### Example 2 +```powershell +Get-MailboxPermission -Identity john@contoso.com -User "Ayla" +``` + +This example returns permissions that the user Ayla has on John's mailbox. + +### Example 3 +```powershell +Get-MailboxPermission -Identity Room222 -Owner +``` + +This example returns the owner information for the resource mailbox Room222. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedUserPermissions +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. + +Soft-deleted mailboxes are mailboxes that have been deleted, but are still recoverable. + +```yaml +Type: SwitchParameter +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeUnresolvedPermissions +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. + +```yaml +Type: SwitchParameter +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeUserWithDisplayName +This parameter is available only in the cloud-based service. + +{{ Fill IncludeUserWithDisplayName Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Owner +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +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 +``` + +### -SoftDeletedMailbox +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. + +Soft-deleted mailboxes are deleted mailboxes that are still recoverable. + +```yaml +Type: SwitchParameter +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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 +- Mail users +- Security groups + +For the best results, we recommend using the following values: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Owner switch. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Get-MailboxPlan.md b/exchange/exchange-ps/exchange/Get-MailboxPlan.md similarity index 78% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxPlan.md rename to exchange/exchange-ps/exchange/Get-MailboxPlan.md index 5649e65d87..c1a6bb560a 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxPlan.md +++ b/exchange/exchange-ps/exchange/Get-MailboxPlan.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxplan +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxplan applicable: Exchange Online title: Get-MailboxPlan schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-MailboxPlan @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Get-MailboxPlan cmdlet to view information about mailbox plans in the cloud-based service. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,7 +26,6 @@ Get-MailboxPlan [[-Identity] ] [-Credential ] [-Filter ] [-IgnoreDefaultScope] - [-OrganizationalUnit ] [-ResultSize ] [-SortBy ] [] @@ -39,7 +34,7 @@ Get-MailboxPlan [[-Identity] ] ## DESCRIPTION A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,13 +58,9 @@ This example returns detailed information for the mailbox plan that has the disp 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 - - Alias - - Display name - - Distinguished name (DN) - - GUID ```yaml @@ -106,7 +97,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -122,19 +113,16 @@ Accept wildcard characters: False ``` ### -Filter -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. +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'"`. -- Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -165,22 +153,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OrganizationalUnit -This parameter is reserved for internal Microsoft use. - -```yaml -Type: OrganizationalUnitIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ResultSize The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. @@ -200,14 +172,12 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following attributes: - Alias - - DisplayName - - Name ```yaml @@ -228,12 +198,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md new file mode 100644 index 0000000000..0915467f52 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md @@ -0,0 +1,227 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailboxRegionalConfiguration + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MailboxRegionalConfiguration cmdlet to view the regional settings of a mailbox. You can view the date format, time format, time zone, and language of the mailbox. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Get-MailboxRegionalConfiguration [-Identity] [-DomainController ] + [-VerifyDefaultFolderNameLanguage] + [] +``` + +### Identity +``` +Get-MailboxRegionalConfiguration [[-Identity] ] [-Archive] [-UseCustomRouting] + [-VerifyDefaultFolderNameLanguage] + [] +``` + +### MailboxLocation +``` +Get-MailboxRegionalConfiguration [-MailboxLocation ] [-UseCustomRouting] + [-VerifyDefaultFolderNameLanguage] + [] +``` + +## DESCRIPTION +To modify the regional settings of a mailbox, use the [Set-MailboxRegionalConfiguration](https://learn.microsoft.com/powershell/module/exchange/set-mailboxregionalconfiguration) cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxRegionalConfiguration -Identity "Marcelo Teixeira" +``` + +This example returns the regional settings for Marcelo Teixeira's mailbox. + +### Example 2 +```powershell +Get-MailboxRegionalConfiguration -Identity "Ella Lack" -DomainController dc01.contoso.com +``` + +In on-premises Exchange, this example returns the regional settings for Ella Lack's mailbox by using the specified domain controller. + +### Example 3 +```powershell +Get-MailboxRegionalConfiguration -Identity "Alice Jakobsen" -VerifyDefaultFolderNameLanguage | Format-List +``` + +This example returns the regional settings for Alice Jakobsen's mailbox and also indicates whether the default folder names of the mailbox are localized in the locale that's specified for the mailbox. The important properties are Language and DefaultFolderNameMatchingUserLanguage. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: 1 +Default value: None +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 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Archive +This parameter is available only in the cloud-based service. + +{{ Fill Archive Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxLocation +This parameter is available only in the cloud-based service. + +{{ Fill MailboxLocation Description }} + +```yaml +Type: MailboxLocationIdParameter +Parameter Sets: MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VerifyDefaultFolderNameLanguage +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: + +- `Get-MailboxRegionalConfiguration -Identity -VerifyDefaultFolderNameLanguage | Format-List` + +Or + +- `Get-MailboxRegionalConfiguration -Identity -VerifyDefaultFolderNameLanguage | Format-Table Language,DefaultFolderNameMatchingUserLanguage` + +If you view the DefaultFolderNameMatchingUserLanguage property without using the VerifyDefaultFolderNameLanguage switch, the value is always $false, even if the default folder names are localized in the language that's specified for the mailbox. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailbox-databases-and-servers/Get-MailboxRepairRequest.md b/exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md similarity index 81% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxRepairRequest.md rename to exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md index 43075fb799..d247baf12a 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxRepairRequest.md +++ b/exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/get-mailboxrepairrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MailboxRepairRequest @@ -17,50 +16,50 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MailboxRepairRequest cmdlet to display information about current mailbox repair requests. Mailbox repair requests are created using the New-MailboxRepairRequest cmdlet to detect and fix mailbox corruptions. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Database ``` Get-MailboxRepairRequest [-Database] [[-StoreMailbox] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ### Identity ``` Get-MailboxRepairRequest [-Identity] [-Detailed] - [-DomainController ] [] + [-DomainController ] + [] ``` ### Mailbox ``` Get-MailboxRepairRequest [-Mailbox] [-Archive] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION The Get-MailboxRepairRequest cmdlet displays information about mailbox repair requests. This information includes: - The mailbox GUID. - - The type of corruption that was specified when the mailbox repair request was created. - - The progress of the repair request in percentage of completion. - - The number of corruptions detected and fixed. - - The status of the repair request; values are Queued, Running, Succeeded and Failed. - - The date and time when the mailbox repair request was created and when it finished. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-MailboxDatabase | Get-MailboxRepairRequest | Format-Table Identity; Get-MailboxRepairRequest -Identity 5b8ca3fa-8227-427f-af04-9b4f206d611f\335c2b06-321d-4e73-b2f7-3dc2b02d0df5\374289de-b899-42dc-8391-4f8579935f1f | Format-List +Get-MailboxDatabase | Get-MailboxRepairRequest | Format-Table Identity + +Get-MailboxRepairRequest -Identity 5b8ca3fa-8227-427f-af04-9b4f206d611f\335c2b06-321d-4e73-b2f7-3dc2b02d0df5\374289de-b899-42dc-8391-4f8579935f1f | Format-List ``` This example displays the value of the Identity property for all mailbox repair requests for all mailbox servers in your organization; the second command displays information about a specific mailbox repair request that was returned by the first command. @@ -74,27 +73,23 @@ This example displays repair request information for the mailbox of Ann Beebe us ### Example 3 ```powershell -$MailboxGuid = Get-MailboxStatistics annb; Get-MailboxRepairRequest -Database $MailboxGuid.Database -StoreMailbox $MailboxGuid.MailboxGuid | Format-List Identity +$MailboxGuid = Get-MailboxStatistics annb + +Get-MailboxRepairRequest -Database $MailboxGuid.Database -StoreMailbox $MailboxGuid.MailboxGuid | Format-List Identity ``` This example uses the Database and StoreMailbox parameters to display the Identity property of the repair request for the mailbox of Ann Beebe. ## PARAMETERS -### -Database -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 - -- Distinguished name (DN) - -- GUID +### -Identity +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 Mailbox parameter. +You can't use this parameter with the Database or Mailbox parameters. ```yaml -Type: DatabaseIdParameter -Parameter Sets: Database +Type: StoreIntegrityCheckJobIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -105,12 +100,18 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 \\\\\\\. +### -Database +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 +- Distinguished name (DN) +- GUID + +You can't use this parameter with the Identity or Mailbox parameters. ```yaml -Type: StoreIntegrityCheckJobIdParameter -Parameter Sets: Identity +Type: DatabaseIdParameter +Parameter Sets: Database Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -125,26 +126,17 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -You can't use this parameter with the Database parameter. +You can't use this parameter with the Database or Identity parameters. ```yaml Type: MailboxIdParameter @@ -159,10 +151,30 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -StoreMailbox +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. + +```yaml +Type: StoreMailboxIdParameter +Parameter Sets: Database +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 2 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Archive -If the associated archive mailbox was included when the mailbox repair request was created, use the Archive parameter to display information about the archive mailbox. If you don't specify this parameter, only information about the primary mailbox is returned. +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. -You can't use this parameter with the Database parameter. +If you don't use this switch, only information about the primary mailbox is returned. + +You can't use this switch with the Database parameter. ```yaml Type: SwitchParameter @@ -178,7 +190,7 @@ Accept wildcard characters: False ``` ### -Detailed -Use the Detailed parameter to display mailbox-level repair tasks associated with the repair request. +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 @@ -209,35 +221,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -StoreMailbox -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. - -```yaml -Type: StoreMailboxIdParameter -Parameter Sets: Database -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxRestoreRequest.md rename to exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md index 34ad7149c7..307c4af120 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxrestorerequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxRestoreRequest @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxRestoreRequest cmdlet to view detailed status of an ongoing restore request that was initiated by using the New-MailboxRestoreRequest cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,27 +24,37 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-MailboxRestoreRequest [[-Identity] ] [-DomainController ] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ### Filtering ``` -Get-MailboxRestoreRequest [-BatchName ] [-HighPriority ] [-Name ] [-RequestQueue ] [-SourceDatabase ] [-Status ] [-Suspend ] [-TargetDatabase ] [-TargetMailbox ] +Get-MailboxRestoreRequest [-BatchName ] + [-HighPriority ] + [-Name ] + [-RequestQueue ] + [-SourceDatabase ] + [-Status ] + [-Suspend ] + [-TargetDatabase ] + [-TargetMailbox ] [-DomainController ] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-MailboxRestoreRequest -Identity "ayla\MailboxRestore" +Get-MailboxRestoreRequest -Identity "Ayla\MailboxRestore" ``` -This example returns the status of the in-progress and queued restore request with the identity ayla\\MailboxRestore. +This example returns the status of the in-progress and queued restore request with the identity ayla\\MailboxRestore, where Ayla is the first name of the user. ### Example 2 ```powershell @@ -71,7 +80,7 @@ This example returns all restore requests that have the name RestoreToMBD01 wher ## PARAMETERS ### -Identity -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: \\\\. +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). @@ -130,7 +139,6 @@ Accept wildcard characters: False 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. - - $false Returns requests that were created with the Priority value Normal, Low, Lower or Lowest. You can't use this parameter with the Identity parameter. @@ -176,9 +184,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -218,9 +224,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -242,23 +246,14 @@ Accept wildcard characters: False The Status parameter filters the results based on status. You can use the following values: - AutoSuspended - - Completed - - CompletedWithWarning - - CompletionInProgress - - Failed - - InProgress - - Queued - - Retrying - - Suspended - - Synced You can't use this parameter with the Identity parameter. @@ -295,14 +290,12 @@ Accept wildcard characters: False ``` ### -TargetDatabase -This parameter is available or functional only in 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -324,17 +317,11 @@ Accept wildcard characters: False The TargetMailbox parameter specifies the identity of the target mailbox. You can use the following values: - GUID - - Distinguished name (DN) - - Domain\\Account - - User principal name (UPN) - - Legacy Exchange DN - - SMTP address - - Alias You can't use this parameter with the Identity parameter. @@ -357,12 +344,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxRestoreRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md similarity index 90% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxRestoreRequestStatistics.md rename to exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md index 5873ec845e..08a0693b85 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxRestoreRequestStatistics.md +++ b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxrestorerequeststatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxRestoreRequestStatistics @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxRestoreRequestStatistics cmdlet to view detailed information about restore requests. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -36,6 +35,7 @@ Get-MailboxRestoreRequestStatistics [-Identity] [-IncludeReport] + [-IncludeSkippedItems] [-DiagnosticInfo ] [-ReportOnly] [] @@ -62,7 +62,7 @@ Get-MailboxRestoreRequestStatistics -RequestQueue ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -104,7 +104,7 @@ This example returns additional information for all the restore requests that ha ## PARAMETERS ### -Identity -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: \\\\. +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). @@ -124,7 +124,7 @@ Accept wildcard characters: False ``` ### -MRSInstance -This parameter is available or functional only in 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. @@ -151,9 +151,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -172,7 +170,7 @@ Accept wildcard characters: False ``` ### -IncludeReport -The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. +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 @@ -208,7 +206,9 @@ Accept wildcard characters: False ### -Diagnostic This parameter is available only in on-premises Exchange. -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -277,6 +277,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IncludeSkippedItems +This parameter is available only in the cloud-based service. + +{{ Fill IncludeSkippedItems Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: IdentityCloud +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ReportOnly 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. @@ -298,12 +316,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-MailboxSearch.md b/exchange/exchange-ps/exchange/Get-MailboxSearch.md similarity index 83% rename from exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-MailboxSearch.md rename to exchange/exchange-ps/exchange/Get-MailboxSearch.md index 5eada835ed..3051b480ef 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-MailboxSearch.md +++ b/exchange/exchange-ps/exchange/Get-MailboxSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/get-mailboxsearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxSearch @@ -17,7 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxSearch cmdlet to view mailbox searches that are in progress, complete or stopped. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +**Note**: As of October 2020, the \*-MailboxSearch cmdlets are retired in Exchange Online PowerShell. Use the \*-ComplianceSearch cmdlets in Security & Compliance PowerShell instead. For more information, see [Retirement of legacy eDiscovery tools](https://learn.microsoft.com/purview/ediscovery-legacy-retirement). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,7 +32,8 @@ Get-MailboxSearch [[-Identity] ] ### EwsStoreObjectIdentity ``` -Get-MailboxSearch [[-Identity] ] [-ShowDeletionInProgressSearches] +Get-MailboxSearch [[-Identity] ] + [-ShowDeletionInProgressSearches] [-DomainController ] [-ResultSize ] [] @@ -39,16 +41,17 @@ Get-MailboxSearch [[-Identity] ] [-ShowDeletionInProg ### InPlaceHoldIdentity ``` -Get-MailboxSearch -InPlaceHoldIdentity [-ShowDeletionInProgressSearches] +Get-MailboxSearch -InPlaceHoldIdentity + [-ShowDeletionInProgressSearches] [-DomainController ] [-ResultSize ] [] ``` ## DESCRIPTION -In on-premises Exchange and Exchange Online, a mailbox search is used to perform an In-Place eDiscovery or to place users on an In-Place Hold. Use the Get-MailboxSearch cmdlet to retrieve details of either type of mailbox search. +In on-premises Exchange, a mailbox search is used to perform an In-Place eDiscovery or to place users on an In-Place Hold. Use the Get-MailboxSearch cmdlet to retrieve details of either type of mailbox search. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -66,66 +69,29 @@ Get-MailboxSearch "Project Hamilton" | Format-List This example retrieves all properties for the mailbox search Project Hamilton. -The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). +The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). ### Example 3 ```powershell -(Get-Mailbox Mark).InPlaceHolds; Get-MailboxSearch -InPlaceHoldIdentity 9953d0f0fd03415e949d4b41c5a28cbb +(Get-Mailbox Mark).InPlaceHolds + +Get-MailboxSearch -InPlaceHoldIdentity 9953d0f0fd03415e949d4b41c5a28cbb ``` This example retrieves the In-Place Holds that a user is placed on. The first command outputs GUIDs of In-Place Holds. The last command retrieves a mailbox search based on the GUID of the In-Place Hold that the user is placed on. ## PARAMETERS -### -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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: - SourceMailboxes - - Sources - - SearchQuery - - ResultsLink - - PreviewResultsLink - - Errors To view these properties, you have to provide the name of a mailbox search. @@ -156,6 +122,40 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -InPlaceHoldIdentity +The InPlaceHoldIdentity parameter specifies the GUID of an In-Place Hold. Use this parameter to search for an In-Place Hold that a user is placed on. GUIDs of all In-Place Holds that a user is placed on are added to the user's InPlaceHolds property. You can retrieve the property by using the Get-Mailbox cmdlet. + +```yaml +Type: String +Parameter Sets: InPlaceHoldIdentity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -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. @@ -193,12 +193,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md similarity index 86% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxSentItemsConfiguration.md rename to exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md index c3931e8afb..0db5f4e4f3 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxSentItemsConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxsentitemsconfiguration +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxsentitemsconfiguration applicable: Exchange Server 2010 title: Get-MailboxSentItemsConfiguration schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Get-MailboxSentItemsConfiguration @@ -17,19 +16,20 @@ This cmdlet is available only in Exchange Server 2010. Use the Get-MailboxSentItemsConfiguration cmdlet to view the Sent Items settings on mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailboxSentItemsConfiguration [-DomainController ] [-Identity ] +Get-MailboxSentItemsConfiguration [-DomainController ] + [-Identity ] [] ``` ## DESCRIPTION By default, when you use Send As or Send On Behalf Of to send a message from another mailbox, the message is saved in your Sent Items folder (not in the Sent Items folder of the source mailbox). In Microsoft Exchange Server 2010 Service Pack 3 (SP3), you can save copies messages in the Sent Items folder of the sender and the source mailbox. For example, consider a shared mailbox that receives customer feedback and is monitored by multiple users. When someone responds to a message in the shared mailbox, you can save the message in the Sent Items folder of the shared mailbox and the sender's mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,23 +62,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -99,12 +90,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxServer.md b/exchange/exchange-ps/exchange/Get-MailboxServer.md similarity index 88% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxServer.md rename to exchange/exchange-ps/exchange/Get-MailboxServer.md index 91c9b05d85..7b2886ee8a 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-MailboxServer.md +++ b/exchange/exchange-ps/exchange/Get-MailboxServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/get-mailboxserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MailboxServer @@ -17,19 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MailboxServer cmdlet to view information about Mailbox servers in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailboxServer [[-Identity] ] [-DomainController ] [-Status] +Get-MailboxServer [[-Identity] ] + [-DomainController ] + [-Status] [] ``` ## DESCRIPTION The ExchangeVersion attribute returned is the minimum version of Microsoft Exchange that you can use to manage the returned object. This attribute isn't the same as the version of Microsoft Exchange that's displayed in the Exchange admin center when you select Server Configuration. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,41 +50,39 @@ This example returns detailed information about the Mailbox server named Server1 ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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 +- GUID +- Distinguished name (DN) ```yaml -Type: Fqdn +Type: MailboxServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- GUID - -- Distinguished name (DN) +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: MailboxServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -110,12 +109,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Get-MailboxSpellingConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md similarity index 90% rename from exchange/exchange-ps/exchange/client-access/Get-MailboxSpellingConfiguration.md rename to exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md index ee5d83b3a6..711e199b87 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-MailboxSpellingConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-mailboxspellingconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxSpellingConfiguration @@ -17,12 +16,13 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxSpellingConfiguration cmdlet to retrieve the Outlook on the web spelling checker settings of a specified user. For example, users can set their dictionary language and configure the spelling checker to ignore mixed digits and words in all uppercase. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailboxSpellingConfiguration [-Identity] [-DomainController ] +Get-MailboxSpellingConfiguration [-Identity] + [-DomainController ] [] ``` @@ -30,14 +30,11 @@ Get-MailboxSpellingConfiguration [-Identity] [-DomainContro The Get-MailboxSpellingConfiguration cmdlet is primarily used to populate the spelling checker settings for end users in Outlook on the web. Administrators can also view users' settings by running this cmdlet. The following spelling checker settings are retrieved by the cmdlet for the specified mailbox: - Identity: This setting specifies the mailbox identity. - - CheckBeforeSend: This setting specifies whether Outlook on the web checks the spelling of every message when the user clicks Send in the new message form. - - DictionaryLanguage: This setting specifies the dictionary language used when the spelling checker checks the spelling in messages. - - IgnoreMixedDigits: This setting specifies whether the spelling checker ignores words that contain numbers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,23 +65,14 @@ This example returns the Outlook on the web spelling checker options for Tony's The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -123,12 +111,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxStatistics.md similarity index 83% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxStatistics.md rename to exchange/exchange-ps/exchange/Get-MailboxStatistics.md index 18bc863d95..364729d637 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxStatistics.md +++ b/exchange/exchange-ps/exchange/Get-MailboxStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxstatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxStatistics @@ -17,10 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxStatistics cmdlet to return information about a mailbox, such as the size of the mailbox, the number of messages it contains, and the last time it was accessed. In addition, you can get the move history or a move report of a completed move request. -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxStatistics cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxStatistics cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,12 +31,14 @@ Get-MailboxStatistics -Database [[-StoreMailboxIdentity] < [-IncludeMoveHistory] [-IncludeMoveReport] [-IncludeQuarantineDetails] - [-NoADLookup] [] + [-NoADLookup] + [] ``` ### Identity ``` -Get-MailboxStatistics [-Identity] [-Archive] +Get-MailboxStatistics [-Identity] + [-Archive] [-CopyOnServer ] [-DomainController ] [-IncludeMoveHistory] @@ -46,6 +46,7 @@ Get-MailboxStatistics [-Identity] [-Archiv [-IncludeQuarantineDetails] [-IncludeSoftDeletedRecipients] [-NoADLookup] + [-UseCustomRouting] [] ``` @@ -58,7 +59,8 @@ Get-MailboxStatistics -Server [-IncludeMoveReport] [-IncludePassive] [-IncludeQuarantineDetails] - [-NoADLookup] [] + [-NoADLookup] + [] ``` ## DESCRIPTION @@ -70,7 +72,9 @@ You can use the Get-MailboxStatistics cmdlet to return detailed move history and You can only see move reports and move history for completed move requests. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +**Note**: We're deprecating the LastUserActionTime property in Exchange Online PowerShell. Don't use the value of that property as the last active time for a mailbox. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -125,14 +129,18 @@ This example returns the summary move history for the completed move request for ### Example 8 ```powershell -$temp=Get-MailboxStatistics -Identity AylaKol -IncludeMoveHistory; $temp.MoveHistory[0] +$temp=Get-MailboxStatistics -Identity AylaKol -IncludeMoveHistory + +$temp.MoveHistory[0] ``` This example returns the detailed move history for the completed move request for Ayla Kol's mailbox. This example uses a temporary variable to store the mailbox statistics object. If the mailbox has been moved multiple times, there are multiple move reports. The last move report is always MoveReport[0]. ### Example 9 ```powershell -$temp=Get-MailboxStatistics -Identity AylaKol -IncludeMoveReport; $temp.MoveHistory[0] | Export-CSV C:\MoveReport_AylaKol.csv +$temp=Get-MailboxStatistics -Identity AylaKol -IncludeMoveReport + +$temp.MoveHistory[0] | Export-CSV C:\MoveReport_AylaKol.csv ``` This example returns the detailed move history and a verbose detailed move report for Ayla Kol's mailbox. This example uses a temporary variable to store the move request statistics object and outputs the move report to a CSV file. @@ -143,23 +151,14 @@ This example returns the detailed move history and a verbose detailed move repor 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -175,8 +174,31 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -StoreMailboxIdentity +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: + +- MailboxGuid +- LegacyDN + +Use this syntax to retrieve information about disconnected mailboxes, which don't have a corresponding Active Directory object or that has a corresponding Active Directory object that doesn't point to the disconnected mailbox in the mailbox database. + +```yaml +Type: StoreMailboxIdParameter +Parameter Sets: Database +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Archive -The Archive switch parameter 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. +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 @@ -199,16 +221,12 @@ The CopyOnServer parameter is used to retrieve statistics from a specific databa You can use any value that uniquely identifies the server. For example: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. - ```yaml Type: ServerIdParameter Parameter Sets: Database, Identity @@ -228,9 +246,7 @@ 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: - Name - - Distinguished name (DN) - - GUID This parameter accepts pipeline input from the Get-MailboxDatabase cmdlet. @@ -269,19 +285,16 @@ Accept wildcard characters: False ### -Filter 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'"`. - -- 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. +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. - Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). For example, to display all disconnected mailboxes on a specific mailbox database, use the following syntax: `'DisconnectDate -ne $null'`. @@ -335,7 +348,9 @@ Accept wildcard characters: False ### -IncludePassive This parameter is available only in on-premises Exchange. -Without the IncludePassive parameter, the cmdlet retrieves statistics from active database copies only. Using the IncludePassive parameter, you can have the cmdlet return statistics from all active and passive database copies. +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. + +If you don't use this switch, the command retrieves statistics from active database copies only. ```yaml Type: SwitchParameter @@ -353,7 +368,9 @@ Accept wildcard characters: False ### -IncludeSoftDeletedRecipients This parameter is available only in the cloud-based service. -{{Fill IncludeSoftDeletedRecipients Description}} +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 deleted mailboxes that are still recoverable. ```yaml Type: SwitchParameter @@ -371,9 +388,9 @@ Accept wildcard characters: False ### -IncludeQuarantineDetails 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. +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. -Specifically, this switch returns the values of the QuarantineDescription, QuarantineLastCrash and QuarantineEnd properties on the mailbox. To see these values, you need use a formatting cmdlet. For example, Get-MailboxStatistics \ -IncludeQuarantineDetails | Format-List Quarantine\*. +Specifically, this switch returns the values of the QuarantineDescription, QuarantineLastCrash and QuarantineEnd properties on the mailbox. To see these values, you need use a formatting cmdlet. For example, `Get-MailboxStatistics -IncludeQuarantineDetails | Format-List Quarantine*`. ```yaml Type: SwitchParameter @@ -391,7 +408,9 @@ Accept wildcard characters: False ### -NoADLookup 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. This helps improve cmdlet performance when querying a mailbox database that contains a large number of mailboxes. +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. + +This switch helps improve cmdlet performance when querying a mailbox database that contains a large number of mailboxes. ```yaml Type: SwitchParameter @@ -412,7 +431,6 @@ 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: - Fully qualified domain name (FQDN) - - NetBIOS name When you specify a value for the Server parameter, the command returns statistics for all the mailboxes on all the databases, including recovery databases, on the specified server. If you don't specify this parameter, the command returns logon statistics for the local server. @@ -430,27 +448,21 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -StoreMailboxIdentity -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: - -- MailboxGuid - -- LegacyDN +### -UseCustomRouting +This parameter is available only in the cloud-based service. -Use this syntax to retrieve information about disconnected mailboxes, which don't have a corresponding Active Directory object or that has a corresponding Active Directory object that doesn't point to the disconnected mailbox in the mailbox database. +{{ Fill UseCustomRouting Description }} ```yaml -Type: StoreMailboxIdParameter -Parameter Sets: Database +Type: SwitchParameter +Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -459,12 +471,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-MailboxTransportService.md b/exchange/exchange-ps/exchange/Get-MailboxTransportService.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Get-MailboxTransportService.md rename to exchange/exchange-ps/exchange/Get-MailboxTransportService.md index e17ccf54ba..4e4beb49a3 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-MailboxTransportService.md +++ b/exchange/exchange-ps/exchange/Get-MailboxTransportService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-mailboxtransportservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MailboxTransportService @@ -17,19 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MailboxTransportService cmdlet to view the configuration of the Mailbox Transport service on Exchange 2013 or later Mailbox servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MailboxTransportService [[-Identity] ] [-DomainController ] +Get-MailboxTransportService [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION The Mailbox Transport service runs on all Mailbox servers and is responsible for delivering messages to and accepting messages from local mailbox databases using remote procedure calls (RPC). The Mailbox Transport service also uses SMTP to send messages to and from the Transport service that runs on all Mailbox servers for routing their ultimate destinations. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,35 +49,35 @@ This example retrieves the detailed transport configuration information for the ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the server that you want to view. ```yaml -Type: Fqdn +Type: MailboxTransportServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the server that you want to view. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: MailboxTransportServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -86,12 +86,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxUserConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md similarity index 82% rename from exchange/exchange-ps/exchange/mailboxes/Get-MailboxUserConfiguration.md rename to exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md index 57e9306ea3..6487e6dc0e 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxUserConfiguration.md +++ b/exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-mailboxuserconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MailboxUserConfiguration @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MailboxUserConfiguration cmdlet to view user configuration items in mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-MailboxUserConfiguration [-Identity] -Mailbox - [-Confirm] [-DomainController ] [-WhatIf] [] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,11 +50,10 @@ This example returns detailed information for the specified user configuration i ## PARAMETERS ### -Identity -The Identity parameter specifies the user configuration item that you want to view. This parameter uses the syntax \\\\: +The Identity parameter specifies the user configuration item that you want to view. This parameter uses the syntax MailboxFolder\ItemName: -- Valid values for \ are folder names (for example, Inbox or Calendar), the value Configuration, or the value Root. Wildcards (\*) aren't supported. - -- Valid values for \ start with IPM.Configuration (for example, IPM.Configuration.Aggregated.OwaUserConfiguration. Wildcards (\*) are supported. +- Valid values for MailboxFolder are folder names (for example, Inbox or Calendar), the value Configuration, or the value Root. Wildcards (\*) aren't supported. +- Valid values for ItemName start with IPM.Configuration (for example, IPM.Configuration.Aggregated.OwaUserConfiguration. Wildcards (\*) are supported. ```yaml Type: MailboxUserConfigurationIdParameter @@ -71,23 +72,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -158,12 +150,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-MailflowStatusReport.md b/exchange/exchange-ps/exchange/Get-MailflowStatusReport.md new file mode 100644 index 0000000000..fef6949dce --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MailflowStatusReport.md @@ -0,0 +1,213 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MailFlowStatusReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MailFlowStatusReport cmdlet to return the message counts for a specific date range organized by the final disposition of the message for the last 90 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MailFlowStatusReport + [-Direction ] + [-Domain ] + [-EndDate ] + [-EventType ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-StartDate ] + [] +``` + +## DESCRIPTION +This cmdlet returns the following information: + +- Date +- Direction +- Event Type +- Count + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailFlowStatusReport -StartDate 06-01-2020 -EndDate 06-10-2020 -Direction Inbound,Outbound -EventType GoodMail,EdgeBlockSpam +``` + +This example returns inbound and outbound messages were classified as GoodMail or EdgeBlockSpam in the specified date range. + +## PARAMETERS + +### -Direction +The Direction parameter filters the results by the direction of the message. Valid values are: + +- Inbound +- IntraOrg +- Outbound + +You can specify multiple value separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -EndDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +The EventType parameter filters the report by the event type. Valid values are: + +- EdgeBlockSpam +- EmailMalware +- EmailPhish +- GoodMail +- SpamDetections +- TransportRules + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md similarity index 88% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilterPolicy.md rename to exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md index b14e7564ec..077860de6f 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-malwarefilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-MalwareFilterPolicy @@ -17,19 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MalwareFilterPolicy cmdlet to view the malware filter policies in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MalwareFilterPolicy [[-Identity] ] [-DomainController ] +Get-MalwareFilterPolicy [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION Malware filter policies contain the malware settings and a list of domains to which those settings apply. A domain can't belong to more than one malware filter policy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,37 +49,37 @@ This example retrieves detailed configuration information for the malware filter ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: MalwareFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -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. ```yaml -Type: MalwareFilterPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -88,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Get-MalwareFilterRule.md similarity index 87% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilterRule.md rename to exchange/exchange-ps/exchange/Get-MalwareFilterRule.md index e0e7b2e068..d8b421d6ef 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilterRule.md +++ b/exchange/exchange-ps/exchange/Get-MalwareFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-malwarefilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-MalwareFilterRule @@ -17,17 +16,19 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Enable-MalwareFilterRule cmdlet to view malware filter rules in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MalwareFilterRule [[-Identity] ] [-DomainController ] [-State ] +Get-MalwareFilterRule [[-Identity] ] + [-DomainController ] + [-State ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,37 +48,37 @@ This example retrieves detailed configuration information for the malware filter ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -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. ```yaml -Type: RuleIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -102,12 +103,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilteringServer.md b/exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md similarity index 88% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilteringServer.md rename to exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md index 89a6402778..11a67a8298 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-MalwareFilteringServer.md +++ b/exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-malwarefilteringserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MalwareFilteringServer @@ -17,17 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MalwareFilteringServer cmdlet to view the Malware agent settings in the Transport service on a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MalwareFilteringServer [[-Identity] ] [-DomainController ] +Get-MalwareFilteringServer [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,45 +47,42 @@ This example returns the detailed Exchange Malware agent settings on a Mailbox s ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: -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. +- Name +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN ```yaml -Type: Fqdn +Type: MalwareFilteringServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- FQDN - -- Distinguished name (DN) +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -- Exchange Legacy DN +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. ```yaml -Type: MalwareFilteringServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -94,12 +91,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedContentSettings.md b/exchange/exchange-ps/exchange/Get-ManagedContentSettings.md similarity index 86% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedContentSettings.md rename to exchange/exchange-ps/exchange/Get-ManagedContentSettings.md index c747078c26..543f807e2a 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedContentSettings.md +++ b/exchange/exchange-ps/exchange/Get-ManagedContentSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-managedcontentsettings +online version: https://learn.microsoft.com/powershell/module/exchange/get-managedcontentsettings applicable: Exchange Server 2010 title: Get-ManagedContentSettings schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Get-ManagedContentSettings @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Get-ManagedContentSettings cmdlet to retrieve managed content settings associated with managed folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,7 +24,6 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-ManagedContentSettings [-FolderName ] [-DomainController ] - [-Organization ] [] ``` @@ -33,7 +31,6 @@ Get-ManagedContentSettings [-FolderName ] ``` Get-ManagedContentSettings [[-Identity] ] [-DomainController ] - [-Organization ] [] ``` @@ -42,7 +39,7 @@ The Get-ManagedContentSettings cmdlet retrieves from one to all of the managed c If only the Identity parameter is present, the folder content settings and all associated attributes are returned. If the Identity parameter isn't present, the command returns all content settings. If the FolderName parameter is present, the command returns all content settings contained in the specified managed folder and all the attributes of each setting. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,30 +66,30 @@ This example retrieves the managed content settings for the managed folder Inbox ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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. ```yaml -Type: Fqdn -Parameter Sets: (All) +Type: ELCContentSettingsIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -FolderName -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. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: ELCFolderIdParameter -Parameter Sets: FolderName +Type: Fqdn +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 @@ -103,30 +100,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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. - -```yaml -Type: ELCContentSettingsIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +### -FolderName +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. -### -Organization -This parameter is reserved for internal Microsoft use. +This parameter can't be used with the Identity parameter. ```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) +Type: ELCFolderIdParameter +Parameter Sets: FolderName Aliases: Applicable: Exchange Server 2010 @@ -142,12 +123,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedFolder.md b/exchange/exchange-ps/exchange/Get-ManagedFolder.md similarity index 77% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedFolder.md rename to exchange/exchange-ps/exchange/Get-ManagedFolder.md index bc12b8f053..f7a6302c2b 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedFolder.md +++ b/exchange/exchange-ps/exchange/Get-ManagedFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-managedfolder +online version: https://learn.microsoft.com/powershell/module/exchange/get-managedfolder applicable: Exchange Server 2010 title: Get-ManagedFolder schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Get-ManagedFolder @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Get-ManagedFolder cmdlet to retrieve the attributes of one or more managed folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,28 +24,26 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-ManagedFolder [[-Identity] ] [-DomainController ] - [-Organization ] [] + [] ``` ### Mailbox ``` Get-ManagedFolder [-Mailbox ] [-DomainController ] - [-Organization ] [] + [] ``` ## DESCRIPTION The Get-ManagedFolder cmdlet retrieves the specified managed folder attributes: - If only an Identity parameter value is present, the command retrieves the specified folder and all associated attributes. - - If a Mailbox parameter value is present, the command retrieves all managed folders that apply to that user by means of a managed folder mailbox policy applied by an administrator. Managed folders that users add by means of an organization's managed folder opt-in Web site aren't displayed by this command. - - If no parameter values are specified, the command retrieves all the folder objects and their associated attributes. The Get-ManagedFolder cmdlet accepts a ManagedFolder object or an identity string as pipelined input. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,35 +56,35 @@ This example retrieves information about the managed folder MyManagedFolder. The ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the name, distinguished name (DN), or GUID of the managed folder. ```yaml -Type: Fqdn -Parameter Sets: (All) +Type: ELCFolderIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name, distinguished name (DN), or GUID of the managed folder. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: ELCFolderIdParameter -Parameter Sets: Identity +Type: Fqdn +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -95,23 +92,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) This cmdlet retrieves all the folders that apply to the specified mailbox. @@ -129,35 +117,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Organization -This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see [Multi-Tenant Support](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/ff923272(v=exchg.141)). - -The Organization parameter specifies the organization in which you'll perform this action. This parameter doesn't accept wildcard characters, and you must use the exact name of the organization. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md new file mode 100644 index 0000000000..773b53f264 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md @@ -0,0 +1,94 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ManagedFolderMailboxPolicy + +## SYNOPSIS +This cmdlet is available only in Exchange Server 2010. + +Use the Get-ManagedFolderMailboxPolicy cmdlet to return all attributes of one or more managed folder mailbox policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ManagedFolderMailboxPolicy [[-Identity] ] + [-DomainController ] + [] +``` + +## DESCRIPTION +A managed folder mailbox policy is a logical grouping of one or more managed folders. Policies are applied to mailboxes. The Get-ManagedFolderMailboxPolicy cmdlet lists one or more managed folder mailbox policies created in the Microsoft Exchange Server 2010 organization. All policies can be listed. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ManagedFolderMailboxPolicy "PM Storage Template" +``` + +This example returns all the attributes of the managed folder mailbox policy PM Storage Template. + +The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ManagementRole.md b/exchange/exchange-ps/exchange/Get-ManagementRole.md new file mode 100644 index 0000000000..72a4c467e8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ManagementRole.md @@ -0,0 +1,296 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ManagementRole + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-ManagementRole cmdlet to view management roles that have been created in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### GetChildren +``` +Get-ManagementRole [-Identity] + [-GetChildren] + [-DomainController ] + [-RoleType ] + [] +``` + +### Recurse +``` +Get-ManagementRole [-Identity] + [-Recurse] + [-DomainController ] + [-RoleType ] + [] +``` + +### Identity +``` +Get-ManagementRole [[-Identity] ] + [-Cmdlet ] + [-CmdletParameters ] + [-DomainController ] + [-RoleType ] + [] +``` + +### Script +``` +Get-ManagementRole [[-Identity] ] + [-Script ] + [-ScriptParameters ] + [-DomainController ] + [-RoleType ] + [] +``` + +## DESCRIPTION +You can view management roles in several ways, from listing all the roles in your organization to listing only the child roles of a specified parent role. You can also view the details of a specific role by piping the output of the Get-ManagementRole cmdlet to the Format-List cmdlet. + +For more information about management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ManagementRole +``` + +This example lists all the roles that have been created in your organization. + +### Example 2 +```powershell +Get-ManagementRole "Mail Recipients" -Recurse +``` + +This example lists all the roles that are children of the Mail Recipients management role. The command performs a recursive query of all the child roles of the specified parent role. This recursive query finds every child role from the immediate children of the parent to the last child role in the hierarchy. In a recursive list, the parent role is also returned in the list. + +### Example 3 +```powershell +Get-ManagementRole -CmdletParameters Identity, Database +``` + +This example lists all the roles that contain both the Identity and Database parameters. Roles that contain only one parameter or the other aren't returned. + +### Example 4 +```powershell +Get-ManagementRole -RoleType UnScopedTopLevel +``` + +This example lists all the roles that have a type of UnScopedTopLevel. These roles contain custom scripts or non-Exchange cmdlets. + +### Example 5 +```powershell +Get-ManagementRole "Transport Rules" | Format-List Name, RoleType +``` + +This example retrieves only the Transport Rules role and passes the output of the Get-ManagementRole cmdlet to the Format-List cmdlet. The Format-List cmdlet then shows only the Name and RoleType properties of the Transport Rules role. For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). + +### Example 6 +```powershell +Get-ManagementRole "Mail Recipients" -GetChildren +``` + +This example lists the immediate children of the Mail Recipients role. Only the child roles that hold the Mail Recipients role as their parent role are returned. The Mail Recipients role isn't returned in the list. + +## PARAMETERS + +### -Identity +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 +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 +Default value: None +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 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -GetChildren +The GetChildren parameter retrieves a list of all the roles that were created based on the parent role specified in the Identity parameter. You don't need to specify a value with this switch. + +Only the immediate child roles of the parent role are included in the results. + +You can use this switch only with the Identity and RoleType parameters. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Recurse +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. + +You can use this switch only with the Identity and RoleType parameters. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Cmdlet +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CmdletParameters +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoleType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Script +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScriptParameters +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/role-based-access-control/Get-ManagementRoleAssignment.md b/exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md similarity index 91% rename from exchange/exchange-ps/exchange/role-based-access-control/Get-ManagementRoleAssignment.md rename to exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md index 242e7110f7..574baae033 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Get-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/get-managementroleassignment +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-ManagementRoleAssignment @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ManagementRoleAssignment cmdlet to retrieve management role assignments. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -35,6 +34,7 @@ Get-ManagementRoleAssignment [[-Identity] ] [-ExclusiveRecipientWriteScope ] [-GetEffectiveUsers] [-RecipientAdministrativeUnitScope ] + [-RecipientGroupScope ] [-RecipientOrganizationalUnitScope ] [-RecipientWriteScope ] [-RoleAssigneeType ] @@ -46,7 +46,8 @@ Get-ManagementRoleAssignment [[-Identity] ] ### RoleAssignee ``` -Get-ManagementRoleAssignment [-AssignmentMethod ] [-Role ] +Get-ManagementRoleAssignment [-AssignmentMethod ] + [-Role ] [-ConfigWriteScope ] [-CustomConfigWriteScope ] [-CustomRecipientWriteScope ] @@ -58,6 +59,7 @@ Get-ManagementRoleAssignment [-AssignmentMethod ] [-Role ] [-GetEffectiveUsers] [-RecipientAdministrativeUnitScope ] + [-RecipientGroupScope ] [-RecipientOrganizationalUnitScope ] [-RecipientWriteScope ] [-RoleAssignee ] @@ -71,9 +73,9 @@ Get-ManagementRoleAssignment [-AssignmentMethod ] [-Role [-DomainController ] [-Parameters ] - [-PSSnapinName ] [-Type ] [] +Get-ManagementRoleEntry [-Identity] + [-DomainController ] + [-Parameters ] + [-PSSnapinName ] + [-ResultSize ] + [-Type ] + [] ``` ## DESCRIPTION The Get-ManagementRoleEntry cmdlet retrieves role entries that have been configured on roles. You can retrieve specific role entries that match specific criteria such as role name, cmdlet name, parameter name, or a combination of each, or role entry type or the associated Windows PowerShell snap-in. -For more information about management role entries, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,9 +63,9 @@ This example retrieves the Tier 2 Help Desk\\Set-Mailbox role entry and pipes th ## PARAMETERS ### -Identity -The Identity parameter specifies the role entry to retrieve. You must specify the value of the Identity parameter in the format, \\\\, for example, ExampleRole\\Set-Mailbox. +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://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about how management role entries work, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). You can use the wildcard character (\*) instead of the role, cmdlet name or both. @@ -132,6 +136,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ResultSize +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. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Type 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. @@ -153,12 +175,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Get-ManagementScope.md b/exchange/exchange-ps/exchange/Get-ManagementScope.md similarity index 84% rename from exchange/exchange-ps/exchange/role-based-access-control/Get-ManagementScope.md rename to exchange/exchange-ps/exchange/Get-ManagementScope.md index 9c65c264fc..38673e7eda 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Get-ManagementScope.md +++ b/exchange/exchange-ps/exchange/Get-ManagementScope.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/get-managementscope +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-ManagementScope @@ -17,21 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ManagementScope cmdlet to return a list of management scopes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ManagementScope [[-Identity] ] [-DomainController ] - [-Exclusive ] [-Orphan] [] +Get-ManagementScope [[-Identity] ] + [-DomainController ] + [-Exclusive ] + [-Orphan] + [] ``` ## DESCRIPTION You can retrieve one scope or many, retrieve only scopes that aren't associated with management role assignments, or retrieve scopes that are exclusive or regular scopes. -For more information about regular and exclusive scopes, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,7 +49,7 @@ This example retrieves all the management scopes that start with the string Redm Get-ManagementScope "Redmond Servers Scope" | Format-List ``` -This example retrieves the Redmond Servers Scope using the Get-ManagementScope cmdlet and pipes the output to the Format-List cmdlet. For more information about the Format-List cmdlet, see [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +This example retrieves the Redmond Servers Scope using the Get-ManagementScope cmdlet and pipes the output to the Format-List cmdlet. For more information about the Format-List cmdlet, see [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ### Example 3 ```powershell @@ -65,6 +67,22 @@ This example retrieves a list of exclusive scopes. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DomainController This parameter is available only in on-premises Exchange. @@ -99,24 +117,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Orphan -The Orphan parameter returns only the management scopes that aren't associated with role assignments. +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 @@ -136,12 +138,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md new file mode 100644 index 0000000000..77a025f2c7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md @@ -0,0 +1,191 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MapiVirtualDirectory + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Get-MapiVirtualDirectory cmdlet to view Message Application Programming Interface (MAPI) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Server +``` +Get-MapiVirtualDirectory -Server + [-ADPropertiesOnly] + [-DomainController ] + [-ShowMailboxVirtualDirectories] + [] +``` + +### Identity +``` +Get-MapiVirtualDirectory [[-Identity] ] + [-ADPropertiesOnly] + [-DomainController ] + [-ShowMailboxVirtualDirectories] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MapiVirtualDirectory -Server ContosoMail +``` + +This example returns a summary list of the MAPI virtual directories on the server named ContosoMail. + +### Example 2 +```powershell +Get-MapiVirtualDirectory -Identity "ContosoMail\mapi (Default Web Site)" | Format-List + +Get-MapiVirtualDirectory "ContosoMail\mapi (Default Web Site)" | Format-List + +Get-MapiVirtualDirectory ContosoMai\mapi* | Format-List +``` + +These examples return detailed information for the MAPI virtual directory named "mapi (Default Web Site)" on the server named ContosoMail. All three commands do the same thing. + +### Example 3 +```powershell +Get-MapiVirtualDirectory +``` + +This example returns a summary list of all MAPI virtual directories in the client access services on all Mailbox servers in the organization. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. + +You can't use the Identity and Server parameters in the same command. + +```yaml +Type: VirtualDirectoryIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Server +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 +- FQDN +- Distinguished name (DN) +- ExchangeLegacyDN + +You can't use the Server and Identity parameters in the same command. + +```yaml +Type: ServerIdParameter +Parameter Sets: Server +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ADPropertiesOnly +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowMailboxVirtualDirectories +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. + +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. + +We recommend that you use this parameter only under the direction of Microsoft Customer Service and Support. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mail-flow/Get-Message.md b/exchange/exchange-ps/exchange/Get-Message.md similarity index 84% rename from exchange/exchange-ps/exchange/mail-flow/Get-Message.md rename to exchange/exchange-ps/exchange/Get-Message.md index 700d7b6d4f..634425d077 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-Message.md +++ b/exchange/exchange-ps/exchange/Get-Message.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-message +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-Message @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-Message cmdlet to view the details of one or more messages in queues on Mailbox servers or Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,7 +32,8 @@ Get-Message [-Filter ] [-ReturnPageInfo ] [-SearchForward ] [-Server ] - [-SortOrder ] [] + [-SortOrder ] + [] ``` ### Identity @@ -47,7 +47,8 @@ Get-Message [[-Identity] ] [-ResultSize ] [-ReturnPageInfo ] [-SearchForward ] - [-SortOrder ] [] + [-SortOrder ] + [] ``` ### Queue @@ -61,13 +62,14 @@ Get-Message [-Queue ] [-ResultSize ] [-ReturnPageInfo ] [-SearchForward ] - [-SortOrder ] [] + [-SortOrder ] + [] ``` ## DESCRIPTION You can display messages by including the server name as part of the Identity parameter or the Queue parameter or by including the Server parameter with a filter query. The Identity parameter, Queue parameter, and Filter parameter settings are mutually exclusive. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -95,7 +97,7 @@ This example displays all messages queued on the server named Server01. The resu ## PARAMETERS ### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity). +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 @@ -143,7 +145,7 @@ Accept wildcard characters: False ``` ### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell). +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 ("). @@ -177,7 +179,9 @@ Accept wildcard characters: False ``` ### -IncludeComponentLatencyInfo -The IncludeComponentLatencyInfo switch specifies whether the information about component latency is included in the message properties. 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. +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. ```yaml Type: SwitchParameter @@ -193,23 +197,21 @@ Accept wildcard characters: False ``` ### -IncludeRecipientInfo -The IncludeRecipientInfo switch specifies whether to display the message recipients in the Recipients field. If you don't include the IncludeRecipientInfo switch, the Recipients field is blank. +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. -Storing the results of a Get-Message -IncludeRecipientInfo command in a variable allows you to display additional properties for the message recipients. The following list describes the available recipient properties: +If you don't include the IncludeRecipientInfo switch, the Recipients field is blank. -- Address: The email address of the recipient. +Storing the results of a `Get-Message -IncludeRecipientInfo` command in a variable allows you to display additional properties for the message recipients. The following list describes the available recipient properties: +- Address: The email address of the recipient. - Type: The recipient type, which may be External, Mailbox or Distribution Group. Distribution Group is used when the destination is an expansion server. - - FinalDestination: The distinguished name (DN) of the object used to route the message. - - Status: The recipient status may be Complete, Ready or Retry. - - LastError: The SMTP response after the last delivery attempt or a localized error message if the message is placed in the unreachable queue. -For example, to store the recipient information of a message in the contoso.com remote delivery queue that has the MessageIdentity value of 1234 to a variable named $x, use the following command: $x=Get-Message -Identity "contoso.com\\1234" -IncludeRecipientInfo. +For example, to store the recipient information of a message in the contoso.com remote delivery queue that has the MessageIdentity value of 1234 to a variable named $x, use the following command: `$x=Get-Message -Identity "contoso.com\\1234" -IncludeRecipientInfo`. -To display the extended recipient properties that are now stored in the $x variable, use the following command : $x.Recipients. +To display the extended recipient properties that are now stored in the $x variable, use the following command: `$x.Recipients`. ```yaml Type: SwitchParameter @@ -225,7 +227,7 @@ Accept wildcard characters: False ``` ### -Queue -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. +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. @@ -294,11 +296,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -341,12 +340,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-MessageCategory.md b/exchange/exchange-ps/exchange/Get-MessageCategory.md similarity index 82% rename from exchange/exchange-ps/exchange/mailboxes/Get-MessageCategory.md rename to exchange/exchange-ps/exchange/Get-MessageCategory.md index 6c08bf481a..6cebfc35f4 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MessageCategory.md +++ b/exchange/exchange-ps/exchange/Get-MessageCategory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-messagecategory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MessageCategory @@ -17,19 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MessageCategory cmdlet to retrieve a message category from the specified mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MessageCategory [[-Identity] ] [-DomainController ] - [-Mailbox ] [] +Get-MessageCategory [[-Identity] ] + [-DomainController ] + [-Mailbox ] + [] ``` ## DESCRIPTION The Get-MessageCategory cmdlet is used by the web management interface in Microsoft Exchange to populate fields that display message category information. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,26 +78,17 @@ Accept wildcard characters: False ``` ### -Mailbox -The Mailbox parameter specifies mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: +The Mailbox parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -117,12 +109,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-MessageClassification.md b/exchange/exchange-ps/exchange/Get-MessageClassification.md similarity index 87% rename from exchange/exchange-ps/exchange/policy-and-compliance/Get-MessageClassification.md rename to exchange/exchange-ps/exchange/Get-MessageClassification.md index 469af03ede..bfb6750a16 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-MessageClassification.md +++ b/exchange/exchange-ps/exchange/Get-MessageClassification.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-messageclassification +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MessageClassification @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MessageClassification cmdlet to view existing message classifications in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,7 @@ Get-MessageClassification [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +45,7 @@ This example lists all message classifications in your organization. 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 - -- Identity: Default\\ or \\\; for example, "Default\My Message Classification" or "es-ES\My Message Classification". - +- Identity: `Default\` or `\`; for example, "Default\My Message Classification" or "es-ES\My Message Classification". - ClassificationID (GUID) ```yaml @@ -105,12 +102,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-MessageTrace.md b/exchange/exchange-ps/exchange/Get-MessageTrace.md similarity index 82% rename from exchange/exchange-ps/exchange/mail-flow/Get-MessageTrace.md rename to exchange/exchange-ps/exchange/Get-MessageTrace.md index 049f34e4a6..fa030fd3a1 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-MessageTrace.md +++ b/exchange/exchange-ps/exchange/Get-MessageTrace.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-messagetrace +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-MessageTrace @@ -15,19 +14,18 @@ monikerRange: "exchonline-ps || eop-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-MessageTrace cmdlet to trace messages as they pass through the cloud-based organization. - > [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). +> This cmdlet is replaced by the [Get-MessageTraceV2](https://learn.microsoft.com/powershell/module/exchange/get-messagetracev2) cmdlet and will eventually be deprecated. + +Use the Get-MessageTrace cmdlet to trace messages as they pass through the cloud-based organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-MessageTrace [-EndDate ] - [-Expression ] [-FromIP ] [-MessageId ] [-MessageTraceId ] @@ -45,15 +43,15 @@ Get-MessageTrace ## DESCRIPTION You can use this cmdlet to search message data for the last 10 days. If you run this cmdlet without any parameters, only data from the last 48 hours is returned. -If you enter a start date that is greater than 10 days and less than or equal to 30 days, only 10 days of data will be returned. - -If you enter a start date that is older than 30 days, you will receive an error and the command will return no results. +If you enter a start date that is older than 10 days, you will receive an error and the command will return no results. To search for message data that is greater than 10 days old, use the Start-HistoricalSearch and Get-HistoricalSearch cmdlets. -This cmdlet returns a maximum of 1000000 results, and will timeout on very large queries. If your query returns too many results, consider splitting it up using smaller StartDate and EndDate intervals. +By default, this cmdlet returns a maximum of 1000 results, and will timeout on very large queries. If your query returns too many results, consider splitting it up using smaller StartDate and EndDate intervals. + +The time stamps on the output are in UTC time format. That might be different from the time format that you used for the -StartDate and the -EndDate parameters. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,7 +67,7 @@ This example retrieves message trace information for messages sent by john@conto ### -EndDate 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". +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". ```yaml Type: DateTime @@ -84,24 +82,8 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -FromIP -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. For outgoing messages from Exchange Online, the value is blank. +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 @@ -133,7 +115,15 @@ Accept wildcard characters: False ``` ### -MessageTraceId -The MessageTraceId parameter can be used with the recipient address to uniquely identify a message trace and obtain more details. A message trace ID is generated for every message that's processed by the system. +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: + +- Get-MailDetailATPReport +- Get-MailDetailDlpPolicyReport +- Get-MailDetailEncryptionReport +- Get-MailDetailTransportRuleReport +- Get-MessageTraceDetail ```yaml Type: Guid @@ -231,7 +221,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: DateTime @@ -250,19 +240,12 @@ Accept wildcard characters: False 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. - - GettingStatus: The message is waiting for status update. - - Failed: Message delivery was attempted and it failed or the message was filtered as spam or malware, or by transport rules. - - Pending: Message delivery is underway or was deferred and is being retried. - - Delivered: The message was delivered to its destination. - - Expanded: There was no message delivery because the message was addressed to a distribution group and the membership of the distribution was expanded. - - Quarantined: The message was quarantined. - - FilteredAsSpam: The message was marked as spam. ```yaml @@ -299,12 +282,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md b/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md new file mode 100644 index 0000000000..2053d79a67 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md @@ -0,0 +1,284 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MessageTraceDetail + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +> [!NOTE] +> This cmdlet is replaced by the [Get-MessageTraceDetailV2](https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetailv2) cmdlet and will eventually be deprecated. + +Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. Note that these detailed results are returned less quickly than the Get-MessageTrace results. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MessageTraceDetail -MessageTraceId -RecipientAddress + [-Action ] + [-EndDate ] + [-Event ] + [-MessageId ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-SenderAddress ] + [-StartDate ] + [] +``` + +## DESCRIPTION +You can use this cmdlet to search message data for the last 10 days. If you enter a time period that's older than 10 days, you will receive an error and the command will return no results. + +To search for message data that is greater than 10 days old, use the Start-HistoricalSearch and Get-HistoricalSearch cmdlets. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MessageTraceDetail -MessageTraceId ae5c1219-4c90-41bf-fef5-08d837917e7c -RecipientAddress robert@contoso.com +``` + +This example retrieves detailed message trace information for messages with the message trace ID value ae5c1219-4c90-41bf-fef5-08d837917e7c that were received by robert@contoso.com. + +### Example 2 +```powershell +Get-MessageTrace -MessageTraceId 2bbad36aa4674c7ba82f4b307fff549f -SenderAddress john@contoso.com -StartDate 06/13/2018 -EndDate 06/15/2018 | Get-MessageTraceDetail +``` + +This example uses the Get-MessageTrace cmdlet to retrieve message trace information for messages with the Exchange Network Message ID value 2bbad36aa4674c7ba82f4b307fff549f sent by john@contoso.com between June 13, 2018 and June 15, 2018, and pipelines the results to the Get-MessageTraceDetail cmdlet. + +## PARAMETERS + +### -MessageTraceId +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: + +- Get-MailDetailATPReport +- Get-MailDetailDlpPolicyReport +- Get-MailDetailEncryptionReport +- Get-MailDetailTransportRuleReport +- Get-MessageTrace + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Action +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +If don't use the StartDate and EndDate parameters, only data from the last 48 hours is returned. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Event +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. +- SEND: The message was sent by the service. +- FAIL: The message failed to be delivered. +- DELIVER: The message was delivered to a mailbox. +- EXPAND: The message was sent to a distribution group that was expanded. +- TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents. +- DEFER: The message delivery was postponed and may be re-attempted later. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageId +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderAddress +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StartDate +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". + +If don't use the StartDate and EndDate parameters, only data from the last 48 hours is returned. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-MessageTraceDetailV2.md b/exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md new file mode 100644 index 0000000000..78e1a37969 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md @@ -0,0 +1,211 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MessageTraceDetailV2 + +## SYNOPSIS + +## SYNTAX + +``` +Get-MessageTraceDetailV2 [-MessageTraceId] [-RecipientAddress] + [[-Action] ] + [[-EndDate] ] + [[-Event] ] + [[-MessageId] ] + [[-SenderAddress] ] + [[-StartDate] ] + [] +``` + +## DESCRIPTION +You can use this cmdlet to search message data for the last 90 days. You can only query 10 days worth of data per query. If you enter a timeframe that's older than 90 days, you receive an error and the command will return no results. + +Throttling limit: A maximum of 100 query requests will be accepted within 5 minutes running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the past 5 minutes + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MessageTraceDetailV2 -MessageTraceId ae5c1219-4c90-41bf-fef5-08d837917e7c -RecipientAddress robert@contoso.com +``` + +This example retrieves detailed message trace information for messages with the message trace ID value ae5c1219-4c90-41bf-fef5-08d837917e7c that were received by `robert@contoso.com`. + +### Example 2 +```powershell +Get-MessageTraceV2 -MessageTraceId 2bbad36aa4674c7ba82f4b307fff549f -SenderAddress john@contoso.com -StartDate 06/13/2025 -EndDate 06/15/2025 | Get-MessageTraceDetailV2 +``` + +This example uses the Get-MessageTraceV2 cmdlet to retrieve message trace information for messages with the Exchange Network Message ID value 2bbad36aa4674c7ba82f4b307fff549f sent by `john@contoso.com` between June 13, 2025 and June 15, 2025, and pipelines the results to the Get-MessageTraceDetailV2 cmdlet. + +## PARAMETERS + +### -MessageTraceId +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Action +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +If don't use the StartDate and EndDate parameters, only data from the last 48 hours is returned. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 2 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Event +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. +- SEND: The message was sent by the service. +- FAIL: The message failed to be delivered. +- DELIVER: The message was delivered to a mailbox. +- EXPAND: The message was sent to a distribution group that was expanded. +- TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents. +- DEFER: The message delivery was postponed and may be re-attempted later. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageId +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -SenderAddress +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -StartDate +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". + +If don't use the StartDate and EndDate parameters, only data from the last 48 hours is returned. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 8 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-MessageTraceV2.md b/exchange/exchange-ps/exchange/Get-MessageTraceV2.md new file mode 100644 index 0000000000..f356876da6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MessageTraceV2.md @@ -0,0 +1,321 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MessageTraceV2 + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MessageTraceV2 cmdlet to trace messages as they pass through the cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MessageTraceV2 + [[-EndDate] ] + [[-FromIP] ] + [[-MessageId] ] + [[-MessageTraceId] ] + [[-RecipientAddress] ] + [[-ResultSize] ] + [[-SenderAddress] ] + [[-StartDate] ] + [[-StartingRecipientAddress] ] + [[-Status] ] + [[-SubjectFilterType] ] + [[-Subject] ] + [[-ToIP] ] + [] +``` + +## DESCRIPTION +You can use this cmdlet to search message data for the last 90 days. If you run this cmdlet without any parameters, only data from the last 48 hours is returned. You can only return 10 days worth of data per query. + +By default, this cmdlet returns up to 1000 results, with a maximum of 5000 results. If your data exceeds the result size, query in multiple rounds or use smaller StartDate and EndDate intervals. + +The time stamps on the output are in UTC time format. That might be different from the time format that you used for the -StartDate and the -EndDate parameters. + +Throttling limit: A maximum of 100 query requests will be accepted within 5 minutes running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the past 5 minutes + +Pagination isn't supported in this cmdlet. To query subsequent data, use the StartingRecipientAddress and EndDate parameters with the values from the **Recipient address** and **Received Time** properties respectively of the previous result in the next query. + +Best Practices: + +- Use the ResultSize parameter to adjust the size of your results. +- Be as precise as possible. Narrow the gap between StartDate and EndDate and use additional parameters (for example, SenderAddress) where possible. +- Use MessageTraceId where possible (required for messages sent to more than 1000 recipients). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MessageTraceV2 -SenderAddress john@contoso.com -StartDate 06/13/2025 -EndDate 06/15/2025 +``` + +This example retrieves message trace information for messages sent by `john@contoso.com` between June 13, 2025 and June 15, 2025. + +## PARAMETERS + +### -EndDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -FromIP +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MessageId +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MessageTraceId +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: + +- Get-MailDetailATPReport +- Get-MailDetailDlpPolicyReport +- Get-MailDetailEncryptionReport +- Get-MailDetailTransportRuleReport +- Get-MessageTraceDetailV2 + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 4 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ResultSize +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 6 +Default value: 0 +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -SenderAddress +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 8 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -StartingRecipientAddress +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Status +The Status parameter filters the results by the delivery status of the message. Valid values are: + +- Delivered: The message was delivered to its destination. +- Expanded: There was no message delivery because the message was addressed to a distribution group and the membership of the distribution was expanded. +- Failed: Message delivery was attempted and it failed. +- FilteredAsSpam: The message was marked as spam. +- GettingStatus: The message is waiting for status update. +- None: The message has no delivery status because it was rejected or redirected to a different recipient. +- Pending: Message delivery is underway or was deferred and is being retried. +- Quarantined: The message was quarantined. + +You can separate multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 10 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Subject +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 11 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -SubjectFilterType +The SubjectFilterType parameter specifies how the value of the Subject parameter is evaluated. Valid values are: + +- Contains +- EndsWith +- StartsWith + +We recommend using StartsWith or EndsWith instead of Contains whenever possible. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 12 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ToIP +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 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-MessageTrackingLog.md b/exchange/exchange-ps/exchange/Get-MessageTrackingLog.md similarity index 86% rename from exchange/exchange-ps/exchange/mail-flow/Get-MessageTrackingLog.md rename to exchange/exchange-ps/exchange/Get-MessageTrackingLog.md index 57797083a6..877d2fd0a3 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-MessageTrackingLog.md +++ b/exchange/exchange-ps/exchange/Get-MessageTrackingLog.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-messagetrackinglog +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MessageTrackingLog @@ -17,15 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MessageTrackingLog cmdlet to search for message delivery information stored in the message tracking log. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MessageTrackingLog [-DomainController ] [-End ] [-EventId ] - [-InternalMessageId ] [-MessageId ] [-MessageSubject ] [-Recipients ] - [-Reference ] [-ResultSize ] [-Sender ] [-Server ] - [-Start ] [-NetworkMessageId ] [-Source ] [-TransportTrafficType ] +Get-MessageTrackingLog [-DomainController ] + [-End ] + [-EventId ] + [-InternalMessageId ] + [-MessageId ] + [-MessageSubject ] + [-Recipients ] + [-Reference ] + [-ResultSize ] + [-Sender ] + [-Server ] + [-Start ] + [-NetworkMessageId ] + [-Source ] + [-TransportTrafficType ] [] ``` @@ -35,27 +45,31 @@ A unique message tracking log exists for the Transport service on a Mailbox serv The field names displayed in the results from the Get-MessageTrackingLog cmdlet are similar to the actual field names used in the message tracking logs. The differences are: - The dashes are removed from the field names. For example internal-message-id is displayed as InternalMessageId. - - The date-time field is displayed as Timestamp. - - The recipient-address field is displayed as Recipients. - - The sender-address field is displayed as Sender. -For more information about the message tracking log files, see [Message tracking](https://docs.microsoft.com/Exchange/mail-flow/transport-logs/message-tracking). +For more information about the message tracking log files, see [Message tracking](https://learn.microsoft.com/Exchange/mail-flow/transport-logs/message-tracking). -The Get-MessageTrackingLog results are displayed on-screen. You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding "\> \" to the command. For example: +You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > ` to the command. For example: `Get-MessageTrackingLog -Start "03/13/2020 09:00:00" -End "03/13/2020 09:10:00" | ConvertTo-Html > "C:\My Documents\message track.html"`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-MessageTrackingLog -Server Mailbox01 -Start "03/13/2018 09:00:00" -End "03/15/2018 17:00:00" -Sender "john@contoso.com" +Get-MessageTrackingLog -Server Mailbox01 -Start "03/13/2024 09:00:00" -End "03/15/2024 17:00:00" -Sender "john@contoso.com" +``` + +This example searches the message tracking logs on the Mailbox server named Mailbox01 for information about all messages sent from March 13, 2024, 09:00 to March 15, 2024, 17:00 by the sender john@contoso.com. + +### Example 2 +```powershell +Get-MessageTrackingLog -Server Mailbox01 -Start "03/13/2024 09:00:00" -Recipients @("john@contoso.com","alice@contoso.com") ``` -This example searches the message tracking logs on the Mailbox server named Mailbox01 for information about all messages sent from March 13, 2018, 09:00 to March 15, 2018, 17:00 by the sender john@contoso.com. +This example searches the message tracking logs on the Mailbox server named Mailbox01 for information about all messages sent from March 13, 2024, 09:00 to today for the recipients john@contoso.com and/or alice@contoso.com. ## PARAMETERS @@ -80,7 +94,7 @@ Accept wildcard characters: False ### -End 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". +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". ```yaml Type: DateTime @@ -162,7 +176,7 @@ Accept wildcard characters: False ``` ### -Recipients -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 recipient email addresses separated by commas. +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[] @@ -229,11 +243,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -254,7 +265,7 @@ Accept wildcard characters: False ### -Start 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". +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". ```yaml Type: DateTime @@ -286,7 +297,7 @@ Accept wildcard characters: False ``` ### -Source -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://docs.microsoft.com/Exchange/mail-flow/transport-logs/message-tracking#source-values-in-the-message-tracking-log). +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 @@ -322,12 +333,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-MessageTrackingReport.md b/exchange/exchange-ps/exchange/Get-MessageTrackingReport.md similarity index 85% rename from exchange/exchange-ps/exchange/mail-flow/Get-MessageTrackingReport.md rename to exchange/exchange-ps/exchange/Get-MessageTrackingReport.md index 841a6732de..fe0eb16c93 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-MessageTrackingReport.md +++ b/exchange/exchange-ps/exchange/Get-MessageTrackingReport.md @@ -1,46 +1,56 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-messagetrackingreport -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MessageTrackingReport ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. Use the Get-MessageTrackingReport cmdlet to return data for a specific message tracking report. This cmdlet is used by the delivery reports feature. -In Exchange Online, delivery reports has been replaced by message trace (the Get-MessageTrace and Get-MessageTraceDetail cmdlets). +In Exchange Online, delivery reports are replaced by message trace (the Get-MessageTraceV2 and Get-MessageTraceDetailV2 cmdlets). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MessageTrackingReport [-Identity] [-BypassDelegateChecking] - [-DetailLevel ] [-DomainController ] [-DoNotResolve] - [-RecipientPathFilter ] [-Recipients ] [-ReportTemplate ] - [-ResultSize ] [-Status <_DeliveryStatus>] - [-TraceLevel ] [] +Get-MessageTrackingReport [-Identity] + [-BypassDelegateChecking] + [-DetailLevel ] + [-DomainController ] + [-DoNotResolve] + [-RecipientPathFilter ] + [-Recipients ] + [-ReportTemplate ] + [-ResultSize ] + [-Status ] + [-TraceLevel ] + [] ``` ## DESCRIPTION -This cmdlet requires the ID for the message tracking report that you want to view. Therefore, first you need to use the Search-MessageTrackingReport cmdlet to find the message tracking report ID for a specific message, and then pass the results to this cmdlet. For more information, see [Search-MessageTrackingReport](https://docs.microsoft.com/powershell/module/exchange/mail-flow/search-messagetrackingreport). +This cmdlet requires the ID for the message tracking report that you want to view. Therefore, first you need to use the Search-MessageTrackingReport cmdlet to find the message tracking report ID for a specific message, and then pass the results to this cmdlet. For more information, see [Search-MessageTrackingReport](https://learn.microsoft.com/powershell/module/exchange/search-messagetrackingreport). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$Temp = Search-MessageTrackingReport -Identity "David Jones" -Recipients "wendy@contoso.com"; Get-MessageTrackingReport -Identity $Temp.MessageTrackingReportID -ReportTemplate Summary +$Temp = Search-MessageTrackingReport -Identity "David Jones" -Recipients "wendy@contoso.com" + +foreach ($reportId in $Temp.MessageTrackingReportId) { + Get-MessageTrackingReport -Identity $reportId -ReportTemplate Summary -Status Delivered +} ``` This example gets the message tracking report for messages sent from one user to another. This example returns the summary of the message tracking report for a message that David Jones sent to Wendy Richardson. @@ -65,7 +75,7 @@ You need to run the Search-MessageTrackingReport cmdlet to find the message trac Type: MessageTrackingReportId Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -83,7 +93,7 @@ By default, each user can only see the message tracking reports for messages tha Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -96,7 +106,6 @@ Accept wildcard characters: False 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. - - Verbose: Full report information is returned, including server names and physical topology information. ```yaml @@ -113,8 +122,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -139,7 +146,7 @@ Using this switch improves performance, but the lack of display names might make Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -155,7 +162,7 @@ The RecipientPathFilter parameter specifies the email address of the recipient w Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -171,7 +178,7 @@ The Recipients parameter specifies the email addresses of the recipients when yo Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -184,14 +191,13 @@ Accept wildcard characters: False 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. - - Summary: Returns a summary for all recipients of the message. You specify the recipients by using the Recipients parameter. ```yaml Type: ReportTemplate Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -207,7 +213,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -220,20 +226,16 @@ Accept wildcard characters: False The Status parameter filters the results by the specified delivery status codes. Valid values are: - Delivered - - Read - - Pending - - Transferred - - Unsuccessful ```yaml Type: _DeliveryStatus Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -246,9 +248,7 @@ Accept wildcard characters: False 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. - - Medium: In addition to the data returned for the Low setting, the actual message tracking search results are also returned. - - High: Full diagnostic data is returned. You only need to use this parameter for troubleshooting message tracking issues. @@ -271,12 +271,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MigrationBatch.md b/exchange/exchange-ps/exchange/Get-MigrationBatch.md new file mode 100644 index 0000000000..ecc0d0aa97 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MigrationBatch.md @@ -0,0 +1,333 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MigrationBatch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MigrationBatch cmdlet to retrieve status information about the current migration batch. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Get-MigrationBatch [[-Identity] ] + [-Diagnostic] + [-DiagnosticArgument ] + [-DiagnosticInfo ] + [-DomainController ] + [-IncludeReport] + [-Partition ] + [-ResultSize ] + [-Status ] + [] +``` + +### BatchesFromEndpoint +``` +Get-MigrationBatch + [-Diagnostic] + [-DiagnosticArgument ] + [-DomainController ] + [-Endpoint ] + [-IncludeReport] + [-Status ] + [] +``` + +### BatchesByEndpoint +``` +Get-MigrationBatch + [-DiagnosticInfo ] + [-Endpoint ] + [-IncludeReport] + [-Partition ] + [-ResultSize ] + [] +``` + +### BatchesByStatus +``` +Get-MigrationBatch + [-DiagnosticInfo ] + [-IncludeReport] + [-Partition ] + [-ResultSize ] + [-Status ] + [] +``` + +## DESCRIPTION +The Get-MigrationBatch cmdlet displays status information about the current migration batch. This information includes the following information: + +- Status of the migration batch +- Total number of mailboxes being migrated +- Number of successfully completed migrations +- Migration errors +- Date and time when the migration was started and completed. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +**Note**: In the cloud-based service, if you don't use the TimeZone parameter in the New-MigrationBatch command, the default time zone for the migration batch is UTC. The CompleteAfter and CompleteAfterUTC properties will contain the same value (as will the StartAfter and StartAfterUTC properties). When you create the migration batch in the Exchange admin center (EAC), the time zone that's used is based on your regional configuration. + +## EXAMPLES + +### Example 1 +```powershell +Get-MigrationBatch -Identity LocalMove2 +``` + +This example displays status information for the migration batch LocalMove2. + +### Example 2 +```powershell +Get-MigrationBatch -Endpoint exsrv1.contoso.com +``` + +This example displays information about all migration batches associated with the migration endpoint exsrv1.contoso.com. + +## PARAMETERS + +### -Identity +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. + +```yaml +Type: MigrationBatchIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Diagnostic +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. + +Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, BatchesFromEndpoint +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DiagnosticArgument +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. + +```yaml +Type: String +Parameter Sets: Identity, BatchesFromEndpoint +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DiagnosticInfo +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: + +- attachmentid=String +- batch=String +- confirm +- duration=String +- endpoints +- endtime=DateTime +- maxsize=Int32 +- organization=String +- partition=String +- reportid=String +- reports +- showtimeline +- showtimeslots=String +- starttime=DateTime +- status=String +- storage +- type=String +- user=String +- verbose + +```yaml +Type: String +Parameter Sets: Identity, BatchesByEndpoint, BatchesByStatus +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Identity, BatchesFromEndpoint +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Endpoint +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. + +```yaml +Type: MigrationEndpointIdParameter +Parameter Sets: BatchesFromEndpoint, BatchesByEndpoint +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeReport +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Partition +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MailboxIdParameter +Parameter Sets: Identity, BatchesByEndpoint, BatchesByStatus +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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. + +```yaml +Type: Unlimited +Parameter Sets: Identity, BatchesByEndpoint, BatchesByStatus +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Status +The Status parameter returns a list of migration batches that have the specified status state. Use one of the following values: + +- Completed +- CompletedWithErrors +- Completing +- Corrupted +- Created +- Failed +- IncrementalSyncing +- Removing +- Starting +- Stopped +- Syncing +- Stopping +- Synced +- SyncedwithErrors +- Waiting + +```yaml +Type: MMigrationBatchStatus +Parameter Sets: Identity, BatchesFromEndpoint, BatchesByStatus +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-MigrationConfig.md b/exchange/exchange-ps/exchange/Get-MigrationConfig.md new file mode 100644 index 0000000000..1d8997faf8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MigrationConfig.md @@ -0,0 +1,144 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MigrationConfig + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MigrationConfig cmdlet to retrieve migration configuration settings on Exchange servers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Get-MigrationConfig [-DomainController ] + [] +``` + +### Partition +``` +Get-MigrationConfig [-Partition ] + [-IncludeSimplifiedGmailMigrationData] + [] +``` + +### AllPartitions +``` +Get-MigrationConfig [-AllPartitions] + [-IncludeSimplifiedGmailMigrationData] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MigrationConfig +``` + +This example retrieves the settings for the migration configuration. + +## PARAMETERS + +### -AllPartitions +This parameter is available only in the cloud-based service. + +{{ Fill AllPartitions Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: AllPartitions +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSimplifiedGmailMigrationData +This parameter is available only in the cloud-based service. + +{{ Fill IncludeSimplifiedGmailMigrationData Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Partition, AllPartitions +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Partition +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MailboxIdParameter +Parameter Sets: Partition +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/move-and-migration/Get-MigrationEndpoint.md b/exchange/exchange-ps/exchange/Get-MigrationEndpoint.md similarity index 76% rename from exchange/exchange-ps/exchange/move-and-migration/Get-MigrationEndpoint.md rename to exchange/exchange-ps/exchange/Get-MigrationEndpoint.md index aca3da05eb..8f8f5dd3c9 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationEndpoint.md +++ b/exchange/exchange-ps/exchange/Get-MigrationEndpoint.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-migrationendpoint +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MigrationEndpoint @@ -17,50 +16,57 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MigrationEndpoint cmdlet to retrieve migration endpoint settings for source or destination servers for cutover or staged Exchange migrations, IMAP migrations, and remote moves. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### ConnectionSettingsFilter ``` -Get-MigrationEndpoint -ConnectionSettings [-Diagnostic] - [-DiagnosticArgument ] [-DomainController ] [] +Get-MigrationEndpoint -ConnectionSettings + [-Diagnostic] + [-DiagnosticArgument ] + [-DomainController ] + [] ``` ### TypeFilter ``` -Get-MigrationEndpoint -Type [-Diagnostic] [-DiagnosticArgument ] - [-DomainController ] [-Partition ] [-DiagnosticInfo ] [] +Get-MigrationEndpoint -Type + [-Diagnostic] + [-DiagnosticArgument ] + [-DomainController ] + [-Partition ] + [-DiagnosticInfo ] + [] ``` ### Identity ``` -Get-MigrationEndpoint [[-Identity] ] [-Diagnostic] [-DiagnosticArgument ] - [-DomainController ] [-Partition ] [-DiagnosticInfo ] [] +Get-MigrationEndpoint [[-Identity] ] + [-Diagnostic] + [-DiagnosticArgument ] + [-DomainController ] + [-Partition ] + [-DiagnosticInfo ] + [] ``` ## DESCRIPTION The Get-MigrationEndpoint cmdlet retrieves settings for different types of migration: - Cross-forest move: Move mailboxes between two different on-premises Exchange forests. Cross-forest moves require the use of a RemoteMove endpoint. - -- Remote move: In a hybrid deployment, a remote move involves onboarding or offboarding migrations. Remote moves require the use of a RemoteMove endpoint. Onboarding moves mailboxes from an on-premises Exchange organization to Exchange Online in Office 365, and uses a RemoteMove endpoint as the source endpoint of the migration batch. Offboarding moves mailboxes from Exchange Online in Office 365 to an on-premises Exchange organization and uses a RemoteMove endpoint as the target endpoint of the migration batch. - -- Cutover Exchange migration: Migrate all mailboxes in an on-premises Exchange organization to Exchange Online in Office 365. Cutover Exchange migration requires the use of an Exchange endpoint. - -- Staged Exchange migration: Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online in Office 365. Staged Exchange migration requires the use of an Exchange endpoint. - -- IMAP migration: Migrate mailbox data from an on-premises Exchange organization or other email system to Exchange Online in Office 365. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP migrations require the use of an IMAP endpoint. - +- Remote move: In a hybrid deployment, a remote move involves onboarding or offboarding migrations. Remote moves require the use of a RemoteMove endpoint. Onboarding moves mailboxes from an on-premises Exchange organization to Exchange Online, and uses a RemoteMove endpoint as the source endpoint of the migration batch. Offboarding moves mailboxes from Exchange Online to an on-premises Exchange organization and uses a RemoteMove endpoint as the target endpoint of the migration batch. +- Cutover Exchange migration: Migrate all mailboxes in an on-premises Exchange organization to Exchange Online. Cutover Exchange migration requires the use of an Exchange endpoint. +- Staged Exchange migration: Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. Staged Exchange migration requires the use of an Exchange endpoint. +- IMAP migration: Migrate mailbox data from an on-premises Exchange organization or other email system to Exchange Online. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP migrations require the use of an IMAP endpoint. - Local: Move mailboxes between different servers or databases within a single on-premises Exchange forest. Local moves don't require the use of an endpoint. For more information about the different move and migration scenarios, see: -- [Mailbox moves in Exchange Server](https://docs.microsoft.com/Exchange/recipients/mailbox-moves) - -- [Manage on-premises mailbox moves in Exchange Server](https://docs.microsoft.com/Exchange/architecture/mailbox-servers/manage-mailbox-moves) +- [Mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/recipients/mailbox-moves) +- [Manage on-premises mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/architecture/mailbox-servers/manage-mailbox-moves) -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -73,6 +79,22 @@ This example retrieves the settings for the migration endpoint, OnboardingME01. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ConnectionSettings This parameter is available only in on-premises Exchange. @@ -94,7 +116,9 @@ Accept wildcard characters: False ### -Diagnostic This parameter is available only in on-premises Exchange. -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -130,7 +154,27 @@ Accept wildcard characters: False ### -DiagnosticInfo 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. +Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. Valid values are: + +- attachmentid=String +- batch=String +- confirm +- duration=String +- endpoints +- endtime=DateTime +- maxsize=Int32 +- organization=String +- partition=String +- reportid=String +- reports +- showtimeline +- showtimeslots=String +- starttime=DateTime +- status=String +- storage +- type=String +- user=String +- verbose ```yaml Type: String @@ -163,22 +207,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Partition This parameter is available only in the cloud-based service. @@ -201,11 +229,8 @@ Accept wildcard characters: False The Type parameter filters the results by the type of migration. Valid values for this parameter are: - ExchangeOutlookAnywhere: Cutover or staged Exchange migrations - - ExchangeRemoteMove: Remote moves and migrations - - IMAP: IMAP migrations - - PublicFolder: Public folder migrations ```yaml @@ -226,12 +251,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationStatistics.md b/exchange/exchange-ps/exchange/Get-MigrationStatistics.md similarity index 81% rename from exchange/exchange-ps/exchange/move-and-migration/Get-MigrationStatistics.md rename to exchange/exchange-ps/exchange/Get-MigrationStatistics.md index a749602c62..c397c884ee 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationStatistics.md +++ b/exchange/exchange-ps/exchange/Get-MigrationStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-migrationstatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MigrationStatistics @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MigrationStatistics cmdlet to view detailed information about migration requests. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MigrationStatistics [-Diagnostic] [-DiagnosticArgument ] [-DiagnosticInfo ] [-DomainController ] - [-Partition ] [] +Get-MigrationStatistics [-Diagnostic] + [-DiagnosticArgument ] + [-DiagnosticInfo ] + [-DomainController ] + [-Partition ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,7 +46,9 @@ This example returns the default statistics for the migration batches. ### -Diagnostic This parameter is available only in on-premises Exchange. -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -79,7 +84,27 @@ Accept wildcard characters: False ### -DiagnosticInfo 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. +Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. Valid values are: + +- attachmentid=String +- batch=String +- confirm +- duration=String +- endpoints +- endtime=DateTime +- maxsize=Int32 +- organization=String +- partition=String +- reportid=String +- reports +- showtimeline +- showtimeslots=String +- starttime=DateTime +- status=String +- storage +- type=String +- user=String +- verbose ```yaml Type: String @@ -135,12 +160,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUser.md b/exchange/exchange-ps/exchange/Get-MigrationUser.md similarity index 75% rename from exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUser.md rename to exchange/exchange-ps/exchange/Get-MigrationUser.md index 1455cbd5b4..e379851050 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUser.md +++ b/exchange/exchange-ps/exchange/Get-MigrationUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-migrationuser +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MigrationUser @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MigrationUser cmdlet to view information about move and migration users. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,6 +24,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-MigrationUser -MailboxGuid [-DomainController ] + [-IncludeAssociatedUsers] [-ResultSize ] [-Partition ] [] @@ -32,10 +32,9 @@ Get-MigrationUser -MailboxGuid ### StatusAndBatchId ``` -Get-MigrationUser [-BatchId ] - [-Status ] - [-StatusSummary ] +Get-MigrationUser [-BatchId ] [-Status ] [-StatusSummary ] [-DomainController ] + [-IncludeAssociatedUsers] [-ResultSize ] [-Partition ] [] @@ -45,12 +44,24 @@ Get-MigrationUser [-BatchId ] ``` Get-MigrationUser [[-Identity] ] [-DomainController ] + [-IncludeAssociatedUsers] [-ResultSize ] - [-Partition ] [] + [-Partition ] + [] +``` + +### EmailAddress +``` +Get-MigrationUser -EmailAddress + [-DomainController ] + [-IncludeAssociatedUsers] + [-ResultSize ] + [-Partition ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,8 +79,38 @@ Get-MigrationUser -MailboxGuid b6a6795c-a010-4f67-aaaa-da372d56fcb9 | Get-Migrat This example retrieves more detailed information about any ongoing migration for the user with the specified mailbox GUID. +### Example 3 +```powershell +Get-MigrationUser -EmailAddress TonySmith@contoso.com +``` + +This example retrieves status information about the recently migrated user, Tony Smith. + +### Example 4 +```powershell +Get-MigrationUser -EmailAddress TonySmith@contoso.com | Get-MigrationUserStatistics +``` + +This example retrieves more detailed information about any ongoing migration for the user with the specified email address. + ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -MailboxGuid The MailboxGuid parameter specifies the GUID of a mailbox for which you want to view the migration information. @@ -120,19 +161,37 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the particular user that you want to retrieve information about. The Identity parameter is represented as an email address. +### -EmailAddress +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: MigrationUserIdParameter -Parameter Sets: Identity +Type: EmailAddress +Parameter Sets: EmailAddress Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAssociatedUsers +This parameter is available only in the cloud-based service. + +{{ Fill IncludeAssociatedUsers Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -174,45 +233,25 @@ Accept wildcard characters: False The Status parameter returns information about migration users that have the specified status state. Use one of the following values: - Completed - - CompletedWithWarnings - - Completing - - CompletionFailed - - CompletionSynced - - Corrupted - - Failed - - IncrementalFailed - - IncrementalStopped - - IncrementalSynced - - IncrementalSyncing - - Provisioning - - ProvisionUpdating - - Queued - - Removing - - Starting - - Stopped - - Stopping - - Synced - - Syncing - - Validating ```yaml @@ -232,13 +271,9 @@ Accept wildcard characters: False The StatusSummary parameter returns abbreviated information about migration users that have the specified status value. Use one of the following values: - Active - - Completed - - Failed - - Stopped - - Synced ```yaml @@ -259,12 +294,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUserStatistics.md b/exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md similarity index 84% rename from exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUserStatistics.md rename to exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md index 2c127933c2..5e64b3de72 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUserStatistics.md +++ b/exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-migrationuserstatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MigrationUserStatistics @@ -17,18 +16,27 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MigrationUserStatistics cmdlet to view detailed information about the migration requested for a specific user. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MigrationUserStatistics [-Identity] [-Diagnostic] [-DiagnosticArgument ] - [-DiagnosticInfo ] [-DomainController ] [-IncludeReport] [-LimitSkippedItemsTo ] - [-IncludeSkippedItems] [-Partition ] [-SkipSubscription] [] +Get-MigrationUserStatistics [-Identity] + [-Diagnostic] + [-DiagnosticArgument ] + [-DiagnosticInfo ] + [-DomainController ] + [-IncludeCopilotReport] + [-IncludeReport] + [-IncludeSkippedItems] + [-LimitSkippedItemsTo ] + [-Partition ] + [-SkipSubscription] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,10 +56,10 @@ This example displays the number of mailbox items that failed to migrate, which ### Example 3 ```powershell -Get-MigrationUserStatistics -Identity davidp@corp.contoso.com -LimitSkippedItemsTo 20 | Format-List SkippedItemCount,SkippedItems +Get-MigrationUserStatistics -Identity davidp@corp.contoso.com -IncludeSkippedItems | Select-Object -ExpandProperty SkippedItems | Format-List DateReceived, Subject ``` -This example displays results information in the SkippedItems property for a maximum of 20 skipped items. +This example displays results information in the SkippedItems property. ### Example 4 ```powershell @@ -95,7 +103,9 @@ Accept wildcard characters: False ### -Diagnostic This parameter is available only in on-premises Exchange. -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -164,8 +174,26 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IncludeCopilotReport +This parameter is available only in the cloud-based service. + +{{ Fill IncludeCopilotReport Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IncludeReport -The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. +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 @@ -251,12 +279,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-MobileDevice.md b/exchange/exchange-ps/exchange/Get-MobileDevice.md similarity index 83% rename from exchange/exchange-ps/exchange/devices/Get-MobileDevice.md rename to exchange/exchange-ps/exchange/Get-MobileDevice.md index f64162e383..7da6e04fbb 100644 --- a/exchange/exchange-ps/exchange/devices/Get-MobileDevice.md +++ b/exchange/exchange-ps/exchange/Get-MobileDevice.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-mobiledevice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MobileDevice @@ -15,9 +14,9 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the Get-MobileDevice cmdlet to get the list of devices in your organization that have active Exchange ActiveSync partnerships. +Use the Get-MobileDevice cmdlet to get the list of devices in your organization that have active partnerships. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,7 +32,8 @@ Get-MobileDevice -Mailbox [-ResultSize ] [-SortBy ] [-RestApi] - [-UniversalOutlook] [] + [-UniversalOutlook] + [] ``` ### Identity @@ -48,22 +48,23 @@ Get-MobileDevice [[-Identity] ] [-ResultSize ] [-SortBy ] [-RestApi] - [-UniversalOutlook] [] + [-UniversalOutlook] + [] ``` ## DESCRIPTION The Get-MobileDevice cmdlet returns identification, configuration, and status information for each mobile device. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-MobileDevice -Mailbox "TonySmith" +Get-MobileDevice -Mailbox "Tony Smith" ``` -This example returns all the Exchange ActiveSync mobile devices that Tony Smith has used that are associated with his mailbox. +This example returns all the mobile devices that Tony Smith has used that are associated with his mailbox. ### Example 2 ```powershell @@ -74,36 +75,49 @@ This example returns a summary list of all mobile devices in the organization. ### Example 3 ```powershell -Get-MobileDevice -Identity lila\ExchangeActiveSyncDevices\Android§android94732903 | Format-List +Get-MobileDevice -Identity Lila\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac | Format-List ``` This example returns detailed information about the specified device on Lila's mailbox. ## PARAMETERS +### -Identity +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`) +- Distinguished name (DN) +- GUID (same as ExchangeObjectId) + +```yaml +Type: MobileDeviceIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Mailbox The Mailbox parameter filters the results by mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) +You can't use this parameter with the Identity parameter. + ```yaml Type: MailboxIdParameter Parameter Sets: Mailbox @@ -118,7 +132,7 @@ Accept wildcard characters: False ``` ### -ActiveSync -The ActiveSync switch specifies whether to include mobile devices that synchronize with Exchange ActiveSync. You don't need to specify a value with this switch. +The ActiveSync switch filters the results by Exchange ActiveSync devices. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -152,56 +166,36 @@ Accept wildcard characters: False ``` ### -Filter -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. +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. - Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can filter by the following properties: - ClientType - - DeviceAccessControlRule - - DeviceAccessState - - DeviceAccessStateReason - - DeviceActiveSyncVersion - - DeviceId - - DeviceImei - - DeviceMobileOperator - - DeviceModel - - DeviceOS - - DeviceOSLanguage - - DeviceTelephoneNumber - - DeviceType - - DeviceUserAgent - - FirstSyncTime - - FriendlyName - - ProvisioningFlags - - UserDisplayName ```yaml @@ -217,26 +211,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- DeviceID - -```yaml -Type: MobileDeviceIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Monitoring This parameter is available only in on-premises Exchange. @@ -261,11 +235,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -316,38 +287,24 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - DeviceAccessControlRule - - DeviceAccessState - - DeviceAccessStateReason - - DeviceId - - DeviceImei - - DeviceMobileOperator - - DeviceModel - - DeviceOS - - DeviceOSLanguage - - DeviceTelephoneNumber - - DeviceType - - DeviceUserAgent - - FirstSyncTime - - FriendlyName - - UserDisplayName ```yaml @@ -400,12 +357,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Get-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md similarity index 80% rename from exchange/exchange-ps/exchange/devices/Get-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md index bd50dfdd41..5a1d4c078b 100644 --- a/exchange/exchange-ps/exchange/devices/Get-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-mobiledevicemailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MobileDeviceMailboxPolicy @@ -17,19 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MobileDeviceMailboxPolicy cmdlet to retrieve the Mobile Device mailbox policy settings for a specific Mobile Device mailbox policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MobileDeviceMailboxPolicy [[-Identity] ] [-DomainController ] +Get-MobileDeviceMailboxPolicy [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION -A Mobile Device mailbox policy is a group of settings that specifies how mobile devices enabled for Exchange ActiveSync connect to the computer running Exchange. Exchange supports multiple Mobile Device mailbox policies. The Get-MobileDeviceMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment settings. +A Mobile Device mailbox policy is a group of settings that specifies how mobile devices connect Exchange. Exchange supports multiple mobile device mailbox policies. The Get-MobileDeviceMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,37 +49,37 @@ This example returns the policy settings for the Mobile Device mailbox policy De ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the policy name. ```yaml -Type: Fqdn +Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the policy name. +### -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. ```yaml -Type: MailboxPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -88,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md b/exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md new file mode 100644 index 0000000000..d493f60367 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md @@ -0,0 +1,305 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MobileDeviceStatistics + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-MobileDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices. + +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXOMobileDeviceStatistics cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Get-MobileDeviceStatistics [-Identity] + [-ActiveSync] + [-DomainController ] + [-GetMailboxLog] + [-NotificationEmailAddresses ] + [-OWAforDevices] + [-ShowRecoveryPassword] + [-RestApi] + [-UniversalOutlook] + [-UseCustomRouting] + [] +``` + +### Mailbox +``` +Get-MobileDeviceStatistics -Mailbox + [-ActiveSync] + [-DomainController ] + [-GetMailboxLog] + [-NotificationEmailAddresses ] + [-OWAforDevices] + [-ShowRecoveryPassword] + [-RestApi] + [-UniversalOutlook] + [-UseCustomRouting] + [] +``` + +## DESCRIPTION +The Get-MobileDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MobileDeviceStatistics -Identity TonySmith\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac +``` + +This example retrieves the statistics for the specified mobile phone. + +### Example 2 +```powershell +$UserList = Get-CASMailbox -ResultSize unlimited -Filter "HasActiveSyncDevicePartnership -eq `$true -and -not DisplayName -like 'CAS_{*'" + +$UserList | foreach {Get-MobileDeviceStatistics -Mailbox $_.Identity} +``` + +This example uses the Get-CASMailbox cmdlet to determine who in the organization has an Exchange ActiveSync mobile device. For each mobile device, the Exchange ActiveSync device statistics are retrieved. + +**Note**: For more information about OPATH filter syntax, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +### Example 3 +```powershell +Get-MobileDeviceStatistics -Mailbox "Tony Smith" -GetMailboxLog -NotificationEmailAddresses "admin@contoso.com" +``` + +This example retrieves the statistics for the mobile phone that's configured to synchronize with Tony Smith's mailbox. It also outputs the log file and sends it to the System Administrator at admin@contoso.com. + +## PARAMETERS + +### -Identity +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`) +- Distinguished name (DN) +- GUID (same as ExchangeObjectId) + +You can't use this parameter with the Mailbox parameter. + +```yaml +Type: MobileDeviceIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Mailbox +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Identity parameter. + +```yaml +Type: MailboxIdParameter +Parameter Sets: Mailbox +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ActiveSync +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GetMailboxLog +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationEmailAddresses +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OWAforDevices +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowRecoveryPassword +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestApi +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UniversalOutlook +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/server-health-and-performance/Get-MonitoringItemHelp.md b/exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md similarity index 82% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-MonitoringItemHelp.md rename to exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md index 2cd7d651d6..b720090806 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-MonitoringItemHelp.md +++ b/exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-monitoringitemhelp +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MonitoringItemHelp @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MonitoringItemHelp cmdlet to discover the monitoring items that you can use to return health information about your Exchange servers. Monitoring items are preconfigured to help you with your server health and monitoring. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MonitoringItemHelp [-Identity] -Server [] +Get-MonitoringItemHelp [-Identity] -Server + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -35,12 +35,12 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Get-MonitoringItemHelp -Server Exch01 -Identity OutlookMapiHttp.Proxy\CrashEvent.msexchangemapifrontendapppoolEscalate\msexchangemapifrontendapppool | Format-List ``` -This example retrieves health set information for a monitoring item on the server named Exch01 and displays the output without truncating the results.. +This example retrieves health set information for a monitoring item on the server named Exch01 and displays the output without truncating the results. ## PARAMETERS ### -Identity -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. +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 @@ -59,11 +59,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -84,12 +81,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-MonitoringItemIdentity.md b/exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md similarity index 86% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-MonitoringItemIdentity.md rename to exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md index 3a582ec2a1..993413da94 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-MonitoringItemIdentity.md +++ b/exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-monitoringitemidentity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-MonitoringItemIdentity @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-MonitoringItemIdentity cmdlet to discover the monitoring items that you can use to return health information about your Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-MonitoringItemIdentity [-Identity] -Server [] +Get-MonitoringItemIdentity [-Identity] -Server + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,11 +59,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -84,12 +81,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-MoveRequest.md b/exchange/exchange-ps/exchange/Get-MoveRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/move-and-migration/Get-MoveRequest.md rename to exchange/exchange-ps/exchange/Get-MoveRequest.md index e09ff169c2..9bd1b19333 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MoveRequest.md +++ b/exchange/exchange-ps/exchange/Get-MoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-moverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MoveRequest @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-MoveRequest cmdlet to view the detailed status of an ongoing asynchronous mailbox move that was initiated by using the New-MoveRequest cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -51,6 +50,7 @@ Get-MoveRequest [-BatchName ] [-ResultSize ] [-SortBy ] [-SourceDatabase ] + [-Status ] [-Suspend ] [-SuspendWhenReadyToComplete ] [-TargetDatabase ] @@ -60,7 +60,7 @@ Get-MoveRequest [-BatchName ] ## DESCRIPTION The search criteria for the Get-MoveRequest cmdlet is a Boolean And statement. If you use multiple parameters, it narrows your search and reduces your search results. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -91,45 +91,27 @@ This example retrieves the status of move requests in the FromDB01ToDB02 batch t 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can use this parameter with the following parameters: - BatchName - - HighPriority - - MoveStatus - - Offline - - Protect - - RemoteHostName - - SourceDatabase - - Suspend - - SuspendWhenReadyToComplete - - TargetDatabase ```yaml @@ -168,7 +150,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -205,35 +187,20 @@ Accept wildcard characters: False The Flags parameter specifies the move type to retrieve information for. The following values may be used: - CrossOrg - - HighPriority - - IntraOrg - - Join - - MoveOnlyArchiveMailbox - - MoveOnlyPrimaryMailbox - - None - - Offline - - Protected - - Pull - - Push - - RemoteLegacy - - Split - - Suspend - - SuspendWhenReadyToComplete - - TargetIsAggregatedMailbox ```yaml @@ -291,21 +258,13 @@ Accept wildcard characters: False The MoveStatus parameter returns move requests in the specified status. You can use the following values: - AutoSuspended - - Completed - - CompletedWithWarning - - CompletionInProgress - - Failed - - InProgress - - Queued - - Retrying - - Suspended You can't use this parameter with the Identity parameter. @@ -314,7 +273,7 @@ You can't use this parameter with the Identity parameter. Type: RequestStatus Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -345,18 +304,15 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -391,23 +347,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -460,21 +407,19 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName - - Alias ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -489,9 +434,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -509,6 +452,36 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Status +This parameter is available only in the cloud-based service. + +The Status parameter filters the results by status. Valid values are: + +- AutoSuspended +- Completed +- CompletedWithSkippedItems +- CompletedWithWarning +- CompletionInProgress +- Failed +- InProgress +- Queued +- Retrying +- Suspended +- Synced + +```yaml +Type: RequestStatus +Parameter Sets: Filtering +Aliases: MoveStatus +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Suspend The Suspend parameter specifies whether to return mailboxes with moves that have been suspended. This parameter accepts $true or $false. @@ -551,9 +524,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -576,12 +547,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-MoveRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md similarity index 85% rename from exchange/exchange-ps/exchange/move-and-migration/Get-MoveRequestStatistics.md rename to exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md index 1b0894ff01..8f312cf0ae 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MoveRequestStatistics.md +++ b/exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-moverequeststatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-MoveRequestStatistics @@ -19,7 +18,7 @@ Use the Get-MoveRequestStatistics cmdlet to view detailed information about move Some of the failure messages that are returned by this cmdlet are temporary and don't indicate that a request has actually failed. If the Status value is Queued or InProgress, then the request is proceeding normally. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -37,7 +36,9 @@ Get-MoveRequestStatistics [-Identity] ### IdentityCloud ``` Get-MoveRequestStatistics [-Identity] + [-Analysis] [-DiagnosticInfo ] + [-DiagnosticOnly] [-IncludeReport] [-ProxyToMailbox ] [-ReportOnly] @@ -46,7 +47,8 @@ Get-MoveRequestStatistics [-Identity] ### MigrationMoveRequestQueue ``` -Get-MoveRequestStatistics -MoveRequestQueue [-MailboxGuid ] +Get-MoveRequestStatistics -MoveRequestQueue + [-MailboxGuid ] [-Diagnostic] [-DiagnosticArgument ] [-DomainController ] @@ -57,13 +59,14 @@ Get-MoveRequestStatistics -MoveRequestQueue [-MailboxGuid ### MigrationMRSInstance ``` -Get-MoveRequestStatistics -MRSInstance [-MailboxGuid ] +Get-MoveRequestStatistics -MRSInstance + [-MailboxGuid ] [-DomainController ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -102,23 +105,24 @@ Get-MoveRequestStatistics -MRSInstance CAS01.contoso.com -MailboxGuid b6a6795c-a In Exchange Server 2010, this example returns default statistics for a mailbox that has been moved by the instance of the Microsoft Exchange Mailbox Replication service running on the server CAS01. +### Example 6 +```powershell +Get-MoveRequestStatistics tony@contoso.com -IncludeReport -DiagnosticInfo Verbose | Export-Clixml "C:\Data\MoveReport.xml" +``` + +This example exports the move request information so you can later import it into the MRS_Explorer.ps1 script for analysis. For more information, see [MRS-Explorer](https://github.com/zarkatech/MRS-Explorer). + ## PARAMETERS ### -Identity The Identity parameter specifies the identity of the mailbox or mail user. You can use one of the following values: - GUID - - Distinguished name (DN) - - Domain\\Account - - User principal name (UPN) - - Legacy Exchange DN - - SMTP address - - Alias You can use this parameter with the MoveRequestQueue or MailboxGuid parameters. @@ -144,9 +148,7 @@ This parameter is for debugging purposes only. The MoveRequestQueue parameter specifies the mailbox database on which the move request resides. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity or MRSInstance parameters. @@ -165,7 +167,7 @@ Accept wildcard characters: False ``` ### -MRSInstance -This parameter is available or functional only in on-premises 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. @@ -184,6 +186,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Analysis +This parameter is available only in the cloud-based service. + +{{ Fill Analysis Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: IdentityCloud +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Diagnostic This parameter is available only in on-premises Exchange. @@ -207,9 +227,7 @@ Accept wildcard characters: False ### -DiagnosticArgument This parameter is available only in on-premises Exchange. -The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. You don't need to specify a value with this switch. - -Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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 @@ -227,7 +245,11 @@ Accept wildcard characters: False ### -DiagnosticInfo 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. +Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. Valid values are: + +- ShowTimeline +- ShowTimeslot +- Verbose ```yaml Type: String @@ -242,6 +264,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DiagnosticOnly +This parameter is available only in the cloud-based service. + +{{ Fill DiagnosticOnly Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: IdentityCloud +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DomainController This parameter is available only in on-premises Exchange. @@ -302,23 +342,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -355,12 +386,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-MxRecordReport.md b/exchange/exchange-ps/exchange/Get-MxRecordReport.md new file mode 100644 index 0000000000..1600495130 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MxRecordReport.md @@ -0,0 +1,90 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-MxRecordReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-MxRecordReport cmdlet to view information about the mail exchanger (MX) records that are configured for a specified domain. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MxRecordReport [-Domain ] + [-ProbeTag ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MxRecordReport -Domain contoso.com +``` + +This example shows the MX record information for the contoso.com domain. + +## PARAMETERS + +### -Domain +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-MyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md new file mode 100644 index 0000000000..ad5461513b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +--- + +# Get-MyAnalyticsFeatureConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-MyAnalyticsFeatureConfig cmdlet to view the availability and feature status of MyAnalytics for the specified user. + +**Note**: This cmdlet replaces the Get-UserAnalyticsConfig cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-MyAnalyticsFeatureConfig -Identity + [-ResultSize ] + [] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +c:\users\vikram Get-MyAnalyticsFeatureConfig -Identity vikram@contoso.com + +UserId : vikram@contoso.com +PrivacyMode : opt-in +IsDashboardEnabled : true +IsAddInEnabled : true +IsDigestEmailEnabled : false +``` + +This example and the corresponding output shows the MyAnalytics configuration for the user vikram@contoso.com. MyAnalytics is available to Vikram (the PrivacyMode property value is opt-in). The only feature that's disabled is digest email messages. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-NetworkConnectionInfo.md b/exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Get-NetworkConnectionInfo.md rename to exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md index e8c920ecd9..3b753febcb 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-NetworkConnectionInfo.md +++ b/exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-networkconnectioninfo +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-NetworkConnectionInfo @@ -17,28 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Get-NetworkConnectionInfo cmdlet to view the network configuration information for all network adapters configured on the local server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-NetworkConnectionInfo [[-Identity] ] [-DomainController ] [] +Get-NetworkConnectionInfo [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION This cmdlet retrieves the following configuration information for each network adapter configured on the server: - Name: This field displays the name of the network adapter. This name indicates the manufacturer and model of the network adapter or the administrator-specified name of the network adapter. - - DnsServers: This field displays the DNS servers used by the network adapter. The server names are separated by commas. - - IPAddresses: This field displays the IP addresses used by the network adapter. The IP addresses are separated by commas. - - AdapterGuid: This field displays the GUID assigned to the network adapter by Windows. - - MacAddress: This field displays the media access control (MAC) address of the network adapter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,47 +48,44 @@ This example retrieves network configuration information for all network adapter ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the server you want to query. You can use any value that uniquely identifies the server. For example: -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. +- Name +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +If you don't use the Identity parameter, the command is run on the local server. ```yaml -Type: Fqdn +Type: ServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the server you want to query. You can use any value that uniquely identifies the server. For example: - -- Name - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -If you don't use the Identity parameter, the command is run on the local server. +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. ```yaml -Type: ServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -100,12 +94,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-Notification.md b/exchange/exchange-ps/exchange/Get-Notification.md similarity index 85% rename from exchange/exchange-ps/exchange/organization/Get-Notification.md rename to exchange/exchange-ps/exchange/Get-Notification.md index 373c845017..a354e891db 100644 --- a/exchange/exchange-ps/exchange/organization/Get-Notification.md +++ b/exchange/exchange-ps/exchange/Get-Notification.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-notification +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-Notification @@ -15,32 +14,48 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the Get-Notification cmdlet to view notification events that are shown in the notification viewer in the Exchange admin center (EAC). These notification events are related to: +> [!NOTE] +> This cmdlet will be deprecated in the cloud-based service. The classic Exchange admin center was deprecated in the cloud-based service in 2023. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the Get-Notification cmdlet to view notification events that are shown in the notification viewer in the Exchange admin center (EAC). These notifications are related to the following events: + +- Mailbox moves and migrations. +- Expiring and expired certificates. +- Exporting mailbox content to .pst files. +- Importing mailbox content from .pst files. +- Restoring deleted mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Settings ``` Get-Notification [-Settings] -ProcessType - [-DomainController ] [] + [-DomainController ] + [] ``` ### Identity ``` -Get-Notification [[-Identity] ] [-Summary] - [-DomainController ] [] +Get-Notification [[-Identity] ] + [-Summary] + [-DomainController ] + [] ``` ### Filter ``` -Get-Notification [-ProcessType ] [-ResultSize ] [-StartDate ] [-Summary] - [-DomainController ] [] +Get-Notification [-ProcessType ] + [-ResultSize ] + [-StartDate ] + [-Summary] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,6 +82,22 @@ This example displays detailed information for the specified notification event. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Settings This parameter is available only in on-premises Exchange. @@ -107,33 +138,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -ProcessType The ProcessType parameter filters the results by the type of notification event. Valid values are: - CertExpiry - - ExportPST - - ImportPST - - MailboxRestore - - Migration ```yaml @@ -181,7 +192,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: ExDateTime @@ -219,12 +230,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-OMEConfiguration.md b/exchange/exchange-ps/exchange/Get-OMEConfiguration.md new file mode 100644 index 0000000000..801c20e7db --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-OMEConfiguration.md @@ -0,0 +1,80 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-OMEConfiguration + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-OMEConfiguration cmdlet to view Microsoft Purview Message Encryption configurations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-OMEConfiguration [[-Identity] ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-OMEConfiguration +``` + +This example returns a summary list of all OME configurations in the organization. + +### Example 2 +```powershell +Get-OMEConfiguration | Format-List +``` + +This example returns detailed information for all OME configurations in the organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-OMEMessageStatus.md b/exchange/exchange-ps/exchange/Get-OMEMessageStatus.md new file mode 100644 index 0000000000..1162642bbb --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-OMEMessageStatus.md @@ -0,0 +1,71 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-OMEMessageStatus + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-OMEMessageStatus cmdlet to view the Microsoft Purview Message Encryption revocation status for a specific message. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-OMEMessageStatus -MessageId + [] +``` + +## DESCRIPTION +If encryption for the message was successfully revoked, the command will return the message: `The encrypted email with the subject "" and Message ID "" was successfully revoked`. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-OMEMessageStatus -MessageId "" +``` + +This example returns the encryption revocation status for the specified message. + +## PARAMETERS + +### -MessageId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-OabVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md similarity index 86% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-OabVirtualDirectory.md rename to exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md index 90ea69560a..274bd7b330 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-OabVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/get-oabvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-OabVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-OabVirtualDirectory cmdlet to view offline address book (OAB) virtual directories(OAB distribution points) that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -40,7 +39,7 @@ Get-OabVirtualDirectory [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,15 +66,36 @@ This example returns detailed information for the OAB virtual directory named "O ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID + +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. + +You can't use the Identity and Server parameters in the same command. + +```yaml +Type: VirtualDirectoryIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Server 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -94,7 +114,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -125,32 +147,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 \\\Name - -- Distinguished name (DN) - -- GUID - -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. - -You can't use the Identity and Server parameters in the same command. - -```yaml -Type: VirtualDirectoryIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -ShowMailboxVirtualDirectories The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch. @@ -176,12 +172,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-OfflineAddressBook.md b/exchange/exchange-ps/exchange/Get-OfflineAddressBook.md similarity index 84% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-OfflineAddressBook.md rename to exchange/exchange-ps/exchange/Get-OfflineAddressBook.md index 8748377a46..dbf02a696b 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-OfflineAddressBook.md +++ b/exchange/exchange-ps/exchange/Get-OfflineAddressBook.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/get-offlineaddressbook +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-OfflineAddressBook @@ -17,24 +16,28 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-OfflineAddressBook cmdlet to view offline address books (OABs). -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Server ``` -Get-OfflineAddressBook -Server [-DomainController ] [] +Get-OfflineAddressBook -Server + [-DomainController ] + [] ``` ### Identity ``` -Get-OfflineAddressBook [[-Identity] ] [-DomainController ] [] +Get-OfflineAddressBook [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,21 +64,39 @@ This example returns specific properties for all existing OABs, including the Ge ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID + +You can't use this parameter with the Server parameter. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Server 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. +**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. The Server parameter returns all of the OABs that are generated by the specified Exchange 2010 or earlier server. You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - FQDN - - ExchangeLegacyDN - - GUID You can't use this parameter with the Identity parameter. @@ -111,41 +132,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -You can't use this parameter with the Server parameter. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md new file mode 100644 index 0000000000..18d268514c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md @@ -0,0 +1,88 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-OnPremisesOrganization + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-OnPremisesOrganization cmdlet to retrieve settings for the OnPremisesOrganization object that has been created for a hybrid deployment. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-OnPremisesOrganization [[-Identity] ] + [] +``` + +## DESCRIPTION +The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. You can use the Get-OnPremisesOrganization cmdlet to view the properties of the OnPremisesOrganization object in the Microsoft 365 organization. + +Manual modification of this object may result in hybrid deployment misconfiguration. We strongly recommend that you use the Hybrid Configuration wizard to modify this object in the Microsoft 365 organization. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-OnPremisesOrganization -Identity ExchangeMail | Format-List +``` + +This example retrieves the on-premises organization settings for ExchangeMail using the Identity parameter. + +### Example 2 +```powershell +Get-OnPremisesOrganization -DomainController 'mail.contoso.com' | Format-List +``` + +This example retrieves the on-premises organization settings by using the FQDN of the domain controller. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the identity of the on-premises organization object. You can use the following values: + +- Canonical name +- GUID +- Name + +```yaml +Type: OnPremisesOrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-OnlineMeetingConfiguration.md b/exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md new file mode 100644 index 0000000000..57d2252911 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md @@ -0,0 +1,102 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-OnlineMeetingConfiguration + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Get-OnlineMeetingConfiguration cmdlet to view status and usage information about Skype Meetings and Skype for Business Online for mailboxes. Skype Meetings automatically includes Skype for Business Online conference join information in Exchange Online meeting invitations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-OnlineMeetingConfiguration [-Identity] + [-DomainController ] + [] +``` + +## DESCRIPTION +Exchange Online maintains a per-user cache of Skype for Business Online meeting information that's updated every 24 hours. The Get-OnlineMeetingConfiguration cmdlet provides the following information about the Skype Meetings configuration and the Skype for Business Online meeting information for the user: + +- IsAutoOnlineMeetingEnabled: Indicates if Skype Meetings is enabled for the mailbox. +- OnlineMeetingInfo: Skype for Business Online meeting coordinates. +- LastSyncTime: The last time Exchange Online successfully synchronized meeting coordinates from Skype for Business Online. +- LastSuccessfulSyncTime: The last time Exchange Online successfully cleaned the cached of used Skype for Business Online meeting coordinates. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-OnlineMeetingConfiguration -Identity carlam@fourthcoffee.com +``` + +This example gets the Skype Meetings configuration for the specified mailbox. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-OrganizationConfig.md b/exchange/exchange-ps/exchange/Get-OrganizationConfig.md similarity index 83% rename from exchange/exchange-ps/exchange/organization/Get-OrganizationConfig.md rename to exchange/exchange-ps/exchange/Get-OrganizationConfig.md index 191818c8a9..0d00218842 100644 --- a/exchange/exchange-ps/exchange/organization/Get-OrganizationConfig.md +++ b/exchange/exchange-ps/exchange/Get-OrganizationConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-organizationconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-OrganizationConfig @@ -17,16 +16,17 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-OrganizationConfig cmdlet to get configuration data for an Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-OrganizationConfig [-DomainController ] [] +Get-OrganizationConfig [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,9 +42,9 @@ This example gets the organization configuration information for the domain cont Get-OrganizationConfig | Export-CliXML C:\Data\MyFile.xml ``` -This example gets the configuration information for the tenant organization. +This example gets the configuration information for the cloud-based organization. -For more information, see [Troubleshoot a hybrid deployment](https://docs.microsoft.com/exchange/hybrid-deployment/troubleshoot-a-hybrid-deployment). +For more information, see [Troubleshoot a hybrid deployment](https://learn.microsoft.com/exchange/hybrid-deployment/troubleshoot-a-hybrid-deployment). ### Example 3 ```powershell @@ -84,12 +84,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-OrganizationRelationship.md b/exchange/exchange-ps/exchange/Get-OrganizationRelationship.md similarity index 84% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-OrganizationRelationship.md rename to exchange/exchange-ps/exchange/Get-OrganizationRelationship.md index d0fdf631c4..0c2f80f334 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-OrganizationRelationship.md +++ b/exchange/exchange-ps/exchange/Get-OrganizationRelationship.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-organizationrelationship -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-OrganizationRelationship @@ -17,16 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-OrganizationRelationship cmdlet to retrieve settings for an organization relationship that has been created for federated sharing with other federated Exchange organizations or for hybrid deployments with Exchange Online. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-OrganizationRelationship [[-Identity] ] [-DomainController ] [] +Get-OrganizationRelationship [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,43 +47,41 @@ This example retrieves the organization relationship settings by using the FQDN ## PARAMETERS -### -DomainController -This parameter is available only in on-premises Exchange. +### -Identity +The Identity parameter specifies the identity of the organizational relationship. You can use the following values: -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +- Canonical name +- GUID +- Name ```yaml -Type: Fqdn +Type: OrganizationRelationshipIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identity of the organizational relationship. You can use the following values: - -- Canonical name - -- GUID +### -DomainController +This parameter is available only in on-premises Exchange. -- Name +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: OrganizationRelationshipIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -91,12 +90,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-OrganizationSegment.md b/exchange/exchange-ps/exchange/Get-OrganizationSegment.md new file mode 100644 index 0000000000..12687a5a45 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-OrganizationSegment.md @@ -0,0 +1,92 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-OrganizationSegment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-OrganizationSegment cmdlet to view organization segments in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### OrganizationSegmentsDefault (Default) +``` +Get-OrganizationSegment [] +``` + +### Identity +``` +Get-OrganizationSegment [[-Identity] ] + [] +``` + +## DESCRIPTION +Segments are defined by using certain [attributes](https://learn.microsoft.com/purview/information-barriers-attributes) in Microsoft Entra ID. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-OrganizationSegment | Format-List Name,UserGroupFilter +``` + +This example returns a summary list of all organization segments. + +### Example 2 +```powershell +Get-OrganizationSegment -Identity "Engineering Group" +``` + +This example returns detailed information about the organization segment named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- ExchangeObjectId (not the ExoSegmentId) + +```yaml +Type: PolicyIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes) + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/active-directory/Get-OrganizationalUnit.md b/exchange/exchange-ps/exchange/Get-OrganizationalUnit.md similarity index 85% rename from exchange/exchange-ps/exchange/active-directory/Get-OrganizationalUnit.md rename to exchange/exchange-ps/exchange/Get-OrganizationalUnit.md index d40915cb69..01e951b29f 100644 --- a/exchange/exchange-ps/exchange/active-directory/Get-OrganizationalUnit.md +++ b/exchange/exchange-ps/exchange/Get-OrganizationalUnit.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-organizationalunit +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-OrganizationalUnit @@ -17,16 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-OrganizationalUnit cmdlet to view a list of organizational units (OUs) that exist in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Get-OrganizationalUnit [[-Identity] ] [-SingleNodeOnly] +Get-OrganizationalUnit [[-Identity] ] + [-SingleNodeOnly] [-DomainController ] [-IncludeContainers] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ### Search @@ -34,13 +35,14 @@ Get-OrganizationalUnit [[-Identity] ] [-S Get-OrganizationalUnit [-SearchText ] [-DomainController ] [-IncludeContainers] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ## DESCRIPTION The Get-OrganizationalUnit cmdlet is used by the Exchange admin center to populate fields that display OU information. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +53,7 @@ Get-OrganizationalUnit "North America" -SingleNodeOnly | Format-Table Name, Dist This example retrieves a list of the first level child OUs beneath the North America OU and formats the output so that only the Name and DistinguishedName properties are displayed. -For more information about pipelining and the Format-Table cmdlet, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining and the Format-Table cmdlet, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ### Example 2 ```powershell @@ -60,7 +62,7 @@ Get-OrganizationalUnit -SearchText "Executives" | Format-Table Name, Distinguish This example retrieves a list of OUs that match the text string "Executives" and formats the output so that only the Name and DistinguishedName properties are displayed. -For more information about pipelining and the Format-Table cmdlet, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining and the Format-Table cmdlet, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ## PARAMETERS @@ -68,11 +70,8 @@ For more information about pipelining and the Format-Table cmdlet, see [About Pi 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 - - Canonical name - - Distinguished name (DN) - - GUID You can use this parameter with the SearchText parameter. @@ -179,12 +178,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-OutboundConnector.md b/exchange/exchange-ps/exchange/Get-OutboundConnector.md similarity index 80% rename from exchange/exchange-ps/exchange/mail-flow/Get-OutboundConnector.md rename to exchange/exchange-ps/exchange/Get-OutboundConnector.md index 367dbc49b8..ef832c3069 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-OutboundConnector.md +++ b/exchange/exchange-ps/exchange/Get-OutboundConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-outboundconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Get-OutboundConnector @@ -17,22 +16,22 @@ This cmdlet is available only in the cloud-based service. Use the Get-OutboundConnector cmdlet to view the configuration information for an Outbound connector in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-OutboundConnector [[-Identity] ] - [-IncludeTestModeConnectors ] [-IsTransportRuleScoped ] [] + [-IncludeTestModeConnectors ] + [-IsTransportRuleScoped ] + [-ResultSize ] + [] ``` ## DESCRIPTION Outbound connectors send email messages to remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,9 +48,7 @@ This example displays detailed information about the Outbound connector named Co 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 - - Distinguished name (DN) - - GUID ```yaml @@ -71,8 +68,7 @@ Accept wildcard characters: False 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. - -- $false: All Outbound connectors that aren't in test mode are returned in the results.. This is the default value. +- $false: All Outbound connectors that aren't in test mode are returned in the results. This is the default value. You configure an Outbound connector in test mode by using the TestMode parameter on the New-OutboundConnector or Set-OutboundConnector cmdlets. @@ -93,8 +89,7 @@ Accept wildcard characters: False 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. - -- $false: All Outbound connectors that aren't scoped to transport rules are returned in the results.. This is the default value. +- $false: All Outbound connectors that aren't scoped to transport rules are returned in the results. This is the default value. You scope a transport rule to a specific Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. @@ -111,17 +106,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md b/exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md new file mode 100644 index 0000000000..a111c53994 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md @@ -0,0 +1,90 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-OutboundConnectorReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-OutboundConnectorReport cmdlet to view the Outbound connectors that are used to deliver mail to specific domains. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-OutboundConnectorReport [-Domain ] + [-ProbeTag ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-OutboundConnectorReport -Domain contoso.com +``` + +This example shows the Outbound connector that's used to deliver mail to the contoso.com domain. + +## PARAMETERS + +### -Domain +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/client-access-servers/Get-OutlookAnywhere.md b/exchange/exchange-ps/exchange/Get-OutlookAnywhere.md similarity index 84% rename from exchange/exchange-ps/exchange/client-access-servers/Get-OutlookAnywhere.md rename to exchange/exchange-ps/exchange/Get-OutlookAnywhere.md index 7a917bbf8d..e2189d867d 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-OutlookAnywhere.md +++ b/exchange/exchange-ps/exchange/Get-OutlookAnywhere.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-outlookanywhere +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-OutlookAnywhere @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-OutlookAnywhere cmdlet to view Outlook Anywhere virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-OutlookAnywhere -Server [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ### Identity @@ -34,11 +34,12 @@ Get-OutlookAnywhere -Server Get-OutlookAnywhere [[-Identity] ] [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,13 +62,11 @@ This example returns information about the Outlook Anywhere virtual directory na ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -88,11 +87,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -111,7 +107,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -167,12 +165,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md similarity index 85% rename from exchange/exchange-ps/exchange/policy-and-compliance/Get-OutlookProtectionRule.md rename to exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md index 659b1d5598..ed2ad0aa94 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-OutlookProtectionRule.md +++ b/exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md @@ -1,34 +1,37 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-outlookprotectionrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-OutlookProtectionRule ## SYNOPSIS +**Note**: This cmdlet is no longer supported in the cloud-based service. + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Get-OutlookProtectionRule cmdlet to retrieve Microsoft Outlook protection rules configured in an organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-OutlookProtectionRule [[-Identity] ] [-DomainController ] [] +Get-OutlookProtectionRule [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -Outlook protection rules are used to automatically Information Rights Management (IRM)-protect email messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To IRM-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://docs.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). +Outlook protection rules are used to automatically Information Rights Management (IRM)-protect email messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To IRM-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,37 +53,37 @@ The Identity parameter is positional. When used after the cmdlet name, the param ## PARAMETERS -### -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. +### -Identity +The Identity parameter identifies an Outlook protection rule. ```yaml -Type: Fqdn +Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter identifies an Outlook protection rule. +### -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. ```yaml -Type: RuleIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -89,12 +92,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Get-OutlookProvider.md b/exchange/exchange-ps/exchange/Get-OutlookProvider.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access/Get-OutlookProvider.md rename to exchange/exchange-ps/exchange/Get-OutlookProvider.md index 548b5ca458..72b2e977b7 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-OutlookProvider.md +++ b/exchange/exchange-ps/exchange/Get-OutlookProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-outlookprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-OutlookProvider @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-OutlookProvider cmdlet to obtain the global settings from the AutoDiscoverConfig object under the Global Settings object in Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-OutlookProvider [[-Identity] ] [-DomainController ] [] +Get-OutlookProvider [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION The Get-OutlookProvider cmdlet gets the global settings from the AutoDiscoverConfig object in Active Directory and returns an OutlookProvider object to be managed in the Exchange admin center. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,41 +49,39 @@ This example returns detailed information for the Outlook provider named WEB. ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the ADIDParameter value of the MAPI protocol that you want to view. Typical values are: + +- EXCH +- EXPR +- WEB ```yaml -Type: Fqdn +Type: OutlookProviderIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the ADIDParameter value of the MAPI protocol that you want to view. Typical values are: - -- EXCH - -- EXPR - -- WEB +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: OutlookProviderIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -91,12 +90,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Get-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access/Get-OwaMailboxPolicy.md rename to exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md index cdb02ec5c8..d3d81a63ed 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-owamailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-OwaMailboxPolicy @@ -17,16 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-OwaMailboxPolicy cmdlet to view Outlook on the web mailbox policies in the organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-OwaMailboxPolicy [[-Identity] ] [-DomainController ] [] +Get-OwaMailboxPolicy [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,43 +54,41 @@ This example retrieves the information for the mailbox policy named Corporate fo ## PARAMETERS -### -DomainController -This parameter is available only in on-premises Exchange. +### -Identity +The Identity parameter specifies the mailbox policy that you want to view. You can use any value that uniquely identifies the policy. For example: -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +- Name +- Distinguished name (DN) +- GUID ```yaml -Type: Fqdn +Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) +### -DomainController +This parameter is available only in on-premises Exchange. -- GUID +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: MailboxPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -98,12 +97,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-OwaVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Get-OwaVirtualDirectory.md rename to exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md index 753107395c..6087a13fe7 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-owavirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-OwaVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-OwaVirtualDirectory cmdlet to view Outlook on the web virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-OwaVirtualDirectory -Server [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ### Identity @@ -34,7 +34,8 @@ Get-OwaVirtualDirectory -Server Get-OwaVirtualDirectory [[-Identity] ] [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ## DESCRIPTION @@ -42,7 +43,7 @@ The Get-OwaVirtualDirectory cmdlet can be run on a local server or run remotely The Get-OwaVirtualDirectory cmdlet can be run on any server that has the Exchange Server administration tools installed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,13 +73,11 @@ This example returns a summary list of all Outlook on the web virtual directorie ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -99,11 +98,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -122,7 +118,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -178,12 +176,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-PartnerApplication.md b/exchange/exchange-ps/exchange/Get-PartnerApplication.md similarity index 87% rename from exchange/exchange-ps/exchange/organization/Get-PartnerApplication.md rename to exchange/exchange-ps/exchange/Get-PartnerApplication.md index 50ef605fca..1e1e76f5db 100644 --- a/exchange/exchange-ps/exchange/organization/Get-PartnerApplication.md +++ b/exchange/exchange-ps/exchange/Get-PartnerApplication.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-partnerapplication +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PartnerApplication @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PartnerApplication cmdlet to retrieve settings for a partner application. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,9 +28,9 @@ Get-PartnerApplication [[-Identity] ] ``` ## DESCRIPTION -You can configure partner applications such as Microsoft SharePoint to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://docs.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). +You can configure partner applications such as Microsoft SharePoint to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -101,12 +100,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md b/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md new file mode 100644 index 0000000000..ca13e8b6fa --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md @@ -0,0 +1,134 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-PendingDelicenseUser + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-PendingDelicenseUser cmdlet to view information about mailboxes that have delayed mailbox license removal requests. You configure delayed mailbox license removal using the DelayedDelicensingEnabled parameter on the Set-OrganizationConfig cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Get-PendingDelicenseUser [[-Identity] ] + [] +``` + +### TenantLevelParameterSet +``` +Get-PendingDelicenseUser [-ResultSize ] [-ShowDueObjectsOnly] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-PendingDelicenseUser | Format-Table DisplayName,UserPrincipalName,WhenDueForDelicensingUTC +``` + +This example returns a summary list of all mailboxes that have pending mailbox license removal requests. + +### Example 2 +```powershell +Get-PendingDelicenseUser -Identity yajvendra@contoso.onmicrosoft.com +``` + +This example returns detailed information about the pending mailbox license removal request for the specified mailbox. + +### Example 3 +```powershell +Get-PendingDelicenseUser -ShowDueObjectsOnly | Format-Table DisplayName,UserPrincipalName,WhenDueForDelicensingUTC +``` + +This example returns a summary list of all mailboxes where the 30 day delay for mailbox license removal requests has ended, so the licenses can be removed from the mailboxes at any time. + +## PARAMETERS + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Email address +- GUID +- LegacyExchangeDN +- User ID or user principal name (UPN) + +You can't use this parameter with the ShowDueObjectsOnly switch. + +```yaml +Type: RecipientIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: TenantLevelParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowDueObjectsOnly +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. + +```yaml +Type: SwitchParameter +Parameter Sets: TenantLevelParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-PendingFederatedDomain.md b/exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md similarity index 83% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-PendingFederatedDomain.md rename to exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md index 6a78929f33..e646d32251 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-PendingFederatedDomain.md +++ b/exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-pendingfederateddomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-PendingFederatedDomain @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. The Get-PendingFederatedDomain cmdlet is used by the Exchange admin center to display a list of pending federated domains for the federation trust for your Exchange organization. You shouldn't use this cmdlet to attempt to manually configure a federation trust. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,7 @@ Get-PendingFederatedDomain [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,12 +43,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Get-PerimeterConfig.md b/exchange/exchange-ps/exchange/Get-PerimeterConfig.md similarity index 76% rename from exchange/exchange-ps/exchange/organization/Get-PerimeterConfig.md rename to exchange/exchange-ps/exchange/Get-PerimeterConfig.md index 3224b96cc1..0559a00b0d 100644 --- a/exchange/exchange-ps/exchange/organization/Get-PerimeterConfig.md +++ b/exchange/exchange-ps/exchange/Get-PerimeterConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-perimeterconfig +online version: https://learn.microsoft.com/powershell/module/exchange/get-perimeterconfig applicable: Exchange Online title: Get-PerimeterConfig schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-PerimeterConfig @@ -17,15 +16,13 @@ This cmdlet is available only in the cloud-based service. Use the Get-PerimeterConfig cmdlet to view the list of gateway server and internal mail server IP addresses that have been added to the cloud-based safelists. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-PerimeterConfig [[-Identity] ] [] +Get-PerimeterConfig [[-Identity] ] + [] ``` ## DESCRIPTION @@ -63,12 +60,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md b/exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md new file mode 100644 index 0000000000..7cb3d2c953 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md @@ -0,0 +1,87 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-PhishSimOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-PhishSimOverridePolicy cmdlet to view third-party phishing simulation override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-PhishSimOverridePolicy [[-Identity] ] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-PhishSimOverridePolicy +``` + +This example returns detailed information about the one and only phishing simulation override policy. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-Place.md b/exchange/exchange-ps/exchange/Get-Place.md new file mode 100644 index 0000000000..c13137555b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-Place.md @@ -0,0 +1,173 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-Place + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-Place cmdlet to view the additional metadata that was configured on room mailboxes by using the Set-Place cmdlet. The additional metadata provides a better search and room suggestion experience. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Get-Place [[-Identity] ] + [-Confirm] + [-ResultSize ] + [-WhatIf] + [] +``` + +### AllPlaces +``` +Get-Place [-Type ] + [-Confirm] + [-ResultSize ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-Place -Identity "Conference Room 01" +``` + +This example returns summary metadata for the room mailbox named Conference Room 1. + +### Example 2 +```powershell +Get-Place -Identity "Conference Room 01" | Format-List +``` + +This example returns detailed metadata for Conference Room 1. + +### Example 3 +```powershell +Get-Place -Type Room +``` + +This example returns all room mailboxes. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can't use this parameter with the Type parameter. + +```yaml +Type: RecipientIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Type +The Type parameter filters the results by the type of room mailbox. Valid values are: + +- Room +- RoomList +- Space + +You can't use this parameter with the Identity parameter. + +```yaml +Type: GetPlaceType +Parameter Sets: AllPlaces +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-PolicyConfig.md b/exchange/exchange-ps/exchange/Get-PolicyConfig.md new file mode 100644 index 0000000000..7b985e28c4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-PolicyConfig.md @@ -0,0 +1,66 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-PolicyConfig + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-PolicyConfig cmdlet to view the endpoint restrictions that are configured in the organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-PolicyConfig [[-Identity] ] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-PolicyConfig +``` + +This example returns the endpoint restrictions that are available in the organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-PolicyTipConfig.md b/exchange/exchange-ps/exchange/Get-PolicyTipConfig.md similarity index 80% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-PolicyTipConfig.md rename to exchange/exchange-ps/exchange/Get-PolicyTipConfig.md index cc7ff87a57..0704474cc3 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-PolicyTipConfig.md +++ b/exchange/exchange-ps/exchange/Get-PolicyTipConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-policytipconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PolicyTipConfig @@ -17,24 +16,28 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PolicyTipConfig cmdlet to view the data loss prevention (DLP) Policy Tips in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Parameters ``` -Get-PolicyTipConfig [-Action ] [-Locale ] [-Original] - [-DomainController ] [] +Get-PolicyTipConfig [-Action ] + [-Locale ] + [-Original] + [-DomainController ] + [] ``` ### Identity ``` Get-PolicyTipConfig [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,13 +64,34 @@ This example returns details about the custom English Policy Tip for the action ## PARAMETERS +### -Identity +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. +- The value Url +- GUID +- Distinguished name (DN) + +You can't use the Identity parameter with the Action, Locale or Original parameters. + +```yaml +Type: PolicyTipConfigIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Action The Action parameter filters the Policy Tips by action. Valid values for this parameter are: - NotifyOnly - - RejectOverride - - Reject You can't use the value Url with the Action parameter. Instead, use command: Get-PolicyTipConfig Url. @@ -105,36 +129,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 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://docs.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. - -- The value Url - -- GUID - -- Distinguished name (DN) - -You can't use the Identity parameter with the Action, Locale or Original parameters. - -```yaml -Type: PolicyTipConfigIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Locale 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://docs.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs). +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). You can't use the Locale parameter with the Identity parameter. @@ -152,7 +150,9 @@ Accept wildcard characters: False ``` ### -Original -The Original switch includes built-in Policy Tips in the results. You don't specify a value with the Original switch. You can't use the Original switch with the Identity parameter. +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. ```yaml Type: SwitchParameter @@ -172,12 +172,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Get-PopSettings.md b/exchange/exchange-ps/exchange/Get-PopSettings.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access/Get-PopSettings.md rename to exchange/exchange-ps/exchange/Get-PopSettings.md index 3799400ce2..4223b39960 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-PopSettings.md +++ b/exchange/exchange-ps/exchange/Get-PopSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-popsettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-PopSettings @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-POPSettings cmdlet to view the configuration of the Microsoft Exchange POP3 service. This service exists on Exchange servers that have the Client Access server role installed and is used by POP3 clients to connect to Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-PopSettings [-DomainController ] [-Server ] [] +Get-PopSettings [-DomainController ] + [-Server ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -66,11 +67,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -93,12 +91,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-PowerShellVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Get-PowerShellVirtualDirectory.md rename to exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md index 67237cbf47..b46a6dbd1e 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-powershellvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-PowerShellVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-PowerShellVirtualDirectory cmdlet to view Windows PowerShell virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-PowerShellVirtualDirectory -Server [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ### Identity @@ -34,11 +34,12 @@ Get-PowerShellVirtualDirectory -Server Get-PowerShellVirtualDirectory [[-Identity] ] [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,13 +69,11 @@ This example returns a summary list of all PowerShell virtual directories in the ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -95,11 +94,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -118,7 +114,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -174,12 +172,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ProtectionAlert.md b/exchange/exchange-ps/exchange/Get-ProtectionAlert.md new file mode 100644 index 0000000000..2e99bc420c --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ProtectionAlert.md @@ -0,0 +1,95 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ProtectionAlert + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-ProtectionAlert cmdlet to view alert policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ProtectionAlert [[-Identity] ] + [-IncludeRuleXml] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ProtectionAlert | Format-List Name,Category,Comment,NotifyUser +``` + +This example returns a summary list of all alert policies. + +### Example 2 +```powershell +Get-ProtectionAlert -Identity "Malware campaign detected after delivery" +``` + +This example returns detailed information about the specified alert policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -IncludeRuleXml +{{ Fill IncludeRuleXml Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolder.md b/exchange/exchange-ps/exchange/Get-PublicFolder.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolder.md rename to exchange/exchange-ps/exchange/Get-PublicFolder.md index b981041df1..6236c3d432 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolder.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-publicfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PublicFolder @@ -17,30 +16,34 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PublicFolder cmdlet to retrieve the attributes of a public folder or a set of public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### GetChildren ``` -Get-PublicFolder [[-Identity] ] [-GetChildren] +Get-PublicFolder [[-Identity] ] + [-GetChildren] [-DomainController ] [-Mailbox ] [-Organization ] [-ResidentFolders] [-ResultSize ] - [-Server ] [] + [-Server ] + [] ``` ### Recurse ``` -Get-PublicFolder [[-Identity] ] [-Recurse] +Get-PublicFolder [[-Identity] ] + [-Recurse] [-DomainController ] [-Mailbox ] [-Organization ] [-ResidentFolders] [-ResultSize ] - [-Server ] [] + [-Server ] + [] ``` ### LostAndFound @@ -50,7 +53,8 @@ Get-PublicFolder [-LostAndFound] [-Mailbox ] [-Organization ] [-ResidentFolders] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ### Identity @@ -60,11 +64,12 @@ Get-PublicFolder [[-Identity] ] [-Mailbox ] [-Organization ] [-ResidentFolders] - [-Server ] [] + [-Server ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -112,6 +117,22 @@ This example returns the public folders that reside in the public folder content ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -GetChildren 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. @@ -166,22 +187,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name and path of the public folder you want to view. A valid value uses the syntax: \\\\\\\\...\\\\\\. 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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -LostAndFound 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. @@ -206,23 +211,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -257,7 +253,9 @@ Accept wildcard characters: False ``` ### -ResidentFolders -The ResidentFolders specifies whether to return public folders that reside in a specific content public folder mailbox. If this parameter isn't specified, the command will only return public folders whose contents reside in the primary hierarchy public folder mailbox. +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. ```yaml Type: SwitchParameter @@ -289,16 +287,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -319,12 +314,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md similarity index 81% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderAdministrativePermission.md rename to exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md index 45546a8586..8827234280 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-publicfolderadministrativepermission +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderadministrativepermission applicable: Exchange Server 2010 title: Get-PublicFolderAdministrativePermission schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Get-PublicFolderAdministrativePermission @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Get-PublicFolderAdministrativePermission cmdlet to get the administrative permissions for a public folder or a public folder hierarchy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,18 +24,20 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-PublicFolderAdministrativePermission [-Identity] [-User ] [-DomainController ] - [-Server ] [] + [-Server ] + [] ``` ### Owner ``` Get-PublicFolderAdministrativePermission [-Identity] [-Owner] [-DomainController ] - [-Server ] [] + [-Server ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -98,7 +99,9 @@ Accept wildcard characters: False ``` ### -Owner -The Owner parameter specifies that the command should return only the owner of the public folder. +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. ```yaml Type: SwitchParameter @@ -117,11 +120,8 @@ Accept wildcard characters: False The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -138,7 +138,26 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the user principal name (UPN), domain\\user, or alias of the user for whom administrative permissions are sought. +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 +- Mail users +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the Owner switch. ```yaml Type: SecurityPrincipalIdParameter @@ -158,12 +177,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderClientPermission.md b/exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md similarity index 82% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderClientPermission.md rename to exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md index 9e43ca40dc..cbf1b56f79 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-publicfolderclientpermission +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PublicFolderClientPermission @@ -17,13 +16,14 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PublicFolderClientPermission cmdlet to retrieve the user permissions for a public folder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-PublicFolderClientPermission [-Identity] [-DomainController ] + [-ResultSize ] [-Server ] [-User ] [-Mailbox ] @@ -31,9 +31,9 @@ Get-PublicFolderClientPermission [-Identity] ``` ## DESCRIPTION -To view the permissions that are available on public folders, see [Public folder permissions for Exchange Server](https://support.microsoft.com/help/2573274/public-folder-permissions-for-exchange-server). +To view the permissions that are available on public folders, see [Public folder permissions for Exchange Server](https://support.microsoft.com/help/2573274). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -89,17 +89,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ResultSize +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. + +```yaml +Type: Unlimited +Parameter Sets: (All)) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -116,7 +131,12 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the user principal name (UPN), domain\\user, or alias of a specific user for whom you want to view the permissions on the public folder. +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: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. ```yaml Type: PublicFolderUserIdParameter @@ -135,23 +155,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) By default, the permissions are returned from the primary public folder mailbox. Using this parameter allows you to specify a different public folder mailbox. @@ -174,12 +185,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderDatabase.md b/exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md similarity index 86% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderDatabase.md rename to exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md index 51c5ba312b..163d873ee4 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderDatabase.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-publicfolderdatabase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-PublicFolderDatabase @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-PublicFolderDatabase cmdlet to view public folder database settings for Microsoft Exchange Server 2010 or earlier public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Get-PublicFolderDatabase -Server [-DomainController ] [-IncludePreExchange2010] [-Status] - [-IncludeCorrupted] [] + [-IncludeCorrupted] + [] ``` ### Identity @@ -36,7 +36,8 @@ Get-PublicFolderDatabase [[-Identity] ] [-DomainController ] [-IncludePreExchange2010] [-Status] - [-IncludeCorrupted] [] + [-IncludeCorrupted] + [] ``` ## DESCRIPTION @@ -44,7 +45,7 @@ You can specify either the Server or Identity parameter, but not both. Only the When you run the Get-PublicFolderDatabase cmdlet with no parameters, it returns attributes of all of the public folder databases in the Exchange organization. To return specific database properties (including backup and mount status information) where the Get-PublicFolderDatabase cmdlet has to contact servers directly or perform a complex or slow calculation, make sure you use the Status parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -75,9 +76,7 @@ This example returns information about all public folders on Server01. 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 - - Distinguished name (DN) - - GUID You can't the Identity and Server parameters in the same command. @@ -101,11 +100,8 @@ Accept wildcard characters: False The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use the Server and Identity parameters in the same command. @@ -139,14 +135,12 @@ Accept pipeline input: False Accept wildcard characters: False ``` - - ### -IncludePreExchange2010 -This parameter is available or functional only in 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. -This parameter isn't useful in commands where you use the Server parameter or Identity parameter. +This switch isn't useful in commands where you use the Server or Identity parameters. ```yaml Type: SwitchParameter @@ -162,7 +156,7 @@ Accept wildcard characters: False ``` ### -Status -The Status parameter specifies whether additional backup and mount status information is included for servers running Exchange 2010. If the Status parameter is included, additional backup and mount status information is included for Exchange 2010 servers. +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 @@ -198,12 +192,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderItemStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md similarity index 86% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderItemStatistics.md rename to exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md index 62b351c465..7e8d13e1d4 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderItemStatistics.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-publicfolderitemstatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PublicFolderItemStatistics @@ -17,20 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PublicFolderItemStatistics cmdlet to view information about items within a specified public folder. Information returned includes subject, last modification time, creation time, attachments, message size, and the type of item. You can use this raw information to better understand the distribution of items and item characteristics across public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Get-PublicFolderItemStatistics [-Identity] [-DomainController ] + [-ResultSize ] [-Server ] [-Mailbox ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,13 +56,9 @@ Get-PublicFolderItemStatistics -Identity "\Marketing\Reports" | Select Subject,L This example exports the output of the Get-PublicFolderItemStatistics command to the PFItemStats.csv file that includes the following information for all items within the public folder \\Marketing\\Reports: - Subject of the message (Subject) - - Date and time when the item was last modified (LastModificationTime) - - If the item has attachments (HasAttachments) - - Type of item (ItemType) - - Size of the item (MessageSize) ## PARAMETERS @@ -105,23 +101,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -137,17 +124,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ResultSize +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. + +```yaml +Type: Unlimited +Parameter Sets: (All)) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -168,12 +170,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderMailboxDiagnostics.md b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderMailboxDiagnostics.md rename to exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md index b81f97a38b..d7b0c82238 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderMailboxDiagnostics.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-publicfoldermailboxdiagnostics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PublicFolderMailboxDiagnostics @@ -17,17 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PublicFolderMailboxDiagnostics cmdlet to view event-level information about a public folder mailbox. This information can be used to troubleshoot public folder issues. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-PublicFolderMailboxDiagnostics [-Identity] [-Confirm] [-DomainController ] - [-IncludeDumpsterInfo] [-IncludeHierarchyInfo] [-WhatIf] [] +Get-PublicFolderMailboxDiagnostics [-Identity] + [-Confirm] + [-DomainController ] + [-IncludeDumpsterInfo] + [-IncludeHierarchyInfo] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,23 +57,14 @@ The Identity parameter specifies the identity of the public folder mailbox. The You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -88,8 +83,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,7 +118,7 @@ Accept wildcard characters: False ``` ### -IncludeDumpsterInfo -The IncludeDumpsterInfo parameter specifies that diagnostic information for the \\NON\_IPM\_TREE\\DUMPSTER\_ROOT folder, which serves as the dumpster for public folder mailboxes, is included in the returned information. +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 @@ -140,26 +134,19 @@ Accept wildcard characters: False ``` ### -IncludeHierarchyInfo -The IncludeHierarchyInfo switch specifies whether to include folder hierarchy information in the results. This includes the following information: +The IncludeHierarchyInfo switch specifies whether to include folder hierarchy information in the results. You don't need to specify a value with this switch. -- TotalFolderCount: The total number of public folders in the specified public folder mailbox. +Using this switch returns the following information: +- TotalFolderCount: The total number of public folders in the specified public folder mailbox. - MaxFolderChildCount: The largest number of child folders in the public folder hierarchy. - - HierarchyDepth: The depth of the public folder hierarchy. The root folder is 0. - - CalendarFolderCount: The number of calendar public folders. - - ContactFolderCount: The number of calendar public folders. - - MailPublicFolderCount: The number of mail-enabled public folders. - - NoteFolderCount: The number of note public folders. - - StickyNoteFolderCount: The number of sticky note public folders. - - TaskFolderCount: The number of task public folders. - - OtherFolderCount: The number of public folders that don't match any of the previously defined public folder types. ```yaml @@ -196,12 +183,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequest.md rename to exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md index ff4fb9e871..4fe2797ff4 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-publicfoldermailboxmigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PublicFolderMailboxMigrationRequest @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PublicFolderMailboxMigrationRequest cmdlet to view the status of individual jobs in public folder migration batches that were created by using the New-MigrationBatch cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -46,12 +45,10 @@ Get-PublicFolderMailboxMigrationRequest [[-Identity] ` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`). + +You can't use this parameter with the following parameters: + +- BatchName +- HighPriority +- Name +- RequestQueue +- Suspend +- Status + +```yaml +Type: PublicFolderMailboxMigrationRequestIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -BatchName -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:\. +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. @@ -127,7 +149,6 @@ 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: - $true Returns requests that were created with the Priority value High, Higher, Highest or Emergency. - - $false Returns requests that were created with the Priority value Normal, Low, Lower or Lowest. You can't use this parameter with the Identity parameter. @@ -145,38 +166,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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: - -- BatchName - -- HighPriority - -- Name - -- RequestQueue - -- Suspend - -- Status - -```yaml -Type: PublicFolderMailboxMigrationRequestIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Name -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). +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. @@ -199,9 +190,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -239,23 +228,14 @@ Accept wildcard characters: False The Status parameter filters the results based on status. You can use the following values: - AutoSuspended - - Completed - - CompletedWithWarning - - CompletionInProgress - - Failed - - InProgress - - Queued - - Retrying - - Suspended - - Synced You can't use this parameter with the Identity parameter. @@ -296,12 +276,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequestStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md similarity index 86% rename from exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequestStatistics.md rename to exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md index 41b066a032..cb164285ad 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequestStatistics.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-publicfoldermailboxmigrationrequeststatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PublicFolderMailboxMigrationRequestStatistics @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PublicFolderMailboxMigrationRequestStatistics cmdlet to view the detailed status of individual jobs in a public folder migration batch created using New-MigrationBatch cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -37,6 +36,7 @@ Get-MailboxRestoreRequestStatistics [-Identity] [-DiagnosticInfo ] [-IncludeReport] + [-IncludeSkippedItems] [-ReportOnly] [] ``` @@ -57,14 +57,11 @@ Get-MailboxRestoreRequestStatistics -RequestQueue The Get-PublicFolderMailboxMigrationRequestStatistics cmdlet displays the following properties by default. - Name: The name assigned by the system to a specific mailbox migration job. - - StatusDetail: The current status of the job. - - TargetMailbox: The mailbox being migrated. - - PercentComplete: The percentage of job completion. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -78,7 +75,7 @@ This example uses the Identity parameter to return information about the specifi ## PARAMETERS ### -Identity -The Identity parameter specifies the public folder mailbox migration request. The default identity value is \\PublicFolderMailboxMigration\ (for example, \\PublicFolderMailboxMigration\ac6d9eb4-ee49-405f-b90d-04e9a258bd7e). +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. @@ -103,9 +100,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -126,7 +121,9 @@ Accept wildcard characters: False ### -Diagnostic This parameter is available only in on-premises Exchange. -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -196,7 +193,7 @@ Accept wildcard characters: False ``` ### -IncludeReport -The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. +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 @@ -211,6 +208,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IncludeSkippedItems +This parameter is available only in the cloud-based service. + +{{ Fill IncludeSkippedItems Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: IdentityCloud +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ReportOnly 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. @@ -252,12 +267,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md similarity index 93% rename from exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md index 3ba091a8e5..c001744a6d 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-publicfoldermigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-PublicFolderMigrationRequest @@ -19,7 +18,7 @@ Use the Get-PublicFolderMigrationRequest cmdlet to view information about serial **Note**: Support for serial migration of public folders ended in Exchange 2013 Cumulative Update 8 (CU8), and the cmdlets are no longer available in Exchange Online. Instead, use the corresponding **\*-MigrationBatch** and **\*-PublicFolderMailboxMigration\*** cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -46,7 +45,7 @@ Get-PublicFolderMigrationRequest [[-Identity] [-Diagnostic] + [-Diagnostic ] [-DiagnosticArgument ] - [-DiagnosticInfo ] [-DomainController ] [-IncludeReport] [-ReportOnly] @@ -37,7 +36,8 @@ Get-PublicFolderMigrationRequestStatistics [-Identity] [-RequestGuid ] +Get-PublicFolderMigrationRequestStatistics -RequestQueue + [-RequestGuid ] [-Diagnostic] [-DiagnosticArgument ] [-DomainController ] @@ -47,7 +47,7 @@ Get-PublicFolderMigrationRequestStatistics -RequestQueue [ ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -71,7 +71,6 @@ This example returns additional information about the migration request and expo The Identity parameter specifies the migration request that you want to view. You can use the following values: - Name - - RequestGUID You can't use this parameter with the RequestQueue or RequestGuid parameter. @@ -95,9 +94,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -116,7 +113,9 @@ Accept wildcard characters: False ``` ### -Diagnostic -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -164,7 +163,7 @@ Accept wildcard characters: False ``` ### -IncludeReport -The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. +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 @@ -218,12 +217,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md similarity index 80% rename from exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMoveRequest.md rename to exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md index 3589f5eba7..5d234a047b 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md @@ -1,43 +1,41 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-publicfoldermoverequest -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-PublicFolderMoveRequest ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Get-PublicFolderMoveRequest cmdlet to view the detailed status of an ongoing public folder move that was initiated using the New-PublicFolderMoveRequest cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX -### Filtering +### Identity ``` -Get-PublicFolderMoveRequest [-BatchName ] +Get-PublicFolderMoveRequest [[-Identity] ] + [-AccountPartition ] [-DomainController ] - [-HighPriority ] - [-Name ] - [-RequestQueue ] + [-Organization ] [-ResultSize ] - [-Status ] - [-Suspend ] [] ``` -### Identity +### Filtering ``` -Get-PublicFolderMoveRequest [[-Identity] ] +Get-PublicFolderMoveRequest [-BatchName ] [-HighPriority ] [-Name ] [-RequestQueue ] [-Status ] [-Suspend ] + [-AccountPartition ] [-DomainController ] + [-Organization ] [-ResultSize ] [] ``` @@ -45,7 +43,7 @@ Get-PublicFolderMoveRequest [[-Identity] ] ## DESCRIPTION Public folder move requests are used to move public folders between public folder mailboxes. After the move request is complete, you need to update the hierarchy using the Update-PublicFolderMailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,6 +63,49 @@ This example returns the status of in-progress and queued requests that are on t ## PARAMETERS +### -Identity +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: + +- BatchName +- HighPriority +- Name +- RequestQueue +- Suspend +- Status + +```yaml +Type: PublicFolderMoveRequestIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccountPartition +This parameter is available only in the cloud-based service. + +{{ Fill AccountPartition Description }} + +```yaml +Type: AccountPartitionIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -BatchName The BatchName parameter specifies the name that was given to a batch public folder move request. @@ -74,7 +115,7 @@ You can't use this parameter with the Identity parameter. Type: String Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -84,13 +125,15 @@ Accept wildcard characters: False ``` ### -DomainController +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. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -103,7 +146,6 @@ Accept wildcard characters: False 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. - - $false Returns requests that were created with the Priority value Normal, Low, Lower or Lowest. You can't use this parameter with the Identity parameter. @@ -112,7 +154,7 @@ You can't use this parameter with the Identity parameter. Type: Boolean Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -121,46 +163,34 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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: - -- BatchName - -- HighPriority - -- Name - -- RequestQueue - -- Suspend +### -Name +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. -- Status +You can't use this parameter with the Identity parameter. ```yaml -Type: PublicFolderMoveRequestIdParameter -Parameter Sets: Identity +Type: String +Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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. +### -Organization +This parameter is available only in the cloud-based service. -You can't use this parameter with the Identity parameter. +{{ Fill Organization Description }} ```yaml -Type: String -Parameter Sets: Filtering +Type: OrganizationIdParameter +Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online Required: False Position: Named @@ -173,9 +203,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -184,7 +212,7 @@ You can't use this parameter with the Identity parameter. Type: DatabaseIdParameter Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -200,7 +228,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -213,23 +241,14 @@ Accept wildcard characters: False The Status parameter filters the results based on status. You can use the following values: - AutoSuspended - - Completed - - CompletedWithWarning - - CompletionInProgress - - Failed - - InProgress - - Queued - - Retrying - - Suspended - - Synced You can't use this parameter with the Identity parameter. @@ -238,7 +257,7 @@ You can't use this parameter with the Identity parameter. Type: RequestStatus Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -256,7 +275,7 @@ You can't use this parameter with the Identity parameter. Type: Boolean Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -270,12 +289,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMoveRequestStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md similarity index 76% rename from exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMoveRequestStatistics.md rename to exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md index 6b5c40c611..475fc29578 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-PublicFolderMoveRequestStatistics.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-publicfoldermoverequeststatistics -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-PublicFolderMoveRequestStatistics ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Get-PublicFolderMoveRequestStatistics cmdlet to view detailed information about public folder move requests. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,9 +25,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-PublicFolderMoveRequestStatistics [-Identity] [-Diagnostic] [-DiagnosticArgument ] + [-DiagnosticInfo ] [-DomainController ] [-IncludeReport] - [-ReportOnly] [] + [-IncludeSkippedItems] + [-ReportOnly] + [] ``` ### MigrationRequestQueue @@ -36,13 +38,16 @@ Get-PublicFolderMoveRequestStatistics [-Identity] [-RequestGuid ] [-Diagnostic] [-DiagnosticArgument ] + [-DiagnosticInfo ] [-DomainController ] [-IncludeReport] - [-ReportOnly] [] + [-IncludeSkippedItems] + [-ReportOnly] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -71,7 +76,7 @@ This parameter can't be used with the RequestQueue parameter. Type: PublicFolderMoveRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -86,9 +91,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -97,7 +100,7 @@ You can't use this parameter with the Identity parameter. Type: DatabaseIdParameter Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -107,7 +110,9 @@ Accept wildcard characters: False ``` ### -Diagnostic -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. +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. ```yaml Type: SwitchParameter @@ -138,14 +143,34 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DiagnosticInfo +This parameter is available only in the cloud-based service. + +{{ Fill DiagnosticInfo Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DomainController +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. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -155,13 +180,13 @@ Accept wildcard characters: False ``` ### -IncludeReport -The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. +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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -170,20 +195,20 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RequestGuid -The RequestGuid parameter specifies the GUID of the public folder move request for which you want to view the request statistics. +### -IncludeSkippedItems +This parameter is available only in the cloud-based service. -This parameter can't be used with the Identity parameter. +{{ Fill IncludeSkippedItems Description }} ```yaml -Type: Guid -Parameter Sets: MigrationRequestQueue +Type: SwitchParameter +Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online Required: False Position: Named -Default value: None +Default value: False Accept pipeline input: False Accept wildcard characters: False ``` @@ -195,7 +220,25 @@ The ReportOnly switch returns the results as an array of report entries (encoded Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequestGuid +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. + +```yaml +Type: Guid +Parameter Sets: MigrationRequestQueue +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -209,12 +252,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md similarity index 90% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderStatistics.md rename to exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md index 7041883d92..023a6d31c0 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderStatistics.md +++ b/exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-publicfolderstatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-PublicFolderStatistics @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-PublicFolderStatistics cmdlet to retrieve statistical information about public folders, such as folder size and last logon time. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,7 +30,7 @@ Get-PublicFolderStatistics [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,39 +43,39 @@ This example retrieves statistics about the public folder Marketing\\2013\\Pamph ## PARAMETERS -### -DomainController -This parameter is available only in on-premises Exchange. +### -Identity +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. -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +You can omit the parameter label so that only the public folder name or GUID is supplied. ```yaml -Type: Fqdn +Type: PublicFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -DomainController +This parameter is available only in on-premises Exchange. -You can omit the parameter label so that only the public folder name or GUID is supplied. +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: PublicFolderIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -84,23 +83,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -135,16 +125,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -165,12 +152,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-QuarantineMessage.md b/exchange/exchange-ps/exchange/Get-QuarantineMessage.md new file mode 100644 index 0000000000..7e98a8ee18 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-QuarantineMessage.md @@ -0,0 +1,595 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-QuarantineMessage + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-QuarantineMessage cmdlet to view quarantined messages and files in your cloud-based organization. Files are quarantined by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Details +``` +Get-QuarantineMessage -Identity + [-EntityType ] + [-RecipientAddress ] + [-SenderAddress ] + [-TeamsConversationTypes ] + [] +``` + +### Summary +``` +Get-QuarantineMessage + [-Direction ] + [-Domain ] + [-EndExpiresDate ] + [-EndReceivedDate ] + [-EntityType ] + [-IncludeMessagesFromBlockedSenderAddress] + [-MessageId ] + [-MyItems] + [-Page ] + [-PageSize ] + [-PolicyName ] + [-PolicyTypes ] + [-QuarantineTypes ] + [-RecipientAddress ] + [-RecipientTag ] + [-ReleaseStatus ] + [-Reported ] + [-SenderAddress ] + [-StartExpiresDate ] + [-StartReceivedDate ] + [-Subject ] + [-TeamsConversationTypes ] + [-Type ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-QuarantineMessage -StartReceivedDate 06/13/2017 -EndReceivedDate 06/15/2017 +``` + +This example returns a summary list of messages quarantined between June 13, 2017 and June 15, 2017. + +### Example 2 +```powershell +Get-QuarantineMessage -PageSize 50 -Page 3 +``` + +This example presents 50 quarantined messages per page, and returns the third page of results. + +### Example 3 +```powershell +Get-QuarantineMessage -MessageID "<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>" +``` + +This example returns the quarantined message with the Message-ID value `<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>`. + +### Example 4 +```powershell +Get-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 | Format-List +``` + +This example returns detailed information for the quarantined message with the specified Identity value. + +### Example 5 +```powershell +Get-QuarantineMessage -QuarantineTypes SPOMalware | Format-List +``` + +This example returns detailed information for the files protected by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. + +## PARAMETERS + +### -Identity +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`. + +```yaml +Type: QuarantineMessageIdentity +Parameter Sets: Details +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Direction +The Direction parameter filters the results by incoming or outgoing messages. Valid values are: + +- Inbound +- Outbound + +You can specify multiple values separated by commas. + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.QuarantineMessageDirectionEnum +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndExpiresDate +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". + +For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days. + +```yaml +Type: System.DateTime +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndReceivedDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntityType +The EntityType parameter filters the results by EntityType. Valid values are: + +- Email +- SharePointOnline +- Teams (currently in Preview) +- DataLossPrevention + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeMessagesFromBlockedSenderAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MyItems +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The PolicyName parameter filters the results by the protection policy that quarantined the message (for example, the anti-malware policy). You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: String +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTypes +The PolicyTypes parameter filters the results by the type of protection policy that quarantined the message. Valid values are: + +- AntiMalwarePolicy +- AntiPhishPolicy +- DataLossPreventionRule +- ExchangeTransportRule (mail flow rule) +- HostedContentFilterPolicy (anti-spam policy) +- SafeAttachmentPolicy (Microsoft Defender for Office 365 only) + +You can specify multiple values separated by commas. + +```yaml +Type: QuarantinePolicyTypeEnum[] +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineTypes +The QuarantineTypes parameter filters the results by what caused the message to be quarantined. Valid values are: + +- Bulk +- DataLossPrevention +- FileTypeBlock (common attachments filter in anti-malware policies in EOP) +- HighConfPhish +- Malware (anti-malware policies in EOP or Safe Attachments policies in Defender for Office 365) +- Phish +- Spam +- SPOMalware (Microsoft Defender for Office 365 only) +- TransportRule + +You can specify multiple values separated by commas. + +You don't need to use this parameter with the Type parameter. + +For files quarantined by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams, the detection information can be found in CustomData field in the output. + +```yaml +Type: QuarantineMessageTypeEnum[] +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientTag +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. + +```yaml +Type: String[] +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReleaseStatus +The ReleaseStatus parameter filters the results by the release status of the message. Valid values are: + +- Approved +- Denied +- Error +- NotReleased +- PreparingToRelease +- Released +- Requested + +You can specify multiple values separated by commas. + +**Note**: Messages that were quarantined and released by Microsoft due to a service issue have the SystemReleased property value TRUE. To filter the results by system released messages, run the following command: `Get-QuarantineMessage | where {$_.systemreleased -like "True"}`. + +```yaml +Type: ReleaseStatus[] +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Reported +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. +- $false: The command only returns quarantined messages that haven't been reported as false positives. + +```yaml +Type: Boolean +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartExpiresDate +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". + +For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days. + +```yaml +Type: System.DateTime +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartReceivedDate +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". + +By default, if you don't use the StartReceivedDate and EndReceivedDate parameters, the command will return data for the last 16 days. The maximum value for this parameter is 30 days. If you use a value that's older than 30 days, the value is ignored and only data for the last 30 days is returned. + +```yaml +Type: System.DateTime +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Subject +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsConversationTypes +This parameter is available only in Security & Compliance PowerShell. + +The TeamsConversationTypes parameters filters the results by Microsoft Teams conversation types. Valid values are: + +- Channel +- Chat + +You can specify multiple values separated by commas. + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.TeamsConversationType[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Type +The Type parameter filters the results by what caused the message to be quarantined. Valid values are: + +- Bulk +- DataLossPrevention +- HighConfPhish +- Malware +- Phish +- Spam +- SPOMalware (Microsoft Defender for Office 365 only) +- TransportRule + +You don't need to use this parameter with the QuarantineTypes parameter. + +For files protected by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams, the detection information can be found in CustomData field in the output. + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.QuarantineMessageTypeEnum +Parameter Sets: Summary +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-QuarantineMessageHeader.md b/exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md new file mode 100644 index 0000000000..9dac21f945 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md @@ -0,0 +1,119 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-QuarantineMessageHeader + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-QuarantineMessageHeader cmdlet to view the message header of a quarantined message. The command will fail if the specified message is not in quarantine. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-QuarantineMessageHeader -Identity + [-EntityType ] + [-RecipientAddress ] + [] +``` + +## DESCRIPTION +Standard SMTP message header syntax is described in RFC 5322. This cmdlet displays the message header exactly as it appears in the message. Individual header fields are not unfolded. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-QuarantineMessageHeader 65ab8c7d-dcd3-4067-7c60-08d116c001c3\8b677327-0ef3-166b-e108-ff6cb380d191 +``` + +This example displays the message header of the quarantined message that has the specified Identity value. + +### Example 2 +```powershell +$qMessages = Get-QuarantineMessage + +Get-QuarantineMessageHeader $qMessages[0].Identity +``` + +This example displays the message header of the first message that's returned by Get-QuarantineMessage cmdlet. + +## PARAMETERS + +### -Identity +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. + +```yaml +Type: QuarantineMessageIdentity +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -EntityType +The EntityType parameter filters the results by EntityType. Valid values are: + +- Email +- SharePointOnline +- Teams (currently in Preview) +- DataLossPrevention + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-QuarantinePolicy.md b/exchange/exchange-ps/exchange/Get-QuarantinePolicy.md new file mode 100644 index 0000000000..93177a8f2a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-QuarantinePolicy.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-QuarantinePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-QuarantinePolicy cmdlet to view quarantine policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-QuarantinePolicy [[-Identity] ] + [-QuarantinePolicyType ] + [] +``` + +## DESCRIPTION +Quarantine policies define what users are allowed to do to quarantined messages based on why the message was quarantined (for supported features) and quarantine notification settings. For more information, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-QuarantinePolicy | Format-Table Name +``` + +This example returns as summary list of all quarantine policies. + +### Example 2 +```powershell +Get-QuarantinePolicy -Identity NoAccess +``` + +This example returns detailed information about the quarantine policy named NoAccess. + +### Example 3 +```powershell +Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy +``` + +This example returns detailed information about the default quarantine policy named DefaultGlobalTag that controls the global quarantine notification (formerly known as end-user spam notification) settings. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: QuarantineTagIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -QuarantinePolicyType +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. +- GlobalQuarantinePolicy: This value is required to return the global settings (quarantine notification settings) in the quarantine policy named DefaultGlobalTag. + +```yaml +Type: QuarantinePolicyType +Parameter Sets: (All) +Aliases: +Accepted values: QuarantinePolicy, GlobalQuarantinePolicy +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-Queue.md b/exchange/exchange-ps/exchange/Get-Queue.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Get-Queue.md rename to exchange/exchange-ps/exchange/Get-Queue.md index 8e310437aa..1b83dcd4a3 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-Queue.md +++ b/exchange/exchange-ps/exchange/Get-Queue.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-queue +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-Queue @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-Queue cmdlet to view configuration information for queues on Mailbox servers or Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,12 +31,14 @@ Get-Queue [[-Identity] ] [-ResultSize ] [-ReturnPageInfo ] [-SearchForward ] - [-SortOrder ] [] + [-SortOrder ] + [] ``` ### Server ``` -Get-Queue [-Server ] [-Filter ] +Get-Queue [-Server ] + [-Filter ] [-BookmarkIndex ] [-BookmarkObject ] [-Exclude ] @@ -46,11 +47,12 @@ Get-Queue [-Server ] [-Filter ] [-ResultSize ] [-ReturnPageInfo ] [-SearchForward ] - [-SortOrder ] [] + [-SortOrder ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -85,7 +87,7 @@ This example lists only the external queues. ## PARAMETERS ### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity). +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 @@ -136,9 +138,7 @@ Accept wildcard characters: False The Exclude parameter specifies the types of queues you want to exclude from the results. Valid values for this parameter are: - Internal - - External - - A valid queue DeliveryType value. For details, see the NextHopSolutionKey section in Queues and messages in queues. ```yaml @@ -155,7 +155,7 @@ Accept wildcard characters: False ``` ### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell). +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 ("). @@ -176,9 +176,7 @@ Accept wildcard characters: False The Include parameter specifies the types of queues you want to include the results. Valid values for this parameter are: - Internal - - External - - A valid queue DeliveryType value. For details, see the NextHopSolutionKey section in Queues and messages in queues. ```yaml @@ -262,11 +260,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -309,12 +304,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-QueueDigest.md b/exchange/exchange-ps/exchange/Get-QueueDigest.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/Get-QueueDigest.md rename to exchange/exchange-ps/exchange/Get-QueueDigest.md index cf196517cf..a45a074bd3 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-QueueDigest.md +++ b/exchange/exchange-ps/exchange/Get-QueueDigest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-queuedigest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-QueueDigest @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the Get-QueueDigest cmdlet to view information about message delivery queues across database availability groups (DAGs) Active Directory sites, or Active Directory forests in your organization. -By default, the Get-QueueDigest cmdlet displays delivery queues that contain ten or more messages, and the results are between one and two minutes old. For instructions on how to change these default values, see [Configure Get-QueueDigest](https://docs.microsoft.com/exchange/configure-get-queuedigest-exchange-2013-help). +By default, the Get-QueueDigest cmdlet displays delivery queues that contain ten or more messages, and the results are between one and two minutes old. For instructions on how to change these default values, see [Configure Get-QueueDigest](https://learn.microsoft.com/exchange/configure-get-queuedigest-exchange-2013-help). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,7 +29,8 @@ Get-QueueDigest -Dag [-Filter ] [-GroupBy ] [-ResultSize ] - [-Timeout ] [] + [-Timeout ] + [] ``` ### Forest @@ -40,7 +40,8 @@ Get-QueueDigest [-Forest] [-Filter ] [-GroupBy ] [-ResultSize ] - [-Timeout ] [] + [-Timeout ] + [] ``` ### Server @@ -49,9 +50,9 @@ Get-QueueDigest -Server [-DetailsLevel ] [-Filter ] [-GroupBy ] - [-IncludeE14Servers] [-ResultSize ] - [-Timeout ] [] + [-Timeout ] + [] ``` ### Site @@ -60,13 +61,13 @@ Get-QueueDigest -Site [-DetailsLevel ] [-Filter ] [-GroupBy ] - [-IncludeE14Servers] [-ResultSize ] - [-Timeout ] [] + [-Timeout ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -175,7 +176,7 @@ Accept wildcard characters: False ``` ### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell). +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 ("). @@ -196,21 +197,13 @@ Accept wildcard characters: False The GroupedBy parameter sorts the messages in the delivery queue results. Valid values are: - DeliveryType - - LastError - - NextHopCategory - - NextHopDomain (this is the default value) - - NextHopKey - - RiskLevel - - Status - - ServerName - - OutboundIPPool ```yaml @@ -265,12 +258,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTemplate.md b/exchange/exchange-ps/exchange/Get-RMSTemplate.md similarity index 88% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTemplate.md rename to exchange/exchange-ps/exchange/Get-RMSTemplate.md index f59e7b0e6d..e495368203 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTemplate.md +++ b/exchange/exchange-ps/exchange/Get-RMSTemplate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-rmstemplate -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-RMSTemplate @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-RMSTemplate cmdlet to retrieve the current list of active rights policy templates from the Active Directory Rights Management Services (AD RMS) deployment for the organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,7 +32,7 @@ Get-RMSTemplate [[-Identity] ] ## DESCRIPTION The Get-RMSTemplate cmdlet doesn't return any active rights policy templates if internal licensing isn't enabled. Use the Get-IRMConfiguration cmdlet to check the InternalLicensingEnabled parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,37 +52,37 @@ This example retrieves the Company Confidential RMS template. ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the name of the RMS template. ```yaml -Type: Fqdn +Type: RmsTemplateIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the RMS template. +### -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. ```yaml -Type: RmsTemplateIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -94,7 +93,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -109,16 +108,14 @@ 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: - Name - - Distinguished name (DN) - - GUID ```yaml Type: RmsTrustedPublishingDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -133,16 +130,14 @@ 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: - All - - Archived - - Distributed ```yaml Type: RmsTemplateType Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -156,12 +151,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-ReceiveConnector.md b/exchange/exchange-ps/exchange/Get-ReceiveConnector.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Get-ReceiveConnector.md rename to exchange/exchange-ps/exchange/Get-ReceiveConnector.md index cba306b6ad..f34ec98584 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-ReceiveConnector.md +++ b/exchange/exchange-ps/exchange/Get-ReceiveConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-receiveconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ReceiveConnector @@ -17,26 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ReceiveConnector cmdlet to view Receive connectors on Mailbox servers and Edge Transport servers. Receive connectors listen for inbound SMTP connections on the Exchange server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` Get-ReceiveConnector [[-Identity] ] - [-DomainController ] [] + [-DomainController ] + [] ``` ### Server ``` Get-ReceiveConnector [-Server ] - [-DomainController ] [] + [-DomainController ] + [] ``` ## DESCRIPTION You can view Receive connectors on Mailbox servers and Edge Transport servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,34 +57,13 @@ This example displays detailed information for the Receive connector named Recei ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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 - - Distinguished name (DN) - - GUID - -- \\\\ +- ServerName\\Name You can't use this parameter with the Server parameter. @@ -100,15 +80,30 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Server 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use this parameter with the Identity parameter. @@ -131,12 +126,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-Recipient.md b/exchange/exchange-ps/exchange/Get-Recipient.md new file mode 100644 index 0000000000..4b5a71f8b1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-Recipient.md @@ -0,0 +1,635 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-Recipient + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-Recipient cmdlet to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). + +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXORecipient cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). + +In cloud environments, to return Microsoft 365 Groups, you need to use the RecipientTypeDetails parameter with the value GroupMailbox. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AnrSet +``` +Get-Recipient [-Anr ] + [-AuthenticationType ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-PropertySet ] + [-ReadFromDomainController] + [-RecipientType ] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SortBy ] + [-Capabilities ] + [-Database ] + [-Properties ] + [-IncludeManagerWithDisplayName] + [-IncludeSoftDeletedRecipients] + [] +``` + +### Identity +``` +Get-Recipient [[-Identity] ] + [-AuthenticationType ] + [-BookmarkDisplayName ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeBookmarkObject ] + [-OrganizationalUnit ] + [-PropertySet ] + [-ReadFromDomainController] + [-RecipientType ] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SortBy ] + [-Capabilities ] + [-Properties ] + [-IncludeManagerWithDisplayName] + [-IncludeSoftDeletedRecipients] + [] +``` + +### DatabaseSet +``` +Get-Recipient [-Database ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-Properties ] + [-PropertySet ] + [-ReadFromDomainController] + [-RecipientType ] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SortBy ] + [-IncludeSoftDeletedRecipients] + [] + [] +``` + +### RecipientPreviewFilterSet +``` +Get-Recipient [-RecipientPreviewFilter ] + [-AuthenticationType ] + [-Capabilities ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeManagerWithDisplayName] + [-IncludeSoftDeletedRecipients] + [-OrganizationalUnit ] + [-Properties ] + [-PropertySet ] + [-ReadFromDomainController] + [-RecipientType ] + [-RecipientTypeDetails ] + [-ResultSize ] + [-SortBy ] + [] +``` + +## DESCRIPTION +The Get-Recipient cmdlet may not return all object-specific properties for a recipient. To view the object-specific properties for a recipient, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox, Get-MailUser, or Get-DistributionGroup). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-Recipient -ResultSize unlimited +``` + +This example retrieves as summary list of all recipients in your organization. + +### Example 2 +```powershell +Get-Recipient -Identity "Marketing Department" | Format-List +``` + +This example returns detailed information for the recipient named Marketing Department. + +### Example 3 +```powershell +Get-Recipient -RecipientType MailContact -SortBy Office | Format-Table -Auto Office,Name +``` + +This example retrieves information about all the mail contacts in your organization and sorts them by office. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuthenticationType +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: + +- Federated +- Managed + +```yaml +Type: AuthenticationType +Parameter Sets: AnrSet, Identity, RecipientPreviewFilterSet +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookmarkDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Capabilities +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: AnrSet, Identity, RecipientPreviewFilterSet +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +This parameter is available only in on-premises Exchange. + +The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. + +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: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Database +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: DatabaseIdParameter +Parameter Sets: DatabaseSet +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeBookmarkObject +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeManagerWithDisplayName +This parameter is available only in the cloud-based service. + +{{ Fill IncludeManagerWithDisplayName Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet, RecipientPreviewFilterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedRecipients +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. + +**Note**: Use this switch with the Identity or RecipientTypeDetails parameters to get the SoftDeletedRecipients. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Properties +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PropertySet +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientPreviewFilter +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientType +The RecipientType parameter filters the results by the specified recipient type. Valid values are: + +- DynamicDistributionGroup +- MailContact +- MailNonUniversalGroup +- MailUniversalDistributionGroup +- MailUniversalSecurityGroup +- MailUser +- PublicFolder +- UserMailbox + +You can specify multiple values separated by commas. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientTypeDetails +The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are: + +- DiscoveryMailbox +- DynamicDistributionGroup +- EquipmentMailbox +- GroupMailbox (Exchange 2013 or later and cloud) +- GuestMailUser (Exchange 2016 or later and cloud) +- LegacyMailbox +- LinkedMailbox +- LinkedRoomMailbox (Exchange 2013 or later and cloud) +- MailContact +- MailForestContact +- MailNonUniversalGroup +- MailUniversalDistributionGroup +- MailUniversalSecurityGroup +- MailUser +- PublicFolder +- PublicFolderMailbox (Exchange 2013 or later and cloud) +- RemoteEquipmentMailbox +- RemoteRoomMailbox +- RemoteSharedMailbox +- RemoteTeamMailbox (Exchange 2013 or later and cloud) +- RemoteUserMailbox +- RoomList +- RoomMailbox +- SchedulingMailbox (Exchange 2016 or later and cloud) +- SharedMailbox +- SharedWithMailUser (cloud only) +- TeamMailbox (Exchange 2013 or later and cloud) +- UserMailbox + +You can specify multiple values separated by commas. + +The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName +- Alias +- City +- FirstName +- LastName +- Office +- ServerLegacyDN + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/antispam-antimalware/Get-RecipientFilterConfig.md b/exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md similarity index 87% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-RecipientFilterConfig.md rename to exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md index a0e801225f..76a02ece24 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-RecipientFilterConfig.md +++ b/exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-recipientfilterconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-RecipientFilterConfig @@ -17,17 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-RecipientFilterConfig cmdlet to view the recipient filter configuration information for the Exchange server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-RecipientFilterConfig [[-Identity] ] [-DomainController ] +Get-RecipientFilterConfig [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -40,37 +40,37 @@ This example returns detailed information about the recipient filter configurati ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +This parameter is reserved for internal Microsoft use. ```yaml -Type: Fqdn +Type: OrganizationIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -This parameter is reserved for internal Microsoft use. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: OrganizationIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -79,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-RecipientPermission.md b/exchange/exchange-ps/exchange/Get-RecipientPermission.md new file mode 100644 index 0000000000..985fc7ff66 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RecipientPermission.md @@ -0,0 +1,187 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-RecipientPermission + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-RecipientPermission cmdlet to view information about SendAs permissions that are configured for users in a cloud-based organization. + +**Note**: In Exchange Online PowerShell, we recommend that you use the Get-EXORecipientPermission cmdlet instead of this cmdlet. For more information, see [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RecipientPermission [[-Identity] ] + [-AccessRights ] + [-ReadFromDomainController] + [-ResultSize ] + [-Trustee ] + [] +``` + +## DESCRIPTION +When a user is given SendAs permission to another user or group, the user can send messages that appear to come from the other user or group. + +> [!NOTE] +> This cmdlet doesn't return expected results when the recipient specified by the Trustee parameter has multiple `SecurityPrincipalIdParameter` (Sid) values. When you use the Trustee parameter, the command compares the Sid of the specified Trustee with the recipient's access control list (ACL) record. If some of the recipient's Sid values have changed, there's a mismatch. The workaround is to not to use the user principal name (UPN) value, to use all Sids including the one for history. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RecipientPermission -Trustee "Kim Akers" +``` + +This example lists the recipients for whom the user Kim Akers has SendAs permission. Kim can send messages that appear to come directly from the recipients. + +### Example 2 +```powershell +Get-RecipientPermission "Help Desk" +``` + +This example lists the users who have SendAs permission on the mailbox Help Desk. The users listed can send messages that appear to come directly from the Help Desk mailbox. + +## PARAMETERS + +### -Identity +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 +- Mail users +- External contacts +- Distribution groups +- Dynamic distribution groups + +You can use any value that uniquely identifies the recipient. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccessRights +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Trustee +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 +- Mail users with a Microsoft account +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/reporting/Get-RecipientStatisticsReport.md b/exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md similarity index 75% rename from exchange/exchange-ps/exchange/reporting/Get-RecipientStatisticsReport.md rename to exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md index 03354ca10c..8f2d888cba 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-RecipientStatisticsReport.md +++ b/exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-recipientstatisticsreport +online version: https://learn.microsoft.com/powershell/module/exchange/get-recipientstatisticsreport applicable: Exchange Online title: Get-RecipientStatisticsReport schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-RecipientStatisticsReport @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Get-RecipientStatisticsReport cmdlet to view the recipient statistics report. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,7 +27,7 @@ Get-RecipientStatisticsReport [] ## DESCRIPTION The recipient statistics report provides information about the total number of mailboxes and the total number of active mailboxes in the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,12 +45,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md new file mode 100644 index 0000000000..4f413a8bf3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md @@ -0,0 +1,50 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-RecordReviewNotificationTemplateConfig + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-RecordReviewNotificationTemplateConfig cmdlet to view the record review notification and reminder settings. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RecordReviewNotificationTemplateConfig [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RecordReviewNotificationTemplateConfig +``` + +This example shows detailed information about the record review notification template configuration. + +## 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-RecoverableItems.md b/exchange/exchange-ps/exchange/Get-RecoverableItems.md similarity index 81% rename from exchange/exchange-ps/exchange/mailboxes/Get-RecoverableItems.md rename to exchange/exchange-ps/exchange/Get-RecoverableItems.md index 4de2ae8410..aebb11746e 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-RecoverableItems.md +++ b/exchange/exchange-ps/exchange/Get-RecoverableItems.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/Get-RecoverableItems +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-RecoverableItems @@ -16,9 +15,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-RecoverableItems items cmdlet to view deleted items in mailboxes. After you find the deleted items, you use the Restore-RecoverableItems cmdlet to restore them. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -45,20 +44,22 @@ Get-RecoverableItems -Identity [-FilterStartTime ] [-LastParentFolderID ] [-MaxParallelSize ] + [-PolicyTag ] [-ResultSize ] + [-SkipCount ] [-SourceFolder ] [-SubjectContains ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-RecoverableItems -Identity laura@contoso.com -Subject -SubjectContains "FY17 Accounting" -FilterItemType IPM.Note -FilterStartTime "2/1/2018 12:00:00 AM" -FilterEndTime "2/5/2018 11:59:59 PM" +Get-RecoverableItems -Identity laura@contoso.com -SubjectContains "FY17 Accounting" -FilterItemType IPM.Note -FilterStartTime "2/1/2018 12:00:00 AM" -FilterEndTime "2/5/2018 11:59:59 PM" ``` This example returns all of the available recoverable deleted messages with the specified subject in the mailbox laura@contoso.com for the specified date/time range. @@ -70,33 +71,23 @@ Get-RecoverableItems -Identity "malik@contoso.com", "lillian@contoso.com" -Filte This example returns all of the available recoverable deleted messages with the specified subject in the mailboxes of both malik@contoso.com and lillian@contoso.com for the specified date/time range. - ## PARAMETERS ### -Identity 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -In tExchange Online, you can specify multiple mailboxes separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +In Exchange Online, you can specify multiple mailboxes separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. ```yaml Type: GeneralMailboxOrMailUserIdParameter @@ -143,9 +134,9 @@ Accept wildcard characters: False ``` ### -FilterEndTime -The FilterEndTime specifies the end date/time of the date range. +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". +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". ```yaml Type: DateTime @@ -164,13 +155,9 @@ Accept wildcard characters: False The FilterItemType parameter filters the results by the specified MessageClass (ItemClass) property value of the deleted item. For example: - IPM.Appointment (Meetings and appointments) - - IPM.Contact - - IPM.File - - IPM.Note - - IPM.Task ```yaml @@ -187,9 +174,9 @@ Accept wildcard characters: False ``` ### -FilterStartTime -The FilterStartTime specifies the start date/time of the date range. +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". +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". ```yaml Type: DateTime @@ -240,6 +227,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PolicyTag +This parameter is available only in the cloud-based service. + +{{ Fill PolicyTag Description }} + +```yaml +Type: String[] +Parameter Sets: Cloud +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ResultSize The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. @@ -256,23 +261,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SourceFolder -The SourceFolder parameter specifies where to search for deleted items in the mailbox. Valid values are: - -- DeletedItems: The Deleted Items folder. - -- RecoverableItems: The Recoverable Items\Deletions folder. This folder contains items that have been deleted from the Deleted Items folder (soft-deleted items). - -- PurgedItems: (Cloud only) The Recoverable Items\Purges folder. This folder contains items that have been purged from the Recoverable Items folder (hard-deleted items). +### -SkipCount +This parameter is available only in the cloud-based service. -If you don't use this parameter, the command will search all of these folders. +{{ Fill SkipCount Description }} ```yaml -Type: RecoverableItemsFolderType -Parameter Sets: OnPremises +Type: Int32 +Parameter Sets: (All) Aliases: -Accepted values: DeletedItems | RecoverableItems -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online Required: False Position: Named @@ -281,12 +279,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceFolder +The SourceFolder parameter specifies where to search for deleted items in the mailbox. Valid values are: + +- DeletedItems: The Deleted Items folder. +- RecoverableItems: The Recoverable Items\Deletions folder. This folder contains items that have been deleted from the Deleted Items folder (soft-deleted items). +- PurgedItems: The Recoverable Items\Purges folder. This folder contains items that have been purged from the Recoverable Items folder (hard-deleted items). + +If you don't use this parameter, the command searches those three folders. + +- DiscoveryHoldsItems (cloud-only): The Recoverable Items\DiscoveryHolds folder. This folder contains items that have been purged from the Recoverable Items folder (hard-deleted items) and are protected by a hold. To search for deleted items in this folder, use this parameter with the value DiscoveryHoldsItems. + ```yaml Type: RecoverableItemsFolderType -Parameter Sets: Cloud +Parameter Sets: (All) Aliases: -Accepted values: DeletedItems | RecoverableItems | PurgedItems -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -316,12 +324,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md b/exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md new file mode 100644 index 0000000000..69ceb96099 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md @@ -0,0 +1,48 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/get-regulatorycomplianceui +applicable: Security & Compliance +title: Get-RegulatoryComplianceUI +schema: 2.0.0 +--- + +# Get-RegulatoryComplianceUI + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell) +. + +Use the Get-RegulatoryComplianceUI cmdlet to view the status of the regulatory compliance UI in the Microsoft Purview compliance portal (whether the preservation lock checkbox is displayed for retention policies and the immutable label checkbox is displayed for retention labels). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RegulatoryComplianceUI [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RegulatoryComplianceUI +``` + +This example returns the status of regulatory compliance UI. + +## 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-RemoteDomain.md b/exchange/exchange-ps/exchange/Get-RemoteDomain.md similarity index 80% rename from exchange/exchange-ps/exchange/mail-flow/Get-RemoteDomain.md rename to exchange/exchange-ps/exchange/Get-RemoteDomain.md index 581de4cef1..ea01811a75 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-RemoteDomain.md +++ b/exchange/exchange-ps/exchange/Get-RemoteDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-remotedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-RemoteDomain @@ -17,16 +16,19 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-RemoteDomain cmdlet to view the configuration information for the remote domains configured in your organization. You can view the remote domain configuration from inside the Exchange organization or from an Edge Transport server in the perimeter network. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-RemoteDomain [[-Identity] ] [-DomainController ] [] +Get-RemoteDomain [[-Identity] ] + [-DomainController ] + [-ResultSize ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,6 +55,26 @@ This example returns all domains where Transport Neutral Encapsulation Format (T ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DomainController This parameter is available only in on-premises Exchange. @@ -73,25 +95,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) +### -ResultSize +This parameter is available only in the cloud-based service. -- GUID +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: RemoteDomainIdParameter +Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -100,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-RemoteMailbox.md b/exchange/exchange-ps/exchange/Get-RemoteMailbox.md similarity index 80% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Get-RemoteMailbox.md rename to exchange/exchange-ps/exchange/Get-RemoteMailbox.md index 8dec7a3a2b..f40415ec08 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-RemoteMailbox.md +++ b/exchange/exchange-ps/exchange/Get-RemoteMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-remotemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-RemoteMailbox @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-RemoteMailbox cmdlet to retrieve the mail-related attributes of users in the on-premises organization that have associated mailboxes in the cloud-based service. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -50,9 +49,9 @@ Get-RemoteMailbox [[-Identity] ] ``` ## DESCRIPTION -The Get-RemoteMailbox cmdlet retrieves the mail-related attributes of a mail user in the on-premises Active Directory. It doesn't retrieve the attributes of the associated cloud-based mailbox. Most of the mail-related attributes of the on-premises mail user and the associated cloud-based mailbox should be the same. However, the cloud-based mailbox has additional attributes that you can't view by using this cmdlet. To view the attributes of the cloud-based mailbox, you need to use the Exchange admin center in the cloud-based service, or use remote PowerShell to connect to your cloud-based organization and run the Get-Mailbox cmdlet. +The Get-RemoteMailbox cmdlet retrieves the mail-related attributes of a mail user in the on-premises Active Directory. It doesn't retrieve the attributes of the associated cloud-based mailbox. Most of the mail-related attributes of the on-premises mail user and the associated cloud-based mailbox should be the same. However, the cloud-based mailbox has additional attributes that you can't view by using this cmdlet. To view the attributes of the cloud-based mailbox, you need to use the Exchange admin center in the cloud-based service, or connect to your cloud-based organization and run the Get-Mailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,7 +71,9 @@ This example returns a detailed information for the remote mailbox for the user ### Example 3 ```powershell -$Credentials = Get-Credential; Get-RemoteMailbox -Credential $Credentials +$Credentials = Get-Credential + +Get-RemoteMailbox -Credential $Credentials ``` This example uses alternate credentials to retrieve a list of one or more mail-enabled users with mailboxes in the service. This is useful if the account you typically use doesn't have administrative permissions. The credentials are used to access the on-premises Active Directory domain controllers. @@ -81,17 +82,40 @@ First, run the following command to prompt you for your credentials and then sto ## PARAMETERS +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: RemoteMailboxIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -126,7 +150,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -158,19 +182,16 @@ Accept wildcard characters: False ``` ### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). +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'"`. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -185,49 +206,12 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: RemoteMailboxIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -249,11 +233,8 @@ The OnPremisesOrganizationalUnit parameter filters the results by the object's l 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -270,7 +251,9 @@ Accept wildcard characters: False ``` ### -ReadFromDomainController -The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -290,6 +273,8 @@ Accept wildcard characters: False ### -ResultSize The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. +**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). + ```yaml Type: Unlimited Parameter Sets: (All) @@ -306,14 +291,12 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the following properties: - Name - - DisplayName - - Alias ```yaml @@ -334,12 +317,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md b/exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md new file mode 100644 index 0000000000..134a709559 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md @@ -0,0 +1,91 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ReportExecutionInstance + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ReportExecutionInstance cmdlet to review the report execution instance in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ReportExecutionInstance [-Identity ] + [-ScheduleId ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ReportExecutionInstance | Format-Table -Auto Identity,ScheduleId,ReportStartDate,ReportEndDate +``` + +This example returns a summary list of all report execution instances. + +### Example 2 +```powershell +Get-ReportExecutionInstance -Identity 277df7c3-5b73-4409-6264-08d4a8052836 +``` + +This example returns detailed information for the specified report execution instance. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ScheduleId +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md b/exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md new file mode 100644 index 0000000000..483f073460 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md @@ -0,0 +1,70 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ReportSubmissionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ReportSubmissionPolicy cmdlet to view the report submission policy in your cloud-based organization. The report submission policy controls most of the user reported message settings in the organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ReportSubmissionPolicy [[-Identity] ] [] +``` + +## DESCRIPTION +The report submission policy controls most of the settings for user submissions in the Microsoft Defender portal at . + +The report submission rule (\*-ReportSubmissionRule cmdlets) controls the email address of the reporting mailbox where user reported messages are delivered. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ReportSubmissionPolicy +``` + +This example returns the settings of the report submission policy in your organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md new file mode 100644 index 0000000000..f64f8d899b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md @@ -0,0 +1,88 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ReportSubmissionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ReportSubmissionRule cmdlet to view the report submission rule in your cloud-based organization. The report submission rule identifies the reporting mailbox where user reported messages are delivered. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ReportSubmissionRule [[-Identity] ] [-State ] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ReportSubmissionRule +``` + +This example returns detailed information about the report submission rule in your organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -State +The State parameter filters the results by whether the report submission rule is enabled or disabled. Valid values are: + +- Disabled +- Enabled + +Remember, there's only one rule in your organization. + +```yaml +Type: RuleState +Parameter Sets: (All) +Aliases: +Accepted values: Enabled, Disabled +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-ResourceConfig.md b/exchange/exchange-ps/exchange/Get-ResourceConfig.md similarity index 83% rename from exchange/exchange-ps/exchange/mailboxes/Get-ResourceConfig.md rename to exchange/exchange-ps/exchange/Get-ResourceConfig.md index 8bca626668..e5087116d5 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-ResourceConfig.md +++ b/exchange/exchange-ps/exchange/Get-ResourceConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-resourceconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-ResourceConfig @@ -17,16 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-ResourceConfig cmdlet to view custom room and equipment mailbox properties that you've configured by using the Set-ResourceConfig cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ResourceConfig [[-Identity] ] [-DomainController ] [] +Get-ResourceConfig [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -39,37 +40,39 @@ This example returns all of the available custom room and equipment mailbox prop ## PARAMETERS -### -DomainController +### -Identity This parameter is available only in on-premises Exchange. -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +This parameter is reserved for internal Microsoft use. ```yaml -Type: Fqdn +Type: OrganizationIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -This parameter is reserved for internal Microsoft use. +### -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. ```yaml -Type: OrganizationIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -78,12 +81,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-ResubmitRequest.md b/exchange/exchange-ps/exchange/Get-ResubmitRequest.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/Get-ResubmitRequest.md rename to exchange/exchange-ps/exchange/Get-ResubmitRequest.md index a2f4796116..e6837d4223 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-ResubmitRequest.md +++ b/exchange/exchange-ps/exchange/Get-ResubmitRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-resubmitrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ResubmitRequest @@ -17,17 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ResubmitRequest cmdlet to view requests to replay redundant copies of messages from Safety Net after a mailbox database recovery. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ResubmitRequest [[-Identity] ] [-Server ] +Get-ResubmitRequest [[-Identity] ] + [-Server ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,11 +67,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -94,12 +91,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md new file mode 100644 index 0000000000..fbb20052f5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md @@ -0,0 +1,210 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-RetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-RetentionCompliancePolicy to view existing retention policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RetentionCompliancePolicy [[-Identity] ] + [-DistributionDetail] + [-ErrorPolicyOnly] + [-ExcludeTeamsPolicy] + [-IncludeTestModeResults] + [-PriorityCleanup] + [-RetentionRuleTypes] + [-TeamsPolicyOnly] + [] +``` + +## DESCRIPTION +This list describes the properties that are displayed by default. + +- Name: The unique name of the policy. +- Workload: At the moment, it will show all workloads (Exchange, SharePoint, OneDriveForBusiness, Skype, ModernGroup) and it will not show the actual workload on which the policy is applied. +- Enabled: The value True means the policy is enabled. +- Mode: The current operating mode of the policy. The possible values are Test (the content is tested, but no rules are enforced), AuditAndNotify (when content matches the conditions specified by the policy, the rule is not enforced, but notification emails are sent) or Enforce (all aspects of the policy are enabled and enforced). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RetentionCompliancePolicy +``` + +This example displays summary information for all retention policies in your organization. + +### Example 2 +```powershell +Get-RetentionCompliancePolicy -Identity "Regulation 123 Compliance" -DistributionDetail | Format-List +``` + +This example displays detailed information for the policy named "Regulation 123 Compliance", including accurate values for the DistributionStatus and \*Location properties. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DistributionDetail +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ErrorPolicyOnly +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 +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeTeamsPolicy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeTestModeResults +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). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionRuleTypes +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsPolicyOnly +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md new file mode 100644 index 0000000000..9c1279ce96 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-RetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-RetentionComplianceRule to view retention rules in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RetentionComplianceRule [[-Identity] ] + [-Policy ] + [-PriorityCleanup] + [] +``` + +## DESCRIPTION +This list describes the properties that are displayed by default in the summary information. + +- Name: The unique name of the rule. +- Disabled: The enabled or disabled status of the rule. +- Mode: The current operating mode of the rule (for example, Enforce). +- Comment: An administrative comment. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RetentionComplianceRule +``` + +This example displays summary information for all retention rules in your organization. + +### Example 2 +```powershell +Get-RetentionComplianceRule -Identity "30 Day Rule" | Format-List +``` + +This example displays detailed information for the retention rule named "30 Day Rule". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the retention rule you want to view. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +You can use this parameter with the Identity parameter in the same command. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-RetentionEvent.md b/exchange/exchange-ps/exchange/Get-RetentionEvent.md new file mode 100644 index 0000000000..c650acf830 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RetentionEvent.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-RetentionEvent + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-RetentionEvent cmdlet to view retention events in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RetentionEvent [[-Identity] ] + [-AllStatus] + [-DomainController ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RetentionEvent +``` + +This example returns a summary list of all retention events. + +### Example 2 +```powershell +Get-RetentionEvent -Identity x | Format-List +``` + +This example returns detailed information about retention the specified retention event. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AllStatus +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionPolicy.md b/exchange/exchange-ps/exchange/Get-RetentionPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionPolicy.md rename to exchange/exchange-ps/exchange/Get-RetentionPolicy.md index b647f36f6c..231c381cff 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionPolicy.md +++ b/exchange/exchange-ps/exchange/Get-RetentionPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-retentionpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-RetentionPolicy @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-RetentionPolicy cmdlet to retrieve the settings for retention policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-RetentionPolicy [[-Identity] ] [-DomainController ] [] +Get-RetentionPolicy [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION A retention policy is associated with a group of retention policy tags that specify retention settings for items in a mailbox. A policy may contain one default policy tag to move items to an archive mailbox, one default policy tag to delete all items, one default policy tag to delete voicemail items and multiple personal tags to move or delete items. A mailbox can have only one retention policy applied to it. The Get-RetentionPolicy cmdlet displays all policy settings associated with the specified policy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,37 +42,37 @@ This example returns all the properties of the retention policy RP Finance. The ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the policy name. ```yaml -Type: Fqdn +Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the policy name. +### -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. ```yaml -Type: MailboxPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -80,12 +81,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionPolicyTag.md b/exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md similarity index 90% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionPolicyTag.md rename to exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md index a5faa46239..53ece7d08e 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionPolicyTag.md +++ b/exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-retentionpolicytag +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-RetentionPolicyTag @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-RetentionPolicyTag cmdlet to retrieve settings for a retention tag. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,29 +25,30 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-RetentionPolicyTag [[-Identity] ] [-DomainController ] [-IncludeSystemTags] - [-Types ] [] + [-Types ] + [] ``` ### Mailbox ``` -Get-RetentionPolicyTag [-Mailbox ] [-OptionalInMailbox] +Get-RetentionPolicyTag [-Mailbox ] + [-OptionalInMailbox] [-DomainController ] [-IncludeSystemTags] - [-Types ] [] + [-Types ] + [] ``` ## DESCRIPTION Retention tags are used to apply message retention settings to messages or folders. There are three types of retention tags: - Retention policy tags - - Default policy tags - - Personal tags Retention policy tags are applied to default folders such as Inbox and Deleted Items. Personal tags are available to users to tag items and folders. The default policy tag is applied to all items that don't have a tag applied by the user or aren't inherited from the folder they're located in. The Get-RetentionPolicyTag cmdlet displays all the settings for the specified tag. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,42 +82,42 @@ This example returns all retention tags of Inbox and All types and pipes the res ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the name of the tag. ```yaml -Type: Fqdn -Parameter Sets: (All) +Type: RetentionPolicyTagIdParameter +Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the tag. +### -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. ```yaml -Type: RetentionPolicyTagIdParameter -Parameter Sets: Identity +Type: Fqdn +Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -IncludeSystemTags -The IncludeSystemTags switch specifies whether to return any system tags. +The IncludeSystemTags switch specifies whether to return any system tags. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -136,23 +136,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) This parameter only returns default policy tags (DPTs) and personal tags; it doesn't return retention policy tags. @@ -192,33 +183,19 @@ Accept wildcard characters: False The Types parameter specifies the type of retention tag to return. Valid values include: - Calendar - - Contacts - - DeletedItems - - Drafts - - Inbox - - JunkEmail - - Journal - - Notes - - Outbox - - SentItems - - Tasks - - All - - RssSubscriptions - - ConversationHistory - - Personal The parameter accepts multiple values separated by a comma. @@ -241,12 +218,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ReviewItems.md b/exchange/exchange-ps/exchange/Get-ReviewItems.md new file mode 100644 index 0000000000..b9fa1c3b40 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ReviewItems.md @@ -0,0 +1,172 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ReviewItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ReviewItems to retrieve a list of disposition review items that are either pending review or already disposed for a specific retention label. It can also be used to retrieve a list of disposed items for a specific record label. + +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ReviewItems -TargetLabelId + [-Disposed ] + [-IncludeHeaders ] + [-PagingCookie ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +The `Get-ReviewItems` cmdlet can be used to export a list of pending or disposed items from disposition review. To learn more about disposition review, see [Disposition of content](https://learn.microsoft.com/purview/disposition). + +## EXAMPLES + +### Example 1 + +```powershell +$itemsPendingDisposition = Get-ReviewItems -TargetLabelId a8cbeaac-e7aa-42ed-8dba-54200537c9c9 -IncludeHeaders $true + +$formattedExportItems = $itemsPendingDisposition.ExportItems | ConvertFrom-Csv -Header $itemsPendingDisposition.Headers + +$formattedExportItems +``` + +This example retrieves the first page of items pending disposition for the label with the immutable ID value `a8cbeaac-e7aa-42ed-8dba-54200537c9c9`. The results are converted to PSObject types for each item and then output to the screen. + +### Example 2 + +```powershell +$itemsPendingDisposition = Get-ReviewItems -TargetLabelId a8cbeaac-e7aa-42ed-8dba-54200537c9c9 -IncludeHeaders $true -Disposed $true + +$formattedExportItems = $itemsPendingDisposition.ExportItems | ConvertFrom-Csv -Header $itemsPendingDisposition.Headers + +$formattedExportItems | Select Subject,Location,ReviewAction,Comment,DeletedBy,DeletedDate +``` + +This example retrieves all disposed items for the label with an immutable ID of `a8cbeaac-e7aa-42ed-8dba-54200537c9c9` and selects specific columns to output to the screen. + +### Example 3 + +```powershell +$itemsPendingDisposition = Get-ReviewItems -TargetLabelId a8cbeaac-e7aa-42ed-8dba-54200537c9c9 -IncludeHeaders $true + +$exportItems = $itemsPendingDisposition.ExportItems + +While (![string]::IsNullOrEmpty($itemsPendingDisposition.PaginationCookie)) +{ + $itemsPendingDisposition = Get-ReviewItems -TargetLabelId a8cbeaac-e7aa-42ed-8dba-54200537c9c9 -IncludeHeaders $true -PagingCookie $itemsPendingDisposition.PaginationCookie + $exportItems += $itemsPendingDisposition.ExportItems +} + +$exportItems | ConvertFrom-Csv -Header $itemsPendingDisposition.Headers | Export-Csv C:\temp\ItemsPendingDisposition.csv -NoTypeInformation +``` + +This example retrieves all items pending disposition for the label with the immutable ID value `a8cbeaac-e7aa-42ed-8dba-54200537c9c9`. If multiple pages of items exist, the command continues until no more pages exist. The results are exported to the specified CSV file. + +**Note**: Although this cmdlet doesn't limit the number of items/pages that can be retrieved, other throttling might occur. To prevent throttling while retrieving a large number of items, we recommended including breaks in your script. You can use the PagingCookie parameter to pick up where the script left off after a break. + +## PARAMETERS + +### -TargetLabelId +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`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disposed +The Disposed parameter specifies whether to return disposed items instead of items pending disposition. Valid values are: + +- $true: Return disposed items. +- $false: Return items pending disposition. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeHeaders +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. +- $false: Headers are not returned as a property with the review items. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PagingCookie +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. +- As a method of starting where the last operation left off. + +The PagingCookie value is returned in the PaginationCookie property each time the cmdlet is successfully run. If the PaginationCookie is blank (null), there are no more items to retrieve. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Get-RoleAssignmentPolicy.md b/exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md similarity index 76% rename from exchange/exchange-ps/exchange/role-based-access-control/Get-RoleAssignmentPolicy.md rename to exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md index bc044cab64..20474cb2b2 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Get-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/get-roleassignmentpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-RoleAssignmentPolicy @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-RoleAssignmentPolicy cmdlet to view existing management role assignment policies in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-RoleAssignmentPolicy [[-Identity] ] [-DomainController ] [] +Get-RoleAssignmentPolicy [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -For more information about assignment policies, see [Understanding management role assignment policies](https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). +For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,7 +47,7 @@ Get-RoleAssignmentPolicy "End User Policy" | Format-List This example returns the details of the specified assignment policy. The output of the Get-RoleAssignmentPolicy cmdlet is piped to the Format-List cmdlet. -For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ### Example 3 ```powershell @@ -57,43 +58,43 @@ This example returns the default assignment policy. The output of the Get-RoleAssignmentPolicy cmdlet is piped to the Where cmdlet. The Where cmdlet filters out all of the policies except the policy that has the IsDefault property set to $True. -For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ## PARAMETERS -### -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. - -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. +### -Identity +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: Fqdn +Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the assignment policy to view. If the name contains spaces, enclose the name in quotation marks ("). +### -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. + +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. ```yaml -Type: MailboxPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -102,12 +103,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-RoleGroup.md b/exchange/exchange-ps/exchange/Get-RoleGroup.md new file mode 100644 index 0000000000..7e6cfdc324 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RoleGroup.md @@ -0,0 +1,237 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-RoleGroup + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-RoleGroup cmdlet to retrieve a list of management role groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RoleGroup [[-Identity] ] + [-DomainController ] + [-Filter ] + [-ReadFromDomainController] + [-ResultSize ] + [-ShowPartnerLinked] + [-SortBy ] + [] +``` + +## DESCRIPTION +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RoleGroup +``` + +This example retrieves a list of role groups. + +### Example 2 +```powershell +Get-RoleGroup "Recipient Administrators" | Format-List +``` + +This example retrieves the details for the Recipient Administrators role group. + +### Example 3 +```powershell +Get-RoleGroup -ReadFromDomainController +``` + +This example retrieves a list of role groups as seen by the domain controller closest to the user. + +### Example 4 +```powershell +Get-RoleGroup -Filter "RoleGroupType -eq 'Linked'" | Format-Table Name, LinkedGroup +``` + +This example retrieves a list of all linked role groups and the Active Directory security identifier (SID) of the foreign universal security groups (USG) that are linked to each of them. You can then use the SIDs to find the USGs so you can modify their members. + +## PARAMETERS + +### -Identity +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. + +```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: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +You can filter on the following properties: + +- LinkedGroup +- ManagedBy +- Members +- Name +- RoleGroupType (the available values are Standard and Linked) +- DisplayName + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowPartnerLinked +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. + +This type of role group is used in the cloud-based service to allow partner service providers to manage their customer organizations. These types of role groups can't be edited and are not shown by default. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-RoleGroupMember.md b/exchange/exchange-ps/exchange/Get-RoleGroupMember.md new file mode 100644 index 0000000000..8416becc8f --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-RoleGroupMember.md @@ -0,0 +1,141 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-RoleGroupMember + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-RoleGroupMember cmdlet to retrieve a list of members of a management role group. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-RoleGroupMember [-Identity] + [-DomainController ] + [-ReadFromDomainController] + [-ResultSize ] + [] +``` + +## DESCRIPTION +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-RoleGroupMember "Recipient Administrators" +``` + +This example retrieves a list of all the members of the Recipient Administrators role group. + +### Example 2 +```powershell +Get-RoleGroupMember "Organization Administrators" -ReadFromDomainController +``` + +This example retrieves a list of all the members of the Organization Administrators role group as seen by the domain controller closest to the user running the command. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mail-flow/Get-RoutingGroupConnector.md b/exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Get-RoutingGroupConnector.md rename to exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md index b8290a9b30..2f0f384197 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-RoutingGroupConnector.md +++ b/exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-routinggroupconnector +online version: https://learn.microsoft.com/powershell/module/exchange/get-routinggroupconnector applicable: Exchange Server 2010 title: Get-RoutingGroupConnector schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Get-RoutingGroupConnector @@ -17,19 +16,20 @@ This cmdlet is available only in Exchange Server 2010. Use the Get-RoutingGroupConnector cmdlet to view the configuration details of the routing group connectors in a Microsoft Exchange Server 2010 organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-RoutingGroupConnector [[-Identity] ] [-DomainController ] +Get-RoutingGroupConnector [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION The Get-RoutingGroupConnector cmdlet displays the configuration details of routing group connectors that exist when an organization is running Exchange 2010 and Exchange Server 2003. A routing group connector is used to send and receive messages between Exchange 2010 Hub Transport servers and Exchange 2003 bridgehead servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,35 +42,35 @@ This example displays detailed configuration information for the routing group c ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: Fqdn +Type: RoutingGroupConnectorIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: RoutingGroupConnectorIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -79,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-RpcClientAccess.md b/exchange/exchange-ps/exchange/Get-RpcClientAccess.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access-servers/Get-RpcClientAccess.md rename to exchange/exchange-ps/exchange/Get-RpcClientAccess.md index 46a1ffbc58..adedda699a 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-RpcClientAccess.md +++ b/exchange/exchange-ps/exchange/Get-RpcClientAccess.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-rpcclientaccess +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-RpcClientAccess @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-RpcClientAccess cmdlet to view the settings of the Microsoft Exchange RPC Client Access service on Exchange servers that have the Client Access server role installed. These settings affect Outlook clients that connect by using Outlook Anywhere (RPC over HTTP). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-RpcClientAccess [-DomainController ] [-Server ] [] +Get-RpcClientAccess [-DomainController ] + [-Server ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,11 +69,8 @@ The Server parameter specifies the Exchange server that you want to view. You can use any value that uniquely identifies the server. For example: - Name (for example, Exchange01) - - Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com) - - Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01) - - GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942) ```yaml @@ -93,12 +91,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-SCInsights.md b/exchange/exchange-ps/exchange/Get-SCInsights.md new file mode 100644 index 0000000000..7675f4455f --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SCInsights.md @@ -0,0 +1,87 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SCInsights + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SCInsights cmdlet to view Microsoft 365 insights information. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SCInsights [-EndDate ] + [] +``` + +## DESCRIPTION +This cmdlet returns the following output: + +- Organization: The Microsoft 365 domain. +- Date: The date of the event in Coordinated Universal Time (UTC). +- InsightType +- InsightSubType: The value All or Archive. +- UsersCount: An integer count, or the size in megabytes for the InsightType value. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SCInsights +``` + +This example returns all insights data. + +### Example 2 +```powershell +Get-SCInsights -EndDate (Get-Date "3/3/2018 9:30 AM").ToUniversalTime() +``` + +This example return insights data for March 15, 2018. + +## PARAMETERS + +### -EndDate +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: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md new file mode 100644 index 0000000000..1330056090 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md @@ -0,0 +1,82 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SafeAttachmentPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SafeAttachmentPolicy cmdlet to view safe attachment policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SafeAttachmentPolicy [[-Identity] ] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SafeAttachmentPolicy +``` + +This example shows a summary list of all safe attachment policies. + +### Example 2 +```powershell +Get-SafeAttachmentPolicy -Identity Default | Format-List +``` + +This example shows detailed information about the safe attachment policy named Default. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: SafeAttachmentPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md new file mode 100644 index 0000000000..0dded56904 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md @@ -0,0 +1,99 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SafeAttachmentRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SafeAttachmentRule cmdlet to view safe attachment rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SafeAttachmentRule [[-Identity] ] + [-State ] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SafeAttachmentRule +``` + +This example returns a summary list of all safe attachment rules in your organization. + +### Example 2 +```powershell +Get-SafeAttachmentRule -Identity "Research Department Attachment Rule" | Format-List +``` + +This example returns detailed information about the safe attachment rule named Research Department Attachment Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -State +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md b/exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md new file mode 100644 index 0000000000..27c72f641a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md @@ -0,0 +1,177 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SafeLinksAggregateReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SafeLinksAggregateReport cmdlet to return general information about Safe Links results for the last 90 days. Yesterday is the most recent date that you can specify. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SafeLinksAggregateReport + [-Action ] + [-AppNameList ] + [-EndDate ] + [-StartDate ] + [-SummarizeBy ] + [] +``` + +## DESCRIPTION +**Note**: If you run Get-SafeLinksAggregateReport without specifying a date range, the command will return an unspecified error. + +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. + +For the reporting period you specify, the cmdlet returns the following information: + +- Action +- App +- MessageCount +- RecipientCount + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SafeLinksAggregateReport -StartDate 06-01-2020 -EndDate 06-10-2020 -SummarizeBy App -AppNameList "Email Client","Teams" +``` + +This example returns results summarized by Email Client and Teams results for the specified date range. + +## PARAMETERS + +### -Action +The Action parameter filters the results by action. Valid values are: + +- Allowed +- Blocked +- ClickedDuringScan +- ClickedEvenBlocked +- Scanning +- TenantAllowed +- TenantBlocked +- TenantBlockedAndClickedThrough + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppNameList +The AppNameList parameter filters the results by the app where the link was found. Valid values are: + +- Email Client +- OfficeDocs +- Teams + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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. + +Yesterday is the most recent date that you can specify. You can't specify a date that's older than 90 days. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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. + +Yesterday is the most recent date that you can specify. You can't specify a date that's older than 90 days. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SummarizeBy +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: + +- Action: Only the values specified by the Action parameter are returned. +- App: Only the values specified by the AppNameList parameter are returned. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md b/exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md new file mode 100644 index 0000000000..ef6379a4e6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md @@ -0,0 +1,245 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SafeLinksDetailReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SafeLinksDetailReport cmdlet to return detailed information about Safe Links results for the last 7 days. Yesterday is the most recent date that you can specify. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SafeLinksDetailReport + [-Action ] + [-AppNameList ] + [-Domain ] + [-EndDate ] + [-Page ] + [-PageSize ] + [-RecipientAddress ] + [-StartDate ] + [] +``` + +## DESCRIPTION +**Note**: If you run Get-SafeLinksDetailReport without specifying a date range, the command will return an unspecified error. + +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. + +This cmdlet returns the following information: + +- ClickTime +- NetworkMessageId +- ClientMessageId +- SenderAddress +- RecipientAddress +- Url +- UrlDomain +- Action +- AppName +- SourceId +- Organization +- DetectedBy (Safe Links in Microsoft Defender for Office 365) +- UrlType (currently empty) +- Flags (0: Allowed 1: Blocked 2: ClickedEvenBlocked 3: ClickedDuringScan) + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SafeLinksDetailReport -StartDate 06-07-2020 -EndDate 06-10-2020 -Action Allowed,Blocked -AppNameList "Email Client","Teams" -Domain google.com,teams.com -RecipientAddress faith@contoso.com,chris@contoso.com +``` + +This example returns filters the results by the following information: + +- Date range: June 7, 2020 to June 10, 2020 +- Action: Allowed and Blocked +- AppNameList: Email Client and Teams +- URL domain: google.com and teams.com +- Recipient email address: faith@contoso.com and chris@contoso.com + +## PARAMETERS + +### -Action +The Action parameter filters the results by action. Valid values are: + +- Allowed: URL was allowed due to a "Good" verdict. +- Blocked: URL was blocked due to a "Bad" verdict. +- ClickedDuringScan: User skipped verification of the URL and proceeded to the destination URL before Safe Links finished scanning. +- ClickedEvenBlocked: User was blocked at time of click from accessing URL. +- Scanning: URL is being scanned. +- TenantAllowed: URL allow entry in the Tenant Allow/Block List. +- TenantBlocked: URL block entry in the Tenant Allow/Block List. +- TenantBlockedAndClickedThrough: URL was blocked due to a block entry in the Tenant Allow/Block List, and the user clicked through the block page to access the URL. + +You can specify multiple values separated by commas. + +**Note**: Values for this parameter are case sensitive. No data returned for an action implies that the action didn't occur. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppNameList +The AppNameList parameter filters the results by the app where the link was found. Valid values are: + +- Email Client +- OfficeDocs +- Teams + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domain +The Domain parameter filters the results by the domain in the URL. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -EndDate +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. + +Yesterday is the most recent date that you can specify. You can't specify a date that's older than 7 days. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -StartDate +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. + +Yesterday is the most recent date that you can specify. You can't specify a date that's older than 7 days. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md new file mode 100644 index 0000000000..63a24625de --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md @@ -0,0 +1,82 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SafeLinksPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SafeLinksPolicy cmdlet to view Safe Links policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SafeLinksPolicy [[-Identity] ] + [] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SafeLinksPolicy | Format-Table Name,EnableSafe* +``` + +This example shows a summary list of all Safe Links policies. + +### Example 2 +```powershell +Get-SafeLinksPolicy -Identity "Contoso All" +``` + +This example shows detailed information about the Safe Links policy named Contoso All. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: SafeLinksPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SafeLinksRule.md b/exchange/exchange-ps/exchange/Get-SafeLinksRule.md new file mode 100644 index 0000000000..279ebc68cd --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SafeLinksRule.md @@ -0,0 +1,99 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SafeLinksRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SafeLinksRule cmdlet to view Safe Links rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SafeLinksRule [[-Identity] ] + [-State ] + [] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SafeLinksRule | Format-Table -Auto Name,State,Priority,SafeLinksPolicy,Comments +``` + +This example returns a summary list of all Safe Links rules in your organization. + +### Example 2 +```powershell +Get-SafeLinksRule -Identity "Research Department URL Rule" +``` + +This example returns detailed information about the Safe Links rule named Research Department URL Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -State +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-SearchDocumentFormat.md b/exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md similarity index 86% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-SearchDocumentFormat.md rename to exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md index c3c6ee0d13..562980e971 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-SearchDocumentFormat.md +++ b/exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/get-searchdocumentformat +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-SearchDocumentFormat @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-SearchDocumentFormat cmdlet to retrieve details of file formats supported by Exchange Search. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SearchDocumentFormat [[-Identity] ] [-Server ] [] +Get-SearchDocumentFormat [[-Identity] ] + [-Server ] + [] ``` ## DESCRIPTION Exchange Search includes built-in support for indexing many file formats. Output from the Get-SearchDocumentFormat cmdlet includes details about each supported file format, including whether content indexing is enabled for the file format, the format handler and the file extension (such as .docx). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,11 +71,8 @@ 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -97,12 +95,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md b/exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md new file mode 100644 index 0000000000..31c46f8403 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md @@ -0,0 +1,89 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SecOpsOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SecOpsOverridePolicy cmdlet to view SecOps mailbox override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SecOpsOverridePolicy [[-Identity] ] + [-DomainController ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SecOpsOverridePolicy +``` + +This example returns detailed information about the one and only SecOps mailbox override policy. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-SecurityPrincipal.md b/exchange/exchange-ps/exchange/Get-SecurityPrincipal.md similarity index 80% rename from exchange/exchange-ps/exchange/users-and-groups/Get-SecurityPrincipal.md rename to exchange/exchange-ps/exchange/Get-SecurityPrincipal.md index 1f6dbe441e..458dcbe1b3 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-SecurityPrincipal.md +++ b/exchange/exchange-ps/exchange/Get-SecurityPrincipal.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-securityprincipal -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" --- # Get-SecurityPrincipal @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-SecurityPrincipal cmdlet to return a list of security principals. Security principals are entities, such as users or security groups, which can be assigned permissions and user rights. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -36,7 +35,7 @@ Get-SecurityPrincipal [[-Identity] ] ## DESCRIPTION The Get-SecurityPrincipal cmdlet is used by the Exchange admin center to populate fields that display recipient information. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,6 +69,22 @@ This example retrieves well-known security principals and displays only the Name ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DomainController This parameter is available only in on-premises Exchange. @@ -89,25 +104,22 @@ Accept wildcard characters: False ``` ### -Filter -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. +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'"`. -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -116,22 +128,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IncludeDomainLocalFrom This parameter is available only in on-premises Exchange. @@ -156,18 +152,15 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml Type: ExtendedOrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -183,7 +176,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -199,7 +192,7 @@ The RoleGroupAssignable switch filters security principals by returning only obj Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -212,15 +205,10 @@ Accept wildcard characters: False The Types parameter filters the results by object type. Valid values are: - Computer - - GlobalSecurityGroup - - Group - - UniversalSecurityGroup - - User - - WellknownSecurityPrincipal You can specify multiple values separated by commas. @@ -229,7 +217,7 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -243,12 +231,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-SendConnector.md b/exchange/exchange-ps/exchange/Get-SendConnector.md similarity index 86% rename from exchange/exchange-ps/exchange/mail-flow/Get-SendConnector.md rename to exchange/exchange-ps/exchange/Get-SendConnector.md index 921ebc7d6e..b285afa86f 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-SendConnector.md +++ b/exchange/exchange-ps/exchange/Get-SendConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-sendconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SendConnector @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-SendConnector cmdlet to view the settings for a Send connector. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SendConnector [[-Identity] ] [-DomainController ] [] +Get-SendConnector [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -78,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderFilterConfig.md b/exchange/exchange-ps/exchange/Get-SenderFilterConfig.md similarity index 85% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderFilterConfig.md rename to exchange/exchange-ps/exchange/Get-SenderFilterConfig.md index 8b365a37ef..b89a8e9412 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderFilterConfig.md +++ b/exchange/exchange-ps/exchange/Get-SenderFilterConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-senderfilterconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SenderFilterConfig @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-SenderFilterConfig cmdlet to view the Sender Filter configuration information for the Exchange server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SenderFilterConfig [[-Identity] ] [-DomainController ] [] +Get-SenderFilterConfig [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -39,37 +40,37 @@ This example returns detailed information about the Sender Filter configuration ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +This parameter is reserved for internal Microsoft use. ```yaml -Type: Fqdn +Type: OrganizationIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -This parameter is reserved for internal Microsoft use. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: OrganizationIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -78,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderIdConfig.md b/exchange/exchange-ps/exchange/Get-SenderIdConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderIdConfig.md rename to exchange/exchange-ps/exchange/Get-SenderIdConfig.md index b3cdbd8dcd..1e0dad4cd1 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderIdConfig.md +++ b/exchange/exchange-ps/exchange/Get-SenderIdConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-senderidconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SenderIdConfig @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-SenderIdConfig cmdlet to view the Sender ID configuration information for the Exchange server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SenderIdConfig [-DomainController ] [] +Get-SenderIdConfig [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,12 +62,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderReputationConfig.md b/exchange/exchange-ps/exchange/Get-SenderReputationConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderReputationConfig.md rename to exchange/exchange-ps/exchange/Get-SenderReputationConfig.md index 0565a99b4f..83288be5e1 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-SenderReputationConfig.md +++ b/exchange/exchange-ps/exchange/Get-SenderReputationConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-senderreputationconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SenderReputationConfig @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-SenderReputationConfig cmdlet to view the configuration information for sender reputation on the computer on which the command is run. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SenderReputationConfig [-DomainController ] [] +Get-SenderReputationConfig [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,12 +62,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerComponentState.md b/exchange/exchange-ps/exchange/Get-ServerComponentState.md similarity index 86% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerComponentState.md rename to exchange/exchange-ps/exchange/Get-ServerComponentState.md index 4d43c8a4a2..2008d37985 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerComponentState.md +++ b/exchange/exchange-ps/exchange/Get-ServerComponentState.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-servercomponentstate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ServerComponentState @@ -17,17 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ServerComponentState cmdlet to retrieve configuration settings for Microsoft Exchange components and endpoints. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ServerComponentState [-Identity] [-Component ] [-DomainController ] +Get-ServerComponentState [-Identity] + [-Component ] + [-DomainController ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,9 +52,7 @@ This example returns detailed information for the component state of the Unified The Identity parameter specifies the Exchange server where you want to view the configuration settings. You can use the following values: - Name - - Distinguished name (DN) - - FQDN ```yaml @@ -70,7 +69,7 @@ Accept wildcard characters: False ``` ### -Component -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 \. +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 @@ -108,12 +107,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerHealth.md b/exchange/exchange-ps/exchange/Get-ServerHealth.md similarity index 86% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerHealth.md rename to exchange/exchange-ps/exchange/Get-ServerHealth.md index 186a62ed39..329cfe409b 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerHealth.md +++ b/exchange/exchange-ps/exchange/Get-ServerHealth.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-serverhealth +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ServerHealth @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ServerHealth cmdlet to return health information related to the server you specify. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,22 +28,17 @@ Get-ServerHealth [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). -The cmdlet returns health values that you can use to determine the state of the server. See [Server health and performance in Exchange Server](https://docs.microsoft.com/Exchange/server-health/server-health) for related information. +The cmdlet returns health values that you can use to determine the state of the server. See [Server health and performance in Exchange Server](https://learn.microsoft.com/Exchange/server-health/server-health) for related information. The cmdlet also returns an alert value that provides the specific state of your server. The following values may be returned: - Degraded - - Unhealthy - - Repairing - - Disabled - - Unavailable - - UnInitialized ## EXAMPLES @@ -62,11 +56,8 @@ This example returns the server health for server Server01. 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -83,7 +74,7 @@ Accept wildcard characters: False ``` ### -HaImpactingOnly -The HaImpactingOnly switch specifies whether the cmdlet must roll up only the monitors that have HaImpacting set to True. +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 @@ -119,12 +110,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerMonitoringOverride.md b/exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md similarity index 83% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerMonitoringOverride.md rename to exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md index f10e548a96..2986dafdb9 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-servermonitoringoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ServerMonitoringOverride @@ -17,16 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ServerMonitoringOverride cmdlet to return all overrides created on the specified server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-ServerMonitoringOverride -Server [] +Get-ServerMonitoringOverride -Server + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,11 +43,8 @@ This example retrieves all monitoring overrides for the Exch01 server. 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use this parameter to configure other Edge Transport servers remotely. @@ -70,12 +67,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md b/exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md new file mode 100644 index 0000000000..842dc2fa11 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md @@ -0,0 +1,90 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ServiceDeliveryReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ServiceDeliveryReport cmdlet to view information about the message delivery path for a specified recipient. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ServiceDeliveryReport [-ProbeTag ] + [-Recipient ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ServiceDeliveryReport -Recipient chris@contoso.com +``` + +This example shows the delivery path information for the recipient chris@contoso.com. + +## PARAMETERS + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Recipient +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-ServicePrincipal.md b/exchange/exchange-ps/exchange/Get-ServicePrincipal.md new file mode 100644 index 0000000000..ee06d9d363 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-ServicePrincipal.md @@ -0,0 +1,101 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-ServicePrincipal + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-ServicePrincipal cmdlet to view information about service principals in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-ServicePrincipal [[-Identity] ] + [-Organization ] + [] +``` + +## DESCRIPTION +Service principals exist in Microsoft Entra ID to define what apps can do, who can access the apps, and what resources the apps can access. In Exchange Online, service principals are references to the service principals in Microsoft Entra ID. To assign Exchange Online role-based access control (RBAC) roles to service principals in Microsoft Entra ID, you use the service principal references in Exchange Online. The **\*-ServicePrincipal** cmdlets in Exchange Online PowerShell let you view, create, and remove these service principal references. + +For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ServicePrincipal +``` + +This example returns a summary list of all service principals within an organization. + +### Example 2 +```powershell +Get-ServicePrincipal -Identity ca73fffa-cedb-4b84-860f-d7fb8aa8a6c1 | Format-List +``` + +This example returns detailed information about the service principal with the ObjectId value ca73fffa-cedb-4b84-860f-d7fb8aa8a6c1. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- AppId +- ObjectId + +```yaml +Type: ServicePrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Organization +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-SettingOverride.md b/exchange/exchange-ps/exchange/Get-SettingOverride.md similarity index 86% rename from exchange/exchange-ps/exchange/organization/Get-SettingOverride.md rename to exchange/exchange-ps/exchange/Get-SettingOverride.md index 78f4a6dc79..dec2d72019 100644 --- a/exchange/exchange-ps/exchange/organization/Get-SettingOverride.md +++ b/exchange/exchange-ps/exchange/Get-SettingOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-settingoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SettingOverride @@ -19,18 +18,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-SettingOverride cmdlet to view existing setting overrides that store Exchange customizations in Active Directory instead of in text files on the server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SettingOverride [[-Identity] ] [-DomainController ] [] +Get-SettingOverride [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and are lost when you install the next Exchange CU. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,41 +51,39 @@ This example displays a detailed information for the setting override object nam ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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 +- Distinguished name (DN) +- GUID ```yaml -Type: Fqdn +Type: SettingOverrideIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: SettingOverrideIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -93,12 +92,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SharingPolicy.md b/exchange/exchange-ps/exchange/Get-SharingPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SharingPolicy.md rename to exchange/exchange-ps/exchange/Get-SharingPolicy.md index ae59bfbdd0..a9e5d5b87f 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SharingPolicy.md +++ b/exchange/exchange-ps/exchange/Get-SharingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-sharingpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-SharingPolicy @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-SharingPolicy cmdlet to view existing sharing policies that control how users inside your organization can share free/busy and contact information with users outside your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SharingPolicy [[-Identity] ] [-DomainController ] [] +Get-SharingPolicy [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION Users can only share free/busy and contact information after federation has been configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing settings for the mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,52 +42,49 @@ This example retrieves the default information for the sharing policy FourthCoff ### Example 2 ```powershell -Get-SharingPolicy Fabrikam | Format List +Get-SharingPolicy Fabrikam | Format-List ``` This example retrieves the full information for the sharing policy Fabrikam. ## PARAMETERS -### -DomainController -This parameter is available only in on-premises Exchange. +### -Identity +The Identity parameter specifies the sharing policy that you want to view. You can use one of the following values: -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +- ADObjectID +- Distinguished name (DN) +- Legacy DN +- GUID ```yaml -Type: Fqdn +Type: SharingPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the sharing policy that you want to view. You can use one of the following values: - -- ADObjectID - -- Distinguished name (DN) - -- Legacy DN +### -DomainController +This parameter is available only in on-premises Exchange. -- GUID +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: SharingPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -95,12 +93,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailbox.md b/exchange/exchange-ps/exchange/Get-SiteMailbox.md similarity index 85% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailbox.md rename to exchange/exchange-ps/exchange/Get-SiteMailbox.md index 660b69ca32..a35a4f6e0c 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailbox.md +++ b/exchange/exchange-ps/exchange/Get-SiteMailbox.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-sitemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SiteMailbox ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Get-SiteMailbox cmdlet to view information about site mailboxes. This cmdlet is primarily used by Microsoft SharePoint and Exchange to display information to users in the user interface. However, you may find it helpful for discovering information such as the site mailbox's owners, members, and lifecycle status. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,13 +29,14 @@ Get-SiteMailbox [[-Identity] ] [-DeletedSiteMailbox] [-DomainController ] [-ReadFromDomainController] - [-ResultSize ] [] + [-ResultSize ] + [] ``` ## DESCRIPTION If you aren't a member or owner of the site mailbox that you want to view the diagnostics information for, you must use the BypassOwnerCheck parameter when running this cmdlet. If you aren't a member or owner of the site mailbox and you run this cmdlet without using the BypassOwnerCheck parameter, the command fails with an "object not found" error. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,17 +63,36 @@ This example queries for site mailboxes that are marked for deletion and removes ## PARAMETERS +### -Identity +The Identity parameter specifies the identity of the site mailbox. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -90,7 +111,7 @@ Accept wildcard characters: False ### -BypassOwnerCheck 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 run the command without this parameter, and you aren't a member or owner of the site mailbox, then the command will fail. +If you don't use this switch, and you aren't a member or owner of the site mailbox, the command will fail. ```yaml Type: SwitchParameter @@ -139,36 +160,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identity of the site mailbox. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -ReadFromDomainController -The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -206,12 +201,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailboxDiagnostics.md b/exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailboxDiagnostics.md rename to exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md index 72a03ab4f9..a79fefc2f8 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailboxDiagnostics.md +++ b/exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-sitemailboxdiagnostics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SiteMailboxDiagnostics ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Get-SiteMailboxDiagnostics cmdlet to view important event-related data for each site mailbox. This information can be used to troubleshoot site mailbox issues. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,13 +27,14 @@ Get-SiteMailboxDiagnostics [-Identity] [-BypassOwnerCheck] [-Confirm] [-SendMeEmail] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION If you aren't a member or owner of the site mailbox that you want to view the diagnostics information for, you must use the BypassOwnerCheck parameter when running this cmdlet. If you aren't a member or owner of the site mailbox and you run this cmdlet without using the BypassOwnerCheck parameter, the command fails with an "object not found" error. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,15 +58,10 @@ This example returns the event information for the Marketing Events 2015 site ma 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -83,7 +80,7 @@ Accept wildcard characters: False ### -BypassOwnerCheck 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 run the command without this parameter and you aren't a member or owner of the site mailbox, then the command will fail. +If you don't use this switch and you aren't a member or owner of the site mailbox, the command will fail. ```yaml Type: SwitchParameter @@ -101,8 +98,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -155,12 +151,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md similarity index 84% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md index e942cd3c08..1e107e4c93 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md @@ -1,35 +1,37 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/get-sitemailboxprovisioningpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SiteMailboxProvisioningPolicy ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Get-SiteMailboxProvisioningPolicy cmdlet to view site mailbox provisioning policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SiteMailboxProvisioningPolicy [[-Identity] ] [-DomainController ] +Get-SiteMailboxProvisioningPolicy [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION Site mailboxes allow access to both Microsoft SharePoint documents and Exchange email using the same client interface. Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,41 +51,39 @@ This example returns detailed information about the site mailbox provisioning po ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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 +- Distinguished name (DN) +- GUID ```yaml -Type: Fqdn +Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: MailboxPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -92,12 +92,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-SmimeConfig.md b/exchange/exchange-ps/exchange/Get-SmimeConfig.md similarity index 82% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Get-SmimeConfig.md rename to exchange/exchange-ps/exchange/Get-SmimeConfig.md index 6a4bdf5b3b..94acefe7bf 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-SmimeConfig.md +++ b/exchange/exchange-ps/exchange/Get-SmimeConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-smimeconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-SmimeConfig @@ -17,16 +16,17 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-SmimeConfig cmdlet to view the S/MIME configuration for Outlook on the web (formerly known as Outlook Web App). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-SmimeConfig [[-Identity] ] [] +Get-SmimeConfig [[-Identity] ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,12 +60,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md b/exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md new file mode 100644 index 0000000000..2bc72a8f55 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md @@ -0,0 +1,68 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SmtpDaneInboundStatus + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SmtpDaneInboundStatus cmdlet to view information about SMTP DNS-based Authentication of Named Entities (DANE) for inbound mail to accepted domains in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SmtpDaneInboundStatus [-DomainName] [] +``` + +## DESCRIPTION +For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SmtpDaneInboundStatus -DomainName contoso.com +``` + +This example checks the DANE status for the accepted domain contoso.com. + +## PARAMETERS + +### -DomainName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md b/exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md new file mode 100644 index 0000000000..01335195b4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md @@ -0,0 +1,84 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SpoofIntelligenceInsight + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SpoofIntelligenceInsight cmdlet to view spoofed senders that were allowed or blocked by spoof intelligence during the last 30 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SpoofIntelligenceInsight [[-Identity] ] [] +``` + +## DESCRIPTION +The Get-SpoofIntelligenceInsight cmdlet returns the following information: + +- SpoofedUser: The sending email address if the domain is one of your organization's domains, or the sending domain if the domain is external. +- SendingInfrastructure: The true sending domain that's found in the DNS record of the source email server. If no domain is found, the source email server's IP address is shown. +- MessageCount: The number of messages. +- LastSeen: The date when the sending email address or domain was last seen by Microsoft 365. +- SpoofType: Indicates whether the domain is internal to your organization or external. +- Action: The two possible values are Allow (messages that contain any spoofed sender email addresses in your organization are allowed from the source email server), and Block (messages that contain any spoofed sender email addresses in your organization are not allowed from the source email server). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SpoofIntelligenceInsight +``` + +This example returns the list of senders that appear to be sending spoofed email to your organization. + +### Example 2 +```powershell +$file = "C:\My Documents\Spoof Insights.csv" + +Get-SpoofIntelligenceInsight | Export-Csv $file +``` + +This example exports the same list of spoofed senders to a CSV file. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SpoofMailReport.md b/exchange/exchange-ps/exchange/Get-SpoofMailReport.md new file mode 100644 index 0000000000..312ec706dc --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SpoofMailReport.md @@ -0,0 +1,212 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SpoofMailReport + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-SpoofMailReport cmdlet to view information about spoofed senders in your cloud-based organization for the past 90 days. Spoofing is where the sender of the inbound message is different than the actual source of the message (for example, the sender is lila@contoso.com, but the message was sent from the email infrastructure of fabrikam.com). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SpoofMailReport [-Action ] + [-Direction ] + [-EndDate ] + [-EventType ] + [-Page ] + [-PageSize ] + [-ProbeTag ] + [-StartDate ] + [] +``` + +## DESCRIPTION +The Get-SpoofMailReport cmdlet returns the following information: + +- Date: Date the message was sent. +- Event Type: Typically, this value is SpoofMail. +- Direction: This value is Inbound. +- Domain: The sender domain. This corresponds to one of your organization's accepted domains. +- Spoofed User: The sending email address if the domain is one of your organization's domains, or the sending domain if the domain is external. +- True Sender: The organizational domain of the PTR record, or pointer record, of the sending IP address, also known as the reverse DNS address. If the sending IP address does not have a PTR record, this field will be blank and the Sender IP column will be filled in. Both columns will not be filled in at the same time. +- Sending Infrastructure: The true sending domain that's found in the DNS record of the source email server. If no domain is found, the source email server's IP address is shown. +- Count: The number of spoofed messages that were sent to your organization from the source messaging server during the specified time period. +- Spoof Type: The relationship between the sender and recipient domain of the spoof mail. If both belong to same domain (including subdomains) or domain owned by the same organization, then Spoof Type is intra-org or Internal. If both belong to different domains, then Spoof Type is cross-org or External. +- Source: Typically, this value is "Spoof intelligence". +- Result: CompAuthResult +- Result Code: CompAuthReason +- SPF +- DKIM +- DMARC + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SpoofMailReport -StartDate 03/01/2020 -EndDate 03/11/2020 +``` + +This example shows the insider spoofing detections in your organization during the month of March 2016. + +## PARAMETERS + +### -Action +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. + +Common values for this report are GoodMail and CaughtAsSpam. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Direction +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProbeTag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-StoreUsageStatistics.md b/exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md similarity index 85% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-StoreUsageStatistics.md rename to exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md index 5e00cafb5f..4a09b7af84 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Get-StoreUsageStatistics.md +++ b/exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/get-storeusagestatistics +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-StoreUsageStatistics @@ -17,35 +16,41 @@ This cmdlet is available only in on-premises Exchange. Use the Get-StoreUsageStatistics cmdlet to aid in diagnosing performance issues with your servers or databases. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Database ``` -Get-StoreUsageStatistics -Database [-CopyOnServer ] +Get-StoreUsageStatistics -Database + [-CopyOnServer ] [-DomainController ] - [-Filter ] [] + [-Filter ] + [] ``` ### Identity ``` -Get-StoreUsageStatistics [-Identity] [-CopyOnServer ] +Get-StoreUsageStatistics [-Identity] + [-CopyOnServer ] [-DomainController ] - [-Filter ] [] + [-Filter ] + [] ``` ### Server ``` -Get-StoreUsageStatistics -Server [-IncludePassive] +Get-StoreUsageStatistics -Server + [-IncludePassive] [-DomainController ] - [-Filter ] [] + [-Filter ] + [] ``` ## DESCRIPTION The Microsoft Exchange Information Store collects per-user information on latency, input/output (I/O), page counts, processor usage, and TimeInServer. The TimeInServer metric represents the total time that synchronous and asynchronous requests spend in the Microsoft Exchange Information Store for a user's mailbox. You can retrieve this resource information in the Microsoft Exchange Information Store for the 25 highest usage accounts on a specified database. Usage of a mailbox is defined as the amount of server time spent in performing operations for that mailbox. The cmdlet reports the top 25 users for every one-minute period for the last 10 minutes (250 objects per ten-minute interval). The resource usage is an indicator of the load that different users are placing on the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,59 +77,51 @@ This example retrieves store usage statistics for database DB1 and sorts the out ## PARAMETERS -### -Database -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 +### -Identity +The Identity parameter specifies the mailbox to get usage statistics from. You can use one of the following values to identify the mailbox: +- GUID - Distinguished name (DN) +- Domain\\Account +- User principal name (UPN) +- Legacy Exchange DN +- SMTP address +- Alias -- GUID +The command returns results for the mailbox only if it's one of the top 25 users of store resources. -You can't use this parameter with the Identity or Server parameters. +You can't use this parameter with the Database or Server parameters. ```yaml -Type: DatabaseIdParameter -Parameter Sets: Database +Type: GeneralMailboxIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the mailbox to get usage statistics from. You can use one of the following values to identify the mailbox: - -- GUID +### -Database +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 - Distinguished name (DN) +- GUID -- Domain\\Account - -- User principal name (UPN) - -- Legacy Exchange DN - -- SMTP address - -- Alias - -The command returns results for the mailbox only if it's one of the top 25 users of store resources. - -You can't use this parameter with the Database or Server parameters. +You can't use this parameter with the Identity or Server parameters. ```yaml -Type: GeneralMailboxIdParameter -Parameter Sets: Identity +Type: DatabaseIdParameter +Parameter Sets: Database Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False @@ -134,7 +131,6 @@ Accept wildcard characters: False 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) - - NetBIOS name You can't use this parameter with the Database or Identity parameters. @@ -156,9 +152,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You use this parameter with the Server or Identity parameters. @@ -193,19 +187,16 @@ Accept wildcard characters: False ``` ### -Filter -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. +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. - Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -223,7 +214,7 @@ Accept wildcard characters: False ### -IncludePassive 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. -To only include statistics from active copies of mailbox databases on the specified Mailbox server, don't use this switch. +If you don't use this switch, only statistics from active copies of mailbox databases are included in the results. ```yaml Type: SwitchParameter @@ -243,12 +234,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewActivity.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md similarity index 77% rename from exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewActivity.md rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md index 7dd198cbed..420045a251 100644 --- a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewActivity.md +++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md @@ -1,13 +1,12 @@ ---- +--- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-supervisoryreviewactivity -applicable: Exchange Online, Office 365 Security & Compliance Center +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Get-SupervisoryReviewActivity @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Get-SupervisoryReviewActivity cmdlet to view all activities performed by a reviewer for a specific supervision policy. This information may be useful if reviewer activities are required in regulatory compliance audits or in litigation. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,14 +26,13 @@ Get-SupervisoryReviewActivity -EndDate -PolicyId -StartDat ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-SupervisoryReviewActivity -PolicyId $policyId -StartDate $startDate -EndDate $endDate | Sort-Object Timestamp -Descending | fl -PolicyId,ItemSubject,ActivityId,Timestamp,ActionType,ActionAppliedBy,ItemStatusAfterAction +Get-SupervisoryReviewActivity -PolicyId $policyId -StartDate $startDate -EndDate $endDate | Sort-Object Timestamp -Descending | Format-List PolicyId,ItemSubject,ActivityId,Timestamp,ActionType,ActionAppliedBy,ItemStatusAfterAction ``` This example returns all the supervisory review activities for specified supervision policy. @@ -54,13 +49,13 @@ This example exports all the supervisory review activities for a policy to a .cs ### -EndDate 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". +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". ```yaml Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Security & Compliance Required: True Position: Named @@ -70,13 +65,13 @@ Accept wildcard characters: False ``` ### -PolicyId -The PolicyId parameter specifies +{{ Fill PolicyId Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Security & Compliance Required: True Position: Named @@ -88,13 +83,13 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Security & Compliance Required: True Position: Named @@ -108,12 +103,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md new file mode 100644 index 0000000000..3a432c1505 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md @@ -0,0 +1,122 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SupervisoryReviewOverallProgressReport + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-SupervisoryReviewOverallProgressReport cmdlet to view the total number of supervised communications classified as Pending, Resolved, Compliant, Non-compliant, and Questionable. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SupervisoryReviewOverallProgressReport [-EndDate ] + [-Page ] + [-PageSize ] + [-StartDate ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SupervisoryReviewOverallProgressReport | ft Pending, Resolved, Compliant, Noncompliant, Questionable +``` + +This example returns a list of the total number of supervised communications classified by status. + +## PARAMETERS + +### -EndDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md new file mode 100644 index 0000000000..d3982ce31b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md @@ -0,0 +1,157 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SupervisoryReviewPolicyReport + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-SupervisoryReviewPolicyReport cmdlet to view supervisory review policy events in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SupervisoryReviewPolicyReport [-EndDate ] + [-Page ] + [-PageSize ] + [-Policies ] + [-StartDate ] + [] +``` + +## DESCRIPTION +For the reporting period you specify, the Get-SupervisoryReviewPolicyReport cmdlet returns the following information: + +- Organization +- Date +- Policy +- Message Type +- Tag Type: Messages that are eligible for evaluation by the policy are `InPurview`. Messages that match the conditions of the policy are `HitPolicy`. Classifications that are manually assigned to messages by the designated reviewers using the Supervision add-in for Outlook web app are `Compliant`, `Non-compliant`, `Questionable`, and `Resolved`. Messages that match the conditions of a policy but haven't been reviewed by a designated reviewer are `Not-Reviewed`. Messages that match the conditions of a policy and have been reviewed by a designated reviewer are `New-Reviewed`. +- Item Count + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SupervisoryReviewPolicyReport -StartDate 03/01/2018 -EndDate 03/31/2018 +``` + +This example returns the supervisory review policy events for the month of March, 2018. + +### Example 2 +```powershell +Get-SupervisoryReviewPolicyReport -Policies "EU Brokers Policy" +``` + +This example returns the supervisory review policy events for the policy named EU Brokers Policy. + +## PARAMETERS + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policies +The Policies parameter filters the results by the supervisory review policy. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md new file mode 100644 index 0000000000..cc356b57a5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md @@ -0,0 +1,78 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SupervisoryReviewPolicyV2 + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-SupervisoryReviewPolicyV2 cmdlet to view supervisory review policies in the Microsoft Purview compliance portal. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SupervisoryReviewPolicyV2 [[-Identity] ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SupervisoryReviewPolicyV2 +``` + +This example returns a summary list of all supervisory review policies. + +### Example 2 +```powershell +Get-SupervisoryReviewPolicyV2 -Identity "EU Brokers Policy" | Format-List +``` + +This example returns detailed information for the supervisory review policy named EU Brokers Policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md new file mode 100644 index 0000000000..5e1a033aa5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md @@ -0,0 +1,167 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SupervisoryReviewReport + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-SupervisoryReviewReport cmdlet to view supervisory review events in the Microsoft Purview compliance portal for the last 90 days. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SupervisoryReviewReport [-EndDate ] + [-Page ] + [-PageSize ] + [-Policies ] + [-Reviewers ] + [-StartDate ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SupervisoryReviewReport -StartDate 03/01/2018 -EndDate 03/31/2018 +``` + +This example returns the supervisory review events for the month of March, 2018. + +### Example 2 +```powershell +Get-SupervisoryReviewPolicyReport -Policies "US Brokers Policy" +``` + +This example returns the supervisory review events for the policy named US Brokers Policy. + +## PARAMETERS + +### -EndDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policies +The Policies parameter filters the results by the supervisory review policy. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Reviewers +The Reviewers parameter filters the results by the reviewers of the supervisory review policy. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md new file mode 100644 index 0000000000..1a7f812f23 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md @@ -0,0 +1,123 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SupervisoryReviewRule + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-SupervisoryReviewRule cmdlet to modify supervisory review rules in the Microsoft Purview compliance portal. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SupervisoryReviewRule [[-Identity] ] + [-IncludeRuleXml] + [-Policy ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SupervisoryReviewRule +``` + +This example returns a summary list of all supervisory review rules. + +### Example 2 +```powershell +Get-SupervisoryReviewRule -Identity "EU Brokers Rule" | Format-List +``` + +This example returns detailed information for the supervisory review rule named EU Brokers Rule. + +### Example 3 +```powershell +Get-SupervisoryReviewRule -Policy "EU Brokers Policy" +``` + +This example returns the rule that assigned to the supervisory review policy named EU Brokers Policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -IncludeRuleXml +{{ Fill IncludeRuleXml Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md new file mode 100644 index 0000000000..f630b5e84b --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md @@ -0,0 +1,121 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SupervisoryReviewTopCasesReport + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-SupervisoryReviewTopCasesReport cmdlet to view the current status of the top supervision policies configured in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SupervisoryReviewTopCasesReport [-EndDate ] + [-Page ] + [-PageSize ] + [-StartDate ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SupervisoryReviewTopCasesReport | Sort-Object Policy | Format-Table Policy,Pending,Total,Date +``` +This example returns detailed information on supervisory policies, including the policy name, the total number of communications under review and pending, and the date of the report. + +## PARAMETERS + +### -EndDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Page +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PageSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SweepRule.md b/exchange/exchange-ps/exchange/Get-SweepRule.md new file mode 100644 index 0000000000..ceab5bc86d --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-SweepRule.md @@ -0,0 +1,203 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-SweepRule + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-SweepRule cmdlet to view Sweep rules in mailboxes. Sweep rules run at regular intervals to help keep your Inbox clean. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-SweepRule [[-Identity] ] + [-BypassScopeCheck] + [-DomainController ] + [-Mailbox ] + [-Provider ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-SweepRule +``` + +This example returns a summary list of all Sweep rules. + +### Example 2 +```powershell +Get-SweepRule -Mailbox julia@contoso.com +``` + +This example returns a summary list of all Sweep rules in the specified mailbox. + +### Example 3 +```powershell +Get-SweepRule -Identity "x2hlsdpGmUifjFgxxGIOJw==" +``` + +This example returns detailed information for the Sweep rule with the specified RuleId property value. + +## PARAMETERS + +### -Identity +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==). +- Exchange Online: `MailboxAlias\RuleID` (for example, `rzaher\2hlsdpGmUifjFgxxGIOJw==`). +- On-premises Exchange: `MailboxCanonicalName\RuleID` (for example, `contoso.com/Users/Rick Zaher\x2hlsdpGmUifjFgxxGIOJw==`). + +```yaml +Type: SweepRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BypassScopeCheck +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mailbox +The Mailbox parameter filters the results by the specified mailbox. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Provider +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipCount +This parameter is available only in the cloud-based service. + +{{ Fill SkipCount Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-SystemMessage.md b/exchange/exchange-ps/exchange/Get-SystemMessage.md similarity index 83% rename from exchange/exchange-ps/exchange/mail-flow/Get-SystemMessage.md rename to exchange/exchange-ps/exchange/Get-SystemMessage.md index 873cf8d55b..ba18ccc28c 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-SystemMessage.md +++ b/exchange/exchange-ps/exchange/Get-SystemMessage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-systemmessage +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-SystemMessage @@ -17,24 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Get-SystemMessage cmdlet to view default or custom system messages. System messages are delivery status notifications (also known as DSNs, non-delivery reports, NDRs or bounce messages) and quota messages. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Get-SystemMessage [[-Identity] ] [-DomainController ] [] +Get-SystemMessage [[-Identity] ] + [-DomainController ] + [] ``` ### Original ``` -Get-SystemMessage [-Original] [-DomainController ] [] +Get-SystemMessage [-Original] + [-DomainController ] + [] ``` ## DESCRIPTION NDRs are issued to the senders of email messages that haven't reached their intended recipients. Quota messages are issued to users whose mailboxes or public folders have reached the specific warning, prohibit send, or prohibit receive quotas. Custom NDRs and quota messages replace the default messages that are included with Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,93 +73,58 @@ You should output the list to a file, because the list is very long, and you'll ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity -TheIdentity parameter specifies the custom system message that you want to view. You can use any value that uniquely identifies the system message. For example: +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 - - Distinguished name (DN) - - GUID You can't use this parameter with the Original switch. The identity value of a system message uses one of these formats: -- System messages for enhanced status codes:\\\\\\\. For example, En\\Internal\\5.1.2 or Ja\\External\\5.1.2. - -- System messages for quotas:\\\\. For example, En\\ProhibitSendReceiveMailBox. +- System messages for enhanced status codes: `Language\\DSNCode`. For example, `En\Internal\5.1.2` or `Ja\External\5.1.2`. +- System messages for quotas: `Language\QuotaMessageType`. For example, `En\ProhibitSendReceiveMailbox`. -\: For the list of supported language codes, see [Supported languages for NDRs](https://docs.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs). +\: 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). -\: Valid values are 4.x.y or 5.x.y where x and y are one to three digit numbers. +\: Valid values are 4.x.y or 5.x.y where x and y are one to three digit numbers. To see the enhanced system codes that are currently used by custom system messages, run the command `Get-SystemMessage`. To generate a list of default enhanced status codes that are used by Exchange, run this command: `Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language,Text | ConvertTo-Html | Set-Content -Path "C:\My Documents\Default DSNs.html"`. \: Valid value are: Mailbox size quotas: -- ProhibitSendReceiveMailBox: A mailbox exceeds its ProhibitSendReceiveQuota limit. - +- ProhibitSendReceiveMailbox: A mailbox exceeds its ProhibitSendReceiveQuota limit. - ProhibitSendMailbox: A mailbox exceeds its ProhibitSendQuota limit. - - WarningMailbox: A mailbox exceeds its IssueWarningQuota limit when it has a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. - - WarningMailboxUnlimitedSize: A mailbox exceeds its IssueWarningQuota limit when it doesn't have a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. Public folder size quotas: - ProhibitPostPublicFolder: A public folder exceeds its ProhibitPostQuota limit. - - WarningPublicFolder: A public folder exceeds its IssueWarningQuota limit when it has a ProhibitPostQuota limit configured. - - WarningPublicFolderUnlimitedSize: A public folder exceeds its IssueWarningQuota limit when it doesn't have a ProhibitPostQuota limit configured. Maximum number of messages in a mailbox folder: - ProhibitReceiveMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountReceiveQuota limit. - - WarningMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it has a MailboxMessagesPerFolderCountReceiveQuota limit configured. - - WarningMailboxMessagesPerFolderUnlimitedCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it doesn't have a MailboxMessagesPerFolderCountReceiveQuota limit configured. Maximum number of subfolders in a mailbox folder: - ProhibitReceiveFolderHierarchyChildrenCountCount: A mailbox exceeds its FolderHierarchyChildrenCountReceiveQuota limit. - - WarningFolderHierarchyChildrenCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it has a FolderHierarchyChildrenCountReceiveQuota limit configured. - - WarningFolderHierarchyChildrenUnlimitedCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it doesn't have a FolderHierarchyChildrenCountReceiveQuota limit configured. - - ProhibitReceiveFoldersCount: A mailbox exceeds its FoldersCountReceiveQuota limit. - - WarningFoldersCount: A mailbox exceeds its FoldersCountWarningQuota limit when it has a FoldersCountReceiveQuota limit configured. - - WarningFoldersCountUnlimited A mailbox exceeds its FoldersCountWarningQuota limit when it doesn't have a FoldersCountReceiveQuota limit configured. Maximum number of levels (depth) in a mailbox folder: - ProhibitReceiveFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit. - - WarningFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it has a FolderHierarchyDepthReceiveQuota limit configured. - - WarningFolderHierarchyDepthUnlimited: : A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it doesn't have a FolderHierarchyDepthReceiveQuota limit configured. ```yaml @@ -172,6 +140,24 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Original 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. @@ -195,12 +181,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md new file mode 100644 index 0000000000..4f520c8a57 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md @@ -0,0 +1,67 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-TeamsProtectionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-TeamsProtectionPolicy cmdlet to view Microsoft Teams protection policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-TeamsProtectionPolicy [[-Identity] ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-TeamsProtectionPolicy +``` + +This example shows detailed information about the Teams protection policy in the organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md new file mode 100644 index 0000000000..5aba335ec7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md @@ -0,0 +1,87 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-TeamsProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-TeamsProtectionPolicyRule cmdlet to view Microsoft Teams protection policy rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-TeamsProtectionPolicyRule [[-Identity] ] + [-State ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-TeamsProtectionPolicyRule +``` + +This example shows detailed information about the Teams protection policy in the organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -State +The State parameter filters the results by the State value of the rule. Valid values are: + +- Enabled +- Disabled + +```yaml +Type: RuleState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md new file mode 100644 index 0000000000..f2a8862ef7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md @@ -0,0 +1,232 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-TenantAllowBlockListItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-TenantAllowBlockListItems cmdlet to view entries in the Tenant Allow/Block List in the Microsoft Defender portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Expiration (Default) +``` +Get-TenantAllowBlockListItems -ListType [-ExpirationDate ] + [-Allow] + [-Block] + [-Entry ] + [-ListSubType ] + [-OutputJson] + [] +``` + +### NoExpiration +``` +Get-TenantAllowBlockListItems -ListType [-NoExpiration] + [-Allow] + [-Block] + [-Entry ] + [-ListSubType ] + [-OutputJson] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-TenantAllowBlockListItems -ListType Url -Block +``` + +This example returns all blocked URLs. + +### Example 2 +```powershell +Get-TenantAllowBlockListItems -ListType FileHash -Entry "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08" +``` + +This example returns information for the specified file hash value. + +### Example 3 +```powershell +Get-TenantAllowBlockListItems -ListType Url -ListSubType AdvancedDelivery +``` + +This example returns information for all allowed third-party phishing simulation URLs. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +## PARAMETERS + +### -ListType +The ListType parameter specifies the list to view. Valid values are: + +- FileHash +- Sender +- Url +- IP + +```yaml +Type: ListType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Entry +The Entry parameter filters the results based on the ListType parameter value. Valid values are: + +- FileHash: The exact SHA256 file hash value. +- Sender: The exact domain or email address value. +- Url: The exact URL value. +- IP: IPv6 addresses only. Single IPv6 addresses in colon-hexadecimal or zero-compression format or CIDR IPv6 ranges from 1 to 128. + +This value is shown in the Value property of the entry in the output of the Get-TenantAllowBlockListItems cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoExpiration +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Allow +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Block +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpirationDate +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: + +- Specify the date/time value in UTC: For example, `"2021-05-06 14:30:00z"`. +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2020 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +```yaml +Type: DateTime +Parameter Sets: Expiration +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ListSubType +The ListSubType parameter filters the results by subtype. Valid values are: + +- AdvancedDelivery +- Tenant: This is the default value. + +```yaml +Type: ListSubType[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutputJson +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md new file mode 100644 index 0000000000..a77fd3036a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md @@ -0,0 +1,136 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-TenantAllowBlockListSpoofItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-TenantAllowBlockListSpoofItems cmdlet to view spoofed sender entries in the Tenant Allow/Block List. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-TenantAllowBlockListSpoofItems [[-Identity] ] + [-Action ] + [-SpoofType ] + [] +``` + +## DESCRIPTION +The Get-TenantAllowBlockListSpoofItems cmdlet returns the following information: + +- Identity: A random Guid assigned to the spoof pair. This will be used as an **Id parameter** while updating or deleting the spoof pair using **Set-TenantAllowBlockListSpoofItems** and **Remove-TenantAllowBlockListSpoofItems**. +- SpoofedUser: The sending email address if the domain is one of your organization's domains or the sending domain if the domain is external. +- SendingInfrastructure: The true sending domain that's found in the DNS record of the source email server. If no domain is found, the source email server's IP address is shown. +- SpoofType: Indicates whether the domain is internal to your organization or external. +- Action: The two possible values are Allow (messages that contain any spoofed sender email addresses in your organization are allowed from the source email server) or Block (messages that contain any spoofed sender email addresses in your organization are not allowed from the source email server). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-TenantAllowBlockListSpoofItems -SpoofType Internal +``` +This example returns the list of internal spoof pairs. + +### Example 2 +```powershell +Get-TenantAllowBlockListSpoofItems -Action Block +``` +This example returns the list of blocked spoof pairs. + +### Example 3 +```powershell +Get-TenantAllowBlockListSpoofItems | Format-Table SpoofedUser,SendingInfrastructure,SpoofType,Action +``` + +This example returns the list of spoof pairs that appear to be sending spoofed email to your organization. + +### Example 4 +```powershell +$file = "C:\My Documents\Spoof Tenant Allow Block List.csv" + +Get-TenantAllowBlockListSpoofItems | Export-Csv $file +``` + +This example exports the same list of spoofed pairs to a CSV file. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Action +The Action parameter filters the results by action type. Valid values are: + +- Allow +- Block + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpoofType +The SpoofType parameter filters the results by spoof type. Valid values are: + +- External +- Internal + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access/Get-TextMessagingAccount.md b/exchange/exchange-ps/exchange/Get-TextMessagingAccount.md similarity index 84% rename from exchange/exchange-ps/exchange/client-access/Get-TextMessagingAccount.md rename to exchange/exchange-ps/exchange/Get-TextMessagingAccount.md index 10b7699614..11e102c7e7 100644 --- a/exchange/exchange-ps/exchange/client-access/Get-TextMessagingAccount.md +++ b/exchange/exchange-ps/exchange/Get-TextMessagingAccount.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-textmessagingaccount +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-TextMessagingAccount @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-TextMessagingAccount cmdlet to view the text notification settings on mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,7 +32,7 @@ Get-TextMessagingAccount [-Identity] ## DESCRIPTION When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,6 +46,7 @@ This example returns the text messaging settings for Tony's mailbox. ### Example 2 ```powershell $mbx = Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited + $mbx | foreach {Get-TextMessagingAccount -Identity $_.Alias | where {($_.NotificationPhoneNumberVerified -eq $true)} | Format-Table Identity,NotificationPhoneNumber} ``` @@ -58,23 +58,14 @@ This example finds all user mailboxes where text messaging notifications are ena The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -93,7 +84,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -127,7 +118,9 @@ Accept wildcard characters: False ``` ### -ReadFromDomainController -The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -165,12 +158,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ThrottlingPolicy.md b/exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md similarity index 83% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-ThrottlingPolicy.md rename to exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md index 4d7409c3a2..5299f4079b 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ThrottlingPolicy.md +++ b/exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-throttlingpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ThrottlingPolicy @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ThrottlingPolicy cmdlet to view the user throttling settings for one or more throttling policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,9 +32,9 @@ Get-ThrottlingPolicy [[-Identity] ] ## DESCRIPTION The Get-ThrottlingPolicy cmdlet returns the client throttling settings for one or more throttling policies. If you use the Identity parameter, the cmdlet returns the settings for the identified throttling policy. If you don't use the Identity parameter, the cmdlet returns the settings for all throttling policies. -For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,42 +54,42 @@ This example displays the parameters and values for throttling policy Throttling ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +The Identity parameter identifies the name of the throttling policy that you want to return settings for. ```yaml -Type: Fqdn +Type: ThrottlingPolicyIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter identifies the name of the throttling policy that you want to return settings for. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: ThrottlingPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Diagnostics -The Diagnostics switch specifies whether you want the output to include the diagnostics string. To return diagnostics information, use the syntax Get-ThrottlingPolicy -Diagnostics. You don't specify a value for this switch. +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 @@ -106,7 +105,7 @@ Accept wildcard characters: False ``` ### -Explicit -The Explicit switch specifies whether you only want to return the policy settings that have been directly assigned using this policy. By default, this parameter is set to $false. +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 @@ -125,12 +124,10 @@ Accept wildcard characters: False The ThrottlingPolicyScope parameter specifies the scope of the throttling policy. You can use the following values: - Global - - Organization - - Regular -For information about each of these policy scopes, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For information about each of these policy scopes, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). ```yaml Type: ThrottlingPolicyScopeType @@ -150,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md similarity index 85% rename from exchange/exchange-ps/exchange/server-health-and-performance/Get-ThrottlingPolicyAssociation.md rename to exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md index 715ed56636..6850db5cc9 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Get-ThrottlingPolicyAssociation.md +++ b/exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-throttlingpolicyassociation +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-ThrottlingPolicyAssociation @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-ThrottlingPolicyAssociation cmdlet to view existing throttling policy associations in your organization. Throttling policies can be associated with mailboxes, user accounts, mail contacts, mail users, and Exchange server computer accounts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Get-ThrottlingPolicyAssociation [-Anr ] [-DomainController ] [-ResultSize ] [-SortBy ] - [-ThrottlingPolicy ] [] + [-ThrottlingPolicy ] + [] ``` ### Identity @@ -36,57 +36,77 @@ Get-ThrottlingPolicyAssociation [[-Identity] ] [-ResultSize ] [-SortBy ] - [-ThrottlingPolicy ] [] + [-ThrottlingPolicy ] + [] ``` ## DESCRIPTION -For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-ThrottlingPolicyAssociation -OrganizationalUnit Users -``` - -In Exchange Server 2010 and 2013, this example returns a list of all the mailboxes in your organization in the Users OU. - -### Example 2 -```powershell Get-ThrottlingPolicyAssociation -ResultSize unlimited ``` This example retrieves a summary list of all throttling policy associations in your organization. -### Example 3 +### Example 2 ```powershell Get-ThrottlingPolicyAssociation -Anr Chr -DomainController DC01 ``` In Exchange Server 2010 and 2013, this example returns all the mailboxes that resolve from the ambiguous name resolution search on the string "Chr" that are in the domain DC01. This example returns mailboxes for users such as Chris Ashton, Christian Hess, and Christa Geller. -### Example 4 +### Example 3 ```powershell -Get-Group -Identity "Courtney Sweet" | Format-List +Get-ThrottlingPolicyAssociation -Identity "Courtney Sweet" | Format-List ``` -This example returns detailed information for the throttling policy association named Courtney Sweet that's associated with the user's mailbox. +This example returns detailed information for the throttling policy association named Courtney Sweet. ## PARAMETERS +### -Identity +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 +- Distinguished name (DN) +- GUID For example: +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: ThrottlingPolicyAssociationIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml @@ -120,48 +140,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- GUID For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: ThrottlingPolicyAssociationIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -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. @@ -198,9 +176,7 @@ Accept wildcard characters: False The ThrottlingPolicy parameter filters the results by throttling policy. You can use any value that uniquely identifies the throttling policy. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -221,12 +197,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-TransportAgent.md b/exchange/exchange-ps/exchange/Get-TransportAgent.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Get-TransportAgent.md rename to exchange/exchange-ps/exchange/Get-TransportAgent.md index 50c25ded2e..8efaaf32bc 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-TransportAgent.md +++ b/exchange/exchange-ps/exchange/Get-TransportAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-transportagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-TransportAgent @@ -17,17 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Get-TransportAgent cmdlet to view the configuration of a transport agent. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-TransportAgent [[-Identity] ] [-DomainController ] - [-TransportService ] [] +Get-TransportAgent [[-Identity] ] + [-DomainController ] + [-TransportService ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,37 +48,37 @@ This example displays detailed information about the Transport Rule agent that's ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +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: Fqdn +Type: TransportAgentObjectId Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the display name of the transport agent to be displayed. The length of the name can't exceed 64 characters. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: TransportAgentObjectId +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -85,13 +86,9 @@ Accept wildcard characters: False 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. - - MailboxSubmission for the Mailbox Transport Submission service on Mailbox servers. - - MailboxDelivery for the Mailbox Transport Delivery service on Mailbox servers. - - FrontEnd for the Front End Transport service on Mailbox servers. - - Edge on Edge Transport servers. ```yaml @@ -112,12 +109,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-TransportConfig.md b/exchange/exchange-ps/exchange/Get-TransportConfig.md similarity index 86% rename from exchange/exchange-ps/exchange/mail-flow/Get-TransportConfig.md rename to exchange/exchange-ps/exchange/Get-TransportConfig.md index d1da8118c6..3357a4be56 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-TransportConfig.md +++ b/exchange/exchange-ps/exchange/Get-TransportConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-transportconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-TransportConfig @@ -17,18 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-TransportConfig cmdlet to view organization-wide transport configuration settings. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-TransportConfig [[-Identity] ] [-DomainController ] [] +Get-TransportConfig [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION The Get-TransportConfig cmdlet displays configuration information for global transport settings applied across the organization when the cmdlet is run on a Mailbox server. When this cmdlet is run on an Edge Transport server, only the transportation configuration settings for the local computer are shown. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,39 +49,41 @@ This example lists all delivery status notification-related (DSN) configuration ## PARAMETERS -### -DomainController +### -Identity This parameter is available only in on-premises Exchange. -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +This parameter is reserved for internal Microsoft use. ```yaml -Type: Fqdn +Type: OrganizationIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -This parameter is reserved for internal Microsoft use. +### -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. + +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. ```yaml -Type: OrganizationIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -89,12 +92,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-TransportPipeline.md b/exchange/exchange-ps/exchange/Get-TransportPipeline.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/Get-TransportPipeline.md rename to exchange/exchange-ps/exchange/Get-TransportPipeline.md index 9d93f5fb6f..8366b7fc1a 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-TransportPipeline.md +++ b/exchange/exchange-ps/exchange/Get-TransportPipeline.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-transportpipeline +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-TransportPipeline @@ -17,26 +16,25 @@ This cmdlet is available only in on-premises Exchange. Use the Get-TransportPipeline cmdlet to view transport agents and the SMTP event where the transport agent is registered. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-TransportPipeline [-DomainController ] [] +Get-TransportPipeline [-DomainController ] + [] ``` ## DESCRIPTION The Get-TransportPipeline cmdlet enables you to view all the transport agents that are configured in the following locations: - In the Transport service on Mailbox servers. - - In the Front End Transport service on Mailbox servers. - - On Edge Transport server in the perimeter network. The associated transport service must be started and at least one email message must be sent through the server since the last service restart before the transport pipeline can be viewed. Only the transport events and agents that were involved in the processing of email messages since the associated service was last started are returned. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,12 +77,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-TransportRule.md b/exchange/exchange-ps/exchange/Get-TransportRule.md new file mode 100644 index 0000000000..d55f8756f4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-TransportRule.md @@ -0,0 +1,226 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-TransportRule + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-TransportRule cmdlet to view transport rules (mail flow rules) in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-TransportRule [[-Identity] ] + [-DomainController ] + [-State ] + [-DlpPolicy ] + [-ExcludeConditionActionDetails ] + [-Filter ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +On Mailbox servers, this cmdlet returns all rules in the Exchange organization that are stored in Active Directory. On an Edge Transport server, this cmdlet only returns rules that are configured on the local server. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-TransportRule +``` + +This example returns a summary list of all rules in your organization. + +### Example 2 +```powershell +Get-TransportRule "Ethical Wall - Sales and Brokerage Departments" | Format-List +``` + +This example returns detailed information for the rule named "Ethical Wall - Sales and Brokerage Departments". + +For more information about pipelining, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). For more information about how to work with the output of a command, see [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). + +### Example 3 +```powershell +Get-TransportRule -DlpPolicy "PII (U.S.)" +``` + +In on-premises Exchange, this example returns a summary list of the rules that enforce the DLP policy named PII (U.S.) in the organization. + +### Example 4 +```powershell +Get-TransportRule | Where {$_.DlpPolicy -ne $null} +``` + +In on-premises Exchange, this example returns a summary list of all rules that enforce DLP policies in the organization. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The State parameter specifies filters the results by enabled or disabled rules. Valid values are: + +- Enabled: Only enabled rules are returned in the results. +- Disabled: Only disabled rules are returned in the results. + +If you don't use this parameter, the command returns all rules, both enabled and disabled. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpPolicy +**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 ("). + +DLP policies in your organization allow you to prevent unintentional disclosure of sensitive information. Each DLP policy is enforced using a set of transport rules. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeConditionActionDetails +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: + +- $true: The Description, Conditions, and Actions properties, as well as any configured condition, exception and action property values are blank. +- $false: No properties or property values are hidden. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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*'"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/policy-and-compliance/Get-TransportRuleAction.md b/exchange/exchange-ps/exchange/Get-TransportRuleAction.md similarity index 79% rename from exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRuleAction.md rename to exchange/exchange-ps/exchange/Get-TransportRuleAction.md index d39b1ff7a9..a7052dc127 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRuleAction.md +++ b/exchange/exchange-ps/exchange/Get-TransportRuleAction.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-transportruleaction +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-TransportRuleAction @@ -17,18 +16,19 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-TransportRuleAction cmdlet to view the actions that are available for transport rules (mail flow rules). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-TransportRuleAction [[-Name] ] [] +Get-TransportRuleAction [[-Name] ] + [] ``` ## DESCRIPTION In on-premises Exchange, the actions that are available on Mailboxes servers and Edge Transports server are different. Also, the names of some of the actions that are returned by this cmdlet are different than the corresponding parameter names in the New-TransportRule and Set-TransportRule cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,7 +46,7 @@ Get-TransportRuleAction -Name DeleteMessage | Format-List This example retrieves detailed information about the action named DeleteMessage. -For more information about pipelining, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). For more information about how to work with the output of a command, see [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). For more information about how to work with the output of a command, see [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ## PARAMETERS @@ -71,12 +71,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRulePredicate.md b/exchange/exchange-ps/exchange/Get-TransportRulePredicate.md similarity index 80% rename from exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRulePredicate.md rename to exchange/exchange-ps/exchange/Get-TransportRulePredicate.md index 3460f1124b..1781b502e3 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRulePredicate.md +++ b/exchange/exchange-ps/exchange/Get-TransportRulePredicate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-transportrulepredicate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Get-TransportRulePredicate @@ -17,12 +16,13 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Get-TransportRulePredicate cmdlet to view the predicates (conditions and exceptions) that are available for transport rules (mal flow rules). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-TransportRulePredicate [[-Name] ] [] +Get-TransportRulePredicate [[-Name] ] + [] ``` ## DESCRIPTION @@ -30,7 +30,7 @@ Collectively, the conditions and exceptions in rules are known as predicates, be In on-premises Exchange, the predicates that are available on Mailboxes servers and Edge Transports server are different. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +48,7 @@ Get-TransportRulePredicate -Name SubjectMatches | Format-List This example returns detailed information about the predicate named SubjectMatches. -For more information about pipelining, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). For more information about how to work with the output of a command, see [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about pipelining, see [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). For more information about how to work with the output of a command, see [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ### Example 3 ```powershell @@ -57,7 +57,7 @@ Get-TransportRulePredicate | Where {$_.Name -like "*Attachment*"} This example returns a summary list of all predicates that have Attachment in the name. -For more information about how to work with the output of a command, see [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). +For more information about how to work with the output of a command, see [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help). ## PARAMETERS @@ -82,12 +82,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-TransportServer.md b/exchange/exchange-ps/exchange/Get-TransportServer.md similarity index 83% rename from exchange/exchange-ps/exchange/mail-flow/Get-TransportServer.md rename to exchange/exchange-ps/exchange/Get-TransportServer.md index b4fedf1480..9e6bfd34f4 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-TransportServer.md +++ b/exchange/exchange-ps/exchange/Get-TransportServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-transportserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-TransportServer @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-TransportServer cmdlet to view settings that are associated with the Hub Transport server role or the Edge Transport server role. -Note: In Exchange 2013 or later, use the Get-TransportService cmdlet instead. If you have scripts that use Get-TransportServer, update them to use Get-TransportService. +**Note**: In Exchange 2013 or later, use the Get-TransportService cmdlet instead. If you have scripts that use Get-TransportServer, update them to use Get-TransportService. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-TransportServer [[-Identity] ] [-DomainController ] [] +Get-TransportServer [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,45 +49,42 @@ This example retrieves the detailed transport configuration information for the ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +The Identity parameter specifies the Transport server that you want to view. You can use any value that uniquely identifies the server. For example: -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. +- Name +- GUID +- Distinguished name (DN) +- ExchangeLegacyDN ```yaml -Type: Fqdn +Type: TransportServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- GUID - -- Distinguished name (DN) +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -- ExchangeLegacyDN +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. ```yaml -Type: TransportServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -95,12 +93,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-TransportService.md b/exchange/exchange-ps/exchange/Get-TransportService.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/Get-TransportService.md rename to exchange/exchange-ps/exchange/Get-TransportService.md index ba1b816fc3..de2c585879 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-TransportService.md +++ b/exchange/exchange-ps/exchange/Get-TransportService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-transportservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-TransportService @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Get-TransportService cmdlet to view the settings of the Transport service on Exchange 2013 or later Mailbox servers or Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-TransportService [[-Identity] ] [-DomainController ] [] +Get-TransportService [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,47 +47,44 @@ This example retrieves the detailed transport configuration information for the ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -Identity +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: -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. +- Name +- GUID +- Distinguished name (DN) +- ExchangeLegacyDN + +You can't use this parameter on an Edge Transport server. ```yaml -Type: Fqdn +Type: TransportServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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 - -- GUID - -- Distinguished name (DN) - -- ExchangeLegacyDN +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. -You can't use this parameter on an Edge Transport server. +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. ```yaml -Type: TransportServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -95,12 +93,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Get-Trust.md b/exchange/exchange-ps/exchange/Get-Trust.md similarity index 83% rename from exchange/exchange-ps/exchange/active-directory/Get-Trust.md rename to exchange/exchange-ps/exchange/Get-Trust.md index 21ec1ea727..06c4e8a053 100644 --- a/exchange/exchange-ps/exchange/active-directory/Get-Trust.md +++ b/exchange/exchange-ps/exchange/Get-Trust.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-trust +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-Trust @@ -17,18 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Get-Trust cmdlet to return external and forest trusts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-Trust [-DomainName ] [] +Get-Trust [-DomainName ] + [] ``` ## DESCRIPTION The Get-Trust cmdlet is used by the Exchange admin center in to populate fields that display recipient information. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,12 +62,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMActiveCalls.md b/exchange/exchange-ps/exchange/Get-UMActiveCalls.md similarity index 85% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMActiveCalls.md rename to exchange/exchange-ps/exchange/Get-UMActiveCalls.md index 54ba8de2e4..ad6d739107 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMActiveCalls.md +++ b/exchange/exchange-ps/exchange/Get-UMActiveCalls.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umactivecalls -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-UMActiveCalls @@ -17,28 +16,36 @@ This cmdlet is available only in on-premises Exchange. Use the Get-UMActiveCalls cmdlet to return information about the calls that are active and being processed by the Mailbox server running the Microsoft Exchange Unified Messaging service. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### DialPlan ``` -Get-UMActiveCalls -DialPlan [-DomainController ] [] +Get-UMActiveCalls -DialPlan + [-DomainController ] + [] ``` ### ServerInstance ``` -Get-UMActiveCalls -InstanceServer [-DomainController ] [] +Get-UMActiveCalls -InstanceServer + [-DomainController ] + [] ``` ### UMIPGateway ``` -Get-UMActiveCalls -IPGateway [-DomainController ] [] +Get-UMActiveCalls -IPGateway + [-DomainController ] + [] ``` ### Server ``` -Get-UMActiveCalls [-Server ] [-DomainController ] [] +Get-UMActiveCalls [-Server ] + [-DomainController ] + [] ``` ## DESCRIPTION @@ -48,7 +55,7 @@ When a Mailbox server is process cycling, the Get-UMActiveCalls cmdlet doesn't r After this task is completed, you can see the list of active calls being processed by a Mailbox server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -91,7 +98,7 @@ You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in t Type: UMDialPlanIdParameter Parameter Sets: DialPlan Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -109,7 +116,7 @@ You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in t Type: UMServer Parameter Sets: ServerInstance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -121,14 +128,13 @@ Accept wildcard characters: False ### -IPGateway 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. ```yaml Type: UMIPGatewayIdParameter Parameter Sets: UMIPGateway Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -144,7 +150,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -157,11 +163,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in the same command. @@ -170,7 +173,7 @@ You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in t Type: ServerIdParameter Parameter Sets: Server Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -184,12 +187,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Get-UMAutoAttendant.md similarity index 79% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMAutoAttendant.md rename to exchange/exchange-ps/exchange/Get-UMAutoAttendant.md index 4dd30973df..4ae3dced8b 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMAutoAttendant.md +++ b/exchange/exchange-ps/exchange/Get-UMAutoAttendant.md @@ -1,29 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umautoattendant -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMAutoAttendant ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMAutoAttendant cmdlet to retrieve the properties and the values for a Unified Messaging (UM) auto attendant. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMAutoAttendant [[-Identity] ] [-DomainController ] - [-UMDialPlan ] [] +Get-UMAutoAttendant [[-Identity] ] + [-DomainController ] + [-UMDialPlan ] + [] ``` ## DESCRIPTION @@ -31,7 +32,7 @@ The Get-UMAutoAttendant cmdlet retrieves the properties for a single UM auto att After this task is completed, if no parameter is supplied with the cmdlet, the cmdlet returns all UM auto attendants in the Active Directory forest. Or, if the UM dial plan ID is supplied but no name is supplied, the cmdlet returns all UM auto attendants linked to the UM dial plan. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,37 +59,35 @@ This examples displays all the UM auto attendants associated with the UM dial pl ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: UMAutoAttendantIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -99,7 +98,7 @@ The UMDialPlan parameter specifies whether to display all the UM auto attendants Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -113,12 +112,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md similarity index 77% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMCallAnsweringRule.md rename to exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md index e67211759c..e469e77136 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md @@ -1,29 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umcallansweringrule -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMCallAnsweringRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMCallAnsweringRule cmdlet to view the properties of a Unified Messaging (UM) call answering rule that has been created within a UM-enabled mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMCallAnsweringRule [[-Identity] ] [-DomainController ] - [-Mailbox ] [] +Get-UMCallAnsweringRule [[-Identity] ] + [-DomainController ] + [-Mailbox ] + [] ``` ## DESCRIPTION @@ -31,7 +32,7 @@ The Get-UMCallAnsweringRule cmdlet enables you to view the properties of a call After this task is completed, the cmdlet returns the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,37 +52,35 @@ This example displays the properties of the call answering rule MyUMCallAnswerin ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the identifier for a call answering rule being viewed. ```yaml -Type: Fqdn +Type: UMCallAnsweringRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identifier for a call answering rule being viewed. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: UMCallAnsweringRuleIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -89,23 +88,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the mailbox of the user who is running the command is used. @@ -114,7 +104,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -128,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallDataRecord.md b/exchange/exchange-ps/exchange/Get-UMCallDataRecord.md similarity index 83% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMCallDataRecord.md rename to exchange/exchange-ps/exchange/Get-UMCallDataRecord.md index 207678e28e..868677c8f0 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallDataRecord.md +++ b/exchange/exchange-ps/exchange/Get-UMCallDataRecord.md @@ -1,28 +1,28 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umcalldatarecord -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMCallDataRecord ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMCallDataRecord cmdlet to display Unified Messaging (UM) call data records for a specific UM-enabled user's mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMCallDataRecord -Mailbox [-DomainController ] +Get-UMCallDataRecord -Mailbox + [-DomainController ] [] ``` @@ -30,34 +30,21 @@ Get-UMCallDataRecord -Mailbox [-DomainController ] The Get-UMCallDataRecord cmdlet displays UM call data records for the last 90 days for a UM-enabled mailbox that you specify. Each UM call data record provides detailed information about all calls either placed to or received by the specified user. The following list details each of the properties that are returned: - Date: Date and time of the Mailbox server running the Microsoft Exchange Unified Messaging service that took the call in the Coordinated Universal Time (UTC) format. - - Duration: Total duration of this call. For Find Me calls, this will always be zero because the call is being transferred and won't be handled by Unified Messaging any longer. - - AudioCodec: Audio codec used for the call including G.711 or Group System Mobile (GSM). - - DialPlan: Name of the UM dial plan handling the call. - - CallType: Type of the call (localized in the user's language): Call Answering Voice Message, Call Answering Missed Call, , Auto Attendant, Subscriber Access, Fax, PlayOnPhone, Find Me, None, UnauthenticatedPilotNumber, or PromptProvisioning. - - CallingNumber: Phone number or address of the caller. - - CalledNumber: Phone number or address of the intended recipient of the call. - - Gateway: Fully qualified domain name (FQDN) of the UM IP gateway handling the call. - - Network MOS (NMOS): Mean opinion score for the network performance. - - NMOSDegradation: Total NMOS degradation, which is how far the NMOS reported value was from its top value for the corresponding audio codec. - - PercentagePacketLoss: Percentage that reflects the average network packet loss during the call. - - Jitter: Average jitter of the network. - - RoundTripMilliseconds: Round trip time for Real Time Control Protocol (RTCP) statistics in milliseconds. - - BurstLossDurationMilliseconds: Average duration of packet loss during bursts during the call. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,30 +61,21 @@ This example displays the UM call data records for the UM-enabled user Tony. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -107,15 +85,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -129,12 +105,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallRouterSettings.md b/exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md similarity index 82% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMCallRouterSettings.md rename to exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md index ce4c2a05a4..44123198a3 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallRouterSettings.md +++ b/exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umcallroutersettings -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-UMCallRouterSettings @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Get-UMCallRouterSettings cmdlet to view the settings of the Microsoft Exchange Unified Messaging Call Router service. This service exists on Exchange servers that have the Client Access server role installed, and is used by telephony clients to connect to Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMCallRouterSettings [[-Server] ] [-DomainController ] [] +Get-UMCallRouterSettings [[-Server] ] + [-DomainController ] + [] ``` ## DESCRIPTION When the cmdlet is used for a single server, it returns the UM call router properties including MaxCalls, MaxFaxCalls and UMDialPlans. The properties and their values are stored in the Unified Messaging section of the Microsoft Exchange configuration object in Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,11 +53,8 @@ This example displays detailed information for the Microsoft Exchange Unified Me 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -65,7 +63,7 @@ If you don't use this parameter, the command is run on the local server. Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: 1 @@ -81,7 +79,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -95,12 +93,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallSummaryReport.md b/exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md similarity index 83% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMCallSummaryReport.md rename to exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md index 0b4a581d58..87b5ea88f8 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMCallSummaryReport.md +++ b/exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md @@ -1,74 +1,57 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umcallsummaryreport -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMCallSummaryReport ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMCallSummaryReport cmdlet to return statistics about all calls received or placed by Mailbox servers running the Microsoft Exchange Unified Messaging service in an organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMCallSummaryReport -GroupBy [-DomainController ] +Get-UMCallSummaryReport -GroupBy + [-DomainController ] [-UMDialPlan ] - [-UMIPGateway ] [] + [-UMIPGateway ] + [] ``` ## DESCRIPTION -The Get-UMCallSummaryReport cmdlet displays the aggregated statistics about all calls received or placed by Mailbox servers running the Microsoft Exchange Unified Messaging service in an organization including voice messages, missed calls, subscriber access, auto attendant, or fax calls. The data returned by running this cmdlet includes audio quality metrics for the sample calls such as the following: +The Get-UMCallSummaryReport cmdlet displays the aggregated statistics about all calls received or placed by servers running the Microsoft Exchange Unified Messaging service in an organization including voice messages, missed calls, subscriber access, auto attendant, or fax calls. The data returned by running this cmdlet includes audio quality metrics for the sample calls such as the following: - Date: Date in which all calls associated with the selected UM IP gateway and UM dial plan have been grouped based on the value of the GroupBy parameter: Total has the value ---, Month has the value MMM/YY and Day has the value MM/DD/YY, where MMM is the first three letters of the month and YY is the last two digits of the year. - - Voice Message: Percentage of incoming calls answered by Unified Messaging on behalf of users in which callers left a voice message. - - Missed Calls: Percentage of incoming calls answered by Unified Messaging on behalf of users in which the callers didn't leave a voice message resulting in a missed call notification. - - Outlook Voice Access: Percentage of incoming calls in which users authenticate to Unified Messaging to access their email, calendars, and voice messages. - - Outbound: Percentage of calls placed or transferred by Unified Messaging on behalf of authenticated or unauthenticated users. This property can have the value Find Me, Play On Phone, or Play On Phone Greetings. - - Automated Attendant: Percentage of incoming calls that were answered by auto attendants. - - Fax: Percentage of incoming calls that were redirected to a fax partner. - - Other: Percentage of any other incoming or placed calls that don't fall in any of the previous categories. This is provided to allow different types of calls that might be provided in the future to be accounted for as well. This category includes unauthenticated calls made to pilot numbers. - -- Failed Or Rejected: Percentage of calls that either failed or were rejected by the Mailbox server for that organization. - +- Failed Or Rejected: Percentage of calls that either failed or were rejected by the server for that organization. - Audio Quality: Overall audio quality for the selected period of time for the organization/user. 4.50 or higher = Excellent, 3.5 to 4.49 = Good, 2.5 to 3.49 = Average, 1.50 to 2.49 =Poor, and 1.49 or lower = Bad. - - Total Calls: If the UM IP gateway is selected, this is the total number of calls grouped for the selected UM IP gateway for the corresponding date, If the UM dial plan control is selected, this is the total number of calls grouped for the selected UM dial plan for the corresponding date, and If the user is selected, this column has the total number of calls for the user. - - Network MOS (NMOS): Average NMOS for the specific UM dial plan or UM IP gateway. - -- NMOS Degradation: - -- NMOS degradation for the specific UM dial plan or UM IP gateway.: - +- NMOS Degradation. +- NMOS degradation for the specific UM dial plan or UM IP gateway. - Jitter: Average jitter for the specific UM dial plan or UM IP gateway. - - Packet loss: Average packet loss for the specific UM dial plan or UM IP gateway. - - Round Trip: Round trip time (in milliseconds) for the selected UM dial plan or UM IP gateway. - - Burst loss Duration: Average duration of packet loss during bursts of losses for the selected UM dial plan or UM IP gateway. - - Number of samples: Number of calls sampled, when calculating the averages. A sample refers to any call data record that contains at least one of the audio quality metrics. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -106,16 +89,14 @@ This example displays the statistics for calls received or placed by Mailbox ser The GroupBy parameter specifies how to return the results. Valid values are: - Day: Daily statistics for the last 90 days. - - Month: Monthly statistics for the last 12 months. - - Total: A summary of all call statistics for your Mailbox servers running the Microsoft Exchange Unified Messaging service in your organization. ```yaml Type: GroupBy Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -125,15 +106,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -149,7 +128,7 @@ The UMDialPlan parameter specifies the Unified Messaging (UM) dial plan to show Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -165,7 +144,7 @@ The UMIPGateway parameter specifies the UM IP gateway to show statistics for. If Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -179,12 +158,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMDialPlan.md b/exchange/exchange-ps/exchange/Get-UMDialPlan.md similarity index 78% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMDialPlan.md rename to exchange/exchange-ps/exchange/Get-UMDialPlan.md index 05be284211..fe86e9ee42 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMDialPlan.md +++ b/exchange/exchange-ps/exchange/Get-UMDialPlan.md @@ -1,28 +1,29 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umdialplan -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMDialPlan ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMDialPlan cmdlet to display the properties of a single Unified Messaging (UM) dial plan or to return a list of all UM dial plans associated with Mailbox servers running the Microsoft Exchange Unified Messaging service. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMDialPlan [[-Identity] ] [-DomainController ] [] +Get-UMDialPlan [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION @@ -30,7 +31,7 @@ The Get-UMDialPlan cmdlet displays all properties for a UM dial plan. After this task is completed, when you specify the Identity parameter, you can view the values set. When the Get-UMDialPlan cmdlet is run, if no parameter is supplied, the cmdlet returns all UM dial plans in the Active Directory forest. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,37 +51,35 @@ This example displays a formatted list of properties for the UM dial plan MyUMDi ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the UM dial plan ID. ```yaml -Type: Fqdn +Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the UM dial plan ID. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: UMDialPlanIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -89,12 +88,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMHuntGroup.md b/exchange/exchange-ps/exchange/Get-UMHuntGroup.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMHuntGroup.md rename to exchange/exchange-ps/exchange/Get-UMHuntGroup.md index 2b384b5812..d1a7328d41 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMHuntGroup.md +++ b/exchange/exchange-ps/exchange/Get-UMHuntGroup.md @@ -1,29 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umhuntgroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMHuntGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMHuntGroup cmdlet to display the properties and values for an existing Unified Messaging (UM) hunt group. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMHuntGroup [[-Identity] ] [-DomainController ] - [-UMDialPlan ] [] +Get-UMHuntGroup [[-Identity] ] + [-DomainController ] + [-UMDialPlan ] + [] ``` ## DESCRIPTION @@ -31,7 +32,7 @@ The Get-UMHuntGroup cmdlet retrieves the properties for a single UM hunt group o After this task is completed, if the Identity parameter is specified, the properties for the UM hunt group are returned. If neither the Identity nor the UMDialPlan parameter is specified, all UM hunt groups in the Active Directory forest are returned. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,37 +59,35 @@ This example displays all of the UM hunt groups associated with the UM dial plan ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: UMHuntGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identifier for the UM hunt group being viewed. This is the directory object ID for the UM hunt group. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: UMHuntGroupIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -99,7 +98,7 @@ The UMDialPlan parameter specifies the UM dial plan associated with a UM hunt gr Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -113,12 +112,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMIPGateway.md b/exchange/exchange-ps/exchange/Get-UMIPGateway.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMIPGateway.md rename to exchange/exchange-ps/exchange/Get-UMIPGateway.md index b5d85d7683..f027b0d0a4 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMIPGateway.md +++ b/exchange/exchange-ps/exchange/Get-UMIPGateway.md @@ -1,28 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umipgateway -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMIPGateway ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMIPGateway cmdlet to return a list of properties and values for a specified Unified Messaging (UM) IP gateway or a list of UM IP gateways. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMIPGateway [[-Identity] ] [-DomainController ] [-IncludeSimulator] [] +Get-UMIPGateway [[-Identity] ] + [-DomainController ] + [-IncludeSimulator] + [] ``` ## DESCRIPTION @@ -32,7 +34,7 @@ When you're using the Get-UMIPGateway cmdlet, you can't enter the IP address con After this task is completed, you can view the list of properties and values for a specific UM IP gateway. Or, if the Identity parameter isn't used, the cmdlet returns a list of all UM IP gateways in the forest. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,48 +61,48 @@ This example displays all the UM IP gateways including IP gateway simulators in ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: UMIPGatewayIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -IncludeSimulator -The IncludeSimulator switch retrieves the simulator of the UM IP gateway being viewed. A simulator allows a client to connect to the Mailbox server. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -114,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-UMMailbox.md b/exchange/exchange-ps/exchange/Get-UMMailbox.md new file mode 100644 index 0000000000..215a6b501d --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-UMMailbox.md @@ -0,0 +1,297 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-UMMailbox + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Get-UMMailbox cmdlet to view existing mailboxes that are Unified Messaging (UM) enabled. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AnrSet +``` +Get-UMMailbox [-Anr ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-ResultSize ] + [-SortBy ] + [] +``` + +### Identity +``` +Get-UMMailbox [[-Identity] ] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-OrganizationalUnit ] + [-ReadFromDomainController] + [-ResultSize ] + [-SortBy ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-UMMailbox +``` + +This example displays a summary list of all the UM-enabled mailboxes in your organization. + +### Example 2 +```powershell +Get-UMMailbox -Identity tonysmith@contoso.com | Format-List +``` + +This example displays detailed information for the UM-enabled mailbox for tonysmith@contoso.com. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +```yaml +Type: String +Parameter Sets: AnrSet +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```yaml +Type: OrganizationalUnitIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName +- ServerLegacyDN + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-UMMailboxPIN.md b/exchange/exchange-ps/exchange/Get-UMMailboxPIN.md new file mode 100644 index 0000000000..c3eb5e4cc0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-UMMailboxPIN.md @@ -0,0 +1,210 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-UMMailboxPin + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Get-UMMailboxPIN cmdlet to return information from a Unified Messaging (UM)-enabled user's mailbox. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-UMMailboxPin [[-Identity] ] + [-Credential ] + [-DomainController ] + [-IgnoreDefaultScope] + [-IgnoreErrors] + [-ReadFromDomainController] + [-ResultSize ] + [] +``` + +## DESCRIPTION +The Get-UMMailboxPIN cmdlet returns information calculated from the PIN data stored in encrypted form in the user's mailbox. This cmdlet also shows whether the mailbox or user access has been locked out. + +After this task is completed, you can view information on a user's mailbox. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-UMMailboxPIN +``` + +This example displays the UM mailbox PIN-related properties for all UM-enabled users. + +### Example 2 +```powershell +Get-UMMailboxPIN -Identity tonysmith@contoso.com +``` + +This example displays the UM mailbox PIN-related properties for tonysmith@contoso.com. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreErrors +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/unified-messaging/Get-UMMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md similarity index 79% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMMailboxPolicy.md rename to exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md index 88c76b662a..d3e95a0446 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md @@ -1,29 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-ummailboxpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UMMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Get-UMMailboxPolicy cmdlet to display the properties and values of a Unified Messaging (UM) mailbox policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMMailboxPolicy [[-Identity] ] [-DomainController ] - [-UMDialPlan ] [] +Get-UMMailboxPolicy [[-Identity] ] + [-DomainController ] + [-UMDialPlan ] + [] ``` ## DESCRIPTION @@ -31,7 +32,7 @@ The Get-UMMailboxPolicy cmdlet retrieves the configuration properties and values After this task is completed, if the Identity parameter is supplied, the properties and values for the specified UM mailbox policy object are returned. If no parameter is specified at the command prompt, all UM mailbox policies in the Active Directory forest are returned. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,37 +59,35 @@ This examples displays all the UM mailbox policies associated with the UM dial p ## PARAMETERS -### -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. +### -Identity +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: Fqdn +Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identifier for the UM mailbox policy being viewed. This is the directory object ID for the UM mailbox policy. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: MailboxPolicyIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -99,7 +98,7 @@ The UMDialPlan parameter specifies that all UM mailbox policies associated with Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -113,12 +112,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMService.md b/exchange/exchange-ps/exchange/Get-UMService.md similarity index 83% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UMService.md rename to exchange/exchange-ps/exchange/Get-UMService.md index 55b08aedf9..6551e952a2 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMService.md +++ b/exchange/exchange-ps/exchange/Get-UMService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umservice -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-UMService @@ -17,12 +16,14 @@ This cmdlet is available only in on-premises Exchange. Use the Get-UMService cmdlet to view the settings of the Microsoft Exchange Unified Messaging service on Exchange 2013 or Exchange 2016 Mailbox servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMService [[-Identity] ] [-DomainController ] [] +Get-UMService [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION @@ -30,7 +31,7 @@ When the cmdlet is used for a single Exchange server, it returns the Unified Mes The ExchangeVersion attribute that's returned is the minimum version of Exchange you can use to manage the returned object. This attribute isn't the same as the version of Exchange that's displayed in the Exchange admin center when you select Server Configuration. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,38 +51,19 @@ This example displays detailed information for the Microsoft Exchange Unified Me ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity 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 - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml Type: UMServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: 1 @@ -90,17 +72,33 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UmServer.md b/exchange/exchange-ps/exchange/Get-UmServer.md similarity index 89% rename from exchange/exchange-ps/exchange/unified-messaging/Get-UmServer.md rename to exchange/exchange-ps/exchange/Get-UmServer.md index 991e84cffc..0ba48166ad 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UmServer.md +++ b/exchange/exchange-ps/exchange/Get-UmServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-umserver +online version: https://learn.microsoft.com/powershell/module/exchange/get-umserver applicable: Exchange Server 2010 title: Get-UmServer schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Get-UMServer @@ -17,12 +16,14 @@ This cmdlet is available only in Exchange Server 2010. Use the Get-UMServer cmdlet to view settings that are associated with the Unified Messaging (UM) server role. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UMServer [[-Identity] ] [-DomainController ] [] +Get-UMServer [[-Identity] ] + [-DomainController ] + [] ``` ## DESCRIPTION @@ -32,7 +33,7 @@ The ExchangeVersion attribute that's returned is the minimum version of Microsof After this task is completed, you can view the parameters and values for a single Unified Messaging server or a list of all of the Unified Messaging servers in Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,11 +57,8 @@ This example returns detailed information for the Unified Messaging server named 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 - - GUID - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -97,12 +95,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md new file mode 100644 index 0000000000..07a961fcf8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md @@ -0,0 +1,139 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-UnifiedAuditLogRetentionPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-UnifiedAuditLogRetentionPolicy cmdlet to view the properties of the audit log retention policies in the Microsoft Defender portal or the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-UnifiedAuditLogRetentionPolicy + [-Operation ] + [-RecordType ] + [-RetentionDuration ] + [-UserId ] + [] +``` + +## DESCRIPTION +Audit log retention policies are used to specify a retention duration for audit logs for that are generated by admin and user activity. An audit log retention policy can specify the retention duration based on the type of audited activities, the Microsoft 365 service that activities are performed in, or the users who performed the activities. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-UnifiedAuditLogRetentionPolicy | Sort-Object -Property Priority | Format-List Priority,Name,Description,RecordTypes,Operations,UserIds,RetentionDuration +``` + +This example lists the configurable properties for all audit log retention policies in your organization. The command also lists the policies in order of highest to lowest priority. + +### Example 2 +```powershell +Get-UnifiedAuditLogRetentionPolicy -RecordType ExchangeItem | Format-List Name,Description,RecordTypes,Operations,UserIds,RetentionDuration,Priority +``` + +This example lists the configurable properties for all audit log retention policies that apply to audit records the record type of ExchangeItem. + +## PARAMETERS + +### -Operation +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"`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter filters the policy results by the retention duration specified in the policy. Valid values are: + +- ThreeMonths +- SixMonths +- NineMonths +- TwelveMonths +- TenYears + +```yaml +Type: UnifiedAuditLogRetentionDuration +Parameter Sets: (All) +Aliases: +Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths, TenYears +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserId +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"`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-UnifiedGroup.md b/exchange/exchange-ps/exchange/Get-UnifiedGroup.md new file mode 100644 index 0000000000..0d661079bb --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-UnifiedGroup.md @@ -0,0 +1,346 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-UnifiedGroup + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-UnifiedGroup cmdlet to view Microsoft 365 Groups in your cloud-based organization. To view members, owners and subscribers for Microsoft 365 Groups, use the Get-UnifiedGroupLinks cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Get-UnifiedGroup [[-Identity] ] + [-Filter ] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAllProperties] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-IncludeRejectMessagesFromSendersOrMembersWithDisplayNames] + [-IncludeSoftDeletedGroups] + [-ResultSize ] + [-SortBy ] + [] +``` + +### AnrSet +``` +Get-UnifiedGroup [-Anr ] + [-Filter ] + [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] + [-IncludeAllProperties] + [-IncludeBypassModerationFromSendersOrMembersWithDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] + [-IncludeModeratedByWithDisplayNames] + [-IncludeRejectMessagesFromSendersOrMembersWithDisplayNames] + [-IncludeSoftDeletedGroups] + [-ResultSize ] + [-SortBy ] + [] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-UnifiedGroup +``` + +This example returns a summary list of all Microsoft 365 Groups. + +### Example 2 +```powershell +Get-UnifiedGroup | Format-List DisplayName,EmailAddresses,Notes,ManagedBy,AccessType +``` + +This example returns the following information about all Microsoft 365 Groups: + +- Display name +- Email address +- Description +- Owners +- Privacy + +### Example 3 +```powershell +Get-UnifiedGroup -Identity "Marketing Department" | Format-List +``` + +This example returns detailed information about the Microsoft 365 Group named Marketing Department. + +### Example 4 +```powershell +Get-UnifiedGroup | Where-Object {-Not $_.ManagedBy} +``` + +This example returns Microsoft 365 Groups that do not have an owner. + +### Example 5 +```powershell +Get-UnifiedGroup -Filter {ResourceProvisioningOptions -eq "Team"} +``` + +This example returns Microsoft 365 Groups that are created when a Microsoft Team is created. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +**Note**: You can use the DisplayName value to identify the Microsoft 365 Group, but the results aren't guaranteed to be unique. If you must return a singular and unique result, use a unique identifier for the Microsoft 365 Group. + +```yaml +Type: UnifiedGroupIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Anr +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAllProperties +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeBypassModerationFromSendersOrMembersWithDisplayNames +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeGrantSendOnBehalfToWithDisplayNames +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeModeratedByWithDisplayNames +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeRejectMessagesFromSendersOrMembersWithDisplayNames +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSoftDeletedGroups +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +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. + +You can sort by the following properties: + +- Name +- DisplayName +- Alias + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md new file mode 100644 index 0000000000..e47851e9e1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md @@ -0,0 +1,113 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-UnifiedGroupLinks + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Get-UnifiedGroupLinks cmdlet to view membership and ownership information for Microsoft 365 Groups in your cloud-based organization. To view other properties for Microsoft 365 Groups, use the Get-UnifiedGroup cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-UnifiedGroupLinks [-Identity] -LinkType + [-ResultSize ] + [] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-UnifiedGroupLinks -Identity "Human Resources Department" -LinkType Members +``` + +This example show the members of the Microsoft 365 Group named Human Resources Department + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: UnifiedGroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -LinkType +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. +- Owners: Add or remove members, delete conversations, changes Team settings, delete the Team, and full control of the connected SharePoint site. A group must have at least one owner. +- Subscribers: Members who receive conversation and calendar event notifications from the group. All subscribers are members of the group, but all members aren't necessarily subscribers (depending on the AutoSubscribeNewMembers property value of the group and when the member was added). + +```yaml +Type: LinkType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-User.md b/exchange/exchange-ps/exchange/Get-User.md new file mode 100644 index 0000000000..3cafe8aba0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-User.md @@ -0,0 +1,517 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-User + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Get-User cmdlet to view existing user objects in your organization. This cmdlet returns all objects that have user accounts (for example, user mailboxes, mail users, and user accounts). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AnrSet +``` +Get-User [-Anr ] + [-Arbitration] + [-AuditLog] + [-AuxAuditLog] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeDirectReportsWithDisplayNames] + [-IsVIP] + [-OrganizationalUnit ] + [-PublicFolder] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-ResultSize ] + [-Sortby ] + [-SupervisoryReviewPolicy] + [] +``` + +### Identity +``` +Get-User [[-Identity] ] + [-Arbitration] + [-AuditLog] + [-AuxAuditLog] + [-Credential ] + [-DomainController ] + [-Filter ] + [-IgnoreDefaultScope] + [-IncludeDirectReportsWithDisplayNames] + [-IsVIP] + [-OrganizationalUnit ] + [-PublicFolder] + [-ReadFromDomainController] + [-RecipientTypeDetails ] + [-ResultSize ] + [-Sortby ] + [-SupervisoryReviewPolicy] + [] +``` + +## DESCRIPTION +The Get-User cmdlet returns no mail-related properties for mailboxes or mail users. To view the mail-related properties for a user, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox or Get-MailUser). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-User -ResultSize unlimited +``` + +This example returns a summary list of all users in your organization. + +### Example 2 +```powershell +Get-User -Identity "Coy Damon" | Format-List +``` + +This example returns detailed information for the user named Coy Damon. + +### Example 3 +```powershell +Get-User -OrganizationalUnit "Marketing" +``` + +This example retrieves information about users in the Marketing OU. + +### Example 4 +```powershell +Get-User -Filter "Title -like 'Manager*'" +``` + +This example uses the Filter parameter to retrieve information about all users that have the word Manager at the end of their title. + +## PARAMETERS + +### -Identity +The Identity parameter the user that you want to view. You can use any value that uniquely identifies the user. For example: + +- Name +- User principal name (UPN) +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Anr +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) +- DisplayName +- FirstName +- LastName +- Alias + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Arbitration +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. + +Arbitration mailboxes are system mailboxes that are used for storing different types of system data and for managing messaging approval workflow. + +To return arbitration mailboxes that are used to store audit log settings or data, don't use this switch. Instead, use the AuditLog or AuxAuditLog switches. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuditLog +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. + +Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. + +To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuxAuditLog +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. + +Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. + +To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +This parameter is available only in on-premises Exchange. + +The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. + +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: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. For more information about the filterable properties in Exchange server and Exchange Online, see [Filterable properties for the Filter parameter](https://learn.microsoft.com/powershell/exchange/filter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeDirectReportsWithDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill IncludeDirectReportsWithDisplayNames Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AnrSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsVIP +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. + +For more information about priority accounts, see [Manage and monitor priority accounts](https://learn.microsoft.com/microsoft-365/admin/setup/priority-accounts). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationalUnit +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 +- Canonical name +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolder +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadFromDomainController +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. + +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. + +By default, the recipient scope is set to the domain that hosts your Exchange servers. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientTypeDetails +The RecipientTypeDetails parameter filters the results by the specified user subtype. Valid values are: + +- DisabledUser +- DiscoveryMailbox +- EquipmentMailbox +- GuestMailUser (Exchange 2016 or later and cloud) +- GroupMailbox (Exchange 2013 only) +- LegacyMailbox +- LinkedMailbox +- LinkedRoomMailbox (Exchange 2013 or later and cloud) +- LinkedUser +- MailUser +- PublicFolderMailbox (Exchange 2013 or later and cloud) +- RemoteEquipmentMailbox +- RemoteRoomMailbox +- RemoteSharedMailbox +- RemoteTeamMailbox (Exchange 2013 or later and cloud) +- RemoteUserMailbox +- RoomMailbox +- SchedulingMailbox (Exchange 2016 or later and cloud) +- SharedMailbox +- SharedWithMailUser (cloud only) +- TeamMailbox (Exchange 2013 or later and cloud) +- User +- UserMailbox + +You can specify multiple values separated by commas. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Sortby +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. + +You can sort by the following properties: + +- Name +- DisplayName +- City +- FirstName +- LastName +- Office + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SupervisoryReviewPolicy +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Get-UserBriefingConfig.md b/exchange/exchange-ps/exchange/Get-UserBriefingConfig.md new file mode 100644 index 0000000000..6c04f88148 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-UserBriefingConfig.md @@ -0,0 +1,93 @@ +--- +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 +ms.author: chrisda +--- + +# Get-UserBriefingConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-UserBriefingConfig cmdlet to get the current state of the Briefing email flag for the specified user. For more details about configuring the Briefing email, see [Configure Briefing email](https://learn.microsoft.com/Briefing/be-admin). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-UserBriefingConfig -Identity + [-ResultSize ] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Get-UserBriefingConfig -Identity lila@contoso.com +``` + +This example returns the Briefing configuration for the user lila@contoso.com. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Configure Briefing email](https://learn.microsoft.com/Briefing/be-admin) diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-UserPhoto.md b/exchange/exchange-ps/exchange/Get-UserPhoto.md similarity index 77% rename from exchange/exchange-ps/exchange/mailboxes/Get-UserPhoto.md rename to exchange/exchange-ps/exchange/Get-UserPhoto.md index ca1cf8f996..5314df112d 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Get-UserPhoto.md +++ b/exchange/exchange-ps/exchange/Get-UserPhoto.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-userphoto -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Get-UserPhoto ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. -Use the Get-UserPhoto cmdlet to view information about the user photos feature that allows users to associate a picture with their account. User photos appear in on-premises and cloud-based client applications, such as Outlook on the web, Lync, Skype for Business and SharePoint. +Use the Get-UserPhoto cmdlet to view information about the user photos feature that allows users to associate a picture with their account. User photos appear in client applications, such as Outlook, Microsoft Teams, and SharePoint. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +**Note**: In Microsoft 365, you can manage user photos in Microsoft Graph PowerShell. For instructions, see [Manage user photos in Microsoft Graph PowerShell](https://learn.microsoft.com/microsoft-365/admin/add-users/change-user-profile-photos#manage-user-photos-in-microsoft-graph-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -34,7 +35,8 @@ Get-UserPhoto [-Anr ] [-Preview] [-ReadFromDomainController] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ### Identity @@ -50,13 +52,14 @@ Get-UserPhoto [[-Identity] ] [-Preview] [-ReadFromDomainController] [-ResultSize ] - [-SortBy ] [] + [-SortBy ] + [] ``` ## DESCRIPTION The user photos feature allows users to associate a picture with their account. User photos are stored in the user's Active Directory account and in the root directory of the user's Exchange mailbox. The user photo feature must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user's photo. Otherwise, you get an error message saying the user photo doesn't exist for the specified users. Administrators use the Set-UserPhoto cmdlet or the Exchange admin center (EAC) to configure user photos. Users can upload, preview, and save a user photo to their account by using the Outlook on the web Options page. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,24 +79,47 @@ This example displays information about the user photo that was uploaded to Pila ## PARAMETERS +### -Identity +The Identity parameter specifies the user account. You can use any value that uniquely identifies the user account. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Anr 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) - - DisplayName - - FirstName - - LastName - - Alias ```yaml Type: String Parameter Sets: AnrSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -105,13 +131,13 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -121,8 +147,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -139,25 +163,22 @@ Accept wildcard characters: False ``` ### -Filter -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. +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. - Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -167,13 +188,13 @@ Accept wildcard characters: False ``` ### -GroupMailbox -The GroupMailbox switch is required to modify Office 365 groups. You don't need to specify a value with this switch. +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 +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -182,56 +203,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the user account. You can use any value that uniquely identifies the user account. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -244,18 +228,15 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -271,7 +252,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -289,7 +270,7 @@ A preview photo is a photo that was uploaded to the user's account, but wasn't s Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -299,7 +280,9 @@ Accept wildcard characters: False ``` ### -ReadFromDomainController -The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. +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. By default, the recipient scope is set to the domain that hosts your Exchange servers. @@ -307,7 +290,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -323,7 +306,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -335,7 +318,7 @@ Accept wildcard characters: False ### -SortBy 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 \,\... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. +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. You can sort by the Id property. @@ -343,7 +326,7 @@ You can sort by the Id property. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -357,12 +340,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Get-UserPrincipalNamesSuffix.md b/exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md similarity index 87% rename from exchange/exchange-ps/exchange/active-directory/Get-UserPrincipalNamesSuffix.md rename to exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md index 3fcd765f50..b9afdf3095 100644 --- a/exchange/exchange-ps/exchange/active-directory/Get-UserPrincipalNamesSuffix.md +++ b/exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-userprincipalnamessuffix +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-UserPrincipalNamesSuffix @@ -17,12 +16,13 @@ This cmdlet is available only in on-premises Exchange. Use the Get-UserPrincipalNamesSuffix cmdlet to view the user principal name (UPN) suffixes in the Active Directory forest. The UPN suffixes are created in Active Directory Domains and Trusts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-UserPrincipalNamesSuffix [-OrganizationalUnit ] [] +Get-UserPrincipalNamesSuffix [-OrganizationalUnit ] + [] ``` ## DESCRIPTION @@ -32,7 +32,7 @@ The default UPN is contained in the Canonical Name attribute on the Partitions c If you create user accounts by using Active Directory Users and Computers, every user must have a UPN. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,11 +49,8 @@ This example returns all UPN suffixes for the Active Directory forest. 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -74,12 +71,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md b/exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md new file mode 100644 index 0000000000..bbfd395ab1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md @@ -0,0 +1,120 @@ +--- +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 +ms.author: chrisda +--- + +# Get-VivaInsightsSettings + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +**Note**: This cmdlet is available only in version 2.0.5 or later of the module. + +Use the Get-VivaInsightsSettings cmdlet to check whether a user has access to features in Microsoft Viva Insights in Microsoft Teams. Only users with provisioned Exchange Online mailboxes can access features within the Viva Insights app in Teams. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-VivaInsightsSettings -Identity + [-Feature ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Teams Administrator + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Get-VivaInsightsSettings -Identity roy@contoso.onmicrosoft.com + +UserId : roy@contoso.onmicrosoft.com +IsInsightsHeadspaceEnabled : True +``` + +This example shows the configuration of Microsoft Viva Insights in Microsoft Teams for the user roy@contoso.onmicrosoft.com. The output of the command shows that the features of Headspace are available to Roy. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Feature +The Feature parameter filters the results by the specified Microsoft Viva Insights feature. Valid values are: + +- Headspace: Represents all features of Headspace. +- MeetingEffectivenessSurvey: This value is available only in version 2.0.6-Preview2 of the module as part of a Private Preview. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-VivaModuleFeature.md b/exchange/exchange-ps/exchange/Get-VivaModuleFeature.md new file mode 100644 index 0000000000..b2787501f8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-VivaModuleFeature.md @@ -0,0 +1,123 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-VivaModuleFeature + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-VivaModuleFeature cmdlet to view the features in a Viva module that support feature access controls. This cmdlet provides details about the features, including the feature identifiers and descriptions. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-VivaModuleFeature -ModuleId + [[-FeatureId] ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +Use the Get-VivaModuleFeature cmdlet to view the features in a Viva module that support feature access controls. + +You can view all features in a particular Viva module that support feature access controls. To view a specific feature, you can include the FeatureId parameter. + +You need to use the Connect-ExchangeOnline cmdlet to authenticate. + +This cmdlet requires the .NET Framework 4.7.2 or later. + +## EXAMPLES + +### Example 1 +```powershell +Get-VivaModuleFeature -ModuleId VivaInsights +``` + +This example returns all features in Viva Insights that support feature access controls. + +### Example 2 +```powershell +Get-VivaModuleFeature -ModuleId VivaInsights -FeatureId Reflection +``` + +This example returns the details of the Reflection feature in Viva Insights. + +## PARAMETERS + +### -ModuleId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FeatureId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Positional +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Exchange PowerShell](https://learn.microsoft.com/powershell/module/exchange) + +[About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2) + +[Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids) diff --git a/exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md b/exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md new file mode 100644 index 0000000000..8fed8e655e --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md @@ -0,0 +1,145 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-VivaModuleFeatureEnablement + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-VivaModuleFeatureEnablement cmdlet to view whether or not a feature in a Viva module is enabled for a specific user or group. Whether or not the feature is enabled is referred to as the feature's "enablement state". The enablement state returned by this cmdlet is based on the access policies set by the admin. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-VivaModuleFeatureEnablement -FeatureId -Identity -ModuleId + [-ResultSize ] + [] +``` + +## DESCRIPTION +Use the Get-VivaModuleFeatureEnablement cmdlet to view whether or not a feature in a Viva module is enabled for a specific user or group. + +You need to use the Connect-ExchangeOnline cmdlet to authenticate. + +This cmdlet requires the .NET Framework 4.7.2 or later. + +Currently, you need to be a member of the Global Administrators role to run this cmdlet. + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Get-VivaModuleFeatureEnablement -ModuleId VivaInsights -FeatureId Reflection -Identity user@contoso.com +``` + +This example returns the enablement state of the Reflection feature in Viva Insights for the **user@contoso.com** user. + +### Example 2 +```powershell +Get-VivaModuleFeatureEnablement -ModuleId VivaInsights -FeatureId Reflection -Identity group@contoso.com +``` + +This example returns the enablement state of the Reflection feature in Viva Insights for the **group@contoso.com** group. + +## PARAMETERS + +### -FeatureId +The FeatureId parameter specifies the feature in the Viva module. + +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: (All) +Aliases: +Type: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter specifies the user principal name (UPN) of the user or the SMTP address (email address) of the group that you want to view the feature enablement status of. + +[Mail-enabled Microsoft Entra groups](https://docs.microsoft.com/graph/api/resources/groups-overview#group-types-in-azure-ad-and-microsoft-graph) are supported. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Type: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModuleId +The ModuleId parameter specifies the Viva module. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Type: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Type: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Exchange PowerShell](https://learn.microsoft.com/powershell/module/exchange) + +[About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2) + +[Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids) diff --git a/exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md new file mode 100644 index 0000000000..1e4a57e8a1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md @@ -0,0 +1,204 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-VivaModuleFeaturePolicy + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-VivaModuleFeaturePolicy cmdlet to view the access policies for a specified feature in a Viva module in Viva. Policies are used to restrict or grant access to the specified feature for specific users, groups, or the entire tenant. This cmdlet provides details about the policies, including the policy's identifier, name, and creation date. The cmdlet can filter policies based on MemberIds, allowing admins to view policies specific to certain users or groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### FeaturePolicy +``` +Get-VivaModuleFeaturePolicy -FeatureId -ModuleId [[-PolicyId] ] + [-ResultSize ] + [] +``` + +### FeaturePolicyWithMembers +``` +Get-VivaModuleFeaturePolicy -ModuleId [[-FeatureId] ] [[-MemberIds] ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +Use the Get-VivaModuleFeaturePolicy cmdlet to view the access policies for a specified feature in a Viva module in Viva. + +You can view all policies for a specified feature in a Viva module in Viva. To view a specific policy, you can include the PolicyId parameter. + +The cmdlet can filter policies based on MemberIds, allowing admins to view policies specific to certain users or groups. + +You need to use the Connect-ExchangeOnline cmdlet to authenticate. + +This cmdlet requires the .NET Framework 4.7.2 or later. + +Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. + +To learn more about assigned roles at the feature level, see [Features Available for Feature Access Management](https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Get-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection +``` + +This example returns details about all the policies added for the Reflection feature in Viva Insights. + +### Example 2 +```powershell +Get-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -PolicyId 3db38dfa-02a3-4039-b33a-42b0b3da029b +``` + +This example returns details about a specific policy added for the Reflection feature in Viva Insights. + +### Example 3 +```powershell +Get-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -MemberIds user1@contoso.com +``` + +This example returns details about the policies for the Reflection feature in Viva Insights that apply to the user with the email user1@contoso.com. + +### Example 4 +```powershell +Get-VivaModuleFeaturePolicy -ModuleId * -FeatureId * -MemberIds user1@contoso.com,group1@contoso.com +``` + +This example returns details about the policies for all features across all Viva modules that apply to the user with the email user1@contoso.com and the group with the email group1@contoso.com. + +## PARAMETERS + +### -FeatureId +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 +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: String +Parameter Sets: FeaturePolicyWithMembers +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -ModuleId +The ModuleId parameter specifies the Viva module of the feature policies that you want to view. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyId +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. + +```yaml +Type: String +Parameter Sets: FeaturePolicy +Aliases: +Applicable: Exchange Online + +Required: False +Position: Positional +Default value: None +Accept pipeline input: False +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. + +You can provide up to three member IDs. Use the \* character to specify all modules or features. + +```yaml +Type: String[] +Parameter Sets: FeaturePolicyWithMembers +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Exchange PowerShell](https://learn.microsoft.com/powershell/module/exchange) + +[About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2) + +[Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids) diff --git a/exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md new file mode 100644 index 0000000000..22defddf64 --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md @@ -0,0 +1,94 @@ +--- +external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml +Module Name: ExchangeOnlineManagement +online version: https://learn.microsoft.com/powershell/module/exchange/get-vivaorginsightsdelegatedrole +title: Get-VivaOrgInsightsDelegatedRole +schema: 2.0.0 +author: chrisda +ms.author: chrisda +ms.reviewer: +--- + +# Get-VivaOrgInsightsDelegatedRole + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.7.1 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Get-VivaOrgInsightsDelegatedRole cmdlet to view all delegates of the specified delegator. Delegate accounts can view organizational insights like the specified delegator. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-VivaOrgInsightsDelegatedRole -Delegator + [-ResultSize ] + [] +``` + +## DESCRIPTION +Typically, you use this cmdlet with the Remove-VivaOrgInsightsDelegatedRole cmdlet to find the Microsoft Entra ObjectId values of the delegate accounts. + +To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: + +- Global Administrator +- Insights Administrator + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Get-VivaOrgInsightsDelegatedRole -Delegator 043f6d38-378b-7dcd-7cd8-c1a901881fa9 +``` + +This example filters the results by the specified delegator. + +## PARAMETERS + +### -Delegator +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Get-WebServicesVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Get-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md index 9c68ffe958..1345ae232f 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-webservicesvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-WebServicesVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-WebServicesVirtualDirectory cmdlet to view Exchange Web Services (EWS) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Get-WebServicesVirtualDirectory -Server [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ### Identity @@ -34,7 +34,8 @@ Get-WebServicesVirtualDirectory -Server Get-WebServicesVirtualDirectory [[-Identity] ] [-ADPropertiesOnly] [-DomainController ] - [-ShowMailboxVirtualDirectories] [] + [-ShowMailboxVirtualDirectories] + [] ``` ## DESCRIPTION @@ -42,13 +43,13 @@ The Get-WebServicesVirtualDirectory cmdlet can be run on a local server or run r The Get-WebServicesVirtualDirectory cmdlet can be run on any server that has the Exchange administration tools installed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-WebServicesVirtualDirectory -ServerMBX01 +Get-WebServicesVirtualDirectory -Server MBX01 ``` This example returns a summary list of all EWS virtual directories on the server named MBX01. @@ -72,13 +73,11 @@ This example returns a summary list of all virtual directories in the client acc ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. You can't use the Identity and Server parameters in the same command. @@ -99,11 +98,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't use the Server and Identity parameters in the same command. @@ -122,7 +118,9 @@ Accept wildcard characters: False ``` ### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. +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. ```yaml Type: SwitchParameter @@ -178,12 +176,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Get-X400AuthoritativeDomain.md b/exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md similarity index 85% rename from exchange/exchange-ps/exchange/mail-flow/Get-X400AuthoritativeDomain.md rename to exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md index 666de50552..3be7ea0728 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Get-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-x400authoritativedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Get-X400AuthoritativeDomain @@ -15,19 +14,20 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Get-X400AuthoritativeDomain cmdlet to view the configuration information for the X.400 authoritative domains configured in your organization. For more information about how to configure an X.400 authoritative domain, see [Set-X400AuthoritativeDomain](https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-x400authoritativedomain). +Use the Get-X400AuthoritativeDomain cmdlet to view the configuration information for the X.400 authoritative domains configured in your organization. For more information about how to configure an X.400 authoritative domain, see [Set-X400AuthoritativeDomain](https://learn.microsoft.com/powershell/module/exchange/set-x400authoritativedomain). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Get-X400AuthoritativeDomain [[-Identity] ] [-DomainController ] +Get-X400AuthoritativeDomain [[-Identity] ] + [-DomainController ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -40,37 +40,37 @@ This example displays detailed information about the X.400 authoritative domain ## PARAMETERS -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. +### -Identity +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: Fqdn +Type: X400AuthoritativeDomainIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies a string value for the X.400 authoritative domain. Enter either the GUID or the name of the remote domain. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: X400AuthoritativeDomainIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -79,12 +79,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md new file mode 100644 index 0000000000..2af5f1721a --- /dev/null +++ b/exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md @@ -0,0 +1,86 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Get-eDiscoveryCaseAdmin + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Get-eDiscoveryCaseAdmin cmdlet to view eDiscovery Administrators in the Microsoft Purview compliance portal. An eDiscovery Administrator is member of the eDiscovery Manager role group who can also view and access all eDiscovery cases in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Get-eDiscoveryCaseAdmin [-DomainController ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +To add or remove individual eDiscovery Administrators, use the Add-eDiscoveryCaseAdmin and Remove-eDiscoveryCaseAdmin cmdlets. To replace all existing eDiscovery Administrators, use the Update-eDiscoveryCaseAdmin cmdlet. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-eDiscoveryCaseAdmin +``` + +This example returns a summary list of all eDiscovery Administrators. + +## PARAMETERS + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Import-DlpPolicyCollection.md b/exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md similarity index 77% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Import-DlpPolicyCollection.md rename to exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md index 4241b02ef2..bdec677fd8 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Import-DlpPolicyCollection.md +++ b/exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md @@ -1,29 +1,34 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/import-dlppolicycollection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Import-DlpPolicyCollection ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). -Use the Import-DlpPolicyCollection cmdlet to import data loss prevention (DLP) policy collections into your organization. +This cmdlet is functional only in on-premises Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the Import-DlpPolicyCollection cmdlet to import data loss prevention (DLP) policy collections that are based on transport rules (mail flow rules) into your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Import-DlpPolicyCollection [-FileData] [[-Identity] ] [-Confirm] - [-DomainController ] [-Force] [-WhatIf] [] +Import-DlpPolicyCollection [[-Identity] ] [-FileData] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,23 +36,39 @@ The Import-DlpPolicyCollection cmdlet imports all the settings of the DLP polici Importing a DLP policy collection from an XML file removes or overwrites all pre-existing DLP policies that were defined in your organization. Make sure that you have a backup of your current DLP policy collection before you import and overwrite your current DLP policies. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Import-DlpPolicyCollection -FileData ([Byte[]]$(Get-Content -Path " C:\My Documents\DLP Backup.xml " -Encoding Byte -ReadCount 0)) +Import-DlpPolicyCollection -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\DLP Backup.xml')) ``` This example imports the DLP policy collection in the file C:\\My Documents\\DLP Backup.xml. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -FileData 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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\" -ReadCount 0\)\). +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[] @@ -65,8 +86,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -83,8 +103,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -101,7 +119,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -116,22 +136,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -153,12 +157,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Import-DlpPolicyTemplate.md b/exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md similarity index 77% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Import-DlpPolicyTemplate.md rename to exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md index 45cd2b5e7c..41752441f8 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Import-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/import-dlppolicytemplate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Import-DlpPolicyTemplate @@ -15,24 +14,27 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Import-DlpPolicyTemplate cmdlet to import a data loss prevention (DLP) policy template file into your Exchange organization. +Use the Import-DlpPolicyTemplate cmdlet to import data loss prevention (DLP) policy template files that are based on transport rules (mail flow rules) into your Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Import-DlpPolicyTemplate [-FileData] [-Confirm] [-WhatIf] [] +Import-DlpPolicyTemplate [-FileData] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Import-DlpPolicyTemplate -FileData ([Byte[]]$(Get-Content -Path "C:\My Documents\External DLP Policy Template.xml" -Encoding Byte -ReadCount 0)) +Import-DlpPolicyTemplate -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\External DLP Policy Template.xml')) ``` This example imports the DLP policy template file C:\\My Documents\\External DLP Policy Template.xml. @@ -42,7 +44,7 @@ This example imports the DLP policy template file C:\\My Documents\\External DLP ### -FileData 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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\" -ReadCount 0\)\). +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[] @@ -60,8 +62,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -98,12 +99,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Import-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Import-ExchangeCertificate.md new file mode 100644 index 0000000000..f9175f98ff --- /dev/null +++ b/exchange/exchange-ps/exchange/Import-ExchangeCertificate.md @@ -0,0 +1,317 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Import-ExchangeCertificate + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Import-ExchangeCertificate cmdlet to import certificates on Exchange servers. You use this cmdlet to install certificates that were exported from other servers, and to complete pending certification requests (also known as certificate signing requests or CSRs) from certification authorities (CAs). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### FileData +``` +Import-ExchangeCertificate -FileData + [-Confirm] + [-DomainController ] + [-FriendlyName ] + [-Password ] + [-PrivateKeyExportable ] + [-Server ] + [-WhatIf] + [] +``` + +### FileName +``` +Import-ExchangeCertificate -Instance + [-Confirm] + [-DomainController ] + [-FriendlyName ] + [-Password ] + [-PrivateKeyExportable ] + [-Server ] + [-WhatIf] + [] +``` + +### Instance +``` +Import-ExchangeCertificate -FileName + [-Confirm] + [-DomainController ] + [-FriendlyName ] + [-Password ] + [-PrivateKeyExportable ] + [-Server ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can use the Import-ExchangeCertificate cmdlet to import the following types of certificate files on an Exchange server: + +- APKCS #7 certificate or chain of certificates file (.p7b or .p7c) that was issued by a certification authority (CA). PKCS #7 is the Cryptographic Message Syntax Standard, a syntax used for digitally signing or encrypting data using public key cryptography, including certificates. For more information, see [PKCS #7 Cryptographic Messaging Syntax Concepts](https://learn.microsoft.com/windows/win32/seccrypto/pkcs--7-concepts). +- A PKCS #12 certificate file (.cer, .crt, .der, .p12, or .pfx) that contains the private key. PKCS #12 is the Personal Information Exchange Syntax Standard, a file format used to store certificates with corresponding private keys that are protected by a password. For more information, see [PKCS #12: Personal Information Exchange Syntax v1.1](https://tools.ietf.org/html/rfc7292). + +After you import a certificate on an Exchange server, you need to assign the certificate to one or more Exchange services by using the Enable-ExchangeCertificate cmdlet. + +There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://learn.microsoft.com/Exchange/architecture/client-access/certificates). + +Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Import-ExchangeCertificate -Server Mailbox01 -FileName "\\FileServer01\Data\Exported Fabrikam Cert.pfx" -Password (Get-Credential).password +``` + +In **Exchange 2013**, this example imports the certificate from the PKCS #12 file from \\\\FileServer01\\Data\\Exported Fabrikam Cert.pfx to the Exchange server named Mailbox01. This file requires the password of the file. This certificate could have been exported from another server or issued by a certification authority. + +To export the certificate in Exchange 2016 or Exchange 2019, use the FileData parameter as described in Example 2. + +### Example 2 +```powershell +Import-ExchangeCertificate -Server Mailbox01 -FileData ([System.IO.File]::ReadAllBytes('\\FileServer01\Data\Exported Fabrikam Cert.pfx')) -Password (Get-Credential).password +``` + +This example imports the same certificate file from Example 1. This method is required in Exchange 2016 and Exchange 2019 because the FileName parameter is not available. + +### Example 3 +```powershell +Import-ExchangeCertificate -FileData ([System.IO.File]::ReadAllBytes('C:\Certificates\Fabrikam IssuedCert.p7b')) +``` + +This example imports a chain of certificates from the PKCS #7 file C:\\Certificates\\Fabrikam IssuedCert.p7b on the local Exchange server. + +## PARAMETERS + +### -FileData +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`). + +You can use a local path if the certificate file is located on the Exchange server where you're running the command, and this is the same server where you want to install the certificate. Otherwise, use a UNC path (`\\Server\Share`). + +When you use this parameter to import PKCS #7 text certificate files, these files contain contain: -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- or -----BEGIN PKCS7----- and -----END PKCS7----- and have .p7b or .p7c filename extensions. + +If the value contains spaces, enclose the value in quotation marks ("). + +```yaml +Type: Byte[] +Parameter Sets: FileData +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileName +**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. + +The FileName parameter specifies the certificate file that you want to import. Typically, you use this parameter for PKCS #12 binary certificate files that have .cer, .crt, .der, .p12, or .pfx filename extensions. This type of binary certificate file is protected by a password when the file contains the private key or chain of trust. + +You can use a local path if the certificate file is located on the Exchange server where you're running the command, and this is the same server where you want to install the certificate. Otherwise, use a UNC path (`\\Server\Share`). + +If the value contains spaces, enclose the value in quotation marks ("). + +```yaml +Type: String +Parameter Sets: Instance +Aliases: +Applicable: Exchange Server 2013 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FriendlyName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Password +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: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +```yaml +Type: SecureString +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivateKeyExportable +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. +- $false: The private key isn't exportable, so you can't export the certificate from this server. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Server +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +If you don't use this parameter, the command is run on the local server. + +```yaml +Type: ServerIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Import-FilePlanProperty.md b/exchange/exchange-ps/exchange/Import-FilePlanProperty.md new file mode 100644 index 0000000000..0a64f7f630 --- /dev/null +++ b/exchange/exchange-ps/exchange/Import-FilePlanProperty.md @@ -0,0 +1,154 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/import-fileplanproperty +applicable: Security & Compliance +title: Import-FilePlanProperty +schema: 2.0.0 +--- + +# Import-FilePlanProperty + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Import-FilePlanProperty cmdlet to import file plan properties. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Import-FilePlanProperty [-RawCsv] + [-Confirm] + [-DomainController ] + [-Force] + [-ValidateOnly] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Import-FilePlanProperty -RawCsv "C:\Data\CSV Import.csv" +``` + +This example imports the specified CSV file. + +## PARAMETERS + +### -RawCsv +The RawCsv parameter specifies the CSV file to import. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidateOnly +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Import-JournalRuleCollection.md b/exchange/exchange-ps/exchange/Import-JournalRuleCollection.md new file mode 100644 index 0000000000..535e6e67f0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Import-JournalRuleCollection.md @@ -0,0 +1,151 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Import-JournalRuleCollection + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Import-JournalRuleCollection cmdlet to import journal rules from an XML file. You can import a journal rule collection you previously exported as a backup, or import rules you exported from an older version of Exchange. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Import-JournalRuleCollection [[-Identity] ] [-FileData] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Import-JournalRuleCollection cmdlet imports a journal rule collection you previously exported. + +Importing a journal rule collection from an XML file removes or overwrites all pre-existing journal rules in your organization. Make sure that you have a backup of your current journal rule collection before you import and overwrite your current journal rules. + +For more information about how to export a journal rule collection to an XML file, see [Export-JournalRuleCollection](https://learn.microsoft.com/powershell/module/exchange/export-journalrulecollection). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Import-JournalRuleCollection -FileData ([System.IO.File]::ReadAllBytes('C:\JournalRules\ExportedJournalRules.xml')) +``` + +This example imports journal rules from the XML file named ExportedJournalRules.xml in the C:\\JournalRules folder. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Import-RecipientDataProperty.md b/exchange/exchange-ps/exchange/Import-RecipientDataProperty.md new file mode 100644 index 0000000000..3c8ed062fd --- /dev/null +++ b/exchange/exchange-ps/exchange/Import-RecipientDataProperty.md @@ -0,0 +1,211 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Import-RecipientDataProperty + +## SYNOPSIS +Use the Import-RecipientDataProperty cmdlet to add a picture or a spoken name audio file to a mailbox or mail contact. + +**Note**: Profile cards across Microsoft apps and services don't support imported pictures for mail contacts. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### ImportPicture +``` +Import-RecipientDataProperty [-Identity] -FileData + [-Picture] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +### ImportSpokenName +``` +Import-RecipientDataProperty [-Identity] -FileData + [-SpokenName] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Import-RecipientDataProperty -Identity "Tony Smith" -SpokenName -FileData ([System.IO.File]::ReadAllBytes('M:\AudioFiles\TonySmith.wma')) +``` + +This example imports the audio file for Tony Smith's spoken name. + +### Example 2 +```powershell +Import-RecipientDataProperty -Identity Ayla -Picture -FileData ([System.IO.File]::ReadAllBytes('M:\Employee Photos\AylaKol.jpg')) +``` + +This example imports the picture file for Ayla Kol. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -FileData +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`). + +To import a picture, use the Picture switch. A valid picture file is JPEG and less than 10 kilobytes (KB). + +To import a spoken name, use the SpokenName switch. A valid spoken name file is WMA 9 and less than 32 KB. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Picture +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpokenName +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Import-TransportRuleCollection.md b/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md new file mode 100644 index 0000000000..30fae12016 --- /dev/null +++ b/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md @@ -0,0 +1,180 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Import-TransportRuleCollection + +## SYNOPSIS +This cmdlet is functional only in on-premises Exchange. + +Use the Import-TransportRuleCollection cmdlet to import a transport rule collection. You can import a rule collection you previously exported as a backup, or import rules that you've exported from an older version of Exchange. + +**Note**: For replacement import functionality in Exchange Online using a PowerShell script, see [Import or export a mail flow rule collection in Exchange Online](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/manage-mail-flow-rules#import-or-export-a-mail-flow-rule-collection-in-exchange-online). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Import-TransportRuleCollection [[-Identity] ] [-FileData] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +Importing a transport rule collection from an XML file removes or overwrites all pre-existing transport rules that were defined in your organization. Make sure that you have a backup of your current transport rule collection before you import and overwrite your current transport rules. + +For information about how to export a transport rule collection to an XML file, see [Export-TransportRuleCollection](https://learn.microsoft.com/powershell/module/exchange/export-transportrulecollection). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Import-TransportRuleCollection -FileData ([System.IO.File]::ReadAllBytes('C:\TransportRules\ExportedRules.xml')) +``` + +This example imports a transport rule collection from the XML file named ExportedRules.xml in the C:\\TransportRules folder. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -FileData +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`). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/unified-messaging/Import-UMPrompt.md b/exchange/exchange-ps/exchange/Import-UMPrompt.md similarity index 77% rename from exchange/exchange-ps/exchange/unified-messaging/Import-UMPrompt.md rename to exchange/exchange-ps/exchange/Import-UMPrompt.md index df02034546..5f34ab73ab 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Import-UMPrompt.md +++ b/exchange/exchange-ps/exchange/Import-UMPrompt.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/import-umprompt -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Import-UMPrompt ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Import-UMPrompt cmdlet to copy or upload a custom audio file to be used by Unified Messaging (UM) dial plans and auto attendants. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Import-UMPrompt -PromptFileData -PromptFileName -UMDialPlan [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UploadAutoAttendantPrompts @@ -34,7 +34,8 @@ Import-UMPrompt -PromptFileData -PromptFileName -UMDialPlan -PromptFileName -UMAutoAttendant [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UploadAutoAttendantPromptsStream @@ -42,7 +43,8 @@ Import-UMPrompt -PromptFileData -PromptFileName -UMAutoAttenda Import-UMPrompt -PromptFileName -PromptFileStream -UMAutoAttendant [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UploadDialPlanPromptsStream @@ -50,7 +52,8 @@ Import-UMPrompt -PromptFileName -PromptFileStream -UMAutoAtten Import-UMPrompt -PromptFileName -PromptFileStream -UMDialPlan [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -58,41 +61,43 @@ The Import-UMPrompt cmdlet imports custom greeting audio files into UM dial plan After this task is completed, the custom audio file can be used by a UM dial plan or auto attendant. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -[byte[]]$c = Get-content -Path "d:\UMPrompts\welcomegreeting.wav" -Encoding Byte -ReadCount 0; Import-UMPrompt -UMDialPlan MyUMDialPlan -PromptFileName "welcomegreeting.wav" -PromptFileData $c +Import-UMPrompt -UMDialPlan MyUMDialPlan -PromptFileName "welcomegreeting.wav" -PromptFileData ([System.IO.File]::ReadAllBytes('D:\UMPrompts\welcomegreeting.wav')) ``` -This example imports the welcome greeting file welcomegreeting.wav from d:\\UMPrompts into the UM dial plan MyUMDialPlan. +This example imports the welcome greeting file welcomegreeting.wav from D:\\UMPrompts into the UM dial plan MyUMDialPlan. ### Example 2 ```powershell -[byte[]]$c = Get-content -Path "d:\UMPrompts\welcomegreeting.wav" -Encoding Byte -ReadCount 0; Import-UMPrompt -UMAutoAttendant MyUMAutoAttendant -PromptFileName "welcomegreeting.wav" -PromptFileData $c +Import-UMPrompt -UMAutoAttendant MyUMAutoAttendant -PromptFileName "welcomegreeting.wav" -PromptFileData ([System.IO.File]::ReadAllBytes('D:\UMPrompts\welcomegreeting.wav')) ``` -This example imports the welcome greeting file welcomegreeting.wav from d:\\UMPrompts into the UM auto attendant MyUMAutoAttendant. +This example imports the welcome greeting file welcomegreeting.wav from D:\\UMPrompts into the UM auto attendant MyUMAutoAttendant. ### Example 3 ```powershell -[byte[]]$c = Get-content -Path "d:\UMPrompts\AfterHoursWelcomeGreeting.wav" -Encoding Byte -ReadCount 0; Import-UMPrompt -UMAutoAttendant MyUMAutoAttendant -PromptFileName "AfterHoursWelcomeGreeting.wav" -PromptFileData $c +Import-UMPrompt -UMAutoAttendant MyUMAutoAttendant -PromptFileName "AfterHoursWelcomeGreeting.wav" -PromptFileData ([System.IO.File]::ReadAllBytes('D:\UMPrompts\AfterHoursWelcomeGreeting.wav')) ``` -This example imports the welcome greeting file AfterHoursWelcomeGreeting.wav from d:\\UMPrompts into the UM auto attendant MyUMAutoAttendant. +This example imports the welcome greeting file AfterHoursWelcomeGreeting.wav from D:\\UMPrompts into the UM auto attendant MyUMAutoAttendant. ## PARAMETERS ### -PromptFileData 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`). + ```yaml Type: Byte[] Parameter Sets: UploadDialPlanPrompts, UploadAutoAttendantPrompts Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -108,7 +113,7 @@ The PromptFileName parameter specifies the name of the custom prompt. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -124,7 +129,7 @@ The PromptFileStream parameter specifies whether the audio file will be uploaded Type: Stream Parameter Sets: UploadAutoAttendantPromptsStream, UploadDialPlanPromptsStream Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -140,7 +145,7 @@ The UMAutoAttendant parameter specifies the UM auto attendant ID. This parameter Type: UMAutoAttendantIdParameter Parameter Sets: UploadAutoAttendantPrompts, UploadAutoAttendantPromptsStream Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -156,7 +161,7 @@ The UMDialPlan parameter specifies the UM dial plan ID. This parameter specifies Type: UMDialPlanIdParameter Parameter Sets: UploadDialPlanPrompts, UploadDialPlanPromptsStream Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -168,15 +173,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -186,15 +190,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -210,7 +212,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -224,12 +226,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Install-TransportAgent.md b/exchange/exchange-ps/exchange/Install-TransportAgent.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Install-TransportAgent.md rename to exchange/exchange-ps/exchange/Install-TransportAgent.md index 3356d0c1a6..9e51b2aaa8 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Install-TransportAgent.md +++ b/exchange/exchange-ps/exchange/Install-TransportAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/install-transportagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Install-TransportAgent @@ -17,21 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Install-TransportAgent cmdlet to register transport agents on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Install-TransportAgent [-Name] -AssemblyPath -TransportAgentFactory [-Confirm] - [-DomainController ] [-WhatIf] - [-TransportService ] [-EscalationTeam ] +Install-TransportAgent [-Name] -AssemblyPath -TransportAgentFactory + [-Confirm] + [-DomainController ] + [-TransportService ] + [-WhatIf] [] ``` ## DESCRIPTION Transport agents have full access to all email messages that they encounter. Exchange puts no restrictions on a transport agent's behavior. Transport agents that are unstable or contain security flaws may affect the stability and security of Exchange. Therefore, you need to only install transport agents that you fully trust and that have been fully tested. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,8 +45,8 @@ This example shows how a fictitious application named Test App is installed in t ## PARAMETERS -### -AssemblyPath -The AssemblyPath parameter specifies the location of the transport agent Microsoft.NET assembly. Universal Naming Convention (UNC) file paths can't be used. +### -Name +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 @@ -54,14 +55,14 @@ Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies the display name of the transport agent to be installed. The length of the name can't exceed 64 characters. +### -AssemblyPath +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 @@ -70,7 +71,7 @@ Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -95,8 +96,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,33 +130,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -TransportService 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. - - MailboxSubmission for the Mailbox Transport Submission service on Mailbox servers. - - MailboxDelivery for the Mailbox Transport Delivery service on Mailbox servers. - - FrontEnd for the Front End Transport service on Mailbox servers. - - Edge on Edge Transport servers. ```yaml @@ -172,14 +152,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -EscalationTeam -This parameter is reserved for internal Microsoft use. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: String +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -193,12 +173,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md b/exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md new file mode 100644 index 0000000000..dfc3b902a4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md @@ -0,0 +1,134 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Install-UnifiedCompliancePrerequisite + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Install-UnifiedCompliancePrerequisite cmdlet to view, create, or configure the Compliance Policy Center in Microsoft SharePoint. The Compliance Policy Center is a site collection that's used by the Microsoft Purview compliance portal to store preservation policies that act on content in SharePoint sites. + +Typically, you don't need to run this cmdlet. You use this cmdlet for troubleshooting and diagnostics. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Initialize +``` +Install-UnifiedCompliancePrerequisite [-ForceInitialize] + [-PolicyCenterSiteOwner ] + [] +``` + +### LoadOnly +``` +Install-UnifiedCompliancePrerequisite [-LoadOnly] + [] +``` + +## DESCRIPTION +This cmdlet returns the following information about the Compliance Policy Center: + +- SharepointRootSiteUrl: This value is typically `https://.sharepoint.com/`. +- SharepointTenantAdminUrl: This value uses the format `https://-admin.sharepoint.com/`. +- SharepointSuccessInitializedUtc: The time that the Compliance Policy Center was last initialized in coordinated universal time (UTC). +- SharepointPolicyCenterSiteUrl: This value is typically `https://.sharepoint.com/sites/compliancepolicycenter`. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Install-UnifiedCompliancePrerequisite +``` + +This example creates the Compliance Policy Center in SharePoint. If it has already been created, the command displays the current configuration information. + +### Example 2 +```powershell +Install-UnifiedCompliancePrerequisite -LoadOnly +``` + +This example loads the Compliance Policy Center using the current settings. + +### Example 3 +```powershell +Install-UnifiedCompliancePrerequisite -ForceInitialize +``` + +This example recreates the Compliance Policy Center, even if the site has already been created. + +## PARAMETERS + +### -ForceInitialize +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Initialize +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LoadOnly +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. + +```yaml +Type: SwitchParameter +Parameter Sets: LoadOnly +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyCenterSiteOwner +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Invoke-ComplianceSearchActionStep.md b/exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md similarity index 75% rename from exchange/exchange-ps/exchange/policy-and-compliance-content-search/Invoke-ComplianceSearchActionStep.md rename to exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md index 8a0191e881..d208ed10b8 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Invoke-ComplianceSearchActionStep.md +++ b/exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/invoke-compliancesearchactionstep -applicable: Office 365 Security & Compliance Center +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 ms.author: chrisda ms.reviewer: -monikerRange: "o365scc-ps" --- # Invoke-ComplianceSearchActionStep @@ -17,14 +16,12 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. This cmdlet is reserved for internal Microsoft use. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Invoke-ComplianceSearchActionStep [[-Identity] ] - -Parameters - -Step +Invoke-ComplianceSearchActionStep [[-Identity] ] -Parameters -Step [] ``` @@ -49,7 +46,7 @@ This cmdlet is reserved for internal Microsoft use. Type: ComplianceSearchActionIdParameter Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: False Position: 1 @@ -65,7 +62,7 @@ This cmdlet is reserved for internal Microsoft use. Type: PSObject Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: True Position: Named @@ -81,7 +78,7 @@ This cmdlet is reserved for internal Microsoft use. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: True Position: Named @@ -95,12 +92,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md b/exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md new file mode 100644 index 0000000000..af2ca95201 --- /dev/null +++ b/exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md @@ -0,0 +1,248 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Invoke-ComplianceSecurityFilterAction + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Invoke-ComplianceSecurityFilterAction cmdlet to view and set compliance boundaries for Microsoft OneDrive sites in cloud-based organizations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Invoke-ComplianceSecurityFilterAction [-Action] [[-EmailAddress] ] [-PropertyName] [[-PropertyValue] ] [-SiteUrl] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +This cmdlet is useful in scenarios where the OneDrive site has fallen out of the compliance boundary due to a departed user and a corresponding inactive mailbox. + +To use this cmdlet in Security & Compliance PowerShell, you need to be a member of the Compliance Administrator role group. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Invoke-ComplianceSecurityFilterAction -Action GetStatus -PropertyName CustomAttribute1 -SiteUrl https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx + +SiteUrlOrEmailAddress : https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx +BoundaryType : UserMailbox +BoundaryInstruction : Set via Set-Mailbox +BoundaryObjectId : SPO_f82ace6e-817e-4752-8917-67164dabde98@SPO_775ea11f-a2af-7821-b04c-9848e903ce47 +BoundaryStatus : Success +BoundaryProperty : CustomAttribute1 +BoundaryPropertyValue : +``` + +This example returns the status of a OneDrive site to indicate it's associated to a user mailbox and the CustomAttribute1 property isn't currently set. + +### Example 2 +```powershell +PS C:\> Invoke-ComplianceSecurityFi1terAction -Action GetStatus -PropertyName "CustomAttribute3" -EmailAddress "nina@contoso.onmicrosoft.com" + +SiteUrlOrEmailAddress : nina@contoso.onmicrosoft.com +BoundaryType : UserMailbox +BoundaryInstruction : Set via Set-Mailbox +BoundaryObjectId : nina@contoso.onmicrosoft.com +BoundaryStatus : Success +BoundaryProperty : CustomAttribute3 +BoundaryPropertyVa1ue : +``` + +This example returns the status of a mailbox to indicate the mailbox is inactive, and the CustomAttribute3 property isn't currently set. + +### Example 3 +```powershell +PS C:\> Invoke-ComplianceSecurityFi1terAction -Action GetStatus -PropertyName "CustomAttribute3" -EmailAddress "zhexuan@contoso.onmicrosoft.com" + +SiteUrlOrEmailAddress : zhexuan@contoso.onmicrosoft.com +BoundaryType : InactiveMailbox +BoundaryInstruction : Set via Invoke-ComplianceSecurityFiIterAction -Set +BoundaryObjectId : zhexuan@contoso.onmicrosoft.com +BoundaryStatus : Success +BoundaryProperty : CustomAttribute3 +BoundaryPropertyVa1ue : test33 +``` + +This example returns the status of a mailbox to indicate the mailbox is inactive, and the CustomAttribute3 property is currently set to test33. + +### Example 4 +```powershell +Invoke-ComplianceSecurityFilterAction -Action Set -PropertyName CustomAttribute1 -PropertyValue "Research and Development" -SiteUrl https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx +``` + +This example sets the boundary of the specified OneDrive site for a user who left the company. + +### Example 5 +```powershell +PS C:\> Invoke-ComplianceSecurityFiIterAction -Action Set -PropertyName "CustomAttribute3" -PropertyValue "ProjectX" -EmailAddress "zhexuan@contoso.onmicrosoft.com" + +Set action succeeded, please use GetStatus to check the result. + +PS C:\> Invoke-ComplianceSecurityFiIterAction -Action GetStatus -PropertyName "CustomAttribute3" -EmailAddress "zhexuan@contoso.onmicrosoft.com" + +SiteUrlOrEmailAddress : zhexuan@contoso.onmicrosoft.com +BoundaryType : InactiveMailbox +BoundaryInstruction : Set via Invoke-ComplianceSecurityFiIterAction -Set +BoundaryObjectId : zhexuan@contoso.onmicrosoft.com +BoundaryStatus : Success +BoundaryProperty : CustomAttribute3 +BoundaryPropertyVa1ue : ProjectX +``` + +This example sets the boundary of the specified OneDrive site to the specified CustomAttribute3 property value, and runs another command to review the result. + +## PARAMETERS + +### -Action +The Action parameter specifies the action for the command. Valid values are: + +- GetStatus +- Set + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailAddress +The EmailAddress parameter specifies the the affected user mailbox. You can use the following values to uniquely identify the mailbox: + +- Name +- Email address +- Alias +- ExchangeGUID + +If the value contains spaces, enclose the value in quotation marks. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PropertyName +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 + +Use the PropertyValue parameter to set the compliance boundary. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PropertyValue +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md b/exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md new file mode 100644 index 0000000000..3579f174b8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md @@ -0,0 +1,198 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Invoke-HoldRemovalAction + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Invoke-HoldRemovalAction cmdlet to view and remove holds on mailboxes and SharePoint sites. You can also see holds that were previously removed by using this cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Invoke-HoldRemovalAction -Action + [-Confirm] + [-ExchangeLocation ] + [-Force] + [-HoldId ] + [-SharePointLocation ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. Only Compliance Administrator can remove hold for Exchange or Sharepoint locations. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Invoke-HoldRemovalAction -Action RemoveHold -ExchangeLocation "KittyPetersen@contoso.onmicrosoft.com" -HoldId "UniHecbf89df-74fc-444a-a2dc-c0756c7d3503" +``` + +This example removes the specified hold on Kitty Petersen's mailbox if policy UniHecbf89df-74fc-444a-a2dc-c0756c7d3503 is not an active case hold policy. + +### Example 2 +```powershell +Invoke-HoldRemovalAction -Action GetHolds -SharePointLocation "https://contoso.sharepoint.com/sites/finance" +``` + +This example displays all hold information on the specified SharePoint site. + +### Example 3 +```powershell +Invoke-HoldRemovalAction -Action GetHoldRemovals +``` + +This example displays all hold removals that have been done using this cmdlet. + +## PARAMETERS + +### -Action +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. +- GetHolds: Shows holds on the specified mailbox (the ExchangeLocation parameter) or SharePoint site (the SharePointLocation parameter). +- RemoveHold: Removes the specified hold (the HoldId parameter) from the specified mailbox (the ExchangeLocation parameter) or SharePoint site (the SharePointLocation parameter). + +```yaml +Type: HoldRemovalActionType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: wi +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Invoke-MonitoringProbe.md b/exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md similarity index 94% rename from exchange/exchange-ps/exchange/server-health-and-performance/Invoke-MonitoringProbe.md rename to exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md index dd704665af..858171d8c8 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Invoke-MonitoringProbe.md +++ b/exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/invoke-monitoringprobe +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Invoke-MonitoringProbe @@ -19,7 +18,7 @@ Use the Invoke-MonitoringProbe cmdlet to run a Managed Availability probe on a s This cmdlet cannot be used to run every Managed Availability probe. Only some probes (mainly the deep test probes) can be run manually using this cmdlet. Probes that cannot be run with this cmdlet will generate an error message when Invoke-MonitoringProbe is used to run them. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -38,7 +37,7 @@ Invoke-MonitoringProbe [-Identity] -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -71,11 +70,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use this parameter to configure other Edge Transport servers remotely. @@ -242,12 +238,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Mount-Database.md b/exchange/exchange-ps/exchange/Mount-Database.md similarity index 84% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Mount-Database.md rename to exchange/exchange-ps/exchange/Mount-Database.md index 2275916f11..8d6dc5909a 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Mount-Database.md +++ b/exchange/exchange-ps/exchange/Mount-Database.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/mount-database +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Mount-Database @@ -17,17 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Mount-Database cmdlet to mount mailbox databases on Exchange servers. The cmdlet mounts the database only if the Microsoft Exchange Information Store service and the Microsoft Exchange Replication service are running. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Mount-Database [-Identity] [-AcceptDataLoss] [-Confirm] [-DomainController ] - [-Force] [-WhatIf] [-NewCapacity] [] +Mount-Database [-Identity] + [-AcceptDataLoss] + [-Confirm] + [-DomainController ] + [-Force] + [-NewCapacity] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,9 +49,7 @@ This example mounts the database MyDatabase. The Identity parameter specifies mailbox database that you want to mount. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -81,8 +84,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,9 +117,9 @@ Accept wildcard characters: False ``` ### -Force -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. +The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -Use this parameter to mount an empty database, or to override any errors or warnings that are encountered during the database mount. +Use this switch to mount an empty database, or to override any errors or warnings that are encountered during the database mount. ```yaml Type: SwitchParameter @@ -132,14 +134,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -NewCapacity +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: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -148,14 +150,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -NewCapacity -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. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. 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 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -169,12 +171,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Move-ActiveMailboxDatabase.md b/exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md similarity index 95% rename from exchange/exchange-ps/exchange/database-availability-groups/Move-ActiveMailboxDatabase.md rename to exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md index f91b2e55ee..c59b2bf565 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Move-ActiveMailboxDatabase.md +++ b/exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/move-activemailboxdatabase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Move-ActiveMailboxDatabase @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Move-ActiveMailboxDatabase cmdlet to perform a database or server switchover. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -36,7 +35,8 @@ Move-ActiveMailboxDatabase [-ActivatePreferredOnServer] ] + [-WhatIf] + [] ``` ### Identity @@ -54,12 +54,14 @@ Move-ActiveMailboxDatabase [-Identity] [[-ActivateOnServer [-SkipMaximumActiveDatabasesChecks] [-SkipMoveSuppressionChecks] [-TerminateOnWarning] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Server ``` -Move-ActiveMailboxDatabase [-Server] [[-ActivateOnServer] ] [-MoveAllDatabasesOrNone] +Move-ActiveMailboxDatabase [-Server] [[-ActivateOnServer] ] + [-MoveAllDatabasesOrNone] [-Confirm] [-DomainController ] [-MountDialOverride ] @@ -72,12 +74,14 @@ Move-ActiveMailboxDatabase [-Server] [[-ActivateOnSer [-SkipMaximumActiveDatabasesChecks] [-SkipMoveSuppressionChecks] [-TerminateOnWarning] - [-WhatIf] [] + [-WhatIf] + [] ``` ### SkipAllChecks ``` -Move-ActiveMailboxDatabase [-Identity] [-ActivateOnServer] [-SkipAllChecks] +Move-ActiveMailboxDatabase [-Identity] [-ActivateOnServer] + [-SkipAllChecks] [-Confirm] [-DomainController ] [-MountDialOverride ] @@ -90,11 +94,12 @@ Move-ActiveMailboxDatabase [-Identity] [-ActivateOnServer] [-SkipMaximumActiveDatabasesChecks] [-SkipMoveSuppressionChecks] [-TerminateOnWarning] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -132,9 +137,7 @@ This example performs a server switchover for the Mailbox server MBX1. All activ 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 - - Distinguished name (DN) - - GUID You can't use this parameter with the Server parameter @@ -156,11 +159,8 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID You can't use this parameter with the Identity parameter @@ -182,11 +182,8 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID You can use this parameter as part of ending maintenance mode on a Mailbox server. @@ -204,6 +201,22 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -ActivateOnServer +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -SkipAllChecks The SkipAllChecks switch specifies whether to skip all checks. You don't need to specify a value with this switch. @@ -224,27 +237,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ActivateOnServer -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -280,13 +276,9 @@ Accept wildcard characters: False 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. - - Lossless: This is the default value. When using this value, the database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy. - - GoodAvailability: If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. - - BestEffort: If you specify this value, the database automatically mounts regardless of the size of the copy queue length. Because the database will mount with any amount of log loss, using this value could result in a large amount of data loss. - - BestAvailability: If you specify this value, 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 then mounts the database. ```yaml @@ -337,7 +329,7 @@ Accept wildcard characters: False ### -SkipActiveCopyChecks 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. +**Note**: When you use this switch, you can move a database that's currently a seeding source, which cancels the seed operation. ```yaml Type: SwitchParameter @@ -491,12 +483,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Move-AddressList.md b/exchange/exchange-ps/exchange/Move-AddressList.md similarity index 86% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Move-AddressList.md rename to exchange/exchange-ps/exchange/Move-AddressList.md index c0321e98a7..d2c70381c6 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Move-AddressList.md +++ b/exchange/exchange-ps/exchange/Move-AddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/move-addresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Move-AddressList @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Move-AddressList cmdlet to move an existing address list to a new container under the root address list. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Move-AddressList [-Identity] -Target [-Confirm] - [-DomainController ] [-WhatIf] [] +Move-AddressList [-Identity] -Target + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,12 +46,9 @@ This example moves the address list with GUID c3fffd8e-026b-41b9-88c4-8c21697ac8 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 - - Distinguished name (DN) - - GUID - -- Path: (\\\) or [\\\\) +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) ```yaml Type: AddressListIdParameter @@ -68,12 +67,9 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID - -- Path: (\\\) or [\\\\) +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) ```yaml Type: AddressListIdParameter @@ -91,10 +87,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -145,12 +142,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Move-DatabasePath.md b/exchange/exchange-ps/exchange/Move-DatabasePath.md similarity index 82% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Move-DatabasePath.md rename to exchange/exchange-ps/exchange/Move-DatabasePath.md index 0b8231ef92..88ab1bea84 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Move-DatabasePath.md +++ b/exchange/exchange-ps/exchange/Move-DatabasePath.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/move-databasepath +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Move-DatabasePath @@ -17,13 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Move-DatabasePath cmdlet to set a new path to the location of a database on the specified Mailbox server and to move the related files to that location. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Move-DatabasePath [-Identity] [-ConfigurationOnly] [-Confirm] [-DomainController ] - [-EDBFilePath ] [-Force] [-LogFolderPath ] [-WhatIf] +Move-DatabasePath [-Identity] + [-ConfigurationOnly] + [-Confirm] + [-DomainController ] + [-EDBFilePath ] + [-Force] + [-LogFolderPath ] + [-WhatIf] [] ``` @@ -31,14 +36,11 @@ Move-DatabasePath [-Identity] [-ConfigurationOnly] [-Confi When you use the Move-DatabasePath cmdlet, consider the following: - This cmdlet fails if it's run while the database is being backed up. - - If the specified database is mounted when this cmdlet is run, the database is automatically dismounted and then remounted, and is unavailable to users while it's dismounted. - - In Exchange 2013 or earlier, you can only run this cmdlet on the affected Mailbox server. If you include the ConfigurationOnly parameter with the value $true, you can run the cmdlet on an administrator's workstation. This does not apply to Exchange 2016 or later (you can run the cmdlet anywhere). - - This cmdlet can't be run against replicated mailbox databases. To move the path of a replicated database, you must first remove all replicated copies, and then you can perform the move operation. After the move operation is complete, you can add copies of the mailbox database. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,9 +57,7 @@ This example sets a new path for the mailbox database specified by the mailbox d The Identity parameter specifies the database that you want to move. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -74,7 +74,9 @@ Accept wildcard characters: False ``` ### -ConfigurationOnly -The ConfigurationOnly switch specifies whether the configuration of the database changes without moving any files. A value of $true changes the configuration. A value of $false changes the configuration and moves the files. The default value is $false. +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. ```yaml Type: SwitchParameter @@ -92,10 +94,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -126,7 +129,7 @@ Accept wildcard characters: False ``` ### -EDBFilePath -The EdbFilePath parameter specifies a new file path for the database. All current database files are moved to this location. The default location is \\\Mailbox\\LocalCopies\\MBDatabase.edb. This file path can't be the same as the path for the backup copy of the database. +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 @@ -142,7 +145,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -190,7 +195,7 @@ Accept wildcard characters: False ``` ### -EDBFilePath -The EdbFilePath parameter specifies a new file path for the database. All current database files are moved to this location. The default location is \\\Mailbox\\LocalCopies\\MBDatabase.edb. This file path can't be the same as the path for the backup copy of the database. +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 @@ -210,12 +215,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Move-OfflineAddressBook.md b/exchange/exchange-ps/exchange/Move-OfflineAddressBook.md similarity index 85% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Move-OfflineAddressBook.md rename to exchange/exchange-ps/exchange/Move-OfflineAddressBook.md index a43665cf1c..52e6b27ad3 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Move-OfflineAddressBook.md +++ b/exchange/exchange-ps/exchange/Move-OfflineAddressBook.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/move-offlineaddressbook +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Move-OfflineAddressBook @@ -15,19 +14,23 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Move-OfflineAddressBook cmdlet to designate a new server responsible for generating the offline address book (OAB) in Exchange Server 2010. This cmdlet isn't used on OABs in Exchange Server 2016 or Exchange Server 2013. To perform this task in Exchange 2016 or Exchange 2013, use the Set-OfflineAddressBook cmdlet with the GeneratingMailbox parameter. +Use the Move-OfflineAddressBook cmdlet to designate a new server that's responsible for generating the offline address book (OAB) in Exchange Server 2010. This cmdlet isn't used on OABs in Exchange Server 2016 or Exchange Server 2013. To perform this task in Exchange 2016 or Exchange 2013, use the Set-OfflineAddressBook cmdlet with the GeneratingMailbox parameter. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Move-OfflineAddressBook [-Identity] [-Confirm] [-DomainController ] - [-Server ] [-WhatIf] [] +Move-OfflineAddressBook [-Identity] + [-Confirm] + [-DomainController ] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,10 +64,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -98,11 +102,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -141,12 +142,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md new file mode 100644 index 0000000000..85953675d6 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md @@ -0,0 +1,238 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ATPBuiltInProtectionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +**Note**: Don't use this cmdlet. This cmdlet is used by the system to create the one and only rule for the Built-in protection preset security policy during the creation of the organization. You can't use this cmdlet if a rule for the Built-in protection preset security policy already exists. The Remove-ATPBuiltInProtectionRule cmdlet is not available to remove rules. + +Use the New-ATPBuiltInProtectionRule cmdlet to create the rule for the Built-in protection preset security policy that effectively provides default policies for Safe Links and Safe Attachments in Microsoft Defender for Office 365. The rule specifies exceptions to the policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ATPBuiltInProtectionRule -SafeAttachmentPolicy -SafeLinksPolicy + [-Comments ] + [-Confirm] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Name ] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +> [!IMPORTANT] +> Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ATPBuiltInProtectionRule -SafeAttachmentPolicy "Built-In Protection Policy" -SafeLinksPolicy "Built-In Protection Policy" +``` + +This cmdlet creates the rule for the Built-in protection preset security policy. This command will fail if the rule already exists. + +## PARAMETERS + +### -SafeAttachmentPolicy +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. + +```yaml +Type: SafeAttachmentPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SafeLinksPolicy +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. + +```yaml +Type: SafeLinksPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/p/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md new file mode 100644 index 0000000000..9397716f14 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md @@ -0,0 +1,364 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ATPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-ATPProtectionPolicyRule cmdlet to create rules for Microsoft Defender for Office 365 protections in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. + +**Note**: Unless you manually removed a rule using the Remove-ATPProtectionPolicyRule cmdlet, we don't recommend using this cmdlet to create rules. To create the rule, you need to specify the existing individual security policies that are associated with the preset security policy. We never recommend creating these required individual security policies manually. Turning on the preset security policy for the first time in the Microsoft Defender portal automatically creates the required individual security policies, but also creates the associated rules using this cmdlet. So, if the rules already exist, you don't need to use this cmdlet to create them. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ATPProtectionPolicyRule [-Name] -SafeAttachmentPolicy -SafeLinksPolicy + [-Comments ] + [-Confirm] + [-Enabled ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Priority ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ATPProtectionPolicyRule -Name "Standard Preset Security Policy" -SafeAttachmentPolicy "Standard Preset Security Policy1622650008019" -SafeLinksRule "Standard Preset Security Policy1622650008534" Priority 1 +``` + +This example creates the rule for the Standard preset security policy. No restrictions are placed on who the Defender for Office 365 protections apply to. If the rule already exists, the command will fail. + +## PARAMETERS + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SafeAttachmentPolicy +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: + +- Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008019`. +- Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034872546`. + +You can find the Safe Attachments policy that's used by the Standard or Strict preset security policies by running the following commands: `Get-SafeAttachmentPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Standard"` or `Get-SafeAttachmentPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Strict"`. + +```yaml +Type: SafeAttachmentPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SafeLinksPolicy +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: + +- Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008534`. +- Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034873192`. + +You can find the Safe Links policy that's used by the Standard or Strict preset security policies by running the following commands: `Get-SafeLinksPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Standard"` or `Get-SafeLinksPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Strict"`. + +```yaml +Type: SafeLinksPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. +- $false: The rule is disabled. The State value of the rule is Disabled. + +After you create the rule, you turn on or turn off the preset security policy using one of the following commands: + +- Turn off: Disable-ATPProtectionPolicyRule and Disable-EOPProtectionPolicyRule. +- Turn on: Enable-ATPProtectionPolicyRule and Enable-EOPProtectionPolicyRule. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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. + +When you create the policy, you must use the default value. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/New-AcceptedDomain.md b/exchange/exchange-ps/exchange/New-AcceptedDomain.md similarity index 92% rename from exchange/exchange-ps/exchange/mail-flow/New-AcceptedDomain.md rename to exchange/exchange-ps/exchange/New-AcceptedDomain.md index c7964703c6..157ffaec81 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-AcceptedDomain.md +++ b/exchange/exchange-ps/exchange/New-AcceptedDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-accepteddomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-AcceptedDomain @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-AcceptedDomain cmdlet to create an accepted domain in your organization. An accepted domain is any SMTP namespace for which an Exchange organization sends and receives email. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,11 +25,12 @@ New-AcceptedDomain [-Name] -DomainName [-Confirm] [-DomainController ] [-DomainType ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,35 +43,35 @@ This example creates the new authoritative accepted domain Contoso. ## PARAMETERS -### -DomainName -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. +### -Name +The Name parameter specifies a unique name for the accepted domain object. ```yaml -Type: SmtpDomainWithSubdomains +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies a unique name for the accepted domain object. +### -DomainName +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. ```yaml -Type: String +Type: SmtpDomainWithSubdomains Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -80,8 +80,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -156,12 +155,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/New-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md similarity index 90% rename from exchange/exchange-ps/exchange/devices/New-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md index c03a61fac2..136f962987 100644 --- a/exchange/exchange-ps/exchange/devices/New-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-activesyncdeviceaccessrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-ActiveSyncDeviceAccessRule @@ -17,20 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-ActiveSyncDeviceAccessRule cmdlet to define the access levels for Exchange ActiveSync devices based on the identity of the device. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-ActiveSyncDeviceAccessRule -AccessLevel - -Characteristic -QueryString [-Confirm] - [-DomainController ] [-WhatIf] [] +New-ActiveSyncDeviceAccessRule -AccessLevel -Characteristic -QueryString + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION You can create multiple rules that define groups of devices: Allowed devices, blocked devices and quarantined devices. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,13 +71,9 @@ Accept wildcard characters: False The Characteristic parameter specifies the device characteristic or category that's used by the rule. Valid values for this parameter are: - DeviceModel - - DeviceType - - DeviceOS - - UserAgent - - XMSWLHeader ```yaml @@ -113,8 +110,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -169,12 +165,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/New-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/devices/New-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md index 45f139fa93..e194e62483 100644 --- a/exchange/exchange-ps/exchange/devices/New-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-activesyncmailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-ActiveSyncMailboxPolicy @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-ActiveSyncMailboxPolicy cmdlet to create a Microsoft Mobile Device mailbox policy object. -Note: In Exchange 2013 or later, use the New-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use New-ActiveSyncMailboxPolicy, update them to use New-MobileDeviceMailboxPolicy. +**Note**: In Exchange 2013 or later, use the New-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use New-ActiveSyncMailboxPolicy, update them to use New-MobileDeviceMailboxPolicy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -69,7 +68,6 @@ New-ActiveSyncMailboxPolicy [-Name] [-MaxInactivityTimeDeviceLock ] [-MinDevicePasswordComplexCharacters ] [-MinDevicePasswordLength ] - [-MobileOTAUpdateMode ] [-PasswordRecoveryEnabled ] [-RequireDeviceEncryption ] [-RequireEncryptedSMIMEMessages ] @@ -81,7 +79,8 @@ New-ActiveSyncMailboxPolicy [-Name] [-UNCAccessEnabled ] [-UnapprovedInROMApplicationList ] [-WSSAccessEnabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -89,7 +88,7 @@ The New-ActiveSyncMailboxPolicy cmdlet creates a Mobile Device mailbox policy fo Some Mobile Device mailbox policy settings require the mobile device to have certain built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This allows devices that can't enforce all policy settings to synchronize with your server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -537,8 +536,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -720,13 +718,9 @@ Accept wildcard characters: False The MaxCalendarAgeFilter parameter specifies the maximum range of calendar days that can be synchronized to the device. Valid values are: - All - - TwoWeeks - - OneMonth - - ThreeMonths - - SixMonths ```yaml @@ -764,19 +758,12 @@ The MaxEmailAgeFilter parameter specifies the maximum number of days of email it Possible values are: - All - - OneDay - - ThreeDays - - OneWeek - - TwoWeeks - - OneMonth - - ThreeMonths - - SixMonths ```yaml @@ -872,32 +859,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MobileOTAUpdateMode -This parameter is available or functional only in Exchange Server 2010. - -The MobileOTAUpdateMode parameter specifies which updates can be seen by the devices that implemented support for this restricting functionality. Valid values are: - -- MajorVersionUpdates - -- MinorVersionUpdates - -- BetaVersionUpdates - -You need to use this parameter with the AllowMobileOTAUpdate parametery. - -```yaml -Type: MobileOTAUpdateModeType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -PasswordRecoveryEnabled 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. @@ -1095,12 +1056,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access-servers/New-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md index e86880d8b8..03c846da01 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-activesyncvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-ActiveSyncVirtualDirectory @@ -17,24 +16,35 @@ This cmdlet is available only in on-premises Exchange. Use the New-ActiveSyncVirtualDirectory cmdlet to create Exchange ActiveSync virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-ActiveSyncVirtualDirectory [-ApplicationRoot ] [-AppPoolId ] [-Confirm] - [-DomainController ] [-ExtendedProtectionFlags ] - [-ExtendedProtectionSPNList ] [-ExtendedProtectionTokenChecking ] - [-ExternalAuthenticationMethods ] [-ExternalUrl ] - [-InstallProxySubDirectory ] [-InternalAuthenticationMethods ] - [-InternalUrl ] [-Path ] [-WebSiteName ] [-WhatIf] [-Role ] - [-Server ] [] +New-ActiveSyncVirtualDirectory [-ApplicationRoot ] + [-AppPoolId ] + [-Confirm] + [-DomainController ] + [-ExtendedProtectionFlags ] + [-ExtendedProtectionSPNList ] + [-ExtendedProtectionTokenChecking ] + [-ExternalAuthenticationMethods ] + [-ExternalUrl ] + [-InstallProxySubDirectory ] + [-InternalAuthenticationMethods ] + [-InternalUrl ] + [-Path ] + [-Role ] + [-Server ] + [-WebSiteName ] + [-WhatIf] + [] ``` ## DESCRIPTION The New-ActiveSyncVirtualDirectory cmdlet creates an Exchange ActiveSync virtual directory on the specified server under the specified website. The Exchange ActiveSync virtual directory created is named Microsoft-Server-ActiveSync. Only one Exchange ActiveSync virtual directory can exist in each Exchange ActiveSync website. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -96,8 +106,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -133,13 +142,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -159,8 +164,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -179,14 +183,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -205,33 +205,19 @@ Accept wildcard characters: False 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 - - Basic - - Certificate - - Digest - - Fba - - Kerberos - - LiveIdBasic - - LiveIdFba - - LiveIdNegotiate - - NegoEx - - Negotiate - - Ntlm - - OAuth - - WindowsIntegrated - - WSSecurity You can specify multiple values separated by commas. @@ -239,7 +225,6 @@ You can specify multiple values separated by commas. Although you can specify any of these values, whether or not the authentication method actually works for external connections depends on other factors. For example: - Is the authentication method available on the virtual directory? - - Is the authentication method available, but disabled on the virtual directory? The default value is blank ($null), which means all available authentication methods are accepted. @@ -293,33 +278,19 @@ Accept wildcard characters: False 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 - - Basic - - Certificate - - Digest - - Fba - - Kerberos - - LiveIdBasic - - LiveIdFba - - LiveIdNegotiate - - NegoEx - - Negotiate - - Ntlm - - OAuth - - WindowsIntegrated - - WSSecurity You can specify multiple values separated by commas. @@ -327,7 +298,6 @@ You can specify multiple values separated by commas. Although you can specify any of these values, whether or not the authentication method actually works for internal connections depends on other factors. For example: - Is the authentication method available on the virtual directory? - - Is the authentication method available, but disabled on the virtual directory? The default value is blank ($null), which means all available authentication methods are accepted. @@ -377,14 +347,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WebSiteName -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. +### -Role +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. +- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. + +Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. ```yaml -Type: String +Type: VirtualDirectoryRole Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -393,36 +368,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -Server +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 +- FQDN +- Distinguished name (DN) +- ExchangeLegacyDN ```yaml -Type: SwitchParameter +Type: ServerIdParameter Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Role -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. - -- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. - -Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. +### -WebSiteName +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: VirtualDirectoryRole +Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -431,27 +405,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Server -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 - -- FQDN - -- Distinguished name (DN) - -- ExchangeLegacyDN +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: ServerIdParameter +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -460,12 +426,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-AdaptiveScope.md b/exchange/exchange-ps/exchange/New-AdaptiveScope.md new file mode 100644 index 0000000000..88433a9deb --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AdaptiveScope.md @@ -0,0 +1,175 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AdaptiveScope + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-AdaptiveScope cmdlet to create adaptive scopes in your organization. Adaptive scopes (or static scopes) are used in retention policies and retention label policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +New-AdaptiveScope -Name -FilterConditions -LocationType + [-AdministrativeUnit ] + [-Comment ] + [] +``` + +### AdaptiveScopeRawQuery +``` +New-AdaptiveScope -Name -LocationType -RawQuery + [-AdministrativeUnit ] + [-Comment ] + [] +``` + +## DESCRIPTION +For more information about the properties to use in adaptive scopes, see [Configuration information for adaptive scopes](https://learn.microsoft.com/purview/retention-settings#configuration-information-for-adaptive-scopes). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AdaptiveScope -Name "Project X" -LocationType User -FilterConditions @{"Conditions" = @(@{"Conditions" = @(@{"Value" = "US"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}, @{"Value" = "Canada"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}); "Conjunction" = "Or"}, @{"Value" = "Finance"; "Operator" = "Equals"; "Name" = "Department"}); "Conjunction" = "And"} +``` + +This example create an adaptive query scope named Project X with the following details: + +- Scope: Users +- Query: "('Country or region' equals 'US' or 'Canada') and 'Department' equals 'Finance'". + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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"}` +- Site: Indexed custom properties. For example, for the condition "'Refinable string 0' equals 'Human Resources', use the following syntax: `@{"Conditions" = @{"Value" = "Human Resources"; "Operator" = "Equals"; "Name" = "RefinableString00"}; "Conjunction" = "And"}` + +You can't use this parameter with the RawQuery parameter. + +```yaml +Type: PswsHashtable +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationType +The LocationType parameter specifies the location where the adaptive scope filter is defined. Valid values are: + +- User +- Group (Microsoft 365 group) +- Site + +```yaml +Type: DynamicBoundaryLocationType +Parameter Sets: (All) +Aliases: +Accepted values: Unknown, User, Group, Site +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RawQuery +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. + +```yaml +Type: String +Parameter Sets: AdaptiveScopeRawQuery +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdministrativeUnit +{{ Fill AdministrativeUnit Description }} + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-AddressBookPolicy.md b/exchange/exchange-ps/exchange/New-AddressBookPolicy.md similarity index 77% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/New-AddressBookPolicy.md rename to exchange/exchange-ps/exchange/New-AddressBookPolicy.md index 274765499a..4bade089b4 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-AddressBookPolicy.md +++ b/exchange/exchange-ps/exchange/New-AddressBookPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/new-addressbookpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-AddressBookPolicy @@ -17,21 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-AddressBookPolicy cmdlet to create an address book policy. Address book policies define the global address list (GAL), offline address book (OAB), room list, and address lists that will be displayed to mailbox users who are assigned the policy. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-AddressBookPolicy [-Name] -AddressLists - -GlobalAddressList -OfflineAddressBook - -RoomList [-Confirm] [-DomainController ] - [-WhatIf] [] +New-AddressBookPolicy [-Name] -AddressLists -GlobalAddressList -OfflineAddressBook -RoomList + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,13 +43,9 @@ New-AddressBookPolicy -Name "All Fabrikam ABP" -AddressLists "\All Fabrikam","\A This example creates an address book policy with the following settings: - Name: All Fabrikam ABP - - Included address lists: All Fabrikam, All Fabrikam Mailboxes, All Fabrikam DLs, All Fabrikam Contacts - - Included room list: All Fabrikam-Rooms - - Included OAB: Fabrikam-All-OAB - - Included GAL: All Fabrikam ## PARAMETERS @@ -119,7 +115,19 @@ Accept wildcard characters: False ``` ### -RoomList -The RoomList parameter specifies the room address list that will be used by mailbox users who are assigned this address book policy. You can specify only one room list for each address book policy. +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. +- When using experiences that aren't location specific (for example, the To or Cc fields of a calendar event), the address lists specified by the AddressLists parameter in this address book policy are applied. The address list specified by this parameter isn't used. + +A valid value for this parameter is one address list. You can use any value that uniquely identifies the address list. For example: + +- Name +- Distinguished name (DN) +- GUID + +> [!NOTE] +> There's no automatic association between this parameter and [room list distribution groups](https://learn.microsoft.com/exchange/recipients/room-mailboxes#create-a-room-list), which also use a parameter named RoomList in the New-DistributionGroup and Set-DistributionGroup cmdlets. You still need to create room list distribution groups and assign resources as group members. Location experiences are filtered to show only rooms included in the address list that's specified by the RoomList property of the address book policy that's assigned to the user (if any). ```yaml Type: AddressListIdParameter @@ -137,8 +145,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -193,12 +200,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-AddressList.md b/exchange/exchange-ps/exchange/New-AddressList.md similarity index 91% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/New-AddressList.md rename to exchange/exchange-ps/exchange/New-AddressList.md index efbe5645be..540855b553 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-AddressList.md +++ b/exchange/exchange-ps/exchange/New-AddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/new-addresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-AddressList @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-AddressList cmdlet to create address lists and apply them to recipients. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -49,7 +48,8 @@ New-AddressList [-Name] -IncludedRecipients [-DisplayName ] [-DomainController ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### CustomFilter @@ -60,27 +60,26 @@ New-AddressList [-Name] -RecipientFilter [-DisplayName ] [-DomainController ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - - The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - - The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPath filter. +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-AddressList -Name MyAddressList -RecipientFilter "((RecipientType -eq 'UserMailbox') -and ((StateOrProvince -eq 'Washington') -or (StateOrProvince -eq 'Oregon')))" +New-AddressList -Name MyAddressList -RecipientFilter "((RecipientTypeDetails -eq 'UserMailbox') -and ((StateOrProvince -eq 'Washington') -or (StateOrProvince -eq 'Oregon')))" ``` This example creates the address list MyAddressList. The address list includes recipients that are mailbox users and have the StateOrProvince property set to Washington or Oregon. @@ -94,7 +93,7 @@ This example creates the address list MyAddressList2 that includes mailboxes tha ### Example 3 ```powershell -New-AddressList -Name "AL_AgencyB" -RecipientFilter "((RecipientType -eq 'UserMailbox') -and (CustomAttribute15 -like '*AgencyB*'))" +New-AddressList -Name "AL_AgencyB" -RecipientFilter "((RecipientTypeDetails -eq 'UserMailbox') -and (CustomAttribute15 -like 'AgencyB*'))" ``` This example creates the address list AL\_AgencyB that includes mailboxes that have the value of the CustomAttribute15 parameter contains AgencyB. @@ -121,20 +120,15 @@ Accept wildcard characters: False 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. - - MailboxUsers - - MailContacts - - MailGroups - - MailUsers - - Resources: This value indicates room or equipment mailboxes. You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. -You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: WellKnownRecipientType @@ -150,21 +144,16 @@ Accept wildcard characters: False ``` ### -RecipientFilter -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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). - In cloud-based environments, you can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. - - In on-premises Exchange, wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter in combination with the IncludedRecipients parameter or any Conditional parameters (which are used to create precanned filters). @@ -186,7 +175,7 @@ The ConditionalCompany parameter specifies a precanned filter that's based on th 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -206,7 +195,7 @@ The ConditionalCustomAttribute1 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -226,7 +215,7 @@ The ConditionalCustomAttribute10 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -246,7 +235,7 @@ The ConditionalCustomAttribute11 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -266,7 +255,7 @@ The ConditionalCustomAttribute12 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -286,7 +275,7 @@ The ConditionalCustomAttribute13 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -306,7 +295,7 @@ The ConditionalCustomAttribute14 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -326,7 +315,7 @@ The ConditionalCustomAttribute15 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -346,7 +335,7 @@ The ConditionalCustomAttribute2 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -366,7 +355,7 @@ The ConditionalCustomAttribute3 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -386,7 +375,7 @@ The ConditionalCustomAttribute4 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -406,7 +395,7 @@ The ConditionalCustomAttribute5 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -426,7 +415,7 @@ The ConditionalCustomAttribute6 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -446,7 +435,7 @@ The ConditionalCustomAttribute7 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -466,7 +455,7 @@ The ConditionalCustomAttribute8 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -486,7 +475,7 @@ The ConditionalCustomAttribute9 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -506,7 +495,7 @@ The ConditionalDepartment parameter specifies a precanned filter that's based on 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -526,7 +515,7 @@ The ConditionalStateOrProvince parameter specifies a precanned filter that's bas 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -544,8 +533,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -565,12 +553,9 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID - -- Path: (\\\) or [\\\\) +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) If you don't use this parameter,the address list is created under the root (\\). @@ -629,11 +614,8 @@ 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: - Name - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is the OU where the object was created. @@ -672,12 +654,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-AddressRewriteEntry.md b/exchange/exchange-ps/exchange/New-AddressRewriteEntry.md similarity index 94% rename from exchange/exchange-ps/exchange/mail-flow/New-AddressRewriteEntry.md rename to exchange/exchange-ps/exchange/New-AddressRewriteEntry.md index 716bcbbe05..1c5c9541bd 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-AddressRewriteEntry.md +++ b/exchange/exchange-ps/exchange/New-AddressRewriteEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-addressrewriteentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-AddressRewriteEntry @@ -17,13 +16,17 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the New-AddressRewriteEntry cmdlet to create an address rewrite entry that rewrites sender and recipient email addresses in messages sent to or sent from your organization through an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-AddressRewriteEntry [-Name] -ExternalAddress -InternalAddress [-Confirm] - [-DomainController ] [-ExceptionList ] [-OutboundOnly ] [-WhatIf] +New-AddressRewriteEntry [-Name] -ExternalAddress -InternalAddress + [-Confirm] + [-DomainController ] + [-ExceptionList ] + [-OutboundOnly ] + [-WhatIf] [] ``` @@ -93,9 +96,7 @@ Accept wildcard characters: False 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 - - Single domain: contoso.com or sales.contoso.com - - Domain and all subdomains: \*.contoso.com ```yaml @@ -114,8 +115,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -206,12 +206,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AdminAuditLogSearch.md b/exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md similarity index 81% rename from exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AdminAuditLogSearch.md rename to exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md index 385b8c60d1..1059619e55 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AdminAuditLogSearch.md +++ b/exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md @@ -1,38 +1,46 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/new-adminauditlogsearch -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-AdminAuditLogSearch ## SYNOPSIS +> [!NOTE] +> This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the New-AdminAuditLogSearch cmdlet to search the contents of the administrator audit log and send the results to one or more mailboxes that you specify. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-AdminAuditLogSearch [ -EndDate - -StartDate -StatusMailRecipients [-Cmdlets ] - [-Confirm] [-DomainController ] [-Name ] [-ObjectIds ] - [-Parameters ] [-UserIds ] [-WhatIf] - [-ExternalAccess ] [] +New-AdminAuditLogSearch -EndDate -StartDate -StatusMailRecipients + [-Cmdlets ] + [-Confirm] + [-DomainController ] + [-ExternalAccess ] + [-Name ] + [-ObjectIds ] + [-Parameters ] + [-UserIds ] + [-WhatIf] + [] ``` ## DESCRIPTION After the New-AdminAuditLogSearch cmdlet is run, the report is delivered to the mailboxes you specify within 15 minutes. The log is included as an XML attachment on the report email message. The maximum size of the log that can be generated is 10 megabytes (MB). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,11 +52,8 @@ New-AdminAuditLogSearch -Name "Mailbox Quota Change Audit" -Cmdlets Set-Mailbox This example finds all the administrator audit log entries that match the following criteria and sends the results to the david@contoso.com and chris@contoso.com SMTP addresses: - Cmdlets:Set-Mailbox - - Parameters:UseDatabaseQuotaDefaults, ProhibitSendReceiveQuota, ProhibitSendQuota - - StartDate: 01/24/2018 - - EndDate: 02/12/2018 ### Example 2 @@ -63,14 +68,13 @@ This example returns entries in the administrator audit log of an Exchange Onlin ### -EndDate 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". +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". ```yaml Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named Default value: None @@ -81,14 +85,13 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named Default value: None @@ -105,8 +108,7 @@ If you want to specify more than one recipient, separate each SMTP address with Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +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 @@ -123,8 +125,7 @@ If you want to specify more than one cmdlet, separate each cmdlet with a comma. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +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 @@ -135,16 +136,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named Default value: None @@ -170,6 +169,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ExternalAccess +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Name 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. @@ -179,8 +193,7 @@ If the name of the report contains spaces, enclose the name in quotation marks ( Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +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 @@ -197,8 +210,7 @@ If you want to specify more than one object ID, separate each ID with a comma. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +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 @@ -215,8 +227,7 @@ If you want to specify more than one parameter, separate each parameter with a c Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +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 @@ -233,8 +244,7 @@ If you want to specify more than one user ID, separate each ID with a comma. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +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 @@ -243,7 +253,7 @@ Accept wildcard characters: False ``` ### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. +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. @@ -251,24 +261,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalAccess -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 - +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 @@ -281,12 +274,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/New-AntiPhishPolicy.md new file mode 100644 index 0000000000..412a2a5340 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AntiPhishPolicy.md @@ -0,0 +1,1003 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AntiPhishPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-AntiPhishPolicy cmdlet to create antiphish policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-AntiPhishPolicy [-Name] + [-AdminDisplayName ] + [-AuthenticationFailAction ] + [-Confirm] + [-DmarcQuarantineAction ] + [-DmarcRejectAction ] + [-Enabled ] + [-EnableFirstContactSafetyTips ] + [-EnableMailboxIntelligence ] + [-EnableMailboxIntelligenceProtection ] + [-EnableOrganizationDomainsProtection ] + [-EnableSimilarDomainsSafetyTips ] + [-EnableSimilarUsersSafetyTips ] + [-EnableSpoofIntelligence ] + [-EnableTargetedDomainsProtection ] + [-EnableTargetedUserProtection ] + [-EnableUnauthenticatedSender ] + [-EnableUnusualCharactersSafetyTips ] + [-EnableViaTag ] + [-ExcludedDomains ] + [-ExcludedSenders ] + [-HonorDmarcPolicy ] + [-ImpersonationProtectionState ] + [-MailboxIntelligenceProtectionAction ] + [-MailboxIntelligenceProtectionActionRecipients ] + [-MailboxIntelligenceQuarantineTag ] + [-MakeDefault] + [-PhishThresholdLevel ] + [-PolicyTag ] + [-RecommendedPolicyType ] + [-SimilarUsersSafetyTipsCustomText ] + [-SpoofQuarantineTag ] + [-TargetedDomainActionRecipients ] + [-TargetedDomainProtectionAction ] + [-TargetedDomainQuarantineTag ] + [-TargetedDomainsToProtect ] + [-TargetedUserActionRecipients ] + [-TargetedUserProtectionAction ] + [-TargetedUserQuarantineTag ] + [-TargetedUsersToProtect ] + [-UnusualCharactersSafetyTipsCustomText ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Phishing messages contain fraudulent links or spoofed domains in an effort to get personal information from the recipients. + +New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the AntiPhishPolicy parameter on the New-AntiPhishRule or Set-AntiPhishRule cmdlets to associate the policy with a rule. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AntiPhishPolicy -Name "Research Quarantine" -AdminDisplayName "Research department policy" -EnableOrganizationDomainsProtection $true -EnableTargetedDomainsProtection $true -TargetedDomainsToProtect fabrikam.com -TargetedDomainProtectionAction Quarantine -EnableTargetedUserProtection $true -TargetedUsersToProtect "Mai Fujito;mfujito@fabrikam.com" -TargetedUserProtectionAction Quarantine -EnableMailboxIntelligenceProtection $true -MailboxIntelligenceProtectionAction Quarantine -EnableSimilarUsersSafetyTips $true -EnableSimilarDomainsSafetyTips $true -EnableUnusualCharactersSafetyTips $true +``` + +In Microsoft Defender for Office 365, this example creates and enables an antiphish policy named Research Quarantine with the following settings: + +- The description is: Research department policy. +- Enables organization domains protection for all accepted domains, and targeted domains protection for fabrikam.com. +- Specifies Mai Fujito (mfujito@fabrikam.com) as a user to protect from impersonation. +- Enables mailbox intelligence protection, and specifies the quarantine action. +- Enables impersonation safety tips (impersonated domains, impersonated users, and unusual characters). + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuthenticationFailAction +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: + +- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. + +```yaml +Type: SpoofAuthenticationFailAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DmarcQuarantineAction +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: + +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. This is the default value. + +This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. + +```yaml +Type: SpoofDmarcQuarantineAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DmarcRejectAction +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: + +- Quarantine: Deliver the message to quarantine. +- Reject: Reject the message. This is the default value. + +This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. + +```yaml +Type: SpoofDmarcRejectAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. + +To enable or disable an existing anti-phishing policy, use the **Enable-AntiPhishRule** or **Disable-AntiPhishRule** cmdlets. + +In the output of the **Get-AntiPhishRule** cmdlet, whether the anti-phishing policy is enabled or disabled is visible in the State property. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableFirstContactSafetyTips +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. +- $false: First contact safety tips are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMailboxIntelligence +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: + +- $true: Mailbox intelligence is enabled. This is the default value. +- $false: Mailbox intelligence is disabled. The values of the EnableMailboxIntelligenceProtection and MailboxIntelligenceProtectionAction parameters are ignored. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMailboxIntelligenceProtection +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: + +- $true: Take action for impersonation detections from mailbox intelligence results. Use the MailboxIntelligenceProtectionAction parameter to specify the action. +- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This is the default value. + +This parameter is meaningful only if the EnableMailboxIntelligence parameter is set to the value $true. + +If you set this parameter to the value $false when the value of the EnableMailboxIntelligence parameter is $true, no action is taken on messages based on mailbox intelligence results (for example, lack of communication history). But, but mailbox intelligence can still help reduce impersonation false positives based on frequent contact information. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOrganizationDomainsProtection +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: + +- $true: Domain impersonation protection is enabled for all registered domains in the Microsoft 365 organization. +- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSimilarDomainsSafetyTips +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: + +- $true: Safety tips for similar domains are enabled. +- $false: Safety tips for similar domains are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSimilarUsersSafetyTips +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: + +- $true: Safety tips for similar users are enabled. +- $false: Safety tips for similar users are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSpoofIntelligence +This setting is part of spoof protection. + +The EnableSpoofIntelligence parameter specifies whether to enable or disable antispoofing protection for the policy. Valid values are: + +- $true: Antispoofing is enabled for the policy. This is the default and recommended value. Use the \*-TenantAllowBlockListSpoofItems, Get-SpoofIntelligenceInsight, and Get-SpoofMailReport cmdlets to view and specify the spoofed senders to allow or block. +- $false: Antispoofing is disabled for the policy. We only recommend this value if you have a domain that's protected by another email filtering service. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTargetedDomainsProtection +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: + +- $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter. +- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTargetedUserProtection +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: + +- $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter. +- $false: The TargetedUsersToProtect parameter isn't used. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUnauthenticatedSender +This setting is part of spoof protection. + +The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are: + +- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. +- $false: A question mark is never applied to the sender's photo. + +To prevent these identifiers from being added to messages from specific senders, you have the following options: + +- Allow the sender to spoof in the spoof intelligence policy. For instructions, see [Configure spoof intelligence in Microsoft 365](https://learn.microsoft.com/defender-office-365/anti-spoofing-spoof-intelligence). +- If you own the domain, configure email authentication for the domain. For more information, see [Configure email authentication for domains you own](https://learn.microsoft.com/defender-office-365/email-authentication-about). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUnusualCharactersSafetyTips +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: + +- $true: Safety tips for unusual characters are enabled. +- $false: Safety tips for unusual characters are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableViaTag +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: + +- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This is the default value. +- $false: The via tag is not added to the From address. + +To prevent the via tag from being added to messages from specific senders, you have the following options: + +- Allow the sender to spoof. For instructions, see [Configure spoof intelligence in Microsoft 365](https://learn.microsoft.com/defender-office-365/anti-spoofing-spoof-intelligence). +- If you own the domain, configure email authentication for the domain. For more information, see [Configure email authentication for domains you own](https://learn.microsoft.com/defender-office-365/email-authentication-about). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedDomains +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. + +The maximum number of entries is approximately 1000. + +**Note**: Domain entries don't include subdomains of the specified domain. You need to add an entry for each subdomain. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedSenders +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. + +The maximum number of entries is approximately 1000. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HonorDmarcPolicy +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: + +- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This is the default value. +- $false: If the message fails DMARC, ignore the action in the sender's DMARC policy. The AuthenticationFailAction parameter specifies the action to take on the message. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImpersonationProtectionState +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: + +- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy. +- Manual: This is the default value in custom policies that you create. +- Off + +```yaml +Type: ImpersonationProtectionState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxIntelligenceProtectionAction +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: + +- NoAction: This is the default value. Note that this value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. +- BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. +- Redirect: Redirect the message to the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter. + +This parameter is meaningful only if the EnableMailboxIntelligence and EnableMailboxIntelligenceProtection parameters are set to the value $true. + +```yaml +Type: ImpersonationAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxIntelligenceProtectionActionRecipients +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. + +A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxIntelligenceQuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined by mailbox intelligence impersonation protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeDefault +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). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishThresholdLevel +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: + +- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. +- 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence. +- 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence. +- 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTag +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecommendedPolicyType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SimilarUsersSafetyTipsCustomText +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpoofQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined by spoof intelligence protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainActionRecipients +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. + +A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainProtectionAction +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: + +- NoAction: This is the default value. +- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. +- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainQuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined by domain impersonation protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainsToProtect +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. + +You can specify multiple domains separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUserActionRecipients +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. + +A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUserProtectionAction +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: + +- NoAction: This is the default value. +- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. +- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUserQuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined by user impersonation protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUsersToProtect +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. + +This parameter uses the syntax: "DisplayName;EmailAddress". + +- DisplayName specifies the display name of the user that could be a target of impersonation. This value can contain special characters. +- EmailAddress specifies the internal or external email address that's associated with the display name. +- You can specify multiple values by using the syntax: `"DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN"`. The combination of DisplayName and EmailAddress needs to be unique for each value. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnusualCharactersSafetyTipsCustomText +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-AntiPhishRule.md b/exchange/exchange-ps/exchange/New-AntiPhishRule.md new file mode 100644 index 0000000000..79afcd0346 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AntiPhishRule.md @@ -0,0 +1,342 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AntiPhishRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-AntiPhishRule cmdlet to create antiphish rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-AntiPhishRule [-Name] -AntiPhishPolicy + [-Comments ] + [-Confirm] + [-Enabled ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Priority ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to add the antiphish rule to an existing policy by using the AntiPhishPolicy parameter. You create antiphish policies by using the New-AntiPhishPolicy cmdlet. + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Common policy settings](https://learn.microsoft.com/defender-office-365/anti-phishing-policies-about#common-policy-settings). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AntiPhishRule -Name "Research Department" -AntiPhishPolicy "Research Quarantine" -SentToMemberOf "Research Department" +``` + +This example creates an antiphish rule named Research Department with the following settings: + +- The rule is associated with the antiphish policy named Research Quarantine. +- The rule applies to members of the group named Research Department. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AntiPhishPolicy +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 +- Distinguished name (DN) +- GUID + +You can't specify the default antiphish policy. And, you can't specify an antiphish policy that's already associated with another antiphish rule. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the rule is enabled. Valid values are: + +- $true: The rule is enabled. This is the default value. +- $false: The rule is disabled. + +In the properties of the rule, the value of this parameter is visible in the State property. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-App.md b/exchange/exchange-ps/exchange/New-App.md new file mode 100644 index 0000000000..12f88e9b57 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-App.md @@ -0,0 +1,680 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-App + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-App cmdlet to install apps for Outlook. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### ExtensionOfficeMarketplace +``` +New-App [-Etoken ] [-MarketplaceCorrelationID ] [-MarketplaceAssetID ] [-MarketplaceQueryMarket ] [-MarketplaceServicesUrl ] [-MarketplaceUserProfileType ] + [-AddInOverrides ] + [-AllowReadWriteMailbox] + [-AllowSetting ] + [-AppState ] + [-AppType ] + [-Confirm] + [-DefaultStateForUser ] + [-DomainController ] + [-DownloadOnly] + [-Enabled ] + [-Identity ] + [-Mailbox ] + [-OrganizationApp] + [-PrivateCatalog] + [-ProvidedTo ] + [-UpdateAppState] + [-UserList ] + [-Version ] + [-WhatIf] + [] +``` + +### ExtensionFileData +``` +New-App [-FileData ] + [-AddInOverrides ] + [-AllowReadWriteMailbox] + [-AllowSetting ] + [-AppState ] + [-AppType ] + [-Confirm] + [-DefaultStateForUser ] + [-DomainController ] + [-DownloadOnly] + [-Enabled ] + [-Identity ] + [-Mailbox ] + [-OrganizationApp] + [-PrivateCatalog] + [-ProvidedTo ] + [-UpdateAppState] + [-UserList ] + [-Version ] + [-WhatIf] + [] +``` + +### ExtensionFileStream +``` +New-App [-FileStream ] + [-AddInOverrides ] + [-AllowReadWriteMailbox] + [-AllowSetting ] + [-AppState ] + [-AppType ] + [-Confirm] + [-DefaultStateForUser ] + [-DomainController ] + [-DownloadOnly] + [-Enabled ] + [-Identity ] + [-Mailbox ] + [-OrganizationApp] + [-PrivateCatalog] + [-ProvidedTo ] + [-UpdateAppState] + [-UserList ] + [-Version ] + [-WhatIf] + [] +``` + +### ExtensionPrivateURL +``` +New-App [-Url ] + [-AddInOverrides ] + [-AllowReadWriteMailbox] + [-AllowSetting ] + [-AppState ] + [-AppType ] + [-Confirm] + [-DefaultStateForUser ] + [-DomainController ] + [-DownloadOnly] + [-Enabled ] + [-Identity ] + [-Mailbox ] + [-OrganizationApp] + [-PrivateCatalog] + [-ProvidedTo ] + [-UpdateAppState] + [-UserList ] + [-Version ] + [-WhatIf] + [] +``` + +## DESCRIPTION +If the app is enabled for the entire organization, users can activate the new app when viewing mail or calendar items within Microsoft Outlook or Outlook on the web. If an installed app isn't enabled, users can enable the app from Outlook on the web Options. Similarly, administrators can enable installed apps from the Exchange admin center or by using the Enable-App or Set-App cmdlet. + +For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-App -FileData ([System.IO.File]::ReadAllBytes('C:\Apps\FinanceTestApp.xml')) +``` + +This example installs the Finance Test app manifest file that has been copied to the local hard disk. + +### Example 2 +```powershell +New-App -OrganizationApp -Url https://Server01.Contoso.com/apps/ContosoCRMApp/manifest.xml -ProvidedTo SpecificUsers -UserList "user1,user2,user3,user4,user5" -DefaultStateForUser Enabled +``` + +This example installs the Contoso CRM app manifest.xml from a URL on the Contoso corporate network. The Exchange server must be able to reach the target URL. This app is installed as an organization app,is made available to a specific list of users, and is enabled for those users by default. + +## PARAMETERS + +### -AddInOverrides +This parameter is available only in the cloud-based service. + +{{ Fill AddInOverrides Description }} + +```yaml +Type: AddInOverrides +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowReadWriteMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSetting +This parameter is available only in the cloud-based service. + +{{ Fill AllowSetting Description }} + +```yaml +Type: AllowSetting +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppState +This parameter is available only in the cloud-based service. + +{{ Fill AppState Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppType +This parameter is available only in the cloud-based service. + +{{ Fill AppType Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultStateForUser +The DefaultStateForUser parameter specifies the default initial state of an organization app. Valid values are: + +- Enabled: The organization app is enabled by default. +- Disabled: The organization app is disabled by default. This is the default value. +- AlwaysEnabled: The organization app is enabled and users can't disable it. + +You need to use the OrganizationApp switch when you use this parameter. + +```yaml +Type: DefaultStateForUser +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DownloadOnly +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. +- $false: The app is hidden from all users in the organization. + +This setting overrides the ProvidedTo, UserList and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Etoken +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: ExtensionFileData +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileStream +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter is available only in the cloud-based service. + +{{ Fill Identity Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mailbox +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarketplaceAssetID +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarketplaceCorrelationID +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarketplaceQueryMarket +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarketplaceServicesUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarketplaceUserProfileType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationApp +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivateCatalog +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProvidedTo +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. +- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. + +You use this parameter with the OrganizationApp switch. + +```yaml +Type: ClientExtensionProvidedTo +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateAppState +This parameter is available only in the cloud-based service. + +{{ Fill UpdateAppState Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Url +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserList +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +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"`. + +You use this parameter with the OrganizationApp switch. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Version +This parameter is available only in the cloud-based service. + +{{ Fill Version Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/New-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md new file mode 100644 index 0000000000..669e94235e --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md @@ -0,0 +1,398 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AppRetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-AppRetentionCompliancePolicy to create app retention compliance policies. App retention & labeling policies target new ways to scope and manage policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AdaptiveScopeLocation +``` +New-AppRetentionCompliancePolicy [-Name] -AdaptiveScopeLocation -Applications + [-Confirm] + [-Comment ] + [-Enabled ] + [-Force] + [-RestrictiveRetention ] + [-WhatIf] + [] +``` + +### Default +``` +New-AppRetentionCompliancePolicy [-Name] -Applications + [-Comment ] + [-Confirm] + [-Enabled ] + [-ExchangeLocation ] + [-ExchangeLocationException ] + [-Force] + [-ModernGroupLocation ] + [-ModernGroupLocationException ] + [-PolicyRBACScopes ] + [-RestrictiveRetention ] + [-WhatIf] + [] +``` + +## DESCRIPTION +\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies in the locations described in [Retention cmdlets for newer locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-newer-locations). You can only set the list of included or excluded scopes for all included workloads, which means you likely need to create one policy per workload. + +\*-RetentionCompliance\* cmdlets continue to primarily support the locations described in [Retention cmdlets for older locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-older-locations). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AppRetentionCompliancePolicy -Name "Regulation 567 Compliance" -Applications "User:MicrosoftTeams,VivaEngage","Group:MicrosoftTeams,VivaEngage" -ExchangeLocation "Jennifer Petersen","Kitty Nakamura" +``` + +This example creates a static scope retention policy named Regulation 567 Compliance for the Viva Engage user messages of Jennifer Petersen and Kitty Nakamura. + +After you create the retention policy, use the New-AppRetentionComplianceRule cmdlet to create a retention rule and assign it the retention policy to it. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdaptiveScopeLocation +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Applications +The Applications parameter specifies the applications to include in the policy. + +This parameter uses the following syntax: `"LocationType:App1,LocationType:App2,...LocationType:AppN`: + +`LocationType` is User or Group. + +`App` is a supported value as shown in the following examples. + +- **Microsoft 365 apps**: For example: + + `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:VivaEngage"` + +- **Microsoft Copilot experiences**: Currently in Preview. You must use *all* of the following values at the same time: + + `"User:M365Copilot,CopilotForSecurity,CopilotinFabricPowerBI,CopilotStudio,CopilotinBusinessApplicationplatformsSales,SQLCopilot"` + + **Note**: Even though you must use `CopilotinBusinessApplicationplatformsSales` and `SQLCopilot`, those values are currently irrelevant. + +- **Enterprise AI apps**: Currently in Preview. You must use *all* of the following values at the same time: + + `"User:Entrabased3PAIApps,ChatGPTEnterprise,AzureAIServices"` + +- **Other AI apps**: Currently in Preview. You must use *all* of the following values at the same time: + + `"User:CloudAIAppChatGPTConsumer,CloudAIAppGoogleGemini,BingConsumer,DeepSeek"` + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter enables or disables the policy. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). +- The value All for all mailboxes. You can only use this value by itself. + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocationException +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 +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModernGroupLocation +The ModernGroupLocation parameter specifies the Microsoft 365 Groups to include in the policy. Valid values are: + +- A Microsoft 365 Group +- The value All for all Microsoft 365 Groups. You can only use this value by itself. + +To identify the Microsoft 365 Group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModernGroupLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +**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. + +Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictiveRetention +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. +- $false: Preservation Lock isn't enabled for the policy. This is the default value. + +After a policy has been locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. + +Therefore, before you lock a policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md b/exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md new file mode 100644 index 0000000000..9cf40c975c --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md @@ -0,0 +1,325 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AppRetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-AppRetentionComplianceRule to create app retention compliance rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +New-AppRetentionComplianceRule [-Name] -Policy + [-Comment ] + [-Confirm] + [-ContentMatchQuery ] + [-ExcludedItemClasses ] + [-ExpirationDateOption ] + [-RetentionComplianceAction ] + [-RetentionDuration ] + [-RetentionDurationDisplayHint ] + [-WhatIf] + [] +``` + +### ComplianceTag +``` +New-AppRetentionComplianceRule -Policy + [-Confirm] + [-ContentContainsSensitiveInformation ] + [-ContentMatchQuery ] + [-ExpirationDateOption ] + [-MachineLearningModelIDs ] + [-RetentionComplianceAction ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AppRetentionComplianceRule -Name RetUnlimited -Policy "Regulation 567 Compliance" -RetentionDuration Unlimited +``` + +This example creates a new retention rule named RetUnlimited and adds it to the retention policy named Regulation 567 Compliance. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +```yaml +Type: PswsHashtable[] +Parameter Sets: ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: Default, ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedItemClasses +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 +- IPM.Note.Microsoft.Conversation.Voice +- IPM.Note.Microsoft.Missed +- IPM.Note.Microsoft.Missed.Voice +- IPM.Note.Microsoft.Voicemail +- IPM.Note.Microsoft.VoiceMessage.UA +- IPM.Note.Microsoft.Voicemail.UM +- IPM.Note.Microsoft.Voicemail.UM.CA + +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or third-party message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. + +You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpirationDateOption +The ExpirationDateOption parameter specifies whether the expiration date is calculated from the content creation date or last modification date. Valid values are: + +- CreationAgeInDays +- ModificationAgeInDays + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MachineLearningModelIDs +{{ Fill MachineLearningModelIDs Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionComplianceAction +The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: + +- Delete +- Keep +- KeepAndDelete + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies the hold duration for the retention rule. Valid values are: + +- An integer: The hold duration in days. +- Unlimited: The content is held indefinitely. + +```yaml +Type: Unlimited +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDurationDisplayHint +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 +- Months +- Years + +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. + +```yaml +Type: HoldDurationHint +Parameter Sets: Default +Aliases: +Accepted values: Days, Months, Years +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md new file mode 100644 index 0000000000..3a8139e536 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md @@ -0,0 +1,228 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ApplicationAccessPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +> [!IMPORTANT] +> App Access Policies will soon be replaced by Role Based Access Control for Applications. To learn more, see [Role Based Access Control for Exchange Applications](https://learn.microsoft.com/exchange/permissions-exo/application-rbac). + +Use the New-ApplicationAccessPolicy cmdlet to restrict or deny access to a specific set of mailboxes by an application that uses APIs (Outlook REST, Microsoft Graph, or Exchange Web Services (EWS)). These policies are complementary to the permission scopes that are declared by the application. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX +``` +New-ApplicationAccessPolicy -AccessRight -AppId -PolicyScopeGroupId + [-Confirm] + [-Description ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +You can create a limited number of policies in your organization based on a fixed amount of space. If your organization runs out of space for these policies, you'll see the error: "The total size of App Access Policies exceeded the limit." To maximize the number of policies and reduce the amount of space that's consumed by the policies, set a one space character description for the policy. This method will allow approximately 300 policies (versus a previous limit of 100 policies). + +While scope-based resource access like Mail.Read or Calendar.Read is effective to ensure that the application can only read email or events within a mailbox and not do anything else, application access policies allow admins to enforce limits that are based on a list of mailboxes. For example, apps developed for one country/region shouldn't have access to data from other countries/regions. Or, or a CRM integration application should only access calendars in the Sales organization and no other departments. + +Every API request using the Outlook REST APIs or Microsoft Graph APIs to a target mailbox done by an application is verified using the following rules (in the same order): + +1. If there are multiple application access policies for the same Application and Target Mailbox pair, DenyAccess policy is prioritized over a RestrictAccess policy. +2. If a DenyAccess policy exists for the Application and Target Mailbox, then the app's access request is denied (even if there exists a RestrictAccess policy). +3. If there are any RestrictAccess policies that match the Application and Target Mailbox, then the app is granted access. +4. If there are any Restrict policies for the Application, and the Target Mailbox is not a member of those policies, then application is denied access to the target mailbox. +5. If none of the above conditions are met, then the application is granted access to the requested target mailbox. + +## EXAMPLES + +### Example 1 +```powershell +New-ApplicationAccessPolicy -AccessRight DenyAccess -AppId "3dbc2ae1-7198-45ed-9f9f-d86ba3ec35b5", "6ac794ca-2697-4137-8754-d2a78ae47d93" -PolicyScopeGroupId "Engineering Staff" -Description "Engineering Group Policy" +``` + +This example creates a new application access policy with the following settings: + +- AccessRight: DenyAccess +- AppIDs: 3dbc2ae1-7198-45ed-9f9f-d86ba3ec35b5 and 6ac794ca-2697-4137-8754-d2a78ae47d93 +- PolicyScopeGroupId: Engineering Staff +- Description: Engineering Group Policy + +### Example 2 +```powershell +New-ApplicationAccessPolicy -AccessRight RestrictAccess -AppId "e7e4dbfc-046f-4074-9b3b-2ae8f144f59b" -PolicyScopeGroupId EvenUsers@AppPolicyTest2.com -Description "Restrict this app's access to members of security group EvenUsers." +``` + +This example creates a new application access policy with the following settings: + +- AccessRight: RestrictAccess +- AppIDs: e7e4dbfc-046f-4074-9b3b-2ae8f144f59b +- PolicyScopeGroupId: EvenUsers@AppPolicyTest2.com +- Description: Restrict this app's access to members of security group EvenUsers. + +### Example 3 +```powershell +New-ApplicationAccessPolicy -AccessRight DenyAccess -AppId "e7e4dbfc-046f-4074-9b3b-2ae8f144f59b" -PolicyScopeGroupId OddUsers@AppPolicyTest2.com -Description "Deny this app access to members of security group OddUsers." +``` + +This example creates a new application access policy with the following settings: + +- AccessRight: DenyAccess +- AppIDs: e7e4dbfc-046f-4074-9b3b-2ae8f144f59b +- PolicyScopeGroupId: OddUsers@AppPolicyTest2.com +- Description: Deny this app access to members of security group OddUsers. + +## PARAMETERS + +### -AccessRight +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. +- DenyAccess: Allows the associated app to only access data that's not associated with mailboxes specified by the PolicyScopeGroupID parameter. + +```yaml +Type: ApplicationAccessPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppId +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PolicyScopeGroupID +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) +- Mail users, also known as mail-enabled users (MailUser) +- Mail-enabled security groups (MailUniversalSecurityGroup) + +You can use any value that uniquely identifies the recipient. For example: + +- Name +- Distinguished name (DN) +- Display name +- Email address +- GUID + +To verify that a recipient is a security principal, run either of the following commands: `Get-Recipient -Identity | Select-Object IsValidSecurityPrincipal` or `Get-Recipient -ResultSize unlimited | Format-Table -Auto Name,RecipientType,RecipientTypeDetails,IsValidSecurityPrincipal`. + +You can't use recipients that aren't security principals with this parameter. For example, the following types of recipients won't work: + +- Discovery mailboxes (DiscoveryMailbox) +- Dynamic distribution groups (DynamicDistributionGroup) +- Distribution groups (MailUniversalDistributionGroup) +- Mail contacts (MailContact) +- Mail-enabled public folders (PublicFolder) +- Microsoft 365 Groups (GroupMailbox) +- Resource mailboxes (RoomMailbox or EquipmentMailbox) +- Shared mailboxes (SharedMailbox) + +If you need to scope the policy to shared mailboxes, you can add the shared mailboxes as members of a mail-enabled security group. + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-AuthRedirect.md b/exchange/exchange-ps/exchange/New-AuthRedirect.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/New-AuthRedirect.md rename to exchange/exchange-ps/exchange/New-AuthRedirect.md index 1f3dd12e27..d885bf6957 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-AuthRedirect.md +++ b/exchange/exchange-ps/exchange/New-AuthRedirect.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-authredirect +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-AuthRedirect @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the New-AuthRedirect cmdlet to create OAuth redirection objects that are used for legacy Microsoft Exchange 2010 Client Access servers in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-AuthRedirect -AuthScheme -TargetUrl [-Confirm] [-DomainController ] - [-WhatIf] [] +New-AuthRedirect -AuthScheme -TargetUrl + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Exchange 2010 Client Access servers don't support OAuth authentication requests. Use this cmdlet to redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,8 +43,7 @@ New-AuthRedirect -AuthScheme Bearer -TargetURL https://mbx01.contoso.com This example creates an OAuth redirection object with the following settings: - AuthScheme: Bearer - -- TargetURL: https://mbx01.contoso.com +- TargetURL: `https://mbx01.contoso.com` ## PARAMETERS @@ -63,7 +64,7 @@ Accept wildcard characters: False ``` ### -TargetUrl -The TargetUrl parameter specifies the FQDN of the Exchange 2013 or later server that has the Client Access server role installed that's responsible for processing the redirected OAuth authentication requests. +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 @@ -81,8 +82,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -135,12 +135,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/New-AuthServer.md b/exchange/exchange-ps/exchange/New-AuthServer.md similarity index 79% rename from exchange/exchange-ps/exchange/organization/New-AuthServer.md rename to exchange/exchange-ps/exchange/New-AuthServer.md index 1ca0f1ca34..5837e8cdb9 100644 --- a/exchange/exchange-ps/exchange/organization/New-AuthServer.md +++ b/exchange/exchange-ps/exchange/New-AuthServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/new-authserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-AuthServer @@ -17,41 +16,50 @@ This cmdlet is available only in on-premises Exchange. Use the New-AuthServer cmdlet to create an authorization server object in Microsoft Exchange and specify its AuthMetadataUrl. Exchange honors tokens issued by the authorization server for access by a partner application. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### AuthMetadataUrl ``` -New-AuthServer [-Name] -AuthMetadataUrl [-TrustAnySSLCertificate] +New-AuthServer [-Name] -AuthMetadataUrl + [-TrustAnySSLCertificate] [-Confirm] [-DomainController ] + [-DomainName ] [-Enabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### NativeClientAuthServer ``` -New-AuthServer [-Name] -AuthMetadataUrl -Type [-TrustAnySSLCertificate] +New-AuthServer [-Name] -AuthMetadataUrl -Type + [-TrustAnySSLCertificate] [-Confirm] [-DomainController ] + [-DomainName ] [-Enabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AppSecret ``` New-AuthServer [-Name] -Type + [-ApplicationIdentifier ] [-Confirm] [-DomainController ] + [-DomainName ] [-Enabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Partner applications authorized by Exchange can access their resources after they're authenticated using server-to-server authentication. A partner application can authenticate by using self-issued tokens trusted by Exchange or by using an authorization server trusted by Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -81,7 +89,7 @@ Accept wildcard characters: False ``` ### -AuthMetadataUrl -The AuthMetadataUrl parameter specifies the URL for the Office 365 authorization server for your cloud-based organization. For details, see the Office 365 documentation. +The AuthMetadataUrl parameter specifies the URL for the Microsoft 365 authorization server for your cloud-based organization. ```yaml Type: String @@ -100,13 +108,9 @@ Accept wildcard characters: False The Type parameter specifies the type of authorization tokens that are issued by the authorization server. Valid values are: - ADFS - - AzureAD - - Facebook - - LinkedIn - - MicrosoftACS ```yaml @@ -122,11 +126,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ApplicationIdentifier +This parameter is available in the April 18, 2025 Hotfix update (HU) for Exchange 2019 CU15 and Exchange 2016 CU23. + +{{ Fill ApplicationIdentifier Description }} + +```yaml +Type: String +Parameter Sets: AppSecret +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -158,12 +179,27 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DomainName +{{ Fill DomainName Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + ### -Enabled 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 - -- $false: Authorization tokens that are issued by the authorization server are are not accepted. +- $false: Authorization tokens that are issued by the authorization server are not accepted. ```yaml Type: Boolean @@ -179,7 +215,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether Exchange should accept certificates from an untrusted certification authority. You don't need to specify a value with this switch. +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. @@ -217,12 +253,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/New-AuthenticationPolicy.md new file mode 100644 index 0000000000..4c06f72d1a --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AuthenticationPolicy.md @@ -0,0 +1,731 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AuthenticationPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-AuthenticationPolicy cmdlet to create authentication policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-AuthenticationPolicy [[-Name] ] + [-AllowBasicAuthActiveSync] + [-AllowBasicAuthAutodiscover] + [-AllowBasicAuthImap] + [-AllowBasicAuthMapi] + [-AllowBasicAuthOfflineAddressBook] + [-AllowBasicAuthOutlookService] + [-AllowBasicAuthPop] + [-AllowBasicAuthPowershell] + [-AllowBasicAuthReportingWebServices] + [-AllowBasicAuthRpc] + [-AllowBasicAuthSmtp] + [-AllowBasicAuthWebServices] + [-BlockLegacyAuthActiveSync] + [-BlockLegacyAuthAutodiscover] + [-BlockLegacyAuthImap] + [-BlockLegacyAuthMapi] + [-BlockLegacyAuthOfflineAddressBook] + [-BlockLegacyAuthPop] + [-BlockLegacyAuthRpc] + [-BlockLegacyAuthWebServices] + [-BlockModernAuthActiveSync] + [-BlockModernAuthAutodiscover] + [-BlockModernAuthImap] + [-BlockModernAuthMapi] + [-BlockModernAuthOfflineAddressBook] + [-BlockModernAuthPop] + [-BlockModernAuthRpc] + [-BlockModernAuthWebServices] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AuthenticationPolicy -Name "Engineering Group" -AllowBasicAuthImap +``` + +In Exchange Online, this example creates a new authentication policy named Engineering Group that allows Basic authentication with IMAP. + +### Example 2 +```powershell +New-AuthenticationPolicy -Name "Research and Development Group" -BlockLegacyAuthActiveSync -BlockLegacyAuthAutodiscover -BlockLegacyAuthImap -BlockLegacyAuthMapi -BlockLegacyAuthOfflineAddressBook -BlockLegacyAuthPop -BlockLegacyAuthRpc -BlockLegacyAuthWebServices +``` + +In Exchange 2019, this example creates a new authentication policy named Research and Development Group that blocks legacy authentication for the specified protocols. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthActiveSync +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthAutodiscover +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthImap +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthMapi +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthOfflineAddressBook +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthOutlookService +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthPop +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthPowershell +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthReportingWebServices +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthRpc +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthSmtp +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthWebServices +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. + +By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthActiveSync +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. + +This switch disables the following legacy authentication methods with Exchange ActiveSync: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthAutodiscover +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. + +This switch disables the following legacy authentication methods with Autodiscover: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthImap +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. + +This switch disables the following legacy authentication methods with IMAP: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthMapi +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. + +This switch disables the following legacy authentication methods with MAPI: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthOfflineAddressBook +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. + +This switch disables the following legacy authentication methods with Offline Address Books: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthPop +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. + +This switch disables the following legacy authentication methods with POP: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthRpc +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. + +This switch disables the following legacy authentication methods with RPC: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthWebServices +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. + +This switch disables the following legacy authentication methods with EWS: + +- Basic authentication +- Digest authentication +- Windows authentication (NTLM and Kerberos) + +Before you disable the legacy authentication methods for this protocol, verify that hybrid modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support modern authentication. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthActiveSync +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthAutodiscover +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthImap +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthMapi +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthOfflineAddressBook +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthPop +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthRpc +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthWebServices +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md new file mode 100644 index 0000000000..41c5654713 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md @@ -0,0 +1,692 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AutoSensitivityLabelPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-AutoSensitivityLabelPolicy cmdlet to create auto-labeling policies in your organization. Create auto-labeling policy rules using the New-AutoSensitivityLabelRule cmdlet and associate them with the policy to complete the policy creation. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-AutoSensitivityLabelPolicy [-Name] -ApplySensitivityLabel + [-Comment ] + [-Confirm] + [-ExceptIfOneDriveSharedBy ] + [-ExceptIfOneDriveSharedByMemberOf ] + [-ExchangeAdaptiveScopes ] + [-ExchangeAdaptiveScopesException ] + [-ExchangeLocation ] + [-ExchangeSender ] + [-ExchangeSenderException ] + [-ExchangeSenderMemberOf ] + [-ExchangeSenderMemberOfException ] + [-ExternalMailRightsManagementOwner ] + [-Force] + [-Locations ] + [-Mode ] + [-OneDriveAdaptiveScopes ] + [-OneDriveAdaptiveScopesException ] + [-OneDriveLocation ] + [-OneDriveLocationException ] + [-OneDriveSharedBy ] + [-OneDriveSharedByMemberOf ] + [-OverwriteLabel ] + [-PolicyRBACScopes ] + [-PolicyTemplateInfo ] + [-Priority ] + [-SharePointAdaptiveScopes ] + [-SharePointAdaptiveScopesException ] + [-SharePointLocation ] + [-SharePointLocationException ] + [-UnifiedAuditLogEnabled ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AutoSensitivityLabelPolicy -Name "GlobalPolicy" -Comment "Primary policy" -SharePointLocation "https://my.url/","https://my.url2/" -OneDriveLocation "https://my.url3/","https://my.url4/" -Mode TestWithoutNotifications -ApplySensitivityLabel "Test" +``` + +This example creates an auto-labeling policy named GlobalPolicy for the specified SharePoint and OneDrive locations with the label "Test". The new policy has a descriptive comment and will be in simulation mode on creation. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplySensitivityLabel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedBy +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). + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the OneDriveSharedBy parameter. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedByMemberOf +{{ Fill ExceptIfOneDriveSharedByMemberOf Description }} + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopes +{{ Fill ExchangeAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopesException +{{ Fill ExchangeAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +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: + +- If you use `-ExchangeLocation All` by itself, the policy applies to email for all internal users. + +- To include email of specific internal or external users in the policy, use `-ExchangeLocation All` with the ExchangeSender parameter in the same command. Only email of the specified users is included in the policy. + +- To include only email of specific group members in the policy, use `-ExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the policy. + +- To exclude email of specific internal users from the policy, use `-ExchangeLocation All` with the ExchangeSenderException parameter in the same command. Only email of the specified users is excluded from the policy. + +- To exclude only email of specific group members from the policy, use `-ExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the policy. + +You can't specify inclusions and exclusions in the same policy. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSender +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: `"","",...""`. + +You must use this parameter with the ExchangeLocation parameter. + +You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderException +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: `"","",...""`. + +You must use this parameter with the ExchangeLocation parameter. + +You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOf +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: `"","",...""`. + +You must use this parameter with the ExchangeLocation parameter. + +You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOfException +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: `"","",...""`. + +You must use this parameter with the ExchangeLocation parameter. + +You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalMailRightsManagementOwner +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. + +```yaml +Type: SmtpAddress +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locations +{{ Fill Locations Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mode +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. +- Disable: The policy is disabled. +- TestWithNotifications: No actions are taken, but notifications are sent. +- TestWithoutNotifications: An audit mode where no actions are taken, and no notifications are sent. + +```yaml +Type: PolicyMode +Parameter Sets: (All) +Aliases: +Accepted values: Enable, TestWithNotifications, TestWithoutNotifications, Disable, PendingDeletion +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopes +{{ Fill OneDriveAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopesException +{{ Fill OneDriveAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedBy +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). + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the ExceptIfOneDriveSharedBy parameter. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedByMemberOf +{{ Fill OneDriveSharedByMemberOf Description }} + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverwriteLabel +The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are: + +- $true: Overwrite the manual label. +- $false: Don't overwrite the manual label. This is the default value. + +This parameter works only on Exchange locations. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTemplateInfo +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopes +{{ Fill SharePointAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopesException +{{ Fill SharePointAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnifiedAuditLogEnabled +{{ Fill UnifiedAuditLogEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md new file mode 100644 index 0000000000..43a5384ec8 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md @@ -0,0 +1,1281 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AutoSensitivityLabelRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-AutoSensitivityLabelRule cmdlet to create auto-labeling rules and associate then with auto-labeling policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-AutoSensitivityLabelRule [-Name] -Policy -Workload + [-AccessScope ] + [-ActivationDate ] + [-AnyOfRecipientAddressContainsWords ] + [-AnyOfRecipientAddressMatchesPatterns ] + [-Comment ] + [-Confirm] + [-ContentContainsSensitiveInformation ] + [-ContentExtensionMatchesWords ] + [-ContentPropertyContainsWords ] + [-Disabled ] + [-DocumentCreatedBy ] + [-DocumentIsPasswordProtected ] + [-DocumentIsUnsupported ] + [-DocumentNameMatchesWords ] + [-DocumentSizeOver ] + [-ExceptIfAccessScope ] + [-ExceptIfAnyOfRecipientAddressContainsWords ] + [-ExceptIfAnyOfRecipientAddressMatchesPatterns ] + [-ExceptIfContentContainsSensitiveInformation ] + [-ExceptIfContentExtensionMatchesWords ] + [-ExceptIfContentPropertyContainsWords ] + [-ExceptIfDocumentCreatedBy ] + [-ExceptIfDocumentIsPasswordProtected ] + [-ExceptIfDocumentIsUnsupported ] + [-ExceptIfDocumentNameMatchesWords ] + [-ExceptIfDocumentSizeOver ] + [-ExceptIfFrom ] + [-ExceptIfFromAddressContainsWords ] + [-ExceptIfFromAddressMatchesPatterns ] + [-ExceptIfFromMemberOf ] + [-ExceptIfHeaderMatchesPatterns ] + [-ExceptIfProcessingLimitExceeded ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSenderDomainIs ] + [-ExceptIfSenderIPRanges ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-ExceptIfSubjectMatchesPatterns ] + [-ExpiryDate ] + [-From ] + [-FromAddressContainsWords ] + [-FromAddressMatchesPatterns ] + [-FromMemberOf ] + [-HeaderMatchesPatterns ] + [-ImmutableId ] + [-Priority ] + [-ProcessingLimitExceeded ] + [-RecipientDomainIs ] + [-ReportSeverityLevel ] + [-RuleErrorAction ] + [-SenderDomainIs ] + [-SenderIPRanges ] + [-SentTo ] + [-SentToMemberOf ] + [-SourceType ] + [-SubjectMatchesPatterns ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AutoSensitivityLabelRule -Name "SocialSecurityRule" -Policy "SSNPolicy" -ContentContainsSensitiveInformation @{"name"="U.S. Social Security Number (SSN)";"mincount"="1"} -Workload SharePoint +``` + +This example creates an autolabeling rule named "SocialSecurityRule" that is assigned to the policy "SSNPolicy." This rule looks for Social Security Numbers on documents with a minimum count of 1 on SharePoint sites. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Workload +The Workload parameter specifies the workload. Valid values are: + +- Exchange +- OneDriveForBusiness +- SharePoint + +```yaml +Type: Workload +Parameter Sets: (All) +Aliases: +Accepted values: Exchange, SharePoint, OneDriveForBusiness +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessScope +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. +- NotInOrganization: The rule is applied to content that's accessible outside the organization. +- None: The condition isn't used. + +```yaml +Type: AccessScope +Parameter Sets: (All) +Aliases: +Accepted values: InOrganization, NotInOrganization, None +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActivationDate +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressMatchesPatterns +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. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})`. + +Exact Data Match sensitive information types are supported only groups. For example: + +`@(@{operator="And"; groups=@(@{name="Default"; operator="Or"; sensitivetypes=@(@{id="<>"; name="<>"; maxcount="-1"; classifiertype="ExactMatch"; mincount="100"; confidencelevel="Medium"})})})` + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter specifies whether the auto-labeling policy rule is enabled or disabled. Valid values are: + +- $true: The rule is disabled. +- $false: The rule is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentCreatedBy +{{ Fill DocumentCreatedBy Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this condition in auto-labeling policy rules that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAccessScope +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. +- NotInOrganization: The rule isn't applied to content that's accessible outside the organization. +- None: The exception isn't used. + +```yaml +Type: AccessScope +Parameter Sets: (All) +Aliases: +Accepted values: InOrganization, NotInOrganization, None +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressMatchesPatterns +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. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentContainsSensitiveInformation +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"})`. + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentCreatedBy +{{ Fill ExceptIfDocumentCreatedBy Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this exception in auto-labeling policy rules that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFrom +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressMatchesPatterns +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. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromMemberOf +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"`. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectMatchesPatterns +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. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpiryDate +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -From +This parameter is reserved for internal Microsoft use. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressMatchesPatterns +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. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromMemberOf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImmutableId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportSeverityLevel +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. +- Low: This is the default value. +- Medium +- High + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Accepted values: Low, Medium, High, None, Informational, Information +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RuleErrorAction +The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: + +- Ignore +- RetryThenBlock +- Blank (the value $null): This is the default value. + +```yaml +Type: PolicyRuleErrorAction +Parameter Sets: (All) +Aliases: +Accepted values: Ignore, RetryThenBlock +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +You can use this condition in auto-sensitivity policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceType +{{ Fill SourceType Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectMatchesPatterns +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. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access-servers/New-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md index cee4c0ffd4..d79e23f643 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-autodiscovervirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-AutodiscoverVirtualDirectory @@ -17,18 +16,30 @@ This cmdlet is available only in on-premises Exchange. Use the New-AutodiscoverVirtualDirectory cmdlet to create Autodiscover virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-AutodiscoverVirtualDirectory [-ApplicationRoot ] [-AppPoolId ] - [-BasicAuthentication ] [-Confirm] [-DigestAuthentication ] - [-DomainController ] [-ExtendedProtectionFlags ] - [-ExtendedProtectionSPNList ] [-ExtendedProtectionTokenChecking ] - [-ExternalUrl ] [-InternalUrl ] [-Path ] [-WebSiteName ] [-WhatIf] - [-WindowsAuthentication ] [-WSSecurityAuthentication ] - [-OAuthAuthentication ] [-Role ] [-Server ] +New-AutodiscoverVirtualDirectory [-ApplicationRoot ] + [-AppPoolId ] + [-BasicAuthentication ] + [-Confirm] + [-DigestAuthentication ] + [-DomainController ] + [-ExtendedProtectionFlags ] + [-ExtendedProtectionSPNList ] + [-ExtendedProtectionTokenChecking ] + [-ExternalUrl ] + [-InternalUrl ] + [-OAuthAuthentication ] + [-Path ] + [-Role ] + [-Server ] + [-WebSiteName ] + [-WhatIf] + [-WindowsAuthentication ] + [-WSSecurityAuthentication ] [] ``` @@ -37,7 +48,7 @@ If your organization has multiple email domains and each requires its own Autodi When you're creating an Autodiscover virtual directory, we recommend that you enable Secure Sockets Layer (SSL) for the Autodiscover service. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -86,7 +97,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. ```yaml @@ -105,8 +115,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,7 +135,6 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. - - $false: Digest authentication is disabled. This is the default value. ```yaml @@ -162,13 +170,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -188,8 +192,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -208,14 +211,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -231,7 +230,7 @@ Accept wildcard characters: False ``` ### -ExternalUrl -This parameter is available or functional only in 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. @@ -249,7 +248,7 @@ Accept wildcard characters: False ``` ### -InternalUrl -This parameter is available or functional only in 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. @@ -266,14 +265,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Path -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. +### -OAuthAuthentication +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. +- $false: OAuth authentication is disabled. ```yaml -Type: String +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -282,8 +284,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WebSiteName -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. +### -Path +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 @@ -298,14 +300,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -Role +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. +- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. + +Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. ```yaml -Type: SwitchParameter +Type: VirtualDirectoryRole Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -314,35 +321,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WindowsAuthentication -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. +### -Server +The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example: -- $false: Integrated Windows authentication is disabled. +- Name +- FQDN +- Distinguished name (DN) +- ExchangeLegacyDN ```yaml -Type: Boolean +Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -WSSecurityAuthentication -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. - -- $false: WS-Security authentication is disabled. +### -WebSiteName +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: Boolean +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -354,18 +358,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OAuthAuthentication -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. - -- $false: OAuth authentication is disabled. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: Boolean +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -374,20 +374,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Role -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. - -- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. +### -WindowsAuthentication +The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. +- $true: Integrated Windows authentication is enabled. This is the default value. +- $false: Integrated Windows authentication is disabled. ```yaml -Type: VirtualDirectoryRole +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -396,27 +393,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Server -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 - -- FQDN - -- Distinguished name (DN) +### -WSSecurityAuthentication +The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are: -- ExchangeLegacyDN +- $true: WS-Security authentication is enabled. This is the default value. +- $false: WS-Security authentication is disabled. ```yaml -Type: ServerIdParameter +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -425,12 +417,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-AvailabilityConfig.md b/exchange/exchange-ps/exchange/New-AvailabilityConfig.md new file mode 100644 index 0000000000..7019d149b7 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-AvailabilityConfig.md @@ -0,0 +1,128 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-AvailabilityConfig + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-AvailabilityConfig cmdlet to create the availability configuration that specifies the Microsoft 365 organizations to exchange free/busy information with. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-AvailabilityConfig + [-AllowedTenantIds ] + [-Confirm] + [-OrgWideAccount ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-AvailabilityConfig -AllowedTenantIds "d6b0a40e-029b-43f2-9852-f3724f68ead9","87d5bade-cefc-4067-a221-794aea71922d" +``` + +This example creates a new availability configuration to share free/busy information with the specified Microsoft 365 organizations. + +## PARAMETERS + +### -AllowedTenantIds +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrgWideAccount +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/server-health-and-performance/New-AvailabilityReportOutage.md b/exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md similarity index 88% rename from exchange/exchange-ps/exchange/server-health-and-performance/New-AvailabilityReportOutage.md rename to exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md index 327d6c5e2e..4c31737bf7 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/New-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/new-availabilityreportoutage +online version: https://learn.microsoft.com/powershell/module/exchange/new-availabilityreportoutage applicable: Exchange Server 2010 title: New-AvailabilityReportOutage schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-AvailabilityReportOutage @@ -17,18 +16,22 @@ This cmdlet is available only in Exchange Server 2010. Use the New-AvailabilityReportOutage cmdlet to create an outage to add unrecorded issues to availability reporting. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-AvailabilityReportOutage [-SiteName] -Comment -DowntimeMinutes - -ReportDate [-Confirm] [-Force] [-ReportingDatabase ] [-ReportingServer ] [-WhatIf] +New-AvailabilityReportOutage [-SiteName] -Comment -DowntimeMinutes -ReportDate + [-Confirm] + [-Force] + [-ReportingDatabase ] + [-ReportingServer ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,8 +44,8 @@ This example creates a timed injected outage scoped to site Site1 on the selecte ## PARAMETERS -### -Comment -The Comment parameter specifies why the outage was inserted. +### -SiteName +The SiteName parameter specifies the name of the Active Directory site to associate the outage report with. ```yaml Type: String @@ -51,17 +54,17 @@ Aliases: Applicable: Exchange Server 2010 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -DowntimeMinutes -The DowntimeMinutes parameter specifies the number of minutes of downtime to insert into the outage report. +### -Comment +The Comment parameter specifies why the outage was inserted. ```yaml -Type: Double +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 @@ -73,11 +76,11 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ReportDate -The ReportDate parameter specifies the date to query for the outage report. +### -DowntimeMinutes +The DowntimeMinutes parameter specifies the number of minutes of downtime to insert into the outage report. ```yaml -Type: ExDateTime +Type: Double Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 @@ -89,17 +92,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SiteName -The SiteName parameter specifies the name of the Active Directory site to associate the outage report with. +### -ReportDate +The ReportDate parameter specifies the date to query for the outage report. ```yaml -Type: String +Type: ExDateTime Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -108,8 +111,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,7 +128,9 @@ Accept wildcard characters: False ``` ### -Force -The Force parameter suppresses the warning or confirmation messages that appear during specific configuration changes. +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. ```yaml Type: SwitchParameter @@ -194,12 +198,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/New-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/New-CaseHoldPolicy.md new file mode 100644 index 0000000000..87605314fc --- /dev/null +++ b/exchange/exchange-ps/exchange/New-CaseHoldPolicy.md @@ -0,0 +1,256 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-CaseHoldPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-CaseHoldPolicy cmdlet to create new case hold policies in the Microsoft Purview compliance portal. + +> [!NOTE] +> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold won't be created, and content locations won't be placed on hold**. +> +> Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to create multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchange/get-caseholdpolicy). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-CaseHoldPolicy [-Name] -Case + [-Comment ] + [-Confirm] + [-Enabled ] + [-ExchangeLocation ] + [-Force] + [-PublicFolderLocation ] + [-SharePointLocation ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-CaseHoldPolicy -Name "Regulation 123 Compliance" -Case "123 Compliance Case" -ExchangeLocation "Kitty Petersen", "Scott Nakamura" -SharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" +``` + +This example creates a case hold policy named "Regulation 123 Compliance" for the mailboxes of Kitty Petersen and Scott Nakamura, and the finance SharePoint site for the eDiscovery case named "123 Compliance Case". + +Remember, after you create the policy, you need to create a rule for the policy by using the New-CaseHoldRule cmdlet. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Case +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 +- Identity (GUID value). + +You can find these values by running the command: Get-ComplianceCase | Format-Table -Auto Name,Status,Identity. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use the following values: + +- Name +- SMTP address. To specify an inactive mailbox, precede the address with a period (.). +- Microsoft Entra ObjectId. Use the [Get-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/get-mguser) or [Get-MgGroup](https://learn.microsoft.com/powershell/module/microsoft.graph.groups/get-mggroup) cmdlets in Microsoft Graph PowerShell to find this 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"`. + +If no mailboxes are specified, then no mailboxes are placed on hold. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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"`. + +Sites can't be added to the policy until they have been indexed. If no sites are specified, then no sites are placed on hold. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-CaseHoldRule.md b/exchange/exchange-ps/exchange/New-CaseHoldRule.md new file mode 100644 index 0000000000..c169c5dfff --- /dev/null +++ b/exchange/exchange-ps/exchange/New-CaseHoldRule.md @@ -0,0 +1,189 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-CaseHoldRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-CaseHoldRule cmdlet to create new case hold rules in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-CaseHoldRule [-Name] -Policy + [-Comment ] + [-Confirm] + [-ContentMatchQuery ] + [-Disabled ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to add the case hold rule to an existing case hold policy using the Policy parameter. Only one rule can be added to each case hold policy. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-CaseHoldRule -Name "2016 Budget Spreadsheets" -Policy "Internal Company Policy" -ContentMatchQuery "filename:2016 budget filetype:xlsx" +``` + +This example creates a new case hold rule named 2016 Budget Spreadsheets and adds it to the existing case hold policy named "Internal Company Policy". The rule applies to Excel worksheets that contain the phrase 2016 budget, such as "2016 budget planning.xlsx" and "2016 budget review.xlsx" + +### Example 2 +```powershell +New-CaseHoldRule -Name "Contoso Case 07172018 Hold 1" -Policy "Contoso Case 07172018" -ContentMatchQuery "received:12/01/2017..12/31/2018" +``` + +This example places email messages received by the recipients between December 1, 2018 and December 31, 2018 on hold. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: + +- $true: The rule is disabled. +- $false: The rule is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-ClassificationRuleCollection.md b/exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md similarity index 80% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-ClassificationRuleCollection.md rename to exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md index a17f05a91d..2f589a0ceb 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-classificationrulecollection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-ClassificationRuleCollection @@ -17,25 +16,28 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-ClassificationRuleCollection cmdlet to import new classification rule collections into your organization. -In the Office 365 Security & Compliance Center, use the New-DlpSensitiveInformationTypeRulePackage cmdlet. +In tSecurity & Compliance PowerShell, use the New-DlpSensitiveInformationTypeRulePackage cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-ClassificationRuleCollection [-FileData] [-Confirm] [-DomainController ] [-WhatIf] +New-ClassificationRuleCollection [-FileData] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-ClassificationRuleCollection -FileData ([Byte[]]$(Get-Content -Path "C:\My Documents\External Classification Rule Collection.xml" -Encoding Byte -ReadCount 0)) +New-ClassificationRuleCollection -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\External Classification Rule Collection.xml')) ``` This example imports the classification rule collection file C:\\My Documents\\External Classification Rule Collection.xml. @@ -45,7 +47,7 @@ This example imports the classification rule collection file C:\\My Documents\\E ### -FileData 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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\" -ReadCount 0\)\). +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[] @@ -63,10 +65,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -119,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-ClientAccessArray.md b/exchange/exchange-ps/exchange/New-ClientAccessArray.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access-servers/New-ClientAccessArray.md rename to exchange/exchange-ps/exchange/New-ClientAccessArray.md index 2bbf9f34bc..93bc940c38 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-ClientAccessArray.md +++ b/exchange/exchange-ps/exchange/New-ClientAccessArray.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-clientaccessarray +online version: https://learn.microsoft.com/powershell/module/exchange/new-clientaccessarray applicable: Exchange Server 2010 title: New-ClientAccessArray schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-ClientAccessArray @@ -17,13 +16,16 @@ This cmdlet is available only in Exchange Server 2010. Use the New-ClientAccessArray cmdlet to create an object that represents a load balanced array of Client Access servers within a single Active Directory site. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-ClientAccessArray [[-Name] ] -Fqdn -Site [-Confirm] - [-DomainController ] [-WhatIf] [] +New-ClientAccessArray [[-Name] ] -Fqdn -Site + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ The New-ClientAccessArray cmdlet creates an object that represents a load balanc Client Access arrays allow Outlook clients in an Active Directory site to access the Client Access servers in the array by using RPC over TCP to a single, unified, fully qualified domain name (FQDN). The RpcClientAccessServer property of new mailbox databases is automatically populated with the FQDN of the Client Access array and this value is used during the creation of Outlook profiles for mailboxes in those databases. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,6 +53,24 @@ This example creates a Client Access array named China CAS Array with the FQDN v ## PARAMETERS +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Fqdn 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. @@ -68,12 +88,10 @@ Accept wildcard characters: False ``` ### -Site -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: +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 - - Distinguished name (DN) - - GUID To see a list of available sites, use the Get-ADSite cmdlet. @@ -94,8 +112,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -127,24 +144,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -166,13 +165,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### -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. +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/New-ClientAccessRule.md b/exchange/exchange-ps/exchange/New-ClientAccessRule.md new file mode 100644 index 0000000000..af5e934438 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ClientAccessRule.md @@ -0,0 +1,585 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ClientAccessRule + +## SYNOPSIS +> [!NOTE] +> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). + +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-ClientAccessRule cmdlet to create client access rules. Client access rules help you control access to your organization based on the properties of the connection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ClientAccessRule [-Name] -Action + [-AnyOfAuthenticationTypes ] + [-AnyOfClientIPAddressesOrRanges ] + [-AnyOfProtocols ] + [-AnyOfSourceTcpPortNumbers ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExceptAnyOfAuthenticationTypes ] + [-ExceptAnyOfClientIPAddressesOrRanges ] + [-ExceptAnyOfProtocols ] + [-ExceptAnyOfSourceTcpPortNumbers ] + [-ExceptUserIsMemberOf ] + [-ExceptUsernameMatchesAnyOfPatterns ] + [-Priority ] + [-Scope ] + [-UserIsMemberOf ] + [-UsernameMatchesAnyOfPatterns ] + [-UserRecipientFilter ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. + +**Note**: Not all protocols support authentication type filters, and even protocols that support authentication type filters don't support all authentication types. The supported combinations are described in the following lists. Use caution when mixing protocols and authentication types in the same rule. + +Protocols that support authentication type filters: + +- ExchangeActiveSync: BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. +- ExchangeAdminCenter: BasicAuthentication and AdfsAuthentication. +- IMAP4: BasicAuthentication and OAuthAuthentication. +- OutlookWebApp: BasicAuthentication and AdfsAuthentication. +- POP3: BasicAuthentication and OAuthAuthentication. +- RemotePowerShell: BasicAuthentication and NonBasicAuthentication. + +Protocols that don't support authentication type filters: + +- ExchangeWebServices +- OfflineAddressBook +- OutlookAnywhere +- PowerShellWebServices +- REST +- UniversalOutlook + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ClientAccessRule -Name AllowRemotePS -Action Allow -AnyOfProtocols RemotePowerShell -Priority 1 +``` + +This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you'll lose the ability to fix the rules yourself (you'll need to call Microsoft Customer Service and Support). + +### Example 2 +```powershell +New-ClientAccessRule -Name "Block ActiveSync" -Action DenyAccess -AnyOfProtocols ExchangeActiveSync -ExceptAnyOfClientIPAddressesOrRanges 192.168.10.1/24 +``` + +This example creates a new client access rule named Block ActiveSync that blocks access for Exchange ActiveSync clients, except for clients in the IP address range 192.168.10.1/24. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Action +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfAuthenticationTypes +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. + +Valid values for this parameter are: + +- AdfsAuthentication +- BasicAuthentication +- CertificateBasedAuthentication +- NonBasicAuthentication +- OAuthAuthentication + +You can enter multiple values separated by commas. Don't use quotation marks. + +**Note**: Refer to the Description section to see which authentication types can be used with what protocols. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfClientIPAddressesOrRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254 or 2001:DB8::2AA:FF:C0A8:640A-2001:DB8::2AA:FF:C0A8:6414. +- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.3.1/24 or 2001:DB8::2AA:FF:C0A8:640A/64. + +You can enter multiple values separated by commas. + +For more information about IPv6 addresses and syntax, see this Exchange 2013 topic: [IPv6 address basics](https://learn.microsoft.com/exchange/ipv6-support-in-exchange-2013-exchange-2013-help#ipv6-address-basics). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfProtocols +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: + +- ExchangeActiveSync +- ExchangeAdminCenter +- ExchangeWebServices +- IMAP4 +- OfflineAddressBook +- OutlookAnywhere +- OutlookWebApp +- POP3 +- PowerShellWebServices +- RemotePowerShell +- REST +- UniversalOutlook (Mail and Calendar app) + +**Note**: In Exchange 2019, the only supported values are ExchangeAdminCenter and RemotePowerShell. + +You can enter multiple values separated by commas. Don't use quotation marks. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfSourceTcpPortNumbers +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfAuthenticationTypes +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. + +Valid values for this parameter are: + +- AdfsAuthentication +- BasicAuthentication +- CertificateBasedAuthentication +- NonBasicAuthentication +- OAuthAuthentication + +You can enter multiple values separated by commas. Don't use quotation marks. + +**Note**: Refer to the Description section to see which authentication types can be used with what protocols. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfClientIPAddressesOrRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254 or 2001:DB8::2AA:FF:C0A8:640A-2001:DB8::2AA:FF:C0A8:6414. +- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.3.1/24 or 2001:DB8::2AA:FF:C0A8:640A/64. + +You can enter multiple values separated by commas. + +For more information about IPv6 addresses and syntax, see this Exchange 2013 topic: [IPv6 address basics](https://learn.microsoft.com/exchange/ipv6-support-in-exchange-2013-exchange-2013-help#ipv6-address-basics). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfProtocols +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. + +Valid values for this parameter are: + +- ExchangeActiveSync +- ExchangeAdminCenter +- ExchangeWebServices +- IMAP4 +- OfflineAddressBook +- OutlookAnywhere +- OutlookWebApp +- POP3 +- PowerShellWebServices +- RemotePowerShell +- REST +- UniversalOutlook (Mail and Calendar app) + +You can enter multiple values separated by commas. Don't use quotation marks. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfSourceTcpPortNumbers +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptUserIsMemberOf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptUsernameMatchesAnyOfPatterns +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. + +You can enter multiple values separated by commas. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Scope +The Scope parameter specifies the scope of the client access rule. Valid values are: + +- Users: The rule only applies to end-user connections. +- All: The rule applies to all connections (end-users and middle-tier apps). + +```yaml +Type: ClientAccessRulesScope +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIsMemberOf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsernameMatchesAnyOfPatterns +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. + +You can enter multiple values separated by commas. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -UserRecipientFilter +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. + +You can use the following properties with this parameter: + +- City +- Company +- CountryOrRegion (ISO 3166-1 alpha-2 country code.) +- CustomAttribute1 to CustomAttribute15 +- Department +- Office +- PostalCode +- StateOrProvince +- StreetAddress + +The basic syntax for this parameter is `"Property -ComparisonOperator 'Value'"`: + +- Property is one of the filterable properties in the list above (for example `City` or `CustomAttribute1`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). +- 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. + +For example: + +- `"City -eq 'Redmond'"` +- `"CountryOrRegion -eq 'SG'"`. + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example: + +- `"CustomAttribute1 -eq 'AllowOWA' -and CountryOrRegion -eq AU'"` +- `"(CountryOrRegion -eq 'US' -and Department -eq 'Sales') -or Department -eq 'Research'"`. + +For detailed information about OPATH filter syntax in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/New-ComplianceCase.md b/exchange/exchange-ps/exchange/New-ComplianceCase.md new file mode 100644 index 0000000000..6366bff3d0 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ComplianceCase.md @@ -0,0 +1,223 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ComplianceCase + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-ComplianceCase cmdlet to create eDiscovery cases in the Microsoft Purview compliance portal. You use eDiscovery cases to place content locations on hold, perform Content Searches associated with the case, and export search results. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ComplianceCase [-Name] + [-CaseType ] + [-Confirm] + [-Description ] + [-DomainController ] + [-ExternalId ] + [-SecondaryCaseType ] + [-SourceCaseType ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ComplianceCase -Name "Fabrikam Litigation" +``` + +This example creates a new eDiscovery Standard case named Fabrikam Litigation. + +### Example 2 +```powershell +New-ComplianceCase -Name "Coho Case 03082020" -CaseType AdvancedEdiscovery -ExternalId "SaraDavis v. Coho Winery" +``` + +This example creates a new eDiscovery Premium case named Coho Case 03082020 and specifies an optional case Id of "SaraDavis v. Coho Winery". + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CaseType +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. +- ComplianceClassifier: This type of case corresponds to a trainable classifier. +- ComplianceWorkspace: This value is reserved for internal Microsoft use. +- DataInvestigation: Data investigation cases are used to investigate data spillage incidents. +- DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. +- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This is the default value. +- InsiderRisk: Insider risk cases are use to manage insider risk management cases. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert. +- InternalInvestigation: This value is reserved for internal Microsoft use. +- SupervisionPolicy: This type of case corresponds to communication compliance policy. + +```yaml +Type: ComplianceCaseType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SecondaryCaseType +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceCaseType +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md b/exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md new file mode 100644 index 0000000000..f1f5f46411 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md @@ -0,0 +1,269 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ComplianceRetentionEvent + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-ComplianceRetentionEvent cmdlet to create compliance retention events in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ComplianceRetentionEvent -Name + [-AssetId ] + [-Comment ] + [-Confirm] + [-DomainController ] + [-EventDateTime ] + [-EventTags ] + [-EventType ] + [-ExchangeAssetIdQuery ] + [-PreviewOnly] + [-SharePointAssetIdQuery ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ComplianceRetentionEvent -Name "Research Project Employees" -EventTag 80e0d620-13ea-4ed9-b6a6-aa883278bcca -EventType e823b782-9a07-4e30-8091-034fc01f9347 -SharePointAssetIDQuery "EmployeeNumber:123456 EmployeeNumber:456789" +``` + +This example creates a compliance retention event named Research Project Employees with the following settings: + +- EventTag: 80e0d620-13ea-4ed9-b6a6-aa883278bcca +- EventTpe: e823b782-9a07-4e30-8091-034fc01f9347 +- SharePointAssetIDQuery: EmployeeNumber:123456 EmployeeNumber:456789 + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssetId +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. +- Project codes that you can use to retain content for only a specific project. +- Employee IDs that you can use to retain content for only a specific person. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventDateTime +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventTags +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAssetIdQuery +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreviewOnly +{{ Fill PreviewOnly Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAssetIdQuery +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md new file mode 100644 index 0000000000..f8097fbf29 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md @@ -0,0 +1,121 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ComplianceRetentionEventType + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-ComplianceRetentionEventType cmdlet to create retention event types in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ComplianceRetentionEventType -Name + [-Comment ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ComplianceRetentionEventType -Name "Fabrikam Project" +``` + +This example creates a new retention event type name Fabrikam Project + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ComplianceSearch.md b/exchange/exchange-ps/exchange/New-ComplianceSearch.md new file mode 100644 index 0000000000..bb3b8def59 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ComplianceSearch.md @@ -0,0 +1,475 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ComplianceSearch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-ComplianceSearch cmdlet to create compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. You use this cmdlet to define the search criteria. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ComplianceSearch [-Name] + [-AllowNotFoundExchangeLocationsEnabled ] + [-Case ] + [-Confirm] + [-ContentMatchQuery ] + [-Description ] + [-ExchangeLocation ] + [-ExchangeLocationExclusion ] + [-Force] + [-HoldNames ] + [-IncludeOrgContent ] + [-IncludeUserAppContent ] + [-Language ] + [-LogLevel ] + [-PublicFolderLocation ] + [-RefinerNames ] + [-SharePointLocation ] + [-SharePointLocationExclusion ] + [-StatusMailRecipients ] + [-WhatIf] + [] +``` + +## DESCRIPTION +A compliance search requires at least one location. For example, mailboxes using the ExchangeLocation parameter, or SharePoint sites using the SharePointLocation parameter. + +After you create a compliance search using the New-ComplianceSearch cmdlet, you run the search using the Start-ComplianceSearch cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ComplianceSearch -Name "Hold Project X" -ExchangeLocation "Finance Department" +``` + +This example creates a new compliance search named Hold-Project X that searches all members of the distribution group named Finance Department. Because the search doesn't use the ContentMatchQuery parameter, all items in the mailboxes are searched. + +### Example 2 +```powershell +New-ComplianceSearch -Name "Hold-Tailspin Toys" -ExchangeLocation "Research Department" -ContentMatchQuery "'Patent' AND 'Project Tailspin Toys'" +``` + +This example creates a new compliance search named Hold-Tailspin Toys that searches all member of the distribution group named Research Department. Because the search uses the ContentMatchQuery parameter, only messages that match the query are searched. + +### Example 3 +```powershell +New-ComplianceSearch -Name "AnnBeebe-InactiveMailbox" -ExchangeLocation .annb@contoso.onmicrosoft.com -AllowNotFoundExchangeLocationsEnabled $true +``` + +This example creates a new compliance search named AnnBeebe-InactiveMailbox that searches an inactive mailbox and returns all items in the mailbox. To search inactive mailboxes, you need to use the primary SMTP address of the inactive mailbox, prepended with a period ("."). You also need to include the AllowNotFoundExchangeLocationsEnabled parameter so the search doesn't try to validate the existence of the inactive mailbox. + +## PARAMETERS + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowNotFoundExchangeLocationsEnabled +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. +- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value. + +The mailbox types that are affected by the value of this parameter include: + +- Inactive mailboxes +- Users without an Exchange Online license who use Office applications +- Microsoft 365 guest users +- On-premises users whose identity is synchronized with your Microsoft 365 organization + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Case +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. + +You can't use this parameter to create compliance searches associated with eDiscovery Premium cases. + +If the Name parameter contains spaces, the value of the ExchangeLocation parameter is cleared when you use the Case parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +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. +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). +- The value All for all mailboxes. You can only use this value by itself. + +To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ExchangeLocationExclusion +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: + +- A mailbox +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldNames +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. + +Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeOrgContent +{{ Fill IncludeOrgContent Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeUserAppContent +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: + +- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search. +- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Language +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). + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LogLevel +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: ComplianceJobLogLevel +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderLocation +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RefinerNames +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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. + +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocationExclusion +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StatusMailRecipients +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/New-ComplianceSearchAction.md new file mode 100644 index 0000000000..e2b6541d63 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ComplianceSearchAction.md @@ -0,0 +1,758 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ComplianceSearchAction + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-ComplianceSearchAction cmdlet to create actions for content searches in Exchange Server and in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Export +``` +New-ComplianceSearchAction [-SearchName] + [-Export] + [-ActionName ] + [-ArchiveFormat ] + [-Confirm] + [-FileTypeExclusionsForUnindexedItems ] + [-EnableDedupe ] + [-ExchangeArchiveFormat ] + [-Force] + [-Format ] + [-IncludeCredential] + [-IncludeSharePointDocumentVersions ] + [-JobOptions ] + [-NotifyEmail ] + [-NotifyEmailCC ] + [-ReferenceActionName ] + [-Region ] + [-Report] + [-RetentionReport] + [-RetryOnError] + [-Scenario ] + [-Scope ] + [-SearchNames ] + [-SharePointArchiveFormat ] + [-ShareRootPath ] + [-Version ] + [-WhatIf] + [] +``` + +### Preview +``` +New-ComplianceSearchAction [-SearchName] + [-Preview] + [-ActionName ] + [-Confirm] + [-Force] + [-Format ] + [-IncludeCredential] + [-JobOptions ] + [-ReferenceActionName ] + [-Region ] + [-RetryOnError] + [-Scenario ] + [-SearchNames ] + [-Version ] + [-WhatIf] + [] +``` + +### Purge +``` +New-ComplianceSearchAction [-SearchName] + [-Purge] + [-PurgeType ] + [-ActionName ] + [-Confirm] + [-Force] + [-Format ] + [-IncludeCredential] + [-JobOptions ] + [-Region ] + [-ReferenceActionName ] + [-RetryOnError] + [-Scenario ] + [-SearchNames ] + [-Version ] + [-WhatIf] + [] +``` + +## DESCRIPTION +After you create a content search using the New-ComplianceSearch cmdlet and run it using the Start-ComplianceSearch cmdlet, you assign a search action to the search using the New-ComplianceSearchAction cmdlet. + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In Microsoft 365, the account that you use to run this cmdlet must have a valid Microsoft 365 license assigned. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ComplianceSearchAction -SearchName "Project X" -Preview +``` + +This example creates a preview search action for the content search named Project X. + +### Example 2 +```powershell +New-ComplianceSearchAction -SearchName "Project X" -Export +``` + +This example creates an export search action for the content search named Project X. + +**Note**: After May 26, 2025, this example no longer works. 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). + +### Example 3 +```powershell +New-ComplianceSearchAction -SearchName "Remove Phishing Message" -Purge -PurgeType SoftDelete +``` + +This example deletes the search results returned by a content search named Remove Phishing Message. Note that unindexed items aren't deleted when you use the Purge parameter. + +### Example 4 +```powershell +New-ComplianceSearchAction -SearchName "Case 321 All Sites" -Export -SharePointArchiveFormat SingleZip -ExchangeArchiveFormat PerUserPst -Format FxStream +``` + +This example exports the results returned by the content search named "Case 321 All Sites". The search results are compressed and exported to a single ZIP file. If the search included any Exchange locations, the search results are exported as one PST file per mailbox. + +**Note**: After May 26, 2025, this example no longer works. 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). + +## PARAMETERS + +### -SearchName +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActionName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ArchiveFormat +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. + +```yaml +Type: ComplianceExportArchiveFormat +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableDedupe +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: Export +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeArchiveFormat + +**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. + +This parameter requires the Export role in Security & Compliance PowerShell. By default, this role is assigned only to the eDiscovery Manager role group. + +The ExchangeArchiveFormat parameter specifies how to export Exchange search results. Valid values are: + +- PerUserPst: One PST file for each mailbox. +- SinglePst: One PST file that contains all exported messages. +- SingleFolderPst: One PST file with a single root folder for the entire export. +- IndividualMessage: Export each message as an .msg message file. This is the default value. +- PerUserZip: One ZIP file for each mailbox. Each ZIP file contains the exported .msg message files from the mailbox. +- SingleZip: One ZIP file for all mailboxes. The ZIP file contains all exported .msg message files from all mailboxes. This output setting is available only in PowerShell. + +To specify the format for SharePoint and OneDrive search results, use the SharePointArchiveFormat parameter. + +```yaml +Type: ComplianceExportArchiveFormat +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Export +**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. + +This parameter requires the Export role in Security & Compliance PowerShell. By default, this role is assigned only to the eDiscovery Manager role group. + +The Export switch specifies the action for the content search is to export the full set of results that match the search criteria. You don't need to specify a value with this switch. + +To only return the information about each detected item in a report, use the Report switch. + +```yaml +Type: SwitchParameter +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileTypeExclusionsForUnindexedItems +**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. + +```yaml +Type: String[] +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Format +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: + +- FxStream: Export to PST files. This is the only option that's available when you export search results from the Microsoft Purview compliance portal. +- Mime: Export to .eml message files. This the default value when you use cmdlets to export the search results. +- Msg: Export to .msg message files. + +```yaml +Type: ComplianceDataTransferFormat +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeCredential +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeSharePointDocumentVersions +**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. + +The IncludeSharePointDocumentVersions parameter specifies whether to export previous versions of the document when you use the Export switch. Valid values are: + +- $true: Export all versions of the document. +- $false: Export only the current published version of the topic. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: Export +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -JobOptions +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmail +**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. + +The NotifyEmail parameter specifies the email address target for the search results when you use the Export switch. + +The recipient you specify is in the To: field of the message. + +```yaml +Type: String +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailCC +**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. + +The NotifyEmailCC parameter specifies the email address target for the search results when you use the Export switch. + +The recipient you specify is in the Cc: field of the message. + +```yaml +Type: String +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Preview +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Preview +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Purge +**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. + +- A maximum of 10 items per mailbox can be removed at one time. Because the capability to search for and remove messages is intended to be an incident-response tool, this limit helps ensure that messages are quickly removed from mailboxes. This action isn't intended to clean up user mailboxes. + + **Tip**: To purge more than 10 items, refer to [ediscoverySearch: purgeData](https://learn.microsoft.com/graph/api/security-ediscoverysearch-purgedata) in the Microsoft Graph API, which allows purging a maximum of 100 items per location. + +- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you'll have to create separate content searches. For more information, see [Search for and delete email messages in your Microsoft 365 organization](https://learn.microsoft.com/purview/ediscovery-search-for-and-delete-email-messages). +- Unindexed items aren't removed from mailboxes when you use this switch. +- The value of the PurgeType parameter controls how the items are removed. + +```yaml +Type: SwitchParameter +Parameter Sets: Purge +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PurgeType +**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: + +- SoftDelete: Purged items are recoverable by users until the deleted item retention period expires. +- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and will be permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items will be permanently removed after the deleted item retention period expires. + +```yaml +Type: ComplianceDestroyType +Parameter Sets: Purge +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReferenceActionName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Region +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Report +**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. + +The Report switch specifies the action for the content search is to export a report about the results (information about each item instead of the full set of results) that match the search criteria. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionReport +**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. + +```yaml +Type: SwitchParameter +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetryOnError +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Scenario +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: + +- AnalyzeWithZoom: Prepare the search results for processing in Microsoft Purview eDiscovery Premium. +- General: Exports the search results to the local computer. Emails are exported to .pst files. SharePoint and OneDrive documents are exported in their native Office formats. +- GenerateReportsOnly +- Inventory +- RetentionReports +- TriagePreview + +```yaml +Type: ComplianceSearchActionScenario +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Scope +**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: + +- IndexedItemsOnly +- UnindexedItemsOnly +- BothIndexedAndUnindexedItems + +```yaml +Type: ComplianceExportScope +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SearchNames +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. + +You can find content search names by running the command Get-ComplianceSearch | Format-Table -Auto Name,Status. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointArchiveFormat +**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. + +This parameter requires the Export role. By default, this role is assigned only to the eDiscovery Manager role group. + +The SharePointArchiveFormat parameter specifies how to export SharePoint and OneDrive search results. Valid values are: + +- IndividualMessage: Export the files uncompressed. This is the default value. +- PerUserZip: One ZIP file for each user. Each ZIP file contains the exported files for the user. +- SingleZip: One ZIP file for all users. The ZIP file contains all exported files from all users. This output setting is available only in PowerShell. + +To specify the format for Exchange search results, use the ExchangeArchiveFormat parameter. + +```yaml +Type: ComplianceExportArchiveFormat +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShareRootPath +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). + +{{ Fill ShareRootPath Description }} + +```yaml +Type: String +Parameter Sets: Export +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Version +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md new file mode 100644 index 0000000000..cf258e62c7 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md @@ -0,0 +1,250 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ComplianceSecurityFilter + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-ComplianceSecurityFilter cmdlet to create compliance security filters in the Microsoft Purview compliance portal. These filters allow specified users to search only a subset of mailboxes and SharePoint or OneDrive sites in your Microsoft 365 organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ComplianceSecurityFilter -Action -FilterName -Users + [-Confirm] + [-Description ] + [-Filters ] + [-Region ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Compliance security filters work with compliance searches in the Microsoft Purview compliance portal (\*-ComplianceSearch cmdlets), not In-Place eDiscovery searches in Exchange Online (\*-MailboxSearch cmdlets). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ComplianceSecurityFilter -FilterName CountryFilter -Users annb@contoso.com -Filters "Mailbox_CountryCode -eq '124'" -Action All +``` + +This example allows the user annb to perform all compliance search actions only for mailboxes in Canada. The filter uses the ISO 3166-1 numeric country code value. + +### Example 2 +```powershell +New-ComplianceSecurityFilter -FilterName USDiscoveryManagers -Users "US Discovery Managers" -Filters "Mailbox_CountryCode -eq '840'" -Action All +``` + +This example allows members of the US Discovery Managers role group to perform all compliance search actions only on mailboxes in the United States. + +### Example 3 +```powershell +New-ComplianceSecurityFilter -FilterName EmailDateRestrictionFilter -Users donh@contoso.com -Filters "MailboxContent_Received -ge '01-01-2018' -and MailboxContent_Received -le '12-31-2018'" -Action All +``` + +This example restricts the user to performing all compliance search actions only on email messages sent during the calendar year 2018. + +### Example 4 +```powershell +New-ComplianceSecurityFilter -FilterName DocumentDateRestrictionFilter -Users donh@contoso.com -Filters "SiteContent_LastModifiedTime -ge '01-01-2018' -and SiteContent_LastModifiedTime -le '12-31-2018'" -Action All +``` + +This example restricts the user to performing all compliance search actions on documents that were last changed sometime in the calendar year 2018. + +### Example 5 +```powershell +New-ComplianceSecurityFilter -FilterName NoEXO -Users suzanf@contoso.com -Filters "Mailbox_Alias -notlike '*'" -Action All +``` + +This example prevents the user from performing any compliance search actions on any mailbox in the organization. + +## PARAMETERS + +### -Action +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. +- Preview: The filter is applied when previewing search results. +- Purge: The filter is applied when purging search results. How the items are deleted is controlled by the PurgeType parameter value on the New-ComplianceSearchAction cmdlet. The default value is SoftDelete, which means the purged items are recoverable by users until the deleted items retention period expires. +- Search: The filter is applied when running a search. +- All: The filter is applied to all search actions. + +```yaml +Type: ComplianceSecurityFilterActionType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FilterName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Users +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. +- The value All: Assigns the filter to all users. You can only use this value by itself. +- One or more role groups: Identify the role group by its name. You can specify multiple values separated by commas. + +You can't specify distribution groups with this parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filters +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). +- Mailbox content filter: Specifies the mailbox content the assigned users can search for. Valid syntax is `MailboxContent_`, where `` specifies a Keyword Query Language (KQL) property that can be specified in a compliance search. For example, `"MailboxContent_Recipients -like 'contoso.com'"` allows users to only search for messages sent to recipients in the contoso.com domain. For a list of searchable email properties, see [Keyword queries for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions#searchable-email-properties). +- Site and site content filter: There are two SharePoint and OneDrive site-related filters that you can create: `Site_` (specifies site-related properties. For example,`"Site_Path -eq 'https://contoso.sharepoint.com/sites/doctors'"` allows users to only search for content in the `https://contoso.sharepoint.com/sites/doctors` site collection) and `SiteContent_` (specifies content-related properties. For example, `"SiteContent_FileExtension -eq 'docx'"` allows users to only search for Word documents). For a list of searchable site properties, see [Overview of crawled and managed properties in SharePoint Server](https://learn.microsoft.com/SharePoint/technical-reference/crawled-and-managed-properties-overview). Properties marked with a Yes in the Queryable column can be used to create a site or site content filter. + +You can specify multiple filters of the same type. For example, `"Mailbox_CustomAttribute10 -eq 'FTE' -and Mailbox_MemberOfGroup -eq '$($DG.DistinguishedName)'"`. + +You need to create a search permissions filter to explicitly prevent users from searching any content location in a specific Microsoft 365 service (such as preventing a user from searching Exchange mailboxes or SharePoint sites). In other words, creating a search permissions filter that allows a user to search all SharePoint sites in the organization doesn't prevent that user from searching mailboxes. For example, to allow a SharePoint admin to only search SharePoint sites, you need to create a filter that prevents them from searching mailboxes (as described in Example 5). Similarly, to allow an Exchange admin to only search mailboxes, you need to create a filter that prevents them from searching sites. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Region +The Region parameter specifies the satellite location for multi-geo tenants to conduct eDiscovery searches in. Valid values are: + +- APC: Asia-Pacific +- AUS: Australia +- CAN: Canada +- EUR: Europe, Middle East, Africa +- FRA: France +- GBR: United Kingdom +- IND: India +- JPN: Japan +- LAM: Latin America +- NAM: North America + +If you don't use this parameter in a multi-geo tenant, eDiscovery searches are performed in the central location. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ComplianceTag.md b/exchange/exchange-ps/exchange/New-ComplianceTag.md new file mode 100644 index 0000000000..9de8c0fca4 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ComplianceTag.md @@ -0,0 +1,513 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ComplianceTag + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-ComplianceTag cmdlet to create retention labels in the Microsoft Purview compliance portal. Retention labels apply retention settings to content. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +New-ComplianceTag [-Name] + [-AutoApprovalPeriod ] + [-Comment ] + [-ComplianceTagForNextStage ] + [-Confirm] + [-EventType ] + [-FilePlanProperty ] + [-FlowId ] + [-Force] + [-IsRecordLabel ] + [-IsRecordUnlockedAsDefault ] + [-MultiStageReviewProperty ] + [-Notes ] + [-Regulatory ] + [-RetentionAction ] + [-RetentionDuration ] + [-RetentionType ] + [-ReviewerEmail ] + [-WhatIf] + [] +``` + +### PriorityCleanup +``` +New-ComplianceTag [-Name] -RetentionAction -RetentionDuration -RetentionType + -MultiStageReviewProperty [-PriorityCleanup] + [-Comment ] + [-Confirm] + [-Force] + [-Notes ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ComplianceTag -Name "HR Content" -RetentionAction Keep -RetentionDuration 1825 -RetentionType ModificationAgeInDays +``` + +This example creates a new label named HR Content with the following settings: + +- Action: Keep. +- Duration: 5 years (1825 days) +- Type: Modification age in days. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionAction +The RetentionAction parameter specifies the action for the label. Valid values are: + +- Delete +- Keep +- KeepAndDelete + +```yaml +Type: String +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: + +- A positive integer. +- The value unlimited. + +```yaml +Type: Unlimited +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: Unlimited +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionType +The RetentionType parameter specifies whether the retention duration is calculated from the content creation date, tagged date, or last modification date. Valid values are: + +- CreationAgeInDays +- EventAgeInDays +- ModificationAgeInDays +- TaggedAgeInDays + +```yaml +Type: String +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoApprovalPeriod +{{ Fill AutoApprovalPeriod Description }} + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceTagForNextStage +{{ Fill ComplianceTagForNextStage Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +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 +- Distinguished name (DN) +- GUID + +You can use the Get-RetentionComplianceRule cmdlet to view the available retention rules. + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FilePlanProperty +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` +- `Get-FilePlanPropertyCategory | Format-List Name` +- `Get-FilePlanPropertyCitation | Format-List Name` +- `Get-FilePlanPropertyDepartment | Format-List Name` +- `Get-FilePlanPropertyReferenceId | Format-List Name` +- `Get-FilePlanPropertySubCategory | Format-List Name` + +A valid value for this parameter involves two steps: + +- A variable to store the file plan properties as a PSCustomObject using the following syntax: + + `$Variable1=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Name"},@{Key="FilePlanPropertyCategory";Value="Name"},@{Key="FilePlanPropertySubcategory";Value="Name"},@{Key="FilePlanPropertyCitation";Value="Name"},@{Key="FilePlanPropertyReferenceId";Value="Name"},@{Key="FilePlanPropertyAuthority";Value="Name"})}` + + For example: + + `$retentionLabelAction=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Legal"},@{Key="FilePlanPropertyCategory";Value="Tax"},@{Key="FilePlanPropertySubcategory";Value="US_Tax"},@{Key="FilePlanPropertyCitation";Value="LegalCitation"},@{Key="FilePlanPropertyReferenceId";Value="Referen`ceA"},@{Key="FilePlanPropertyAuthority";Value="Auth1"})} + +- A second variable to convert the PSCustomObject to a JSON object using the following syntax: + + `$Variable2 = ConvertTo-Json $Variable1` + + For example: + + `$fpStr = ConvertTo-Json $retentionLabelAction` + +You use the second variable as the value for this parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FlowId +**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. + +You can find the GUID value of the flow by using either of the following methods: + +- Navigate to the flow from the Power Automate portal. The GUID value of the flow is in the URL. +- Use the Power Automate action named 'List flows as admin'. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsRecordLabel +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. +- $false: The label isn't a record label. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsRecordUnlockedAsDefault +{{ Fill IsRecordUnlockedAsDefault Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiStageReviewProperty +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]},]}'` + +For example: + +`'{"MultiStageReviewSettings":[{"StageName":"Stage1","Reviewers":[jie@contoso.onmicrosoft.com]},{"StageName":"Stage2","Reviewers":[bharath@contoso.onmicrosoft.com,helen@contoso.onmicrosoft.com]},]}'` + +This syntax is a JSON object that defines each review stage id, review stage name, and list of reviewers. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Notes +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Regulatory +{{ Fill Regulatory Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReviewerEmail +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DataClassification.md b/exchange/exchange-ps/exchange/New-DataClassification.md similarity index 78% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DataClassification.md rename to exchange/exchange-ps/exchange/New-DataClassification.md index 5f9721ce58..ee21f6fc1a 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DataClassification.md +++ b/exchange/exchange-ps/exchange/New-DataClassification.md @@ -1,44 +1,55 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dataclassification -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-DataClassification ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [New-DlpSensitiveInformationType](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpsensitiveinformationtype) cmdlet in Office 365 Security & Compliance Center PowerShell. +In Exchange Online, this cmdlet has been replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchange/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the New-DataClassification cmdlet to create data classification rules that use document fingerprints. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` New-DataClassification [-Name] -Description -Fingerprints - [-ClassificationRuleCollectionIdentity ] [-Confirm] - [-DomainController ] [-Locale ] [-WhatIf] [] + [-ClassificationRuleCollectionIdentity ] + [-Confirm] + [-DomainController ] + [-Locale ] + [-WhatIf] + [] ``` ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$Employee_Template = Get-Content "C:\My Documents\Contoso Employee Template.docx" -Encoding byte; $Employee_Fingerprint = New-Fingerprint -FileData $Employee_Template -Description "Contoso Employee Template"; $Customer_Template = Get-Content "D:\Data\Contoso Customer Template.docx" -Encoding byte; $Customer_Fingerprint = New-Fingerprint -FileData $Customer_Template -Description "Contoso Customer Template"; New-DataClassification -Name "Contoso Employee-Customer Confidential" -Fingerprints $Employee_Fingerprint,$Customer_Fingerprint -Description "Message contains Contoso employee or customer information." +$Employee_Template = [System.IO.File]::ReadAllBytes('C:\My Documents\Contoso Employee Template.docx') + +$Employee_Fingerprint = New-Fingerprint -FileData $Employee_Template -Description "Contoso Employee Template" + +$Customer_Template = [System.IO.File]::ReadAllBytes('D:\Data\Contoso Customer Template.docx') + +$Customer_Fingerprint = New-Fingerprint -FileData $Customer_Template -Description "Contoso Customer Template" + +New-DataClassification -Name "Contoso Employee-Customer Confidential" -Fingerprints $Employee_Fingerprint,$Customer_Fingerprint -Description "Message contains Contoso employee or customer information." ``` This example creates a new data classification rule named "Contoso Employee-Customer Confidential" that uses the document fingerprints of the files C:\\My Documents\\Contoso Employee Template.docx and D:\\Data\\Contoso Customer Template.docx. @@ -52,7 +63,7 @@ The Description parameter specifies a description for the data classification ru Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -62,13 +73,13 @@ Accept wildcard characters: False ``` ### -Fingerprints -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://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-fingerprint) or the Examples section. +The Fingerprints parameter specifies the byte-encoded files to use as document fingerprints. You can use multiple document fingerprints separated by commas. For instructions on how to import documents to use as templates for fingerprints, see [New-Fingerprint](https://learn.microsoft.com/powershell/module/exchange/new-fingerprint) or the Examples section. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -86,7 +97,7 @@ The value of this parameter is used in the Policy Tip that's presented to users Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -102,7 +113,7 @@ This parameter is reserved for internal Microsoft use. Type: ClassificationRuleCollectionIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -114,15 +125,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -150,7 +160,7 @@ Accept wildcard characters: False ### -Locale 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://go.microsoft.com/fwlink/p/?linkId=184859). +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). You can add additional language translations to the data classification rule by using the Set-DataClassification cmdlet. @@ -158,7 +168,7 @@ You can add additional language translations to the data classification rule by Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -174,7 +184,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -188,12 +198,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/New-DataEncryptionPolicy.md b/exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md similarity index 76% rename from exchange/exchange-ps/exchange/encryption-and-certificates/New-DataEncryptionPolicy.md rename to exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md index e23f4cc041..fb8c9ddfeb 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/New-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/new-dataencryptionpolicy +online version: https://learn.microsoft.com/powershell/module/exchange/new-dataencryptionpolicy applicable: Exchange Online title: New-DataEncryptionPolicy schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # New-DataEncryptionPolicy @@ -17,24 +16,26 @@ This cmdlet is available only in the cloud-based service. Use the New-DataEncryptionPolicy cmdlet to create data encryption policies in Exchange Online. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-DataEncryptionPolicy [-Name] -AzureKeyIDs [-Confirm] [-Description ] - [-DomainController ] [-Enabled ] [-WhatIf] [] +New-DataEncryptionPolicy [-Name] -AzureKeyIDs + [-Confirm] + [-Description ] + [-DomainController ] + [-Enabled ] + [-WhatIf] + [] ``` ## DESCRIPTION -Data encryption policy cmdlets are the Exchange Online part of service encryption with Customer Key in Office 365. For more information, see [Controlling your data in Office 365 using Customer Key](https://aka.ms/customerkey). +Data encryption policy cmdlets are the Exchange Online part of Customer Key. For more information, see [Controlling your data in Microsoft 365 using Customer Key](https://aka.ms/customerkey). You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,35 +48,35 @@ This example creates a data encryption policy named US Mailboxes with the specif ## PARAMETERS -### -AzureKeyIDs -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 [What is Azure Key Vault?](https://go.microsoft.com/fwlink/p/?linkid=521402). +### -Name +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: MultiValuedProperty +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Online Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies the unique name for the data encryption policy. If the value contains spaces, enclose the value in quotation marks. +### -AzureKeyIDs +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). ```yaml -Type: String +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Online Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -84,8 +85,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -137,7 +137,6 @@ Accept wildcard characters: False The Enabled parameter enables or disable the data encryption policy. Valid values are: - $true: The policy is enabled. This is the default value. - - $false: The policy is disabled. ```yaml @@ -174,12 +173,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/database-availability-groups/New-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md similarity index 93% rename from exchange/exchange-ps/exchange/database-availability-groups/New-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md index 66ae72edf3..8b05d74e98 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/New-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/new-databaseavailabilitygroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-DatabaseAvailabilityGroup @@ -17,17 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the New-DatabaseAvailabilityGroup cmdlet to create a database availability group (DAG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-DatabaseAvailabilityGroup [-Name] [-Confirm] [-DatabaseAvailabilityGroupIpAddresses ] - [-DomainController ] [-ThirdPartyReplication ] [-WhatIf] - [-WitnessDirectory ] [-WitnessServer ] - [-DagConfiguration ] +New-DatabaseAvailabilityGroup [-Name] [-ActivityState ] - [-FileSystem ] [] + [-Confirm] + [-DagConfiguration ] + [-DatabaseAvailabilityGroupIpAddresses ] + [-DomainController ] + [-FileSystem ] + [-ThirdPartyReplication ] + [-WhatIf] + [-WitnessDirectory ] + [-WitnessServer ] + [] ``` ## DESCRIPTION @@ -36,22 +41,19 @@ When creating a DAG, you need to specify a valid computer name for the DAG no lo The requirements for the witness server are as follows: - The witness server can't be a member of the DAG. - - The witness server must be running the Windows Server 2008 operating system or later. - - A single server can serve as a witness for multiple DAGs; however, each DAG requires its own witness directory. The following combinations of options and behaviors are available: - You can specify a name for the DAG, the witness server that you want to use, and the directory you want created and shared on the witness server. - - You can specify a name for the DAG and the witness server that you want to use. In this scenario, the task creates the default directory on the specified witness server. If the witness server that you specify isn't an Exchange server, you need to add the Exchange Trusted Subsystem universal security group (USG) to the local Administrators group on the witness server. If the witness server is a directory server, you need to add the Exchange Trusted Subsystem USG to the Builtin\\Administrators group. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed. In Windows Server 2012 R2 or later, a DAG is created without a cluster administrative access point by default. In this scenario, you don't need to provide any IP addresses to the DAG. However, in all supported versions of Windows, you have the option of assigning static IP addresses to the DAG by using the DatabaseAvailabilityGroupIpAddresses parameter. If you specify Any or 0.0.0.0, the task attempts to use Dynamic Host Configuration Protocol (DHCP) to obtain IP addresses. If you omit this parameter or configure the parameter with a value of None or 255.255.255.255, the DAG will not have a cluster administrative access point. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -94,18 +96,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +### -ActivityState +This parameter is reserved for internal Microsoft use. ```yaml -Type: SwitchParameter +Type: ActivityStateOption Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -114,13 +112,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DatabaseAvailabilityGroupIpAddresses -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. +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: IPAddress[] +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -130,14 +131,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -DagConfiguration +This parameter is reserved for internal Microsoft use. ```yaml -Type: Fqdn +Type: DatabaseAvailabilityGroupConfigurationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -146,11 +147,11 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ThirdPartyReplication -The ThirdPartyReplication parameter specifies to configure and enable a DAG to use third-party 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. +### -DatabaseAvailabilityGroupIpAddresses +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: ThirdPartyReplicationMode +Type: IPAddress[] Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -162,13 +163,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: SwitchParameter +Type: Fqdn Parameter Sets: (All) -Aliases: wi +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -178,14 +179,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WitnessDirectory -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. +### -FileSystem +The FileSystem parameter specifies the file system that's used for the DAG. Valid values are: + +- NTFS +- ReFS ```yaml -Type: NonRootLocalLongFullPath +Type: FileSystemMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -194,11 +198,11 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WitnessServer -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. +### -ThirdPartyReplication +The ThirdPartyReplication parameter specifies to configure and enable a DAG to use third-party 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: FileShareWitnessServerName +Type: ThirdPartyReplicationMode Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -210,14 +214,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DagConfiguration -This parameter is reserved for internal Microsoft use. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: DatabaseAvailabilityGroupConfigurationIdParameter +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -226,14 +230,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ActivityState -This parameter is reserved for internal Microsoft use. +### -WitnessDirectory +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: ActivityStateOption +Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -242,18 +246,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -FileSystem -The FileSystem parameter specifies the file system that's used for the DAG. Valid values are: - -- NTFS - -- ReFS +### -WitnessServer +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: FileSystemMode +Type: FileShareWitnessServerName Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -267,12 +267,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/New-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md similarity index 88% rename from exchange/exchange-ps/exchange/database-availability-groups/New-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md index d8486945f0..cdf95fa60f 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/New-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/new-databaseavailabilitygroupnetwork +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-DatabaseAvailabilityGroupNetwork @@ -17,19 +16,24 @@ This cmdlet is available only in on-premises Exchange. Use the New-DatabaseAvailabilityGroupNetwork cmdlet to create a database availability group (DAG) network. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-DatabaseAvailabilityGroupNetwork [-Name] - [-DatabaseAvailabilityGroup] [-Confirm] [-Description ] - [-DomainController ] [-IgnoreNetwork ] [-ReplicationEnabled ] - [-Subnets ] [-WhatIf] [] +New-DatabaseAvailabilityGroupNetwork [-Name] [-DatabaseAvailabilityGroup] + [-Confirm] + [-Description ] + [-DomainController ] + [-IgnoreNetwork ] + [-ReplicationEnabled ] + [-Subnets ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,33 +46,33 @@ This example creates the DAG network DAG1Repl in the DAG DAG1. A subnet of 10.0. ## PARAMETERS -### -DatabaseAvailabilityGroup -The DatabaseAvailabilityGroup parameter specifies the name of the DAG that'll use the network being created. +### -Name +The Name parameter specifies the name of the DAG network being created. ```yaml -Type: DatabaseAvailabilityGroupIdParameter +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 2 +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies the name of the DAG network being created. +### -DatabaseAvailabilityGroup +The DatabaseAvailabilityGroup parameter specifies the name of the DAG that'll use the network being created. ```yaml -Type: String +Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: 2 Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -77,8 +81,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -195,12 +198,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-DeliveryAgentConnector.md b/exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/New-DeliveryAgentConnector.md rename to exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md index 1f10e84be6..42534c6c9d 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-deliveryagentconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-DeliveryAgentConnector @@ -17,22 +16,29 @@ This cmdlet is available only in on-premises Exchange. The New-DeliveryAgentConnector cmdlet creates a delivery agent connector in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` New-DeliveryAgentConnector [-Name] -AddressSpaces -DeliveryProtocol - [-Comment ] [-Confirm] [-DomainController ] [-Enabled ] - [-IsScopedConnector ] [-MaxConcurrentConnections ] [-MaxMessageSize ] - [-MaxMessagesPerConnection ] [-SourceTransportServers ] [-WhatIf] + [-Comment ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-IsScopedConnector ] + [-MaxConcurrentConnections ] + [-MaxMessageSize ] + [-MaxMessagesPerConnection ] + [-SourceTransportServers ] + [-WhatIf] [] ``` ## DESCRIPTION -Delivery agent connectors are used to route messages addressed to foreign systems that don't utilize the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in the Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://docs.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). +Delivery agent connectors are used to route messages addressed to foreign systems that don't utilize the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in the Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +52,7 @@ This example creates a delivery agent connector named Contoso X.400 Connector wi The delivery agent connector is hosted on the following servers: - Hub01 - - Hub02 - - Hub05 The delivery agent connector is designed to handle X.400 connections to a company called Contoso that uses the carrier Fabrikam. @@ -57,27 +61,27 @@ The address space for the connector is c=US;a=Fabrikam;p=Contoso. ## PARAMETERS -### -AddressSpaces -The AddressSpaces parameter specifies the domain names for which this delivery agent connector is responsible. The syntax for entering an address space is as follows: \:\;\. You must enclose each address space in quotation marks ("). +### -Name +The Name parameter specifies the name of this delivery agent connector. The value for the Name parameter can't exceed 64 characters. ```yaml -Type: MultiValuedProperty +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -DeliveryProtocol -The DeliveryProtocol parameter specifies the communication protocol that determines which delivery agents are responsible for servicing the connector. +### -AddressSpaces +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: String +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -89,8 +93,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies the name of this delivery agent connector. The value for the Name parameter can't exceed 64 characters. +### -DeliveryProtocol +The DeliveryProtocol parameter specifies the communication protocol that determines which delivery agents are responsible for servicing the connector. ```yaml Type: String @@ -99,7 +103,7 @@ Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -124,8 +128,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -213,11 +216,8 @@ Accept wildcard characters: False 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) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are treated as bytes. The valid input range for this parameter is from 65536 through 2147483647 bytes. The default value is unlimited. @@ -290,12 +290,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md new file mode 100644 index 0000000000..b8386092bb --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md @@ -0,0 +1,169 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DeviceConditionalAccessPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DeviceConditionalAccessPolicy cmdlet to create mobile device conditional access policies in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DeviceConditionalAccessPolicy [-Name] + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DeviceConditionalAccessPolicy -Identity "Human Resources" +``` + +This example creates a new mobile device conditional access policy named Human Resources + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/New-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md similarity index 82% rename from exchange/exchange-ps/exchange/devices/New-DeviceConditionalAccessRule.md rename to exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md index cbd6db5cf9..102c007035 100644 --- a/exchange/exchange-ps/exchange/devices/New-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md @@ -1,66 +1,92 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-deviceconditionalaccessrule -applicable: Office 365 Security & Compliance Center +online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconditionalaccessrule +applicable: Security & Compliance title: New-DeviceConditionalAccessRule schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "o365scc-ps" --- # New-DeviceConditionalAccessRule ## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). -Use the New-DeviceConditionalAccessRule cmdlet to create mobile device conditional access rules in the Security & Compliance Center. +Use the New-DeviceConditionalAccessRule cmdlet to create mobile device conditional access rules in Basic Mobility and Security in Microsoft 365. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` New-DeviceConditionalAccessRule -Policy -TargetGroups - [-AccountName ] [-AccountUserName ] [-AllowAppStore ] - [-AllowAssistantWhileLocked ] [-AllowConvenienceLogon ] - [-AllowDiagnosticSubmission ] [-AllowiCloudBackup ] - [-AllowiCloudDocSync ] [-AllowiCloudPhotoSync ] - [-AllowJailbroken ] [-AllowPassbookWhileLocked ] - [-AllowScreenshot ] [-AllowSimplePassword ] - [-AllowVideoConferencing ] [-AllowVoiceAssistant ] - [-AllowVoiceDialing ] [-AntiVirusSignatureStatus ] [-AntiVirusStatus ] + [-AccountName ] + [-AccountUserName ] + [-AllowAppStore ] + [-AllowAssistantWhileLocked ] + [-AllowConvenienceLogon ] + [-AllowDiagnosticSubmission ] + [-AllowiCloudBackup ] + [-AllowiCloudDocSync ] + [-AllowiCloudPhotoSync ] + [-AllowJailbroken ] + [-AllowPassbookWhileLocked ] + [-AllowScreenshot ] + [-AllowSimplePassword ] + [-AllowVideoConferencing ] + [-AllowVoiceAssistant ] + [-AllowVoiceDialing ] + [-AntiVirusSignatureStatus ] + [-AntiVirusStatus ] [-AppsRating ] [-AutoUpdateStatus ] - [-BluetoothEnabled ] [-CameraEnabled ] [-Confirm] [-DomainController ] - [-EmailAddress ] [-EnableRemovableStorage ] [-ExchangeActiveSyncHost ] - [-FirewallStatus ] [-ForceAppStorePassword ] - [-ForceEncryptedBackup ] [-MaxPasswordAttemptsBeforeWipe ] + [-BluetoothEnabled ] + [-CameraEnabled ] + [-Confirm] + [-DomainController ] + [-EmailAddress ] + [-EnableRemovableStorage ] + [-ExchangeActiveSyncHost ] + [-FirewallStatus ] + [-ForceAppStorePassword ] + [-ForceEncryptedBackup ] + [-MaxPasswordAttemptsBeforeWipe ] [-MaxPasswordGracePeriod ] [-MoviesRating ] - [-PasswordComplexity ] [-PasswordExpirationDays ] [-PasswordHistoryCount ] - [-PasswordMinComplexChars ] [-PasswordMinimumLength ] [-PasswordQuality ] - [-PasswordRequired ] [-PasswordTimeout ] [-PhoneMemoryEncrypted ] - [-RegionRatings ] [-RequireEmailProfile ] - [-SmartScreenEnabled ] [-SystemSecurityTLS ] + [-PasswordComplexity ] + [-PasswordExpirationDays ] + [-PasswordHistoryCount ] + [-PasswordMinComplexChars ] + [-PasswordMinimumLength ] + [-PasswordQuality ] + [-PasswordRequired ] + [-PasswordTimeout ] + [-PhoneMemoryEncrypted ] + [-RegionRatings ] + [-RequireEmailProfile ] + [-SmartScreenEnabled ] + [-SystemSecurityTLS ] [-TVShowsRating ] [-UserAccountControlStatus ] - [-WhatIf] [-WLANEnabled ] [-WorkFoldersSyncUrl ] [] + [-WhatIf] + [-WLANEnabled ] + [-WorkFoldersSyncUrl ] + [] ``` ## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. +The cmdlets in Basic Mobility and Security are described in the following list: +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. - DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). ## EXAMPLES @@ -72,7 +98,6 @@ New-DeviceConditionalAccessRule -Policy "Secure Email" -TargetGroups 5bff73eb-0b This example creates a new mobile device conditional access rule with the following settings: - Policy: Secure Email - - TargetGroups:5bff73eb-0ba7-461b-b7c9-9b4c173cc266 ## PARAMETERS @@ -81,16 +106,14 @@ This example creates a new mobile device conditional access rule with the follow 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 - - Distinguished name (DN) - - GUID ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: True Position: Named @@ -108,7 +131,7 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: True Position: Named @@ -121,14 +144,13 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -141,14 +163,13 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -161,22 +182,19 @@ Accept wildcard characters: False 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. - - $false: Access to the app store isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -189,9 +207,7 @@ Accept wildcard characters: False 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. - - $false: The voice assistant can't be used while devices are locked. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -200,7 +216,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -213,9 +229,7 @@ Accept wildcard characters: False The AllowConvenienceLogon parameter specifies whether to allow convenience logons on devices. Valid values for this parameter are: - $true: Convenience logons are allowed. - - $false: Convenience logons aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -224,7 +238,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -237,24 +251,20 @@ Accept wildcard characters: False The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic submissions from devices. Valid values for this parameter are: - $true: Diagnostic submissions are allowed. - - $false: Diagnostic submissions aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -267,22 +277,19 @@ Accept wildcard characters: False The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup from devices. Valid values for this parameter are: - $true: iCloud Backup is allowed. - - $false: iCloud Backup isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -295,22 +302,19 @@ Accept wildcard characters: False 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. - - $false: iCloud Documents & Data sync isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -323,22 +327,19 @@ Accept wildcard characters: False 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. - - $false: iCloud Photo sync isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -351,22 +352,19 @@ Accept wildcard characters: False The AllowJailbroken parameter specifies whether to allow access to your organization by jailbroken or rooted devices. - $true: Jailbroken devices are allowed. - - $false: Jailbroken devices aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -379,9 +377,7 @@ Accept wildcard characters: False 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. - - $false: Passbook isn't available while devices are locked. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -390,7 +386,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -403,22 +399,19 @@ Accept wildcard characters: False The AllowScreenshot parameter specifies whether to allow screenshots on devices. Valid values for this parameter are: - $true: Screenshots are allowed. - - $false: Screenshots aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -431,24 +424,20 @@ Accept wildcard characters: False 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. - - $false: Simple passwords aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -461,9 +450,7 @@ Accept wildcard characters: False The AllowVideoConferencing parameter specifies whether to allow video conferencing on devices. Valid values for this parameter are: - $true: Video conferencing is allowed. - - $false: Video conferencing isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -472,7 +459,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -485,9 +472,7 @@ Accept wildcard characters: False 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. - - $false: The voice assistant isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -496,7 +481,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -509,9 +494,7 @@ Accept wildcard characters: False The AllowVoiceDialing parameter specifies whether to allow voice-activated telephone dialing. Valid values for this parameter are: - $true: Voice dialing is allowed. - - $false: Voice dialing isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -520,7 +503,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -533,7 +516,6 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -542,7 +524,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -555,7 +537,6 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -564,7 +545,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -577,15 +558,10 @@ Accept wildcard characters: False The AppsRating parameter species the maximum or most restrictive rating of apps that are allowed on devices. Valid values for this parameter are: - AllowAll - - DontAllow - - Rating9plus - - Rating12plus - - Rating17plus - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -594,7 +570,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingAppsEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -607,15 +583,10 @@ Accept wildcard characters: False The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are: - AutomaticCheckForUpdates - - AutomaticDownloadUpdates - - AutomaticUpdatesRequired - - DeviceDefault - - NeverCheckUpdates - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -624,7 +595,7 @@ This setting is available only on Windows 8.1 RT devices. Type: CAAutoUpdateStatusEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -637,9 +608,7 @@ Accept wildcard characters: False The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth on devices. Valid values for this parameter are: - $true: Bluetooth is enabled. - - $false: Bluetooth is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows Phone 8.1 devices. @@ -648,7 +617,7 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -661,24 +630,20 @@ Accept wildcard characters: False The CameraEnabled parameter specifies whether to enable or disable cameras on devices. Valid values for this parameter are: - $true: Cameras are enabled. - - $false: Cameras are disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -690,15 +655,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -714,7 +678,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -727,14 +691,13 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -747,9 +710,7 @@ Accept wildcard characters: False The EnableRemovableStorage parameter specifies whether removable storage can be used by devices. Valid values for this parameter are: - $true: Removable storage can be used. - - $false: Removable storage can't be used. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows Phone 8.1 devices. @@ -758,7 +719,7 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -771,14 +732,13 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -791,7 +751,6 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -800,7 +759,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Required Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -813,9 +772,7 @@ Accept wildcard characters: False 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. - - $false: App store passwords aren't required. - - $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -824,7 +781,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -837,22 +794,19 @@ Accept wildcard characters: False The ForceEncryptedBackup parameter specifies whether to force encrypted backups for devices. Valid values for this parameter are: - $true: Encrypted backups are required. - - $false: Encrypted backups aren't required. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -865,24 +819,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -902,7 +852,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -912,130 +862,88 @@ Accept wildcard characters: False ``` ### -MoviesRating -The MoviesRating parameter species the maximum or most restrictive rating of movies that are allowed on devices. You specify the country rating system to use with the RegionRatings parameter. +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: - AllowAll: All movies are allowed, regardless of their rating. - - DontAllow: No movies are allowed, regardless of their rating. - - $null (blank): The setting isn't configured. This is the default value. Australia - AURatingG - - AURatingPG - - AURatingM - - AURatingMA15plus - - AURatingR18plus Canada - CARatingG - - CARatingPG - - CARating14A - - CARating18A - - CARatingR Germany - DERatingab0Jahren - - DERatingab6Jahren - - DERatingab12Jahren - - DERatingab16Jahren - - DERatingab18Jahren France - FRRating10minus - - FRRating12minus - - FRRating16minus - - FRRating18minus United Kingdom - GBRatingU - - GBRatingUc - - GBRatingPG - - GBRating12 - - GBRating12A - - GBRating15 - - GBRating18 Ireland - IERatingG - - IERatingPG - - IERating12 - - IERating15 - - IERating16 - - IERating18 Japan - JPRatingG - - JPRatingPG12 - - JPRatingRdash15 - - JPRatingRdash18 New Zealand - NZRatingG - - NZRatingPG - - NZRatingM - - NZRatingR13 - - NZRatingR15 - - NZRatingR16 - - NZRatingR18 - - NZRatingR United States - USRatingG - - USRatingPG - - USRatingPG13 - - USRatingR - - USRatingNC17 This setting is available only on Apple iOS 6+ devices. @@ -1044,7 +952,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingMovieEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1057,14 +965,13 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1077,24 +984,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1107,24 +1010,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1137,14 +1036,13 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1157,24 +1055,20 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1189,7 +1083,6 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Android 4+ devices. @@ -1198,7 +1091,7 @@ This setting is available only on Android 4+ devices. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1211,24 +1104,20 @@ Accept wildcard characters: False The PasswordRequired parameter specifies whether a password is required to access devices. Valid values for this parameter are: - $true: Device passwords are required. - - $false: Device passwords aren't required. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1243,11 +1132,8 @@ The PasswordTimeout parameter specifies the length of time that devices can be i This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1256,7 +1142,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1269,22 +1155,19 @@ Accept wildcard characters: False The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on devices. Valid values for this parameter are: - $true: Memory is encrypted. - - $false: Memory isn't encrypted. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 (already encrypted and can't be unencrypted) - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1294,28 +1177,19 @@ Accept wildcard characters: False ``` ### -RegionRatings -The RegionRatings parameter specifies the rating system (country) to use for movie and television ratings with the MoviesRating and TVShowsRating parameters. +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: - $null (blank): The setting isn't configured. This is the default value. - - au: Australia - - ca: Canada - - de: Germany - - fr: France - - gb: United Kingdom - - ie: Ireland - - jp: Japan - - nz: New Zealand - - us: United States This setting is available only on Apple iOS 6+ devices. @@ -1324,7 +1198,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingRegionEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1337,16 +1211,14 @@ Accept wildcard characters: False 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. - - $false: An email profile isn't required. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1359,9 +1231,7 @@ Accept wildcard characters: False The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen on devices. Valid values for this parameter are: - $true: SmartScreen is enabled. - - $false: SmartScreen is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -1370,7 +1240,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1383,9 +1253,7 @@ Accept wildcard characters: False The SystemSecurityTLS parameter specifies whether TLS encryption is used on devices. Valid values for this parameter are: - $true: TLS encryption is used. - - $false: TLS encryption isn't used. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -1394,7 +1262,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1404,66 +1272,46 @@ Accept wildcard characters: False ``` ### -TVShowsRating -The TVShowsRating parameter species the maximum or most restrictive rating of television shows that are allowed on devices. You specify the country rating system to use with the RegionRatings parameter. +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: - AllowAll: All television shows are allowed, regardless of their rating. - - DontAllow: No televisions shows are allowed, regardless of their rating. - - $null (blank): The setting isn't configured. This is the default value. Australia - AURatingP - - AURatingC - - AURatingG - - AURatingPG - - AURatingM - - AURatingMA15plus - - AURatingAv15plus Canada - CARatingC - - CARatingC8 - - CARatingG - - CARatingPG - - CARating14plus - - CARating18plus Germany - DERatingab0Jahren - - DERatingab6Jahren - - DERatingab12Jahren - - DERatingab16Jahren - - DERatingab18Jahren France - FRRating10minus - - FRRating12minus - - FRRating16minus - - FRRating18minus United Kingdom @@ -1473,13 +1321,9 @@ United Kingdom Ireland - IERatingGA - - IERatingCh - - IERatingYA - - IERatingPS - - IERatingMA Japan @@ -1489,23 +1333,16 @@ Japan New Zealand - NZRatingG - - NZRatingPGR - - NZRatingAO United States - USRatingTVY - - USRatingTVY7 - - USRatingTVG - - USRatingTVPG - - USRatingTV14 - - USRatingTVMA This setting is available only on Apple iOS 6+ devices. @@ -1514,7 +1351,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingTvShowEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1527,13 +1364,9 @@ Accept wildcard characters: False 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. - - AlwaysNotify - - NeverNotify - - NotifyAppChanges - - NotifyAppChangesDoNotDimdesktop This setting is available only on Windows 8.1 RT devices. @@ -1542,7 +1375,7 @@ This setting is available only on Windows 8.1 RT devices. Type: CAUserAccountControlStatusEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1552,13 +1385,13 @@ Accept wildcard characters: False ``` ### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. +The WhatIf switch doesn't work in Security & Compliance PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1571,9 +1404,7 @@ Accept wildcard characters: False The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid values for this parameter are: - $true: Wi-Fi is enabled. - - $false: Wi-Fi is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Microsoft Windows Phone 8.1 devices. @@ -1582,7 +1413,7 @@ This setting is available only on Microsoft Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1594,7 +1425,7 @@ Accept wildcard characters: False ### -WorkFoldersSyncUrl 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. +Valid input for this parameter a URL. For example, `https://workfolders.contoso.com`. This setting is available only on Windows 8.1 RT devices. @@ -1602,7 +1433,7 @@ This setting is available only on Windows 8.1 RT devices. Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1616,12 +1447,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md new file mode 100644 index 0000000000..67e19df788 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md @@ -0,0 +1,169 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DeviceConfigurationPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DeviceConfigurationPolicy cmdlet to create mobile device configuration policies in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DeviceConfigurationPolicy [-Name] + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DeviceConfigurationPolicy -Name "Engineering Group" +``` + +This example creates a new mobile device configuration policy named Engineering Group. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/New-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md similarity index 82% rename from exchange/exchange-ps/exchange/devices/New-DeviceConfigurationRule.md rename to exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md index aad30cab94..e4505ceb8f 100644 --- a/exchange/exchange-ps/exchange/devices/New-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md @@ -1,66 +1,91 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-deviceconfigurationrule -applicable: Office 365 Security & Compliance Center +online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconfigurationrule +applicable: Security & Compliance title: New-DeviceConfigurationRule schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "o365scc-ps" --- # New-DeviceConfigurationRule ## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). -Use the New-DeviceConfigurationRule cmdlet to create mobile device configuration rules in the Security & Compliance Center. +Use the New-DeviceConfigurationRule cmdlet to create mobile device configuration rules in Basic Mobility and Security in Microsoft 365. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` New-DeviceConfigurationRule -Policy -TargetGroups - [-AccountName ] [-AccountUserName ] [-AllowAppStore ] - [-AllowAssistantWhileLocked ] [-AllowConvenienceLogon ] - [-AllowDiagnosticSubmission ] [-AllowiCloudBackup ] - [-AllowiCloudDocSync ] [-AllowiCloudPhotoSync ] - [-AllowPassbookWhileLocked ] [-AllowScreenshot ] - [-AllowSimplePassword ] [-AllowVideoConferencing ] - [-AllowVoiceAssistant ] [-AllowVoiceDialing ] - [-AntiVirusSignatureStatus ] [-AntiVirusStatus ] + [-AccountName ] + [-AccountUserName ] + [-AllowAppStore ] + [-AllowAssistantWhileLocked ] + [-AllowConvenienceLogon ] + [-AllowDiagnosticSubmission ] + [-AllowiCloudBackup ] + [-AllowiCloudDocSync ] + [-AllowiCloudPhotoSync ] + [-AllowPassbookWhileLocked ] + [-AllowScreenshot ] + [-AllowSimplePassword ] + [-AllowVideoConferencing ] + [-AllowVoiceAssistant ] + [-AllowVoiceDialing ] + [-AntiVirusSignatureStatus ] + [-AntiVirusStatus ] [-AppsRating ] [-AutoUpdateStatus ] - [-BluetoothEnabled ] [-CameraEnabled ] [-Confirm] [-DomainController ] - [-EmailAddress ] [-EnableRemovableStorage ] [-ExchangeActiveSyncHost ] - [-FirewallStatus ] [-ForceAppStorePassword ] - [-ForceEncryptedBackup ] [-MaxPasswordAttemptsBeforeWipe ] + [-BluetoothEnabled ] + [-CameraEnabled ] + [-Confirm] + [-DomainController ] + [-EmailAddress ] + [-EnableRemovableStorage ] + [-ExchangeActiveSyncHost ] + [-FirewallStatus ] + [-ForceAppStorePassword ] + [-ForceEncryptedBackup ] + [-MaxPasswordAttemptsBeforeWipe ] [-MaxPasswordGracePeriod ] [-MoviesRating ] - [-PasswordComplexity ] [-PasswordExpirationDays ] [-PasswordHistoryCount ] - [-PasswordMinComplexChars ] [-PasswordMinimumLength ] [-PasswordQuality ] - [-PasswordRequired ] [-PasswordTimeout ] [-PhoneMemoryEncrypted ] - [-RegionRatings ] [-RequireEmailProfile ] - [-SmartScreenEnabled ] [-SystemSecurityTLS ] + [-PasswordComplexity ] + [-PasswordExpirationDays ] + [-PasswordHistoryCount ] + [-PasswordMinComplexChars ] + [-PasswordMinimumLength ] + [-PasswordQuality ] + [-PasswordRequired ] + [-PasswordTimeout ] + [-PhoneMemoryEncrypted ] + [-RegionRatings ] + [-RequireEmailProfile ] + [-SmartScreenEnabled ] + [-SystemSecurityTLS ] [-TVShowsRating ] [-UserAccountControlStatus ] - [-WhatIf] [-WLANEnabled ] [-WorkFoldersSyncUrl ] [] + [-WhatIf] + [-WLANEnabled ] + [-WorkFoldersSyncUrl ] + [] ``` ## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. +The cmdlets in Basic Mobility and Security are described in the following list: +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. - DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). ## EXAMPLES @@ -72,7 +97,6 @@ New-DeviceConfigurationRule -Policy "Engineering Group" -TargetGroups 5bff73eb-0 This example creates a new mobile device configuration rule with the following settings: - Policy: Engineering Group - - TargetGroups:5bff73eb-0ba7-461b-b7c9-9b4c173cc266 ## PARAMETERS @@ -81,16 +105,14 @@ This example creates a new mobile device configuration rule with the following s 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 - - Distinguished name (DN) - - GUID ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: True Position: Named @@ -108,7 +130,7 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: True Position: Named @@ -121,14 +143,13 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -141,14 +162,13 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -161,22 +181,19 @@ Accept wildcard characters: False 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. - - $false: Access to the app store isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -189,9 +206,7 @@ Accept wildcard characters: False 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. - - $false: The voice assistant can't be used while devices are locked. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -200,7 +215,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -213,9 +228,7 @@ Accept wildcard characters: False The AllowConvenienceLogon parameter specifies whether to allow convenience logons on devices. Valid values for this parameter are: - $true: Convenience logons are allowed. - - $false: Convenience logons aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -224,7 +237,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -237,24 +250,20 @@ Accept wildcard characters: False The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic submissions from devices. Valid values for this parameter are: - $true: Diagnostic submissions are allowed. - - $false: Diagnostic submissions aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -267,22 +276,19 @@ Accept wildcard characters: False The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup from devices. Valid values for this parameter are: - $true: iCloud Backup is allowed. - - $false: iCloud Backup isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -295,22 +301,19 @@ Accept wildcard characters: False 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. - - $false: iCloud Documents & Data sync isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -323,22 +326,19 @@ Accept wildcard characters: False 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. - - $false: iCloud Photo sync isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -351,9 +351,7 @@ Accept wildcard characters: False 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. - - $false: Passbook isn't available while devices are locked. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -362,7 +360,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -375,22 +373,19 @@ Accept wildcard characters: False The AllowScreenshot parameter specifies whether to allow screenshots on devices. Valid values for this parameter are: - $true: Screenshots are allowed. - - $false: Screenshots aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -403,24 +398,20 @@ Accept wildcard characters: False 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. - - $false: Simple passwords aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -433,9 +424,7 @@ Accept wildcard characters: False The AllowVideoConferencing parameter specifies whether to allow video conferencing on devices. Valid values for this parameter are: - $true: Video conferencing is allowed. - - $false: Video conferencing isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -444,7 +433,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -457,9 +446,7 @@ Accept wildcard characters: False 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. - - $false: The voice assistant isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -468,7 +455,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -481,9 +468,7 @@ Accept wildcard characters: False The AllowVoiceDialing parameter specifies whether to allow voice-activated telephone dialing. Valid values for this parameter are: - $true: Voice dialing is allowed. - - $false: Voice dialing isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -492,7 +477,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -505,7 +490,6 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -514,7 +498,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -527,7 +511,6 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -536,7 +519,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -549,15 +532,10 @@ Accept wildcard characters: False The AppsRating parameter species the maximum or most restrictive rating of apps that are allowed on devices. Valid values for this parameter are: - AllowAll - - DontAllow - - Rating9plus - - Rating12plus - - Rating17plus - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -566,7 +544,7 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingAppsEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -579,15 +557,10 @@ Accept wildcard characters: False The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are: - AutomaticCheckForUpdates - - AutomaticDownloadUpdates - - AutomaticUpdatesRequired - - DeviceDefault - - NeverCheckUpdates - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -596,7 +569,7 @@ This setting is available only on Windows 8.1 RT devices. Type: AutoUpdateStatusEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -609,9 +582,7 @@ Accept wildcard characters: False The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth on devices. Valid values for this parameter are: - $true: Bluetooth is enabled. - - $false: Bluetooth is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows Phone 8.1 devices. @@ -620,7 +591,7 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -633,24 +604,20 @@ Accept wildcard characters: False The CameraEnabled parameter specifies whether to enable or disable cameras on devices. Valid values for this parameter are: - $true: Cameras are enabled. - - $false: Cameras are disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -662,15 +629,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -686,7 +652,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -699,14 +665,13 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -719,9 +684,7 @@ Accept wildcard characters: False The EnableRemovableStorage parameter specifies whether removable storage can be used by devices. Valid values for this parameter are: - $true: Removable storage can be used. - - $false: Removable storage can't be used. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows Phone 8.1 devices. @@ -730,7 +693,7 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -743,14 +706,13 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -763,7 +725,6 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -772,7 +733,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Required Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -785,9 +746,7 @@ Accept wildcard characters: False 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. - - $false: App store passwords aren't required. - - $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -796,7 +755,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -809,22 +768,19 @@ Accept wildcard characters: False The ForceEncryptedBackup parameter specifies whether to force encrypted backups for devices. Valid values for this parameter are: - $true: Encrypted backups are required. - - $false: Encrypted backups aren't required. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -837,24 +793,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -874,7 +826,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -884,130 +836,88 @@ Accept wildcard characters: False ``` ### -MoviesRating -The MoviesRating parameter species the maximum or most restrictive rating of movies that are allowed on devices. You specify the country rating system to use with the RegionRatings parameter. +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: - AllowAll: All movies are allowed, regardless of their rating. - - DontAllow: No movies are allowed, regardless of their rating. - - $null (blank): The setting isn't configured. This is the default value. Australia - AURatingG - - AURatingPG - - AURatingM - - AURatingMA15plus - - AURatingR18plus Canada - CARatingG - - CARatingPG - - CARating14A - - CARating18A - - CARatingR Germany - DERatingab0Jahren - - DERatingab6Jahren - - DERatingab12Jahren - - DERatingab16Jahren - - DERatingab18Jahren France - FRRating10minus - - FRRating12minus - - FRRating16minus - - FRRating18minus United Kingdom - GBRatingU - - GBRatingUc - - GBRatingPG - - GBRating12 - - GBRating12A - - GBRating15 - - GBRating18 Ireland - IERatingG - - IERatingPG - - IERating12 - - IERating15 - - IERating16 - - IERating18 Japan - JPRatingG - - JPRatingPG12 - - JPRatingRdash15 - - JPRatingRdash18 New Zealand - NZRatingG - - NZRatingPG - - NZRatingM - - NZRatingR13 - - NZRatingR15 - - NZRatingR16 - - NZRatingR18 - - NZRatingR United States - USRatingG - - USRatingPG - - USRatingPG13 - - USRatingR - - USRatingNC17 This setting is available only on Apple iOS 6+ devices. @@ -1016,7 +926,7 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingMovieEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1029,14 +939,13 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1049,24 +958,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1079,24 +984,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1109,14 +1010,13 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1129,24 +1029,20 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1161,7 +1057,6 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Android 4+ devices. @@ -1170,7 +1065,7 @@ This setting is available only on Android 4+ devices. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1183,24 +1078,20 @@ Accept wildcard characters: False The PasswordRequired parameter specifies whether a password is required to access devices. Valid values for this parameter are: - $true: Device passwords are required. - - $false: Device passwords aren't required. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1215,11 +1106,8 @@ The PasswordTimeout parameter specifies the length of time that devices can be i This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1228,7 +1116,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1241,22 +1129,19 @@ Accept wildcard characters: False The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on devices. Valid values for this parameter are: - $true: Memory is encrypted. - - $false: Memory isn't encrypted. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 (already encrypted and can't be unencrypted) - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1266,28 +1151,19 @@ Accept wildcard characters: False ``` ### -RegionRatings -The RegionRatings parameter specifies the rating system (country) to use for movie and television ratings with the MoviesRating and TVShowsRating parameters. +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: - $null (blank): The setting isn't configured. This is the default value. - - au: Australia - - ca: Canada - - de: Germany - - fr: France - - gb: United Kingdom - - ie: Ireland - - jp: Japan - - nz: New Zealand - - us: United States This setting is available only on Apple iOS 6+ devices. @@ -1296,7 +1172,7 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingRegionEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1309,16 +1185,14 @@ Accept wildcard characters: False 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. - - $false: An email profile isn't required. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1331,9 +1205,7 @@ Accept wildcard characters: False The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen on devices. Valid values for this parameter are: - $true: SmartScreen is enabled. - - $false: SmartScreen is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -1342,7 +1214,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1355,9 +1227,7 @@ Accept wildcard characters: False The SystemSecurityTLS parameter specifies whether TLS encryption is used on devices. Valid values for this parameter are: - $true: TLS encryption is used. - - $false: TLS encryption isn't used. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -1366,7 +1236,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1376,66 +1246,46 @@ Accept wildcard characters: False ``` ### -TVShowsRating -The TVShowsRating parameter species the maximum or most restrictive rating of television shows that are allowed on devices. You specify the country rating system to use with the RegionRatings parameter. +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: - AllowAll: All television shows are allowed, regardless of their rating. - - DontAllow: No televisions shows are allowed, regardless of their rating. - - $null (blank): The setting isn't configured. This is the default value. Australia - AURatingP - - AURatingC - - AURatingG - - AURatingPG - - AURatingM - - AURatingMA15plus - - AURatingAv15plus Canada - CARatingC - - CARatingC8 - - CARatingG - - CARatingPG - - CARating14plus - - CARating18plus Germany - DERatingab0Jahren - - DERatingab6Jahren - - DERatingab12Jahren - - DERatingab16Jahren - - DERatingab18Jahren France - FRRating10minus - - FRRating12minus - - FRRating16minus - - FRRating18minus United Kingdom @@ -1445,13 +1295,9 @@ United Kingdom Ireland - IERatingGA - - IERatingCh - - IERatingYA - - IERatingPS - - IERatingMA Japan @@ -1461,23 +1307,16 @@ Japan New Zealand - NZRatingG - - NZRatingPGR - - NZRatingAO United States - USRatingTVY - - USRatingTVY7 - - USRatingTVG - - USRatingTVPG - - USRatingTV14 - - USRatingTVMA This setting is available only on Apple iOS 6+ devices. @@ -1486,7 +1325,7 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingTvShowEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1499,13 +1338,9 @@ Accept wildcard characters: False 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. - - AlwaysNotify - - NeverNotify - - NotifyAppChanges - - NotifyAppChangesDoNotDimdesktop This setting is available only on Windows 8.1 RT devices. @@ -1514,7 +1349,7 @@ This setting is available only on Windows 8.1 RT devices. Type: UserAccountControlStatusEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1524,13 +1359,13 @@ Accept wildcard characters: False ``` ### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. +The WhatIf switch doesn't work in Security & Compliance PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1543,9 +1378,7 @@ Accept wildcard characters: False The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid values for this parameter are: - $true: Wi-Fi is enabled. - - $false: Wi-Fi is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Microsoft Windows Phone 8.1 devices. @@ -1554,7 +1387,7 @@ This setting is available only on Microsoft Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1566,7 +1399,7 @@ Accept wildcard characters: False ### -WorkFoldersSyncUrl 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. +Valid input for this parameter a URL. For example, `https://workfolders.contoso.com`. This setting is available only on Windows 8.1 RT devices. @@ -1574,7 +1407,7 @@ This setting is available only on Windows 8.1 RT devices. Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1588,12 +1421,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md new file mode 100644 index 0000000000..13317afc2d --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md @@ -0,0 +1,152 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DeviceTenantPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DeviceTenantPolicy cmdlet to create your organization's mobile device tenant policy in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DeviceTenantPolicy [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DeviceTenantPolicy +``` + +This example creates your organization's mobile device tenant policy. You can have only one mobile device tenant policy in your organization. + +## PARAMETERS + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DeviceTenantRule.md b/exchange/exchange-ps/exchange/New-DeviceTenantRule.md new file mode 100644 index 0000000000..214a1d7524 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DeviceTenantRule.md @@ -0,0 +1,177 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DeviceTenantRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DeviceTenantRule cmdlet to create your organization's mobile device tenant rule in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DeviceTenantRule [-ApplyPolicyTo ] + [-BlockUnsupportedDevices ] + [-Confirm] + [-DomainController ] + [-ExclusionList ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DeviceTenantRule -ExclusionList "e10214c1-49b6-47d2-b5e6-466e918648b1","6e3931bd-a716-4bb9-9a2f-093aa2c967b4" +``` + +This example creates a new mobile device tenant rule with GUIDs of the security groups named Engineering and Research and Development on the exclusion list. Members of these groups are allowed access even if they use non-compliant devices + +You can have only one mobile device tenant rule in your organization. + +## PARAMETERS + +### -ApplyPolicyTo +The ApplyPolicyTo parameter specifies where to apply the policy in your organization. Valid values for this parameter are: + +- ExchangeOnline +- SharePointOnline +- ExchangeAndSharePoint + +```yaml +Type: PolicyResourceScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockUnsupportedDevices +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. +- $false: Unsupported devices are allowed. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExclusionList +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. + +You can specify multiple groups separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/New-DistributionGroup.md b/exchange/exchange-ps/exchange/New-DistributionGroup.md similarity index 81% rename from exchange/exchange-ps/exchange/users-and-groups/New-DistributionGroup.md rename to exchange/exchange-ps/exchange/New-DistributionGroup.md index 7d5f730551..de47db246c 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/New-DistributionGroup.md +++ b/exchange/exchange-ps/exchange/New-DistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/new-distributiongroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-DistributionGroup @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-DistributionGroup cmdlet to create distribution groups and mail-enabled security groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,14 @@ For information about the parameter sets in the Syntax section below, see [Excha New-DistributionGroup [-Name] [-Alias ] [-ArbitrationMailbox ] + [-BccBlocked ] [-BypassNestedModerationEnabled ] [-Confirm] [-CopyOwnerToMember] + [-Description ] [-DisplayName ] [-DomainController ] + [-HiddenGroupMembershipEnabled] [-IgnoreNamingPolicy] [-ManagedBy ] [-MemberDepartRestriction ] @@ -39,26 +41,27 @@ New-DistributionGroup [-Name] [-ModerationEnabled ] [-Notes ] [-OrganizationalUnit ] - [-OverrideRecipientQuotas] [-PrimarySmtpAddress ] [-RequireSenderAuthenticationEnabled ] [-RoomList] [-SamAccountName ] [-SendModerationNotifications ] [-Type ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can use the New-DistributionGroup cmdlet to create the following types of groups: - Mail-enabled universal security groups (USGs) - - Universal distribution groups Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Distribution groups aren't security principals, and therefore can't be assigned permissions. However, you can assign permissions to mail-enabled security groups. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. ## EXAMPLES @@ -99,16 +102,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -134,23 +141,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -166,11 +164,31 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -BccBlocked +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: + +- $true: If the group is used in the Bcc line, members of the group don't receive the message, and the sender receives a non-delivery report (also known as an NDR or bounce message). Other recipients of the message aren't blocked. If an external sender uses the group in the Bcc line, members of the group aren't blocked. For nested groups, the message is blocked only for members of the top-level group. +- $false: There are no restrictions for using the group in the Bcc line of messages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -BypassNestedModerationEnabled 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. - - $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This is the default value. This parameter can be used only by top-level organization and tenant administrators. @@ -191,8 +209,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -224,6 +241,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Description +This parameter is available only in the cloud-based service. + +{{ Fill Description Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DisplayName 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 ("). @@ -262,6 +297,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -HiddenGroupMembershipEnabled +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. + +You can use this setting to help comply with regulations that require you to hide group membership from members or outsiders (for example, a distribution group that represents students enrolled in a class). + +**Note**: If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IgnoreNamingPolicy 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. @@ -284,42 +341,36 @@ Accept wildcard characters: False 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 - - Add or remove group members - - Delete the group - - Approve member depart or join requests (if available) - - Approve messages sent to the group if moderation is enabled, but no moderators are specified. -The owner 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 owner. For example: +The owner 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). -- Name +Considerations for mail-enabled security groups as group owners: -- Alias +- If you specify a mail-enabled security group as a group owner in on-premises Exchange, the mail-enabled security group doesn't sync to the cloud object. +- Group management in Outlook doesn't work if the owner is a mail-enabled security group. To manage the group in Outlook, the owner must be a mailbox or a mail user. If you specify a mail-enabled security group as the owner of the group, the group isn't visible in **Distribution groups I own** for the group owners (members of the mail-enabled security group). -- Distinguished name (DN) +You can use any value that uniquely identifies the owner. For example: +- Name +- Alias +- Distinguished name (DN) - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +To enter multiple owners, use the following syntax: `Owner1,Owner2,...OwnerN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Owner1","Owner2",..."OwnerN"`. -An owner that you specify with this parameter isn't automatically a member of the group. You need to manually add the owner as a member. +Owners that you specify with this parameter are not automatically added as group members. Use the CopyOwnerToMember switch or manually add the owners as members. -Alternatively, you can use the CopyOwnerToMember switch so the owners are automatically made members of the group. +**Note**: Group management in Outlook doesn't work when the owner is a mail-enabled security group. To manage the group in Outlook, the owner must be a mailbox or a mail user. ```yaml Type: MultiValuedProperty @@ -338,7 +389,6 @@ Accept wildcard characters: False 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. - - Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This is the default value for universal security groups. ```yaml @@ -358,9 +408,7 @@ Accept wildcard characters: False 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. - - Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This is the default value on universal security groups and universal distribution groups. - - ApprovalRequired: Users can request to join the group. The user is added to the group after the request is approved by one of the group owners. Although you can use this value on universal security groups, user requests to join the group aren't sent to the group owners, so this setting is only effective on universal distribution groups. ```yaml @@ -380,23 +428,20 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. After you create the group, you use the Get-DistributionGroupMember cmdlet to view the group members, and the Add-DistributionGroupMember, Remove-DistributionGroupMember, and Update-DistributionGroupMember cmdlets to manage group membership. Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned. +The maximum number of entries for this parameter is 10000. + ```yaml Type: MultiValuedProperty Parameter Sets: (All) @@ -414,18 +459,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. For mail-enabled security groups, you need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -448,7 +488,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -488,11 +527,8 @@ The OrganizationalUnit parameter specifies the location in Active Directory wher 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -508,22 +544,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OverrideRecipientQuotas -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, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -PrimarySmtpAddress The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. @@ -544,7 +564,6 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. The default value is $true. @@ -583,7 +602,7 @@ Accept wildcard characters: False ### -SamAccountName 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 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. +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 @@ -602,9 +621,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -626,7 +643,6 @@ Accept wildcard characters: False 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. - - Security: A mail-enabled security group. These groups can have permissions assigned. The group's scope is always Universal. @@ -665,12 +681,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/New-DkimSigningConfig.md b/exchange/exchange-ps/exchange/New-DkimSigningConfig.md similarity index 82% rename from exchange/exchange-ps/exchange/antispam-antimalware/New-DkimSigningConfig.md rename to exchange/exchange-ps/exchange/New-DkimSigningConfig.md index 5c0e37be7a..5bd296a8ba 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/New-DkimSigningConfig.md +++ b/exchange/exchange-ps/exchange/New-DkimSigningConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/new-dkimsigningconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # New-DkimSigningConfig @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the New-DkimSigningConfig cmdlet to create the DomainKeys Identified Mail (DKIM) signing policy settings for domains in a cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,13 +27,14 @@ New-DkimSigningConfig [-DomainName] [-Enabled] ] [-KeySize ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -DKIM in Microsoft Office 365 is an email authentication method that uses a public key infrastructure (PKI), message headers, and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field. +DKIM in Microsoft 365 is an email authentication method that uses a public key infrastructure (PKI), message headers, and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -73,8 +70,7 @@ Accept wildcard characters: False ### -Enabled The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. - +- $true: The policy is enabled. - $false: The policy is disabled. ```yaml @@ -110,7 +106,6 @@ Accept wildcard characters: False 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. - - Simple: Only changes in empty lines at the end of the message body are tolerated. ```yaml @@ -129,8 +124,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -150,7 +144,6 @@ Accept wildcard characters: False 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. - - Simple: No changes to the header fields are tolerated. ```yaml @@ -167,9 +160,12 @@ Accept wildcard characters: False ``` ### -KeySize -The KeySize parameter specifies the size in bits of the public key that's used in the DKIM signing policy. Valid values are 1024 or 2048. +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) +- 2048 -RSA keys are supported; Ed25519 keys aren't supported. +RSA keys are supported. Ed25519 keys aren't supported. ```yaml Type: UInt16 @@ -205,12 +201,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md new file mode 100644 index 0000000000..53dccb7f13 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md @@ -0,0 +1,1061 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DlpCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DlpCompliancePolicy cmdlet to create data loss prevention (DLP) policies in the Microsoft Purview compliance portal. DLP policies contain DLP rules that identify, monitor, and protect sensitive information. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DlpCompliancePolicy [-Name] + [-Comment ] + [-Confirm] + [-EndpointDlpAdaptiveScopes ] + [-EndpointDlpAdaptiveScopesException ] + [-EndpointDlpExtendedLocations ] + [-EndpointDlpLocation ] + [-EndpointDlpLocationException ] + [-EnforcementPlanes ] + [-ExceptIfOneDriveSharedBy ] + [-ExceptIfOneDriveSharedByMemberOf ] + [-ExchangeAdaptiveScopes ] + [-ExchangeAdaptiveScopesException ] + [-ExchangeLocation ] + [-ExchangeSenderMemberOf ] + [-ExchangeSenderMemberOfException ] + [-Force] + [-IsFromSmartInsights ] + [-Locations ] + [-Mode ] + [-OneDriveAdaptiveScopes ] + [-OneDriveAdaptiveScopesException ] + [-OneDriveLocation ] + [-OneDriveLocationException ] + [-OneDriveSharedBy ] + [-OneDriveSharedByMemberOf ] + [-OnPremisesScannerDlpLocation ] + [-OnPremisesScannerDlpLocationException ] + [-PolicyRBACScopes ] + [-PolicyTemplateInfo ] + [-PowerBIDlpLocation ] + [-PowerBIDlpLocationException ] + [-Priority ] + [-SharePointAdaptiveScopes ] + [-SharePointAdaptiveScopesException ] + [-SharePointLocation ] + [-SharePointLocationException ] + [-TeamsAdaptiveScopes ] + [-TeamsAdaptiveScopesException ] + [-TeamsLocation ] + [-TeamsLocationException ] + [-ThirdPartyAppDlpLocation ] + [-ThirdPartyAppDlpLocationException ] + [-ValidatePolicy] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DlpCompliancePolicy -Name "GlobalPolicy" -SharePointLocation All +``` + +This example creates a DLP policy named GlobalPolicy that will be enforced across all SharePoint locations. + +### Example 2 +```powershell +New-DlpCompliancePolicy -Name "GlobalPolicy" -Comment "Primary policy" -SharePointLocation "https://my.url/","https://my.url2/" -OneDriveLocation "https://my.url3/","https://my.url4/" -Mode Enable +``` + +This example creates a DLP policy named GlobalPolicy for the specified SharePoint and OneDrive locations. The new policy has a descriptive comment and will be enabled on creation. + +### Example 3 +```powershell +New-DlpCompliancePolicy -Name "PowerBIPolicy" -Comment "Primary policy" -PowerBIDlpLocation "All" -PowerBIDlpLocationException "workspaceID1","workspaceID2","workspaceID3" -Mode Enable +``` + +This example creates a DLP policy named PowerBIPolicy for all qualifying Power BI workspaces (that is, those hosted on Premium Gen2 capacities) except for the specified workspaces. The new policy has a descriptive comment and will be enabled on creation. + +### Example 4 +```powershell +Get-Label | Format-List Priority,ContentType,Name,DisplayName,Identity,Guid + +$guidVar = "e222b65a-b3a8-46ec-ae12-00c2c91b71c0" + +$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{Type:"Tenant", Identity:"All"}]}]" + +New-DLPCompliancePolicy -Name "Copilot Policy" -Locations $loc + +$advRule = @{ + "Version" = "1.0" + "Condition" = @{ + "Operator" = "And" + "SubConditions" = @( + @{ + "ConditionName" = "ContentContainsSensitiveInformation" + "Value" = @( + @{ + "groups" = @( + @{ + "Operator" = "Or" + "labels" = @( + @{ + "name" = $guidVar + "type" = "Sensitivity" + } + ) + "name" = "Default" + } + ) + } + ) + } + ) + } +} | ConvertTo-Json -Depth 100 + +New-DLPComplianceRule -Name "Copilot Rule" -Policy "Copilot Policy" -AdvancedRule $advrule -RestrictAccess @(@{setting="ExcludeContentProcessing";value="Block"}) +``` + +This example creates a DLP policy for Microsoft 365 Copilot (Preview) in several steps: + +- The first command returns information about all sensitivity labels. Select the GUID value of the sensitivity label that you want to use. For example, `e222b65a-b3a8-46ec-ae12-00c2c91b71c0`. + +- The second command stores the GUID value of the sensitivity label in the variable named `$guidVar`. + +- The third command stores the Microsoft 365 Copilot location (`470f2276-e011-4e9d-a6ec-20768be3a4b0`) in the variable named `$loc`. Update the `$loc` value based on the Inclusions/Exclusions scoping that you want to provide. + +- The fourth command creates the DLP policy using the `$loc` variable for the value of the Locations parameter, and "Copilot Policy" as the name of the policy (use any unique name). + +- The fifth command creates the variable named `$advRule`. The advanced rule needs to be updated depending on the grouping of labels you want to provide as input. + +- The last command creates the DLP rule with the name "Copilot Rule" (use any unique name). Use the name of the DLP policy from step four as the value of the Policy parameter. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpAdaptiveScopes +{{ Fill EndpointDlpAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpAdaptiveScopesException +{{ Fill EndpointDlpAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpExtendedLocations +{{ Fill EndpointDlpExtendedLocations Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpLocation +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpLocationException +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnforcementPlanes +The EnforcementPlanes parameter defines the layer where policy actions are run. This parameter uses the following syntax: + +`-EnforcementPlanes @("")`. + +Currently, the only supported value is Entra, for use with policies applied to an Entra-registered enterprise application in the organization. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedBy +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). + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedByMemberOf +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). + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopes +{{ Fill ExchangeAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopesException +{{ Fill ExchangeAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +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: + +- If you use `-ExchangeLocation All` by itself, the policy applies to email for all users. + +- To include email of specific group members in the policy, use `-ExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the policy. + +- To exclude email of specific group members from the policy, use `-ExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the policy. + +You can't specify inclusions and exclusions in the same policy. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOf +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: `"","",...""`. + +You must use this parameter with the ExchangeLocation parameter. + +You can't use this parameter with the ExchangeSenderMemberOfException parameter. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOfException +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: `"","",...""`. + +You must use this parameter with the ExchangeLocation parameter. + +You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsFromSmartInsights +{{ Fill IsFromSmartInsights Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locations +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`. +- Location: Where the DLP policy applies. For Microsoft 365 Copilot, (Preview), use the value `470f2276-e011-4e9d-a6ec-20768be3a4b0`. +- Inclusions: Who the DLP policy applies to. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:}`. For security groups or distribution groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group,Identity:}`. For the entire tenant, use this value: `{Type:"Tenant",Identity:"All"}`. +- Exclusions: Exclude security groups, distribution groups, or users from the scope of this DLP policy. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:}`. For groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group, Identity:}`. + +You create and store the properties in a variable as shown in the following examples: + +DLP policy scoped to all users in the tenant: + +`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{Type:"Tenant",Identity:"All"}]}]"` + +DLP policy scoped to the specified user and groups: + +`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{"Type":"Group","Identity":"fef0dead-5668-4bfb-9fc2-9879a47f9bdb"},{"Type":"Group","Identity":"b4dc1e1d-8193-4525-b59c-6d6e0f1718d2"},{"Type":"IndividualResource","Identity":"yibing@contoso.com"}]}]"` + +DLP policy scoped to all users in the tenant except for members of the specified group: + +`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{Type:"Tenant",Identity:"All"}]}],"Exclusions":[{"Type":"Group","Identity":"fef0dead-5668-4bfb-9fc2-9879a47f9bdb"}]}]"` + +After you create the `$loc` variable as shown in the previous examples, use the value `$loc` for this parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mode +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. +- Disable: The policy is disabled. +- TestWithNotifications: Simulation mode where no actions are taken, but notifications **are** sent. +- TestWithoutNotifications: Simulation mode where no actions are taken, and no notifications are sent. + +```yaml +Type: PolicyMode +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopes +{{ Fill OneDriveAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopesException +{{ Fill OneDriveAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocation +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: + +- To include sites of specific OneDrive accounts in the policy, use the OneDriveSharedBy parameter to specify the users. Only sites of the specified users are included in the policy. + +- To include sites of specific group members in the policy, use the OneDriveSharedByMemberOf parameter to specify the groups. Only sites of members of the specified groups are included in the policy. + +- To exclude sites of specific OneDrive accounts from the policy, use the ExceptIfOneDriveSharedBy parameter to specify the users. Only sites of the specified users are excluded from the policy. + +- To exclude sites of specific group members from the policy, use the ExceptIfOneDriveSharedByMemberOf parameter to specify the groups. Only sites of members of the specified groups are excluded from the policy. + +- If you use `-OneDriveLocation $null`, the policy does not apply to OneDrive sites. + +You can't specify inclusions and exclusions in the same policy. + +**Note**: Although this parameter accepts site URLs, don't specify site URLs values. Use the OneDriveSharedBy, ExceptIfOneDriveShareBy, OneDriveSharedByMemberOf, and ExceptIfOneDriveSharedByMemberOf parameters instead. In the DLP policy settings in the Microsoft Defender portal, you can't identify sites by URL; you specify sites only by users or groups. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocationException +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedBy +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). + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedByMemberOf +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). + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnPremisesScannerDlpLocation +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: `"","",...""`. + +For more information about the DLP on-premises scanner, see [Learn about the data loss prevention on-premises scanner](https://learn.microsoft.com/purview/dlp-on-premises-scanner-learn). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnPremisesScannerDlpLocationException +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: `"","",...""`. + +For more information about the DLP on-premises scanner, see [Learn about the data loss prevention on-premises scanner](https://learn.microsoft.com/purview/dlp-on-premises-scanner-learn). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTemplateInfo +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). + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PowerBIDlpLocation +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: + +- In the Admin portal, choose **Workspaces**, then select a workspace and choose **\> More options (...) \> Details**. +- Look in the URL of a selected workspace. +- In PowerShell, use the **Get-PowerBIWorkspace** cmdlet. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +**Note**: You can't use this parameter if the DLP policy applies to other locations. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PowerBIDlpLocationException +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: + +- In the Admin portal, choose **Workspaces**, then select a workspace and choose **\> More options (...) \> Details**. +- Look in the URL of a selected workspace. +- In PowerShell, use the **Get-PowerBIWorkspace** cmdlet. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 5 policies are from 0 through 4. +- Valid priority values for a new 6th policy are from 0 through 5. +- The default value for a new 6th policy is 5. + +If you modify the priority value of a policy, the position of the policy in the list changes to match the priority value you specify. In other words, if you set the priority value of a policy to the same value as an existing policy, the priority value of the existing policy and all other lower priority policies after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopes +{{ Fill SharePointAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopesException +{{ Fill SharePointAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocationException +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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAdaptiveScopes +{{ Fill TeamsAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAdaptiveScopesException +{{ Fill TeamsAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsLocation +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThirdPartyAppDlpLocation +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about DLP for non-Microsoft cloud apps, see [Use data loss prevention policies for non-Microsoft cloud apps](https://learn.microsoft.com/purview/dlp-use-policies-non-microsoft-cloud-apps). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThirdPartyAppDlpLocationException +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about DLP for non-Microsoft cloud apps, see [Use data loss prevention policies for non-Microsoft cloud apps](https://learn.microsoft.com/purview/dlp-use-policies-non-microsoft-cloud-apps). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidatePolicy +{{ Fill ValidatePolicy Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DlpComplianceRule.md b/exchange/exchange-ps/exchange/New-DlpComplianceRule.md new file mode 100644 index 0000000000..177d38fa19 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DlpComplianceRule.md @@ -0,0 +1,3634 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DlpComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DlpComplianceRule to create data loss prevention (DLP) rules in the Microsoft Purview compliance portal. DLP rules define sensitive information to be protected and the actions to take on rule matches. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DlpComplianceRule [-Name] -Policy + [-AccessScope ] + [-ActivationDate ] + [-AddRecipients ] + [-AdvancedRule ] + [-AlertProperties ] + [-AnyOfRecipientAddressContainsWords ] + [-AnyOfRecipientAddressMatchesPatterns ] + [-ApplyBrandingTemplate ] + [-ApplyHtmlDisclaimer ] + [-AttachmentIsNotLabeled ] + [-BlockAccess ] + [-BlockAccessScope ] + [-Comment ] + [-Confirm] + [-ContentCharacterSetContainsWords ] + [-ContentContainsSensitiveInformation ] + [-ContentExtensionMatchesWords ] + [-ContentFileTypeMatches ] + [-ContentIsNotLabeled ] + [-ContentIsShared ] + [-ContentPropertyContainsWords ] + [-Disabled ] + [-DocumentContainsWords ] + [-DocumentCreatedBy ] + [-DocumentCreatedByMemberOf ] + [-DocumentIsPasswordProtected ] + [-DocumentIsUnsupported ] + [-DocumentMatchesPatterns ] + [-DocumentNameMatchesPatterns ] + [-DocumentNameMatchesWords ] + [-DocumentSizeOver ] + [-DomainCountOver ] + [-EncryptRMSTemplate ] + [-EndpointDlpBrowserRestrictions ] + [-EndpointDlpRestrictions ] + [-EnforcePortalAccess ] + [-EvaluateRulePerComponent ] + [-ExceptIfAccessScope ] + [-ExceptIfAnyOfRecipientAddressContainsWords ] + [-ExceptIfAnyOfRecipientAddressMatchesPatterns ] + [-ExceptIfContentCharacterSetContainsWords ] + [-ExceptIfContentContainsSensitiveInformation ] + [-ExceptIfContentExtensionMatchesWords ] + [-ExceptIfContentFileTypeMatches ] + [-ExceptIfContentIsShared ] + [-ExceptIfContentPropertyContainsWords ] + [-ExceptIfDocumentContainsWords ] + [-ExceptIfDocumentCreatedBy ] + [-ExceptIfDocumentCreatedByMemberOf ] + [-ExceptIfDocumentIsPasswordProtected ] + [-ExceptIfDocumentIsUnsupported ] + [-ExceptIfDocumentMatchesPatterns ] + [-ExceptIfDocumentNameMatchesPatterns ] + [-ExceptIfDocumentNameMatchesWords ] + [-ExceptIfDocumentSizeOver ] + [-ExceptIfFrom ] + [-ExceptIfFromAddressContainsWords ] + [-ExceptIfFromAddressMatchesPatterns ] + [-ExceptIfFromMemberOf ] + [-ExceptIfFromScope ] + [-ExceptIfHasSenderOverride ] + [-ExceptIfHeaderContainsWords ] + [-ExceptIfHeaderMatchesPatterns ] + [-ExceptIfMessageSizeOver ] + [-ExceptIfMessageTypeMatches ] + [-ExceptIfProcessingLimitExceeded ] + [-ExceptIfRecipientADAttributeContainsWords ] + [-ExceptIfRecipientADAttributeMatchesPatterns ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSenderADAttributeContainsWords ] + [-ExceptIfSenderADAttributeMatchesPatterns ] + [-ExceptIfSenderDomainIs ] + [-ExceptIfSenderIPRanges ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-ExceptIfSubjectContainsWords ] + [-ExceptIfSubjectMatchesPatterns ] + [-ExceptIfSubjectOrBodyContainsWords ] + [-ExceptIfSubjectOrBodyMatchesPatterns ] + [-ExceptIfUnscannableDocumentExtensionIs ] + [-ExceptIfWithImportance ] + [-ExpiryDate ] + [-From ] + [-FromAddressContainsWords ] + [-FromAddressMatchesPatterns ] + [-FromMemberOf ] + [-FromScope ] + [-GenerateAlert ] + [-GenerateIncidentReport ] + [-HasSenderOverride ] + [-HeaderContainsWords ] + [-HeaderMatchesPatterns ] + [-ImmutableId ] + [-IncidentReportContent ] + [-MessageIsNotLabeled ] + [-MessageSizeOver ] + [-MessageTypeMatches ] + [-MipRestrictAccess ] + [-Moderate ] + [-ModifySubject ] + [-NonBifurcatingAccessScope ] + [-NotifyAllowOverride ] + [-NotifyEmailCustomSenderDisplayName ] + [-NotifyEmailCustomSubject ] + [-NotifyEmailCustomText ] + [-NotifyEmailExchangeIncludeAttachment ] + [-NotifyEmailOnedriveRemediationActions ] + [-NotifyEndpointUser ] + [-NotifyOverrideRequirements ] + [-NotifyPolicyTipCustomDialog ] + [-NotifyPolicyTipCustomText ] + [-NotifyPolicyTipCustomTextTranslations ] + [-NotifyPolicyTipDisplayOption ] + [-NotifyPolicyTipUrl ] + [-NotifyUser ] + [-NotifyUserType ] + [-OnPremisesScannerDlpRestrictions ] + [-PrependSubject ] + [-Priority ] + [-ProcessingLimitExceeded ] + [-Quarantine ] + [-RecipientADAttributeContainsWords ] + [-RecipientADAttributeMatchesPatterns ] + [-RecipientCountOver ] + [-RecipientDomainIs ] + [-RedirectMessageTo ] + [-RemoveHeader ] + [-RemoveRMSTemplate ] + [-ReportSeverityLevel ] + [-RestrictAccess ] + [-RestrictBrowserAccess ] + [-RuleErrorAction ] + [-SenderADAttributeContainsWords ] + [-SenderADAttributeMatchesPatterns ] + [-SenderAddressLocation ] + [-SenderDomainIs ] + [-SenderIPRanges ] + [-SentTo ] + [-SentToMemberOf ] + [-SetHeader ] + [-SharedByIRMUserRisk ] + [-StopPolicyProcessing ] + [-SubjectContainsWords ] + [-SubjectMatchesPatterns ] + [-SubjectOrBodyContainsWords ] + [-SubjectOrBodyMatchesPatterns ] + [-ThirdPartyAppDlpRestrictions ] + [-TriggerPowerAutomateFlow ] + [-UnscannableDocumentExtensionIs ] + [-ValidateRule] + [-WhatIf] + [-WithImportance ] + [] +``` + +## DESCRIPTION +Each new rule must contain one condition filter or test, and one associated action. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DlpComplianceRule -Name "SocialSecurityRule" -Policy "USFinancialChecks" -ContentContainsSensitiveInformation @{Name="U.S. Social Security Number (SSN)"} -BlockAccess $True +``` + +This example creates a new DLP compliance rule named "SocialSecurityRule" that is assigned to the "USFinancialChecks" policy. The rule checks for social security numbers and blocks access if it finds them. + +### Example 2 +```powershell +$contains_complex_types = @{ + operator = "And" + groups = @( + @{ + operator = "Or" + name = "PII Identifiers" + sensitivetypes = @( + @{ + name = "Drug Enforcement Agency (DEA) Number" + maxconfidence = 100 + minconfidence = 75 + mincount = 1 + maxcount = -1 + } + ) + } + @{ + operator = "Or" + name = "Medical Terms" + sensitivetypes = @( + @{ + name = "International Classification of Diseases (ICD-9-CM)" + maxconfidence = 100 + minconfidence = 75 + mincount = 1 + maxcount = -1 + } + @{ + name = "International Classification of Diseases (ICD-10-CM)" + maxconfidence = 100 + minconfidence = 75 + mincount = 1 + maxcount = -1 + } + ) + } + + ) +} + +New-DLPComplianceRule -Name "Contoso Medical Information" -Policy "Contoso Medical Checks" -ContentContainsSensitiveInformation $contains_complex_types +``` + +This example creates a new DLP compliance rule named "Contoso Medical Information". The rule is assigned to the "Contoso Medical Checks" policy. It uses advanced syntax to search for the specified content. + +### Example 3 +```powershell +Contents of the file named C:\Data\Sensitive Type.txt: + +{ +"Version": "1.0", +"Condition": { + "Operator": "And", + "SubConditions": [ + { + "ConditionName": "ContentContainsSensitiveInformation", + "Value": [ + { + "groups": [ + { + "Operator": "Or", + "labels": [ + { + "name": "defa4170-0d19-0005-000a-bc88714345d2", + "type": "Sensitivity" + } + ], + "name": "Default", + "sensitivetypes": [ + { + "confidencelevel": "Low", + "name": "Credit Card Number" + } + ] + } + ] + } + ] + }, + { + "Operator": "Not", + "SubConditions": [ + { + "Operator": "OR", + "SubConditions": [ + { + "ConditionName": "FromMemberOf", + "Value": [ + "janesteam@contoso.com" + ] + }, + { + "ConditionName": "SentTo", + "Value": [ + "adele@contoso.com" + ] + } + ], + } + ] + } + ] + } +} + +$data = Get-Content -Path "C:\Data\Sensitive Type.txt" -ReadCount 0 -encoding Byte + +$string = [System.Text.Encoding]::UTF8.GetString($data) + +New-DLPComplianceRule -Name "Contoso Rule 1" -Policy "Contoso Policy 1" -AdvancedRule $string -NotifyUser +``` + +This example uses the AdvancedRule parameter to read the following complex condition from a file: "Content contains sensitive information: "Credit card number OR Highly confidential" AND (NOT (Sender is a member of "Jane's Team" OR Recipient is "adele@contoso.com")). + +### Example 4 +```powershell + +$myEntraAppId = "" + +$myEntraAppName = "" + +$locations = "[{`"Workload`":`"Applications`",`"Location`":`"$myEntraAppId`",`"LocationDisplayName`":`"$myEntraAppName`",`"LocationSource`":`"Entra`",`"LocationType`":`"Individual`",`"Inclusions`":[{`"Type`":`"Tenant`",`"Identity`":`"All`"}]}]" + +New-DlpCompliancePolicy -Name "Test Entra DLP" -Mode Enable -Locations $locations -EnforcementPlanes @("Entra") + +New-DlpComplianceRule -Name "Test Entra Rule" -Policy "Test Entra DLP" -ContentContainsSensitiveInformation @{Name = "credit card number"} -GenerateAlert $true -GenerateIncidentReport @("siteadmin") -NotifyUser @("admin@contonso.onmicrosoft.com") -RestrictAccess @(@{setting="UploadText";value="Block"}) +``` + +This is an example of applying a CCSI-based DLP rule that should be handled by an entra-registered enterprise application in the organization. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessScope +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. +- NotInOrganization: The rule is applied to content that's accessible or delivered to a recipient outside the organization. +- None: The condition isn't used. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.AccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActivationDate +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddRecipients +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"}`. +- `@{AddManagerAsRecipientType = ""}`. For example, `@{AddManagerAsRecipientType = "Bcc"}`. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdvancedRule +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. + +For syntax details, see Example 3. + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlertProperties +{{ Fill AlertProperties Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressMatchesPatterns +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyBrandingTemplate +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyHtmlDisclaimer +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. +- Location: Specifies where to insert the HTML disclaimer text in the body of messages. Append = Add to the end of the message body. Prepend = Insert at the beginning of the message body. +- FallbackAction: Specifies what to do if the HTML disclaimer can't be added to a message. Wrap = The original message is wrapped in a new message envelope, and the disclaimer is used as the message body for the new message. Ignore = The rule is ignored and the message is delivered without the disclaimer. Reject = The message is rejected. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AttachmentIsNotLabeled +{{ Fill AttachmentIsNotLabeled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockAccess +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. +- $false: Allows access to the source item that matched the rule. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockAccessScope +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. +- PerUser: Blocks access to external users. +- PerAnonymousUser: Blocks access to people through the "Anyone with the link" option in SharePoint and OneDrive. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.BlockAccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentCharacterSetContainsWords +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`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})})})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +For an example of advanced syntax, see Example 2 in this topic. + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentFileTypeMatches +{{ Fill ContentFileTypeMatches Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentIsNotLabeled +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. +- $false: Don't look for unlabeled attachments or documents. + +In Exchange, this condition is matched only if both the attachment and the message body aren't labeled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentIsShared +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. +- $false: Don't look for unlabeled attachments or documents. + +In Exchange, this condition is matched only if both the attachment and the message body aren't labeled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter specifies whether the DLP rule is disabled. Valid values are: + +- $true: The rule is disabled. +- $false: The rule is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentContainsWords +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentCreatedBy +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentCreatedByMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentMatchesPatterns +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"`. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentNameMatchesPatterns +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -DomainCountOver +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. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -EncryptRMSTemplate +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. + +```yaml +Type: RmsTemplateIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpBrowserRestrictions +{{ Fill EndpointDlpBrowserRestrictions Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpRestrictions +**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"=""},...)`. + +The `` value is one of the supported values. + +The available values for `` are: Audit, Block, Ignore, or Warn. + +Example values: + +- `@{"Setting"="Print"; "Value"="Block"}` +- `@{"Setting"="CopyPaste"; "Value"="Block";}` +- `@{"Setting"="ScreenCapture"; "Value"="Block";}` +- `@{"Setting"="RemovableMedia"; "Value"="Block";}` +- `@{"Setting"="NetworkShare"; "Value"="Block";}` +- `@{"Setting"="Print"; "Value"="Audit";}` +- `@{"Setting"="UnallowedApps"; "Value"="notepad"; "value2"="Microsoft Notepad"}` + +When you use the values Block or Warn in this parameter, you also need to use the NotifyUser parameter. + +You can view and configure the available restrictions with the Get-PolicyConfig and Set-PolicyConfig cmdlets. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnforcePortalAccess +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. +- $false: External recipients aren't required to use the encrypted message portal. Outlook can decrypt messages inline. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EvaluateRulePerComponent +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). +- $false: A DLP rule match for conditions and exceptions can be anywhere in the message. + +For example, say a DLP rule is configured to block messages that contain three or more Social Security numbers (SSNs). When the value of this parameter is $true, a message is blocked only if there are three or more SSNs in the message body, or there are three or more SSNs in a specific attachment. The DLP rule doesn't match and the message isn't blocked if there are two SSNs in the message body, one SSN in an attachment, and two SSNs in another attachment in the same email message. + +This parameter works with the following conditions or exceptions only: + +- Content contains +- Attachment contains +- Attachment is not labeled +- File extension is + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAccessScope +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. +- NotInOrganization: The rule isn't applied to content that's accessible or delivered to a recipient outside the organization. +- None: The exception isn't used. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.AccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressMatchesPatterns +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentCharacterSetContainsWords +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. + +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`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentContainsSensitiveInformation +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"})})})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentFileTypeMatches +{{ Fill ExceptIfContentFileTypeMatches Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentIsShared +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. +- $false: Don't look for unlabeled attachments or documents. + +In Exchange, this condition is matched only if both the attachment and the message body aren't labeled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentContainsWords +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentCreatedBy +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentCreatedByMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentNameMatchesPatterns +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentMatchesPatterns +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"`. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFrom +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressMatchesPatterns +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromMemberOf +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"`. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromScope +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. +- NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.FromScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHasSenderOverride +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. +- $false: Don't look for messages where the sender took action to override a DLP policy. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHeaderContainsWords +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfMessageSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfMessageTypeMatches +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. +- AutomaticForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook on the web or Outlook). +- AutomaticReply: Out of office (OOF) messages configured by the user. +- Calendaring: Meeting requests and responses. +- Encrypted: S/MIME encrypted messages. +- PermissionControlled: Messages protected with Rights Management, Office 365 Message Encryption (OME), and sensitivity labels (with encryption). +- ReadReceipt: Read receipts. +- Signed: Digitally signed messages. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.MessageTypes +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectMatchesPatterns +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectOrBodyContainsWords +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectOrBodyMatchesPatterns +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. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfUnscannableDocumentExtensionIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfWithImportance +The ExceptIfWithImportance parameter specifies an exception for the rule that looks for messages with the specified importance level. Valid values are: + +- Low +- Normal +- High + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.WithImportance +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpiryDate +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -From +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressMatchesPatterns +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromMemberOf +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"`. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromScope +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. +- NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.FromScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GenerateAlert +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. +- SiteAdmin + +You can specify multiple values separated by commas. + +The email message that's generated by this action contains a link to detailed information in the Microsoft Purview compliance portal (the details aren't in the email message itself). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GenerateIncidentReport +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. +- SiteAdmin + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HasSenderOverride +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. +- $false: Don't look for messages where the sender took action to override a DLP policy. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HeaderContainsWords +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImmutableId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncidentReportContent +The IncidentReportContent parameter specifies the content to include in the report when you use the GenerateIncidentReport parameter. Valid values are: + +- All +- Default +- DetectionDetails +- Detections +- DocumentAuthor +- DocumentLastModifier +- MatchedItem +- OriginalContent +- RulesMatched +- Service +- Severity +- Title + +You can specify multiple values separated by commas. You can only use the value "All" by itself. If you use the value "Default", the report includes the following content: + +- DocumentAuthor +- MatchedItem +- RulesMatched +- Service +- Title + +Therefore, any additional values that you use with the value "Default" are ignored. + +```yaml +Type: ReportContentOption[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageIsNotLabeled +{{ Fill MessageIsNotLabeled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageTypeMatches +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. +- AutomaticForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook on the web or Outlook). +- AutomaticReply: Out of office (OOF) messages configured by the user. +- Calendaring: Meeting requests and responses. +- Encrypted: S/MIME encrypted messages. +- PermissionControlled: Messages protected with Rights Management, Office 365 Message Encryption (OME), and sensitivity labels (with encryption). +- ReadReceipt: Read receipts. +- Signed: Digitally signed messages. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MessageTypes +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MipRestrictAccess +{{ Fill MipRestrictAccess Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Moderate +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModifySubject +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: + +- Replace: Replaces all regular expression matches (the `Patterns=` value) in the subject with the `SubjectText=` value. +- Append: Removes all regular expression matches (the `Patterns=` value) in the subject and inserts the `SubjectText=` value at the end of the subject. +- Prepend: Removes all regular expression matches (the `Patterns=` value) and inserts the `SubjectText=` value at the beginning of the subject. + +The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10. + +```yaml +Type: PswsHashtable +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NonBifurcatingAccessScope +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. +- HasExternal: At least one recipient is outside the organization. +- None: The condition isn't used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.NonBifurcatingAccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyAllowOverride +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. +- WithAcknowledgement: Allows overrides with explicit user acknowledgement. (Exchange only) +- WithoutJustification: Allows overrides without justification. +- WithJustification: Allows overrides with justification. + +You can specify multiple values separated by commas. The values WithoutJustification and WithJustification are mutually exclusive. + +```yaml +Type: OverrideOption[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailCustomSenderDisplayName +{{ Fill NotifyEmailCustomSenderDisplayName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailCustomSubject +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailCustomText +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): + +- %%AppliedActions%%: The actions applied to the content. +- %%ContentURL%%: The URL of the document on the SharePoint site or OneDrive site. +- %%MatchedConditions%%: The conditions that were matched by the content. Use this token to inform people of possible issues with the content. +- %%BlockedMessageInfo%%: The details of the message that was blocked. Use this token to inform people of the details of the message that was blocked. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailExchangeIncludeAttachment +{{ Fill NotifyEmailExchangeIncludeAttachment Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailOnedriveRemediationActions +{{ Fill NotifyEmailOnedriveRemediationActions Description }} + +```yaml +Type: NotifyEmailRemediationActions +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEndpointUser +**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. + +{{ Fill NotifyEndpointUser Description }} + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: PswsHashtable +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyOverrideRequirements +{{ Fill NotifyOverrideRequirements Description }} + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyOverrideRequirements +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipCustomDialog +{{ Fill NotifyPolicyTipCustomDialog Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipCustomText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipCustomTextTranslations +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). + +To enter multiple values, use the following syntax: `"Value1","Value2",..."ValueN"`. For example: `"en:PolicyTipInEnglish","zh:警告：这个文件含有非法内容","th:คำแนะนำนโยบายในไทย"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipDisplayOption +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. +- Dialog: Displays policy tip at the top of the mail and as a popup dialog. (exchange only) + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyTipDisplayOption +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUser +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. +- LastModifier +- Owner +- SiteAdmin + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserType +The NotifyUserType parameter specifies the type of notification that's used for the rule. Valid values are: + +- NotSet +- Email +- PolicyTip +- Email,PolicyTip + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.NotifyUserType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnPremisesScannerDlpRestrictions +{{ Fill OnPremisesScannerDlpRestrictions Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrependSubject +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new 9th rule that you add to the policy are from 0 through 8. +- The default value for a new 9th rule that you add to the policy is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Quarantine +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: + +- $true: The message is delivered to the hosted quarantine. +- $false: The message is not quarantined. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientCountOver +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. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RedirectMessageTo +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveHeader +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. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveRMSTemplate +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. +- $False: The messages and attachments are not decrypted. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportSeverityLevel +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. +- Low: This is the default value. +- Medium +- High + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictAccess +{{ Fill RestrictAccess Description }} + +```yaml +Type: System.Collections.Hashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictBrowserAccess +{{ Fill RestrictBrowserAccess Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RuleErrorAction +The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: + +- Ignore +- RetryThenBlock +- Blank (the value $null): This is the default value. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderAddressLocation +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. +- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). +- HeaderOrEnvelope: Examine senders in the message header and the message envelope. + +Note that message envelope searching is available only for the following conditions and exceptions: + +- From and ExceptIfFrom +- FromAddressContainsWords and ExceptIfFromAddressContainsWords +- FromAddressMatchesPatterns and ExceptIfFromAddressMatchesPatterns +- FromMemberOf and ExceptIfFromMemberOf +- SenderDomainIs and ExceptIfSenderDomainIs + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicySenderAddressLocation +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SetHeader +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. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharedByIRMUserRisk +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) +- 797C4446-5C73-484F-8E58-0CCA08D6DF6C (Moderate Risk Level) +- 75A4318B-94A2-4323-BA42-2CA6DB29AAFE (Minor Risk Level) + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StopPolicyProcessing +The StopPolicyProcessing parameter specifies an action that stops processing more DLP policy rules. Valid values are: + +- $true: Stop processing more rules. +- $false: Continue processing more rules after this one. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectMatchesPatterns +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectOrBodyContainsWords +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectOrBodyMatchesPatterns +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. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThirdPartyAppDlpRestrictions +{{ Fill ThirdPartyAppDlpRestrictions Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TriggerPowerAutomateFlow +{{ Fill TriggerPowerAutomateFlow Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnscannableDocumentExtensionIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidateRule +{{ Fill ValidateRule Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WithImportance +The WithImportance parameter specifies a condition for the rule that looks for messages with the specified importance level. Valid values are: + +- Low +- Normal +- High + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.WithImportance +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DlpEdmSchema.md b/exchange/exchange-ps/exchange/New-DlpEdmSchema.md new file mode 100644 index 0000000000..27c440830a --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DlpEdmSchema.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DlpEdmSchema + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DlpEdmSchema cmdlet to create exact data match (EDM)-based classification schemas in the Microsoft Purview compliance portal. Such schemas can be used with data loss prevention (DLP) policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DlpEdmSchema [-FileData] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For an explanation and example of the EDM schema, see [Learn about exact data match based sensitive information types](https://learn.microsoft.com/purview/sit-learn-about-exact-data-match-based-sits). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DlpEdmSchema -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\edm.xml')) -Confirm:$true +``` + +This example creates a new DLP EDM schema using the file named edm.xml in the folder C:\\My Documents. + +## PARAMETERS + +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DlpFingerprint.md b/exchange/exchange-ps/exchange/New-DlpFingerprint.md new file mode 100644 index 0000000000..cbd457cd29 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DlpFingerprint.md @@ -0,0 +1,160 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DlpFingerprint + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DlpFingerprint cmdlet to create document fingerprints that are used with data loss prevention (DLP) sensitive information types in the Microsoft Purview compliance portal. Because the results of New-DlpFingerprint aren't stored outside of the sensitive information type, you always run New-DlpFingerprint and New-DlpSensitiveInformationType or Set-DlpSensitiveInformationType in the same PowerShell session. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DlpFingerprint [[-FileData] ] -Description + [-IsExact ] + [-Confirm] + [-ThresholdConfig ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$Patent_Template = [System.IO.File]::ReadAllBytes('C:\My Documents\Contoso Patent Template.docx)' + +$Patent_Fingerprint = New-DlpFingerprint -FileData $Patent_Template -Description "Contoso Patent Template" +``` + +This example creates a new document fingerprint based on the file C:\\My Documents\\Contoso Patent Template.docx. You store the new fingerprint as a variable so you can use it with the New-DlpSensitiveInformationType cmdlet in the same PowerShell session. + +## PARAMETERS + +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter specifies a description for the document fingerprint. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsExact +{{ Fill IsExact Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThresholdConfig +{{ Fill ThresholdConfig Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md new file mode 100644 index 0000000000..10ac021e60 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md @@ -0,0 +1,189 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DlpKeywordDictionary + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DlpKeywordDictionary cmdlet to create data loss prevention (DLP) keyword dictionaries in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DlpKeywordDictionary -Name + [-Confirm] + [-Description ] + [-DoNotPersistKeywords] + [-FileData ] + [-Organization ] + [-WhatIf] + [] +``` + +## DESCRIPTION +After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary will appear in your list of sensitive information types, and you can use it in policies. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$Keywords = @("Aarskog's syndrome","Abandonment","Abasia","Abderhalden-Kaufmann-Lignac","Abdominalgia","Abduction contracture","Abetalipo proteinemia","Abiotrophy","Ablatio","ablation","Ablepharia","Abocclusion","Abolition","Aborter","Abortion","Abortus","Aboulomania","Abrami's disease","Abramo") + +$EncodedKeywords = $Keywords | ForEach-Object {[System.Text.Encoding]::Unicode.GetBytes($_+"`r`n")} + +New-DlpKeywordDictionary -Name "Diseases" -Description "Names of diseases and injuries from ICD-10-CM lexicon" -FileData $EncodedKeywords +``` + +This example creates a DLP keyword dictionary named Diseases by using the specified values. + +### Example 2 +```powershell +$Keywords = Get-Content "C:\My Documents\InappropriateTerms.txt" + +$EncodedKeywords = $Keywords | ForEach-Object {[System.Text.Encoding]::Unicode.GetBytes($_+"`r`n")} + +New-DlpKeywordDictionary -Name "Inappropriate Language" -Description "Unprofessional and inappropriate terminology" -FileData $EncodedKeywords +``` + +This example creates a DLP keyword dictionary named Inappropriate Language from the file C:\\My Documents\\InappropriateTerms.txt. The file contains one term on each line. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DoNotPersistKeywords +{{ Fill DoNotPersistKeywords Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileData +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +{{ Fill Organization Description }} + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpPolicy.md b/exchange/exchange-ps/exchange/New-DlpPolicy.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpPolicy.md rename to exchange/exchange-ps/exchange/New-DlpPolicy.md index f910fd46c1..705a5e5e46 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpPolicy.md +++ b/exchange/exchange-ps/exchange/New-DlpPolicy.md @@ -1,34 +1,43 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlppolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-DlpPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the New-DlpCompliancePolicy and New-DlpComplianceRule cmdlets instead. -Use the New-DlpPolicy cmdlet to create data loss prevention (DLP) policies in your Exchange organization. +This cmdlet is functional only in on-premises Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the New-DlpPolicy cmdlet to create data loss prevention (DLP) policies that are based on transport rules (mail flow rules) in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-DlpPolicy [[-Name] ] [-Confirm] [-Description ] [-DomainController ] - [-Mode ] [-Parameters ] [-State ] - [-Template ] [-TemplateData ] [-WhatIf] [] +New-DlpPolicy [[-Name] ] + [-Confirm] + [-Description ] + [-DomainController ] + [-Mode ] + [-Parameters ] + [-State ] + [-Template ] + [-TemplateData ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -40,16 +49,30 @@ New-DlpPolicy -Name "Contoso PII" -Template "U.S. Personally Identifiable Inform This example creates a new DLP policy named Contoso PII with the following values: - The DLP policy is enabled and set to audit only. - - The DLP policy is based on the existing "U.S. Personally Identifiable Information (PII) Data" DLP policy template. ## PARAMETERS +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -82,8 +105,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -103,9 +124,7 @@ Accept wildcard characters: False 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. - - AuditAndNotify: The actions specified by the DLP policy aren't enforced when a message matches the conditions specified by the policy, but the Policy Tip is displayed to the user in a supported email client. - - Enforce: The actions specified by the DLP policy are enforced when a message matches the conditions specified by the policy, and the Policy Tip is displayed to the user in a supported email client. By default, the value of this parameter is set to Audit when you create a new DLP policy. If the State parameter is set to Disabled, the value of the Mode parameter is irrelevant. @@ -123,26 +142,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Parameters 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. -Valid input for this parameter is in the format: @{\="\";\="\"...}. +This parameter uses the syntax: `@{Parameter1="Value1";Parameter2="Value2"...}`. ```yaml Type: Hashtable @@ -192,7 +195,7 @@ Accept wildcard characters: False ### -TemplateData 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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\" -ReadCount 0\)\). +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[] @@ -228,12 +231,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md new file mode 100644 index 0000000000..961c0d2e48 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md @@ -0,0 +1,222 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DlpSensitiveInformationType + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DlpSensitiveInformationType cmdlet to create sensitive information type rules that use document fingerprints. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DlpSensitiveInformationType [[-Name] ] + [-Fingerprints ] + [-Confirm] + [-Description ] + [-FileData ] + [-IsExact ] + [-Locale ] + [-ThresholdConfig ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$Employee_Template = [System.IO.File]::ReadAllBytes('C:\My Documents\Contoso Employee Template.docx') + +$Employee_Fingerprint = New-DlpFingerprint -FileData $Employee_Template -Description "Contoso Employee Template" + +$Customer_Template = [System.IO.File]::ReadAllBytes('D:\Data\Contoso Customer Template.docx') + +$Customer_Fingerprint = New-DlpFingerprint -FileData $Customer_Template -Description "Contoso Customer Template" + +New-DlpSensitiveInformationType -Name "Contoso Employee-Customer Confidential" -Fingerprints $Employee_Fingerprint[0],$Customer_Fingerprint[0] -Description "Message contains Contoso employee or customer information." +``` + +This example creates a new sensitive information type rule named "Contoso Employee-Customer Confidential" that uses the document fingerprints of the files C:\\My Documents\\Contoso Employee Template.docx and D:\\Data\\Contoso Customer Template.docx. + +## PARAMETERS + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Fingerprints +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileData +{{ Fill FileData Description }} + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsExact +{{ Fill IsExact Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locale +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). + +You can add additional language translations to the sensitive information type rule by using the Set-DlpSensitiveInformationType cmdlet. + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThresholdConfig +{{ Fill ThresholdConfig Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md new file mode 100644 index 0000000000..ff65bcc045 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-DlpSensitiveInformationTypeRulePackage + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-DlpSensitiveInformationTypeConfig cmdlet to import data loss prevention (DLP) sensitive information type rule packages in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-DlpSensitiveInformationTypeRulePackage [-FileData] + [-Confirm] + [-MigrationId ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-DlpSensitiveInformationTypeRulePackage -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\External Sensitive Info Type Rule Collection.xml')) +``` + +This example imports the sensitive information type rule package C:\\My Documents\\External Sensitive Info Type Rule Collection.xml. + +## PARAMETERS + +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrationId +{{ Fill MigrationId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Learn about exact data match based sensitive information types](https://learn.microsoft.com/purview/sit-learn-about-exact-data-match-based-sits) diff --git a/exchange/exchange-ps/exchange/users-and-groups/New-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md similarity index 85% rename from exchange/exchange-ps/exchange/users-and-groups/New-DynamicDistributionGroup.md rename to exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md index 2a5f41fde6..548bcc5965 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/New-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/new-dynamicdistributiongroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-DynamicDistributionGroup @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-DynamicDistributionGroup cmdlet to create dynamic distribution groups. A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -54,7 +53,8 @@ New-DynamicDistributionGroup [-Name] -IncludedRecipients ] [-RecipientContainer ] [-SendModerationNotifications ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### CustomFilter @@ -72,21 +72,20 @@ New-DynamicDistributionGroup [-Name] -RecipientFilter [-PrimarySmtpAddress ] [-RecipientContainer ] [-SendModerationNotifications ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - - The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - - The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPath filter. +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -99,7 +98,7 @@ This example creates a dynamic distribution group named Marketing Group that con ### Example 2 ```powershell -New-DynamicDistributionGroup -Name "Washington Management Team" -RecipientFilter "(RecipientType -eq 'UserMailbox') -and (Title -like 'Director*' -or Title -like 'Manager*') -and (StateOrProvince -eq 'WA')" -RecipientContainer "North America" +New-DynamicDistributionGroup -Name "Washington Management Team" -RecipientFilter "(RecipientTypeDetails -eq 'UserMailbox') -and (Title -like 'Director*' -or Title -like 'Manager*') -and (StateOrProvince -eq 'WA')" -RecipientContainer "North America" ``` This example creates a dynamic distribution group named Washington Management Team that contains all users in the organizational unit named North America from Washington State whose titles start with "Director" or "Manager". @@ -115,7 +114,7 @@ This value is also used for the DisplayName property if you don't use the Displa Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -128,26 +127,21 @@ Accept wildcard characters: False 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. - - MailboxUsers - - MailContacts - - MailGroups - - MailUsers - - Resources: This value indicates room or equipment mailboxes. You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. -You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: WellKnownRecipientType Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -157,29 +151,26 @@ Accept wildcard characters: False ``` ### -RecipientFilter -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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). - In cloud-based environments, you can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. - - In on-premises Exchange, wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter in combination with the IncludedRecipients parameter or any Conditional parameters (which are used to create precanned filters). +The maximum length for the RecipientFilter property is 2048 characters, including internal syntax. + ```yaml Type: String Parameter Sets: CustomFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -189,16 +180,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -209,7 +204,7 @@ The Alias parameter never generates or updates the primary email address of a ma Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -224,23 +219,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -261,13 +247,13 @@ The ConditionalCompany parameter specifies a precanned filter that's based on th 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -281,13 +267,13 @@ The ConditionalCustomAttribute1 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -301,13 +287,13 @@ The ConditionalCustomAttribute10 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -321,13 +307,13 @@ The ConditionalCustomAttribute11 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -341,13 +327,13 @@ The ConditionalCustomAttribute12 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -361,13 +347,13 @@ The ConditionalCustomAttribute13 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -381,13 +367,13 @@ The ConditionalCustomAttribute14 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -401,13 +387,13 @@ The ConditionalCustomAttribute15 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -421,13 +407,13 @@ The ConditionalCustomAttribute2 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -441,13 +427,13 @@ The ConditionalCustomAttribute3 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -461,13 +447,13 @@ The ConditionalCustomAttribute4 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -481,13 +467,13 @@ The ConditionalCustomAttribute5 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -501,13 +487,13 @@ The ConditionalCustomAttribute6 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -521,13 +507,13 @@ The ConditionalCustomAttribute7 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -541,13 +527,13 @@ The ConditionalCustomAttribute8 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -561,13 +547,13 @@ The ConditionalCustomAttribute9 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -581,13 +567,13 @@ The ConditionalDepartment parameter specifies a precanned filter that's based on 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -601,13 +587,13 @@ The ConditionalStateOrProvince parameter specifies a precanned filter that's bas 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty Parameter Sets: PrecannedFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -619,15 +605,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -645,7 +630,7 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -663,7 +648,7 @@ If you don't use the DisplayName parameter, the value of the Name parameter is u Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -694,18 +679,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -713,7 +693,7 @@ You use this parameter to specify at least one moderator when you set the Modera Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -726,7 +706,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -735,7 +714,7 @@ You use the ModeratedBy parameter to specify the moderators. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -750,11 +729,8 @@ The OrganizationalUnit parameter specifies the organizational unit (OU) where th 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 - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is typically the Users container in the domain of the Exchange server that you're connected to (also known as the recipient scope). In on-premises Exchange, you can change the recipient scope for the current PowerShell session by using the Set-AdServerSettings cmdlet. @@ -767,7 +743,7 @@ If you don't use the RecipientContainer parameter, the location of the dynamic d Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -783,7 +759,7 @@ 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -796,11 +772,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is the OU where the object was created. @@ -813,7 +786,7 @@ Note that the RecipientContainer property can't be blank. The group is always li Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -826,9 +799,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -837,7 +808,7 @@ This parameter is only meaningful when moderation is enabled (the ModerationEnab Type: TransportModerationNotificationFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -853,7 +824,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -867,12 +838,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md new file mode 100644 index 0000000000..0f0e180485 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md @@ -0,0 +1,386 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-EOPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-EOPProtectionPolicyRule cmdlet to create rules for Exchange Online Protection (EOP) protections in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. + +**Note**: Unless you manually removed a rule using the Remove-EOPProtectionPolicyRule cmdlet, we don't recommend using this cmdlet to create rules. To create the rule, you need to specify the existing individual security policies that are associated with the preset security policy. We never recommend creating these required individual security policies manually. Turning on the preset security policy for the first time in the Microsoft Defender portal automatically creates the required individual security policies, but also creates the associated rules using this cmdlet. So, if the rules already exist, you don't need to use this cmdlet to create them. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-EOPProtectionPolicyRule [-Name] [-Priority ] -AntiPhishPolicy -HostedContentFilterPolicy -MalwareFilterPolicy + [-Comments ] + [-Confirm] + [-Enabled ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-EOPProtectionPolicyRule -Name "Standard Preset Security Policy" -AntiPhishPolicy "Standard Preset Security Policy1622650005393" -HostedContentFilterPolicy "Standard Preset Security Policy1622650006407" -MalwareFilterPolicy "Standard Preset Security Policy1622650007658" Priority 1 +``` + +This example creates the rule for the Standard preset security policy. No restrictions are placed on who the Defender for Office 365 protections apply to. If the rule already exists, the command will fail. + +## PARAMETERS + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AntiPhishPolicy +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: + +- Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650005393`. +- Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034844713`. + +You can find the anti-phishing policy that's used by the Standard or Strict preset security policies by running the following commands: `Get-AntiPhishPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Standard"` or `AntiPhishPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Strict"`. + +```yaml +Type: AntiPhishPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HostedContentFilterPolicy +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: + +- Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650006407`. +- Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034847393`. + +You can find the anti-spam policy that's used by the Standard or Strict preset security policies by running the following commands: `Get-HostedContentFilterPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Standard"` or `Get-HostedContentFilterPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Strict"`. + +```yaml +Type: HostedContentFilterPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MalwareFilterPolicy +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: + +- Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650007658`. +- Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034871908`. + +You can find the anti-malware policy that's used by the Standard or Strict preset security policies by running the following commands: `Get-MalwareFilterPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Standard"` or `Get-MalwareFilterPolicy | Where-Object -Property RecommendedPolicyType -eq -Value "Strict"`. + +```yaml +Type: MalwareFilterPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. +- $false: The rule is disabled. The State value of the rule is Disabled. + +After you create the rule, you turn on or turn off the preset security policy using one of the following commands: + +- Turn off: Disable-EOPProtectionPolicyRule. +- Turn on: Enable-EOPProtectionPolicyRule. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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. + +When you create the policy, you must use the default value. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-EcpVirtualDirectory.md b/exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access-servers/New-EcpVirtualDirectory.md rename to exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md index 6ac6fd7f75..d888a64122 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-ecpvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-EcpVirtualDirectory @@ -19,20 +18,29 @@ Use the New-EcpVirtualDirectory cmdlet to create Exchange Control Panel (ECP) vi The ECP web management interface was introduced in Exchange Server 2010. In Exchange Server 2013 and Exchange Server 2016, the EAC virtual directories and the corresponding management cmdlets still use ECP in the name. You can use these cmdlets to manage ECP virtual directories on Exchange 2010, Exchange 2013, and Exchange 2016 servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-EcpVirtualDirectory [-AppPoolId ] [-Confirm] [-DomainController ] - [-ExtendedProtectionFlags ] [-ExtendedProtectionSPNList ] - [-ExtendedProtectionTokenChecking ] [-ExternalUrl ] [-InternalUrl ] - [-Path ] [-Server ] [-WebSiteName ] [-WhatIf] - [-Role ] [] +New-EcpVirtualDirectory [-AppPoolId ] + [-Confirm] + [-DomainController ] + [-ExtendedProtectionFlags ] + [-ExtendedProtectionSPNList ] + [-ExtendedProtectionTokenChecking ] + [-ExternalUrl ] + [-InternalUrl ] + [-Path ] + [-Role ] + [-Server ] + [-WebSiteName ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -64,8 +72,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -101,13 +108,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -127,8 +130,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -147,14 +149,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -221,15 +219,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Role +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. +- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. + +Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. + +```yaml +Type: VirtualDirectoryRole +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Server 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN You can't create an ECP virtual directory remotely. You can only create an ECP virtual directory on the local computer. @@ -279,39 +295,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Role -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. - -- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. - -Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. - -```yaml -Type: VirtualDirectoryRole -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-EdgeSubscription.md b/exchange/exchange-ps/exchange/New-EdgeSubscription.md similarity index 82% rename from exchange/exchange-ps/exchange/mail-flow/New-EdgeSubscription.md rename to exchange/exchange-ps/exchange/New-EdgeSubscription.md index 8d8ea1c04a..e7c67b1d70 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-EdgeSubscription.md +++ b/exchange/exchange-ps/exchange/New-EdgeSubscription.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-edgesubscription +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-EdgeSubscription @@ -17,34 +16,43 @@ This cmdlet is available only in on-premises Exchange. Use the New-EdgeSubscription cmdlet to export an Edge Subscription file from an Edge Transport server and to import the Edge Subscription file to a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-EdgeSubscription [-AccountExpiryDuration ] [-Confirm] - [-CreateInboundSendConnector ] [-CreateInternetSendConnector ] - [-DomainController ] [-FileData ] [-FileName ] [-Force] [-Site ] - [-WhatIf] [] +New-EdgeSubscription [-AccountExpiryDuration ] + [-Confirm] + [-CreateInboundSendConnector ] + [-CreateInternetSendConnector ] + [-DomainController ] + [-FileData ] + [-FileName ] + [-Force] + [-Site ] + [-WhatIf] + [] ``` ## DESCRIPTION -The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file that will be imported on a Mailbox server in the Active Directory site to which you want to subscribe this Edge Transport server.. +The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file that will be imported on a Mailbox server in the Active Directory site to which you want to subscribe this Edge Transport server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-EdgeSubscription -FileName "c:\EdgeServerSubscription.xml" +New-EdgeSubscription -FileName "C:\Data\EdgeSubscription.xml" ``` This example creates the Edge Subscription file. It should be run on your Edge Transport server. ### Example 2 ```powershell -[byte[]]$Temp = Get-Content -Path "C:\EdgeServerSubscription.xml" -Encoding Byte -ReadCount 0; New-EdgeSubscription -FileData $Temp -Site "Default-First-Site-Name" +$Temp = [System.IO.File]::ReadAllBytes('C:\Data\EdgeSubscription.xml') + +New-EdgeSubscription -FileData $Temp -Site "Default-First-Site-Name" ``` This example imports the Edge Subscription file generated in Example 1 to the Active Directory site Default-First-Site-Name. Importing the Edge Subscription file completes the Edge Subscription process. You must run this command on the Mailbox server. @@ -53,7 +61,7 @@ The first command reads the data from the Edge Subscription file and stores it i ### Example 3 ```powershell -New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeServerSubscription.xml" -Encoding Byte -ReadCount 0)) -Site "Default-First-Site-Name" +New-EdgeSubscription -FileData ([System.IO.File]::ReadAllBytes('C:\Data\EdgeSubscription.xml')) -Site "Default-First-Site-Name" ``` This example also imports the Edge Subscription file generated in Example 1 to the Active Directory site Default-First-Site-Name; however, the end result is accomplished using one command. You must run this command on the Mailbox server. @@ -83,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -153,9 +160,9 @@ Accept wildcard characters: False ### -FileData 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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\" -ReadCount 0\)\). +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`). -You can only use this parameter when you're running this command on a Mailbox server. +You can only use this parameter when you're running the command on a Mailbox server. ```yaml Type: Byte[] @@ -189,9 +196,12 @@ Accept wildcard characters: False ``` ### -Force -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. +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: -This switch is useful when you use a script with the Edge Subscription command because it bypasses confirmation. Another scenario in which this switch is useful is when you have to subscribe an Edge Transport server again and you want to overwrite the existing configuration information. +- Bypassing confirmation when you script the Edge Subscription command. +- Recreating an Edge Transport server subscription and overwriting the existing configuration information. ```yaml Type: SwitchParameter @@ -243,12 +253,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-EdgeSyncServiceConfig.md b/exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/mail-flow/New-EdgeSyncServiceConfig.md rename to exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md index f4339f28a2..f961f43a6f 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-edgesyncserviceconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-EdgeSyncServiceConfig @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-EdgeSyncServiceConfig cmdlet to create edge synchronization service settings that control the general synchronization behavior shared by all EdgeSync services. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -38,11 +37,12 @@ New-EdgeSyncServiceConfig [-ConfigurationSyncInterval ] [-OptionDuration ] [-RecipientSyncInterval ] [-Site ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,11 +54,8 @@ New-EdgeSyncServiceConfig -LogEnabled $true -LogPath "\\Server01\EdgeSyncLog" -L This example creates EdgeSync service settings with the following configuration: - EdgeSync logging is enabled. - - The log files are stored in the EdgeSyncLog share on Server01. - - The maximum individual log file size is 5 megabytes (MB). - - The log files are kept for 3 days. ## PARAMETERS @@ -84,8 +81,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -209,11 +205,8 @@ Accept wildcard characters: False The LogLevel parameter specifies the EdgeSync logging level. Valid values are: - None (This is the default value) - - Low - - Medium - - High ```yaml @@ -253,13 +246,9 @@ The LogMaxDirectorySize parameter specifies the maximum amount of disk space the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -285,13 +274,9 @@ The LogMaxFileSize parameter specifies the maximum log file size for the EdgeSyn When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -400,12 +385,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/New-EmailAddressPolicy.md similarity index 83% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/New-EmailAddressPolicy.md rename to exchange/exchange-ps/exchange/New-EmailAddressPolicy.md index a721a76fe2..966babe33d 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-EmailAddressPolicy.md +++ b/exchange/exchange-ps/exchange/New-EmailAddressPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/new-emailaddresspolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-EmailAddressPolicy @@ -15,9 +14,9 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the New-EmailAddressPolicy cmdlet to create email address policies. In Exchange Online, email address policies are only available for Office 365 groups. +Use the New-EmailAddressPolicy cmdlet to create email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -47,7 +46,8 @@ New-EmailAddressPolicy [-Name] -EnabledEmailAddressTemplates ] [-Priority ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AllTemplatesWithCustomFilter @@ -58,7 +58,8 @@ New-EmailAddressPolicy [-Name] -EnabledEmailAddressTemplates ] [-Priority ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### SMTPTemplateWithPrecannedFilter @@ -86,7 +87,8 @@ New-EmailAddressPolicy [-Name] -EnabledPrimarySMTPAddressTemplate ] [-Priority ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### SMTPTemplateWithCustomFilter @@ -96,12 +98,15 @@ New-EmailAddressPolicy [-Name] -EnabledPrimarySMTPAddressTemplate ] [-Priority ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AllTemplatesForUnifiedGroupRecipientsFilter ``` -New-EmailAddressPolicy [-Name] -EnabledEmailAddressTemplates [-IncludeUnifiedGroupRecipients] [-ManagedByFilter ] +New-EmailAddressPolicy [-Name] -EnabledEmailAddressTemplates + [-IncludeUnifiedGroupRecipients] + [-ManagedByFilter ] [-Confirm] [-DisabledEmailAddressTemplates ] [-DomainController ] @@ -113,12 +118,15 @@ New-EmailAddressPolicy [-Name] -EnabledEmailAddressTemplates -EnabledPrimarySMTPAddressTemplate [-IncludeUnifiedGroupRecipients] [-ManagedByFilter ] +New-EmailAddressPolicy [-Name] -EnabledPrimarySMTPAddressTemplate + [-IncludeUnifiedGroupRecipients] + [-ManagedByFilter ] [-Confirm] [-DomainController ] [-Priority ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -127,14 +135,12 @@ After you use the New-EmailAddressPolicy cmdlet to create an email address polic The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - - The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - - The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPath filter. +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -146,30 +152,22 @@ New-EmailAddressPolicy -Name "Southeast Offices" -IncludedRecipients MailboxUser This example creates an email address policy in an on-premises Exchange organization that uses a precanned recipient filter: - Name: Southeast Offices - - Precanned recipient filter: All users with mailboxes where the State or province value is GA, AL, or LA (Georgia, Alabama, or Louisiana). - -- Primary SMTP email address: \.\@contoso.com - -- Additional proxy email addresses: \.\@contoso.net - +- Primary SMTP email address: `.@contoso.com` +- Additional proxy email addresses: `.@contoso.net` - Priority:N+1, where N is the number of manually created email address policies that already exist (we didn't use the Priority parameter, and the default value is N+1). ### Example 2 ```powershell -New-EmailAddressPolicy -Name "Northwest Executives" -RecipientFilter "(RecipientType -eq 'UserMailbox') -and (Title -like '*Director*' -or Title -like '*Manager*') -and (StateOrProvince -eq 'WA' -or StateOrProvince -eq 'OR' -or StateOrProvince -eq 'ID')" -EnabledEmailAddressTemplates "SMTP:%2g%s@contoso.com" -Priority 2 +New-EmailAddressPolicy -Name "Northwest Executives" -RecipientFilter "(RecipientTypeDetails -eq 'UserMailbox') -and (Title -like '*Director*' -or Title -like '*Manager*') -and (StateOrProvince -eq 'WA' -or StateOrProvince -eq 'OR' -or StateOrProvince -eq 'ID')" -EnabledEmailAddressTemplates "SMTP:%2g%s@contoso.com" -Priority 2 ``` This example creates an email address policy in an on-premises Exchange organization that uses a custom recipient filter: - Name: Northwest Executives - - Custom recipient filter: All users with mailboxes where the Title value contains Director or Manager, and the State or province value is WA, OR, or ID (Washington, Oregon, or Idaho). - -- Primary SMTP email address: \\@contoso.com - +- Primary SMTP email address: `@contoso.com` - Additional proxy email addresses: None - - Priority: 2 ## PARAMETERS @@ -193,19 +191,18 @@ Accept wildcard characters: False ### -EnabledEmailAddressTemplates 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 \:\: - -- \: A valid email address type as described in "Address types" section in [Email address policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, SMTP for the primary email address, and smtp for proxy addresses. +Valid syntax for this parameter is `Type:AddressFormat`: -- \: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: \@contoso.com requires the value %m@contoso.com, and \.\@contoso.com requires the value %g.%s@contoso.com. +- Type: A valid email address type as described in "Address types" 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, SMTP for the primary email address, and smtp for proxy addresses. +- AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" 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`. -This parameter requires at least one template with the \ value SMTP (to define the primary SMTP email address). After that, if you don't include a \ prefix for a template, the value smtp (an SMTP proxy address) is assumed. +This parameter requires at least one template with the Type value SMTP (to define the primary SMTP email address). After that, if you don't include a Type prefix for a template, the value smtp (an SMTP proxy address) is assumed. -You can specify multiple email address templates separated by commas: "SMTP:\","[\]:\","[\]:\",..."[\]:\". +You can specify multiple email address templates separated by commas: `"SMTP:PrimarySMTPEmailAddress","[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`. You can't use this parameter with the EnabledPrimarySMTPAddressTemplate parameter. -In Office 365, if you use this parameter with the IncludeUnifiedGroupRecipients, you can't use variables in the email address template. +In Exchange Online PowerShell, you can't use variables in the email address template. ```yaml Type: ProxyAddressTemplateCollection @@ -221,13 +218,13 @@ Accept wildcard characters: False ``` ### -EnabledPrimarySMTPAddressTemplate -The EnabledPrimarySMTPAddressTemplate parameter specifies the 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. +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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: \@contoso.com requires the value %m@contoso.com, and \.\@contoso.com requires the value %g.%s@contoso.com. +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`. You can't use this parameter with the EnabledEmailAddressTemplates parameter. -In Office 365, if you use this parameter with the IncludeUnifiedGroupRecipients, you can't use variables in the email address template. +In Exchange Online PowerShell, you can't use variables in the email address template. ```yaml Type: String @@ -248,20 +245,15 @@ 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: - AllRecipients: This value can be used only by itself. - - MailboxUsers - - MailContacts - - MailGroups - - MailUsers - - Resources: This value indicates room or equipment mailboxes. You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. -You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: WellKnownRecipientType @@ -279,7 +271,9 @@ Accept wildcard characters: False ### -IncludeUnifiedGroupRecipients This parameter is available only in the cloud-based service. -The IncludeUnifiedGroupRecipients switch specifies that the email address policy applies to Office 365 groups. You don't need to specify a value with this switch. +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. + +In Exchange Online PowerShell, you always need to use this switch, because email address policies in Exchange Online are only applied to Microsoft 365 groups. ```yaml Type: SwitchParameter @@ -297,21 +291,16 @@ Accept wildcard characters: False ### -RecipientFilter 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'"`. - -- 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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). - In cloud-based environments, you can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. - - In on-premises Exchange, wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter in combination with the IncludedRecipients parameter or any Conditional parameters (which are used to create precanned filters). @@ -335,7 +324,7 @@ The ConditionalCompany parameter specifies a precanned filter that's based on th 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -357,7 +346,7 @@ The ConditionalCustomAttribute1 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -379,7 +368,7 @@ The ConditionalCustomAttribute10 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -401,7 +390,7 @@ The ConditionalCustomAttribute11 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -423,7 +412,7 @@ The ConditionalCustomAttribute12 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -445,7 +434,7 @@ The ConditionalCustomAttribute13 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -467,7 +456,7 @@ The ConditionalCustomAttribute14 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -489,7 +478,7 @@ The ConditionalCustomAttribute15 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -511,7 +500,7 @@ The ConditionalCustomAttribute2 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -533,7 +522,7 @@ The ConditionalCustomAttribute3 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -555,7 +544,7 @@ The ConditionalCustomAttribute4 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -577,7 +566,7 @@ The ConditionalCustomAttribute5 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -599,7 +588,7 @@ The ConditionalCustomAttribute6 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -621,7 +610,7 @@ The ConditionalCustomAttribute7 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -643,7 +632,7 @@ The ConditionalCustomAttribute8 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -665,7 +654,7 @@ The ConditionalCustomAttribute9 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -687,7 +676,7 @@ The ConditionalDepartment parameter specifies a precanned filter that's based on 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -709,7 +698,7 @@ The ConditionalStateOrProvince parameter specifies a precanned filter that's bas 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -727,8 +716,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -749,13 +737,12 @@ 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. -Valid syntax for this parameter is \:\: - -- \: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address. +Valid syntax for this parameter is `Type:AddressFormat`: -- \: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: \@contoso.com requires the value %m@contoso.com, and \.\@contoso.com requires the value %g.%s@contoso.com. +- Type: A valid email address type as described in the "Address types" 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, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address. +- AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" 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`. -You can specify multiple disabled email address templates separated by commas: "[\]:\","[\]:\",..."[\]:\". +You can specify multiple disabled email address templates separated by commas: `"[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`. ```yaml Type: ProxyAddressTemplateCollection @@ -791,25 +778,21 @@ Accept wildcard characters: False ### -ManagedByFilter This parameter is available only in the cloud-based service. -The ManagedByFilter parameter specifies the email address policies to apply to Office 365 groups based on the properties of the users who create the Office 365 groups. - -This parameter is an OPath filter that's based on the value of any available recipient property (for example, `"Department -eq 'Sales'"`). 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. +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. -- Property is a filterable property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +This parameter is an OPATH filter that's based on the value of any available recipient property (for example, `"Department -eq 'Sales'"`). 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. +- Property is a filterable property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). - You can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. -For more information, see [Choose the domain to use when creating Office 365 Groups](https://go.microsoft.com/fwlink/p/?linkid=838413). +For more information, see [Choose the domain to use when creating Microsoft 365 Groups](https://learn.microsoft.com/microsoft-365/admin/create-groups/choose-domain-to-create-groups). -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). -You need to use this parameter with the IncludeUnifiedGroupRecipients switch. +You can only use this parameter in Exchange Online PowerShell with the IncludeUnifiedGroupRecipients switch. ```yaml Type: String @@ -829,7 +812,7 @@ The Priority parameter specifies the order that the email address policies are e 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. -Note: The first email address policy that identifies a recipient configures the recipient's email addresses. All other policies are ignored, even if the first policy is unapplied and can't configure the recipient's email addresses. +**Note**: The first email address policy that identifies a recipient configures the recipient's email addresses. All other policies are ignored, even if the first policy is unapplied and can't configure the recipient's email addresses. ```yaml Type: EmailAddressPolicyPriority @@ -850,11 +833,8 @@ 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: - Name - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is the OU where the object was created. @@ -893,12 +873,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-ExchangeCertificate.md b/exchange/exchange-ps/exchange/New-ExchangeCertificate.md new file mode 100644 index 0000000000..5d957d9ce7 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ExchangeCertificate.md @@ -0,0 +1,619 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ExchangeCertificate + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the New-ExchangeCertificate cmdlet to create and renew self-signed certificates, and to create certificate requests (also known as certificate signing requests or CSRs) for new certificates and certificate renewals from a certification authority (CA). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Request +``` +New-ExchangeCertificate [-BinaryEncoded] [-GenerateRequest] [-RequestFile ] + [-Confirm] + [-DomainController ] + [-DomainName ] + [-Force] + [-FriendlyName ] + [-IncludeAcceptedDomains] + [-IncludeAutoDiscover] + [-IncludeServerFQDN] + [-IncludeServerNetBIOSName] + [-Instance ] + [-KeySize ] + [-PrivateKeyExportable ] + [-Server ] + [-SubjectKeyIdentifier ] + [-SubjectName ] + [-WhatIf] + [] +``` + +### Certificate +``` +New-ExchangeCertificate [-Services ] + [-Confirm] + [-DomainController ] + [-DomainName ] + [-Force] + [-FriendlyName ] + [-IncludeAcceptedDomains] + [-IncludeAutoDiscover] + [-IncludeServerFQDN] + [-IncludeServerNetBIOSName] + [-Instance ] + [-KeySize ] + [-PrivateKeyExportable ] + [-Server ] + [-SubjectKeyIdentifier ] + [-SubjectName ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Exchange uses certificates for SSL and TLS encryption. + +There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://learn.microsoft.com/Exchange/architecture/client-access/certificates). + +Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://azure.microsoft.com/blog/protecting-against-the-ssl-3-0-vulnerability/). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ExchangeCertificate +``` + +This example creates a self-signed certificate with the following settings: + +- The Subject value is `CN=` (for example, CN=Mailbox01). +- The Domains (subject alternative names) value is `,` (for example, `Mailbox01,Mailbox01.contoso.com`). +- The Services value is `IMAP,POP,SMTP`. +- The Services value SMTP grants the Network Services local security group read access to the certificate's private key. +- The Services value SMTP and the Subject value that contains the server name publishes the certificate to Active Directory so that Exchange direct trust can validate the authenticity of the server for mutual TLS. + +If you don't want this certificate to replace the existing self-signed certificate that was created during Exchange setup, be sure to select "No" in the prompt that asks you overwrite the existing default SMTP certificate. + +### Example 2 +```powershell +Get-ExchangeCertificate -Thumbprint c4248cd7065c87cb942d60f7293feb7d533a4afc | New-ExchangeCertificate -PrivateKeyExportable $true +``` + +This example shows how to renew a certificate with a specific thumbprint value. You can find the thumbprint value in one of two ways: + +- Select the certificate in the Exchange admin center and then select Edit to view properties of the certificate. The thumbprint value is shown in the Exchange Certificate window. +- Run the Get-ExchangeCertificate cmdlet to return a list of all certificates installed on the server with their thumbprint values. + +Setting the PrivateKeyExportable parameter to the value $true allows the renewed certificate to be exported from the server (and imported on other servers). + +### Example 3 +```powershell +New-ExchangeCertificate -GenerateRequest -SubjectName "c=US,o=Woodgrove Bank,cn=mail.woodgrovebank.com" -DomainName autodiscover.woodgrovebank.com,mail.fabrikam.com,autodiscover.fabrikam.com -RequestFile "C:\Cert Requests\woodgrovebank.req" +``` + +In **Exchange 2013**, this example creates a new certificate request for a certification authority that has the following settings: + +- The request is Base64 encoded. +- The Subject value is `c=US,o=Woodgrove Bank,cn=mail.woodgrovebank.com`. +- The Domains (subject alternative names) value contains the additional valuesautodiscover.woodgrovebank.com, mail.fabrikam.com, and autodiscover.fabrikam.com. +- The command output is displayed onscreen and is also written to the text file C:\\Cert Requests\\woodgrovebank.req. + +**Note**: The RequestFile parameter is available only in Exchange 2013. To create a new certificate request file in Exchange 2016 or Exchange 2019, see Example 4 and Example 5. + +After you create the certificate request, you send the output to the CA. After you receive the certificate from the CA, you install the certificate by using the Import-ExchangeCertificate cmdlet, and you assign the certificate to Exchange services by using the Enable-ExchangeCertificate cmdlet. + +If the CA requires the certificate request in a file that's encoded by DER, use the BinaryEncoding switch and save the file with the .pfx extension. + +### Example 4 +```powershell +$txtrequest = New-ExchangeCertificate -GenerateRequest -SubjectName "c=US,o=Woodgrove Bank,cn=mail.woodgrovebank.com" -DomainName autodiscover.woodgrovebank.com,mail.fabrikam.com,autodiscover.fabrikam.com + +[System.IO.File]::WriteAllBytes('\\FileServer01\Data\woodgrovebank.req', [System.Text.Encoding]::Unicode.GetBytes($txtrequest)) +``` + +This example creates a new Base64 encoded certificate request for a certification authority using the same certificate settings as Example 3. + +This method is required in Exchange 2016 and Exchange 2019 because the RequestFile parameter is not available. + +### Example 5 +```PowerShell +$binrequest = New-ExchangeCertificate -GenerateRequest -BinaryEncoded -SubjectName "c=US,o=Woodgrove Bank,cn=mail.woodgrovebank.com" -DomainName autodiscover.woodgrovebank.com,mail.fabrikam.com,autodiscover.fabrikam.com + +[System.IO.File]::WriteAllBytes('\\FileServer01\Data\woodgrovebank.pfx', $binrequest.FileData) +``` + +This example creates a new DER encoded (binary) certificate request for a certification authority using the same certificate settings as Example 4. + +This method is required in Exchange 2016 and Exchange 2019 because the RequestFile parameter is not available. + +### Example 6 +```powershell +Get-ExchangeCertificate -Thumbprint 8A141F7F2BBA8041973399723BD2598D2ED2D831 | New-ExchangeCertificate -GenerateRequest -RequestFile "C:\Cert Requests\fabrikam_renewal.req" +``` + +In **Exchange 2013**, this example creates a request to renew an existing certificate that was issued by a certification authority. The certificate request has the following settings: + +- The thumbprint value of the existing certificate is 8A141F7F2BBA8041973399723BD2598D2ED2D831. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. +- The request is Base64 encoded. +- The output is displayed onscreen and is also written to the text file C:\\Cert Requests\\fabrikam\_renewal.req. + +**Note**: The RequestFile parameter is available only in Exchange 2013. To create a certificate renewal request for a certification authority in Exchange 2016 or Exchange 2019, see Example 7 and Example 8. + +After you create the certificate renewal request, you send the output to the CA. After you receive the renewed certificate from the CA, you install the certificate by using the Import-ExchangeCertificate cmdlet. + +### Example 7 +```powershell +$txtrequest = Get-ExchangeCertificate -Thumbprint 8A141F7F2BBA8041973399723BD2598D2ED2D831 | New-ExchangeCertificate -GenerateRequest + +[System.IO.File]::WriteAllBytes('C:\Cert Requests\fabrikam_renewal.req', [System.Text.Encoding]::Unicode.GetBytes($txtrequest)) +``` + +This example create a Base64 encoded certificate renewal request file for a certification authority using the same certificate settings as Example 6. + +This method is required in Exchange 2016 and Exchange 2019 because the RequestFile parameter is not available. + +### Example 8 +```powershell +$binrequest = Get-ExchangeCertificate -Thumbprint 8A141F7F2BBA8041973399723BD2598D2ED2D831 | New-ExchangeCertificate -GenerateRequest + +[System.IO.File]::WriteAllBytes('C:\Cert Requests\fabrikam_renewal.pfx', $binrequest.FileData) +``` + +This example creates a new DER encoded (binary) certificate renewal request file for a certification authority using the same certificate settings as Example 7. + +## PARAMETERS + +### -BinaryEncoded +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. + +This switch is available only when you use the GenerateRequest switch. + +For Base64 encoded requests, you send the contents of the file to the certificate authority. For requests that are encoded by DER, you send the certificate file itself. + +```yaml +Type: SwitchParameter +Parameter Sets: Request +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainName +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. + +Typically, values include server names (for example, Mailbox01) and FQDNs (for example, mail.contoso.com). You can specify multiple values separated by commas. Valuescan contain the characters a through z, 0 through 9, and the hyphen (-). The length of the domain name can't exceed 255 characters. + +The default value includes the name and FQDN of the Exchange server when both of the following conditions are true: + +- You don't use this parameter. +- You don't use any of these parameters: IncludeAcceptedDomains, IncludeAutoDiscover, IncludeServerFQDN, or IncludeServerNetBIOSName. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FriendlyName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GenerateRequest +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. + +After you install the certificate from the certification authority by using the Import-ExchangeCertificate cmdlet, you use the Enable-ExchangeCertficate cmdlet to enable the certificate for Exchange services. + +If you don't use this switch, the command creates a new self-signed certificate on the Exchange server. + +```yaml +Type: SwitchParameter +Parameter Sets: Request +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAcceptedDomains +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: + +- If you've already included an accepted domain in the DomainName parameter, the value isn't duplicated in the Subject Alternative Name field. +- For new self-signed certificates, if you don't use the Services parameter, the certificate is only assigned to SMTP. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAutoDiscover +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: + +- autodiscover.woodgrovebank.com +- autodiscover.woodgrovebank.co.uk + +When you use this switch: + +- If you've already included the value `autodiscover.` in the DomainName parameter, the value isn't duplicated in the Subject Alternative Name field. +- For new self-signed certificates, if you don't use the Services parameter, the certificate is only assigned to SMTP. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeServerFQDN +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeServerNetBIOSName +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +This parameter 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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -KeySize +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 +- 2048 (This is the default value) +- 4096 + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivateKeyExportable +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. +- $false: The private key isn't exportable, so you can't export the certificate. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequestFile +**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. + +The RequestFile parameter specifies the name and path of the certificate request file. The file contains the same information that's displayed on-screen when you generate a Base64 encoded certificate request (you don't use the BinaryEncoded switch). + +You can use a local path if the certificate or certificate request is located on the same Exchange server where you're running the command. Otherwise, use a UNC path (`\\Server\Share`). If the value contains spaces, enclose the value in quotation marks ("). + +You can use this parameter only when you use the GenerateRequest switch. + +```yaml +Type: String +Parameter Sets: Request +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Server +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +If you don't use this parameter, the command is run on the local server. + +```yaml +Type: ServerIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Services +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. +- Federation +- IIS +- IMAP: Don't enable a wildcard certificate for the IMAP4 service. Instead, use the Set-ImapSettings cmdlet to configure the FQDN that clients use to connect to the IMAP4 service. +- POP: Don't enable a wildcard certificate for the POP3 service. Instead, use the Set-PopSettings cmdlet to configure the FQDN that clients use to connect to the POP3 service. +- SMTP: When you enable a certificate for SMTP, you're prompted to replace the default Exchange self-signed certificate that's used to encrypt SMTP traffic between internal Exchange. If you want to replace the default certificate without the confirmation prompt, use the Force switch. +- UM: This value requires that the UMStartupMode parameter on the Set-UMService cmdlet is set to TLS or Dual. If the UMStartupMode parameter is set to the default value of TCP, you can't enable the certificate for the UM service. +- UMCallRouter: This value requires that the UMStartupMode parameter on the Set-UMCallRouterService cmdlet is set to TLS or Dual. If the UMStartupMode parameter is set to the default value TCP, you can't enable the certificate for the UM Call Router service. + +You can specify multiple values separated by commas. The default values are IMAP, POP, and SMTP. + +You can't use this parameter with the GenerateRequest switch. + +Once you enable a certificate for a service, you can't remove the service from the certificate. + +```yaml +Type: AllowedServices +Parameter Sets: Certificate +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectKeyIdentifier +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectName +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. + +This parameter uses the syntax: `[C=CountryOrRegion,S=StateOrProvince,L=LocalityOrCity,O=Organization,OU=Department],CN=HostNameOrFQDN`. Although the only required value is `CN=HostNameOrFQDN`, you should always include `C=CountryOrRegion` for certificate requests, but other values might also be required by the certification authority. + +For example, if you want the certificate's subject to be mail.contoso.com in the United States, you can use any of the following values: + +- C=US,S=WA,L=Redmond,O=Contoso,OU=IT,CN=mail.contoso.com +- C=US,O=Contoso,CN=mail.contoso.com +- C=US,CN=mail.contoso.com + +If you don't use this parameter, the default value is the name of the Exchange server where you run the command (for example, CN=Mailbox01). + +For a subject alternative name (SAN) certificate, you should choose one of the values from the DomainName parameter to use in the SubjectName value. In fact, the CN value that you specify for SubjectName is automatically included in the DomainName values. + +For a wildcard certificate, use a SubjectName value that contains the wildcard character (\*). For example, C=US,CN=\*.contoso.com. + +```yaml +Type: X500DistinguishedName +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/organization/New-ExchangeSettings.md b/exchange/exchange-ps/exchange/New-ExchangeSettings.md similarity index 84% rename from exchange/exchange-ps/exchange/organization/New-ExchangeSettings.md rename to exchange/exchange-ps/exchange/New-ExchangeSettings.md index 959075628f..abedc962ae 100644 --- a/exchange/exchange-ps/exchange/organization/New-ExchangeSettings.md +++ b/exchange/exchange-ps/exchange/New-ExchangeSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/new-exchangesettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019" --- # New-ExchangeSettings @@ -17,17 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the New-ExchangeSettings cmdlet to create customized Exchange setting objects that are stored in Active Directory. Use the Set-ExchangeSettings cmdlet to configure the actual settings. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-ExchangeSettings [-Name] [-Confirm] [-DomainController ] [-Force] [-WhatIf] +New-ExchangeSettings [-Name] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,21 +47,13 @@ This example creates a new Exchange settings object for the Audit configuration 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 - - Audit - - Compliance - - DirectoryTasks - - LinkedRoleGroup - - MRS - - MRSScripts - - Store - - TopologyService ```yaml @@ -77,8 +72,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -111,7 +105,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -147,12 +143,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md new file mode 100644 index 0000000000..cc46098b0a --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md @@ -0,0 +1,209 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ExoPhishSimOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-ExoPhishSimOverrideRule cmdlet to create third-party phishing simulation override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +New-ExoPhishSimOverrideRule -Policy -SenderIpRanges + [-Comment ] + [-Confirm] + [-DomainController ] + [-Domains ] + [-Name ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ExoPhishSimOverrideRule -Policy PhishSimOverridePolicy -Domains fabrikam.com,wingtiptoys.com -SenderIpRanges 192.168.1.55 +``` + +This example creates a new phishing simulation override rule with the specified settings. Regardless of the Name value specified, the rule name will be `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). + +## PARAMETERS + +### -Policy +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 +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: Default, PublishComplianceTag, ComplianceTag, SetRawXml +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderIpRanges +The SenderIpRanges parameter specifies the source IP address that's used by the third-party phishing simulation. Valid values are: + +- Single IP address: For example, 192.168.1.1. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify up to 10 entries separated by commas. + +A phishing simulation entry requires at least one IP address in this parameter and at least one domain in the Domains parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Domains +The Domains parameter specifies the email domain that's used by the third-party 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). +- The DKIM domain. + +You can specify up to 20 values separated by commas. + +A phishing simulation requires at least one domain from this parameter and at least one IP address in the SenderIPRanges parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md new file mode 100644 index 0000000000..7abc967735 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md @@ -0,0 +1,158 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ExoSecOpsOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-ExoSecOpsOverrideRule cmdlet to create SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +New-ExoSecOpsOverrideRule -Policy + [-Comment ] + [-Confirm] + [-DomainController ] + [-Name ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ExoSecOpsOverrideRule -Name SecOpsOverrideRule -Policy SecOpsOverridePolicy +``` + +This example creates the SecOps mailbox override rule with the specified settings. Regardless of the Name value specified, the rule name will be `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). + +## PARAMETERS + +### -Policy +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 +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: Default, PublishComplianceTag, ComplianceTag, SetRawXml +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-FeatureConfiguration.md b/exchange/exchange-ps/exchange/New-FeatureConfiguration.md new file mode 100644 index 0000000000..2f093ab5f4 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-FeatureConfiguration.md @@ -0,0 +1,218 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/new-featureconfiguration +applicable: Security & Compliance +title: New-FeatureConfiguration +schema: 2.0.0 +--- + +# New-FeatureConfiguration + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +> [!NOTE] +> This cmdlet is currently available in Public Preview, isn't available in all organizations, and is subject to change. + +Use the New-FeatureConfiguration cmdlet to create Microsoft Purview feature configurations within your organization, including: + +- Collection policies. +- Advanced label based protection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-FeatureConfiguration [-Name] -Mode -FeatureScenario -ScenarioConfig + [-Comment ] + [-Confirm] + [-Locations ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +New-FeatureConfiguration -Name "Collection policy for supported Copilots" -FeatureScenario KnowYourData -Mode Enable -ScenarioConfig '{"Activities":["UploadText","DownloadText"],"EnforcementPlanes":["CopilotExperiences","Browser"],"SensitiveTypeIds":["All"],"IsIngestionEnabled":true}' –Locations '[{"Workload":"Applications","Location":"52655","LocationSource":"SaaS","LocationType":"Individual","Inclusions":[{"Type":"Tenant","Identity":"All","DisplayName":"All","Name":"All"}]},{"Workload":"Applications","Location":"49baeafd-1a6b-4c58-be55-75ae6d1dff6a","LocationSource":"PurviewConfig","LocationType":"Group","Inclusions":[{"Type":"Tenant","Identity":"All","DisplayName":"All","Name":"All"}]}]' +``` + +This example creates an enabled collection policy named "Collection policy for supported Copilots" that: +- Includes UploadText & DownloadText activity for all supported classifiers +- Captures all AI prompts +- Includes Microsoft Copilot & Copilot Experiences locations, both scoped to all users & groups + +### Example 2 +```powershell +New-FeatureConfiguration -Name "Scoped browser collection policy for Microsoft Copilot" -FeatureScenario KnowYourData -Mode Enable -ScenarioConfig '{"Activities":["UploadText"],"EnforcementPlanes":["Browser"],"SensitiveTypeIds":["All"],"ExcludedSensitiveTypeIds":["50b8b56b-4ef8-44c2-a924-03374f5831ce","8548332d-6d71-41f8-97db-cc3b5fa544e6"],"IsIngestionEnabled":false}' –Locations '[{"Workload":"Applications","Location":"52655","LocationDisplayName":null,"LocationSource":"SaaS","LocationType":"Individual","Inclusions":[{"Type":"Tenant","Identity":"All","DisplayName":"All","Name":"All"}],"Exclusions":[{"Type":"Group","Identity":"db458ddb-4f56-4d88-a4f7-e29545560839","DisplayName":"Contoso Executives","Name":"Executives@contoso.com"}]}]' +``` + +This example creates an enabled collection policy named "Scoped browser collection policy for Microsoft Copilot" that: +- Includes UploadText activity for all supported classifiers except "All Full Names" and "All Physical Addresses" +- Includes Microsoft Copilot location, for all users & groups except the "Contoso Executives Group" + +### Example 3 +```powershell +New-FeatureConfiguration -Name "Scoped collection policies for browser and devices" -FeatureScenario KnowYourData -Mode Disable -ScenarioConfig '{"Activities":["UploadText","filecreated","filedeleted","filemodified"],"EnforcementPlanes":["Devices","Browser"],"SensitiveTypeIds":["a44669fe-0d48-453d-a9b1-2cc83f2cba77","cb353f78-2b72-4c3c-8827-92ebe4f69fdf"],"FileExtensions":["pdf"],"IsIngestionEnabled":false}' –Locations '[{"Workload":"EndpointDevices","Location":"","Inclusions":[{"Type":"Group","Identity":"db458ddb-4f56-4d88-a4f7-e29545560839","DisplayName":"All Company","Name":"allcompany@contoso.com"}],"Exclusions":[{"Type":"IndividualResource","Identity":"a828f25a-cede-4d0e-97e6-b0b0c913732a","DisplayName":"Alex Wilber","Name":"alex@contoso.com"}]},{"Workload":"Applications","Location":"52655","LocationSource":"SaaS","LocationType":"Individual","Inclusions":[{"Type":"IndividualResource","Identity":"84f9af2e-b224-4cb8-b9cd-bc531bb07a48","DisplayName":"Adele Vance","Name":"adele@contoso.com"}]}]' +``` + +This example creates a disabled collection policy named "Scoped collection policies for browser and devices" that: +- Includes UploadText (for browser) and filecreated, filedeleted, and filemodified activities (for devices) +- Includes "U.S. Social Security Number (SSN)" and "ABA Routing Number" classifiers only +- Detects files on devices with "pdf" file extension only +- Includes devices location, scoped to the "All company" group, excluding the user "Alex Wilber" +- Includes Microsoft Copilot location, scoped only to the user "Adele Vance" + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FeatureScenario +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 + +```yaml +Type: PolicyScenario +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mode +The Mode parameter specifies feature configuration mode. Valid values are: + +- Enable: The feature configuration is enabled. +- Disable: The feature configuration is disabled. + +```yaml +Type: PolicyMode +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScenarioConfig +The ScenarioConfig parameter specifies additional information about the feature configuration. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locations +The locations parameter specifies where the feature configuration applies. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/New-FederationTrust.md b/exchange/exchange-ps/exchange/New-FederationTrust.md similarity index 80% rename from exchange/exchange-ps/exchange/federation-and-hybrid/New-FederationTrust.md rename to exchange/exchange-ps/exchange/New-FederationTrust.md index 36e5d43e2d..b1f50c5c62 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/New-FederationTrust.md +++ b/exchange/exchange-ps/exchange/New-FederationTrust.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/new-federationtrust +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-FederationTrust @@ -17,34 +16,41 @@ This cmdlet is available only in on-premises Exchange. Use the New-FederationTrust cmdlet to set up a federation trust between your Exchange organization and the Microsoft Federation Gateway. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### SkipNamespaceProviderProvisioning ``` -New-FederationTrust [-Name] -Thumbprint -ApplicationUri [-SkipNamespaceProviderProvisioning] [-AdministratorProvisioningId ] [-ApplicationIdentifier ] +New-FederationTrust [-Name] -Thumbprint -ApplicationUri + [-SkipNamespaceProviderProvisioning] + [-AdministratorProvisioningId ] + [-ApplicationIdentifier ] [-Confirm] [-DomainController ] [-MetadataUrl ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### FederationTrust ``` -New-FederationTrust [-Name] -Thumbprint [-SuppressDnsWarning] [-UseLegacyProvisioningService] +New-FederationTrust [-Name] -Thumbprint + [-SuppressDnsWarning] + [-UseLegacyProvisioningService] [-Confirm] [-DomainController ] [-MetadataUrl ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Federation trusts are trusts created between an Exchange organization and the Microsoft Federation Gateway. A federation trust is required to configure a federated organization identifier for federated sharing. -For more information, see [Federation](https://docs.microsoft.com/exchange/federation-exchange-2013-help). +For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -92,7 +98,7 @@ Accept wildcard characters: False ``` ### -SkipNamespaceProviderProvisioning -The SkipNamespaceProviderProvisioning switch specifies that the trust and federated organization identifier are provisioned externally without using federation functionality in Microsoft Exchange. +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. @@ -110,7 +116,7 @@ Accept wildcard characters: False ``` ### -Thumbprint -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://docs.microsoft.com/exchange/federation-exchange-2013-help). +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 @@ -164,8 +170,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -214,9 +219,11 @@ Accept wildcard characters: False ``` ### -SuppressDnsWarning -This parameter is available or functional only in 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. -The SuppressDNSWarning parameter specifies whether to display the DNS warning message for creating TXT records in your public DNS when running the New-FederationTrust cmdlet. Valid values are $true or $false. The default value is $false. However, this parameter is automatically set to $true when used by the Hybrid Configuration wizard. It's not recommended that you use this parameter when using the New-FederationTrust cmdlet. +This switch is used automatically by the Hybrid Configuration wizard. We don't recommend manually using this switch. ```yaml Type: SwitchParameter @@ -232,7 +239,9 @@ Accept wildcard characters: False ``` ### -UseLegacyProvisioningService -The UseLegacyProvisioningService parameter specifies if the legacy interface on the Microsoft Federation Gateway will be used for managing the federation trust, including federated domains, certificates, and federation metadata. Valid input for this parameter is $true or $false. The default value is $false. When using a self-signed certificate for configuring a federation trust with the Microsoft Federation Gateway, the trust needs to be created with the parameter set to $true. After the federation trust is created, this behavior can't be changed and requires the deletion and re-creation of the federation trust. We recommend you always use the default value of $false. +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. ```yaml Type: SwitchParameter @@ -268,12 +277,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md new file mode 100644 index 0000000000..4d11d7b876 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md @@ -0,0 +1,101 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertyauthority +applicable: Security & Compliance +title: New-FilePlanPropertyAuthority +schema: 2.0.0 +--- + +# New-FilePlanPropertyAuthority + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-FilePlanPropertyAuthority cmdlet to create file plan property authorities. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-FilePlanPropertyAuthority [-Name] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +New-FilePlanPropertyAuthority -Name "Contoso Authority" +``` + +This example creates a new file plan property authority named Contoso Authority. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md new file mode 100644 index 0000000000..acdefd1244 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md @@ -0,0 +1,101 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertycategor +applicable: Security & Compliance +title: New-FilePlanPropertyCategory +schema: 2.0.0 +--- + +# New-FilePlanPropertyCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-FilePlanPropertyCategory cmdlet to create file plan property categories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-FilePlanPropertyCategory [-Name] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +New-FilePlanPropertyCategory -Name "Contoso Category" +``` + +This example creates a new file plan property category named Contoso Category. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md new file mode 100644 index 0000000000..80625e0af9 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md @@ -0,0 +1,133 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertycitation +applicable: Security & Compliance +title: New-FilePlanPropertyCitation +schema: 2.0.0 +--- + +# New-FilePlanPropertyCitation + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-FilePlanPropertyCitation cmdlet to create file plan property citations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-FilePlanPropertyCitation [-Name] [[-CitationUrl] ] [[-CitationJurisdiction] ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +New-FilePlanPropertyCitation -Name "Contoso-0001" +``` + +This example creates a new file plan property citation named Contoso-0001. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CitationUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CitationJurisdiction +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md new file mode 100644 index 0000000000..8d084f8c09 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md @@ -0,0 +1,101 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertydepartment +applicable: Security & Compliance +title: New-FilePlanPropertyDepartment +schema: 2.0.0 +--- + +# New-FilePlanPropertyDepartment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-FilePlanPropertyDepartment cmdlet to create file plan property departments. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-FilePlanPropertyDepartment [-Name] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +New-FilePlanPropertyDepartment -Name "Contoso HR" +``` + +This example creates a new file plan property department named Contoso HR. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md new file mode 100644 index 0000000000..f32d9f3ac4 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md @@ -0,0 +1,101 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertyreferenceid +applicable: Security & Compliance +title: New-FilePlanPropertyReferenceId +schema: 2.0.0 +--- + +# New-FilePlanPropertyReferenceId + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-FilePlanPropertyReferenceId cmdlet to create file plan property reference IDs. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-FilePlanPropertyReferenceId [-Name] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +New-FilePlanPropertyAuthority -Name "Contoso-0001" +``` + +This example creates a new file plan property reference ID named Contoso-0001. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md b/exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md new file mode 100644 index 0000000000..ceff1b7f3e --- /dev/null +++ b/exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md @@ -0,0 +1,121 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertysubcategory +applicable: Security & Compliance +title: New-FilePlanPropertySubCategory +schema: 2.0.0 +--- + +# New-FilePlanPropertySubCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-FilePlanPropertySubCategory cmdlet to create file plan property subcategories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-FilePlanPropertySubCategory [-Name] -ParentId + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +New-FilePlanPropertySubCategory -Name "US Tax" -ParentId "Contoso Category" +``` + +This example creates a new file plan property subcategory named US Tax that's a subcategory of the parent file plan property category named Contoso Category. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParentId +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-Fingerprint.md b/exchange/exchange-ps/exchange/New-Fingerprint.md similarity index 75% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-Fingerprint.md rename to exchange/exchange-ps/exchange/New-Fingerprint.md index 57a236cebc..b2d1f80558 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-Fingerprint.md +++ b/exchange/exchange-ps/exchange/New-Fingerprint.md @@ -1,48 +1,70 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-fingerprint -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-Fingerprint ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. -**Note**: In Exchange Online, this cmdlet has been replaced by the [New-DlpFingerPrint](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpfingerprint) cmdlet in Office 365 Security & Compliance Center PowerShell. +**Note**: In Exchange Online, this cmdlet has been replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchange/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell. Use the New-Fingerprint cmdlet to create document fingerprints that are used with data classification rules. Because the results of New-Fingerprint are not stored outside of the data classification rule, you always run New-Fingerprint and New-DataClassification or Set-DataClassification in the same PowerShell session. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-Fingerprint [[-FileData] ] -Description [-Confirm] [-WhatIf] [] +New-Fingerprint [[-FileData] ] -Description + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$Patent_Template = Get-Content "C:\My Documents\Contoso Patent Template.docx" -Encoding byte; $Patent_Fingerprint = New-Fingerprint -FileData $Patent_Template -Description "Contoso Patent Template" +$Patent_Template = [System.IO.File]::ReadAllBytes('C:\My Documents\Contoso Patent Template.docx') + +$Patent_Fingerprint = New-Fingerprint -FileData $Patent_Template -Description "Contoso Patent Template" ``` This example creates a new document fingerprint based on the file C:\\My Documents\\Contoso Patent Template.docx. You store the new fingerprint as a variable so you can use it with the New-DataClassification cmdlet in the same PowerShell session. ## PARAMETERS +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Description The Description parameter specifies a description for the document fingerprint. @@ -50,7 +72,7 @@ The Description parameter specifies a description for the document fingerprint. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -62,15 +84,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -79,24 +100,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -FileData -The FileData parameter specifies the file to use as a document fingerprint. - -You need to read the file to a byte-encoded object using the Get-Content cmdlet. For details, see the section. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -104,7 +107,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -118,12 +121,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-ForeignConnector.md b/exchange/exchange-ps/exchange/New-ForeignConnector.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/New-ForeignConnector.md rename to exchange/exchange-ps/exchange/New-ForeignConnector.md index 326b328762..07676050af 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-ForeignConnector.md +++ b/exchange/exchange-ps/exchange/New-ForeignConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-foreignconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-ForeignConnector @@ -17,20 +16,24 @@ This cmdlet is available only in on-premises Exchange. Use the New-ForeignConnector cmdlet to create a new Foreign connector in the Transport service of a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-ForeignConnector [-Name] -AddressSpaces [-Confirm] - [-DomainController ] [-IsScopedConnector ] - [-SourceTransportServers ] [-WhatIf] [] +New-ForeignConnector [-Name] -AddressSpaces + [-Confirm] + [-DomainController ] + [-IsScopedConnector ] + [-SourceTransportServers ] + [-WhatIf] + [] ``` ## DESCRIPTION A Foreign connector uses a Drop directory in the Transport service of a Mailbox server to send messages to a local messaging server that doesn't use SMTP as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Third-party fax gateway servers are examples of foreign gateway servers. The address spaces assigned to a Foreign connector can be SMTP or non-SMTP. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,37 +45,44 @@ New-ForeignConnector -Name "Contoso Foreign Connector" -AddressSpaces "X400:c=US This example creates a Foreign connector with the following properties: - Connector name: Contoso Foreign Connector - - Address space: "c=US;a=Fabrikam;P=Contoso" - - Address space type: X.400 - - Address space cost: 5 - - Source transport servers: Hub01 and Hub02 ## PARAMETERS +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -AddressSpaces -The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is as follows: \:\;\ +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. - - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of an address type, you can enter any text for the address space. - - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("). For example, the following address space entries are equivalent: - "SMTP:contoso.com;1" - - "contoso.com;1" - - "SMTP:contoso.com" - - contoso.com -You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3". +You may specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. ```yaml Type: MultiValuedProperty @@ -87,27 +97,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -160,7 +153,7 @@ Accept wildcard characters: False ### -SourceTransportServers 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. -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: MultiValuedProperty @@ -196,12 +189,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-GlobalAddressList.md b/exchange/exchange-ps/exchange/New-GlobalAddressList.md similarity index 91% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/New-GlobalAddressList.md rename to exchange/exchange-ps/exchange/New-GlobalAddressList.md index b530b29be7..990ae4ba24 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-GlobalAddressList.md +++ b/exchange/exchange-ps/exchange/New-GlobalAddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/new-globaladdresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-GlobalAddressList @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-GlobalAddressList cmdlet to create a global address list (GAL). -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -47,7 +46,8 @@ New-GlobalAddressList [-Name] -IncludedRecipients ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### CustomFilter @@ -56,21 +56,20 @@ New-GlobalAddressList [-Name] -RecipientFilter [-Confirm] [-DomainController ] [-RecipientContainer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - - The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - - The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPath filter. +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -83,7 +82,7 @@ This example creates the GAL named NewGAL. ### Example 2 ```powershell -New-GlobalAddressList -Name GAL_AgencyB -RecipientFilter "(RecipientType -eq 'UserMailbox') -and (CustomAttribute15 -eq 'AgencyB')" +New-GlobalAddressList -Name GAL_AgencyB -RecipientFilter "(RecipientTypeDetails -eq 'UserMailbox') -and (CustomAttribute15 -eq 'AgencyB')" ``` This example creates the GAL named GAL\_AgencyB by using the RecipientFilter parameter to include all mailbox users whose custom attribute 15 equals AgencyB. @@ -110,20 +109,15 @@ Accept wildcard characters: False 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. - - MailboxUsers - - MailContacts - - MailGroups - - MailUsers - - Resources: This value indicates room or equipment mailboxes. You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. -You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You need to use this parameter when you use any Conditional parameters as part of a precanned filter. You can't use this parameter in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: WellKnownRecipientType @@ -139,21 +133,16 @@ Accept wildcard characters: False ``` ### -RecipientFilter -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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). - In cloud-based environments, you can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. - - In on-premises Exchange, wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter in combination with the IncludedRecipients parameter or any Conditional parameters (which are used to create precanned filters). @@ -175,7 +164,7 @@ The ConditionalCompany parameter specifies a precanned filter that's based on th 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -195,7 +184,7 @@ The ConditionalCustomAttribute1 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -215,7 +204,7 @@ The ConditionalCustomAttribute10 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -235,7 +224,7 @@ The ConditionalCustomAttribute11 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -255,7 +244,7 @@ The ConditionalCustomAttribute12 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -275,7 +264,7 @@ The ConditionalCustomAttribute13 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -295,7 +284,7 @@ The ConditionalCustomAttribute14 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -315,7 +304,7 @@ The ConditionalCustomAttribute15 parameter specifies a precanned filter that's b 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -335,7 +324,7 @@ The ConditionalCustomAttribute2 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -355,7 +344,7 @@ The ConditionalCustomAttribute3 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -375,7 +364,7 @@ The ConditionalCustomAttribute4 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -395,7 +384,7 @@ The ConditionalCustomAttribute5 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -415,7 +404,7 @@ The ConditionalCustomAttribute6 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -435,7 +424,7 @@ The ConditionalCustomAttribute7 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -455,7 +444,7 @@ The ConditionalCustomAttribute8 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -475,7 +464,7 @@ The ConditionalCustomAttribute9 parameter specifies a precanned filter that's ba 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -495,7 +484,7 @@ The ConditionalDepartment parameter specifies a precanned filter that's based on 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -515,7 +504,7 @@ The ConditionalStateOrProvince parameter specifies a precanned filter that's bas 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. -You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPath filters). +You use this parameter in combination with the IncludedRecipients parameter as part of a precanned filter. You can't use any Conditional parameters in combination with the RecipientFilter parameter (which is used to create custom OPATH filters). ```yaml Type: MultiValuedProperty @@ -533,8 +522,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -574,11 +562,8 @@ 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: - Name - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is the OU where the object was created. @@ -617,12 +602,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md new file mode 100644 index 0000000000..68a8cdeb6a --- /dev/null +++ b/exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md @@ -0,0 +1,233 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-HoldCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-HoldCompliancePolicy cmdlet to create new preservation policies in the Microsoft Purview compliance portal. + +**Note**: The New-HoldCompliancePolicy cmdlet has been replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-HoldCompliancePolicy [-Name] + [-Comment ] + [-Confirm] + [-Enabled ] + [-ExchangeLocation ] + [-Force] + [-PublicFolderLocation ] + [-SharePointLocation ] + [-WhatIf] + [] +``` + +## DESCRIPTION +New policies are not valid and will not be applied until a preservation rule is added to the policy. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-HoldCompliancePolicy -Name "Regulation 123 Compliance" -ExchangeLocation "Kitty Petersen", "Scott Nakamura" -SharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" +``` + +This example creates a preservation policy named "Regulation 123 Compliance" for the mailboxes of Kitty Petersen and Scott Nakamura, and the finance SharePoint site. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +If no mailboxes are specified, then no mailboxes are placed on hold. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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"`. + +SharePoint sites can't be added to the policy until they have been indexed. If no sites are specified, then no sites are placed on hold. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-HoldComplianceRule.md b/exchange/exchange-ps/exchange/New-HoldComplianceRule.md new file mode 100644 index 0000000000..9ebebdb7c5 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-HoldComplianceRule.md @@ -0,0 +1,258 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-HoldComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-HoldComplianceRule cmdlet to create new preservation rules in the Microsoft Purview compliance portal. + +**Note**: The New-HoldComplianceRule cmdlet has been replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-HoldComplianceRule [-Name] -Policy + [-Comment ] + [-Confirm] + [-ContentDateFrom ] + [-ContentDateTo ] + [-ContentMatchQuery ] + [-Disabled ] + [-HoldContent ] + [-HoldDurationDisplayHint ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The preservation rule must be added to an existing preservation policy using the Policy parameter. Only one rule can be added to each preservation policy. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-HoldComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -ContentDateFrom "09/10/14 5:00 PM" -ContentDateTo "09/10/15 5:00 PM" -HoldContent Unlimited +``` + +This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates will be held indefinitely. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +The Policy parameter specifies the policy to contain the rule. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateFrom +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateTo +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldContent +The HoldContent parameter specifies the hold duration for the preservation rule. Valid values are: + +- An integer: The hold duration in days. +- Unlimited: The content is held indefinitely. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldDurationDisplayHint +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 +- Years + +For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. + +```yaml +Type: HoldDurationHint +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md new file mode 100644 index 0000000000..ef6356928d --- /dev/null +++ b/exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md @@ -0,0 +1,1310 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-HostedContentFilterPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-HostedContentFilterPolicy cmdlet to create spam filter policies (content filter policies) in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-HostedContentFilterPolicy [-Name] + [-AddXHeaderValue ] + [-AdminDisplayName ] + [-AllowedSenderDomains ] + [-AllowedSenders ] + [-BlockedSenderDomains ] + [-BlockedSenders ] + [-BulkQuarantineTag ] + [-BulkSpamAction ] + [-BulkThreshold ] + [-Confirm] + [-DownloadLink ] + [-EnableEndUserSpamNotifications ] + [-EnableLanguageBlockList ] + [-EnableRegionBlockList ] + [-EndUserSpamNotificationCustomFromAddress ] + [-EndUserSpamNotificationCustomFromName ] + [-EndUserSpamNotificationCustomSubject ] + [-EndUserSpamNotificationFrequency ] + [-EndUserSpamNotificationLanguage ] + [-EndUserSpamNotificationLimit ] + [-HighConfidencePhishAction ] + [-HighConfidencePhishQuarantineTag ] + [-HighConfidenceSpamAction ] + [-HighConfidenceSpamQuarantineTag ] + [-IncreaseScoreWithBizOrInfoUrls ] + [-IncreaseScoreWithImageLinks ] + [-IncreaseScoreWithNumericIps ] + [-IncreaseScoreWithRedirectToOtherPort ] + [-InlineSafetyTipsEnabled ] + [-IntraOrgFilterState ] + [-LanguageBlockList ] + [-MarkAsSpamBulkMail ] + [-MarkAsSpamEmbedTagsInHtml ] + [-MarkAsSpamEmptyMessages ] + [-MarkAsSpamFormTagsInHtml ] + [-MarkAsSpamFramesInHtml ] + [-MarkAsSpamFromAddressAuthFail ] + [-MarkAsSpamJavaScriptInHtml ] + [-MarkAsSpamNdrBackscatter ] + [-MarkAsSpamObjectTagsInHtml ] + [-MarkAsSpamSensitiveWordList ] + [-MarkAsSpamSpfRecordHardFail ] + [-MarkAsSpamWebBugsInHtml ] + [-ModifySubjectValue ] + [-PhishQuarantineTag ] + [-PhishSpamAction ] + [-PhishZapEnabled ] + [-QuarantineRetentionPeriod ] + [-RecommendedPolicyType ] + [-RedirectToRecipients ] + [-RegionBlockList ] + [-SpamAction ] + [-SpamQuarantineTag ] + [-SpamZapEnabled ] + [-TestModeAction ] + [-TestModeBccToRecipients ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits). + +## EXAMPLES + +### Example 1 +```powershell +New-HostedContentFilterPolicy -Name "Contoso Executives" -HighConfidenceSpamAction Quarantine -SpamAction Quarantine -BulkThreshold 6 +``` + +This example creates a spam filter policy named Contoso Executives with the following settings: + +- Quarantine messages when the spam filtering verdict is spam or high confidence spam. +- BCL 6 triggers the action for a bulk email spam filtering verdict. + +## PARAMETERS + +### -Name +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: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddXHeaderValue +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 +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +The maximum length is 255 characters, and the value can't contain spaces or colons (:). + +For example, if you enter the value `X-This-is-my-custom-header`, the X-header that's added to the message is `X-This-is-my-custom-header: This message appears to be spam.` + +If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`). + +Note that this setting is independent of the AddXHeader value of the TestModeAction parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedSenderDomains +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedSenders +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedSenderDomains +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedSenders +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BulkQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined as bulk as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BulkSpamAction +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. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- NoAction +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BulkThreshold +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). + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DownloadLink +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableEndUserSpamNotifications +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableLanguageBlockList +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. +- $false: Don't mark messages as spam solely based on their languages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableRegionBlockList +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. +- $false: Don't mark messages as spam solely based on the source country or region. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomFromAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomFromName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomSubject +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationFrequency +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationLanguage +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationLimit +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidencePhishAction +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. +- Quarantine: Move the message to quarantine. By default, messages that are quarantined as high confidence phishing are available only to admins. Or, you can use the HighConfidencePhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. + +```yaml +Type: PhishFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidencePhishQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named AdminOnlyAccessPolicy is used. This quarantine policy enforces the historical capabilities for messages that were quarantined as high confidence phishing as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidenceSpamAction +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). +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as high confidence spam are available to the intended recipients and admins. Or, you can use the HighConfidenceSpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidenceSpamQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined as high confidence spam as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithBizOrInfoUrls +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. +- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting will be marked as spam. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithImageLinks +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. +- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting will be marked as spam. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithNumericIps +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. +- On: The setting is enabled. Messages that contain links to IP addresses are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. Note that not all messages which matches the setting will be marked as spam. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithRedirectToOtherPort +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. +- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. Note that not all messages which matches the setting will be marked as spam. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InlineSafetyTipsEnabled +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. +- $false: Safety tips are disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IntraOrgFilterState +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. +- HighConfidencePhish +- Phish: Includes phishing and high confidence phishing. +- HighConfidenceSpam: Includes high confidence spam, phishing, and high confidence phishing. +- Spam: Includes spam, high confidence spam, phishing, and high confidence phishing. +- Disabled + +```yaml +Type: IntraOrgFilterState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LanguageBlockList +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. + +A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Not all possible language codes are available as input for this parameter. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamBulkMail +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. +- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. +- Test: This value is available, but isn't used for this parameter. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamEmbedTagsInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamEmptyMessages +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. +- On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamFormTagsInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamFramesInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ or \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamFromAddressAuthFail +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. +- On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamJavaScriptInHtml +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. +- On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamNdrBackscatter +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. +- On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamObjectTagsInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamSensitiveWordList +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. +- On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamSpfRecordHardFail +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. +- On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamWebBugsInHtml +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. +- On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModifySubjectValue +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 +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined as phishing as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishSpamAction +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. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients (as of April, 2020) and admins. +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishZapEnabled +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. +- $false: ZAP for phishing messages is disabled. + +You configure ZAP for spam with the SpamZapEnabled parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineRetentionPeriod +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 +- HighConfidencePhishAction +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +A valid value is an integer between 1 and 30. The default value is 15. + +After the time period expires, the message is deleted. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecommendedPolicyType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RedirectToRecipients +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 +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RegionBlockList +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. + +A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). + +To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +To empty the list, use the value $null. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamAction +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). +- Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization) is used. This quarantine policy enforces the historical capabilities for messages that were quarantined as spam as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamZapEnabled +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. +- $false: ZAP for spam is disabled. + +You configure ZAP for phishing messages with the PhishZapEnabled parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TestModeAction +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. +- AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. +- BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter. + +```yaml +Type: SpamFilteringTestModeAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TestModeBccToRecipients + +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. + +This parameter is meaningful only when the value of the TestModeAction parameter is BccMessage, and when the value of one or more IncreaseScoreWith\* or MarkAsSpam\* parameters is Test. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/antispam-antimalware/New-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/New-HostedContentFilterRule.md similarity index 79% rename from exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterRule.md rename to exchange/exchange-ps/exchange/New-HostedContentFilterRule.md index e663911cfc..427202c583 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterRule.md +++ b/exchange/exchange-ps/exchange/New-HostedContentFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/new-hostedcontentfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # New-HostedContentFilterRule @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the New-HostedContentFilterRule cmdlet to create spam filter rules (content filter rules) in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -36,11 +32,15 @@ New-HostedContentFilterRule [-Name] -HostedContentFilterPolicy ] [-SentTo ] [-SentToMemberOf ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Use the Microsoft Defender portal to create anti-spam policies](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure#use-the-microsoft-defender-portal-to-create-anti-spam-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,45 +53,43 @@ This example creates a new spam filter rule named Contoso Recipients with the fo ## PARAMETERS -### -HostedContentFilterPolicy -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: - -- Name - -- Distinguished name (DN) - -- GUID +### -Name +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 ("). -You can't specify the default spam filter policy, and you can't specify a spam filter policy that's already associated with another spam filter rule. +Don't use the following characters in the name value: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. ```yaml -Type: HostedContentFilterPolicyIdParameter +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Online, Exchange Online Protection Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 ("). +### -HostedContentFilterPolicy +The HostedContentFilterPolicy parameter specifies the spam filter policy (content filter policy) that's associated with the rule. -Don't use the following characters in the name value: \\, %, &, \*, +, /, =, ?, {, }, \|, \<, \>, (, ), ;, :, [, ], comma (,), or double quotation mark ("). +You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can't specify the default spam filter policy, and you can't specify a spam filter policy that's already associated with another spam filter rule. ```yaml -Type: String +Type: HostedContentFilterPolicyIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Online, Exchange Online Protection Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -116,8 +114,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -150,7 +147,7 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception for the rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -169,18 +166,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -196,21 +188,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf -The ExceptIfSentToMemberOf parameter specifies an exception for the rule that looks for messages sent to members of groups. You can use any value that uniquely identifies the group. For example: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. @@ -233,9 +220,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a 9th new rule are from 0 through 8. - - The default value for the new 9th rule is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -254,7 +239,7 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition for the rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -273,18 +258,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -300,21 +280,16 @@ Accept wildcard characters: False ``` ### -SentToMemberOf -The SentToMemberOf parameter specifies a condition for the rule 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: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. @@ -352,12 +327,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md new file mode 100644 index 0000000000..6f78d93176 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md @@ -0,0 +1,285 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-HostedOutboundSpamFilterPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-HostedOutboundSpamFilterPolicy cmdlet to create outbound spam filter policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-HostedOutboundSpamFilterPolicy [-Name] + [-ActionWhenThresholdReached ] + [-AdminDisplayName ] + [-AutoForwardingMode ] + [-BccSuspiciousOutboundAdditionalRecipients ] + [-BccSuspiciousOutboundMail ] + [-NotifyOutboundSpam ] + [-NotifyOutboundSpamRecipients ] + [-RecipientLimitExternalPerHour ] + [-RecipientLimitInternalPerHour ] + [-RecipientLimitPerDay ] + [-RecommendedPolicyType ] + [] +``` + +## DESCRIPTION +New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the HostedOutboundSpamFilterPolicy parameter on the New-HostedOutboundSpamFilterRule or Set-HostedOutboundSpamFilterRule cmdlets to associate the policy with a rule. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-HostedOutboundSpamFilterPolicy -Name "Contoso Executives" -RecipientLimitExternalPerHour 400 -RecipientLimitInternalPerHour 800 -RecipientLimitPerDay 800 -ActionWhenThresholdReached BlockUser +``` + +This example creates a new outbound spam filter policy named Contoso Executives with the following settings: + +- The recipient rate limits are restricted to smaller values that the service defaults. +- After one of the limits is reached, the user is prevented from sending messages (added to the Restricted Users portal). + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActionWhenThresholdReached +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. +- BlockUser: Prevent the user from sending email messages. +- BlockUserForToday: Prevent the user from sending email messages until the following day. This is the default value. + +```yaml +Type: OutboundRecipientLimitsExceededAction +Parameter Sets: (All) +Aliases: +Accepted values: Alert, BlockUserForToday, BlockUser +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoForwardingMode +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). +- On: Automatic external email forwarding isn't disabled by the policy. +- Off: Automatic external email forwarding is disabled by the policy and results in a non-delivery report (also known as an NDR or bounce message) to the sender. + +This setting applies to cloud-based mailboxes only. Automatic forwarding to internal recipients isn't affected by this setting. + +```yaml +Type: AutoForwardingMode +Parameter Sets: (All) +Aliases: +Accepted values: Automatic, Off, On +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BccSuspiciousOutboundAdditionalRecipients +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BccSuspiciousOutboundMail +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. +- $false: No additional messages are added to outgoing spam messages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyOutboundSpam +**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: + +- $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter. +- $false: Don't send notifications. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyOutboundSpamRecipients +**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. + +The specified recipients receive notifications when the value of the NotifyOutboundSpam parameter is $true. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientLimitExternalPerHour +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientLimitInternalPerHour +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientLimitPerDay +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecommendedPolicyType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md similarity index 83% rename from exchange/exchange-ps/exchange/antispam-antimalware/New-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md index 14864746e9..721a9bd38a 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/new-hostedoutboundspamfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # New-HostedOutboundSpamFilterRule @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the New-HostedOutboundSpamFilterRule cmdlet to create outbound spam filter rules in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -36,11 +32,12 @@ New-HostedOutboundSpamFilterRule [-Name] -HostedOutboundSpamFilterPolic [-FromMemberOf ] [-Priority ] [-SenderDomainIs ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,7 +53,7 @@ This example creates a new outbound spam filter rule named Contoso Executives th ### -Name 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 ("). -The value itself can't contain the following characters: \\, %, &, \*, +, /, =, ?, {, }, \|, \<, \>, (, ), ;, :, [, ], comma (,), or double quotation mark ("). +Don't use the following characters: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. ```yaml Type: String @@ -77,9 +74,7 @@ The HostedOutboundSpamFilterPolicy parameter specifies the outbound spam filter You can use any value that uniquely identifies the policy. For example: - Name - - Distinguished name (DN) - - GUID. You can't specify the default outbound spam filter policy, and you can't specify a policy that's already associated with another outbound spam filter rule. @@ -116,8 +111,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -137,7 +131,6 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: - $true: The rule is enabled. This is the default value. - - $false: The rule is disabled. In the properties of the rule, the value of this parameter is visible in the State property. @@ -159,18 +152,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -189,18 +177,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -235,18 +218,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -265,18 +243,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -297,9 +270,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a new rule (the 9th rule) are from 0 through 8. - - The default value for a new rule (the 9th rule) is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -354,12 +325,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/New-HybridConfiguration.md b/exchange/exchange-ps/exchange/New-HybridConfiguration.md similarity index 78% rename from exchange/exchange-ps/exchange/federation-and-hybrid/New-HybridConfiguration.md rename to exchange/exchange-ps/exchange/New-HybridConfiguration.md index cfd4a13ea4..7d9e42ecac 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/New-HybridConfiguration.md +++ b/exchange/exchange-ps/exchange/New-HybridConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/new-hybridconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-HybridConfiguration @@ -15,28 +14,38 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the New-HybridConfiguration cmdlet to create the HybridConfiguration object and set up a hybrid deployment between your on-premises Exchange organization and a Microsoft Office 365 for enterprises organization. +Use the New-HybridConfiguration cmdlet to create the HybridConfiguration object and set up a hybrid deployment between your on-premises Exchange organization and a Microsoft 365 for enterprises organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-HybridConfiguration [-ClientAccessServers ] [-Confirm] [-DomainController ] - [-Domains ] [-ExternalIPAddresses ] - [-Features ] [-OnPremisesSmartHost ] - [-SecureMailCertificateThumbprint ] [-TransportServers ] [-WhatIf] - [-EdgeTransportServers ] [-ReceivingTransportServers ] - [-SendingTransportServers ] [-ServiceInstance ] - [-TlsCertificateName ] [] +New-HybridConfiguration + [-ClientAccessServers ] + [-Confirm] + [-DomainController ] + [-Domains ] + [-EdgeTransportServers ] + [-ExternalIPAddresses ] + [-Features ] + [-OnPremisesSmartHost ] + [-ReceivingTransportServers ] + [-SecureMailCertificateThumbprint ] + [-SendingTransportServers ] + [-ServiceInstance ] + [-TlsCertificateName ] + [-TransportServers ] + [-WhatIf] + [] ``` ## DESCRIPTION A hybrid deployment offers organizations the ability to extend the feature-rich experience and administrative control they have with their existing on-premises Microsoft Exchange organization to the cloud. The New-HybridConfiguration cmdlet is used with the Hybrid Configuration wizard and is typically configured when the hybrid deployment is initially created by the wizard. We strongly recommend that you use the Hybrid Configuration wizard to create the HybridConfiguration object and configure your hybrid deployment with the Exchange Online organization. -For more information, see [Exchange Server hybrid deployments](https://docs.microsoft.com/exchange/exchange-hybrid). +For more information, see [Exchange Server hybrid deployments](https://learn.microsoft.com/exchange/exchange-hybrid). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,19 +54,17 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-HybridConfiguration ``` -This example creates the hybrid configuration Hybrid Configuration with the default hybrid configuration settings. +This example creates the hybrid configuration named Hybrid Configuration with the default hybrid configuration settings. ## PARAMETERS ### -ClientAccessServers -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. The ClientAccessServers parameter specifies the Exchange Server 2010 SP2 servers with the Client Access server role installed that will be configured to support the hybrid deployment features. At least one Client Access server must be defined and be externally accessible from the Internet on ports 80 and 443. The servers will be configured to enable the following: - Mailbox Replication Service (MRS) Proxy The MRS Proxy service configuration on the Client Access servers will be enabled. - - Virtual Directories The Client Access servers will host the default Web sites for the Exchange Web Services (EWS), offline address books, and ActiveSync services. - - Outlook Anywhere The Client Access servers will have Outlook Anywhere enabled. ```yaml @@ -76,8 +83,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,6 +131,24 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -EdgeTransportServers +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ExternalIPAddresses The ExternalIPAddresses parameter is a legacy parameter that specifies the publicly accessible inbound IP address of Microsoft Exchange Server 2010 Hub Transport servers. The only configuration change that should be made with this parameter is to change or clear the legacy Exchange 2010 Hub Transport server IP address value. The IP address must be Internet Protocol version 4 (IPv4) based only. @@ -145,19 +169,12 @@ Accept wildcard characters: False The Features parameter specifies the features that are enabled for the hybrid configuration. One or more of the following values separated by commas can be entered. When using the Hybrid Configuration wizard, all features are enabled by default. - OnlineArchive: Enables the Exchange Online archive for on-premises Exchange and Exchange Online organization users. - - FreeBusy: Enables free/busy calendar information to be shared between on-premises Exchange and Exchange Online organization users. - - MailTips: Enables MailTips information to be shared between on-premises Exchange and Exchange Online organization users. - - MessageTracking: Enables message tracking information to be shared between on-premises Exchange and Exchange Online organization users. - - OWARedirection: Enables automatic Microsoft Outlook on the web redirection to either the on-premises Exchange or Exchange Online organizations depending on where the user mailbox is located. - - SecureMail: Enables secure message transport via Transport Layer Security (TLS) between the on-premises Exchange and Exchange Online organizations. - - Centralized: Enables the on-premises servers to handle all message transport between the on-premises Exchange and Exchange Online organizations, including message delivering to the Internet for both organizations. If this value is $false, the on-premises server and Exchange Online organization are each responsible for their own Internet message delivery. - - Photos: Enables the sharing of user photo data between the on-premises Exchange and Exchange Online organizations. This feature works in tandem with the PhotosEnabled parameter in the OrganizationRelationship cmdlets in a hybrid deployment. If the Photos parameter is $true, the PhotosEnabled parameter is automatically set to $true. If the Photos parameter is $false, the PhotosEnabled parameter is automatically set to $false. When running the Hybrid Configuration wizard for the first time, the default value is $true. ```yaml @@ -189,16 +206,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -SecureMailCertificateThumbprint -This parameter is available or functional only in Exchange Server 2010. +### -ReceivingTransportServers +The ReceivingTransportServers parameter specifies the Mailbox servers that are defined in the outbound connector configuration of the Microsoft Exchange Online Protection (EOP) service included as part of the Microsoft 365 organization. The servers defined in the ReceivingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the Exchange Online organization to the on-premises Exchange organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the ReceivingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. -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. +If configuring the EdgeTransportServers parameter in the hybrid deployment, the ReceivingTransportServers parameter value must be $null. ```yaml -Type: String +Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -207,13 +224,13 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -TransportServers -This parameter is available or functional only in Exchange Server 2010. +### -SecureMailCertificateThumbprint +This parameter is available only in Exchange Server 2010. -The TransportServers parameter specifies the Exchange Server 2010 SP2 servers with the Hub Transport server role installed that are configured to support the hybrid deployment features. At least one Hub Transport server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises and cloud-based organizations. +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. ```yaml -Type: MultiValuedProperty +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 @@ -225,26 +242,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EdgeTransportServers -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. +### -SendingTransportServers +The SendingTransportServers parameter specifies the Exchange Mailbox servers that are defined in the inbound connector configuration of the EOP service included as part of the Microsoft 365 organization. The servers defined in the SendingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the on-premises Exchange organization to the Exchange Online organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the SendingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. -When configuring the EdgeTransportServers parameter, you must configure the ReceivingTransportServers and SendingTransportServers parameter values to $null. +If configuring the EdgeTransportServers parameter in the hybrid deployment, the SendingTransportServers parameter value must be $null. ```yaml Type: MultiValuedProperty @@ -259,13 +260,11 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -ReceivingTransportServers -The ReceivingTransportServers parameter specifies the Mailbox servers that are defined in the outbound connector configuration of the Microsoft Exchange Online Protection (EOP) service included as part of the Office 365 for enterprises tenant. The servers defined in the ReceivingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the Exchange Online organization to the on-premises Exchange organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the ReceivingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. - -If configuring the EdgeTransportServers parameter in the hybrid deployment, the ReceivingTransportServers parameter value must be $null. +### -ServiceInstance +The ServiceInstance parameter should only be used by organizations manually configuring hybrid deployments with Office 365 operated by 21Vianet in China. All other organizations should use the Hybrid Configuration wizard to configure a hybrid deployment with Microsoft 365. The valid values for this parameter are 0 (null) or 1. The default value is 0 (null).For organizations connecting with Office 365 operated by 21Vianet in China, set this value to 1 when manually configuring your hybrid deployment. ```yaml -Type: MultiValuedProperty +Type: Int32 Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -277,13 +276,11 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -SendingTransportServers -The SendingTransportServers parameter specifies the Exchange Mailbox servers that are defined in the inbound connector configuration of the EOP service included as part of the Office 365 for enterprises tenant. The servers defined in the SendingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the on-premises Exchange organization to the Exchange Online organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the SendingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. - -If configuring the EdgeTransportServers parameter in the hybrid deployment, the SendingTransportServers parameter value must be $null. +### -TlsCertificateName +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: MultiValuedProperty +Type: SmtpX509Identifier Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -295,14 +292,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -ServiceInstance -The ServiceInstance parameter should only be used by organizations manually configuring hybrid deployments with Office 365 operated by 21Vianet in China. All other organizations should use the Hybrid Configuration wizard to configure a hybrid deployment with Office 365. The valid values for this parameter are 0 (null) or 1. The default value is 0 (null).For organizations connecting with Office 365 operated by 21Vianet in China, set this value to 1 when manually configuring your hybrid deployment. +### -TransportServers +This parameter is available only in Exchange Server 2010. + +The TransportServers parameter specifies the Exchange Server 2010 SP2 servers with the Hub Transport server role installed that are configured to support the hybrid deployment features. At least one Hub Transport server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises and cloud-based organizations. ```yaml -Type: Int32 +Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010 Required: False Position: Named @@ -311,19 +310,19 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -TlsCertificateName -The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\X.500Issuer\X.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. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: SmtpX509Identifier +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -332,12 +331,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-InboundConnector.md b/exchange/exchange-ps/exchange/New-InboundConnector.md new file mode 100644 index 0000000000..ab3f7a8b2d --- /dev/null +++ b/exchange/exchange-ps/exchange/New-InboundConnector.md @@ -0,0 +1,550 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-InboundConnector + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-InboundConnector cmdlet to create a new Inbound connector in your cloud-based organization. + +**Note**: Creation of inbound connectors is restricted in [Microsoft 365 E5 developer subscriptions](https://learn.microsoft.com/office/developer-program/microsoft-365-developer-program-faq#does-the-microsoft-365-e5-developer-subscription-include-the-same-capabilities-that-the-regular-microsoft-365-e5-subscription-includes-). Opening a support ticket in affected organizations won't help. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-InboundConnector [-Name] -SenderDomains + [-AssociatedAcceptedDomains ] + [-ClientHostNames ] + [-CloudServicesMailEnabled ] + [-Comment ] + [-Confirm] + [-ConnectorSource ] + [-ConnectorType ] + [-EFSkipIPs ] + [-EFSkipLastIP ] + [-EFSkipMailGateway ] + [-EFTestMode ] + [-EFUsers ] + [-Enabled ] + [-RequireTls ] + [-RestrictDomainsToCertificate ] + [-RestrictDomainsToIPAddresses ] + [-ScanAndDropRecipients ] + [-SenderIPAddresses ] + [-TlsSenderCertificateName ] + [-TreatMessagesAsInternal ] + [-TrustedOrganizations ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Inbound connectors accept email messages from remote domains that require specific configuration options. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-InboundConnector -Name "Contoso Inbound Connector" -SenderDomains *.contoso.com -SenderIPAddresses 192.168.0.1/25 -RestrictDomainsToIPAddresses $true +``` + +This example creates the Inbound connector named Contoso Inbound Connector with the following properties: + +- It listens for incoming connections from the domain contoso.com and all subdomains. +- It only accepts mail from contoso.com, and from the IP range 192.168.0.1/25. It rejects mail from contoso.com if it originates from any other IP address. + +### Example 2 +```powershell +New-InboundConnector -Name "Contoso Inbound Secure Connector" -SenderDomains *.contoso.com -SenderIPAddresses 192.168.0.1/25 -RestrictDomainsToIPAddresses $true -RequireTLS $true -TlsSenderCertificateName *.contoso.com +``` + +This example creates the Inbound connector named Contoso Inbound Secure Connector and requires TLS transmission for all messages. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderDomains +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssociatedAcceptedDomains +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ClientHostNames +{{ Fill ClientHostNames Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CloudServicesMailEnabled +**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. + +Valid values are: + +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorSource +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. +- HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. +- Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. + +We recommended that you don't change this value. + +```yaml +Type: TenantConnectorSource +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorType +The ConnectorType parameter specifies the category for the source domains that the connector accepts messages for. Valid values are: + +- Partner: External partners or services. +- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors grant special rights to an email that matches the connector and additional requirements. For example: allowing relay through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows. + +```yaml +Type: TenantConnectorType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFSkipIPs +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.3.1/24. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFSkipLastIP +The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are: + +- $true: Only the last message source is skipped. +- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFSkipMailGateway +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFTestMode +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFUsers +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter enables or disables the connector. Valid values are: + +- $true: The connector is enabled. This is the default value. +- $false: The connector is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireTls +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 +- $false: Allow messages if they aren't sent over TLS. + +**Note**: This parameter applies only to Partner type connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictDomainsToCertificate +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. +- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value. + +**Note**: This parameter applies only to Partner type connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictDomainsToIPAddresses +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. +- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value. + +**Note**: This parameter applies only to Partner type connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScanAndDropRecipients +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderIPAddresses +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. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32. + +You can specify multiple IP addresses separated by commas. + +IPv6 addresses are not supported. + +**Note**: This parameter applies to Partner type connectors only if the value of the RestrictDomainsToIPAddresses parameter is $true. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TlsSenderCertificateName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TreatMessagesAsInternal +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. +- $false: Messages aren't considered internal. This is the default value. + +In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Microsoft 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter). + +**Note**: You can't set this parameter to the value $true if either of the following conditions is true: + +- The CloudServicesMailEnabled parameter is set to the value $true. +- The ConnectorType parameter value is not OnPremises. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrustedOrganizations +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/New-InboxRule.md b/exchange/exchange-ps/exchange/New-InboxRule.md similarity index 90% rename from exchange/exchange-ps/exchange/mailboxes/New-InboxRule.md rename to exchange/exchange-ps/exchange/New-InboxRule.md index 792a92fc02..a3b0fe0e83 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-InboxRule.md +++ b/exchange/exchange-ps/exchange/New-InboxRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-inboxrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-InboxRule @@ -19,7 +18,7 @@ Use the New-InboxRule cmdlet to create Inbox rules in mailboxes. Inbox rules pro You must have adequate permissions on the mailbox to create an Inbox rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,7 +38,6 @@ New-InboxRule [-Name] [-ExceptIfFlaggedForAction ] [-ExceptIfFrom ] [-ExceptIfFromAddressContainsWords ] - [-ExceptIfFromSubscription ] [-ExceptIfHasAttachment ] [-ExceptIfHasClassification ] [-ExceptIfHeaderContainsWords ] @@ -65,7 +63,6 @@ New-InboxRule [-Name] [-ForwardTo ] [-From ] [-FromAddressContainsWords ] - [-FromSubscription ] [-HasAttachment ] [-HasClassification ] [-HeaderContainsWords ] @@ -87,6 +84,7 @@ New-InboxRule [-Name] [-SendTextMessageNotificationTo ] [-SentOnlyToMe ] [-SentTo ] + [-SoftDeleteMessage ] [-StopProcessingRules ] [-SubjectContainsWords ] [-SubjectOrBodyContainsWords ] @@ -109,7 +107,8 @@ New-InboxRule -FromMessageId [-Force] [-FromSubscription ] [-Mailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -117,13 +116,13 @@ When you create, modify, remove, enable, or disable an Inbox rule in Exchange Po Parameters that are used for conditions also have corresponding exception parameters. When conditions specified in an exception are matched, the rule isn't applied to the message. Exception parameters begin with ExceptIf. For example, the exception parameter for SubjectOrBodyContainsWords is ExceptIfSubjectOrBodyContainsWords. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-InboxRule "CheckActionRequired" -MyNameInToBox $true -FlaggedForAction Any -MarkImportance "High" +New-InboxRule -Mailbox chris@contoso.com -Name "CheckActionRequired" -MyNameInToBox $true -FlaggedForAction Any -MarkImportance "High" ``` This example raises the message importance to High if the mailbox owner is in the To field. In addition, the message is flagged for action. @@ -131,7 +130,7 @@ This example raises the message importance to High if the mailbox owner is in th ## PARAMETERS ### -Name -The Name parameter specifies the name of the Inbox rule. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). +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 @@ -150,15 +149,12 @@ Accept wildcard characters: False 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 - - StoreObjectId When you use this parameter to create an Inbox rule, the following message properties are used in the rule: - Subject: The message subject is added to the SubjectContainsWords condition. - - From: The message sender is added to the From condition. - - To and Cc: Recipients in the To and Cc fields are added to the SentTo condition. ```yaml @@ -191,7 +187,7 @@ Accept wildcard characters: False ``` ### -AlwaysDeleteOutlookRulesBlob -The AlwaysDeleteOutlookRulesBlob parameter suppresses a warning that end users or administrators get if they use Outlook Web App or Windows PowerShell to modify Inbox rules. +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 @@ -228,51 +224,28 @@ Accept wildcard characters: False 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 - - Bills - - Document - - DocumentPlus - - Event - - Family - - File - - Flight - - FromContact - - Important - - LiveView - - Lodging - - MailingList - - Newsletter - - Photo - - Purchase - - RentalCar - - RestaurantReservation - - RetiredPromotion - - ShippingNotification - - Shopping - - SocialUpdate - - Travel - - Video You can specify multiple values separated by commas. @@ -293,7 +266,9 @@ Accept wildcard characters: False ### -BodyContainsWords The BodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the body of messages. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfBodyContainsWords. @@ -313,8 +288,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -336,23 +310,14 @@ The CopyToFolder parameter specifies an action for the Inbox rule that copies me For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Marketing` or `John:\Inbox\Reports`. @@ -374,7 +339,6 @@ Accept wildcard characters: False 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. - - $false: The action isn't used. ```yaml @@ -394,51 +358,28 @@ Accept wildcard characters: False 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 - - Bills - - Document - - DocumentPlus - - Event - - Family - - File - - Flight - - FromContact - - Important - - LiveView - - Lodging - - MailingList - - Newsletter - - Photo - - Purchase - - RentalCar - - RestaurantReservation - - RetiredPromotion - - ShippingNotification - - Shopping - - SocialUpdate - - Travel - - Video You can specify multiple values separated by commas. @@ -477,7 +418,9 @@ Accept wildcard characters: False ### -ExceptIfBodyContainsWords The ExceptIfBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the body of messages. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is BodyContainsWords. @@ -498,25 +441,15 @@ Accept wildcard characters: False The ExceptIfFlaggedForAction parameter specifies an exception for the Inbox rule that looks messages with the specified message flag. Valid values are: - Any - - Call - - DoNotForward - - FollowUp - - ForYourInformation - - Forward - - NoResponseNecessary - - Read - - Reply - - ReplyToAll - - Review The corresponding condition parameter to this exception is FlaggedForAction. @@ -535,21 +468,16 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom -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: For example: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding condition parameter to this exception is From. @@ -569,7 +497,9 @@ Accept wildcard characters: False ### -ExceptIfFromAddressContainsWords 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. -You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is FromAddressContainsWords. @@ -586,31 +516,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ExceptIfFromSubscription -This parameter is available only in the cloud-based service. - -The ExceptIfFromSubscription parameter specifies an exception for the Inbox rule that looks for messages received from subscriptions (for example, POP or IMAP subscriptions). You can identify the subscription by using the Get-Subscription cmdlet. - -The corresponding condition parameter to this exception is FromSubscription. - -```yaml -Type: AggregationSubscriptionIdentity[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ExceptIfHasAttachment 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is HasAttachment. @@ -649,7 +558,9 @@ Accept wildcard characters: False ### -ExceptIfHeaderContainsWords The HeaderContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the header fields of messages. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is HeaderContainsWords. @@ -670,25 +581,15 @@ Accept wildcard characters: False The ExceptIfMessageTypeMatches parameter specifies an exception for the Inbox rule that looks for messages of the specified type. Valid values are: - AutomaticReply - - AutomaticForward - - Encrypted - - Calendaring - - CalendaringResponse - - PermissionControlled - - Voicemail - - Signed - - ApprovalRequest - - ReadReceipt - - NonDeliveryReport The corresponding condition parameter to this exception is MessageTypeMatches. @@ -710,7 +611,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInCcBox. @@ -732,7 +632,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInToBox. @@ -754,7 +653,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInToOrCcBox. @@ -776,7 +674,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameNotInToBox. @@ -797,7 +694,7 @@ Accept wildcard characters: False ### -ExceptIfReceivedAfterDate 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". +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". The corresponding condition parameter to this exception is ReceivedAfterDate. @@ -817,7 +714,7 @@ Accept wildcard characters: False ### -ExceptIfReceivedBeforeDate 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". +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". The corresponding condition parameter to this exception is ReceivedBeforeDate. @@ -837,7 +734,7 @@ Accept wildcard characters: False ### -ExceptIfRecipientAddressContainsWords 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. +You can specify multiple values separated by commas. The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is RecipientAddressContainsWords. @@ -858,7 +755,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is SentOnlyToMe. @@ -880,18 +776,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding condition parameter to this exception is SentTo. @@ -911,7 +802,9 @@ Accept wildcard characters: False ### -ExceptIfSubjectContainsWords The ExceptIfSubjectContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field of messages. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is SubjectContainsWords. @@ -931,9 +824,11 @@ Accept wildcard characters: False ### -ExceptIfSubjectOrBodyContainsWords 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. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. -The corresponding condition parameter to this exception is ExceptIfSubjectOrBodyContainsWords. +The maximum length of this parameter is 255 characters. + +The corresponding condition parameter to this exception is SubjectOrBodyContainsWords. ```yaml Type: MultiValuedProperty @@ -952,9 +847,7 @@ Accept wildcard characters: False The ExceptIfWithImportance parameter specifies an exception for the Inbox rule that looks for messages with the specified importance level. Valid values are: - High - - Normal - - Low The corresponding condition parameter to this exception is WithImportance. @@ -978,13 +871,9 @@ The ExceptIfWithinSizeRangeMaximum parameter specifies part of an exception for When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1012,13 +901,9 @@ The ExceptIfWithinSizeRangeMinimum parameter specifies part of an exception for When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1044,11 +929,8 @@ Accept wildcard characters: False The ExceptIfWithSensitivity parameter specifies an exception for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are: - Normal - - Personal - - Private - - CompanyConfidential The corresponding condition parameter to this exception is WithSensitivity. @@ -1070,25 +952,15 @@ Accept wildcard characters: False The FlaggedForAction parameter specifies a condition for the Inbox rule that looks for messages with the specified message flag. Valid values are: - Any - - Call - - DoNotForward - - FollowUp - - ForYourInformation - - Forward - - NoResponseNecessary - - Read - - Reply - - ReplyToAll - - Review ```yaml @@ -1105,7 +977,7 @@ Accept wildcard characters: False ``` ### -Force -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. +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. @@ -1126,18 +998,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1156,18 +1023,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1186,18 +1048,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding exception parameter to this condition is ExceptIfFrom. @@ -1217,7 +1074,9 @@ Accept wildcard characters: False ### -FromAddressContainsWords 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. -You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfFromAddressContainsWords. @@ -1234,31 +1093,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -FromSubscription -This parameter is available only in the cloud-based service. - -The FromSubscription parameter specifies a condition for the Inbox rule that looks for messages received from subscriptions (for example, POP or IMAP subscriptions). You can identify the subscription by using the Get-Subscription cmdlet. - -The corresponding exception parameter to this condition is ExceptIfFromSubscription. - -```yaml -Type: AggregationSubscriptionIdentity[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -HasAttachment 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfHasAttachment. @@ -1297,7 +1135,9 @@ Accept wildcard characters: False ### -HeaderContainsWords The HeaderContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the header fields of messages. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfHeaderContainsWords. @@ -1318,23 +1158,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -1354,7 +1185,6 @@ Accept wildcard characters: False 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. - - $false: The action isn't used. ```yaml @@ -1374,9 +1204,7 @@ Accept wildcard characters: False The MarkImportance parameter specifies an action for the Inbox rule that marks messages with the specified importance flag. Valid values are: - Low - - Normal - - High ```yaml @@ -1396,25 +1224,15 @@ Accept wildcard characters: False The MessageTypeMatches parameter specifies a condition for the Inbox rule that looks for messages of the specified type. Valid values are: - AutomaticReply - - AutomaticForward - - Encrypted - - Calendaring - - CalendaringResponse - - PermissionControlled - - Voicemail - - Signed - - ApprovalRequest - - ReadReceipt - - NonDeliveryReport The corresponding exception parameter to this condition is ExceptIfMessageTypeMatches. @@ -1438,23 +1256,14 @@ The MoveToFolder parameter specifies an action for the Inbox rule that moves mes For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Marketing` or `John:\Inbox\Reports`. @@ -1476,7 +1285,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInCcBox. @@ -1498,7 +1306,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInToBox. @@ -1520,7 +1327,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInToOrCcBox. @@ -1542,7 +1348,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameNotInToBox. @@ -1564,7 +1369,6 @@ Accept wildcard characters: False 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. - - $false: The action isn't used. ```yaml @@ -1599,7 +1403,7 @@ Accept wildcard characters: False ### -ReceivedAfterDate 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". +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". The corresponding exception parameter to this condition is ExceptIfReceivedAfterDate. @@ -1619,7 +1423,7 @@ Accept wildcard characters: False ### -ReceivedBeforeDate 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". +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". The corresponding exception parameter to this condition is ExceptIfReceivedBeforeDate. @@ -1639,7 +1443,7 @@ Accept wildcard characters: False ### -RecipientAddressContainsWords 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. +You can specify multiple values separated by commas. The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfRecipientAddressContainsWords. @@ -1660,18 +1464,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1687,6 +1486,8 @@ Accept wildcard characters: False ``` ### -SendTextMessageNotificationTo +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. You can specify multiple values separated by commas. @@ -1695,7 +1496,7 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1708,7 +1509,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfSentOnlyToMe. @@ -1730,18 +1530,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding exception parameter to this condition is ExceptIfSentTo. @@ -1758,11 +1553,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SoftDeleteMessage +This parameter is available only in the cloud-based service. + +{{ Fill SoftDeleteMessage Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -StopProcessingRules 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. - - $false: The action isn't used (continue processing more rules after this one). ```yaml @@ -1781,7 +1593,9 @@ Accept wildcard characters: False ### -SubjectContainsWords The SubjectContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field of messages. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfSubjectContainsWords. @@ -1801,7 +1615,9 @@ Accept wildcard characters: False ### -SubjectOrBodyContainsWords 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. -If the phrase contains spaces, you need to enclose the value in quotation marks. You can specify multiple values separated by commas. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfSubjectOrBodyContainsWords. @@ -1838,9 +1654,7 @@ Accept wildcard characters: False The WithImportance parameter specifies a condition for the Inbox rule that looks for messages with the specified importance level. Valid values are: - High - - Normal - - Low The corresponding exception parameter to this condition is ExceptIfWithImportance. @@ -1864,13 +1678,9 @@ The WithinSizeRangeMaximum parameter specifies part of a condition for the Inbox When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1898,13 +1708,9 @@ The WithinSizeRangeMinimum parameter specifies part of a condition for the Inbox When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1930,11 +1736,8 @@ Accept wildcard characters: False The WithSensitivity parameter specifies a condition for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are: - Normal - - Personal - - Private - - CompanyConfidential The corresponding exception parameter to this condition is ExceptIfWithSensitivity. @@ -1957,12 +1760,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md new file mode 100644 index 0000000000..0e1826be8c --- /dev/null +++ b/exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md @@ -0,0 +1,293 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-InformationBarrierPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-InformationBarrierPolicy cmdlet to create information barrier policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### OrganizationSegmentAllowedFilter +``` +New-InformationBarrierPolicy [-Name] -AssignedSegment -SegmentAllowedFilter + [-Comment ] + [-Confirm] + [-Force] + [-ModerationAllowed ] + [-State ] + [-WhatIf] + [] +``` + +### OrganizationSegmentsAllowed +``` +New-InformationBarrierPolicy [-Name] -AssignedSegment -SegmentsAllowed + [-Comment ] + [-Confirm] + [-Force] + [-ModerationAllowed ] + [-WhatIf] + [] +``` + +### OrganizationSegmentsBlocked +``` +New-InformationBarrierPolicy [-Name] -AssignedSegment -SegmentsBlocked + [-Comment ] + [-Confirm] + [-Force] + [-ModerationAllowed ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Information barrier policies are not in effect until you set them to active status, and then apply the policies: + +- (If needed): [Block communications between segments](https://learn.microsoft.com/purview/information-barriers-policies#scenario-1-block-communications-between-segments). +- After all of your policies are defined: [Apply information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies#step-4-apply-ib-policies). + +For more information, see [Information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-InformationBarrierPolicy -Name "Sales-Research" -AssignedSegment "Sales" -SegmentsBlocked "Research" -State Inactive +``` + +This example creates an inactive policy named *Sales-Research* for a segment named *Sales*. When active and applied, this policy prevents people in *Sales* from communicating with people in the segment named *Research*. + +### Example 2 +```powershell +New-InformationBarrierPolicy -Name "Manufacturing-HR" -AssignedSegment "Manufacturing" -SegmentsAllowed "Manufacturing","HR" -State Inactive +``` + +This example creates an inactive policy named *Manufacturing-HR* for a segment named *Manufacturing*. When active and applied, this policy allows people in *Manufacturing* to communicate only with people in the segment named *HR*. (In this example, Manufacturing can't communicate with users who aren't in HR.) + +### Example 3 +```powershell +New-InformationBarrierPolicy -Name "Research-HRManufacturing" -AssignedSegment "Research" -SegmentsAllowed "Research","HR","Manufacturing" -State Inactive +``` + +This example creates a policy that allows the *Research* segment to communicate with only *HR* and *Manufacturing*. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssignedSegment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SegmentAllowedFilter +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: OrganizationSegmentAllowedFilter +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SegmentsAllowed +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"). + +You can't use this parameter with the SegmentsBlocked parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: OrganizationSegmentsAllowed +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SegmentsBlocked +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"). + +You can't use this parameter with the SegmentsAllowed parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: OrganizationSegmentsBlocked +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch doesn't work on this cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModerationAllowed +{{ Fill ModerationAllowed Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The State parameter specifies whether the information barrier policy is active or inactive. Valid values are: + +- Active +- Inactive (This is the default value.) + +```yaml +Type: EopInformationBarrierPolicyState +Parameter Sets: (All) +Aliases: +Accepted values: Inactive, Active +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/New-IntraOrganizationConnector.md b/exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/federation-and-hybrid/New-IntraOrganizationConnector.md rename to exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md index 1e233f999e..4e22683783 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/New-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/new-intraorganizationconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-IntraOrganizationConnector @@ -17,14 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-IntraOrganizationConnector cmdlet to create an Intra-Organization connector between two on-premises Exchange forests in an organization, between an Exchange on-premises organization and an Exchange Online organization, or between two Exchange Online organizations. This connector enables feature availability and service connectivity across the organizations using a common connector and connection endpoints. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-IntraOrganizationConnector [-Name] -DiscoveryEndpoint - -TargetAddressDomains [-Confirm] [-DomainController ] [-Enabled ] - [-WhatIf] [] +New-IntraOrganizationConnector [-Name] -DiscoveryEndpoint -TargetAddressDomains + [-Confirm] + [-DomainController ] + [-Enabled ] + [-TargetSharingEpr ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -32,7 +35,7 @@ The New-IntraOrganizationConnector cmdlet is used to create a connection for fea For hybrid deployments between on-premises Exchange and Exchange Online organizations, the New-IntraOrganizationConnector cmdlet is used by the Hybrid Configuration wizard. Typically, the Intra-Organization connector is configured when the hybrid deployment is initially created by the wizard. We strongly recommend that you use the Hybrid Configuration wizard to create the Intra-Organization connector when configuring a hybrid deployment with an Exchange Online organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,33 +48,33 @@ This example creates an Intra-Organization connector named "MainCloudConnector" ## PARAMETERS -### -DiscoveryEndpoint -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. +### -Name +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: Uri +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies a friendly name for the Intra-Organization connector. If the value contains spaces, enclose the value in double quotation marks. +### -DiscoveryEndpoint +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: String +Type: Uri Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -98,8 +101,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -151,6 +153,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -TargetSharingEpr +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. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -172,12 +192,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-JournalRule.md b/exchange/exchange-ps/exchange/New-JournalRule.md similarity index 90% rename from exchange/exchange-ps/exchange/policy-and-compliance/New-JournalRule.md rename to exchange/exchange-ps/exchange/New-JournalRule.md index c59e496f3a..2812bcf0ef 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-JournalRule.md +++ b/exchange/exchange-ps/exchange/New-JournalRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-journalrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-JournalRule @@ -17,23 +16,27 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-JournalRule cmdlet to create a journal rule in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-JournalRule -Name -JournalEmailAddress [-Confirm] - [-DomainController ] [-Enabled ] +New-JournalRule -Name -JournalEmailAddress + [-Confirm] + [-DomainController ] + [-Enabled ] [-Recipient ] - [-Scope ] [-WhatIf] [] + [-Scope ] + [-WhatIf] + [] ``` ## DESCRIPTION The New-JournalRule cmdlet creates a journal rule in your organization. -By default, new journal rules are disabled unless the Enabled parameter is set to $true. For more information about how to enable a new journal rule that was created in a disabled state, see [Enable-JournalRule](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/enable-journalrule). +By default, new journal rules are disabled unless the Enabled parameter is set to $true. For more information about how to enable a new journal rule that was created in a disabled state, see [Enable-JournalRule](https://learn.microsoft.com/powershell/module/exchange/enable-journalrule). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,18 +66,13 @@ Accept wildcard characters: False ``` ### -JournalEmailAddress -The JournalEmailAddress parameter specifies a recipient object to which journal reports are sent. You ean use any value that uniquely identifies the recipient. For example: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -93,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -147,6 +144,8 @@ Accept wildcard characters: False ### -Recipient 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. + ```yaml Type: SmtpAddress Parameter Sets: (All) @@ -164,9 +163,7 @@ Accept wildcard characters: False 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. - - Internal: Internal rules process email messages sent and received by recipients in your organization. - - External: External rules process email messages sent to recipients or from senders outside your organization. ```yaml @@ -203,12 +200,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-Label.md b/exchange/exchange-ps/exchange/New-Label.md new file mode 100644 index 0000000000..ccfa3a9d5e --- /dev/null +++ b/exchange/exchange-ps/exchange/New-Label.md @@ -0,0 +1,1675 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-Label + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-Label cmdlet to create sensitivity labels in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-Label [-Name] -DisplayName -Tooltip + [-AdvancedSettings ] + [-ApplyContentMarkingFooterAlignment ] + [-ApplyContentMarkingFooterEnabled ] + [-ApplyContentMarkingFooterFontColor ] + [-ApplyContentMarkingFooterFontName ] + [-ApplyContentMarkingFooterFontSize ] + [-ApplyContentMarkingFooterMargin ] + [-ApplyContentMarkingFooterText ] + [-ApplyContentMarkingHeaderAlignment ] + [-ApplyContentMarkingHeaderEnabled ] + [-ApplyContentMarkingHeaderFontColor ] + [-ApplyContentMarkingHeaderFontName ] + [-ApplyContentMarkingHeaderFontSize ] + [-ApplyContentMarkingHeaderMargin ] + [-ApplyContentMarkingHeaderText ] + [-ApplyDynamicWatermarkingEnabled ] + [-ApplyWaterMarkingEnabled ] + [-ApplyWaterMarkingFontColor ] + [-ApplyWaterMarkingFontName ] + [-ApplyWaterMarkingFontSize ] + [-ApplyWaterMarkingLayout ] + [-ApplyWaterMarkingText ] + [-ColumnAssetCondition ] + [-Comment ] + [-Conditions ] + [-Confirm] + [-ContentType ] + [-DefaultContentLabel ] + [-DynamicWatermarkDisplay ] + [-EncryptionAipTemplateScopes ] + [-EncryptionContentExpiredOnDateInDaysOrNever ] + [-EncryptionDoNotForward ] + [-EncryptionDoubleKeyEncryptionUrl ] + [-EncryptionEnabled ] + [-EncryptionEncryptOnly ] + [-EncryptionLinkedTemplateId ] + [-EncryptionOfflineAccessDays ] + [-EncryptionPromptUser ] + [-EncryptionProtectionType ] + [-EncryptionRightsDefinitions ] + [-EncryptionRightsUrl ] + [-EncryptionTemplateId ] + [-Identity ] + [-LabelActions ] + [-LocaleSettings ] + [-MigrationId ] + [-ParentId ] + [-SchematizedDataCondition ] + [-Setting ] + [-Settings ] + [-SiteAndGroupProtectionAllowAccessToGuestUsers ] + [-SiteAndGroupProtectionAllowEmailFromGuestUsers ] + [-SiteAndGroupProtectionAllowFullAccess ] + [-SiteAndGroupProtectionAllowLimitedAccess ] + [-SiteAndGroupProtectionBlockAccess ] + [-SiteAndGroupProtectionEnabled ] + [-SiteAndGroupProtectionLevel ] + [-SiteAndGroupProtectionPrivacy ] + [-SiteExternalSharingControlType ] + [-TeamsAllowedPresenters ] + [-TeamsAllowMeetingChat ] + [-TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch ] + [-TeamsBypassLobbyForDialInUsers ] + [-TeamsChannelProtectionEnabled ] + [-TeamsChannelSharedWithExternalTenants ] + [-TeamsChannelSharedWithPrivateTeamsOnly ] + [-TeamsChannelSharedWithSameLabelOnly ] + [-TeamsCopyRestrictionEnforced ] + [-TeamsEndToEndEncryptionEnabled ] + [-TeamsLobbyBypassScope ] + [-TeamsLobbyRestrictionEnforced ] + [-TeamsPresentersRestrictionEnforced ] + [-TeamsProtectionEnabled ] + [-TeamsRecordAutomatically ] + [-TeamsVideoWatermark ] + [-TeamsWhoCanRecord ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-Label -DisplayName "My New label" -Name "New Label" +``` + +This example create a new label named "New Label" with a display name "My New Label". + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tooltip +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdvancedSettings +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. + +Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings). + +Supported settings for built-in labeling: + +- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting impacts services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `New-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). + +- **Color**: Specifies a label color as a hex triplet code for the red, green, and blue (RGB) components of the color. Example: `New-Label -DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{color="#40e0d0"}`. For more information, see [Configuring custom colors by using PowerShell](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configuring-custom-colors-by-using-powershell). + +- **DefaultSharingScope**: Specifies the default sharing link type for a site when the label scope includes **Groups & sites**, and the default sharing link type for a document when the label scope includes **Files & emails**. Available values are SpecificPeople, Organization, and Anyone. Example: `New-Label DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{DefaultSharingScope="SpecificPeople"}`. For more information, see [Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive](https://learn.microsoft.com/purview/sensitivity-labels-default-sharing-link). + +- **DefaultShareLinkPermission**: Specifies the permissions for the sharing link for a site when the label scope includes **Groups & sites**, and the permissions for the sharing link for a document when the label scope includes **Files & emails**. Available values are View and Edit. Example: `New-Label DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{DefaultShareLinkPermission="Edit"}`. For more information, see [Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive](https://learn.microsoft.com/purview/sensitivity-labels-default-sharing-link). + +- **DefaultShareLinkToExistingAccess**: Specifies whether to override *DefaultSharingScope* and *DefaultShareLinkPermission* to instead set the default sharing link type to people with existing access with their existing permissions. Example: `New-Label DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{DefaultShareLinkToExistingAccess="True"}`. For more information, see [Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive](https://learn.microsoft.com/purview/sensitivity-labels-default-sharing-link). + +- **DefaultSubLabelId**: Specifies a default sublabel to be applied automatically when a user selects a parent label in Office apps. Example: `New-Label -DisplayName "Confidential" -Name "Confidential" -Tooltip "Confidential data that requires protection, which allows all employees full permissions. Data owners can track and revoke content." -AdvancedSettings @{DefaultSubLabelId="8faca7b8-8d20-48a3-8ea2-0f96310a848e"}`. For more information, see [Specify a default sublabel for a parent label](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#specify-a-default-sublabel-for-a-parent-label). + +- **MembersCanShare**: For a container label, specifies how members can share for a SharePoint site. Available values are MemberShareAll, MemberShareFileAndFolder, and MemberShareNone. Example: `New-Label -DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{MembersCanShare="MemberShareFileAndFolder"}`. For more information, see [Configure site sharing permissions by using PowerShell advanced settings](https://learn.microsoft.com/purview/sensitivity-labels-teams-groups-sites#configure-site-sharing-permissions-by-using-powershell-advanced-settings). + +- **SMimeEncrypt**: Specifies S/MIME encryption for Outlook. Available values are True, and False (the default). Example: `New-Label DisplayName "Confidential" -Name "Confidential" -Tooltip "Sensitive business data that could cause damage to the business if shared with unauthorized people." -AdvancedSettings @{SMimeEncrypt="True"}`. For more information, see [Configure a label to apply S/MIME protection in Outlook](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configure-a-label-to-apply-smime-protection-in-outlook). + +- **SMimeSign**: Specifies S/MIME digital signature for Outlook. Available values are True, and False (the default). Example: `New-Label DisplayName "Confidential" -Name "Confidential" -Tooltip "Sensitive business data that could cause damage to the business if shared with unauthorized people." -AdvancedSettings @{SMimeSign="True"}`. For more information, see [Configure a label to apply S/MIME protection in Outlook](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configure-a-label-to-apply-smime-protection-in-outlook). + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterAlignment +The ApplyContentMarkingFooterAlignment parameter specifies the footer alignment. Valid values are: + +- Left +- Center +- Right + +This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterEnabled +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. +- $false: The Apply Content Marking Footer action is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterFontColor +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterFontName +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. + +This parameter is supported only by the Azure Information Protection unified labeling client and not by Office apps and services that support built-in labeling. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterFontSize +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterMargin +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. + +**Note**: In Microsoft Word and PowerPoint, the specified value is used as a bottom margin and left margin or right margin for left-aligned or right-aligned content marks. A minimum value of 15 points is required. Word also adds a constant offset of 5 points to the left margin for left-aligned content marks, or to the right margin for right-aligned content marks. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderAlignment +The ApplyContentMarkingHeaderAlignment parameter specifies the header alignment. Valid values are: + +- Left +- Center +- Right + +This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderEnabled +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. +- $false: The Apply Content Marking Header action is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderFontColor +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderFontName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderFontSize +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderMargin +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. + +**Note**: In Microsoft Word and PowerPoint, the specified value is used as a top margin and left margin or right margin for left-aligned or right-aligned content marks. A minimum value of 15 points is required. Word also adds a constant offset of 5 points to the left margin for left-aligned content marks, or to the right margin for right-aligned content marks. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyDynamicWatermarkingEnabled +**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: + +- $true: Enables dynamic watermarking for a specific label. +- $false: Disables dynamic watermarking for a specific label. + +You set the watermark text with the DynamicWatermarkDisplay parameter. For more information about using dynamic watermarks for supported apps, see [Dynamic watermarks](https://learn.microsoft.com/purview/encryption-sensitivity-labels#dynamic-watermarks). + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingEnabled +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. +- $false: The Apply Watermarking Header action is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingFontColor +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingFontName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingFontSize +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingLayout +The ApplyWaterMarkingLayout parameter specifies the watermark alignment. Valid values are: + +- Horizontal +- Diagonal + +This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+WaterMarkingLayout +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ColumnAssetCondition +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Conditions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MulitValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentType +The ContentType parameter specifies where the sensitivity label can be applied. Valid values are: + +- File +- Email +- Site +- UnifiedGroup +- PurviewAssets +- Teamwork +- SchematizedData + +Values can be combined, for example: "File, Email, PurviewAssets". + +```yaml +Type: MipLabelContentType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultContentLabel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DynamicWatermarkDisplay +**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: + +- `${Consumer.PrincipalName}`: Required. The value is the user principal name (UPN) of the user. +- `${Device.DateTime}`: Optional. The value is current date/time of the device used to view the document. + +This parameter is meaningful only when the ApplyDynamicWatermarkingEnabled parameter value is $true. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionAipTemplateScopes +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionContentExpiredOnDateInDaysOrNever +The EncryptionContentExpiredOnDateInDaysOrNever parameter specifies when the encrypted content expires. Valid values are: + +- An integer (number of days) +- The value `Never` + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionDoNotForward +The EncryptionDoNotForward parameter specifies whether the Do Not Forward template is applied. Valid values are: + +- $true: The Do Not Forward template is applied. +- $false: The Do Not Forward template is not applied. + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionDoubleKeyEncryptionUrl +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. + +You can't remove the URL after the label has been created; you can only modify it. + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionEnabled +The EncryptionEnabled parameter specifies whether encryption in enabled. Valid values are: + +- $true: Encryption is enabled. +- $false: Encryption is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionEncryptOnly +The EncryptionEncryptOnly parameter specifies whether the encrypt-only template is applied. Valid values are: + +- $true: The encrypt-only template is applied. +- $false: The encrypt-only template is not applied. + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionLinkedTemplateId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionOfflineAccessDays +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionPromptUser +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. +- $false: The label is not set with user defined permissions in Word, Excel and PowerPoint. + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false, and when the EncryptionProtectionType parameter value is UserDefined. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionProtectionType +The EncryptionProtectionType parameter specifies the protection type for encryption. Valid values are: + +- Template +- RemoveProtection +- UserDefined + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+SupportedProtectionType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionRightsDefinitions +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. + +```yaml +Type: EncryptionRightsDefinitionsParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionRightsUrl +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionTemplateId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LabelActions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocaleSettings +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"}]}` +- Label Tooltips: `{"localeKey":"Tooltip","Settings":[{"Key":"en-us","Value":"English Tooltip"},{"Key":"de-de",Value":"Deutscher Tooltip"},{"Key":"es-es","Value":"Tooltip Español"}]}` + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrationId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParentId +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SchematizedDataCondition +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Setting +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Settings +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowAccessToGuestUsers +The SiteAndGroupProtectionAllowAccessToGuestUsers parameter enables or disables access to guest users. Valid values are: + +- $true: Guest access is enabled. +- $false: Guest access is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowEmailFromGuestUsers +The SiteAndGroupProtectionAllowEmailFromGuestUsers parameter enables or disables email from guest users. Valid values are: + +- $true: Email from guest users is enabled. +- $false: Email from guest users is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowFullAccess +The SiteAndGroupProtectionAllowFullAccess parameter enables or disables full access. Valid values are: + +- $true: Full access is enabled. +- $false: Full access is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowLimitedAccess +The SiteAndGroupProtectionAllowLimitedAccess parameter enables or disables limited access. Valid values are: + +- $true: Limited access is enabled. +- $false: Limited access is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionBlockAccess +The SiteAndGroupProtectionBlockAccess parameter blocks access. Valid values are: + +- $true: Access is blocked. +- $false: Access is allowed. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionEnabled +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. +- $false: The Site and Group Protection action is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionLevel +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SiteAndGroupProtectionLevelParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionPrivacy +The SiteAndGroupProtectionPrivacy parameter specifies the privacy level for the labe. Valid values are: + +- Public +- Private + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+GroupProtectionPrivacy +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteExternalSharingControlType +The SiteExternalSharingControlType parameter specifies the external user sharing setting for the label. Valid values are: + +- ExternalUserAndGuestSharing +- ExternalUserSharingOnly +- ExistingExternalUserSharingOnly +- Disabled + +These correspond to the following settings through the admin center: + +- Anyone +- New and Existing Guests +- Existing Guests +- Only people in your organization + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.SiteExternalSharingControlType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAllowedPresenters +The TeamsAllowedPresenters parameter controls who can present in Teams meetings. Valid values are: + +- Everyone +- Organization +- Organizer +- RoleIsPresenter +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.AllowedPresenters +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAllowMeetingChat +The TeamsAllowMeetingChat parameter controls whether chat is available in Teams meetings. Valid values are: + +- Enabled +- Disabled +- Limited: Chat is available only for the duration of the call. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.MeetingChatMode +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch +{{ Fill TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsBypassLobbyForDialInUsers +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. +- $false: Dial in users don't bypass the lobby when joining Teams meetings. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelProtectionEnabled +{{ Fill TeamsChannelProtectionEnabled Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelSharedWithExternalTenants +{{ Fill TeamsChannelSharedWithExternalTenants Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelSharedWithPrivateTeamsOnly +{{ Fill TeamsChannelSharedWithPrivateTeamsOnly Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelSharedWithSameLabelOnly +{{ Fill TeamsChannelSharedWithSameLabelOnly Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsCopyRestrictionEnforced +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. +- $false: Chat messages can't be copied to the clipboard. + +The value $null (blank) allows users to configure this setting in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsEndToEndEncryptionEnabled +The TeamsEndToEndEncryptionEnabled parameter controls video stream encryption in Teams meetings. Valid values are: + +- $true: Video stream encryption is enabled. +- $false: Video stream encryption is not enabled. +- $null (blank): Users configure this setting themselves in the Teams app. + +The value $null (blank) allows users to configure this setting in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsLobbyBypassScope +The TeamsLobbyBypassScope parameter controls who bypasses the lobby when joining Teams meetings. Valid values are: + +- Everyone +- Invited +- Organization +- OrganizationAndFederated +- OrganizationExcludingGuests +- Organizer +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.LobbyBypassScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsLobbyRestrictionEnforced +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. +- $false: Users don't bypass the lobby when joining Teams meetings. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsPresentersRestrictionEnforced +The TeamsPresentersRestrictionEnforced parameter controls whether presenter restrictions are enabled in Teams meetings. Valid values are: + +- $true: Presenter restrictions are enabled in Teams meetings. +- $false: Presenter restrictions aren't enabled in Teams meetings. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsProtectionEnabled +The TeamsProtectionEnabled parameter controls whether Teams protection is enabled in Teams meetings. Valid values are: + +- $true: Teams protection is enabled in Teams meetings. +- $false: Teams protection is not enabled in Teams meetings. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsRecordAutomatically +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. +- $false: Teams meetings are not automatically recorded. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsVideoWatermark +The TeamsVideoWatermark parameter controls whether a watermark is shown in Teams meetings. Valid values are: + +- None +- EnabledForContentSharing +- EnabledForVideo +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WaterMarkProtectionValues +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsWhoCanRecord +The TeamsWhoCanRecord parameter controls who can record Teams meetings. Valid values are: + +- Organizer +- Coorganizers +- Presenters +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WhoCanRecordOptions +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-LabelPolicy.md b/exchange/exchange-ps/exchange/New-LabelPolicy.md new file mode 100644 index 0000000000..ce59ac07c5 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-LabelPolicy.md @@ -0,0 +1,486 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-LabelPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-LabelPolicy cmdlet to create sensitivity label policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-LabelPolicy -Name -Labels + [-AdvancedSettings ] + [-Comment ] + [-Confirm] + [-ExchangeLocation ] + [-ExchangeLocationException ] + [-Force] + [-MigrationId ] + [-ModernGroupLocation ] + [-ModernGroupLocationException ] + [-OneDriveLocation ] + [-OneDriveLocationException ] + [-PolicyRBACScopes ] + [-PublicFolderLocation ] + [-Setting ] + [-Settings ] + [-SharePointLocation ] + [-SharePointLocationException ] + [-SkypeLocation ] + [-SkypeLocationException ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-LabelPolicy -Name "Research and Development" -Labels "R and D","R and D Management" +``` + +This example creates the sensitivity label policy named Research and Development that contains sensitivity labels named R and D and R and D Management. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Labels +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 +- Distinguished name (DN) +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdvancedSettings +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. + +Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings). + +Supported settings for built-in labeling: + +- **AttachmentAction**: Unlabeled emails inherit the highest priority label from file attachments. Set the value to **Automatic** (to automatically apply the label) or **Recommended** (as a recommended prompt to the user. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{AttachmentAction="Automatic"}`. For more information about this configuration choice, see [Configure label inheritance from email attachments](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configure-label-inheritance-from-email-attachments). + +- **EnableAudit**: Prevent Office apps from sending sensitivity label data to Microsoft 365 auditing solutions. Supported apps: Word, Excel, and PowerPoint on Windows (version 2201+), macOS (version 16.57+), iOS (version 2.57+), and Android (version 16.0.14827+); Outlook on Windows (version 2201+), Outlook on the web, and rolling out to macOS, iOS, and Android. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{EnableAudit="False"}`. + +- **EnableRevokeGuiSupport**: Remove the Track & Revoke button from the sensitivity menu in Office clients. Supported apps: Word, Excel, and PowerPoint on Windows (version 2406+). Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{EnableRevokeGuiSupport="False"}`. For more information about this configuration choice, see [Track and revoke document access](https://learn.microsoft.com/purview/track-and-revoke-admin). + +- **DisableMandatoryInOutlook**: Outlook apps that support this setting exempt Outlook messages from mandatory labeling. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{DisableMandatoryInOutlook="True"}`. For more information about this configuration choice, see [Outlook-specific options for default label and mandatory labeling](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#outlook-specific-options-for-default-label-and-mandatory-labeling). + +- **DisableShowSensitiveContent**: For Office apps that highlight the sensitive content that caused a label to be recommended, turn off these highlights and corresponding indications about the sensitive content. For more information, see [Sensitivity labels are automatically applied or recommended for your files and emails in Office](https://support.microsoft.com/office/sensitivity-labels-are-automatically-applied-or-recommended-for-your-files-and-emails-in-office-622e0d9c-f38c-470a-bcdb-9e90b24d71a1). Supported apps: Word for Windows (version 2311+). Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{DisableShowSensitiveContent="True"}` + +- **OutlookDefaultLabel**: Outlook apps that support this setting apply a default label, or no label. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{OutlookDefaultLabel="None"}`. For more information about this configuration choice, see [Outlook-specific options for default label and mandatory labeling](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#outlook-specific-options-for-default-label-and-mandatory-labeling). + +- **TeamworkMandatory**: Outlook and Teams apps that support this setting can enable or disable mandatory labeling for meetings. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{TeamworkMandatory="True"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings). + +- **teamworkdefaultlabelid**: Outlook and Teams apps that support this setting apply a default label, or no label for meetings. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{teamworkdefaultlabelid="General"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings). + +- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) will be displayed. Users can't revert this setting in the app. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` + +Additionally, for Power BI: + +- **powerbimandatory**: Mandatory labeling for Power BI. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{powerbimandatory="true"}`. For more information about this configuration choice, see [Mandatory label policy for Power BI](https://learn.microsoft.com/power-bi/admin/service-security-sensitivity-label-mandatory-label-policy). + +- **powerbidefaultlabelid**: Default label for Power BI content. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{powerbidefaultlabelid="General"}`. For more information about this configuration choice, see [Default label policy for Power BI](https://learn.microsoft.com/power-bi/admin/service-security-sensitivity-label-default-label-policy). + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrationId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModernGroupLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModernGroupLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Setting +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Settings +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkypeLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkypeLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/exchange/New-M365DataAtRestEncryptionPolicy.md new file mode 100644 index 0000000000..1182270b7a --- /dev/null +++ b/exchange/exchange-ps/exchange/New-M365DataAtRestEncryptionPolicy.md @@ -0,0 +1,178 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-M365DataAtRestEncryptionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-M365DataAtRestEncryptionPolicy cmdlet to create a new Microsoft 365 data-at-rest encryption policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-M365DataAtRestEncryptionPolicy [-Name] -AzureKeyIDs + [-Confirm] + [-Description ] + [-DomainController ] + [-Enabled ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the New-M365DataAtRestEncryptionPolicy cmdlet to create a new Microsoft 365 data-at-rest encryption policy for multi-workload usage. For more information, see [Service encryption with Microsoft Purview Customer Key](https://learn.microsoft.com/purview/customer-key-overview). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-M365DataAtRestEncryptionPolicy -Name "Default_Policy" -AzureKeyIDs "https://contosowestusvault01.vault.azure.net/keys/Key_01","https://contosoeastusvault01.vault.azure.net/keys/Key_02" -Description "Tenant default policy" +``` + +This example creates a Microsoft 365 data-at-rest multi-workload encryption policy named Default_Policy with the specified Azure Key Vault keys and description for all users in your tenant. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AzureKeyIDs +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter specifies an optional description for the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/New-MailContact.md b/exchange/exchange-ps/exchange/New-MailContact.md similarity index 90% rename from exchange/exchange-ps/exchange/users-and-groups/New-MailContact.md rename to exchange/exchange-ps/exchange/New-MailContact.md index 379e8d6e6b..fcccb631e5 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/New-MailContact.md +++ b/exchange/exchange-ps/exchange/New-MailContact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/new-mailcontact +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-MailContact @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MailContact cmdlet to create mail contacts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -37,15 +36,15 @@ New-MailContact -Name -ExternalEmailAddress [-ModeratedBy ] [-ModerationEnabled ] [-OrganizationalUnit ] - [-OverrideRecipientQuotas] [-PrimarySmtpAddress ] [-SendModerationNotifications ] [-UsePreferMessageFormat ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,53 +57,57 @@ This example creates a new mail contact named Chris Ashton. ## PARAMETERS -### -ExternalEmailAddress -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. +### -Name +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 ("). -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. +This value is also used for the DisplayName property if you don't use the DisplayName parameter. ```yaml -Type: ProxyAddress +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 +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 ("). +### -ExternalEmailAddress +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. -This value is also used for the DisplayName property if you don't use the DisplayName parameter. +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: String +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: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -130,23 +133,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -165,8 +159,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -270,17 +263,13 @@ Accept wildcard characters: False 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) - - UuEncode - - AppleSingle - - AppleDouble The MacAttachmentFormat and MessageFormat parameters are interdependent: - MessageFormat is Text: MacAttachmentFormat can be BinHex or UuEncode. - - MessageFormat is Mime: MacAttachmentFormat can be BinHex, AppleSingle, or AppleDouble. ```yaml @@ -300,15 +289,12 @@ Accept wildcard characters: False The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text - - Html - - TextAndHtml (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. ```yaml @@ -328,15 +314,12 @@ Accept wildcard characters: False The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text - - Html - - TextAndHtml (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. ```yaml @@ -356,18 +339,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -388,7 +366,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -412,11 +389,8 @@ The OrganizationalUnit parameter specifies the location in Active Directory wher 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -432,22 +406,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OverrideRecipientQuotas -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, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -PrimarySmtpAddress This parameter is available only in on-premises Exchange. @@ -474,9 +432,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -498,7 +454,6 @@ Accept wildcard characters: False 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. - - $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. ```yaml @@ -535,12 +490,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/New-MailMessage.md b/exchange/exchange-ps/exchange/New-MailMessage.md similarity index 77% rename from exchange/exchange-ps/exchange/mailboxes/New-MailMessage.md rename to exchange/exchange-ps/exchange/New-MailMessage.md index 1b2cef91a7..c016c6ef01 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-MailMessage.md +++ b/exchange/exchange-ps/exchange/New-MailMessage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-mailmessage +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MailMessage @@ -17,19 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MailMessage cmdlet to create an email message for the specified user mailbox and place the email message in the Drafts folder of the user's mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-MailMessage [[-Body] ] -Mailbox [-BodyFormat ] - [-Confirm] [-DomainController ] [-Subject ] [-WhatIf] [] +New-MailMessage + [[-Body] ] + [-BodyFormat ] + [-Confirm] + [-DomainController ] + [-Subject ] + [-WhatIf] + [] ``` ## DESCRIPTION If the cmdlet is run without specifying the Subject or Body parameters, an empty email message is placed in the user's Drafts folder. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -38,7 +43,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-MailMessage -Subject "Delivery Report" -Body "Click here to view this report" -Mailbox tony ``` -In Exchange Server 2010, this example creates an message in the Drafts folder of Tony's mailbox, with the subject and body specified by the Subject and Body parameters. The message body is rendered in plain text because no format for the message body is specified. +In Exchange Server 2010, this example creates a message in the Drafts folder of Tony's mailbox, with the subject and body specified by the Subject and Body parameters. The message body is rendered in plain text because no format for the message body is specified. ### Example 2 ```powershell @@ -52,7 +57,7 @@ This example creates an email message in the Drafts folder with the subject and New-MailMessage -Mailbox tony@contoso.com ``` -In Exchange Server 2010, this example creates an empty message in the Drafts folder of Tony's mailbox because no subject or message body is specified. +In Exchange Server 2010, this example creates an empty message in the Drafts folder of Tony's mailbox because no subject or message body is specified. ### Example 4 ```powershell @@ -66,7 +71,7 @@ This example creates an empty email message in the Drafts folder because no subj New-MailMessage -Subject "Delivery Information" -Body "Click here to see details" -Mailbox tony -BodyFormat Html ``` -In Exchange Server 2010, this example creates an message in the Drafts folder of Tony's mailbox with the subject and body specified by the Subject and Body parameters. The message body is rendered in HTML format. +In Exchange Server 2010, this example creates a message in the Drafts folder of Tony's mailbox with the subject and body specified by the Subject and Body parameters. The message body is rendered in HTML format. ### Example 6 ```powershell @@ -77,44 +82,6 @@ This example creates an email message in the Drafts folder with the subject and ## PARAMETERS -### -Mailbox -This parameter is available or functional only in Exchange Server 2010. - -The Mailbox parameter specifies the target mailbox where the message is created. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Body The Body parameter specifies the content of the body section of the new email message. @@ -150,8 +117,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -222,12 +188,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/New-MailUser.md b/exchange/exchange-ps/exchange/New-MailUser.md similarity index 83% rename from exchange/exchange-ps/exchange/users-and-groups/New-MailUser.md rename to exchange/exchange-ps/exchange/New-MailUser.md index 7c0a5b12a4..27ea5d62e4 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/New-MailUser.md +++ b/exchange/exchange-ps/exchange/New-MailUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/new-mailuser +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-MailUser @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MailUser cmdlet to create mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -46,7 +45,8 @@ New-MailUser [-Name] -ExternalEmailAddress [-SamAccountName ] [-SendModerationNotifications ] [-UsePreferMessageFormat ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### EnabledUser @@ -74,17 +74,16 @@ New-MailUser [-Name] -ExternalEmailAddress -Password ] [-SendModerationNotifications ] [-UsePreferMessageFormat ] - [-WhatIf] [] + [-WhatIf] + [] ``` -### MicrosoftOnlineServicesID +### EnableRoomMailboxAccount ``` -New-MailUser [-Name] -MicrosoftOnlineServicesID -Password [-ExternalEmailAddress ] +New-MailUser [-Name] [-MicrosoftOnlineServicesID ] [-Alias ] - [-ArbitrationMailbox ] [-Confirm] [-DisplayName ] - [-DomainController ] [-FirstName ] [-ImmutableId ] [-Initials ] @@ -95,15 +94,15 @@ New-MailUser [-Name] -MicrosoftOnlineServicesID -Passwo [-OrganizationalUnit ] [-PrimarySmtpAddress ] [-RemotePowerShellEnabled ] - [-ResetPasswordOnNextLogon ] - [-SamAccountName ] [-SendModerationNotifications ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### FederatedUser ``` -New-MailUser [-Name] -FederatedIdentity [-ExternalEmailAddress ] +New-MailUser [-Name] -FederatedIdentity + [-ExternalEmailAddress ] [-Alias ] [-ArbitrationMailbox ] [-Confirm] @@ -122,7 +121,51 @@ New-MailUser [-Name] -FederatedIdentity [-ExternalEmailAddress [-ResetPasswordOnNextLogon ] [-SamAccountName ] [-SendModerationNotifications ] - [-WhatIf] [] + [-WhatIf] + [] +``` + +### HVEAccount +``` +New-MailUser [-Name] -Password [-HVEAccount] + [-Alias ] + [-Confirm] + [-DisplayName ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-MailboxRegion ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OrganizationalUnit ] + [-PrimarySmtpAddress ] + [-RemotePowerShellEnabled ] + [-SendModerationNotifications ] + [-WhatIf] + [] +``` + +### LOBAppAccount +``` +New-MailUser [-Name] -Password [-LOBAppAccount] + [-Alias ] + [-Confirm] + [-DisplayName ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-MailboxRegion ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OrganizationalUnit ] + [-PrimarySmtpAddress ] + [-ProgressAction ] + [-RemotePowerShellEnabled ] + [-SendModerationNotifications ] + [-WhatIf] + [] ``` ### MicrosoftOnlineServicesFederatedUser @@ -146,15 +189,19 @@ New-MailUser [-Name] -FederatedIdentity -MicrosoftOnlineServic [-ResetPasswordOnNextLogon ] [-SamAccountName ] [-SendModerationNotifications ] - [-WhatIf] [] + [-WhatIf] + [] ``` -### EnableRoomMailboxAccount +### MicrosoftOnlineServicesID ``` -New-MailUser [-Name] [-MicrosoftOnlineServicesID ] +New-MailUser [-Name] -MicrosoftOnlineServicesID -Password + [-ExternalEmailAddress ] [-Alias ] + [-ArbitrationMailbox ] [-Confirm] [-DisplayName ] + [-DomainController ] [-FirstName ] [-ImmutableId ] [-Initials ] @@ -163,30 +210,27 @@ New-MailUser [-Name] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-OrganizationalUnit ] + [-PrimarySmtpAddress ] [-RemotePowerShellEnabled ] + [-ResetPasswordOnNextLogon ] + [-SamAccountName ] [-SendModerationNotifications ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-MailUser -Name "Ed Meadows" -ExternalEmailAddress ed@tailspintoys.com -MicrosoftOnlineServicesID ed@tailspintoys -Password (ConvertTo-SecureString -String 'P@ssw0rd1' -AsPlainText -Force) +New-MailUser -Name "Ed Meadows" -ExternalEmailAddress ed@tailspintoys.com -MicrosoftOnlineServicesID ed@contoso.com -Password (Get-Credential).password ``` This example creates a new mail user for Ed Meadows in the contoso.com cloud-based organization. The mail user gives Ed an account and email address in the contoso.com domain, but messages sent to Ed are delivered to his tailspintoys.com email address. -### Example 2 -```powershell -$password = Read-Host "Enter password" -AsSecureString; New-MailUser -Name "Ed Meadows" -ExternalEmailAddress ed@tailspintoys.com -UserPrincipalName ed@contoso.com -Password $password -``` - -This example is similar to the first, except contoso.com is now an on-premises Exchange organization, and you use a separate command to enter the password so it isn't stored in clear text. - ## PARAMETERS ### -Name @@ -227,7 +271,7 @@ Accept wildcard characters: False ```yaml Type: ProxyAddress -Parameter Sets: MicrosoftOnlineServicesID, FederatedUser +Parameter Sets: FederatedUser, MicrosoftOnlineServicesID Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection @@ -288,11 +332,15 @@ Accept wildcard characters: False ### -Password The Password parameter specifies the password for the user's account. -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. ```yaml Type: SecureString -Parameter Sets: EnabledUser, MicrosoftOnlineServicesID +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 @@ -322,16 +370,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -357,23 +409,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -392,8 +435,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -511,21 +553,53 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -HVEAccount +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. + +```yaml +Type: SwitchParameter +Parameter Sets: HVEAccount +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Position: Named +Default value: None +Required: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LOBAppAccount +This parameter is available only in the cloud-based service. + +{{ Fill LOBAppAccount Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: LOBAppAccount +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MacAttachmentFormat 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) - - UuEncode - - AppleSingle - - AppleDouble The MacAttachmentFormat and MessageFormat parameters are interdependent: - MessageFormat is Text: MacAttachmentFormat can be BinHex or UuEncode. - - MessageFormat is Mime: MacAttachmentFormat can be BinHex, AppleSingle, or AppleDouble. ```yaml @@ -550,7 +624,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -563,15 +637,12 @@ Accept wildcard characters: False The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text - - Html - - TextAndHtml (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. ```yaml @@ -591,13 +662,11 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text - - Mime (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. Therefore, if you want to change the MessageFormat parameter from Mime to Text, you must also change the MessageBodyFormat parameter to Text. @@ -619,18 +688,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -651,7 +715,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -675,11 +738,8 @@ The OrganizationalUnit parameter specifies the location in Active Directory wher 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -696,7 +756,7 @@ Accept wildcard characters: False ``` ### -PrimarySmtpAddress -This parameter is available only in on-premises Exchange. +This parameter is functional only in on-premises Exchange. The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. @@ -706,9 +766,9 @@ If you use the PrimarySmtpAddress parameter to specify the primary email address ```yaml Type: SmtpAddress -Parameter Sets: DisabledUser, EnabledUser, FederatedUser, MicrosoftOnlineServicesID +Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -718,11 +778,14 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled -The RemotePowerShellEnabled parameter specifies whether the user can connect to Exchange using remote PowerShell. Remote PowerShell is required to open the Exchange Management Shell on Exchange servers, or to use Windows PowerShell open and import a remote PowerShell session to Exchange. Access to remote PowerShell is required even if you're trying to open the Exchange Management Shell on the local Exchange server. Valid values are: +The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: -- $true: The user can use remote PowerShell. This is the default value. +- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. +- $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. -- $false: The user can't use remote PowerShell. +Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. + +A user's experience in any of these management interfaces is still controlled by the role-based access control (RBAC) permissions that are assigned to them. ```yaml Type: Boolean @@ -743,7 +806,6 @@ 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: - $true: The user is required to change their password the next time they log on. - - $false: The user isn't required to change their password the next time they log on. This is the default value. ```yaml @@ -762,7 +824,7 @@ Accept wildcard characters: False ### -SamAccountName 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 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. +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 @@ -781,9 +843,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -805,7 +865,6 @@ Accept wildcard characters: False 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. - - $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. ```yaml @@ -842,12 +901,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/New-Mailbox.md b/exchange/exchange-ps/exchange/New-Mailbox.md similarity index 85% rename from exchange/exchange-ps/exchange/mailboxes/New-Mailbox.md rename to exchange/exchange-ps/exchange/New-Mailbox.md index ac2999a7dd..8a4bb79a06 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-Mailbox.md +++ b/exchange/exchange-ps/exchange/New-Mailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-mailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-Mailbox @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-Mailbox cmdlet to create mailboxes and user accounts at the same time. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -56,7 +55,8 @@ New-Mailbox [-Name] -Password -UserPrincipalName ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MicrosoftOnlineServicesID @@ -95,12 +95,13 @@ New-Mailbox [-Name] -Password -MicrosoftOnlineServicesID [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Arbitration ``` -New-Mailbox [-Name] [-Arbitration] [-Password ] [-UserPrincipalName ] +New-Mailbox [-Name] [-Arbitration] [-Password ] [-UserPrincipalName ] [-ActiveSyncMailboxPolicy ] [-AddressBookPolicy ] [-Alias ] @@ -118,6 +119,7 @@ New-Mailbox [-Name] [-Arbitration] [-Password ] [-UserPri [-MailboxRegion ] [-OrganizationalUnit ] [-PrimarySmtpAddress ] + [-ProxyEmailAddress ] [-RemotePowerShellEnabled ] [-ResetPasswordOnNextLogon ] [-RetentionPolicy ] @@ -126,7 +128,8 @@ New-Mailbox [-Name] [-Arbitration] [-Password ] [-UserPri [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AuditLog @@ -155,7 +158,8 @@ New-Mailbox [-Name] -UserPrincipalName [-AuditLog] [-SamAccountName ] [-SharingPolicy ] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AuxAuditLog @@ -184,7 +188,8 @@ New-Mailbox [-Name] [-AuxAuditLog] [-UserPrincipalName ] [-SamAccountName ] [-SharingPolicy ] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### DisabledUser @@ -223,7 +228,8 @@ New-Mailbox [-Name] [-AccountDisabled] [-Password ] [-Use [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Discovery @@ -256,12 +262,13 @@ New-Mailbox [-Name] [-Discovery] [-Password ] [-UserPrinc [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### EnableRoomMailboxAccount ``` -New-Mailbox [-Name] -EnableRoomMailboxAccount [-MicrosoftOnlineServicesID [-Room] [-RoomMailboxPassword ] [-UserPrincipalName ] +New-Mailbox [-Name] -EnableRoomMailboxAccount [-MicrosoftOnlineServicesID ] [-Room] [-RoomMailboxPassword ] [-UserPrincipalName ] [-ActiveSyncMailboxPolicy ] [-AddressBookPolicy ] [-Alias ] @@ -287,7 +294,8 @@ New-Mailbox [-Name] -EnableRoomMailboxAccount [-MicrosoftOnli [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Equipment @@ -322,7 +330,8 @@ New-Mailbox [-Name] [-Equipment] [-Password ] [-UserPrinc [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### FederatedUser @@ -349,7 +358,8 @@ New-Mailbox [-Name] -FederatedIdentity [-RemovedMailbox ] [-RoleAssignmentPolicy ] [-TargetAllMDBs] - [-WhatIf] [] + [-WhatIf] + [] ``` ### InactiveMailbox @@ -387,7 +397,8 @@ New-Mailbox [-Name] -InactiveMailbox [-Password ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Linked @@ -425,12 +436,19 @@ New-Mailbox [-Name] -LinkedDomainController -LinkedMasterAccou [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### LinkedRoomMailbox ``` -New-Mailbox [-Name] -LinkedDomainController -LinkedMasterAccount [-LinkedCredential ] [-LinkedRoom] [-Office ] [-Password ] [-Phone ] [-UserPrincipalName ] +New-Mailbox [-Name] -LinkedDomainController -LinkedMasterAccount + [-LinkedCredential ] + [-LinkedRoom] + [-Office ] + [-Password ] + [-Phone ] + [-UserPrincipalName ] [-ActiveSyncMailboxPolicy ] [-AddressBookPolicy ] [-Alias ] @@ -463,7 +481,8 @@ New-Mailbox [-Name] -LinkedDomainController -LinkedMasterAccou [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MicrosoftOnlineServicesFederatedUser @@ -489,7 +508,8 @@ New-Mailbox [-Name] -FederatedIdentity -MicrosoftOnlineService [-ResetPasswordOnNextLogon ] [-RoleAssignmentPolicy ] [-TargetAllMDBs] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Migration @@ -520,7 +540,8 @@ New-Mailbox [-Name] [-Arbitration] [-Migration] [-Password ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### PublicFolder @@ -551,7 +572,8 @@ New-Mailbox [-Name] [-PublicFolder] [-HoldForMigration] [-IsExcludedFro [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RemoteArchive @@ -590,7 +612,8 @@ New-Mailbox [-Name] -ArchiveDomain -Password ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RemovedMailbox @@ -628,7 +651,8 @@ New-Mailbox [-Name] -RemovedMailbox [-Passw [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Room @@ -667,15 +691,17 @@ New-Mailbox [-Name] [-Password ] [-ResourceCapacity ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` -### Scheduling +### Shared ``` -New-Mailbox [-Name] [-Password ] [-UserPrincipalName ] [-Scheduling] +New-Mailbox [-Name] [-Password ] [-Shared] [-UserPrincipalName ] [-ActiveSyncMailboxPolicy ] [-AddressBookPolicy ] [-Alias ] + [-ArbitrationMailbox ] [-Archive] [-ArchiveDatabase ] [-Confirm] @@ -688,6 +714,8 @@ New-Mailbox [-Name] [-Password ] [-UserPrincipalName ] [-LastName ] [-MailboxRegion ] + [-ModeratedBy ] + [-ModerationEnabled ] [-OrganizationalUnit ] [-PrimarySmtpAddress ] [-RemotePowerShellEnabled ] @@ -695,21 +723,22 @@ New-Mailbox [-Name] [-Password ] [-UserPrincipalName ] [-RoleAssignmentPolicy ] [-SamAccountName ] + [-SendModerationNotifications ] [-SharingPolicy ] [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] + [-WhatIf] + [] ``` -### Shared +### SupervisoryReviewPolicyMailbox ``` -New-Mailbox [-Name] [-Password ] [-Shared] [-UserPrincipalName ] +New-Mailbox [-Name] [-SupervisoryReviewPolicy] [-ActiveSyncMailboxPolicy ] [-AddressBookPolicy ] [-Alias ] - [-ArbitrationMailbox ] - [-Archive] [-ArchiveDatabase ] + [-Archive] [-Confirm] [-Database ] [-DisplayName ] @@ -719,9 +748,6 @@ New-Mailbox [-Name] [-Password ] [-Shared] [-UserPrincipa [-ImmutableId ] [-Initials ] [-LastName ] - [-MailboxRegion ] - [-ModeratedBy ] - [-ModerationEnabled ] [-OrganizationalUnit ] [-PrimarySmtpAddress ] [-RemotePowerShellEnabled ] @@ -729,21 +755,25 @@ New-Mailbox [-Name] [-Password ] [-Shared] [-UserPrincipa [-RetentionPolicy ] [-RoleAssignmentPolicy ] [-SamAccountName ] - [-SendModerationNotifications ] [-SharingPolicy ] - [-TargetAllMDBs] [-ThrottlingPolicy ] - [-WhatIf] [] -``` + [-UserPrincipalName ] + [-WhatIf] + [] + ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. ## EXAMPLES ### Example 1 ```powershell -$password = Read-Host "Enter password" -AsSecureString; New-Mailbox -UserPrincipalName chris@contoso.com -Alias chris -Database "Mailbox Database 1" -Name ChrisAshton -OrganizationalUnit Users -Password $password -FirstName Chris -LastName Ashton -DisplayName "Chris Ashton" -ResetPasswordOnNextLogon $true +$password = Read-Host "Enter password" -AsSecureString + +New-Mailbox -UserPrincipalName chris@contoso.com -Alias chris -Database "Mailbox Database 1" -Name ChrisAshton -OrganizationalUnit Users -Password $password -FirstName Chris -LastName Ashton -DisplayName "Chris Ashton" -ResetPasswordOnNextLogon $true ``` This example creates a user Chris Ashton in Active Directory and creates a mailbox for the user. The mailbox is located on Mailbox Database 1. The password must be reset at the next logon. To set the initial value of the password, this example creates a variable ($password), prompts you to enter a password, and assigns that password to the variable as a SecureString object. @@ -757,14 +787,18 @@ This example creates a user in Active Directory and a resource mailbox for a con ### Example 3 ```powershell -New-Mailbox -UserPrincipalName confroom1010@contoso.com -Alias confroom1010 -Name "Conference Room 1010" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String P@ssw0rd -AsPlainText -Force) +New-Mailbox -UserPrincipalName confroom1010@contoso.com -Alias confroom1010 -Name "Conference Room 1010" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (Get-Credential).password ``` -This example creates an enabled user account in Active Directory and a room mailbox for a conference room in an on-premises Exchange organization. The RoomMailboxPassword parameter specifies the password for the user account. +This example creates an enabled user account in Active Directory and a room mailbox for a conference room in an on-premises Exchange organization. The RoomMailboxPassword parameter prompts you to enter the password for the user account. ### Example 4 ```powershell -New-Mailbox -Shared -Name "Sales Department" -DisplayName "Sales Department" -Alias Sales; Set-Mailbox -Identity Sales -GrantSendOnBehalfTo MarketingSG; Add-MailboxPermission -Identity Sales -User MarketingSG -AccessRights FullAccess -InheritanceType All +New-Mailbox -Shared -Name "Sales Department" -DisplayName "Sales Department" -Alias Sales + +Set-Mailbox -Identity Sales -GrantSendOnBehalfTo MarketingSG + +Add-MailboxPermission -Identity Sales -User MarketingSG -AccessRights FullAccess -InheritanceType All ``` This example creates the shared mailbox "Sales Department" and grants Full Access and Send on Behalf permissions for the security group "MarketingSG". Users who are members of the security group will be granted the permissions to the mailbox. @@ -776,6 +810,8 @@ This example assumes that you've already created a mail-enabled security group n ### -Name 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). + ```yaml Type: String Parameter Sets: (All) @@ -867,7 +903,7 @@ Accept wildcard characters: False ### -Discovery 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://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). +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). ```yaml Type: SwitchParameter @@ -883,17 +919,18 @@ Accept wildcard characters: False ``` ### -EnableRoomMailboxAccount +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: -- $true: The disabled account that's associated with the room mailbox is enabled. You also need to use the RoomMailboxPassword with this value. This allows the account to log on to the room mailbox. +- $true: The disabled account that's associated with the room mailbox is enabled. You also need to use the RoomMailboxPassword with this value. The account is able to log in and access the room mailbox or other resources. +- $false: The account that's associated with the room mailbox is disabled. The account is not able to log in and access the room mailbox or other resources. In on-premises Exchange, this is the default value. -- $false: The account that's associated with the room mailbox is disabled. You can't use the account to logon to the room mailbox. This is the default value. +You need to enable the account for features like the Skype for Business Room System or Microsoft Teams Rooms. You need to use this parameter with the Room switch. -Typically, the account that's associated with a room mailbox is disabled. However, you need to enable the account for features like the Skype for Business Room System or Microsoft Teams Rooms. - -In Exchange Online, a room mailbox with an associated enabled account doesn't require a license. +A room mailbox in Exchange Online is created with associated an account that has a random, unknown password. This account is active and visible in Microsoft Graph PowerShell and the Microsoft 365 admin center just like a regular user account, but it consumes no licenses. To prevent this account from being able to log in after you create the mailbox, use the AccountEnabled parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. ```yaml Type: Boolean @@ -953,7 +990,7 @@ The InactiveMailbox parameter specifies the inactive mailbox that you want to re Type: MailboxIdParameter Parameter Sets: InactiveMailbox Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: True Position: Named @@ -996,21 +1033,20 @@ Accept wildcard characters: False ``` ### -LinkedMasterAccount +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: - Name - - Distinguished name (DN) - - Canonical DN - - GUID ```yaml Type: UserIdParameter Parameter Sets: Linked, LinkedRoomMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -1042,7 +1078,7 @@ Accept wildcard characters: False ### -MicrosoftOnlineServicesID 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. +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 @@ -1089,7 +1125,11 @@ Accept wildcard characters: False ### -Password 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. -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. ```yaml Type: SecureString @@ -1106,7 +1146,7 @@ Accept wildcard characters: False ```yaml Type: SecureString -Parameter Sets: Arbitration, DisabledUser, Discovery, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration RemovedMailbox, Room, Scheduling, Shared +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 @@ -1155,25 +1195,14 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: RemovedMailboxIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, FederatedUser, MicrosoftOnlineServicesFederatedUser, RemoteArchive, RemovedMailbox -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Room 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). -When you use this switch, a logon-disabled account is created with the room mailbox, which prevents users from signing in to the mailbox. When you use the EnableRoomMailboxAccount and RoomMailboxPassword parameters, you can mail-enable the associated account. +When you use this switch in on-premises Exchange, a disabled account is created with the room mailbox. The account can't be used to sign in to the mailbox or anywhere in the organization. To enable the associated account, use the EnableRoomMailboxAccount and RoomMailboxPassword parameters. + +When you use this switch in Exchange Online, an account with a random, unknown password is created for the room mailbox. If the password is known or changed, the account can be used to log in to the mailbox or anywhere in the organization. To prevent this account from being able to log in after you create the room mailbox, use the AccountEnabled parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. ```yaml Type: SwitchParameter @@ -1209,7 +1238,9 @@ Accept wildcard characters: False ### -UserPrincipalName 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 \@\. Typically, the \ value is the domain where the user account resides. +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. + +In the cloud-based service, use the MicrosoftOnlineServicesID parameter instead. ```yaml Type: String @@ -1226,7 +1257,7 @@ Accept wildcard characters: False ```yaml Type: String -Parameter Sets: AuxAuditLog, DisabledUser,Discovery, EnableRoomMailboxAccount, Equipment, Linked, LinkedRoomMailbox, Migration, Room, Scheduling, Shared +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 @@ -1241,9 +1272,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID If you don't use this parameter, the default mobile device mailbox policy is used. @@ -1267,16 +1296,14 @@ 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: - Name - - Distinguished name (DN) - - GUID -For more information about address book policies, see [Address book policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies). +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). ```yaml Type: AddressBookMailboxPolicyIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -1288,16 +1315,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -1323,23 +1354,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -1377,14 +1399,12 @@ 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: - Name - - Distinguished name (DN) - - GUID ```yaml Type: DatabaseIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -1442,8 +1462,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -1465,16 +1484,14 @@ 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: - Name - - Distinguished name (DN) - - GUID Use the Get-MailboxDatabase cmdlet to see the available mailbox databases. ```yaml Type: DatabaseIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -1510,7 +1527,7 @@ The DomainController parameter specifies the domain controller that's used by th ```yaml Type: Fqdn -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -1538,7 +1555,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -1644,7 +1663,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -1665,16 +1684,12 @@ 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: - Name - - Alias - - Display name - - Distinguished name (DN) - - GUID -A mailbox plan specifies the permissions and features that are available to a mailbox. In Office 365, mailbox plans correspond to the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. +A mailbox plan specifies the permissions and features that are available to a mailbox. In Exchange Online, mailbox plans correspond to the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can see the available mailbox plans by using the Get-MailboxPlan cmdlet. @@ -1694,11 +1709,15 @@ Accept wildcard characters: False ### -MailboxRegion This parameter is available only in the cloud-based service. -This parameter is reserved for internal Microsoft use. +The MailboxRegion parameter specifies the geo location for the mailbox in multi-geo environments. + +To see the list of configured geo locations in Microsoft 365 Multi-Geo, run the following command: `Get-OrganizationConfig | Select -ExpandProperty AllowedMailboxRegions | Format-Table`. To view your central geo location, run the following command: `Get-OrganizationConfig | Select DefaultMailboxRegion`. + + For more information, see [Administering Exchange Online mailboxes in a multi-geo environment](https://learn.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo). ```yaml Type: String -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared Aliases: Applicable: Exchange Online @@ -1710,13 +1729,13 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicy -This parameter is available or functional only in 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. ```yaml Type: MailboxPolicyIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -1728,15 +1747,17 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicyAllowed -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. -The ManagedFolderMailboxPolicyAllowed parameter 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. When a managed folder mailbox policy is assigned to a mailbox using the ManagedFolderMailboxPolicy parameter, the warning appears by default unless the ManagedFolderMailboxPolicyAllowed parameter is used. +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. + +When a managed folder mailbox policy is assigned to a mailbox using the ManagedFolderMailboxPolicy parameter, the warning appears by default unless the ManagedFolderMailboxPolicyAllowed switch is used. Outlook 2003 Service Pack 3 clients are supported but are provided limited functionality for MRM. ```yaml Type: SwitchParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -1751,18 +1772,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -1783,7 +1799,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -1823,11 +1838,8 @@ The OrganizationalUnit parameter specifies the location in Active Directory wher 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 - - Canonical name - - Distinguished name (DN) - - GUID ```yaml @@ -1877,6 +1889,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ProxyEmailAddress +This parameter is available only in the cloud-based service. + +{{ Fill ProxyEmailAddress Description }} + +```yaml +Type: Object +Parameter Sets: Arbitration +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RemoteArchive This parameter is available only in on-premises Exchange. @@ -1896,13 +1926,12 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled -The RemotePowerShellEnabled parameter specifies whether the user has access to remote PowerShell. Valid values are: +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. - - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. -Access to remote PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. +Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. A user's experience in any of these management interfaces is still controlled by the role-based access control (RBAC) permissions that are assigned to them. @@ -1923,7 +1952,6 @@ Accept wildcard characters: False 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. - - $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value. ```yaml @@ -1961,9 +1989,7 @@ 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: - Name - - Distinguished Name (DN) - - GUID Retention policies consist of tags that are applied to mailbox folders and mail items to determine the period of time that the items should be retained. @@ -1974,7 +2000,7 @@ If you don't use this parameter, the retention policy named Default MRM Policy i ```yaml Type: MailboxPolicyIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -1989,14 +2015,12 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID -In Office 365, if you don't use this parameter, the default role assignment policy named Default Role Assignment Policy is automatically applied to the mailbox. In on-premises Exchange, no role assignment policy is automatically applied to the mailbox. +In Exchange Online PowerShell, if you don't use this parameter, the default role assignment policy named Default Role Assignment Policy is automatically applied to the mailbox. In on-premises Exchange, no role assignment policy is automatically applied to the mailbox. -Use the Get-RoleAssignmentPolicy cmdlet to see the available role assignment policies. For more information about assignment policies, see [Understanding management role assignment policies](https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). +Use the Get-RoleAssignmentPolicy cmdlet to see the available role assignment policies. For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). ```yaml Type: MailboxPolicyIdParameter @@ -2012,15 +2036,25 @@ Accept wildcard characters: False ``` ### -RoomMailboxPassword -Use the RoomMailboxPassword parameter to configure the password for a room mailbox that has a logon-enabled account (the EnableRoomMailboxAccount parameter is set to the value $true.) +This parameter is functional only in on-premises Exchange. -To use this parameter, you need to be a member of one of the following role groups: +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). -- Office 365: The Organization Management role group via the Mail Recipients, Reset Password, and User Options roles, the Help Desk role group via the Reset Password and User Options roles, or the Recipient Management role group via the Mail Recipients and Reset Password roles. +To use this parameter in on-premises Exchange, you need to be a member of one of the following role groups: -- On-premises Exchange: The Organization Management role group via the Mail Recipients and User Options roles, the Recipient Management role group via the Mail Recipients role, or the Help Desk role group via the User Options role. The Reset Password role also allows you to use this parameter, but it isn't assigned to any role groups by default. +- The Organization Management role group via the Mail Recipients and User Options roles. +- The Recipient Management role group via the Mail Recipients role. +- The Help Desk role group via the User Options role. -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +The Reset Password role also allows you to use this parameter, but it isn't assigned to any role groups by default. + +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +To configure the password for a room mailbox account in Exchange Online, use [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. ```yaml Type: SecureString @@ -2038,11 +2072,11 @@ Accept wildcard characters: False ### -SamAccountName 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 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. +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: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -2053,31 +2087,11 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Scheduling -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: Scheduling -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -SendModerationNotifications 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -2101,9 +2115,7 @@ 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: - Name - - Distinguished name (DN) - - GUID Use the Get-SharingPolicy cmdlet to see the available sharing policies. @@ -2112,7 +2124,7 @@ If you don't use this parameter, the sharing policy named Default Sharing Policy ```yaml Type: SharingPolicyIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -2123,6 +2135,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SupervisoryReviewPolicy +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: SupervisoryReviewPolicyMailbox +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -TargetAllMDBs This parameter is available only in the cloud-based service. @@ -2130,7 +2160,7 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared Aliases: Applicable: Exchange Online @@ -2147,9 +2177,7 @@ 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: - Name - - Distinguished name (DN) - - GUID Use the Get-ThrottlingPolicy cmdlet to see the available throttling policies. @@ -2158,7 +2186,7 @@ By default, no throttling policy is applied to the mailbox. ```yaml Type: ThrottlingPolicyIdParameter -Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Scheduling, Shared +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 @@ -2190,12 +2218,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-MailboxAuditLogSearch.md b/exchange/exchange-ps/exchange/New-MailboxAuditLogSearch.md similarity index 92% rename from exchange/exchange-ps/exchange/policy-and-compliance-audit/New-MailboxAuditLogSearch.md rename to exchange/exchange-ps/exchange/New-MailboxAuditLogSearch.md index 10e9bd0785..38f9329045 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-MailboxAuditLogSearch.md +++ b/exchange/exchange-ps/exchange/New-MailboxAuditLogSearch.md @@ -1,23 +1,25 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/new-mailboxauditlogsearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MailboxAuditLogSearch ## SYNOPSIS +> [!NOTE] +> This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the New-MailboxAuditLogSearch cmdlet to search mailbox audit logs and have search results sent via email to specified recipients. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,15 +35,16 @@ New-MailboxAuditLogSearch -EndDate -StartDate -StatusM [-Name ] [-Operations ] [-ShowDetails] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The New-MailboxAuditLogSearch cmdlet performs an asynchronous search of mailbox audit logs for the specified mailboxes and sends the search results by email to the specified recipients. The body of the email message contains search metadata such as search parameters and the time when the search request was submitted. The results are attached in an .xml file. -To search mailbox audit logs for a single mailbox and have the results displayed in the Exchange Management Shell window, use the Search-MailboxAuditLog cmdlet instead. To learn more about mailbox audit logging, see [Mailbox audit logging in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/mailbox-audit-logging/mailbox-audit-logging). +To search mailbox audit logs for a single mailbox and have the results displayed in the Exchange Management Shell window, use the Search-MailboxAuditLog cmdlet instead. To learn more about mailbox audit logging, see [Mailbox audit logging in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mailbox-audit-logging/mailbox-audit-logging). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -64,7 +67,7 @@ This example returns entries from the mailbox audit logs of all users in organiz ### -EndDate 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". +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". ```yaml Type: ExDateTime @@ -82,7 +85,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: ExDateTime @@ -116,8 +119,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -174,7 +176,7 @@ Accept wildcard characters: False ### -GroupMailbox This parameter is available only in the cloud-based service. -The GroupMailbox switch is required to include Office 365 groups in the search. You don't need to specify a value with this switch. +The GroupMailbox switch is required to include Microsoft 365 Groups in the search. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -193,7 +195,6 @@ Accept wildcard characters: False The HasAttachments parameter filters the search by messages that have attachments. Valid values are: - $true: Only messages with attachments are included in the search. - - $false: Messages with and without attachments are included in the search. ```yaml @@ -213,11 +214,8 @@ Accept wildcard characters: False The LogonTypes parameter specifies the type of logons. Valid values are: - Admin: Audit log entries for mailbox access by administrator logons are returned. - - Delegate: Audit log entries for mailbox access by delegates are returned, including access by users with Full Mailbox Access permission. - - External: For Exchange Online mailboxes, audit log entries for mailbox access by Microsoft datacenter administrators are returned. - - Owner: Audit log entries for mailbox access by the primary mailbox owner are returned. This value requires the ShowDetails switch. You can enter multiple values separated by commas. @@ -238,7 +236,7 @@ Accept wildcard characters: False ### -Mailboxes 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: "\","\",..."\". +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"`. If you don't specify a value, mailbox audit logs for all mailboxes in the organization are returned. @@ -275,27 +273,16 @@ Accept wildcard characters: False The Operations parameter filters the search results by the operations that are logged by mailbox audit logging. Valid values are: - Copy - - Create - - FolderBind - - HardDelete - - MailboxLogin - - MessageBind - - Move - - MoveToDeletedItems - - SendAs - - SendOnBehalf - - SoftDelete - - Update You can enter multiple values separated by commas. @@ -350,12 +337,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxDatabase.md b/exchange/exchange-ps/exchange/New-MailboxDatabase.md similarity index 89% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxDatabase.md rename to exchange/exchange-ps/exchange/New-MailboxDatabase.md index a28213de79..a16092d137 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxDatabase.md +++ b/exchange/exchange-ps/exchange/New-MailboxDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/new-mailboxdatabase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-MailboxDatabase @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-MailboxDatabase cmdlet to create a mailbox database, or a recovery database. Each database you create must have a unique name in the organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -35,31 +34,34 @@ New-MailboxDatabase [-Name] -Server [-EdbFilePath ] [-LogFolderPath ] [-SkipDatabaseLogFolderCreation] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Recovery ``` -New-MailboxDatabase [[-Name] ] -Server [-Recovery] +New-MailboxDatabase [[-Name] ] -Server + [-Recovery] [-Confirm] [-DomainController ] [-EdbFilePath ] [-LogFolderPath ] [-SkipDatabaseLogFolderCreation] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-MailboxDatabase -Name "DB1" -EdbFilePath D:\ExchangeDatabases\DB1\DB1.edb +New-MailboxDatabase -Server Server1 -Name "DB1" -EdbFilePath D:\ExchangeDatabases\DB1\DB1.edb ``` -This example creates the mailbox database DB1. This example also uses a non-default location for the database file. +This example creates the mailbox database DB1 on the Mailbox server named Server1. This example also uses a non-default location for the database file. ## PARAMETERS @@ -112,11 +114,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -151,8 +150,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -185,7 +183,7 @@ Accept wildcard characters: False ``` ### -EdbFilePath -The EdbFilePath parameter specifies the path to the database files. The default value is %programfiles%\\Microsoft\\Exchange Server\\V15\\Mailbox\\\.edb. +The EdbFilePath parameter specifies the path to the database files. The default location is `%ExchangeInstallPath%Mailbox\\.edb`. ```yaml Type: EdbFilePath @@ -201,7 +199,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromInitialProvisioning -The IsExcludedFromInitialProvisioning parameter specifies that this database is temporarily not considered by the mailbox provisioning load balancer. If the IsExcludedFromInitialProvisioning parameter is enabled, new mailboxes aren't added automatically to this database. +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. ```yaml Type: SwitchParameter @@ -249,7 +249,7 @@ Accept wildcard characters: False ``` ### -LogFolderPath -The LogFolderPath parameter specifies the folder location for log files. +The LogFolderPath parameter specifies the folder location for log files.The default location is `%ExchangeInstallPath%Mailbox\` ```yaml Type: NonRootLocalLongFullPath @@ -284,9 +284,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID ```yaml @@ -339,12 +337,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/New-MailboxExportRequest.md b/exchange/exchange-ps/exchange/New-MailboxExportRequest.md similarity index 87% rename from exchange/exchange-ps/exchange/mailboxes/New-MailboxExportRequest.md rename to exchange/exchange-ps/exchange/New-MailboxExportRequest.md index 81b56df9b7..56a97e1c20 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-MailboxExportRequest.md +++ b/exchange/exchange-ps/exchange/New-MailboxExportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-mailboxexportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-MailboxExportRequest @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the New-MailboxExportRequest cmdlet to begin the process of exporting contents of a primary mailbox or archive to a .pst file. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -118,14 +117,13 @@ New-MailboxExportRequest [-Mailbox] -ComplianceStor ``` ## DESCRIPTION -You can create more than one mailbox export request per mailbox, and each mailbox export request must have a unique name. Microsoft Exchange automatically generates up to 10 unique names for a mailbox export request. However, to create more than 10 export requests for a mailbox, you need to specify a unique name when creating the export request. You can remove existing export requests with the Remove-MailboxExportRequest cmdlet before starting a new request with the default request name \\\MailboxExportX (where X = 0-9). +You can create more than one mailbox export request per mailbox, and each mailbox export request must have a unique name. Microsoft Exchange automatically generates up to 10 unique names for a mailbox export request. However, to create more than 10 export requests for a mailbox, you need to specify a unique name when creating the export request. You can remove existing export requests with the Remove-MailboxExportRequest cmdlet before starting a new request with the default request name `\MailboxExportX` (where X = 0-9). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). 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: - To import PST files from the share: Read permission - - To save exported PST files to the share: Read/Write permission. If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. @@ -162,46 +160,6 @@ This example exports all messages from Kweku's Inbox to the .pst file InPlaceHol ## PARAMETERS -### -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilePath -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: - -- To import PST files from the share: Read permission - -- To save exported PST files to the share: Read/Write permission. - -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. - -```yaml -Type: LongPath -Parameter Sets: Mailbox, MailboxExportRequest -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Mailbox The Mailbox parameter specifies the source mailbox where the contents are being exported from. @@ -210,23 +168,14 @@ In Exchange 2016 CU7 or later, this parameter is the type MailboxLocationIdParam In Exchange 2016 CU6 or earlier, this parameter is the type MailboxOrMailUserIdParameter, so you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -255,6 +204,45 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FilePath +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: + +- To import PST files from the share: Read permission +- To save exported PST files to the share: Read/Write permission. + +If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. + +```yaml +Type: LongPath +Parameter Sets: Mailbox, MailboxExportRequest +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RemoteCredential This parameter is reserved for internal Microsoft use. @@ -308,9 +296,7 @@ Accept wildcard characters: False 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. - - MapByMessageClass: This option finds the corresponding associated message by looking up the MessageClass attribute of the source message. If there's an associated message of this class in both source and target folders, it overwrites the associated message in the target. If there isn't an associated message in the target, it creates a copy in the target. - - Copy: This option copies associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This is the default option. Content filtering doesn't apply to associated messages. @@ -383,8 +369,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -404,15 +389,10 @@ Accept wildcard characters: False The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are: - ForceCopy - - KeepAll - - KeepLatestItem - - KeepSourceItem (This is the default value.) - - KeepTargetItem - - UpdateFromSource ```yaml @@ -429,19 +409,18 @@ Accept wildcard characters: False ``` ### -ContentFilter -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'"`. - -- 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. +**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. -- Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://docs.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). +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'"`. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -459,7 +438,7 @@ Accept wildcard characters: False ### -ContentFilterLanguage 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://go.microsoft.com/fwlink/p/?linkId=184859). +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). ```yaml Type: CultureInfo @@ -491,12 +470,12 @@ Accept wildcard characters: False ``` ### -ExcludeDumpster -The ExcludeDumpster parameter specifies whether to exclude the Recoverable Items folder. You don't have to include a value with this parameter. If you don't specify this parameter, the Recoverable Items folder is copied with the following subfolders: +The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch. -- Deletions +If you don't use this switch, the Recoverable Items folder is copied with the following subfolders: +- Deletions - Versions - - Purges ```yaml @@ -517,48 +496,34 @@ The ExcludeFolders parameter specifies the list of folders to exclude during the Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: -\/\*: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". -\#\\#/\*: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: - Inbox - - SentItems - - DeletedItems - - Calendar - - Contacts - - Drafts - - Journal - - Tasks - - Notes - - JunkEmail - - CommunicatorHistory - - Voicemail - - Fax - - Conflicts - - SyncIssues - - LocalFailures - - ServerFailures -If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a back slash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder, but not the well-known Notes folder, use the following syntax: \\\#Notes\\\#. +If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a backslash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. Wildcard characters can't be used in folder names. +To exclude the Recoverable Items folder, you must use the ExcludeDumpster parameter. + ```yaml Type: String[] Parameter Sets: Mailbox, MailboxExportRequest @@ -577,48 +542,34 @@ The IncludeFolders parameter specifies the list of folders to include during the Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: -\/\*: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". -\#\\#/\*: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: - Inbox - - SentItems - - DeletedItems - - Calendar - - Contacts - - Drafts - - Journal - - Tasks - - Notes - - JunkEmail - - CommunicatorHistory - - Voicemail - - Fax - - Conflicts - - SyncIssues - - LocalFailures - - ServerFailures -If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a back slash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder, but not the well-known Notes folder, use the following syntax: \\\#Notes\\\#. +If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a backslash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. Wildcard characters can't be used in folder names. +The Recoverable Items folder is always included if you don't use the ExcludeDumpster parameter, regardless of the list of folders you provide. + ```yaml Type: String[] Parameter Sets: Mailbox, MailboxExportRequest @@ -669,9 +620,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -681,7 +631,7 @@ 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 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -691,7 +641,7 @@ Accept wildcard characters: False ``` ### -MRSServer -This parameter is available or functional only in 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. @@ -711,7 +661,7 @@ Accept wildcard characters: False ### -Name 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. +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`. ```yaml Type: String @@ -746,17 +696,11 @@ Accept wildcard characters: False 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 - - Low - - Normal (This is the default value.) - - High - - Higher - - Highest - - Emergency ```yaml @@ -792,7 +736,6 @@ Accept wildcard characters: False 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. - - If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -845,7 +788,9 @@ Accept wildcard characters: False ``` ### -Suspend -The Suspend switch specifies whether to suspend the request. 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. You don't have to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -929,12 +874,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/New-MailboxFolder.md b/exchange/exchange-ps/exchange/New-MailboxFolder.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/New-MailboxFolder.md rename to exchange/exchange-ps/exchange/New-MailboxFolder.md index e197cadfb4..8edb27513b 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-MailboxFolder.md +++ b/exchange/exchange-ps/exchange/New-MailboxFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-mailboxfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MailboxFolder @@ -17,42 +16,38 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MailboxFolder cmdlet to create folders in your own mailbox. Administrators can't use this cmdlet to create folders in other mailboxes (the cmdlet is available only from the MyBaseOptions user role). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-MailboxFolder [-Name] -Parent [-Confirm] [-DomainController ] - [-WhatIf] [] +New-MailboxFolder [-Name] -Parent + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION If no parent folder is specified, the cmdlet creates a mail folder in the root folder hierarchy of the mailbox. If the mailbox isn't specified, the cmdlet creates the folder in the mailbox of the user currently running the task. When run, the cmdlet returns the new folder name and the folder path as the output. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). . +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). . ## EXAMPLES ### Example 1 ```powershell -New-MailboxFolder -Parent Tony:\Inbox -Name Personal +New-MailboxFolder -Parent :\Inbox -Name Personal ``` -This example creates the folder Personal under the Inbox folder of Tony's mailbox. +This example creates the folder named Personal under the Inbox folder of your own mailbox. ### Example 2 ```powershell -New-MailboxFolder -Parent Tony -Name Personal +New-MailboxFolder -Parent :\ -Name Personal ``` -This example creates the folder Personal in the root folder hierarchy of Tony's mailbox. - -### Example 3 -```powershell -New-MailboxFolder -Parent :\Inbox -Name Personal -``` - -This example creates the folder Personal under the Inbox folder in the mailbox for Tony who's running the command. +This example creates the folder named Personal in the root folder hierarchy of your own mailbox. ## PARAMETERS @@ -73,28 +68,23 @@ Accept wildcard characters: False ``` ### -Parent -The Parent parameter specifies where to create the new mailbox folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`. +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. + +To specify the root folder hierarchy of your own mailbox, use the value `:\`. For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't specify the parent folder, the command creates the folder in the root folder hierarchy of the specified mailbox. @@ -117,8 +107,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -173,12 +162,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/New-MailboxImportRequest.md b/exchange/exchange-ps/exchange/New-MailboxImportRequest.md similarity index 80% rename from exchange/exchange-ps/exchange/mailboxes/New-MailboxImportRequest.md rename to exchange/exchange-ps/exchange/New-MailboxImportRequest.md index 27addb5d09..f037f6aba2 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-MailboxImportRequest.md +++ b/exchange/exchange-ps/exchange/New-MailboxImportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-mailboximportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MailboxImportRequest @@ -17,9 +16,11 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MailboxImportRequest cmdlet to begin the process of importing a .pst file to a mailbox or archive. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +**Note**: This cmdlet is no longer supported in Exchange Online. To import a .pst file in Exchange Online, see [Use network upload to import PST files](https://learn.microsoft.com/purview/use-network-upload-to-import-pst-files). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -44,8 +45,6 @@ New-MailboxImportRequest [-Mailbox] -FilePath ] [-Name ] [-Priority ] - [-RemoteCredential ] - [-RemoteHostName ] [-SkipMerging ] [-SourceRootFolder ] [-Suspend] @@ -56,7 +55,7 @@ New-MailboxImportRequest [-Mailbox] -FilePath ] ``` -### MailboxImportRequest +### MailboxLocationId ``` New-MailboxImportRequest [-Mailbox] -FilePath [-AcceptLargeDataLoss] @@ -101,72 +100,36 @@ New-MailboxImportRequest [-Mailbox] -AzureBlobStora [-Confirm] [-ConflictResolutionOption ] [-ContentCodePage ] - [-DomainController ] [-ExcludeDumpster] [-ExcludeFolders ] [-IncludeFolders ] - [-InternalFlags ] [-IsArchive] [-LargeItemLimit ] - [-MigrationMailbox ] [-MRSContentFilterSasUri ] - [-Name ] - [-Priority ] - [-RequestExpiryInterval ] - [-SkipMerging ] - [-SourceEndpoint ] - [-SourceRootFolder ] - [-Suspend] - [-SuspendComment ] - [-TargetRootFolder ] - [-WhatIf] - [-WorkloadType ] - [] -``` - -### RemoteRequest -``` -New-MailboxImportRequest [-Mailbox] -RemoteFilePath -RemoteHostName - [-AcceptLargeDataLoss] - [-AssociatedMessagesCopyOption ] - [-BadItemLimit ] - [-BatchName ] - [-CompletedRequestAgeLimit ] - [-Confirm] - [-ConflictResolutionOption ] - [-ContentCodePage ] - [-DomainController ] - [-ExcludeDumpster] - [-ExcludeFolders ] - [-IncludeFolders ] - [-InternalFlags ] - [-IsArchive] - [-LargeItemLimit ] + [-MigrationBatch ] [-MigrationMailbox ] + [-MigrationUser ] [-Name ] - [-Priority ] - [-RemoteCredential ] [-RequestExpiryInterval ] + [-SkipInitialConnectionValidation] [-SkipMerging ] [-SourceEndpoint ] [-SourceRootFolder ] - [-Suspend] [-SuspendComment ] + [-Suspend] [-TargetRootFolder ] [-WhatIf] - [-WorkloadType ] [] ``` ## DESCRIPTION -You can create more than one mailbox import request per mailbox and each mailbox import request must have a unique name. Microsoft Exchange automatically generates up to 10 unique names for a mailbox import request. However, to create more than 10 import requests for a mailbox, you need to specify a unique name when creating the import request, or you can remove existing import requests with the Remove-MailboxExportRequest cmdlet before starting a new import request with the default request \\\MailboxImportX (where X = 0-9). +You can create more than one mailbox import request per mailbox and each mailbox import request must have a unique name. Microsoft Exchange automatically generates up to 10 unique names for a mailbox import request. However, to create more than 10 import requests for a mailbox, you need to specify a unique name when creating the import request, or you can remove existing import requests with the Remove-MailboxExportRequest cmdlet before starting a new import request with the default request `\MailboxImportX` (where X = 0-9). By default, the import checks for duplication of items and doesn't copy the data from the .pst file into the mailbox or archive if a matching item exists in the target mailbox or target archive. In on-premises Exchange, 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: - To import PST files from the share: Read permission - - To save exported PST files to the share: Read/Write permission. If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. @@ -182,7 +145,7 @@ This example imports a recovered .pst file on SERVER01 into the user Ayla's prim ### Example 2 ```powershell -New-MailboxImportRequest User2 -FilePath \\server\share\User1.pst -IsArchive -TargetRootFolder / +New-MailboxImportRequest Kweku -FilePath \\server\share\User1.pst -IsArchive -TargetRootFolder / ``` This example imports a .pst file into Kweku's archive folder. The TargetRootFolder isn't specified; therefore, content is merged under existing folders and new folders are created if they don't already exist in the target folder structure. @@ -196,57 +159,22 @@ This example imports all of the .pst files on a shared folder. Each .pst file na ## PARAMETERS -### -FilePath -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. - -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: - -- To import PST files from the share: Read permission - -- To save exported PST files to the share: Read/Write permission. - -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. - -```yaml -Type: LongPath -Parameter Sets: Mailbox, MailboxImportRequest -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Mailbox The Mailbox parameter specifies the destination mailbox where the content is being imported to. -In Exchange 2016 CU7 or later and Exchange Online, this parameter is the type MailboxLocationIdParameter, so the easiest value that you can use to identify the mailbox is the Alias value. +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. In Exchange 2016 CU6 or earlier, this parameter is the type MailboxOrMailUserIdParameter, so you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -264,7 +192,7 @@ Accept wildcard characters: False ```yaml Type: MailboxLocationIdParameter -Parameter Sets: MailboxImportRequest +Parameter Sets: MailboxLocationId Aliases: Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online @@ -275,14 +203,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -RemoteFilePath +### -AzureBlobStorageAccountUri +This parameter is available only in the cloud-based service. + This parameter is reserved for internal Microsoft use. ```yaml -Type: LongPath -Parameter Sets: RemoteRequest +Type: Uri +Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: True Position: Named @@ -291,14 +221,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RemoteHostName +### -AzureSharedAccessSignatureToken +This parameter is available only in the cloud-based service. + This parameter is reserved for internal Microsoft use. ```yaml -Type: Fqdn -Parameter Sets: RemoteRequest +Type: String +Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: True Position: Named @@ -307,13 +239,25 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -FilePath +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. + +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: + +- To import PST files from the share: Read permission +- To save exported PST files to the share: Read/Write permission. + +If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. + ```yaml -Type: Fqdn -Parameter Sets: Mailbox +Type: LongPath +Parameter Sets: Mailbox, MailboxLocationId Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -Required: False +Required: True Position: Named Default value: None Accept pipeline input: False @@ -323,7 +267,7 @@ Accept wildcard characters: False ### -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. +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. In Exchange 2010, you need to use this switch if you set the BadItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -344,9 +288,7 @@ Accept wildcard characters: False 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. - - MapByMessageClass: This option finds the corresponding associated message by looking up the MessageClass attribute of the source message. If there's an associated message of this class in both source and target folders, it overwrites the associated message in the target. If there isn't an associated message in the target, it creates a copy in the target. - - Copy: This option copies associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This is the default option. Content filtering doesn't apply to associated messages. @@ -364,46 +306,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AzureBlobStorageAccountUri -This parameter is available only in the cloud-based service. - -PARAMVALUE: Uri - -```yaml -Type: Uri -Parameter Sets: AzureImportRequest -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AzureSharedAccessSignatureToken -This parameter is available only in the cloud-based service. - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: AzureImportRequest -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -AzureStatusPublishEndpointInfo This parameter is available only in the cloud-based service. -PARAMVALUE: String +This parameter is reserved for internal Microsoft use. ```yaml Type: String @@ -425,8 +331,6 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. - ```yaml Type: Unlimited Parameter Sets: (All) @@ -475,8 +379,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -495,17 +398,12 @@ Accept wildcard characters: False ### -ConflictResolutionOption The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are: -- ForceCopy - +- ForceCopy (Exchange 2016 or later) - KeepAll - - KeepLatestItem - -- KeepSourceItem (This is the default value.) - -- KeepTargetItem - -- UpdateFromSource +- KeepSourceItem (This is the default value) +- KeepTargetItem (Exchange 2016 or later) +- UpdateFromSource (Exchange 2016 or later) ```yaml Type: ConflictResolutionOption @@ -521,7 +419,7 @@ Accept wildcard characters: False ``` ### -ContentCodePage -The ContentCodePage parameter specifies the specific code page to use for an ANSI pst file. ANSI pst filesare used in Outlook 97 to Outlook 2002. You can find the valid values in the [Code Page Identifiers](https://go.microsoft.com/fwlink/p/?linkId=328514) topic. +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 @@ -555,12 +453,12 @@ Accept wildcard characters: False ``` ### -ExcludeDumpster -The ExcludeDumpster parameter specifies whether to exclude the Recoverable Items folder. You don't have to include a value with this parameter. If you don't specify this parameter, the Recoverable Items folder is copied with the following subfolders: +The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch. -- Deletions +If you don't use this switch, the Recoverable Items folder is copied with the following subfolders: +- Deletions - Versions - - Purges ```yaml @@ -581,45 +479,29 @@ The ExcludeFolders parameter specifies the list of folders to exclude during the Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: -\/\*: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". -\#\\#/\*: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: - Inbox - - SentItems - - DeletedItems - - Calendar - - Contacts - - Drafts - - Journal - - Tasks - - Notes - - JunkEmail - - CommunicatorHistory - - Voicemail - - Fax - - Conflicts - - SyncIssues - - LocalFailures - - ServerFailures -If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a back slash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder, but not the well-known Notes folder, use the following syntax: \\\#Notes\\\#. +If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a backslash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. Wildcard characters can't be used in folder names. @@ -643,45 +525,29 @@ The IncludeFolders parameter specifies the list of folders to include during the Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: -\/\*: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". -\#\\#/\*: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: - Inbox - - SentItems - - DeletedItems - - Calendar - - Contacts - - Drafts - - Journal - - Tasks - - Notes - - JunkEmail - - CommunicationHistory - - Voicemail - - Fax - - Conflicts - - SyncIssues - - LocalFailures - - ServerFailures -If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a back slash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder, but not the well-known Notes folder, use the following syntax: \\\#Notes\\\#. +If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a backslash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. Wildcard characters can't be used in folder names. @@ -705,7 +571,7 @@ The InternalFlags parameter specifies the optional steps in the request. This pa ```yaml Type: InternalMrsFlag[] -Parameter Sets: (All) +Parameter Sets: Mailbox, MailboxLocationId Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -737,16 +603,13 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. - ```yaml Type: Unlimited Parameter Sets: (All) @@ -760,12 +623,30 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MigrationBatch +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use + +```yaml +Type: MigrationBatchIdParameter +Parameter Sets: AzureImportRequest +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MigrationMailbox This parameter is reserved for internal Microsoft use. ```yaml -Type: MailboxIdParameter -Parameter Sets: AzureImportRequest, MailboxImportRequest, RemoteRequest +Type: MailboxIdParameter, AzureImportRequest +Parameter Sets: MailboxLocationId Aliases: Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online @@ -776,14 +657,34 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MigrationUser +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MigrationUserIdParameter +Parameter Sets: AzureImportRequest +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MRSContentFilterSasUri +This parameter is available only in the cloud-based service. + This parameter is reserved for internal Microsoft use. ```yaml Type: Uri Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -793,7 +694,7 @@ Accept wildcard characters: False ``` ### -MRSServer -This parameter is available or functional only in 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. @@ -813,7 +714,7 @@ Accept wildcard characters: False ### -Name 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. +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`. ```yaml Type: String @@ -829,13 +730,15 @@ Accept wildcard characters: False ``` ### -Priority +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. ```yaml Type: RequestPriority -Parameter Sets: (All) +Parameter Sets: Mailbox, MailboxLocationId Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -844,18 +747,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RemoteCredential -This parameter is available only in on-premises Exchange. +### -RequestExpiryInterval +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. +- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. -The RemoteCredential parameter specifies the credentials of an administrator who has permission to perform the mailbox import request. +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. -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://go.microsoft.com/fwlink/p/?linkId=142122). +When you use the value Unlimited, the completed request isn't automatically removed. ```yaml -Type: PSCredential -Parameter Sets: Mailbox, RemoteRequest +Type: Unlimited +Parameter Sets: MailboxLocationId, AzureImportRequest Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -864,22 +770,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RequestExpiryInterval -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. - -- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. - -To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. +### -SkipInitialConnectionValidation +This parameter is available only in the cloud-based service. -When you use the value Unlimited, the completed request isn't automatically removed. +This parameter is reserved for internal Microsoft use. ```yaml -Type: Unlimited -Parameter Sets: AzureImportRequest, MailboxImportRequest, RemoteRequest +Type: SwitchParameter +Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -909,7 +809,7 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: MigrationEndpointIdParameter -Parameter Sets: AzureImportRequest, MailboxImportRequest, RemoteRequest +Parameter Sets: MailboxLocationId, AzureImportRequest Aliases: Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online @@ -937,7 +837,9 @@ Accept wildcard characters: False ``` ### -Suspend -The Suspend switch specifies whether to suspend the request. 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. You don't have to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -1007,7 +909,7 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: RequestWorkloadType -Parameter Sets: (All) +Parameter Sets: Mailbox, MailboxLocationId Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -1023,12 +925,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxRepairRequest.md b/exchange/exchange-ps/exchange/New-MailboxRepairRequest.md similarity index 83% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxRepairRequest.md rename to exchange/exchange-ps/exchange/New-MailboxRepairRequest.md index 7be2006e95..b5e267cdc2 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxRepairRequest.md +++ b/exchange/exchange-ps/exchange/New-MailboxRepairRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/new-mailboxrepairrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-MailboxRepairRequest @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-MailboxRepairRequest cmdlet to detect and fix mailbox corruption issues. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,17 +27,20 @@ New-MailboxRepairRequest [-Database] -CorruptionType ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Mailbox ``` -New-MailboxRepairRequest [-Mailbox] -CorruptionType [-Archive] +New-MailboxRepairRequest [-Mailbox] -CorruptionType + [-Archive] [-Confirm] [-DetectOnly] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -48,7 +50,7 @@ After you begin a repair request, you can't stop it unless you dismount the data To avoid performance problems, only one request can be active on a server for a database-level repair, or up to 100 requests can be active on a server for a mailbox-level repair. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,116 +84,20 @@ This example detects and repairs all corruption types for Ayla Kol's mailbox and ### Example 5 ```powershell -$Mailbox = Get-MailboxStatistics annb; New-MailboxRepairRequest -Database $Mailbox.Database -StoreMailbox $Mailbox.MailboxGuid -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview +$Mailbox = Get-MailboxStatistics annb + +New-MailboxRepairRequest -Database $Mailbox.Database -StoreMailbox $Mailbox.MailboxGuid -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview ``` This example creates a variable that identifies Ann Beebe's mailbox and then uses the variable to specify the values for the Database and StoreMailbox parameters to create a request to detect and repair all corruption types. ## PARAMETERS -### -CorruptionType -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. - -- AggregateCounts: Aggregate counts on folders that aren't reflecting correct values. - -- BigFunnelMissingPOIs: Exchange 2016. - -- BigFunnelPOI: Exchange 2019. - -- CleanupFilesFolder: Exchange 2016 or later. - -- CleanupGraphNodesWithPropertyError: Exchange 2016 or later. - -- CleanupOfficeGraphFolders: Exchange 2016 or later. - -- CleanupOfficeGraphSsc: Exchange 2016 or later. - -- CleanupOrphanedIndexes: Exchange 2016 or later. - -- CleanupTrendingAroundMe: Exchange 2016 or later. - -- CorruptJunkRule: Exchange 2013 or later. - -- CorruptSearchFolderCriteria: Exchange 2016 or later. - -- CorruptedPerUserData: Exchange 2016 or later. - -- DropAllLazyIndexes: Exchange 2013 or later. - -- EmptyFilesFolder: Exchange 2016 or later. - -- Extension1: Exchange 2013 or later, but reserved for internal Microsoft use. - -- Extension2: Exchange 2013 or later, but reserved for internal Microsoft use. - -- Extension3: Exchange 2013 or later, but reserved for internal Microsoft use. - -- Extension4: Exchange 2013 or later, but reserved for internal Microsoft use. - -- Extension5: Exchange 2013 or later, but reserved for internal Microsoft use. - -- FocusedInboxCleanup: Exchange 2016 or later. - -- FolderACL: Exchange 2013 or later. - -- FolderView: Views on folders that aren't returning correct contents. - -- ImapId: Exchange 2013 or later. - -- LockedMoveTarget: Exchange 2013 or later, but only if the mailbox is locked. - -- MessageId - -- MessagePtagCn - -- MissingSpecialFolders: Exchange 2013 or later. - -- OlcFolderCleanup: Exchange 2016 or later. - -- ProvisionedFolder: Provisioned folders that are incorrectly pointing into parent folders that aren't provisioned. - -- ReduceRedundantAI: Exchange 2016 or later, and only by itself. - -- RemovePICWFolder: Exchange 2016 or later, but reserved for internal Microsoft use. - -- ReplState: Exchange 2013 or later. - -- RestrictionFolder: Exchange 2013 or later. - -- RuleMessageClass: Exchange 2013 or later. - -- ScheduledCheck: Exchange 2013 or later. - -- SearchFolder: Search folder corruption. - -- SyncDefaultFolderLocalizationWithMailbox: Exchange 2016 or later. - -- UniqueMidIndex: Exchange 2013 or later. - -You can specify multiple values separated by commas. - -```yaml -Type: MailboxStoreCorruptionType[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Database 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 - - Distinguished name (DN) - - GUID You can't use this parameter with the Mailbox parameter. @@ -215,23 +121,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Database parameter. @@ -249,6 +146,84 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -StoreMailbox +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. + +```yaml +Type: StoreMailboxIdParameter +Parameter Sets: Database +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 2 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CorruptionType +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. +- AggregateCounts\*: Aggregate counts on folders that aren't reflecting correct values. +- BigFunnelMissingPOIs\*: Exchange 2016. +- BigFunnelPOI: Exchange 2019. +- CleanupFilesFolder\*: Exchange 2016 or later. +- CleanupGraphNodesWithPropertyError\*: Exchange 2016 or later. +- CleanupOfficeGraphFolders\*: Exchange 2016 or later. +- CleanupOfficeGraphSsc: Exchange 2016 or later. +- CleanupOrphanedIndexes\*: Exchange 2016 or later. +- CleanupTrendingAroundMe\*: Exchange 2016 or later. +- CorruptJunkRule\*: Exchange 2013 or later. +- CorruptSearchFolderCriteria\*: Exchange 2016 or later. +- CorruptedPerUserData\*: Exchange 2016 or later. +- DropAllLazyIndexes\*: Exchange 2013 or later. +- EmptyFilesFolder\*: Exchange 2016 or later. +- Extension1: Exchange 2013 or later, but reserved for internal Microsoft use. +- Extension2: Exchange 2013 or later, but reserved for internal Microsoft use. +- Extension3: Exchange 2013 or later, but reserved for internal Microsoft use. +- Extension4: Exchange 2013 or later, but reserved for internal Microsoft use. +- Extension5: Exchange 2013 or later, but reserved for internal Microsoft use. +- FocusedInboxCleanup\*: Exchange 2016 or later. +- FolderACL\*: Exchange 2013 or later. +- FolderView\*: Views on folders that aren't returning correct contents. +- ImapId\*: Exchange 2013 or later. +- LockedMoveTarget\*: Exchange 2013 or later, but only if the mailbox is locked. +- MessageId +- MessagePtagCn +- MissingSpecialFolders: Exchange 2013 or later. +- OlcFolderCleanup: Exchange 2016 or later. +- ProvisionedFolder: Provisioned folders that are incorrectly pointing into parent folders that aren't provisioned. +- ReduceRedundantAI\*: Exchange 2016 or later. +- RemovePICWFolder: Exchange 2016 or later, but reserved for internal Microsoft use. +- ReplState: Exchange 2013 or later. +- RestrictionFolder: Exchange 2013 or later. +- RuleMessageClass: Exchange 2013 or later. +- ScheduledCheck: Exchange 2013 or later. +- SearchFolder: Search folder corruption. +- SyncDefaultFolderLocalizationWithMailbox: Exchange 2016 or later. +- UniqueMidIndex: Exchange 2013 or later. + +You can specify multiple values separated by commas. + +\* You can only use this value by itself. + +```yaml +Type: MailboxStoreCorruptionType[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Archive 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. @@ -272,8 +247,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -322,7 +296,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch specifies that the command should run immediately and not wait to be dispatched by workload management. You don't need to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -337,24 +313,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -StoreMailbox -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. - -```yaml -Type: StoreMailboxIdParameter -Parameter Sets: Database -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -376,12 +334,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/New-MailboxRestoreRequest.md new file mode 100644 index 0000000000..43a1b13892 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-MailboxRestoreRequest.md @@ -0,0 +1,1162 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-MailboxRestoreRequest + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-MailboxRestoreRequest cmdlet to restore a soft-deleted or disconnected mailbox. This cmdlet starts the process of moving content from the soft-deleted mailbox, disabled mailbox, or any mailbox in a recovery database into a connected primary or archive mailbox. + +The properties used to find disconnected mailboxes and restore a mailbox are different in Exchange Server and Exchange Online. For more information about Exchange Online, see [Restore an inactive mailbox](https://learn.microsoft.com/purview/restore-an-inactive-mailbox). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +New-MailboxRestoreRequest -SourceDatabase -SourceStoreMailbox -TargetMailbox + [-AcceptLargeDataLoss] + [-AllowLegacyDNMismatch] + [-AssociatedMessagesCopyOption ] + [-BadItemLimit ] + [-BatchName ] + [-Confirm] + [-ConflictResolutionOption ] + [-DomainController ] + [-ExcludeDumpster] + [-ExcludeFolders ] + [-IncludeFolders ] + [-MRSServer ] + [-Name ] + [-Priority ] + [-SourceRootFolder ] + [-SuspendComment ] + [-Suspend] + [-TargetIsArchive] + [-TargetRootFolder ] + [-WhatIf] + [] +``` + +### CrossTenantRestore +``` +New-MailboxRestoreRequest -SourceEndpoint -SourceExchangeGuid -SourceTenant -TargetMailbox + [-AcceptLargeDataLoss] + [-AllowLegacyDNMismatch] + [-AssociatedMessagesCopyOption ] + [-BadItemLimit ] + [-BatchName ] + [-CompletedRequestAgeLimit ] + [-Confirm] + [-ConflictResolutionOption ] + [-ContentFilter ] + [-ContentFilterLanguage ] + [-CrossTenantRestore] + [-DomainController ] + [-ExcludeDumpster] + [-ExcludeFolders ] + [-IncludeFolders ] + [-LargeItemLimit ] + [-Name ] + [-SkipMerging ] + [-SourceRootFolder ] + [-SuspendComment ] + [-Suspend] + [-TargetIsArchive] + [-TargetRootFolder ] + [-TargetType ] + [-WhatIf] + [] +``` + +### MigrationLocalMailboxRestore +``` +New-MailboxRestoreRequest -SourceDatabase -SourceStoreMailbox > + [-AcceptLargeDataLoss] + [-AllowLegacyDNMismatch] + [-AssociatedMessagesCopyOption ] + [-BadItemLimit ] + [-BatchName ] + [-CompletedRequestAgeLimit ] + [-Confirm] + [-ConflictResolutionOption ] + [-ContentFilter ] + [-ContentFilterLanguage ] + [-DomainController ] + [-ExcludeDumpster] + [-ExcludeFolders ] + [-IncludeFolders ] + [-InternalFlags ] + [-LargeItemLimit ] + [-Name ] + [-Priority ] + [-RequestExpiryInterval ] + [-SkipMerging ] + [-SourceRootFolder ] + [-Suspend] + [-SuspendComment ] + [-TargetIsArchive] + [-TargetRootFolder ] + [-TargetType ] + [-WhatIf] + [-WorkloadType ] + [] +``` + +### RemoteMailboxRestoreMailboxLocationId +``` +New-MailboxRestoreRequest -SourceStoreMailbox -TargetMailbox + [-AcceptLargeDataLoss] + [-AllowLegacyDNMismatch] + [-AssociatedMessagesCopyOption ] + [-BadItemLimit ] + [-BatchName ] + [-CompletedRequestAgeLimit ] + [-Confirm] + [-ConflictResolutionOption ] + [-ContentFilter ] + [-ContentFilterLanguage ] + [-DomainController ] + [-ExcludeDumpster] + [-ExcludeFolders ] + [-IncludeFolders ] + [-InternalFlags ] + [-LargeItemLimit ] + [-Name ] + [-Priority ] + [-RequestExpiryInterval ] + [-SkipMerging ] + [-SourceRootFolder ] + [-Suspend] + [-SuspendComment ] + [-TargetIsArchive] + [-TargetRootFolder ] + [-TargetType ] + [-WhatIf] + [-WorkloadType ] + [] +``` + +### RemoteMailboxRestoreMailboxId +``` +New-MailboxRestoreRequest -SourceStoreMailbox -TargetMailbox + [-AcceptLargeDataLoss] + [-AllowLegacyDNMismatch] + [-AssociatedMessagesCopyOption ] + [-BadItemLimit ] + [-BatchName ] + [-CompletedRequestAgeLimit ] + [-Confirm] + [-ConflictResolutionOption ] + [-DomainController ] + [-ExcludeDumpster] + [-ExcludeFolders ] + [-IncludeFolders ] + [-InternalFlags ] + [-LargeItemLimit ] + [-Name ] + [-Priority ] + [-SkipMerging ] + [-SourceRootFolder ] + [-Suspend] + [-SuspendComment ] + [-TargetIsArchive] + [-TargetRootFolder ] + [-WhatIf] + [-WorkloadType ] + [] +``` + +### SourceMailbox +``` +New-MailboxRestoreRequest -RemoteDatabaseGuid -RemoteHostName -RemoteRestoreType -RemoteCredential -SourceMailbox -TargetMailbox + [-AcceptLargeDataLoss] + [-AllowLegacyDNMismatch] + [-AssociatedMessagesCopyOption ] + [-BadItemLimit ] + [-BatchName ] + [-CompletedRequestAgeLimit ] + [-Confirm] + [-ConflictResolutionOption ] + [-ContentFilter ] + [-ContentFilterLanguage ] + [-DomainController ] + [-ExcludeDumpster] + [-ExcludeFolders ] + [-IncludeFolders ] + [-InternalFlags ] + [-LargeItemLimit ] + [-Name ] + [-Priority ] + [-RequestExpiryInterval ] + [-SkipMerging ] + [-SourceIsArchive] + [-SourceRootFolder ] + [-Suspend] + [-SuspendComment ] + [-TargetIsArchive] + [-TargetRootFolder ] + [-TargetType ] + [-WhatIf] + [-WorkloadType ] + [] +``` + +## DESCRIPTION +When mailboxes are moved from one database to another, Exchange doesn't fully delete the mailbox from the source database immediately upon completion of the move. Instead, the mailbox in the source mailbox database is switched to a soft-deleted state, which allows mailbox data to be accessed during a mailbox restore operation by using the new MailboxRestoreRequest cmdlet set. The soft-deleted mailboxes are retained in the source database until either the deleted mailbox retention period expires or you use the Remove-StoreMailbox cmdlet to purge the mailbox. + +To view soft-deleted mailboxes, run the Get-MailboxStatistics cmdlet against a database and look for results that have a DisconnectReason with a value of SoftDeleted. For more information, see Example 1 later in this topic. + +A mailbox is marked as Disabled a short time after the Disable-Mailbox or Remove-Mailbox command completes. + +The mailbox won't be marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory has been updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database. + +Exchange retains disabled mailboxes in the mailbox database based on the deleted mailbox retention settings configured for that mailbox database. After the specified period of time, the mailbox is permanently deleted. + +To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database and look for results that have a DisconnectReason with a value of Disabled. For more information, see Examples 2 and 3 later in this topic. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +**Note**: To restore the contents of a primary mailbox to an archive mailbox, use the TargetRootFolder 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. + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxStatistics -Database MBD01 | Where {$_.DisconnectReason -eq "SoftDeleted" -or $_.DisconnectReason -eq "Disabled"} | Format-List LegacyExchangeDN,DisplayName,MailboxGUID, DisconnectReason + +New-MailboxRestoreRequest -SourceDatabase "MBD01" -SourceStoreMailbox 1d20855f-fd54-4681-98e6-e249f7326ddd -TargetMailbox Ayla +``` + +In on-premises Exchange, this example uses the Get-MailboxStatistics cmdlet to return the DisplayName, LegacyExchangeDN, and MailboxGUID (valid source mailbox identity values) for all mailboxes in the mailbox database named MBD01 that have a disconnect reason of SoftDeleted or Disabled. + +Using this information, the source mailbox with the MailboxGUID value 1d20855f-fd54-4681-98e6-e249f7326ddd is restored to the target mailbox that has the Alias value Ayla. + +### Example 2 +```powershell +New-MailboxRestoreRequest -SourceDatabase "MBD01" -SourceStoreMailbox "Tony Smith" -TargetMailbox Tony@contoso.com -TargetIsArchive +``` + +In on-premises Exchange, this example restores the content of the source mailbox with the DisplayName of Tony Smith on mailbox database MBD01 to the archive mailbox for Tony@contoso.com. + +### Example 3 +```powershell +New-MailboxRestoreRequest -SourceMailbox 33948c06-c453-48be-bdb9-08eacd466f81 -TargetMailbox Tony@contoso.com -AllowLegacyDNMismatch +``` + +In Exchange Online, this example restores the content of the inactive, disconnected, or soft deleted source mailbox to the active mailbox for Tony@contoso.com: + +- The SourceMailbox value is the MailboxGUID value of an inactive, disconnected, or soft deleted mailbox. +- The TargetMailbox value is the MailboxGUID or email address of the active target mailbox. +- AllowLegacyDNMismatch allows copying data from one mailbox to another in this scenario. + +## PARAMETERS + +### -CrossTenantRestore +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: CrossTenantRestore +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteCredential +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PSCredential +Parameter Sets: SourceMailbox +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteDatabaseGuid +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: SourceMailbox +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteHostName +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: SourceMailbox +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteRestoreType +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: RemoteRestoreType +Parameter Sets: SourceMailbox +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceDatabase +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: DatabaseIdParameter +Parameter Sets: Default, MigrationLocalMailboxRestore +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceEndpoint +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MigrationEndpointIdParameter +Parameter Sets: CrossTenantRestore +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceExchangeGuid +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: CrossTenantRestore +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceStoreMailbox +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. + +You can find the MailboxGUID by running the Get-MailboxStatistics cmdlet. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceTenant +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SmtpDomain +Parameter Sets: CrossTenantRestore +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetMailbox +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. + +In Exchange 2016 or later and Exchange Online, this parameter is the type MailboxLocationIdParameter. + +In Exchange 2013 or earlier, this parameter is the type MailboxOrMailUserIdParameter. + +```yaml +Type: MailboxLocationIdParameter +Parameter Sets: CrossTenantRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: MailboxOrMailUserIdParameter +Parameter Sets: Default, RemoteMailboxRestoreMailboxId +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +In Exchange 2010, you need to use this switch if you set the BadItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLegacyDNMismatch +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. + +**Note**: This parameter is being deprecated in the cloud-based service. To complete a mailbox restore request for mailboxes with a LegacyExchangeDN that doesn't match, you need to obtain the LegacyExchangeDN value for the source mailbox and add it to the target mailbox as an X500 proxy address. For detailed instructions, see [Restore an inactive mailbox](https://learn.microsoft.com/purview/restore-an-inactive-mailbox#restore-inactive-mailboxes). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssociatedMessagesCopyOption +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. +- MapByMessageClass: Find the associated message by looking up the MessageClass attribute of the source message. If there's an associated message of this class in both source and target folders, it overwrites the associated message in the target. If there isn't an associated message in the target, it creates a copy in the target. +- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This is the default value. + +Content filtering doesn't apply to associated messages. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BadItemLimit +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. + +In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. + +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BatchName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompletedRequestAgeLimit +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConflictResolutionOption +The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are: + +- ForceCopy +- KeepAll +- KeepLatestItem +- KeepSourceItem (This is the default value.) +- KeepTargetItem +- UpdateFromSource + +```yaml +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 +Default value: KeepSourceItem +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentFilter +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'"`. + +- 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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentFilterLanguage +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. + +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). + +```yaml +Type: CultureInfo +Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeDumpster +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: + +- Deletions +- Versions +- Purges + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeFolders +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: + +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". + +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: + +- Inbox +- SentItems +- DeletedItems +- Calendar +- Contacts +- Drafts +- Journal +- Tasks +- Notes +- JunkEmail +- CommunicatorHistory +- Voicemail +- Fax +- Conflicts +- SyncIssues +- LocalFailures +- ServerFailures + +If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a backslash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. + +Wildcard characters can't be used in folder names. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeFolders +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: + +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". + +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: + +- Inbox +- SentItems +- DeletedItems +- Calendar +- Contacts +- Drafts +- Journal +- Tasks +- Notes +- JunkEmail +- CommunicationHistory +- Voicemail +- Fax +- Conflicts +- SyncIssues +- LocalFailures +- ServerFailures + +If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a backslash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. + +Wildcard characters can't be used in folder names. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalFlags +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. + +```yaml +Type: InternalMrsFlag[] +Parameter Sets: MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LargeItemLimit +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: + +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) + +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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. + +If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. + +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MRSServer +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. + +```yaml +Type: Fqdn +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Lowest +- Lower +- Low +- Normal (This is the default value.) +- High +- Higher +- Highest +- Emergency + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequestExpiryInterval +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: + +- The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. +- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. + +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. + +When you use the value Unlimited, the completed request isn't automatically removed. + +```yaml +Type: Unlimited +Parameter Sets: MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipMerging +The SkipMerging parameter specifies folder-related items to skip when restoring the mailbox. Use one of the following values: + +- FolderACLs +- FolderProperties +- FolderRules +- InitialConnectionValidation + +Use this parameter only if a restore request fails because of folder rules, folder access control lists (ACLs), or initial connection validation. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceIsArchive +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. + +```yaml +Type: SwitchParameter +Parameter Sets: SourceMailboxMailbox +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceRootFolder +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Suspend +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SuspendComment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetIsArchive +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetRootFolder +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetType +The TargetType parameter specifies the type of mailbox that's the target for the restore operation. Valid values are: + +- Archive +- MailboxLocation +- Primary (This is the default value) + +```yaml +Type: TargetTypeComponent +Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkloadType +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: RequestWorkloadType +Parameter Sets: MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/policy-and-compliance-content-search/New-MailboxSearch.md b/exchange/exchange-ps/exchange/New-MailboxSearch.md similarity index 82% rename from exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-MailboxSearch.md rename to exchange/exchange-ps/exchange/New-MailboxSearch.md index 080bba17d6..8c7db70175 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-MailboxSearch.md +++ b/exchange/exchange-ps/exchange/New-MailboxSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/new-mailboxsearch -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MailboxSearch @@ -15,15 +14,11 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -On July 1, 2018, you'll no longer be able to use the New-MailboxSearch cmdlet to create In-Place eDiscovery searches and In-Place Holds in Exchange Online. To create eDiscovery searches and eDiscovery case holds, please start using New-ComplianceSearch and New-CaseHoldPolicy in the Office 365 Security & Compliance Center. You'll still be able to use Set-MailboxSearch to modify existing In-Place eDiscovery searches and In-Place Holds. Creating new searches and holds in Exchange Server 2013 will still be supported, and searches run from your on-premises organization in an Exchange hybrid deployment aren't affected by this change. - Use the New-MailboxSearch cmdlet to create a mailbox search and either get an estimate of search results, place search results on In-Place Hold or copy them to a Discovery mailbox. You can also place all contents in a mailbox on hold by not specifying a search query, which accomplishes similar results as Litigation Hold. -By default, mailbox searches are performed across all Exchange 2013 or later Mailbox servers in an Exchange organization, unless you constrain the search to fewer mailboxes by using the SourceMailboxes parameter. To search mailboxes on Exchange 2010 Mailbox servers, run the command on an Exchange 2010 server. - -For more information, see [In-Place eDiscovery in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/holds/holds). +**Note**: As of October 2020, the \*-MailboxSearch cmdlets are retired in Exchange Online PowerShell. Use the \*-ComplianceSearch cmdlets in Security & Compliance PowerShell instead. For more information, see [Retirement of legacy eDiscovery tools](https://learn.microsoft.com/purview/ediscovery-legacy-retirement). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -55,13 +50,18 @@ New-MailboxSearch [-Name] [-StartDate ] [-StatusMailRecipients ] [-TargetMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -The New-MailboxSearch cmdlet creates an In-Place eDiscovery search or an In-Place Hold. Unless specified, mailboxes on all Mailbox servers in an organization are searched. You can stop, start, modify, or remove the search. +The New-MailboxSearch cmdlet creates an In-Place eDiscovery search or an In-Place Hold. You can stop, start, modify, or remove the search. + +By default, mailbox searches are performed across all Exchange 2013 or later Mailbox servers in an organization, unless you constrain the search to fewer mailboxes by using the SourceMailboxes parameter. To search mailboxes on Exchange 2010 Mailbox servers, run the command on an Exchange 2010 server. + +For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -73,15 +73,10 @@ New-MailboxSearch -Name "Legal-ProjectX" -SourceMailboxes DG-Marketing,DG-Execut This example creates the mailbox search Legal-ProjectX. The search uses several parameters to restrict the search query: - SourceMailboxes: This parameter restricts the search to members of the DG-Marketing and DG-Executives distribution groups. - - Recipients: This parameter specifies that the search includes all mail sent to the domain contoso.com. - - SearchQuery: This parameter specifies a KQL query for messages with either the words project or report and for messages with attachments. - - StartDate and EndDate: These parameters specify the start date of January 1, 2018, and end date of December 31, 2018, for the search. - - TargetMailbox: This parameter specifies that search results should be copied to the discovery mailbox LegalDiscovery. - - StatusMailRecipients: This parameter specifies that the distribution group DG-DiscoveryTeam is to receive a notification when the search is complete. ### Example 2 @@ -89,14 +84,14 @@ This example creates the mailbox search Legal-ProjectX. The search uses several New-MailboxSearch -Name "Hold-ProjectX" -SourceMailboxes DG-Finance -InPlaceHoldEnabled $true ``` -This example creates an In-Place Hold Hold-ProjectX and places all members of the distribution group DG-Finance on hold. Because the search doesn't specify the SearchQuery and ItemHoldPeriod parameters, all messages in mailboxes returned are placed on indefinite In-Place Hold. +This example creates an In-Place Hold named Hold-ProjectX and places all members of the distribution group DG-Finance on hold. Because the search doesn't specify the SearchQuery and ItemHoldPeriod parameters, all messages in mailboxes returned are placed on indefinite In-Place Hold. ### Example 3 ```powershell -New-MailboxSearch -Name "Hold-tailspintoys" -SourceMailboxes DG-Research -SearchQuery "'Patent' AND 'Project tailspintoys'" -InPlaceHoldEnabled $true +New-MailboxSearch -Name "Hold-tailspintoys" -SourceMailboxes DG-Research -SearchQuery '"Patent" AND "Project tailspintoys"' -InPlaceHoldEnabled $true ``` -This example creates an In-Place Hold Hold-tailspintoys and places all members of the distribution group DG-Research on hold. Because the search specifies the SearchQuery parameter, only messages that match the search query are placed on indefinite In-Place Hold. +This example creates an In-Place Hold named Hold-tailspintoys and places all members of the distribution group DG-Research on hold. Because the search specifies the SearchQuery parameter, only messages that match the search query are placed on indefinite In-Place Hold. ### Example 4 ```powershell @@ -126,19 +121,16 @@ Accept wildcard characters: False ``` ### -AllPublicFolderSources -This parameter is available only in on-premises Exchange. - 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]). - - $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -148,19 +140,16 @@ Accept wildcard characters: False ``` ### -AllSourceMailboxes -This parameter is available only in on-premises Exchange. - 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]). - - $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -172,15 +161,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -224,9 +212,11 @@ Accept wildcard characters: False ``` ### -DoNotIncludeArchive -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. -The DoNotIncludeArchive parameter specifies whether archive mailboxes are included in the search. By default, archive mailboxes are included in the search. To exclude archive mailboxes, set the DoNotIncludeArchive parameter to $true. +The DoNotIncludeArchive switch specifies that archive mailboxes are not included in the search. You don't need to specify a value with this switch. + +By default, archive mailboxes are included in the search. To exclude archive mailboxes, use this switch. ```yaml Type: SwitchParameter @@ -244,7 +234,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". ```yaml Type: ExDateTime @@ -281,7 +271,6 @@ Accept wildcard characters: False 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. - - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes. ```yaml @@ -298,7 +287,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -351,7 +342,6 @@ Accept wildcard characters: False 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. - - $false: In-Place Hold isn't enabled on the search results. This is the default value. You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true. @@ -362,7 +352,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -391,14 +381,13 @@ Accept wildcard characters: False 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. - - The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -410,7 +399,7 @@ Accept wildcard characters: False ### -Language 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://go.microsoft.com/fwlink/p/?linkId=184859). +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). ```yaml Type: CultureInfo @@ -429,9 +418,7 @@ Accept wildcard characters: False The LogLevel parameter specifies the logging level for the search. Valid values are: - Suppress: No logs are kept. - - Basic: Basic information about the query and who ran it is kept. This is the default value. - - Full: In addition to the information kept by the Basic log level, the Full log level adds a complete list of search results. ```yaml @@ -451,19 +438,12 @@ Accept wildcard characters: False The MessageTypes parameter specifies the message types to include in the search query. Valid values are: - Contacts - - Docs - - Email - - IM - - Journals - - Meetings - - Notes - - Tasks You can specify multiple values separated by commas. @@ -502,11 +482,11 @@ Accept wildcard characters: False ``` ### -SearchDumpster -This parameter is available or functional only in 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. +The SearchDumpster switch specifies whether the dumpster is searched. You don't need to specify a value with this switch. -By default, items in the dumpster are searched. Set the value to $false to disable searching the dumpster. +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. ```yaml Type: SwitchParameter @@ -522,20 +502,16 @@ Accept wildcard characters: False ``` ### -SearchQuery -The SearchQuery parameter specifies keywords for the search query by using the Keyword Query Language (KQL). For more information about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). +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. The other search query parameters are: - EndDate - - MessageTypes - - Recipients - - Senders - - StartDate ```yaml @@ -573,18 +549,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. To use this parameter, the AllSourceMailboxes parameter needs to be $false (the default value). @@ -593,7 +564,6 @@ The default value is blank ($null), which means no source mailboxes are specifie To enable In-Place Hold on the search results, you need to set the AllSourceMailboxes parameter to $false (the default value) and configure one or both of the following settings: - Specify one ore more source mailboxes by using the SourceMailboxes parameter. - - In on-premises Exchange, set the AllPublicFolderSources parameter to $true. ```yaml @@ -612,7 +582,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: ExDateTime @@ -631,18 +601,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -661,23 +626,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -700,7 +656,7 @@ The WhatIf switch doesn't work on this cmdlet. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -714,12 +670,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md new file mode 100644 index 0000000000..0dd0822a20 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md @@ -0,0 +1,677 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-MalwareFilterPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-MalwareFilterPolicy cmdlet to create malware filter policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-MalwareFilterPolicy [-Name] + [-Action ] + [-AdminDisplayName ] + [-BypassInboundMessages ] + [-BypassOutboundMessages ] + [-Confirm] + [-CustomAlertText ] + [-CustomExternalBody ] + [-CustomExternalSubject ] + [-CustomFromAddress ] + [-CustomFromName ] + [-CustomInternalBody ] + [-CustomInternalSubject ] + [-CustomNotifications ] + [-DomainController ] + [-EnableExternalSenderAdminNotifications ] + [-EnableExternalSenderNotifications ] + [-EnableFileFilter ] + [-EnableInternalSenderAdminNotifications ] + [-EnableInternalSenderNotifications ] + [-ExternalSenderAdminAddress ] + [-FileTypeAction ] + [-FileTypes ] + [-InternalSenderAdminAddress ] + [-QuarantineTag ] + [-RecommendedPolicyType ] + [-WhatIf] + [-ZapEnabled ] + [] +``` + +## DESCRIPTION +New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the MalwareFilterPolicy parameter on the New-MalwareFilterRule or Set-MalwareFilterRule cmdlets to associate the policy with a rule. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-MalwareFilterPolicy -Name "Contoso Malware Filter Policy" -EnableInternalSenderAdminNotifications $true -InternalSenderAdminAddress admin@contoso.com +``` + +This example creates a new malware filter policy named Contoso Malware Filter Policy with the following settings: + +- Block messages that contain malware in on-premises Exchange, or quarantine the message in Exchange Online. +- Notify the administrator admin@contoso.com when malware is detected in a message from an internal sender. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Action +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: + +- DeleteMessage: Handles the message without notifying the recipients. This is the default value. +- DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. +- DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. + +```yaml +Type: MalwareFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassInboundMessages +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: + +- $true: Malware filtering is disabled on inbound messages. +- $false: Malware filtering is enabled on inbound messages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassOutboundMessages +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: + +- $true: Malware filtering is disabled on outbound messages. +- $false: Malware filtering is enabled on outbound messages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAlertText +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 ("). + +This parameter is meaningful only when the value of the Action parameter is DeleteAttachmentAndUseCustomAlert. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomExternalBody +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomExternalSubject +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomFromAddress +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomFromName +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomInternalBody +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: + +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomInternalSubject +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: + +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomNotifications +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. +- $false: No customization is done to notification messages. The default values are used. + +This parameter is meaningful only when the value of at least one of the following parameters is also $true: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableExternalSenderAdminNotifications +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. +- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value. + +**Note**: Admin notifications are sent only for _attachments_ that are classified as malware. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableExternalSenderNotifications +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: + +- $true: When malware is detected in a message from an external sender, send them a notification message. +- $false: Don't send malware detection notification messages to external message senders. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableFileFilter +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: + +- $true: The common attachments filter is enabled. This is the default value. +- $false: The common attachments filter is disabled. + +You specify the file types using the FileTypes parameter. A default list of values is automatically provided, but you can customize it. + +You specify the action for detected files using the FileTypeAction parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableInternalSenderAdminNotifications +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. +- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value. + +**Note**: Admin notifications are sent only for _attachments_ that are classified as malware. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableInternalSenderNotifications +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: + +- $true: When malware is detected in a message from an internal sender, send them a notification message. +- $false: Don't send malware detection notification messages to internal message senders. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalSenderAdminAddress +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileTypeAction +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: + +- Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter. +- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value. + +This parameter is meaningful only when the value of the EnableFileFilter parameter is $true. + +```yaml +Type: FileTypeFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileTypes +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: + +`ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z` + +This parameter is meaningful only if the value of the EnableFileFilter parameter is $true. + +The common attachments filter uses best effort true-typing to detect the file type regardless of the file name extension. For example, an exe file renamed to txt is detected as an exe file. If true-typing fails or isn't supported for the specified file type, then extension matching is used. + +To replace the existing list of file types with the values you specify, use the syntax `FileType1,FileType2,...FileTypeN`. To preserve existing values, be sure to include the file types that you want to keep along with the new values that you want to add. + +To add or remove file types without affecting the other file type entries, see the Examples section in the Set-MalwareFilterPolicy cmdlet topic. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalSenderAdminAddress +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages, and whether users receive quarantine notifications. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the default quarantine policy that's used is named AdminOnlyAccessPolicy. For more information about this quarantine policy, see [Anatomy of a quarantine policy](https://learn.microsoft.com/defender-office-365/quarantine-policies#anatomy-of-a-quarantine-policy). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecommendedPolicyType +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. + +```yaml +Type: RecommendedPolicyType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ZapEnabled +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: + +- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This is the default value. +- $false: ZAP for malware is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/antispam-antimalware/New-MalwareFilterRule.md b/exchange/exchange-ps/exchange/New-MalwareFilterRule.md similarity index 83% rename from exchange/exchange-ps/exchange/antispam-antimalware/New-MalwareFilterRule.md rename to exchange/exchange-ps/exchange/New-MalwareFilterRule.md index f6ed84b9ef..ad4f6ad019 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/New-MalwareFilterRule.md +++ b/exchange/exchange-ps/exchange/New-MalwareFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/new-malwarefilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-MalwareFilterRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MalwareFilterRule cmdlet to create malware filter rules in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -34,11 +33,15 @@ New-MalwareFilterRule [-Name] -MalwareFilterPolicy ] [-SentTo ] [-SentToMemberOf ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,43 +54,41 @@ This example creates a new malware filter rule named Contoso Recipients with the ## PARAMETERS -### -MalwareFilterPolicy -The MalwareFilterPolicy parameter specifies the malware filter policy that's associated with the malware filter rule rule. - -You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID. - -You can't specify the default malware filter policy, and you can't specify a policy that's already associated with another malware filter rule. +### -Name +The Name parameter specifies a unique name for the malware filter rule. ```yaml -Type: MalwareFilterPolicyIdParameter +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies a unique name for the malware filter rule. +### -MalwareFilterPolicy +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: + +- Name +- Distinguished name (DN) +- GUID. + +You can't specify the default malware filter policy, and you can't specify a policy that's already associated with another malware filter rule. ```yaml -Type: String +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 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -112,8 +113,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -164,7 +164,7 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -183,18 +183,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -210,21 +205,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf -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: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. @@ -247,9 +237,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a new rule (the 9th rule) are from 0 through 8. - - The default value for a new rule (the 9th rule) is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -268,7 +256,7 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -287,18 +275,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -314,21 +297,16 @@ Accept wildcard characters: False ``` ### -SentToMemberOf -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: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. @@ -366,12 +344,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedContentSettings.md b/exchange/exchange-ps/exchange/New-ManagedContentSettings.md similarity index 90% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedContentSettings.md rename to exchange/exchange-ps/exchange/New-ManagedContentSettings.md index 716df60c9a..1d10f3fbcb 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedContentSettings.md +++ b/exchange/exchange-ps/exchange/New-ManagedContentSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-managedcontentsettings +online version: https://learn.microsoft.com/powershell/module/exchange/new-managedcontentsettings applicable: Exchange Server 2010 title: New-ManagedContentSettings schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-ManagedContentSettings @@ -17,18 +16,24 @@ This cmdlet is available only in Exchange Server 2010. Use the New-ManagedContentSettings cmdlet to create managed content settings for managed folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` New-ManagedContentSettings [-Name] -FolderName -MessageClass - [-AddressForJournaling ] [-AgeLimitForRetention ] [-Confirm] - [-DomainController ] [-JournalingEnabled ] [-LabelForJournaling ] - [-MessageFormatForJournaling ] [-MoveToDestinationFolder ] - [-Organization ] + [-AddressForJournaling ] + [-AgeLimitForRetention ] + [-Confirm] + [-DomainController ] + [-JournalingEnabled ] + [-LabelForJournaling ] + [-MessageFormatForJournaling ] + [-MoveToDestinationFolder ] [-RetentionAction ] - [-RetentionEnabled ] [-TriggerForRetention ] [-WhatIf] + [-RetentionEnabled ] + [-TriggerForRetention ] + [-WhatIf] [] ``` @@ -36,12 +41,11 @@ New-ManagedContentSettings [-Name] -FolderName - Managed content settings are settings that you associate with managed folders to control the lifespan of items in users' mailboxes. Lifespan is controlled in the following ways: - By controlling content retention and removing content that's no longer needed. - - By automatically journaling important content to a separate storage location outside the mailbox. -For more information about managed content settings, see [Messaging Records Management](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb123507(v=exchg.141)). +For more information about managed content settings, see [Messaging Records Management](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123507(v=exchg.141)). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,6 +65,22 @@ This example creates managed content settings CS-Exec-Calendar for the Calendar ## PARAMETERS +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -FolderName The FolderName parameter specifies the name or GUID of the managed folder to which the managed content settings apply. @@ -83,41 +103,27 @@ The MessageClass parameter specifies the message type to which any expiration an 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: - For All mailbox content, use the value \*. - - For the Calendar items message type, use the value IPM.Appointment\*. - - For the Contacts message type, use the value IPM.Contact\*. - - For the Documents message type, use the value IPM.Document\*. - - For the Faxes message type, use the value IPM.Note.Microsoft.Fax. - - For the Journalitems message type, use the value IPM.Activity. - - For the Meeting requests, responses, and cancellations message type, use the value IPM.Schedule\*. - - For the Notes message type, use the value IPM.StickyNote. - - For the Posts message type, use the value IPM.Post. - - For the RSS items message type, use the value IPM.Post.RSS. - - For the Tasks message type, use the value IPM.Task\*. - - For the Voice mail message type, use the value IPM.Note.Microsoft.Voicemail\*. Valid parameter values for custom message classes include: - A specific message class (for example, IPM.NOTE). - - The asterisk (\*) wildcard character, which indicates that the content settings apply to all message classes. - - A specific message class that has the asterisk wildcard character. The asterisk wildcard character must appear as the last character in the message class. For example, IPM.NOTE\* (includes IPM.NOTE and all subclasses) or IPM.NOTE.\* (includes the subclasses for IPM.NOTE but not IPM.NOTE itself). \*.NOTE and IPM.\*.NOTE aren't valid values. -Notes: +**Notes**: - When wildcard characters are used, these policies apply only to message classes that don't have a specific content setting. Therefore, IPM.NOTE.SMIME overrides IPM.NOTE.\*. - - Specific settings supersede general settings, for example, Voicemail supersedes AllMailboxContent. ```yaml @@ -133,35 +139,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -AddressForJournaling 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID This parameter is required if the JournalingEnabled parameter is set to $true. @@ -198,8 +183,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -267,7 +251,6 @@ Accept wildcard characters: False The MessageFormatForJournaling parameter specifies the message format that an item should be journaled in. You can use the following values: - UseMsg Outlook .msg format - - UseTnef Outlook MAPI format ```yaml @@ -301,33 +284,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Organization -This parameter is reserved for internal Microsoft use. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -RetentionAction The RetentionAction parameter specifies one of the following actions: - Mark as past retention limit - - Move to a managed custom folder - - Move to the Deleted Items folder - - Delete and allow recovery - - Permanently delete If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. @@ -367,7 +330,6 @@ The TriggerForRetention parameter specifies the date that's considered as the st Valid values include: - WhenDelivered - - WhenMoved This value corresponds to the 0x4 bit of the msExchELCFlags attribute in Active Directory. The flag is set to $true if the item will expire based on the date it was moved and $false if the item will expire based on the delivery date. @@ -408,12 +370,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedFolder.md b/exchange/exchange-ps/exchange/New-ManagedFolder.md similarity index 85% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedFolder.md rename to exchange/exchange-ps/exchange/New-ManagedFolder.md index 7e1a117f15..da5d39bc23 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedFolder.md +++ b/exchange/exchange-ps/exchange/New-ManagedFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-managedfolder +online version: https://learn.microsoft.com/powershell/module/exchange/new-managedfolder applicable: Exchange Server 2010 title: New-ManagedFolder schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-ManagedFolder @@ -19,7 +18,7 @@ Use the New-ManagedFolder cmdlet to create a managed folder object for messaging This command doesn't accept pipelined input. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,39 +31,37 @@ New-ManagedFolder [-Name] -DefaultFolderType [-DomainController ] [-LocalizedComment ] [-MustDisplayCommentEnabled ] - [-Organization ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ManagedCustomFolder ``` -New-ManagedFolder [-Name] -FolderName [-LocalizedFolderName ] [-StorageQuota ] +New-ManagedFolder [-Name] -FolderName + [-LocalizedFolderName ] + [-StorageQuota ] [-BaseFolderOnly ] [-Comment ] [-Confirm] [-DomainController ] [-LocalizedComment ] [-MustDisplayCommentEnabled ] - [-Organization ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The New-ManagedFolder cmdlet creates a new managed folder in Active Directory. After a new managed folder object is created, the following steps need to be taken to use it for MRM: -- Create managed content settings for the folder. For information, see [Create Managed Content Settings](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/aa997968(v=exchg.141)). - +- Create managed content settings for the folder. For information, see [Create Managed Content Settings](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/aa997968(v=exchg.141)). - Link the managed folder to an existing managed folder mailbox policy or create a managed folder mailbox policy and link the managed folder to it. - - Apply a managed folder mailbox policy to a user's mailbox. For information, seeApply a Managed Folder Mailbox Policy to Users. - -- Ensure the managed folder assistant is scheduled or run the managed folder assistant manually. For information about scheduling the managed folder assistant, see [Configure the Managed Folder Assistant](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb123958(v=exchg.141)). When the managed folder assistant runs, it configures default folders as managed and creates any managed custom folders in the user's mailbox with the settings specified. - -- For more information about the steps to implement MRM in Microsoft Exchange Server 2010, see [Deploying Messaging Records Management](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb123548(v=exchg.141)). +- Ensure the managed folder assistant is scheduled or run the managed folder assistant manually. For information about scheduling the managed folder assistant, see [Configure the Managed Folder Assistant](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123958(v=exchg.141)). When the managed folder assistant runs, it configures default folders as managed and creates any managed custom folders in the user's mailbox with the settings specified. +- For more information about the steps to implement MRM in Microsoft Exchange Server 2010, see [Deploying Messaging Records Management](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123548(v=exchg.141)). By default, managed custom folders are created with this cmdlet. However, you can also create additional copies of managed default folders using the DefaultFolderType parameter to specify which type of default folder to create (for example, an additional Inbox folder). When you create multiple copies of a managed default folder, you can assign different content settings to each one. For example, you could have two Inbox folders, one named InboxSixMonths and another named InboxOneYear. Then, you could assign a retention time of six months to the first folder and one year to the second folder with the New-ManagedContentSettings cmdlet (or using the New Managed Content Settings wizard in the Exchange Management Console). You must assign a unique name (using the Name parameter) to each of the managed default folders that you create. Users, however, always see the unaltered default folder name. In the example, whether users are assigned an InboxSixMonths folder or an InboxOneYear folder, the Inbox that they see in their mailbox is labeled Inbox. Although the folder names that users see in their mailboxes can be reassigned for managed custom folders (using the Set-ManagedFolder command FolderName parameter), the folder names seen by users for managed default folders can't be changed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -91,6 +88,24 @@ This example creates an instance of the default folder Inbox. ## PARAMETERS +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DefaultFolderType The DefaultFolderType parameter specifies the type of default folder to create, such as Inbox or Deleted Items. @@ -103,35 +118,20 @@ If a value isn't entered for the DefaultFolderType parameter, it's treated as a The default folder types that you can specify are: - Calendar - - Contacts - - DeletedItems - - Drafts - - Inbox - - JunkEmail - - Journal - - Notes - - Outbox - - SentItems - - Tasks - - All - - ManagedCustomFolder - - RssSubscriptions - - SyncIssues - - ConversationHistory ```yaml @@ -165,24 +165,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -BaseFolderOnly 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. @@ -218,8 +200,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -299,24 +280,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Organization -This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see [Multi-Tenant Support](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/ff923272(v=exchg.141)). - -The Organization parameter specifies the organization in which you'll perform this action. This parameter doesn't accept wildcard characters, and you must use the exact name of the organization. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -StorageQuota 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. @@ -354,12 +317,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/New-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/exchange/New-ManagedFolderMailboxPolicy.md new file mode 100644 index 0000000000..0a4c872b09 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ManagedFolderMailboxPolicy.md @@ -0,0 +1,148 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ManagedFolderMailboxPolicy + +## SYNOPSIS +This cmdlet is available only in Exchange Server 2010. + +Use the New-ManagedFolderMailboxPolicy cmdlet to create a managed folder mailbox policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ManagedFolderMailboxPolicy [-Name] + [-Confirm] + [-DomainController ] + [-ManagedFolderLinks ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Managed folder mailbox policies are applied to user mailboxes to control message retention settings. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +Managed custom folders are a premium feature of messaging records management (MRM). Mailboxes with policies that include managed custom folders require an Exchange Server Enterprise client access license (CAL). + +## EXAMPLES + +### Example 1 +```powershell +New-ManagedFolderMailboxPolicy -Name "My Managed Folder Mailbox Policy" -ManagedFolderLinks Inbox, MyFolder +``` + +This example creates the managed folder mailbox policy My Managed Folder Mailbox Policy, with a list of managed folders to which the managed folder mailbox policy is to be linked. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedFolderLinks +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/role-based-access-control/New-ManagementRole.md b/exchange/exchange-ps/exchange/New-ManagementRole.md similarity index 79% rename from exchange/exchange-ps/exchange/role-based-access-control/New-ManagementRole.md rename to exchange/exchange-ps/exchange/New-ManagementRole.md index f060dc6277..84f1b34a67 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/New-ManagementRole.md +++ b/exchange/exchange-ps/exchange/New-ManagementRole.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/new-managementrole +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-ManagementRole @@ -17,28 +16,32 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-ManagementRole cmdlet to create a management role based on an existing role or create an unscoped management role. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### NewDerivedRole ``` -New-ManagementRole [-Name] -Parent [-EnabledCmdlets ] +New-ManagementRole [-Name] -Parent + [-EnabledCmdlets ] [-Confirm] [-Description ] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UnScopedTopLevelRole ``` -New-ManagementRole [-Name] [-UnScopedTopLevel] +New-ManagementRole [-Name] + [-UnScopedTopLevel] [-Confirm] [-Description ] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -46,32 +49,31 @@ You can either create a management role based on an existing role, or you can cr An unscoped role doesn't have any scope restrictions applied. Scripts or third-party cmdlets included in an unscoped role can view or modify any object in the Exchange organization. -The ability to create an unscoped management role isn't granted by default. To create an unscoped management role, you must assign the Unscoped Role Management management role to a role group you're a member of. For more information about how to create an unscoped management role, see [Create an unscoped role](https://docs.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). +The ability to create an unscoped management role isn't granted by default. To create an unscoped management role, you must assign the management role named Unscoped Role Management to a role group you're a member of. For more information about how to create an unscoped management role, see [Create an unscoped role](https://learn.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). After you create a role, you can change the management role entries on the role and assign the role with a management scope to a user or universal security group (USG). -For more information about management roles, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-ManagementRole -Name "Redmond Journaling View-Only" -Parent Journaling; Get-ManagementRoleEntry "Redmond Journaling View-Only\*" | Where { $_.Name -NotLike "Get*" } | Remove-ManagementRoleEntry -WhatIf +New-ManagementRole -Name "Redmond Journaling View-Only" -Parent Journaling + +Get-ManagementRoleEntry "Redmond Journaling View-Only\*" | Where { $_.Name -NotLike "Get*" } | %{Remove-ManagementRoleEntry -Identity "$($_.id)\$($_.name)"} ``` This example creates the management role Redmond Journaling View-Only based on the Journaling parent role. -After the role is created, the Remove-ManagementRoleEntry cmdlet is used along with the Where cmdlet to remove all the management role entries that aren't needed on the role. You can't add role entries to the newly created role because it already has all the role entries that exist on its parent role, Journaling. The WhatIf switch is used to verify that the correct role entries are removed. - -After confirmation that the command removes the correct role entries, the second command is run again without the WhatIf switch. +After the role is created, the Remove-ManagementRoleEntry cmdlet is used along with the Where cmdlet to remove all the management role entries that aren't needed on the role. You can't add role entries to the newly created role because it already has all the role entries that exist on its parent role, Journaling. For more information about pipelining and the Where cmdlet, see the following topics: -- [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) - -- [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help) +- [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) +- [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help) ### Example 2 ```powershell @@ -115,13 +117,13 @@ Accept wildcard characters: False ``` ### -UnScopedTopLevel -This parameter is available on in on-premises Exchange. +This parameter is available only in on-premises Exchange. -By default, this parameter is only available 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +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). The UnScopedTopLevel switch specifies that the role new role is an unscoped top-level management role (a custom, empty role). You don't need to specify a value with this switch. -You can only add custom scripts or non-Exchange cmdlets to an unscoped top-level management role. For more information, see [Create an unscoped role](https://docs.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). +Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. For more information, see [Create an unscoped role](https://learn.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). You can't use this switch with the Parent parameter. @@ -141,8 +143,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -213,7 +214,9 @@ Accept wildcard characters: False ### -Force This parameter is available only in the cloud-based service. -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. +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. ```yaml Type: SwitchParameter @@ -249,12 +252,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/New-ManagementRoleAssignment.md b/exchange/exchange-ps/exchange/New-ManagementRoleAssignment.md similarity index 75% rename from exchange/exchange-ps/exchange/role-based-access-control/New-ManagementRoleAssignment.md rename to exchange/exchange-ps/exchange/New-ManagementRoleAssignment.md index 80609a9054..9cd0581b13 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/New-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/exchange/New-ManagementRoleAssignment.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/new-managementroleassignment +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-ManagementRoleAssignment @@ -17,10 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-ManagementRoleAssignment cmdlet to assign a management role to a management role group, management role assignment policy, user, or universal security group (USG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX +### App +``` +New-ManagementRoleAssignment [[-Name] ] -Role -App [-CustomResourceScope ] + [-Confirm] + [-Delegating] + [-Force] + [-RecipientAdministrativeUnitScope ] + [-RecipientGroupScope ] + [-WhatIf] + [] +``` + ### Computer ``` New-ManagementRoleAssignment [[-Name] ] -Computer -Role @@ -30,11 +41,14 @@ New-ManagementRoleAssignment [[-Name] ] -Computer [-DomainController ] [-ExclusiveConfigWriteScope ] [-ExclusiveRecipientWriteScope ] + [-Force] [-RecipientAdministrativeUnitScope ] + [-RecipientGroupScope ] [-RecipientOrganizationalUnitScope ] [-RecipientRelativeWriteScope ] [-UnScopedTopLevel] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Policy @@ -48,15 +62,18 @@ New-ManagementRoleAssignment [[-Name] ] -Policy ] [-Force] [-RecipientAdministrativeUnitScope ] + [-RecipientGroupScope ] [-RecipientOrganizationalUnitScope ] [-RecipientRelativeWriteScope ] [-UnScopedTopLevel] - [-WhatIf] [] + [-WhatIf] + [] ``` ### SecurityGroup ``` -New-ManagementRoleAssignment [[-Name] ] -Role -SecurityGroup [-Delegating] +New-ManagementRoleAssignment [[-Name] ] -Role -SecurityGroup + [-Delegating] [-Confirm] [-CustomConfigWriteScope ] [-CustomRecipientWriteScope ] @@ -65,15 +82,18 @@ New-ManagementRoleAssignment [[-Name] ] -Role -Securit [-ExclusiveRecipientWriteScope ] [-Force] [-RecipientAdministrativeUnitScope ] + [-RecipientGroupScope ] [-RecipientOrganizationalUnitScope ] [-RecipientRelativeWriteScope ] [-UnScopedTopLevel] - [-WhatIf] [] + [-WhatIf] + [] ``` ### User ``` -New-ManagementRoleAssignment [[-Name] ] -Role -User [-Delegating] +New-ManagementRoleAssignment [[-Name] ] -Role -User + [-Delegating] [-Confirm] [-CustomConfigWriteScope ] [-CustomRecipientWriteScope ] @@ -82,10 +102,12 @@ New-ManagementRoleAssignment [[-Name] ] -Role -User ] [-Force] [-RecipientAdministrativeUnitScope ] + [-RecipientGroupScope ] [-RecipientOrganizationalUnitScope ] [-RecipientRelativeWriteScope ] [-UnScopedTopLevel] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -93,9 +115,9 @@ When you add a new role assignment, you can specify a built-in or custom role th You can create custom management scopes using the New-ManagementScope cmdlet and can view a list of existing scopes using the Get-ManagementScope cmdlet. If you choose not to specify an OU, or predefined or custom scope, the implicit write scope of the role applies to the role assignment. -For more information about management role assignments, see [Understanding management role assignments](https://docs.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). +For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -108,7 +130,9 @@ This example assigns the Mail Recipients role to the Tier 2 Help Desk role group ### Example 2 ```powershell -Get-ManagementRole "MyVoiceMail" | Format-Table Name, IsEndUserRole; New-ManagementRoleAssignment -Role "MyVoiceMail" -Policy "Sales end-users" +Get-ManagementRole "MyVoiceMail" | Format-Table Name, IsEndUserRole + +New-ManagementRoleAssignment -Role "MyVoiceMail" -Policy "Sales end-users" ``` This example assigns the MyVoiceMail role to the "Sales end-users" role assignment policy. First, the IsEndUserRole property on the MyVoiceMail role is verified to be sure it's set to $true, indicating it's an end-user role. @@ -168,12 +192,34 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -App +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). + +For more information about service principals, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). + +You can't use this parameter with the SecurityGroup, Policy, or User cmdlets. + +```yaml +Type: ServicePrincipalIdParameter +Parameter Sets: App +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Computer This parameter is available only in on-premises Exchange. The Computer parameter specifies the name of the computer to assign the management role to. -If you specify the Computer parameter, you can't specify the SecurityGroup, User, or Policy parameters. +You can't use this parameter with the SecurityGroup, User, or Policy parameters. ```yaml Type: ComputerIdParameter @@ -189,11 +235,11 @@ Accept wildcard characters: False ``` ### -Policy -The Policy parameter specifies the name of the management role assignment policy to assign the management role to. +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. -If you specify the Policy parameter, you can't specify the SecurityGroup, Computer, or User parameters. If the policy name contains spaces, enclose the name in quotation marks ("). +You can't use this parameter with the App, SecurityGroup, Computer, or User parameters. ```yaml Type: MailboxPolicyIdParameter @@ -209,7 +255,15 @@ Accept wildcard characters: False ``` ### -Role -The Role parameter specifies the existing role to assign. If the role name contains spaces, enclose the name in quotation marks ("). +The Role parameter specifies the existing role to assign. You can use any value that uniquely identifies the role. For example: + +- Name +- Distinguished name (DN) +- GUID + +If the value contains spaces, enclose the value in quotation marks ("). + +If you use the App parameter, you can't specify admin or user roles; you can only specify application roles (for example, "Application Mail.Read"). ```yaml Type: RoleIdParameter @@ -225,9 +279,9 @@ Accept wildcard characters: False ``` ### -SecurityGroup -The SecurityGroup parameter specifies the name of the management role group or universal USG to assign the management role to. +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 ("). -If you specify the SecurityGroup parameter, you can't specify the Policy, Computer, or User parameters. If the role group or USG name contains spaces, enclose the name in quotation marks ("). +You can't use this parameter with the App, Policy, Computer, or User parameters. ```yaml Type: SecurityGroupIdParameter @@ -243,9 +297,14 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the name or alias of the user to assign the management role to. +The User parameter specifies the user to assign the management role to. + +For the best results, we recommend using the following values: -If you specify the User parameter, you can't specify the SecurityGroup, Computer, or Policy parameters. If the value contains spaces, enclose the name in quotation marks ("). +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +You can't use this parameter with the App, SecurityGroup, Computer, or Policy parameters. ```yaml Type: UserIdParameter @@ -263,8 +322,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -287,7 +345,7 @@ The CustomConfigWriteScope parameter specifies the existing configuration scope ```yaml Type: ManagementScopeIdParameter -Parameter Sets: (All) +Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -303,7 +361,7 @@ The CustomRecipientWriteScope parameter specifies the existing recipient-based m ```yaml Type: ManagementScopeIdParameter -Parameter Sets: (All) +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 @@ -314,12 +372,38 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -CustomResourceScope +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: + +- Name +- Distinguished name (DN) +- GUID + +If the value contains spaces, enclose the value in quotation marks ("). + +You use this parameter with the App parameter to assign permissions to service principals. For more information, see For more information about service principals, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). + +```yaml +Type: ManagementScopeIdParameter +Parameter Sets: App +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Delegating -The Delegating parameter specifies whether the user or USG assigned to the role can delegate the role to other users or groups. You don't have to specify a value with the Delegating parameter. +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 +Parameter Sets: SecurityGroup, User, App Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection @@ -337,7 +421,7 @@ The DomainController parameter specifies the domain controller that's used by th ```yaml Type: Fqdn -Parameter Sets: (All) +Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -355,7 +439,7 @@ The ExclusiveConfigWriteScope parameter specifies the exclusive configuration-ba ```yaml Type: ManagementScopeIdParameter -Parameter Sets: (All) +Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -371,7 +455,7 @@ The ExclusiveRecipientWriteScope parameter specifies the exclusive recipient-bas ```yaml Type: ManagementScopeIdParameter -Parameter Sets: (All) +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 @@ -385,11 +469,13 @@ Accept wildcard characters: False ### -Force This parameter is available only in the cloud-based service. -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. +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. ```yaml Type: SwitchParameter -Parameter Sets: Policy, SecurityGroup, User +Parameter Sets: (All) Aliases: Applicable: Exchange Online, Exchange Online Protection @@ -401,15 +487,35 @@ Accept wildcard characters: False ``` ### -RecipientAdministrativeUnitScope +This parameter is functional only in the cloud-based service. + The RecipientAdministrativeUnitScope parameter specifies the administrative unit to scope the new role assignment to. -Administrative units are Azure Active Directory containers of resources. You can view the available administrative units by using the Get-AdministrativeUnit cmdlet. +Administrative units are Microsoft Entra containers of resources. You can view the available administrative units by using the Get-AdministrativeUnit cmdlet. ```yaml Type: AdministrativeUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientGroupScope +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. + +```yaml +Type: GroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -423,7 +529,7 @@ The RecipientOrganizationalUnitScope parameter specifies the OU to scope the new ```yaml Type: OrganizationalUnitIdParameter -Parameter Sets: (All) +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 @@ -441,7 +547,7 @@ Even though the NotApplicable, OU, MyDirectReports, CustomRecipientScope, MyExec ```yaml Type: RecipientWriteScopeType -Parameter Sets: (All) +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 @@ -453,19 +559,19 @@ Accept wildcard characters: False ``` ### -UnScopedTopLevel -This parameter is available on in on-premises Exchange. +This parameter is available only in on-premises Exchange. -By default, this parameter is only available 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +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). The UnScopedTopLevel switch specifies that the role provided with the Role parameter is an unscoped top-level management role. You don't need to specify a value with this switch. -Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. For more information, see [Create an unscoped role](https://docs.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). +Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. For more information, see [Create an unscoped role](https://learn.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). ```yaml Type: SwitchParameter -Parameter Sets: (All) +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -495,12 +601,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/New-ManagementScope.md b/exchange/exchange-ps/exchange/New-ManagementScope.md similarity index 81% rename from exchange/exchange-ps/exchange/role-based-access-control/New-ManagementScope.md rename to exchange/exchange-ps/exchange/New-ManagementScope.md index 0fc4e808f6..c2fcc0e2d9 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/New-ManagementScope.md +++ b/exchange/exchange-ps/exchange/New-ManagementScope.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/new-managementscope +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-ManagementScope @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-ManagementScope cmdlet to create a regular or exclusive management scope. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,7 +27,8 @@ New-ManagementScope [-Name] -DatabaseList [-DomainController ] [-Exclusive] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### DatabaseFilter @@ -38,7 +38,8 @@ New-ManagementScope [-Name] -DatabaseRestrictionFilter [-DomainController ] [-Exclusive] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RecipientFilter @@ -49,7 +50,8 @@ New-ManagementScope [-Name] -RecipientRestrictionFilter [-Exclusive] [-Force] [-RecipientRoot ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ServerList @@ -59,7 +61,8 @@ New-ManagementScope [-Name] -ServerList [-DomainController ] [-Exclusive] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ServerFilter @@ -69,15 +72,16 @@ New-ManagementScope [-Name] -ServerRestrictionFilter [-DomainController ] [-Exclusive] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -After you create a regular or exclusive scope, you need to associate the scope with a management role assignment. To associate a scope with a role assignment, use the New-ManagementRoleAssignment cmdlet. For more information about adding new management scopes, see [Create a regular or exclusive scope](https://docs.microsoft.com/exchange/create-a-regular-or-exclusive-scope-exchange-2013-help). +After you create a regular or exclusive scope, you need to associate the scope with a management role assignment. To associate a scope with a role assignment, use the New-ManagementRoleAssignment cmdlet. For more information about adding new management scopes, see [Create a regular or exclusive scope](https://learn.microsoft.com/exchange/create-a-regular-or-exclusive-scope-exchange-2013-help). -For more information about regular and exclusive scopes, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -93,7 +97,7 @@ This example creates a scope that includes only the servers MailboxServer1, Mail New-ManagementScope -Name "Redmond Site Scope" -ServerRestrictionFilter "ServerSite -eq 'CN=Redmond,CN=Sites,CN=Configuration,DC=contoso,DC=com'" ``` -This example creates the Redmond Site Scope scope and sets a server restriction filter that matches only the servers located in the "CN=Redmond,CN=Sites,CN=Configuration,DC=contoso,DC=com" Active Directory Domain Services (AD DS) site. +This example creates the scope named Redmond Site Scope and sets a server restriction filter that matches only the servers located in the "CN=Redmond,CN=Sites,CN=Configuration,DC=contoso,DC=com" Active Directory Domain Services (AD DS) site. ### Example 3 ```powershell @@ -104,7 +108,9 @@ This example creates the Executive Mailboxes scope. Only mailboxes located withi ### Example 4 ```powershell -New-ManagementScope -Name "Protected Exec Users" -RecipientRestrictionFilter "Title -like '*VP*'" -Exclusive; New-ManagementRoleAssignment -SecurityGroup "Executive Administrators" -Role "Mail Recipients" -CustomRecipientWriteScope "Protected Exec Users" +New-ManagementScope -Name "Protected Exec Users" -RecipientRestrictionFilter "Title -like 'VP*'" -Exclusive + +New-ManagementRoleAssignment -SecurityGroup "Executive Administrators" -Role "Mail Recipients" -CustomRecipientWriteScope "Protected Exec Users" ``` This example creates the Protected Exec Users exclusive scope. Users that contain the string "VP" in their title match the recipient filter for the scope. When the exclusive scope is created, all users are immediately blocked from modifying the recipients that match the exclusive scope until the scope is associated with a management role assignment. If other role assignments are associated with other exclusive scopes that match the same recipients, those assignments can still modify the recipients. @@ -142,12 +148,10 @@ 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: - Name - - Distinguished name (DN) - - GUID -You can specify multiple values separated by commas. If the values contain spaces, use the following syntax: \"","\",..."\". +You can specify multiple values separated by commas. If the values contain spaces, use the following syntax: `"Value1","Value2",..."ValueN"`. You can't use this parameter with the DatabaseRestrictionFilter, ServerList, RecipientRestrictionFilter, RecipientRoot, or ServerRestrictionFilter parameters. @@ -167,19 +171,16 @@ Accept wildcard characters: False ### -DatabaseRestrictionFilter 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'"`. - -- 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. - -- Property is a filterable property. For a list of filterable database properties, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +The DatabaseRestrictionFilter parameter uses OPATH filter syntax to specify the databases that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For a list of filterable database properties, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter with the RecipientRestrictionFilter, ServerRestrictionFilter, RecipientRoot, DatabaseList, or ServerList parameters. @@ -197,19 +198,16 @@ Accept wildcard characters: False ``` ### -RecipientRestrictionFilter -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. - -- Property is a filterable property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). +The RecipientRestrictionFilter parameter uses OPATH filter syntax to specify the recipients that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter with the DatabaseRestrictionFilter, DatabaseList, ServerList, or ServerRestrictionFilter parameters. @@ -232,14 +230,11 @@ 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN -You can specify multiple values separated by commas. If the values contains spaces or otherwise require quotation marks, use the following syntax: "\","\,"..."\". +You can specify multiple values separated by commas. If the values contains spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. You can't use this parameter with the RecipientRestrictionFilter, RecipientRoot, DatabaseRestrictionFilter, DatabaseList, or ServerRestrictionFilter parameters. @@ -259,19 +254,16 @@ Accept wildcard characters: False ### -ServerRestrictionFilter 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'"`. - -- 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. - -- Property is a filterable property. For a list of filterable server properties, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). +The ServerRestrictionFilter parameter uses OPATH filter syntax to specify the servers that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For a list of filterable server properties, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter wit the RecipientRestrictionFilter, RecipientRoot, DatabaseRestrictionFilter, DatabaseList, or ServerList parameters. @@ -291,8 +283,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -327,7 +318,7 @@ Accept wildcard characters: False ``` ### -Exclusive -The Exclusive switch specifies that the role should be an exclusive scope. +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. @@ -345,7 +336,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch specifies that an exclusive scope should be created without showing the warning that the exclusive scope takes effect immediately. +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. ```yaml Type: SwitchParameter @@ -364,11 +357,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID You can't use this parameter with the ServerRestrictionFilter or DatabaseRestrictionFilter parameters. @@ -407,14 +397,15 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 +Use two-letter country codes (ISO 3166-1 alpha-2) instead of the full country name in filters. For example, use `-RecipientRestrictionFilter "UsageLocation -eq 'FR'"` for France. ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-MapiVirtualDirectory.md b/exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/New-MapiVirtualDirectory.md rename to exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md index 9ea53f0df8..54765cae91 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-mapivirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-MapiVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-MapiVirtualDirectory cmdlet to create Messaging Application Programming Interface (MAPI) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -34,11 +33,12 @@ New-MapiVirtualDirectory [-Role ] [-Server ] [-WebSiteName ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,8 +49,7 @@ New-MapiVirtualDirectory -InternalUrl https://contoso.com/mapi -IISAuthenticatio This example creates a new MAPI virtual directory that has the following configuration: -- Internal URL: https://contoso.com/mapi - +- Internal URL: `https://contoso.com/mapi` - IIS authentication methods: NTLM, Negotiate and OAuth. ## PARAMETERS @@ -58,8 +57,7 @@ This example creates a new MAPI virtual directory that has the following configu ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -92,25 +90,19 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionFlags -This parameter is available only in Exchange 2013. - The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -120,19 +112,16 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionSPNList -This parameter is available only in Exchange 2013. - 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -142,25 +131,19 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionTokenChecking -This parameter is available only in Exchange 2013. - 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,7 +155,7 @@ Accept wildcard characters: False ### -ExternalUrl 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. +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`. When you use the InternalUrl or ExternalUrl parameters, you need to specify one or more authentication values by using the IISAuthenticationMethods parameter. @@ -193,17 +176,16 @@ Accept wildcard characters: False 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 - - Negotiate - - NTLM - - OAuth You can specify multiple values separated by commas. The default values are NTLM, OAuth, and Negotiate. We recommend that you always have the virtual directory configured for OAuth. +For more information about the different authentication methods, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication) and [What is OAuth authentication?](https://learn.microsoft.com/exchange/using-oauth-authentication-to-support-ediscovery-in-an-exchange-hybrid-deployment-exchange-2013-help#what-is-oauth-authentication). + ```yaml Type: MultiValuedProperty Parameter Sets: (All) @@ -220,7 +202,7 @@ Accept wildcard characters: False ### -InternalUrl 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. +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`. When you use the InternalUrl or ExternalUrl parameters, you need to specify one or more authentication values by using the IISAuthenticationMethods parameter. @@ -238,12 +220,11 @@ Accept wildcard characters: False ``` ### -Role -This parameter is available only in Exchange 2013. +This parameter is available only in Exchange Server 2013. 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. - - Mailbox: Configure the virtual directory for the backend services on the Mailbox server. Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. @@ -265,11 +246,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -322,12 +300,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-MessageClassification.md b/exchange/exchange-ps/exchange/New-MessageClassification.md similarity index 88% rename from exchange/exchange-ps/exchange/policy-and-compliance/New-MessageClassification.md rename to exchange/exchange-ps/exchange/New-MessageClassification.md index 3a5f36654b..2692993652 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-MessageClassification.md +++ b/exchange/exchange-ps/exchange/New-MessageClassification.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-messageclassification +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MessageClassification @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MessageClassification cmdlet to create a message classification instance in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ New-MessageClassification [-Name] -DisplayName -Locale ] [-RecipientDescription ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity @@ -40,7 +40,8 @@ New-MessageClassification [-Name] -DisplayName -SenderDescript [-PermissionMenuVisible ] [-RecipientDescription ] [-RetainClassificationEnabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -48,7 +49,7 @@ After you create a new message classification, you can specify the message class When you create a message classification, it has no locale. By default, the new message classification is used for all locales. After a default message classification is defined, you can add new locales of the classification by running the New-MessageClassification cmdlet and by specifying the default message classification identity that you want to localize. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,7 +61,6 @@ New-MessageClassification -Name "My Message Classification" -DisplayName "New Me This example creates the message classification named My Message Classification with the following properties: - The display name is New Message Classification. - - The sender description is "This is the description text". ### Example 2 @@ -107,17 +107,17 @@ Accept wildcard characters: False ``` ### -Locale -This parameter is available or functional on in on-premises Exchange. +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. -A valid value 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://go.microsoft.com/fwlink/p/?linkId=184859). +A valid value 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). ```yaml Type: CultureInfo Parameter Sets: Localized Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -127,7 +127,7 @@ Accept wildcard characters: False ``` ### -SenderDescription -The SenderDescription parameter specifies the 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 ("). +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 @@ -145,7 +145,7 @@ Accept wildcard characters: False ### -ClassificationID 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-MessageCalssification -Identity "\. +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 ""`. ```yaml Type: Guid @@ -163,8 +163,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -184,21 +183,13 @@ Accept wildcard characters: False 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 - - Higher - - High - - MediumHigh - - Medium (This is the default value) - - MediumLow - - Low - - Lower - - Lowest Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. @@ -240,7 +231,6 @@ Accept wildcard characters: False 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. - - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information. ```yaml @@ -257,7 +247,7 @@ Accept wildcard characters: False ``` ### -RecipientDescription -The RecipientDescription parameter specifies the 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 ("). +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. @@ -313,12 +303,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-MigrationBatch.md b/exchange/exchange-ps/exchange/New-MigrationBatch.md new file mode 100644 index 0000000000..e17cdd2090 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-MigrationBatch.md @@ -0,0 +1,2018 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-MigrationBatch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-MigrationBatch cmdlet to submit a new migration request for a batch of users. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Abch +``` +New-MigrationBatch -Name -CSVData [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-DomainController ] + [-Locale ] + [-NotificationEmails ] + [-ReportInterval ] + [-SkipReports] + [-SkipSteps ] + [-StartAfter ] + [-TargetDatabases ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### Analysis +``` +New-MigrationBatch -Name -CSVData [-Analyze] + [-AllowUnknownColumnsInCSV ] + [-AutoComplete] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-ExcludeFolders ] + [-IncludeFolders ] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipDetails] + [-SkipReports] + [-SourceEndpoint ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### FolderMove +``` +New-MigrationBatch -Name -CSVData + [-AllowUnknownColumnsInCSV ] + [-AutoComplete] + [-AutoStart] + [-BadItemLimit ] + [-CompleteAfter ] + [-Confirm] + [-LargeItemLimit ] + [-MoveOptions ] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### GoogleResourceOnboarding +``` +New-MigrationBatch -Name -CSVData + [-AdoptPreexisting] + [-AllowUnknownColumnsInCSV ] + [-AutoComplete] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-GoogleResource] + [-NotificationEmails ] + [-Partition ] + [-RemoveOnCopy] + [-ReportInterval ] + [-SkipDelegates] + [-SkipMerging ] + [-SkipProvisioning] + [-SkipReports] + [-SourceEndpoint ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### Local +``` +New-MigrationBatch [-Local] -Name -CSVData [-DisallowExistingUsers] [-WorkloadType ] [-WorkflowControlFlags ] + [-AdoptPreexisting] + [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-ArchiveOnly] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-BadItemLimit ] + [-CompleteAfter ] + [-Confirm] + [-DomainController ] + [-Locale ] + [-MoveOptions ] + [-NotificationEmails ] + [-Partition ] + [-PrimaryOnly] + [-RemoveOnCopy] + [-ReportInterval ] + [-SkipMoving ] + [-SkipReports] + [-SkipSteps ] + [-StartAfter ] + [-TargetArchiveDatabases ] + [-TargetDatabases ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### LocalPublicFolder +``` +New-MigrationBatch -Name -CSVData -SourcePublicFolderDatabase + [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-BadItemLimit ] + [-CompleteAfter ] + [-Confirm] + [-DomainController ] + [-LargeItemLimit ] + [-Locale ] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipMerging ] + [-SkipReports] + [-SkipSteps ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### ManagedGmailTeams +``` +New-MigrationBatch -Name -CSVData [-ManagedGmailTeams] + [-AdoptPreexisting] + [-AllowUnknownColumnsInCSV ] + [-AutoComplete] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-NotificationEmails ] + [-Partition ] + [-RemoveOnCopy] + [-ReportInterval ] + [-SkipCalendar] + [-SkipContacts] + [-SkipReports] + [-SourceEndpoint ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### Offboarding +``` +New-MigrationBatch -Name -CSVData [-DisallowExistingUsers] + [-AdoptPreexisting] + [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-ArchiveDomain ] + [-ArchiveOnly] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-BadItemLimit ] + [-CompleteAfter ] + [-Confirm] + [-DomainController ] + [-LargeItemLimit ] + [-Locale ] + [-MoveOptions ] + [-NotificationEmails ] + [-Partition ] + [-PrimaryOnly] + [-RemoveOnCopy] + [-ReportInterval ] + [-SkipMerging ] + [-SkipMoving ] + [-SkipReports] + [-SkipSteps ] + [-StartAfter ] + [-TargetArchiveDatabases ] + [-TargetDatabases ] + [-TargetDeliveryDomain ] + [-TargetEndpoint ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### Onboarding +``` +New-MigrationBatch -Name [-CSVData ] [-DisallowExistingUsers] [-WorkflowControlFlags ] + [-AdoptPreexisting] + [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-ArchiveDomain ] + [-ArchiveOnly] + [-AutoComplete] + [-AutoProvisioning] + [-AutoRetryCount ] + [-AutoStart] + [-AvoidMergeOverlap] + [-BadItemLimit ] + [-CompleteAfter ] + [-Confirm] + [-ContentFilter ] + [-ContentFilterLanguage ] + [-DataFusion] + [-DomainController ] + [-ExcludeDumpsters] + [-ExcludeFolders ] + [-ForwardingDisposition ] + [-IncludeFolders ] + [-IncludeOtherContacts] + [-LargeItemLimit ] + [-Locale ] + [-MigrateTasks] + [-MoveOptions ] + [-NotificationEmails ] + [-Partition ] + [-PrimaryOnly] + [-RemoveOnCopy] + [-RenamePrimaryCalendar] + [-ReportInterval ] + [-Restore] + [-SimplifiedSwitchOver] + [-SkipCalendar] + [-SkipContacts] + [-SkipDelegates] + [-SkipMail] + [-SkipMerging ] + [-SkipMoving ] + [-SkipProvisioning] + [-SkipReports] + [-SkipRules] + [-SkipSteps ] + [-SourceEndpoint ] + [-SourcePFPrimaryMailboxGuid ] + [-StartAfter ] + [-TargetArchiveDatabases ] + [-TargetDatabases ] + [-TargetDeliveryDomain ] + [-TimeZone ] + [-WhatIf] + [-XMLData ] + [] +``` + +### PointInTimeRecovery +``` +New-MigrationBatch -Name -CSVData + [-AllowUnknownColumnsInCSV ] + [-AutoComplete] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### PointInTimeRecoveryProvisionOnly +``` +New-MigrationBatch -Name -CSVData + [-AllowUnknownColumnsInCSV ] + [-AutoComplete] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### Preexisting +``` +New-MigrationBatch -Name [-Users] + [-AllowIncrementalSyncs ] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-DisableOnCopy] + [-DomainController ] + [-Locale ] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-SkipSteps ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### PreexistingUserIds +``` +New-MigrationBatch -Name [-UserIds] + [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-DisableOnCopy] + [-DomainController ] + [-Locale ] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-SkipSteps ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### PreexistingUsers +``` +New-MigrationBatch [-Users] MultiValuedProperty> -Name + [-AllowUnknownColumnsInCSV ] + [-AutoComplete] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-DisableOnCopy] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### PublicFolderToUnifiedGroup +``` +New-MigrationBatch -Name -CSVData [-PublicFolderToUnifiedGroup] + [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-BadItemLimit ] + [-CompleteAfter ] + [-Confirm] + [-DomainController ] + [-LargeItemLimit ] + [-Locale ] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-SkipSteps ] + [-SourceEndpoint ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### WorkflowTemplate +``` +New-MigrationBatch -Name [-WorkflowTemplate ] + [-AllowIncrementalSyncs ] + [-AllowUnknownColumnsInCsv ] + [-AutoComplete] + [-AutoRetryCount ] + [-AutoStart] + [-CompleteAfter ] + [-Confirm] + [-DomainController ] + [-Locale ] + [-NotificationEmails ] + [-Partition ] + [-ReportInterval ] + [-SkipReports] + [-SkipSteps ] + [-StartAfter ] + [-TimeZone ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the New-MigrationBatch cmdlet to create a migration batch to migrate mailboxes and mailbox data in one of the following migration scenarios. + +Moves in on-premises Exchange organizations + +- Local move: A local move is where you move mailboxes from one mailbox database to another. A local move occurs within a single forest. For more information, see Example 1. +- Cross-forest enterprise move: In a cross-forest enterprise move, mailboxes are moved to a different forest. Cross-forest moves are initiated either from the target forest, which is the forest that you want to move the mailboxes to, or from the source forest, which is the forest that currently hosts the mailboxes. For more information, see Example 2. + +Onboarding and offboarding in Exchange Online + +- Onboarding remote move migration: In a hybrid deployment, you can move mailboxes from an on-premises Exchange organization to Exchange Online. This is also known as an onboarding remote move migration because you on-board mailboxes to Exchange Online. For more information, see Example 3. +- Offboarding remote move migration: You can also perform an offboarding remote move migration, where you migrate Exchange Online mailboxes to your on-premises Exchange organization. For more information, see Example 4. + + Both onboarding and offboarding remote move migrations are initiated from your Exchange Online organization. + +- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes will be automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5. +- Staged Exchange migration: You can also migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. This is another type of onboarding migration. Migrating mailboxes from Exchange 2010 or later versions of Exchange isn't supported using a staged migration. Prior to running a staged migration, you have to use directory synchronization or some other method to provision mail users in your Exchange Online organization. For more information, see Example 6. +- IMAP migration: This onboarding migration type migrates mailbox data from an IMAP server (including Exchange) to Exchange Online. For an IMAP migration, you must first provision mailboxes in Exchange Online before you can migrate mailbox data. For more information, see Example 7. +- Google Workspace (formerly G Suite) migration: This onboarding migration type migrates mailbox data from a Google Workspace organization to Exchange Online. For a Google Workspace migration, you must first provision mail users (or mailboxes) in Exchange Online before you can migrate mailbox data. For more information, see Example 10. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-MigrationBatch -Local -Name LocalMove1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\LocalMove1.csv")) -TargetDatabases MBXDB2 + +Start-MigrationBatch -Identity LocalMove1 +``` + +This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes that will be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically. + +### Example 2 +```powershell +$Credentials = Get-Credential + +$MigrationEndpointSource = New-MigrationEndpoint -ExchangeRemoteMove -Name Forest1Endpoint -Autodiscover -EmailAddress administrator@forest1.contoso.com -Credentials $Credentials + +$CrossForestBatch = New-MigrationBatch -Name CrossForestBatch1 -SourceEndpoint $MigrationEndpointSource.Identity -TargetDeliveryDomain forest2.contoso.com -TargetDatabases MBXDB1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\CrossForestBatch1.csv")) + +Start-MigrationBatch -Identity $CrossForestBatch.Identity +``` + +This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Note that cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to. + +### Example 3 +```powershell +$Credentials = Get-Credential + +$MigrationEndpointOnPrem = New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials + +$OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $MigrationEndpointOnprem.Identity -TargetDeliveryDomain contoso.mail.onmicrosoft.com -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\RemoteOnBoarding1.csv")) + +Start-MigrationBatch -Identity $OnboardingBatch.Identity.Name +``` + +This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes that will be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. + +### Example 4 +```powershell +$Credentials = Get-Credential + +$MigrationEndpointOnPrem = New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials + +$OffboardingBatch = New-MigrationBatch -Name RemoteOffBoarding1 -TargetEndpoint $MigrationEndpointOnprem.Identity -TargetDeliveryDomain onprem.contoso.com -TargetDatabases @(MBXDB01,MBXDB02,MBXDB03) -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\RemoteOffBoarding1.csv")) + +Start-MigrationBatch -Identity $OffboardingBatch.Identity +``` + +This example creates a migration batch for an offboarding remote move migration from Exchange Online to an on-premises Exchange organization. Like an onboarding remote move, it's initiated from the Exchange Online organization. First a Migration Endpoint is created that contains information about how to connect to the on-premises organization. The endpoint is used as the TargetEndpoint when creating the migration batch, which is then started with the Start-MigrationBatch cmdlet. The TargetDatabases parameter specifies multiple on-premises databases that the migration service can select as the target database to move the mailbox to. + +### Example 5 +```powershell +$credentials = Get-Credential + +$SourceEndpoint = New-MigrationEndpoint -ExchangeOutlookAnywhere -Autodiscover -Name SourceEndpoint -EmailAddress administrator@contoso.com -Credentials $credentials + +New-MigrationBatch -Name CutoverBatch -SourceEndpoint $SourceEndpoint.Identity -TimeZone "Pacific Standard Time" -AutoStart +``` + +This example creates a migration batch for the cutover Exchange migration CutoverBatch that's automatically started. The example obtains the connection settings to the on-premises Exchange server, and then uses those connection settings to create a migration endpoint. The endpoint is then used to create the migration batch. This example also includes the optional TimeZone parameter. + +### Example 6 +```powershell +$Credentials = Get-Credential + +$MigrationEndpoint = New-MigrationEndpoint -ExchangeOutlookAnywhere -Name ContosoEndpoint -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials + +$StagedBatch1 = New-MigrationBatch -Name StagedBatch1 -SourceEndpoint $MigrationEndpoint.Identity -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\StagedBatch1.csv")) + +Start-MigrationBatch -Identity $StagedBatch1.Identity +``` + +This example creates and starts a migration batch for a staged Exchange migration. The example uses the New-MigrationEndpoint cmdlet to create a migration endpoint for the on-premises Exchange server, and then uses that endpoint to create the migration batch. The migration batch is started with the Start-MigrationBatch cmdlet. + +### Example 7 +```powershell +New-MigrationEndpoint -IMAP -Name IMAPEndpoint1 -RemoteServer imap.contoso.com -Port 993 + +New-MigrationBatch -Name IMAPbatch1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\IMAPmigration_1.csv")) -SourceEndpoint IMAPEndpoint1 -ExcludeFolders "Deleted Items","Junk Email" +``` + +This example creates a migration endpoint for the connection settings to the IMAP server. Then an IMAP migration batch is created that uses the CSV migration file IMAPmigration\_1.csv and excludes the contents of the Deleted Items and Junk Email folders. This migration batch is pending until it's started with the Start-MigrationBatch cmdlet. + +### Example 8 +```powershell +$Credentials = Get-Credential + +$MigrationEndpointOnPrem = New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials + +$OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $MigrationEndpointOnprem.Identity -TargetDeliveryDomain contoso.mail.onmicrosoft.com -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\RemoteOnBoarding1.csv")) -CompleteAfter "09/01/2018 7:00 PM" + +Start-MigrationBatch -Identity $OnboardingBatch.Identity +``` + +This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (UTC). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Coordinated Universal Time. + +### Example 9 +```powershell +$Credentials = Get-Credential + +$MigrationEndpointOnPrem = New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials + +$OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $MigrationEndpointOnprem.Identity -TargetDeliveryDomain contoso.mail.onmicrosoft.com -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\RemoteOnBoarding1.csv")) -CompleteAfter "09/01/2018 7:00 PM" -TimeZone "Pacific Standard Time" + +Start-MigrationBatch -Identity $OnboardingBatch.Identity +``` + +This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time. + +### Example 10 +```powershell +$MigrationEndpointGmail = New-MigrationEndpoint -Gmail -ServiceAccountKeyFileData $([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\gmailonboarding.json")) -EmailAddress admin@contoso.com -Name GmailEndpoint + +$OnboardingBatch = New-MigrationBatch -SourceEndpoint $MigrationEndpointGmail.Identity -Name GmailBatch1 -CSVData $([System.IO.File]::ReadAll +Bytes("C:\Users\Administrator\Desktop\gmail.csv")) -TargetDeliveryDomain "o365.contoso.com" -ContentFilter "Received -ge '2019/4/30'" -Inc +ludeFolders "Payment" + +Start-MigrationBatch -Identity $OnboardingBatch.Identity +``` + +A Google Workspace migration batch is created that uses the CSV migration file gmail.csv and includes the contents of the Payment label and only migrate the mails which were received after the time '2019/4/30 00:00' (local system time). This migration batch is pending until it's started with the Start-MigrationBatch cmdlet. + +## PARAMETERS + +### -UserIds +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. + +To disable the migration of the users in the original migration batch, use the DisableOnCopy switch with this parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: PreexistingUserIds +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Users +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 + +New-MigrationBatch -Name "Retry Failed Users" -Users $Failed + +The users that you specify for this parameter must be defined in an existing migration batch. + +To disable the migration of the users in the original migration batch, use the DisableOnCopy switch with this parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Preexisting, PreexistingUsers +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Analyze +This parameter is available only in the cloud-based service. + +{{ Fill Analyze Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Analysis +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedGmailTeams +This parameter is available only in the cloud-based service. + +{{ Fill ManagedGmailTeams Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: ManagedGmailTeams +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CSVData +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`). + +**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. + +```yaml +Type: Byte[] +Parameter Sets: Abch, Analysis, FolderMove, Local, LocalPublicFolder, Offboarding, XO1, PublicFolderToUnifiedGroup, GoogleResourceOnboarding, PointInTimeRecoveryProvisionOnly, PointInTimeRecovery +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +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 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: SwitchParameter +Parameter Sets: Local +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourcePublicFolderDatabase +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: DatabaseIdParameter +Parameter Sets: LocalPublicFolder +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdoptPreexisting +This parameter is available only in the cloud-based service. + +{{ Fill AdoptPreexisting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding, Local, Offboarding, GoogleResourceOnboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowIncrementalSyncs +This parameter is available only in on-premises Exchange. + +The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: + +- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This is the default value. +- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUnknownColumnsInCsv +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. +- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ArchiveDomain +This parameter is available only in the cloud-based service. + +{{ Fill ArchiveDomain Description }} + +```yaml +Type: String +Parameter Sets: Onboarding, Offboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ArchiveOnly +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. + +You can use the TargetArchiveDatabases parameter to specify the database to migrate the archive mailboxes to. You can also specify the target archive database in the CSV file. If you don't specify the target archive database, the cmdlet uses the automatic mailbox distribution logic to select the database. + +```yaml +Type: SwitchParameter +Parameter Sets: Local, Onboarding, Offboarding +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoComplete +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. + +If you don't use this switch, you need to run the Complete-MigrationBatch cmdlet to finalize a migration batch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoProvisioning +This parameter is available only in the cloud-based service. + +{{ Fill AutoProvisioning Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoRetryCount +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoStart +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AvoidMergeOverlap +This parameter is available only in the cloud-based service. + +{{ Fill AvoidMergeOverlap Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BadItemLimit +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. + +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration will use Skipped Item approval semantics instead of BadItemLimit semantics. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompleteAfter +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. + +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". + +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: + +- Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. +- Specify the date/time value in your local time zone: For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentFilter +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: + +- `"Received -gt '8/23/2020'"` +- `"Received -le '2019/01/01'"` +- `"Received -gt '8/23/2015' -and Received -lt '8/23/2020'"` + +You can specify the language by using the ContentFilterLanguage parameter. + +```yaml +Type: String +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentFilterLanguage +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. + +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). + +```yaml +Type: CultureInfo +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DataFusion +This parameter is available only in the cloud-based service. + +{{ Fill DataFusion Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableOnCopy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisallowExistingUsers +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. + +A validation warning is displayed for any pre-existing mailbox in the target destination. + +```yaml +Type: SwitchParameter +Parameter Sets: Local, Onboarding, Offboarding +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeDumpsters +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. + +You use this switch only in public folder migrations from Exchange 2013 or later to Exchange Online. + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeFolders +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. + +For IMAP migration, use folder names relative to the IMAP root on the source mail server. For Google Workspace migration, use label names on the source mail server. + +Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: + +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, `MyProjects` or `MyProjects/FY2010`. + +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: + +- Root +- Inbox +- SentItems +- Outbox +- DeletedItems +- Calendar +- Contacts +- Drafts +- Journal +- Tasks +- Notes +- AllItems +- JunkEmail +- Archive + +If the user creates a personal folder with the same name as a well-known folder and the `#` symbol surrounding it, you can use a backslash (`\`) as an escape character to specify that folder. For example, if a user creates a folder named `#Notes#` and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. + +Wildcard characters can't be used in folder names. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Onboarding, Analysis +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardingDisposition +This parameter is available only in the cloud-based service. + +{{ Fill ForwardingDisposition Description }} + +```yaml +Type: GmailForwardingDisposition +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GoogleResource +{{ Fill GoogleResource Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: GoogleResourceOnboarding +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeFolders +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. + +For IMAP migration, use folder names relative to the IMAP root on the source mail server. For Google Workspace migration, use label names on the source mail server. + +Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: + +`/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, `MyProjects` or `MyProjects/FY2010`. + +`##/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: + +- Root +- Inbox +- SentItems +- Outbox +- DeletedItems +- Calendar +- Contacts +- Drafts +- Journal +- Tasks +- Notes +- AllItems +- JunkEmail +- Archive + +If the user creates a personal folder with the same name as a well-known folder and the `#` symbol surrounding it, you can use a backslash (`\`) as an escape character to specify that folder. For example, if a user creates a folder named `#Notes#` and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`. + +Wildcard characters can't be used in folder names. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Onboarding, Analysis +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeOtherContacts +This parameter is available only in the cloud-based service. + +{{ Fill IncludeOtherContacts Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LargeItemLimit +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: + +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) + +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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. + +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locale +This parameter is available only in on-premises Exchange. + +The Locale parameter specifies the language for the migration batch. + +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrateTasks +This parameter is available only in the cloud-based service. + +{{ Fill MigrateTasks Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MoveOptions +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Onboarding, Local, Offboarding, FolderMove +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationEmails +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Partition +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MailboxIdParameter +Parameter Sets: PreexistingUserIds, Onboarding, Local, Offboarding, PublicFolderToUnifiedGroup, WorkflowTemplate, PreexistingUsers, GoogleResourceOnboarding, FolderMove, Analysis, PointInTimeRecoveryProvisionOnly, PointInTimeRecovery +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimaryOnly +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. + +**Note**: If the users don't have archive mailboxes, don't use this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: Local, Onboarding, Offboarding +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderToUnifiedGroup +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. + +```yaml +Type: SwitchParameter +Parameter Sets: PublicFolderToUnifiedGroup +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOnCopy +This parameter is available only in the cloud-based service. + +{{ Fill RemoveOnCopy Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding, Local, Offboarding, GoogleResourceOnboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RenamePrimaryCalendar +This parameter is available only in the cloud-based service. + +{{ Fill RenamePrimaryCalendar Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportInterval +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. + +This parameter should only be used in the cloud-based service. + +```yaml +Type: TimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Restore +This parameter is available only in the cloud-based service. + +{{ Fill Restore Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SimplifiedSwitchOver +This parameter is available only in the cloud-based service. + +{{ Fill SimplifiedSwitchOver Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipCalendar +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding, ManagedGmailTeams +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipContacts +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding, ManagedGmailTeams +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipDelegates +This parameter is available only in the cloud-based service. + +{{ Fill SkipDelegates Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding, GoogleResourceOnboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipDetails +This parameter is available only in the cloud-based service. + +{{ Fill SkipDetails Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Analysis +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipMail +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipMerging +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipMoving +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Local, Onboarding, Offboarding +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipProvisioning +This parameter is available only in the cloud-based service. + +{{ Fill SkipProvisioning Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding, GoogleResourceOnboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipReports +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipRules +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipSteps +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: + +- None (This is the default value) +- SettingTargetAddress: Don't set the target email address on the source mailbox. This setting prevents mail from being forwarded from the original mailbox to the new migrated mailbox. + +This parameter is only enforced for staged Exchange migrations. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceEndpoint +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) +- GUID + +This parameter defines the settings that are used to connect to the server where the source mailboxes are located. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourcePFPrimaryMailboxGuid +This parameter is available only in the cloud-based service. + +{{ Fill SourcePFPrimaryMailboxGuid Description }} + +```yaml +Type: Guid +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartAfter +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". + +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: + +- Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. + +```yaml +Type: DateTime +Parameter Sets: Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetArchiveDatabases +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 +- Distinguished name (DN) +- GUID + +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"`. + +When you enter multiple values, the migration service selects one database as the target database to move the archive mailbox to. + +You can only use this parameter for local moves and remote move migrations. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Local, Onboarding, Offboarding +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetDatabases +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 +- Distinguished name (DN) +- GUID + +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"`. + +When you enter multiple values, the migration service selects one database as the target database to move the mailbox to. + +You can only use this parameter for local moves and remote move migrations. + +If you don't use this parameter for a local move, the cmdlet uses the automatic mailbox distribution logic to select the database. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetDeliveryDomain +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 + +```yaml +Type: String +Parameter Sets: Onboarding, Offboarding +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetEndpoint +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) +- GUID + +This parameter defines the settings that are used to connect to the destination server where the mailboxes will be moved. + +```yaml +Type: MigrationEndpointIdParameter +Parameter Sets: Offboarding +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeZone +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"`). + +To see the available values, run the following command: `$TimeZone = Get-ChildItem "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Time zones" | foreach {Get-ItemProperty $_.PSPath}; $TimeZone | sort Display | Format-Table -Auto PSChildname,Display`. + +If the value contains spaces, enclose the value in quotation marks ("). + +In on-premises Exchange, the default value is the time zone setting of the Exchange server. + +In Exchange Online, the default value is `UTC`. + +```yaml +Type: ExTimeZoneValue +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkflowControlFlags +The WorkflowControlFlags parameter specifies advanced controls for the steps that are performed in the migration. Valid values are: + +- None (This is the default value) +- InjectAndForget +- SkipSwitchover + +Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. + +```yaml +Type: MigrationWorkflowControlFlags +Parameter Sets: Local, Onboarding +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkflowTemplate +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkloadType +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: RequestWorkloadType +Parameter Sets: Local +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -XMLData +This parameter is available only in the cloud-based service. + +{{ Fill XMLData Description }} + +```yaml +Type: Byte[] +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/move-and-migration/New-MigrationEndpoint.md b/exchange/exchange-ps/exchange/New-MigrationEndpoint.md similarity index 81% rename from exchange/exchange-ps/exchange/move-and-migration/New-MigrationEndpoint.md rename to exchange/exchange-ps/exchange/New-MigrationEndpoint.md index 57ff65eebe..f7429f506d 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/New-MigrationEndpoint.md +++ b/exchange/exchange-ps/exchange/New-MigrationEndpoint.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-migrationendpoint +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MigrationEndpoint @@ -15,27 +14,33 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the New-MigrationEndpoint cmdlet to configure the connection settings for cross-forests moves, remote move migrations, cutover or staged Exchange migrations, IMAP migrations, and G Suite migrations. +Use the New-MigrationEndpoint cmdlet to configure the connection settings for cross-forests moves, remote move migrations, cutover or staged Exchange migrations, IMAP migrations, and Google Workspace (formerly G Suite) migrations. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### ExchangeRemoteMoveAutoDiscover ``` -New-MigrationEndpoint -Name -Credentials -EmailAddress [-Autodiscover] [-ExchangeRemoteMove] +New-MigrationEndpoint -Name -Credentials -EmailAddress + [-Autodiscover] + [-ExchangeRemoteMove] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] [-MaxConcurrentMigrations ] [-Partition ] [-SkipVerification] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ExchangeOutlookAnywhereAutoDiscover ``` -New-MigrationEndpoint -Name -Credentials -EmailAddress [-Autodiscover] [-ExchangeOutlookAnywhere] +New-MigrationEndpoint -Name -Credentials -EmailAddress + [-Autodiscover] + [-ExchangeOutlookAnywhere] + [-AcceptUntrustedCertificates] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] @@ -44,12 +49,17 @@ New-MigrationEndpoint -Name -Credentials -EmailAddress < [-SkipVerification] [-SourceMailboxLegacyDN ] [-TestMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ExchangeOutlookAnywhere ``` -New-MigrationEndpoint -Name -Credentials [-EmailAddress ] [-ExchangeOutlookAnywhere] [-ExchangeServer ] +New-MigrationEndpoint -Name -Credentials + [-EmailAddress ] + [-ExchangeOutlookAnywhere] + [-ExchangeServer ] + [-AcceptUntrustedCertificates] [-Authentication ] [-Confirm] [-DomainController ] @@ -62,36 +72,50 @@ New-MigrationEndpoint -Name -Credentials [-EmailAddress [-SkipVerification] [-SourceMailboxLegacyDN ] [-TestMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ExchangeRemoteMove ``` -New-MigrationEndpoint -Name -RemoteServer [-Credentials ] [-ExchangeRemoteMove] +New-MigrationEndpoint -Name -RemoteServer + [-Credentials ] + [-ExchangeRemoteMove] + [-ApplicationId ] + [-AppSecretKeyVaultUrl ] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] [-MaxConcurrentMigrations ] [-Partition ] + [-RemoteTenant ] [-SkipVerification] - [-WhatIf] [] + [-WhatIf] + [] ``` ### PSTImport ``` -New-MigrationEndpoint -Name -RemoteServer [-Credentials ] [-PSTImport] +New-MigrationEndpoint -Name -RemoteServer + [-Credentials ] + [-PSTImport] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] [-MaxConcurrentMigrations ] [-Partition ] [-SkipVerification] - [-WhatIf] [] + [-WhatIf] + [] ``` ### IMAP ``` -New-MigrationEndpoint -Name -RemoteServer [-IMAP] [-Port ] [-Security ] +New-MigrationEndpoint -Name -RemoteServer + [-IMAP] + [-Port ] + [-Security ] + [-AcceptUntrustedCertificates] [-Authentication ] [-Confirm] [-DomainController ] @@ -99,24 +123,44 @@ New-MigrationEndpoint -Name -RemoteServer [-IMAP] [-Port [-MaxConcurrentMigrations ] [-Partition ] [-SkipVerification] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Gmail ``` -New-MigrationEndpoint -Name -ServiceAccountKeyFileData [-Gmail] [-EmailAddress ] +New-MigrationEndpoint -Name -ServiceAccountKeyFileData + [-Gmail] + [-EmailAddress ] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] [-MaxConcurrentMigrations ] [-Partition ] [-SkipVerification] - [-WhatIf] [] + [-WhatIf] + [] +``` + +### GoogleMarketplaceApp +``` +New-MigrationEndpoint -Name -OAuthCode [-Gmail] + [-Confirm] + [-MaxConcurrentIncrementalSyncs ] + [-MaxConcurrentMigrations ] + [-Partition ] + [-ProgressAction ] + [-RedirectUri ] + [-SkipVerification] + [-TestMailbox ] + [-WhatIf] + [] ``` ### PublicFolder ``` -New-MigrationEndpoint -Name -Credentials -PublicFolderDatabaseServerLegacyDN -RpcProxyServer -SourceMailboxLegacyDN [-PublicFolder] +New-MigrationEndpoint -Name -Credentials -PublicFolderDatabaseServerLegacyDN -RpcProxyServer -SourceMailboxLegacyDN + [-PublicFolder] [-Authentication ] [-Confirm] [-DomainController ] @@ -125,24 +169,28 @@ New-MigrationEndpoint -Name -Credentials -PublicFolderDa [-Partition ] [-SkipVerification] [-TestMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Compliance ``` -New-MigrationEndpoint -Name -Credentials -RemoteServer [-Compliance] +New-MigrationEndpoint -Name -Credentials -RemoteServer + [-Compliance] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] [-MaxConcurrentMigrations ] [-Partition ] [-SkipVerification] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MrsProxyPublicFolderToUnifiedGroup ``` -New-MigrationEndpoint -Name -Credentials -RemoteServer [-PublicFolderToUnifiedGroup] +New-MigrationEndpoint -Name -Credentials -RemoteServer + [-PublicFolderToUnifiedGroup] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] @@ -150,24 +198,28 @@ New-MigrationEndpoint -Name -Credentials -RemoteServer < [-Partition ] [-SkipVerification] [-TestMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MrsProxyPublicFolder ``` -New-MigrationEndpoint -Name -Credentials -RemoteServer [-PublicFolder] +New-MigrationEndpoint -Name -Credentials -RemoteServer + [-PublicFolder] [-Confirm] [-DomainController ] [-MaxConcurrentIncrementalSyncs ] [-MaxConcurrentMigrations ] [-Partition ] [-SkipVerification] - [-WhatIf] [] + [-WhatIf] + [] ``` ### LegacyPublicFolderToUnifiedGroup ``` -New-MigrationEndpoint -Name -Credentials -PublicFolderDatabaseServerLegacyDN -RpcProxyServer -SourceMailboxLegacyDN [-PublicFolderToUnifiedGroup] +New-MigrationEndpoint -Name -Credentials -PublicFolderDatabaseServerLegacyDN -RpcProxyServer -SourceMailboxLegacyDN + [-PublicFolderToUnifiedGroup] [-Authentication ] [-Confirm] [-DomainController ] @@ -176,27 +228,23 @@ New-MigrationEndpoint -Name -Credentials -PublicFolderDa [-Partition ] [-SkipVerification] [-TestMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The New-MigrationEndpoint cmdlet configures the connection settings for different types of migrations: - Cross-forest move: Move mailboxes between two different on-premises Exchange forests. Cross-forest moves require the use of a Remote Move endpoint. - -- Remote move migration: In a hybrid deployment, a remote move migration involves onboarding or offboarding migrations. Remote move migrations also require the use of an Exchange remote move endpoint. Onboarding moves mailboxes from an on-premises Exchange organization to Exchange Online in Office 365, and uses a remote move endpoint as the source endpoint of the migration batch. Offboarding moves mailboxes from Exchange Online in Office 365 to an on-premises Exchange organization and uses a remote move endpoint as the target endpoint of the migration batch. - -- Cutover Exchange migration: Migrate all mailboxes in an on-premises Exchange organization to Exchange Online in Office 365. A cutover Exchange migration requires the use of an Outlook Anywhere migration endpoint. - -- Staged Exchange migration: Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online in Office 365. A staged Exchange migration requires the use of an Outlook Anywhere migration endpoint. - -- IMAP migration: Migrate mailbox data from an on-premises Exchange organization or other email system to Exchange Online in Office 365. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP migrations require the use of an IMAP endpoint. - -- G Suite migration: Migration mailbox data from a G Suite tenant to Exchange Online in Office 365. For a G Suite migration, you must first create cloud-based mail users or mailboxes before you migrate mailbox data. G Suite migrations require the use of a Gmail endpoint. +- Remote move migration: In a hybrid deployment, a remote move migration involves onboarding or offboarding migrations. Remote move migrations also require the use of an Exchange remote move endpoint. Onboarding moves mailboxes from an on-premises Exchange organization to Exchange Online, and uses a remote move endpoint as the source endpoint of the migration batch. Offboarding moves mailboxes from Exchange Online to an on-premises Exchange organization and uses a remote move endpoint as the target endpoint of the migration batch. +- Cutover Exchange migration: Migrate all mailboxes in an on-premises Exchange organization to Exchange Online. A cutover Exchange migration requires the use of an Outlook Anywhere migration endpoint. +- Staged Exchange migration: Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. A staged Exchange migration requires the use of an Outlook Anywhere migration endpoint. +- IMAP migration: Migrate mailbox data from an on-premises Exchange organization or other email system to Exchange Online. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP migrations require the use of an IMAP endpoint. +- Google Workspace migration: Migration mailbox data from a Google Workspace tenant to Exchange Online. For a Google Workspace migration, you must first create cloud-based mail users or mailboxes before you migrate mailbox data. Google Workspace migrations require the use of a Gmail endpoint. Moving mailboxes between different servers or databases within a single on-premises Exchange forest (called a local move) doesn't require a migration endpoint. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -216,7 +264,9 @@ This example creates an endpoint for remote moves by specifying the settings man ### Example 3 ```powershell -$Credentials = Get-Credential; New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH-AutoDiscover -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials +$Credentials = Get-Credential + +New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH-AutoDiscover -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials ``` This example creates an Outlook Anywhere migration endpoint by using the Autodiscover parameter to detect the connection settings to the on-premises organization. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The Get-Credential cmdlet is used to obtain the credentials for an on-premises account that has the necessary administrative privileges in the domain and that can access the mailboxes that will be migrated. When prompted for the user name, you can use either the email address or the domain\\username format for the administrator account. This account can be the same one that is specified by the EmailAddress parameter. @@ -297,7 +347,7 @@ Accept wildcard characters: False ### -Credentials 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -391,7 +441,7 @@ Accept wildcard characters: False ### -Gmail This parameter is available only in the cloud-based service. -The Gmail switch specifies the type of endpoint for G Suite migrations. You don't need to specify a value with this switch. +The Gmail switch specifies the type of endpoint for Google Workspace migrations. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -424,14 +474,34 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -OAuthCode +This parameter is available only in the cloud-based service. + +{{ Fill OAuthCode Description }} + +```yaml +Type: SecureString +Parameter Sets: GoogleMarketplaceApp +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -PSTImport +This parameter is available only in on-premises Exchange. + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: PSTImport Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -477,7 +547,7 @@ Accept wildcard characters: False ``` ### -PublicFolderToUnifiedGroup -The PublicFolderToUnifiedGroup switch specifies that the endpoint type is public folders to Office 365 groups. You don't need to specify a value with this switch. +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 @@ -496,7 +566,6 @@ Accept wildcard characters: False 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. - - For IMAP migrations, this parameter refers to the IMAP server. ```yaml @@ -550,7 +619,7 @@ 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. -Use the following format for the value of this parameter: ([System.IO.File]::ReadAllBytes(\)). For example: -CSVData ([System.IO.File]::ReadAllBytes("C:\\Users\\Administrator\\Desktop\\service-account.json")) +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[] @@ -596,6 +665,60 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AcceptUntrustedCertificates +This parameter is available only in the cloud-based service. + +{{ Fill AcceptUntrustedCertificates Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, IMAP +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplicationId +This parameter is available only in the cloud-based service. + +{{ Fill ApplicationId Description }} + +```yaml +Type: String +Parameter Sets: ExchangeRemoteMove +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppSecretKeyVaultUrl +This parameter is available only in the cloud-based service. + +{{ Fill AppSecretKeyVaultUrl Description }} + +```yaml +Type: String +Parameter Sets: ExchangeRemoteMove +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Authentication This parameter is available only in the cloud-based service. @@ -617,8 +740,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -680,7 +802,6 @@ The MailboxPermission parameter specifies what permissions to use to access the The migration administrator account specified for the endpoint must have one of the following permissions: - Admin: The account is a domain administrator who can access any mailbox they want to migrate. - - FullAccess: The account is assigned either the Full Access permission to the mailboxes they want to migrate or the Receive As permission to the mailbox database that hosts the mailboxes that will be migrated. If this parameter isn't specified, the cmdlet tries to access source mailboxes using the domain administrator permission and if that fails, it then tries to access the source mailboxes using the Full Access or Receive As permissions. @@ -786,6 +907,42 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RedirectUri +This parameter is available only in the cloud-based service. + +{{ Fill RedirectUri Description }} + +```yaml +Type: String +Parameter Sets: GoogleMarketplaceApp +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteTenant +This parameter is available only in the cloud-based service. + +{{ Fill RemoteTenant Description }} + +```yaml +Type: String +Parameter Sets: ExchangeRemoteMove +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Security This parameter is available only in the cloud-based service. @@ -826,23 +983,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the migration service uses the migration arbitration mailbox in the Exchange Online organization to verify the connection. @@ -851,7 +999,7 @@ This parameter is only used to create Outlook Anywhere migration endpoints. ```yaml Type: MailboxIdParameter -Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, Gmail, PublicFolder, MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup +Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, Gmail, GoogleMarketplaceApp, PublicFolder, MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup Aliases: Applicable: Exchange Online @@ -883,12 +1031,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/New-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/exchange/New-MobileDeviceMailboxPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/devices/New-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/exchange/New-MobileDeviceMailboxPolicy.md index 2e551e2fa8..a091ad8d3d 100644 --- a/exchange/exchange-ps/exchange/devices/New-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/New-MobileDeviceMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-mobiledevicemailboxpolicy -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MobileDeviceMailboxPolicy @@ -17,39 +16,70 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MobileDeviceMailboxPolicy cmdlet to create mobile device mailbox policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-MobileDeviceMailboxPolicy [-Name] [-AllowApplePushNotifications ] - [-AllowBluetooth ] [-AllowBrowser ] - [-AllowCamera ] [-AllowConsumerEmail ] [-AllowDesktopSync ] - [-AllowExternalDeviceManagement ] [-AllowGooglePushNotifications ] - [-AllowHTMLEmail ] [-AllowInternetSharing ] [-AllowIrDA ] - [-AllowMicrosoftPushNotifications ] [-AllowMobileOTAUpdate ] - [-AllowNonProvisionableDevices ] [-AllowPOPIMAPEmail ] - [-AllowRemoteDesktop ] [-AllowSimplePassword ] +New-MobileDeviceMailboxPolicy [-Name] + [-AllowApplePushNotifications ] + [-AllowBluetooth ] + [-AllowBrowser ] + [-AllowCamera ] + [-AllowConsumerEmail ] + [-AllowDesktopSync ] + [-AllowExternalDeviceManagement ] + [-AllowGooglePushNotifications ] + [-AllowHTMLEmail ] + [-AllowInternetSharing ] + [-AllowIrDA ] + [-AllowMicrosoftPushNotifications ] + [-AllowMobileOTAUpdate ] + [-AllowNonProvisionableDevices ] + [-AllowPOPIMAPEmail ] + [-AllowRemoteDesktop ] + [-AllowSimplePassword ] [-AllowSMIMEEncryptionAlgorithmNegotiation ] - [-AllowSMIMESoftCerts ] [-AllowStorageCard ] - [-AllowTextMessaging ] [-AllowUnsignedApplications ] - [-AllowUnsignedInstallationPackages ] [-AllowWiFi ] - [-AlphanumericPasswordRequired ] [-ApprovedApplicationList ] - [-AttachmentsEnabled ] [-Confirm] [-DeviceEncryptionEnabled ] - [-DevicePolicyRefreshInterval ] [-DomainController ] [-IrmEnabled ] - [-IsDefault ] [-MaxAttachmentSize ] + [-AllowSMIMESoftCerts ] + [-AllowStorageCard ] + [-AllowTextMessaging ] + [-AllowUnsignedApplications ] + [-AllowUnsignedInstallationPackages ] + [-AllowWiFi ] + [-AlphanumericPasswordRequired ] + [-ApprovedApplicationList ] + [-AttachmentsEnabled ] + [-Confirm] + [-DeviceEncryptionEnabled ] + [-DevicePolicyRefreshInterval ] + [-DomainController ] + [-IrmEnabled ] + [-IsDefault ] + [-MaxAttachmentSize ] [-MaxCalendarAgeFilter ] [-MaxEmailAgeFilter ] - [-MaxEmailBodyTruncationSize ] [-MaxEmailHTMLBodyTruncationSize ] - [-MaxInactivityTimeLock ] [-MaxPasswordFailedAttempts ] - [-MinPasswordComplexCharacters ] [-MinPasswordLength ] [-PasswordEnabled ] - [-PasswordExpiration ] [-PasswordHistory ] [-PasswordRecoveryEnabled ] - [-RequireDeviceEncryption ] [-RequireEncryptedSMIMEMessages ] + [-MaxEmailBodyTruncationSize ] + [-MaxEmailHTMLBodyTruncationSize ] + [-MaxInactivityTimeLock ] + [-MaxPasswordFailedAttempts ] + [-MinPasswordComplexCharacters ] + [-MinPasswordLength ] + [-PasswordEnabled ] + [-PasswordExpiration ] + [-PasswordHistory ] + [-PasswordRecoveryEnabled ] + [-RequireDeviceEncryption ] + [-RequireEncryptedSMIMEMessages ] [-RequireEncryptionSMIMEAlgorithm ] - [-RequireManualSyncWhenRoaming ] [-RequireSignedSMIMEAlgorithm ] - [-RequireSignedSMIMEMessages ] [-RequireStorageCardEncryption ] - [-UnapprovedInROMApplicationList ] [-UNCAccessEnabled ] [-WhatIf] - [-WSSAccessEnabled ] [] + [-RequireManualSyncWhenRoaming ] + [-RequireSignedSMIMEAlgorithm ] + [-RequireSignedSMIMEMessages ] + [-RequireStorageCardEncryption ] + [-UnapprovedInROMApplicationList ] + [-UNCAccessEnabled ] + [-WhatIf] + [-WSSAccessEnabled ] + [] ``` ## DESCRIPTION @@ -57,7 +87,9 @@ Mobile device mailbox policies define settings for mobile devices that are used Some mobile device mailbox policy settings require the mobile device to have certain built-in features that enforce these security and device management settings. If your organization allows all devices, you need to set the AllowNonProvisionableDevices parameter to $true. This allows devices that can't enforce all policy settings to synchronize with your server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -88,9 +120,7 @@ This example creates the mobile device mailbox policy Contoso Policy that has se 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 - - Distinguished name (DN) - - GUID The name of the built-in mobile device mailbox policy is Default. @@ -127,7 +157,15 @@ Accept wildcard characters: False ``` ### -AllowBluetooth -The AllowBluetooth parameter specifies whether the Bluetooth capabilities of the mobile device are allowed. The available options are Disable, HandsfreeOnly, and Allow. The default value is Allow. +The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile device. Valid values are: + +- Allow (this is the default value). +- Disable +- HandsfreeOnly + +The values Allow or HandsfreeOnly allow synchronization between Outlook for Android and the Outlook for Android wearable app for the associated Microsoft account. + +The value Disable disables synchronization between Outlook for Android and the Outlook for Android wearable app for the associated Microsoft account. Any previously synchronized data is deleted. This value does not disable Bluetooth on the Android device or the wearable device, nor does it affect other Android wearable apps. ```yaml Type: BluetoothType @@ -231,7 +269,7 @@ The AllowGooglePushNotifications parameter controls whether the user can receive Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -297,7 +335,7 @@ The AllowMicrosoftPushNotifications parameter specifies whether push notificatio Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -392,9 +430,7 @@ Accept wildcard characters: False 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 - - BlockNegotiation - - OnlyStrongAlgorithmNegotiation The default value is AllowAnyAlgorithmNegotiation. @@ -561,15 +597,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -579,6 +614,8 @@ Accept wildcard characters: False ``` ### -DeviceEncryptionEnabled +**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. When this parameter is set to $true, device encryption is enabled on the mobile device. @@ -676,9 +713,7 @@ Unqualified values are treated as bytes. You can qualify the value with KB (kilo The maximum value is 1024 bytes (one kilobyte) less than two gigabytes (2\*1024^3), so these are the maximum qualified values you can use with this parameter. - 2097151KB - - 2047.999024MB - - 1.999999047GB ```yaml @@ -698,13 +733,9 @@ Accept wildcard characters: False 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 - - TwoWeeks - - OneMonth - - ThreeMonths - - SixMonths The default value is All. @@ -726,15 +757,10 @@ Accept wildcard characters: False 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 - - OneDay - - ThreeDays - - OneWeek - - TwoWeeks - - OneMonth The default value is All. @@ -792,7 +818,6 @@ Accept wildcard characters: False 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). - - The value Unlimited. This is the default value. ```yaml @@ -830,11 +855,8 @@ Accept wildcard characters: False The MinPasswordComplexCharacters parameter specifies the character sets that are required in the password of the mobile device. The character sets are: - Lower case letters. - - Upper case letters. - - Digits 0 through 9. - - Special characters (for example, exclamation marks). A valid value for this parameter is an integer from 1 through 4. The default value is 1. @@ -844,11 +866,8 @@ For Windows Phone 8 devices, the value specifies the number of character sets th For Windows Phone 10 devices, the value specifies the following password complexity requirements: - Digits only. - - Digits and lower case letters. - - Digits, lower case letters, and upper case letters. - - Digits, lower case letters, upper case letters, and special characters. ```yaml @@ -865,6 +884,8 @@ Accept wildcard characters: False ``` ### -MinPasswordLength +**Note**: This setting is supported by Outlook for Android. + The MinPasswordLength parameter specifies the minimum number of characters in the mobile device password. You can enter any number from 1 through 16 or the value $null. The default value is blank. The maximum password length is 16 characters. @@ -904,7 +925,6 @@ Accept wildcard characters: False 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). - - The value Unlimited. This is the default value ```yaml @@ -992,13 +1012,9 @@ Accept wildcard characters: False 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 - - TripleDES - - RC240bit - - RC264bit - - RC2128bit The default value is TripleDES. @@ -1123,7 +1139,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1153,12 +1169,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/New-MoveRequest.md b/exchange/exchange-ps/exchange/New-MoveRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/move-and-migration/New-MoveRequest.md rename to exchange/exchange-ps/exchange/New-MoveRequest.md index e9c9651af7..85f5f280eb 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/New-MoveRequest.md +++ b/exchange/exchange-ps/exchange/New-MoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-moverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-MoveRequest @@ -17,16 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-MoveRequest cmdlet to begin the process of an asynchronous mailbox or personal archive move. You can also check mailbox readiness to be moved by using the WhatIf parameter. -**Note**: After April 15, 2020, you can't use this cmdlet to manually move mailboxes within an Exchange Online organization. You can only use this cmdlet for migrating to and from Exchange Online. +**Note**: After April 15, 2020, you shouldn't use this cmdlet to manually move mailboxes within an Exchange Online organization. You can only use this cmdlet for migrating to and from Exchange Online. If you have issues with a mailbox and want to fix it by moving the mailbox within your Exchange Online organization, please open a Microsoft Support request instead. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### MigrationOutbound ``` -New-MoveRequest [-Identity] - [-Outbound] [-RemoteCredential ] [-RemoteGlobalCatalog ] -RemoteHostName +New-MoveRequest [-Identity] -RemoteHostName + [-Outbound] + [-RemoteCredential ] + [-RemoteGlobalCatalog ] [-AcceptLargeDataLoss] [-AllowLargeItems] [-ArchiveDomain ] @@ -54,6 +55,7 @@ New-MoveRequest [-Identity] [-RemoteTargetDatabase ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -66,7 +68,10 @@ New-MoveRequest [-Identity] ### MigrationRemote ``` -New-MoveRequest [-Identity] [-Remote] [-RemoteCredential ] [-RemoteGlobalCatalog ] -RemoteHostName +New-MoveRequest [-Identity] -RemoteHostName + [-Remote] + [-RemoteCredential ] + [-RemoteGlobalCatalog ] [-AcceptLargeDataLoss] [-AllowLargeItems] [-ArchiveDomain ] @@ -93,6 +98,7 @@ New-MoveRequest [-Identity] [-Remote] [-RemoteCre [-RemoteOrganizationName ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -106,8 +112,8 @@ New-MoveRequest [-Identity] [-Remote] [-RemoteCre ### MigrationRemoteLegacy ``` -New-MoveRequest [-Identity] -RemoteCredential - -RemoteGlobalCatalog [-RemoteLegacy] +New-MoveRequest [-Identity] -RemoteCredential -RemoteGlobalCatalog + [-RemoteLegacy] [-AcceptLargeDataLoss] [-AllowLargeItems] [-BadItemLimit ] @@ -130,6 +136,7 @@ New-MoveRequest [-Identity] -RemoteCredential ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -171,6 +178,7 @@ New-MoveRequest [-Identity] [-ProxyToMailbox ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -183,7 +191,7 @@ New-MoveRequest [-Identity] ### MigrationOutboundCrossTenant ``` -New-MoveRequest [-Identity] [-Outbound] -RemoteTenant -TargetDeliveryDomain +New-MoveRequest [-Identity] -TargetDeliveryDomain [-Outbound] [-AcceptLargeDataLoss] [-AllowLargeItems] [-BadItemLimit ] @@ -214,7 +222,8 @@ New-MoveRequest [-Identity] [-Outbound] -RemoteTe ### MigrationRemoteCrossTenant ``` -New-MoveRequest [-Identity] [-Remote] -RemoteTenant -TargetDeliveryDomain [-TargetDatabase ] +New-MoveRequest [-Identity] -TargetDeliveryDomain [-Remote] + [-TargetDatabase ] [-AcceptLargeDataLoss] [-AllowLargeItems] [-ArchiveTargetDatabase ] @@ -235,6 +244,7 @@ New-MoveRequest [-Identity] [-Remote] -RemoteTena [-ProxyToMailbox ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -245,7 +255,7 @@ New-MoveRequest [-Identity] [-Remote] -RemoteTena ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -276,17 +286,11 @@ This example creates a batch move request for all mailboxes on the database DB01 The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values: - GUID - - Distinguished name (DN) - - Domain\\Account - - User principal name (UPN) - - LegacyExchangeDN - - SMTP address - - Alias ```yaml @@ -341,7 +345,7 @@ Accept wildcard characters: False ### -RemoteCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -432,26 +436,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RemoteTenant -This parameter is available only in the cloud-based service. - -PARAMVALUE: SmtpDomain - -```yaml -Type: SmtpDomain -Parameter Sets: MigrationOutboundCrossTenant, MigrationRemoteCrossTenant -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -TargetDeliveryDomain -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 or RemoteLegacy parameter. +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 @@ -536,7 +522,7 @@ Accept wildcard characters: False ``` ### -ArchiveOnly -The ArchiveOnly switch specifies that you're moving only the personal archive associated with the mailbox. +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. @@ -559,14 +545,11 @@ 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: - Name - - Distinguished name (DN) - - GUID If you don't use this parameter, the archive is moved to the same database as the primary mailbox. - ```yaml Type: DatabaseIdParameter Parameter Sets: MigrationRemote, MigrationLocal, MigrationRemoteCrossTenant @@ -621,15 +604,14 @@ Accept wildcard characters: False ### -CompleteAfter 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". +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". -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a date/time value for this parameter, use either of the following options: -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). ```yaml Type: DateTime @@ -663,8 +645,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -779,7 +760,7 @@ Accept wildcard characters: False ### -IgnoreRuleLimitErrors This parameter is available only in Exchange Server 2010 or Exchange Server 2013 -The IgnoreRuleLimitErrors parameter specifies that the command doesn't move the user's rules to the target server running Exchange. +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. ```yaml Type: SwitchParameter @@ -837,9 +818,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange Server: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange Server: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -879,7 +859,7 @@ Accept wildcard characters: False ``` ### -MRSServer -This parameter is available or functional only in 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. @@ -897,7 +877,9 @@ Accept wildcard characters: False ``` ### -PreventCompletion -The PreventCompletion switch specifies whether to run the move request, but not allow it to complete. Instead of this switch, we recommend using the CompleteAfter parameter. +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. ```yaml Type: SwitchParameter @@ -917,7 +899,7 @@ The PrimaryOnly switch specifies that the command should only move the primary m 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. -You can't use this parameter with the ArchiveOnly parameter. +You can't use this switch with the ArchiveOnly sitch. ```yaml Type: SwitchParameter @@ -938,19 +920,12 @@ 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: - Lowest - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml @@ -967,13 +942,15 @@ Accept wildcard characters: False ``` ### -Protect +This parameter is available only in on-premises Exchange. + 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -988,23 +965,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -1076,7 +1044,6 @@ Accept wildcard characters: False 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. - - If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1114,18 +1081,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceEndpoint +This parameter is available only in the cloud-based service. + +{{ Fill SourceEndpoint Description }} + +```yaml +Type: MigrationEndpointIdParameter +Parameter Sets: MigrationOutbound, MigrationRemote, MigrationRemoteLegacy, MigrationLocal, MigrationRemoteCrossTenant +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -StartAfter 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". +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". -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a date/time value for this parameter, use either of the following options: -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). ```yaml Type: DateTime @@ -1141,7 +1125,9 @@ Accept wildcard characters: False ``` ### -Suspend -The Suspend switch specifies whether to suspend the request. 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. You don't have to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -1173,7 +1159,9 @@ Accept wildcard characters: False ``` ### -SuspendWhenReadyToComplete -The SuspendWhenReadyToComplete switch specifies whether to suspend the move request before it reaches the status of CompletionInProgress. Instead of this switch, we recommend that you use the CompleteAfter parameter. +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. ```yaml Type: SwitchParameter @@ -1194,9 +1182,7 @@ 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: - Name - - Distinguished name (DN) - - GUID If you don't use this parameter, the automatic distribution logic will select a random database in the Active Directory site where you are running the command. @@ -1255,12 +1241,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-OMEConfiguration.md b/exchange/exchange-ps/exchange/New-OMEConfiguration.md new file mode 100644 index 0000000000..8be7fb364c --- /dev/null +++ b/exchange/exchange-ps/exchange/New-OMEConfiguration.md @@ -0,0 +1,310 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-OMEConfiguration + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-OMEConfiguration cmdlet to create a Microsoft Purview Message Encryption configuration. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-OMEConfiguration [-Identity] + [-BackgroundColor ] + [-Confirm] + [-DisclaimerText ] + [-EmailText ] + [-ExternalMailExpiryInDays ] + [-Image ] + [-IntroductionText ] + [-OTPEnabled ] + [-PortalText ] + [-PrivacyStatementUrl ] + [-ReadButtonText ] + [-SocialIdSignIn ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-OMEConfiguration -Identity "Contoso Marketing" -EmailText "Encrypted message enclosed." -PortalText "This portal is encrypted." -DisclaimerText "Encryption security disclaimer." -Image ([System.IO.File]::ReadAllBytes('C:\Temp\OME Logo.gif')) +``` + +This example creates a new OME configuration named "Contoso Marketing" with the specified values specified. Unused parameters get the default values. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -BackgroundColor +The BackgroundColor parameter specifies the background color. Valid values are: + +- An available HTML hexadecimal (hex triplet) color code value (for example, `0x000000` is white). +- An available text value (for example, `yellow` is 0x00FFFF00). +- $null (blank). This is the default value. + +For more information, see [Add your organization's brand to your encrypted messages](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisclaimerText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalMailExpiryInDays +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. + +In the output of the Get-OMEConfiguration cmdlet, the value of this parameter is displayed in the ExternalMailExpiryInterval property. + +```yaml +Type: String +Parameter Sets: Int32 +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Image +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`). + +- Supported file formats: .png, .jpg, .bmp, or .tiff +- Optimal size of logo file: less than 40 KB +- Optimal dimensions of logo image: 170x70 pixels + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IntroductionText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OTPEnabled +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. +- $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PortalText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyStatementUrl +{{ Fill PrivacyStatementUrl Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadButtonText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SocialIdSignIn +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. +- $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-OabVirtualDirectory.md b/exchange/exchange-ps/exchange/New-OabVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/New-OabVirtualDirectory.md rename to exchange/exchange-ps/exchange/New-OabVirtualDirectory.md index 6aec0725eb..7732f3db5a 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-OabVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/New-OabVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/new-oabvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-OabVirtualDirectory @@ -17,16 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the New-OABVirtualDirectory cmdlet to create offline address book (OAB) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. The OAB virtual directory configures the server as a web distribution point for an offline address book (OAB). Typically, you create virtual directories on Exchange servers that have the Client Access server role installed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-OabVirtualDirectory [-Confirm] [-DomainController ] [-ExtendedProtectionFlags ] - [-ExtendedProtectionSPNList ] [-ExtendedProtectionTokenChecking ] - [-ExternalUrl ] [-InternalUrl ] [-Path ] [-PollInterval ] [-Recovery] - [-RequireSSL ] [-Server ] [-WebSiteName ] [-WhatIf] - [-Role ] [] +New-OabVirtualDirectory [-Confirm] + [-DomainController ] + [-ExtendedProtectionFlags ] + [-ExtendedProtectionSPNList ] + [-ExtendedProtectionTokenChecking ] + [-ExternalUrl ] + [-InternalUrl ] + [-Path ] + [-PollInterval ] + [-Recovery] + [-RequireSSL ] + [-Role ] + [-Server ] + [-WebSiteName ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -34,7 +44,7 @@ The New-OABVirtualDirectory cmdlet configures a web distribution point for an OA You have to manually create the file system folder on the server that hosts the OAB files. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,8 +60,7 @@ This example creates an OAB virtual directory on CASServer01 and configures the ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -87,13 +96,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -113,8 +118,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -133,14 +137,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -239,7 +239,6 @@ Accept wildcard characters: False 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. - - $false: SSL encryption isn't required to connect to the virtual directory. ```yaml @@ -255,15 +254,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Role +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. +- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. + +Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. + +```yaml +Type: VirtualDirectoryRole +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Server 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -311,39 +328,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Role -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. - -- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. - -Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. - -```yaml -Type: VirtualDirectoryRole -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-OfflineAddressBook.md b/exchange/exchange-ps/exchange/New-OfflineAddressBook.md similarity index 86% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/New-OfflineAddressBook.md rename to exchange/exchange-ps/exchange/New-OfflineAddressBook.md index 82448f22c4..cc267ae497 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/New-OfflineAddressBook.md +++ b/exchange/exchange-ps/exchange/New-OfflineAddressBook.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/new-offlineaddressbook +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-OfflineAddressBook @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-OfflineAddressBook cmdlet to create offline address books (OABs). -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,17 +38,20 @@ New-OfflineAddressBook [-Name] -AddressLists ] [-VirtualDirectories ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$a = Get-AddressList | Where {$_.Name -Like "*AgencyB*"}; New-OfflineAddressBook -Name "OAB_AgencyB" -Server myserver.contoso.com -AddressLists $a -Schedule "Mon.01:00-Mon.02:00, Wed.01:00-Wed.02:00" +$a = Get-AddressList | Where {$_.Name -Like "*AgencyB*"} + +New-OfflineAddressBook -Name "OAB_AgencyB" -Server myserver.contoso.com -AddressLists $a -Schedule "Mon.01:00-Mon.02:00, Wed.01:00-Wed.02:00" ``` In Exchange Server 2010 and 2013, this example uses two commands to create the OAB named OAB\_AgencyB that includes all address lists in which AgencyB is part of the name. By using the settings shown, an OAB is generated by myserver.contoso.com on Mondays and Wednesdays from 01:00 (1 A.M.) to 02:00 (2 A.M.). This example command also creates the default OAB for the organization. @@ -62,7 +64,6 @@ New-OfflineAddressBook -Name "Contoso Executives OAB" -AddressLists "Default Glo This example creates a new OAB named Contoso Executives OAB with the following properties: - Address lists included in the OAB: Default Global Address List and Contoso Executives Address List - - All OAB virtual directories in the organization can accept requests to download the OAB. The organization mailbox that's responsible for generating the OAB is SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} (we didn't use the GeneratingMailbox parameter to specify a different organization mailbox). @@ -83,7 +84,7 @@ New-OfflineAddressBook -Name "Legacy OAB" -AddressLists "\Default Global Address In Exchange Server 2010, this example creates the OAB Legacy OAB that uses public folder distribution for Outlook 2003 Service Pack 1 (SP1) and Outlook 98 Service Pack 2 (SP2) clients on SERVER01. -If you configure OABs to use public folder distribution, but your organization doesn't have any public folder infrastructure, an error will be returned. For more information, see [Managing Public Folders](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb124411(v=exchg.141)). +If you configure OABs to use public folder distribution, but your organization doesn't have any public folder infrastructure, an error will be returned. For more information, see [Managing Public Folders](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb124411(v=exchg.141)). ## PARAMETERS @@ -107,12 +108,10 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You can find the identify values of address lists and global address lists by using the Get-AddressList and Get-GlobalAddressList cmdlets. @@ -132,8 +131,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -189,23 +187,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) The default value for this parameter is the organization mailbox named SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}. @@ -231,7 +220,6 @@ 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: - $true: Any OAB virtual directory in the organization can accept requests to download the OAB. You can't use this setting with the VirtualDirectories parameter. - - $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This is the default value. In Exchange 2013 CU7 or later, we recommend that you use the value $true for this parameter. The Client Access services on any Mailbox server can proxy incoming OAB download requests to the correct location. @@ -253,7 +241,6 @@ Accept wildcard characters: False 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. - - $false: The OAB is isn't the default OAB. This is the default value. ```yaml @@ -270,14 +257,12 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabase -This parameter is available or functional only in 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: - Name - - Distinguished name (DN) - - GUID To use this parameter, the PublicFolderDistributionEnabled parameter must be set to $true. @@ -296,7 +281,7 @@ Accept wildcard characters: False ``` ### -PublicFolderDistributionEnabled -This parameter is available or functional only in 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. @@ -314,18 +299,16 @@ Accept wildcard characters: False ``` ### -Schedule -This parameter is available or functional only in 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. -The syntax for this parameter is: StartDay.Hour:Minute \[AM/PM\]-EndDay.Hour:Minute \[AM/PM\]. +The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -337,9 +320,7 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" ```yaml @@ -356,16 +337,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN If you don't use this parameter, the command is run on the local server. @@ -389,7 +367,6 @@ 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: - $true: The OAB is distributed to all other organization mailboxes. - - $false: The OAB is isn't distributed to other organization mailboxes. This is the default value. The value of this parameter is only meaningful if you have multiple organization mailboxes, and is only beneficial in Exchange organizations that have multiple Active Directory sites. @@ -408,9 +385,11 @@ Accept wildcard characters: False ``` ### -SkipPublicFolderInitialization -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. -The SkipPublicFolderInitialization parameter specifies whether to skip the immediate creation of the OAB public folders if you're creating an OAB that uses public folder distribution. The OAB isn't available for download until the next site folder maintenance cycle has completed. You don't have to specify a value with the SkipPublicFolderInitialization parameter. Omitting this parameter may cause the task to pause while it contacts the responsible public folder server to create the necessary public folders. If the server is presently unreachable, or is otherwise costly to contact, the pause could be significant. +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. + +The OAB isn't available for download until the next site folder maintenance cycle has completed. Omitting this switch might cause the task to pause while it contacts the responsible public folder server to create the necessary public folders. If the server is presently unreachable, or is otherwise costly to contact, the pause could be significant. ```yaml Type: SwitchParameter @@ -426,17 +405,13 @@ Accept wildcard characters: False ``` ### -Versions -This parameter is available or functional only in Exchange Server 2010. - -The Versions parameter specifies what version of OAB to generate. The allowed values are: +This parameter is available only in Exchange Server 2010. -- Version1 +The Versions parameter specifies the OAB versions that are generated for client download. Valid values are: -- Version2 - -- Version3 - -- Version4 +- Version2 (requires public folder distribution) +- Version3 (requires public folder distribution) +- Version4 (default value) ```yaml Type: MultiValuedProperty @@ -458,13 +433,11 @@ The VirtualDirectories parameter specifies the OAB virtual directories that acce You can use any value that uniquely identifies the virtual directory. For example: -- Name or \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. The default value of this parameter is the Client Access services (frontend) and backend OAB virtual directories on the Mailbox server that holds the OAB generation mailbox (the GeneratingMailbox parameter or SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}). For example, Mailbox01\\OAB (Default Web Site),Mailbox01\\OAB (Exchange Back End. @@ -506,12 +479,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/New-OnPremisesOrganization.md new file mode 100644 index 0000000000..a8a5a4ed57 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-OnPremisesOrganization.md @@ -0,0 +1,227 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-OnPremisesOrganization + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-OnPremisesOrganization cmdlet to create an OnPremisesOrganization object in a Microsoft 365 organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-OnPremisesOrganization [-Name] -HybridDomains -InboundConnector -OrganizationGuid -OutboundConnector + [-Comment ] + [-Confirm] + [-OrganizationName ] + [-OrganizationRelationship ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-OnPremisesOrganization -Name "ExchangeMail" -OrganizationGuid "a1bc23cb-3456-bcde-abcd-feb363cacc88" -HybridDomains contoso.com, sales.contoso.com -InboundConnector "Inbound to ExchangeMail" -OutboundConnector "Outbound to ExchangeMail" +``` + +This example creates the OnPremisesOrganization object ExchangeMail in a Microsoft 365 organization for the hybrid domains contoso.com and sales.contoso.com. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HybridDomains +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundConnector +The InboundConnector parameter specifies the name of the inbound connector configured on the Microsoft Exchange Online Protection (EOP) service 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationGuid +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutboundConnector +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationRelationship +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/sharing-and-collaboration/New-OrganizationRelationship.md b/exchange/exchange-ps/exchange/New-OrganizationRelationship.md similarity index 79% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/New-OrganizationRelationship.md rename to exchange/exchange-ps/exchange/New-OrganizationRelationship.md index 6b8ae16998..8fe6d28c4a 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-OrganizationRelationship.md +++ b/exchange/exchange-ps/exchange/New-OrganizationRelationship.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-organizationrelationship -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-OrganizationRelationship @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-OrganizationRelationship cmdlet to create organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,23 +30,27 @@ New-OrganizationRelationship [-Name] -DomainNames [-FreeBusyAccessEnabled ] [-FreeBusyAccessLevel ] [-FreeBusyAccessScope ] + [-MailboxMoveCapability ] [-MailboxMoveEnabled ] + [-MailboxMovePublishedScopes ] [-MailTipsAccessEnabled ] [-MailTipsAccessLevel ] [-MailTipsAccessScope ] + [-OAuthApplicationId ] [-OrganizationContact ] [-PhotosEnabled ] [-TargetApplicationUri ] [-TargetAutodiscoverEpr ] [-TargetOwaURL ] [-TargetSharingEpr ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -Before you can create an organization relationship, you must first create a federation trust. For more information, see [Federation](https://docs.microsoft.com/exchange/federation-exchange-2013-help). +Before you can create an organization relationship, you must first create a federation trust. For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -75,7 +78,7 @@ The domain to connect to is mail.fourthcoffee.com. The Exchange Web Services application URL is mail.fourthcoffee.com. -The Autodiscover URL is https://mail.fourthcoffee.com/autodiscover/autodiscover.svc/wssecurity. +The Autodiscover URL is `https://mail.fourthcoffee.com/autodiscover/autodiscover.svc/wssecurity`. Free/busy access is enabled. @@ -90,7 +93,7 @@ The Name parameter specifies the unique name of the organization relationship. T Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -106,7 +109,7 @@ The DomainNames parameter specifies the SMTP domains of the external organizatio Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -119,14 +122,13 @@ Accept wildcard characters: False 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. - - $false: The external organization doesn't provide remote access to mailbox archives. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -138,15 +140,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -159,7 +160,6 @@ Accept wildcard characters: False 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. - - $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction. @@ -168,7 +168,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -199,14 +199,13 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable the organization relationship. Valid values are: - $true: The organization relationship is enabled. This is the default value. - - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -219,7 +218,6 @@ Accept wildcard characters: False 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. - - $false: Free/busy information isn't retrieved from the external organization. This is the default value. You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters. @@ -228,7 +226,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -241,9 +239,7 @@ Accept wildcard characters: False The FreeBusyAccessLevel parameter specifies the maximum amount of detail returned to the requesting organization. Valid values are: - None: No free/busy access. - - AvailabilityOnly: Free/busy access with time only. - - LimitedDetails: Free/busy access with time, subject, and location. This parameter is only meaningful when the FreeBusyAccessEnabled parameter value is $true. @@ -252,7 +248,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -265,11 +261,8 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - Canonical DN - - GUID This parameter is only meaningful when the FreeBusyAccessEnabled parameter value is $true. @@ -278,7 +271,32 @@ 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 +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxMoveCapability +This parameter is available only in the cloud-based service. + +The MailboxMoveCapability parameter is used in cross-tenant mailbox migrations. Valid values are: + +- Inbound +- Outbound +- RemoteInbound +- RemoteOutbound + +For more information, see [Cross-tenant mailbox migration](https://learn.microsoft.com/microsoft-365/enterprise/cross-tenant-mailbox-migration). + +```yaml +Type: MailboxMoveCapability +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -291,14 +309,40 @@ Accept wildcard characters: False 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. - - $false: Mailbox moves to or from the external organization aren't allowed. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxMovePublishedScopes +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: + +- Name +- Distinguished name (DN) +- Canonical DN +- GUID + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information, see [Cross-tenant mailbox migration](https://learn.microsoft.com/microsoft-365/enterprise/cross-tenant-mailbox-migration). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -311,7 +355,6 @@ Accept wildcard characters: False 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. - - $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value. You control the MailTips access level by using the MailTipsAccessLevel parameter. @@ -320,7 +363,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -333,9 +376,7 @@ Accept wildcard characters: False 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. - - Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned. - - None: No MailTips are returned to the remote organization. This is the default value. This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true. @@ -344,7 +385,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -357,11 +398,8 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - Canonical DN - - GUID The default value is blank ($null), which means no group is specified. @@ -369,9 +407,7 @@ The default value is blank ($null), which means no group is specified. If you use this parameter, recipient-specific MailTips are returned only for those recipients that are members of the specified group. The recipient-specific MailTips are: - Auto Reply - - Mailbox Full - - Custom If you don't use this parameter, recipient-specific MailTips are returned for all recipients in the organization. @@ -382,7 +418,25 @@ 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 +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OAuthApplicationId +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -398,7 +452,7 @@ The OrganizationContact parameter specifies the email address that can be used t Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -411,14 +465,13 @@ Accept wildcard characters: False 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. - - $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -434,7 +487,7 @@ The TargetApplicationUri parameter specifies the target Uniform Resource Identif Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -444,13 +497,13 @@ Accept wildcard characters: False ``` ### -TargetAutodiscoverEpr -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. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -466,7 +519,7 @@ The TargetOwaURL parameter specifies the Outlook on the web (formerly Outlook We Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -484,7 +537,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -500,7 +553,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -514,12 +567,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-OrganizationSegment.md b/exchange/exchange-ps/exchange/New-OrganizationSegment.md new file mode 100644 index 0000000000..a8a7015875 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-OrganizationSegment.md @@ -0,0 +1,149 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-OrganizationSegment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-OrganizationSegment cmdlet to create organization segments for use with information barrier policies in the Microsoft Purview compliance portal. Organization Segments are not in effect until you [apply information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies#step-4-apply-ib-policies). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-OrganizationSegment [-Name] -UserGroupFilter + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about the filterable attributes that you can use to define segments, see [Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-OrganizationSegment -Name "HR" -UserGroupFilter "Department -eq 'HR'" +``` + +In this example, a segment called HR is defined using HR, a value in the Department attribute. + +### Example 2 +```powershell +New-OrganizationSegment -Name "NotSales" -UserGroupFilter "Department -ne 'Sales'" +``` + +In this example, we defined a segment called NotSales that includes everyone who is not in Sales. The "-ne" portion of the cmdlet refers to "not equals." + +### Example 3 +```powershell +New-OrganizationSegment -Name "LocalFTE" -UserGroupFilter "Location -eq 'Local' -and Position -ne 'Temporary'" +``` + +In this example, we defined a segment called LocalFTE that includes people who are locally located and whose positions are not listed as Temporary. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserGroupFilter +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. +- Property is a filterable property. For more information, see [Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +Use the same property for all of your segments, and verify that your segments don't overlap (a user must be assigned to only one segment). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes) + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) diff --git a/exchange/exchange-ps/exchange/mail-flow/New-OutboundConnector.md b/exchange/exchange-ps/exchange/New-OutboundConnector.md similarity index 79% rename from exchange/exchange-ps/exchange/mail-flow/New-OutboundConnector.md rename to exchange/exchange-ps/exchange/New-OutboundConnector.md index 0d149a914c..2121c66207 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-OutboundConnector.md +++ b/exchange/exchange-ps/exchange/New-OutboundConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-outboundconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # New-OutboundConnector @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the New-OutboundConnector cmdlet to create a new Outbound connector in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -37,18 +33,20 @@ New-OutboundConnector [-Name] [-LinkForModifiedConnector ] [-RecipientDomains ] [-RouteAllMessagesViaOnPremises ] + [-SenderRewritingEnabled ] [-SmartHosts ] [-TestMode ] [-TlsDomain ] [-TlsSettings ] [-UseMXRecord ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Outbound connectors send email messages to remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,7 +58,6 @@ New-OutboundConnector -Name "Contoso Outbound Connector" -RecipientDomains *.con This example creates the Outbound connector named Contoso Outbound Connector with the following properties: - It sends messages to recipients in the contoso.com domain and all subdomains. - - It uses TLS encryption and certificate verification for mail routed to the contoso.com domain and all subdomains ## PARAMETERS @@ -84,10 +81,11 @@ Accept wildcard characters: False ### -AllAcceptedDomains 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. You can only use this value when the ConnectorType parameter value is OnPremises. - +- $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. - $false: The Outbound connector isn't used in hybrid organizations. This is the default value. +This parameter is effective only for OnPremises connectors. + ```yaml Type: Boolean Parameter Sets: (All) @@ -102,14 +100,13 @@ Accept wildcard characters: False ``` ### -CloudServicesMailEnabled -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://docs.microsoft.com/exchange/hybrid-configuration-wizard). +**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 Office 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. +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. Valid values are: - $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -144,8 +141,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -165,9 +161,7 @@ Accept wildcard characters: False 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. - - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. ```yaml @@ -187,7 +181,6 @@ Accept wildcard characters: False 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. - - OnPremises: The connector services domains that are used by your on-premises organization. ```yaml @@ -207,7 +200,6 @@ Accept wildcard characters: False 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. - - $false: The connector is disabled. ```yaml @@ -227,7 +219,6 @@ Accept wildcard characters: False 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. - - $false: The connector isn't associated with a transport rule. This is the default value. You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector. @@ -280,11 +271,33 @@ Accept wildcard characters: False ``` ### -RouteAllMessagesViaOnPremises -The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises messaging system in hybrid organizations. Valid values are: +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 messaging system. This setting requires you to set the ConnectorType parameter to the value OnPremises in the same command. +- $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. +- $false: Messages aren't routed through the on-premises email system. This is the default value. -- $false: Messages aren't routed through the on-premises messaging system. This is the default value. +This parameter is effective only for OnPremises connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderRewritingEnabled +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. +- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value. + +This parameter is effective only for OnPremises connectors. ```yaml Type: Boolean @@ -300,7 +313,15 @@ Accept wildcard characters: False ``` ### -SmartHosts -The SmartHosts parameter specifies the smart hosts the Outbound connector uses to route mail. This parameter is required if you set the UseMxRecord parameter to $false and 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. Separate each value by using a comma. If you enter an IP address, you may enter the IP address as a literal, for example: 10.10.1.1, or using Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25. The smart host identity can be the FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record. +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. +- Single IP address: For example, 10.10.1.1. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple value separated by commas: `"Value1","Value2",..."ValueN"`. + +This parameter is required if you use the value $false for the UseMxRecord parameter. ```yaml Type: MultiValuedProperty @@ -319,7 +340,6 @@ Accept wildcard characters: False 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. - - $false: Test mode is disabled. This is the default value. ```yaml @@ -336,7 +356,11 @@ Accept wildcard characters: False ``` ### -TlsDomain -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. This parameter is only used if the TlsSettings parameter is set to DomainValidation. Valid input for the TlsDomain 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 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). + +This parameter meaningful only when the TlsSettings value is DomainValidation. ```yaml Type: SmtpDomainWithSubdomains @@ -355,11 +379,8 @@ Accept wildcard characters: False 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. - - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. - - $null (blank): This is the default value. ```yaml @@ -379,8 +400,7 @@ Accept wildcard characters: False 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. - -- $false: The connector delivers email to one or more smart hosts. When you use this value, you also need to specify the smart hosts by using the SmartHosts parameter in the same command. +- $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value. ```yaml Type: Boolean @@ -416,12 +436,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/New-OutlookProtectionRule.md similarity index 85% rename from exchange/exchange-ps/exchange/policy-and-compliance/New-OutlookProtectionRule.md rename to exchange/exchange-ps/exchange/New-OutlookProtectionRule.md index c11ef394ee..871a1233f5 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-OutlookProtectionRule.md +++ b/exchange/exchange-ps/exchange/New-OutlookProtectionRule.md @@ -1,41 +1,50 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-outlookprotectionrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-OutlookProtectionRule ## SYNOPSIS +**Note**: This cmdlet is no longer supported in the cloud-based service. + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the New-OutlookProtectionRule cmdlet to create a Microsoft Outlook protection rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-OutlookProtectionRule [-Name] -ApplyRightsProtectionTemplate [-Confirm] - [-DomainController ] [-Enabled ] [-Force] [-FromDepartment ] - [-Priority ] [-SentTo ] - [-SentToScope ] [-UserCanOverride ] [-WhatIf] [] +New-OutlookProtectionRule [-Name] -ApplyRightsProtectionTemplate + [-Confirm] + [-DomainController ] + [-Enabled ] + [-Force] + [-FromDepartment ] + [-Priority ] + [-SentTo ] + [-SentToScope ] + [-UserCanOverride ] + [-WhatIf] + [] ``` ## DESCRIPTION Outlook protection rules are administrator-created rules applied before a user sends a message using Outlook. Outlook inspects message content and protects messages by applying Active Directory Rights Management Services (AD RMS) rights templates. -For more information, see [Outlook protection rules](https://docs.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). +For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). Outlook protection rules created without a condition apply to all messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,47 +53,46 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-OutlookProtectionRule -Name "Project Contoso" -SentTo Joe@contoso.com -ApplyRightsProtectionTemplate "Template-Contoso" ``` -This example applies the AD RMS template Template-Contoso to messages sent to the SMTP address Joe@contoso.com. +This example applies the AD RMS template named Template-Contoso to messages sent to the SMTP address Joe@contoso.com. ## PARAMETERS -### -ApplyRightsProtectionTemplate -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. +### -Name +The Name parameter specifies a name for the rule. ```yaml -Type: RmsTemplateIdParameter +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 +Position: 1 Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies a name for the rule. +### -ApplyRightsProtectionTemplate +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: String +Type: RmsTemplateIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -135,7 +143,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch specifies whether to suppress the confirmation prompt used to warn the administrator when rules are created without any conditions. Rules without any conditions specified apply to all messages. The Force switch doesn't require a value. +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). ```yaml Type: SwitchParameter @@ -186,20 +196,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID You can also specify the SMTP email address of an external recipient. -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. When you specify multiple recipients, messages sent to any of the specified recipients are considered a match. @@ -222,7 +227,6 @@ Accept wildcard characters: False 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. - - All: This value is for messages sent to all recipients. ```yaml @@ -275,12 +279,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/New-OutlookProvider.md b/exchange/exchange-ps/exchange/New-OutlookProvider.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access/New-OutlookProvider.md rename to exchange/exchange-ps/exchange/New-OutlookProvider.md index 75e0daa644..8552c51259 100644 --- a/exchange/exchange-ps/exchange/client-access/New-OutlookProvider.md +++ b/exchange/exchange-ps/exchange/New-OutlookProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/new-outlookprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-OutlookProvider @@ -17,18 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the New-OutlookProvider cmdlet to create the AutoDiscoverConfig object and then populate the object with relevant settings. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-OutlookProvider [-Name] [-Confirm] [-DomainController ] [-WhatIf] [] +New-OutlookProvider [-Name] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The New-OutlookProvider cmdlet creates the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,8 +70,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +123,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/New-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/New-OwaMailboxPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access/New-OwaMailboxPolicy.md rename to exchange/exchange-ps/exchange/New-OwaMailboxPolicy.md index 8d26cdf6fc..b25a96ccdb 100644 --- a/exchange/exchange-ps/exchange/client-access/New-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/New-OwaMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/new-owamailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-OwaMailboxPolicy @@ -17,21 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-OwaMailboxPolicy cmdlet to create Outlook on the web mailbox policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-OwaMailboxPolicy [-Name] [-Confirm] [-DomainController ] - [-WhatIf] [-IsDefault] [] +New-OwaMailboxPolicy [-Name] + [-Confirm] + [-DomainController ] + [-IsDefault] + [-WhatIf] + [] ``` ## DESCRIPTION Use the Set-OwaMailboxPolicy cmdlet to configure the new policy. -Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). +Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +66,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -98,14 +100,18 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -IsDefault +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. + +If another policy is currently set as the default, using this switch replaces the old default policy with this policy. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Aliases: +Applicable: Exchange Online Required: False Position: Named @@ -114,18 +120,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -IsDefault -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. - -If another policy is currently set as the default, using this switch replaces the old default policy with this policy. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Online +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -139,12 +141,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-OwaVirtualDirectory.md b/exchange/exchange-ps/exchange/New-OwaVirtualDirectory.md similarity index 91% rename from exchange/exchange-ps/exchange/client-access-servers/New-OwaVirtualDirectory.md rename to exchange/exchange-ps/exchange/New-OwaVirtualDirectory.md index dc6a3b21e0..703e02a8bd 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/New-OwaVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-owavirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-OwaVirtualDirectory @@ -17,13 +16,13 @@ This cmdlet is available only in on-premises Exchange. Use the New-OwaVirtualDirectory cmdlet to create Outlook on the web virtual directories that are used in Internet Information Services on Exchange servers. Typically, you create virtual directories on Exchange servers that have the Client Access server role installed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` New-OwaVirtualDirectory - [[-ApplicationRoot ] + [-ApplicationRoot ] [-AppPoolId ] [-Confirm] [-DomainController ] @@ -31,19 +30,21 @@ New-OwaVirtualDirectory [-ExtendedProtectionSPNList ] [-ExtendedProtectionTokenChecking ] [-ExternalAuthenticationMethods ] - [-ExternalUrl ] [-InternalUrl ] + [-ExternalUrl ] + [-InternalUrl ] [-Name ] [-Path ] [-Role ] [-Server ] [-WebSiteName ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION By default, when Exchange is installed, the Outlook on the web virtual directory owa is created in the default IIS website on the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,6 +57,24 @@ This example creates the Outlook on the web virtual directory in an IIS website ## PARAMETERS +### -Name +This parameter is available only in 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: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ApplicationRoot 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. @@ -91,8 +110,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -128,13 +146,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -154,8 +168,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -174,14 +187,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -200,33 +209,19 @@ Accept wildcard characters: False 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 - - Basic - - Certificate - - Digest - - Fba - - Kerberos - - LiveIdBasic - - LiveIdFba - - LiveIdNegotiate - - NegoEx - - Negotiate - - Ntlm - - OAuth - - WindowsIntegrated - - WSSecurity You can specify multiple values separated by commas. @@ -234,7 +229,6 @@ You can specify multiple values separated by commas. Although you can specify any of these values, whether or not the authentication method actually works for external connections depends on other factors. For example: - Is the authentication method available on the virtual directory? - - Is the authentication method available, but disabled on the virtual directory? ```yaml @@ -282,24 +276,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -This parameter is available or functional only in 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: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Path 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. @@ -320,7 +296,6 @@ Accept wildcard characters: False 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. - - Mailbox: Configure the virtual directory for the backend services on the Mailbox server. Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. @@ -342,11 +317,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -399,12 +371,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/New-PartnerApplication.md b/exchange/exchange-ps/exchange/New-PartnerApplication.md similarity index 89% rename from exchange/exchange-ps/exchange/organization/New-PartnerApplication.md rename to exchange/exchange-ps/exchange/New-PartnerApplication.md index ea85796640..d0ef93326f 100644 --- a/exchange/exchange-ps/exchange/organization/New-PartnerApplication.md +++ b/exchange/exchange-ps/exchange/New-PartnerApplication.md @@ -1,29 +1,29 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/new-partnerapplication +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-PartnerApplication ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is functional only in on-premises Exchange. -Use the New-PartnerApplication cmdlet to create a partner application configuration. +Use the New-PartnerApplication cmdlet to create partner application configurations in on-premises Exchange organizations. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### ACSTrustApplication ``` -New-PartnerApplication [-Name] -ApplicationIdentifier [-Realm ] +New-PartnerApplication [-Name] -ApplicationIdentifier + [-Realm ] [-AcceptSecurityIdentifierInformation ] [-AccountType ] [-ActAsPermissions ] @@ -33,12 +33,14 @@ New-PartnerApplication [-Name] -ApplicationIdentifier [-Realm [-Enabled ] [-IssuerIdentifier ] [-LinkedAccount ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AuthMetadataUrl ``` -New-PartnerApplication [-Name] -AuthMetadataUrl [-TrustAnySSLCertificate] +New-PartnerApplication [-Name] -AuthMetadataUrl + [-TrustAnySSLCertificate] [-AcceptSecurityIdentifierInformation ] [-AccountType ] [-ActAsPermissions ] @@ -48,15 +50,16 @@ New-PartnerApplication [-Name] -AuthMetadataUrl [-TrustAnySSLC [-Enabled ] [-IssuerIdentifier ] [-LinkedAccount ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You can configure partner applications such as Microsoft SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://docs.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). +You can configure partner applications such as Microsoft SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -139,7 +142,6 @@ Accept wildcard characters: False 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) - - ConsumerAccount ```yaml @@ -156,7 +158,7 @@ Accept wildcard characters: False ``` ### -ActAsPermissions -This parameter is available only in Exchange 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -174,7 +176,7 @@ Accept wildcard characters: False ``` ### -AppOnlyPermissions -This parameter is available only in Exchange 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -194,8 +196,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -246,7 +247,7 @@ Accept wildcard characters: False ``` ### -IssuerIdentifier -This parameter is available only in Exchange 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -300,7 +301,7 @@ Accept wildcard characters: False ### -TrustAnySSLCertificate This parameter is available only in on-premises Exchange. -The TrustAnySSLCertificate switch specifies whether Exchange should trust certificates issued by a certification authority (CA) not trusted by the server. +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. @@ -338,12 +339,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-PhishSimOverridePolicy.md b/exchange/exchange-ps/exchange/New-PhishSimOverridePolicy.md new file mode 100644 index 0000000000..4d6de2ee03 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-PhishSimOverridePolicy.md @@ -0,0 +1,179 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-PhishSimOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-PhishSimOverridePolicy cmdlet to create third-party phishing simulation override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-PhishSimOverridePolicy [-Name] + [-Comment ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-PhishSimOverridePolicy -Name PhishSimOverridePolicy +``` + +This example creates the phishing simulation override policy named PhishSimOverridePolicy. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-PolicyTipConfig.md b/exchange/exchange-ps/exchange/New-PolicyTipConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-PolicyTipConfig.md rename to exchange/exchange-ps/exchange/New-PolicyTipConfig.md index 8f53f2f043..c32359ad77 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-PolicyTipConfig.md +++ b/exchange/exchange-ps/exchange/New-PolicyTipConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-policytipconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-PolicyTipConfig @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-PolicyTipConfig cmdlet to create custom Policy Tips in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-PolicyTipConfig [-Name] -Value [-Confirm] [-DomainController ] [-WhatIf] +New-PolicyTipConfig [-Name] -Value + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -39,9 +41,7 @@ New-PolicyTipConfig -Name en\NotifyOnly -Value "This message contains content th This example creates a custom Policy Tip with the following settings: - Locale: English - - Action: NotifyOnly - - Policy Tip text: "This message contains content that is restricted by Contoso company policy." ### Example 2 @@ -49,15 +49,14 @@ This example creates a custom Policy Tip with the following settings: New-PolicyTipConfig Url -Value "https://www.contoso.com/PolicyTipInformation" ``` -This example sets the informational URL in Policy Tips to the value https://www.contoso.com/PolicyTipInformation. +This example sets the informational URL in Policy Tips to the value `https://www.contoso.com/PolicyTipInformation`. ## PARAMETERS ### -Name The Name parameter specifies the custom Policy Tip you want to modify. Valid input for this parameter is one of the following values: -- \\\\: 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://docs.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. - +- `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. - Url There can be only one custom Policy Tip with the value Url for the Name parameter. For the remaining Policy Tip actions, there can be only one custom Policy Tip for each combination of locale and action. For example, there can be only one custom Policy Tip with the Name value en\\NotifyOnly, but you can create additional custom Policy Tips with the values de\\NotifyOnly and fr\\NotifyOnly for the Name parameter. @@ -94,8 +93,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -150,12 +148,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-PowerShellVirtualDirectory.md b/exchange/exchange-ps/exchange/New-PowerShellVirtualDirectory.md new file mode 100644 index 0000000000..fd597096d0 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-PowerShellVirtualDirectory.md @@ -0,0 +1,324 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-PowerShellVirtualDirectory + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the New-PowerShellVirtualDirectory cmdlet to create Windows PowerShell virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-PowerShellVirtualDirectory [-Name] + [-BasicAuthentication ] + [-Confirm] + [-DomainController ] + [-ExtendedProtectionFlags ] + [-ExtendedProtectionSPNList ] + [-ExtendedProtectionTokenChecking ] + [-ExternalUrl ] + [-InternalUrl ] + [-RequireSSL ] + [-Role ] + [-Server ] + [-WhatIf] + [-WindowsAuthentication ] + [] +``` + +## DESCRIPTION +Although it's possible to create a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-PowerShellVirtualDirectory -Name "Contoso Certificates Required" -BasicAuthentication $false -WindowsAuthentication $false -CertificateAuthentication $true +``` + +This example creates a Windows PowerShell virtual directory and configures it to accept only certificate authentication. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BasicAuthentication +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedProtectionFlags +The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: + +- None: This is the default setting. +- AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. +- NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. +- Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. +- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedProtectionSPNList +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. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedProtectionTokenChecking +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. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. + +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. + +```yaml +Type: ExtendedProtectionTokenCheckingMode +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireSSL +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Role +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. +- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. + +Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. + +```yaml +Type: VirtualDirectoryRole +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Server +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 +- FQDN +- Distinguished name (DN) +- ExchangeLegacyDN + +```yaml +Type: ServerIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WindowsAuthentication +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/New-ProtectionAlert.md b/exchange/exchange-ps/exchange/New-ProtectionAlert.md new file mode 100644 index 0000000000..5c469a4905 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ProtectionAlert.md @@ -0,0 +1,696 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ProtectionAlert + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-ProtectionAlert cmdlet to create alert policies in the Microsoft Purview compliance portal and the Microsoft Defender portal. Alert policies contain conditions that define the user activities to monitor, and the notification options for email alerts and entries. + +> [!NOTE] +> Although the cmdlet is available, you receive the following error if you don't have an enterprise license: +> +> _Creating advanced alert policies requires an Office 365 E5 subscription or Office 365 E3 subscription with an Office 365 Threat Intelligence or +Office 365 EquivioAnalytics add-on subscription for your organization. With your current subscription, only single event alerts can be created._ +> +> You can bypass this error by specifying `-AggregationType None` and an `-Operation` within the command. +> +> For more information, see [Alert policies in Microsoft 365](https://learn.microsoft.com/purview/alert-policies). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ProtectionAlert -Category -Name -NotifyUser -ThreatType + [-AggregationType ] + [-AlertBy ] + [-AlertFor ] + [-Comment ] + [-Confirm] + [-CorrelationPolicyId ] + [-Description ] + [-Disabled ] + [-Filter ] + [-LogicalOperationName ] + [-NotificationCulture ] + [-NotificationEnabled ] + [-NotifyUserOnFilterMatch ] + [-NotifyUserSuppressionExpiryDate ] + [-NotifyUserThrottleThreshold ] + [-NotifyUserThrottleWindow ] + [-Operation ] + [-PrivacyManagementScopedSensitiveInformationTypes ] + [-PrivacyManagementScopedSensitiveInformationTypesForCounting ] + [-PrivacyManagementScopedSensitiveInformationTypesThreshold ] + [-CustomProperties ] + [-Severity ] + [-Threshold ] + [-TimeWindow ] + [-UseCreatedDateTime ] + [-VolumeThreshold ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ProtectionAlert -Name "Content search deleted" -Category Others -NotifyUser admin@contoso.com -ThreatType Activity -Operation SearchRemoved -Description "Custom alert policy to track when content searches are deleted" -AggregationType None +``` + +This example creates an alert policy that triggers an alert whenever anyone in the organization deletes a Content Search in the Microsoft Purview compliance portal. + +## PARAMETERS + +### -Category +The Category parameter specifies a category for the alert policy. Valid values are: + +- AccessGovernance +- ComplianceManager +- DataGovernance +- MailFlow +- Others +- PrivacyManagement +- Supervision +- ThreatManagement + +When an activity occurs that matches the conditions of the alert policy, the alert that's generated is tagged with the category that's specified by this parameter. This allows you to track and manage alerts that have the same category setting + +```yaml +Type: AlertRuleCategory +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUser +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThreatType +The ThreatType parameter specifies the type of activities that are monitored by the alert policy. Valid values are: + +- Activity +- Malware + +The value that you select for this parameter determines the values you can use for the AlertBy, Filter, and Operation parameters. + +You can't change this value after you create the alert policy. + +```yaml +Type: ThreatAlertType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AggregationType +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. +- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. +- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. + +```yaml +Type: AlertAggregationType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlertBy +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. +- Malware: Valid values are Mail.Recipient or Mail.ThreatName. + +You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlertFor +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CorrelationPolicyId +{{ Fill CorrelationPolicyId Description }} + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomProperties +{{ Fill CustomProperties Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter enables or disables the alert policy. Valid values are: + +- $true: The alert policy is disabled. +- $false: The alert policy is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the logical `-and` operator (for example, `"Criteria1 -and Criteria2"`). + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +The filterable properties are: + +Activity + +- Activity.ClientIp +- Activity.CreationTime +- Activity.Item +- Activity.ItemType +- Activity.Operation +- Activity.ResultStatus +- Activity.Scope +- Activity.SiteUrl +- Activity.SourceFileExtension +- Activity.SourceFileName +- Activity.TargetUserOrGroupType +- Activity.UserAgent +- Activity.UserId +- Activity.UserType +- Activity.Workload + +Malware + +- Mail:AttachmentExtensions +- Mail:AttachmentNames +- Mail:CreationTime +- Mail:DeliveryStatus +- Mail:Direction +- Mail:From +- Mail:FromDomain +- Mail:InternetMessageId +- Mail:IsIntraOrgSpoof +- Mail:IsMalware +- Mail:IsSpam +- Mail:IsThreat +- Mail:Language +- Mail:Recipient +- Mail:Scl +- Mail:SenderCountry +- Mail:SenderIpAddress +- Mail:Subject +- Mail:TenantId +- Mail:ThreatName + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LogicalOperationName +{{ Fill LogicalOperationName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationCulture +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). + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationEnabled +{{ Fill NotificationEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserOnFilterMatch +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). +- $false: Alerts are triggered according to the specified aggregation type. This is the default value. + +You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserSuppressionExpiryDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserThrottleThreshold +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. +- The value $null. This is the default value (no maximum number of notifications for an alert). + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserThrottleWindow +The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: + +- An integer. +- The value $null. This is the default value (no interval for notification throttling). + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Operation +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. + +You can only use this parameter when the ThreatType parameter has the value Activity. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyManagementScopedSensitiveInformationTypes +{{ Fill PrivacyManagementScopedSensitiveInformationTypes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyManagementScopedSensitiveInformationTypesForCounting +{{ Fill PrivacyManagementScopedSensitiveInformationTypesForCounting Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyManagementScopedSensitiveInformationTypesThreshold +{{ Fill PrivacyManagementScopedSensitiveInformationTypesThreshold Description }} + +```yaml +Type: System.UInt64 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Severity +The Severity parameter specifies the severity of the detection. Valid values are: + +- Low (This is the default value) +- Medium +- High + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Threshold +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeWindow +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCreatedDateTime +{{ Fill UseCreatedDateTime Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VolumeThreshold +{{ Fill VolumeThreshold Description }} + +```yaml +Type: System.UInt64 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolder.md b/exchange/exchange-ps/exchange/New-PublicFolder.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolder.md rename to exchange/exchange-ps/exchange/New-PublicFolder.md index e3b8984bc5..71c11a5ab5 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolder.md +++ b/exchange/exchange-ps/exchange/New-PublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-publicfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-PublicFolder @@ -17,18 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-PublicFolder cmdlet to create a public folder with the specified name. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-PublicFolder [-Name] [-Confirm] [-DomainController ] [-EformsLocaleId ] - [-Path ] [-Server ] - [-WhatIf] [-Mailbox ] [] +New-PublicFolder [-Name] + [-Confirm] + [-DomainController ] + [-EformsLocaleId ] + [-Mailbox ] + [-Path ] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,10 +53,10 @@ In Exchange Server 2010, this example creates the public folder FY2010 under the ### Example 3 ```powershell -New-PublicFolder -Name FY2013 -Path \Legal\Cases +New-PublicFolder -Name FY2014 -Path \Legal\Cases ``` -This example creates the public folder FY2013 under the existing folders \\Legal\\Cases. The path to the new folder is \\Legal\\Cases\\FY2013. +This example creates the public folder FY2014 under the existing folders \\Legal\\Cases. The path to the new folder is \\Legal\\Cases\\FY2014. ### Example 4 ```powershell @@ -81,8 +86,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,7 +121,7 @@ Accept wildcard characters: False ``` ### -EformsLocaleId -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://go.microsoft.com/fwlink/p/?linkId=184859). +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 @@ -132,6 +136,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Mailbox +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Path The Path parameter specifies the location of the folder in the folder hierarchy, for example, \\Legal\\Cases. @@ -149,16 +180,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server if the server is a Mailbox server with a public folder database. If not, Exchange creates the new public folder on the closest (by site cost) Exchange 2007 or Exchange 2010 Mailbox server with a public folder database. @@ -192,53 +220,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Mailbox -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolderDatabase.md b/exchange/exchange-ps/exchange/New-PublicFolderDatabase.md similarity index 84% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolderDatabase.md rename to exchange/exchange-ps/exchange/New-PublicFolderDatabase.md index a0bbebc7ed..992f21daac 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolderDatabase.md +++ b/exchange/exchange-ps/exchange/New-PublicFolderDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-publicfolderdatabase +online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolderdatabase applicable: Exchange Server 2010 title: New-PublicFolderDatabase schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-PublicFolderDatabase @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the New-PublicFolderDatabase cmdlet to create a public folder database. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,14 +26,14 @@ New-PublicFolderDatabase [-Name] -Server [-DomainController ] [-EdbFilePath ] [-LogFolderPath ] - [-Organization ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -The new database must be mounted after it's created. For more information about mounting databases, see [Mount a Database](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb123587(v=exchg.141)). +The new database must be mounted after it's created. For more information about mounting databases, see [Mount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123587(v=exchg.141)). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,11 +66,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN A server can have only one public folder database. @@ -92,8 +88,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,7 +121,7 @@ Accept wildcard characters: False ``` ### -EdbFilePath -The EdbFilePath parameter specifies the full path of the public folder database files. +The EdbFilePath parameter specifies the full path of the public folder database files. The default location is `%ExchangeInstallPath%Mailbox\\.edb` ```yaml Type: EdbFilePath @@ -142,7 +137,7 @@ Accept wildcard characters: False ``` ### -LogFolderPath -The LogFolderPath parameter specifies the folder location for log files. The default path is \V14\\Mailbox. +The LogFolderPath parameter specifies the folder location for log files. The default location is `%ExchangeInstallPath%Mailbox\`. ```yaml Type: NonRootLocalLongFullPath @@ -157,22 +152,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Organization -This parameter is reserved for internal Microsoft use. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -194,12 +173,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolderDatabaseRepairRequest.md b/exchange/exchange-ps/exchange/New-PublicFolderDatabaseRepairRequest.md similarity index 88% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolderDatabaseRepairRequest.md rename to exchange/exchange-ps/exchange/New-PublicFolderDatabaseRepairRequest.md index 31da7318fc..332ac3deec 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-PublicFolderDatabaseRepairRequest.md +++ b/exchange/exchange-ps/exchange/New-PublicFolderDatabaseRepairRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-publicfolderdatabaserepairrequest +online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolderdatabaserepairrequest applicable: Exchange Server 2010 title: New-PublicFolderDatabaseRepairRequest schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-PublicFolderDatabaseRepairRequest @@ -17,22 +16,25 @@ This cmdlet is available only in Exchange Server 2010. Use the New-PublicFolderDatabaseRepairRequest cmdlet to detect and fix replication issues in the public folder database. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-PublicFolderDatabaseRepairRequest [-Database] - -CorruptionType [-Confirm] [-DetectOnly] [-DomainController ] - [-WhatIf] [] +New-PublicFolderDatabaseRepairRequest [-Database] -CorruptionType + [-Confirm] + [-DetectOnly] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Public folders on the public folder database can still be accessed while the request is running. However, access isn't available to the public folder currently being repaired. -After you begin the repair request, it can't be stopped unless you dismount the database. For more information, see [Dismount a Database](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb123903(v=exchg.141)). +After you begin the repair request, it can't be stopped unless you dismount the database. For more information, see [Dismount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123903(v=exchg.141)). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,49 +54,46 @@ This example only detects and reports on replication issues on public folder dat ## PARAMETERS -### -CorruptionType -The CorruptionType parameter specifies the type of corruption that you want to detect and repair. The only available value is ReplState. +### -Database +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 +- Distinguished name (DN) +- GUID ```yaml -Type: PublicFolderDatabaseCorruptionType[] +Type: DatabaseIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Database -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 - -- Distinguished name (DN) - -- GUID +### -CorruptionType +The CorruptionType parameter specifies the type of corruption that you want to detect and repair. The only available value is ReplState. ```yaml -Type: DatabaseIdParameter +Type: PublicFolderDatabaseCorruptionType[] Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -163,12 +162,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/move-and-migration/New-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/New-PublicFolderMigrationRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/move-and-migration/New-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/exchange/New-PublicFolderMigrationRequest.md index c73079d47b..8707577d81 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/New-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/exchange/New-PublicFolderMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-publicfoldermigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-PublicFolderMigrationRequest @@ -19,12 +18,12 @@ Use the New-PublicFolderMigrationRequest cmdlet to start a serial public folder **Note**: Support for serial migration of public folders ended in Exchange 2013 Cumulative Update 8 (CU8), and the cmdlets are no longer available in Exchange Online. Instead, use the corresponding **\*-MigrationBatch** and **\*-PublicFolderMailboxMigration\*** cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-PublicFolderMigrationRequest -SourceDatabase +New-PublicFolderMigrationRequest [[-Name] ] -SourceDatabase [-AcceptLargeDataLoss] [-BadItemLimit ] [-BatchName ] @@ -35,7 +34,6 @@ New-PublicFolderMigrationRequest -SourceDatabase [-DomainController ] [-InternalFlags ] [-LargeItemLimit ] - [[-Name] ] [-MigrationMailbox ] [-Priority ] [-RequestExpiryInterval ] @@ -49,28 +47,42 @@ New-PublicFolderMigrationRequest -SourceDatabase ``` ## DESCRIPTION -Migrating public folders is a multi-step process. For more information before you attempt a public folder migration, see [Use serial migration to migrate public folders to Exchange 2013 from previous versions](https://docs.microsoft.com/previous-versions/exchange-server/exchange-150/jj150486(v=exchg.150)). +Migrating public folders is a multi-step process. For more information before you attempt a public folder migration, see [Use serial migration to migrate public folders to Exchange 2013 from previous versions](https://learn.microsoft.com/previous-versions/exchange-server/exchange-150/jj150486(v=exchg.150)). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-PublicFolderMigrationRequest -SourceDatabase PFDB01 -CSVData (Get-Content C:\PFMigration\CSVData.csv -Encoding Byte) +New-PublicFolderMigrationRequest -SourceDatabase PFDB01 -CSVData ([System.IO.File]::ReadAllBytes('C:\PFMigration\CSVData.csv')) ``` -This example creates a public folder migration request from the Exchange 2010 source public folder database PFDB01 and uses the CSVData.csv file that was created using the Export-PublicFolderStatistics.ps1 script. For more information, see [Use serial migration to migrate public folders to Exchange 2013 from previous versions](https://docs.microsoft.com/previous-versions/exchange-server/exchange-150/jj150486(v=exchg.150)). +This example creates a public folder migration request from the Exchange 2010 source public folder database PFDB01 and uses the CSVData.csv file that was created using the Export-PublicFolderStatistics.ps1 script. For more information, see [Use serial migration to migrate public folders to Exchange 2013 from previous versions](https://learn.microsoft.com/previous-versions/exchange-server/exchange-150/jj150486(v=exchg.150)). ## PARAMETERS +### -Name +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -SourceDatabase The SourceDatabase parameter specifies the target database for the public folders. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -157,8 +169,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -177,7 +188,7 @@ Accept wildcard characters: False ### -CSVData 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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\" -ReadCount 0\)\). +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`). You can't use this parameter with the CSVStream parameter, but you need to use it if you don't use CSVStream parameter. @@ -249,9 +260,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -286,39 +296,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Priority 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 - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml @@ -338,7 +325,6 @@ Accept wildcard characters: False 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. - - If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. @@ -461,12 +447,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md new file mode 100644 index 0000000000..435cac68b3 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md @@ -0,0 +1,431 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-PublicFolderMoveRequest + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the New-PublicFolderMoveRequest cmdlet to begin the process of moving public folder contents between public folder mailboxes. Moving public folders only moves the physical contents of the public folder; it doesn't change the logical hierarchy. When the move request is completed, you must run the Remove-PublicFolderMoveRequest cmdlet to remove the request or wait until the time specified in the CompletedRequestAgeLimit parameter has passed. The request must be removed before you can run another move request. + +Be aware that the target public folder mailbox will be locked while the move request is active. For more information, see the Description section. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-PublicFolderMoveRequest -Folders -TargetMailbox + [-AcceptLargeDataLoss] + [-AllowLargeItems] + [-BadItemLimit ] + [-CompletedRequestAgeLimit ] + [-Confirm] + [-DomainController ] + [-InternalFlags ] + [-Name ] + [[-Organization] ] + [-Priority ] + [-RequestExpiryInterval ] + [-Suspend] + [-SuspendComment ] + [-SuspendWhenReadyToComplete] + [-WhatIf] + [-WorkloadType ] + [] +``` + +## DESCRIPTION +The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox will be locked. As a result, public folders already residing in the target public folder mailbox will be inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox. + +To move the public folder mailbox to another mailbox database, use the New-MoveRequest cmdlet. To ensure that this folder is already in the target public folder mailbox, run the Update-PublicFolderMailbox cmdlet against the target public folder mailbox. You can only perform one move request at a time. You can also move public folders by using the Move-PublicFolderBranch.ps1 script. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-PublicFolderMoveRequest -Folders \DeveloperReports\CustomerEngagements -TargetMailbox DeveloperReports01 +``` + +This example begins the move request for the public folder \\CustomerEngagements from public folder mailbox DeveloperReports to DeveloperReports01. + +### Example 2 +```powershell +New-PublicFolderMoveRequest -Folders \Dev\CustomerEngagements,\Dev\RequestsforChange,\Dev\Usability -TargetMailbox DeveloperReports01 +``` + +This example begins the move request for public folders under the \\Dev public folder branch to the target public folder mailbox DeveloperReports01. + +You can also move a branch of public folders by using the Move-PublicFolderBranch.ps1 script. + +### Example 3 +```powershell +$folders = Get-PublicFolder \ -Recurse -Mailbox PUB1 -ResidentFolders | ?{$_.Name -ne "IPM_SUBTREE"} | %{$_.Identity} + +New-PublicFolderMoveRequest -TargetMailbox PUB2 -Folders $folders +``` + +This example moves all public folders from public folder mailbox Pub1 to public folder mailbox Pub2. + +## PARAMETERS + +### -Folders +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetMailbox +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AcceptLargeDataLoss +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLargeItems +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BadItemLimit +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. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompletedRequestAgeLimit +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalFlags +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +This parameter is available only in the cloud-based service. + +{{ Fill Organization Description }} + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: 7 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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 +- Lower +- Low +- Normal: This is the default value. +- High +- Higher +- Highest +- Emergency + +```yaml +Type: RequestPriority +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequestExpiryInterval +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. +- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. + +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. + +When you use the value Unlimited, the completed request isn't automatically removed. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Suspend +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SuspendComment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SuspendWhenReadyToComplete +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. + +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: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkloadType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/New-QuarantinePermissions.md b/exchange/exchange-ps/exchange/New-QuarantinePermissions.md new file mode 100644 index 0000000000..2ce42db98f --- /dev/null +++ b/exchange/exchange-ps/exchange/New-QuarantinePermissions.md @@ -0,0 +1,243 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-QuarantinePermissions + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +**Note**: Instead of using this cmdlet to set quarantine policy permissions, we recommend using the EndUserQuarantinePermissionsValue parameter on the New-QuarantinePolicy and Set-QuarantinePolicy cmdlets. + +Use the New-QuarantinePermissions cmdlet to create a variable that contains a quarantine permissions object to use with the EndUserQuarantinePermission parameter on the New-QuarantinePolicy or Set-QuarantinePolicy cmdlets in the same PowerShell session. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-QuarantinePermissions + [[-PermissionToAllowSender] ] + [[-PermissionToBlockSender] ] + [[-PermissionToDelete] ] + [[-PermissionToDownload] ] + [[-PermissionToPreview] ] + [[-PermissionToRelease] ] + [[-PermissionToRequestRelease] ] + [[-PermissionToViewHeader] ] + [] +``` + +## DESCRIPTION +The default value for any parameters that you don't use is $false, so you only need to use parameters (permissions) that you want to set to $true. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$NoAccess = New-QuarantinePermissions +``` + +This example creates the same permissions that are used by the No access permissions group in quarantine policies. The permissions object is stored in the variable named `$NoAccess`. + +In the same PowerShell session, you can use `$NoAccess` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command. + +### Example 2 +```powershell +$LimitedAccess = New-QuarantinePermissions -PermissionToAllowSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRequestRelease $true +``` + +This example creates the same permissions that are used by the Limited access permissions group in quarantine policies. The permissions object is stored in the variable named `$LimitedAccess`. + +In the same PowerShell session, you can use `$LimitedAccess` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command. + +### Example 3 +```powershell +$FullAccess = New-QuarantinePermissions -PermissionToAllowSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRelease $true +``` + +This example creates the same permissions that are used by the Full access permissions group in quarantine policies. The permissions object is stored in the variable named `$FullAccess`. + +In the same PowerShell session, you can use `$FullAccess` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command. + +## PARAMETERS + +### -PermissionToAllowSender +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. +- $false: Allow sender isn't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToBlockSender +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. +- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToDelete +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. +- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToDownload +The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: + +- $true: The permission is enabled. +- $false: The permission is disabled. This is the default value. + +Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 4 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToPreview +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. +- $false: Preview message isn't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 5 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToRelease +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. +- $false: Release message isn't available in quarantine notifications for affected messages, and Release and Release email aren't available for affected messages in quarantine. + +Don't set this parameter and the _PermissionToRequestRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 6 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToRequestRelease +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. +- $false: Request Release isn't available in quarantine notifications for affected messages, and Request release isn't available for affected messages in quarantine. + +Don't set this parameter and the _PermissionRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 7 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToViewHeader +The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: + +- $true: The permission is enabled. +- $false: The permission is disabled. This is the default value. + +Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 8 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-QuarantinePolicy.md b/exchange/exchange-ps/exchange/New-QuarantinePolicy.md new file mode 100644 index 0000000000..1d12b70c98 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-QuarantinePolicy.md @@ -0,0 +1,493 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-QuarantinePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-QuarantinePolicy cmdlet to create quarantine policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-QuarantinePolicy [-Name] + [-AdminDisplayName ] + [-AdminNotificationFrequencyInDays ] + [-AdminNotificationLanguage ] + [-AdminNotificationsEnabled ] + [-AdminQuarantinePermissionsList ] + [-CustomDisclaimer ] + [-DomainController ] + [-EndUserQuarantinePermissions ] + [-EndUserQuarantinePermissionsValue ] + [-EndUserSpamNotificationCustomFromAddress ] + [-EndUserSpamNotificationFrequency ] + [-EndUserSpamNotificationFrequencyInDays ] + [-EndUserSpamNotificationLanguage ] + [-EsnCustomSubject ] + [-ESNEnabled ] + [-IncludeMessagesFromBlockedSenderAddress ] + [-MultiLanguageCustomDisclaimer ] + [-MultiLanguageSenderName ] + [-MultiLanguageSetting ] + [-OrganizationBrandingEnabled ] + [-QuarantinePolicyType ] + [-QuarantineRetentionDays ] + [] +``` + +## DESCRIPTION +Quarantine policies define what users are allowed to do to quarantined messages based on why the message was quarantined (for supported features) and quarantine notification settings. For more information, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-QuarantinePolicy -Name ContosoTag -EndUserQuarantinePermissionsValue 0 +``` + +This example creates a new quarantine policy named ContosoTag with the same permissions as the No access preset permissions group. + +To assign Limited access permissions, use the value 27. To assign Full access permissions, use the value 23. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminNotificationFrequencyInDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminNotificationLanguage +This parameter is reserved for internal Microsoft use. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminNotificationsEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminQuarantinePermissionsList +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomDisclaimer +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserQuarantinePermissions +**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. + +For example, run the following command to store the required permissions in a variable: `$Perms = New-QuarantinePermissions `. In the same PowerShell session, use the value `$Perms` for this parameter. + +```yaml +Type: QuarantinePermissions +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserQuarantinePermissionsValue +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): + +- PermissionToViewHeader: The value 0 doesn't hide the **View message header** action in quarantine. If the message is visible in quarantine, the action is always available for the message. +- PermissionToDownload: This permission is not used (the value 0 or 1 does nothing). +- PermissionToAllowSender +- PermissionToBlockSender +- PermissionToRequestRelease: Don't set this permission and PermissionToRelease to the value 1. Set one value to 1 and the other value to 0, or set both values to 0. +- PermissionToRelease: Don't set this permission and PermissionToRequestRelease to value 1. Set one value to 1 and the other value to 0, or set both values to 0. This permission isn't honored for messages that were quarantined as malware or high confidence phishing. If the quarantine policy gives users this permission, users are allowed to request the release of their quarantined malware or high confidence phishing messages as if PermissionToRequestRelease was selected instead. +- PermissionToPreview +- PermissionToDelete + +The values for the preset end-user permission groups are described in the following list: + +- No access: Binary = 0000000, so use the decimal value 0. +- Limited access: Binary = 00101011, so use the decimal value 43. +- Full access: Binary = 00100111, so use the decimal value 39. + +For custom permissions, get the binary value that corresponds to the permissions you want. Convert the binary value to a decimal value to use. Don't use the binary value for this parameter. + +**Note**: If the value of this parameter is 0 (No access) and the value of the ESNEnabled parameter is $true, users can view their messages in quarantine, but the only available action for the messages is **View message header**. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomFromAddress +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationFrequency +The EndUserSpamNotificationFrequency parameter specifies how often quarantine notifications are sent to users. Valid values are: + +- 04:00:00 (4 hours) +- 1.00:00:00 (1 day) +- 7.00:00:00 (7 days) + +```yaml +Type: TimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationFrequencyInDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationLanguage +This parameter is reserved for internal Microsoft use. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EsnCustomSubject +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. + +To modify an existing value and preserve other values, you need to specify all existing values and the new value in the existing order. + +This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global quarantine policy settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: MultiValuedProperty +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ESNEnabled +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. +- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value. + +**Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can see their messages in quarantine, but the only available action for the messages is **View message header**. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeMessagesFromBlockedSenderAddress +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. +- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiLanguageCustomDisclaimer +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiLanguageSenderName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiLanguageSetting +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationBrandingEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineRetentionDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantinePolicyType +This parameter is reserved for internal Microsoft use. + +```yaml +Type: QuarantinePolicyType +Parameter Sets: (All) +Aliases: +Accepted values: QuarantinePolicy, GlobalQuarantinePolicy +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/New-ReceiveConnector.md b/exchange/exchange-ps/exchange/New-ReceiveConnector.md similarity index 93% rename from exchange/exchange-ps/exchange/mail-flow/New-ReceiveConnector.md rename to exchange/exchange-ps/exchange/New-ReceiveConnector.md index c53c0e1b5b..a053087232 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-ReceiveConnector.md +++ b/exchange/exchange-ps/exchange/New-ReceiveConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-receiveconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-ReceiveConnector @@ -17,13 +16,14 @@ This cmdlet is available only in on-premises Exchange. Use the New-ReceiveConnector cmdlet to create Receive connectors on Mailbox servers and Edge Transport servers. Receive connectors listen for inbound SMTP connections on the Exchange server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Custom ``` -New-ReceiveConnector [-Name] -Bindings -RemoteIPRanges [-Custom] +New-ReceiveConnector [-Name] -Bindings -RemoteIPRanges + [-Custom] [-AdvertiseClientSettings ] [-AuthMechanism ] [-AuthTarpitInterval ] @@ -75,12 +75,14 @@ New-ReceiveConnector [-Name] -Bindings -RemoteIPR [-TlsCertificateName ] [-TlsDomainCapabilities ] [-TransportRole ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Internet ``` -New-ReceiveConnector [-Name] -Bindings [-Internet] +New-ReceiveConnector [-Name] -Bindings + [-Internet] [-RemoteIPRanges ] [-AdvertiseClientSettings ] [-AuthMechanism ] @@ -133,12 +135,14 @@ New-ReceiveConnector [-Name] -Bindings [-Internet [-TlsCertificateName ] [-TlsDomainCapabilities ] [-TransportRole ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Partner ``` -New-ReceiveConnector [-Name] -Bindings -RemoteIPRanges [-Partner] +New-ReceiveConnector [-Name] -Bindings -RemoteIPRanges + [-Partner] [-AdvertiseClientSettings ] [-AuthMechanism ] [-AuthTarpitInterval ] @@ -190,12 +194,15 @@ New-ReceiveConnector [-Name] -Bindings -RemoteIPR [-TlsDomainCapabilities ] [-TlsCertificateName ] [-TransportRole ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Internal ``` -New-ReceiveConnector [-Name] -RemoteIPRanges [-Bindings ] [-Internal] +New-ReceiveConnector [-Name] -RemoteIPRanges + [-Bindings ] + [-Internal] [-AdvertiseClientSettings ] [-AuthMechanism ] [-AuthTarpitInterval ] @@ -247,12 +254,15 @@ New-ReceiveConnector [-Name] -RemoteIPRanges [-Bi [-TlsCertificateName ] [-TlsDomainCapabilities ] [-TransportRole ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Client ``` -New-ReceiveConnector [-Name] -RemoteIPRanges [-Bindings ] [-Client] +New-ReceiveConnector [-Name] -RemoteIPRanges + [-Bindings ] + [-Client] [-AdvertiseClientSettings ] [-AuthMechanism ] [-AuthTarpitInterval ] @@ -304,12 +314,15 @@ New-ReceiveConnector [-Name] -RemoteIPRanges [-Bi [-TlsCertificateName ] [-TlsDomainCapabilities ] [-TransportRole ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UsageType ``` -New-ReceiveConnector [-Name] -Usage [-Bindings ] [-RemoteIPRanges ] +New-ReceiveConnector [-Name] -Usage + [-Bindings ] + [-RemoteIPRanges ] [AdvertiseClientSettings ] [-AuthMechanism ] [-AuthTarpitInterval ] @@ -361,15 +374,16 @@ New-ReceiveConnector [-Name] -Usage [-Bindings ] [-TlsDomainCapabilities ] [-TransportRole ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION On Mailbox servers, you can create Receive connectors in the Front End Transport service, and the Transport (Hub) service. On Edge Transport servers, you can create Receive connectors in the Transport service. -For more information about Receive connector usage types, permission groups, and authentication methods, see [Receive connectors](https://docs.microsoft.com/Exchange/mail-flow/connectors/receive-connectors). +For more information about Receive connector usage types, permission groups, and authentication methods, see [Receive connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/receive-connectors). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -403,28 +417,24 @@ Accept wildcard characters: False ``` ### -Bindings -The Bindings parameter specifies the local IP address and TCP port number that's used by the Receive connector. This parameter uses the syntax "\:\","\:\". You can specify an IPv4 address and port, and 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. +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. You need to use this parameter when you use these usage type parameters: - The Internet switch (or the Usage parameter with the value Internet). - - The Partner switch (or the Usage parameter with the value Partner). - - The Custom switch (or the Usage parameter with the value Custom). You can't use this parameter when you use the following usage type parameters: - The Client switch (or the Usage parameter with the value Client. The default value is 0.0.0.0:587. - - The Internal switch (or Usage parameter with the value Internal). The default value is 0.0.0.0:25. The values for this parameter must satisfy one of the following uniqueness requirements: - The combination of IP address and TCP port doesn't conflict with the IP address and TCP port that's used on another Receive connector on the server. - - You use an existing combination of IP address and TCP port that's configured on another Receive connector on the server, but you restrict the remote IP addresses by using the RemoteIPRanges parameter. When you create a Receive connector, you can only use the RemoteIPRanges and Bindings parameters together with the Custom and Partner switches (or the Usage parameter with the value Custom or Partner). ```yaml @@ -459,7 +469,6 @@ The Client switch specifies the Client usage type for the Receive connector. You This usage type assigns the following default permission groups and authentication methods: - Permission groups:ExchangeUsers - - Authentication methods:TLS, BasicAuth, BasicAuthRequireTLS, and Integrated. When you use this switch, you also need to use the RemoteIPRanges parameter, and you can't use the Bindings parameter (the default value is 0.0.0.0:587). @@ -485,7 +494,6 @@ The Internal switch specifies the Internal usage type for the Receive connector. This usage type assigns the following default permission groups and authentication methods: - Permission groups:ExchangeLegacyServers and ExchangeServers. - - Authentication methods:TLS and ExchangeServers. When you use this switch, you also need to use the RemoteIPRanges parameter, and you can't use the Bindings parameter (the default value is 0.0.0.0:25). @@ -511,7 +519,6 @@ The Internet switch specifies the Internet usage type for the Receive connector. This usage type assigns the following default permission groups and authentication methods: - Permission groups:AnonymousUsers - - Authentication methods:TLS When you use this switch, you also need to use the Bindings parameter, and you can't use the RemoteIPRanges parameter (the default value is 0.0.0.0-255.255.255.255). @@ -537,7 +544,6 @@ The Partner switch specifies the Partner usage type for the Receive connector. Y This usage type assigns the following default permission groups and authentication methods: - Permission groups:Partners - - Authentication methods:TLS When you use this switch, you also need to use the Bindings and RemoteIPRanges parameters. @@ -561,19 +567,15 @@ Accept wildcard characters: False 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. - - IP address range: For example, 192.168.1.1-192.168.1.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.1.1/24 or 2001:0DB8::CD3/60. -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.1.1/24 or 2001:0DB8::CD3/60. - -You can specify multiple value separated by commas ("\","\"...). +You can specify multiple value separated by commas: `"Value1","Value2",..."ValueN"`. Multiple Receive connectors on the same server can have overlapping remote IP address ranges as long as one IP address range is completely overlapped by another. For example, you can configure the following remote IP address ranges on different Receive connectors on the same server: - 0.0.0.0 - - 192.168.1.1/24 - - 192.168.1.10 When remote IP address ranges overlap, the Receive connector with the most specific match to the IP address of the connecting server is used. @@ -581,11 +583,8 @@ When remote IP address ranges overlap, the Receive connector with the most speci You need to use this parameter with the following usage type parameters: - The Client switch (or the Usage parameter with the value Client). - - The Internal switch (or the Usage parameter with the value Internal). - - The Partner switch (or the Usage parameter with the value Partner). - - The Custom switch (or the Usage parameter with the value Custom). You can't use this parameter with the Internet usage type (the default value is 0.0.0.0-255.255.255.255). @@ -620,31 +619,22 @@ Accept wildcard characters: False The Usage parameter specifies the default permission groups and authentication methods that are assigned to the Receive connector. Valid values are: - Client - - Custom - - Internal - - Internet - - Partner The following values for this parameter also require the Bindings parameter: - Internet - - Partner - - Custom The following values for this parameter also require the RemoteIPRanges parameter: - Client - - Internal - - Partner - - Custom For a description of the default permission groups and authentication methods that are assigned for each value, see the corresponding usage type switch descriptions. @@ -668,7 +658,6 @@ Accept wildcard characters: False 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). - - $false: The SMTP values are displayed in Outlook on the web. This is the default value. ```yaml @@ -688,29 +677,19 @@ Accept wildcard characters: False The AuthMechanism parameter specifies the advertised and accepted authentication mechanisms for the Receive connector. Valid values are: - None - - Tls - - Integrated - - BasicAuth - - BasicAuthRequireTLS - - ExchangeServer - - ExternalAuthoritative You can specify multiple values separated by commas, but some values have dependencies and exclusions: - You can only use the value None by itself. - - The value BasicAuthRequireTLS also requires the values BasicAuth and Tls. - - The only other value that you can use with ExternalAuthoritative is Tls. - - The value Tls is required when the value of the RequireTLS parameter is $true. - - The value ExternalAuthoritative requires you to set the value of the PermissionGroups parameter to ExchangeServers. ```yaml @@ -753,7 +732,7 @@ The Banner parameter specifies a custom SMTP 220 banner that's displayed to remo The default value of this parameter is blank ($null), which uses the following SMTP banner: -220 \ Microsoft ESMTP MAIL service ready at \\ +`220 Microsoft ESMTP MAIL service ready at ` ```yaml Type: String @@ -772,7 +751,6 @@ Accept wildcard characters: False 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. - - $false: BINARYMIME is disabled and isn't advertised in the EHLO response. The binary MIME extension is defined in RFC 3030. @@ -794,7 +772,6 @@ Accept wildcard characters: False 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. - - $false: CHUNKING is disabled and isn't advertised in the EHLO response. Chunking is defined in RFC 3030. @@ -831,8 +808,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -902,7 +878,6 @@ The Custom switch specifies the Custom usage type for the Receive connector. You This usage type assigns the following default permission groups and authentication methods: - Permission groups:None - - Authentication methods:TLS When you use this switch, you also need to use the Bindings and RemoteIPRanges parameters. @@ -928,17 +903,13 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID Although you can configure any accepted domain as the default domain, you typically specify an authoritative domain. The default domain is used by: -- The external postmaster address: postmaster@\. - +- The external postmaster address: `postmaster@`. - Encapsulated non-SMTP email addresses (Internet Mail Connector Encapsulated Address or IMCEA encapsulation). - - The primary address for all recipients in the default email address policy. If you configure another accepted domain as the default domain, the default email address policy isn't automatically updated. ```yaml @@ -958,7 +929,6 @@ Accept wildcard characters: False 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. - - $false: DSN is disabled and isn't advertised in the EHLO response. Delivery status notifications are defined in RFC 3461. @@ -998,19 +968,14 @@ Accept wildcard characters: False 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. - - $false: Mutual TLS authentication is disabled. Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative. - - The domain that's used for mutual TLS authentication must be configured in the following locations: - - The TLSReceiveDomainSecureList parameter on the Set-TransportConfig cmdlet. - - The AddressSpaces parameter on the Set-SendConnector cmdlet for the corresponding Send connector. - - The TLSSendDomainSecureList parameter on the Set-TransportConfig cmdlet. ```yaml @@ -1030,7 +995,6 @@ Accept wildcard characters: False 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. - - $false: 8BITMIME is disabled and isn't advertised in the EHLO response. 8-bit data transmission is defined in RFC 6152. @@ -1052,7 +1016,6 @@ Accept wildcard characters: False 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. - - $false: Kerberos is disabled. The Extended SMTP keyword AUTH NTLM is advertised in the EHLO response. Clients can only use NTLM for Integrated Windows authentication. The Generic Security Services application programming interface (GSSAPI) is an IETF standard for accessing security services. @@ -1074,7 +1037,6 @@ Accept wildcard characters: False 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. - - $false: The Receive connector is disabled. ```yaml @@ -1094,7 +1056,6 @@ Accept wildcard characters: False 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. - - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response. Enhanced status codes are defined in RFC 2034. @@ -1116,9 +1077,7 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used only if the connecting host supports it. Otherwise, connections are established without Extended Protection for Authentication. - - Require: Extended Protection for Authentication is required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection is rejected. Extended Protection for Authentication enhances the protection and handling of credentials when authenticating network connections using Integrated Windows authentication. Integrated Windows authentication is also known as NTLM. We strongly recommend that you use Extended Protection for Authentication if you are using Integrated Windows authentication. @@ -1140,11 +1099,8 @@ Accept wildcard characters: False 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. - - In the EHLO/HELO response of the Receive connector. - - In the most recent Received header field in the incoming message when. - - During TLS authentication. The default value is the FQDN of theExchange server that contains the Receive connector (for example edge01.contoso.com). You can specify a different FQDN (for example, mail.contoso.com). @@ -1166,15 +1122,12 @@ Accept wildcard characters: False 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. - - $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value. When you set this parameter to the value $true, the following changes are made to the Receive connector: - The XLONGADDR Extended SMTP extension is enabled and is advertised in the EHLO response. - - The accepted line length of an SMTP session is increased to 8,000 characters. - - Valid long addresses are accepted by the MAIL FROM and RCPT TO SMTP commands. You can only configure this parameter on Receive connectors in the Transport service on Mailbox servers. @@ -1193,9 +1146,9 @@ Accept wildcard characters: False ``` ### -MaxAcknowledgementDelay -This parameter isn't used by Microsoft Exchange Server 2016. It's only used by Microsoft Exchange 2010 servers in a coexistence environment. +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 acknowledgement 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 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 will time out and issue an acknowledgement anyway. +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. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1220,11 +1173,8 @@ The MaxHeaderSize parameter specifies the maximum size of the SMTP message heade When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1366,18 +1316,15 @@ The MaxMessageSize parameter specifies the maximum size of a message that's allo When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value for this parameter is from 65536 to 2147483647 bytes. -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: ByteQuantifiedSize @@ -1456,11 +1403,8 @@ Accept wildcard characters: False The MessageRateSource parameter specifies how the message submission rate is calculated. Valid values are: - None: The message submission rate isn't calculated. - - User: The message submission rate is calculated for sending users (specified with the MAIL FROM SMTP command). - - IPAddress: The message submission rate is calculated for sending hosts. - - All: The message submission rate is calculated for both sending users and sending hosts. ```yaml @@ -1480,7 +1424,6 @@ Accept wildcard characters: False 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. - - $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value. If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true. @@ -1502,24 +1445,18 @@ Accept wildcard characters: False 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 - - AnonymousUsers - - ExchangeUsers - - ExchangeServers - - ExchangeLegacyServers - - Partners - - Custom The default permission groups that are assigned to a Receive connector depend on the connector usage type parameter that was used when the connector was created (Client, Internal, Internet, Partner, or Usage). When you use the value Custom, you need to configure individual permissions by using the Add-ADPermission cmdlet. -For more information about the default permissions and security principals for permission groups, see [Receive connector permission groups](https://docs.microsoft.com/Exchange/mail-flow/connectors/receive-connectors#receive-connector-permission-groups). +For more information about the default permissions and security principals for permission groups, see [Receive connector permission groups](https://learn.microsoft.com/Exchange/mail-flow/connectors/receive-connectors#receive-connector-permission-groups). ```yaml Type: PermissionGroups @@ -1538,7 +1475,6 @@ Accept wildcard characters: False 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. - - $false: PIPELINING is disabled and isn't advertised in the EHLO response. Pipelining is defined in RFC 2920. @@ -1560,10 +1496,9 @@ Accept wildcard characters: False 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. - - Verbose: Protocol logging is enabled on the Receive connector. -For more information about protocol logging, see [Protocol logging](https://docs.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). +For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). ```yaml Type: ProtocolLoggingLevel @@ -1582,7 +1517,6 @@ Accept wildcard characters: False 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. - - $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value. ```yaml @@ -1602,7 +1536,6 @@ Accept wildcard characters: False 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. - - $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value. ```yaml @@ -1622,7 +1555,6 @@ Accept wildcard characters: False 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. - - $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value. ```yaml @@ -1642,7 +1574,6 @@ Accept wildcard characters: False 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. - - $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value. ```yaml @@ -1662,7 +1593,6 @@ Accept wildcard characters: False 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. - - $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value. ```yaml @@ -1682,11 +1612,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -1724,9 +1651,7 @@ Accept wildcard characters: False 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. - - Disabled: SIZE is disabled and isn't advertised in the EHLO response. - - EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers. SIZE is defined in RFC 1870. @@ -1748,7 +1673,6 @@ Accept wildcard characters: False 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. - - $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value. The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer. @@ -1789,7 +1713,7 @@ Accept wildcard characters: False ``` ### -TlsCertificateName -The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\X.500Issuer\X.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. +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 @@ -1809,17 +1733,18 @@ The TlsDomainCapabilities parameter specifies the capabilities that the Receive This parameter uses the following syntax: -"\:\,\\>"...,"\:\,\..."... +`"Domain1:Capability1,Capability2,"...,"Domain2:Capability1,Capability2,...",...` -The available \ values are: +You can only use this parameter in Exchange hybrid deployments, and the valid Capability values are: -- AcceptOorgProtocol +- AcceptCloudServicesMail (Exchange 2013 or later) +- AcceptOorgProtocol (Exchange 2010) -- AcceptOorgHeader +More Capability values are available, but there is no scenario to use them. For more information, see [Advanced Office 365 Routing](https://techcommunity.microsoft.com/t5/exchange-team-blog/advanced-office-365-routing-locking-down-exchange-on-premises/ba-p/609238). -The available \ values are an SMTP domain (for example, contoso.com), or the value NO-TLS for non-TLS encrypted inbound connections. +The available Domain values are an SMTP domain (for example, contoso.com), or the value NO-TLS for non-TLS encrypted inbound connections. -For example, "contoso.com:AcceptOorgProtocol","fabrikam.com:AcceptOorgProtocol,AcceptOorgHeader" +For example, `"contoso.com:AcceptOorgProtocol","fabrikam.com:AcceptCloudServicesMail"`. ```yaml Type: MultiValuedProperty @@ -1835,10 +1760,9 @@ Accept wildcard characters: False ``` ### -TransportRole -The TransportRole parameter specifies the transport service on the Mailbox server where the Receive connector is created.. Valid values are: +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. - - HubTransport: The Transport service where Exchange server and proxied client SMTP connections occur. ```yaml @@ -1875,12 +1799,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-RemoteDomain.md b/exchange/exchange-ps/exchange/New-RemoteDomain.md similarity index 91% rename from exchange/exchange-ps/exchange/mail-flow/New-RemoteDomain.md rename to exchange/exchange-ps/exchange/New-RemoteDomain.md index b5010d1d30..d482738214 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-RemoteDomain.md +++ b/exchange/exchange-ps/exchange/New-RemoteDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-remotedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-RemoteDomain @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-RemoteDomain cmdlet to create a managed connection for a remote domain. When you create a remote domain, you can control mail flow with more precision, apply message formatting and messaging policies and specify acceptable character sets for messages sent to and received from the remote domain. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,12 @@ For information about the parameter sets in the Syntax section below, see [Excha New-RemoteDomain [-Name] -DomainName [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,35 +42,35 @@ This example creates the remote domain named Contoso for the domain contoso.com ## PARAMETERS -### -DomainName -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). +### -Name +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: SmtpDomainWithSubdomains +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 +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 ("). +### -DomainName +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). ```yaml -Type: String +Type: SmtpDomainWithSubdomains Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -79,8 +79,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -137,12 +136,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/New-RemoteMailbox.md b/exchange/exchange-ps/exchange/New-RemoteMailbox.md similarity index 78% rename from exchange/exchange-ps/exchange/federation-and-hybrid/New-RemoteMailbox.md rename to exchange/exchange-ps/exchange/New-RemoteMailbox.md index 952b91ab32..2647a103bb 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/New-RemoteMailbox.md +++ b/exchange/exchange-ps/exchange/New-RemoteMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/new-remotemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-RemoteMailbox @@ -17,72 +16,137 @@ This cmdlet is available only in on-premises Exchange. Use the New-RemoteMailbox cmdlet to create a mail user in the on-premises Active Directory and also create an associated mailbox in the cloud-based service. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Default ``` -New-RemoteMailbox [-Name] -Password -UserPrincipalName [-Alias ] - [-ArbitrationMailbox ] [-Archive] [-Confirm] [-DisplayName ] - [-DomainController ] [-FirstName ] [-ImmutableId ] [-Initials ] - [-LastName ] [-ModeratedBy ] [-ModerationEnabled ] - [-OnPremisesOrganizationalUnit ] [-PrimarySmtpAddress ] - [-RemotePowerShellEnabled ] [-RemoteRoutingAddress ] - [-ResetPasswordOnNextLogon ] [-SamAccountName ] - [-SendModerationNotifications ] [-WhatIf] [-ACLableSyncedObjectEnabled] +New-RemoteMailbox [-Name] -Password -UserPrincipalName + [-ACLableSyncedObjectEnabled] + [-Alias ] + [-Archive] + [-Confirm] + [-DisplayName ] + [-DomainController ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OnPremisesOrganizationalUnit ] + [-PrimarySmtpAddress ] + [-RemotePowerShellEnabled ] + [-RemoteRoutingAddress ] + [-ResetPasswordOnNextLogon ] + [-SamAccountName ] + [-SendModerationNotifications ] + [-WhatIf] [] ``` ### Room ``` New-RemoteMailbox [-Name] [-Password ] [-Room] [-UserPrincipalName ] - [-Alias ] [-ArbitrationMailbox ] [-Archive] [-Confirm] [-DisplayName ] - [-DomainController ] [-FirstName ] [-ImmutableId ] [-Initials ] - [-LastName ] [-ModeratedBy ] [-ModerationEnabled ] - [-OnPremisesOrganizationalUnit ] [-PrimarySmtpAddress ] - [-RemotePowerShellEnabled ] [-RemoteRoutingAddress ] - [-ResetPasswordOnNextLogon ] [-SamAccountName ] - [-SendModerationNotifications ] [-WhatIf] [-ACLableSyncedObjectEnabled] + [-ACLableSyncedObjectEnabled] + [-Alias ] + [-Archive] + [-Confirm] + [-DisplayName ] + [-DomainController ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OnPremisesOrganizationalUnit ] + [-PrimarySmtpAddress ] + [-RemotePowerShellEnabled ] + [-RemoteRoutingAddress ] + [-ResetPasswordOnNextLogon ] + [-SamAccountName ] + [-SendModerationNotifications ] + [-WhatIf] [] ``` ### Equipment ``` New-RemoteMailbox [-Name] [-Equipment] [-Password ] [-UserPrincipalName ] - [-Alias ] [-ArbitrationMailbox ] [-Archive] [-Confirm] [-DisplayName ] - [-DomainController ] [-FirstName ] [-ImmutableId ] [-Initials ] - [-LastName ] [-ModeratedBy ] [-ModerationEnabled ] - [-OnPremisesOrganizationalUnit ] [-PrimarySmtpAddress ] - [-RemotePowerShellEnabled ] [-RemoteRoutingAddress ] - [-ResetPasswordOnNextLogon ] [-SamAccountName ] - [-SendModerationNotifications ] [-WhatIf] [-ACLableSyncedObjectEnabled] + [-ACLableSyncedObjectEnabled] + [-Alias ] + [-Archive] + [-Confirm] + [-DisplayName ] + [-DomainController ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OnPremisesOrganizationalUnit ] + [-PrimarySmtpAddress ] + [-RemotePowerShellEnabled ] + [-RemoteRoutingAddress ] + [-ResetPasswordOnNextLogon ] + [-SamAccountName ] + [-SendModerationNotifications ] + [-WhatIf] [] ``` ### Shared ``` New-RemoteMailbox [-Name] [-Shared] [-Password ] [-UserPrincipalName ] - [-Alias ] [-ArbitrationMailbox ] [-Archive] [-Confirm] [-DisplayName ] - [-DomainController ] [-FirstName ] [-ImmutableId ] [-Initials ] - [-LastName ] [-ModeratedBy ] [-ModerationEnabled ] - [-OnPremisesOrganizationalUnit ] [-PrimarySmtpAddress ] - [-RemotePowerShellEnabled ] [-RemoteRoutingAddress ] - [-ResetPasswordOnNextLogon ] [-SamAccountName ] - [-SendModerationNotifications ] [-WhatIf] [-ACLableSyncedObjectEnabled] + [-ACLableSyncedObjectEnabled] + [-Alias ] + [-Archive] + [-Confirm] + [-DisplayName ] + [-DomainController ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OnPremisesOrganizationalUnit ] + [-PrimarySmtpAddress ] + [-RemotePowerShellEnabled ] + [-RemoteRoutingAddress ] + [-ResetPasswordOnNextLogon ] + [-SamAccountName ] + [-SendModerationNotifications ] + [-WhatIf] [] ``` ### AccountDisabled ``` New-RemoteMailbox [-Name] [-AccountDisabled] [-Password ] [-UserPrincipalName ] - [-Alias ] [-ArbitrationMailbox ] [-Archive] [-Confirm] [-DisplayName ] - [-DomainController ] [-FirstName ] [-ImmutableId ] [-Initials ] - [-LastName ] [-ModeratedBy ] [-ModerationEnabled ] - [-OnPremisesOrganizationalUnit ] [-PrimarySmtpAddress ] - [-RemotePowerShellEnabled ] [-RemoteRoutingAddress ] - [-ResetPasswordOnNextLogon ] [-SamAccountName ] - [-SendModerationNotifications ] [-WhatIf] [-ACLableSyncedObjectEnabled] + [-ACLableSyncedObjectEnabled] + [-Alias ] + [-Archive] + [-Confirm] + [-DisplayName ] + [-DomainController ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OnPremisesOrganizationalUnit ] + [-PrimarySmtpAddress ] + [-RemotePowerShellEnabled ] + [-RemoteRoutingAddress ] + [-ResetPasswordOnNextLogon ] + [-SamAccountName ] + [-SendModerationNotifications ] + [-WhatIf] [] ``` @@ -93,13 +157,15 @@ Directory synchronization must be configured correctly for a mailbox to be creat The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$Credentials = Get-Credential; New-RemoteMailbox -Name "Kim Akers" -Password $Credentials.Password -UserPrincipalName kim@corp.contoso.com +$Credentials = Get-Credential + +New-RemoteMailbox -Name "Kim Akers" -Password $Credentials.Password -UserPrincipalName kim@corp.contoso.com ``` This example creates an on-premises mail user and its associated mailbox in the service. The remote routing address doesn't need to be specified because mail flow between the on-premises organization and the service has been configured. Using this configuration, the New-RemoteMailbox cmdlet automatically calculates the SMTP address of the mailbox to be used with the RemoteRoutingAddress parameter. This example also assumes directory synchronization has been configured. @@ -110,7 +176,9 @@ After the new mail user is created, directory synchronization synchronizes the n ### Example 2 ```powershell -$Credentials = Get-Credential; New-RemoteMailbox -Name "Kim Akers" -Password $Credentials.Password -UserPrincipalName kim@corp.contoso.com -OnPremisesOrganizationalUnit "corp.contoso.com/Archive Users" -Archive +$Credentials = Get-Credential + +New-RemoteMailbox -Name "Kim Akers" -Password $Credentials.Password -UserPrincipalName kim@corp.contoso.com -OnPremisesOrganizationalUnit "corp.contoso.com/Archive Users" -Archive ``` This example does the following steps: @@ -125,32 +193,28 @@ As in Example 1, this example assumes that mail flow and directory synchronizati ## PARAMETERS -### -AccountDisabled -The AccountDisabled switch specifies whether to create the mail user in a disabled state. You don't have to specify a value with this switch. +### -Name +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: SwitchParameter -Parameter Sets: AccountDisabled +Type: String +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Equipment -The Equipment switch specifies that the mailbox in the service should be created as an equipment resource mailbox. - -Equipment mailboxes are resource mailboxes that aren't associated with a specific location (for example, vehicles or computers). - -You can't use this switch with the Room switch. +### -AccountDisabled +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: Equipment +Parameter Sets: AccountDisabled Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -161,17 +225,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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 ("). +### -Equipment +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). + +You can't use this switch with the Room switch. ```yaml -Type: String -Parameter Sets: (All) +Type: SwitchParameter +Parameter Sets: Equipment Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -180,7 +248,11 @@ Accept wildcard characters: False ### -Password The Password parameter specifies the password used by the mail user to secure his or her account and associated mailbox in the service. -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. ```yaml Type: SecureString @@ -209,7 +281,7 @@ Accept wildcard characters: False ``` ### -Room -The Room switch specifies that the mailbox in the service should be created as a room resource mailbox. +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. @@ -227,7 +299,7 @@ Accept wildcard characters: False ``` ### -Shared -**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/cmdlets-to-create-modify-remote-shared-mailbox-in-on-premises-exchange). +**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. @@ -247,7 +319,7 @@ Accept wildcard characters: False ``` ### -UserPrincipalName -The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format \@\. Typically, the \ value is the domain where the user account resides. +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 @@ -275,28 +347,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. - -The value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. - -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: - -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. - -- Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). - -If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). - -The Alias parameter never generates or updates the primary email address of a mail contact or a mail user. +### -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: String +Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -305,36 +363,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ArbitrationMailbox -This parameter is available or functional 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: - -- Name - -- Alias - -- Distinguished name (DN) +### -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. -- Canonical DN +The Alias value can contain letters, numbers and the following characters: -- \\\\ +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -- Email address +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- GUID +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: -- LegacyExchangeDN +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. +- Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). -- SamAccountName +If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). -- User ID or user principal name (UPN) +The Alias parameter never generates or updates the primary email address of a mail contact or a mail user. ```yaml -Type: MailboxIdParameter +Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -362,8 +416,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -483,18 +536,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -515,7 +563,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -539,11 +586,8 @@ The OnPremisesOrganizationalUnit parameter specifies the organizational unit (OU 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 - - Canonical name - - Distinguished name (DN) - - GUID This parameter has no effect on the mailbox in the service. @@ -578,11 +622,14 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled -The RemotePowerShellEnabled parameter specifies whether the user can connect to Exchange using remote PowerShell. Remote PowerShell is required to open the Exchange Management Shell on Exchange servers, or to use Windows PowerShell open and import a remote PowerShell session to Exchange. Access to remote PowerShell is required even if you're trying to open the Exchange Management Shell on the local Exchange server. Valid values are: +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. +- $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. -- $true: The user can use remote PowerShell. This is the default value. +Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. -- $false: The user can't use remote PowerShell. +A user's experience in any of these management interfaces is still controlled by the role-based access control (RBAC) permissions that are assigned to them. ```yaml Type: Boolean @@ -598,7 +645,7 @@ Accept wildcard characters: False ``` ### -RemoteRoutingAddress -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. +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. @@ -619,7 +666,6 @@ Accept wildcard characters: False 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. - - $false: The user isn't required to change their password the next time they log on. This is the default value. ```yaml @@ -636,7 +682,7 @@ Accept wildcard characters: False ``` ### -SamAccountName -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 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. +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 @@ -655,9 +701,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -691,33 +735,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-ReportSubmissionPolicy.md b/exchange/exchange-ps/exchange/New-ReportSubmissionPolicy.md new file mode 100644 index 0000000000..6ae7128ad5 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ReportSubmissionPolicy.md @@ -0,0 +1,1029 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ReportSubmissionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-ReportSubmissionPolicy cmdlet to create the report submission policy in your cloud-based organization. The report submission policy controls most of the user reported message settings in the organization. + +**Note**: If the policy already exists (the Get-ReportSubmissionPolicy cmdlet returns output), you can't use this cmdlet. To delete the existing policy and start over with the default settings, use the Remove-ReportSubmissionPolicy cmdlet first. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ReportSubmissionPolicy + [-DisableQuarantineReportingOption ] + [-DisableUserSubmissionOptions ] + [-EnableCustomizedMsg ] + [-EnableCustomNotificationSender ] + [-EnableOrganizationBranding ] + [-EnableReportToMicrosoft ] + [-EnableThirdPartyAddress ] + [-EnableUserEmailNotification ] + [-JunkReviewResultMessage ] + [-NotificationFooterMessage ] + [-NotificationSenderAddress ] + [-NotificationsForCleanSubmissionAirInvestigationsEnabled ] + [-NotificationsForPhishMalwareSubmissionAirInvestigationsEnabled ] + [-NotificationsForSpamSubmissionAirInvestigationsEnabled ] + [-NotificationsForSubmissionAirInvestigationsEnabled ] + [-NotJunkReviewResultMessage ] + [-OnlyShowPhishingDisclaimer ] + [-PhishingReviewResultMessage ] + [-PostSubmitMessage ] + [-PostSubmitMessageEnabled ] + [-PostSubmitMessageForJunk ] + [-PostSubmitMessageForNotJunk ] + [-PostSubmitMessageForPhishing ] + [-PostSubmitMessageTitle ] + [-PostSubmitMessageTitleForJunk ] + [-PostSubmitMessageTitleForNotJunk ] + [-PostSubmitMessageTitleForPhishing ] + [-PreSubmitMessage ] + [-PreSubmitMessageEnabled ] + [-PreSubmitMessageForJunk ] + [-PreSubmitMessageForNotJunk ] + [-PreSubmitMessageForPhishing ] + [-PreSubmitMessageTitle ] + [-PreSubmitMessageTitleForJunk ] + [-PreSubmitMessageTitleForNotJunk ] + [-PreSubmitMessageTitleForPhishing ] + [-ReportChatMessageEnabled ] + [-ReportChatMessageToCustomizedAddressEnabled ] + [-ReportJunkAddresses ] + [-ReportJunkToCustomizedAddress ] + [-ReportNotJunkAddresses ] + [-ReportNotJunkToCustomizedAddress ] + [-ReportPhishAddresses ] + [-ReportPhishToCustomizedAddress ] + [-ThirdPartyReportAddresses ] + [-UserSubmissionOptions ] + [-UserSubmissionOptionsMessage ] + [] +``` + +## DESCRIPTION +The report submission policy controls most of the settings for user submissions in the Microsoft Defender portal at . + +The report submission rule (\*-ReportSubmissionRule cmdlets) controls the email address of the reporting mailbox where user reported messages are delivered. + +When you set the email address of the reporting mailbox in the Microsoft Defender portal at , the same email address is also set in the following parameters in the \*-ReportSubmissionPolicy cmdlets: + +- Microsoft integrated reporting using Microsoft reporting tools in Outlook: The ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses parameters. +- Microsoft integrated reporting using third-party tools in Outlook: The ThirdPartyReportAddresses parameter. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ReportSubmissionPolicy +``` + +This example creates the one and only report submission policy named DefaultReportSubmissionPolicy with the default values: reporting in Outlook is on, Microsoft reporting tools in Outlook are used, and reported messages are sent only to Microsoft (the reporting mailbox isn't used). + +### Example 2 +```powershell +$usersub = "reportedmessages@contoso.com" + +New-ReportSubmissionPolicy -ReportJunkToCustomizedAddress $true -ReportJunkAddresses $usersub -ReportNotJunkToCustomizedAddress $true -ReportNotJunkAddresses $usersub -ReportPhishToCustomizedAddress $true -ReportPhishAddresses $usersub + +New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub +``` + +This example creates the report submission policy with the following values: reporting in Outlook is on, Microsoft reporting tools in Outlook are used, and reported messages are sent to Microsoft and the specified reporting mailbox in Exchange Online. + +**Notes**: + +- The default value of the EnableReportToMicrosoft parameter is $true and the default value of the EnableThirdPartyAddress parameter is $false, so you don't need to use them. +- To create the policy, you need to specify the same email address in the ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhisAddresses parameters, and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlets. +- Like the report submission policy, you can create the report submission rule only if it doesn't already exist. If the rule already exists, you can use Set-ReportSubmissionRule to change the email address of the reporting mailbox, or Remove-ReportSubmissionRule to delete it and recreate it. + +### Example 3 +```powershell +$usersub = "userreportedmessages@fabrikam.com" + +New-ReportSubmissionPolicy -EnableReportToMicrosoft $false -ReportJunkToCustomizedAddress $true -ReportJunkAddresses $usersub -ReportNotJunkToCustomizedAddress $true -ReportNotJunkAddresses $usersub -ReportPhishToCustomizedAddress $true -ReportPhishAddresses $usersub -DisableUserSubmissionOptions $false + +New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub +``` + +This example creates the report submission policy with the following values: reporting in Outlook is on, Microsoft reporting tools in Outlook are used, and reported messages are sent only to the specified reporting mailbox in Exchange Online. + +### Example 4 +```powershell +$usersub = "thirdpartyreporting@wingtiptoys.com" + +New-ReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableThirdPartyAddress $true -ThirdPartyReportAddresses $usersub + +New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub +``` + +This example creates the report submission policy with the following values: reporting in Outlook is on and third-party reporting tools in Outlook are used to send reported messages to the specified reporting mailbox in Exchange Online. + +### Example 5 +```powershell +New-ReportSubmissionPolicy -EnableReportToMicrosoft $false +``` + +This example creates the report submission policy with the following values: reporting in Outlook is off. Microsoft reporting tools in Outlook are not available to users and messages reported by third-party tools in Outlook are not available on the Submissions page in the Microsoft Defender portal. + +## PARAMETERS + +### -DisableQuarantineReportingOption +The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: + +- $true: Users can't report quarantined messages from quarantine. +- $false: Users can report quarantined messages from quarantine. This is the default value. + +This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableUserSubmissionOptions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableCustomizedMsg +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableCustomNotificationSender +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. +- $false: Use the default sender email address. This is the default value. + +You specify the sender email address using the NotificationSenderAddress parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOrganizationBranding +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. +- $false: Don't use the company logo in the footer text. Use the Microsoft logo. + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableReportToMicrosoft +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: + +- **Microsoft reporting tools are available in Outlook for users to report messages to Microsoft only (the reporting mailbox isn't used)**: The ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $false. This is the default result. +- **Microsoft reporting tools are available in Outlook for users to report messages to Microsoft and reported messages are sent to the specified reporting mailbox**: The ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $true. To create the policy, use the same email address in the ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhisAddresses parameters, and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. + +The value $false for this parameter disables reporting in Outlook. The following configurations are possible: + +- **Microsoft reporting tools are available in Outlook, but reported messages are sent only to the reporting mailbox**: The ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $true. To create the policy, use the same email address in the ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhisAddresses parameters, and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. +- **Reporting in Outlook is disabled. Microsoft reporting tools are not available in Outlook. Any messages reported by users in Outlook with third-party reporting tools aren't visible on the Submissions page in the Microsoft Defender portal**: The EnableThirdPartyAddress, ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $false. + +This parameter is required to create the report submission policy only if you set the value to $false (the default value is $true). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableThirdPartyAddress +The EnableThirdPartyAddress parameter specifies whether you're using third-party 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 third-party 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. +- $false: Third-party reporting tools in Outlook aren't used. + +This parameter is required to create the report submission policy only if you set the value to $true (the default value is $false). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUserEmailNotification +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. +- $false: Customized admin review result messages are not sent. + +Use the JunkReviewResultMessage, NotJunkReviewResultMessage, PhishingReviewResultMessage parameters to configure the message body text that's used for each verdict. + +Use the NotificationFooterMessage parameter for the footer that's used for all verdicts (junk, not junk, and phishing). + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -JunkReviewResultMessage +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. + +Use the NotificationFooterMessage parameter to customize the footer text of result messages. + +Use the NotificationSenderAddress parameter to customize the sender email address of result messages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotJunkReviewResultMessage +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. + +Use the NotificationFooterMessage parameter to customize the footer text of result messages. + +Use the NotificationSenderAddress parameter to customize the sender email address of result messages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationFooterMessage +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. + +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationSenderAddress +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForCleanSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForPhishMalwareSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForSpamSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlyShowPhishingDisclaimer +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishingReviewResultMessage +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. + +Use the NotificationFooterMessage parameter to customize the footer text of result messages. + +Use the NotificationSenderAddress parameter to customize the sender email address of result messages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessage +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. + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageEnabled +{{ Fill PostSubmitMessageEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageForJunk +Don't use this parameter. Use the PostSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageForNotJunk +Don't use this parameter. Use the PostSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageForPhishing +Don't use this parameter. Use the PostSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitle +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. + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitleForJunk +Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitleForNotJunk +Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitleForPhishing +Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessage +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. + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageEnabled +{{ Fill PreSubmitMessageEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageForJunk +Don't use this parameter. Use the PreSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageForNotJunk +Don't use this parameter. Use the PreSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageForPhishing +Don't use this parameter. Use the PreSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitle +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. + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitleForJunk +Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitleForNotJunk +Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitleForPhishing +Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportChatMessageEnabled +{{ Fill ReportChatMessageEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportChatMessageToCustomizedAddressEnabled +{{ Fill ReportChatMessageToCustomizedAddressEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportJunkAddresses +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 third-party reporting tools in Outlook. + +This parameter is required to create the report submission policy if the ReportJunkToCustomizedAddress parameter value is $true. + +You can't use this parameter by itself. You need to specify the same email address for the ReportJunkAddresses, ReportNotJunkAddresses and ReportPhishAddresses parameters. + +You also need to specify the same email address in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportJunkToCustomizedAddress +The ReportJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or third-party 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. +- $false: User reported messages are not sent to the reporting mailbox. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameters in the same command. + +This parameter is required to create the report submission policy if you're using reporting in Outlook (see the EnableReportToMicrosoft parameter) and sending reported messages to the reporting mailbox (exclusively or in addition to reporting to Microsoft). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportNotJunkAddresses +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 third-party reporting tools in Outlook. + +This parameter is required to create the report submission policy if the ReportNotJunkToCustomizedAddress parameter value is $true. + +You can't use this parameter by itself. You need to specify the same email address for the ReportJunkAddresses, ReportNotJunkAddresses and ReportPhishAddresses parameters. + +You also need to specify the same email address in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportNotJunkToCustomizedAddress +The ReportNotJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or third-party 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. +- $false: User reported messages are not sent to the reporting mailbox. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameters. + +This parameter is required to create the report submission policy if you're using reporting in Outlook (see the EnableReportToMicrosoft parameter) and sending reported messages to the reporting mailbox (exclusively or in addition to reporting to Microsoft). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportPhishAddresses +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 third-party reporting tools in Outlook. + +This parameter is required to create the report submission policy if the ReportPhishToCustomizedAddress parameter value is $true. + +You can't use this parameter by itself. You need to specify the same email address for the ReportJunkAddresses, ReportNotJunkAddresses and ReportPhishAddresses parameters. + +You also need to specify the same email address in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportPhishToCustomizedAddress +The ReportPhishToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or third-party 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. +- $false: User reported messages are not sent to the reporting mailbox. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameters. + +This parameter is required to create the report submission policy if you're using reporting in Outlook (see the EnableReportToMicrosoft parameter) and sending reported messages to the reporting mailbox (exclusively or in addition to reporting to Microsoft). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThirdPartyReportAddresses +Use the ThirdPartyReportAddresses parameter to specify the email address of the reporting mailbox in Exchange Online when you're using a third-party 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 third-party tools (`-EnableThirdPartyAddress $true`). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserSubmissionOptions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserSubmissionOptionsMessage +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/New-ReportSubmissionRule.md new file mode 100644 index 0000000000..9128905359 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ReportSubmissionRule.md @@ -0,0 +1,204 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ReportSubmissionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-ReportSubmissionRule cmdlet to create the report submission rule in your cloud-based organization. The report submission rule identifies the reporting mailbox where user reported messages are delivered. + +**Note**: If the rule already exists (the Get-ReportSubmissionRule cmdlet returns output), you can't use this cmdlet. To delete the existing rule and start over, use the Remove-ReportSubmissionRule cmdlet first. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ReportSubmissionRule [-Name] -ReportSubmissionPolicy + [-Comments ] + [-Confirm] + [-Enabled ] + [-SentTo ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can use this cmdlet only if the following statements are true: + +- The report submission rule doesn't exist (the Get-ReportSubmissionRule cmdlet returns no output). +- The report submission policy exists (the Get-ReportSubmissionPolicy cmdlet returns output). + +The SentTo parameter identifies the email address of the reporting mailbox. Your organization needs a report submission rule only to send user reported messages to the reporting mailbox using Microsoft or third-party reporting tools in Outlook (reporting in Outlook is turned on). + +When you set the email address of the reporting mailbox in the Microsoft Defender portal at , the same email address is also set in the *\-ReportSubmissionPolicy cmdlets: + +- Microsoft integrated reporting using Microsoft reporting tools in Outlook: ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses (all three must be the same value). +- Microsoft integrated reporting using third-party reporting tools in Outlook: ThirdPartyReportAddresses. + +When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo "userreportedmessages@contoso.onmicrosoft.com" +``` + +This example creates the report submission rule. The reporting mailbox is userreportedmessages@contoso.onmicrosoft.com. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportSubmissionPolicy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the rule is enabled or disabled. Valid values are: + +- $true: The rule is enabled. This is the default value. +- $false: The rule is disabled. + +After you create the rule, use the Enable-ReportSubmissionRule and Disable-ReportSubmissionRule cmdlets to enable or disable the rule. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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): + +- Microsoft integrated reporting is enabled using Microsoft reporting tools in Outlook: `-EnableThirdPartyAddress $false -ReportJunkToCustomizedAddress $true -ReportNotJunkToCustomizedAddress $true -ReportPhishToCustomizedAddress $true`. +- Microsoft integrated reporting is enabled using third-party reporting tools in Outlook: `-EnableReportToMicrosoft $false -EnableThirdPartyAddress $true -ReportJunkToCustomizedAddress $false -ReportNotJunkToCustomizedAddress $false -ReportPhishToCustomizedAddress $false`. + +If you set the email address of the reporting mailbox in the Microsoft Defender portal, the following parameters in the *\-ReportSubmissionPolicy cmdlets are set to the same value: + +- Microsoft integrated reporting using Microsoft reporting tools in Outlook: ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses (all three must be the same value). +- Microsoft integrated reporting using third-party reporting tools in Outlook: ThirdPartyReportAddresses. + +When you use this cmdlet to set the email address of the reporting mailbox, the related parameter values in the *\-ReportSubmissionPolicy cmdlets are not updated, which doesn't affect the functionality of the reporting mailbox. You should update the related values in the \*-ReportSubmissionPolicy cmdlets for consistency and to avoid confusion. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md new file mode 100644 index 0000000000..80238a5236 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md @@ -0,0 +1,748 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-RetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-RetentionCompliancePolicy cmdlet to create new retention policies and new retention label policies in the Microsoft Purview compliance portal. Creating a new policy also requires use of the New-RetentionComplianceRule cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +New-RetentionCompliancePolicy [-Name] + [-Applications ] + [-Comment ] + [-Confirm] + [-Enabled ] + [-ExchangeLocation ] + [-ExchangeLocationException ] + [-Force] + [-IsSimulation] + [-ModernGroupLocation ] + [-ModernGroupLocationException ] + [-OneDriveLocation ] + [-OneDriveLocationException ] + [-PolicyRBACScopes ] + [-PolicyTemplateInfo ] + [-PriorityCleanup] + [-PublicFolderLocation ] + [-RestrictiveRetention ] + [-RetainCloudAttachment ] + [-SharePointLocation ] + [-SharePointLocationException ] + [-SkipPriorityCleanupConfirmation] + [-SkypeLocation ] + [-SkypeLocationException ] + [-WhatIf] + [] +``` + +### TeamLocation +``` +New-RetentionCompliancePolicy [-Name] + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-IsSimulation] + [-PriorityCleanup] + [-RestrictiveRetention ] + [-RetainCloudAttachment ] + [-SkipPriorityCleanupConfirmation] + [-TeamsChannelLocation ] + [-TeamsChannelLocationException ] + [-TeamsChatLocation ] + [-TeamsChatLocationException ] + [-WhatIf] + [] +``` + +### AdaptiveScopeLocation +``` +New-RetentionCompliancePolicy [-Name] -AdaptiveScopeLocation + [-Applications ] + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-IsSimulation] + [-PriorityCleanup] + [-RestrictiveRetention ] + [-RetainCloudAttachment ] + [-SkipPriorityCleanupConfirmation] + [-WhatIf] + [] +``` + +## DESCRIPTION +Policies are not valid until a rule is added (for retention policies) or a label is added (for retention label policies). For more information, see [New-RetentionComplianceRule](/powershell/module/exchange/new-retentioncompliancerule). In addition, at least one location parameter must be defined to create a retention policy or retention label policy. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal]/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-RetentionCompliancePolicy -Name "Regulation 123 Compliance" -ExchangeLocation "Kitty Petersen", "Scott Nakamura" -SharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" +``` + +This example creates a retention policy named "Regulation 123 Compliance" for the mailboxes of Kitty Petersen and Scott Nakamura, and the finance SharePoint site. + +The next step is to use the New-RetentionComplianceRule cmdlet to add a rule to the retention policy. + +### Example 2 +```powershell +New-RetentionCompliancePolicy -Name "Marketing Department" -Enabled $true -SharePointLocation https://contoso.sharepoint.com -RetainCloudAttachment $true -Comment "Regulatory compliance for Marketing Dept." +``` + +This example creates a new auto-apply label policy targeted to cloud attachments named Marketing Department with the specified details. + +The next step is to use the New-RetentionComplianceRule cmdlet to add a retention label to the retention label policy. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdaptiveScopeLocation +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Applications +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. +- `Group:SharePoint` for the SharePoint site that's connected to the Microsoft 365 Group. +- `"Group:Exchange,SharePoint"` for both the mailbox and the SharePoint site that are connected to the Microsoft 365 Group. +- blank (`$null`): This is the default value, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default, AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). +- The value All for all mailboxes. You can only use this value by itself. + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +If no mailboxes are specified, then no mailboxes are placed on hold. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocationException +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 +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsSimulation +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). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModernGroupLocation +The ModernGroupLocation parameter specifies the Microsoft 365 Groups to include in the policy. Valid values are: + +- A Microsoft 365 Group +- The value All for all Microsoft 365 Groups. You can only use this value by itself. + +To identify the Microsoft 365 Group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModernGroupLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +**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. + +Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTemplateInfo +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +The PriorityCleanup switch specifies whether to create a [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup) policy to expedite the deletion of sensitive content, overriding any existing retention settings or eDiscovery holds. 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictiveRetention +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. +- $false: Preservation Lock isn't enabled for the policy. This is the default value. + +After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. + +Therefore, before you lock a retention policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetainCloudAttachment +**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: + +- $true: The policy is a cloud attachment policy. +- $false: The policy is not a cloud attachment policy. This is the default value. + +For the value $true, you can only use the following location parameters: + +- SharePointLocation and SharePointLocationException +- OneDriveLocation and OneDriveLocationException +- ModernGroupLocation and ModernGroupLocationException + +A tag that uses a cloud attachment policy to create a rule can be a record label or a regulatory label. You can't use a publishing tag for a cloud attachment policy to create a rule; only apply tags are supported. + +The RetainCloudAttachment parameter is not available on the Set-RetentionCompliancePolicy cmdlet. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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"`. + +SharePoint sites can't be added to the policy until they have been indexed. If no sites are specified, then no sites are placed on hold. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipPriorityCleanupConfirmation +{{ Fill SkipPriorityCleanupConfirmation Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkypeLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkypeLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelLocation +The TeamsChannelLocation parameter specifies the Teams to include in the policy. + +You can use any value that uniquely identifies the team. For example: + +- Name +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelLocationException +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 +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChatLocation +The TeamsChatLocation parameter specifies the Teams users to include in the policy. + +You can use any value that uniquely identifies the user. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChatLocationException +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 +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md new file mode 100644 index 0000000000..c7471abe72 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md @@ -0,0 +1,437 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-RetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-RetentionComplianceRule cmdlet to create new retention rules in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### ComplianceTag +``` +New-RetentionComplianceRule -ApplyComplianceTag -Policy + [-ContentContainsSensitiveInformation ] + [-Confirm] + [-ContentMatchQuery ] + [-ExpirationDateOption ] + [-IRMRiskyUserProfiles ] + [-MachineLearningModelIDs ] + [-PriorityCleanup] + [-RetentionComplianceAction ] + [-WhatIf] + [] +``` + +### Default +``` +New-RetentionComplianceRule [-Name] -Policy + [-Comment ] + [-ExcludedItemClasses ] + [-RetentionDuration ] + [-RetentionDurationDisplayHint ] + [-Confirm] + [-ContentMatchQuery ] + [-ExpirationDateOption ] + [-PriorityCleanup] + [-RetentionComplianceAction ] + [-WhatIf] + [] +``` + +### PublishComplianceTag +``` +New-RetentionComplianceRule -Policy -PublishComplianceTag + [-Confirm] + [-ExpirationDateOption ] + [-PriorityCleanup] + [-RetentionComplianceAction ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The retention rule must be added to an existing retention policy using the Policy parameter. Only one rule can be added to each retention policy. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-RetentionComplianceRule -Name InternalCompanyRule -Policy "Internal Company Policy" -RetentionDuration Unlimited +``` + +This example creates a new case hold rule named InternalCompanyRule and adds it to the existing case hold policy named "Internal Company Policy". Content will be held indefinitely. + +### Example 2 +```powershell +New-RetentionComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -RetentionDuration 365 -RetentionComplianceAction KeepAndDelete -ExpirationDateOption ModificationAgeInDays +``` + +This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content will be held for one year from the day content was last modified before it is deleted. + +## PARAMETERS + +### -Name +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. + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyComplianceTag +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. + +You can't use this parameter with the Name or PublishComplianceTag parameters. + +You can't use this parameter for Teams retention rules. + +```yaml +Type: String +Parameter Sets: ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +The Policy parameter specifies the policy to contain the rule. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublishComplianceTag +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. + +You can't use this parameter in the following scenarios: + +- With the Name or ApplyComplianceTag parameters. +- For Teams retention rules. +- With cloud attachment policies. + +```yaml +Type: String +Parameter Sets: PublishComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +You can use this parameter with the ApplyComplianceTag parameter. + +You can't use this parameter for Teams retention rules. + +```yaml +Type: PswsHashtable[] +Parameter Sets: ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +You can't use this parameter for Teams retention rules. + +```yaml +Type: String +Parameter Sets: ComplianceTag, Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedItemClasses +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 +- IPM.Note.Microsoft.Conversation.Voice +- IPM.Note.Microsoft.Missed +- IPM.Note.Microsoft.Missed.Voice +- IPM.Note.Microsoft.Voicemail +- IPM.Note.Microsoft.VoiceMessage.UA +- IPM.Note.Microsoft.Voicemail.UM +- IPM.Note.Microsoft.Voicemail.UM.CA + +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or third-party message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. + +You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. + +You can't use this parameter for Teams retention rules. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpirationDateOption +The ExpirationDateOption parameter specifies whether the expiration date is calculated from the content creation date or last modification date. Valid values are: + +- CreationAgeInDays +- ModificationAgeInDays + +You can't use this parameter for Teams retention rules. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IRMRiskyUserProfiles +{{ Fill IRMRiskyUserProfiles Description }} + +```yaml +Type: String +Parameter Sets: ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MachineLearningModelIDs +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionComplianceAction +The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: + +- Delete +- Keep +- KeepAndDelete + +If you don't use this parameter, the retention policy is created as an "UniH" policy instead of a "mbx" policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies the hold duration for the retention rule. Valid values are: + +- An integer: The hold duration in days. +- Unlimited: The content is held indefinitely. + +```yaml +Type: Unlimited +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDurationDisplayHint +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 +- Years + +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. + +You can't use this parameter for Teams retention rules. + +```yaml +Type: HoldDurationHint +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionPolicy.md b/exchange/exchange-ps/exchange/New-RetentionPolicy.md similarity index 76% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionPolicy.md rename to exchange/exchange-ps/exchange/New-RetentionPolicy.md index c655fa14be..a6a970985e 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionPolicy.md +++ b/exchange/exchange-ps/exchange/New-RetentionPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-retentionpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-RetentionPolicy @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-RetentionPolicy cmdlet to create a retention policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,13 +28,14 @@ New-RetentionPolicy [-Name] [-IsDefaultArbitrationMailbox] [-RetentionId ] [-RetentionPolicyTagLinks ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Retention policy tags are associated with a retention policy. When a retention policy is applied to a mailbox, tags associated with the policy are available to the mailbox user. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,8 +76,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -112,15 +111,26 @@ Accept wildcard characters: False ``` ### -IsDefault -This parameter is reserved for internal Microsoft use. +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. + +When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. -To set the default retention policy for new mailboxes, use the RetentionPolicy parameter on the Set-MailboxPlan cmdlet. +**Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans: + +- $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes. +- A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). + +If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. + +Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -132,7 +142,7 @@ Accept wildcard characters: False ### -IsDefaultArbitrationMailbox 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. +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. ```yaml Type: SwitchParameter @@ -200,12 +210,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionPolicyTag.md b/exchange/exchange-ps/exchange/New-RetentionPolicyTag.md similarity index 92% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionPolicyTag.md rename to exchange/exchange-ps/exchange/New-RetentionPolicyTag.md index 6fc21664c6..a320464cfa 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionPolicyTag.md +++ b/exchange/exchange-ps/exchange/New-RetentionPolicyTag.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-retentionpolicytag +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-RetentionPolicyTag @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-RetentionPolicyTag cmdlet to create a retention tag. -For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). +For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ New-RetentionPolicyTag [-Name] [-AddressForJournaling ] [-AgeLimitForRetention ] [-Comment ] - [-Confirm] [-DomainController ] + [-Confirm] + [-DomainController ] [-IsDefaultAutoGroupPolicyTag] [-IsDefaultModeratedRecipientsPolicyTag] [-JournalingEnabled ] @@ -44,12 +44,14 @@ New-RetentionPolicyTag [-Name] [-RetentionId ] [-SystemTag ] [-Type ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UpgradeManagedFolder ``` -New-RetentionPolicyTag [-Name] [-ManagedFolderToUpgrade ] +New-RetentionPolicyTag [-Name] + [-ManagedFolderToUpgrade ] [-Comment ] [-Confirm] [-DomainController ] @@ -60,7 +62,8 @@ New-RetentionPolicyTag [-Name] [-ManagedFolderToUpgrade ] [-SystemTag ] [-Type ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -68,7 +71,7 @@ Retention tags are used to apply message retention settings to folders and items Retention tags support a display of the tag name and an optional comment in localized languages. Language culture codes from the CultureInfo class are used for this purpose. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -112,12 +115,12 @@ Accept wildcard characters: False ``` ### -AddressForJournaling -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. ```yaml -Type: Object +Type: RecipientIdParameter Parameter Sets: RetentionPolicy Aliases: Applicable: Exchange Server 2010 @@ -164,8 +167,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -200,13 +202,15 @@ Accept wildcard characters: False ``` ### -IsDefaultAutoGroupPolicyTag +This parameter is available only in the cloud-based service. + 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 +Applicable: Exchange Online Required: False Position: Named @@ -216,13 +220,15 @@ Accept wildcard characters: False ``` ### -IsDefaultModeratedRecipientsPolicyTag +This parameter is available only in the cloud-based service. + 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 +Applicable: Exchange Online Required: False Position: Named @@ -232,12 +238,12 @@ Accept wildcard characters: False ``` ### -JournalingEnabled -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. ```yaml -Type: Object +Type: Boolean Parameter Sets: RetentionPolicy Aliases: Applicable: Exchange Server 2010 @@ -250,7 +256,7 @@ Accept wildcard characters: False ``` ### -LabelForJournaling -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -340,7 +346,7 @@ Accept wildcard characters: False ``` ### -MessageFormatForJournaling -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -377,11 +383,8 @@ Accept wildcard characters: False 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. - - MarkAsPastRetentionLimit: Messages are marked as past the retention limit. - - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal and RecoverableItems. - - PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1). @@ -406,7 +409,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to 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. -When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as DISABLED\_\. +When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. ```yaml Type: Boolean @@ -457,45 +460,25 @@ Accept wildcard characters: False The Type parameter specifies the type of retention tag being created. Valid values include: - All - - Archive - - Calendar - - Clutter: Available in Exchange Online only. - - Contacts - - ConversationHistory - - DeletedItems - - Drafts - - Inbox - - Journal - - JunkEmail - - LegacyArchiveJournals - - ManagedCustomFolder - - Notes - - Outbox - - Personal - - RecoverableItems - - RssSubscriptions - - SentItems - - SyncIssues - - Tasks To create a default policy tag (DPT), specify type All. For tags of type RecoverableItems, the only valid retention action is MoveToArchive. @@ -534,12 +517,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/New-RoleAssignmentPolicy.md b/exchange/exchange-ps/exchange/New-RoleAssignmentPolicy.md similarity index 81% rename from exchange/exchange-ps/exchange/role-based-access-control/New-RoleAssignmentPolicy.md rename to exchange/exchange-ps/exchange/New-RoleAssignmentPolicy.md index b1a72368b2..37d991b855 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/New-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/exchange/New-RoleAssignmentPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/new-roleassignmentpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-RoleAssignmentPolicy @@ -17,30 +16,37 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-RoleAssignmentPolicy cmdlet to create management role assignment policies in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-RoleAssignmentPolicy [-Name] [-Confirm] [-Description ] [-DomainController ] - [-IsDefault] [-Roles ] [-WhatIf] +New-RoleAssignmentPolicy [-Name] + [-Confirm] + [-Description ] + [-DomainController ] + [-IsDefault] + [-Roles ] + [-WhatIf] [] ``` ## DESCRIPTION When you create an assignment policy, you can assign it to users using the New-Mailbox, Set-Mailbox, or Enable-Mailbox cmdlets. If you make the new assignment policy the default assignment policy, it's assigned to all new mailboxes that don't have an explicit assignment policy assigned to them. -You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it won't be able to manage their mailbox configuration. To assign a management role after the assignment policy has been created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://docs.microsoft.com/Exchange/permissions/role-assignment-policies). +You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it won't be able to manage their mailbox configuration. To assign a management role after the assignment policy has been created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://learn.microsoft.com/Exchange/permissions/role-assignment-policies). -For more information about assignment policies, see [Understanding management role assignment policies](https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). +For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -New-RoleAssignmentPolicy -Name "End User Policy"; Set-Mailbox -Identity Joe -RoleAssignmentPolicy "End User Policy" +New-RoleAssignmentPolicy -Name "End User Policy" + +Set-Mailbox -Identity Joe -RoleAssignmentPolicy "End User Policy" ``` This example creates an assignment policy. After the assignment policy is created, you can assign the assignment policy to a mailbox using the Set-Mailbox cmdlet. @@ -54,7 +60,9 @@ This example creates an assignment policy using the IsDefault switch. ### Example 3 ```powershell -New-RoleAssignmentPolicy -Name "Limited End User Policy" -Roles "MyPersonalInformation", "MyDistributionGroupMembership", "MyVoiceMail" -IsDefault; Get-Mailbox -ResultSize Unlimited | Set-Mailbox -RoleAssignmentPolicy "Limited End User Policy" +New-RoleAssignmentPolicy -Name "Limited End User Policy" -Roles "MyPersonalInformation", "MyDistributionGroupMembership", "MyVoiceMail" -IsDefault + +Get-Mailbox -ResultSize Unlimited | Set-Mailbox -RoleAssignmentPolicy "Limited End User Policy" ``` This example creates an assignment policy that enables users to modify their personal information, manage their distribution group membership, and manage their voice mail. The new assignment policy is created as the new default assignment policy. Then, all existing mailboxes are configured to use the new assignment policy. @@ -72,7 +80,7 @@ The Name parameter specifies the name of the new assignment policy. If the assig Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -84,15 +92,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -108,7 +115,7 @@ The Description parameter specifies the description that's displayed when the ro Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -128,7 +135,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -138,7 +145,7 @@ Accept wildcard characters: False ``` ### -IsDefault -The IsDefault switch makes the assignment policy the default assignment policy. You don't have to specify a value with this switch. +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. @@ -148,7 +155,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -160,13 +167,13 @@ Accept wildcard characters: False ### -Roles 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://docs.microsoft.com/exchange/built-in-management-roles-exchange-2013-help). +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). ```yaml Type: RoleIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -182,7 +189,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -196,12 +203,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/New-RoleGroup.md b/exchange/exchange-ps/exchange/New-RoleGroup.md similarity index 80% rename from exchange/exchange-ps/exchange/role-based-access-control/New-RoleGroup.md rename to exchange/exchange-ps/exchange/New-RoleGroup.md index bfbaf7b9b5..308719a319 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/New-RoleGroup.md +++ b/exchange/exchange-ps/exchange/New-RoleGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/new-rolegroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" --- # New-RoleGroup @@ -17,13 +16,14 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-RoleGroup cmdlet to create management role groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### CrossForest ``` -New-RoleGroup [-Name] -LinkedDomainController -LinkedForeignGroup [-LinkedCredential ] +New-RoleGroup [-Name] -LinkedDomainController -LinkedForeignGroup + [-LinkedCredential ] [-Confirm] [-CustomConfigWriteScope ] [-CustomRecipientWriteScope ] @@ -36,7 +36,9 @@ New-RoleGroup [-Name] -LinkedDomainController -LinkedForeignGr [-RecipientOrganizationalUnitScope ] [-Roles ] [-SamAccountName ] - [-WhatIf] [] + [-WellKnownObject ] + [-WhatIf] + [] ``` ### Default @@ -49,12 +51,14 @@ New-RoleGroup [-Name] [-DisplayName ] [-DomainController ] [-Force] + [-Id ] [-ManagedBy ] [-Members ] [-RecipientOrganizationalUnitScope ] [-Roles ] [-SamAccountName ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -62,9 +66,9 @@ You don't have to add members or assign management roles to the role group when When you create a role group, you can create the group and add members to it directly, or you can create a linked role group. A linked role group links the role group to a universal security group (USG) in another forest. Creating a linked role group is useful if your servers running Exchange reside in a resource forest and your users and administrators reside in a separate user forest. If you create a linked role group, you can't add members directly to it. You must add the members to the USG in the foreign forest. -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -91,7 +95,9 @@ This example creates a role group and enables Isabel to add or remove members to ### Example 4 ```powershell -$Credentials = Get-Credential; New-RoleGroup -Name "ContosoUsers: Toronto Recipient Admins" -LinkedDomainController dc02.contosousers.contoso.com -LinkedCredential $Credentials -LinkedForeignGroup "Toronto Administrators" -CustomRecipientWriteScope "Toronto Recipients" -Roles "Mail Recipients" +$Credentials = Get-Credential + +New-RoleGroup -Name "ContosoUsers: Toronto Recipient Admins" -LinkedDomainController dc02.contosousers.contoso.com -LinkedCredential $Credentials -LinkedForeignGroup "Toronto Administrators" -CustomRecipientWriteScope "Toronto Recipients" -Roles "Mail Recipients" ``` This example creates a linked role group that enables the members of the Toronto Administrators USG in the Contoso user forest to manage recipients located in the Toronto office. The custom recipient scope, Toronto Recipients, limits the scope of the roles assigned to the role group to recipients who have their City property set to Toronto. The Mail Recipients role is assigned to the role group. @@ -100,14 +106,16 @@ The first command retrieves the credentials using the Get-Credential cmdlet and ### Example 5 ```powershell -$RoleGroup = Get-RoleGroup "Recipient Management"; New-RoleGroup "Limited Recipient Management" -Roles $RoleGroup.Roles +$RoleGroup = Get-RoleGroup "Recipient Management" + +New-RoleGroup "Limited Recipient Management" -Roles $RoleGroup.Roles ``` This example takes an existing role group and copies the roles from that role group into a new custom role group. This can be useful if you want to create a role group similar to an existing role group but don't want to manually create all the role assignments. For example, you might want to create a role group that has most, but not all, of the management roles assigned to the Recipient Management role group. The first command stores the existing role group in a variable, and the second command creates the custom role group. -This example uses variables to store information. For more information about variables, see [About Variables](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_variables). +This example uses variables to store information. For more information about variables, see [About Variables](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_variables). ### Example 6 ```powershell @@ -118,6 +126,24 @@ This example removes the role assignment between the Distribution Groups managem ## PARAMETERS +### -Name +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. + +```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: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -LinkedDomainController This parameter is available only in on-premises Exchange. @@ -158,36 +184,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -225,7 +232,7 @@ 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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -241,7 +248,7 @@ The Description parameter specifies the description that's displayed when the ro Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -251,13 +258,13 @@ Accept wildcard characters: False ``` ### -DisplayName -The DisplayName parameter specifies the friendly name of the role group. If the name contains spaces, enclose the name in quotation marks ("). This parameter can have a maximum length of 256 characters. +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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -285,13 +292,35 @@ Accept wildcard characters: False ``` ### -Force -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. +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Id +This parameter is available only in Security & Compliance PowerShell. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance Required: False Position: Named @@ -305,7 +334,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -331,7 +360,7 @@ 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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -349,7 +378,7 @@ 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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -379,13 +408,13 @@ Accept wildcard characters: False ### -Roles 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://docs.microsoft.com/exchange/built-in-management-roles-exchange-2013-help). +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). ```yaml Type: RoleIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -397,7 +426,7 @@ Accept wildcard characters: False ### -SamAccountName 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 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. +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 @@ -412,8 +441,26 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WellKnownObject +This parameter is available only in the cloud-based service. + +{{ Fill WellKnownObject Description }} + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. +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. @@ -421,7 +468,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -435,12 +482,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-RoutingGroupConnector.md b/exchange/exchange-ps/exchange/New-RoutingGroupConnector.md similarity index 92% rename from exchange/exchange-ps/exchange/mail-flow/New-RoutingGroupConnector.md rename to exchange/exchange-ps/exchange/New-RoutingGroupConnector.md index 02b9424cca..4fd4b16fbf 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-RoutingGroupConnector.md +++ b/exchange/exchange-ps/exchange/New-RoutingGroupConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-routinggroupconnector +online version: https://learn.microsoft.com/powershell/module/exchange/new-routinggroupconnector applicable: Exchange Server 2010 title: New-RoutingGroupConnector schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-RoutingGroupConnector @@ -17,14 +16,19 @@ This cmdlet is available only in Exchange Server 2010. Use the New-RoutingGroupConnector cmdlet to establish a connection between a Microsoft Exchange Server 2010 routing group and an Exchange Server 2003 routing group when the organization is running more than one version of Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-RoutingGroupConnector [-Name] -SourceTransportServers - -TargetTransportServers [-BiDirectional ] [-Confirm] [-Cost ] - [-DomainController ] [-PublicFolderReferralsEnabled ] [-WhatIf] [] +New-RoutingGroupConnector [-Name] -SourceTransportServers -TargetTransportServers + [-BiDirectional ] + [-Confirm] + [-Cost ] + [-DomainController ] + [-PublicFolderReferralsEnabled ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -32,7 +36,7 @@ The New-RoutingGroupConnector cmdlet creates a new routing group connector betwe To create the routing group connector, you must specify the source servers from the originating routing group and the target servers in the destination routing group. The routing group connector is created in the routing group of which the source server is a member. By using the Bidirectional parameter, you can specify whether the connector is used for one-way or two-way mail flow. If you specify a two-way connector, a reciprocal connector is created in the target routing group. The source and target servers must be Exchange 2010 Hub Transport servers or Exchange 2003 bridgehead servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,11 +48,8 @@ New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Hub2010.c This example creates the routing group connector Interop RGC with the following properties: - The Exchange 2010 server is Hub2010.contoso.com. - - The Exchange 2003 bridgehead server is Bridgehead2003.contoso.com. - - The routing group connector is a two-way connector between the Exchange 2010 routing group and the routing group associated with the specified Exchange 2003 server. - - The cost is 100. ## PARAMETERS @@ -120,8 +121,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -206,12 +206,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-RpcClientAccess.md b/exchange/exchange-ps/exchange/New-RpcClientAccess.md similarity index 91% rename from exchange/exchange-ps/exchange/client-access-servers/New-RpcClientAccess.md rename to exchange/exchange-ps/exchange/New-RpcClientAccess.md index a0ffc2c662..183a022952 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-RpcClientAccess.md +++ b/exchange/exchange-ps/exchange/New-RpcClientAccess.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-rpcclientaccess +online version: https://learn.microsoft.com/powershell/module/exchange/new-rpcclientaccess applicable: Exchange Server 2010 title: New-RpcClientAccess schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # New-RpcClientAccess @@ -15,9 +14,9 @@ monikerRange: "exchserver-ps-2010" ## SYNOPSIS This cmdlet is available only in Exchange Server 2010. -Use the New-RpcClientAccess cmdlet to create configuration information for the Exchange RPC Client Access service on a Client Access server. This setup task is performed by default on new installations of the Client Access server role on Microsoft Exchange Server 2010. +Use the New-RpcClientAccess cmdlet to create configuration information for the Exchange RPC Client Access service on a Client Access server. This set up task is performed by default on new installations of the Client Access server role on Microsoft Exchange Server 2010. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,13 +27,14 @@ New-RpcClientAccess -Server [-DomainController ] [-EncryptionRequired ] [-MaximumConnections ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION After you run this command, you must start the Exchange RPC Client Access service on the Exchange Client Access server to enable RPC client access. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,11 +51,8 @@ This example creates configuration information for the Exchange RPC Client Acces 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -92,8 +89,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -182,12 +178,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/New-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/New-SafeAttachmentPolicy.md new file mode 100644 index 0000000000..7bd53126c9 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-SafeAttachmentPolicy.md @@ -0,0 +1,281 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-SafeAttachmentPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-SafeAttachmentPolicy cmdlet to create safe attachment policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-SafeAttachmentPolicy [-Name] + [-Action ] + [-AdminDisplayName ] + [-Confirm] + [-Enable ] + [-MakeBuiltInProtection] + [-QuarantineTag ] + [-RecommendedPolicyType ] + [-Redirect ] + [-RedirectAddress ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +New safe attachment policies that you create using this cmdlet aren't applied to users and aren't visible in the Microsoft Defender portal. You need to use the SafeAttachmentPolicy parameter on the New-SafeAttachmentRule or Set-SafeAttachmentRule cmdlets to associate the policy with a rule to create a complete Safe Attachments policy that's visible in the Defender portal. + +A safe attachment policy can be assigned to only one safe attachment rule. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-SafeAttachmentPolicy -Name "Marketing Block Attachments" -Enable $true -Redirect $true -RedirectAddress admin@contoso.com +``` + +This example creates a new safe attachment policy named Marketing Block Attachments with the following options: + +- The action is Block. This is the default value of the Action parameter, so you don't need to specify it. +- The value $true for the Enable parameter is required so the policy will actually use the default Action parameter value of Block (or any other Action parameter value). +- Enable redirection for detected malware attachments and send the messages to admin@contoso.com. +- If Safe Attachments scanning isn't available or encounters errors, don't deliver the message as normal. The default value of the ActionOnError parameter is $true, so you don't need to specify it. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Action +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. +- Block: Block the email message that contains the malware attachment. This is the default value. +- DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies). + +The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false). + +To specify no action for the safe attachment policy (corresponds to the value **Off** for the **Safe Attachments unknown malware response** policy setting in the Defender portal), use the value $false for the Enable parameter. + +The results of all actions are available in message trace. + +```yaml +Type: SafeAttachmentAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enable +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. +- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. This value corresponds to the **Off** selection for the **Safe Attachments unknown malware response** setting of the policy in the Microsoft Defender portal. + +To enable or disable a complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell), use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeBuiltInProtection +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the built-in quarantine policy named AdminOnlyAccessPolicy is used. This quarantine policy enforces the historical capabilities for messages that were quarantined as malware by Safe Attachments as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecommendedPolicyType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Redirect +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. +- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RedirectAddress +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. + +```yaml +Type: SmtpAddress +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/New-SafeAttachmentRule.md new file mode 100644 index 0000000000..373513e1c0 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-SafeAttachmentRule.md @@ -0,0 +1,347 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-SafeAttachmentRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-SafeAttachmentRule cmdlet to create safe attachment rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-SafeAttachmentRule [-Name] -SafeAttachmentPolicy + [-Comments ] + [-Confirm] + [-Enabled ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Priority ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to specify at least one condition for the rule. + +A safe attachment policy can be assigned only to one safe attachment rule. + +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-policy-settings). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-SafeAttachmentRule -Name "Research Department Attachment Rule" -SafeAttachmentPolicy "Research Block Attachments" -SentToMemberOf "Research Department" -ExceptIfSentToMemberOf "Research Department Managers" +``` + +This example creates a new safe attachment rule named Research Department Attachment Rule with the following conditions: + +- The rule is associated with the safe attachment policy named Research Block Attachments. +- The rule applies to members of the group named Research Department. +- The rule doesn't apply to members of the group named Research Department Managers. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SafeAttachmentPolicy +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: + +- Name +- Distinguished name (DN) +- GUID + +You can't specify a safe attachment policy that's already associated with another safe attachment rule. + +```yaml +Type: SafeAttachmentPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the rule is enabled. Valid values are: + +- $true: The rule is enabled. This is the default value. +- $false: The rule is disabled. + +In the properties of the rule, the value of this parameter is visible in the State property. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/New-SafeLinksPolicy.md new file mode 100644 index 0000000000..07d98d9dab --- /dev/null +++ b/exchange/exchange-ps/exchange/New-SafeLinksPolicy.md @@ -0,0 +1,429 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-SafeLinksPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-SafeLinksPolicy cmdlet to create Safe Links policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-SafeLinksPolicy [-Name] + [-AdminDisplayName ] + [-AllowClickThrough ] + [-Confirm] + [-CustomNotificationText ] + [-DeliverMessageAfterScan ] + [-DisableUrlRewrite ] + [-DoNotRewriteUrls ] + [-EnableForInternalSenders ] + [-EnableOrganizationBranding ] + [-EnableSafeLinksForEmail ] + [-EnableSafeLinksForOffice ] + [-EnableSafeLinksForTeams ] + [-MakeBuiltInProtection] + [-RecommendedPolicyType ] + [-ScanUrls ] + [-TrackClicks ] + [-UseTranslatedNotificationText ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links to see if they lead to malicious web sites. When a user clicks a link, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the SafeLinksPolicy parameter on the New-SafeLinksRule or Set-SafeLinksRule cmdlets to associate the policy with a rule. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-SafeLinksPolicy -Name "Marketing Block URL" -EnableSafeLinksForEmail $true -AllowClickThrough $false +``` + +This example creates a new Safe Links policy named Marketing Block URL with the following options: + +- The policy is enabled. +- Users aren't allowed to click through to the original URL. +- User clicks on URLs are tracked. This is the default value of the TrackClicks parameter, so you don't need to specify it. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowClickThrough +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. +- $false: The user isn't allowed to click through to the original URL. + +In PowerShell, the default value is $false. In new Safe Links policies created in the Microsoft Defender portal, the default value is $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomNotificationText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeliverMessageAfterScan +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. +- $false: If Safe Links scanning can't complete, deliver the message anyway. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableUrlRewrite +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). +- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. This is the default value. + +In PowerShell, the default value is $false. In new Safe Links policies created in the Microsoft Defender portal, the default value is $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DoNotRewriteUrls +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +For details about the entry syntax, see [Entry syntax for the "Do not rewrite the following URLs" list](https://learn.microsoft.com/defender-office-365/safe-links-about#entry-syntax-for-the-do-not-rewrite-the-following-urls-list). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableForInternalSenders +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. +- $false: The policy is applied only to external senders. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOrganizationBranding +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. +- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSafeLinksForEmail +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. +- $false: Safe Links isn't enabled for email. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSafeLinksForOffice +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. +- $false: Safe Links isn't enabled for Office apps. + +Note that this protection applies to links in Office documents, not links in email messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSafeLinksForTeams +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. +- $false: Safe Links isn't enabled for Teams. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeBuiltInProtection +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecommendedPolicyType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScanUrls +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. +- $false: Real-time scanning of clicked links, including links that point to files, is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrackClicks +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. +- $false: User clicks messages aren't tracked. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseTranslatedNotificationText +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. +- $false: Don't translate custom notification text to the user's language. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-SafeLinksRule.md b/exchange/exchange-ps/exchange/New-SafeLinksRule.md new file mode 100644 index 0000000000..33a08f67c7 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-SafeLinksRule.md @@ -0,0 +1,370 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-SafeLinksRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-SafeLinksRule cmdlet to create Safe Links rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-SafeLinksRule [-Name] -SafeLinksPolicy + [-Comments ] + [-Confirm] + [-Enabled ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Priority ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to specify at least one condition for the rule. + +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-SafeLinksRule -Name "Research Department URL Rule" -SafeLinksPolicy "Research Block URL" -SentToMemberOf "Research Department" -ExceptIfSentToMemberOf "Research Department Managers" +``` + +This example creates a new Safe Links rule named Research Department URL Rule with the following conditions: + +- The rule is associated with the Safe Links policy named Research Block URL. +- The rule applies to members of the group named Research Department. +- Because we aren't using the Priority parameter, the default priority is used. +- The rule doesn't apply to members of the group named Research Department Managers. +- The rule is enabled (we aren't using the Enabled parameter, and the default value is `$true`). + +### Example 2 +```powershell +New-SafeLinksRule -Name "Contoso All" -SafeLinksPolicy "Contoso All" -RecipientDomainIs (Get-AcceptedDomain).Name +``` + +This example creates a Safe Links rule named Contoso All with the following conditions: + +- The rule is associated with the Safe Links policy named Contoso All. +- The rule applies to recipients in all accepted domains in the organization. +- Because we aren't using the Priority parameter, the default priority is used. +- The rule is enabled (we aren't using the Enabled parameter, and the default value is `$true`). + +### Example 3 +```powershell +$Data = Import-Csv -Path "C:\Data\SafeLinksDomains.csv" + +$SLDomains = $Data.Domains + +New-SafeLinksRule -Name "Contoso All" -SafeLinksPolicy "Contoso All" -RecipientDomainIs $SLDomains +``` + +This example is similar to Example 2, but in this example, the rule applies to recipients in the domains specified in a .csv file. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SafeLinksPolicy +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: + +- Name +- Distinguished name (DN) +- GUID + +You can't specify a Safe Links policy that's already associated with another Safe Links rule. + +```yaml +Type: SafeLinksPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the rule is enabled. Valid values are: + +- $true: The rule is enabled. This is the default value. +- $false: The rule is disabled. + +In the properties of the rule, the value of this parameter is visible in the State property. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-SearchDocumentFormat.md b/exchange/exchange-ps/exchange/New-SearchDocumentFormat.md similarity index 91% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-SearchDocumentFormat.md rename to exchange/exchange-ps/exchange/New-SearchDocumentFormat.md index 60b9a8181b..2f54d72235 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-SearchDocumentFormat.md +++ b/exchange/exchange-ps/exchange/New-SearchDocumentFormat.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/new-searchdocumentformat +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-SearchDocumentFormat @@ -17,20 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the New-SearchDocumentFormat cmdlet to add a format-specific filter to those used by Exchange search. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-SearchDocumentFormat [-Identity] -Extension -MimeType - -Name [-Confirm] [-Enabled ] [-Server ] [-WhatIf] +New-SearchDocumentFormat [-Identity] -Extension -MimeType -Name + [-Confirm] + [-Enabled ] + [-Server ] + [-WhatIf] [] ``` ## DESCRIPTION After running the New-SearchDocumentFormat cmdlet, your must run the following cmdlet to restart the search service. There will be a brief search outage. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,35 +45,35 @@ This example creates a new search document format with an extension of .sct and ## PARAMETERS -### -Extension -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. +### -Identity +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: String +Type: SearchDocumentFormatId Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. +### -Extension +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: SearchDocumentFormatId +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -110,8 +112,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -149,11 +150,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -192,12 +190,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-SecOpsOverridePolicy.md b/exchange/exchange-ps/exchange/New-SecOpsOverridePolicy.md new file mode 100644 index 0000000000..e24f5206c9 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-SecOpsOverridePolicy.md @@ -0,0 +1,195 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-SecOpsOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-SecOpsOverridePolicy cmdlet to create SecOps mailbox override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-SecOpsOverridePolicy [-Name] -SentTo + [-Comment ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-SecOpsOverridePolicy -Name SecOpsOverridePolicy -SentTo secops@contoso.com +``` + +This example creates the SecOps mailbox override policy with the specified settings. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +The SentTo parameter specifies the email address of the SecOps mailbox. Groups are not allowed. + +You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/New-SendConnector.md b/exchange/exchange-ps/exchange/New-SendConnector.md similarity index 86% rename from exchange/exchange-ps/exchange/mail-flow/New-SendConnector.md rename to exchange/exchange-ps/exchange/New-SendConnector.md index 6bb4d26054..bb0b4fa218 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-SendConnector.md +++ b/exchange/exchange-ps/exchange/New-SendConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-sendconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-SendConnector @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-SendConnector cmdlet to create a new Send connector. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -61,12 +60,14 @@ New-SendConnector -Name -AddressSpaces [-TlsDomain ] [-Usage ] [-UseExternalDNSServersEnabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### LinkedReceiveConnector ``` -New-SendConnector [-Name] [-LinkedReceiveConnector ] +New-SendConnector [-Name] + [-LinkedReceiveConnector ] [-AuthenticationCredential ] [-Comment ] [-Confirm] @@ -99,11 +100,12 @@ New-SendConnector [-Name] [-LinkedReceiveConnector ] [-Usage ] [-UseExternalDNSServersEnabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -115,20 +117,19 @@ New-SendConnector -Internet -Name MySendConnector -AddressSpaces contoso.com,fab This example creates the Send connector named MySendConnector with the following properties: - It sends email messages over the Internet. - - It processes messages addressed only to Contoso.com and Fabrikam.com domains. ### Example 2 ```powershell -$CredentialObject = Get-Credential; New-SendConnector -Name "Secure Email to Contoso.com" -AddressSpaces contoso.com -AuthenticationCredential $CredentialObject -SmartHostAuthMechanism BasicAuth +$CredentialObject = Get-Credential + +New-SendConnector -Name "Secure Email to Contoso.com" -AddressSpaces contoso.com -AuthenticationCredential $CredentialObject -SmartHostAuthMechanism BasicAuth ``` This example creates the Send connector Secure Email to Contoso.com with the following properties: - It processes messages only for the Contoso.com domain. - - It uses Basic authentication. - - It uses a specific authentication credential. To assign a specific authentication credential for the Send connector, you must first run the Get-Credential command and store the user input in a temporary variable. When you run the Get-Credential command, the command asks for the username and password of the account used during authentication with the Contoso.com email server. The temporary variable can then be used in the New-SendConnector cmdlet to create the new connector. @@ -152,22 +153,17 @@ Accept wildcard characters: False ``` ### -AddressSpaces -The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is as follows: \:\;\ +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. - - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com is not. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address space type, you can enter any text for the address space. - - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. This parameter is optional. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("). For example, the following address space entries are equivalent: - "SMTP:contoso.com;1" - - "contoso.com;1" - - "SMTP:contoso.com" - - contoso.com You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3". @@ -175,10 +171,9 @@ You may specify multiple address spaces by separating the address spaces with co If you specify a non-SMTP address space type on a Send connector configured in the Transport service on a Mailbox server, you must configure the following parameters: - The SmartHosts parameter must be set to a value that specifies a smart host. - - The DNSRoutingEnabled parameter must be set to $false. -Although you can configure non-SMTP address spaces on a Send connector in the Transport service on a Mailbox server, the Send connector uses SMTP as the transport mechanism to send messages to other messaging servers. Foreign connectors in the Transport service on a Mailbox server are used to send messages to local messaging servers, such as third-party fax gateway servers, which don't use SMTP as their primary transport mechanism. For more information, see [Foreign connectors](https://docs.microsoft.com/exchange/foreign-connectors-exchange-2013-help). +Although you can configure non-SMTP address spaces on a Send connector in the Transport service on a Mailbox server, the Send connector uses SMTP as the transport mechanism to send messages to other messaging servers. Foreign connectors in the Transport service on a Mailbox server are used to send messages to local messaging servers, such as third-party fax gateway servers, which don't use SMTP as their primary transport mechanism. For more information, see [Foreign connectors](https://learn.microsoft.com/exchange/foreign-connectors-exchange-2013-help). ```yaml Type: MultiValuedProperty @@ -196,7 +191,7 @@ Accept wildcard characters: False ### -AuthenticationCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -212,14 +207,13 @@ Accept wildcard characters: False ``` ### -CloudServicesMailEnabled -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://docs.microsoft.com/exchange/hybrid-configuration-wizard). +**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 Office 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. +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. Valid values are: - $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -254,8 +248,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -292,11 +285,10 @@ Accept wildcard characters: False ``` ### -ConnectorType -The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Office 365. Valid values are: - -- Default: The connector isn't used to send messages to Office 365. This is the default value. +The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are: -- XPremises: The connector is used to send messages to Office 365. +- Default: The connector isn't used to send messages to Microsoft 365. This is the default value. +- XPremises: The connector is used to send messages to Microsoft 365. ```yaml Type: TenantConnectorType @@ -312,17 +304,16 @@ Accept wildcard characters: False ``` ### -Custom -The Custom parameter specifies the Custom usage type. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Custom parameter, you can't use any of the following parameters: +The Custom switch specifies the Custom usage type. You don't need to specify a value with this switch. -- Internal +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: +- Internal - Internet - - Partner - - Usage -For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://docs.microsoft.com/Exchange/mail-flow/connectors/send-connectors). +For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/send-connectors). ```yaml Type: SwitchParameter @@ -375,9 +366,7 @@ Accept wildcard characters: False 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. - - DNSRoutingEnabled is set to $true. - - IgnoreSTARTTLS is set to $false. The wildcard character (\*) isn't supported in domains configured for mutual TLS authentication. The same domain must also be defined on the corresponding Receive connector, and in the value of the TLSReceiveDomainSecureList attribute of the transport configuration. @@ -385,7 +374,6 @@ The wildcard character (\*) isn't supported in domains configured for mutual TLS The default value for the DomainSecureEnabled parameter is $false for the following types of Send connectors: - Those defined in the Transport service on a Mailbox server. - - User-created Send connectors defined on an Edge server. The default value is $true for a default Send connector defined on an Edge server. @@ -423,11 +411,8 @@ Accept wildcard characters: False 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. - - DowngradeDnsFailures: All DNS errors are treated as transient. - - DowngradeCustomFailures: Particular SMTP errors are treated as transient. - - UpgradeCustomFailures Custom transient failures are upgraded and treated as permanent failures. Multiple values can be specified for this parameter, separated by commas. @@ -448,7 +433,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -483,9 +470,7 @@ Accept wildcard characters: False 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 - - In the most recent Received header field added to the message by the next hop messaging server after the message leaves the Transport service on a Mailbox server or an Edge server - - During TLS authentication The default value of the Fqdn parameter is $null. This means the default FQDN value is the FQDN of the Mailbox server or Edge server that contains the Send connector. @@ -536,17 +521,16 @@ Accept wildcard characters: False ``` ### -Internal -The Internal parameter specifies the Internal usage type. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Internal parameter, you can't use any of the following parameters: +The Internal switch specifies the Internal usage type. You don't need to specify a value with this switch. -- Custom +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: +- Custom - Internet - - Partner - - Usage -For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://docs.microsoft.com/Exchange/mail-flow/connectors/send-connectors). +For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/send-connectors). ```yaml Type: SwitchParameter @@ -562,17 +546,16 @@ Accept wildcard characters: False ``` ### -Internet -The Internet parameter specifies the Internet usage type. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Internet parameter, you can't use any of the following parameters: +The Internet switch specifies the Internet usage type. You don't need to specify a value with this switch. -- Custom +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: +- Custom - Internal - - Partner - - Usage -For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://docs.microsoft.com/Exchange/mail-flow/connectors/send-connectors). +For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/send-connectors). ```yaml Type: SwitchParameter @@ -588,9 +571,9 @@ Accept wildcard characters: False ``` ### -IsCoexistenceConnector -This parameter is available or functional only in 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 Office 365 organization. The default value is $false. +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. ```yaml Type: Boolean @@ -622,25 +605,20 @@ Accept wildcard characters: False ``` ### -LinkedReceiveConnector -This parameter is available or functional only in 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: - GUID - - Distinguished name (DN) - -- Servername\\ConnectorName +- ServerName\\ConnectorName When you use the LinkReceiveConnector parameter with this command, you must also use the following parameters with the specified values: -- DNSRoutingEnabled $false - -- MaxMessageSize unlimited - -- Smarthosts \ - -- SmarthostAuthMechanism \ +- `DNSRoutingEnabled $false` +- `MaxMessageSize unlimited` +- `Smarthosts ` +- `SmarthostAuthMechanism ` When you use the LinkedReceiveConnector parameter, you can't use the AddressSpaces parameter. @@ -663,13 +641,9 @@ The MaxMessageSize parameter specifies the maximum size of a message that can pa When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -690,17 +664,16 @@ Accept wildcard characters: False ``` ### -Partner -The Partner parameter specifies the Partner usage type. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Partner parameter, you can't use any of the following parameters: +The Partner switch specifies the Partner usage type. You don't need to specify a value with this switch. -- Custom +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: +- Custom - Internal - - Internet - - Usage -For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://docs.microsoft.com/Exchange/mail-flow/connectors/send-connectors). +For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/send-connectors). ```yaml Type: SwitchParameter @@ -798,7 +771,7 @@ Accept wildcard characters: False ### -SmartHosts 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, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: MultiValuedProperty @@ -848,7 +821,7 @@ Accept wildcard characters: False ### -SourceTransportServers 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, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: MultiValuedProperty @@ -867,9 +840,7 @@ Accept wildcard characters: False 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. - - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - - DomainValidation: In addition to channel encryption and certificate validation, the Send connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. If no domain is specified in the TlsDomain parameter, the FQDN on the certificate is compared with the recipient's domain. You can't specify a value for this parameter if the IgnoreSTARTTLS parameter is set to $true, or if the RequireTLS parameter is set to $false. @@ -888,7 +859,7 @@ Accept wildcard characters: False ``` ### -TlsCertificateName -The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\X.500Issuer\X.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. +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 @@ -911,7 +882,6 @@ This parameter is used only if the TlsAuthLevel parameter is set to DomainValida A value for this parameter is required if: - The TLSAuthLevel parameter is set to DomainValidation. - - The DNSRoutingEnabled parameter is set to $false (smart host Send connector). ```yaml @@ -933,14 +903,11 @@ The Usage parameter specifies the default permissions and authentication methods If you use the Usage parameter, you can't use any of the following parameters: - Custom - - Internal - - Internet - - Partner -For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://docs.microsoft.com/Exchange/mail-flow/connectors/send-connectors). +For more information about Send connector usage types, permissions, and authentication methods, see [Send connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/send-connectors). ```yaml Type: UsageType @@ -992,12 +959,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-ServicePrincipal.md b/exchange/exchange-ps/exchange/New-ServicePrincipal.md new file mode 100644 index 0000000000..6e59edbe3e --- /dev/null +++ b/exchange/exchange-ps/exchange/New-ServicePrincipal.md @@ -0,0 +1,185 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-ServicePrincipal + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-ServicePrincipal cmdlet to create service principals in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ServicePrincipal -AppId -ObjectId + -ServiceId + [-Confirm] + [-DisplayName ] + [-Organization ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Service principals exist in Microsoft Entra ID to define what apps can do, who can access the apps, and what resources the apps can access. In Exchange Online, service principals are references to the service principals in Microsoft Entra ID. To assign Exchange Online role-based access control (RBAC) roles to service principals in Microsoft Entra ID, you use the service principal references in Exchange Online. The **\*-ServicePrincipal** cmdlets in Exchange Online PowerShell let you view, create, and remove these service principal references. + +For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ServicePrincipal -AppId 71487acd-ec93-476d-bd0e-6c8b31831053 -ObjectId 6233fba6-0198-4277-892f-9275bf728bcc +``` + +This example create a new service principal in Exchange Online with the specified AppId and ObjectId values. + +## PARAMETERS + +### -AppId +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: + +- The AppId property in the output of the [Get-MgServicePrincipal](https://learn.microsoft.com/powershell/module/microsoft.graph.applications/get-mgserviceprincipal) cmdlet in Microsoft Graph PowerShell. +- The Application ID property from Enterprise applications in the Microsoft Entra admin center: . + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ObjectId +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: + +- The Id property in the output of the [Get-MgServicePrincipal](https://learn.microsoft.com/powershell/module/microsoft.graph.applications/get-mgserviceprincipal) cmdlet in Microsoft Graph PowerShell. +- The Object ID property from Enterprise applications in the Microsoft Entra admin center: . + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/New-SettingOverride.md b/exchange/exchange-ps/exchange/New-SettingOverride.md similarity index 89% rename from exchange/exchange-ps/exchange/organization/New-SettingOverride.md rename to exchange/exchange-ps/exchange/New-SettingOverride.md index 1ae3cda4ba..6ffa158c1c 100644 --- a/exchange/exchange-ps/exchange/organization/New-SettingOverride.md +++ b/exchange/exchange-ps/exchange/New-SettingOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/new-settingoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-SettingOverride @@ -19,26 +18,26 @@ This cmdlet is available only in on-premises Exchange. Use the New-SettingOverride cmdlet to create setting overrides that store Exchange customizations in Active Directory instead of in text files on the server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-SettingOverride [-Name] -Component -Parameters -Reason - -Section +New-SettingOverride [-Name] -Component -Parameters -Reason -Section [-Confirm] [-DomainController ] [-Force] [-MaxVersion ] [-MinVersion ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and are lost when you install the next Exchange CU. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,16 +57,12 @@ New-SettingOverride -Name "Change OAB Generation" -Server Mailbox01 -Component T This example creates a new setting override named Change OAB Generation. This override specifies a 2 hour OAB generation interval. Because the Server parameter is used, the override applies only to the specified server named Mailbox01. -For more information, see the topic [Change the offline address book generation schedule in Exchange](https://docs.microsoft.com/Exchange/plan-and-deploy/post-installation-tasks/change-oab-generation-schedule). +For more information, see the topic [Change the offline address book generation schedule in Exchange](https://learn.microsoft.com/Exchange/plan-and-deploy/post-installation-tasks/change-oab-generation-schedule). ## PARAMETERS -### -Component -The Component parameter specifies the component that the setting override is applied to. For example: - -- TimeBasedAssistants - -- OwaServer +### -Name +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 @@ -76,14 +71,17 @@ Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies the unique name of the setting override. If the value contains spaces, enclose the value in quotation marks ("). +### -Component +The Component parameter specifies the component that the setting override is applied to. For example: + +- TimeBasedAssistants +- OwaServer ```yaml Type: String @@ -92,18 +90,17 @@ Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Parameters -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 @("\=\","\=\"...). For example: - -- @("Enabled=true") +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: -- @("IMServerName=\","IMCertificateThumbprint=\") +- `@("Enabled=true")` +- `@("IMServerName=","IMCertificateThumbprint=")` ```yaml Type: MultiValuedProperty @@ -153,8 +150,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -187,7 +183,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -281,12 +279,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-SharingPolicy.md b/exchange/exchange-ps/exchange/New-SharingPolicy.md similarity index 76% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/New-SharingPolicy.md rename to exchange/exchange-ps/exchange/New-SharingPolicy.md index 6114c0640b..c955830dfd 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-SharingPolicy.md +++ b/exchange/exchange-ps/exchange/New-SharingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-sharingpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-SharingPolicy @@ -17,18 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-SharingPolicy cmdlet to create a sharing policy to regulate how users inside your organization can share calendar and contact information with users outside the organization. Users can only share this information after federation has been configured in Exchange. After federation is configured, users can send sharing invitations that comply with a sharing policy to external recipients in other Exchange Server 2010 or later organizations that have federation enabled. A sharing policy needs to get assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the level of sharing permitted for this mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Sharing policies provide user-established, people-to-people sharing of both calendar and contact information with different types of external users. Sharing policies allow users to share both their free/busy and contact information (including the Calendar and Contacts folders) with recipients in other external federated Exchange organizations. For recipients that aren't in an external federated organization or are in non-Exchange organizations, sharing policies allow people-to-people sharing of their calendar information with anonymous users through the use of Internet Calendar Publishing. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-SharingPolicy [-Name] -Domains [-Confirm] [-Default] - [-DomainController ] [-Enabled ] [-WhatIf] +New-SharingPolicy [-Name] -Domains + [-Confirm] + [-Default] + [-DomainController ] + [-Enabled ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,47 +53,48 @@ This example creates a default sharing policy, which is applied to all mailboxes ## PARAMETERS -### -Domains -The Domains parameter specifies the domains to which this sharing policy applies and the sharing policy actions. Values for this parameter take the format: 'Domain: SharingPolicyAction'. - -The following sharing policy action values can be used: - -- CalendarSharingFreeBusySimple: Share free/busy hours only - -- CalendarSharingFreeBusyDetail: Share free/busy hours, subject and location - -- CalendarSharingFreeBusyReviewer: Share free/busy hours, subject, location and the body of the message or calendar item - -- ContactsSharing: Share contacts only - -Separate multiple domains with a comma, for example, 'mail.contoso.com: CalendarSharingFreeBusySimple', 'mail.fabrikam.com: CalendarSharingFreeBusyDetail, ContactsSharing'. - -A domain doesn't include subdomains. You must configure each subdomain separately. +### -Name +The Name parameter specifies the name of the new sharing policy. ```yaml -Type: MultiValuedProperty +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 +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -The Name parameter specifies the name of the new sharing policy. +### -Domains +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`: + +- A domain: For example, `mail.contoso.com`. A domain doesn't include subdomains. You must configure each subdomain separately. +- \*: Share with external federated organizations. For example, another Microsoft 365 organization or an on-premises Exchange organization. +- Anonymous: Share with external, non-federated organizations and individuals with internet access. + +You can use the following values for `SharingPolicyAction`: + +- CalendarSharingFreeBusySimple: Share free/busy hours only +- CalendarSharingFreeBusyDetail: Share free/busy hours, subject and location +- CalendarSharingFreeBusyReviewer: Share free/busy hours, subject, location and the body of the message or calendar item +- ContactsSharing: Share contacts only + +You can specify multiple `'Domain: SharingPolicyAction'` values separated by commas, and you can specify multiple `SharingPolicyAction` values for the same domain separated by commas. For example, `'mail.contoso.com: CalendarSharingFreeBusySimple', 'mail.fabrikam.com: CalendarSharingFreeBusyDetail, ContactsSharing'`. ```yaml -Type: String +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -97,8 +103,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,9 +120,9 @@ Accept wildcard characters: False ``` ### -Default -The Default switch specifies that this sharing policy is the default sharing policy for all mailboxes. 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. +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. -You don't have 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. ```yaml Type: SwitchParameter @@ -189,12 +194,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/New-SiteMailbox.md b/exchange/exchange-ps/exchange/New-SiteMailbox.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/New-SiteMailbox.md rename to exchange/exchange-ps/exchange/New-SiteMailbox.md index 05f98c15e8..21fd001892 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-SiteMailbox.md +++ b/exchange/exchange-ps/exchange/New-SiteMailbox.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-sitemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-SiteMailbox ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. -The New-SiteMailbox cmdlet is used by the Microsoft SharePoint and Microsoft Exchange user interfaces to create site mailboxes. We recommend that you don't use this cmdlet in the Exchange Management Shell; instead use SharePoint to create the site mailbox. This cmdlet should only be used for diagnostic and troubleshooting purposes. +The New-SiteMailbox cmdlet is used by the Microsoft SharePoint and Microsoft Exchange user interfaces to create site mailboxes. We recommend that you don't use this cmdlet; instead use SharePoint to create the site mailbox. This cmdlet should only be used for diagnostic and troubleshooting purposes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,11 +32,12 @@ New-SiteMailbox [[-DisplayName] ] -SharePointUrl [-Name ] [-OrganizationalUnit ] [-OverrideRecipientQuotas] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,6 +50,22 @@ You can't run this cmdlet from the Exchange Management Shell. Use SharePoint to ## PARAMETERS +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -SharePointUrl The SharePointUrl parameter specifies the SharePoint URL where the site mailbox is hosted, for example, "https://myserver/teams/edu". @@ -83,8 +101,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -104,9 +121,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID ```yaml @@ -122,22 +137,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -DomainController The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. @@ -155,9 +154,9 @@ Accept wildcard characters: False ``` ### -Force -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. +The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -This parameter specifies whether to test that the site mailbox provisioning is working independently of the SharePoint deployment. We recommend that you never use this parameter for production site mailboxes. +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. ```yaml Type: SwitchParameter @@ -241,12 +240,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/exchange/New-SiteMailboxProvisioningPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/New-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/exchange/New-SiteMailboxProvisioningPolicy.md index 3d773c284c..2766674f44 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/exchange/New-SiteMailboxProvisioningPolicy.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-sitemailboxprovisioningpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-SiteMailboxProvisioningPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the New-SiteMailboxProvisioningPolicy cmdlet to create provisioning policies for site mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,13 +32,14 @@ New-SiteMailboxProvisioningPolicy [-Name] [-IssueWarningQuota ] [-MaxReceiveSize ] [-ProhibitSendReceiveQuota ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Site mailboxes allow access to both Microsoft SharePoint documents and Exchange email using the same client interface. Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,9 +51,7 @@ New-SiteMailboxProvisioningPolicy -Name SM_ProvisioningPolicy -IsDefault -IssueW This example creates the default provisioning policy named SM\_ProvisioningPolicy that has the following settings: - The warning quota for the site mailboxes is 9 GB. - - The site mailboxes are prohibited from receiving messages when the mailbox size reaches 10 GB. - - The maximum size of email messages that can be sent to site mailboxes is 50 MB. ### Example 2 @@ -90,7 +90,6 @@ Accept wildcard characters: False 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. - - The value $null. This is the default value. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text. ```yaml @@ -109,8 +108,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -129,8 +127,7 @@ Accept wildcard characters: False ### -DefaultAliasPrefixEnabled 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 Office 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). - +- $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`). - $false: Aliases don't get the default prefix text. The value of this parameter is related to the value of the AliasPrefix parameter. If you specify a text string for AliasPrefix, the DefaultAliasPrefixEnabled value is ignored. Specifying a text value for AliasPrefix automatically sets the value to $false, but even if you set it to $true, the default alias prefix text isn't used. @@ -188,13 +185,9 @@ The IssueWarningQuota parameter specifies the warning threshold for the size of 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -222,11 +215,8 @@ The MaxReceiveSize parameter specifies the maximum size of a message that can be When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -252,13 +242,9 @@ The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. I 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -301,12 +287,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/New-SupervisoryReviewPolicyV2.md new file mode 100644 index 0000000000..ed8687d950 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-SupervisoryReviewPolicyV2.md @@ -0,0 +1,224 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-SupervisoryReviewPolicyV2 + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-SupervisoryReviewPolicyV2 cmdlet to create supervisory review policies in the Microsoft Purview compliance portal. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-SupervisoryReviewPolicyV2 [-Name] -Reviewers + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-PolicyRBACScopes ] + [-PreservationPeriodInDays ] + [-UserReportingWorkloads ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-SupervisoryReviewPolicyV2 -Name "EU Brokers Policy" -Reviewers laura@contoso.com,julia@contoso.com -Comment "Created by the compliance team" +``` + +This example creates a new supervisory review policy named EU Brokers Policy. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Reviewers +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +{{ Fill Enabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +{{ Fill PolicyRBACScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreservationPeriodInDays +{{ Fill PreservationPeriodInDays Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserReportingWorkloads +{{ Fill UserReportingWorkloads Description }} + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-SupervisoryReviewRule.md b/exchange/exchange-ps/exchange/New-SupervisoryReviewRule.md new file mode 100644 index 0000000000..c4b9d1a57f --- /dev/null +++ b/exchange/exchange-ps/exchange/New-SupervisoryReviewRule.md @@ -0,0 +1,479 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-SupervisoryReviewRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-SupervisoryReviewRule cmdlet to create supervisory review rules in the Microsoft Purview compliance portal. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-SupervisoryReviewRule [-Name] -Policy + [-AdvancedRule ] + [-CcsiDataModelOperator ] + [-Condition ] + [-Confirm] + [-ContentContainsSensitiveInformation ] + [-ContentMatchesDataModel ] + [-ContentSources ] + [-DayXInsights ] + [-ExceptIfFrom ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfRevieweeIs ] + [-ExceptIfSenderDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSubjectOrBodyContainsWords ] + [-From ] + [-IncludeAdaptiveScopes ] + [-InPurviewFilter ] + [-Ocr ] + [-PolicyRBACScopes ] + [-SamplingRate ] + [-SentTo ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-SupervisoryReviewRule -Name "EU Brokers Rule" -Policy "EU Brokers Policy" -SamplingRate 100 -Condition "((NOT(Reviewee:US Compliance)) -AND (Reviewee:EU Brokers) -AND ((trade) -OR (insider trading)) -AND (NOT(approved by the Contoso financial team)))" +``` + +This example creates a new supervisory review rule named EU Brokers Rule with the following settings: + +- Policy: EU Brokers Policy +- Sampling rate: 100% +- Conditions: Supervise inbound and outbound communications for members of the EU Brokers group that contain the words trade or insider trading. +- Exceptions: Exclude supervision for members of the EU Compliance group, or messages that contain the phrase "approved by the Contoso financial team". + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Policy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdvancedRule +{{ Fill AdvancedRule Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CcsiDataModelOperator +{{ Fill CcsiDataModelOperator Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Condition +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:)...))"`. +- Direction: `"((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal))"`. +- Message contains words: `"(() -OR ()...)"`. Exceptions use the syntax `"(NOT(() -OR ()...))"`. +- Any attachment contains words: `"((Attachment:) -OR (Attachment:)...)"`. Exceptions use the syntax `"(NOT((Attachment:) -OR (Attachment:)...))"`. +- Any attachment has the extension: `"((AttachmentName:.) -OR (AttachmentName:.)...)"`. Exceptions use the syntax `"(NOT((AttachmentName:.) -OR (AttachmentName:.)...))"`. +- Message size is larger than: `"(MessageSize:)"`. For example `"(MessageSize:300KB)"`. Exceptions use the syntax `"(NOT(MessageSize:))"`. +- Any attachment is larger than: `"(AttachmentSize:)"`. For example `"(AttachmentSize:3MB)"`. Exceptions use the syntax `"(NOT(AttachmentSize:))"`. +- Parentheses ( ) are required around the whole filter. +- Separate multiple conditions or exception types with the AND operator. For example, `"((Reviewee:chris@contoso.com) -AND (AttachmentSize:3MB))"`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +{{ Fill ContentContainsSensitiveInformation Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchesDataModel +{{ Fill ContentMatchesDataModel Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentSources +{{ Fill ContentSources Description }} + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DayXInsights +{{ Fill DayXInsights Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFrom +{{ Fill ExceptIfFrom Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +{{ Fill ExceptIfRecipientDomainIs Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRevieweeIs +{{ Fill ExceptIfRevieweeIs Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderDomainIs +{{ Fill ExceptIfSenderDomainIs Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +{{ Fill ExceptIfSentTo Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectOrBodyContainsWords +{{ Fill ExceptIfSubjectOrBodyContainsWords Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -From +{{ Fill From Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAdaptiveScopes +{{ Fill IncludeAdaptiveScopes Description }} + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InPurviewFilter +{{ Fill InPurviewFilter Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Ocr +{{ Fill Ocr Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +{{ Fill PolicyRBACScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SamplingRate +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +{{ Fill SentTo Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/New-SweepRule.md b/exchange/exchange-ps/exchange/New-SweepRule.md similarity index 90% rename from exchange/exchange-ps/exchange/mailboxes/New-SweepRule.md rename to exchange/exchange-ps/exchange/New-SweepRule.md index 3bae35ddce..6aa53c55aa 100644 --- a/exchange/exchange-ps/exchange/mailboxes/New-SweepRule.md +++ b/exchange/exchange-ps/exchange/New-SweepRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-sweeprule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-SweepRule @@ -15,23 +14,32 @@ monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the New-SweepRule cmdlet to create Sweep rules in mailboxes. Sweep rules run a regular intervals to help keep your Inbox clean. +Use the New-SweepRule cmdlet to create Sweep rules in mailboxes. Sweep rules run at regular intervals to help keep your Inbox clean. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-SweepRule [-Name] -Provider [-Confirm] [-DestinationFolder ] - [-DomainController ] [-Enabled ] [-ExceptIfFlagged ] - [-ExceptIfPinned ] [-KeepForDays ] [-KeepLatest ] - [-Mailbox ] [-Sender ] [-SourceFolder ] +New-SweepRule [-Name] -Provider + [-Confirm] + [-DestinationFolder ] + [-DomainController ] + [-Enabled ] + [-ExceptIfFlagged ] + [-ExceptIfPinned ] + [-KeepForDays ] + [-KeepLatest ] + [-Mailbox ] + [-Sender ] + [-SourceFolder ] [-SystemCategory ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -94,8 +102,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,23 +124,14 @@ The DestinationFolder parameter specifies an action for the Sweep rule that move For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Unimportant` or `John:\Inbox\Misc`. The default value is `MailboxID:\Deleted Items`. @@ -173,7 +171,6 @@ Accept wildcard characters: False 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. - - $false: The rule is disabled. After you create the rule, you can enable or disable it by using the Enable-SweepRule and Disable-SweepRule cmdlets. @@ -192,41 +189,32 @@ Accept wildcard characters: False ``` ### -ExceptIfFlagged +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: - $true: The rule action isn't applied to messages that have a message flag applied. - - $false: The exception isn't used. The typical message flag values are: - Any - - Call - - DoNotForward - - FollowUp - - ForYourInformation - - Forward - - NoResponseNecessary - - Read - - Reply - - ReplyToAll - - Review ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,17 +224,18 @@ Accept wildcard characters: False ``` ### -ExceptIfPinned +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: - $true: The rule action isn't applied to messages that are pinned to the top of the Inbox. - - $false: The exception isn't used. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -295,23 +284,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -331,15 +311,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID For external senders, use their email address. @@ -363,23 +338,14 @@ The SourceFolder parameter specifies a condition for the Sweep rule that looks f For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Marketing` or `John:\Inbox\Reports`. The default value is `MailboxID:\Inbox`. @@ -401,51 +367,28 @@ Accept wildcard characters: False 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 - - Bills - - Document - - DocumentPlus - - Event - - Family - - File - - Flight - - FromContact - - Important - - LiveView - - Lodging - - MailingList - - Newsletter - - Photo - - Purchase - - RentalCar - - RestaurantReservation - - RetiredPromotion - - ShippingNotification - - Shopping - - SocialUpdate - - Travel - - Video ```yaml @@ -482,12 +425,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-SyncMailPublicFolder.md b/exchange/exchange-ps/exchange/New-SyncMailPublicFolder.md similarity index 76% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/New-SyncMailPublicFolder.md rename to exchange/exchange-ps/exchange/New-SyncMailPublicFolder.md index 1f0421cf72..8084e8b744 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/exchange/New-SyncMailPublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-syncmailpublicfolder -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-SyncMailPublicFolder @@ -15,33 +14,55 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -The New-SyncMailPublicFolder cmdlet is used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts to create mail-enabled public folder recipient objects in Exchange Online in Office 365 (the scripts synchronize mail-enabled public folder objects from the source on-premises Exchange organization to Office 365). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. +The New-SyncMailPublicFolder cmdlet is used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts to create mail-enabled public folder recipient objects in Exchange Online (the scripts synchronize mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-SyncMailPublicFolder [-Alias] [-Name] -EntryId [-Confirm] - [-DomainController ] [-EmailAddresses ] [-ExternalEmailAddress ] - [-HiddenFromAddressListsEnabled] [-OverrideRecipientQuotas] [-WhatIf] [-WindowsEmailAddress ] - [-AcceptMessagesOnlyFrom ] [-Contacts ] - [-CustomAttribute1 ] [-CustomAttribute10 ] [-CustomAttribute11 ] - [-CustomAttribute12 ] [-CustomAttribute13 ] [-CustomAttribute14 ] - [-CustomAttribute15 ] [-CustomAttribute2 ] [-CustomAttribute3 ] - [-CustomAttribute4 ] [-CustomAttribute5 ] [-CustomAttribute6 ] - [-CustomAttribute7 ] [-CustomAttribute8 ] [-CustomAttribute9 ] - [-DeliverToMailboxAndForward ] [-DisplayName ] - [-ForwardingAddress ] [-GrantSendOnBehalfTo ] - [-MaxReceiveSize ] [-MaxSendSize ] [-OnPremisesObjectId ] - [-RejectMessagesFrom ] [-RequireSenderAuthenticationEnabled ] +New-SyncMailPublicFolder [-Name] [-Alias] -EntryId + [-AcceptMessagesOnlyFrom ] + [-Confirm] + [-Contacts ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DeliverToMailboxAndForward ] + [-DisplayName ] + [-DomainController ] + [-EmailAddresses ] + [-ExternalEmailAddress ] + [-ForwardingAddress ] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled] + [-MaxReceiveSize ] + [-MaxSendSize ] + [-OnPremisesObjectId ] + [-OverrideRecipientQuotas] + [-RejectMessagesFrom ] + [-RequireSenderAuthenticationEnabled ] + [-WhatIf] + [-WindowsEmailAddress ] [] ``` ## DESCRIPTION This cmdlet is only used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,52 +75,6 @@ This cmdlet is only used by the Import-MailPublicFoldersForMigration.ps1 and Syn ## PARAMETERS -### -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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. - -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: - -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. - -- Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). - -If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). - -The Alias parameter never generates or updates the primary email address of a mail contact or a mail user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EntryId -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: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Name 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 ("). @@ -109,7 +84,7 @@ This value is also used for the DisplayName property if you don't use the Displa Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -118,166 +93,50 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). - -Valid syntax for this parameter is \:\,\:\,...\:\. The optional \ value specifies the type of email address. Some examples of valid values include: - -- SMTP: The primary SMTP address. You can use this value only once in a command. - -- smtp: Other SMTP email addresses. - -- X400: X.400 addresses in on-premises Exchange. - -- X500: X.500 addresses in on-premises Exchange. - -If you don't include a \ value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. - -To specify the primary SMTP email address, you can use any of the following methods: - -- Use the \ value SMTP on the address. - -- The first email address when you don't use any \ values, or when you use multiple \ values of smtp. +### -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. -- If it's available, use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. +The Alias value can contain letters, numbers and the following characters: -To enter multiple proxy email addresses, use the following syntax: "\:\","\:\",..."\:\". +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -```yaml -Type: ProxyAddress[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalEmailAddress -The ExternalEmailAddress parameter specifies an email address outside the organization. +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: -### -HiddenFromAddressListsEnabled -The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. +- Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). -- $true: The recipient isn't visible in address lists. +If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). -- $false: The recipient is visible in address lists. This is the default value. +The Alias parameter never generates or updates the primary email address of a mail contact or a mail user. ```yaml -Type: SwitchParameter +Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -Required: False -Position: Named +Required: True +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -OverrideRecipientQuotas +### -EntryId 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WindowsEmailAddress -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. - -- In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. - -The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. - -```yaml -Type: SmtpAddress +Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -Required: False +Required: True Position: Named Default value: None Accept pipeline input: False @@ -290,18 +149,13 @@ The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages t 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can specify multiple senders separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -311,7 +165,26 @@ 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 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -326,24 +199,19 @@ The Contacts parameter specifies the contacts for the public folder. Contacts ar Valid values for this parameter are recipients in your organization. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -359,7 +227,7 @@ This parameter specifies a value for the CustomAttribute1 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -375,7 +243,7 @@ This parameter specifies a value for the CustomAttribute10 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -391,7 +259,7 @@ This parameter specifies a value for the CustomAttribute11 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -407,7 +275,7 @@ This parameter specifies a value for the CustomAttribute12 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -423,7 +291,7 @@ This parameter specifies a value for the CustomAttribute13 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -439,7 +307,7 @@ This parameter specifies a value for the CustomAttribute14 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -455,7 +323,7 @@ This parameter specifies a value for the CustomAttribute15 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -471,7 +339,7 @@ This parameter specifies a value for the CustomAttribute2 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -487,7 +355,7 @@ This parameter specifies a value for the CustomAttribute3 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -503,7 +371,7 @@ This parameter specifies a value for the CustomAttribute4 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -519,7 +387,7 @@ This parameter specifies a value for the CustomAttribute5 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -535,7 +403,7 @@ This parameter specifies a value for the CustomAttribute6 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -551,7 +419,7 @@ This parameter specifies a value for the CustomAttribute7 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -567,7 +435,7 @@ This parameter specifies a value for the CustomAttribute8 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -583,7 +451,7 @@ This parameter specifies a value for the CustomAttribute9 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -596,7 +464,6 @@ Accept wildcard characters: False 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. - - $false: If a forwarding recipient is configured, messages are delivered only to the specified recipient, and messages aren't delivered to this mail-enabled public folder. If no forwarding recipient is configured, messages are delivered only to this mailbox. This is the default value. The default value is $false. This parameter is meaningful only if you configure a forwarding recipient by using the ForwardingAddress parameter. @@ -605,7 +472,7 @@ 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 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -623,7 +490,72 @@ 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 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailAddresses +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: + +- SMTP: The primary SMTP address. You can use this value only once in a command. +- smtp: Other SMTP email addresses. +- X400: X.400 addresses in on-premises Exchange. +- X500: X.500 addresses in on-premises Exchange. + +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. + +To specify the primary SMTP email address, you can use any of the following methods: + +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. +- If it's available, use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. + +```yaml +Type: ProxyAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalEmailAddress +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 @@ -636,21 +568,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID How messages are delivered and forwarded is controlled by the DeliverToMailboxAndForward parameter. - DeliverToMailboxAndForward is $true: Messages are delivered to this mail-enabled public folder and forwarded to the specified recipient. - - DeliverToMailboxAndForward is $false: Messages are only forwarded to the specified recipient. Messages aren't delivered to this mail-enabled public folder. The default value is blank ($null), which means no forwarding recipient is configured. @@ -659,7 +585,7 @@ 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 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -669,23 +595,18 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo -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 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. By default, this parameter is blank, which means no one else has permission to send on behalf of this public folder. @@ -693,7 +614,23 @@ 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 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenFromAddressListsEnabled +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 @@ -708,24 +645,21 @@ The MaxReceiveSize parameter specifies the maximum size of a message that can be When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -740,24 +674,21 @@ The MaxSendSize parameter specifies the maximum size of a message that can be se When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -767,13 +698,29 @@ Accept wildcard characters: False ``` ### -OnPremisesObjectId -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 Office 365. +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 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverrideRecipientQuotas +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 @@ -788,18 +735,13 @@ The RejectMessagesFrom parameter specifies who isn't allowed to send messages to 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can specify multiple senders separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -809,7 +751,7 @@ 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 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -822,14 +764,50 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WindowsEmailAddress +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. +- In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. + +The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. + +```yaml +Type: SmtpAddress +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -843,12 +821,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-SystemMessage.md b/exchange/exchange-ps/exchange/New-SystemMessage.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/New-SystemMessage.md rename to exchange/exchange-ps/exchange/New-SystemMessage.md index b034c5e148..05d97b7970 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-SystemMessage.md +++ b/exchange/exchange-ps/exchange/New-SystemMessage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-systemmessage +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-SystemMessage @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-SystemMessage cmdlet to create custom system messages. System messages are delivery status notifications (also known as DSNs, non-delivery reports, NDRs or bounce messages) and quota messages. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha New-SystemMessage -DsnCode -Internal -Language -Text [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Quota @@ -34,13 +34,14 @@ New-SystemMessage -DsnCode -Internal -Language -QuotaMessageType -Text [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION NDRs are issued to the senders of email messages that haven't reached their intended recipients. Quota messages are issued to users whose mailboxes or public folders have reached the specific warning, prohibit send, or prohibit receive quotas. Custom NDRs and quota messages replace the default messages that are included with Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,7 +66,7 @@ The DsnCode parameter specifies the enhanced status code for the custom system m 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. -To generate a list of default enhanced status codes that are used by Exchange, run this command: Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language,Text | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\Default DSNs.html". +To generate a list of default enhanced status codes that are used by Exchange, run this command: `Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language,Text | ConvertTo-Html | Set-Content -Path "C:\My Documents\Default DSNs.html"`. You need to use this parameter with the Language and Internal parameters. @@ -88,7 +89,6 @@ Accept wildcard characters: False 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. - - $false: The NDR is displayed to external senders. You need to use this parameter with the DsnCode and Language parameters. @@ -109,7 +109,7 @@ Accept wildcard characters: False ``` ### -Language -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://docs.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs). +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. @@ -131,50 +131,36 @@ The QuotaMessageType parameter specifies the quota for the custom system message Mailbox size quotas: -- ProhibitSendReceiveMailBox: A mailbox exceeds its ProhibitSendReceiveQuota limit. - +- ProhibitSendReceiveMailbox: A mailbox exceeds its ProhibitSendReceiveQuota limit. - ProhibitSendMailbox: A mailbox exceeds its ProhibitSendQuota limit. - - WarningMailbox: A mailbox exceeds its IssueWarningQuota limit when it has a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. - - WarningMailboxUnlimitedSize: A mailbox exceeds its IssueWarningQuota limit when it doesn't have a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. Public folder size quotas: - ProhibitPostPublicFolder: A public folder exceeds its ProhibitPostQuota limit. - - WarningPublicFolder: A public folder exceeds its IssueWarningQuota limit when it has a ProhibitPostQuota limit configured. - - WarningPublicFolderUnlimitedSize: A public folder exceeds its IssueWarningQuota limit when it doesn't have a ProhibitPostQuota limit configured. Maximum number of messages in a mailbox folder: - ProhibitReceiveMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountReceiveQuota limit. - - WarningMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it has a MailboxMessagesPerFolderCountReceiveQuota limit configured. - - WarningMailboxMessagesPerFolderUnlimitedCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it doesn't have a MailboxMessagesPerFolderCountReceiveQuota limit configured. Maximum number of subfolders in a mailbox folder: - ProhibitReceiveFolderHierarchyChildrenCountCount: A mailbox exceeds its FolderHierarchyChildrenCountReceiveQuota limit. - - WarningFolderHierarchyChildrenCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it has a FolderHierarchyChildrenCountReceiveQuota limit configured. - - WarningFolderHierarchyChildrenUnlimitedCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it doesn't have a FolderHierarchyChildrenCountReceiveQuota limit configured. - - ProhibitReceiveFoldersCount: A mailbox exceeds its FoldersCountReceiveQuota limit. - - WarningFoldersCount: A mailbox exceeds its FoldersCountWarningQuota limit when it has a FoldersCountReceiveQuota limit configured. - - WarningFoldersCountUnlimited A mailbox exceeds its FoldersCountWarningQuota limit when it doesn't have a FoldersCountReceiveQuota limit configured. Maximum number of levels (depth) in a mailbox folder: - ProhibitReceiveFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit. - - WarningFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it has a FolderHierarchyDepthReceiveQuota limit configured. - - WarningFolderHierarchyDepthUnlimited: : A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it doesn't have a FolderHierarchyDepthReceiveQuota limit configured. You need to use this parameter with the Language parameter. @@ -203,29 +189,22 @@ This parameter can contain text and HTML tags. The maximum length is 512 charact The following HTML tags are available: -- \ and \ (bold) - -- \ and \ (italic) - -- \ (line break) - -- \ and \ (paragraph) - -- \ and \ (hyperlink). Note: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag). +- `` and `` (bold) +- `` and `` (italic) +- `
` (line break) +- `

` and `

` (paragraph) +- `` and `` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag). Use the following escape codes for these special characters: -- < for \<. - -- > for \>. - -- " for ". - -- & for &. +- `<` for \< +- `>` for \> +- `"` for " +- `&` for & Here's an example value for this parameter that uses HTML tags and special characters: -'You tried to send a message to a \disabled\ mailbox. Please visit \Internal Support\ or contact "InfoSec" for more information.' +`'You tried to send a message to a disabled mailbox. Please visit Internal Support or contact "InfoSec" for more information.'` ```yaml Type: String @@ -243,8 +222,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -299,12 +277,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-TeamsProtectionPolicy.md b/exchange/exchange-ps/exchange/New-TeamsProtectionPolicy.md new file mode 100644 index 0000000000..18775fc30b --- /dev/null +++ b/exchange/exchange-ps/exchange/New-TeamsProtectionPolicy.md @@ -0,0 +1,194 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-TeamsProtectionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-TeamsProtectionPolicy cmdlet to create Microsoft Teams protection policies. + +**Note**: If the policy already exists (the Get-TeamsProtectionPolicy cmdlet returns output), you can't use this cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-TeamsProtectionPolicy [-Name] + [-Confirm] + [-HighConfidencePhishQuarantineTag ] + [-MalwareQuarantineTag ] + [-Organization ] + [-WhatIf] + [-ZapEnabled ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-TeamsProtectionPolicy -Name "Teams Protection Policy" +``` + +This example creates the Teams protection policy with the default values. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidencePhishQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages, and whether users receive quarantine notifications. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the default quarantine policy that's used is named AdminOnlyAccessPolicy. For more information about this quarantine policy, see [Anatomy of a quarantine policy](https://learn.microsoft.com/defender-office-365/quarantine-policies#anatomy-of-a-quarantine-policy). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MalwareQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages, and whether users receive quarantine notifications. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the default quarantine policy that's used is named AdminOnlyAccessPolicy. For more information about this quarantine policy, see [Anatomy of a quarantine policy](https://learn.microsoft.com/defender-office-365/quarantine-policies#anatomy-of-a-quarantine-policy). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ZapEnabled +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. +- $false: ZAP for malware and high confidence phishing messages in Teams is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/exchange/New-TeamsProtectionPolicyRule.md new file mode 100644 index 0000000000..b2a9f0c731 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-TeamsProtectionPolicyRule.md @@ -0,0 +1,252 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-TeamsProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-TeamsProtectionPolicyRule cmdlet to create Microsoft Teams protection policy rules. + +**Note**: If the rule already exists (the Get-TeamsProtectionPolicyRule cmdlet returns output), you can't use this cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-TeamsProtectionPolicyRule [-Name] -TeamsProtectionPolicy + [-Comments ] + [-Confirm] + [-Enabled ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Organization ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can use this cmdlet only if the following statements are true: + +- The Teams protection policy rule doesn't exist (the Get-TeamsProtectionPolicyRule cmdlet returns no output). +- The Teams protection policy exists (the Get-TeamsProtectionPolicy cmdlet returns output). + +> [!IMPORTANT] +> Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Configure ZAP for Teams protection in Defender for Office 365 Plan 2](https://learn.microsoft.com/defender-office-365/mdo-support-teams-about#configure-zap-for-teams-protection-in-defender-for-office-365-plan-2). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-TeamsProtectionPolicyRule -Name "Teams Protection Policy Rule" -TeamsProtectionPolicy "Teams Protection Policy" -ExceptIfSentToMemberOf research@contoso.onmicrosoft.com +``` + +This example creates the Teams protection policy rule with members of the group named Research excluded from ZAP for Teams protection. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsProtectionPolicy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for Teams messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md b/exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md new file mode 100644 index 0000000000..6ef2975372 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md @@ -0,0 +1,353 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-TenantAllowBlockListItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-TenantAllowBlockListItems cmdlet to add entries to the Tenant Allow/Block List in the Microsoft Defender portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Expiration +``` +New-TenantAllowBlockListItems -Entries -ListType [-ExpirationDate ] + [-Allow] + [-Block] + [-ListSubType ] + [-LogExtraDetails] + [-Notes ] + [-OutputJson] + [-RemoveAfter ] + [-SubmissionID ] + [] +``` + +### NoExpiration +``` +New-TenantAllowBlockListItems -Entries -ListType [-NoExpiration] + [-Allow] + [-Block] + [-ListSubType ] + [-LogExtraDetails] + [-Notes ] + [-OutputJson] + [-RemoveAfter ] + [-SubmissionID ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-TenantAllowBlockListItems -ListType Url -Block -Entries ~contoso.com~ +``` + +This example adds a URL block entry for contoso.com and all subdomains (for example, contoso.com, www.contoso.com, xyz.abc.contoso.com, and www.contoso.com/b). Because we didn't use the ExpirationDate or NoExpiration parameters, the entry expires after 30 days. + +### Example 2 +```powershell +New-TenantAllowBlockListItems -ListType FileHash -Block -Entries "768a813668695ef2483b2bde7cf5d1b2db0423a0d3e63e498f3ab6f2eb13ea3","2c0a35409ff0873cfa28b70b8224e9aca2362241c1f0ed6f622fef8d4722fd9a" -NoExpiration +``` + +This example adds a file block entry for the specified files that never expires. + +### Example 3 +```powershell +New-TenantAllowBlockListItems -Allow -ListType Url -ListSubType AdvancedDelivery -Entries *.fabrikam.com -NoExpiration +``` + +This example adds a URL allow entry for the specified third-party phishing simulation URL with no expiration. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +### Example 4 +```powershell +New-TenantAllowBlockListItems -Allow -ListType Url -Entries abcd.fabrikam.com -RemoveAfter 45 +``` + +This example adds a URL allow entry for the specified domain with expiration as 45 days after last used date. This allow entry permits URLs identified as bulk, spam, high confidence spam, and phishing (not high confidence phishing). + +For URLs identified as malware or high-confidence phishing, you need to submit the URLs Microsoft to create allow entries. For instructions, see [Report good URLs to Microsoft](https://learn.microsoft.com/defender-office-365/submissions-admin#report-good-urls-to-microsoft). + +## PARAMETERS + +### -Entries +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`. +- Sender: A domain or email address value. For example, `contoso.com` or `michelle@contoso.com`. +- URL: Use IPv4 or IPv6 addresses or hostnames. Wildcards (\* and ~) are supported in hostnames. Protocols, TCP/UDP ports, or user credentials are not supported. For details, see [URL syntax for the Tenant Allow/Block List](https://learn.microsoft.com/defender-office-365/tenant-allow-block-list-urls-configure#url-syntax-for-the-tenant-allowblock-list). +- IP: IPv6 addresses only: + + • Single IPv6 addresses in colon-hexadecimal format (for example, 2001:0db8:85a3:0000:0000:8a2e:0370:7334). + + • Single IPv6 addresses in zero-compression format (for example, 2001:db8::1 for 2001:0db8:0000:0000:0000:0000:0000:0001). + + • CIDR IPv6 ranges from 1 to 128 (for example, 2001:0db8::/32). + +To enter multiple values, use the following syntax: `"Value1","Value2",..."ValueN"`. + +Entry limits for each list subtype (sender, URL, file, or IP address): + +- **Exchange Online Protection**: The maximum number of allow entries is 500, and the maximum number of block entries is 500. +- **Defender for Office 365 Plan 1**: The maximum number of allow entries is 1000, and the maximum number of block entries is 1000. +- **Defender for Office 365 Plan 2**: The maximum number of allow entries is 5000, and the maximum number of block entries is 10000. + +The maximum number of characters in a file entry is 64 and the maximum number of characters in a URL entry is 250. + +You can't mix value types (sender, URL, file, or IP address) or allow and block actions in the same command. + +In most cases, you can't modify the sender, URL, file, or IP address values after you create the entry. The only exception is URL allow entries for phishing simulations (ListType = URL, ListSubType = AdvancedDelivery). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpirationDate +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: + +- Specify the date/time value in UTC: For example, `"2021-05-06 14:30:00z"`. +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2020 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +You can't use this parameter with the NoExpiration or RemoveAfter parameters. + +```yaml +Type: DateTime +Parameter Sets: Expiration +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ListType +The ListType parameter specifies the type of entry to add. Valid values are: + +- FileHash +- Sender +- Url +- IP + +```yaml +Type: ListType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoExpiration +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: + +- With the Block switch. +- With the Allow switch where the ListType parameter value is URL and the ListSubType parameter value is AdvancedDelivery. +- With the Allow switch where the ListType parameter value is IP. + +You can't use this switch with the ExpirationDate or RemoveAfter parameter. + +```yaml +Type: SwitchParameter +Parameter Sets: NoExpiration +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Allow +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. + +**Note**: See [Allow entries in the Tenant Allow/Block List](https://learn.microsoft.com/defender-office-365/tenant-allow-block-list-about#allow-entries-in-the-tenant-allowblock-list), before you try to create an allow entry. + +You can also use allow entries for third-party phishing simulation URLs with no expiration. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Block +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ListSubType +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 third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). +- Tenant: This is the default value. + +```yaml +Type: ListSubType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LogExtraDetails +{{ Fill LogExtraDetails Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Notes +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveAfter +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. + +You can use this parameter with the Allow switch when the ListType parameter value is Sender, FileHash, or Url. + +You can't use this parameter with the ExpirationDate or NoExpirationDate parameters. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutputJson +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubmissionID +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md new file mode 100644 index 0000000000..48976dd565 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md @@ -0,0 +1,185 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-TenantAllowBlockListSpoofItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-TenantAllowBlockListSpoofItems cmdlet to create spoofed sender entries in the Tenant Allow/Block List. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-TenantAllowBlockListSpoofItems [-Identity] -Action -SendingInfrastructure -SpoofedUser -SpoofType + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +This cmdlet adds a spoof pair (the combination of the spoofed user and the sending infrastructure) to the Tenant Allow/Block List. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-TenantAllowBlockListSpoofItems -Identity Default -Action Allow -SendingInfrastructure contoso.com -SpoofedUser bob@contoso.com -SpoofType External +``` + +This example creates an allow entry for the sender bob@contoso.com from the source contoso.com. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -SendingInfrastructure +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. +- An IP address using the syntax: \/24 (for example, 192.168.100.100/24). Use the IP address if the source IP address has no PTR record. /24 is the only available and maximum subnet depth. +- A verified DKIM domain. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -SpoofedUser +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. +- For domains inside your organization (intra-org), use the full email address that appears in the From field of the message. + +For spoofed senders, the maximum number of entries is 1024. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -SpoofType +The SpoofType parameter specifies whether this is an internal or external spoofed sender entry. Valid values are: + +- External +- Internal + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Action +The Action parameter specifies whether is an allowed or blocked spoofed sender entry. Valid values are: + +- Allow +- Block + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/New-ThrottlingPolicy.md b/exchange/exchange-ps/exchange/New-ThrottlingPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/server-health-and-performance/New-ThrottlingPolicy.md rename to exchange/exchange-ps/exchange/New-ThrottlingPolicy.md index 1b33d861c8..4b540a9784 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/New-ThrottlingPolicy.md +++ b/exchange/exchange-ps/exchange/New-ThrottlingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/new-throttlingpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-ThrottlingPolicy @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-ThrottlingPolicy cmdlet to create a non-default user throttling policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -169,15 +168,16 @@ New-ThrottlingPolicy [-Name] [-SuiteMaxConcurrency ] [-SuiteRechargeRate ] [-ThrottlingPolicyScope ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -By default, there is one default throttling policy named GlobalThrottlingPolicy\_\ with a throttling scope of Global. Microsoft Exchange Setup creates a default client throttling policy as part of the Client Access server role. You should not replace, re-create, or remove the existing default throttling policy. However, you can create additional throttling policies with the scope of Organization or Regular to change your user throttling settings. You can also edit policies with the scope of Organization and Regular that you've created using the Set-ThrottlingPolicy cmdlet. +By default, there is one default throttling policy named `GlobalThrottlingPolicy_` with a throttling scope of Global. Microsoft Exchange Setup creates a default client throttling policy as part of the Client Access server role. You should not replace, re-create, or remove the existing default throttling policy. However, you can create additional throttling policies with the scope of Organization or Regular to change your user throttling settings. You can also edit policies with the scope of Organization and Regular that you've created using the Set-ThrottlingPolicy cmdlet. -For more information about how to control how resources are consumed by individual users, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For more information about how to control how resources are consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -193,7 +193,7 @@ In Exchange Server 2010, this example creates a non-default throttling policy. A New-ThrottlingPolicy -Name ITUserPolicy -EwsMaxConcurrency 4 -ThrottlingPolicyScope Regular ``` -This example creates a non-default user throttling policy that can be associated with specific users. Any parameters that you omit inherit the values from the default throttling policy GlobalThrottlingPolicy\_\. After you create this policy, you must associate it with specific users. +This example creates a non-default user throttling policy that can be associated with specific users. Any parameters that you omit inherit the values from the default throttling policy `GlobalThrottlingPolicy_`. After you create this policy, you must associate it with specific users. ### Example 3 ```powershell @@ -207,7 +207,7 @@ In Exchange Server 2010, this example creates a policy for a tenant that sets th New-ThrottlingPolicy -Name AllUsersEWSPolicy -EwsMaxConcurrency 4 -ThrottlingPolicyScope Organization ``` -This example creates a policy that applies to all users in your organization. Any parameters that you omit inherit the values from the default throttling policy GlobalThrottlingPolicy\_\. +This example creates a policy that applies to all users in your organization. Any parameters that you omit inherit the values from the default throttling policy `GlobalThrottlingPolicy_`. ### Example 5 ```powershell @@ -233,7 +233,7 @@ This example creates a throttling policy that restricts a user to be able to onl ## PARAMETERS ### -Name -The Name parameter specifies the name of the object in Active Directory. The default policy is named DefaultThrottlingPolicy\. +The Name parameter specifies the name of the object in Active Directory. The default policy is named `DefaultThrottlingPolicy`. ```yaml Type: String @@ -297,7 +297,7 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInAD -This parameter is available or functional only in 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. @@ -315,7 +315,7 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInCAS -This parameter is available or functional only in 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. @@ -333,7 +333,7 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -465,8 +465,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -611,7 +610,7 @@ Accept wildcard characters: False ``` ### -CPAPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -645,7 +644,7 @@ Accept wildcard characters: False ``` ### -CPUStartPercent -This parameter is available or functional only in 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. @@ -663,7 +662,7 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxConcurrency -The DiscoveryMaxConcurrency parameter specifies the number of concurrent discovery search executions that a user can have at the same time. +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 @@ -679,7 +678,7 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxKeywords -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://docs.microsoft.com/powershell/module/exchange/mailboxes/search-mailbox). +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 @@ -775,7 +774,7 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxStatsSearchMailboxes -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://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). +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 @@ -937,7 +936,7 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInAD -This parameter is available or functional only in 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. @@ -955,7 +954,7 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInCAS -This parameter is available or functional only in 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. @@ -973,7 +972,7 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1183,7 +1182,7 @@ Accept wildcard characters: False ``` ### -EWSFastSearchTimeoutInSeconds -This parameter is available or functional only in 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. @@ -1201,7 +1200,7 @@ Accept wildcard characters: False ``` ### -EWSFindCountLimit -This parameter is available or functional only in 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. @@ -1251,7 +1250,7 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInAD -This parameter is available or functional only in 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. @@ -1269,7 +1268,7 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1287,7 +1286,7 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1403,7 +1402,7 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInAD -This parameter is available or functional only in 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. @@ -1421,7 +1420,7 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1439,7 +1438,7 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1473,13 +1472,11 @@ Accept wildcard characters: False ``` ### -IsServiceAccount -The IsServiceAccount switch specifies whether you want the user accounts associated with this policy to be moderated by the per-user thresholds specified by this policy, and also by additional throttling based on the health of system resources, such as overall CPU usage. - -This value is set to $false by default. +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 may want to set this value to $true if you intend to associate this policy with user accounts that require higher throttling limits. An account that might require higher throttling limits is a service account that performs a lot of non-interactive work (for example, service accounts that perform IMAP mailbox migrations or nightly Windows PowerShell tasks). +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). -By setting the IsServiceAccount switch to $true, work done by these accounts is moderated by the higher user throttling settings that you configure using the user throttling policy, but is slowed if resources start getting unhealthy. +By using this switch, work done by these accounts is moderated by the higher user throttling settings that you configure using the user throttling policy, but is slowed if resources start getting unhealthy. ```yaml Type: SwitchParameter @@ -1655,7 +1652,11 @@ Accept wildcard characters: False ``` ### -OWAMaxConcurrency -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. The OwaMaxConcurrency 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. +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. + +**Note**: We don't recommend setting this parameter to a large number or the value $null, because server performance might be negatively affected. ```yaml Type: UInt32 @@ -1671,7 +1672,7 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInAD -This parameter is available or functional only in 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. @@ -1689,7 +1690,7 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1707,7 +1708,7 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1853,7 +1854,7 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInAD -This parameter is available or functional only in 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. @@ -1871,7 +1872,7 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1889,7 +1890,7 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -2006,7 +2007,6 @@ Accept wildcard characters: False 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. - - In the context of Exchange Web Services, the PowerShellMaxConcurrency parameter specifies the number of concurrent cmdlet executions that a user can have at the same time. This parameter value doesn't necessarily correlate to the number of browsers opened by the user. @@ -2028,21 +2028,13 @@ Accept wildcard characters: False 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 - - Move-ActiveMailboxDatabase - - Remove-AcceptedDomain - - Remove-Mailbox - - Remove-MailUser - - Remove-Organization - - Set-Mailbox - - Set-MailUser - - Update-MailboxDatabaseCopy The time period used for this limit is specified by the PowerShellMaxDestructiveCmdletsTimePeriod parameter. Both values should be set at the same time. This feature isn't on by default. For more information, see the "Examples" section. @@ -2389,7 +2381,7 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInAD -This parameter is available or functional only in 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. @@ -2407,7 +2399,7 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInCAS -This parameter is available or functional only in 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. @@ -2425,7 +2417,7 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -2672,12 +2664,10 @@ Accept wildcard characters: False 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. - - Organization: Specifies a custom policy that applies to all users in your organization. - - Global: Reserved for the default throttling policy. -For more information about throttling policy scopes, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For more information about throttling policy scopes, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). ```yaml Type: ThrottlingPolicyScopeType @@ -2713,12 +2703,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-TransportRule.md b/exchange/exchange-ps/exchange/New-TransportRule.md similarity index 76% rename from exchange/exchange-ps/exchange/policy-and-compliance/New-TransportRule.md rename to exchange/exchange-ps/exchange/New-TransportRule.md index ae5478ee58..97c913ad9b 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-TransportRule.md +++ b/exchange/exchange-ps/exchange/New-TransportRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-transportrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # New-TransportRule @@ -17,7 +16,13 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the New-TransportRule cmdlet to create transport rules (mail flow rules) in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +**Note**: + +- The action of a rule without conditions or exceptions is applied to all messages, which could have unintended consequences. For example, if the rule action deletes messages, the rule without conditions or exceptions might delete all inbound and outbound messages for the entire organization. + +- Rules that use Active Directory or Microsoft Entra ID properties as conditions or exceptions work only on senders or recipients in the organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,110 +32,110 @@ New-TransportRule [-Name] [-ADComparisonAttribute ] [-ADComparisonOperator ] [-AddManagerAsRecipientType ] - [-AddToRecipients ] - [-AnyOfCcHeader ] - [-AnyOfCcHeaderMemberOf ] - [-AnyOfRecipientAddressContainsWords ] - [-AnyOfRecipientAddressMatchesPatterns ] - [-AnyOfToCcHeader ] - [-AnyOfToCcHeaderMemberOf ] - [-AnyOfToHeader ] - [-AnyOfToHeaderMemberOf ] + [-AddToRecipients ] + [-AnyOfCcHeader ] + [-AnyOfCcHeaderMemberOf ] + [-AnyOfRecipientAddressContainsWords ] + [-AnyOfRecipientAddressMatchesPatterns ] + [-AnyOfToCcHeader ] + [-AnyOfToCcHeaderMemberOf ] + [-AnyOfToHeader ] + [-AnyOfToHeaderMemberOf ] [-ApplyClassification ] [-ApplyHtmlDisclaimerFallbackAction ] [-ApplyHtmlDisclaimerLocation ] [-ApplyHtmlDisclaimerText ] [-ApplyOME ] + [-ApplyRightsProtectionCustomizationTemplate ] [-ApplyRightsProtectionTemplate ] - [-AttachmentContainsWords ] - [-AttachmentExtensionMatchesWords ] + [-AttachmentContainsWords ] + [-AttachmentExtensionMatchesWords ] [-AttachmentHasExecutableContent ] [-AttachmentIsPasswordProtected ] [-AttachmentIsUnsupported ] - [-AttachmentMatchesPatterns ] - [-AttachmentNameMatchesPatterns ] + [-AttachmentMatchesPatterns ] + [-AttachmentNameMatchesPatterns ] [-AttachmentProcessingLimitExceeded ] - [-AttachmentPropertyContainsWords ] + [-AttachmentPropertyContainsWords ] [-AttachmentSizeOver ] - [-BetweenMemberOf1 ] - [-BetweenMemberOf2 ] - [-BlindCopyTo ] + [-BetweenMemberOf1 ] + [-BetweenMemberOf2 ] + [-BlindCopyTo ] [-Comments ] [-Confirm] - [-ContentCharacterSetContainsWords ] - [-CopyTo ] + [-ContentCharacterSetContainsWords ] + [-CopyTo ] [-DeleteMessage ] - [-Disconnect ] [-DlpPolicy ] + [-Disconnect ] [-DomainController ] [-Enabled ] [-ExceptIfADComparisonAttribute ] [-ExceptIfADComparisonOperator ] - [-ExceptIfAnyOfCcHeader ] - [-ExceptIfAnyOfCcHeaderMemberOf ] - [-ExceptIfAnyOfRecipientAddressContainsWords ] - [-ExceptIfAnyOfRecipientAddressMatchesPatterns ] - [-ExceptIfAnyOfToCcHeader ] - [-ExceptIfAnyOfToCcHeaderMemberOf ] - [-ExceptIfAnyOfToHeader ] - [-ExceptIfAnyOfToHeaderMemberOf ] - [-ExceptIfAttachmentContainsWords ] - [-ExceptIfAttachmentExtensionMatchesWords ] + [-ExceptIfAnyOfCcHeader ] + [-ExceptIfAnyOfCcHeaderMemberOf ] + [-ExceptIfAnyOfRecipientAddressContainsWords ] + [-ExceptIfAnyOfRecipientAddressMatchesPatterns ] + [-ExceptIfAnyOfToCcHeader ] + [-ExceptIfAnyOfToCcHeaderMemberOf ] + [-ExceptIfAnyOfToHeader ] + [-ExceptIfAnyOfToHeaderMemberOf ] + [-ExceptIfAttachmentContainsWords ] + [-ExceptIfAttachmentExtensionMatchesWords ] [-ExceptIfAttachmentHasExecutableContent ] [-ExceptIfAttachmentIsPasswordProtected ] [-ExceptIfAttachmentIsUnsupported ] - [-ExceptIfAttachmentMatchesPatterns ] - [-ExceptIfAttachmentNameMatchesPatterns ] + [-ExceptIfAttachmentMatchesPatterns ] + [-ExceptIfAttachmentNameMatchesPatterns ] [-ExceptIfAttachmentProcessingLimitExceeded ] - [-ExceptIfAttachmentPropertyContainsWords ] + [-ExceptIfAttachmentPropertyContainsWords ] [-ExceptIfAttachmentSizeOver ] - [-ExceptIfBetweenMemberOf1 ] - [-ExceptIfBetweenMemberOf2 ] - [-ExceptIfContentCharacterSetContainsWords ] - [-ExceptIfFrom ] - [-ExceptIfFromAddressContainsWords ] - [-ExceptIfFromAddressMatchesPatterns ] - [-ExceptIfFromMemberOf ] + [-ExceptIfBetweenMemberOf1 ] + [-ExceptIfBetweenMemberOf2 ] + [-ExceptIfContentCharacterSetContainsWords ] + [-ExceptIfFrom ] + [-ExceptIfFromAddressContainsWords ] + [-ExceptIfFromAddressMatchesPatterns ] + [-ExceptIfFromMemberOf ] [-ExceptIfFromScope ] [-ExceptIfHasClassification ] [-ExceptIfHasNoClassification ] [-ExceptIfHasSenderOverride ] [-ExceptIfHeaderContainsMessageHeader ] - [-ExceptIfHeaderContainsWords ] + [-ExceptIfHeaderContainsWords ] [-ExceptIfHeaderMatchesMessageHeader ] - [-ExceptIfHeaderMatchesPatterns ] - [-ExceptIfManagerAddresses ] + [-ExceptIfHeaderMatchesPatterns ] + [-ExceptIfManagerAddresses ] [-ExceptIfManagerForEvaluatedUser ] - [-ExceptIfMessageContainsAllDataClassifications ] - [-ExceptIfMessageContainsDataClassifications ] + [-ExceptIfMessageContainsDataClassifications ] [-ExceptIfMessageSizeOver ] [-ExceptIfMessageTypeMatches ] - [-ExceptIfRecipientADAttributeContainsWords ] - [-ExceptIfRecipientADAttributeMatchesPatterns ] - [-ExceptIfRecipientAddressContainsWords ] - [-ExceptIfRecipientAddressMatchesPatterns ] - [-ExceptIfRecipientDomainIs ] - [-ExceptIfRecipientInSenderList ] + [-ExceptIfRecipientADAttributeContainsWords ] + [-ExceptIfRecipientADAttributeMatchesPatterns ] + [-ExceptIfRecipientAddressContainsWords ] + [-ExceptIfRecipientAddressMatchesPatterns ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfRecipientInSenderList ] [-ExceptIfSCLOver ] - [-ExceptIfSenderADAttributeContainsWords ] - [-ExceptIfSenderADAttributeMatchesPatterns ] - [-ExceptIfSenderDomainIs ] - [-ExceptIfSenderInRecipientList ] + [-ExceptIfSenderADAttributeContainsWords ] + [-ExceptIfSenderADAttributeMatchesPatterns ] + [-ExceptIfSenderDomainIs ] + [-ExceptIfSenderInRecipientList ] [-ExceptIfSenderIpRanges ] [-ExceptIfSenderManagementRelationship ] - [-ExceptIfSentTo ] - [-ExceptIfSentToMemberOf ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] [-ExceptIfSentToScope ] - [-ExceptIfSubjectContainsWords ] - [-ExceptIfSubjectMatchesPatterns ] - [-ExceptIfSubjectOrBodyContainsWords ] - [-ExceptIfSubjectOrBodyMatchesPatterns ] + [-ExceptIfSubjectContainsWords ] + [-ExceptIfSubjectMatchesPatterns ] + [-ExceptIfSubjectOrBodyContainsWords ] + [-ExceptIfSubjectOrBodyMatchesPatterns ] [-ExceptIfWithImportance ] [-ExpiryDate ] - [-From ] - [-FromAddressContainsWords ] - [-FromAddressMatchesPatterns ] - [-FromMemberOf ] + [-From ] + [-FromAddressContainsWords ] + [-FromAddressMatchesPatterns ] + [-FromMemberOf ] [-FromScope ] [-GenerateIncidentReport ] [-GenerateNotification ] @@ -138,51 +143,52 @@ New-TransportRule [-Name] [-HasNoClassification ] [-HasSenderOverride ] [-HeaderContainsMessageHeader ] - [-HeaderContainsWords ] + [-HeaderContainsWords ] [-HeaderMatchesMessageHeader ] - [-HeaderMatchesPatterns ] - [-IncidentReportContent ] + [-HeaderMatchesPatterns ] + [-IncidentReportContent ] [-IncidentReportOriginalMail ] [-LogEventText ] - [-ManagerAddresses ] + [-ManagerAddresses ] [-ManagerForEvaluatedUser ] - [-MessageContainsAllDataClassifications ] - [-MessageContainsDataClassifications ] + [-MessageContainsDataClassifications ] [-MessageSizeOver ] [-MessageTypeMatches ] [-Mode ] [-ModerateMessageByManager ] - [-ModerateMessageByUser ] + [-ModerateMessageByUser ] [-NotifySender ] [-PrependSubject ] [-Priority ] [-Quarantine ] - [-RecipientADAttributeContainsWords ] - [-RecipientADAttributeMatchesPatterns ] - [-RecipientAddressContainsWords ] - [-RecipientAddressMatchesPatterns ] - [-RecipientDomainIs ] - [-RecipientInSenderList ] - [-RedirectMessageTo ] + [-RecipientADAttributeContainsWords ] + [-RecipientADAttributeMatchesPatterns ] + [-RecipientAddressContainsWords ] + [-RecipientAddressMatchesPatterns ] + [-RecipientAddressType ] + [-RecipientDomainIs ] + [-RecipientInSenderList ] + [-RedirectMessageTo ] [-RejectMessageEnhancedStatusCode ] [-RejectMessageReasonText ] [-RemoveHeader ] [-RemoveOME ] [-RemoveOMEv2 ] + [-RemoveRMSAttachmentEncryption ] [-RouteMessageOutboundConnector ] [-RouteMessageOutboundRequireTls ] [-RuleErrorAction ] [-RuleSubType ] [-SCLOver ] - [-SenderADAttributeContainsWords ] - [-SenderADAttributeMatchesPatterns ] + [-SenderADAttributeContainsWords ] + [-SenderADAttributeMatchesPatterns ] [-SenderAddressLocation ] - [-SenderDomainIs ] - [-SenderInRecipientList ] + [-SenderDomainIs ] + [-SenderInRecipientList ] [-SenderIpRanges ] [-SenderManagementRelationship ] - [-SentTo ] - [-SentToMemberOf ] + [-SentTo ] + [-SentToMemberOf ] [-SentToScope ] [-SetAuditSeverity ] [-SetHeaderName ] @@ -191,10 +197,10 @@ New-TransportRule [-Name] [-SmtpRejectMessageRejectStatusCode ] [-SmtpRejectMessageRejectText ] [-StopRuleProcessing ] - [-SubjectContainsWords ] - [-SubjectMatchesPatterns ] - [-SubjectOrBodyContainsWords ] - [-SubjectOrBodyMatchesPatterns ] + [-SubjectContainsWords ] + [-SubjectMatchesPatterns ] + [-SubjectOrBodyContainsWords ] + [-SubjectOrBodyMatchesPatterns ] [-UseLegacyRegex ] [-WhatIf] [-WithImportance ] @@ -206,7 +212,7 @@ In on-premises Exchange organizations, rules created on Mailbox servers are stor The search for words or text patterns in the subject or other header fields in the message occurs after the message has been decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -218,11 +224,8 @@ New-TransportRule "Ethical Wall - Sales and Brokerage Departments" -BetweenMembe This example creates a rule with the following settings: - Name: Ethical Wall - Sales and Brokerage Departments - - Conditions: Messages that are sent between members of the groups named Sales Department and Brokerage Department. - - Actions: The message is rejected, and the custom rejection text is Messages sent between the Sales and Brokerage departments are strictly prohibited. Note that the default enhanced status code 5.7.1 is used, because we didn't use the RejectMessageEnhancedStatusCode parameter. - - Exceptions: The Subject field contains the phrases Press Release or Corporate Communication or the message was sent by Tony Smith or Pilar Ackerman. ## PARAMETERS @@ -246,7 +249,7 @@ Accept wildcard characters: False ### -ActivationDate 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". +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". ```yaml Type: DateTime @@ -264,64 +267,38 @@ Accept wildcard characters: False ### -ADComparisonAttribute 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ADComparisonAttribute parameter specifies a condition that compares an Active Directory attribute between the sender and all recipients of the message. This parameter works when the recipients are individual users. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode If you don't use the ADComparisonOperator parameter, the default comparison operator Equal is used. @@ -342,12 +319,11 @@ Accept wildcard characters: False ### -ADComparisonOperator 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ADComparisonOperator parameter specifies the comparison operator for the ADComparisonAttribute parameter. Valid values are: - Equal (This is the default value) - - NotEqual ```yaml @@ -366,16 +342,13 @@ Accept wildcard characters: False ### -AddManagerAsRecipientType This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The AddManagerAsRecipientType parameter specifies an action that delivers or redirects messages to the user that's defined in the sender's Manager attribute. Valid values are: - To: Add the sender's manager to the To field of the message. - - Cc: Add the sender's manager to the Cco field of the message. - - Bcc: Add the sender's manager to the Bcc field of the message. - - Redirect: Redirect the message to the sender's manager without notifying the sender or the recipients. This action only works if the sender's Manager attribute is defined. @@ -401,18 +374,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The AddToRecipients parameter specifies an action that adds recipients to the To field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -430,27 +398,22 @@ Accept wildcard characters: False ### -AnyOfCcHeader 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfCcHeader parameter specifies a condition that looks for recipients in the Cc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -468,27 +431,22 @@ Accept wildcard characters: False ### -AnyOfCcHeaderMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfCcHeaderMemberOf parameter specifies a condition that looks for group members in the Cc field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -512,7 +470,7 @@ The AnyOfRecipientAddressContainsWords parameter specifies a condition that look A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Word[] @@ -532,11 +490,11 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The AnyOfRecipientAddressMatchesPatterns parameter specifies a condition that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The AnyOfRecipientAddressMatchesPatterns parameter specifies a condition 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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Pattern[] @@ -554,27 +512,22 @@ Accept wildcard characters: False ### -AnyOfToCcHeader 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToCcHeader parameter specifies a condition that looks for recipients in the To or Cc fields of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -592,27 +545,22 @@ Accept wildcard characters: False ### -AnyOfToCcHeaderMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToCcHeaderMemberOf parameter specifies a condition that looks for group members in the To and Cc fields of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -630,27 +578,22 @@ Accept wildcard characters: False ### -AnyOfToHeader 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToHeader parameter specifies a condition that looks for recipients in the To field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -668,27 +611,22 @@ Accept wildcard characters: False ### -AnyOfToHeaderMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToHeaderMemberOf parameter specifies a condition that looks for group members in the To field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -706,7 +644,7 @@ Accept wildcard characters: False ### -ApplyClassification This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyClassification parameter specifies an action that applies a message classification to messages. Use the Get-MessageClassification cmdlet to see the message classification objects that are available. @@ -728,15 +666,20 @@ Accept wildcard characters: False ### -ApplyHtmlDisclaimerFallbackAction This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. + +The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be applied to a message (for example, encrypted or signed messages where the contents can't be altered). Valid values are: -The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be added to a message. Valid values are: +- Wrap: This is the default value. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients. -- Wrap: The original message is wrapped in a new message envelope, and the disclaimer is used as the message body for the new message. This is the default value. Subsequent mail flow rules are applied to the new message envelope, not to the original message. Therefore, configure a rule with this action at a lower priority (a higher priority number) than other rules. If the original message can't be wrapped in a new message envelope, the original message isn't delivered. The message is returned to the sender in an non-delivery report (also known as an NDR or bounce message). + If you want other rules to examine and act on the original message (which is now an attachment in the new message), make sure those rules are applied _before_ the disclaimer rule by using a lower priority for the disclaimer rule and higher priority for other rules. -- Ignore: The rule is ignored and the message is delivered without the disclaimer. + If the process of inserting the original message as an attachment in the new message fails, the original message isn't delivered. The original message is returned to the sender in an NDR. -- Reject: The message is rejected. + In Microsoft 365, don't use this value in rules that affect incoming messages from external senders. Use the value Reject instead. The effects of the value Wrap interfere with Safe Attachments scanning of messages from external senders. + +- Ignore: The rule is ignored and the original message is delivered without the disclaimer. +- Reject: The original message is returned to the sender in an NDR. If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Wrap is used. @@ -756,13 +699,12 @@ Accept wildcard characters: False ### -ApplyHtmlDisclaimerLocation This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerLocation parameter specifies where to insert the HTML disclaimer text in the body of messages. Valid values are: - Append: The disclaimer is added to the end of the message body. This is the default value. - -- Prepend: The disclaimer is inserted to the beginning of the message body. +- Prepend: The disclaimer is inserted at the beginning of the message body. If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Append is used. @@ -782,10 +724,38 @@ Accept wildcard characters: False ### -ApplyHtmlDisclaimerText This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerText parameter specifies an action that adds the disclaimer text to messages. Disclaimer text can include HTML tags and inline cascading style sheet (CSS) tags. You can add images using the IMG tag. +This parameter also supports the following tokens that use values from the sender: + +- %%City%% +- %%Company%% +- %%CountryOrRegion%% +- %%Department%% +- %%DisplayName%% +- %%Fax%% +- %%FirstName%% +- %%HomePhone%% +- %%Initials%% +- %%LastName%% +- %%Manager%% +- %%MobilePhone%% +- %%Notes%% +- %%Office%% +- %%Pager%% +- %%Phone%% +- %%PostalCode%% +- %%PostOfficeBox%% +- %%StateOrProvince%% +- %%StreetAddress%% +- %%Title%% +- %%UserPrincipalName%% +- %%WindowsEmailAddress%% + +The maximum number of characters is 5000. + You use the ApplyHtmlDisclaimerLocation parameter to specify where to insert the text in the message body (the default value is Append), and the ApplyHtmlDisclaimerFallbackAction parameter to specify what to do if the disclaimer can't be added to the message (the default value is Wrap). ```yaml @@ -806,10 +776,9 @@ This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. -The ApplyOME parameter specifies an action that encrypts messages and their attachments by using Office 365 Message Encryption. Valid values are: +The ApplyOME parameter specifies an action that encrypts messages and their attachments by using Microsoft Purview Message Encryption. Valid values are: - $true: The message and attachments are encrypted. - - $false: The message and attachments aren't encrypted. ```yaml @@ -825,10 +794,30 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ApplyRightsProtectionCustomizationTemplate +This parameter is available only in the cloud-based service. + +This parameter specifies an action or part of an action for the rule. + +The ApplyRightsProtectionCustomizationTemplate parameter specifies an action that applies a custom branding template for OME encrypted messages. You identify the custom branding template by name. If the name contains spaces, enclose the name in quotation marks ("). + +```yaml +Type: OMEConfigurationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ApplyRightsProtectionTemplate This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyRightsProtectionTemplate parameter specifies an action that applies rights management service (RMS) templates to messages. You identify the RMS template by name. If the name contains spaces, enclose the name in quotation marks ("). @@ -836,7 +825,7 @@ To use this action, you need to have an Active Directory Rights Management Servi Use the Get-RMSTemplate cmdlet to see the RMS templates that are available. -For more information, see [Transport protection rules](https://docs.microsoft.com/exchange/transport-protection-rules-exchange-2013-help). +For more information, see [Transport protection rules](https://learn.microsoft.com/exchange/transport-protection-rules-exchange-2013-help). ```yaml Type: RmsTemplateIdParameter @@ -854,7 +843,7 @@ Accept wildcard characters: False ### -AttachmentContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentContainsWords parameter specifies a condition that looks for words in message attachments. Only supported attachment types are checked. @@ -876,10 +865,12 @@ Accept wildcard characters: False ### -AttachmentExtensionMatchesWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentExtensionMatchesWords parameter specifies a condition that looks for words in the file name extensions of message attachments. You can specify multiple words separated by commas. +**Note:** Nested attachment extensions (files inside the original attachments) are also inspected. To see all attachment extensions that were evaluated for a specific message, use the Test-TextExtraction cmdlet. + ```yaml Type: Word[] Parameter Sets: (All) @@ -896,14 +887,15 @@ Accept wildcard characters: False ### -AttachmentHasExecutableContent 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentHasExecutableContent parameter specifies a condition that looks for executable content in message attachments. Valid values are: +The AttachmentHasExecutableContent parameter specifies a condition that inspects messages where an attachment is an executable file. Valid values are: - $true: Look for executable content in message attachments. - - $false: Don't look for executable content in message attachments. +The system inspects the file properties rather than relying on the file's extension. For more information, see [Supported executable file types for mail flow rule inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-executable-file-types-for-mail-flow-rule-inspection). + ```yaml Type: Boolean Parameter Sets: (All) @@ -920,12 +912,11 @@ Accept wildcard characters: False ### -AttachmentIsPasswordProtected 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentIsPasswordProtected parameter specifies a condition that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection only works for Office documents and .zip files. Valid values are: +The AttachmentIsPasswordProtected parameter specifies a condition that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z), and .pdf files. Valid values are: - $true: Look for password protected attachments. - - $false: Don't look for password protected attachments. ```yaml @@ -944,15 +935,18 @@ Accept wildcard characters: False ### -AttachmentIsUnsupported 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentIsUnsupported parameter specifies a condition that looks for unsupported file types in messages. Unsupported file types are message attachments that aren't natively recognized by Exchange, and the required IFilter isn't installed. Valid values are: +The AttachmentIsUnsupported parameter specifies a condition that looks for unsupported file types in messages. Valid values are: - $true: Look for unsupported file types in messages. - - $false: Don't look for unsupported file types in messages. -For more information, see [Register Filter Pack IFilters with Exchange 2013](https://docs.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). +Rules can inspect the content of supported file types only. If the rule finds an attachment file type that isn't supported, the AttachmentIsUnsupported condition is triggered. + +For the list of supported file types, see [Supported file types for mail flow rule content inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-file-types-for-mail-flow-rule-content-inspection). + +In Exchange 2010, to extend the list of supported file types, see [Register Filter Pack IFilters](https://learn.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). ```yaml Type: Boolean @@ -970,11 +964,11 @@ Accept wildcard characters: False ### -AttachmentMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentMatchesPatterns parameter specifies a condition 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: "\","\",..."\". +You can specify multiple text patterns by using the following syntax: `"Regular expression1","Regular expression2",..."Regular expressionN"`. Only the first 150 kilobytes (KB) of the attachment is scanned when trying to match a text pattern. @@ -994,9 +988,9 @@ Accept wildcard characters: False ### -AttachmentNameMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentNameMatchesPatterns parameter specifies a condition that looks for text patterns in the file name of message attachments by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The AttachmentNameMatchesPatterns parameter specifies a condition that looks for text patterns in the file 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"`. ```yaml Type: Pattern[] @@ -1014,12 +1008,11 @@ Accept wildcard characters: False ### -AttachmentProcessingLimitExceeded 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentProcessingLimitExceeded parameter specifies a condition that looks for messages where attachment scanning didn't complete. Valid values are: - $true: Look for messages where attachment scanning didn't complete. - - $false: Don't look for messages where attachment scanning didn't complete. You use this condition to create rules that work together with other attachment processing rules to handle messages where the content can't be fully scanned. @@ -1040,36 +1033,23 @@ Accept wildcard characters: False ### -AttachmentPropertyContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentPropertyContainsWords parameter specifies a condition that looks for words in the properties of attached Office documents. This condition helps integrate mail flow rules (transport rules) with the File Classification Infrastructure (FCI) in Windows Server 2012 R2 or later, SharePoint, or a third-party classification system. Valid values are a built-in document property, or a custom property. The built-in document properties are: - Business Impact - - Compliancy - - Confidentiality - - Department - - Impact - - Intellectual Property - - Personally Identifiable Information - - Personal Information - - Personal Use - - Required Clearance - - PHI - - PII - - Project - - Protected Health Information The syntax for this parameter is "PropertyName:Word". To specify multiple properties, or multiple words for the same property, use the following syntax: "PropertyName1:Word1,Phrase with spaces,word2,...","PropertyName2:Word3,Phrase with spaces,word4,...". Don't use leading or trailing spaces. @@ -1080,7 +1060,7 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1099,17 +1079,15 @@ The AttachmentSizeOver parameter specifies a condition that looks for messages w When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages will be blocked. + ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) @@ -1126,23 +1104,18 @@ Accept wildcard characters: False ### -BetweenMemberOf1 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The BetweenMemberOf1 parameter specifies a condition that looks for messages that are sent between group members. You need to use this parameter with the BetweenMemberOf2 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1160,23 +1133,18 @@ Accept wildcard characters: False ### -BetweenMemberOf2 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The BetweenMemberOf2 parameter specifies a condition that looks for messages that are sent between group members. You need to use this parameter with the BetweenMemberOf1 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1199,18 +1167,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The BlindCopyTo parameter specifies an action that adds recipients to the Bcc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1244,8 +1207,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -1264,7 +1226,7 @@ Accept wildcard characters: False ### -ContentCharacterSetContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ContentCharacterSetContainsWords parameter specifies a condition that looks for character set names in messages. @@ -1291,18 +1253,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The CopyTo parameter specifies an action that adds recipients to the Cc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1325,7 +1282,6 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The DeleteMessage parameter specifies an action that silently drops messages without an NDR. Valid values are: - $true: Silently drop the message without an NDR. - - $false: Don't silently drop the message. ```yaml @@ -1342,21 +1298,20 @@ Accept wildcard characters: False ``` ### -Disconnect -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The Disconnect parameter specifies an action that ends the SMTP connection between the sending server and the Edge Transport server without generating an NDR. - $true: Silently end the SMTP session without generating an NDR. - - $false: Don't silently end the SMTP session. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1366,13 +1321,15 @@ Accept wildcard characters: False ``` ### -DlpPolicy -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://docs.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/data-loss-prevention). +**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). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1405,7 +1362,6 @@ Accept wildcard characters: False 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. - - $false: The new rule is disabled. To enable or disable a rule after you create it, use the Enable-TransportRule and Disable-TransportRule cmdlets. @@ -1424,66 +1380,40 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonAttribute -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfADComparisonAttribute parameter specifies an exception that compares an Active Directory attribute between the sender and all recipients of the message. This parameter works when the recipients are individual users. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode If you don't use the ExceptIfADComparisonOperator parameter, the default comparison operator Equal is used. @@ -1502,14 +1432,13 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonOperator -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfADComparisonOperator parameter specifies the comparison operator for the ExceptIfADComparisonAttribute parameter. Valid values are: - Equal (This is the default value) - - NotEqual ```yaml @@ -1526,29 +1455,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfCcHeader parameter specifies an exception that looks for recipients in the Cc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1564,29 +1488,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeaderMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfCcHeaderMemberOf parameter specifies an exception that looks for group members in the Cc field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1602,7 +1521,7 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -1610,7 +1529,7 @@ The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Word[] @@ -1626,15 +1545,15 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfAnyOfRecipientAddressMatchesPatterns parameter specifies an exception that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The ExceptIfAnyOfRecipientAddressMatchesPatterns parameter specifies an exception 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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Pattern[] @@ -1650,29 +1569,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToCcHeader parameter specifies an exception that looks for recipients in the To or Cc fields of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1688,29 +1602,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeaderMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToCcHeaderMemberOf parameter specifies an exception that looks for group members in the To and Cc fields of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1726,29 +1635,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToHeader parameter specifies an exception that looks for recipients in the To field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1764,29 +1668,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeaderMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToHeaderMemberOf parameter specifies an exception that looks for group members in the To field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1802,9 +1701,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentContainsWords parameter specifies an exception that looks for words in message attachments. Only supported attachment types are checked. @@ -1824,12 +1723,14 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentExtensionMatchesWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentExtensionMatchesWords parameter specifies an exception that looks for words in the file name extensions of message attachments. You can specify multiple words separated by commas. +**Note:** Nested attachment extensions (files inside the original attachments) are also inspected. To see all attachment extensions that were evaluated for a specific message, use the Test-TextExtraction cmdlet. + ```yaml Type: Word[] Parameter Sets: (All) @@ -1844,16 +1745,17 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentHasExecutableContent -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentHasExecutableContent parameter specifies an exception that looks for executable content in message attachments. Valid values are: +The ExceptIfAttachmentHasExecutableContent parameter specifies an exception that inspects messages where an attachment is an executable file. Valid values are: - $true: Look for executable content in message attachments. - - $false: Don't look for executable content in message attachments. +The system inspects the file properties rather than relying on the file extension. For more information, see [Supported executable file types for mail flow rule inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-executable-file-types-for-mail-flow-rule-inspection). + ```yaml Type: Boolean Parameter Sets: (All) @@ -1868,14 +1770,13 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsPasswordProtected -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentIsPasswordProtected parameter specifies an exception that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection only works for Office documents and .zip files. Valid values are: +The ExceptIfAttachmentIsPasswordProtected parameter specifies an exception that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z), and .pdf files. Valid values are: - $true: Look for password protected attachments. - - $false: Don't look for password protected attachments. ```yaml @@ -1892,17 +1793,20 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsUnsupported -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentIsUnsupported parameter specifies an exception that looks for unsupported file types in messages. Unsupported file types are message attachments that aren't natively recognized by Exchange, and the required IFilter isn't installed. Valid values are: +The ExceptIfAttachmentIsUnsupported parameter specifies an exception that looks for unsupported file types in messages. Valid values are: - $true: Look for unsupported file types in messages. - - $false: Don't look for unsupported file types in messages. -For more information, see [Register Filter Pack IFilters with Exchange 2013](https://docs.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). +Rules can inspect the content of supported file types only. If the rule finds an attachment file type that isn't supported, the ExceptIfAttachmentIsUnsupported exception is triggered. + +For the list of supported file types, see [Supported file types for mail flow rule content inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-file-types-for-mail-flow-rule-content-inspection). + +In Exchange 2010, to extend the list of supported file types, see [Register Filter Pack IFilters](https://learn.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). ```yaml Type: Boolean @@ -1918,13 +1822,13 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentMatchesPatterns parameter specifies an exception 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: "\","\",..."\". +You can specify multiple text patterns by using the following syntax: `"Regular expression1","Regular expression2",..."Regular expressionN"`. Only the first 150 KB of the attachment is scanned when trying to match a text pattern. @@ -1942,11 +1846,11 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentNameMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentNameMatchesPatterns parameter specifies an exception that looks for text patterns in the file name of message attachments by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The ExceptIfAttachmentNameMatchesPatterns parameter specifies an exception that looks for text patterns in the file 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"`. ```yaml Type: Pattern[] @@ -1962,14 +1866,13 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentProcessingLimitExceeded -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentProcessingLimitExceeded parameter specifies an exception that looks for messages where attachment scanning didn't complete. Valid values are: - $true: Look for messages where attachment scanning didn't complete. - - $false: Don't look for messages where attachment scanning didn't complete. You use this exception to create rules that work together with other attachment processing rules to handle messages where the content can't be fully scanned. @@ -1988,38 +1891,25 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentPropertyContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentPropertyContainsWords parameter specifies an exception that looks for words in the properties of attached Office documents. This condition helps integrate rules with the File Classification Infrastructure (FCI) in Windows Server 2012 R2 or later, SharePoint, or a third-party classification system. Valid values are a built-in document property, or a custom property. The built-in document properties are: - Business Impact - - Compliancy - - Confidentiality - - Department - - Impact - - Intellectual Property - - Personally Identifiable Information - - Personal Information - - Personal Use - - Required Clearance - - PHI - - PII - - Project - - Protected Health Information The syntax for this parameter is "PropertyName:Word". To specify multiple properties, or multiple words for the same property, use the following syntax: "PropertyName1:Word1,Phrase with spaces,word2,...","PropertyName2:Word3,Phrase with spaces,word4,...". Don't use values with leading or trailing spaces. @@ -2030,7 +1920,7 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2040,7 +1930,7 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentSizeOver -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2049,13 +1939,9 @@ The ExceptIfAttachmentSizeOver parameter specifies an exception that looks for m When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -2074,25 +1960,20 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf1 -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfBetweenMemberOf1 parameter specifies an exception that looks for messages that are sent between group members. You need to use this parameter with the ExceptIfBetweenMemberOf2 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -2108,25 +1989,20 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf2 -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfBetweenMemberOf2 parameter specifies an exception that looks for messages that are sent between group members. You need to use this parameter with the ExceptIfBetweenMemberOf1 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -2142,9 +2018,9 @@ Accept wildcard characters: False ``` ### -ExceptIfContentCharacterSetContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfContentCharacterSetContainsWords parameter specifies an exception that looks for character set names in messages. @@ -2164,25 +2040,20 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -2200,7 +2071,7 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2222,14 +2093,16 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfFromAddressMatchesPatterns parameter specifies an exception 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: "\","\",..."\". +The ExceptIfFromAddressMatchesPatterns parameter specifies an exception 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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). +**Note**: Trying to search for empty From addresses using this parameter doesn't work. + ```yaml Type: Pattern[] Parameter Sets: (All) @@ -2244,25 +2117,20 @@ Accept wildcard characters: False ``` ### -ExceptIfFromMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -2280,14 +2148,13 @@ Accept wildcard characters: False ``` ### -ExceptIfFromScope -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. The ExceptIfFromScope parameter specifies an exception 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. - +- InOrganization: The message was sent or received over an authenticated connection **AND** the sender meets at least one of the following criteria: The sender is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. - NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. ```yaml @@ -2304,15 +2171,15 @@ Accept wildcard characters: False ``` ### -ExceptIfHasClassification -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfHasClassification parameter specifies an exception that looks for messages with the specified message classification. You use the Get-MessageClassification cmdlet to identify the message classification. For example, to find messages with the Company Internal classification, use the following syntax: --ExceptIfHasClassification @(Get-MessageClassification "Company Internal").Identity +`-ExceptIfHasClassification @(Get-MessageClassification "Company Internal").Identity` The message classification referred to in this parameter is the custom message classification that you can create in your organization by using the New-MessageClassification cmdlet. It isn't related to the DLP data classification. @@ -2330,14 +2197,13 @@ Accept wildcard characters: False ``` ### -ExceptIfHasNoClassification -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfHasNoClassification parameter specifies an exception that looks for messages with or without any message classifications. Valid values are: - $true: Look for messages that don't have a message classification. - - $false: Look for messages that have one or more message classifications. ```yaml @@ -2354,14 +2220,15 @@ Accept wildcard characters: False ``` ### -ExceptIfHasSenderOverride -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +**Note:** This parameter is functional only in on-premises Exchange. -In on-premises Exchange, this exception is only available on Mailbox servers. +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. The ExceptIfHasSenderOverride parameter specifies an exception 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. - - $false: Don't look for messages where the sender took action to override a DLP policy. ```yaml @@ -2378,7 +2245,7 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsMessageHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2398,7 +2265,7 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2422,7 +2289,7 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesMessageHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2442,11 +2309,11 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfHeaderMatchesPatterns parameter specifies an exception that looks for text patterns in a header field by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The ExceptIfHeaderMatchesPatterns parameter specifies an exception 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 specify the header field to search by using the ExceptIfHeaderMatchesMessageHeader parameter. @@ -2464,25 +2331,20 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerAddresses -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfManagerAddresses parameter specifies the users (managers) for the ExceptIfManagerForEvaluatedUser parameter. You can use any value that uniquely identifies the user. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You specify if you want to look for these users as managers of senders or recipients by using the ExceptIfManagerForEvaluatedUser parameter. @@ -2500,14 +2362,13 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerForEvaluatedUser -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfManagerForEvaluatedUser parameter specifies an exception that looks for users in the Manager attribute of senders or recipients. Valid values are: - Recipient: The user is the manager of a recipient. - - Sender: The user is the manager of the sender. You specify the users to look for by using the ExceptIfManagerAddresses parameter. @@ -2525,40 +2386,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ExceptIfMessageContainsAllDataClassifications -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Hashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ExceptIfMessageContainsDataClassifications -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +**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. -In on-premises Exchange, this exception is only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfMessageContainsDataClassifications parameter specifies an exception that looks for sensitive information types in the body of messages, and in any attachments. -This parameter uses the syntax @{\},@{\},...@{\}. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. +This parameter uses the syntax `@{SensitiveInformationType1},@{SensitiveInformationType2},...@{SensitiveInformationTypeN}`. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. -For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). +For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). ```yaml Type: Hashtable[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2568,7 +2413,7 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageSizeOver -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2577,13 +2422,9 @@ The ExceptIfMessageSizeOver parameter specifies an exception that looks for mess When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -2602,28 +2443,20 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageTypeMatches -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfMessageTypeMatches parameter specifies an exception that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. - -- AutoForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook or Outlook). - -- Encrypted: Encrypted messages. - +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **will not** match during mail flow rule evaluation. +- Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - -- PermissionControlled: Messages that have specific permissions configured. - +- PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). - Voicemail: Voice mail messages forwarded by Unified Messaging service. - - Signed: Digitally signed messages. - -- ApprovalRequest: Moderations request messages sent to moderators. - +- ApprovalRequest: Moderation request messages sent to moderators. - ReadReceipt: Read receipts. ```yaml @@ -2640,66 +2473,40 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfRecipientADAttributeContainsWords parameter specifies an exception that looks for words in the Active Directory attributes of recipients. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -2722,66 +2529,40 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfRecipientADAttributeMatchesPatterns parameter specifies an exception that looks for text patterns in the Active Directory attributes of recipients by using regular expressions. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -2802,9 +2583,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfRecipientAddressContainsWords parameter specifies an exception that looks for words in recipient email addresses. You can specify multiple words separated by commas. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -2822,11 +2603,11 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfRecipientAddressMatchesPatterns parameter specifies an exception that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The ExceptIfRecipientAddressMatchesPatterns parameter specifies an exception 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"`. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -2844,13 +2625,13 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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. -If you want to look for recipient email addresses that contain the specified domain (for example, any subdomain of a domain), use the ExceptIfRecipientAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This exception matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". ```yaml Type: Word[] @@ -2874,7 +2655,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2884,16 +2665,13 @@ Accept wildcard characters: False ``` ### -ExceptIfSCLOver -This parameter is available or 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 doesn't include the ExceptIf prefix. +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. -This exception is available on Mailbox servers and Edge Transport servers. This condition is not available or functional in the cloud-based service due to how the service filtering stack works. +In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. The ExceptIfSCLOver parameter specifies an exception that looks for the SCL value of messages. Valid values are: - -1: The message is from a trusted sender, so the message bypasses spam filtering. - - Integers 0 through 9: A higher value indicates that a message is more likely to be spam. The rule looks for messages with an SCL value that's greater than or equal to the specified value. @@ -2902,7 +2680,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2912,66 +2690,40 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderADAttributeContainsWords parameter specifies an exception that looks for words in Active Directory attributes of message senders. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -2994,66 +2746,40 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderADAttributeMatchesPatterns parameter specifies an exception 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 - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -3074,13 +2800,13 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderDomainIs -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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. -If you want to look for sender email addresses that contain the specified domain (for example, any subdomain of a domain), use the FromAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This exception matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -3106,7 +2832,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3116,19 +2842,19 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderIpRanges -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderIpRanges parameter specifies an exception 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. - - IP address range: For example, 192.168.0.1-192.168.0.254. - - Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. -You can specify multiple IP addresses or ranges separated by commas. +You can specify multiple values separated by commas. + +In Exchange Online, the IP address that's used during evaluation of this exception is the address of the last hop before reaching the service. This IP address is not guaranteed to be the original sender's IP address, especially if third-party software is used during message transport. ```yaml Type: MultiValuedProperty @@ -3144,14 +2870,13 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderManagementRelationship -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderManagementRelationship parameter specifies an exception that looks for the relationship between the sender and recipients in messages. Valid values are: - Manager: The sender is the manager of a recipient. - - DirectReport: A recipient is the manager of the sender. ```yaml @@ -3168,25 +2893,20 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -3202,19 +2922,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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: - Name - - Distinguished name (DN) - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. @@ -3232,19 +2949,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToScope -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSentToScope parameter specifies an exception that looks for the location of a recipient. Valid values are: -- InOrganization: The recipient is a mailbox, mail user, group, or mail-enabled public folder in your organization or the recipient'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. - -- NotInOrganization: The recipients are outside your organization. The recipient's email address isn't in an accepted domain or the recipient's email address is in an accepted domain that's configured as an external relay domain. - -- ExternalPartner: The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. This value is only available in on-premises Exchange. - -- ExternalNonPartner: The recipients are external to your organization, and the organization isn't a partner organization. This value is only available in on-premises Exchange. +- InOrganization: The message was sent or received over an authenticated connection **AND** the recipient meets at least one of the following criteria: The recipient is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the recipient's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. +- NotInOrganization: The recipients are outside the organization. The recipient's email address isn't in an accepted domain or is in an accepted domain that's configured as an external relay domain in the organization. +- ExternalPartner: This value is available only in on-premises Exchange. The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. +- ExternalNonPartner: This value is available only in on-premises Exchange. The recipients are external to your organization, and the organization isn't a partner organization. ```yaml Type: ToUserScope @@ -3260,13 +2974,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. The ExceptIfSubjectContainsWords parameter specifies an exception that looks for words in the Subject field 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -3282,11 +2998,11 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfSubjectMatchesPatterns parameter specifies an exception 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: "\","\",..."\". +The ExceptIfSubjectMatchesPatterns parameter specifies an exception 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"`. ```yaml Type: Pattern[] @@ -3302,13 +3018,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -3324,11 +3042,11 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception that looks for text patterns in the Subject field or body of messages. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception 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"`. ```yaml Type: Pattern[] @@ -3344,16 +3062,14 @@ Accept wildcard characters: False ``` ### -ExceptIfWithImportance -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfWithImportance parameter specifies an exception that looks for messages with the specified importance level. Valid values are: - Low - - Normal - - High ```yaml @@ -3370,11 +3086,11 @@ Accept wildcard characters: False ``` ### -ExpiryDate -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -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". +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". ```yaml Type: DateTime @@ -3392,23 +3108,18 @@ Accept wildcard characters: False ### -From 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -3452,10 +3163,12 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The FromAddressMatchesPatterns parameter specifies a condition 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: "\","\",..."\". +The FromAddressMatchesPatterns parameter specifies a condition 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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). +**Note**: Trying to search for empty From addresses using this parameter doesn't work. + ```yaml Type: Pattern[] Parameter Sets: (All) @@ -3472,23 +3185,18 @@ Accept wildcard characters: False ### -FromMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -3512,8 +3220,7 @@ In on-premises Exchange, this condition is available on Mailbox servers and Edge The FromScope parameter specifies a condition 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. - +- InOrganization: The message was sent or received over an authenticated connection **AND** the sender meets at least one of the following criteria: The sender is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. - NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. ```yaml @@ -3532,23 +3239,18 @@ Accept wildcard characters: False ### -GenerateIncidentReport This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The GenerateIncidentReport parameter specifies where to send the incident report that's defined by the IncidentReportContent parameter. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -An incident report is generated for messages that violate a DLP policy in your organization. +**Note**: An incident report isn't generated for notifications or other incident reports that are generated by DLP or mail flow rules. ```yaml Type: RecipientIdParameter @@ -3566,29 +3268,26 @@ Accept wildcard characters: False ### -GenerateNotification This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. -The GenerateNotification parameter specifies an action that sends a notification message to recipients. For example, you can use this parameter to notify recipients that a message was rejected by the rule, or marked as spam and delivered to their Junk Email folder. +The GenerateNotification parameter specifies an action that sends a notification message to recipients that match the conditions of the rule. For example, you can use this parameter to notify recipients that a message was rejected by the rule, or marked as spam and delivered to their Junk Email folder. Each matched recipient receives a separate notification. This parameter supports plain text, HTML tags and the following keywords that use values from the original message: - %%From%% - - %%To%% - - %%Cc%% - - %%Subject%% - - %%Headers%% - - %%MessageDate%% +The maximum number of characters is 5120. + ```yaml Type: DisclaimerText Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3600,13 +3299,13 @@ Accept wildcard characters: False ### -HasClassification 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The HasClassification parameter specifies a condition that looks for messages with the specified message classification. You use the Get-MessageClassification cmdlet to identify the message classification. For example, to find messages with the Company Internal classification, use the following syntax: --HasClassification @(Get-MessageClassification "Company Internal").Identity +`-HasClassification @(Get-MessageClassification "Company Internal").Identity` The message classification referred to in this parameter is the custom message classification that you can create in your organization by using the New-MessageClassification cmdlet. It isn't related to the DLP classification. @@ -3626,12 +3325,11 @@ Accept wildcard characters: False ### -HasNoClassification 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The HasNoClassification parameter specifies a condition that looks for messages with or without any message classifications. Valid values are: - $true: Look for messages that don't have a message classification. - - $false: Look for messages that have one or more message classifications. ```yaml @@ -3648,14 +3346,15 @@ Accept wildcard characters: False ``` ### -HasSenderOverride +**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. -In on-premises Exchange, this condition is only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The HasSenderOverride parameter specifies a condition 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. - - $false: Don't look for messages where the sender took action to override a DLP policy. ```yaml @@ -3740,7 +3439,7 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The HeaderMatchesPatterns parameter specifies a condition that looks for text patterns in a header field by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The HeaderMatchesPatterns parameter specifies a condition 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 specify the header field to search by using the HeaderMatchesMessageHeader parameter. @@ -3760,32 +3459,19 @@ Accept wildcard characters: False ### -IncidentReportContent This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. -The IncidentReportContent parameter specifies the message properties that are included in the incident report that's generated when a message violates a DLP policy. Valid values are: +The IncidentReportContent parameter specifies the message properties that are included in the incident report. Valid values are: - Sender: The sender of the message. - - Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. - - Subject: The Subject field of the message. - - CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. - - BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. - - Severity: The audit severity of the rule that was triggered. If the message was processed by more than one rule, the highest severity is displayed. - -- Override: The override if the sender chose to override a PolicyTip. If the sender provided a justification, the first 100 characters of the justification is also included. - - RuleDetections: The list of rules that the message triggered. - - FalsePositive: The false positive if the sender marked the message as a false positive for a PolicyTip. - -- DataClassifications: The list of sensitive information types that were detected in the message. - - IdMatch: The sensitive information type that was detected, the exact matched content from the message, and the 150 characters before and after the matched sensitive information. - - AttachOriginalMail: The entire original message as an attachment. The message ID is always included in the incident report. @@ -3808,18 +3494,17 @@ Accept wildcard characters: False ``` ### -IncidentReportOriginalMail -This parameter is available or functional only in 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. This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. This parameter is used together with the GenerateIncidentReport parameter. Valid values are: - IncludeOriginalMail - - DoNotIncludeOriginalMail (this is the default value) ```yaml @@ -3836,29 +3521,25 @@ Accept wildcard characters: False ``` ### -LogEventText -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The LogEventText parameter specifies an action that creates an entry in the Application log on the local Edge Transport server. The value for this parameter specifies the text that you want to include in the event log entry. If the text contains spaces, enclose the value in quotation marks ("). The entry contains the following information: - Level: Information - - Source: MSExchange Messaging Policies - - Event ID: 4000 - - Task Category: Rules - -- EventData: The following message is logged by an action in the rules: \ +- EventData: `The following message is logged by an action in the rules: ` ```yaml Type: EventLogText Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3870,23 +3551,18 @@ Accept wildcard characters: False ### -ManagerAddresses 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ManagerAddresses parameter specifies the users (managers) for the ExceptIfManagerForEvaluatedUser parameter. You can use any value that uniquely identifies the user. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You specify if you want to look for these users as managers of senders or recipients by using the ManagerForEvaluatedUser parameter. @@ -3906,12 +3582,11 @@ Accept wildcard characters: False ### -ManagerForEvaluatedUser 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ManagerForEvaluatedUser parameter specifies a condition that looks for users in the Manager attribute of senders or recipients. Valid values are: - Recipient: The user is the manager of a recipient. - - Sender: The user is the manager of the sender. You specify the users to look for by using the ManagerAddresses parameter. @@ -3929,34 +3604,18 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MessageContainsAllDataClassifications -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Hashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -MessageContainsDataClassifications +**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. -In on-premises Exchange, this condition is only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The MessageContainsDataClassifications parameter specifies a condition that looks for sensitive information types in the body of messages, and in any attachments. -This parameter uses the syntax @{\},@{\},...@{\}. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. +This parameter uses the syntax `@{SensitiveInformationType1},@{SensitiveInformationType2},...@{SensitiveInformationTypeN}`. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. -For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). +For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). You can specify the notification options by using the NotifySender parameter. @@ -3964,7 +3623,7 @@ 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, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3983,13 +3642,9 @@ The MessageSizeOver parameter specifies a condition that looks for messages larg When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -4010,26 +3665,18 @@ Accept wildcard characters: False ### -MessageTypeMatches 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The MessageTypeMatches parameter specifies a condition that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. - -- AutoForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook or Outlook). - -- Encrypted: Encrypted messages. - +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **will not** match during mail flow rule evaluation. +- Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - -- PermissionControlled: Messages that have specific permissions configured. - +- PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). - Voicemail: Voice mail messages forwarded by Unified Messaging service. - - Signed: Digitally signed messages. - -- ApprovalRequest: Moderations request messages sent to moderators. - +- ApprovalRequest: Moderation request messages sent to moderators. - ReadReceipt: Read receipts. ```yaml @@ -4048,10 +3695,8 @@ Accept wildcard characters: False ### -Mode 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 any action is taken on the message that would impact delivery. - -- AuditAndNotify: The rule operates the same as in Audit mode, but notifications are also enabled. - +- 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. +- AuditAndNotify: 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 and GenerateNotification actions occur. - Enforce: All actions specified in the rule are taken. This is the default value. ```yaml @@ -4070,12 +3715,11 @@ Accept wildcard characters: False ### -ModerateMessageByManager This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ModerateMessageByManager parameter specifies an action that forwards messages for approval to the user that's specified in the sender's Manager attribute. After the manager approves the message, it's delivered to the recipients. Valid values are: - $true: Moderation by the sender's manager is enabled. - - $false: Moderation by the sender's manager is disabled. This action only works if the sender's Manager attribute is defined. @@ -4096,23 +3740,18 @@ Accept wildcard characters: False ### -ModerateMessageByUser This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ModerateMessageByUser parameter specifies an action that forwards messages for approval to the specified users. After one of the users approves the message, it's delivered to the recipients. You can use ay value that uniquely identifies the user. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You can't use a distribution group as a moderator. @@ -4130,31 +3769,31 @@ Accept wildcard characters: False ``` ### -NotifySender +**Note:** This parameter is functional only in on-premises Exchange. + This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The NotifySender parameter specifies an action that notifies the sender when messages violate DLP policies. Valid values are: - NotifyOnly: The sender is notified, but the message is delivered normally. - - RejectMessage: The message is rejected, and the sender is notified. - - RejectUnlessFalsePositiveOverride: The message is rejected unless it's marked as a false positive by the sender. - - RejectUnlessSilentOverride: The message is rejected unless the sender has chosen to override the policy restriction. - - RejectUnlessExplicitOverride: This is the same as RejectUnlessSilentOverride, but the sender can also provide a justification for overriding the policy restriction. For all values except NotifyOnly, you can specify an enhanced status code and a rejection reason by using the RejectMessageEnhancedStatusCode and RejectMessageReasonText parameters. The default enhanced status code is 5.7.1, and the default rejection reason is Delivery not authorized, message refused. If you use this parameter, you also need to specify a condition that looks for sensitive information types in messages by using the MessageContainsDataClassifications parameter. +This action is applicable to messages sent by internal users only. External senders will not receive notifications. + ```yaml Type: NotifySenderType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -4168,7 +3807,7 @@ 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. -The PrependSubject parameter specifies an action that adds text to add to the beginning of the Subject field of messages. The value for this parameter is the text that you want to add. If the text contains spaces, enclose the value in quotation marks (")\> +The PrependSubject parameter specifies an action that adds text to add to the beginning of the Subject field of messages. The value for this parameter is the text that you want to add. 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. @@ -4191,9 +3830,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a new rule (the 9th rule) are from 0 through 8. - - The default value for a new rule (the 9th rule) is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -4214,19 +3851,20 @@ Accept wildcard characters: False ### -Quarantine This parameter specifies an action or part of an action for the rule. -This action is available only on Edge Transport servers in on-premises Exchange. +In on-premises Exchange, this action is available only on Edge Transport servers. The Quarantine parameter specifies an action that quarantines messages. - In on-premises Exchange, messages are delivered to the quarantine mailbox that you've configured as part of Content filtering. If the quarantine mailbox isn't configured, the message is returned to the sender in an NDR. +- In Microsoft 365, messages are delivered to the hosted quarantine. -- In Office 365, messages are delivered to the hosted quarantine. +If this action is in a rule that's not the last rule in the list, rule evaluation stops after this rule is run. When the message is released from quarantine, the remaining rules in the list aren't evaluated. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4238,64 +3876,38 @@ Accept wildcard characters: False ### -RecipientADAttributeContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The RecipientADAttributeContainsWords parameter specifies a condition that looks for words in the Active Directory attributes of recipients. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -4320,64 +3932,38 @@ Accept wildcard characters: False ### -RecipientADAttributeMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The RecipientADAttributeMatchesPatterns parameter specifies a condition that looks for text patterns in the Active Directory attributes of recipients by using regular expressions. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -4400,7 +3986,7 @@ Accept wildcard characters: False ### -RecipientAddressContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The RecipientAddressContainsWords parameter specifies a condition that looks for words in recipient email addresses. You can specify multiple words separated by commas. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -4420,9 +4006,9 @@ Accept wildcard characters: False ### -RecipientAddressMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The RecipientAddressMatchesPatterns parameter specifies a condition that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The RecipientAddressMatchesPatterns parameter specifies a condition 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"`. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -4439,14 +4025,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RecipientAddressType +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: + +- Original: The rule checks the original address in the To field of the message. +- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This is the default value. + +```yaml +Type: RecipientAddressType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RecipientDomainIs 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The RecipientDomainIs parameter specifies a condition that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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. -If you want to look for recipient email addresses that contain the specified domain (for example, any subdomain of a domain), use the RecipientAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This condition matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". ```yaml Type: Word[] @@ -4470,7 +4077,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4487,18 +4094,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The RedirectMessageTo parameter specifies a rule action that redirects messages to the specified recipients. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -4516,7 +4118,7 @@ Accept wildcard characters: False ### -RejectMessageEnhancedStatusCode This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The RejectMessageEnhancedStatusCode parameter specifies the enhanced status code that's used when the rule rejects messages. Valid values are 5.7.1 or between 5.7.900 and 5.7.999. @@ -4542,10 +4144,14 @@ Accept wildcard characters: False ### -RejectMessageReasonText This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The RejectMessageReasonText parameter specifies the explanation text that's used when the rule rejects messages. If the value contains spaces, enclose the value in quotation marks ("). +In Exchange 2013 or later, the maximum number of characters is 256. + +In the cloud-based service, the maximum number of characters is 1024. + You can use this parameter with the NotifySender parameter for a custom non-delivery report (also known as an NDR or bounce message). If you use this parameter with the RejectMessageEnhancedStatusCode parameter, the custom explanation text value is set to "Delivery not authorized, message refused". @@ -4590,10 +4196,9 @@ This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. -The RemoveOME parameter specifies an action that removes the previous version of Office 365 Message Encryption from messages and their attachments. Valid values are: +The RemoveOME parameter specifies an action that removes the previous version of Microsoft Purview Message Encryption from messages and their attachments. Valid values are: - $true: The message and attachments are decrypted. - - $false: The message and attachments aren't decrypted. ```yaml @@ -4614,10 +4219,9 @@ This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. -The RemoveOMEv2 parameter specifies an action that removes Office 365 Message Encryption from messages and their attachments. Valid values are: +The RemoveOMEv2 parameter specifies an action that removes Microsoft Purview Message Encryption from messages and their attachments. Valid values are: - $true: The message and attachments are decrypted. - - $false: The message and attachments aren't decrypted. ```yaml @@ -4633,17 +4237,40 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RemoveRMSAttachmentEncryption +This parameter is available only in the cloud-based service. + +This parameter specifies an action or part of an action for the rule. + +The RemoveRMSAttachmentEncryption parameter specifies an action that removes Microsoft Purview Message Encryption from encrypted attachments in email. The attachments were already encrypted before they were attached to the message. The message itself doesn't need to be encrypted. Valid values are: + +- $true: The encrypted attachments are decrypted. +- $false: The encrypted attachments aren't decrypted. + + This parameter also requires the value $true for the RemoveOMEv2 parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RouteMessageOutboundConnector This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. -The RouteMessageOutboundConnector parameter specifies an action that routes messages through the specified Outbound connector in Office 365. You can use any value that uniquely identifies the connector. For example: +The RouteMessageOutboundConnector parameter specifies an action that routes messages through the specified Outbound connector in Microsoft 365. You can use any value that uniquely identifies the connector. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -4662,12 +4289,11 @@ Accept wildcard characters: False ### -RouteMessageOutboundRequireTls This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The RouteMessageOutboundRequireTls parameter specifies an action that uses Transport Layer Security (TLS) encryption to deliver messages outside your organization. Valid values are: - $true: The messages must be delivered over a TLS encrypted channel. - - $false: A TLS encrypted channel isn't required to deliver the messages. ```yaml @@ -4687,7 +4313,6 @@ Accept wildcard characters: False 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. - - Defer: The message is deferred so the rules engine can attempt to process the message again. ```yaml @@ -4706,9 +4331,8 @@ Accept wildcard characters: False ### -RuleSubType The RuleSubType parameter specifies the rule type. Valid values are: -- Dlp: The rule is associated with a DLP policy. - -- None: The rule is a regular rule that isn't associated with a DLP policy. +- Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange. +- None: The rule is a regular transport rule. This is the default value. ```yaml Type: RuleSubType @@ -4724,16 +4348,13 @@ Accept wildcard characters: False ``` ### -SCLOver -This parameter is available or 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. -This exception is available on Mailbox servers and Edge Transport servers. This condition is not available or functional in the cloud-based service due to how the service filtering stack works. +In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. The SCLOver parameter specifies a condition that looks for the SCL value of messages. Valid values are: - -1: The message is from a trusted sender, so the message bypasses spam filtering. - - Integers 0 through 9: A higher value indicates that a message is more likely to be spam. The rule looks for messages with an SCL value that's greater than or equal to the specified value. @@ -4742,7 +4363,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4754,64 +4375,38 @@ Accept wildcard characters: False ### -SenderADAttributeContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderADAttributeContainsWords parameter specifies a condition that looks for words in Active Directory attributes of message senders. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -4836,64 +4431,38 @@ Accept wildcard characters: False ### -SenderADAttributeMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderADAttributeMatchesPatterns parameter specifies a condition 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 - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -4916,22 +4485,16 @@ Accept wildcard characters: False ### -SenderAddressLocation 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, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). - +- 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). - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - - HeaderOrEnvelope: Examine senders in the message header and the message envelope. -Note that message envelope searching is only available for the following conditions and exceptions: +Message envelope searching is available only for the following conditions and exceptions: - From and ExceptIfFrom - - FromAddressContainsWords and ExceptIfFromAddressContainsWords - - FromAddressMatchesPatterns and ExceptIfFromAddressMatchesPatterns - - FromMemberOf and ExceptIfFromMemberOf - - SenderDomainIs and ExceptIfSenderDomainIs ```yaml @@ -4950,11 +4513,11 @@ Accept wildcard characters: False ### -SenderDomainIs 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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. -If you want to look for sender email addresses that contain the specified domain (for example, any subdomain of a domain), use the FromAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This condition matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -4980,7 +4543,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4992,17 +4555,17 @@ Accept wildcard characters: False ### -SenderIpRanges 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderIpRanges parameter specifies a condition 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. - - IP address range: For example, 192.168.0.1-192.168.0.254. - - Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. -You can specify multiple IP addresses or ranges separated by commas. +You can specify multiple values separated by commas. + +In Exchange Online, the IP address that's used during evaluation of this condition is the address of the last hop before reaching the service. This IP address is not guaranteed to be the original sender's IP address, especially if third-party software is used during message transport. ```yaml Type: MultiValuedProperty @@ -5020,12 +4583,11 @@ Accept wildcard characters: False ### -SenderManagementRelationship 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderManagementRelationship parameter specifies a condition that looks for the relationship between the sender and recipients in messages. Valid values are: - Manager: The sender is the manager of a recipient. - - DirectReport: A recipient is the manager of the sender. ```yaml @@ -5044,23 +4606,18 @@ Accept wildcard characters: False ### -SentTo 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -5078,23 +4635,18 @@ Accept wildcard characters: False ### -SentToMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. @@ -5114,17 +4666,14 @@ Accept wildcard characters: False ### -SentToScope 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SentToScope parameter specifies a condition that looks for the location of recipients. Valid values are: -- InOrganization: The recipient is a mailbox, mail user, group, or mail-enabled public folder in your organization or the recipient'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. - -- NotInOrganization: The recipients are outside your organization. The recipient's email address isn't in an accepted domain or the recipient's email address is in an accepted domain that's configured as an external relay domain. - -- ExternalPartner: The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. This value is only available in on-premises Exchange. - -- ExternalNonPartner: The recipients are external to your organization, and the organization isn't a partner organization. This value is only available in on-premises Exchange. +- InOrganization: The message was sent or received over an authenticated connection **AND** the recipient meets at least one of the following criteria: The recipient is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the recipient's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. +- NotInOrganization: The recipients are outside the organization. The recipient's email address isn't in an accepted domain or is in an accepted domain that's configured as an external relay domain in the organization. +- ExternalPartner: This value is available only in on-premises Exchange. The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. +- ExternalNonPartner: This value is available only in on-premises Exchange. The recipients are external to your organization, and the organization isn't a partner organization. ```yaml Type: ToUserScope @@ -5142,16 +4691,13 @@ Accept wildcard characters: False ### -SetAuditSeverity This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The SetAuditSeverity parameter specifies an action that sets the severity level of the incident report and the corresponding entry that's written to the message tracking log when messages violate DLP policies. Valid values are: - DoNotAudit: No audit entry is logged. - - Low: The audit entry is assigned low severity. - - Medium: The audit entry is assigned medium severity. - - High: The audit entry is assigned high severity. ```yaml @@ -5215,7 +4761,6 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The SetSCL parameter specifies an action that adds or modifies the SCL value of messages. Valid values are: - -1: The message is from a trusted sender, so the message bypasses spam filtering. - - Integers 0 through 9: A higher value indicates that a message is more likely to be spam. ```yaml @@ -5232,9 +4777,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectStatusCode -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The SmtpRejectMessageRejectStatusCode parameter specifies an action that disconnects the sending server from the Edge Transport server. The value of this parameter is the SMTP code that's used. Valid values are the integers 400 through 500. @@ -5244,7 +4789,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5254,9 +4799,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectText -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The SmtpRejectMessageRejectText parameter specifies an action that disconnects the sending server from the Edge Transport server. The value of this parameter is the explanation text that's used. If the value contains spaces, enclose the value in quotation marks ("). @@ -5266,7 +4811,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5283,7 +4828,6 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The StopRuleProcessing parameter specifies an action that stops processing more rules. Valid values are: - $true: Stop processing more rules. - - $false: Continue processing more rules after this one. ```yaml @@ -5306,7 +4850,9 @@ In on-premises Exchange, this condition is available on Mailbox servers and Edge The SubjectContainsWords parameter specifies a condition that looks for words in the Subject field 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -5326,7 +4872,7 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The SubjectMatchesPatterns parameter specifies a condition 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: "\","\",..."\". +The SubjectMatchesPatterns parameter specifies a condition 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"`. ```yaml Type: Pattern[] @@ -5348,7 +4894,9 @@ In on-premises Exchange, this condition is available on Mailbox servers and Edge The SubjectOrBodyContainsWords parameter specifies a condition 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -5368,7 +4916,7 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The SubjectOrBodyMatchesPatterns parameter specifies a condition that looks for text patterns in the Subject field or body of messages. You can specify multiple text patterns by using the following syntax: "\","\",..."\". +The SubjectOrBodyMatchesPatterns parameter specifies a condition 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"`. ```yaml Type: Pattern[] @@ -5387,7 +4935,6 @@ Accept wildcard characters: False 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. - - $false: Regular expression syntax that's compatible with Exchange 2013 or later. ```yaml @@ -5422,14 +4969,12 @@ Accept wildcard characters: False ### -WithImportance 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The WithImportance parameter specifies a condition that looks for messages with the specified importance level. Valid values are: - Low - - Normal - - High ```yaml @@ -5450,12 +4995,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/New-UMAutoAttendant.md b/exchange/exchange-ps/exchange/New-UMAutoAttendant.md similarity index 83% rename from exchange/exchange-ps/exchange/unified-messaging/New-UMAutoAttendant.md rename to exchange/exchange-ps/exchange/New-UMAutoAttendant.md index f9754c4a23..7f9922c4c4 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/New-UMAutoAttendant.md +++ b/exchange/exchange-ps/exchange/New-UMAutoAttendant.md @@ -1,29 +1,35 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/new-umautoattendant -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-UMAutoAttendant ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the New-UMAutoAttendant cmdlet to create a Unified Messaging (UM) auto attendant. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-UMAutoAttendant [-Name] -UMDialPlan [-Confirm] [-DomainController ] - [-DTMFFallbackAutoAttendant ] [-PilotIdentifierList ] [-SpeechEnabled ] [-Status ] +New-UMAutoAttendant [-Name] -UMDialPlan + [-Confirm] + [-DomainController ] + [-DTMFFallbackAutoAttendant ] + [-PilotIdentifierList ] + [-SpeechEnabled ] + [-Status ] ``` ## DESCRIPTION @@ -31,7 +37,7 @@ The New-UMAutoAttendant cmdlet creates one or more UM auto attendants. UM auto a After this task is completed, a UM auto attendant is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,7 +64,7 @@ The Name parameter specifies the display name for the UM auto attendant. The dis Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -74,7 +80,7 @@ The UMDialPlan parameter specifies the UM dial plan identifier for the UM dial p Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -86,15 +92,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -104,15 +109,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -128,7 +131,7 @@ The DTMFFallbackAutoAttendant parameter specifies a secondary UM auto attendant. Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -144,7 +147,7 @@ The PilotIdentifierList parameter specifies a list of one or more pilot numbers. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -160,7 +163,7 @@ The SpeechEnabled parameter specifies whether the UM auto attendant is speech-en Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -173,14 +176,13 @@ Accept wildcard characters: False The Status parameter specifies whether the UM auto attendant being created will be enabled. Valid values are: - Enabled - - Disabled (This is the default value) ```yaml Type: StatusEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -196,7 +198,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -210,12 +212,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/New-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/New-UMCallAnsweringRule.md similarity index 82% rename from exchange/exchange-ps/exchange/unified-messaging/New-UMCallAnsweringRule.md rename to exchange/exchange-ps/exchange/New-UMCallAnsweringRule.md index 438bcbad14..4fa9e1f46e 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/New-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/exchange/New-UMCallAnsweringRule.md @@ -1,56 +1,59 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/new-umcallansweringrule -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-UMCallAnsweringRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the New-UMCallAnsweringRule cmdlet to create a call answering rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-UMCallAnsweringRule -Name [-CallerIds ] - [-CallersCanInterruptGreeting ] [-CheckAutomaticReplies ] [-Confirm] - [-DomainController ] [-ExtensionsDialed ] [-KeyMappings ] - [-Mailbox ] [-Priority ] [-ScheduleStatus ] [-TimeOfDay ] - [-WhatIf] [] +New-UMCallAnsweringRule -Name + [-CallerIds ] + [-CallersCanInterruptGreeting ] + [-CheckAutomaticReplies ] + [-Confirm] + [-DomainController ] + [-ExtensionsDialed ] + [-KeyMappings ] + [-Mailbox ] + [-Priority ] + [-ScheduleStatus ] + [-TimeOfDay ] + [-WhatIf] + [] ``` ## DESCRIPTION The New-UMCallAnsweringRule cmdlet creates a Unified Messaging (UM) call answering rule stored in a UM-enabled user's mailbox. You can run the cmdlet and create a call answering rule of the user that's logged on or use the Mailbox parameter to specify the mailbox where you want the call answering rule to be created. You can use the New-UMCallAnsweringRule cmdlet to specify the following conditions: - Who the incoming call is from - - Time of day - - Calendar free/busy status - - Whether automatic replies are turned on for email You can also specify the following actions: - Find me - - Transfer the caller to someone else - - Leave a voice message After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,9 +72,7 @@ New-UMCallAnsweringRule -Name MyCallAnsweringRule -CallerIds "1,4255550100,,","1 This example creates the following actions on the call answering rule MyCallAnsweringRule in the mailbox for tonysmith: - Sets the call answering rule to two caller IDs. - - Sets the priority of the call answering rule to 2. - - Sets the call answering rule to allow callers to interrupt the greeting. ### Example 3 @@ -89,13 +90,11 @@ New-UMCallAnsweringRule -Name MyCallAnsweringRule -Priority 2 -Mailbox tonysmith This example creates the call answering rule MyCallAnsweringRule in the mailbox tonysmith and performs the following actions: - Sets the priority of the call answering rule to 2. - - Creates key mappings for the call answering rule. If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can: - Press the 1 key and be transferred to a receptionist at extension 45678. - - Press the 2 key and the Find Me feature will be used for urgent issues and ring extension 23456 first, and then 45671. ### Example 5 @@ -106,7 +105,6 @@ New-UMCallAnsweringRule -Name MyCallAnsweringRule -Priority 2 -Mailbox tonysmith This example creates the call answering rule MyCallAnsweringRule in the mailbox for tonysmith and performs the following actions: - Sets the priority of the call answering rule to 2. - - If the caller reaches voice mail during working hours, the caller is asked to call back later. ### Example 6 @@ -117,7 +115,6 @@ New-UMCallAnsweringRule -Name MyCallAnsweringRule -Priority 2 -Mailbox tonysmith This example creates the call answering rule MyCallAnsweringRule in the mailbox for tonysmith with a custom period for the time of day and performs the following actions: - Sets the priority of the call answering rule to 2. - - If the caller reaches voice mail and the time is between 8:00 A.M. and 12:00 P.M. on Tuesday, ask the caller to call back later. ## PARAMETERS @@ -129,7 +126,7 @@ The Name parameter specifies the name of the Unified Messaging (UM) call answeri Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -145,7 +142,7 @@ The CallerIds parameter specifies an entry for the "If the Caller is" condition. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -161,7 +158,7 @@ The CallersCanInterruptGreeting parameter specifies whether a caller can interru Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -177,7 +174,7 @@ The CheckAutomaticReplies parameter specifies an entry for the "If My Automatic Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -189,15 +186,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -207,15 +203,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -231,7 +225,7 @@ The ExtensionsDialed parameter specifies an entry for the "If the Caller Dials" Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -247,7 +241,7 @@ The KeyMappings parameter specifies a key mapping entry for a call answering rul Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -257,26 +251,17 @@ Accept wildcard characters: False ``` ### -Mailbox -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: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the mailbox of the user who is running the command is used. @@ -285,7 +270,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -301,7 +286,7 @@ The Priority parameter specifies the order that the call answering rule will be Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -314,13 +299,9 @@ Accept wildcard characters: False 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 - - Free = 0x1 - - Tentative = 0x2 - - Busy = 0x4 - - OutOfOffice = 0x8 The default setting is $null. @@ -329,7 +310,7 @@ The default setting is $null. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -345,7 +326,7 @@ The TimeOfDay parameter specifies an entry for the "If the Call Arrives During" Type: TimeOfDay Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -361,7 +342,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -375,12 +356,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/New-UMDialPlan.md b/exchange/exchange-ps/exchange/New-UMDialPlan.md similarity index 82% rename from exchange/exchange-ps/exchange/unified-messaging/New-UMDialPlan.md rename to exchange/exchange-ps/exchange/New-UMDialPlan.md index 3a471422a7..5b47dbb7ad 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/New-UMDialPlan.md +++ b/exchange/exchange-ps/exchange/New-UMDialPlan.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/new-umdialplan -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-UMDialPlan ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the New-UMDialPlan cmdlet to create a Unified Messaging (UM) dial plan to establish a link between UM IP gateways, UM hunt groups, and Mailbox servers to enable communication between Unified Messaging components. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,13 +25,13 @@ New-UMDialPlan [-Name] -CountryOrRegionCode -NumberOfDigitsInE [-AccessTelephoneNumbers ] [-Confirm] [-DefaultLanguage ] - [-DefaultOutboundCallingLineId ] [-DomainController ] [-FaxEnabled ] [-GenerateUMMailboxPolicy ] [-URIType ] [-VoIPSecurity ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -42,7 +41,7 @@ After the new UM dial plan is created, a UM IP gateway and a Mailbox server must After this task is completed, a new UM dial plan is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,33 +68,33 @@ This example creates the unsecured UM dial plan MyUMDialPlan that supports E.164 ## PARAMETERS -### -CountryOrRegionCode -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. +### -Name +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, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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. +### -CountryOrRegionCode +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, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -108,7 +107,7 @@ The NumberOfDigitsInExtension parameter specifies the fixed number of digits in Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -124,7 +123,7 @@ The AccessTelephoneNumbers parameter specifies the telephone number or numbers u Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -136,15 +135,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -160,25 +158,7 @@ The DefaultLanguage parameter specifies the default language of the system. This Type: UMLanguage Parameter Sets: (All) 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 -``` - -### -DefaultOutboundCallingLineId -This parameter is available or functional only in Exchange Server 2010. - -The DefaultOutboundCallingLineId parameter specifies the phone number that a Unified Messaging server would use as the calling line ID when placing an outbound call. By default, this is set to $null and only the extension number of the UM-enabled user that places the outbound call is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -188,15 +168,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -212,7 +190,7 @@ The FaxEnabled parameter specifies whether the Mailbox servers associated with t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -228,7 +206,7 @@ The GenerateUMMailboxPolicy parameter specifies whether a default UM mailbox pol Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -244,7 +222,7 @@ The URIType parameter specifies the URI type to be sent and received with SIP me Type: UMURIType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -254,15 +232,13 @@ Accept wildcard characters: False ``` ### -VoIPSecurity -This parameter is available only in on-premises Exchange. - 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, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -278,7 +254,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -292,12 +268,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/New-UMHuntGroup.md b/exchange/exchange-ps/exchange/New-UMHuntGroup.md similarity index 83% rename from exchange/exchange-ps/exchange/unified-messaging/New-UMHuntGroup.md rename to exchange/exchange-ps/exchange/New-UMHuntGroup.md index 003864db6e..c471f60d1e 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/New-UMHuntGroup.md +++ b/exchange/exchange-ps/exchange/New-UMHuntGroup.md @@ -1,30 +1,32 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/new-umhuntgroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-UMHuntGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the New-UMHuntGroup cmdlet to create a Unified Messaging (UM) hunt group used to link incoming calls to a specific UM dial plan. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` New-UMHuntGroup [-Name] -UMDialPlan -UMIPGateway - [-Confirm] [-DomainController ] [-PilotIdentifier ] - [-WhatIf] [] + [-Confirm] + [-DomainController ] + [-PilotIdentifier ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -32,7 +34,7 @@ The New-UMHuntGroup cmdlet creates a UM hunt group in Active Directory. Running After this task is completed, a new UM hunt group is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,7 +61,7 @@ The Name parameter specifies the UM hunt group name used for display purposes. T Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -75,7 +77,7 @@ The UMDialPlan parameter specifies the UM dial plan used with the UM hunt group. Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -91,7 +93,7 @@ The UMIPGateway parameter specifies the UM IP gateway to be associated with the Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -103,15 +105,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -121,15 +122,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -145,7 +144,7 @@ The PilotIdentifier parameter specifies the number string used to uniquely ident Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -161,7 +160,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -175,12 +174,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/New-UMIPGateway.md b/exchange/exchange-ps/exchange/New-UMIPGateway.md similarity index 82% rename from exchange/exchange-ps/exchange/unified-messaging/New-UMIPGateway.md rename to exchange/exchange-ps/exchange/New-UMIPGateway.md index 32efb1bd0d..3e03d94273 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/New-UMIPGateway.md +++ b/exchange/exchange-ps/exchange/New-UMIPGateway.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/new-umipgateway -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-UMIPGateway @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the New-UMIPGateway cmdlet to create a Unified Messaging (UM) IP gateway. A UM IP gateway is used to connect Unified Messaging servers to an IP gateway or a Session Initiation Protocol (SIP)-enabled IP Private Branch eXchange (PBX). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,10 +24,10 @@ For information about the parameter sets in the Syntax section below, see [Excha New-UMIPGateway [-Name] -Address [-Confirm] [-DomainController ] - [-GlobalCallRoutingScheme ] [-IPAddressFamily ] [-UMDialPlan ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -36,7 +35,7 @@ A UM IP gateway has organization-wide scope and references a single physical IP This cmdlet is scheduled to be removed from Exchange Online on December 1, 2019. For more information, see this [blog post](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/New-date-for-discontinuation-of-support-for-Session-Border/ba-p/607853). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,33 +62,33 @@ This example creates the UM IP gateway MyUMIPGateway that enables a Mailbox serv ## PARAMETERS -### -Address -The Address parameter specifies the IP address configured on the IP gateway or SIP-enabled IP PBX. +### -Name +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: UMSmartHost +Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -Name -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. +### -Address +The Address parameter specifies the IP address configured on the IP gateway or SIP-enabled IP PBX. ```yaml -Type: String +Type: UMSmartHost Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -98,15 +97,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -124,25 +122,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GlobalCallRoutingScheme -This parameter is available or functional only in Exchange Server 2010. - -The GlobalCallRoutingScheme parameter specifies whether the IP gateway can accept calls for UM-enabled users and auto attendant numbers included in the global routing database. If the value is E.164, the IP gateway accepts the call. - -```yaml -Type: UMGlobalCallRoutingScheme -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -155,16 +135,14 @@ Accept wildcard characters: False 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. - - IPv6Only: The UM IP gateway will only use IPv6. - - Any: IPv6 will be used first, and then if necessary, it will fall back to IPv4. ```yaml Type: IPAddressFamily Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -180,7 +158,7 @@ The UMDialPlan parameter specifies the UM dial plan to be associated with the UM Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -196,7 +174,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -210,12 +188,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/New-UMMailboxPolicy.md b/exchange/exchange-ps/exchange/New-UMMailboxPolicy.md similarity index 75% rename from exchange/exchange-ps/exchange/unified-messaging/New-UMMailboxPolicy.md rename to exchange/exchange-ps/exchange/New-UMMailboxPolicy.md index 4c72b61483..3ab4d1f26f 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/New-UMMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/New-UMMailboxPolicy.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/new-ummailboxpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # New-UMMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the New-UMMailboxPolicy cmdlet to create a Unified Messaging (UM) mailbox policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,8 +24,8 @@ For information about the parameter sets in the Syntax section below, see [Excha New-UMMailboxPolicy [-Name] -UMDialPlan [-Confirm] [-DomainController ] - [-SharedUMDialPlan] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -34,7 +33,7 @@ The New-UMMailboxPolicy cmdlet creates a UM mailbox policy that has organization After this task is completed, a new UM mailbox policy is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,7 +53,7 @@ The Name parameter specifies the display name for the UM mailbox policy. The nam Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -70,7 +69,7 @@ The UMDialPlan parameter specifies the identifier for the UM dial plan to be ass Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -82,15 +81,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -100,33 +98,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharedUMDialPlan -This parameter is available or functional only in Exchange Server 2010. - -The SharedUMDialPlan parameter specifies whether the new UM mailbox policy being created is linked or associated with a dial plan outside the scope of the organization. If you specify this parameter, the UM mailbox policy can be linked with another tenant's dial plan. This parameter is used during tenant provisioning and is only used in a data center. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -142,7 +120,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -156,12 +134,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/New-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/New-UnifiedAuditLogRetentionPolicy.md new file mode 100644 index 0000000000..2196b0f833 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-UnifiedAuditLogRetentionPolicy.md @@ -0,0 +1,232 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-UnifiedAuditLogRetentionPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-UnifiedAuditLogRetentionPolicy cmdlet to create audit log retention policies in the Microsoft Defender portal or the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-UnifiedAuditLogRetentionPolicy [-Name] -Priority -RetentionDuration + [-Confirm] + [-Description ] + [-Operations ] + [-RecordTypes ] + [-UserIds ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Audit log retention policies are used to specify a retention duration for audit logs for that are generated by admin and user activity. An audit log retention policy can specify the retention duration based on the type of audited activities, the Microsoft 365 service that activities are performed in, or the users who performed the activities. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-UnifiedAuditLogRetentionPolicy -Name "Microsoft Teams Audit Policy" -Description "One year retention policy for all Microsoft Teams activities" -RecordTypes MicrosoftTeams -RetentionDuration TwelveMonths -Priority 100 +``` + +This example creates an audit log retention policy that retains all audit logs related to Microsoft Teams events for one year. + +### Example 2 +```powershell +New-UnifiedAuditLogRetentionPolicy -Name "SearchQueryPerformed by app@sharepoint" -Description "90 day retention policy for noisy SharePoint events" -RecordTypes SharePoint -Operations SearchQueryPerformed -UserIds "app@sharepoint" -RetentionDuration ThreeMonths -Priority 10000 +``` + +This example creates an audit log retention policy that retains all audit logs for the SearchQueryPerformed activity performed by the app@sharepoint service account for 90 days. + +## PARAMETERS + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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. + +Any custom audit log retention policy that you create will take precedence over the default audit log retention policy. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies how long audit log records are kept. Valid values are: + +- ThreeMonths +- SixMonths +- NineMonths +- TwelveMonths +- TenYears + +```yaml +Type: UnifiedAuditLogRetentionDuration +Parameter Sets: (All) +Aliases: +Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths, TenYears +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Operations +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"`. + +If you use this parameter, you must also use the RecordTypes parameter to specify the record type. You can't use this parameter if you've specified more than one value for the RecordTypes parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordTypes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIds +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-UnifiedGroup.md b/exchange/exchange-ps/exchange/New-UnifiedGroup.md new file mode 100644 index 0000000000..7490a242d1 --- /dev/null +++ b/exchange/exchange-ps/exchange/New-UnifiedGroup.md @@ -0,0 +1,721 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# New-UnifiedGroup + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the New-UnifiedGroup cmdlet to create Microsoft 365 Groups in your cloud-based organization. To add members, owners, and subscribers to Microsoft 365 Groups, use the Add-UnifiedGroupLinks cmdlet. + +**Note**: You can't use this cmdlet to create Microsoft 365 Groups if you connect using certificate based authentication (also known as CBA or app-only authentication for unattended scripts) or Azure managed identity. You can use Microsoft Graph instead. For more information, see [Create group](https://learn.microsoft.com/graph/api/group-post-groups). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +New-UnifiedGroup [-DisplayName ] + [-AccessType ] + [-MailboxRegion ] + [-Alias ] + [-AlwaysSubscribeMembersToCalendarEvents] + [-AutoSubscribeNewMembers] + [-Classification ] + [-Confirm] + [-DataEncryptionPolicy ] + [-EmailAddresses ] + [-ExecutingUser ] + [-ExoErrorAsWarning] + [-HiddenGroupMembershipEnabled] + [-IsMemberAllowedToEditContent ] + [-Language ] + [-ManagedBy ] + [-Members ] + [-Name ] + [-Notes ] + [-Owner ] + [-PrimarySmtpAddress ] + [-RequireSenderAuthenticationEnabled ] + [-SensitivityLabelId ] + [-SuppressWarmupMessage] + [-WhatIf] + [] +``` + +### ProvisioningOptions +``` +New-UnifiedGroup [-DisplayName ] + [-AccessType ] + [-Alias ] + [-AlwaysSubscribeMembersToCalendarEvents] + [-AutoSubscribeNewMembers] + [-Classification ] + [-Confirm] + [-DataEncryptionPolicy ] + [-EmailAddresses ] + [-ExecutingUser ] + [-ExoErrorAsWarning] + [-HiddenGroupMembershipEnabled] + [-Language ] + [-ManagedBy ] + [-Members ] + [-Name ] + [-Notes ] + [-Owner ] + [-PrimarySmtpAddress ] + [-RequireSenderAuthenticationEnabled ] + [-SensitivityLabelId ] + [-SuppressWarmupMessage] + [-WhatIf] + [] +``` + +### SegmentationOption +``` +New-UnifiedGroup [-DisplayName ] + [-SubscriptionEnabled] + [-AccessType ] + [-Alias ] + [-AlwaysSubscribeMembersToCalendarEvents] + [-AutoSubscribeNewMembers] + [-Classification ] + [-Confirm] + [-DataEncryptionPolicy ] + [-EmailAddresses ] + [-ExecutingUser ] + [-ExoErrorAsWarning] + [-HiddenGroupMembershipEnabled] + [-Language ] + [-ManagedBy ] + [-Members ] + [-Name ] + [-Notes ] + [-Owner ] + [-PrimarySmtpAddress ] + [-RequireSenderAuthenticationEnabled ] + [-SensitivityLabelId ] + [-SuppressWarmupMessage] + [-WhatIf] + [] +``` + +### DlMigration +``` +New-UnifiedGroup -DlIdentity + [-ConvertClosedDlToPrivateGroup] + [-DeleteDlAfterMigration] + [-Confirm] + [-ExecutingUser ] + [-ManagedBy ] + [-Members ] + [-Owner ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-UnifiedGroup -DisplayName "Engineering Department" -Alias "engineering" +``` + +This example creates a new Microsoft 365 Group named Engineering Department. + +## PARAMETERS + +### -DisplayName +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. + +```yaml +Type: String +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlIdentity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +All the properties and membership of the distribution group are copied to the Microsoft 365 Group. + +The alias and proxy addresses of the distribution group are moved to the Microsoft 365 Group, and are replaced on the distribution group by the values `DLMigrated_`. The original proxy addresses are copied to the ExtensionCustomAttribute5 property of the distribution group. + +Microsoft 365 Groups don't have ReportToManager and ReportToOriginator parameters, so the values of these parameters aren't migrated from the distribution group to the Microsoft 365 Group. The Microsoft 365 Group behaves as if the default values of these parameters were set (ReportToManager is $false and ReportToOriginator is $true). In other words, delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the message sender and not to the owner of the Microsoft 365 Group. + +```yaml +Type: DistributionGroupIdParameter +Parameter Sets: DlMigration +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessType +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. +- Private: The group content and conversations are available only to members of the group, and joining the group requires approval from a group owner. + +You can change the privacy type at any point in the lifecycle of the group. + +**Note**: Although a user needs to be a member to participate in a private group, anyone can send email to a private group, and receive replies from the private group. + +```yaml +Type: ModernGroupTypeInfo +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Alias +The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the 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: + +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. + +If you don't use the Alias parameter when you create a Microsoft 365 Group, the value of the DisplayName parameter is used for the Alias value. Spaces are removed, unsupported characters are converted to question marks (?), and numbers may be added to maintain the uniqueness of the Alias value. + +When you create a Microsoft 365 Group without using the EmailAddresses parameter, the Alias value is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. + +The Alias value is appended with the ExternalDirectoryObjectId property value and used as the Name property value for the Microsoft 365 Group (`_`). + +```yaml +Type: String +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlwaysSubscribeMembersToCalendarEvents +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. +- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false`, all future members that are added to the group will have their subscriptions set to ReplyOnly. + +Group members can change their own subscription settings, which can override your intended use of this switch. + +The AutoSubscribeNewMembers switch overrides this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoSubscribeNewMembers +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Classification +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConvertClosedDlToPrivateGroup +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. + +If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group will always be migrated to a private Microsoft 365 Group. For open distribution groups, the migrated Microsoft 365 Group is always public, not private. + +You can only use this switch with the DlIdentity parameter. + +```yaml +Type: SwitchParameter +Parameter Sets: DlMigration +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DataEncryptionPolicy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: Identity, SegmentationOption, ProvisioningOptions +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeleteDlAfterMigration +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. + +```yaml +Type: SwitchParameter +Parameter Sets: DlMigration +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailAddresses +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: + +- SMTP: The primary SMTP address. You can use this value only once in a command. +- smtp: Other SMTP email addresses. +- SPO: SharePoint email address. + +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. + +To specify the primary SMTP email address, you can use any of the following methods: + +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. +- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. + +```yaml +Type: ProxyAddressCollection +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExecutingUser +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExoErrorAsWarning +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenGroupMembershipEnabled +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). + +**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa. In addition, any Microsoft 365 Groups with this setting will not be supported in sensitivity labeling policies. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsMemberAllowedToEditContent +{{ Fill IsMemberAllowedToEditContent Description }} + +```yaml +Type: System.Boolean +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Language +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). + +```yaml +Type: CultureInfo +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxRegion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedBy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Members +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 (`_`). + +```yaml +Type: String +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Notes +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Owner +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireSenderAuthenticationEnabled +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. +- $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. + +```yaml +Type: Boolean +Parameter Sets: Identity, ProvisioningOptions, SegmentationOption +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SensitivityLabelId +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. + +```yaml +Type: System.Guid +Parameter Sets: Identity, SegmentationOption, ProvisioningOptions +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubscriptionEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SuppressWarmupMessage +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/New-WebServicesVirtualDirectory.md b/exchange/exchange-ps/exchange/New-WebServicesVirtualDirectory.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access-servers/New-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/exchange/New-WebServicesVirtualDirectory.md index 2b3937042d..f99ae64e15 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/New-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/New-WebServicesVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-webservicesvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-WebServicesVirtualDirectory @@ -19,25 +18,41 @@ Use the New-WebServicesVirtualDirectory cmdlet to create Exchange Web Services v You can create multiple virtual directories by using this cmdlet. However, you can create only one Exchange Web Services virtual directory for each website. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-WebServicesVirtualDirectory [-ApplicationRoot ] [-AppPoolId ] - [-AppPoolIdForManagement ] [-BasicAuthentication ] [-Confirm] - [-DigestAuthentication ] [-DomainController ] - [-ExtendedProtectionFlags ] [-ExtendedProtectionSPNList ] - [-ExtendedProtectionTokenChecking ] [-ExternalUrl ] [-Force] - [-GzipLevel ] [-InternalNLBBypassUrl ] [-InternalUrl ] - [-MRSProxyEnabled ] [-MRSProxyMaxConnections ] [-Path ] - [-WebSiteName ] [-WhatIf] [-WindowsAuthentication ] - [-WSSecurityAuthentication ] [-OAuthAuthentication ] - [-Role ] [-Server ] [] +New-WebServicesVirtualDirectory [-ApplicationRoot ] + [-AppPoolId ] + [-AppPoolIdForManagement ] + [-BasicAuthentication ] + [-Confirm] + [-DigestAuthentication ] + [-DomainController ] + [-ExtendedProtectionFlags ] + [-ExtendedProtectionSPNList ] + [-ExtendedProtectionTokenChecking ] + [-ExternalUrl ] + [-Force] + [-GzipLevel ] + [-InternalNLBBypassUrl ] + [-InternalUrl ] + [-MRSProxyEnabled ] + [-MRSProxyMaxConnections ] + [-OAuthAuthentication ] + [-Path ] + [-Role ] + [-Server ] + [-WebSiteName ] + [-WhatIf] + [-WindowsAuthentication ] + [-WSSecurityAuthentication ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,7 +61,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-WebServicesVirtualDirectory -WebSiteName "www.contoso.com" -ExternalUrl "https://www.contoso.com/webservices.aspx" ``` -This example creates a virtual directory under the non-default website www.contoso.com. It also sets the external URL to https://www.contoso.com/webservices.aspx. +This example creates a virtual directory under the non-default website www.contoso.com. It also sets the external URL to `https://www.contoso.com/webservices.aspx`. ## PARAMETERS @@ -102,7 +117,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. ```yaml @@ -121,8 +135,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -142,7 +155,6 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. - - $false: Digest authentication is disabled. This is the default value. ```yaml @@ -178,13 +190,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -204,8 +212,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -224,14 +231,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -265,7 +268,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -284,11 +289,8 @@ Accept wildcard characters: False The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are: - Off: No compression. - - Low: Static compression only. This is the default value. This value has the same result as the Off value, because Exchange Web Services content is dynamic. - - High: Static and dynamic compression. Content from Exchange Web Services is compressed if clients indicate support for Gzip compression in their requests. - - Error: Identifies errors in the Gzip compression configuration. ```yaml @@ -341,7 +343,7 @@ Accept wildcard characters: False ``` ### -MRSProxyEnabled -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://docs.microsoft.com/Exchange/recipients/mailbox-moves). +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 @@ -357,9 +359,9 @@ Accept wildcard characters: False ``` ### -MRSProxyMaxConnections -This parameter is available or functional only in 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://docs.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). +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)). ```yaml Type: Unlimited @@ -374,14 +376,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Path -The Path parameter sets the path of the virtual directory in the metabase. +### -OAuthAuthentication +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. +- $false: OAuth authentication is disabled. ```yaml -Type: String +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -390,8 +395,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WebSiteName -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. +### -Path +The Path parameter sets the path of the virtual directory in the metabase. ```yaml Type: String @@ -406,14 +411,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -Role +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. +- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. + +Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. ```yaml -Type: SwitchParameter +Type: VirtualDirectoryRole Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -422,35 +432,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WindowsAuthentication -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. +### -Server +The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example: -- $false: Integrated Windows authentication is disabled. +- Name +- FQDN +- Distinguished name (DN) +- ExchangeLegacyDN ```yaml -Type: Boolean +Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -WSSecurityAuthentication -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. - -- $false: WS-Security authentication is disabled. +### -WebSiteName +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: Boolean +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -462,18 +469,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OAuthAuthentication -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. - -- $false: OAuth authentication is disabled. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: Boolean +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -482,20 +485,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Role -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. - -- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. +### -WindowsAuthentication +The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. +- $true: Integrated Windows authentication is enabled. This is the default value. +- $false: Integrated Windows authentication is disabled. ```yaml -Type: VirtualDirectoryRole +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -504,27 +504,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Server -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 - -- FQDN - -- Distinguished name (DN) +### -WSSecurityAuthentication +The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are: -- ExchangeLegacyDN +- $true: WS-Security authentication is enabled. This is the default value. +- $false: WS-Security authentication is disabled. ```yaml -Type: ServerIdParameter +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -533,12 +528,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/New-X400AuthoritativeDomain.md b/exchange/exchange-ps/exchange/New-X400AuthoritativeDomain.md similarity index 92% rename from exchange/exchange-ps/exchange/mail-flow/New-X400AuthoritativeDomain.md rename to exchange/exchange-ps/exchange/New-X400AuthoritativeDomain.md index c0f0404dfb..c18e6668eb 100644 --- a/exchange/exchange-ps/exchange/mail-flow/New-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/exchange/New-X400AuthoritativeDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-x400authoritativedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # New-X400AuthoritativeDomain @@ -17,24 +16,25 @@ This cmdlet is available only in on-premises Exchange. Use the New-X400AuthoritativeDomain cmdlet to create and specify the X.400 authoritative domain for the organization. The X.400 authoritative domain defines the standard fields for the namespace appended to the recipient identity for all mailboxes assigned an X.400 address. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -New-X400AuthoritativeDomain [-Name] -X400DomainName [-Confirm] [-DomainController ] - [-WhatIf] [-X400ExternalRelay ] [] +New-X400AuthoritativeDomain [-Name] -X400DomainName + [-Confirm] + [-DomainController ] + [-WhatIf] + [-X400ExternalRelay ] + [] ``` ## DESCRIPTION X.400 domain names can only include the following ASCII characters: - A to Z - - a to z - - 0-9 - - These punctuation and special characters: (space) ' () + , - . / : = ? You can use the following X.400 attributes (one each per address): @@ -42,34 +42,29 @@ You can use the following X.400 attributes (one each per address): country - Abbreviation: C - - Maximum character length: 2 administrative domain - Abbreviation: A - - Maximum character length: 16 private domain - Abbreviation: P - - Maximum character length: 16 organization name - Abbreviation: O - - Maximum character length: 64 organizational unit name - Abbreviation: OU1 to OU4 - - Maximum character length: 32 -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -109,19 +104,12 @@ Accept wildcard characters: False 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) - - A (ADMD) - - P (PRMD) - - O (Organization) - - OU1 (Organization unit 1) - - OU2 (Organization unit 2) - - OU3 (Organization unit 3) - - OU4 (Organization unit 4) Separate the address attributes with semicolons and enclose the entire address in quotation marks (for example, "C=US;A=att;P=Contoso;O=Sales"). @@ -142,8 +130,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -214,12 +201,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Preview-QuarantineMessage.md b/exchange/exchange-ps/exchange/Preview-QuarantineMessage.md new file mode 100644 index 0000000000..655b0da6f5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Preview-QuarantineMessage.md @@ -0,0 +1,115 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Preview-QuarantineMessage + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Preview-QuarantineMessage cmdlet to preview the contents of quarantined messages in your cloud-based organization. This cmdlet doesn't work on files that were quarantined by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Preview-QuarantineMessage -Identity + [-EntityType ] + [-RecipientAddress ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-QuarantineMessage -MessageID <5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com> | Preview-QuarantineMessage +``` + +This example previews the quarantined message with the Message-ID value `<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>`. + +### Example 2 +```powershell +Preview-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 +``` + +This example previews the quarantined message that has the specified Identity value. + +## PARAMETERS + +### -Identity +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. + +```yaml +Type: QuarantineMessageIdentity +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -EntityType +The EntityType parameter filters the results by EntityType. Valid values are: + +- Email +- SharePointOnline +- Teams (currently in Preview) +- DataLossPrevention + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Redirect-Message.md b/exchange/exchange-ps/exchange/Redirect-Message.md similarity index 91% rename from exchange/exchange-ps/exchange/mail-flow/Redirect-Message.md rename to exchange/exchange-ps/exchange/Redirect-Message.md index b14c751c54..1a0354a5bc 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Redirect-Message.md +++ b/exchange/exchange-ps/exchange/Redirect-Message.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/redirect-message +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Redirect-Message @@ -17,13 +16,14 @@ This cmdlet is available only in on-premises Exchange. Use the Redirect-Message cmdlet to drain the active messages from all the delivery queues on a Mailbox server, and transfer those messages to another Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Redirect-Message -Server -Target - [-Confirm] [-WhatIf] + [-Confirm] + [-WhatIf] [] ``` @@ -31,12 +31,10 @@ Redirect-Message -Server -Target When a message queue is drained, the active messages in the queues on the source Mailbox server are routed to the target Mailbox server. After the messages are received and queued by the target Mailbox server, the messages are made redundant. Other considerations include the following: - Only active messages are drained. Shadow queues aren't drained. - - Messages in the poison message queue aren't drained. - - The source server won't accept new messages while the queues are drained. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,11 +51,8 @@ This example drains the active messages from the delivery queues on the Mailbox 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -92,8 +87,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,12 +124,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Release-QuarantineMessage.md b/exchange/exchange-ps/exchange/Release-QuarantineMessage.md new file mode 100644 index 0000000000..17f3d5590b --- /dev/null +++ b/exchange/exchange-ps/exchange/Release-QuarantineMessage.md @@ -0,0 +1,369 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Release-QuarantineMessage + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Release-QuarantineMessage cmdlet to release messages from quarantine in your cloud-based organization. You can release messages to all original recipients, or to specific recipients. + +For files that were quarantined by Safe Attachments for SharePoint, OneDrive, and Microsoft Teams, you can unblock the files in the respective team sites and document libraries by using the Release-QuarantineMessage cmdlet so users can access, share, and download the files. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### OrgReleaseToUser +``` +Release-QuarantineMessage -User [-Identities ] + [-Identity ] + [-AllowSender] + [-Confirm] + [-EntityType ] + [-Force] + [-ReportFalsePositive] + [-WhatIf] + [] +``` + +### OrgReleaseToAll +``` +Release-QuarantineMessage [-Identities ] [-Identity ] + [-ReleaseToAll] + [-AllowSender] + [-Confirm] + [-EntityType ] + [-Force] + [-ReportFalsePositive] + [-WhatIf] + [] +``` + +### Identities +``` +Release-QuarantineMessage -Identities + [-Identity ] + [-ActionType ] + [-AllowSender] + [-Confirm] + [-EntityType ] + [-Force] + [-ReportFalsePositive] + [-WhatIf] + [] +``` + +### IdentityOnly +``` +Release-QuarantineMessage -Identity + [-AllowSender] + [-Confirm] + [-EntityType ] + [-Force] + [-ReportFalsePositive] + [-WhatIf] + [] +``` + +## DESCRIPTION +Consider the following scenario: john@gmail.com sends a message to faith@contoso.com and john@subsidiary.contoso.com. Gmail bifurcates this message into two copies that are both routed to quarantine as phishing in Microsoft. An admin releases both of these messages to admin@contoso.com. The first released message that reaches the admin mailbox is delivered. The second released message is identified as duplicate delivery and is skipped. Message are identified as duplicates if they have the same message ID and received time. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-QuarantineMessage -MessageID "<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>" | Release-QuarantineMessage -User julia@contoso.com +``` + +This example uses the Get-QuarantineMessage cmdlet to release the quarantined message with the Message-ID value `<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>` to an original recipient julia@contoso.com. + +### Example 2 +```powershell +Release-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 -ReleaseToAll +``` + +This example releases the quarantined message with the specified Identity value to all original recipients. + +### Example 3 +```powershell +Get-QuarantineMessage | Release-QuarantineMessage -ReleaseToAll +``` + +This example releases all messages to all original recipients. + +### Example 4 +```powershell +$q = Get-QuarantineMessage -QuarantineTypes SPOMalware + +$q[-1] | Release-QuarantineMessage -ReleaseToAll +``` + +This example releases a file that was quarantined as part of Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. The first command stores all quarantined files in the variable $q. The second command releases the last file in the list. For more information about elements in arrays and index numbers, see [Accessing and Using Array Elements](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_arrays#accessing-and-using-array-elements). + +## PARAMETERS + +### -Identities +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. + +When you use this parameter, the Identity parameter is required, but the value is ignored. For example, use the value 000 for the Identity parameter. + +```yaml +Type: QuarantineMessageIdentity[] +Parameter Sets: Identities +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: QuarantineMessageIdentity[] +Parameter Sets: OrgReleaseToAll, OrgReleaseToUser +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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 +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +```yaml +Type: QuarantineMessageIdentity +Parameter Sets: IdentityOnly +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -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. + +If you previously used the User parameter or the ReleaseToAll switch to release the quarantined message to some or all of the original recipients, those recipients are skipped when you use the ReleaseToAll switch again. + +You can't use the ReleaseToAll switch and the User parameter in the same command. + +```yaml +Type: SwitchParameter +Parameter Sets: OrgReleaseToAll +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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. + +If you previously used the ReleaseToAll switch to release the quarantined message to all original recipients, and you later release the message again with the User parameter, any original recipients you specify with the User parameter are skipped. + +```yaml +Type: String[] +Parameter Sets: OrgReleaseToUser +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActionType +The ActionType parameter specifies the release action type. Valid values are: + +- Deny +- Release: Use this value to release messages or approve requests to release messages. +- Request + +```yaml +Type: ReleaseActionType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSender +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntityType +The EntityType parameter filters the results by EntityType. Valid values are: + +- Email +- SharePointOnline +- Teams (currently in Preview) +- DataLossPrevention + +```yaml +Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportFalsePositive +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this 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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/active-directory/Remove-ADPermission.md b/exchange/exchange-ps/exchange/Remove-ADPermission.md similarity index 83% rename from exchange/exchange-ps/exchange/active-directory/Remove-ADPermission.md rename to exchange/exchange-ps/exchange/Remove-ADPermission.md index ca28a89e11..13ca24fb1e 100644 --- a/exchange/exchange-ps/exchange/active-directory/Remove-ADPermission.md +++ b/exchange/exchange-ps/exchange/Remove-ADPermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/remove-adpermission +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ADPermission @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ADPermission cmdlet to remove permissions from an Active Directory object. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,7 +32,8 @@ Remove-ADPermission [-Identity] -User ] [-InheritedObjectType ] [-Properties ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Owner @@ -41,30 +41,31 @@ Remove-ADPermission [-Identity] -User [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Instance ``` -Remove-ADPermission -Instance +Remove-ADPermission [[-Identity] ] -Instance [-AccessRights ] [-ChildObjectTypes ] [-Confirm] [-Deny] [-DomainController ] [-ExtendedRights ] - [[-Identity] ] [-InheritanceType ] [-InheritedObjectType ] [-Properties ] [-User ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors) Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://docs.microsoft.com/Exchange/permissions/permissions). +The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -132,7 +133,29 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the user object that will have permissions removed. +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 +- Mail users +- Security groups + +For the best results, we recommend using the following values: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) ```yaml Type: SecurityPrincipalIdParameter @@ -161,46 +184,30 @@ Accept wildcard characters: False ``` ### -AccessRights -The AccessRights parameter specifies the rights needed to perform the operation. Valid values include: +The AccessRights parameter specifies the rights that you want to remove from the user on the Active Directory object. Valid values include: - CreateChild - - DeleteChild - - ListChildren - - Self - - ReadProperty - - WriteProperty - - DeleteTree - - ListObject - - ExtendedRight - - Delete - - ReadControl - - GenericExecute - - GenericWrite - - GenericRead - - WriteDacl - - WriteOwner - - GenericAll - - Synchronize - - AccessSystemSecurity +You can specify multiple values separated by commas. + ```yaml Type: ActiveDirectoryRights[] Parameter Sets: (All) @@ -235,8 +242,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -253,7 +259,7 @@ Accept wildcard characters: False ``` ### -Deny -The Deny switch specifies whether the permission to remove is a deny permission. +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 @@ -303,7 +309,13 @@ Accept wildcard characters: False ``` ### -InheritanceType -The InheritanceType parameter specifies whether permissions are inherited. +The InheritanceType parameter specifies how permissions are inherited. Valid values are: + +- None +- All (this is the default value) +- Children +- Descendents [sic] +- SelfAndChildren ```yaml Type: ActiveDirectorySecurityInheritance @@ -373,12 +385,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Remove-ATPProtectionPolicyRule.md new file mode 100644 index 0000000000..47ada3944f --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ATPProtectionPolicyRule.md @@ -0,0 +1,114 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ATPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-ATPProtectionPolicyRule cmdlet to remove rules from Microsoft Defender for Office 365 protections in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. + +**Note**: Use this cmdlet to remove a rule only if you plan to immediately recreate the rule using the New-ATPProtectionPolicyRule cmdlet. The affected preset security policy won't function without a corresponding rule. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ATPProtectionPolicyRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +This example removes the existing rule for Defender for Office 365 protections in the Standard preset security policy. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to remove. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-AcceptedDomain.md b/exchange/exchange-ps/exchange/Remove-AcceptedDomain.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Remove-AcceptedDomain.md rename to exchange/exchange-ps/exchange/Remove-AcceptedDomain.md index 2aeb6ba34e..5339aa412e 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-AcceptedDomain.md +++ b/exchange/exchange-ps/exchange/Remove-AcceptedDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-accepteddomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-AcceptedDomain @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-AcceptedDomain cmdlet to remove an accepted domain. When you remove an accepted domain, the accepted domain object is deleted. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AcceptedDomain [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-AcceptedDomain [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +61,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDevice.md b/exchange/exchange-ps/exchange/Remove-ActiveSyncDevice.md similarity index 87% rename from exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDevice.md rename to exchange/exchange-ps/exchange/Remove-ActiveSyncDevice.md index d95292965b..5ec58a6bb4 100644 --- a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDevice.md +++ b/exchange/exchange-ps/exchange/Remove-ActiveSyncDevice.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-activesyncdevice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-ActiveSyncDevice @@ -17,21 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-ActiveSyncDevice cmdlet to remove mobile device partnerships that identify the devices that are configured to synchronize with user mailboxes. -Note: In Exchange 2013 or later, use the Remove-MobileDevice cmdlet instead. If you have scripts that use Remove-ActiveSyncDevice, update them to use Remove-MobileDevice. +**Note**: In Exchange 2013 or later, use the Remove-MobileDevice cmdlet instead. If you have scripts that use Remove-ActiveSyncDevice, update them to use Remove-MobileDevice. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ActiveSyncDevice [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-ActiveSyncDevice [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Remove-ActiveSyncDevice cmdlet is useful for removing mobile devices that no longer synchronize successfully with the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,8 +79,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -133,12 +134,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceAccessRule.md similarity index 89% rename from exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceAccessRule.md index 89614b21ad..5e56ff683d 100644 --- a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceAccessRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-activesyncdeviceaccessrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-ActiveSyncDeviceAccessRule @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-ActiveSyncDeviceAccessRule cmdlet to remove any existing device access rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ActiveSyncDeviceAccessRule [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-ActiveSyncDeviceAccessRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION If you've created device access rules for groups of devices, you can use the Remove-ActiveSyncDeviceAccessRule cmdlet to remove any access rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,8 +70,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,12 +125,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDeviceClass.md b/exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceClass.md similarity index 89% rename from exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDeviceClass.md rename to exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceClass.md index 5d7a791310..fee0ac4e53 100644 --- a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncDeviceClass.md +++ b/exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceClass.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-activesyncdeviceclass +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ActiveSyncDeviceClass @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ActiveSyncDeviceClass cmdlet to clean up the list of mobile devices synchronizing with Microsoft Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ActiveSyncDeviceClass [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-ActiveSyncDeviceClass [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Remove-ActiveSyncDeviceClass cmdlet cleans up the list of devices that are associated with your organization. Mobile phones and devices that are inactive or have been remote wiped are removed from the list and the Microsoft Exchange ActiveSync process regenerates the list with the current mobile phones and devices. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/exchange/Remove-ActiveSyncMailboxPolicy.md similarity index 84% rename from exchange/exchange-ps/exchange/devices/Remove-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/exchange/Remove-ActiveSyncMailboxPolicy.md index 5c7a75f2e5..faa170542f 100644 --- a/exchange/exchange-ps/exchange/devices/Remove-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-ActiveSyncMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-activesyncmailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-ActiveSyncMailboxPolicy @@ -17,21 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-ActiveSyncMailboxPolicy cmdlet to remove mobile device mailbox policies. -Note: In Exchange 2013 or later, use the Remove-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use Remove-ActiveSyncMailboxPolicy, update them to use Remove-MobileDeviceMailboxPolicy. +**Note**: In Exchange 2013 or later, use the Remove-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use Remove-ActiveSyncMailboxPolicy, update them to use Remove-MobileDeviceMailboxPolicy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ActiveSyncMailboxPolicy [-Identity] [-Confirm] [-DomainController ] - [-Force] [-WhatIf] [] +Remove-ActiveSyncMailboxPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION A mobile device mailbox policy is a group of settings that specifies how mobile phones connect to Exchange. Exchange supports multiple mobile device mailbox policies. If any users are assigned to the policy when you attempt to remove it, the command fails. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,9 +58,7 @@ This example removes the mobile device mailbox policy named Management and bypas 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 - - Distinguished name (DN) - - GUID ```yaml @@ -76,8 +77,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -112,7 +112,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -148,12 +150,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-ActiveSyncVirtualDirectory.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-ActiveSyncVirtualDirectory.md index a4696b0bb1..a45a5a2bd8 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-ActiveSyncVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-activesyncvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ActiveSyncVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ActiveSyncVirtualDirectory cmdlet to remove existing Exchange ActiveSync virtual directories from Internet Information Services (IIS) virtual directories on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,13 +24,14 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-ActiveSyncVirtualDirectory [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION When the Exchange ActiveSync virtual directory is removed from a specified server and website, the virtual directory is also removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,13 +61,11 @@ This example removes a custom Exchange ActiveSync virtual directory from the ser ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -85,8 +83,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -139,12 +136,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-AdaptiveScope.md b/exchange/exchange-ps/exchange/Remove-AdaptiveScope.md new file mode 100644 index 0000000000..6716aabc5e --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AdaptiveScope.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AdaptiveScope + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-AdaptiveScope cmdlet to remove adaptive scopes from your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AdaptiveScope [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-AdaptiveScope -Identity "Project X" +``` + +This example removes the adaptive scope named Project X. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-AddressBookPolicy.md b/exchange/exchange-ps/exchange/Remove-AddressBookPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-AddressBookPolicy.md rename to exchange/exchange-ps/exchange/Remove-AddressBookPolicy.md index 3bafef468f..f2bac7b9a2 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-AddressBookPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AddressBookPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/remove-addressbookpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-AddressBookPolicy @@ -17,23 +16,26 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-AddressBookPolicy cmdlet to delete an address book policy. You can't remove the address book policy if it's still assigned to a user's mailbox. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AddressBookPolicy [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-AddressBookPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You can't delete an address book policy if it's assigned to a user. To determine if an address book policy is assigned to a user, run the following command: +You can't delete an address book policy if it's assigned to a user. To determine if an address book policy is assigned to a user, replace the example value Murchison's Class with the name of the ABP and run the following command: -Get-Mailbox | where $._AddressBookPolicy -eq "Murchison's Class"} +`Get-Mailbox -ResultSize unlimited -Filter "AddressBookPolicy -eq '$((Get-AddressBookPolicy "Murchison's Class").DistinguishedName)'"` -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-AddressList.md b/exchange/exchange-ps/exchange/Remove-AddressList.md similarity index 88% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-AddressList.md rename to exchange/exchange-ps/exchange/Remove-AddressList.md index 953cfb7235..a77eb38489 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-AddressList.md +++ b/exchange/exchange-ps/exchange/Remove-AddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/remove-addresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-AddressList @@ -17,25 +16,28 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-AddressList cmdlet to remove existing address lists. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AddressList [-Identity] [-Confirm] [-DomainController ] [-Recursive] - [-WhatIf] [] +Remove-AddressList [-Identity] + [-Confirm] + [-DomainController ] + [-Recursive] + [-WhatIf] + [] ``` ## DESCRIPTION You can use the Remove-AddressList cmdlet with the Get-AddressList cmdlet in the following scenarios: - Use the Get-AddressList cmdlet to get address list information, and then pipe the output to the Format-List cmdlet to get the GUID, distinguished name (DN), or path and name of an existing address list. - - Use the Get-AddressList cmdlet to get a specific existing address list, and then pipe the output directly to the Remove-AddressList cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,12 +54,9 @@ This example removes the address list named AddressList1 and all of its child ad 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 - - Distinguished name (DN) - - GUID - -- Path: (\\\) or [\\\\) +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) If the address list has child address lists that you also want to remove, you need to use the Recursive switch. @@ -77,8 +76,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -151,12 +149,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-AddressRewriteEntry.md b/exchange/exchange-ps/exchange/Remove-AddressRewriteEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/mail-flow/Remove-AddressRewriteEntry.md rename to exchange/exchange-ps/exchange/Remove-AddressRewriteEntry.md index 7a4ba7b826..8eb9950d2e 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-AddressRewriteEntry.md +++ b/exchange/exchange-ps/exchange/Remove-AddressRewriteEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-addressrewriteentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-AddressRewriteEntry @@ -17,13 +16,16 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Remove-AddressRewriteEntry cmdlet to remove an existing address rewrite entry that's no longer needed on an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AddressRewriteEntry [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-AddressRewriteEntry [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -46,9 +48,7 @@ Get-AddressRewriteEntry | Where {$_.InternalAddress -like '*contoso.com'} | Remo This example removes all address rewrite entries that include contoso.com in the domain name. It accomplishes the following: - Retrieves all address rewrite entries. - - Filters the result for entries that have contoso.com or its subdomains as the internal address. - - Removes the filtered entries. ## PARAMETERS @@ -72,8 +72,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -128,12 +127,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/Remove-AntiPhishPolicy.md new file mode 100644 index 0000000000..6bff81fad7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AntiPhishPolicy.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AntiPhishPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-AntiPhishPolicy cmdlet to remove antiphish policies from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AntiPhishPolicy [-Identity] + [-Confirm] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-AntiPhishPolicy -Identity "Quarantine Policy" +``` + +This example removes the antiphish policy named Quarantine Policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: AntiPhishPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-AntiPhishRule.md b/exchange/exchange-ps/exchange/Remove-AntiPhishRule.md new file mode 100644 index 0000000000..77562bbd26 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AntiPhishRule.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AntiPhishRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-AntiPhishRule cmdlet to remove antiphish rules from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AntiPhishRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-AntiPhishRule -Identity "Research Department Phishing Rule" +``` + +This examples removes the antiphish rule named Research Department Phishing Rule. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Remove-App.md b/exchange/exchange-ps/exchange/Remove-App.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Remove-App.md rename to exchange/exchange-ps/exchange/Remove-App.md index 00ee5bec56..c24c1658e5 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-App.md +++ b/exchange/exchange-ps/exchange/Remove-App.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-app +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-App @@ -17,19 +16,26 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-App cmdlet to uninstall an app. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-App [-Identity] [-Confirm] [-DomainController ] [-Mailbox ] - [-OrganizationApp] [-WhatIf] [-PrivateCatalog] [] +Remove-App [-Identity] + [-AppType ] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-OrganizationApp] + [-PrivateCatalog] + [-WhatIf] + [] ``` ## DESCRIPTION The Remove-App cmdlet requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet. Apps installed by default can't be uninstalled, but they can be disabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,11 +64,28 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -AppType +This parameter is available only in the cloud-based service. + +{{ Fill AppType Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -100,23 +123,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -133,7 +147,9 @@ Accept wildcard characters: False ``` ### -OrganizationApp -The OrganizationApp parameter specifies that the scope of the app is organizational. This is set to $false by default. This parameter is required if the targeted app is installed for the organization. +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. ```yaml Type: SwitchParameter @@ -148,14 +164,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -PrivateCatalog +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: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -164,14 +180,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -PrivateCatalog -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. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. 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 +Aliases: wi +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -185,12 +201,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Remove-AppRetentionCompliancePolicy.md new file mode 100644 index 0000000000..c470a3f9f2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AppRetentionCompliancePolicy.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AppRetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-AppRetentionCompliancePolicy to remove app retention compliance policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AppRetentionCompliancePolicy [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-AppRetentionCompliancePolicy -Identity "Contoso Viva Engage" +``` + +This example removes the app retention compliance policy named Contoso Viva Engage. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-AppRetentionComplianceRule.md b/exchange/exchange-ps/exchange/Remove-AppRetentionComplianceRule.md new file mode 100644 index 0000000000..724cda7063 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AppRetentionComplianceRule.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AppRetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-AppRetentionComplianceRule to remove app retention compliance rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AppRetentionComplianceRule [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-AppRetentionComplianceRule -Identity "Contoso Viva Engage" +``` + +This example removes the app retention compliance policy rule Contoso Viva Engage. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/Remove-ApplicationAccessPolicy.md new file mode 100644 index 0000000000..9b1bae6a1a --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ApplicationAccessPolicy.md @@ -0,0 +1,104 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ApplicationAccessPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-ApplicationAccessPolicy cmdlet to remove application access policies. These changes may take up to 30 minutes to go live. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ApplicationAccessPolicy [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ApplicationAccessPolicy -Identity "596ade3a-1abe-4c5b-b7d5-a169c4b05d4a\7a774f0c-7a6f-11e0-85ad-07fb4824019b:S-1-5-21-724521725-2336880675-2689004279-1821338;8b6ce428-cca2-459a-ac50-d38bcc932258" +``` + +This example removes the specified policy. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-AttachmentFilterEntry.md b/exchange/exchange-ps/exchange/Remove-AttachmentFilterEntry.md similarity index 89% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-AttachmentFilterEntry.md rename to exchange/exchange-ps/exchange/Remove-AttachmentFilterEntry.md index 78a00b75ee..a166c59fe8 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-AttachmentFilterEntry.md +++ b/exchange/exchange-ps/exchange/Remove-AttachmentFilterEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-attachmentfilterentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-AttachmentFilterEntry @@ -17,17 +16,20 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Remove-AttachmentFilterEntry cmdlet to remove an entry from the attachment filter list that's used by the Attachment Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AttachmentFilterEntry [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-AttachmentFilterEntry [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-attachmentfilterlistconfig). +On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://learn.microsoft.com/powershell/module/exchange/set-attachmentfilterlistconfig). On Edge Transport servers, you need to be a member of the local Administrators group to run this cmdlet. @@ -53,7 +55,6 @@ This example removes the attachment filter entry that filters attachments that h 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. - - FileName: This value matches the attachment filter entry against the simple file name. In Type:Name, Name can be either the file name of the attachment filter entry to be removed, or the content type of the attachment filter entry to be removed. @@ -74,8 +75,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,12 +130,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-AuthRedirect.md b/exchange/exchange-ps/exchange/Remove-AuthRedirect.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-AuthRedirect.md rename to exchange/exchange-ps/exchange/Remove-AuthRedirect.md index 6c06d01050..5472c1ac64 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-AuthRedirect.md +++ b/exchange/exchange-ps/exchange/Remove-AuthRedirect.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-authredirect +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-AuthRedirect @@ -17,23 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-AuthRedirect cmdlet to remove OAuth redirection objects that are used for legacy Microsoft Exchange 2010 Client Access servers in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AuthRedirect [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-AuthRedirect [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Remove-AuthRedirect AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE +Remove-AuthRedirect -Identity AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE ``` This example removes the existing OAuth redirection object named AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE. @@ -48,7 +50,7 @@ This example removes all existing OAuth redirection objects from your organizati ## PARAMETERS ### -Identity -The Identity parameter specifies the existing OAuth redirection object that you want to remove. The object name uses the syntax AuthRedirect-Bearer-\. The easiest way to find the name of the OAuth redirection object is to run Get-AuthRedirect. +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 @@ -66,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -120,12 +121,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Remove-AuthServer.md b/exchange/exchange-ps/exchange/Remove-AuthServer.md similarity index 88% rename from exchange/exchange-ps/exchange/organization/Remove-AuthServer.md rename to exchange/exchange-ps/exchange/Remove-AuthServer.md index cfe243012b..826c25a07f 100644 --- a/exchange/exchange-ps/exchange/organization/Remove-AuthServer.md +++ b/exchange/exchange-ps/exchange/Remove-AuthServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/remove-authserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-AuthServer @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-AuthServer cmdlet to remove an authorization server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AuthServer [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-AuthServer [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,9 +46,7 @@ This example removes the authorization server named AMC. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -65,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md new file mode 100644 index 0000000000..7881265a05 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -0,0 +1,164 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AuthenticationPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-AuthenticationPolicy cmdlet to remove authentication policies from your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AuthenticationPolicy [-Identity] + [-Confirm] + [-AllowLegacyExchangeTokens] + [-TenantId ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-AuthenticationPolicy -Identity "Engineering Group" +``` + +This example removes the authentication policy named "Engineering Group". + +### Example 2 +```powershell +Remove-AuthenticationPolicy -Identity "LegacyExchangeTokens" -AllowLegacyExchangeTokens +``` + +In Exchange Online, this example enables legacy Exchange tokens to be issued to Outlook add-ins. This switch applies to the entire organization. The Identity parameter is required, and its value must be set to "LegacyExchangeTokens". Specific authentication policies can't be applied. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the authentication policy you want to remove. You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: AuthPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLegacyExchangeTokens +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. + +Legacy Exchange tokens include Exchange user identity and callback tokens. + +This switch applies to the entire organization. The Identity parameter is required, and its value must be set to "LegacyExchangeTokens". Specific authentication policies can't be applied. + +**Important**: + +- Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- It might take up to 24 hours for the change to take effect across your entire organization. +- Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization will remain valid until they expire. +- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantId +This parameter is available only in the cloud-based service. + +{{ Fill TenantId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelPolicy.md new file mode 100644 index 0000000000..d6b2940550 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelPolicy.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AutoSensitivityLabelPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-AutoSensitivityLabelPolicy cmdlet to remove auto-labeling policies from your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AutoSensitivityLabelPolicy [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-AutoSensitivityLabelPolicy -Identity "Marketing Group" +``` + +This example removes the policy named Marketing Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelRule.md new file mode 100644 index 0000000000..f779597117 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelRule.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-AutoSensitivityLabelRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-AutoSensitivityLabelPolicy cmdlet to remove auto-labeling policy rules from your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-AutoSensitivityLabelRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-AutoSensitivityLabelRule -Identity "Social Security Rule" +``` + +This example removes the rule named Social Security Rule. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-AutodiscoverVirtualDirectory.md similarity index 82% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-AutodiscoverVirtualDirectory.md index 0e672295d8..948dcc21f7 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-AutodiscoverVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-autodiscovervirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-AutodiscoverVirtualDirectory @@ -15,9 +14,9 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Remove-AutodiscoverVirtualDirectory cmdlet to remove the an existing Autodiscover virtual directory from Internet Information Services (IIS). +Use the Remove-AutodiscoverVirtualDirectory cmdlet to remove an existing Autodiscover virtual directory from Internet Information Services (IIS). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-AutodiscoverVirtualDirectory [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,13 +45,11 @@ This example removes the Autodiscover virtual directory from the site autodiscov ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -69,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-AvailabilityAddressSpace.md b/exchange/exchange-ps/exchange/Remove-AvailabilityAddressSpace.md similarity index 89% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-AvailabilityAddressSpace.md rename to exchange/exchange-ps/exchange/Remove-AvailabilityAddressSpace.md index ea5ab5bf6b..97bf6ead5a 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/exchange/Remove-AvailabilityAddressSpace.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-availabilityaddressspace +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-AvailabilityAddressSpace @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-AvailabilityAddressSpace cmdlet to remove existing availability address space objects and the associated credentials that were used to share free/busy data across Exchange organizations. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AvailabilityAddressSpace [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-AvailabilityAddressSpace [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION In on-premises Exchange organizations, you run the Remove-AvailabilityAddressSpace cmdlet on Exchange servers that have the Client Access server role installed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,9 +55,7 @@ This example immediately removes the availability address space object named Con 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 - - Distinguished name (DN) - - GUID ```yaml @@ -74,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,12 +129,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-AvailabilityConfig.md b/exchange/exchange-ps/exchange/Remove-AvailabilityConfig.md similarity index 75% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-AvailabilityConfig.md rename to exchange/exchange-ps/exchange/Remove-AvailabilityConfig.md index a6355e5fab..f51da6fded 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-AvailabilityConfig.md +++ b/exchange/exchange-ps/exchange/Remove-AvailabilityConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-availabilityconfig +online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityconfig applicable: Exchange Online title: Remove-AvailabilityConfig schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Remove-AvailabilityConfig @@ -15,22 +14,21 @@ monikerRange: "exchonline-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Remove-AvailabilityConfig cmdlet to remove an availability configuration. An availability configuration specifies an existing account that's used to exchange free/busy information between organizations. +Use the Remove-AvailabilityConfig cmdlet to remove the availability configuration that specifies the Microsoft 365 organizations to exchange free/busy information with. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AvailabilityConfig [[-Identity] ] [-Confirm] [-WhatIf] +Remove-AvailabilityConfig [[-Identity] ] + [-Confirm] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,39 +41,38 @@ This example removes the existing availability configuration. ## PARAMETERS -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +### -Identity +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: SwitchParameter +Type: AvailabilityConfigIdParameter Parameter Sets: (All) -Aliases: cf +Aliases: Applicable: Exchange Online Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the availability configuration that you want to remove. The default name of the availability configuration you create by using the New-AvailabilityConfig is Availability Configuration. +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: AvailabilityConfigIdParameter +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Online Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -100,12 +97,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-AvailabilityReportOutage.md b/exchange/exchange-ps/exchange/Remove-AvailabilityReportOutage.md similarity index 87% rename from exchange/exchange-ps/exchange/server-health-and-performance/Remove-AvailabilityReportOutage.md rename to exchange/exchange-ps/exchange/Remove-AvailabilityReportOutage.md index 3ade6bc52f..8e66eefd7a 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/exchange/Remove-AvailabilityReportOutage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/remove-availabilityreportoutage +online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityreportoutage applicable: Exchange Server 2010 title: Remove-AvailabilityReportOutage schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-AvailabilityReportOutage @@ -17,17 +16,22 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-AvailabilityReportOutage cmdlet to remove existing outages that have been added with the New-AvailabilityReportOutage cmdlet. Other outages must be modified with the Set-AvailabilityReportOutage cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-AvailabilityReportOutage [-SiteName] -ReportDate [-Confirm] [-Force] - [-ReportingDatabase ] [-ReportingServer ] [-WhatIf] [] +Remove-AvailabilityReportOutage [-SiteName] -ReportDate + [-Confirm] + [-Force] + [-ReportingDatabase ] + [-ReportingServer ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -40,33 +44,33 @@ This example removes a manually injected site-scoped outage for a specified day. ## PARAMETERS -### -ReportDate -The ReportDate parameter specifies the date to query for the outage report. +### -SiteName +The SiteName parameter specifies the name of the Active Directory site to associate the outage report with. ```yaml -Type: ExDateTime +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -SiteName -The SiteName parameter specifies the name of the Active Directory site to associate the outage report with. +### -ReportDate +The ReportDate parameter specifies the date to query for the outage report. ```yaml -Type: String +Type: ExDateTime Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False @@ -75,8 +79,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -93,7 +96,9 @@ Accept wildcard characters: False ``` ### -Force -The Force parameter suppresses the warning or confirmation messages that appear during specific configuration changes. +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. ```yaml Type: SwitchParameter @@ -161,12 +166,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Remove-BlockedConnector.md b/exchange/exchange-ps/exchange/Remove-BlockedConnector.md new file mode 100644 index 0000000000..6520e630b3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-BlockedConnector.md @@ -0,0 +1,82 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-BlockedConnector + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-BlockedConnector cmdlet to unblock inbound connectors that have been detected as potentially compromised. Blocked connectors are prevented from sending email. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-BlockedConnector -ConnectorId [-Reason ] [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-BlockedConnector -ConnectorId 159eb7c4-75d7-43e2-95fe-ced44b3e0a56 +``` + +This unblocks the specified blocked connector. + +## PARAMETERS + +### -ConnectorId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Reason +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_commonparameters). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-BlockedSenderAddress.md b/exchange/exchange-ps/exchange/Remove-BlockedSenderAddress.md new file mode 100644 index 0000000000..ce007bf146 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-BlockedSenderAddress.md @@ -0,0 +1,86 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-BlockedSenderAddress + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-BlockedSenderAddress cmdlet to unblock users in your Microsoft 365 organization that were impacted by the protection system. These users sent multiple messages that were classified as spam, so they were blocked from sending messages. + +**Note**: There's a limit to the number of times you can unblock a Microsoft 365 account. If you exceed the unblock limit for a user, you'll receive an error, and you'll need to contact support to unblock the user. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-BlockedSenderAddress -SenderAddress + [-Reason ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-BlockedSenderAddress -SenderAddress julia@contoso.com +``` + +This example unblocks the user julia@contoso.com. + +## PARAMETERS + +### -SenderAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Reason +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Remove-CalendarEvents.md b/exchange/exchange-ps/exchange/Remove-CalendarEvents.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Remove-CalendarEvents.md rename to exchange/exchange-ps/exchange/Remove-CalendarEvents.md index 8caedf746b..c199b24fec 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-CalendarEvents.md +++ b/exchange/exchange-ps/exchange/Remove-CalendarEvents.md @@ -1,12 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -Applicable: Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" --- # Remove-CalendarEvents @@ -16,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-CalendarEvents cmdlet to cancel future meetings in user or resource mailboxes. Cancelling future meetings removes them from attendee and resource calendars (for example, you're going to remove the mailbox, or the user is going on a leave of absence). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,13 +26,15 @@ Remove-CalendarEvents [-Identity] -QueryWindowInDays ] - [-WhatIf] [] + [-UseCustomRouting] + [-WhatIf] + [] ``` ## DESCRIPTION This cmdlet cancels meetings in the specified mailbox where the mailbox is the meeting organizer, and the meeting has one or more attendees or resources. It doesn't cancel appointments or meetings without attendees or resources. Because meeting cancellations must be sent out, the mailbox must still be enabled to send mail. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,23 +65,14 @@ This example previews the meetings that would be cancelled in Jacob Berger's cal The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -136,8 +129,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -174,7 +166,7 @@ Accept wildcard characters: False ### -QueryStartDate 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". +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". **Note**: If you don't use this parameter, today's date is used. @@ -193,6 +185,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -214,12 +224,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/Remove-CaseHoldPolicy.md new file mode 100644 index 0000000000..0a3fbdb087 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-CaseHoldPolicy.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-CaseHoldPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-CaseHoldPolicy cmdlet to remove case hold policies from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-CaseHoldPolicy [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +You should also remove the case hold rule that corresponds to the removed policy by using the Remove-CaseHoldRule cmdlet. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-CaseHoldPolicy -Identity "Regulation 123 Compliance" +``` + +This example removes the case hold policy named "Regulation 123 Compliance". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the case hold policy to remove. You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-CaseHoldRule.md b/exchange/exchange-ps/exchange/Remove-CaseHoldRule.md new file mode 100644 index 0000000000..cb7f9417bd --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-CaseHoldRule.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-CaseHoldRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-CaseHoldRule cmdlet to remove case hold rules from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-CaseHoldRule [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +Removing a case hold rule causes the release of all Exchange mailbox and SharePoint site case holds that are associated with the rule. Removing a case hold rule also causes the corresponding case hold policy to become invalid, so you should remove it by using the Remove-CaseHoldPolicy cmdlet. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-CaseHoldRule -Identity "One Year Standard" +``` + +This example removes the case hold rule named "One Year Standard". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the case hold rule to remove. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-ClassificationRuleCollection.md b/exchange/exchange-ps/exchange/Remove-ClassificationRuleCollection.md similarity index 87% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-ClassificationRuleCollection.md rename to exchange/exchange-ps/exchange/Remove-ClassificationRuleCollection.md index ec9ca4dd19..9e0c0ef4af 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/exchange/Remove-ClassificationRuleCollection.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-classificationrulecollection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-ClassificationRuleCollection @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-ClassificationRuleCollection to remove classification rule collections from your organization. -In the Office 365 Security & Compliance Center, use the Remove-DlpSensitiveInformationTypeRulePackage cmdlet. +In Security & Compliance PowerShell, use the Remove-DlpSensitiveInformationTypeRulePackage cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ClassificationRuleCollection [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-ClassificationRuleCollection [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-ClientAccessArray.md b/exchange/exchange-ps/exchange/Remove-ClientAccessArray.md similarity index 83% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-ClientAccessArray.md rename to exchange/exchange-ps/exchange/Remove-ClientAccessArray.md index 4f7b33abd1..24930a04a7 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-ClientAccessArray.md +++ b/exchange/exchange-ps/exchange/Remove-ClientAccessArray.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-clientaccessarray +online version: https://learn.microsoft.com/powershell/module/exchange/remove-clientaccessarray applicable: Exchange Server 2010 title: Remove-ClientAccessArray schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-ClientAccessArray @@ -17,17 +16,20 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-ClientAccessArray cmdlet to remove RPC Client Access arrays (load-balanced arrays of Client Access servers within a single Active Directory site). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ClientAccessArray [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-ClientAccessArray [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,13 +46,9 @@ This example removes the existing Client Access array with the FQDN value casarr 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) - - ExchangeLegacyDN - - Fully qualified domain name (FQDN) - - Distinguished name (DN) - - GUID ```yaml @@ -69,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,13 +120,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### -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. +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md b/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md new file mode 100644 index 0000000000..df3b17ddf9 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md @@ -0,0 +1,138 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ClientAccessRule + +## SYNOPSIS +> [!NOTE] +> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). + +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-ClientAccessRule cmdlet to remove client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ClientAccessRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ClientAccessRule "Block Client Connections from 192.168.1.0/24" +``` + +This example removes the existing client access rule named "Block Connections from 192.168.1.0/24". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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-ComplianceCase.md b/exchange/exchange-ps/exchange/Remove-ComplianceCase.md new file mode 100644 index 0000000000..a636d54a72 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ComplianceCase.md @@ -0,0 +1,124 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ComplianceCase + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-ComplianceCase cmdlet to remove compliance cases from the Microsoft Purview compliance portal or the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ComplianceCase [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ComplianceCase -Identity "Case 5150" +``` + +This example removes the compliance case named Case 5150 + +## PARAMETERS + +### -Identity +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 +- Identity (GUID value) + +```yaml +Type: ComplianceCaseIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/Remove-ComplianceCaseMember.md new file mode 100644 index 0000000000..2a22dd2318 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ComplianceCaseMember.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ComplianceCaseMember + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-ComplianceCaseMember cmdlet to remove a single member from an eDiscovery search in Security & Compliance. To replace all existing members, use the Update-ComplianceCaseMember cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ComplianceCaseMember [-Case] -Member + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ComplianceCaseMember -Case "Case OU812" -Member "Jan Dryml" +``` + +This example removes Jan Dryml from the eDiscovery case named Case OU812. + +## PARAMETERS + +### -Case +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Member +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/Remove-ComplianceRetentionEventType.md new file mode 100644 index 0000000000..fdca44b480 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ComplianceRetentionEventType.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ComplianceRetentionEventType + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-ComplianceRetentionEventType cmdlet to remove retention event types in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ComplianceRetentionEventType -Identity + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ComplianceRetentionEventType -Identity "Fabrikam Project" +``` + +This example remove the retention event type name Fabrikam Project + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ComplianceSearch.md b/exchange/exchange-ps/exchange/Remove-ComplianceSearch.md new file mode 100644 index 0000000000..92fdcfc7a7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ComplianceSearch.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ComplianceSearch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-ComplianceSearch cmdlet to remove compliance searches from Exchange Server 2016 and from the Microsoft Purview compliance portal. The searches must be stopped or completed. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ComplianceSearch [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ComplianceSearch -Identity "Case 1234" +``` + +This example removes the compliance search named Case 1234 + +## PARAMETERS + +### -Identity +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: + +- Name +- JobRunId (GUID) + +You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status + +```yaml +Type: ComplianceSearchIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/Remove-ComplianceSearchAction.md new file mode 100644 index 0000000000..8140168e36 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ComplianceSearchAction.md @@ -0,0 +1,107 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ComplianceSearchAction + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-ComplianceSearch cmdlet to remove compliance search actions from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ComplianceSearchAction [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ComplianceSearchAction -Identity "Case 1234_Preview" +``` + +This example removes the compliance search action named `Case 1234_Preview`. + +## PARAMETERS + +### -Identity +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"`. +- JobRunId (GUID) + +```yaml +Type: ComplianceSearchActionIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/Remove-ComplianceSecurityFilter.md new file mode 100644 index 0000000000..8b38b2ba8a --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ComplianceSecurityFilter.md @@ -0,0 +1,104 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ComplianceSecurityFilter + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-ComplianceSecurityFilter cmdlet to remove compliance security filters from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ComplianceSecurityFilter -FilterName + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ComplianceSecurityFilter -FilterName "HR Filter" +``` + +This example removes the compliance security filter named HR Filter. + +## PARAMETERS + +### -FilterName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ComplianceTag.md b/exchange/exchange-ps/exchange/Remove-ComplianceTag.md new file mode 100644 index 0000000000..46c293ddf7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ComplianceTag.md @@ -0,0 +1,142 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ComplianceTag + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-ComplianceTag cmdlet to remove retention labels from the Microsoft Purview compliance portal. Retention labels apply retention settings to content. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ComplianceTag [-Identity] + [-Confirm] + [-ForceDeletion] + [-PriorityCleanup] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ComplianceTag -Identity "HR Content" +``` + +This example removes the label named HR Content. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the label that you want to remove. You can use any value that uniquely identifies the tag. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-ContentFilterPhrase.md b/exchange/exchange-ps/exchange/Remove-ContentFilterPhrase.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-ContentFilterPhrase.md rename to exchange/exchange-ps/exchange/Remove-ContentFilterPhrase.md index 0021fcffbb..88836574db 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-ContentFilterPhrase.md +++ b/exchange/exchange-ps/exchange/Remove-ContentFilterPhrase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-contentfilterphrase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ContentFilterPhrase @@ -17,15 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ContentFilterPhrase cmdlet to remove one or all custom words that the Content Filter agent processes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` Remove-ContentFilterPhrase [-Identity] - [-Confirm] [-DomainController ] - [-WhatIf] [] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ### Phrase @@ -33,11 +34,12 @@ Remove-ContentFilterPhrase [-Identity] Remove-ContentFilterPhrase [-Phrase ] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -71,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -145,12 +146,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DataClassification.md b/exchange/exchange-ps/exchange/Remove-DataClassification.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DataClassification.md rename to exchange/exchange-ps/exchange/Remove-DataClassification.md index 50cac4a9a3..c89fd96ca0 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DataClassification.md +++ b/exchange/exchange-ps/exchange/Remove-DataClassification.md @@ -1,37 +1,39 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dataclassification -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-DataClassification ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [Remove-DlpSensitiveInformationType](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlpsensitiveinformationtype) cmdlet in Office 365 Security & Compliance Center PowerShell. +In Exchange Online, this cmdlet has been replaced by the [Remove-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchange/remove-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the Remove-DataClassification cmdlet to remove data classification rules that use document fingerprints. You can't use this cmdlet to remove built-in data classification rules. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DataClassification [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-DataClassification [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,16 +50,14 @@ This example removes the data classification rule named "Contoso Confidential". 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 - - LocalizedName - - Identity GUID value ```yaml Type: DataClassificationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -69,15 +69,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -109,7 +108,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -123,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroup.md similarity index 88% rename from exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroup.md index 92ce53f35c..2311d1505f 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/remove-databaseavailabilitygroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-DatabaseAvailabilityGroup @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-DatabaseAvailabilityGroup cmdlet to delete an empty database availability group (DAG). Before you can delete a DAG, you must first remove all Mailbox servers from the DAG. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DatabaseAvailabilityGroup [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-DatabaseAvailabilityGroup [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +61,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -113,12 +114,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupNetwork.md similarity index 87% rename from exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupNetwork.md index 35a0812cb1..2a130fd882 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupNetwork.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/remove-databaseavailabilitygroupnetwork +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-DatabaseAvailabilityGroupNetwork @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-DatabaseAvailabilityGroupNetwork cmdlet to remove a database availability group (DAG) network. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DatabaseAvailabilityGroupNetwork [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-DatabaseAvailabilityGroupNetwork [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +61,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -113,12 +114,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupServer.md similarity index 85% rename from exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupServer.md rename to exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupServer.md index 6b724b2a68..dfb283d873 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupServer.md +++ b/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/remove-databaseavailabilitygroupserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-DatabaseAvailabilityGroupServer @@ -17,22 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-DatabaseAvailabilityGroupServer cmdlet to remove a Mailbox server from a database availability group (DAG). To remove a Mailbox server from a DAG, the Mailbox server must not host any replicated databases. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DatabaseAvailabilityGroupServer [-Identity] - [-MailboxServer] +Remove-DatabaseAvailabilityGroupServer [-Identity] [-MailboxServer] [-ConfigurationOnly] [-Confirm] [-DomainController ] [-SkipDagValidation] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,11 +71,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -93,7 +89,11 @@ Accept wildcard characters: False ``` ### -ConfigurationOnly -The ConfigurationOnly switch should only be used if the Mailbox server has been lost and can no longer be contacted, or in situations when the Mailbox server can't be restored to operational service before the messaging service is needed. When used, it removes the Mailbox server from the DAG object in Active Directory. 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. +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. + +You should use this switch only if the Mailbox server has been lost and can no longer be contacted, or in situations when the Mailbox server can't be restored to operational service before the messaging service is needed. ```yaml Type: SwitchParameter @@ -111,8 +111,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -181,12 +180,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-DeliveryAgentConnector.md b/exchange/exchange-ps/exchange/Remove-DeliveryAgentConnector.md similarity index 87% rename from exchange/exchange-ps/exchange/mail-flow/Remove-DeliveryAgentConnector.md rename to exchange/exchange-ps/exchange/Remove-DeliveryAgentConnector.md index d67d5b38e9..ff7ae195fd 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/exchange/Remove-DeliveryAgentConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-deliveryagentconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-DeliveryAgentConnector @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. The Remove-DeliveryAgentConnector cmdlet removes a specific delivery agent connector configured in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DeliveryAgentConnector [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-DeliveryAgentConnector [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://docs.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). +Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessPolicy.md new file mode 100644 index 0000000000..12423d67fd --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessPolicy.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DeviceConditionalAccessPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DeviceConditionalAccessPolicy cmdlet to remove mobile device conditional access policies from Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DeviceConditionalAccessPolicy [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DeviceConditionalAccessPolicy -Identity "Human Resources" +``` + +This example removes the mobile device conditional access policy named Human Resources. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessRule.md new file mode 100644 index 0000000000..08e72f3b32 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessRule.md @@ -0,0 +1,113 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DeviceConditionalAccessRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DeviceConditionalAccessRule cmdlet to remove mobile device conditional access rules from Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DeviceConditionalAccessRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DeviceConditionalAccessRule "Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}" +``` + +This example removes the mobile device conditional access rule named Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/Remove-DeviceConfigurationPolicy.md new file mode 100644 index 0000000000..913547d5a2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DeviceConfigurationPolicy.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DeviceConfigurationPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DeviceConfigurationPolicy cmdlet to remove mobile device configuration policies from Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DeviceConfigurationPolicy [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DeviceConfigurationPolicy -Identity "Engineering Group" +``` + +This example removes the mobile device configuration policy named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/Remove-DeviceConfigurationRule.md new file mode 100644 index 0000000000..d3ab49229c --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DeviceConfigurationRule.md @@ -0,0 +1,113 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DeviceConfigurationRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-DeviceConfigurationRule cmdlet to remove mobile device configuration rules from Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DeviceConfigurationRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DeviceConfigurationRule "Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}" +``` + +This example removes the mobile device configuration rule named Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/Remove-DeviceTenantPolicy.md new file mode 100644 index 0000000000..919b43271d --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DeviceTenantPolicy.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DeviceTenantPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DeviceTenantPolicy cmdlet to remove your organization's mobile device tenant policy from Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DeviceTenantPolicy [-Identity ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). +## EXAMPLES + +### Example 1 +```powershell +Remove-DeviceTenantPolicy +``` + +This example removes your organization's mobile device tenant policy. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DeviceTenantRule.md b/exchange/exchange-ps/exchange/Remove-DeviceTenantRule.md new file mode 100644 index 0000000000..0fe5232d12 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DeviceTenantRule.md @@ -0,0 +1,113 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DeviceTenantRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DeviceTenantRule cmdlet to remove your organization's mobile device tenant rule from Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DeviceTenantRule [-Identity ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DeviceTenantRule +``` + +This example removes the mobile device tenant rule from your organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-DistributionGroup.md b/exchange/exchange-ps/exchange/Remove-DistributionGroup.md similarity index 85% rename from exchange/exchange-ps/exchange/users-and-groups/Remove-DistributionGroup.md rename to exchange/exchange-ps/exchange/Remove-DistributionGroup.md index c5008e4d53..b35ddb9a2a 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-DistributionGroup.md +++ b/exchange/exchange-ps/exchange/Remove-DistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-distributiongroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-DistributionGroup @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-DistributionGroup cmdlet to remove distribution groups and mail-enabled security groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,11 +26,12 @@ Remove-DistributionGroup [-Identity] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,15 +48,10 @@ This example removes the distribution group named Temporary Staff. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -73,14 +68,13 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. 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: +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. -- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +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: +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. - Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. -You don't need to specify a value with this switch. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -97,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -135,12 +128,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -177,12 +169,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-DistributionGroupMember.md b/exchange/exchange-ps/exchange/Remove-DistributionGroupMember.md similarity index 87% rename from exchange/exchange-ps/exchange/users-and-groups/Remove-DistributionGroupMember.md rename to exchange/exchange-ps/exchange/Remove-DistributionGroupMember.md index 79c1ca5d08..0f323c30da 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-DistributionGroupMember.md +++ b/exchange/exchange-ps/exchange/Remove-DistributionGroupMember.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-distributiongroupmember +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-DistributionGroupMember @@ -17,19 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-DistributionGroupMember cmdlet to remove a single member from distribution groups or mail-enabled security groups. To replace all members, use the Update-DistributionGroupMember cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DistributionGroupMember [-Identity] [-BypassSecurityGroupManagerCheck] - [-Confirm] [-DomainController ] [-Member ] [-WhatIf] [] +Remove-DistributionGroupMember [-Identity] + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-DomainController ] + [-Member ] + [-WhatIf] + [] ``` ## DESCRIPTION You can't use the Remove-DistributionGroupMember cmdlet to remove the member of a dynamic distribution group. A dynamic distribution group's membership is calculated from query results. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,15 +50,10 @@ This example removes Jan Dryml from the distribution group named Technical Suppo 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -71,14 +70,13 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. 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: +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. -- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +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: +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. - Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. -You don't need to specify a value with this switch. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -95,8 +93,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -134,15 +131,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -179,12 +171,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/Remove-DlpCompliancePolicy.md new file mode 100644 index 0000000000..86f93677d8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DlpCompliancePolicy.md @@ -0,0 +1,116 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DlpCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DlpCompliancePolicy cmdlet to remove data loss prevention (DLP) policies from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DlpCompliancePolicy [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DlpCompliancePolicy -Identity 7e640345-1a7f-4f4e-9c17-681c070ed5e2 +``` + +This example removes a DLP policy specified by its GUID. + +### Example 2 +```powershell +Remove-DlpCompliancePolicy -Identity "PII Main Policy" +``` + +This example removes a DLP policy specified by its name. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DlpComplianceRule.md b/exchange/exchange-ps/exchange/Remove-DlpComplianceRule.md new file mode 100644 index 0000000000..cbbfa8b856 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DlpComplianceRule.md @@ -0,0 +1,109 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DlpComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DlpComplianceRule cmdlet to remove Data Loss Prevention (DLP) rules from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DlpComplianceRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DlpComplianceRule -Identity "PII SS# Custom" +``` + +This example removes the DLP rule named "PII SS# Custom". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DlpEdmSchema.md b/exchange/exchange-ps/exchange/Remove-DlpEdmSchema.md new file mode 100644 index 0000000000..f32281feb1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DlpEdmSchema.md @@ -0,0 +1,109 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DlpEdmSchema + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DlpEdmSchema cmdlet to remove exact data match (EDM) data loss prevention (DLP) schemas from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DlpEdmSchema [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DlpEdmSchema -Identity "Schema for Patient Records" +``` + +This example removes the DLP EDM schema named Schema for Patient Records. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) + +```yaml +Type: EdmStorageIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Learn about exact data match based sensitive information types](https://learn.microsoft.com/purview/sit-learn-about-exact-data-match-based-sits) diff --git a/exchange/exchange-ps/exchange/Remove-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/Remove-DlpKeywordDictionary.md new file mode 100644 index 0000000000..9497d5484f --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DlpKeywordDictionary.md @@ -0,0 +1,111 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DlpKeywordDictionary + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DlpKeywordDictionary cmdlet to remove data loss prevention (DLP) keyword dictionaries from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DlpKeywordDictionary [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DlpKeywordDictionary -Identity "Financial Data" +``` + +This example removes the DLP keyword dictionary named Financial Data. + +### Example 2 +```powershell +Get-DlpKeywordDictionary | Foreach-Object { Remove-DlpKeywordDictionary -Identity $_.Name -confirm:$True } +``` + +This example removes all the DLP keyword dictionaries with a Confirm on each removal. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpPolicy.md b/exchange/exchange-ps/exchange/Remove-DlpPolicy.md similarity index 77% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpPolicy.md rename to exchange/exchange-ps/exchange/Remove-DlpPolicy.md index cdbf91ecb9..e7591b41e1 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-DlpPolicy.md @@ -1,33 +1,37 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlppolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-DlpPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Remove-DlpCompliancePolicy and Remove-DlpComplianceRule cmdlets instead. -Use the Remove-DlpPolicy cmdlet to remove an existing data loss prevention (DLP) policy. +This cmdlet is functional only in on-premises Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the Remove-DlpPolicy cmdlet to remove existing data loss prevention (DLP) policies that are based on transport rules (mail flow rules) from your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DlpPolicy [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-DlpPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,7 +45,11 @@ This example removes the existing DLP policy named Contoso PII. ## PARAMETERS ### -Identity -The Identity parameter specifies the DLP policy you want to remove. 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. +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 +- Distinguished name (DN) +- GUID ```yaml Type: DlpPolicyIdParameter @@ -59,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -77,8 +84,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -115,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpPolicyTemplate.md b/exchange/exchange-ps/exchange/Remove-DlpPolicyTemplate.md similarity index 85% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpPolicyTemplate.md rename to exchange/exchange-ps/exchange/Remove-DlpPolicyTemplate.md index adff0c09d8..6ec3166bac 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/exchange/Remove-DlpPolicyTemplate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlppolicytemplate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-DlpPolicyTemplate @@ -15,19 +14,22 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Remove-DlpPolicyTemplate cmdlet to remove a data loss prevention (DLP) policy template from your organization. +Use the Remove-DlpPolicyTemplate cmdlet to remove data loss prevention (DLP) policy templates that are based on transport rules (mail flow rules) from your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DlpPolicyTemplate [[-Identity] ] [-Confirm] [-DomainController ] [-WhatIf] +Remove-DlpPolicyTemplate [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -40,11 +42,26 @@ This example removes the DLP policy template named External DLP Policy Template. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -76,22 +93,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -113,12 +114,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationType.md new file mode 100644 index 0000000000..248e930c45 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationType.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DlpSensitiveInformationType + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DlpSensitiveInformationType cmdlet to remove sensitive information type rules that use document fingerprints. You can't use this cmdlet to remove built-in sensitive information type rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DlpSensitiveInformationType [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. + +**Note**: A "ManagementObjectNotFoundException" error means there was a synchronization problem between the Microsoft Purview compliance portal and Exchange Online. This happens when you try to remove data classifications that are being used in mail flow rules (also known as transport rules). You can remove the mail flow rule, wait for synchronization to finish, and then add the rule back. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-DlpSensitiveInformationType "Contoso Confidential" +``` + +This example removes the sensitive information type rule named "Contoso Confidential". + +## PARAMETERS + +### -Identity +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 +- LocalizedName +- Identity GUID value + +```yaml +Type: DataClassificationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationTypeRulePackage.md new file mode 100644 index 0000000000..dcf39f5bd5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationTypeRulePackage.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-DlpSensitiveInformationTypeRulePackage + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-DlpSensitiveInformationTypeConfig cmdlet to remove data loss prevention (DLP) sensitive information type rule packages from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-DlpSensitiveInformationTypeRulePackage [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$Rule = Get-DlpSensitiveInformationTypeRulePackage -Identity "Contoso Rule Pack" + +$Rule | Remove-DlpSensitiveInformationTypeRulePackage +``` + +This example removes the third-party sensitive information type rule package named Contoso Rule Pack. The first command stores the identity of the rule package in a variable. The second command pipes the variable to the Remove-DlpSensitiveInformationTypeRulePackage cmdlet. + +## PARAMETERS + +### -Identity +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 +- LocalizedName +- GUID (from the Identity value) + +```yaml +Type: SensitiveInformationTypeRuleCollectionIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/Remove-DynamicDistributionGroup.md similarity index 82% rename from exchange/exchange-ps/exchange/users-and-groups/Remove-DynamicDistributionGroup.md rename to exchange/exchange-ps/exchange/Remove-DynamicDistributionGroup.md index d05476b972..3c76cd90a3 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/exchange/Remove-DynamicDistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-dynamicdistributiongroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-DynamicDistributionGroup @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-DynamicDistributionGroup cmdlet to delete dynamic distribution groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-DynamicDistributionGroup [-Identity] [-Confirm] [-DomainController ] - [-IgnoreDefaultScope] [-WhatIf] [] +Remove-DynamicDistributionGroup [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,22 +47,17 @@ This example deletes the dynamic distribution group named Test Users. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml Type: DynamicGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -71,15 +69,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -109,12 +106,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -137,7 +133,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -151,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Remove-EOPProtectionPolicyRule.md new file mode 100644 index 0000000000..ba11d899b1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-EOPProtectionPolicyRule.md @@ -0,0 +1,114 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-EOPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-EOPProtectionPolicyRule cmdlet to remove rules from Exchange Online Protection (EOP) protections in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. + +**Note**: Use this cmdlet to remove a rule only if you plan to immediately recreate the rule using the New-EOPProtectionPolicyRule cmdlet. The affected preset security policy won't function without a corresponding rule. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-EOPProtectionPolicyRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" +``` + +This example removes the existing rule for EOP protections in the Standard preset security policy. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to remove. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-EcpVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-EcpVirtualDirectory.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-EcpVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-EcpVirtualDirectory.md index dca2286966..07f4762142 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-EcpVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-ecpvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-EcpVirtualDirectory @@ -19,7 +18,7 @@ Use the Remove-EcpVirtualDirectory cmdlet to remove Exchange Control Panel (ECP) The ECP web management interface was introduced in Exchange Server 2010. In Exchange Server 2013 and Exchange Server 2016, the EAC virtual directories and the corresponding management cmdlets still use ECP in the name. You can use these cmdlets to manage ECP virtual directories on Exchange 2010, Exchange 2013 and Exchange 2016 servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,11 +26,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-EcpVirtualDirectory [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,13 +47,11 @@ This example removes the ECP virtual directory named ecp located on the default ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. Remote removal of an ECP virtual directory isn't supported. You need run this command from the local computer. @@ -73,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -127,12 +124,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-EdgeSubscription.md b/exchange/exchange-ps/exchange/Remove-EdgeSubscription.md similarity index 84% rename from exchange/exchange-ps/exchange/mail-flow/Remove-EdgeSubscription.md rename to exchange/exchange-ps/exchange/Remove-EdgeSubscription.md index 41c0ae2828..e792a7e0b9 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-EdgeSubscription.md +++ b/exchange/exchange-ps/exchange/Remove-EdgeSubscription.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-edgesubscription +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-EdgeSubscription @@ -17,27 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-EdgeSubscription cmdlet to remove Edge Subscription from the Exchange organization and from the subscribed Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-EdgeSubscription [-Identity] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] +Remove-EdgeSubscription [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION When you remove an Edge Subscription, the following changes are made: - Synchronization of information from Active Directory to the Active Directory Lightweight Directory Services (AD LDS) instance stops. - - All the accounts stored in AD LDS are removed. - - The Edge Transport server is removed from the list of source servers for any Send connector. - - If the Edge Transport server is the only source server for any Send connector, the Send connector is removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -105,9 +104,9 @@ Accept wildcard characters: False ``` ### -Force -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. +The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -If you don't specify the Force 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. +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. ```yaml Type: SwitchParameter @@ -143,12 +142,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/Remove-EmailAddressPolicy.md similarity index 87% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-EmailAddressPolicy.md rename to exchange/exchange-ps/exchange/Remove-EmailAddressPolicy.md index 6d4d1461db..8389a40fd5 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-EmailAddressPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-EmailAddressPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/remove-emailaddresspolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-EmailAddressPolicy @@ -15,19 +14,22 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the Remove-EmailAddressPolicy cmdlet to remove existing email address policies and update the affected recipients. In Exchange Online, email address policies are only available for Office 365 groups. +Use the Remove-EmailAddressPolicy cmdlet to remove existing email address policies and update the affected recipients. In Exchange Online, email address policies are available only for Microsoft 365 Groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-EmailAddressPolicy [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-EmailAddressPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,9 +46,7 @@ This example removes the email address policy named Southwest Executives. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -65,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Remove-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Remove-ExchangeCertificate.md similarity index 87% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Remove-ExchangeCertificate.md rename to exchange/exchange-ps/exchange/Remove-ExchangeCertificate.md index 6702c4aaa7..e6a35f7f1c 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Remove-ExchangeCertificate.md +++ b/exchange/exchange-ps/exchange/Remove-ExchangeCertificate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/remove-exchangecertificate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ExchangeCertificate @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ExchangeCertificate cmdlet to remove existing Exchange certificates or pending certificate requests (also known as certificate signing requests or CSRs) from Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Thumbprint ``` -Remove-ExchangeCertificate [-Thumbprint] [-Server ] +Remove-ExchangeCertificate [-Thumbprint] + [-Server ] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity @@ -34,17 +35,18 @@ Remove-ExchangeCertificate [-Thumbprint] [-Server ] Remove-ExchangeCertificate [[-Identity] ] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can't remove the certificate that's being used. If you want to replace the default certificate for the server with another certificate that has the same fully qualified domain name (FQDN), you must create the new certificate first, and then remove the old certificate. -There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://docs.microsoft.com/Exchange/architecture/client-access/certificates). +There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://learn.microsoft.com/Exchange/architecture/client-access/certificates). -Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://blogs.office.com/2014/10/29/protecting-ssl-3-0-vulnerability/). +Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,11 +84,35 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -Identity +The Identity parameter specifies the certificate that you want to remove. Valid values are: + +- `ServerNameOrFQDN\Thumbprint` +- `Thumbprint` + +You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. + +You can't use this parameter with the Server parameter. + +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. + +```yaml +Type: ExchangeCertificateIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,11 +150,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -164,43 +187,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the certificate that you want to remove. Valid values are: - -- \\\\ - -- \ - -You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. - -You can't use this parameter with the Server parameter. - -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. - -```yaml -Type: ExchangeCertificateIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/exchange/Remove-ExoPhishSimOverrideRule.md new file mode 100644 index 0000000000..57130dbbe8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ExoPhishSimOverrideRule.md @@ -0,0 +1,135 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ExoPhishSimOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-ExoPhishSimOverrideRule cmdlet to remove third-party phishing simulation override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ExoPhishSimOverrideRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoPhishSimOverrideRule | Remove-ExoPhishSimOverrideRule +``` + +This example removes any phishing simulation override rules. + +### Example 2 +```powershell +Remove-ExoPhishSimOverrideRule -Identity "_Exe:PhishSimOverr:6fed4b63-3563-495d-a481-b24a311f8329" +``` + +This example removes the specified phishing simulation override rule. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +Use the Get-ExoPhishSimOverrideRule cmdlet to find the values. The rule name syntax is `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/exchange/Remove-ExoSecOpsOverrideRule.md new file mode 100644 index 0000000000..b127bd5c6f --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ExoSecOpsOverrideRule.md @@ -0,0 +1,132 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ExoSecOpsOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-ExoSecOpsOverrideRule cmdlet to remove SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ExoSecOpsOverrideRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoSecOpsOverrideRule| Remove-ExoSecOpsOverrideRule +``` + +This example removes any SecOps mailbox override rules. + +### Example 2 +```powershell +Remove-ExoSecOpsOverrideRule -Identity "_Exe:SecOpsOverrid:312c23cf-0377-4162-b93d-6548a9977efb" +``` + +This example removes the specified SecOps mailbox override rule. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +Use the Get-ExoSecOpsMailboxRule cmdlet to find these values. The name of the rule uses the following syntax: `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-FeatureConfiguration.md b/exchange/exchange-ps/exchange/Remove-FeatureConfiguration.md new file mode 100644 index 0000000000..d6b0f82b35 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-FeatureConfiguration.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/remove-featureconfiguration +applicable: Security & Compliance +title: Remove-FeatureConfiguration +schema: 2.0.0 +--- + +# Remove-FeatureConfiguration + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +> [!NOTE] +> This cmdlet is currently available in Public Preview, isn't available in all organizations, and is subject to change. + +Use the Remove-FeatureConfiguration cmdlet to remove Microsoft Purview feature configurations within your organization, including: + +- Collection policies. +- Advanced label based protection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-FeatureConfiguration [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Remove-FeatureConfiguration -Identity "Engineering Group" +``` + +This example removes the specified feature configuration. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-FederatedDomain.md b/exchange/exchange-ps/exchange/Remove-FederatedDomain.md similarity index 82% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Remove-FederatedDomain.md rename to exchange/exchange-ps/exchange/Remove-FederatedDomain.md index 0eb60b9358..c0cbc63696 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-FederatedDomain.md +++ b/exchange/exchange-ps/exchange/Remove-FederatedDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/remove-federateddomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-FederatedDomain @@ -19,21 +18,25 @@ Use the Remove-FederatedDomain cmdlet to remove a federated domain from the fede If you remove a domain configured for federated sharing, federated sharing for that domain is disabled. -For more information, see [Federation](https://docs.microsoft.com/exchange/federation-exchange-2013-help). +For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-FederatedDomain [[-Identity] ] -DomainName [-Confirm] - [-DomainController ] [-Force] [-WhatIf] [] +Remove-FederatedDomain [[-Identity] ] -DomainName + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION An Exchange organization's federated organization identifier is generally created using the organization's primary domain name. Additional domain names can be added and removed. The Remove-FederatedDomain cmdlet removes a federated domain from the federated organization identifier. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,6 +49,22 @@ This example removes the federated domain contoso.co.uk from the federated organ ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -DomainName The DomainName parameter specifies the federated domain name to be removed from the federated organization identifier. @@ -65,8 +84,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -99,7 +117,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch specifies whether to suppress warning or confirmation messages when removing a federated domain. This parameter can be used when the removal of the federated domain from Windows Live fails, but the configuration of this domain as a federated domain in Exchange should be removed regardless. The result of running this task with the Force switch is that the Exchange configuration is removed but the domain may not be released in Windows Live. We recommend that you not use the Force switch unless the release of the domain from Windows Live continues to fail. +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. ```yaml Type: SwitchParameter @@ -114,22 +134,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -151,12 +155,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-FederationTrust.md b/exchange/exchange-ps/exchange/Remove-FederationTrust.md similarity index 88% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Remove-FederationTrust.md rename to exchange/exchange-ps/exchange/Remove-FederationTrust.md index adad0fab9a..86132d007a 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-FederationTrust.md +++ b/exchange/exchange-ps/exchange/Remove-FederationTrust.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/remove-federationtrust +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-FederationTrust @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-FederationTrust cmdlet to remove an existing federation trust from an Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-FederationTrust [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-FederationTrust [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION Federation trusts are set up with Microsoft Federation Gateway to enable calendar sharing and free/busy sharing with external Exchange organizations or individuals. The Remove-FederationTrust cmdlet removes a federation trust. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyAuthority.md b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyAuthority.md new file mode 100644 index 0000000000..6de6ae8679 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyAuthority.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/remove-fileplanpropertyauthority +applicable: Security & Compliance +title: Remove-FilePlanPropertyAuthority +schema: 2.0.0 +--- + +# Remove-FilePlanPropertyAuthority + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-FilePlanPropertyAuthority cmdlet to remove file plan property authorities. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-FilePlanPropertyAuthority [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Remove-FilePlanPropertyAuthority -Identity "Contoso Authority" +``` + +This example removes the custom file plan property authority named Contoso Authority. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCategory.md b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCategory.md new file mode 100644 index 0000000000..e5e7d1c7fa --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCategory.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/remove-fileplanpropertycategory +applicable: Security & Compliance +title: Remove-FilePlanPropertyCategory +schema: 2.0.0 +--- + +# Remove-FilePlanPropertyCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-FilePlanPropertyCategory cmdlet to remove file plan property categories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-FilePlanPropertyCategory [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Remove-FilePlanPropertyCategory -Identity "Contoso Category" +``` + +This example removes the custom file plan property category named Contoso Category. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCitation.md b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCitation.md new file mode 100644 index 0000000000..70c1f29a20 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCitation.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/remove-fileplanpropertycitation +applicable: Security & Compliance +title: Remove-FilePlanPropertyCitation +schema: 2.0.0 +--- + +# Remove-FilePlanPropertyCitation + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-FilePlanPropertyCitation cmdlet to remove file plan property citations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-FilePlanPropertyCitation [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Remove-FilePlanPropertyCitation -Identity "Contoso Citation" +``` + +This example removes the custom file plan property citation named Contoso Citation. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyDepartment.md b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyDepartment.md new file mode 100644 index 0000000000..630bbe64a4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyDepartment.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/remove-fileplanpropertydepartment +applicable: Security & Compliance +title: Remove-FilePlanPropertyDepartment +schema: 2.0.0 +--- + +# Remove-FilePlanPropertyDepartment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Removet-FilePlanPropertyDepartment cmdlet to remove file plan property departments. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-FilePlanPropertyDepartment [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Remove-FilePlanPropertyDepartment -Identity "Contoso HR" +``` + +This example removes the custom file plan property department named Contoso HR. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyReferenceId.md new file mode 100644 index 0000000000..7548cc4cf3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-FilePlanPropertyReferenceId.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/remove-fileplanpropertyreferenceid +applicable: Security & Compliance +title: Remove-FilePlanPropertyReferenceId +schema: 2.0.0 +--- + +# Remove-FilePlanPropertyReferenceId + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the New-FilePlanPropertyReferenceId cmdlet to remove file plan property reference IDs. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-FilePlanPropertyReferenceId [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Remove-FilePlanPropertyReferenceId -Identity "Contoso-0001" +``` + +This example removes the custom file plan property reference ID named Contoso-0001. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-FilePlanPropertySubCategory.md b/exchange/exchange-ps/exchange/Remove-FilePlanPropertySubCategory.md new file mode 100644 index 0000000000..5e45a1faf5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-FilePlanPropertySubCategory.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/remove-fileplanpropertysubcategory +applicable: Security & Compliance +title: Remove-FilePlanPropertySubCategory +schema: 2.0.0 +--- + +# Remove-FilePlanPropertySubCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-FilePlanPropertySubCategory cmdlet to remove file plan property subcategories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-FilePlanPropertySubCategory [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Remove-FilePlanPropertySubCategory -Identity "US Tax" +``` + +This example removes the custom file plan property subcategory named US Tax. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-ForeignConnector.md b/exchange/exchange-ps/exchange/Remove-ForeignConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Remove-ForeignConnector.md rename to exchange/exchange-ps/exchange/Remove-ForeignConnector.md index e40ecb977d..d43ea4b717 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-ForeignConnector.md +++ b/exchange/exchange-ps/exchange/Remove-ForeignConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-foreignconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ForeignConnector @@ -17,13 +16,16 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ForeignConnector cmdlet to delete a Foreign connector in the Transport service of a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ForeignConnector [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-ForeignConnector [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ The Remove-ForeignConnector cmdlet deletes the object and the configuration info Although a Foreign connector is configured on a local Mailbox server, if you delete a Foreign connector, you may affect mail flow throughout the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -119,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-GlobalAddressList.md b/exchange/exchange-ps/exchange/Remove-GlobalAddressList.md similarity index 87% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-GlobalAddressList.md rename to exchange/exchange-ps/exchange/Remove-GlobalAddressList.md index d22b8bf90c..2307a60bef 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-GlobalAddressList.md +++ b/exchange/exchange-ps/exchange/Remove-GlobalAddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/remove-globaladdresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-GlobalAddressList @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-GlobalAddressList cmdlet to remove an existing global address list (GAL). -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-GlobalAddressList [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-GlobalAddressList [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +48,7 @@ This example removes the GAL named OldGAL. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-GlobalMonitoringOverride.md b/exchange/exchange-ps/exchange/Remove-GlobalMonitoringOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/server-health-and-performance/Remove-GlobalMonitoringOverride.md rename to exchange/exchange-ps/exchange/Remove-GlobalMonitoringOverride.md index 4756a56cdc..6bdf488dfa 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/exchange/Remove-GlobalMonitoringOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/remove-globalmonitoringoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-GlobalMonitoringOverride @@ -17,18 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-GlobalMonitoringOverride cmdlet to remove a managed availability global override that has been configured for a probe, monitor or responder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-GlobalMonitoringOverride [-Identity] -ItemType - -PropertyName [-Confirm] [-DomainController ] [-WhatIf] [-BuildRange ] - [-Roles ] [] +Remove-GlobalMonitoringOverride [-Identity] -ItemType -PropertyName + [-BuildRange ] + [-Confirm] + [-DomainController ] + [-Roles ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,9 +71,7 @@ Accept wildcard characters: False The ItemType parameter specifies the item type that you want to remove. It can be any of the following values: - Probe - - Monitor - - Responder ```yaml @@ -102,18 +103,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +### -BuildRange +This parameter is reserved for internal Microsoft use. ```yaml -Type: SwitchParameter +Type: String Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -122,15 +119,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -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. -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. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: Fqdn +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -140,13 +138,15 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. ```yaml -Type: SwitchParameter +Type: Fqdn Parameter Sets: (All) -Aliases: wi +Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -156,7 +156,7 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -BuildRange +### -Roles This parameter is reserved for internal Microsoft use. ```yaml @@ -172,14 +172,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Roles -This parameter is reserved for internal Microsoft use. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: String +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -193,12 +193,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/Remove-HoldCompliancePolicy.md new file mode 100644 index 0000000000..f4e942a974 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-HoldCompliancePolicy.md @@ -0,0 +1,129 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-HoldCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-HoldCompliancePolicy cmdlet to remove preservation policies from the Microsoft Purview compliance portal. + +**Note**: The Remove-HoldCompliancePolicy cmdlet has been replaced by the Remove-RetentionCompliancePolicy cmdlet. If you have scripts that use Remove-HoldCompliancePolicy, update them to use Remove-RetentionCompliancePolicy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-HoldCompliancePolicy [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +You should also remove the preservation rule that corresponds to the removed policy by using the Remove-HoldComplianceRule cmdlet. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-HoldCompliancePolicy -Identity "Regulation 123 Compliance" +``` + +This example removes the preservation policy named "Regulation 123 Compliance". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the preservation policy to remove. You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-HoldComplianceRule.md b/exchange/exchange-ps/exchange/Remove-HoldComplianceRule.md new file mode 100644 index 0000000000..5b0fea9c47 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-HoldComplianceRule.md @@ -0,0 +1,129 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-HoldComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-HoldComplianceRule cmdlet to remove preservation rules from the Microsoft Purview compliance portal. + +**Note**: The Remove-HoldComplianceRule cmdlet has been replaced by the Remove-RetentionComplianceRule cmdlet. If you have scripts that use Remove-HoldComplianceRule, update them to use Remove-RetentionComplianceRule. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-HoldComplianceRule [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +Removing a preservation rule causes the release of all Exchange mailbox and SharePoint site preservations that are associated with the rule. Removing a preservation rule also causes the corresponding preservation policy to become invalid, so you should remove it by using the Remove-HoldCompliancePolicy cmdlet. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-HoldComplianceRule -Identity "One Year Standard" +``` + +This example removes the preservation rule named "One Year Standard". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the preservation rule to remove. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/Remove-HostedContentFilterPolicy.md similarity index 83% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedContentFilterPolicy.md rename to exchange/exchange-ps/exchange/Remove-HostedContentFilterPolicy.md index 7f9fbf2e8e..b94bb23bff 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-HostedContentFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-hostedcontentfilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Remove-HostedContentFilterPolicy @@ -19,20 +18,19 @@ Use the Remove-HostedContentFilterPolicy cmdlet to remove spam filter policies ( When a policy is removed and there are rules associated with it, the rules are not removed when the policy is removed. This is by design. If you want to remove the associated rules, you need to do this separately via the Remove-HostedContentFilterRule cmdlet. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-HostedContentFilterPolicy [-Identity] [-Confirm] [-WhatIf] +Remove-HostedContentFilterPolicy [-Identity] + [-Confirm] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,9 +47,7 @@ This example removes the spam filter policy named Contoso Content Filter Policy. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -70,8 +66,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -108,12 +103,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Remove-HostedContentFilterRule.md similarity index 81% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedContentFilterRule.md rename to exchange/exchange-ps/exchange/Remove-HostedContentFilterRule.md index c15536b5f5..473b44deb4 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedContentFilterRule.md +++ b/exchange/exchange-ps/exchange/Remove-HostedContentFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-hostedcontentfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Remove-HostedContentFilterRule @@ -17,19 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Remove-HostedContentFilterRule cmdlet to remove spam filter rules (content filter rules) in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-HostedContentFilterRule [-Identity] [-Confirm] [-WhatIf] [] +Remove-HostedContentFilterRule [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +45,7 @@ This example removes the spam filter rule named Contoso Recipients. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -105,12 +101,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterPolicy.md new file mode 100644 index 0000000000..20e3e3eb7f --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterPolicy.md @@ -0,0 +1,92 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-HostedOutboundSpamFilterPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-HostedOutboundSpamFilterPolicy cmdlet to remove outbound spam filter policies from your cloud-based organization. + +When a policy is removed and there are rules associated with it, the rules are not removed when the policy is removed. This is by design. If you want to remove the associated rules, you need to do this separately via the Remove-HostedOutboundSpamFilterRule cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-HostedOutboundSpamFilterPolicy [-Identity] + [-Force] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-HostedOutboundSpamFilterPolicy -Identity "Contoso Executives" +``` + +This example removes the outbound spam filter policy named Contoso Executives. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: HostedOutboundSpamFilterPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterRule.md similarity index 80% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterRule.md index 1f8443b2df..cc89753dc3 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-hostedoutboundspamfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Remove-HostedOutboundSpamFilterRule @@ -17,19 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Remove-HostedOutboundSpamFilterRule cmdlet to remove outbound spam filter rules in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-HostedOutboundSpamFilterRule [-Identity] [-Confirm] [-WhatIf] [] +Remove-HostedOutboundSpamFilterRule [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +45,7 @@ This example removes the outbound spam filter rule named Contoso Executives. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -105,12 +101,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-HybridConfiguration.md b/exchange/exchange-ps/exchange/Remove-HybridConfiguration.md similarity index 89% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Remove-HybridConfiguration.md rename to exchange/exchange-ps/exchange/Remove-HybridConfiguration.md index e7d6745f0e..ed6b8d990c 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-HybridConfiguration.md +++ b/exchange/exchange-ps/exchange/Remove-HybridConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/remove-hybridconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-HybridConfiguration @@ -17,18 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-HybridConfiguration cmdlet to delete the HybridConfigurationActive Directory object for your on-premises Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-HybridConfiguration [-Confirm] [-DomainController ] [-WhatIf] [] +Remove-HybridConfiguration [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Removing a HybridConfiguration object should typically only be performed in circumstances where the hybrid deployment state is corrupt and under the direction of Microsoft Customer Service and Support. After removing the HybridConfiguration object, your existing hybrid deployment configuration settings aren't disabled or removed. However, when the Hybrid Configuration wizard is run again after removing the HybridConfiguration object, the wizard won't have a hybrid configuration reference point for your existing feature settings. As a result, it will automatically create a HybridConfiguration object and record the new hybrid deployment configuration feature values defined in the wizard. The feature settings associated with the hybrid deployment, such as organization relationship or Send and Receive connector parameters, which were configured with the HybridConfiguration object that's removed, aren't removed or modified until the Hybrid Configuration wizard is run again. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,8 +46,7 @@ This example removes the HybridConfiguration object for the hybrid deployment. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -100,12 +101,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPAllowListEntry.md b/exchange/exchange-ps/exchange/Remove-IPAllowListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPAllowListEntry.md rename to exchange/exchange-ps/exchange/Remove-IPAllowListEntry.md index 4f62a0f21e..07022d05d8 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPAllowListEntry.md +++ b/exchange/exchange-ps/exchange/Remove-IPAllowListEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-ipallowlistentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-IPAllowListEntry @@ -17,12 +16,15 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Remove-IPAllowListEntry cmdlet to remove IP address entries from the IP Allow list that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-IPAllowListEntry [-Identity] [-Confirm] [-Server ] [-WhatIf] +Remove-IPAllowListEntry [-Identity] + [-Confirm] + [-Server ] + [-WhatIf] [] ``` @@ -66,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -87,11 +88,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -132,12 +130,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPAllowListProvider.md b/exchange/exchange-ps/exchange/Remove-IPAllowListProvider.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPAllowListProvider.md rename to exchange/exchange-ps/exchange/Remove-IPAllowListProvider.md index 351b611d10..530652a8e2 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPAllowListProvider.md +++ b/exchange/exchange-ps/exchange/Remove-IPAllowListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-ipallowlistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-IPAllowListProvider @@ -17,13 +16,16 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Remove-IPAllowListProvider cmdlet to remove IP Allow list providers that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-IPAllowListProvider [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-IPAllowListProvider [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -44,9 +46,7 @@ This example removes the IP Allow list provider named Contoso.com. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -65,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPBlockListEntry.md b/exchange/exchange-ps/exchange/Remove-IPBlockListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPBlockListEntry.md rename to exchange/exchange-ps/exchange/Remove-IPBlockListEntry.md index 38c02fca98..81f9179a23 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPBlockListEntry.md +++ b/exchange/exchange-ps/exchange/Remove-IPBlockListEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-ipblocklistentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-IPBlocklistEntry @@ -17,12 +16,15 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Remove-IPBlockListEntry cmdlet to remove IP block list entries that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-IPBlocklistEntry [-Identity] [-Confirm] [-Server ] [-WhatIf] +Remove-IPBlocklistEntry [-Identity] + [-Confirm] + [-Server ] + [-WhatIf] [] ``` @@ -66,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -87,11 +88,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -132,12 +130,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPBlockListProvider.md b/exchange/exchange-ps/exchange/Remove-IPBlockListProvider.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPBlockListProvider.md rename to exchange/exchange-ps/exchange/Remove-IPBlockListProvider.md index aaeb7774f7..27e5a41a87 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-IPBlockListProvider.md +++ b/exchange/exchange-ps/exchange/Remove-IPBlockListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-ipblocklistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-IPBlockListProvider @@ -17,13 +16,16 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Remove-IPBlockListProvider cmdlet to remove IP Block list providers that are used by the Connection Filtering agent on Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-IPBlockListProvider [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-IPBlockListProvider [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -44,9 +46,7 @@ This example removes the IP Block list provider named Contoso.com. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -65,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-InboundConnector.md b/exchange/exchange-ps/exchange/Remove-InboundConnector.md similarity index 82% rename from exchange/exchange-ps/exchange/mail-flow/Remove-InboundConnector.md rename to exchange/exchange-ps/exchange/Remove-InboundConnector.md index ef7c75e2e6..643afa3df0 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-InboundConnector.md +++ b/exchange/exchange-ps/exchange/Remove-InboundConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-inboundconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Remove-InboundConnector @@ -17,21 +16,21 @@ This cmdlet is available only in the cloud-based service. Use the Remove-InboundConnector cmdlet to delete an Inbound connector from your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-InboundConnector [-Identity] [-Confirm] [-WhatIf] [] +Remove-InboundConnector [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +62,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -101,12 +99,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Remove-InboxRule.md b/exchange/exchange-ps/exchange/Remove-InboxRule.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Remove-InboxRule.md rename to exchange/exchange-ps/exchange/Remove-InboxRule.md index 231ea94674..78a9af6e7b 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-InboxRule.md +++ b/exchange/exchange-ps/exchange/Remove-InboxRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-inboxrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-InboxRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-InboxRule cmdlet to remove an Inbox rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,13 +27,14 @@ Remove-InboxRule [-Identity] [-DomainController ] [-Force] [-Mailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,12 +58,9 @@ This example removes all Inbox rules from the mailbox Joe@Contoso.com. 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 - - RuleIdentity property (for example, 16752869479666417665). - -- Exchange Online: `\` (for example, `rzaher\16752869479666417665`. - -- On-premises Exchange: `\` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). +- Exchange Online: `MailboxAlias\RuleIdentity` (for example, `rzaher\16752869479666417665`). +- On-premises Exchange: `MailboxCanonicalName\RuleIdentity` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). ```yaml Type: InboxRuleIdParameter @@ -79,7 +76,7 @@ Accept wildcard characters: False ``` ### -AlwaysDeleteOutlookRulesBlob -The AlwaysDeleteOutlookRulesBlob switch hides a warning message when end users or administrators use Outlook on the web or PowerShell to modify Inbox rules. You don't need to specify a value with this switch. +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 @@ -97,8 +94,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -133,7 +129,7 @@ Accept wildcard characters: False ``` ### -Force -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. +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. @@ -154,23 +150,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -207,12 +194,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/Remove-InformationBarrierPolicy.md new file mode 100644 index 0000000000..daac4a22b1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-InformationBarrierPolicy.md @@ -0,0 +1,131 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-InformationBarrierPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-InformationBarrierPolicy cmdlet to remove information barrier policies from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-InformationBarrierPolicy [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information, see [Information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-InformationBarrierPolicy -Identity HR-Sales +``` + +This example removes the information barrier policy named HR-Sales. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-IntraOrganizationConnector.md b/exchange/exchange-ps/exchange/Remove-IntraOrganizationConnector.md similarity index 88% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Remove-IntraOrganizationConnector.md rename to exchange/exchange-ps/exchange/Remove-IntraOrganizationConnector.md index 5da23ef256..6f4cb23daa 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/exchange/Remove-IntraOrganizationConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/remove-intraorganizationconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-IntraOrganizationConnector @@ -17,21 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-IntraOrganizationConnector cmdlet to remove existing Intra-Organization connectors. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-IntraOrganizationConnector [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-IntraOrganizationConnector [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Intra-Organizational connectors enable features and services between divisions in your Exchange organization. It allows for the expansion of organizational boundaries for features and services across different hosts and network boundaries, such as between Active Directory forests, between on-premises and cloud-based organizations or between tenants hosted in the same or different datacenters. -The Remove-IntraOrganizationConnector cmdlet removes the connector objects. To stop feature or service connectivity without removing the connector object, run the command Set-IntraOrganizationConnector \ -Enabled $false. +The Remove-IntraOrganizationConnector cmdlet removes the connector objects. To stop feature or service connectivity without removing the connector object, run the command: `Set-IntraOrganizationConnector -Enabled $false`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,9 +50,7 @@ This example removes the existing Intra-Organization connector named "Contoso On 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 - - Distinguished name (DN) - - GUID ```yaml @@ -69,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,12 +124,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-JournalRule.md b/exchange/exchange-ps/exchange/Remove-JournalRule.md similarity index 88% rename from exchange/exchange-ps/exchange/policy-and-compliance/Remove-JournalRule.md rename to exchange/exchange-ps/exchange/Remove-JournalRule.md index b37e42ee81..da555a20f0 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-JournalRule.md +++ b/exchange/exchange-ps/exchange/Remove-JournalRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-journalrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-JournalRule @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-JournalRule cmdlet to remove an existing journal rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-JournalRule [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-JournalRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Remove-JournalRule cmdlet removes the specified journal rule from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-Label.md b/exchange/exchange-ps/exchange/Remove-Label.md new file mode 100644 index 0000000000..7b1812a00e --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-Label.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-Label + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-Label cmdlet to remove sensitivity labels from your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-Label [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-Label -Identity "Marketing Group" +``` + +This example removes the sensitivity label named Marketing Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-LabelPolicy.md b/exchange/exchange-ps/exchange/Remove-LabelPolicy.md new file mode 100644 index 0000000000..2289247216 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-LabelPolicy.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-LabelPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-LabelPolicies cmdlet to remove sensitivity label policies from your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-LabelPolicy [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-LabelPolicy -Identity "Marketing Group" +``` + +This example removes the policy named Marketing Group. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the policy that you want to remove. You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-MailContact.md b/exchange/exchange-ps/exchange/Remove-MailContact.md similarity index 86% rename from exchange/exchange-ps/exchange/users-and-groups/Remove-MailContact.md rename to exchange/exchange-ps/exchange/Remove-MailContact.md index d7a41b95e9..8a14dbb711 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-MailContact.md +++ b/exchange/exchange-ps/exchange/Remove-MailContact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-mailcontact +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-MailContact @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MailContact cmdlet to delete existing mail contacts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,11 +25,12 @@ Remove-MailContact [-Identity] [-Confirm] [-DomainController ] [-IgnoreDefaultScope] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,15 +47,10 @@ This example removes the mail contact named John. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -74,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -112,12 +106,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -154,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-MailUser.md b/exchange/exchange-ps/exchange/Remove-MailUser.md new file mode 100644 index 0000000000..022d16da1d --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-MailUser.md @@ -0,0 +1,207 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-MailUser + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-MailUser cmdlet to remove existing mail users. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-MailUser [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-IgnoreLegalHold] + [-PermanentlyDelete] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-MailUser -Identity "Ed Meadows" +``` + +This example removes the mail user named Ed Meadows. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreLegalHold +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. + +When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed. + +After you disable or remove a mailbox, you can't include it in a discovery search. When you disable a mailbox, the mailbox is disconnected from the user account. Disconnected mailboxes and removed mailboxes are permanently deleted from the mailbox database after the deleted mailbox retention period expires. However, you can also remove a mailbox and purge it immediately from the mailbox database. Check with your organization's legal or Human Resources department before you disable or remove a mailbox that's on legal hold. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermanentlyDelete +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. + +**Notes**: + +- This switch works only on mail users that have already been deleted, but are still recoverable (known as soft-deleted mail-users) that also have a blank value for the ExternalDirectoryObjectId property. +- Use the Get-MailUser cmdlet to identify the soft-deleted mail user, and then pipe the results to the Remove-MailUser cmdlet with this switch. For example, `Get-MailUser -Identity Laura -SoftDeletedMailUser | Remove-MailUser -PermanentlyDelete`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Remove-Mailbox.md b/exchange/exchange-ps/exchange/Remove-Mailbox.md similarity index 81% rename from exchange/exchange-ps/exchange/mailboxes/Remove-Mailbox.md rename to exchange/exchange-ps/exchange/Remove-Mailbox.md index cb4f011caa..27447b1e7a 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-Mailbox.md +++ b/exchange/exchange-ps/exchange/Remove-Mailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-mailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-Mailbox @@ -17,13 +16,14 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-Mailbox cmdlet to delete mailboxes and the associated user accounts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Remove-Mailbox [-Identity] [-Permanent ] +Remove-Mailbox [-Identity] + [-Permanent ] [-Arbitration] [-AuditLog] [-AuxAuditLog] @@ -36,7 +36,9 @@ Remove-Mailbox [-Identity] [-Permanent ] [-PublicFolder] [-RemoveArbitrationMailboxWithOABsAllowed] [-RemoveLastArbitrationMailboxAllowed] - [-WhatIf] [] + [-SupervisoryReviewPolicy] + [-WhatIf] + [] ``` ### StoreMailboxIdentity @@ -54,7 +56,9 @@ Remove-Mailbox -Database -StoreMailboxIdentity ] + [-SupervisoryReviewPolicy] + [-WhatIf] + [] ``` ### Default @@ -62,10 +66,11 @@ Remove-Mailbox -Database -StoreMailboxIdentity [-PermanentlyDelete] [-Confirm] [-Force] - [-IgnoreLegalHold] [-Migration] [-PublicFolder] - [-WhatIf] [] + [-RemoveCNFPublicFolderMailboxPermanently] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -75,7 +80,7 @@ Use the Identity and Permanent parameters to disconnect the mailbox from the use Use the Disable-Mailbox cmdlet to disconnect the mailbox from the user account, but keep the user account. The mailbox is retained until the deleted mailbox retention period for the database or the mailbox expires, and then the mailbox is permanently deleted (purged). Or, you can immediately purge the disconnected mailbox by using the Database and StoreMailboxIdentity parameters on the Remove-Mailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -91,21 +96,23 @@ This example removes the mailbox and the user account for the user named John Ro Remove-Mailbox -Identity "John Rodman" -Permanent $true ``` -This example removes the mailbox and the user account for the user named John Rodman. The mailbox is immediately and permanently removed from the mailbox database. +In on-premises Exchange, this example removes the mailbox and the user account for the user named John Rodman. The mailbox is immediately and permanently removed from the mailbox database. ### Example 3 ```powershell -$Temp = Get-Mailbox | Where {$_.DisplayName -eq 'John Rodman'}; Remove-Mailbox -Database Server01\Database01 -StoreMailboxIdentity $Temp.MailboxGuid +$Temp = Get-Mailbox | Where {$_.DisplayName -eq 'John Rodman'} + +Remove-Mailbox -Database Server01\Database01 -StoreMailboxIdentity $Temp.MailboxGuid ``` -This example removes John Rodman's mailbox from the mailbox database after the mailbox has been disconnected from the user account. The example uses the Get-Mailbox cmdlet to retrieve the mailbox GUID value of the disconnected mailbox, which is required by the StoreMailboxIdentity parameter. +In on-premises Exchange, this example removes John Rodman's mailbox from the mailbox database after the mailbox has been disconnected from the user account. The example uses the Get-Mailbox cmdlet to retrieve the mailbox GUID value of the disconnected mailbox, which is required by the StoreMailboxIdentity parameter. ### Example 4 ```powershell -Get-Mailbox -Identity Laura -SoftDeleted | Remove-Mailbox -PermanentlyDelete. +Get-Mailbox -Identity Laura -SoftDeletedMailbox | Remove-Mailbox -PermanentlyDelete ``` -In Exchange Online, this example removes the specified soft-deleted mailbox mailbox. +In Exchange Online, this example removes the specified soft-deleted mailbox. ## PARAMETERS @@ -113,23 +120,14 @@ In Exchange Online, this example removes the specified soft-deleted mailbox mail The Identity parameter identifies the mailbox that you want to remove. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You can't use this parameter with the Database parameter. @@ -153,9 +151,7 @@ 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: - Name - - Distinguished name (DN) - - GUID When you use this parameter with the StoreMailboxIdentity parameter to identify and remove the mailbox, the mailbox is immediately and permanently deleted from the database, so you can't reconnect or restore the mailbox. You can't use either of these parameters with the Identity parameter. @@ -266,8 +262,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -302,7 +297,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -318,19 +315,20 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +This parameter is available only in on-premises Exchange. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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. -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +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: +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml Type: SwitchParameter Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -340,15 +338,19 @@ Accept wildcard characters: False ``` ### -IgnoreLegalHold -The IgnoreLegalHold switch specifies whether to ignore the legal hold status of the user. When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed. You don't need to specify a value with this switch. +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. + +When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed. After you disable or remove a mailbox, you can't include it in a discovery search. When you disable a mailbox, the mailbox is disconnected from the user account. Disconnected mailboxes and removed mailboxes are permanently deleted from the mailbox database after the deleted mailbox retention period expires. However, you can also remove a mailbox and purge it immediately from the mailbox database. Check with your organization's legal or Human Resources department before you disable or remove a mailbox that's on legal hold. ```yaml Type: SwitchParameter -Parameter Sets: (All) +Parameter Sets: Identity, StoreMailboxIdentity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -379,7 +381,6 @@ 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: - $true: The mailbox is immediately and permanently deleted (purged). You can't reconnect or restore the mailbox. - - $false: The mailbox disabled and retained until the deleted mailbox retention period expires. You can reconnect or restore the mailbox until the deleted mailbox retention period expires. This is the default value. ```yaml @@ -398,12 +399,11 @@ Accept wildcard characters: False ### -PermanentlyDelete This parameter is available only in the cloud-based service. -The PermanentlyDelete switch specifies whether to immediately and permanently delete (purge) the mailbox, which prevents you from recovering or restoring the mailbox. You don't need to specify a value with this switch. - -Notes: +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. -- This switch works only on mailboxes that have already been deleted, but are still recoverable (known as soft-deleted mailboxes). Use the Get-Mailbox cmdlet to identify the soft-deleted mailbox, and then pipe the results to the Remove-Mailbox cmdlet as shown in Example 3 in this topic. +**Notes**: +- This switch works only on mailboxes that have already been deleted, but are still recoverable (known as soft-deleted mailboxes). Use the Get-Mailbox cmdlet to identify the soft-deleted mailbox, and then pipe the results to the Remove-Mailbox cmdlet as shown in Example 4 in this topic. - This switch doesn't work on soft-deleted mailboxes that are on In-Place Hold or Litigation Hold (known as inactive mailboxes). ```yaml @@ -440,7 +440,9 @@ Accept wildcard characters: False ### -RemoveArbitrationMailboxWithOABsAllowed 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. When you use this switch, the arbitration mailbox is removed even if OABs are present in the mailbox. You don't need to specify a value with this switch. +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. + +When you use this switch, the arbitration mailbox is removed even if OABs are present in the mailbox. ```yaml Type: SwitchParameter @@ -455,10 +457,30 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RemoveCNFPublicFolderMailboxPermanently +This parameter is available only in the cloud-based service. + +{{ Fill RemoveCNFPublicFolderMailboxPermanently Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Default +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RemoveLastArbitrationMailboxAllowed 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. If you remove 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. +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. + +If you remove the last arbitration mailbox in the organization, you can't have user-created distribution groups or moderated recipients. ```yaml Type: SwitchParameter @@ -473,6 +495,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SupervisoryReviewPolicy +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, StoreMailboxIdentity +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -494,12 +534,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-MailboxDatabase.md b/exchange/exchange-ps/exchange/Remove-MailboxDatabase.md similarity index 88% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-MailboxDatabase.md rename to exchange/exchange-ps/exchange/Remove-MailboxDatabase.md index 64fab459fa..3e424e0421 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-MailboxDatabase.md +++ b/exchange/exchange-ps/exchange/Remove-MailboxDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/remove-mailboxdatabase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-MailboxDatabase @@ -17,12 +16,15 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-MailboxDatabase cmdlet to delete a mailbox database object. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MailboxDatabase [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-MailboxDatabase [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ If the mailbox database has a database copy, the Remove-MailboxDatabase cmdlet a The Remove-MailboxDatabase cmdlet removes only the database object from Active Directory. It doesn't remove the physical database files. You must remove the database files manually after you run the Remove-MailboxDatabase cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,9 +50,7 @@ This example removes the mailbox database MailboxDatabase01. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -69,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Remove-MailboxDatabaseCopy.md b/exchange/exchange-ps/exchange/Remove-MailboxDatabaseCopy.md similarity index 90% rename from exchange/exchange-ps/exchange/database-availability-groups/Remove-MailboxDatabaseCopy.md rename to exchange/exchange-ps/exchange/Remove-MailboxDatabaseCopy.md index 62c0be08cc..6fd45481ac 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Remove-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/exchange/Remove-MailboxDatabaseCopy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/remove-mailboxdatabasecopy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-MailboxDatabaseCopy @@ -17,25 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-MailboxDatabaseCopy cmdlet to remove a passive copy of a mailbox database. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MailboxDatabaseCopy [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-MailboxDatabaseCopy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION To use the Remove-MailboxDatabaseCopy cmdlet to remove a mailbox database copy, the following criteria must be met: - The database availability group (DAG) hosting the mailbox database must have quorum and all cluster and network functions must be healthy. - - If you're removing the last passive copy of the database, continuous replication circular logging (CRCL) must not be enabled for the specified mailbox database. If CRCL is enabled, you must first disable it. After the mailbox database copy has been removed, circular logging can be enabled. After enabling circular logging for a non-replicated mailbox database, JET circular logging is used instead of CRCL. If you aren't removing the last passive copy of a database, CRCL can remain enabled. You can't use this cmdlet to remove the active copy of a mailbox database. To remove the active copy of a mailbox database, you must first remove all passive copies of the database and then use the Remove-MailboxDatabase cmdlet to remove the active copy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). Running this cmdlet removes the mailbox database copy configuration, but doesn't delete the database copy's files. If necessary, you can manually delete those files. @@ -69,8 +70,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,12 +123,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxExportRequest.md b/exchange/exchange-ps/exchange/Remove-MailboxExportRequest.md similarity index 88% rename from exchange/exchange-ps/exchange/mailboxes/Remove-MailboxExportRequest.md rename to exchange/exchange-ps/exchange/Remove-MailboxExportRequest.md index 5be4edc5c8..6f850b68be 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxExportRequest.md +++ b/exchange/exchange-ps/exchange/Remove-MailboxExportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-mailboxexportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-MailboxExportRequest @@ -17,20 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-MailboxExportRequest cmdlet to remove fully or partially completed export requests. You can create multiple export requests for a specified mailbox provided that you specify a distinct name. Completed export requests aren't cleared automatically; they need to be removed by using this cmdlet. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). When a partially completed export request is removed, content already exported isn't removed from the PST file. If you want to start a new export request to the same file name and start with an empty PST file, you need to rename or delete the previous PST file. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Remove-MailboxExportRequest [-Identity] [-Force] +Remove-MailboxExportRequest [-Identity] + [-Force] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MigrationRequestQueue @@ -38,7 +39,8 @@ Remove-MailboxExportRequest [-Identity] [-Forc Remove-MailboxExportRequest -RequestGuid -RequestQueue [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -46,7 +48,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu The parameter set that requires the RequestGuid and RequestQueue parameters is used for Microsoft Exchange Mailbox Replication service (MRS) debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,7 +76,7 @@ This example cancels the export request by using the RequestGuid parameter for a ## PARAMETERS ### -Identity -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: \\\\. +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. @@ -111,9 +113,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -134,8 +134,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -168,7 +167,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -204,12 +205,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/Remove-MailboxFolderPermission.md new file mode 100644 index 0000000000..3dccb1d13c --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-MailboxFolderPermission.md @@ -0,0 +1,273 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-MailboxFolderPermission + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-MailboxFolderPermission cmdlet to remove folder-level permissions for users in mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Remove-MailboxFolderPermission [-Identity] -User + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +### Identity +``` +Remove-MailboxFolderPermission [-Identity] -User + [-Confirm] + [-Force] + [-SendNotificationToUser ] + [-WhatIf] + [] +``` + +### ResetDelegateUserCollection +``` +Remove-MailboxFolderPermission [-Identity] [-ResetDelegateUserCollection] + [-Confirm] + [-Force] + [-SendNotificationToUser ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can't use this cmdlet to selectively remove permissions from a user on a mailbox folder. The cmdlet removes all permissions that are assigned to the user on the specified folder. To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-MailboxFolderPermission -Identity kim@contoso.com:\Training -User john@contoso.com +``` + +This example removes John's permissions to the Training folder in Kim's mailbox. + +### Example 2 +```powershell +Remove-MailboxFolderPermission -Identity kim@contoso.com:\Calendar -ResetDelegateUserCollection +``` + +This example will clear any corrupted delegate information from Kim's mailbox. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +Example values for the Identity parameter are `john@contoso.com:\Calendar` or `John:\Marketing\Reports`. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -User +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: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, ResetDelegateUserCollection +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResetDelegateUserCollection +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`. + +When you use this switch, the value of Identity should be the user's primary calendar folder (for example, `kim@contoso.com:\Calendar`). + +```yaml +Type: SwitchParameter +Parameter Sets: ResetDelegateUserCollection +Aliases: +Applicable: Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendNotificationToUser +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: + +- $true: A notification is sent. +- $false: No notification is sent. This is the default value. + +This parameter only applies to calendar folders. + +```yaml +Type: Boolean +Parameter Sets: Identity, ResetDelegateUserCollection +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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 + +[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission) + +[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission) + +[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission) + +[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission) diff --git a/exchange/exchange-ps/exchange/Remove-MailboxIRMAccess.md b/exchange/exchange-ps/exchange/Remove-MailboxIRMAccess.md new file mode 100644 index 0000000000..688966ba55 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-MailboxIRMAccess.md @@ -0,0 +1,110 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-MailboxIRMAccess + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-MailboxIRMAccess cmdlet to allow (unblock) delegate access to IRM-protected messages in other mailboxes (shared mailboxes or user mailboxes where delegates have Full Access permission). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-MailboxIRMAccess [-Identity] -User + [] +``` + +## DESCRIPTION +> [!NOTE] +> This cmdlet works only for delegates who 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). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-MailboxIRMAccess -Identity lynette@contoso.onmicrosoft.com -User chris@contoso.onmicrosoft.com +``` + +This example removes the restriction from IRM-protected messages in Lynette's mailbox for delegate Chris. In other words, delegate Chris can now access IRM-protected messages in Lynette's mailbox. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -User +**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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxImportRequest.md b/exchange/exchange-ps/exchange/Remove-MailboxImportRequest.md similarity index 86% rename from exchange/exchange-ps/exchange/mailboxes/Remove-MailboxImportRequest.md rename to exchange/exchange-ps/exchange/Remove-MailboxImportRequest.md index 75bb721726..e4a36d24de 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxImportRequest.md +++ b/exchange/exchange-ps/exchange/Remove-MailboxImportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-mailboximportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MailboxImportRequest @@ -17,20 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MailboxImportRequest cmdlet to remove fully or partially completed import requests. Completed import requests aren't automatically cleared. Requests need to be removed by using the Remove-MailboxImportRequest cmdlet. Multiple import requests can exist against the same mailbox if you provide a distinct import request name. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +NOTE: This cmdlet is no longer supported in Exchange Online. To import a .pst file in Exchange Online, see [Use network upload to import PST files](https://learn.microsoft.com/purview/use-network-upload-to-import-pst-files). + +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). Removing a partially completed import request removes the request from the Microsoft Exchange Mailbox Replication service (MRS) job queue. Any import progress that was made until the removal won't be reverted. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Remove-MailboxImportRequest [-Identity] [-Force] +Remove-MailboxImportRequest [-Identity] + [-Force] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MigrationRequestQueue @@ -38,7 +41,8 @@ Remove-MailboxImportRequest [-Identity] [-Forc Remove-MailboxImportRequest -RequestGuid -RequestQueue [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -46,7 +50,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu The parameter set that requires the RequestGuid and RequestQueue parameters is used for MRS debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,7 +78,7 @@ This example removes all completed import requests. ## PARAMETERS ### -Identity -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: \\\\. +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. @@ -117,9 +121,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -140,8 +142,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -166,7 +167,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 201 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -176,7 +177,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -212,12 +215,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-MailboxPermission.md b/exchange/exchange-ps/exchange/Remove-MailboxPermission.md new file mode 100644 index 0000000000..b6e76be563 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-MailboxPermission.md @@ -0,0 +1,494 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-MailboxPermission + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-MailboxPermission cmdlet to remove permissions from a user's mailbox or from an Exchange Server 2016, Exchange Server 2019 or Exchange Online mail user. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### AccessRights +``` +Remove-MailboxPermission [-Identity] -AccessRights -User + [-BypassMasterAccountSid] + [-Confirm] + [-Deny] + [-DomainController ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-InheritanceType ] + [-SoftDeletedMailbox] + [-WhatIf] + [] +``` + +### Instance +``` +Remove-MailboxPermission [[-Identity] ] -Instance + [-AccessRights ] + [-Confirm] + [-Deny] + [-DomainController ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-InheritanceType ] + [-User ] + [-WhatIf] + [] +``` + +### Owner +``` +Remove-MailboxPermission [[-Identity] ] + [-BypassMasterAccountSid] + [-Confirm] + [-DomainController ] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-WhatIf] + [] +``` + +### ClearAutoMapping +``` +Remove-MailboxPermission [-Identity] [-ClearAutoMapping] + [-BypassMasterAccountSid] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-WhatIf] + [] +``` + +### ResetDefault +``` +Remove-MailboxPermission [-Identity] [-ResetDefault] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Remove-MailboxPermission cmdlet allows you to remove permissions from a user's mailbox, for example, removing full access to another user's mailbox. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-MailboxPermission -Identity "Yuuto Sasaki" -User "Pedro Pizarro" -AccessRights FullAccess -InheritanceType All +``` + +This example removes Pedro Pizarro's full access permission to Yuuto Sasaki's mailbox. + +### Example 2 +```powershell +Remove-MailboxPermission -Identity "HR Project" -ClearAutoMapping +``` + +In Exchange Online, this example excludes the HR Project mailbox from auto-mapping in Outlook for all users who have Full Access permission to the mailbox. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox where you are removing permissions. You can use any value that uniquely identifies the mailbox: For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccessRights +The AccessRights parameter specifies the permission that you want to remove from the user on the mailbox. Valid values are: + +- FullAccess +- SendAs +- ExternalAccount +- DeleteItem +- ReadPermission +- ChangePermission +- ChangeOwner + +You can specify multiple values separated by commas. + +```yaml +Type: MailboxRights[] +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +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 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: MailboxAcePresentationObject +Parameter Sets: Instance +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -User +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 +- Mail users +- Security groups + +For the best results, we recommend using the following values: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +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 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. Use this switch to exclude this mailbox from auto-mapping for all users who have Full Access permission to the mailbox. + +You can't use this switch with the User or AccessRights parameters. + +**Note**: If you use this switch in a Remove-MailboxPermission command, but the mailbox is not excluded from auto-mapping for a user, remove the user's Full Access permission by using the Remove-MailboxPermission cmdlet with the User parameter. Then, reassign the user's Full Access permission on the mailbox using the Add-MailboxPermission cmdlet with the AutoMapping parameter set to the value $false. + +```yaml +Type: SwitchParameter +Parameter Sets: ClearAutoMapping +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResetDefault +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. + +Permissions on the mailbox are reset so only the mailbox owner has Full Access permission to the mailbox. The following types of permissions are not affected: + +- Recipient permissions (for example, SendAs, SendOnBehalf and delegates). +- Mailbox folder permissions assigned using the MailboxFolderPermission cmdlets. +- Mailbox folder permissions assigned using Outlook or other MAPI clients. + +Also, because this switch removes Full Access permission from other users on the mailbox, the mailbox is no longer auto-mapped by Autodiscover into the Outlook profiles of other users. + +You can't use this switch with the User for AccessRights parameters. + +```yaml +Type: SwitchParameter +Parameter Sets: Instance +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassMasterAccountSid +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. + +Typically, you only need to use this switch in Office 365 Dedicated or ITAR legacy environments. + +```yaml +Type: SwitchParameter +Parameter Sets: AccessRights, Owner, ClearAutoMapping +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Deny +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +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. + +```yaml +Type: SwitchParameter +Parameter Sets: AccessRights, Owner, Instance +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InheritanceType +The InheritanceType parameter specifies whether permissions are inherited to folders within the mailbox. Valid values are: + +- None +- All (this is the default value) +- Children +- Descendents [sic] +- SelfAndChildren + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SoftDeletedMailbox +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. + +Soft-deleted mailboxes are deleted mailboxes that are still recoverable. + +```yaml +Type: SwitchParameter +Parameter Sets: AccessRights +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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-MailboxRepairRequest.md b/exchange/exchange-ps/exchange/Remove-MailboxRepairRequest.md new file mode 100644 index 0000000000..c9037afa2f --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-MailboxRepairRequest.md @@ -0,0 +1,147 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-MailboxRepairRequest + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Remove-MailboxRepairRequest cmdlet to remove mailbox repair requests from a mailbox database that were created using the New-MailboxRepairRequest cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-MailboxRepairRequest [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can run the Remove-MailboxRepairRequest cmdlet to remove all mailbox repair requests for a specific database, for a group of related mailbox repair requests, or for a specific mailbox repair request. Mailbox repair requests are identified by a complex GUID with the following format: `DatabaseGuid\RequestGuid\JobGuid`. The DatabaseGuid identifies the mailbox database where the mailbox being repaired is located. The RequestGuid identifies related requests that may contain more than one job if the request runs more than one task or targets more than one mailbox. The JobGuid identifies a unique job. See the examples to remove all requests on a mailbox database, remove a group of related requests that share the same RequestGuid, or remove a specific request by specifying the complete `DatabaseGuid\RequestGuid\JobGuid` value. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-MailboxRepairRequest -Database "EXCH-MBX-01" | Remove-MailboxRepairRequest +``` + +This example removes all mailbox repair requests for the mailbox database EXCH-MBX-01. + +### Example 2 +```powershell +Get-MailboxRepairRequest -Database "EXCH-MBX-02" | Format-List Identity + +Remove-MailboxRepairRequest -Identity 5b8ca3fa-8227-427f-af04-9b4f206d611f\335c2b06-321d-4e73-b2f7-3dc2b02d0df5 +``` + +This example removes all related mailbox repair requests that have the same `DatabaseGuid\RequestGuid` value. The example uses the Get-MailboxRepairRequest cmdlet to display the value of the Identity parameter for all mailbox repair request for EXCH-MBX-02 mailbox database. + +### Example 3 +```powershell +Get-MailboxRepairRequest -Database "EXCH-MBX-02" | Format-List Identity + +Remove-MailboxRepairRequest -Identity 5b8ca3fa-8227-427f-af04-9b4f206d611f\189c7852-49bd-4737-a53e-6e6caa5a183c\1d8ca58a-186f-4dc6-b481-f835b548a929 +``` + +This example deletes a specific mailbox repair request by specifying the unique `DatabaseGuid\RequestGuid\JobGuid` identity value. The example also uses the Get-MailboxRepairRequest cmdlet to display the identities of all mailbox repair request for the EXCH-MBX-02 mailbox database. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Remove-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/Remove-MailboxRestoreRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Remove-MailboxRestoreRequest.md rename to exchange/exchange-ps/exchange/Remove-MailboxRestoreRequest.md index 03eb064979..96cc00e783 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/exchange/Remove-MailboxRestoreRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-mailboxrestorerequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MailboxRestoreRequest @@ -17,16 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MailboxRestoreRequest cmdlet to remove fully or partially completed restore requests. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Remove-MailboxRestoreRequest [-Identity] [-Force] +Remove-MailboxRestoreRequest [-Identity] + [-Force] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MigrationRequestQueue @@ -34,7 +35,8 @@ Remove-MailboxRestoreRequest [-Identity] [-Fo Remove-MailboxRestoreRequest -RequestGuid -RequestQueue [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -42,7 +44,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu The parameter set that requires the RequestGuid and RequestQueue parameters is used for Microsoft Exchange Mailbox Replication service (MRS) debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,7 +72,7 @@ This example cancels the restore request by using the RequestGuid parameter for ## PARAMETERS ### -Identity -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: \\\\. +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). @@ -113,9 +115,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You must use this parameter with the RequestGuid parameter. You can't use this parameter with the Identity parameter. @@ -136,8 +136,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -172,7 +171,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -208,12 +209,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-MailboxSearch.md b/exchange/exchange-ps/exchange/Remove-MailboxSearch.md similarity index 82% rename from exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-MailboxSearch.md rename to exchange/exchange-ps/exchange/Remove-MailboxSearch.md index e1b46b0055..eca5f3db04 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-MailboxSearch.md +++ b/exchange/exchange-ps/exchange/Remove-MailboxSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/remove-mailboxsearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MailboxSearch @@ -17,19 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MailboxSearch cmdlet to remove a mailbox search. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +**Note**: As of October 2020, the \*-MailboxSearch cmdlets are retired in Exchange Online PowerShell. Use the \*-ComplianceSearch cmdlets in Security & Compliance PowerShell instead. For more information, see [Retirement of legacy eDiscovery tools](https://learn.microsoft.com/purview/ediscovery-legacy-retirement). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MailboxSearch [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-MailboxSearch [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -In on-premises Exchange and Exchange Online, mailbox searches are used for In-Place eDiscovery and In-Place Hold. You can't remove an In-Place Hold without first disabling the hold. +In on-premises Exchange, mailbox searches are used for In-Place eDiscovery and In-Place Hold. You can't remove an In-Place Hold without first disabling the hold. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxUserConfiguration.md b/exchange/exchange-ps/exchange/Remove-MailboxUserConfiguration.md similarity index 83% rename from exchange/exchange-ps/exchange/mailboxes/Remove-MailboxUserConfiguration.md rename to exchange/exchange-ps/exchange/Remove-MailboxUserConfiguration.md index 30ed7a8199..723d1efc08 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxUserConfiguration.md +++ b/exchange/exchange-ps/exchange/Remove-MailboxUserConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-mailboxuserconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MailboxUserConfiguration @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MailboxUserConfiguration cmdlet to remove user configuration items from mailboxes. Typically, after you delete a user configuration item, it's automatically recreated the next time the user uses that feature in their mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Remove-MailboxUserConfiguration [-Identity] -Mailbox - [-Confirm] [-DomainController ] [-WhatIf] [] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,11 +43,10 @@ This example removes the specified user configuration item from the mailbox juli ## PARAMETERS ### -Identity -The Identity parameter specifies the user configuration item that you want to remove. This parameter uses the syntax \\\\: +The Identity parameter specifies the user configuration item that you want to remove. This parameter uses the syntax MailboxFolder\ItemName: -- Valid values for \ are folder names (for example, Inbox or Calendar), the value Configuration, or the value Root. Wildcards (\*) aren't supported. - -- Valid values for \ start with IPM.Configuration (for example, IPM.Configuration.Aggregated.OwaUserConfiguration. Wildcards (\*) are supported. +- Valid values for MailboxFolder are folder names (for example, Inbox or Calendar), the value Configuration, or the value Root. Wildcards (\*) aren't supported. +- Valid values for ItemName start with IPM.Configuration (for example, IPM.Configuration.Aggregated.OwaUserConfiguration. Wildcards (\*) are supported. ```yaml Type: MailboxUserConfigurationIdParameter @@ -64,23 +65,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -99,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -155,12 +146,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/Remove-MalwareFilterPolicy.md similarity index 85% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-MalwareFilterPolicy.md rename to exchange/exchange-ps/exchange/Remove-MalwareFilterPolicy.md index c70abf3158..a5c3c84db4 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-MalwareFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-malwarefilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-MalwareFilterPolicy @@ -19,17 +18,21 @@ Use the Remove-MalwareFilterPolicy cmdlet to remove malware filter policies from When a policy is removed and there are rules associated with it, the rules are not removed when the policy is removed. This is by design. If you want to remove the associated rules, you need to do this separately via the Remove-MalwareFilterRule cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MalwareFilterPolicy [-Identity] [-Confirm] [-DomainController ] - [-Force] [-WhatIf] [] +Remove-MalwareFilterPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -97,13 +99,17 @@ Accept wildcard characters: False ``` ### -Force -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. +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -133,12 +139,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Remove-MalwareFilterRule.md similarity index 88% rename from exchange/exchange-ps/exchange/antispam-antimalware/Remove-MalwareFilterRule.md rename to exchange/exchange-ps/exchange/Remove-MalwareFilterRule.md index bcff0592d3..4171ff3c01 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-MalwareFilterRule.md +++ b/exchange/exchange-ps/exchange/Remove-MalwareFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-malwarefilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-MalwareFilterRule @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MalwareFilterRule cmdlet to remove malware filter rules from your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MalwareFilterRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-MalwareFilterRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +61,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedContentSettings.md b/exchange/exchange-ps/exchange/Remove-ManagedContentSettings.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedContentSettings.md rename to exchange/exchange-ps/exchange/Remove-ManagedContentSettings.md index f898b304e2..3ec37d8684 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedContentSettings.md +++ b/exchange/exchange-ps/exchange/Remove-ManagedContentSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-managedcontentsettings +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedcontentsettings applicable: Exchange Server 2010 title: Remove-ManagedContentSettings schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-ManagedContentSettings @@ -17,19 +16,22 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-ManagedContentSettings cmdlet to delete managed content settings from a managed folder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ManagedContentSettings [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-ManagedContentSettings [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION When managed content settings are removed from a managed folder, the folder effectively ceases to be a managed folder, and folder contents are no longer under messaging records management (MRM). Removing managed content settings disables any retention and journaling policies for the folder. It doesn't affect whether you can move, delete, or rename the folder, or whether the folder has a quota or policy statement that's displayed in Microsoft Outlook or Microsoft Office Outlook Web App. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedFolder.md b/exchange/exchange-ps/exchange/Remove-ManagedFolder.md similarity index 88% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedFolder.md rename to exchange/exchange-ps/exchange/Remove-ManagedFolder.md index 1be39bbf9f..7b68957f99 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedFolder.md +++ b/exchange/exchange-ps/exchange/Remove-ManagedFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-managedfolder +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedfolder applicable: Exchange Server 2010 title: Remove-ManagedFolder schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-ManagedFolder @@ -17,19 +16,22 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-ManagedFolder cmdlet to remove a managed folder from Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ManagedFolder [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-ManagedFolder [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The Remove-ManagedFolder cmdlet accepts a managed folder object or a mailbox identity as pipelined input. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/exchange/Remove-ManagedFolderMailboxPolicy.md similarity index 81% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedFolderMailboxPolicy.md rename to exchange/exchange-ps/exchange/Remove-ManagedFolderMailboxPolicy.md index 06665c1191..4cd1f7a86c 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-ManagedFolderMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-managedfoldermailboxpolicy +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedfoldermailboxpolicy applicable: Exchange Server 2010 title: Remove-ManagedFolderMailboxPolicy schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-ManagedFolderMailboxPolicy @@ -17,19 +16,23 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-ManagedFolderMailboxPolicy cmdlet to delete managed folder mailbox policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ManagedFolderMailboxPolicy [-Identity] [-Confirm] [-DomainController ] - [-Force] [-WhatIf] [] +Remove-ManagedFolderMailboxPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION If you remove a managed folder mailbox policy that's applied to users' mailboxes, the affected mailboxes may no longer have retention settings. Therefore, before using this cmdlet to remove a policy, you should determine if the managed folder mailbox policy is applied to any users, and apply another policy to those users. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -95,7 +97,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch overrides the confirmation prompt displayed by the cmdlet when the managed folder mailbox policy being removed is assigned to a mailbox user. +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. ```yaml Type: SwitchParameter @@ -131,13 +135,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### -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. +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRole.md b/exchange/exchange-ps/exchange/Remove-ManagementRole.md similarity index 82% rename from exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRole.md rename to exchange/exchange-ps/exchange/Remove-ManagementRole.md index a391df6113..60ed3913e0 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRole.md +++ b/exchange/exchange-ps/exchange/Remove-ManagementRole.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/remove-managementrole +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-ManagementRole @@ -17,19 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-ManagementRole cmdlet to remove custom management roles that you don't need anymore. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ManagementRole [-Identity] [-Confirm] [-DomainController ] [-Force] [-Recurse] - [-UnScopedTopLevel] [-WhatIf] [] +Remove-ManagementRole [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-Recurse] + [-UnScopedTopLevel] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to remove all the management role assignments from a role before you delete it. If the role is the parent of child roles, the child roles must be removed before you remove the parent role, or you must use the Recurse parameter when you remove the parent role. You can only remove custom roles. Built-in roles, such as the Mail Recipients role, can't be removed. For more information about how to remove a custom role, see [Remove a role](https://docs.microsoft.com/exchange/remove-a-role-exchange-2013-help). +You need to remove all the management role assignments from a role before you delete it. If the role is the parent of child roles, the child roles must be removed before you remove the parent role, or you must use the Recurse parameter when you remove the parent role. You can only remove custom roles. Built-in roles, such as the Mail Recipients role, can't be removed. For more information about how to remove a custom role, see [Remove a role](https://learn.microsoft.com/exchange/remove-a-role-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,7 +68,7 @@ Remove-ManagementRole "In-house scripts" -UnScopedTopLevel In on-premises Exchange, this example removes the In-house scripts unscoped top-level management role. Because this is an unscoped top-level role, the UnScopedTopLevel switch must be used. Note that the UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default. -For more information about unscoped top-level management roles, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about unscoped top-level management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). ## PARAMETERS @@ -86,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,7 +128,9 @@ Accept wildcard characters: False ### -Force This parameter is available only in the cloud-based service. -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. +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. ```yaml Type: SwitchParameter @@ -140,9 +146,9 @@ Accept wildcard characters: False ``` ### -Recurse -The Recurse parameter removes all child roles of the role specified with the Identity parameter, and then removes the specified role. +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. -The Recurse parameter removes all child roles of the specified role. We recommend that you first use the command with the WhatIf switch to confirm that the action to be taken is correct. +We recommend that you test the command with the WhatIf switch to confirm that the results will be correct. ```yaml Type: SwitchParameter @@ -158,16 +164,14 @@ Accept wildcard characters: False ``` ### -UnScopedTopLevel -This parameter is available on in on-premises Exchange. +This parameter is available only in on-premises Exchange. -By default, this parameter is only available 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +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). The UnScopedTopLevel switch specifies the role that you want to remove is an unscoped top-level role. You don't need to specify a value with this switch. Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. -You must use this switch if you want to remove an unscoped top-level role. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -202,12 +206,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRoleAssignment.md b/exchange/exchange-ps/exchange/Remove-ManagementRoleAssignment.md similarity index 84% rename from exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRoleAssignment.md rename to exchange/exchange-ps/exchange/Remove-ManagementRoleAssignment.md index bb6a7c5ac5..7540ec48ac 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/exchange/Remove-ManagementRoleAssignment.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/remove-managementroleassignment +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-ManagementRoleAssignment @@ -17,19 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-ManagementRoleAssignment cmdlet to remove management role assignments. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ManagementRoleAssignment [-Identity] [-Confirm] [-DomainController ] - [-Force] [-WhatIf] [] +Remove-ManagementRoleAssignment [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION -When you remove a role assignment, the management role group, management role assignment, user, or universal security group (USG) that was assigned the associated role can no longer access the cmdlets or parameters made available by the role. For more information about management role assignments, see [Understanding management role assignments](https://docs.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). +When you remove a role assignment, the management role group, management role assignment, user, or universal security group (USG) that was assigned the associated role can no longer access the cmdlets or parameters made available by the role. For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -106,13 +108,17 @@ Accept wildcard characters: False ``` ### -Force -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. +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. ```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 +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -142,12 +148,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-ManagementRoleEntry.md b/exchange/exchange-ps/exchange/Remove-ManagementRoleEntry.md new file mode 100644 index 0000000000..a6d8a1d54c --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ManagementRoleEntry.md @@ -0,0 +1,169 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ManagementRoleEntry + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-ManagementRoleEntry cmdlet to remove existing management role entries. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ManagementRoleEntry [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Remove-ManagementRoleEntry cmdlet removes existing role entries. However, you can't remove role entries from built-in management roles. + +For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ManagementRoleEntry "Tier 1 Help Desk\New-Mailbox" +``` + +This example removes the New-Mailbox role entry from the Tier 1 Help Desk role. + +### Example 2 +```powershell +Get-ManagementRoleEntry "Tier 1 Help Desk\*" | where {$_.Name -like 'New-*'} | foreach {Remove-ManagementRoleEntry -Identity "$($_.id)\$($_.name)"} +``` + +This example removes all the role entries that have the verb New on the Tier 1 Help Desk role by piping the output of the Get-ManagementRoleEntry cmdlet to the Where-Object cmdlet which specifies the verb filter, and then these results are piped to the Remove-ManagementRoleEntry cmdlet. + +This example forces you to acknowledge the command before proceeding (we didn't use `-Confirm:$false` or `-Force`). + +**Note**: Exchange Online PowerShell requires the complex syntax as described, and the same command also works in the Exchange Management Shell in on-premises Exchange servers. The Exchange Management Shell supports much simpler syntax for the same result, but the command doesn't work in Exchange Online PowerShell: `Get-ManagementRoleEntry "Tier 1 Help Desk\New-* | Remove-ManagementRoleEntry`. + +## PARAMETERS + +### -Identity +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). + +If the role entry name contains spaces, enclose the name in quotation marks ("). + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/role-based-access-control/Remove-ManagementScope.md b/exchange/exchange-ps/exchange/Remove-ManagementScope.md similarity index 82% rename from exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementScope.md rename to exchange/exchange-ps/exchange/Remove-ManagementScope.md index d8babed534..ec73842594 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementScope.md +++ b/exchange/exchange-ps/exchange/Remove-ManagementScope.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/remove-managementscope +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-ManagementScope @@ -17,19 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-ManagementScope cmdlet to remove an existing management scope. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ManagementScope [-Identity] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] +Remove-ManagementScope [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION -You can't remove a management scope if it's associated with a management role assignment. Use the Get-ManagementScope cmdlet to retrieve a list of orphaned scopes. For more information about regular and exclusive scopes, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +You can't remove a management scope if it's associated with a management role assignment. Use the Get-ManagementScope cmdlet to retrieve a list of orphaned scopes. For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -106,13 +108,17 @@ Accept wildcard characters: False ``` ### -Force -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. +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. ```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 +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -142,12 +148,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-MapiVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-MapiVirtualDirectory.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-MapiVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-MapiVirtualDirectory.md index 69d24704ae..936faaf305 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-MapiVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-mapivirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-MapiVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-MapiVirtualDirectory cmdlet to remove Message Application Programming Interface (MAPI) virtual directories from Exchange servers. A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-MapiVirtualDirectory [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,13 +45,11 @@ This example removes the MAPI virtual directory from the local server named Cont ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -69,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-Message.md b/exchange/exchange-ps/exchange/Remove-Message.md similarity index 86% rename from exchange/exchange-ps/exchange/mail-flow/Remove-Message.md rename to exchange/exchange-ps/exchange/Remove-Message.md index 8e08a06b9b..ecf08727f1 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-Message.md +++ b/exchange/exchange-ps/exchange/Remove-Message.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-message +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-Message @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-Message cmdlet to delete a message from a queue on a Mailbox server or an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-Message -Filter [-Server ] [-Confirm] [-WhatIf] - [-WithNDR ] [] + [-WithNDR ] + [] ``` ### Identity @@ -34,13 +34,14 @@ Remove-Message -Filter [-Server ] Remove-Message [-Identity] [-Confirm] [-WhatIf] - [-WithNDR ] [] + [-WithNDR ] + [] ``` ## DESCRIPTION A message being transmitted to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is removed from a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To remove a message from more than one queue in a single operation, you must use the Filter parameter. If you try to remove a message currently being delivered, the message status changes to PendingDelete. Message delivery isn't interrupted, but if the delivery fails and causes the message to re-enter the queue, it's then removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,50 +53,48 @@ Remove-Message -Server Server1 -Filter "FromAddress -eq 'Kweku@contoso.com'" -Wi This example removes all messages that meet the following criteria without generating NDRs: - The messages are sent by the sender Kweku@contoso.com. - - The messages are queued on the server Server1. ## PARAMETERS -### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.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 ("). +### -Identity +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: String -Parameter Sets: Filter +Type: MessageIdentity +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity). +### -Filter +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 ("). ```yaml -Type: MessageIdentity -Parameter Sets: Identity +Type: String +Parameter Sets: Filter Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,11 +114,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -176,12 +172,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-MessageClassification.md b/exchange/exchange-ps/exchange/Remove-MessageClassification.md similarity index 88% rename from exchange/exchange-ps/exchange/policy-and-compliance/Remove-MessageClassification.md rename to exchange/exchange-ps/exchange/Remove-MessageClassification.md index 557e8ec32b..430c30d775 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-MessageClassification.md +++ b/exchange/exchange-ps/exchange/Remove-MessageClassification.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-messageclassification +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MessageClassification @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MessageClassification cmdlet to delete an existing message classification instance from your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-MessageClassification [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +46,7 @@ This example removes the message classification named "My Message Classification 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 - -- Identity: Default\\ or \\\; for example, "Default\My Message Classification" or "es-ES\My Message Classification". - +- Identity: `Default\` or `\` (for example, `"Default\My Message Classification"` or `"es-ES\My Message Classification"`). - ClassificationID (GUID) ```yaml @@ -67,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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. ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationBatch.md b/exchange/exchange-ps/exchange/Remove-MigrationBatch.md similarity index 78% rename from exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationBatch.md rename to exchange/exchange-ps/exchange/Remove-MigrationBatch.md index 8ba085514c..7a3f08fc37 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationBatch.md +++ b/exchange/exchange-ps/exchange/Remove-MigrationBatch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/remove-migrationbatch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MigrationBatch @@ -17,21 +16,26 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MigrationBatch cmdlet to delete a migration batch that either isn't running or has been completed. If necessary, you can run the Get-MigrationBatch cmdlet to determine the status of a migration batch before you remove it. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MigrationBatch [[-Identity] ] [-Confirm] [-DomainController ] [-Force] [-Partition - [-WhatIf]] [] +Remove-MigrationBatch [[-Identity] ] + [-Confirm] + [-DomainController ] + [-Force] + [-Partition ] + [-WhatIf] + [] ``` ## DESCRIPTION The Remove-MigrationBatch cmdlet removes a migration batch. All subscriptions are deleted and any object related to the migration batch is also deleted. -If you use the Force parameter with this cmdlet, the individual user requests and subscriptions that were part of the removed migration batch aren't removed. You have to remove the individual migration user requests with the Remove-MigrationUser \ -Force command. +If you use the Force switch with this cmdlet, the individual user requests and subscriptions that were part of the removed migration batch aren't removed. You need to remove the individual migration user requests with the command: `Remove-MigrationUser -Force`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -108,9 +111,11 @@ Accept wildcard characters: False ### -Force This parameter is available only in on-premises Exchange. -The Force switch specifies whether to remove a corrupted migration batch. Corrupted migration batches have a status of Corrupted. If you try to remove a corrupted migration batch without using this switch, you receive an error saying the migrated batch can't be found. +The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. + +Use this switch to remove a corrupted migration batch. Corrupted migration batches have a status of Corrupted. If you try to remove a corrupted migration batch without using this switch, you receive an error saying the migrated batch can't be found. -If you use this parameter to remove a corrupted migration batch, the individual user requests (also called job items) and subscriptions that were part of the removed migration batch aren't removed. You have to remove the individual migration user requests with the Remove-MigrationUser \ -Force command. +If you use this switch to remove a corrupted migration batch, the individual user requests (also called job items) and subscriptions that were part of the removed migration batch aren't removed. You need to remove the individual migration user requests with the command: `Remove-MigrationUser -Force`. ```yaml Type: SwitchParameter @@ -164,12 +169,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationEndpoint.md b/exchange/exchange-ps/exchange/Remove-MigrationEndpoint.md similarity index 86% rename from exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationEndpoint.md rename to exchange/exchange-ps/exchange/Remove-MigrationEndpoint.md index 287f63327b..9484d7d7e2 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationEndpoint.md +++ b/exchange/exchange-ps/exchange/Remove-MigrationEndpoint.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/remove-migrationendpoint +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MigrationEndpoint @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MigrationEndpoint cmdlet to remove existing migration endpoints for source or destination servers for cutover or staged Exchange migrations, IMAP migrations and remote moves. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,15 +25,16 @@ Remove-MigrationEndpoint [-Identity] [-Confirm] [-DomainController ] [-Partition ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Use the Remove-MigrationEndpoint cmdlet to remove an existing migration endpoint. -For more information about migration endpoints, see [Set-MigrationEndpoint](https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-migrationendpoint) and [New-MigrationEndpoint](https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-migrationendpoint). +For more information about migration endpoints, see [Set-MigrationEndpoint](https://learn.microsoft.com/powershell/module/exchange/set-migrationendpoint) and [New-MigrationEndpoint](https://learn.microsoft.com/powershell/module/exchange/new-migrationendpoint). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -66,8 +66,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -110,7 +109,7 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -140,12 +139,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationUser.md b/exchange/exchange-ps/exchange/Remove-MigrationUser.md similarity index 83% rename from exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationUser.md rename to exchange/exchange-ps/exchange/Remove-MigrationUser.md index 52134a2fb1..61036e2269 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationUser.md +++ b/exchange/exchange-ps/exchange/Remove-MigrationUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/remove-migrationuser +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MigrationUser @@ -17,16 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MigrationUser cmdlet to remove a migration user from a batch. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MigrationUser [-Identity] [-Confirm] [-DomainController ] [-Force] [-Partition ] [-WhatIf] [] +Remove-MigrationUser [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-Partition ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -96,7 +100,9 @@ Accept wildcard characters: False ### -Force This parameter is available only in on-premises Exchange. -The Force switch specifies that some specific checks and removal steps should be skipped and that the migration user should be forcibly removed. This parameter is used to work around issues where the migration user needs to be removed to fix issues when the user or data is corrupted, or to prevent such issues from occurring. +The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. + +Use this switch to work around user or data corruption issues. Specific checks and removal steps are skipped to forcibly remove the migration user. ```yaml Type: SwitchParameter @@ -150,12 +156,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Remove-MobileDevice.md b/exchange/exchange-ps/exchange/Remove-MobileDevice.md similarity index 78% rename from exchange/exchange-ps/exchange/devices/Remove-MobileDevice.md rename to exchange/exchange-ps/exchange/Remove-MobileDevice.md index da749c160b..dc6843cec8 100644 --- a/exchange/exchange-ps/exchange/devices/Remove-MobileDevice.md +++ b/exchange/exchange-ps/exchange/Remove-MobileDevice.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-mobiledevice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MobileDevice @@ -17,44 +16,47 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MobileDevice cmdlet to remove mobile device partnerships that identify the devices that are configured to synchronize with user mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MobileDevice [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-MobileDevice [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The Remove-MobileDevice cmdlet is useful for removing mobile devices that no longer synchronize successfully with the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Remove-MobileDevice -Identity WM_JeffHay +Remove-MobileDevice -Identity JeffHay\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac ``` -This example removes the mobile device partnership for the device named WM\_JeffHay. +This example removes the mobile device partnership for the specified mobile device. ### Example 2 ```powershell -Remove-MobileDevice -Identity iPhone_TonySmith -Confirm:$false +Remove-MobileDevice -Identity TonySmith\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac -Confirm:$false ``` -This example removes the mobile device partnership for the device named iPhone\_TonySmith and doesn't display the confirm prompt. +This example removes the mobile device partnership for the specified device and doesn't display the confirm prompt. ## PARAMETERS ### -Identity -The Identity parameter specifies the mobile device partnership that you want to remove. You can use any value that uniquely identifies the mobile device. For example: +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: -- GUID - -- DeviceID +- Identity (`\ExchangeActiveSyncDevices\` for example, `CarlosM\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac`) +- Distinguished name (DN) +- GUID (same as ExchangeObjectId) ```yaml Type: MobileDeviceIdParameter @@ -72,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -128,12 +129,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Remove-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/exchange/Remove-MobileDeviceMailboxPolicy.md similarity index 87% rename from exchange/exchange-ps/exchange/devices/Remove-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/exchange/Remove-MobileDeviceMailboxPolicy.md index 18af4d8fd2..24f850cef1 100644 --- a/exchange/exchange-ps/exchange/devices/Remove-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-MobileDeviceMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-mobiledevicemailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MobileDeviceMailboxPolicy @@ -17,19 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MobileDeviceMailboxPolicy cmdlet to remove mobile device mailbox policies from Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-MobileDeviceMailboxPolicy [-Identity] [-Confirm] [-DomainController ] - [-Force] [-WhatIf] [] +Remove-MobileDeviceMailboxPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION A Mobile Device mailbox policy is a group of settings that specifies how mobile phones connect to Exchange. Exchange supports multiple mobile device mailbox policies. The Remove-MobileDeviceMailboxPolicy cmdlet removes a specific mobile device mailbox policy. If any users are assigned to the policy when you remove it, the Remove-MobileDeviceMailboxPolicy cmdlet fails. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,9 +63,7 @@ This example removes the mobile device mailbox policy named Management and bypas 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 - - Distinguished name (DN) - - GUID ```yaml @@ -81,8 +82,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,7 +117,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -153,12 +155,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Remove-MoveRequest.md b/exchange/exchange-ps/exchange/Remove-MoveRequest.md similarity index 85% rename from exchange/exchange-ps/exchange/move-and-migration/Remove-MoveRequest.md rename to exchange/exchange-ps/exchange/Remove-MoveRequest.md index df379fd2b1..ff8f5e3203 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Remove-MoveRequest.md +++ b/exchange/exchange-ps/exchange/Remove-MoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/remove-moverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-MoveRequest @@ -17,17 +16,19 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-MoveRequest cmdlet to cancel a mailbox move initiated using the New-MoveRequest cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Remove-MoveRequest [-Identity] [-Force] +Remove-MoveRequest [-Identity] + [-Force] [-Confirm] [-DomainController ] [-ProxyToMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MigrationMoveRequestQueue @@ -36,17 +37,18 @@ Remove-MoveRequest -MailboxGuid -MoveRequestQueue [-Confirm] [-DomainController ] [-ProxyToMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -In coexistence environments with Exchange 2010 and newer versions of Exchange, don't run a newer version of Remove-MoveRequest to clear completed mailbox move requests between Exchange 2010 databases as documented in [Clear or Remove Move Requests](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/dd351276(v=exchg.141)). Otherwise, you might delete the mailbox that you just moved. In coexistence environments, only use the Remove-MoveRequest cmdlet on Exchange 2010 servers to clear completed Exchange 2010 move requests. For mailbox moves from an Exchange 2010 database to an Exchange 2016 database, you can safely run Remove-MoveRequest on the Exchange 2016 server. +In coexistence environments with Exchange 2010 and newer versions of Exchange, don't run a newer version of Remove-MoveRequest to clear completed mailbox move requests between Exchange 2010 databases as documented in [Clear or Remove Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd351276(v=exchg.141)). Otherwise, you might delete the mailbox that you just moved. In coexistence environments, only use the Remove-MoveRequest cmdlet on Exchange 2010 servers to clear completed Exchange 2010 move requests. For mailbox moves from an Exchange 2010 database to an Exchange 2016 database, you can safely run Remove-MoveRequest on the Exchange 2016 server. In Exchange 2010, you need to use the Remove-MoveRequest cmdlet on completed move requests to clear the InTransit flag from the mailbox. This step isn't required for mailbox moves in newer versions of Exchange where the Remove-MoveRequest is only used to cancel existing move requests. The MoveRequestQueue and MailboxGuid parameters are for debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,17 +74,11 @@ The MailboxGuid and MoveRequestQueue parameters are for debugging purposes only. The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values: - GUID - - Distinguished name (DN) - - Domain\\Account - - User principal name (UPN) - - Legacy Exchange DN - - SMTP address - - Alias You can't use this parameter with the MailboxGuid or MoveRequestQueue parameters. @@ -126,9 +122,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -149,8 +143,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -185,7 +178,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -206,23 +201,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -259,12 +245,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Remove-OMEConfiguration.md b/exchange/exchange-ps/exchange/Remove-OMEConfiguration.md similarity index 78% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Remove-OMEConfiguration.md rename to exchange/exchange-ps/exchange/Remove-OMEConfiguration.md index 9f3abfd049..20d726ee54 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Remove-OMEConfiguration.md +++ b/exchange/exchange-ps/exchange/Remove-OMEConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/Remove-OMEConfiguration +online version: https://learn.microsoft.com/powershell/module/exchange/remove-omeconfiguration applicable: Exchange Online title: Remove-OMEConfiguration schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Remove-OMEConfiguration @@ -15,23 +14,21 @@ monikerRange: "exchonline-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Remove-OMEConfiguration cmdlet to remove custom Microsoft Office 365 Message Encryption (OME) configurations. You can't use this cmdlet to remove the default OME configuration. +Use the Remove-OMEConfiguration cmdlet to remove custom Microsoft Purview Message Encryption configurations. You can't use this cmdlet to remove the default OME configuration. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Remove-OMEConfiguration [-Identity] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +60,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -101,12 +97,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-OabVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-OabVirtualDirectory.md similarity index 83% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-OabVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-OabVirtualDirectory.md index 4a6f2377fe..24791b7b37 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-OabVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-OabVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/remove-oabvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-OabVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-OabVirtualDirectory cmdlet to remove offline address book (OAB) virtual directories from Internet Information Services (IIS) on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,13 +25,14 @@ Remove-OabVirtualDirectory [-Identity] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Some situations require the removal of an OAB virtual directory. For example, to uninstall an Exchange server that contains an OAB distribution points list, you need to remove the OAB virtual directory and then re-create it on another server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,13 +55,11 @@ This example removes the default OAB virtual directory from Server1. ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -79,8 +77,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -113,7 +110,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -149,12 +148,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-OfflineAddressBook.md b/exchange/exchange-ps/exchange/Remove-OfflineAddressBook.md similarity index 85% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-OfflineAddressBook.md rename to exchange/exchange-ps/exchange/Remove-OfflineAddressBook.md index ce4adc835a..b9d780e4f5 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Remove-OfflineAddressBook.md +++ b/exchange/exchange-ps/exchange/Remove-OfflineAddressBook.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/remove-offlineaddressbook +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-OfflineAddressBook @@ -17,21 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-OfflineAddressBook cmdlet to remove (delete) offline address books (OABs). -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-OfflineAddressBook [-Identity] [-Confirm] [-DomainController ] - [-Force] [-WhatIf] [] +Remove-OfflineAddressBook [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION If you remove the default OAB, you need to configure another OAB as the default by using the IsDefault parameter on the New-OfflineAddressBook or Set-OfflineAddressBook cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,9 +51,7 @@ This example removes the OAB named Contoso Executives. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -69,8 +70,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -105,7 +105,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -141,12 +143,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/Remove-OnPremisesOrganization.md similarity index 82% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Remove-OnPremisesOrganization.md rename to exchange/exchange-ps/exchange/Remove-OnPremisesOrganization.md index 8a6517fda2..a6196d357b 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-OnPremisesOrganization.md +++ b/exchange/exchange-ps/exchange/Remove-OnPremisesOrganization.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/remove-onpremisesorganization +online version: https://learn.microsoft.com/powershell/module/exchange/remove-onpremisesorganization applicable: Exchange Online title: Remove-OnPremisesOrganization schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Remove-OnPremisesOrganization @@ -15,24 +14,23 @@ monikerRange: "exchonline-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Remove-OnPremisesOrganization cmdlet to remove an OnPremisesOrganization object in a Microsoft Office 365 tenant. +Use the Remove-OnPremisesOrganization cmdlet to remove an OnPremisesOrganization object in a Microsoft 365 tenant. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-OnPremisesOrganization [-Identity] [-Confirm] [-WhatIf] +Remove-OnPremisesOrganization [-Identity] + [-Confirm] + [-WhatIf] [] ``` ## DESCRIPTION Removing an OnPremisesOrganization object should only be used in circumstances where the hybrid deployment state is corrupt and under the direction and supervision of Microsoft Customer Service and Support. After removing the OnPremisesOrganization object, any related hybrid deployment configured with this object won't be functional and will need to be re-created and reconfigured. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,7 +39,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Remove-OnPremisesOrganization -Identity ExchangeMail ``` -This example removes the ExchangeMail OnPremisesOrganization object in an Office 365 tenant. +This example removes the ExchangeMail OnPremisesOrganization object in a Microsoft 365 organization. ## PARAMETERS @@ -49,9 +47,7 @@ This example removes the ExchangeMail OnPremisesOrganization object in an Office The Identity parameter specifies the identity of the on-premises organization object. You can use the following values: - Canonical name - - GUID - - Name ```yaml @@ -70,8 +66,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -108,12 +103,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-OrganizationRelationship.md b/exchange/exchange-ps/exchange/Remove-OrganizationRelationship.md similarity index 85% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-OrganizationRelationship.md rename to exchange/exchange-ps/exchange/Remove-OrganizationRelationship.md index 7a1162a455..0598e9d220 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-OrganizationRelationship.md +++ b/exchange/exchange-ps/exchange/Remove-OrganizationRelationship.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-organizationrelationship -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-OrganizationRelationship @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-OrganizationRelationship cmdlet to remove the organization relationship with an external Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-OrganizationRelationship [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-OrganizationRelationship [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Remove-OrganizationRelationship cmdlet removes the organization relationship objects. To stop sharing information without removing the organization relationship objects, disable the organization relationship by using the Set-OrganizationRelationship cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,16 +48,14 @@ This example removes the organization relationship Contoso using the Identity pa 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 - - GUID - - Name ```yaml Type: OrganizationRelationshipIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -67,15 +67,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -109,7 +108,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -123,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-OrganizationSegment.md b/exchange/exchange-ps/exchange/Remove-OrganizationSegment.md new file mode 100644 index 0000000000..0d1f0c04fb --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-OrganizationSegment.md @@ -0,0 +1,114 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-OrganizationSegment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-OrganizationSegment cmdlet to remove organization segments from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-OrganizationSegment [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-OrganizationSegment -Identity "Engineering Group" +``` + +This example removes the organization segment named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes) + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-OutboundConnector.md b/exchange/exchange-ps/exchange/Remove-OutboundConnector.md similarity index 82% rename from exchange/exchange-ps/exchange/mail-flow/Remove-OutboundConnector.md rename to exchange/exchange-ps/exchange/Remove-OutboundConnector.md index 01cb7f2e8d..7cfabaff38 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-OutboundConnector.md +++ b/exchange/exchange-ps/exchange/Remove-OutboundConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-outboundconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Remove-OutboundConnector @@ -17,21 +16,21 @@ This cmdlet is available only in the cloud-based service. Use the Remove-OutboundConnector cmdlet to delete an Outbound connector from your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-OutboundConnector [-Identity] [-Confirm] [-WhatIf] [] +Remove-OutboundConnector [-Identity] + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION Outbound connectors send email messages to remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +62,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -101,12 +99,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Remove-OutlookProtectionRule.md similarity index 87% rename from exchange/exchange-ps/exchange/policy-and-compliance/Remove-OutlookProtectionRule.md rename to exchange/exchange-ps/exchange/Remove-OutlookProtectionRule.md index f0b66c175e..2fd3e45e05 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-OutlookProtectionRule.md +++ b/exchange/exchange-ps/exchange/Remove-OutlookProtectionRule.md @@ -1,35 +1,39 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-outlookprotectionrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-OutlookProtectionRule ## SYNOPSIS +**Note**: This cmdlet is no longer supported in the cloud-based service. + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Remove-OutlookProtectionRule cmdlet to remove Outlook protection rules. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-OutlookProtectionRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-OutlookProtectionRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -Outlook protection rules use an Active Directory Rights Management Services (AD RMS) rights template to automatically apply Information Rights Management (IRM) protection to messages before they're sent. For more information, see [Outlook protection rules](https://docs.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). +Outlook protection rules use an Active Directory Rights Management Services (AD RMS) rights template to automatically apply Information Rights Management (IRM) protection to messages before they're sent. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,8 +72,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,12 +127,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Remove-OutlookProvider.md b/exchange/exchange-ps/exchange/Remove-OutlookProvider.md similarity index 88% rename from exchange/exchange-ps/exchange/client-access/Remove-OutlookProvider.md rename to exchange/exchange-ps/exchange/Remove-OutlookProvider.md index 6579d891f5..1d6410cdd9 100644 --- a/exchange/exchange-ps/exchange/client-access/Remove-OutlookProvider.md +++ b/exchange/exchange-ps/exchange/Remove-OutlookProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/remove-outlookprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-OutlookProvider @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-OutlookProvider cmdlet to delete the AutoDiscoverConfig object from Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-OutlookProvider [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-OutlookProvider [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION The Remove-OutlookProvider cmdlet deletes the AutoDiscoverConfig object under the Global Settings object in Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Remove-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/Remove-OwaMailboxPolicy.md similarity index 82% rename from exchange/exchange-ps/exchange/client-access/Remove-OwaMailboxPolicy.md rename to exchange/exchange-ps/exchange/Remove-OwaMailboxPolicy.md index 545ea6e02e..b9f7e4ee5e 100644 --- a/exchange/exchange-ps/exchange/client-access/Remove-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-OwaMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/remove-owamailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-OwaMailboxPolicy @@ -17,19 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-OwaMailboxPolicy cmdlet to remove Outlook on the web mailbox policies from the organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-OwaMailboxPolicy [-Identity] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] +Remove-OwaMailboxPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION -Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). +Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,9 +63,7 @@ This example removes the mailbox policy named Corporate for the tenant Contoso i 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 - - Distinguished name (DN) - - GUID ```yaml @@ -81,8 +82,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,7 +117,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -153,12 +155,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-OwaVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-OwaVirtualDirectory.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-OwaVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-OwaVirtualDirectory.md index 383a47f427..f97d5d7436 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-OwaVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-owavirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-OwaVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-OwaVirtualDirectory cmdlet to remove Outlook on the web virtual directories from Internet Information Services (IIS) on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,19 +24,19 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-OwaVirtualDirectory [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You might be required to use the Remove-OwaVirtualDirectory cmdlet in the following situations: - The Get-OwaVirtualDirectory cmdlet detects an Outlook on the web virtual directory deleted in IIS but not deleted in Active Directory. These abandoned Outlook on the web virtual directory objects are known as Active Directory orphans. We recommend that you remove these orphans by using the Remove-OwaVirtualDirectory cmdlet. - - You are troubleshooting an Outlook on the web configuration issue that requires you to delete the existing Outlook on the web virtual directory and then re-create the Outlook on the web virtual directory. Remove-OwaVirtualDirectory permanently removes an Outlook on the web virtual directory or directories. When you use this cmdlet, make sure that you don't accidentally delete the default Outlook on the web virtual directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,13 +52,11 @@ This example removes the specified Outlook on the web virtual directory from the ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -77,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -131,12 +127,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Remove-PartnerApplication.md b/exchange/exchange-ps/exchange/Remove-PartnerApplication.md similarity index 87% rename from exchange/exchange-ps/exchange/organization/Remove-PartnerApplication.md rename to exchange/exchange-ps/exchange/Remove-PartnerApplication.md index d1c4f7ec3c..2eb9caf5e4 100644 --- a/exchange/exchange-ps/exchange/organization/Remove-PartnerApplication.md +++ b/exchange/exchange-ps/exchange/Remove-PartnerApplication.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/remove-partnerapplication +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-PartnerApplication @@ -17,21 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-PartnerApplication cmdlet to remove a partner application configuration. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-PartnerApplication [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-PartnerApplication [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You can configure partner applications such as Microsoft SharePoint to access Exchange resources. Use the Remove-PartnerApplication cmdlet to remove a partner application configuration if the application no longer needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://docs.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). +You can configure partner applications such as Microsoft SharePoint to access Exchange resources. Use the Remove-PartnerApplication cmdlet to remove a partner application configuration if the application no longer needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -119,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-PhishSimOverridePolicy.md b/exchange/exchange-ps/exchange/Remove-PhishSimOverridePolicy.md new file mode 100644 index 0000000000..590d704a0c --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-PhishSimOverridePolicy.md @@ -0,0 +1,147 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-PhishSimOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-PhishSimOverridePolicy cmdlet to remove third-party phishing simulation override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-PhishSimOverridePolicy [-Identity] + [-Confirm] + [-DomainController ] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-PhishSimOverridePolicy | Remove-PhishSimOverridePolicy +``` + +This example removes the phishing simulation override policy. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +Use the Get-PhishSimOverridePolicy cmdlet to find the values. The only available policy is named PhishSimOverridePolicy. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-PolicyTipConfig.md b/exchange/exchange-ps/exchange/Remove-PolicyTipConfig.md similarity index 82% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-PolicyTipConfig.md rename to exchange/exchange-ps/exchange/Remove-PolicyTipConfig.md index 2afa351227..45d9e9b72c 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-PolicyTipConfig.md +++ b/exchange/exchange-ps/exchange/Remove-PolicyTipConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-policytipconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-PolicyTipConfig @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-PolicyTipConfig cmdlet to remove custom data loss prevention (DLP) Policy Tips from your organization. You can't remove built-in Policy Tips. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-PolicyTipConfig [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-PolicyTipConfig [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,12 +52,9 @@ This example removes all the custom Russian Policy Tips. ### -Identity 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 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://docs.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. - +- `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. - The value Url - - GUID - - Distinguished name (DN) ```yaml @@ -74,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,12 +128,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-PowerShellVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-PowerShellVirtualDirectory.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-PowerShellVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-PowerShellVirtualDirectory.md index 081aecdefd..56801944fd 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-PowerShellVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-powershellvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-PowerShellVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-PowerShellVirtualDirectory cmdlet to remove existing Windows PowerShell virtual directories from Internet Information Services (IIS) on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,13 +24,14 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-PowerShellVirtualDirectory [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Although it's possible to remove a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,13 +49,11 @@ Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confi ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -73,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -127,12 +124,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-ProtectionAlert.md b/exchange/exchange-ps/exchange/Remove-ProtectionAlert.md new file mode 100644 index 0000000000..f4edc74c13 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ProtectionAlert.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ProtectionAlert + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-ProtectionAlert cmdlet to remove alert policies from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ProtectionAlert [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ProtectionAlert -Identity "External User File Activities" +``` + +This example removes the specified alert policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolder.md b/exchange/exchange-ps/exchange/Remove-PublicFolder.md similarity index 83% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolder.md rename to exchange/exchange-ps/exchange/Remove-PublicFolder.md index 01d50c3d9b..036d6a15da 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolder.md +++ b/exchange/exchange-ps/exchange/Remove-PublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-publicfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-PublicFolder @@ -19,7 +18,7 @@ Use the Remove-PublicFolder cmdlet to remove an existing public folder. The Remove-PublicFolder cmdlet removes the public folder data from all servers in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,13 +26,15 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-PublicFolder [-Identity] [-Confirm] [-DomainController ] + [-Mailbox ] [-Recurse] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,7 +55,7 @@ This example deletes the public folder Directory Folder and all its child public ## PARAMETERS ### -Identity -The Identity parameter specifies the name and path of the public folder you want to remove. A valid value uses the syntax: \\\\\\\\...\\\\\\. For example, "\\Customer Discussion" or "\\Engineering\\Customer Discussion". +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 @@ -72,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -107,8 +107,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Mailbox +This parameter is available only in the cloud-based service. + +{{ Fill Mailbox Description }} + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Recurse -The Recurse switch specifies whether all subfolders of the specified folder should be removed. If the Recurse switch isn't specified and the public folder has subfolders, the command doesn't run and an error message is returned. +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. ```yaml Type: SwitchParameter @@ -124,16 +144,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -172,12 +189,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/exchange/Remove-PublicFolderAdministrativePermission.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderAdministrativePermission.md rename to exchange/exchange-ps/exchange/Remove-PublicFolderAdministrativePermission.md index c00ecb0158..b1b0afb2e2 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/exchange/Remove-PublicFolderAdministrativePermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-publicfolderadministrativepermission +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderadministrativepermission applicable: Exchange Server 2010 title: Remove-PublicFolderAdministrativePermission schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-PublicFolderAdministrativePermission @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-PublicFolderAdministrativePermission cmdlet to remove administrative permissions for a public folder or a public folder hierarchy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,25 +28,26 @@ Remove-PublicFolderAdministrativePermission [-Identity] ] [-InheritanceType ] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Instance ``` -Remove-PublicFolderAdministrativePermission -Instance +Remove-PublicFolderAdministrativePermission [[-Identity] ] -Instance [-AccessRights ] [-Confirm] [-Deny] [-DomainController ] - [[-Identity] ] [-InheritanceType ] [-Server ] [-User ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,25 +82,18 @@ Accept wildcard characters: False The AccessRights parameter specifies the rights being removed. Valid values include: - None The administrator doesn't have any rights to modify public folder attributes. - - ModifyPublicFolderACL The administrator has the right to modify client access permissions for the specified folder. - - ModifyPublicFolderAdminACL The administrator has the right to modify administrator permissions for the specified public folder. - - ModifyPublicFolderDeletedItemRetention The administrator has the right to modify the Public Folder Deleted Item Retention attributes (RetainDeletedItemsFor or UseDatabaseRetentionDefaults). - - ModifyPublicFolderExpiry The administrator has the right to modify the Public Folder Expiration attributes (AgeLimitUseDatabaseAgeDefaults). - - ModifyPublicFolderQuotas The administrator has the right to modify the Public Folder Quota attributes (MaxItemSize, PostQuota, PostWarningQuota, or UseDatabaseQuotaDefaults). - - ModifyPublicFolderReplicaList The administrator has the right to modify the replica list attribute for the specified public folder (Replicas). - - AdministerInformationStore The administrator has the right to modify all other public folder properties not defined previously. - - ViewInformationStore The administrator has the right to view public folder properties. - - AllExtendedRights The administrator has the right to modify all public folder properties. +You can specify multiple values separated by commas. + ```yaml Type: MultiValuedProperty Parameter Sets: Identity @@ -157,7 +150,24 @@ Accept wildcard characters: False ``` ### -User -The User parameter specifies the user principal name (UPN), domain\\user, or alias of the user for whom rights are being removed. +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 +- Mail users +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) ```yaml Type: SecurityPrincipalIdParameter @@ -188,8 +198,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -206,7 +215,7 @@ Accept wildcard characters: False ``` ### -Deny -The Deny parameter specifies whether to deny the permission specified. +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 @@ -241,14 +250,10 @@ Accept wildcard characters: False The InheritanceType parameter specifies the type of inheritance. Valid values are: - None - -- All - -- Descendents - -- SelfAndChildren - +- All (this is the default value) - Children +- Descendents [sic] +- SelfAndChildren ```yaml Type: ActiveDirectorySecurityInheritance @@ -267,11 +272,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -310,12 +312,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderClientPermission.md b/exchange/exchange-ps/exchange/Remove-PublicFolderClientPermission.md similarity index 79% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderClientPermission.md rename to exchange/exchange-ps/exchange/Remove-PublicFolderClientPermission.md index 0946e32119..726354e79b 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/exchange/Remove-PublicFolderClientPermission.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-publicfolderclientpermission +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-PublicFolderClientPermission @@ -17,18 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-PublicFolderClientPermission cmdlet to remove permissions from public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-PublicFolderClientPermission [-Identity] -AccessRights - -User [-Confirm] [-DomainController ] [-Server ] - [-WhatIf] [] +Remove-PublicFolderClientPermission [-Identity] -AccessRights -User + [-Confirm] + [-DomainController ] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,50 +50,55 @@ This example removes permission for the user Chris to the public folder My Publi ## PARAMETERS -### -AccessRights -This parameter is available or functional only in Exchange Server 2010. +### -Identity +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. -The AccessRights parameter specifies the rights being removed. This parameter accepts the following values: +You can omit the parameter label so that only the public folder name or GUID is supplied. -- ReadItems: The user has the right to read items within the specified public folder. +```yaml +Type: PublicFolderIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -- CreateItems: The user has the right to create items within the specified public folder. +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` -- EditOwnedItems: The user has the right to edit the items that the user owns in the specified public folder. +### -AccessRights +This parameter is available only in Exchange Server 2010. -- DeleteOwnedItems: The user has the right to delete items that the user owns in the specified public folder. +The AccessRights parameter specifies the rights that you want to remove from the user on the public folder. -- EditAllItems: The user has the right to edit all items in the specified 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. -- DeleteAllItems: The user has the right to delete all items in the specified public folder. +The following individual permissions are available: +- CreateItems: The user has the right to create items within the specified public folder. - CreateSubfolders: The user has the right to create subfolders in the specified public folder. - -- FolderOwner: The user is the owner of the specified public folder. The user has the right to view and move the public folder and create subfolders. The user can't read items, edit items, delete items, or create items. - +- DeleteAllItems: The user has the right to delete all items in the specified public folder. +- DeleteOwnedItems: The user has the right to delete items that the user owns in the specified public folder. +- EditAllItems: The user has the right to edit all items in the specified public folder. +- EditOwnedItems: The user has the right to edit the items that the user owns in the specified public folder. - FolderContact: The user is the contact for the specified public folder. - +- FolderOwner: The user is the owner of the specified public folder. The user has the right to view and move the public folder and create subfolders. The user can't read items, edit items, delete items, or create items. - FolderVisible: The user can view the specified public folder, but can't read or edit items within the specified public folder. +- ReadItems: The user has the right to read items within the specified public folder. In addition to the access rights, you can create rights based upon roles, which includes multiple access rights. This parameter accepts the following values for roles: -- None: FolderVisible - -- Owner: CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems - -- PublishingEditor: CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems - -- Editor: CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems - -- PublishingAuthor: CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems - -- Author: CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems - -- NonEditingAuthor: CreateItems, ReadItems, FolderVisible - -- Reviewer: ReadItems, FolderVisible - +- Author: CreateItems, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems - Contributor: CreateItems, FolderVisible +- Editor: CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems +- None: FolderVisible +- NonEditingAuthor: CreateItems, DeleteOwnedItems, FolderVisible, ReadItems +- Owner: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderContact, FolderOwner, FolderVisible, ReadItems +- PublishingAuthor: CreateItems, CreateSubfolders, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems +- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems +- Reviewer: FolderVisible, ReadItems ```yaml Type: MultiValuedProperty @@ -106,26 +113,13 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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. - -```yaml -Type: PublicFolderIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -User +The User parameter specifies the user whose permissions are being removed. -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +For the best results, we recommend using the following values: -### -User -The User parameter specifies the user principal name (UPN), domain\\user, or alias of the user whose permissions are being removed. +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. ```yaml Type: PublicFolderUserIdParameter @@ -143,8 +137,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -179,16 +172,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -227,12 +217,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderDatabase.md b/exchange/exchange-ps/exchange/Remove-PublicFolderDatabase.md similarity index 84% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderDatabase.md rename to exchange/exchange-ps/exchange/Remove-PublicFolderDatabase.md index 4da529c79d..1da34f3a54 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-PublicFolderDatabase.md +++ b/exchange/exchange-ps/exchange/Remove-PublicFolderDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-publicfolderdatabase +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderdatabase applicable: Exchange Server 2010 title: Remove-PublicFolderDatabase schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-PublicFolderDatabase @@ -17,19 +16,23 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-PublicFolderDatabase cmdlet to delete public folder databases. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-PublicFolderDatabase [-Identity] [-Confirm] [-DomainController ] - [-RemoveLastAllowed] [-WhatIf] [] +Remove-PublicFolderDatabase [-Identity] + [-Confirm] + [-DomainController ] + [-RemoveLastAllowed] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). -Removing a public folder database can have a broad range of serious consequences. (This is particularly true when removing the last public folder database in the organization.) For more information, see [Remove Public Folder Databases](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/dd876883(v=exchg.141)). +Removing a public folder database can have a broad range of serious consequences. (This is particularly true when removing the last public folder database in the organization.) For more information, see [Remove Public Folder Databases](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd876883(v=exchg.141)). ## EXAMPLES @@ -46,9 +49,7 @@ This example removes the database Public Folder Database after all the prerequis 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -101,7 +101,7 @@ Accept wildcard characters: False ``` ### -RemoveLastAllowed -The RemoveLastAllowed parameter specifies whether to enable removal of the last public folder database in the organization. +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 @@ -137,12 +137,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/exchange/Remove-PublicFolderMailboxMigrationRequest.md similarity index 84% rename from exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMailboxMigrationRequest.md rename to exchange/exchange-ps/exchange/Remove-PublicFolderMailboxMigrationRequest.md index 16160321fe..647e00554d 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Remove-PublicFolderMailboxMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/remove-publicfoldermailboxmigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-PublicFolderMailboxMigrationRequest @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-PublicFolderMailboxMigrationRequest cmdlet to remove individual jobs from public folder migration batches that were created by using the New-MigrationBatch cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Remove-PublicFolderMailboxMigrationRequest [-Identity] ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MigrationRequestQueue @@ -35,11 +35,12 @@ Remove-PublicFolderMailboxMigrationRequest [-Identity] -RequestQueue [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -64,12 +65,10 @@ Get-PublicFolderMailboxMigrationRequest | group TargetMailbox | ?{$_.Count -gt 1 This example returns duplicate public folder migration requests (requests created for the same target mailbox). If the command returns no results, then there are no duplicate migration requests. -The sample script [Remove Duplicate public folder MRS Requests](https://gallery.technet.microsoft.com/scriptcenter/Remove-Duplicate-public-055f0e5e) detects duplicate or orphaned public folder mailbox migration requests and also removes them. - ## PARAMETERS ### -Identity -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). +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. @@ -87,6 +86,8 @@ Accept wildcard characters: False ``` ### -RequestGuid +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. If you use this parameter, you also need to use the RequestQueue parameter. You can't use either of these parameters with the Identity parameter. @@ -95,7 +96,7 @@ If you use this parameter, you also need to use the RequestQueue parameter. You Type: Guid Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -105,12 +106,12 @@ Accept wildcard characters: False ``` ### -RequestQueue +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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -119,7 +120,7 @@ You can't use this parameter with the Identity parameter. Type: DatabaseIdParameter Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -131,8 +132,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -149,7 +149,7 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. +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 +157,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -167,7 +167,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -203,12 +205,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/Remove-PublicFolderMigrationRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/exchange/Remove-PublicFolderMigrationRequest.md index 05b35507ba..c85f9d9a62 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Remove-PublicFolderMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/remove-publicfoldermigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-PublicFolderMigrationRequest @@ -19,7 +18,7 @@ Use the Remove-PublicFolderMigrationRequest cmdlet to cancel or complete serial **Note**: Support for serial migration of public folders ended in Exchange 2013 Cumulative Update 8 (CU8), and the cmdlets are no longer available in Exchange Online. Instead, use the corresponding **\*-MigrationBatch** and **\*-PublicFolderMailboxMigration\*** cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ Remove-PublicFolderMigrationRequest [-Identity] ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MigrationRequestQueue @@ -37,13 +37,14 @@ Remove-PublicFolderMigrationRequest [-Identity] -RequestQueue [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The RequestQueue and RequestGuid parameters are for debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,7 +70,6 @@ The RequestGuid and RequestQueue parameters are for debugging purposes only. The Identity parameter specifies the migration request that you want to remove. You can use the following values: - Name - - RequestGUID You can't use this parameter with the RequestGuid or RequestQueue parameters. @@ -109,9 +109,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You need to use this parameter with the RequestGuid parameter. @@ -134,8 +132,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -168,7 +165,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -204,12 +203,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/Remove-PublicFolderMoveRequest.md similarity index 84% rename from exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMoveRequest.md rename to exchange/exchange-ps/exchange/Remove-PublicFolderMoveRequest.md index 870eb4bf93..b32e757add 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/exchange/Remove-PublicFolderMoveRequest.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/remove-publicfoldermoverequest -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-PublicFolderMoveRequest ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Remove-PublicFolderMoveRequest cmdlet to cancel a mailbox move initiated using the New-MoveRequest cmdlet. After the move has been finalized, you can't undo the move request. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Remove-PublicFolderMoveRequest [-Identity] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### MigrationRequestQueue @@ -35,13 +35,14 @@ Remove-PublicFolderMoveRequest [-Identity] Remove-PublicFolderMoveRequest -RequestGuid -RequestQueue [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The RequestQueue and RequestGuid parameters are for debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,7 +73,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -90,7 +91,7 @@ You can't use this parameter with the Identity parameter. Type: Guid Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -103,9 +104,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity parameter. @@ -114,7 +113,7 @@ You can't use this parameter with the Identity parameter. Type: DatabaseIdParameter Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -126,15 +125,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -144,13 +142,15 @@ Accept wildcard characters: False ``` ### -DomainController +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. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -160,13 +160,15 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -182,7 +184,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -196,12 +198,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-QuarantinePolicy.md b/exchange/exchange-ps/exchange/Remove-QuarantinePolicy.md new file mode 100644 index 0000000000..6c828f12bb --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-QuarantinePolicy.md @@ -0,0 +1,90 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-QuarantinePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-QuarantinePolicy cmdlet to remove quarantine policies from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-QuarantinePolicy [-Identity] + [-DomainController ] + [] +``` + +## DESCRIPTION +You can't remove the built-in quarantine policies named AdminOnlyAccessPolicy or DefaultFullAccessPolicy. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-QuarantinePolicy -Identity "Contoso Engineering" +``` + +This example removes the quarantine policy named Contoso Engineering. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: QuarantineTagIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-ReceiveConnector.md b/exchange/exchange-ps/exchange/Remove-ReceiveConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Remove-ReceiveConnector.md rename to exchange/exchange-ps/exchange/Remove-ReceiveConnector.md index 33ba00624c..16d1194f04 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-ReceiveConnector.md +++ b/exchange/exchange-ps/exchange/Remove-ReceiveConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-receiveconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ReceiveConnector @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ReceiveConnector cmdlet to remove Receive connectors from Mailbox servers and Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ReceiveConnector [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-ReceiveConnector [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Removing a Receive connector from the server might affect mail flow throughout the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,12 +48,9 @@ This example removes the Receive connector named Contoso.com Receive Connector. 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 - - Distinguished name (DN) - - GUID - -- \\\\ +- ServerName\\Name ```yaml Type: ReceiveConnectorIdParameter @@ -69,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,12 +123,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-RecipientPermission.md b/exchange/exchange-ps/exchange/Remove-RecipientPermission.md new file mode 100644 index 0000000000..2b1a383994 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-RecipientPermission.md @@ -0,0 +1,263 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-RecipientPermission + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-RecipientPermission cmdlet to remove SendAs permission from users in a cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-RecipientPermission [-Identity] -AccessRights -Trustee + [-Confirm] + [-Deny] + [-MultiTrustees ] + [-SkipDomainValidationForMailContact] + [-SkipDomainValidationForMailUser] + [-SkipDomainValidationForSharedMailbox] + [-WhatIf] + [] +``` + +## DESCRIPTION +When a user is given SendAs permission to another user or group, the user can send messages that appear to come from the other user or group. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-RecipientPermission "Help Desk" -AccessRights SendAs -Trustee "Ayla Kol" +``` + +This example removes the SendAs permission from the user Ayla Kol for the mailbox Help Desk. Ayla can't send messages that appear to come directly from the Help Desk mailbox. + +## PARAMETERS + +### -Identity +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: + +- Mailboxes +- Mail users +- External contacts +- Distribution groups +- Dynamic distribution groups + +You can use any value that uniquely identifies the recipient. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccessRights +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Trustee +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 +- Mail users with a Microsoft account +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Deny +{{ Fill Deny Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -MultiTrustees +{{ Fill MultiTrustees Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipDomainValidationForMailContact +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -SkipDomainValidationForMailUser +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -SkipDomainValidationForSharedMailbox +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mail-flow/Remove-RemoteDomain.md b/exchange/exchange-ps/exchange/Remove-RemoteDomain.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Remove-RemoteDomain.md rename to exchange/exchange-ps/exchange/Remove-RemoteDomain.md index cb76ed7960..bc7601b802 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-RemoteDomain.md +++ b/exchange/exchange-ps/exchange/Remove-RemoteDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-remotedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-RemoteDomain @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-RemoteDomain cmdlet to remove a remote domain. When you remove a remote domain, the remote domain object is deleted. Removing a remote domain doesn't disable mail flow to that domain. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-RemoteDomain [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-RemoteDomain [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,9 +46,7 @@ This example removes the remote domain object named Contoso. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -65,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-RemoteMailbox.md b/exchange/exchange-ps/exchange/Remove-RemoteMailbox.md similarity index 81% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Remove-RemoteMailbox.md rename to exchange/exchange-ps/exchange/Remove-RemoteMailbox.md index 4376366eb2..1795e792f9 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Remove-RemoteMailbox.md +++ b/exchange/exchange-ps/exchange/Remove-RemoteMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/remove-remotemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-RemoteMailbox @@ -17,13 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-RemoteMailbox cmdlet to remove a mail-enabled user in the on-premises Active Directory and the associated mailbox in the cloud-based service. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-RemoteMailbox [-Identity] [-Confirm] [-DomainController ] - [-IgnoreDefaultScope] [-IgnoreLegalHold] [-WhatIf] [] +Remove-RemoteMailbox [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-IgnoreLegalHold] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +35,7 @@ With the Remove-RemoteMailbox cmdlet, you can remove an on-premises mail-enabled Directory synchronization must be configured correctly for a mailbox to be removed from the service. Removal of the mailbox from the service isn't immediate and depends on the directory synchronization schedule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,19 +52,12 @@ This example removes the on-premises mail-enabled user Kim Akers and the associa 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 - - Distinguished name (DN) - - Legacy DN - - GUID - - Domain\\Account name - - User principal name (UPN) - - Email address - - Alias ```yaml @@ -79,8 +76,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -113,12 +109,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -135,9 +130,9 @@ Accept wildcard characters: False ``` ### -IgnoreLegalHold -The IgnoreLegalHold switch ignores the legal hold status of the mailbox user and allows you to remove the cloud-based mailbox on legal hold. +The IgnoreLegalHold switch ignores the legal hold status of the remote user. You don't need to specify a value with this switch. -After you remove a mailbox, you can't include it in a discovery search. Depending on the command parameters you use, removed mailboxes are either purged immediately or when the deleted mailbox retention period expires. Check with your organization's legal or Human Resources department before disabling a mailbox that's on legal hold. +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. ```yaml Type: SwitchParameter @@ -173,12 +168,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-ReportSubmissionPolicy.md b/exchange/exchange-ps/exchange/Remove-ReportSubmissionPolicy.md new file mode 100644 index 0000000000..bdcd81de21 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ReportSubmissionPolicy.md @@ -0,0 +1,68 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ReportSubmissionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-ReportSubmissionPolicy cmdlet to remove the report submission policy from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ReportSubmissionPolicy [-Identity] [] +``` + +## DESCRIPTION +There's only one report submission policy in an organization, and it's named DefaultReportSubmissionPolicy. You can remove the policy and then use the New-ReportSubmissionPolicy cmdlet to recreate it with the default settings. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy +``` + +This example removes the report submission policy from your organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Remove-ReportSubmissionRule.md new file mode 100644 index 0000000000..7c7b4a7d97 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ReportSubmissionRule.md @@ -0,0 +1,106 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ReportSubmissionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-ReportSubmissionRule cmdlet to remove the report submission rule from your cloud-based organization. The report submission rule identifies the reporting mailbox where user reported messages are delivered. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ReportSubmissionRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To disable the report submission rule without deleting it, use the Disable-ReportSubmissionRule cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ReportSubmissionRule -Identity DefaultReportSubmissionRule +``` + +This example removes the report submission rule from your organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-ResubmitRequest.md b/exchange/exchange-ps/exchange/Remove-ResubmitRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Remove-ResubmitRequest.md rename to exchange/exchange-ps/exchange/Remove-ResubmitRequest.md index 6548c0637b..6b01e58449 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-ResubmitRequest.md +++ b/exchange/exchange-ps/exchange/Remove-ResubmitRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-resubmitrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ResubmitRequest @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ResubmitRequest cmdlet to remove requests to replay redundant copies of messages from Safety Net after a mailbox database recovery. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ResubmitRequest [-Identity] [-Confirm] [-Server ] - [-WhatIf] [] +Remove-ResubmitRequest [-Identity] + [-Confirm] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -66,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -87,11 +88,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -130,12 +128,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md new file mode 100644 index 0000000000..586520eb81 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md @@ -0,0 +1,142 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-RetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-RetentionCompliancePolicy cmdlet to remove retention policies from the Microsoft Purview compliance portal. This cmdlet also removes the corresponding retention rule. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-RetentionCompliancePolicy [-Identity] + [-Confirm] + [-ForceDeletion] + [-PriorityCleanup] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-RetentionCompliancePolicy -Identity "Regulation 123 Compliance" +``` + +This example removes the retention policy named "Regulation 123 Compliance". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md new file mode 100644 index 0000000000..fd33677240 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md @@ -0,0 +1,144 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-RetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-RetentionComplianceRule cmdlet to remove retention rules from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-RetentionComplianceRule [-Identity] + [-Confirm] + [-ForceDeletion] + [-PriorityCleanup] + [-WhatIf] + [] +``` + +## DESCRIPTION +Removing a retention rule causes the release of all Exchange mailbox and SharePoint site retentions that are associated with the rule. Removing a retention rule also causes the corresponding retention policy to become invalid, so you should remove it by using the Remove-RetentionCompliancePolicy cmdlet. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-RetentionComplianceRule -Identity "One Year Standard" +``` + +This example removes the retention rule named "One Year Standard". + +## PARAMETERS + +### -Identity +The Identity parameter specifies the retention rule to remove. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionPolicy.md b/exchange/exchange-ps/exchange/Remove-RetentionPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionPolicy.md rename to exchange/exchange-ps/exchange/Remove-RetentionPolicy.md index 9e87551d45..3606e9995c 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-RetentionPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-retentionpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-RetentionPolicy @@ -17,13 +16,17 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-RetentionPolicy cmdlet to remove a retention policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-RetentionPolicy [-Identity] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] +Remove-RetentionPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +34,7 @@ Retention policies are used to apply message retention settings to folders and i If you remove a retention policy that's assigned to users and they don't have another retention policy assigned, messages in those mailboxes may never expire. This may be a violation of the organization's messaging retention policies. When you attempt to remove a policy that's assigned to users, Microsoft Exchange displays a confirmation message indicating that the policy is assigned to users. Note that this message is in addition to the confirmation prompt displayed when removing a retention policy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,8 +80,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -113,7 +115,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch specifies whether to override the confirmation prompt that appears when removing 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. You don't have to specify a value with the Force switch. +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. ```yaml Type: SwitchParameter @@ -149,12 +153,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionPolicyTag.md b/exchange/exchange-ps/exchange/Remove-RetentionPolicyTag.md similarity index 87% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionPolicyTag.md rename to exchange/exchange-ps/exchange/Remove-RetentionPolicyTag.md index 359b18283e..03f3e9a59f 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionPolicyTag.md +++ b/exchange/exchange-ps/exchange/Remove-RetentionPolicyTag.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-retentionpolicytag +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-RetentionPolicyTag @@ -17,13 +16,16 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-RetentionPolicyTag cmdlet to remove a retention tag. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-RetentionPolicyTag [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-RetentionPolicyTag [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,9 +33,9 @@ Retention tags are added to a retention policy, which is applied to a mailbox. When you use the Remove-RetentionPolicyTag cmdlet to remove a retention tag, it removes the tag definition stored in Active Directory. The next time the Managed Folder Assistant runs, it processes all items that have the removed tag applied and restamps them. Depending on the number of mailboxes and messages, this process may result in significant resource consumption on all Mailbox servers that contain mailboxes with a retention policy that includes the removed tag. -For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). +For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Remove-RoleAssignmentPolicy.md b/exchange/exchange-ps/exchange/Remove-RoleAssignmentPolicy.md similarity index 82% rename from exchange/exchange-ps/exchange/role-based-access-control/Remove-RoleAssignmentPolicy.md rename to exchange/exchange-ps/exchange/Remove-RoleAssignmentPolicy.md index 5e4ab6ca84..30fc9c2297 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Remove-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-RoleAssignmentPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/remove-roleassignmentpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-RoleAssignmentPolicy @@ -17,33 +16,40 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-RoleAssignmentPolicy cmdlet to remove existing management role assignment policies from your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-RoleAssignmentPolicy [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-RoleAssignmentPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The assignment policy you want to remove can't be assigned to any mailboxes or management roles. Also, if you want to remove the default assignment policy, it must be the last assignment policy. Do the following before you attempt to remove an assignment policy: - Use the Set-Mailbox cmdlet to change the assignment policy for any mailbox assigned the assignment policy you want to remove. - - If the assignment policy is the default assignment policy, use the Set-RoleAssignmentPolicy cmdlet to select a new default assignment policy. You don't need to do this if you're removing the last assignment policy. - - Use the Remove-ManagementRoleAssignment cmdlet to remove any management role assignments assigned to the policy. -For more information about assignment policies, see [Understanding management role assignment policies](https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). +For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Get-Mailbox | Where {$_.RoleAssignmentPolicy -Eq "End User"}; Get-Mailbox | Where {$_.RoleAssignmentPolicy -Eq "End User"} | Set-Mailbox -RoleAssignmentPolicy "Seattle End User"; Get-ManagementRoleAssignment -RoleAssignee "End User" | Remove-ManagementRoleAssignment; Remove-RoleAssignmentPolicy "End User" +Get-Mailbox | Where {$_.RoleAssignmentPolicy -Eq "End User"} + +Get-Mailbox | Where {$_.RoleAssignmentPolicy -Eq "End User"} | Set-Mailbox -RoleAssignmentPolicy "Seattle End User" + +Get-ManagementRoleAssignment -RoleAssignee "End User" | Remove-ManagementRoleAssignment + +Remove-RoleAssignmentPolicy "End User" ``` This example removes the role assignment policy named End User. @@ -56,7 +62,7 @@ Remove all management role assignments that are assigned to the End User policy. Remove the End User role assignment policy. -For more information about the Where cmdlet and pipelining, see [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help) and [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). +For more information about the Where cmdlet and pipelining, see [Working with command output](https://learn.microsoft.com/exchange/working-with-command-output-exchange-2013-help) and [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). ## PARAMETERS @@ -79,8 +85,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -137,12 +142,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-RoleGroup.md b/exchange/exchange-ps/exchange/Remove-RoleGroup.md new file mode 100644 index 0000000000..ed3cddf995 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-RoleGroup.md @@ -0,0 +1,189 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-RoleGroup + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-RoleGroup cmdlet to remove a management role group. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-RoleGroup [-Identity] + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +When you remove a role group, all the management role assignments assigned management roles to the role group are also removed. The management roles aren't removed. Members of a removed role group can no longer manage a feature if the role group was the only means by which they were granted access to the feature. + +You can't remove built-in role groups. + +If the ManagedBy property has been populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. + +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-RoleGroup "Training Administrators" +``` + +This example removes the Training Administrators role group. + +### Example 2 +```powershell +Remove-RoleGroup "Vancouver Recipient Administrators" -BypassSecurityGroupManagerCheck +``` + +This example removes the Vancouver Recipient Administrators role group. Because the user running the command wasn't added to the ManagedBy property of the role group, the BypassSecurityGroupManagerCheck switch must be used. The user is assigned the Role Management role, which enables the user to bypass the security group manager check. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BypassSecurityGroupManagerCheck +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: + +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +- Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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-RoleGroupMember.md b/exchange/exchange-ps/exchange/Remove-RoleGroupMember.md new file mode 100644 index 0000000000..34807f1679 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-RoleGroupMember.md @@ -0,0 +1,216 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-RoleGroupMember + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Remove-RoleGroupMember cmdlet to remove a member of a management role group. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-RoleGroupMember [-Identity] -Member + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +When you remove a member from a role group, that member can no longer manage the features made available by the role group if the role group is the only means by which the member is granted access to the feature. + +If the ManagedBy property has been populated with role group managers, the user removing a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. + +If the role group is a linked role group, you can't use the Remove-RoleGroupMember cmdlet to remove members from the role group. Instead, you need to remove members from the foreign universal security group (USG) linked to the linked role group. To find the foreign USG linked to a role group, use the Get-RoleGroup cmdlet. + +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-RoleGroupMember "Recipient Management" -Member David +``` + +This example removes the user David from the role group Recipient Management. + +### Example 2 +```powershell +Get-User -Filter "Department -eq 'Sales' -and -RecipientType -eq 'UserMailbox'" | Get-Mailbox | Remove-RoleGroupMember "Sales and Marketing Group" -WhatIf +``` + +This example finds all the mailboxes that are part of the Sales department and removes them from the Sales and Marketing Group role group. Because we're using the WhatIf switch, the changes aren't written to the role group, so you can verify that the correct members will be removed. + +After you've verified that the correct members will be removed the role group, remove the WhatIf switch and run the command again. + +For more information about pipelining, and the WhatIf parameter, see the following topics: + +- [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) +- [WhatIf, Confirm and ValidateOnly switches](https://learn.microsoft.com/exchange/whatif-confirm-and-validateonly-switches-exchange-2013-help) + +### Example 3 +```powershell +Remove-RoleGroupMember "Training Administrators" -Member "Training Assistants" -BypassSecurityGroupManagerCheck +``` + +This example removes the Training Assistants USG from the Training Administrators role group. Because the user running the command wasn't added to the ManagedBy property of the role group, the BypassSecurityGroupManagerCheck switch must be used. The user is assigned the Role Management role, which enables the user to bypass the security group manager check. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Member +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 +- Mail users +- Mail-enabled security groups +- Security groups (on-premises Exchange only) + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BypassSecurityGroupManagerCheck +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: + +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +- Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mail-flow/Remove-RoutingGroupConnector.md b/exchange/exchange-ps/exchange/Remove-RoutingGroupConnector.md similarity index 90% rename from exchange/exchange-ps/exchange/mail-flow/Remove-RoutingGroupConnector.md rename to exchange/exchange-ps/exchange/Remove-RoutingGroupConnector.md index 515425f35c..e34b39e341 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-RoutingGroupConnector.md +++ b/exchange/exchange-ps/exchange/Remove-RoutingGroupConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-routinggroupconnector +online version: https://learn.microsoft.com/powershell/module/exchange/remove-routinggroupconnector applicable: Exchange Server 2010 title: Remove-RoutingGroupConnector schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-RoutingGroupConnector @@ -17,13 +16,16 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-RoutingGroupConnector cmdlet to remove a routing group connector between a Microsoft Exchange Server 2010 routing group and an Exchange Server 2003 routing group. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-RoutingGroupConnector [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-RoutingGroupConnector [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ A routing group connector is used to send and receive messages between computers The Exchange 2003 servers used as source servers for the specified routing group connector are automatically removed from the ExchangeLegacyInterop universal security group. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-RpcClientAccess.md b/exchange/exchange-ps/exchange/Remove-RpcClientAccess.md similarity index 91% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-RpcClientAccess.md rename to exchange/exchange-ps/exchange/Remove-RpcClientAccess.md index 7cedb8a643..869e6560c5 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-RpcClientAccess.md +++ b/exchange/exchange-ps/exchange/Remove-RpcClientAccess.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-rpcclientaccess +online version: https://learn.microsoft.com/powershell/module/exchange/remove-rpcclientaccess applicable: Exchange Server 2010 title: Remove-RpcClientAccess schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Remove-RPCClientAccess @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Remove-RpcClientAccess cmdlet to remove the configuration information that allows RPC access through the Client Access server role on Microsoft Exchange Server 2010. After you remove the configuration information, the Exchange RPC Client Access service stops and no longer starts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,13 +24,14 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-RPCClientAccess -Server [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Disabling RPC client access on a server blocks all RPC access through the specified Client Access server. Therefore, RPC clients (for example, clients running Microsoft Office Outlook 2007) with mailboxes on any mailbox databases configured to use the specified Client Access server won't be able to connect. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,11 +48,8 @@ This example removes the configuration information for the Exchange RPC Client A 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -71,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,12 +121,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Remove-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/Remove-SafeAttachmentPolicy.md new file mode 100644 index 0000000000..857607a82b --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-SafeAttachmentPolicy.md @@ -0,0 +1,131 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-SafeAttachmentPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-SafeAttachmentPolicy cmdlet to remove safe attachment policies from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-SafeAttachmentPolicy [-Identity] + [-Confirm] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-SafeAttachmentPolicy -Identity "Block Attachments Policy" +``` + +This example removes the safe attachment policy named Block Attachments Policy. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: SafeAttachmentPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Remove-SafeAttachmentRule.md new file mode 100644 index 0000000000..e442e79efb --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-SafeAttachmentRule.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-SafeAttachmentRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-SafeAttachmentRule cmdlet to remove safe attachment rules from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-SafeAttachmentRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-SafeAttachmentRule -Identity "Research Department Attachment Rule" +``` + +This examples removes the safe attachment rule named Research Department Attachment Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/Remove-SafeLinksPolicy.md new file mode 100644 index 0000000000..287856fcc5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-SafeLinksPolicy.md @@ -0,0 +1,133 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-SafeLinksPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-SafeLinksPolicy cmdlet to remove Safe Links policies from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-SafeLinksPolicy [-Identity] + [-Confirm] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can't remove the default Safe Links policy (the policy where the IsDefault property is True). + +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-SafeLinksPolicy -Identity "Engineering Department URL Policy" +``` + +This example remove the Safe Links policy named Engineering Department URL Policy. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: SafeLinksPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-SafeLinksRule.md b/exchange/exchange-ps/exchange/Remove-SafeLinksRule.md new file mode 100644 index 0000000000..472e9e9324 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-SafeLinksRule.md @@ -0,0 +1,112 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-SafeLinksRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-SafeLinksRule cmdlet to remove Safe Links rules from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-SafeLinksRule [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-SafeLinksRule -Identity "Research Department URL Rule" +``` + +This examples removes the Safe Links rule named Research Department URL Rule. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-SearchDocumentFormat.md b/exchange/exchange-ps/exchange/Remove-SearchDocumentFormat.md similarity index 89% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-SearchDocumentFormat.md rename to exchange/exchange-ps/exchange/Remove-SearchDocumentFormat.md index 7b85cc3384..b15bec5d2b 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-SearchDocumentFormat.md +++ b/exchange/exchange-ps/exchange/Remove-SearchDocumentFormat.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/remove-searchdocumentformat +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-SearchDocumentFormat @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-SearchDocumentFormat cmdlet to remove a format-specific filter from those used by Exchange search. Only filters added with New-SearchDocumentFormat can be removed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-SearchDocumentFormat [-Identity] [-Confirm] [-Server ] - [-WhatIf] [] +Remove-SearchDocumentFormat [-Identity] + [-Confirm] + [-Server ] + [-WhatIf] + [] ``` ## DESCRIPTION After running the Remove-SearchDocumentFormat cmdlet, your must run the following cmdlet to restart the search service. There will be a brief search outage. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -82,11 +83,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -125,12 +123,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-SecOpsOverridePolicy.md b/exchange/exchange-ps/exchange/Remove-SecOpsOverridePolicy.md new file mode 100644 index 0000000000..116c6c915a --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-SecOpsOverridePolicy.md @@ -0,0 +1,143 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-SecOpsOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-SecOpsOverridePolicy cmdlet to remove SecOps mailbox override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-SecOpsOverridePolicy [-Identity] + [-Confirm] + [-DomainController ] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-SecOpsOverridePolicy -Identity SecOpsOverridePolicy +``` + +This example removes the SecOps mailbox override policy. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-SendConnector.md b/exchange/exchange-ps/exchange/Remove-SendConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Remove-SendConnector.md rename to exchange/exchange-ps/exchange/Remove-SendConnector.md index d97d0c1a55..e1ce45ac63 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-SendConnector.md +++ b/exchange/exchange-ps/exchange/Remove-SendConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-sendconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-SendConnector @@ -17,12 +16,15 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-SendConnector cmdlet to delete a Send connector. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-SendConnector [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-SendConnector [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ The Remove-SendConnector cmdlet deletes the object and the configuration setting Although a Send connector is configured locally in the Transport service on a Mailbox server or on an Edge server, deleting a Send connector may affect mail flow throughout the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -119,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-ServerMonitoringOverride.md b/exchange/exchange-ps/exchange/Remove-ServerMonitoringOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/server-health-and-performance/Remove-ServerMonitoringOverride.md rename to exchange/exchange-ps/exchange/Remove-ServerMonitoringOverride.md index 4b94a72949..dff6213508 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/exchange/Remove-ServerMonitoringOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/remove-servermonitoringoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ServerMonitoringOverride @@ -17,19 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ServerMonitoringOverride cmdlet to remove a managed availability local server override that has been configured for a probe, monitor or responder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ServerMonitoringOverride [-Identity] -ItemType - -PropertyName -Server +Remove-ServerMonitoringOverride [-Identity] -ItemType -PropertyName -Server [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,9 +68,7 @@ Accept wildcard characters: False The ItemType parameter specifies the item type of the override that you want to remove. It can be any of the following values: - Probe - - Monitor - - Responder ```yaml @@ -107,11 +104,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -130,8 +124,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -168,12 +161,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-ServicePrincipal.md b/exchange/exchange-ps/exchange/Remove-ServicePrincipal.md new file mode 100644 index 0000000000..855f9df7b6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-ServicePrincipal.md @@ -0,0 +1,110 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-ServicePrincipal + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-ServicePrincipal cmdlet to remove service principals from your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-ServicePrincipal [-Identity] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-ServicePrincipal -Identity 7c7599b2-23af-45e3-99ff-0025d148e929 +``` + +This example removes the specified service principal. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- AppId +- ObjectId + +```yaml +Type: ServicePrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Remove-SettingOverride.md b/exchange/exchange-ps/exchange/Remove-SettingOverride.md similarity index 88% rename from exchange/exchange-ps/exchange/organization/Remove-SettingOverride.md rename to exchange/exchange-ps/exchange/Remove-SettingOverride.md index 048e4ce48a..c3488fbb4e 100644 --- a/exchange/exchange-ps/exchange/organization/Remove-SettingOverride.md +++ b/exchange/exchange-ps/exchange/Remove-SettingOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/remove-settingoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-SettingOverride @@ -19,19 +18,22 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-SettingOverride cmdlet to remove setting overrides from Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-SettingOverride [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-SettingOverride [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and they're lost when you install the next Exchange CU. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,9 +50,7 @@ This example removes the setting override named IM Server Integration. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -69,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,12 +122,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SharingPolicy.md b/exchange/exchange-ps/exchange/Remove-SharingPolicy.md similarity index 88% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SharingPolicy.md rename to exchange/exchange-ps/exchange/Remove-SharingPolicy.md index f77cd2d225..ac9dbb8159 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SharingPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-SharingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-sharingpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-SharingPolicy @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-SharingPolicy cmdlet to remove a sharing policy. Before you can remove a sharing policy, you must ensure that no mailbox users are provisioned to use that policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-SharingPolicy [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-SharingPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,11 +53,8 @@ This example removes the sharing policy Contoso and suppresses the confirmation The Identity parameter specifies the identity of the sharing policy that you want to remove. You can use one of the following values: - ADObjectID - - Distinguished name (DN) - - Legacy DN - - GUID ```yaml @@ -74,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,12 +128,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/exchange/Remove-SiteMailboxProvisioningPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/exchange/Remove-SiteMailboxProvisioningPolicy.md index f3895ced14..3b226be32b 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-SiteMailboxProvisioningPolicy.md @@ -1,35 +1,39 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-sitemailboxprovisioningpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-SiteMailboxProvisioningPolicy ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Remove-SiteMailboxProvisioningPolicy cmdlet to remove site mailbox provisioning policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-SiteMailboxProvisioningPolicy [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-SiteMailboxProvisioningPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION You can't delete the default site mailbox provisioning policy. You need to create a new default policy by using the New-SiteMailboxProvisioningPolicy cmdlet or designate an existing policy as the default policy by using the Set-SiteMailboxProvisioningPolicy cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,9 +50,7 @@ This example deletes the site mailbox policy named Default that was created when 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 - - Distinguished name (DN) - - GUID ```yaml @@ -67,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-StoreMailbox.md b/exchange/exchange-ps/exchange/Remove-StoreMailbox.md similarity index 93% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-StoreMailbox.md rename to exchange/exchange-ps/exchange/Remove-StoreMailbox.md index c902613c36..4faccccab2 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-StoreMailbox.md +++ b/exchange/exchange-ps/exchange/Remove-StoreMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/remove-storemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-StoreMailbox @@ -17,14 +16,15 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-StoreMailbox cmdlet to purge the mailbox and all of its message content from the mailbox database. This results in permanent data loss for the mailbox being purged. You can only run this cmdlet against disconnected or soft-deleted mailboxes. Running this command against an active mailbox fails, and you receive an error. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Remove-StoreMailbox -Database -Identity -MailboxState [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -36,7 +36,7 @@ A mailbox is marked as Disabled immediately after the Disable-Mailbox or Remove- To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database using the property DisconnectReason with a value of Disabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,9 +67,7 @@ This example permanently purges all soft-deleted mailboxes from mailbox database 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 - - Distinguished name (DN) - - GUID ```yaml @@ -107,7 +105,6 @@ Accept wildcard characters: False The MailboxState parameter specifies the mailbox state on the source mailbox database. This parameter accepts the following values: - Disabled - - SoftDeleted ```yaml @@ -126,8 +123,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -164,12 +160,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/Remove-SupervisoryReviewPolicyV2.md new file mode 100644 index 0000000000..1bbb2eaf31 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-SupervisoryReviewPolicyV2.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-SupervisoryReviewPolicyV2 + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-SupervisoryReviewPolicyV2 cmdlet to remove supervisory review policies from the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-SupervisoryReviewPolicyV2 [-Identity] + [-Confirm] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-SupervisoryReviewPolicyV2 -Identity "EU Brokers Policy" +``` + +This example removes the supervisory review policy named EU Brokers Policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Remove-SweepRule.md b/exchange/exchange-ps/exchange/Remove-SweepRule.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Remove-SweepRule.md rename to exchange/exchange-ps/exchange/Remove-SweepRule.md index d0f6a1c260..5a20fe05fc 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-SweepRule.md +++ b/exchange/exchange-ps/exchange/Remove-SweepRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-sweeprule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-SweepRule @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-SweepRule cmdlet to remove Sweep rules from mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-SweepRule [-Identity] [-Confirm] [-DomainController ] - [-Mailbox ] [-WhatIf] [] +Remove-SweepRule [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,10 +54,8 @@ This example removes all Sweep rules in the specified mailbox. 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==). - -- Exchange Online: \\\\ (for example, rzaher\\x2hlsdpGmUifjFgxxGIOJw==. - -- On-premises Exchange: \\\\ (for example, contoso.com/Users/Rick Zaher\\x2hlsdpGmUifjFgxxGIOJw==. +- Exchange Online: `MailboxAlias\RuleID` (for example, `rzaher\2hlsdpGmUifjFgxxGIOJw==`). +- On-premises Exchange: `MailboxCanonicalName\RuleID` (for example, `contoso.com/Users/Rick Zaher\x2hlsdpGmUifjFgxxGIOJw==`). ```yaml Type: SweepRuleIdParameter @@ -72,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -111,23 +111,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -164,12 +155,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SyncMailPublicFolder.md b/exchange/exchange-ps/exchange/Remove-SyncMailPublicFolder.md similarity index 76% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SyncMailPublicFolder.md rename to exchange/exchange-ps/exchange/Remove-SyncMailPublicFolder.md index 7c6f5d9ff1..b48470c51b 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Remove-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/exchange/Remove-SyncMailPublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/remove-syncmailpublicfolder -applicable: Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-SyncMailPublicFolder @@ -15,21 +14,24 @@ monikerRange: "exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -The Remove-SyncMailPublicFolder cmdlet is used by the Sync-MailPublicFolders.ps1 script to remove mail-enabled public folder recipient objects from Exchange Online in Office 365 (the script synchronizes mail-enabled public folder objects from the source on-premises Exchange organization to Office 365). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. +The Remove-SyncMailPublicFolder cmdlet is used by the Sync-MailPublicFolders.ps1 script to remove mail-enabled public folder recipient objects from Exchange Online (the script synchronizes mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-SyncMailPublicFolder [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Remove-SyncMailPublicFolder [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION This cmdlet is only used by the Sync-MailPublicFolders.ps1 script. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,21 +45,18 @@ This cmdlet is only used by the Sync-MailPublicFolders.ps1 script. Don't run thi ## PARAMETERS ### -Identity -The Identity parameter specifies the mail-enabled public folder object that you want to remove from Exchange Online in Office 365. For example: +The Identity parameter specifies the mail-enabled public folder object that you want to remove from Exchange Online. For example: - Name - - Distinguished name (DN) - - GUID - -- Path: (\\\\\\ +- Path (`\\`) ```yaml Type: MailPublicFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -69,15 +68,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -111,7 +109,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -125,12 +123,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-SystemMessage.md b/exchange/exchange-ps/exchange/Remove-SystemMessage.md new file mode 100644 index 0000000000..c61753f2b5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-SystemMessage.md @@ -0,0 +1,187 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-SystemMessage + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Remove-SystemMessage cmdlet to remove custom system messages. System messages are delivery status notifications (also known as DSNs, non-delivery reports, NDRs or bounce messages) and quota messages. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-SystemMessage [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You can't remove a default system message that's included with Exchange. When you remove a custom system message, the message text reverts to the text in the corresponding system message (if any) that's included with Exchange. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-SystemMessage En\Internal\5.7.9 +``` + +This example removes the specified custom NDR (combination of language, audience, and enhanced status code values). + +### Example 2 +```powershell +Remove-SystemMessage En\WarningMailbox +``` + +This example removes the specified custom quota message (combination of language and quota values). + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +The identity value of a system message uses one of these formats: + +- System messages for enhanced status codes: `Language\\DSNCode`. For example, `En\Internal\5.1.2` or `Ja\External\5.1.2`. +- System messages for quotas: `Language\QuotaMessageType`. For example, `En\ProhibitSendReceiveMailbox`. + +\: 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). + +\: Valid values are 4.x.y or 5.x.y where x and y are one to three digit numbers. To see the enhanced system codes that are currently used by custom system messages, run the command `Get-SystemMessage`. To generate a list of default enhanced status codes that are used by Exchange, run this command: `Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language,Text | ConvertTo-Html | Set-Content -Path "C:\My Documents\Default DSNs.html"`. + +\: Valid value are: + +Mailbox size quotas: + +- ProhibitSendReceiveMailbox: A mailbox exceeds its ProhibitSendReceiveQuota limit. +- ProhibitSendMailbox: A mailbox exceeds its ProhibitSendQuota limit. +- WarningMailbox: A mailbox exceeds its IssueWarningQuota limit when it has a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. +- WarningMailboxUnlimitedSize: A mailbox exceeds its IssueWarningQuota limit when it doesn't have a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. + +Public folder size quotas: + +- ProhibitPostPublicFolder: A public folder exceeds its ProhibitPostQuota limit. +- WarningPublicFolder: A public folder exceeds its IssueWarningQuota limit when it has a ProhibitPostQuota limit configured. +- WarningPublicFolderUnlimitedSize: A public folder exceeds its IssueWarningQuota limit when it doesn't have a ProhibitPostQuota limit configured. + +Maximum number of messages in a mailbox folder: + +- ProhibitReceiveMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountReceiveQuota limit. +- WarningMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it has a MailboxMessagesPerFolderCountReceiveQuota limit configured. +- WarningMailboxMessagesPerFolderUnlimitedCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it doesn't have a MailboxMessagesPerFolderCountReceiveQuota limit configured. + +Maximum number of subfolders in a mailbox folder: + +- ProhibitReceiveFolderHierarchyChildrenCountCount: A mailbox exceeds its FolderHierarchyChildrenCountReceiveQuota limit. +- WarningFolderHierarchyChildrenCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it has a FolderHierarchyChildrenCountReceiveQuota limit configured. +- WarningFolderHierarchyChildrenUnlimitedCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it doesn't have a FolderHierarchyChildrenCountReceiveQuota limit configured. +- ProhibitReceiveFoldersCount: A mailbox exceeds its FoldersCountReceiveQuota limit. +- WarningFoldersCount: A mailbox exceeds its FoldersCountWarningQuota limit when it has a FoldersCountReceiveQuota limit configured. +- WarningFoldersCountUnlimited A mailbox exceeds its FoldersCountWarningQuota limit when it doesn't have a FoldersCountReceiveQuota limit configured. + +Maximum number of levels (depth) in a mailbox folder: + +- ProhibitReceiveFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit. +- WarningFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it has a FolderHierarchyDepthReceiveQuota limit configured. +- WarningFolderHierarchyDepthUnlimited: : A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it doesn't have a FolderHierarchyDepthReceiveQuota limit configured. + +```yaml +Type: SystemMessageIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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-TenantAllowBlockListItems.md b/exchange/exchange-ps/exchange/Remove-TenantAllowBlockListItems.md new file mode 100644 index 0000000000..131df513a6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-TenantAllowBlockListItems.md @@ -0,0 +1,174 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-TenantAllowBlockListItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-TenantAllowBlockListItems cmdlet to remove entries from the Tenant Allow/Block List in the Microsoft Defender portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Entries +``` +Remove-TenantAllowBlockListItems -Entries -ListType + [-ListSubType ] + [-OutputJson] + [] +``` + +### Ids +``` +Remove-TenantAllowBlockListItems -Ids -ListType + [-ListSubType ] + [-OutputJson] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-TenantAllowBlockListItems -ListType Url -Ids "RgAAAAAI8gSyI_NmQqzeh-HXJBywBwCqfQNJY8hBTbdlKFkv6BcUAAAl_QCZAACqfQNJY8hBTbdlKFkv6BcUAAAl_oSPAAAA0l" +``` + +This example removes the specified URL entry from the Tenant Allow/Block List. + +### Example 2 +```powershell +Remove-TenantAllowBlockListItems -ListType Url -ListSubType AdvancedDelivery -Entries *.fabrikam.com +``` + +This example removes the URL allow entry for the specified third-party phishing simulation URL. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +## PARAMETERS + +### -Entries +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. +- Sender domains and email addresses: The exact domain or email address value. +- Url: The exact URL value. +- IP: IPv6 addresses only. Single IPv6 addresses in colon-hexadecimal or zero-compression format or CIDR IPv6 ranges from 1 to 128. + +This value is shown in the Value property of the entry in the output of the Get-TenantAllowBlockListItems cmdlet. + +You can't mix value types (sender, URL, file, or IP address) or allow and block actions in the same command. + +You can't use this parameter with the Ids parameter. + +```yaml +Type: String[] +Parameter Sets: Entries +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Ids +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`. + +You can't use this parameter with the Entries parameter. + +```yaml +Type: String[] +Parameter Sets: Ids +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ListType +The ListType parameter specifies the type of entry that you want to remove. Valid values are: + +- FileHash +- Sender +- Url +- IP + +```yaml +Type: ListType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ListSubType +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. +- Tenant: This is the default value. + +```yaml +Type: ListSubType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutputJson +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md new file mode 100644 index 0000000000..dffc5da8d0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md @@ -0,0 +1,122 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-TenantAllowBlockListSpoofItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-TenantAllowBlockListSpoofItems cmdlet to remove spoofed sender entries from the Tenant Allow/Block List. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-TenantAllowBlockListSpoofItems [-Identity] -Ids + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +This cmdlet removes spoof pairs (the combination of the spoofed user and the sending infrastructure) from the Tenant Allow/Block List. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-TenantAllowBlockListSpoofItems -Identity domain.com\Default -Ids 375e76f1-eefb-1626-c8bc-5efefd057488,f8cb0908-8533-1156-ce7b-9aebd685b0eb +``` + +This example removes the specified spoofed sender. You get the Ids parameter value from the Identity property in the output of Get-TenantAllowBlockListSpoofItems command. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Ids +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-ThrottlingPolicy.md b/exchange/exchange-ps/exchange/Remove-ThrottlingPolicy.md similarity index 80% rename from exchange/exchange-ps/exchange/server-health-and-performance/Remove-ThrottlingPolicy.md rename to exchange/exchange-ps/exchange/Remove-ThrottlingPolicy.md index 820e32f3e6..98949a3787 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Remove-ThrottlingPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-ThrottlingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/remove-throttlingpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-ThrottlingPolicy @@ -17,21 +16,25 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-ThrottlingPolicy cmdlet to remove a non-default Microsoft Exchange throttling policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-ThrottlingPolicy [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [-Force] [] +Remove-ThrottlingPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION You can't remove the default client throttling policy. Also, you can't remove a policy associated with any users. For more information, see Example 2. -For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,7 +47,15 @@ This example removes the user throttling policy ClientThrottlingPolicy2. ### Example 2 ```powershell -$policy = Get-ThrottlingPolicy ClientThrottlingPolicy2; $mailboxes = Get-Mailbox | where-object {$_.ThrottlingPolicy -eq $policy.Identity}; $defaultPolicy = Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true}; foreach ($mailbox in $mailboxes) {Set-Mailbox -Identity $mailbox.Identity -ThrottlingPolicy $defaultPolicy}; Remove-ThrottlingPolicy ClientThrottlingPolicy2 +$policy = Get-ThrottlingPolicy ClientThrottlingPolicy2 + +$mailboxes = Get-Mailbox | where-object {$_.ThrottlingPolicy -eq $policy.Identity} + +$defaultPolicy = Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true} + +foreach ($mailbox in $mailboxes) {Set-Mailbox -Identity $mailbox.Identity -ThrottlingPolicy $defaultPolicy} + +Remove-ThrottlingPolicy ClientThrottlingPolicy2 ``` You can't remove a policy that's associated with any users. This example reassigns the users subject to ClientThrottlingPolicy2 to the default policy. Then, it removes ClientThrottlingPolicy2. @@ -70,8 +81,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -105,14 +115,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -Force +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. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -121,14 +133,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Force -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. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. 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 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -142,12 +154,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-TransportRule.md b/exchange/exchange-ps/exchange/Remove-TransportRule.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance/Remove-TransportRule.md rename to exchange/exchange-ps/exchange/Remove-TransportRule.md index eeaab2da27..110d9f1322 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-TransportRule.md +++ b/exchange/exchange-ps/exchange/Remove-TransportRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-transportrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Remove-TransportRule @@ -17,12 +16,15 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Remove-TransportRule cmdlet to remove transport rules (mail flow rules) from your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-TransportRule [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-TransportRule [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ On Mailbox servers, this cmdlet removes the rule from Active Directory. On an Ed To temporarily disable a transport rule without removing it, use the Disable-TransportRule cmdlet instead. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,9 +50,7 @@ This example removes the rule named "Redirect messages from kim@contoso.com to l The Identity parameter specifies the rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -69,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -127,12 +126,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Remove-UMAutoAttendant.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Remove-UMAutoAttendant.md rename to exchange/exchange-ps/exchange/Remove-UMAutoAttendant.md index 214b561239..902c636055 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMAutoAttendant.md +++ b/exchange/exchange-ps/exchange/Remove-UMAutoAttendant.md @@ -1,28 +1,31 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/remove-umautoattendant -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-UMAutoAttendant ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Remove-UMAutoAttendant cmdlet to delete a Unified Messaging (UM) auto attendant. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-UMAutoAttendant [-Identity] [-Confirm] [-DomainController ] [-WhatIf] [] +Remove-UMAutoAttendant [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -30,7 +33,7 @@ The Remove-UMAutoAttendant cmdlet deletes an existing UM auto attendant from Act After this task is completed, the UM auto attendant is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,7 +53,7 @@ The Identity parameter specifies the identifier for the UM auto attendant being Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -62,15 +65,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -80,15 +82,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -104,7 +104,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -118,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Remove-UMCallAnsweringRule.md similarity index 78% rename from exchange/exchange-ps/exchange/unified-messaging/Remove-UMCallAnsweringRule.md rename to exchange/exchange-ps/exchange/Remove-UMCallAnsweringRule.md index f924b84309..85003d4509 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/exchange/Remove-UMCallAnsweringRule.md @@ -1,29 +1,32 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/remove-umcallansweringrule -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-UMCallAnsweringRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Remove-UMCallAnsweringRule cmdlet to remove an existing Unified Messaging (UM) call answering rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-UMCallAnsweringRule [-Identity] [-Confirm] [-DomainController ] - [-Mailbox ] [-WhatIf] [] +Remove-UMCallAnsweringRule [-Identity] + [-Confirm] + [-DomainController ] + [-Mailbox ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +34,7 @@ The Remove-UMCallAnsweringRule cmdlet removes an existing UM call answering rule After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,7 +61,7 @@ The Identity parameter specifies the identifier for a call answering rule being Type: UMCallAnsweringRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -70,15 +73,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -88,15 +90,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -109,23 +109,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the mailbox of the user who is running the command is used. @@ -134,7 +125,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -150,7 +141,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -164,12 +155,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMDialPlan.md b/exchange/exchange-ps/exchange/Remove-UMDialPlan.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Remove-UMDialPlan.md rename to exchange/exchange-ps/exchange/Remove-UMDialPlan.md index 6c26864b80..15968a4562 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMDialPlan.md +++ b/exchange/exchange-ps/exchange/Remove-UMDialPlan.md @@ -1,28 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/remove-umdialplan -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-UMDialPlan ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Remove-UMDialPlan cmdlet to delete an existing Unified Messaging (UM) dial plan. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-UMDialPlan [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-UMDialPlan [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ The Remove-UMDialPlan cmdlet deletes an existing UM dial plan from Active Direct After this task is completed, the UM dial plan is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +53,7 @@ The Identity parameter specifies the identifier for the UM dial plan being delet Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,15 +65,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -81,15 +82,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -105,7 +104,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMHuntGroup.md b/exchange/exchange-ps/exchange/Remove-UMHuntGroup.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Remove-UMHuntGroup.md rename to exchange/exchange-ps/exchange/Remove-UMHuntGroup.md index a3c87d82b7..0923af3a69 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMHuntGroup.md +++ b/exchange/exchange-ps/exchange/Remove-UMHuntGroup.md @@ -1,28 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/remove-umhuntgroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-UMHuntGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Remove-UMHuntGroup cmdlet to remove and delete an existing Unified Messaging (UM) hunt group. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-UMHuntGroup [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-UMHuntGroup [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ The Remove-UMHuntGroup cmdlet deletes an existing UM hunt group from Active Dire After this task is completed, the UM hunt group is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +53,7 @@ The Identity parameter specifies the identifier for the UM hunt group being dele Type: UMHuntGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,15 +65,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -81,15 +82,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -105,7 +104,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMIPGateway.md b/exchange/exchange-ps/exchange/Remove-UMIPGateway.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Remove-UMIPGateway.md rename to exchange/exchange-ps/exchange/Remove-UMIPGateway.md index 1a79bc4938..e19873e3a1 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMIPGateway.md +++ b/exchange/exchange-ps/exchange/Remove-UMIPGateway.md @@ -1,28 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/remove-umipgateway -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-UMIPGateway ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Remove-UMIPGateway cmdlet to delete a Unified Messaging (UM) IP gateway. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-UMIPGateway [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-UMIPGateway [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -33,7 +35,7 @@ The Remove-UMIPGateway cmdlet should be run only by an administrator who fully u After this task is completed, the UM IP gateway is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,7 +55,7 @@ The Identity parameter specifies the identifier for the UM IP gateway being dele Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -65,15 +67,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -83,15 +84,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -107,7 +106,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -121,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMMailboxPolicy.md b/exchange/exchange-ps/exchange/Remove-UMMailboxPolicy.md similarity index 80% rename from exchange/exchange-ps/exchange/unified-messaging/Remove-UMMailboxPolicy.md rename to exchange/exchange-ps/exchange/Remove-UMMailboxPolicy.md index d3bbe419ac..56d19d3378 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Remove-UMMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-UMMailboxPolicy.md @@ -1,28 +1,30 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/remove-ummailboxpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Remove-UMMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Remove-UMMailboxPolicy cmdlet to delete a Unified Messaging (UM) mailbox policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-UMMailboxPolicy [-Identity] [-Confirm] [-DomainController ] [-WhatIf] +Remove-UMMailboxPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` @@ -31,7 +33,7 @@ The Remove-UMMailboxPolicy cmdlet deletes or removes a UM mailbox policy. If the After this task is completed, the UM mailbox policy is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +53,7 @@ The Identity parameter specifies the identifier for the UM mailbox policy being Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,15 +65,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -81,15 +82,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -105,7 +104,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md new file mode 100644 index 0000000000..ed810f1d9c --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md @@ -0,0 +1,144 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-UnifiedAuditLogRetentionPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-UnifiedAuditLogRetentionPolicy cmdlet to delete audit log retention policies from the Microsoft Defender portal or the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-UnifiedAuditLogRetentionPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-ForceDeletion] + [-WhatIf] + [] +``` + +## DESCRIPTION +It might take up to 30 minutes for the policy to be completely removed. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-UnifiedAuditLogRetentionPolicy -Identity "SearchQueryPerformed by app@sharepoint" +``` + +This example deletes the audit log retention policy named "SearchQueryPerformed by app@sharepoint". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceDeletion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-UnifiedGroup.md b/exchange/exchange-ps/exchange/Remove-UnifiedGroup.md new file mode 100644 index 0000000000..8c186032fb --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-UnifiedGroup.md @@ -0,0 +1,134 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-UnifiedGroup + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-UnifiedGroup cmdlet to remove Microsoft 365 Groups from your cloud-based organization. + +**Note**: You can't use this cmdlet to remove Microsoft 365 Groups if you connect using certificate based authentication (also known as CBA or app-only authentication for unattended scripts) or Azure managed identity. You can use Microsoft Graph instead. For more information, see [Delete group](https://learn.microsoft.com/graph/api/group-delete). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-UnifiedGroup [-Identity] + [-Confirm] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-UnifiedGroup -Identity "Research Department" +``` + +This example removes the Microsoft 365 Group named Research Department. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: UnifiedGroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/Remove-UnifiedGroupLinks.md new file mode 100644 index 0000000000..f6ae947e09 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-UnifiedGroupLinks.md @@ -0,0 +1,167 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-UnifiedGroupLinks + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Remove-UnifiedGroupLinks cmdlet to remove members, owners, and subscribers from Microsoft 365 Groups in your cloud-based organization. To add members, owners and subscribers, use the Add-UnifiedGroupLinks cmdlet. To modify other properties of Microsoft 365 Groups, use the Set-UnifiedGroup cmdlet. + +> [!NOTE] +> You can't use this cmdlet to modify Microsoft 365 Group members, owners, or subscribers if you connect using certificate based authentication (also known as CBA or app-only authentication for unattended scripts) or Azure managed identity. You can use Microsoft Graph instead. For more information, see [Group resource type](https://learn.microsoft.com/graph/api/resources/group). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-UnifiedGroupLinks [-Identity] -Links -LinkType + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-UnifiedGroupLinks -Identity "Legal Department" -LinkType Members -Links laura@contoso.com,julia@contoso.com +``` + +This example removes members `laura@contoso.com` and `julia@contoso.com` from the Microsoft 365 Group named Legal Department. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: UnifiedGroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Links +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +You must use this parameter with the LinkType parameter, which means the specified recipients are removed from the same role in the Microsoft 365 Group (you can't remove recipients from different roles in the same command). + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LinkType +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. +- Owners: Add or remove members, delete conversations, changes Team settings, delete the Team, and full control of the connected SharePoint site. A group must have at least one owner. +- Subscribers: Existing group members who receive conversation and calendar event notifications from the group. All subscribers are members of the group, but all members aren't necessarily subscribers (depending on the AutoSubscribeNewMembers property value of the group and when the member was added). + +You must use this parameter with the Links parameter. + +```yaml +Type: LinkType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-UserPhoto.md b/exchange/exchange-ps/exchange/Remove-UserPhoto.md new file mode 100644 index 0000000000..fa074e42db --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-UserPhoto.md @@ -0,0 +1,236 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-UserPhoto + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Remove-UserPhoto cmdlet to delete the photo associated with a user's account. The user photo feature allows users to associate a picture with their account. User photos appear in client applications, such as Outlook, Microsoft Teams, and SharePoint. + +**Note**: In Microsoft 365, you can manage user photos in Microsoft Graph PowerShell. For instructions, see [Manage user photos in Microsoft Graph PowerShell](https://learn.microsoft.com/microsoft-365/admin/add-users/change-user-profile-photos#manage-user-photos-in-microsoft-graph-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Remove-UserPhoto [-Identity] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-WhatIf] + [] +``` + +### ClearMailboxPhoto +``` +Remove-UserPhoto [-Identity] + [-ClearMailboxPhotoRecord] + [-GroupMailbox] + [-PhotoType ] + [-Confirm] + [-DomainController ] + [-IgnoreDefaultScope] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the Remove-UserPhoto cmdlet to delete the user photo currently associated with a user's account. This cmdlet removes the photo from user's Exchange mailbox root. +In on-premises Exchange, it also removes the user's photo from their Active Directory account. Administrators can also use the Exchange admin center (EAC) to delete user photos by accessing the Options page in the user's mailbox in Outlook on the web. + +**Notes**: Changes to the user photo won't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-UserPhoto "Ann Beebe" +``` + +This example deletes the photo associated with Ann Beebe's user account. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ClearMailboxPhotoRecord +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: + +- Return a blank photo. +- Prevent searching Active Directory for a photo. + +Using this switch allows photo requests to search Active Directory for a photo. + +```yaml +Type: SwitchParameter +Parameter Sets: ClearMailboxPhoto +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhotoType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Remove-VivaModuleFeaturePolicy.md new file mode 100644 index 0000000000..e263889a41 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-VivaModuleFeaturePolicy.md @@ -0,0 +1,176 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-VivaModuleFeaturePolicy + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. Once you delete a policy, the policy is permanently deleted. You cannot undo the deletion. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX +``` +Remove-VivaModuleFeaturePolicy -FeatureId -ModuleId -PolicyId + [-Confirm] + [-ResultSize ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. + +You need to use the Connect-ExchangeOnline cmdlet to authenticate. + +This cmdlet requires the .NET Framework 4.7.2 or later. + +Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. + +To learn more about assigned roles at the feature level, see [Features Available for Feature Access Management](https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Remove-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -PolicyId 3db38dfa-02a3-4039-b33a-42b0b3da029b +``` + +This example deletes the specified policy for the Reflection feature in Viva Insights. + +## PARAMETERS + +### -FeatureId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModuleId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Exchange PowerShell](https://learn.microsoft.com/powershell/module/exchange) + +[About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2) + +[Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids) diff --git a/exchange/exchange-ps/exchange/Remove-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/exchange/Remove-VivaOrgInsightsDelegatedRole.md new file mode 100644 index 0000000000..037e2a9216 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-VivaOrgInsightsDelegatedRole.md @@ -0,0 +1,112 @@ +--- +external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml +Module Name: ExchangeOnlineManagement +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: +--- + +# Remove-VivaOrgInsightsDelegatedRole + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.7.1 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Remove-VivaOrgInsightsDelegatedRole cmdlet to remove delegate access from the specified account (the delegate) so they can't view organizational insights like the leader (the delegator). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-VivaOrgInsightsDelegatedRole -Delegate -Delegator + [-ResultSize ] + [] +``` + +## DESCRIPTION +Use the Get-VivaOrgInsightsDelegatedRole cmdlet to find the Microsoft Entra ObjectId values of delegate accounts that were given the capabilities of delegator accounts. + +To run this cmdlet, you need to be a member of one of the following role groups in Microsoft Entra ID in the destination organization: + +- Global Administrator +- Insights Administrator + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Remove-VivaOrgInsightsDelegatedRole -Delegate 5eaf7164-f36f-5381-5546-dcaa1792f077 -Delegator 043f6d38-378b-7dcd-7cd8-c1a901881fa9 +``` + +This example removes the organization insights viewing capability of the specified delegator account from the specified delegate account. + +## PARAMETERS + +### -Delegate +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Delegator +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. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Remove-WebServicesVirtualDirectory.md b/exchange/exchange-ps/exchange/Remove-WebServicesVirtualDirectory.md similarity index 82% rename from exchange/exchange-ps/exchange/client-access-servers/Remove-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/exchange/Remove-WebServicesVirtualDirectory.md index 1bbe043121..f4f42ba089 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Remove-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Remove-WebServicesVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/remove-webservicesvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-WebServicesVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-WebServicesVirtualDirectory cmdlet to remove existing Exchange Web Services virtual directories from Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,13 +25,14 @@ Remove-WebServicesVirtualDirectory [-Identity] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can remove the default Exchange Web Services virtual directory or another Exchange Web Services virtual directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,13 +48,11 @@ This example removes the Exchange Web Services virtual directory named Sales fro ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -72,8 +70,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -106,7 +103,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -142,12 +141,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Remove-X400AuthoritativeDomain.md b/exchange/exchange-ps/exchange/Remove-X400AuthoritativeDomain.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Remove-X400AuthoritativeDomain.md rename to exchange/exchange-ps/exchange/Remove-X400AuthoritativeDomain.md index 2f0a414510..f6c5c5dddd 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/exchange/Remove-X400AuthoritativeDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-x400authoritativedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Remove-X400AuthoritativeDomain @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Remove-X400AuthoritativeDomain cmdlet to remove an X.400 authoritative domain. When you remove an X.400 authoritative domain, the X.400 authoritative domain object is deleted from Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Remove-X400AuthoritativeDomain [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Remove-X400AuthoritativeDomain [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +61,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,12 +116,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Remove-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/Remove-eDiscoveryCaseAdmin.md new file mode 100644 index 0000000000..828137cfb4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Remove-eDiscoveryCaseAdmin.md @@ -0,0 +1,113 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Remove-eDiscoveryCaseAdmin + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Remove-eDiscoveryCaseAdmin cmdlet to remove an eDiscovery Administrator from the Microsoft Purview compliance portal. To replace all eDiscovery Administrators, use the Update-eDiscoveryCaseAdmin cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Remove-eDiscoveryCaseAdmin -User + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +An eDiscovery Administrator is member of the eDiscovery Manager role group who can also view and access all eDiscovery cases in your organization. + +When you remove a user from the list of eDiscovery Administrators, the user isn't removed from the eDiscovery Manager role group. That means the user can still view and access the eDiscovery cases they are a member of and the eDiscovery cases they created. To remove all eDiscovery permissions, you can remove the user from the eDiscovery Manager role group by running the Remove-RoleGroupMember cmdlet. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Remove-eDiscoveryCaseAdmin -User chris@contoso.com +``` + +This example removes an eDiscovery Administrator. + +## PARAMETERS + +### -User +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/active-directory/Reset-ProvisioningCache.md b/exchange/exchange-ps/exchange/Reset-ProvisioningCache.md similarity index 89% rename from exchange/exchange-ps/exchange/active-directory/Reset-ProvisioningCache.md rename to exchange/exchange-ps/exchange/Reset-ProvisioningCache.md index 4f6112c5da..0c541d75c8 100644 --- a/exchange/exchange-ps/exchange/active-directory/Reset-ProvisioningCache.md +++ b/exchange/exchange-ps/exchange/Reset-ProvisioningCache.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/reset-provisioningcache +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Reset-ProvisioningCache @@ -17,24 +16,29 @@ This cmdlet is available only in on-premises Exchange. The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. This cmdlet is only used for diagnostic purposes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### GlobalCache ``` -Reset-ProvisioningCache [-Server] -Application [-GlobalCache] +Reset-ProvisioningCache [-Server] -Application + [-GlobalCache] [-CacheKeys ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### OrganizationCache ``` -Reset-ProvisioningCache [-Server] -Application ] [-CurrentOrganization] [-Organizations ] +Reset-ProvisioningCache [-Server] -Application ] + [-CurrentOrganization] + [-Organizations ] [-CacheKeys ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -42,7 +46,7 @@ The Reset-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. To reduce Active Directory requests, a provisioning cache is initialized in each Windows PowerShell runspace and is used to cache common objects that are frequently used by cmdlets and provisioning handlers. During Exchange cmdlet execution, the provisioning cache loads configuration objects from Active Directory to help run a cmdlet. For example, when you create a mailbox, the New-Mailbox cmdlet obtains properties from Active Directory. When running cmdlets, configuration objects such as database containers, administrative role groups, and LegacyDNs are retrieved from Active Directory. Because these types of objects are stable and don't change for months or years after they're created, they're stored in the provisioning cache used by Windows PowerShell. This increases provisioning efficiency and significantly improves cmdlet performance. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,19 +66,30 @@ This example runs in a multi-tenant deployment by a data center administrator to ## PARAMETERS +### -Server +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Application The Application parameter specifies the specific administrative application to reset the provisioning cache for. You can use the following values: - Powershell - - Powershell-LiveId - - Powershell-Proxy - - PowershellLiveId-Proxy - - Ecp - - Psws ```yaml @@ -91,7 +106,7 @@ Accept wildcard characters: False ``` ### -GlobalCache -The GlobalCache switch specifies that all cache keys are cleared. +The GlobalCache switch clears all cache keys. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -106,22 +121,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Server -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -CacheKeys 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 @@ -143,8 +142,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -161,7 +159,7 @@ Accept wildcard characters: False ``` ### -CurrentOrganization -The CurrentOrganization switch specifies that the provision cache is reset for this organization. +The CurrentOrganization switch resets the provision cache for the organization. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -213,12 +211,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Restore-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/Restore-DatabaseAvailabilityGroup.md similarity index 88% rename from exchange/exchange-ps/exchange/database-availability-groups/Restore-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/exchange/Restore-DatabaseAvailabilityGroup.md index 34edc828de..e7ed934cf1 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Restore-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/exchange/Restore-DatabaseAvailabilityGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/restore-databaseavailabilitygroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Restore-DatabaseAvailabilityGroup @@ -17,31 +16,35 @@ This cmdlet is available only in on-premises Exchange. Use the Restore-DatabaseAvailabilityGroup cmdlet as part of a datacenter switchover of a database availability group (DAG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Restore-DatabaseAvailabilityGroup [-Identity] - [-ActiveDirectorySite ] [-AlternateWitnessDirectory ] - [-AlternateWitnessServer ] [-Confirm] [-DomainController ] [-WhatIf] - [-UsePrimaryWitnessServer] [] + [-ActiveDirectorySite ] + [-AlternateWitnessDirectory ] + [-AlternateWitnessServer ] + [-Confirm] + [-DomainController ] + [-UsePrimaryWitnessServer] + [-WhatIf] + [] ``` ## DESCRIPTION You can also use this cmdlet for disaster recovery purposes to restore functionality to a DAG that has lost quorum due to one or more DAG members being offline for an extended period. Before running this cmdlet, you must first run the Stop-DatabaseAvailabilityGroup cmdlet. -The Restore-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode parameter value of DagOnly. For more information about the DatacenterActivationMode parameter, see [Datacenter Activation Coordination mode](https://docs.microsoft.com/Exchange/high-availability/database-availability-groups/dac-mode). +The Restore-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode parameter value of DagOnly. For more information about the DatacenterActivationMode parameter, see [Datacenter Activation Coordination mode](https://learn.microsoft.com/Exchange/high-availability/database-availability-groups/dac-mode). You can use the Set-DatabaseAvailabilityGroup cmdlet to configure the value for the DatacenterActivationMode parameter. The Restore-DatabaseAvailabilityGroup cmdlet performs several operations that affect the structure and membership of the DAG's cluster. This task does the following: - Forcibly evicts the servers listed on the StoppedMailboxServers list from the DAG's cluster, thereby reestablishing quorum for the cluster enabling the surviving DAG members to start and provide service. - - Configures the DAG to use the alternate witness server if there is an even number of surviving DAG members, or a single surviving DAG member. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -128,10 +131,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -161,14 +165,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -UsePrimaryWitnessServer +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: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -177,14 +181,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -UsePrimaryWitnessServer -The UsePrimaryWitnessServer parameter specifies that the DAG's currently configured witness server should be used if a witness is needed by the DAG members being activated. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. 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 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -198,12 +202,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Restore-DetailsTemplate.md b/exchange/exchange-ps/exchange/Restore-DetailsTemplate.md similarity index 89% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Restore-DetailsTemplate.md rename to exchange/exchange-ps/exchange/Restore-DetailsTemplate.md index 39ebb39f77..c064436cf5 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Restore-DetailsTemplate.md +++ b/exchange/exchange-ps/exchange/Restore-DetailsTemplate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/restore-detailstemplate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Restore-DetailsTemplate @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Restore-DetailsTemplate cmdlet to restore the specified template to its default state. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Restore-DetailsTemplate [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Restore-DetailsTemplate [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Details templates can't be created or deleted, but this task restores the specified template to its default state. All user changes are lost. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,15 +48,10 @@ This example restores the default attributes to the User details template for th 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 - - Group - - PublicFolder - - SearchDialog - - MailboxAgent - - Contact ```yaml @@ -73,10 +70,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -127,12 +125,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Restore-Mailbox.md b/exchange/exchange-ps/exchange/Restore-Mailbox.md similarity index 88% rename from exchange/exchange-ps/exchange/mailboxes/Restore-Mailbox.md rename to exchange/exchange-ps/exchange/Restore-Mailbox.md index c1e556d54d..8e775b1697 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Restore-Mailbox.md +++ b/exchange/exchange-ps/exchange/Restore-Mailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/restore-mailbox +online version: https://learn.microsoft.com/powershell/module/exchange/restore-mailbox applicable: Exchange Server 2010 title: Restore-Mailbox schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Restore-Mailbox @@ -17,26 +16,39 @@ This cmdlet is available only in Exchange Server 2010. Use the Restore-Mailbox cmdlet to extract mailbox content from a restored database. -Note: In Exchange Server 2010 Service Pack 1 (SP1) or later, use the New-MailboxRestoreRequest cmdlet instead of the Restore-Mailbox cmdlet to extract mailbox content from a restored database. +**Note**: In Exchange Server 2010 Service Pack 1 (SP1) or later, use the New-MailboxRestoreRequest cmdlet instead of the Restore-Mailbox cmdlet to extract mailbox content from a restored database. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Restore-Mailbox [-Identity] -RecoveryDatabase - -RecoveryMailbox -TargetFolder [-AllowDuplicates] - [-AllContentKeywords ] [-AttachmentFilenames ] [-BadItemLimit ] [-Confirm] - [-ContentKeywords ] [-EndDate ] [-ExcludeFolders ] - [-GlobalCatalog ] [-IncludeFolders ] [-Locale ] [-MaxThreads ] - [-RecipientKeywords ] [-SenderKeywords ] [-StartDate ] - [-SubjectKeywords ] [-ValidateOnly] [-WhatIf] [] +Restore-Mailbox [-Identity] -RecoveryDatabase -RecoveryMailbox -TargetFolder + [-AllowDuplicates] + [-AllContentKeywords ] + [-AttachmentFilenames ] + [-BadItemLimit ] + [-Confirm] + [-ContentKeywords ] + [-EndDate ] + [-ExcludeFolders ] + [-GlobalCatalog ] + [-IncludeFolders ] + [-Locale ] + [-MaxThreads ] + [-RecipientKeywords ] + [-SenderKeywords ] + [-StartDate ] + [-SubjectKeywords ] + [-ValidateOnly] + [-WhatIf] + [] ``` ## DESCRIPTION The Restore-Mailbox cmdlet copies end-user data from any server running Microsoft Exchange Server 2010 to a mailbox on an Exchange 2010 Mailbox server in the same organization that has adequate space and resources to support the mailbox. The Restore-Mailbox cmdlet can only use disconnected mailboxes on a server as a source of data, and the cmdlet can only use connected mailboxes as a target for data. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,23 +86,14 @@ This example bulk restores all the mailboxes in the MyDatabase mailbox database The Identity parameter specifies the mailbox that you want to restore. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -110,9 +113,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID ```yaml @@ -163,7 +164,9 @@ Accept wildcard characters: False ``` ### -AllowDuplicates -The AllowDuplicates parameter specifies whether to copy mail items without checking if they're duplicates of existing items and without removing duplicate items. We recommend that you use the AllowDuplicates parameter together with the IncludeFolders parameter. +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. ```yaml Type: SwitchParameter @@ -182,9 +185,7 @@ Accept wildcard characters: False The AllContentKeywords parameter specifies the filters for all of the following: - Subject - - Message body - - Attachment content This allows an OR search of all these fields. If your search criteria are part of the subject, message body, or attachment content, you get results. @@ -237,8 +238,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -271,7 +271,7 @@ Accept wildcard characters: False ``` ### -EndDate -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. +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 @@ -431,7 +431,9 @@ Accept wildcard characters: False ``` ### -ValidateOnly -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. +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. ```yaml Type: SwitchParameter @@ -467,12 +469,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/mailboxes/Restore-RecoverableItems.md b/exchange/exchange-ps/exchange/Restore-RecoverableItems.md similarity index 77% rename from exchange/exchange-ps/exchange/mailboxes/Restore-RecoverableItems.md rename to exchange/exchange-ps/exchange/Restore-RecoverableItems.md index c159c1c053..5132660f97 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Restore-RecoverableItems.md +++ b/exchange/exchange-ps/exchange/Restore-RecoverableItems.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/Restore-RecoverableItems +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Restore-RecoverableItems @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Restore-RecoverableItems items cmdlet to restore deleted items in mailboxes. You use the Get-RecoverableItems cmdlet to find the deleted items to recover. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -47,6 +46,8 @@ Restore-RecoverableItems -Identity [-LastParentFolderID ] [-MaxParallelSize ] [-NoOutput] + [-PolicyTag ] + [-RestoreTargetFolder ] [-ResultSize ] [-SourceFolder ] [-SubjectContains ] @@ -56,7 +57,7 @@ Restore-RecoverableItems -Identity ## DESCRIPTION Items are restored to the original folder location if the information is available for the item. If the information can't be found, the item is restored to the default folder for the item type (Inbox for messages, Calendar for meetings and appointments, etc.). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,18 +69,16 @@ Restore-RecoverableItems -Identity laura@contoso.com -FilterItemType IPM.Note -S After using the Get-RecoverableItems cmdlet to verify the existence of the item, this example restores the specified deleted item from the specified mailbox: - Mailbox: laura@contoso.com - - Item type: Email message - - Message subject: FY18 Accounting - - Location: Recoverable Items\Deletions - - Date range: 2/1/2018 to 2/5/2018 ### Example 2 ```powershell -$mailboxes = Import-CSV "C:\My Documents\RestoreMessage.csv"; $mailboxes | foreach {Restore-RecoverableItems -Identity $_.SMTPAddress -SubjectContains Project X" -SourceFolder DeletedItems -FilterItemType IPM.Note} +$mailboxes = Import-CSV "C:\My Documents\RestoreMessage.csv" + +$mailboxes | foreach {Restore-RecoverableItems -Identity $_.SMTPAddress -SubjectContains "Project X" -SourceFolder DeletedItems -FilterItemType IPM.Note} ``` In Exchange Server, this example restores the deleted email message "Project X" for the mailboxes that are specified in the comma-separated value (CSV) file C:\\My Documents\\RestoreMessage.csv. The CSV file uses the header value SMTPAddress, and contains the email address of each mailbox on a separate line like this: @@ -104,43 +103,36 @@ Restore-RecoverableItems -Identity "malik@contoso.com","lillian@contoso.com" -Fi In Exchange Online, after using the Get-RecoverableItems cmdlet to verify the existence of the item, this example restores the specified deleted items in the specified mailboxes: - Mailboxes: malik@contoso.com, lillian@contoso.com - - Item type: Email message - - Message subject: COGS FY17 Review - - Location: Recoverable Items\Deletions - - Date range: 3/15/2019 to 3/25/2019 - - Number of mailboxes processed simultaneously: 2 +### Example 4 +```powershell +Get-RecoverableItems administrator | Restore-RecoverableItems +``` + +This example bulk restores all the recoverable items for administrator. + ## PARAMETERS ### -Identity 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -In Exchange Online, you can specify multiple mailboxes separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +In Exchange Online, you can specify multiple mailboxes separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. ```yaml Type: GeneralMailboxOrMailUserIdParameter @@ -187,9 +179,9 @@ Accept wildcard characters: False ``` ### -FilterEndTime -The FilterEndTime specifies the end date/time of the date range. +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". +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". ```yaml Type: DateTime @@ -208,20 +200,16 @@ Accept wildcard characters: False The FilterItemType parameter filters the results by the specified MessageClass (ItemClass) property value of the deleted item. For example: - IPM.Appointment (Meetings and appointments) - - IPM.Contact - - IPM.File - - IPM.Note - - IPM.Task ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -231,9 +219,9 @@ Accept wildcard characters: False ``` ### -FilterStartTime -The FilterStartTime specifies the start date/time of the date range. +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". +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". ```yaml Type: DateTime @@ -287,7 +275,7 @@ Accept wildcard characters: False ### -NoOutput This parameter is available only in the cloud-based service. -The NoOutput switch specifies whether to restore the deleted items directly without any command output in the console. You don't need to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -302,14 +290,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. +### -PolicyTag +This parameter is available only in the cloud-based service. + +{{ Fill PolicyTag Description }} ```yaml -Type: Unlimited -Parameter Sets: (All) +Type: String[] +Parameter Sets: Default Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -318,23 +308,42 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SourceFolder -The SourceFolder parameter specifies where to search for deleted items in the mailbox. Valid values are: +### -RestoreTargetFolder +This parameter is available only in the cloud-based service. -- DeletedItems: The Deleted Items folder. +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. -- RecoverableItems: The Recoverable Items\Deletions folder. This folder contains items that have been deleted from the Deleted Items folder (soft-deleted items). +This parameter is available only on primary mailboxes and is ignored on archive mailboxes. A destination folder will be created if it does not exist. Valid paths are: -- PurgedItems: (Cloud only) The Recoverable Items\Purges folder. This folder contains items that have been purged from the Recoverable Items folder (hard-deleted items). +- `/` +- `/folder1` +- `/folder1/folder2` +- `folder1` +- `folder1/folder2` -If you don't use this parameter, the command will search all of these folders. +The preceding or trailing `/` will be ignored. Then, it will be treated as the relative path of the IPM sub-tree: `/Top Of Information Store`. ```yaml -Type: RecoverableItemsFolderType -Parameter Sets: OnPremises +Type: String +Parameter Sets: Default Aliases: -Accepted values: DeletedItems | RecoverableItems -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -343,12 +352,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceFolder +The SourceFolder parameter specifies where to search for deleted items in the mailbox. Valid values are: + +- DeletedItems: The Deleted Items folder. +- RecoverableItems: The Recoverable Items\Deletions folder. This folder contains items that have been deleted from the Deleted Items folder (soft-deleted items). +- PurgedItems: The Recoverable Items\Purges folder. This folder contains items that have been purged from the Recoverable Items folder (hard-deleted items). + +If you don't use this parameter, the command searches those three folders. + +- DiscoveryHoldsItems (cloud-only): The Recoverable Items\DiscoveryHolds folder. This folder contains items that have been purged from the Recoverable Items folder (hard-deleted items) and are protected by a hold. To search for deleted items in this folder, use this parameter with the value DiscoveryHoldsItems. + ```yaml Type: RecoverableItemsFolderType -Parameter Sets: Cloud +Parameter Sets: OnPrem Aliases: -Accepted values: DeletedItems | RecoverableItems | PurgedItems -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -378,12 +397,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Resume-MailboxDatabaseCopy.md b/exchange/exchange-ps/exchange/Resume-MailboxDatabaseCopy.md similarity index 87% rename from exchange/exchange-ps/exchange/database-availability-groups/Resume-MailboxDatabaseCopy.md rename to exchange/exchange-ps/exchange/Resume-MailboxDatabaseCopy.md index 03381bdf1f..fd5c0c4ae9 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Resume-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/exchange/Resume-MailboxDatabaseCopy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/resume-mailboxdatabasecopy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Resume-MailboxDatabaseCopy @@ -17,30 +16,35 @@ This cmdlet is available only in on-premises Exchange. Use the Resume-MailboxDatabaseCopy cmdlet to unblock activation or resume log copying and replay for a passive mailbox database copy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Resume-MailboxDatabaseCopy [-Identity] [-ReplicationOnly] +Resume-MailboxDatabaseCopy [-Identity] + [-ReplicationOnly] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### DisableReplayLag ``` -Resume-MailboxDatabaseCopy [-Identity] [-DisableReplayLag] [-DisableReplayLagReason ] +Resume-MailboxDatabaseCopy [-Identity] + [-DisableReplayLag] + [-DisableReplayLagReason ] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Resume-MailboxDatabaseCopy cmdlet resumes replication and replay from a suspended state. If a database copy was suspended without administrator intervention, it's because the database copy is in a bad state. You can use the Get-MailboxDatabaseCopyStatus cmdlet to see if there are any messages indicating a failure. If the copy of the database is in a bad state, resuming the copy causes replication to fail and the mailbox database copy to return to a suspended state. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,8 +83,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -96,30 +99,30 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -DisableReplayLag +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: Fqdn -Parameter Sets: (All) +Type: SwitchParameter +Parameter Sets: DisableReplayLag Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -Required: False +Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -ReplicationOnly -The ReplicationOnly switch specifies whether to resume replication without affecting the activation setting (for example, the ActivationSuspended property for the database copy remains set to True). +### -DisableReplayLagReason +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: SwitchParameter -Parameter Sets: Identity +Type: String +Parameter Sets: DisableReplayLag Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -128,13 +131,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: SwitchParameter +Type: Fqdn Parameter Sets: (All) -Aliases: wi +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -144,30 +147,30 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -DisableReplayLag -The DisableReplayLag parameter specifies that any configured replay lag time for the database copy should be disabled when the passive copy is resumed. +### -ReplicationOnly +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: DisableReplayLag +Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -Required: True +Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -DisableReplayLagReason -The DisableReplayLagReason parameter is used with the DisableReplayLag parameter to specify an administrative reason for disabling replay lag time for a passive copy. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: String -Parameter Sets: DisableReplayLag -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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,12 +184,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Resume-MailboxExportRequest.md b/exchange/exchange-ps/exchange/Resume-MailboxExportRequest.md similarity index 86% rename from exchange/exchange-ps/exchange/mailboxes/Resume-MailboxExportRequest.md rename to exchange/exchange-ps/exchange/Resume-MailboxExportRequest.md index cd24dcebca..48f67e84d6 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Resume-MailboxExportRequest.md +++ b/exchange/exchange-ps/exchange/Resume-MailboxExportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/resume-mailboxexportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Resume-MailboxExportRequest @@ -17,21 +16,24 @@ This cmdlet is available only in on-premises Exchange. Use the Resume-MailboxExportRequest cmdlet to resume an export request that was suspended or failed. -This cmdlet is available only in the Mailbox Import Export role and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Resume-MailboxExportRequest [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Resume-MailboxExportRequest [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Resume-MailboxExportRequest cmdlet can be pipelined with the Get-MailboxExportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,7 +54,7 @@ This example resumes any failed export move requests. ## PARAMETERS ### -Identity -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: \\\\. +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 @@ -70,8 +72,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,12 +125,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Resume-MailboxImportRequest.md b/exchange/exchange-ps/exchange/Resume-MailboxImportRequest.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Resume-MailboxImportRequest.md rename to exchange/exchange-ps/exchange/Resume-MailboxImportRequest.md index bc1f3cfd54..f1d190bae5 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Resume-MailboxImportRequest.md +++ b/exchange/exchange-ps/exchange/Resume-MailboxImportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/resume-mailboximportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Resume-MailboxImportRequest @@ -17,21 +16,26 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Resume-MailboxImportRequest cmdlet to resume an import request that was suspended or failed. -This cmdlet is available only in the Mailbox Import Export role and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +NOTE: This cmdlet is no longer supported in Exchange Online. To import a .pst file in Exchange Online, see [Use network upload to import PST files](https://learn.microsoft.com/purview/use-network-upload-to-import-pst-files). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +This cmdlet is available only in the Mailbox Import Export role and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Resume-MailboxImportRequest [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] +Resume-MailboxImportRequest [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION This cmdlet can be pipelined with the Get-MailboxImportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,7 +56,7 @@ This example resumes all failed import requests. ## PARAMETERS ### -Identity -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: \\\\. +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 @@ -70,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,12 +129,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Resume-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/Resume-MailboxRestoreRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Resume-MailboxRestoreRequest.md rename to exchange/exchange-ps/exchange/Resume-MailboxRestoreRequest.md index 3df38e294e..b7faf00b00 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Resume-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/exchange/Resume-MailboxRestoreRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/resume-mailboxrestorerequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Resume-MailboxRestoreRequest @@ -17,17 +16,20 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Resume-MailboxRestoreRequest cmdlet to resume a restore request that was suspended or failed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Resume-MailboxRestoreRequest [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Resume-MailboxRestoreRequest [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +50,7 @@ This example resumes any restore request with the status of Failed. ## PARAMETERS ### -Identity -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: \\\\. +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). @@ -68,8 +70,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,12 +125,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Resume-Message.md b/exchange/exchange-ps/exchange/Resume-Message.md similarity index 84% rename from exchange/exchange-ps/exchange/mail-flow/Resume-Message.md rename to exchange/exchange-ps/exchange/Resume-Message.md index 7581f2ecd4..3015c97f9a 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Resume-Message.md +++ b/exchange/exchange-ps/exchange/Resume-Message.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/resume-message +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Resume-Message @@ -17,28 +16,31 @@ This cmdlet is available only in on-premises Exchange. Use the Resume-Message cmdlet to enable delivery of a previously suspended message in a queue on a Mailbox server or Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Filter ``` -Resume-Message -Filter [-Server ] +Resume-Message -Filter + [-Server ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity ``` Resume-Message [-Identity] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION A message being sent to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is resumed in a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To resume a message in more than one queue in a single operation, you must use the Filter parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,52 +52,49 @@ Resume-Message -Server Server1 -Filter "FromAddress -eq 'kweku@contoso.com' -and This example resumes delivery of all messages in a suspended state and for which the following conditions are true: - The messages were sent by the sender kweku@contoso.com. - - The messages are queued on the server Server1. - - The messages will expire before 15:00 on January 5, 2018. ## PARAMETERS -### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.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 ("). +### -Identity +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: String -Parameter Sets: Filter +Type: MessageIdentity +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity). +### -Filter +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 ("). ```yaml -Type: MessageIdentity -Parameter Sets: Identity +Type: String +Parameter Sets: Filter Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,11 +114,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -160,12 +156,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Resume-MoveRequest.md b/exchange/exchange-ps/exchange/Resume-MoveRequest.md similarity index 82% rename from exchange/exchange-ps/exchange/move-and-migration/Resume-MoveRequest.md rename to exchange/exchange-ps/exchange/Resume-MoveRequest.md index 3546062860..81384c86be 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Resume-MoveRequest.md +++ b/exchange/exchange-ps/exchange/Resume-MoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/resume-moverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Resume-MoveRequest @@ -17,17 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Resume-MoveRequest cmdlet to resume a move request that has been suspended or has failed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Resume-MoveRequest [-Identity] [-Confirm] [-DomainController ] [-WhatIf] - [-ProxyToMailbox ] [-SuspendWhenReadyToComplete] [] +Resume-MoveRequest [-Identity] + [-Confirm] + [-DomainController ] + [-ProxyToMailbox ] + [-SuspendWhenReadyToComplete] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,7 +51,7 @@ This example resumes any failed move requests. ### Example 3 ```powershell -Get-MoveRequest -MoveStatus Suspended | Get-MoveRequestStatistics |Where {$_.Message -like "*resume after 10 P.M."} | Resume-MoveRequest +Get-MoveRequest -MoveStatus Suspended | Get-MoveRequestStatistics | Where {$_.Message -like "*resume after 10 P.M."} | Resume-MoveRequest ``` This example resumes any move requests that have the suspend comment "Resume after 10 P.M." @@ -58,17 +62,11 @@ This example resumes any move requests that have the suspend comment "Resume aft The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values: - GUID - - Distinguished name (DN) - - Domain\\Account - - User principal name (UPN) - - LegacyExchangeDN - - SMTP address - - Alias ```yaml @@ -87,15 +85,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -122,45 +119,20 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ProxyToMailbox 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -177,7 +149,9 @@ Accept wildcard characters: False ``` ### -SuspendWhenReadyToComplete -The SuspendWhenReadyToComplete switch specifies whether to suspend the move request before it reaches the status of CompletionInProgress. Instead of this switch, we recommend using the Set-MoveRequest cmdlet with the CompleteAfter parameter. +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. ```yaml Type: SwitchParameter @@ -192,17 +166,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Resume-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/Resume-PublicFolderMigrationRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/move-and-migration/Resume-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/exchange/Resume-PublicFolderMigrationRequest.md index d8898d629d..42768b7cfb 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Resume-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Resume-PublicFolderMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/resume-publicfoldermigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Resume-PublicFolderMigrationRequest @@ -19,7 +18,7 @@ Use the Resume-PublicFolderMigrationRequest cmdlet to resume serial public folde **Note**: Support for serial migration of public folders ended in Exchange 2013 Cumulative Update 8 (CU8), and the cmdlets are no longer available in Exchange Online. Instead, use the corresponding **\*-MigrationBatch** and **\*-PublicFolderMailboxMigration\*** cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,11 +26,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Resume-PublicFolderMigrationRequest [-Identity] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,7 +55,6 @@ This example resumes any failed migration requests. The Identity parameter specifies the migration request that you want to resume. You can use the following values: - Name - - RequestGUID ```yaml @@ -74,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -128,12 +126,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Resume-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/Resume-PublicFolderMoveRequest.md similarity index 87% rename from exchange/exchange-ps/exchange/move-and-migration/Resume-PublicFolderMoveRequest.md rename to exchange/exchange-ps/exchange/Resume-PublicFolderMoveRequest.md index 8b5d1b25a6..af943a8370 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Resume-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/exchange/Resume-PublicFolderMoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/resume-publicfoldermoverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Resume-PublicFolderMoveRequest @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Resume-PublicFolderMoveRequest cmdlet to resume a public folder move request that has been suspended or has failed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Resume-PublicFolderMoveRequest [-Identity] [-Confirm] - [-DomainController ] [-WhatIf] [] +Resume-PublicFolderMoveRequest [-Identity] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,7 +49,7 @@ This example resumes failed public folder move requests. ### Example 3 ```powershell -Get-PublicFolderMoveRequest -MoveStatus Suspended | Get-PublicFolderMoveRequestStatistics |Where {$_.Message -like "*resume after 10 P.M."} | Resume-PublicFolderMoveRequest +Get-PublicFolderMoveRequest -MoveStatus Suspended | Get-PublicFolderMoveRequestStatistics | Where {$_.Message -like "*resume after 10 P.M."} | Resume-PublicFolderMoveRequest ``` This example resumes a move request that has the suspend comment "Resume after 10 P.M." @@ -73,8 +75,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -127,12 +128,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Resume-PublicFolderReplication.md b/exchange/exchange-ps/exchange/Resume-PublicFolderReplication.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Resume-PublicFolderReplication.md rename to exchange/exchange-ps/exchange/Resume-PublicFolderReplication.md index d771627f80..a781b34c89 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Resume-PublicFolderReplication.md +++ b/exchange/exchange-ps/exchange/Resume-PublicFolderReplication.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/resume-publicfolderreplication +online version: https://learn.microsoft.com/powershell/module/exchange/resume-publicfolderreplication applicable: Exchange Server 2010 title: Resume-PublicFolderReplication schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Resume-PublicFolderReplication @@ -17,16 +16,19 @@ This cmdlet is available only in Exchange Server 2010. Use the Resume-PublicFolderReplication cmdlet to resume public folder content replication when it's been stopped. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Resume-PublicFolderReplication [-Confirm] [-DomainController ] [-WhatIf] [] +Resume-PublicFolderReplication [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,8 +44,7 @@ This example resumes content replication for the entire organization. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -96,12 +97,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/mail-flow/Resume-Queue.md b/exchange/exchange-ps/exchange/Resume-Queue.md similarity index 83% rename from exchange/exchange-ps/exchange/mail-flow/Resume-Queue.md rename to exchange/exchange-ps/exchange/Resume-Queue.md index d677cf6e7f..43bb312d87 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Resume-Queue.md +++ b/exchange/exchange-ps/exchange/Resume-Queue.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/resume-queue +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Resume-Queue @@ -17,28 +16,31 @@ This cmdlet is available only in on-premises Exchange. Use the Resume-Queue cmdlet to restart processing for a suspended queue on a Mailbox server or an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Filter ``` -Resume-Queue -Filter [-Server ] +Resume-Queue -Filter + [-Server ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity ``` Resume-Queue [-Identity] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION If you use the Identity parameter, the queue is resumed only if that identity matches a single queue. If the identity matches more than one queue, you receive an error. To resume more than one queue in a single operation, you must use the Filter parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,45 +53,44 @@ This example resumes processing of all queues where the NextHopDomain is Fourthc ## PARAMETERS -### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.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 ("). +### -Identity +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: String -Parameter Sets: Filter +Type: QueueIdentity +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity). +### -Filter +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 ("). ```yaml -Type: QueueIdentity -Parameter Sets: Identity +Type: String +Parameter Sets: Filter Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -109,11 +110,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -154,12 +152,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Retry-Queue.md b/exchange/exchange-ps/exchange/Retry-Queue.md similarity index 85% rename from exchange/exchange-ps/exchange/mail-flow/Retry-Queue.md rename to exchange/exchange-ps/exchange/Retry-Queue.md index 215158def9..c34b537241 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Retry-Queue.md +++ b/exchange/exchange-ps/exchange/Retry-Queue.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/retry-queue +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Retry-Queue @@ -17,16 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Retry-Queue cmdlet to force a connection attempt for a queue on a Mailbox server or an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Filter ``` -Retry-Queue -Filter [-Server ] +Retry-Queue -Filter + [-Server ] [-Confirm] [-Resubmit ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity @@ -34,13 +35,14 @@ Retry-Queue -Filter [-Server ] Retry-Queue [-Identity] [-Confirm] [-Resubmit ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Retry-Queue cmdlet forces a connection attempt for a queue that has a status of Retry. The cmdlet establishes a connection to the next hop if possible. If a connection isn't established, a new retry time is set. To use this command to retry delivery of messages in the Unreachable queue, you must include the Resubmit parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,52 +54,49 @@ Retry-Queue -Filter "NextHopDomain -eq "contoso.com" -and Status -eq 'Retry'" This example forces a connection attempt for all queues that meet the following criteria: - The queues are holding messages for the domain contoso.com. - - The queues have a status of Retry. - - The queues are located on the server on which the command is executed. ## PARAMETERS -### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.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 ("). +### -Identity +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: String -Parameter Sets: Filter +Type: QueueIdentity +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity). +### -Filter +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 ("). ```yaml -Type: QueueIdentity -Parameter Sets: Identity +Type: String +Parameter Sets: Filter Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -133,11 +132,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -178,12 +174,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Rotate-DkimSigningConfig.md b/exchange/exchange-ps/exchange/Rotate-DkimSigningConfig.md similarity index 77% rename from exchange/exchange-ps/exchange/antispam-antimalware/Rotate-DkimSigningConfig.md rename to exchange/exchange-ps/exchange/Rotate-DkimSigningConfig.md index a66bc19b14..d424e6898b 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Rotate-DkimSigningConfig.md +++ b/exchange/exchange-ps/exchange/Rotate-DkimSigningConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/rotate-dkimsigningconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Rotate-DkimSigningConfig @@ -15,22 +14,22 @@ monikerRange: "exchonline-ps || eop-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Rotate-DkimSigningConfig cmdlet to rotate the public and private DomainKeys Identified Mail (DKIM) signing policy keys for domains in a cloud-based organization. This cmdlet creates new DKIM keys and uses the alternate DKIM selector. Typically, you don't need to use this cmdlet, because Microsoft Office 365 automatically rotates your DKIM keys. +Use the Rotate-DkimSigningConfig cmdlet to rotate the public and private DomainKeys Identified Mail (DKIM) signing policy keys for domains in a cloud-based organization. This cmdlet creates new DKIM keys and uses the alternate DKIM selector. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Rotate-DkimSigningConfig [-Identity] [-Confirm] [-KeySize ] [-WhatIf] +Rotate-DkimSigningConfig [-Identity] + [-Confirm] + [-KeySize ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,9 +46,7 @@ This example rotates the DKIM signing policy for the contoso.com domain. 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). - - Distinguished name (DN) - - GUID ```yaml @@ -68,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -86,9 +82,14 @@ Accept wildcard characters: False ``` ### -KeySize -The KeySize parameter specifies the size in bits of the public key that's used in the DKIM signing policy. Valid values are 1024 or 2048. +The KeySize parameter specifies the size in bits of the public key that's used in the DKIM signing policy. Valid values are: -RSA keys are supported; Ed25519 keys aren't supported. +- 1024 +- 2048 + +RSA keys are supported. Ed25519 keys aren't supported. + +**Note**: Upgrading the key size to 2048 only upgrades the selector that isn't currently active. After key rotation has taken place, you need to run the command again to upgrade the key size of the other selector. ```yaml Type: UInt16 @@ -124,12 +125,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Search-AdminAuditLog.md b/exchange/exchange-ps/exchange/Search-AdminAuditLog.md new file mode 100644 index 0000000000..f42ad8e781 --- /dev/null +++ b/exchange/exchange-ps/exchange/Search-AdminAuditLog.md @@ -0,0 +1,335 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Search-AdminAuditLog + +## SYNOPSIS +> [!NOTE] +> This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . + +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Search-AdminAuditLog cmdlet to search the contents of the administrator audit log. Administrator audit logging records when a user or administrator makes a change in your organization (in the Exchange admin center or by using cmdlets). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Search-AdminAuditLog + [-Cmdlets ] + [-DomainController ] + [-EndDate ] + [-ExternalAccess ] + [-IsSuccess ] + [-ObjectIds ] + [-Parameters ] + [-ResultSize ] + [-StartDate ] + [-StartIndex ] + [-UserIds ] + [] +``` + +## DESCRIPTION +If you run the Search-AdminAuditLog cmdlet without any parameters, up to 1,000 log entries are returned by default. + +In Exchange Online PowerShell, if you don't use the StartDate or EndDate parameters, only results from the last 14 days are returned. + +In Exchange Online PowerShell, data is available for the last 90 days. You can enter dates older than 90 days, but only data from the last 90 days will be returned. + +For more information about the structure and properties of the audit log, see [Administrator audit log structure](https://learn.microsoft.com/Exchange/policy-and-compliance/admin-audit-logging/log-structure). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Search-AdminAuditLog -Cmdlets New-RoleGroup,New-ManagementRoleAssignment +``` + +This example finds all the administrator audit log entries that contain either the New-RoleGroup or the New-ManagementRoleAssignment cmdlet. + +### Example 2 +```powershell +Search-AdminAuditLog -Cmdlets Set-Mailbox -Parameters UseDatabaseQuotaDefaults,ProhibitSendReceiveQuota,ProhibitSendQuota -StartDate 01/24/2018 -EndDate 02/12/2018 -IsSuccess $true +``` + +This example finds all the administrator audit log entries that match the following criteria: + +- Cmdlets: Set-Mailbox +- Parameters: UseDatabaseQuotaDefaults, ProhibitSendReceiveQuota, ProhibitSendQuota +- StartDate: 01/24/2018 +- EndDate: 02/12/2018 + +The command completed successfully + +### Example 3 +```powershell +$LogEntries = Search-AdminAuditLog -Cmdlets Write-AdminAuditLog + +$LogEntries | ForEach { $_.CmdletParameters } +``` + +This example displays all the comments written to the administrator audit log by the Write-AdminAuditLog cmdlet. + +First, store the audit log entries in a temporary variable. Then, iterate through all the audit log entries returned and display the Parameters property. + +### Example 4 +```powershell +Search-AdminAuditLog -ExternalAccess $true -StartDate 09/17/2018 -EndDate 10/02/2018 +``` + +This example returns entries in the administrator audit log of an Exchange Online organization for cmdlets run by Microsoft datacenter administrators between September 17, 2018 and October 2, 2018. + +## PARAMETERS + +### -Cmdlets +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**. + +```yaml +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 +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndDate +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". + +In the cloud-based service, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a date/time value for this parameter, use either of the following options: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +In the results of this cmdlet, the date/time when the change was made (the cmdlet was run) is returned in the property named **RunDate**. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalAccess +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. +- $false: Only return audit log entries where the change was made by an internal user. + +```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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsSuccess +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). +- $false: Only return audit log entries where the change was not successful (in other words, the cmdlet did not run successfully and resulted in an error). + +In the results of this cmdlet, this property is named **Succeeded**. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ObjectIds +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 +- Canonical distinguished name (for example, contoso.com/Users/Akia Al-Zuhairi) +- Public folder identity (for example, \\Engineering\\Customer Discussion) + +You'll likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**. + +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"`. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Parameters +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** + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The ResultSize parameter specifies the maximum number of results to return. The default value is 1000. + +The maximum results to return is 250,000. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +In the cloud-based service, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a date/time value for this parameter, use either of the following options: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +In the results of this cmdlet, the date/time when the change was made (the cmdlet was run) is returned in the property named **RunDate**. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartIndex +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIds +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)). + +You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"User1","User2",..."UserN"`. + +In the results of this cmdlet, this property is named **Caller** + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Search-Mailbox.md b/exchange/exchange-ps/exchange/Search-Mailbox.md similarity index 75% rename from exchange/exchange-ps/exchange/mailboxes/Search-Mailbox.md rename to exchange/exchange-ps/exchange/Search-Mailbox.md index bc25ce4820..942951ea8b 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Search-Mailbox.md +++ b/exchange/exchange-ps/exchange/Search-Mailbox.md @@ -1,29 +1,26 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/search-mailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Search-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Search-Mailbox cmdlet to search a mailbox and copy the results to a specified target mailbox, delete messages from the source mailbox, or both. -> [!NOTE] -> By default, Search-Mailbox is available only in the Mailbox Search or Mailbox Import Export roles, and these roles aren't assigned to *any* role groups. To use this cmdlet, you need to add one or both of the roles to a role group (for example, the Organization Management role group). Only the Mailbox Import Export role gives you access to the DeleteContent parameter. For more information about adding roles to role groups, see [Add a role to a role group](https://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +**Note**: In cloud-based environments, the Search-Mailbox cmdlet was deprecated in favor of [New-ComplianceSearch](https://learn.microsoft.com/powershell/module/exchange/new-compliancesearch) and related eDiscovery cmdlets. -> [!NOTE] -> In cloud-based environments, the Search-Mailbox cmdlet is being deprecated in favor of [New-ComplianceSearch](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/new-compliancesearch) and related eDiscovery cmdlets. +By default, Search-Mailbox is available only in the Mailbox Search or Mailbox Import Export roles, and these roles aren't assigned to *any* role groups. To use this cmdlet, you need to add one or both of the roles to a role group (for example, the Organization Management role group). Only the Mailbox Import Export role gives you access to the DeleteContent parameter. For more information about adding roles to role groups, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,12 +36,14 @@ Search-Mailbox [-Identity] [-SearchDumpster] [-SearchDumpsterOnly] [-SearchQuery ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### EstimateResult ``` -Search-Mailbox [-Identity] [-EstimateResultOnly] +Search-Mailbox [-Identity] + [-EstimateResultOnly] [-Confirm] [-DomainController ] [-DoNotIncludeArchive] @@ -53,7 +52,8 @@ Search-Mailbox [-Identity] [-EstimateResultOnly] [-SearchDumpster] [-SearchDumpsterOnly] [-SearchQuery ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Mailbox @@ -70,18 +70,16 @@ Search-Mailbox [-Identity] -TargetFolder [-SearchDumpster] [-SearchDumpsterOnly] [-SearchQuery ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can use the Search-Mailbox cmdlet to search messages in a specified mailbox and perform any of the following tasks: - Copy messages to a specified target mailbox. - - Delete messages from the source mailbox. You have to be assigned the Mailbox Import Export management role to delete messages. - - Perform single item recovery to recover items from a user's Recoverable Items folder. - - Clean up the Recoverable Items folder for a mailbox when it has reached the Recoverable Items hard quota. ## EXAMPLES @@ -116,50 +114,25 @@ This example searches all mailboxes in your organization for messages that conta ## PARAMETERS -### -EstimateResultOnly -The EstimateResultOnly switch specifies that only an estimate of the total number and size of messages returned by the search be provided. Messages aren't copied to the target mailbox. You can't use this switch with the TargetMailbox parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: EstimateResult -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity The Identity parameter specifies the identity of the mailbox to search. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxOrMailUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -168,6 +141,24 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -EstimateResultOnly +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. + +```yaml +Type: SwitchParameter +Parameter Sets: EstimateResult +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -TargetFolder 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. @@ -175,7 +166,7 @@ The TargetFolder parameter specifies a folder name in which search results are s Type: String Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -188,23 +179,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You must use this parameter with the TargetFolder parameter. You can't use this parameter with the EstimateResultOnly switch. @@ -213,7 +195,7 @@ 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -225,15 +207,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -255,7 +236,7 @@ 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -265,8 +246,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -283,7 +262,9 @@ Accept wildcard characters: False ``` ### -DoNotIncludeArchive -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. +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. If auto-expanding archiving is enabled for an Exchange Online mailbox, only the user's primary archive mailbox is searched. Auxiliary archive mailboxes aren't included in the search. @@ -291,7 +272,7 @@ 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -301,13 +282,15 @@ Accept wildcard characters: False ``` ### -Force -The Force switch overrides the confirmation prompt displayed when your use the DeleteContent switch to permanently delete messages. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -317,13 +300,13 @@ Accept wildcard characters: False ``` ### -IncludeUnsearchableItems -The IncludeUnsearchableItems switch specifies whether to include items that couldn't be indexed by Exchange Search. When set to $true, the IncludeUnsearchableItems switch specifies that items that couldn't be indexed by Exchange Search should be included in the search results. +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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -336,9 +319,7 @@ Accept wildcard characters: False The LogLevel parameter specifies the logging level for the search. It can have one of the following values: - Suppress: No logs are kept. - - Basic: Basic information about the query and who ran it is kept. - - Full: In addition to the information kept by the Basic log level, the Full log level adds a complete list of search results. The default log level is Basic. @@ -349,7 +330,7 @@ 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -359,13 +340,15 @@ Accept wildcard characters: False ``` ### -LogOnly -The LogOnly switch specifies that a search be performed and only a log be generated. Messages returned by the search aren't copied to the target mailbox. The logging level is specified by using the LogLevel parameter. +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. ```yaml Type: SwitchParameter Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -375,13 +358,15 @@ Accept wildcard characters: False ``` ### -SearchDumpster -The SearchDumpster parameter specifies whether to search the Recoverable Items folder, which is the storage location in which items deleted from the Deleted Items folder or hard-deleted items are stored until they're purged from the mailbox database. By default, the Recoverable Items folder is always searched. To exclude the folder from the search, set the SearchDumpster switch to $false, for example,-SearchDumpster:$false +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`. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -391,13 +376,17 @@ Accept wildcard characters: False ``` ### -SearchDumpsterOnly -The SearchDumpsterOnly switch specifies that only the Recoverable Items folder of the specified mailbox be searched. You can also use this switch with the DeleteContent switch to delete messages from the Recoverable Items folder and reduce the size of the folder. +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. + +You can also use this switch with the DeleteContent switch to delete messages from the Recoverable Items folder and reduce the size of the folder. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -407,7 +396,7 @@ Accept wildcard characters: False ``` ### -SearchQuery -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://docs.microsoft.com/exchange/security-and-compliance/in-place-ediscovery/message-properties-and-search-operators). +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. @@ -417,7 +406,7 @@ 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -433,7 +422,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -447,12 +436,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-MailboxAuditLog.md b/exchange/exchange-ps/exchange/Search-MailboxAuditLog.md similarity index 88% rename from exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-MailboxAuditLog.md rename to exchange/exchange-ps/exchange/Search-MailboxAuditLog.md index a095d2f6ad..f6ff4a429a 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-MailboxAuditLog.md +++ b/exchange/exchange-ps/exchange/Search-MailboxAuditLog.md @@ -1,29 +1,32 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/search-mailboxauditlog +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Search-MailboxAuditLog ## SYNOPSIS +> [!NOTE] +> This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Search-MailboxAuditLog cmdlet to search mailbox audit log entries matching the specified search terms. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Search-MailboxAuditLog [[-Identity] ] [-ShowDetails] +Search-MailboxAuditLog [[-Identity] ] + [-ShowDetails] [-DomainController ] [-EndDate ] [-ExternalAccess ] @@ -54,9 +57,11 @@ Search-MailboxAuditLog [-Mailboxes ] ``` ## DESCRIPTION -The Search-MailboxAuditLog cmdlet performs a synchronous search of mailbox audit logs for one or more specified mailboxes and displays search results in the Exchange Management Shell window. To search mailbox audit logs for multiple mailboxes and have the results sent by email to specified recipients, use the New-MailboxAuditLogSearch cmdlet instead. To learn more about mailbox audit logging, see [Mailbox audit logging in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/mailbox-audit-logging/mailbox-audit-logging). +The Search-MailboxAuditLog cmdlet performs a synchronous search of mailbox audit logs for one or more specified mailboxes and displays search results in the Exchange Management Shell window. To search mailbox audit logs for multiple mailboxes and have the results sent by email to specified recipients, use the New-MailboxAuditLogSearch cmdlet instead. To learn more about mailbox audit logging, see [Mailbox audit logging in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mailbox-audit-logging/mailbox-audit-logging). + +In multi-geo environments, when you run this cmdlet in a different region from the mailbox that you're trying to search, you might receive the error, "An error occurred while trying to access the audit log." In this scenario, you need to anchor the PowerShell session to a user in the same region as the mailbox as described in [Connect directly to a geo location using Exchange Online PowerShell](https://learn.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo#connect-directly-to-a-geo-location-using-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,10 +81,10 @@ This example retrieves mailbox audit log entries for Ken Kwok and Ben Smith's ma ### Example 3 ```powershell -Search-MailboxAuditLog -Identity kwok -LogonTypes Owner -ShowDetails -StartDate 1/1/2016 -EndDate 3/1/2016 | Where-Object {$_.Operation -eq "HardDelete"} +Search-MailboxAuditLog -Identity kwok -LogonTypes Owner -ShowDetails -StartDate 1/1/2017 -EndDate 3/1/2017 | Where-Object {$_.Operation -eq "HardDelete"} ``` -This example retrieves mailbox audit log entries for Ken Kwok's mailbox for actions performed by the mailbox owner between 1/1/2016 and 3/1/2016. The results are piped to the Where-Object cmdlet and filtered to return only entries with the HardDelete action. +This example retrieves mailbox audit log entries for Ken Kwok's mailbox for actions performed by the mailbox owner between 1/1/2017 and 3/1/2017. The results are piped to the Where-Object cmdlet and filtered to return only entries with the HardDelete action. ## PARAMETERS @@ -87,23 +92,14 @@ This example retrieves mailbox audit log entries for Ken Kwok's mailbox for acti 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -140,7 +136,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". ```yaml Type: ExDateTime @@ -178,7 +174,7 @@ Accept wildcard characters: False ### -GroupMailbox This parameter is available only in the cloud-based service. -The GroupMailbox switch is required to include Office 365 groups in the search. You don't need to specify a value with this switch. +The GroupMailbox switch is required to include Microsoft 365 Groups in the search. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -197,7 +193,6 @@ Accept wildcard characters: False The HasAttachments parameter filters the search by messages that have attachments. Valid values are: - $true: Only messages with attachments are included in the search. - - $false: Messages with and without attachments are included in the search. ```yaml @@ -216,9 +211,7 @@ Accept wildcard characters: False ### -IncludeInactiveMailbox This parameter is available only in the cloud-based service. -The IncludeInactiveMailbox switch is required to include inactive mailboxes in the search. 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. +{{ Fill IncludeInactiveMailbox Description }} ```yaml Type: SwitchParameter @@ -237,11 +230,7 @@ Accept wildcard characters: False The LogonTypes parameter specifies the type of logons. Valid values are: - Admin: Audit log entries for mailbox access by administrator logons are returned. - - Delegate: Audit log entries for mailbox access by delegates are returned, including access by users with Full Mailbox Access permission. - -- External: For Exchange Online mailboxes, audit log entries for mailbox access by Microsoft datacenter administrators are returned. - - Owner: Audit log entries for mailbox access by the primary mailbox owner are returned. This value requires the ShowDetails switch. ```yaml @@ -260,7 +249,7 @@ Accept wildcard characters: False ### -Mailboxes 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: "\","\",..."\". +You enter multiple mailboxes separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. You can't use this parameter with the ShowDetails switch. @@ -281,49 +270,27 @@ Accept wildcard characters: False 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.) - - ApplyRecord (Exchange Online only) - - Copy - - Create - - Default (Exchange Online only) - - FolderBind - - HardDelete - - MailboxLogin - - MailItemsAccessed (Exchange Online only and only for E5 or E5 Compliance add-on subscription users.) - - MessageBind (Although this value is accepted, these actions are no longer logged.) - - ModifyFolderPermissions (Exchange 2019 and Exchange Online only. Although this value is accepted, it's already included in the UpdateFolderPermissions action and isn't audited separately.) - - Move - - MoveToDeletedItems - - RecordDelete (Exchange Online only) - - RemoveFolderPermissions (Exchange 2019 and Exchange Online only. Although this value is accepted, it's already included in the UpdateFolderPermissions action and isn't audited separately.) - - SendAs - - SendOnBehalf - - SoftDelete - - Update - - UpdateCalendarDelegation (Exchange 2019 and Exchange Online only) - - UpdateComplianceTag (Exchange Online only) - - UpdateFolderPermissions (Exchange 2019 and Exchange Online only) - - UpdateInboxRules (Exchange 2019 and Exchange Online only) You can enter multiple values separated by commas. @@ -380,7 +347,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". ```yaml Type: ExDateTime @@ -400,12 +367,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Search-MessageTrackingReport.md b/exchange/exchange-ps/exchange/Search-MessageTrackingReport.md similarity index 90% rename from exchange/exchange-ps/exchange/mail-flow/Search-MessageTrackingReport.md rename to exchange/exchange-ps/exchange/Search-MessageTrackingReport.md index b6b44b461e..b56afd8580 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Search-MessageTrackingReport.md +++ b/exchange/exchange-ps/exchange/Search-MessageTrackingReport.md @@ -1,31 +1,31 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/search-messagetrackingreport +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Search-MessageTrackingReport ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. -Use the Search-MessageTrackingReport cmdlet to find the unique message tracking report based on the search criteria provided. You can then pass this message tracking report ID to the Get-MessageTrackingReport cmdlet to get full message tracking information. For more information, see [Get-MessageTrackingReport](https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-messagetrackingreport). The message tracking report cmdlets are used by the delivery reports feature. +Use the Search-MessageTrackingReport cmdlet to find the unique message tracking report based on the search criteria provided. You can then pass this message tracking report ID to the Get-MessageTrackingReport cmdlet to get full message tracking information. For more information, see [Get-MessageTrackingReport](https://learn.microsoft.com/powershell/module/exchange/get-messagetrackingreport). The message tracking report cmdlets are used by the delivery reports feature. -In Exchange Online, delivery reports has been replaced by message trace (the Get-MessageTrace and Get-MessageTraceDetail cmdlets). +In Exchange Online, delivery reports are replaced by message trace (the Get-MessageTraceV2 and Get-MessageTraceDetailV2 cmdlets). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### SearchAsSender ``` -Search-MessageTrackingReport [-Identity] -Sender [-BypassDelegateChecking] +Search-MessageTrackingReport [-Identity] -Sender + [-BypassDelegateChecking] [-Confirm] [-DomainController ] [-DoNotResolve] @@ -34,12 +34,14 @@ Search-MessageTrackingReport [-Identity] -Sender ] [-Subject ] [-TraceLevel ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### SearchAsRecipient ``` -Search-MessageTrackingReport [-Identity] [-Recipients ] +Search-MessageTrackingReport [-Identity] + [-Recipients ] [-BypassDelegateChecking] [-Confirm] [-DomainController ] @@ -49,11 +51,12 @@ Search-MessageTrackingReport [-Identity] [-Recipients ] [-Subject ] [-TraceLevel ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,23 +82,14 @@ This example returns the message tracking reports that the Help desk can analyze The Identity parameter scopes the search to the specified mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) When you use this parameter without the Sender parameter, the specified mailbox is the message sender that's used in the search. You can specify the recipients by using the Recipients parameter. @@ -154,8 +148,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -293,9 +286,7 @@ Accept wildcard characters: False 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. - - Medium: In addition to all the data returned for the Low setting, the actual message tracking search results are also returned. - - High: Full diagnostic data is returned. You only need to use this parameter for troubleshooting message tracking issues. @@ -304,7 +295,7 @@ You only need to use this parameter for troubleshooting message tracking issues. Type: TraceLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -334,12 +325,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md b/exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md new file mode 100644 index 0000000000..9043d4d2b9 --- /dev/null +++ b/exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md @@ -0,0 +1,395 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Search-UnifiedAuditLog + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Search-UnifiedAuditLog cmdlet to search the unified audit log. This log contains events from Exchange Online, SharePoint, OneDrive, Microsoft Entra ID, Microsoft Teams, Power BI, and other Microsoft 365 services. You can search for all events in a specified date range, or you can filter the results based on specific criteria, such as the user who performed the action, the action, or the target object. + +**Note**: By default, this cmdlet returns a subset of results containing up to 100 records. Use SessionCommand parameter with the ReturnLargeSet value to exhaustively search up to 50,000 results. The SessionCommand parameter causes the cmdlet to return unsorted data. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Search-UnifiedAuditLog -EndDate -StartDate + [-Formatted] + [-FreeText ] + [-HighCompleteness] + [-IPAddresses ] + [-LongerRetentionEnabled ] + [-ObjectIds ] + [-Operations ] + [-RecordType ] + [-ResultSize ] + [-SessionCommand ] + [-SessionId ] + [-SiteIds ] + [-UserIds ] + [] +``` + +## DESCRIPTION +The Search-UnifiedAuditLog cmdlet presents pages of data based on repeated iterations of the same command. Use SessionId and SessionCommand to repeatedly run the cmdlet until you get zero returns, or hit the maximum number of results based on the session command. To gauge progress, look at the ResultIndex (hits in the current iteration) and ResultCount (hits for all iterations) properties of the data returned by the cmdlet. + +The Search-UnifiedAuditLog cmdlet is available in Exchange Online PowerShell. You can also view events from the unified auditing log by using the Microsoft Purview compliance portal. For more information, see [Audited activities](https://learn.microsoft.com/purview/audit-log-activities). + +If you want to programmatically download data from the Microsoft 365 audit log, we recommend that you use the Microsoft 365 Management Activity API instead of using the Search-UnifiedAuditLog cmdlet in a PowerShell script. The Microsoft 365 Management Activity API is a REST web service that you can use to develop operations, security, and compliance monitoring solutions for your organization. For more information, see [Management Activity API reference](https://learn.microsoft.com/office/office-365-management-api/office-365-management-activity-api-reference). + +This cmdlet is available in Office 365 operated by 21Vianet, but it won't return any results. + +The OutVariable parameter accepts objects of type ArrayList. Here's an example of how to use it: + +`$start = (Get-Date).AddDays(-1); $end = (Get-Date).AddDays(-0.5); $auditData = New-Object System.Collections.ArrayList; Search-UnifiedAuditLog -StartDate $start -EndDate $end -OutVariable +auditData | Out-Null` + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Search-UnifiedAuditLog -StartDate 5/1/2023 -EndDate 5/2/2023 -SessionCommand ReturnLargeSet +``` + +This example searches the unified audit log for all events from May 1, 2023 12:00AM to May 2, 2023 12:00AM. + +**Note**: If you don't include a timestamp in the value for the StartDate or EndDate parameters, the default timestamp 12:00 AM (midnight) is used. + +### Example 2 +```powershell +Search-UnifiedAuditLog -StartDate "6/1/2023 8:00 AM" -EndDate "6/1/2023 6:00 PM" -RecordType ExchangeAdmin -SessionCommand ReturnLargeSet +``` + +This example searches the unified audit log for all Exchange admin events from 8:00 AM to 6:00 PM on June 1, 2023. + +**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results will be returned because the date and time for the start and end dates will be the same. + +### Example 3 +```powershell +Search-UnifiedAuditLog -StartDate 5/1/2023 -EndDate 5/8/2023 -SessionId "UnifiedAuditLogSearch 05/08/17" -SessionCommand ReturnLargeSet +``` + +This example searches the unified audit log for all events from May 1, 2023 to May 8, 2023. If you don't include a time stamp in the StartDate or EndDate parameters, The data is returned in pages as the command is rerun sequentially while using the same SessionId value. + +**Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. Otherwise, the output is limited to 10,000 results. + +### Example 4 +```powershell +Search-UnifiedAuditLog -StartDate 5/1/2023 -EndDate 5/8/2023 -RecordType SharePointFileOperation -Operations FileAccessed -SessionId "WordDocs_SharepointViews" -SessionCommand ReturnLargeSet +``` + +This example searches the unified audit log for any files accessed in SharePoint from May 1, 2023 to May 8, 2023. The data is returned in pages as the command is rerun sequentially while using the same SessionId value. + +### Example 5 +```powershell +Search-UnifiedAuditLog -StartDate 5/1/2023 -EndDate 5/8/2023 -ObjectIDs "https://alpinehouse.sharepoint.com/sites/contoso/Departments/SM/International/Shared%20Documents/Sales%20Invoice%20-%20International.docx" -SessionCommand ReturnLargeSet +``` + +This example searches the unified audit log from May 1, 2023 to May 8, 2023 for all events relating to a specific Word document identified by its ObjectIDs value. + +## PARAMETERS + +### -EndDate +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: + +- Specify the date/time value in UTC: For example, `"2018-05-06 14:30:00z"`. +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2018 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +If you don't include a timestamp in the value for this parameter, the default timestamp is 12:00 AM (midnight) on the specified date. + +```yaml +Type: ExDateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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: + +- Specify the date/time value in UTC: For example, `"2018-05-06 14:30:00z"`. +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2018 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +If you don't include a timestamp in the value for this parameter, the default timestamp is 12:00 AM (midnight) on the specified date. + +```yaml +Type: ExDateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Formatted +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FreeText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighCompleteness +**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. + +When you use this switch, the query returns more complete search results but might take significantly longer to run. If you don't use this switch, the query runs faster but might have missing search results. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPAddresses +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LongerRetentionEnabled +{{ Fill LongerRetentionEnabled Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ObjectIds +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/*"`). + +For Microsoft Entra operations, the object ID is the account name or GUID value of the account. + +The ObjectId value appears in the AuditData (also known as Details) property of the event. + +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Operations +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SessionCommand +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. +- ReturnNextPreviewPage: This value causes the cmdlet to return data sorted on date. The maximum number of records returned through use of either paging or the ResultSize parameter is 5,000 records. + +**Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. Otherwise, the output is limited to 10,000 results. + +```yaml +Type: UnifiedAuditSessionCommand +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SessionId +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. + +For a given session ID, if you use the SessionCommand value ReturnLargeSet, and then you use the SessionCommand value ReturnNextPreviewPage, the results are limited to 10,000 records. To have all 50,000 records available, always use the ReturnLargeSet value each time your run the cmdlet for the same session ID. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteIds +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`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIds +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access/Send-TextMessagingVerificationCode.md b/exchange/exchange-ps/exchange/Send-TextMessagingVerificationCode.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access/Send-TextMessagingVerificationCode.md rename to exchange/exchange-ps/exchange/Send-TextMessagingVerificationCode.md index dec8394590..dd6524d3fd 100644 --- a/exchange/exchange-ps/exchange/client-access/Send-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/exchange/Send-TextMessagingVerificationCode.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/send-textmessagingverificationcode +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Send-TextMessagingVerificationCode @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Send-TextMessagingVerificationCode cmdlet to send a text messaging verification as part of configuring text message notifications on the mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Send-TextMessagingVerificationCode [[-Identity] ] [-Confirm] [-DomainController ] - [-WhatIf] [] +Send-TextMessagingVerificationCode [[-Identity] ] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION The Send-TextMessagingVerificationCode cmdlet generates a verification code and sends it to a user's mobile phone. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). This cmdlet returns an error if the user requests a verification code more than three times within a 24-hour period. @@ -58,11 +60,37 @@ This example sends the text messaging verification code to Tony Smith's mobile p ## PARAMETERS +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -96,42 +124,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -153,12 +145,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Set-ADServerSettings.md b/exchange/exchange-ps/exchange/Set-ADServerSettings.md similarity index 89% rename from exchange/exchange-ps/exchange/active-directory/Set-ADServerSettings.md rename to exchange/exchange-ps/exchange/Set-ADServerSettings.md index c28bd52acd..fbc8c31fba 100644 --- a/exchange/exchange-ps/exchange/active-directory/Set-ADServerSettings.md +++ b/exchange/exchange-ps/exchange/Set-ADServerSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/set-adserversettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AdServerSettings @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-AdServerSettings cmdlet to manage the Active Directory Domain Services (AD DS) environment in the current Exchange Management Shell session. The Set-AdServerSettings cmdlet replaces the AdminSessionADSettings session variable that was used in Exchange Server 2007. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,25 +24,34 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Set-AdServerSettings -RunspaceServerSettings [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### FullParams ``` -Set-AdServerSettings [-ConfigurationDomainController ] [-PreferredGlobalCatalog ] [-RecipientViewRoot ] [-SetPreferredDomainControllers ] [-ViewEntireForest ] +Set-AdServerSettings [-ConfigurationDomainController ] + [-PreferredGlobalCatalog ] + [-RecipientViewRoot ] + [-SetPreferredDomainControllers ] + [-ViewEntireForest ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ### SingleDC ``` -Set-AdServerSettings [[-PreferredServer] ] [-RecipientViewRoot ] [-ViewEntireForest ] +Set-AdServerSettings [[-PreferredServer] ] + [-RecipientViewRoot ] + [-ViewEntireForest ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -114,8 +122,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -148,7 +155,7 @@ Accept wildcard characters: False ``` ### -RecipientViewRoot -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 \/\. +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 @@ -218,12 +225,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Set-ADSite.md b/exchange/exchange-ps/exchange/Set-ADSite.md similarity index 89% rename from exchange/exchange-ps/exchange/active-directory/Set-ADSite.md rename to exchange/exchange-ps/exchange/Set-ADSite.md index c45b908278..b2769997e3 100644 --- a/exchange/exchange-ps/exchange/active-directory/Set-ADSite.md +++ b/exchange/exchange-ps/exchange/Set-ADSite.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/set-adsite +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AdSite @@ -17,18 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Set-AdSite cmdlet to configure the Exchange settings of Active Directory sites. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-AdSite [-Identity] [-Confirm] [-DomainController ] - [-HubSiteEnabled ] [-PartnerId ] - [-WhatIf] [-InboundMailEnabled ] [] +Set-AdSite [-Identity] + [-Confirm] + [-DomainController ] + [-HubSiteEnabled ] + [-InboundMailEnabled ] + [-PartnerId ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -109,14 +112,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -PartnerId -This parameter is reserved for internal Microsoft use. +### -InboundMailEnabled +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. ```yaml -Type: Int32 +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -125,13 +130,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -PartnerId +This parameter is reserved for internal Microsoft use. ```yaml -Type: SwitchParameter +Type: Int32 Parameter Sets: (All) -Aliases: wi +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -141,16 +146,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -InboundMailEnabled -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. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: Boolean +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -164,12 +167,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/exchange/Set-ATPBuiltInProtectionRule.md new file mode 100644 index 0000000000..cb0c15498e --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ATPBuiltInProtectionRule.md @@ -0,0 +1,219 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ATPBuiltInProtectionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ATPBuiltInProtectionRule cmdlet to modify the rule for the Built-in protection preset security policy that effectively provides default policies for Safe Links and Safe Attachments in Microsoft Defender for Office 365. The rule specifies exceptions to the policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ATPBuiltInProtectionRule [-Identity] + [-Comments ] + [-Confirm] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +> [!IMPORTANT] +> Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ATPBuiltInProtectionRule -Identity "ATP Built-In Protection Rule" -ExceptIfSentToMemberOf "Test Group1","Test Group2" +``` + +This example provides exceptions to the Built-in protection preset security policy for members of the specified groups. + +### Example 2 +```powershell +Set-ATPBuiltInProtectionRule -Identity "ATP Built-In Protection Rule" -ExceptIfRecipientDomainIs (Get-AcceptedDomain).Name +``` + +This example provides exceptions to the Built-in protection preset security policy for recipients in all accepted domains. To see all of your accepted domains, run the following command: `Get-AcceptedDomain | Format-List Name,DomainName`. + +### Example 3 +```powershell +Set-ATPBuiltInProtectionRule -Identity "ATP Built-In Protection Rule" -ExceptIfRecipientDomainIs $null -ExceptIfSentTo $null -ExceptIfSentToMemberOf $null +``` + +This example remove all exceptions from the Built-in protection preset security policy. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to modify. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +The name of the only rule is ATP Built-In Protection Rule. + +```yaml +Type: DehydrateableRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +Dynamic distribution groups are not supported. + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Set-ATPProtectionPolicyRule.md new file mode 100644 index 0000000000..a2820af421 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ATPProtectionPolicyRule.md @@ -0,0 +1,321 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ATPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ATPProtectionPolicyRule cmdlet to modify rules that are associated with Microsoft Defender for Office 365 protections in preset security policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ATPProtectionPolicyRule [-Identity] + [-Comments ] + [-Confirm] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Name ] + [-Priority ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy" -ExceptIfSentToMemberOf "Test Group1","Test Group2" +``` + +This example provides exceptions to Defender for Office 365 protections in the Standard preset security policy for members of the specified groups. + +### Example 2 +```powershell +Set-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy" -SentTo $null -ExceptIfSentTo $null -SentToMemberOf $null -ExceptIfSentToMemberOf $null -RecipientDomainIs $null -ExceptIfRecipientDomainIs $null +``` + +This example removes all conditions and exceptions from the Standard preset security policy. No restrictions are placed on who the Defender for Office 365 protections apply to. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to modify. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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. + +You must use the default value for the rule. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-AcceptedDomain.md b/exchange/exchange-ps/exchange/Set-AcceptedDomain.md new file mode 100644 index 0000000000..d8069d6995 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AcceptedDomain.md @@ -0,0 +1,384 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AcceptedDomain + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-AcceptedDomain cmdlet to modify existing accepted domains in your organization. An accepted domain is any SMTP namespace for which an Exchange organization sends and receives email. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AcceptedDomain [-Identity] + [-AddressBookEnabled ] + [-CanHaveCloudCache ] + [-Confirm] + [-DomainController ] + [-DomainType ] + [-EnableNego2Authentication ] + [-MakeDefault ] + [-MatchSubDomains ] + [-Name ] + [-OutboundOnly ] + [-PendingCompletion ] + [-PendingRemoval ] + [-SendingFromDomainDisabled ] + [-SendingToDomainDisabled ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AcceptedDomain -Identity Contoso -MakeDefault $true +``` + +This example makes the accepted domain Contoso the default accepted domain. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AddressBookEnabled +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: + +- $true for authoritative domains. +- $false for internal relay domains. +- $false for external relay domains. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CanHaveCloudCache +This parameter is available only in the cloud-based service. + +{{ Fill CanHaveCloudCache Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainType +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. +- InternalRelay: This is a type of non-authoritative domain. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's under your control. The external email system is responsible for generating NDRs for unresolved recipients. Use this value to treat messages that are sent to the domain as internal messages. +- ExternalRelay: This is a type of non-authoritative domain that's available only in on-premises Exchange organizations. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's completely outside of your control. The external email system is responsible for generating NDRs for unresolved recipients. + +**Note**: For the value InternalRelay or ExternalRelay, you typically use mail users or mail contacts to relay the messages to the external email system. Address rewriting is also available on Edge Transport servers in on-premises Exchange organizations. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableNego2Authentication +This parameter is available only in the cloud-based service. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeDefault +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. + +- $true: The accepted domain is the default domain. This is the default value for first accepted domain that's created in the organization. +- $false: The accepted domain isn't the default domain. This the default value for subsequent accepted domains. + +The default accepted domain is used in sender email addresses when the senders have only non-SMTP email addresses (for example, X.400 addresses). Non-SMTP email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. IMCEA encapsulation uses the default domain value in the SMTP email address. + +If you don't use non-SMTP email addresses in your organization, you don't need to worry about the value of this 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MatchSubDomains +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 ("). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutboundOnly +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. + +The authoritative accepted domain for the on-premises deployment is configured as an internal relay accepted domain on the cloud side. If the on-premises deployment is using Exchange Online Protection, you need to set this parameter to $true for the accepted domain that represents your on-premises deployment. This parameter is used only if the DomainType parameter is set to Authoritative or InternalRelay. The default value is $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PendingCompletion +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PendingRemoval +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendingFromDomainDisabled +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: + +- $true: Email can't be sent from addresses in the domain. +- $false: Email can be sent from addresses in the domain. + +A common scenario is addresses in a legacy domain that still need to receive email, but shouldn't be used to send email. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendingToDomainDisabled +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: + +- $true: Email sent to recipients in the domain is blocked. +- $false: Email sent to recipients in the domain isn't blocked. + +A common scenario is to prevent email delivery to recipients in your unused Micorost Online Email Routing Address (MOERA) domain (for example, contoso.onmicrosoft.com). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-AccessToCustomerDataRequest.md b/exchange/exchange-ps/exchange/Set-AccessToCustomerDataRequest.md new file mode 100644 index 0000000000..a8ff53f2c3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AccessToCustomerDataRequest.md @@ -0,0 +1,128 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AccessToCustomerDataRequest + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-AccessToCustomerDataRequest cmdlet to approve, deny, or cancel Microsoft 365 customer lockbox requests that control access to your data by Microsoft support engineers. + +**Note**: Customer Lockbox is included in Microsoft 365 E5, or you can buy a separate Customer Lockbox subscription with any Microsoft 365 Enterprise plan. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AccessToCustomerDataRequest -ApprovalDecision -RequestId + [-Comment ] + [-ServiceName ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AccessToCustomerDataRequest -ApprovalDecision Approve -RequestId EXSR123456 -Comment "Troubleshoot issues in Rick Hofer mailbox" +``` + +This example approves the customer lockbox request EXSR123456 with a comment. + +## PARAMETERS + +### -ApprovalDecision +The ApprovalDecision parameter specifies the approval decision for the customer lockbox request. Valid values are: + +- Approve +- Deny +- Cancel + +```yaml +Type: AccessToCustomerDataApproverDecision +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequestId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceName +The ServiceName parameter specifies the related service. Valid values are: + +- EOP +- Exchange +- SharePoint +- Teams + +```yaml +Type: Microsoft.Exchange.Management.AccessToCustomerDataApproval.AccessToCustomerDataRequestServiceName +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAccessRule.md similarity index 90% rename from exchange/exchange-ps/exchange/devices/Set-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAccessRule.md index 12c4b301d5..3649c7062d 100644 --- a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAccessRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-activesyncdeviceaccessrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-ActiveSyncDeviceAccessRule @@ -17,20 +16,23 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ActiveSyncDeviceAccessRule cmdlet to set the level of access for the rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-ActiveSyncDeviceAccessRule [-Identity] - [-AccessLevel ] [-Confirm] [-DomainController ] [-WhatIf] + [-AccessLevel ] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION Your rule can define multiple groups of devices: allowed devices, blocked devices and quarantined devices. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -85,8 +87,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -141,12 +142,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAutoblockThreshold.md similarity index 91% rename from exchange/exchange-ps/exchange/devices/Set-ActiveSyncDeviceAutoblockThreshold.md rename to exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAutoblockThreshold.md index a0255f8200..ba3b345abe 100644 --- a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncDeviceAutoblockThreshold.md +++ b/exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAutoblockThreshold.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-activesyncdeviceautoblockthreshold +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ActiveSyncDeviceAutoblockThreshold @@ -17,21 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ActiveSyncDeviceAutoblockThreshold cmdlet to change settings for autoblocking mobile devices. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-ActiveSyncDeviceAutoblockThreshold [-Identity] - [-AdminEmailInsert ] [-BehaviorTypeIncidenceDuration ] - [-BehaviorTypeIncidenceLimit ] [-Confirm] [-DeviceBlockDuration ] - [-DomainController ] [-WhatIf] [] + [-AdminEmailInsert ] + [-BehaviorTypeIncidenceDuration ] + [-BehaviorTypeIncidenceLimit ] + [-Confirm] + [-DeviceBlockDuration ] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION Microsoft Exchange and Microsoft Exchange ActiveSync can block Exchange ActiveSync mobile devices if these devices display any of a defined list of behaviors that can potentially cause issues with the server. The Set-ActiveSyncDeviceAutoblockThreshold cmdlet can modify an existing autoblock threshold rule and change a variety of settings including the duration of blocking. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -118,8 +122,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -188,12 +191,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/exchange/Set-ActiveSyncMailboxPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/devices/Set-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/exchange/Set-ActiveSyncMailboxPolicy.md index 0fbad4f858..6a74c4ad63 100644 --- a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Set-ActiveSyncMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-activesyncmailboxpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-ActiveSyncMailboxPolicy @@ -17,45 +16,72 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ActiveSyncMailboxPolicy cmdlet to apply a variety of Mobile Device mailbox policy settings to a server. You can set any of the parameters by using one command. -Note: In Exchange 2013 or later, use the Set-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use Set-ActiveSyncMailboxPolicy, update them to use Set-MobileDeviceMailboxPolicy. +**Note**: In Exchange 2013 or later, use the Set-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use Set-ActiveSyncMailboxPolicy, update them to use Set-MobileDeviceMailboxPolicy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-ActiveSyncMailboxPolicy [-Identity] - [-AllowBluetooth ] [-AllowBrowser ] - [-AllowCamera ] [-AllowConsumerEmail ] [-AllowDesktopSync ] - [-AllowExternalDeviceManagement ] [-AllowHTMLEmail ] - [-AllowInternetSharing ] [-AllowIrDA ] - [-AllowMobileOTAUpdate ] [-AllowNonProvisionableDevices ] - [-AllowPOPIMAPEmail ] [-AllowRemoteDesktop ] + [-AllowApplePushNotifications ] + [-AllowBluetooth ] + [-AllowBrowser ] + [-AllowCamera ] + [-AllowConsumerEmail ] + [-AllowDesktopSync ] + [-AllowExternalDeviceManagement ] + [-AllowHTMLEmail ] + [-AllowInternetSharing ] + [-AllowIrDA ] + [-AllowMobileOTAUpdate ] + [-AllowNonProvisionableDevices ] + [-AllowPOPIMAPEmail ] + [-AllowRemoteDesktop ] [-AllowSimpleDevicePassword ] [-AllowSMIMEEncryptionAlgorithmNegotiation ] - [-AllowSMIMESoftCerts ] [-AllowStorageCard ] - [-AllowTextMessaging ] [-AllowUnsignedApplications ] - [-AllowUnsignedInstallationPackages ] [-AllowWiFi ] + [-AllowSMIMESoftCerts ] + [-AllowStorageCard ] + [-AllowTextMessaging ] + [-AllowUnsignedApplications ] + [-AllowUnsignedInstallationPackages ] + [-AllowWiFi ] [-AlphanumericDevicePasswordRequired ] - [-ApprovedApplicationList ] [-AttachmentsEnabled ] [-Confirm] - [-DeviceEncryptionEnabled ] [-DevicePasswordEnabled ] - [-DevicePasswordExpiration ] [-DevicePasswordHistory ] - [-DevicePolicyRefreshInterval ] [-DomainController ] [-IrmEnabled ] - [-IsDefaultPolicy ] [-MaxAttachmentSize ] + [-ApprovedApplicationList ] + [-AttachmentsEnabled ] + [-Confirm] + [-DeviceEncryptionEnabled ] + [-DevicePasswordEnabled ] + [-DevicePasswordExpiration ] + [-DevicePasswordHistory ] + [-DevicePolicyRefreshInterval ] + [-DomainController ] + [-IrmEnabled ] + [-IsDefault ] + [-IsDefaultPolicy ] + [-MaxAttachmentSize ] [-MaxCalendarAgeFilter ] [-MaxDevicePasswordFailedAttempts ] [-MaxEmailAgeFilter ] - [-MaxEmailBodyTruncationSize ] [-MaxEmailHTMLBodyTruncationSize ] - [-MaxInactivityTimeDeviceLock ] [-MinDevicePasswordComplexCharacters ] + [-MaxEmailBodyTruncationSize ] + [-MaxEmailHTMLBodyTruncationSize ] + [-MaxInactivityTimeDeviceLock ] + [-MinDevicePasswordComplexCharacters ] [-MinDevicePasswordLength ] - [-Name ] [-PasswordRecoveryEnabled ] [-RequireDeviceEncryption ] + [-Name ] + [-PasswordRecoveryEnabled ] + [-RequireDeviceEncryption ] [-RequireEncryptedSMIMEMessages ] [-RequireEncryptionSMIMEAlgorithm ] - [-RequireManualSyncWhenRoaming ] [-RequireSignedSMIMEAlgorithm ] - [-RequireSignedSMIMEMessages ] [-RequireStorageCardEncryption ] - [-UnapprovedInROMApplicationList ] [-UNCAccessEnabled ] [-WhatIf] - [-WSSAccessEnabled ] [-AllowApplePushNotifications ] - [-IsDefault ] [] + [-RequireManualSyncWhenRoaming ] + [-RequireSignedSMIMEAlgorithm ] + [-RequireSignedSMIMEMessages ] + [-RequireStorageCardEncryption ] + [-UnapprovedInROMApplicationList ] + [-UNCAccessEnabled ] + [-WhatIf] + [-WSSAccessEnabled ] + [] ``` ## DESCRIPTION @@ -63,7 +89,7 @@ With the Set-ActiveSyncMailboxPolicy cmdlet, you can set each parameter in a mai Some Microsoft Mobile Device mailbox policy settings require the mobile device to have specific built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This applies to devices that can't enforce all policy settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -106,6 +132,24 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -AllowApplePushNotifications +This parameter is available only in the cloud-based service. + +The AllowApplePushNotifications parameter specifies whether push notifications are allowed to Apple mobile devices. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -AllowBluetooth 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. @@ -493,8 +537,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -624,6 +667,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IsDefault +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IsDefaultPolicy 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. @@ -660,15 +719,10 @@ Accept wildcard characters: False 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 - - OneDay - - ThreeDays - - OneWeek - - TwoWeeks - - OneMonth ```yaml @@ -704,15 +758,10 @@ Accept wildcard characters: False 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 - - OneDay - - ThreeDays - - OneWeek - - TwoWeeks - - OneMonth ```yaml @@ -1016,51 +1065,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AllowApplePushNotifications -This parameter is available only in the cloud-based service. - -The AllowApplePushNotifications parameter specifies whether push notifications are allowed to Apple mobile devices. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefault -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/exchange/Set-ActiveSyncOrganizationSettings.md similarity index 81% rename from exchange/exchange-ps/exchange/devices/Set-ActiveSyncOrganizationSettings.md rename to exchange/exchange-ps/exchange/Set-ActiveSyncOrganizationSettings.md index d1e20b3c54..78b5bcd932 100644 --- a/exchange/exchange-ps/exchange/devices/Set-ActiveSyncOrganizationSettings.md +++ b/exchange/exchange-ps/exchange/Set-ActiveSyncOrganizationSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-activesyncorganizationsettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-ActiveSyncOrganizationSettings @@ -17,16 +16,28 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ActiveSyncOrganizationSettings cmdlet to set the Exchange ActiveSync settings for the organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ActiveSyncOrganizationSettings [[-Identity] ] [-AdminMailRecipients ] [-AllowAccessForUnSupportedPlatform ] [-AllowRMSSupportForUnenlightenedApps ] [-Confirm] [-DefaultAccessLevel ] [-DomainController ] [-OtaNotificationMailInsert ] [-UserMailInsert ] [-WhatIf] [] +Set-ActiveSyncOrganizationSettings [[-Identity] ] + [-AdminMailRecipients ] + [-AllowAccessForUnSupportedPlatform ] + [-AllowRMSSupportForUnenlightenedApps ] + [-Confirm] + [-DefaultAccessLevel ] + [-DomainController ] + [-EnableMobileMailboxPolicyWhenCAInplace ] + [-OtaNotificationMailInsert ] + [-TenantAdminPreference ] + [-UserMailInsert ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -39,12 +50,28 @@ This example sets the default access level to quarantine and sets two administra ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -AdminMailRecipients 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -76,10 +103,11 @@ Accept wildcard characters: False ``` ### -AllowRMSSupportForUnenlightenedApps +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: - $true - - $false (This is the default value) ```yaml @@ -98,8 +126,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -119,9 +146,7 @@ Accept wildcard characters: False The DefaultAccessLevel parameter specifies the access level for new and existing device partnerships. Valid values are: - Allow (This is the default value) - - Block - - Quarantine If you change this value from Allow to Block or Quarantine, all existing connected devices are immediately affected, unless the devices are subject to device access rules or individual allow or block list entries. @@ -157,19 +182,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the ActiveSync organization settings object that you want to modify. The default name of this object is Mobile Mailbox Settings. +### -EnableMobileMailboxPolicyWhenCAInplace +This parameter is available only in the cloud-based service. + +{{ Fill EnableMobileMailboxPolicyWhenCAInplace Description }} ```yaml -Type: ActiveSyncOrganizationSettingsIdParameter +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -191,6 +218,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -TenantAdminPreference +This parameter is available only in the cloud-based service. + +{{ Fill TenantAdminPreference Description }} + +```yaml +Type: TenantAdminPreference +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -UserMailInsert 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. @@ -230,12 +275,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-ActiveSyncVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/client-access-servers/Set-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/exchange/Set-ActiveSyncVirtualDirectory.md index e22a4da47b..e46e295975 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Set-ActiveSyncVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-activesyncvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ActiveSyncVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ActiveSyncVirtualDirectory cmdlet to modify existing Microsoft Exchange ActiveSync virtual directories that are used in Internet Information Services (IIS) on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -55,27 +54,27 @@ Set-ActiveSyncVirtualDirectory [-Identity] ## DESCRIPTION The Set-ActiveSyncVirtualDirectory cmdlet configures a variety of settings on the virtual directory used for Exchange ActiveSync including security, authentication, and internal and external URL settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-ActiveSyncVirtualDirectory -Identity "contoso\Microsoft-Server-ActiveSync" -BasicAuthEnabled $false +Set-ActiveSyncVirtualDirectory -Identity "contoso\Microsoft-Server-ActiveSync (Default Web Site)" -BasicAuthEnabled $false ``` This example disables Basic authentication on the default Exchange ActiveSync virtual directory on the server Contoso. ### Example 2 ```powershell -Set-ActiveSyncVirtualDirectory -Identity "contoso\Microsoft-Server-ActiveSync" -BadItemReportingEnabled $true -SendWatsonReport:$true +Set-ActiveSyncVirtualDirectory -Identity "contoso\Microsoft-Server-ActiveSync (Default Web Site)" -BadItemReportingEnabled $true -SendWatsonReport:$true ``` This example enables bad item reporting and turns on the option to send Watson reports for errors on the server Contoso. ### Example 3 ```powershell -Set-ActiveSyncVirtualDirectory -Identity "contoso\Microsoft-Server-ActiveSync" -ExternalUrl "https://contoso.com/mail" +Set-ActiveSyncVirtualDirectory -Identity "contoso\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalUrl "https://contoso.com/mail" ``` This example configures the external URL on the default Exchange ActiveSync virtual directory on the server Contoso. @@ -85,13 +84,11 @@ This example configures the external URL on the default Exchange ActiveSync virt ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -142,7 +139,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. ```yaml @@ -193,8 +189,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -230,13 +225,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -256,8 +247,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -276,14 +266,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -302,33 +288,19 @@ Accept wildcard characters: False 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 - - Basic - - Certificate - - Digest - - Fba - - Kerberos - - LiveIdBasic - - LiveIdFba - - LiveIdNegotiate - - NegoEx - - Negotiate - - Ntlm - - OAuth - - WindowsIntegrated - - WSSecurity You can specify multiple values separated by commas. @@ -336,7 +308,6 @@ You can specify multiple values separated by commas. Although you can specify any of these values, whether or not the authentication method actually works for external connections depends on other factors. For example: - Is the authentication method available on the virtual directory? - - Is the authentication method available, but disabled on the virtual directory? ```yaml @@ -597,12 +568,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Set-AdSiteLink.md b/exchange/exchange-ps/exchange/Set-AdSiteLink.md similarity index 91% rename from exchange/exchange-ps/exchange/active-directory/Set-AdSiteLink.md rename to exchange/exchange-ps/exchange/Set-AdSiteLink.md index 1d3b950b04..0bdcffba25 100644 --- a/exchange/exchange-ps/exchange/active-directory/Set-AdSiteLink.md +++ b/exchange/exchange-ps/exchange/Set-AdSiteLink.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/set-adsitelink +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AdSiteLink @@ -17,19 +16,25 @@ This cmdlet is available only in on-premises Exchange. Use the Set-AdSiteLink cmdlet to assign an Exchange-specific cost to an Active Directory IP site link. You can also use this cmdlet to configure the maximum message size that can pass across an Active Directory IP site link. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-AdSiteLink [-Identity] [-Confirm] [-DomainController ] - [-ExchangeCost ] [-MaxMessageSize ] [-Name ] [-WhatIf] [] +Set-AdSiteLink [-Identity] + [-Confirm] + [-DomainController ] + [-ExchangeCost ] + [-MaxMessageSize ] + [-Name ] + [-WhatIf] + [] ``` ## DESCRIPTION By default, Microsoft Exchange determines the least cost routing path by using the cost assigned to the Active Directory IP site link. You can use the Set-AdSiteLink cmdlet to assign an Exchange-specific cost to the Active Directory IP site link. The Exchange-specific cost is a separate attribute used instead of the Active Directory-assigned cost to determine the least cost routing path. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +66,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -118,13 +122,9 @@ The MaxMessageSize parameter specifies the maximum size of a message that can pa When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -181,12 +181,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-AdaptiveScope.md b/exchange/exchange-ps/exchange/Set-AdaptiveScope.md new file mode 100644 index 0000000000..6560f5f4ab --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AdaptiveScope.md @@ -0,0 +1,173 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AdaptiveScope + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-AdaptiveScope cmdlet to modify adaptive scopes in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Set-AdaptiveScope [-Identity] -FilterConditions + [-AdministrativeUnit ] + [-Comment ] + [] +``` + +### AdaptiveScopeRawQuery +``` +Set-AdaptiveScope [-Identity] -RawQuery + [-AdministrativeUnit ] + [-Comment ] + [] +``` + +### AdministrativeUnit +``` +Set-AdaptiveScope [-Identity] -AdministrativeUnit + [-Comment ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AdaptiveScope -Identity "Project X" -FilterConditions @{"Conditions" = @{"Value" = "Redmond"; "Operator" = "Equals"; "Name" = "City"}; "Conjunction" = "And"} +``` + +This example modifies the filter in exiting adaptive scope named Project X. The new filter looks for all users in the city of Redmond. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AdministrativeUnit +{{ Fill AdministrativeUnit Description }} + +```yaml +Type: Guid +Parameter Sets: AdministrativeUnit +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: Guid +Parameter Sets: Default, AdaptiveScopeRawQuery +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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"}` +- Site: Indexed custom properties. For example, for the condition "'Refinable string 0' equals 'Human Resources', use the following syntax: `@{"Conditions" = @{"Value" = "Human Resources"; "Operator" = "Equals"; "Name" = "RefinableString00"}; "Conjunction" = "And"}` + +You can't use this parameter with the RawQuery parameter. + +```yaml +Type: PswsHashtable +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RawQuery +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. + +```yaml +Type: String +Parameter Sets: AdaptiveScopeRawQuery +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-AddressBookPolicy.md b/exchange/exchange-ps/exchange/Set-AddressBookPolicy.md similarity index 76% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-AddressBookPolicy.md rename to exchange/exchange-ps/exchange/Set-AddressBookPolicy.md index c17ef5cabd..6438ed69a2 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-AddressBookPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AddressBookPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/set-addressbookpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-AddressBookPolicy @@ -17,21 +16,27 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-AddressBookPolicy cmdlet to change the settings of an address book policy. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-AddressBookPolicy [-Identity] [-AddressLists ] - [-Confirm] [-DomainController ] [-GlobalAddressList ] [-Name ] - [-OfflineAddressBook ] [-RoomList ] [-WhatIf] +Set-AddressBookPolicy [-Identity] + [-AddressLists ] + [-Confirm] + [-DomainController ] + [-GlobalAddressList ] + [-Name ] + [-OfflineAddressBook ] + [-RoomList ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,8 +84,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -163,7 +167,19 @@ Accept wildcard characters: False ``` ### -RoomList -The RoomList parameter specifies the name of the room address list. +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. +- When using experiences that aren't location specific (for example, the To or Cc fields of a calendar event), the address lists specified by the AddressLists parameter in this address book policy are applied. The address list specified by this parameter isn't used. + +A valid value for this parameter is one address list. You can use any value that uniquely identifies the address list. For example: + +- Name +- Distinguished name (DN) +- GUID + +> [!NOTE] +> There's no automatic association between this parameter and [room list distribution groups](https://learn.microsoft.com/exchange/recipients/room-mailboxes#create-a-room-list), which also use a parameter named RoomList in the New-DistributionGroup and Set-DistributionGroup cmdlets. You still need to create room list distribution groups and assign resources as group members. Location experiences are filtered to show only rooms included in the address list that's specified by the RoomList property of the address book policy that's assigned to the user (if any). ```yaml Type: AddressListIdParameter @@ -199,12 +215,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-AddressList.md b/exchange/exchange-ps/exchange/Set-AddressList.md similarity index 78% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-AddressList.md rename to exchange/exchange-ps/exchange/Set-AddressList.md index f18d89db64..686f5b3185 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-AddressList.md +++ b/exchange/exchange-ps/exchange/Set-AddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/set-addresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-AddressList @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-AddressList cmdlet to modify existing address lists. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -51,7 +50,8 @@ Set-AddressList [-Identity] [-Name ] [-RecipientContainer ] [-RecipientFilter ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -60,16 +60,14 @@ Use the Get-AddressList cmdlet, piped to Format-List, to get the GUID, distingui The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - - The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - - The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPath filter. +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter. -You can't use this cmdlet to replace a precanned filter with a custom OPath filter, or vice-versa. You can only modify the existing filter. +You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -93,12 +91,9 @@ This example modifies the type of recipients and the department of the recipient 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 - - Distinguished name (DN) - - GUID - -- Path: (\\\) or [\\\\) +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) ```yaml Type: AddressListIdParameter @@ -118,9 +113,9 @@ The ConditionalCompany parameter specifies a precanned filter that's based on th 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -140,9 +135,9 @@ The ConditionalCustomAttribute1 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -162,9 +157,9 @@ The ConditionalCustomAttribute10 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -184,9 +179,9 @@ The ConditionalCustomAttribute11 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -206,9 +201,9 @@ The ConditionalCustomAttribute12 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -228,9 +223,9 @@ The ConditionalCustomAttribute13 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -250,9 +245,9 @@ The ConditionalCustomAttribute14 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -272,9 +267,9 @@ The ConditionalCustomAttribute15 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -294,9 +289,9 @@ The ConditionalCustomAttribute2 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -316,9 +311,9 @@ The ConditionalCustomAttribute3 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -338,9 +333,9 @@ The ConditionalCustomAttribute4 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -360,9 +355,9 @@ The ConditionalCustomAttribute5 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -382,9 +377,9 @@ The ConditionalCustomAttribute6 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -404,9 +399,9 @@ The ConditionalCustomAttribute7 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -426,9 +421,9 @@ The ConditionalCustomAttribute8 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -448,9 +443,9 @@ The ConditionalCustomAttribute9 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -470,9 +465,9 @@ The ConditionalDepartment parameter specifies a precanned filter that's based on 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -492,9 +487,9 @@ The ConditionalStateOrProvince parameter specifies a precanned filter that's bas 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -512,8 +507,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -566,7 +560,7 @@ Accept wildcard characters: False ### -ForceUpgrade This parameter is available only in on-premises Exchange. -The ForceUpgrade switch specifies whether to suppress 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. +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 @@ -585,15 +579,10 @@ Accept wildcard characters: False 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. - - MailboxUsers - - MailContacts - - MailGroups - - MailUsers - - Resources: This value indicates room or equipment mailboxes. You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. @@ -633,11 +622,8 @@ 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: - Name - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is the OU where the object was created. @@ -656,21 +642,16 @@ Accept wildcard characters: False ``` ### -RecipientFilter -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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). - In cloud-based environments, you can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. - - In on-premises Exchange, wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -706,12 +687,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-AddressRewriteEntry.md b/exchange/exchange-ps/exchange/Set-AddressRewriteEntry.md similarity index 92% rename from exchange/exchange-ps/exchange/mail-flow/Set-AddressRewriteEntry.md rename to exchange/exchange-ps/exchange/Set-AddressRewriteEntry.md index 6529d0e23a..09836f6007 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-AddressRewriteEntry.md +++ b/exchange/exchange-ps/exchange/Set-AddressRewriteEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-addressrewriteentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AddressRewriteEntry @@ -17,14 +16,21 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-AddressRewriteEntry cmdlet to modify an existing address rewrite entry that rewrites sender and recipient email addresses in messages sent to or sent from your organization through an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-AddressRewriteEntry [-Identity] [-Confirm] [-DomainController ] - [-ExceptionList ] [-ExternalAddress ] [-InternalAddress ] - [-Name ] [-OutboundOnly ] [-WhatIf] [] +Set-AddressRewriteEntry [-Identity] + [-Confirm] + [-DomainController ] + [-ExceptionList ] + [-ExternalAddress ] + [-InternalAddress ] + [-Name ] + [-OutboundOnly ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -71,8 +77,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -107,7 +112,7 @@ Accept wildcard characters: False ``` ### -ExceptionList -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://docs.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). +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 @@ -144,9 +149,7 @@ Accept wildcard characters: False 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 - - Single domain: contoso.com or sales.contoso.com - - Domain and all subdomains: \*.contoso.com ```yaml @@ -219,12 +222,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md b/exchange/exchange-ps/exchange/Set-AdminAuditLogConfig.md similarity index 83% rename from exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md rename to exchange/exchange-ps/exchange/Set-AdminAuditLogConfig.md index f9eb8261a9..6812c3cc6d 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md +++ b/exchange/exchange-ps/exchange/Set-AdminAuditLogConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/set-adminauditlogconfig -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-AdminAuditLogConfig @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-AdminAuditLogConfig cmdlet to configure the administrator audit logging configuration settings. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,11 +29,13 @@ Set-AdminAuditLogConfig [[-Identity] ] [-AdminAuditLogParameters ] [-Confirm] [-DomainController ] + [-Force] [-LogLevel ] [-Name ] [-TestCmdletLoggingEnabled ] [-UnifiedAuditLogIngestionEnabled ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -46,13 +47,13 @@ Administrator audit logging relies on Active Directory replication to replicate Changes to the audit log configuration may take up to 60 minutes to be applied on computers that have the Exchange Management Shell open at the time a configuration change is made. If you want to apply the changes immediately, close and reopen the Exchange Management Shell on each computer. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-AdminAuditLogConfig -AdminAuditLogEnabled $true -AdminAuditLogCmdlets * -AdminAuditLogParameters * +Set-AdminAuditLogConfig -AdminAuditLogEnabled $true -AdminAuditLogCmdlets * -AdminAuditLogParameters * -AdminAuditLogExcludedCmdlets Get-* ``` This example enables administrator audit logging for every cmdlet and every parameter in the organization, with the exception of Get cmdlets. @@ -73,6 +74,24 @@ This example enables administrator audit logging only for specific parameters th ## PARAMETERS +### -Identity +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -AdminAuditLogAgeLimit This parameter is available only in on-premises Exchange. @@ -120,7 +139,12 @@ Accept wildcard characters: False ### -AdminAuditLogEnabled This parameter is available only in on-premises Exchange. -The AdminAuditLogEnabled parameter specifies whether administrator audit logging is enabled. The default value is $true. The valid values are $true and $false. You must specify an administrator audit log mailbox before you enable logging. +The AdminAuditLogEnabled parameter specifies whether administrator audit logging is enabled. Valid values are: + +- $true: Administrator audit logging is enabled. This is the default value. +- $false: Administrator audit logging is disabled. + +You must specify an administrator audit log mailbox before you enable logging. Changes to the administrator audit log configuration are always logged, regardless of whether audit logging is enabled or disabled. @@ -180,16 +204,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named Default value: None @@ -216,14 +238,15 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named Default value: None @@ -231,28 +254,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -LogLevel 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 None and Verbose. +The LogLevel parameter specifies whether additional properties should be included in the log entries. Valid values are: -By default, the CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. When the Verbose value is used, the ModifiedProperties (old and new) and ModifiedObjectResolvedName properties are included in the log entries. +- None: The CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. This is the default value. +- Verbose: The ModifiedProperties (old and new) and ModifiedObjectResolvedName properties are also included in log entries. ```yaml Type: AuditLogLevel @@ -290,7 +298,10 @@ Accept wildcard characters: False ### -TestCmdletLoggingEnabled This parameter is available only in on-premises Exchange. -The TestCmdletLoggingEnabled parameter specifies whether the execution of test cmdlets should be logged. Test cmdlets begin with the verb Test. Valid values are $true and $false. The default value is $false. +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: + +- $true: Test cmdlets are included in admin audit logging. +- $false: Test cmdlets aren't included in admin audit logging. This is the default value. Test cmdlets can produce a large amount of information. As such, you should only enable logging of test cmdlets for a short period of time. @@ -308,20 +319,18 @@ Accept wildcard characters: False ``` ### -UnifiedAuditLogIngestionEnabled -This parameter is available only in the cloud-based service. - -The UnifiedAuditLogIngestionEnabled parameter specifies whether to enable or disable the recording of user and admin activities in the Office 365 audit log. Valid values are: +This parameter is functional only in the cloud-based service. -- $true: User and admin activities are recorded in the Office 365 audit log, and you can search the Office 365 audit log. +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: -- $false: User and admin activities aren't recorded in the Office 365 audit log, and you can't search the Office 365 audit log. This is the default value. +- $true: User and admin activities are recorded in the Microsoft 365 audit log, and admins can search the Microsoft 365 audit log. This is the default value. +- $false: User and admin activities aren't recorded in the Microsoft 365 audit log, and admins can't search the Microsoft 365 audit log. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online - +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named Default value: None @@ -336,8 +345,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - +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 @@ -350,12 +358,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md new file mode 100644 index 0000000000..a552fa50b5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md @@ -0,0 +1,957 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AntiPhishPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-AntiPhishPolicy cmdlet to modify antiphish policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AntiPhishPolicy -Identity + [-AdminDisplayName ] + [-AuthenticationFailAction ] + [-Confirm] + [-DmarcQuarantineAction ] + [-DmarcRejectAction ] + [-Enabled ] + [-EnableFirstContactSafetyTips ] + [-EnableMailboxIntelligence ] + [-EnableMailboxIntelligenceProtection ] + [-EnableOrganizationDomainsProtection ] + [-EnableSimilarDomainsSafetyTips ] + [-EnableSimilarUsersSafetyTips ] + [-EnableSpoofIntelligence ] + [-EnableTargetedDomainsProtection ] + [-EnableTargetedUserProtection ] + [-EnableUnauthenticatedSender ] + [-EnableUnusualCharactersSafetyTips ] + [-EnableViaTag ] + [-ExcludedDomains ] + [-ExcludedSenders ] + [-HonorDmarcPolicy ] + [-ImpersonationProtectionState ] + [-MailboxIntelligenceProtectionAction ] + [-MailboxIntelligenceProtectionActionRecipients ] + [-MailboxIntelligenceQuarantineTag ] + [-MakeDefault] + [-PhishThresholdLevel ] + [-PolicyTag ] + [-SpoofQuarantineTag ] + [-TargetedDomainActionRecipients ] + [-TargetedDomainProtectionAction ] + [-TargetedDomainQuarantineTag ] + [-TargetedDomainsToProtect ] + [-TargetedUserActionRecipients ] + [-TargetedUserProtectionAction ] + [-TargetedUserQuarantineTag ] + [-TargetedUsersToProtect ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AntiPhishPolicy -Identity "Office365 AntiPhish Default" -AuthenticationFailAction Quarantine +``` + +This example modifies the default antiphish policy named Office365 AntiPhish Default to quarantine spoofed messages from senders who aren't allowed to spoof. + +### Example 2 +```powershell +Set-AntiPhishPolicy -Identity "Office365 AntiPhish Default" -EnableOrganizationDomainsProtection $true -EnableTargetedDomainsProtection $true -TargetedDomainsToProtect fabrikam.com -TargetedDomainProtectionAction Quarantine -EnableTargetedUserProtection $true -TargetedUsersToProtect "Mai Fujito;mfujito@fabrikam.com" -TargetedUserProtectionAction Quarantine -EnableMailboxIntelligenceProtection $true -MailboxIntelligenceProtectionAction Quarantine -EnableSimilarUsersSafetyTips $true -EnableSimilarDomainsSafetyTips $true -EnableUnusualCharactersSafetyTips $true +``` + +In Microsoft Defender for Office 365, this example modifies the default antiphish policy named Office365 AntiPhish Default with the following settings: + +- Enables organization domains protection for all accepted domains, and targeted domains protection for fabrikam.com. +- Specifies Mai Fujito (mfujito@fabrikam.com) as a user to protect from impersonation. +- Enables mailbox intelligence protection, and specifies the quarantine action. +- Enables impersonation safety tips (impersonated domains, impersonated users, and unusual characters). + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: AntiPhishPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuthenticationFailAction +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: + +- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. + +```yaml +Type: SpoofAuthenticationFailAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DmarcQuarantineAction +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: + +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. This is the default value. + +```yaml +Type: SpoofDmarcQuarantineAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DmarcRejectAction +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: + +- Quarantine: Deliver the message to quarantine. +- Reject: Reject the message. This is the default value. + +This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. + +```yaml +Type: SpoofDmarcRejectAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. + +To create a disabled anti-phishing policy, use `-Enabled $false` on the **New-AntiPhishRule** cmdlet. + +In the output of the **Get-AntiPhishRule** cmdlet, whether the anti-phishing policy is enabled or disabled is visible in the State property. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -EnableFirstContactSafetyTips +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. +- $false: First contact safety tips are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMailboxIntelligence +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: + +- $true: Mailbox intelligence is enabled. This is the default value. +- $false: Mailbox intelligence is disabled. The values of the EnableMailboxIntelligenceProtection and MailboxIntelligenceProtectionAction parameters are ignored. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMailboxIntelligenceProtection +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: + +- $true: Take action for impersonation detections from mailbox intelligence results. Use the MailboxIntelligenceProtectionAction parameter to specify the action. +- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This is the default value. + +This parameter is meaningful only if the EnableMailboxIntelligence parameter is set to the value $true. + +If you set this parameter to the value $false when the value of the EnableMailboxIntelligence parameter is $true, no action is taken on messages based on mailbox intelligence results (for example, lack of communication history). But, but mailbox intelligence can still help reduce impersonation false positives based on frequent contact information. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOrganizationDomainsProtection +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: + +- $true: Domain impersonation protection is enabled for all registered domains in the Microsoft 365 organization. +- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSimilarDomainsSafetyTips +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: + +- $true: Safety tips for similar domains are enabled. +- $false: Safety tips for similar domains are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSimilarUsersSafetyTips +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: + +- $true: Safety tips for similar users are enabled. +- $false: Safety tips for similar users are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSpoofIntelligence +This setting is part of spoof protection. + +The EnableSpoofIntelligence parameter specifies whether to enable or disable antispoofing protection for the policy. Valid values are: + +- $true: Antispoofing is enabled for the policy. This is the default and recommended value. Use the \*-TenantAllowBlockListSpoofItems, Get-SpoofIntelligenceInsight, and Get-SpoofMailReport cmdlets to view and specify the spoofed senders to allow or block. +- $false: Antispoofing is disabled for the policy. We only recommend this value if you have a domain that's protected by another email filtering service. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTargetedDomainsProtection +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: + +- $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter. +- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTargetedUserProtection +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: + +- $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter. +- $false: The TargetedUsersToProtect parameter isn't used. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUnauthenticatedSender +This setting is part of spoof protection. + +The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are: + +- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. +- $false: A question mark is never applied to the sender's photo. + +To prevent these identifiers from being added to messages from specific senders, you have the following options: + +- Allow the sender to spoof in the spoof intelligence policy. For instructions, see [Configure spoof intelligence in Microsoft 365](https://learn.microsoft.com/defender-office-365/anti-spoofing-spoof-intelligence). +- If you own the domain, configure email authentication for the domain. For more information, see [Configure email authentication for domains you own](https://learn.microsoft.com/defender-office-365/email-authentication-about). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUnusualCharactersSafetyTips +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: + +- $true: Safety tips for unusual characters are enabled. +- $false: Safety tips for unusual characters are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableViaTag +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: + +- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This is the default value. +- $false: The via tag is not added to the From address. + +To prevent the via tag from being added to messages from specific senders, you have the following options: + +- Allow the sender to spoof. For instructions, see [Configure spoof intelligence in Microsoft 365](https://learn.microsoft.com/defender-office-365/anti-spoofing-spoof-intelligence). +- If you own the domain, configure email authentication for the domain. For more information, see [Configure email authentication for domains you own](https://learn.microsoft.com/defender-office-365/email-authentication-about). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedDomains +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. + +The maximum number of entries is approximately 1000. + +**Note**: Domain entries don't include subdomains of the specified domain. You need to add an entry for each subdomain. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedSenders +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. + +The maximum number of entries is approximately 1000. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HonorDmarcPolicy +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: + +- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This is the default value. +- $false: If the message fails DMARC, ignore the action in the sender's DMARC policy. The AuthenticationFailAction parameter specifies the action to take on the message. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImpersonationProtectionState +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: + +- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy. +- Manual: This is the default value in custom policies that you create. +- Off + +```yaml +Type: ImpersonationProtectionState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxIntelligenceProtectionAction +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: + +- NoAction: This is the default value. Note that this value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. +- BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. +- Redirect: Redirect the message to the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter. + +This parameter is meaningful only if the EnableMailboxIntelligence and EnableMailboxIntelligenceProtection parameters are set to the value $true. + +```yaml +Type: ImpersonationAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxIntelligenceProtectionActionRecipients +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. + +A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxIntelligenceQuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined by mailbox intelligence impersonation protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeDefault +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). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishThresholdLevel +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: + +- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. +- 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence. +- 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence. +- 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTag +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpoofQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined by spoof intelligence protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainActionRecipients +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. + +A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainProtectionAction +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: + +- NoAction: This is the default value. +- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message, and deliver the message to the Junk Email folder of all (original + BCC-ed) recipients' mailboxes. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. +- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainQuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined by domain impersonation protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedDomainsToProtect +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. + +You can specify multiple domains separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUserActionRecipients +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. + +A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUserProtectionAction +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: + +- NoAction: This is the default value. +- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. +- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. +- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUserQuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined by user impersonation protection as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetedUsersToProtect +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. + +This parameter uses the syntax: "DisplayName;EmailAddress". + +- DisplayName specifies the display name of the user that could be a target of impersonation. This value can contain special characters. +- EmailAddress specifies the internal or external email address that's associated with the display name. +- You can specify multiple values that overwrite any existing values by using the syntax: `"DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN"`. The combination of DisplayName and EmailAddress needs to be unique for each value. +- You can append new values by using the syntax: `@{Add="NewDisplayName1;NewEmailAddress1","NewDisplayName2;NewEmailAddress2",..."NewDisplayNameN;NewEmailAddressN"}` or remove an existing value using the syntax: `@{Remove="OldDisplayName1;OldEmailAddress1"}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-AntiPhishRule.md b/exchange/exchange-ps/exchange/Set-AntiPhishRule.md new file mode 100644 index 0000000000..9d41dff174 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AntiPhishRule.md @@ -0,0 +1,331 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AntiPhishRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-AntiPhishRule cmdlet to modify antiphish rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AntiPhishRule [-Identity] + [-AntiPhishPolicy ] + [-Comments ] + [-Confirm] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Name ] + [-Priority ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Common policy settings](https://learn.microsoft.com/defender-office-365/anti-phishing-policies-about#common-policy-settings). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AntiPhishRule -Identity "Engineering Department Phishing Rule" -ExceptIfRecipientDomainIs fabrikam.com +``` + +This example modifies the existing antiphish rule named Engineering Department Phishing Rule to exclude messages sent to the fabrikam.com domain. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AntiPhishPolicy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: AntiPhishPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-App.md b/exchange/exchange-ps/exchange/Set-App.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Set-App.md rename to exchange/exchange-ps/exchange/Set-App.md index 879bbd0a04..af5a021961 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-App.md +++ b/exchange/exchange-ps/exchange/Set-App.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-app -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-App @@ -17,14 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-App cmdlet to modify the availability of organization apps. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-App [-Identity] [-Confirm] [-DefaultStateForUser ] - [-DomainController ] [-Enabled ] [-OrganizationApp] - [-ProvidedTo ] [-UserList ] [-WhatIf] [-PrivateCatalog] +Set-App [-Identity] + [-Confirm] + [-DefaultStateForUser ] + [-DomainController ] + [-Enabled ] + [-OrganizationApp] + [-PrivateCatalog] + [-ProvidedTo ] + [-UserList ] + [-WhatIf] [] ``` @@ -33,15 +39,17 @@ The Set-App cmdlet can only be used when configuring the availability of an orga Default apps in Outlook on the web and apps that you've installed for use by users in your organization are known as organization apps. Organization apps can't be removed by end users, but can be enabled or disabled. If an app is an organization app (scope default or organization), the delete control on the toolbar is disabled for end users. Administrators are able to remove organization apps. Administrators can't remove default apps, but they can disable them for the entire organization. -For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://docs.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of Office 365 add-ins in the Microsoft 365 admin center](https://docs.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). +For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$a= Get-DistributionGroupMember -Identity "Finance Team"; Set-App -OrganizationApp -Identity 3f10017a-9bbe-4a23-834b-6a8fe3af0e37 -ProvidedTo SpecificUsers -UserList $a.Identity -DefaultStateForUser Enabled +$a= Get-DistributionGroupMember -Identity "Finance Team" + +Set-App -OrganizationApp -Identity 3f10017a-9bbe-4a23-834b-6a8fe3af0e37 -ProvidedTo SpecificUsers -UserList $a.Identity -DefaultStateForUser Enabled ``` This example changes the organization app named FinanceTestApp, which was installed to everyone in the organization, to be provided to members of the Finance Team group and to be enabled by default. @@ -62,7 +70,7 @@ The Identity parameter specifies the AppID (GUID value) of the app that you want Type: AppIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -74,15 +82,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -95,9 +102,7 @@ Accept wildcard characters: False 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. - - Disabled: The organization app is disabled. This is the default value. - - AlwaysEnabled: The organization app is enabled, and users can't disable it. You use this parameter with the OrganizationApp switch. @@ -137,7 +142,6 @@ Accept wildcard characters: False 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. - - $false: The app isn't enabled for any users in the organization. This hides the app from user view for all users. This setting overrides the ProvidedTo, UserList, and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions. @@ -171,11 +175,26 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PrivateCatalog +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ProvidedTo 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. - - SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. You use this parameter with the OrganizationApp switch. @@ -194,31 +213,22 @@ Accept wildcard characters: False ``` ### -UserList -The UserList parameter specifies who can use an organizational app. This parameter is currently limited to 1000 users. This will not change in the future as we are planning on moving to [Centralized Deployment](https://docs.microsoft.com/office/dev/add-ins/publish/centralized-deployment). +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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". Maximum size of the list is 1000 recipients. +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"`. Maximum size of the list is 1000 recipients. You use this parameter with the OrganizationApp switch. @@ -242,23 +252,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateCatalog -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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -272,12 +266,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md new file mode 100644 index 0000000000..d7b88cea53 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md @@ -0,0 +1,660 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AppRetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-AppRetentionCompliancePolicy to modify app retention compliance policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Set-AppRetentionCompliancePolicy [-Identity] + [-AddExchangeLocation ] + [-AddExchangeLocationException ] + [-AddModernGroupLocation ] + [-AddModernGroupLocationException ] + [-Applications ] + [-Comment ] + [-Confirm] + [-DeletedResources ] + [-Enabled ] + [-Force] + [-PolicyRBACScopes ] + [-RemoveExchangeLocation ] + [-RemoveExchangeLocationException ] + [-RemoveModernGroupLocation ] + [-RemoveModernGroupLocationException ] + [-RestrictiveRetention ] + [-WhatIf] + [] +``` + +### AdaptiveScopeLocation +``` +Set-AppRetentionCompliancePolicy [-Identity] + [-AddAdaptiveScopeLocation ] + [-Applications ] + [-Comment ] + [-Confirm] + [-DeletedResources ] + [-Enabled ] + [-Force] + [-RemoveAdaptiveScopeLocation ] + [-WhatIf] + [] +``` + +### DisableRestrictiveRetentionParameterSet +``` +Set-AppRetentionCompliancePolicy [-Identity] + [-Confirm] + [-DeletedResources ] + [-WhatIf] + [] +``` + +### InformationBarrierDefault +``` +Set-AppRetentionCompliancePolicy [-Identity] + [-Confirm] + [-DeletedResources ] + [-Force] + [-WhatIf] + [] +``` + +### OrganizationSegmentsDefault +``` +Set-AppRetentionCompliancePolicy [-Identity] + [-Confirm] + [-DeletedResources ] + [-WhatIf] + [] +``` + +### RetryDistributionParameterSet +``` +Set-AppRetentionCompliancePolicy [-Identity] + [-Confirm] + [-RetryDistribution] + [-WhatIf] + [] +``` + +### TeamLocation +``` +Set-AppRetentionCompliancePolicy [-Identity] + [-Comment ] + [-Confirm] + [-DeletedResources ] + [-Enabled ] + [-Force] + [-WhatIf] + [] +``` + +## DESCRIPTION +\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies in the locations described in [Retention cmdlets for newer locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-newer-locations). You can only set the list of included or excluded scopes for all included workloads, which means you likely need to create one policy per workload. + +\*-RetentionCompliance\* cmdlets continue to primarily support the locations described in [Retention cmdlets for older locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-older-locations). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AppRetentionCompliancePolicy -Identity "Regulation 563 Marketing" -Applications "User:MicrosoftTeams","Group:MicrosoftTeams,VivaEngage" -AddExchangeLocation "Scott Smith" -Comment "Added new counsel, 9/9/21" +``` + +This example adds a new user to the existing static scope retention policy named Regulation 563 Marketing that's set up for Teams private channels messages. + +### Example 2 +```powershell +$stringJson = @" +[{ + 'EmailAddress': 'SalesUser@contoso.onmicrosoft.com' +}] +"@ +Set-AppRetentionCompliancePolicy -Identity "Teams Private Channel Retention Policy" -AddExchangeLocationException "SalesUser@contoso.onmicrosoft.com" -DeletedResources $stringJson +``` +This example excludes the specified soft-deleted mailbox or mail user from the retention policy configured for Teams private channel messages. You can identify the deleted resources using the mailbox or mail user's email address. + +**IMPORTANT**: Before you run this command, make sure you read the Caution information for the [DeletedResources parameter](#-deletedresources) about duplicate SMTP addresses. + +Policy exclusions must remain within the supported limits for retention policies. For more information, see [Limits for Microsoft 365 retention policies and retention label policies](https://learn.microsoft.com/purview/retention-limits#maximum-number-of-items-per-policy). + +### Example 3 +```powershell +$stringJson = @" +[{ + 'EmailAddress': 'SalesUser1@contoso.onmicrosoft.com' +}, +{ + 'EmailAddress': 'SalesUser2@contoso.onmicrosoft.com' +}] +"@ +Set-AppRetentionCompliancePolicy -Identity "Teams Private Chat Retention Policy" -AddExchangeLocationException "SalesUser1@contoso.onmicrosoft.com", "SalesUser2@contoso.onmicrosoft.com" -DeletedResources $stringJson +``` + +This example is similar to Example 2, except multiple deleted resources are specified. + +**IMPORTANT**: Before you run this command, make sure you read the Caution information for the [DeletedResources parameter](#-deletedresources) about duplicate SMTP addresses. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -RetryDistribution +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. + +**Note**: Because the process of retrying distribution is a significant operation, run it only if necessary and for one policy at a time. It is not intended to be run every time you update a policy. If you run a script to update multiple policies, wait until the policy distribution is successful before running the command again for the next policy. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistributionParameterSet +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddAdaptiveScopeLocation +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 +- Distinguished name (DN) +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocation +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 +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocationException +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 +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddModernGroupLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddModernGroupLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Applications +The Applications parameter specifies the applications to include in the policy. + +This parameter uses the following syntax: `"LocationType:App1,LocationType:App2,...LocationType:AppN`: + +`LocationType` is User or Group. + +`App` is a supported value as shown in the following examples. + +- **Microsoft 365 apps**: For example: + + `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:VivaEngage"` + +- **Microsoft Copilot experiences**: Currently in Preview. You must use *all* of the following values at the same time: + + `"User:M365Copilot,CopilotForSecurity,CopilotinFabricPowerBI,CopilotStudio,CopilotinBusinessApplicationplatformsSales,SQLCopilot"` + + **Note**: Even though you must use `CopilotinBusinessApplicationplatformsSales` and `SQLCopilot`, those values are currently irrelevant. + +- **Enterprise AI apps**: Currently in Preview. You must use *all* of the following values at the same time: + + `"User:Entrabased3PAIApps,ChatGPTEnterprise,AzureAIServices"` + +- **Other AI apps**: Currently in Preview. You must use *all* of the following values at the same time: + + `"User:CloudAIAppChatGPTConsumer,CloudAIAppGoogleGemini,BingConsumer,DeepSeek"` + +```yaml +Type: String[] +Parameter Sets: Identity, AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeletedResources +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. + +For information about the inactive mailbox scenario, see [Learn about inactive mailboxes](https://learn.microsoft.com/purview/inactive-mailboxes-in-office-365). + +**CAUTION**: This parameter uses the SMTP address of the deleted mailbox or mail user, which might also be specified for other mailboxes or mail users. If you use this parameter without first taking additional steps, other mailboxes and mail users with the same SMTP address in the retention policy will also be excluded. To check for additional mailboxes or mail users with the same SMTP address, use the following command and replace `user@contoso.com` with the SMTP address to check: `Get-Recipient -IncludeSoftDeletedRecipients user@contoso.com | Select-Object DisplayName, EmailAddresses, Description, Alias, RecipientTypeDetails, WhenSoftDeleted` + +To prevent active mailboxes or mail users with the same SMTP address from being excluded, put the mailbox on [Litigation Hold](https://learn.microsoft.com/purview/ediscovery-create-a-litigation-hold) before you run the command with the DeletedResources parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter enables or disables the policy. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity, AdaptiveScopeLocation, TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, AdaptiveScopeLocation, TeamLocation, InformationBarrierDefault +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +**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. + +Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveAdaptiveScopeLocation +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 +- Distinguished name (DN) +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +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 +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocationException +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 +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveModernGroupLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveModernGroupLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictiveRetention +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. +- $false: Preservation Lock isn't enabled for the policy. This is the default value. + +After a policy has been locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. + +Therefore, before you lock a policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-AppRetentionComplianceRule.md b/exchange/exchange-ps/exchange/Set-AppRetentionComplianceRule.md new file mode 100644 index 0000000000..a6b2925a84 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AppRetentionComplianceRule.md @@ -0,0 +1,314 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AppRetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-AppRetentionComplianceRule to modify app retention compliance rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AppRetentionComplianceRule [-Identity] + [-Comment ] + [-Confirm] + [-ContentContainsSensitiveInformation ] + [-ContentDateFrom ] + [-ContentDateTo ] + [-ContentMatchQuery ] + [-ExcludedItemClasses ] + [-ExpirationDateOption ] + [-RetentionComplianceAction ] + [-RetentionDuration ] + [-RetentionDurationDisplayHint ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AppRetentionComplianceRule -Identity "563 Marketing Rule" -RetentionDuration 180 -RetentionDurationDisplayHint Days +``` + +This example updates the length of the retention duration for a rule named 563 Marketing Rule. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateFrom +{{ Fill ContentDateFrom Description }} + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateTo +{{ Fill ContentDateTo Description }} + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedItemClasses +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 +- IPM.Note.Microsoft.Conversation.Voice +- IPM.Note.Microsoft.Missed +- IPM.Note.Microsoft.Missed.Voice +- IPM.Note.Microsoft.Voicemail +- IPM.Note.Microsoft.VoiceMessage.UA +- IPM.Note.Microsoft.Voicemail.UM +- IPM.Note.Microsoft.Voicemail.UM.CA + +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or third-party message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. + +You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpirationDateOption +The ExpirationDateOption parameter specifies whether the expiration date is calculated from the content creation date or last modification date. Valid values are: + +- CreationAgeInDays +- ModificationAgeInDays + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionComplianceAction +The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: + +- Delete +- Keep +- KeepAndDelete + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies the hold duration for the retention rule. Valid values are: + +- An integer: The hold duration in days. +- Unlimited: The content is held indefinitely. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDurationDisplayHint +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 +- Months +- Years + +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. + +```yaml +Type: HoldDurationHint +Parameter Sets: (All) +Aliases: +Accepted values: Days, Months, Years +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/Set-ApplicationAccessPolicy.md similarity index 77% rename from exchange/exchange-ps/exchange/organization/Set-ApplicationAccessPolicy.md rename to exchange/exchange-ps/exchange/Set-ApplicationAccessPolicy.md index aa0439aee0..dd98f50127 100644 --- a/exchange/exchange-ps/exchange/organization/Set-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/exchange/Set-ApplicationAccessPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-applicationaccesspolicy -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Set-ApplicationAccessPolicy @@ -17,25 +16,22 @@ This cmdlet is available only in the cloud-based service. Use the Set-ApplicationAccessPolicy cmdlet to modify the description of an application access policy. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX -### Set1 ``` Set-ApplicationAccessPolicy [-Identity] [-Description ] [-Confirm] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,7 +51,7 @@ The Identity parameter specifies the application access policy that you want to Type: ApplicationAccessPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -71,7 +67,7 @@ The Description parameter modifies the description of the policy. If the value c Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -83,15 +79,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -101,13 +96,13 @@ Accept wildcard characters: False ``` ### -WhatIf -The WhatIf switch doesn’t work on this cmdlet. +The WhatIf switch doesn't work on this cmdlet. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -121,12 +116,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ArcConfig.md b/exchange/exchange-ps/exchange/Set-ArcConfig.md new file mode 100644 index 0000000000..5bf267a358 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ArcConfig.md @@ -0,0 +1,186 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ArcConfig + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ArcConfig cmdlet to modify the list of trusted Authenticated Received Chain (ARC) sealers that are configured in the cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ArcConfig [-Identity] -ArcTrustedSealers + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ArcConfig -Identity Default -ArcTrustedSealers fabrikam.com +``` + +This example configures "fabrikam.com" as the only trusted ARC sealer in the organization. + +### Example 2 +```powershell +$DomainsAdd = @(Get-ArcConfig | select -Expand ArcTrustedSealers) + +$DomainsAdd += "cohovineyard.com","tailspintoys.com" + +Set-ArcConfig -Identity Default -ArcTrustedSealers $DomainsAdd +``` + +This example adds the trusted ARC sealers "cohovineyard.com" and "tailspintoys.com" without affecting the other trusted ARC sealer entries. + +### Example 3 +```powershell +$x = @(Get-ArcConfig | select -Expand ArcTrustedSealers) + +$y = $x.Split(",") + +$DomainsRemove = [System.Collections.ArrayList]($y) + +$DomainsRemove + +$DomainsRemove.RemoveAt(6) + +Set-ArcConfig -Identity Default -ArcTrustedSealers $DomainsRemove +``` + +This example modifies the trusted ARC sealers list by removing an existing ARC sealer without affecting other ARC sealers that are already specified. + +The first four commands return the existing list of ARC sealers. The first ARC sealer in the list has the index number 0, the second has the index number 1, and so on. Use the index number to specify the ARC sealer that you want to remove. + +The last two commands remove the seventh ARC sealer that's displayed in the list. + +### Example 4 +```powershell +$arcSealer = 'fabrikam.com' +$x = @(Get-ArcConfig | Select-Object -Expand ArcTrustedSealers) + +$y = @($x.Split(",")) +$DomainsRemove = [System.Collections.ArrayList]($y) +$DomainsRemove.Remove($arcSealer) + +if ($DomainsToRemove.Count -eq 0) { + Set-ArcConfig -Identity Default -ArcTrustedSealers " " + } +else { + Set-ArcConfig -Identity Default -ArcTrustedSealers $DomainsRemove + } +``` + +This example removes the specified ARC sealer from the list (`$arcSealer`). + +If no other ARC sealers exist after removing this entry from the list, using the value `" "` for the ArcTrustedSealers parameter avoids a bind argument error if the `$DomainsToRemove` value is empty. + +## PARAMETERS + +### -Identity +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. +- \\Default for delegated organizations. The \ value is a GUID that's visible in many admin portal URLs in Microsoft 365 (the tid= value). For example, a32d39e2-3702-4ff5-9628-31358774c091. + +```yaml +Type: HostedConnectionFilterPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -ArcTrustedSealers +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. + +To replace the existing list of ARC sealers with the values you specify, use the syntax `Domain1,Domain2,...DomainN`. To preserve existing values, be sure to include the entries that you want to keep along with the new values that you want to add. + +To add or remove values without affecting the other entries, see the Examples section in this article. + +To empty the list, use the value `" "` (a space enclosed in double quotation marks). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md b/exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md new file mode 100644 index 0000000000..bcdc6c3dd1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md @@ -0,0 +1,178 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AtpPolicyForO365 + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-AtpPolicyForO365 cmdlet to modify the settings for the following features in Microsoft Defender for Office 365: + +- Safe Links protection for supported Office 365 apps. +- Safe Documents: Uses Microsoft Defender for Endpoint to scan documents and files that are opened in Protected View in Microsoft 365 apps for enterprise. +- Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AtpPolicyForO365 [[-Identity] ] + [-AllowSafeDocsOpen ] + [-Confirm] + [-EnableATPForSPOTeamsODB ] + [-EnableSafeDocs ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Safe Links protection for Office 365 apps checks links in Office documents, not links in email messages. For more information, see [Safe Links settings for Office 365 apps](https://learn.microsoft.com/defender-office-365/safe-links-about#safe-links-settings-for-office-apps). + +Safe Documents scans documents and files that are opened in Protected View. For more information, see [Safe Documents in Microsoft 365 E5](https://learn.microsoft.com/defender-office-365/safe-documents-in-e5-plus-security-about). + +Safe Attachments for SharePoint, OneDrive, and Microsoft Teams prevents users from opening and downloading files that are identified as malicious. For more information, see [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](https://learn.microsoft.com/defender-office-365/safe-attachments-for-spo-odfb-teams-about). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AtpPolicyForO365 -EnableATPForSPOTeamsODB $true +``` + +This example enables Safe Documents and Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AllowSafeDocsOpen +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. +- $false: Users aren't allowed to exit Protected View in case of a malicious detection. + +This parameter is meaningful only when the EnableSafeDocs parameter value is $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableATPForSPOTeamsODB +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. +- $false: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSafeDocs +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. +- $false: Safe Documents is disabled. This is the default value. + +For more information about Safe Documents, see [Safe Documents in Microsoft 365 A5 or E5 Security](https://learn.microsoft.com/defender-office-365/safe-documents-in-e5-plus-security-about) + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-AttachmentFilterListConfig.md b/exchange/exchange-ps/exchange/Set-AttachmentFilterListConfig.md similarity index 94% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-AttachmentFilterListConfig.md rename to exchange/exchange-ps/exchange/Set-AttachmentFilterListConfig.md index 8996427ad0..0bc5e542b8 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-AttachmentFilterListConfig.md +++ b/exchange/exchange-ps/exchange/Set-AttachmentFilterListConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-attachmentfilterlistconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AttachmentFilterListConfig @@ -17,7 +16,7 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-AttachmentFilterListConfig cmdlet to modify the configuration of the Attachment Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ Set-AttachmentFilterListConfig [-DomainController ] [-ExceptionConnectors ] [-RejectResponse ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -52,9 +52,7 @@ This example modifies the action that the Attachment Filtering agent takes on an 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. - - Strip: This value removes the offending attachment from the email message and allows the message and other attachments that don't match an entry on the attachment filter list through. A notification that the attachment was removed is added to the email message. - - SilentDelete: This value prevents both the email message and the attachment from being delivered to the recipient. No notification that the email message and attachment were blocked is sent to the sender. ```yaml @@ -89,8 +87,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -177,12 +174,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-AuditConfig.md b/exchange/exchange-ps/exchange/Set-AuditConfig.md new file mode 100644 index 0000000000..e2c5d20cfd --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AuditConfig.md @@ -0,0 +1,124 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AuditConfig + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-AuditConfig cmdlet to configure the auditing configuration in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AuditConfig [[-Identity] ] -Workload + [-DomainController ] + [-Organization ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AuditConfig -Workload Exchange,SharePoint +``` + +This example sets the auditing configuration for Exchange and SharePoint. + +## PARAMETERS + +### -Identity +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Workload +The Workload parameter specifies where auditing is allowed. Valid values are: + +- Exchange +- InTune +- OneDriveForBusiness +- SharePoint + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-AuthConfig.md b/exchange/exchange-ps/exchange/Set-AuthConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/organization/Set-AuthConfig.md rename to exchange/exchange-ps/exchange/Set-AuthConfig.md index a5af981dd8..a6ffa805ac 100644 --- a/exchange/exchange-ps/exchange/organization/Set-AuthConfig.md +++ b/exchange/exchange-ps/exchange/Set-AuthConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-authconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AuthConfig @@ -17,57 +16,66 @@ This cmdlet is available only in on-premises Exchange. Use the Set-AuthConfig cmdlet to modify the authorization configuration for your Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### CurrentCertificateParameter ``` -Set-AuthConfig -CertificateThumbprint [-SkipImmediateCertificateDeployment] +Set-AuthConfig -CertificateThumbprint + [-SkipImmediateCertificateDeployment] [-Confirm] [-DomainController ] [-Force] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### PublishAuthCertificateParameter ``` -Set-AuthConfig [-ClearPreviousCertificate] [-PublishCertificate] +Set-AuthConfig [-ClearPreviousCertificate] + [-PublishCertificate] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### NewCertificateParameter ``` -Set-AuthConfig [-NewCertificateEffectiveDate ] [-NewCertificateThumbprint ] [-SkipImmediateCertificateDeployment] +Set-AuthConfig [-NewCertificateEffectiveDate ] + [-NewCertificateThumbprint ] + [-SkipImmediateCertificateDeployment] [-Confirm] [-DomainController ] [-Force] [-Server ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### AuthConfigSettings ``` -Set-AuthConfig [-Realm ] [-ServiceName ] +Set-AuthConfig [-Realm ] + [-ServiceName ] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Set-AuthConfig parameter defines Microsoft Exchange as a partner application for server-to-server authentication with other partner applications such as Microsoft SharePoint 2013 and Microsoft Lync 2013 or Skype for Business Server 2015, including the certificate used for signing tokens. It's generally not required for this configuration to be modified except in some cases where you must use a different certificate instead of the self-signed certificate created by Exchange Setup or to use a new certificate after the old one has expired. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-AuthConfig -NewCertificateThumbprint DB821B4FCA2A5DA9593B9DE00C86BC5EA35D0FC0 -NewCertificateEffectiveDate 4/17/2013 +Set-AuthConfig -NewCertificateThumbprint DB821B4FCA2A5DA9593B9DE00C86BC5EA35D0FC0 -NewCertificateEffectiveDate 4/17/2014 ``` This example specifies a new certificate and a date when the certificate will become effective. @@ -98,7 +106,7 @@ Accept wildcard characters: False ``` ### -ClearPreviousCertificate -The ClearPreviousCertificate switch clears the certificate saved as the previous certificate in the authorization configuration. +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 @@ -116,8 +124,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -150,7 +157,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -198,7 +207,9 @@ Accept wildcard characters: False ``` ### -PublishCertificate -The PublishCertificate switch specifies that the specified certificate be immediately rolled over as the current certificate. The certificate is immediately deployed to all Client Access servers. +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. ```yaml Type: SwitchParameter @@ -264,7 +275,9 @@ Accept wildcard characters: False ``` ### -SkipImmediateCertificateDeployment -The SkipImmediateCertificateDeployment switch specifies that the certificate shouldn't be used immediately. We recommend that you don't use this parameter in a production environment. +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. ```yaml Type: SwitchParameter @@ -300,12 +313,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-AuthRedirect.md b/exchange/exchange-ps/exchange/Set-AuthRedirect.md similarity index 82% rename from exchange/exchange-ps/exchange/client-access-servers/Set-AuthRedirect.md rename to exchange/exchange-ps/exchange/Set-AuthRedirect.md index 562eb3884c..e39dde30f7 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-AuthRedirect.md +++ b/exchange/exchange-ps/exchange/Set-AuthRedirect.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-authredirect +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AuthRedirect @@ -17,26 +16,30 @@ This cmdlet is available only in on-premises Exchange. Use the Set-AuthRedirect cmdlet to modify the existing OAuth redirection settings for Microsoft Exchange 2010 Client Access servers in your Microsoft Exchange 2013 organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-AuthRedirect [-Identity] [-Confirm] [-DomainController ] - [-TargetUrl ] [-WhatIf] [] +Set-AuthRedirect [-Identity] + [-Confirm] + [-DomainController ] + [-TargetUrl ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-AuthRedirect AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE -TargetUrl https://mbx01.contoso.com +Set-AuthRedirect -Identity AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE -TargetUrl https://mbx01.contoso.com ``` -This example sets the TargetURL value to https://mbx01.contoso.com for the existing OAuth redirection object named AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE. +This example sets the TargetURL value to `https://mbx01.contoso.com` for the existing OAuth redirection object named `AuthRedirect-Bearer-C0B7AC3F-FE64-4B4B-A907-9226F8027CCE`. ### Example 2 ```powershell @@ -48,7 +51,7 @@ This example sets the TargetURL value for all existing OAuth redirection objects ## PARAMETERS ### -Identity -The Identity parameter specifies the existing OAuth redirection object that you want to modify. The object name uses the syntax AuthRedirect-Bearer-\. The easiest way to find the name of the OAuth redirection object is to run Get-AuthRedirect. +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 @@ -66,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -136,12 +138,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Set-AuthServer.md b/exchange/exchange-ps/exchange/Set-AuthServer.md similarity index 77% rename from exchange/exchange-ps/exchange/organization/Set-AuthServer.md rename to exchange/exchange-ps/exchange/Set-AuthServer.md index dff9a88d36..7caef4d3c2 100644 --- a/exchange/exchange-ps/exchange/organization/Set-AuthServer.md +++ b/exchange/exchange-ps/exchange/Set-AuthServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-authserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AuthServer @@ -17,38 +16,63 @@ This cmdlet is available only in on-premises Exchange. Use the Set-AuthServer cmdlet to configure an authorization server that partner applications can use to obtain tokens recognized by Microsoft Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### AuthMetadataUrl ``` -Set-AuthServer [-Identity] [-AuthMetadataUrl ] [-TrustAnySSLCertificate] +Set-AuthServer [-Identity] + [-AuthMetadataUrl ] + [-TrustAnySSLCertificate] [-Confirm] [-DomainController ] + [-DomainName ] [-Enabled ] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### NativeClientAuthServer ``` -Set-AuthServer [-Identity] [-AuthMetadataUrl ] [-IsDefaultAuthorizationEndpoint ] [-TrustAnySSLCertificate] +Set-AuthServer [-Identity] + [-AuthMetadataUrl ] + [-IsDefaultAuthorizationEndpoint ] + [-TrustAnySSLCertificate] [-Confirm] [-DomainController ] + [-DomainName ] [-Enabled ] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RefreshAuthMetadata ``` -Set-AuthServer [-Identity] [-RefreshAuthMetadata] +Set-AuthServer [-Identity] + [-RefreshAuthMetadata] [-Confirm] [-DomainController ] + [-DomainName ] [-Enabled ] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] +``` + +### AppSecret +``` +Set-AuthServer [-Identity] + [-ApplicationIdentifier ] + [-Confirm] + [-DomainController ] + [-DomainName ] + [-Enabled ] + [-Name ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -56,7 +80,7 @@ Partner applications authorized by Exchange can access their resources after the Use the Set-AuthServer cmdlet to enable or disable the authorization server, change the AuthMetadataUrl parameter or refresh authorization metadata. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -73,9 +97,7 @@ This command disables the authorization server ACS. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -91,6 +113,24 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -ApplicationIdentifier +This parameter is available in the April 18, 2025 Hotfix update (HU) for Exchange 2019 CU15 and Exchange 2016 CU23. + +{{ Fill ApplicationIdentifier Description }} + +```yaml +Type: String +Parameter Sets: AppSecret +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -AuthMetadataUrl The AuthMetadataUrl parameter specifies the URL of the authorization server. This can be the AuthMetadataUrl of your Exchange Online organization. @@ -110,8 +150,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -143,13 +182,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DomainName +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". + +This parameter is used to link Tenant to the corresponding authserver object in the Multi-Tenant Exchange Hybrid. For example, if DomainName is contoso.onmicrosoft.com, then the AuthServer object will be associated with the contoso tenant. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + ### -Enabled 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: - $true: Authorization tokens that are issued by the authorization server are accepted. This is the default value - - $false: The authorization server does not issue or accept authorization tokens. ```yaml @@ -218,7 +276,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether Exchange should accept certificates from an untrusted certification authority. You don't need to specify a value with this switch. +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. @@ -256,12 +314,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md new file mode 100644 index 0000000000..5f9a01b922 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -0,0 +1,793 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AuthenticationPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-AuthenticationPolicy cmdlet to modify authentication policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AuthenticationPolicy [-Identity] + [-AllowBasicAuthActiveSync] + [-AllowBasicAuthAutodiscover] + [-AllowBasicAuthImap] + [-AllowBasicAuthMapi] + [-AllowBasicAuthOfflineAddressBook] + [-AllowBasicAuthOutlookService] + [-AllowBasicAuthPop] + [-AllowBasicAuthPowershell] + [-AllowBasicAuthReportingWebServices] + [-AllowBasicAuthRpc] + [-AllowBasicAuthSmtp] + [-AllowBasicAuthWebServices] + [-AllowLegacyExchangeTokens] + [-BlockLegacyAuthActiveSync] + [-BlockLegacyAuthAutodiscover] + [-BlockLegacyAuthImap] + [-BlockLegacyAuthMapi] + [-BlockLegacyAuthOfflineAddressBook] + [-BlockLegacyAuthPop] + [-BlockLegacyAuthRpc] + [-BlockLegacyAuthWebServices] + [-BlockLegacyExchangeTokens] + [-BlockModernAuthActiveSync] + [-BlockModernAuthAutodiscover] + [-BlockModernAuthImap] + [-BlockModernAuthMapi] + [-BlockModernAuthOfflineAddressBook] + [-BlockModernAuthPop] + [-BlockModernAuthRpc] + [-BlockModernAuthWebServices] + [-Confirm] + [-TenantId ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AuthenticationPolicy -Identity "Engineering Group" -AllowBasicAuthReportingWebServices +``` + +In Exchange Online, this example modifies the authentication policy named Engineering Group to allow Basic authentication for Exchange Reporting Web Services. + +### Example 2 +```powershell +Set-AuthenticationPolicy -Identity "Research and Development Group" -BlockLegacyAuthReportingWebServices:$false +``` + +In Exchange 2019, this example re-enables Basic authentication for Exchange Reporting Web Services in the authentication policy named Research and Development Group. + +### Example 3 +```powershell +Set-AuthenticationPolicy -Identity "LegacyExchangeTokens" -BlockLegacyExchangeTokens +``` + +In Exchange Online, this example blocks legacy Exchange tokens from being issued to Outlook add-ins. The switch applies to the entire organization, and the Identity parameter must be set to the value "LegacyExchangeTokens". Specific authentication policies can't be applied. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the authentication policy you want to modify. You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: AuthPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthActiveSync +This parameter is available only in the cloud-based service. + +The AllowBasicAuthActiveSync switch specifies whether to allow Basic authentication with Exchange Active Sync. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthActiveSync:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthAutodiscover +This parameter is available only in the cloud-based service. + +The AllowBasicAuthAutodiscover switch specifies whether to allow Basic authentication with Autodiscover. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthAutodiscover:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthImap +This parameter is available only in the cloud-based service. + +The AllowBasicAuthImap switch specifies whether to allow Basic authentication with IMAP. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthImap:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthMapi +This parameter is available only in the cloud-based service. + +The AllowBasicAuthMapi switch specifies whether to allow Basic authentication with MAPI. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAutMapi:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthOfflineAddressBook +This parameter is available only in the cloud-based service. + +The AllowBasicAuthOfflineAddressBook switch specifies whether to allow Basic authentication with Offline Address Books. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthOfflineAddressBook:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthOutlookService +This parameter is available only in the cloud-based service. + +The AllowBasicAuthOutlookService switch specifies whether to allow Basic authentication with the Outlook service. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthOutlookService:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthPop +This parameter is available only in the cloud-based service. + +The AllowBasicAuthPop switch specifies whether to allow Basic authentication with POP. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthPop:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthPowershell +This parameter is available only in the cloud-based service. + +The AllowBasicAuthPowerShell switch specifies whether to allow Basic authentication with PowerShell. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthPowershell:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthReportingWebServices +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. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthReportingWebServices:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthRpc +This parameter is available only in the cloud-based service. + +The AllowBasicAuthRpc switch specifies whether to allow Basic authentication with RPC. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthRpc:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthSmtp +This parameter is available only in the cloud-based service. + +The AllowBasicAuthSmtp switch specifies whether to allow Basic authentication with SMTP. + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthSmtp:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBasicAuthWebServices +This parameter is available only in the cloud-based service. + +The AllowBasicAuthWebServices switch specifies whether to allow Basic authentication with Exchange Web Services (EWS). + +- To allow Basic authentication for the protocol, use this switch without a value. +- To block Basic authentication for the protocol, use this exact syntax: `-AllowBasicAuthWebServices:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLegacyExchangeTokens +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. + +Legacy Exchange tokens include Exchange user identity and callback tokens. + +The switch applies to the entire organization. The Identity parameter is required and must be set to the value "LegacyExchangeTokens". Specific authentication policies can't be applied. + +**Important**: + +- Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- It might take up to 24 hours for the change to take effect across your entire organization. +- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthActiveSync +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for ActiveSync, use this switch without a value. +- To allow legacy authentication methods for ActiveSync, use this exact syntax: `-BlockLegacyAuthActiveSync:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthAutodiscover +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for Autodiscover, use this switch without a value. +- To allow legacy authentication methods for Autodiscover, use this exact syntax: `-BlockLegacyAuthAutodiscover:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthImap +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for IMAP, use this switch without a value. +- To allow legacy authentication methods for IMAP, use this exact syntax: `-BlockLegacyAuthImap:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthMapi +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for MAPI, use this switch without a value. +- To allow legacy authentication methods for MAPI, use this exact syntax: `-BlockLegacyAuthMapi:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthOfflineAddressBook +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for Offline Address Books, use this switch without a value. +- To allow legacy authentication methods for OfflineAddressBooks, use this exact syntax: `-BlockLegacyAuthOfflineAddressBook:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthPop +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for POP, use this switch without a value. +- To allow legacy authentication methods for POP, use this exact syntax: `-BlockLegacyAuthPop:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthRpc +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for RPC, use this switch without a value. +- To allow legacy authentication methods for RPC, use this exact syntax: `-BlockLegacyAuthRpc:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthWebServices +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. + +- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for EWS, use this switch without a value. +- To allow legacy authentication methods for EWS, use this exact syntax: `-BlockLegacyAuthWebServices:$false`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyExchangeTokens +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. + +Legacy Exchange tokens include Exchange user identity and callback tokens. + +The switch applies to the entire organization. The Identity parameter is required and must be set to the value "LegacyExchangeTokens". Specific authentication policies can't be applied. + +**Important**: + +- Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- It might take up to 24 hours for the change to take effect across your entire organization. +- Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization will remain valid until they expire. +- Blocking legacy Exchange tokens might cause some Microsoft add-ins to stop working. These add-ins are being updated to no longer use legacy tokens. +- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthActiveSync +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthAutodiscover +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthImap +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthMapi +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthOfflineAddressBook +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthPop +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthRpc +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockModernAuthWebServices +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantId +This parameter is available only in the cloud-based service. + +{{ Fill TenantId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md new file mode 100644 index 0000000000..08f50e337c --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md @@ -0,0 +1,933 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AutoSensitivityLabelPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-AutoSensitivityLabelPolicy cmdlet to modify auto-labeling policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Set-AutoSensitivityLabelPolicy [-Identity] + [-AddExchangeLocation ] + [-AddOneDriveLocation ] + [-AddOneDriveLocationException ] + [-AddSharePointLocation ] + [-AddSharePointLocationException ] + [-ApplySensitivityLabel ] + [-AutoEnableAfter ] + [-Comment ] + [-Confirm] + [-Enabled ] + [-ExceptIfOneDriveSharedBy ] + [-ExceptIfOneDriveSharedByMemberOf ] + [-ExchangeAdaptiveScopes ] + [-ExchangeAdaptiveScopesException ] + [-ExchangeSender ] + [-ExchangeSenderException ] + [-ExchangeSenderMemberOf ] + [-ExchangeSenderMemberOfException ] + [-ExternalMailRightsManagementOwner ] + [-Force] + [-Locations ] + [-Mode ] + [-OneDriveAdaptiveScopes ] + [-OneDriveAdaptiveScopesException ] + [-OneDriveSharedBy ] + [-OneDriveSharedByMemberOf ] + [-OverwriteLabel ] + [-PolicyRBACScopes ] + [-PolicyTemplateInfo ] + [-Priority ] + [-RemoveExchangeLocation ] + [-RemoveOneDriveLocation ] + [-RemoveOneDriveLocationException ] + [-RemoveSharePointLocation ] + [-RemoveSharePointLocationException ] + [-SharePointAdaptiveScopes ] + [-SharePointAdaptiveScopesException ] + [-SpoAipIntegrationEnabled ] + [-StartSimulation ] + [-WhatIf] + [] +``` + +### TeamLocation +``` +Set-AutoSensitivityLabelPolicy [-Identity] + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-Mode ] + [-WhatIf] + [] +``` + +### RetryDistributionParameterSet +``` +Set-AutoSensitivityLabelPolicy [-Identity] + [-Confirm] + [-Mode ] + [-RetryDistribution] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AutoSensitivityLabelPolicy -Identity "Main PII" -AddSharePointLocation "https://my.url1/","https://my.url2/" -AddOneDriveLocation "https://my.url3/","https://my.url4/" +``` + +This example adds the specified URLs to the SharePoint and OneDrive locations for the autolabeling policy named Main PII without affecting the existing URL values. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AddExchangeLocation +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: + +- If you use `-AddExchangeLocation All` by itself, the policy applies to email for all internal users. + +- To include email of specific internal or external users in the policy, use `-AddExchangeLocation All` with the ExchangeSender parameter in the same command. Only email of the specified users is included in the policy. + +- To include email of specific group members in the policy, use `-AddExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the policy. + +- To exclude email of specific internal users from the policy, use `-AddExchangeLocation All` with the ExchangeSenderException parameter in the same command. Only email of the specified users is excluded from the policy. + +- To exclude email of specific group members from the policy, use `-AddExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the policy. + +You can't specify inclusions and exclusions in the same policy. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocation +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocation +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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplySensitivityLabel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoEnableAfter +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. + +A valid value is between 1 hour and 25 days. To clear an existing AutoEnableAfter schedule that's associated with a policy, use the value $null. + +You must use this parameter with the -StartSimulation parameter. + +```yaml +Type: System.TimeSpan +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter enables or disables the policy. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity, TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedBy +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: + +- The policy already includes OneDrive sites (in the output of Get-AutoSensitivityLabelPolicy, the OneDriveLocation property value is All, which is the default value). +- Use `-AddOneDriveLocation All` in the same command with this parameter. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the OneDriveSharedBy parameter. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedByMemberOf +{{ Fill ExceptIfOneDriveSharedByMemberOf Description }} + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopes +{{ Fill ExchangeAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopesException +{{ Fill ExchangeAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSender +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: `"","",...""`. + +To use this parameter, one of the following statements must be true: + +- The policy already includes email messages (in the output of the Get-AutoSensitivityLabelPolicy cmdlet, the ExchangeLocation property value is All). +- Use `-AddExchangeLocation All` in the same command with this parameter. + +You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters. + +```yaml +Type: SmtpAddress[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderException +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: `"","",...""`. + +To use this parameter, one of the following statements must be true: + +- The policy already includes email messages (in the output of Get-AutoSensitivityLabelPolicy, the ExchangeLocation property value is All). +- Use `-AddExchangeLocation All` in the same command with this parameter. + +You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters. + +```yaml +Type: SmtpAddress[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOf +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: `"","",...""`. + +To use this parameter, one of the following statements must be true: + +- The policy already includes email messages (in the output of Get-AutoSensitivityLabelPolicy, the ExchangeLocation property value is All). +- Use `-AddExchangeLocation All` in the same command with this parameter. + +You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: SmtpAddress[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOfException +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: `"","",...""`. + +To use this parameter, one of the following statements must be true: + +- The policy already includes email messages (in the output of Get-AutoSensitivityLabelPolicy, the ExchangeLocation property value is All). +- Use `-AddExchangeLocation All` in the same command with this parameter. + +You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: SmtpAddress[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalMailRightsManagementOwner +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. + +To clear an existing email address, use the value $null. + +```yaml +Type: SmtpAddress +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locations +{{ Fill Locations Description }} + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mode +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. +- Disable: The policy is disabled. +- TestWithNotifications: Not supported. +- TestWithoutNotifications: An audit mode where no actions are taken, and no notifications are sent (Test mode). + +```yaml +Type: PolicyMode +Parameter Sets: (All) +Aliases: +Accepted values: Enable, TestWithNotifications, TestWithoutNotifications, Disable, PendingDeletion +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopes +{{ Fill OneDriveAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopesException +{{ Fill OneDriveAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedBy +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: + +- The policy already includes OneDrive sites (in the output of Get-AutoSensitivityLabelPolicy, the OneDriveLocation property value is All, which is the default value). +- Use `-AddOneDriveLocation All` in the same command with this parameter. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the ExceptIfOneDriveSharedBy parameter. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedByMemberOf +{{ Fill OneDriveSharedByMemberOf Description }} + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverwriteLabel +The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are: + +- $true: Overwrite the manual label. +- $false: Don't overwrite the manual label. This is the default value. + +This parameter works only on Exchange locations. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTemplateInfo +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 5 policies are from 0 through 4. +- Valid priority values for a new 6th policy are from 0 through 5. +- The default value for a new 6th policy is 5. + +If you modify the priority value of a policy, the position of the policy in the list changes to match the priority value you specify. In other words, if you set the priority value of a policy to the same value as an existing policy, the priority value of the existing policy and all other lower priority policies after it is increased by 1. + +```yaml +Type: System.Int32 +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +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. + +You can't use this parameter if email (the value Exchange) is used by any of the associated rules. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocation +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocation +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetryDistribution +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. + +**Note**: Because the process of retrying distribution is a significant operation, run it only if necessary and for one policy at a time. It is not intended to be run every time you update a policy. If you run a script to update multiple policies, wait until the policy distribution is successful before running the command again for the next policy. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistributionParameterSet +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopes +{{ Fill SharePointAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopesException +{{ Fill SharePointAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpoAipIntegrationEnabled +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. +- $false: Users can't apply your sensitivity labels in Office for the web. Also, coauthoring, eDiscovery, Microsoft Purview data loss prevention, search, and other collaborative features don't work for encrypted files. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartSimulation +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.** +- $false: This is the default value + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md new file mode 100644 index 0000000000..f477c1b30d --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md @@ -0,0 +1,1265 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AutoSensitivityLabelRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-AutoSensitivityLabelPolicy cmdlet to modify auto-labeling policy rules in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AutoSensitivityLabelRule [-Identity] + [-AccessScope ] + [-ActivationDate ] + [-AnyOfRecipientAddressContainsWords ] + [-AnyOfRecipientAddressMatchesPatterns ] + [-Comment ] + [-Confirm] + [-ContentContainsSensitiveInformation ] + [-ContentExtensionMatchesWords ] + [-ContentPropertyContainsWords ] + [-DefaultSpoDocLibraryHasLabel ] + [-Disabled ] + [-DocumentCreatedBy ] + [-DocumentIsPasswordProtected ] + [-DocumentIsUnsupported ] + [-DocumentNameMatchesWords ] + [-DocumentSizeOver ] + [-ExceptIfAccessScope ] + [-ExceptIfAnyOfRecipientAddressContainsWords ] + [-ExceptIfAnyOfRecipientAddressMatchesPatterns ] + [-ExceptIfContentContainsSensitiveInformation ] + [-ExceptIfContentExtensionMatchesWords ] + [-ExceptIfContentPropertyContainsWords ] + [-ExceptIfDocumentCreatedBy ] + [-ExceptIfDocumentIsPasswordProtected ] + [-ExceptIfDocumentIsUnsupported ] + [-ExceptIfDocumentNameMatchesWords ] + [-ExceptIfDocumentSizeOver ] + [-ExceptIfFrom ] + [-ExceptIfFromAddressContainsWords ] + [-ExceptIfFromAddressMatchesPatterns ] + [-ExceptIfFromMemberOf ] + [-ExceptIfHeaderMatchesPatterns ] + [-ExceptIfProcessingLimitExceeded ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSenderDomainIs ] + [-ExceptIfSenderIPRanges ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-ExceptIfSubjectMatchesPatterns ] + [-ExpiryDate ] + [-From ] + [-FromAddressContainsWords ] + [-FromAddressMatchesPatterns ] + [-FromMemberOf ] + [-HeaderMatchesPatterns ] + [-Priority ] + [-ProcessingLimitExceeded ] + [-RecipientDomainIs ] + [-ReportSeverityLevel ] + [-RuleErrorAction ] + [-SenderDomainIs ] + [-SenderIPRanges ] + [-SentTo ] + [-SentToMemberOf ] + [-SourceType ] + [-SubjectMatchesPatterns ] + [-WhatIf] + [-Workload ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AutoSensitivityLabelRule -Identity "SocialSecurityRule1" -Comment "Example" +``` + +This example changes the rule property "Comment" with the rule name "SocialSecurityRule1" to the text "Example". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AccessScope +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. +- NotInOrganization: The rule is applied to content that's accessible outside the organization. +- None: The condition isn't used. + +```yaml +Type: AccessScope +Parameter Sets: (All) +Aliases: +Accepted values: InOrganization, NotInOrganization, None +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActivationDate +{{ Fill ActivationDate Description }} + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressMatchesPatterns +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. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})`. + +Exact Data Match sensitive types are not supported outside of Groups. + +To use groups: `@(@{operator="And"; groups=@(@{name="Default"; operator="Or"; sensitivetypes=@(@{id="<>"; name="<>"; maxcount="-1"; classifiertype="ExactMatch"; mincount="100"; confidencelevel="Medium"})})})` + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultSpoDocLibraryHasLabel +{{ Fill DefaultSpoDocLibraryHasLabel Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: + +- $true: The rule is disabled. +- $false: The rule is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentCreatedBy +{{ Fill DocumentCreatedBy Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` + +The maximum individual word length is 128 characters. The maximum number of words is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this condition in auto-labeling policy rules that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAccessScope +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. +- NotInOrganization: The rule isn't applied to content that's accessible outside the organization. +- None: The exception isn't used. + +```yaml +Type: AccessScope +Parameter Sets: (All) +Aliases: +Accepted values: InOrganization, NotInOrganization, None +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressMatchesPatterns +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. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentContainsSensitiveInformation +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"})`. + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentCreatedBy +{{ Fill ExceptIfDocumentCreatedBy Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this exception in auto-labeling policy rules that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFrom +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressMatchesPatterns +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. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromMemberOf +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"`. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectMatchesPatterns +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. + +You can use this exception in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpiryDate +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -From +This parameter is reserved for internal Microsoft use. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressMatchesPatterns +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. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromMemberOf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportSeverityLevel +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. +- Low: This is the default value. +- Medium +- High + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Accepted values: Low, Medium, High, None, Informational, Information +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RuleErrorAction +The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: + +- Ignore +- RetryThenBlock +- Blank (the value $null): This is the default value. + +```yaml +Type: PolicyRuleErrorAction +Parameter Sets: (All) +Aliases: +Accepted values: Ignore, RetryThenBlock +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +You can use this condition in auto-sensitivity policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceType +{{ Fill SourceType Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectMatchesPatterns +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. + +You can use this condition in auto-labeling policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Workload +The Workload parameter specifies the workload. Valid values are: + +- Exchange +- OneDriveForBusiness +- SharePoint + +```yaml +Type: Workload +Parameter Sets: (All) +Aliases: +Accepted values: Exchange, SharePoint, OneDriveForBusiness +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-AutodiscoverVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access-servers/Set-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/exchange/Set-AutodiscoverVirtualDirectory.md index 44514026ba..21d6376337 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Set-AutodiscoverVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-autodiscovervirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-AutodiscoverVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-AutodiscoverVirtualDirectory cmdlet to configure Autodiscover virtual directories that are used in Internet Information Services (IIS) on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -40,7 +39,7 @@ Set-AutodiscoverVirtualDirectory [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,13 +69,11 @@ This example sets Integrated Windows authentication for the Autodiscover virtual ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -95,7 +92,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. ```yaml @@ -114,8 +110,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -135,7 +130,6 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. - - $false: Digest authentication is disabled. This is the default value. ```yaml @@ -171,13 +165,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -197,8 +187,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -217,14 +206,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -240,7 +225,7 @@ Accept wildcard characters: False ``` ### -ExternalUrl -This parameter is available or functional only in 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. @@ -258,7 +243,7 @@ Accept wildcard characters: False ``` ### -InternalUrl -This parameter is available or functional only in 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. @@ -279,7 +264,6 @@ Accept wildcard characters: False 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. - - $false: OAuth authentication is disabled. ```yaml @@ -315,7 +299,6 @@ Accept wildcard characters: False 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. - - $false: Integrated Windows authentication is disabled. ```yaml @@ -335,7 +318,6 @@ Accept wildcard characters: False 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. - - $false: WS-Security authentication is disabled. ```yaml @@ -356,12 +338,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-AvailabilityConfig.md b/exchange/exchange-ps/exchange/Set-AvailabilityConfig.md new file mode 100644 index 0000000000..7fc266524e --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-AvailabilityConfig.md @@ -0,0 +1,224 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-AvailabilityConfig + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-AvailabilityConfig cmdlet to set the access level for free/busy information. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-AvailabilityConfig + [-AllowedTenantIds ] + [-Confirm] + [-DomainController ] + [-OrgWideAccount ] + [-PerUserAccount ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Set-AvailabilityConfig cmdlet defines two accounts or security groups: a per-user free/busy proxy account or group, and an organization-wide free/busy proxy account or group. These accounts and groups are trusted by all availability services in the current organization for availability proxy requests. + +For cross-forest availability services to retrieve free/busy information in the current forest, they must be using one of the specified accounts, belong to one of the specified security groups, or have a username and password for one of the specified accounts or security groups. + +In Exchange Online, this cmdlet lets you update the set of tenant ids that free/busy information sharing is allowed with. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-AvailabilityConfig -PerUserAccount exchangeserversgroup@fabrikam.com +``` + +In on-premises Exchange, this example is useful with a trusted cross-forest Availability service. If the remote forest is trusted, and a per-user free/busy proxy account or group in the remote forest is configured to use the service account, the configuration is added to the current forest to authorize the Microsoft ActiveSync request from the remote forest. + +### Example 2 +```powershell +Set-AvailabilityConfig -OrgWideAccount orgwide@contoso.com +``` + +In on-premises Exchange, this example is useful if the remote forest isn't trusted. Because this account is used for a cross-forest free/busy proxy account or group, minimize security vulnerabilities by using the credentials of a user who doesn't have an Exchange mailbox. When you're prompted, type the username and password. + +### Example 3 +```powershell +Set-AvailabilityConfig -AllowedTenantIds "d6b0a40e-029b-43f2-9852-f3724f68ead9","87d5bade-cefc-4067-a221-794aea71922d" +``` + +In Exchange Online, this example allows free/busy sharing only with the specified tenants. + +## PARAMETERS + +### -AllowedTenantIds +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. + +To replace all existing tenant IDs with the values you specify, use the following syntax: `"TenantID1","TenantID2",..."TenantID25"`. + +To add or remove tenant IDs without affecting other existing values, use the following syntax: `@{Add="TenantID1","TenantID2",...; Remove="TenantID3","TenantID4",...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrgWideAccount +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: + +- Mailbox users +- Mail users +- Security groups + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PerUserAccount +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. + +You can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/server-health-and-performance/Set-AvailabilityReportOutage.md b/exchange/exchange-ps/exchange/Set-AvailabilityReportOutage.md similarity index 86% rename from exchange/exchange-ps/exchange/server-health-and-performance/Set-AvailabilityReportOutage.md rename to exchange/exchange-ps/exchange/Set-AvailabilityReportOutage.md index 2e9a514e11..051ad1654f 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Set-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/exchange/Set-AvailabilityReportOutage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/set-availabilityreportoutage +online version: https://learn.microsoft.com/powershell/module/exchange/set-availabilityreportoutage applicable: Exchange Server 2010 title: Set-AvailabilityReportOutage schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-AvailabilityReportOutage @@ -17,32 +16,36 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-AvailabilityReportOutage cmdlet to set the outages that contribute to the overall reported availability for the day. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity (Default) ``` -Set-AvailabilityReportOutage [-Identity] -Comment -ReportDate [-DowntimeMinutes ] +Set-AvailabilityReportOutage [-Identity] -Comment -ReportDate + [-DowntimeMinutes ] [-Confirm] [-Force] [-ReportingDatabase ] [-ReportingServer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ResetToOriginal ``` -Set-AvailabilityReportOutage [-Identity] -ReportDate [-ResetToOriginal] +Set-AvailabilityReportOutage [-Identity] -ReportDate + [-ResetToOriginal] [-Confirm] [-Force] [-ReportingDatabase ] [-ReportingServer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,35 +58,35 @@ This example overrides the specified outage with a new downtime value of 40 minu ## PARAMETERS -### -Comment -The Comment parameter describes the outage that was inserted. +### -Identity +The Identity parameter specifies the outage to add to the outage reporting. ```yaml -Type: String -Parameter Sets: Identity +Type: AvailabilityReportOutageIdParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the outage to add to the outage reporting. +### -Comment +The Comment parameter describes the outage that was inserted. ```yaml -Type: AvailabilityReportOutageIdParameter -Parameter Sets: (All) +Type: String +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -104,7 +107,7 @@ Accept wildcard characters: False ``` ### -ResetToOriginal -The ResetToOriginal parameter specifies whether to reset the previously selected outage value to the default value. +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 @@ -122,8 +125,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -156,7 +158,9 @@ Accept wildcard characters: False ``` ### -Force -The Force parameter suppresses the warning or confirmation messages that appear during specific configuration changes. +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. ```yaml Type: SwitchParameter @@ -224,12 +228,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Set-CASMailbox.md b/exchange/exchange-ps/exchange/Set-CASMailbox.md new file mode 100644 index 0000000000..6ff7e5c704 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-CASMailbox.md @@ -0,0 +1,1314 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-CASMailbox + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-CASMailbox cmdlet to configure client access settings on a mailbox. For example, you can configure settings for Exchange ActiveSync, Outlook, Outlook on the web, POP3, and IMAP4. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-CASMailbox [-Identity] + [-ActiveSyncAllowedDeviceIDs ] + [-ActiveSyncBlockedDeviceIDs ] + [-ActiveSyncDebugLogging ] + [-ActiveSyncEnabled ] + [-ActiveSyncMailboxPolicy ] + [-ActiveSyncSuppressReadReceipt ] + [-Confirm] + [-DisplayName ] + [-DomainController ] + [-ECPEnabled ] + [-EmailAddresses ] + [-EwsAllowEntourage ] + [-EwsAllowList ] + [-EwsAllowMacOutlook ] + [-EwsAllowOutlook ] + [-EwsApplicationAccessPolicy ] + [-EwsBlockList ] + [-EwsEnabled ] + [-HasActiveSyncDevicePartnership ] + [-IgnoreDefaultScope] + [-ImapEnabled ] + [-ImapEnableExactRFC822Size ] + [-ImapMessagesRetrievalMimeFormat ] + [-ImapForceICalForCalendarRetrievalOption ] + [-ImapSuppressReadReceipt ] + [-ImapUseProtocolDefaults ] + [-IsOptimizedForAccessibility ] + [-MacOutlookEnabled ] + [-MAPIBlockOutlookExternalConnectivity ] + [-MAPIBlockOutlookNonCachedMode ] + [-MAPIBlockOutlookRpcHttp ] + [-MAPIBlockOutlookVersions ] + [-MAPIEnabled ] + [-MapiHttpEnabled ] + [-Name ] + [-OneWinNativeOutlookEnabled ] + [-OutlookMobileEnabled ] + [-OWAEnabled ] + [-OWAforDevicesEnabled ] + [-OwaMailboxPolicy ] + [-PopEnabled ] + [-PopEnableExactRFC822Size ] + [-PopForceICalForCalendarRetrievalOption ] + [-PopMessagesRetrievalMimeFormat ] + [-PopSuppressReadReceipt ] + [-PopUseProtocolDefaults ] + [-PrimarySmtpAddress ] + [-PublicFolderClientAccess ] + [-ResetAutoBlockedDevices] + [-SamAccountName ] + [-ShowGalAsDefaultView ] + [-SmtpClientAuthenticationDisabled ] + [-UniversalOutlookEnabled ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-CASMailbox adam@contoso.com -OWAEnabled $false -PopEnabled $false +``` + +This example disables Outlook on the web and POP3 access for the user adam@contoso.com. + +### Example 2 +```powershell +Set-CASMailbox adam@contoso.com -ActiveSyncDebugLogging $true -ActiveSyncMailboxPolicy Management +``` + +This example enables Exchange ActiveSync debug logging and specifies the Exchange ActiveSync mailbox policy named Management for the user adam@contoso.com. + +### Example 3 +```powershell +Set-CASMailbox tony@contoso.com -DisplayName "Tony Smith" -MAPIBlockOutlookRpcHttp $true +``` + +This example sets the display name and disables Outlook Anywhere access for the user tony@contoso.com. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to configure. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ActiveSyncAllowedDeviceIDs +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +To clear the list of device IDs, use the value $null for this parameter. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActiveSyncBlockedDeviceIDs +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +To clear the list of device IDs, use the value $null for this parameter. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActiveSyncDebugLogging +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. +- $false: ActiveSync debug logging is disabled. This is the default value + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActiveSyncEnabled +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. +- $false. Access to the mailbox using ActiveSync is disabled. Other ActiveSync settings in this cmdlet are ignored. + +For more information, see [Enable or disable Exchange ActiveSync for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-exchange-activesync), or [Enable or disable Exchange ActiveSync access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/exchange-activesync/activesync-mailbox-access). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActiveSyncMailboxPolicy +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 +- Distinguished name (DN) +- GUID + +The name of the default Exchange ActiveSync mailbox policy is Default. However, to reset this parameter back to the default value, use the value $null. The value $null also changes the value of the ActiveSyncMailboxPolicyIsDefaulted property to True. If you specify the value Default for the ActiveSyncMailboxPolicy parameter, the value of the ActiveSyncMailboxPolicyIsDefaulted property remains False. + +```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: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActiveSyncSuppressReadReceipt +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. +- $false: A read receipt is automatically returned when the user opens a message sent with a read receipt request. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 ("). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ECPEnabled +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: + +- $true: Access to the EAC or ECP is enabled. This is the default value. +- $false: Access to the EAC or ECP is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailAddresses +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). + +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: + +- SMTP: The primary SMTP address. You can use this value only once in a command. +- smtp: Other SMTP email addresses. +- X400: X.400 addresses in on-premises Exchange. +- X500: X.500 addresses in on-premises Exchange. + +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. + +To specify the primary SMTP email address, you can use any of the following methods: + +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. +- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. + +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. + +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. + +```yaml +Type: ProxyAddressCollection +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowEntourage +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. +- $false: Access to the mailbox using Microsoft Entourage is disabled. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowList +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +This parameter is meaningful only when the EwsEnabled parameter is set to $true, and the EwsApplicationAccessPolicy parameter is set to EnforceAllowList. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowMacOutlook +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. +- $false: Outlook for Mac clients that use EWS are not allowed to access the mailbox. + +In the cloud-based service, access for Outlook for Mac clients that use Microsoft Sync technology is controlled by the MacOutlookEnabled 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowOutlook +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. +- $false: Access to the mailbox using EWS in Outlook client is disabled. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsApplicationAccessPolicy +The EwsApplicationAccessPolicy parameter controls access to the mailbox using Exchange Web Services applications. + +Valid values for this parameter are: + +- EnforceAllowList: Only applications specified in the EwsAllowList parameter are allowed to access the mailbox. +- EnforceBlockList: Applications specified in the EwsBlockList parameter aren't allowed to access the mailbox, but any other applications can access the mailbox. + +This parameter doesn't affect access to the mailbox using Entourage, Outlook for Mac, and Outlook. Access to the mailbox using these clients is controlled by the EwsAllowEntourage, EwsAllowMacOutlook and EwsAllowOutlook parameters. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsBlockList +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +This parameter is meaningful only when the EwsEnabled parameter is set to $true, and the EwsApplicationAccessPolicy parameter is set to EnforceBlockList. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsEnabled +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. +- $false: Access to the mailbox using EWS is disabled. Other Exchange Web Services settings in this cmdlet are ignored. + +The value of this parameter is meaningful only if the EwsEnabled parameter on the Set-OrganizationConfig parameter isn't set to the value $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 +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HasActiveSyncDevicePartnership +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: + +- $true: The mailbox has an ActiveSync device partnership. +- $false: The mailbox does not have an ActiveSync device partnership. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImapEnabled +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. +- $fale: Access to the mailbox using IMAP4 is disabled. The other IMAP4 settings in this cmdlet are ignored. + +For more information, see [Enable or Disable POP3 or IMAP4 access for a user in Exchange Online](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/pop3-and-imap4/enable-or-disable-pop3-or-imap4-access), or [Enable or disable POP3 or IMAP4 access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/pop3-and-imap4/configure-mailbox-access). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImapEnableExactRFC822Size +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: + +- $true: Calculate the exact message size. +- $false: Use an estimated message size. This is the default value. + +We don't recommend changing this value unless you determine that the default setting causes problems for IMAP4 clients. To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImapForceICalForCalendarRetrievalOption +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. +- $false: All meeting requests appear as Outlook on the web links. This is the default value. + +To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImapMessagesRetrievalMimeFormat +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 +- 1: HtmlOnly +- 2: HtmlAndTextAlternative +- 3: TextEnrichedOnly +- 4: TextEnrichedAndTextAlternative +- 5: BestBodyFormat (this is the default value) +- 6: Tnef + +To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImapSuppressReadReceipt +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. +- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This is the default value. + +To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImapUseProtocolDefaults +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. +- $false: Use custom protocol settings for IMAP4 access to the mailbox. + +You need to set this parameter to $false when you use any of the following IMAP4 parameters: + +- ImapEnableExactRFC822Size +- ImapForceICalForCalendarRetrievalOption +- ImapMessagesRetrievalMimeFormat +- ImapSuppressReadReceipt + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsOptimizedForAccessibility +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: + +- $true: The mailbox is configured to use the light version of Outlook on the web. +- $false: The mailbox isn't configured to use the light version of Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MacOutlookEnabled +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: + +- $true: Access to the mailbox using Outlook for Mac clients is enabled. This is the default value. +- $false: Access to the mailbox using Outlook for Mac clients is disabled. + +Access for older Outlook for Mac clients that use Exchange Web Services is controlled by the EwsAllowMacOutlook parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MAPIBlockOutlookNonCachedMode +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: + +- $true: Only Outlook clients that are configured to use Cached Exchange Mode (offline mode) are allowed to access the mailbox. +- $false: The state of the Cached Exchange Mode setting isn't checked before Outlook clients are allowed to access the mailbox (online mode and offline mode are allowed). This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MAPIBlockOutlookExternalConnectivity +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: + +- $true: External Outlook clients can't use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox. +- $false: External Outlook clients can use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox. + +**Note**: If your organization uses the same Autodiscover URL values for internal and external clients, setting this parameter to $true won't block access for external clients. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MAPIBlockOutlookRpcHttp +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: + +- $true: Access to the mailbox using Outlook Anywhere is disabled. +- $false: Access to the mailbox using Outlook Anywhere is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MAPIBlockOutlookVersions +This parameter is available only in on-premises Exchange. + +The MAPIBlockOutlookVersions parameter blocks access to the mailbox for specific versions of Outlook. + +For example, if you specify the value 15.0.4569, only Outlook 2013 Service Pack 1 (SP1) or later clients are allowed to access the mailbox. Earlier versions of Outlook are blocked. + +The default value is blank. To reset this parameter, use the value $null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MAPIEnabled +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. +- $false: Access to the mailbox using MAPI clients is disabled. The other MAPI settings in this cmdlet are ignored. + +For more information, see[Enable or disable MAPI for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-mapi), or [Enable or disable MAPI access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/mapi-mailbox-access). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MapiHttpEnabled +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: + +- $true: Access to the mailbox using MAPI over HTTP is enabled. +- $false: Access to the mailbox using MAPI over HTTP is disabled. +- $null (blank): The setting isn't configured. The mailbox uses the organization setting for MAPI over HTTP (the MapiHttpEnabled parameter on the Set-OrganizationConfig cmdlet). This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 ("). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneWinNativeOutlookEnabled +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. +Valid values are: + +- $true: Access to the mailbox using the new Outlook for Windows is enabled. This is the default value. +- $false: Access to the mailbox using the new Outlook for Windows is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookMobileEnabled +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: + +- $true: Access to the mailbox using Outlook for iOS and Android is enabled. This is the default value. +- $false: Access to the mailbox using Outlook for iOS and Android is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OWAEnabled +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. +- $false: Access to the mailbox using Outlook on the web and the new Outlook for Windows is disabled. The other Outlook on the web settings in this cmdlet are ignored. + +For more information, see [Enable or disable Outlook on the web for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-outlook-web-app), or [Enable or disable Outlook on the web access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/outlook-on-the-web/mailbox-access). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OWAforDevicesEnabled +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. +- $false: Access to the mailbox using OWA for Devices is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OwaMailboxPolicy +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 +- Distinguished name (DN) +- GUID + +The name of the default Outlook on the web mailbox policy is Default. + +```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: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopEnabled +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. +- $false: Access to the mailbox using POP3 clients is disabled. The other POP3 settings in this cmdlet are ignored. + +For more information, see [Enable or Disable POP3 or IMAP4 access for a user in Exchange Online](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/pop3-and-imap4/enable-or-disable-pop3-or-imap4-access), or [Enable or disable POP3 or IMAP4 access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/pop3-and-imap4/configure-mailbox-access). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopEnableExactRFC822Size +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: + +- $true: Calculate the exact message size. +- $false: Use an estimated message size. This is the default value + +We don't recommend changing this value unless you determine that the default setting causes problems for POP3 clients. To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopForceICalForCalendarRetrievalOption +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. +- $false: All meeting requests appear as Outlook on the web links. This is the default value. + +To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopMessagesRetrievalMimeFormat +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 +- 1: HtmlOnly +- 2: HtmlAndTextAlternative +- 3: TextEnrichedOnly +- 4: TextEnrichedAndTextAlternative +- 5: BestBodyFormat (this is the default value) +- 6: Tnef + +To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopSuppressReadReceipt +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. +- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This is the default value. + +To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopUseProtocolDefaults +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. +- $false: Use custom protocol settings for POP3 access to the mailbox. + +You need to set this parameter to $false when you use any of following parameters: + +- PopEnableExactRFC822Size +- PopForceICalForCalendarRetrievalOption +- PopMessagesRetrievalMimeFormat +- PopSuppressReadReceipt + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +```yaml +Type: SmtpAddress +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderClientAccess +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). +- $false: The user can't access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResetAutoBlockedDevices +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SamAccountName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowGalAsDefaultView +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. +- $false: Don't use the GAL as the primary address picker. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SmtpClientAuthenticationDisabled +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: + +- POP3 and IMAP4 clients. +- Devices with scan to email capability. +- Workflow applications that send email notifications. +- Online services that send messages using internal email addresses in the organization. + +Valid values for this parameter are: + +- $true: Authenticated SMTP is disabled for the mailbox. +- $false: Authenticated SMTP is enabled for the mailbox. +- blank ($null): This is the default value. The authenticated SMTP setting for the mailbox is controlled by the corresponding SmtpClientAuthenticationDisabled parameter on the Set-TransportConfig cmdlet for the whole organization. + +To selectively enable authenticated SMTP for specific mailboxes only: disable authenticated SMTP at the organizational level ($true), enable it for the specific mailboxes ($false), and leave the rest of the mailboxes with their default value ($null). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UniversalOutlookEnabled +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: + +- $true: Access to the mailbox using Windows 10 Mail and Calendar is enabled. This is the default value. +- $false: Access to the mailbox using Windows 10 Mail and Calendar is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-CASMailboxPlan.md b/exchange/exchange-ps/exchange/Set-CASMailboxPlan.md new file mode 100644 index 0000000000..5901e16225 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-CASMailboxPlan.md @@ -0,0 +1,265 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-CASMailboxPlan + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-CASMailboxPlan cmdlet to modify Client Access services (CAS) mailbox plans in cloud-based organizations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-CASMailboxPlan [-Identity] + [-ActiveSyncEnabled ] + [-Confirm] + [-ECPEnabled ] + [-EwsEnabled ] + [-ImapEnabled ] + [-MAPIEnabled ] + [-OWAEnabled ] + [-OwaMailboxPolicy ] + [-PopEnabled ] + [-WhatIf] + [] +``` + +## DESCRIPTION +A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-CASMailboxPlan -Identity ExchangeOnlineEnterprise -ActiveSyncEnabled $false -PopEnabled $false +``` + +This example disables Exchange ActiveSync and POP3 access to mailboxes in the CAS mailbox plan named ExchangeOnlineEnterprise. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +The display name and name of the CAS mailbox plan is the same as the corresponding mailbox plan (for example, `ExchangeOnlineEnterprise` and `ExchangeOnlineEnterprise-`, respectively). + +```yaml +Type: MailboxPlanIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ActiveSyncEnabled +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. +- $false: ActiveSync access to the mailbox is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ECPEnabled +{{ Fill ECPEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsEnabled +{{ Fill EwsEnabled Description }} + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImapEnabled +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. +- $false: IMAP4 access to the mailbox is disabled. This is default value for ExchangeOnlineDeskless. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MAPIEnabled +{{ Fill MAPIEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OWAEnabled +{{ Fill OWAEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OwaMailboxPolicy +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 +- Distinguished name (DN) +- GUID + +The default value is OwaMailboxPolicy-Default. + +You can use the Get-OwaMailboxPolicy cmdlet to view the available Outlook on the web mailbox policies. + +```yaml +Type: MailboxPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopEnabled +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. +- $false: POP3 access to the mailbox is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-CalendarNotification.md b/exchange/exchange-ps/exchange/Set-CalendarNotification.md new file mode 100644 index 0000000000..29fe0d712f --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-CalendarNotification.md @@ -0,0 +1,301 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-CalendarNotification + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +The Set-CalendarNotification cmdlet allows users to set text message notification options for calendar events in their own calendar. By default, the MyTextMessaging end-user role gives access to this cmdlet, so admins can't configure text messaging notification for calendar events in user calendars. + +**Note**: This cmdlet has been deprecated in Exchange Online PowerShell. The text message notification service has been discontinued in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-CalendarNotification [-Identity] + [-CalendarUpdateNotification ] + [-CalendarUpdateSendDuringWorkHour ] + [-Confirm] + [-DailyAgendaNotification ] + [-DailyAgendaNotificationSendTime ] + [-DomainController ] + [-IgnoreDefaultScope] + [-MeetingReminderNotification ] + [-MeetingReminderSendDuringWorkHour ] + [-NextDays ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Users can receive text message notifications of changes to calendar events and daily agendas. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-CalendarNotification -Identity "TonySmith" -CalendarUpdateNotification $true -MeetingReminderNotification $true -MeetingReminderSendDuringWorkHour $true -DailyAgendaNotification $true +``` + +This example configures the calendar in Tony's mailbox to send the following text message notifications to his mobile device: + +- Calendar updates. +- Meeting reminders during business hours. +- Daily agendas. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CalendarUpdateNotification +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. +- $false: Calendar update text message notifications aren't enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CalendarUpdateSendDuringWorkHour +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. +- $false: Calendar update text message notifications are sent anytime. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DailyAgendaNotification +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. +- $false: Daily agenda text message notifications aren't sent. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DailyAgendaNotificationSendTime +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. + +The default value is 08:00:00. + +```yaml +Type: TimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingReminderNotification +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. +- $false: Meeting reminder text message notifications aren't sent. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingReminderSendDuringWorkHour +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. +- $false: Meeting update notifications are sent anytime. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NextDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Set-CalendarProcessing.md b/exchange/exchange-ps/exchange/Set-CalendarProcessing.md similarity index 82% rename from exchange/exchange-ps/exchange/mailboxes/Set-CalendarProcessing.md rename to exchange/exchange-ps/exchange/Set-CalendarProcessing.md index d14630cc25..edc2b0bc9a 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-CalendarProcessing.md +++ b/exchange/exchange-ps/exchange/Set-CalendarProcessing.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-calendarprocessing -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-CalendarProcessing @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-CalendarProcessing cmdlet to modify calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant, and calendar configuration. Note that this cmdlet is effective only on resource mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -43,14 +42,19 @@ Set-CalendarProcessing [-Identity] [-DeleteNonCalendarItems ] [-DeleteSubject ] [-DomainController ] + [-EnableAutoRelease ] [-EnableResponseDetails ] + [-EnforceCapacity ] [-EnforceSchedulingHorizon ] [-ForwardRequestsToDelegates ] [-IgnoreDefaultScope] [-MaximumConflictInstances ] [-MaximumDurationInMinutes ] + [-MinimumDurationInMinutes ] [-OrganizerInfo ] + [-PostReservationMaxClaimTimeInMinutes ] [-ProcessExternalMeetingMessages ] + [-RemoveCanceledMeetings ] [-RemoveForwardedMeetingNotifications ] [-RemoveOldMeetingMessages ] [-RemovePrivateProperty ] @@ -59,11 +63,12 @@ Set-CalendarProcessing [-Identity] [-ResourceDelegates ] [-ScheduleOnlyDuringWorkHours ] [-TentativePendingApproval ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -109,16 +114,39 @@ Set-CalendarProcessing -Identity "Car 53" -AutomateProcessing AutoAccept -BookIn This example allows a list of users to submit in-policy meeting requests to the equipment mailbox for Car 53. +The users you specify for the BookInPolicy using this syntax overwrite any existing values. + ### Example 7 ```powershell +$CurrentBIP = (Get-CalendarProcessing -Identity "Conference Room 1").BookInPolicy + +$AddToBIP = "shiraz@contoso.com","chris@contoso.com" + +$UpdatedBIP = $CurrentBIP + $AddToBIP + +Set-CalendarProcessing -Identity "Conference Room 1" -BookInPolicy $UpdatedBIP +``` + +This example adds Shiraz and Chris to the BookInPolicy of the room mailbox named Conference Room 1 without affecting any existing BookInPolicy values. + +The first command retrieves the current BookInPolicy values of Conference Room 1 and stores them in a variable. + +The next two commands identify the new users to add to the BookInPolicy, combine the old and new values, and store the updated list a variable. + +The last command updates the BookInPolicy value with the combined list. + +### Example 8 +```powershell $group = New-DistributionGroup "Room 221 Booking Allowed" + Update-DistributionGroupMember -Identity $group.Identity -Members karina@contoso.com,tony@contoso.com -BypassSecurityGroupManagerCheck:$true + Set-CalendarProcessing -Identity "Room 221" -AutomateProcessing AutoAccept -BookInPolicy $group.Identity -AllBookInPolicy $false ``` This example rejects meeting requests from any user who isn't a member of the "Room 221 Booking Allowed" distribution group. -### Example 8 +### Example 9 ```powershell Set-CalendarProcessing -Identity "Room 221" -ProcessExternalMeetingMessages $false ``` @@ -131,30 +159,21 @@ This example rejects meeting requests from any user who isn't a member of the Ex 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -167,7 +186,6 @@ Accept wildcard characters: False 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. - - $false: No additional text is added to meeting request responses (any text in the AddAdditionalResponse parameter isn't used). This is the default value. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -205,7 +223,6 @@ Accept wildcard characters: False 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. - - $false: Only existing calendar items are updated by the Calendar Attendant. ```yaml @@ -225,11 +242,12 @@ Accept wildcard characters: False 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. - - $false: The original Subject value is preserved. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. +**Note**: Default Calendar folder permissions use the AvailabilityOnly role, which doesn't allow viewing Subject fields in meeting requests. At a minimum, the LimitedDetails role is required to view Subject fields in meeting requests. Use the **\*-MailboxFolderPermission** cmdlets to manage mailbox folder permissions. + ```yaml Type: Boolean Parameter Sets: (All) @@ -247,7 +265,6 @@ Accept wildcard characters: False 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. - - $false: In-policy requests from all users aren't automatically approved (approval by a delegate is required). ```yaml @@ -266,9 +283,12 @@ Accept wildcard characters: False ### -AllowConflicts The AllowConflicts parameter specifies whether to allow conflicting meeting requests. Valid values are: -- $true: Conflicts are allowed. +- $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. +- $false: Conflicts aren't allowed. This is the default value. Whether an entire series is declined depends on the amount of conflicts in the series: + + • The series is declined if the number or percentage of conflicts is higher than the ConflictPercentageAllowed or MaximumConflictInstances parameter values. -- $false: Conflicts aren't allowed. This is the default value. + • The series is accepted, but conflicting occurrences are declined if the number or percentage of conflicts is lower than the ConflictPercentageAllowed or MaximumConflictInstances parameter values. If the EnableResponseDetails parameter value is $true, the organizer will receive a notification email for each declined occurrence. ```yaml Type: Boolean @@ -287,7 +307,6 @@ Accept wildcard characters: False 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. - - $false: Recurring meetings aren't allowed. ```yaml @@ -306,8 +325,7 @@ Accept wildcard characters: False ### -AllRequestInPolicy 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 is $true). - +- $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). - $false: All users can't submit in-policy requests to the resource mailbox. This is the default value. ```yaml @@ -327,7 +345,6 @@ Accept wildcard characters: False 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. - - $false: All users can't submit out-of-policy requests to the resource mailbox. This is the default value. ```yaml @@ -347,9 +364,7 @@ Accept wildcard characters: False 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. - - AutoUpdate: Only the Calendar Attendant processes meeting requests and responses. Meeting requests are tentative in the calendar until they're approved by a delegate. Meeting organizers receive only decisions from delegates. - - AutoAccept: Both the Calendar Attendant and resource booking attendant are enabled on the mailbox. This means that the Calendar Attendant updates the calendar, and then the resource booking assistant accepts the meeting based upon the policies. Eligible meeting organizers receive the decision directly without human intervention (free = accept; busy = decline). In on-premises Exchange, resource mailboxes created in the Exchange admin center (EAC) have the default value AutoAccept, while resource mailboxes created in PowerShell have the default value AutoUpdate. @@ -377,7 +392,6 @@ This parameter is available only in the cloud-based service. The BookingType parameter specifies how reservations work on the resource mailbox. Valid values are: - Standard: The resource can be reserved based on the other settings in this cmdlet. This is the default value - - Reserved: The resource can't be reserved. ```yaml @@ -413,18 +427,19 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +Query-based groups (for example, dynamic distribution groups) aren't supported. + +In delegate and principal scenarios, if the delegate or principal is specified by the BookInPolicy parameter, in-policy meeting requests to the resource mailbox are automatically approved. + +To replace the existing list of users or groups with the values you specify, use the syntax `UserOrGroup1,UserOrGroup2,...UserOrGroupN`. If the values contain spaces or otherwise require quotation marks, use the syntax `"UserOrGroup1","UserOrGroup2",..."UserOrGroupN"`. + +To add users or groups without affecting the other entries, see Example 7. ```yaml Type: RecipientIdParameter[] @@ -442,15 +457,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -481,7 +495,6 @@ Accept wildcard characters: False 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. - - $false: Preserve any attachments in incoming messages. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -503,7 +516,6 @@ Accept wildcard characters: False 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. - - $false: Preserve any text in the message body of incoming meeting requests. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -525,7 +537,6 @@ Accept wildcard characters: False 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. - - $false: Non-calendar messages are preserved. ```yaml @@ -545,7 +556,6 @@ Accept wildcard characters: False 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. - - $false: Preserve The Subject value of incoming meeting requests. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -581,11 +591,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnableAutoRelease +This parameter is available only in the cloud-based service. + +{{ Fill EnableAutoRelease Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -EnableResponseDetails 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. - - $false: The reasons for accepting or declining a meeting aren't included in the response message. ```yaml @@ -601,11 +628,31 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnforceCapacity +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: + +- $true: Capacity is enforced. +- $false: Capacity is not enforced. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -EnforceSchedulingHorizon 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. - - $false: A recurring meeting request is automatically accepted if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. However, the number of meetings is automatically reduced so meetings won't occur after the specified date. ```yaml @@ -625,7 +672,6 @@ Accept wildcard characters: False 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. - - $false: Don't forward incoming meeting requests to the delegates. ```yaml @@ -642,12 +688,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -699,11 +744,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MinimumDurationInMinutes +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. + +For recurring meetings, the value of this parameter applies to the length of an individual meeting instance. + +This parameter only works on workspace mailboxes. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -OrganizerInfo 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. - - $false: Organizer information isn't sent when a meeting request is declined because of conflicts. ```yaml @@ -719,11 +785,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PostReservationMaxClaimTimeInMinutes +This parameter is available only in the cloud-based service. + +{{ Fill PostReservationMaxClaimTimeInMinutes Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ProcessExternalMeetingMessages 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. - - $false: Meeting requests from external senders are rejected. This is the default value. ```yaml @@ -739,11 +822,31 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RemoveCanceledMeetings +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: + +- $true: Canceled meetings are deleted. +- $false: Canceled meetings aren't deleted. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RemoveForwardedMeetingNotifications 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). - - $false: Processed forwarded meeting notifications aren't deleted. This is the default value. ```yaml @@ -763,7 +866,6 @@ Accept wildcard characters: False 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. - - $false: Outdated and redundant meeting messages aren't deleted. ```yaml @@ -783,7 +885,6 @@ Accept wildcard characters: False 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. - - $false: The private flag for incoming meeting requests is preserved (private meetings stay private). ```yaml @@ -803,18 +904,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -833,18 +929,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -863,18 +954,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -893,7 +979,6 @@ Accept wildcard characters: False 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. - - $false: Meeting requests that are outside of working hours aren't automatically rejected. This is the default value. You configure the working hours of the resource mailbox by using the WorkDays, WorkingHoursStartTime, WorkingHoursEndTime and WorkingHoursTimeZone parameters on the Set-MailboxCalendarConfiguration cmdlet. @@ -915,7 +1000,6 @@ Accept wildcard characters: False 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. - - $false: Meeting requests that are awaiting approval appear in the calendar as free. ```yaml @@ -938,7 +1022,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -952,12 +1036,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/Set-CaseHoldPolicy.md new file mode 100644 index 0000000000..db1f2c2ede --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-CaseHoldPolicy.md @@ -0,0 +1,333 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-CaseHoldPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-CaseHoldPolicy cmdlet to modify existing case hold policies in the Microsoft Purview compliance portal. + +**Note**: Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to update multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. If you need to update a policy multiple times, make all changes in a single call of the cmdlet. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchange/get-caseholdpolicy). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### RetryDistribution +``` +Set-CaseHoldPolicy [-Identity] + [-RetryDistribution] + [-Confirm] + [-WhatIf] + [] +``` + +### Identity +``` +Set-CaseHoldPolicy [-Identity] + [-AddExchangeLocation ] + [-AddPublicFolderLocation ] + [-AddSharePointLocation ] + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-RemoveExchangeLocation ] + [-RemovePublicFolderLocation ] + [-RemoveSharePointLocation ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +**Note**: Don't use a piped Foreach-Object command when adding or removing scope locations: `"Value1","Value2",..."ValueN" | Foreach-Object {Set-CaseHoldPolicy -Identity "Regulation 123 Compliance" -RemoveExchangeLocation $_}`. + +## EXAMPLES + +### Example 1 +```powershell +Set-CaseHoldPolicy -Identity "Regulation 123 Compliance" -AddExchangeLocation "Kitty Petersen" -AddSharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -RemovePublicFolderLocation All -Comment "Added new counsel, 9/9/14" +``` + +This example makes the following changes to the existing case hold policy named "Regulation 123 Compliance": + +- Adds the mailbox for the user named Kitty Petersen. +- Adds the SharePoint site `https://contoso.sharepoint.com/sites/teams/finance`. +- Removes public folders. +- Updates the comment. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RetryDistribution +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. + +**Note**: Because the process of retrying distribution is a significant operation, run it only if necessary and for one policy at a time. It is not intended to be run every time you update a policy. If you run a script to update multiple policies, wait until the policy distribution is successful before running the command again for the next policy. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocation +The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use the following values: + +- Name +- SMTP address. To specify an inactive mailbox, precede the address with a period (.). +- Microsoft Entra ObjectId. Use the [Get-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/get-mguser) or [Get-MgGroup](https://learn.microsoft.com/powershell/module/microsoft.graph.groups/get-mggroup) cmdlets in Microsoft Graph PowerShell to find this 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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddPublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocation +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"`. + +SharePoint sites can't be added to the policy until they have been indexed. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +The RemoveExchangeLocation parameter specifies the existing mailboxes to remove from the policy. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- SMTP address. To specify an inactive mailbox, precede the address with a period (.). +- Microsoft Entra ObjectId. Use the [Get-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/get-mguser) or [Get-MgGroup](https://learn.microsoft.com/powershell/module/microsoft.graph.groups/get-mggroup) cmdlets in Microsoft Graph PowerShell to find this 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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-CaseHoldRule.md b/exchange/exchange-ps/exchange/Set-CaseHoldRule.md new file mode 100644 index 0000000000..3935336a80 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-CaseHoldRule.md @@ -0,0 +1,164 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-CaseHoldRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-CaseHoldRule cmdlet to modify existing case hold rules in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-CaseHoldRule [-Identity] + [-Comment ] + [-Confirm] + [-ContentMatchQuery ] + [-Disabled ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-CaseHoldRule -Identity "Internal Company Rule" -Disabled $true +``` + +This example disables the enabled case hold rule named "Internal Company Rule". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: + +- $true: The rule is disabled. +- $false: The rule is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-ClassificationRuleCollection.md b/exchange/exchange-ps/exchange/Set-ClassificationRuleCollection.md similarity index 80% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-ClassificationRuleCollection.md rename to exchange/exchange-ps/exchange/Set-ClassificationRuleCollection.md index 1ec179e6ad..1848e06aee 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/exchange/Set-ClassificationRuleCollection.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-classificationrulecollection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-ClassificationRuleCollection @@ -17,25 +16,28 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ClassificationRuleCollection cmdlet to update existing classification rule collections in your organization. -In the Office 365 Security & Compliance Center, use the Set-DlpSensitiveInformationTypeRulePackage cmdlet. +In the Microsoft Purview compliance portal, use the Set-DlpSensitiveInformationTypeRulePackage cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ClassificationRuleCollection [-FileData] [-Confirm] [-DomainController ] [-WhatIf] +Set-ClassificationRuleCollection [-FileData] + [-Confirm] + [-DomainController ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-ClassificationRuleCollection -FileData ([Byte[]]$(Get-Content -Path "C:\My Documents\External Classification Rule Collection.xml" -Encoding Byte -ReadCount 0)) +Set-ClassificationRuleCollection -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\External Classification Rule Collection.xml')) ``` This example imports the classification rule collection file C:\\My Documents\\External Classification Rule Collection.xml. @@ -45,7 +47,7 @@ This example imports the classification rule collection file C:\\My Documents\\E ### -FileData 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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\" -ReadCount 0\)\). +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[] @@ -63,10 +65,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -119,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessArray.md b/exchange/exchange-ps/exchange/Set-ClientAccessArray.md similarity index 85% rename from exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessArray.md rename to exchange/exchange-ps/exchange/Set-ClientAccessArray.md index a9fdb21397..caa657f795 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessArray.md +++ b/exchange/exchange-ps/exchange/Set-ClientAccessArray.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-clientaccessarray +online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessarray applicable: Exchange Server 2010 title: Set-ClientAccessArray schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-ClientAccessArray @@ -17,17 +16,23 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-ClientAccessArray cmdlet to modify RPC Client Access arrays (load-balanced arrays of Client Access servers within a single Active Directory site). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ClientAccessArray [-Identity] [-Confirm] [-DomainController ] - [-Fqdn ] [-Name ] [-Site ] [-WhatIf] [] +Set-ClientAccessArray [-Identity] + [-Confirm] + [-DomainController ] + [-Fqdn ] + [-Name ] + [-Site ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,16 +60,12 @@ This example associates the existing Client Access array named ContosoArray with ## PARAMETERS ### -Identity -The Identity parameter specifies the Client Access array that you want to modify. You can use these values: +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) - - Distinguished name (DN) - - ExchangeLegacyDN - - Fully qualified domain name (FQDN) - - GUID ```yaml @@ -83,8 +84,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -149,12 +149,10 @@ Accept wildcard characters: False ``` ### -Site -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: +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 - - Distinguished name (DN) - - GUID To see a list of available sites, use the Get-ADSite cmdlet. @@ -193,13 +191,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### -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. +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Set-ClientAccessRule.md b/exchange/exchange-ps/exchange/Set-ClientAccessRule.md new file mode 100644 index 0000000000..9a82144d26 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ClientAccessRule.md @@ -0,0 +1,606 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ClientAccessRule + +## SYNOPSIS +> [!NOTE] +> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). + +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-ClientAccessRule cmdlet to modify existing client access rules. Client access rules help you control access to your organization based on the properties of the connection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ClientAccessRule [-Identity] + [-Action ] + [-AnyOfAuthenticationTypes ] + [-AnyOfClientIPAddressesOrRanges ] + [-AnyOfProtocols ] + [-AnyOfSourceTcpPortNumbers ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExceptAnyOfAuthenticationTypes ] + [-ExceptAnyOfClientIPAddressesOrRanges ] + [-ExceptAnyOfProtocols ] + [-ExceptAnyOfSourceTcpPortNumbers ] + [-ExceptUserIsMemberOf ] + [-ExceptUsernameMatchesAnyOfPatterns ] + [-Name ] + [-Priority ] + [-Scope ] + [-UserIsMemberOf ] + [-UsernameMatchesAnyOfPatterns ] + [-UserRecipientFilter ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. + +**Note**: Not all protocols support authentication type filters, and even protocols that support authentication type filters don't support all authentication types. The supported combinations are described in the following lists. Use caution when mixing protocols and authentication types in the same rule. + +Protocols that support authentication type filters: + +- ExchangeActiveSync: BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. +- ExchangeAdminCenter: BasicAuthentication and AdfsAuthentication. +- IMAP4: BasicAuthentication and OAuthAuthentication. +- OutlookWebApp: BasicAuthentication and AdfsAuthentication. +- POP3: BasicAuthentication and OAuthAuthentication. +- RemotePowerShell: BasicAuthentication and NonBasicAuthentication. + +Protocols that don't support authentication type filters: + +- ExchangeWebServices +- OfflineAddressBook +- OutlookAnywhere +- PowerShellWebServices +- REST +- UniversalOutlook + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ClientAccessRule "Allow IMAP4" -AnyOfClientIPAddressesOrRanges @{Add="172.17.17.27/16"} +``` + +This example adds the IP address range 172.17.17.27/16 to the existing client access rule named Allow IMAP4 without affecting the existing IP address values. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Action +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfAuthenticationTypes +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. + +Valid values for this parameter are: + +- AdfsAuthentication +- BasicAuthentication +- CertificateBasedAuthentication +- NonBasicAuthentication +- OAuthAuthentication + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +**Note**: Refer to the Description section to see which authentication types can be used with what protocols. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfClientIPAddressesOrRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254 or 2001:DB8::2AA:FF:C0A8:640A-2001:DB8::2AA:FF:C0A8:6414. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.3.1/24 or 2001:DB8::2AA:FF:C0A8:640A/64. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +For more information about IPv6 addresses and syntax, see this Exchange 2013 topic: [IPv6 address basics](https://learn.microsoft.com/exchange/ipv6-support-in-exchange-2013-exchange-2013-help#ipv6-address-basics). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfProtocols +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: + +- ExchangeActiveSync +- ExchangeAdminCenter +- ExchangeWebServices +- IMAP4 +- OfflineAddressBook +- OutlookAnywhere +- OutlookWebApp +- POP3 +- PowerShellWebServices +- RemotePowerShell +- REST +- UniversalOutlook (Mail and Calendar app) + +**Note**: In Exchange 2019, the only supported values are ExchangeAdminCenter and RemotePowerShell. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfSourceTcpPortNumbers +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfAuthenticationTypes +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. + +Valid values for this parameter are: + +- AdfsAuthentication +- BasicAuthentication +- CertificateBasedAuthentication +- NonBasicAuthentication +- OAuthAuthentication + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +**Note**: Refer to the Description section to see which authentication types can be used with what protocols. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfClientIPAddressesOrRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254 or 2001:DB8::2AA:FF:C0A8:640A-2001:DB8::2AA:FF:C0A8:6414. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.3.1/24 or 2001:DB8::2AA:FF:C0A8:640A/64. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +For more information about IPv6 addresses and syntax, see this Exchange 2013 topic: [IPv6 address basics](https://learn.microsoft.com/exchange/ipv6-support-in-exchange-2013-exchange-2013-help#ipv6-address-basics). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfProtocols +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. + +Valid values for this parameter are: + +- ExchangeActiveSync +- ExchangeAdminCenter +- ExchangeWebServices +- IMAP4 +- OfflineAddressBook +- OutlookAnywhere +- OutlookWebApp +- POP3 +- PowerShellWebServices +- RemotePowerShell +- REST +- UniversalOutlook (Mail and Calendar app) + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfSourceTcpPortNumbers +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptUserIsMemberOf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptUsernameMatchesAnyOfPatterns +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Scope +The Scope parameter specifies the scope of the client access rule. Valid values are: + +- Users: The rule only applies to end-user connections. +- All: The rule applies to all connections (end-users and middle-tier apps). + +```yaml +Type: ClientAccessRulesScope +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIsMemberOf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsernameMatchesAnyOfPatterns +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserRecipientFilter +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. + +You can use the following properties with this parameter: + +- City +- Company +- CountryOrRegion (ISO 3166-1 alpha-2 country code.) +- CustomAttribute1 to CustomAttribute15 +- Department +- Office +- PostalCode +- StateOrProvince +- StreetAddress + +The basic syntax for this parameter is `"Property -ComparisonOperator 'Value'"`: + +- Property is one of the filterable properties in the list above (for example `City` or `CustomAttribute1`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). +- 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. + +For example: + +- `"City -eq 'Redmond'"` +- `"CountryOrRegion -eq 'SG'"`. + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example: + +- `"CustomAttribute1 -eq 'AllowOWA' -and CountryOrRegion -eq AU'"` +- `"(CountryOrRegion -eq 'US' -and Department -eq 'Sales') -or Department -eq 'Research'"`. + +For detailed information about OPATH filter syntax in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/client-access-servers/Set-ClientAccessServer.md b/exchange/exchange-ps/exchange/Set-ClientAccessServer.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessServer.md rename to exchange/exchange-ps/exchange/Set-ClientAccessServer.md index 263bf2ddf7..343bf8d337 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessServer.md +++ b/exchange/exchange-ps/exchange/Set-ClientAccessServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-clientaccessserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ClientAccessServer @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ClientAccessServer cmdlet to modify settings that are associated with the Client Access server role. -Note: In Exchange 2013 or later, use the Set-ClientAccessService cmdlet instead. If you have scripts that use Set-ClientAccessServer, update them to use Set-ClientAccessService. +**Note**: In Exchange 2013 or later, use the Set-ClientAccessService cmdlet instead. If you have scripts that use Set-ClientAccessServer, update them to use Set-ClientAccessService. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -37,7 +36,8 @@ Set-ClientAccessServer [-Identity] [-IrmLogPath ] [-IsOutOfService ] [-RemoveAlternateServiceAccountCredentials] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity @@ -54,11 +54,12 @@ Set-ClientAccessServer [-Identity] [-IrmLogMaxFileSize ] [-IrmLogPath ] [-IsOutOfService ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -75,11 +76,8 @@ This example configures the internal Autodiscover URL for the Active Directory s The Identity parameter specifies the server that you want to modify. You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - FQDN - - GUID ```yaml @@ -98,7 +96,7 @@ Accept wildcard characters: False ### -AlternateServiceAccountCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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[] @@ -150,9 +148,7 @@ The AutoDiscoverSiteScope parameter specifies the Active Directory site that the To see the available Active Directory sites, use the Get-ADSite cmdlet. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To specify multiple values, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. ```yaml Type: MultiValuedProperty @@ -186,8 +182,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -220,7 +215,7 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled -This parameter is available or functional only in 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. @@ -238,7 +233,7 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge -This parameter is available or functional only in 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. @@ -260,7 +255,7 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize -This parameter is available or functional only in 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. @@ -269,13 +264,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -294,7 +285,7 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize -This parameter is available or functional only in 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. @@ -303,11 +294,8 @@ A valid value is a number up to 4 gigabytes (4294967296 bytes). The default valu When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -328,7 +316,7 @@ Accept wildcard characters: False ``` ### -IrmLogPath -This parameter is available or functional only in 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. @@ -346,7 +334,7 @@ Accept wildcard characters: False ``` ### -IsOutOfService -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -400,12 +388,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessService.md b/exchange/exchange-ps/exchange/Set-ClientAccessService.md similarity index 84% rename from exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessService.md rename to exchange/exchange-ps/exchange/Set-ClientAccessService.md index 520e782e4b..bff2cc0183 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessService.md +++ b/exchange/exchange-ps/exchange/Set-ClientAccessService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-clientaccessservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ClientAccessService @@ -17,28 +16,36 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ClientAccessService cmdlet to modify settings that are associated with the Client Access server role. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### AlternateServiceAccount ``` -Set-ClientAccessService [-Identity] [-AlternateServiceAccountCredential ] [-CleanUpInvalidAlternateServiceAccountCredentials] [-RemoveAlternateServiceAccountCredentials] +Set-ClientAccessService [-Identity] + [-AlternateServiceAccountCredential ] + [-CleanUpInvalidAlternateServiceAccountCredentials] + [-RemoveAlternateServiceAccountCredentials] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity ``` -Set-ClientAccessService [-Identity] [-Array ] [-AutoDiscoverServiceInternalUri ] [-AutoDiscoverSiteScope ] +Set-ClientAccessService [-Identity] + [-Array ] + [-AutoDiscoverServiceInternalUri ] + [-AutoDiscoverSiteScope ] [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,11 +62,8 @@ This example configures the internal Autodiscover URL for the Active Directory s The Identity parameter specifies the server that you want to modify. You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - FQDN - - GUID ```yaml @@ -78,7 +82,7 @@ Accept wildcard characters: False ### -AlternateServiceAccountCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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[] @@ -130,9 +134,7 @@ The AutoDiscoverSiteScope parameter specifies the Active Directory site that the To see the available Active Directory sites, use the Get-ADSite cmdlet. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To specify multiple values, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. ```yaml Type: MultiValuedProperty @@ -166,8 +168,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -236,12 +237,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-Clutter.md b/exchange/exchange-ps/exchange/Set-Clutter.md new file mode 100644 index 0000000000..980d6d409c --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-Clutter.md @@ -0,0 +1,115 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-Clutter + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-Clutter cmdlet to configure Clutter settings for mailboxes in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-Clutter -Identity + [-Enable ] + [-UseCustomRouting] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-Clutter -Identity "Alexander Martinez" -Enable $false +``` + +This example disables Clutter for the user Alexander Martinez. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enable +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. +- $false: Clutter is disabled for the mailbox. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-CmdletExtensionAgent.md b/exchange/exchange-ps/exchange/Set-CmdletExtensionAgent.md similarity index 90% rename from exchange/exchange-ps/exchange/organization/Set-CmdletExtensionAgent.md rename to exchange/exchange-ps/exchange/Set-CmdletExtensionAgent.md index 912dcb6bc2..4fcef9f94d 100644 --- a/exchange/exchange-ps/exchange/organization/Set-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/exchange/Set-CmdletExtensionAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-cmdletextensionagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-CmdletExtensionAgent @@ -17,13 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Set-CmdletExtensionAgent cmdlet to modify cmdlet extension agents. To enable or disable cmdlet extension agents, use the Enable-CmdletExtensionAgent and Disable-CmdletExtensionAgent cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-CmdletExtensionAgent [-Identity] [-Confirm] [-DomainController ] - [-Name ] [-Priority ] [-WhatIf] [] +Set-CmdletExtensionAgent [-Identity] + [-Confirm] + [-DomainController ] + [-Name ] + [-Priority ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +35,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and The changes that you make by using the Set-CmdletExtensionAgent cmdlet are applied to every Exchange server in the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,9 +52,7 @@ This example changes the priority of the fictitious "Validation Agent" cmdlet ex 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 - - Distinguished name (DN) - - GUID ```yaml @@ -69,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -155,12 +156,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-ComplianceCase.md b/exchange/exchange-ps/exchange/Set-ComplianceCase.md similarity index 75% rename from exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-ComplianceCase.md rename to exchange/exchange-ps/exchange/Set-ComplianceCase.md index b7f22c7873..2975872e51 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-ComplianceCase.md +++ b/exchange/exchange-ps/exchange/Set-ComplianceCase.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/set-compliancecase -applicable: Office 365 Security & Compliance Center +online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancecase +applicable: Security & Compliance title: Set-ComplianceCase schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "o365scc-ps" --- # Set-ComplianceCase ## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). -Use the Set-ComplianceCase cmdlet to modify eDiscovery cases in the Security & Compliance Center. +Use the Set-ComplianceCase cmdlet to modify eDiscovery cases in the Microsoft Purview compliance portal. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,11 +30,12 @@ Set-ComplianceCase [-Identity] [-ExternalId ] [-Name ] [-Reopen] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). ## EXAMPLES @@ -52,14 +52,13 @@ This example adds a description and case Id to the existing eDiscovery case name 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 - - Identity (GUID value) ```yaml Type: ComplianceCaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: True Position: 1 @@ -75,7 +74,7 @@ This parameter is reserved for internal Microsoft use. Type: ComplianceCaseType Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -91,7 +90,7 @@ The Close switch specifies that you want to close the compliance case. You don't Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -103,15 +102,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -127,7 +125,7 @@ The Description parameter specifies a description for the compliance case. The m Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -143,7 +141,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -159,7 +157,7 @@ The ExternalId parameter specifies an optional ID or external case number that y Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -175,7 +173,7 @@ The Name parameter specifies the unique name of the compliance case. The maximum Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -191,7 +189,7 @@ The Reopen switch specifies that you want to re-open a closed compliance case. Y Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -201,13 +199,13 @@ Accept wildcard characters: False ``` ### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. +The WhatIf switch doesn't work in Security & Compliance PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -221,12 +219,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/Set-ComplianceRetentionEventType.md new file mode 100644 index 0000000000..095fd20c7a --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ComplianceRetentionEventType.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ComplianceRetentionEventType + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-ComplianceRetentionEventType cmdlet to modify retention event types in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ComplianceRetentionEventType -Identity + [-Comment ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ComplianceRetentionEventType -Identity "Fabrikam Project" -Comment "Case officer is Pedro Pizarro" +``` + +This example add a comment to the retention event type named Fabrikam Project + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ComplianceSearch.md b/exchange/exchange-ps/exchange/Set-ComplianceSearch.md new file mode 100644 index 0000000000..2f6e6859f5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ComplianceSearch.md @@ -0,0 +1,631 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ComplianceSearch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-ComplianceSearch cmdlet to modify non-running compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ComplianceSearch [-Identity] + [-AddExchangeLocation ] + [-AddExchangeLocationExclusion ] + [-AddSharePointLocation ] + [-AddSharePointLocationExclusion ] + [-AllowNotFoundExchangeLocationsEnabled ] + [-Confirm] + [-ContentMatchQuery ] + [-Description ] + [-ExchangeLocation ] + [-ExchangeLocationExclusion ] + [-Force] + [-HoldNames ] + [-IncludeOrgContent ] + [-IncludeUserAppContent ] + [-Language ] + [-Name ] + [-PublicFolderLocation ] + [-RefinerNames ] + [-RemoveExchangeLocation ] + [-RemoveExchangeLocationExclusion ] + [-RemovePublicFolderLocation ] + [-RemoveSharePointLocation ] + [-RemoveSharePointLocationExclusion ] + [-SharePointLocation ] + [-SharePointLocationExclusion ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ComplianceSearch -Identity "Project X" -ExchangeLocation All +``` + +This example changes the existing compliance search named Project X. The scope of the Exchange search is changed to all mailboxes. + +### Example 2 +```powershell +Set-ComplianceSearch -Identity "Contoso Case Search 1" -HoldNames All -ExchangeLocation $null -SharePointLocation $null +``` + +This example changes an existing compliance search that's associated with an eDiscovery case in the Microsoft Purview compliance portal. The scope of the search is changed from searching selected mailboxes and SharePoint sites to searching all content locations that have been placed on hold in the eDiscovery case. + +### Example 3 +```powershell +Set-ComplianceSearch -Identity "China Subsidiary Search" -Language zh-CN +``` + +This example changes the language setting for an existing compliance search to Chinese. + +You might have to change the language setting if you're using non-English keywords in the search query (which is specified in the ContentMatchQuery parameter). + +## PARAMETERS + +### -Identity +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: + +- Name +- JobRunId (GUID) + +You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status + +```yaml +Type: ComplianceSearchIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AddExchangeLocation +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. +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocationExclusion +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: + +- A regular user mailbox. Including other types of mailboxes (for example, inactive mailboxes or Microsoft 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter. +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocation +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. + +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocationExclusion +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowNotFoundExchangeLocationsEnabled +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. +- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value. + +The mailbox types that are affected by the value of this parameter include: + +- Inactive mailboxes +- Users without an Exchange Online license who use Office applications +- Guest users +- On-premises users whose identity is synchronized with your Microsoft 365 organization + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocation +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. +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). +- The value All for all mailboxes. You can only use this value by itself. + +To specify a mailbox or distribution group, use the email address. You can specify multiple values 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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeLocationExclusion +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: + +- A regular user mailbox. Including other types of mailboxes (for example, inactive mailboxes or Microsoft 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter. +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldNames +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. + +If the content locations in the compliance search include mailboxes, you also need to use the ExchangeLocation parameter with the value $null. Similarly, if the compliance search includes SharePoint sites, you also need to use the SharePointLocation parameter with the value $null. + +Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you restart this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeOrgContent +{{ Fill IncludeOrgContent Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeUserAppContent +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: + +- $true: The cloud-based storage location for the users specified in any of the Exchange location parameters will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search. +- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Language +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). + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderLocation +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RefinerNames +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +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 +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocationExclusion +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: + +- A mailbox +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePublicFolderLocation +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocation +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. + +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocationExclusion +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocation +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. + +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointLocationExclusion +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/Set-ComplianceSearchAction.md new file mode 100644 index 0000000000..a490fa06ca --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ComplianceSearchAction.md @@ -0,0 +1,148 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ComplianceSearchAction + +## SYNOPSIS +> [!NOTE] +> After May 26, 2025, this cmdlet 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 cmdlet is functional only in on-premises Exchange. + +Use the Set-ComplianceSearchAction cmdlet to change the export key on export compliance search actions in on-premises Exchange. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ComplianceSearchAction [-Identity] + [-ChangeExportKey] + [-DomainController ] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +## EXAMPLES + +### Example 1 +```powershell +Set-ComplianceSearchAction -Identity "Project X_Export" -ChangeExportKey +``` + +This example changes the export key on the export compliance search action named Project X\_Export. + +## PARAMETERS + +### -Identity +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`). +- JobRunId (GUID) + +```yaml +Type: ComplianceSearchActionIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ChangeExportKey +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md new file mode 100644 index 0000000000..5301f61588 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md @@ -0,0 +1,237 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ComplianceSecurityFilter + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-ComplianceSecurityFilter cmdlet to modify compliance security filters in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ComplianceSecurityFilter -FilterName + [-Action ] + [-Confirm] + [-Description ] + [-Filters ] + [-Region ] + [-Users ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$filterusers = Get-ComplianceSecurityFilter -FilterName "Ottawa Users Filter" + +$filterusers.users.add("pilarp@contoso.com") + +Set-ComplianceSecurityFilter -FilterName "Ottawa Users Filter" -Users $filterusers.users +``` + +This example adds user pilarp@contoso.com to the compliance security filter named Ottawa Users Filter without affecting other users assigned to the filter. + +### Example 2 +```powershell +$filterusers = Get-ComplianceSecurityFilter -FilterName "Ottawa Users Filter" + +$filterusers.users.remove("annb@contoso.com") + +Set-ComplianceSecurityFilter -FilterName "Ottawa Users Filter" -Users $filterusers.users +``` + +This example removes user annb@contoso.com to the compliance security filter named Ottawa Users Filter without affecting other users assigned to the filter. + +## PARAMETERS + +### -FilterName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Action +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. +- Preview: The filter is applied when previewing search results. +- Purge: The filter is applied when purging search results. How the items are deleted is controlled by the PurgeType parameter value on the New-ComplianceSearchAction cmdlet. The default value is SoftDelete, which means the purged items are recoverable by users until the deleted items retention period expires. +- Search: The filter is applied when running a search. +- All: The filter is applied to all search actions. + +```yaml +Type: ComplianceSecurityFilterActionType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filters +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). +- Mailbox content filter: Specifies the mailbox content the assigned users can search for. Valid syntax is `MailboxContent_`, where `` specifies a Keyword Query Language (KQL) property that can be specified in a compliance search. For example, `"MailboxContent_Recipients -like 'contoso.com'"` allows users to only search for messages sent to recipients in the contoso.com domain. For a list of searchable email properties, see [Keyword queries for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions#searchable-email-properties). +- Site and site content filter: There are two SharePoint and OneDrive site-related filters that you can create: `Site_` (specifies site-related properties. For example,`"Site_Path -eq 'https://contoso.sharepoint.com/sites/doctors'"` allows users to only search for content in the `https://contoso.sharepoint.com/sites/doctors` site collection) and `SiteContent_` (specifies content-related properties. For example, `"SiteContent_FileExtension -eq 'docx'"` allows users to only search for Word documents). For a list of searchable site properties, see [Overview of crawled and managed properties in SharePoint Server](https://learn.microsoft.com/SharePoint/technical-reference/crawled-and-managed-properties-overview). Properties marked with a Yes in the Queryable column can be used to create a site or site content filter. + +You can specify multiple filters of the same type. For example, `"Mailbox_CustomAttribute10 -eq 'FTE' -and Mailbox_MemberOfGroup -eq '$($DG.DistinguishedName)'"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Region +The Region parameter specifies the satellite location for multi-geo tenants to conduct eDiscovery searches in. Valid values are: + +- APC: Asia-Pacific +- AUS: Australia +- CAN: Canada +- EUR: Europe, Middle East, Africa +- FRA: France +- GBR: United Kingdom +- IND: India +- JPN: Japan +- LAM: Latin America +- NAM: North America + +If you don't use this parameter in a multi-geo tenant, eDiscovery searches are performed in the central location. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Users +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. +- The value All: Assigns the filter to all users. You can only use this value by itself. +- One or more role groups: Identify the role group by its name. You can specify multiple values separated by commas. + +You can't specify distribution groups with this parameter. + +The values you specify will overwrite any existing entries. See the Examples section to add or remove users without affecting other existing entries. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ComplianceTag.md b/exchange/exchange-ps/exchange/Set-ComplianceTag.md new file mode 100644 index 0000000000..ef1e0e1fd7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ComplianceTag.md @@ -0,0 +1,378 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ComplianceTag + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-ComplianceTag cmdlet to modify retention labels in the Microsoft Purview compliance portal. Retention labels apply retention settings to content. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Set-ComplianceTag [-Identity] + [-AutoApprovalPeriod ] + [-Comment ] + [-ComplianceTagForNextStage ] + [-Confirm] + [-EventType ] + [-FilePlanProperty ] + [-FlowId ] + [-Force] + [-MultiStageReviewProperty ] + [-Notes ] + [-RetentionDuration ] + [-ReviewerEmail ] + [-WhatIf] + [] +``` + +### PriorityCleanup +``` +Set-ComplianceTag [-Identity] [-PriorityCleanup] + [-Comment ] + [-Confirm] + [-Force] + [-MultiStageReviewProperty ] + [-Notes ] + [-RetentionDuration ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ComplianceTag -Identity "HR Content" -RetentionDuration 2555 -Comment "Retain HR content for 7 years" +``` + +This example modifies the existing label named HR Content by modifying the retention duration and adding a comment. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the label that you want to modify. You can use any value that uniquely identifies the tag. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AutoApprovalPeriod +{{ Fill AutoApprovalPeriod Description }} + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceTagForNextStage +{{ Fill ComplianceTagForNextStage Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventType +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 +- Distinguished name (DN) +- GUID + +You can use the Get-RetentionComplianceRule cmdlet to view the available retention rules. + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FilePlanProperty +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` +- `Get-FilePlanPropertyCategory | Format-List Name` +- `Get-FilePlanPropertyCitation | Format-List Name` +- `Get-FilePlanPropertyDepartment | Format-List Name` +- `Get-FilePlanPropertyReferenceId | Format-List Name` +- `Get-FilePlanPropertySubCategory | Format-List Name` + +A valid value for this parameter involves two steps: + +- A variable to store the file plan properties as a PSCustomObject using the following syntax: + + `$Variable1=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Name"},@{Key="FilePlanPropertyCategory";Value="Name"},@{Key="FilePlanPropertySubcategory";Value="Name"},@{Key="FilePlanPropertyCitation";Value="Name"},@{Key="FilePlanPropertyReferenceId";Value="Name"},@{Key="FilePlanPropertyAuthority";Value="Name"})}` + + For example: + + `$retentionLabelAction=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Legal"},@{Key="FilePlanPropertyCategory";Value="Tax"},@{Key="FilePlanPropertySubcategory";Value="US_Tax"},@{Key="FilePlanPropertyCitation";Value="LegalCitation"},@{Key="FilePlanPropertyReferenceId";Value="Referen`ceA"},@{Key="FilePlanPropertyAuthority";Value="Auth1"})} + +- A second variable to convert the PSCustomObject to a JSON object using the following syntax: + + `$Variable2 = ConvertTo-Json $Variable1` + + For example: + + `$fpStr = ConvertTo-Json $retentionLabelAction` + +You use the second variable as the value for this parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FlowId +**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. + +You can find the GUID value of the flow by using either of the following methods: + +- Navigate to the flow from the Power Automate portal. The GUID value of the flow is in the URL. +- Use the Power Automate action named 'List flows as admin'. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiStageReviewProperty +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]},]}'` + +For example: + +`'{"MultiStageReviewSettings":[{"StageName":"Stage1","Reviewers":[jie@contoso.onmicrosoft.com]},{"StageName":"Stage2","Reviewers":[bharath@contoso.onmicrosoft.com,helen@contoso.onmicrosoft.com]},]}'` + +This syntax is a JSON object that defines each review stage id, review stage name, and list of reviewers. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Notes +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: + +- A positive integer. +- The value unlimited. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReviewerEmail +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-Contact.md b/exchange/exchange-ps/exchange/Set-Contact.md similarity index 86% rename from exchange/exchange-ps/exchange/users-and-groups/Set-Contact.md rename to exchange/exchange-ps/exchange/Set-Contact.md index 02ba7fae98..a173246fe3 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-Contact.md +++ b/exchange/exchange-ps/exchange/Set-Contact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-contact +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-Contact @@ -17,27 +16,58 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-Contact cmdlet to modify contact object settings. If the contact is a mail contact, you can use the Set-MailContact cmdlet to modify other Microsoft Exchange settings that aren't available by using the Set-Contact cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-Contact [-Identity] [-AllowUMCallsFromNonUsers ] - [-AssistantName ] [-City ] [-Company ] [-Confirm] [-CountryOrRegion ] - [-CreateDTMFMap ] [-Department ] [-DisplayName ] [-DomainController ] - [-Fax ] [-FirstName ] [-HomePhone ] [-IgnoreDefaultScope] [-Initials ] - [-LastName ] [-Manager ] [-MobilePhone ] [-Name ] - [-Notes ] [-Office ] [-OtherFax ] [-OtherHomePhone ] - [-OtherTelephone ] [-Pager ] [-Phone ] [-PhoneticDisplayName ] - [-PostalCode ] [-PostOfficeBox ] [-SeniorityIndex ] - [-SimpleDisplayName ] [-StateOrProvince ] [-StreetAddress ] - [-TelephoneAssistant ] [-Title ] [-UMCallingLineIds ] - [-UMDtmfMap ] [-WebPage ] [-WhatIf] [-WindowsEmailAddress ] - [-GeoCoordinates ] [] +Set-Contact [-Identity] + [-AllowUMCallsFromNonUsers ] + [-AssistantName ] + [-City ] + [-Company ] + [-Confirm] + [-CountryOrRegion ] + [-CreateDTMFMap ] + [-Department ] + [-DisplayName ] + [-DomainController ] + [-Fax ] + [-FirstName ] + [-GeoCoordinates ] + [-HomePhone ] + [-IgnoreDefaultScope] + [-Initials ] + [-LastName ] + [-Manager ] + [-MobilePhone ] + [-Name ] + [-Notes ] + [-Office ] + [-OtherFax ] + [-OtherHomePhone ] + [-OtherTelephone ] + [-Pager ] + [-Phone ] + [-PhoneticDisplayName ] + [-PostalCode ] + [-PostOfficeBox ] + [-SeniorityIndex ] + [-SimpleDisplayName ] + [-StateOrProvince ] + [-StreetAddress ] + [-TelephoneAssistant ] + [-Title ] + [-UMCallingLineIds ] + [-UMDtmfMap ] + [-WebPage ] + [-WhatIf] + [-WindowsEmailAddress ] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,11 +88,8 @@ Change the Company parameter value to Contoso. The Identity parameter specifies the contact that you want to modify. You can use any value that uniquely identifies the contact. For example: - Name - - Distinguished name (DN) - - Canonical DN - - GUID ```yaml @@ -79,13 +106,15 @@ Accept wildcard characters: False ``` ### -AllowUMCallsFromNonUsers -The AllowUMCallsFromNonUsers parameter specifies whether to exclude the contact from directory searches. +This parameter is available only in on-premises Exchange. + +The AllowUMCallsFromNonUsers parameter specifies whether to exclude the contact from Unified Messaging directory searches. ```yaml Type: AllowUMCallsFromNonUsersFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -145,8 +174,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -163,7 +191,11 @@ Accept wildcard characters: False ``` ### -CountryOrRegion -The CountryOrRegion parameter specifies the contact's country or region. +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). + +The friendly name is returned in the CountryOrRegion property value by the Get-Contact cmdlet, but you can use either the friendly name or the two-letter country code in filter operations. ```yaml Type: CountryInfo @@ -179,17 +211,18 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap +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: - $true: A DTMF map is created for the recipient. This is the default value. - - $false: A DTMF map isn't created for the recipient. ```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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -282,6 +315,27 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -GeoCoordinates +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" +- Latitude, longitude, and altitude: For example, "47.644125;-122.122411;161.432" + +**Note**: If period separators don't work for you, use commas instead. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -HomePhone The HomePhone parameter specifies the contact's home telephone number. @@ -301,12 +355,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -582,12 +635,10 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\", """, "'", "(", ")", "+", ",", "-", ".", "/", ":" and "?". +- space +- `" ' ( ) + , - . / : ?` This parameter is meaningful only if the contact is mail-enabled. @@ -669,13 +720,15 @@ Accept wildcard characters: False ``` ### -UMCallingLineIds +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. ```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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -685,27 +738,27 @@ Accept wildcard characters: False ``` ### -UMDtmfMap -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: - -- emailAddress:\ +This parameter is available only in on-premises Exchange. -- lastNameFirstName:\ +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: -- firstNameLastName:\ +- `emailAddress:` +- `lastNameFirstName:` +- `firstNameLastName:` -To enter values that overwrite all existing entries, use the following syntax: emailAddress:\,lastNameFirstName:\,firstNameLastName:\. +To enter values that overwrite all existing entries, use the following syntax: `emailAddress:,lastNameFirstName:,firstNameLastName:`. -If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:\, all existing lastNameFirstName and firstNameLastName values are removed. +If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only `emailAddress:`, all existing lastNameFirstName and firstNameLastName values are removed. -To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"; Remove="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"}. +To add or remove values without affecting other existing entries, use the following syntax: `@{Add="emailAddress:","lastNameFirstName:","firstNameLastName:"; Remove="emailAddress:","lastNameFirstName:","firstNameLastName:"}`. -If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:\","emailAddress:\} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. +If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use `@{Add="emailAddress:","emailAddress:}` to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. ```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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -750,7 +803,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -768,37 +820,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -GeoCoordinates -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" - -- Latitude, longitude, and altitude: For example, "47.644125;-122.122411;161.432" - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-ContentFilterConfig.md b/exchange/exchange-ps/exchange/Set-ContentFilterConfig.md new file mode 100644 index 0000000000..80deb1646f --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ContentFilterConfig.md @@ -0,0 +1,412 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ContentFilterConfig + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Set-ContentFilterConfig cmdlet to modify the content filter configuration on a Mailbox server or an Edge Transport server. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ContentFilterConfig [-BypassedRecipients ] + [-BypassedSenderDomains ] + [-BypassedSenders ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExternalMailEnabled ] + [-InternalMailEnabled ] + [-OutlookEmailPostmarkValidationEnabled ] + [-QuarantineMailbox ] + [-RejectionResponse ] + [-SCLDeleteEnabled ] + [-SCLDeleteThreshold ] + [-SCLQuarantineEnabled ] + [-SCLQuarantineThreshold ] + [-SCLRejectEnabled ] + [-SCLRejectThreshold ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ContentFilterConfig -BypassedSenderDomains woodgrovebank.com +``` + +This example specifies the sender domain woodgrovebank.com as a bypassed domain. Messages received from that domain bypass the Content Filter agent. + +### Example 2 +```powershell +Set-ContentFilterConfig -SCLQuarantineEnabled $true -SCLRejectEnabled $true -SCLDeleteEnabled $true -SCLQuarantineThreshold 5 -SCLRejectThreshold 6 -SCLDeleteThreshold 8 -QuarantineMailbox SpamQuarantineMailbox@contoso.com -RejectionResponse "Message rejected due to content restrictions" -BypassedRecipients user1@contoso.com,user2@contoso.com +``` + +This example makes the following modifications to the Content Filter agent configuration: + +It enables and configures the SCL threshold functionalities that quarantine, reject and delete messages to 5, 6 and 8 respectively. + +It specifies `SpamQuarantineMailbox@contoso.com` as the spam quarantine mailbox. + +It defines two users for whom the Content Filter won't process messages. + +## PARAMETERS + +### -BypassedRecipients +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassedSenderDomains +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassedSenders +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. +- $false: The Content Filter agent is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalMailEnabled +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. +- $false: Messages from unauthenticated connections aren't processed by the Content Filter agent. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalMailEnabled +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. +- $false: Messages from authenticated connections aren't processed by the Content Filter agent. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookEmailPostmarkValidationEnabled +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. +- For inbound messages, the Content Filter agent looks for a computational postmark header in the message. The presence of a valid, solved computational postmark header indicates the client computer that generated the message solved the computational postmark, so the Content Filter agent is likely to lower the message's spam confidence level (SCL) rating. + +Valid values are: + +- $true: Outlook Email Postmark validation is enabled. +- $false: Outlook Email Postmark validation is disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RejectionResponse +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SCLDeleteEnabled +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. +- $false: Messages aren't deleted. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SCLDeleteThreshold +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SCLQuarantineEnabled +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. +- $false: Messages aren't quarantined. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SCLQuarantineThreshold +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SCLRejectEnabled +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. +- $false: Messages aren't rejected. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SCLRejectThreshold +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/policy-and-compliance-dlp/Set-DataClassification.md b/exchange/exchange-ps/exchange/Set-DataClassification.md similarity index 81% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DataClassification.md rename to exchange/exchange-ps/exchange/Set-DataClassification.md index cc0d74e983..a31254e845 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DataClassification.md +++ b/exchange/exchange-ps/exchange/Set-DataClassification.md @@ -1,38 +1,44 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dataclassification -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-DataClassification ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [Set-DlpSensitiveInformationType](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlpsensitiveinformationtype) cmdlet in Office 365 Security & Compliance Center PowerShell. +In Exchange Online, this cmdlet has been replaced by the [Set-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchange/set-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the Set-DataClassification cmdlet to modify data classification rules that use document fingerprints. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-DataClassification [-Identity] [-Confirm] [-Description ] - [-DomainController ] [-Fingerprints ] [-IsDefault] [-Locale ] - [-Name ] [-WhatIf] [] +Set-DataClassification [-Identity] + [-Confirm] + [-Description ] + [-DomainController ] + [-Fingerprints ] + [-IsDefault] + [-Locale ] + [-Name ] + [-WhatIf] + [] ``` ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,14 +58,32 @@ This example removes the existing Spanish translation from the data classificati ### Example 3 ```powershell -$Benefits_Template = Get-Content "C:\My Documents\Contoso Benefits Template.docx" -Encoding byte; $Benefits_Fingerprint = New-Fingerprint -FileData $Benefits_Template -Description "Contoso Benefits Template"; $Contoso_Confidential = Get-DataClassification "Contoso Confidential"; $Array = [System.Collections.ArrayList]($Contoso_Confidential.Fingerprints); $Array.Add($Benefits_FingerPrint); Set-DataClassification $Contoso_Confidential.Identity -FingerPrints $Array +$Benefits_Template = [System.IO.File]::ReadAllBytes('C:\My Documents\Contoso Benefits Template.docx') + +$Benefits_Fingerprint = New-Fingerprint -FileData $Benefits_Template -Description "Contoso Benefits Template" + +$Contoso_Confidential = Get-DataClassification "Contoso Confidential" + +$Array = [System.Collections.ArrayList]($Contoso_Confidential.Fingerprints) + +$Array.Add($Benefits_FingerPrint) + +Set-DataClassification $Contoso_Confidential.Identity -FingerPrints $Array ``` This example modifies the existing data classification rule named "Contoso Confidential" by adding a new document fingerprint for the file C:\\My Documents\\Contoso Benefits Template.docx without affecting any existing document fingerprints that are already defined. ### Example 4 ```powershell -$cc = Get-DataClassification "Contoso Confidential"; $a = [System.Collections.ArrayList]($cc.Fingerprints); $a; $a.RemoveAt(0); Set-DataClassification $cc.Identity -FingerPrints $a +$cc = Get-DataClassification "Contoso Confidential" + +$a = [System.Collections.ArrayList]($cc.Fingerprints) + +$a + +$a.RemoveAt(0) + +Set-DataClassification $cc.Identity -FingerPrints $a ``` This example modifies the data classification rule named "Contoso Confidential" by removing an existing document fingerprint without affecting other document fingerprints that are already defined. @@ -72,16 +96,14 @@ The first three commands return the list of document fingerprints in the data cl 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 - - LocalizedName - - Identity GUID value ```yaml Type: DataClassificationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -93,15 +115,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -117,7 +138,7 @@ The Description parameter specifies a description for the data classification ru Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -143,13 +164,13 @@ Accept wildcard characters: False ``` ### -Fingerprints -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://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/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. +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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -159,7 +180,9 @@ Accept wildcard characters: False ``` ### -IsDefault -The IsDefault switch is used with the Locale parameter to specify the default language for the data classification rule. The default Locale value is stored in the DefaultCulture property. +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. When you change the default Locale value, the Name value of the data classification rule changes to match the Name value that's associated with the new default locale. The original Name value when the rule was created is permanently stored the LocalizedName property. @@ -167,7 +190,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -179,7 +202,7 @@ Accept wildcard characters: False ### -Locale 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://go.microsoft.com/fwlink/p/?linkId=184859). +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). Typically, you use the Locale parameter with the Name and Description parameters to add or remove translated names and descriptions for the data classification rule. You can also use the Locale parameter with the IsDefault switch to designate an existing translated name and description as the default. Before you can remove the default translation, you need to set another translation as the default. @@ -187,7 +210,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -207,7 +230,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -223,7 +246,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -237,12 +260,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-DataEncryptionPolicy.md b/exchange/exchange-ps/exchange/Set-DataEncryptionPolicy.md similarity index 84% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Set-DataEncryptionPolicy.md rename to exchange/exchange-ps/exchange/Set-DataEncryptionPolicy.md index ea12464184..729b74f9f7 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/exchange/Set-DataEncryptionPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/set-dataencryptionpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Set-DataEncryptionPolicy @@ -17,50 +16,52 @@ This cmdlet is available only in the cloud-based service. Use the Set-DataEncryptionPolicy cmdlet to modify data encryption policies in Exchange Online. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### DCAdminPurgeKeyRequest ``` -Set-DataEncryptionPolicy [-Identity] [-PermanentDataPurgeContact ] -PermanentDataPurgeReason +Set-DataEncryptionPolicy [-Identity] -PermanentDataPurgeReason [-PermanentDataPurgeContact ] [-Confirm] [-Description ] [-DomainController ] [-Enabled ] [-Force] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### TenantAdminPurgeKeyRequest ``` -Set-DataEncryptionPolicy [-Identity] -PermanentDataPurgeContact -PermanentDataPurgeReason [-PermanentDataPurgeRequested] +Set-DataEncryptionPolicy [-Identity] -PermanentDataPurgeContact -PermanentDataPurgeReason + [-PermanentDataPurgeRequested] [-Confirm] [-Description ] [-DomainController ] [-Enabled ] [-Force] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RefreshKey ``` -Set-DataEncryptionPolicy [-Identity] [-Refresh] +Set-DataEncryptionPolicy [-Identity] + [-Refresh] [-Confirm] [-Description ] [-DomainController ] [-Enabled ] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,16 +85,14 @@ This example updates the data encryption policy named Europe Mailboxes after one 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 - - Distinguished name (DN) - - GUID ```yaml Type: DataEncryptionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection +Applicable: Exchange Online Required: True Position: 1 @@ -178,7 +177,7 @@ Use the Refresh switch to update the data encryption policy in Exchange Online a Type: SwitchParameter Parameter Sets: RefreshKey Aliases: -Applicable: Exchange Online, Exchange Online Protection +Applicable: Exchange Online Required: True Position: Named @@ -190,10 +189,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -214,7 +214,7 @@ The Description parameter specifies an optional description for the data encrypt Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection +Applicable: Exchange Online Required: False Position: Named @@ -243,7 +243,6 @@ Accept wildcard characters: False The Enabled parameter enables or disable the data encryption policy. Valid values are: - $true: The policy is enabled. - - $false: The policy is disabled. ```yaml @@ -260,7 +259,9 @@ Accept wildcard characters: False ``` ### -Force -Use the Force switch when you're trying to initiate the deletion of all data that's encrypted by the data encryption policy (the PermanentDataPurgeRequested switch), but the associated Azure Key Vault has also been deleted. You don't need to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -282,7 +283,7 @@ The Name parameter specifies the unique name for the data encryption policy. If Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection +Applicable: Exchange Online Required: False Position: Named @@ -312,12 +313,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroup.md similarity index 97% rename from exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroup.md index ae906bcd9c..d5e6a1b952 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/set-databaseavailabilitygroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-DatabaseAvailabilityGroup @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-DatabaseAvailabilityGroup cmdlet to configure properties of a database availability group (DAG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -65,14 +64,11 @@ The Set-DatabaseAvailabilityGroup cmdlet enables you to manage DAG properties th DAG property values are stored in both Active Directory and the cluster database. Because some properties are stored in the cluster database, the underlying cluster for the DAG must have quorum to set the properties for: - ReplicationPort - - NetworkCompression - - NetworkEncryption - - DiscoverNetworks -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -395,8 +391,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -448,7 +443,6 @@ Accept wildcard characters: False The DatacenterActivationMode parameter specifies the datacenter activation mode for the DAG. Valid values are: - Off: Datacenter activation mode is disabled. - - DagOnly: Datacenter activation mode is enabled. ```yaml @@ -502,7 +496,6 @@ Accept wildcard characters: False The FileSystem parameter specifies the file system that's used for the DAG. Valid values are: - NTFS - - ReFS ```yaml @@ -541,7 +534,7 @@ This parameter is reserved for internal Microsoft use. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2019 Required: False Position: Named @@ -554,11 +547,8 @@ Accept wildcard characters: False The NetworkCompression parameter specifies the network compression option for the DAG. Valid values are: - Disabled: Network compression is disabled on all networks. - - Enabled: Network compression is enabled on all networks. - - InterSubnetOnly: Network compression is enabled only for inter-subnet communication. - - SeedOnly: Network compression is enabled only for seeding. ```yaml @@ -578,11 +568,8 @@ Accept wildcard characters: False The NetworkEncryption parameter specifies the network encryption option for the DAG. Valid values are: - Disabled: Network encryption is disabled on all networks. - - Enabled: Network encryption is enabled on all networks. - - InterSubnetOnly: Network encryption is enabled only for inter-subnet communication. - - SeedOnly: Network encryption is enabled only for seeding. ```yaml @@ -603,7 +590,9 @@ The PreferenceMoveFrequency parameter specifies how frequently the Microsoft Exc To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. -The default value is 01:00:00 (1 hour). To disable this feature, specify the value ([System.Threading.Timeout]::InfiniteTimeSpan). +The default value is 01:00:00 (1 hour). To disable this feature, specify the value `([System.Threading.Timeout]::InfiniteTimeSpan)`. + +**Important**: Don't specify a value larger than 49.7 days. A larger value will crash MSExchangeRepl.exe with an ArgumentOutOfRangeException error on all DAG members. ```yaml Type: TimeSpan @@ -719,12 +708,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroupNetwork.md similarity index 90% rename from exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroupNetwork.md index 6a37e29b6d..1cf2e33f62 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroupNetwork.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/set-databaseavailabilitygroupnetwork +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-DatabaseAvailabilityGroupNetwork @@ -17,21 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Set-DatabaseAvailabilityGroupNetwork cmdlet to configure a network for a database availability group (DAG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-DatabaseAvailabilityGroupNetwork [-Identity] [-Confirm] - [-Description ] [-DomainController ] [-IgnoreNetwork ] [-Name ] - [-ReplicationEnabled ] [-Subnets ] [-WhatIf] +Set-DatabaseAvailabilityGroupNetwork [-Identity] + [-Confirm] + [-Description ] + [-DomainController ] + [-IgnoreNetwork ] + [-Name ] + [-ReplicationEnabled ] + [-Subnets ] + [-WhatIf] [] ``` ## DESCRIPTION You can configure a variety of network properties, such as the name for the network, a description of the network, a list of one or more subnets that comprise the network and whether the network is enabled for replication (log shipping and seeding). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,8 +75,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -204,12 +208,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-DefaultTenantBriefingConfig.md b/exchange/exchange-ps/exchange/Set-DefaultTenantBriefingConfig.md new file mode 100644 index 0000000000..82ecf059aa --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DefaultTenantBriefingConfig.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DefaultTenantBriefingConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module version 3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Set-DefaultTenantBriefingConfig cmdlet to modify the default Briefing email configuration in cloud-based organizations. For details about configuring the Briefing email, see [Configure Briefing email](https://learn.microsoft.com/viva/insights/personal/Briefing/be-admin). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DefaultTenantBriefingConfig -IsEnabledByDefault + [-ResultSize ] + [] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +``` +Set-DefaultTenantBriefingConfig -IsEnabledByDefault Opt-in + +This example sets the default Briefing email configuration for the organization to receive the Briefing email. +``` + +## PARAMETERS + +### -IsEnabledByDefault +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. +- Opt-out: By default, no users in the organization are subscribed to receive the Briefing email. This is the default value. + +This setting affects the following users: + +- Existing users who haven't already updated their user settings to opt-in or opt-out of the Briefing email. +- New users that you create. + +This setting does not affect users who've already updated their user settings to opt-in or opt-out of the Briefing email. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/p/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Deploy personal insights](https://learn.microsoft.com/viva/insights/personal/setup/deployment-guide) diff --git a/exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md new file mode 100644 index 0000000000..9c1ba06bb4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md @@ -0,0 +1,161 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DefaultTenantMyAnalyticsFeatureConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module version 3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Set-DefaultTenantMyAnalyticsFeatureConfig cmdlet to update the availability and status of Viva Insights features for the cloud-based organization: digest email, add-in, dashboard, meeting effectiveness survey, and schedule send suggestions. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DefaultTenantMyAnalyticsFeatureConfig + [-Feature ] + [-IsEnabled ] + [-ResultSize ] + [-SamplingRate ] + [] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Set-DefaultTenantMyAnalyticsFeatureConfig -Feature All -IsEnabled $true +``` + +This example enables all available Viva Insights features for the organization: add-in, dashboard, digest email, meeting effectiveness survey, schedule send suggestions. + +### Example 2 +```powershell +Set-DefaultTenantMyAnalyticsFeatureConfig -Feature Add-in -IsEnabled $false +``` + +This example disables Viva Insight add-in feature for the organization. + +### Example 3 +```powershell +Set-DefaultTenantMyAnalyticsFeatureConfig -Feature Meeting-Effectiveness-Survey-Sampling-Rate -SamplingRate 0.2 +``` + +This example sets the meeting effectiveness survey sampling rate to 20%. + +## PARAMETERS + +### -Feature +The Feature parameter specifies the Viva Insights feature to enable or disable. Valid values are: + +- Add-in +- Dashboard +- Digest-email +- Meeting-effectiveness-survey +- Meeting-effectiveness-survey-sampling-rate +- Schedule-send +- All (all features) + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsEnabled +The IsEnabled parameter enables or disables the Viva Insights feature specified by the Feature parameter. Valid values are: + +- $true: The feature is enabled. +- $false: The feature is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SamplingRate +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. + +```yaml +Type: Double +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Deploy personal insights](https://learn.microsoft.com/viva/insights/personal/setup/deployment-guide) diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-DeliveryAgentConnector.md b/exchange/exchange-ps/exchange/Set-DeliveryAgentConnector.md similarity index 85% rename from exchange/exchange-ps/exchange/mail-flow/Set-DeliveryAgentConnector.md rename to exchange/exchange-ps/exchange/Set-DeliveryAgentConnector.md index 245e9d6b68..e1280caf99 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/exchange/Set-DeliveryAgentConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-deliveryagentconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-DeliveryAgentConnector @@ -17,22 +16,33 @@ This cmdlet is available only in on-premises Exchange. Use the Set-DeliveryAgentConnector cmdlet to configure a specific delivery agent connector in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-DeliveryAgentConnector [-Identity] - [-AddressSpaces ] [-Comment ] [-Confirm] [-DeliveryProtocol ] - [-DomainController ] [-Enabled ] [-Force] [-IsScopedConnector ] - [-MaxConcurrentConnections ] [-MaxMessageSize ] [-MaxMessagesPerConnection ] - [-Name ] [-SourceTransportServers ] [-WhatIf] [] + [-AddressSpaces ] + [-Comment ] + [-Confirm] + [-DeliveryProtocol ] + [-DomainController ] + [-Enabled ] + [-Force] + [-IsScopedConnector ] + [-MaxConcurrentConnections ] + [-MaxMessageSize ] + [-MaxMessagesPerConnection ] + [-Name ] + [-SourceTransportServers ] + [-WhatIf] + [] ``` ## DESCRIPTION -Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://docs.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). +Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,7 +61,11 @@ Sets the maximum concurrent connections to 10. ### Example 2 ```powershell -$ConnectorConfig = Get-DeliveryAgentConnector "Contoso X.400 Connector"; $ConnectorConfig.AddressSpaces += "X400:c=US;p=Fabrikam;a=Contoso;o=Sales;1"; $ConnectorConfig.SourceTransportServers += Hub04; Set-DeliveryAgentConnector "Contoso X.400 Connector" -AddressSpaces $ConnectorConfig.AddressSpaces -SourceTransportServers $ConnectorConfig.SourceTransportServers +$ConnectorConfig = Get-DeliveryAgentConnector "Contoso X.400 Connector" + +$ConnectorConfig.AddressSpaces += "X400:c=US;p=Fabrikam;a=Contoso;o=Sales;1" + +$ConnectorConfig.SourceTransportServers += Hub04; Set-DeliveryAgentConnector "Contoso X.400 Connector" -AddressSpaces $ConnectorConfig.AddressSpaces -SourceTransportServers $ConnectorConfig.SourceTransportServers ``` This example uses the temporary variable $ConnectorConfig to add the address space c=US;p=Fabrikam;a=Contoso;o=Sales to the delivery agent connector Contoso X.400 Connector and also adds the server Hub04 to the list of servers that host the connector. @@ -75,7 +89,7 @@ Accept wildcard characters: False ``` ### -AddressSpaces -The AddressSpaces parameter specifies the domain names for which this delivery agent connector is responsible. The syntax for entering an address space is as follows: \:\;\. You must enclose each address space in quotation marks ("). +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 @@ -109,8 +123,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -179,7 +192,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -234,11 +249,8 @@ Accept wildcard characters: False 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) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are treated as bytes. The valid input range for this parameter is from 65536 through 2147483647 bytes. @@ -331,12 +343,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-DetailsTemplate.md b/exchange/exchange-ps/exchange/Set-DetailsTemplate.md similarity index 88% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-DetailsTemplate.md rename to exchange/exchange-ps/exchange/Set-DetailsTemplate.md index 17a8c545e5..dfeb2f1c61 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-DetailsTemplate.md +++ b/exchange/exchange-ps/exchange/Set-DetailsTemplate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/set-detailstemplate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-DetailsTemplate @@ -17,17 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Set-DetailsTemplate cmdlet to modify the attributes of a details template. To make changes to the details template format and layout, you need to use the Details Templates Editor in the Exchange Toolbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-DetailsTemplate [-Identity] [-Confirm] [-DomainController ] - [-Pages ] [-WhatIf] [] +Set-DetailsTemplate [-Identity] + [-Confirm] + [-DomainController ] + [-Pages ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,15 +47,10 @@ This example sets attributes for the User details template for the U.S. English 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 - - Group - - PublicFolder - - SearchDialog - - MailboxAgent - - Contact ```yaml @@ -71,8 +69,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -141,12 +138,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/Set-DeviceConditionalAccessPolicy.md new file mode 100644 index 0000000000..0bbba58e9e --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DeviceConditionalAccessPolicy.md @@ -0,0 +1,199 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DeviceConditionalAccessPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DeviceConditionalAccessPolicy cmdlet to modify mobile device conditional access policies in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### RetryDistribution +``` +Set-DeviceConditionalAccessPolicy [-Identity] + [-RetryDistribution] + [-Confirm] + [-WhatIf] + [] +``` + +### Identity +``` +Set-DeviceConditionalAccessPolicy [-Identity] + [-Comment ] + [-Enabled ] + [-Force] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DeviceConditionalAccessPolicy -Identity Executives -Enabled $false +``` + +This example disables the existing mobile device conditional access policy named Executives. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RetryDistribution +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/Set-DeviceConditionalAccessRule.md similarity index 82% rename from exchange/exchange-ps/exchange/devices/Set-DeviceConditionalAccessRule.md rename to exchange/exchange-ps/exchange/Set-DeviceConditionalAccessRule.md index 50388dcf18..f9e793ed4e 100644 --- a/exchange/exchange-ps/exchange/devices/Set-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/exchange/Set-DeviceConditionalAccessRule.md @@ -1,66 +1,92 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-deviceconditionalaccessrule -applicable: Office 365 Security & Compliance Center +online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconditionalaccessrule +applicable: Security & Compliance title: Set-DeviceConditionalAccessRule schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "o365scc-ps" --- # Set-DeviceConditionalAccessRule ## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). -Use the Set-DeviceConditionalAccessRule cmdlet to modify mobile device conditional access rules in the Security & Compliance Center. +Use the Set-DeviceConditionalAccessRule cmdlet to modify mobile device conditional access rules in Basic Mobility and Security in Microsoft 365. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-DeviceConditionalAccessRule [-Identity] -TargetGroups - [-AccountName ] [-AccountUserName ] [-AllowAppStore ] - [-AllowAssistantWhileLocked ] [-AllowConvenienceLogon ] - [-AllowDiagnosticSubmission ] [-AllowiCloudBackup ] - [-AllowiCloudDocSync ] [-AllowiCloudPhotoSync ] - [-AllowJailbroken ] [-AllowPassbookWhileLocked ] - [-AllowScreenshot ] [-AllowSimplePassword ] - [-AllowVideoConferencing ] [-AllowVoiceAssistant ] - [-AllowVoiceDialing ] [-AntiVirusSignatureStatus ] [-AntiVirusStatus ] + [-AccountName ] + [-AccountUserName ] + [-AllowAppStore ] + [-AllowAssistantWhileLocked ] + [-AllowConvenienceLogon ] + [-AllowDiagnosticSubmission ] + [-AllowiCloudBackup ] + [-AllowiCloudDocSync ] + [-AllowiCloudPhotoSync ] + [-AllowJailbroken ] + [-AllowPassbookWhileLocked ] + [-AllowScreenshot ] + [-AllowSimplePassword ] + [-AllowVideoConferencing ] + [-AllowVoiceAssistant ] + [-AllowVoiceDialing ] + [-AntiVirusSignatureStatus ] + [-AntiVirusStatus ] [-AppsRating ] [-AutoUpdateStatus ] - [-BluetoothEnabled ] [-CameraEnabled ] [-Confirm] [-DomainController ] - [-EmailAddress ] [-EnableRemovableStorage ] [-ExchangeActiveSyncHost ] - [-FirewallStatus ] [-ForceAppStorePassword ] - [-ForceEncryptedBackup ] [-MaxPasswordAttemptsBeforeWipe ] + [-BluetoothEnabled ] + [-CameraEnabled ] + [-Confirm] + [-DomainController ] + [-EmailAddress ] + [-EnableRemovableStorage ] + [-ExchangeActiveSyncHost ] + [-FirewallStatus ] + [-ForceAppStorePassword ] + [-ForceEncryptedBackup ] + [-MaxPasswordAttemptsBeforeWipe ] [-MaxPasswordGracePeriod ] [-MoviesRating ] - [-PasswordComplexity ] [-PasswordExpirationDays ] [-PasswordHistoryCount ] - [-PasswordMinComplexChars ] [-PasswordMinimumLength ] [-PasswordQuality ] - [-PasswordRequired ] [-PasswordTimeout ] [-PhoneMemoryEncrypted ] - [-RegionRatings ] [-RequireEmailProfile ] - [-SmartScreenEnabled ] [-SystemSecurityTLS ] + [-PasswordComplexity ] + [-PasswordExpirationDays ] + [-PasswordHistoryCount ] + [-PasswordMinComplexChars ] + [-PasswordMinimumLength ] + [-PasswordQuality ] + [-PasswordRequired ] + [-PasswordTimeout ] + [-PhoneMemoryEncrypted ] + [-RegionRatings ] + [-RequireEmailProfile ] + [-SmartScreenEnabled ] + [-SystemSecurityTLS ] [-TVShowsRating ] [-UserAccountControlStatus ] - [-WhatIf] [-WLANEnabled ] [-WorkFoldersSyncUrl ] [] + [-WhatIf] + [-WLANEnabled ] + [-WorkFoldersSyncUrl ] + [] ``` ## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. +The cmdlets in Basic Mobility and Security are described in the following list: +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. - DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). ## EXAMPLES @@ -74,13 +100,13 @@ This example modifies the specified mobile device conditional access rule to blo ## PARAMETERS ### -Identity -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. +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: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: True Position: 1 @@ -98,7 +124,7 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: True Position: Named @@ -111,14 +137,13 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -131,14 +156,13 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -151,22 +175,19 @@ Accept wildcard characters: False 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. - - $false: Access to the app store isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -179,9 +200,7 @@ Accept wildcard characters: False 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. - - $false: The voice assistant can't be used while devices are locked. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -190,7 +209,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -203,9 +222,7 @@ Accept wildcard characters: False The AllowConvenienceLogon parameter specifies whether to allow convenience logons on devices. Valid values for this parameter are: - $true: Convenience logons are allowed. - - $false: Convenience logons aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -214,7 +231,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -227,24 +244,20 @@ Accept wildcard characters: False The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic submissions from devices. Valid values for this parameter are: - $true: Diagnostic submissions are allowed. - - $false: Diagnostic submissions aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -257,22 +270,19 @@ Accept wildcard characters: False The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup from devices. Valid values for this parameter are: - $true: iCloud Backup is allowed. - - $false: iCloud Backup isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -285,22 +295,19 @@ Accept wildcard characters: False 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. - - $false: iCloud Documents & Data sync isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -313,22 +320,19 @@ Accept wildcard characters: False 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. - - $false: iCloud Photo sync isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -341,22 +345,19 @@ Accept wildcard characters: False The AllowJailbroken parameter specifies whether to allow access to your organization by jailbroken or rooted devices. - $true: Jailbroken devices are allowed. - - $false: Jailbroken devices aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -369,9 +370,7 @@ Accept wildcard characters: False 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. - - $false: Passbook isn't available while devices are locked. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -380,7 +379,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -393,22 +392,19 @@ Accept wildcard characters: False The AllowScreenshot parameter specifies whether to allow screenshots on devices. Valid values for this parameter are: - $true: Screenshots are allowed. - - $false: Screenshots aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -421,24 +417,20 @@ Accept wildcard characters: False 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. - - $false: Simple passwords aren't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -451,9 +443,7 @@ Accept wildcard characters: False The AllowVideoConferencing parameter specifies whether to allow video conferencing on devices. Valid values for this parameter are: - $true: Video conferencing is allowed. - - $false: Video conferencing isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -462,7 +452,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -475,9 +465,7 @@ Accept wildcard characters: False 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. - - $false: The voice assistant isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -486,7 +474,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -499,9 +487,7 @@ Accept wildcard characters: False The AllowVoiceDialing parameter specifies whether to allow voice-activated telephone dialing. Valid values for this parameter are: - $true: Voice dialing is allowed. - - $false: Voice dialing isn't allowed. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -510,7 +496,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -523,7 +509,6 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -532,7 +517,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -545,7 +530,6 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies antivirus status. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -554,7 +538,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -567,15 +551,10 @@ Accept wildcard characters: False The AppsRating parameter species the maximum or most restrictive rating of apps that are allowed on devices. Valid values for this parameter are: - AllowAll - - DontAllow - - Rating9plus - - Rating12plus - - Rating17plus - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -584,7 +563,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingAppsEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -597,15 +576,10 @@ Accept wildcard characters: False The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are: - AutomaticCheckForUpdates - - AutomaticDownloadUpdates - - AutomaticUpdatesRequired - - DeviceDefault - - NeverCheckUpdates - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -614,7 +588,7 @@ This setting is available only on Windows 8.1 RT devices. Type: CAAutoUpdateStatusEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -627,9 +601,7 @@ Accept wildcard characters: False The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth on devices. Valid values for this parameter are: - $true: Bluetooth is enabled. - - $false: Bluetooth is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows Phone 8.1 devices. @@ -638,7 +610,7 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -651,24 +623,20 @@ Accept wildcard characters: False The CameraEnabled parameter specifies whether to enable or disable cameras on devices. Valid values for this parameter are: - $true: Cameras are enabled. - - $false: Cameras are disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -680,15 +648,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -704,7 +671,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -717,14 +684,13 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -737,9 +703,7 @@ Accept wildcard characters: False The EnableRemovableStorage parameter specifies whether removable storage can be used by devices. Valid values for this parameter are: - $true: Removable storage can be used. - - $false: Removable storage can't be used. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows Phone 8.1 devices. @@ -748,7 +712,7 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -761,14 +725,13 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -781,7 +744,6 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -790,7 +752,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Required Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -803,9 +765,7 @@ Accept wildcard characters: False 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. - - $false: App store passwords aren't required. - - $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -814,7 +774,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -827,22 +787,19 @@ Accept wildcard characters: False The ForceEncryptedBackup parameter specifies whether to force encrypted backups for devices. Valid values for this parameter are: - $true: Encrypted backups are required. - - $false: Encrypted backups aren't required. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -855,24 +812,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -892,7 +845,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -902,130 +855,88 @@ Accept wildcard characters: False ``` ### -MoviesRating -The MoviesRating parameter species the maximum or most restrictive rating of movies that are allowed on devices. You specify the country rating system to use with the RegionRatings parameter. +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: - AllowAll: All movies are allowed, regardless of their rating. - - DontAllow: No movies are allowed, regardless of their rating. - - $null (blank): The setting isn't configured. This is the default value. Australia - AURatingG - - AURatingPG - - AURatingM - - AURatingMA15plus - - AURatingR18plus Canada - CARatingG - - CARatingPG - - CARating14A - - CARating18A - - CARatingR Germany - DERatingab0Jahren - - DERatingab6Jahren - - DERatingab12Jahren - - DERatingab16Jahren - - DERatingab18Jahren France - FRRating10minus - - FRRating12minus - - FRRating16minus - - FRRating18minus United Kingdom - GBRatingU - - GBRatingUc - - GBRatingPG - - GBRating12 - - GBRating12A - - GBRating15 - - GBRating18 Ireland - IERatingG - - IERatingPG - - IERating12 - - IERating15 - - IERating16 - - IERating18 Japan - JPRatingG - - JPRatingPG12 - - JPRatingRdash15 - - JPRatingRdash18 New Zealand - NZRatingG - - NZRatingPG - - NZRatingM - - NZRatingR13 - - NZRatingR15 - - NZRatingR16 - - NZRatingR18 - - NZRatingR United States - USRatingG - - USRatingPG - - USRatingPG13 - - USRatingR - - USRatingNC17 This setting is available only on Apple iOS 6+ devices. @@ -1034,7 +945,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingMovieEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1047,14 +958,13 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1067,24 +977,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1097,24 +1003,20 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1127,14 +1029,13 @@ Accept wildcard characters: False 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. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1147,24 +1048,20 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1179,7 +1076,6 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Android 4+ devices. @@ -1188,7 +1084,7 @@ This setting is available only on Android 4+ devices. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1201,24 +1097,20 @@ Accept wildcard characters: False The PasswordRequired parameter specifies whether a password is required to access devices. Valid values for this parameter are: - $true: Device passwords are required. - - $false: Device passwords aren't required. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 - - Apple iOS 6+ - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1233,11 +1125,8 @@ The PasswordTimeout parameter specifies the length of time that devices can be i This setting is available on the following types of devices: - Windows Phone 8.1 - - Windows 8.1 RT - - Apple iOS 6+ - - Android 4+ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1246,7 +1135,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1259,22 +1148,19 @@ Accept wildcard characters: False The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on devices. Valid values for this parameter are: - $true: Memory is encrypted. - - $false: Memory isn't encrypted. - - $null (blank): The setting isn't configured. This is the default value. This setting is available on the following types of devices: - Windows Phone 8.1 (already encrypted and can't be unencrypted) - - Android 4+ ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1284,28 +1170,19 @@ Accept wildcard characters: False ``` ### -RegionRatings -The RegionRatings parameter specifies the rating system (country) to use for movie and television ratings with the MoviesRating and TVShowsRating parameters. +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: - $null (blank): The setting isn't configured. This is the default value. - - au: Australia - - ca: Canada - - de: Germany - - fr: France - - gb: United Kingdom - - ie: Ireland - - jp: Japan - - nz: New Zealand - - us: United States This setting is available only on Apple iOS 6+ devices. @@ -1314,7 +1191,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingRegionEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1327,16 +1204,14 @@ Accept wildcard characters: False 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. - - $false: An email profile isn't required. - - $null (blank): The setting isn't configured. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1349,9 +1224,7 @@ Accept wildcard characters: False The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen on devices. Valid values for this parameter are: - $true: SmartScreen is enabled. - - $false: SmartScreen is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Windows 8.1 RT devices. @@ -1360,7 +1233,7 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1373,9 +1246,7 @@ Accept wildcard characters: False The SystemSecurityTLS parameter specifies whether TLS encryption is used on devices. Valid values for this parameter are: - $true: TLS encryption is used. - - $false: TLS encryption isn't used. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Apple iOS 6+ devices. @@ -1384,7 +1255,7 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1394,66 +1265,46 @@ Accept wildcard characters: False ``` ### -TVShowsRating -The TVShowsRating parameter species the maximum or most restrictive rating of television shows that are allowed on devices. You specify the country rating system to use with the RegionRatings parameter. +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: - AllowAll: All television shows are allowed, regardless of their rating. - - DontAllow: No televisions shows are allowed, regardless of their rating. - - $null (blank): The setting isn't configured. This is the default value. Australia - AURatingP - - AURatingC - - AURatingG - - AURatingPG - - AURatingM - - AURatingMA15plus - - AURatingAv15plus Canada - CARatingC - - CARatingC8 - - CARatingG - - CARatingPG - - CARating14plus - - CARating18plus Germany - DERatingab0Jahren - - DERatingab6Jahren - - DERatingab12Jahren - - DERatingab16Jahren - - DERatingab18Jahren France - FRRating10minus - - FRRating12minus - - FRRating16minus - - FRRating18minus United Kingdom @@ -1463,13 +1314,9 @@ United Kingdom Ireland - IERatingGA - - IERatingCh - - IERatingYA - - IERatingPS - - IERatingMA Japan @@ -1479,23 +1326,16 @@ Japan New Zealand - NZRatingG - - NZRatingPGR - - NZRatingAO United States - USRatingTVY - - USRatingTVY7 - - USRatingTVG - - USRatingTVPG - - USRatingTV14 - - USRatingTVMA This setting is available only on Apple iOS 6+ devices. @@ -1504,7 +1344,7 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingTvShowEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1517,13 +1357,9 @@ Accept wildcard characters: False 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. - - AlwaysNotify - - NeverNotify - - NotifyAppChanges - - NotifyAppChangesDoNotDimdesktop This setting is available only on Windows 8.1 RT devices. @@ -1532,7 +1368,7 @@ This setting is available only on Windows 8.1 RT devices. Type: CAUserAccountControlStatusEntry Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1542,13 +1378,13 @@ Accept wildcard characters: False ``` ### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. +The WhatIf switch doesn't work in Security & Compliance PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1561,9 +1397,7 @@ Accept wildcard characters: False The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid values for this parameter are: - $true: Wi-Fi is enabled. - - $false: Wi-Fi is disabled. - - $null (blank): The setting isn't configured. This is the default value. This setting is available only on Microsoft Windows Phone 8.1 devices. @@ -1572,7 +1406,7 @@ This setting is available only on Microsoft Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1584,7 +1418,7 @@ Accept wildcard characters: False ### -WorkFoldersSyncUrl 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. +Valid input for this parameter a URL. For example, `https://workfolders.contoso.com`. This setting is available only on Windows 8.1 RT devices. @@ -1592,7 +1426,7 @@ This setting is available only on Windows 8.1 RT devices. Type: String Parameter Sets: (All) Aliases: -Applicable: Office 365 Security & Compliance Center +Applicable: Security & Compliance Required: False Position: Named @@ -1606,12 +1440,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/Set-DeviceConfigurationPolicy.md new file mode 100644 index 0000000000..ed19ba795f --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DeviceConfigurationPolicy.md @@ -0,0 +1,199 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DeviceConfigurationPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DeviceConfigurationPolicy cmdlet to modify mobile device configuration policies in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### RetryDistribution +``` +Set-DeviceConfigurationPolicy [-Identity] + [-RetryDistribution] + [-Confirm] + [-WhatIf] + [] +``` + +### Identity +``` +Set-DeviceConfigurationPolicy [-Identity] + [-Comment ] + [-Enabled ] + [-Force] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DeviceConfigurationPolicy -Identity "Engineering Group" -Enabled $false +``` + +This example disables the mobile device configuration policy named Engineering Group. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RetryDistribution +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/Set-DeviceConfigurationRule.md similarity index 82% rename from exchange/exchange-ps/exchange/devices/Set-DeviceConfigurationRule.md rename to exchange/exchange-ps/exchange/Set-DeviceConfigurationRule.md index 62c7ae6ac2..3ea511f71e 100644 --- a/exchange/exchange-ps/exchange/devices/Set-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/exchange/Set-DeviceConfigurationRule.md @@ -1,66 +1,91 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-deviceconfigurationrule -applicable: Office 365 Security & Compliance Center +online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconfigurationrule +applicable: Security & Compliance title: Set-DeviceConfigurationRule schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "o365scc-ps" --- # Set-DeviceConfigurationRule ## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). -Use the Set-DeviceConfigurationRule cmdlet to modify mobile device configuration rules in the Security & Compliance Center. +Use the Set-DeviceConfigurationRule cmdlet to modify mobile device configuration rules in Basic Mobility and Security in Microsoft 365. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-DeviceConfigurationRule [-Identity] -TargetGroups - [-AccountName ] [-AccountUserName ] [-AllowAppStore ] - [-AllowAssistantWhileLocked ] [-AllowConvenienceLogon ] - [-AllowDiagnosticSubmission ] [-AllowiCloudBackup ] - [-AllowiCloudDocSync ] [-AllowiCloudPhotoSync ] - [-AllowPassbookWhileLocked ] [-AllowScreenshot ] - [-AllowSimplePassword ] [-AllowVideoConferencing ] - [-AllowVoiceAssistant ] [-AllowVoiceDialing ] - [-AntiVirusSignatureStatus ] [-AntiVirusStatus ] + [-AccountName ] + [-AccountUserName ] + [-AllowAppStore ] + [-AllowAssistantWhileLocked ] + [-AllowConvenienceLogon ] + [-AllowDiagnosticSubmission ] + [-AllowiCloudBackup ] + [-AllowiCloudDocSync ] + [-AllowiCloudPhotoSync ] + [-AllowPassbookWhileLocked ] + [-AllowScreenshot ] + [-AllowSimplePassword ] + [-AllowVideoConferencing ] + [-AllowVoiceAssistant ] + [-AllowVoiceDialing ] + [-AntiVirusSignatureStatus ] + [-AntiVirusStatus ] [-AppsRating ] [-AutoUpdateStatus ] - [-BluetoothEnabled ] [-CameraEnabled ] [-Confirm] [-DomainController ] - [-EmailAddress ] [-EnableRemovableStorage ] [-ExchangeActiveSyncHost ] - [-FirewallStatus ] [-ForceAppStorePassword ] - [-ForceEncryptedBackup ] [-MaxPasswordAttemptsBeforeWipe ] + [-BluetoothEnabled ] + [-CameraEnabled ] + [-Confirm] + [-DomainController ] + [-EmailAddress ] + [-EnableRemovableStorage ] + [-ExchangeActiveSyncHost ] + [-FirewallStatus ] + [-ForceAppStorePassword ] + [-ForceEncryptedBackup ] + [-MaxPasswordAttemptsBeforeWipe ] [-MaxPasswordGracePeriod ] [-MoviesRating ] - [-PasswordComplexity ] [-PasswordExpirationDays ] [-PasswordHistoryCount ] - [-PasswordMinComplexChars ] [-PasswordMinimumLength ] [-PasswordQuality ] - [-PasswordRequired ] [-PasswordTimeout ] [-PhoneMemoryEncrypted ] - [-RegionRatings ] [-RequireEmailProfile ] - [-SmartScreenEnabled ] [-SystemSecurityTLS ] + [-PasswordComplexity ] + [-PasswordExpirationDays ] + [-PasswordHistoryCount ] + [-PasswordMinComplexChars ] + [-PasswordMinimumLength ] + [-PasswordQuality ] + [-PasswordRequired ] + [-PasswordTimeout ] + [-PhoneMemoryEncrypted ] + [-RegionRatings ] + [-RequireEmailProfile ] + [-SmartScreenEnabled ] + [-SystemSecurityTLS ] [-TVShowsRating ] [-UserAccountControlStatus ] - [-WhatIf] [-WLANEnabled ] [-WorkFoldersSyncUrl ] [] + [-WhatIf] + [-WLANEnabled ] + [-WorkFoldersSyncUrl ] + [] ``` ## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. +The cmdlets in Basic Mobility and Security are described in the following list: +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. - DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). ## EXAMPLES @@ -74,13 +99,13 @@ This example modifies the specified mobile device configuration rule to block sc ## PARAMETERS ### -Identity -The Identity parameter specifies the mobile device configuration rule that you want to modify. The name of the rule uses the syntax \{\}. For example, Engineering Group{914f151c-394b-4da9-9422-f5a2f65dec30}.. +The Identity parameter specifies the mobile device configuration rule that you want to modify. The name of the rule uses the syntax `] + [-RetryDistribution] + [-Confirm] + [-WhatIf] + [] +``` + +### Identity +``` +Set-DeviceTenantPolicy [-Identity ] + [-Comment ] + [-Enabled ] + [-Force] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DeviceTenantPolicy -Enabled $false +``` + +This example disables your organization's mobile device tenant policy. + +## PARAMETERS + +### -RetryDistribution +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-DeviceTenantRule.md b/exchange/exchange-ps/exchange/Set-DeviceTenantRule.md new file mode 100644 index 0000000000..e931196275 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DeviceTenantRule.md @@ -0,0 +1,192 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DeviceTenantRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DeviceTenantRule cmdlet to modify your organization's mobile device tenant rule in Basic Mobility and Security in Microsoft 365. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DeviceTenantRule [-Identity] + [-ApplyPolicyTo ] + [-BlockUnsupportedDevices ] + [-Confirm] + [-DomainController ] + [-ExclusionList ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The cmdlets in Basic Mobility and Security are described in the following list: + +- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Exchange Online email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. +- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Microsoft 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in Basic Mobility and Security. +- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. +- Get-DevicePolicy: Returns all Basic Mobility and Security policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). + +For more information about Basic Mobility and Security, see [Overview of Basic Mobility and Security for Microsoft 365](https://learn.microsoft.com/microsoft-365/admin/basic-mobility-security/overview). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DeviceTenantRule -ExclusionList "Research and Development" +``` + +This example modifies your organization's mobile device tenant rule by replacing the current exclusion list with the security group named Research and Development. Members of this group are allowed access even if they use non-compliant devices. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ApplyPolicyTo +The ApplyPolicyTo parameter specifies where to apply the policy in your organization. Valid values for this parameter are: + +- ExchangeOnline +- SharePointOnline +- ExchangeAndSharePoint + +```yaml +Type: PolicyResourceScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockUnsupportedDevices +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. +- $false: Unsupported devices are allowed. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExclusionList +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. + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-DistributionGroup.md b/exchange/exchange-ps/exchange/Set-DistributionGroup.md similarity index 81% rename from exchange/exchange-ps/exchange/users-and-groups/Set-DistributionGroup.md rename to exchange/exchange-ps/exchange/Set-DistributionGroup.md index ba5cc05be4..7d84dcf397 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-DistributionGroup.md +++ b/exchange/exchange-ps/exchange/Set-DistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-distributiongroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-DistributionGroup @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-DistributionGroup cmdlet to modify the settings of existing distribution groups or mail-enabled security groups. To add or remove group members, use the Add-DistributionGroupMember, Remove-DistributionGroupMember or Update-DistributionGroupMember cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,6 +27,7 @@ Set-DistributionGroup [-Identity] [-AcceptMessagesOnlyFromSendersOrMembers ] [-Alias ] [-ArbitrationMailbox ] + [-BccBlocked ] [-BypassModerationFromSendersOrMembers ] [-BypassNestedModerationEnabled ] [-BypassSecurityGroupManagerCheck] @@ -48,6 +48,7 @@ Set-DistributionGroup [-Identity] [-CustomAttribute7 ] [-CustomAttribute8 ] [-CustomAttribute9 ] + [-Description ] [-DisplayName ] [-DomainController ] [-EmailAddresses ] @@ -61,6 +62,7 @@ Set-DistributionGroup [-Identity] [-ForceUpgrade] [-GrantSendOnBehalfTo ] [-HiddenFromAddressListsEnabled ] + [-HiddenGroupMembershipEnabled] [-IgnoreDefaultScope] [-IgnoreNamingPolicy] [-MailTip ] @@ -87,6 +89,7 @@ Set-DistributionGroup [-Identity] [-SendOofMessageToOriginatorEnabled ] [-SimpleDisplayName ] [-UMDtmfMap ] + [-UpdateMemberCount] [-WhatIf] [-WindowsEmailAddress ] [] @@ -95,7 +98,7 @@ Set-DistributionGroup [-Identity] ## DESCRIPTION Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Distribution groups aren't security principals, and therefore can't be assigned permissions. However, you can assign permissions to mail-enabled security groups. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -126,15 +129,10 @@ This example changes the name of an existing distribution group from Ed\_DirectR 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -156,20 +154,15 @@ The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages t 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -194,20 +187,15 @@ The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send m 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -234,20 +222,15 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. +To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromDLMembers parameters. The individual senders and groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromDLMembers properties, respectively. Therefore, you can't use the AcceptMessagesOnlyFromSendersOrMembers parameter and the AcceptMessagesOnlyFrom or AcceptMessagesOnlyFromDLMembers parameters in the same command. @@ -267,16 +250,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -302,23 +289,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -334,26 +312,42 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -BccBlocked +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: + +- $true: If the group is used in the Bcc line, members of the group don't receive the message, and the sender receives a non-delivery report (also known as an NDR or bounce message). Other recipients of the message aren't blocked. If an external sender uses the group in the Bcc line, members of the group aren't blocked. For nested groups, the message is blocked only for members of the top-level group. +- $false: There are no restrictions for using the group in the Bcc line of messages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -BypassModerationFromSendersOrMembers 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +To enter multiple senders and overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more senders without affecting any existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. @@ -374,7 +368,6 @@ Accept wildcard characters: False 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. - - $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This is the default value. ```yaml @@ -391,14 +384,13 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. 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: +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. -- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +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: +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. - Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. -You don't need to specify a value with this switch. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -415,8 +407,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -433,17 +424,18 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap +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: - $true: A DTMF map is created for the recipient. This is the default value. - - $false: A DTMF map isn't created for the recipient. ```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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -692,6 +684,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Description +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DisplayName 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 ("). @@ -729,33 +739,28 @@ Accept wildcard characters: False ``` ### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). +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 \:\,\:\,...\:\. The optional \ value specifies the type of email address. Some examples of valid values include: +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: - SMTP: The primary SMTP address. You can use this value only once in a command. - - smtp: Other SMTP email addresses. - - X400: X.400 addresses in on-premises Exchange. - - X500: X.500 addresses in on-premises Exchange. -If you don't include a \ value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. To specify the primary SMTP email address, you can use any of the following methods: -- Use the \ value SMTP on the address. - -- The first email address when you don't use any \ values, or when you use multiple \ values of smtp. - +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. - Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\:\","\:\",..."\:\". +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\:\","\:\",...; Remove="\:\","\:\",...}. +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. ```yaml Type: ProxyAddressCollection @@ -776,7 +781,6 @@ 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: - $true: Email address policies are applied to this recipient. This is the default value. - - $false: Email address policies aren't applied to this recipient. ```yaml @@ -800,10 +804,9 @@ The ExpansionServer parameter specifies the Exchange server that's used to expan You can specify the following types of servers as expansion servers: - An Exchange 2013 or later Mailbox server. - - An Exchange 2010 Hub Transport server. -When you specify an expansion server, use the ExchangeLegacyDN. You can find this value by running the command: Get-ExchangeServer \ | Format-List ExchangeLegacyDN. An example value for this parameter is "/o=Contoso/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01". +When you specify an expansion server, use the ExchangeLegacyDN. You can find this value by running the command: `Get-ExchangeServer | Format-List ExchangeLegacyDN`. An example value for this parameter is "/o=Contoso/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01". ```yaml Type: String @@ -821,9 +824,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute1 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -843,9 +846,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute2 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -865,9 +868,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute3 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -887,9 +890,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute4 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -909,9 +912,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute5 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -929,7 +932,7 @@ Accept wildcard characters: False ``` ### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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. +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 @@ -945,33 +948,24 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo -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 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. By default, this parameter is blank, which means no one else has permission to send on behalf of this group. @@ -992,7 +986,6 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. - - $false: The recipient is visible in address lists. This is the default value. ```yaml @@ -1008,15 +1001,36 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -HiddenGroupMembershipEnabled +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. + +You can use this setting to help comply with regulations that require you to hide group membership from members or outsiders (for example, a distribution group that represents students enrolled in a class). + +**Note**: If you hide the membership of the group with this parameter, you can't edit the group later to reveal the membership to the group. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -1055,9 +1069,8 @@ The MailTip parameter specifies the custom MailTip text for this recipient. The When you add a MailTip to a recipient, two things happen: -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \\This mailbox is not monitored\\. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `This mailbox is not monitored`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. ```yaml Type: String @@ -1077,11 +1090,11 @@ The MailTipTranslations parameter specifies additional languages for the custom To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: -@{Add="\:\","\:\"...; Remove="\:\","\:\"...} +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. -\ is a valid ISO 639 two-letter culture code that's associated with the language. +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. ```yaml Type: MultiValuedProperty @@ -1100,42 +1113,36 @@ Accept wildcard characters: False 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 - - Add or remove group members - - Delete the group - - Approve member depart or join requests (if available) - - Approve messages sent to the group if moderation is enabled, but no moderators are specified. -The owner 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 owner. For example: +The owner 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). -- Name +Considerations for mail-enabled security groups as group owners: -- Alias +- If you specify a mail-enabled security group as a group owner in on-premises Exchange, the mail-enabled security group doesn't sync to the cloud object. +- Group management in Outlook doesn't work if the owner is a mail-enabled security group. To manage the group in Outlook, the owner must be a mailbox or a mail user. If you specify a mail-enabled security group as the owner of the group, the group isn't visible in **Distribution groups I own** for the group owners (members of the mail-enabled security group). -- Distinguished name (DN) +You can use any value that uniquely identifies the owner. For example: +- Name +- Alias +- Distinguished name (DN) - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple owners and overwrite all existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +To enter multiple owners and overwrite all existing entries, use the following syntax: `Owner1,Owner2,...OwnerN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Owner1","Owner2",..."OwnerN"`. -To add or remove owners without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove owners without affecting other existing entries, use the following syntax: `@{Add="Owner1","Owner2",...; Remove="Owner3","Owner4"...}`. -An owner that you specify with this parameter isn't automatically a member of the group. You need to manually add the owner as a member. +Owners that you specify with this parameter are not added as group members. You need to manually add the owner as a member. ```yaml Type: MultiValuedProperty @@ -1158,18 +1165,15 @@ The MaxReceiveSize parameter specifies the maximum size of an email message that When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1192,18 +1196,15 @@ The MaxSendSize parameter specifies the maximum size of an email message that ca When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1222,7 +1223,6 @@ Accept wildcard characters: False 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. - - Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This is the default value for universal security groups. ```yaml @@ -1242,9 +1242,7 @@ Accept wildcard characters: False 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. - - Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This is the default value on universal security groups and universal distribution groups. - - ApprovalRequired: Users can request to join the group. The user is added to the group after the request is approved by one of the group owners. Although you can use this value on universal security groups, user requests to join the group aren't sent to the group owners, so this setting is only effective on universal distribution groups. ```yaml @@ -1264,20 +1262,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. For mail-enabled security groups, you need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -1300,7 +1293,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -1337,7 +1329,7 @@ Accept wildcard characters: False ### -PrimarySmtpAddress 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 that means the email addresses of the mail user no longer automatically updated by email address policies. +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. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. @@ -1360,20 +1352,15 @@ The RejectMessagesFrom parameter specifies who isn't allowed to send messages to 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1398,20 +1385,15 @@ The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send me 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1438,18 +1420,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. @@ -1471,11 +1448,10 @@ Accept wildcard characters: False ``` ### -ReportToManagerEnabled -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: +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 owners of the group. - -- $false: Delivery status notifications aren't sent to the owners of the group. This is the default value. +- $true: Delivery status notifications are sent to the owner (first one listed if more than one) of the group. +- $false: Delivery status notifications aren't sent to the owner (first one listed if more than one) of the group. This is the default value. The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true. @@ -1496,7 +1472,6 @@ Accept wildcard characters: False 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. - - $false: Delivery status notifications aren't sent to the message senders. The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true. @@ -1518,7 +1493,6 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. ```yaml @@ -1537,7 +1511,7 @@ Accept wildcard characters: False ### -ResetMigrationToUnifiedGroup 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 an Office 365 Group is in progress. You don't need to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -1573,7 +1547,7 @@ Accept wildcard characters: False ### -SamAccountName 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 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. +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 @@ -1592,9 +1566,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -1616,7 +1588,6 @@ Accept wildcard characters: False 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. - - $false: When messages are sent to the group, OOF messages for any of the group members aren't sent to the message sender. This is the default value. ```yaml @@ -1636,12 +1607,10 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". +- space +- `" ' ( ) + , - . / : ?` ```yaml Type: String @@ -1657,27 +1626,45 @@ Accept wildcard characters: False ``` ### -UMDtmfMap +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: -- emailAddress:\ +- `emailAddress:` +- `lastNameFirstName:` +- `firstNameLastName:` + +To enter values that overwrite all existing entries, use the following syntax: `emailAddress:,lastNameFirstName:,firstNameLastName:`. -- lastNameFirstName:\ +If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only `emailAddress:`, all existing lastNameFirstName and firstNameLastName values are removed. -- firstNameLastName:\ +To add or remove values without affecting other existing entries, use the following syntax: `@{Add="emailAddress:","lastNameFirstName:","firstNameLastName:"; Remove="emailAddress:","lastNameFirstName:","firstNameLastName:"}`. -To enter values that overwrite all existing entries, use the following syntax: emailAddress:\,lastNameFirstName:\,firstNameLastName:\. +If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use `@{Add="emailAddress:","emailAddress:}` to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:\, all existing lastNameFirstName and firstNameLastName values are removed. +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` -To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"; Remove="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"}. +### -UpdateMemberCount +This parameter is available only in the cloud-based service. -If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:\","emailAddress:\} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. +{{ Fill UpdateMemberCount Description }} ```yaml -Type: MultiValuedProperty +Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1706,7 +1693,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -1729,12 +1715,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-DkimSigningConfig.md b/exchange/exchange-ps/exchange/Set-DkimSigningConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-DkimSigningConfig.md rename to exchange/exchange-ps/exchange/Set-DkimSigningConfig.md index 61d79e903c..f2b0ed064b 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-DkimSigningConfig.md +++ b/exchange/exchange-ps/exchange/Set-DkimSigningConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-dkimsigningconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Set-DkimSigningConfig @@ -17,18 +16,24 @@ This cmdlet is available only in the cloud-based service. Use the Set-DkimSigningConfig cmdlet to modify the DomainKeys Identified Mail (DKIM) signing policy settings for domains in a cloud-based organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-DkimSigningConfig [-Identity] [-AdminDisplayName ] - [-BodyCanonicalization ] [-Confirm] [-Enabled ] - [-HeaderCanonicalization ] [-PublishTxtRecords] [-WhatIf] [] +Set-DkimSigningConfig [-Identity] + [-AdminDisplayName ] + [-BodyCanonicalization ] + [-Confirm] + [-Enabled ] + [-HeaderCanonicalization ] + [-PublishTxtRecords] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,9 +50,7 @@ This example disables the DKIM signing policy for the contoso.com domain. 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). - - Distinguished name (DN) - - GUID ```yaml @@ -83,7 +86,6 @@ Accept wildcard characters: False 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. - - Simple: Only changes in empty lines at the end of the message body are tolerated. ```yaml @@ -102,8 +104,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,7 +124,6 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: - $true: The policy is enabled. This is the default value. - - $false: The policy is disabled. ```yaml @@ -143,7 +143,6 @@ Accept wildcard characters: False 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. - - Simple: No changes to the header fields are tolerated. ```yaml @@ -198,12 +197,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md new file mode 100644 index 0000000000..ef3708c0cf --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md @@ -0,0 +1,1375 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DlpCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DlpCompliancePolicy cmdlet to modify data loss prevention (DLP) policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Set-DlpCompliancePolicy [-Identity] + [-AddEndpointDlpLocation ] + [-AddEndpointDlpLocationException ] + [-AddExchangeLocation ] + [-AddOneDriveLocation ] + [-AddOneDriveLocationException ] + [-AddOnPremisesScannerDlpLocation ] + [-AddOnPremisesScannerDlpLocationException ] + [-AddPowerBIDlpLocation ] + [-AddPowerBIDlpLocationException ] + [-AddSharePointLocation ] + [-AddSharePointLocationException ] + [-AddTeamsLocation ] + [-AddTeamsLocationException ] + [-AddThirdPartyAppDlpLocation ] + [-AddThirdPartyAppDlpLocationException ] + [-Comment ] + [-Confirm] + [-EndpointDlpAdaptiveScopes ] + [-EndpointDlpAdaptiveScopesException ] + [-EndpointDlpExtendedLocations ] + [-EnforcementPlanes ] + [-ExceptIfOneDriveSharedBy ] + [-ExceptIfOneDriveSharedByMemberOf ] + [-ExchangeAdaptiveScopes ] + [-ExchangeAdaptiveScopesException ] + [-ExchangeSenderMemberOf ] + [-ExchangeSenderMemberOfException ] + [-Force] + [-IsFromSmartInsights ] + [-Locations ] + [-Mode ] + [-OneDriveAdaptiveScopes ] + [-OneDriveAdaptiveScopesException ] + [-OneDriveSharedBy ] + [-OneDriveSharedByMemberOf ] + [-PolicyRBACScopes ] + [-PolicyTemplateInfo ] + [-Priority ] + [-RemoveEndpointDlpLocation ] + [-RemoveEndpointDlpLocationException ] + [-RemoveExchangeLocation ] + [-RemoveOneDriveLocation ] + [-RemoveOneDriveLocationException ] + [-RemoveOnPremisesScannerDlpLocation ] + [-RemoveOnPremisesScannerDlpLocationException ] + [-RemovePowerBIDlpLocation ] + [-RemovePowerBIDlpLocationException ] + [-RemoveSharePointLocation ] + [-RemoveSharePointLocationException ] + [-RemoveTeamsLocation ] + [-RemoveTeamsLocationException ] + [-RemoveThirdPartyAppDlpLocation ] + [-RemoveThirdPartyAppDlpLocationException ] + [-SharePointAdaptiveScopes ] + [-SharePointAdaptiveScopesException ] + [-StartSimulation ] + [-TeamsLocation ] + [-TeamsLocationException ] + [-WhatIf] + [] +``` + +### RetryDistribution +``` +Set-DlpCompliancePolicy [-Identity] [-RetryDistribution] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +**Note**: Don't use a piped Foreach-Object command when adding or removing scope locations: `"Value1","Value2",..."ValueN" | Foreach-Object {Set-DlpCompliancePolicy -Identity "Main PII" -RemoveExchangeLocation $_}`. + +## EXAMPLES + +### Example 1 +```powershell +Set-DlpCompliancePolicy -Identity "Main PII" -AddSharePointLocation "https://my.url1/","https://my.url2/" -AddOneDriveLocation "https://my.url3/","https://my.url4/" +``` + +This example adds the specified URLs to the SharePoint and OneDrive locations for the DLP policy named Main PII without affecting the existing URL values. + +### Example 2 +```powershell +Set-DlpCompliancePolicy -Identity MainPII -Mode Disable +``` + +This example disables the "MainPII" policy. + +### Example 3 +```powershell +Set-DlpCompliancePolicy -Identity "PowerBIPolicy" -AddPowerBILocation "workspaceID1","workspaceID2","workspaceID3" +``` + +This example adds the specified workspace IDs to the Power BI location for the DLP policy named PowerBIPolicy without affecting the existing workspace IDs. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RetryDistribution +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. + +**Note**: Because the process of retrying distribution is a significant operation, run it only if necessary and for one policy at a time. It is not intended to be run every time you update a policy. If you run a script to update multiple policies, wait until the policy distribution is successful before running the command again for the next policy. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddEndpointDlpLocation +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddEndpointDlpLocationException +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocation +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: + +- If you use `-AddExchangeLocation All` by itself, the policy applies to email for all users. + +- To include email of specific group members in the policy, use `-AddExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the policy. + +- To exclude email of specific group members from the policy, use `-AddExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the policy. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocation +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: + +- If you use `-AddOneDriveLocation All` by itself, the policy applies to all OneDrive sites. + +- To include sites of specific OneDrive accounts in the policy, use `-AddOneDriveLocation All` and the OneDriveSharedBy parameter to specify the users. Only the sites of the specified users are included in the policy. + +- To include sites of specific group members in the policy, use `-AddOneDriveLocation All` and the OneDriveSharedByMemberOf parameter to specify the groups. Only the sites of members of the specified groups are included in the policy. + +- To exclude sites of specific OneDrive accounts from the policy, use `-AddOneDriveLocation All` and the ExceptIfOneDriveSharedBy parameter to specify the users. Only sites of the specified users are excluded from the policy. + +- To exclude sites of specific group members from the policy, use `-AddOneDriveLocation All` and the ExceptIfOneDriveSharedByMemberOf parameter to specify the groups. Only sites of members of the specified groups are excluded from the policy. + +You can't specify inclusions and exclusions in the same policy. + +**Note**: Although this parameter accepts site URLs, don't specify site URLs values. Use the OneDriveSharedBy, ExceptIfOneDriveShareBy, OneDriveSharedByMemberOf, and ExceptIfOneDriveSharedByMemberOf parameters instead. In the DLP policy settings in the Microsoft Defender portal, you can't specify sites to include or exclude by URL; you specify sites to include or exclude only by users or groups. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocationException +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOnPremisesScannerDlpLocation +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: `"","",...""`. + +For more information about the DLP on-premises scanner, see [Learn about the data loss prevention on-premises scanner](https://learn.microsoft.com/purview/dlp-on-premises-scanner-learn). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOnPremisesScannerDlpLocationException +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: `"","",...""`. + +For more information about the DLP on-premises scanner, see [Learn about the data loss prevention on-premises scanner](https://learn.microsoft.com/purview/dlp-on-premises-scanner-learn). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddPowerBIDlpLocation +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: + +- In the Admin portal, choose **Workspaces**, then select a workspace and choose **\> More options (...) \> Details**. +- Look in the URL of a selected workspace. +- In PowerShell, use the command **Get-PowerBIWorkspace**. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddPowerBIDlpLocationException +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: + +- In the Admin portal, choose **Workspaces**, then select a workspace and choose **\> More options (...) \> Details**. +- Look in the URL of a selected workspace. +- In PowerShell, use the command **Get-PowerBIWorkspace**. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocation +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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocationException +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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddTeamsLocation +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddTeamsLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddThirdPartyAppDlpLocation +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about DLP for non-Microsoft cloud apps, see [Use data loss prevention policies for non-Microsoft cloud apps](https://learn.microsoft.com/purview/dlp-use-policies-non-microsoft-cloud-apps). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddThirdPartyAppDlpLocationException +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about DLP for non-Microsoft cloud apps, see [Use data loss prevention policies for non-Microsoft cloud apps](https://learn.microsoft.com/purview/dlp-use-policies-non-microsoft-cloud-apps). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpAdaptiveScopes +{{ Fill EndpointDlpAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpAdaptiveScopesException +{{ Fill EndpointDlpAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpExtendedLocations +{{ Fill EndpointDlpExtendedLocations Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnforcementPlanes +The EnforcementPlanes parameter defines the layer where policy actions are run. This parameter uses the following syntax: + +`-EnforcementPlanes @("")`. + +Currently, the only supported value is Entra, for use with policies applied to an Entra-registered enterprise application in the organization. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedBy +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: + +- The policy already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value). +- Use `-AddOneDriveLocation All` in the same command with this parameter. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfOneDriveSharedByMemberOf +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: + +- The policy already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value). +- Use `-AddOneDriveLocation All` in the same command with this parameter. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopes +{{ Fill ExchangeAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeAdaptiveScopesException +{{ Fill ExchangeAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOf +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: `"","",...""`. + +To use this parameter, one of the following statements must be true: + +- The policy already includes email messages (in the output of Get-DlpCOmpliancePolicy, the ExchangeLocation property value is All). +- Use `-AddExchangeLocation All` in the same command with this parameter. + +You can't use this parameter with the ExchangeSenderMemberOfException parameter. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeSenderMemberOfException +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: `"","",...""`. + +To use this parameter, one of the following statements must be true: + +- The policy already includes email messages (in the output of Get-DlpCOmpliancePolicy, the ExchangeLocation property value is All). +- Use `-AddExchangeLocation All` in the same command with this parameter. + +You can't use this parameter with the ExchangeSenderMemberOf parameter. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsFromSmartInsights +{{ Fill IsFromSmartInsights Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locations +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`. +- Location: Where the DLP policy applies. For Microsoft 365 Copilot, (Preview), use the value `470f2276-e011-4e9d-a6ec-20768be3a4b0`. +- AddInclusions or RemoveInclusions: Add or remove security groups, distribution groups, or users to or from the scope of this DLP policy. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:}`. For security groups or distribution groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group,Identity:}`. +- AddExclusions or RemoveExclusions: Add or remove security groups, distribution groups, or users to or from exclusions to the scope of this DLP policy. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:}`. For security groups or distribution groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group,Identity:}`. + +You create and store the properties in a variable as shown in the following examples: + +DLP policy scoped to all users in the tenant: + +`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","AddInclusions":[{Type:"Tenant",Identity:"All"}]}]"` + +DLP policy scoped to the specified user and groups: + +`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","AddInclusions":[{"Type":"Group","Identity":"fef0dead-5668-4bfb-9fc2-9879a47f9bdb"},{"Type":"Group","Identity":"b4dc1e1d-8193-4525-b59c-6d6e0f1718d2"},{"Type":"IndividualResource","Identity":"yibing@contoso.com"}]}]"` + +DLP policy scoped to all users in the tenant except for members of the specified group: + +`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","AddInclusions":[{Type:"Tenant",Identity:"All"}],"AddExclusions": [{"Type":"Group","Identity":"fef0dead-5668-4bfb-9fc2-9879a47f9bdb"},{"Type":"Group","Identity":"b4dc1e1d-8193-4525-b59c-6d6e0f1718d2"}]}]` + +After you create the `$loc` variable as shown in the previous examples, use the value `$loc` for this parameter. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mode +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. +- Disable: The policy is disabled. +- TestWithNotifications: Simulation mode where no actions are taken, but notifications **are** sent. +- TestWithoutNotifications: Simulation mode where no actions are taken, and no notifications are sent. + +```yaml +Type: PolicyMode +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopes +{{ Fill OneDriveAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAdaptiveScopesException +{{ Fill OneDriveAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedBy +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: + +- The policy already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value). +- Use `-AddOneDriveLocation All` in the same command with this parameter. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveSharedByMemberOf +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: + +- The policy already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value). +- Use `-AddOneDriveLocation All` in the same command with this parameter. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters. + +You can't use this parameter to specify Microsoft 365 Groups. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTemplateInfo +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). + +```yaml +Type: PswsHashtable +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 5 policies are from 0 through 4. +- Valid priority values for a new 6th policy are from 0 through 5. +- The default value for a new 6th policy is 5. + +If you modify the priority value of a policy, the position of the policy in the list changes to match the priority value you specify. In other words, if you set the priority value of a policy to the same value as an existing policy, the priority value of the existing policy and all other lower priority policies after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveEndpointDlpLocation +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveEndpointDlpLocationException +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocation +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. + +**Note**: Although this parameter accepts site URLs, don't specify site URLs values. Use the OneDriveSharedBy, ExceptIfOneDriveShareBy, OneDriveSharedByMemberOf, and ExceptIfOneDriveSharedByMemberOf parameters instead. In the DLP policy settings in the Microsoft Defender portal, you can't specify sites to include or exclude by URL; you specify sites to include or exclude only by users or groups. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocationException +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOnPremisesScannerDlpLocation +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: `"","",...""`. + +For more information about the DLP on-premises scanner, see [Learn about the data loss prevention on-premises scanner](https://learn.microsoft.com/purview/dlp-on-premises-scanner-learn). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOnPremisesScannerDlpLocationException +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: `"","",...""`. + +For more information about the DLP on-premises scanner, see [Learn about the data loss prevention on-premises scanner](https://learn.microsoft.com/purview/dlp-on-premises-scanner-learn). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePowerBIDlpLocation +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: + +- In the Admin portal, choose **Workspaces**, then select a workspace and choose **\> More options (...) \> Details**. +- Look in the URL of a selected workspace. +- In PowerShell, use the command **Get-PowerBIWorkspace**. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePowerBIDlpLocationException +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: + +- In the Admin portal, choose **Workspaces**, then select a workspace and choose **\> More options (...) \> Details**. +- Look in the URL of a selected workspace. +- In PowerShell, use the command **Get-PowerBIWorkspace**. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocation +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveTeamsLocation +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveTeamsLocationException +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: `"","",...""`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveThirdPartyAppDlpLocation +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about DLP for non-Microsoft cloud apps, see [Use data loss prevention policies for non-Microsoft cloud apps](https://learn.microsoft.com/purview/dlp-use-policies-non-microsoft-cloud-apps). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveThirdPartyAppDlpLocationException +**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. + +To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. + +For more information about DLP for non-Microsoft cloud apps, see [Use data loss prevention policies for non-Microsoft cloud apps](https://learn.microsoft.com/purview/dlp-use-policies-non-microsoft-cloud-apps). + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopes +{{ Fill SharePointAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharePointAdaptiveScopesException +{{ Fill SharePointAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartSimulation +{{ Fill StartSimulation Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAdaptiveScopes +{{ Fill TeamsAdaptiveScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAdaptiveScopesException +{{ Fill TeamsAdaptiveScopesException Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md b/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md new file mode 100644 index 0000000000..4a833c4d4b --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md @@ -0,0 +1,3495 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DlpComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DlpComplianceRule to modify data loss prevention (DLP) rules in the Microsoft Purview compliance portal. DLP rules define sensitive information to be protected and the actions to take on rule violations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DlpComplianceRule [-Identity] + [-AccessScope ] + [-ActivationDate ] + [-AddRecipients ] + [-AdvancedRule ] + [-AlertProperties ] + [-AnyOfRecipientAddressContainsWords ] + [-AnyOfRecipientAddressMatchesPatterns ] + [-ApplyBrandingTemplate ] + [-ApplyHtmlDisclaimer ] + [-AttachmentIsNotLabeled ] + [-BlockAccess ] + [-BlockAccessScope ] + [-Comment ] + [-Confirm] + [-ContentCharacterSetContainsWords ] + [-ContentContainsSensitiveInformation ] + [-ContentExtensionMatchesWords ] + [-ContentFileTypeMatches ] + [-ContentIsNotLabeled ] + [-ContentIsShared ] + [-ContentPropertyContainsWords ] + [-Disabled ] + [-DocumentContainsWords ] + [-DocumentCreatedBy ] + [-DocumentCreatedByMemberOf ] + [-DocumentIsPasswordProtected ] + [-DocumentIsUnsupported ] + [-DocumentMatchesPatterns ] + [-DocumentNameMatchesPatterns ] + [-DocumentNameMatchesWords ] + [-DocumentSizeOver ] + [-DomainCountOver ] + [-EncryptRMSTemplate ] + [-EndpointDlpBrowserRestrictions ] + [-EndpointDlpRestrictions ] + [-EnforcePortalAccess ] + [-EvaluateRulePerComponent ] + [-ExceptIfAccessScope ] + [-ExceptIfAnyOfRecipientAddressContainsWords ] + [-ExceptIfAnyOfRecipientAddressMatchesPatterns ] + [-ExceptIfContentCharacterSetContainsWords ] + [-ExceptIfContentContainsSensitiveInformation ] + [-ExceptIfContentExtensionMatchesWords ] + [-ExceptIfContentFileTypeMatches ] + [-ExceptIfContentIsShared ] + [-ExceptIfContentPropertyContainsWords ] + [-ExceptIfDocumentContainsWords ] + [-ExceptIfDocumentCreatedBy ] + [-ExceptIfDocumentCreatedByMemberOf ] + [-ExceptIfDocumentIsPasswordProtected ] + [-ExceptIfDocumentIsUnsupported ] + [-ExceptIfDocumentMatchesPatterns ] + [-ExceptIfDocumentNameMatchesPatterns ] + [-ExceptIfDocumentNameMatchesWords ] + [-ExceptIfDocumentSizeOver ] + [-ExceptIfFrom ] + [-ExceptIfFromAddressContainsWords ] + [-ExceptIfFromAddressMatchesPatterns ] + [-ExceptIfFromMemberOf ] + [-ExceptIfFromScope ] + [-ExceptIfHasSenderOverride ] + [-ExceptIfHeaderContainsWords ] + [-ExceptIfHeaderMatchesPatterns ] + [-ExceptIfMessageSizeOver ] + [-ExceptIfMessageTypeMatches ] + [-ExceptIfProcessingLimitExceeded ] + [-ExceptIfRecipientADAttributeContainsWords ] + [-ExceptIfRecipientADAttributeMatchesPatterns ] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSenderADAttributeContainsWords ] + [-ExceptIfSenderADAttributeMatchesPatterns ] + [-ExceptIfSenderDomainIs ] + [-ExceptIfSenderIPRanges ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-ExceptIfSubjectContainsWords ] + [-ExceptIfSubjectMatchesPatterns ] + [-ExceptIfSubjectOrBodyContainsWords ] + [-ExceptIfSubjectOrBodyMatchesPatterns ] + [-ExceptIfUnscannableDocumentExtensionIs ] + [-ExceptIfWithImportance ] + [-ExpiryDate ] + [-From ] + [-FromAddressContainsWords ] + [-FromAddressMatchesPatterns ] + [-FromMemberOf ] + [-FromScope ] + [-GenerateAlert ] + [-GenerateIncidentReport ] + [-HasSenderOverride ] + [-HeaderContainsWords ] + [-HeaderMatchesPatterns ] + [-IncidentReportContent ] + [-MessageIsNotLabeled ] + [-MessageSizeOver ] + [-MessageTypeMatches ] + [-MipRestrictAccess ] + [-Moderate ] + [-ModifySubject ] + [-NonBifurcatingAccessScope ] + [-NotifyAllowOverride ] + [-NotifyEmailCustomSenderDisplayName ] + [-NotifyEmailCustomSubject ] + [-NotifyEmailCustomText ] + [-NotifyEmailExchangeIncludeAttachment ] + [-NotifyEmailOnedriveRemediationActions ] + [-NotifyEndpointUser ] + [-NotifyOverrideRequirements ] + [-NotifyPolicyTipCustomDialog ] + [-NotifyPolicyTipCustomText ] + [-NotifyPolicyTipCustomTextTranslations ] + [-NotifyPolicyTipDisplayOption ] + [-NotifyPolicyTipUrl ] + [-NotifyUser ] + [-NotifyUserType ] + [-OnPremisesScannerDlpRestrictions ] + [-PrependSubject ] + [-Priority ] + [-ProcessingLimitExceeded ] + [-Quarantine ] + [-RecipientADAttributeContainsWords ] + [-RecipientADAttributeMatchesPatterns ] + [-RecipientCountOver ] + [-RecipientDomainIs ] + [-RedirectMessageTo ] + [-RemoveHeader ] + [-RemoveRMSTemplate ] + [-ReportSeverityLevel ] + [-RestrictAccess ] + [-RestrictBrowserAccess ] + [-RuleErrorAction ] + [-SenderADAttributeContainsWords ] + [-SenderADAttributeMatchesPatterns ] + [-SenderAddressLocation ] + [-SenderDomainIs ] + [-SenderIPRanges ] + [-SentTo ] + [-SentToMemberOf ] + [-SetHeader ] + [-SharedByIRMUserRisk ] + [-StopPolicyProcessing ] + [-SubjectContainsWords ] + [-SubjectMatchesPatterns ] + [-SubjectOrBodyContainsWords ] + [-SubjectOrBodyMatchesPatterns ] + [-ThirdPartyAppDlpRestrictions ] + [-TriggerPowerAutomateFlow ] + [-UnscannableDocumentExtensionIs ] + [-WhatIf] + [-WithImportance ] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DlpComplianceRule -Identity 25bf67b6-3783-4f74-bde9-98dd40333082 -AccessScope NotInOrganization -BlockAccess $true +``` + +This example modifies the access scope and blocking behavior of a DLP compliance rule that's identified by its GUID value. + +### Example 2 +```powershell +# Contents of the file named C:\Data\Sensitive Type.txt: + +{ +"Version": "1.0", +"Condition": { + "Operator": "And", + "SubConditions": [ + { + "ConditionName": "ContentContainsSensitiveInformation", + "Value": [ + { + "groups": [ + { + "Operator": "Or", + "labels": [ + { + "name": "defa4170-0d19-0005-000a-bc88714345d2", + "type": "Sensitivity" + } + ], + "name": "Default", + "sensitivetypes": [ + { + "confidencelevel": "Low", + "name": "Credit Card Number" + } + ] + } + ] + } + ] + }, + { + "Operator": "Not", + "SubConditions": [ + { + "Operator": "OR", + "SubConditions": [ + { + "ConditionName": "FromMemberOf", + "Value": [ + "janesteam@contoso.com" + ] + }, + { + "ConditionName": "SentTo", + "Value": [ + "adele@contoso.com" + ] + } + ], + } + ] + } + ] + } +} + +$data = Get-Content -Path "C:\Data\Sensitive Type.txt" -ReadCount 0 + +$AdvancedRuleString = $data | Out-string + +Set-DLPComplianceRule -Identity "Contoso Rule 1" -AdvancedRule $AdvancedRuleString +``` + +This example uses the AdvancedRule parameter to read the following complex condition from a file: "Content contains sensitive information: "Credit card number OR Highly confidential" AND (NOT (Sender is a member of "Jane's Team" OR Recipient is "adele@contoso.com")). + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccessScope +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. +- NotInOrganization: The rule is applied to content that's accessible or delivered to a recipient outside the organization. +- None: The condition isn't used. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.AccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActivationDate +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddRecipients +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"}`. +- `@{AddManagerAsRecipientType = ""}`. For example, `@{AddManagerAsRecipientType = "Bcc"}`. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdvancedRule +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. + +For syntax details, see Example 2. + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlertProperties +{{ Fill AlertProperties Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfRecipientAddressMatchesPatterns +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyBrandingTemplate +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyHtmlDisclaimer +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. +- Location: Specifies where to insert the HTML disclaimer text in the body of messages. Append = Add to the end of the message body. Prepend = Insert at the beginning of the message body. +- FallbackAction: Specifies what to do if the HTML disclaimer can't be added to a message. Wrap = The original message is wrapped in a new message envelope, and the disclaimer is used as the message body for the new message. Ignore = The rule is ignored and the message is delivered without the disclaimer. Reject = The message is rejected. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AttachmentIsNotLabeled +{{ Fill AttachmentIsNotLabeled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockAccess +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. +- $false: Allows access to the source item that matched the rule. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockAccessScope +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. +- PerUser: Blocks access to external users. +- PerAnonymousUser: Blocks access to people through the "Anyone with the link" option in SharePoint and OneDrive. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.BlockAccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentCharacterSetContainsWords +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`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})})})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentFileTypeMatches +{{ Fill ContentFileTypeMatches Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentIsNotLabeled +{{ Fill ContentIsNotLabeled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentIsShared +{{ Fill ContentIsShared Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter specifies whether the DLP rule is disabled. Valid values are: + +- $true: The rule is disabled. +- $false: The rule is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentContainsWords +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentCreatedBy +{{ Fill DocumentCreatedBy Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentCreatedByMemberOf +{{ Fill DocumentCreatedByMemberOf Description }} + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentMatchesPatterns +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"`. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentNameMatchesPatterns +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainCountOver +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. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptRMSTemplate +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. + +```yaml +Type: RmsTemplateIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpBrowserRestrictions +{{ Fill EndpointDlpBrowserRestrictions Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpRestrictions +**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"=""},...)`. + +The value of `` is one of the supported values. + +The value of `` is Audit, Block, Ignore, or Warn. + +Example values: + +- `@{"Setting"="Print"; "Value"="Block"}` +- `@{"Setting"="CopyPaste"; "Value"="Block";}` +- `@{"Setting"="ScreenCapture"; "Value"="Block";}` +- `@{"Setting"="RemovableMedia"; "Value"="Block";}` +- `@{"Setting"="NetworkShare"; "Value"="Block";}` +- `@{"Setting"="Print"; "Value"="Audit";}` +- `@{"Setting"="UnallowedApps"; "Value"="notepad"; "value2"="Microsoft Notepad"}` + +When you use the values Block or Warn in this parameter, also need to use the NotifyUser parameter. + +You can view and configure the available restrictions with the Get-PolicyConfig and Set-PolicyConfig cmdlets. + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnforcePortalAccess +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. +- $false: External recipients aren't required to use the encrypted message portal. Outlook can decrypt messages inline. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EvaluateRulePerComponent +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). +- $false: A DLP rule match for conditions and exceptions can be anywhere in the message. + +For example, say a DLP rule is configured to block messages that contain three or more Social Security numbers (SSNs). When the value of this parameter is $true, a message is blocked only if there are three or more SSNs in the message body, or there are three or more SSNs in a specific attachment. The DLP rule doesn't match and the message isn't blocked if there are two SSNs in the message body, one SSN in an attachment, and two SSNs in another attachment in the same email message. + +This parameter works with the following conditions or exceptions only: + +- Content contains +- Attachment contains +- Attachment is not labeled +- File extension is + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAccessScope +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. +- NotInOrganization: The rule isn't applied to content that's accessible or delivered to a recipient outside the organization. +- None: The exception isn't used. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.AccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfAnyOfRecipientAddressMatchesPatterns +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentCharacterSetContainsWords +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. + +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`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentContainsSensitiveInformation +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"})})})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentExtensionMatchesWords +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentFileTypeMatches +{{ Fill ExceptIfContentFileTypeMatches Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentIsShared +{{ Fill ExceptIfContentIsShared Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfContentPropertyContainsWords +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentContainsWords +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentCreatedBy +{{ Fill ExceptIfDocumentCreatedBy Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentCreatedByMemberOf +{{ Fill ExceptIfDocumentCreatedByMemberOf Description }} + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsPasswordProtected +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. +- $false: Don't look for password protected files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentIsUnsupported +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. +- $false: Don't look for unsupported files that can't be scanned. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentMatchesPatterns +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"`. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentNameMatchesPatterns +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentNameMatchesWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfDocumentSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFrom +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromAddressMatchesPatterns +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromMemberOf +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"`. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFromScope +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. +- NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.FromScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHasSenderOverride +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. +- $false: Don't look for messages where the sender took action to override a DLP policy. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHeaderContainsWords +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfHeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfMessageSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, although small values may be rounded up to the nearest kilobyte. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfMessageTypeMatches +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. +- AutomaticForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook on the web or Outlook). +- AutomaticReply: Out of office (OOF) messages configured by the user. +- Calendaring: Meeting requests and responses. +- Encrypted: S/MIME encrypted messages. +- PermissionControlled: Messages protected with Rights Management, Office 365 Message Encryption (OME), and sensitivity labels (with encryption). +- ReadReceipt: Read receipts. +- Signed: Digitally signed messages. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.MessageTypes +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectMatchesPatterns +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectOrBodyContainsWords +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. + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectOrBodyMatchesPatterns +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. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfUnscannableDocumentExtensionIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfWithImportance +The ExceptIfWithImportance parameter specifies an exception for the rule that looks for messages with the specified importance level. Valid values are: + +- Low +- Normal +- High + +You can use this exception in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.WithImportance +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpiryDate +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -From +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromAddressMatchesPatterns +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromMemberOf +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"`. + +```yaml +Type: SmtpAddress[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FromScope +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. +- NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.FromScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GenerateAlert +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. +- SiteAdmin + +You can specify multiple values separated by commas. + +The email message that's generated by this action contains a link to detailed information in the Microsoft Purview compliance portal (the details aren't in the email message itself). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GenerateIncidentReport +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. +- SiteAdmin + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HasSenderOverride +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. +- $false: Don't look for messages where the sender took action to override a DLP policy. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HeaderContainsWords +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HeaderMatchesPatterns +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncidentReportContent +The IncidentReportContent parameter specifies the content to include in the report when you use the GenerateIncidentReport parameter. Valid values are: + +- All +- Default +- Detections +- DocumentAuthor +- DocumentLastModifier +- MatchedItem +- RulesMatched +- Service +- Severity +- Service +- Title + +You can specify multiple values separated by commas. You can only use the value "All" by itself. If you use the value "Default", the report includes the following content: + +- DocumentAuthor +- MatchedItem +- RulesMatched +- Service +- Title + +Therefore, any additional values that you use with the value "Default" are ignored. + +```yaml +Type: ReportContentOption[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageIsNotLabeled +{{ Fill MessageIsNotLabeled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageSizeOver +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Exchange.Data.ByteQuantifiedSize +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageTypeMatches +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. +- AutomaticForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook on the web or Outlook). +- AutomaticReply: Out of office (OOF) messages configured by the user. +- Calendaring: Meeting requests and responses. +- Encrypted: S/MIME encrypted messages. +- PermissionControlled: Messages protected with Rights Management, Office 365 Message Encryption (OME), and sensitivity labels (with encryption). +- ReadReceipt: Read receipts. +- Signed: Digitally signed messages. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.MessageTypes +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MipRestrictAccess +{{ Fill MipRestrictAccess Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Moderate +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. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModifySubject +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: + +- Replace: Replaces all regular expression matches (the `Patterns=` value) in the subject with the `SubjectText=` value. +- Append: Removes all regular expression matches (the `Patterns=` value) in the subject and inserts the `SubjectText=` value at the end of the subject. +- Prepend: Removes all regular expression matches (the `Patterns=` value) and inserts the `SubjectText=` value at the beginning of the subject. + +The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10. + +```yaml +Type: PswsHashtable +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NonBifurcatingAccessScope +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. +- HasExternal: At least one recipient is outside the organization. +- None: The condition isn't used. + +You can use this condition in DLP policies that are scoped only to Exchange + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.NonBifurcatingAccessScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyAllowOverride +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. +- WithAcknowledgement: Allows overrides with explicit user acknowledgement. (Exchange only) +- WithoutJustification: Allows overrides without justification. +- WithJustification: Allows overrides with justification. + +You can specify multiple values separated by commas. The values WithoutJustification and WithJustification are mutually exclusive. + +```yaml +Type: OverrideOption[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailCustomSenderDisplayName +{{ Fill NotifyEmailCustomSenderDisplayName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailCustomSubject +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailCustomText +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): + +- %%AppliedActions%%: The actions applied to the content. +- %%ContentURL%%: The URL of the document on the SharePoint site or OneDrive site. +- %%MatchedConditions%%: The conditions that were matched by the content. Use this token to inform people of possible issues with the content. +- %%BlockedMessageInfo%%: The details of the message that was blocked. Use this token to inform people of the details of the message that was blocked. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailExchangeIncludeAttachment +{{ Fill NotifyEmailExchangeIncludeAttachment Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEmailOnedriveRemediationActions +{{ Fill NotifyEmailOnedriveRemediationActions Description }} + +```yaml +Type: NotifyEmailRemediationActions +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyEndpointUser +**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. + +{{ Fill NotifyEndpointUser Description }} + +For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about). + +```yaml +Type: PswsHashtable +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyOverrideRequirements +{{ Fill NotifyOverrideRequirements Description }} + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyOverrideRequirements +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipCustomDialog +{{ Fill NotifyPolicyTipCustomDialog Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipCustomText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipCustomTextTranslations +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). + +To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. For example: `"en:PolicyTipInEnglish","zh:警告：这个文件含有非法内容","th:คำแนะนำนโยบายในไทย"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipDisplayOption +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. +- Dialog: Displays policy tip at the top of the mail and as a popup dialog. (exchange only) + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyTipDisplayOption +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyPolicyTipUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUser +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. +- LastModifier +- Owner +- SiteAdmin + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserType +The NotifyUserType parameter specifies the type of notification that's used for the rule. Valid values are: + +- NotSet +- Email +- PolicyTip +- Email,PolicyTip + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.NotifyUserType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnPremisesScannerDlpRestrictions +{{ Fill OnPremisesScannerDlpRestrictions Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrependSubject +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new 9th rule that you add to the policy are from 0 through 8. +- The default value for a new 9th rule that you add to the policy is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it are increased by 1. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProcessingLimitExceeded +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. +- $false: Don't look for files where scanning couldn't complete. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Quarantine +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: + +- $true: The message is delivered to the hosted quarantine. +- $false: The message is not quarantined. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientCountOver +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. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RedirectMessageTo +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveHeader +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. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveRMSTemplate +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. +- $False: The messages and attachments are not decrypted. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportSeverityLevel +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. +- Low: This is the default value. +- Medium +- High + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictAccess +{{ Fill RestrictAccess Description }} + +```yaml +Type: System.Collections.Hashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictBrowserAccess +{{ Fill RestrictBrowserAccess Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RuleErrorAction +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. +- RetryThenBlock: Do a maximum of 5 retries of the rule with an increasing time gap of 10 min (i.e, 1st retry happens after 10 min, 2nd retry after 20 min, etc.). After the failure of the fifth retry, the message is dropped and we send a non-delivery report (also known as an NDR or bounce messages). +- Blank (the value $null): Defer the delivery of the message and keep retrying the rule. This is the default value. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderADAttributeContainsWords +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="Word"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="Word1";AttributeName2="Word2";...AttributeNameN="WordN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderADAttributeMatchesPatterns +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 +- Company +- Country or Region +- CustomAttribute1 to CustomAttribute15 +- Department +- DisplayName +- Email Addresses +- Fax +- FirstName +- HomePhoneNumber +- Initials +- LastName +- Manager +- Mobile Phone +- Notes +- Office +- OtherFax +- OtherHomePhone +- Other Telephone +- Pager +- Phone +- Post Office Box +- State or Province +- Street Address +- Title +- UserLogonName +- Postal Code + +This parameter uses the syntax: `@{AttributeName="RegularExpression"}`. To specify multiple attributes, use the following syntax: `@{AttributeName1="RegularExpression1";AttributeName2="RegularExpression2";...AttributeNameN="RegularExpressionN"}`. Don't use words with leading or trailing spaces. + +When you specify multiple attributes, the OR operator is used. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderAddressLocation +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. +- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). +- HeaderOrEnvelope: Examine senders in the message header and the message envelope. + +Note that message envelope searching is available only for the following conditions and exceptions: + +- From and ExceptIfFrom +- FromAddressContainsWords and ExceptIfFromAddressContainsWords +- FromAddressMatchesPatterns and ExceptIfFromAddressMatchesPatterns +- FromMemberOf and ExceptIfFromMemberOf +- SenderDomainIs and ExceptIfSenderDomainIs + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicySenderAddressLocation +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderDomainIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderIPRanges +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SetHeader +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. + +You can use this action in DLP policies that are scoped only to Exchange. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharedByIRMUserRisk +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) +- 797C4446-5C73-484F-8E58-0CCA08D6DF6C (Moderate Risk Level) +- 75A4318B-94A2-4323-BA42-2CA6DB29AAFE (Minor Risk Level) + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: All +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StopPolicyProcessing +The StopPolicyProcessing parameter specifies an action that stops processing more DLP policy rules. Valid values are: + +- $true: Stop processing more rules. +- $false: Continue processing more rules after this one. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectContainsWords +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"` +- Multiple words: `no_reply,urgent,...` +- Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...` + +The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectMatchesPatterns +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectOrBodyContainsWords +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. + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubjectOrBodyMatchesPatterns +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. + +```yaml +Type: +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThirdPartyAppDlpRestrictions +{{ Fill ThirdPartyAppDlpRestrictions Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TriggerPowerAutomateFlow +{{ Fill TriggerPowerAutomateFlow Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnscannableDocumentExtensionIs +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WithImportance +The WithImportance parameter specifies a condition for the rule that looks for messages with the specified importance level. Valid values are: + +- Low +- Normal +- High + +You can use this condition in DLP policies that are scoped only to Exchange. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.WithImportance +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-DlpEdmSchema.md b/exchange/exchange-ps/exchange/Set-DlpEdmSchema.md new file mode 100644 index 0000000000..be8d02a43c --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DlpEdmSchema.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DlpEdmSchema + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DlpEdmSchema cmdlet to modify exact data match (EDM) data loss prevention (DLP) schemas in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DlpEdmSchema [-FileData] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +For an explanation and example of the EDM schema, see [Learn about exact data match based sensitive information types](https://learn.microsoft.com/purview/sit-learn-about-exact-data-match-based-sits). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DlpEdmSchema -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\edm.xml')) -Confirm:$true +``` + +This example modifies a DLP EDM schema using the edm.xml file in the C:\\My Documents folder. + +## PARAMETERS + +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/Set-DlpKeywordDictionary.md new file mode 100644 index 0000000000..aa9f4a5616 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DlpKeywordDictionary.md @@ -0,0 +1,235 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DlpKeywordDictionary + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DlpKeywordDictionary cmdlet to modify data loss prevention (DLP) keyword dictionaries in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DlpKeywordDictionary [-Identity] + [-Confirm] + [-Description ] + [-DoNotPersistKeywords] + [-FileData ] + [-Name ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$Keywords = "Aarskog's syndrome, Abandonment, Abasia, Abderhalden-Kaufmann-Lignac, Abdominalgia, Abduction contracture, Abetalipo proteinemia, Abiotrophy, Ablatio, ablation, Ablepharia, Abocclusion, Abolition, Aborter, Abortion, Abortus, Aboulomania, Abrami's disease, Abramo" + +$EncodedKeywords = [System.Text.Encoding]::Unicode.GetBytes($keywords) + +Set-DlpKeywordDictionary -Identity "Diseases" -FileData $EncodedKeywords +``` + +This example replaces the existing terms in the DLP keyword dictionary named Diseases with the specified values. + +### Example 2 +```powershell +$Dictionary = Get-DlpKeywordDictionary -Name "Diseases" + +$Terms = $Dictionary.KeywordDictionary.split(',').trim() + +$Terms += "Achylia","Acidemia","Acidocytopenia","Acidocytosis","Acidopenia","Acidosis","Aciduria","Acladiosis","Aclasis" + +$Keywords = $Terms -Join ", " + +$EncodedKeywords = [System.Text.Encoding]::Unicode.GetBytes($Keywords) + +Set-DlpKeywordDictionary -Identity "Diseases" -FileData $EncodedKeywords +``` + +This example adds the specified terms to the DLP keyword dictionary named Diseases without affecting other existing terms. + +### Example 3 +```powershell +$Dictionary = Get-DlpKeywordDictionary -Name "Diseases" + +$Terms = $Dictionary.KeywordDictionary.split(',').trim() + +$TermsToRemove = @('abandonment', 'ablatio') + +$UpdatedTerms = $Terms | Where-Object {$_ -NotIn $TermsToRemove} + +$Keywords = $UpdatedTerms -Join ", " + +$EncodedKeywords = [System.Text.Encoding]::Unicode.GetBytes($Keywords) + +Set-DlpKeywordDictionary -Identity "Diseases" -FileData $EncodedKeywords +``` + +This example removes the specified terms from the DLP keyword dictionary named Diseases without affecting other existing terms. + +### Example 4 +```powershell +$Dictionary = Get-DlpKeywordDictionary -Name "Inappropriate Language" + +$Terms = $Dictionary.KeywordDictionary.split(',').trim() + +Set-Content $Terms -Path "C:\My Documents\InappropriateTerms.txt" + +$UpdatedTerms = Get-Content -Path "C:\My Documents\InappropriateTerms.txt" + +$Keywords = $UpdatedTerms -Join ", " + +$EncodedKeywords = [System.Text.Encoding]::Unicode.GetBytes($Keywords) + +Set-DlpKeywordDictionary -Identity "Inappropriate Language" -FileData $EncodedKeywords +``` + +The first three commands export the terms from the existing keyword dictionary named Inappropriate Language to the file C:\\My Documents\\InappropriateTerms.txt, where each term is on a separate line. + +After you use Notepad to modify the terms and save the file, the last four commands use the file to replace the terms in the keyword dictionary. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DoNotPersistKeywords +{{ Fill DoNotPersistKeywords Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileData +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. + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpPolicy.md b/exchange/exchange-ps/exchange/Set-DlpPolicy.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpPolicy.md rename to exchange/exchange-ps/exchange/Set-DlpPolicy.md index 0018d6c234..74002da4a2 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpPolicy.md +++ b/exchange/exchange-ps/exchange/Set-DlpPolicy.md @@ -1,34 +1,41 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlppolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-DlpPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Set-DlpCompliancePolicy and Set-DlpComplianceRule cmdlets instead. -Use the Set-DlpPolicy cmdlet to modify data loss prevention (DLP) policies in your organization. +This cmdlet is functional only in on-premises Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the Set-DlpPolicy cmdlet to modify data loss prevention (DLP) policies that are based on transport rules (mail flow rules) in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-DlpPolicy [-Identity] [-Confirm] [-Description ] [-DomainController ] - [-Mode ] [-Name ] [-State ] [-WhatIf] +Set-DlpPolicy [-Identity] + [-Confirm] + [-Description ] + [-DomainController ] + [-Mode ] + [-Name ] + [-State ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,7 +49,11 @@ This example disables the DLP policy named Employee Numbers. ## PARAMETERS ### -Identity -The Identity parameter specifies the DLP policy you want to modify. 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. +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 +- Distinguished name (DN) +- GUID ```yaml Type: DlpPolicyIdParameter @@ -60,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -94,8 +104,6 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml @@ -115,9 +123,7 @@ Accept wildcard characters: False 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. - - AuditAndNotify: When a message matches the conditions specified by the DLP policy, the actions specified by the policy aren't enforced, but notification emails are sent. - - Enforce: When a message matches the conditions specified by the DLP policy, the actions specified by the policy are enforced and notification emails are sent. If the State parameter is set to Disabled, the value of the Mode parameter is irrelevant. @@ -188,12 +194,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationType.md new file mode 100644 index 0000000000..e6a09ab1b6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationType.md @@ -0,0 +1,297 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DlpSensitiveInformationType + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-DlpSensitiveInformationType cmdlet to modify sensitive information type rules that use document fingerprints. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DlpSensitiveInformationType [-Identity] + [-Confirm] + [-Description ] + [-FileData ] + [-Fingerprints ] + [-IsExact ] + [-Locale ] + [-Name ] + [-Threshold ] + [-ThresholdConfig ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DlpSensitiveInformationType "Contoso Confidential" -Locale fr -Name "Contoso Confidentiel" -Description "Ce message contient des informations confidentielles." -IsDefault +``` + +This example adds a French translation to the existing sensitive information type rule named "Contoso Confidential", and sets this French translation as the default. + +### Example 2 +```powershell +Set-DlpSensitiveInformationType "Contoso Confidential" -Locale es -Name $null -Description $null +``` + +This example removes the existing Spanish translation from the sensitive information type rule named "Contoso Confidential". + +### Example 3 +```powershell +$Benefits_Template = [System.IO.File]::ReadAllBytes('C:\My Documents\Contoso Benefits Template.docx') + +$Benefits_Fingerprint = New-DlpFingerprint -FileData $Benefits_Template -Description "Contoso Benefits Template" + +$Contoso_Confidential = Get-DlpSensitiveInformationType "Contoso Confidential" + +$Array = [System.Collections.ArrayList]($Contoso_Confidential.Fingerprints) + +$Array.Add($Benefits_FingerPrint[0]) + +Set-DlpSensitiveInformationType $Contoso_Confidential.Identity -FingerPrints $Array +``` + +This example modifies the existing sensitive information type rule named "Contoso Confidential" by adding a new document fingerprint for the file C:\\My Documents\\Contoso Benefits Template.docx without affecting any existing document fingerprints that are already defined. + +### Example 4 +```powershell +$cc = Get-DlpSensitiveInformationType "Contoso Confidential" + +$a = [System.Collections.ArrayList]($cc.Fingerprints) + +$a + +$a.RemoveAt(0) + +Set-DlpSensitiveInformationType $cc.Identity -FingerPrints $a +``` + +This example modifies the sensitive information type rule named "Contoso Confidential" by removing an existing document fingerprint without affecting other document fingerprints that are already defined. + +The first three commands return the list of document fingerprints in the sensitive information type. The first document fingerprint in the list has the index number 0, the second has the index number 1, and so on. You use the index number to specify the document fingerprint that you want to remove. The last two commands remove the first document fingerprint that's displayed in the list. + +## PARAMETERS + +### -Identity +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 +- LocalizedName +- Identity GUID value + +```yaml +Type: SensitiveInformationTypeIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileData +{{ Fill FileData Description }} + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Fingerprints +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsExact +{{ Fill IsExact Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locale +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). + +Typically, you use the Locale parameter with the Name and Description parameters to add or remove translated names and descriptions for the sensitive information type rule. You can also use the Locale parameter with the IsDefault switch to designate an existing translated name and description as the default. Before you can remove the default translation, you need to set another translation as the default. + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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. + +The value of the Name parameter is used in the Policy Tip that's presented to users in Outlook on the web. When a translated value of the Name parameter matches the client's language, the Policy Tip is displayed in the client's language. If no translated values of the Name parameter match the client's language, the default translation that's specified by the IsDefault parameter is used for the Policy Tip. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Threshold +{{ Fill Threshold Description }} + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThresholdConfig +{{ Fill ThresholdConfig Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationTypeRulePackage.md new file mode 100644 index 0000000000..944203816e --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationTypeRulePackage.md @@ -0,0 +1,110 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-DlpSensitiveInformationTypeRulePackage + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-DlpSensitiveInformationTypeRulePackage cmdlet to update existing data loss prevention (DLP) sensitive information type rule packages in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-DlpSensitiveInformationTypeRulePackage [-FileData] + [-Confirm] + [-WhatIf] + [] +``` + +## DESCRIPTION +Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-DlpSensitiveInformationTypeRulePackage -FileData ([System.IO.File]::ReadAllBytes('C:\My Documents\External Sensitive Info Type Rule Collection.xml')) +``` + +This example imports the sensitive information type rule package C:\\My Documents\\External Sensitive Info Type Rule Collection.xml. + +## PARAMETERS + +### -FileData +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`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md similarity index 76% rename from exchange/exchange-ps/exchange/users-and-groups/Set-DynamicDistributionGroup.md rename to exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md index 3c7eb31663..4b26f36939 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-dynamicdistributiongroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-DynamicDistributionGroup @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-DynamicDistributionGroup cmdlet to modify existing dynamic distribution groups. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -75,6 +74,7 @@ Set-DynamicDistributionGroup [-Identity] [-ExtensionCustomAttribute3 ] [-ExtensionCustomAttribute4 ] [-ExtensionCustomAttribute5 ] + [-ForceMembershipRefresh] [-ForceUpgrade] [-GrantSendOnBehalfTo ] [-HiddenFromAddressListsEnabled ] @@ -103,6 +103,7 @@ Set-DynamicDistributionGroup [-Identity] [-SendOofMessageToOriginatorEnabled ] [-SimpleDisplayName ] [-UMDtmfMap ] + [-UpdateMemberCount] [-WhatIf] [-WindowsEmailAddress ] [] @@ -114,16 +115,14 @@ A dynamic distribution group queries mail-enabled objects and builds the group m The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - - The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - - The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPath filter. +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter. -You can't use this cmdlet to replace a precanned filter with a custom OPath filter, or vice-versa. You can only modify the existing filter. +You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -134,21 +133,20 @@ Set-DynamicDistributionGroup -Identity Developers -IncludedRecipients MailboxUse This example applies the following changes to the existing dynamic distribution group named Developers: -Change the ConditionalCompany query filter to Contoso. - -Change the IncludedRecipients query filter to MailboxUsers. - -Add the value Internal to the ConditionalCustomAttribute1 attribute. +- Change the ConditionalCompany query filter to Contoso. +- Change the IncludedRecipients query filter to MailboxUsers. +- Add the value Internal to the ConditionalCustomAttribute1 attribute. ### Example 2 ```powershell $extAtrValue="Contoso" + Set-DynamicDistributionGroup -Identity Developers -RecipientFilter "ExtensionCustomAttribute1 -eq '$extAtrValue'" ``` This example applies the following changes to the existing dynamic distribution group named Developers: -Sets the RecipientFilter custom OPath filter using a variable based value of a specific recipient property. +- Sets the RecipientFilter custom OPATH filter using a variable based value of a specific recipient property. ## PARAMETERS @@ -156,22 +154,17 @@ Sets the RecipientFilter custom OPath filter using a variable based value of a s 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml Type: DynamicGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -186,20 +179,15 @@ The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages t 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -209,7 +197,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -224,20 +212,15 @@ The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send m 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -247,7 +230,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -264,18 +247,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. @@ -287,7 +265,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -297,16 +275,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -317,7 +299,7 @@ The Alias parameter never generates or updates the primary email address of a ma Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -332,23 +314,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -370,20 +343,15 @@ The BypassModerationFromSendersOrMembers parameter specifies who is allowed to s To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +To enter multiple senders and overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more senders without affecting any existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. @@ -391,7 +359,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -405,15 +373,15 @@ The ConditionalCompany parameter specifies a precanned filter that's based on th 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -427,15 +395,15 @@ The ConditionalCustomAttribute1 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -449,15 +417,15 @@ The ConditionalCustomAttribute10 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -471,15 +439,15 @@ The ConditionalCustomAttribute11 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -493,15 +461,15 @@ The ConditionalCustomAttribute12 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -515,15 +483,15 @@ The ConditionalCustomAttribute13 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -537,15 +505,15 @@ The ConditionalCustomAttribute14 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -559,15 +527,15 @@ The ConditionalCustomAttribute15 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -581,15 +549,15 @@ The ConditionalCustomAttribute2 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -603,15 +571,15 @@ The ConditionalCustomAttribute3 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -625,15 +593,15 @@ The ConditionalCustomAttribute4 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -647,15 +615,15 @@ The ConditionalCustomAttribute5 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -669,15 +637,15 @@ The ConditionalCustomAttribute6 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -691,15 +659,15 @@ The ConditionalCustomAttribute7 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -713,15 +681,15 @@ The ConditionalCustomAttribute8 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -735,15 +703,15 @@ The ConditionalCustomAttribute9 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -757,15 +725,15 @@ The ConditionalDepartment parameter specifies a precanned filter that's based on 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -779,15 +747,15 @@ The ConditionalStateOrProvince parameter specifies a precanned filter that's bas 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -799,15 +767,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -817,17 +784,18 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap +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: - $true: A DTMF map is created for the recipient. This is the default value. - - $false: A DTMF map isn't created for the recipient. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -843,7 +811,7 @@ This parameter specifies a value for the CustomAttribute1 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -859,7 +827,7 @@ This parameter specifies a value for the CustomAttribute10 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -875,7 +843,7 @@ This parameter specifies a value for the CustomAttribute11 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -891,7 +859,7 @@ This parameter specifies a value for the CustomAttribute12 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -907,7 +875,7 @@ This parameter specifies a value for the CustomAttribute13 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -923,7 +891,7 @@ This parameter specifies a value for the CustomAttribute14 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -939,7 +907,7 @@ This parameter specifies a value for the CustomAttribute15 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -955,7 +923,7 @@ This parameter specifies a value for the CustomAttribute2 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -971,7 +939,7 @@ This parameter specifies a value for the CustomAttribute3 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -987,7 +955,7 @@ This parameter specifies a value for the CustomAttribute4 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1003,7 +971,7 @@ This parameter specifies a value for the CustomAttribute5 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1019,7 +987,7 @@ This parameter specifies a value for the CustomAttribute6 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1035,7 +1003,7 @@ This parameter specifies a value for the CustomAttribute7 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1051,7 +1019,7 @@ This parameter specifies a value for the CustomAttribute8 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1067,7 +1035,7 @@ This parameter specifies a value for the CustomAttribute9 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1085,7 +1053,7 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1101,7 +1069,7 @@ The DisplayName parameter specifies the display name of the dynamic distribution Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1129,39 +1097,34 @@ Accept wildcard characters: False ``` ### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). +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 \:\,\:\,...\:\. The optional \ value specifies the type of email address. Some examples of valid values include: +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: - SMTP: The primary SMTP address. You can use this value only once in a command. - - smtp: Other SMTP email addresses. - - X400: X.400 addresses in on-premises Exchange. - - X500: X.500 addresses in on-premises Exchange. -If you don't include a \ value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. To specify the primary SMTP email address, you can use any of the following methods: -- Use the \ value SMTP on the address. - -- The first email address when you don't use any \ values, or when you use multiple \ values of smtp. - +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. - Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\:\","\:\",..."\:\". +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\:\","\:\",...; Remove="\:\","\:\",...}. +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. ```yaml Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1176,7 +1139,6 @@ 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: - $true: Email address policies are applied to this recipient. This is the default value. - - $false: Email address policies aren't applied to this recipient. ```yaml @@ -1195,17 +1157,14 @@ Accept wildcard characters: False ### -ExpansionServer 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 2016 Mailbox 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. Therefore, you should consider implementing a high availability solution for an expansion server. +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. You can specify the following types of servers as expansion servers: -- An Exchange 2016 Mailbox server. - -- An Exchange 2013 Mailbox server. - +- An Exchange 2013 or later Mailbox server. - An Exchange 2010 Hub Transport server. -When you specify an expansion server, use the ExchangeLegacyDN. You can find this value by running the command: Get-ExchangeServer \ | Format-List ExchangeLegacyDN. An example value for this parameter is "/o=Contoso/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01". +When you specify an expansion server, use the ExchangeLegacyDN. You can find this value by running the command: `Get-ExchangeServer | Format-List ExchangeLegacyDN`. An example value for this parameter is "/o=Contoso/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox01". ```yaml Type: String @@ -1223,9 +1182,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute1 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -1233,7 +1192,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1245,9 +1204,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute2 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -1255,7 +1214,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1267,9 +1226,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute3 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -1277,7 +1236,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1289,9 +1248,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute4 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -1299,7 +1258,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1311,9 +1270,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute5 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -1321,7 +1280,25 @@ 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 +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceMembershipRefresh +This parameter is available only in the cloud-based service. + +{{ Fill ForceMembershipRefresh Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1331,13 +1308,13 @@ Accept wildcard characters: False ``` ### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1347,33 +1324,24 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo -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 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. By default, this parameter is blank, which means no one else has permission to send on behalf of this group. @@ -1381,7 +1349,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1394,14 +1362,13 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. - - $false: The recipient is visible in address lists. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1413,12 +1380,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -1438,15 +1404,10 @@ Accept wildcard characters: False 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. - - MailboxUsers - - MailContacts - - MailGroups - - MailUsers - - Resources: This value indicates room or equipment mailboxes. You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. @@ -1455,7 +1416,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1469,15 +1430,14 @@ The MailTip parameter specifies the custom MailTip text for this recipient. The When you add a MailTip to a recipient, two things happen: -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \\This mailbox is not monitored\\. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `This mailbox is not monitored`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1491,17 +1451,17 @@ The MailTipTranslations parameter specifies additional languages for the custom To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: -@{Add="\:\","\:\"...; Remove="\:\","\:\"...} +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. -\ is a valid ISO 639 two-letter culture code that's associated with the language. +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1514,38 +1474,27 @@ Accept wildcard characters: False 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 - - Delete the group - - Approve messages sent to the group if moderation is enabled, but no moderators are specified. The owner 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 owner. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: GeneralRecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1562,18 +1511,15 @@ The MaxReceiveSize parameter specifies the maximum allowed email message size th When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1596,18 +1542,15 @@ The MaxSendSize parameter specifies the maximum allowed email message size that When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1626,20 +1569,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -1647,7 +1585,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1660,7 +1598,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -1669,7 +1606,7 @@ You use the ModeratedBy parameter to specify the moderators. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1685,7 +1622,7 @@ The Name parameter specifies the unique name of the dynamic distribution group. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1701,7 +1638,7 @@ The Notes parameters specifies additional information about the object. If the v Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1717,7 +1654,7 @@ The PhoneticDisplayName parameter specifies an alternate spelling of the user's Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1729,7 +1666,7 @@ Accept wildcard characters: False ### -PrimarySmtpAddress 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 that means the email addresses of the mail user no longer automatically updated by email address policies. +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. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. @@ -1737,7 +1674,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1750,11 +1687,8 @@ Accept wildcard characters: False 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 - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is the OU where the object was created. @@ -1765,7 +1699,7 @@ Note that the RecipientContainer property can't be blank. The group is always li Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1775,27 +1709,22 @@ Accept wildcard characters: False ``` ### -RecipientFilter -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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). +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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). - In cloud-based environments, you can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. - - In on-premises Exchange, wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1810,20 +1739,15 @@ The RejectMessagesFrom parameter specifies who isn't allowed to send messages to 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1833,7 +1757,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1848,20 +1772,15 @@ The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send me 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1871,7 +1790,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1888,18 +1807,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. @@ -1911,7 +1825,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1924,7 +1838,6 @@ Accept wildcard characters: False 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. - - $false: Delivery status notifications aren't sent to the owners of the group. This is the default value. The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true. @@ -1933,7 +1846,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1946,7 +1859,6 @@ Accept wildcard characters: False 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. - - $false: Delivery status notifications aren't sent to the message senders. The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true. @@ -1955,7 +1867,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1968,14 +1880,13 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1988,9 +1899,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -1999,7 +1908,7 @@ This parameter is only meaningful when moderation is enabled (the ModerationEnab Type: TransportModerationNotificationFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2012,14 +1921,13 @@ Accept wildcard characters: False 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. - - $false: When messages are sent to the group, OOF messages for any of the group members aren't sent to the message sender. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2032,18 +1940,16 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". +- space +- `" ' ( ) + , - . / : ?` ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2053,27 +1959,45 @@ Accept wildcard characters: False ``` ### -UMDtmfMap +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: -- emailAddress:\ +- `emailAddress:` +- `lastNameFirstName:` +- `firstNameLastName:` + +To enter values that overwrite all existing entries, use the following syntax: `emailAddress:,lastNameFirstName:,firstNameLastName:`. + +If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only `emailAddress:`, all existing lastNameFirstName and firstNameLastName values are removed. -- lastNameFirstName:\ +To add or remove values without affecting other existing entries, use the following syntax: `@{Add="emailAddress:","lastNameFirstName:","firstNameLastName:"; Remove="emailAddress:","lastNameFirstName:","firstNameLastName:"}`. -- firstNameLastName:\ +If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use `@{Add="emailAddress:","emailAddress:}` to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. -To enter values that overwrite all existing entries, use the following syntax: emailAddress:\,lastNameFirstName:\,firstNameLastName:\. +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:\, all existing lastNameFirstName and firstNameLastName values are removed. +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` -To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"; Remove="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"}. +### -UpdateMemberCount +This parameter is available only in the cloud-based service. -If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:\","emailAddress:\} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. +{{ Fill UpdateMemberCount Description }} ```yaml -Type: MultiValuedProperty +Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2089,7 +2013,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2102,7 +2026,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -2111,7 +2034,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2125,12 +2048,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Set-EOPProtectionPolicyRule.md new file mode 100644 index 0000000000..2f487200f3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-EOPProtectionPolicyRule.md @@ -0,0 +1,321 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-EOPProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-EOPProtectionPolicyRule cmdlet to modify rules that are associated with Exchange Online Protection (EOP) protections in preset security policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-EOPProtectionPolicyRule [-Identity] + [-Comments ] + [-Confirm] + [-ExceptIfRecipientDomainIs ] + [-ExceptIfSentTo ] + [-ExceptIfSentToMemberOf ] + [-Name ] + [-Priority ] + [-RecipientDomainIs ] + [-SentTo ] + [-SentToMemberOf ] + [-WhatIf] + [] +``` + +## DESCRIPTION +For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" -ExceptIfSentToMemberOf "Test Group1","Test Group2" +``` + +This example provides exceptions to EOP protections in the Standard preset security policy for members of the specified groups. + +### Example 2 +```powershell +Set-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" -SentTo $null -ExceptIfSentTo $null -SentToMemberOf $null -ExceptIfSentToMemberOf $null -RecipientDomainIs $null -ExceptIfRecipientDomainIs $null +``` + +This example removes all conditions and exceptions from the Standard preset security policy. No restrictions are placed on who the Defender for Office 365 protections apply to. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example: + +- Name +- Distinguished name (DN) +- GUID + +By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy. + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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. + +You must use the default value for the rule. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-EcpVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-EcpVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access-servers/Set-EcpVirtualDirectory.md rename to exchange/exchange-ps/exchange/Set-EcpVirtualDirectory.md index 6b6fd0784f..3383449510 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Set-EcpVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-ecpvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-EcpVirtualDirectory @@ -19,7 +18,7 @@ Use the Set-EcpVirtualDirectory cmdlet to modify Exchange Control Panel (ECP) vi The ECP web management interface was introduced in Exchange Server 2010. In Exchange Server 2013 and Exchange Server 2016, the EAC virtual directories and the corresponding management cmdlets still use ECP in the name. You can use these cmdlets to manage ECP virtual directories on Exchange 2010, Exchange 2013, and Exchange 2016 servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,7 +38,7 @@ Set-EcpVirtualDirectory [-Identity] [-FormsAuthentication ] [-GzipLevel ] [-InternalUrl ] - [-LiveIdAuthentication ] + [-OAuthAuthentication ] [-OwaOptionsEnabled ] [-WhatIf] [-WindowsAuthentication ] @@ -47,7 +46,7 @@ Set-EcpVirtualDirectory [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,13 +69,11 @@ This example turns off the Internet access to the EAC on server named Server01. ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. To manage the first ECP virtual directory created in an Exchange organization, you need to use this cmdlet on the computer that includes the first ECP virtual directory. If you create additional ECP virtual directories, you can manage those remotely. @@ -112,7 +109,7 @@ Accept wildcard characters: False ``` ### -AdminEnabled -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://docs.microsoft.com/Exchange/architecture/client-access/disable-exchange-admin-center-access). This parameter accepts $true or $false. +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 @@ -131,7 +128,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. This parameter can be used with the FormsAuthentication parameter or with the DigestAuthentication and WindowsAuthentication parameters. @@ -152,8 +148,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -173,7 +168,6 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. - - $false: Digest authentication is disabled. This is the default value. ```yaml @@ -209,13 +203,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -235,8 +225,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -255,14 +244,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -315,7 +300,6 @@ Accept wildcard characters: False 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. - - $false: Forms authentication is disabled. ```yaml @@ -365,16 +349,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -LiveIdAuthentication -This parameter is available or functional only in Exchange Server 2010. - -The LiveIdAuthentication parameter specifies whether Windows Live ID authentication is enabled for the Exchange Control Panel virtual directory. +### -OAuthAuthentication +{{ Fill OAuthAuthentication Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2019 Required: False Position: Named @@ -419,7 +401,6 @@ Accept wildcard characters: False 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. - - $false: Integrated Windows authentication is disabled. ```yaml @@ -440,12 +421,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-EdgeSyncServiceConfig.md b/exchange/exchange-ps/exchange/Set-EdgeSyncServiceConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/mail-flow/Set-EdgeSyncServiceConfig.md rename to exchange/exchange-ps/exchange/Set-EdgeSyncServiceConfig.md index 446f1d504e..e63e09bc66 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/exchange/Set-EdgeSyncServiceConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-edgesyncserviceconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-EdgeSyncServiceConfig @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-EdgeSyncServiceConfig cmdlet to modify the configuration of edge synchronization service settings that control the general synchronization behavior shared by all EdgeSync services. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,11 +38,12 @@ Set-EdgeSyncServiceConfig [-Identity] [-Name ] [-OptionDuration ] [-RecipientSyncInterval ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -101,8 +101,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -226,11 +225,8 @@ Accept wildcard characters: False The LogLevel parameter specifies the EdgeSync logging level. Valid values are: - None (This is the default value) - - Low - - Medium - - High ```yaml @@ -270,13 +266,9 @@ The LogMaxDirectorySize specifies the maximum amount of disk space the EdgeSyncL When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -302,13 +294,9 @@ The LogMaxFileSize parameter specifies the maximum log file size for the EdgeSyn When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -417,12 +405,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/Set-EmailAddressPolicy.md new file mode 100644 index 0000000000..3d157d6042 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-EmailAddressPolicy.md @@ -0,0 +1,826 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-EmailAddressPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-EmailAddressPolicy cmdlet to modify email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-EmailAddressPolicy [-Identity] + [-ConditionalCompany ] + [-ConditionalCustomAttribute1 ] + [-ConditionalCustomAttribute10 ] + [-ConditionalCustomAttribute11 ] + [-ConditionalCustomAttribute12 ] + [-ConditionalCustomAttribute13 ] + [-ConditionalCustomAttribute14 ] + [-ConditionalCustomAttribute15 ] + [-ConditionalCustomAttribute2 ] + [-ConditionalCustomAttribute3 ] + [-ConditionalCustomAttribute4 ] + [-ConditionalCustomAttribute5 ] + [-ConditionalCustomAttribute6 ] + [-ConditionalCustomAttribute7 ] + [-ConditionalCustomAttribute8 ] + [-ConditionalCustomAttribute9 ] + [-ConditionalDepartment ] + [-ConditionalStateOrProvince ] + [-Confirm] + [-DisabledEmailAddressTemplates ] + [-DomainController ] + [-EnabledEmailAddressTemplates ] + [-EnabledPrimarySMTPAddressTemplate ] + [-ForceUpgrade] + [-IncludedRecipients ] + [-Name ] + [-Priority ] + [-RecipientContainer ] + [-RecipientFilter ] + [-WhatIf] + [] +``` + +## DESCRIPTION +After you use the Set-EmailAddressPolicy cmdlet to modify an email address policy in an on-premises Exchange organization, you need to use the Update-EmailAddressPolicy cmdlet to apply the updated policy to recipients. + +The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: + +- The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. +- The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". +- The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". + +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter. + +You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-EmailAddressPolicy -Identity "Southeast Executives" -ConditionalStateOrProvince @{Add="TX"} +``` + +In on-premises Exchange, this example modifies the existing email address policy named Southeast Executives by adding the State or province value TX (Texas) to the precanned recipient filter. + +### Example 2 +```powershell +Set-EmailAddressPolicy -Identity "Contoso Corp" -DisabledEmailAddressTemplates $null +``` + +In on-premises Exchange, this example clears the disabled email address templates from the email address policy named Contoso Corp. + +### Example 3 +```powershell +Set-EmailAddressPolicy -Identity "Office 365 Groups" -EnabledEmailAddressTemplates "SMTP:@contoso.com","smtp:@contoso.onmicrosoft.com","smtp:@contoso.microsoftonline.com" +``` + +In Exchange Online, this example modifies the existing email address policy named "Office 365 Groups" and sets the enabled email address templates to use "@contoso.com" as the primary SMTP address and "@contoso.onmicrosoft.com" and "@contoso.microsoftonline.com" as proxy addresses. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ConditionalCompany +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute1 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute10 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute11 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute12 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute13 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute14 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute15 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute2 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute3 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute4 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute5 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute6 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute7 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute8 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalCustomAttribute9 +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalDepartment +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalStateOrProvince +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. + +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisabledEmailAddressTemplates +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. + +Valid syntax for this parameter is `Type:AddressFormat`: + +- Type: A valid email address type as described in the "Address types" 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, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address. +- AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" 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`. + +You can specify multiple disabled email address templates separated by commas: `"[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`. + +Typically, this property is only populated by values after a migration from a previous version of Exchange. To clear these values, use the value $null for this parameter. + +```yaml +Type: ProxyAddressTemplateCollection +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnabledEmailAddressTemplates +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`: + +- Type: A valid email address type as described in "Address types" 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, SMTP for the primary email address, and smtp for proxy addresses. +- AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" 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`. + +This parameter requires at least one template with the Type value SMTP (to define the primary SMTP email address). After that, if you don't include a Type prefix for a template, the value smtp (an SMTP proxy address) is assumed. + +You can specify multiple email address templates separated by commas: `"SMTP:PrimarySMTPEmailAddress","[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`. + +You can't use this parameter with the EnabledPrimarySMTPAddressTemplate parameter. + +In Exchange Online PowerShell, if you use this parameter with the IncludeUnifiedGroupRecipients, you can't use variables in the email address template. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnabledPrimarySMTPAddressTemplate +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`. + +You can't use this parameter with the EnabledEmailAddressTemplates parameter. + +In Exchange Online PowerShell, if you use this parameter with the IncludeUnifiedGroupRecipients, you can't use variables in the email address template. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceUpgrade +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludedRecipients +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: + +- AllRecipients: This value can be used only by itself. +- MailboxUsers +- MailContacts +- MailGroups +- MailUsers +- Resources: This value indicates room or equipment mailboxes. + +You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. + +```yaml +Type: WellKnownRecipientType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The Name parameter specifies 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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. + +**Note**: The first email address policy that identifies a recipient configures the recipient's email addresses. All other policies are ignored, even if the first policy is unapplied and can't configure the recipient's email addresses. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientContainer +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: + +- Name +- Canonical name +- Distinguished name (DN) +- GUID + +If you don't use this parameter, the default value is the OU where the object was created. + +```yaml +Type: OrganizationalUnitIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientFilter +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'"`. + +- 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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). +- Wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-EmailTenantSettings.md b/exchange/exchange-ps/exchange/Set-EmailTenantSettings.md new file mode 100644 index 0000000000..795f69bb1f --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-EmailTenantSettings.md @@ -0,0 +1,158 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-EmailTenantSettings + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-EmailTenantSettings cmdlet to enable or disable priority account protection in your Microsoft Defender for Office 365 organization. For more information about priority accounts, see [Manage and monitor priority accounts](https://learn.microsoft.com/microsoft-365/admin/setup/priority-accounts). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-EmailTenantSettings [[-Identity] ] + [-Confirm] + [-DomainController ] + [-EnablePriorityAccountProtection ] + [-IgnoreDehydratedFlag] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-EmailTenantSettings -EnablePriorityAccountProtection $true +``` + +This example enables priority account protection in the organization. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnablePriorityAccountProtection +The EnablePriorityAccountProtection parameter enables or disable priority account protection in the organization. Valid values are: + +- $true: Priority account protection is enabled. +- $false: Priority account protection is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDehydratedFlag +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/p/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Set-EventLogLevel.md b/exchange/exchange-ps/exchange/Set-EventLogLevel.md similarity index 84% rename from exchange/exchange-ps/exchange/server-health-and-performance/Set-EventLogLevel.md rename to exchange/exchange-ps/exchange/Set-EventLogLevel.md index af23a499a8..4b819c2bb3 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Set-EventLogLevel.md +++ b/exchange/exchange-ps/exchange/Set-EventLogLevel.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/set-eventloglevel +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-EventLogLevel @@ -17,17 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Set-EventLogLevel cmdlet to set the event log level registry value for the specified category. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-EventLogLevel [-Identity] -Level [-Confirm] - [-WhatIf] [] +Set-EventLogLevel [-Identity] -Level + [-Confirm] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -38,7 +39,7 @@ Set-EventLogLevel -Identity "Exchange01\MSExchangeTransport\SmtpReceive" -Level This example sets the event log level to High for the MSExchangeTransport\\SmtpReceive event logging category on the Exchange server Exchange01. -Note: Run the Get-EventLogLevel cmdlet to retrieve a list of the event categories on your server. For more information, see [Get-EventLogLevel](https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/get-eventloglevel). +**Note**: Run the Get-EventLogLevel cmdlet to retrieve a list of the event categories on your server. For more information, see [Get-EventLogLevel](https://learn.microsoft.com/powershell/module/exchange/get-eventloglevel). ## PARAMETERS @@ -62,13 +63,9 @@ Accept wildcard characters: False The Level parameter specifies the log level for the specific event logging category. The valid values are: - Lowest - - Low - - Medium - - High - - Expert ```yaml @@ -87,8 +84,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,12 +121,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md b/exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md new file mode 100644 index 0000000000..77225894de --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md @@ -0,0 +1,279 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-EventsFromEmailConfiguration + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-EventsFromEmailConfiguration cmdlet to modify the events from email settings on a mailbox. on Outlook clients and Outlook on the web. These settings define whether Outlook or Outlook on the web (formerly known as Outlook Web App) automatically discovers events from email messages and adds them to the user's calendar. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Set-EventsFromEmailConfiguration [-Identity] + [-CreateEventsFromEmailAsPrivate ] + [-EventReservationProcessingLevel ] + [-FlightReservationProcessingLevel ] + [-FoodEstablishmentReservationProcessingLevel ] + [-InvoiceProcessingLevel ] + [-LodgingReservationProcessingLevel ] + [-ParcelDeliveryProcessingLevel ] + [-RentalCarReservationProcessingLevel ] + [-ServiceReservationProcessingLevel ] + [] +``` + +### ResetSettings +``` +Set-EventsFromEmailConfiguration [-Identity] + [-ResetSettings] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-EventsFromEmailConfiguration -Identity peter@contoso.com -InvoiceProgressingLevel Disabled +``` + +This example disables the discovery of invoices from messages for the user. + +### Example 2 +```powershell +Set-EventsFromEmailConfiguration -Identity peter@contoso.com -ServiceReservationProcessingLevel Calendar -CreateEventsFromEmailAsPrivate $true +``` + +This example enables the discovery of service reservations, automatically adds them to the user's calendar, and makes these automatically added events private. + +### Example 3 +```powershell +Set-EventsFromEmailConfiguration -Identity peter@contoso.com -ResetSettings +``` + +This example resets Events from Email settings for the user. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -CreateEventsFromEmailAsPrivate +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. +- $false: The events are created as normal events. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventReservationProcessingLevel +This parameter has been deprecated and is no longer used. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FlightReservationProcessingLevel +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. +- Email: Discover flight reservations from messages, but don't automatically add them to the user's calendar. +- Calendar: Discover flight reservations from messages and automatically add them to the user's calendar. This is the default value. + +Note that these values are case sensitive. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FoodEstablishmentReservationProcessingLevel +This parameter has been deprecated and is no longer used. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InvoiceProcessingLevel +This parameter has been deprecated and is no longer used. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LodgingReservationProcessingLevel +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. +- Email: Discover lodging reservations from messages however do not automatically add these to the user's calendar. +- Calendar: Discover lodging reservations from messages and automatically add them to the user's calendar. This is the default value. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParcelDeliveryProcessingLevel +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. +- Email: Discover parcel deliveries from messages however do not automatically add these to the user's calendar. +- Calendar: Discover parcel deliveries from messages and automatically add them to the user's calendar. This is the default value. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RentalCarReservationProcessingLevel +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. +- Email: Discover rental car reservations from messages, but don't automatically add them to the user's calendar. +- Calendar: Discover rental car reservations from messages and automatically add them to the user's calendar. This is the default value. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResetSettings +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceReservationProcessingLevel +This parameter has been deprecated and is no longer used. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-ExchangeAssistanceConfig.md b/exchange/exchange-ps/exchange/Set-ExchangeAssistanceConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/organization/Set-ExchangeAssistanceConfig.md rename to exchange/exchange-ps/exchange/Set-ExchangeAssistanceConfig.md index 1525eed5ca..69e2cfccc7 100644 --- a/exchange/exchange-ps/exchange/organization/Set-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/exchange/Set-ExchangeAssistanceConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-exchangeassistanceconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ExchangeAssistanceConfig @@ -17,24 +16,37 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ExchangeAssistanceConfig cmdlet to modify the Microsoft Exchange Help configurations for your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-ExchangeAssistanceConfig [[-Identity] ] - [-CommunityLinkDisplayEnabled ] [-CommunityURL ] [-Confirm] - [-ControlPanelFeedbackEnabled ] [-ControlPanelFeedbackURL ] [-ControlPanelHelpURL ] - [-DomainController ] [-ExchangeHelpAppOnline ] - [-ManagementConsoleFeedbackEnabled ] [-ManagementConsoleFeedbackURL ] - [-ManagementConsoleHelpURL ] [-OWAFeedbackEnabled ] [-OWAFeedbackURL ] - [-OWAHelpURL ] [-OWALightFeedbackEnabled ] [-OWALightFeedbackURL ] - [-OWALightHelpURL ] [-PrivacyLinkDisplayEnabled ] [-PrivacyStatementURL ] [-WhatIf] + [-CommunityLinkDisplayEnabled ] + [-CommunityURL ] + [-Confirm] + [-ControlPanelFeedbackEnabled ] + [-ControlPanelFeedbackURL ] + [-ControlPanelHelpURL ] + [-DomainController ] + [-ExchangeHelpAppOnline ] + [-ManagementConsoleFeedbackEnabled ] + [-ManagementConsoleFeedbackURL ] + [-ManagementConsoleHelpURL ] + [-OWAFeedbackEnabled ] + [-OWAFeedbackURL ] + [-OWAHelpURL ] + [-OWALightFeedbackEnabled ] + [-OWALightFeedbackURL ] + [-OWALightHelpURL ] + [-PrivacyLinkDisplayEnabled ] + [-PrivacyStatementURL ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,6 +59,22 @@ This example changes the Help location for the Exchange admin center. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -CommunityLinkDisplayEnabled This parameter is reserved for internal Microsoft use. @@ -82,8 +110,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -169,7 +196,6 @@ Accept wildcard characters: False 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. - - $false: Your organization doesn't use the help that's hosted by Microsoft. You need to use the ControlPanelHelpURL, ManagementConsoleHelpURL, OWAHelpURL, and OWALightHelpURL parameters to configure the URLs where the help files are hosted. ```yaml @@ -185,22 +211,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -ManagementConsoleFeedbackEnabled This parameter is reserved for internal Microsoft use. @@ -398,12 +408,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-ExchangeFeature.md b/exchange/exchange-ps/exchange/Set-ExchangeFeature.md new file mode 100644 index 0000000000..f023153538 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ExchangeFeature.md @@ -0,0 +1,176 @@ +--- +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 +ms.author: lusassl +ms.reviewer: srvar +--- + +# Set-ExchangeFeature + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Set-ExchangeFeature cmdlet to approve or block features flighted via Feature Flighting on Exchange Server. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ExchangeFeature [-Identity] + [-Approve] + [-Block] + [-Confirm] + [-FeatureID ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Set-ExchangeFeature cmdlet lets you approve or block features flighted via Feature Flighting, a service introduced in the Exchange Server 2019 CU15 (2025H1) update. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ExchangeFeature -Identity ex01.contoso.com -FeatureID @("F1.1.1") -Approve +``` + +This example approves the feature F1.1.1 on the computer named ex01.contoso.com. + +### Example 2 +```powershell +Set-ExchangeFeature -Identity ex01.contoso.com -FeatureID @("F1.1.1", "F1.2.1", "F2.1.1") -Approve +``` + +This example approves the features F1.1.1, F1.2.1, and F2.1.1 on the computer named ex01.contoso.com. + +### Example 3 +```powershell +Set-ExchangeFeature -Identity ex01.contoso.com -FeatureID @("F1.1.1", "F1.2.1", "F2.1.1") -Block +``` + +This example blocks the features F1.1.1, F1.2.1, and F2.1.1 on the computer named ex01.contoso.com. + +## PARAMETERS + +### -Identity +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +```yaml +Type: ServerIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Approve +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Block +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FeatureID +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-ExchangeServer.md b/exchange/exchange-ps/exchange/Set-ExchangeServer.md similarity index 77% rename from exchange/exchange-ps/exchange/organization/Set-ExchangeServer.md rename to exchange/exchange-ps/exchange/Set-ExchangeServer.md index 58bf44453c..b010016da0 100644 --- a/exchange/exchange-ps/exchange/organization/Set-ExchangeServer.md +++ b/exchange/exchange-ps/exchange/Set-ExchangeServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-exchangeserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ExchangeServer @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ExchangeServer cmdlet to set Exchange attributes in Active Directory for a specified server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,23 +24,29 @@ For information about the parameter sets in the Syntax section below, see [Excha Set-ExchangeServer [-Identity] [-Confirm] [-CustomerFeedbackEnabled ] + [-DataCollectionEnabled ] [-DomainController ] [-ErrorReportingEnabled ] [-InternetWebProxy ] [-InternetWebProxyBypassList ] + [-MitigationsApplied ] + [-MitigationsBlocked ] + [-MitigationsEnabled ] [-MonitoringGroup ] [-ProductKey ] + [-RingLevel ] [-StaticConfigDomainController ] [-StaticDomainControllers ] [-StaticExcludedDomainControllers ] [-StaticGlobalCatalogs ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Set-ExchangeServer cmdlet sets generic Exchange attributes in Active Directory for a specified computer. You can only use this task on one server at a time. If you want to bulk manage your servers running Microsoft Exchange, add this task to a script. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,11 +77,8 @@ This example removes an Exchange server from the Customer Experience Improvement 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -95,8 +97,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -128,6 +129,25 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DataCollectionEnabled +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. +- $false: Data collection is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DomainController The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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 +217,62 @@ Required: False Position: Named Default value: None Accept pipeline input: False -Accept wildcard characters: True +Accept wildcard characters: False +``` + +### -MitigationsApplied +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MitigationsBlocked +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")`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MitigationsEnabled +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. +- $false: Mitigations are not automatically applied on the Exchange server. + +For more information, see [Exchange Emergency Mitigation (EM) service](https://learn.microsoft.com/exchange/exchange-emergency-mitigation-service). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False ``` ### -MonitoringGroup @@ -232,6 +307,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RingLevel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -StaticConfigDomainController The StaticConfigDomainController parameter specifies whether to configure a domain controller to be used by the server via Directory Service Access (DSAccess). @@ -317,12 +408,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Set-ExchangeSettings.md b/exchange/exchange-ps/exchange/Set-ExchangeSettings.md similarity index 87% rename from exchange/exchange-ps/exchange/organization/Set-ExchangeSettings.md rename to exchange/exchange-ps/exchange/Set-ExchangeSettings.md index 7a5c7b7377..436392e2c0 100644 --- a/exchange/exchange-ps/exchange/organization/Set-ExchangeSettings.md +++ b/exchange/exchange-ps/exchange/Set-ExchangeSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-exchangesettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ExchangeSettings @@ -17,17 +16,19 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ExchangeSettings cmdlet to configure Exchange setting objects that you created with the New-ExchangeSettings cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### ClearHistory ``` -Set-ExchangeSettings [-Identity] [-ClearHistory] -Reason +Set-ExchangeSettings [-Identity] -Reason + [-ClearHistory] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UpdateSetting @@ -37,7 +38,8 @@ Set-ExchangeSettings [-Identity] -ConfigName ] [-Force] [-GroupName ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RemoveSetting @@ -47,14 +49,16 @@ Set-ExchangeSettings [-Identity] -ConfigName ] [-Force] [-GroupName ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### CreateSettingsGroup ``` -Set-ExchangeSettings [-Identity] [-CreateSettingsGroup] - -ExpirationDate -Reason [-ConfigPairs ] +Set-ExchangeSettings [-Identity] -ExpirationDate -Reason + [-ConfigPairs ] [-Confirm] + [-CreateSettingsGroup] [-Disable] [-DomainController ] [-Force] @@ -63,60 +67,77 @@ Set-ExchangeSettings [-Identity] [-CreateSettingsG [-MinVersion ] [-NameMatch ] [-Priority ] - [-Scope ] [-ScopeFilter ] - [-WhatIf] [] + [-Scope ] + [-ScopeFilter ] + [-WhatIf] + [] ``` ### CreateSettingsGroupGuid ``` -Set-ExchangeSettings [-Identity] [-CreateSettingsGroup] - -ExpirationDate -GuidMatch -Reason [-ConfigPairs ] [-Confirm] +Set-ExchangeSettings [-Identity] -ExpirationDate -GuidMatch -Reason + [-ConfigPairs ] + [-Confirm] + [-CreateSettingsGroup] [-Disable] [-DomainController ] [-Force] [-GroupName ] [-Priority ] - [-Scope ] [-WhatIf] + [-Scope ] + [-WhatIf] [] ``` ### CreateSettingsGroupAdvanced ``` -Set-ExchangeSettings [-Identity] [-CreateSettingsGroup] -Reason -SettingsGroup +Set-ExchangeSettings [-Identity] -Reason -SettingsGroup + [-CreateSettingsGroup] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### CreateSettingsGroupGeneric ``` -Set-ExchangeSettings [-Identity] [-CreateSettingsGroup] - -ExpirationDate -Reason [-ConfigPairs ] [-GenericScopeName ] [-GenericScopeValue ] [-GroupName ] +Set-ExchangeSettings [-Identity] -ExpirationDate -Reason + [-CreateSettingsGroup] + [-ConfigPairs ] + [-GenericScopeName ] + [-GenericScopeValue ] + [-GroupName ] [-Confirm] [-Disable] [-DomainController ] [-Force] [-Priority ] [-Scope ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UpdateSettingsGroup ``` -Set-ExchangeSettings [-Identity] [-ExpirationDate ] -Reason [-GroupName ] [-UpdateSettingsGroup] +Set-ExchangeSettings [-Identity] -Reason + [-ExpirationDate ] + [-GroupName ] + [-UpdateSettingsGroup] [-Confirm] [-DomainController ] [-Force] [-Priority ] [-ScopeFilter ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RemoveMultipleSettings ``` -Set-ExchangeSettings [-Identity] -Reason - -ConfigPairs [-GroupName ] [-RemoveSetting] +Set-ExchangeSettings [-Identity] -Reason -ConfigPairs + [-GroupName ] + [-RemoveSetting] [-Confirm] [-DomainController ] [-Force] @@ -126,44 +147,53 @@ Set-ExchangeSettings [-Identity] -Reason ### RemoveSettingsGroup ``` -Set-ExchangeSettings [-Identity] -Reason [-GroupName ] [-RemoveSettingsGroup] +Set-ExchangeSettings [-Identity] -Reason + [-GroupName ] + [-RemoveSettingsGroup] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UpdateSettingsGroupAdvanced ``` -Set-ExchangeSettings [-Identity] -Reason -SettingsGroup [-UpdateSettingsGroup] +Set-ExchangeSettings [-Identity] -Reason -SettingsGroup + [-UpdateSettingsGroup] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### UpdateMultipleSettings ``` -Set-ExchangeSettings [-Identity] -Reason - -ConfigPairs [-GroupName ] [-UpdateSetting] +Set-ExchangeSettings [-Identity] -Reason -ConfigPairs + [-GroupName ] + [-UpdateSetting] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### EnableSettingsGroup ``` Set-ExchangeSettings [-Identity] -Reason - [-EnableGroup [-DisableGroup ] + [-EnableGroup ] + [-DisableGroup ] [-Confirm] [-DomainController ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -229,7 +259,7 @@ Accept wildcard characters: False ``` ### -ConfigPairs -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. +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. @@ -298,7 +328,7 @@ Accept wildcard characters: False ### -ExpirationDate 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". +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". You can only use the ExpirationDate parameter with the CreateSettingsGroup or UpdateSettings group parameters. @@ -457,10 +487,11 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -479,7 +510,7 @@ The Disable switch specifies that the Exchange settings group is disabled. You d You can only use this switch with the CreateSettingsGroup switch. -To use this switch to enable an Exchange settings group, use the syntax -Disable:$false. +To use this switch to enable an Exchange settings group, use this exact syntax `-Disable:$false`. ```yaml Type: SwitchParameter @@ -547,7 +578,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -598,11 +631,8 @@ Accept wildcard characters: False 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. - - Modify the ExpirationDate, Priority, and ScopeFilter values of existing Exchange settings groups. - - Remove existing Exchange settings groups. - - Add, remove, or update Exchange setting objects in existing Exchange settings groups. If the value contains spaces, enclose the value in quotation marks ("). @@ -700,19 +730,12 @@ Accept wildcard characters: False The Scope parameter specifies the scope of the Exchange settings object. Valid values are: - Dag - - Database - - Forest - - Generic - - Organization - - Process - - Server - - User ```yaml @@ -729,19 +752,16 @@ Accept wildcard characters: False ``` ### -ScopeFilter -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. +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. - Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter with the Scope parameter and the value Forest or other scope-related parameters. @@ -781,12 +801,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/exchange/Set-ExoPhishSimOverrideRule.md new file mode 100644 index 0000000000..2b5d969329 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ExoPhishSimOverrideRule.md @@ -0,0 +1,240 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ExoPhishSimOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ExoPhishSimOverrideRule cmdlet to modify third-party phishing simulation override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ExoPhishSimOverrideRule [-Identity] + [-AddDomains ] + [-AddSenderIpRanges ] + [-Comment ] + [-Confirm] + [-DomainController ] + [-RemoveDomains ] + [-RemoveSenderIpRanges ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoPhishSimOverrideRule | Set-ExoPhishSimOverrideRule -AddDomains blueyonderairlines.com -RemoveSenderIpRanges 192.168.1.55 +``` + +This example modifies the (presumably only) phishing simulation override rule with the specified settings. + +This example modifies the phishing simulation override rule with the specified settings. + +### Example 2 +```powershell +Set-ExoPhishSimOverrideRule -Identity "_Exe:PhishSimOverr:6fed4b63-3563-495d-a481-b24a311f8329" -AddDomains blueyonderairlines.com -RemoveSenderIpRanges 192.168.1.55 +``` + +This example modifies the specified phishing simulation override rule with the specified settings. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +Use the Get-ExoPhishSimOverrideRule cmdlet to find the values. The name of the rule uses the following syntax: `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AddDomains +The AddDomains parameter specifies an existing entry to add to the list of email domains that are used by the third-party phishing simulation. + +You can specify multiple values separated by commas. A maximum of 20 entries are allowed in the list. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSenderIpRanges +The AddSenderIpRanges parameter specifies an existing entry to add to the list of source IP addresses that are used by the third-party phishing simulation. Valid values are: + +- Single IP address: For example, 192.168.1.1. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +A maximum of 10 entries are allowed in the list. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveDomains +The RemoveDomains parameter specifies an existing entry to remove from the list of email domains that are used by the third-party phishing simulation. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSenderIpRanges +The RemoveSenderIpRanges parameter specifies an existing entry to remove from the list of source IP addresses that are used by the third-party phishing simulation. Valid values are: + +- Single IP address: For example, 192.168.1.1. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/p/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/exchange/Set-ExoSecOpsOverrideRule.md new file mode 100644 index 0000000000..b20f1787e3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ExoSecOpsOverrideRule.md @@ -0,0 +1,154 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ExoSecOpsOverrideRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ExoSecOpsOverrideRule cmdlet to modify SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +**Tip**: This cmdlet doesn't modify email addresses in the SecOps override rule. To modify the email addresses in the SecOps override rule, use the Set-SecOpsOverridePolicy cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ExoSecOpsOverrideRule [-Identity] + [-Comment ] + [-Confirm] + [-DomainController ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-ExoSecOpsOverrideRule| Set-ExoSecOpsOverrideRule -Comment "Contact IT Management before modifying or removing this rule." +``` + +This example adds a comment to the (presumably only) SecOps mailbox override rule with the specified settings. + +### Example 2 +```powershell +Set-ExoSecOpsOverrideRule -Identity "_Exe:SecOpsOverrid:312c23cf-0377-4162-b93d-6548a9977efb" -Comment "Contact IT Management before modifying or removing this rule." +``` + +This example adds a comment to the specified SecOps mailbox override rule. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +Use the Get-ExoSecOpsMailboxRule cmdlet to find these values. The name of the rule uses the following syntax: `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ExternalInOutlook.md b/exchange/exchange-ps/exchange/Set-ExternalInOutlook.md new file mode 100644 index 0000000000..83221e105b --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ExternalInOutlook.md @@ -0,0 +1,138 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ExternalInOutlook + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ExternalInOutlook cmdlet to modify the configuration of external sender identification that's available in Outlook, Outlook for Mac, Outlook on the web, and Outlook for iOS and Android. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ExternalInOutlook [[-Identity] ] + [-AllowList ] + [-Enabled ] + [] +``` + +## DESCRIPTION +If your organization already uses mail flow rules (also known as transport rules) to add text to the subject line of messages from external senders, you should disable those rules before you enable this feature to avoid duplication. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ExternalInOutlook -Enabled $true +``` + +This example enables external sender identification in supported versions of Outlook. + +### Example 2 +```powershell +Set-ExternalInOutlook -AllowList admin@fabrikam.com,admin@fourthcoffee.com +``` + +This example prevents the specified email addresses from receiving the External icon in the area of the subject line in supported versions of Outlook. + +### Example 3 +```powershell +Set-ExternalInOutlook -AllowList @{Add="admin@cohovineyard.com"; Remove="admin@fourthcoffee.com"} +``` + +This example adds and removes the specified email addresses from the exception list without affecting other existing entries. + +## PARAMETERS + +### -Identity +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. + +If you specify an invalid Identity value, the cmdlet still runs and changes the settings for the entire organization. Always verify the Identity value before you run this cmdlet. + +```yaml +Type: OrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowList +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +This parameter is meaningful only when the value of the Enabled parameter is $true. + +The maximum number of entries is 50, and the total size of all entries can't exceed one kilobyte. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. +- $false: External sender identification in Outlook is disabled. + +After an admin enables this setting, it can take between 24 and 48 hours for users to see the External icon in messages from external senders in supported versions of Outlook. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-OrganizationConfig](https://learn.microsoft.com/powershell/module/exchange/set-organizationconfig) diff --git a/exchange/exchange-ps/exchange/Set-FeatureConfiguration.md b/exchange/exchange-ps/exchange/Set-FeatureConfiguration.md new file mode 100644 index 0000000000..775dd3b86a --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FeatureConfiguration.md @@ -0,0 +1,195 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-featureconfiguration +applicable: Security & Compliance +title: Set-FeatureConfiguration +schema: 2.0.0 +--- + +# Set-FeatureConfiguration + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +> [!NOTE] +> This cmdlet is currently available in Public Preview, isn't available in all organizations, and is subject to change. + +Use the Set-FeatureConfiguration cmdlet to modify Microsoft Purview feature configurations within your organization, including: + +- Collection policies. +- Advanced label based protection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FeatureConfiguration [-Identity] [-Locations ] + [-Comment ] + [-Confirm] + [-Mode ] + [-ScenarioConfig ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Set-FeatureConfiguration "DSPM for AI - Capture interactions for Copilot experiences" -ScenarioConfig '{"Activities":["UploadText","DownloadText"],"EnforcementPlanes":["CopilotExperiences"],"SensitiveTypeIds":["All"],"IsIngestionEnabled":false}' +``` + +This example updates a collection policy named "DSPM for AI - Capture interactions for Copilot experiences" to disable content capture. + +### Example 2 +```powershell +Set-FeatureConfiguration "Microsoft Copilot collection policy for Contoso Sales" -Locations '[{"Workload":"Applications","Location":"52655","AddInclusions":[{"Type":"Group","Identity":"USSales@contoso.com"}]}]' +``` + +This example updates a collection policy named "Microsoft Copilot collection policy for Contoso Sales" to include the USSales@contoso.com group. + +### Example 3 +```powershell +Set-FeatureConfiguration "Microsoft Copilot collection policy for Contoso Sales" -Locations '[{"Workload":"Applications","Location":"52655","AddExclusions":[{"Type":"IndividualResource","Identity":"adele@contoso.com"}]}]' +``` + +This example updates a collection policy named "Microsoft Copilot collection policy for Contoso Sales" to exclude the adele@contoso.com. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locations +The locations parameter specifies where the feature configuration applies. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Mode +The Mode parameter specifies feature configuration mode. Valid values are: + +- Enable: The feature configuration is enabled. +- Disable: The feature configuration is disabled. + +```yaml +Type: PolicyMode +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScenarioConfig +The ScenarioConfig parameter specifies additional information about the feature configuration. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md similarity index 85% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Set-FederatedOrganizationIdentifier.md rename to exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md index 1c660014e2..92e99bb1fe 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-federatedorganizationidentifier -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-FederatedOrganizationIdentifier @@ -17,16 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-FederatedOrganizationIdentifier cmdlet to configure the federated organization identifier for the Exchange organization. -For more details, see [Federation](https://docs.microsoft.com/exchange/federation-exchange-2013-help). +For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-FederatedOrganizationIdentifier [[-Identity] ] [-AccountNamespace ] - [-Confirm] [-DelegationFederationTrust ] [-DomainController ] - [-Enabled ] [-OrganizationContact ] [-WhatIf] [-DefaultDomain ] +Set-FederatedOrganizationIdentifier [[-Identity] ] + [-AccountNamespace ] + [-Confirm] + [-DefaultDomain ] + [-DelegationFederationTrust ] + [-DomainController ] + [-Enabled ] + [-OrganizationContact ] + [-WhatIf] [] ``` @@ -35,7 +40,7 @@ You must configure a federated organization identifier to create an account name You can temporarily disable federation by disabling the organization identifier. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,6 +67,22 @@ This example enables the organization identifier. This enables federation for th ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -AccountNamespace The AccountNamespace parameter specifies the federated domain to be used to establish the organization identifier with the Microsoft Federation Gateway. @@ -69,7 +90,7 @@ The AccountNamespace parameter specifies the federated domain to be used to esta Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -81,15 +102,30 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultDomain +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 @@ -105,7 +141,7 @@ The DelegationFederationTrust parameter specifies the identity of the federation Type: FederationTrustIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -141,7 +177,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -150,22 +186,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -OrganizationContact The OrganizationContact parameter specifies the SMTP address of the federation contact. @@ -173,7 +193,7 @@ The OrganizationContact parameter specifies the SMTP address of the federation c Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -189,23 +209,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultDomain -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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -219,12 +223,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-FederationTrust.md b/exchange/exchange-ps/exchange/Set-FederationTrust.md similarity index 88% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Set-FederationTrust.md rename to exchange/exchange-ps/exchange/Set-FederationTrust.md index c7d429e8a1..5a6e6a3d8a 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-FederationTrust.md +++ b/exchange/exchange-ps/exchange/Set-FederationTrust.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-federationtrust +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-FederationTrust @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-FederationTrust cmdlet to modify an existing federation trust. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -34,7 +33,8 @@ Set-FederationTrust [-Identity] -ApplicationUri [-PublishFederationCertificate] +Set-FederationTrust [-Identity] + [-PublishFederationCertificate] [-Confirm] [-DomainController ] [-Name ] @@ -51,30 +51,38 @@ Set-FederationTrust [-Identity] [-Name ] [-RefreshMetadata] [-Thumbprint ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can use the Set-FederationTrust cmdlet to manage the certificates used for the federation trust. You can also use the Set-FederationTrust cmdlet to refresh the metadata document from the Microsoft Federation Gateway and download its certificate. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-FederationTrust -Identity "Microsoft Federation Gateway" -Thumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 +Set-FederationTrust -Identity "Azure AD Authentication" -Thumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 ``` This example configures the federation trust Microsoft Federation Gateway to use the certificate with the thumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 as the next certificate. ### Example 2 ```powershell -Set-FederationTrust -Identity "Microsoft Federation Gateway" -PublishFederationCertificate +Set-FederationTrust -Identity "Azure AD Authentication" -PublishFederationCertificate ``` This example configures the federation trust Microsoft Federation Gateway to use the next certificate as the current certificate. +### Example 3 +```powershell +Set-FederationTrust -Identity "Azure AD Authentication" -MetadataUrl https://nexus.microsoftonline-p.com/federationmetadata/2006-12/federationmetadata.xml +``` + +This example updates the configuration if the tenant is hosted in Microsoft 365 U.S. Government GCC High or DoD environment. + Before you configure a federation trust to use the next certificate as the current certificate, you need to use the Test-FederationTrust cmdlet to verify that the certificate is available on all Exchange servers. ## PARAMETERS @@ -82,6 +90,8 @@ Before you configure a federation trust to use the next certificate as the curre ### -Identity The Identity parameter specifies the name of the federation trust being modified. +**Note**: For Exchange Online organizations, use the value "Microsoft Entra authentication". + ```yaml Type: FederationTrustIdParameter Parameter Sets: (All) @@ -134,8 +144,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -200,7 +209,7 @@ Accept wildcard characters: False ``` ### -RefreshMetadata -The RefreshMetadata switch specifies that the metadata document and certificate is retrieved again from the Microsoft Federation Gateway. +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 @@ -252,12 +261,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-FilePlanPropertyAuthority.md b/exchange/exchange-ps/exchange/Set-FilePlanPropertyAuthority.md new file mode 100644 index 0000000000..2c6319179c --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FilePlanPropertyAuthority.md @@ -0,0 +1,121 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertyauthority +applicable: Security & Compliance +title: Set-FilePlanPropertyAuthority +schema: 2.0.0 +--- + +# Set-FilePlanPropertyAuthority + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-FilePlanPropertyAuthority cmdlet to modify file plan property authorities. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FilePlanPropertyAuthority [-Identity] + [-Confirm] + [-DisplayName ] + [-WhatIf] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Set-FilePlanPropertyAuthority -Identity "Contoso Authority" -DisplayName "Parent authority for Contoso" +``` + +This example modifies the display name for the custom file plan property authority named Contoso Authority. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-FilePlanPropertyCategory.md b/exchange/exchange-ps/exchange/Set-FilePlanPropertyCategory.md new file mode 100644 index 0000000000..c997f07927 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FilePlanPropertyCategory.md @@ -0,0 +1,119 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertycategory +applicable: Security & Compliance +title: Set-FilePlanPropertyCategory +schema: 2.0.0 +--- + +# Set-FilePlanPropertyCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-FilePlanPropertyCategory cmdlet to modify file plan property categories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FilePlanPropertyCategory [-Identity] [-Confirm] [-DisplayName ] + [-WhatIf] [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Set-FilePlanPropertyCategory -Identity "Contoso Category" -DisplayName "Parent category for Contoso" +``` + +This example modifies the display name for the custom file plan property category named Contoso Category. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-FilePlanPropertyCitation.md b/exchange/exchange-ps/exchange/Set-FilePlanPropertyCitation.md new file mode 100644 index 0000000000..78ebda0733 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FilePlanPropertyCitation.md @@ -0,0 +1,156 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertycitation +applicable: Security & Compliance +title: Set-FilePlanPropertyCitation +schema: 2.0.0 +--- + +# Set-FilePlanPropertyCitation + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-FilePlanPropertyCitation cmdlet to modify file plan property citations. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FilePlanPropertyCitation [-Identity] + [-CitationJurisdiction ] + [-CitationUrl ] + [-Confirm] + [-DisplayName ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Set--FilePlanPropertyCitation -Identity "Contoso-0001" -CitationUrl https:intra.contoso.com/citation +``` + +This example modifies the citation URL for the custom file plan property citation named Contoso-0001. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -CitationJurisdiction +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CitationUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-FilePlanPropertyDepartment.md b/exchange/exchange-ps/exchange/Set-FilePlanPropertyDepartment.md new file mode 100644 index 0000000000..40d312c5a8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FilePlanPropertyDepartment.md @@ -0,0 +1,126 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertydepartment +applicable: Security & Compliance +title: Set-FilePlanPropertyDepartment +schema: 2.0.0 +--- + +# Set-FilePlanPropertyDepartment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-FilePlanPropertyDepartment cmdlet to modify file plan property departments. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FilePlanPropertyDepartment [-Identity] + [-Confirm] + [-DisplayName ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +Use the Set-FilePlanPropertyDepartment cmdlet to + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## EXAMPLES + +### Example 1 +```powershell +Set-FilePlanPropertyDepartment -Identity "Contoso HR" -DisplayName "HR department for Contoso" +``` + +This example modifies the display name for the custom file plan property department named Contoso HR. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/exchange/Set-FilePlanPropertyReferenceId.md new file mode 100644 index 0000000000..0be4986969 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FilePlanPropertyReferenceId.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertyreferenceid +applicable: Security & Compliance +title: Set-FilePlanPropertyReferenceId +schema: 2.0.0 +--- + +# Set-FilePlanPropertyReferenceId + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-FilePlanPropertyReferenceId cmdlet to modify file plan property reference IDs. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FilePlanPropertyReferenceId [-Identity] + [-Confirm] + [-DisplayName ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Set-FilePlanPropertyReferenceId -Identity "Contoso-0001" -DisplayName "Reference ID Contoso-0001" +``` + +This example modifies the display name for the custom file plan property reference ID named Contoso-0001. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-FilePlanPropertySubCategory.md b/exchange/exchange-ps/exchange/Set-FilePlanPropertySubCategory.md new file mode 100644 index 0000000000..384fa72ff4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FilePlanPropertySubCategory.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertysubcategory +applicable: Security & Compliance +title: Set-FilePlanPropertySubCategory +schema: 2.0.0 +--- + +# Set-FilePlanPropertySubCategory + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-FilePlanPropertySubCategory cmdlet to modify file plan property subcategories. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FilePlanPropertySubCategory [-Identity] + [-Confirm] + [-DisplayName ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920). + +## EXAMPLES + +### Example 1 +```powershell +Set-FilePlanPropertySubCategory -Identity "US Tax" -DisplayName "Subcategory for US Tax" +``` + +This example modifies the display name for the custom file plan property subcategory named US Tax. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- Id + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-FocusedInbox.md b/exchange/exchange-ps/exchange/Set-FocusedInbox.md new file mode 100644 index 0000000000..daebaa21e2 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-FocusedInbox.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-FocusedInbox + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-FocusedInbox cmdlet to enable or disable Focused Inbox for mailboxes in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-FocusedInbox -Identity + [-FocusedInboxOn ] + [-UseCustomRouting] + [] +``` + +## DESCRIPTION +Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-FocusedInbox -Identity laura@contoso.com -FocusedInboxOn $false +``` + +This example disables Focused Inbox for the mailbox of laura@contoso.com. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FocusedInboxOn +The FocusedInboxOn parameter enables or disables Focused Inbox for the mailbox. Valid values are: + +- $true: Focused Inbox is enabled. This is the default value. +- $false: Focused Inbox is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseCustomRouting +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-ForeignConnector.md b/exchange/exchange-ps/exchange/Set-ForeignConnector.md similarity index 88% rename from exchange/exchange-ps/exchange/mail-flow/Set-ForeignConnector.md rename to exchange/exchange-ps/exchange/Set-ForeignConnector.md index 34e8cf60ca..8ce9583a9c 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-ForeignConnector.md +++ b/exchange/exchange-ps/exchange/Set-ForeignConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-foreignconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ForeignConnector @@ -17,22 +16,33 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ForeignConnector cmdlet to modify an existing Foreign connector in the Transport service of a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ForeignConnector [-Identity] [-AddressSpaces ] - [-Comment ] [-Confirm] [-DomainController ] [-DropDirectory ] - [-DropDirectoryQuota ] [-Enabled ] [-Force] [-IsScopedConnector ] - [-MaxMessageSize ] [-Name ] [-RelayDsnRequired ] - [-SourceTransportServers ] [-WhatIf] [] +Set-ForeignConnector [-Identity] + [-AddressSpaces ] + [-Comment ] + [-Confirm] + [-DomainController ] + [-DropDirectory ] + [-DropDirectoryQuota ] + [-Enabled ] + [-Force] + [-IsScopedConnector ] + [-MaxMessageSize ] + [-Name ] + [-RelayDsnRequired ] + [-SourceTransportServers ] + [-WhatIf] + [] ``` ## DESCRIPTION A Foreign connector uses a Drop directory in the Transport service of a Mailbox server to send messages to a local messaging server that doesn't use SMTP as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Third-party fax gateway servers are examples of foreign gateway servers. The address spaces assigned to a Foreign connector can be SMTP or non-SMTP. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,9 +59,7 @@ This example configures a 10 MB message size limit on the existing Foreign conne 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 - - Connector name - - ServerName\\ConnectorName ```yaml @@ -68,27 +76,22 @@ Accept wildcard characters: False ``` ### -AddressSpaces -The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is as follows: \:\;\ +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. - - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address type, you can enter any text for the address space. - - AddressSpaceCost : The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains a semicolon (;), you must specify the address space cost. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("). For example, the following address space entries are equivalent: - "SMTP:contoso.com;1" - - "contoso.com;1" - - "SMTP:contoso.com" - - contoso.com -You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3". +You may specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. -To add or remove one or more address space values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more address space values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -122,8 +125,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -161,7 +163,6 @@ Accept wildcard characters: False 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. - - DropDirectory parameter in the Set-ForeignConnector cmdlet: This value is set for each Foreign Connector that exists on the server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange 2010 installation folder. The default Exchange 2010 installation folder is C:\\Program Files\\Microsoft\\Exchange Server\\. By default, the value of the DropDirectory parameter is the name of the Foreign connector. @@ -173,9 +174,7 @@ The Drop directory isn't created for you. Therefore, you have to manually create The Drop directory must have the following permissions assigned to it: - Network Service: Full Control - - System: Full Control - - Administrators: Full Control ```yaml @@ -197,13 +196,9 @@ The DropDirectoryQuota parameter specifies the maximum size of all message files When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -240,7 +235,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -277,13 +274,9 @@ The MaxMessageSize parameter specifies the maximum size of a message that can pa When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -338,9 +331,9 @@ Accept wildcard characters: False ### -SourceTransportServers 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -376,12 +369,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-FrontendTransportService.md b/exchange/exchange-ps/exchange/Set-FrontendTransportService.md similarity index 98% rename from exchange/exchange-ps/exchange/mail-flow/Set-FrontendTransportService.md rename to exchange/exchange-ps/exchange/Set-FrontendTransportService.md index 75c784906d..1332c4a436 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-FrontendTransportService.md +++ b/exchange/exchange-ps/exchange/Set-FrontendTransportService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-frontendtransportservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-FrontendTransportService @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-FrontEndTransportService cmdlet to modify the configuration of the Front End Transport service on Exchange 2013 or later servers that have the Client Access server role installed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -65,13 +64,14 @@ Set-FrontendTransportService [-Identity] [-SendProtocolLogPath ] [-TransientFailureRetryCount ] [-TransientFailureRetryInterval ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Front End Transport service runs on all Mailbox servers and acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization. The Front End Transport service only communicates with the Transport service on a Mailbox server, and doesn't queue any messages locally. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -149,13 +149,9 @@ The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent l When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -181,13 +177,9 @@ The AgentLogMaxFileSize parameter specifies the maximum size of each agent log f When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -244,8 +236,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -303,13 +294,9 @@ The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -335,13 +322,9 @@ The ConnectivityLogMaxFileSize parameter specifies the maximum size of each conn When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -419,13 +402,9 @@ The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -451,13 +430,9 @@ The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -667,7 +642,6 @@ Accept wildcard characters: False 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. - - Verbose: Protocol logging is enabled for the intra-organization Send connector in the Front End Transport service. This is the default value. The location of the log files is controlled by the SendProtocolLogPath parameter. ```yaml @@ -729,13 +703,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -765,13 +735,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -837,13 +803,9 @@ The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -909,13 +871,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -945,13 +903,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -979,7 +933,6 @@ The SendProtocolLogPath parameter specifies the location of the protocol log dir 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: - The IntraOrgConnectorProtocolLoggingLevel parameter. - - The ProtocolLoggingLevel parameter on the Set-SendConnector cmdlet for each Send connector in the Front End Transport service. ```yaml @@ -1052,12 +1005,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-GlobalAddressList.md b/exchange/exchange-ps/exchange/Set-GlobalAddressList.md similarity index 78% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-GlobalAddressList.md rename to exchange/exchange-ps/exchange/Set-GlobalAddressList.md index fd0d6509e3..b4bbb3747e 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-GlobalAddressList.md +++ b/exchange/exchange-ps/exchange/Set-GlobalAddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/set-globaladdresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-GlobalAddressList @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-GlobalAddressList cmdlet to modify an existing global address list (GAL). -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -50,23 +49,22 @@ Set-GlobalAddressList [-Identity] [-Name ] [-RecipientContainer ] [-RecipientFilter ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - - The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - - The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPath filter. +To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter. -You can't use this cmdlet to replace a precanned filter with a custom OPath filter, or vice-versa. You can only modify the existing filter. +You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -83,9 +81,7 @@ This example assigns a new name, GALwithNewName, to the GAL with the GUID 96d0c5 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 - - Distinguished name (DN) - - GUID ```yaml @@ -106,9 +102,9 @@ The ConditionalCompany parameter specifies a precanned filter that's based on th 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -128,9 +124,9 @@ The ConditionalCustomAttribute1 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -150,9 +146,9 @@ The ConditionalCustomAttribute10 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -172,9 +168,9 @@ The ConditionalCustomAttribute11 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -194,9 +190,9 @@ The ConditionalCustomAttribute12 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -216,9 +212,9 @@ The ConditionalCustomAttribute13 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -238,9 +234,9 @@ The ConditionalCustomAttribute14 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -260,9 +256,9 @@ The ConditionalCustomAttribute15 parameter specifies a precanned filter that's b 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -282,9 +278,9 @@ The ConditionalCustomAttribute2 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -304,9 +300,9 @@ The ConditionalCustomAttribute3 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -326,9 +322,9 @@ The ConditionalCustomAttribute4 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -348,9 +344,9 @@ The ConditionalCustomAttribute5 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -370,9 +366,9 @@ The ConditionalCustomAttribute6 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -392,9 +388,9 @@ The ConditionalCustomAttribute7 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -414,9 +410,9 @@ The ConditionalCustomAttribute8 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -436,9 +432,9 @@ The ConditionalCustomAttribute9 parameter specifies a precanned filter that's ba 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -458,9 +454,9 @@ The ConditionalDepartment parameter specifies a precanned filter that's based on 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -480,9 +476,9 @@ The ConditionalStateOrProvince parameter specifies a precanned filter that's bas 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. -To enter multiple values that overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -500,8 +496,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -538,7 +533,7 @@ Accept wildcard characters: False ### -ForceUpgrade This parameter is available only in on-premises Exchange. -The ForceUpgrade switch specifies whether to suppress 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. +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 @@ -557,15 +552,10 @@ Accept wildcard characters: False 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. - - MailboxUsers - - MailContacts - - MailGroups - - MailUsers - - Resources: This value indicates room or equipment mailboxes. You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. @@ -605,11 +595,8 @@ 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: - Name - - Canonical name - - Distinguished name (DN) - - GUID If you don't use this parameter, the default value is the OU where the object was created. @@ -628,21 +615,16 @@ Accept wildcard characters: False ``` ### -RecipientFilter -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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +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. +- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). - In cloud-based environments, you can't use a wildcard as the first character. For example, `'Sales*'` is allowed, but `'*Sales'` isn't allowed. - - In on-premises Exchange, wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). ```yaml Type: String @@ -678,12 +660,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-Group.md b/exchange/exchange-ps/exchange/Set-Group.md similarity index 85% rename from exchange/exchange-ps/exchange/users-and-groups/Set-Group.md rename to exchange/exchange-ps/exchange/Set-Group.md index 0aba31872b..25c66b6124 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-Group.md +++ b/exchange/exchange-ps/exchange/Set-Group.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-group +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-Group @@ -17,22 +16,35 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-Group cmdlet to modify group object settings. If the group is a mail-enabled security group or a distribution group, you can use the Set-DistributionGroup cmdlet to modify other Microsoft Exchange settings that aren't available by using the Set-Group cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-Group [-Identity] [-BypassSecurityGroupManagerCheck] [-Confirm] [-DisplayName ] - [-DomainController ] [-IgnoreDefaultScope] [-IsHierarchicalGroup ] - [-ManagedBy ] [-Name ] [-Notes ] - [-PhoneticDisplayName ] [-SeniorityIndex ] [-SimpleDisplayName ] [-Universal] [-WhatIf] - [-WindowsEmailAddress ] [] +Set-Group [-Identity] + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-Description ] + [-DisplayName ] + [-DomainController ] + [-IgnoreDefaultScope] + [-IsHierarchicalGroup ] + [-ManagedBy ] + [-Name ] + [-Notes ] + [-PhoneticDisplayName ] + [-SeniorityIndex ] + [-SimpleDisplayName ] + [-Universal] + [-WhatIf] + [-WindowsEmailAddress ] + [] ``` ## DESCRIPTION You can't use the Set-Group cmdlet to modify dynamic distribution groups. To modify dynamic distribution groups, use the Set-DynamicDistributionGroup cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,11 +72,8 @@ This example specifies that the group Human Resources is a hierarchical group an The Identity parameter specifies the group that you want to modify. You can use any value that uniquely identifies the group. For example: - Name - - Distinguished name (DN) - - Canonical DN - - GUID ```yaml @@ -81,14 +90,13 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. 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: +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. -- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +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: +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. - Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. -You don't need to specify a value with this switch. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -105,8 +113,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -122,6 +129,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Description +This parameter is available only in the cloud-based service. + +{{ Fill Description Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DisplayName 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 ("). @@ -163,12 +188,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -204,42 +228,31 @@ Accept wildcard characters: False 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 - - Add or remove group members - - Delete the group - - Approve member depart or join requests (if available) - - Approve messages sent to the group if moderation is enabled, but no moderators are specified. The owner 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 owner. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple owners and overwrite all existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +To enter multiple owners and overwrite all existing entries, use the following syntax: `Owner1,Owner2,...OwnerN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Owner1","Owner2",..."OwnerN"`. + +To add or remove owners without affecting other existing entries, use the following syntax: `@{Add="Owner1","Owner2",...; Remove="Owner3","Owner4"...}`. -To add or remove owners without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +Owners that you specify with this parameter are not added as group members. You need to manually add the owners as a members. -An owner that you specify with this parameter isn't automatically a member of the group. You need to manually add the owner as a member. +**Note**: Group management in Outlook doesn't work when the owner is a mail-enabled security group. To manage the group in Outlook, the owner must be a mailbox or a mail user. ```yaml Type: GeneralRecipientIdParameter[] @@ -322,12 +335,10 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\", """, "'", "(", ")", "+", ",", "-", ".", "/", ":" and "?". +- space +- `" ' ( ) + , - . / : ?` This parameter is meaningful only if the group is mail-enabled. @@ -380,7 +391,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -403,12 +413,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-HoldCompliancePolicy.md new file mode 100644 index 0000000000..d1f0720b66 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-HoldCompliancePolicy.md @@ -0,0 +1,335 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-HoldCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-HoldCompliancePolicy cmdlet to modify existing preservation policies in the Microsoft Purview compliance portal. + +**Note**: The Set-HoldCompliancePolicy cmdlet has been replaced by the Set-RetentionCompliancePolicy cmdlet. If you have scripts that use Set-HoldCompliancePolicy, update them to use Set-RetentionCompliancePolicy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### RetryDistribution +``` +Set-HoldCompliancePolicy [-Identity] + [-RetryDistribution] + [-Confirm] + [-WhatIf] + [] +``` + +### Identity +``` +Set-HoldCompliancePolicy [-Identity] + [-AddExchangeLocation ] + [-AddPublicFolderLocation ] + [-AddSharePointLocation ] + [-Comment ] + [-Confirm] + [-Enabled ] + [-Force] + [-RemoveExchangeLocation ] + [-RemovePublicFolderLocation ] + [-RemoveSharePointLocation ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +**Note**: Don't use a piped Foreach-Object command when adding or removing scope locations: `"Value1","Value2",..."ValueN" | Foreach-Object {Set-HoldCompliancePolicy -Identity "Regulation 123 Compliance" -RemoveExchangeLocation $_}`. + +## EXAMPLES + +### Example 1 +```powershell +Set-HoldCompliancePolicy -Identity "Regulation 123 Compliance" -AddExchangeLocation "Kitty Petersen" -AddSharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -RemovePublicFolderLocation All -Comment "Added new counsel, 9/9/14" +``` + +This example makes the following changes to the existing preservation policy named "Regulation 123 Compliance": + +- Adds the mailbox for the user named Kitty Petersen. +- Adds the SharePoint site `https://contoso.sharepoint.com/sites/teams/finance`. +- Removes public folders. +- Updates the comment. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RetryDistribution +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. + +**Note**: Because the process of retrying distribution is a significant operation, run it only if necessary and for one policy at a time. It is not intended to be run every time you update a policy. If you run a script to update multiple policies, wait until the policy distribution is successful before running the command again for the next policy. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocation +The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddPublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocation +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"`. + +SharePoint sites can't be added to the policy until they have been indexed. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +The RemoveExchangeLocation parameter specifies the existing mailboxes to remove from the policy. Valid values are: + +- A mailbox +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-HoldComplianceRule.md b/exchange/exchange-ps/exchange/Set-HoldComplianceRule.md new file mode 100644 index 0000000000..e86f4d51b9 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-HoldComplianceRule.md @@ -0,0 +1,244 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-HoldComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-HoldComplianceRule cmdlet to modify existing preservation rules in the Microsoft Purview compliance portal. + +**Note**: The Set-HoldComplianceRule cmdlet has been replaced by the Set-RetentionComplianceRule cmdlet. If you have scripts that use Set-HoldComplianceRule, update them to use Set-RetentionComplianceRule. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-HoldComplianceRule [-Identity] + [-Comment ] + [-Confirm] + [-ContentDateFrom ] + [-ContentDateTo ] + [-ContentMatchQuery ] + [-Disabled ] + [-HoldContent ] + [-HoldDurationDisplayHint ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-HoldComplianceRule -Identity "Internal Company Rule" -HoldContent 180 +``` + +This example changes the hold duration for the existing preservation rule named "Internal Company Rule". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateFrom +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateTo +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldContent +The HoldContent parameter specifies the hold duration for the preservation rule. Valid values are: + +- An integer: The hold duration in days. +- Unlimited: The content is held indefinitely. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldDurationDisplayHint +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 +- Months +- Years + +For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. + +```yaml +Type: HoldDurationHint +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/exchange/Set-HostedConnectionFilterPolicy.md similarity index 77% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedConnectionFilterPolicy.md rename to exchange/exchange-ps/exchange/Set-HostedConnectionFilterPolicy.md index 4e2cb95a1d..83888c656c 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Set-HostedConnectionFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-hostedconnectionfilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Set-HostedConnectionFilterPolicy @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Set-HostedConnectionFilterPolicy cmdlet to modify the settings of connection filter policies in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,15 +24,17 @@ For information about the parameter sets in the Syntax section below, see [Excha Set-HostedConnectionFilterPolicy [-Identity] [-AdminDisplayName ] [-ConfigurationXmlRaw ] - [-Confirm] [-EnableSafeList ] + [-Confirm] + [-EnableSafeList ] [-IPAllowList ] [-IPBlockList ] [-MakeDefault] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,18 +46,16 @@ Set-HostedConnectionFilterPolicy "Default" -IPAllowList 192.168.1.10,192.168.1.2 This example modifies the connection filter policy named Default with the following settings: - Messages from 192.168.1.10 and 192.168.1.23 are never identified as spam. - - Messages from 10.10.10.0/25 and 172.17.17.0/24 are always identified as spam. ### Example 2 ```powershell -Set-HostedConnectionFilterPolicy "Default" -IPAllowList @{Add="192.168.2.10","192.169.3.0/24","192.168.4.1-192.168.4.5";Remove="192.168.1.10"} +Set-HostedConnectionFilterPolicy "Default" -IPAllowList @{Add="192.168.2.10","192.169.3.0/24","192.168.4.1-192.168.4.5"; Remove="192.168.1.10"} ``` This example modifies the connection filter policy named Default with the following settings: - The following IP addresses are added to the existing values in the IP allow list: 192.168.2.10, 192.169.3.0/24 and 192.168.4.1-192.168.4.5. - - The IP address 192.168.1.10 is removed from the existing values in the IP allow list. ## PARAMETERS @@ -68,9 +64,7 @@ This example modifies the connection filter policy named Default with the follow 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 - - Distinguished name (DN) - - GUID Typically, you only have one connection filter policy: the default policy named Default. @@ -123,8 +117,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -161,17 +154,15 @@ Accept wildcard characters: False ``` ### -IPAllowList -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. - -You enter the IP addresses using the following syntax: - -- Single IP: For example, 192.168.1.1. +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: -- IP range: You can use an IP address range, for example, 192.168.0.1-192.168.0.254. +- Single IP address: For example, 192.168.1.1. +- IP address range: You can use an IP address range, for example, 192.168.0.1-192.168.0.254. The maximum number of addresses in the range is 256. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32. -- CIDR IP: You can use Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25. Valid network mask values are /24 through /32. +You can specify multiple IP addresses of the same type separated by commas. For example, `SingleIP1, SingleIP2,...SingleIPN` or `CIDRIP1,CIDRIP2,...CIDRIPN`. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: `@{Add="SingleIP1","IPRange1","CIDRIP1",...}`. -You can specify multiple IP addresses of the same type separated by commas. For example, \, \ or \, \. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: @{Add="\","\",\...}. +**Note**: IPv6 ranges are not supported. ```yaml Type: MultiValuedProperty @@ -187,17 +178,15 @@ Accept wildcard characters: False ``` ### -IPBlockList -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. - -You enter the IP addresses using the following syntax: - -- Single IP: For example, 192.168.1.1. +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: -- IP range: You can use an IP address range, for example, 192.168.0.1-192.168.0.254. +- Single IP address: For example, 192.168.1.1. +- IP address range: You can use an IP address range, for example, 192.168.0.1-192.168.0.254. The maximum number of addresses in the range is 256. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32. -- CIDR IP: You can use Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25. Valid network mask values are /24 through /32. +You can specify multiple IP addresses of the same type separated by commas. For example, `SingleIP1, SingleIP2,...SingleIPN` or `CIDRIP1,CIDRIP2,...CIDRIPN`. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: `@{Add="SingleIP1","IPRange1","CIDRIP1",...}`. -You can specify multiple IP addresses of the same type separated by commas. For example, \, \ or \, \. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: @{Add="\","\",\...}. +**Note**: IPv6 ranges are not supported. ```yaml Type: MultiValuedProperty @@ -249,12 +238,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md new file mode 100644 index 0000000000..64de11808a --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md @@ -0,0 +1,1317 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-HostedContentFilterPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-HostedContentFilterPolicy cmdlet to modify spam filter policies (content filter policies) in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-HostedContentFilterPolicy [-Identity] + [-AddXHeaderValue ] + [-AdminDisplayName ] + [-AllowedSenderDomains ] + [-AllowedSenders ] + [-BlockedSenderDomains ] + [-BlockedSenders ] + [-BulkQuarantineTag ] + [-BulkSpamAction ] + [-BulkThreshold ] + [-Confirm] + [-DownloadLink ] + [-EnableEndUserSpamNotifications ] + [-EnableLanguageBlockList ] + [-EnableRegionBlockList ] + [-EndUserSpamNotificationCustomFromAddress ] + [-EndUserSpamNotificationCustomFromName ] + [-EndUserSpamNotificationCustomSubject ] + [-EndUserSpamNotificationFrequency ] + [-EndUserSpamNotificationLanguage ] + [-EndUserSpamNotificationLimit ] + [-HighConfidencePhishAction ] + [-HighConfidencePhishQuarantineTag ] + [-HighConfidenceSpamAction ] + [-HighConfidenceSpamQuarantineTag ] + [-IncreaseScoreWithBizOrInfoUrls ] + [-IncreaseScoreWithImageLinks ] + [-IncreaseScoreWithNumericIps ] + [-IncreaseScoreWithRedirectToOtherPort ] + [-InlineSafetyTipsEnabled ] + [-IntraOrgFilterState ] + [-LanguageBlockList ] + [-MakeDefault] + [-MarkAsSpamBulkMail ] + [-MarkAsSpamEmbedTagsInHtml ] + [-MarkAsSpamEmptyMessages ] + [-MarkAsSpamFormTagsInHtml ] + [-MarkAsSpamFramesInHtml ] + [-MarkAsSpamFromAddressAuthFail ] + [-MarkAsSpamJavaScriptInHtml ] + [-MarkAsSpamNdrBackscatter ] + [-MarkAsSpamObjectTagsInHtml ] + [-MarkAsSpamSensitiveWordList ] + [-MarkAsSpamSpfRecordHardFail ] + [-MarkAsSpamWebBugsInHtml ] + [-ModifySubjectValue ] + [-PhishQuarantineTag ] + [-PhishSpamAction ] + [-PhishZapEnabled ] + [-QuarantineRetentionPeriod ] + [-RedirectToRecipients ] + [-RegionBlockList ] + [-SpamAction ] + [-SpamQuarantineTag ] + [-SpamZapEnabled ] + [-TestModeAction ] + [-TestModeBccToRecipients ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits). + +## EXAMPLES + +### Example 1 +```powershell +Set-HostedContentFilterPolicy -Identity "Contoso Executives" -HighConfidenceSpamAction Quarantine -SpamAction Quarantine -BulkThreshold 6 +``` + +This example modifies the spam filter policy named Contoso Executives with the following settings: + +- Quarantine messages when the spam filtering verdict is spam or high confidence spam. +- BCL 6 triggers the action for a bulk email spam filtering verdict. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: HostedContentFilterPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AddXHeaderValue +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 +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +The maximum length is 255 characters, and the value can't contain spaces or colons (:). + +For example, if you enter the value `This-is-my-custom-header`, the X-header that's added to the message is `This-is-my-custom-header: This message appears to be spam.` + +If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`). + +Note that this setting is independent of the AddXHeader value of the TestModeAction parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedSenderDomains +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedSenders +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedSenderDomains +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedSenders +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). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BulkQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined as bulk as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BulkSpamAction +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. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- NoAction +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BulkThreshold +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). + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DownloadLink +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableEndUserSpamNotifications +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableLanguageBlockList +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. +- $false: Don't mark messages as spam solely based on their languages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableRegionBlockList +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. +- $false: Don't mark messages as spam solely based on the source country or region. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomFromAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomFromName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomSubject +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationFrequency +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationLanguage +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationLimit +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidencePhishAction +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. +- Quarantine: Move the message to quarantine. By default, messages that are quarantined as high confidence phishing are available only to admins. Or, you can use the HighConfidencePhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. + +```yaml +Type: PhishFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidencePhishQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named AdminOnlyAccessPolicy. This quarantine policy enforces the historical capabilities for messages that were quarantined as high confidence phishing as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidenceSpamAction +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). +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as high confidence spam are available to the intended recipients and admins. Or, you can use the HighConfidenceSpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidenceSpamQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined as high confidence spam as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithBizOrInfoUrls +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. +- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting will be marked as spam. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithImageLinks +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. +- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting will be marked as spam. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithNumericIps +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. +- On: The setting is enabled. Messages that contain links to IP addresses are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncreaseScoreWithRedirectToOtherPort +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. +- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InlineSafetyTipsEnabled +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. +- $false: Safety tips are disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IntraOrgFilterState +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. +- HighConfidencePhish +- Phish: Includes phishing and high confidence phishing. +- HighConfidenceSpam: Includes high confidence spam, phishing, and high confidence phishing. +- Spam: Includes spam, high confidence spam, phishing, and high confidence phishing. +- Disabled + +```yaml +Type: IntraOrgFilterState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LanguageBlockList +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. + +A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Not all possible language codes are available as input for this parameter. + +To enter multiple values and overwrite any existing entries, use the following syntax: `"Value1","Value2",..."ValueN"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +To empty the list, use the value $null. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeDefault +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). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamBulkMail +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. +- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. +- Test: This value is available, but isn't used for this parameter. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamEmbedTagsInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamEmptyMessages +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. +- On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamFormTagsInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamFramesInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ or \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamFromAddressAuthFail +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. +- On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamJavaScriptInHtml +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. +- On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamNdrBackscatter +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. +- On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamObjectTagsInHtml +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. +- On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamSensitiveWordList +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. +- On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamSpfRecordHardFail +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. +- On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MarkAsSpamWebBugsInHtml +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. +- On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message. +- Test: The action specified by the TestModeAction parameter is taken on the message. + +```yaml +Type: SpamFilteringOption +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModifySubjectValue +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 +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined as phishing as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishSpamAction +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. +- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishZapEnabled +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. +- $false: ZAP for phishing messages is disabled. + +You configure ZAP for spam with the SpamZapEnabled parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineRetentionPeriod +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 +- HighConfidencePhishAction +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +A valid value is an integer between 1 and 30. + +After the time period expires, the message is deleted. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RedirectToRecipients +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 +- HighConfidenceSpamAction +- PhishSpamAction +- SpamAction + +You can specify multiple email addresses separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RegionBlockList +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. + +A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). + +To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +To empty the list, use the value $null. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamAction +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). +- Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. +- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). +- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. +- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. + +```yaml +Type: SpamFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named DefaultFullAccessPolicy (no notifications) or NotificationEnabledPolicy (if available in your organization). This quarantine policy enforces the historical capabilities for messages that were quarantined as spam as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamZapEnabled +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. +- $false: ZAP for spam is disabled. + +You configure ZAP for phishing messages with the PhishZapEnabled parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TestModeAction +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. +- AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. +- BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter. + +```yaml +Type: SpamFilteringTestModeAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TestModeBccToRecipients +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. + +This parameter is meaningful only when the value of the TestModeAction parameter is BccMessage, and when the value of one or more IncreaseScoreWith\* or MarkAsSpam\* parameters is Test. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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 + +[Safe sender and blocked sender lists in Exchange Online](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365) diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Set-HostedContentFilterRule.md similarity index 79% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterRule.md rename to exchange/exchange-ps/exchange/Set-HostedContentFilterRule.md index a7f2f5870b..991cf73ca1 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterRule.md +++ b/exchange/exchange-ps/exchange/Set-HostedContentFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-hostedcontentfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Set-HostedContentFilterRule @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Set-HostedContentFilterRule cmdlet to modify spam filter rules (content filter rules) in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -37,11 +33,15 @@ Set-HostedContentFilterRule [-Identity] [-RecipientDomainIs ] [-SentTo ] [-SentToMemberOf ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Use the Microsoft Defender portal to create anti-spam policies](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure#use-the-microsoft-defender-portal-to-create-anti-spam-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,9 +58,7 @@ This example adds an exception to the spam filter rule named Contoso Recipients 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 - - Distinguished name (DN) - - GUID ```yaml @@ -95,8 +93,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -113,7 +110,7 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception for the rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -132,18 +129,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -159,21 +151,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf -The ExceptIfSentToMemberOf parameter specifies an exception for the rule that looks for messages sent to members of groups. You can use any value that uniquely identifies the group. For example: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. @@ -213,7 +200,7 @@ Accept wildcard characters: False ### -Name 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: \\, %, &, \*, +, /, =, ?, {, }, \|, \<, \>, (, ), ;, :, [, ], comma (,), or double quotation mark ("). +Don't use the following characters in the name value: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. ```yaml Type: String @@ -234,9 +221,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a 9th new rule are from 0 through 8. - - The default value for the new 9th rule is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -255,7 +240,7 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition for the rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -274,18 +259,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -301,21 +281,16 @@ Accept wildcard characters: False ``` ### -SentToMemberOf -The SentToMemberOf parameter specifies a condition for the rule 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: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. @@ -353,12 +328,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterPolicy.md similarity index 80% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterPolicy.md rename to exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterPolicy.md index 74d9e66ea8..5a570aaa15 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-hostedoutboundspamfilterpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Set-HostedOutboundSpamFilterPolicy @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Set-HostedOutboundSpamFilterPolicy cmdlet to modify outbound spam filter policies in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,6 +24,7 @@ For information about the parameter sets in the Syntax section below, see [Excha Set-HostedOutboundSpamFilterPolicy [-Identity] [-ActionWhenThresholdReached ] [-AdminDisplayName ] + [-AutoForwardingMode ] [-BccSuspiciousOutboundAdditionalRecipients ] [-BccSuspiciousOutboundMail ] [-Confirm] @@ -36,11 +33,12 @@ Set-HostedOutboundSpamFilterPolicy [-Identity] ] [-RecipientLimitInternalPerHour ] [-RecipientLimitPerDay ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,7 +50,6 @@ Set-HostedOutboundSpamFilterPolicy -Identity Default -RecipientLimitExternalPerH This example configures the following settings in the outbound spam filter policy named Default: - The recipient rate limits are restricted to smaller values that the service defaults. - - After one of the limits is reached, the user is prevented from sending messages (added to the Restricted Users portal). ## PARAMETERS @@ -61,9 +58,7 @@ This example configures the following settings in the outbound spam filter polic 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 - - Distinguished name (DN) - - GUID ```yaml @@ -83,9 +78,7 @@ Accept wildcard characters: False 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. - - BlockUser: Prevent the user from sending email messages. - - BlockUserForToday: Prevent the user from sending email messages until the following day. This is the default value. ```yaml @@ -118,6 +111,29 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AutoForwardingMode +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). +- On: Automatic external email forwarding isn't disabled by the policy. +- Off: Automatic external email forwarding is disabled by the policy and results in a non-delivery report (also known as an NDR or bounce message) to the sender. + +This setting applies to cloud-based mailboxes only. Automatic forwarding to internal recipients isn't affected by this setting. + +```yaml +Type: AutoForwardingMode +Parameter Sets: (All) +Aliases: +Accepted values: Automatic, Off, On +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -BccSuspiciousOutboundAdditionalRecipients 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. @@ -140,7 +156,6 @@ Accept wildcard characters: False 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. - - $false: No additional messages are added to outgoing spam messages. This is the default value. ```yaml @@ -159,8 +174,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -177,12 +191,11 @@ Accept wildcard characters: False ``` ### -NotifyOutboundSpam -**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://docs.microsoft.com/microsoft-365/security/office-365-security/removing-user-from-restricted-users-portal-after-spam#verify-the-alert-settings-for-restricted-users). +**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: - $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter. - - $false: Don't send notifications. This is the default value. ```yaml @@ -199,7 +212,7 @@ Accept wildcard characters: False ``` ### -NotifyOutboundSpamRecipients -**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://docs.microsoft.com/microsoft-365/security/office-365-security/removing-user-from-restricted-users-portal-after-spam#verify-the-alert-settings-for-restricted-users). +**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. @@ -219,7 +232,7 @@ Accept wildcard characters: False ``` ### -RecipientLimitExternalPerHour -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 Office 365 options](https://docs.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-across-office-365-options). +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 @@ -235,7 +248,7 @@ Accept wildcard characters: False ``` ### -RecipientLimitInternalPerHour -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 Office 365 options](https://docs.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-across-office-365-options). +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 @@ -251,7 +264,7 @@ Accept wildcard characters: False ``` ### -RecipientLimitPerDay -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 Office 365 options](https://docs.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-across-office-365-options). +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 @@ -287,12 +300,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterRule.md similarity index 83% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterRule.md index a259f4ac0b..fd8d912dd6 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-hostedoutboundspamfilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Set-HostedOutboundSpamFilterRule @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Set-HostedOutboundSpamFilterRule cmdlet to modify the settings of outbound spam filter rules in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -37,11 +33,12 @@ Set-HostedOutboundSpamFilterRule [-Identity] [-Name ] [-Priority ] [-SenderDomainIs ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -58,9 +55,7 @@ This example adds an exception to the existing rule named Contoso Executives. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -95,8 +90,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -116,18 +110,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -146,18 +135,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -192,18 +176,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -222,18 +201,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -254,9 +228,7 @@ The HostedOutboundSpamFilterPolicy parameter specifies the outbound spam filter You can use any value that uniquely identifies the policy. For example: - Name - - Distinguished name (DN) - - GUID. You can't specify the default outbound spam filter policy, and you can't specify an outbound spam filter policy that's already associated with another outbound spam filter rule. @@ -277,7 +249,7 @@ Accept wildcard characters: False ### -Name 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 ("). -The value itself can't contain the following characters: \\, %, &, \*, +, /, =, ?, {, }, \|, \<, \>, (, ), ;, :, [, ], comma (,), or double quotation mark ("). +Don't use the following characters: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. ```yaml Type: String @@ -298,9 +270,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a new rule (the 9th rule) are from 0 through 8. - - The default value for a new rule (the 9th rule) is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -355,12 +325,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-HybridConfiguration.md b/exchange/exchange-ps/exchange/Set-HybridConfiguration.md similarity index 78% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Set-HybridConfiguration.md rename to exchange/exchange-ps/exchange/Set-HybridConfiguration.md index e48c850467..5811e49d7f 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-HybridConfiguration.md +++ b/exchange/exchange-ps/exchange/Set-HybridConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-hybridconfiguration +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-HybridConfiguration @@ -15,26 +14,37 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Set-HybridConfiguration cmdlet to modify the hybrid deployment between your on-premises Exchange organization and Exchange Online in a Microsoft Office 365 for enterprises organization. +Use the Set-HybridConfiguration cmdlet to modify the hybrid deployment between your on-premises Exchange organization and Exchange Online in a Microsoft 365 for enterprises organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-HybridConfiguration [-ClientAccessServers ] [-Confirm] [-DomainController ] - [-Domains ] [-ExternalIPAddresses ] - [-Features ] [-Name ] [-OnPremisesSmartHost ] - [-SecureMailCertificateThumbprint ] [-TransportServers ] [-WhatIf] - [-EdgeTransportServers ] [-ReceivingTransportServers ] - [-SendingTransportServers ] [-ServiceInstance ] - [-TlsCertificateName ] [] +Set-HybridConfiguration + [-ClientAccessServers ] + [-Confirm] + [-DomainController ] + [-Domains ] + [-EdgeTransportServers ] + [-ExternalIPAddresses ] + [-Features ] + [-Name ] + [-OnPremisesSmartHost ] + [-ReceivingTransportServers ] + [-SecureMailCertificateThumbprint ] + [-SendingTransportServers ] + [-ServiceInstance ] + [-TlsCertificateName ] + [-TransportServers ] + [-WhatIf] + [] ``` ## DESCRIPTION The Set-HybridConfiguration cmdlet modifies the hybrid configuration features, such as enabling secure mail, designating a specific Mailbox server for hybrid functionality, or enabling or disabling free/busy information sharing and message tracking between the on-premises Exchange and Exchange Online organizations. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,14 +72,12 @@ This example specifies that the hybrid deployment uses a defined TLS certificate ## PARAMETERS ### -ClientAccessServers -This parameter is available or functional only in Exchange Server 2010. +This parameter is functional only in Exchange Server 2010. -The ClientAccessServers parameter specifies the Exchange Server 2010 SP2 servers with the Client Access server role installed that will be configured to support the hybrid deployment features. At least one Client Access server must be defined and be externally accessible from the Internet on ports 80 and 443. The servers will be configured to enable the following: +The ClientAccessServers parameter specifies the Exchange 2010 SP2 or later servers with the Client Access server role installed that will be configured to support the hybrid deployment features. At least one Client Access server must be defined and be externally accessible from the Internet on ports 80 and 443. The servers will be configured to enable the following: - Mailbox Replication Service (MRS) Proxy The MRS Proxy service configuration on the Client Access servers will be enabled. - - Virtual Directories The Client Access servers will host the default Web sites for the Exchange Web Services (EWS), offline address books, and ActiveSync services. - - Outlook Anywhere The Client Access servers will have Outlook Anywhere enabled. ```yaml @@ -88,8 +96,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -157,19 +164,12 @@ Accept wildcard characters: False The Features parameter specifies the features enabled for the hybrid configuration. One or more of the following values separated by commas can be entered. When using the Hybrid Configuration wizard, all features are enabled by default. - Centralized: Enables transport servers to handle all message transport between the on-premises Exchange and Exchange Online organizations, including external message delivery to the Internet for both organizations. If this value is $false, the on-premises transport servers and Exchange Online organization are each responsible for their own Internet message delivery. - - FreeBusy: Enables free/busy calendar information to be shared between on-premises Exchange and Exchange Online organization users. - - MailTips: Enables MailTips information to be shared between on-premises Exchange and Exchange Online organization users. - - MessageTracking: Enables message tracking information to be shared between on-premises Exchange and Exchange Online organization users. - - OnlineArchive: Enables the Exchange Online archive feature so that Exchange Online supports hosting archive mailboxes for on-premises users. - - OWARedirection: Enables automatic Microsoft Outlook on the web redirection to either the on-premises Exchange or Exchange Online organizations depending on where the user mailbox is located. - - SecureMail: Enables secure message transport via Transport Layer Security (TLS) between the on-premises Exchange and Exchange Online organizations. - - Photos: Enables the sharing of user photo data between the on-premises Exchange and Exchange Online organizations. This feature works in tandem with the PhotosEnabled parameter in the OrganizationRelationship cmdlets in a hybrid deployment. If the Photos parameter is $true, the PhotosEnabled parameter is automatically set to $true. If the Photos parameter is $false, the PhotosEnabled parameter is automatically set to $false. When running the Hybrid Configuration wizard for the first time, the default value is $true. ```yaml @@ -219,16 +219,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -SecureMailCertificateThumbprint -This parameter is available or functional only in Exchange Server 2010. +### -ReceivingTransportServers +The ReceivingTransportServers parameter specifies the Mailbox servers that are defined in the outbound connector configuration of the Microsoft Exchange Online Protection (EOP) service included as part of the Microsoft 365 tenant. The servers defined in the ReceivingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the Exchange Online organization to the on-premises Exchange organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the ReceivingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. -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. +If configuring the EdgeTransportServers parameter in the hybrid deployment, the ReceivingTransportServers parameter value must be $null. ```yaml -Type: String +Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -237,13 +237,13 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -TransportServers -This parameter is available or functional only in Exchange Server 2010. +### -SecureMailCertificateThumbprint +This parameter is available only in Exchange Server 2010. -The TransportServers parameter specifies the Exchange Server 2010 SP2 servers with the Hub Transport server role installed that will be configured to support the hybrid deployment features. At least one Hub Transport server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises and cloud-based organizations. +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. ```yaml -Type: MultiValuedProperty +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 @@ -255,29 +255,29 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -SendingTransportServers +The SendingTransportServers parameter specifies the Mailbox servers that are defined in the inbound connector configuration of the EOP service included as part of the Microsoft 365 tenant. The servers defined in the SendingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the on-premise organization to the Exchange Online organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the SendingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. + +If configuring the EdgeTransportServers parameter in the hybrid deployment, the SendingTransportServers parameter value must be $null. ```yaml -Type: SwitchParameter +Type: MultiValuedProperty Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -EdgeTransportServers -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. +### -ServiceInstance +The ServiceInstance parameter should only be used by organizations manually configuring hybrid deployments with Office 365 operated by 21Vianet in China. All other organizations should use the Hybrid Configuration wizard to configure a hybrid deployment with Microsoft 365. The valid values for this parameter are 0 (null) or 1. The default value is 0 (null). For organizations connecting with Office 365 operated by 21Vianet in China, set this value to 1 when manually configuring your hybrid deployment. ```yaml -Type: MultiValuedProperty +Type: Int32 Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -289,13 +289,11 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -ReceivingTransportServers -The ReceivingTransportServers parameter specifies the Mailbox servers that are defined in the outbound connector configuration of the Microsoft Exchange Online Protection (EOP) service included as part of the Office 365 for enterprises tenant. The servers defined in the ReceivingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the Exchange Online organization to the on-premises Exchange organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the ReceivingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. - -If configuring the EdgeTransportServers parameter in the hybrid deployment, the ReceivingTransportServers parameter value must be $null. +### -TlsCertificateName +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: MultiValuedProperty +Type: SmtpX509Identifier Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -307,16 +305,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -SendingTransportServers -The SendingTransportServers parameter specifies the Mailbox servers that are defined in the inbound connector configuration of the EOP service included as part of the Office 365 for enterprises tenant. The servers defined in the SendingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the on-premise organization to the Exchange Online organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the SendingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either mbx.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. +### -TransportServers +This parameter is available only in Exchange Server 2010. -If configuring the EdgeTransportServers parameter in the hybrid deployment, the SendingTransportServers parameter value must be $null. +The TransportServers parameter specifies the Exchange Server 2010 SP2 servers with the Hub Transport server role installed that will be configured to support the hybrid deployment features. At least one Hub Transport server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises and cloud-based organizations. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010 Required: False Position: Named @@ -325,27 +323,29 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -ServiceInstance -The ServiceInstance parameter should only be used by organizations manually configuring hybrid deployments with Office 365 operated by 21Vianet in China. All other organizations should use the Hybrid Configuration wizard to configure a hybrid deployment with Office 365. The valid values for this parameter are 0 (null) or 1. The default value is 0 (null). For organizations connecting with Office 365 operated by 21Vianet in China, set this value to 1 when manually configuring your hybrid deployment. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: Int32 +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` -### -TlsCertificateName -The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\X.500Issuer\X.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. +### -EdgeTransportServers +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. ```yaml -Type: SmtpX509Identifier +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -362,12 +362,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListConfig.md b/exchange/exchange-ps/exchange/Set-IPAllowListConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListConfig.md rename to exchange/exchange-ps/exchange/Set-IPAllowListConfig.md index 65f4506c8e..0c7a6349a0 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListConfig.md +++ b/exchange/exchange-ps/exchange/Set-IPAllowListConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-ipallowlistconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-IPAllowListConfig @@ -17,13 +16,18 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-IPAllowListConfig cmdlet to modify the IP Allow list configuration that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-IPAllowListConfig [-Confirm] [-DomainController ] [-Enabled ] - [-ExternalMailEnabled ] [-InternalMailEnabled ] [-WhatIf] [] +Set-IPAllowListConfig [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExternalMailEnabled ] + [-InternalMailEnabled ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -45,8 +49,7 @@ This example configures connection filtering to use the IP Allow list on message ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -149,12 +152,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListProvider.md b/exchange/exchange-ps/exchange/Set-IPAllowListProvider.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListProvider.md rename to exchange/exchange-ps/exchange/Set-IPAllowListProvider.md index 36f0de038e..4ede592a05 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListProvider.md +++ b/exchange/exchange-ps/exchange/Set-IPAllowListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-ipallowlistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-IPAllowListProvider @@ -17,15 +16,23 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-IPAllowListProvider cmdlet to modify IP Allow list providers that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-IPAllowListProvider [-Identity] [-AnyMatch ] - [-BitmaskMatch ] [-Confirm] [-DomainController ] [-Enabled ] - [-IPAddressesMatch ] [-LookupDomain ] [-Name ] [-Priority ] - [-WhatIf] [] +Set-IPAllowListProvider [-Identity] + [-AnyMatch ] + [-BitmaskMatch ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-IPAddressesMatch ] + [-LookupDomain ] + [-Name ] + [-Priority ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -53,9 +60,7 @@ This example sets the priority to 1 for the existing IP Allow list provider name 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 - - Distinguished name (DN) - - GUID ```yaml @@ -106,8 +111,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -160,9 +164,9 @@ Accept wildcard characters: False ### -IPAddressesMatch 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -248,12 +252,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListProvidersConfig.md b/exchange/exchange-ps/exchange/Set-IPAllowListProvidersConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListProvidersConfig.md rename to exchange/exchange-ps/exchange/Set-IPAllowListProvidersConfig.md index 9130b0bd0b..214711a0f1 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPAllowListProvidersConfig.md +++ b/exchange/exchange-ps/exchange/Set-IPAllowListProvidersConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-ipallowlistprovidersconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-IPAllowListProvidersConfig @@ -17,13 +16,18 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-IPAllowListProvidersConfig cmdlet to modify the settings that affect all IP Allow list providers that are configured on an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-IPAllowListProvidersConfig [-Confirm] [-DomainController ] [-Enabled ] - [-ExternalMailEnabled ] [-InternalMailEnabled ] [-WhatIf] [] +Set-IPAllowListProvidersConfig [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExternalMailEnabled ] + [-InternalMailEnabled ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -45,8 +49,7 @@ This example configures connection filtering to use IP Allow list providers on m ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -149,12 +152,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListConfig.md b/exchange/exchange-ps/exchange/Set-IPBlockListConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListConfig.md rename to exchange/exchange-ps/exchange/Set-IPBlockListConfig.md index a4f396c1ff..af8ccda55d 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListConfig.md +++ b/exchange/exchange-ps/exchange/Set-IPBlockListConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-ipblocklistconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-IPBlockListConfig @@ -17,14 +16,19 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-IPBlockListConfig cmdlet to modify the IP Block list configuration that's used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-IPBlockListConfig [-Confirm] [-DomainController ] [-Enabled ] - [-ExternalMailEnabled ] [-InternalMailEnabled ] - [-MachineEntryRejectionResponse ] [-StaticEntryRejectionResponse ] [-WhatIf] +Set-IPBlockListConfig [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExternalMailEnabled ] + [-InternalMailEnabled ] + [-MachineEntryRejectionResponse ] + [-StaticEntryRejectionResponse ] + [-WhatIf] [] ``` @@ -47,8 +51,7 @@ This example configures connection filtering to use the IP Block list on message ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -183,12 +186,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListProvider.md b/exchange/exchange-ps/exchange/Set-IPBlockListProvider.md similarity index 90% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListProvider.md rename to exchange/exchange-ps/exchange/Set-IPBlockListProvider.md index 9e6bf171a3..f7394da090 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListProvider.md +++ b/exchange/exchange-ps/exchange/Set-IPBlockListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-ipblocklistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-IPBlockListProvider @@ -17,15 +16,24 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-IPBlockListProvider cmdlet to modify IP Block list providers that are used by the Connection Filtering agent on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-IPBlockListProvider [-Identity] [-AnyMatch ] - [-BitmaskMatch ] [-Confirm] [-DomainController ] [-Enabled ] - [-IPAddressesMatch ] [-LookupDomain ] [-Name ] [-Priority ] - [-RejectionResponse ] [-WhatIf] [] +Set-IPBlockListProvider [-Identity] + [-AnyMatch ] + [-BitmaskMatch ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-IPAddressesMatch ] + [-LookupDomain ] + [-Name ] + [-Priority ] + [-RejectionResponse ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -53,9 +61,7 @@ This example sets the priority value to 1 for the IP Block list provider named C 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 - - Distinguished name (DN) - - GUID ```yaml @@ -106,8 +112,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -160,9 +165,9 @@ Accept wildcard characters: False ### -IPAddressesMatch 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -266,12 +271,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListProvidersConfig.md b/exchange/exchange-ps/exchange/Set-IPBlockListProvidersConfig.md similarity index 89% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListProvidersConfig.md rename to exchange/exchange-ps/exchange/Set-IPBlockListProvidersConfig.md index 4a76367dd6..50419ac6d6 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-IPBlockListProvidersConfig.md +++ b/exchange/exchange-ps/exchange/Set-IPBlockListProvidersConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-ipblocklistprovidersconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-IPBlockListProvidersConfig @@ -17,14 +16,19 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Set-IPBlockListProvidersConfig cmdlet to modify the settings that affect all IP Block list providers that are configured on an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-IPBlockListProvidersConfig [-BypassedRecipients ] [-Confirm] - [-DomainController ] [-Enabled ] [-ExternalMailEnabled ] - [-InternalMailEnabled ] [-WhatIf] [] +Set-IPBlockListProvidersConfig [-BypassedRecipients ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExternalMailEnabled ] + [-InternalMailEnabled ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -49,7 +53,6 @@ Set-IPBlockListProvidersConfig -BypassedRecipients @{Add="chris@contoso.com","mi This example makes the following changes to the list of bypassed recipients: - Adds the values chris@contoso.com and michelle@contoso.com - - Removes the values laura@contoso.com and julia@contoso.com ## PARAMETERS @@ -57,9 +60,9 @@ This example makes the following changes to the list of bypassed recipients: ### -BypassedRecipients 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -77,8 +80,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -181,12 +183,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-IRMConfiguration.md b/exchange/exchange-ps/exchange/Set-IRMConfiguration.md similarity index 78% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Set-IRMConfiguration.md rename to exchange/exchange-ps/exchange/Set-IRMConfiguration.md index bdde58cc60..76f288110e 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-IRMConfiguration.md +++ b/exchange/exchange-ps/exchange/Set-IRMConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/set-irmconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-IRMConfiguration @@ -19,7 +18,7 @@ Use the Set-IRMConfiguration cmdlet to configure Information Rights Management ( Configuring and using IRM features in an on-premises Exchange organization requires Active Directory Rights Management Services (AD RMS). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,25 +32,28 @@ Set-IRMConfiguration [-Identity ] [-DomainController ] [-EDiscoverySuperUserEnabled ] [-EnablePdfEncryption ] + [-EnablePortalTrackingLogs ] [-ExternalLicensingEnabled ] [-Force] [-InternalLicensingEnabled ] [-JournalReportDecryptionEnabled ] [-LicensingLocation ] [-RefreshServerCertificates] + [-RejectIfRecipientHasNoRights ] [-RMSOnlineKeySharingLocation ] [-SearchEnabled ] [-SimplifiedClientAccessDoNotForwardDisabled ] [-SimplifiedClientAccessEnabled ] [-SimplifiedClientAccessEncryptOnlyDisabled ] [-TransportDecryptionSetting ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION IRM requires the use of an on-premises AD RMS server or the ILS service. IRM features can be selectively enabled or disabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,7 +89,7 @@ The Identity parameter specifies the organization's IRM configuration object to Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -101,15 +103,14 @@ 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: -- $true: New Azure Information Protection features announced through Office 365 message center will be enabled automatically in your cloud-based organization. This is the default value. - +- $true: New Azure Information Protection features announced through Microsoft 365 message center will be enabled automatically in your cloud-based organization. - $false: Prevents new Azure Information Protection features from automatically being introduced into your tenant organization. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -123,15 +124,14 @@ 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: -- $true: The Exchange Online organization can connect directly to Azure Rights Management. This enables Office 365 Message Encryption. - +- $true: The Exchange Online organization can connect directly to Azure Rights Management. This enables Microsoft Purview Message Encryption. - $false: The Exchange Online organization can't connect directly to Azure Rights Management. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -145,8 +145,7 @@ 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: -- $true: Client Access servers are allowed to authenticate clients. This is the default value. Note that enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see [Information Rights Management in Outlook Web App](https://docs.microsoft.com/exchange/information-rights-management-in-outlook-web-app-exchange-2013-help). - +- $true: Client Access servers are allowed to authenticate clients. This is the default value. Note that enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see [Information Rights Management in Outlook Web App](https://learn.microsoft.com/exchange/information-rights-management-in-outlook-web-app-exchange-2013-help). - $false: Client Access servers aren't allowed to authenticate clients. ```yaml @@ -165,15 +164,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -185,10 +183,9 @@ Accept wildcard characters: False ### -DecryptAttachmentForEncryptOnly 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 new Office 365 Message Encryption capabilities. Valid values are: +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: - $true: The recipients will have unrestricted rights on attachments sent using Encrypt-Only policy. - - $false: The recipients will not have unrestricted rights on attachments sent using Encrypt-Only policy. This parameter replaces the deprecated DecryptAttachmentFromPortal parameter. @@ -197,7 +194,7 @@ This parameter replaces the deprecated DecryptAttachmentFromPortal parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -228,16 +225,15 @@ Accept wildcard characters: False 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. - - $false: Members of the Discovery Management role group can't access IRM-protected messages in discovery mailboxes. -For more information about In-Place eDiscovery and IRM-protected messages, see [In-Place eDiscovery in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). +For more information about In-Place eDiscovery and IRM-protected messages, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -249,12 +245,34 @@ Accept wildcard characters: False ### -EnablePdfEncryption This parameter is available only in the cloud-based service. -The EnablePdfEncryption parameter specifies whether to enable the encryption of PDF attachments using Office 365 Message Encryption (OME). Valid values are: +The EnablePdfEncryption parameter specifies whether to enable the encryption of PDF attachments using Microsoft Purview Message Encryption. Valid values are: - $true: Messages that contain PDF attachments can be encrypted. - - $false: Messages that contain PDF attachments can't be encrypted. +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnablePortalTrackingLogs +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). + +The EnablePortalTrackingLogs parameter specifies whether to turn on auditing for the Office 365 Message Encryption (OME) portal. Valid values are: + +- $true: Turn on auditing for activities in the OME portal. Activities are visible in the audit logs. +- $false: Turn off auditing for activities in the OME portal. + ```yaml Type: Boolean Parameter Sets: (All) @@ -271,11 +289,12 @@ Accept wildcard characters: False ### -ExternalLicensingEnabled This parameter is available only in on-premises Exchange. -The ExternalLicensingEnabled parameter specifies whether to enable IRM features for messages that are sent to external recipients. Valid values are: +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. -- $true: IRM features are enabled for external messages. +Valid values are: -- $false: IRM features are disabled for external messages. This is the default value. +- $true: Exchange will try to acquire licenses from clusters other than the one it is configured to use. This value can help prevent denial of service (DoS) attacks. +- $false: Exchange will try to acquire licenses only from clusters that it is configured to use. This is the default value. The *LicensingLocation* parameter specifies the list of allowed clusters. ```yaml Type: Boolean @@ -291,13 +310,15 @@ Accept wildcard characters: False ``` ### -Force -The Force switch specifies whether to suppress the confirmation prompt that appears when you modify the InternalLicensingEnabled parameter. You don't need to specify a value with this switch. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -312,14 +333,13 @@ Accept wildcard characters: False The InternalLicensingEnabled parameter specifies whether to enable IRM features for messages that are sent to internal recipients. Valid values are: - $true: IRM features are enabled for internal messages. This is the default value in Exchange Online. - - $false: IRM features are disabled for internal messages. This is the default value in on-premises Exchange. Note that this value causes the Get-RMSTemplate to return no AD RMS templates. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -331,8 +351,7 @@ Accept wildcard characters: False ### -JournalReportDecryptionEnabled 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://docs.microsoft.com/exchange/journal-report-decryption-exchange-2013-help). - +- $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). - $false: Journal report decryption is disabled. ```yaml @@ -353,11 +372,13 @@ The LicensingLocation parameter specifies the RMS licensing URLs. You can specif Typically, in on-premises Exchange, you only need to use this parameter in cross-forest deployments of AD RMS licensing servers. +**IMPORTANT**: If you specify multiple URLs, always specify the Azure RMS URL first. Otherwise, encryption services won't function properly. + ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -371,7 +392,7 @@ 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. -Clearing RACs, CLCs, and cached templates might be required during troubleshooting or after changing keys on the AD RMS cluster in your organization. For more information about RACs and CLCs, see [Understanding AD RMS Certificates](https://go.microsoft.com/fwlink/p/?linkId=197118). +Clearing RACs, CLCs, and cached templates might be required during troubleshooting or after changing keys on the AD RMS cluster in your organization. For more information about RACs and CLCs, see [Understanding AD RMS Certificates](https://learn.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753886(v=ws.11)). ```yaml Type: SwitchParameter @@ -386,6 +407,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RejectIfRecipientHasNoRights +This parameter is available only in the cloud-based service. + +{{ Fill RejectIfRecipientHasNoRights Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RMSOnlineKeySharingLocation This parameter is available only in the cloud-based service. @@ -395,7 +434,7 @@ The RMSOnlineKeySharingLocation parameter specifies the Azure Rights Management Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -408,14 +447,13 @@ Accept wildcard characters: False 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. - - $false: Searching IRM-encrypted messages in Outlook on the web is disabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -430,14 +468,13 @@ 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: - $true: **Do not forward** is not available in Outlook on the web. - - $false: **Do not forward** is available in Outlook on the web. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -452,14 +489,13 @@ 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: - $true: The Protect button is enabled in Outlook on the web. - - $false: The Protect button is disabled in Outlook on the web. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -474,14 +510,13 @@ 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: - $true: **Encrypt only** is not available in Outlook on the web. - - $false: **Encrypt only** is available in Outlook on the web. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -494,16 +529,14 @@ Accept wildcard characters: False The TransportDecryptionSetting parameter specifies the transport decryption configuration. Valid values are: - Disabled: Transport decryption is disabled for internal and external messages. - - Mandatory: Messages that can't be decrypted are rejected with a non-delivery report (also known as an NDR or bounce message). - - Optional: Messages are decrypted if possible, but are delivered even if decryption fails. This is the default value. ```yaml Type: TransportDecryptionSetting Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -519,7 +552,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -533,12 +566,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Set-ImapSettings.md b/exchange/exchange-ps/exchange/Set-ImapSettings.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access/Set-ImapSettings.md rename to exchange/exchange-ps/exchange/Set-ImapSettings.md index 887be7b9b3..d6a70cad13 100644 --- a/exchange/exchange-ps/exchange/client-access/Set-ImapSettings.md +++ b/exchange/exchange-ps/exchange/Set-ImapSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-imapsettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ImapSettings @@ -17,33 +16,49 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ImapSettings cmdlet to modify the settings of the Microsoft Exchange IMAP4 service on Exchange servers. This service exists on Exchange servers that have the Client Access server role installed, and is used by IMAP4 clients to connect to Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ImapSettings [-AuthenticatedConnectionTimeout ] [-Banner ] - [-CalendarItemRetrievalOption ] [-Confirm] - [-DomainController ] [-EnableExactRFC822Size ] - [-EnableGSSAPIAndNTLMAuth ] [-EnforceCertificateErrors ] - [-ExtendedProtectionPolicy ] [-ExternalConnectionSettings ] - [-InternalConnectionSettings ] [-LogFileLocation ] +Set-ImapSettings [-AuthenticatedConnectionTimeout ] + [-Banner ] + [-CalendarItemRetrievalOption ] + [-Confirm] + [-DomainController ] + [-EnableExactRFC822Size ] + [-EnableGSSAPIAndNTLMAuth ] + [-EnforceCertificateErrors ] + [-ExtendedProtectionPolicy ] + [-ExternalConnectionSettings ] + [-InternalConnectionSettings ] + [-LogFileLocation ] [-LogFileRollOverSettings ] - [-LoginType ] [-LogPerFileSizeQuota ] - [-MaxCommandSize ] [-MaxConnectionFromSingleIP ] [-MaxConnections ] + [-LoginType ] + [-LogPerFileSizeQuota ] + [-MaxCommandSize ] + [-MaxConnectionFromSingleIP ] + [-MaxConnections ] [-MaxConnectionsPerUser ] [-MessageRetrievalMimeFormat ] - [-OwaServerUrl ] [-PreAuthenticatedConnectionTimeout ] - [-ProtocolLogEnabled ] [-ProxyTargetPort ] [-Server ] - [-ShowHiddenFoldersEnabled ] [-SSLBindings ] - [-SuppressReadReceipt ] [-UnencryptedOrTLSBindings ] [-WhatIf] - [-X509CertificateName ] [] + [-OwaServerUrl ] + [-PreAuthenticatedConnectionTimeout ] + [-ProtocolLogEnabled ] + [-ProxyTargetPort ] + [-Server ] + [-ShowHiddenFoldersEnabled ] + [-SSLBindings ] + [-SuppressReadReceipt ] + [-UnencryptedOrTLSBindings ] + [-WhatIf] + [-X509CertificateName ] + [] ``` ## DESCRIPTION You can run the Set-ImapSettings cmdlet for a single Exchange server that's running the Microsoft Exchange IMAP4 service, or for all Exchange servers that are running the Microsoft Exchange IMAP4 service. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -126,11 +141,8 @@ Accept wildcard characters: False The CalendarItemRetrievalOption parameter specifies how calendar items are presented to IMAP4 clients. Valid values are: - 0 or iCalendar. This is the default value. - - 1 or IntranetUrl - - 2 or InternetUrl - - 3 or Custom If you specify 3 or Custom, you need to specify a value for the OwaServerUrl parameter setting. @@ -151,8 +163,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -188,7 +199,6 @@ Accept wildcard characters: False 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. - - $false: Use an estimated message size. This is the default value. ```yaml @@ -208,7 +218,6 @@ Accept wildcard characters: False 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. - - $false: NTLM for IMAP4 connections is disabled. ```yaml @@ -230,7 +239,6 @@ The EnforceCertificateErrors parameter specifies whether to enforce valid Secure The default setting is $false. - $true: If the certificate isn't valid or doesn't match the target IMAP4 server's FQDN, the connection attempt fails. - - $false: The server doesn't deny IMAP4 connections based on certificate errors. This is the default value. ```yaml @@ -250,9 +258,7 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used only if it's supported by the incoming IMAP4 connection. If it's not, Extended Protection for Authentication isn't used. - - Require: Extended Protection for Authentication is required for all IMAP4 connections. If the incoming IMAP4 connection doesn't support it, the connection is rejected. Extended Protection for Authentication enhances the protection and handling of credentials by Integrated Windows authentication (also known as NTLM), so we strongly recommend that you use it if it's supported by your clients (default installations of Windows 7 or later and Windows Server 2008 R2 or later support it). @@ -273,13 +279,13 @@ Accept wildcard characters: False ### -ExternalConnectionSettings 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 \:\:[\]. The encryption method value is optional (blank indicates unencrypted connections). +This parameter uses the syntax `HostName:Port:[]`. The encryption method value is optional (blank indicates unencrypted connections). The default value is blank ($null), which means no external IMAP4 connection settings are configured. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The combination of encryption methods and ports that are specified for this parameter need to match the corresponding encryption methods and ports that are specified by the SSLBindings and UnencryptedOrTLSBindings parameters. @@ -299,13 +305,13 @@ Accept wildcard characters: False ### -InternalConnectionSettings 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 \:\:[\]. The encryption method value is optional (blank indicates unencrypted connections). +This parameter uses the syntax `HostName:Port:[]`. The encryption method value is optional (blank indicates unencrypted connections). -The default value is \:993:SSL,\:143:TLS. +The default value is `:993:SSL,:143:TLS`. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The combination of encryption methods and ports that are specified for this parameter need to match the corresponding encryption methods and ports that are specified by the SSLBindings and UnencryptedOrTLSBindings parameters. @@ -343,12 +349,9 @@ Accept wildcard characters: False ### -LogFileRollOverSettings The LogFileRollOverSettings parameter specifies how frequently IMAP4 protocol logging creates a new log file. Valid values are: -- 1 or Hourly. - -- 2 or Daily. This is the default value - +- 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016. +- 2 or Daily. This is the default value in Exchange 2013 and Exchange 2010. - 3 or Weekly. - - 4 or Monthly. This parameter is only meaningful when the LogPerFileSizeQuota parameter value is 0, and the ProtocolLogEnabled parameter value is $true. @@ -370,9 +373,7 @@ Accept wildcard characters: False The LoginType parameter specifies the authentication method for IMAP4 connections. Valid values are: - 1 or PlainTextLogin. - - 2 or PlainTextAuthentication. - - 3 or SecureLogin. This is the default value. ```yaml @@ -394,13 +395,9 @@ The LogPerFileSizeQuota parameter specifies the maximum size of a IMAP4 protocol When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -490,17 +487,11 @@ Accept wildcard characters: False The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages. Valid values are: - 0 or TextOnly. - - 1 or HtmlOnly. - - 2 or HtmlAndTextAlternative. - - 3 or TextEnrichedOnly. - - 4 or TextEnrichedAndTextAlternative. - - 5 or BestBodyFormat. This is the default value. - - 6 or Tnef. ```yaml @@ -556,7 +547,6 @@ Accept wildcard characters: False The ProtocolLogEnabled parameter specifies whether to enable protocol logging for IMAP4. Valid values are: - $true: IMAP4 protocol logging is enabled. - - $false: IMAP4 protocol logging is disabled. This is the default value. ```yaml @@ -592,11 +582,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -618,7 +605,6 @@ Accept wildcard characters: False The ShowHiddenFoldersEnabled parameter specifies whether hidden mailbox folders are visible. Valid values are: - $true: Hidden folders are visible. - - $false: Hidden folders aren't visible. This is the default value. ```yaml @@ -635,13 +621,13 @@ Accept wildcard characters: False ``` ### -SSLBindings -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 \:\. +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. +The default value is `[::]:993,0.0.0.0:993`. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -660,7 +646,6 @@ Accept wildcard characters: False 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. - - $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This is the default value. ```yaml @@ -677,13 +662,13 @@ Accept wildcard characters: False ``` ### -UnencryptedOrTLSBindings -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 \:\. +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. +The default value is `[::]:143,0.0.0.0:143`. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -741,12 +726,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-InboundConnector.md b/exchange/exchange-ps/exchange/Set-InboundConnector.md new file mode 100644 index 0000000000..285ba184d1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-InboundConnector.md @@ -0,0 +1,544 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-InboundConnector + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-InboundConnector cmdlet to change an existing Inbound connector in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-InboundConnector [-Identity] + [-AssociatedAcceptedDomains ] + [-CloudServicesMailEnabled ] + [-Comment ] + [-Confirm] + [-ConnectorSource ] + [-ConnectorType ] + [-EFSkipIPs ] + [-EFSkipLastIP ] + [-EFSkipMailGateway ] + [-EFTestMode ] + [-EFUsers ] + [-Enabled ] + [-Name ] + [-RequireTls ] + [-RestrictDomainsToCertificate ] + [-RestrictDomainsToIPAddresses ] + [-ScanAndDropRecipients ] + [-SenderDomains ] + [-SenderIPAddresses ] + [-TlsSenderCertificateName ] + [-TreatMessagesAsInternal ] + [-TrustedOrganizations ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Inbound connectors accept email messages from remote domains that require specific configuration options. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-InboundConnector "Contoso Inbound Connector" -RequireTls $true -TlsSenderCertificateName contoso.com +``` + +This example makes the following configuration changes to the existing Inbound connector named Contoso.com Inbound Connector. + +Require TLS transmission for all incoming messages on the connector. + +Require that the TLS certificate that is used to encrypt communications contain the domain name contoso.com + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AssociatedAcceptedDomains +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CloudServicesMailEnabled +**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. + +Valid values are: + +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorSource +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. +- HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. +- Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. + +We recommended that you don't change this value. + +```yaml +Type: TenantConnectorSource +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorType +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. +- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors grant special rights to an email that matches the connector and additional requirements. For example: allowing relay through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows. + +```yaml +Type: TenantConnectorType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFSkipIPs +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. +- IP address range: For example, 192.168.0.1-192.168.0.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.3.1/24. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFSkipLastIP +The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are: + +- $true: Only the last message source is skipped. +- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFSkipMailGateway +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFTestMode +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EFUsers +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter enables or disables the connector. Valid values are: + +- $true: The connector is enabled. This is the default value. +- $false: The connector is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireTls +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 +- $false: Allow messages if they aren't sent over TLS. + +**Note**: This parameter applies only to Partner type connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictDomainsToCertificate +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. +- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value. + +**Note**: This parameter applies only to Partner type connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictDomainsToIPAddresses +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. +- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value. + +**Note**: This parameter applies only to Partner type connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScanAndDropRecipients +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderDomains +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderIPAddresses +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. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32. +@@ -435,6 +441,8 @@ You can specify multiple IP addresses separated by commas. + +IPv6 addresses are not supported. + +**Note**: This parameter applies to Partner type connectors only if the value of the RestrictDomainsToIPAddresses parameter is $true. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TlsSenderCertificateName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TreatMessagesAsInternal +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. +- $false: Messages aren't considered internal. This is the default value. + +In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Microsoft 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter). + +**Note**: You can't set this parameter to the value $true if either of the following conditions is true: + +- The CloudServicesMailEnabled parameter is set to the value $true. +- The ConnectorType parameter value is not OnPremises. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrustedOrganizations +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Set-InboxRule.md b/exchange/exchange-ps/exchange/Set-InboxRule.md similarity index 84% rename from exchange/exchange-ps/exchange/mailboxes/Set-InboxRule.md rename to exchange/exchange-ps/exchange/Set-InboxRule.md index e28bb40ff8..fbbb29f2cb 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-InboxRule.md +++ b/exchange/exchange-ps/exchange/Set-InboxRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-inboxrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-InboxRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-InboxRule cmdlet to modify existing Inbox rules in mailboxes. Inbox rules process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -36,7 +35,6 @@ Set-InboxRule [-Identity] [-ExceptIfFlaggedForAction ] [-ExceptIfFrom ] [-ExceptIfFromAddressContainsWords ] - [-ExceptIfFromSubscription ] [-ExceptIfHasAttachment ] [-ExceptIfHasClassification ] [-ExceptIfHeaderContainsWords ] @@ -62,7 +60,6 @@ Set-InboxRule [-Identity] [-ForwardTo ] [-From ] [-FromAddressContainsWords ] - [-FromSubscription ] [-HasAttachment ] [-HasClassification ] [-HeaderContainsWords ] @@ -85,6 +82,7 @@ Set-InboxRule [-Identity] [-SendTextMessageNotificationTo ] [-SentOnlyToMe ] [-SentTo ] + [-SoftDeleteMessage ] [-StopProcessingRules ] [-SubjectContainsWords ] [-SubjectOrBodyContainsWords ] @@ -101,13 +99,13 @@ The Set-InboxRule cmdlet allows you to modify the rule conditions, exceptions, a When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-InboxRule ProjectContoso -MarkImportance "High" +Set-InboxRule -Mailbox chris@contoso.com -Name ProjectContoso -MarkImportance "High" ``` This example modifies the action of the existing Inbox rule ProjectContoso. The MarkImportance parameter is used to mark the message with high importance. @@ -118,12 +116,9 @@ This example modifies the action of the existing Inbox rule ProjectContoso. The 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 - - RuleIdentity property (for example, 16752869479666417665). - -- Exchange Online: `\` (for example, `rzaher\16752869479666417665`. - -- On-premises Exchange: `\` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). +- Exchange Online: `MailboxAlias\RuleIdentity` (for example, `rzaher\16752869479666417665`). +- On-premises Exchange: `MailboxCanonicalName\RuleIdentity` (for example, `contoso.com/Users/Rick Zaher\16752869479666417665`). ```yaml Type: InboxRuleIdParameter @@ -139,7 +134,7 @@ Accept wildcard characters: False ``` ### -AlwaysDeleteOutlookRulesBlob -The AlwaysDeleteOutlookRulesBlob switch hides a warning message when end users or administrators use Outlook on the web or PowerShell to modify Inbox rules. You don't need to specify a value with this switch. +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 @@ -176,56 +171,33 @@ Accept wildcard characters: False 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 - - Bills - - Document - - DocumentPlus - - Event - - Family - - File - - Flight - - FromContact - - Important - - LiveView - - Lodging - - MailingList - - Newsletter - - Photo - - Purchase - - RentalCar - - RestaurantReservation - - RetiredPromotion - - ShippingNotification - - Shopping - - SocialUpdate - - Travel - - Video -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. +To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -243,9 +215,11 @@ Accept wildcard characters: False ### -BodyContainsWords The BodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the body of messages. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfBodyContainsWords. @@ -265,8 +239,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -288,23 +261,14 @@ The CopyToFolder parameter specifies an action for the Inbox rule that copies me For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Marketing` or `John:\Inbox\Reports`. @@ -326,51 +290,28 @@ Accept wildcard characters: False 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 - - Bills - - Document - - DocumentPlus - - Event - - Family - - File - - Flight - - FromContact - - Important - - LiveView - - Lodging - - MailingList - - Newsletter - - Photo - - Purchase - - RentalCar - - RestaurantReservation - - RetiredPromotion - - ShippingNotification - - Shopping - - SocialUpdate - - Travel - - Video You can specify multiple values separated by commas. @@ -392,7 +333,6 @@ Accept wildcard characters: False 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. - - $false: The action isn't used. ```yaml @@ -429,9 +369,11 @@ Accept wildcard characters: False ### -ExceptIfBodyContainsWords The ExceptIfBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the body of messages. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is BodyContainsWords. @@ -452,25 +394,15 @@ Accept wildcard characters: False The ExceptIfFlaggedForAction parameter specifies an exception for the Inbox rule that looks messages with the specified message flag. Valid values are: - Any - - Call - - DoNotForward - - FollowUp - - ForYourInformation - - Forward - - NoResponseNecessary - - Read - - Reply - - ReplyToAll - - Review The corresponding condition parameter to this exception is FlaggedForAction. @@ -489,21 +421,16 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom -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: For example: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding condition parameter to this exception is From. @@ -523,9 +450,11 @@ Accept wildcard characters: False ### -ExceptIfFromAddressContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is FromAddressContainsWords. @@ -542,31 +471,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ExceptIfFromSubscription -This parameter is available only in the cloud-based service. - -The ExceptIfFromSubscription parameter specifies an exception for the Inbox rule that looks for messages received from subscriptions (for example, POP or IMAP subscriptions). You can identify the subscription by using the Get-Subscription cmdlet. - -The corresponding condition parameter to this exception is FromSubscription. - -```yaml -Type: AggregationSubscriptionIdentity[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ExceptIfHasAttachment 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is HasAttachment. @@ -605,9 +513,11 @@ Accept wildcard characters: False ### -ExceptIfHeaderContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is HeaderContainsWords. @@ -628,25 +538,15 @@ Accept wildcard characters: False The ExceptIfMessageTypeMatches parameter specifies an exception for the Inbox rule that looks for messages of the specified type. Valid values are: - AutomaticReply - - AutomaticForward - - Encrypted - - Calendaring - - CalendaringResponse - - PermissionControlled - - Voicemail - - Signed - - ApprovalRequest - - ReadReceipt - - NonDeliveryReport The corresponding condition parameter to this exception is MessageTypeMatches. @@ -668,7 +568,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInCcBox. @@ -690,7 +589,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInToBox. @@ -712,7 +610,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInToOrCcBox. @@ -734,7 +631,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameNotInToBox. @@ -755,7 +651,7 @@ Accept wildcard characters: False ### -ExceptIfReceivedAfterDate 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". +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". The corresponding condition parameter to this exception is ReceivedAfterDate. @@ -775,7 +671,7 @@ Accept wildcard characters: False ### -ExceptIfReceivedBeforeDate 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". +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". The corresponding condition parameter to this exception is ReceivedBeforeDate. @@ -795,9 +691,11 @@ Accept wildcard characters: False ### -ExceptIfRecipientAddressContainsWords 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is RecipientAddressContainsWords. @@ -818,7 +716,6 @@ Accept wildcard characters: False 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. - - $false: The exception isn't used. The corresponding condition parameter to this exception is SentOnlyToMe. @@ -840,18 +737,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding condition parameter to this exception is SentTo. @@ -871,9 +763,11 @@ Accept wildcard characters: False ### -ExceptIfSubjectContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is SubjectContainsWords. @@ -893,11 +787,13 @@ Accept wildcard characters: False ### -ExceptIfSubjectOrBodyContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -The corresponding condition parameter to this exception is ExceptIfSubjectOrBodyContainsWords. +The maximum length of this parameter is 255 characters. + +The corresponding condition parameter to this exception is SubjectOrBodyContainsWords. ```yaml Type: MultiValuedProperty @@ -916,9 +812,7 @@ Accept wildcard characters: False The ExceptIfWithImportance parameter specifies an exception for the Inbox rule that looks for messages with the specified importance level. Valid values are: - High - - Normal - - Low The corresponding condition parameter to this exception is WithImportance. @@ -942,13 +836,9 @@ The ExceptIfWithinSizeRangeMaximum parameter specifies part of an exception for When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -976,13 +866,9 @@ The ExceptIfWithinSizeRangeMinimum parameter specifies part of an exception for When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1008,11 +894,8 @@ Accept wildcard characters: False The ExceptIfWithSensitivity parameter specifies an exception for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are: - Normal - - Personal - - Private - - CompanyConfidential The corresponding condition parameter to this exception is WithSensitivity. @@ -1034,25 +917,15 @@ Accept wildcard characters: False The FlaggedForAction parameter specifies a condition for the Inbox rule that looks for messages with the specified message flag. Valid values are: - Any - - Call - - DoNotForward - - FollowUp - - ForYourInformation - - Forward - - NoResponseNecessary - - Read - - Reply - - ReplyToAll - - Review ```yaml @@ -1069,7 +942,7 @@ Accept wildcard characters: False ``` ### -Force -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. +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. @@ -1090,18 +963,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1120,18 +988,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1150,18 +1013,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding exception parameter to this condition is ExceptIfFrom. @@ -1181,9 +1039,11 @@ Accept wildcard characters: False ### -FromAddressContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfFromAddressContainsWords. @@ -1200,31 +1060,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -FromSubscription -This parameter is available only in the cloud-based service. - -The FromSubscription parameter specifies a condition for the Inbox rule that looks for messages received from subscriptions (for example, POP or IMAP subscriptions). You can identify the subscription by using the Get-Subscription cmdlet. - -The corresponding exception parameter to this condition is ExceptIfFromSubscription. - -```yaml -Type: AggregationSubscriptionIdentity[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -HasAttachment 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfHasAttachment. @@ -1263,9 +1102,11 @@ Accept wildcard characters: False ### -HeaderContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfHeaderContainsWords. @@ -1286,23 +1127,14 @@ Accept wildcard characters: False The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -1322,7 +1154,6 @@ Accept wildcard characters: False 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. - - $false: The action isn't used. ```yaml @@ -1342,9 +1173,7 @@ Accept wildcard characters: False The MarkImportance parameter specifies an action for the Inbox rule that marks messages with the specified importance flag. Valid values are: - Low - - Normal - - High ```yaml @@ -1364,25 +1193,15 @@ Accept wildcard characters: False The MessageTypeMatches parameter specifies a condition for the Inbox rule that looks for messages of the specified type. Valid values are: - AutomaticReply - - AutomaticForward - - Encrypted - - Calendaring - - CalendaringResponse - - PermissionControlled - - Voicemail - - Signed - - ApprovalRequest - - ReadReceipt - - NonDeliveryReport The corresponding exception parameter to this condition is ExceptIfMessageTypeMatches. @@ -1406,23 +1225,14 @@ The MoveToFolder parameter specifies an action for the Inbox rule that moves mes For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Marketing` or `John:\Inbox\Reports`. @@ -1444,7 +1254,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInCcBox. @@ -1466,7 +1275,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInToBox. @@ -1488,7 +1296,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInToOrCcBox. @@ -1510,7 +1317,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameNotInToBox. @@ -1529,7 +1335,7 @@ Accept wildcard characters: False ``` ### -Name -The Name parameter specifies a name for the Inbox rule. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). +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 @@ -1548,7 +1354,6 @@ Accept wildcard characters: False 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. - - $false: The action isn't used. ```yaml @@ -1583,7 +1388,7 @@ Accept wildcard characters: False ### -ReceivedAfterDate 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". +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". The corresponding exception parameter to this condition is ExceptIfReceivedAfterDate. @@ -1603,7 +1408,7 @@ Accept wildcard characters: False ### -ReceivedBeforeDate 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". +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". The corresponding exception parameter to this condition is ExceptIfReceivedBeforeDate. @@ -1623,9 +1428,11 @@ Accept wildcard characters: False ### -RecipientAddressContainsWords 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfRecipientAddressContainsWords. @@ -1646,18 +1453,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1673,17 +1475,19 @@ Accept wildcard characters: False ``` ### -SendTextMessageNotificationTo +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. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1696,7 +1500,6 @@ Accept wildcard characters: False 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. - - $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfSentOnlyToMe. @@ -1718,18 +1521,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. The corresponding exception parameter to this condition is ExceptIfSentTo. @@ -1746,11 +1544,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SoftDeleteMessage +This parameter is available only in the cloud-based service. + +{{ Fill SoftDeleteMessage Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -StopProcessingRules 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. - - $false: The action isn't used (continue processing more rules after this one). ```yaml @@ -1769,9 +1584,11 @@ Accept wildcard characters: False ### -SubjectContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfSubjectContainsWords. @@ -1791,9 +1608,11 @@ Accept wildcard characters: False ### -SubjectOrBodyContainsWords 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 enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfSubjectOrBodyContainsWords. @@ -1830,9 +1649,7 @@ Accept wildcard characters: False The WithImportance parameter specifies a condition for the Inbox rule that looks for messages with the specified importance level. Valid values are: - High - - Normal - - Low The corresponding exception parameter to this condition is ExceptIfWithImportance. @@ -1856,13 +1673,9 @@ The WithinSizeRangeMaximum parameter specifies part of a condition for the Inbox When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1890,13 +1703,9 @@ The WithinSizeRangeMinimum parameter specifies part of a condition for the Inbox When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1922,11 +1731,8 @@ Accept wildcard characters: False The WithSensitivity parameter specifies a condition for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are: - Normal - - Personal - - Private - - CompanyConfidential The corresponding exception parameter to this condition is ExceptIfWithSensitivity. @@ -1949,12 +1755,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/Set-InformationBarrierPolicy.md new file mode 100644 index 0000000000..2fbe4dd044 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-InformationBarrierPolicy.md @@ -0,0 +1,274 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-InformationBarrierPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-InformationBarrierPolicy cmdlet to modify information barrier policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### OrganizationSegmentsAllowed +``` +Set-InformationBarrierPolicy -Identity + [-SegmentsAllowed ] + [-Comment ] + [-Confirm] + [-ModerationAllowed ] + [-Force] + [-State ] + [-WhatIf] + [] +``` + +### OrganizationSegmentAllowedFilter +``` +Set-InformationBarrierPolicy -Identity + [-SegmentAllowedFilter ] + [-Comment ] + [-Confirm] + [-Force] + [-ModerationAllowed ] + [-State ] + [-WhatIf] + [] +``` + +### OrganizationSegmentsBlocked +``` +Set-InformationBarrierPolicy -Identity + [-SegmentsBlocked ] + [-Comment ] + [-Confirm] + [-Force] + [-ModerationAllowed ] + [-State ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Information barrier policies are not in effect until you set them to active status, and then apply the policies: + +- (If needed): [Block communications between segments](https://learn.microsoft.com/purview/information-barriers-policies#scenario-1-block-communications-between-segments). +- After all of your policies are defined: [Apply information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies#step-4-apply-ib-policies). + +For more information, see [Information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-InformationBarrierPolicy -Identity 43c37853-ea10-4b90-a23d-ab8c93772471 -State Active +``` + +This example activates the specified inactive information barrier policy. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModerationAllowed +{{ Fill ModerationAllowed Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SegmentsAllowed +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"). + +You can't use this parameter with the SegmentsBlocked parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: OrganizationSegmentsAllowed +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SegmentAllowedFilter +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: OrganizationSegmentAllowedFilter +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SegmentsBlocked +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"). + +You can't use this parameter with the SegmentsAllowed parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: OrganizationSegmentsBlocked +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The State parameter specifies whether the information barrier policy is active or inactive. Valid values are: + +- Active +- Inactive + +```yaml +Type: EopInformationBarrierPolicyState +Parameter Sets: (All) +Aliases: +Accepted values: Inactive, Active +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-IntraOrganizationConnector.md b/exchange/exchange-ps/exchange/Set-IntraOrganizationConnector.md similarity index 84% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Set-IntraOrganizationConnector.md rename to exchange/exchange-ps/exchange/Set-IntraOrganizationConnector.md index 8edcb753e5..5216746dff 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/exchange/Set-IntraOrganizationConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-intraorganizationconnector -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-IntraOrganizationConnector @@ -17,20 +16,26 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-IntraOrganizationConnector cmdlet to modify an existing Intra-Organization connector between two on-premises Exchange forests in an organization, between an on-premises Exchange organization and an Exchange Online organization or between two Exchange Online organizations. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-IntraOrganizationConnector [-Identity] [-Confirm] - [-DiscoveryEndpoint ] [-DomainController ] [-Enabled ] - [-TargetAddressDomains ] [-WhatIf] [] +Set-IntraOrganizationConnector [-Identity] + [-Confirm] + [-DiscoveryEndpoint ] + [-DomainController ] + [-Enabled ] + [-TargetAddressDomains ] + [-TargetSharingEpr ] + [-WhatIf] + [] ``` ## DESCRIPTION Intra-Organizational connectors enable features and services between divisions in your Exchange organization. It allows for the expansion of organizational boundaries for features and services across different hosts and network boundaries, such as between Active Directory forests, between on-premises and cloud-based organizations or between tenants hosted in the same or different datacenters. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,16 +52,14 @@ This example disables the Intra-Organization connector named "MainCloudConnector 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 - - Distinguished name (DN) - - GUID ```yaml Type: IntraOrganizationConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -68,15 +71,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -153,6 +155,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -TargetSharingEpr +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. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -160,7 +180,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -174,12 +194,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-JournalRule.md b/exchange/exchange-ps/exchange/Set-JournalRule.md similarity index 93% rename from exchange/exchange-ps/exchange/policy-and-compliance/Set-JournalRule.md rename to exchange/exchange-ps/exchange/Set-JournalRule.md index b45bfa8272..3c8d9f1233 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-JournalRule.md +++ b/exchange/exchange-ps/exchange/Set-JournalRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-journalrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-JournalRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-JournalRule cmdlet to modify an existing journal rule in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,13 +28,14 @@ Set-JournalRule [-Identity] [-Name ] [-Recipient ] [-Scope ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Set-JournalRule cmdlet modifies an existing journal rule used in your organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,8 +76,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,15 +114,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -158,6 +152,8 @@ Accept wildcard characters: False ### -Recipient 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. + ```yaml Type: SmtpAddress Parameter Sets: (All) @@ -175,9 +171,7 @@ Accept wildcard characters: False 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. - - Internal: Internal rules process email messages sent to and received by recipients in your organization. - - External: External rules process email messages sent to recipients or from senders outside your organization. ```yaml @@ -214,12 +208,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-Label.md b/exchange/exchange-ps/exchange/Set-Label.md new file mode 100644 index 0000000000..8424874e92 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-Label.md @@ -0,0 +1,1665 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-Label + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-Label cmdlet to modify sensitivity labels in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-Label [-Identity] + [-AdvancedSettings ] + [-ApplyContentMarkingFooterAlignment ] + [-ApplyContentMarkingFooterEnabled ] + [-ApplyContentMarkingFooterFontColor ] + [-ApplyContentMarkingFooterFontName ] + [-ApplyContentMarkingFooterFontSize ] + [-ApplyContentMarkingFooterMargin ] + [-ApplyContentMarkingFooterText ] + [-ApplyContentMarkingHeaderAlignment ] + [-ApplyContentMarkingHeaderEnabled ] + [-ApplyContentMarkingHeaderFontColor ] + [-ApplyContentMarkingHeaderFontName ] + [-ApplyContentMarkingHeaderFontSize ] + [-ApplyContentMarkingHeaderMargin ] + [-ApplyContentMarkingHeaderText ] + [-ApplyDynamicWatermarkingEnabled ] + [-ApplyWaterMarkingEnabled ] + [-ApplyWaterMarkingFontColor ] + [-ApplyWaterMarkingFontName ] + [-ApplyWaterMarkingFontSize ] + [-ApplyWaterMarkingLayout ] + [-ApplyWaterMarkingText ] + [-ColumnAssetCondition ] + [-Comment ] + [-Conditions ] + [-Confirm] + [-ContentType ] + [-DefaultContentLabel ] + [-DisplayName ] + [-DynamicWatermarkDisplay ] + [-EncryptionContentExpiredOnDateInDaysOrNever ] + [-EncryptionDoNotForward ] + [-EncryptionDoubleKeyEncryptionUrl ] + [-EncryptionEnabled ] + [-EncryptionEncryptOnly ] + [-EncryptionOfflineAccessDays ] + [-EncryptionPromptUser ] + [-EncryptionProtectionType ] + [-EncryptionRightsDefinitions ] + [-EncryptionRightsUrl ] + [-LabelActions ] + [-LocaleSettings ] + [-MigrationId ] + [-NextLabel ] + [-ParentId ] + [-PreviousLabel ] + [-Priority ] + [-SchematizedDataCondition ] + [-Setting ] + [-Settings ] + [-SiteAndGroupProtectionAllowAccessToGuestUsers ] + [-SiteAndGroupProtectionAllowEmailFromGuestUsers ] + [-SiteAndGroupProtectionAllowFullAccess ] + [-SiteAndGroupProtectionAllowLimitedAccess ] + [-SiteAndGroupProtectionBlockAccess ] + [-SiteAndGroupProtectionEnabled ] + [-SiteAndGroupProtectionLevel ] + [-SiteAndGroupProtectionPrivacy ] + [-SiteExternalSharingControlType ] + [-TeamsAllowedPresenters ] + [-TeamsAllowMeetingChat ] + [-TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch ] + [-TeamsBypassLobbyForDialInUsers ] + [-TeamsChannelProtectionEnabled ] + [-TeamsChannelSharedWithExternalTenants ] + [-TeamsChannelSharedWithPrivateTeamsOnly ] + [-TeamsChannelSharedWithSameLabelOnly ] + [-TeamsCopyRestrictionEnforced ] + [-TeamsEndToEndEncryptionEnabled ] + [-TeamsLobbyBypassScope ] + [-TeamsLobbyRestrictionEnforced ] + [-TeamsPresentersRestrictionEnforced ] + [-TeamsProtectionEnabled ] + [-TeamsRecordAutomatically ] + [-TeamsVideoWatermark ] + [-TeamsWhoCanRecord ] + [-Tooltip ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-Label -Identity "Label1" -LocaleSettings '{"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"}]}','{"localeKey":"tooltip","Settings":[{"Key":"en-us","Value":"This is an example label"},{"Key":"de-de","Value":"Dies ist ein Beispieletikett"},{"Key":"es-es","Value":"Esta es una etiqueta de ejemplo"}]}' +``` + +This example sets the localized label name and label Tooltips for "Label1" in different languages (English, German, and Spanish). + +### Example 2 +```powershell +Set-Label -Identity "Label1" -LocaleSettings '{"localeKey":"DisplayName","Settings":[{"Key":"en-us","Value":""},{"Key":"de-de","Value":""},{"Key":"es-es","Value":""}]}','{"localeKey":"tooltip","Settings":[{"Key":"en-us","Value":""},{"Key":"de-de","Value":""},{"Key":"es-es","Value":""}]}' +``` + +This example removes the localized label name and label Tooltips for "Label1" in different languages (English, German, and Spanish). + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AdvancedSettings +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. + +Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings). + +Supported settings for built-in labeling: + +- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting impacts services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `Set-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). + +- **Color**: Specifies a label color as a hex triplet code for the red, green, and blue (RGB) components of the color. Example: `Set-Label -Identity 8faca7b8-8d20-48a3-8ea2-0f96310a848e -AdvancedSettings @{color="#40e0d0"}`. For more information, see [Configuring custom colors by using PowerShell](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configuring-custom-colors-by-using-powershell). + +- **DefaultSharingScope**: Specifies the default sharing link type for a site when the label scope includes **Groups & sites**, and the default sharing link type for a document when the label scope includes **Files & emails**. Available values are SpecificPeople, Organization, and Anyone. Example: `Set-Label -Identity General -AdvancedSettings @{DefaultSharingScope="SpecificPeople"}`. For more information, see [Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive](https://learn.microsoft.com/purview/sensitivity-labels-default-sharing-link). + +- **DefaultShareLinkPermission**: Specifies the permissions for the sharing link for a site when the label scope includes **Groups & sites**, and the permissions for the sharing link for a document when the label scope includes **Files & emails**. Available values are View and Edit. Example: `Set-Label -Identity General -AdvancedSettings @{DefaultShareLinkPermission="Edit"}`. For more information, see [Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive](https://learn.microsoft.com/purview/sensitivity-labels-default-sharing-link). + +- **DefaultShareLinkToExistingAccess**: Specifies whether to override *DefaultSharingScope* and *DefaultShareLinkPermission* to instead set the default sharing link type to people with existing access with their existing permissions. Example: `Set-Label -Identity General -AdvancedSettings @{DefaultShareLinkToExistingAccess="True"}`. For more information, see [Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive](https://learn.microsoft.com/purview/sensitivity-labels-default-sharing-link). + +- **DefaultSubLabelId**: Specifies a default sublabel to be applied automatically when a user selects a parent label in Office apps. Example: `Set-Label -Identity Confidential -AdvancedSettings @{DefaultSubLabelId="8faca7b8-8d20-48a3-8ea2-0f96310a848e"}`. For more information, see [Specify a default sublabel for a parent label](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#specify-a-default-sublabel-for-a-parent-label). + +- **MembersCanShare**: For a container label, specifies how members can share for a SharePoint site. Available values are MemberShareAll, MemberShareFileAndFolder, and MemberShareNone. Example: `Set-Label -Identity General -AdvancedSettings @{MembersCanShare="MemberShareFileAndFolder"}`. For more information, see [Configure site sharing permissions by using PowerShell advanced settings](https://learn.microsoft.com/purview/sensitivity-labels-teams-groups-sites#configure-site-sharing-permissions-by-using-powershell-advanced-settings). + +- **SMimeEncrypt**: Specifies S/MIME encryption for Outlook. Available values are True, and False (the default). Example: `Set-Label -Identity "Confidential" -AdvancedSettings @{SMimeEncrypt="True"}`. For more information, see [Configure a label to apply S/MIME protection in Outlook](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configure-a-label-to-apply-smime-protection-in-outlook). + +- **SMimeSign**: Specifies S/MIME digital signature for Outlook. Available values are True, and False (the default). Example: `Set-Label -Identity "Confidential" -AdvancedSettings @{SMimeSign="True"}`. For more information, see [Configure a label to apply S/MIME protection in Outlook](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configure-a-label-to-apply-smime-protection-in-outlook). + +For more information to help you configure advanced settings for a label, see [PowerShell tips for specifying the advanced settings](https://learn.microsoft.com/purview/create-sensitivity-labels#powershell-tips-for-specifying-the-advanced-settings). + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterAlignment +The ApplyContentMarkingFooterAlignment parameter specifies the footer alignment. Valid values are: + +- Left +- Center +- Right + +This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterEnabled +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. +- $false: The Apply Content Marking Footer action is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterFontColor +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterFontName +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. + +This parameter is supported only by the Azure Information Protection unified labeling client and not by Office apps and services that support built-in labeling. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterFontSize +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterMargin +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. + +**Note**: In Microsoft Word and PowerPoint, the specified value is used as a bottom (vertical) margin and left margin or right margin for left-aligned or right-aligned content marks. A minimum value of 15 points is required. Word also adds a constant offset of 5 points to the left margin for left-aligned content marks, or to the right margin for right-aligned content marks. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingFooterText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderAlignment +The ApplyContentMarkingHeaderAlignment parameter specifies the header alignment. Valid values are: + +- Left +- Center +- Right + +This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderEnabled +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. +- $false: The Apply Content Marking Header action is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderFontColor +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderFontName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderFontSize +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderMargin +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. + +**Note**: In Microsoft Word and PowerPoint, the specified value is used as a top margin and left margin or right margin for left-aligned or right-aligned content marks. A minimum value of 15 points is required. Word also adds a constant offset of 5 points to the left margin for left-aligned content marks, or to the right margin for right-aligned content marks. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyContentMarkingHeaderText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyDynamicWatermarkingEnabled +**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: + +- $true: Enables dynamic watermarking for a specific label. +- $false: Disables dynamic watermarking for a specific label. + +You set the watermark text with the DynamicWatermarkDisplay parameter. For more information about using dynamic watermarks for supported apps, see [Dynamic watermarks](https://learn.microsoft.com/purview/encryption-sensitivity-labels#dynamic-watermarks). + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingEnabled +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. +- $false: The Apply Watermarking Header action is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingFontColor +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingFontName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingFontSize +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingLayout +The ApplyWaterMarkingLayout parameter specifies the watermark alignment. Valid values are: + +- Horizontal +- Diagonal + +This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+WaterMarkingLayout +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplyWaterMarkingText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ColumnAssetCondition +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Conditions +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentType +The ContentType parameter specifies where the sensitivity label can be applied. Valid values are: + +- File +- Email +- Site +- UnifiedGroup +- PurviewAssets +- Teamwork +- SchematizedData + +Values can be combined, for example: "File, Email, PurviewAssets". + +```yaml +Type: MipLabelContentType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultContentLabel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DynamicWatermarkDisplay +**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: + +- **"\`${Consumer.PrincipalName}**": Required. The value is the user principal name (UPN) of the user. +- **"\`${Device.DateTime}**": Optional. The value is current date/time of the device used to view the document. + +**Tip** The back quotation mark character ( \` ) is required as an escape character for the dollar sign character ( $ ) in PowerShell. For more information, see [Escape characters in Exchange PowerShell](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax#escape-characters-in-exchange-powershell). + +This parameter is meaningful only when the ApplyDynamicWatermarkingEnabled parameter value is $true. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionContentExpiredOnDateInDaysOrNever +The EncryptionContentExpiredOnDateInDaysOrNever parameter specifies when the encrypted content expires. Valid values are: + +- An integer (number of days) +- The value `Never` + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionDoNotForward +The EncryptionDoNotForward parameter specifies whether the Do Not Forward template is applied. Valid values are: + +- $true: The Do Not Forward template is applied. +- $false: The Do Not Forward template is not applied. + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionDoubleKeyEncryptionUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionEnabled +The EncryptionEnabled parameter specifies whether encryption in enabled. Valid values are: + +- $true: Encryption is enabled. +- $false: Encryption is disabled. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionEncryptOnly +The EncryptionEncryptOnly parameter specifies whether the encrypt-only template is applied. Valid values are: + +- $true: The encrypt-only template is applied. +- $false: The encrypt-only template is not applied. + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionOfflineAccessDays +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. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionPromptUser +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. +- $false: The label is not set with user defined permissions in Word, Excel and PowerPoint. + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false, and when the EncryptionProtectionType parameter value is UserDefined. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionProtectionType +The EncryptionProtectionType parameter specifies the protection type for encryption. Valid values are: + +- Template +- RemoveProtection +- UserDefined + +This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+SupportedProtectionType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionRightsDefinitions +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. + +```yaml +Type: EncryptionRightsDefinitionsParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionRightsUrl +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LabelActions +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocaleSettings +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"}]}` +- Label Tooltips: `{"localeKey":"Tooltip","Settings":[{"Key":"en-us","Value":"English Tooltip"},{"Key":"de-de","Value":"Deutscher Tooltip"},{"Key":"es-es","Value":"Tooltip Español"}]}` + +To remove a language, you need to enter an empty value for that language. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrationId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NextLabel +This parameter is reserved for internal Microsoft use. + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParentId +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreviousLabel +This parameter is reserved for internal Microsoft use. + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SchematizedDataCondition +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Setting +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Settings +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowAccessToGuestUsers +The SiteAndGroupProtectionAllowAccessToGuestUsers parameter enables or disables access to guest users. Valid values are: + +- $true: Guest access is enabled. +- $false: Guest access is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowEmailFromGuestUsers +The SiteAndGroupProtectionAllowEmailFromGuestUsers parameter enables or disables email from guest users. Valid values are: + +- $true: Email from guest users is enabled. +- $false: Email from guest users is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowFullAccess +The SiteAndGroupProtectionAllowFullAccess parameter enables or disables full access. Valid values are: + +- $true: Full access is enabled. +- $false: Full access is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionAllowLimitedAccess +The SiteAndGroupProtectionAllowLimitedAccess parameter enables or disables limited access. Valid values are: + +- $true: Limited access is enabled. +- $false: Limited access is disabled. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionBlockAccess +The SiteAndGroupProtectionBlockAccess parameter blocks access. Valid values are: + +- $true: Access is blocked. +- $false: Access is allowed. + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionEnabled +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. +- $false: The Site and Group Protection action is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionLevel +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SiteAndGroupProtectionLevelParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAndGroupProtectionPrivacy +The SiteAndGroupProtectionPrivacy parameter specifies the privacy level for the labe. Valid values are: + +- Public +- Private + +This parameter is meaningful only when the SiteAndGroupProtectionEnabled parameter value is $true or $false. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.AccessType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteExternalSharingControlType +The SiteExternalSharingControlType parameter specifies the external user sharing setting for the label. Valid values are: + +- ExternalUserAndGuestSharing +- ExternalUserSharingOnly +- ExistingExternalUserSharingOnly +- Disabled + +These correspond to the following settings through the admin center: + +- Anyone +- New and Existing Guests +- Existing Guests +- Only people in your organization + +```yaml +Type: Microsoft.Office.CompliancePolicy.Tasks.SiteExternalSharingControlType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAllowedPresenters +The TeamsAllowedPresenters parameter controls who can present in Teams meetings. Valid values are: + +- Everyone +- Organization +- Organizer +- RoleIsPresenter +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.AllowedPresenters +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAllowMeetingChat +The TeamsAllowMeetingChat parameter controls whether chat is available in Teams meetings. Valid values are: + +- Enabled +- Disabled +- Limited: Chat is available only for the duration of the call. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.MeetingChatMode +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch +{{ Fill TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsBypassLobbyForDialInUsers +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. +- $false: Dial in users don't bypass the lobby when joining Teams meetings. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelProtectionEnabled +{{ Fill TeamsChannelProtectionEnabled Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelSharedWithExternalTenants +{{ Fill TeamsChannelSharedWithExternalTenants Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelSharedWithPrivateTeamsOnly +{{ Fill TeamsChannelSharedWithPrivateTeamsOnly Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsChannelSharedWithSameLabelOnly +{{ Fill TeamsChannelSharedWithSameLabelOnly Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsCopyRestrictionEnforced +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. +- $false: Chat messages can't be copied to the clipboard. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsEndToEndEncryptionEnabled +The TeamsEndToEndEncryptionEnabled parameter controls video stream encryption in Teams meetings. Valid values are: + +- $true: Video stream encryption is enabled. +- $false: Video stream encryption is not enabled. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsLobbyBypassScope +The TeamsLobbyBypassScope parameter controls who bypasses the lobby when joining Teams meetings. Valid values are: + +- Everyone +- Invited +- Organization +- OrganizationAndFederated +- OrganizationExcludingGuests +- Organizer +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.LobbyBypassScope +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsLobbyRestrictionEnforced +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. +- $false: Users don't bypass the lobby when joining Teams meetings. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsPresentersRestrictionEnforced +The TeamsPresentersRestrictionEnforced parameter controls whether presenter restrictions are enabled in Teams meetings. Valid values are: + +- $true: Presenter restrictions are enabled in Teams meetings. +- $false: Presenter restrictions aren't enabled in Teams meetings. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsProtectionEnabled +The TeamsProtectionEnabled parameter controls whether Teams protection is enabled in Teams meetings. Valid values are: + +- $true: Teams protection is enabled in Teams meetings. +- $false: Teams protection is not enabled in Teams meetings. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsRecordAutomatically +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. +- $false: Teams meetings are not automatically recorded. +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsVideoWatermark +The TeamsVideoWatermark parameter controls whether a watermark is shown in Teams meetings. Valid values are: + +- None +- EnabledForContentSharing +- EnabledForVideo +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WaterMarkProtectionValues +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsWhoCanRecord +The TeamsWhoCanRecord parameter controls who can record Teams meetings. Valid values are: + +- Organizer +- Coorganizers +- Presenters +- $null (blank): Users configure this setting themselves in the Teams app. + +```yaml +Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WhoCanRecordOptions +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tooltip +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-Label](https://learn.microsoft.com/powershell/module/exchange/new-label) diff --git a/exchange/exchange-ps/exchange/Set-LabelPolicy.md b/exchange/exchange-ps/exchange/Set-LabelPolicy.md new file mode 100644 index 0000000000..5b190d2637 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-LabelPolicy.md @@ -0,0 +1,818 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-LabelPolicy + +## SYNOPSIS +This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-Label cmdlet to modify sensitivity label policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### RetryDistribution +``` +Set-LabelPolicy [-Identity] -RetryDistribution + [-AddLabels ] + [-AdvancedSettings ] + [-Confirm] + [-MigrationId ] + [-NextLabelPolicy ] + [-PreviousLabelPolicy ] + [-RemoveLabels ] + [] +``` + +### Identity +``` +Set-LabelPolicy [-Identity] + [-AddExchangeLocation ] + [-AddExchangeLocationException ] + [-AddLabels ] + [-AddModernGroupLocation ] + [-AddModernGroupLocationException ] + [-AddOneDriveLocation ] + [-AddOneDriveLocationException ] + [-AddPublicFolderLocation ] + [-AddSharePointLocation ] + [-AddSharePointLocationException ] + [-AddSkypeLocation ] + [-AddSkypeLocationException ] + [-AdvancedSettings ] + [-Comment ] + [-Confirm] + [-MigrationId ] + [-NextLabelPolicy ] + [-PolicyRBACScopes ] + [-RemoveExchangeLocation ] + [-RemoveExchangeLocationException ] + [-RemoveLabels ] + [-RemoveModernGroupLocation ] + [-RemoveModernGroupLocationException ] + [-RemoveOneDriveLocation ] + [-RemoveOneDriveLocationException ] + [-RemovePublicFolderLocation ] + [-RemoveSharePointLocation ] + [-RemoveSharePointLocationException ] + [-RemoveSkypeLocation ] + [-RemoveSkypeLocationException ] + [] +``` + +### AdaptiveScopeLocation +``` +Set-LabelPolicy [-Identity] + [-AddLabels ] + [-AdvancedSettings ] + [-Comment ] + [-Confirm] + [-Force] + [-MigrationId ] + [-NextLabelPolicy ] + [-PreviousLabelPolicy ] + [-RemoveLabels ] + [-Setting ] + [-Settings ] + [-WhatIf] + [] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +**Note**: Don't use a piped Foreach-Object command when adding or removing scope locations: `"Value1","Value2",..."ValueN" | Foreach-Object {Set-LabelPolicy -Identity "Global Policy" -RemoveExchangeLocation $_ }`. + +## EXAMPLES + +### Example 1 +```powershell +Set-LabelPolicy -Identity "Global Policy" -AdvancedSettings @{EnableCustomPermissions="False"} +``` + +This example configures the specified advanced setting for the sensitivity label policy name Global Policy. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the policy that you want to view. You can use any value that uniquely identifies the policy. For example: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RetryDistribution +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. + +**Note**: Because the process of retrying distribution is a significant operation, run it only if necessary and for one policy at a time. It is not intended to be run every time you update a policy. If you run a script to update multiple policies, wait until the policy distribution is successful before running the command again for the next policy. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddLabels +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 +- Distinguished name (DN) +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddModernGroupLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddModernGroupLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddPublicFolderLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSkypeLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSkypeLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdvancedSettings +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. + +Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings). + +Supported settings for built-in labeling: + +- **AttachmentAction**: Unlabeled emails inherit the highest priority label from file attachments. Set the value to **Automatic** (to automatically apply the label) or **Recommended** (as a recommended prompt to the user. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{AttachmentAction="Automatic"}`. For more information about this configuration choice, see [Configure label inheritance from email attachments](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configure-label-inheritance-from-email-attachments). + +- **EnableAudit**: Prevent Office apps from sending sensitivity label data to Microsoft 365 auditing solutions. Supported apps: Word, Excel, and PowerPoint on Windows (version 2201+), macOS (version 16.57+), iOS (version 2.57+), and Android (version 16.0.14827+); Outlook on Windows (version 2201+), Outlook on the web, and rolling out to macOS, iOS, and Android. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableAudit="False"}`. + +- **EnableRevokeGuiSupport**: Remove the Track & Revoke button from the sensitivity menu in Office clients. Supported apps: Word, Excel, and PowerPoint on Windows (version 2406+). Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableRevokeGuiSupport="False"}`. For more information about this configuration choice, see [Track and revoke document access](https://learn.microsoft.com/purview/track-and-revoke-admin). + +- **DisableMandatoryInOutlook**: Outlook apps that support this setting exempt Outlook messages from mandatory labeling. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{DisableMandatoryInOutlook="True"}`. For more information about this configuration choice, see [Outlook-specific options for default label and mandatory labeling](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#outlook-specific-options-for-default-label-and-mandatory-labeling). + +- **OutlookDefaultLabel**: Outlook apps that support this setting apply a default label, or no label. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{OutlookDefaultLabel="None"}`. For more information about this configuration choice, see [Outlook-specific options for default label and mandatory labeling](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#outlook-specific-options-for-default-label-and-mandatory-labeling). + +- **TeamworkMandatory**: Outlook and Teams apps that support this setting can enable or disable mandatory labeling for meetings. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{TeamworkMandatory="True"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings). + +- **teamworkdefaultlabelid**: Outlook and Teams apps that support this setting apply a default label, or no label for meetings. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{teamworkdefaultlabelid="General"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings). + +- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) will be displayed. Users can't revert this setting in the app. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` + +- **DisableShowSensitiveContent**: For Office apps that highlight the sensitive content that caused a label to be recommended, turn off these highlights and corresponding indications about the sensitive content. For more information, see [Sensitivity labels are automatically applied or recommended for your files and emails in Office](https://support.microsoft.com/office/sensitivity-labels-are-automatically-applied-or-recommended-for-your-files-and-emails-in-office-622e0d9c-f38c-470a-bcdb-9e90b24d71a1). Supported apps: Word for Windows (version 2311+). Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{DisableShowSensitiveContent="True"}` + +Additionally, for Power BI: + +- **powerbimandatory**: Mandatory labeling for Power BI. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{powerbimandatory="true"}`. For more information about this configuration choice, see [Mandatory label policy for Power BI](https://learn.microsoft.com/power-bi/admin/service-security-sensitivity-label-mandatory-label-policy). + +- **powerbidefaultlabelid**: Default label for Power BI content. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{powerbidefaultlabelid="General"}`. For more information about this configuration choice, see [Default label policy for Power BI](https://learn.microsoft.com/power-bi/admin/service-security-sensitivity-label-default-label-policy). + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrationId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NextLabelPolicy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreviousLabelPolicy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +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 +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocationException +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 +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveLabels +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 +- Distinguished name (DN) +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveModernGroupLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveModernGroupLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePublicFolderLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSkypeLocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSkypeLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Setting +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Settings +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-LinkedUser.md b/exchange/exchange-ps/exchange/Set-LinkedUser.md similarity index 78% rename from exchange/exchange-ps/exchange/users-and-groups/Set-LinkedUser.md rename to exchange/exchange-ps/exchange/Set-LinkedUser.md index b9cb4dfe1e..ab7afd569b 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-LinkedUser.md +++ b/exchange/exchange-ps/exchange/Set-LinkedUser.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-linkeduser -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Set-LinkedUser @@ -17,22 +16,22 @@ This cmdlet is available only in the cloud-based service. Use the Set-LinkedUser cmdlet to modify the properties of an existing linked user account. The Outlook Live Directory Sync (OLSync) service account is a linked user. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-LinkedUser [-Identity] [-CertificateSubject ] [-Confirm] [-WhatIf] +Set-LinkedUser [-Identity] + [-CertificateSubject ] + [-Confirm] + [-WhatIf] [] ``` ## DESCRIPTION The OLSync service account is the only linked user in your organization. By default, the account is named GALSync-ServiceAccount. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,14 +48,13 @@ This example modifies the certificate subject for the linked user "GALSync-Servi The Identity parameter specifies the linked user. You can use any value that uniquely identifies the linked user, for example: - Name - - Distinguished name (DN) ```yaml Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -66,7 +64,7 @@ Accept wildcard characters: False ``` ### -CertificateSubject -The CertificateSubject parameter specifies the value of the subject field of the user's digital certificate. The syntax of the CertificateSubject value is X509:\Issuer\Subject. 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. +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 @@ -84,15 +82,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -108,7 +105,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -122,12 +119,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicy.md new file mode 100644 index 0000000000..db10ad8518 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicy.md @@ -0,0 +1,233 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-M365DataAtRestEncryptionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-M365DataAtRestEncryptionPolicy cmdlet to modify Microsoft 365 data-at-rest encryption policies in Exchange Online. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### TenantAdminPurgeKeyRequest +``` +Set-M365DataAtRestEncryptionPolicy [-Identity] [-Confirm] + [-Description ] + [-DomainController ] + [-Enabled ] + [-Force] + [-Name ] + [-WhatIf] + [] +``` + +### RefreshKey +``` +Set-M365DataAtRestEncryptionPolicy [-Identity] [-Confirm] + [-Description ] + [-DomainController ] + [-Enabled ] + [-Name ] + [-Refresh] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-M365DataAtRestEncryptionPolicy -Identity "Tenant Default Policy" -Enabled $false +``` + +This example disabled the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy. + +### Example 2 +```powershell +Set-M365DataAtRestEncryptionPolicy -Identity "Tenant Default Policy" -Refresh +``` + +This example updates the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy after one of the associated keys has been rotated in the Azure Key Vault. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter specifies an optional description for the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: DCAdminPurgeKeyRequest, TenantAdminPurgeKeyRequest +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Refresh +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicyAssignment.md new file mode 100644 index 0000000000..d5a82bfdda --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicyAssignment.md @@ -0,0 +1,70 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-M365DataAtRestEncryptionPolicyAssignment + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-M365DataAtRestEncryptionPolicyAssignment cmdlet to assign a Microsoft 365 data-at-rest encryption policy at the tenant level. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-M365DataAtRestEncryptionPolicyAssignment -DataEncryptionPolicy [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-M365DataAtRestEncryptionPolicyAssignment -DataEncryptionPolicy "Contoso Corporate" +``` + +This example assigns the Microsoft 365 data-at-rest encryption policy named Contoso Corporate. + +## PARAMETERS + +### -DataEncryptionPolicy +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-MailContact.md b/exchange/exchange-ps/exchange/Set-MailContact.md similarity index 78% rename from exchange/exchange-ps/exchange/users-and-groups/Set-MailContact.md rename to exchange/exchange-ps/exchange/Set-MailContact.md index e9b0e112d5..e699c9dec7 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-MailContact.md +++ b/exchange/exchange-ps/exchange/Set-MailContact.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-mailcontact -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailContact @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailContact cmdlet to modify existing mail contacts. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -85,13 +84,15 @@ Set-MailContact [-Identity] [-UMDtmfMap ] [-UseMapiRichTextFormat ] [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] [-WhatIf] [-WindowsEmailAddress ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -108,22 +109,17 @@ This example sets John Rodman's external email address to john@contoso.com. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml Type: MailContactIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -138,20 +134,15 @@ The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages t 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -161,7 +152,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -176,20 +167,15 @@ The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send m 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -199,7 +185,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -216,18 +202,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. @@ -239,7 +220,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -249,16 +230,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -269,7 +254,7 @@ The Alias parameter never generates or updates the primary email address of a ma Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -284,23 +269,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -322,20 +298,15 @@ The BypassModerationFromSendersOrMembers parameter specifies who is allowed to s To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +To enter multiple senders and overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more senders without affecting any existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. @@ -343,7 +314,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -355,15 +326,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -373,17 +343,18 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap +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: - $true: A DTMF map is created for the recipient. This is the default value. - - $false: A DTMF map isn't created for the recipient. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -399,7 +370,7 @@ This parameter specifies a value for the CustomAttribute1 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -415,7 +386,7 @@ This parameter specifies a value for the CustomAttribute10 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -431,7 +402,7 @@ This parameter specifies a value for the CustomAttribute11 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -447,7 +418,7 @@ This parameter specifies a value for the CustomAttribute12 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -463,7 +434,7 @@ This parameter specifies a value for the CustomAttribute13 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -479,7 +450,7 @@ This parameter specifies a value for the CustomAttribute14 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -495,7 +466,7 @@ This parameter specifies a value for the CustomAttribute15 property on the recip Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -511,7 +482,7 @@ This parameter specifies a value for the CustomAttribute2 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -527,7 +498,7 @@ This parameter specifies a value for the CustomAttribute3 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -543,7 +514,7 @@ This parameter specifies a value for the CustomAttribute4 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -559,7 +530,7 @@ This parameter specifies a value for the CustomAttribute5 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -575,7 +546,7 @@ This parameter specifies a value for the CustomAttribute6 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -591,7 +562,7 @@ This parameter specifies a value for the CustomAttribute7 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -607,7 +578,7 @@ This parameter specifies a value for the CustomAttribute8 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -623,7 +594,7 @@ This parameter specifies a value for the CustomAttribute9 property on the recipi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -639,7 +610,7 @@ The DisplayName parameter specifies the display name of the mail contact. The di Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -667,39 +638,34 @@ Accept wildcard characters: False ``` ### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). +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 \:\,\:\,...\:\. The optional \ value specifies the type of email address. Some examples of valid values include: +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: - SMTP: The primary SMTP address. You can use this value only once in a command. - - smtp: Other SMTP email addresses. - - X400: X.400 addresses in on-premises Exchange. - - X500: X.500 addresses in on-premises Exchange. -If you don't include a \ value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. To specify the primary SMTP email address, you can use any of the following methods: -- Use the \ value SMTP on the address. - -- The first email address when you don't use any \ values, or when you use multiple \ values of smtp. - +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. - Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\:\","\:\",..."\:\". +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\:\","\:\",...; Remove="\:\","\:\",...}. +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. ```yaml Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -714,7 +680,6 @@ 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: - $true: Email address policies are applied to this recipient. This is the default value. - - $false: Email address policies aren't applied to this recipient. ```yaml @@ -733,9 +698,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute1 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -743,7 +708,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -755,9 +720,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute2 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -765,7 +730,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -777,9 +742,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute3 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -787,7 +752,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -799,9 +764,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute4 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -809,7 +774,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -821,9 +786,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute5 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -831,7 +796,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -851,7 +816,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -861,13 +826,13 @@ Accept wildcard characters: False ``` ### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -877,33 +842,24 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo -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 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. By default, this parameter is blank, which means no one else has permission to send on behalf of this mail contact. @@ -911,7 +867,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -924,14 +880,13 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. - - $false: The recipient is visible in address lists. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -943,12 +898,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -968,24 +922,20 @@ Accept wildcard characters: False 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) - - UuEncode - - AppleSingle - - AppleDouble The MacAttachmentFormat and MessageFormat parameters are interdependent: - MessageFormat is Text: MacAttachmentFormat can be BinHex or UuEncode. - - MessageFormat is Mime: MacAttachmentFormat can be BinHex, AppleSingle, or AppleDouble. ```yaml Type: MacAttachmentFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -999,15 +949,14 @@ The MailTip parameter specifies the custom MailTip text for this recipient. The When you add a MailTip to a recipient, two things happen: -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \\This mailbox is not monitored\\. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `This mailbox is not monitored`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1021,17 +970,17 @@ The MailTipTranslations parameter specifies additional languages for the custom To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: -@{Add="\:\","\:\"...; Remove="\:\","\:\"...} +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. -\ is a valid ISO 639 two-letter culture code that's associated with the language. +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1048,11 +997,8 @@ The MaxReceiveSize parameter specifies the maximum size of a message that can be When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1061,7 +1007,7 @@ A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the val The value unlimited indicates the maximum receive message size for the mail contact is controlled elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1106,11 +1052,8 @@ The MaxSendSize parameter specifies the maximum size of a message that can be se When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1119,7 +1062,7 @@ A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the val The value unlimited indicates the maximum send message size for the mail contact is controlled elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1138,22 +1081,19 @@ Accept wildcard characters: False The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text - - Html - - TextAndHtml (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. ```yaml Type: MessageBodyFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1166,13 +1106,11 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text - - Mime (This is the default value) The MessageFormat and MessageBodyFormat parameters are interdependent: - MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - - MessageFormat is Text: MessageBodyFormat can only be Text. Therefore, if you want to change the MessageFormat parameter from Mime to Text, you must also change the MessageBodyFormat parameter to Text. @@ -1181,7 +1119,7 @@ Therefore, if you want to change the MessageFormat parameter from Mime to Text, Type: MessageFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1194,20 +1132,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -1215,7 +1148,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1228,7 +1161,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -1237,7 +1169,7 @@ You use the ModeratedBy parameter to specify the moderators. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1253,7 +1185,7 @@ The Name parameter specifies the unique name of the mail contact. The maximum le Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1269,7 +1201,7 @@ The PrimarySmtpAddress parameter specifies the primary return email address that By default, the primary address is the same as the ExternalEmailAddress parameter value. -If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, which means the email addresses of the mail contact aren't automatically updated by email address policies. We recommend that you don't set the primary email address to a value other than the ExternalEmailAddress unless you're in a cross-forest scenario. +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 contact aren't automatically updated by email address policies. We recommend that you don't set the primary email address to a value other than the ExternalEmailAddress unless you're in a cross-forest scenario. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. @@ -1292,20 +1224,15 @@ The RejectMessagesFrom parameter specifies who isn't allowed to send messages to 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1315,7 +1242,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1330,20 +1257,15 @@ The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send me 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1353,7 +1275,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1370,18 +1292,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. @@ -1393,7 +1310,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1405,7 +1322,7 @@ Accept wildcard characters: False ### -RemovePicture This parameter is available only in on-premises Exchange. -The RemovePicture switch specifies whether to remove the picture from the mail contact. You don't need to specify a value with this switch. +The RemovePicture switch removes the picture from the mail contact. You don't need to specify a value with this switch. You can add a picture to a mail contact by using the Import-RecipientDataProperty cmdlet. @@ -1425,7 +1342,7 @@ Accept wildcard characters: False ### -RemoveSpokenName This parameter is available only in on-premises Exchange. -The RemoveSpokenName parameter specifies whether to remove the spoken name from the mail contact. You don't need to specify a value with this switch. +The RemoveSpokenName switch removes the spoken name from the mail contact. You don't need to specify a value with this switch. You can add a sound file to a mail contact by using the Import-RecipientDataProperty cmdlet. @@ -1446,14 +1363,13 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1463,13 +1379,15 @@ Accept wildcard characters: False ``` ### -SecondaryAddress +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. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1479,13 +1397,15 @@ Accept wildcard characters: False ``` ### -SecondaryDialPlan +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. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1498,9 +1418,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -1509,7 +1427,7 @@ This parameter is only meaningful when moderation is enabled (the ModerationEnab Type: TransportModerationNotificationFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1522,18 +1440,16 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". +- space +- `" ' ( ) + , - . / : ?` ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1543,27 +1459,27 @@ Accept wildcard characters: False ``` ### -UMDtmfMap -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: - -- emailAddress:\ +This parameter is available only in on-premises Exchange. -- lastNameFirstName:\ +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: -- firstNameLastName:\ +- `emailAddress:` +- `lastNameFirstName:` +- `firstNameLastName:` -To enter values that overwrite all existing entries, use the following syntax: emailAddress:\,lastNameFirstName:\,firstNameLastName:\. +To enter values that overwrite all existing entries, use the following syntax: `emailAddress:,lastNameFirstName:,firstNameLastName:`. -If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:\, all existing lastNameFirstName and firstNameLastName values are removed. +If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only `emailAddress:`, all existing lastNameFirstName and firstNameLastName values are removed. -To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"; Remove="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"}. +To add or remove values without affecting other existing entries, use the following syntax: `@{Add="emailAddress:","lastNameFirstName:","firstNameLastName:"; Remove="emailAddress:","lastNameFirstName:","firstNameLastName:"}`. -If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:\","emailAddress:\} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. +If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use `@{Add="emailAddress:","emailAddress:}` to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1576,9 +1492,7 @@ Accept wildcard characters: False 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. - - Never: TNEF is never used for any messages sent to the mail user or mail contact. TNEF messages are converted to plain text. - - UseDefaultSettings: TNEF messages aren't specifically allowed or prevented for the mail user or mail contact. Whether TNEF messages are sent to the recipient depends on the remote domain TNEF settings (the default remote domain or a specific remote domain), or the Outlook Rich Text message settings specified by the sender in Outlook. The default value is UseDefaultSettings. @@ -1587,7 +1501,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1600,14 +1514,49 @@ Accept wildcard characters: False 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. - - $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserCertificate +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserSMimeCertificate +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1623,7 +1572,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1636,7 +1585,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -1645,7 +1593,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1659,12 +1607,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-MailPublicFolder.md b/exchange/exchange-ps/exchange/Set-MailPublicFolder.md similarity index 84% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Set-MailPublicFolder.md rename to exchange/exchange-ps/exchange/Set-MailPublicFolder.md index 3e5b185aa9..8dd27b3503 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-MailPublicFolder.md +++ b/exchange/exchange-ps/exchange/Set-MailPublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-mailpublicfolder -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailPublicFolder @@ -19,7 +18,7 @@ Use the Set-MailPublicFolder cmdlet to configure the mail-related settings of ma NOTE: The settings that you configure on a public folder mailbox might interfere with the existing settings on a public folder within in the mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -91,7 +90,7 @@ Set-MailPublicFolder [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -129,7 +128,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -144,20 +143,15 @@ The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages t 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -182,20 +176,15 @@ The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send m 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -222,18 +211,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. @@ -255,16 +239,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -285,28 +273,19 @@ Accept wildcard characters: False ``` ### -ArbitrationMailbox -This parameter is available or functional only in 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -328,20 +307,15 @@ The BypassModerationFromSendersOrMembers parameter specifies who is allowed to s To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +To enter multiple senders and overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more senders without affecting any existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. @@ -361,15 +335,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -384,18 +357,13 @@ The Contacts parameter specifies the contacts for the public folder. Contacts ar Valid values for this parameter are recipients in your organization. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -670,7 +638,6 @@ Accept wildcard characters: False 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. - - $false: If a forwarding recipient or email address is configured, messages are delivered only to the specified recipient or email address, and messages aren't delivered to this public folder. If no forwarding recipient or email address is configured, messages are delivered only to this public folder. The default value is $false. The value of this parameter is meaningful only if you configure a forwarding recipient or email address. @@ -723,33 +690,28 @@ Accept wildcard characters: False ``` ### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). +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 \:\,\:\,...\:\. The optional \ value specifies the type of email address. Some examples of valid values include: +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: - SMTP: The primary SMTP address. You can use this value only once in a command. - - smtp: Other SMTP email addresses. - - X400: X.400 addresses in on-premises Exchange. - - X500: X.500 addresses in on-premises Exchange. -If you don't include a \ value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. To specify the primary SMTP email address, you can use any of the following methods: -- Use the \ value SMTP on the address. - -- The first email address when you don't use any \ values, or when you use multiple \ values of smtp. - +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. - Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\:\","\:\",..."\:\". +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\:\","\:\",...; Remove="\:\","\:\",...}. +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. ```yaml Type: ProxyAddressCollection @@ -768,7 +730,6 @@ Accept wildcard characters: False 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. - - $false: Email address policies aren't applied to this recipient. ```yaml @@ -803,9 +764,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute1 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -825,9 +786,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute2 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -847,9 +808,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute3 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -869,9 +830,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute4 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -891,9 +852,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute5 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -930,21 +891,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID How messages are delivered and forwarded is controlled by the DeliverToMailboxAndForward parameter. - DeliverToMailboxAndForward is $true: Messages are delivered to this public folder and forwarded to the specified recipient. - - DeliverToMailboxAndForward is $false: Messages are only forwarded to the specified recipient. Messages aren't delivered to this public folder. The default value is blank ($null), which means no forwarding recipient is configured. @@ -963,33 +918,24 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo -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 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. By default, this parameter is blank, which means no one else has permission to send on behalf of this public folder. @@ -1010,7 +956,6 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. - - $false: The recipient is visible in address lists. This is the default value. ```yaml @@ -1027,12 +972,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -1052,7 +996,6 @@ Accept wildcard characters: False 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. - - $false: Don't skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the entire public folder migration will fail. This is the default value. ```yaml @@ -1073,9 +1016,8 @@ The MailTip parameter specifies the custom MailTip text for this recipient. The When you add a MailTip to a recipient, two things happen: -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \\This mailbox is not monitored\\. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `This mailbox is not monitored`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. ```yaml Type: String @@ -1095,11 +1037,11 @@ The MailTipTranslations parameter specifies additional languages for the custom To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: -@{Add="\:\","\:\"...; Remove="\:\","\:\"...} +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. -\ is a valid ISO 639 two-letter culture code that's associated with the language. +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. ```yaml Type: MultiValuedProperty @@ -1120,18 +1062,15 @@ The MaxReceiveSize parameter specifies the maximum size of a message that can be When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1152,18 +1091,15 @@ The MaxSendSize parameter specifies the maximum size of a message that can be se When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -1182,20 +1118,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -1216,7 +1147,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -1285,7 +1215,7 @@ Accept wildcard characters: False ### -PrimarySmtpAddress 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 that means the email addresses of the mail user no longer automatically updated by email address policies. +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. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. @@ -1306,11 +1236,8 @@ Accept wildcard characters: False The PublicFolderType parameter specifies which of the following four types is assigned to the public folder: - GeneralPurpose - - Mapi - - Nntp - - NotSpecified ```yaml @@ -1332,20 +1259,15 @@ The RejectMessagesFrom parameter specifies who isn't allowed to send messages to 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1370,20 +1292,15 @@ The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send me 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1410,18 +1327,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. @@ -1446,7 +1358,6 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. ```yaml @@ -1466,9 +1377,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -1490,11 +1399,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -1516,12 +1422,10 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". +- space +- `" ' ( ) + , - . / : ?` ```yaml Type: String @@ -1537,6 +1441,8 @@ Accept wildcard characters: False ``` ### -UMDtmfMap +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. ```yaml @@ -1559,7 +1465,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1572,7 +1478,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -1595,12 +1500,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-MailUser.md b/exchange/exchange-ps/exchange/Set-MailUser.md new file mode 100644 index 0000000000..45d451af6c --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailUser.md @@ -0,0 +1,3051 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailUser + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-MailUser cmdlet to modify mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Set-MailUser [-Identity] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArbitrationMailbox ] + [-ArchiveGuid ] + [-ArchiveName ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DisplayName ] + [-DomainController ] + [-EmailAddressPolicyEnabled ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-IgnoreDefaultScope] + [-ImmutableId ] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MaxReceiveSize ] + [-MaxSendSize ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RecoverableItemsQuota ] + [-RecoverableItemsWarningQuota ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemovePicture] + [-RemoveSpokenName] + [-RequireSenderAuthenticationEnabled ] + [-SamAccountName ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-SkipDualWrite] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserPrincipalName ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### EnableLitigationHoldForMigration +``` +Set-MailUser [-Identity] [-EnableLitigationHoldForMigration] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MailboxRegion ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### ExcludeFromAllOrgHolds +``` +Set-MailUser [-Identity] [-ExcludeFromAllOrgHolds] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-LOBAppAccount] + [-JournalArchiveAddress ] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MailboxRegion ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### ExcludeFromOrgHolds +``` +Set-MailUser [-Identity] [-ExcludeFromOrgHolds ] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailboxRegion ] + [-MailTip ] + [-MailTipTranslations ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### RecalculateInactiveMailUser +``` +Set-MailUser [-Identity] [-RecalculateInactiveMailUser] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailboxRegion ] + [-MailTip ] + [-MailTipTranslations ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### RemoveComplianceTagHoldApplied +``` +Set-MailUser [-Identity] [-RemoveComplianceTagHoldApplied] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailboxRegion ] + [-MailTip ] + [-MailTipTranslations ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### RemoveDelayHoldApplied +``` +Set-MailUser [-Identity] [-RemoveDelayHoldApplied] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MailboxRegion ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### RemoveDelayReleaseHoldApplied +``` +Set-MailUser [-Identity] [-RemoveDelayReleaseHoldApplied] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MailboxRegion ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### RemoveDisabledArchive +``` +Set-MailUser [-Identity] [-RemoveDisabledArchive] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailboxRegion ] + [-MailTip ] + [-MailTipTranslations ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### RemoveLitigationHoldEnabled +``` +Set-MailUser [-Identity] [-RemoveLitigationHoldEnabled] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MailboxRegion ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### RemoveOrphanedHolds +``` +Set-MailUser [-Identity] [-RemoveOrphanedHolds ] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CreateDTMFMap ] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HiddenFromAddressListsEnabled ] + [-HVEAccount] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MailboxRegion ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SecondaryAddress ] + [-SecondaryDialPlan ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UMDtmfMap ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +### UnblockForwardSyncPostCrossTenantMigration +``` +Set-MailUser [-Identity] [-UnblockForwardSyncPostCrossTenantMigration] + [-AcceptMessagesOnlyFrom ] + [-AcceptMessagesOnlyFromDLMembers ] + [-AcceptMessagesOnlyFromSendersOrMembers ] + [-Alias ] + [-ArchiveGuid ] + [-BypassModerationFromSendersOrMembers ] + [-Confirm] + [-CustomAttribute1 ] + [-CustomAttribute10 ] + [-CustomAttribute11 ] + [-CustomAttribute12 ] + [-CustomAttribute13 ] + [-CustomAttribute14 ] + [-CustomAttribute15 ] + [-CustomAttribute2 ] + [-CustomAttribute3 ] + [-CustomAttribute4 ] + [-CustomAttribute5 ] + [-CustomAttribute6 ] + [-CustomAttribute7 ] + [-CustomAttribute8 ] + [-CustomAttribute9 ] + [-DataEncryptionPolicy ] + [-DisplayName ] + [-EmailAddresses ] + [-ExchangeGuid ] + [-ExtensionCustomAttribute1 ] + [-ExtensionCustomAttribute2 ] + [-ExtensionCustomAttribute3 ] + [-ExtensionCustomAttribute4 ] + [-ExtensionCustomAttribute5 ] + [-ExternalEmailAddress ] + [-FederatedIdentity ] + [-ForceUpgrade] + [-GrantSendOnBehalfTo ] + [-HVEAccount] + [-HiddenFromAddressListsEnabled ] + [-ImmutableId ] + [-JournalArchiveAddress ] + [-LOBAppAccount] + [-MacAttachmentFormat ] + [-MailTip ] + [-MailTipTranslations ] + [-MailboxRegion ] + [-MaxReceiveSize ] + [-MaxSendSize ] + [-MessageBodyFormat ] + [-MessageFormat ] + [-MicrosoftOnlineServicesID ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-Name ] + [-Password ] + [-PrimarySmtpAddress ] + [-RecipientLimits ] + [-RejectMessagesFrom ] + [-RejectMessagesFromDLMembers ] + [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] + [-RequireSenderAuthenticationEnabled ] + [-ResetPasswordOnNextLogon ] + [-SendModerationNotifications ] + [-SimpleDisplayName ] + [-UseMapiRichTextFormat ] + [-UsePreferMessageFormat ] + [-UserCertificate ] + [-UserSMimeCertificate ] + [-WhatIf] + [-WindowsEmailAddress ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailUser -Identity "John Woods" -ExternalEmailAddress john@tailspintoys.com +``` + +This example modifies the external email address for the mail user named John Woods. Note that the original external email address isn't kept as a proxy address. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AcceptMessagesOnlyFrom +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. + +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. + +The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AcceptMessagesOnlyFromDLMembers +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. + +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. + +The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all groups. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AcceptMessagesOnlyFromSendersOrMembers +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. + +To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. + +To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. + +The individual senders and groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromDLMembers properties, respectively. Therefore, you can't use the AcceptMessagesOnlyFromSendersOrMembers parameter and the AcceptMessagesOnlyFrom or AcceptMessagesOnlyFromDLMembers parameters in the same command. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Alias +The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters. + +The Alias value can contain letters, numbers and the following characters: + +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. + +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. + +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: + +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. +- Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). + +If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). + +The Alias parameter never generates or updates the primary email address of a mail contact or a mail user. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ArbitrationMailbox +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ArchiveGuid +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ArchiveName +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassModerationFromSendersOrMembers +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +To enter multiple senders and overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. + +To add or remove one or more senders without affecting any existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. + +This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CreateDTMFMap +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: + +- $true: A DTMF map is created for the recipient. This is the default value. +- $false: A DTMF map isn't created for the recipient. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute1 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute10 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute11 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute12 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute13 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute14 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute15 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute2 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute3 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute4 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute5 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute6 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute7 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute8 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute9 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DataEncryptionPolicy +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: + +- Name +- Distinguished name (DN) +- GUID + +You can use the Get-DataEncryptionPolicy cmdlet to view the available policies. + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailAddresses +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: + +- SMTP: The primary SMTP address. You can use this value only once in a command. +- smtp: Other SMTP email addresses. +- X400: X.400 addresses in on-premises Exchange. +- X500: X.500 addresses in on-premises Exchange. + +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. + +To specify the primary SMTP email address, you can use any of the following methods: + +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. +- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. + +The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. + +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. + +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailAddressPolicyEnabled +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: + +- $true: Email address policies are applied to this recipient. This is the default value. +- $false: Email address policies aren't applied to this recipient. + +```yaml +Type: Boolean +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableLitigationHoldForMigration +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. + +This feature is not available in hybrid tenants. + +```yaml +Type: SwitchParameter +Parameter Sets: EnableLitigationHoldForMigration +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeGuid +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeFromAllOrgHolds +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. + +When you use this switch, use one of the following values to uniquely identify the soft-deleted mail user in the Identity parameter: + +- DistinguishedName +- Guid +- ExchangeGuid + +```yaml +Type: SwitchParameter +Parameter Sets: ExcludeFromAllOrgHolds +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeFromOrgHolds +This parameter is available only in the cloud-based service. + +{{ Fill ExcludeFromOrgHolds Description }} + +```yaml +Type: String[] +Parameter Sets: ExcludeFromOrgHolds +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute1 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute2 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute3 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute4 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute5 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalEmailAddress +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. + +When you use the ExternalEmailAddress parameter to change the external email address, the old external email address isn't kept as a proxy address. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceUpgrade +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GrantSendOnBehalfTo +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +By default, this parameter is blank, which means no one else has permission to send on behalf of this mail user. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenFromAddressListsEnabled +The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: + +- $true: The recipient isn't visible in address lists. +- $false: The recipient is visible in address lists. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HVEAccount +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. + +```yaml +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 +Required: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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. + +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImmutableId +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -JournalArchiveAddress +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LOBAppAccount +This parameter is available only in the cloud-based service. + +{{ Fill LOBAppAccount Description }} + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MacAttachmentFormat +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) +- UuEncode +- AppleSingle +- AppleDouble + +The MacAttachmentFormat and MessageFormat parameters are interdependent: + +- MessageFormat is Text: MacAttachmentFormat can be BinHex or UuEncode. +- MessageFormat is Mime: MacAttachmentFormat can be BinHex, AppleSingle, or AppleDouble. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxRegion +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTip +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: + +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `This mailbox is not monitored`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTipTranslations +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: + +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. + +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. + +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxReceiveSize +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). + +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxSendSize +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). + +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageBodyFormat +The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: + +- Text +- Html +- TextAndHtml (This is the default value) + +The MessageFormat and MessageBodyFormat parameters are interdependent: + +- MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. +- MessageFormat is Text: MessageBodyFormat can only be Text. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageFormat +The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: + +- Text +- Mime (This is the default value) + +The MessageFormat and MessageBodyFormat parameters are interdependent: + +- MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. +- MessageFormat is Text: MessageBodyFormat can only be Text. + +Therefore, if you want to change the MessageFormat parameter from Mime to Text, you must also change the MessageBodyFormat parameter to Text. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MicrosoftOnlineServicesID +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModeratedBy +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModerationEnabled +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. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. + +You use the ModeratedBy parameter to specify the moderators. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Password +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: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +You can't use this parameter to change another user's password (the parameter is available only via the MyBaseOptions user role). 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. + +```yaml +Type: SecureString +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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. + +By default, the primary address is the same as the ExternalEmailAddress parameter value. + +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. We recommend that you don't set the primary email address to a value other than the ExternalEmailAddress unless you're in a cross-forest scenario. + +The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecalculateInactiveMailUser +This parameter is available only in the cloud-based service. + +{{ Fill RecalculateInactiveMailUser Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: RecalculateInactiveMailUser +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientLimits +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. + +A valid value is an integer or the value unlimited. The default value is unlimited. + +The value unlimited indicates the maximum number of recipients per message for the mail user is controlled elsewhere (for example, organization, server, or connector limits). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecoverableItemsQuota +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. + +When you enter a value, qualify the value with one of the following units: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 30 gigabytes (32212254720 bytes). + +The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. + +```yaml +Type: Unlimited +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecoverableItemsWarningQuota +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. + +When you enter a value, qualify the value with one of the following units: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 20 gigabytes (21474836480 bytes). + +The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. + +```yaml +Type: Unlimited +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RejectMessagesFrom +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. + +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. + +The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RejectMessagesFromDLMembers +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. + +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. + +The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all groups. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RejectMessagesFromSendersOrMembers +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. + +To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. + +To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. + +The individual senders and groups you specify for this parameter are automatically copied to the RejectMessagesFrom and RejectMessagesFromDLMembers properties, respectively. Therefore, you can't use the RejectMessagesFromSendersOrMembers parameter and the RejectMessagesFrom or RejectMessagesFromDLMembers parameters in the same command. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveComplianceTagHoldApplied +This parameter is available only in the cloud-based service. + +{{ Fill RemoveComplianceTagHoldApplied Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: RemoveComplianceTagHoldApplied +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveDelayHoldApplied +This parameter is available only in the cloud-based service. + +{{ Fill RemoveDelayHoldApplied Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: RemoveDelayHoldApplied +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveDelayReleaseHoldApplied +This parameter is available only in the cloud-based service. + +{{ Fill RemoveDelayReleaseHoldApplied Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: RemoveDelayReleaseHoldApplied +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveDisabledArchive +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. + +```yaml +Type: SwitchParameter +Parameter Sets: RemoveDisabledArchive +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveLitigationHoldEnabled +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. + +This switch is useful in scenarios where admins can't permanently delete mail users due to litigation holds on the mail users. For more information on litigation hold, see [Create a Litigation hold](https://learn.microsoft.com/en-us/purview/ediscovery-create-a-litigation-hold). + +```yaml +Type: SwitchParameter +Parameter Sets: RemoveLitigationHoldEnabled +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveMailboxProvisioningConstraint +This parameter is available only in the cloud-based service. + +{{ Fill RemoveMailboxProvisioningConstraint Description }} + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOrphanedHolds +This parameter is available only in the cloud-based service. + +{{ Fill RemoveOrphanedHolds Description }} + +```yaml +Type: String[] +Parameter Sets: RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePicture +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. + +You can add a picture to a mail user by using the Import-RecipientDataProperty cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSpokenName +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. + +You can add a sound file to a mail user by using the Import-RecipientDataProperty cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireSenderAuthenticationEnabled +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. +- $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResetPasswordOnNextLogon +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: + +- $true: The user is required to change their password then next time they successfully log on. +- $false: The user isn't required to change their password then next time they successfully log on. This is the default value. + +You can't use this parameter to require another user to change their password (the parameter is available only via the MyBaseOptions user role). You need to use the ForceChangePasswordNextSignIn value in the PasswordProfile parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SamAccountName +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. + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SecondaryAddress +This parameter is available only in on-premises Exchange. + +The SecondaryAddress parameter specifies the secondary address used by the Unified Messaging (UM)-enabled user. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SecondaryDialPlan +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. + +```yaml +Type: UMDialPlanIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendModerationNotifications +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. +- Internal: Notify senders in the organization when their messages aren't approved. +- Never: Don't notify anyone when a message isn't approved. + +This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SimpleDisplayName +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 +- A - Z +- 0 - 9 +- space +- `" ' ( ) + , - . / : ?` + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipDualWrite +This parameter is available only in Exchange 2016 or later. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UMDtmfMap +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: + +- `emailAddress:` +- `lastNameFirstName:` +- `firstNameLastName:` + +To enter values that overwrite all existing entries, use the following syntax: `emailAddress:,lastNameFirstName:,firstNameLastName:`. + +If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only `emailAddress:`, all existing lastNameFirstName and firstNameLastName values are removed. + +To add or remove values without affecting other existing entries, use the following syntax: `@{Add="emailAddress:","lastNameFirstName:","firstNameLastName:"; Remove="emailAddress:","lastNameFirstName:","firstNameLastName:"}`. + +If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use `@{Add="emailAddress:","emailAddress:}` to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnblockForwardSyncPostCrossTenantMigration +This parameter is available only in the cloud-based service. + +{{ Fill UnblockForwardSyncPostCrossTenantMigration Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: UnblockForwardSyncPostCrossTenantMigration +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseMapiRichTextFormat +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. +- Never: TNEF is never used for any messages sent to the mail user or mail contact. TNEF messages are converted to plain text. +- UseDefaultSettings: TNEF messages aren't specifically allowed or prevented for the mail user or mail contact. Whether TNEF messages are sent to the recipient depends on the remote domain TNEF settings (the default remote domain or a specific remote domain), or the Outlook Rich Text message settings specified by the sender in Outlook. + +The default value is UseDefaultSettings. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsePreferMessageFormat +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. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserCertificate +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserPrincipalName +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. + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserSMimeCertificate +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WindowsEmailAddress +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. +- In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. + +The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailboxes/Set-Mailbox.md b/exchange/exchange-ps/exchange/Set-Mailbox.md similarity index 81% rename from exchange/exchange-ps/exchange/mailboxes/Set-Mailbox.md rename to exchange/exchange-ps/exchange/Set-Mailbox.md index 8a03304a92..f24e40f01c 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-Mailbox.md +++ b/exchange/exchange-ps/exchange/Set-Mailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-Mailbox @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-Mailbox cmdlet to modify the settings of existing mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -204,12 +203,14 @@ Set-Mailbox [-Identity] [-UserPrincipalName ] [-UserSMimeCertificate ] [-WhatIf] - [-WindowsEmailAddress ] [] + [-WindowsEmailAddress ] + [] ``` ### ExcludeFromAllOrgHolds ``` -Set-Mailbox [-Identity] [-ExcludeFromAllOrgHolds] +Set-Mailbox [-Identity] + [-ExcludeFromAllOrgHolds] [-AcceptMessagesOnlyFrom ] [-AcceptMessagesOnlyFromDLMembers ] [-AcceptMessagesOnlyFromSendersOrMembers ] @@ -227,6 +228,7 @@ Set-Mailbox [-Identity] [-ExcludeFromAllOrgHolds] [-BypassModerationFromSendersOrMembers ] [-CalendarRepairDisabled ] [-CalendarVersionStoreDisabled ] + [-ClearThrottlingPolicyAssignment] [-Confirm] [-CreateDTMFMap ] [-CustomAttribute1 ] @@ -250,9 +252,11 @@ Set-Mailbox [-Identity] [-ExcludeFromAllOrgHolds] [-DeliverToMailboxAndForward ] [-DisplayName ] [-ElcProcessingDisabled ] + [-EmailAddressDisplayNames ] [-EmailAddresses ] [-EnableRoomMailboxAccount ] [-EndDateForRetentionHold ] + [-EnforcedTimestamps ] [-ExtensionCustomAttribute1 ] [-ExtensionCustomAttribute2 ] [-ExtensionCustomAttribute3 ] @@ -283,12 +287,14 @@ Set-Mailbox [-Identity] [-ExcludeFromAllOrgHolds] [-MaxSendSize ] [-MessageCopyForSendOnBehalfEnabled ] [-MessageCopyForSentAsEnabled ] + [-MessageCopyForSMTPClientSubmissionEnabled ] [-MessageTracking ] [-MessageTrackingReadStatusEnabled ] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-Name ] + [-NonCompliantDevices ] [-Office ] [-Password ] [-ProhibitSendQuota ] @@ -299,6 +305,7 @@ Set-Mailbox [-Identity] [-ExcludeFromAllOrgHolds] [-RejectMessagesFrom ] [-RejectMessagesFromDLMembers ] [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] [-RequireSenderAuthenticationEnabled ] [-ResourceCapacity ] [-ResourceCustom ] @@ -310,6 +317,7 @@ Set-Mailbox [-Identity] [-ExcludeFromAllOrgHolds] [-RoleAssignmentPolicy ] [-RoomMailboxPassword ] [-RulesQuota ] + [-SchedulerAssistant ] [-SecondaryAddress ] [-SecondaryDialPlan ] [-SendModerationNotifications ] @@ -320,17 +328,20 @@ Set-Mailbox [-Identity] [-ExcludeFromAllOrgHolds] [-StartDateForRetentionHold ] [-Type ] [-UMDtmfMap ] + [-UpdateEnforcedTimestamp] [-UseDatabaseQuotaDefaults ] [-UseDatabaseRetentionDefaults ] [-UserCertificate ] [-UserSMimeCertificate ] [-WhatIf] - [-WindowsEmailAddress ] [] + [-WindowsEmailAddress ] + [] ``` ### ExcludeFromOrgHolds ``` -Set-Mailbox [-Identity] [-ExcludeFromOrgHolds ] +Set-Mailbox [-Identity] + [-ExcludeFromOrgHolds ] [-AcceptMessagesOnlyFrom ] [-AcceptMessagesOnlyFromDLMembers ] [-AcceptMessagesOnlyFromSendersOrMembers ] @@ -348,6 +359,7 @@ Set-Mailbox [-Identity] [-ExcludeFromOrgHolds ] [-BypassModerationFromSendersOrMembers ] [-CalendarRepairDisabled ] [-CalendarVersionStoreDisabled ] + [-ClearThrottlingPolicyAssignment] [-Confirm] [-CreateDTMFMap ] [-CustomAttribute1 ] @@ -371,9 +383,11 @@ Set-Mailbox [-Identity] [-ExcludeFromOrgHolds ] [-DeliverToMailboxAndForward ] [-DisplayName ] [-ElcProcessingDisabled ] + [-EmailAddressDisplayNames ] [-EmailAddresses ] [-EnableRoomMailboxAccount ] [-EndDateForRetentionHold ] + [-EnforcedTimestamps ] [-ExtensionCustomAttribute1 ] [-ExtensionCustomAttribute2 ] [-ExtensionCustomAttribute3 ] @@ -404,12 +418,14 @@ Set-Mailbox [-Identity] [-ExcludeFromOrgHolds ] [-MaxSendSize ] [-MessageCopyForSendOnBehalfEnabled ] [-MessageCopyForSentAsEnabled ] + [-MessageCopyForSMTPClientSubmissionEnabled ] [-MessageTracking ] [-MessageTrackingReadStatusEnabled ] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-Name ] + [-NonCompliantDevices ] [-Office ] [-Password ] [-ProhibitSendQuota ] @@ -420,6 +436,7 @@ Set-Mailbox [-Identity] [-ExcludeFromOrgHolds ] [-RejectMessagesFrom ] [-RejectMessagesFromDLMembers ] [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] [-RequireSenderAuthenticationEnabled ] [-ResourceCapacity ] [-ResourceCustom ] @@ -431,6 +448,7 @@ Set-Mailbox [-Identity] [-ExcludeFromOrgHolds ] [-RoleAssignmentPolicy ] [-RoomMailboxPassword ] [-RulesQuota ] + [-SchedulerAssistant ] [-SecondaryAddress ] [-SecondaryDialPlan ] [-SendModerationNotifications ] @@ -441,17 +459,20 @@ Set-Mailbox [-Identity] [-ExcludeFromOrgHolds ] [-StartDateForRetentionHold ] [-Type ] [-UMDtmfMap ] + [-UpdateEnforcedTimestamp] [-UseDatabaseQuotaDefaults ] [-UseDatabaseRetentionDefaults ] [-UserCertificate ] [-UserSMimeCertificate ] [-WhatIf] - [-WindowsEmailAddress ] [] + [-WindowsEmailAddress ] + [] ``` ### RecalculateInactiveMailbox ``` -Set-Mailbox [-Identity] [-RecalculateInactiveMailbox] +Set-Mailbox [-Identity] + [-RecalculateInactiveMailbox] [-AcceptMessagesOnlyFrom ] [-AcceptMessagesOnlyFromDLMembers ] [-AcceptMessagesOnlyFromSendersOrMembers ] @@ -469,6 +490,7 @@ Set-Mailbox [-Identity] [-RecalculateInactiveMailbox] [-BypassModerationFromSendersOrMembers ] [-CalendarRepairDisabled ] [-CalendarVersionStoreDisabled ] + [-ClearThrottlingPolicyAssignment] [-Confirm] [-CreateDTMFMap ] [-CustomAttribute1 ] @@ -492,9 +514,11 @@ Set-Mailbox [-Identity] [-RecalculateInactiveMailbox] [-DeliverToMailboxAndForward ] [-DisplayName ] [-ElcProcessingDisabled ] + [-EmailAddressDisplayNames ] [-EmailAddresses ] [-EnableRoomMailboxAccount ] [-EndDateForRetentionHold ] + [-EnforcedTimestamps ] [-ExtensionCustomAttribute1 ] [-ExtensionCustomAttribute2 ] [-ExtensionCustomAttribute3 ] @@ -525,12 +549,14 @@ Set-Mailbox [-Identity] [-RecalculateInactiveMailbox] [-MaxSendSize ] [-MessageCopyForSendOnBehalfEnabled ] [-MessageCopyForSentAsEnabled ] + [-MessageCopyForSMTPClientSubmissionEnabled ] [-MessageTracking ] [-MessageTrackingReadStatusEnabled ] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-Name ] + [-NonCompliantDevices ] [-Office ] [-Password ] [-ProhibitSendQuota ] @@ -541,6 +567,7 @@ Set-Mailbox [-Identity] [-RecalculateInactiveMailbox] [-RejectMessagesFrom ] [-RejectMessagesFromDLMembers ] [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] [-RequireSenderAuthenticationEnabled ] [-ResourceCapacity ] [-ResourceCustom ] @@ -552,6 +579,7 @@ Set-Mailbox [-Identity] [-RecalculateInactiveMailbox] [-RoleAssignmentPolicy ] [-RoomMailboxPassword ] [-RulesQuota ] + [-SchedulerAssistant ] [-SecondaryAddress ] [-SecondaryDialPlan ] [-SendModerationNotifications ] @@ -562,17 +590,20 @@ Set-Mailbox [-Identity] [-RecalculateInactiveMailbox] [-StartDateForRetentionHold ] [-Type ] [-UMDtmfMap ] + [-UpdateEnforcedTimestamp] [-UseDatabaseQuotaDefaults ] [-UseDatabaseRetentionDefaults ] [-UserCertificate ] [-UserSMimeCertificate ] [-WhatIf] - [-WindowsEmailAddress ] [] + [-WindowsEmailAddress ] + [] ``` ### RemoveDelayHoldApplied ``` -Set-Mailbox [-Identity] [-RemoveDelayHoldApplied] +Set-Mailbox [-Identity] + [-RemoveDelayHoldApplied] [-AcceptMessagesOnlyFrom ] [-AcceptMessagesOnlyFromDLMembers ] [-AcceptMessagesOnlyFromSendersOrMembers ] @@ -590,6 +621,7 @@ Set-Mailbox [-Identity] [-RemoveDelayHoldApplied] [-BypassModerationFromSendersOrMembers ] [-CalendarRepairDisabled ] [-CalendarVersionStoreDisabled ] + [-ClearThrottlingPolicyAssignment] [-Confirm] [-CreateDTMFMap ] [-CustomAttribute1 ] @@ -613,9 +645,11 @@ Set-Mailbox [-Identity] [-RemoveDelayHoldApplied] [-DeliverToMailboxAndForward ] [-DisplayName ] [-ElcProcessingDisabled ] + [-EmailAddressDisplayNames ] [-EmailAddresses ] [-EnableRoomMailboxAccount ] [-EndDateForRetentionHold ] + [-EnforcedTimestamps ] [-ExtensionCustomAttribute1 ] [-ExtensionCustomAttribute2 ] [-ExtensionCustomAttribute3 ] @@ -646,12 +680,14 @@ Set-Mailbox [-Identity] [-RemoveDelayHoldApplied] [-MaxSendSize ] [-MessageCopyForSendOnBehalfEnabled ] [-MessageCopyForSentAsEnabled ] + [-MessageCopyForSMTPClientSubmissionEnabled ] [-MessageTracking ] [-MessageTrackingReadStatusEnabled ] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-Name ] + [-NonCompliantDevices ] [-Office ] [-Password ] [-ProhibitSendQuota ] @@ -662,6 +698,7 @@ Set-Mailbox [-Identity] [-RemoveDelayHoldApplied] [-RejectMessagesFrom ] [-RejectMessagesFromDLMembers ] [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] [-RequireSenderAuthenticationEnabled ] [-ResourceCapacity ] [-ResourceCustom ] @@ -673,6 +710,7 @@ Set-Mailbox [-Identity] [-RemoveDelayHoldApplied] [-RoleAssignmentPolicy ] [-RoomMailboxPassword ] [-RulesQuota ] + [-SchedulerAssistant ] [-SecondaryAddress ] [-SecondaryDialPlan ] [-SendModerationNotifications ] @@ -683,17 +721,20 @@ Set-Mailbox [-Identity] [-RemoveDelayHoldApplied] [-StartDateForRetentionHold ] [-Type ] [-UMDtmfMap ] + [-UpdateEnforcedTimestamp] [-UseDatabaseQuotaDefaults ] [-UseDatabaseRetentionDefaults ] [-UserCertificate ] [-UserSMimeCertificate ] [-WhatIf] - [-WindowsEmailAddress ] [] + [-WindowsEmailAddress ] + [] ``` ### RemoveDelayReleaseHoldApplied ``` -Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] +Set-Mailbox [-Identity] + [-RemoveDelayReleaseHoldApplied] [-AcceptMessagesOnlyFrom ] [-AcceptMessagesOnlyFromDLMembers ] [-AcceptMessagesOnlyFromSendersOrMembers ] @@ -710,6 +751,7 @@ Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] [-BypassModerationFromSendersOrMembers ] [-CalendarRepairDisabled ] [-CalendarVersionStoreDisabled ] + [-ClearThrottlingPolicyAssignment] [-CreateDTMFMap ] [-CustomAttribute1 ] [-CustomAttribute10 ] @@ -732,9 +774,11 @@ Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] [-DeliverToMailboxAndForward ] [-DisplayName ] [-ElcProcessingDisabled ] + [-EmailAddressDisplayNames ] [-EmailAddresses ] [-EnableRoomMailboxAccount ] [-EndDateForRetentionHold ] + [-EnforcedTimestamps ] [-ExtensionCustomAttribute1 ] [-ExtensionCustomAttribute2 ] [-ExtensionCustomAttribute3 ] @@ -765,11 +809,13 @@ Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] [-MaxSendSize ] [-MessageCopyForSendOnBehalfEnabled ] [-MessageCopyForSentAsEnabled ] + [-MessageCopyForSMTPClientSubmissionEnabled ] [-MessageTrackingReadStatusEnabled ] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-Name ] + [-NonCompliantDevices ] [-Office ] [-Password ] [-ProhibitSendQuota ] @@ -780,6 +826,7 @@ Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] [-RejectMessagesFrom ] [-RejectMessagesFromDLMembers ] [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] [-RequireSenderAuthenticationEnabled ] [-ResourceCapacity ] [-ResourceCustom ] @@ -791,6 +838,7 @@ Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] [-RoleAssignmentPolicy ] [-RoomMailboxPassword ] [-RulesQuota ] + [-SchedulerAssistant ] [-SecondaryAddress ] [-SecondaryDialPlan ] [-SendModerationNotifications ] @@ -801,6 +849,7 @@ Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] [-StsRefreshTokensValidFrom ] [-Type ] [-UMDtmfMap ] + [-UpdateEnforcedTimestamp] [-UseDatabaseQuotaDefaults ] [-UseDatabaseRetentionDefaults ] [-UserCertificate ] @@ -813,7 +862,8 @@ Set-Mailbox [-Identity] [-RemoveDelayReleaseHoldApplied] ### RemoveDisabledArchive ``` -Set-Mailbox [-Identity] [-RemoveDisabledArchive] +Set-Mailbox [-Identity] + [-RemoveDisabledArchive] [-AcceptMessagesOnlyFrom ] [-AcceptMessagesOnlyFromDLMembers ] [-AcceptMessagesOnlyFromSendersOrMembers ] @@ -830,6 +880,7 @@ Set-Mailbox [-Identity] [-RemoveDisabledArchive] [-BypassModerationFromSendersOrMembers ] [-CalendarRepairDisabled ] [-CalendarVersionStoreDisabled ] + [-ClearThrottlingPolicyAssignment] [-Confirm] [-CreateDTMFMap ] [-CustomAttribute1 ] @@ -853,9 +904,11 @@ Set-Mailbox [-Identity] [-RemoveDisabledArchive] [-DeliverToMailboxAndForward ] [-DisplayName ] [-ElcProcessingDisabled ] + [-EmailAddressDisplayNames ] [-EmailAddresses ] [-EnableRoomMailboxAccount ] [-EndDateForRetentionHold ] + [-EnforcedTimestamps ] [-ExtensionCustomAttribute1 ] [-ExtensionCustomAttribute2 ] [-ExtensionCustomAttribute3 ] @@ -886,11 +939,13 @@ Set-Mailbox [-Identity] [-RemoveDisabledArchive] [-MaxSendSize ] [-MessageCopyForSendOnBehalfEnabled ] [-MessageCopyForSentAsEnabled ] + [-MessageCopyForSMTPClientSubmissionEnabled ] [-MessageTrackingReadStatusEnabled ] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-Name ] + [-NonCompliantDevices ] [-Office ] [-Password ] [-ProhibitSendQuota ] @@ -901,6 +956,7 @@ Set-Mailbox [-Identity] [-RemoveDisabledArchive] [-RejectMessagesFrom ] [-RejectMessagesFromDLMembers ] [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] [-RequireSenderAuthenticationEnabled ] [-ResourceCapacity ] [-ResourceCustom ] @@ -912,6 +968,7 @@ Set-Mailbox [-Identity] [-RemoveDisabledArchive] [-RoleAssignmentPolicy ] [-RoomMailboxPassword ] [-RulesQuota ] + [-SchedulerAssistant ] [-SecondaryAddress ] [-SecondaryDialPlan ] [-SendModerationNotifications ] @@ -923,17 +980,20 @@ Set-Mailbox [-Identity] [-RemoveDisabledArchive] [-StsRefreshTokensValidFrom ] [-Type ] [-UMDtmfMap ] + [-UpdateEnforcedTimestamp] [-UseDatabaseQuotaDefaults ] [-UseDatabaseRetentionDefaults ] [-UserCertificate ] [-UserSMimeCertificate ] [-WhatIf] - [-WindowsEmailAddress ] [] + [-WindowsEmailAddress ] + [] ``` ### RemoveOrphanedHolds ``` -Set-Mailbox [-Identity] [-RemoveOrphanedHolds ] +Set-Mailbox [-Identity] + [-RemoveOrphanedHolds ] [-AcceptMessagesOnlyFrom ] [-AcceptMessagesOnlyFromDLMembers ] [-AcceptMessagesOnlyFromSendersOrMembers ] @@ -950,6 +1010,7 @@ Set-Mailbox [-Identity] [-RemoveOrphanedHolds ] [-BypassModerationFromSendersOrMembers ] [-CalendarRepairDisabled ] [-CalendarVersionStoreDisabled ] + [-ClearThrottlingPolicyAssignment] [-Confirm] [-CreateDTMFMap ] [-CustomAttribute1 ] @@ -967,15 +1028,17 @@ Set-Mailbox [-Identity] [-RemoveOrphanedHolds ] [-CustomAttribute7 ] [-CustomAttribute8 ] [-CustomAttribute9 ] - [-DataEncryptionPolicy + [-DataEncryptionPolicy ] [-DefaultAuditSet ] [-DefaultPublicFolderMailbox ] [-DeliverToMailboxAndForward ] [-DisplayName ] [-ElcProcessingDisabled ] + [-EmailAddressDisplayNames ] [-EmailAddresses ] [-EnableRoomMailboxAccount ] [-EndDateForRetentionHold ] + [-EnforcedTimestamps ] [-ExtensionCustomAttribute1 ] [-ExtensionCustomAttribute2 ] [-ExtensionCustomAttribute3 ] @@ -1006,11 +1069,14 @@ Set-Mailbox [-Identity] [-RemoveOrphanedHolds ] [-MaxSendSize ] [-MessageCopyForSendOnBehalfEnabled ] [-MessageCopyForSentAsEnabled ] + [-MessageCopyForSMTPClientSubmissionEnabled ] + [-MessageRecallProcessingEnabled ] [-MessageTrackingReadStatusEnabled ] [-MicrosoftOnlineServicesID ] [-ModeratedBy ] [-ModerationEnabled ] [-Name ] + [-NonCompliantDevices ] [-Office ] [-Password ] [-ProhibitSendQuota ] @@ -1021,6 +1087,7 @@ Set-Mailbox [-Identity] [-RemoveOrphanedHolds ] [-RejectMessagesFrom ] [-RejectMessagesFromDLMembers ] [-RejectMessagesFromSendersOrMembers ] + [-RemoveMailboxProvisioningConstraint] [-RequireSenderAuthenticationEnabled ] [-ResourceCapacity ] [-ResourceCustom ] @@ -1032,6 +1099,7 @@ Set-Mailbox [-Identity] [-RemoveOrphanedHolds ] [-RoleAssignmentPolicy ] [-RoomMailboxPassword ] [-RulesQuota ] + [-SchedulerAssistant ] [-SecondaryAddress ] [-SecondaryDialPlan ] [-SendModerationNotifications ] @@ -1043,17 +1111,19 @@ Set-Mailbox [-Identity] [-RemoveOrphanedHolds ] [-StsRefreshTokensValidFrom ] [-Type ] [-UMDtmfMap ] + [-UpdateEnforcedTimestamp] [-UseDatabaseQuotaDefaults ] [-UserCertificate ] [-UserSMimeCertificate ] [-WhatIf] - [-WindowsEmailAddress ] [] + [-WindowsEmailAddress ] + [] ``` ## DESCRIPTION You can use this cmdlet for one mailbox at a time. To perform bulk management, you can pipeline the output of various Get- cmdlets (for example, the Get-Mailbox or Get-User cmdlets) and configure several mailboxes in a single-line command. You can also use the Set-Mailbox cmdlet in scripts. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -1087,14 +1157,18 @@ This example sets the MailTip translation in French and Chinese. ### Example 5 ```powershell -$password = Read-Host "Enter password" -AsSecureString; Set-Mailbox florencef -Password $password -ResetPasswordOnNextLogon $true +$password = Read-Host "Enter password" -AsSecureString + +Set-Mailbox florencef -Password $password -ResetPasswordOnNextLogon $true ``` In on-premises Exchange, this example resets the password for Florence Flipo's mailbox. The next time she signs in to her mailbox, she'll have to change her password. ### Example 6 ```powershell -Set-Mailbox -Arbitration -Identity "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}" -MessageTracking $false; Set-Mailbox -Arbitration -Identity "SystemMailbox{1f05a927-b864-48a7-984d-95b1adfbfe2d}" -MessageTracking $true +Set-Mailbox -Arbitration -Identity "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}" -MessageTracking $false + +Set-Mailbox -Arbitration -Identity "SystemMailbox{1f05a927-b864-48a7-984d-95b1adfbfe2d}" -MessageTracking $true ``` This example removes the message tracking organization capability from the arbitration mailbox named SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} and assigns it to an arbitration mailbox named SystemMailbox{1f05a927-b864-48a7-984d-95b1adfbfe2d}. @@ -1111,7 +1185,7 @@ This example adds a secondary email address to John's mailbox. Set-Mailbox -Identity asraf@contoso.com -RemoveDelayReleaseHoldApplied ``` -In Exchange Online, this example removes the delay hold that's applied to Asraf's mailbox so an offboarding migration (that is, a mailbox migration from Exchange Online back to on-premises Exchange) can continue successfully. For more information about delay holds, see [Managing mailboxes on delay hold](https://docs.microsoft.com/microsoft-365/compliance/identify-a-hold-on-an-exchange-online-mailbox#managing-mailboxes-on-delay-hold). +In Exchange Online, this example removes the delay hold that's applied to Asraf's mailbox so an offboarding migration (that is, a mailbox migration from Exchange Online back to on-premises Exchange) can continue successfully. For more information about delay holds, see [Managing mailboxes on delay hold](https://learn.microsoft.com/purview/ediscovery-identify-a-hold-on-an-exchange-online-mailbox#managing-mailboxes-on-delay-hold). ## PARAMETERS @@ -1119,30 +1193,21 @@ In Exchange Online, this example removes the delay hold that's applied to Asraf' The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -1157,20 +1222,15 @@ The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages t 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -1195,20 +1255,15 @@ The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send m 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -1235,18 +1290,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. @@ -1268,19 +1318,18 @@ Accept wildcard characters: False ``` ### -AccountDisabled -This parameter is available only in the cloud-based service. +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: - $true: The associated account is disabled. The user can't log in to the mailbox. - - $false: The associated account is enabled. The user can log in to the mailbox. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1293,12 +1342,10 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID -For more information about address book policies, see [Address book policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies). +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) or [Address book policies in Exchange Online](https://learn.microsoft.com/exchange/address-books/address-book-policies/address-book-policies). ```yaml Type: AddressBookMailboxPolicyIdParameter @@ -1314,16 +1361,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\@\). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -1349,7 +1400,6 @@ 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: - $true: Anti-spam processing is skipped on the mailbox. - - $false: Anti-spam processing occurs on the mailbox. This is the default value ```yaml @@ -1366,7 +1416,9 @@ Accept wildcard characters: False ``` ### -ApplyMandatoryProperties -The ApplyMandatoryProperties switch specifies whether to update the msExchVersion attribute of the mailbox. You may need to use this switch to fix inaccessible mailboxes or mailboxes that were created in previous versions of Exchange. You don't need to specify a value with this switch. +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. ```yaml Type: SwitchParameter @@ -1409,23 +1461,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -1447,9 +1490,7 @@ 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: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -1486,9 +1527,17 @@ Accept wildcard characters: False ``` ### -ArchiveName -The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook and Outlook Web App. +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: + +- Exchange 2016 or later: `In-Place Archive -` +- Exchange 2013: `In-Place Archive - ` +- Exchange 2010: `Personal Archive - ` + +In Exchange Online, the default value is `In-Place Archive -`. -If you don't use this parameter, the default value is In-Place Archive - \. +In Outlook in Exchange Online, the value of this parameter is ignored. The name of the archive mailbox that's shown in the folder list is `Online Archive - `. ```yaml Type: MultiValuedProperty @@ -1511,13 +1560,9 @@ The ArchiveQuota parameter specifies the maximum size for the user's archive mai 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1538,13 +1583,15 @@ Accept wildcard characters: False ``` ### -ArchiveStatus +This cmdlet is available only in on-premises Exchange. + This parameter is reserved for internal Microsoft use. ```yaml Type: ArchiveStatusFlags Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1561,13 +1608,9 @@ The ArchiveWarningQuota parameter specifies the warning threshold for the size o 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1597,6 +1640,8 @@ Type: SetMailbox+ClearableADAttributes[] Parameter Sets: Identity Aliases: Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False Position: Named Default value: None Accept pipeline input: False @@ -1607,48 +1652,29 @@ Accept wildcard characters: False The AuditAdmin parameter specifies the mailbox operations to log for administrators as part of mailbox audit logging. Valid values are: - None - - AddFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - ApplyRecord (Available only in the cloud-based service.) - - Copy - - Create (Enabled by default.) - - FolderBind (Enabled by default in on-premises Exchange 2010 or later.) - - HardDelete (Enabled by default.) - - MessageBind (This has been deprecated in the cloud-based service.) - - ModifyFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - Move (Enabled by default in on-premises Exchange 2010 or later.) - - MoveToDeletedItems (Enabled by default.) - - RecordDelete (Available only in the cloud-based service.) - - RemoveFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - SendAs (Enabled by default.) - - SendOnBehalf (Enabled by default.) - - SoftDelete (Enabled by default.) - - Update (Enabled by default.) - - UpdateFolderPermissions (Available only in Exchange 2019 and the cloud-based service; enabled by default.) - - UpdateCalendarDelegation (Available only in Exchange 2019 and the cloud-based service; enabled by default.) - - UpdateInboxRules (Available only in Exchange 2019 and the cloud-based service; enabled by default.) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The AuditEnabled parameter must be set to $true to enable mailbox audit logging. @@ -1669,44 +1695,26 @@ Accept wildcard characters: False The AuditDelegate parameter specifies the mailbox operations to log for delegate users as part of mailbox audit logging. Valid values are: - None - - AddFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - ApplyRecord (Available only in the cloud-based service.) - - Create (Enabled by default.) - - FolderBind - - HardDelete (Enabled by default.) - - ModifyFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - Move - - MoveToDeletedItems (Enabled by default only in the cloud-based service.) - - RecordDelete (Available only in the cloud-based service.) - - RemoveFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - SendAs (Enabled by default.) - - SendOnBehalf (Enabled by default only in the cloud-based service.) - - SoftDelete (Enabled by default only in the cloud-based service.) - - Update (Enabled by default only in the cloud-based service.) - -- UpdateCalendarDelegation (Available only in the cloud-based service.) - - UpdateFolderPermissions (Available only in Exchange 2019 and the cloud-based service; enabled by default.) - - UpdateInboxRules (Available only in Exchange 2019 and the cloud-based service; enabled by default.) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The AuditEnabled parameter must be set to $true to enable mailbox audit logging. @@ -1727,10 +1735,9 @@ Accept wildcard characters: False 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. - - $false: Mailbox audit logging is disabled. This is the default value. -**Note**: In Exchange Online, mailbox auditing on by default was enabled for all organizations in January, 2019. For more information, see [Manage mailbox auditing](https://docs.microsoft.com/microsoft-365/compliance/enable-mailbox-auditing). +**Note**: In Exchange Online, mailbox auditing on by default was enabled for all organizations in January, 2019. For more information, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). ```yaml Type: Boolean @@ -1758,7 +1765,7 @@ To modify other types of arbitration mailboxes, don't use this switch. Instead, Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1791,44 +1798,27 @@ Accept wildcard characters: False 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.) - - AddFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - ApplyRecord (Available only in the cloud-based service.) - - Create - - FolderBind (Available only in Exchange 2013.) - - HardDelete (Enabled by default in the cloud-based service.) - - MailboxLogin (Available only in Exchange 2016, Exchange 2019, and the cloud-based service.) - - MessageBind (Available only in Exchange 2013.) - - ModifyFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - Move - - MoveToDeletedItems (Enabled by default in the cloud-based service.) - - RecordDelete (Available only in the cloud-based service.) - - RemoveFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - - SoftDelete (Enabled by default in the cloud-based service.) - - Update (Enabled by default in the cloud-based service.) - - UpdateFolderPermissions (Available only in the cloud-based service; enabled by default.) - - UpdateCalendarDelegation (Available only in the cloud-based service; enabled by default.) - - UpdateInboxRules (Available only in the cloud-based service; enabled by default.) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The AuditEnabled parameter must be set to $true to enable mailbox audit logging. @@ -1873,20 +1863,15 @@ The BypassModerationFromSendersOrMembers parameter specifies who is allowed to s To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +To enter multiple senders and overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more senders without affecting any existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. @@ -1913,20 +1898,16 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the RecoverableItemsQuota parameter. -When the UseDatabaseQuotaDefaults parameter is set to the value $true, the value of the this parameter is ignored, and the mailbox uses the CalendarLoggingQuota value on the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. +When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the CalendarLoggingQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. ```yaml Type: Unlimited @@ -1945,7 +1926,6 @@ Accept wildcard characters: False 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. - - $false: The Calendar Repair Assistant repairs calendars items in the mailbox. This is the default value. ```yaml @@ -1965,7 +1945,6 @@ Accept wildcard characters: False 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. - - $false: Changes to a calendar item are recorded. This keeps older versions of meetings and appointments. This is the default value. ```yaml @@ -1981,6 +1960,26 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ClearThrottlingPolicyAssignment +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. + +Admins can contact Microsoft Support to assign a throttling policy to a mailbox, which changes the default throttling limits for various protocols. To revert those changes, use this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ClientExtensions This parameter is available only in on-premises Exchange. @@ -2004,15 +2003,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2022,17 +2020,18 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap +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: - $true: A DTMF map is created for the recipient. This is the default value. - - $false: A DTMF map isn't created for the recipient. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2287,9 +2286,7 @@ 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: - Name - - Distinguished name (DN) - - GUID Use the Get-MailboxDatabase cmdlet to see the available mailbox databases. @@ -2313,9 +2310,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can use the Get-DataEncryptionPolicy cmdlet to view the available policies. @@ -2339,12 +2334,10 @@ 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: - Admin: Reverts the mailbox operations to log for administrators back to the default list of operations. - - Delegate: Reverts the mailbox operations to log for delegate users back to the default list of operations. - - Owner: Reverts the mailbox operations to log for mailbox owners back to the default list of operations. -With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, who will automatically add new operations to be audited when they are released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft will not be audited; you'll need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://docs.microsoft.com/microsoft-365/compliance/enable-mailbox-auditing). +With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, who will automatically add new operations to be audited when they are released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft will not be audited; you'll need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). ```yaml Type: MultiValuedProperty @@ -2363,15 +2356,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID By default, the public folder mailbox used by a user is automatically selected by an algorithm that load-balances users across all public folder mailboxes. @@ -2393,7 +2381,6 @@ Accept wildcard characters: False 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. - - $false: If a forwarding recipient or email address is configured, messages are delivered only to the specified recipient or email address, and messages aren't delivered to this mailbox. If no forwarding recipient or email address is configured, messages are delivered only to this mailbox. The default value is $false. The value of this parameter is meaningful only if you configure a forwarding recipient or email address. @@ -2417,7 +2404,6 @@ This parameter is available only in on-premises Exchange. The DisableThrottling parameter enables or disables sender rate throttling for the mailbox. Valid values are: - $true: Messages sent by this mailbox will not be throttled by Sender Rate Control. We only recommend this value for moderation mailboxes. - - $false: Messages will be throttled after the threshold is exceeded. This is the default value. ```yaml @@ -2473,7 +2459,6 @@ 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: - $true: High priority messages sent to X.400 recipients are changed to normal priority. - - $false: High priority messages set to X.400 recipients remain high priority. This is the default value. ```yaml @@ -2494,7 +2479,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List DumpsterMessagesPerFolderCountReceiveQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List DumpsterMessagesPerFolderCountReceiveQuota`. ```yaml Type: Int32 @@ -2514,7 +2499,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List DumpsterMessagesPerFolderCountWarningQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List DumpsterMessagesPerFolderCountWarningQuota`. ```yaml Type: Int32 @@ -2535,7 +2520,6 @@ 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: - $true: The Managed Folder Assistant isn't allowed to process the mailbox. Note that this setting will be ignored if a retention policy that has Preservation Lock enabled is applied to the mailbox. - - $false: The Managed Folder Assistant is allowed to process the mailbox. This is the default value. ```yaml @@ -2551,34 +2535,47 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EmailAddressDisplayNames +This parameter is available only in the cloud-based service. + +{{ Fill EmailAddressDisplayNames Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). +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 \:\,\:\,...\:\. The optional \ value specifies the type of email address. Some examples of valid values include: +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: - SMTP: The primary SMTP address. You can use this value only once in a command. - - smtp: Other SMTP email addresses. - - X400: X.400 addresses in on-premises Exchange. - - X500: X.500 addresses in on-premises Exchange. -If you don't include a \ value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. To specify the primary SMTP email address, you can use any of the following methods: -- Use the \ value SMTP on the address. - -- The first email address when you don't use any \ values, or when you use multiple \ values of smtp. - +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. - Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\:\","\:\",..."\:\". +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\:\","\:\",...; Remove="\:\","\:\",...}. +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. ```yaml Type: ProxyAddressCollection @@ -2599,7 +2596,6 @@ 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: - $true: Email address policies are applied to this recipient. This is the default value. - - $false: Email address policies aren't applied to this recipient. ```yaml @@ -2616,17 +2612,16 @@ Accept wildcard characters: False ``` ### -EnableRoomMailboxAccount -The EnableRoomMailboxAccount parameter specifies whether to enable the disabled user account that's associated with this room mailbox. Valid values are: +This parameter is functional only in on-premises Exchange. -- $true: The disabled account that's associated with the room mailbox is enabled. You also need to use the RoomMailboxPassword with this value. This allows the account to log on to the room mailbox. - -- $false: The account that's associated with the room mailbox is disabled. You can't use the account to logon to the room mailbox. This is the default value. +The EnableRoomMailboxAccount parameter specifies whether to enable the disabled user account that's associated with this room mailbox. Valid values are: -Typically, the account that's associated with a room mailbox is disabled. However, you need to enable the account for features like the Skype for Business Room System or Microsoft Teams Rooms. +- $true: The disabled account that's associated with the room mailbox is enabled. You also need to use the RoomMailboxPassword with this value. The account is able to log in and access the room mailbox or other resources. +- $false: The account that's associated with the room mailbox is disabled. The account is not able to log in and access the room mailbox or other resources. In on-premises Exchange, this is the default value. -In Exchange Online, a room mailbox with an associated enabled account doesn't require a license. +You need to enable the account for features like the Skype for Business Room System or Microsoft Teams Rooms. -In an on-premises Exchange organization, you also need to enable the corresponding user account in Active Directory Users and Computers or by running the Enable-ADAccount cmdlet in Windows PowerShell. +A room mailbox in Exchange Online is created with associated an account that has a random, unknown password. This account is active and visible in Microsoft Graph PowerShell and the Microsoft 365 admin center just like a regular user account, but it consumes no licenses. To prevent this account from being able to log in after you create the mailbox, use the AccountEnabled parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. ```yaml Type: Boolean @@ -2644,7 +2639,9 @@ Accept wildcard characters: False ### -EndDateForRetentionHold 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. -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". +**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. + +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". ```yaml Type: DateTime @@ -2659,10 +2656,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnforcedTimestamps +This parameter is available only in the cloud-based service. + +{{ Fill EnforcedTimestamps Description }} + +```yaml +Type: String +Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ExcludeFromAllOrgHolds This parameter is available only in Exchange Online. -The ExcludeFromAllOrgHolds switch excludes the mailbox from all organization-wide Office 365 retention policies. This switch can only be used for inactive mailboxes. You don't need to specify a value with this switch. +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. When you use this switch, use the DistinguishedName or ExchangeGuid property value for the identity of the inactive mailbox (those are the only values that guarantee uniqueness). @@ -2670,7 +2685,7 @@ When you use this switch, use the DistinguishedName or ExchangeGuid property val Type: SwitchParameter Parameter Sets: ExcludeFromAllOrgHolds Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2682,7 +2697,7 @@ Accept wildcard characters: False ### -ExcludeFromOrgHolds This parameter is available only in Exchange Online. -The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Office 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 Office 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Office 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Note that retention policies assigned to mailboxes are prefaced by 'mbx'. +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'. You can specify multiple values by using the syntax: "GUID1","GUID2",..."GUIDX". @@ -2692,7 +2707,7 @@ When you use this parameter, use the DistinguishedName or ExchangeGuid property Type: String[] Parameter Sets: ExcludeFromOrgHolds Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2722,9 +2737,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute1 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -2744,9 +2759,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute2 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -2766,9 +2781,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute3 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -2788,9 +2803,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute4 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -2810,9 +2825,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute5 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: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -2833,7 +2848,6 @@ Accept wildcard characters: False 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. - - InternalOnly: Automatic replies can be configured only for internal senders. ```yaml @@ -2854,7 +2868,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List FolderHierarchyChildrenCountReceiveQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyChildrenCountReceiveQuota`. ```yaml Type: Int32 @@ -2874,7 +2888,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List FolderHierarchyChildrenCountWarningQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyChildrenCountWarningQuota`. ```yaml Type: Int32 @@ -2894,7 +2908,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List FolderHierarchyDepthReceiveQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyDepthReceiveQuota`. ```yaml Type: Int32 @@ -2914,7 +2928,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List FolderHierarchyDepthWarningQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyDepthWarningQuota`. ```yaml Type: Int32 @@ -2934,7 +2948,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List FoldersCountReceiveQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FoldersCountReceiveQuota`. ```yaml Type: Int32 @@ -2954,7 +2968,7 @@ 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. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List FoldersCountReceiveQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FoldersCountReceiveQuota`. ```yaml Type: Int32 @@ -2970,7 +2984,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -2989,21 +3005,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID How messages are delivered and forwarded is controlled by the DeliverToMailboxAndForward parameter. - DeliverToMailboxAndForward is $true: Messages are delivered to this mailbox and forwarded to the specified recipient. - - DeliverToMailboxAndForward is $false: Messages are only forwarded to the specified recipient. Messages aren't delivered to this mailbox. The default value is blank ($null), which means no forwarding recipient is configured. @@ -3029,7 +3039,6 @@ The ForwardingSmtpAddress parameter specifies a forwarding SMTP address for mess How messages are delivered and forwarded is controlled by the DeliverToMailboxAndForward parameter. - DeliverToMailboxAndForward is $true: Messages are delivered to this mailbox and forwarded to the specified email address. - - DeliverToMailboxAndForward is $false: Messages are only forwarded to the specified email address. Messages aren't delivered to this mailbox. The default value is blank ($null), which means no forwarding email address is configured. @@ -3070,33 +3079,24 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo -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 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. By default, this parameter is blank, which means no one else has permission to send on behalf of this mailbox. @@ -3116,35 +3116,13 @@ Accept wildcard characters: False ### -GroupMailbox This parameter is available only in the cloud-based service. -The GroupMailbox switch is required to modify Group Mailboxes in Exchange Online. You don't need to specify a value with this switch. - -You can use any value that uniquely identifies the Group Mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \\\\ - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) +The GroupMailbox switch is required to modify Microsoft 365 Groups. You don't need to specify a value with this switch. ```yaml Type: MailboxIdParameter Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3157,7 +3135,6 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. - - $false: The recipient is visible in address lists. This is the default value. ```yaml @@ -3176,12 +3153,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -3198,15 +3174,16 @@ Accept wildcard characters: False ``` ### -ImListMigrationCompleted +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. Valid values are: - $true: The user's Lync or Skype for Business contact list is stored in their Exchange 2016 mailbox. This prevents you from migrating the mailbox back to an Exchange 2010 server. - - $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This is the default value. -Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://go.microsoft.com/fwlink/p/?LinkID=313550). +Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://learn.microsoft.com/lyncserver/lync-server-2013-configuring-lync-server-to-use-the-unified-contact-store). If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list has been moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false. @@ -3214,7 +3191,7 @@ 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, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3248,7 +3225,7 @@ The InactiveMailbox switch specifies that the mailbox is an inactive mailbox. Yo An inactive mailbox is a mailbox that's placed on Litigation Hold or In-Place Hold before it's soft-deleted. -To find inactive mailboxes, run the command Get-Mailbox -InactiveMailboxOnly | FL Name,PrimarySmtpAddress,DistinguishedName,ExchangeGuid and then use the DistinguishedName or ExchangeGuid property values for the Identity parameter (values guaranteed to be unique). +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 for the Identity parameter (values guaranteed to be unique). This switch is required to use the LitigationHoldEnabled and LitigationHoldDuration parameters on inactive mailboxes. @@ -3258,7 +3235,7 @@ 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 +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3327,22 +3304,18 @@ The IssueWarningQuota parameter specifies the warning threshold for the size of 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -In Office 365, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Office 365, you can't use this parameter on public folder mailboxes. +In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. -In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter is set to $true, the value of the this parameter is ignored, and the mailbox uses the IssueWarningQuota value on the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. +In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to $true (the default value), the value of the this parameter is ignored, and the mailbox uses the IssueWarningQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. ```yaml Type: Unlimited @@ -3378,11 +3351,11 @@ Accept wildcard characters: False ### -Languages 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://go.microsoft.com/fwlink/p/?linkId=184859). +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). -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -3402,7 +3375,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -3441,11 +3414,8 @@ 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: - Name - - Distinguished name (DN) - - Canonical DN - - GUID ```yaml @@ -3488,7 +3458,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3501,7 +3471,6 @@ Accept wildcard characters: False The LitigationHoldEnabled parameter specifies whether to place the mailbox on litigation hold. Valid values are: - $true: The mailbox is on litigation hold. - - $false: The mailbox isn't on litigation hold. This is the default value. After a mailbox is placed on litigation hold, messages can't be deleted from the mailbox. Deleted items and all versions of changed items are retained in the Recoverable Items folder. Items that are purged from the dumpster are also retained and the items are held indefinitely. If you enable litigation hold, single-item recovery quotas aren't applied. @@ -3512,7 +3481,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3528,7 +3497,7 @@ The LitigationHoldOwner parameter specifies the user who placed the mailbox on l Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3538,19 +3507,19 @@ Accept wildcard characters: False ``` ### -MailboxMessagesPerFolderCountReceiveQuota -This parameter is a available only in on-premises Exchange. +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. The MailboxMessagesPerFolderCountReceiveQuota value must be greater than or equal to the MailboxMessagesPerFolderCountWarningQuota value. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List MailboxMessagesPerFolderCountReceiveQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List MailboxMessagesPerFolderCountReceiveQuota`. ```yaml Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3560,19 +3529,19 @@ Accept wildcard characters: False ``` ### -MailboxMessagesPerFolderCountWarningQuota -This parameter is a available only in on-premises Exchange. +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. The MailboxMessagesPerFolderCountReceiveQuota value must be greater than or equal to the MailboxMessagesPerFolderCountWarningQuota value. -To see the current value of this property, run the command Get-MailboxStatistics \ | Format-List MailboxMessagesPerFolderCountWarningQuota +To see the current value of this property, run the command `Get-MailboxStatistics | Format-List MailboxMessagesPerFolderCountWarningQuota`. ```yaml Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3584,7 +3553,11 @@ Accept wildcard characters: False ### -MailboxRegion This parameter is available only in the cloud-based service. -This parameter is reserved for internal Microsoft use. +The MailboxRegion parameter specifies the geo location for the mailbox in multi-geo environments. + +To see the list of configured geo locations in Microsoft 365 Multi-Geo, run the following command: `Get-OrganizationConfig | Select -ExpandProperty AllowedMailboxRegions | Format-Table`. To view your central geo location, run the following command: `Get-OrganizationConfig | Select DefaultMailboxRegion`. + + For more information, see [Administering Exchange Online mailboxes in a multi-geo environment](https://learn.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo). ```yaml Type: String @@ -3604,9 +3577,8 @@ The MailTip parameter specifies the custom MailTip text for this recipient. The When you add a MailTip to a recipient, two things happen: -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \\This mailbox is not monitored\\. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `This mailbox is not monitored`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. ```yaml Type: String @@ -3626,11 +3598,11 @@ The MailTipTranslations parameter specifies additional languages for the custom To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: -@{Add="\:\","\:\"...; Remove="\:\","\:\"...} +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. -\ is a valid ISO 639 two-letter culture code that's associated with the language. +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. ```yaml Type: MultiValuedProperty @@ -3646,7 +3618,7 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicy -This parameter is available or functional only in 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. @@ -3664,9 +3636,11 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicyAllowed -This parameter is available or functional only in 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. -The ManagedFolderMailboxPolicyAllowed parameter bypasses the warning that MRM features aren't supported for clients running versions of Outlook earlier than Outlook 2007. When a managed folder mailbox policy is assigned to a mailbox by using the ManagedFolderMailboxPolicy parameter, the warning appears by default unless the ManagedFolderMailboxPolicyAllowed parameter is used. +When a managed folder mailbox policy is assigned to a mailbox by using the ManagedFolderMailboxPolicy parameter, the warning appears by default unless you also use the ManagedFolderMailboxPolicyAllowed switch. Although Outlook 2003 Service Pack 3 clients are supported, they have limited MRM functionality. @@ -3722,37 +3696,32 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize -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 mailbox. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. -In Office 365, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. +In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. -In Office 365, you use this parameter to configure the MaxReceiveSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxReceiveSize value for all new mailboxes that you create in the future. +In Exchange Online, you use this parameter to configure the MaxReceiveSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxReceiveSize value for all new mailboxes that you create in the future. In on-premises Exchange, the default value unlimited indicates the maximum receive size for the mailbox is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3785,24 +3754,21 @@ The MaxSendSize parameter specifies the maximum size of a message that can be se When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. -In Office 365, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. +In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. -In Office 365, you use this parameter to configure the MaxSendSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxSendSize value for all new mailboxes that you create in the future. +In Exchange Online, you use this parameter to configure the MaxSendSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxSendSize value for all new mailboxes that you create in the future. In on-premises Exchange, the default value unlimited indicates the maximum send size for the mailbox is imposed elsewhere (for example, organization, server, or connector limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -3823,7 +3789,6 @@ Accept wildcard characters: False 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: - $true: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message is sent to the sender's mailbox. - - $false: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value. You give users permission to send on behalf of a mailbox by using the GrantSendOnBehalfTo parameter on the mailbox. @@ -3847,7 +3812,6 @@ Accept wildcard characters: False 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: - $true: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message is sent to the sender's mailbox. - - $false: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value. In Exchange Online, you give a user permission to send as a mailbox by running this command: `Add-RecipientPermission -AccessRights SendAs -Trustee `. @@ -3867,6 +3831,27 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MessageCopyForSMTPClientSubmissionEnabled +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: + +- $true: When the user's account sends messages using SMTP AUTH, a copy of the message is sent to the users's mailbox. This is the default value. +- $false: When the user's account sends messages using SMTP AUTH, a copy of the message isn't sent to the users's mailbox. + +```yaml +Type: Boolean +Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MessageTracking This parameter is available only in on-premises Exchange. @@ -3891,7 +3876,6 @@ Accept wildcard characters: False 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. - - $false: The read status of the message isn't displayed in the delivery report for messages sent to this mailbox. Only the date-time that the message was delivered is shown in the delivery report. ```yaml @@ -3947,20 +3931,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -3981,7 +3960,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -4002,6 +3980,8 @@ Accept wildcard characters: False ### -Name 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). + ```yaml Type: String Parameter Sets: (All) @@ -4020,7 +4000,11 @@ 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. -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. ```yaml Type: SecureString @@ -4035,6 +4019,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -NonCompliantDevices +This parameter is available only in the cloud-based service. + +{{ Fill NonCompliantDevices Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -OABGen This parameter is available only in on-premises Exchange. @@ -4077,9 +4079,7 @@ 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: - Name - - Distinguished name (DN) - - GUID Use the Get-OfflineAddressBook cmdlet to see the available offline address books. @@ -4102,7 +4102,11 @@ 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. -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. ```yaml Type: SecureString @@ -4154,13 +4158,16 @@ Accept wildcard characters: False ``` ### -Password -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, you need to be a member of one of the following role groups: +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: -- Office 365: You can't use this parameter to change another user's password. To change another user's password, use the Set-MsolUserPassword cmdlet in Office 365 (Azure AD) PowerShell. For connection instructions, see [Connect to Office 365 PowerShell](https://go.microsoft.com/fwlink/p/?LinkId=614839). To change a another user's password in the Microsoft 365 admin center, see [Reset Office 365 business passwords](https://go.microsoft.com/fwlink/p/?LinkId=614837). +- 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. +- On-premises Exchange: You need the User Options or Reset Password role. The User Options role is assigned to the Organization Management or Help Desk role groups. The Reset Password role it isn't assigned to any role groups by default. -- On-premises Exchange: The Organization Management or Help Desk role groups via the User Options role. The Reset Password role also allows you to use this parameter, but it isn't assigned to any role groups by default. +You can use the following methods as a value for this parameter: -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. ```yaml Type: SecureString @@ -4180,7 +4187,7 @@ 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. -If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, but that means the email addresses of the mail user no longer automatically updated by email address policies. +If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, but the email addresses of the mailbox are no longer automatically updated by email address policies. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. @@ -4203,22 +4210,18 @@ The ProhibitSendQuota parameter specifies a size limit for the mailbox. If the m 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -In Office 365, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Office 365, you can't use this parameter on public folder mailboxes. +In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. -In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter is set to the value $true, the value of the this parameter is ignored, and the mailbox uses the ProhibitSendQuota value on the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. +In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the ProhibitSendQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. ```yaml Type: Unlimited @@ -4239,22 +4242,18 @@ The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. I 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. -In Office 365, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, but you can't exceed the maximum value that's allowed by the subscription or license. In Office 365, you can't use this parameter on public folder mailboxes. +In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. -In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter is set to the value $true, the value of the this parameter is ignored, and the mailbox uses the ProhibitSendReceiveQuota value on the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. +In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the ProhibitSendReceiveQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. ```yaml Type: Unlimited @@ -4354,7 +4353,7 @@ You use this switch with the InactiveMailbox switch and the Identity parameter ( Type: SwitchParameter Parameter Sets: RecalculateInactiveMailbox Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -4368,7 +4367,7 @@ The RecipientLimits parameter specifies the maximum number of recipients allowed 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). -In the cloud-based service, a valid value is an integer from 1 to 1000. +In the cloud-based service, a valid value is an integer from 1 to 1000. The default value is 500. This value does not apply to meeting messages. ```yaml Type: Unlimited @@ -4393,20 +4392,16 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t When you enter a number, you can qualify it with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. -When the UseDatabaseQuotaDefaults parameter is set to the value $true, the value of the this parameter is ignored, and the mailbox uses the RecoverableItemsQuota value on the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. +When the UseDatabaseQuotaDefaults parameter is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the RecoverableItemsQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. ```yaml Type: Unlimited @@ -4431,20 +4426,16 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t When you enter a number, you can qualify it with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value. -When the UseDatabaseQuotaDefaults parameter is set to the value $true, the value of the this parameter is ignored, and the mailbox uses the RecoverableItemsWarningQuota value on the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. +When the UseDatabaseQuotaDefaults parameter is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the RecoverableItemsWarningQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. ```yaml Type: Unlimited @@ -4465,20 +4456,15 @@ The RejectMessagesFrom parameter specifies who isn't allowed to send messages to 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -4503,20 +4489,15 @@ The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send me 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -4543,18 +4524,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. @@ -4598,16 +4574,16 @@ 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. -The removal of a hold from a mailbox is temporarily delayed to prevent the accidental purge of content that's no longer affected by the hold. This temporary delay in the removal of the hold is known as a delay hold. To see the hold history on a mailbox, replace \ with the name, email address, or alias of the mailbox, and run this command: Export-MailboxDiagnosticLogs -Identity \ -ComponentName HoldTracking. +The removal of a hold from a mailbox is temporarily delayed to prevent the accidental purge of content that's no longer affected by the hold. This temporary delay in the removal of the hold is known as a delay hold. To see the hold history on a mailbox, replace `` with the name, email address, or alias of the mailbox, and run this command: `Export-MailboxDiagnosticLogs -Identity -ComponentName HoldTracking`. You can use this switch with the GroupMailbox or InactiveMailbox switch to remove delay holds from group mailboxes or inactive mailboxes. -For more information, see [Managing mailboxes on delay hold](https://docs.microsoft.com/microsoft-365/compliance/identify-a-hold-on-an-exchange-online-mailbox#managing-mailboxes-on-delay-hold). +For more information, see [Managing mailboxes on delay hold](https://learn.microsoft.com/purview/ediscovery-identify-a-hold-on-an-exchange-online-mailbox#managing-mailboxes-on-delay-hold). ```yaml Type: SwitchParameter Parameter Sets: RemoveDelayHoldApplied Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -4619,19 +4595,19 @@ Accept wildcard characters: False ### -RemoveDelayReleaseHoldApplied 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 Yammer) 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. +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. -The removal of a hold from a mailbox is temporarily delayed to prevent the accidental purge of content that's no longer affected by the hold. This temporary delay in the removal of the hold is known as a delay hold. To see the hold history on a mailbox, replace \ with the name, email address, or alias of the mailbox, and run this command: Export-MailboxDiagnosticLogs -Identity \ -ComponentName SubstrateHoldTracking. +The removal of a hold from a mailbox is temporarily delayed to prevent the accidental purge of content that's no longer affected by the hold. This temporary delay in the removal of the hold is known as a delay hold. To see the hold history on a mailbox, replace `` with the name, email address, or alias of the mailbox, and run this command: `Export-MailboxDiagnosticLogs -Identity -ComponentName SubstrateHoldTracking`. You can use this switch with the GroupMailbox or InactiveMailbox switch to remove delay holds from group mailboxes or inactive mailboxes. -For more information, see [Managing mailboxes on delay hold](https://docs.microsoft.com/microsoft-365/compliance/identify-a-hold-on-an-exchange-online-mailbox#managing-mailboxes-on-delay-hold). +For more information, see [Managing mailboxes on delay hold](https://learn.microsoft.com/purview/ediscovery-identify-a-hold-on-an-exchange-online-mailbox#managing-mailboxes-on-delay-hold). ```yaml Type: SwitchParameter Parameter Sets: RemoveDelayReleaseHoldApplied Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -4658,12 +4634,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RemoveMailboxProvisioningConstraint +This parameter is available only in the cloud-based service. + +{{ Fill RemoveMailboxProvisioningConstraint Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RemoveManagedFolderAndPolicy 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. +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. ```yaml Type: SwitchParameter @@ -4691,7 +4683,7 @@ In an Exchange hybrid deployment, In-Place Holds that are created in the on-prem Type: String[] Parameter Sets: RemoveOrphanedHolds Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4744,7 +4736,6 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. ```yaml @@ -4766,16 +4757,15 @@ 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: - $true: The user is required to change their password the next time they log on to their mailbox. - - $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value. -In Office 365, administrators can require users to reset their password the next time they log on by using the ResetPasswordOnNextLogon parameter on the Set-User cmdlet. +In Exchange Online, administrators can require users to reset their password the next time they log on by using the ResetPasswordOnNextLogon parameter on the Set-User cmdlet. ```yaml Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4807,9 +4797,9 @@ You use the Set-ResourceConfig and Get-ResourceConfig cmdlets to create and view After you create custom resource properties, you use this parameter to assign one or more of those properties to a resource mailbox. Properties that begin with the prefix Room/ are available only on room mailboxes, and properties that begin with the prefix Equipment/ are available only on equipment mailboxes. When you specify a property value for this parameter, don't include the prefix. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -4828,22 +4818,20 @@ Accept wildcard characters: False 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. - - Selecting the Empty Deleted Items Folder action. - - Deleting items using Shift + Delete. -These actions move the items to the Recoverable Items folder, into a subfolder named Deletions. +These actions move the items into the Recoverable Items\\Deletions folder. -Before the deleted item retention period expires, users can recover soft-deleted items in Outlook and Outlook on the web by using the Recover Deleted Items feature. For more information, see [Recoverable Items folder in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). +Before the deleted item retention period expires, users can recover soft-deleted items in Outlook and Outlook on the web by using the Recover Deleted Items feature. For more information, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. -The default value is 14 days (14.00:00:00). In Office 365, you can increase the value to a maximum of 30 days. +The default value is 14 days (14.00:00:00). In Exchange Online, you can increase the value to a maximum of 30 days. -In Office 365, you use this parameter to configure the RetainDeletedItemsFor value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the RetainDeletedItemsFor value for all new mailboxes that you create in the future. +In Exchange Online, you use this parameter to configure the deleted item retention on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the RetainDeletedItemsFor value for all new mailboxes that you create in the future. -In on-premises Exchange, the default value is configured by the value of the DeletedItemRetention parameter on mailbox database. To override the default value, enter a value for the RetainDeletedItemsFor parameter on the mailbox. +In on-premises Exchange, when the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the DeletedItemRetention value from the mailbox database. To use the RetainDeletedItemsFor parameter on the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. ```yaml Type: EnhancedTimeSpan @@ -4863,13 +4851,12 @@ 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: -- $true: Deleted items are kept until the next mailbox database backup. This value could effectively override the deleted item retention and recoverable items quota values. +- $true: Deleted items are kept until the next mailbox database backup. This value could effectively override the DeletedItemRetention and RecoverableItemsQuota parameter values. +- $false: This is the default value. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameter values. -- $false: Retention of deleted items doesn't depend on a backup of the mailbox database. This is the default value. +When the UseDatabaseRetentionDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the RetainDeletedItemsUntilBackup parameter value from the mailbox database. To use the RetainDeletedItemsUntilBackup parameter on the mailbox, you need to set the UseDatabaseRetentionDefaults parameter to the value $false. -For more information, see [Recoverable Items folder in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). - -The default value is configured by the value of the DeletedItemRetention parameter on mailbox database. To override the default value, enter a value for the RetainDeletedItemsFor parameter on the mailbox. +For more information, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). ```yaml Type: Boolean @@ -4887,13 +4874,17 @@ Accept wildcard characters: False ### -RetentionComment The RetentionComment parameter specifies a comment that's displayed in Outlook regarding the user's retention hold status. -This comment can only be set if the RetentionHoldEnabled parameter is set to $true. This comment should be localized to the user's preferred language. If the comment contains spaces, enclose the comment in quotation marks ("). +In on-premises Exchange, you can only use this parameter if the RetentionHoldEnabled parameter is set to $true. + +In Exchange Online, this parameter is associated with Litigation Hold (the LitigationHoldEnabled parameter), so you don't need to set the RetentionHoldEnabled parameter to $true when you use this parameter. + +This comment should be localized to the user's preferred language. If the comment contains spaces, enclose the comment 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4905,8 +4896,7 @@ Accept wildcard characters: False ### -RetentionHoldEnabled 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. - +- $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). - $false: The retention hold is removed from the mailbox. The mailbox is subject to retention policies and managed folder policies. This is the default value. To set the start date for retention hold, use the StartDateForRetentionHold parameter. @@ -4928,9 +4918,7 @@ Accept wildcard characters: False 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 - - Distinguished Name (DN) - - GUID Retention policies consist of tags that are applied to mailbox folders and mail items to determine the period of time that the items should be retained. @@ -4959,7 +4947,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4972,14 +4960,12 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID -In Office 365, a role assignment policy must be assigned to the mailbox. In on-premises Exchange, to configure the mailbox so there's no role assignment policy assigned, use the value $null. +In Exchange Online, a role assignment policy must be assigned to the mailbox. In on-premises Exchange, to configure the mailbox so there's no role assignment policy assigned, use the value $null. -Use the Get-RoleAssignmentPolicy cmdlet to see the available role assignment policies. For more information, see [Understanding management role assignment policies](https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). +Use the Get-RoleAssignmentPolicy cmdlet to see the available role assignment policies. For more information, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). ```yaml Type: MailboxPolicyIdParameter @@ -4995,9 +4981,25 @@ Accept wildcard characters: False ``` ### -RoomMailboxPassword -Use the RoomMailboxPassword parameter to change the password for a room mailbox that has an enabled account (the EnableRoomMailboxAccount parameter is set to the value $true.) +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). + +To use this parameter in on-premises Exchange, you need to be a member of one of the following role groups: -This parameter uses the syntax `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +- The Organization Management role group via the Mail Recipients and User Options roles. +- The Recipient Management role group via the Mail Recipients role. +- The Help Desk role group via the User Options role. + +The Reset Password role also allows you to use this parameter, but it isn't assigned to any role groups by default. + +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. + +To configure the password for a room mailbox account in Exchange Online, use the PasswordProfile parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. ```yaml Type: SecureString @@ -5018,12 +5020,13 @@ The RulesQuota parameter specifies the limit for the size of Inbox rules for the 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: - B (bytes) - - KB (kilobytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. -The default value is 64 kilobytes (65536 bytes). +In Exchange Online, Exchange 2019, Exchange 2016, and Exchange 2013, the default value is 256 kilobytes (262,144 bytes). + +In Exchange 2010, the default value is 64 kilobytes (65,536 bytes). The quota for Inbox rules applies only to enabled rules. There is no restriction on the number of disabled rules a mailbox can have. However, the total size of rules that are enabled or active can't exceed the value specified for this parameter. @@ -5043,7 +5046,7 @@ Accept wildcard characters: False ### -SamAccountName 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 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. +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 @@ -5058,15 +5061,31 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SchedulerAssistant +This parameter is available only in the cloud-based service. + +{{ Fill SchedulerAssistant Description }} + +```yaml +Type: Boolean +Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -SCLDeleteEnabled 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: -- $true: Messages that meet or exceed the SCLDeleteThreshold value are silently deleted without sending an non-delivery report (NDR). - +- $true: Messages that meet or exceed the SCLDeleteThreshold value are silently deleted without sending a non-delivery report (NDR). - $false: Messages that meet or exceed the SCLDeleteThreshold value aren't deleted. - - $null (blank): The value isn't configured. This is the default value. ```yaml @@ -5108,9 +5127,7 @@ 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: - $true: Messages that exceed the SCLJunkThreshold value are moved to the Junk Email folder. Messages that meet the SCLJunkThreshold value aren't moved to the Junk Email folder. - - $false: Messages that meet or exceed the SCLJunkThreshold value aren't moved to the Junk Email folder. - - $null (blank): The value isn't configured. This is the default value. ```yaml @@ -5152,12 +5169,10 @@ 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: - $true: Messages that meet or exceed the SCLQuarantineThreshold value are sent to the quarantine mailbox. - - $false: Messages that meet or exceed the SCLQuarantineThreshold value aren't sent to the quarantine mailbox. - - $null (blank): The value isn't configured. This is the default value. -To configure the quarantine mailbox, see [Configure a spam quarantine mailbox](https://docs.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-quarantine-mailboxes). +To configure the quarantine mailbox, see [Configure a spam quarantine mailbox](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-quarantine-mailboxes). ```yaml Type: Boolean @@ -5198,9 +5213,7 @@ 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: - $true: Messages that meet or exceed the SCLRejectThreshold value are rejected, and an NDR is sent to the sender. - - $false: Messages that meet or exceed the SCLRejectThreshold value aren't rejected. - - $null (blank): The value isn't configured. This is the default value. ```yaml @@ -5237,13 +5250,15 @@ Accept wildcard characters: False ``` ### -SecondaryAddress +This parameter is available only in on-premises Exchange. + The SecondaryAddress parameter specifies the secondary address used by the UM-enabled user. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5253,13 +5268,15 @@ Accept wildcard characters: False ``` ### -SecondaryDialPlan +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. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5272,9 +5289,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -5296,9 +5311,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID Use the Get-SharingPolicy cmdlet to see the available sharing policies. @@ -5320,12 +5333,10 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". +- space +- `" ' ( ) + , - . / : ?` ```yaml Type: String @@ -5341,11 +5352,10 @@ Accept wildcard characters: False ``` ### -SingleItemRecoveryEnabled -The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recovery Items folder from being purged. Valid values are: - -- $true: Single item recovery is enabled. The Recovery Items folder can't be purged. and items that have been deleted or edited can't be removed. +The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recoverable Items folder from being purged. Valid values are: -- $false: Single item recovery isn't enabled. The Recovery Items folder can be purged, and, items that have been deleted or edited can be removed. This is the default value. +- $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). +- $false: Single item recovery isn't enabled. The Recoverable Items folder can be purged, and deleted or edited items can be removed. This is the default value in Exchange Server. For more information, see [Enable or disable single item recovery for a mailbox](https://learn.microsoft.com/exchange/recipients/user-mailboxes/single-item-recovery). ```yaml Type: Boolean @@ -5381,7 +5391,7 @@ Accept wildcard characters: False ### -StartDateForRetentionHold 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". +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". To use this parameter, you need to set the RetentionHoldEnabled parameter to value $true. @@ -5405,7 +5415,7 @@ This parameter is reserved for internal Microsoft use. Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5456,9 +5466,7 @@ 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: - Name - - Distinguished name (DN) - - GUID Use the Get-ThrottlingPolicy cmdlet to see the available throttling policies. @@ -5479,13 +5487,12 @@ Accept wildcard characters: False ### -Type The Type parameter specifies the mailbox type for the mailbox. Valid values are: +- Equipment - Regular - - Room - -- Equipment - - Shared +- Workspace (cloud-only) +- Desk (cloud-only): This value doesn't result in a desk that's available for booking. Instead, create the desk in Places PowerShell using the [New-Place](https://learn.microsoft.com/microsoft-365/places/powershell/new-place) cmdlet, and then link the desk to this mailbox using the [Set-PlaceV3](/microsoft-365/places/powershell/set-placev3) cmdlet. ```yaml Type: ConvertibleMailboxSubType @@ -5521,27 +5528,27 @@ Accept wildcard characters: False ``` ### -UMDtmfMap -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: - -- emailAddress:\ +This parameter is available only in on-premises Exchange. -- lastNameFirstName:\ +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: -- firstNameLastName:\ +- `emailAddress:` +- `lastNameFirstName:` +- `firstNameLastName:` -To enter values that overwrite all existing entries, use the following syntax: emailAddress:\,lastNameFirstName:\,firstNameLastName:\. +To enter values that overwrite all existing entries, use the following syntax: `emailAddress:,lastNameFirstName:,firstNameLastName:`. -If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:\, all existing lastNameFirstName and firstNameLastName values are removed. +If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only `emailAddress:`, all existing lastNameFirstName and firstNameLastName values are removed. -To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"; Remove="emailAddress:\","lastNameFirstName:\","firstNameLastName:\"}. +To add or remove values without affecting other existing entries, use the following syntax: `@{Add="emailAddress:","lastNameFirstName:","firstNameLastName:"; Remove="emailAddress:","lastNameFirstName:","firstNameLastName:"}`. -If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:\","emailAddress:\} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. +If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use `@{Add="emailAddress:","emailAddress:}` to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5570,34 +5577,44 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -UseDatabaseQuotaDefaults -The UseDatabaseQuotaDefaults parameter specifies whether the mailbox uses the applicable quota values that are configured on the mailbox or on the mailbox database. Valid values are: +### -UpdateEnforcedTimestamp +This parameter is available only in the cloud-based service. -- $true: The mailbox uses the applicable quota values that are configured on the mailbox database. Any of those quota values configured directly on the mailbox are ignored. +{{ Fill UpdateEnforcedTimestamp Description }} -- $false: The mailbox uses its own values for the applicable quota values. Any of those quota values on the mailbox database are ignored. +```yaml +Type: SwitchParameter +Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds +Aliases: +Applicable: Exchange Online, Exchange Online Protection -In Office 365, the default value is $false. In on-premises Exchange, the default value is $true. +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` -The applicable quota values are: +### -UseDatabaseQuotaDefaults +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: -- CalendarLoggingQuota +- $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. +- $false: The mailbox uses its own values for the applicable quotas. Any corresponding quotas that are configured on the mailbox database are ignored. In Exchange Online, this is the default value. -- IssueWarningQuota +The following quotas are affected by this parameter: +- CalendarLoggingQuota +- IssueWarningQuota - ProhibitSendQuota - - ProhibitSendReceiveQuota - - RecoverableItemsQuota - - RecoverableItemsWarningQuota ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -5607,19 +5624,28 @@ Accept wildcard characters: False ``` ### -UseDatabaseRetentionDefaults -This parameter is available only in on-premises Exchange. +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: + +- $true: The mailbox uses the applicable retention settings that are configured on the mailbox database. Any corresponding settings that are configured on the mailbox are ignored. This is the default value. +- $false: The mailbox uses its own values for the applicable retention settings. Any corresponding settings that are configured on the mailbox database are ignored. + +The following retention settings are affected by this parameter: -The UseDatabaseRetentionDefaults parameter specifies whether the mailbox uses the MailboxRetention attribute value that's configured on the mailbox database. This value controls how long deleted mailboxes are kept in the database before they are permanently removed (purged). The default value is 30 days. Valid values are: +- DeletedItemRetention +- RetainDeletedItemsUntilBackup -- $true: The mailbox uses the MailboxRetention value that's configured on the mailbox database. This is the default value. +**Note**: If you set the RetainDeletedItemsUntilBackup parameter on the mailbox database to the value $true when the value of the UseDatabaseRetentionDefaults parameter on a mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet will erroneously appear as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: -- $false: When the mailbox is deleted, it's retained indefinitely. +- Run the following command: `Import-Module ActiveDirectory`. +- Replace \ with the Alias value of the mailbox, and run the following command: `Get-ADUser -Properties mDBUseDefaults | Format-List mDBUseDefaults`. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -5647,7 +5673,7 @@ Accept wildcard characters: False ### -UserPrincipalName 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 \@\. Typically, the \ value is the domain where the user account resides. +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 @@ -5685,7 +5711,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5698,7 +5724,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -5721,12 +5746,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/exchange/Set-MailboxAuditBypassAssociation.md similarity index 87% rename from exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-MailboxAuditBypassAssociation.md rename to exchange/exchange-ps/exchange/Set-MailboxAuditBypassAssociation.md index e5ef82abb5..bf087d92fa 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-MailboxAuditBypassAssociation.md +++ b/exchange/exchange-ps/exchange/Set-MailboxAuditBypassAssociation.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/set-mailboxauditbypassassociation -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailboxAuditBypassAssociation @@ -17,13 +16,16 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailboxAuditBypassAssociation cmdlet to configure mailbox audit logging bypass for user or computer accounts such as service accounts for applications that access mailboxes frequently. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-MailboxAuditBypassAssociation [-Identity] - -AuditBypassEnabled [-Confirm] [-DomainController ] [-WhatIf] [] +Set-MailboxAuditBypassAssociation [-Identity] -AuditBypassEnabled + [-Confirm] + [-DomainController ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ When you configure a user or computer account to bypass mailbox audit logging, a If you use mailbox audit logging to audit mailbox access and actions, you must monitor mailbox audit bypass associations at regular intervals. If a mailbox audit bypass association is added for an account, the account can access any mailbox in the organization to which it has been assigned access permissions, without any mailbox audit logging entries being generated for such access, or any actions taken such as message deletions. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,54 +53,52 @@ This example removes the bypass association for the Svc-MyApplication account. ## PARAMETERS -### -AuditBypassEnabled -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 - -- $false: Disables mailbox audit logging bypass +### -Identity +The Identity parameter specifies a user or computer account to be bypassed from mailbox audit logging. ```yaml -Type: Boolean +Type: MailboxAuditBypassAssociationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies a user or computer account to be bypassed from mailbox audit logging. +### -AuditBypassEnabled +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 +- $false: Disables mailbox audit logging bypass ```yaml -Type: MailboxAuditBypassAssociationIdParameter +Type: Boolean Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -132,7 +132,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -146,12 +146,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/exchange/Set-MailboxAutoReplyConfiguration.md similarity index 81% rename from exchange/exchange-ps/exchange/mailboxes/Set-MailboxAutoReplyConfiguration.md rename to exchange/exchange-ps/exchange/Set-MailboxAutoReplyConfiguration.md index 2839239ba4..24d0f4377e 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxAutoReplyConfiguration.md +++ b/exchange/exchange-ps/exchange/Set-MailboxAutoReplyConfiguration.md @@ -1,14 +1,13 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailboxautoreplyconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailboxAutoReplyConfiguration @@ -18,7 +17,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailboxAutoReplyConfiguration cmdlet to configure Automatic Replies settings for a specific mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -40,29 +39,30 @@ Set-MailboxAutoReplyConfiguration [-Identity] [-InternalMessage ] [-OOFEventSubject ] [-StartTime ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can disable Automatic Replies for a specified mailbox or organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-MailboxAutoReplyConfiguration -Identity tony -AutoReplyState Scheduled -StartTime "7/10/2018 08:00:00" -EndTime "7/15/2018 17:00:00" -InternalMessage "Internal auto-reply message" +Set-MailboxAutoReplyConfiguration -Identity tony@contoso.com -AutoReplyState Scheduled -StartTime "7/10/2018 08:00:00" -EndTime "7/15/2018 17:00:00" -InternalMessage "Internal auto-reply message" ``` -This example configures Automatic Replies for Tony's mailbox to be sent between the specified start and end dates and includes an internal message. +This example configures Automatic Replies for Tony's mailbox to be sent between the specified start and end dates and includes an internal reply. ### Example 2 ```powershell -Set-MailboxAutoReplyConfiguration -Identity tony -AutoReplyState Enabled -InternalMessage "Internal auto-reply message." -ExternalMessage "External auto-reply message." +Set-MailboxAutoReplyConfiguration -Identity tony@contoso.com -AutoReplyState Enabled -InternalMessage "Internal auto-reply message." -ExternalMessage "External auto-reply message." -ExternalAudience All ``` -This example configures Automatic Replies for Tony's mailbox to be sent and includes an internal and an external message. +This example configures Automatic Replies for Tony's mailbox to be sent, specifies the reply for messages from internal and external senders, and specifies the external reply is sent to any external address. ## PARAMETERS @@ -70,30 +70,21 @@ This example configures Automatic Replies for Tony's mailbox to be sent and incl The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -103,12 +94,11 @@ Accept wildcard characters: False ``` ### -AutoDeclineFutureRequestsWhenOOF -This parameter is available only in the cloud-based service. +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: - $true: New meeting requests that are received during the scheduled time period are automatically declined. - - $false: Meeting requests received during the scheduled time period aren't automatically declined. This is the default value. You can use this parameter only when the AutoReplyState parameter is set to Scheduled. @@ -117,7 +107,7 @@ You can use this parameter only when the AutoReplyState parameter is set to Sche Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -130,15 +120,12 @@ Accept wildcard characters: False The AutoReplyState parameter specifies whether the mailbox is enabled for Automatic Replies. Valid values are: - Enabled: Automatic Replies are sent for the mailbox. - - Disabled: Automatic Replies aren't sent for the mailbox. This is the default value. - - Scheduled: Automatic Replies are sent for the mailbox during the time period that's specified by the StartTime and EndTime parameters. The Enabled and Scheduled values require these additional settings: - A value for the InternalMessageValue parameter. - - A value for the ExternalMessageValue parameter if the ExternalAudience parameter is set to Known or All. ```yaml @@ -157,15 +144,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -175,19 +161,18 @@ Accept wildcard characters: False ``` ### -CreateOOFEvent -This parameter is available only in the cloud-based service. +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: - $true: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, a calendar event is created in the mailbox for those dates. You can specify the subject for the event by using the OOFEventSubject parameter. - - $false: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, no calendar event is created for those dates. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -197,12 +182,11 @@ Accept wildcard characters: False ``` ### -DeclineAllEventsForScheduledOOF -This parameter is available only in the cloud-based service. +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: -- $true: Existing calendar events in the mailbox that occur during the scheduled time period are declined and removed from the calendar. - +- $true: Existing calendar events in the mailbox that occur during the scheduled time period are declined and removed from the calendar. If the mailbox is the meeting organizer, the events are cancelled for all other attendees. - $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value. You can use this parameter only when the DeclineEventsForScheduledOOF parameter is set to $true. @@ -213,7 +197,7 @@ You can't use this parameter with the EventsToDeleteIDs parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -223,11 +207,13 @@ Accept wildcard characters: False ``` ### -DeclineEventsForScheduledOOF -This parameter is available only in the cloud-based service. +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: -- $true: Existing calendar events in the mailbox that occur during the scheduled time period can be declined and removed from the calendar. To decline specific events during the scheduled time period, use the EventsToDeleteIDs parameter. To decline all events during the scheduled time period, use the DeclineAllEventsForScheduledOOF parameter. +- $true: Existing calendar events in the mailbox that occur during the scheduled time period can be declined and removed from the calendar. If the mailbox is the meeting organizer, the events are cancelled for all other attendees. + + To decline specific events during the scheduled time period, use the EventsToDeleteIDs parameter. To decline all events during the scheduled time period, use the DeclineAllEventsForScheduledOOF parameter. - $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value. @@ -237,7 +223,7 @@ You can use this parameter only when the AutoReplyState parameter is set to Sche Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -247,15 +233,14 @@ Accept wildcard characters: False ``` ### -DeclineMeetingMessage -This parameter is available only in the cloud-based service. +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: - The AutoDeclineFutureRequestsWhenOOF parameter is set to $true. - - The DeclineEventsForScheduledOOF parameter is set to $true, and the DeclineAllEventsForScheduledOOF parameter is set to $true, or individual events are specified by using the EventsToDeleteIDs parameter. -If the value contains spaces, enclose the value in quotation marks ("). HTML tags aren't automatically added to the text, but you can use values that contain HTML tags. For example, "\\I'm on vacation.\I can't attend the meeting.\\". +If the value contains spaces, enclose the value in quotation marks ("). HTML tags aren't automatically added to the text, but you can use values that contain HTML tags. For example, `"I'm on vacation. I can't attend the meeting."`. To clear the value of this parameter, use the value $null. @@ -263,7 +248,7 @@ To clear the value of this parameter, use the value $null. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -293,7 +278,7 @@ Accept wildcard characters: False ### -EndTime 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". +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". ```yaml Type: DateTime @@ -309,7 +294,7 @@ Accept wildcard characters: False ``` ### -EventsToDeleteIDs -This parameter is available only in the cloud-based service. +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. @@ -321,7 +306,7 @@ You can't use this parameter with the DeclineAllEventsForScheduledOOF parameter. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -334,9 +319,7 @@ Accept wildcard characters: False 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. - - Known: Automatic Replies are sent only to external senders that are specified in the Contact list of the mailbox. - - All: Automatic Replies are sent to all external senders. This is the default value. The value of this parameter is meaningful only when the AutoReplyState parameter is set to Enabled or Scheduled. @@ -357,12 +340,11 @@ Accept wildcard characters: False ### -ExternalMessage 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.\\". +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."`. The value of this parameter is meaningful only when both of the following conditions are true: - The AutoReplyState parameter is set to Enabled or Scheduled. - - The ExternalAudience parameter is set to Known or All. To clear the value of this parameter when it's no longer required (for example, if you change the ExternalAudience parameter to None), use the value $null. @@ -381,12 +363,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -405,7 +386,7 @@ Accept wildcard characters: False ### -InternalMessage 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.\\". +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."`. The value of this parameter is meaningful only when the AutoReplyState parameter is set to Enabled or Scheduled. @@ -425,7 +406,7 @@ Accept wildcard characters: False ``` ### -OOFEventSubject -This parameter is available only in the cloud-based service. +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. @@ -435,7 +416,7 @@ If the value contains spaces, enclose the value in quotation marks ("). To clear Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -447,7 +428,7 @@ Accept wildcard characters: False ### -StartTime 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". +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". ```yaml Type: DateTime @@ -469,7 +450,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -483,12 +464,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-MailboxCalendarConfiguration.md b/exchange/exchange-ps/exchange/Set-MailboxCalendarConfiguration.md new file mode 100644 index 0000000000..78d43a57d3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailboxCalendarConfiguration.md @@ -0,0 +1,1281 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailboxCalendarConfiguration + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-MailboxCalendarConfiguration cmdlet to modify mailbox calendar settings for Outlook on the web. This affects how the user's calendar looks and how reminders work in Outlook on the web. This also affects settings that define how meeting invitations, responses, and notifications are sent to the user. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Set-MailboxCalendarConfiguration [-Identity] + [-AgendaMailEnabled ] + [-Confirm] + [-ConversationalSchedulingEnabled ] + [-DailyAgendaMailSchedule ] + [-DefaultMeetingDuration ] + [-DefaultReminderTime ] + [-DomainController ] + [-FirstWeekOfYear ] + [-RemindersEnabled ] + [-ReminderSoundEnabled ] + [-ShowWeekNumbers ] + [-SkipAgendaMailOnFreeDays ] + [-TimeIncrement ] + [-UseBrightCalendarColorThemeInOwa ] + [-WeekStartDay ] + [-WhatIf] + [-WorkDays ] + [-WorkingHoursEndTime ] + [-WorkingHoursStartTime ] + [-WorkingHoursTimeZone ] + [] +``` + +### Identity +``` +Set-MailboxCalendarConfiguration [-Identity] + [-AgendaMailEnabled ] + [-AgendaMailIntroductionEnabled ] + [-AgendaPaneEnabled ] + [-AutoDeclineWhenBusy ] + [-CalendarFeedsPreferredLanguage ] + [-CalendarFeedsPreferredRegion ] + [-CalendarFeedsRootPageId ] + [-Confirm] + [-ConversationalSchedulingEnabled ] + [-CreateEventsFromEmailAsPrivate ] + [-DailyAgendaMailSchedule ] + [-DefaultMeetingDuration ] + [-DefaultMinutesToReduceLongEventsBy ] + [-DefaultMinutesToReduceShortEventsBy ] + [-DefaultOnlineMeetingProvider ] + [-DefaultReminderTime ] + [-DeleteMeetingRequestOnRespond ] + [-DiningEventsFromEmailEnabled ] + [-EntertainmentEventsFromEmailEnabled ] + [-EventsFromEmailEnabled ] + [-FirstWeekOfYear ] + [-FlightEventsFromEmailEnabled ] + [-HotelEventsFromEmailEnabled ] + [-InvoiceEventsFromEmailEnabled ] + [-LocationDetailsInFreeBusy ] + [-OnlineMeetingsByDefaultEnabled ] + [-PackageDeliveryEventsFromEmailEnabled ] + [-PreserveDeclinedMeetings ] + [-RemindersEnabled ] + [-ReminderSoundEnabled ] + [-RentalCarEventsFromEmailEnabled ] + [-ServiceAppointmentEventsFromEmailEnabled ] + [-ShortenEventScopeDefault ] + [-ShowWeekNumbers ] + [-SkipAgendaMailOnFreeDays ] + [-TimeIncrement ] + [-UseBrightCalendarColorThemeInOwa ] + [-WeatherEnabled ] + [-WeatherLocationBookmark ] + [-WeatherLocations ] + [-WeatherUnit ] + [-WeekStartDay ] + [-WhatIf] + [-WorkDays ] + [-WorkingHoursEndTime ] + [-WorkingHoursStartTime ] + [-WorkingHoursTimeZone ] + [-WorkspaceUserEnabled ] + [] +``` + +### MailboxLocation +``` +Set-MailboxCalendarConfiguration [-MailboxLocation ] + [-AgendaMailEnabled ] + [-AgendaMailIntroductionEnabled ] + [-AgendaPaneEnabled ] + [-AutoDeclineWhenBusy ] + [-CalendarFeedsPreferredLanguage ] + [-CalendarFeedsPreferredRegion ] + [-CalendarFeedsRootPageId ] + [-Confirm] + [-ConversationalSchedulingEnabled ] + [-CreateEventsFromEmailAsPrivate ] + [-DailyAgendaMailSchedule ] + [-DefaultMeetingDuration ] + [-DefaultMinutesToReduceLongEventsBy ] + [-DefaultMinutesToReduceShortEventsBy ] + [-DefaultOnlineMeetingProvider ] + [-DefaultReminderTime ] + [-DeleteMeetingRequestOnRespond ] + [-DiningEventsFromEmailEnabled ] + [-EntertainmentEventsFromEmailEnabled ] + [-EventsFromEmailEnabled ] + [-FirstWeekOfYear ] + [-FlightEventsFromEmailEnabled ] + [-HotelEventsFromEmailEnabled ] + [-InvoiceEventsFromEmailEnabled ] + [-LocationDetailsInFreeBusy ] + [-OnlineMeetingsByDefaultEnabled ] + [-PackageDeliveryEventsFromEmailEnabled ] + [-PreserveDeclinedMeetings ] + [-RemindersEnabled ] + [-ReminderSoundEnabled ] + [-RentalCarEventsFromEmailEnabled ] + [-ServiceAppointmentEventsFromEmailEnabled ] + [-ShortenEventScopeDefault ] + [-ShowWeekNumbers ] + [-SkipAgendaMailOnFreeDays ] + [-TimeIncrement ] + [-UseBrightCalendarColorThemeInOwa ] + [-WeatherEnabled ] + [-WeatherLocationBookmark ] + [-WeatherLocations ] + [-WeatherUnit ] + [-WeekStartDay ] + [-WhatIf] + [-WorkDays ] + [-WorkingHoursEndTime ] + [-WorkingHoursStartTime ] + [-WorkingHoursTimeZone ] + [-WorkspaceUserEnabled ] + [] +``` + +## DESCRIPTION +The Set-MailboxCalendarConfiguration cmdlet primarily allows users to manage their own calendar settings in Outlook on the web Options. However, administrators who are members of the Organization Management or Recipient Management role groups can configure the calendar settings for users by using this cmdlet. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailboxCalendarConfiguration -Identity peter@contoso.com -RemindersEnabled $false +``` + +This example disables the calendar reminders for the calendar of the user peter@contoso.com. + +### Example 2 +```powershell +Set-MailboxCalendarConfiguration -Identity peter@contoso.com -WorkingHoursTimeZone "Pacific Standard Time" +``` + +This example sets the time zone of the work hours' start and end times to Pacific Standard Time for the calendar of the user peter@contoso.com. + +### Example 3 +```powershell +Set-MailboxCalendarConfiguration -Identity Tony -WorkingHoursStartTime 07:00:00 +``` + +This example sets the working day's starting hour to 7 A.M. for the calendar of the user Tony. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AgendaMailEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AgendaMailIntroductionEnabled +This parameter is available only in the cloud-based service. + +{{ Fill AgendaMailIntroductionEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AgendaPaneEnabled +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoDeclineWhenBusy +This parameter is available only in the cloud-based service. + +{{ Fill AutoDeclineWhenBusy Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CalendarFeedsPreferredLanguage +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). + +```yaml +Type: String +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CalendarFeedsPreferredRegion +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). + +A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). + +```yaml +Type: String +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CalendarFeedsRootPageId +This parameter is available only in the cloud-based service. + +The CalendarFeedsRootPageId parameter specifies the root page ID for calendar feeds. + +```yaml +Type: String +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConversationalSchedulingEnabled +The ConversationalSchedulingEnabled parameter specifies whether to enable or disable conversational scheduling. Valid values are: + +- $true: Conversational scheduling is enabled. This is the default value. +- $false: Conversational scheduling is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CreateEventsFromEmailAsPrivate +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: + +- $true: Events from email are created as Private. This is the default value. +- $false: Events from email are created as Normal (public). + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DailyAgendaMailSchedule +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultMeetingDuration +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultMinutesToReduceLongEventsBy +This parameter is available only in the cloud-based service. + +{{ Fill DefaultMinutesToReduceLongEventsBy Description }} + +```yaml +Type: Int32 +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultMinutesToReduceShortEventsBy +This parameter is available only in the cloud-based service. + +{{ Fill DefaultMinutesToReduceShortEventsBy Description }} + +```yaml +Type: Int32 +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultOnlineMeetingProvider +This parameter is available only in the cloud-based service. + +The DefaultOnlineMeetingProvider parameter specifies the default provider for online meetings. Valid values are: + +- AlibabaDingTalk +- AmazonChimePrivate +- AmazonChimePublic +- AppleFacetime +- BlueJeans +- ClaroVideoconferencia +- FacebookWorkplace +- GoogleMeet +- GoToMeeting +- JioMeet +- RingCentral +- SkypeForBusiness +- SkypeForConsumer +- TeamsForBusiness (This is the default value.) +- Webex +- Zoom + +```yaml +Type: OnlineMeetingProviderType +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultReminderTime +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. + +Note that the value can't contain seconds. Valid values are: + +- 00:00:00 +- 00:05:00 (5 minutes) +- 00:10:00 (10 minutes) +- 00:15:00 (15 minutes) This is the default value. +- 00:30:00 (30 minutes) +- 01:00:00 (1 hour) +- 02:00:00 (2 hours) +- 03:00:00 (3 hours) +- 04:00:00 (4 hours) +- 08:00:00 (8 hours) +- 12:00:00 (12 hours) +- 1.00:00:00 (1 day) +- 2.00:00:00 (2 days) +- 3.00:00:00 (3 days) +- 7.00:00:00 (7 days) +- 14.00:00:00 (14 days) + +This parameter is ignored when the RemindersEnabled parameter is set to $false. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeleteMeetingRequestOnRespond +This parameter is available only in the cloud-based service. + +{{ Fill DeleteMeetingRequestOnRespond Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DiningEventsFromEmailEnabled +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: + +- $true: Create dining reservation events from email messages. This is the default value. +- $false: Don't create dining reservation events from email messages. + +This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntertainmentEventsFromEmailEnabled +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: + +- $true: Create entertainment reservation events from email messages. This is the default value. +- $false: Don't create entertainment reservation events from email messages. + +This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventsFromEmailEnabled +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: + +- $true: Creating events from email messages is enabled. This is the default value. +- $false: Creating events from email messages is disabled. + +When this setting is enabled, you can enable or disable creating specific types of events from email messages by using the following parameters: + +- DiningEventsFromEmailEnabled +- EntertainmentEventsFromEmailEnabled +- FlightEventsFromEmailEnabled +- HotelEventsFromEmailEnabled +- PackageDeliveryEventsFromEmailEnabled +- RentalCarEventsFromEmailEnabled + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FirstWeekOfYear +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. +- FirstFourDayWeek: Week numbers start on the first week that has at least four days. +- FirstFullWeek: Week numbers start on the first week that has seven days. +- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox has been moved from an earlier version of Exchange. + +You configure the first day of the week by using the WeekStartDay parameter. + +```yaml +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 +Default value: None +Accept pipeline input: false +Accept wildcard characters: False +``` + +### -FlightEventsFromEmailEnabled +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: + +- $true: Create flight reservation events from email messages. This is the default value. +- $false: Don't create flight reservation events from email messages. + +This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HotelEventsFromEmailEnabled +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: + +- $true: Create hotel reservation events from email messages. This is the default value. +- $false: Don't create hotel reservation events from email messages. + +This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InvoiceEventsFromEmailEnabled +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: + +- $true: Creating invoices from messages is enabled. This is the default value. +- $false: Creating invoices from messages is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationDetailsInFreeBusy +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: + +- None: No location information is returned. +- Building: Only Office or Remote are returned as work location information, if provided. +- Desk: All work location information is returned, including Building and Desk, if provided. This is the default value. + +```yaml +Type: LocationDetailsPermissionInFreeBusy +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: Desk +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxLocation +This parameter is available only in the cloud-based service. + +{{ Fill MailboxLocation Description }} + +```yaml +Type: MailboxLocationIdParameter +Parameter Sets: MailboxLocation +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlineMeetingsByDefaultEnabled +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. + +Valid values are: + +- $true: All meetings are online by default. +- $false: All meetings are not online by default. +- $null: The value of the OnlineMeetingsByDefaultEnabled parameter on the Set-OrganizationConfig cmdlet (the organizational setting) is used. + +Setting this parameter enables the display of the **Add online meeting to all meetings** option in **Calendar options** in Outlook for Windows. This setting allows users to enable or disable the option when Teams is used for online meetings. It does not override the organization setting that's configured by the OnlineMeetingsByDefaultEnabled parameter on the Set-OrganizationConfig cmdlet. + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PackageDeliveryEventsFromEmailEnabled +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: + +- $true: Create package delivery events from email messages. +- $false: Don't create package delivery events from email messages. This is the default value. + +This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreserveDeclinedMeetings +This parameter is available only in the cloud-based service. + +{{ Fill PreserveDeclinedMeetings Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemindersEnabled +The RemindersEnabled parameter enables or disables reminders for calendar items. Valid values are: + +- $true: Reminders are enabled. This is the default value. +- $false: Reminders are disabled. + +When the reminder is first displayed is controlled by the DefaultReminderTime 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReminderSoundEnabled +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. +- $false: No sound is played with the reminder. + +This parameter is ignored when the RemindersEnabled parameter is set 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RentalCarEventsFromEmailEnabled +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: + +- $true: Create rental car reservation events from email messages. This is the default value. +- $false: Don't create rental car reservation events from email messages. + +This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceAppointmentEventsFromEmailEnabled +This parameter is available only in the cloud-based service. + +{{ Fill ServiceAppointmentEventsFromEmailEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShortenEventScopeDefault +This parameter is available only in the cloud-based service. + +{{ Fill ShortenEventScopeDefault Description }} + +```yaml +Type: ShortenEventScopeOption +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowWeekNumbers +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. +- $false: The week number isn't displayed. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipAgendaMailOnFreeDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeIncrement +The TimeIncrement parameter specifies the scale that the Outlook on the web calendar uses to show time. Valid values are: + +- FifteenMinutes +- ThirtyMinutes (This is the default value) + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseBrightCalendarColorThemeInOwa +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. +- $false: Use light colors in the calendar. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WeatherEnabled +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: + +- FirstRun (This is the default value) +- Disabled: Hide weather on the calendar. +- Enabled: Show weather on the calendar. + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WeatherLocationBookmark +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. + +A valid value for this parameter depends on the number of weather locations that are configured for the mailbox. For example, if there are 3 weather locations configured, you can specify the value 0, 1, or 2 for this parameter. + +```yaml +Type: Int32 +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WeatherLocations +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. + +This parameter uses the syntax: `LocationId:;Name:;Latitude:;Longitude:`. For example, `LocationId:105808079;Name:Redmond, WA;Latitude:47.679;Longitude:-122.132`. + +To enter multiple values and overwrite any existing entries, use the following syntax: `"Value1","Value2",..."ValueN"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +For this parameter, each Value is `LocationId:;Name:;Latitude:;Longitude:`. + +You can configure a maximum of 5 weather locations. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WeatherUnit +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: + +- Default (This is the default value) +- Celsius +- Fahrenheit + +```yaml +Type: WeatherTemperatureUnit +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WeekStartDay +The WeekStartDay parameter specifies the first day of the week. Valid values are: + +- Sunday (This is the default value) +- Monday +- Tuesday +- Wednesday +- Thursday +- Friday +- Saturday + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkDays +The WorkDays parameter specifies the work days in the calendar. Valid values are: + +- None +- AllDays +- Weekdays (This is the default value) +- WeekEndDays +- Sunday +- Monday +- Tuesday +- Wednesday +- Thursday +- Friday +- Saturday + +You can specify multiple values separated by commas, but redundant values are ignored. For example, entering Weekdays,Monday results in the value Weekdays. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkingHoursEndTime +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. + +The default value is 17:00:00 (5:00 P.M.). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkingHoursStartTime +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. + +The default value is 08:00:00(8:00 A.M.). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkingHoursTimeZone +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"). + +To see the available values, run the following command: `$TimeZone = Get-ChildItem "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Time zones" | foreach {Get-ItemProperty $_.PSPath}; $TimeZone | sort Display | Format-Table -Auto PSChildname,Display`. + +If the value contains spaces, enclose the value in quotation marks ("). The default value is the time zone setting of the Exchange server. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkspaceUserEnabled +This parameter is available only in the cloud-based service. + +{{ Fill WorkspaceUserEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-MailboxCalendarFolder.md b/exchange/exchange-ps/exchange/Set-MailboxCalendarFolder.md new file mode 100644 index 0000000000..7a30ee7341 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailboxCalendarFolder.md @@ -0,0 +1,363 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailboxCalendarFolder + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-MailboxCalendarFolder cmdlet to configure calendar publishing or sharing settings on a mailbox for the visibility of calendar information to external users. To add or modify the permissions so internal users can access the calendar, use the Add-MailboxFolderPermission or Set-MailboxFolderPermission cmdlets. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MailboxCalendarFolder [-Identity] + [-Confirm] + [-DetailLevel ] + [-DomainController ] + [-PublishDateRangeFrom ] + [-PublishDateRangeTo ] + [-PublishEnabled ] + [-ResetUrl] + [-SearchableUrlEnabled ] + [-SetAsSharingSource] + [-SharedCalendarSyncStartDate ] + [-UseHttps] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Set-MailboxCalendarFolder cmdlet configures calendar publishing information. The calendar folder can be configured as follows: + +- Whether the calendar folder is enabled for publishing +- Range of start and end calendar days to publish +- Level of detail to publish for the calendar +- Whether the published URL of the calendar is enabled for search on the web + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailboxCalendarFolder -Identity kai:\Calendar -DetailLevel LimitedDetails +``` + +This example sets the level of details to publish for Kai's shared calendar to LimitedDetails, which means limited details are displayed. + +### Example 2 +```powershell +Set-MailboxCalendarFolder -Identity kai:\Calendar -SearchableUrlEnabled $true +``` + +This example enables the calendar in Kai's mailbox to be searchable on the web. + +## PARAMETERS + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Calendar` + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DetailLevel +The DetailLevel parameter specifies the level of calendar detail that's published and available to anonymous users. Valid values are: + +- AvailabilityOnly (default) +- LimitedDetails +- FullDetails + +This parameter is meaningful only when the PublishEnabled parameter value is $true. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublishDateRangeFrom +The PublishDateRangeFrom parameter specifies the start date of calendar information to publish (past information). Valid values are: + +- OneDay +- ThreeDays +- OneWeek +- OneMonth +- ThreeMonths (This is the default value) +- SixMonths +- OneYear + +This parameter is meaningful only when the PublishEnabled parameter value is $true. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublishDateRangeTo +The PublishDateRangeTo parameter specifies the end date of calendar information to publish (future information). Valid values are: + +- OneDay +- ThreeDays +- OneWeek +- OneMonth +- ThreeMonths (This is the default value) +- SixMonths +- OneYear + +This parameter is meaningful only when the PublishEnabled parameter value is $true. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublishEnabled +The PublishEnabled parameter specifies whether to publish the specified calendar information. Valid values are: + +- $true: The calendar information is published. +- $false: The calendar information is not published. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResetUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SearchableUrlEnabled +The SearchableUrlEnabled parameter specifies whether the published calendar URL is discoverable on the web. + +- $true: The published calendar URL is discoverable on the web. +- $false: The published calendar URL is not discoverable on the web. This is the default value. + +This parameter is meaningful only when the PublishEnabled parameter 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SetAsSharingSource +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharedCalendarSyncStartDate +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. + +The SharedCalendarSyncStartDate parameter specifies the limit for past events in the shared calendar that are visible to delegates. A copy of the shared calendar within the specified date range is stored in the delegate's mailbox. + +To specify a date/time value for this parameter, use either of the following options: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +**Notes**: + +- You use this parameter on the shared calendar in the delegate's mailbox. For example, `Set-MailboxCalendarFolder -Identity delegate@contoso.onmicrosoft.com:DelegateSharedCalendarFolderId" -SharedCalendarSyncStartDate (Get-Date "5/6/2023 9:30 AM").ToUniversalTime()`. DelegateSharedCalendarFolderId is the FolderId of the shared calendar in the delegate's mailbox (for example, `Get-MailboxFolderStatistics -Identity delegate@contoso.onmicrosoft.com -FolderScope Calendar | Format-List Name,FolderId`). +- Users need to have FullDetails, Editor, or Delegate access to the specified shared calendar. +- Setting this parameter might cause events in the shared calendar to briefly disappear from view while the calendar is resynchronized. +- The value of this parameter is used when initializing the calendar folder sync. After that, every new, updated, and deleted item is processed and synced, regardless of the SharedCalendarSyncStartDate parameter value. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseHttps +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mailbox-databases-and-servers/Set-MailboxDatabase.md b/exchange/exchange-ps/exchange/Set-MailboxDatabase.md similarity index 91% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-MailboxDatabase.md rename to exchange/exchange-ps/exchange/Set-MailboxDatabase.md index b3f9ddcd6c..bf3cb3151f 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-MailboxDatabase.md +++ b/exchange/exchange-ps/exchange/Set-MailboxDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/set-mailboxdatabase +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-MailboxDatabase @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-MailboxDatabase cmdlet to configure a variety of properties for a mailbox database. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -58,11 +57,12 @@ Set-MailboxDatabase [-Identity] [-RecoverableItemsWarningQuota ] [-RetainDeletedItemsUntilBackup ] [-RpcClientAccessServer ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -80,7 +80,7 @@ Set-MailboxDatabase -RpcClientAccessServer with the Alias value of the mailbox, and run the following command: `Get-ADUser -Properties mDBUseDefaults | Format-List mDBUseDefaults`. ```yaml Type: Boolean @@ -971,11 +908,11 @@ Accept wildcard characters: False ``` ### -RpcClientAccessServer -This parameter is available or functional only in 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. -When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients won't be able to connect. For more information, see [Understanding RPC Client Access](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)). +When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients won't be able to connect. For more information, see [Understanding RPC Client Access](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)). ```yaml Type: ClientAccessServerOrArrayIdParameter @@ -1011,12 +948,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Set-MailboxDatabaseCopy.md b/exchange/exchange-ps/exchange/Set-MailboxDatabaseCopy.md similarity index 94% rename from exchange/exchange-ps/exchange/database-availability-groups/Set-MailboxDatabaseCopy.md rename to exchange/exchange-ps/exchange/Set-MailboxDatabaseCopy.md index 361d78e9c1..7a63396766 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Set-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/exchange/Set-MailboxDatabaseCopy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/set-mailboxdatabasecopy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-MailboxDatabaseCopy @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-MailboxDatabaseCopy cmdlet to configure the properties of a database copy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -30,13 +29,14 @@ Set-MailboxDatabaseCopy [-Identity] [-ReplayLagMaxDelay ] [-ReplayLagTime ] [-TruncationLagTime ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION With this cmdlet, you can configure the replay lag time, truncation lag time, and activation preference value for a mailbox database copy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -91,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -225,12 +224,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxExportRequest.md b/exchange/exchange-ps/exchange/Set-MailboxExportRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/mailboxes/Set-MailboxExportRequest.md rename to exchange/exchange-ps/exchange/Set-MailboxExportRequest.md index e9c54df155..400403f687 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxExportRequest.md +++ b/exchange/exchange-ps/exchange/Set-MailboxExportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailboxexportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-MailboxExportRequest @@ -17,19 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Set-MailboxExportRequest cmdlet to change export request options after the request has been created. You can use the Set-MailboxExportRequest cmdlet to recover from failed export requests. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Rehome ``` -Set-MailboxExportRequest [-Identity] [-RehomeRequest] +Set-MailboxExportRequest [-Identity] + [-RehomeRequest] [-Confirm] [-DomainController ] [-RequestExpiryInterval ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Identity @@ -48,13 +49,14 @@ Set-MailboxExportRequest [-Identity] [-RemoteHostName ] [-RequestExpiryInterval ] [-SkipMerging ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can pipeline the Set-MailboxExportRequest cmdlet from the Get-MailboxExportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,7 +70,7 @@ This example changes the second export request Ayla\\MailboxExport1 to accept up ## PARAMETERS ### -Identity -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: \\\\. +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 @@ -142,8 +144,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -212,9 +213,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -237,19 +237,12 @@ Accept wildcard characters: False 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 - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml @@ -266,7 +259,9 @@ Accept wildcard characters: False ``` ### -RehomeRequest -The RehomeRequest parameter specifies to 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. This parameter is used primarily for debugging purposes. +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. ```yaml Type: SwitchParameter @@ -333,7 +328,6 @@ Accept wildcard characters: False 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. - - If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -374,12 +368,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/Set-MailboxFolderPermission.md new file mode 100644 index 0000000000..52df63f5f3 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailboxFolderPermission.md @@ -0,0 +1,323 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailboxFolderPermission + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-MailboxFolderPermission cmdlet to modify folder-level permissions for users in mailboxes. This cmdlet differs from the Add-MailboxFolderPermission cmdlet in that it modifies existing permission entries. To configure calendar publishing or sharing settings for a mailbox so calendar information is visible to external users, use the Set-MailboxCalendarFolder cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MailboxFolderPermission [-Identity] -AccessRights -User + [-Confirm] + [-DomainController ] + [-SendNotificationToUser ] + [-SharingPermissionFlags ] + [-WhatIf] + [] +``` + +## DESCRIPTION +In Exchange Online PowerShell, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user will no longer be a delegate and will only have Editor permissions to the folder. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailboxFolderPermission -Identity ayla@contoso.com:\Marketing -User ed@contoso.com -AccessRights Owner +``` + +This example overwrites Ed's existing permissions for the Marketing folder in Ayla's mailbox. Ed is now granted the Owner role on the folder. + +### Example 2 +```powershell +Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SharingPermissionFlags Delegate -SendNotificationToUser $true +``` + +In Exchange Online, this example resends the sharing invitation to an existing delegate without changing their effective permissions (Ed is already a delegate with Editor permissions to Ayla's mailbox). + +### Example 3 +```powershell +Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SharingPermissionFlags Delegate +``` + +In Exchange Online, this example removes access to private items for an existing delegate. + +### Example 4 +```powershell +Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SharingPermissionFlags None +``` + +In Exchange Online, this example changes an existing calendar delegate to Editor. + +### Example 5 +```powershell +Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor +``` + +In Exchange Online, this example changes an existing user's permissions to Editor without changing their current delegate status. + +### Example 6 +```powershell +Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SendNotificationToUser $false +``` + +In Exchange Online, this example changes an existing user's permissions to Editor and removes their current delegate status. + +## PARAMETERS + +### -Identity +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inbox\Reports`. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccessRights +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. + +The following individual permissions are available: + +- None: The user has no access to view or interact with the folder or its contents. +- CreateItems: The user can create items in the specified folder. +- CreateSubfolders: The user can create subfolders in the specified folder. +- DeleteAllItems: The user can delete all items in the specified folder. +- DeleteOwnedItems: The user can only delete items that they created from the specified folder. +- EditAllItems: The user can edit all items in the specified folder. +- EditOwnedItems: The user can only edit items that they created in the specified folder. +- FolderContact: The user is the contact for the specified public folder. +- FolderOwner: The user is the owner of the specified folder. The user can view the folder, move the folder, and create subfolders. The user can't read items, edit items, delete items, or create items. +- FolderVisible: The user can view the specified folder, but can't read or edit items within the specified public folder. +- ReadItems: The user can read items within the specified folder. + +The roles that are available, along with the permissions that they assign, are described in the following list: + +- Author: CreateItems, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems +- Contributor: CreateItems, FolderVisible +- Editor: CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems +- NonEditingAuthor: CreateItems, DeleteOwnedItems, FolderVisible, ReadItems +- Owner: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderContact, FolderOwner, FolderVisible, ReadItems +- PublishingAuthor: CreateItems, CreateSubfolders, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems +- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems +- Reviewer: FolderVisible, ReadItems + +The following roles apply specifically to calendar folders: + +- AvailabilityOnly: View only availability data +- LimitedDetails: View availability data with subject and location + +When the Editor role is applied to calendar folders, delegates can accept or decline meetings by manually selecting the meeting request in the mailbox. In Exchange Online, to send meeting requests to delegates where they can accept or decline meetings, also use the SharingPermissionFlags parameter with the value Delegate. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +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: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user or group. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendNotificationToUser +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: + +- $true: A sharing invitation is sent. +- $false: No sharing invitation is sent. This is the default value. + +This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values: + +- AvailabilityOnly +- LimitedDetails +- Reviewer +- Editor + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharingPermissionFlags +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: + +- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This is the default value when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter. +- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. +- CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value. + +You can specify multiple values separated by commas. + +```yaml +Type: MailboxFolderPermissionFlags +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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 + +[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission) + +[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission) + +[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission) + +[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission) diff --git a/exchange/exchange-ps/exchange/Set-MailboxIRMAccess.md b/exchange/exchange-ps/exchange/Set-MailboxIRMAccess.md new file mode 100644 index 0000000000..aab760df38 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailboxIRMAccess.md @@ -0,0 +1,130 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailboxIRMAccess + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-MailboxIRMAccess cmdlet to block delegate access to IRM-protected messages in other mailboxes (shared mailboxes or user mailboxes where delegates have Full Access permission). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MailboxIRMAccess -AccessLevel [-Identity] -User [] +``` + +## DESCRIPTION +> [!NOTE] +> This cmdlet works only for delegates who 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). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailboxIRMAccess -Identity lynette@contoso.onmicrosoft.com -User chris@contoso.onmicrosoft.com -AccessLevel Block +``` + +This example prevents delegate Chris from reading IRM-protected messages in Lynette's mailbox. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AccessLevel +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. + +To allow access to IRM-protected messages in the mailbox, use the Remove-MailboxIRMAccess cmdlet. + +```yaml +Type: IRMAccessLevel +Parameter Sets: (All) +Aliases: +Accepted values: Block +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +**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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: SecurityPrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxImportRequest.md b/exchange/exchange-ps/exchange/Set-MailboxImportRequest.md similarity index 85% rename from exchange/exchange-ps/exchange/mailboxes/Set-MailboxImportRequest.md rename to exchange/exchange-ps/exchange/Set-MailboxImportRequest.md index 3d17987b4d..07b606b809 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxImportRequest.md +++ b/exchange/exchange-ps/exchange/Set-MailboxImportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailboximportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailboxImportRequest @@ -17,22 +16,12 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailboxImportRequest cmdlet to change import request options after the request has been created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX -### Rehome -``` -Set-MailboxImportRequest [-Identity] [-RehomeRequest] - [-AzureSharedAccessSignatureToken ] - [-Confirm] - [-DomainController ] - [-RequestExpiryInterval ] - [-WhatIf] [] -``` - ### Identity ``` Set-MailboxImportRequest [-Identity] @@ -46,17 +35,29 @@ Set-MailboxImportRequest [-Identity] [-InternalFlags ] [-LargeItemLimit ] [-Priority ] - [-RemoteCredential ] - [-RemoteHostName ] [-RequestExpiryInterval ] + [-SkipInitialConnectionValidation] [-SkipMerging ] - [-WhatIf] [] + [-SkippedItemApprovalTime ] + [-WhatIf] + [] +``` + +### Rehome +``` +Set-MailboxImportRequest [-Identity] [-RehomeRequest] + [-Confirm] + [-DomainController ] + [-RehomeRequest] + [-RequestExpiryInterval ] + [-WhatIf] + [] ``` ## DESCRIPTION You can pipeline the Set-MailboxImportRequest cmdlet from the Get-MailboxImportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,7 +78,7 @@ This example finds all import requests that have a status of Suspended, and then ## PARAMETERS ### -Identity -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: \\\\. +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 @@ -92,36 +93,36 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -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. +### -AzureSharedAccessSignatureToken +This parameter is available only in the cloud-based service. -In Exchange 2010, you need to use this switch if you set the BadItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. +This parameter is reserved for internal Microsoft use. ```yaml -Type: SwitchParameter -Parameter Sets: Identity +Type: String +Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online -Required: False +Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -AzureSharedAccessSignatureToken -This parameter is available only in the cloud-based service. +### -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. -PARAMVALUE: String +In Exchange 2010, you need to use this switch if you set the BadItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. ```yaml -Type: String -Parameter Sets: (All) +Type: SwitchParameter +Parameter Sets: Identity Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -187,8 +188,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -245,9 +245,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -274,19 +273,12 @@ 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: - Lowest - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml @@ -305,7 +297,9 @@ Accept wildcard characters: False ### -RehomeRequest This parameter is available only in on-premises Exchange. -The RehomeRequest parameter specifies to the Microsoft Exchange Mailbox Replication service (MRS) that the request needs to be moved to the same database as the mailbox being imported. This parameter is used primarily for debugging purposes. +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. + +This switch is used primarily for debugging purposes. ```yaml Type: SwitchParameter @@ -320,18 +314,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RemoteCredential -This parameter is available only in on-premises Exchange. +### -RequestExpiryInterval +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. +- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. -The RemoteCredential parameter specifies the username and password an administrator who has permission to perform the mailbox import request. +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. -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://go.microsoft.com/fwlink/p/?linkId=142122). +When you use the value Unlimited, the completed request isn't automatically removed. ```yaml -Type: PSCredential -Parameter Sets: Identity +Type: Unlimited +Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -340,16 +337,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RemoteHostName -This parameter is available only in on-premises Exchange. +### -SkipInitialConnectionValidation +This parameter is available only in the cloud-based service -The RemoteHostName parameter specifies the FQDN of the cross-forest organization from which you're configuring the import request. +This parameter is reserved for internal Microsoft use. ```yaml -Type: Fqdn +Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Online Required: False Position: Named @@ -358,22 +355,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RequestExpiryInterval -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. - -- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. - -To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. - -When you use the value Unlimited, the completed request isn't automatically removed. +### -SkipMerging +The SkipMerging parameter specifies the steps in the import that should be skipped. This parameter is used primarily for debugging purposes. ```yaml -Type: Unlimited -Parameter Sets: (All) +Type: SkippableMergeComponent[] +Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -382,14 +371,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SkipMerging -The SkipMerging parameter specifies the steps in the import that should be skipped. This parameter is used primarily for debugging purposes. +### -SkippedItemApprovalTime +This parameter is available only in the cloud-based service + +This parameter is reserved for internal Microsoft use. ```yaml -Type: SkippableMergeComponent[] +Type: System.DateTime Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -419,12 +410,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/exchange/Set-MailboxJunkEmailConfiguration.md new file mode 100644 index 0000000000..7392f0f33e --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailboxJunkEmailConfiguration.md @@ -0,0 +1,372 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailboxJunkEmailConfiguration + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-MailboxJunkEmailConfiguration cmdlet to configure the junk email settings on mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MailboxJunkEmailConfiguration [-Identity] + [-BlockedSendersAndDomains ] + [-Confirm] + [-ContactsTrusted ] + [-DomainController ] + [-Enabled ] + [-FailOnError ] + [-IgnoreDefaultScope] + [-SenderScreeningEnabled ] + [-TrustedListsOnly ] + [-TrustedRecipientsAndDomains ] + [-TrustedSendersAndDomains ] + [-WhatIf] + [] +``` + +## DESCRIPTION +This cmdlet controls the following junk email settings on the mailbox: + +- Enable or disable the junk email rule: In on-premises Exchange, the junk email rule (a hidden Inbox rule named Junk E-mail Rule) controls the delivery of messages to the Junk Email folder or the Inbox based on the SCL Junk Email Folder threshold (for the organization or the mailbox) and the safelist collection on the mailbox. + + In the cloud-based service, the junk email rule has no effect on mail flow. Exchange Online Protection delivers messages to the Junk Email folder based on the actions set in anti-spam policies. The junk email rule on the mailbox still controls what happens to messages after delivery based on the safelist collection of the mailbox. + + Users can enable or disable the junk email rule in their own mailbox by using Outlook on the web. + +- Configure the safelist collection: The safelist collection is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list. Users can configure the safelist collection on their own mailbox by using Microsoft Outlook or Outlook on the web. + +For more information, see [Configure Exchange antispam settings on mailboxes](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailboxJunkEmailConfiguration "David Pelton" -Enabled $false +``` + +This example disables the junk email rule for the user named David Pelton. In on-premises Exchange, messages are no longer moved between the Inbox and the Junk Email folder based on the SCL Junk Email Folder threshold (organization or mailbox) or the safelist collection of the mailbox. In Exchange Online, the safelist collection of the mailbox is unable to move messages between the Inbox and the Junk Email folder. Messages are still delivered to the Junk Email folder based on the verdict and corresponding action of anti-spam policies. + +### Example 2 +```powershell +Set-MailboxJunkEmailConfiguration "Michele Martin" -TrustedSendersAndDomains @{Add="contoso.com","fabrikam.com"} -BlockedSendersAndDomains @{Add="jane@fourthcoffee.com"} +``` + +This example makes the following configuration changes to the safelist collection for the user named Michele Martin: + +- Adds contoso.com and fabrikam.com to the Safe Senders list without affecting other existing entries. +- Adds jane@fourthcoffee.com to the Blocked senders list without affecting other existing entries. + +### Example 3 +```powershell +Get-MailboxJunkEmailConfiguration * | Where {$_.ContactsTrusted -eq $true} | Set-MailboxJunkEmailConfiguration -ContactsTrusted $false +``` + +This example identifies mailboxes where contacts are treated as trusted senders and then changes the junk email configuration to not treat contacts as trusted senders. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BlockedSendersAndDomains +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContactsTrusted +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. +- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. + + In on-premises Exchange, the safelist collection of the mailbox (the Safe Senders list, Safe Recipients list, and Blocked Senders list), and the SCL Junk Email folder threshold (for the organization or the mailbox) delivers messages to the Inbox or the Junk Email folder. + + In the cloud-based service, the safelist collection of the mailbox moves delivered messages between the Inbox or the Junk Email folder. Messages are delivered to the Junk Email folder based on the verdict and corresponding action of anti-spam policies only. + +- $false: The junk email rule is disabled in the mailbox. This value corresponds to the Outlook on the web setting: Don't move email to my Junk Email folder. + + In on-premises Exchange, the safelist collection of the mailbox or the SCL Junk Email folder threshold are unable to deliver messages to the Inbox or the Junk Email folder. + + In the cloud-based service, the safelist collection of the mailbox is unable to move delivered messages between the Inbox or the Junk Email folder. Messages are still delivered to the Junk Email folder based on the verdict and corresponding action of anti-spam policies. + +You can view the status of the junk email rule by running either of the following commands to find the Enabled property value: + +- `Get-MailboxJunkEmailConfiguration -Identity ` +- On-premises Exchange only: `Get-InboxRule "Junk E-mail Rule" -Mailbox -IncludeHidden` + +The state of the junk email rule on the mailbox doesn't affect the client-side junk email settings that are available in the Outlook Junk Email Filter. Even when the junk email rule is disabled in the mailbox, Outlook can still move messages to the Junk Email folder. For example, if Outlook determines the message is spam, or the sender is defined in the Blocked Senders list, Outlook can move the message to the Junk Email folder. For more information, see [Overview of the Junk Email Filter](https://support.microsoft.com/office/5ae3ea8e-cf41-4fa0-b02a-3b96e21de089). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FailOnError +This parameter is available only in the cloud-based service. + +{{ Fill FailOnError Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderScreeningEnabled +This parameter is available only in the cloud-based service. + +{{ Fill SenderScreeningEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrustedListsOnly +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. +- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrustedRecipientsAndDomains +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrustedSendersAndDomains +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +To empty the list of email addresses and domains, use the value $null. + +**Notes**: + +- You can't add sender email addresses from the same domain as the recipient's email address. All mailboxes in the global address list (GAL) are automatically considered as trusted senders. +- You can't directly modify the Safe Recipients list by using this cmdlet. You use this parameter to modify the Safe Senders list, and the email addresses and domains are synchronized to the Safe Recipients list. +- In standalone EOP with directory synchronization, domain entries aren't synchronized by default, but you can enable synchronization for domains. For more information, see [Configure Content Filtering to Use Safe Domain Data](/exchange/configure-content-filtering-to-use-safe-domain-data-exchange-2013-help). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-MailboxMessageConfiguration.md b/exchange/exchange-ps/exchange/Set-MailboxMessageConfiguration.md new file mode 100644 index 0000000000..047f4af452 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailboxMessageConfiguration.md @@ -0,0 +1,1420 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailboxMessageConfiguration + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-MailboxMessageConfiguration cmdlet to configure the Outlook on the web settings that are applied to specific mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MailboxMessageConfiguration [-Identity] + [-AfterMoveOrDeleteBehavior ] + [-AlwaysShowBcc ] + [-AlwaysShowFrom ] + [-AutoAddSignature ] + [-AutoAddSignatureOnMobile ] + [-AutoAddSignatureOnReply ] + [-CheckForForgottenAttachments ] + [-CheckForReportJunkDialog ] + [-Confirm] + [-ConversationSortOrder ] + [-DefaultFontColor ] + [-DefaultFontFlags ] + [-DefaultFontName ] + [-DefaultFontSize ] + [-DefaultFormat ] + [-DefaultSignature ] + [-DefaultSignatureOnReply ] + [-DeleteSignatureName ] + [-DisplayDensityMode ] + [-DomainController ] + [-EchoGroupMessageBackToSubscribedSender ] + [-EmailComposeMode ] + [-EmptyDeletedItemsOnLogoff ] + [-FavoritesBitFlags ] + [-GlobalReadingPanePosition ] + [-HideDeletedItems ] + [-IgnoreDefaultScope] + [-IsDarkModeTheme ] + [-IsFavoritesFolderTreeCollapsed ] + [-IsFocusedInboxEnabled ] + [-IsMailRootFolderTreeCollapsed ] + [-IsReplyAllTheDefaultResponse ] + [-LinkPreviewEnabled ] + [-MailFolderPaneExpanded ] + [-MailSendUndoInterval ] + [-ManuallyPickCertificate ] + [-NavigationBarWidth ] + [-NavigationPaneViewOption ] + [-NewEnabledPonts ] + [-NewItemNotification ] + [-PreferAccessibleContent ] + [-PreviewMarkAsReadBehavior ] + [-PreviewMarkAsReadDelaytime ] + [-ReadReceiptResponse ] + [-ReportJunkSelected ] + [-SendAddressDefault ] + [-ShowConversationAsTree ] + [-ShowInlinePreviews ] + [-ShowNotificationBar ] + [-ShowPreviewTextInListView ] + [-ShowReadingPaneOnFirstLoad ] + [-ShowSenderOnTopInListView ] + [-ShowUpNext ] + [-SignatureHtml ] + [-SignatureHtmlBody ] + [-SignatureName ] + [-SignatureText ] + [-SignatureTextOnMobile ] + [-SigningCertificateId ] + [-SigningCertificateSubject ] + [-SmimeEncrypt ] + [-SmimeSign ] + [-UseDefaultSignatureOnMobile ] + [-WebSuggestedRepliesEnabledForUser ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The Set-MailboxMessageConfiguration cmdlet configures Outlook on the web settings for the specified mailbox. These settings include email signature, message format, message options, read receipts, reading pane, and conversations. These settings are not used in Outlook, Exchange ActiveSync, or other email clients. These settings are applied in Outlook on the web only. Some settings also apply to the new Outlook client. Settings that contain the word Mobile are applied in Outlook on the web for devices only. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailboxMessageConfiguration kai@contoso.com -HideDeletedItems $true +``` + +This example sets items deleted from a conversation thread to not show in the list view of the conversation in Outlook on the web for Kai's mailbox. + +### Example 2 +```powershell +Set-MailboxMessageConfiguration kai@contoso.com -AlwaysShowBcc $true +``` + +This example sets the compose email message form to always show the Bcc field in Outlook on the web for Kai's mailbox. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AfterMoveOrDeleteBehavior +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 +- OpenNextItem +- ReturnToView + +The default value is OpenNextItem. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlwaysShowBcc +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlwaysShowFrom +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoAddSignature +**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: + +- $true: Email signatures are automatically added to new messages. +- $false: Email signatures aren't automatically added to new messages. + +The email signature specified by the SignatureText parameter is added to plain text messages. The email signature specified by the SignatureHTML parameter is added to HTML-formatted 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoAddSignatureOnMobile +**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. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoAddSignatureOnReply +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. +- $false: Email signatures aren't automatically added to reply messages. + +The email signature specified by the SignatureText parameter is added to plain text messages. The email signature specified by the SignatureHTML parameter is added to HTML-formatted messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CheckForForgottenAttachments +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. + +For example, the user creates a message that includes the text "Please see the attached Word document", but the user doesn't attach a file, and clicks Send. If this value is set to $true, the user gets a warning prompt so they can go back to the message and attach a file. If this value is set to $false, the user doesn't get the warning prompt. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CheckForReportJunkDialog +This parameter is available only in the cloud-based service. + +{{ Fill CheckForReportJunkDialog Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConversationSortOrder +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 +- Tree +- NewestOnTop +- NewestOnBottom +- ChronologicalNewestOnTop +- ChronologicalNewestOnBottom +- TreeNewestOnBottom + +The default value is ChronologicalNewestOnTop. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultFontColor +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultFontFlags +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 +- Bold +- Italic +- Underline +- All + +The default value is Normal. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultFontName +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultFontSize +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultFormat +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultSignature +This parameter is available only in the cloud-based service. + +{{ Fill DefaultSignature Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultSignatureOnReply +This parameter is available only in the cloud-based service. + +{{ Fill DefaultSignatureOnReply Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeleteSignatureName +This parameter is available only in the cloud-based service. + +{{ Fill DeleteSignatureName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayDensityMode +This parameter is available only in the cloud-based service. + +{{ Fill DisplayDensityMode Description }} + +```yaml +Type: DisplayDensityMode +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EchoGroupMessageBackToSubscribedSender +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: + +- $true: If a subscribed member of a Microsoft 365 Group sends a message to that Group, they'll receive a copy of the message in their Inbox. +- $false: Subscribed members of a Microsoft 365 Group don't receive their own copies of messages that they send to the Group. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailComposeMode +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: + +- Inline: New messages and replies are created in the preview pane. This is the default value. +- SeparateForm: New messages and replies are created in a new browser window. + +```yaml +Type: EmailComposeMode +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmptyDeletedItemsOnLogoff +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FavoritesBitFlags +This parameter is available only in the cloud-based service. + +{{ Fill FavoritesBitFlags Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GlobalReadingPanePosition +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: + +- Off +- Bottom +- Right (This is the default value) + +```yaml +Type: MailReadingPanePosition +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HideDeletedItems +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDarkModeTheme +This parameter is available only in the cloud-based service. + +{{ Fill IsDarkModeTheme Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsFavoritesFolderTreeCollapsed +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. +- $false: The Favorites folder tree isn't collapsed by default. This is the default value + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsFocusedInboxEnabled +This parameter is available only in the cloud-based service. + +{{ Fill IsFocusedInboxEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsMailRootFolderTreeCollapsed +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. +- $false: The Mail root folder tree isn't collapsed by default. This is the default value + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsReplyAllTheDefaultResponse +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. +- $false: Reply All isn't the default response option for messages in the reading pane. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LinkPreviewEnabled +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. +- $false: Link preview of URLs in email messages is disabled for the user. + +This parameter depends on the value of the LinkPreviewEnabled parameter on the Set-OrganizationConfig cmdlet, which controls the link preview behavior in Outlook on the web for the entire organization. If link preview is disabled for the organization, users can't enable it for themselves. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailFolderPaneExpanded +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. +- $false: The Mail folder pane isn't expanded by default. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailSendUndoInterval +This parameter is available only in the cloud-based service. + +{{ Fill MailSendUndoInterval Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManuallyPickCertificate +This parameter is available only in the cloud-based service. + +{{ Fill ManuallyPickCertificate Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NavigationBarWidth +This parameter is available only in the cloud-based service. + +{{ Fill NavigationBarWidth Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NavigationPaneViewOption +The NavigationPaneViewOption parameter specifies the default navigation pane view in Outlook on the web. Valid values are: + +- Default: This is the default value +- MailFolders +- PeopleFolders +- Groups +- PinnedMailFolders + +```yaml +Type: NavigationPaneView +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NewEnabledPonts +This parameter is available only in the cloud-based service. + +{{ Fill NewEnabledPonts Description }} + +```yaml +Type: PontType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NewItemNotification +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 +- EMailToast +- VoiceMailToast +- FaxToast +- None +- All + +The default value is All. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreferAccessibleContent +The PreferAccessibleContent parameter specifies whether to prefer accessible content in Outlook on the web. Valid values are: + +- $true: Prefer accessible content. +- $false: Don't prefer accessible content. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreviewMarkAsReadBehavior +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. +- OnSelectionChange +- Never + +The default value is OnSelectionChange. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreviewMarkAsReadDelaytime +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. + +This parameter is meaningful only if you set the PreviewMarkAsReadBehavior parameter to the value Delayed. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadReceiptResponse +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 +- AlwaysSend +- NeverSend + +The default value is DoNotAutomaticallySend. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportJunkSelected +This parameter is available only in the cloud-based service. + +{{ Fill ReportJunkSelected Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendAddressDefault +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. + +You can use one of the following values: + +- Blank, which is represented by the value $null. This indicates no default From address is specified. +- The user's primary email address. For example, bob@contoso.com. +- The GUID of a POP, IMAP, or Hotmail subscription that's configured on the user's mailbox. + +By default, no default From address is specified on the mailbox. When no default From address is specified, the default behavior is: + +- The primary email address on the mailbox is used for all new messages. +- The To address of the incoming message is used as the From address for all replies or forwarded messages. + +You can find the available values for SendAddressDefault on a mailbox by running the command: `Get-MailboxMessageConfiguration -Mailbox | Format-List SendAddressDefault`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowConversationAsTree +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowInlinePreviews +This parameter is available only in the cloud-based service. + +{{ Fill ShowInlinePreviews Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowNotificationBar +This parameter is available only in the cloud-based service. + +{{ Fill ShowNotificationBar Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowPreviewTextInListView +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. +- $false: Don't show preview text for messages in list view. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowReadingPaneOnFirstLoad +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. +- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowSenderOnTopInListView +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. +- $false: Don't show the message sender on top in list view. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowUpNext +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. +- $false: Don't show the next upcoming event above the mail list view. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignatureHtml +**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. + +To automatically add this email signature to HTML-formatted messages created by the user in Outlook on the web, the AutoAddSignature parameter must be set to $true. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignatureHtmlBody +This parameter is available only in the cloud-based service. + +{{ Fill SignatureHtmlBody Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignatureName +This parameter is available only in the cloud-based service. + +{{ Fill SignatureName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignatureText +**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. + +To automatically add the email signature to plain text messages created by the user in Outlook on the web, the AutoAddSignature parameter must be set to the value $true. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignatureTextOnMobile +**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. + +To automatically add the email signature to messages created by the user in Outlook on the web for devices, the AutoAddSignatureOnMobile parameter must be set to the value $true. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SigningCertificateId +This parameter is available only in the cloud-based service. + +{{ Fill SigningCertificateId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SigningCertificateSubject +This parameter is available only in the cloud-based service. + +{{ Fill SigningCertificateSubject Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SmimeEncrypt +This parameter is available only in the cloud-based service. + +{{ Fill SmimeEncrypt Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SmimeSign +This parameter is available only in the cloud-based service. + +{{ Fill SmimeSign Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseDefaultSignatureOnMobile +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. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebSuggestedRepliesEnabledForUser +This parameter is available only in the cloud-based service. + +{{ Fill WebSuggestedRepliesEnabledForUser Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-MailboxPlan.md b/exchange/exchange-ps/exchange/Set-MailboxPlan.md new file mode 100644 index 0000000000..96b60c149b --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MailboxPlan.md @@ -0,0 +1,425 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MailboxPlan + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-MailboxPlan cmdlet to modify the settings of mailbox plans in the cloud-based service. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MailboxPlan [-Identity] + [-Confirm] + [-Force] + [-IsDefault] + [-IssueWarningQuota ] + [-MaxReceiveSize ] + [-MaxSendSize ] + [-ProhibitSendQuota ] + [-ProhibitSendReceiveQuota ] + [-RecipientLimits ] + [-RetainDeletedItemsFor ] + [-RetentionPolicy ] + [-RoleAssignmentPolicy ] + [-WhatIf] + [] +``` + +## DESCRIPTION +A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your organization. + +Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which will apply the corresponding mailbox plan to the mailbox. + +Each mailbox plan has a corresponding Client Access services (CAS) mailbox plan with the same name and display name value. You can use the Set-CasMailboxPlan cmdlet to enable or disable POP3, IMAP4 or Exchange ActiveSync (EAS) access to new or newly-enabled mailboxes, and you can specify the Outlook on the web (formerly known as Outlook Web App) mailbox policy for the mailboxes. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MailboxPlan -Identity ExchangeOnlineEnterprise -ProhibitSendReceiveQuota 40GB -ProhibitSendQuota 39.5GB -IssueWarningQuota 39GB +``` + +This example lowers the default mailbox quotas in the mailbox plan named ExchangeOnlineEnterprise. + +## PARAMETERS + +### -Identity +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 +- Alias +- Display name +- Distinguished name (DN) +- GUID + +```yaml +Type: MailboxPlanIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDefault +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IssueWarningQuota +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. + +The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxReceiveSize +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is a number up to 150 MB. The default value is 36 MB. + +The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. + +Use this parameter to change the MaxReceiveSize value for new mailboxes that you create. Use the MaxReceiveSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes. + +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxSendSize +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is a number up to 150 MB. The default value is 35 MB. + +The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. + +Use this parameter to change the MaxSendSize value for new mailboxes that you create. Use the MaxSendSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes. + +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProhibitSendQuota +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. + +The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProhibitSendReceiveQuota +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. + +The maximum value is determined by the mailbox plan. You can lower the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientLimits +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetainDeletedItemsFor +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. +- Selecting the Empty Deleted Items Folder action. +- Deleting items using Shift + Delete. + +These actions move the items to the Recoverable Items folder, into a subfolder named Deletions. + +Before the deleted item retention period expires, users can recover soft-deleted items in Outlook and Outlook on the web by using the Recover Deleted Items feature. For more information, see [Recoverable Items folder in Exchange Online](https://learn.microsoft.com/Exchange/security-and-compliance/recoverable-items-folder/recoverable-items-folder). + +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. + +The default value is 14 days (14.00:00:00). In Exchange Online, you can increase the value to a maximum of 30 days. + +```yaml +Type: EnhancedTimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionPolicy +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 +- Distinguished Name (DN) +- GUID + +Retention policies consist of tags that are applied to mailbox folders and mail items to determine the period of time that the items should be retained. Use the Get-RetentionPolicy cmdlet to see the available retention policies. + +By default, the value of this parameter is blank ($null), which means the default retention policy (the retention policy where the IsDefault property value is True) is assigned to new mailboxes. By default, the default retention policy is named Default MRM Policy. + +If you don't set a value for this parameter, existing mailboxes are also updated if you change which retention policy is the default by using the IsDefault switch on the New-RetentionPolicy or Set-RetentionPolicy cmdlets. + +**Note**: Specifying a value for this parameter has the following potential issues: + +- If the value of this parameter is not blank ($null), then the specified retention policy must be the default Exchange retention policy that's configured for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. +- If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. +- Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. + +For more information, see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). + +```yaml +Type: MailboxPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoleAssignmentPolicy +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 +- Distinguished name (DN) +- GUID + +The default value is Default Role Assignment Policy. + +To see the available role assignment policies, use the Get-RoleAssignmentPolicy cmdlet. + +```yaml +Type: MailboxPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/client-access/Set-MailboxRegionalConfiguration.md b/exchange/exchange-ps/exchange/Set-MailboxRegionalConfiguration.md similarity index 75% rename from exchange/exchange-ps/exchange/client-access/Set-MailboxRegionalConfiguration.md rename to exchange/exchange-ps/exchange/Set-MailboxRegionalConfiguration.md index 31802f3a1d..ef75fd3f02 100644 --- a/exchange/exchange-ps/exchange/client-access/Set-MailboxRegionalConfiguration.md +++ b/exchange/exchange-ps/exchange/Set-MailboxRegionalConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-mailboxregionalconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailboxRegionalConfiguration @@ -17,25 +16,53 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailboxRegionalConfiguration cmdlet to modify the regional settings of a mailbox. You can modify the date format, time format, time zone and language of the mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX +### Default ``` -Set-MailboxRegionalConfiguration [-Identity] - [-Confirm] [-DateFormat ] - [-DomainController ] +Set-MailboxRegionalConfiguration [-Identity] [-DomainController ] + [-Confirm] + [-DateFormat ] [-Language ] [-LocalizeDefaultFolderName] [-TimeFormat ] [-TimeZone ] - [-WhatIf] [] + [-WhatIf] + [] +``` + +### Identity +``` +Set-MailboxRegionalConfiguration [-Identity] [-Archive] [-UseCustomRouting] + [-Confirm] + [-DateFormat ] + [-Language ] + [-LocalizeDefaultFolderName] + [-TimeFormat ] + [-TimeZone ] + [-WhatIf] + [] +``` + +### MailboxLocation +``` +Set-MailboxRegionalConfiguration [-MailboxLocation ] [-UseCustomRouting] + [-Confirm] + [-DateFormat ] + [-Language ] + [-LocalizeDefaultFolderName] + [-TimeFormat ] + [-TimeZone ] + [-WhatIf] + [] ``` ## DESCRIPTION -As shown in Example 5, you might need to set the DateFormat and TimeFormat parameter values to $null when you change the Language parameter value and you recieve an error about invalid DateFormat values. +As shown in Example 5, you might need to set the DateFormat and TimeFormat parameter values to $null when you change the Language parameter value and you receive an error about invalid DateFormat values. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,25 +75,24 @@ This example sets Marcelo Teixeira's mailbox language to Brazilian Portuguese, a ### Example 2 ```powershell -Set-MailboxRegionalConfiguration -Identity "Ella Lack's" -DateFormat "d/m/yyyy" +Set-MailboxRegionalConfiguration -Identity "Ella Lack's" -DateFormat "d/M/yyyy" ``` This example sets the date format for Ella Lack's mailbox. ### Example 3 ```powershell -Set-MailboxRegionalConfiguration -Identity "Alice Jakobsen" -Language da-dk -DateFormat "dd-mm-yyyy" -LocalizeDefaultFolderName +Set-MailboxRegionalConfiguration -Identity "Alice Jakobsen" -Language da-dk -DateFormat "dd-MM-yyyy" -LocalizeDefaultFolderName ``` This example sets Alice Jakobsen's mailbox language to Danish Denmark, sets the date in the day/month/year format and localizes the default folder names in Danish. - ### Example 4 ```powershell Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited | Set-MailboxRegionalConfiguration -Language es-es -DateFormat "dd/MM/yyyy" -TimeFormat H:mm -LocalizeDefaultFolderName ``` -This example sets all User Mailboxes language to Spanish Spain, sets the date in the day/month/year format, sets the time in the H:mm format and localizes the default forder names in Spanish. +This example sets all User Mailboxes language to Spanish Spain, sets the date in the day/month/year format, sets the time in the H:mm format and localizes the default folder names in Spanish. ### Example 5 ```powershell @@ -81,30 +107,21 @@ This example sets Megan Bowen mailbox language to Spanish Argentina, sets the da The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter -Parameter Sets: (All) +Parameter Sets: Default, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -113,18 +130,35 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -Archive +This parameter is available only in the cloud-based service. + +{{ Fill Archive Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -137,20 +171,14 @@ Accept wildcard characters: False 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. - - M/d/yy - - MM/dd/yy - - MM/dd/yyyy - - yy/MM/dd - - yyyy-MM-dd - - dd-MMM-yy -For more information about the date format strings, see [Standard Date and Time Format Strings](https://go.microsoft.com/fwlink/p/?LinkId=784852). +For more information about the date format strings, see [Standard Date and Time Format Strings](https://learn.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings). ```yaml Type: String @@ -172,7 +200,7 @@ The DomainController parameter specifies the domain controller that's used by th ```yaml Type: Fqdn -Parameter Sets: (All) +Parameter Sets: Default Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -186,7 +214,7 @@ Accept wildcard characters: False ### -Language 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://go.microsoft.com/fwlink/p/?linkId=184859). +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). ```yaml Type: CultureInfo @@ -201,6 +229,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MailboxLocation +This parameter is available only in the cloud-based service. + +{{ Fill MailboxLocation Description }} + +```yaml +Type: MailboxLocationIdParameter +Parameter Sets: MailboxLocation +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -LocalizeDefaultFolderName 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. @@ -221,14 +267,11 @@ Accept wildcard characters: False 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. - - hh:mm tt - - H:mm - - HH:mm -For more information about the time format strings, see [Standard Date and Time Format Strings](https://go.microsoft.com/fwlink/p/?LinkId=784852). +For more information about the time format strings, see [Standard Date and Time Format Strings](https://learn.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings). ```yaml Type: String @@ -265,6 +308,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -UseCustomRouting +This parameter is available only in the cloud-based service. + +{{ Fill UseCustomRouting Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, MailboxLocation +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -272,7 +333,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -286,12 +347,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/Set-MailboxRestoreRequest.md similarity index 80% rename from exchange/exchange-ps/exchange/mailboxes/Set-MailboxRestoreRequest.md rename to exchange/exchange-ps/exchange/Set-MailboxRestoreRequest.md index d0d3990c78..a874cb3a60 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/exchange/Set-MailboxRestoreRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailboxrestorerequest -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailboxRestoreRequest @@ -17,20 +16,10 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request has been created. You can use this cmdlet to recover from failed restore requests. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX -### Rehome -``` -Set-MailboxRestoreRequest [-Identity] [-RehomeRequest] - [-Confirm] - [-DomainController ] - [-RemoteHostName ] - [-RequestExpiryInterval ] - [-WhatIf] [] -``` - ### Identity ``` Set-MailboxRestoreRequest [-Identity] @@ -45,13 +34,33 @@ Set-MailboxRestoreRequest [-Identity] [-Priority ] [-RemoteHostName ] [-RequestExpiryInterval ] + [-SkipInitialConnectionValidation] [-SkipMerging ] + [-SkippedItemApprovalTime ] + [-SourceWlmLevel ] + [-TargetWlmLevel ] + [-WhatIf] + [] +``` + +### Rehome +``` +Set-MailboxRestoreRequest [-Identity] + [-Confirm] + [-DomainController ] + [-RehomeRequest] + [-RemoteHostName ] + [-RequestExpiryInterval ] + [-SkipInitialConnectionValidation] + [-SkippedItemApprovalTime ] + [-SourceWlmLevel ] + [-TargetWlmLevel ] [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,7 +81,7 @@ This example changes the first restore request for Kweku's mailbox to skip 100 c ## PARAMETERS ### -Identity -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: \\\\ +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). @@ -80,7 +89,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -168,15 +177,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -186,7 +194,7 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. +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. @@ -194,7 +202,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -204,7 +212,7 @@ Accept wildcard characters: False ``` ### -InternalFlags -This parameter is available only in on-premises Exchange. +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. @@ -212,7 +220,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -226,9 +234,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -250,31 +257,24 @@ Accept wildcard characters: False ``` ### -Priority -This parameter is available only in on-premises Exchange. +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: - Lowest - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml Type: RequestPriority Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -284,15 +284,17 @@ Accept wildcard characters: False ``` ### -RehomeRequest -This parameter is available only in on-premises Exchange. +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. -The RehomeRequest switch specifies that the mailbox restore request be moved to a different mailbox database. Use this parameter to edit a mailbox restore request in the case where the source mailbox database from the original move request has to be removed. +Use this switch to edit a mailbox restore request in the case where the source mailbox database from the original move request has to be removed. ```yaml Type: SwitchParameter Parameter Sets: Rehome Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -308,7 +310,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -321,7 +323,6 @@ Accept wildcard characters: False 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. - - If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. @@ -341,13 +342,30 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SkipInitialConnectionValidation +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -SkipMerging The SkipMerging parameter specifies folder-related items to skip when restoring the mailbox. Use one of the following values: -- FolderRules - - FolderACLs - +- FolderProperties +- FolderRules - InitialConnectionValidation Use this parameter only if a restore request fails because of folder rules, folder access control lists (ACLs), or initial connection validation. @@ -365,6 +383,60 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SkippedItemApprovalTime +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: DateTime +Parameter Sets: Identity, Rehome +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceWlmLevel +This parameter is available only in the cloud-based service. + +{{ Fill SourceWlmLevel Description }} + +```yaml +Type: WlmLevel +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetWlmLevel +This parameter is available only in the cloud-based service. + +{{ Fill TargetWlmLevel Description }} + +```yaml +Type: WlmLevel +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -372,7 +444,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -386,12 +458,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-MailboxSearch.md b/exchange/exchange-ps/exchange/Set-MailboxSearch.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-MailboxSearch.md rename to exchange/exchange-ps/exchange/Set-MailboxSearch.md index 1bbfa67c98..ee2ec50572 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-MailboxSearch.md +++ b/exchange/exchange-ps/exchange/Set-MailboxSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/set-mailboxsearch -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-Mailboxsearch @@ -17,7 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailboxSearch cmdlet to modify an existing mailbox search. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +**Note**: As of October 2020, the \*-MailboxSearch cmdlets are retired in Exchange Online PowerShell. Use the \*-ComplianceSearch cmdlets in Security & Compliance PowerShell instead. For more information, see [Retirement of legacy eDiscovery tools](https://learn.microsoft.com/purview/ediscovery-legacy-retirement). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -50,25 +51,26 @@ Set-Mailboxsearch [-Identity] [-StatisticsStartIndex ] [-StatusMailRecipients ] [-TargetMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -In on-premises Exchange and Exchange Online, mailbox searches are used for In-Place eDiscovery and In-Place Hold. For In-Place eDiscovery, unless specified, mailboxes on all Mailbox servers in an organization are searched. To create an In-Place Hold, you need to specify the mailboxes to place on hold using the SourceMailboxes parameter. The search can be stopped, started, modified, and removed. +In on-premises Exchange, mailbox searches are used for In-Place eDiscovery and In-Place Hold. For In-Place eDiscovery, unless specified, mailboxes on all Mailbox servers in an organization are searched. To create an In-Place Hold, you need to specify the mailboxes to place on hold using the SourceMailboxes parameter. The search can be stopped, started, modified, and removed. -By default, mailbox searches are performed across all Exchange 2016 and Exchange 2013 Mailbox servers in an Exchange organization, unless you constrain the search to fewer mailboxes by using the SourceMailboxes parameter. To search mailboxes on Exchange 2010 Mailbox servers, run the command on an Exchange 2010 server. +By default, mailbox searches are performed across all Exchange 2013 or later Mailbox servers in an organization, unless you constrain the search to fewer mailboxes by using the SourceMailboxes parameter. To search mailboxes on Exchange 2010 Mailbox servers, run the command on an Exchange 2010 server. If the In-Place eDiscovery search you want to modify is running, stop it before using the Set-MailboxSearch cmdlet. When restarting a search, any previous search results are removed from the target mailbox. -For more information, see [In-Place eDiscovery in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/holds/holds). +For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-MailboxSearch -Identity "Legal-ProjectX" -StartDate "01/01/2016" +Set-MailboxSearch -Identity "Legal-ProjectX" -StartDate "01/01/2017" ``` This example modifies the start date of a mailbox search. @@ -80,9 +82,7 @@ Set-MailboxSearch -Identity "Legal-ProjectX" -AllPublicFolderSources $true In on-premises Exchange, this example adds all public folders to the existing mailbox search named Legal-ProjectX. -Note: - -If we wanted to place the results of this search on In-Place Hold, the AllSourceMailboxes parameter must be set to $false. We could still include specific mailboxes in the search by using the SourceMailboxes parameter. +**Note**: If we wanted to place the results of this search on In-Place Hold, the AllSourceMailboxes parameter must be set to $false. We could still include specific mailboxes in the search by using the SourceMailboxes parameter. ## PARAMETERS @@ -102,20 +102,36 @@ Accept pipeline input: True Accept wildcard characters: False ``` -### -AllSourceMailboxes -This parameter is available only in on-premises Exchange. +### -AllPublicFolderSources +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]). +- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllSourceMailboxes 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]). - - $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -127,15 +143,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -179,9 +194,11 @@ Accept wildcard characters: False ``` ### -DoNotIncludeArchive -This parameter is available or functional only in 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. -The DoNotIncludeArchive parameter specifies whether items in the user's Archive mailbox are included in mailbox searches. By default, items in the user's Archive mailbox are included in mailbox searches. If set to $true, the DoNotIncludeArchive parameter instructs Multi-Mailbox Search to exclude archive mailboxes from the search. +By default, items in the user's Archive mailbox are included in mailbox searches. ```yaml Type: SwitchParameter @@ -199,7 +216,7 @@ Accept wildcard characters: False ### -EndDate 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". +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". To clear the end date, use the value $null. @@ -217,11 +234,7 @@ Accept wildcard characters: False ``` ### -EstimateOnly -The EstimateOnly parameter specifies whether to provide only an estimate of the number of items that will be returned. Valid values are: - -- $true: Messages aren't copied to the target mailbox, and only an estimate of the number of items is returned. - -- $false: Messages are copied to the target mailbox. +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 @@ -240,7 +253,6 @@ Accept wildcard characters: False 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. - - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes. ```yaml @@ -257,9 +269,9 @@ Accept wildcard characters: False ``` ### -Force -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. +The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -Use this to switch suppress the confirmation prompt that indicates the previous search results will be removed from the target mailbox, and that the search will be restarted. +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. ```yaml Type: SwitchParameter @@ -294,7 +306,6 @@ Accept wildcard characters: False 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. - - $false: Unsearchable items aren't included in the results. This is the default value. 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. @@ -316,7 +327,6 @@ Accept wildcard characters: False 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. - - $false: In-Place Hold isn't enabled on the search results. This is the default value. You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true. @@ -327,7 +337,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -340,14 +350,13 @@ Accept wildcard characters: False 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. - - The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -359,7 +368,7 @@ Accept wildcard characters: False ### -Language 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://go.microsoft.com/fwlink/p/?linkId=184859). +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). ```yaml Type: CultureInfo @@ -378,9 +387,7 @@ Accept wildcard characters: False 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. - - Full: In addition to details in the Basic logging level, a full list of all messages returned is included. - - Suppress: Logging is suppressed. No logs are kept. ```yaml @@ -400,19 +407,12 @@ Accept wildcard characters: False The MessageTypes parameter specifies the message types to include in the search query. Valid values are: - Contacts - - Docs - - Email - - IM - - Journals - - Meetings - - Notes - - Tasks You can specify multiple values separated by commas. @@ -471,7 +471,7 @@ Accept wildcard characters: False ``` ### -SearchDumpster -This parameter is available or functional only in 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. @@ -491,20 +491,16 @@ Accept wildcard characters: False ``` ### -SearchQuery -The SearchQuery parameter specifies keywords for the search query by using the Keyword Query Language (KQL). For more information about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). +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. The other search query parameters are: - EndDate - - MessageTypes - - Recipients - - Senders - - StartDate ```yaml @@ -544,18 +540,13 @@ Accept wildcard characters: False The SourceMailboxes parameter specifies the mailboxes to be searched. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. To use this parameter, the AllSourceMailboxes parameter needs to be $false (the default value). @@ -564,7 +555,6 @@ To clear the source mailboxes, use the value $null. To enable In-Place Hold on the search results, you need to set the AllSourceMailboxes parameter to $false (the default value) and configure one or both of the following settings: - Specify one or more source mailboxes by using the SourceMailboxes parameter. - - In on-premises Exchange, set the AllPublicFolderSources parameter to $true. ```yaml @@ -583,7 +573,7 @@ Accept wildcard characters: False ### -StartDate 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". +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". To clear start date, use the value $null. @@ -620,18 +610,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -650,23 +635,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -689,29 +665,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllPublicFolderSources -This parameter is available only in on-premises Exchange. - -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]). - -- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -725,12 +679,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/exchange/Set-MailboxSentItemsConfiguration.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Set-MailboxSentItemsConfiguration.md rename to exchange/exchange-ps/exchange/Set-MailboxSentItemsConfiguration.md index 7d7ebb4c6e..fc78cfa732 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxSentItemsConfiguration.md +++ b/exchange/exchange-ps/exchange/Set-MailboxSentItemsConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailboxsentitemsconfiguration +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxsentitemsconfiguration applicable: Exchange Server 2010 title: Set-MailboxSentItemsConfiguration schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-MailboxSentItemsConfiguration @@ -17,20 +16,24 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-MailboxSentItemsConfiguration cmdlet to modify the Sent Items settings for mailboxes in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-MailboxSentItemsConfiguration [-Confirm] [-DomainController ] [-Identity ] - [-SendAsItemsCopiedTo ] [-SendOnBehalfOfItemsCopiedTo ] [-WhatIf] +Set-MailboxSentItemsConfiguration [-Confirm] + [-DomainController ] + [-Identity ] + [-SendAsItemsCopiedTo ] + [-SendOnBehalfOfItemsCopiedTo ] + [-WhatIf] [] ``` ## DESCRIPTION By default, when you use Send As or Send On Behalf Of to send a message from another mailbox, the message is saved in your Sent Items folder (not in the Sent Items folder of the source mailbox). In Microsoft Exchange Server 2010 Service Pack 3 (SP3), you can save copies messages in the Sent Items folder of the sender and the source mailbox. For example, consider a shared mailbox that receives customer feedback and is monitored by multiple users. When someone responds to a message in the shared mailbox, you can save the message in the Sent Items folder of the shared mailbox and the sender's mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,8 +49,7 @@ This example configures the shared mailbox named "Customer Support Feedback" so ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -83,23 +85,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -119,7 +112,6 @@ Accept wildcard characters: False 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. - - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox. ```yaml @@ -139,7 +131,6 @@ Accept wildcard characters: False 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. - - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox. ```yaml @@ -176,12 +167,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-MailboxServer.md b/exchange/exchange-ps/exchange/Set-MailboxServer.md similarity index 91% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-MailboxServer.md rename to exchange/exchange-ps/exchange/Set-MailboxServer.md index d100f587fb..1e8ce40d3a 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-MailboxServer.md +++ b/exchange/exchange-ps/exchange/Set-MailboxServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/set-mailboxserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-MailboxServer @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-MailboxServer cmdlet to modify the mailbox configuration settings and attributes of Mailbox servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -107,6 +106,7 @@ Set-MailboxServer [-Identity] [-SharingPolicyWorkCycleCheckpoint ] [-SharingSyncWorkCycle ] [-SharingSyncWorkCycleCheckpoint ] + [-SiteMailboxWorkCycle ] [-SiteMailboxWorkCycleCheckpoint ] [-StoreDsMaintenanceWorkCycle ] [-StoreDsMaintenanceWorkCycleCheckpoint ] @@ -125,11 +125,12 @@ Set-MailboxServer [-Identity] [-UMReportingWorkCycle ] [-UMReportingWorkCycleCheckpoint ] [-WacDiscoveryEndpoint ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -195,9 +196,7 @@ In Exchange 2010, this example throttles the TopN Words Assistant and the Unifie 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 - - Distinguished name (DN) - - GUID ```yaml @@ -233,9 +232,7 @@ Accept wildcard characters: False 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. - - GoodAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to six. 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 six, the database doesn't automatically mount. When the copy queue length is less than or equal to six, Exchange attempts to replicate the remaining logs to the passive copy and mounts the database. - - Lossless: The database doesn't automatically mount until all logs that were generated on the active copy have been copied to the passive copy. This setting also causes Active Manager's best copy selection algorithm to sort potential candidates for activation based on the database copy's activation preference value and not its copy queue length. The default value is GoodAvailability. If you specify either BestAvailability or GoodAvailability, and all of the logs from the active copy haven't been replicated to the passive copy, you may lose some mailbox data. However, the Safety Net feature, (which is enabled by default) helps protect against data loss by resubmitting messages that are in Safety Net. @@ -254,7 +251,11 @@ Accept wildcard characters: False ``` ### -CalendarRepairIntervalEndWindow -The CalendarRepairIntervalEndWindow parameter specifies the number of days into the future to repair calendar items in mailboxes on the Mailbox server. The default value is 30. This means the Calendar Repair Assistant repairs meetings in calendars up to 30 days from now. Meetings that are scheduled to occur more than 30 days in the future aren't repaired. +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. + +The default value in Exchange 2013 and Exchange 2010 is 30. This value means the Calendar Repair Assistant repairs meetings in calendars up to 30 days from now. Meetings that are scheduled to occur more than 30 days in the future aren't repaired. ```yaml Type: Int32 @@ -279,13 +280,9 @@ The default value is 500 megabytes (MB). When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -313,11 +310,8 @@ Valid input for this parameter is $true or $false. The default value is $true. The value of this parameter affects the following parameters: - CalendarRepairLogDirectorySizeLimit - - CalendarRepairLogFileAgeLimit - - CalendarRepairLogPath - - CalendarRepairLogSubjectLoggingEnabled ```yaml @@ -418,18 +412,16 @@ Accept wildcard characters: False ``` ### -CalendarRepairSchedule -This parameter is available or functional only in 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. -The syntax for this parameter is: StartDay.Hour:Minute \[AM/PM\]-EndDay.Hour:Minute \[AM/PM\]. You can specify multiple schedules separated by commas: "\","\",..."\". +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"`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -441,11 +433,8 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" - - "Monday.4:30 AM-Monday.5:30 AM","Wednesday.4:30 AM-Wednesday.5:30 AM" (Run on Monday and Wednesday mornings from 4:30 until 5:30.) ```yaml @@ -462,7 +451,7 @@ Accept wildcard characters: False ``` ### -CalendarRepairWorkCycle -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -486,7 +475,7 @@ Accept wildcard characters: False ``` ### -CalendarRepairWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -510,8 +499,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -528,7 +516,7 @@ Accept wildcard characters: False ``` ### -DarTaskStoreTimeBasedAssistantWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -546,7 +534,7 @@ Accept wildcard characters: False ``` ### -DarTaskStoreTimeBasedAssistantWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -568,7 +556,7 @@ The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prev Valid input for this parameter is $true or $false. The default value is $false. -Setting this parameter to $truewon't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked. +Setting this parameter to $true won't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked. ```yaml Type: Boolean @@ -587,9 +575,7 @@ Accept wildcard characters: False 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. - - IntrasiteOnly: The database copy is allowed to be activated only on Mailbox servers in the same Active Directory site. This prevents cross-site failover and activation. - - Unrestricted: There are no special restrictions on activating mailbox database copies on the specified Mailbox server. This is the default value. ```yaml @@ -606,7 +592,7 @@ Accept wildcard characters: False ``` ### -DirectoryProcessorWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -624,7 +610,7 @@ Accept wildcard characters: False ``` ### -DirectoryProcessorWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -683,17 +669,11 @@ If you specify $true, managed folder logging is enabled. Message activity in fol The value of this parameter affects the following parameters: - JournalingLogForManagedFoldersEnabled - - LogDirectorySizeLimitForManagedFolders - - LogFileAgeLimitForManagedFolders - - LogFileSizeLimitForManagedFolders - - LogPathForManagedFolders - - RetentionLogForManagedFoldersEnabled - - SubjectLogForManagedFoldersEnabled ```yaml @@ -728,7 +708,7 @@ Accept wildcard characters: False ``` ### -GroupMailboxWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -746,7 +726,7 @@ Accept wildcard characters: False ``` ### -GroupMailboxWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -764,7 +744,7 @@ Accept wildcard characters: False ``` ### -GroupMetricsGenerationTime -This parameter is available or functional only in 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. @@ -782,7 +762,7 @@ Accept wildcard characters: False ``` ### -InferenceDataCollectionWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -800,7 +780,7 @@ Accept wildcard characters: False ``` ### -InferenceDataCollectionWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -818,7 +798,7 @@ Accept wildcard characters: False ``` ### -InferenceTrainingWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -836,7 +816,7 @@ Accept wildcard characters: False ``` ### -InferenceTrainingWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -854,12 +834,11 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled -This parameter is available or functional only in 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: - $true Enable IRM logging - - $false Disable IRM logging ```yaml @@ -876,7 +855,7 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge -This parameter is available or functional only in 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. @@ -898,18 +877,14 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize -This parameter is available or functional only in 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are treated as bytes. The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. @@ -930,18 +905,14 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize -This parameter is available or functional only in 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are treated as bytes. The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the IRM log files. @@ -960,7 +931,7 @@ Accept wildcard characters: False ``` ### -IrmLogPath -This parameter is available or functional only in 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. @@ -1016,7 +987,7 @@ Accept wildcard characters: False ``` ### -JunkEmailOptionsCommitterWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1037,16 +1008,14 @@ Accept wildcard characters: False 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) - - de-AT (German - Austria) - - es-CL (Spanish - Chile) -For more information, see [CultureInfo Class](https://go.microsoft.com/fwlink/p/?linkId=68806). +For more information, see [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo). -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -1066,18 +1035,14 @@ This parameter is used for coexistence with Exchange 2010. Specifically, this pa 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. -Every mailbox database on the server uses a different log file name prefix (for example, Managed\_Folder\_Assistant[Mailbox database name]). Therefore, the maximum size of the managed folder log directory is the number of mailbox databases multiplied by the value of the LogDirectorySizeLimitForManagedFolders parameter. Other files aren't counted in the total size calculation. Renaming old log files or copying other files into the managed folder log directory could cause the directory to exceed its specified maximum size. +Every mailbox database on the server uses a different log file name prefix (for example, `Managed_Folder_Assistant`). Therefore, the maximum size of the managed folder log directory is the number of mailbox databases multiplied by the value of the LogDirectorySizeLimitForManagedFolders parameter. Other files aren't counted in the total size calculation. Renaming old log files or copying other files into the managed folder log directory could cause the directory to exceed its specified maximum size. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1127,13 +1092,9 @@ The LogFileSizeLimitForManagedFolders parameter specifies the maximum size for e When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1172,7 +1133,7 @@ Accept wildcard characters: False ``` ### -MailboxAssociationReplicationWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1190,7 +1151,7 @@ Accept wildcard characters: False ``` ### -MailboxAssociationReplicationWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1208,7 +1169,7 @@ Accept wildcard characters: False ``` ### -MailboxProcessorWorkCycle -This parameter is available or functional only in 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. @@ -1228,18 +1189,16 @@ Accept wildcard characters: False ``` ### -ManagedFolderAssistantSchedule -**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://docs.microsoft.com/Exchange/policy-and-compliance/mrm/configure-managed-folder-assistant). +**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. -The syntax for this parameter is: StartDay.Hour:Minute \[AM/PM\]-EndDay.Hour:Minute \[AM/PM\]. You can specify multiple schedules separated by commas: "\","\",..."\". +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"`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -1251,11 +1210,8 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" - - "Monday.4:30 AM-Monday.5:30 AM","Wednesday.4:30 AM-Wednesday.5:30 AM" (Run on Monday and Wednesday mornings from 4:30 until 5:30.) If the Managed Folder Assistant doesn't finish processing the mailboxes on the server during the time that you've scheduled, it automatically resumes processing where it left off the next time it runs. @@ -1274,7 +1230,7 @@ Accept wildcard characters: False ``` ### -ManagedFolderWorkCycle -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -1298,7 +1254,7 @@ Accept wildcard characters: False ``` ### -ManagedFolderWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -1376,7 +1332,7 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogEnabled -This parameter is available or functional only in 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. @@ -1394,7 +1350,7 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxAge -This parameter is available or functional only in 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. @@ -1416,7 +1372,7 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxDirectorySize -This parameter is available or functional only in 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. @@ -1427,13 +1383,9 @@ When the Hub Transport server role and the Mailbox server role are installed on The default value is 250 MB. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are treated as bytes. The value of the MessageTrackingLogMaxFileSize parameter must be less than or equal to the value of the MessageTrackingLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. @@ -1452,16 +1404,13 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxFileSize -This parameter is available or functional only in 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are treated as bytes. The value of the MessageTrackingLogMaxFileSize parameter must be less than or equal to the value of the MessageTrackingLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 4294967296 bytes (4 GB). @@ -1480,7 +1429,7 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogPath -This parameter is available or functional only in 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. @@ -1498,7 +1447,7 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogSubjectLoggingEnabled -This parameter is available or functional only in 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. @@ -1596,7 +1545,7 @@ Accept wildcard characters: False ``` ### -OABGeneratorWorkCycle -This parameter is available or functional only in 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. @@ -1618,7 +1567,7 @@ Accept wildcard characters: False ``` ### -OABGeneratorWorkCycleCheckpoint -This parameter is available or functional only in 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. @@ -1640,7 +1589,7 @@ Accept wildcard characters: False ``` ### -PeopleCentricTriageWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1658,7 +1607,7 @@ Accept wildcard characters: False ``` ### -PeopleCentricTriageWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1676,7 +1625,7 @@ Accept wildcard characters: False ``` ### -PeopleRelevanceWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1694,7 +1643,7 @@ Accept wildcard characters: False ``` ### -PeopleRelevanceWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1712,7 +1661,7 @@ Accept wildcard characters: False ``` ### -ProbeTimeBasedAssistantWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1730,7 +1679,7 @@ Accept wildcard characters: False ``` ### -ProbeTimeBasedAssistantWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1748,7 +1697,7 @@ Accept wildcard characters: False ``` ### -PublicFolderWorkCycle -This parameter is available or functional only in 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. @@ -1768,7 +1717,7 @@ Accept wildcard characters: False ``` ### -PublicFolderWorkCycleCheckpoint -This parameter is available or functional only in 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. @@ -1808,7 +1757,7 @@ Accept wildcard characters: False ``` ### -SearchIndexRepairTimeBasedAssistantWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1826,7 +1775,7 @@ Accept wildcard characters: False ``` ### -SearchIndexRepairTimeBasedAssistantWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1844,7 +1793,7 @@ Accept wildcard characters: False ``` ### -SharePointSignalStoreWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1862,7 +1811,7 @@ Accept wildcard characters: False ``` ### -SharePointSignalStoreWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1882,14 +1831,12 @@ Accept wildcard characters: False ### -SharingPolicySchedule 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: "\","\",..."\". +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"`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -1901,11 +1848,8 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" - - "Monday.4:30 AM-Monday.5:30 AM","Wednesday.4:30 AM-Wednesday.5:30 AM" (Run on Monday and Wednesday mornings from 4:30 until 5:30.) ```yaml @@ -1922,11 +1866,11 @@ Accept wildcard characters: False ``` ### -SharingPolicyWorkCycle -This parameter is available or functional only in Exchange Server 2010 or 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. -The Sharing Policy Assistant scans all mailboxes and enables or disables sharing polices according to the interval specified by the SharingPolicyWorkCycle. +The Sharing Policy Assistant scans all mailboxes and enables or disables sharing policies according to the interval specified by the SharingPolicyWorkCycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. @@ -1946,7 +1890,7 @@ Accept wildcard characters: False ``` ### -SharingPolicyWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -1970,7 +1914,7 @@ Accept wildcard characters: False ``` ### -SharingSyncWorkCycle -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -1994,7 +1938,7 @@ Accept wildcard characters: False ``` ### -SharingSyncWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -2018,7 +1962,7 @@ Accept wildcard characters: False ``` ### -SiteMailboxWorkCycle -This parameter is available or functional only in 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. @@ -2040,7 +1984,7 @@ Accept wildcard characters: False ``` ### -SiteMailboxWorkCycleCheckpoint -This parameter is available or functional only in 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. @@ -2062,7 +2006,7 @@ Accept wildcard characters: False ``` ### -StoreDsMaintenanceWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2080,7 +2024,7 @@ Accept wildcard characters: False ``` ### -StoreDsMaintenanceWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2098,7 +2042,7 @@ Accept wildcard characters: False ``` ### -StoreIntegrityCheckWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2116,7 +2060,7 @@ Accept wildcard characters: False ``` ### -StoreIntegrityCheckWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2134,7 +2078,7 @@ Accept wildcard characters: False ``` ### -StoreMaintenanceWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2152,7 +2096,7 @@ Accept wildcard characters: False ``` ### -StoreMaintenanceWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2170,7 +2114,7 @@ Accept wildcard characters: False ``` ### -StoreScheduledIntegrityCheckWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2188,7 +2132,7 @@ Accept wildcard characters: False ``` ### -StoreScheduledIntegrityCheckWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2206,7 +2150,7 @@ Accept wildcard characters: False ``` ### -StoreUrgentMaintenanceWorkCycle -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2224,7 +2168,7 @@ Accept wildcard characters: False ``` ### -StoreUrgentMaintenanceWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2278,7 +2222,7 @@ Accept wildcard characters: False ``` ### -TopNWorkCycle -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -2302,7 +2246,7 @@ Accept wildcard characters: False ``` ### -TopNWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -2326,7 +2270,7 @@ Accept wildcard characters: False ``` ### -UMReportingWorkCycle -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -2352,7 +2296,7 @@ Accept wildcard characters: False ``` ### -UMReportingWorkCycleCheckpoint -This parameter is available or functional only in Exchange Server 2010 or 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. @@ -2374,7 +2318,7 @@ Accept wildcard characters: False ``` ### -WacDiscoveryEndpoint -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. +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). @@ -2412,12 +2356,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Set-MailboxSpellingConfiguration.md b/exchange/exchange-ps/exchange/Set-MailboxSpellingConfiguration.md similarity index 89% rename from exchange/exchange-ps/exchange/client-access/Set-MailboxSpellingConfiguration.md rename to exchange/exchange-ps/exchange/Set-MailboxSpellingConfiguration.md index 6e63df2231..975a5bcb45 100644 --- a/exchange/exchange-ps/exchange/client-access/Set-MailboxSpellingConfiguration.md +++ b/exchange/exchange-ps/exchange/Set-MailboxSpellingConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-mailboxspellingconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MailboxSpellingConfiguration @@ -17,20 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MailboxSpellingConfiguration cmdlet to modify Outlook on the web spelling checker options for a specified user. For example, you can set the dictionary language and configure the spelling checker to ignore mixed digits or words in all uppercase. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-MailboxSpellingConfiguration [-Identity] [-CheckBeforeSend ] +Set-MailboxSpellingConfiguration [-Identity] + [-CheckBeforeSend ] [-Confirm] [-DictionaryLanguage ] - [-DomainController ] [-IgnoreMixedDigits ] [-IgnoreUppercase ] [-WhatIf] + [-DomainController ] + [-IgnoreMixedDigits ] + [-IgnoreUppercase ] + [-WhatIf] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,30 +57,21 @@ This example sets the spelling checker to ignore words containing numbers for me The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -105,15 +99,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -126,45 +119,25 @@ Accept wildcard characters: False The DictionaryLanguage parameter specifies the dictionary language to use when the spelling checker checks the spelling in messages. Valid values are: - Arabic - - Catalan - - Danish - - Dutch - - EnglishAustralia - - EnglishCanada - - EnglishUnitedKingdom - - EnglishUnitedStates - - Finnish - - French - - GermanPreReform - - GermanPostReform - - Hebrew - - Italian - - Korean - - NorwegianBokMal - - NorwegianNyorsk - - PortuguesePortugal - - PortugueseBrasil - - Spanish - - Swedish ```yaml @@ -239,7 +212,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -253,12 +226,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-MailboxTransportService.md b/exchange/exchange-ps/exchange/Set-MailboxTransportService.md similarity index 97% rename from exchange/exchange-ps/exchange/mail-flow/Set-MailboxTransportService.md rename to exchange/exchange-ps/exchange/Set-MailboxTransportService.md index cec774b28a..ae787b004f 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-MailboxTransportService.md +++ b/exchange/exchange-ps/exchange/Set-MailboxTransportService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-mailboxtransportservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-MailboxTransportService @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-MailboxTransportService cmdlet to modify the configuration of the Mailbox Transport service on Exchange 2013 or later Mailbox servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -65,13 +64,14 @@ Set-MailboxTransportService [-Identity] [-SendProtocolLogMaxDirectorySize ] [-SendProtocolLogMaxFileSize ] [-SendProtocolLogPath ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Mailbox Transport service runs on all Mailbox servers and is responsible for delivering messages to and accepting messages from local mailbox databases using a remote procedure call (RPC). The Mailbox Transport service also uses SMTP to send messages to and from the Transport service that runs on all Mailbox servers for routing messages to their ultimate destinations. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -103,8 +103,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -162,13 +161,9 @@ The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -194,13 +189,9 @@ The ConnectivityLogMaxFileSize parameter specifies the maximum size of each conn When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -240,9 +231,7 @@ Accept wildcard characters: False 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 - - Network Service: Full Control - - System: Full Control ```yaml @@ -316,13 +305,9 @@ The MailboxDeliveryAgentLogMaxDirectorySize parameter specifies the maximum size When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -348,13 +333,9 @@ The MailboxDeliveryAgentLogMaxFileSize parameter specifies the maximum size of e When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -410,7 +391,6 @@ Accept wildcard characters: False 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. - - Verbose: Protocol logging is enabled for the mailbox delivery Receive connector. The location of the log files is controlled by the ReceiveProtocolLogPath parameter. ```yaml @@ -430,7 +410,6 @@ Accept wildcard characters: False 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 - - $false: Mail can't be delivered to local mailboxes that have international characters in email addresses. ```yaml @@ -488,13 +467,9 @@ The MailboxDeliveryThrottlingLogMaxDirectorySize parameter specifies the maximum When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -520,13 +495,9 @@ The MailboxDeliveryThrottlingLogMaxFileSize parameter specifies the maximum size When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -604,13 +575,9 @@ The MailboxSubmissionAgentLogMaxDirectorySize parameter specifies the maximum si When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -636,13 +603,9 @@ The MailboxSubmissionAgentLogMaxFileSize parameter specifies the maximum size of When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -727,12 +690,14 @@ Accept wildcard characters: False ``` ### -PipelineTracingPath -The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location is %ExchangeInstallPath%TransportRoles\\Mailbox\\Hub\\PipelineTracing. The path must be local to the Exchange computer. 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. Pipeline 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: +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. -- Administrators: Full Control +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. -- Network Service: Full Control +Pipeline 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 +- Network Service: Full Control - System: Full Control ```yaml @@ -796,13 +761,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -832,13 +793,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -904,13 +861,9 @@ The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -976,13 +929,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1012,13 +961,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1044,7 +989,6 @@ Accept wildcard characters: False 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. - - Delivery: Protocol log files for side effect messages that are submitted after messages are delivered to mailboxes. For example, a message delivered to a mailbox triggers an Inbox rule that redirects the message to another recipient. Don't use the value $null for this parameter, because event log errors are generated if protocol logging is enabled for the intra-organization Send connector in the Mailbox Transport Submission service. To disable protocol logging for this connector, use the value None for the IntraOrgConnectorProtocolLoggingLevel parameter on the Set-TransportService cmdlet. @@ -1083,12 +1027,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md new file mode 100644 index 0000000000..97910b18d9 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md @@ -0,0 +1,727 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MalwareFilterPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-MalwareFilterPolicy cmdlet to modify malware filter policies in your organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MalwareFilterPolicy [-Identity] + [-Action ] + [-AdminDisplayName ] + [-BypassInboundMessages ] + [-BypassOutboundMessages ] + [-Confirm] + [-CustomAlertText ] + [-CustomExternalBody ] + [-CustomExternalSubject ] + [-CustomFromAddress ] + [-CustomFromName ] + [-CustomInternalBody ] + [-CustomInternalSubject ] + [-CustomNotifications ] + [-DomainController ] + [-EnableExternalSenderAdminNotifications ] + [-EnableExternalSenderNotifications ] + [-EnableFileFilter ] + [-EnableInternalSenderAdminNotifications ] + [-EnableInternalSenderNotifications ] + [-ExternalSenderAdminAddress ] + [-FileTypeAction ] + [-FileTypes ] + [-InternalSenderAdminAddress ] + [-IsPolicyOverrideApplied ] + [-MakeDefault] + [-QuarantineTag ] + [-WhatIf] + [-ZapEnabled ] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MalwareFilterPolicy -Identity "Contoso Malware Filter Policy" -Action DeleteMessage -EnableInternalSenderAdminNotifications $true -InternalSenderAdminAddress admin@contoso.com +``` + +In on-premises Exchange, this example modifies the malware filter policy named Contoso Malware Filter Policy with the following settings: + +- Delete messages that contain malware. +- Don't notify the message sender when malware is detected in the message. +- Notify the administrator admin@contoso.com when malware is detected in a message from an internal sender. + +### Example 2 +```powershell +$FileTypesAdd = Get-MalwareFilterPolicy -Identity Default | select -Expand FileTypes + +$FileTypesAdd += "dgz","mde" + +Set-MalwareFilterPolicy -Identity Default -EnableFileFilter $true -FileTypes $FileTypesAdd +``` + +This example enables the common attachments filter in the malware filter policy named Default and adds the file types "dgz" and "mde" without affecting the other file type entries. + +### Example 3 +```powershell +$ft = Get-MalwareFilterPolicy -Identity Default + +$a = [System.Collections.ArrayList]($ft.FileTypes) + +$a + +$a.RemoveAt(6) + +Set-MalwareFilterPolicy -Identity Default -FileTypes $a +``` + +This example modifies the malware filter policy named Default by removing an existing file type from the common attachments filter without affecting other file types that are already specified. + +The first three commands return the existing list of file types. The first file type in the list has the index number 0, the second has the index number 1, and so on. Use the index number to specify the file type that you want to remove. + +The last two commands remove the seventh file type that's displayed in the list. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Action +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: + +- DeleteMessage: Handles the message without notifying the recipients. This is the default value. +- DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. +- DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. + +```yaml +Type: MalwareFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassInboundMessages +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: + +- $true: Malware filtering is disabled on inbound messages. +- $false: Malware filtering is enabled on inbound messages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassOutboundMessages +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: + +- $true: Malware filtering is disabled on outbound messages. +- $false: Malware filtering is enabled on outbound messages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAlertText +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 ("). + +This parameter is meaningful only when the value of the Action parameter is DeleteAttachmentAndUseCustomAlert. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomExternalBody +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomExternalSubject +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomFromAddress +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomFromName +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: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomInternalBody +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: + +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomInternalSubject +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: + +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomNotifications +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. +- $false: No customization is done to notification messages. The default values are used. + +This parameter is meaningful only when the value of at least one of the following parameters is also $true: + +- EnableExternalSenderAdminNotifications +- EnableExternalSenderNotifications +- EnableInternalSenderAdminNotifications +- EnableInternalSenderNotifications + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableExternalSenderAdminNotifications +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. +- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value. + +**Note**: Admin notifications are sent only for _attachments_ that are classified as malware. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableExternalSenderNotifications +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: + +- $true: When malware is detected in a message from an external sender, send them a notification message. +- $false: Don't send malware detection notification messages to external message senders. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableFileFilter +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: + +- $true: The common attachments filter is enabled. This is the default value. +- $false: The common attachments filter is disabled. + +You specify the file types using the FileTypes parameter. + +You specify the action for detected files using the FileTypeAction parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableInternalSenderAdminNotifications +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. +- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value. + +**Note**: Admin notifications are sent only for _attachments_ that are classified as malware. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableInternalSenderNotifications +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: + +- $true: When malware is detected in a message from an internal sender, send them a notification message. +- $false: Don't send malware detection notification messages to internal message senders. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalSenderAdminAddress +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileTypeAction +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: + +- Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter. +- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value. + +This parameter is meaningful only when the value of the EnableFileFilter parameter is $true. + +```yaml +Type: FileTypeFilteringAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileTypes +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: + +`ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z` + +This parameter is meaningful only if the value of the EnableFileFilter parameter is $true. + +The common attachments filter uses best effort true-typing to detect the file type regardless of the file name extension. For example, an exe file renamed to txt is detected as an exe file. If true-typing fails or isn't supported for the specified file type, then extension matching is used. + +To replace the existing list of file types with the values you specify, use the syntax `FileType1,FileType2,...FileTypeN`. To preserve existing values, be sure to include the file types that you want to keep along with the new values that you want to add. + +To add or remove file types without affecting the other file type entries, see the Examples section in this topic. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalSenderAdminAddress +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsPolicyOverrideApplied +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeDefault +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineTag +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: + +- Name +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages, and whether users receive quarantine notifications. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default quarantine policy that's used is named AdminOnlyAccessPolicy. For more information about this quarantine policy, see [Anatomy of a quarantine policy](https://learn.microsoft.com/defender-office-365/quarantine-policies#anatomy-of-a-quarantine-policy). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ZapEnabled +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: + +- $true: ZAP for malware is enabled. This is the default value. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined. +- $false: ZAP for malware is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/antispam-antimalware/Set-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Set-MalwareFilterRule.md similarity index 83% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilterRule.md rename to exchange/exchange-ps/exchange/Set-MalwareFilterRule.md index 5c6822531d..9589a6fc72 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilterRule.md +++ b/exchange/exchange-ps/exchange/Set-MalwareFilterRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-malwarefilterrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-MalwareFilterRule @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MalwareFilterRule cmdlet to modify malware filter rules in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -35,11 +34,15 @@ Set-MalwareFilterRule [-Identity] [-RecipientDomainIs ] [-SentTo ] [-SentToMemberOf ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,8 +90,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,7 +125,7 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -142,18 +144,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -169,21 +166,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf -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: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. @@ -201,14 +193,12 @@ Accept wildcard characters: False ``` ### -MalwareFilterPolicy -The MalwareFilterPolicy parameter specifies the malware filter policy that's associated with the malware filter rule rule. +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: - Name - - Distinguished name (DN) - - GUID. You can't specify the default malware filter policy, and you can't specify a policy that's already associated with another malware filter rule. @@ -248,9 +238,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a new rule (the 9th rule) are from 0 through 8. - - The default value for a new rule (the 9th rule) is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -269,7 +257,7 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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[] @@ -288,18 +276,13 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. ```yaml Type: RecipientIdParameter[] @@ -315,21 +298,16 @@ Accept wildcard characters: False ``` ### -SentToMemberOf -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: +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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. @@ -367,12 +345,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilteringServer.md b/exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md similarity index 92% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilteringServer.md rename to exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md index 1d676a83e7..5766c7970f 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilteringServer.md +++ b/exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-malwarefilteringserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-MalwareFilteringServer @@ -17,20 +16,31 @@ This cmdlet is available only in on-premises Exchange. Use the Set-MalwareFilteringServer cmdlet to configure the Malware agent settings in the Transport service on a Mailbox server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-MalwareFilteringServer [-Identity] [-BypassFiltering ] - [-Confirm] [-DeferAttempts ] [-DeferWaitTime ] [-DomainController ] - [-ForceRescan ] [-MinimumSuccessfulEngineScans ] [-PrimaryUpdatePath ] - [-ScanErrorAction ] [-ScanTimeout ] [-SecondaryUpdatePath ] - [-UpdateFrequency ] [-UpdateTimeout ] [-WhatIf] [] +Set-MalwareFilteringServer [-Identity] + [-BypassFiltering ] + [-Confirm] + [-DeferAttempts ] + [-DeferWaitTime ] + [-DomainController ] + [-ForceRescan ] + [-MinimumSuccessfulEngineScans ] + [-PrimaryUpdatePath ] + [-ScanErrorAction ] + [-ScanTimeout ] + [-SecondaryUpdatePath ] + [-UpdateFrequency ] + [-UpdateTimeout ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,7 +52,6 @@ Set-MalwareFilteringServer Mailbox01 -UpdateFrequency 120 -DeferWaitTime 10 This example sets the following Malware agent settings on the Mailbox server named Mailbox01: - Sets the update frequency interval to 2 hours - - Sets the time to wait between resubmit attempts to 10 minutes ## PARAMETERS @@ -51,11 +60,8 @@ This example sets the following Malware agent settings on the Mailbox server nam 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -90,8 +96,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -196,7 +201,7 @@ Accept wildcard characters: False ``` ### -PrimaryUpdatePath -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. +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 @@ -316,12 +321,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedContentSettings.md b/exchange/exchange-ps/exchange/Set-ManagedContentSettings.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedContentSettings.md rename to exchange/exchange-ps/exchange/Set-ManagedContentSettings.md index 42ad6fdc53..9606389193 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedContentSettings.md +++ b/exchange/exchange-ps/exchange/Set-ManagedContentSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-managedcontentsettings +online version: https://learn.microsoft.com/powershell/module/exchange/set-managedcontentsettings applicable: Exchange Server 2010 title: Set-ManagedContentSettings schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-ManagedContentSettings @@ -17,27 +16,34 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-ManagedContentSettings cmdlet to modify existing managed content settings for a managed folder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-ManagedContentSettings [-Identity] - [-AddressForJournaling ] [-AgeLimitForRetention ] [-Confirm] - [-DomainController ] [-JournalingEnabled ] [-LabelForJournaling ] - [-MessageFormatForJournaling ] [-MoveToDestinationFolder ] + [-AddressForJournaling ] + [-AgeLimitForRetention ] + [-Confirm] + [-DomainController ] + [-JournalingEnabled ] + [-LabelForJournaling ] + [-MessageFormatForJournaling ] + [-MoveToDestinationFolder ] [-Name ] [-RetentionAction ] - [-RetentionEnabled ] [-TriggerForRetention ] [-WhatIf] + [-RetentionEnabled ] + [-TriggerForRetention ] + [-WhatIf] [] ``` ## DESCRIPTION -Managed content settings are settings that you apply to managed folders to control the lifespan of items in users' mailboxes. For more information about managed content settings, see [Messaging Records Management](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb123507(v=exchg.141)). +Managed content settings are settings that you apply to managed folders to control the lifespan of items in users' mailboxes. For more information about managed content settings, see [Messaging Records Management](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123507(v=exchg.141)). -Although the New-ManagedContentSettings cmdlet has the MessageClass parameter, the Set-ManagedContentSettings cmdlet doesn't. If you want to change the message type to which content settings apply, you must delete and then re-create the content settings. For more information about the MessageClass parameter, see [New-ManagedContentSettings](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-managedcontentsettings). +Although the New-ManagedContentSettings cmdlet has the MessageClass parameter, the Set-ManagedContentSettings cmdlet doesn't. If you want to change the message type to which content settings apply, you must delete and then re-create the content settings. For more information about the MessageClass parameter, see [New-ManagedContentSettings](https://learn.microsoft.com/powershell/module/exchange/new-managedcontentsettings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,15 +76,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -115,8 +116,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -184,7 +184,6 @@ Accept wildcard characters: False 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 - - UseTnef Outlook MAPI format ```yaml @@ -236,13 +235,9 @@ Accept wildcard characters: False 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 - - Move to a managed custom folder - - Move to the Deleted Items folder - - Delete and allow recovery - - Permanently delete If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. @@ -282,7 +277,6 @@ The TriggerForRetention parameter specifies the date that's considered as the st Valid values include: - WhenDelivered The item expires based on when it was delivered. - - WhenMoved The item expires based on the date it was moved. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. @@ -321,12 +315,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedFolder.md b/exchange/exchange-ps/exchange/Set-ManagedFolder.md similarity index 91% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedFolder.md rename to exchange/exchange-ps/exchange/Set-ManagedFolder.md index 2b2539652f..aef4960fcd 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedFolder.md +++ b/exchange/exchange-ps/exchange/Set-ManagedFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-managedfolder +online version: https://learn.microsoft.com/powershell/module/exchange/set-managedfolder applicable: Exchange Server 2010 title: Set-ManagedFolder schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-ManagedFolder @@ -17,15 +16,24 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-ManagedFolder cmdlet to modify the settings of managed folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ManagedFolder [-Identity] [-BaseFolderOnly ] [-Comment ] - [-Confirm] [-DomainController ] [-FolderName ] [-LocalizedComment ] - [-LocalizedFolderName ] [-MustDisplayCommentEnabled ] [-Name ] - [-StorageQuota ] [-WhatIf] [] +Set-ManagedFolder [-Identity] + [-BaseFolderOnly ] + [-Comment ] + [-Confirm] + [-DomainController ] + [-FolderName ] + [-LocalizedComment ] + [-LocalizedFolderName ] + [-MustDisplayCommentEnabled ] + [-Name ] + [-StorageQuota ] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -33,7 +41,7 @@ The Set-ManagedFolder cmdlet modifies the specified parameters of a managed fold The Set-ManagedFolder cmdlet accepts a managed custom folder or an identity string as pipelined input. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -97,8 +105,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -247,12 +254,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/exchange/Set-ManagedFolderMailboxPolicy.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedFolderMailboxPolicy.md rename to exchange/exchange-ps/exchange/Set-ManagedFolderMailboxPolicy.md index e54023dccf..4e82b118b4 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Set-ManagedFolderMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-managedfoldermailboxpolicy +online version: https://learn.microsoft.com/powershell/module/exchange/set-managedfoldermailboxpolicy applicable: Exchange Server 2010 title: Set-ManagedFolderMailboxPolicy schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-ManagedFolderMailboxPolicy @@ -17,17 +16,22 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-ManagedFolderMailboxPolicy cmdlet to change the settings of a managed folder mailbox policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ManagedFolderMailboxPolicy [-Identity] [-Confirm] [-DomainController ] - [-ManagedFolderLinks ] [-Name ] [-WhatIf] [] +Set-ManagedFolderMailboxPolicy [-Identity] + [-Confirm] + [-DomainController ] + [-ManagedFolderLinks ] + [-Name ] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -38,7 +42,7 @@ Set-ManagedFolderMailboxPolicy "PM Storage Template1" -Name "PM Storage Template This example changes the name of the managed folder mailbox policy PM Storage Template1 to PM Storage Template2. -The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). +The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). ### Example 2 ```powershell @@ -68,8 +72,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -154,13 +157,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### -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. +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementRoleAssignment.md b/exchange/exchange-ps/exchange/Set-ManagementRoleAssignment.md similarity index 81% rename from exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementRoleAssignment.md rename to exchange/exchange-ps/exchange/Set-ManagementRoleAssignment.md index 1923ca6b2d..44d3d2ad77 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/exchange/Set-ManagementRoleAssignment.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/set-managementroleassignment +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-ManagementRoleAssignment @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ManagementRoleAssignment cmdlet to modify existing management role assignments. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ Set-ManagementRoleAssignment [-Identity] [-Recipient [-DomainController ] [-Enabled ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### CustomRecipientWriteScope @@ -40,7 +40,8 @@ Set-ManagementRoleAssignment [-Identity] [-CustomCon [-DomainController ] [-Enabled ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RecipientOrganizationalUnitScope @@ -51,7 +52,8 @@ Set-ManagementRoleAssignment [-Identity] [-Recipient [-DomainController ] [-Enabled ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ExclusiveScope @@ -61,7 +63,8 @@ Set-ManagementRoleAssignment [-Identity] [-Exclusive [-DomainController ] [-Enabled ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RecipientAdministrativeUnitScope @@ -71,7 +74,28 @@ Set-ManagementRoleAssignment [-Identity] -RecipientA [-DomainController ] [-Enabled ] [-Force] - [-WhatIf] [] + [-WhatIf] + [] +``` + +### App +``` +Set-ManagementRoleAssignment [-Identity] [-CustomResourceScope ] + [-Confirm] + [-Enabled ] + [-Force] + [-WhatIf] + [] +``` + +### RecipientGroupScope +``` +Set-ManagementRoleAssignment [-Identity] -RecipientGroupScope + [-Confirm] + [-Enabled ] + [-Force] + [-WhatIf] + [] ``` ## DESCRIPTION @@ -79,9 +103,9 @@ When you modify a role assignment, you can specify a new predefined or custom ma You can create custom management scopes using the New-ManagementScope cmdlet and can view a list of existing scopes using the Get-ManagementScope cmdlet. If you choose not to specify an OU, predefined scope, or custom scope, the implicit write scope of the role applies to the role assignment. -For more information about management role assignments, see [Understanding management role assignments](https://docs.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). +For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -131,11 +155,50 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -RecipientAdministrativeUnitScope +This parameter is functional only in the cloud-based service. + +The RecipientAdministrativeUnitScope parameter specifies the administrative unit to scope the role assignment to. + +Administrative units are Microsoft Entra containers of resources. You can view the available administrative units by using the Get-AdministrativeUnit cmdlet. + +You can't use this parameter with any of the other scope parameters. + +```yaml +Type: AdministrativeUnitIdParameter +Parameter Sets: RecipientAdministrativeUnitScope +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientGroupScope +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. + +```yaml +Type: GroupIdParameter +Parameter Sets: RecipientGroupScope +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -193,6 +256,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -CustomResourceScope +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: + +- Name +- Distinguished name (DN) +- GUID + +If the value contains spaces, enclose the value in quotation marks ("). + +You use this parameter with the App parameter to assign permissions to service principals. For more information, see For more information about service principals, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). + +```yaml +Type: ManagementScopeIdParameter +Parameter Sets: App +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DomainController This parameter is available only in on-premises Exchange. @@ -200,7 +289,7 @@ The DomainController parameter specifies the domain controller that's used by th ```yaml Type: Fqdn -Parameter Sets: (All) +Parameter Sets: RelativeRecipientWriteScope, CustomRecipientWriteScope, RecipientOrganizationalUnitScope, ExclusiveScope, RecipientAdministrativeUnitScope Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -270,37 +359,19 @@ Accept wildcard characters: False ``` ### -Force -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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAdministrativeUnitScope This parameter is available only in the cloud-based service. -The RecipientAdministrativeUnitScope parameter specifies the administrative unit to scope the role assignment to. - -Administrative units are Azure Active Directory containers of resources. You can view the available administrative units by using the Get-AdministrativeUnit cmdlet. +The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -You can't use this parameter with any of the other scope parameters. +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. ```yaml -Type: AdministrativeUnitIdParameter -Parameter Sets: RecipientAdministrativeUnitScope +Type: SwitchParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Online, Exchange Online Protection -Required: True +Required: False Position: Named Default value: None Accept pipeline input: False @@ -370,12 +441,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementRoleEntry.md b/exchange/exchange-ps/exchange/Set-ManagementRoleEntry.md similarity index 80% rename from exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementRoleEntry.md rename to exchange/exchange-ps/exchange/Set-ManagementRoleEntry.md index 850d599152..ee811f9b5f 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementRoleEntry.md +++ b/exchange/exchange-ps/exchange/Set-ManagementRoleEntry.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/set-managementroleentry +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-ManagementRoleEntry @@ -17,22 +16,29 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ManagementRoleEntry cmdlet to change the available parameters on an existing management role entry. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ManagementRoleEntry [-Identity] [-AddParameter] [-Confirm] - [-DomainController ] [-Parameters ] [-RemoveParameter] [-UnScopedTopLevel] [-WhatIf] [-Force] +Set-ManagementRoleEntry [-Identity] + [-AddParameter] + [-Confirm] + [-DomainController ] + [-Force] + [-Parameters ] + [-RemoveParameter] + [-UnScopedTopLevel] + [-WhatIf] [] ``` ## DESCRIPTION The Set-ManagementRoleEntry cmdlet changes the available parameters on an existing role entry. If you want to add parameters to a role entry, the parameters must exist in the role entry in the parent management role. If you want to remove parameters from a role entry, there can be no role entries in child roles that inherit those parameters from the role entry you want to change. You can't change role entries associated with built-in roles. -For more information about management role entries, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,9 +73,9 @@ In on-premises Exchange, this example adds the Location parameter to the Mailbox ## PARAMETERS ### -Identity -The Identity parameter specifies the role entry to change. You must specify the value of the Identity parameter in the format, \\\\, for example, ExampleRole\\Set-Mailbox. +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://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). +For more information about how management role entries work, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). If the role entry name contains spaces, enclose it in quotation marks ("). @@ -87,7 +93,11 @@ Accept wildcard characters: False ``` ### -AddParameter -The AddParameter parameter adds the specified parameters to the specified role entry. Use the Parameters parameter to specify the parameters to add. You can't use the AddParameter parameter in the same command as the RemoveParameter parameter. +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. + +You can't use the AddParameter switch and the RemoveParameter switch together in the same command. ```yaml Type: SwitchParameter @@ -105,8 +115,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -140,15 +149,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Force +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Parameters The Parameters parameter specifies the parameters to be added to or removed from the role entry. The Parameters parameter has the following modes: - When used with the AddParameter parameter, the parameters you specify are added to the role entry. - - When used with the RemoveParameter parameter, the parameters you specify are removed from the role entry. - - When neither the AddParameter nor RemoveParameter parameters are used, only the parameters you specify are included in the role entry. If you specify a value of $Null and neither the AddParameter nor RemoveParameter parameters are used, all of the parameters on the role entry are removed. You can specify multiple parameters, separated with commas. @@ -167,7 +194,11 @@ Accept wildcard characters: False ``` ### -RemoveParameter -The RemoveParameter parameter removes the specified parameters from the specified role entry. Use the Parameters parameter to specify the parameters to remove. You can't use the RemoveParameter parameter in the same command as the AddParameter parameter. +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. + +You can't use the AddParameter switch and the RemoveParameter switch together in the same command. ```yaml Type: SwitchParameter @@ -183,15 +214,13 @@ Accept wildcard characters: False ``` ### -UnScopedTopLevel -This parameter is available on in on-premises Exchange. +This parameter is available only in on-premises Exchange. -By default, this parameter is only available 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +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). The UnScopedTopLevel switch specifies the role entry that you want to modify is on an unscoped top-level role. You don't need to specify a value with this switch. -Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. For more information, see [Create an unscoped role](https://docs.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). - -You must use this switch to modify role entries on unscoped top level roles. +Unscoped top-level management roles can only contain custom scripts or non-Exchange cmdlets. For more information, see [Create an unscoped role](https://learn.microsoft.com/exchange/create-an-unscoped-role-exchange-2013-help). ```yaml Type: SwitchParameter @@ -222,35 +251,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Force -This parameter is available only in the cloud-based service. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementScope.md b/exchange/exchange-ps/exchange/Set-ManagementScope.md similarity index 78% rename from exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementScope.md rename to exchange/exchange-ps/exchange/Set-ManagementScope.md index 834a26d19c..7d84c230ae 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Set-ManagementScope.md +++ b/exchange/exchange-ps/exchange/Set-ManagementScope.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/set-managementscope +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-ManagementScope @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ManagementScope cmdlet to change an existing management scope. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,7 +27,8 @@ Set-ManagementScope [-Identity] -DatabaseRestrictio [-DomainController ] [-Force] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### ServerFilter @@ -38,25 +38,29 @@ Set-ManagementScope [-Identity] -ServerRestrictionF [-DomainController ] [-Force] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### RecipientFilter ``` -Set-ManagementScope [-Identity] [-RecipientRestrictionFilter ] [-RecipientRoot ] +Set-ManagementScope [-Identity] + [-RecipientRestrictionFilter ] + [-RecipientRoot ] [-Confirm] [-DomainController ] [-Force] [-Name ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -If you change a scope that has been associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://docs.microsoft.com/exchange/change-a-role-scope-exchange-2013-help). +If you change a scope that has been associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://learn.microsoft.com/exchange/change-a-role-scope-exchange-2013-help). -For more information about regular and exclusive scopes, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -83,22 +87,35 @@ This example changes the Active Directory site used in the server restriction fi ## PARAMETERS -### -DatabaseRestrictionFilter -This parameter is available only in on-premises Exchange. +### -Identity +The Identity parameter specifies the name of the management scope to modify. If the name contains spaces, enclose it in quotation marks ("). -The DatabaseRestrictionFilter parameter uses OPath filter syntax to specify the databases that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. +```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 -- 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. +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` -- Property is a filterable property. For a list of filterable database properties, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +### -DatabaseRestrictionFilter +This parameter is available only in on-premises Exchange. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). +The DatabaseRestrictionFilter parameter uses OPATH filter syntax to specify the databases that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For a list of filterable database properties, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter with the RecipientRestrictionFilter, ServerRestrictionFilter, RecipientRoot, DatabaseList, or ServerList parameters. @@ -115,38 +132,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -ServerRestrictionFilter 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'"`. - -- 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. - -- Property is a filterable property. For a list of filterable server properties, see [Understanding management role scopes](https://docs.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +The ServerRestrictionFilter parameter uses OPATH filter syntax to specify the servers that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable property. For a list of filterable server properties, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter wit the RecipientRestrictionFilter, RecipientRoot, DatabaseRestrictionFilter, DatabaseList, or ServerList parameters. @@ -166,8 +164,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -202,13 +199,17 @@ Accept wildcard characters: False ``` ### -Force -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. +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. ```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 +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -234,19 +235,16 @@ Accept wildcard characters: False ``` ### -RecipientRestrictionFilter -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. +The RecipientRestrictionFilter parameter uses OPATH filter syntax to specify the recipients that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. -- Property is a filterable recipient property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). +- 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. +- Property is a filterable recipient property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). You can't use this parameter with the DatabaseRestrictionFilter, DatabaseList, ServerList, or ServerRestrictionFilter parameters. @@ -264,14 +262,11 @@ Accept wildcard characters: False ``` ### -RecipientRoot -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 visibor domain that's returned bylUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example: +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 - - Canonical name - - Distinguished name (DN) - - GUID You can't use this parameter with the ServerRestrictionFilter or DatabaseRestrictionFilter parameters. @@ -310,14 +305,15 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 +Use two-letter country codes (ISO 3166-1 alpha-2) instead of the full country name in filters. For example, use `-RecipientRestrictionFilter "UsageLocation -eq 'FR'"` for France. ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-MapiVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-MapiVirtualDirectory.md similarity index 83% rename from exchange/exchange-ps/exchange/client-access-servers/Set-MapiVirtualDirectory.md rename to exchange/exchange-ps/exchange/Set-MapiVirtualDirectory.md index c05f16b94b..ec322afd70 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Set-MapiVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-mapivirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-MapiVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-MapiVirtualDirectory cmdlet to modify Messaging Application Programming Interface (MAPI) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,11 +31,12 @@ Set-MapiVirtualDirectory [-Identity] [-ExternalUrl ] [-IISAuthenticationMethods ] [-InternalUrl ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,8 +47,7 @@ Set-MapiVirtualDirectory -Identity "ContosoMail\mapi (Default Web Site)" -Intern This example makes the following configuration changes to the MAPI virtual directory on the default web site of the server named ContosoMail: -- Internal URL: https://contoso/mapi. - +- Internal URL: `https://contoso/mapi`. - IIS authentication methods: NTLM, Negotiate, and OAuth. ## PARAMETERS @@ -56,13 +55,11 @@ This example makes the following configuration changes to the MAPI virtual direc ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -78,7 +75,7 @@ Accept wildcard characters: False ``` ### -ApplyDefaults -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. +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. @@ -98,8 +95,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -132,25 +128,19 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionFlags -This parameter is available only in Exchange 2013. - The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -160,19 +150,16 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionSPNList -This parameter is available only in Exchange 2013. - 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -182,25 +169,19 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionTokenChecking -This parameter is available only in Exchange 2013. - 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -212,7 +193,7 @@ Accept wildcard characters: False ### -ExternalUrl 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. +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`). When you use the InternalUrl or ExternalUrl parameters, you need to specify one or more authentication values by using the IISAuthenticationMethods parameter. @@ -233,17 +214,16 @@ Accept wildcard characters: False The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values are: - Basic - - Negotiate - - NTLM - - OAuth You can specify multiple values separated by commas. The default values are NTLM, OAuth, and Negotiate. We recommend that you always have the virtual directory configured for OAuth. +For more information about the different authentication methods, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication) and [What is OAuth authentication?](https://learn.microsoft.com/exchange/using-oauth-authentication-to-support-ediscovery-in-an-exchange-hybrid-deployment-exchange-2013-help#what-is-oauth-authentication). + ```yaml Type: MultiValuedProperty Parameter Sets: (All) @@ -260,7 +240,7 @@ Accept wildcard characters: False ### -InternalUrl 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. +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`). When you use the InternalUrl or ExternalUrl parameters, you need to specify one or more authentication values by using the IISAuthenticationMethods parameter. @@ -298,12 +278,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-MessageClassification.md b/exchange/exchange-ps/exchange/Set-MessageClassification.md similarity index 85% rename from exchange/exchange-ps/exchange/policy-and-compliance/Set-MessageClassification.md rename to exchange/exchange-ps/exchange/Set-MessageClassification.md index fd4233cb87..4c48abce78 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-MessageClassification.md +++ b/exchange/exchange-ps/exchange/Set-MessageClassification.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-messageclassification -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MessageClassification @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MessageClassification cmdlet to configure an existing message classification instance in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,11 +32,12 @@ Set-MessageClassification [-Identity] [-RecipientDescription ] [-RetainClassificationEnabled ] [-SenderDescription ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,7 +49,6 @@ Set-MessageClassification -Identity "My Message Classification" -DisplayPreceden This example makes the following configuration changes to the message classification named My Message Classification: - Changes the display precedence to Low. - - Specifies that the message classification shouldn't persist with the message if the message is forwarded or replied to. ## PARAMETERS @@ -58,16 +57,14 @@ This example makes the following configuration changes to the message classifica 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 - -- Identity: Default\\ or \\\; for example, "Default\My Message Classification" or "es-ES\My Message Classification". - +- Identity: `Default\` or `\`; for example, `"Default\My Message Classification"` or `"es-ES\My Message Classification"`. - ClassificationID (GUID) ```yaml Type: MessageClassificationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -79,7 +76,7 @@ Accept wildcard characters: False ### -ClassificationID 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-MessageCalssification -Identity "\. +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 ""`. ```yaml Type: Guid @@ -97,15 +94,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -136,21 +132,13 @@ Accept wildcard characters: False 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 - - Higher - - High - - MediumHigh - - Medium (This is the default value) - - MediumLow - - Low - - Lower - - Lowest Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. @@ -208,7 +196,6 @@ Accept wildcard characters: False 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. - - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information. ```yaml @@ -225,7 +212,7 @@ Accept wildcard characters: False ``` ### -RecipientDescription -The RecipientDescription parameter specifies the 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 ("). +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 @@ -259,7 +246,7 @@ Accept wildcard characters: False ``` ### -SenderDescription -The SenderDescription parameter specifies the 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 ("). +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 @@ -281,7 +268,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -295,12 +282,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationBatch.md b/exchange/exchange-ps/exchange/Set-MigrationBatch.md similarity index 82% rename from exchange/exchange-ps/exchange/move-and-migration/Set-MigrationBatch.md rename to exchange/exchange-ps/exchange/Set-MigrationBatch.md index 00bd0f1833..17981b8c20 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationBatch.md +++ b/exchange/exchange-ps/exchange/Set-MigrationBatch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-migrationbatch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MigrationBatch @@ -15,14 +14,15 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the Set-MigrationBatch cmdlet to update a migration request for a batch of users. For more information, see [New-MigrationBatch](https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-migrationbatch). +Use the Set-MigrationBatch cmdlet to update a migration request for a batch of users. For more information, see [New-MigrationBatch](https://learn.microsoft.com/powershell/module/exchange/new-migrationbatch). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-MigrationBatch [-Identity] + [-AddUsers] [-AllowIncrementalSyncs ] [-AllowUnknownColumnsInCsv ] [-ApproveSkippedItems] @@ -44,29 +44,24 @@ Set-MigrationBatch [-Identity] [-StartAfter ] [-SyncNow] [-Update] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION The Set-MigrationBatch cmdlet configures your existing migration batches to migrate mailboxes and mailbox data in one of the following scenarios: - Local move - - Cross-forest move - - Remote move - - Cutover Exchange migration - - Staged Exchange migration - - IMAP migration - -- G Suite migration +- Google Workspace (formerly G Suite) migration Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -83,7 +78,6 @@ This example updates MigrationBatch01 by approving all of the skipped items for 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) - - GUID (the BatchGuid property value) ```yaml @@ -99,13 +93,30 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -AddUsers +This parameter is available only in the cloud-based service. + +{{ Fill AddUsers Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -AllowIncrementalSyncs This parameter is available only in on-premises Exchange. The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: - $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. - - $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization. ```yaml @@ -125,7 +136,6 @@ Accept wildcard characters: False 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. - - $false: The migration fails if there are any unknown columns in the CSV file. This setting protects against spelling errors in column headers. This is the default value. ```yaml @@ -144,11 +154,11 @@ Accept wildcard characters: False ### -ApproveSkippedItems This parameter is available only in the cloud-based service. -The ApproveSkippedItems switch marks all of the skipped items discovered prior to the current 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. +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. -For more information about maximum message size values, see the following topic [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926). +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. -You don't need to specify a value with this switch. +For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). ```yaml Type: SwitchParameter @@ -202,25 +212,22 @@ Accept wildcard characters: False ``` ### -CompleteAfter -This parameter is available only in the cloud-based service. +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 won't complete until the date/time you specify with this parameter. +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. -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". +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". -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: -To specify a date/time value for this parameter, use either of the following options: - -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +- Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -232,8 +239,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -250,15 +256,17 @@ Accept wildcard characters: False ``` ### -CSVData -This parameter is available only in on-premises Exchange. +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. -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. Use the following format for the value of this parameter: ([System.IO.File]::ReadAllBytes(\)). For example: -CSVData ([System.IO.File]::ReadAllBytes("C:\\Users\\Administrator\\Desktop\\MigrationBatch\_1.csv")) +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`). + +**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. ```yaml Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -290,9 +298,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. @@ -334,9 +341,7 @@ The NotificationEmails parameter specifies one or more email addresses that migr If you don't use this parameter, the status report isn't sent. -To enter multiple values and overwrite any existing entries, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\","\",..."\". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\","\"...; Remove="\","\"...}. +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"`. ```yaml Type: MultiValuedProperty @@ -445,9 +450,7 @@ 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: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -464,25 +467,20 @@ Accept wildcard characters: False ``` ### -StartAfter -This parameter is available only in the cloud-based service. - 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". - -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). - -To specify a date/time value for this parameter, use either of the following options: +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". -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +- Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -548,12 +546,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationConfig.md b/exchange/exchange-ps/exchange/Set-MigrationConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/move-and-migration/Set-MigrationConfig.md rename to exchange/exchange-ps/exchange/Set-MigrationConfig.md index c819e86deb..99bb6f912b 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationConfig.md +++ b/exchange/exchange-ps/exchange/Set-MigrationConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-migrationconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MigrationConfig @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MigrationConfig cmdlet to edit migration configurations on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,11 +28,12 @@ Set-MigrationConfig [-MaxConcurrentMigrations ] [-MaxNumberOfBatches ] [-Partition ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,8 +56,7 @@ This example sets the migration system to only allow 100 concurrent migrations. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -97,11 +96,8 @@ 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: - None - - MultiBatch - - Endpoints - - UpgradeBlock ```yaml @@ -162,7 +158,7 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -178,7 +174,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -192,12 +188,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationEndpoint.md b/exchange/exchange-ps/exchange/Set-MigrationEndpoint.md similarity index 81% rename from exchange/exchange-ps/exchange/move-and-migration/Set-MigrationEndpoint.md rename to exchange/exchange-ps/exchange/Set-MigrationEndpoint.md index bd41083148..cade570874 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationEndpoint.md +++ b/exchange/exchange-ps/exchange/Set-MigrationEndpoint.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-migrationendpoint +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MigrationEndpoint @@ -15,14 +14,17 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the Set-MigrationEndpoint cmdlet to edit settings for cutover or staged Exchange migrations, IMAP migrations, G Suite migrations, and remote moves. +Use the Set-MigrationEndpoint cmdlet to edit settings for cutover or staged Exchange migrations, IMAP migrations, Google Workspace (formerly G Suite) migrations, and remote moves. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-MigrationEndpoint [-Identity] + [-AcceptUntrustedCertificates ] + [-ApplicationId ] + [-AppSecretKeyVaultUrl ] [-Authentication ] [-Confirm] [-Credentials ] @@ -42,35 +44,29 @@ Set-MigrationEndpoint [-Identity] [-SkipVerification] [-SourceMailboxLegacyDN ] [-TestMailbox ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION Use the Set-MigrationEndpoint cmdlet to configure settings for different types of migration: - Cross-forest move: Move mailboxes between two different on-premises Exchange forests. Cross-forest moves require the use of a RemoteMove endpoint. - -- Remote move: In a hybrid deployment, a remote move involves onboarding or offboarding migrations. Remote moves require the use of a RemoteMove endpoint. Onboarding moves mailboxes from an on-premises Exchange organization to Exchange Online in Office 365, and uses a RemoteMove endpoint as the source endpoint of the migration batch. Offboarding moves mailboxes from Exchange Online in Office 365 to an on-premises Exchange organization and uses a RemoteMove endpoint as the target endpoint of the migration batch. - -- Cutover Exchange migration: Migrate all mailboxes in an on-premises Exchange organization to Exchange Online in Office 365. Cutover Exchange migration requires the use of an Exchange endpoint. - -- Staged Exchange migration: Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online in Office 365. Staged Exchange migration requires the use of an Exchange endpoint. - -- IMAP migration: Migrate mailbox data from an on-premises Exchange organization or other email system to Exchange Online in Office 365. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP migrations require the use of an IMAP endpoint. - -- Gmail migration: Migration mailbox data from a G Suite tenant to Exchange Online in Office 365. For a G Suite migration, you must first create the cloud-based mail users or mailboxes before you migrate mailbox data. G Suite migrations require the use of a Gmail endpoint. - +- Remote move: In a hybrid deployment, a remote move involves onboarding or offboarding migrations. Remote moves require the use of a RemoteMove endpoint. Onboarding moves mailboxes from an on-premises Exchange organization to Exchange Online, and uses a RemoteMove endpoint as the source endpoint of the migration batch. Offboarding moves mailboxes from Exchange Online to an on-premises Exchange organization and uses a RemoteMove endpoint as the target endpoint of the migration batch. +- Cutover Exchange migration: Migrate all mailboxes in an on-premises Exchange organization to Exchange Online. Cutover Exchange migration requires the use of an Exchange endpoint. +- Staged Exchange migration: Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. Staged Exchange migration requires the use of an Exchange endpoint. +- IMAP migration: Migrate mailbox data from an on-premises Exchange organization or other email system to Exchange Online. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP migrations require the use of an IMAP endpoint. +- Gmail migration: Migration mailbox data from a Google Workspace tenant to Exchange Online. For a Google Workspace migration, you must first create the cloud-based mail users or mailboxes before you migrate mailbox data. Google Workspace migrations require the use of a Gmail endpoint. - Local: Move mailboxes between different servers or databases within a single on-premises Exchange forest. Local moves don't require the use of an endpoint. For more information about the different move and migration scenarios, see: -- [Mailbox moves in Exchange Server](https://docs.microsoft.com/Exchange/recipients/mailbox-moves) - -- [Manage on-premises mailbox moves in Exchange Server](https://docs.microsoft.com/Exchange/architecture/mailbox-servers/manage-mailbox-moves) +- [Mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/recipients/mailbox-moves) +- [Manage on-premises mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/architecture/mailbox-servers/manage-mailbox-moves) Changes made to an endpoint that affect the individual users within the batch are applied starting at the next time that the batch is processed. If you are running this cmdlet in the cloud-based service and wish to speed up the application of these settings, consider running the Set-MigrationBatch cmdlet with the -Update parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -106,6 +102,60 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -AcceptUntrustedCertificates +This parameter is available only in the cloud-based service. + +{{ Fill AcceptUntrustedCertificates Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplicationId +This parameter is available only in the cloud-based service. + +{{ Fill ApplicationId Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppSecretKeyVaultUrl +This parameter is available only in the cloud-based service. + +{{ Fill AppSecretKeyVaultUrl Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Authentication This parameter is available only in the cloud-based service. @@ -127,8 +177,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -147,7 +196,7 @@ Accept wildcard characters: False ### -Credentials 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -206,7 +255,6 @@ The MailboxPermission parameter specifies what permissions should be used to acc The account specified must have the following permissions: - FullAccess permission. The account has Full-Access permission to the mailboxes they want to migrate. - - Admin permission. The account is a domain administrator who can access any mailbox they want to migrate. ```yaml @@ -330,7 +378,6 @@ Accept wildcard characters: False 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. - - IMAP moves: The FQDN of the IMAP server. ```yaml @@ -373,7 +420,7 @@ For an IMAP migration, the Security parameter specifies the encryption method us Type: IMAPSecurityMechanism Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -387,7 +434,7 @@ 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. -Use the following format for the value of this parameter: ([System.IO.File]::ReadAllBytes(\)). For example: -CSVData ([System.IO.File]::ReadAllBytes("C:\\Users\\Administrator\\Desktop\\service-account.json")) +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[] @@ -403,7 +450,7 @@ Accept wildcard characters: False ``` ### -SkipVerification -The SkipVerification switch specifies whether to skip verifying that the remote server is reachable when creating a migration endpoint. The default value is $false. +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 @@ -475,12 +522,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-MigrationUser.md b/exchange/exchange-ps/exchange/Set-MigrationUser.md new file mode 100644 index 0000000000..9a4d3dc9f8 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MigrationUser.md @@ -0,0 +1,300 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-MigrationUser + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Set-MigrationUser cmdlet to modify the migration settings of a user in an existing migration batch. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MigrationUser [-Identity] + [-ApproveSkippedItems] + [-BadItemLimit ] + [-CompleteAfter ] + [-Confirm] + [-DomainController ] + [-LargeItemLimit ] + [-Partition ] + [-StartAfter ] + [-SyncNow] + [-WhatIf] + [] +``` + +## DESCRIPTION +Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-MigrationUser -Identity laura@contoso.com -LargeItemLimit 15 -BadItemLimit 15 +``` + +This example changes the large item limit and bad item limit for the user laura@contoso.com in an existing migration batch. + +### Example 2 +```powershell +Set-MigrationUser -Identity laura@contoso.com -ApproveSkippedItems +``` + +This example approves all of the skipped items encountered for the user laura@contoso.com in an existing migration batch. + +## PARAMETERS + +### -Identity +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. + +```yaml +Type: MigrationUserIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ApproveSkippedItems +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. + +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. + +For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BadItemLimit +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. + +**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompleteAfter +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. + +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". + +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). + +To specify a date/time value for this parameter, use either of the following options: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LargeItemLimit +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: + +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) + +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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. + +**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Partition +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartAfter +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. + +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". + +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). + +To specify a date/time value for this parameter, use either of the following options: + +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncNow +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/exchange/Set-MobileDeviceMailboxPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/devices/Set-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/exchange/Set-MobileDeviceMailboxPolicy.md index 6754d2d859..1a4006943c 100644 --- a/exchange/exchange-ps/exchange/devices/Set-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Set-MobileDeviceMailboxPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-mobiledevicemailboxpolicy -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MobileDeviceMailboxPolicy @@ -17,41 +16,71 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MobileDeviceMailboxPolicy cmdlet to modify mobile device mailbox policies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-MobileDeviceMailboxPolicy [-Identity] - [-AllowApplePushNotifications ] [-AllowBluetooth ] - [-AllowBrowser ] [-AllowCamera ] [-AllowConsumerEmail ] - [-AllowDesktopSync ] [-AllowExternalDeviceManagement ] - [-AllowGooglePushNotifications ] [-AllowHTMLEmail ] - [-AllowInternetSharing ] [-AllowIrDA ] - [-AllowMicrosoftPushNotifications ] [-AllowMobileOTAUpdate ] - [-AllowNonProvisionableDevices ] [-AllowPOPIMAPEmail ] - [-AllowRemoteDesktop ] [-AllowSimplePassword ] + [-AllowApplePushNotifications ] + [-AllowBluetooth ] + [-AllowBrowser ] + [-AllowCamera ] + [-AllowConsumerEmail ] + [-AllowDesktopSync ] + [-AllowExternalDeviceManagement ] + [-AllowGooglePushNotifications ] + [-AllowHTMLEmail ] + [-AllowInternetSharing ] + [-AllowIrDA ] + [-AllowMicrosoftPushNotifications ] + [-AllowMobileOTAUpdate ] + [-AllowNonProvisionableDevices ] + [-AllowPOPIMAPEmail ] + [-AllowRemoteDesktop ] + [-AllowSimplePassword ] [-AllowSMIMEEncryptionAlgorithmNegotiation ] - [-AllowSMIMESoftCerts ] [-AllowStorageCard ] - [-AllowTextMessaging ] [-AllowUnsignedApplications ] - [-AllowUnsignedInstallationPackages ] [-AllowWiFi ] - [-AlphanumericPasswordRequired ] [-ApprovedApplicationList ] - [-AttachmentsEnabled ] [-Confirm] [-DeviceEncryptionEnabled ] - [-DevicePolicyRefreshInterval ] [-DomainController ] [-IrmEnabled ] - [-IsDefault ] [-MaxAttachmentSize ] + [-AllowSMIMESoftCerts ] + [-AllowStorageCard ] + [-AllowTextMessaging ] + [-AllowUnsignedApplications ] + [-AllowUnsignedInstallationPackages ] + [-AllowWiFi ] + [-AlphanumericPasswordRequired ] + [-ApprovedApplicationList ] + [-AttachmentsEnabled ] + [-Confirm] + [-DeviceEncryptionEnabled ] + [-DevicePolicyRefreshInterval ] + [-DomainController ] + [-IrmEnabled ] + [-IsDefault ] + [-MaxAttachmentSize ] [-MaxCalendarAgeFilter ] [-MaxEmailAgeFilter ] - [-MaxEmailBodyTruncationSize ] [-MaxEmailHTMLBodyTruncationSize ] - [-MaxInactivityTimeLock ] [-MaxPasswordFailedAttempts ] - [-MinPasswordComplexCharacters ] [-MinPasswordLength ] [-Name ] - [-PasswordEnabled ] [-PasswordExpiration ] [-PasswordHistory ] - [-PasswordRecoveryEnabled ] [-RequireDeviceEncryption ] + [-MaxEmailBodyTruncationSize ] + [-MaxEmailHTMLBodyTruncationSize ] + [-MaxInactivityTimeLock ] + [-MaxPasswordFailedAttempts ] + [-MinPasswordComplexCharacters ] + [-MinPasswordLength ] + [-Name ] + [-PasswordEnabled ] + [-PasswordExpiration ] + [-PasswordHistory ] + [-PasswordRecoveryEnabled ] + [-RequireDeviceEncryption ] [-RequireEncryptedSMIMEMessages ] [-RequireEncryptionSMIMEAlgorithm ] - [-RequireManualSyncWhenRoaming ] [-RequireSignedSMIMEAlgorithm ] - [-RequireSignedSMIMEMessages ] [-RequireStorageCardEncryption ] - [-UnapprovedInROMApplicationList ] [-UNCAccessEnabled ] [-WhatIf] - [-WSSAccessEnabled ] [] + [-RequireManualSyncWhenRoaming ] + [-RequireSignedSMIMEAlgorithm ] + [-RequireSignedSMIMEMessages ] + [-RequireStorageCardEncryption ] + [-UnapprovedInROMApplicationList ] + [-UNCAccessEnabled ] + [-WhatIf] + [-WSSAccessEnabled ] + [] ``` ## DESCRIPTION @@ -59,7 +88,9 @@ Mobile device mailbox policies define settings for mobile devices that are used Some mobile device mailbox policy settings require the mobile device to have specific built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This applies to devices that can't enforce all policy settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -90,9 +121,7 @@ This example sets several policy settings for the mobile device mailbox policy D The Identity parameter specifies the mobile device mailbox policy. You can use any value that uniquely identifies the policy. For example: - Name - - Distinguished name (DN) - - GUID The name of the built-in mobile device mailbox policy is Default. @@ -129,7 +158,15 @@ Accept wildcard characters: False ``` ### -AllowBluetooth -The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile device. The available options are Disable, HandsfreeOnly, and Allow. The default value is Allow. +The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile device. Valid values are: + +- Allow (this is the default value). +- Disable +- HandsfreeOnly + +The values Allow or HandsfreeOnly allow synchronization between Outlook for Android and the Outlook for Android wearable app for the associated Microsoft account. + +The value Disable disables synchronization between Outlook for Android and the Outlook for Android wearable app for the associated Microsoft account. Any previously synchronized data is deleted. This value does not disable Bluetooth on the Android device or the wearable device, nor does it affect other Android wearable apps. ```yaml Type: BluetoothType @@ -233,7 +270,7 @@ The AllowGooglePushNotifications parameter controls whether the user can receive Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -299,7 +336,7 @@ The AllowMicrosoftPushNotifications parameter specifies whether push notificatio Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -394,9 +431,7 @@ Accept wildcard characters: False 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 - - BlockNegotiation - - OnlyStrongAlgorithmNegotiation The default value is AllowAnyAlgorithmNegotiation. @@ -563,15 +598,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -581,6 +615,8 @@ Accept wildcard characters: False ``` ### -DeviceEncryptionEnabled +**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. When this parameter is set to $true, device encryption is enabled on the mobile device. @@ -678,9 +714,7 @@ Unqualified values are treated as bytes. You can qualify the value with KB (kilo The maximum value is 1024 bytes (one kilobyte) less than two gigabytes (2\*1024^3), so these are the maximum qualified values you can use with this parameter. - 2097151KB - - 2047.999024MB - - 1.999999047GB ```yaml @@ -700,13 +734,9 @@ Accept wildcard characters: False 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 - - TwoWeeks - - OneMonth - - ThreeMonths - - SixMonths The default value is All. @@ -728,15 +758,10 @@ Accept wildcard characters: False 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 - - OneDay - - ThreeDays - - OneWeek - - TwoWeeks - - OneMonth The default value is All. @@ -794,7 +819,6 @@ Accept wildcard characters: False 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). - - The value Unlimited. This is the default value. ```yaml @@ -832,11 +856,8 @@ Accept wildcard characters: False The MinPasswordComplexCharacters parameter specifies the character sets that are required in the password of the mobile device. The character sets are: - Lower case letters. - - Upper case letters. - - Digits 0 through 9. - - Special characters (for example, exclamation marks). A valid value for this parameter is an integer from 1 through 4. The default value is 1. @@ -846,11 +867,8 @@ For Windows Phone 8 devices, the value specifies the number of character sets th For Windows Phone 10 devices, the value specifies the following password complexity requirements: - Digits only. - - Digits and lower case letters. - - Digits, lower case letters, and upper case letters. - - Digits, lower case letters, upper case letters and special characters. ```yaml @@ -867,6 +885,8 @@ Accept wildcard characters: False ``` ### -MinPasswordLength +**Note**: This setting is supported by Outlook for Android. + The MinPasswordLength parameter specifies the minimum number of characters in the mobile device password. You can enter any number from 1 through 16 or the value $null. The default value is blank. The maximum password length is 16 characters. @@ -922,7 +942,6 @@ Accept wildcard characters: False 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). - - The value Unlimited. This is the default value ```yaml @@ -1010,13 +1029,9 @@ Accept wildcard characters: False 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 - - TripleDES - - RC240bit - - RC264bit - - RC2128bit The default value is TripleDES. @@ -1141,7 +1156,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1171,12 +1186,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Set-MoveRequest.md b/exchange/exchange-ps/exchange/Set-MoveRequest.md similarity index 88% rename from exchange/exchange-ps/exchange/move-and-migration/Set-MoveRequest.md rename to exchange/exchange-ps/exchange/Set-MoveRequest.md index 131b844155..1d1ecd41fb 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Set-MoveRequest.md +++ b/exchange/exchange-ps/exchange/Set-MoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-moverequest -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-MoveRequest @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-MoveRequest cmdlet to change move request options after the move request has been created. You can use the Set-MoveRequest cmdlet to recover from failed move requests. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -46,16 +45,18 @@ Set-MoveRequest [-Identity] [-RequestExpiryInterval ] [-SkipMoving ] [-SkippedItemApprovalTime ] + [-SourceEndpoint ] [-StartAfter ] [-SuspendWhenReadyToComplete ] [-TargetDatabase ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION You can pipeline the Set-MoveRequest cmdlet from the Get-MoveRequestStatistics, Get-MoveRequest, or Get-Mailbox cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,24 +80,18 @@ This example changes the move request for Sruthi to approve all skipped items en The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values: - GUID - - Distinguished name (DN) - - Domain\\Account - - User principal name (UPN) - - LegacyExchangeDN - - SMTP address - - Alias ```yaml Type: MoveRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -131,14 +126,11 @@ 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: - Name - - Distinguished name (DN) - - GUID You can use this parameter to change the target database only if the move request has a MoveStatus value of Queued. - ```yaml Type: DatabaseIdParameter Parameter Sets: (All) @@ -193,15 +185,14 @@ Accept wildcard characters: False ### -CompleteAfter 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". +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". -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a date/time value for this parameter, use either of the following options: -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). ```yaml Type: DateTime @@ -235,15 +226,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -329,9 +319,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -374,7 +363,6 @@ Accept wildcard characters: False 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. - - $false: This is the default value. The move request is run and allowed to complete. If you created the move request with the SuspendWhenReadyToComplete or PreventCompletion switches, set this parameter to $false before you run the Resume-MoveRequest cmdlet to complete the move request. ```yaml @@ -396,19 +384,12 @@ 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: - Lowest - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml @@ -448,23 +429,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -483,7 +455,7 @@ Accept wildcard characters: False ### -RemoteCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -534,7 +506,6 @@ Accept wildcard characters: False 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. - - If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -572,18 +543,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceEndpoint +This parameter is available only in the cloud-based service. + +{{ Fill SourceEndpoint Description }} + +```yaml +Type: MigrationEndpointIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -StartAfter 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". +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". -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). +In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a date/time value for this parameter, use either of the following options: -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). ```yaml Type: DateTime @@ -603,13 +591,12 @@ 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. -For more information about maximum message size values, see the following topic [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926). +For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). To specify a date/time value for this parameter, use either of the following options: -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). ```yaml Type: DateTime @@ -646,9 +633,7 @@ 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: - Name - - Distinguished name (DN) - - GUID You can use this parameter to change the target database only if the move request has a MoveStatus value of Queued. @@ -673,7 +658,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -687,12 +672,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-MyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Set-MyAnalyticsFeatureConfig.md new file mode 100644 index 0000000000..68c9290d33 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-MyAnalyticsFeatureConfig.md @@ -0,0 +1,177 @@ +--- +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 +ms.author: chrisda +--- + +# Set-MyAnalyticsFeatureConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Set-MyAnalyticsFeatureConfig cmdlet to configure the availability and features of MyAnalytics for the specified user. + +**Note**: This cmdlet replaces the Set-UserAnalyticsConfig cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-MyAnalyticsFeatureConfig -Identity + [-Feature ] + [-IsEnabled ] + [-PrivacyMode ] + [-ResultSize ] + [] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Set-MyAnalyticsFeatureConfig -Identity vikram@contoso.com -PrivacyMode opt-in +``` + +This example makes MyAnalytics and all features available to Vikram. + +### Example 2 +```powershell +Set-MyAnalyticsFeatureConfig -Identity swathy@contoso.com -PrivacyMode opt-in -Feature digest-email -IsEnabled $false +``` + +This example makes MyAnalytics available to Swathy, but disables the digest email feature. + +### Example 3 +```powershell +Set-MyAnalyticsFeatureConfig -Identity akshath@contoso.com -Feature digest-email -IsEnabled $false +``` + +This example disables the digest email feature for Akshath. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Feature +The Feature parameter specifies the MyAnalytics features to enable or disable for the user. Valid values are: + +- all (this is the default value) +- add-in +- dashboard +- digest-email + +To actually enable or disable a feature that's specified by this parameter, use the IsEnabled parameter in the same command. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Accepted values: dashboard, add-in, digest-email, all +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsEnabled +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. +- $false: The specified feature is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyMode +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. +-opt-out: MyAnalytics is disabled for the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Accepted values: opt-in, opt-out +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-Notification.md b/exchange/exchange-ps/exchange/Set-Notification.md similarity index 88% rename from exchange/exchange-ps/exchange/organization/Set-Notification.md rename to exchange/exchange-ps/exchange/Set-Notification.md index 4977faa4be..4d7ef423b7 100644 --- a/exchange/exchange-ps/exchange/organization/Set-Notification.md +++ b/exchange/exchange-ps/exchange/Set-Notification.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-notification +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-Notification @@ -15,9 +14,18 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || ## SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. -Use the Set-Notification cmdlet to modify notification events that are shown in the notification viewer in the Exchange admin center (EAC). These notification events are related to: +> [!NOTE] +> This cmdlet will be deprecated in the cloud-based service. The classic Exchange admin center was deprecated in the cloud-based service in 2023. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Use the Set-Notification cmdlet to modify notification events that are shown in the notification viewer in the Exchange admin center (EAC). These notifications are related to the following events: + +- Mailbox moves and migrations. +- Expiring and expired certificates. +- Exporting mailbox content to .pst files. +- Importing mailbox content from .pst files. +- Restoring deleted mailboxes. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +34,8 @@ For information about the parameter sets in the Syntax section below, see [Excha Set-Notification [-Identity] -NotificationEmails [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ### Settings @@ -34,11 +43,12 @@ Set-Notification [-Identity] -NotificationEmails -ProcessType [-Confirm] [-DomainController ] - [-WhatIf] [] + [-WhatIf] + [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,7 +69,7 @@ This example configures the specified notification event to send notification em ## PARAMETERS ### -Identity -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,AlternateID,StartTime,Status,Type. +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). @@ -84,7 +94,6 @@ The NotificationEmails parameter specifies the recipients for notification email You need to use this parameter with either the ProcessType or Identity parameters: - ProcessType: The only ProcessType value that's allowed is CertExpiry. - - Identity: You can modify the notification recipients for all types of notification events (CertExpiry, ExportPST, ImportPST, MailboxRestore, and Migration). For Migration events, you can also use the NotificationEmails parameter on the New-MigrationBatch, Set-MigrationBatch and Complete-MigrationBatch cmdlets to specify the notification email recipients. @@ -125,8 +134,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -181,12 +189,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-OMEConfiguration.md b/exchange/exchange-ps/exchange/Set-OMEConfiguration.md new file mode 100644 index 0000000000..5e1079d1bc --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-OMEConfiguration.md @@ -0,0 +1,333 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-OMEConfiguration + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-OMEConfiguration cmdlet to configure Microsoft Purview Message Encryption. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-OMEConfiguration [-Identity] + [-BackgroundColor ] + [-Confirm] + [-DisclaimerText ] + [-EmailText ] + [-ExternalMailExpiryInDays ] + [-Image ] + [-IntroductionText ] + [-OTPEnabled ] + [-PortalText ] + [-PrivacyStatementUrl ] + [-ReadButtonText ] + [-SocialIdSignIn ] + [-WhatIf] + [] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-OMEConfiguration -Identity "OME Configuration" -EmailText "Encrypted message enclosed." -PortalText "This portal is encrypted." -DisclaimerText "Encryption security disclaimer." -Image ([System.IO.File]::ReadAllBytes('C:\Temp\OME Logo.gif')) +``` + +This example configures the specified values for the default OME configuration named "OME Configuration". + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BackgroundColor +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. +- A valid color name value. For example, `yellow` is #ffff00. For a list of the valid color names, see [Background color reference](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages#background-color-reference). +- $null (blank). This is the default value. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisclaimerText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalMailExpiryInDays +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. + +You can't update the value of this parameter in the default OME configuration. You can only modify this value in a customized configuration. + +In the output of the Get-OMEConfiguration cmdlet, the value of this parameter is displayed in the ExternalMailExpiryInterval property. + +```yaml +Type: String +Parameter Sets: Int32 +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Image +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`). + +- Supported file formats: .png, .jpg, .bmp, or .tiff +- Optimal size of logo file: less than 40 KB +- Optimal dimensions of logo image: 170x70 pixels + +To remove an existing image and use the default image, use the value $null for this parameter. + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IntroductionText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OTPEnabled +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. +- $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PortalText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyStatementUrl +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadButtonText +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SocialIdSignIn +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. +- $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-OMEMessageRevocation.md b/exchange/exchange-ps/exchange/Set-OMEMessageRevocation.md new file mode 100644 index 0000000000..d08012a2ab --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-OMEMessageRevocation.md @@ -0,0 +1,92 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-OMEMessageRevocation + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-OMEMessageRevocation cmdlet to revoke Microsoft Purview Message Encryption for a message. Revoking encryption prevents the recipient from viewing the message in the OME portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-OMEMessageRevocation -MessageId -Revoke + [] +``` + +## DESCRIPTION +When an email has been revoked, the recipient will get the following error when they try to view the encrypted message in the OME portal: "The message has been revoked by the sender". + +You can revoke encrypted messages if the recipient received a link-based, branded encrypted email message. If the recipient received a native inline experience in a supported Outlook client, then you can't revoke encryption for the message. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-OMEMessageRevocation -MessageId "" -Revoke $true +``` + +This example revokes encryption for the specified message. + +## PARAMETERS + +### -MessageId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Revoke +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 +- $false: Encryption for the specified message isn't revoked. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OabVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-OabVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OabVirtualDirectory.md rename to exchange/exchange-ps/exchange/Set-OabVirtualDirectory.md index eb7f8cda26..23e45c17c1 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OabVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Set-OabVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/set-oabvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-OabVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-OABVirtualDirectory cmdlet to modify offline address book (OAB) virtual directories that are used in Internet Information Services (IIS) on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -40,7 +39,7 @@ Set-OabVirtualDirectory [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,20 +48,18 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-OABVirtualDirectory -Identity "Server1\OAB (Default Web Site)" -ExternalUrl "https://www.contoso.com/OAB" ``` -This example changes the external URL of the OAB virtual directory OAB (Default Web Site) to https://www.contoso.com/OAB. +This example changes the external URL of the OAB virtual directory OAB (Default Web Site) to `https://www.contoso.com/OAB`. ## PARAMETERS ### -Identity 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 \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -81,7 +78,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. You can use this parameter with the WindowsAuthentication parameter. @@ -102,8 +98,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -139,13 +134,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -165,8 +156,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \/\. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -185,14 +175,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -256,6 +242,8 @@ Accept wildcard characters: False ``` ### -PollInterval +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. ```yaml @@ -275,7 +263,6 @@ Accept wildcard characters: False 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. - - $false: SSL encryption isn't required to connect to the virtual directory. ```yaml @@ -311,7 +298,6 @@ Accept wildcard characters: False 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. - - $false: Integrated Windows authentication is disabled. You can use this parameter with the BasicAuthentication parameter. @@ -334,12 +320,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md b/exchange/exchange-ps/exchange/Set-OfflineAddressBook.md similarity index 90% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md rename to exchange/exchange-ps/exchange/Set-OfflineAddressBook.md index 54b591789d..b6bd614d26 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md +++ b/exchange/exchange-ps/exchange/Set-OfflineAddressBook.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/set-offlineaddressbook +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-OfflineAddressBook @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-OfflineAddressBook cmdlet to modify offline address book (OAB) settings. -In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -53,7 +52,7 @@ Set-OfflineAddressBook [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,9 +76,7 @@ This example changes the organization mailbox that's responsible for generating 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 - - Distinguished name (DN) - - GUID ```yaml @@ -99,12 +96,10 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID -To enter multiple values, use the following syntax: \,\,...\. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\","\",..."\". +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"`. You can find the identify values of address lists and global address lists by using the Get-AddressList and Get-GlobalAddressList cmdlets. @@ -140,7 +135,7 @@ Accept wildcard characters: False ``` ### -ConfiguredAttributes -The ConfiguredAttributes parameter specifies the recipient MAPI properties that are available in the OAB. This parameter uses the syntax: "\,\","\,\"... where \ is the name of the MAPI property (for example, MobileTelephoneNumber), and \ is the value ANR (ambiguous name resolution), Value, or Indicator. +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. @@ -160,8 +155,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -233,23 +227,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \\\\ - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) The default value for this parameter is the organization mailbox named SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}. @@ -275,7 +260,6 @@ 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: - $true: Any OAB virtual directory in the organization can accept requests to download the OAB. You can't use this setting with the VirtualDirectories parameter. - - $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This is the default value. In Exchange 2013 CU7 or later, we recommend that you use the value $true for this parameter. The Client Access services on any Mailbox server can proxy incoming OAB download requests to the correct location. @@ -297,7 +281,6 @@ Accept wildcard characters: False 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. - - $false: The OAB is isn't the default OAB. ```yaml @@ -402,7 +385,7 @@ Accept wildcard characters: False ``` ### -PublicFolderDistributionEnabled -This parameter is available or functional only in 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. @@ -420,20 +403,18 @@ Accept wildcard characters: False ``` ### -Schedule -This parameter is available only in on-premises Exchange. +This parameter is functional only in Exchange 2010. -Note: 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://docs.microsoft.com/Exchange/plan-and-deploy/post-installation-tasks/change-oab-generation-schedule). +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). The Schedule parameter specifies the interval for generating the OAB in Exchange 2010 or earlier. -The syntax for this parameter is: StartDay.Hour:Minute \[AM/PM\]-EndDay.Hour:Minute \[AM/PM\]. +The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -445,18 +426,16 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" -Note: In Office 365, the read only value of this property is displayed in Coordinated Universal Time (UTC). +**Note**: In Exchange Online, the read only value of this property is displayed in Coordinated Universal Time (UTC). ```yaml Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -471,7 +450,6 @@ 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: - $true: The OAB is distributed to all other organization mailboxes. - - $false: The OAB is isn't distributed to other organization mailboxes. This is the default value. The value of this parameter is only meaningful if you have multiple organization mailboxes, and is only beneficial in Exchange organizations that have multiple Active Directory sites. @@ -524,7 +502,11 @@ Accept wildcard characters: False ``` ### -Versions -The Versions parameter specifies the OAB versions that are generated for client download. In Exchange 2013 or later, the default and only supported value is Version4 (Version3 and Version2 require public folder distribution). +The Versions parameter specifies the OAB versions that are generated for client download. Valid values are: + +- Version2 (requires public folder distribution) +- Version3 (requires public folder distribution) +- Version4 (default value in Exchange 2010 or later; the only available value in Exchange 2013 or later) ```yaml Type: MultiValuedProperty @@ -546,13 +528,11 @@ The VirtualDirectories parameter specifies the OAB virtual directories that acce You can use any value that uniquely identifies the virtual directory. For example: -- Name or \\\Name - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\ (\)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. The default value of this parameter is the Client Access services (frontend) and backend OAB virtual directories on the Mailbox server that holds the OAB generation mailbox (the GeneratingMailbox parameter or SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}) when you created the OAB (for example, Mailbox01\\OAB (Default Web Site),Mailbox01\\OAB (Exchange Back End). @@ -593,7 +573,6 @@ Accept wildcard characters: False 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. - - $false: Don't ZIP the OAB files. This is the default value. ```yaml @@ -614,12 +593,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/Set-OnPremisesOrganization.md new file mode 100644 index 0000000000..666358469d --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-OnPremisesOrganization.md @@ -0,0 +1,218 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-OnPremisesOrganization + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-OnPremisesOrganization cmdlet to modify the parameters of the OnPremisesOrganization object on the Microsoft 365 tenant. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-OnPremisesOrganization [-Identity] + [-Comment ] + [-Confirm] + [-HybridDomains ] + [-InboundConnector ] + [-OrganizationName ] + [-OrganizationRelationship ] + [-OutboundConnector ] + [-WhatIf] + [] +``` + +## DESCRIPTION +The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-OnPremisesOrganization -Identity "ExchangeMail" -HybridDomains contoso.com, sales.contoso.com, legal.contoso.com +``` + +This example adds a third domain legal.contoso.com to the ExchangeMail OnPremisesOrganization object on the Microsoft 365 organization, which already has the contoso.com and sales.contoso.com domains. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the identity of the on-premises organization object. You can use the following values: + +- Canonical name +- GUID +- Name + +```yaml +Type: OnPremisesOrganizationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HybridDomains +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundConnector +The InboundConnector parameter specifies the name of the inbound connector configured on the Microsoft Exchange Online Protection (EOP) service 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationRelationship +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutboundConnector +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-OrganizationConfig.md b/exchange/exchange-ps/exchange/Set-OrganizationConfig.md new file mode 100644 index 0000000000..738f268b0b --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-OrganizationConfig.md @@ -0,0 +1,4074 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-OrganizationConfig + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-OrganizationConfig cmdlet to configure various settings of an Exchange organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### ShortenEventScopeParameter +``` +Set-OrganizationConfig -ShortenEventScopeDefault + [-AcceptedDomainApprovedSendersEnabled ] + [-ActionableMessagesExtenalAccessTokenEnabled ] + [-ActivityBasedAuthenticationTimeoutEnabled ] + [-ActivityBasedAuthenticationTimeoutInterval ] + [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled ] + [-AppsForOfficeEnabled ] + [-AsyncSendEnabled ] + [-AuditDisabled ] + [-AutodiscoverPartialDirSync ] + [-AutoEnableArchiveMailbox ] + [-AutoExpandingArchive] + [-AutomaticForcedReadReceiptEnabled ] + [-BlockMoveMessagesForGroupFolders ] + [-BookingsAddressEntryRestricted ] + [-BookingsAuthEnabled ] + [-BookingsBlockedWordsEnabled ] + [-BookingsCreationOfCustomQuestionsRestricted ] + [-BookingsEnabled ] + [-BookingsExposureOfStaffDetailsRestricted ] + [-BookingsMembershipApprovalRequired ] + [-BookingsNamingPolicyEnabled ] + [-BookingsNamingPolicyPrefix ] + [-BookingsNamingPolicyPrefixEnabled ] + [-BookingsNamingPolicySuffix ] + [-BookingsNamingPolicySuffixEnabled ] + [-BookingsNotesEntryRestricted ] + [-BookingsPaymentsEnabled ] + [-BookingsPhoneNumberEntryRestricted ] + [-BookingsSearchEngineIndexDisabled ] + [-BookingsSmsMicrosoftEnabled ] + [-BookingsSocialSharingRestricted ] + [-ByteEncoderTypeFor7BitCharsets ] + [-CalendarVersionStoreEnabled ] + [-ComplianceMLBgdCrawlEnabled ] + [-Confirm] + [-ConnectorsActionableMessagesEnabled ] + [-ConnectorsEnabled ] + [-ConnectorsEnabledForOutlook ] + [-ConnectorsEnabledForSharepoint ] + [-ConnectorsEnabledForTeams ] + [-ConnectorsEnabledForYammer ] + [-CustomerLockboxEnabled ] + [-DefaultAuthenticationPolicy ] + [-DefaultGroupAccessType ] + [-DefaultMinutesToReduceLongEventsBy ] + [-DefaultMinutesToReduceShortEventsBy ] + [-DefaultPublicFolderAgeLimit ] + [-DefaultPublicFolderDeletedItemRetention ] + [-DefaultPublicFolderIssueWarningQuota ] + [-DefaultPublicFolderMaxItemSize ] + [-DefaultPublicFolderMovedItemRetention ] + [-DefaultPublicFolderProhibitPostQuota ] + [-DirectReportsGroupAutoCreationEnabled ] + [-DisablePlusAddressInRecipients ] + [-DistributionGroupDefaultOU ] + [-DistributionGroupNameBlockedWordsList ] + [-DistributionGroupNamingPolicy ] + [-ElcProcessingDisabled ] + [-EnableForwardingAddressSyncForMailboxes ] + [-EnableOutlookEvents ] + [-EndUserDLUpgradeFlowsDisabled ] + [-EwsAllowEntourage ] + [-EwsAllowList ] + [-EwsAllowMacOutlook ] + [-EwsAllowOutlook ] + [-EwsApplicationAccessPolicy ] + [-EwsBlockList ] + [-EwsEnabled ] + [-ExchangeNotificationEnabled ] + [-ExchangeNotificationRecipients ] + [-FindTimeAttendeeAuthenticationEnabled ] + [-FindTimeAutoScheduleDisabled ] + [-FindTimeLockPollForAttendeesEnabled ] + [-FindTimeOnlineMeetingOptionDisabled ] + [-FocusedInboxOn ] + [-HierarchicalAddressBookRoot ] + [-HybridRSVPEnabled ] + [-IPListBlocked ] + [-IsAgendaMailEnabled ] + [-IsGroupFoldersAndRulesEnabled ] + [-IsGroupMemberAllowedToEditContent ] + [-LeanPopoutEnabled ] + [-LinkPreviewEnabled ] + [-MailTipsAllTipsEnabled ] + [-MailTipsExternalRecipientsTipsEnabled ] + [-MailTipsGroupMetricsEnabled ] + [-MailTipsLargeAudienceThreshold ] + [-MailTipsMailboxSourcedTipsEnabled ] + [-MaskClientIpInReceivedHeadersEnabled ] + [-MatchSenderOrganizerProperties ] + [-MessageHighlightsEnabled ] + [-MessageRecallAlertRecipientsEnabled ] + [-MessageRecallAlertRecipientsReadMessagesOnlyEnabled ] + [-MessageRecallEnabled ] + [-MessageRecallMaxRecallableAge ] + [-MessageRemindersEnabled ] + [-MobileAppEducationEnabled ] + [-OAuth2ClientProfileEnabled ] + [-OnlineMeetingsByDefaultEnabled ] + [-OutlookGifPickerDisabled ] + [-OutlookMobileGCCRestrictionsEnabled ] + [-OutlookMobileHelpShiftEnabled ] + [-OutlookMobileSingleAccountEnabled ] + [-OutlookPayEnabled ] + [-OutlookTextPredictionDisabled ] + [-PerTenantSwitchToESTSEnabled ] + [-PostponeRoamingSignaturesUntilLater ] + [-PreferredInternetCodePageForShiftJis ] + [-PublicComputersDetectionEnabled ] + [-PublicFoldersEnabled ] + [-PublicFolderShowClientControl ] + [-ReadTrackingEnabled ] + [-RecallReadMessagesEnabled ] + [-RefreshSessionEnabled ] + [-RejectDirectSend ] + [-RemotePublicFolderMailboxes ] + [-RequiredCharsetCoverage ] + [-SendFromAliasEnabled ] + [-SharedDomainEmailAddressFlowEnabled ] + [-SiteMailboxCreationURL ] + [-SmtpActionableMessagesEnabled ] + [-TwoClickMailPreviewEnabled ] + [-UnblockUnsafeSenderPromptEnabled ] + [-VisibleMeetingUpdateProperties ] + [-WebPushNotificationsDisabled ] + [-WebSuggestedRepliesDisabled ] + [-WhatIf] + [-WorkspaceTenantEnabled ] + [] +``` + +### AdfsAuthenticationParameter +``` +Set-OrganizationConfig [-AdfsAudienceUris ] [-AdfsEncryptCertificateThumbprint ] [-AdfsIssuer ] [-AdfsSignCertificateThumbprints ] + [-ACLableSyncedObjectEnabled ] + [-ActivityBasedAuthenticationTimeoutEnabled ] + [-ActivityBasedAuthenticationTimeoutInterval ] + [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled ] + [-AppsForOfficeEnabled ] + [-AsyncSendEnabled ] + [-ByteEncoderTypeFor7BitCharsets ] + [-Confirm] + [-ConnectorsActionableMessagesEnabled ] + [-ConnectorsEnabled ] + [-CustomerFeedbackEnabled ] + [-DataClassifications ] + [-DefaultAuthenticationPolicy ] + [-DefaultPublicFolderAgeLimit ] + [-DefaultPublicFolderDeletedItemRetention ] + [-DefaultPublicFolderIssueWarningQuota ] + [-DefaultPublicFolderMaxItemSize ] + [-DefaultPublicFolderMovedItemRetention ] + [-DefaultPublicFolderProhibitPostQuota ] + [-DistributionGroupDefaultOU ] + [-DistributionGroupNameBlockedWordsList ] + [-DistributionGroupNamingPolicy ] + [-DomainController ] + [-EmptyAddressBookForNonExchangeUsers] + [-EnableAuthAdminReadSession] + [-EnableDownloadDomains ] + [-EnableOrgWidePermissionOnScopedRoles] + [-EwsAllowEntourage ] + [-EwsAllowList ] + [-EwsAllowMacOutlook ] + [-EwsAllowOutlook ] + [-EwsApplicationAccessPolicy ] + [-EwsBlockList ] + [-EwsEnabled ] + [-HierarchicalAddressBookRoot ] + [-Industry ] + [-IsAgendaMailEnabled ] + [-IsExcludedFromOffboardMigration ] + [-IsExcludedFromOnboardMigration ] + [-IsFfoMigrationInProgress ] + [-LeanPopoutEnabled ] + [-LinkPreviewEnabled ] + [-MailboxDataEncryptionEnabled] + [-MailTipsAllTipsEnabled ] + [-MailTipsExternalRecipientsTipsEnabled ] + [-MailTipsGroupMetricsEnabled ] + [-MailTipsLargeAudienceThreshold ] + [-MailTipsMailboxSourcedTipsEnabled ] + [-ManagedFolderHomepage ] + [-MapiHttpEnabled ] + [-MaxConcurrentMigrations ] + [-MicrosoftExchangeRecipientEmailAddresses ] + [-MicrosoftExchangeRecipientEmailAddressPolicyEnabled ] + [-MicrosoftExchangeRecipientPrimarySmtpAddress ] + [-MicrosoftExchangeRecipientReplyRecipient ] + [-MitigationsEnabled ] + [-OabShadowDistributionOldestFileAgeLimit ] + [-OAuth2ClientProfileEnabled ] + [-OrganizationSummary ] + [-PreferredInternetCodePageForShiftJis ] + [-PublicComputersDetectionEnabled ] + [-PublicFolderMailboxesLockedForNewConnections ] + [-PublicFolderMailboxesMigrationComplete ] + [-PublicFolderMigrationComplete ] + [-PublicFolderShowClientControl ] + [-PublicFoldersEnabled ] + [-PublicFoldersLockedForMigration ] + [-ReadTrackingEnabled ] + [-RefreshSessionEnabled ] + [-RemotePublicFolderMailboxes ] + [-RequiredCharsetCoverage ] + [-SCLJunkThreshold ] + [-SiteMailboxCreationURL ] + [-SmtpActionableMessagesEnabled ] + [-UMAvailableLanguages ] + [-UnblockUnsafeSenderPromptEnabled ] + [-UseIcsSyncStateStreaming] + [-WACDiscoveryEndpoint ] + [-WhatIf] + [] +``` + +### AdfsAuthenticationRawConfiguration +``` +Set-OrganizationConfig [-AdfsAuthenticationConfiguration ] + [-ACLableSyncedObjectEnabled ] + [-ActivityBasedAuthenticationTimeoutEnabled ] + [-ActivityBasedAuthenticationTimeoutInterval ] + [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled ] + [-AppsForOfficeEnabled ] + [-AsyncSendEnabled ] + [-ByteEncoderTypeFor7BitCharsets ] + [-Confirm] + [-ConnectorsActionableMessagesEnabled ] + [-ConnectorsEnabled ] + [-CustomerFeedbackEnabled ] + [-DataClassifications ] + [-DefaultAuthenticationPolicy ] + [-DefaultPublicFolderAgeLimit ] + [-DefaultPublicFolderDeletedItemRetention ] + [-DefaultPublicFolderIssueWarningQuota ] + [-DefaultPublicFolderMaxItemSize ] + [-DefaultPublicFolderMovedItemRetention ] + [-DefaultPublicFolderProhibitPostQuota ] + [-DistributionGroupDefaultOU ] + [-DistributionGroupNameBlockedWordsList ] + [-DistributionGroupNamingPolicy ] + [-DomainController ] + [-EmptyAddressBookForNonExchangeUsers] + [-EnableAuthAdminReadSession] + [-EnableDownloadDomains ] + [-EnableOrgWidePermissionOnScopedRoles] + [-EwsAllowEntourage ] + [-EwsAllowList ] + [-EwsAllowMacOutlook ] + [-EwsAllowOutlook ] + [-EwsApplicationAccessPolicy ] + [-EwsBlockList ] + [-EwsEnabled ] + [-HierarchicalAddressBookRoot ] + [-Industry ] + [-IsAgendaMailEnabled ] + [-IsExcludedFromOffboardMigration ] + [-IsExcludedFromOnboardMigration ] + [-IsFfoMigrationInProgress ] + [-LeanPopoutEnabled ] + [-LinkPreviewEnabled ] + [-MailboxDataEncryptionEnabled] + [-MailTipsAllTipsEnabled ] + [-MailTipsExternalRecipientsTipsEnabled ] + [-MailTipsGroupMetricsEnabled ] + [-MailTipsLargeAudienceThreshold ] + [-MailTipsMailboxSourcedTipsEnabled ] + [-ManagedFolderHomepage ] + [-MapiHttpEnabled ] + [-MaxConcurrentMigrations ] + [-MicrosoftExchangeRecipientEmailAddresses ] + [-MicrosoftExchangeRecipientEmailAddressPolicyEnabled ] + [-MicrosoftExchangeRecipientPrimarySmtpAddress ] + [-MicrosoftExchangeRecipientReplyRecipient ] + [-MitigationsEnabled ] + [-OabShadowDistributionOldestFileAgeLimit ] + [-OAuth2ClientProfileEnabled ] + [-OrganizationSummary ] + [-PreferredInternetCodePageForShiftJis ] + [-PublicComputersDetectionEnabled ] + [-PublicFolderMailboxesLockedForNewConnections ] + [-PublicFolderMailboxesMigrationComplete ] + [-PublicFolderMigrationComplete ] + [-PublicFoldersEnabled ] + [-PublicFolderShowClientControl ] + [-PublicFoldersLockedForMigration ] + [-ReadTrackingEnabled ] + [-RefreshSessionEnabled ] + [-RemotePublicFolderMailboxes ] + [-RequiredCharsetCoverage ] + [-SCLJunkThreshold ] + [-SiteMailboxCreationURL ] + [-SmtpActionableMessagesEnabled ] + [-UMAvailableLanguages ] + [-UnblockUnsafeSenderPromptEnabled ] + [-UseIcsSyncStateStreaming] + [-WACDiscoveryEndpoint ] + [-WhatIf] + [] +``` + +### DelayedDelicensingParameterSet +``` +Set-OrganizationConfig [-DelayedDelicensingEnabled ] [-EndUserMailNotificationForDelayedDelicensingEnabled ] [-TenantAdminNotificationForDelayedDelicensingEnabled ] + [-AcceptedDomainApprovedSendersEnabled ] + [-ActionableMessagesExtenalAccessTokenEnabled ] + [-ActivityBasedAuthenticationTimeoutEnabled ] + [-ActivityBasedAuthenticationTimeoutInterval ] + [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled ] + [-AppsForOfficeEnabled ] + [-AsyncSendEnabled ] + [-AuditDisabled ] + [-AutodiscoverPartialDirSync ] + [-AutoEnableArchiveMailbox ] + [-AutoExpandingArchive] + [-AutomaticForcedReadReceiptEnabled ] + [-BlockMoveMessagesForGroupFolders ] + [-BookingsAddressEntryRestricted ] + [-BookingsAuthEnabled ] + [-BookingsBlockedWordsEnabled ] + [-BookingsCreationOfCustomQuestionsRestricted ] + [-BookingsEnabled ] + [-BookingsExposureOfStaffDetailsRestricted ] + [-BookingsMembershipApprovalRequired ] + [-BookingsNamingPolicyEnabled ] + [-BookingsNamingPolicyPrefix ] + [-BookingsNamingPolicyPrefixEnabled ] + [-BookingsNamingPolicySuffix ] + [-BookingsNamingPolicySuffixEnabled ] + [-BookingsNotesEntryRestricted ] + [-BookingsPaymentsEnabled ] + [-BookingsPhoneNumberEntryRestricted ] + [-BookingsSearchEngineIndexDisabled ] + [-BookingsSmsMicrosoftEnabled ] + [-BookingsSocialSharingRestricted ] + [-ByteEncoderTypeFor7BitCharsets ] + [-CalendarVersionStoreEnabled ] + [-ComplianceMLBgdCrawlEnabled ] + [-Confirm] + [-ConnectorsActionableMessagesEnabled ] + [-ConnectorsEnabled ] + [-ConnectorsEnabledForOutlook ] + [-ConnectorsEnabledForSharepoint ] + [-ConnectorsEnabledForTeams ] + [-ConnectorsEnabledForYammer ] + [-CustomerLockboxEnabled ] + [-DefaultAuthenticationPolicy ] + [-DefaultGroupAccessType ] + [-DefaultPublicFolderAgeLimit ] + [-DefaultPublicFolderDeletedItemRetention ] + [-DefaultPublicFolderIssueWarningQuota ] + [-DefaultPublicFolderMaxItemSize ] + [-DefaultPublicFolderMovedItemRetention ] + [-DefaultPublicFolderProhibitPostQuota ] + [-DirectReportsGroupAutoCreationEnabled ] + [-DisablePlusAddressInRecipients ] + [-DistributionGroupDefaultOU ] + [-DistributionGroupNameBlockedWordsList ] + [-DistributionGroupNamingPolicy ] + [-ElcProcessingDisabled ] + [-EnableForwardingAddressSyncForMailboxes ] + [-EnableOutlookEvents ] + [-EndUserDLUpgradeFlowsDisabled ] + [-EwsAllowEntourage ] + [-EwsAllowList ] + [-EwsAllowMacOutlook ] + [-EwsAllowOutlook ] + [-EwsApplicationAccessPolicy ] + [-EwsBlockList ] + [-EwsEnabled ] + [-ExchangeNotificationEnabled ] + [-ExchangeNotificationRecipients ] + [-FindTimeAttendeeAuthenticationEnabled ] + [-FindTimeAutoScheduleDisabled ] + [-FindTimeLockPollForAttendeesEnabled ] + [-FindTimeOnlineMeetingOptionDisabled ] + [-FocusedInboxOn ] + [-HierarchicalAddressBookRoot ] + [-HybridRSVPEnabled ] + [-IPListBlocked ] + [-IsAgendaMailEnabled ] + [-IsGroupFoldersAndRulesEnabled ] + [-IsGroupMemberAllowedToEditContent ] + [-LeanPopoutEnabled ] + [-LinkPreviewEnabled ] + [-MailTipsAllTipsEnabled ] + [-MailTipsExternalRecipientsTipsEnabled ] + [-MailTipsGroupMetricsEnabled ] + [-MailTipsLargeAudienceThreshold ] + [-MailTipsMailboxSourcedTipsEnabled ] + [-MaskClientIpInReceivedHeadersEnabled ] + [-MatchSenderOrganizerProperties ] + [-MessageHighlightsEnabled ] + [-MessageRecallEnabled ] + [-MessageRemindersEnabled ] + [-MobileAppEducationEnabled ] + [-OAuth2ClientProfileEnabled ] + [-OnlineMeetingsByDefaultEnabled ] + [-OutlookGifPickerDisabled ] + [-OutlookMobileGCCRestrictionsEnabled ] + [-OutlookMobileHelpShiftEnabled ] + [-OutlookMobileSingleAccountEnabled ] + [-OutlookPayEnabled ] + [-OutlookTextPredictionDisabled ] + [-PerTenantSwitchToESTSEnabled ] + [-PostponeRoamingSignaturesUntilLater ] + [-PreferredInternetCodePageForShiftJis ] + [-PublicComputersDetectionEnabled ] + [-PublicFoldersEnabled ] + [-PublicFolderShowClientControl ] + [-ReadTrackingEnabled ] + [-RefreshSessionEnabled ] + [-RemotePublicFolderMailboxes ] + [-RequiredCharsetCoverage ] + [-SendFromAliasEnabled ] + [-SharedDomainEmailAddressFlowEnabled ] + [-SiteMailboxCreationURL ] + [-SmtpActionableMessagesEnabled ] + [-TwoClickMailPreviewEnabled ] + [-UnblockUnsafeSenderPromptEnabled ] + [-VisibleMeetingUpdateProperties ] + [-WebPushNotificationsDisabled ] + [-WebSuggestedRepliesDisabled ] + [-WhatIf] + [-WorkspaceTenantEnabled ] + [] +``` + +### Identity +``` +Set-OrganizationConfig + [-ActivityBasedAuthenticationTimeoutEnabled ] + [-ActivityBasedAuthenticationTimeoutInterval ] + [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled ] + [-ByteEncoderTypeFor7BitCharsets ] + [-Confirm] + [-CustomerFeedbackEnabled ] + [-DefaultAuthenticationPolicy ] + [-DistributionGroupDefaultOU ] + [-DistributionGroupNameBlockedWordsList ] + [-DistributionGroupNamingPolicy ] + [-DomainController ] + [-EwsAllowEntourage ] + [-EwsAllowList ] + [-EwsAllowMacOutlook ] + [-EwsAllowOutlook ] + [-EwsApplicationAccessPolicy ] + [-EwsBlockList ] + [-EwsEnabled ] + [-Force] + [-HierarchicalAddressBookRoot ] + [-Industry ] + [-MailTipsAllTipsEnabled ] + [-MailTipsExternalRecipientsTipsEnabled ] + [-MailTipsGroupMetricsEnabled ] + [-MailTipsLargeAudienceThreshold ] + [-MailTipsMailboxSourcedTipsEnabled ] + [-ManagedFolderHomepage ] + [-MicrosoftExchangeRecipientEmailAddresses ] + [-MicrosoftExchangeRecipientEmailAddressPolicyEnabled ] + [-MicrosoftExchangeRecipientPrimarySmtpAddress ] + [-MicrosoftExchangeRecipientReplyRecipient ] + [-OabShadowDistributionOldestFileAgeLimit ] + [-OrganizationSummary ] + [-PermanentlyDeleteDisabled ] + [-PreferredInternetCodePageForShiftJis ] + [-PublicFolderContentReplicationDisabled ] + [-PublicFolderMigrationComplete ] + [-PublicFoldersLockedForMigration ] + [-ReadTrackingEnabled ] + [-RequiredCharsetCoverage ] + [-SCLJunkThreshold ] + [-WhatIf] + [] +``` + +## DESCRIPTION + +> [!TIP] +> The output of the **Get-OrganizationConfig** cmdlet often shows curly braces or `{}` around properties values that accept multiple comma-separated values. Don't use those extra characters in values for the corresponding parameters on this cmdlet. Use the syntax as explained in the parameter descriptions. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-OrganizationConfig -DistributionGroupDefaultOU Users\Groups -DistributionGroupNameBlockedWordsList curse,bad,offensive -DistributionGroupNamingPolicy "DL__" +``` + +This example creates a distribution group naming policy using the following configuration: + +Distribution groups will be created in the Users\\Groups container. + +The words curse, bad, and offensive will be blocked from being used in distribution group names. + +All distribution groups will be prefixed with `DL_` and suffixed with an underscore (\_\) and the user's department and country code. + +### Example 2 +```powershell +Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceBlockList -EwsBlockList $null +``` + +This example allows all client applications to use REST and EWS. + +### Example 3 +```powershell +Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceBlockList -EwsBlockList "OtherApps*" +``` + +This example allows all client applications to use REST and EWS, except those that are specified by the EwsBlockList parameter. + +### Example 4 +```powershell +Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceAllowList -EwsAllowList $null +``` + +This example prevents all client applications from using REST and EWS. + +### Example 5 +```powershell +Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceAllowList -EwsAllowList "CorpApp*" +``` + +This example allows only the client applications specified by the EwsAllowList parameter to use REST and EWS. + +### Example 6 +```powershell +Set-OrganizationConfig -VisibleMeetingUpdateProperties "Location,Subject,Body,AllProperties:15" +``` + +In Exchange Online, this example results in meeting updates being auto-processed (meeting update messages aren't visible in attendee Inbox folders) except any changes to meeting location, subject and body as well as any property changes within 15 minutes of the meeting start time. + +## PARAMETERS + +### -ShortenEventScopeDefault +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: + +- 0 or None: Calendar events in the organization don't automatically start late or end early. This is the default value. +- 1 or EndEarly: By default, the end time of all calendar events is reduced by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters. +- 2 or StartLate: By default, the start time of all calendar events is delayed by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters. + +```yaml +Type: ShortenEventScopeMode +Parameter Sets: ShortenEventScopeParameter +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AcceptedDomainApprovedSendersEnabled +This parameter is available only in the cloud-based service. + +{{ Fill AcceptedDomainApprovedSendersEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ACLableSyncedObjectEnabled +This parameter is available only in on-premises Exchange. + +The ACLableSyncedObjectEnabled parameter specifies whether remote mailboxes in hybrid environments are stamped as ACLableSyncedMailboxUser. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActionableMessagesExtenalAccessTokenEnabled +This parameter is available only in the cloud-based service. + +{{ Fill ActionableMessagesExtenalAccessTokenEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActivityBasedAuthenticationTimeoutEnabled +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. +- $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled. + +If you're using single sign-on, use the ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActivityBasedAuthenticationTimeoutInterval +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. + +Valid values for this parameter are from 00:05:00 to 08:00:00 (5 minutes to 8 hours). The default value is 06:00:00 (6 hours). + +The value of this parameter is meaningful only if the ActivityBasedAuthenticationTimeoutEnabled or ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter value is $true. + +For more information about the activity-based timeout in Outlook on the web, see [Description of the Activity-Based Authentication Timeout for OWA in Office 365](https://support.microsoft.com/topic/0c101e1b-020e-69c1-a0b0-26532d60c0a4). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled +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. +- $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled for single sign-on. + +If you aren't using single sign-on, use the ActivityBasedAuthenticationTimeoutEnabled 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdfsAudienceUris +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. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +For more information about configuring AD FS claims based authentication in Exchange, see [Use AD FS claims-based authentication with Outlook on the web](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/ad-fs-claims-based-auth). + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdfsAuthenticationParameter +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdfsAuthenticationConfiguration +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdfsEncryptCertificateThumbprint +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: AdfsAuthenticationParameter +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdfsIssuer +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. + +To get this value, open Windows PowerShell on the AD FS server and run the command Get-ADFSEndpoint -AddressPath /adfs/ls | Format-List FullUrl. + +```yaml +Type: Uri +Parameter Sets: AdfsAuthenticationParameter +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdfsSignCertificateThumbprints +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. + +To get the thumbprint values of the primary and secondary token-signing certificates, open Windows PowerShell on the AD FS server and run the command Get-ADFSCertificate -CertificateType "Token-signing". For more information, see [Get-ADFSCertificate](https://learn.microsoft.com/powershell/module/adfs/get-adfscertificate). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdfsAuthenticationParameter +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppsForOfficeEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AsyncSendEnabled +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. +- $false: Async send is disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuditDisabled +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: + +- $true: Mailbox auditing is disabled for the organization. +- $false: Allow mailbox auditing in the organization. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutodiscoverPartialDirSync +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. + +After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours to fully saturate across the cloud. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoEnableArchiveMailbox +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: + +- $true: An archive mailbox is automatically provisioned. +- $false: An archive mailbox isn't automatically provisioned. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoExpandingArchive +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. + +After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. Note that a user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled. + +```yaml +Type: SwitchParameter +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutomaticForcedReadReceiptEnabled +This parameter is available only in the cloud-based service. + +{{ Fill AutomaticForcedReadReceiptEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockMoveMessagesForGroupFolders +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: + +- $true: Group owners or group members can't move messages between folders in Microsoft 365 groups (manually or vial Inbox rules). +- $false: Group owners or group members can move messages between folders in Microsoft 365 groups. This is the default value. + +The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true. + +Whether group members (not just group owners) are allowed to move messages between folders in Microsoft 365 Groups also depends on the following settings: + +- The value of the IsGroupMemberAllowedToEditContent parameter is $true. +- The group owner selected **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** in the properties of the group in Outlook on the web. + +For more information, see [Manage Folders and Rules feature in Microsoft 365 Groups](https://learn.microsoft.com/microsoft-365/enterprise/manage-folders-and-rules-feature). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsAddressEntryRestricted +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: + +- $true: Addresses can't be collected from Bookings customers. +- $false: Addresses can be collected from Bookings customers. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsAuthEnabled +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: + +- $true: All new and existing Bookings pages are forced to authenticate users before they can book the appointment. +- $false: All bookings pages are not forced to authenticate users. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsBlockedWordsEnabled +This parameter is available only in the cloud-based service. + +{{ Fill BookingsBlockedWordsEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsCreationOfCustomQuestionsRestricted +This parameter is available only in the cloud-based service. + +The BookingsCreationOfCustomQuestionsRestricted parameter specifies whether Bookings admins can add custom questions. Valid values are: + +- $true: Bookings admins can't add custom questions. +- $false: Bookings admins can add custom questions. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsEnabled +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: + +- $true: Bookings is enabled. +- $false: Bookings is disabled. This is the default value. + +Microsoft Bookings is an online and mobile app for small businesses who provide appointment services to customers. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsExposureOfStaffDetailsRestricted +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: + +- $true: Internal Bookings staff member attributes aren't visible to external Bookings customers. +- $false: Internal Bookings staff member attributes are visible to external Bookings customers. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsMembershipApprovalRequired +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: + +- $true: Newly added staff members need to accept membership in Bookings calendars before the resources are bookable. +- $false: Newly added staff members do not need to accept membership in Bookings calendars to make the resources bookable. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsNamingPolicyEnabled +This parameter is available only in the cloud-based service. + +{{ Fill BookingsNamingPolicyEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsNamingPolicyPrefix +This parameter is available only in the cloud-based service. + +{{ Fill BookingsNamingPolicyPrefix Description }} + +```yaml +Type: String +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsNamingPolicyPrefixEnabled +This parameter is available only in the cloud-based service. + +{{ Fill BookingsNamingPolicyPrefixEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsNamingPolicySuffix +This parameter is available only in the cloud-based service. + +{{ Fill BookingsNamingPolicySuffix Description }} + +```yaml +Type: String +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsNamingPolicySuffixEnabled +This parameter is available only in the cloud-based service. + +{{ Fill BookingsNamingPolicySuffixEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsNotesEntryRestricted +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: + +- $true: Appointment notes can't be collected from Bookings customers. +- $false: Appointment notes can be collected from Bookings customers. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsPaymentsEnabled +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: + +- $true: Online payments are enabled. +- $false: Online payments are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsPhoneNumberEntryRestricted +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: + +- $true: Appointment notes can't be collected from Bookings customers. +- $false: Appointment notes can be collected from Bookings customers. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsSearchEngineIndexDisabled +This parameter is available only in the cloud-based service. + +{{ Fill BookingsSearchEngineIndexDisabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsSmsMicrosoftEnabled +This parameter is available only in the cloud-based service. + +{{ Fill BookingsSmsMicrosoftEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsSocialSharingRestricted +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: + +- $true: Social sharing options are restricted. +- $false: Users can see social sharing options inside Bookings. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ByteEncoderTypeFor7BitCharsets +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. +- 1: Always use QP (quoted-printable) encoding for HTML and plain text. +- 2: Always use Base64 encoding for HTML and plain text. +- 5: Use QP encoding for HTML and plain text unless line wrapping is enabled in plain text. If line wrapping is enabled, use 7-bit encoding for plain text. +- 6: Use Base64 encoding for HTML and plain text, unless line wrapping is enabled in plain text. If line wrapping is enabled in plain text, use Base64 encoding for HTML, and use 7-bit encoding for plain text. +- 13: Always use QP encoding for HTML. Always use 7-bit encoding for plain text. +- 14: Always use Base64 encoding for HTML. Always use 7-bit encoding for plain text. + +If no value is specified, Exchange always uses QP encoding for HTML and plain text. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CalendarVersionStoreEnabled +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceMLBgdCrawlEnabled +This parameter is available only in the cloud-based service. + +{{ Fill ComplianceMLBgdCrawlEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorsActionableMessagesEnabled +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. +- $false: Action buttons in connector cards are disabled. + +For more information about actionable messages in connected apps, see [Connect apps to your inbox in Outlook on the web](https://support.microsoft.com/office/3d41b99c-bf8d-47d4-bc7a-97758b74689d). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorsEnabled +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. +- $false: Connectors are disabled. + +The workloads that are affected by this parameter are Outlook, SharePoint, Teams, and Viva Engage. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorsEnabledForOutlook +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: + +- $true: Connectors are enabled. This is the default value. +- $false: Connectors are disabled. + +To enable and disable the ability to use connectors on specific Microsoft 365 Groups, set the value of this parameter to $true, and then use the ConnectorsEnabled switch on the Set-UnifiedGroup cmdlet. + +For more information about connectors for Outlook on the web, see [Connect apps to your inbox in Outlook on the web](https://support.microsoft.com/office/3d41b99c-bf8d-47d4-bc7a-97758b74689d). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorsEnabledForSharepoint +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: + +- $true: Connectors are enabled. This is the default value. +- $false: Connectors are disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorsEnabledForTeams +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: + +- $true: Connectors are enabled. This is the default value. +- $false: Connectors are disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorsEnabledForYammer +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: + +- $true: Connectors are enabled. This is the default value. +- $false: Connectors are disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomerFeedbackEnabled +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomerLockboxEnabled +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DataClassifications +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultAuthenticationPolicy +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 +- Distinguished name (DN) +- GUID + +To remove the default policy assignment for the organization, use the value $null. + +You create authentication policies with the New-AuthenticationPolicy cmdlet to block or selectively allow Basic authentication or (in Exchange 2019 CU2 or later) other legacy authentication methods. + +```yaml +Type: AuthPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultGroupAccessType +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: + +- Public +- Private (this is the default value) + +```yaml +Type: ModernGroupObjectType +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: Private +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultMinutesToReduceLongEventsBy +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. + +To use this parameter, you also need to include the ShortenEventScopeDefault parameter. + +Whether long events start late or end early by the specified number of minutes depends on the value of the ShortenEventScopeDefault parameter (EndEarly or StartLate). + +```yaml +Type: Int32 +Parameter Sets: ShortenEventScopeParameter +Aliases: +Applicable: Exchange Online +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultMinutesToReduceShortEventsBy +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. + +To use this parameter, you also need to include the ShortenEventScopeDefault parameter. + +Whether short events start late or end early by the specified number of minutes depends on the value of the ShortenEventScopeDefault parameter (EndEarly or StartLate). + +```yaml +Type: Int32 +Parameter Sets: ShortenEventScopeParameter +Aliases: +Applicable: Exchange Online +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultPublicFolderAgeLimit +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). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultPublicFolderDeletedItemRetention +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultPublicFolderIssueWarningQuota +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +The valid input range for this parameter is from 0 through 2199023254529 bytes(2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultPublicFolderMaxItemSize +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultPublicFolderMovedItemRetention +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). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultPublicFolderProhibitPostQuota +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DelayedDelicensingEnabled +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: + +- $true: Exchange Online license removals from mailboxes are delayed by 30 days. Admins can use the delay to identify potential mistakes and avoid disruptions for affected users. +- $false: Exchange Online license removals from mailboxes aren't delayed. This is the default value. + +Use the TenantAdminNotificationForDelayedDelicensingEnabled parameter to turn on weekly Service Health advisory notifications for admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health). + +Use the EndUserMailNotificationForDelayedDelicensingEnabled to send affected users periodic email notifications that they're going to lose access to their mailbox. + +Use the Get-PendingDelicenseUser cmdlet to view mailboxes with pending mailbox license removal requests. + +Use the Expedite-Delicensing cmdlet to end the delay for removing the Exchange Online license from the mailbox. + +When you set the value of the DelayedDelicensingEnabled parameter to $true, the TenantAdminNotificationForDelayedDelicensingEnabled and EndUserMailNotificationForDelayedDelicensingEnabled parameters are set to $true by default. + +When you set the value of the DelayedDelicensingEnabled parameter to $false, the TenantAdminNotificationForDelayedDelicensingEnabled and EndUserMailNotificationForDelayedDelicensingEnabled parameters are set to $false by default. + +```yaml +Type: Boolean +Parameter Sets: DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DirectReportsGroupAutoCreationEnabled +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: + +- $true: The automatic creation of direct report Microsoft 365 Groups is enabled. +- $false: The automatic creation of direct report Microsoft 365 Groups is disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisablePlusAddressInRecipients +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: + +- $true: Plus addressing is disabled. You can no longer use the plus sign in regular email addresses. The plus sign is available only for plus addressing. +- $false: Plus addressing is enabled. You can use the plus sign in regular email addresses. + +For more information about plus addressing, see [Plus addressing in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/plus-addressing-in-exchange-online). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DistributionGroupDefaultOU +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DistributionGroupNameBlockedWordsList +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DistributionGroupNamingPolicy +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. + +You can use the following user attributes. The actual values are determined by the user who creates the group: + +- `` +- `` +- `` +- `` +- `` to `` +- `` +- `` to `` +- `` +- `` +- `` + +For example: `"DL_<StateOrProvince>_<GroupName>"`, `"<StateOrProvince>-<City>-<Office>-<GroupName>"` or `"<GroupName> <CustomAttribute1>"`. + +```yaml +Type: DistributionGroupNamingPolicy +Parameter Sets: (All) +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 +``` + +### -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. + +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ElcProcessingDisabled +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: + +- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. Note that this setting will be ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox. +- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmptyAddressBookForNonExchangeUsers +This parameter is available only in on-premises Exchange. + +{{ Fill EmptyAddressBookForNonExchangeUsers Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableAuthAdminReadSession +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. + +```yaml +Type: SwitchParameter +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableDownloadDomains +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: + +- $true: Outlook on the web uses a different download domain for inline images (for example, downloads.contoso.com). Before you enable this setting, you need to create a CNAME record and certificate for this domain, and add the domain to the ExternalDownloadHostName and InternalDownloadHostName parameters on the Set-OwaVirtualDirectory cmdlet. +- $false: The setting is disabled. This is the default value. + +For more information about the security vulnerability that's addressed by this parameter, and for detailed configuration instructions, see [CVE 2021 1730](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-1730). + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableForwardingAddressSyncForMailboxes +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOrgWidePermissionOnScopedRoles +This parameter is available only in on-premises Exchange. + +{{ Fill EnableOrgWidePermissionOnScopedRoles Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOutlookEvents +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: + +- $true: Discovery of events from email messages is enabled. +- $false: Discovery of events from email messages is disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserDLUpgradeFlowsDisabled +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: + +- $true: Users can upgrade distribution groups that they own to Microsoft 365 Groups. +- $false: Users can't upgrade distribution groups that they own to Microsoft 365 Groups. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserMailNotificationForDelayedDelicensingEnabled +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: + +- $true: Affected users receive periodic email notifications about losing access to their mailbox starting ~18 days after the Exchange Online license was removed. +- $false: Affected users don't receive periodic email notifications about losing access to their mailbox. This is the default value. + +The value of this parameter is meaningful on when the value of the DelayedDelicensingEnabled parameter is $true. + +Use the TenantAdminNotificationForDelayedDelicensingEnabled parameter to turn on weekly Service Health advisory notifications for admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health). + +```yaml +Type: Boolean +Parameter Sets: DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowEntourage +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowList +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +**Note**: If users receive an error when they try to run "Play My Emails" in Outlook Mobile, use this parameter to add the value "Cortana" to the list of allowed applications. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowMacOutlook +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsAllowOutlook +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsApplicationAccessPolicy +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. +- EnforceBlockList: All applications are allowed to access EWS and REST, except for the applications specified by the EwsBlockList parameter. + +Note that if the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsBlockList +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EwsEnabled +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. +- $false: All EWS access is disabled. +- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This is the default value. + +This parameter has no affect on access to REST. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeNotificationEnabled +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. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeNotificationRecipients +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FindTimeAttendeeAuthenticationEnabled +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: + +- $true: Attendees are required to validate their identity and the meeting organizer can't turn off this setting (Always On). +- $false: By default, attendees are required to verify their identity, but the meeting organizer is allowed to turn this setting off. + +This setting overrides individual user settings. + +For more information about FindTime, see [How to create a FindTime poll](https://support.microsoft.com/office/4dc806ed-fde3-4ea7-8c5e-b5d1fddab4a6). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FindTimeAutoScheduleDisabled +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: + +- $true: Reaching a consensus for the meeting time doesn't automatically schedule the meeting, and the meeting organizer can't change this setting (Off). +- $false: By default, reaching a consensus for the meeting time doesn't automatically schedule the meeting, but meeting organizer is allowed to turn on this setting. + +This setting overrides individual user settings. + +For more information about FindTime, see [How to create a FindTime poll](https://support.microsoft.com/office/4dc806ed-fde3-4ea7-8c5e-b5d1fddab4a6). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FindTimeLockPollForAttendeesEnabled +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: + +- $true: **Lock poll for attendees** is on. Attendees will not be able to suggest new times or edit other attendees. The meeting organizer can't turn off this setting (always on). +- $false: By default, **Lock poll for attendees** is off (initial default) or on (the user saved settings from last poll), but the meeting organizer is allowed to turn the setting off or on to allow or prevent attendees from suggesting new times or editing attendees. + +This setting overrides individual user settings. + +For more information about FindTime, see [How to create a FindTime poll](https://support.microsoft.com/office/4dc806ed-fde3-4ea7-8c5e-b5d1fddab4a6). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FindTimeOnlineMeetingOptionDisabled +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: + +- $true: The **Online meeting** checkbox is not available in the meeting poll in FindTime, and the meeting organizer can't change this setting. If your organization uses a third-party online meeting provider, the meeting organizer can make the meeting online using the third-party provider while creating the meeting based on the FindTime poll results. +- $false: The **Online meeting** checkbox is available in the meeting poll in FindTime, so the meeting organizer can choose to select or not select this setting. + +This setting overrides individual user settings. + +For more information about FindTime, see [How to create a FindTime poll](https://support.microsoft.com/office/4dc806ed-fde3-4ea7-8c5e-b5d1fddab4a6). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FocusedInboxOn +This parameter is available only in the cloud-based service. + +The FocusedInboxOn parameter enables or disables Focused Inbox for the organization. Valid values are: + +- $true: Focused Inbox is enabled. +- $false: Focused Inbox is disabled. + +To disable Focused Inbox on specific mailboxes, enable Focused Inbox for the organization, and then use the Set-FocusedInbox cmdlet. + +Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HierarchicalAddressBookRoot +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +Setting a value for this parameter enables the hierarchical address book to be automatically displayed in Outlook for the organization. + +The default value is blank. To reset this parameter, use the value $null. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HybridRSVPEnabled +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: + +- $true: Hybrid RSVP is enabled (this is the default value). +- $false: Hybrid RSVP is disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Industry +This parameter is available only in on-premises Exchange. + +The Industry parameter specifies the industry that best represents your organization. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPListBlocked +This parameter is available only in the cloud-based service. + +This parameter only affects Basic authentication connections. + +The IPListBlocked parameter specifies the blocked IP addresses that aren't allowed to connect to Exchange Online organization. Valid values are: + +- Single IP address: For example, 192.168.1.1 or fe80::39bd:88f7:6969:d223%11. +- IP address range: For example, 192.168.0.1-192.168.0.254 or 192.168.8.2(255.255.255.0). +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.3.1/24 or 2001:0DB8::CD3/60. + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +This parameter has a limit of approximately 1200 entries. + +Changes to this parameter might take up to 4 hours to fully propagate across the service. + +```yaml +Type: MultiValuedProperty +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsAgendaMailEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsExcludedFromOffboardMigration +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. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsExcludedFromOnboardMigration +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. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsFfoMigrationInProgress +This parameter is available only in on-premises Exchange. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsGroupFoldersAndRulesEnabled +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: + +- $true: Group owners can create folders and move messages between folders in Microsoft 365 Groups. +- $false: Group owners can't create folders or move messages between folders in Microsoft 365 Groups. This is the default value. + +To allow group owners to allow group users to create folders and moved messages in Microsoft 365 Groups, use the IsGroupMemberAllowedToEditContent parameter. + +For more information, see [Manage Folders and Rules feature in Microsoft 365 Groups](https://learn.microsoft.com/microsoft-365/enterprise/manage-folders-and-rules-feature). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsGroupMemberAllowedToEditContent +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: + +- $true: Group owners can use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to do the following tasks in Microsoft 365 Groups: + + • Create, rename, move, copy, and delete folders. + + • Move, copy, and delete messages manually or via Inbox rules. + + • Create, edit, copy, and delete Inbox rules. + +- $false: Group owners can't use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to manage folders and messages in Microsoft 365 Groups. Only group owners can manage folders and messages in Microsoft 365 Groups. This is the default value. + +The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true. + +To prevent group owners or group members from moving messages between folders manually or vial Inbox rules in Microsoft 365 Groups, use the BlockMoveMessagesForGroupFolders parameter. + +For more information, see [Manage Folders and Rules feature in Microsoft 365 Groups](https://learn.microsoft.com/microsoft-365/enterprise/manage-folders-and-rules-feature). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LeanPopoutEnabled +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. +- $false: Lean pop-outs are disabled. This is the default value. + +**Notes**: + +- Lean pop-outs aren't available for messages that contain attachments or information rights management (IRM) restrictions. +- Outlook add-ins and Skype for Business Online presence aren't available with lean pop-outs. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LinkPreviewEnabled +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. +- $false: Link preview of URLs in email messages is not allowed. Users can't enable link preview in their Outlook on the web settings. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxDataEncryptionEnabled +This parameter is available only in on-premises Exchange. + +{{ Fill MailboxDataEncryptionEnabled Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTipsAllTipsEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTipsExternalRecipientsTipsEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTipsGroupMetricsEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTipsLargeAudienceThreshold +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTipsMailboxSourcedTipsEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedFolderHomepage +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MapiHttpEnabled +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: + +- $true: Access to mailboxes by using MAPI over HTTP is enabled. This is the default value. +- $false: Access to mailboxes by using MAPI over HTTP is disabled. + +You can use the MapiHttpEnabled parameter on the Set-CASMailbox cmdlet to override the global MAPI over HTTP settings for individual users. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaskClientIpInReceivedHeadersEnabled +This parameter is available only in the cloud-based service. + +{{ Fill MaskClientIpInReceivedHeadersEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MatchSenderOrganizerProperties +This parameter is available only in the cloud-based service. + +{{ Fill MatchSenderOrganizerProperties Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxConcurrentMigrations +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. + +```yaml +Type: Unlimited +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageHighlightsEnabled +This parameter is available only in the cloud-based service. + +{{ Fill MessageHighlightsEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageRecallAlertRecipientsEnabled +This parameter is available only in the cloud-based service. + +{{ Fill MessageRecallAlertRecipientsEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageRecallAlertRecipientsReadMessagesOnlyEnabled +This parameter is available only in the cloud-based service. + +{{ Fill MessageRecallAlertRecipientsReadMessagesOnlyEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageRecallEnabled +This parameter is available only in the cloud-based service. + +{{ Fill MessageRecallEnabled Description }} + +```yaml +Type: System.Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageRecallMaxRecallableAge +{{ Fill MessageRecallMaxRecallableAge Description }} + +```yaml +Type: Microsoft.Exchange.Data.EnhancedTimeSpan +Parameter Sets: ShortenEventScopeParameter +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageRemindersEnabled +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: + +- $true: Message reminders are enabled. A message is moved to the top of the user's inbox if Outlook determines that the message requires follow-up or a reply. Only one message is moved at a time, and the user must take action on the message before another message is moved to the top of the Inbox. +- $false: Message reminders are disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MicrosoftExchangeRecipientEmailAddresses +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. + +Email addresses that you specify by using the MicrosoftExchangeRecipientEmailAddresses parameter replace any existing email addresses already configured. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MicrosoftExchangeRecipientEmailAddressPolicyEnabled +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. + +If you change the value of the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter from $false to $true, any email addresses that you defined by using the MicrosoftExchangeRecipientEmailAddresses parameter are preserved. However, the value of the MicrosoftExchangeRecipientPrimarySmtpAddress parameter reverts to `MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@<Accepted Domain in Highest Priority Email Address Policy>`. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MicrosoftExchangeRecipientPrimarySmtpAddress +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. + +If you modify the value of the MicrosoftExchangeRecipientPrimarySmtpAddress parameter, the value is automatically added to the list of email addresses defined in the MicrosoftExchangeRecipientEmailAddresses parameter. + +The MicrosoftExchangeRecipientPrimarySmtpAddress parameter is meaningful only if the Exchange recipient has more than one defined SMTP email address. If the MicrosoftExchangeRecipientEmailAddresses parameter has only one defined SMTP email address, the value of the MicrosoftExchangeRecipientPrimarySmtpAddress parameter and the MicrosoftExchangeRecipientEmailAddresses parameter are the same. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MicrosoftExchangeRecipientReplyRecipient +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MitigationsEnabled +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: + +- $true: The EM Service automatically applies mitigations on Exchange servers where the value of the _MitigationsEnabled_ parameter is $true on the **Set-ExchangeServer**. +- $false: Mitigations are not automatically applied on Exchange servers. + +For more information, see [Exchange Emergency Mitigation (EM) service](https://learn.microsoft.com/exchange/exchange-emergency-mitigation-service). + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MobileAppEducationEnabled +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: + +- $true: Outlook on the web and Outlook desktop will show the education reminder to users who aren't using Outlook for iOS and Android to check their company email and calendar events. This is the default value. +- $false: The Outlook for iOS and Android education reminder is disabled. + +This setting will affect Outlook desktop at some point in the future. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OabShadowDistributionOldestFileAgeLimit +This parameter is available only in on-premises Exchange. + +{{ Fill OabShadowDistributionOldestFileAgeLimit Description }} + +```yaml +Type: EnhancedTimeSpan +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OAuth2ClientProfileEnabled +The OAuth2ClientProfileEnabled parameter enables or disables modern authentication in the Exchange organization. Valid values are: + +- $true: modern authentication is enabled. +- $false: modern authentication is disabled. + +modern authentication is based on the Active Directory Authentication Library (ADAL) and OAuth 2.0, and enables authentication features like multi-factor authentication (MFA), certificate-based authentication (CBA), and third-party SAML identity providers. + +When you enable modern authentication in Exchange Online, we recommend that you also enable it in Skype for Business Online. For more information, see [Skype for Business Online: Enable your tenant for modern authentication](https://aka.ms/SkypeModernAuth). + +```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 +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlineMeetingsByDefaultEnabled +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: + +- $true: All meetings are online by default. +- $false: All meetings are not online by default. +- $null: If the organization value has not been specified, the default behavior is for meetings to be online. + +If a user has already directly interacted with this setting in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA), the value of this parameter is ignored. Eventually, this parameter will override the Outlook-configured setting. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationSummary +This parameter is available only in on-premises Exchange. + +The OrganizationSummary parameter specifies a summarized description that best represents your organization. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookGifPickerDisabled +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: + +- $true: GIF Search in Outlook on the web is disabled. +- $false: GIF Search in Outlook on the web is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookMobileGCCRestrictionsEnabled +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: + +- $true: Disable features that aren't FedRAMP compliant for GCC customers. This is the default value for all GCC customers. +- $false: Enable features that aren't FedRAMP compliant for GCC customers. + +The Outlook for iOS and Android feature and services that are not FedRAMP compliant for Microsoft 365 US Government customers include: + +- Multi-account support +- Third-party services +- HelpShift and in-app support +- Any Microsoft services that are outside the Microsoft 365 US Government Community Cloud (for example, Bing and Cortana). + + For a full list of Features and services that are not FedRAMP compliant for GCC customers, see [Services and features of Outlook for iOS and Android that aren't available for Government Community Cloud users](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/outlook-for-ios-and-android-in-the-government-cloud#services-and-features-not-available). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookMobileHelpShiftEnabled +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookMobileSingleAccountEnabled +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookPayEnabled +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: + +- $true: Payments in Outlook are enabled. +- $False: Payments in Outlook are disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookTextPredictionDisabled +This parameter is available only in the cloud-based service. + +{{ Fill OutlookTextPredictionDisabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermanentlyDeleteDisabled +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: + +- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing policies, block the creation of policies with the PermanentlyDelete action or notify users that thePermanentlyDelete action won't actually take effect. +- $false The PermanentlyDelete retention action is enabled. This is the default value. + +A message that's permanently deleted can't be recovered by using the Recoverable Items folder. Additionally, permanently deleted messages aren't returned by a Discovery search, unless litigation hold or single item recovery is enabled for the mailbox. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PerTenantSwitchToESTSEnabled +This parameter is available only in the cloud-based service. + +This parameter has been deprecated and is no longer used. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostponeRoamingSignaturesUntilLater +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: + +- $true: Roaming signatures are disabled for Outlook on the web and the new Outlook for Windows. For Windows clients, the registry setting to disable roaming signatures still works. For more information, see [Outlook roaming signatures](https://support.microsoft.com/office/420c2995-1f57-4291-9004-8f6f97c54d15). When roaming signatures are disabled, admins can use the signature-related parameters on the Set-MailboxMessageConfiguration cmdlet (for example, AutoAddSignature, AutoAddSignatureOnReply, and SignatureHtml) to configure email signatures. + + Previously, the only way to disable roaming signatures in Outlook on the web was to open a support ticket. With the introduction of this parameter and value, admins can disable roaming signatures themselves. + +- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This is the default value. + +We recommend that independent software vendors (ISVs) onboard to the [signature API](https://learn.microsoft.com/javascript/api/outlook/office.body#outlook-office-body-setsignatureasync-member(1)) based on [event-based hooks +](https://learn.microsoft.com/office/dev/add-ins/outlook/autolaunch). + +We have no plans to support roaming signature management in the Microsoft Graph API. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreferredInternetCodePageForShiftJis +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicComputersDetectionEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderContentReplicationDisabled +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. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderMailboxesLockedForNewConnections +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: + +- $true: Users aren't allowed to make new connections to public folder mailboxes. You use this setting during the final stages of public folder migrations. +- $false: Users are allowed to make new connections to public folder mailboxes. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderMailboxesMigrationComplete +This parameter is available only in on-premises Exchange. + +The PublicFolderMailboxesMigrationComplete parameter is used during public folder migration. + +- $true: Queued messages are rerouted to the new destination. +- $false (This is the default value) + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderMigrationComplete +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. + +```yaml +Type: Boolean +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFoldersEnabled +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. +- Remote: The public folders are deployed in the remote forest. +- None: No public folders are deployed for this organization. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFolderShowClientControl +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). +- $false: This is the default value. User access to public folders in Outlook is enabled (the control access feature is disabled). The value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is meaningless. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFoldersLockedForMigration +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadTrackingEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecallReadMessagesEnabled +This parameter is available only in the cloud-based service. + +{{ Fill RecallReadMessagesEnabled Description }} + +```yaml +Type: System.Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RefreshSessionEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RejectDirectSend +This parameter is available only in the cloud-based service. + +{{ Fill RejectDirectSend Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemotePublicFolderMailboxes +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredCharsetCoverage +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SCLJunkThreshold +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendFromAliasEnabled +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: + +- $true: Aliases on messages will no longer be rewritten to their primary SMTP addresses. Compatible Outlook clients will allow sending from aliases and replying to aliases. Even without an updated Outlook client, users might see changes in behavior because the setting affects all messages sent and received by a mailbox. +- $false: Aliases on messages sent or received will be rewritten to their primary email address. This is the default value. + +For more information about the availability of the feature in Outlook on the web, see the [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Exchange&searchterms=59437). For Outlook for Windows, see this [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Outlook&searchterms=64123). + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharedDomainEmailAddressFlowEnabled +This parameter is available only in the cloud-based service. + +{{ Fill SharedDomainEmailAddressFlowEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteMailboxCreationURL +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SmtpActionableMessagesEnabled +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. +- $false: Action buttons in email messages are disabled. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantAdminNotificationForDelayedDelicensingEnabled +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: + +- $true: Weekly Service Health advisory notifications are sent to admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. +- $false: Disable weekly Service Health advisory notifications about the number of Exchange Online delicensed users. This is the default value. + +For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health). + +The value of this parameter is meaningful on when the value of the DelayedDelicensingEnabled parameter is $true. + +Use the EndUserMailNotificationForDelayedDelicensingEnabled to send affected users periodic email notifications that they're going to lose access to their mailbox. + +```yaml +Type: Boolean +Parameter Sets: DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TwoClickMailPreviewEnabled +This parameter is available only in the cloud-based service. + +{{ Fill TwoClickMailPreviewEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UMAvailableLanguages +This parameter is available only in on-premises Exchange. + +This parameter has been deprecated and is no longer used. + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnblockUnsafeSenderPromptEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseIcsSyncStateStreaming +This parameter is available only in on-premises Exchange. + +{{ Fill UseIcsSyncStateStreaming Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VisibleMeetingUpdateProperties +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. + +This parameter uses the syntax: `"MeetingProperty1:MeetingStartTimeWithinXMinutes1,MeetingProperty2:MeetingStartTimeWithinXMinutes2,...MeetingPropertyN:MeetingStartTimeWithinXMinutesN"`. + +The valid meeting properties to monitor for updates are: + +- Location: The meeting location field. +- Subject: The meeting subject or title. +- Sensitivity: The sensitivity (privacy) of the event. +- Body: The meeting body or description. +- OnlineMeetingLinks: The meeting join URL. +- AllowForwarding: The option to allow or prevent forwarding of meetings. +- RequestResponses: The option on whether responses are requested. +- AllowNewTimeProposals: The option to allow or prevent new time proposals. +- ShowAs: The free/busy state of the meeting: Free, Tentative, Busy, Working elsewhere, or Away/Out of office. +- Reminder: The reminder time. +- AllProperties: Any meeting change. + +If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property will result in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series. + +The default value is `"Location,AllProperties:15"`: changes to the meeting location at any time, or changes to other meeting properties within 15 minutes of the meeting start time results in visible meeting update messages. + +In the following scenarios, meeting update messages are not auto-processed, regardless of the values specified in this parameter. In these scenarios, attendees will always see meeting update messages in their Inbox: + +- The update contains a change to the meeting date, time, or recurrence pattern. +- The meeting message is received for a delegated shared calendar. +- The receiving attendee is @ mentioned in the meeting body. +- The attendee has not yet responded to the meeting. + +```yaml +Type: String +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WACDiscoveryEndpoint +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`. + +Office Online Server enables users to view supported file attachments in Outlook on the web (formerly known as Outlook Web App). + +```yaml +Type: String +Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebPushNotificationsDisabled +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: + +- $true: Web Push Notifications are disabled. +- $false: Web Push Notifications are enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebSuggestedRepliesDisabled +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: + +- $true: Suggested Replies are disabled. +- $false: Suggested Replies are enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WorkspaceTenantEnabled +This parameter is available only in the cloud-based service. + +The WorkspaceTenantEnabled parameter enables or disables workspace booking in the organization. Valid values are: + +- $true: In Outlook for iOS and Android, the calendar setting for workspace booking is visible and is off by default. +- $false: In Outlook for iOS and Android, the calendar setting for workspace booking is hidden. + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/sharing-and-collaboration/Set-OrganizationRelationship.md b/exchange/exchange-ps/exchange/Set-OrganizationRelationship.md similarity index 77% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Set-OrganizationRelationship.md rename to exchange/exchange-ps/exchange/Set-OrganizationRelationship.md index 6b445ad946..f21e2920e4 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-OrganizationRelationship.md +++ b/exchange/exchange-ps/exchange/Set-OrganizationRelationship.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-organizationrelationship -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-OrganizationRelationship @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-OrganizationRelationship cmdlet to modify existing organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,22 +32,26 @@ Set-OrganizationRelationship [-Identity] <OrganizationRelationshipIdParameter> [-FreeBusyAccessEnabled <Boolean>] [-FreeBusyAccessLevel <FreeBusyAccessLevel>] [-FreeBusyAccessScope <GroupIdParameter>] + [-MailboxMoveCapability <MailboxMoveCapability>] [-MailboxMoveEnabled <Boolean>] + [-MailboxMovePublishedScopes <MultiValuedProperty>] [-MailTipsAccessEnabled <Boolean>] [-MailTipsAccessLevel <MailTipsAccessLevel>] [-MailTipsAccessScope <GroupIdParameter>] [-Name <String>] + [-OAuthApplicationId <String>] [-OrganizationContact <SmtpAddress>] [-PhotosEnabled <Boolean>] [-TargetApplicationUri <Uri>] [-TargetAutodiscoverEpr <Uri>] [-TargetOwaURL <Uri>] [-TargetSharingEpr <Uri>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,16 +75,14 @@ This example disables the organization relationship with Contoso 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 - - Canonical name - - GUID ```yaml Type: OrganizationRelationshipIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -94,14 +95,13 @@ Accept wildcard characters: False 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. - - $false: The external organization doesn't provide remote access to mailbox archives. This is the default value ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -113,15 +113,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -134,7 +133,6 @@ Accept wildcard characters: False 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. - - $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction. @@ -143,7 +141,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -177,7 +175,7 @@ The DomainNames parameter specifies the SMTP domains of the external organizatio Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -190,14 +188,13 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable the organization relationship. Valid values are: - $true: The organization relationship is enabled. This is the default value. - - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -207,13 +204,15 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -226,7 +225,6 @@ Accept wildcard characters: False 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. - - $false: Free/busy information isn't retrieved from the external organization. This is the default value. You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters. @@ -235,7 +233,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -248,9 +246,7 @@ Accept wildcard characters: False The FreeBusyAccessLevel parameter specifies the maximum amount of detail returned to the requesting organization. Valid values are: - None: No free/busy access. - - AvailabilityOnly: Free/busy access with time only. - - LimitedDetails: Free/busy access with time, subject, and location. This parameter is only meaningful when the FreeBusyAccessEnabled parameter value is $true. @@ -259,7 +255,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -272,11 +268,8 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - Canonical DN - - GUID This parameter is only meaningful when the FreeBusyAccessEnabled parameter value is $true. @@ -285,7 +278,32 @@ 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 +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxMoveCapability +This parameter is available only in the cloud-based service. + +The MailboxMoveCapability parameter is used in cross-tenant mailbox migrations. Valid values are: + +- Inbound +- Outbound +- RemoteInbound +- RemoteOutbound + +For more information, see [Cross-tenant mailbox migration](https://learn.microsoft.com/microsoft-365/enterprise/cross-tenant-mailbox-migration). + +```yaml +Type: MailboxMoveCapability +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -298,14 +316,42 @@ Accept wildcard characters: False 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. - - $false: Mailbox moves to from the external organization aren't allowed. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxMovePublishedScopes +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: + +- Name +- Distinguished name (DN) +- Canonical DN +- GUID + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +For more information, see [Cross-tenant mailbox migration](https://learn.microsoft.com/microsoft-365/enterprise/cross-tenant-mailbox-migration). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -318,7 +364,6 @@ Accept wildcard characters: False 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. - - $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value. You control the MailTips access level by using the MailTipsAccessLevel parameter. @@ -327,7 +372,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -340,9 +385,7 @@ Accept wildcard characters: False 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. - - Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned. - - None: No MailTips are returned to the remote organization. This is the default value. This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true. @@ -351,7 +394,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -364,11 +407,8 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - Canonical DN - - GUID The default value is blank ($null), which means no group is specified. @@ -376,9 +416,7 @@ The default value is blank ($null), which means no group is specified. If you use this parameter, recipient-specific MailTips are returned only for those recipients that are members of the specified group. The recipient-specific MailTips are: - Auto Reply - - Mailbox Full - - Custom If you don't use this parameter, recipient-specific MailTips are returned for all recipients in the organization. @@ -389,7 +427,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -405,7 +443,25 @@ The Name parameter specifies the unique name of the organization relationship. T Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OAuthApplicationId +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -421,7 +477,7 @@ The OrganizationContact parameter specifies the email address that can be used t Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -434,14 +490,13 @@ Accept wildcard characters: False 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. - - $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -457,7 +512,7 @@ The TargetApplicationUri parameter specifies the target Uniform Resource Identif Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -467,13 +522,13 @@ Accept wildcard characters: False ``` ### -TargetAutodiscoverEpr -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 Exchangeserver endpoint to use for external requests. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -489,7 +544,7 @@ The TargetOwaURL parameter specifies the Outlook on the web (formerly Outlook We Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -507,7 +562,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -523,7 +578,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -537,12 +592,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-OrganizationSegment.md b/exchange/exchange-ps/exchange/Set-OrganizationSegment.md new file mode 100644 index 0000000000..49cf493921 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-OrganizationSegment.md @@ -0,0 +1,103 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-OrganizationSegment + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-OrganizationSegment cmdlet to modify organization segments in the Microsoft Purview compliance portal. Organization Segments are not in effect until you [apply information barrier policies](https://learn.microsoft.com/purview/information-barriers-policies#step-4-apply-ib-policies). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-OrganizationSegment [-Identity] <PolicyIdParameter> + [-UserGroupFilter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +Segments are defined by using certain [attributes](https://learn.microsoft.com/purview/information-barriers-attributes) in Microsoft Entra ID. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-OrganizationSegment -Identity c96e0837-c232-4a8a-841e-ef45787d8fcd -UserGroupFilter "Department -eq 'HRDept'" +``` + +In this example, for the segment that has the GUID c96e0837-c232-4a8a-841e-ef45787d8fcd, we updated the department name to "HRDept". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -UserGroupFilter +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. +- Property is a filterable property. For more information, see [Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +Use the same property for all of your segments, and verify that your segments don't overlap (a user must be assigned to only one segment). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Attributes for information barrier policies](https://learn.microsoft.com/purview/information-barriers-attributes) + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-OutboundConnector.md b/exchange/exchange-ps/exchange/Set-OutboundConnector.md similarity index 79% rename from exchange/exchange-ps/exchange/mail-flow/Set-OutboundConnector.md rename to exchange/exchange-ps/exchange/Set-OutboundConnector.md index ff57cbab70..a73f8dfcd5 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-OutboundConnector.md +++ b/exchange/exchange-ps/exchange/Set-OutboundConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-outboundconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Set-OutboundConnector @@ -17,10 +16,7 @@ This cmdlet is available only in the cloud-based service. Use the Set-OutboundConnector cmdlet to modify an existing Outbound connector in your cloud-based organization. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,19 +35,21 @@ Set-OutboundConnector [-Identity] <OutboundConnectorIdParameter> [-Name <String>] [-RecipientDomains <MultiValuedProperty>] [-RouteAllMessagesViaOnPremises <Boolean>] + [-SenderRewritingEnabled <Boolean>] [-SmartHosts <MultiValuedProperty>] [-TestMode <Boolean>] [-TlsDomain <SmtpDomainWithSubdomains>] [-TlsSettings <TlsAuthLevel>] [-UseMXRecord <Boolean>] [-ValidationRecipients <String[]>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION Outbound connectors send email messages to remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,9 +66,7 @@ This example changes the settings of the existing Outbound connector named Conto The Identity parameter specifies the connector you want to modify. You can use any value that uniquely identifies the connector. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -89,10 +85,11 @@ Accept wildcard characters: False ### -AllAcceptedDomains 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. You can only use this value when the ConnectorType parameter value is OnPremises. - +- $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. - $false: The Outbound connector isn't used in hybrid organizations. This is the default value. +This parameter is effective only for OnPremises connectors. + ```yaml Type: Boolean Parameter Sets: (All) @@ -107,14 +104,13 @@ Accept wildcard characters: False ``` ### -CloudServicesMailEnabled -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://docs.microsoft.com/exchange/hybrid-configuration-wizard). +**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 Office 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. +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. Valid values are: - $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -149,8 +145,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -170,9 +165,7 @@ Accept wildcard characters: False 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. - - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. ```yaml @@ -192,7 +185,6 @@ Accept wildcard characters: False 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. - - OnPremises: The connector services domains that are used by your on-premises organization. ```yaml @@ -212,7 +204,6 @@ Accept wildcard characters: False 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. - - $false: The connector is disabled. ```yaml @@ -232,7 +223,6 @@ Accept wildcard characters: False 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. - - $false: The connector isn't associated with a transport rule. This is the default value. You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector. @@ -254,9 +244,10 @@ Accept wildcard characters: False The IsValidated parameter specifies whether the Outbound connector has been validated. Valid values are: - $true: The connector has been validated, - - $false: The connector hasn't been validated. This is the default value. +Use the Validate-OutboundConnector cmdlet to validate the connector. + ```yaml Type: Boolean Parameter Sets: (All) @@ -275,9 +266,10 @@ The LastValidationTimestamp parameter specifies the date/time that the Outbound To specify a date/time value for this parameter, use either of the following options: -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". +- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z". +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). +Use the Validate-OutboundConnector cmdlet to validate the connector. ```yaml Type: DateTime @@ -327,11 +319,33 @@ Accept wildcard characters: False ``` ### -RouteAllMessagesViaOnPremises -The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises messaging system. Valid values are: +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. +- $false: Messages aren't routed through the on-premises email system. This is the default value. + +This parameter is effective only for OnPremises connectors. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderRewritingEnabled +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 routed through the on-premises messaging system. This setting requires you to set the ConnectorType parameter to the value OnPremises in the same command. +- $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. +- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value. -- $false: Messages aren't routed through the on-premises messaging system. This is the default value. +This parameter is effective only for OnPremises connectors. ```yaml Type: Boolean @@ -347,7 +361,15 @@ Accept wildcard characters: False ``` ### -SmartHosts -The SmartHosts parameter specifies the smart hosts the Outbound connector uses to route mail. This parameter is required if you set the UseMxRecord parameter to $false and 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. Separate each value by using a comma. If you enter an IP address, you may enter the IP address as a literal, for example: 10.10.1.1, or using Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25. The smart host identity can be the FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record. +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. +- Single IP address: For example, 10.10.1.1. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. + +You can specify multiple value separated by commas: `"Value1","Value2",..."ValueN"`. + +This parameter is required if you use the value $false for the UseMxRecord parameter. ```yaml Type: MultiValuedProperty @@ -366,7 +388,6 @@ Accept wildcard characters: False 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. - - $false: Test mode is disabled. This is the default value. ```yaml @@ -383,7 +404,11 @@ Accept wildcard characters: False ``` ### -TlsDomain -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. This parameter is only used if the TlsSettings parameter is set to DomainValidation. Valid input for the TlsDomain 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 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). + +This parameter meaningful only when the TlsSettings value is DomainValidation. ```yaml Type: SmtpDomainWithSubdomains @@ -402,11 +427,8 @@ Accept wildcard characters: False 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. - - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. - - $null (blank): This is the default value. ```yaml @@ -426,8 +448,7 @@ Accept wildcard characters: False 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. - -- $false: The connector delivers email to one or more smart hosts. When you use this value, you also need to specify the smart hosts by using the SmartHosts parameter in the same command. +- $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value. ```yaml Type: Boolean @@ -479,12 +500,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-OutlookAnywhere.md b/exchange/exchange-ps/exchange/Set-OutlookAnywhere.md similarity index 92% rename from exchange/exchange-ps/exchange/client-access-servers/Set-OutlookAnywhere.md rename to exchange/exchange-ps/exchange/Set-OutlookAnywhere.md index 1deecc3d50..bdc199f0c5 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-OutlookAnywhere.md +++ b/exchange/exchange-ps/exchange/Set-OutlookAnywhere.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-outlookanywhere +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-OutlookAnywhere @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-OutlookAnywhere cmdlet to modify Outlook Anywhere virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. Outlook Anywhere uses virtual directories that contain "rpc" in the name. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,11 +38,14 @@ Set-OutlookAnywhere [-Identity] <VirtualDirectoryIdParameter> [-InternalHostname <String>] [-Name <String>] [-SSLOffloading <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,13 +89,11 @@ In Exchange 2010 and Exchange 2013, this example sets the available authenticati ### -Identity 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 - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\<VirtualDirectoryName\> (\<WebsiteName\>)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \<VirtualDirectoryName\>\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -109,12 +109,11 @@ Accept wildcard characters: False ``` ### -ClientAuthenticationMethod -This parameter is available or functional only in 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: - Basic - - Ntlm Although you can use this parameter to set only one authentication method, the command won't return an error if you include multiple values. @@ -135,8 +134,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -156,9 +154,7 @@ Accept wildcard characters: False 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 - - Ntlm - - Negotiate You can't use this parameter with the ExternalClientAuthenticationMethod, InternalClientAuthenticationMethod and IISAuthenticationMethods parameters. @@ -196,13 +192,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -222,8 +214,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \<protocol\>/\<FQDN\>. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -242,14 +233,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -268,9 +255,7 @@ Accept wildcard characters: False The ExternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate external Outlook Anywhere clients. Valid values are: - Basic - - Ntlm - - Negotiate (This is the default value) You can't use this parameter with the DefaultAuthenticationMethods parameter. @@ -292,7 +277,6 @@ Accept wildcard characters: False 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. - - $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This is the default value. The value of this parameter is related to the value of the SSLOffloading parameter. @@ -330,9 +314,7 @@ Accept wildcard characters: False The IISAuthenticationMethods parameter specifies the authentication method that's used on the Outlook Anywhere virtual directory in IIS. Valid values are: - Basic - - Ntlm - - Negotiate You can specify multiple value separated by commas. By default, all values are used. @@ -356,9 +338,7 @@ Accept wildcard characters: False The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are: - Basic - - Ntlm (This is the default value) - - Negotiate You can't use this parameter with the DefaultAuthenticationMethods parameter. @@ -380,7 +360,6 @@ Accept wildcard characters: False 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. - - $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This is the default value. The value of this parameter is related to the value of the SSLOffloading parameter. @@ -434,7 +413,6 @@ Accept wildcard characters: False 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. - - $false: Outlook Anywhere clients using SSL maintain an SSL connection along the entire network path to the Exchange server. Only SSL connections are allowed to the Outlook Anywhere virtual directory. This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it may take several minutes before the change is visible in IIS Manager. @@ -477,12 +455,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Set-OutlookProtectionRule.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance/Set-OutlookProtectionRule.md rename to exchange/exchange-ps/exchange/Set-OutlookProtectionRule.md index ceefb9bad3..9e222994d5 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-OutlookProtectionRule.md +++ b/exchange/exchange-ps/exchange/Set-OutlookProtectionRule.md @@ -1,39 +1,49 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-outlookprotectionrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-OutlookProtectionRule ## SYNOPSIS +**Note**: This cmdlet is no longer supported in the cloud-based service. + This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the Set-OutlookProtectionRule cmdlet to modify an existing Microsoft Outlook protection rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-OutlookProtectionRule [-Identity] <RuleIdParameter> - [-ApplyRightsProtectionTemplate <RmsTemplateIdParameter>] [-Confirm] [-DomainController <Fqdn>] [-Force] - [-FromDepartment <String[]>] [-Name <String>] [-Priority <Int32>] [-SentTo <MultiValuedProperty>] - [-SentToScope <ToUserScope>] [-UserCanOverride <Boolean>] [-WhatIf] [<CommonParameters>] + [-ApplyRightsProtectionTemplate <RmsTemplateIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-Force] + [-FromDepartment <String[]>] + [-Name <String>] + [-Priority <Int32>] + [-SentTo <MultiValuedProperty>] + [-SentToScope <ToUserScope>] + [-UserCanOverride <Boolean>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -Outlook protection rules are used to automatically rights-protect email messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://docs.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). +Outlook protection rules are used to automatically rights-protect email messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). Not specifying any conditions results in an Outlook protection rule being applied to all messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -88,8 +98,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,7 +133,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch specifies whether to suppress the confirmation prompt produced by the cmdlet when modifying a rule with no conditions, resulting in such rules being applied to all messages. +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). ```yaml Type: SwitchParameter @@ -195,15 +206,10 @@ The SentTo parameter specifies one or more recipients. External recipients can b Internal recipients can be specified using any of the following values: - Alias - - Distinguished name (DN) - - ExchangeGUID - - LegacyExchangeDN - - SmtpAddress - - User principal name (UPN) ```yaml @@ -223,7 +229,6 @@ Accept wildcard characters: False The SentToScope parameter specifies the scope of messages to which the rule applies. Valid values include: - All: Applies to all messages. - - InOrganization: Applies to messages originating from inside the Exchange organization, where all recipients are also internal. If not specified, the parameter defaults to All. @@ -245,7 +250,6 @@ Accept wildcard characters: False 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. - - $false: User can't override rule action. ```yaml @@ -282,12 +286,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Set-OutlookProvider.md b/exchange/exchange-ps/exchange/Set-OutlookProvider.md similarity index 83% rename from exchange/exchange-ps/exchange/client-access/Set-OutlookProvider.md rename to exchange/exchange-ps/exchange/Set-OutlookProvider.md index d285c213db..3d9413c338 100644 --- a/exchange/exchange-ps/exchange/client-access/Set-OutlookProvider.md +++ b/exchange/exchange-ps/exchange/Set-OutlookProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-outlookprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-OutlookProvider @@ -17,20 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Set-OutlookProvider cmdlet to set specific global settings using the msExchOutlookProvider attribute on the msExchAutoDiscoverConfig object in Active Directory. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-OutlookProvider [-Identity] <OutlookProviderIdParameter> [-CertPrincipalName <String>] [-Confirm] - [-DomainController <Fqdn>] [-Name <String>] [-OutlookProviderFlags <OutlookProviderFlags>] - [-Server <String>] [-TTL <Int32>] [-WhatIf] [-RequiredClientVersions <String[]>] [<CommonParameters>] +Set-OutlookProvider [-Identity] <OutlookProviderIdParameter> + [-CertPrincipalName <String>] + [-Confirm] + [-DomainController <Fqdn>] + [-Name <String>] + [-OutlookProviderFlags <OutlookProviderFlags>] + [-RequiredClientVersions <String[]>] + [-Server <String>] + [-TTL <Int32>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Set-OutlookProvider cmdlet creates the global settings for the Autodiscover service. It sets the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified in the parameters listed in the Parameters section. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -80,8 +87,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -145,6 +151,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RequiredClientVersions +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. + +ExpirationDate is the UTC date-time when connections by older versions of Outlook will be blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-MM-ddThh:mm:ss.fffZ, where yyyy = year, MM = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC. + +An example of a valid value for this parameter is `"14.0.7012.1000, 2020-01-01T12:00:00Z"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Server The Server parameter specifies the Mailbox server to use for Outlook Anywhere clients. @@ -195,39 +223,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RequiredClientVersions -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. Valid input for this parameter is "\<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. - -\<ExpirationDate\> is the UTC date-time when connections by older versions of Outlook will be blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-mm-ddThh:mm:ss.fffZ, where yyyy = year, mm = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC. - -An example of a valid value for this parameter is "14.0.7012.1000, 2014-01-01T12:00:00Z". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md new file mode 100644 index 0000000000..ffb11aae40 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md @@ -0,0 +1,3015 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-OwaMailboxPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-OwaMailboxPolicy cmdlet to configure existing Outlook on the web mailbox policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-OwaMailboxPolicy [-Identity] <MailboxPolicyIdParameter> + [-AccountTransferEnabled <Boolean>] + [-ActionForUnknownFileAndMIMETypes <AttachmentBlockingActions>] + [-ActiveSyncIntegrationEnabled <Boolean>] + [-AdditionalAccountsEnabled <System.Boolean>] + [-AdditionalStorageProvidersAvailable <Boolean>] + [-AllAddressListsEnabled <Boolean>] + [-AllowCopyContactsToDeviceAddressBook <Boolean>] + [-AllowedFileTypes <MultiValuedProperty>] + [-AllowedMimeTypes <MultiValuedProperty>] + [-AllowedOrganizationAccountDomains <String[]>] + [-AllowOfflineOn <AllowOfflineOnEnum>] + [-BizBarEnabled <Boolean>] + [-BlockedFileTypes <MultiValuedProperty>] + [-BlockedMimeTypes <MultiValuedProperty>] + [-BookingsMailboxCreationEnabled <Boolean>] + [-BookingsMailboxDomain <String>] + [-BoxAttachmentsEnabled <Boolean>] + [-CalendarEnabled <Boolean>] + [-ChangePasswordEnabled <Boolean>] + [-ChangeSettingsAccountEnabled <System.Boolean>] + [-ClassicAttachmentsEnabled <Boolean>] + [-ConditionalAccessPolicy <PolicyEnum>] + [-Confirm] + [-ContactsEnabled <Boolean>] + [-DefaultClientLanguage <Int32>] + [-DefaultTheme <String>] + [-DelegateAccessEnabled <Boolean>] + [-DirectFileAccessOnPrivateComputersEnabled <Boolean>] + [-DirectFileAccessOnPublicComputersEnabled <Boolean>] + [-DisableFacebook] + [-DisplayPhotosEnabled <Boolean>] + [-DomainController <Fqdn>] + [-DropboxAttachmentsEnabled <Boolean>] + [-EmptyStateEnabled <Boolean>] + [-ExplicitLogonEnabled <Boolean>] + [-ExternalImageProxyEnabled <Boolean>] + [-ExternalSPMySiteHostURL <String>] + [-FeedbackEnabled <Boolean>] + [-ForceSaveAttachmentFilteringEnabled <Boolean>] + [-ForceSaveFileTypes <MultiValuedProperty>] + [-ForceSaveMimeTypes <MultiValuedProperty>] + [-ForceWacViewingFirstOnPrivateComputers <Boolean>] + [-ForceWacViewingFirstOnPublicComputers <Boolean>] + [-ForceWebReadyDocumentViewingFirstOnPrivateComputers <Boolean>] + [-ForceWebReadyDocumentViewingFirstOnPublicComputers <Boolean>] + [-FreCardsEnabled <Boolean>] + [-GlobalAddressListEnabled <Boolean>] + [-GoogleDriveAttachmentsEnabled <Boolean>] + [-GroupCreationEnabled <Boolean>] + [-HideClassicOutlookToggleOut <System.Boolean>] + [-InstantMessagingEnabled <Boolean>] + [-InstantMessagingType <InstantMessagingTypeOptions>] + [-InterestingCalendarsEnabled <Boolean>] + [-InternalSPMySiteHostURL <String>] + [-IRMEnabled <Boolean>] + [-IsDefault] + [-ItemsToOtherAccountsEnabled <System.Boolean>] + [-JournalEnabled <Boolean>] + [-JunkEmailEnabled <Boolean>] + [-LinkedInEnabled <Boolean>] + [-LocalEventsEnabled <Boolean>] + [-LogonAndErrorLanguage <Int32>] + [-MessagePreviewsDisabled <Boolean>] + [-MonthlyUpdatesEnabled <Boolean>] + [-Name <String>] + [-NotesEnabled <Boolean>] + [-NpsSurveysEnabled <Boolean>] + [-OfflineEnabledWeb <Boolean>] + [-OfflineEnabledWin <Boolean>] + [-OneDriveAttachmentsEnabled <Boolean>] + [-OneWinNativeOutlookEnabled <System.Boolean>] + [-OnSendAddinsEnabled <Boolean>] + [-OrganizationEnabled <Boolean>] + [-OutboundCharset <OutboundCharsetOptions>] + [-OutlookBetaToggleEnabled <Boolean>] + [-OutlookDataFile <OutlookDataFileFeatureState>] + [-OutlookNewslettersAccessLevel <OutlookNewslettersAccessLevel>] + [-OutlookNewslettersReactions <OutlookNewslettersFeatureState>] + [-OutlookNewslettersShowMore <OutlookNewslettersFeatureState>] + [-OWALightEnabled <Boolean>] + [-OWAMiniEnabled <Boolean>] + [-PersonalAccountCalendarsEnabled <Boolean>] + [-PersonalAccountsEnabled <System.Boolean>] + [-PhoneticSupportEnabled <Boolean>] + [-PlacesEnabled <Boolean>] + [-PremiumClientEnabled <Boolean>] + [-PrintWithoutDownloadEnabled <Boolean>] + [-ProjectMocaEnabled <Boolean>] + [-PublicFoldersEnabled <Boolean>] + [-RecoverDeletedItemsEnabled <Boolean>] + [-ReferenceAttachmentsEnabled <Boolean>] + [-RemindersAndNotificationsEnabled <Boolean>] + [-ReportJunkEmailEnabled <Boolean>] + [-RulesEnabled <Boolean>] + [-SatisfactionEnabled <Boolean>] + [-SaveAttachmentsToCloudEnabled <Boolean>] + [-SearchFoldersEnabled <Boolean>] + [-SetPhotoEnabled <Boolean>] + [-SetPhotoURL <String>] + [-ShowOnlineArchiveEnabled <Boolean>] + [-SignaturesEnabled <Boolean>] + [-SilverlightEnabled <Boolean>] + [-SkipCreateUnifiedGroupCustomSharepointClassification <Boolean>] + [-SMimeEnabled <Boolean>] + [-SMimeSuppressNameChecksEnabled <Boolean>] + [-SpellCheckerEnabled <Boolean>] + [-TasksEnabled <Boolean>] + [-TeamSnapCalendarsEnabled <Boolean>] + [-TextMessagingEnabled <Boolean>] + [-ThemeSelectionEnabled <Boolean>] + [-ThirdPartyAttachmentsEnabled <Boolean>] + [-UMIntegrationEnabled <Boolean>] + [-UNCAccessOnPrivateComputersEnabled <Boolean>] + [-UNCAccessOnPublicComputersEnabled <Boolean>] + [-UseGB18030 <Boolean>] + [-UseISO885915 <Boolean>] + [-UserVoiceEnabled <Boolean>] + [-WacEditingEnabled <Boolean>] + [-WacExternalServicesEnabled <Boolean>] + [-WacOMEXEnabled <Boolean>] + [-WacViewingOnPrivateComputersEnabled <Boolean>] + [-WacViewingOnPublicComputersEnabled <Boolean>] + [-WeatherEnabled <Boolean>] + [-WebPartsFrameOptionsType <WebPartsFrameOptions>] + [-WebReadyDocumentViewingForAllSupportedTypes <Boolean>] + [-WebReadyDocumentViewingOnPrivateComputersEnabled <Boolean>] + [-WebReadyDocumentViewingOnPublicComputersEnabled <Boolean>] + [-WebReadyDocumentViewingSupportedFileTypes <MultiValuedProperty>] + [-WebReadyDocumentViewingSupportedMimeTypes <MultiValuedProperty>] + [-WebReadyFileTypes <MultiValuedProperty>] + [-WebReadyMimeTypes <MultiValuedProperty>] + [-WhatIf] + [-WSSAccessOnPrivateComputersEnabled <Boolean>] + [-WSSAccessOnPublicComputersEnabled <Boolean>] + [<CommonParameters>] +``` + +## DESCRIPTION +In on-premises Exchange, the default Outlook on the web mailbox policy is named Default. In Exchange Online, the default Outlook on the web mailbox policy is named OwaMailboxPolicy-Default. + +Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (`Stop-Service WAS -Force` and `Start-Service W3SVC`). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-OwaMailboxPolicy -Identity EMEA\Contoso\Corporate -CalendarEnabled $false +``` + +This example disables access to the calendar for the mailbox policy named Corporate for the tenant Contoso in the organization EMEA. + +### Example 2 +```powershell +Set-OwaMailboxPolicy -Identity Default -TasksEnabled $false +``` + +This example disables access to the Tasks folder for the default mailbox policy in an on-premises Exchange organization. + +### Example 3 +```powershell +Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -AllowedFileTypes '.doc', '.pdf' +``` + +This example sets the allowed file type extensions to .doc and .pdf for the default mailbox policy in an Exchange Online organization, allowing users to save files with those extensions locally or view them from a web browser. + +### Example 4 +```powershell +Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -UserVoiceEnabled $false +``` + +This example disables Outlook UserVoice for the default mailbox policy in Microsoft 365. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AccountTransferEnabled +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActionForUnknownFileAndMIMETypes +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.) +- ForceSave +- Block + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdditionalStorageProvidersAvailable +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: + +- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This is the default value. +- $false: Additional storage providers are disabled in Outlook on the web. Users can't connect their additional storage providers or share files over email. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ActiveSyncIntegrationEnabled +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. +- $false: ActiveSync isn't available in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdditionalAccountsEnabled +This parameter is available only in the cloud-based service. + +This parameter has been deprecated and is no longer used. + +To enable or disable personal accounts in the new Outlook for Windows, use the PersonalAccountsEnabled parameter. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllAddressListsEnabled +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. +- $false: Only the global address list is visible in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCopyContactsToDeviceAddressBook +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. +- $false: Contacts can't be copied to the device's address book in Outlook on the web for devices. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedFileTypes +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 + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +If the same file types are specified in multiple lists: + +- The Block list overrides the Allow list and the Force Save list. +- The Force Save list overrides the Allow list. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedMimeTypes +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 +- image/gif +- image/jpeg +- image/png + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +If the same MIME types are specified in multiple lists: + +- The Allow list overrides the Block list and the Force Save list. +- The Block list overrides the Force Save list. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedOrganizationAccountDomains +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOfflineOn +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: + +- PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later and Exchange Online, 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 on the Set-OwaVirtualDirectory cmdlet). +- NoComputers: Offline mode is disabled. +- AllComputers: Offline mode is available for public and private computer sessions. This is the default value. + +When offline mode is available, users can turn offline mode on or off themselves in Outlook Web App. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7). + +```yaml +Type: AllowOfflineOnEnum +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BizBarEnabled +This parameter is available only in the cloud-based service. + +{{ Fill BizBarEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedFileTypes +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, .appx, .appcontent-ms, .appref-ms, .asp, .aspx, .asx, .bas, .bat, .cdxml, .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, .pssc, .pst, .py, .pyc, .pyo, .pyw, .pyz, .pyzw, .reg, .scf, .scr, .sct, .settingcontent-ms, .shb, .shs, .theme, .tmp, .udl, .url, .vb, .vbe, .vbp, .vbs, .vsmacros, .vsw, .webpnp, .website, .ws, .wsb, .wsc, .wsf, .wsh, .xbap, .xll, .xnk + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +If the same file types are specified in multiple lists: + +- The Allow list overrides the Block list and the Force Save list. +- The Block list overrides the Force Save list. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedMimeTypes +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 +- application/javascript +- application/msaccess +- application/prg +- application/x-javascript +- text/javascript +- text/scriplet +- x-internet-signup + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +If the same MIME types are specified in multiple lists: + +- The Allow list overrides the Block list and the Force Save list. +- The Block list overrides the Force Save list. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsMailboxCreationEnabled +This parameter is available only in the cloud-based service. + +The BookingsMailboxCreationEnabled parameter allows you disable Microsoft Bookings. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BookingsMailboxDomain +This parameter is available only in the cloud-based service. + +{{ Fill BookingsMailboxDomain Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BoxAttachmentsEnabled +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CalendarEnabled +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: + +- $true: The Calendar is available in Outlook Web App. This is the default value. +- $false: The Calendar isn't available in Outlook Web App. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChangePasswordEnabled +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: + +- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange. +- $false: The Change password option isn't available in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChangeSettingsAccountEnabled +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: + +- $true: Users can change their settings account in the new Outlook for Windows. This is the default value. +- $false: Users can't change their settings account in the new Outlook for Windows. + +**Note**: The settings account is referred to as the primary account in the new Outlook for Windows setting at Settings \> Accounts \> Email accounts \> Manage. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ClassicAttachmentsEnabled +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. +- $false: Users can't attach local files to email messages in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConditionalAccessPolicy +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. + +**Note**: When you enable a Conditional Access policy, users will no longer be able to access the light version of Outlook on the web. An error message will direct them to use the default premium experience. + +Valid values are: + +- Off: No conditional access policy is applied to Outlook on the web. This is the default value. +- ReadOnly: Users can't download attachments to their local computer, and can't enable Offline Mode on non-compliant computers. They can still view attachments in the browser. This doesn't apply to in-line images. +- ReadOnlyPlusAttachmentsBlocked: All restrictions from ReadOnly apply, but users can't view attachments in the browser. This doesn't apply to in-line images. + +```yaml +Type: PolicyEnum +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContactsEnabled +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: + +- $true: Contacts are available in Outlook Web App. This is the default value. +- $false: Contacts aren't available in Outlook Web App. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultClientLanguage +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultTheme +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DelegateAccessEnabled +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: + +- $true: Delegates can open the mailbox in Outlook on the web. This is the default value. +- $false: Delegates can't open the mailbox in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DirectFileAccessOnPrivateComputersEnabled +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. +- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. + +By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DirectFileAccessOnPublicComputersEnabled +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. +- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. + +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 on the Set-OwaVirtualDirectory cmdlet). + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableFacebook +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). + +The DisableFacebook switch specifies whether users can synchronize their Facebook contacts to their Contacts folder in Outlook on the web. By default, Facebook integration is enabled. + +- To disable Facebook integration, use this switch without a value. +- To enable Facebook integration after it's been disabled, use this exact syntax: `-DisableFacebook:$false`. + +The value of this switch is stored in the FacebookEnabled property in the output of the Get-OwaMailboxPolicy cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayPhotosEnabled +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. +- $false: Users don't see sender photos in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DropboxAttachmentsEnabled +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmptyStateEnabled +This parameter is available only in the cloud-based service. + +{{ Fill EmptyStateEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExplicitLogonEnabled +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: + +- $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. +- $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalImageProxyEnabled +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: + +- $true: All external images are loaded through the Outlook external image proxy. This is the default value. +- $false: All external images are loaded through the web browser. This is potentially unsafe, as the images could have mixed content or malformed images that ask for user credentials. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalSPMySiteHostURL +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FeedbackEnabled +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: + +- $true: Inline feedback surveys are enabled. This is the default value. +- $false: Inline feedback surveys are disabled. + + Surveys allow users to provide feedback on specific features. For example, for the text predictions feature, the inline feedback "Are the above autocomplete suggestions helpful (yes/no)?" is shown. If a user chooses "no" they can provide specific feedback. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceSaveAttachmentFilteringEnabled +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. +- $false: The attachments aren't filtered before they're saved. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceSaveFileTypes +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 + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +If the same file types are specified in multiple lists: + +- The Allow list overrides the Block list and the Force Save list. +- The Block list overrides the Force Save list. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceSaveMimeTypes +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 +- Application/octet-stream +- Application/x-director +- Application/x-shockwave-flash +- text/html + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +If the same MIME types are specified in multiple lists: + +- The Allow list overrides the Block list and the Force Save list. +- The Block list overrides the Force Save list. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceWacViewingFirstOnPrivateComputers +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. +- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. + +By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceWacViewingFirstOnPublicComputers +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. +- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. + +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 on the Set-OwaVirtualDirectory cmdlet). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceWebReadyDocumentViewingFirstOnPrivateComputers +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: + +- $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. +- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. + +By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceWebReadyDocumentViewingFirstOnPublicComputers +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: + +- $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. +- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. + +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 on the Set-OwaVirtualDirectory cmdlet). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FreCardsEnabled +This parameter is functional only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GlobalAddressListEnabled +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. +- $false: The global address list isn't visible in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GoogleDriveAttachmentsEnabled +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupCreationEnabled +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: + +- $true: Users can create Microsoft 365 Groups in Outlook and Outlook on the web. This is the default value. +- $false: Users can't create Microsoft 365 Groups in Outlook and Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HideClassicOutlookToggleOut +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: + +- $true: The toggle to switch back to classic Outlook is hidden in new Outlook for Windows. +- $false: The toggle to switch back to classic Outlook isn't hidden in new Outlook for Windows. This is the default value. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InstantMessagingEnabled +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. +- $false: Instant messaging isn't available in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InstantMessagingType +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. +- Ocs: Lync or Skype (formerly known as Office Communication Server). This is the default value in Exchange Online. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InterestingCalendarsEnabled +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: + +- $true: Interesting calendars are available in Outlook on thew web. This is the default value. +- $false: Interesting calendars aren't available in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalSPMySiteHostURL +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IRMEnabled +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. +- $false: IRM isn't available in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDefault +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. + +**Note**: In Exchange Online - and excluding resource mailboxes - this value will be superseded by the **OwaMailboxPolicy** parameter in each organization's [CASMailboxPlan](https://learn.microsoft.com/powershell/module/exchange/set-casmailboxplan). That value will instead be applied per each mailbox's SKU. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ItemsToOtherAccountsEnabled +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: + +- $true: Users can move and copy messages to and from external accounts. +- $false: Users can't move or copy messages to and from external accounts. This is the default value. + +**Note:** This policy doesn't affect moving or copying messages between Microsoft 365 Groups and shared mailboxes within the organization. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -JournalEnabled +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. +- $false: The Journal folder isn't visible in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -JunkEmailEnabled +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: + +- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value. +- $false: The Junk Email folder and junk email management aren't available in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LinkedInEnabled +This parameter is available only in the cloud-based service. + +LinkedIn integration is no longer supported. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalEventsEnabled +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: + +- $true: Local events are available in Outlook on the web. +- $false: Local events aren't available in Outlook on the web. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LogonAndErrorLanguage +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. + +The default value is 0, which means the logon and error language selection is undefined. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessagePreviewsDisabled +This parameter is available only in the cloud-based service. + +{{ Fill MessagePreviewsDisabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MonthlyUpdatesEnabled +This parameter is available only in the cloud-based service. + +{{ Fill MonthlyUpdatesEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotesEnabled +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. +- $false: The Notes folder isn't visible in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NpsSurveysEnabled +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: + +- $true: The NPS survey is available in Outlook on the web. This is the default value. +- $false: The NPS survey isn't available in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OfflineEnabledWeb +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: + +- $true: Users can manage offline capabilities in Outlook on the web. This is the default value. +- $false: Users can't manage offline capabilities in Outlook on the web. No items are saved to the user's device. Previously save items are deleted. + +When offline capabilities are available, users can turn offline capabilities on or off themselves in Outlook on the web at Settings \> General \> Offline. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OfflineEnabledWin +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: + +- $true: Users can manage offline capabilities in the new Outlook for Windows. This is the default value. +- $false: Users can't manage offline capabilities in the new Outlook for Windows. No items are saved to the user's device. Previously save items are deleted. + +When offline capabilities are available, users can turn offline capabilities on or off themselves in the New Outlook for Windows at Settings \> General \> Offline. By default, offline capabilities are turned on. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneDriveAttachmentsEnabled +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. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OneWinNativeOutlookEnabled +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: + +- $true: The New Outlook for Windows App is available. This is the default value. +- $false: The new Outlook for Windows App isn't available. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnSendAddinsEnabled +The OnSendAddinsEnabled parameter specifies whether to enable or disable on send add-ins in Outlook on the web (add-ins that support events when a user clicks Send). Valid values are: + +- $true: On send add-ins are enabled. +- $false: On send add-ins are disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutboundCharset +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. +- AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. +- UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookBetaToggleEnabled +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: + +- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This is the default value. +- $false: Outlook on the web Preview is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookNewslettersAccessLevel +This parameter is available only in the cloud-based service. + +The OutlookNewslettersAccessLevelAccess parameter specifies the access level in Outlook Newsletters. Valid values are: + +- NoAccess: No access to Outlook Newsletters in the New Outlook for Windows or Outlook on the web. Users can still read email messages sent or forwarded to them. +- ReadOnly: Read newsletters and browse pages in Outlook Newsletters. +- ReadWrite: Full authoring permissions to create pages and newsletters in Outlook Newsletters. +- Undefined: This is the default value. Currently, this value is equivalent to NoAccess. + +```yaml +Type: OutlookNewslettersAccessLevel +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookDataFile +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: + +- Allow: The default value. Users can open .pst files, import from a .pst file to a mailbox, export from a mailbox to a .pst file, and copy items to and from .pst files. +- NoExport: Users can't export from a mailbox to a .pst file. +- NoExportNoGrow: Users can't export from a mailbox to a .pst file, or copy items from a mailbox to a .pst file. +- NoExportNoOpen: Users can't export from a mailbox to a .pst file, or open new .pst files. +- NoExportNoOpenNoGrow: Users can't export from a mailbox to a .pst file, copy items from a mailbox to a .pst file, or open new .pst files. +- Deny: Users can't open new .pst files, import from a .pst file to a mailbox, export from a mailbox to a .pst file, or copy items to and from .pst files. + +```yaml +Type: OutlookDataFileFeatureState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: Allow +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookNewslettersReactions +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: + +- DefaultOff: The controls are turned off. +- DefaultOn: The controls are turned on. +- Disabled: The controls are disabled for users. +- Undefined: This is the default value. + +```yaml +Type: OutlookNewslettersFeatureState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutlookNewslettersShowMore +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: + +- DefaultOff: Recommendations are turned off. +- DefaultOn: Recommendations are turned on. +- Disabled: Recommendations are disabled for users. +- Undefined: This is the default value. + +Authors can disable these recommendations for each individual newsletter edition, or admins can use this parameter to globally disable these recommendations. + +```yaml +Type: OutlookNewslettersFeatureState +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OWALightEnabled +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. +- $false: The light version of Outlook on the web isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OWAMiniEnabled +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: + +- $true: The mini version of Outlook Web App is available. This is the default value. +- $false: The mini version of Outlook Web App isn't available. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PersonalAccountCalendarsEnabled +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: + +- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This is the default value. +- $false: Users can't connect to their Outlook.com or Google Calendar in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PersonalAccountsEnabled +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: + +- $true: Users can add their personal accounts in the new Outlook for Windows. This is the default value. +- $false: Users can't add their personal accounts in the new Outlook for Windows. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhoneticSupportEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PlacesEnabled +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: + +- $true: Places is enabled. This is the default value. +- $false: Places is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PremiumClientEnabled +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. +- $false: The full version of Outlook Web App isn't available. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrintWithoutDownloadEnabled +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: + +- $true: Supported files can be printed without being downloaded in Outlook on the web. This is the default value. +- $false: Supported files must be downloaded before they can be printed in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProjectMocaEnabled +**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. + +The ProjectMocaEnabled parameter enables or disables access to Project Moca in Outlook on the web. Valid values are: + +- $true: Access to Project Moca is enabled in Outlook on the web. +- $false: Access to Project Moca is disabled in Outlook on the web. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublicFoldersEnabled +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: + +- $true: Public folders are available in Outlook Web App. This is the default value. +- $false: Public folders aren't available in Outlook Web App. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecoverDeletedItemsEnabled +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: + +- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value. +- $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReferenceAttachmentsEnabled +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. +- $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemindersAndNotificationsEnabled +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. +- $false: Notifications and reminders are disabled in Outlook on the web. + +This parameter doesn't apply to the light version of Outlook Web App. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportJunkEmailEnabled +**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: + +- $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. +- $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no 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. + +This parameter is meaningful only when the JunkEmailEnabled parameter is set 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RulesEnabled +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. +- $false: Users can't view, create, or modify server-side rules in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SatisfactionEnabled +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. +- $false: The satisfaction survey is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SaveAttachmentsToCloudEnabled +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. +- $false: Users can only save regular email attachments locally. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SearchFoldersEnabled +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. +- $false: Search Folders aren't visible in Outlook on the Web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SetPhotoEnabled +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. +- $false: Users can't manage their user photo in Outlook on the web. + +**Note**: To control whether users can update photos for Exchange Online, see [Configure User Administrator support for profile photo updates](https://learn.microsoft.com/graph/profilephoto-configure-settings#configure-user-administrator-support-for-profile-photo-updates). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SetPhotoURL +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShowOnlineArchiveEnabled +This parameter is available only in the cloud-based service. + +{{ Fill ShowOnlineArchiveEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignaturesEnabled +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. +- $false: Signatures aren't available in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SilverlightEnabled +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: + +- $true: Silverlight features are available in Outlook Web App. This is the default value. +- $false: Silverlight features aren't available in Outlook Web App. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipCreateUnifiedGroupCustomSharepointClassification +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: + +- $true: The custom SharePoint page is skipped when a user creates a Microsoft 365 Group in Outlook on the web. This is the default value. +- $false: The custom SharePoint page is shown when a user creates a Microsoft 365 Group in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SMimeEnabled +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: + +- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value. +- $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated. + +**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SMimeSuppressNameChecksEnabled +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. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpellCheckerEnabled +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: + +- $true: Spell checking is available in Outlook Web App. This is the default value. +- $false: Spell checking isn't available in Outlook Web App. + +This parameter doesn't apply to the light version of Outlook Web App. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TasksEnabled +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: + +- $true: The Tasks folder is available in Outlook Web App. This is the default value. +- $false: The Tasks folder isn't available in Outlook Web App. + +This parameter doesn't apply to the light version of Outlook Web App. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamSnapCalendarsEnabled +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: + +- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This is the default value. +- $false: Users can't connect to their TeamSnap calendars in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TextMessagingEnabled +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. +- $false: Text messaging isn't available in Outlook on the web. + +This parameter doesn't apply to the light version of Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThemeSelectionEnabled +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. +- $false: Users can't specify or change the theme in Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThirdPartyAttachmentsEnabled +This parameter is available only in on-premises Exchange. + +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 +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UMIntegrationEnabled +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. +- $false: UM integration is disabled in Outlook on the web. + +This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). + +This parameter doesn't apply to the light version of Outlook on the web. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UNCAccessOnPrivateComputersEnabled +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UNCAccessOnPublicComputersEnabled +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseGB18030 +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. +- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseISO885915 +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. +- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserVoiceEnabled +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: + +- $true: Outlook UserVoice is enabled. This is the default value. +- $false: Outlook UserVoice is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WacEditingEnabled +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. +- $false: Users can't edit supported documents in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WacExternalServicesEnabled +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. +- $false: External services are disabled when viewing supported documents in Outlook on the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WacOMEXEnabled +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. +- $false: apps for Outlook are disabled in Outlook on the web. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WacViewingOnPrivateComputersEnabled +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. +- $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. + +By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WacViewingOnPublicComputersEnabled +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. +- $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. + +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 on the Set-OwaVirtualDirectory cmdlet). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WeatherEnabled +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: + +- $true: Weather is enabled. This is the default value. +- $false: Weather is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebPartsFrameOptionsType +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. +- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. +- Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it. + +```yaml +Type: WebPartsFrameOptions +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebReadyDocumentViewingForAllSupportedTypes +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: + +- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value. +- $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebReadyDocumentViewingOnPrivateComputersEnabled +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: + +- $true: WebReady Document Viewing is available in private computer sessions. This is the default value. +- $false: WebReady Document Viewing isn't available in private computer sessions. + +By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebReadyDocumentViewingOnPublicComputersEnabled +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: + +- $true: WebReady Document Viewing is available for public computer sessions. This is the default value. +- $false: WebReady Document Viewing isn't available for public computer sessions. + +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 on the Set-OwaVirtualDirectory cmdlet). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebReadyDocumentViewingSupportedFileTypes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebReadyDocumentViewingSupportedMimeTypes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebReadyFileTypes +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: + +- .doc +- .docx +- .dot +- .pdf +- .pps +- .ppt +- .pptx +- .rtf +- .xls +- .xlsx + +You can only remove or add values from within the list of supported file types (you can't add additional values). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parameter is set to $false. Otherwise, all supported file types are available in WebReady Document Viewing. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WebReadyMimeTypes +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: + +- application/msword +- application/pdf +- application/vnd.ms-excel +- application/vnd.ms-powerpoint +- application/vnd.openxmlformats-officedocument.presentationml.presentation +- application/vnd.openxmlformats-officedocument.spreadsheetml.sheet +- application/vnd.openxmlformats-officedocument.wordprocessingml.document +- application/x-msexcel +- application/x-mspowerpoint + +You can only remove or add values from within the list of supported file types (you can't add additional values). + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parameter is set to $false. Otherwise, all supported MIME types are available in WebReady Document Viewing. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WSSAccessOnPrivateComputersEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WSSAccessOnPublicComputersEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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 + +[New-OwaMailboxPolicy](https://learn.microsoft.com/powershell/module/exchange/new-owamailboxpolicy) + +[Get-OwaMailboxPolicy](https://learn.microsoft.com/powershell/module/exchange/get-owamailboxpolicy) + +[Set-CASMailbox](https://learn.microsoft.com/powershell/module/exchange/set-casmailbox) + +[Outlook on the web mailbox policy procedures in Exchange Online](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-on-the-web/outlook-web-app-mailbox-policy-procedures) diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-OwaVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md rename to exchange/exchange-ps/exchange/Set-OwaVirtualDirectory.md index c245976ccf..14358aa512 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Set-OwaVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-owavirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-OwaVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-OwaVirtualDirectory cmdlet to modify existing Outlook on the web virtual directories that are used in Internet Information Services (IIS) on Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -155,20 +154,14 @@ Set-OwaVirtualDirectory [-Identity] <VirtualDirectoryIdParameter> Before you run the Set-OwaVirtualDirectory cmdlet, consider the following items: - You must have Write access to virtual directory objects in Active Directory. If you don't have the necessary permissions and you try to run the Set-OwaVirtualDirectory cmdlet on the Active Directory virtual directory object, the cmdlet fails. - - You must have Write access to virtual directory objects in the metabase for some properties, such as Authentication and GZip. If you don't have the necessary permissions to run the Set-OwaVirtualDirectory cmdlet on a metabase virtual directory object or on a parameter that writes to the metabase, the cmdlet fails. - - Verify that the data source can be read. Depending on the properties that you want to set on an Outlook on the web virtual directory, you may want to run the cmdlet in a test environment on the Outlook on the web virtual directory object in Active Directory, the metabase, or both. - - You can run the Set-OwaVirtualDirectory cmdlet on any server that has the Exchange Server administration tools installed. - -- Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see [Modifying multivalued properties](https://docs.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). - +- Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). - Many of the Outlook on the web virtual directory settings require you to restart IIS (Stop-Service WAS -Force and Start-Service W3SVC) before the change takes effect. For example, when you enable or disable forms-based authentication, or when you enable or disable the Private computer option on the sign-in page. - - To switch from forms-based authentication to Basic authentication, you must first disable forms-based authentication, and then as a separate task, enable Basic authentication. You can't disable forms-based authentication and enable Basic authentication in a single task. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -191,13 +184,11 @@ This example sets the ActionForUnknownFileAndMIMETypes parameter to Block on the ### -Identity 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 - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\<VirtualDirectoryName\> (\<WebsiteName\>)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \<VirtualDirectoryName\>\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -216,9 +207,7 @@ Accept wildcard characters: False 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.) - - ForceSave - - Block ```yaml @@ -238,7 +227,6 @@ Accept wildcard characters: False 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. - - $false: ActiveSync isn't available in Outlook on the web ```yaml @@ -258,7 +246,6 @@ Accept wildcard characters: False 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. - - $false: ADFS authentication is disabled. This is the default value. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false before you can use this value. ```yaml @@ -278,7 +265,6 @@ Accept wildcard characters: False 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. - - $false: Only the global address list is visible in Outlook on the web. ```yaml @@ -298,7 +284,6 @@ Accept wildcard characters: False 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. - - $false: Contacts can't be copied to the device's address book in Outlook on the web for devices. ```yaml @@ -319,14 +304,13 @@ The AllowedFileTypes parameter specifies the attachment file types (file extensi .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 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the same file types are specified in multiple lists: - The Allow list overrides the Block list and the Force Save list. - - The Block list overrides the Force Save list. ```yaml @@ -346,21 +330,17 @@ Accept wildcard characters: False 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 - - image/gif - - image/jpeg - - image/png -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the same MIME types are specified in multiple lists: - The Allow list overrides the Block list and the Force Save list. - - The Block list overrides the Force Save list. ```yaml @@ -380,12 +360,10 @@ Accept wildcard characters: False 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). - - NoComputers: Offline mode is disabled. - - AllComputers: Offline mode is available for public and private computer sessions. This is the default value. -When offline mode is available, users can turn offline mode on or off themselves in Outlook on the web. For more information, see [Using Outlook Web App offline](https://go.microsoft.com/fwlink/p/?linkid=267644). +When offline mode is available, users can turn offline mode on or off themselves in Outlook on the web. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7). ```yaml Type: AllowOfflineOnEnum @@ -404,7 +382,6 @@ Accept wildcard characters: False 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. - - $false: Features are disabled for anonymous users. ```yaml @@ -424,7 +401,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. This parameter can be used with the FormsAuthentication parameter or with the DigestAuthentication and WindowsAuthentication parameters. @@ -447,14 +423,13 @@ The BlockedFileTypes parameter specifies a list of attachment file types (file e .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 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the same file types are specified in multiple lists: - The Allow list overrides the Block list and the Force Save list. - - The Block list overrides the Force Save list. ```yaml @@ -474,29 +449,21 @@ Accept wildcard characters: False 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 - - application/javascript - - application/msaccess - - application/prg - - application/x-javascript - - text/javascript - - text/scriplet - - x-internet-signup -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the same MIME types are specified in multiple lists: - The Allow list overrides the Block list and the Force Save list. - - The Block list overrides the Force Save list. ```yaml @@ -532,7 +499,6 @@ Accept wildcard characters: False 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. - - $false: The Calendar isn't available in Outlook on the web. ```yaml @@ -549,12 +515,11 @@ Accept wildcard characters: False ``` ### -CalendarPublishingEnabled -This parameter is available or functional only in 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: - $true: Calendar publishing is enabled. This is the default value. - - $false: Calendar publishing is disabled. ```yaml @@ -574,7 +539,6 @@ Accept wildcard characters: False 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. - - $false: The Change password option isn't available in Outlook on the web. ```yaml @@ -594,7 +558,6 @@ Accept wildcard characters: False 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. - - $false: Users can't attach local files to email messages in Outlook on the web. ```yaml @@ -614,7 +577,6 @@ Accept wildcard characters: False 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 - - High (This is the default value) This parameter doesn't apply to the light version of Outlook on the web. @@ -635,8 +597,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -656,7 +617,6 @@ Accept wildcard characters: False 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. - - $false: Contacts aren't available in Outlook on the web. ```yaml @@ -673,12 +633,11 @@ Accept wildcard characters: False ``` ### -CrossSiteRedirectType -This parameter is available or functional only in 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: - Silent: Users are automatically redirected when the Client Access server redirects an Outlook Web App request to Client Access server infrastructure in another Active Directory site. If using forms-based authentication, SSL is required. For redirection to occur, the target OWA virtual directory must have an ExternalURL value. - - Manual: Users receive a notification that they are accessing the wrong URL and that they must click a link to access the preferred Outlook Web App URL for their mailbox. This notification occurs only when the Client Access server determines that it must redirect an Outlook Web App request to the Client Access server infrastructure in another Active Directory site. For redirection to occur, the target OWA virtual directory must have an ExternalURL value. The default value is Manual. @@ -729,7 +688,7 @@ Accept wildcard characters: False ``` ### -DefaultTheme -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://docs.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016). +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. @@ -747,19 +706,18 @@ Accept wildcard characters: False ``` ### -DelegateAccessEnabled -This parameter is available or functional only in Exchange Server 2010. +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: - $true: Delegates can open the mailbox in Outlook Web App. This is the default value. - - $false: Delegates can't open the mailbox in Outlook Web App. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -772,7 +730,6 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. - - $false: Digest authentication is disabled. This is the default value. You can use this parameter with the FormsAuthentication parameter. @@ -794,7 +751,6 @@ Accept wildcard characters: False 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. - - $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -816,7 +772,6 @@ Accept wildcard characters: False 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. - - $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. 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). @@ -838,7 +793,6 @@ Accept wildcard characters: False 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. - - $false: Users don't see sender photos in Outlook on the web. ```yaml @@ -887,7 +841,7 @@ Accept wildcard characters: False ``` ### -Exchange2003Url -This parameter is available or functional only in Exchange Server 2010. +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. @@ -895,7 +849,7 @@ The Exchange2003Url parameter specifies the Outlook Web App URL for Exchange Ser Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -924,7 +878,6 @@ Accept wildcard characters: False 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. - - $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web. ```yaml @@ -944,18 +897,14 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -974,12 +923,11 @@ Accept wildcard characters: False 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. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \<protocol\>/\<FQDN\>. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -998,12 +946,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -1022,33 +968,19 @@ Accept wildcard characters: False 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 - - Basic - - Certificate - - Digest - - Fba - - Kerberos - - LiveIdBasic - - LiveIdFba - - LiveIdNegotiate - - NegoEx - - Negotiate - - Ntlm - - OAuth - - WindowsIntegrated - - WSSecurity You can specify multiple values separated by commas. @@ -1056,7 +988,6 @@ You can specify multiple values separated by commas. Although you can specify any of these values, whether or not the authentication method actually works for external connections depends on other factors. For example: - Is the authentication method available on the virtual directory? - - Is the authentication method available, but disabled on the virtual directory? ```yaml @@ -1089,9 +1020,9 @@ Accept wildcard characters: False ``` ### -ExternalSPMySiteHostURL -The ExternalSPMySiteHostURL specifies the My Site Host URL for external users (for example, https://sp01.contoso.com). +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 for Business to appear as regular file attachments in messages. +This parameter is part of rich document collaboration that allows links to documents in OneDrive to appear as regular file attachments in messages. ```yaml Type: String @@ -1146,9 +1077,7 @@ Accept wildcard characters: False The FilterWebBeaconsAndHtmlForms parameter specifies how web beacons are handled in Outlook on the web. Valid values are: - UserFilterChoice (This is the default value) - - ForceFilter - - DisableFilter ```yaml @@ -1168,7 +1097,6 @@ Accept wildcard characters: False 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. - - $false: The attachments aren't filtered before they're saved. This is the default value. ```yaml @@ -1189,14 +1117,13 @@ The ForceSaveFileTypes parameter specifies the attachment file types (file exten .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 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the same file types are specified in multiple lists: - The Allow list overrides the Block list and the Force Save list. - - The Block list overrides the Force Save list. ```yaml @@ -1216,23 +1143,18 @@ Accept wildcard characters: False 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 - - Application/octet-stream - - Application/x-director - - Application/x-shockwave-flash - - text/html -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the same MIME types are specified in multiple lists: - The Allow list overrides the Block list and the Force Save list. - - The Block list overrides the Force Save list. ```yaml @@ -1252,7 +1174,6 @@ Accept wildcard characters: False 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. - - $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -1274,7 +1195,6 @@ Accept wildcard characters: False 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. - - $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. 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). @@ -1298,7 +1218,6 @@ 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: - $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. - - $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -1322,7 +1241,6 @@ 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: - $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. - - $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. 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). @@ -1344,7 +1262,6 @@ Accept wildcard characters: False 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. - - $false: Forms-based authentication is disabled in Outlook on the web. ```yaml @@ -1380,7 +1297,6 @@ Accept wildcard characters: False 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. - - $false: The global address list isn't visible in Outlook on the web. ```yaml @@ -1416,11 +1332,8 @@ Accept wildcard characters: False The GzipLevel parameter sets Gzip configuration information for the Outlook on the web virtual directory. Valid values are: - Off - - Low (This is the default value) - - High - - Error ```yaml @@ -1453,10 +1366,9 @@ Accept wildcard characters: False ``` ### -InstantMessagingEnabled -The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. Valid values are: +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. - - $false: Instant messaging isn't available in Outlook on the web. ```yaml @@ -1492,7 +1404,6 @@ Accept wildcard characters: False The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are: - None: This is the default value. - - Ocs: Lync or Skype (formerly known as Office Communication Server). ```yaml @@ -1512,7 +1423,6 @@ Accept wildcard characters: False 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. - - $false: Integrated features are disabled. ```yaml @@ -1545,9 +1455,9 @@ Accept wildcard characters: False ``` ### -InternalSPMySiteHostURL -The InternalSPMySiteHostURL specifies the My Site Host URL for internal users (for example, https://sp01.contoso.com). +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 for Business to appear as regular file attachments in messages. +This parameter is part of rich document collaboration that allows links to documents in OneDrive to appear as regular file attachments in messages. ```yaml Type: String @@ -1584,7 +1494,6 @@ Accept wildcard characters: False 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. - - $false: IRM isn't available in Outlook on the web. ```yaml @@ -1604,7 +1513,6 @@ Accept wildcard characters: False 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. - - $false: External users don't use the virtual directory for Outlook on the web. This is the default value. ```yaml @@ -1624,7 +1532,6 @@ Accept wildcard characters: False 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. - - $false: The Journal folder isn't visible in Outlook on the web. ```yaml @@ -1644,7 +1551,6 @@ Accept wildcard characters: False 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. - - $false: The Junk Email folder and junk email management aren't available in Outlook on the web. ```yaml @@ -1661,12 +1567,11 @@ Accept wildcard characters: False ``` ### -LegacyRedirectType -This parameter is available or functional only in 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: - Silent: A standard redirect is used. This is the default value. - - Manual: An intermediate page is displayed to show the legacy URL so that users can change their bookmarks. ```yaml @@ -1706,9 +1611,7 @@ Accept wildcard characters: False 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. - - UserName: Requires only the username, but you also need to specify a value for the DefaultDomain parameter. - - PrincipalName: Requires the user principal name (UPN) (for example, user@contoso.com). This sign-in method works only for users whose UPN name is the same as their email address. ```yaml @@ -1728,7 +1631,6 @@ Accept wildcard characters: False 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. - - $false: The option to use the light version of Outlook on the web is available on the sign-in page. This parameter is meaningful only for browsers that support the full version of Outlook on the web; unsupported browsers are always required to use the light version of Outlook on the web. @@ -1750,10 +1652,9 @@ Accept wildcard characters: False 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. - - $false: The public/private computer session selection isn't available on the Outlook on the web sign-in page. All sessions are considered to be on private computers. This is the default value. -By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. Users can only specify public computer sessions if you've set this parameter value to $false. +By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. Users can only specify public computer sessions if you've set this parameter value to $true. When you change the value of this parameter, restart IIS (Stop-Service WAS -Force and Start-Service W3SVC). @@ -1774,7 +1675,6 @@ Accept wildcard characters: False 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. - - $false: The Notes folder isn't visible in Outlook on the web. ```yaml @@ -1791,7 +1691,7 @@ Accept wildcard characters: False ``` ### -NotificationInterval -This parameter is available or functional only in Exchange Server 2010. +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. @@ -1864,9 +1764,7 @@ Accept wildcard characters: False 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. - -- AlwaysUTF8: Always use UTF-8 encoded UNICODE characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. - +- AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. - UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages. ```yaml @@ -1886,7 +1784,6 @@ Accept wildcard characters: False 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. - - $false: The light version of Outlook on the web is isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web. ```yaml @@ -1903,12 +1800,11 @@ Accept wildcard characters: False ``` ### -OWAMiniEnabled -This parameter is available or functional only in 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: - $true: The mini version of Outlook Web App is available. This is the default value. - - $false: The mini version of Outlook Web App isn't available. ```yaml @@ -1928,7 +1824,6 @@ Accept wildcard characters: False 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. - - $false: The full version of Outlook Web App isn't available. ```yaml @@ -1945,12 +1840,11 @@ Accept wildcard characters: False ``` ### -PublicFoldersEnabled -This parameter is available or functional only in Exchange Server 2010. +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: - $true: Public folders are available in Outlook Web App. This is the default value. - - $false: Public folders aren't available in Outlook Web App. ```yaml @@ -1967,12 +1861,11 @@ Accept wildcard characters: False ``` ### -RecoverDeletedItemsEnabled -This parameter is available or functional only in Exchange Server 2010. +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: - $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value. - - $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained. ```yaml @@ -1992,7 +1885,6 @@ Accept wildcard characters: False 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. - - $false: Outlook on the web doesn't redirect clients to the optimal Mailbox server. ```yaml @@ -2012,7 +1904,6 @@ Accept wildcard characters: False 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. - - $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message. ```yaml @@ -2032,7 +1923,6 @@ Accept wildcard characters: False 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. - - $false: Notifications and reminders are disabled in Outlook on the web. This parameter doesn't apply to the light version of Outlook Web App. @@ -2051,7 +1941,7 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsActionForUnknownServers -This parameter is available or functional only in Exchange Server 2010. +This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -2059,7 +1949,7 @@ This parameter has been deprecated and is no longer used. Type: RemoteDocumentsActions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2069,7 +1959,7 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsAllowedServers -This parameter is available or functional only in Exchange Server 2010. +This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -2087,7 +1977,7 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsBlockedServers -This parameter is available or functional only in Exchange Server 2010. +This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -2095,7 +1985,7 @@ This parameter has been deprecated and is no longer used. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2105,7 +1995,7 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsInternalDomainSuffixList -This parameter is available or functional only in Exchange Server 2010. +This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -2113,7 +2003,7 @@ This parameter has been deprecated and is no longer used. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2125,9 +2015,8 @@ Accept wildcard characters: False ### -ReportJunkEmailEnabled 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. - -- $false: Selecting a message in the Junk Email folder and clicking Not junk \> Not junk moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking Junk \> Junk moves the message to the Junk Email folder with no 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. +- $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. +- $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no 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. This parameter is meaningful only when the JunkEmailEnabled parameter is set to $true. @@ -2148,7 +2037,6 @@ Accept wildcard characters: False 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. - - $false: Users can't view, create, or modify server-side rules in Outlook on the web. ```yaml @@ -2168,7 +2056,6 @@ Accept wildcard characters: False 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. - - $false: Users can only save regular email attachments locally. ```yaml @@ -2185,19 +2072,18 @@ Accept wildcard characters: False ``` ### -SearchFoldersEnabled -This parameter is available or functional only in Exchange Server 2010. +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: - $true: Search Folders are visible in Outlook on the Web. This is the default value. - - $false: Search Folders aren't visible in Outlook on the Web. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2210,7 +2096,6 @@ Accept wildcard characters: False 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. - - $false: Users can't manage their user photo in Outlook on the web. ```yaml @@ -2246,7 +2131,6 @@ Accept wildcard characters: False 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. - - $false: Signatures aren't available in Outlook on the web. ```yaml @@ -2263,19 +2147,18 @@ Accept wildcard characters: False ``` ### -SilverlightEnabled -This parameter is available or functional only in Exchange Server 2010. +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: - $true: Silverlight features are available in Outlook Web App. This is the default value. - - $false: Silverlight features aren't available in Outlook Web App. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2285,21 +2168,20 @@ Accept wildcard characters: False ``` ### -SMimeEnabled -This parameter is available or functional only in Exchange Server 2010. +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: - $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value. - - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated. -**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://docs.microsoft.com/Exchange/policy-and-compliance/smime). +**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2309,12 +2191,11 @@ Accept wildcard characters: False ``` ### -SpellCheckerEnabled -This parameter is available or functional only in Exchange Server 2010. +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: - $true: Spell checking is available in Outlook Web App. This is the default value. - - $false: Spell checking isn't available in Outlook Web App. This parameter doesn't apply to the light version of Outlook Web App. @@ -2323,7 +2204,7 @@ This parameter doesn't apply to the light version of Outlook Web App. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2336,7 +2217,6 @@ Accept wildcard characters: False 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. - - $false: The Tasks folder isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2358,7 +2238,6 @@ Accept wildcard characters: False 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. - - $false: Text messaging isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2380,7 +2259,6 @@ Accept wildcard characters: False 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. - - $false: Users can't specify or change the theme in Outlook on the web. ```yaml @@ -2400,7 +2278,6 @@ Accept wildcard characters: False 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. - - $false: UM integration is disabled in Outlook on the web. This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). @@ -2456,7 +2333,6 @@ Accept wildcard characters: False 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. - - $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value. ```yaml @@ -2476,7 +2352,6 @@ Accept wildcard characters: False 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. - - $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value. ```yaml @@ -2530,7 +2405,6 @@ Accept wildcard characters: False 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. - - $false: Users can't edit supported documents in Outlook on the web. ```yaml @@ -2550,7 +2424,6 @@ Accept wildcard characters: False 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. - - $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -2572,7 +2445,6 @@ Accept wildcard characters: False 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. - - $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. 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). @@ -2594,9 +2466,7 @@ Accept wildcard characters: False 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. - - SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. - - Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it. ```yaml @@ -2618,7 +2488,6 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are: - $true: All supported attachment types are available for WebReady Document Viewing. This is the default value. - - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists). ```yaml @@ -2640,7 +2509,6 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are: - $true: WebReady Document Viewing is available in private computer sessions. This is the default value. - - $false: WebReady Document Viewing isn't available in private computer sessions. By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers. @@ -2664,7 +2532,6 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are: - $true: WebReady Document Viewing is available for public computer sessions. This is the default value. - - $false: WebReady Document Viewing isn't available for public computer sessions. In Exchange 2013, 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). @@ -2703,7 +2570,7 @@ Accept wildcard characters: False ### -WebReadyDocumentViewingSupportedMimeTypes 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.. +This is a read-only parameter that can't be modified; use the WebReadyMimeTypes parameter instead. ```yaml Type: MultiValuedProperty @@ -2724,30 +2591,21 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 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: - .doc - - .docx - - .dot - - .pdf - - .pps - - .ppt - - .pptx - - .rtf - - .xls - - .xlsx You can only remove or add values from within the list of supported file types (you can't add additional values). -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parameter is set to $false. Otherwise, all supported file types are available in WebReady Document Viewing. @@ -2770,28 +2628,20 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 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: - application/msword - - application/pdf - - application/vnd.ms-excel - - application/vnd.ms-powerpoint - - application/vnd.openxmlformats-officedocument.presentationml.presentation - - application/vnd.openxmlformats-officedocument.spreadsheetml.sheet - - application/vnd.openxmlformats-officedocument.wordprocessingml.document - - application/x-msexcel - - application/x-mspowerpoint You can only remove or add values from within the list of supported file types (you can't add additional values). -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parameter is set to $false. Otherwise, all supported MIME types are available in WebReady Document Viewing. @@ -2828,7 +2678,6 @@ Accept wildcard characters: False 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. - - $false: Integrated Windows authentication is disabled on the Outlook on the web virtual directory. This is the default value. ```yaml @@ -2881,12 +2730,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Set-PartnerApplication.md b/exchange/exchange-ps/exchange/Set-PartnerApplication.md similarity index 86% rename from exchange/exchange-ps/exchange/organization/Set-PartnerApplication.md rename to exchange/exchange-ps/exchange/Set-PartnerApplication.md index f9e9d8bc4d..157ce52607 100644 --- a/exchange/exchange-ps/exchange/organization/Set-PartnerApplication.md +++ b/exchange/exchange-ps/exchange/Set-PartnerApplication.md @@ -1,29 +1,30 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-partnerapplication -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-PartnerApplication ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is functional only in on-premises Exchange. -Use the Set-PartnerApplication cmdlet to configure partner application configurations. +Use the Set-PartnerApplication cmdlet to configure partner application configurations in on-premises Exchange organizations. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### ACSTrustApplication ``` -Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> [-ApplicationIdentifier <String>] [-Realm <String>] +Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> + [-ApplicationIdentifier <String>] + [-Realm <String>] [-AcceptSecurityIdentifierInformation <Boolean>] [-AccountType <SupportedAccountType>] [-ActAsPermissions <String[]>] @@ -34,12 +35,15 @@ Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> [-Application [-IssuerIdentifier <String>] [-LinkedAccount <UserIdParameter>] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### AuthMetadataUrl ``` -Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> [-AuthMetadataUrl <String>] [-TrustAnySSLCertificate] +Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> + [-AuthMetadataUrl <String>] + [-TrustAnySSLCertificate] [-AcceptSecurityIdentifierInformation <Boolean>] [-AccountType <SupportedAccountType>] [-ActAsPermissions <String[]>] @@ -50,12 +54,14 @@ Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> [-AuthMetadat [-IssuerIdentifier <String>] [-LinkedAccount <UserIdParameter>] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### RefreshAuthMetadata ``` -Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> [-RefreshAuthMetadata] +Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> + [-RefreshAuthMetadata] [-AcceptSecurityIdentifierInformation <Boolean>] [-AccountType <SupportedAccountType>] [-ActAsPermissions <String[]>] @@ -66,13 +72,14 @@ Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter> [-RefreshAuth [-IssuerIdentifier <String>] [-LinkedAccount <UserIdParameter>] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You can configure partner applications such as SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://docs.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. +You can configure partner applications such as SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -89,18 +96,15 @@ This example refreshes the auth metadata for the HRApp partner application. 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 - - ApplicationID (GUID value) - - Distinguished name (DN) - - GUID ```yaml Type: PartnerApplicationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -129,7 +133,6 @@ Accept wildcard characters: False 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 - - ConsumerAccount ```yaml @@ -178,7 +181,7 @@ Accept wildcard characters: False ``` ### -AppOnlyPermissions -This parameter is available only in Exchange 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -216,15 +219,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -268,7 +270,7 @@ Accept wildcard characters: False ``` ### -IssuerIdentifier -This parameter is available or functional only in Exchange Server 2013. +This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -338,7 +340,7 @@ Accept wildcard characters: False ### -RefreshAuthMetadata This parameter is available only in on-premises Exchange. -The RefreshAuthMetadata switch specifies that the auth metadata should be refreshed from the authorization server. +The RefreshAuthMetadata switch refreshes the auth metadata from the authorization server. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -356,7 +358,9 @@ Accept wildcard characters: False ### -TrustAnySSLCertificate This parameter is available only in on-premises Exchange. -The TrustAnySSLCertificate switch specifies whether Exchange should trust certificates issued by a certification authority (CA) not trusted by the server. We don't recommend using this switch in a production environment. +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. ```yaml Type: SwitchParameter @@ -378,7 +382,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -392,12 +396,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-PendingFederatedDomain.md b/exchange/exchange-ps/exchange/Set-PendingFederatedDomain.md similarity index 90% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Set-PendingFederatedDomain.md rename to exchange/exchange-ps/exchange/Set-PendingFederatedDomain.md index 3cee8ec541..a823ef0913 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-PendingFederatedDomain.md +++ b/exchange/exchange-ps/exchange/Set-PendingFederatedDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-pendingfederateddomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-PendingFederatedDomain @@ -19,19 +18,24 @@ The Set-PendingFederatedDomain cmdlet is used by the Exchange admin center to co The domains being added to the federation trust must exist as accepted domains in the Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-PendingFederatedDomain [[-Identity] <OrganizationIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-PendingAccountNamespace <SmtpDomain>] [-PendingDomains <SmtpDomain[]>] [-WhatIf] [<CommonParameters>] +Set-PendingFederatedDomain [[-Identity] <OrganizationIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-PendingAccountNamespace <SmtpDomain>] + [-PendingDomains <SmtpDomain[]>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION This cmdlet allows the Exchange admin center to save domains selected as the FederatedOrganizationIdentifier or federated domains when proof of domain ownership hasn't been completed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,11 +48,26 @@ This example adds the pending domains contoso.com and sales.contoso.com to the e ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -80,22 +99,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -PendingAccountNamespace The PendingAccountNamespace parameter specifies the pending domain that's used as the account namespace for the federation trust. @@ -149,12 +152,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Set-PerimeterConfig.md b/exchange/exchange-ps/exchange/Set-PerimeterConfig.md similarity index 79% rename from exchange/exchange-ps/exchange/organization/Set-PerimeterConfig.md rename to exchange/exchange-ps/exchange/Set-PerimeterConfig.md index 4c3650c8fb..d104c470f0 100644 --- a/exchange/exchange-ps/exchange/organization/Set-PerimeterConfig.md +++ b/exchange/exchange-ps/exchange/Set-PerimeterConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-perimeterconfig -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Set-PerimeterConfig @@ -17,15 +16,16 @@ This cmdlet is available only in the cloud-based service. Use the Set-PerimeterConfig cmdlet to modify the list of gateway server IP addresses that have been added to the cloud-based safelists. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-PerimeterConfig [-Confirm] [-GatewayIPAddresses <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] +Set-PerimeterConfig [[-Identity] <OrganizationIdParameter>] + [-Confirm] + [-GatewayIPAddresses <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -42,18 +42,33 @@ This example shows how to add an IP address to cloud-based safelists where the g ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -85,7 +100,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -99,12 +114,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-PhishSimOverridePolicy.md b/exchange/exchange-ps/exchange/Set-PhishSimOverridePolicy.md new file mode 100644 index 0000000000..95798fa9a6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-PhishSimOverridePolicy.md @@ -0,0 +1,182 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-PhishSimOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-PhishSimOverridePolicy cmdlet to modify third-party phishing simulation override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-PhishSimOverridePolicy [-Identity] <PolicyIdParameter> + [-Comment <String>] + [-Confirm] + [-DomainController <Fqdn>] + [-Enabled <Boolean>] + [-Force] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-PhishSimOverridePolicy -Identity PhishSimOverridePolicy -Enabled $false +``` + +This example disables the phishing simulation override policy. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-Place.md b/exchange/exchange-ps/exchange/Set-Place.md new file mode 100644 index 0000000000..aeffd3882a --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-Place.md @@ -0,0 +1,497 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-Place + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-Place cmdlet to update room mailboxes with additional metadata, which provides a better search and room suggestion experience. + +**Note**: In hybrid environments, this cmdlet doesn't work on the following properties on synchronized room mailboxes: City, CountryOrRegion, GeoCoordinates, Phone, PostalCode, State, or Street. To modify these properties (except GeoCoordinates on synchronized room mailboxes), use the Set-User or Set-Mailbox cmdlets in on-premises Exchange. + +**Note**: We recommend using this cmdlet with the EXO V3 module. Commands using Set-Place to change certain combinations of properties together can fail in older versions of the module. For more information about the EXO V3 module, see [About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-Place [-Identity] <RecipientIdParameter> + [-AudioDeviceName <String>] + [-Building <String>] + [-Capacity <System.Int32>] + [-City <String>] + [-Confirm] + [-CountryOrRegion <CountryInfo>] + [-DisplayDeviceName <String>] + [-Floor <System.Int32>] + [-FloorLabel <String>] + [-GeoCoordinates <GeoCoordinates>] + [-IsWheelChairAccessible <Boolean>] + [-Label <String>] + [-MTREnabled <Boolean>] + [-ParentId <String>] + [-ParentType <Microsoft.Exchange.Management.RecipientTasks.SetPlaceParentType>] + [-Phone <String>] + [-PostalCode <String>] + [-State <String>] + [-Street <String>] + [-Tags <String[]>] + [-VideoDeviceName <String>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-Place -Identity "Conference Room 01" -IsWheelChairAccessible $true -AudioDeviceName PolyCom -DisplayDeviceName "InFocus WXGA Projector" +``` + +The example adds the specified metadata to the room mailbox named Conference Room 01. + +### Example 2 +```powershell +Set-Place -Identity "Conference Room 02" -Building "Building 02" -Capacity 5 -CountryOrRegion ES -Floor 3 -FloorLabel "Human Resources" -Label Interviews +``` + +The example adds the specified metadata to the room mailbox named Conference Room 02. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: RecipientIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AudioDeviceName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Building +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Capacity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -City +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CountryOrRegion +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). + +The friendly name is returned in the CountryOrRegion property value by the Get-Place cmdlet, but you can use either the friendly name or the two-letter country code in filter operations. + +```yaml +Type: CountryInfo +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayDeviceName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Floor +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FloorLabel +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GeoCoordinates +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" +- Latitude, longitude, and altitude: For example, "47.644125;-122.122411;161.432" + +**Note**: If period separators don't work for you, use commas instead. + +```yaml +Type: GeoCoordinates +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsWheelChairAccessible +The IsWheelChairAccessible parameter specifies whether the room is wheelchair accessible. Valid values are: + +- $true: The room is wheelchair accessible. +- $false: The room is not wheelchair accessible. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Label +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MTREnabled +**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: + +- $true: The room is has a Teams room system. You can add the Teams room system to Microsoft Teams meetings when selecting to join a meeting with room audio. +- $false: The room is does not have a Teams room system. Users will join Teams meetings using their PC or mobile device audio instead of using room audio. This is the default value. + +For more information about Microsoft Teams Rooms, see [Microsoft Teams Rooms](https://learn.microsoft.com/microsoftteams/rooms/). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParentId +**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. + +Organizations that are onboarding Rooms and Workspaces to Microsoft Places need to use the ParentId and ParentType parameters in a Set-Place command so Microsoft Places works properly. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParentType +**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: + +- Floor +- Section + +Organizations that are onboarding Rooms and Workspaces to Microsoft Places need to use the ParentId and ParentType parameters in a Set-Place command so Microsoft Places works properly. + +```yaml +Type: Microsoft.Exchange.Management.RecipientTasks.SetPlaceParentType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Phone +The Phone parameter specifies the room's telephone number. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostalCode +The PostalCode parameter specifies the room's postal code. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The State parameter specifies the room's state or province. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Street +The Street parameter specifies the room's physical address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tags +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VideoDeviceName +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-PolicyConfig.md b/exchange/exchange-ps/exchange/Set-PolicyConfig.md new file mode 100644 index 0000000000..6455c497f6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-PolicyConfig.md @@ -0,0 +1,630 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-PolicyConfig + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-PolicyConfig cmdlet to modify the endpoint restrictions that are configured in the organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-PolicyConfig [[-Identity] <OrganizationIdParameter>] + [-CaseHoldPolicyLimit <Int32>] + [-ClassificationScheme <ClassificationScheme>] + [-ComplianceUrl <String>] + [-Confirm] + [-DlpAppGroups <PswsHashtable[]>] + [-DlpAppGroupsPsws <PswsHashtable[]>] + [-DlpExtensionGroups <PswsHashtable[]>] + [-DlpNetworkShareGroups <PswsHashtable>] + [-DlpPrinterGroups <PswsHashtable>] + [-DlpRemovableMediaGroups <PswsHashtable>] + [-DocumentIsUnsupportedSeverity <RuleSeverity>] + [-EnableAdvancedRuleBuilder <Boolean>] + [-EnableLabelCoauth <Boolean>] + [-EnableSpoAipMigration <Boolean>] + [-EndpointDlpGlobalSettings <PswsHashtable[]>] + [-EndpointDlpGlobalSettingsPsws <PswsHashtable[]>] + [-ExtendTeamsDlpPoliciesToSharePointOneDrive <Boolean>] + [-InformationBarrierMode <InformationBarrierMode>] + [-InformationBarrierPeopleSearchRestriction <InformationBarrierPeopleSearchRestriction>] + [-IsDlpSimulationOptedIn <Boolean>] + [-OnPremisesWorkload <Workload>] + [-ProcessingLimitExceededSeverity <RuleSeverity>] + [-PurviewLabelConsent <Boolean>] + [-ReservedForFutureUse <Boolean>] + [-RetentionForwardCrawl <Boolean>] + [-RuleErrorAction <PolicyRuleErrorAction>] + [-SenderAddressLocation <PolicySenderAddressLocation>] + [-SiteGroups <PswsHashtable[]>] + [-SiteGroupsPsws <PswsHashtable[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +{{ Add example code here }} +``` + +{{ Add example description here }} + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -CaseHoldPolicyLimit +{{ Fill CaseHoldPolicyLimit Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ClassificationScheme +{{ Fill ClassificationScheme Description }} + +```yaml +Type: ClassificationScheme +Parameter Sets: (All) +Aliases: +Accepted values: Default, V0_AggregatedOnly, V1_DetailedResults +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceUrl +{{ Fill ComplianceUrl Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpAppGroups +{{ Fill DlpAppGroups Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpAppGroupsPsws +{{ Fill DlpAppGroupsPsws Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpExtensionGroups +{{ Fill DlpExtensionGroups Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpNetworkShareGroups +{{ Fill DlpNetworkShareGroups Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpPrinterGroups +{{ Fill DlpPrinterGroups Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DlpRemovableMediaGroups +{{ Fill DlpRemovableMediaGroups Description }} + +```yaml +Type: PswsHashtable +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DocumentIsUnsupportedSeverity +{{ Fill DocumentIsUnsupportedSeverity Description }} + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Accepted values: Low, Medium, High, None, Informational, Information +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableAdvancedRuleBuilder +{{ Fill EnableAdvancedRuleBuilder Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableLabelCoauth +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. +- $false: Co-authoring support in Office desktop apps is disabled. + +Disabling co-authoring support in Office desktop apps in the organization has the following consequences: + +- For apps and services that support the new labeling metadata, they now revert to the original metadata format and location when labels are read or saved. +- The new metadata format and location for Office documents that was used while the setting was enabled will not be copied to the original format and location. As a result, this labeling information for unencrypted Word, Excel, and PowerPoint files will be lost. +- Co-authoring and AutoSave no longer work in your organization for labeled and encrypted documents. +- Sensitivity labels remain enabled for Office files in OneDrive and SharePoint. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSpoAipMigration +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. +- $false: Users can't apply your sensitivity labels in Office for the web. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpGlobalSettings +The EndpointDlpGlobalSettings parameter specifies the global endpoints. This parameter uses the following syntax: `@(@{"Setting"="<Setting>"; "Value"="<Value>}",@{"Setting"="<Setting>"; "Value"="<Value>"},...)`. + +The value of `<Setting>` is one of the supported values. + +Example values: + +- `@{"Setting"="PathExclusion"; "Value"="C:\Windows";}` +- `@{"Setting"="PathExclusion"; "Value"="%AppData%\Mozilla";}` +- `@{"Setting"="PathExclusion"; "Value"="C:\Users\*\Desktop";}` +- `@{"Setting"="UnallowedApp"="Notepad ++;"Executable"="notepad++"}` +- `@{"Setting"="UnallowedApp"="Executable"="cmd"}` +- `@{"Setting"="UnallowedBrowser"="Chrome";"Executable"="chrome"}` +- `@{"Setting"="CloudAppRestrictions"="Allow"}` +- `@{"Setting"="CloudAppRestrictionList"="1.1.2.2"}` +- `@{"Setting"="CloudAppRestrictionList"="subdomain.com"}` +- `@{"Setting"="CloudAppRestrictionList"="another.differentdomain.edu"}` +- `@{"Setting"="ShowEndpointJustificationDropdown"; "True";}` + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointDlpGlobalSettingsPsws +{{ Fill EndpointDlpGlobalSettingsPsws Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendTeamsDlpPoliciesToSharePointOneDrive +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 +- $false + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InformationBarrierMode +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. +- MultiSegment: Users in the organization can have 5000 segments and can be assigned up to 10 segments. For more information, see [Use multi-segment support in information barriers](https://learn.microsoft.com/purview/information-barriers-multi-segment). + +```yaml +Type: InformationBarrierMode +Parameter Sets: (All) +Aliases: +Accepted values: SingleSegment, MultiSegment +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InformationBarrierPeopleSearchRestriction +{{ Fill InformationBarrierPeopleSearchRestriction Description }} + +```yaml +Type: InformationBarrierPeopleSearchRestriction +Parameter Sets: (All) +Aliases: +Accepted values: Enabled, Disabled +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDlpSimulationOptedIn +{{ Fill IsDlpSimulationOptedIn Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnPremisesWorkload +{{ Fill OnPremisesWorkload Description }} + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProcessingLimitExceededSeverity +{{ Fill ProcessingLimitExceededSeverity Description }} + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Accepted values: Low, Medium, High, None, Informational, Information +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PurviewLabelConsent +{{ Fill PurviewLabelConsent Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReservedForFutureUse +{{ Fill ReservedForFutureUse Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionForwardCrawl +{{ Fill RetentionForwardCrawl Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RuleErrorAction +The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: + +- Ignore +- RetryThenBlock (This is the default value) + +```yaml +Type: PolicyRuleErrorAction +Parameter Sets: (All) +Aliases: +Accepted values: Ignore, RetryThenBlock +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SenderAddressLocation +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. +- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). +- HeaderOrEnvelope: Examine senders in the message header and the message envelope. + +```yaml +Type: PolicySenderAddressLocation +Parameter Sets: (All) +Aliases: +Accepted values: Header, Envelope, HeaderOrEnvelope +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteGroups +{{ Fill SiteGroups Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteGroupsPsws +{{ Fill SiteGroupsPsws Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-PolicyTipConfig.md b/exchange/exchange-ps/exchange/Set-PolicyTipConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-PolicyTipConfig.md rename to exchange/exchange-ps/exchange/Set-PolicyTipConfig.md index 39b9b639ff..16cd681d3b 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-PolicyTipConfig.md +++ b/exchange/exchange-ps/exchange/Set-PolicyTipConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-policytipconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-PolicyTipConfig @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-PolicyTipConfig cmdlet to modify custom Policy Tips in your organization. You can't modify built-in Policy Tips. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-PolicyTipConfig [-Identity] <PolicyTipConfigIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-Value <String>] [-WhatIf] [<CommonParameters>] +Set-PolicyTipConfig [-Identity] <PolicyTipConfigIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-Value <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,12 +53,9 @@ This example replaces the text of all custom Spanish Policy Tips with the value, ### -Identity 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://docs.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. - +- `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. - The value Url - - GUID - - Distinguished name (DN) ```yaml @@ -74,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -146,12 +145,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Set-PopSettings.md b/exchange/exchange-ps/exchange/Set-PopSettings.md similarity index 87% rename from exchange/exchange-ps/exchange/client-access/Set-PopSettings.md rename to exchange/exchange-ps/exchange/Set-PopSettings.md index 1dc13c40bd..a6e5d017f8 100644 --- a/exchange/exchange-ps/exchange/client-access/Set-PopSettings.md +++ b/exchange/exchange-ps/exchange/Set-PopSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-popsettings +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-PopSettings @@ -17,31 +16,47 @@ This cmdlet is available only in on-premises Exchange. Use the Set-PopSettings cmdlet to modify the configuration of the Microsoft Exchange POP3 service. This service exists on Exchange servers that have the Client Access server role installed, and is used by POP3 clients to connect to Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-PopSettings [-AuthenticatedConnectionTimeout <EnhancedTimeSpan>] [-Banner <String>] - [-CalendarItemRetrievalOption <CalendarItemRetrievalOptions>] [-Confirm] - [-DomainController <Fqdn>] [-EnableExactRFC822Size <Boolean>] - [-EnableGSSAPIAndNTLMAuth <Boolean>] [-EnforceCertificateErrors <Boolean>] - [-ExtendedProtectionPolicy <ExtendedProtectionTokenCheckingMode>] [-ExternalConnectionSettings <MultiValuedProperty>] - [-InternalConnectionSettings <MultiValuedProperty>] [-LogFileLocation <String>] +Set-PopSettings [-AuthenticatedConnectionTimeout <EnhancedTimeSpan>] + [-Banner <String>] + [-CalendarItemRetrievalOption <CalendarItemRetrievalOptions>] + [-Confirm] + [-DomainController <Fqdn>] + [-EnableExactRFC822Size <Boolean>] + [-EnableGSSAPIAndNTLMAuth <Boolean>] + [-EnforceCertificateErrors <Boolean>] + [-ExtendedProtectionPolicy <ExtendedProtectionTokenCheckingMode>] + [-ExternalConnectionSettings <MultiValuedProperty>] + [-InternalConnectionSettings <MultiValuedProperty>] + [-LogFileLocation <String>] [-LogFileRollOverSettings <LogFileRollOver>] - [-LoginType <LoginOptions>] [-LogPerFileSizeQuota <Unlimited>] - [-MaxCommandSize <Int32>] [-MaxConnectionFromSingleIP <Int32>] [-MaxConnections <Int32>] + [-LoginType <LoginOptions>] + [-LogPerFileSizeQuota <Unlimited>] + [-MaxCommandSize <Int32>] + [-MaxConnectionFromSingleIP <Int32>] + [-MaxConnections <Int32>] [-MaxConnectionsPerUser <Int32>] [-MessageRetrievalMimeFormat <MimeTextFormat>] - [-MessageRetrievalSortOrder <SortOrder>] [-OwaServerUrl <Uri>] - [-PreAuthenticatedConnectionTimeout <EnhancedTimeSpan>] [-ProtocolLogEnabled <Boolean>] - [-ProxyTargetPort <Int32>] [-Server <ServerIdParameter>] [-SSLBindings <MultiValuedProperty>] - [-SuppressReadReceipt <Boolean>] [-UnencryptedOrTLSBindings <MultiValuedProperty>] [-WhatIf] - [-X509CertificateName <String>] [<CommonParameters>] + [-MessageRetrievalSortOrder <SortOrder>] + [-OwaServerUrl <Uri>] + [-PreAuthenticatedConnectionTimeout <EnhancedTimeSpan>] + [-ProtocolLogEnabled <Boolean>] + [-ProxyTargetPort <Int32>] + [-Server <ServerIdParameter>] + [-SSLBindings <MultiValuedProperty>] + [-SuppressReadReceipt <Boolean>] + [-UnencryptedOrTLSBindings <MultiValuedProperty>] + [-WhatIf] + [-X509CertificateName <String>] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -121,14 +136,11 @@ Accept wildcard characters: False ``` ### -CalendarItemRetrievalOption -The CalendarItemRetrievalOption parameter specifies how calendar items are presented to POP3 clients.. Valid values are: +The CalendarItemRetrievalOption parameter specifies how calendar items are presented to POP3 clients. Valid values are: - 0 or iCalendar. This is the default value. - - 1 or IntranetUrl. - - 2 or InternetUrl. - - 3 or Custom. If you specify 3 or Custom, you need to specify a value for the OwaServerUrl parameter. @@ -149,8 +161,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -186,7 +197,6 @@ Accept wildcard characters: False 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. - - $false: Use an estimated message size. This is the default value. ```yaml @@ -206,7 +216,6 @@ Accept wildcard characters: False 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. - - $false: NTLM for POP3 connections is disabled. ```yaml @@ -226,7 +235,6 @@ Accept wildcard characters: False 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. - - $false: The server doesn't deny POP3 connections based on certificate errors. This is the default value. ```yaml @@ -246,9 +254,7 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used only if it's supported by the incoming POP3 connection. If it's not, Extended Protection for Authentication isn't used. - - Require: Extended Protection for Authentication is required for all POP3 connections. If the incoming POP3 connection doesn't support it, the connection is rejected. Extended Protection for Authentication enhances the protection and handling of credentials by Integrated Windows authentication (also known as NTLM), so we strongly recommend that you use it if it's supported by your clients (default installations of Windows 7 or later and Windows Server 2008 R2 or later support it). @@ -269,13 +275,13 @@ Accept wildcard characters: False ### -ExternalConnectionSettings 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\>:[\<TLS | SSL\>]. The encryption method value is optional (blank indicates unencrypted connections). +This parameter uses the syntax `HostName:Port:[<TLS | SSL>]`. The encryption method value is optional (blank indicates unencrypted connections). The default value is blank ($null), which means no external POP3 connection settings are configured. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The combination of encryption methods and ports that are specified for this parameter need to match the corresponding encryption methods and ports that are specified by the SSLBindings and UnencryptedOrTLSBindings parameters. @@ -295,13 +301,13 @@ Accept wildcard characters: False ### -InternalConnectionSettings 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\>:[\<TLS | SSL\>]. The encryption method value is optional (blank indicates unencrypted connections). +This parameter uses the syntax `HostName:Port:[<TLS | SSL>]`. The encryption method value is optional (blank indicates unencrypted connections). -The default value is \<ServerFQDN\>:995:SSL,\<ServerFQDN\>:110:TLS. +The default value is `<ServerFQDN>:995:SSL,<ServerFQDN>:110:TLS`. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The combination of encryption methods and ports that are specified for this parameter need to match the corresponding encryption methods and ports that are specified by the SSLBindings and UnencryptedOrTLSBindings parameters. @@ -339,12 +345,9 @@ Accept wildcard characters: False ### -LogFileRollOverSettings The LogFileRollOverSettings parameter defines how frequently POP3 protocol logging creates a new log file. Valid values are: -- 1 or Hourly. - -- 2 or Daily. This is the default value. - +- 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016. +- 2 or Daily. This is the default value in Exchange 2013 and Exchange 2010. - 3 or Weekly. - - 4 or Monthly. This parameter is only meaningful when the LogPerFileSizeQuota parameter value is 0, and the ProtocolLogEnabled parameter value is $true. @@ -366,9 +369,7 @@ Accept wildcard characters: False The LoginType parameter specifies the authentication method for POP3 connections. Valid values are: - 1 or PlainTextLogin. - - 2 or PlainTextAuthentication. - - 3 or SecureLogin. This is the default value. ```yaml @@ -390,13 +391,9 @@ The LogPerFileSizeQuota parameter specifies the maximum size of a POP3 protocol When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -486,17 +483,11 @@ Accept wildcard characters: False The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages. Valid values are: - 0 or TextOnly. - - 1 or HtmlOnly. - - 2 or HtmlAndTextAlternative. - - 3 or TextEnrichedOnly. - - 4 or TextEnrichedAndTextAlternative. - - 5 or BestBodyFormat. This is the default value. - - 6 or Tnef. ```yaml @@ -516,7 +507,6 @@ Accept wildcard characters: False The MessageRetrievalSortOrder parameter specifies how retrieved messages are sorted. Valid values are: - 0 or Ascending. This is the default value. - - 1 or Descending. ```yaml @@ -572,7 +562,6 @@ Accept wildcard characters: False The ProtocolLogEnabled parameter specifies whether to enable protocol logging for POP3. Valid values are: - $true: POP3 protocol logging is enabled. - - $false: POP3 protocol logging is disabled. This is the default value. ```yaml @@ -608,11 +597,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -631,13 +617,13 @@ Accept wildcard characters: False ``` ### -SSLBindings -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 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. +The default value is `[::]:995,0.0.0.0:995`. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -656,7 +642,6 @@ Accept wildcard characters: False 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. - - $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This is the default value. ```yaml @@ -673,13 +658,13 @@ Accept wildcard characters: False ``` ### -UnencryptedOrTLSBindings -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 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. +The default value is `[::]:110, 0.0.0.0:110`. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -737,12 +722,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-PowerShellVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-PowerShellVirtualDirectory.md new file mode 100644 index 0000000000..16c3da7808 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-PowerShellVirtualDirectory.md @@ -0,0 +1,309 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-PowerShellVirtualDirectory + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Set-PowerShellVirtualDirectory cmdlet to modify existing Windows PowerShell virtual directories that are used in Internet Information Services (IIS) on Exchange servers. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-PowerShellVirtualDirectory [-Identity] <VirtualDirectoryIdParameter> + [-BasicAuthentication <Boolean>] + [-CertificateAuthentication <Boolean>] + [-Confirm] + [-DomainController <Fqdn>] + [-ExtendedProtectionFlags <MultiValuedProperty>] + [-ExtendedProtectionSPNList <MultiValuedProperty>] + [-ExtendedProtectionTokenChecking <ExtendedProtectionTokenCheckingMode>] + [-ExternalUrl <Uri>] + [-InternalUrl <Uri>] + [-RequireSSL <Boolean>] + [-WhatIf] + [-WindowsAuthentication <Boolean>] + [<CommonParameters>] +``` + +## DESCRIPTION +Although it's possible to modify a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-PowerShellVirtualDirectory "Contoso (default Web site)" -ExternalUrl "https://www.contoso.com/powershell" +``` + +This example modifies the external URL of the Contoso Windows PowerShell virtual directory. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. + +```yaml +Type: VirtualDirectoryIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BasicAuthentication +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. +- $false: Basic authentication is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CertificateAuthentication +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedProtectionFlags +The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: + +- None: This is the default setting. +- AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. +- NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. +- Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. +- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedProtectionSPNList +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. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedProtectionTokenChecking +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. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. + +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. + +```yaml +Type: ExtendedProtectionTokenCheckingMode +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InternalUrl +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireSSL +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WindowsAuthentication +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. +- $false: Integrated Windows authentication is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-ProtectionAlert.md b/exchange/exchange-ps/exchange/Set-ProtectionAlert.md new file mode 100644 index 0000000000..c1875d6ea6 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ProtectionAlert.md @@ -0,0 +1,612 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ProtectionAlert + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-ProtectionAlert cmdlet to modify alert policies in the Microsoft Purview compliance portal. + +**Note**: You can't use this cmdlet to edit default alert policies. You can only modify alerts that you created using the New-ProtectionAlert cmdlet. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ProtectionAlert [-Identity] <ComplianceRuleIdParameter> + [-AggregationType <AlertAggregationType>] + [-AlertBy <MultiValuedProperty>] + [-AlertFor <MultiValuedProperty>] + [-Category <AlertRuleCategory>] + [-Comment <String>] + [-Confirm] + [-Description <String>] + [-Disabled <Boolean>] + [-Filter <String>] + [-NotificationCulture <CultureInfo>] + [-NotificationEnabled <Boolean>] + [-NotifyUser <MultiValuedProperty>] + [-NotifyUserOnFilterMatch <Boolean>] + [-NotifyUserSuppressionExpiryDate <DateTime>] + [-NotifyUserThrottleThreshold <Int32>] + [-NotifyUserThrottleWindow <Int32>] + [-Operation <MultiValuedProperty>] + [-PrivacyManagementScopedSensitiveInformationTypes <MultiValuedProperty>] + [-PrivacyManagementScopedSensitiveInformationTypesForCounting <MultiValuedProperty>] + [-PrivacyManagementScopedSensitiveInformationTypesThreshold <System.UInt64>] + [-Severity <RuleSeverity>] + [-Threshold <Int32>] + [-TimeWindow <Int32>] + [-VolumeThreshold <System.UInt64>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ProtectionAlert -Identity "Content search deleted" -Severity High +``` + +This example sets the Severity of the detection to High for the specified alert policy. + +### Example 2 +```powershell +Set-ProtectionAlert -Identity "Content search deleted" -NotifyUserOnFilterMatch:$true -AggregationType SimpleAggregation -Threshold 10 -TimeWindow 120 +``` + +This example modifies an alert so that even though it's configured for aggregated activity, a notification is triggered during a match for the activity. A threshold of 10 detections and a TimeWindow of two hours are also configured in the same command. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AggregationType +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. +- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. +- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. + +```yaml +Type: AlertAggregationType +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlertBy +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. +- Malware: Valid values are Mail.Recipient or Mail.ThreatName. + +You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlertFor +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Category +The Category parameter specifies a category for the alert policy. Valid values are: + +- AccessGovernance +- ComplianceManager +- DataGovernance +- MailFlow +- Others +- PrivacyManagement +- Supervision +- ThreatManagement + +When an activity occurs that matches the conditions of the alert policy, the alert that's generated is tagged with the category that's specified by this parameter. This allows you to track and manage alerts that have the same category setting + +```yaml +Type: AlertRuleCategory +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Disabled +The Disabled parameter enables or disables the alert policy. Valid values are: + +- $true: The alert policy is disabled. +- $false: The alert policy is enabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +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. +- Property is a filterable property. +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). + +You can chain multiple search criteria together using the `-and` logical operator (for example, `"Criteria1 -and Criteria2"`). + +For detailed information about OPATH filters in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +The filterable properties are: + +Activity + +- Activity.ClientIp +- Activity.CreationTime +- Activity.Item +- Activity.ItemType +- Activity.Operation +- Activity.ResultStatus +- Activity.Scope +- Activity.SiteUrl +- Activity.SourceFileExtension +- Activity.SourceFileName +- Activity.TargetUserOrGroupType +- Activity.UserAgent +- Activity.UserId +- Activity.UserType +- Activity.Workload + +Malware + +- Mail:AttachmentExtensions +- Mail:AttachmentNames +- Mail:CreationTime +- Mail:DeliveryStatus +- Mail:Direction +- Mail:From +- Mail:FromDomain +- Mail:InternetMessageId +- Mail:IsIntraOrgSpoof +- Mail:IsMalware +- Mail:IsSpam +- Mail:IsThreat +- Mail:Language +- Mail:Recipient +- Mail:Scl +- Mail:SenderCountry +- Mail:SenderIpAddress +- Mail:Subject +- Mail:TenantId +- Mail:ThreatName + +You can specify multiple criteria by using the -and comparison operator. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationCulture +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). + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationEnabled +{{ Fill NotificationEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUser +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserOnFilterMatch +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). +- $false: Alerts are triggered according to the specified aggregation type. This is the default value. + +You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserSuppressionExpiryDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserThrottleThreshold +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. +- The value $null. This is the default value (no maximum number of notifications for an alert). + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyUserThrottleWindow +The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: + +- An integer. +- The value $null. This is the default value (no interval for notification throttling). + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Operation +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. + +You can only use this parameter when the ThreatType parameter has the value Activity. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyManagementScopedSensitiveInformationTypes +{{ Fill PrivacyManagementScopedSensitiveInformationTypes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyManagementScopedSensitiveInformationTypesForCounting +{{ Fill PrivacyManagementScopedSensitiveInformationTypesForCounting Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivacyManagementScopedSensitiveInformationTypesThreshold +{{ Fill PrivacyManagementScopedSensitiveInformationTypesThreshold Description }} + +```yaml +Type: System.UInt64 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Severity +The Severity parameter specifies the severity of the detection. Valid values are: + +- Low (This is the default value) +- Medium +- High + +```yaml +Type: RuleSeverity +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Threshold +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeWindow +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VolumeThreshold +{{ Fill VolumeThreshold Description }} + +```yaml +Type: System.UInt64 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-PublicFolder.md b/exchange/exchange-ps/exchange/Set-PublicFolder.md similarity index 90% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Set-PublicFolder.md rename to exchange/exchange-ps/exchange/Set-PublicFolder.md index 3b02ba0af3..d2f0376645 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-PublicFolder.md +++ b/exchange/exchange-ps/exchange/Set-PublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-publicfolder +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-PublicFolder @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-PublicFolder cmdlet to set the attributes of public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,6 +26,7 @@ Set-PublicFolder [-Identity] <PublicFolderIdParameter> [-Confirm] [-DomainController <Fqdn>] [-EformsLocaleId <CultureInfo>] + [-Force] [-HiddenFromAddressListsEnabled <Boolean>] [-IssueWarningQuota <Unlimited>] [-LocalReplicaAgeLimit <EnhancedTimeSpan>] @@ -46,11 +46,12 @@ Set-PublicFolder [-Identity] <PublicFolderIdParameter> [-UseDatabaseQuotaDefaults <Boolean>] [-UseDatabaseReplicationSchedule <Boolean>] [-UseDatabaseRetentionDefaults <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -78,7 +79,7 @@ In Exchange 2010, this example sets the folder to replicate only on weekends. ## PARAMETERS ### -Identity -The Identity parameter specifies the name and path of the public folder you want to modify. A valid value uses the format: \\\<Level1\>\\\<Level2\>\\...\\\<LevelN\>\\\<PublicFolder\>. For example, "\\Customer Discussion" or "\\Engineering\\Customer Discussion". +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 @@ -114,8 +115,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -150,7 +150,7 @@ Accept wildcard characters: False ``` ### -EformsLocaleId -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://go.microsoft.com/fwlink/p/?linkId=184859). +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 @@ -166,7 +166,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -182,7 +184,7 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled -This parameter is available or functional only in 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. @@ -207,13 +209,9 @@ The default value is unlimited, which is 2 terabytes. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -234,7 +232,7 @@ Accept wildcard characters: False ``` ### -LocalReplicaAgeLimit -This parameter is available or functional only in 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. @@ -293,13 +291,9 @@ The MaxItemSize parameter specifies the maximum size for posted items. Items lar When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -341,23 +335,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -411,13 +396,9 @@ The ProhibitPostQuota parameter specifies the size of a public folder at which u When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -438,17 +419,15 @@ Accept wildcard characters: False ``` ### -Replicas -This parameter is available or functional only in 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: - Name - - Distinguished name (DN) - - GUID -You can specify multiple values separated by commas. If the values contain spaces, use the following syntax: \"<Value1\>","\<Value2\>",..."\<ValueN\>". +You can specify multiple values separated by commas. If the values contain spaces, use the following syntax: `"Value1","Value2",..."ValueN"`. ```yaml Type: DatabaseIdParameter[] @@ -464,18 +443,16 @@ Accept wildcard characters: False ``` ### -ReplicationSchedule -This parameter is available or functional only in Exchange Server 2010 +This parameter is available only in Exchange Server 2010 The ReplicationSchedule parameter specifies the replication schedule for the folder. -The syntax for this parameter is: StartDay.Hour:Minute \[AM/PM\]-EndDay.Hour:Minute \[AM/PM\]. +The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -487,9 +464,7 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" ```yaml @@ -524,16 +499,13 @@ Accept wildcard characters: False ``` ### -Server -This parameter is available or functional only in 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -552,7 +524,7 @@ Accept wildcard characters: False ``` ### -UseDatabaseAgeDefaults -This parameter is available or functional only in Exchange Server 2010 +This parameter is available only in Exchange Server 2010 The UseDatabaseAgeDefaults parameter specifies whether to use the database age limit. @@ -570,7 +542,7 @@ Accept wildcard characters: False ``` ### -UseDatabaseQuotaDefaults -This parameter is available or functional only in Exchange Server 2010 +This parameter is available only in Exchange Server 2010 The UseDatabaseQuotaDefaults parameter specifies whether to use the public store quota limits. @@ -588,7 +560,7 @@ Accept wildcard characters: False ``` ### -UseDatabaseReplicationSchedule -This parameter is available or functional only in Exchange Server 2010 +This parameter is available only in Exchange Server 2010 The UseDatabaseReplicationSchedule parameter specifies whether to use the public folder replication schedule. @@ -606,7 +578,7 @@ Accept wildcard characters: False ``` ### -UseDatabaseRetentionDefaults -This parameter is available or functional only in Exchange Server 2010 +This parameter is available only in Exchange Server 2010 The UseDatabaseRetentionDefaults parameter specifies whether to use the database retention defaults. @@ -644,12 +616,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-PublicFolderDatabase.md b/exchange/exchange-ps/exchange/Set-PublicFolderDatabase.md similarity index 95% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Set-PublicFolderDatabase.md rename to exchange/exchange-ps/exchange/Set-PublicFolderDatabase.md index 76003963cc..85ad17feda 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-PublicFolderDatabase.md +++ b/exchange/exchange-ps/exchange/Set-PublicFolderDatabase.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-publicfolderdatabase +online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfolderdatabase applicable: Exchange Server 2010 title: Set-PublicFolderDatabase schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-PublicFolderDatabase @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-PublicFolderDatabase cmdlet to set attributes of public folder databases. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -44,11 +43,12 @@ Set-PublicFolderDatabase [-Identity] <DatabaseIdParameter> [-ReplicationSchedule <Schedule>] [-RetainDeletedItemsUntilBackup <Boolean>] [-UseCustomReferralServerList <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,9 +79,7 @@ This example prevents the deleted items in the public folder database PFDB01 fro 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 - - Distinguished name (DN) - - GUID ```yaml @@ -148,8 +146,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -266,14 +263,12 @@ Accept wildcard characters: False ### -MaintenanceSchedule The MaintenanceSchedule parameter specifies the store maintenance schedule. -The syntax for this parameter is: StartDay.Hour:Minute \[AM/PM\]-EndDay.Hour:Minute \[AM/PM\]. +The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -284,9 +279,7 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" ```yaml @@ -369,14 +362,12 @@ Accept wildcard characters: False ### -QuotaNotificationSchedule 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\]. +The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -387,9 +378,7 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" ```yaml @@ -413,11 +402,8 @@ A valid value is a number up to 2 gigabytes (2147482624 bytes). The default valu When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -454,14 +440,12 @@ Accept wildcard characters: False ### -ReplicationSchedule 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\]. +The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -473,9 +457,7 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" ```yaml @@ -546,12 +528,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/move-and-migration/Set-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/Set-PublicFolderMigrationRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/move-and-migration/Set-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/exchange/Set-PublicFolderMigrationRequest.md index 0645d74d42..7c4de5b3bf 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Set-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Set-PublicFolderMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-publicfoldermigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-PublicFolderMigrationRequest @@ -19,7 +18,7 @@ Use the Set-PublicFolderMigrationRequest cmdlet to modify serial public folder m **Note**: Support for serial migration of public folders ended in Exchange 2013 Cumulative Update 8 (CU8), and the cmdlets are no longer available in Exchange Online. Instead, use the corresponding **\*-MigrationBatch** and **\*-PublicFolderMailboxMigration\*** cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -34,14 +33,12 @@ Set-PublicFolderMigrationRequest [-Identity] <PublicFolderMigrationRequestIdPara [-DomainController <Fqdn>] [-InternalFlags <InternalMrsFlag[]>] [-LargeItemLimit <Unlimited>] - [-OutlookAnywhereHostName <Fqdn>] [-PreventCompletion <Boolean>] [-Priority <RequestPriority>] - [-RemoteMailboxLegacyDN <String>] - [-RemoteMailboxServerLegacyDN <String>] [-RequestExpiryInterval <Unlimited>] [-SkipMerging <SkippableMergeComponent[]>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Rehome @@ -51,13 +48,14 @@ Set-PublicFolderMigrationRequest [-Identity] <PublicFolderMigrationRequestIdPara [-DomainController <Fqdn>] [-PreventCompletion <Boolean>] [-RequestExpiryInterval <Unlimited>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION You can pipe output of Get-PublicFolderMigrationRequestStatistics, Get-PublicFolderMigrationRequest, or Get-PublicFolder to this cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,7 +72,6 @@ This example changes the setting of the PublicFolderMigration migration request The Identity parameter specifies the migration request that you want to modify. You can use the following values: - Name - - RequestGUID ```yaml @@ -91,7 +88,9 @@ Accept wildcard characters: False ``` ### -RehomeRequest -The RehomeRequest parameter specifies to the Microsoft Exchange Mailbox Replication service (MRS) that the request needs to be moved to the same database as the public folder being migrated. This parameter is used primarily for debugging purposes. +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. ```yaml Type: SwitchParameter @@ -177,8 +176,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -231,9 +229,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -256,7 +253,6 @@ Accept wildcard characters: False 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. - - $false: The migration request is run and allowed to complete. This is the default value. ```yaml @@ -276,19 +272,12 @@ Accept wildcard characters: False 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 - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml @@ -308,7 +297,6 @@ Accept wildcard characters: False 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. - - If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. @@ -365,12 +353,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Set-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/Set-PublicFolderMoveRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/move-and-migration/Set-PublicFolderMoveRequest.md rename to exchange/exchange-ps/exchange/Set-PublicFolderMoveRequest.md index 6c32397ddc..f63c7353d0 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Set-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/exchange/Set-PublicFolderMoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-publicfoldermoverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-PublicFolderMoveRequest @@ -17,23 +16,30 @@ This cmdlet is available only in on-premises Exchange. Use the Set-PublicFolderMoveRequest cmdlet to change a public folder move request after the move request has been created. You can use the Set-PublicFolderMoveRequest cmdlet to recover from a failed move request. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter> [-AcceptLargeDataLoss] - [-BadItemLimit <Unlimited>] [-CompletedRequestAgeLimit <Unlimited>] [-Confirm] [-DomainController <Fqdn>] - [-InternalFlags <InternalMrsFlag[]>] [-LargeItemLimit <Unlimited>] +Set-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter> + [-AcceptLargeDataLoss] + [-BadItemLimit <Unlimited>] + [-CompletedRequestAgeLimit <Unlimited>] + [-Confirm] + [-DomainController <Fqdn>] + [-InternalFlags <InternalMrsFlag[]>] + [-LargeItemLimit <Unlimited>] [-Priority <RequestPriority>] - [-SuspendWhenReadyToComplete <Boolean>] [-WhatIf] [-RequestExpiryInterval <Unlimited>] + [-RequestExpiryInterval <Unlimited>] + [-SuspendWhenReadyToComplete <Boolean>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION You can pipeline the Set-PublicFolderMoveRequest cmdlet from the Get-PublicFolderMoveRequestStatistics or Get-PublicFolderMoveRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -117,8 +123,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -171,9 +176,8 @@ The LargeItemLimit parameter specifies the maximum number of large items that ar For more information about maximum message size values, see the following topics: -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) +- Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) +- Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) 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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. @@ -196,19 +200,12 @@ Accept wildcard characters: False 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 - - Lower - - Low - - Normal: This is the default value. - - High - - Higher - - Highest - - Emergency ```yaml @@ -224,14 +221,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SuspendWhenReadyToComplete -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. +### -RequestExpiryInterval +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. +- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. + +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. + +When you use the value Unlimited, the completed request isn't automatically removed. ```yaml -Type: Boolean +Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -240,13 +244,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -SuspendWhenReadyToComplete +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: SwitchParameter +Type: Boolean Parameter Sets: (All) -Aliases: wi +Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -256,22 +260,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RequestExpiryInterval -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. - -- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. - -To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. - -When you use the value Unlimited, the completed request isn't automatically removed. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: Unlimited +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -285,12 +281,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-QuarantinePermissions.md b/exchange/exchange-ps/exchange/Set-QuarantinePermissions.md new file mode 100644 index 0000000000..124bd14378 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-QuarantinePermissions.md @@ -0,0 +1,241 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-QuarantinePermissions + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +**Note**: Instead of using this cmdlet to set quarantine policy permissions, we recommend using the EndUserQuarantinePermissionsValue parameter on the New-QuarantinePolicy and Set-QuarantinePolicy cmdlets. + +Use the Set-QuarantinePermissions cmdlet to modify quarantine permissions objects that were created by the New-QuarantinePermissions and stored as a variable in the current PowerShell session. You use the variable as a value for the EndUserQuarantinePermission parameter on the New-QuarantinePolicy or Set-QuarantinePolicy cmdlets in the same PowerShell session. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-QuarantinePermissions -QuarantinePermissionsObject <QuarantinePermissions> + [[-PermissionToAllowSender] <Boolean>] + [[-PermissionToBlockSender] <Boolean>] + [[-PermissionToDelete] <Boolean>] + [[-PermissionToDownload] <Boolean>] + [[-PermissionToPreview] <Boolean>] + [[-PermissionToRelease] <Boolean>] + [[-PermissionToRequestRelease] <Boolean>] + [[-PermissionToViewHeader] <Boolean>] + [<CommonParameters>] +``` + +## DESCRIPTION +To see the current value of the permissions object that you want to modify, run the variable name as a command. For example, run the command `$Perms` to see the quarantine policy permissions stored in the `$Perms` variable. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-QuarantinePermissions -QuarantinePermissionsObject $Perms -PermissionToRequestRelease $true -PermissionToRelease $false +``` + +This example modifies the quarantine policy permissions in the exiting `$Perms` variable that was previously created using the New-QuarantinePermissions cmdlet in the same PowerShell session (the `$Perms` variable is still available and populated). + +In the same PowerShell session, you can use `$Perms` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command. + +## PARAMETERS + +### -QuarantinePermissionsObject +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 <permissions>`, use the value `$Perms` for this parameter. + +```yaml +Type: QuarantinePermissions +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 9 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToAllowSender +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. +- $false: Allow sender isn't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 1 +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToBlockSender +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. +- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToDelete +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. +- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToDownload +The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: + +- $true: The permission is enabled. +- $false: The permission is disabled. This is the default value. + +Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 4 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToPreview +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. +- $false: Preview message isn't available for affected messages in quarantine. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 5 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToRelease +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. +- $false: Release message isn't available in quarantine notifications for affected messages, and Release and Release email aren't available for affected messages in quarantine. + +Don't set this parameter and the _PermissionToRequestRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 6 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToRequestRelease +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. +- $false: Request Release isn't available in quarantine notifications for affected messages, and Request release isn't available for affected messages in quarantine. + +Don't set this parameter and the _PermissionRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 7 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PermissionToViewHeader +The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: + +- $true: The permission is enabled. +- $false: The permission is disabled. This is the default value. + +Currently, this value has no effect on available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 8 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/p/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-QuarantinePolicy.md b/exchange/exchange-ps/exchange/Set-QuarantinePolicy.md new file mode 100644 index 0000000000..796d65b9a1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-QuarantinePolicy.md @@ -0,0 +1,551 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-QuarantinePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-QuarantinePolicy cmdlet to modify quarantine policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-QuarantinePolicy [-Identity] <QuarantineTagIdParameter> + [-AdminNotificationFrequencyInDays <Int32>] + [-AdminNotificationLanguage <EsnLanguage>] + [-AdminNotificationsEnabled <Boolean>] + [-AdminQuarantinePermissionsList <MultiValuedProperty>] + [-Confirm] + [-CustomDisclaimer <String>] + [-DomainController <Fqdn>] + [-EndUserQuarantinePermissions <QuarantinePermissions>] + [-EndUserQuarantinePermissionsValue <Int32>] + [-EndUserSpamNotificationCustomFromAddress <String>] + [-EndUserSpamNotificationFrequency <TimeSpan>] + [-EndUserSpamNotificationFrequencyInDays <Int32>] + [-EndUserSpamNotificationLanguage <EsnLanguage>] + [-EsnCustomSubject <MultiValuedProperty>] + [-ESNEnabled <Boolean>] + [-IgnoreDehydratedFlag] + [-IncludeMessagesFromBlockedSenderAddress <Boolean>] + [-MultiLanguageCustomDisclaimer <MultiValuedProperty>] + [-MultiLanguageSenderName <MultiValuedProperty>] + [-MultiLanguageSetting <MultiValuedProperty>] + [-OrganizationBrandingEnabled <Boolean>] + [-QuarantineRetentionDays <Int32>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You can't modify the built-in quarantine policies named AdminOnlyAccessPolicy, DefaultFullAccessPolicy, or DefaultFullAccessWithNotificationPolicy. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-QuarantinePolicy -Identity CustomAccess -EndUserQuarantinePermissionsValue 1 +``` + +This example configures the permissions in the quarantine policy named CustomAccess that allows users to delete quarantined messages only. + +### Example 2 +```powershell +Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy -MultiLanguageSetting ('English','ChineseSimplified','French') -MultiLanguageCustomDisclaimer ('For more information, contact the Help Desk.','有关更多信息，请联系服务台','Pour plus d''informations, contactez le service d''assistance.') -ESNCustomSubject ('You have quarantined messages','您有隔离邮件','Vous avez des messages en quarantaine') -MultiLanguageSenderName ('Contoso administrator','Contoso管理员','Administrateur Contoso') -EndUserSpamNotificationCustomFromAddress aashutosh@contso.onmicrosoft.com -OrganizationBrandingEnabled $true -EndUserSpamNotificationFrequency 04:00:00 +``` + +This example modifies the global settings for quarantine notifications (formerly known as end-user spam notification settings): + +- Quarantine notifications are customized for English, Chinese, and French. Extra quotation marks are required in the French MultiLanguageCustomDisclaimer value as escape characters for the quotation mark characters in the text. +- The existing user aashutosh@contso.onmicrosoft.com is used as the quarantine notification sender. +- The previously configured custom logo replaces the default Microsoft logo. +- The frequency of quarantine notifications is changed to 4 hours. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: QuarantineTagIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AdminNotificationFrequencyInDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminNotificationLanguage +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 +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminNotificationsEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminQuarantinePermissionsList +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomDisclaimer +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserQuarantinePermissions +**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. + +For example, run the following command to store the required permissions in a variable: `$Perms = New-QuarantinePermissions <permissions>`. In the same PowerShell session, use the value `$Perms` for this parameter. + +```yaml +Type: QuarantinePermissions +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserQuarantinePermissionsValue +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): + +- PermissionToViewHeader: The value 0 doesn't hide the **View message header** action in quarantine. If the message is visible in quarantine, the action is always available for the message. +- PermissionToDownload: This permission is not used (the value 0 or 1 does nothing). +- PermissionToAllowSender +- PermissionToBlockSender +- PermissionToRequestRelease: Don't set this permission and PermissionToRelease to the value 1. Set one value to 1 and the other value to 0, or set both values to 0. +- PermissionToRelease: Don't set this permission and PermissionToRequestRelease to value 1. Set one value to 1 and the other value to 0, or set both values to 0. This permission isn't honored for messages that were quarantined as malware or high confidence phishing. If the quarantine policy gives users this permission, users are allowed to request the release of their quarantined malware or high confidence phishing messages as if PermissionToRequestRelease was selected instead. +- PermissionToPreview +- PermissionToDelete + +The values for the preset end-user permission groups are described in the following list: + +- No access: Binary = 0000000, so use the decimal value 0. +- Limited access: Binary = 00101011, so use the decimal value 43. +- Full access: Binary = 00100111, so use the decimal value 39. + +For custom permissions, get the binary value that corresponds to the permissions you want. Convert the binary value to a decimal value to use. Don't use the binary value for this parameter. + +**Note**: If the value of this parameter is 0 (No access) and the value of the ESNEnabled parameter is $true, users can view their messages in quarantine, but the only available action for the messages is **View message header**. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationCustomFromAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationFrequency +The EndUserSpamNotificationFrequency parameter species how often quarantine notifications are sent to users. Valid values are: + +- 04:00:00 (4 hours) +- 1.00:00:00 (1 day) +- 7.00:00:00 (7 days) + +```yaml +Type: TimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationFrequencyInDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndUserSpamNotificationLanguage +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 +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EsnCustomSubject +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. + +To modify an existing value and preserve other values, you need to specify all existing values and the new value in the existing order. + +This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global quarantine policy settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: MultiValuedProperty +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ESNEnabled +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. +- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value. + +**Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can view their messages in quarantine, but the only available action for the messages is **View message header**. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDehydratedFlag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeMessagesFromBlockedSenderAddress +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. +- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiLanguageCustomDisclaimer +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. + +To modify an existing value and preserve other values, you need to specify all existing values and the new value in the existing order. + +This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global quarantine policy settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiLanguageSenderName +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. + +To modify an existing value and preserve other values, you need to specify all existing values and the new value in the existing order. + +This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MultiLanguageSetting +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. + +You can specify multiple value separated by commas using the syntax: `('value1',''value2',...'valueN')`. The default value is Default, which means quarantine notifications use the default language of the cloud-based organization. + +For each language that you specify, you can specify a unique value for the MultiLanguageCustomDisclaimer and MultiLanguageSenderName parameters. Be sure to align the corresponding MultiLanguageSetting, MultiLanguageCustomDisclaimer, and MultiLanguageSenderName parameter values in the same order. + +This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. + +**Note**: The value English maps to every English language code except en-US. If you have users with en-US mailboxes only, use the value Default. If you have a mix of mailboxes with en-US and other English languages codes (en-GB, en-CA, en-AU, etc.), use the value Default in one customized quarantine notification, and the value English in another customized quarantine notification. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrganizationBrandingEnabled +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. +- $false: Organization branding is disabled. The default Microsoft logo is used in quarantine notifications. This is the default value. + +This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineRetentionDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTemplate.md b/exchange/exchange-ps/exchange/Set-RMSTemplate.md similarity index 78% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTemplate.md rename to exchange/exchange-ps/exchange/Set-RMSTemplate.md index 813e0ac350..807ec202d5 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTemplate.md +++ b/exchange/exchange-ps/exchange/Set-RMSTemplate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/set-rmstemplate -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Set-RMSTemplate @@ -15,19 +14,20 @@ monikerRange: "exchonline-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Set-RMSTemplate cmdlet to modify the properties of an existing Rights Management Services (RMS) template in your organization. - > [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). +> This cmdlet has been deprecated. If you use AD RMS with Exchange Online, you need to migrate to Azure Information Protection before you can use message encryption. For more information, see [Verify that Azure Rights Management is active](https://learn.microsoft.com/purview/set-up-new-message-encryption-capabilities#verify-that-azure-rights-management-is-active). + +Use the Set-RMSTemplate cmdlet to modify the properties of an existing Active Directory Rights Management Services (AD RMS) template in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Set-RMSTemplate [-Identity] <RmsTemplateIdParameter> -Type <RmsTemplateType> [-Confirm] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -48,7 +48,6 @@ This example changes the RMS template Contoso Confidential from Distributed to A The Identity parameter specifies the RMS template. You can use any value that uniquely identifies the RMS template, for example: - Name - - GUID You can use the Get-RMSTemplate cmdlet to view the RMS templates in your organization. @@ -57,7 +56,7 @@ You can use the Get-RMSTemplate cmdlet to view the RMS templates in your organiz Type: RmsTemplateIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -70,9 +69,7 @@ Accept wildcard characters: False The Type parameter specifies the type of RMS template. You can specify one of the following values: - Archived - - Distributed - - All The default type for imported RMS templates is Archived. @@ -81,7 +78,7 @@ The default type for imported RMS templates is Archived. Type: RmsTemplateType Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -93,15 +90,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -117,7 +113,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -131,12 +127,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-ReceiveConnector.md b/exchange/exchange-ps/exchange/Set-ReceiveConnector.md similarity index 90% rename from exchange/exchange-ps/exchange/mail-flow/Set-ReceiveConnector.md rename to exchange/exchange-ps/exchange/Set-ReceiveConnector.md index 16044ad4a0..0243479192 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-ReceiveConnector.md +++ b/exchange/exchange-ps/exchange/Set-ReceiveConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-receiveconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ReceiveConnector @@ -17,41 +16,73 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ReceiveConnector cmdlet to modify Receive connectors on Mailbox servers and Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ReceiveConnector [-Identity] <ReceiveConnectorIdParameter> [-AdvertiseClientSettings <Boolean>] +Set-ReceiveConnector [-Identity] <ReceiveConnectorIdParameter> + [-AdvertiseClientSettings <Boolean>] [-AuthMechanism <AuthMechanisms>] - [-Banner <String>] [-BareLinefeedRejectionEnabled <Boolean>] [-BinaryMimeEnabled <Boolean>] - [-Bindings <MultiValuedProperty>] [-ChunkingEnabled <Boolean>] [-Comment <String>] [-Confirm] - [-ConnectionInactivityTimeout <EnhancedTimeSpan>] [-ConnectionTimeout <EnhancedTimeSpan>] - [-DefaultDomain <AcceptedDomainIdParameter>] [-DeliveryStatusNotificationEnabled <Boolean>] - [-DomainController <Fqdn>] [-DomainSecureEnabled <Boolean>] [-EightBitMimeEnabled <Boolean>] - [-EnableAuthGSSAPI <Boolean>] [-Enabled <Boolean>] - [-EnhancedStatusCodesEnabled <Boolean>] [-ExtendedProtectionPolicy <ExtendedProtectionPolicySetting>] - [-Fqdn <Fqdn>] [-LongAddressesEnabled <Boolean>] - [-MaxAcknowledgementDelay <EnhancedTimeSpan>] [-MaxHeaderSize <ByteQuantifiedSize>] [-MaxHopCount <Int32>] - [-MaxInboundConnection <Unlimited>] [-MaxInboundConnectionPercentagePerSource <Int32>] - [-MaxInboundConnectionPerSource <Unlimited>] [-MaxLocalHopCount <Int32>] [-MaxLogonFailures <Int32>] - [-MaxMessageSize <ByteQuantifiedSize>] [-MaxProtocolErrors <Unlimited>] [-MaxRecipientsPerMessage <Int32>] - [-MessageRateLimit <Unlimited>] [-MessageRateSource <MessageRateSourceFlags>] [-Name <String>] + [-AuthTarpitInterval <EnhancedTimeSpan>] + [-Banner <String>] + [-BareLinefeedRejectionEnabled <Boolean>] + [-BinaryMimeEnabled <Boolean>] + [-Bindings <MultiValuedProperty>] + [-ChunkingEnabled <Boolean>] + [-Comment <String>] + [-Confirm] + [-ConnectionInactivityTimeout <EnhancedTimeSpan>] + [-ConnectionTimeout <EnhancedTimeSpan>] + [-DefaultDomain <AcceptedDomainIdParameter>] + [-DeliveryStatusNotificationEnabled <Boolean>] + [-DomainController <Fqdn>] + [-DomainSecureEnabled <Boolean>] + [-EightBitMimeEnabled <Boolean>] + [-EnableAuthGSSAPI <Boolean>] + [-Enabled <Boolean>] + [-EnhancedStatusCodesEnabled <Boolean>] + [-ExtendedProtectionPolicy <ExtendedProtectionPolicySetting>] + [-Fqdn <Fqdn>] + [-LongAddressesEnabled <Boolean>] + [-MaxAcknowledgementDelay <EnhancedTimeSpan>] + [-MaxHeaderSize <ByteQuantifiedSize>] + [-MaxHopCount <Int32>] + [-MaxInboundConnection <Unlimited>] + [-MaxInboundConnectionPerSource <Unlimited>] + [-MaxInboundConnectionPercentagePerSource <Int32>] + [-MaxLocalHopCount <Int32>] + [-MaxLogonFailures <Int32>] + [-MaxMessageSize <ByteQuantifiedSize>] + [-MaxProtocolErrors <Unlimited>] + [-MaxRecipientsPerMessage <Int32>] + [-MessageRateLimit <Unlimited>] + [-MessageRateSource <MessageRateSourceFlags>] + [-Name <String>] [-OrarEnabled <Boolean>] [-PermissionGroups <PermissionGroups>] - [-PipeliningEnabled <Boolean>] [-ProtocolLoggingLevel <ProtocolLoggingLevel>] - [-RemoteIPRanges <MultiValuedProperty>] [-RequireEHLODomain <Boolean>] [-RequireTLS <Boolean>] - [-SizeEnabled <SizeMode>] [-SuppressXAnonymousTls <Boolean>] - [-TarpitInterval <EnhancedTimeSpan>] [-TlsDomainCapabilities <MultiValuedProperty>] [-WhatIf] - [-ServiceDiscoveryFqdn <Fqdn>] [-SmtpUtf8Enabled <Boolean>] [-TlsCertificateName <SmtpX509Identifier>] - [-TransportRole <ServerRole>] - [-AuthTarpitInterval <EnhancedTimeSpan>] [-RejectReservedSecondLevelRecipientDomains <Boolean>] + [-PipeliningEnabled <Boolean>] + [-ProtocolLoggingLevel <ProtocolLoggingLevel>] + [-RejectReservedSecondLevelRecipientDomains <Boolean>] [-RejectReservedTopLevelRecipientDomains <Boolean>] - [-RejectSingleLabelRecipientDomains <Boolean>] [<CommonParameters>] + [-RejectSingleLabelRecipientDomains <Boolean>] + [-RemoteIPRanges <MultiValuedProperty>] + [-RequireEHLODomain <Boolean>] + [-RequireTLS <Boolean>] + [-ServiceDiscoveryFqdn <Fqdn>] + [-SizeEnabled <SizeMode>] + [-SmtpUtf8Enabled <Boolean>] + [-SuppressXAnonymousTls <Boolean>] + [-TarpitInterval <EnhancedTimeSpan>] + [-TlsCertificateName <SmtpX509Identifier>] + [-TlsDomainCapabilities <MultiValuedProperty>] + [-TransportRole <ServerRole>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,12 +103,9 @@ Configures the Receive connector to time out connections after 15 minutes. 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 - - Distinguished name (DN) - - GUID - -- \<ServerName\>\\\<Name\> +- ServerName\\Name ```yaml Type: ReceiveConnectorIdParameter @@ -96,7 +124,6 @@ Accept wildcard characters: False 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). - - $false: The SMTP values are displayed in Outlook on the web. This is the default value. ```yaml @@ -116,29 +143,19 @@ Accept wildcard characters: False The AuthMechanism parameter specifies the advertised and accepted authentication mechanisms for the Receive connector. Valid values are: - None - - Tls - - Integrated - - BasicAuth - - BasicAuthRequireTLS - - ExchangeServer - - ExternalAuthoritative You can specify multiple values separated by commas, but some values have dependencies and exclusions: - You can only use the value None by itself. - - The value BasicAuthRequireTLS also requires the values BasicAuth and Tls. - - The only other value that you can use with ExternalAuthoritative is Tls. - - The value Tls is required when the value of the RequireTLS parameter is $true. - - The value ExternalAuthoritative, requires you to set the value of the PermissionGroups parameter to ExchangeServers. ```yaml @@ -154,12 +171,34 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AuthTarpitInterval +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. + +When you set the value to 00:00:00, you disable the authentication tarpit interval. Setting the value to more than a few seconds can cause timeouts and mail flow issues. + +You can configure the delay for other SMTP failure responses by using the TarpitInterval parameter. + +```yaml +Type: EnhancedTimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Banner 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: -220 \<Servername\> Microsoft ESMTP MAIL service ready at \<RegionalDay-Date-24HourTimeFormat\>\<RegionalTimeZoneOffset\> +`220 <ServerName> Microsoft ESMTP MAIL service ready at <RegionalDay-Date-24HourTimeFormat><RegionalTimeZoneOffset>` ```yaml Type: String @@ -178,7 +217,6 @@ Accept wildcard characters: False 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. - - $false: Messages that contain bare line feeds aren't rejected. This is the default value. Although message that contain bare line feeds might be delivered successfully, these messages don't follow SMTP protocol standards and might cause problems on messaging servers. @@ -200,7 +238,6 @@ Accept wildcard characters: False 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. - - $false: BINARYMIME is disabled and isn't advertised in the EHLO response. The binary MIME extension is defined in RFC 3030. @@ -219,14 +256,13 @@ Accept wildcard characters: False ``` ### -Bindings -The Bindings parameter specifies the local IP address and TCP port number that's used by the Receive connector. This parameter uses the syntax "\<IPv4 Address\>:\<TCP Port\>","\<IPv6 Address\>:\<TCP Port\>". You can specify an IPv4 address and port, and 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. +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. The values for this parameter must satisfy one of the following uniqueness requirements: - The combination of IP address and TCP port doesn't conflict with the IP address and TCP port that's used on another Receive connector on the server. - - You use an existing combination of IP address and TCP port that's configured on another Receive connector on the server, but you restrict the remote IP addresses by using the RemoteIPRanges parameter. When you create a Receive connector, you can only use the RemoteIPRanges and Bindings parameters together with the Custom or Partner switches (or the Usage parameter with the values Custom or Partner. ```yaml @@ -246,7 +282,6 @@ Accept wildcard characters: False 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. - - $false: CHUNKING is disabled and isn't advertised in the EHLO response. Chunking is defined in RFC 3030. @@ -283,8 +318,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -352,17 +386,13 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID Although you can configure any accepted domain as the default domain, you typically specify an authoritative domain. The default domain is used by: -- The external postmaster address: postmaster@\<default domain\>. - +- The external postmaster address: `postmaster@<default domain>`. - Encapsulated non-SMTP email addresses (Internet Mail Connector Encapsulated Address or IMCEA encapsulation). - - The primary address for all recipients in the default email address policy. If you configure another accepted domain as the default domain, the default email address policy isn't automatically updated. ```yaml @@ -382,7 +412,6 @@ Accept wildcard characters: False 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. - - $false: DSN is disabled and isn't advertised in the EHLO response. Delivery status notifications are defined in RFC 3461. @@ -422,19 +451,14 @@ Accept wildcard characters: False 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. - - $false: Mutual TLS authentication is disabled. Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative. - - The domain that's used for mutual TLS authentication must be configured in the following locations: - - The TLSReceiveDomainSecureList parameter on the Set-TransportConfig cmdlet. - - The AddressSpaces parameter on the Set-SendConnector cmdlet for the corresponding Send connector. - - The TLSSendDomainSecureList parameter on the Set-TransportConfig cmdlet. ```yaml @@ -454,7 +478,6 @@ Accept wildcard characters: False 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. - - $false: 8BITMIME is disabled and isn't advertised in the EHLO response. 8-bit data transmission is defined in RFC 6152. @@ -476,7 +499,6 @@ Accept wildcard characters: False 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. - - $false: Kerberos is disabled. The Extended SMTP keyword AUTH NTLM is advertised in the EHLO response. Clients can only use NTLM for Integrated Windows authentication. The Generic Security Services application programming interface (GSSAPI) is an IETF standard for accessing security services. @@ -498,7 +520,6 @@ Accept wildcard characters: False 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. - - $false: The Receive connector is disabled. ```yaml @@ -518,7 +539,6 @@ Accept wildcard characters: False 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. - - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response. Enhanced status codes are defined in RFC 2034. @@ -540,9 +560,7 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication will be used only if the connecting host supports it. Otherwise, the connections will be established without Extended Protection for Authentication. - - Require: Extended Protection for Authentication will be required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection will be rejected. Extended Protection for Authentication enhances the protection and handling of credentials when authenticating network connections using Integrated Windows authentication. Integrated Windows authentication is also known as NTLM. We strongly recommend that you use Extended Protection for Authentication if you are using Integrated Windows authentication. @@ -564,16 +582,13 @@ Accept wildcard characters: False 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 - - In the EHLO/HELO response of the Receive connector - - In the most recent Received header field in the incoming message when the message enters the Transport service on a Mailbox server or an Edge server - - During TLS authentication The default value is the FQDN of theExchange server that contains the Receive connector (for example edge01.contoso.com). You can specify a different FQDN (for example, mail.contoso.com). -Don't modify this value on the default Receive connector named Default \<Server Name\> on Mailbox servers. If you have multiple Mailbox servers in your organization, internal mail flow between Mailbox servers fails if you change the FQDN value on this Receive connector. +Don't modify this value on the default Receive connector named `Default <Server Name>` on Mailbox servers. If you have multiple Mailbox servers in your organization, internal mail flow between Mailbox servers fails if you change the FQDN value on this Receive connector. ```yaml Type: Fqdn @@ -592,15 +607,12 @@ Accept wildcard characters: False 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. - - $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value. When you set this parameter to the value $true the following changes are made to the Receive connector: - The XLONGADDR Extended SMTP extension is enabled and is advertised in the EHLO response. - - The accepted line length of an SMTP session is increased to 8,000 characters. - - Valid long addresses are accepted by the MAIL FROM and RCPT TO SMTP commands. You can only configure this parameter on Receive connectors in the Transport service on Mailbox servers. @@ -619,7 +631,7 @@ Accept wildcard characters: False ``` ### -MaxAcknowledgementDelay -This parameter isn't used by Microsoft Exchange Server 2016. It's only used by Microsoft Exchange 2010 servers in a coexistence environment. +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. @@ -644,11 +656,8 @@ The MaxHeaderSize parameter specifies the maximum size of the SMTP message heade When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -790,20 +799,16 @@ The MaxMessageSize parameter specifies the maximum size of a message that's allo When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value for this parameter is from 65536 to 2147483647 bytes. -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: ByteQuantifiedSize @@ -882,11 +887,8 @@ Accept wildcard characters: False The MessageRateSource parameter specifies how the message submission rate is calculated. Valid values are: - None: No message submission rate is calculated. - - IPAddress: The message submission rate is calculated for sending hosts. - - User: The message submission rate is calculated for sending users (specified with the MAIL FROM SMTP command). - - All: The message submission rate is calculated for both the sending users and sending hosts. ```yaml @@ -922,7 +924,6 @@ Accept wildcard characters: False 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. - - $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value. If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true. @@ -944,24 +945,18 @@ Accept wildcard characters: False 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 - - AnonymousUsers - - ExchangeUsers - - ExchangeServers - - ExchangeLegacyServers - - Partners - - Custom The default permission groups that are assigned to a Receive connector depend on the connector usage type parameter that was used when the connector was created (Client, Internal, Internet, Partner, or Usage). When you use the value Custom, you need to configure individual permissions by using the Add-ADPermission cmdlet. -For more information about the default permissions and security principals for permission groups, see [Receive connector permission groups](https://docs.microsoft.com/Exchange/mail-flow/connectors/receive-connectors#receive-connector-permission-groups). +For more information about the default permissions and security principals for permission groups, see [Receive connector permission groups](https://learn.microsoft.com/Exchange/mail-flow/connectors/receive-connectors#receive-connector-permission-groups). ```yaml Type: PermissionGroups @@ -980,7 +975,6 @@ Accept wildcard characters: False 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. - - $false: PIPELINING is disabled and isn't advertised in the EHLO response. Pipelining is defined in RFC 2920. @@ -1002,10 +996,9 @@ Accept wildcard characters: False 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. - - Verbose: Protocol logging is enabled on the Receive connector. -For more information about protocol logging, see [Protocol logging](https://docs.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). +For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). ```yaml Type: ProtocolLoggingLevel @@ -1020,32 +1013,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RemoteIPRanges -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 . - -- IP address range: For example, 192.168.1.1-192.168.1.254. - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.1.1/24 or 2001:0DB8::CD3/60. - -You can specify multiple value separated by commas ("\<value1\>","\<value2\>"...). - -Multiple Receive connectors on the same server can have overlapping remote IP address ranges as long as one IP address range is completely overlapped by another. For example, you can configure the following remote IP address ranges on different Receive connectors on the same server: - -- 0.0.0.0 - -- 192.168.1.1/24 - -- 192.168.1.10 +### -RejectReservedSecondLevelRecipientDomains +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: -When remote IP address ranges overlap, the Receive connector with the most specific match to the IP address of the connecting server is used. +- $true: RCPT TO commands that contain reserved second-level domains are rejected. +- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value. ```yaml -Type: MultiValuedProperty +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1054,18 +1032,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RequireEHLODomain -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. +### -RejectReservedTopLevelRecipientDomains +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: -- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value. +- $true: RCPT TO commands that contain reserved TLDs are rejected. +- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1074,18 +1051,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RequireTLS -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. +### -RejectSingleLabelRecipientDomains +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: -- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value. +- $true: RCPT TO commands that contain single-label domains are rejected. +- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1094,19 +1070,25 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SizeEnabled -The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: +### -RemoteIPRanges +The RemoteIPRanges parameter specifies the remote IP addresses that the Receive connector accepts messages from. 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. +- Single IP address: For example, 192.168.1.1 or fe80::39bd:88f7:6969:d223%11. +- IP address range: For example, 192.168.1.1-192.168.1.254. +- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.1.1/24 or 2001:0DB8::CD3/60. -- Disabled: SIZE is disabled and isn't advertised in the EHLO response. +You can specify multiple value separated by commas: `"Value1","Value2",..."ValueN"`. -- EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers. +Multiple Receive connectors on the same server can have overlapping remote IP address ranges as long as one IP address range is completely overlapped by another. For example, you can configure the following remote IP address ranges on different Receive connectors on the same server: -SIZE is defined in RFC 1870. +- 0.0.0.0 +- 192.168.1.1/24 +- 192.168.1.10 + +When remote IP address ranges overlap, the Receive connector with the most specific match to the IP address of the connecting server is used. ```yaml -Type: SizeMode +Type: MultiValuedProperty Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -1118,14 +1100,11 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SuppressXAnonymousTls -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. - -- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value. +### -RequireEHLODomain +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: -The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer. +- $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed. +- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value. ```yaml Type: Boolean @@ -1140,17 +1119,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -TarpitInterval -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. - -When you set the value to 00:00:00, you disable the tarpit interval. Setting this value to more than a few seconds can cause timeouts and mail flow issues. +### -RequireTLS +The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are: -You can configure the delay for authentication failure responses by using the AuthTarpitInterval parameter. +- $true: Inbound messages on the Receive connector require TLS transmission. +- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value. ```yaml -Type: EnhancedTimeSpan +Type: Boolean Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -1162,30 +1138,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -TlsDomainCapabilities -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: - -"\<domain1\>:\<capability1\>,\<capability 2\>\>"...,"\<domain2\>:\<capability1\>,\<capability2\>..."... - -The available \<capability\> values are: - -- AcceptCloudServicesMail (Exchange 2013 or later) - -- AcceptOorgProtocol - -- AcceptOorgHeader - -The available \<domainy\> values are an SMTP domain (for example, contoso.com), or the value NO-TLS for non-TLS encrypted inbound connections. - -For example, "contoso.com:AcceptOorgProtocol","fabrikam.com:AcceptOorgProtocol,AcceptOorgHeader" +### -ServiceDiscoveryFqdn +The ServiceDiscoveryFqdn parameter specifies the service discovery fully-qualified domain name (FQDN). for the Receive connector. ```yaml -Type: MultiValuedProperty +Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1194,30 +1154,20 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -SizeEnabled +The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +- 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. +- Disabled: SIZE is disabled and isn't advertised in the EHLO response. +- EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers. -### -ServiceDiscoveryFqdn -The ServiceDiscoveryFqdn parameter specifies the service discovery fully-qualified domain name (FQDN). for the Receive connector. +SIZE is defined in RFC 1870. ```yaml -Type: Fqdn +Type: SizeMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1242,14 +1192,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -TlsCertificateName -The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\<I\>X.500Issuer\<S\>X.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 \<Thumbprint\>, run the command $TLSCertName = "\<I\>$($TLSCert.Issuer)\<S\>$($TLSCert.Subject)" and then use the value $TLSCertName for this parameter. +### -SuppressXAnonymousTls +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. +- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value. + +The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer. ```yaml -Type: SmtpX509Identifier +Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1258,20 +1213,20 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -TransportRole -The TransportRole parameter specifies the transport service on the Mailbox server where the Receive connector is created.. Valid values are: +### -TarpitInterval +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). -- FrontendTransport: The Front End Transport service where client or external SMTP connections occur. +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. -- HubTransport: The Transport service where Exchange server and proxied client SMTP connections occur. +When you set the value to 00:00:00, you disable the tarpit interval. Setting this value to more than a few seconds can cause timeouts and mail flow issues. -You can't use this parameter on Edge Transport servers. +You can configure the delay for authentication failure responses by using the AuthTarpitInterval parameter. ```yaml -Type: ServerRole +Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1280,20 +1235,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AuthTarpitInterval -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. - -When you set the value to 00:00:00, you disable the authentication tarpit interval. Setting the value to more than a few seconds can cause timeouts and mail flow issues. - -You can configure the delay for other SMTP failure responses by using the TarpitInterval parameter. +### -TlsCertificateName +The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is `"<I>X.500Issuer<S>X.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 <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"` and then use the value $TLSCertName for this parameter. ```yaml -Type: EnhancedTimeSpan +Type: SmtpX509Identifier Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1302,18 +1251,29 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RejectReservedSecondLevelRecipientDomains -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: +### -TlsDomainCapabilities +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. -- $true: RCPT TO commands that contain reserved second-level domains are rejected. +This parameter uses the following syntax: -- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value. +`"Domain1:Capability1,Capability2,"...,"Domain2:Capability1,Capability2,...",...` + +You can only use this parameter in Exchange hybrid deployments, and the valid Capability values are: + +- AcceptCloudServicesMail (Exchange 2013 or later) +- AcceptOorgProtocol (Exchange 2010) + +More Capability values are available, but there is no scenario to use them. For more information, see [Advanced Office 365 Routing](https://techcommunity.microsoft.com/t5/exchange-team-blog/advanced-office-365-routing-locking-down-exchange-on-premises/ba-p/609238). + +The available Domain values are an SMTP domain (for example, contoso.com), or the value NO-TLS for non-TLS encrypted inbound connections. + +For example, `"contoso.com:AcceptOorgProtocol","fabrikam.com:AcceptCloudServicesMail"`. ```yaml -Type: Boolean +Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1322,18 +1282,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RejectReservedTopLevelRecipientDomains -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: +### -TransportRole +The TransportRole parameter specifies the transport service on the Mailbox server where the Receive connector is created. Valid values are: -- $true: RCPT TO commands that contain reserved TLDs are rejected. +- FrontendTransport: The Front End Transport service where client or external SMTP connections occur. +- HubTransport: The Transport service where Exchange server and proxied client SMTP connections occur. -- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value. +You can't use this parameter on Edge Transport servers. ```yaml -Type: Boolean +Type: ServerRole Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1342,18 +1303,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RejectSingleLabelRecipientDomains -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. - -- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: Boolean +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1367,12 +1324,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-RecipientFilterConfig.md b/exchange/exchange-ps/exchange/Set-RecipientFilterConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-RecipientFilterConfig.md rename to exchange/exchange-ps/exchange/Set-RecipientFilterConfig.md index ee1de20bb8..d1543894e3 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-RecipientFilterConfig.md +++ b/exchange/exchange-ps/exchange/Set-RecipientFilterConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-recipientfilterconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-RecipientFilterConfig @@ -17,19 +16,25 @@ This cmdlet is available only in on-premises Exchange. Use the Set-RecipientFilterConfig cmdlet to enable and configure the Recipient Filter agent. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-RecipientFilterConfig [-BlockedRecipients <MultiValuedProperty>] [-BlockListEnabled <Boolean>] - [-Confirm] [-DomainController <Fqdn>] [-Enabled <Boolean>] [-ExternalMailEnabled <Boolean>] - [-InternalMailEnabled <Boolean>] [-RecipientValidationEnabled <Boolean>] [-WhatIf] +Set-RecipientFilterConfig [-BlockedRecipients <MultiValuedProperty>] + [-BlockListEnabled <Boolean>] + [-Confirm] + [-DomainController <Fqdn>] + [-Enabled <Boolean>] + [-ExternalMailEnabled <Boolean>] + [-InternalMailEnabled <Boolean>] + [-RecipientValidationEnabled <Boolean>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +53,6 @@ Set-RecipientFilterConfig -BlockListEnabled $true -BlockedRecipients user1@conto This example makes the following changes to the Recipient Filter agent configuration: - Enables the Blocked Recipients list. - - Adds two users to the Blocked Recipients list. ## PARAMETERS @@ -88,8 +92,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -208,12 +211,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/exchange/Set-RecordReviewNotificationTemplateConfig.md new file mode 100644 index 0000000000..b3552f8231 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-RecordReviewNotificationTemplateConfig.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-RecordReviewNotificationTemplateConfig + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-RecordReviewNotificationTemplateConfig cmdlet to set up the customized record review notification and reminder that's sent when an item requires review. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-RecordReviewNotificationTemplateConfig -IsCustomizedNotificationTemplate <Boolean> -IsCustomizedReminderTemplate <Boolean> + [-CustomizedNotificationDataString <String>] + [-CustomizedReminderDataString <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-RecordReviewNotificationTemplateConfig -IsCustomizedNotificationTemplate $true -CustomizedNotificationDataString "This is the Contoso notification" -IsCustomizedReminderTemplate $true -CustomizedReminderDataString "This is the Contoso reminder" +``` + +This example configures customized review notification text and review reminder text. + +## PARAMETERS + +### -IsCustomizedNotificationTemplate +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. +- $false: Use the default system notification. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsCustomizedReminderTemplate +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. +- $false: Use the default system reminder. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomizedNotificationDataString +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomizedReminderDataString +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-RegulatoryComplianceUI.md b/exchange/exchange-ps/exchange/Set-RegulatoryComplianceUI.md new file mode 100644 index 0000000000..8f4caf3d77 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-RegulatoryComplianceUI.md @@ -0,0 +1,69 @@ +--- +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +online version: https://learn.microsoft.com/powershell/module/exchange/set-regulatorycomplianceui +applicable: Security & Compliance +title: Set-RegulatoryComplianceUI +schema: 2.0.0 +--- + +# Set-RegulatoryComplianceUI + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell) +. + +Use the Set-RegulatoryComplianceUI cmdlet to display the UI option in retention label settings to mark content as a regulatory record. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-RegulatoryComplianceUI -Enabled <Boolean> + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-RegulatoryComplianceUI -Enabled $true +``` + +This example displays the UI option in retention label settings to mark content as a regulatory record. + +## PARAMETERS + +### -Enabled +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. + +$false: The option to mark content as a regulatory record is not visible in the UI for retention label settings. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-RemoteDomain.md b/exchange/exchange-ps/exchange/Set-RemoteDomain.md similarity index 90% rename from exchange/exchange-ps/exchange/mail-flow/Set-RemoteDomain.md rename to exchange/exchange-ps/exchange/Set-RemoteDomain.md index d7c40448a7..8f7c3965a5 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-RemoteDomain.md +++ b/exchange/exchange-ps/exchange/Set-RemoteDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-remotedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-RemoteDomain @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-RemoteDomain cmdlet to configure a managed connection for a remote domain. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -44,18 +43,20 @@ Set-RemoteDomain [-Identity] <RemoteDomainIdParameter> [-NonMimeCharacterSet <String>] [-PreferredInternetCodePageForShiftJis <PreferredInternetCodePageForShiftJisEnum>] [-RequiredCharsetCoverage <Int32>] + [-SmtpDaneMandatoryModeEnabled <Boolean>] [-TargetDeliveryDomain <Boolean>] [-TNEFEnabled <Boolean>] [-TrustedMailInboundEnabled <Boolean>] [-TrustedMailOutboundEnabled <Boolean>] [-UseSimpleDisplayName <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION When you set a remote domain, you can control mail flow with more precision, specify message formatting and policy and specify acceptable character sets for messages sent to or received from the remote domain. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,9 +68,7 @@ Set-RemoteDomain Contoso -AllowedOOFType None -DeliveryReportEnabled $false -TNE This example performs the following actions: - It disables out-of-office notifications to the remote domain. - - It suppresses delivery receipts sent from clients in your organization to the remote domain. - - It enables TNEF message data on messages sent to the remote domain. ### Example 2 @@ -85,9 +84,7 @@ This example queries Active Directory for all remote domains for which auto repl 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 - - Distinguished name (DN) - - GUID ```yaml @@ -107,13 +104,15 @@ Accept wildcard characters: False 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. - - ExternalLegacy: Only external automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain. - - InternalLegacy: Only internal automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain. - - None: No automatic replies are sent to recipients in the remote domain. +The value of this parameter is affected by the value of the IsInternal parameter, and vice-versa: + +- If you change the AllowedOOFType parameter to the value InternalLegacy, the IsInternal parameter is changed to the value $true. +- If you change the IsInternal parameter to the value $false, the AllowedOOFType parameter is changed to the value ExternalLegacy. + ```yaml Type: AllowedOOFType Parameter Sets: (All) @@ -131,7 +130,6 @@ Accept wildcard characters: False 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. - - $false: Auto-forwarded messages aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange. ```yaml @@ -151,7 +149,6 @@ Accept wildcard characters: False 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. - - $false: Automatic replies aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange. ```yaml @@ -171,19 +168,12 @@ Accept wildcard characters: False 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. - - UseQP: Always use QP (quoted-printable) encoding for HTML and for plain text. - - UseBase64: Always use Base64 encoding for HTML and for plain text. - - UseQPHtmlDetectTextPlain: Use QP encoding for HTML and for plain text unless line wrapping is enabled in plain text. If line wrapping is enabled, use 7-bit encoding for plain text. - - UseBase64HtmlDetectTextPlain: Use Base64 encoding for HTML and for plain text, unless line wrapping is enabled in plain text. If line wrapping is enabled in plain text, use Base64 encoding for HTML, and use 7-bit encoding for plain text. - - UseQPHtml7BitTextPlain: Always use QP encoding for HTML. Always use 7-bit encoding for plain text. - - UseBase64Html7BitTextPlain: Always use Base64 encoding for HTML. Always use 7-bit encoding for plain text. - - Undefined: Always use QP encoding for HTML and plain text. This is the default value. ```yaml @@ -224,8 +214,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -245,9 +234,7 @@ Accept wildcard characters: False 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. - - MimeText: Converts all messages to MIME messages that use text formatting. - - MimeHtml: Converts all messages to MIME messages that use HTML formatting. ```yaml @@ -267,7 +254,6 @@ Accept wildcard characters: False 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. - - $false: Delivery reports aren't delivered to recipients in the remote domain. ```yaml @@ -284,12 +270,11 @@ Accept wildcard characters: False ``` ### -DisplaySenderName -Note: You should only modify this parameter under the direction of Microsoft Customer Service and Support. +**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: - $true: Sender names are displayed in messages sent to recipients in the remote domain. This is the default value. - - $false. Sender names aren't displayed in messages sent to recipients in the remote domain. ```yaml @@ -326,12 +311,11 @@ Accept wildcard characters: False ``` ### -IsCoexistenceDomain -This parameter is available or functional only in 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: - $true: The remote domain represents your Exchange Online organization. - - $false: The remote domain doesn't represent your Exchange Online organization. This is the default value. ```yaml @@ -350,10 +334,14 @@ Accept wildcard characters: False ### -IsInternal 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 or antispam agents) treat recipients in the remote domain as internal recipients. Typically, you use this value in cross-forest deployments. - +- $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. - $false: Recipients in the remote domain are treated as external recipients. This is the default value. +The value of this parameter is affected by the value of the AllowedOOFType parameter, and vice-versa: + +- If you change the AllowedOOFType parameter to the value InternalLegacy, the IsInternal parameter is changed to the value $true. +- If you change the IsInternal parameter to the value $false, the AllowedOOFType parameter is changed to the value ExternalLegacy. + ```yaml Type: Boolean Parameter Sets: (All) @@ -387,7 +375,6 @@ Accept wildcard characters: False 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. - - $false: Meeting requests forwarded to recipients in the remote domain don't generate a meeting forward notification to the meeting organizer. ```yaml @@ -440,12 +427,11 @@ Accept wildcard characters: False ``` ### -NDRDiagnosticInfoEnabled -This parameter is available only in on-premises Exchange. +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: - $true: The diagnostic information of an NDR includes details that help administrators troubleshoot delivery problems. This detailed information includes internal server names. This is the default value. - - $false: The diagnostic information section in the NDR body as well as internal server headers from the attached original message headers are removed from the NDR. This parameter is meaningful only when the value of the NDREnabled parameter is $true. @@ -454,7 +440,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -464,19 +450,16 @@ Accept wildcard characters: False ``` ### -NDREnabled -This parameter is available only in on-premises Exchange. - 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. - - $false: NDRs from your organization aren't sent to recipients in the remote domain. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -511,11 +494,8 @@ Accept wildcard characters: False 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. - - 50221: Use ESC-2022-JP codepage. - - 50222: Use SIO-2022-JP codepage. - - Undefined: No codepage is defined. This is the default value. ```yaml @@ -534,7 +514,7 @@ Accept wildcard characters: False ### -RequiredCharsetCoverage 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. +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. If recipients in the remote domain use characters that span character sets, you might want to specify a lower percentage to ensure that your organization's preferred character set is used during content conversion. @@ -551,11 +531,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SmtpDaneMandatoryModeEnabled +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -TargetDeliveryDomain 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. - - $false: The remote domain isn't used for the target email address of mail users that represent the users in the other forest. This is the default value. ```yaml @@ -575,9 +572,7 @@ Accept wildcard characters: False 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. - - $false: TNEF encoding isn't used on any messages sent to the remote domain. - - $null (blank): TNEF encoding isn't specified for the remote domain. This is the default value. TNEF encoding for recipients in the remote domain is controlled by the value of the UseMapiRichTextFormat parameter for any mail user or mail contact objects, the sender's per-recipient settings in Outlook, or the sender's default internet message settings in Outlook ```yaml @@ -597,7 +592,6 @@ Accept wildcard characters: False 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. - - $false: Inbound messages from senders in the remote domain won't bypass content filtering and recipient filtering. This is the default value. ```yaml @@ -617,7 +611,6 @@ Accept wildcard characters: False 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. - - $false: Outbound messages to recipients in the remote domain won't bypass content filtering and recipient filtering. This is the default value. ```yaml @@ -636,8 +629,7 @@ Accept wildcard characters: False ### -UseSimpleDisplayName 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 \<EmailAddress\>". - +- $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 <EmailAddress>`. - $false: Simple display names aren't used in messages sent to recipients in the remote domain. This is the default value. ```yaml @@ -653,17 +645,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-RemoteMailbox.md b/exchange/exchange-ps/exchange/Set-RemoteMailbox.md similarity index 84% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Set-RemoteMailbox.md rename to exchange/exchange-ps/exchange/Set-RemoteMailbox.md index a25d44736b..6850e91830 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-RemoteMailbox.md +++ b/exchange/exchange-ps/exchange/Set-RemoteMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-remotemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-RemoteMailbox @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-RemoteMailbox cmdlet to modify remote mailboxes. A remote mailbox is a mail user in Active Directory that's associated with a mailbox in the cloud-based service. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -93,7 +92,7 @@ Some attributes on mailboxes in the service can only be configured by connecting Directory synchronization must be configured correctly for changes made to an on-premises mail user to be applied to a mailbox in the service. Changing the configuration of the mailbox in the service isn't immediate and depends on the directory synchronization schedule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -117,19 +116,12 @@ This example configures delivery restrictions for the mailbox in the service tha 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 - - GUID - - Distinguished name (DN) - -- Domain\\SamAccountName - +- Domain\\Username - User principal name (UPN) - - Legacy DN - - Email address - - User alias ```yaml @@ -151,20 +143,15 @@ The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages t 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\<sender1\>","\<sender2\>"...; Remove="\<sender1\>","\<sender2\>"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -189,20 +176,15 @@ The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send m 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \<group1\>,\<group2\>,...\<groupN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<group1\>","\<group2\>",..."\<groupN\>". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\<group1\>","\<group2\>"...; Remove="\<group1\>","\<group2\>"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. @@ -229,18 +211,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. @@ -262,7 +239,10 @@ Accept wildcard characters: False ``` ### -ACLableSyncedObjectEnabled -The ACLableSyncedObjectEnabled switch specifies whether the remote mailbox is an ACLableSyncedMailboxUser. To enable this, use this switch without a value. To disable this, use this exact syntax: -ACLableSyncedObjectEnabled:$false. +The ACLableSyncedObjectEnabled switch specifies whether the remote mailbox is an ACLableSyncedMailboxUser. + +- To enable this feature, use this switch without a value. +- To disable this feature, use this exact syntax: `-ACLableSyncedObjectEnabled:$false`. ```yaml Type: SwitchParameter @@ -278,16 +258,20 @@ Accept wildcard characters: False ``` ### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. +The 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. +The Alias value can contain letters, numbers and the following characters: -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\<alias\>@\<domain\>). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. +If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: +- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.onmicrosoft.com results in the Alias property value `helpdesk`. - Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). @@ -324,7 +308,15 @@ Accept wildcard characters: False ``` ### -ArchiveName -The ArchiveName parameter specifies the name of the archive mailbox. Use this parameter to change the name of the archive. +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: + +- Exchange 2016 or later: `In-Place Archive -<Display Name>` +- Exchange 2013: `In-Place Archive - <Display Name>` +- Exchange 2010: `Personal Archive - <Display Name>` + +In Outlook, the value of this parameter is ignored. The name of the archive mailbox that's shown in the folder list is `Online Archive - <PrimarySMTPAddress>`. ```yaml Type: MultiValuedProperty @@ -345,20 +337,15 @@ The BypassModerationFromSendersOrMembers parameter specifies who is allowed to s To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple senders and overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". +To enter multiple senders and overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="\<sender1\>","\<sender2\>"...; Remove="\<sender3\>","\<sender4\>"...}. +To add or remove one or more senders without affecting any existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. @@ -378,8 +365,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -668,33 +654,28 @@ Accept wildcard characters: False ``` ### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). +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. Some examples of valid values include: +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: - SMTP: The primary SMTP address. You can use this value only once in a command. - - smtp: Other SMTP email addresses. - - X400: X.400 addresses in on-premises Exchange. - - X500: X.500 addresses in on-premises Exchange. -If you don't include a \<Type\> value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. To specify the primary SMTP email address, you can use any of the following methods: -- Use the \<Type\> value SMTP on the address. - -- The first email address when you don't use any \<Type\> values, or when you use multiple \<Type\> values of smtp. - +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. - Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",..."\<Type\>:\<emailaddressN\>". +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",...; Remove="\<Type\>:\<emailaddress2\>","\<Type\>:\<emailaddress2\>",...}. +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. ```yaml Type: ProxyAddressCollection @@ -713,7 +694,6 @@ Accept wildcard characters: False 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. - - $false: Email address policies aren't applied to this recipient. ```yaml @@ -750,9 +730,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute1 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -772,9 +752,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute2 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -794,9 +774,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute3 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -816,9 +796,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute4 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -838,9 +818,9 @@ Accept wildcard characters: False ### -ExtensionCustomAttribute5 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. @@ -877,7 +857,6 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. - - $false: The recipient is visible in address lists. This is the default value. ```yaml @@ -894,12 +873,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -938,9 +916,8 @@ The MailTip parameter specifies the custom MailTip text for this recipient. The When you add a MailTip to a recipient, two things happen: -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \<html\>\<body\>This mailbox is not monitored\</body\>\</html\>. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\<MailTip text\>. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `<html><body>This mailbox is not monitored</body></html>`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:<MailTip text>`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. ```yaml Type: String @@ -960,11 +937,11 @@ The MailTipTranslations parameter specifies additional languages for the custom To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: -@{Add="\<culture 1\>:\<localized text 1\>","\<culture 2\>:\<localized text 2\>"...; Remove="\<culture 3\>:\<localized text 3\>","\<culture 4\>:\<localized text 4\>"...} +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. -\<culture\> is a valid ISO 639 two-letter culture code that's associated with the language. +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. ```yaml Type: MultiValuedProperty @@ -983,20 +960,15 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. @@ -1017,7 +989,6 @@ Accept wildcard characters: False 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. - - $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. @@ -1054,7 +1025,7 @@ Accept wildcard characters: False ### -PrimarySmtpAddress 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 that means the email addresses of the mail user no longer automatically updated by email address policies. +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. The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. @@ -1079,13 +1050,9 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t When you enter a number, you can qualify it with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1113,13 +1080,9 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t When you enter a number, you can qualify it with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1145,20 +1108,15 @@ The RejectMessagesFrom parameter specifies who isn't allowed to send messages to 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\<sender1\>","\<sender2\>"...; Remove="\<sender1\>","\<sender2\>"...}. +To add or remove senders without affecting other existing entries, use the following syntax: `@{Add="Sender1","Sender2"...; Remove="Sender3","Sender4"...}`. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1183,20 +1141,15 @@ The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send me 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \<group1\>,\<group2\>,...\<groupN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<group1\>","\<group2\>",..."\<groupN\>". +You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: `Group1,Group2,...GroupN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Group1","Group2",..."GroupN"`. -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\<group1\>","\<group2\>"...; Remove="\<group1\>","\<group2\>"...}. +To add or remove groups without affecting other existing entries, use the following syntax: `@{Add="Group1","Group2"...; Remove="Group3","Group4"...}`. The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. @@ -1223,18 +1176,13 @@ Valid values for this parameter are individual senders and groups in your organi To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. @@ -1274,7 +1222,7 @@ Accept wildcard characters: False ``` ### -RemovePicture -The RemovePicture switch specifies whether to remove the picture from the mail user. You don't need to specify a value with this switch. +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. @@ -1292,7 +1240,7 @@ Accept wildcard characters: False ``` ### -RemoveSpokenName -The RemoveSpokenName switch specifies whether to remove the spoken name from the mail user. You don't need to specify a value with this switch. +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. @@ -1313,7 +1261,6 @@ Accept wildcard characters: False 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. - - $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. The default value is $false. @@ -1335,7 +1282,6 @@ Accept wildcard characters: False 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. - - $false: The user isn't required to change their password the next time they log on. This is the default value. ```yaml @@ -1352,7 +1298,7 @@ Accept wildcard characters: False ``` ### -SamAccountName -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 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. +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 @@ -1371,9 +1317,7 @@ Accept wildcard characters: False 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. - - Internal: Notify senders in the organization when their messages aren't approved. - - Never: Don't notify anyone when a message isn't approved. This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). @@ -1397,18 +1341,15 @@ Accept wildcard characters: False The Type parameter specifies the type for the mailbox in the service. Valid values are: - Regular - - Room - - Equipment - - Shared Notes on the value Shared: -- Shared is available only in Exchange 2013 CU21 or later and Exchange 2016 CU10 or later. To use this value, you also need to run setup.exe /PrepareAD. For more information, see [KB4133605](https://support.microsoft.com/help/4133605/cmdlets-to-create-modify-remote-shared-mailbox-in-on-premises-exchange). - -- You can only use Shared on a mailbox that was originally created in Exchange Online. If the mailbox was originally created in on-premises Exchange and then migrated to Exchange Online, you need to migrate the mailbox back to on-premises Exchange, convert the mailbox to a shared mailbox in on-premises Exchange, and then migrate the shared mailbox to Exchange Online. Or, you can change the RemoteRecipientType property value of the on-premises mailbox to "ProvisionMailbox, Migrated, DeprovisionArchive" by running the following command on an Exchange server: Set-ADUser -Identity "\<UserName\>" -Replace @{msExchRemoteRecipientTYpe="21"}. +- Shared is available only in Exchange 2013 CU21 or later, Exchange 2016 CU10 or later, and Exchange 2019. In Exchange 2013 and Exchange 2016, you also need to run setup.exe /PrepareAD. For more information, see [KB4133605](https://support.microsoft.com/help/4133605). +- In hybrid environments, changing the mailbox type of a migrated mailbox needs to be done on both sides: Set-Mailbox in Exchange Online and Set-RemoteMailbox in on-premises Exchange. +- If directory synchronization unexpectedly converts shared mailboxes in Exchange Online back into user mailboxes, or if you continue to receive the `remoteMailbox.RemoteRecipientType must include ProvisionMailbox` error when you use the value Shared, take the action described in Step 3 in the Resolution section in [KB2710029](https://support.microsoft.com/help/2710029). ```yaml Type: ConvertibleRemoteMailboxSubType @@ -1424,7 +1365,7 @@ Accept wildcard characters: False ``` ### -UserPrincipalName -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. +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 @@ -1459,7 +1400,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -1482,12 +1422,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-ReportSubmissionPolicy.md b/exchange/exchange-ps/exchange/Set-ReportSubmissionPolicy.md new file mode 100644 index 0000000000..9e9b525a46 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ReportSubmissionPolicy.md @@ -0,0 +1,1107 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ReportSubmissionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ReportSubmissionPolicy cmdlet to modify the report submission policy in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ReportSubmissionPolicy [-Identity] <ReportSubmissionPolicyIdParameter> + [-Confirm] + [-DisableQuarantineReportingOption <Boolean>] + [-DisableUserSubmissionOptions <Boolean>] + [-EnableCustomizedMsg <Boolean>] + [-EnableCustomNotificationSender <Boolean>] + [-EnableOrganizationBranding <Boolean>] + [-EnableReportToMicrosoft <Boolean>] + [-EnableThirdPartyAddress <Boolean>] + [-EnableUserEmailNotification <Boolean>] + [-JunkReviewResultMessage <String>] + [-NotJunkReviewResultMessage <String>] + [-NotificationFooterMessage <String>] + [-NotificationSenderAddress <MultiValuedProperty>] + [-NotificationsForCleanSubmissionAirInvestigationsEnabled <Boolean>] + [-NotificationsForPhishMalwareSubmissionAirInvestigationsEnabled <Boolean>] + [-NotificationsForSpamSubmissionAirInvestigationsEnabled <Boolean>] + [-NotificationsForSubmissionAirInvestigationsEnabled <Boolean>] + [-OnlyShowPhishingDisclaimer <Boolean>] + [-PhishingReviewResultMessage <String>] + [-PostSubmitMessage <String>] + [-PostSubmitMessageEnabled <Boolean>] + [-PostSubmitMessageForJunk <String>] + [-PostSubmitMessageForNotJunk <String>] + [-PostSubmitMessageForPhishing <String>] + [-PostSubmitMessageTitle <String>] + [-PostSubmitMessageTitleForJunk <String>] + [-PostSubmitMessageTitleForNotJunk <String>] + [-PostSubmitMessageTitleForPhishing <String>] + [-PreSubmitMessage <String>] + [-PreSubmitMessageEnabled <Boolean>] + [-PreSubmitMessageForJunk <String>] + [-PreSubmitMessageForNotJunk <String>] + [-PreSubmitMessageForPhishing <String>] + [-PreSubmitMessageTitle <String>] + [-PreSubmitMessageTitleForJunk <String>] + [-PreSubmitMessageTitleForNotJunk <String>] + [-PreSubmitMessageTitleForPhishing <String>] + [-ReportChatMessageEnabled <Boolean>] + [-ReportChatMessageToCustomizedAddressEnabled <Boolean>] + [-ReportJunkAddresses <MultiValuedProperty>] + [-ReportJunkToCustomizedAddress <Boolean>] + [-ReportNotJunkAddresses <MultiValuedProperty>] + [-ReportNotJunkToCustomizedAddress <Boolean>] + [-ReportPhishAddresses <MultiValuedProperty>] + [-ReportPhishToCustomizedAddress <Boolean>] + [-ThirdPartyReportAddresses <MultiValuedProperty>] + [-UserSubmissionOptions <Int32>] + [-UserSubmissionOptionsMessage <String>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The report submission policy controls most of the settings for user submissions in the Microsoft Defender portal at <https://security.microsoft.com/securitysettings/userSubmission>. + +The report submission rule (the SentTo parameter \*-ReportSubmissionRule cmdlets) controls the email address of the reporting mailbox where user reported messages are sent. + +When you set the email address of the reporting mailbox in the Microsoft Defender portal, the same email address is also set in the following parameters in the \*-ReportSubmissionPolicy cmdlets: + +- Microsoft integrated reporting using Microsoft reporting tools in Outlook: The ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses parameters. +- Microsoft integrated reporting using third-party tools in Outlook: The ThirdPartyReportAddresses parameter. + +Although it's not absolutely required, it makes sense to keep the email address consistent in the related parameters in the \*-ReportSubmissionPolicy and \*-ReportSubmissionRule cmdlets. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $true -EnableThirdPartyAddress $false -ThirdPartyReportAddresses $null -ReportJunkToCustomizedAddress $false -ReportJunkAddresses $null -ReportNotJunkToCustomizedAddress $false -ReportNotJunkAddresses $null -ReportPhishToCustomizedAddress $false -ReportPhishAddresses $null + +Get-ReportSubmissionRule | Remove-ReportSubmissionRule +``` + +This example turns on reporting in Outlook, uses Microsoft reporting tools in Outlook, but allows users to report messages to Microsoft only. The reporting mailbox is not used. + +**Notes**: + +- You can use this example (and the other examples) without concern for the existing values of the specified parameters. Depending on your current configuration, some of the parameters might already be set to the required values and therefore might not be required. +- If the report submission rule doesn't already exist (the Get-ReportSubmissionRule command returns no output), you don't need to run the second command to remove it. + +### Example 2 +```powershell +$usersub = "reportedmessages@contoso.com" + +Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $true -EnableThirdPartyAddress $false -ThirdPartyReportAddresses $null -ReportJunkToCustomizedAddress $true -ReportJunkAddresses $usersub -ReportNotJunkToCustomizedAddress $true -ReportNotJunkAddresses $usersub -ReportPhishToCustomizedAddress $true -ReportPhishAddresses $usersub + +New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub +``` + +This example turns on reporting in Outlook, uses Microsoft reporting tools in Outlook, allows users to report messages to Microsoft, and sends reported messages to the specified reporting mailbox. + +The required third command is different based on whether you already have a report submission rule: + +- If you don't already have a report submission rule (the Get-ReportSubmissionRule cmdlet returns nothing), run the New-ReportSubmissionRule command as described. +- If you already have a report submission rule (the Get-ReportSubmissionRule cmdlet returns output), run the following command instead: `Set-ReportSubmissionRule -Name DefaultReportSubmissionRule -SentTo $usersub`. + +### Example 3 +```powershell +$usersub = "userreportedmessages@fabrikam.com" + +Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableThirdPartyAddress $false -ThirdPartyReportAddresses $null -ReportJunkToCustomizedAddress $true -ReportJunkAddresses $usersub -ReportNotJunkToCustomizedAddress $true -ReportNotJunkAddresses $usersub -ReportPhishToCustomizedAddress $true -ReportPhishAddresses $usersub + +New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub +``` + +This example turns on reporting in Outlook, uses Microsoft reporting tools in Outlook, and sends reported messages to the specified reporting mailbox only (users can't report messages to Microsoft). + +The required third command is different based on whether you already have a report submission rule: + +- If you don't already have a report submission rule (the Get-ReportSubmissionRule cmdlet returns nothing), run the New-ReportSubmissionRule command as described. +- If you already have a report submission rule (the Get-ReportSubmissionRule cmdlet returns output), run the following command instead: `Set-ReportSubmissionRule -Name DefaultReportSubmissionRule -SentTo $usersub`. + +### Example 4 +```powershell +$usersub = "thirdpartyreporting@wingtiptoys.com" + +Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableThirdPartyAddress $true -ThirdPartyReportAddresses $usersub -ReportJunkToCustomizedAddress $false -ReportJunkAddresses $null -ReportNotJunkToCustomizedAddress $false -ReportNotJunkAddresses $null -ReportPhishToCustomizedAddress $false -ReportPhishAddresses $null + +New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub +``` + +This example turns on reporting in Outlook, but uses third-party reporting tools in Outlook to send reported messages to the specified reporting mailbox in Exchange Online. + +The required third command is different based on whether you already have a report submission rule: + +- If you don't already have a report submission rule (the Get-ReportSubmissionRule cmdlet returns nothing), run the New-ReportSubmissionRule command as described. +- If you already have a report submission rule (the Get-ReportSubmissionRule cmdlet returns output), run the following command instead: `Set-ReportSubmissionRule -Name DefaultReportSubmissionRule -SentTo $usersub`. + +### Example 5 +```powershell +Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableThirdPartyAddress $true -ThirdPartyReportAddresses $usersub -ReportJunkToCustomizedAddress $false -ReportJunkAddresses $null -ReportNotJunkToCustomizedAddress $false -ReportNotJunkAddresses $null -ReportPhishToCustomizedAddress $false -ReportPhishAddresses $null + +Get-ReportSubmissionRule | Remove-ReportSubmissionRule +``` + +This example turns off the Microsoft integrated reporting. Microsoft reporting tools in Outlook are not available to users and messages reported by third-party tools in Outlook are not available on the Submissions page in the Microsoft Defender portal. + +If the report submission rule doesn't already exist (the Get-ReportSubmissionRule command returns no output), you don't need to run the second command to remove it. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableQuarantineReportingOption +The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: + +- $true: Users can't report quarantined messages from quarantine. +- $false: Users can report quarantined messages from quarantine. This is the default value. + +This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableUserSubmissionOptions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableCustomizedMsg +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableCustomNotificationSender +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. +- $false: Use the default sender email address. This is the default value. + +You specify the sender email address using the NotificationSenderAddress parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOrganizationBranding +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. +- $false: Don't use the company logo in the footer text. Use the Microsoft logo. + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableReportToMicrosoft +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: + +- **Microsoft reporting tools are available in Outlook for users to report messages to Microsoft only (the reporting mailbox isn't used)**: The ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $false. +- **Microsoft reporting tools are available in Outlook for users to report messages to Microsoft and reporting mailbox (reported messages are sent to the specified mailbox)**: The ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $true. To create the policy, use the same email address in the ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhisAddresses parameters, and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. This is the default configuration. +- **Using a third party add-in in Outlook for users to report to Microsoft and reporting mailbox**: The ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $false. The EnableThirdPartyAddress parameter value is $true. 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. + +The value $false for this parameter disables reporting in Outlook. The following configurations are possible: + +- **Microsoft reporting tools are available in Outlook, but reported messages are sent only to the reporting mailbox**: The ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $true. To create the policy, use the same email address in the ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhisAddresses parameters, and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. +- **Reporting in Outlook is disabled. Microsoft reporting tools are not available in Outlook. Any messages reported by users in Outlook with third-party reporting tools aren't visible on the Submissions page in the Microsoft Defender portal**: The EnableThirdPartyAddress, ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameter values are $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableThirdPartyAddress +The EnableThirdPartyAddress parameter specifies whether you're using third-party 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 third-party reporting mailbox. The following configurations are possible: + +- **Reported messages are sent only to the reporting mailbox**: Microsoft pulls metadata from messages sent to the Exchange Online reporting mailbox by third-party tools. Microsoft uses the metadata to populate the submissions page in the Microsoft Defender Portal and fire alerts. You also need to set the EnableReportToMicrosoft parameter value to $false. Use the same email address in the ThirdPartyReportAddresses parameter and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlets. +- **Reported messages are sent to both Microsoft and reporting mailbox**: Microsoft pulls the metadata and message content from messages sent to the Exchange Online reporting mailbox by third-party tools. Microsoft uses the metadata to populate the submissions page in the Microsoft Defender Portal and fire alerts. The email is used to generate result for the submissions. You also need to set the EnableReportToMicrosoft parameter value to $true. Use the same email address in the ThirdPartyReportAddresses parameter and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlets. + +The value $false means third-party reporting tools in Outlook aren't used. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUserEmailNotification +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). +- $false: Customized admin review result messages are not sent. + +Use the JunkReviewResultMessage, NotJunkReviewResultMessage, PhishingReviewResultMessage parameters to configure the message body text that's used for each verdict. + +Use the NotificationFooterMessage parameter for the footer that's used for all verdicts (junk, not junk, and phishing). + +This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -JunkReviewResultMessage +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. + +Use the NotificationFooterMessage parameter to customize the footer text of result messages. + +Use the NotificationSenderAddress parameter to customize the sender email address of result messages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotJunkReviewResultMessage +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. + +Use the NotificationFooterMessage parameter to customize the footer text of result messages. + +Use the NotificationSenderAddress parameter to customize the sender email address of result messages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationFooterMessage +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. + +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationSenderAddress +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForCleanSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForPhishMalwareSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForSpamSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationsForSubmissionAirInvestigationsEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlyShowPhishingDisclaimer +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhishingReviewResultMessage +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. + +Use the NotificationFooterMessage parameter to customize the footer text of result messages. + +Use the NotificationSenderAddress parameter to customize the sender email address of result messages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessage +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. + +This parameter is meaningful only when the value of the PostSubmitMessageEnabled parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageEnabled +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. +- $false: Users don't receive pop-up notifications in Outlook after they report messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageForJunk +Don't use this parameter. Use the PostSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageForNotJunk +Don't use this parameter. Use the PostSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageForPhishing +Don't use this parameter. Use the PostSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitle +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. + +This parameter is meaningful only when the value of the PostSubmitMessageEnabled parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitleForJunk +Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitleForNotJunk +Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostSubmitMessageTitleForPhishing +Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessage +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. + +This parameter is meaningful only when the value of the PreSubmitMessageEnabled parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageEnabled +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. +- $false: Users don't receive pop-up notifications in Outlook before they report messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageForJunk +Don't use this parameter. Use the PreSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageForNotJunk +Don't use this parameter. Use the PreSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageForPhishing +Don't use this parameter. Use the PreSubmitMessage parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitle +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. + +This parameter is meaningful only when the value of the PreSubmitMessageEnabled parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitleForJunk +Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitleForNotJunk +Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreSubmitMessageTitleForPhishing +Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportChatMessageEnabled +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportChatMessageToCustomizedAddressEnabled +{{ Fill ReportChatMessageToCustomizedAddressEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportJunkAddresses +**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 third-party reporting tools in Outlook. + +If you change the ReportJunkToCustomizedAddress parameter value to $false, you should set the value $null (blank) for this parameter. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkAddresses, ReportNotJunkAddresses and ReportPhishAddresses parameters. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportJunkToCustomizedAddress +The ReportJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or third-party 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. +- $false: User reported messages are not sent to the reporting mailbox. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameters in the same command. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportNotJunkAddresses +**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 third-party reporting tools in Outlook. + +If you change the ReportNotJunkToCustomizedAddress parameter value to $false, you should set the value $null (blank) for this parameter. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkAddresses, ReportNotJunkAddresses and ReportPhishAddresses parameters. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportNotJunkToCustomizedAddress +The ReportNotJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or third-party 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. +- $false: User reported messages are not sent to the reporting mailbox. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameters. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportPhishAddresses +**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 third-party reporting tools in Outlook. + +If you change the ReportPhishToCustomizedAddress parameter value to $false, you should set the value $null (blank) for this parameter. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkAddresses, ReportNotJunkAddresses and ReportPhishAddresses parameters. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportPhishToCustomizedAddress +The ReportPhishToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or third-party 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. +- $false: User reported messages are not sent to the reporting mailbox. + +You can't use this parameter by itself. You need to specify the same value for the ReportJunkToCustomizedAddress, ReportNotJunkToCustomizedAddress, and ReportPhishToCustomizedAddress parameters. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThirdPartyReportAddresses +**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 third-party product for user submissions instead of reporting in Outlook. + +If you change the EnableThirdPartyAddress parameter value to $false, you should set the value $null (blank) for this parameter. + +For more information about using third-party reporting tools with or without reporting in Outlook in favor of a third-party product, see the EnableThirdPartyAddress parameter. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserSubmissionOptions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserSubmissionOptionsMessage +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Set-ReportSubmissionRule.md new file mode 100644 index 0000000000..88878ff4a1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ReportSubmissionRule.md @@ -0,0 +1,193 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ReportSubmissionRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ReportSubmissionRule cmdlet to modify the report submission rule in your cloud-based organization. The report submission rule identifies the reporting mailbox where user reported messages are delivered. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ReportSubmissionRule [-Identity] <RuleIdParameter> + [-Comments <String>] + [-Confirm] + [-Name <String>] + [-ReportSubmissionPolicy <ReportSubmissionPolicyIdParameter>] + [-SentTo <RecipientIdParameter[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The SentTo parameter identifies the email address of the reporting mailbox. + +If you set the email address of the reporting mailbox in the Microsoft Defender portal at <https://security.microsoft.com/securitysettings/userSubmission>, the same email address is also set in the *\-ReportSubmissionPolicy cmdlets: + +- Microsoft integrated reporting using Microsoft reporting tools in Outlook: ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses (all three must be the same value). +- Microsoft integrated reporting using third-party reporting tools in Outlook: ThirdPartyReportAddresses. + +When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ReportSubmissionRule -Identity DefaultReportSubmissionRule -SentTo "userreportedmessages@contoso.onmicrosoft.com" +``` + +This example changes the reporting mailbox to userreportedmessages@contoso.onmicrosoft.com. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportSubmissionPolicy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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): + +- Microsoft integrated reporting is enabled using Microsoft reporting tools in Outlook: `-EnableThirdPartyAddress $false -ReportJunkToCustomizedAddress $true -ReportNotJunkToCustomizedAddress $true -ReportPhishToCustomizedAddress $true`. +- Microsoft integrated reporting is enabled using third-party reporting tools in Outlook: `-EnableReportToMicrosoft $false -EnableThirdPartyAddress $true -ReportJunkToCustomizedAddress $false -ReportNotJunkToCustomizedAddress $false -ReportPhishToCustomizedAddress $false`. + +If you set the email address of the reporting mailbox in the Microsoft Defender portal, the following parameters in the *\-ReportSubmissionPolicy cmdlets are set to the same value: + +- Microsoft integrated reporting using Microsoft reporting tools in Outlook: ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses (all three must be the same value). +- Microsoft integrated reporting using third-party reporting tools in Outlook: ThirdPartyReportAddresses. + +When you use this cmdlet to set the email address of the reporting mailbox, the related parameter values in the *\-ReportSubmissionPolicy cmdlets are not updated, which doesn't affect the functionality of the reporting mailbox. You should update the related values in the \*-ReportSubmissionPolicy cmdlets for consistency and to avoid confusion. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-ResourceConfig.md b/exchange/exchange-ps/exchange/Set-ResourceConfig.md similarity index 82% rename from exchange/exchange-ps/exchange/mailboxes/Set-ResourceConfig.md rename to exchange/exchange-ps/exchange/Set-ResourceConfig.md index fc7bbd3a7e..19453e4a45 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-ResourceConfig.md +++ b/exchange/exchange-ps/exchange/Set-ResourceConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-resourceconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-ResourceConfig @@ -17,19 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-ResourceConfig cmdlet to create custom resource properties that you can add to room and equipment mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ResourceConfig [-Confirm] [-DomainController <Fqdn>] [-ResourcePropertySchema <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] +Set-ResourceConfig [-Confirm] + [-DomainController <Fqdn>] + [-ResourcePropertySchema <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION After you use this cmdlet to create custom resource properties, you use the ResourceCustom parameter on the Set-Mailbox cmdlet to add one or more of those properties to a room or equipment mailbox. For more information, see the ResourceCustom parameter description in Set-Mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,8 +54,7 @@ This example adds the custom resource property Room/TV and removes Equipment/Lap ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -88,11 +89,11 @@ Accept wildcard characters: False ``` ### -ResourcePropertySchema -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/\<Text\> or Equipment/\<Text\> where the \<Text\> value doesn't contain spaces. For example, Room/Whiteboard or Equipment/Van. You can specify multiple values separated by commas. +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/<Text>` or `Equipment/<Text>` where the `<Text>` 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -128,12 +129,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-ResubmitRequest.md b/exchange/exchange-ps/exchange/Set-ResubmitRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Set-ResubmitRequest.md rename to exchange/exchange-ps/exchange/Set-ResubmitRequest.md index d0f55de588..222f007a7c 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-ResubmitRequest.md +++ b/exchange/exchange-ps/exchange/Set-ResubmitRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-resubmitrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ResubmitRequest @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ResubmitRequest cmdlet to enable or disable requests to replay redundant copies of messages from Safety Net after a mailbox database recovery. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ResubmitRequest [-Identity] <ResubmitRequestIdentityParameter> -Enabled <Boolean> [-Confirm] - [-Server <ServerIdParameter>] [-WhatIf] [<CommonParameters>] +Set-ResubmitRequest [-Identity] <ResubmitRequestIdentityParameter> -Enabled <Boolean> + [-Confirm] + [-Server <ServerIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -40,43 +42,42 @@ This example disables the resubmit request with the identity 8. ## PARAMETERS -### -Enabled -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. +### -Identity +The Identity parameter specifies the resubmit request you want to modify. Each resubmit request is identified by an incremented integer value. ```yaml -Type: Boolean +Type: ResubmitRequestIdentityParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the resubmit request you want to modify. Each resubmit request is identified by an incremented integer value. +### -Enabled +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: ResubmitRequestIdentityParameter +Type: Boolean Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -96,11 +97,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -139,12 +137,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md new file mode 100644 index 0000000000..c309e308bb --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md @@ -0,0 +1,1221 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-RetentionCompliancePolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-RetentionCompliancePolicy cmdlet to modify existing retention policies in the Microsoft Purview compliance portal. + +**Note**: Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to update multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. For information about the distribution status, see [Get-RetentionCompliancePolicy](https://learn.microsoft.com/powershell/module/exchange/get-retentioncompliancepolicy). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity +``` +Set-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> + [-AddExchangeLocation <MultiValuedProperty>] + [-AddExchangeLocationException <MultiValuedProperty>] + [-AddModernGroupLocation <MultiValuedProperty>] + [-AddModernGroupLocationException <MultiValuedProperty>] + [-AddOneDriveLocation <MultiValuedProperty>] + [-AddOneDriveLocationException <MultiValuedProperty>] + [-AddPublicFolderLocation <MultiValuedProperty>] + [-AddSharePointLocation <MultiValuedProperty>] + [-AddSharePointLocationException <MultiValuedProperty>] + [-AddSkypeLocation <MultiValuedProperty>] + [-AddSkypeLocationException <MultiValuedProperty>] + [-Applications <MultiValuedProperty>] + [-Comment <String>] + [-Confirm] + [-DeletedResources <String>] + [-Enabled <Boolean>] + [-EnforceSimulationPolicy <Boolean>] + [-Force] + [-PolicyTemplateInfo <PswsHashtable>] + [-PolicyRBACScopes <MultiValuedProperty>] + [-PriorityCleanup] + [-RemoveExchangeLocation <MultiValuedProperty>] + [-RemoveExchangeLocationException <MultiValuedProperty>] + [-RemoveModernGroupLocation <MultiValuedProperty>] + [-RemoveModernGroupLocationException <MultiValuedProperty>] + [-RemoveOneDriveLocation <MultiValuedProperty>] + [-RemoveOneDriveLocationException <MultiValuedProperty>] + [-RemovePublicFolderLocation <MultiValuedProperty>] + [-RemoveSharePointLocation <MultiValuedProperty>] + [-RemoveSharePointLocationException <MultiValuedProperty>] + [-RemoveSkypeLocation <MultiValuedProperty>] + [-RemoveSkypeLocationException <MultiValuedProperty>] + [-RestrictiveRetention <Boolean>] + [-StartSimulation <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +### AdaptiveScopeLocation +``` +Set-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> [-AddAdaptiveScopeLocation <MultiValuedProperty>] + [-Applications <MultiValuedProperty>] + [-Comment <String>] + [-Confirm] + [-DeletedResources <String>] + [-Enabled <Boolean>] + [-EnforceSimulationPolicy <Boolean>] + [-Force] + [-PriorityCleanup] + [-RemoveAdaptiveScopeLocation <MultiValuedProperty>] + [-StartSimulation <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +### RetryDistribution +``` +Set-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> [-RetryDistribution] + [-Confirm] + [-DeletedResources <String>] + [-EnforceSimulationPolicy <Boolean>] + [-PriorityCleanup] + [-StartSimulation <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +### TeamLocation +``` +Set-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> + [-AddTeamsChannelLocation <MultiValuedProperty>] + [-AddTeamsChannelLocationException <MultiValuedProperty>] + [-AddTeamsChatLocation <MultiValuedProperty>] + [-AddTeamsChatLocationException <MultiValuedProperty>] + [-Comment <String>] + [-Confirm] + [-DeletedResources <String>] + [-Enabled <Boolean>] + [-EnforceSimulationPolicy <Boolean>] + [-Force] + [-PriorityCleanup] + [-RemoveTeamsChannelLocation <MultiValuedProperty>] + [-RemoveTeamsChannelLocationException <MultiValuedProperty>] + [-RemoveTeamsChatLocation <MultiValuedProperty>] + [-RemoveTeamsChatLocationException <MultiValuedProperty>] + [-StartSimulation <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +**Note**: Don't use a piped Foreach-Object command when adding or removing scope locations: `"Value1","Value2",..."ValueN" | Foreach-Object {Set-RetentionCompliancePolicy -Identity "Regulation 123 Compliance" -RemoveExchangeLocation $_}`. + +## EXAMPLES + +### Example 1 +```powershell +Set-RetentionCompliancePolicy -Identity "Regulation 123 Compliance" -AddExchangeLocation "Kitty Petersen" -AddSharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -RemovePublicFolderLocation All -Comment "Added new counsel, 9/9/14" +``` + +This example makes the following changes to the existing retention policy named "Regulation 123 Compliance": + +- Adds the mailbox for the user named Kitty Petersen. +- Adds the SharePoint site `https://contoso.sharepoint.com/sites/teams/finance`. +- Removes public folders. +- Updates the comment. + +### Example 2 +```powershell +$stringJson = @" +[{ + 'EmailAddress': 'USSales@contoso.onmicrosoft.com', + 'SiteId': '9b2a8116-b9ec-4e2c-bf31-7eaa83697c4b' +}] +"@ + +Set-RetentionCompliancePolicy -Identity "Sales Policy" -RemoveModernGroupLocation "USSales@contoso.onmicrosoft.com" -DeletedResources $stringJson +``` + +The example removes the specified deleted Microsoft 365 Group and site from the specified policy. You identify the deleted resources using the Microsoft 365 Group email address and the related site ID. + +**IMPORTANT**: Before you run this command, make sure you read the Caution information for the [DeletedResources parameter](#-deletedresources) about duplicate SMTP addresses. + +### Example 3 +```powershell +$stringJson = @" +[{ + 'EmailAddress': 'USSales@contoso.onmicrosoft.com', + 'SiteId': '8b2a8345-b9ec-3b6a-bf31-6eaa83697c4b' +}] +"@ + +Set-RetentionCompliancePolicy -Identity "Tenant Level Policy" -AddModernGroupLocationException "USSales@contoso.onmicrosoft.com" -DeletedResources $stringJson +``` + +The example excludes the specified deleted Microsoft 365 Group and site from the specified tenant level policy. You identify the deleted resources using the Microsoft 365 Group email address and the related site ID. + +**IMPORTANT**: Before you run this command, make sure you read the Caution information for the [DeletedResources parameter](#-deletedresources) about duplicate SMTP addresses. + +### Example 4 +```powershell +$stringJson = @" +[{ + 'EmailAddress': 'USSales2@contoso.onmicrosoft.com', + 'SiteId': '9b2a8116-b9ec-4e2c-bf31-7eaa83697c4b' + }, +{ + 'EmailAddress': 'USSales2@contoso.onmicrosoft.com', + 'SiteId': '4afb7116-b9ec-4b2c-bf31-4abb83697c4b' +}] +"@ + +Set-RetentionCompliancePolicy -Identity "Sales Policy" -RemoveModernGroupLocation "USSales2@contoso.onmicrosoft.com" -DeletedResources $stringJson +``` + +This example is similar to Example 2, except multiple deleted resources are specified. + +**IMPORTANT**: Before you run this command, make sure you read the Caution information for the [DeletedResources parameter](#-deletedresources) about duplicate SMTP addresses. + +### Example 5 +```powershell +$stringJson = @" +[{ + 'EmailAddress': 'SalesUser@contoso.onmicrosoft.com' +}] +"@ + +Set-RetentionCompliancePolicy -Identity "Teams Chat Retention Policy" -AddTeamsChatLocationException "SalesUser@contoso.onmicrosoft.com" -DeletedResources $stringJson +``` + +This example excludes the specified soft-deleted mailbox or mail user from the mentioned Teams Retention Policy. You can identify the deleted resources using the mailbox or mail user's email address. + +**IMPORTANT**: Before you run this command, make sure you read the Caution information for the [DeletedResources parameter](#-deletedresources) about duplicate SMTP addresses. + +### Example 6 +```powershell +$stringJson = @" +[{ + 'EmailAddress': 'SalesUser1@contoso.onmicrosoft.com' +}, +{ + 'EmailAddress': 'SalesUser2@contoso.onmicrosoft.com' +}] +"@ + +Set-RetentionCompliancePolicy -Identity "Teams Chat Retention Policy" -AddTeamsChatLocationException "SalesUser1@contoso.onmicrosoft.com", "SalesUser2@contoso.onmicrosoft.com" -DeletedResources $stringJson +``` + +This example is similar to Example 5, except multiple deleted resources are specified. + +**IMPORTANT**: Before you run this command, make sure you read the Caution information for the [DeletedResources parameter](#-deletedresources) about duplicate SMTP addresses. + +Policy exclusions must remain within the supported limits for retention policies: [Limits for Microsoft 365 retention policies and retention label policies](https://learn.microsoft.com/purview/retention-limits#maximum-number-of-items-per-policy) + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -RetryDistribution +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. + +```yaml +Type: SwitchParameter +Parameter Sets: RetryDistribution +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddAdaptiveScopeLocation +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 +- Distinguished name (DN) +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocation +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 +- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddExchangeLocationException +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 +- A distribution group or mail-enabled security group + +To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddModernGroupLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddModernGroupLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddOneDriveLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddPublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocation +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"`. + +SharePoint sites can't be added to the policy until they have been indexed. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSharePointLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSkypeLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddSkypeLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddTeamsChannelLocation +The AddTeamsChannelLocation parameter specifies the Teams to add to the policy. + +You can use any value that uniquely identifies the team. For example: + +- Name +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddTeamsChannelLocationException +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 +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddTeamsChatLocation +The AddTeamsChatLocation parameter specifies the Teams users to add to the policy. + +You can use any value that uniquely identifies the user. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AddTeamsChatLocationException +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 +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Applications +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. +- `Group:SharePoint` for the SharePoint site that's connected to the Microsoft 365 Group. +- `"Group:Exchange,SharePoint"` for both the mailbox and the SharePoint site that are connected to the Microsoft 365 Group. +- blank (`$null`): This is the default value, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. To return to the default value of both the mailbox and SharePoint site for the selected Microsoft 365 groups, specify `"Group:Exchange,SharePoint"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeletedResources +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. + +**CAUTION**: When you use a SMTP address with this parameter, be aware that the same address might also be in use for other mailboxes or mail users. To check for additional mailboxes or mail users with the same SMTP address, use the following command and replace `user@contoso.com` with the SMTP address to check: `Get-Recipient -IncludeSoftDeletedRecipients user@contoso.com | Select-Object DisplayName, EmailAddresses, Description, Alias, RecipientTypeDetails, WhenSoftDeleted` + +To prevent active mailboxes or mail users with the same SMTP address from being excluded, put the mailbox on [Litigation Hold](https://learn.microsoft.com/purview/ediscovery-create-a-litigation-hold) before you run the command with the DeletedResources parameter. + +For more information about the deleted Microsoft 365 Group scenario, see [Learn more about modern group deletion under retention hold](https://learn.microsoft.com/purview/retention-settings#what-happens-if-a-microsoft-365-group-is-deleted-after-a-policy-is-applied). + +For more information about the inactive mailbox scenario, see [Learn about inactive mailboxes](https://learn.microsoft.com/purview/inactive-mailboxes-in-office-365). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: Identity, TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnforceSimulationPolicy +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. +- $false: Don't enforce the simulation policy as an active policy. This is the default value. + +For more information about simulation mode, see [Learn about simulation mode](https://learn.microsoft.com/purview/apply-retention-labels-automatically#learn-about-simulation-mo). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: Identity, TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +**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. + +Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTemplateInfo +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PswsHashtable +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveAdaptiveScopeLocation +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 +- Distinguished name (DN) +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: AdaptiveScopeLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveExchangeLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveModernGroupLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveModernGroupLocationException +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveOneDriveLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemovePublicFolderLocation +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocation +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSharePointLocationException +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSkypeLocation +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: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSkypeLocationException +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictiveRetention +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. +- $false: Preservation Lock isn't enabled for the policy. This is the default value. + +After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only way that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. + +Therefore, before you lock a policy for retention, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. + +```yaml +Type: Boolean +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveTeamsChannelLocation +The RemoveTeamsChannelLocation parameter specifies the Teams to remove from the policy. + +You can use any value that uniquely identifies the team. For example: + +- Name +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveTeamsChannelLocationException +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 +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveTeamsChatLocation +The RemoveTeamsChatLocation parameter specifies the Teams users to remove from the policy. + +You can use any value that uniquely identifies the user. For example: + +- Name +- Distinguished name (DN) +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveTeamsChatLocationException +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 +- Email address +- GUID + +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: TeamLocation +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartSimulation +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. +- $false: Don't start the simulation. This is the default value. + +For more information about simulation mode, see [Learn about simulation mode](https://learn.microsoft.com/purview/apply-retention-labels-automatically#learn-about-simulation-mo). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md new file mode 100644 index 0000000000..3a544e128a --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md @@ -0,0 +1,384 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-RetentionComplianceRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-RetentionComplianceRule cmdlet to modify existing retention rules in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-RetentionComplianceRule [-Identity] <ComplianceRuleIdParameter> + [-ApplyComplianceTag <String>] + [-Comment <String>] + [-Confirm] + [-ContentContainsSensitiveInformation <PswsHashtable[]>] + [-ContentDateFrom <DateTime>] + [-ContentDateTo <DateTime>] + [-ContentMatchQuery <String>] + [-ExcludedItemClasses <MultiValuedProperty>] + [-ExpirationDateOption <String>] + [-IRMRiskyUserProfiles <String>] + [-PriorityCleanup] + [-RetentionComplianceAction <String>] + [-RetentionDuration <Unlimited>] + [-RetentionDurationDisplayHint <HoldDurationHint>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-RetentionComplianceRule -Identity "Internal Company Rule" -RetentionDuration 180 -RetentionDurationDisplayHint Days +``` + +This example changes the hold duration for the existing retention rule named "Internal Company Rule". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ApplyComplianceTag +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. + +You can't use this parameter with the Name or PublishComplianceTag parameters. + +You can't use this parameter for Teams retention rules. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +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"})`. + +Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://learn.microsoft.com/exchange/what-the-sensitive-information-types-in-exchange-look-for-exchange-online-help). + +You can't use this parameter for Teams retention rules. + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateFrom +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentDateTo +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchQuery +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). + +You can't use this parameter for Teams retention rules. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludedItemClasses +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 +- IPM.Note.Microsoft.Conversation.Voice +- IPM.Note.Microsoft.Missed +- IPM.Note.Microsoft.Missed.Voice +- IPM.Note.Microsoft.Voicemail +- IPM.Note.Microsoft.VoiceMessage.UA +- IPM.Note.Microsoft.Voicemail.UM +- IPM.Note.Microsoft.Voicemail.UM.CA + +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or third-party message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. + +You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. + +You can't use this parameter for Teams retention rules. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpirationDateOption +The ExpirationDateOption parameter specifies whether the expiration date is calculated from the content creation date or last modification date. Valid values are: + +- CreationAgeInDays +- ModificationAgeInDays + +You can't use this parameter for Teams retention rules. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IRMRiskyUserProfiles +{{ Fill IRMRiskyUserProfiles Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionComplianceAction +The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: + +- Delete +- Keep +- KeepAndDelete + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies the hold duration for the retention rule. Valid values are: + +- An integer: The hold duration in days. +- Unlimited: The content is held indefinitely. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDurationDisplayHint +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 +- Months +- Years + +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. + +You can't use this parameter for Teams retention rules. + +```yaml +Type: HoldDurationHint +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-RetentionPolicy.md b/exchange/exchange-ps/exchange/Set-RetentionPolicy.md new file mode 100644 index 0000000000..14102c1ff4 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-RetentionPolicy.md @@ -0,0 +1,254 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-RetentionPolicy + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Set-RetentionPolicy cmdlet to change the properties of an existing retention policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-RetentionPolicy [-Identity] <MailboxPolicyIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-Force] + [-IsDefault] + [-IsDefaultArbitrationMailbox] + [-Name <String>] + [-RetentionId <Guid>] + [-RetentionPolicyTagLinks <RetentionPolicyTagIdParameter[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-RetentionPolicy "MyPolicy" -RetentionPolicyTagLinks "MyRetentionPolicyTag" +``` + +This example modifies the policy MyPolicy to link the retention policy tag MyRetentionPolicyTag with it. + +The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDefault +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. + +When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. + +**Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans: + +- $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes. +- A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as the default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). + +If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. + +Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDefaultArbitrationMailbox +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. + +This parameter isn't available in on-premises deployments. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionId +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. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionPolicyTagLinks +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/policy-and-compliance-retention/Set-RetentionPolicyTag.md b/exchange/exchange-ps/exchange/Set-RetentionPolicyTag.md similarity index 91% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionPolicyTag.md rename to exchange/exchange-ps/exchange/Set-RetentionPolicyTag.md index de79d0471b..f4d7334536 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionPolicyTag.md +++ b/exchange/exchange-ps/exchange/Set-RetentionPolicyTag.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-retentionpolicytag +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-RetentionPolicyTag @@ -17,9 +16,9 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-RetentionPolicyTag cmdlet to modify the properties of a retention tag. -For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). +For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -43,8 +42,10 @@ Set-RetentionPolicyTag [-Identity] <RetentionPolicyTagIdParameter> [-Name <String>] [-RetentionAction <RetentionAction>] [-RetentionEnabled <Boolean>] - [-RetentionId <Guid>] [-SystemTag <Boolean>] - [-WhatIf] [<CommonParameters>] + [-RetentionId <Guid>] + [-SystemTag <Boolean>] + [-WhatIf] + [<CommonParameters>] ``` ### MailboxTask @@ -62,13 +63,14 @@ Set-RetentionPolicyTag -Mailbox <MailboxIdParameter> [-OptionalInMailbox <RetentionPolicyTagIdParameter[]>] [-RetentionId <Guid>] [-SystemTag <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION Retention tags are used to apply message retention settings to folders and items in a mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -108,23 +110,14 @@ Accept wildcard characters: False The Mailbox parameter specifies a mailbox for assigning opt-in tags. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) You must use this parameter with the OptionalInMailbox parameter. @@ -143,12 +136,12 @@ Accept wildcard characters: False ``` ### -AddressForJournaling -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. ```yaml -Type: Object +Type: RecipientIdParameter Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010 @@ -195,8 +188,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -231,7 +223,9 @@ Accept wildcard characters: False ``` ### -Force -The Force switch overrides the confirmation prompt displayed by the cmdlet when you use the RetentionId parameter. +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. ```yaml Type: SwitchParameter @@ -247,12 +241,12 @@ Accept wildcard characters: False ``` ### -JournalingEnabled -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. ```yaml -Type: Object +Type: Boolean Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010 @@ -265,7 +259,7 @@ Accept wildcard characters: False ``` ### -LabelForJournaling -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -353,7 +347,7 @@ Accept wildcard characters: False ``` ### -MessageFormatForJournaling -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -422,11 +416,8 @@ Accept wildcard characters: False 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. - - MarkAsPastRetentionLimit: Messages are marked as past the retention limit. - - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal, and RecoverableItems. - - PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1). @@ -451,7 +442,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to 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. -When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as DISABLED\_\<Original Name\>. +When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_<Original Name>`. ```yaml Type: Boolean @@ -469,7 +460,7 @@ Accept wildcard characters: False ### -RetentionId 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). -It's not ordinarily required to specify or modify the RetentionId parameter for a retention tag. The parameter is populated automatically by \<scriptname\> when importing retention tags in a cross-forest or cross-premises deployment. +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. ```yaml Type: Guid @@ -521,12 +512,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Set-RoleAssignmentPolicy.md b/exchange/exchange-ps/exchange/Set-RoleAssignmentPolicy.md similarity index 88% rename from exchange/exchange-ps/exchange/role-based-access-control/Set-RoleAssignmentPolicy.md rename to exchange/exchange-ps/exchange/Set-RoleAssignmentPolicy.md index 694c373810..eca66e5008 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Set-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/exchange/Set-RoleAssignmentPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/set-roleassignmentpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-RoleAssignmentPolicy @@ -17,21 +16,27 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-RoleAssignmentPolicy cmdlet to modify existing management role assignment policies in your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-RoleAssignmentPolicy [-Identity] <MailboxPolicyIdParameter> [-Confirm] [-Description <String>] - [-DomainController <Fqdn>] [-IsDefault] [-Name <String>] [-WhatIf] [<CommonParameters>] +Set-RoleAssignmentPolicy [-Identity] <MailboxPolicyIdParameter> + [-Confirm] + [-Description <String>] + [-DomainController <Fqdn>] + [-IsDefault] + [-Name <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION You can use the Set-RoleAssignmentPolicy cmdlet to change the name of an assignment policy or to set the assignment policy as the default assignment policy. -For more information about assignment policies, see [Understanding management role assignment policies](https://docs.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). +For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,7 +121,7 @@ Accept wildcard characters: False ``` ### -IsDefault -The IsDefault switch makes the assignment policy the default assignment policy. You don't have to specify a value with this switch. +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. @@ -171,12 +175,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Set-RoleGroup.md b/exchange/exchange-ps/exchange/Set-RoleGroup.md similarity index 77% rename from exchange/exchange-ps/exchange/role-based-access-control/Set-RoleGroup.md rename to exchange/exchange-ps/exchange/Set-RoleGroup.md index 7e521612be..b0c9fd04a3 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Set-RoleGroup.md +++ b/exchange/exchange-ps/exchange/Set-RoleGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/set-rolegroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" --- # Set-RoleGroup @@ -17,13 +16,14 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-RoleGroup cmdlet to modify who can add or remove members to or from management role groups or change the name of the role group. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### CrossForest ``` -Set-RoleGroup [-Identity] <RoleGroupIdParameter> -LinkedDomainController <String> -LinkedForeignGroup <UniversalSecurityGroupIdParameter> [-LinkedCredential <PSCredential>] +Set-RoleGroup [-Identity] <RoleGroupIdParameter> -LinkedDomainController <String> -LinkedForeignGroup <UniversalSecurityGroupIdParameter> + [-LinkedCredential <PSCredential>] [-BypassSecurityGroupManagerCheck] [-Confirm] [-Description <String>] @@ -31,19 +31,23 @@ Set-RoleGroup [-Identity] <RoleGroupIdParameter> -LinkedDomainController <String [-DomainController <Fqdn>] [-ManagedBy <MultiValuedProperty>] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Default ``` -Set-RoleGroup [-Identity] <RoleGroupIdParameter> [-Force] +Set-RoleGroup [-Identity] <RoleGroupIdParameter> + [-Force] [-BypassSecurityGroupManagerCheck] [-Confirm] [-Description <String>] [-DisplayName <String>] [-ManagedBy <MultiValuedProperty>] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WellKnownObject <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -51,9 +55,9 @@ If you want to add or remove members to or from an existing role group, use the If the ManagedBy property is populated with role group managers, the user configuring a role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -73,7 +77,9 @@ This example sets the role group managers list to the Seattle Role Administrator ### Example 3 ```powershell -$Credentials = Get-Credential; Set-RoleGroup "ContosoUsers: Toronto Recipient Admins" -LinkedDomainController dc02.contosousers.contoso.com -LinkedCredential $Credentials -LinkedForeignGroup "Toronto Tier 2 Administrators" +$Credentials = Get-Credential + +Set-RoleGroup "ContosoUsers: Toronto Recipient Admins" -LinkedDomainController dc02.contosousers.contoso.com -LinkedCredential $Credentials -LinkedForeignGroup "Toronto Tier 2 Administrators" ``` This example modifies the linked foreign USG on the existing linked role group ContosoUsers: Toronto Recipient Admins. The foreign USG that should be linked is Toronto Tier 2 Administrators. @@ -89,7 +95,7 @@ The Identity parameter specifies the name of the role group to modify. If the na Type: RoleGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: 1 @@ -141,13 +147,18 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch enables a user who hasn't been added to the ManagedBy property to modify a role group. The user must be a member of the Organization Management role group or be assigned, either directly or indirectly, the Role Management role. +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: + +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +- Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -159,15 +170,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -183,7 +193,7 @@ The Description parameter specifies the description displayed when the role grou Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -193,13 +203,13 @@ Accept wildcard characters: False ``` ### -DisplayName -The DisplayName parameter specifies the friendly name of the role group. If the name contains spaces, enclose the name in quotation marks ("). This parameter can have a maximum length of 256 characters. +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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -227,13 +237,17 @@ Accept wildcard characters: False ``` ### -Force -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. +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. + +You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. ```yaml Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -247,7 +261,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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). You can only use the LinkedCredential parameter with a linked role group. @@ -263,7 +277,7 @@ Accept wildcard characters: False ``` ### -ManagedBy -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://docs.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). +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 ("). @@ -273,7 +287,7 @@ 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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -289,7 +303,25 @@ The Name parameter specifies the name of the role group. The name can contain up Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WellKnownObject +This parameter is available only in the cloud-based service. + +{{ Fill WellKnownObject Description }} + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -299,7 +331,7 @@ Accept wildcard characters: False ``` ### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. +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. @@ -307,7 +339,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -321,12 +353,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-RoutingGroupConnector.md b/exchange/exchange-ps/exchange/Set-RoutingGroupConnector.md similarity index 90% rename from exchange/exchange-ps/exchange/mail-flow/Set-RoutingGroupConnector.md rename to exchange/exchange-ps/exchange/Set-RoutingGroupConnector.md index b8f058d8d5..d17b041270 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-RoutingGroupConnector.md +++ b/exchange/exchange-ps/exchange/Set-RoutingGroupConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-routinggroupconnector +online version: https://learn.microsoft.com/powershell/module/exchange/set-routinggroupconnector applicable: Exchange Server 2010 title: Set-RoutingGroupConnector schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-RoutingGroupConnector @@ -17,15 +16,22 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-RoutingGroupConnector cmdlet to modify the properties of an existing routing group connector between a Microsoft Exchange Server 2010 routing group and an Exchange Server 2003 routing group. You can also use this cmdlet to configure the maximum message size that can pass across a routing group connector. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-RoutingGroupConnector [-Identity] <RoutingGroupConnectorIdParameter> [-Confirm] [-Cost <Int32>] - [-DomainController <Fqdn>] [-MaxMessageSize <Unlimited>] [-Name <String>] - [-PublicFolderReferralsEnabled <Boolean>] [-SourceTransportServers <MultiValuedProperty>] - [-TargetTransportServers <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] +Set-RoutingGroupConnector [-Identity] <RoutingGroupConnectorIdParameter> + [-Confirm] + [-Cost <Int32>] + [-DomainController <Fqdn>] + [-MaxMessageSize <Unlimited>] + [-Name <String>] + [-PublicFolderReferralsEnabled <Boolean>] + [-SourceTransportServers <MultiValuedProperty>] + [-TargetTransportServers <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -33,7 +39,7 @@ The Set-RoutingGroupConnector cmdlet modifies the properties of an existing rout The Exchange 2003 source servers specified in this cmdlet are automatically added to the ExchangeLegacyInterop universal security group. By default, the Exchange 2010 system grants Send to and Receive from permissions on the Hub Transport servers to members of this group. The source and target servers must be computers that have the Exchange 2010 Hub Transport server role installed, or Exchange 2003 bridgehead servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,9 +51,7 @@ Set-RoutingGroupConnector -Identity "Exchange Administrative Group (FYDIBOHF23SP This example makes the following configuration changes to the routing group connector Ex2010 to Ex2003 RGC: - Sets the cost to 70. - - Sets a maximum message size limit of 10 MB. - - Specifies new source and target servers for the connector. ## PARAMETERS @@ -71,8 +75,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -124,11 +127,8 @@ Accept wildcard characters: False 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) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are treated as bytes. The valid input range for this parameter is from 64KB through Int64. To remove the message size limit on a Send connector, enter a value of unlimited. @@ -179,7 +179,7 @@ Accept wildcard characters: False ``` ### -SourceTransportServers -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://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb684908(v=exchg.141)). +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 @@ -195,7 +195,7 @@ Accept wildcard characters: False ``` ### -TargetTransportServers -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://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb684908(v=exchg.141)). +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 @@ -231,12 +231,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-RpcClientAccess.md b/exchange/exchange-ps/exchange/Set-RpcClientAccess.md similarity index 91% rename from exchange/exchange-ps/exchange/client-access-servers/Set-RpcClientAccess.md rename to exchange/exchange-ps/exchange/Set-RpcClientAccess.md index e20c15a4d1..970b171e11 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-RpcClientAccess.md +++ b/exchange/exchange-ps/exchange/Set-RpcClientAccess.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-rpcclientaccess +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-RpcClientAccess @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-RpcClientAccess cmdlet to modify the settings of the Microsoft Exchange RPC Client Access service on Exchange servers that have the Client Access server role installed. These settings affect Outlook clients that connect by using Outlook Anywhere (RPC over HTTP). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ Set-RpcClientAccess -Server <ServerIdParameter> [-EncryptionRequired <Boolean>] [-MaximumConnections <Int32>] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -37,7 +37,7 @@ Outlook 2007 isn't supported in Exchange 2016 or later, so you shouldn't see Out To block Outlook versions for specific mailboxes, use the Set-CASMailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,7 +55,7 @@ Set-RpcClientAccess -Server MBX01 -BlockedClientVersions 15.0.0-15.4737.999 This example prevents Outlook Anywhere connections by Outlook 2013 clients that don't have KB3054940 installed (version 15.0.4737.1000) on the server named MBX01. -Note: You can determine specific client software versions by parsing the RPC Client Access log files located at %ExchangeInstallPath%Logging\\RPC Client Access. +**Note**: You can determine specific client software versions by parsing the RPC Client Access log files located at %ExchangeInstallPath%Logging\\RPC Client Access. ## PARAMETERS @@ -63,11 +63,8 @@ Note: You can determine specific client software versions by parsing the RPC Cli 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 - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -89,9 +86,7 @@ The BlockedClientVersions parameter specifies the RPC client versions that aren' 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. - X is the major version number. For example, Outlook 2016 is 16, Outlook 2013 is 15, and Outlook 2010 is 14. - - Y is the minor revision number, and must be less than or equal to 32767. - - Z is the build number, and must be less than or equal to 65535. You can specify ranges. For example, -13.32767.65535, 14.0.0-14.32767.65535, or 15.0.0-. @@ -116,8 +111,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -153,7 +147,6 @@ Accept wildcard characters: False 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. - - $false: Unencrypted RPC client connections are allowed. ```yaml @@ -172,7 +165,7 @@ Accept wildcard characters: False ### -MaximumConnections 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. +**Note**: Although you can configure a non-default value for this parameter, changes to this setting aren't enforced. ```yaml Type: Int32 @@ -224,12 +217,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md new file mode 100644 index 0000000000..fbaa17c621 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md @@ -0,0 +1,246 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-SafeAttachmentPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-SafeAttachmentPolicy cmdlet to modify safe attachment policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-SafeAttachmentPolicy [-Identity] <SafeAttachmentPolicyIdParameter> + [-Action <SafeAttachmentAction>] + [-AdminDisplayName <String>] + [-Confirm] + [-Enable <Boolean>] + [-QuarantineTag <String>] + [-Redirect <Boolean>] + [-RedirectAddress <SmtpAddress>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +A safe attachment policy can be assigned to only one safe attachment rule by using the SafeAttachmentPolicy parameter on the New-SafeAttachmentRule or Set-SafeAttachmentRule cmdlets. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-SafeAttachmentsPolicy -Identity "Engineering Block Attachments" -QuarantineTag ContosoLimitedAccess +``` + +This example modifies the existing safe attachment policy named Engineering Block Attachments to set the quarantine policy to ContosoLimitedAccess. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: SafeAttachmentPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Action +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. +- Block: Block the email message that contains the malware attachment. This is the default value. +- DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies). + +The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false). + +To specify no action for the safe attachment policy (corresponds to the value **Off** for the **Safe Attachments unknown malware response** policy setting in the Defender portal), use the value $false for the Enable parameter. + +The results of all actions are available in message trace. + +```yaml +Type: SafeAttachmentAction +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enable +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. +- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. $false corresponds to the value **Off** for the **Safe Attachments unknown malware response** setting of the complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell). + +To enable or disable an existing Safe Attachments policy, use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages based on why the message was quarantined and quarantine notification settings. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +The default value for this parameter is the built-in quarantine policy named AdminOnlyAccessPolicy. This quarantine policy enforces the historical capabilities for messages that were quarantined as malware by Safe Attachments as described in the table [here](https://learn.microsoft.com/defender-office-365/quarantine-end-user). + +To view the list of available quarantine policies, run the following command: `Get-QuarantinePolicy | Format-List Name,EndUser*,ESNEnabled`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Redirect +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. +- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RedirectAddress +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. + +```yaml +Type: SmtpAddress +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Set-SafeAttachmentRule.md new file mode 100644 index 0000000000..985e31a012 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-SafeAttachmentRule.md @@ -0,0 +1,343 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-SafeAttachmentRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-SafeAttachmentRule cmdlet to modify safe attachment rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-SafeAttachmentRule [-Identity] <RuleIdParameter> + [-Comments <String>] + [-Confirm] + [-ExceptIfRecipientDomainIs <Word[]>] + [-ExceptIfSentTo <RecipientIdParameter[]>] + [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] + [-Name <String>] + [-Priority <Int32>] + [-RecipientDomainIs <Word[]>] + [-SafeAttachmentPolicy <SafeAttachmentPolicyIdParameter>] + [-SentTo <RecipientIdParameter[]>] + [-SentToMemberOf <RecipientIdParameter[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). + +A safe attachment policy can be assigned only to one safe attachment rule. + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-policy-settings). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-SafeAttachmentRule -Identity "Engineering Department Attachment Rule" -ExceptIfRecipientDomainIs fabrikam.com +``` + +This example modifies the existing safe attachment rule named Engineering Department Attachment Rule to exclude messages sent to the fabrikam.com domain. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SafeAttachmentPolicy +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: + +- Name +- Distinguished name (DN) +- GUID + +You can't specify a safe attachment policy that's already associated with another safe attachment rule. + +```yaml +Type: SafeAttachmentPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md new file mode 100644 index 0000000000..4587cee20b --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md @@ -0,0 +1,391 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-SafeLinksPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-SafeLinksPolicy cmdlet to modify Safe Links policies in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-SafeLinksPolicy [-Identity] <SafeLinksPolicyIdParameter> + [-AdminDisplayName <String>] + [-AllowClickThrough <Boolean>] + [-Confirm] + [-CustomNotificationText <String>] + [-DeliverMessageAfterScan <Boolean>] + [-DisableUrlRewrite <Boolean>] + [-DoNotRewriteUrls <MultiValuedProperty>] + [-EnableForInternalSenders <Boolean>] + [-EnableOrganizationBranding <Boolean>] + [-EnableSafeLinksForEmail <Boolean>] + [-EnableSafeLinksForOffice <Boolean>] + [-EnableSafeLinksForTeams <Boolean>] + [-ScanUrls <Boolean>] + [-TrackClicks <Boolean>] + [-UseTranslatedNotificationText <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links to see if they lead to malicious web sites. When a user clicks a link, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-SafeLinksPolicy -Identity "Engineering Block URL" -AllowClickThrough $false +``` + +This example modifies the existing Safe Links policy named Engineering Block URL to not allow click through to the original URLs on warning pages. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: SafeLinksPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowClickThrough +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. +$false: The user isn't allowed to click through to the original URL. + +In PowerShell, the default value is $false. In new Safe Links policies created in the Microsoft Defender portal, the default value is $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomNotificationText +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeliverMessageAfterScan +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. +- $false: If Safe Links scanning can't complete, deliver the message anyway. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableUrlRewrite +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). +- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. + +In PowerShell, the default value is $false. In new Safe Links policies created in the Microsoft Defender portal, the default value is $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DoNotRewriteUrls +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"`. + +For details about the entry syntax, see [Entry syntax for the "Do not rewrite the following URLs" list](https://learn.microsoft.com/defender-office-365/safe-links-about#entry-syntax-for-the-do-not-rewrite-the-following-urls-list). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableForInternalSenders +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. +- $false: The policy is applied only to external senders. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOrganizationBranding +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. +- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSafeLinksForEmail +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. +- $false: Safe Links isn't enabled for email. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSafeLinksForOffice +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. +- $false: Safe Links isn't enabled for Office apps. + +Note that this protection applies to links in Office documents, not links in email messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSafeLinksForTeams +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. +- $false: Safe Links isn't enabled for Teams. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScanUrls +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. +- $false: Real-time scanning of clicked links, including links that point to files, is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrackClicks +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. +- $false: User clicks aren't tracked. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseTranslatedNotificationText +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. +- $false: Don't translate custom notification text to the user's language. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-SafeLinksRule.md b/exchange/exchange-ps/exchange/Set-SafeLinksRule.md new file mode 100644 index 0000000000..6db4b01eeb --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-SafeLinksRule.md @@ -0,0 +1,359 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-SafeLinksRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-SafeLinksRule cmdlet to create Safe Links rules in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-SafeLinksRule [-Identity] <RuleIdParameter> + [-Comments <String>] + [-Confirm] + [-ExceptIfRecipientDomainIs <Word[]>] + [-ExceptIfSentTo <RecipientIdParameter[]>] + [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] + [-Name <String>] + [-Priority <Int32>] + [-RecipientDomainIs <Word[]>] + [-SafeLinksPolicy <SafeLinksPolicyIdParameter>] + [-SentTo <RecipientIdParameter[]>] + [-SentToMemberOf <RecipientIdParameter[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. + +> [!IMPORTANT] +> Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-policies). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-SafeLinksRule -Identity "Engineering Department URL Rule" -ExceptIfRecipientDomainIs fabrikam.com +``` + +This example modifies the existing Safe Links rule named Engineering Department URL Rule to exclude messages sent to recipients in the fabrikam.com domain. + +### Example 2 +```powershell +Set-SafeLinksRule -Identity "Contoso All" -RecipientDomainIs (Get-AcceptedDomain).Name +``` + +This example modifies the existing Safe Links rule named Contoso All to include messages sent to recipients in all accepted domains in the organization. + +### Example 3 +```powershell +$Data = Import-Csv -Path "C:\Data\SafeLinksDomains.csv" + +$SLDomains = $Data.Domains + +Set-SafeLinksRule -Identity "Contoso All" -RecipientDomainIs $SLDomains +``` + +This example is similar to Example 2, but in this example, the Safe Links rule includes messages sent to recipients in the accepted domains specified in a .csv file. + +## PARAMETERS + +### -Identity +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: + +- Name +- Distinguished name (DN) +- GUID + +```yaml +Type: RuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +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: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientDomainIs +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SafeLinksPolicy +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: + +- Name +- Distinguished name (DN) +- GUID + +You can't specify a Safe Attachments policy that's already associated with another Safe Attachments rule. + +```yaml +Type: SafeLinksPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-SearchDocumentFormat.md b/exchange/exchange-ps/exchange/Set-SearchDocumentFormat.md similarity index 84% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-SearchDocumentFormat.md rename to exchange/exchange-ps/exchange/Set-SearchDocumentFormat.md index e391a9f7a5..4288a07794 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Set-SearchDocumentFormat.md +++ b/exchange/exchange-ps/exchange/Set-SearchDocumentFormat.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/set-searchdocumentformat +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SearchDocumentFormat @@ -19,19 +18,22 @@ Use the Set-SearchDocumentFormat cmdlet to enable or disable the file format for When you disable a file format for content indexing by Exchange Search, contents of the file become unsearchable by Exchange Search clients such as Outlook on the web, Microsoft Outlook in online mode and In-Place eDiscovery. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SearchDocumentFormat [-Identity] <SearchDocumentFormatId> -Enabled <Boolean> [-Confirm] - [-Server <ServerIdParameter>] [-WhatIf] [<CommonParameters>] +Set-SearchDocumentFormat [-Identity] <SearchDocumentFormatId> -Enabled <Boolean> + [-Confirm] + [-Server <ServerIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -Exchange Search includes built-in support for indexing many file formats. If you disable indexing for a supported file format, items containing an attachment of that file type aren't considered unsearchable. When you perform an [In-Place eDiscovery in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) search and you select the option to include unsearchable items, only items that are actually unsearchable are returned. Items that weren't searched because the associated file format is set as unsearchable aren't returned. +Exchange Search includes built-in support for indexing many file formats. If you disable indexing for a supported file format, items containing an attachment of that file type aren't considered unsearchable. When you perform an [In-Place eDiscovery search in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and you select the option to include unsearchable items, only items that are actually unsearchable are returned. Items that weren't searched because the associated file format is set as unsearchable aren't returned. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,43 +46,42 @@ This command disables the Zip file format for indexing by Exchange Search. ## PARAMETERS -### -Enabled -The Enabled parameter specifies whether the file format is enabled. Set the parameter to $false to disable the format for content indexing. +### -Identity +The Identity parameter specifies the identity of the file format. ```yaml -Type: Boolean +Type: SearchDocumentFormatId Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the identity of the file format. +### -Enabled +The Enabled parameter specifies whether the file format is enabled. Set the parameter to $false to disable the format for content indexing. ```yaml -Type: SearchDocumentFormatId +Type: Boolean Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -100,11 +101,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -143,12 +141,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-SecOpsOverridePolicy.md b/exchange/exchange-ps/exchange/Set-SecOpsOverridePolicy.md new file mode 100644 index 0000000000..0c6e563991 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-SecOpsOverridePolicy.md @@ -0,0 +1,222 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-SecOpsOverridePolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-SecOpsOverridePolicy cmdlet to modify SecOps mailbox override policies to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-SecOpsOverridePolicy [-Identity] <PolicyIdParameter> + [-AddSentTo <MultiValuedProperty>] + [-Comment <String>] + [-Confirm] + [-DomainController <Fqdn>] + [-Enabled <Boolean>] + [-Force] + [-RemoveSentTo <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-SecOpsOverridePolicy -Identity SecOpsOverridePolicy -AddSentTo secops2@contoso.com +``` + +This example modifies the SecOPs mailbox override policy with the specified settings. + +## PARAMETERS + +### -Identity +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 +- Id +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AddSentTo +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The Enabled parameter specifies whether the policy is enabled. Valid values are: + +- $true: The policy is enabled. This is the default value. +- $false: The policy is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveSentTo +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this 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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-SendConnector.md b/exchange/exchange-ps/exchange/Set-SendConnector.md similarity index 84% rename from exchange/exchange-ps/exchange/mail-flow/Set-SendConnector.md rename to exchange/exchange-ps/exchange/Set-SendConnector.md index 06193c5df8..a8e6726d37 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-SendConnector.md +++ b/exchange/exchange-ps/exchange/Set-SendConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-sendconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SendConnector @@ -17,32 +16,53 @@ This cmdlet is available only in on-premises Exchange. Use the Set-SendConnector cmdlet to modify a Send connector. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SendConnector [-Identity] <SendConnectorIdParameter> [-AddressSpaces <MultiValuedProperty>] - [-AuthenticationCredential <PSCredential>] [-Comment <String>] [-Confirm] - [-ConnectionInactivityTimeOut <EnhancedTimeSpan>] [-DNSRoutingEnabled <Boolean>] - [-DomainController <Fqdn>] [-DomainSecureEnabled <Boolean>] [-Enabled <Boolean>] - [-ErrorPolicies <ErrorPolicies>] [-Force] - [-ForceHELO <Boolean>] [-Fqdn <Fqdn>] [-IgnoreSTARTTLS <Boolean>] - [-IsCoexistenceConnector <Boolean>] [-IsScopedConnector <Boolean>] - [-LinkedReceiveConnector <ReceiveConnectorIdParameter>] [-MaxMessageSize <Unlimited>] [-Name <String>] - [-Port <Int32>] [-ProtocolLoggingLevel <ProtocolLoggingLevel>] [-RequireOorg <Boolean>] +Set-SendConnector [-Identity] <SendConnectorIdParameter> + [-AddressSpaces <MultiValuedProperty>] + [-AuthenticationCredential <PSCredential>] + [-CloudServicesMailEnabled <Boolean>] + [-Comment <String>] + [-Confirm] + [-ConnectionInactivityTimeOut <EnhancedTimeSpan>] + [-ConnectorType <TenantConnectorType>] + [-DNSRoutingEnabled <Boolean>] + [-DomainController <Fqdn>] + [-DomainSecureEnabled <Boolean>] + [-Enabled <Boolean>] + [-ErrorPolicies <ErrorPolicies>] + [-Force] + [-ForceHELO <Boolean>] + [-Fqdn <Fqdn>] + [-FrontendProxyEnabled <Boolean>] + [-IgnoreSTARTTLS <Boolean>] + [-IsCoexistenceConnector <Boolean>] + [-IsScopedConnector <Boolean>] + [-LinkedReceiveConnector <ReceiveConnectorIdParameter>] + [-MaxMessageSize <Unlimited>] + [-Name <String>] + [-Port <Int32>] + [-ProtocolLoggingLevel <ProtocolLoggingLevel>] + [-RequireOorg <Boolean>] [-RequireTLS <Boolean>] [-SmartHostAuthMechanism <AuthMechanisms>] - [-SmartHosts <MultiValuedProperty>] [-SmtpMaxMessagesPerConnection <Int32>] [-SourceIPAddress <IPAddress>] + [-SmartHosts <MultiValuedProperty>] + [-SmtpMaxMessagesPerConnection <Int32>] + [-SourceIPAddress <IPAddress>] [-SourceTransportServers <MultiValuedProperty>] [-TlsAuthLevel <TlsAuthLevel>] - [-TlsDomain <SmtpDomainWithSubdomains>] [-UseExternalDNSServersEnabled <Boolean>] [-WhatIf] - [-CloudServicesMailEnabled <Boolean>] [-FrontendProxyEnabled <Boolean>] - [-TlsCertificateName <SmtpX509Identifier>] [-ConnectorType <TenantConnectorType>] [<CommonParameters>] + [-TlsCertificateName <SmtpX509Identifier>] + [-TlsDomain <SmtpDomainWithSubdomains>] + [-UseExternalDNSServersEnabled <Boolean>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,7 +74,6 @@ Set-SendConnector "Contoso.com Send Connector" -MaxMessageSize 10MB -ConnectionI This example makes the following configuration changes to the Send connector named Contoso.com Send Connector: - Sets the maximum message size limit to 10 MB. - - Changes the connection inactivity time-out to 15 minutes. ## PARAMETERS @@ -76,22 +95,17 @@ Accept wildcard characters: False ``` ### -AddressSpaces -The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is as follows: \<AddressSpaceType\>:\<AddressSpace\>;\<AddressSpaceCost\> +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. - - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com is not. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address space type, you can enter any text for the address space. - - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. This parameter is optional. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("). For example, the following address space entries are equivalent: - "SMTP:contoso.com;1" - - "contoso.com;1" - - "SMTP:contoso.com" - - contoso.com You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3". @@ -99,10 +113,9 @@ You may specify multiple address spaces by separating the address spaces with co If you specify a non-SMTP address space type on a Send connector configured in the Transport service on a Mailbox server, you must configure the following parameters: - The SmartHosts parameter must be set to a value that specifies a smart host. - - The DNSRoutingEnabled parameter must be set to $false. -Although you can configure non-SMTP address spaces on a Send connector in the Transport service on a Mailbox server, the Send connector uses SMTP as the transport mechanism to send messages to other messaging servers. Foreign connectors in the Transport service on a Mailbox server are used to send messages to local messaging servers, such as third-party fax gateway servers, which don't use SMTP as their primary transport mechanism. For more information, see [Foreign connectors](https://docs.microsoft.com/exchange/foreign-connectors-exchange-2013-help). +Although you can configure non-SMTP address spaces on a Send connector in the Transport service on a Mailbox server, the Send connector uses SMTP as the transport mechanism to send messages to other messaging servers. Foreign connectors in the Transport service on a Mailbox server are used to send messages to local messaging servers, such as third-party fax gateway servers, which don't use SMTP as their primary transport mechanism. For more information, see [Foreign connectors](https://learn.microsoft.com/exchange/foreign-connectors-exchange-2013-help). ```yaml Type: MultiValuedProperty @@ -120,7 +133,7 @@ Accept wildcard characters: False ### -AuthenticationCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -135,6 +148,29 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -CloudServicesMailEnabled +**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. + +Valid values are: + +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Comment TheComment parameter specifies an optional comment. You must enclose the Comment parameter in quotation marks ("), for example: "this is an admin note". @@ -154,8 +190,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -171,6 +206,25 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ConnectorType +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. +- XPremises: The connector is used to send messages to Microsoft 365. + +```yaml +Type: TenantConnectorType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ConnectionInactivityTimeOut The ConnectionInactivityTimeOut parameter specifies the maximum time an idle connection can remain open. The default value is ten minutes. @@ -229,9 +283,7 @@ Accept wildcard characters: False 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. - - The value of the DNSRoutingEnabled parameter must be $true. - - The value of the IgnoreStartTLS parameter must be $false. The wildcard character (\*) is not supported in domains that are configured for mutual TLS authentication. The same domain must also be defined on the corresponding Receive connector and in the TLSReceiveDomainSecureList attribute of the transport configuration. @@ -239,7 +291,6 @@ The wildcard character (\*) is not supported in domains that are configured for The default value for the DomainSecureEnabled parameter is $false for the following types of Send connectors: - All Send connectors defined in the Transport service on a Mailbox server. - - User-created Send connectors defined on an Edge server. The default value for the DomainSecureEnabled parameter is $true for default Send connectors defined on an Edge server. @@ -277,11 +328,8 @@ Accept wildcard characters: False 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. - - DowngradeDnsFailures: All DNS errors are treated as transient. - - DowngradeCustomFailures: Particular SMTP errors are treated as transient. - - UpgradeCustomFailures Custom transient failures are upgraded and treated as permanent failures. Multiple values can be specified for this parameter, separated by commas. @@ -302,7 +350,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -337,9 +387,7 @@ Accept wildcard characters: False 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 - - In the most recent Received header field added to the message by the next hop messaging server after the message leaves the Transport service on a Mailbox server or an Edge server - - During TLS authentication The default value of the Fqdn parameter is $null. This means the default FQDN value is the FQDN of the Mailbox server or Edge server that contains the Send connector. @@ -357,6 +405,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -FrontendProxyEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IgnoreSTARTTLS 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. @@ -374,9 +438,9 @@ Accept wildcard characters: False ``` ### -IsCoexistenceConnector -This parameter is available or functional only in 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 Office 365 organization. The default value is $false. +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. ```yaml Type: Boolean @@ -408,27 +472,21 @@ Accept wildcard characters: False ``` ### -LinkedReceiveConnector -This parameter is available or functional only in 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: - GUID - - Distinguished name (DN) - - Servername\\ConnectorName When you use the LinkedReceiveConnector parameter with this command, you must also use the following parameters with the specified values: -- AddressSpaces$null - -- DNSRoutingEnabled$false - -- MaxMessageSizeunlimited - -- Smarthosts \<SmarthostID\> - -- SmarthostAuthMechanism \<AuthMechanism\> +- `AddressSpaces $null` +- `DNSRoutingEnabled $false` +- `MaxMessageSize unlimited` +- `Smarthosts <SmarthostID>` +- `SmarthostAuthMechanism <AuthMechanism>` ```yaml Type: ReceiveConnectorIdParameter @@ -449,13 +507,9 @@ The MaxMessageSize parameter specifies the maximum size of a message that can pa When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -572,11 +626,11 @@ Accept wildcard characters: False ``` ### -SmartHosts -The SmartHosts parameter specifies the smart hosts the Send connector uses to route mail. This parameteris 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. +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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -626,9 +680,9 @@ Accept wildcard characters: False ### -SourceTransportServers 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -647,9 +701,7 @@ Accept wildcard characters: False 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. - - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - - DomainValidation: In addition to channel encryption and certificate validation, the Send connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. If no domain is specified in the TlsDomain parameter, the FQDN on the certificate is compared with the recipient's domain. You can't specify a value for this parameter if the IgnoreSTARTTLS parameter is set to $true, or if the RequireTLS parameter is set to $false. @@ -667,6 +719,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -TlsCertificateName +The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is `"<I>X.500Issuer<S>X.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 <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -TlsDomain 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. @@ -675,7 +743,6 @@ This parameter is used only if the TlsAuthLevel parameter is set to DomainValida A value for this parameter is required if: - The TLSAuthLevel parameter is set to DomainValidation. - - The DNSRoutingEnabled parameter is set to $false (smart host Send connector). ```yaml @@ -723,93 +790,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -CloudServicesMailEnabled -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://docs.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 Office 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. - -Valid values are: - -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - -- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FrontendProxyEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TlsCertificateName -The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\<I\>X.500Issuer\<S\>X.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 \<Thumbprint\>, run the command $TLSCertName = "\<I\>$($TLSCert.Issuer)\<S\>$($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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorType -The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Office 365. Valid values are: - -- Default: The connector isn't used to send messages to Office 365. This is the default value. - -- XPremises: The connector is used to send messages to Office 365. - -```yaml -Type: TenantConnectorType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderFilterConfig.md b/exchange/exchange-ps/exchange/Set-SenderFilterConfig.md similarity index 84% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderFilterConfig.md rename to exchange/exchange-ps/exchange/Set-SenderFilterConfig.md index 05da1f3fc2..1b634750be 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderFilterConfig.md +++ b/exchange/exchange-ps/exchange/Set-SenderFilterConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-senderfilterconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SenderFilterConfig @@ -17,20 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Set-SenderFilterConfig cmdlet to modify the Sender Filter agent configuration. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SenderFilterConfig [-Action <BlockedSenderAction>] [-BlankSenderBlockingEnabled <Boolean>] - [-BlockedDomains <MultiValuedProperty>] [-BlockedDomainsAndSubdomains <MultiValuedProperty>] - [-BlockedSenders <MultiValuedProperty>] [-Confirm] [-DomainController <Fqdn>] [-Enabled <Boolean>] - [-ExternalMailEnabled <Boolean>] [-InternalMailEnabled <Boolean>] - [-RecipientBlockedSenderAction <RecipientBlockedSenderAction>] [-WhatIf] [<CommonParameters>] +Set-SenderFilterConfig [-Action <BlockedSenderAction>] + [-BlankSenderBlockingEnabled <Boolean>] + [-BlockedDomains <MultiValuedProperty>] + [-BlockedDomainsAndSubdomains <MultiValuedProperty>] + [-BlockedSenders <MultiValuedProperty>] + [-Confirm] + [-DomainController <Fqdn>] + [-Enabled <Boolean>] + [-ExternalMailEnabled <Boolean>] + [-InternalMailEnabled <Boolean>] + [-RecipientBlockedSenderAction <RecipientBlockedSenderAction>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -86,9 +93,9 @@ The BlockedDomains parameter specifies the domain names to block. When the Sende 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. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The maximum number of entries for this parameter is 800. @@ -110,9 +117,9 @@ The BlockedDomainsAndSubdomains parameter specifies the domain names to block. W 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. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The maximum number of entries for this parameter is 800. @@ -132,9 +139,9 @@ Accept wildcard characters: False ### -BlockedSenders 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The maximum number of entries for this parameter is 800. @@ -154,8 +161,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -276,12 +282,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderIdConfig.md b/exchange/exchange-ps/exchange/Set-SenderIdConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderIdConfig.md rename to exchange/exchange-ps/exchange/Set-SenderIdConfig.md index 140ec6cd95..eaeddca576 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderIdConfig.md +++ b/exchange/exchange-ps/exchange/Set-SenderIdConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-senderidconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SenderIdConfig @@ -17,19 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Set-SenderIdConfig cmdlet to modify the configuration of the Sender ID agent. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SenderIdConfig [-BypassedRecipients <MultiValuedProperty>] [-BypassedSenderDomains <MultiValuedProperty>] - [-Confirm] [-DomainController <Fqdn>] [-Enabled <Boolean>] [-ExternalMailEnabled <Boolean>] - [-InternalMailEnabled <Boolean>] [-SpoofedDomainAction <SenderIdAction>] - [-TempErrorAction <SenderIdAction>] [-WhatIf] [<CommonParameters>] +Set-SenderIdConfig + [-BypassedRecipients <MultiValuedProperty>] + [-BypassedSenderDomains <MultiValuedProperty>] + [-Confirm] + [-DomainController <Fqdn>] + [-Enabled <Boolean>] + [-ExternalMailEnabled <Boolean>] + [-InternalMailEnabled <Boolean>] + [-SpoofedDomainAction <SenderIdAction>] + [-TempErrorAction <SenderIdAction>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,7 +48,6 @@ Set-SenderIdConfig -SpoofedDomainAction Delete -BypassedRecipients user1@contoso This example makes the following modifications to the Sender ID configuration: - It sets the Sender ID agent to delete all messages sent from spoofed domains. - - It specifies two recipients for the Sender ID agent to exclude when it processes messages. ## PARAMETERS @@ -81,8 +87,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -217,12 +222,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderReputationConfig.md b/exchange/exchange-ps/exchange/Set-SenderReputationConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderReputationConfig.md rename to exchange/exchange-ps/exchange/Set-SenderReputationConfig.md index 5a14bfb8af..610a9441ff 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-SenderReputationConfig.md +++ b/exchange/exchange-ps/exchange/Set-SenderReputationConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-senderreputationconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SenderReputationConfig @@ -17,21 +16,29 @@ This cmdlet is available only in on-premises Exchange. Use the Set-SenderReputationConfig cmdlet to modify the sender reputation configuration on Mailbox servers or Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SenderReputationConfig [-Confirm] [-DomainController <Fqdn>] [-Enabled <Boolean>] - [-ExternalMailEnabled <Boolean>] [-InternalMailEnabled <Boolean>] - [-OpenProxyDetectionEnabled <Boolean>] [-ProxyServerName <String>] [-ProxyServerPort <Int32>] +Set-SenderReputationConfig [-Confirm] + [-DomainController <Fqdn>] + [-Enabled <Boolean>] + [-ExternalMailEnabled <Boolean>] + [-InternalMailEnabled <Boolean>] + [-OpenProxyDetectionEnabled <Boolean>] + [-ProxyServerName <String>] + [-ProxyServerPort <Int32>] [-ProxyServerType <ProxyType>] - [-SenderBlockingEnabled <Boolean>] [-SenderBlockingPeriod <Int32>] [-SrlBlockThreshold <Int32>] - [-WhatIf] [<CommonParameters>] + [-SenderBlockingEnabled <Boolean>] + [-SenderBlockingPeriod <Int32>] + [-SrlBlockThreshold <Int32>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,8 +58,7 @@ It sets the number of hours that senders are put on the blocked senders list to ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -90,7 +96,6 @@ Accept wildcard characters: False 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. - - $false: Sender reputation is disabled. ```yaml @@ -110,7 +115,6 @@ Accept wildcard characters: False 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. - - $false: Sender reputation is disabled on mail from external sources. ```yaml @@ -130,7 +134,6 @@ Accept wildcard characters: False 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. - - $false: Sender reputation is disabled on mail from internal sources. This is the default value. ```yaml @@ -150,7 +153,6 @@ Accept wildcard characters: False 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. - - $false: Open proxy server detection is disabled. Open proxy server detection requires the following open outbound TCP ports in your firewall: 23, 80, 1080, 1081, 3128, and 6588. @@ -212,19 +214,12 @@ Accept wildcard characters: False 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. - - Cisco - - HttpConnect - - HttpPost - - Socks4 - - Socks5 - - Telnet - - Wingate ```yaml @@ -244,7 +239,6 @@ Accept wildcard characters: False 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. - - $false: Sender blocking is disabled. You can temporarily block senders for up to 48 hours when you use the SenderBlockingPeriod parameter. @@ -319,12 +313,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Set-ServerComponentState.md b/exchange/exchange-ps/exchange/Set-ServerComponentState.md similarity index 83% rename from exchange/exchange-ps/exchange/server-health-and-performance/Set-ServerComponentState.md rename to exchange/exchange-ps/exchange/Set-ServerComponentState.md index c87ca0379d..11c76cf3c6 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Set-ServerComponentState.md +++ b/exchange/exchange-ps/exchange/Set-ServerComponentState.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/set-servercomponentstate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ServerComponentState @@ -17,60 +16,56 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ServerComponentState cmdlet to configure and update Microsoft Exchange components and endpoints on servers you specify. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-ServerComponentState [-Identity] <ServerIdParameter> -Component <String> -Requester <String> - -State <ServiceState> +Set-ServerComponentState [-Identity] <ServerIdParameter> -Component <String> -Requester <String> -State <ServiceState> [-Confirm] [-DomainController <Fqdn>] [-LocalOnly] [-RemoteOnly] [-TimeoutInSeconds <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-ServerComponentState -Component UMCallRouter -Identity MailboxServer01 -Requester Maintenance -State Active +Set-ServerComponentState -Identity MailboxServer01 -Component UMCallRouter -Requester Maintenance -State Active ``` This example sets the Unified Messaging (UM) component state to Active, as requested by maintenance mode. -## PARAMETERS +### Example 2 +```powershell +Set-ServerComponentState -Identity Exch5 -Component ServerWideOffline -State Inactive -Requester Maintenance -### -Component -The Component parameter specifies the component or endpoint for which you want to set the state. +Set-ServerComponentState -Identity Exch5 -Component ServerWideOffline -State Active -Requester Maintenance +``` -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +This example prepares the server for maintenance, such as installing a Security Update or Cumulative Update. -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +The first command changes the state of all server components to Inactive. + +The second command changes the state to Active after the maintenance is over (required). + +**Note**: By design, the Microsoft Exchange IMAP4 and Microsoft Exchange POP3 services stop if the related `ImapProxy` and `PopProxy` components are in the Inactive state. You might need to manually restart the services after the related `ImapProxy` and `PopProxy` components are changed to the Active state. + +## PARAMETERS ### -Identity 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -86,17 +81,29 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -Component +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Requester The Requester parameter specifies the system requesting this state change. Valid values are: - HealthAPI - - Maintenance - - Sidelined - - Functional - - Deployment ```yaml @@ -116,9 +123,7 @@ Accept wildcard characters: False The State parameter specifies the state that you want for the component. Valid values are: - Active - - Inactive - - Draining ```yaml @@ -137,8 +142,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -241,12 +245,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Set-ServerMonitor.md b/exchange/exchange-ps/exchange/Set-ServerMonitor.md similarity index 90% rename from exchange/exchange-ps/exchange/server-health-and-performance/Set-ServerMonitor.md rename to exchange/exchange-ps/exchange/Set-ServerMonitor.md index c6a995976f..42b0c4a810 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Set-ServerMonitor.md +++ b/exchange/exchange-ps/exchange/Set-ServerMonitor.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/set-servermonitor +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ServerMonitor @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ServerMonitor cmdlet to edit or set a parameter on a single monitor on an Exchange server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Set-ServerMonitor [-Server] <ServerIdParameter> -Name <String> -Repairing <Boolean> [-Confirm] [-TargetResource <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,29 +42,32 @@ This example sets the maintenance monitor on the Exch01 server. ## PARAMETERS -### -Name -The Name parameter specifies the monitor identity. +### -Server +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN ```yaml -Type: String +Type: ServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -Repairing -The Repairing parameter specifies whether to set or clear the repairing property on a monitor. - -The default value is $true. +### -Name +The Name parameter specifies the monitor identity. ```yaml -Type: Boolean +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -72,39 +75,32 @@ Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Server -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 - -- FQDN - -- Distinguished name (DN) +### -Repairing +The Repairing parameter specifies whether to set or clear the repairing property on a monitor. -- Exchange Legacy DN +The default value is $true. ```yaml -Type: ServerIdParameter +Type: Boolean Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -157,12 +153,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-ServicePrincipal.md b/exchange/exchange-ps/exchange/Set-ServicePrincipal.md new file mode 100644 index 0000000000..78b5a30bc0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ServicePrincipal.md @@ -0,0 +1,129 @@ +--- +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 +ms.author: chrisda +ms.reviewer: bili1 +--- + +# Set-ServicePrincipal + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-ServicePrincipal cmdlet to change service principals in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ServicePrincipal [-Identity] <ServicePrincipalIdParameter> + [-Confirm] + [-DisplayName <String>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You can use this cmdlet to change the DisplayName only. If AppId/ObjectId is wrong, delete the service principal and create a new one. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ServicePrincipal -Identity dc873ad4-0397-4d74-b5c0-897cd3a94731 -DisplayName "Another App Name" +``` + +This example sets the service principal in Exchange Online with the specified display name. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- AppId +- ObjectId + +```yaml +Type: ServicePrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-SettingOverride.md b/exchange/exchange-ps/exchange/Set-SettingOverride.md similarity index 88% rename from exchange/exchange-ps/exchange/organization/Set-SettingOverride.md rename to exchange/exchange-ps/exchange/Set-SettingOverride.md index 1612fde6b5..f038384c37 100644 --- a/exchange/exchange-ps/exchange/organization/Set-SettingOverride.md +++ b/exchange/exchange-ps/exchange/Set-SettingOverride.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-settingoverride +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SettingOverride @@ -19,7 +18,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-SettingOverride cmdlet to modify setting overrides that store Exchange customizations in Active Directory instead of in text files on the server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,26 +26,26 @@ For information about the parameter sets in the Syntax section below, see [Excha Set-SettingOverride [-Identity] <SettingOverrideIdParameter> [-Confirm] [-DomainController <Fqdn>] + [-Force] [-MaxVersion <Version>] [-MinVersion <Version>] [-Parameters <MultiValuedProperty>] [-Reason <String>] [-Server <String[]>] [-WhatIf] - [-Force] [<CommonParameters>] ``` ## DESCRIPTION Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and they're lost when you install the next Exchange CU. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-SettingOverride -Identity "Change OAB Generation" -Server Mailbox01 -Component TimeBasedAssistants -Section OABGeneratorAssistant -Parameters @("WorkCycle=03:00:00") +Set-SettingOverride -Identity "Change OAB Generation" -Server Mailbox01 -Parameters @("WorkCycle=03:00:00") ``` This example modifies the setting override named Change OAB Generation on the server named Mailbox01 by changing the OAB generation interval to 3 hours. @@ -57,9 +56,7 @@ This example modifies the setting override named Change OAB Generation on the se 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 - - Distinguished name (DN) - - GUID ```yaml @@ -78,8 +75,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -112,7 +108,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -168,11 +166,10 @@ Accept wildcard characters: False ``` ### -Parameters -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") +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: -- @("IMServerName=\<SkypePoolFQDN\>","IMCertificateThumbprint=\<ThumbprintGUID\>") +- `@("Enabled=true")` +- `@("IMServerName=<SkypePoolFQDN>","IMCertificateThumbprint=<ThumbprintGUID>")` ```yaml Type: MultiValuedProperty @@ -242,12 +239,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SharingPolicy.md b/exchange/exchange-ps/exchange/Set-SharingPolicy.md similarity index 78% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SharingPolicy.md rename to exchange/exchange-ps/exchange/Set-SharingPolicy.md index daa6e5ea1f..5f5182f760 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SharingPolicy.md +++ b/exchange/exchange-ps/exchange/Set-SharingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-sharingpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-SharingPolicy @@ -17,19 +16,26 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-SharingPolicy cmdlet to modify existing sharing policies that control how users inside your organization can share free/busy and contact information with users outside your organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SharingPolicy [-Identity] <SharingPolicyIdParameter> [-Confirm] [-Default] [-DomainController <Fqdn>] - [-Domains <MultiValuedProperty>] [-Enabled <Boolean>] [-Name <String>] [-WhatIf] [<CommonParameters>] +Set-SharingPolicy [-Identity] <SharingPolicyIdParameter> + [-Confirm] + [-Default] + [-DomainController <Fqdn>] + [-Domains <MultiValuedProperty>] + [-Enabled <Boolean>] + [-Name <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION Users can only share free/busy and contact information after federation has been configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing options for the mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,18 +66,15 @@ This example disables the sharing policy SharingPolicy01. The Identity parameter specifies the identity of the sharing policy that you want to modify. You can use one of the following values: - ADObjectID - - Distinguished name (DN) - - Legacy DN - - GUID ```yaml Type: SharingPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -83,15 +86,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -137,23 +139,22 @@ Accept wildcard characters: False ``` ### -Domains -The Domains parameter specifies domains to which this policy applies and the sharing policy action. Values for this parameter use the format \<Domain\>: \<SharingPolicyAction\>. - -The following sharing policy action values can be used: - -- CalendarSharingFreeBusySimple: Share free/busy hours only. +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'`. -- CalendarSharingFreeBusyDetail: Share free/busy hours, subject, and location. +You can use the following values for `Domain`: -- CalendarSharingFreeBusyReviewer: Share free/busy hours, subject, location, and the body of the message or calendar item. +- A domain: For example, `mail.contoso.com`. A domain doesn't include subdomains. You must configure each subdomain separately. +- \*: Share with external federated organizations. For example, another Microsoft 365 organization or an on-premises Exchange organization. +- Anonymous: Share with external, non-federated organizations and individuals with internet access. -- ContactsSharing: Share contacts only. +You can use the following values for `SharingPolicyAction`: -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +- CalendarSharingFreeBusySimple: Share free/busy hours only +- CalendarSharingFreeBusyDetail: Share free/busy hours, subject and location +- CalendarSharingFreeBusyReviewer: Share free/busy hours, subject, location and the body of the message or calendar item +- ContactsSharing: Share contacts only -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -A domain doesn't include subdomains. You need to configure each subdomain separately. +You can specify multiple `'Domain: SharingPolicyAction'` values separated by commas, and you can specify multiple `SharingPolicyAction` values for the same domain separated by commas. For example, `'mail.contoso.com: CalendarSharingFreeBusySimple', 'mail.fabrikam.com: CalendarSharingFreeBusyDetail, ContactsSharing'`. ```yaml Type: MultiValuedProperty @@ -209,7 +210,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -223,12 +224,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SiteMailbox.md b/exchange/exchange-ps/exchange/Set-SiteMailbox.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SiteMailbox.md rename to exchange/exchange-ps/exchange/Set-SiteMailbox.md index ca4069c244..c9c67e224a 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SiteMailbox.md +++ b/exchange/exchange-ps/exchange/Set-SiteMailbox.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-sitemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SiteMailbox ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Set-SiteMailbox cmdlet to change a site mailbox's settings, such as the Microsoft SharePoint URL. This cmdlet is primarily used by the SharePoint and Microsoft Exchange user interfaces, such as the SharePoint URL. This cmdlet should only be used for diagnostic and troubleshooting purposes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,7 +40,7 @@ Set-SiteMailbox [-Identity] <RecipientIdParameter> ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,15 +64,10 @@ This example disables the duplication of email messages in the site mailbox SMO\ The Identity parameter specifies the identity of the site mailbox. You can use any value that uniquely identifies the site mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -106,8 +102,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -156,7 +151,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -179,18 +176,13 @@ The Members parameter specifies the members of the site mailbox. You can add or You can use any value that uniquely identifies the member. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -213,18 +205,13 @@ The Owners parameter specifies the owners of the site mailbox. You can add or re You can use any value that uniquely identifies the owner. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -293,7 +280,6 @@ Accept wildcard characters: False The SyncEnabled parameter specifies whether to enable or disable synchronization for the site mailbox. Valid values are: - $true: Synchronization is enabled. - - $true: Synchronization is disabled. ```yaml @@ -330,12 +316,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/exchange/Set-SiteMailboxProvisioningPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/exchange/Set-SiteMailboxProvisioningPolicy.md index 8e3bae5379..460a831c41 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/exchange/Set-SiteMailboxProvisioningPolicy.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-sitemailboxprovisioningpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SiteMailboxProvisioningPolicy ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Set-SiteMailboxProvisioningPolicy cmdlet to modify an existing site mailbox provisioning policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,13 +33,14 @@ Set-SiteMailboxProvisioningPolicy [-Identity] <MailboxPolicyIdParameter> [-MaxReceiveSize <ByteQuantifiedSize>] [-Name <String>] [-ProhibitSendReceiveQuota <ByteQuantifiedSize>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,7 +63,7 @@ This example changes the warning quota to 9.5 GB and the prohibit send and recei Set-SiteMailboxProvisioningPolicy -Identity SM_DefaultPolicy -AliasPrefix Project ``` -This example changes the default provisioning policy named SM\_DefaultPolicy and sets the AliasPrefix value to Project. When you create new site mailboxes, the prefix Project- is automatically added to the alias. +This example changes the default provisioning policy named SM\_DefaultPolicy and sets the AliasPrefix value to Project. When you create new site mailboxes, the prefix `Project-` is automatically added to the alias. ## PARAMETERS @@ -69,9 +71,7 @@ This example changes the default provisioning policy named SM\_DefaultPolicy and 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 - - Distinguished name (DN) - - GUID ```yaml @@ -91,7 +91,6 @@ Accept wildcard characters: False 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. - - The value $null. This is the default value. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text. ```yaml @@ -110,8 +109,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,8 +128,7 @@ Accept wildcard characters: False ### -DefaultAliasPrefixEnabled 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 Office 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). - +- $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`). - $false: Aliases don't get the default prefix text. The value of this parameter is related to the value of the AliasPrefix parameter. If you specify a text string for AliasPrefix, the DefaultAliasPrefixEnabled value is ignored. Specifying a text value for AliasPrefix automatically sets the value to $false, but even if you set it to $true, the default alias prefix text isn't used. @@ -189,13 +186,9 @@ The IssueWarningQuota parameter specifies the warning threshold for the size of 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -223,11 +216,8 @@ The MaxReceiveSize parameter specifies the maximum size of a message that can be When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -269,13 +259,9 @@ The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. I 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: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -318,12 +304,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-SmimeConfig.md b/exchange/exchange-ps/exchange/Set-SmimeConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Set-SmimeConfig.md rename to exchange/exchange-ps/exchange/Set-SmimeConfig.md index ad0fda3536..3b0f0fe2bb 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-SmimeConfig.md +++ b/exchange/exchange-ps/exchange/Set-SmimeConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/set-smimeconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-SmimeConfig @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-SmimeConfig cmdlet to modify the S/MIME configuration for Outlook on the web (formerly known as Outlook Web App). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -41,6 +40,7 @@ Set-SmimeConfig [[-Identity] <OrganizationIdParameter>] [-OWAIncludeCertificateChainAndRootCertificate <Boolean>] [-OWAIncludeCertificateChainWithoutRootCertificate <Boolean>] [-OWAIncludeSMIMECapabilitiesInMessage <Boolean>] + [-OWANoSignOnReply <Boolean>] [-OWAOnlyUseSmartCard <Boolean>] [-OWASenderCertificateAttributesToDisplay <String>] [-OWASignedEmailCertificateInclusion <Boolean>] @@ -49,13 +49,14 @@ Set-SmimeConfig [[-Identity] <OrganizationIdParameter>] [-OWAUseKeyIdentifier <Boolean>] [-OWAUseSecondaryProxiesWhenFindingCertificates <Boolean>] [-SMIMECertificateIssuingCA <Byte[]>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Set-SmimeConfig cmdlet can change several important parameters than can reduce the overall level of message security. Review your organization's security policy before you make any changes. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -158,9 +159,7 @@ Accept wildcard characters: False 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. - - 1: One single encrypted message for all Bcc recipients. - - 2: One encrypted message without Bcc forking. This setting affects the security and privacy of Outlook on the web. Consult your organization's security policy before you change this setting. @@ -182,7 +181,6 @@ Accept wildcard characters: False 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. - - $false: When the CRL distribution point is inaccessible, Outlook on the web allows signed or encrypted messages to be sent. This is the default value. ```yaml @@ -202,7 +200,6 @@ Accept wildcard characters: False 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. - - $false: digitally signed messages are opaque-signed. Clear-signed messages are larger than opaque-signed messages, but clear-signed messages can be read in most email clients, including clients that don't support S/MIME. @@ -280,7 +277,6 @@ Accept wildcard characters: False The OWADisableCRLCheck parameter enables or disables CRL checking in Outlook on the web. Valid values are: - $true: CRL checks are disabled when validating certificates. - - $false: CRL checks are enabled when validating certificates.This is the default value. Disabling CRL checking can decrease the time that's required to validate the signatures of signed email messages, but it also validates email messages that are signed with revoked certificates. @@ -321,23 +317,18 @@ Accept wildcard characters: False ``` ### -OWAEncryptionAlgorithms -The OWAEncryptionAlgorithms parameter specifies a list of symmetric encryption algorithms that are used by Outlook on the web to encrypt messages. Valid values are:: +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) - - 6602: RC2. Supported key lengths are 40, 56, 64, and 128. RC2 is the only supported algorithm that offers multiple key lengths. - - 6603: 3DES (168-bit) - - 660E: AES128 - - 660F: AES192 - - 6610: AES256 (This is the default value) -If you use a third-party cryptographic service provider (CSP), you need to specify the object identifier (OID) together with an algorithm ID (Outlook on the web needs an algorithm ID to infer how the algorithm should be used). For example, to provide a custom replacement for the 3DES algorithm, use the value 6603,\<CustomOID\>. +If you use a third-party cryptographic service provider (CSP), you need to specify the object identifier (OID) together with an algorithm ID (Outlook on the web needs an algorithm ID to infer how the algorithm should be used). For example, to provide a custom replacement for the 3DES algorithm, use the value `6603,<CustomOID>`. -This parameter uses the syntax \<AlgorithmID\> or RC2:\<KeyLength\> or \<AlgorithmID\>,\<CustomOID\>. You can specify multiple values separated by semicolons (;). For example, to set the encryption algorithms to 3DES, RC2-128, RC2-64, DES, and RC2-56, use the following value: 6603;6602:128;6602:64;6601;6602:56. +This parameter uses the syntax `<AlgorithmID>` or `RC2:<KeyLength>` or `<AlgorithmID>,<CustomOID>`. You can specify multiple values separated by semicolons (;). For example, to set the encryption algorithms to 3DES, RC2-128, RC2-64, DES, and RC2-56, use the following value: `6603;6602:128;6602:64;6601;6602:56`. If the parameter is not specified or is not formatted correctly, Outlook on the web uses 6610 (AES256). If the encryption algorithm or minimum key length is not available on a client, Outlook on the web does not allow encryption. @@ -358,7 +349,6 @@ Accept wildcard characters: False 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. - - $false: Temporary buffer encryption is disabled. Disabling encryption of the buffers can increase performance of the Outlook on the web client but also leaves information unencrypted in the client's buffer. Consult your organization's security policy before you disable this feature. @@ -380,7 +370,6 @@ Accept wildcard characters: False 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. - - $false: Users receive a warning if the S/MIME control on their computer is not current, but they can still use S/MIME without updating the control. ```yaml @@ -418,7 +407,6 @@ Accept wildcard characters: False 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. - - $false: Signed or encrypted messages include only the signing and encrypting certificates, not their corresponding certificate chains. This is the default value. ```yaml @@ -454,6 +442,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -OWANoSignOnReply +This parameter is available only in the cloud-based service. + +{{ Fill OWANoSignOnReply Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -OWAOnlyUseSmartCard The OWAOnlyUseSmartCard parameter specifies whether smartcard-based certificates are required for Outlook on the web message signing and decryption. Valid values are: @@ -496,7 +502,6 @@ Accept wildcard characters: False 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. - - $false: Outlook on the web and the S/MIME control do not include signing and encrypting certificates with signed email messages. When you don't include the certificates with signed email messages, the size of encrypted messages is reduced. However, recipients don't have access to the sender's encryption certificate in the message. Recipients need to retrieve the certificate from a directory, or from the sender. @@ -518,20 +523,16 @@ Accept wildcard characters: False 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 - - 800E: CALG\_SHA\_512 or 512-bit Secure Hash Algorithm (SHA) - - 800D: CALG\_SHA\_384 or 384-bit SHA - - 800C: CALG\_SHA\_256 or 256-bit SHA - - 8004: SHA1 or 160-bit SHA-1 (This is the default value) -If you use a third-party cryptographic service provider (CSP), you need to specify the object identifier (OID) together with an algorithm ID (Outlook on the web needs an algorithm ID to infer how the algorithm should be used). For example, to provide a custom replacement for the SHA1 algorithm, use the value 8804,\<CustomOID\>. +If you use a third-party cryptographic service provider (CSP), you need to specify the object identifier (OID) together with an algorithm ID (Outlook on the web needs an algorithm ID to infer how the algorithm should be used). For example, to provide a custom replacement for the SHA1 algorithm, use the value `8804,<CustomOID>`. -This parameter uses the syntax \<AlgorithmID\> or \<AlgorithmID\>:\<KeyLength\> or \<AlgorithmID\>,\<CustomOID\>. You can specify multiple values separated by semicolons (;). +This parameter uses the syntax `<AlgorithmID>` or `<AlgorithmID>:<KeyLength>` or `<AlgorithmID>,<CustomOID>`. You can specify multiple values separated by semicolons (;). -For example, to set the signing algorithms to CALG\_SHA\_512, SHA1, and CALG\_MD5, use the value 800E;8004;8003. +For example, to set the signing algorithms to CALG\_SHA\_512, SHA1, and CALG\_MD5, use the value `800E;8004;8003`. If this parameter is not specified or is not formatted correctly, Outlook on the web defaults to 8004 (SHA1). @@ -552,7 +553,6 @@ Accept wildcard characters: False 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). - - $false: A signed message is encrypted only (there is no additional signing of the encrypted message). This is the default value. Triple-wrapped messages offer the highest level of security for messages under the S/MIME standard, but are larger in size. @@ -575,7 +575,7 @@ The OWAUseKeyIdentifier parameter specifies whether a certificate's key identifi Valid input for this parameter is $true or $false. The default is $false. -By default, Outlook on the web encodes the asymmetrically encrypted token (sometimes called a lockbox) that's required to decrypt the rest of the message by indicating the issuer and serial number of each recipient's certificate. The issuer and serial number can then be used to locate the certificate and private key for decrypting the message. +By default, Outlook on the web encodes the asymmetrically encrypted token (sometimes called a Lockbox) that's required to decrypt the rest of the message by indicating the issuer and serial number of each recipient's certificate. The issuer and serial number can then be used to locate the certificate and private key for decrypting the message. This parameter causes the use of a certificate's key identifier when encoding the asymmetrically encrypted token. Because a key pair can be reused in new certificates, using the key identifier for encrypted email messages means that users need to keep only the most recent certificate and associated private key, rather than all old certificates. Because some email clients do not support finding certificates with a key identifier, Outlook on the web uses the issuer and serial number of each recipient's certificate by default. @@ -615,7 +615,7 @@ Accept wildcard characters: False ### -SMIMECertificateIssuingCA The SMIMECertificateIssuingCA parameter specifies the serialized certificate store (SST) that contains the Certificate Authority (CA) signing and intermediate certificate information. -You need to read the file to a byte-encoded object using the Get-Content cmdlet. For example: -SMIMECertificateIssuingCA $\(\[byte\[\]\]\(Get-Content -Encoding byte -Path "C:\\Temp\\CACertificateSerializedStore.sst" -ReadCount 0\) +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). Each certificate is checked, and if any certificates are expired, the operation will fail. @@ -653,12 +653,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/Set-SupervisoryReviewPolicyV2.md new file mode 100644 index 0000000000..ac5377657b --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-SupervisoryReviewPolicyV2.md @@ -0,0 +1,299 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-SupervisoryReviewPolicyV2 + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-SupervisoryReviewPolicyV2 cmdlet to modify supervisory review policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-SupervisoryReviewPolicyV2 [-Identity] <PolicyIdParameter> + [-AddReviewers <String[]>] + [-Comment <String>] + [-Confirm] + [-Enabled <Boolean>] + [-Force] + [-PolicyRBACScopes <MultiValuedProperty>] + [-PolicyTemplate <String>] + [-PreservationPeriodInDays <Int32>] + [-RemoveReviewers <String[]>] + [-RetentionPeriodInDays <Int32>] + [-Reviewers <String[]>] + [-UserReportingWorkloads <String[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-SupervisoryReviewPolicyV2 -Identity "EU Brokers" -AddReviewers chris@contoso.com,michelle@contoso.com -Comment "Updated for new EU regulations" +``` + +This example adds reviewers and updates the comment for the supervisory review policy named EU Brokers. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AddReviewers +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Comment +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +{{ Fill Enabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +{{ Fill PolicyRBACScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All)) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyTemplate +{{ Fill PolicyTemplate Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreservationPeriodInDays +{{ Fill PreservationPeriodInDays Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveReviewers +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionPeriodInDays +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Reviewers +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. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserReportingWorkloads +{{ Fill UserReportingWorkloads Description }} + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-SupervisoryReviewRule.md b/exchange/exchange-ps/exchange/Set-SupervisoryReviewRule.md new file mode 100644 index 0000000000..3b3c0210d9 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-SupervisoryReviewRule.md @@ -0,0 +1,461 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-SupervisoryReviewRule + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-SupervisoryReviewRule cmdlet to modify supervisory review rules in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-SupervisoryReviewRule [-Identity] <ComplianceRuleIdParameter> + [-AdvancedRule <String>] + [-CcsiDataModelOperator <String>] + [-Condition <String>] + [-Confirm] + [-ContentContainsSensitiveInformation <PswsHashtable[]>] + [-ContentMatchesDataModel <String>] + [-ContentSources <String[]>] + [-DayXInsights <Boolean>] + [-ExceptIfFrom <MultiValuedProperty>] + [-ExceptIfRecipientDomainIs <MultiValuedProperty>] + [-ExceptIfRevieweeIs <MultiValuedProperty>] + [-ExceptIfSenderDomainIs <MultiValuedProperty>] + [-ExceptIfSentTo <MultiValuedProperty>] + [-ExceptIfSubjectOrBodyContainsWords <MultiValuedProperty>] + [-From <MultiValuedProperty>] + [-IncludeAdaptiveScopes <String[]>] + [-InPurviewFilter <String>] + [-Ocr <Boolean>] + [-PolicyRBACScopes <MultiValuedProperty>] + [-SamplingRate <Int32>] + [-SentTo <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-SupervisoryReviewRule -Identity "EU Brokers Rule" -Conditions "((NOT(Reviewee:US Compliance)) -AND (Reviewee:EU Brokers) -AND ((trade) -OR (insider trading)) -AND (NOT(approved by the Contoso financial team)))" +``` + +This example modifies the existing rule named EU Brokers Rule with the following settings: + +- Conditions: Supervise inbound and outbound communications for members of the EU Brokers group that contain the words trade or insider trading. +- Exceptions: Exclude supervision for members of the EU Compliance group, or messages that contain the phrase "approved by the Contoso financial team". + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: ComplianceRuleIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AdvancedRule +{{ Fill AdvancedRule Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CcsiDataModelOperator +{{ Fill CcsiDataModelOperator Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Condition +The Condition parameter specifies the conditions and exceptions for the rule. This parameter uses the following syntax: + +- User or group communications to supervise: `"((Reviewee:<emailaddress1>) -OR (Reviewee:<emailaddress2>)...)"`. Exceptions use the syntax `"(NOT((Reviewee:<emailaddress1>) -OR (Reviewee:<emailaddress2>)...))"`. +- Direction: `"((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal))"`. +- Message contains words: `"((<Word1orPhrase1>) -OR (<Word2orPhrase2>)...)"`. Exceptions use the syntax `"(NOT((<Word1orPhrase1>) -OR (<Word2orPhrase2>)...))"`. +- Any attachment contains words: `"((Attachment:<word1>) -OR (Attachment:<word2>)...)"`. Exceptions use the syntax `"(NOT((Attachment:<word1>) -OR (Attachment:<word2>)...))"`. +- Any attachment has the extension: `"((AttachmentName:.<extension1>) -OR (AttachmentName:.<extension2>)...)"`. Exceptions use the syntax `"(NOT((AttachmentName:.<extension1>) -OR (AttachmentName:.<extension2>)...))"`. +- Message size is larger than: `"(MessageSize:<size in B, KB, MB or GB>)"`. For example `"(MessageSize:300KB)"`. Exceptions use the syntax `"(NOT(MessageSize:<size in B, KB, MB or GB>))"`. +- Any attachment is larger than: `"(AttachmentSize:<size in B, KB, MB or GB>)"`. For example `"(AttachmentSize:3MB)"`. Exceptions use the syntax `"(NOT(AttachmentSize:<size in B, KB, MB or GB>))"`. +- Parentheses ( ) are required around the whole filter. +- Separate multiple conditions or exception types with the AND operator. For example, `"((Reviewee:chris@contoso.com) -AND (AttachmentSize:3MB))"`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentContainsSensitiveInformation +{{ Fill ContentContainsSensitiveInformation Description }} + +```yaml +Type: PswsHashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentMatchesDataModel +{{ Fill ContentMatchesDataModel Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentSources +{{ Fill ContentSources Description }} + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DayXInsights +{{ Fill DayXInsights Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfFrom +{{ Fill ExceptIfFrom Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +{{ Fill ExceptIfRecipientDomainIs Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRevieweeIs +{{ Fill ExceptIfRevieweeIs Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSenderDomainIs +{{ Fill ExceptIfSenderDomainIs Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +{{ Fill ExceptIfSentTo Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSubjectOrBodyContainsWords +{{ Fill ExceptIfSubjectOrBodyContainsWords Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -From +{{ Fill From Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeAdaptiveScopes +{{ Fill IncludeAdaptiveScopes Description }} + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InPurviewFilter +{{ Fill InPurviewFilter Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Ocr +{{ Fill Ocr Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRBACScopes +{{ Fill PolicyRBACScopes Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SamplingRate +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SentTo +{{ Fill SentTo Description }} + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-SweepRule.md b/exchange/exchange-ps/exchange/Set-SweepRule.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Set-SweepRule.md rename to exchange/exchange-ps/exchange/Set-SweepRule.md index d5eb05b375..184a02c1af 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Set-SweepRule.md +++ b/exchange/exchange-ps/exchange/Set-SweepRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-sweeprule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-SweepRule @@ -17,22 +16,32 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-SweepRule cmdlet to modify Sweep rules in mailboxes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SweepRule [-Identity] <SweepRuleIdParameter> [-Confirm] [-DestinationFolder <MailboxFolderIdParameter>] - [-DomainController <Fqdn>] [-Enabled <Boolean>] [-ExceptIfFlagged <Boolean>] - [-ExceptIfPinned <Boolean>] [-KeepForDays <Int32>] [-KeepLatest <Int32>] - [-Mailbox <MailboxIdParameter>] [-Name <String>] [-Provider <String>] [-Sender <RecipientIdParameter>] +Set-SweepRule [-Identity] <SweepRuleIdParameter> + [-Confirm] + [-DestinationFolder <MailboxFolderIdParameter>] + [-DomainController <Fqdn>] + [-Enabled <Boolean>] + [-ExceptIfFlagged <Boolean>] + [-ExceptIfPinned <Boolean>] + [-KeepForDays <Int32>] + [-KeepLatest <Int32>] + [-Mailbox <MailboxIdParameter>] + [-Name <String>] + [-Provider <String>] + [-Sender <RecipientIdParameter>] [-SourceFolder <MailboxFolderIdParameter>] [-SystemCategory <SystemCategoryType>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,10 +58,8 @@ This example modifies the existing rule that has the rule ID value x2hlsdpGmUifj 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==). - -- Exchange Online: \<mailbox alias\>\\\<RuleId\> (for example, rzaher\\x2hlsdpGmUifjFgxxGIOJw==. - -- On-premises Exchange: \<mailbox canonical name\>\\\<RuleId\> (for example, contoso.com/Users/Rick Zaher\\x2hlsdpGmUifjFgxxGIOJw==. +- Exchange Online: `MailboxAlias\RuleID` (for example, `rzaher\2hlsdpGmUifjFgxxGIOJw==`). +- On-premises Exchange: `MailboxCanonicalName\RuleID` (for example, `contoso.com/Users/Rick Zaher\x2hlsdpGmUifjFgxxGIOJw==`). You can get these identity values by using the Get-SweepRule cmdlet. @@ -72,8 +79,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -95,23 +101,14 @@ The DestinationFolder parameter specifies an action for the Sweep rule that move For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Unimportant` or `John:\Inbox\Misc`. The default value is `MailboxID:\Deleted Items`. @@ -164,41 +161,32 @@ Accept wildcard characters: False ``` ### -ExceptIfFlagged +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: - $true: The rule action isn't applied to messages that have a message flag applied. - - $false: The exception isn't used. The typical message flag values are: - Any - - Call - - DoNotForward - - FollowUp - - ForYourInformation - - Forward - - NoResponseNecessary - - Read - - Reply - - ReplyToAll - - Review ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -208,17 +196,18 @@ Accept wildcard characters: False ``` ### -ExceptIfPinned +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: - $true: The rule action isn't applied to messages that are pinned to the top of the Inbox. - - $false: The exception isn't used. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -267,23 +256,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -337,15 +317,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID For external senders, use their email address. @@ -369,23 +344,14 @@ The SourceFolder parameter specifies a condition for the Sweep rule that looks f For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) Example values for this parameter are `john@contoso.com:\Marketing` or `John:\Inbox\Reports`. The default value is `MailboxID:\Inbox`. @@ -407,51 +373,28 @@ Accept wildcard characters: False 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 - - Bills - - Document - - DocumentPlus - - Event - - Family - - File - - Flight - - FromContact - - Important - - LiveView - - Lodging - - MailingList - - Newsletter - - Photo - - Purchase - - RentalCar - - RestaurantReservation - - RetiredPromotion - - ShippingNotification - - Shopping - - SocialUpdate - - Travel - - Video ```yaml @@ -488,12 +431,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-SystemMessage.md b/exchange/exchange-ps/exchange/Set-SystemMessage.md similarity index 82% rename from exchange/exchange-ps/exchange/mail-flow/Set-SystemMessage.md rename to exchange/exchange-ps/exchange/Set-SystemMessage.md index 74d59fd907..0cb1bfebec 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-SystemMessage.md +++ b/exchange/exchange-ps/exchange/Set-SystemMessage.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-systemmessage +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-SystemMessage @@ -17,17 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Set-SystemMessage cmdlet to modify custom system messages. System messages are delivery status notifications (also known as DSNs, non-delivery reports, NDRs or bounce messages) and quota messages. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-SystemMessage [-Identity] <SystemMessageIdParameter> [-Confirm] [-DomainController <Fqdn>] [-Name <String>] - [-Original] [-Text <String>] [-WhatIf] [<CommonParameters>] +Set-SystemMessage [-Identity] <SystemMessageIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-Name <String>] + [-Original] + [-Text <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,69 +56,52 @@ This example modifies the text of the custom English WarningMailbox quota messag 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 - - Distinguished name (DN) - - GUID The identity value of a system message uses one of these formats: -- System messages for enhanced status codes: \<Language\>\\\<Internal \| External\>\\\<DSNcode\>. For example, En\\Internal\\5.1.2 or Ja\\External\\5.1.2. +- System messages for enhanced status codes: `Language\<Internal | External>\DSNCode`. For example, `En\Internal\5.1.2` or `Ja\External\5.1.2`. +- System messages for quotas: `Language\QuotaMessageType`. For example, `En\ProhibitSendReceiveMailbox`. -- System messages for quotas: \<Language\>\\\<QuotaMessageType\>. For example, En\\ProhibitSendReceiveMailBox. +\<Language\>: 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). -\<Language\>: For the list of supported language codes, see [Supported languages for NDRs](https://docs.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs). - -\<DSNcode\>: Valid values are 4.x.y or 5.x.y where x and y are one to three digit numbers. To see the enhanced system codes that are currently used by custom system messages, run the command Get-SystemMessage. To generate a list of default enhanced status codes that are used by Exchange, run this command: Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language,Text | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\Default DSNs.html". +\<DSNCode\>: Valid values are 4.x.y or 5.x.y where x and y are one to three digit numbers. To see the enhanced system codes that are currently used by custom system messages, run the command `Get-SystemMessage`. To generate a list of default enhanced status codes that are used by Exchange, run this command: `Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language,Text | ConvertTo-Html | Set-Content -Path "C:\My Documents\Default DSNs.html"`. \<QuotaMessageType\>: Valid value are: Mailbox size quotas: -- ProhibitSendReceiveMailBox: A mailbox exceeds its ProhibitSendReceiveQuota limit. - +- ProhibitSendReceiveMailbox: A mailbox exceeds its ProhibitSendReceiveQuota limit. - ProhibitSendMailbox: A mailbox exceeds its ProhibitSendQuota limit. - - WarningMailbox: A mailbox exceeds its IssueWarningQuota limit when it has a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. - - WarningMailboxUnlimitedSize: A mailbox exceeds its IssueWarningQuota limit when it doesn't have a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. Public folder size quotas: - ProhibitPostPublicFolder: A public folder exceeds its ProhibitPostQuota limit. - - WarningPublicFolder: A public folder exceeds its IssueWarningQuota limit when it has a ProhibitPostQuota limit configured. - - WarningPublicFolderUnlimitedSize: A public folder exceeds its IssueWarningQuota limit when it doesn't have a ProhibitPostQuota limit configured. Maximum number of messages in a mailbox folder: - ProhibitReceiveMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountReceiveQuota limit. - - WarningMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it has a MailboxMessagesPerFolderCountReceiveQuota limit configured. - - WarningMailboxMessagesPerFolderUnlimitedCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it doesn't have a MailboxMessagesPerFolderCountReceiveQuota limit configured. Maximum number of subfolders in a mailbox folder: - ProhibitReceiveFolderHierarchyChildrenCountCount: A mailbox exceeds its FolderHierarchyChildrenCountReceiveQuota limit. - - WarningFolderHierarchyChildrenCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it has a FolderHierarchyChildrenCountReceiveQuota limit configured. - - WarningFolderHierarchyChildrenUnlimitedCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it doesn't have a FolderHierarchyChildrenCountReceiveQuota limit configured. - - ProhibitReceiveFoldersCount: A mailbox exceeds its FoldersCountReceiveQuota limit. - - WarningFoldersCount: A mailbox exceeds its FoldersCountWarningQuota limit when it has a FoldersCountReceiveQuota limit configured. - - WarningFoldersCountUnlimited A mailbox exceeds its FoldersCountWarningQuota limit when it doesn't have a FoldersCountReceiveQuota limit configured. Maximum number of levels (depth) in a mailbox folder: - ProhibitReceiveFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit. - - WarningFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it has a FolderHierarchyDepthReceiveQuota limit configured. - - WarningFolderHierarchyDepthUnlimited: : A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it doesn't have a FolderHierarchyDepthReceiveQuota limit configured. ```yaml @@ -132,8 +120,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -210,31 +197,22 @@ This parameter can contain text and HTML tags. The maximum length is 512 charact The following HTML tags are available: -- \<B\> and \</B\> (bold) - -- \<EM\> and \</EM\> (italic) - -- \<BR\> (line break) - -- \<P\> and \</P\> (paragraph) - -- \<A HREF="url"\> and \</A\> (hyperlink) - -You need to use single quotation marks (not double quotation marks) around the complete text string if you use the hyperlink tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag). +- `<B>` and `</B>` (bold) +- `<EM>` and `</EM>` (italic) +- `<BR>` (line break) +- `<P>` and `</P>` (paragraph) +- `<A HREF="url">` and `</A>` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag). Use the following escape codes for these special characters: -- < for \<. - -- > for \>. - -- " for ". - -- & for &. +- `<` for \< +- `>` for \> +- `"` for " +- `&` for & Here's an example value for this parameter that uses HTML tags and special characters: -'You tried to send a message to a \<B\>disabled\</B\> mailbox. Please visit \<A HREF="https://it.contoso.com/"\>Internal Support\</A\> or contact "InfoSec" for more information.' +`'You tried to send a message to a <B>disabled</B> mailbox. Please visit <A HREF="https://it.contoso.com/">Internal Support</A> or contact "InfoSec" for more information.'` ```yaml Type: String @@ -270,12 +248,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicy.md b/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicy.md new file mode 100644 index 0000000000..65370a81b9 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicy.md @@ -0,0 +1,192 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-TeamsProtectionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-TeamsProtectionPolicy cmdlet to modify Microsoft Teams protection policies. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-TeamsProtectionPolicy [-Identity] <TeamsProtectionPolicyIdParameter> + [-AdminDisplayName <String>] + [-Confirm] + [-HighConfidencePhishQuarantineTag <String>] + [-MalwareQuarantineTag <String>] + [-WhatIf] + [-ZapEnabled <Boolean>] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-TeamsProtectionPolicy -Identity "Teams Protection Policy" -HighConfidencePhishQuarantineTag AdminOnlyWithNotifications +``` + +This example changes the quarantine policy that's used for high confidence phishing detections. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AdminDisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HighConfidencePhishQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages, and whether users receive quarantine notifications. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the default quarantine policy that's used is named AdminOnlyAccessPolicy. For more information about this quarantine policy, see [Anatomy of a quarantine policy](https://learn.microsoft.com/defender-office-365/quarantine-policies#anatomy-of-a-quarantine-policy). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MalwareQuarantineTag +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 +- Distinguished name (DN) +- GUID + +Quarantine policies define what users are able to do to quarantined messages, and whether users receive quarantine notifications. For more information about quarantine policies, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). + +If you don't use this parameter, the default quarantine policy that's used is named AdminOnlyAccessPolicy. For more information about this quarantine policy, see [Anatomy of a quarantine policy](https://learn.microsoft.com/defender-office-365/quarantine-policies#anatomy-of-a-quarantine-policy). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ZapEnabled +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. +- $false: ZAP for malware and high confidence phishing messages in Teams is disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicyRule.md new file mode 100644 index 0000000000..859d7e7ee7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicyRule.md @@ -0,0 +1,279 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-TeamsProtectionPolicyRule + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-TeamsProtectionPolicyRule cmdlet to modify Microsoft Teams protection policy rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-TeamsProtectionPolicyRule [-Identity] <RuleIdParameter> + [-Comments <String>] + [-Confirm] + [-ExceptIfRecipientDomainIs <Word[]>] + [-ExceptIfSentTo <RecipientIdParameter[]>] + [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +> [!IMPORTANT] +> Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Configure ZAP for Teams protection in Defender for Office 365 Plan 2](https://learn.microsoft.com/defender-office-365/mdo-support-teams-about#configure-zap-for-teams-protection-in-defender-for-office-365-plan-2). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" -ExceptIfRecipientDomainIs research.contoso.com +``` + +This example modifies the existing Teams protection policy rule by excluding recipients in the domain research.contoso.com from ZAP for Teams protection. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Comments +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfRecipientDomainIs +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`. + +To add domains without affecting other existing values, use the following syntax: + +`$DomainsAdd = Get-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" | select -Expand ExceptIfRecipientDomainIs` + +`$DomainsAdd += "Domain1","Domain2",..."DomainN"` + +`Set-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" -ExceptIfRecipientDomainIs $DomainsAdd` + +To remove domains without affecting other existing values, use the following syntax: + +- Run the following commands to see the existing list of values in order: + + `$x = Get-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule"` + + `$d = [System.Collections.ArrayList]($x.ExceptIfRecipientDomainIs)` + + `$d` + + The first value in the list has the index number 0, the second has the index number 1, and so on. + +- Use the index number to specify the value to remove. For example, to remove the seventh value in the list, run the following commands: + + `$d.RemoveAt(6)` + + `Set-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" -ExceptIfRecipientDomainIs $d` + +To empty the list, use the value $null for this parameter. + +```yaml +Type: Word[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentTo +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +To replace all existing recipients with the values you specify, use the following syntax: `"User1","User2",..."UserN"`. + +To add recipients without affecting other existing values, use the following syntax: + +`$UsersAdd = Get-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" | select -Expand ExceptIfSentTo` + +`$UsersAdd += "User1","User2",..."UserN"` + +`Set-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" -ExceptIfSentTo $UsersAdd` + +To remove recipients without affecting other existing values, use the following syntax: + +- Run the following commands to see the existing list of values in order: + + `$x = Get-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule"` + + `$u = [System.Collections.ArrayList]($x.ExceptIfSentTo)` + + `$u` + + The first value in the list has the index number 0, the second has the index number 1, and so on. + +- Use the index number to specify the value to remove. For example, to remove the seventh value in the list, run the following commands: + + `$u.RemoveAt(6)` + + `Set-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" -ExceptIfSentTo $u` + +To empty the list, use the value $null for this parameter. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptIfSentToMemberOf +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +To add groups without affecting other existing values, use the following syntax: + +`$GroupsAdd = Get-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" | select -Expand ExceptIfSentToMemberOf` + +`$GroupsAdd += "Group1","Group2",..."GroupN"` + +`Set-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" -ExceptIfSentToMemberOf $GroupsAdd` + +To remove groups without affecting other existing values, use the following syntax: + +- Run the following commands to see the existing list of values in order: + + `$x = Get-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule"` + + `$g = [System.Collections.ArrayList]($x.ExceptIfSentToMemberOf)` + + `$g` + + The first value in the list has the index number 0, the second has the index number 1, and so on. + +- Use the index number to specify the value to remove. For example, to remove the seventh value in the list, run the following commands: + + `$g.RemoveAt(6)` + + `Set-TeamsProtectionPolicyRule -Identity "Teams Protection Policy Rule" -ExceptIfSentTo $g` + +If you remove the group after you create the rule, no exception is made for ZAP for Teams for messages that are sent to members of the group. + +To empty the list, use the value $null for this parameter. + +```yaml +Type: RecipientIdParameter[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-TenantAllowBlockListItems.md b/exchange/exchange-ps/exchange/Set-TenantAllowBlockListItems.md new file mode 100644 index 0000000000..843a7d4d31 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-TenantAllowBlockListItems.md @@ -0,0 +1,306 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-TenantAllowBlockListItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-TenantAllowBlockListItems cmdlet to modify entries in the Tenant Allow/Block List in the Microsoft Defender portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Ids (Default) +``` +Set-TenantAllowBlockListItems -Ids <String[]> -ListType <ListType> + [-Allow] + [-Block] + [-ExpirationDate <DateTime>] + [-ListSubType <ListSubType>] + [-NoExpiration] + [-Notes <String>] + [-OutputJson] + [-RemoveAfter <Int32>] + [<CommonParameters>] +``` + +### Entries +``` +Set-TenantAllowBlockListItems -Entries <String[]> -ListType <ListType> + [-Allow] + [-Block] + [-ExpirationDate <DateTime>] + [-ListSubType <ListSubType>] + [-NoExpiration] + [-Notes <String>] + [-OutputJson] + [-RemoveAfter <Int32>] + [<CommonParameters>] +``` + +## DESCRIPTION +In most cases, you can't modify the sender, URL, file, or IP address values after you create the entry. The only exception is URL allow entries for phishing simulations (ListType = URL, ListSubType = AdvancedDelivery). For more information about allowing URLs for phishing simulations, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-TenantAllowBlockListItems -ListType Url -Ids "RgAAAAAI8gSyI_NmQqzeh-HXJBywBwCqfQNJY8hBTbdlKFkv6BcUAAAl_QCZAACqfQNJY8hBTbdlKFkv6BcUAAAl_oSRAAAA" -ExpirationDate (Get-Date "5/30/2021 9:30 AM").ToUniversalTime() +``` + +This example changes the expiration date of the specified entry. + +### Example 2 +```powershell +Set-TenantAllowBlockListItems -ListType Url -ListSubType AdvancedDelivery -Entries *.fabrikam.com -ExpirationDate 9/11/2021 +``` + +This example changes the expiration date of the URL allow entry for the specified third-party phishing simulation URL. + +## PARAMETERS + +### -Entries +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. +- Sender domains and email addresses: The exact domain or email address value. +- Url: The exact URL value. +- IP: IPv6 addresses only. Single IPv6 addresses in colon-hexadecimal or zero-compression format or CIDR IPv6 ranges from 1 to 128. + +This value is shown in the Value property of the entry in the output of the Get-TenantAllowBlockListItems cmdlet. + +You can't mix value types (sender, URL, file, or IP address) or allow and block actions in the same command. + +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Ids +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`. + +You can't use this parameter with the Entries parameter. + +```yaml +Type: String[] +Parameter Sets: Ids +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ListType +The ListType parameter specifies the type of entry that you want to modify. Valid values are: + +- FileHash +- Sender +- Url +- IP + +Use the Entries or Ids parameter with this parameter to identify the entry itself. + +```yaml +Type: ListType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoExpiration +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: + +- Block entries. +- URL allow entries where the ListSubType parameter value is AdvancedDelivery. +- IP address allow entries. + +You can't use this switch with the ExpirationDate parameter. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Allow +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Block +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpirationDate +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: + +- Specify the date/time value in UTC: For example, `"2021-05-06 14:30:00z"`. +- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2020 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date). + +You can't use this parameter with the NoExpiration or RemoveAfter parameters. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ListSubType +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 third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). +- Tenant: This is the default value. + +```yaml +Type: ListSubType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Notes +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutputJson +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveAfter +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. + +You can't use this parameter with the ExpirationDate or NoExpirationDate parameters. + +To change the allow entry to a static expiration date/time value that doesn't depend on the LastUsedDate property, run a Set-TenantAllowBlockListItems command with the ExpirationDate parameter. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/exchange/Set-TenantAllowBlockListSpoofItems.md new file mode 100644 index 0000000000..e410aa39ca --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-TenantAllowBlockListSpoofItems.md @@ -0,0 +1,150 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-TenantAllowBlockListSpoofItems + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-TenantAllowBlockListSpoofItems cmdlet to modify spoofed sender entries in the Tenant Allow/Block List. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-TenantAllowBlockListSpoofItems [-Identity] <HostedConnectionFilterPolicyIdParameter> -Action <String> -Ids <String[]> + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet allows or blocks spoof pairs (the combination of the spoofed user and the sending infrastructure) in the Tenant Allow/Block List. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Get-TenantAllowBlockListSpoofItems | Format-Table SpoofedUser,SendingInfrastructure,SpoofType,Action,Identity + +Set-TenantAllowBlockListSpoofItems -Identity Default -Action Block -Ids 375e76f1-eefb-1626-c8bc-5efefd057488,f8cb0908-8533-1156-ce7b-9aebd685b0eb +``` + +This example bocks the specified spoof pairs. You get the Ids parameter values from the output of Get-TenantAllowBlockListSpoofItems command (the Identity property). + +### Example 2 +```powershell +(Get-TenantAllowBlockListSpoofItems -SpoofType External | Select-Object -Property Identity).Identity | Remove-TenantAllowBlockListSpoofItems -Identity Default +``` + +This example removes all external spoof pairs from the Tenant Allow/Block List. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Action +The Action parameter specifies whether this entry is an allow or block spoofed sender entry. Valid values are: + +- Allow +- Block + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Ids +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access/Set-TextMessagingAccount.md b/exchange/exchange-ps/exchange/Set-TextMessagingAccount.md similarity index 81% rename from exchange/exchange-ps/exchange/client-access/Set-TextMessagingAccount.md rename to exchange/exchange-ps/exchange/Set-TextMessagingAccount.md index 0757941400..57563a2af1 100644 --- a/exchange/exchange-ps/exchange/client-access/Set-TextMessagingAccount.md +++ b/exchange/exchange-ps/exchange/Set-TextMessagingAccount.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-textmessagingaccount +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-TextMessagingAccount @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. The Set-TextMessagingAccount cmdlet allows a user to configure the text messaging settings on their own mailbox. An administrator can't use this cmdlet to configure the text messaging settings on another user's mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,7 +28,8 @@ Set-TextMessagingAccount [-Identity] <MailboxIdParameter> [-IgnoreDefaultScope] [-MobileOperatorId <Int32>] [-NotificationPhoneNumber <E164Number>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -37,7 +37,7 @@ When text messaging notifications are enabled on a mailbox, you can configure ca To clear the text messaging settings from your own mailbox, use the Clear-TextMessagingAccount parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,23 +61,14 @@ This example sets the region, mobile operator and notification phone number for The Identity parameter specifies the target mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -96,8 +87,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -114,15 +104,13 @@ Accept wildcard characters: False ``` ### -CountryRegionId -The CountryRegionId parameter specifies the country that your mobile phone is registered in. Although this parameter accepts any valid ISO 3166-1 alpha-2 country code value, the following values correspond to the country selections that are available in the text messaging settings in Outlook on the web (formerly known as Outlook Web App): +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 - - CA - - RO -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://go.microsoft.com/fwlink/p/?linkId=184859). +A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). ```yaml Type: RegionInfo @@ -156,12 +144,11 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -178,22 +165,18 @@ Accept wildcard characters: False ``` ### -MobileOperatorId -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 and mobile operator selections that are available in the text messaging settings in Outlook on the web (formerly known as Outlook Web App): +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: - AT&T: 15001 - - Sprint PCS: 15004 - - T-Mobile: 15005 - - Verizon Wireless: 15006 Canada: - Bell: 17001 - - Telus Mobility: 17002 Romania: @@ -214,7 +197,7 @@ Accept wildcard characters: False ``` ### -NotificationPhoneNumber -The NotificationPhoneNumber parameter specifies the telephone number to use for your text messaging notifications. This parameter uses the E.164 format: +\<CountryCode\>\<CompleteTelephoneNumber\> (for example, +15551234567). +The NotificationPhoneNumber parameter specifies the telephone number to use for your text messaging notifications. This parameter uses the E.164 format: `+<CountryCode><CompleteTelephoneNumber>` (for example, `+15551234567`). ```yaml Type: E164Number @@ -250,12 +233,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Set-ThrottlingPolicy.md b/exchange/exchange-ps/exchange/Set-ThrottlingPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/server-health-and-performance/Set-ThrottlingPolicy.md rename to exchange/exchange-ps/exchange/Set-ThrottlingPolicy.md index 4393c23d36..aec6333325 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Set-ThrottlingPolicy.md +++ b/exchange/exchange-ps/exchange/Set-ThrottlingPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/set-throttlingpolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-ThrottlingPolicy @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-ThrottlingPolicy cmdlet to modify the settings for a user throttling policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -167,23 +166,26 @@ Set-ThrottlingPolicy [-Identity] <ThrottlingPolicyIdParameter> [-SchedulesMaxConcurrency <Unlimited>] [-SchedulesRechargeRate <Unlimited>] [-ThrottlingPolicyScope <ThrottlingPolicyScopeType>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION Throttling policy settings are stored in Active Directory. -By default, there is one default user throttling policy named GlobalThrottlingPolicy with a throttling scope of Global. Microsoft Setup creates this policy as part of the Client Access server role. You shouldn't replace, re-create, or remove the existing default throttling policy. However, you can edit any additional throttling policies with the scope of Organization or Regular if you want to change your user throttling settings. You can create polices with the scope of Organization or Regular using the New-ThrottlingPolicy cmdlet. +By default, there is one default user throttling policy named GlobalThrottlingPolicy with a throttling scope of Global. Exchange Setup creates this policy as part of the Client Access server role. You shouldn't replace, re-create, or remove the existing default throttling policy. However, you can edit any additional throttling policies with the scope of Organization or Regular if you want to change your user throttling settings. You can create policies with the scope of Organization or Regular using the New-ThrottlingPolicy cmdlet. -For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -$a = Get-ThrottlingPolicy RemoteSiteUserPolicy; $a | Set-ThrottlingPolicy -EwsMaxConcurrency 4 +$a = Get-ThrottlingPolicy RemoteSiteUserPolicy + +$a | Set-ThrottlingPolicy -EwsMaxConcurrency 4 ``` This example modifies a throttling policy so that users associated with this policy can have a maximum of four concurrent requests running in Exchange Web Services. @@ -269,7 +271,7 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInAD -This parameter is available or functional only in 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. @@ -287,7 +289,7 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInCAS -This parameter is available or functional only in 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. @@ -305,7 +307,7 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -437,8 +439,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -583,7 +584,7 @@ Accept wildcard characters: False ``` ### -CPAPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -617,7 +618,7 @@ Accept wildcard characters: False ``` ### -CPUStartPercent -This parameter is available or functional only in 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. @@ -635,7 +636,7 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxConcurrency -The DiscoveryMaxConcurrency parameter specifies the number of concurrent discovery search executions that a user can have at the same time. +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 @@ -651,7 +652,7 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxKeywords -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://docs.microsoft.com/powershell/module/exchange/mailboxes/search-mailbox). +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 @@ -747,7 +748,7 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxStatsSearchMailboxes -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://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). +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 @@ -909,7 +910,7 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInAD -This parameter is available or functional only in 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. @@ -927,7 +928,7 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInCAS -This parameter is available or functional only in 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. @@ -945,7 +946,7 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1155,7 +1156,7 @@ Accept wildcard characters: False ``` ### -EWSFastSearchTimeoutInSeconds -This parameter is available or functional only in 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. @@ -1173,7 +1174,7 @@ Accept wildcard characters: False ``` ### -EWSFindCountLimit -This parameter is available or functional only in 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. @@ -1223,7 +1224,7 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInAD -This parameter is available or functional only in 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. @@ -1241,7 +1242,7 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1259,7 +1260,7 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1311,7 +1312,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -1391,7 +1394,7 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInAD -This parameter is available or functional only in 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. @@ -1409,7 +1412,7 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1427,7 +1430,7 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1461,13 +1464,11 @@ Accept wildcard characters: False ``` ### -IsServiceAccount -The IsServiceAccount switch specifies whether you want the user accounts associated with this policy to be moderated by the per-user thresholds specified by this policy, and also by additional throttling based on the health of system resources, such as overall CPU usage. +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. -This value is set to $false by default. +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). -You may want to set this value to $true if you intend to associate this policy with user accounts that require higher throttling limits. An account that might require higher throttling limits is a service account that performs a lot of non-interactive work (for example, service accounts that perform IMAP mailbox migrations or nightly Windows PowerShell tasks). - -By setting the IsServiceAccount switch to $true, work done by these accounts is moderated by the higher user throttling settings that you configure using the user throttling policy, but is slowed if resources start getting unhealthy. +By using this switch, work done by these accounts is moderated by the higher user throttling settings that you configure using the user throttling policy, but is slowed if resources start getting unhealthy. ```yaml Type: SwitchParameter @@ -1499,7 +1500,7 @@ Accept wildcard characters: False ``` ### -Name -The Name parameter specifies the name of the object in Active Directory. The default policy is named DefaultThrottlingPolicy\<GUID\>. +The Name parameter specifies the name of the object in Active Directory. The default policy is named `DefaultThrottlingPolicy<GUID>`. ```yaml Type: String @@ -1659,7 +1660,11 @@ Accept wildcard characters: False ``` ### -OWAMaxConcurrency -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. The OwaMaxConcurrency 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. +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. + +**Note**: We don't recommend setting this parameter to a large number or the value $null, because server performance might be negatively affected. ```yaml Type: UInt32 @@ -1675,7 +1680,7 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInAD -This parameter is available or functional only in 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. @@ -1693,7 +1698,7 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1711,7 +1716,7 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -1857,7 +1862,7 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInAD -This parameter is available or functional only in 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. @@ -1875,7 +1880,7 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInCAS -This parameter is available or functional only in 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. @@ -1893,7 +1898,7 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -2010,7 +2015,6 @@ Accept wildcard characters: False 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. - - In the context of Exchange Web Services, the PowerShellMaxConcurrency parameter specifies the number of concurrent cmdlet executions that a user can have at the same time. This parameter value doesn't necessarily correlate to the number of browsers opened by the user. @@ -2032,21 +2036,13 @@ Accept wildcard characters: False 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 - - Move-ActiveMailboxDatabase - - Remove-AcceptedDomain - - Remove-Mailbox - - Remove-MailUser - - Remove-Organization - - Set-Mailbox - - Set-MailUser - - Update-MailboxDatabaseCopy The time period used for this limit is specified by the PowerShellMaxDestructiveCmdletsTimePeriod parameter. Both values should be set at the same time. This feature isn't on by default. For more information, see the "Examples" section. @@ -2393,7 +2389,7 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInAD -This parameter is available or functional only in 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. @@ -2411,7 +2407,7 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInCAS -This parameter is available or functional only in 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. @@ -2429,7 +2425,7 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInMailboxRPC -This parameter is available or functional only in 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. @@ -2612,12 +2608,10 @@ Accept wildcard characters: False 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. - - Organization: This scope specifies a custom policy that applies to all users in your organization. - - Global: This scope is reserved for the default throttling policy. -For more information about throttling policy scopes, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). +For more information about throttling policy scopes, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). ```yaml Type: ThrottlingPolicyScopeType @@ -2653,12 +2647,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/exchange/Set-ThrottlingPolicyAssociation.md new file mode 100644 index 0000000000..7179fe0d72 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-ThrottlingPolicyAssociation.md @@ -0,0 +1,163 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-ThrottlingPolicyAssociation + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Set-ThrottlingPolicyAssociation cmdlet to associate a throttling policy with a specific object. The object can be a user with a mailbox, a user without a mailbox, a contact, or a computer account. + +**Note**: Some parameters in the throttling policy (for example, MessageRateLimit) apply only to objects that have mailbox GUIDs (mailboxes or remote mailboxes) and don't apply to mail users. And, if you want to apply throttling policy to a remote mailbox, first populate the remote mailbox with an ExchangeGUID by using Set-RemoteMailbox -ExchangeGUID. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-ThrottlingPolicyAssociation [-Identity] <ThrottlingPolicyAssociationIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-ThrottlingPolicy <ThrottlingPolicyIdParameter>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The Set-ThrottlingPolicyAssociation cmdlet defines quota limits for specific objects. For example, if you notice that a user or other object is using excessive bandwidth, you can associate that object with a throttling policy that's more restrictive. + +In data center deployments, the object referred to by the Identity and ThrottlingPolicy parameters must be in the same tenant. + +For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). + +You need to be assigned permissions before you can run the Set-ThrottlingPolicyAssociation cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-ThrottlingPolicyAssociation -Identity tonysmith -ThrottlingPolicy ITStaffPolicy +``` + +This example associates a user with a username of tonysmith to the throttling policy ITStaffPolicy that has higher limits. + +### Example 2 +```powershell +$b = Get-ThrottlingPolicy ITStaffPolicy + +Set-Mailbox -Identity tonysmith -ThrottlingPolicy $b +``` + +You don't need to use the Set-ThrottlingPolicyAssociation cmdlet to associate a user with a policy. The following commands show another way to associate tonysmith with the throttling policy ITStaffPolicy. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThrottlingPolicy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/mail-flow/Set-TransportAgent.md b/exchange/exchange-ps/exchange/Set-TransportAgent.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Set-TransportAgent.md rename to exchange/exchange-ps/exchange/Set-TransportAgent.md index 6a7d6c4906..65fa73a458 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-TransportAgent.md +++ b/exchange/exchange-ps/exchange/Set-TransportAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-transportagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-TransportAgent @@ -17,24 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Set-TransportAgent cmdlet to modify existing transport agents. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-TransportAgent [-Identity] <TransportAgentObjectId> [-Confirm] [-DomainController <Fqdn>] - [-Priority <Int32>] [-WhatIf] - [-TransportService <TransportService>] [<CommonParameters>] +Set-TransportAgent [-Identity] <TransportAgentObjectId> + [-Confirm] + [-DomainController <Fqdn>] + [-Priority <Int32>] + [-TransportService <TransportService>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-TransportAgent "Test App" -Priority 3 -TransportService -FrontEnd +Set-TransportAgent "Test App" -Priority 3 -TransportService FrontEnd ``` This example modifies the priority of a fictitious agent named Test App in the Front End Transport service. @@ -60,8 +63,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -111,33 +113,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -TransportService 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. - - MailboxSubmission for the Mailbox Transport Submission service on Mailbox servers. - - MailboxDelivery for the Mailbox Transport Delivery service on Mailbox servers. - - FrontEnd for the Front End Transport service on Mailbox servers. - - Edge on Edge Transport servers. ```yaml @@ -153,17 +135,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-TransportConfig.md b/exchange/exchange-ps/exchange/Set-TransportConfig.md similarity index 83% rename from exchange/exchange-ps/exchange/mail-flow/Set-TransportConfig.md rename to exchange/exchange-ps/exchange/Set-TransportConfig.md index c0673ea2e2..57473281ff 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-TransportConfig.md +++ b/exchange/exchange-ps/exchange/Set-TransportConfig.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-transportconfig +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-TransportConfig @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-TransportConfig cmdlet to modify the transport configuration settings for the whole Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,6 +25,7 @@ Set-TransportConfig [[-Identity] <OrganizationIdParameter>] [-AddressBookPolicyRoutingEnabled <Boolean>] [-AgentGeneratedMessageLoopDetectionInSmtpEnabled <Boolean>] [-AgentGeneratedMessageLoopDetectionInSubmissionEnabled <Boolean>] + [-AllowLegacyTLSClients <System.Boolean>] [-ClearCategories <Boolean>] [-Confirm] [-ConvertDisclaimerWrapperToEml <Boolean>] @@ -49,6 +49,7 @@ Set-TransportConfig [[-Identity] <OrganizationIdParameter>] [-InternalDsnReportingAuthority <SmtpDomain>] [-InternalDsnSendHtml <Boolean>] [-InternalSMTPServers <MultiValuedProperty>] + [-JournalMessageExpirationDays <Int32>] [-JournalingReportNdrTo <SmtpAddress>] [-LegacyJournalingMigrationEnabled <Boolean>] [-MaxAllowedAgentGeneratedMessageDepth <UInt32>] @@ -60,9 +61,14 @@ Set-TransportConfig [[-Identity] <OrganizationIdParameter>] [-MaxRetriesForLocalSiteShadow <Int32>] [-MaxRetriesForRemoteSiteShadow <Int32>] [-MaxSendSize <Unlimited>] - [-OrganizationFederatedMailbox <SmtpAddress>] + [-MessageExpiration <EnhancedTimeSpan>] + [-PreventDuplicateJournalingEnabled <Boolean>] [-QueueDiagnosticsAggregationInterval <EnhancedTimeSpan>] [-RejectMessageOnShadowFailure <Boolean>] + [-ReplyAllStormBlockDurationHours <Int32>] + [-ReplyAllStormDetectionMinimumRecipients <Int32>] + [-ReplyAllStormDetectionMinimumReplies <Int32>] + [-ReplyAllStormProtectionEnabled <Boolean>] [-Rfc2231EncodingEnabled <Boolean>] [-SafetyNetHoldTime <EnhancedTimeSpan>] [-ShadowHeartbeatFrequency <EnhancedTimeSpan>] @@ -85,7 +91,7 @@ Set-TransportConfig [[-Identity] <OrganizationIdParameter>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -103,18 +109,20 @@ Set-TransportConfig -JournalingReportNdrTo journalingndr@contoso.com This example configures the Exchange organization to redirect all journaling reports that can't be delivered to the journaling mailbox to the email account journalingndr@contoso.com. -To avoid journaling issues, we recommend that you set JournalingReportNdrTo to a dedicated mailbox without any transport rule or mailbox rule. Or, set JournalingReportNdrTo to an external address. In Exchange Online, you can configure this setting by using the Office 365 portal or Exchange Online PowerShell. In on-premises Exchange Server, you can configure this setting by using the Exchange Management Shell. For more information, see [KB2829319](https://go.microsoft.com/fwlink/p/?linkid=787472). +To avoid journaling issues, we recommend that you set JournalingReportNdrTo to an external address. Like the journaling mailbox, the alternate journaling mailbox can't be an Exchange Online mailbox. In Exchange Online, you can configure this setting by using the Microsoft 365 admin center or Exchange Online PowerShell. In on-premises Exchange Server, you can configure this setting by using the Exchange Management Shell. For more information, see [KB2829319](https://support.microsoft.com/help/2829319). ## PARAMETERS ### -Identity +This parameter is available only in on-premises Exchange. + 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, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -126,7 +134,7 @@ Accept wildcard characters: False ### -AddressBookPolicyRoutingEnabled 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://docs.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies). +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). ```yaml Type: Boolean @@ -185,6 +193,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AllowLegacyTLSClients +This parameter is available only in the cloud-based service. + +{{ Fill AllowLegacyTLSClients Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ClearCategories 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. @@ -204,8 +230,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -225,9 +250,7 @@ Accept wildcard characters: False 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. - - The sender has signed the message. - - The message is processed by a Transport rule that adds a disclaimer. When a Transport rule that adds disclaimers to outbound messages encounters a message signed by the sender, the Transport rule can't add the disclaimer directly to the message. As a result, the disclaimer is sent to the intended recipient with the original message as an attachment. @@ -286,14 +309,14 @@ Accept wildcard characters: False ``` ### -DSNConversionMode -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 messaging systems. Valid values are: +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. - -- PreserveDSNBody: DSNs are converted to the Exchange 2010 or later format, and the text in the body of the DSN message is retained. This is the default value. - +- PreserveDSNBody: DSNs are converted to the Exchange 2010 or later format, and the text in the body of the DSN message is retained. - UseExchangeDSNs: DSNs are converted to the Exchange 2010 or later format. However, any customized text or attachments that were associated with the original DSN are overwritten. +The default value in Exchange 2010 and Exchange 2013 is UseExchangeDSNs. Otherwise, the default value is PreserveDSNBody. + ```yaml Type: DSNConversionOption Parameter Sets: (All) @@ -363,13 +386,9 @@ The ExternalDsnMaxMessageAttachSize parameter specifies the maximum size of the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -390,7 +409,7 @@ Accept wildcard characters: False ``` ### -ExternalDsnReportingAuthority -The ExternalDsnReportingAuthority parameter specifies what the server name should be in the machine-readable part of the external DSN message. The default value is the authoritative domain specified during installation. +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 @@ -406,7 +425,10 @@ Accept wildcard characters: False ``` ### -ExternalDsnSendHtml -The ExternalDsnSendHtml parameter specifies whether external DSN messages should be sent by using HTML or whether messages should be sent in plain text. Valid input for this parameter is $true or $false.The default value is $true. +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. +- $false: External DSNs are plain text. ```yaml Type: Boolean @@ -422,7 +444,17 @@ Accept wildcard characters: False ``` ### -ExternalPostmasterAddress -The ExternalPostmasterAddress parameter specifies the email address in the From header field of an external DSN message. The default value is $null. In the Transport service on a Mailbox server, the value of the external postmaster email address is postmaster@\<defaultaccepteddomain\>. If an Edge Transport server hasn't yet been through the EdgeSync process, and the ExternalPostmasterAddress parameter is set to $null, the external postmaster email address on the Edge Transport server is postmaster@\<edgetransportserverfqdn\>. If an Edge Transport server has completed the EdgeSync process, and the ExternalPostmasterAddress parameter is set to $null, the external postmaster email address on the Edge Transport server is postmaster@\<defaultaccepteddomain\>. To override the default behavior, you can specify an email address for the ExternalPostMasterAddress parameter. +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@<DefaultAcceptedDomain>` in the following locations: + +- On Hub Transport servers or the Transport service on Mailbox servers. +- On Edge Transport servers that are subscribed to the Exchange organization. +- In Exchange Online. + +On Edge Transport servers that aren't subscribed to the Exchange organization, the default external postmaster email address is `postmaster@<EdgeTransportServerFQDN>`. + +To override the default behavior, you can specify an email address for the ExternalPostMasterAddress parameter. ```yaml Type: SmtpAddress @@ -438,7 +470,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -463,24 +497,19 @@ On a Mailbox server, NDRs are copied to the mailbox assigned to the Exchange rec DSN codes are entered as x.y.z and are separated by commas. By default, the following DSN codes are monitored: - 5.4.8 - - 5.4.6 - - 5.4.4 - - 5.2.4 - - 5.2.0 - - 5.1.4 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Although these DSN codes are monitored by default, the associated NDRs aren't copied to the Exchange recipient or to the external postmaster address if no mailbox is assigned to the Exchange recipient or to the external postmaster address. By default, no mailbox is assigned to the Exchange recipient or to the external postmaster address. -To assign a mailbox to the Exchange recipient, use the Set-OrganizationConfig cmdlet with the MicrosoftExchangeRecipientReplyRecipient parameter. To assign a mailbox to the external postmaster address, create a new mailbox postmaster. The default email address policy of the Exchange organization should automatically add an SMTP address of postmaster@\<Authoritative domain\> to the mailbox. +To assign a mailbox to the Exchange recipient, use the Set-OrganizationConfig cmdlet with the MicrosoftExchangeRecipientReplyRecipient parameter. To assign a mailbox to the external postmaster address, create a new mailbox postmaster. The default email address policy of the Exchange organization should automatically add an SMTP address of `postmaster@<AuthoritativeDomain>` to the mailbox. ```yaml Type: MultiValuedProperty @@ -496,13 +525,11 @@ Accept wildcard characters: False ``` ### -HeaderPromotionModeSetting -The HeaderPromotionModeSetting parameter specifies whether named properties are created for custom X-headers on messages received from outside the Exchange organization. You can use one of the following values: +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. - - MayCreate: Exchange creates a named property for each new custom X-header on messages received from authenticated senders. No named properties are created for custom X-headers on messages received from unauthenticated senders. - -- NoCreate: Exchange won't create any named properties based on custom X-headers on incoming messages. +- NoCreate: Exchange won't create any named properties based on custom X-headers on incoming messages. This is the default value. ```yaml Type: HeaderPromotionMode @@ -573,11 +600,8 @@ The InternalDsnMaxMessageAttachSize parameter specifies the maximum size of the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -598,7 +622,7 @@ Accept wildcard characters: False ``` ### -InternalDsnReportingAuthority -The InternalDsnReportingAuthority parameter specifies what the server name should be in the internal DSN message. The default value is the authoritative domain specified during installation. +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 @@ -614,7 +638,10 @@ Accept wildcard characters: False ``` ### -InternalDsnSendHtml -The InternalDsnSendHtml parameter specifies whether internal DSN messages should be sent by using HTML or whether messages should be sent in plain text. Valid input for this parameter is $true or $false. The default is $true. +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. +- $false: Internal DSNs are plain text. ```yaml Type: Boolean @@ -634,9 +661,9 @@ 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. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty @@ -651,8 +678,26 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -JournalMessageExpirationDays +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -JournalingReportNdrTo -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 argument to JournalingReportNdrTo. +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 @@ -668,7 +713,7 @@ Accept wildcard characters: False ``` ### -LegacyJournalingMigrationEnabled -This parameter is available or functional only in 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. @@ -728,20 +773,16 @@ Accept wildcard characters: False ### -MaxDumpsterSizePerDatabase This parameter is available only in on-premises Exchange. -This parameter isn't used by Microsoft Exchange Server 2016. It's only used by Microsoft Exchange 2010 servers in a coexistence environment. +This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. The MaxDumpsterSizePerDatabase parameter specifies the maximum size of the transport dumpster on a Hub Transport server for each database. The default value is 18 MB. The valid input range for this parameter is from 0 through 2147483647 KB. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -766,7 +807,7 @@ Accept wildcard characters: False ### -MaxDumpsterTime This parameter is available only in on-premises Exchange. -This parameter isn't used by Microsoft Exchange Server 2016. It's only used by Microsoft Exchange 2010 servers in a coexistence environment. +This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. The MaxDumpsterTime parameter specifies how long an email message should remain in the transport dumpster on a Hub Transport server. The default value is seven days. @@ -799,11 +840,8 @@ The MaxReceiveSize parameter specifies the maximum message size that can be rece When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -812,7 +850,7 @@ A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the val The value unlimited indicates the maximum size is imposed elsewhere (for example, server, connector, or individual recipient limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -828,15 +866,17 @@ Accept wildcard characters: False ``` ### -MaxRecipientEnvelopeLimit -This parameter is available only in on-premises Exchange. +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. -The MaxRecipientEnvelopeLimit parameter specifies the maximum number of recipients in a message. 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. Exchange treats an unexpanded distribution group as one recipient. +In Exchange Online, the default value is Unlimited, which means the organizational limit of 1000 is used. You can enter a custom value up to 1000. For more information, see [Sending limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-1) in the Microsoft 365 service description. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -851,9 +891,7 @@ 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: - If ShadowMessagePreferenceSetting is set to LocalOnly, the total number of attempts to make a shadow copy of the message is the value of the MaxRetriesForLocalSiteShadow parameter. - - If ShadowMessagePreferenceSetting is set to PreferRemote, the total number of attempts to make a shadow copy of the message is the value of the MaxRetriesForLocalSiteShadow and MaxRetriesForRemoteSiteShadow parameters added together. - - If ShadowMessagePreferenceSetting is set to RemoteOnly, the value of MaxRetriesForLocalSiteShadow is 0, and the MaxRetriesForLocalSiteShadow parameter has no effect on the total number of attempts to create a shadow copy of the message. If a shadow copy of the message isn't created after the specified number of attempts, accepting or rejecting the message is controlled by the RejectMessageOnShadowFailure parameter. @@ -877,9 +915,7 @@ 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: - If ShadowMessagePreferenceSetting is set to RemoteOnly, the total number of attempts to make a shadow copy of the message is the value of the MaxRetriesForRemoteSiteShadow parameter. - - If ShadowMessagePreferenceSetting is set to PreferRemote, the total number of attempts to make a shadow copy of the message is the value of the MaxRetriesForLocalSiteShadow and MaxRetriesForRemoteSiteShadow parameters added together. - - If ShadowMessagePreferenceSetting is set to LocalOnly, the value of MaxRetriesForRemoteSiteShadow is 0, and the MaxRetriesForRemoteSiteShadow parameter has no effect on the total number of attempts to create a shadow copy of the message. If a shadow copy of the message isn't created after the specified number of attempts, accepting or rejecting the message is controlled by the RejectMessageOnShadowFailure parameter. @@ -905,11 +941,8 @@ The MaxSendSize parameter specifies the maximum message size that can be sent by When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -918,7 +951,7 @@ A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the val The value unlimited indicates the maximum size is imposed elsewhere (for example, server, connector, or individual sender limits). -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. ```yaml Type: Unlimited @@ -933,16 +966,45 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OrganizationFederatedMailbox -This parameter is available or functional only in Exchange Server 2010. +### -MessageExpiration +This parameter is available only in the cloud-based service. + +The MessageExpiration parameter specifies the message expiration timeout interval for the organization. + +To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. -The OrganizationFederatedMailbox parameter specifies the SMTP address of the federated mailbox used for federated delivery with other organizations. +The default value is 1.00:00:00 or 1 day. + +A valid value is from 12 hours (0.12:00:00) to 24 hours (1.00:00:00). + +Queued messages typically expire after 24 hours, resulting in an NDR for failed delivery. If you change this value, the NDR will be sent at the new applicable time. ```yaml -Type: SmtpAddress +Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreventDuplicateJournalingEnabled +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: + +- $true: Ensure that journaling messages aren't duplicated in hybrid environments. +- $false: Journaling messages might be duplicated in hybrid environments. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online Required: False Position: Named @@ -977,7 +1039,6 @@ 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: - $true: Messages are rejected with the SMTP code 450 4.5.1. Use this value only if you have multiple Mailbox servers in a database availability group (DAG) or in an Active Directory site where shadow copies of the messages can be created. - - $false: Messages are accepted without making shadow copies. This is the default value. The number of attempts to make a shadow copy of the message and where to make the shadow copy are controlled by the MaxRetriesForLocalSiteShadow, MaxRetriesForRemoteSiteShadow, and ShadowMessagePreferenceSetting parameter settings. @@ -995,6 +1056,78 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ReplyAllStormBlockDurationHours +This parameter is available only in the cloud-based service. + +{{ Fill ReplyAllStormBlockDurationHours Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReplyAllStormDetectionMinimumRecipients +This parameter is available only in the cloud-based service. + +{{ Fill ReplyAllStormDetectionMinimumRecipients Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReplyAllStormDetectionMinimumReplies +This parameter is available only in the cloud-based service. + +{{ Fill ReplyAllStormDetectionMinimumReplies Description }} + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReplyAllStormProtectionEnabled +This parameter is available only in the cloud-based service. + +{{ Fill ReplyAllStormProtectionEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Rfc2231EncodingEnabled 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. @@ -1058,7 +1191,7 @@ Accept wildcard characters: False ### -ShadowHeartbeatRetryCount This parameter is available only in on-premises Exchange. -This parameter isn't used by Microsoft Exchange Server 2016. It's only used by Microsoft Exchange 2010 servers in a coexistence environment. +This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. The ShadowHeartbeatRetryCount parameter specifies the number of time-outs 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. Valid input for this parameter is an integer between 1 and 15. The default value is 12. @@ -1080,7 +1213,7 @@ Accept wildcard characters: False ### -ShadowHeartbeatTimeoutInterval This parameter is available only in on-premises Exchange. -This parameter isn't used by Microsoft Exchange Server 2016. It's only used by Microsoft Exchange 2010 servers in a coexistence environment. +This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. The ShadowHeartbeatTimeoutInterval 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. @@ -1131,9 +1264,7 @@ 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: - LocalOnly: A shadow copy of the message should only be made on a server in the local Active Directory site. - - RemoteOnly: A shadow copy of the message should only be made on a server in a different Active Directory site. - - PreferRemote: Try to make a shadow copy of the message in a different Active Directory site. If the operation fails, try make a shadow copy of the message on a server in the local Active Directory site. The default value is PreferRemote. @@ -1199,18 +1330,14 @@ 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: - POP3 and IMAP4 clients. - - Devices with scan to email capability. - - Workflow applications that send email notifications. - - Online services that send messages using internal email addresses in the organization. Valid values for this parameter are: -- $true: Authenticated SMTP is disabled. - -- $false: Authenticated SMTP is enabled. This is the default value. +- $true: Authenticated SMTP is disabled. This is the default value for organizations created after January 2020. +- $false: Authenticated SMTP is enabled. The corresponding parameter that controls authenticated SMTP on individual mailboxes is the SmtpClientAuthenticationDisabled parameter on the Set-CASMailbox cmdlet. The default mailbox value is blank ($null), which means the mailbox setting is controlled by this organizational setting. @@ -1255,14 +1382,12 @@ 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: - Enable Domain Security (Mutual Auth TLS) and the TLS authentication method on the Receive connectors that receive messages from the domains that you specified with the TLSReceiveDomainSecureList parameter. - - Specify the domains to which you want to send domain secured email by using the TLSSendDomainSecureList parameter. - - Enable Domain Security (Mutual Auth TLS) on the Send connectors that send messages to the domains that you specified in the TLSSendDomainSecureList 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. The wildcard character (\*) isn't supported in the domains listed in the TLSReceiveDomainSecureList parameter or in the TLSSendDomainSecureList parameter. The default value for both parameters is an empty list ({}). @@ -1285,14 +1410,12 @@ 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: - Enable Domain Security (Mutual Auth TLS) on the Send connectors that send messages to the domains that you specified in the TLSSendDomainSecureList parameter. - - Specify the domains from which you want to receive domain secured email by using the TLSReceiveDomainSecureList parameter. - - Enable Domain Security (Mutual Auth TLS) and the TLS authentication method on the Receive connectors that receive messages from the domains that you specified in the TLSReceiveDomainSecureList 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. Multiple domains may be separated by commas. The wildcard character (\*) isn't supported in the domains listed in the TLSSendDomainSecureList parameter or in the TLSReceiveSecureList parameter. The default values for both parameters are an empty list ({}). @@ -1312,20 +1435,19 @@ Accept wildcard characters: False ### -TransportRuleAttachmentTextScanLimit 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. The default value is 150 kilobytes (KB). +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. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +In Exchange Online, Exchange 2019, and Exchange 2016, the default value is 1 MB (1,048,576 bytes). In Exchange 2013, the default value is 150 KB (153,600 bytes). + If the amount of text in the attachment is larger than the value of this parameter, only the specified amount of text is scanned. For example, if a 5 megabyte attachment contains 300 kilobytes of text, and the value of TransportRuleAttachmentTextScanLimit is 150 kilobytes, only the first 150 kilobytes of text are extracted and scanned. ```yaml @@ -1364,7 +1486,7 @@ Accept wildcard characters: False ``` ### -VoicemailJournalingEnabled -This parameter is available only in on-premises Exchange. +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. @@ -1372,7 +1494,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1420,12 +1542,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-TransportRule.md b/exchange/exchange-ps/exchange/Set-TransportRule.md similarity index 76% rename from exchange/exchange-ps/exchange/policy-and-compliance/Set-TransportRule.md rename to exchange/exchange-ps/exchange/Set-TransportRule.md index c2df275ea9..d5e0d7dd39 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-TransportRule.md +++ b/exchange/exchange-ps/exchange/Set-TransportRule.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-transportrule +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-TransportRule @@ -17,9 +16,13 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-TransportRule cmdlet to modify existing transport rules (mail flow rules) in your organization. -If you delete all conditions and exceptions from a rule, the rule action is applied to all messages. This can have unintended consequences. For example, if the rule action is to delete the message, removing the conditions and exceptions could cause the rule to delete all inbound and outbound messages for the entire organization. +**Note**: -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +- The action of a rule without conditions or exceptions is applied to all messages, which could have unintended consequences. For example, if the rule action deletes messages, the rule without conditions or exceptions might delete all inbound and outbound messages for the entire organization. + +- Rules that use Active Directory or Microsoft Entra ID properties as conditions or exceptions work only on senders or recipients in the organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,109 +32,109 @@ Set-TransportRule [-Identity] <RuleIdParameter> [-ADComparisonAttribute <ADAttribute>] [-ADComparisonOperator <Evaluation>] [-AddManagerAsRecipientType <AddedRecipientType>] - [-AddToRecipients <RecipientIdParameter []>] - [-AnyOfCcHeader <RecipientIdParameter []>] - [-AnyOfCcHeaderMemberOf <RecipientIdParameter []>] - [-AnyOfRecipientAddressContainsWords <Word []>] - [-AnyOfRecipientAddressMatchesPatterns <Pattern []>] - [-AnyOfToCcHeader <RecipientIdParameter []>] - [-AnyOfToCcHeaderMemberOf <RecipientIdParameter []>] - [-AnyOfToHeader <RecipientIdParameter []>] - [-AnyOfToHeaderMemberOf <RecipientIdParameter []>] + [-AddToRecipients <RecipientIdParameter[]>] + [-AnyOfCcHeader <RecipientIdParameter[]>] + [-AnyOfCcHeaderMemberOf <RecipientIdParameter[]>] + [-AnyOfRecipientAddressContainsWords <Word[]>] + [-AnyOfRecipientAddressMatchesPatterns <Pattern[]>] + [-AnyOfToCcHeader <RecipientIdParameter[]>] + [-AnyOfToCcHeaderMemberOf <RecipientIdParameter[]>] + [-AnyOfToHeader <RecipientIdParameter[]>] + [-AnyOfToHeaderMemberOf <RecipientIdParameter[]>] [-ApplyClassification <String>] [-ApplyHtmlDisclaimerFallbackAction <DisclaimerFallbackAction>] [-ApplyHtmlDisclaimerLocation <DisclaimerLocation>] [-ApplyHtmlDisclaimerText <DisclaimerText>] [-ApplyOME <Boolean>] + [-ApplyRightsProtectionCustomizationTemplate <OMEConfigurationIdParameter>] [-ApplyRightsProtectionTemplate <RmsTemplateIdParameter>] - [-AttachmentContainsWords <Word []>] - [-AttachmentExtensionMatchesWords <Word []>] + [-AttachmentContainsWords <Word[]>] + [-AttachmentExtensionMatchesWords <Word[]>] [-AttachmentHasExecutableContent <Boolean>] [-AttachmentIsPasswordProtected <Boolean>] [-AttachmentIsUnsupported <Boolean>] - [-AttachmentMatchesPatterns <Pattern []>] - [-AttachmentNameMatchesPatterns <Pattern []>] + [-AttachmentMatchesPatterns <Pattern[]>] + [-AttachmentNameMatchesPatterns <Pattern[]>] [-AttachmentProcessingLimitExceeded <Boolean>] - [-AttachmentPropertyContainsWords <Word []>] + [-AttachmentPropertyContainsWords <Word[]>] [-AttachmentSizeOver <ByteQuantifiedSize>] - [-BetweenMemberOf1 <RecipientIdParameter []>] - [-BetweenMemberOf2 <RecipientIdParameter []>] - [-BlindCopyTo <RecipientIdParameter []>] + [-BetweenMemberOf1 <RecipientIdParameter[]>] + [-BetweenMemberOf2 <RecipientIdParameter[]>] + [-BlindCopyTo <RecipientIdParameter[]>] [-Comments <String>] [-Confirm] - [-ContentCharacterSetContainsWords <Word []>] - [-CopyTo <RecipientIdParameter []>] + [-ContentCharacterSetContainsWords <Word[]>] + [-CopyTo <RecipientIdParameter[]>] [-DeleteMessage <Boolean>] [-Disconnect <Boolean>] [-DlpPolicy <String>] [-DomainController <Fqdn>] [-ExceptIfADComparisonAttribute <ADAttribute>] [-ExceptIfADComparisonOperator <Evaluation>] - [-ExceptIfAnyOfCcHeader <RecipientIdParameter []>] - [-ExceptIfAnyOfCcHeaderMemberOf <RecipientIdParameter []>] - [-ExceptIfAnyOfRecipientAddressContainsWords <Word []>] - [-ExceptIfAnyOfRecipientAddressMatchesPatterns <Pattern []>] - [-ExceptIfAnyOfToCcHeader <RecipientIdParameter []>] - [-ExceptIfAnyOfToCcHeaderMemberOf <RecipientIdParameter []>] - [-ExceptIfAnyOfToHeader <RecipientIdParameter []>] - [-ExceptIfAnyOfToHeaderMemberOf <RecipientIdParameter []>] - [-ExceptIfAttachmentContainsWords <Word []>] - [-ExceptIfAttachmentExtensionMatchesWords <Word []>] + [-ExceptIfAnyOfCcHeader <RecipientIdParameter[]>] + [-ExceptIfAnyOfCcHeaderMemberOf <RecipientIdParameter[]>] + [-ExceptIfAnyOfRecipientAddressContainsWords <Word[]>] + [-ExceptIfAnyOfRecipientAddressMatchesPatterns <Pattern[]>] + [-ExceptIfAnyOfToCcHeader <RecipientIdParameter[]>] + [-ExceptIfAnyOfToCcHeaderMemberOf <RecipientIdParameter[]>] + [-ExceptIfAnyOfToHeader <RecipientIdParameter[]>] + [-ExceptIfAnyOfToHeaderMemberOf <RecipientIdParameter[]>] + [-ExceptIfAttachmentContainsWords <Word[]>] + [-ExceptIfAttachmentExtensionMatchesWords <Word[]>] [-ExceptIfAttachmentHasExecutableContent <Boolean>] [-ExceptIfAttachmentIsPasswordProtected <Boolean>] [-ExceptIfAttachmentIsUnsupported <Boolean>] - [-ExceptIfAttachmentMatchesPatterns <Pattern []>] - [-ExceptIfAttachmentNameMatchesPatterns <Pattern []>] + [-ExceptIfAttachmentMatchesPatterns <Pattern[]>] + [-ExceptIfAttachmentNameMatchesPatterns <Pattern[]>] [-ExceptIfAttachmentProcessingLimitExceeded <Boolean>] - [-ExceptIfAttachmentPropertyContainsWords <Word []>] + [-ExceptIfAttachmentPropertyContainsWords <Word[]>] [-ExceptIfAttachmentSizeOver <ByteQuantifiedSize>] - [-ExceptIfBetweenMemberOf1 <RecipientIdParameter []>] - [-ExceptIfBetweenMemberOf2 <RecipientIdParameter []>] - [-ExceptIfContentCharacterSetContainsWords <Word []>] - [-ExceptIfFrom <RecipientIdParameter []>] - [-ExceptIfFromAddressContainsWords <Word []>] - [-ExceptIfFromAddressMatchesPatterns <Pattern []>] - [-ExceptIfFromMemberOf <RecipientIdParameter []>] + [-ExceptIfBetweenMemberOf1 <RecipientIdParameter[]>] + [-ExceptIfBetweenMemberOf2 <RecipientIdParameter[]>] + [-ExceptIfContentCharacterSetContainsWords <Word[]>] + [-ExceptIfFrom <RecipientIdParameter[]>] + [-ExceptIfFromAddressContainsWords <Word[]>] + [-ExceptIfFromAddressMatchesPatterns <Pattern[]>] + [-ExceptIfFromMemberOf <RecipientIdParameter[]>] [-ExceptIfFromScope <FromUserScope>] [-ExceptIfHasClassification <String>] [-ExceptIfHasNoClassification <Boolean>] [-ExceptIfHasSenderOverride <Boolean>] [-ExceptIfHeaderContainsMessageHeader <HeaderName>] - [-ExceptIfHeaderContainsWords <Word []>] + [-ExceptIfHeaderContainsWords <Word[]>] [-ExceptIfHeaderMatchesMessageHeader <HeaderName>] - [-ExceptIfHeaderMatchesPatterns <Pattern []>] - [-ExceptIfManagerAddresses <RecipientIdParameter []>] + [-ExceptIfHeaderMatchesPatterns <Pattern[]>] + [-ExceptIfManagerAddresses <RecipientIdParameter[]>] [-ExceptIfManagerForEvaluatedUser <EvaluatedUser>] - [-ExceptIfMessageContainsAllDataClassifications <Hashtable []>] - [-ExceptIfMessageContainsDataClassifications <Hashtable []>] + [-ExceptIfMessageContainsDataClassifications <Hashtable[]>] [-ExceptIfMessageSizeOver <ByteQuantifiedSize>] [-ExceptIfMessageTypeMatches <MessageType>] - [-ExceptIfRecipientADAttributeContainsWords <Word []>] - [-ExceptIfRecipientADAttributeMatchesPatterns <Pattern []>] - [-ExceptIfRecipientAddressContainsWords <Word []>] - [-ExceptIfRecipientAddressMatchesPatterns <Pattern []>] - [-ExceptIfRecipientDomainIs <Word []>] - [-ExceptIfRecipientInSenderList <Word []>] + [-ExceptIfRecipientADAttributeContainsWords <Word[]>] + [-ExceptIfRecipientADAttributeMatchesPatterns <Pattern[]>] + [-ExceptIfRecipientAddressContainsWords <Word[]>] + [-ExceptIfRecipientAddressMatchesPatterns <Pattern[]>] + [-ExceptIfRecipientDomainIs <Word[]>] + [-ExceptIfRecipientInSenderList <Word[]>] [-ExceptIfSCLOver <SclValue>] - [-ExceptIfSenderADAttributeContainsWords <Word []>] - [-ExceptIfSenderADAttributeMatchesPatterns <Pattern []>] - [-ExceptIfSenderDomainIs <Word []>] - [-ExceptIfSenderInRecipientList <Word []>] + [-ExceptIfSenderADAttributeContainsWords <Word[]>] + [-ExceptIfSenderADAttributeMatchesPatterns <Pattern[]>] + [-ExceptIfSenderDomainIs <Word[]>] + [-ExceptIfSenderInRecipientList <Word[]>] [-ExceptIfSenderIpRanges <MultiValuedProperty>] [-ExceptIfSenderManagementRelationship <ManagementRelationship>] - [-ExceptIfSentTo <RecipientIdParameter []>] - [-ExceptIfSentToMemberOf <RecipientIdParameter []>] + [-ExceptIfSentTo <RecipientIdParameter[]>] + [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] [-ExceptIfSentToScope <ToUserScope>] - [-ExceptIfSubjectContainsWords <Word []>] - [-ExceptIfSubjectMatchesPatterns <Pattern []>] - [-ExceptIfSubjectOrBodyContainsWords <Word []>] - [-ExceptIfSubjectOrBodyMatchesPatterns <Pattern []>] + [-ExceptIfSubjectContainsWords <Word[]>] + [-ExceptIfSubjectMatchesPatterns <Pattern[]>] + [-ExceptIfSubjectOrBodyContainsWords <Word[]>] + [-ExceptIfSubjectOrBodyMatchesPatterns <Pattern[]>] [-ExceptIfWithImportance <Importance>] [-ExpiryDate <DateTime>] - [-From <RecipientIdParameter []>] - [-FromAddressContainsWords <Word []>] - [-FromAddressMatchesPatterns <Pattern []>] - [-FromMemberOf <RecipientIdParameter []>] + [-From <RecipientIdParameter[]>] + [-FromAddressContainsWords <Word[]>] + [-FromAddressMatchesPatterns <Pattern[]>] + [-FromMemberOf <RecipientIdParameter[]>] [-FromScope <FromUserScope>] [-GenerateIncidentReport <RecipientIdParameter>] [-GenerateNotification <DisclaimerText>] @@ -139,52 +142,53 @@ Set-TransportRule [-Identity] <RuleIdParameter> [-HasNoClassification <Boolean>] [-HasSenderOverride <Boolean>] [-HeaderContainsMessageHeader <HeaderName>] - [-HeaderContainsWords <Word []>] + [-HeaderContainsWords <Word[]>] [-HeaderMatchesMessageHeader <HeaderName>] - [-HeaderMatchesPatterns <Pattern []>] - [-IncidentReportContent <IncidentReportContent []>] + [-HeaderMatchesPatterns <Pattern[]>] + [-IncidentReportContent <IncidentReportContent[]>] [-IncidentReportOriginalMail <IncidentReportOriginalMail>] [-LogEventText <EventLogText>] - [-ManagerAddresses <RecipientIdParameter []>] + [-ManagerAddresses <RecipientIdParameter[]>] [-ManagerForEvaluatedUser <EvaluatedUser>] - [-MessageContainsAllDataClassifications <Hashtable []>] - [-MessageContainsDataClassifications <Hashtable []>] + [-MessageContainsDataClassifications <Hashtable[]>] [-MessageSizeOver <ByteQuantifiedSize>] [-MessageTypeMatches <MessageType>] [-Mode <RuleMode>] [-ModerateMessageByManager <Boolean>] - [-ModerateMessageByUser <RecipientIdParameter []>] + [-ModerateMessageByUser <RecipientIdParameter[]>] [-Name <String>] [-NotifySender <NotifySenderType>] [-PrependSubject <SubjectPrefix>] [-Priority <Int32>] [-Quarantine <Boolean>] - [-RecipientADAttributeContainsWords <Word []>] - [-RecipientADAttributeMatchesPatterns <Pattern []>] - [-RecipientAddressContainsWords <Word []>] - [-RecipientAddressMatchesPatterns <Pattern []>] - [-RecipientDomainIs <Word []>] - [-RecipientInSenderList <Word []>] - [-RedirectMessageTo <RecipientIdParameter []>] + [-RecipientADAttributeContainsWords <Word[]>] + [-RecipientADAttributeMatchesPatterns <Pattern[]>] + [-RecipientAddressContainsWords <Word[]>] + [-RecipientAddressMatchesPatterns <Pattern[]>] + [-RecipientAddressType <RecipientAddressType>] + [-RecipientDomainIs <Word[]>] + [-RecipientInSenderList <Word[]>] + [-RedirectMessageTo <RecipientIdParameter[]>] [-RejectMessageEnhancedStatusCode <RejectEnhancedStatus>] [-RejectMessageReasonText <RejectText>] [-RemoveHeader <HeaderName>] [-RemoveOME <Boolean>] [-RemoveOMEv2 <Boolean>] + [-RemoveRMSAttachmentEncryption <Boolean>] [-RouteMessageOutboundConnector <OutboundConnectorIdParameter>] [-RouteMessageOutboundRequireTls <Boolean>] [-RuleErrorAction <RuleErrorAction>] [-RuleSubType <RuleSubType>] [-SCLOver <SclValue>] - [-SenderADAttributeContainsWords <Word []>] - [-SenderADAttributeMatchesPatterns <Pattern []>] + [-SenderADAttributeContainsWords <Word[]>] + [-SenderADAttributeMatchesPatterns <Pattern[]>] [-SenderAddressLocation <SenderAddressLocation>] - [-SenderDomainIs <Word []>] - [-SenderInRecipientList <Word []>] + [-SenderDomainIs <Word[]>] + [-SenderInRecipientList <Word[]>] [-SenderIpRanges <MultiValuedProperty>] [-SenderManagementRelationship <ManagementRelationship>] - [-SentTo <RecipientIdParameter []>] - [-SentToMemberOf <RecipientIdParameter []>] + [-SentTo <RecipientIdParameter[]>] + [-SentToMemberOf <RecipientIdParameter[]>] [-SentToScope <ToUserScope>] [-SetAuditSeverity <String>] [-SetHeaderName <HeaderName>] @@ -193,10 +197,10 @@ Set-TransportRule [-Identity] <RuleIdParameter> [-SmtpRejectMessageRejectStatusCode <RejectStatusCode>] [-SmtpRejectMessageRejectText <RejectText>] [-StopRuleProcessing <Boolean>] - [-SubjectContainsWords <Word []>] - [-SubjectMatchesPatterns <Pattern []>] - [-SubjectOrBodyContainsWords <Word []>] - [-SubjectOrBodyMatchesPatterns <Pattern []>] + [-SubjectContainsWords <Word[]>] + [-SubjectMatchesPatterns <Pattern[]>] + [-SubjectOrBodyContainsWords <Word[]>] + [-SubjectOrBodyMatchesPatterns <Pattern[]>] [-WhatIf] [-WithImportance <Importance>] [<CommonParameters>] @@ -207,7 +211,7 @@ In on-premises Exchange organizations, rules created on Mailbox servers are stor The search for words or text patterns in the subject or other header fields in the message occurs after the message has been decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -218,17 +222,13 @@ Set-TransportRule "Sales Team Disclaimer" -FromMemberOf "Sales Department" This example modifies the existing rule named Sales Team Disclaimer transport rule by adding the condition that the sender of the message is a member of the Sales Department group. -This example sets the FromMemberOf parameter to a value of Sales-Group, which specifies that the rule is applied if the sender of the message is a member of the Sales-Group distribution group. - ## PARAMETERS ### -Identity The Identity parameter specifies the rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -247,7 +247,7 @@ Accept wildcard characters: False ### -ActivationDate 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". +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". ```yaml Type: DateTime @@ -265,64 +265,38 @@ Accept wildcard characters: False ### -ADComparisonAttribute 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ADComparisonAttribute parameter specifies a condition that compares an Active Directory attribute between the sender and all recipients of the message. This parameter works when the recipients are individual users. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode If you don't use the ADComparisonOperator parameter, the default comparison operator Equal is used. @@ -343,12 +317,11 @@ Accept wildcard characters: False ### -ADComparisonOperator 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ADComparisonOperator parameter specifies the comparison operator for the ADComparisonAttribute parameter. Valid values are: - Equal (This is the default value) - - NotEqual ```yaml @@ -367,16 +340,13 @@ Accept wildcard characters: False ### -AddManagerAsRecipientType This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The AddManagerAsRecipientType parameter specifies an action that delivers or redirects messages to the user that's defined in the sender's Manager attribute. Valid values are: - To: Add the sender's manager to the To field of the message. - - Cc: Add the sender's manager to the Cco field of the message. - - Bcc: Add the sender's manager to the Bcc field of the message. - - Redirect: Redirect the message to the sender's manager without notifying the sender or the recipients. This action only works if the sender's Manager attribute is defined. @@ -402,18 +372,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The AddToRecipients parameter specifies an action that adds recipients to the To field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -431,27 +396,22 @@ Accept wildcard characters: False ### -AnyOfCcHeader 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfCcHeader parameter specifies a condition that looks for recipients in the Cc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -469,27 +429,22 @@ Accept wildcard characters: False ### -AnyOfCcHeaderMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfCcHeaderMemberOf parameter specifies a condition that looks for group members in the Cc field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -513,7 +468,7 @@ The AnyOfRecipientAddressContainsWords parameter specifies a condition that look A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Word[] @@ -533,11 +488,11 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The AnyOfRecipientAddressMatchesPatterns parameter specifies a condition 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 AnyOfRecipientAddressMatchesPatterns parameter specifies a condition 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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Pattern[] @@ -555,27 +510,22 @@ Accept wildcard characters: False ### -AnyOfToCcHeader 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToCcHeader parameter specifies a condition that looks for recipients in the To or Cc fields of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -593,27 +543,22 @@ Accept wildcard characters: False ### -AnyOfToCcHeaderMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToCcHeaderMemberOf parameter specifies a condition that looks for group members in the To and Cc fields of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -631,27 +576,22 @@ Accept wildcard characters: False ### -AnyOfToHeader 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToHeader parameter specifies a condition that looks for recipients in the To field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -669,27 +609,22 @@ Accept wildcard characters: False ### -AnyOfToHeaderMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AnyOfToHeaderMemberOf parameter specifies a condition that looks for group members in the To field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this condition applies the rule action to all recipients of the message. For example, if the action is to reject the message, the message is rejected for all recipients of the message, not just for the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -707,7 +642,7 @@ Accept wildcard characters: False ### -ApplyClassification This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyClassification parameter specifies an action that applies a message classification to messages. Use the Get-MessageClassification cmdlet to see the message classification objects that are available. @@ -729,15 +664,20 @@ Accept wildcard characters: False ### -ApplyHtmlDisclaimerFallbackAction This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. + +The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be applied to a message (for example, encrypted or signed messages where the contents can't be altered). Valid values are: + +- Wrap: This is the default value. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients. -The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be added to a message. Valid values are: + If you want other rules to examine and act on the original message (which is now an attachment in the new message), make sure those rules are applied _before_ the disclaimer rule by using a lower priority for the disclaimer rule and higher priority for other rules. -- Wrap: The original message is wrapped in a new message envelope, and the disclaimer is used as the message body for the new message. This is the default value. Subsequent mail flow rules are applied to the new message envelope, not to the original message. Therefore, configure a rule with this action at a lower priority (a higher priority number) than other rules. If the original message can't be wrapped in a new message envelope, the original message isn't delivered. The message is returned to the sender in an non-delivery report (also known as an NDR or bounce message). + If the process of inserting the original message as an attachment in the new message fails, the original message isn't delivered. The original message is returned to the sender in an NDR. -- Ignore: The rule is ignored and the message is delivered without the disclaimer. + In Microsoft 365, don't use this value in rules that affect incoming messages from external senders. Use the value Reject instead. The effects of the value Wrap interfere with Safe Attachments scanning of messages from external senders. -- Reject: The message is rejected. +- Ignore: The rule is ignored and the original message is delivered without the disclaimer. +- Reject: The original message is returned to the sender in an NDR. If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Wrap is used. @@ -757,13 +697,12 @@ Accept wildcard characters: False ### -ApplyHtmlDisclaimerLocation This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerLocation parameter specifies where to insert the HTML disclaimer text in the body of messages. Valid values are: - Append: The disclaimer is added to the end of the message body. This is the default value. - -- Prepend: The disclaimer is inserted to the beginning of the message body. +- Prepend: The disclaimer is inserted at the beginning of the message body. If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Append is used. @@ -783,10 +722,38 @@ Accept wildcard characters: False ### -ApplyHtmlDisclaimerText This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerText parameter specifies an action that adds the disclaimer text to messages. Disclaimer text can include HTML tags and inline cascading style sheet (CSS) tags. You can add images using the IMG tag. +This parameter also supports the following tokens that use values from the sender: + +- %%City%% +- %%Company%% +- %%CountryOrRegion%% +- %%Department%% +- %%DisplayName%% +- %%Fax%% +- %%FirstName%% +- %%HomePhone%% +- %%Initials%% +- %%LastName%% +- %%Manager%% +- %%MobilePhone%% +- %%Notes%% +- %%Office%% +- %%Pager%% +- %%Phone%% +- %%PostalCode%% +- %%PostOfficeBox%% +- %%StateOrProvince%% +- %%StreetAddress%% +- %%Title%% +- %%UserPrincipalName%% +- %%WindowsEmailAddress%% + +The maximum number of characters is 5000. + You use the ApplyHtmlDisclaimerLocation parameter to specify where to insert the text in the message body (the default value is Append), and the ApplyHtmlDisclaimerFallbackAction parameter to specify what to do if the disclaimer can't be added to the message (the default value is Wrap). ```yaml @@ -810,7 +777,6 @@ This parameter specifies an action or part of an action for the rule. The ApplyOME parameter specifies an action that encrypts messages and their attachments by using Office 365 Message Encryption. Valid values are: - $true: The message and attachments are encrypted. - - $false: The message and attachments aren't encrypted. ```yaml @@ -826,10 +792,30 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ApplyRightsProtectionCustomizationTemplate +This parameter is available only in the cloud-based service. + +This parameter specifies an action or part of an action for the rule. + +The ApplyRightsProtectionCustomizationTemplate parameter specifies an action that applies a custom branding template for OME encrypted messages. You identify the custom branding template by name. If the name contains spaces, enclose the name in quotation marks ("). + +```yaml +Type: OMEConfigurationIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ApplyRightsProtectionTemplate This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ApplyRightsProtectionTemplate parameter specifies an action that applies rights management service (RMS) templates to messages. You identify the RMS template by name. If the name contains spaces, enclose the name in quotation marks ("). @@ -837,7 +823,7 @@ To use this action, you need to have an Active Directory Rights Management Servi Use the Get-RMSTemplate cmdlet to see the RMS templates that are available. -For more information, see [Transport protection rules](https://docs.microsoft.com/exchange/transport-protection-rules-exchange-2013-help). +For more information, see [Transport protection rules](https://learn.microsoft.com/exchange/transport-protection-rules-exchange-2013-help). ```yaml Type: RmsTemplateIdParameter @@ -855,7 +841,7 @@ Accept wildcard characters: False ### -AttachmentContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentContainsWords parameter specifies a condition that looks for words in message attachments. Only supported attachment types are checked. @@ -877,10 +863,12 @@ Accept wildcard characters: False ### -AttachmentExtensionMatchesWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentExtensionMatchesWords parameter specifies a condition that looks for words in the file name extensions of message attachments. You can specify multiple words separated by commas. +**Note:** Nested attachment extensions (files inside the original attachments) are also inspected. To see all attachment extensions that were evaluated for a specific message, use the Test-TextExtraction cmdlet. + ```yaml Type: Word[] Parameter Sets: (All) @@ -897,14 +885,15 @@ Accept wildcard characters: False ### -AttachmentHasExecutableContent 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentHasExecutableContent parameter specifies a condition that looks for executable content in message attachments. Valid values are: +The AttachmentHasExecutableContent parameter specifies a condition that inspects messages where an attachment is an executable file. Valid values are: - $true: Look for executable content in message attachments. - - $false: Don't look for executable content in message attachments. +The system inspects the file properties rather than relying on the file extension. For more information, see [Supported executable file types for mail flow rule inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-executable-file-types-for-mail-flow-rule-inspection). + ```yaml Type: Boolean Parameter Sets: (All) @@ -921,12 +910,11 @@ Accept wildcard characters: False ### -AttachmentIsPasswordProtected 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentIsPasswordProtected parameter specifies a condition that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection only works for Office documents and .zip files. Valid values are: +The AttachmentIsPasswordProtected parameter specifies a condition that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z), and .pdf files. Valid values are: - $true: Look for password protected attachments. - - $false: Don't look for password protected attachments. ```yaml @@ -945,15 +933,18 @@ Accept wildcard characters: False ### -AttachmentIsUnsupported 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentIsUnsupported parameter specifies a condition that looks for unsupported file types in messages. Unsupported file types are message attachments that aren't natively recognized by Exchange, and the required IFilter isn't installed. Valid values are: +The AttachmentIsUnsupported parameter specifies a condition that looks for unsupported file types in messages. Valid values are: - $true: Look for unsupported file types in messages. - - $false: Don't look for unsupported file types in messages. -For more information, see [Register Filter Pack IFilters with Exchange 2013](https://docs.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). +Rules can inspect the content of supported file types only. If the rule finds an attachment file type that isn't supported, the AttachmentIsUnsupported condition is triggered. + +For the list of supported file types, see [Supported file types for mail flow rule content inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-file-types-for-mail-flow-rule-content-inspection). + +In Exchange 2010, to extend the list of supported file types, see [Register Filter Pack IFilters](https://learn.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). ```yaml Type: Boolean @@ -971,11 +962,11 @@ Accept wildcard characters: False ### -AttachmentMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentMatchesPatterns parameter specifies a condition 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\>". +You can specify multiple text patterns by using the following syntax: `"Regular expression1","Regular expression2",..."Regular expressionN"`. Only the first 150 kilobytes (KB) of the attachment is scanned when trying to match a text pattern. @@ -995,9 +986,9 @@ Accept wildcard characters: False ### -AttachmentNameMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The AttachmentNameMatchesPatterns parameter specifies a condition that looks for text patterns in the file 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 AttachmentNameMatchesPatterns parameter specifies a condition that looks for text patterns in the file 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"`. ```yaml Type: Pattern[] @@ -1015,12 +1006,11 @@ Accept wildcard characters: False ### -AttachmentProcessingLimitExceeded 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentProcessingLimitExceeded parameter specifies a condition that looks for messages where attachment scanning didn't complete. Valid values are: - $true: Look for messages where attachment scanning didn't complete. - - $false: Don't look for messages where attachment scanning didn't complete. You use this condition to create rules that work together with other attachment processing rules to handle messages where the content can't be fully scanned. @@ -1041,36 +1031,23 @@ Accept wildcard characters: False ### -AttachmentPropertyContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The AttachmentPropertyContainsWords parameter specifies a condition that looks for words in the properties of attached Office documents. This condition helps integrate mail flow rules (transport rules) with the File Classification Infrastructure (FCI) in Windows Server 2012 R2 or later, SharePoint, or a third-party classification system. Valid values are a built-in document property, or a custom property. The built-in document properties are: - Business Impact - - Compliancy - - Confidentiality - - Department - - Impact - - Intellectual Property - - Personally Identifiable Information - - Personal Information - - Personal Use - - Required Clearance - - PHI - - PII - - Project - - Protected Health Information The syntax for this parameter is "PropertyName:Word". To specify multiple properties, or multiple words for the same property, use the following syntax: "PropertyName1:Word1,Phrase with spaces,word2,...","PropertyName2:Word3,Phrase with spaces,word4,...". Don't use leading or trailing spaces. @@ -1081,7 +1058,7 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1100,17 +1077,15 @@ The AttachmentSizeOver parameter specifies a condition that looks for messages w When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages will be blocked. + ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) @@ -1127,23 +1102,18 @@ Accept wildcard characters: False ### -BetweenMemberOf1 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The BetweenMemberOf1 parameter specifies a condition that looks for messages that are sent between group members. You need to use this parameter with the BetweenMemberOf2 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1161,23 +1131,18 @@ Accept wildcard characters: False ### -BetweenMemberOf2 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The BetweenMemberOf2 parameter specifies a condition that looks for messages that are sent between group members. You need to use this parameter with the BetweenMemberOf1 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1200,18 +1165,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The BlindCopyTo parameter specifies an action that adds recipients to the Bcc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1245,8 +1205,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -1265,7 +1224,7 @@ Accept wildcard characters: False ### -ContentCharacterSetContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ContentCharacterSetContainsWords parameter specifies a condition that looks for character set names in messages. @@ -1292,18 +1251,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The CopyTo parameter specifies an action that adds recipients to the Cc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -1326,7 +1280,6 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The DeleteMessage parameter specifies an action that silently drops messages without an NDR. Valid values are: - $true: Silently drop the message without an NDR. - - $false: Don't silently drop the message. ```yaml @@ -1343,21 +1296,20 @@ Accept wildcard characters: False ``` ### -Disconnect -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The Disconnect parameter specifies an action that ends the SMTP connection between the sending server and the Edge Transport server without generating an NDR. - $true: Silently end the SMTP session without generating an NDR. - - $false: Don't silently end the SMTP session. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1367,13 +1319,15 @@ Accept wildcard characters: False ``` ### -DlpPolicy -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://docs.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/data-loss-prevention). +**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). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1403,66 +1357,40 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonAttribute -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfADComparisonAttribute parameter specifies an exception that compares an Active Directory attribute between the sender and all recipients of the message. This parameter works when the recipients are individual users. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode If you don't use the ExceptIfADComparisonOperator parameter, the default comparison operator Equal is used. @@ -1481,14 +1409,13 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonOperator -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfADComparisonOperator parameter specifies the comparison operator for the ExceptIfADComparisonAttribute parameter. Valid values are: - Equal (This is the default value) - - NotEqual ```yaml @@ -1505,29 +1432,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfCcHeader parameter specifies an exception that looks for recipients in the Cc field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1543,29 +1465,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeaderMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfCcHeaderMemberOf parameter specifies an exception that looks for group members in the Cc field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1581,7 +1498,7 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -1589,7 +1506,7 @@ The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Word[] @@ -1605,15 +1522,15 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfAnyOfRecipientAddressMatchesPatterns parameter specifies an exception 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 ExceptIfAnyOfRecipientAddressMatchesPatterns parameter specifies an exception 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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: Pattern[] @@ -1629,29 +1546,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToCcHeader parameter specifies an exception that looks for recipients in the To or Cc fields of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1667,29 +1579,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeaderMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToCcHeaderMemberOf parameter specifies an exception that looks for group members in the To and Cc fields of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1705,29 +1612,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToHeader parameter specifies an exception that looks for recipients in the To field of messages. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1743,29 +1645,24 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeaderMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAnyOfToHeaderMemberOf parameter specifies an exception that looks for group members in the To field of messages. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. A match for this exception prevents the rule action from being applied to all recipients of the message. For example, if the action is to reject the message, the message is delivered to all recipients of the message, not just to the specified recipients. -Note: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. +**Note**: This condition or exception doesn't consider messages that are sent to recipient proxy addresses. It only matches messages that are sent to the recipient's primary email address. ```yaml Type: RecipientIdParameter[] @@ -1781,9 +1678,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentContainsWords parameter specifies an exception that looks for words in message attachments. Only supported attachment types are checked. @@ -1803,12 +1700,14 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentExtensionMatchesWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentExtensionMatchesWords parameter specifies an exception that looks for words in the file name extensions of message attachments. You can specify multiple words separated by commas. +**Note:** Nested attachment extensions (files inside the original attachments) are also inspected. To see all attachment extensions that were evaluated for a specific message, use the Test-TextExtraction cmdlet. + ```yaml Type: Word[] Parameter Sets: (All) @@ -1823,16 +1722,17 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentHasExecutableContent -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentHasExecutableContent parameter specifies an exception that looks for executable content in message attachments. Valid values are: +The ExceptIfAttachmentHasExecutableContent parameter specifies an exception that inspects messages where an attachment is an executable file. Valid values are: - $true: Look for executable content in message attachments. - - $false: Don't look for executable content in message attachments. +The system inspects the file properties rather than relying on the file extension. For more information, see [Supported executable file types for mail flow rule inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-executable-file-types-for-mail-flow-rule-inspection). + ```yaml Type: Boolean Parameter Sets: (All) @@ -1847,14 +1747,13 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsPasswordProtected -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentIsPasswordProtected parameter specifies an exception that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection only works for Office documents and .zip files. Valid values are: +The ExceptIfAttachmentIsPasswordProtected parameter specifies an exception that looks for password protected files in messages (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z), and .pdf files. Valid values are: - $true: Look for password protected attachments. - - $false: Don't look for password protected attachments. ```yaml @@ -1871,17 +1770,20 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsUnsupported -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentIsUnsupported parameter specifies an exception that looks for unsupported file types in messages. Unsupported file types are message attachments that aren't natively recognized by Exchange, and the required IFilter isn't installed. Valid values are: +The ExceptIfAttachmentIsUnsupported parameter specifies an exception that looks for unsupported file types in messages. Valid values are: - $true: Look for unsupported file types in messages. - - $false: Don't look for unsupported file types in messages. -For more information, see [Register Filter Pack IFilters with Exchange 2013](https://docs.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). +Rules can inspect the content of supported file types only. If the rule finds an attachment file type that isn't supported, the ExceptIfAttachmentIsUnsupported exception is triggered. + +For the list of supported file types, see [Supported file types for mail flow rule content inspection](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/inspect-message-attachments#supported-file-types-for-mail-flow-rule-content-inspection). + +In Exchange 2010, to extend the list of supported file types, see [Register Filter Pack IFilters](https://learn.microsoft.com/exchange/register-filter-pack-ifilters-with-exchange-2013-exchange-2013-help). ```yaml Type: Boolean @@ -1897,13 +1799,13 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentMatchesPatterns parameter specifies an exception 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\>". +You can specify multiple text patterns by using the following syntax: `"Regular expression1","Regular expression2",..."Regular expressionN"`. Only the first 150 KB of the attachment is scanned when trying to match a text pattern. @@ -1921,11 +1823,11 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentNameMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfAttachmentNameMatchesPatterns parameter specifies an exception that looks for text patterns in the file 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 ExceptIfAttachmentNameMatchesPatterns parameter specifies an exception that looks for text patterns in the file 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"`. ```yaml Type: Pattern[] @@ -1941,14 +1843,13 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentProcessingLimitExceeded -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentProcessingLimitExceeded parameter specifies an exception that looks for messages where attachment scanning didn't complete. Valid values are: - $true: Look for messages where attachment scanning didn't complete. - - $false: Don't look for messages where attachment scanning didn't complete. You use this exception to create rules that work together with other attachment processing rules to handle messages where the content can't be fully scanned. @@ -1967,38 +1868,25 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentPropertyContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfAttachmentPropertyContainsWords parameter specifies an exception that looks for words in the properties of attached Office documents. This condition helps integrate rules with the File Classification Infrastructure (FCI) in Windows Server 2018 R2 or later, SharePoint, or a third-party classification system. Valid values are a built-in document property, or a custom property. The built-in document properties are: - Business Impact - - Compliancy - - Confidentiality - - Department - - Impact - - Intellectual Property - - Personally Identifiable Information - - Personal Information - - Personal Use - - Required Clearance - - PHI - - PII - - Project - - Protected Health Information The syntax for this parameter is "PropertyName:Word". To specify multiple properties, or multiple words for the same property, use the following syntax: "PropertyName1:Word1,Phrase with spaces,word2,...","PropertyName2:Word3,Phrase with spaces,word4,...". Don't use values with leading or trailing spaces. @@ -2009,7 +1897,7 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2019,7 +1907,7 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentSizeOver -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2028,13 +1916,9 @@ The ExceptIfAttachmentSizeOver parameter specifies an exception that looks for m When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -2053,25 +1937,20 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf1 -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfBetweenMemberOf1 parameter specifies an exception that looks for messages that are sent between group members. You need to use this parameter with the ExceptIfBetweenMemberOf2 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -2087,25 +1966,20 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf2 -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfBetweenMemberOf2 parameter specifies an exception that looks for messages that are sent between group members. You need to use this parameter with the ExceptIfBetweenMemberOf1 parameter. You can use any value that uniquely identifies the group. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -2121,9 +1995,9 @@ Accept wildcard characters: False ``` ### -ExceptIfContentCharacterSetContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfContentCharacterSetContainsWords parameter specifies an exception that looks for character set names in messages. @@ -2143,25 +2017,20 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -2179,7 +2048,7 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2201,14 +2070,16 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfFromAddressMatchesPatterns parameter specifies an exception 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 ExceptIfFromAddressMatchesPatterns parameter specifies an exception 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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). +**Note**: Trying to search for empty From addresses using this parameter doesn't work. + ```yaml Type: Pattern[] Parameter Sets: (All) @@ -2223,25 +2094,20 @@ Accept wildcard characters: False ``` ### -ExceptIfFromMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -2259,14 +2125,13 @@ Accept wildcard characters: False ``` ### -ExceptIfFromScope -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. The ExceptIfFromScope parameter specifies an exception 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. - +- InOrganization: The message was sent or received over an authenticated connection **AND** the sender meets at least one of the following criteria: The sender is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. - NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. ```yaml @@ -2283,15 +2148,15 @@ Accept wildcard characters: False ``` ### -ExceptIfHasClassification -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfHasClassification parameter specifies an exception that looks for messages with the specified message classification. You use the Get-MessageClassification cmdlet to identify the message classification. For example, to find messages with the Company Internal classification, use the following syntax: --ExceptIfHasClassification @(Get-MessageClassification "Company Internal").Identity +`-ExceptIfHasClassification @(Get-MessageClassification "Company Internal").Identity` The message classification referred to in this parameter is the custom message classification that you can create in your organization by using the New-MessageClassification cmdlet. It isn't related to the DLP data classification. @@ -2309,14 +2174,13 @@ Accept wildcard characters: False ``` ### -ExceptIfHasNoClassification -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfHasNoClassification parameter specifies an exception that looks for messages with or without any message classifications. Valid values are: - $true: Look for messages that don't have a message classification. - - $false: Look for messages that have one or more message classifications. ```yaml @@ -2333,14 +2197,15 @@ Accept wildcard characters: False ``` ### -ExceptIfHasSenderOverride -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +**Note:** This parameter is functional only in on-premises Exchange. -In on-premises Exchange, this exception is only available on Mailbox servers. +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. The ExceptIfHasSenderOverride parameter specifies an exception 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. - - $false: Don't look for messages where the sender took action to override a DLP policy. ```yaml @@ -2357,7 +2222,7 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsMessageHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2377,7 +2242,7 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2401,7 +2266,7 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesMessageHeader -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2421,11 +2286,11 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfHeaderMatchesPatterns parameter specifies an exception 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\>". +The ExceptIfHeaderMatchesPatterns parameter specifies an exception 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 specify the header field to search by using the ExceptIfHeaderMatchesMessageHeader parameter. @@ -2443,25 +2308,20 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerAddresses -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfManagerAddresses parameter specifies the users (managers) for the ExceptIfManagerForEvaluatedUser parameter. You can use any value that uniquely identifies the user. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. You specify if you want to look for these users as managers of senders or recipients by using the ExceptIfManagerForEvaluatedUser parameter. @@ -2479,14 +2339,13 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerForEvaluatedUser -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfManagerForEvaluatedUser parameter specifies an exception that looks for users in the Manager attribute of senders or recipients. Valid values are: - Recipient: The user is the manager of a recipient. - - Sender: The user is the manager of the sender. You specify the users to look for by using the ExceptIfManagerAddresses parameter. @@ -2504,40 +2363,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ExceptIfMessageContainsAllDataClassifications -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Hashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ExceptIfMessageContainsDataClassifications -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +**Note:** This parameter is functional only in on-premises Exchange. -In on-premises Exchange, this exception is only available on Mailbox servers. +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. The ExceptIfMessageContainsDataClassifications parameter specifies an exception that looks for sensitive information types in the body of messages, and in any attachments. -This parameter uses the syntax @{\<SensitiveInformationType1\>},@{\<SensitiveInformationType2\>},...@{\<SensitiveInformationTypeN\>}. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. +This parameter uses the syntax `@{SensitiveInformationType1},@{SensitiveInformationType2},...@{SensitiveInformationTypeN}`. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. -For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). +For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). ```yaml Type: Hashtable[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2547,7 +2390,7 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageSizeOver -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. @@ -2556,13 +2399,9 @@ The ExceptIfMessageSizeOver parameter specifies an exception that looks for mess When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -2581,28 +2420,20 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageTypeMatches -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfMessageTypeMatches parameter specifies an exception that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. - -- AutoForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook or Outlook). - -- Encrypted: Encrypted messages. - +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **will not** match during mail flow rule evaluation. +- Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - -- PermissionControlled: Messages that have specific permissions configured. - +- PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). - Voicemail: Voice mail messages forwarded by Unified Messaging service. - - Signed: Digitally signed messages. - -- ApprovalRequest: Moderations request messages sent to moderators. - +- ApprovalRequest: Moderation request messages sent to moderators. - ReadReceipt: Read receipts. ```yaml @@ -2619,66 +2450,40 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfRecipientADAttributeContainsWords parameter specifies an exception that looks for words in the Active Directory attributes of recipients. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -2701,66 +2506,40 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfRecipientADAttributeMatchesPatterns parameter specifies an exception that looks for text patterns in the Active Directory attributes of recipients by using regular expressions. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -2781,9 +2560,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfRecipientAddressContainsWords parameter specifies an exception that looks for words in recipient email addresses. You can specify multiple words separated by commas. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -2801,11 +2580,11 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfRecipientAddressMatchesPatterns parameter specifies an exception 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 ExceptIfRecipientAddressMatchesPatterns parameter specifies an exception 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"`. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -2823,13 +2602,13 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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. -If you want to look for recipient email addresses that contain the specified domain (for example, any subdomain of a domain), use the ExceptIfRecipientAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This exception matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". ```yaml Type: Word[] @@ -2853,7 +2632,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2863,16 +2642,13 @@ Accept wildcard characters: False ``` ### -ExceptIfSCLOver -This parameter is available or 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. -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. - -This condition is available on Mailbox servers and Edge Transport servers. This condition is not available or functional in the cloud-based service due to how the service filtering stack works. +In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. The ExceptIfSCLOver parameter specifies an exception that looks for the SCL value of messages. Valid values are: - -1: The message is from a trusted sender, so the message bypasses spam filtering. - - Integers 0 through 9: A higher value indicates that a message is more likely to be spam. The rule looks for messages with an SCL value that's greater than or equal to the specified value. @@ -2881,7 +2657,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2891,66 +2667,40 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderADAttributeContainsWords parameter specifies an exception that looks for words in Active Directory attributes of message senders. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -2973,66 +2723,40 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderADAttributeMatchesPatterns parameter specifies an exception 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 - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -3053,13 +2777,13 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderDomainIs -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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. -If you want to look for sender email addresses that contain the specified domain (for example, any subdomain of a domain), use the FromAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This exception matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -3085,7 +2809,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3095,19 +2819,19 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderIpRanges -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderIpRanges parameter specifies an exception 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. - - IP address range: For example, 192.168.0.1-192.168.0.254. - - Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. -You can specify multiple IP addresses or ranges separated by commas. +You can specify multiple values separated by commas. + +In Exchange Online, the IP address that's used during evaluation of this exception is the address of the last hop before reaching the service. This IP address is not guaranteed to be the original sender's IP address, especially if third-party software is used during message transport. ```yaml Type: MultiValuedProperty @@ -3123,14 +2847,13 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderManagementRelationship -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSenderManagementRelationship parameter specifies an exception that looks for the relationship between the sender and recipients in messages. Valid values are: - Manager: The sender is the manager of a recipient. - - DirectReport: A recipient is the manager of the sender. ```yaml @@ -3147,25 +2870,20 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -3181,19 +2899,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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: - Name - - Distinguished name (DN) - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. @@ -3211,19 +2926,16 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToScope -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfSentToScope parameter specifies an exception that looks for the location of a recipient. Valid values are: -- InOrganization: The recipient is a mailbox, mail user, group, or mail-enabled public folder in your organization or the recipient'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. - -- NotInOrganization: The recipients are outside your organization. The recipient's email address isn't in an accepted domain or the recipient's email address is in an accepted domain that's configured as an external relay domain. - -- ExternalPartner: The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. This value is only available in on-premises Exchange. - -- ExternalNonPartner: The recipients are external to your organization, and the organization isn't a partner organization. This value is only available in on-premises Exchange. +- InOrganization: The message was sent or received over an authenticated connection **AND** the recipient meets at least one of the following criteria: The recipient is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the recipient's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. +- NotInOrganization: The recipients are outside the organization. The recipient's email address isn't in an accepted domain or is in an accepted domain that's configured as an external relay domain in the organization. +- ExternalPartner: This value is available only in on-premises Exchange. The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. +- ExternalNonPartner: This value is available only in on-premises Exchange. The recipients are external to your organization, and the organization isn't a partner organization. ```yaml Type: ToUserScope @@ -3239,13 +2951,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. The ExceptIfSubjectContainsWords parameter specifies an exception that looks for words in the Subject field 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -3261,11 +2975,11 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfSubjectMatchesPatterns parameter specifies an exception 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 ExceptIfSubjectMatchesPatterns parameter specifies an exception 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"`. ```yaml Type: Pattern[] @@ -3281,13 +2995,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyContainsWords -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -3303,11 +3019,11 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyMatchesPatterns -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception 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\>". +The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception 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"`. ```yaml Type: Pattern[] @@ -3323,16 +3039,14 @@ Accept wildcard characters: False ``` ### -ExceptIfWithImportance -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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 only available on Mailbox servers. +In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfWithImportance parameter specifies an exception that looks for messages with the specified importance level. Valid values are: - Low - - Normal - - High ```yaml @@ -3349,11 +3063,11 @@ Accept wildcard characters: False ``` ### -ExpiryDate -This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition doesn't include the ExceptIf prefix. +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. -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". +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". ```yaml Type: DateTime @@ -3371,23 +3085,18 @@ Accept wildcard characters: False ### -From 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -3431,10 +3140,12 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The FromAddressMatchesPatterns parameter specifies a condition 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 FromAddressMatchesPatterns parameter specifies a condition 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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). +**Note**: Trying to search for empty From addresses using this parameter doesn't work. + ```yaml Type: Pattern[] Parameter Sets: (All) @@ -3451,23 +3162,18 @@ Accept wildcard characters: False ### -FromMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -3491,8 +3197,7 @@ In on-premises Exchange, this condition is available on Mailbox servers and Edge The FromScope parameter specifies a condition 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. - +- InOrganization: The message was sent or received over an authenticated connection **AND** the sender meets at least one of the following criteria: The sender is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. - NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain. ```yaml @@ -3511,23 +3216,18 @@ Accept wildcard characters: False ### -GenerateIncidentReport This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The GenerateIncidentReport parameter specifies where to send the incident report that's defined by the IncidentReportContent parameter. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -An incident report is generated for messages that violate a DLP policy in your organization. +**Note**: An incident report isn't generated for notifications or other incident reports that are generated by DLP or mail flow rules. ```yaml Type: RecipientIdParameter @@ -3545,29 +3245,26 @@ Accept wildcard characters: False ### -GenerateNotification This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. -The GenerateNotification parameter specifies an action that sends a notification message to recipients. For example, you can use this parameter to notify recipients that a message was rejected by the rule, or marked as spam and delivered to their Junk Email folder. +The GenerateNotification parameter specifies an action that sends a notification message to recipients that match the conditions of the rule. For example, you can use this parameter to notify recipients that a message was rejected by the rule, or marked as spam and delivered to their Junk Email folder. Each matched recipient receives a separate notification. This parameter supports plain text, HTML tags and the following keywords that use values from the original message: - %%From%% - - %%To%% - - %%Cc%% - - %%Subject%% - - %%Headers%% - - %%MessageDate%% +The maximum number of characters is 5120. + ```yaml Type: DisclaimerText Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3579,13 +3276,13 @@ Accept wildcard characters: False ### -HasClassification 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The HasClassification parameter specifies a condition that looks for messages with the specified message classification. You use the Get-MessageClassification cmdlet to identify the message classification. For example, to find messages with the Company Internal classification, use the following syntax: --HasClassification @(Get-MessageClassification "Company Internal").Identity +`-HasClassification @(Get-MessageClassification "Company Internal").Identity` The message classification referred to in this parameter is the custom message classification that you can create in your organization by using the New-MessageClassification cmdlet. It isn't related to the DLP classification. @@ -3605,12 +3302,11 @@ Accept wildcard characters: False ### -HasNoClassification 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The HasNoClassification parameter specifies a condition that looks for messages with or without any message classifications. Valid values are: - $true: Look for messages that don't have a message classification. - - $false: Look for messages that have one or more message classifications. ```yaml @@ -3627,14 +3323,15 @@ Accept wildcard characters: False ``` ### -HasSenderOverride +**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. -In on-premises Exchange, this condition is only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The HasSenderOverride parameter specifies a condition 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. - - $false: Don't look for messages where the sender took action to override a DLP policy. ```yaml @@ -3719,7 +3416,7 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The HeaderMatchesPatterns parameter specifies a condition 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\>". +The HeaderMatchesPatterns parameter specifies a condition 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 specify the header field to search by using the HeaderMatchesMessageHeader parameter. @@ -3739,32 +3436,19 @@ Accept wildcard characters: False ### -IncidentReportContent This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. -The IncidentReportContent parameter specifies the message properties that are included in the incident report that's generated when a message violates a DLP policy. Valid values are: +The IncidentReportContent parameter specifies the message properties that are included in the incident report. Valid values are: - Sender: The sender of the message. - - Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. - - Subject: The Subject field of the message. - - CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. - - BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. - - Severity: The audit severity of the rule that was triggered. If the message was processed by more than one rule, the highest severity is displayed. - -- Override: The override if the sender chose to override a PolicyTip. If the sender provided a justification, the first 100 characters of the justification is also included. - - RuleDetections: The list of rules that the message triggered. - - FalsePositive: The false positive if the sender marked the message as a false positive for a PolicyTip. - -- DataClassifications: The list of sensitive information types that were detected in the message. - - IdMatch: The sensitive information type that was detected, the exact matched content from the message, and the 150 characters before and after the matched sensitive information. - - AttachOriginalMail: The entire original message as an attachment. The message ID is always included in the incident report. @@ -3787,18 +3471,17 @@ Accept wildcard characters: False ``` ### -IncidentReportOriginalMail -This parameter is available or functional only in 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. This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. This parameter is used together with the GenerateIncidentReport parameter. Valid values are: - IncludeOriginalMail - - DoNotIncludeOriginalMail (this is the default value) ```yaml @@ -3815,29 +3498,25 @@ Accept wildcard characters: False ``` ### -LogEventText -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The LogEventText parameter specifies an action that creates an entry in the Application log on the local Edge Transport server. The value for this parameter specifies the text that you want to include in the event log entry. If the text contains spaces, enclose the value in quotation marks ("). The entry contains the following information: - Level: Information - - Source: MSExchange Messaging Policies - - Event ID: 4000 - - Task Category: Rules - -- EventData: The following message is logged by an action in the rules: \<text you specify\> +- EventData: `The following message is logged by an action in the rules: <text you specify>` ```yaml Type: EventLogText Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3849,23 +3528,18 @@ Accept wildcard characters: False ### -ManagerAddresses 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ManagerAddresses parameter specifies the users (managers) for the ExceptIfManagerForEvaluatedUser parameter. You can use any value that uniquely identifies the user. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. You specify if you want to look for these users as managers of senders or recipients by using the ManagerForEvaluatedUser parameter. @@ -3885,12 +3559,11 @@ Accept wildcard characters: False ### -ManagerForEvaluatedUser 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The ManagerForEvaluatedUser parameter specifies a condition that looks for users in the Manager attribute of senders or recipients. Valid values are: - Recipient: The user is the manager of a recipient. - - Sender: The user is the manager of the sender. You specify the users to look for by using the ManagerAddresses parameter. @@ -3908,34 +3581,18 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MessageContainsAllDataClassifications -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Hashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -MessageContainsDataClassifications +**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. -In on-premises Exchange, this condition is only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The MessageContainsDataClassifications parameter specifies a condition that looks for sensitive information types in the body of messages, and in any attachments. -This parameter uses the syntax @{\<SensitiveInformationType1\>},@{\<SensitiveInformationType2\>},...@{\<SensitiveInformationTypeN\>}. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. +This parameter uses the syntax `@{SensitiveInformationType1},@{SensitiveInformationType2},...@{SensitiveInformationTypeN}`. For example, to look for content that contains at least two credit card numbers, and at least one ABA routing number, use the value @{Name="Credit Card Number"; minCount="2"},@{Name="ABA Routing Number"; minCount="1"}. -For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). +For a list of sensitive information types available, see [Sensitive information types in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types). You can specify the notification options by using the NotifySender parameter. @@ -3943,7 +3600,7 @@ 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, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3962,13 +3619,9 @@ The MessageSizeOver parameter specifies a condition that looks for messages larg When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -3989,26 +3642,18 @@ Accept wildcard characters: False ### -MessageTypeMatches 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The MessageTypeMatches parameter specifies a condition that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. - -- AutoForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook or Outlook). - -- Encrypted: Encrypted messages. - +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **will not** match during mail flow rule evaluation. +- Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - -- PermissionControlled: Messages that have specific permissions configured. - +- PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). - Voicemail: Voice mail messages forwarded by Unified Messaging service. - - Signed: Digitally signed messages. - -- ApprovalRequest: Moderations request messages sent to moderators. - +- ApprovalRequest: Moderation request messages sent to moderators. - ReadReceipt: Read receipts. ```yaml @@ -4027,10 +3672,8 @@ Accept wildcard characters: False ### -Mode 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 any action is taken on the message that would impact delivery. - -- AuditAndNotify: The rule operates the same as in Audit mode, but notifications are also enabled. - +- 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. +- AuditAndNotify: 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 and GenerateNotification actions occur. - Enforce: All actions specified in the rule are taken. This is the default value. ```yaml @@ -4049,12 +3692,11 @@ Accept wildcard characters: False ### -ModerateMessageByManager This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ModerateMessageByManager parameter specifies an action that forwards messages for approval to the user that's specified in the sender's Manager attribute. After the manager approves the message, it's delivered to the recipients. Valid values are: - $true: Moderation by the sender's manager is enabled. - - $false: Moderation by the sender's manager is disabled. This action only works if the sender's Manager attribute is defined. @@ -4075,23 +3717,18 @@ Accept wildcard characters: False ### -ModerateMessageByUser This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The ModerateMessageByUser parameter specifies an action that forwards messages for approval to the specified users. After one of the users approves the message, it's delivered to the recipients. You can use ay value that uniquely identifies the user. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. You can't use a distribution group as a moderator. @@ -4125,31 +3762,31 @@ Accept wildcard characters: False ``` ### -NotifySender +**Note:** This parameter is functional only in on-premises Exchange. + This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The NotifySender parameter specifies an action that notifies the sender when messages violate DLP policies. Valid values are: - NotifyOnly: The sender is notified, but the message is delivered normally. - - RejectMessage: The message is rejected, and the sender is notified. - - RejectUnlessFalsePositiveOverride: The message is rejected unless it's marked as a false positive by the sender. - - RejectUnlessSilentOverride: The message is rejected unless the sender has chosen to override the policy restriction. - - RejectUnlessExplicitOverride: This is the same as RejectUnlessSilentOverride, but the sender can also provide a justification for overriding the policy restriction. For all values except NotifyOnly, you can specify an enhanced status code and a rejection reason by using the RejectMessageEnhancedStatusCode and RejectMessageReasonText parameters. The default enhanced status code is 5.7.1, and the default rejection reason is Delivery not authorized, message refused. If you use this parameter, you also need to specify a condition that looks for sensitive information types in messages by using the MessageContainsDataClassifications parameter. +This action is applicable to messages sent by internal users only. External senders will not receive notifications. + ```yaml Type: NotifySenderType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -4163,7 +3800,7 @@ 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. -The PrependSubject parameter specifies an action that adds text to add to the beginning of the Subject field of messages. The value for this parameter is the text that you want to add. If the text contains spaces, enclose the value in quotation marks (")\> +The PrependSubject parameter specifies an action that adds text to add to the beginning of the Subject field of messages. The value for this parameter is the text that you want to add. 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. @@ -4186,9 +3823,7 @@ The Priority parameter specifies a priority value for the rule that determines t Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: - Valid priority values for the existing 8 rules are from 0 through 7. - - Valid priority values for a new rule (the 9th rule) are from 0 through 8. - - The default value for a new rule (the 9th rule) is 8. If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. @@ -4209,19 +3844,20 @@ Accept wildcard characters: False ### -Quarantine This parameter specifies an action or part of an action for the rule. -This action is available only on Edge Transport servers in on-premises Exchange. +In on-premises Exchange, this action is available only on Edge Transport servers. The Quarantine parameter specifies an action that quarantines messages. - In on-premises Exchange, messages are delivered to the quarantine mailbox that you've configured as part of Content filtering. If the quarantine mailbox isn't configured, the message is returned to the sender in an NDR. +- In Microsoft 365, messages are delivered to the hosted quarantine. -- In Office 365, messages are delivered to the hosted quarantine. +If this action is in a rule that's not the last rule in the list, rule evaluation stops after this rule is run. When the message is released from quarantine, the remaining rules in the list aren't evaluated. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4233,64 +3869,38 @@ Accept wildcard characters: False ### -RecipientADAttributeContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The RecipientADAttributeContainsWords parameter specifies a condition that looks for words in the Active Directory attributes of recipients. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -4315,64 +3925,38 @@ Accept wildcard characters: False ### -RecipientADAttributeMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The RecipientADAttributeMatchesPatterns parameter specifies a condition that looks for text patterns in the Active Directory attributes of recipients by using regular expressions. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -4395,7 +3979,7 @@ Accept wildcard characters: False ### -RecipientAddressContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The RecipientAddressContainsWords parameter specifies a condition that looks for words in recipient email addresses. You can specify multiple words separated by commas. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -4415,9 +3999,9 @@ Accept wildcard characters: False ### -RecipientAddressMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The RecipientAddressMatchesPatterns parameter specifies a condition 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 RecipientAddressMatchesPatterns parameter specifies a condition 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"`. This parameter works when the recipient is an individual user. This parameter doesn't work with distribution groups. @@ -4434,14 +4018,35 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RecipientAddressType +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: + +- Original: The rule checks the original address in the To field of the message. +- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This is the default value. + +```yaml +Type: RecipientAddressType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RecipientDomainIs 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. -The RecipientDomainIs parameter specifies a condition that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. +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. -If you want to look for recipient email addresses that contain the specified domain (for example, any subdomain of a domain), use the RecipientAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This condition matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". ```yaml Type: Word[] @@ -4465,7 +4070,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4482,18 +4087,13 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The RedirectMessageTo parameter specifies a rule action that redirects messages to the specified recipients. You can use any value that uniquely identifies the recipient. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -4511,7 +4111,7 @@ Accept wildcard characters: False ### -RejectMessageEnhancedStatusCode This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The RejectMessageEnhancedStatusCode parameter specifies the enhanced status code that's used when the rule rejects messages. Valid values are 5.7.1 or between 5.7.900 and 5.7.999. @@ -4537,10 +4137,14 @@ Accept wildcard characters: False ### -RejectMessageReasonText This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The RejectMessageReasonText parameter specifies the explanation text that's used when the rule rejects messages. If the value contains spaces, enclose the value in quotation marks ("). +In Exchange 2013 or later, the maximum number of characters is 256. + +In the cloud-based service, the maximum number of characters is 1024. + You can use this parameter with the NotifySender parameter for a custom non-delivery report (also known as an NDR or bounce message). If you use this parameter with the RejectMessageEnhancedStatusCode parameter, the custom explanation text value is set to "Delivery not authorized, message refused". @@ -4588,7 +4192,6 @@ This parameter specifies an action or part of an action for the rule. The RemoveOME parameter specifies an action that removes the previous version of Office 365 Message Encryption from messages and their attachments. Valid values are: - $true: The message and attachments are decrypted. - - $false: The message and attachments aren't decrypted. ```yaml @@ -4612,7 +4215,6 @@ This parameter specifies an action or part of an action for the rule. The RemoveOMEv2 parameter specifies an action that removes Office 365 Message Encryption from messages and their attachments. Valid values are: - $true: The message and attachments are decrypted. - - $false: The message and attachments aren't decrypted. ```yaml @@ -4628,17 +4230,40 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RemoveRMSAttachmentEncryption +This parameter is available only in the cloud-based service. + +This parameter specifies an action or part of an action for the rule. + +The RemoveRMSAttachmentEncryption parameter specifies an action that removes Microsoft Purview Message Encryption from encrypted attachments in email. The attachments were already encrypted before they were attached to the message. The message itself doesn't need to be encrypted. Valid values are: + +- $true: The encrypted attachments are decrypted. +- $false: The encrypted attachments aren't decrypted. + + This parameter also requires the value $true for the RemoveOMEv2 parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RouteMessageOutboundConnector This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. -The RouteMessageOutboundConnector parameter specifies an action that routes messages through the specified Outbound connector in Office 365. You can use any value that uniquely identifies the connector. For example: +The RouteMessageOutboundConnector parameter specifies an action that routes messages through the specified Outbound connector in Microsoft 365. You can use any value that uniquely identifies the connector. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -4657,12 +4282,11 @@ Accept wildcard characters: False ### -RouteMessageOutboundRequireTls This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The RouteMessageOutboundRequireTls parameter specifies an action that uses Transport Layer Security (TLS) encryption to deliver messages outside your organization. Valid values are: - $true: The messages must be delivered over a TLS encrypted channel. - - $false: A TLS encrypted channel isn't required to deliver the messages. ```yaml @@ -4682,7 +4306,6 @@ Accept wildcard characters: False 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. - - Defer: The message is deferred so the rules engine can attempt to process the message again. ```yaml @@ -4701,9 +4324,8 @@ Accept wildcard characters: False ### -RuleSubType The RuleSubType parameter specifies the rule type. Valid values are: -- Dlp: The rule is associated with a DLP policy. - -- None: The rule is a regular rule that isn't associated with a DLP policy. +- Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange. +- None: The rule is a regular transport rule. This is the default value. ```yaml Type: RuleSubType @@ -4719,16 +4341,13 @@ Accept wildcard characters: False ``` ### -SCLOver -This parameter is available or 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. -This condition is available on Mailbox servers and Edge Transport servers. This condition is not available or functional in the cloud-based service due to how the service filtering stack works. +In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. The SCLOver parameter specifies a condition that looks for the SCL value of messages. Valid values are: - -1: The message is from a trusted sender, so the message bypasses spam filtering. - - Integers 0 through 9: A higher value indicates that a message is more likely to be spam. The rule looks for messages with an SCL value that's greater than or equal to the specified value. @@ -4737,7 +4356,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4749,64 +4368,38 @@ Accept wildcard characters: False ### -SenderADAttributeContainsWords 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderADAttributeContainsWords parameter specifies a condition that looks for words in Active Directory attributes of message senders. You can use any of the following Active Directory attributes: - City - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Word". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Word1,Phrase with spaces,word2...","AttributeName2:Word3,Phrase with spaces,word4...". Don't use words with leading or trailing spaces. @@ -4831,64 +4424,38 @@ Accept wildcard characters: False ### -SenderADAttributeMatchesPatterns 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderADAttributeMatchesPatterns parameter specifies a condition 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 - - Company - - Country - - CustomAttribute1 to CustomAttribute15 - - Department - - DisplayName - - Email - - FaxNumber - - FirstName - - HomePhoneNumber - - Initials - - LastName - - Manager - - MobileNumber - - Notes - - Office - - OtherFaxNumber - - OtherHomePhoneNumber - - OtherPhoneNumber - - PagerNumber - - PhoneNumber - - POBox - - State - - Street - - Title - - UserLogonName - - ZipCode This parameter uses the syntax: "AttributeName:Regular Expression". To specify multiple attributes, or multiple words for the same attribute, use the following syntax: "AttributeName1:Regular Expression1,Regular Expression2...","AttributeName2:Regular Expression3,Regular Expression4...". @@ -4911,22 +4478,16 @@ Accept wildcard characters: False ### -SenderAddressLocation 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, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). - +- 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). - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - - HeaderOrEnvelope: Examine senders in the message header and the message envelope. -Note that message envelope searching is only available for the following conditions and exceptions: +Message envelope searching is available only for the following conditions and exceptions: - From and ExceptIfFrom - - FromAddressContainsWords and ExceptIfFromAddressContainsWords - - FromAddressMatchesPatterns and ExceptIfFromAddressMatchesPatterns - - FromMemberOf and ExceptIfFromMemberOf - - SenderDomainIs and ExceptIfSenderDomainIs ```yaml @@ -4945,11 +4506,11 @@ Accept wildcard characters: False ### -SenderDomainIs 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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. -If you want to look for sender email addresses that contain the specified domain (for example, any subdomain of a domain), use the FromAddressMatchesPatterns parameter, and specify the domain by using the syntax '@domain\\.com$'. +This condition matches domains and subdomains. For example, "contoso.com" matches both "contoso.com" and "subdomain.contoso.com". You can use SenderAddressLocation parameter to specify where to look for the sender's email address (message header, message envelope, or both). @@ -4975,7 +4536,7 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4987,17 +4548,17 @@ Accept wildcard characters: False ### -SenderIpRanges 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderIpRanges parameter specifies a condition 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. - - IP address range: For example, 192.168.0.1-192.168.0.254. - - Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. -You can specify multiple IP addresses or ranges separated by commas. +You can specify multiple values separated by commas. + +In Exchange Online, the IP address that's used during evaluation of this condition is the address of the last hop before reaching the service. This IP address is not guaranteed to be the original sender's IP address, especially if third-party software is used during message transport. ```yaml Type: MultiValuedProperty @@ -5015,12 +4576,11 @@ Accept wildcard characters: False ### -SenderManagementRelationship 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SenderManagementRelationship parameter specifies a condition that looks for the relationship between the sender and recipients in messages. Valid values are: - Manager: The sender is the manager of a recipient. - - DirectReport: A recipient is the manager of the sender. ```yaml @@ -5039,23 +4599,18 @@ Accept wildcard characters: False ### -SentTo 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: RecipientIdParameter[] @@ -5073,23 +4628,18 @@ Accept wildcard characters: False ### -SentToMemberOf 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. @@ -5109,17 +4659,14 @@ Accept wildcard characters: False ### -SentToScope 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The SentToScope parameter specifies a condition that looks for the location of recipients. Valid values are: -- InOrganization: The recipient is a mailbox, mail user, group, or mail-enabled public folder in your organization or the recipient'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. - -- NotInOrganization: The recipients are outside your organization. The recipient's email address isn't in an accepted domain or the recipient's email address is in an accepted domain that's configured as an external relay domain. - -- ExternalPartner: The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. This value is only available in on-premises Exchange. - -- ExternalNonPartner: The recipients are external to your organization, and the organization isn't a partner organization. This value is only available in on-premises Exchange. +- InOrganization: The message was sent or received over an authenticated connection **AND** the recipient meets at least one of the following criteria: The recipient is a mailbox, mail user, group, or mail-enabled public folder in the organization, **OR** the recipient's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain in the organization. +- NotInOrganization: The recipients are outside the organization. The recipient's email address isn't in an accepted domain or is in an accepted domain that's configured as an external relay domain in the organization. +- ExternalPartner: This value is available only in on-premises Exchange. The recipients are in a partner organization where you've configured Domain Security (mutual TLS authentication) to send mail. +- ExternalNonPartner: This value is available only in on-premises Exchange. The recipients are external to your organization, and the organization isn't a partner organization. ```yaml Type: ToUserScope @@ -5137,16 +4684,13 @@ Accept wildcard characters: False ### -SetAuditSeverity This parameter specifies an action or part of an action for the rule. -In on-premises Exchange, this action is only available on Mailbox servers. +In on-premises Exchange, this action is available only on Mailbox servers. The SetAuditSeverity parameter specifies an action that sets the severity level of the incident report and the corresponding entry that's written to the message tracking log when messages violate DLP policies. Valid values are: - DoNotAudit: No audit entry is logged. - - Low: The audit entry is assigned low severity. - - Medium: The audit entry is assigned medium severity. - - High: The audit entry is assigned high severity. ```yaml @@ -5210,7 +4754,6 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The SetSCL parameter specifies an action that adds or modifies the SCL value of messages. Valid values are: - -1: The message is from a trusted sender, so the message bypasses spam filtering. - - Integers 0 through 9: A higher value indicates that a message is more likely to be spam. ```yaml @@ -5227,9 +4770,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectStatusCode -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The SmtpRejectMessageRejectStatusCode parameter specifies an action that disconnects the sending server from the Edge Transport server. The value of this parameter is the SMTP code that's used. Valid values are the integers 400 through 500. @@ -5239,7 +4782,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5249,9 +4792,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectText -This parameter specifies an action or part of an action for the rule. +This parameter is functional only on Edge Transport servers in on-premises Exchange. -This action is available only on Edge Transport servers in on-premises Exchange. +This parameter specifies an action or part of an action for the rule. The SmtpRejectMessageRejectText parameter specifies an action that disconnects the sending server from the Edge Transport server. The value of this parameter is the explanation text that's used. If the value contains spaces, enclose the value in quotation marks ("). @@ -5261,7 +4804,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5278,7 +4821,6 @@ In on-premises Exchange, this action is available on Mailbox servers and Edge Tr The StopRuleProcessing parameter specifies an action that stops processing more rules. Valid values are: - $true: Stop processing more rules. - - $false: Continue processing more rules after this one. ```yaml @@ -5301,7 +4843,9 @@ In on-premises Exchange, this condition is available on Mailbox servers and Edge The SubjectContainsWords parameter specifies a condition that looks for words in the Subject field 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -5321,7 +4865,7 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The SubjectMatchesPatterns parameter specifies a condition 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 SubjectMatchesPatterns parameter specifies a condition 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"`. ```yaml Type: Pattern[] @@ -5343,7 +4887,9 @@ In on-premises Exchange, this condition is available on Mailbox servers and Edge The SubjectOrBodyContainsWords parameter specifies a condition 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. +To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. + +The maximum length of this parameter is 128 characters. ```yaml Type: Word[] @@ -5363,7 +4909,7 @@ This parameter specifies a condition or part of a condition for the rule. The na In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. -The SubjectOrBodyMatchesPatterns parameter specifies a condition 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\>". +The SubjectOrBodyMatchesPatterns parameter specifies a condition 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"`. ```yaml Type: Pattern[] @@ -5397,14 +4943,12 @@ Accept wildcard characters: False ### -WithImportance 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 only available on Mailbox servers. +In on-premises Exchange, this condition is available only on Mailbox servers. The WithImportance parameter specifies a condition that looks for messages with the specified importance level. Valid values are: - Low - - Normal - - High ```yaml @@ -5425,12 +4969,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-TransportServer.md b/exchange/exchange-ps/exchange/Set-TransportServer.md similarity index 90% rename from exchange/exchange-ps/exchange/mail-flow/Set-TransportServer.md rename to exchange/exchange-ps/exchange/Set-TransportServer.md index fdd3c59fbe..f9958ab658 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-TransportServer.md +++ b/exchange/exchange-ps/exchange/Set-TransportServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-transportserver +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-TransportServer @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the Set-TransportServer cmdlet to modify settings that are associated with the Hub Transport server role or the Edge Transport server role. -Note: In Exchange 2013 or later, use the Set-TransportService cmdlet instead. If you have scripts that use Set-TransportServer, update them to use Set-TransportService. +**Note**: In Exchange 2013 or later, use the Set-TransportService cmdlet instead. If you have scripts that use Set-TransportServer, update them to use Set-TransportService. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -43,7 +42,6 @@ Set-TransportServer [-Identity] <ServerIdParameter> [-ConnectivityLogPath <LocalLongFullPath>] [-ContentConversionTracingEnabled <Boolean>] [-DelayNotificationTimeout <EnhancedTimeSpan>] - [-DeltaSyncClientCertificateThumbprint <String>] [-DnsLogEnabled <Boolean>] [-DnsLogMaxAge <EnhancedTimeSpan>] [-DnsLogMaxDirectorySize <Unlimited>] @@ -55,13 +53,6 @@ Set-TransportServer [-Identity] <ServerIdParameter> [-ExternalDNSProtocolOption <ProtocolOption>] [-ExternalDNSServers <MultiValuedProperty>] [-ExternalIPAddress <IPAddress>] - [-HttpProtocolLogEnabled <Boolean>] - [-HttpProtocolLogFilePath <LocalLongFullPath>] - [-HttpProtocolLogLoggingLevel <ProtocolLoggingLevel>] - [-HttpProtocolLogMaxAge <EnhancedTimeSpan>] - [-HttpProtocolLogMaxDirectorySize <ByteQuantifiedSize>] - [-HttpProtocolLogMaxFileSize <ByteQuantifiedSize>] - [-HttpTransportSyncProxyServer <String>] [-InternalDNSAdapterEnabled <Boolean>] [-InternalDNSAdapterGuid <Guid>] [-InternalDNSProtocolOption <ProtocolOption>] @@ -73,11 +64,9 @@ Set-TransportServer [-Identity] <ServerIdParameter> [-IrmLogMaxDirectorySize <Unlimited>] [-IrmLogMaxFileSize <ByteQuantifiedSize>] [-IrmLogPath <LocalLongFullPath>] - [-MaxActiveTransportSyncJobsPerProcessor <Int32>] [-MaxConcurrentMailboxDeliveries <Int32>] [-MaxConcurrentMailboxSubmissions <Int32>] [-MaxConnectionRatePerMinute <Int32>] - [-MaxNumberOfTransportSyncAttempts <Int32>] [-MaxOutboundConnections <Unlimited>] [-MaxPerDomainOutboundConnections <Unlimited>] [-MessageExpirationTimeout <EnhancedTimeSpan>] @@ -133,7 +122,7 @@ Set-TransportServer [-Identity] <ServerIdParameter> ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -164,11 +153,8 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs 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 - - GUID - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -210,13 +196,9 @@ The ActiveUserStatisticsLogMaxDirectorySize parameter specifies the cap on the s When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -242,13 +224,9 @@ The ActiveUserStatisticsLogMaxFileSize parameter specifies the maximum file size When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -269,7 +247,12 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogPath -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. +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. +- Exchange 2013 or later: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ActiveUsersStats. + +Setting the value of this parameter to $null disables server statistics logging. ```yaml Type: LocalLongFullPath @@ -326,13 +309,9 @@ The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent l When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -358,13 +337,9 @@ The AgentLogMaxFileSize parameter specifies the maximum size of each agent log f When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -421,8 +396,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -480,13 +454,9 @@ The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -512,13 +482,9 @@ The ConnectivityLogMaxFileSize parameter specifies the maximum size of each conn When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -539,7 +505,12 @@ Accept wildcard characters: False ``` ### -ConnectivityLogPath -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. +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 +- Exchange 2013 or later: 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 @@ -555,12 +526,10 @@ Accept wildcard characters: False ``` ### -ContentConversionTracingEnabled -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: +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 - - Network Service: Full Control - - System: Full Control ```yaml @@ -638,13 +607,9 @@ The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -670,13 +635,9 @@ The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -783,9 +744,9 @@ Accept wildcard characters: False ### -ExternalDNSServers 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the value of the ExternalDNSAdapterEnabled parameter is set to $true, the ExternalDNSServers parameter and its list of DNS servers isn't used. @@ -873,9 +834,9 @@ Accept wildcard characters: False ### -InternalDNSServers 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. 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. @@ -930,7 +891,6 @@ Accept wildcard characters: False The IrmLogEnabled parameter enables logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include: - $true: Enable IRM logging - - $false: Disable IRM logging ```yaml @@ -972,13 +932,9 @@ This IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1004,13 +960,9 @@ This IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1111,7 +1063,7 @@ Accept wildcard characters: False ``` ### -MaxPerDomainOutboundConnections -The MaxPerDomainOutboundConnections parameter specifies the maximum number of concurrent connections to any single domain. The default value is 20. 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. +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 @@ -1147,7 +1099,7 @@ Accept wildcard characters: False ``` ### -MessageRetryInterval -The MessageRetryInterval parameter specifies the retry interval for individual messages after a connection failure with a remote server. The default value is 15 minutes. +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. @@ -1214,13 +1166,9 @@ The default value is 1000 MB. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1246,11 +1194,8 @@ The MessageTrackingLogMaxFileSize parameter specifies the maximum size of the me When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1328,11 +1273,8 @@ The PickupDirectoryMaxHeaderSize parameter specifies the maximum message header When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1369,7 +1311,7 @@ Accept wildcard characters: False ``` ### -PickupDirectoryMaxRecipientsPerMessage -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. +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 @@ -1417,12 +1359,19 @@ Accept wildcard characters: False ``` ### -PipelineTracingPath -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 computer. 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. Pipeline 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: +The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location depends on your version of Exchange: -- Administrators: Full Control +- Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\PipelineTracing. +- Exchange 2013 or later: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\PipelineTracing. -- Network Service: Full Control +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. + +Pipeline 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 +- Network Service: Full Control - System: Full Control ```yaml @@ -1439,7 +1388,7 @@ Accept wildcard characters: False ``` ### -PipelineTracingSenderAddress -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. +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 @@ -1532,13 +1481,9 @@ The QueueLogMaxDirectorySize parameter specifies the maximum size of the queue l When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1564,13 +1509,9 @@ The QueueLogMaxFileSize parameter specifies the maximum size of the queue log fi When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1632,13 +1573,9 @@ The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of t When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1664,13 +1601,9 @@ The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of the Re When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1691,7 +1624,12 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogPath -The ReceiveProtocolLogPath parameter specifies the path of the protocol log directory for all the Receive connectors that exist on the server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpReceive. Setting the value of this parameter to $null disables protocol logging for all Receive connectors on the server. However, setting this parameter to $null when the value of the ProtocolLoggingLevel attribute for any Receive connector on the server is Verbose generates event log errors. The preferred method of disabling protocol logging is to use the Set-ReceiveConnector cmdlet to set the ProtocolLoggingLevel to None on each Receive connector. +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. +- Exchange 2013 or later: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpReceive. + +Setting the value of this parameter to $null disables protocol logging for all Receive connectors on the server. However, setting this parameter to $null when the value of the ProtocolLoggingLevel attribute for any Receive connector on the server is Verbose generates event log errors. The preferred method of disabling protocol logging is to use the Set-ReceiveConnector cmdlet to set the ProtocolLoggingLevel to None on each Receive connector. ```yaml Type: LocalLongFullPath @@ -1780,13 +1718,9 @@ The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1807,7 +1741,12 @@ Accept wildcard characters: False ``` ### -RoutingTableLogPath -The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Routing. Setting the value of the RoutingTableLogPath parameter to $null disables routing table logging. +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. +- Exchange 2013 or later: 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 @@ -1848,13 +1787,9 @@ The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1880,13 +1815,9 @@ The SendProtocolLogMaxFileSize parameter specifies the maximum size of the Send When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1907,7 +1838,12 @@ Accept wildcard characters: False ``` ### -SendProtocolLogPath -The SendProtocolLogPath parameter specifies the location of protocol log storage for the Send connectors. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpSend. Setting the value of this parameter to $null disables protocol logging for all Send connectors on the server. However, setting this parameter to $null when the value of the ProtocolLoggingLevel or IntraOrgConnectorProtocolLoggingLevel attribute for any Send connector on the server is Verbose generates event log errors. The preferred method of disabling protocol logging is to use the Set-SendConnector cmdlet to set the ProtocolLoggingLevel parameter to None on each Send connector and to set the IntraOrgConnectorProtocolLoggingLevel parameter to None. +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. +- Exchange 2013 or later: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpSend. + +Setting the value of this parameter to $null disables protocol logging for all Send connectors on the server. However, setting this parameter to $null when the value of the ProtocolLoggingLevel or IntraOrgConnectorProtocolLoggingLevel attribute for any Send connector on the server is Verbose generates event log errors. The preferred method of disabling protocol logging is to use the Set-SendConnector cmdlet to set the ProtocolLoggingLevel parameter to None on each Send connector and to set the IntraOrgConnectorProtocolLoggingLevel parameter to None. ```yaml Type: LocalLongFullPath @@ -1923,7 +1859,7 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxAge -This parameter has been deprecated and is no longer used. +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. @@ -1945,7 +1881,19 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxDirectorySize -This parameter has been deprecated and is no longer used. +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are treated as bytes. + +The value of the ServerStatisticsLogMaxFileSize parameter must be less than or equal to the value of the ServerStatisticsLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the server statistics log directory. ```yaml Type: ByteQuantifiedSize @@ -1961,7 +1909,19 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxFileSize -This parameter has been deprecated and is no longer used. +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) +- TB (terabytes) + +Unqualified values are treated as bytes. + +The value of the ServerStatisticsLogMaxFileSize parameter must be less than or equal to the value of the ServerStatisticsLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the server statistics log files. ```yaml Type: ByteQuantifiedSize @@ -1977,7 +1937,14 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogPath -This parameter has been deprecated and is no longer used. +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: + +- Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\ServerStats. +- Exchange 2013 or later: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ServerStats. + +Setting the value of this parameter to $null disables server statistics logging. ```yaml Type: LocalLongFullPath @@ -2133,12 +2100,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-TransportService.md b/exchange/exchange-ps/exchange/Set-TransportService.md similarity index 97% rename from exchange/exchange-ps/exchange/mail-flow/Set-TransportService.md rename to exchange/exchange-ps/exchange/Set-TransportService.md index f820450ab8..c6c5a3fe45 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-TransportService.md +++ b/exchange/exchange-ps/exchange/Set-TransportService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-transportservice +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-TransportService @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-TransportService cmdlet to modify the settings of the Transport service on Exchange 2013 or later Mailbox servers or Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -165,7 +164,7 @@ Set-TransportService [-Identity] <ServerIdParameter> ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -196,11 +195,8 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs 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 - - GUID - - Distinguished name (DN) - - ExchangeLegacyDN You can't use this parameter on an Edge Transport server. @@ -244,13 +240,9 @@ The ActiveUserStatisticsLogMaxDirectorySize parameter specifies the cap on the s When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -276,13 +268,9 @@ The ActiveUserStatisticsLogMaxFileSize parameter specifies the maximum file size When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -360,13 +348,9 @@ The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent l When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -392,13 +376,9 @@ The AgentLogMaxFileSize parameter specifies the maximum size of each agent log f When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -455,8 +435,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -514,13 +493,9 @@ The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -546,13 +521,9 @@ The ConnectivityLogMaxFileSize parameter specifies the maximum size of each conn When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -592,9 +563,7 @@ Accept wildcard characters: False 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 - - Network Service: Full Control - - System: Full Control ```yaml @@ -672,13 +641,9 @@ The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -704,13 +669,9 @@ The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -817,9 +778,9 @@ Accept wildcard characters: False ### -ExternalDNSServers 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. If the value of the ExternalDNSAdapterEnabled parameter is set to $true, the ExternalDNSServers parameter and its list of DNS servers isn't used. @@ -905,9 +866,9 @@ Accept wildcard characters: False ### -InternalDNSServers 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. 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. @@ -928,13 +889,11 @@ Accept wildcard characters: False 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. - - The Mailbox Transport Submission service. Valid values are: - None: Protocol logging is disabled for the intra-organization Send connector in the Transport service and in the Mailbox Transport Submission service. This is the default value. - - Verbose: Protocol logging is enabled for the intra-organization Send connector in the Transport service and in the Mailbox Transport Submission service. The location of the log files is controlled by the SendProtocolLogPath parameter. ```yaml @@ -972,7 +931,6 @@ Accept wildcard characters: False The IrmLogEnabled parameter enables logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include: - $true: Enable IRM logging - - $false: Disable IRM logging ```yaml @@ -1014,13 +972,9 @@ This IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1046,13 +1000,9 @@ This IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1153,7 +1103,7 @@ Accept wildcard characters: False ``` ### -MaxPerDomainOutboundConnections -The MaxPerDomainOutboundConnections parameter specifies the maximum number of concurrent connections to any single domain. The default value is 20. 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. +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 @@ -1189,7 +1139,7 @@ Accept wildcard characters: False ``` ### -MessageRetryInterval -The MessageRetryInterval parameter specifies the retry interval for individual messages after a connection failure with a remote server. The default value is 15 minutes. +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. @@ -1256,13 +1206,9 @@ The default value is 1000 MB. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1288,11 +1234,8 @@ The MessageTrackingLogMaxFileSize parameter specifies the maximum size of the me When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1370,11 +1313,8 @@ The PickupDirectoryMaxHeaderSize parameter specifies the maximum message header When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1459,12 +1399,14 @@ Accept wildcard characters: False ``` ### -PipelineTracingPath -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 computer. 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. Pipeline 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: +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. -- Administrators: Full Control +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. -- Network Service: Full Control +Pipeline 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 +- Network Service: Full Control - System: Full Control ```yaml @@ -1554,13 +1496,9 @@ The QueueLogMaxDirectorySize parameter specifies the maximum size of the queue l When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1586,13 +1524,9 @@ The QueueLogMaxFileSize parameter specifies the maximum size of the queue log fi When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1678,13 +1612,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1714,13 +1644,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -1994,13 +1920,9 @@ The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -2021,7 +1943,7 @@ Accept wildcard characters: False ``` ### -RoutingTableLogPath -The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Routing. Setting the value of the RoutingTableLogPath parameter to $null disables routing table logging. +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 @@ -2066,13 +1988,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -2102,13 +2020,9 @@ A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the v When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -2136,7 +2050,6 @@ The SendProtocolLogPath parameter specifies the location of the protocol log dir 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: - The IntraOrgConnectorProtocolLoggingLevel parameter. - - The ProtocolLoggingLevel parameter on the Set-SendConnector cmdlet for each Send connector in the Transport service. ```yaml @@ -2153,9 +2066,7 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxAge -This parameter is available or functional only in Exchange Server 2013. - -Server statistics aren't available in Exchange 2013 Cumulative Update 7 (CU7) or later, so this parameter has no effect in those versions of Exchange 2013. +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. @@ -2167,7 +2078,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2177,22 +2088,16 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxDirectorySize -This parameter is available or functional only in Exchange Server 2013. - -Server statistics aren't available in Exchange 2013 CU7 or later, so this parameter has no effect in those versions of Exchange 2013. +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. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are treated as bytes. @@ -2203,7 +2108,7 @@ The value of the ServerStatisticsLogMaxFileSize parameter must be less than or e Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2213,22 +2118,16 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxFileSize -This parameter is available or functional only in Exchange Server 2013. - -Server statistics aren't available in Exchange 2013 CU7 or later, so this parameter has no effect in those versions of Exchange 2013. +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. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are treated as bytes. @@ -2239,7 +2138,7 @@ The value of the ServerStatisticsLogMaxFileSize parameter must be less than or e Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2249,9 +2148,7 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogPath -This parameter is available or functional only in Exchange Server 2013. - -Server statistics aren't available in Exchange 2013 CU7 or later, so this parameter has no effect in those versions of Exchange 2013. +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. @@ -2259,7 +2156,7 @@ The ServerStatisticsLogPath parameter specifies the location of server statistic Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2953,12 +2850,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Set-UMAutoAttendant.md similarity index 88% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMAutoAttendant.md rename to exchange/exchange-ps/exchange/Set-UMAutoAttendant.md index 17b38271fe..c224bb9dc4 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMAutoAttendant.md +++ b/exchange/exchange-ps/exchange/Set-UMAutoAttendant.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-umautoattendant -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-UMAutoAttendant ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Set-UMAutoAttendant cmdlet to modify an existing Unified Messaging (UM) auto attendant. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -66,7 +65,8 @@ Set-UMAutoAttendant [-Identity] <UMAutoAttendantIdParameter> [-Timezone <String>] [-TimeZoneName <UMTimeZone>] [-WeekStartDay <DayOfWeek>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -74,7 +74,7 @@ The Set-UMAutoAttendant cmdlet changes or modifies the settings of an existing U After this task is completed, the parameters and values specified are configured on the UM auto attendant. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,10 +87,10 @@ This example configures the UM auto attendant MySpeechEnabledAA to fall back to ### Example 2 ```powershell -Set-UMAutoAttendant -Identity MyUMAutoAttendant -BusinessHoursSchedule 0.10:45-0.13:15,1.09:00-1.17:00,6.09:00-6.16:30 -HolidaySchedule "New Year,newyrgrt.wav,1/2/2013","Building Closed for Construction,construction.wav,4/24/2013,4/28/2013" +Set-UMAutoAttendant -Identity MyUMAutoAttendant -BusinessHoursSchedule 0.10:45-0.13:15,1.09:00-1.17:00,6.09:00-6.16:30 -HolidaySchedule "New Year,newyrgrt.wav,1/2/2014","Building Closed for Construction,construction.wav,4/24/2014,4/28/2014" ``` -This example configures the UM auto attendant MyUMAutoAttendant that has business hours configured to be 10:45 to 13:15 (Sunday), 09:00 to 17:00 (Monday), and 09:00 to 16:30 (Saturday) and holiday times and their associated greetings configured to be "New Year" on January 2, 2013, and "Building Closed for Construction" from April 24, 2013 through April 28, 2013. +This example configures the UM auto attendant MyUMAutoAttendant that has business hours configured to be 10:45 to 13:15 (Sunday), 09:00 to 17:00 (Monday), and 09:00 to 16:30 (Saturday) and holiday times and their associated greetings configured to be "New Year" on January 2, 2014, and "Building Closed for Construction" from April 24, 2014 through April 28, 2014. ### Example 3 ```powershell @@ -108,7 +108,7 @@ The Identity parameter specifies the identifier for the UM auto attendant being Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -130,7 +130,7 @@ The default value is disabled. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -150,7 +150,7 @@ 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, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -166,7 +166,7 @@ The AfterHoursMainMenuCustomPromptEnabled parameter specifies whether the after Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -182,7 +182,7 @@ The AfterHoursMainMenuCustomPromptFilename parameter specifies the .wav file to Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -198,7 +198,7 @@ The AfterHoursTransferToOperatorEnabled parameter specifies whether to allow cal Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -214,7 +214,7 @@ The AfterHoursWelcomeGreetingEnabled parameter specifies whether the after hours Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -230,7 +230,7 @@ The AfterHoursWelcomeGreetingFilename parameter specifies the .wav file to be us Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -246,7 +246,7 @@ The AllowDialPlanSubscribers parameter specifies whether to allow the dial plan Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -262,7 +262,7 @@ The AllowedInCountryOrRegionGroups parameter specifies the list of in-country/re Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -278,7 +278,7 @@ The AllowedInternationalGroups parameter specifies the list of international dia Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -294,7 +294,7 @@ The AllowExtensions parameter specifies whether callers can make calls to extens Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -316,7 +316,7 @@ The default is disabled. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -332,7 +332,7 @@ The BusinessHoursKeyMappingEnabled parameter specifies whether the custom menus Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -348,7 +348,7 @@ The BusinessHoursMainMenuCustomPromptEnabled parameter specifies whether the bus Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -364,7 +364,7 @@ The BusinessHoursMainMenuCustomPromptFilename parameter specifies the .wav file Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -376,14 +376,12 @@ Accept wildcard characters: False ### -BusinessHoursSchedule 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\>". +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"`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -395,18 +393,15 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (From Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" - - "Monday.4:30 AM-Monday.5:30 AM","Wednesday.4:30 AM-Wednesday.5:30 AM" (Run on Monday and Wednesday mornings from 4:30 until 5:30.) ```yaml Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -422,7 +417,7 @@ The BusinessHoursTransferToOperatorEnabled parameter specifies whether to allow Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -438,7 +433,7 @@ The BusinessHoursWelcomeGreetingEnabled parameter specifies whether the custom b Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -454,7 +449,7 @@ The BusinessHoursWelcomeGreetingFilename parameter specifies the .wav file to be Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -470,7 +465,7 @@ The BusinessLocation parameter specifies what the Mailbox server should read to Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -486,7 +481,7 @@ The BusinessName parameter specifies the name of the company or organization bei Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -502,7 +497,7 @@ The CallSomeoneEnabled parameter specifies whether the Call Someone feature is e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -514,15 +509,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -538,7 +532,7 @@ The ContactAddressList parameter specifies the identity of the address list. If Type: AddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -554,7 +548,7 @@ The ContactRecipientContainer parameter specifies the name or identity of the co Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -570,7 +564,7 @@ The ContactScope parameter specifies the scope of the directory search given to Type: DialScopeEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -580,15 +574,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -604,7 +596,7 @@ The DTMFFallbackAutoAttendant parameter specifies the dual tone multi-frequency Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -614,13 +606,13 @@ Accept wildcard characters: False ``` ### -ForceUpgrade -The ForceUpgrade switch specifies whether you're prompted for confirmation before a UM auto attendant object is upgraded. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -633,20 +625,18 @@ Accept wildcard characters: False 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 - - File name for the audio prompt, which is in the .wav format - - Day (date) of the holiday The following is an example: -"Christmas, Christmas.wav, 12/25/2013". +"Christmas, Christmas.wav, 12/25/2014". ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -662,7 +652,7 @@ The InfoAnnouncementEnabled parameter specifies whether to enable the informatio Type: InfoAnnouncementEnabledEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -678,7 +668,7 @@ The InfoAnnouncementFilename parameter specifies the .wav file to be used for th Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -694,7 +684,7 @@ The Language parameter specifies the language used by the UM auto attendant. Thi Type: UMLanguage Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -707,22 +697,17 @@ Accept wildcard characters: False 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 - - Title - - Location - - None - - Prompt for alias - - Inherited from UM dial plan ```yaml Type: AutoAttendantDisambiguationFieldEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -738,7 +723,7 @@ The Name parameter specifies the display name to be used for the UM auto attenda Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -754,7 +739,7 @@ The NameLookupEnabled parameter specifies whether to allow callers to perform di Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -770,7 +755,7 @@ The OperatorExtension parameter specifies the extension number of the operator. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -786,7 +771,7 @@ The PilotIdentifierList parameter specifies a list of one or more pilot numbers. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -802,7 +787,7 @@ The SendVoiceMsgEnabled parameter specifies whether to allow the Send Message fe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -818,7 +803,7 @@ The SpeechEnabled parameter specifies whether the auto attendant is speech-enabl Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -834,7 +819,7 @@ The Timezone parameter specifies the time zone used with the auto attendant. The Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -850,7 +835,7 @@ The Timezone parameter specifies the time zone used with the auto attendant. The Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -866,7 +851,7 @@ The TimeZoneName parameter specifies all or part of a MicrosoftWindows time zone Type: UMTimeZone Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -882,7 +867,7 @@ The WeekStartDay parameter specifies the starting day of the week. The valid val Type: DayOfWeek Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -898,7 +883,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -912,12 +897,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Set-UMCallAnsweringRule.md similarity index 82% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMCallAnsweringRule.md rename to exchange/exchange-ps/exchange/Set-UMCallAnsweringRule.md index 56a7cde4d7..f5a3f24afa 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/exchange/Set-UMCallAnsweringRule.md @@ -1,56 +1,60 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-umcallansweringrule -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-UMCallAnsweringRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Set-UMCallAnsweringRule cmdlet to change properties of an existing UM call answering rule. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-UMCallAnsweringRule [-Identity] <UMCallAnsweringRuleIdParameter> [-CallerIds <MultiValuedProperty>] - [-CallersCanInterruptGreeting <Boolean>] [-CheckAutomaticReplies <Boolean>] [-Confirm] - [-DomainController <Fqdn>] [-ExtensionsDialed <MultiValuedProperty>] [-KeyMappings <MultiValuedProperty>] - [-Mailbox <MailboxIdParameter>] [-Name <String>] [-Priority <Int32>] [-ScheduleStatus <Int32>] - [-TimeOfDay <TimeOfDay>] [-WhatIf] [<CommonParameters>] +Set-UMCallAnsweringRule [-Identity] <UMCallAnsweringRuleIdParameter> + [-CallerIds <MultiValuedProperty>] + [-CallersCanInterruptGreeting <Boolean>] + [-CheckAutomaticReplies <Boolean>] + [-Confirm] + [-DomainController <Fqdn>] + [-ExtensionsDialed <MultiValuedProperty>] + [-KeyMappings <MultiValuedProperty>] + [-Mailbox <MailboxIdParameter>] + [-Name <String>] + [-Priority <Int32>] + [-ScheduleStatus <Int32>] + [-TimeOfDay <TimeOfDay>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Set-UMCallAnsweringRule cmdlet changes the properties of an existing UM call answering rule stored in a UM enabled user's mailbox. You can use the Set-UMCallAnsweringRule cmdlet to specify the following conditions: - Who the incoming call is from - - Time of day - - Calendar free/busy status - - Whether automatic replies are turned on for email You can also specify the following actions: - Find me - - Transfer the caller to someone else - - Leave a voice message After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,9 +73,7 @@ Set-UMCallAnsweringRule -Name MyCallAnsweringRule -CallerIds "1,4255550100,,","1 This example performs the following actions on the call answering rule MyCallAnsweringRule in the mailbox for tonysmith: - Sets the call answering rule to two caller IDs. - - Sets the priority of the call answering rule to 2. - - Sets the call answering rule to allow callers to interrupt the greeting. ### Example 3 @@ -89,13 +91,11 @@ Set-UMCallAnsweringRule -Name MyCallAnsweringRule -Priority 2 -Mailbox tonysmith This example performs the following actions on the call answering rule MyCallAnsweringRule in the mailbox tonysmith: - Sets the priority of the call answering rule to 2. - - Creates key mappings for the call answering rule. If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can: - Press the 1 key and be transferred to a receptionist at extension 45678. - - Press the 2 key and the Find Me feature will be used for urgent issues and ring extension 23456 first and then 45671. ### Example 5 @@ -106,7 +106,6 @@ Set-UMCallAnsweringRule -Name MyCallAnsweringRule -Priority 2 -Mailbox tonysmith This example performs the following actions on the call answering rule MyCallAnsweringRule in the mailbox for tonysmith: - Sets the priority of the call answering rule to 2. - - If the caller reaches voice mail during working hours, the caller is asked to call back later. ### Example 6 @@ -117,7 +116,6 @@ Set-UMCallAnsweringRule -Name MyCallAnsweringRule -Priority 2 -Mailbox tonysmith This example sets a custom period for the time of day on the call answering rule MyCallAnsweringRule in the mailbox for tonysmith and performs the following actions: - Sets the priority of the call answering rule to 2. - - If the caller reaches voice mail and the time is between 8:00 A.M. and 12:00 P.M. on Tuesday, ask the caller to call back later. ## PARAMETERS @@ -129,7 +127,7 @@ The Identity parameter specifies the identifier for a call answering rule being Type: UMCallAnsweringRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -145,7 +143,7 @@ The CallerIds parameter specifies an entry for the "If the Caller is" condition. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -161,7 +159,7 @@ The CallersCanInterruptGreeting parameter specifies whether a caller can interru Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -177,7 +175,7 @@ The CheckAutomaticReplies parameter specifies an entry for the "If My Automatic Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -189,15 +187,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -207,15 +204,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -231,7 +226,7 @@ The ExtensionsDialed parameter specifies an entry for the "If the Caller Dials" Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -247,7 +242,7 @@ The KeyMappings parameter specifies a key mapping entry for a call answering rul Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -260,23 +255,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the mailbox of the user who is running the command is used. @@ -285,7 +271,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -301,7 +287,7 @@ The Name parameter specifies the name of the UM call answering rule or Call Answ Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -317,7 +303,7 @@ The Priority parameter specified the order that the call answering rule will be Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -330,13 +316,9 @@ Accept wildcard characters: False 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 - - Free = 0x1 - - Tentative = 0x2 - - Busy = 0x4 - - OutOfOffice = 0x8 The default setting is $null. @@ -345,7 +327,7 @@ The default setting is $null. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -361,7 +343,7 @@ The TimeOfDay parameter specifies an entry for the "If the Call Arrives During" Type: TimeOfDay Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -377,7 +359,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -391,12 +373,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UMCallRouterSettings.md b/exchange/exchange-ps/exchange/Set-UMCallRouterSettings.md similarity index 83% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMCallRouterSettings.md rename to exchange/exchange-ps/exchange/Set-UMCallRouterSettings.md index f8431f1f76..e2d42d19d4 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMCallRouterSettings.md +++ b/exchange/exchange-ps/exchange/Set-UMCallRouterSettings.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-umcallroutersettings -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-UMCallRouterSettings @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-UMCallRouterSettings cmdlet to modify the configuration of the Microsoft Exchange Unified Messaging Call Router service. This service exists on Exchange servers that have the Client Access server role installed, and is used by telephony clients to connect to Exchange. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -32,11 +31,12 @@ Set-UMCallRouterSettings [[-Server] <ServerIdParameter>] [-SipTcpListeningPort <Int32>] [-SipTlsListeningPort <Int32>] [-UMStartupMode <UMStartupMode>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,11 +48,8 @@ Set-UMCallRouterSettings -DialPlans MySIPDialPlan -IPAddressFamily Any -Server M This example creates the following configuration on the Exchange server named MyUMCallRouter: - Adds the server to the UM SIP dial plan MySIPDialPlan. - - Enables the Microsoft Exchange Unified Messaging Call Router service to accept both IPv4 and IPv6 data packets. - - Sets the maximum number of incoming voice, fax, auto attendant and Outlook Voice Access calls to 150. - - Enables the Microsoft Exchange Unified Messaging Call Router service to start up using TLS mode. ### Example 2 @@ -68,11 +65,8 @@ This example removes the Exchange server named UMCallRouter001 from all UM SIP d 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -81,7 +75,7 @@ If you don't use this parameter, the command is run on the local server. Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: 1 @@ -90,19 +84,17 @@ Accept pipeline input: True Accept wildcard characters: False ``` - ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -114,15 +106,15 @@ Accept wildcard characters: False ### -DialPlans 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -138,7 +130,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -154,7 +146,7 @@ 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, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -170,7 +162,7 @@ The IPAddressFamilyConfigurable parameter specifies whether you're able to set t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -186,7 +178,7 @@ This parameter has been deprecated and is no longer used. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -202,7 +194,7 @@ The SipTcpListeningPort parameter specifies the TCP port that's used by the Micr Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -218,7 +210,7 @@ The SipTlsListeningPort parameter specifies the Transport Layer Security (TLS) p Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -234,7 +226,7 @@ The UMStartupMode parameter specifies whether the Microsoft Exchange Unified Mes Type: UMStartupMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -250,7 +242,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -264,12 +256,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UMDialPlan.md b/exchange/exchange-ps/exchange/Set-UMDialPlan.md similarity index 81% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMDialPlan.md rename to exchange/exchange-ps/exchange/Set-UMDialPlan.md index d402351e2f..0255771570 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMDialPlan.md +++ b/exchange/exchange-ps/exchange/Set-UMDialPlan.md @@ -1,52 +1,78 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-umdialplan -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-UMDialPlan ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Set-UMDialPlan cmdlet to set various properties on a Unified Messaging (UM) dial plan. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-UMDialPlan [-Identity] <UMDialPlanIdParameter> [-AccessTelephoneNumbers <MultiValuedProperty>] - [-AllowDialPlanSubscribers <Boolean>] [-AllowedInCountryOrRegionGroups <MultiValuedProperty>] - [-AllowedInternationalGroups <MultiValuedProperty>] [-AllowExtensions <Boolean>] - [-AllowHeuristicADCallingLineIdResolution <Boolean>] [-AudioCodec <AudioCodecEnum>] - [-AutomaticSpeechRecognitionEnabled <Boolean>] [-CallAnsweringRulesEnabled <Boolean>] - [-CallSomeoneEnabled <Boolean>] [-ConfiguredInCountryOrRegionGroups <MultiValuedProperty>] - [-ConfiguredInternationalGroups <MultiValuedProperty>] [-Confirm] - [-ContactAddressList <AddressListIdParameter>] [-ContactRecipientContainer <OrganizationalUnitIdParameter>] +Set-UMDialPlan [-Identity] <UMDialPlanIdParameter> + [-AccessTelephoneNumbers <MultiValuedProperty>] + [-AllowDialPlanSubscribers <Boolean>] + [-AllowedInCountryOrRegionGroups <MultiValuedProperty>] + [-AllowedInternationalGroups <MultiValuedProperty>] + [-AllowExtensions <Boolean>] + [-AllowHeuristicADCallingLineIdResolution <Boolean>] + [-AudioCodec <AudioCodecEnum>] + [-AutomaticSpeechRecognitionEnabled <Boolean>] + [-CallAnsweringRulesEnabled <Boolean>] + [-CallSomeoneEnabled <Boolean>] + [-ConfiguredInCountryOrRegionGroups <MultiValuedProperty>] + [-ConfiguredInternationalGroups <MultiValuedProperty>] + [-Confirm] + [-ContactAddressList <AddressListIdParameter>] + [-ContactRecipientContainer <OrganizationalUnitIdParameter>] [-ContactScope <CallSomeoneScopeEnum>] - [-CountryOrRegionCode <String>] [-DefaultLanguage <UMLanguage>] [-DefaultOutboundCallingLineId <String>] + [-CountryOrRegionCode <String>] + [-DefaultLanguage <UMLanguage>] [-DialByNamePrimary <DialByNamePrimaryEnum>] - [-DialByNameSecondary <DialByNameSecondaryEnum>] [-DomainController <Fqdn>] - [-EquivalentDialPlanPhoneContexts <MultiValuedProperty>] [-Extension <String>] [-FaxEnabled <Boolean>] - [-ForceUpgrade] [-InCountryOrRegionNumberFormat <NumberFormat>] - [-InfoAnnouncementEnabled <InfoAnnouncementEnabledEnum>] [-InfoAnnouncementFilename <String>] - [-InputFailuresBeforeDisconnect <Int32>] [-InternationalAccessCode <String>] - [-InternationalNumberFormat <NumberFormat>] [-LegacyPromptPublishingPoint <String>] + [-DialByNameSecondary <DialByNameSecondaryEnum>] + [-DomainController <Fqdn>] + [-EquivalentDialPlanPhoneContexts <MultiValuedProperty>] + [-Extension <String>] + [-FaxEnabled <Boolean>] + [-ForceUpgrade] + [-InCountryOrRegionNumberFormat <NumberFormat>] + [-InfoAnnouncementEnabled <InfoAnnouncementEnabledEnum>] + [-InfoAnnouncementFilename <String>] + [-InputFailuresBeforeDisconnect <Int32>] + [-InternationalAccessCode <String>] + [-InternationalNumberFormat <NumberFormat>] + [-LegacyPromptPublishingPoint <String>] [-LogonFailuresBeforeDisconnect <Int32>] [-MatchedNameSelectionMethod <DisambiguationFieldEnum>] - [-MaxCallDuration <Int32>] [-MaxRecordingDuration <Int32>] [-Name <String>] [-NationalNumberPrefix <String>] - [-NumberingPlanFormats <MultiValuedProperty>] [-OperatorExtension <String>] [-OutsideLineAccessCode <String>] - [-PilotIdentifierList <MultiValuedProperty>] [-RecordingIdleTimeout <Int32>] - [-SendVoiceMsgEnabled <Boolean>] [-TUIPromptEditingEnabled <Boolean>] - [-UMAutoAttendant <UMAutoAttendantIdParameter>] [-VoIPSecurity <UMVoIPSecurityType>] - [-WelcomeGreetingEnabled <Boolean>] [-WelcomeGreetingFilename <String>] [-WhatIf] [<CommonParameters>] + [-MaxCallDuration <Int32>] + [-MaxRecordingDuration <Int32>] + [-Name <String>] + [-NationalNumberPrefix <String>] + [-NumberingPlanFormats <MultiValuedProperty>] + [-OperatorExtension <String>] + [-OutsideLineAccessCode <String>] + [-PilotIdentifierList <MultiValuedProperty>] + [-RecordingIdleTimeout <Int32>] + [-SendVoiceMsgEnabled <Boolean>] + [-TUIPromptEditingEnabled <Boolean>] + [-UMAutoAttendant <UMAutoAttendantIdParameter>] + [-VoIPSecurity <UMVoIPSecurityType>] + [-WelcomeGreetingEnabled <Boolean>] + [-WelcomeGreetingFilename <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -56,7 +82,7 @@ UM dial plans are important to the operation of Unified Messaging. Modifications After this task is completed, the parameters and values specified are configured on the UM dial plan. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,7 +102,11 @@ This example configures the UM dial plan MyDialPlan to use a welcome greeting. ### Example 3 ```powershell -$csv=import-csv "C:\MyInCountryGroups.csv"; Set-UMDialPlan -Identity MyDialPlan -ConfiguredInCountryOrRegionGroups $csv; Set-UMDialPlan -Identity MyDialPlan -AllowedInCountryOrRegionGroups "local, long distance" +$csv=import-csv "C:\MyInCountryGroups.csv" + +Set-UMDialPlan -Identity MyDialPlan -ConfiguredInCountryOrRegionGroups $csv + +Set-UMDialPlan -Identity MyDialPlan -AllowedInCountryOrRegionGroups "local, long distance" ``` This example configures the UM dial plan MyDialPlan with dialing rules. @@ -90,7 +120,7 @@ The Identity parameter specifies the UM dial plan ID. This parameter is the dire Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -106,7 +136,7 @@ The AccessTelephoneNumbers parameter specifies a single valid voice mail pilot n Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -122,7 +152,7 @@ The AllowDialPlanSubscribers parameter specifies whether to allow subscribers di Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -138,7 +168,7 @@ The AllowedInCountryOrRegionGroups parameter specifies the list of in-country/re Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -154,7 +184,7 @@ The AllowedInternationalGroups parameter specifies the list of international dia Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -170,7 +200,7 @@ The AllowExtensions parameter specifies whether to allow calls to dial plan exte Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -186,7 +216,7 @@ The AllowHeuristicADCallingLineIdResolution parameter specifies whether to allow Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -202,7 +232,7 @@ The AudioCodec parameter specifies the audio codec used for recording. Mp3 is th Type: AudioCodecEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -218,7 +248,7 @@ The AutomaticSpeechRecognitionEnabled parameter specifies whether Automatic Spee Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -234,7 +264,7 @@ The CallAnsweringRulesEnabled parameter specifies whether Call Answering Rules a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -250,7 +280,7 @@ The CallSomeoneEnabled parameter specifies whether the Call Someone feature is e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -263,18 +293,15 @@ Accept wildcard characters: False The ConfiguredInCountryOrRegionGroups parameter specifies the in-country groups that can be used. Each string consists of four parts: - Group name (up to 32 characters) - - AllowedNumberString - - DialNumberString - - TextComment ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -287,18 +314,15 @@ Accept wildcard characters: False The ConfiguredInternationalGroups parameter specifies the international groups that can be used. Each string consists of four parts: - Group name (up to 32 characters) - - AllowedNumberString - - DialNumberString - - TextComment ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -310,15 +334,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -334,7 +357,7 @@ The ContactAddressList parameter specifies the identity of the address list. If Type: AddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -350,7 +373,7 @@ The ContactRecipientContainer parameter specifies the name or identity of the co Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -366,7 +389,7 @@ The ContactScope parameter specifies the scope of the directory search provided Type: CallSomeoneScopeEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -382,7 +405,7 @@ The CountryOrRegionCode parameter specifies the country or region code that prec Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -398,25 +421,7 @@ The DefaultLanguage parameter specifies the default language of the system. This Type: UMLanguage Parameter Sets: (All) 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 -``` - -### -DefaultOutboundCallingLineId -This parameter is available or functional only in Exchange Server 2010. - -The DefaultOutboundCallingLineId parameter specifies the phone number that a Unified Messaging server would use as the calling line ID when placing an outbound call. By default, this is set to $null and only the extension number of the UM-enabled user that places the outbound call is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -432,7 +437,7 @@ The DialByNamePrimary parameter specifies that the Dial by Name lookup key is to Type: DialByNamePrimaryEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -448,7 +453,7 @@ The DialByNameSecondary parameter specifies that the secondary Dial by Name look Type: DialByNameSecondaryEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -458,15 +463,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -482,7 +485,7 @@ The EquivalentDialPlanPhoneContexts parameter specifies the name of an equivalen Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -498,7 +501,7 @@ The Extension parameter specifies the extension number used by the Call Someone Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -514,7 +517,7 @@ The FaxEnabled parameter specifies whether the Mailbox servers associated with t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -524,13 +527,13 @@ Accept wildcard characters: False ``` ### -ForceUpgrade -The ForceUpgrade switch specifies whether you're prompted for confirmation before a UM dial plan object is upgraded. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -546,7 +549,7 @@ The InCountryOrRegionNumberFormat parameter specifies the prefix string to use a Type: NumberFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -562,7 +565,7 @@ The InfoAnnouncementEnabled parameter specifies whether an informational announc Type: InfoAnnouncementEnabledEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -578,7 +581,7 @@ The InfoAnnouncementFilename parameter specifies the audio file name for an info Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -594,7 +597,7 @@ The InputFailuresBeforeDisconnect parameter specifies the number of sequential u Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -610,7 +613,7 @@ The InternationalAccessCode parameter specifies the code that precedes a telepho Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -626,7 +629,7 @@ The InternationalNumberFormat parameter specifies the prefix string to use and t Type: NumberFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -642,7 +645,7 @@ The LegacyPromptPublishingPoint parameter was used to specify the location of th Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -658,7 +661,7 @@ The LogonFailuresBeforeDisconnect parameter specifies the number of sequential u Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -671,20 +674,16 @@ Accept wildcard characters: False 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 - - Department - - Location - - None - - PromptForAlias ```yaml Type: DisambiguationFieldEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -700,7 +699,7 @@ The MaxCallDuration parameter specifies the maximum length of time that a call c Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -716,7 +715,7 @@ The MaxRecordingDuration parameter specifies the maximum length of time that mes Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -732,7 +731,7 @@ The Name parameter specifies the display name to use for the UM dial plan. This Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -748,7 +747,7 @@ The NationalNumberPrefix parameter specifies the dialing code that precedes a te Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -764,7 +763,7 @@ The NumberingPlanFormats parameter specifies one or more phone number masks that Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -780,7 +779,7 @@ The OperatorExtension parameter specifies the extension number of the operator. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -796,7 +795,7 @@ The OutsideLineAccessCode parameter specifies the code that precedes a telephone Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -812,7 +811,7 @@ The PilotIdentifierList parameter specifies the pilot numbers configured on the Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -828,7 +827,7 @@ The RecordingIdleTimeout parameter specifies the length of time that a caller ca Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -844,7 +843,7 @@ The SendVoiceMsgEnabled parameter specifies whether the Send Message feature is Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -860,7 +859,7 @@ The TUIPromptEditingEnabled parameter specifies whether authorized users are per Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -876,7 +875,7 @@ The UMAutoAttendant parameter specifies the auto attendant run when the caller p Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -886,15 +885,13 @@ Accept wildcard characters: False ``` ### -VoIPSecurity -This parameter is available only in on-premises Exchange. - 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, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -910,7 +907,7 @@ The WelcomeGreetingEnabled parameter specifies whether a custom welcome greeting Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -926,7 +923,7 @@ The WelcomeGreetingFilename parameter specifies the audio file name for the welc Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -942,7 +939,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -956,12 +953,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UMIPGateway.md b/exchange/exchange-ps/exchange/Set-UMIPGateway.md similarity index 86% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMIPGateway.md rename to exchange/exchange-ps/exchange/Set-UMIPGateway.md index 463f278380..af9d1ffda1 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMIPGateway.md +++ b/exchange/exchange-ps/exchange/Set-UMIPGateway.md @@ -1,23 +1,22 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-umipgateway -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-UMIPGateway ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Set-UMIPGateway cmdlet to modify the configuration settings for a single Unified Messaging (UM) IP gateway or to return a list of configuration settings that can be modified on a specified UM IP gateway. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -35,7 +34,8 @@ Set-UMIPGateway [-Identity] <UMIPGatewayIdParameter> [-Port <Int32>] [-Simulator <Boolean>] [-Status <GatewayStatus>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -45,7 +45,7 @@ It's possible that modifications to the UM IP gateway settings may disrupt commu After this task is completed, the parameters and values specified are configured on the UM IP gateway. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -86,7 +86,7 @@ The Identity parameter specifies the identifier for the UM IP gateway being modi Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -102,7 +102,7 @@ The Address parameter specifies the IP address or the fully qualified domain nam Type: UMSmartHost Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -114,15 +114,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -138,7 +137,7 @@ The DelayedSourcePartyInfoEnabled parameter specifies whether Unified Messaging Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -148,15 +147,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -166,15 +163,13 @@ Accept wildcard characters: False ``` ### -ForceUpgrade -This parameter is available only in on-premises Exchange. - -The ForceUpgrade switch specifies whether you're prompted for confirmation before a UM IP gateway object is upgraded. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -187,16 +182,14 @@ Accept wildcard characters: False 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. - - IPv6Only: The UM IP gateway will only use IPv6. - - Any: IPv6 will be used first, and then if necessary, it will fall back to IPv4. ```yaml Type: IPAddressFamily Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -212,7 +205,7 @@ The MessageWaitingIndicatorAllowed parameter specifies whether to enable the UM Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -228,7 +221,7 @@ The Name parameter specifies the display name for the UM IP gateway. This displa Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -244,7 +237,7 @@ The OutcallsAllowed parameter specifies whether to allow this UM IP gateway to b Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -260,7 +253,7 @@ The Port parameter specifies the IP port on which the IP gateway or IP PBX is li Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -276,7 +269,7 @@ The Simulator parameter specifies the simulator used for the UM IP gateway being Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -289,16 +282,14 @@ Accept wildcard characters: False The Status parameter specifies whether to enable or disable the UM IP gateway. Valid values are: - Enabled - - Disabled - - NoNewCalls ```yaml Type: GatewayStatus Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -314,7 +305,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -328,12 +319,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-UMMailbox.md b/exchange/exchange-ps/exchange/Set-UMMailbox.md new file mode 100644 index 0000000000..7e179f4bc5 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-UMMailbox.md @@ -0,0 +1,496 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-UMMailbox + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Set-UMMailbox cmdlet to set the Unified Messaging (UM) properties for a user who is currently UM-enabled. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-UMMailbox [-Identity] <MailboxIdParameter> + [-AllowUMCallsFromNonUsers <AllowUMCallsFromNonUsersFlags>] + [-AnonymousCallersCanLeaveMessages <Boolean>] + [-AutomaticSpeechRecognitionEnabled <Boolean>] + [-CallAnsweringAudioCodec <AudioCodecEnum>] + [-CallAnsweringRulesEnabled <Boolean>] + [-Confirm] + [-DomainController <Fqdn>] + [-FaxEnabled <Boolean>] + [-IgnoreDefaultScope] + [-ImListMigrationCompleted <Boolean>] + [-MissedCallNotificationEnabled <Boolean>] + [-Name <String>] + [-OperatorNumber <String>] + [-PinlessAccessToVoiceMailEnabled <Boolean>] + [-PlayOnPhoneEnabled <Boolean>] + [-SubscriberAccessEnabled <Boolean>] + [-TUIAccessToCalendarEnabled <Boolean>] + [-TUIAccessToEmailEnabled <Boolean>] + [-UMMailboxPolicy <MailboxPolicyIdParameter>] + [-UMSMSNotificationOption <UMSMSNotificationOptions>] + [-VoiceMailAnalysisEnabled <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The Set-UMMailbox cmdlet sets UM properties associated with a user who has been UM-enabled. Many of the UM properties for the user are stored on the user's mailbox, and other UM properties for the user are stored in Active Directory. + +After this task is completed, the parameters and values specified are configured on the UM mailbox. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-UMMailbox -Identity tony@contoso.com -CallAnsweringAudioCodec Wma -CallAnsweringRulesEnabled $false -FaxEnabled $false -UMSMSNotificationOption VoiceMail +``` + +This example configures a UM-enabled user, tony@contoso.com with the following settings: + +Changes the call answering audio codec to Wma + +Disables call answering rules + +Prevents him from receiving incoming faxes + +Enables voice mail notifications but not missed call notifications using text messaging + +### Example 2 +```powershell +Set-UMMailbox -Identity tony@contoso.com -TUIAccessToCalendarEnabled $false -TUIAccessToEmailEnabled $false +``` + +This example prevents the user tony@contoso.com from accessing his calendar and email when he's using Outlook Voice Access. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AllowUMCallsFromNonUsers +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnonymousCallersCanLeaveMessages +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutomaticSpeechRecognitionEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallAnsweringAudioCodec +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallAnsweringRulesEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FaxEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ImListMigrationCompleted +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: + +- $true: The user's Lync or Skype for Business contact list is stored in their Exchange 2016 mailbox. This prevents you from migrating the mailbox back to an Exchange 2010 server. +- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This is the default value. + +Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://learn.microsoft.com/lyncserver/lync-server-2013-configuring-lync-server-to-use-the-unified-contact-store). + +If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list has been moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MissedCallNotificationEnabled +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. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OperatorNumber +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinlessAccessToVoiceMailEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PlayOnPhoneEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubscriberAccessEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TUIAccessToCalendarEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TUIAccessToEmailEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UMMailboxPolicy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UMSMSNotificationOption +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceMailAnalysisEnabled +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/unified-messaging/Set-UMMailboxPIN.md b/exchange/exchange-ps/exchange/Set-UMMailboxPIN.md similarity index 82% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMMailboxPIN.md rename to exchange/exchange-ps/exchange/Set-UMMailboxPIN.md index 00efd80b19..bec81a4cf6 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMMailboxPIN.md +++ b/exchange/exchange-ps/exchange/Set-UMMailboxPIN.md @@ -1,30 +1,37 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-ummailboxpin -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-UMMailboxPIN ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Set-UMMailboxPIN cmdlet to reset the PIN for a Unified Messaging (UM)-enabled mailbox. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-UMMailboxPIN [-Identity] <MailboxIdParameter> [-Confirm] [-DomainController <Fqdn>] [-IgnoreDefaultScope] - [-LockedOut <Boolean>] [-NotifyEmail <String>] [-Pin <String>] [-PINExpired <Boolean>] - [-SendEmail <Boolean>] [-WhatIf] [<CommonParameters>] +Set-UMMailboxPIN [-Identity] <MailboxIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-IgnoreDefaultScope] + [-LockedOut <Boolean>] + [-NotifyEmail <String>] + [-Pin <String>] + [-PINExpired <Boolean>] + [-SendEmail <Boolean>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -32,7 +39,7 @@ The Set-UMMailboxPIN cmdlet is used when a UM-enabled user has been locked out o After this task is completed, the PIN on a UM-enabled mailbox is set. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,30 +77,21 @@ This example unlocks the UM-enabled mailbox for tonysmith@contoso.com and allows The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -105,15 +103,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -123,15 +120,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -141,21 +136,18 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -171,7 +163,7 @@ The LockedOut parameter specifies whether the mailbox will continue to be locked Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -187,7 +179,7 @@ The NotifyEmail parameter specifies the email address to which the server sends Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -203,7 +195,7 @@ The Pin parameter specifies a new PIN for use with the mailbox. The PIN is check Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -219,7 +211,7 @@ The PINExpired parameter specifies whether the PIN is treated as expired. If thi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -235,7 +227,7 @@ The SendEmail parameter specifies whether to send a PIN to the user in an email Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -251,7 +243,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -267,7 +259,7 @@ The PINExpired parameter specifies whether the PIN is treated as expired. If thi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -281,12 +273,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UMMailboxPolicy.md b/exchange/exchange-ps/exchange/Set-UMMailboxPolicy.md similarity index 83% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMMailboxPolicy.md rename to exchange/exchange-ps/exchange/Set-UMMailboxPolicy.md index 72db2182ce..789aabc713 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMMailboxPolicy.md +++ b/exchange/exchange-ps/exchange/Set-UMMailboxPolicy.md @@ -1,48 +1,76 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-ummailboxpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Set-UMMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available only in on-premises Exchange. Use the Set-UMMailboxPolicy cmdlet to modify a Unified Messaging (UM) mailbox policy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-UMMailboxPolicy [-Identity] <MailboxPolicyIdParameter> [-AllowAutomaticSpeechRecognition <Boolean>] - [-AllowCallAnsweringRules <Boolean>] [-AllowCommonPatterns <Boolean>] - [-AllowDialPlanSubscribers <Boolean>] [-AllowedInCountryOrRegionGroups <MultiValuedProperty>] - [-AllowedInternationalGroups <MultiValuedProperty>] [-AllowExtensions <Boolean>] - [-AllowFax <Boolean>] [-AllowMessageWaitingIndicator <Boolean>] - [-AllowMissedCallNotifications <Boolean>] [-AllowPinlessVoiceMailAccess <Boolean>] - [-AllowPlayOnPhone <Boolean>] [-AllowSMSNotification <Boolean>] - [-AllowSubscriberAccess <Boolean>] [-AllowTUIAccessToCalendar <Boolean>] - [-AllowTUIAccessToDirectory <Boolean>] [-AllowTUIAccessToEmail <Boolean>] - [-AllowTUIAccessToPersonalContacts <Boolean>] [-AllowVoiceMailAnalysis <Boolean>] - [-AllowVoiceMailPreview <Boolean>] [-AllowVoiceResponseToOtherMessageTypes <Boolean>] [-Confirm] - [-DomainController <Fqdn>] [-FaxMessageText <String>] [-FaxServerURI <String>] [-ForceUpgrade] - [-InformCallerOfVoiceMailAnalysis <Boolean>] [-LogonFailuresBeforePINReset <Unlimited>] - [-MaxGreetingDuration <Int32>] [-MaxLogonAttempts <Unlimited>] [-MinPINLength <Int32>] [-Name <String>] - [-PINHistoryCount <Int32>] [-PINLifetime <Unlimited>] [-ProtectAuthenticatedVoiceMail <DRMProtectionOptions>] - [-ProtectedVoiceMailText <String>] [-ProtectUnauthenticatedVoiceMail <DRMProtectionOptions>] - [-RequireProtectedPlayOnPhone <Boolean>] [-ResetPINText <String>] - [-SourceForestPolicyNames <MultiValuedProperty>] [-UMDialPlan <UMDialPlanIdParameter>] - [-UMEnabledText <String>] [-VoiceMailPreviewPartnerAddress <SmtpAddress>] - [-VoiceMailPreviewPartnerAssignedID <String>] [-VoiceMailPreviewPartnerMaxDeliveryDelay <Int32>] - [-VoiceMailPreviewPartnerMaxMessageDuration <Int32>] [-VoiceMailText <String>] [-WhatIf] [<CommonParameters>] +Set-UMMailboxPolicy [-Identity] <MailboxPolicyIdParameter> + [-AllowAutomaticSpeechRecognition <Boolean>] + [-AllowCallAnsweringRules <Boolean>] + [-AllowCommonPatterns <Boolean>] + [-AllowDialPlanSubscribers <Boolean>] + [-AllowedInCountryOrRegionGroups <MultiValuedProperty>] + [-AllowedInternationalGroups <MultiValuedProperty>] + [-AllowExtensions <Boolean>] + [-AllowFax <Boolean>] + [-AllowMessageWaitingIndicator <Boolean>] + [-AllowMissedCallNotifications <Boolean>] + [-AllowPinlessVoiceMailAccess <Boolean>] + [-AllowPlayOnPhone <Boolean>] + [-AllowSMSNotification <Boolean>] + [-AllowSubscriberAccess <Boolean>] + [-AllowTUIAccessToCalendar <Boolean>] + [-AllowTUIAccessToDirectory <Boolean>] + [-AllowTUIAccessToEmail <Boolean>] + [-AllowTUIAccessToPersonalContacts <Boolean>] + [-AllowVoiceMailAnalysis <Boolean>] + [-AllowVoiceMailPreview <Boolean>] + [-AllowVoiceResponseToOtherMessageTypes <Boolean>] + [-Confirm] + [-DomainController <Fqdn>] + [-FaxMessageText <String>] + [-FaxServerURI <String>] + [-ForceUpgrade] + [-InformCallerOfVoiceMailAnalysis <Boolean>] + [-LogonFailuresBeforePINReset <Unlimited>] + [-MaxGreetingDuration <Int32>] + [-MaxLogonAttempts <Unlimited>] + [-MinPINLength <Int32>] + [-Name <String>] + [-PINHistoryCount <Int32>] + [-PINLifetime <Unlimited>] + [-ProtectAuthenticatedVoiceMail <DRMProtectionOptions>] + [-ProtectedVoiceMailText <String>] + [-ProtectUnauthenticatedVoiceMail <DRMProtectionOptions>] + [-RequireProtectedPlayOnPhone <Boolean>] + [-ResetPINText <String>] + [-SourceForestPolicyNames <MultiValuedProperty>] + [-UMDialPlan <UMDialPlanIdParameter>] + [-UMEnabledText <String>] + [-VoiceMailPreviewPartnerAddress <SmtpAddress>] + [-VoiceMailPreviewPartnerAssignedID <String>] + [-VoiceMailPreviewPartnerMaxDeliveryDelay <Int32>] + [-VoiceMailPreviewPartnerMaxMessageDuration <Int32>] + [-VoiceMailText <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -50,7 +78,7 @@ When the Set-UMMailboxPolicy cmdlet is used to modify UM mailbox policy objects, After this task is completed, the parameters and values specified are configured on the UM mailbox policy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,7 +112,7 @@ The Identity parameter specifies the identifier for the UM mailbox policy being Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -100,7 +128,7 @@ The AllowAutomaticSpeechRecognition parameter specifies whether users associated Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -116,7 +144,7 @@ The AllowCallAnsweringRules parameter specifies whether users associated with th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -132,7 +160,7 @@ The AllowCommonPatterns parameter specifies whether to allow obvious PINs. Examp Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -148,7 +176,7 @@ The AllowDialPlanSubscribers parameter specifies whether to let subscribers in a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -164,7 +192,7 @@ The AllowedInCountryOrRegionGroups parameter specifies whether to let subscriber Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -180,7 +208,7 @@ The AllowedInternationalGroups parameter specifies whether to let subscribers di Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -196,7 +224,7 @@ The AllowExtensions parameter specifies whether to let subscribers dial calls to Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -212,7 +240,7 @@ The AllowFax parameter specifies whether users associated with the UM mailbox po Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -228,7 +256,7 @@ The AllowMessageWaitingIndicator parameter specifies whether users associated wi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -246,7 +274,7 @@ 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, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -262,7 +290,7 @@ The AllowPinlessVoiceMailAccess parameter specifies whether users associated wit Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -278,7 +306,7 @@ The AllowPlayOnPhone parameter specifies whether users associated with the UM ma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -294,7 +322,7 @@ The AllowSMSNotification parameter specifies whether UM-enabled users associated Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -310,7 +338,7 @@ The AllowSubscriberAccess parameter specifies whether users associated with the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -326,7 +354,7 @@ The AllowTUIAccessToCalendar parameter specifies whether users associated with t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -342,7 +370,7 @@ The AllowTUIAccessToDirectory parameter specifies whether users associated with Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -358,7 +386,7 @@ The AllowTUIAccessToEmail parameter specifies whether users associated with the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -374,7 +402,7 @@ The AllowTUIAccessToPersonalContacts parameter specifies whether users associate Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -390,7 +418,7 @@ The AllowVoiceMailAnalysis parameter specifies whether a copy of each voice mail Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -406,7 +434,7 @@ The AllowVoiceMailPreview parameter specifies whether users associated with the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -422,7 +450,7 @@ The AllowVoiceResponseToOtherMessageTypes parameter specifies whether UM-enabled Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -434,15 +462,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -452,15 +479,13 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available only in on-premises Exchange. - The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -476,7 +501,7 @@ The FaxMessageText parameter specifies the text included in the body part of fax Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -486,13 +511,13 @@ Accept wildcard characters: False ``` ### -FaxServerURI -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 Server 2016 Mailbox 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 Mailbox servers running UM services. +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, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -502,13 +527,13 @@ Accept wildcard characters: False ``` ### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -524,7 +549,7 @@ The InformCallerOfVoiceMailAnalysis parameter specifies whether the callers leav Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -540,7 +565,7 @@ The LogonFailuresBeforePINReset parameter specifies the number of sequential uns Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -556,7 +581,7 @@ The MaxGreetingDuration parameter specifies the maximum greeting length. The ran Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -572,7 +597,7 @@ The MaxLogonAttempts parameter specifies the number of times users can try unsuc Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -588,7 +613,7 @@ The MinPINLength parameter specifies the minimum number of digits required in a Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -604,7 +629,7 @@ The Name parameter specifies the display name for the UM mailbox policy. This se Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -620,7 +645,7 @@ The PINHistoryCount parameter specifies the number of previous PINs that are rem Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -636,7 +661,7 @@ The PINLifetime parameter specifies the number of days until a new password is r Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -652,7 +677,7 @@ The ProtectAuthenticatedVoiceMail parameter specifies whether Mailbox servers th Type: DRMProtectionOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -668,7 +693,7 @@ The ProtectedVoiceMailText parameter specifies the text included in the body par Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -684,7 +709,7 @@ The ProtectUnauthenticatedVoiceMail parameter specifies whether the Mailbox serv Type: DRMProtectionOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -700,7 +725,7 @@ The RequireProtectedPlayOnPhone parameter specifies whether users associated wit Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -716,7 +741,7 @@ The ResetPINText parameter specifies the text to be included in the PIN reset em Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -732,7 +757,7 @@ The SourceForestPolicyNames parameter specifies the name or names of the corresp Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -748,7 +773,7 @@ The UMDialPlan parameter specifies the UM dial plan associated with the UM mailb Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -764,7 +789,7 @@ The UMEnabledText parameter specifies the text to be included when a user is ena Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -780,7 +805,7 @@ The VoiceMailPreviewPartnerAddress parameter specifies the SMTP address of a Voi Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -796,7 +821,7 @@ The VoiceMailPreviewPartnerAssignedID parameter specifies the identification str Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -812,7 +837,7 @@ The VoiceMailPreviewPartnerMaxDeliveryDelay parameter specifies the number of se Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -828,7 +853,7 @@ The VoiceMailPreviewPartnerMaxMessageDuration parameter specifies the maximum du Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -844,7 +869,7 @@ The VoiceMailText parameter specifies the text to be included in the body part o Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -860,7 +885,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -874,12 +899,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UMService.md b/exchange/exchange-ps/exchange/Set-UMService.md similarity index 82% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UMService.md rename to exchange/exchange-ps/exchange/Set-UMService.md index 1458c163ee..51772cc547 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMService.md +++ b/exchange/exchange-ps/exchange/Set-UMService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-umservice -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-UMService @@ -17,22 +16,33 @@ This cmdlet is available only in on-premises Exchange. Use the Set-UMService cmdlet to modify the properties of the Microsoft Exchange Unified Messaging service on Exchange 2013 or Exchange 2016 Mailbox servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-UMService [-Identity] <UMServerIdParameter> [-Confirm] [-DialPlans <MultiValuedProperty>] - [-DomainController <Fqdn>] [-GrammarGenerationSchedule <ScheduleInterval[]>] - [-IPAddressFamily <IPAddressFamily>] [-IPAddressFamilyConfigurable <Boolean>] - [-IrmLogEnabled <Boolean>] [-IrmLogMaxAge <EnhancedTimeSpan>] [-IrmLogMaxDirectorySize <Unlimited>] - [-IrmLogMaxFileSize <ByteQuantifiedSize>] [-IrmLogPath <LocalLongFullPath>] [-MaxCallsAllowed <Int32>] - [-SIPAccessService <ProtocolConnectionSettings>] [-Status <ServerStatus>] - [-UMStartupMode <UMStartupMode>] [-WhatIf] [<CommonParameters>] +Set-UMService [-Identity] <UMServerIdParameter> + [-Confirm] + [-DialPlans <MultiValuedProperty>] + [-DomainController <Fqdn>] + [-GrammarGenerationSchedule <ScheduleInterval[]>] + [-IPAddressFamily <IPAddressFamily>] + [-IPAddressFamilyConfigurable <Boolean>] + [-IrmLogEnabled <Boolean>] + [-IrmLogMaxAge <EnhancedTimeSpan>] + [-IrmLogMaxDirectorySize <Unlimited>] + [-IrmLogMaxFileSize <ByteQuantifiedSize>] + [-IrmLogPath <LocalLongFullPath>] + [-MaxCallsAllowed <Int32>] + [-SIPAccessService <ProtocolConnectionSettings>] + [-Status <ServerStatus>] + [-UMStartupMode <UMStartupMode>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,7 +54,6 @@ Set-UMService -Identity MyUMServer -IPAddressFamily Any -UMStartupMode Dual This example performs the following actions: - Enables the Microsoft Exchange Unified Messaging service on the Mailbox server MyUMServer to accept both IPv4 and IPv6 data packets. - - Enables the Microsoft Exchange Unified Messaging service on the Mailbox server MyUMServer to start up using both TCP and TLS mode. ### Example 2 @@ -62,11 +71,8 @@ Set-UMService -Identity MyUMServer -DialPlans MySIPDialPlan -MaxCallsAllowed 50 This example performs the following actions: - Adds the Mailbox server MyUMServer to the UM dial plan MySIPDialPlan. - - Sets the maximum number of incoming calls to 50. - - Sets northamerica.lyncpoolna.contoso.com:5061 as the FQDN and port for the SIP access service that is used by Microsoft Lync Server or Skype for Business Server for inbound and outbound calling from remote Lync or Skype for Business clients. - - Enables the Microsoft Exchange Unified Messaging service on the Mailbox server MyUMServer to start up in TLS mode. ## PARAMETERS @@ -75,18 +81,15 @@ This example performs the following actions: 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 - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml Type: UMServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -98,15 +101,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -122,15 +124,15 @@ Exchange 2016 and Exchange 2013 servers can't be associated with a TelExt or E.1 You can also use this parameter to associate Exchange 2010 Unified Messaging servers to a UM dial plan. -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". +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"`. -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -146,7 +148,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -158,14 +160,12 @@ Accept wildcard characters: False ### -GrammarGenerationSchedule 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\>". +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"`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -177,18 +177,15 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" - - "Monday.4:30 AM-Monday.5:30 AM","Wednesday.4:30 AM-Wednesday.5:30 AM" (Run on Monday and Wednesday mornings from 4:30 until 5:30.) ```yaml Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -201,16 +198,14 @@ Accept wildcard characters: False The IPAddressFamily parameter specifies whether the UM IP gateway will use IPv4, IPv6, or both to communicate. Valid values are: - IPv4 - - IPv6 - - Any: IPv6 is used first and if necessary, the UM IP gateway falls back to IPv4. This is the default value. ```yaml Type: IPAddressFamily Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -226,7 +221,7 @@ The IPAddressFamilyConfigurable parameter specifies whether you're able to set t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -239,14 +234,13 @@ Accept wildcard characters: False 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 - - $false: Disable IRM logging ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -266,7 +260,7 @@ 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, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -281,13 +275,9 @@ The IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -298,7 +288,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -313,13 +303,9 @@ The IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When you enter a value, qualify the value with one of the following units: - B (bytes) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. @@ -330,7 +316,7 @@ 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 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -348,7 +334,7 @@ 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, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -364,7 +350,7 @@ The MaxCallsAllowed parameter specifies the maximum number of concurrent voice c Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -384,7 +370,7 @@ 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, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -400,7 +386,7 @@ This parameter has been deprecated and is no longer used. Type: ServerStatus Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -413,9 +399,7 @@ Accept wildcard characters: False The UMStartupMode parameter specifies the startup mode for the Unified Messaging service. Valid values are: - TCP (This is the default value) - - TLS - - Dual: The service can listen on ports 5060 and 5061 at the same time. If you add the Exchange server to UM dial plans that have different security settings, you should use this value. If you change the value of this parameter, you need to restart the Unified Messaging service. @@ -424,7 +408,7 @@ 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, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -440,7 +424,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -454,12 +438,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/unified-messaging/Set-UmServer.md b/exchange/exchange-ps/exchange/Set-UmServer.md similarity index 95% rename from exchange/exchange-ps/exchange/unified-messaging/Set-UmServer.md rename to exchange/exchange-ps/exchange/Set-UmServer.md index 90e2be1bc1..6fa2f340bf 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UmServer.md +++ b/exchange/exchange-ps/exchange/Set-UmServer.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-umserver +online version: https://learn.microsoft.com/powershell/module/exchange/set-umserver applicable: Exchange Server 2010 title: Set-UmServer schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Set-UMServer @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Set-UMServer cmdlet to modify settings that are associated with the Unified Messaging (UM) server role. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -39,7 +38,8 @@ Set-UMServer [-Identity] <UMServerIdParameter> [-SipTlsListeningPort <Int32>] [-Status <ServerStatus>] [-UMStartupMode <UMStartupMode>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -47,7 +47,7 @@ The Set-UMServer cmdlet sets specific properties on a Unified Messaging server. After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -85,11 +85,8 @@ This example changes the grammar generation schedule to 02:30-03:00 every day on 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 - - GUID - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -108,8 +105,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -176,14 +172,12 @@ Accept wildcard characters: False ### -GrammarGenerationSchedule 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\>". +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"`. You can use the following values for days: - Full name of the day. - - Abbreviated name of the day. - - Integer from 0 through 6, where 0 = Sunday. You can enter the time in 24 hour format and omit the AM/PM value. If you enter the time in 12 time hour format, include a space between the time and the AM/PM value. @@ -195,11 +189,8 @@ The start time and end time must be at least 15 minutes apart. Minutes are round Here are some examples: - "Sun.11:30 PM-Mon.1:30 AM" - - "6.22:00-6.22:15" (Run from Saturday at 10:00 PM until Saturday at 10:15 PM.) - - "Sun.1:15 AM-Monday.23:00" - - "Monday.4:30 AM-Monday.5:30 AM","Wednesday.4:30 AM-Wednesday.5:30 AM" (Run on Monday and Wednesday mornings from 4:30 until 5:30.) ```yaml @@ -219,7 +210,6 @@ Accept wildcard characters: False 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 - - $false Disable IRM logging ```yaml @@ -255,13 +245,9 @@ Accept wildcard characters: False 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) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are treated as bytes. The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory. @@ -283,13 +269,9 @@ Accept wildcard characters: False 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) - - KB (kilobytes) - - MB (megabytes) - - GB (gigabytes) - - TB (terabytes) Unqualified values are treated as bytes. The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the IRM log files. @@ -444,12 +426,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Set-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/Set-UnifiedAuditLogRetentionPolicy.md new file mode 100644 index 0000000000..b54bb64a99 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-UnifiedAuditLogRetentionPolicy.md @@ -0,0 +1,234 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-UnifiedAuditLogRetentionPolicy + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Set-UnifiedAuditLogRetentionPolicy cmdlet to modify audit log retention policies in the Microsoft Defender portal or the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-UnifiedAuditLogRetentionPolicy [-Identity] <PolicyIdParameter> -Priority <Int32> -RetentionDuration <UnifiedAuditLogRetentionDuration> + [-Confirm] + [-Description <String>] + [-Operations <MultiValuedProperty>] + [-RecordTypes <MultiValuedProperty>] + [-UserIds <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Audit log retention policies are used to specify a retention duration for audit logs for that are generated by admin and user activity. An audit log retention policy can specify the retention duration based on the type of audited activities, the Microsoft 365 service that activities are performed in, or the users who performed the activities. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Defender portal](https://learn.microsoft.com/defender-office-365/mdo-portal-permissions) or [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-UnifiedAuditLogRetentionPolicy -Identity "eDiscovery audit retention" -RecordTypes Discovery,AeD -UserIds admin@contoso.onmicrosoft.com -RetentionDuration SixMonths -Priority 100 +``` + +This example adds the AeD (for eDiscovery Premium events) record type to the policy. It also configures that the policy is applied only to the audit logs for activities performed only by the user admin@contoso.onmicrosoft.com. + +### Example 2 +```powershell +Set-UnifiedAuditLogRetentionPolicy -Name "SearchQueryPerformed by app@sharepoint" -Operations SearchQueryPerformed,FileAccessed -UserIds $null -RetentionDuration SixMonths -Priority 10000 +``` + +This example modifies an audit log retention policy and changes to retention duration to six months, adds an additional activity to the Operations parameter, and removes all values from the UserId property so that the policy will apply to all users. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Priority +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. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies how long audit log records are kept. Valid values are: + +- ThreeMonths +- SixMonths +- NineMonths +- TwelveMonths +- TenYears + +This parameter is required when modifying an audit log retention policy. + +```yaml +Type: UnifiedAuditLogRetentionDuration +Parameter Sets: (All) +Aliases: +Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths, TenYears +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Operations +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordTypes +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIds +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"`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Set-UnifiedGroup.md b/exchange/exchange-ps/exchange/Set-UnifiedGroup.md new file mode 100644 index 0000000000..c592fda80d --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-UnifiedGroup.md @@ -0,0 +1,1256 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-UnifiedGroup + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Set-UnifiedGroup cmdlet to modify Microsoft 365 Groups in your cloud-based organization. To modify members, owners, and subscribers of Microsoft 365 Groups, use the Add-UnifiedGroupLinks and Remove-UnifiedGroupLinks cmdlets. + +**Important**: You can't use this cmdlet to remove all Microsoft Online Email Routing Address (MOERA) addresses from the Microsoft 365 Group. There must be at least one MOERA address attached to a group. To learn more about MOERA addresses, see [How the proxyAddresses attribute is populated in Microsoft Entra ID](https://support.microsoft.com/help/3190357). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-UnifiedGroup [-Identity] <UnifiedGroupIdParameter> + [-AcceptMessagesOnlyFromSendersOrMembers <MultiValuedProperty>] + [-AccessType <ModernGroupTypeInfo>] + [-Alias <String>] + [-AlwaysSubscribeMembersToCalendarEvents] + [-AuditLogAgeLimit <EnhancedTimeSpan>] + [-AutoSubscribeNewMembers] + [-CalendarMemberReadOnly] + [-Classification <String>] + [-Confirm] + [-ConnectorsEnabled] + [-CustomAttribute1 <String>] + [-CustomAttribute10 <String>] + [-CustomAttribute11 <String>] + [-CustomAttribute12 <String>] + [-CustomAttribute13 <String>] + [-CustomAttribute14 <String>] + [-CustomAttribute15 <String>] + [-CustomAttribute2 <String>] + [-CustomAttribute3 <String>] + [-CustomAttribute4 <String>] + [-CustomAttribute5 <String>] + [-CustomAttribute6 <String>] + [-CustomAttribute7 <String>] + [-CustomAttribute8 <String>] + [-CustomAttribute9 <String>] + [-DataEncryptionPolicy <DataEncryptionPolicyIdParameter>] + [-DisplayName <String>] + [-EmailAddresses <ProxyAddressCollection>] + [-ExtensionCustomAttribute1 <MultiValuedProperty>] + [-ExtensionCustomAttribute2 <MultiValuedProperty>] + [-ExtensionCustomAttribute3 <MultiValuedProperty>] + [-ExtensionCustomAttribute4 <MultiValuedProperty>] + [-ExtensionCustomAttribute5 <MultiValuedProperty>] + [-ForceUpgrade] + [-GrantSendOnBehalfTo <MultiValuedProperty>] + [-HiddenFromAddressListsEnabled <Boolean>] + [-HiddenFromExchangeClientsEnabled] + [-InformationBarrierMode <GroupInformationBarrierMode>] + [-IsMemberAllowedToEditContent <System.Boolean>] + [-Language <CultureInfo>] + [-MailboxRegion <String>] + [-MailTip <String>] + [-MailTipTranslations <MultiValuedProperty>] + [-MaxReceiveSize <Unlimited>] + [-MaxSendSize <Unlimited>] + [-ModeratedBy <MultiValuedProperty>] + [-ModerationEnabled <Boolean>] + [-Notes <String>] + [-PrimarySmtpAddress <SmtpAddress>] + [-RejectMessagesFromSendersOrMembers <MultiValuedProperty>] + [-RequireSenderAuthenticationEnabled <Boolean>] + [-SensitivityLabelId <Sustem.Guid>] + [-SubscriptionEnabled] + [-UnifiedGroupWelcomeMessageEnabled] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +> [!NOTE] +> You can't change the HiddenGroupMembershipEnabled setting on an existing Microsoft 365 Group. The setting is available only during new group creation. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-UnifiedGroup -Identity "Marketing Department" -PrimarySmtpAddress marketing@contoso.com -RequireSenderAuthenticationEnabled $false +``` + +This example makes the following changes to the Microsoft 365 Group named Marketing Department: + +- The primary email address is changed to marketing@contoso.com. +- The Microsoft 365 Group is allowed to receive mail from unauthenticated (external) senders. + +### Example 2 +```powershell +Set-UnifiedGroup -Identity "Legal Department" -AccessType Private +``` + +This example changes the Microsoft 365 Group named Legal Department from a public group to a private group. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +Type: UnifiedGroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AcceptMessagesOnlyFromSendersOrMembers +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. + +To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessType +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. +- Private: The group content and conversations are available only to members of the group, and joining the group requires approval from a group owner. + +**Note**: Although a user needs to be a member to participate in a private group, anyone can send email to a private group, and receive replies from the private group. + +```yaml +Type: ModernGroupTypeInfo +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Alias +The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the 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: + +- !, #, %, \*, +, -, /, =, ?, ^, \_, and ~. +- $, &, ', \`, {, }, and \| need to be escaped (for example ``-Alias what`'snew``) or the entire value enclosed in single quotation marks (for example, `-Alias 'what'snew'`). The & character is not supported in the Alias value for Microsoft Entra Connect synchronization. +- Periods (.) must be surrounded by other valid characters (for example, `help.desk`). +- Unicode characters U+00A1 to U+00FF. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AlwaysSubscribeMembersToCalendarEvents +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. +- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false,` all future members that are added to the group will have their subscriptions set to ReplyOnly. + +Group members can change their own subscription settings, which can override your intended use of this switch. + +The AutoSubscribeNewMembers switch overrides this switch. + +**Note**: This property is evaluated only when you add internal members from your organization. Guest user accounts are always subscribed when added as a member. You can manually remove subscriptions for guest users by using the Remove-UnifiedGroupLinks cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuditLogAgeLimit +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. + +For example, to specify 60 days for this parameter, use 60.00:00:00. + +```yaml +Type: EnhancedTimeSpan +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoSubscribeNewMembers +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. +- If you don't want to subscribe new members to conversations and calendar events, use this exact syntax: `-AutoSubscribeNewMembers:$false`. + +**Note**: This property is evaluated only when you add internal members from your organization. Guest user accounts are always subscribed when added as a member. You can manually remove subscriptions for guest users by using the Remove-UnifiedGroupLinks cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CalendarMemberReadOnly +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. +- To remove read-only Calendar permissions, use this exact syntax: `-CalendarMemberReadOnly:$false`. + +To view the current value of the CalendarMemberReadOnly property on a Microsoft 365 Group, replace `<EmailAddress>` with the email address of the group, and run this command: `Get-UnifiedGroup -Identity <EmailAddress> -IncludeAllProperties | Format-List *Calendar*`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Classification +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorsEnabled +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. +- To disable connectors, use this exact syntax: `-ConnectorsEnabled:$false`. + +To use this switch, the value of the ConnectorsEnabled parameter on the Set-OrganizationConfig cmdlet must be set to $true (which is the default value). + +For more information about connectors for Microsoft 365 Groups, see [Connect apps to your groups in Outlook](https://support.microsoft.com/office/ed0ce547-038f-4902-b9b3-9e518ae6fbab). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute1 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute10 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute11 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute12 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute13 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute14 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute15 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute2 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute3 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute4 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute5 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute6 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute7 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute8 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAttribute9 +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DataEncryptionPolicy +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 +- Distinguished name (DN) +- GUID + +To remove an existing policy, use the value $null. + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmailAddresses +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: + +- SMTP: The primary SMTP address. You can use this value only once in a command. +- smtp: Other SMTP email addresses. +- SPO: SharePoint email address. + +If you don't include a Type value for an email address, the address is assumed to be an SMTP email address. The syntax of SMTP email addresses is validated, but the syntax of other email address types isn't validated. Therefore, you need to verify that any custom addresses are formatted correctly. + +To specify the primary SMTP email address, you can use any of the following methods: + +- Use the Type value SMTP on the address. +- The first email address when you don't use any Type values, or when you use multiple lowercase smtp Type values. +- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. + +To replace all existing proxy email addresses with the values you specify, use the following syntax: `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. + +To add or remove specify proxy addresses without affecting other existing values, use the following syntax: `@{Add="Type:EmailAddress1","Type:EmailAddress2",...; Remove="Type:EmailAddress3","Type:EmailAddress4",...}`. + +```yaml +Type: ProxyAddressCollection +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute1 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute2 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute3 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute4 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtensionCustomAttribute5 +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceUpgrade +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GrantSendOnBehalfTo +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 (`<Sender> on behalf of <Microsoft 365 Group>`), 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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +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"`. + +To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. + +By default, this parameter is blank, which means no one else has permission to send on behalf of this Microsoft 365 Group. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenFromAddressListsEnabled +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. +- $false: The Microsoft 365 Group is visible in the GAL and other address lists. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenFromExchangeClientsEnabled +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). +- To disable this setting, use this exact syntax: `-HiddenFromExchangeClientsEnabled:$false`. The Microsoft 365 Group isn't hidden from Outlook experiences. The group will be visible in the GAL and other address lists. This is the default value. +- If Microsoft 365 Groups are hidden from Exchange clients, users don't see the option to subscribe or unsubscribe to a Microsoft 365 Group. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InformationBarrierMode +The InformationBarrierMode parameter specifies the information barrier mode for the Microsoft 365 Group. Valid values are: + +- Explicit +- Implicit +- Open +- OwnerModerated + +```yaml +Type: GroupInformationBarrierMode +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsMemberAllowedToEditContent +{{ Fill IsMemberAllowedToEditContent Description }} + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Language +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). + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxRegion +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTip +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: + +- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: `<html><body>This mailbox is not monitored</body></html>`. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. +- The text is automatically added to the MailTipTranslations property of the recipient as the default value: `default:<MailTip text>`. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailTipTranslations +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: + +`@{Add="Culture1:Localized text 1","\Culture2:Localized text 2"...; Remove="Culture3:Localized text 3","Culture4:Localized text 4"...}`. + +CultureN is a valid ISO 639 two-letter culture code that's associated with the language. + +For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: `@{Add="ES:Esta caja no se supervisa."}`. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxReceiveSize +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). + +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxSendSize +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: + +- B (bytes) +- KB (kilobytes) +- MB (megabytes) +- GB (gigabytes) + +Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. + +A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). + +Base64 encoding increases the size of messages by approximately 33%, so specify a value that's 33% larger than the actual maximum message size that you want to enforce. For example, the value 64 MB results in a maximum message size of approximately 48 MB. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModeratedBy +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +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"`. + +You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModerationEnabled +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. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. + +You use the ModeratedBy parameter to specify the moderators. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Notes +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySmtpAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RejectMessagesFromSendersOrMembers +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. + +To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: `Sender1,Sender2,...SenderN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Sender1","Sender2",..."SenderN"`. + +To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. + +The individual senders and groups you specify for this parameter are automatically copied to the RejectMessagesFrom and RejectMessagesFromDLMembers properties, respectively. Therefore, you can't use the RejectMessagesFromSendersOrMembers parameter and the RejectMessagesFrom or RejectMessagesFromDLMembers parameters in the same command. + +By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireSenderAuthenticationEnabled +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. +- $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SensitivityLabelId +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. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubscriptionEnabled +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. +- To change the value to $false, use this exact syntax: `-SubscriptionEnabled:$false`. The value of the AutoSubscribeNewMembers parameter must also be $false before you can use the value $false for this switch. + +**Note**: You should use the value $false for this switch only if you intend to disable group owner ability to change subscription options on the group. Group owners will not be able to enable subscription options on the group settings using Outlook on the web or Outlook desktop. Group owners might see the error, "The group update is in progress" error when they try to enable Subscription option. Admins trying to enable Subscription from Microsoft admin center might also see error, "Can't save 'Send copies of group conversations and events to group member's inboxes' Either your assigned product license doesn't include Exchange Online or you have recently created this group and it's still not ready for management". + +**Note**: This property is evaluated only when you add internal members from your organization. Guest user accounts are always subscribed when added as a member. You can manually remove subscriptions for guest users by using the Remove-UnifiedGroupLinks cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnifiedGroupWelcomeMessageEnabled +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. +- To disable this setting, use this exact syntax: `-UnifiedGroupWelcomeMessageEnabled:$false`. + +This setting only controls email send by the Microsoft 365 Group. It doesn't control email sent by connected products (for example, Teams or Viva Engage). + +This setting is enabled by default. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-User.md b/exchange/exchange-ps/exchange/Set-User.md similarity index 77% rename from exchange/exchange-ps/exchange/users-and-groups/Set-User.md rename to exchange/exchange-ps/exchange/Set-User.md index 94b64da187..09606906d6 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-User.md +++ b/exchange/exchange-ps/exchange/Set-User.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-user +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Set-User @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Set-User cmdlet to modify user attributes. You can use this cmdlet to modify all objects that have user accounts (for example, user mailboxes, mail users, and user accounts). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,26 +26,35 @@ Set-User [-Identity] <UserIdParameter> [-Arbitration] [-AssistantName <String>] [-AuthenticationPolicy <String>] + [-BlockCloudCache <Boolean>] + [-CanHaveCloudCache <Boolean>] [-CertificateSubject <MultiValuedProperty>] [-City <String>] + [-ClearDataEncryptionPolicy] [-Company <String>] [-Confirm] [-CountryOrRegion <CountryInfo>] [-CreateDTMFMap <Boolean>] [-Department <String>] + [-DesiredWorkloads <MailboxWorkloadFlags>] [-DisplayName <String>] [-DomainController <Fqdn>] + [-EXOModuleEnabled <Boolean>] [-Fax <String>] [-FirstName <String>] [-Force] [-GeoCoordinates <GeoCoordinates>] [-HomePhone <String>] [-IgnoreDefaultScope] + [-IsShadowMailbox <Boolean>] [-Initials <String>] [-LastName <String>] [-LinkedCredential <PSCredential>] [-LinkedDomainController <String>] [-LinkedMasterAccount <UserIdParameter>] + [-MailboxRegion <String>] + [-MailboxRegionSuffix <MailboxRegionSuffixValue>] + [-ManagedOnboardingType <ManagedOnboardingType>] [-Manager <UserContactIdParameter>] [-MobilePhone <String>] [-Name <String>] @@ -77,6 +85,7 @@ Set-User [-Identity] <UserIdParameter> [-UMCallingLineIds <MultiValuedProperty>] [-UMDtmfMap <MultiValuedProperty>] [-UserPrincipalName <String>] + [-VIP <Boolean>] [-WebPage <String>] [-WhatIf] [-WindowsEmailAddress <SmtpAddress>] @@ -86,7 +95,7 @@ Set-User [-Identity] <UserIdParameter> ## DESCRIPTION The Set-User cmdlet contains no mail-related properties for mailboxes or mail users. To modify the mail-related properties for a user, you need to use the corresponding cmdlet based on the object type (for example, Set-Mailbox or Set-MailUser). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -112,13 +121,10 @@ Performing this procedure on a linked mailbox removes all permissions on the mai The Identity parameter specifies the user that you want to modify. You can use any value that uniquely identifies the user. For example: - Name - +- User principal name (UPN) - Distinguished name (DN) - - Canonical DN - - GUID - - UserPrincipalName ```yaml @@ -135,13 +141,15 @@ Accept wildcard characters: False ``` ### -AllowUMCallsFromNonUsers -The AllowUMCallsFromNonUsers parameter specifies whether to exclude the user from directory searches. +This parameter is available only in on-premises Exchange. + +The AllowUMCallsFromNonUsers parameter specifies whether to exclude the user from Unified Messaging directory searches. ```yaml Type: AllowUMCallsFromNonUsersFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -190,9 +198,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID To remove the policy assignment for the user, use the value $null. @@ -203,7 +209,43 @@ You create authentication policies with the New-AuthenticationPolicy cmdlet to b Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockCloudCache +This parameter is available only in the cloud-based service. + +{{ Fill BlockCloudCache Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CanHaveCloudCache +This parameter is available only in the cloud-based service. + +{{ Fill CanHaveCloudCache Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -246,6 +288,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ClearDataEncryptionPolicy +This parameter is available only in the cloud-based service. + +{{ Fill ClearDataEncryptionPolicy Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Company The Company parameter specifies the user's company. @@ -265,8 +325,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -283,7 +342,11 @@ Accept wildcard characters: False ``` ### -CountryOrRegion -The CountryOrRegion parameter specifies the user's country or region. +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). + +The friendly name is returned in the CountryOrRegion property value by the Get-User cmdlet, but you can use either the friendly name or the two-letter country code in filter operations. ```yaml Type: CountryInfo @@ -299,17 +362,18 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap +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: - $true: A DTMF map is created for the recipient. This is the default value. - - $false: A DTMF map isn't created for the recipient. ```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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -334,6 +398,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DesiredWorkloads +This parameter is available only in the cloud-based service. + +{{ Fill DesiredWorkloads Description }} + +```yaml +Type: Microsoft.Exchange.Data.MailboxWorkloadFlags +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DisplayName 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 ("). @@ -368,6 +450,31 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EXOModuleEnabled +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: + +- $true: The user can connect to Exchange Online PowerShell. +- $false: The user can't connect to Exchange Online PowerShell. + +The default value depends on the management roles that are assigned to the user. + + Access to Exchange Online PowerShell is also required for other features (for example, the ability to open the Exchange admin center (EAC)). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Fax The Fax parameter specifies the user's fax number. @@ -403,13 +510,15 @@ Accept wildcard characters: False ### -Force This parameter is available only in the cloud-based service. -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. +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. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -422,9 +531,10 @@ Accept wildcard characters: False 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" - - Latitude, longitude, and altitude: For example, "47.644125;-122.122411;161.432" +**Note**: If period separators don't work for you, use commas instead. + ```yaml Type: GeoCoordinates Parameter Sets: (All) @@ -457,12 +567,11 @@ Accept wildcard characters: False ### -IgnoreDefaultScope 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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. +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. -Using the IgnoreDefaultScope switch introduces the following restrictions: +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: - You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - - You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. ```yaml @@ -494,6 +603,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IsShadowMailbox +This parameter is available only in the cloud-based service. + +{{ Fill IsShadowMailbox Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -LastName The LastName parameter specifies the user's last name. @@ -515,7 +642,7 @@ 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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). You can only use the LinkedCredential parameter with a linked user. @@ -558,19 +685,12 @@ 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: - GUID - - DN - - Domain\\Account - - UPN - - LegacyExchangeDN - - SmtpAddress - - Alias - - $null If you set this parameter's value to $null, you will unlink the account and convert the linked mailbox into a non-linked user mailbox. The mailbox won't retain the permissions previously set on it such as Send As, full access, folder, and calendar delegation. @@ -590,6 +710,60 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MailboxRegion +This parameter is available only in the cloud-based service. + +{{ Fill MailboxRegion Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxRegionSuffix +This parameter is available only in the cloud-based service. + +{{ Fill MailboxRegionSuffix Description }} + +```yaml +Type: MailboxRegionSuffixValue +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedOnboardingType +This parameter is available only in the cloud-based service. + +{{ Fill ManagedOnboardingType Description }} + +```yaml +Type: ManagedOnboardingType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Manager The Manager parameter specifies the user's manager. @@ -609,6 +783,8 @@ Accept wildcard characters: False ### -MobilePhone 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. + ```yaml Type: String Parameter Sets: (All) @@ -735,18 +911,19 @@ Accept wildcard characters: False ``` ### -PermanentlyClearPreviousMailboxInfo -The PermanentlyClearPreviousMailboxInfo switch specifies whether to clear the Exchange mailbox attributes on a user. You don't need to specify a value with this switch. +This parameter is functional only in the cloud-based service. -Clearing these attributes might be required in mailbox move and re-licensing scenarios between on-premises Exchange and Office 365. For more information, see [Permanently Clear Previous Mailbox Info](https://techcommunity.microsoft.com/t5/exchange-team-blog/permanently-clear-previous-mailbox-info/ba-p/607619). +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. -> [!CAUTION] -> This switch permanently deletes the existing cloud mailbox and its associated archive, prevents you from reconnecting to the mailbox, and prevents you from recovering content from the mailbox. +Clearing these attributes might be required in mailbox move and re-licensing scenarios between on-premises Exchange and Microsoft 365. For more information, see [Permanently Clear Previous Mailbox Info](https://techcommunity.microsoft.com/t5/exchange-team-blog/permanently-clear-previous-mailbox-info/ba-p/607619). + +**Caution**: This switch prevents you from reconnecting to the mailbox and prevents you from recovering content from the mailbox. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -758,6 +935,8 @@ Accept wildcard characters: False ### -Phone 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. + ```yaml Type: String Parameter Sets: (All) @@ -838,14 +1017,19 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled -The RemotePowerShellEnabled parameter specifies whether the user has access to remote PowerShell. Remote PowerShell access is required to open the Exchange Management Shell or the Exchange admin center (EAC), even if you're trying to open the Exchange Management Shell or the EAC on the local Mailbox server. Valid values are: +**Note**: In cloud-based environments, this parameter is being deprecated, so use the EXOModuleEnabled parameter instead. -- $true: The user has access to remote PowerShell. +The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: -- $false: The user doesn't have access to remote PowerShell. +- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). +- $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. The default value depends on the management roles that are assigned to the user. +Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. + +A user's experience in any of these management interfaces is still controlled by the role-based access control (RBAC) permissions that are assigned to them. + ```yaml Type: Boolean Parameter Sets: (All) @@ -868,7 +1052,7 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -881,7 +1065,6 @@ Accept wildcard characters: False 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. - - $false: The user isn't required to change their password the next time they log on. This is the default value. ```yaml @@ -900,7 +1083,7 @@ Accept wildcard characters: False ### -SamAccountName 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 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. +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 @@ -935,12 +1118,10 @@ Accept wildcard characters: False 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 - - A - Z - - 0 - 9 - -- "\<space\>", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". +- space +- `" ' ( ) + , - . / : ?` ```yaml Type: String @@ -956,13 +1137,15 @@ Accept wildcard characters: False ``` ### -SkipDualWrite +This parameter is available only in on-premises Exchange. + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1008,13 +1191,13 @@ 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. -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". +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". ```yaml Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1076,27 +1259,27 @@ Accept wildcard characters: False ``` ### -UMDtmfMap -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: - -- emailAddress:\<integers\> +This parameter is available only in on-premises Exchange. -- lastNameFirstName:\<integers\> +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: -- firstNameLastName:\<integers\> +- `emailAddress:<integers>` +- `lastNameFirstName:<integers>` +- `firstNameLastName:<integers>` -To enter values that overwrite all existing entries, use the following syntax: emailAddress:\<integers\>,lastNameFirstName:\<integers\>,firstNameLastName:\<integers\>. +To enter values that overwrite all existing entries, use the following syntax: `emailAddress:<integers>,lastNameFirstName:<integers>,firstNameLastName:<integers>`. -If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:\<integers\>, all existing lastNameFirstName and firstNameLastName values are removed. +If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only `emailAddress:<integers>`, all existing lastNameFirstName and firstNameLastName values are removed. -To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:\<integers\>","lastNameFirstName:\<integers\>","firstNameLastName:\<integers\>"; Remove="emailAddress:\<integers\>","lastNameFirstName:\<integers\>","firstNameLastName:\<integers\>"}. +To add or remove values without affecting other existing entries, use the following syntax: `@{Add="emailAddress:<integers>","lastNameFirstName:<integers>","firstNameLastName:<integers>"; Remove="emailAddress:<integers>","lastNameFirstName:<integers>","firstNameLastName:<integers>"}`. -If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:\<integers1\>","emailAddress:\<integers2\>} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. +If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use `@{Add="emailAddress:<integers1>","emailAddress:<integers2>}` to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. ```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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1108,7 +1291,7 @@ Accept wildcard characters: False ### -UserPrincipalName 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. +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 @@ -1123,6 +1306,29 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -VIP +This parameter is available only in the cloud-based service. + +The VIP parameter specifies whether the user is a priority account. Valid values are: + +- $true: The user is a priority account. +- $false: The user is not a priority account. + +For more information about priority accounts, see [Manage and monitor priority accounts](https://learn.microsoft.com/microsoft-365/admin/setup/priority-accounts). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WebPage The WebPage parameter specifies the user's Web page. @@ -1140,7 +1346,7 @@ Accept wildcard characters: False ``` ### -WhatIf -The WhatIf switch doesn’t work on this cmdlet. +The WhatIf switch doesn't work on this cmdlet. ```yaml Type: SwitchParameter @@ -1159,7 +1365,6 @@ Accept wildcard characters: False 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. - - In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. @@ -1182,12 +1387,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Set-UserBriefingConfig.md b/exchange/exchange-ps/exchange/Set-UserBriefingConfig.md new file mode 100644 index 0000000000..d036882c11 --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-UserBriefingConfig.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +--- + +# Set-UserBriefingConfig + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Set-UserBriefingConfig cmdlet to enable or disable the Briefing email for a user. For more details about configuring the Briefing email, see [Configure Briefing email](https://learn.microsoft.com/Briefing/be-admin). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-UserBriefingConfig -Identity <String> -Enabled <Boolean> + [-ResultSize <Unlimited>] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Insights Administrator + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 + +```powershell +Set-UserBriefingConfig -Identity lila@contoso.com -Enabled $true +``` + +This example enables the Briefing email for lila@contoso.com. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. +- $false: The daily briefing message is disabled. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Configure Briefing email](https://learn.microsoft.com/Briefing/be-admin) diff --git a/exchange/exchange-ps/exchange/Set-UserPhoto.md b/exchange/exchange-ps/exchange/Set-UserPhoto.md new file mode 100644 index 0000000000..d2c06bedea --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-UserPhoto.md @@ -0,0 +1,391 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Set-UserPhoto + +## SYNOPSIS +This cmdlet is available only in on-premises Exchange. + +Use the Set-UserPhoto cmdlet to configure the user photos feature that allows users to associate a picture with their account. User photos appear in client applications, such as Outlook, Microsoft Teams, and SharePoint. + +**Note**: In Microsoft 365, you can manage user photos in Microsoft Graph PowerShell. For instructions, see [Manage user photos in Microsoft Graph PowerShell](https://learn.microsoft.com/microsoft-365/admin/add-users/change-user-profile-photos#manage-user-photos-in-microsoft-graph-powershell). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### CancelPhoto +``` +Set-UserPhoto [-Identity] <MailboxIdParameter> + [-Cancel] + [-Confirm] + [-GroupMailbox] + [-DomainController <Fqdn>] + [-IgnoreDefaultScope] + [-PhotoType <String>] + [-UseCustomRouting] + [-WhatIf] + [<CommonParameters>] +``` + +### UploadPhotoData +``` +Set-UserPhoto [-Identity] <MailboxIdParameter> -PictureData <Byte[]> + [-Confirm] + [-DomainController <Fqdn>] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-PhotoType <String>] + [-UseCustomRouting] + [-WhatIf] + [<CommonParameters>] +``` + +### UploadPreview +``` +Set-UserPhoto [-Identity] <MailboxIdParameter> + [-PictureData <Byte[]>] + [-PictureStream <Stream>] + [-Preview] + [-Confirm] + [-DomainController <Fqdn>] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-PhotoType <String>] + [-UseCustomRouting] + [-WhatIf] + [<CommonParameters>] +``` + +### UploadPhotoStream +``` +Set-UserPhoto [-Identity] <MailboxIdParameter> -PictureStream <Stream> + [-Confirm] + [-DomainController <Fqdn>] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-PhotoType <String>] + [-UseCustomRouting] + [-WhatIf] + [<CommonParameters>] +``` + +### SavePhoto +``` +Set-UserPhoto [-Identity] <MailboxIdParameter> + [-Save] + [-Confirm] + [-DomainController <Fqdn>] + [-GroupMailbox] + [-IgnoreDefaultScope] + [-PhotoType <String>] + [-UseCustomRouting] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The user photos feature allows users to associate a picture with their account. User photos are stored in the user's Active Directory account and in the root directory of the user's Exchange mailbox. Administrators use the Set-UserPhoto cmdlet to configure user photos. Users can upload, preview, and save a user photo to their account in the Options page in Outlook on the web. When a user uploads a photo, a preview of the photo is displayed on the Options page in Outlook on the web. This is the preview state, and creates the same result as running the Set-UserPhoto cmdlet using the Preview parameter. If the user clicks Save, the preview photo is saved as the user's photo. This is the same result as running the `Set-UserPhoto -Save` command or running both the `Set-UserPhoto -Preview` and `Set-UserPhoto -Save` commands. If the user cancels the preview photo on the Options page in Outlook on the web, then the `Set-UserPhoto -Cancel` command is called. + +A user photo must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user's photo. Otherwise, you'll get an error message saying the user photo doesn't exist for the specified user. Alternatively, you can run the `Get-UserPhoto -Preview` command to view information about a preview photo. + +**Notes**: Changes to the user photo won't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Set-UserPhoto -Identity "Paul Cannon" -PictureData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\PaulCannon.jpg")) +``` + +This example uploads and saves a photo to Paul Cannon's user account using a single command. + +### Example 2 +```powershell +Set-UserPhoto -Identity "Ann Beebe" -PictureData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\AnnBeebe.jpg")) -Preview + +Set-UserPhoto "Ann Beebe" -Save +``` + +This example shows how to use two commands to upload and save a preview photo to Ann Beebe's user account. The first command uploads a preview photo to Ann Beebe's user account, and the second command saves the uploaded photo as the preview photo. + +### Example 3 +```powershell +Set-UserPhoto -Identity "Ann Beebe" -Cancel +``` + +This example deletes the preview photo that was uploaded in the previous example. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Cancel +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. + +```yaml +Type: SwitchParameter +Parameter Sets: CancelPhoto +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PictureData +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). + +```yaml +Type: Byte[] +Parameter Sets: UploadPhotoData +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +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 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +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 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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. + +```yaml +Type: SwitchParameter +Parameter Sets: UploadPreview +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Save +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMailbox +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IgnoreDefaultScope +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: + +- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. +- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhotoType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Set-VivaInsightsSettings.md b/exchange/exchange-ps/exchange/Set-VivaInsightsSettings.md new file mode 100644 index 0000000000..d794753e4e --- /dev/null +++ b/exchange/exchange-ps/exchange/Set-VivaInsightsSettings.md @@ -0,0 +1,136 @@ +--- +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 +ms.author: chrisda +--- + +# Set-VivaInsightsSettings + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +**Note**: This cmdlet is available only in version 2.0.5 or later of the module. + +Use the Set-VivaInsightsSettings cmdlet to control user access to features in Viva Insights. Only users with provisioned Exchange Online mailboxes can access features within the Viva Insights app in Teams. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Set-VivaInsightsSettings -Identity <String> -Enabled <Boolean> -Feature <String> + [-ResultSize <Unlimited>] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet requires the .NET Framework 4.7.2 or later. + +To run this cmdlet, you need to be a member of one of the following directory role groups in the destination organization: + +- Global Administrator +- Exchange Administrator +- Teams Administrator + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Set-VivaInsightsSettings -Identity roy@contoso.onmicrosoft.com -Enabled $false -Feature headspace +``` + +This example disables access to all the Headspace features in Microsoft Viva Insights in Microsoft Teams for the specified user. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +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. +- $false: The specified features in Microsoft Viva Insights in Microsoft Teams are disabled for the user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Feature +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. +- MeetingEffectivenessSurvey: This value is available only in version 2.0.6-Preview2 of the module as part of a Private Preview. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Accepted values: headspace +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-WebServicesVirtualDirectory.md b/exchange/exchange-ps/exchange/Set-WebServicesVirtualDirectory.md similarity index 86% rename from exchange/exchange-ps/exchange/client-access-servers/Set-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/exchange/Set-WebServicesVirtualDirectory.md index 1857c87a3a..09636df6f4 100644 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/exchange/Set-WebServicesVirtualDirectory.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-webservicesvirtualdirectory +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-WebServicesVirtualDirectory @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Set-WebServicesVirtualDirectory cmdlet to modify existing Exchange Web Services virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -38,8 +37,7 @@ Set-WebServicesVirtualDirectory [-Identity] <VirtualDirectoryIdParameter> [-InternalUrl <Uri>] [-MRSProxyEnabled <Boolean>] [-MRSProxyMaxConnections <Unlimited>] - [-OAuthAuthentication <Boolean>] [-OAuthAuthentication <Boolean>] - [-UpdateManagementVirtualDirectory] + [-OAuthAuthentication <Boolean>] [-WhatIf] [-WindowsAuthentication <Boolean>] [-WSSecurityAuthentication <Boolean>] @@ -47,7 +45,7 @@ Set-WebServicesVirtualDirectory [-Identity] <VirtualDirectoryIdParameter> ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,13 +75,11 @@ This example enables MRSProxy on the EWS default website. MRSProxy is the servic ### -Identity 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 - +- Name or Server\\Name - Distinguished name (DN) - - GUID -The Name value uses the syntax "\<VirtualDirectoryName\> (\<WebsiteName\>)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \<VirtualDirectoryName\>\*. +The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax `VirtualDirectoryName*`. ```yaml Type: VirtualDirectoryIdParameter @@ -102,7 +98,6 @@ Accept wildcard characters: False 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. - - $false: Basic authentication is disabled. ```yaml @@ -119,7 +114,7 @@ Accept wildcard characters: False ``` ### -CertificateAuthentication -The CertificateAuthentication parameter specifies whether certificate authentication is enabled. This parameter affects the \<Servername\>/ews/management/ virtual directory. It doesn't affect the \<Servername\>/ews/ virtual directory. +The CertificateAuthentication parameter specifies whether certificate authentication is enabled. This parameter affects the `<Servername>/ews/management/` virtual directory. It doesn't affect the `<Servername>/ews/` virtual directory. ```yaml Type: Boolean @@ -137,8 +132,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -158,7 +152,6 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. - - $false: Digest authentication is disabled. This is the default value. ```yaml @@ -194,13 +187,9 @@ Accept wildcard characters: False The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are: - None: This is the default setting. - - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. - - ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml @@ -220,8 +209,7 @@ Accept wildcard characters: False 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. - -- Single SPN or comma delimited list of valid SPNs: The SPN value format is \<protocol\>/\<FQDN\>. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. +- Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml Type: MultiValuedProperty @@ -240,14 +228,10 @@ Accept wildcard characters: False 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. - - Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. - - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. -Note: - -If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. ```yaml Type: ExtendedProtectionTokenCheckingMode @@ -281,7 +265,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -300,11 +286,8 @@ Accept wildcard characters: False The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are: - Off: No compression. - - Low: Static compression only. This is the default value. This value has the same result as the Off value, because Exchange Web Services content is dynamic. - - High: Static and dynamic compression. Content from Exchange Web Services is compressed if clients indicate support for Gzip compression in their requests. - - Error: Identifies errors in the Gzip compression configuration. ```yaml @@ -321,6 +304,8 @@ Accept wildcard characters: False ``` ### -InternalNLBBypassUrl +**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. 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. @@ -373,9 +358,9 @@ Accept wildcard characters: False ``` ### -MRSProxyMaxConnections -This parameter is available or functional only in 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://docs.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). +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)). ```yaml Type: Unlimited @@ -394,7 +379,6 @@ Accept wildcard characters: False 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. - - $false: OAuth authentication is disabled. ```yaml @@ -410,24 +394,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -UpdateManagementVirtualDirectory -This parameter is available or functional only in Exchange Server 2010. - -The UpdateManagementVirtualDirectory parameter makes sure that the Exchange Web Services objects in Active Directory and the respective objects in Internet Information Services (IIS) are up to date and consistent. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -448,7 +414,6 @@ Accept wildcard characters: False 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. - - $false: Integrated Windows authentication is disabled. ```yaml @@ -468,7 +433,6 @@ Accept wildcard characters: False 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. - - $false: WS-Security authentication is disabled. ```yaml @@ -489,12 +453,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Set-X400AuthoritativeDomain.md b/exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Set-X400AuthoritativeDomain.md rename to exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md index 06fb3eb27b..30872ecd30 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Set-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-x400authoritativedomain +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Set-X400AuthoritativeDomain @@ -17,25 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Set-X400AuthoritativeDomain cmdlet to edit an existing X.400 authoritative domain for your organization. The X.400 authoritative domain defines the standard fields for the namespace appended to the recipient identity for all mailboxes assigned an X.400 address. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Set-X400AuthoritativeDomain [-Identity] <X400AuthoritativeDomainIdParameter> [-Confirm] - [-DomainController <Fqdn>] [-Name <String>] [-WhatIf] [-X400DomainName <X400Domain>] - [-X400ExternalRelay <Boolean>] [<CommonParameters>] +Set-X400AuthoritativeDomain [-Identity] <X400AuthoritativeDomainIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-Name <String>] + [-WhatIf] + [-X400DomainName <X400Domain>] + [-X400ExternalRelay <Boolean>] + [<CommonParameters>] ``` ## DESCRIPTION X.400 domain names can include only the following ASCII characters: - A to Z - - a to z - - 0-9 - - These punctuation marks and special characters: (space) ' () + , - . / : = ? You can use the following X.400 attributes (1 each per address): @@ -43,34 +44,29 @@ You can use the following X.400 attributes (1 each per address): country - Abbreviation: C - - Maximum character length: 2 administrative domain - Abbreviation: A - - Maximum character length: 16 private domain - Abbreviation: P - - Maximum character length: 16 organization name - Abbreviation: O - - Maximum character length: 64 organizational unit name - Abbreviation: OU1 to OU4 - - Maximum character length: 32 -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,18 +78,15 @@ Set-X400AuthoritativeDomain Sales -X400DomainName "C=US;A=att,P=Contoso;O=Sales This example makes the following changes to an existing X.400 authoritative domain: - It changes the domain name from Sales to Sales and Marketing. - - It updates the organizational attribute to Sales and Marketing. ## PARAMETERS ### -Identity -The Identity parameter specifies the X.400 authoritative domain tht you want to modify. You can use any value that uniquely identifies the domain. For example: +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 - - Distinguished name (DN) - - GUID ```yaml @@ -112,8 +105,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -183,19 +175,12 @@ Accept wildcard characters: False 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) - - A (ADMD) - - P (PRMD) - - O (Organization) - - OU1 (Organization unit 1) - - OU2 (Organization unit 2) - - OU3 (Organization unit 3) - - OU4 (Organization unit 4) Separate the address attributes with semicolons and enclose the entire address in quotation marks (for example, "C=US;A=att;P=Contoso;O=Sales"). @@ -214,7 +199,7 @@ Accept wildcard characters: False ``` ### -X400ExternalRelay -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. +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 @@ -234,12 +219,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Start-ComplianceSearch.md b/exchange/exchange-ps/exchange/Start-ComplianceSearch.md new file mode 100644 index 0000000000..ddcb34db75 --- /dev/null +++ b/exchange/exchange-ps/exchange/Start-ComplianceSearch.md @@ -0,0 +1,153 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Start-ComplianceSearch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Start-ComplianceSearch cmdlet to start stopped, completed or not started compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Start-ComplianceSearch [-Identity] <ComplianceSearchIdParameter> + [-Confirm] + [-Force] + [-RetryOnError] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Start-ComplianceSearch -Identity "Case 1234" +``` + +This example starts the compliance search named Case 1234 + +## PARAMETERS + +### -Identity +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: + +- Name +- JobRunId (GUID) + +You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status + +```yaml +Type: ComplianceSearchIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetryOnError +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Start-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/Start-DatabaseAvailabilityGroup.md similarity index 91% rename from exchange/exchange-ps/exchange/database-availability-groups/Start-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/exchange/Start-DatabaseAvailabilityGroup.md index 50a2e082b3..771a794112 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Start-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/exchange/Start-DatabaseAvailabilityGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/start-databaseavailabilitygroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Start-DatabaseAvailabilityGroup @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Start-DatabaseAvailabilityGroup cmdlet to reincorporate one or more previously failed members of a database availability group (DAG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Start-DatabaseAvailabilityGroup [-Identity] <DatabaseAvailabilityGroupIdParamete [-ConfigurationOnly] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### MailboxSet @@ -36,13 +36,14 @@ Start-DatabaseAvailabilityGroup [-Identity] <DatabaseAvailabilityGroupIdParamete [-ConfigurationOnly] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Start-DatabaseAvailabilityGroup cmdlet is used to activate DAG members in a recovered datacenter after a datacenter switchover, as part of the switchback process to the recovered datacenter. The Start-DatabaseAvailabilityGroup cmdlet manipulates configuration and state so that the servers are incorporated into the operating DAG, and joined to the DAG's underlying cluster. The Move-ActiveMailboxDatabase cmdlet is then used to activate databases in the primary datacenter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,33 +63,33 @@ This example starts the members of the DAG DAG1 in the Active Directory site Red ## PARAMETERS -### -ActiveDirectorySite -The ActiveDirectorySite parameter specifies whether to start all DAG members in the specified site. +### -Identity +The Identity parameter specifies the name of the DAG being started. ```yaml -Type: AdSiteIdParameter -Parameter Sets: Identity +Type: DatabaseAvailabilityGroupIdParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the DAG being started. +### -ActiveDirectorySite +The ActiveDirectorySite parameter specifies whether to start all DAG members in the specified site. ```yaml -Type: DatabaseAvailabilityGroupIdParameter -Parameter Sets: (All) +Type: AdSiteIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False @@ -111,7 +112,7 @@ Accept wildcard characters: False ``` ### -ConfigurationOnly -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. +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 @@ -129,8 +130,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -183,12 +183,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Start-EdgeSynchronization.md b/exchange/exchange-ps/exchange/Start-EdgeSynchronization.md similarity index 76% rename from exchange/exchange-ps/exchange/mail-flow/Start-EdgeSynchronization.md rename to exchange/exchange-ps/exchange/Start-EdgeSynchronization.md index d59bdbb988..a61cfb7896 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Start-EdgeSynchronization.md +++ b/exchange/exchange-ps/exchange/Start-EdgeSynchronization.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/start-edgesynchronization +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Start-EdgeSynchronization @@ -17,19 +16,24 @@ This cmdlet is available only in on-premises Exchange. Use the Start-EdgeSynchronization cmdlet to immediately start synchronization of configuration data from Active Directory to the subscribed Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Start-EdgeSynchronization [-Confirm] [-ForceFullSync] [-ForceUpdatecookie] [-Server <ServerIdParameter>] - [-TargetServer <String>] [-WhatIf] [<CommonParameters>] +Start-EdgeSynchronization [-Confirm] + [-ForceFullSync] + [-ForceUpdateCookie] + [-Server <ServerIdParameter>] + [-TargetServer <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Microsoft Exchange EdgeSync service that runs on Mailbox servers replicates data stored in Active Directory to the local Active Directory Lightweight Directory Services (AD LDS) store on the Edge Transport server. After the initial replication, one-way synchronization of changed data in Active Directory to AD LDS keeps this data up to date. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,8 +49,7 @@ This example starts edge synchronization on the Mailbox server named Mailbox01. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -63,7 +66,9 @@ Accept wildcard characters: False ``` ### -ForceFullSync -The ForceFullSync switch specifies whether to initiate a full edge synchronization. If you run the command without this switch, only changes since the last replication are synchronized. If you use this switch, the entire configuration information and recipient data are synchronized. +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. ```yaml Type: SwitchParameter @@ -78,8 +83,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ForceUpdatecookie -The ForceUpdateCookie switch specifies whether to force the Microsoft Exchange EdgeSync service to update the replication cookie even if it encounters an error. 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. +### -ForceUpdateCookie +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. ```yaml Type: SwitchParameter @@ -98,11 +105,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -154,33 +158,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ForceUpdatecookie -The ForceUpdateCookie switch specifies whether to force the Microsoft Exchange EdgeSync service to update the replication cookie even if it encounters an error. 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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Start-HistoricalSearch.md b/exchange/exchange-ps/exchange/Start-HistoricalSearch.md new file mode 100644 index 0000000000..598f93159b --- /dev/null +++ b/exchange/exchange-ps/exchange/Start-HistoricalSearch.md @@ -0,0 +1,497 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Start-HistoricalSearch + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Start-HistoricalSearch cmdlet to start a new historical search. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Start-HistoricalSearch -EndDate <DateTime> -ReportTitle <String> -ReportType <HistoricalSearchReportType> -StartDate <DateTime> + [-BlockStatus <String>] + [-CompressFile <Boolean>] + [-ConnectorType <String>] + [-DeliveryStatus <String>] + [-Direction <MessageDirection>] + [-DLPPolicy <MultiValuedProperty>] + [-EncryptionTemplate <String>] + [-EncryptionType <String>] + [-Locale <CultureInfo>] + [-MessageID <MultiValuedProperty>] + [-NetworkMessageID <MultiValuedProperty>] + [-NotifyAddress <MultiValuedProperty>] + [-OriginalClientIP <String>] + [-RecipientAddress <MultiValuedProperty>] + [-SenderAddress <MultiValuedProperty>] + [-SmtpSecurityError <String>] + [-TLSUsed <String>] + [-TransportRule <MultiValuedProperty>] + [-Url <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are aged between 1-4 hours (depending on your environment) and 90 days old. There is a limit of 250 historical searches that you can submit in a 24 hour period; you'll be warned if you're nearing the daily quota. Cancelled searches count against the daily quota. Also, in each CSV file there is a limit of 100000 results or lines. + +If you specify a distribution group, all messages might not be returned in the results. To ensure that all messages are returned, specify the individual recipient. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Start-HistoricalSearch -ReportTitle "Fabrikam Search" -StartDate 1/1/2023 -EndDate 1/7/2023 -ReportType MessageTrace -SenderAddress michelle@fabrikam.com -NotifyAddress chris@contoso.com +``` + +This example starts a new historical search named "Fabrikam Search" that has the following properties: + +- Date range: January 1 2023 to January 6 2023. Because we aren't specifying the time of day, the value 0:00 AM is used. In this example, the date range is equivalent to -StartDate "1/1/2023 0:00 AM" -EndDate "1/7/2023 0:00 AM" +- Report type: Message trace +- Sender address: michelle@fabrikam.com +- Internal notification email address: chris@contoso.com + +## PARAMETERS + +### -EndDate +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". + +If you don't specify the time of day, the default value 0:00 AM is used. For example, the value 12/31/2022 is really "12/31/2022 0:00 AM", which means no data from 12/31/2022 is included (only data from 12/30/2022 is included). + +You also need to use at least one of the following parameters in the command: MessageID, RecipientAddress, or SenderAddress. + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ReportTitle +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportType +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 +- ConnectorReport: Inbound/Outbound Message Report. +- DLP: Data Loss Prevention Report. +- MessageTrace: Message Trace Report. +- MessageTraceDetail: Message Trace Details Report. +- OutboundSecurityReport: Outbound Message in Transit Security Report. +- P2SenderAttribution: P2 Sender Attribution Report. +- SPAM: SPAM Detections Report. +- Spoof: Spoof Mail Report. +- TransportRule: Transport or Mail Flow Rules Report. +- UnifiedDLP: Unified Data Loss Prevention Report. + +You also need to use at least one of the following parameters in the command: MessageID, RecipientAddress, or SenderAddress. + +```yaml +Type: HistoricalSearchReportType +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartDate +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". + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -BlockStatus +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompressFile +{{ Fill CompressFile Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorType +The ConnectorType parameter filters the results in ConnectorReport reports by the connector type. Valid values are: + +- OnPremises +- Partner +- NoConnector + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeliveryStatus +The DeliveryStatus parameter filters the results by the delivery status of the message. You can use one of the following values: + +- Delivered +- Expanded +- Failed + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Direction +The Direction parameter filters the results by the direction of the message. Valid values are: + +- All: Incoming and outgoing messages. +- Received: Ingoing messages only. +- Sent: Outgoing messages only. + +```yaml +Type: MessageDirection +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DLPPolicy +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionTemplate +{{ Fill EncryptionTemplate Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EncryptionType +{{ Fill EncryptionType Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locale +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). + +```yaml +Type: CultureInfo +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageID +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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkMessageID +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotifyAddress +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**. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -OriginalClientIP +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecipientAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -SenderAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SmtpSecurityError +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TLSUsed +The TLSUsed parameter filters the results in ConnectorReport reports by the TLS version. Valid values are: + +- No Tls +- TLS1.2 +- TLS1.3 + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TransportRule +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Url +{{ Fill Url Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/Start-InformationBarrierPoliciesApplication.md b/exchange/exchange-ps/exchange/Start-InformationBarrierPoliciesApplication.md new file mode 100644 index 0000000000..2afb3f3ca7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Start-InformationBarrierPoliciesApplication.md @@ -0,0 +1,125 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Start-InformationBarrierPoliciesApplication + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Start-InformationBarrierPoliciesApplication cmdlet to apply active information barrier policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Start-InformationBarrierPoliciesApplication [[-Identity] <PolicyIdParameter>] + [-CleanupGroupSegmentLink] + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Start-InformationBarrierPoliciesApplication +``` + +This applies all active information barrier policies. + +## PARAMETERS + +### -Identity +This parameter is reserved for internal Microsoft use. + +```yaml +Type: PolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -CleanupGroupSegmentLink +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/Start-MailboxAssistant.md b/exchange/exchange-ps/exchange/Start-MailboxAssistant.md new file mode 100644 index 0000000000..52a05e9bcb --- /dev/null +++ b/exchange/exchange-ps/exchange/Start-MailboxAssistant.md @@ -0,0 +1,182 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- +# Start-MailboxAssistant + +## SYNOPSIS +This cmdlet is available only in Exchange Server 2019 in Cumulative Update 11 (CU11) or later. + +Use the Start-MailboxAssistant cmdlet to start processing of a mailbox by the specified assistant. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Start-MailboxAssistant [-Identity] <UserIdParameter> -AssistantName <String> + [-Confirm] + [-DomainController <Fqdn>] + [-Parameters <String>] + [-SoftDeletedMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Start-MailboxAssistant -Identity "Chris" -AssistantName BigFunnelRetryFeederTimeBasedAssistant +``` + +This example starts the `BigFunnelRetryFeederTimeBasedAssistant` assistant and lets it process the mailbox of the user "Chris". The assistant indexes the mailbox items that were not indexed previously. + +**Note**: You first need to create a setting override as described in [Incomplete search results after installing an Exchange Server 2019 update](https://support.microsoft.com/topic/incomplete-search-results-after-installing-an-exchange-server-2019-update-96ae2ef0-4569-4327-8d0c-8a3c1abdc1f6). + +## PARAMETERS + +### -Identity +The Identity parameter specifies the user whose mailbox should be processed by the Mailbox Assistant. Valid values are: + +- Distinguished name (DN) +- SamAccountName +- User ID or user principal name (UPN) + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AssistantName +The AssistantName parameter specifies the assistant that should process the mailbox. Valid values are: + +- BigFunnelRetryFeederTimeBasedAssistant + +Values are case sensitive. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Parameters +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SoftDeletedMailbox +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-MailboxSearch.md b/exchange/exchange-ps/exchange/Start-MailboxSearch.md similarity index 83% rename from exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-MailboxSearch.md rename to exchange/exchange-ps/exchange/Start-MailboxSearch.md index 6c90bc1c41..a84f5ccd78 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-MailboxSearch.md +++ b/exchange/exchange-ps/exchange/Start-MailboxSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/start-mailboxsearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Start-MailboxSearch @@ -17,13 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Start-MailboxSearch cmdlet to restart or resume a mailbox search that's been stopped. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +**Note**: As of October 2020, the \*-MailboxSearch cmdlets are retired in Exchange Online PowerShell. Use the \*-ComplianceSearch cmdlets in Security & Compliance PowerShell instead. For more information, see [Retirement of legacy eDiscovery tools](https://learn.microsoft.com/purview/ediscovery-legacy-retirement). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Start-MailboxSearch [-Identity] <SearchObjectIdParameter> [-Confirm] [-DomainController <Fqdn>] [-Force] - [-Resume] [-WhatIf] [-StatisticsStartIndex <Int32>] [<CommonParameters>] +Start-MailboxSearch [-Identity] <SearchObjectIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-Force] + [-Resume] + [-StatisticsStartIndex <Int32>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -33,9 +40,9 @@ When restarting a search, any previous results returned by the same search and c In Exchange 2013 or later, mailbox searches are also used for In-Place Hold. However, you can't start or stop In-Place Hold using the Start-MailboxSearch and Stop-MailboxSearch cmdlets. -For more details, see [In-Place Hold and Litigation Hold in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/holds/holds) and [In-Place eDiscovery in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). +For more details, see [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds) and [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -103,7 +109,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -136,14 +144,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -StatisticsStartIndex +The StatisticsStartIndex parameter is used by the EAC to retrieve keyword statistics in a paged operation. ```yaml -Type: SwitchParameter +Type: Int32 Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -152,14 +160,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -StatisticsStartIndex -The StatisticsStartIndex parameter is used by the EAC to retrieve keyword statistics in a paged operation. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: Int32 +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -173,12 +181,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Start-ManagedFolderAssistant.md b/exchange/exchange-ps/exchange/Start-ManagedFolderAssistant.md new file mode 100644 index 0000000000..2e90b4cf4d --- /dev/null +++ b/exchange/exchange-ps/exchange/Start-ManagedFolderAssistant.md @@ -0,0 +1,424 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Start-ManagedFolderAssistant + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Start-ManagedFolderAssistant cmdlet to immediately start messaging records management (MRM) processing of mailboxes that you specify. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Identity (Default) +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-HoldCleanup] + [-AggMailboxCleanup] + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] +``` + +### ComplianceBoundaryAssistantParameterSet +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-AdaptiveScope] + [-AggMailboxCleanup] + [-Confirm] + [-FullCrawl] + [-InactiveMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +### ComplianceJobAssistantParameterSet +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-ComplianceJob] + [-AggMailboxCleanup] + [-Confirm] + [-FullCrawl] + [-InactiveMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +### DataGovernanceAssistantParameterSet +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-DataGovernance] + [-AggMailboxCleanup] + [-Confirm] + [-FullCrawl] + [-InactiveMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +### ElcB2DumpsterArchiverAssistantParameterSet +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-B2DumpsterArchiver] + [-AggMailboxCleanup] + [-Confirm] + [-FullCrawl] + [-InactiveMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +### ElcB2IPMArchiverAssistantParameterSet +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-B2IPMArchiver] + [-AggMailboxCleanup] + [-Confirm] + [-FullCrawl] + [-InactiveMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +### HoldCleanupParameterSet +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-HoldCleanup] + [-AggMailboxCleanup] + [-Confirm] + [-FullCrawl] + [-InactiveMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +### StopHoldCleanupParameterSet +``` +Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-StopHoldCleanup] + [-AggMailboxCleanup] + [-Confirm] + [-FullCrawl] + [-InactiveMailbox] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The Managed Folder Assistant uses the retention policy settings of users' mailboxes to process retention of items. This mailbox processing occurs automatically. You can use the Start-ManagedFolderAssistant cmdlet to immediately start processing the specified mailbox. + +In Exchange Server 2010 release to manufacturing (RTM), the Identity parameter specifies the Mailbox server to start the assistant and process all mailboxes on that server, and the Mailbox parameter specifies the mailbox to process. In Exchange 2010 Service Pack 1 (SP1) and later, the Mailbox parameter has been removed, and the Identity parameter accepts the mailbox or mail user to process. + +If you use these parameters in scheduled commands or scripts, we recommend that you review them and make any necessary changes. + +For more information, see [KB4032361](https://support.microsoft.com/help/4032361). + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Start-ManagedFolderAssistant -Identity "Chris" +``` + +This example processes the mailbox for a user with the alias Chris. + +### Example 2 +```powershell +Get-Mailbox -Anr Chr -DomainController DC01 | Start-ManagedFolderAssistant +``` + +This example uses the Get-Mailbox command to retrieve all the mailboxes that resolve from the ambiguous name resolution (ANR) search on the string "Chr" in the domain DC01 (for example, users such as Chris Ashton, Christian Hess, and Christa Geller), and the results are piped to the Start-ManagedFolderAssistant cmdlet for processing. + +## PARAMETERS + +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +**Note**: In the cloud-based service, if you receive an error, try using the mailbox GUID for the value of this parameter. You can get the mailbox GUID value by replacing \<UserIdentity\> with the email address of the user and running the following command: `Get-Mailbox -User <UserIdentity> | Format-List *GUID,MailboxLocations`. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -AdaptiveScope +This parameter is available only in the cloud-based service. + +{{ Fill AdaptiveScope Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: ComplianceBoundaryAssistantParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AggMailboxCleanup +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -B2DumpsterArchiver +This parameter is available only in the cloud-based service. + +{{ Fill B2DumpsterArchiver Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: ElcB2DumpsterArchiverAssistantParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -B2IPMArchiver +This parameter is available only in the cloud-based service. + +{{ Fill B2IPMArchiver Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: ElcB2IPMArchiverAssistantParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceJob +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: ComplianceJobAssistantParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DataGovernance +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: DataGovernanceAssistantParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FullCrawl +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. + +```yaml +Type: SwitchParameter +Parameter Sets: ComplianceBoundaryAssistantParameterSet, ComplianceJobAssistantParameterSet, DataGovernanceAssistantParameterSet, ElcB2DumpsterArchiverAssistantParameterSet, ElcB2IPMArchiverAssistantParameterSet, HoldCleanupParameterSet, StopHoldCleanupParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HoldCleanup +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InactiveMailbox +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. + +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. + +When you use this switch, items aren't moved from the inactive mailbox to the archive mailbox. + +```yaml +Type: SwitchParameter +Parameter Sets: ComplianceBoundaryAssistantParameterSet, ComplianceJobAssistantParameterSet, DataGovernanceAssistantParameterSet, ElcB2DumpsterArchiverAssistantParameterSet, ElcB2IPMArchiverAssistantParameterSet, HoldCleanupParameterSet, StopHoldCleanupParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StopHoldCleanup +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. + +A hold clean-up command will run until it completely scans the Recoverable Items folder for duplicate versions of items (it even continues after an interruption). In some cases, the hold clean-up command gets stuck, which can block other regular MRM tasks on the mailbox (for example, expiring items). The StopHoldCleanup switch tells MRM to abandon the stuck hold clean-up task so that regular tasks can continue. + +```yaml +Type: SwitchParameter +Parameter Sets: StopHoldCleanupParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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 + +[Export-MailboxDiagnosticLogs](https://learn.microsoft.com/powershell/module/exchange/Export-MailboxDiagnosticLogs) diff --git a/exchange/exchange-ps/exchange/move-and-migration/Start-MigrationBatch.md b/exchange/exchange-ps/exchange/Start-MigrationBatch.md similarity index 88% rename from exchange/exchange-ps/exchange/move-and-migration/Start-MigrationBatch.md rename to exchange/exchange-ps/exchange/Start-MigrationBatch.md index 9a52339e41..cf1d3e9731 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Start-MigrationBatch.md +++ b/exchange/exchange-ps/exchange/Start-MigrationBatch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/start-migrationbatch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Start-MigrationBatch @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Start-MigrationBatch cmdlet to start a move request or migration batch that was created with the New-MigrationBatch cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Start-MigrationBatch [[-Identity] <MigrationBatchIdParameter>] [-DomainController <Fqdn>] [-Partition <MailboxIdParameter>] [-Validate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -37,7 +37,7 @@ The Start-MigrationBatch cmdlet also will resume a Stopped migration batch or re In the cloud-based service, the Start-MigrationBatch cmdlet can be run at any time to retry failed users within the batch. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,11 +50,26 @@ This example starts the migration batch SEM1. ## PARAMETERS +### -Identity +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -88,22 +103,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Partition This parameter is available only in the cloud-based service. @@ -123,13 +122,17 @@ Accept wildcard characters: False ``` ### -Validate -The Validate parameter specifies whether to start the migration batch in the validation stage of the migration process. If you include this parameter, the migration performs a validation check of the mailboxes in the batch. +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. + +If you use this switch, the migration performs a validation check of the mailboxes in the batch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -159,12 +162,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Start-MigrationUser.md b/exchange/exchange-ps/exchange/Start-MigrationUser.md new file mode 100644 index 0000000000..be88fe1878 --- /dev/null +++ b/exchange/exchange-ps/exchange/Start-MigrationUser.md @@ -0,0 +1,144 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Start-MigrationUser + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Start-MigrationUser cmdlet to start the migration of a user in an existing migration batch. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Start-MigrationUser [[-Identity] <MigrationUserIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Start-MigrationUser -Identity laura@contoso.com +``` + +This example starts the migration of the user named laura@contoso.com + +## PARAMETERS + +### -Identity +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. + +```yaml +Type: MigrationUserIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Partition +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Start-RetentionAutoTagLearning.md b/exchange/exchange-ps/exchange/Start-RetentionAutoTagLearning.md similarity index 86% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Start-RetentionAutoTagLearning.md rename to exchange/exchange-ps/exchange/Start-RetentionAutoTagLearning.md index 04083ed4c7..3ad1a2652d 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Start-RetentionAutoTagLearning.md +++ b/exchange/exchange-ps/exchange/Start-RetentionAutoTagLearning.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/start-retentionautotaglearning +online version: https://learn.microsoft.com/powershell/module/exchange/start-retentionautotaglearning applicable: Exchange Server 2010 title: Start-RetentionAutoTagLearning schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Start-RetentionAutoTagLearning @@ -17,30 +16,36 @@ This cmdlet is available only in Exchange Server 2010. Use the Start-RetentionAutoTagLearning cmdlet to start auto-tagging for a specified mailbox or to cross-validate auto-tagging results for the mailbox. -Messaging records management (MRM) must be configured before the Start-RetentionAutoTagLearning cmdlet can be used. For more information, see [Understanding Retention Tags and Retention Policies](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/dd297955(v=exchg.141)). +Messaging records management (MRM) must be configured before the Start-RetentionAutoTagLearning cmdlet can be used. For more information, see [Understanding Retention Tags and Retention Policies](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd297955(v=exchg.141)). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### CrossValidate ``` -Start-RetentionAutoTagLearning [-Identity] <MailboxIdParameter> [-CrossValidate] [-NumberOfSegments <Int32>] +Start-RetentionAutoTagLearning [-Identity] <MailboxIdParameter> + [-CrossValidate] + [-NumberOfSegments <Int32>] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Train ``` -Start-RetentionAutoTagLearning [-Identity] <MailboxIdParameter> [-Clear] [-Train] +Start-RetentionAutoTagLearning [-Identity] <MailboxIdParameter> + [-Clear] + [-Train] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,43 +72,18 @@ This example sets user Joe Healy's mailbox to clear all retention policy tags as ## PARAMETERS -### -CrossValidate -The CrossValidate switch specifies whether items in the specified mailbox are being auto-tagged. - -```yaml -Type: SwitchParameter -Parameter Sets: CrossValidate -Aliases: -Applicable: Exchange Server 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity The Identity parameter identifies the mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -119,8 +99,24 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -CrossValidate +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Clear -The Clear switch specifies whether to clear auto-tags from the specified mailbox. +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 @@ -138,8 +134,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -194,7 +189,9 @@ Accept wildcard characters: False ``` ### -Train -The Train switch specifies whether to start the training algorithm for auto-tagging on the specified mailbox. This switch is especially useful for retraining. No values are required with this switch. +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. ```yaml Type: SwitchParameter @@ -230,12 +227,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Stop-ComplianceSearch.md b/exchange/exchange-ps/exchange/Stop-ComplianceSearch.md new file mode 100644 index 0000000000..a0b52107ee --- /dev/null +++ b/exchange/exchange-ps/exchange/Stop-ComplianceSearch.md @@ -0,0 +1,117 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Stop-ComplianceSearch + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Stop-ComplianceSearch cmdlet to stop running compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Stop-ComplianceSearch [-Identity] <ComplianceSearchIdParameter> + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Stop-ComplianceSearch -Identity "Case 1234" +``` + +This example stops the active compliance search named Case 1234 + +## PARAMETERS + +### -Identity +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: + +- Name +- JobRunId (GUID) + +You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status + +```yaml +Type: ComplianceSearchIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Stop-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/Stop-DatabaseAvailabilityGroup.md similarity index 89% rename from exchange/exchange-ps/exchange/database-availability-groups/Stop-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/exchange/Stop-DatabaseAvailabilityGroup.md index 8b03f86ea5..c9f3ae6135 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Stop-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/exchange/Stop-DatabaseAvailabilityGroup.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/stop-databaseavailabilitygroup +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Stop-DatabaseAvailabilityGroup @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Stop-DatabaseAvailabilityGroup cmdlet to mark a member of a database availability group (DAG) as failed, or to mark all DAG members in a specific Active Directory site as failed. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,7 +26,8 @@ Stop-DatabaseAvailabilityGroup [-Identity] <DatabaseAvailabilityGroupIdParameter [-ConfigurationOnly] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### MailboxSet @@ -36,13 +36,14 @@ Stop-DatabaseAvailabilityGroup [-Identity] <DatabaseAvailabilityGroupIdParameter [-ConfigurationOnly] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Stop-DatabaseAvailabilityGroup cmdlet is used during a datacenter switchover. This cmdlet is used to mark one or members of the DAG as failed (also known as stopped).The Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of DagOnly. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,33 +70,33 @@ This example stops the Mailbox server MBX3, which is currently offline, in the D ## PARAMETERS -### -ActiveDirectorySite -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). +### -Identity +The Identity parameter specifies the name of the DAG being stopped. ```yaml -Type: AdSiteIdParameter -Parameter Sets: Identity +Type: DatabaseAvailabilityGroupIdParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name of the DAG being stopped. +### -ActiveDirectorySite +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: DatabaseAvailabilityGroupIdParameter -Parameter Sets: (All) +Type: AdSiteIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False @@ -118,7 +119,9 @@ Accept wildcard characters: False ``` ### -ConfigurationOnly -The ConfigurationOnly parameter updates the Active Directory properties with the stop action, but doesn't perform a stop of the DAG or any members. This parameter must be used when the DAG member servers are offline, but Active Directory is up and accessible in the primary datacenter. +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. ```yaml Type: SwitchParameter @@ -136,8 +139,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -190,12 +192,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Stop-HistoricalSearch.md b/exchange/exchange-ps/exchange/Stop-HistoricalSearch.md similarity index 79% rename from exchange/exchange-ps/exchange/mail-flow/Stop-HistoricalSearch.md rename to exchange/exchange-ps/exchange/Stop-HistoricalSearch.md index ccb85eb11d..314339dd93 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Stop-HistoricalSearch.md +++ b/exchange/exchange-ps/exchange/Stop-HistoricalSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/stop-historicalsearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Stop-HistoricalSearch @@ -17,15 +16,13 @@ This cmdlet is available only in the cloud-based service. Use the Stop-HistoricalSearch cmdlet to stop an existing historical search that has a status value of NotStarted. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Stop-HistoricalSearch -JobId <Guid> [<CommonParameters>] +Stop-HistoricalSearch -JobId <Guid> + [<CommonParameters>] ``` ## DESCRIPTION @@ -33,7 +30,7 @@ A historical search provides message trace and report details in a comma-separat After you start a historical search by using the Start-HistoricalSearch cmdlet, the search is queued, but not actually running. While the search is queued and has the status value of NotStarted, you can use the Stop-HistoricalSearch cmdlet to stop it. After the search is actively running, and has a status value of InProgress, you can't stop it. When you stop a historical search, it's given a status value of Cancelled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,12 +64,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Stop-InformationBarrierPoliciesApplication.md b/exchange/exchange-ps/exchange/Stop-InformationBarrierPoliciesApplication.md new file mode 100644 index 0000000000..00b91d2c2c --- /dev/null +++ b/exchange/exchange-ps/exchange/Stop-InformationBarrierPoliciesApplication.md @@ -0,0 +1,108 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Stop-InformationBarrierPoliciesApplication + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Stop-InformationBarrierPoliciesApplication cmdlet to stop the process of applying information barrier policies in the Microsoft Purview compliance portal. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Stop-InformationBarrierPoliciesApplication [-Identity] <PolicyIdParameter> + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +InformationBarrierPoliciesApplication -Identity 46237888-12ca-42e3-a541-3fcb7b5231d1 +``` + +This example stops the application of information barrier policies per the policy application with the specified Identity value. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies) + +[Edit (or remove) information barrier policies](https://learn.microsoft.com/purview/information-barriers-edit-segments-policies) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Stop-MailboxSearch.md b/exchange/exchange-ps/exchange/Stop-MailboxSearch.md similarity index 84% rename from exchange/exchange-ps/exchange/policy-and-compliance-content-search/Stop-MailboxSearch.md rename to exchange/exchange-ps/exchange/Stop-MailboxSearch.md index 6198c9da3a..b78b8cb8b3 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Stop-MailboxSearch.md +++ b/exchange/exchange-ps/exchange/Stop-MailboxSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/stop-mailboxsearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Stop-MailboxSearch @@ -17,19 +16,24 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Stop-MailboxSearch cmdlet to stop a mailbox search that's in progress. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +**Note**: As of October 2020, the \*-MailboxSearch cmdlets are retired in Exchange Online PowerShell. Use the \*-ComplianceSearch cmdlets in Security & Compliance PowerShell instead. For more information, see [Retirement of legacy eDiscovery tools](https://learn.microsoft.com/purview/ediscovery-legacy-retirement). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Stop-MailboxSearch [-Identity] <SearchObjectIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] +Stop-MailboxSearch [-Identity] <SearchObjectIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION -In Microsoft Exchange, mailbox searches are used for In-Place eDiscovery and In-Place Hold. You can start and stop a mailbox search. For more information, see [In-Place eDiscovery in Exchange Server](https://docs.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). +In Microsoft Exchange, mailbox searches are used for In-Place eDiscovery and In-Place Hold. You can start and stop a mailbox search. For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,12 +120,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Stop-ManagedFolderAssistant.md b/exchange/exchange-ps/exchange/Stop-ManagedFolderAssistant.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance-retention/Stop-ManagedFolderAssistant.md rename to exchange/exchange-ps/exchange/Stop-ManagedFolderAssistant.md index 96e87b2d89..0b03abf051 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Stop-ManagedFolderAssistant.md +++ b/exchange/exchange-ps/exchange/Stop-ManagedFolderAssistant.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/stop-managedfolderassistant +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Stop-ManagedFolderAssistant @@ -17,19 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Stop-ManagedFolderAssistant cmdlet to immediately stop messaging records management (MRM) from processing users' mailboxes on the specified servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Stop-ManagedFolderAssistant [[-Identity] <ServerIdParameter>] [-Confirm] [-DomainController <Fqdn>] [-WhatIf] +Stop-ManagedFolderAssistant [[-Identity] <ServerIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION The Managed Folder Assistant uses the managed folder mailbox policy settings of users to process mailbox items for retention and journaling as needed. Use the Stop-ManagedFolderAssistant cmdlet to stop the Managed Folder Assistant as soon as processing of the current mailbox is completed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -49,33 +51,39 @@ This example stops the Managed Folder Assistant on the servers ExchSrvr1 and Exc ## PARAMETERS -### -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. +### -Identity +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: -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Name +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +If you don't use this parameter, the command is run on the local server. ```yaml -Type: SwitchParameter +Type: ServerIdParameter Parameter Sets: (All) -Aliases: cf +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: Fqdn +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -85,29 +93,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN - -If you don't use this parameter, the command is run on the local server. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: ServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -132,12 +130,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationBatch.md b/exchange/exchange-ps/exchange/Stop-MigrationBatch.md similarity index 84% rename from exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationBatch.md rename to exchange/exchange-ps/exchange/Stop-MigrationBatch.md index d27ef435dd..2c68616341 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationBatch.md +++ b/exchange/exchange-ps/exchange/Stop-MigrationBatch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/stop-migrationbatch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Stop-MigrationBatch @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Stop-MigrationBatch cmdlet to stop the processing of a migration batch that's in progress. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,13 +25,14 @@ Stop-MigrationBatch [[-Identity] <MigrationBatchIdParameter>] [-Confirm] [-DomainController <Fqdn>] [-Partition <MailboxIdParameter>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -The Stop-MigrationBatch cmdlet stops the migration batch that's being processed in your on-premises Exchange organization or by the cloud-based migration service running in Microsoft Office 365. You can only stop migration batches that have mailboxes that are still in the process of being migrated or are waiting to be migrated. Stopping a migration won't affect mailboxes that have been migrated already. The migration of mailboxes that are being actively migrated is stopped immediately. If all migration requests in a migration batch are completed or failed, this cmdlet won't run. +The Stop-MigrationBatch cmdlet stops the migration batch that's being processed in your on-premises Exchange organization or by the cloud-based migration service running in Microsoft 365. You can only stop migration batches that have mailboxes that are still in the process of being migrated or are waiting to be migrated. Stopping a migration won't affect mailboxes that have been migrated already. The migration of mailboxes that are being actively migrated is stopped immediately. If all migration requests in a migration batch are completed or failed, this cmdlet won't run. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -71,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -145,12 +144,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Stop-MigrationUser.md b/exchange/exchange-ps/exchange/Stop-MigrationUser.md new file mode 100644 index 0000000000..ccaca8fe4d --- /dev/null +++ b/exchange/exchange-ps/exchange/Stop-MigrationUser.md @@ -0,0 +1,144 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Stop-MigrationUser + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Stop-MigrationUser cmdlet to stop the migration of a user in an existing migration batch. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Stop-MigrationUser [[-Identity] <MigrationUserIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Stop-MigrationUser -Identity laura@contoso.com +``` + +This example stops the migration of the user laura@contoso.com. + +## PARAMETERS + +### -Identity +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. + +```yaml +Type: MigrationUserIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Partition +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Suspend-MailboxDatabaseCopy.md b/exchange/exchange-ps/exchange/Suspend-MailboxDatabaseCopy.md similarity index 90% rename from exchange/exchange-ps/exchange/database-availability-groups/Suspend-MailboxDatabaseCopy.md rename to exchange/exchange-ps/exchange/Suspend-MailboxDatabaseCopy.md index 7a5acdea5d..bbd7d1ecfa 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Suspend-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/exchange/Suspend-MailboxDatabaseCopy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/suspend-mailboxdatabasecopy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Suspend-MailboxDatabaseCopy @@ -17,28 +16,33 @@ This cmdlet is available only in on-premises Exchange. Use the Suspend-MailboxDatabaseCopy cmdlet to block replication and replay activities (log copying and replay) or activation for a database configured with two or more database copies. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### EnableReplayLag ``` -Suspend-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> [-EnableReplayLag] +Suspend-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> + [-EnableReplayLag] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Identity ``` -Suspend-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> [-ActivationOnly] [-SuspendComment <String>] +Suspend-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> + [-ActivationOnly] + [-SuspendComment <String>] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -75,7 +79,7 @@ Accept wildcard characters: False ``` ### -ActivationOnly -The ActivationOnly switch specifies whether to suspend only activation for the mailbox database copy. +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 @@ -93,8 +97,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,6 +129,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnableReplayLag +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -SuspendComment The SuspendComment parameter specifies the reason that the database copy is being suspended. This parameter is limited to 512 characters. @@ -158,33 +177,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -EnableReplayLag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxExportRequest.md b/exchange/exchange-ps/exchange/Suspend-MailboxExportRequest.md similarity index 88% rename from exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxExportRequest.md rename to exchange/exchange-ps/exchange/Suspend-MailboxExportRequest.md index de3c3663a7..5f063c4f44 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxExportRequest.md +++ b/exchange/exchange-ps/exchange/Suspend-MailboxExportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/suspend-mailboxexportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Suspend-MailboxExportRequest @@ -17,19 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Suspend-MailboxExportRequest cmdlet to suspend an export request any time after the request was created, but before the request reaches the status of Completed. You can resume the request by using the Resume-MailboxExportRequest cmdlet. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Suspend-MailboxExportRequest [-Identity] <MailboxExportRequestIdParameter> [-Confirm] - [-DomainController <Fqdn>] [-SuspendComment <String>] [-WhatIf] [<CommonParameters>] +Suspend-MailboxExportRequest [-Identity] <MailboxExportRequestIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-SuspendComment <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,7 +53,7 @@ This example suspends all export requests that are in progress by using the Get- ## PARAMETERS ### -Identity -The Identity parameter specifies the identity of the export request. By default, export requests are named \<alias\>\\MailboxExportX (where X = 0-9). Use the following syntax: \<alias\>\\\<name\>. +The Identity parameter specifies the identity of the export request. By default, export requests are named `<alias>\MailboxExportX` (where X = 0-9). Use the following syntax: `Alias\Name`. ```yaml Type: MailboxExportRequestIdParameter @@ -68,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -138,12 +140,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxImportRequest.md b/exchange/exchange-ps/exchange/Suspend-MailboxImportRequest.md similarity index 86% rename from exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxImportRequest.md rename to exchange/exchange-ps/exchange/Suspend-MailboxImportRequest.md index 6a1bd19bc5..41e44b0123 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxImportRequest.md +++ b/exchange/exchange-ps/exchange/Suspend-MailboxImportRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/suspend-mailboximportrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Suspend-MailboxImportRequest @@ -17,19 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Suspend-MailboxImportRequest cmdlet to suspend an import request any time after the request was created, but before the request reaches the status of Completed. You can resume the move request by using the Resume-MailboxImportRequest cmdlet. -This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). +NOTE: This cmdlet is no longer supported in Exchange Online. To import a .pst file in Exchange Online, see [Use network upload to import PST files](https://learn.microsoft.com/purview/use-network-upload-to-import-pst-files). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export 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). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Suspend-MailboxImportRequest [-Identity] <MailboxImportRequestIdParameter> [-Confirm] - [-DomainController <Fqdn>] [-SuspendComment <String>] [-WhatIf] [<CommonParameters>] +Suspend-MailboxImportRequest [-Identity] <MailboxImportRequestIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-SuspendComment <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,7 +55,7 @@ This example suspends all import requests that are in progress by using the Get- ## PARAMETERS ### -Identity -The Identity parameter specifies the identity of the import request. By default, import requests are named \<alias\>\\MailboxImportX (where X = 0-9). If you created the request by using the Name parameter, use the following syntax: \<alias\>\\\<name\>. +The Identity parameter specifies the identity of the import request. By default, import requests are named `<alias>\MailboxImportX` (where X = 0-9). If you created the request by using the Name parameter, use the following syntax: `Alias\Name`. ```yaml Type: MailboxImportRequestIdParameter @@ -68,8 +73,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -140,12 +144,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/Suspend-MailboxRestoreRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxRestoreRequest.md rename to exchange/exchange-ps/exchange/Suspend-MailboxRestoreRequest.md index 799e6e307d..ca7cdcbde0 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Suspend-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/exchange/Suspend-MailboxRestoreRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/suspend-mailboxrestorerequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Suspend-MailboxRestoreRequest @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Suspend-MailboxRestoreRequest cmdlet to suspend a restore request any time after the request was created, but before the request reaches the status of Completed. You can resume the restore request by using the Resume-MailboxRestoreRequest cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Suspend-MailboxRestoreRequest [-Identity] <MailboxRestoreRequestIdParameter> [-Confirm] - [-DomainController <Fqdn>] [-SuspendComment <String>] [-WhatIf] [<CommonParameters>] +Suspend-MailboxRestoreRequest [-Identity] <MailboxRestoreRequestIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-SuspendComment <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +51,7 @@ This example suspends all restore requests that are in progress by using the Get ## PARAMETERS ### -Identity -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\>. +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). @@ -68,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -140,12 +142,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Suspend-Message.md b/exchange/exchange-ps/exchange/Suspend-Message.md similarity index 82% rename from exchange/exchange-ps/exchange/mail-flow/Suspend-Message.md rename to exchange/exchange-ps/exchange/Suspend-Message.md index 131a567c67..e978e8d3de 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Suspend-Message.md +++ b/exchange/exchange-ps/exchange/Suspend-Message.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/suspend-message +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Suspend-Message @@ -17,32 +16,35 @@ This cmdlet is available only in on-premises Exchange. Use the Suspend-Message cmdlet to prevent delivery of a particular message in a queue on a Mailbox server or an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Filter ``` -Suspend-Message -Filter <String> [-Server <ServerIdParameter>] +Suspend-Message -Filter <String> + [-Server <ServerIdParameter>] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Identity ``` Suspend-Message [-Identity] <MessageIdentity> [-Confirm] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -A message already in delivery won't be suspended. Delivery will continue and the message status will be PendingSuspend. If the delivery fails, the message will re-enter the queue and it will then be suspended. You can't suspend a message that's in the Submission queue or poison message queue. +A message already in delivery won't be suspended. Delivery will continue and the message status will be PendingSuspend. If the delivery fails, the message will re-enter the queue and it will then be suspended. You can't suspend a message that's in the poison message queue. A message being sent to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is suspended in a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To suspend a message in more than one queue in a single operation, you must use the Filter parameter. -For instructions on how to resume a suspended message, see [Resume-Message](https://docs.microsoft.com/powershell/module/exchange/mail-flow/resume-message). +For instructions on how to resume a suspended message, see [Resume-Message](https://learn.microsoft.com/powershell/module/exchange/resume-message). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,50 +56,48 @@ Suspend-Message -Server Server1 -Filter "FromAddress -eq 'kweku@contoso.com'" This example prevents delivery of all messages for which the following conditions are true: - The messages are sent by the sender kweku@contoso.com. - - The messages are queued on the server Server1. ## PARAMETERS -### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.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 ("). +### -Identity +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: String -Parameter Sets: Filter +Type: MessageIdentity +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity). +### -Filter +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 ("). ```yaml -Type: MessageIdentity -Parameter Sets: Identity +Type: String +Parameter Sets: Filter Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -117,11 +117,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -162,12 +159,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Suspend-MoveRequest.md b/exchange/exchange-ps/exchange/Suspend-MoveRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/move-and-migration/Suspend-MoveRequest.md rename to exchange/exchange-ps/exchange/Suspend-MoveRequest.md index c6615e08b5..852bd02d0b 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Suspend-MoveRequest.md +++ b/exchange/exchange-ps/exchange/Suspend-MoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/suspend-moverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Suspend-MoveRequest @@ -17,17 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Suspend-MoveRequest cmdlet to suspend a move request any time after the move request was created, but before it reaches the status of CompletionInProgress. You can resume the move request by using the Resume-MoveRequest cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Suspend-MoveRequest [-Identity] <MoveRequestIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-SuspendComment <String>] [-WhatIf] [-ProxyToMailbox <MailboxIdParameter>] [<CommonParameters>] +Suspend-MoveRequest [-Identity] <MoveRequestIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-ProxyToMailbox <MailboxIdParameter>] + [-SuspendComment <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -51,17 +55,11 @@ This example suspends all move requests that are in progress by using the Get-Mo The Identity parameter specifies the identity of the mailbox or mail user. You can use one of the following values: - GUID - - Distinguished Name (DN) - - Domain\\Account - - User principal name (UPN) - - LegacyExchangeDN - - SMTP address - - Alias ```yaml @@ -80,8 +78,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,14 +112,27 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -SuspendComment -The SuspendComment parameter specifies a description as to why the request was suspended. +### -ProxyToMailbox +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: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) ```yaml -Type: String +Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: False Position: Named @@ -131,13 +141,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -SuspendComment +The SuspendComment parameter specifies a description as to why the request was suspended. ```yaml -Type: SwitchParameter +Type: String Parameter Sets: (All) -Aliases: wi +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False @@ -147,36 +157,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ProxyToMailbox -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: MailboxIdParameter +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Online +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -190,12 +178,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/exchange/Suspend-PublicFolderMailboxMigrationRequest.md similarity index 86% rename from exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMailboxMigrationRequest.md rename to exchange/exchange-ps/exchange/Suspend-PublicFolderMailboxMigrationRequest.md index 5dadfb1130..6e8a63fbb7 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Suspend-PublicFolderMailboxMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/suspend-publicfoldermailboxmigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Suspend-PublicFolderMailboxMigrationRequest @@ -17,17 +16,21 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Suspend-PublicFolderMailboxMigrationRequest cmdlet to suspend individual jobs in public folder migration batches that were created by using the New-MigrationBatch cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Suspend-PublicFolderMailboxMigrationRequest [-Identity] <PublicFolderMailboxMigrationRequestIdParameter> - [-Confirm] [-DomainController <Fqdn>] [-SuspendComment <String>] [-WhatIf] [<CommonParameters>] + [-Confirm] + [-DomainController <Fqdn>] + [-SuspendComment <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -41,7 +44,7 @@ This example suspends the specified public folder mailbox migration request. ## PARAMETERS ### -Identity -The Identity parameter specifies the public folder mailbox migration request that you want to suspend. This value uses the syntax \\PublicFolderMailboxMigration\<GUID\> (for example, \\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e). +The Identity parameter specifies the public folder mailbox migration request that you want to suspend. This value uses the syntax `\PublicFolderMailboxMigration<GUID>` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`). ```yaml Type: PublicFolderMailboxMigrationRequestIdParameter @@ -59,8 +62,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -131,12 +133,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/Suspend-PublicFolderMigrationRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/exchange/Suspend-PublicFolderMigrationRequest.md index 4c77d438af..824fe531ac 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/exchange/Suspend-PublicFolderMigrationRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/suspend-publicfoldermigrationrequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Suspend-PublicFolderMigrationRequest @@ -19,7 +18,7 @@ Use the Suspend-PublicFolderMigrationRequest cmdlet to suspend serial public fol **Note**: Support for serial migration of public folders ended in Exchange 2013 Cumulative Update 8 (CU8), and the cmdlets are no longer available in Exchange Online. Instead, use the corresponding **\*-MigrationBatch** and **\*-PublicFolderMailboxMigration\*** cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,11 +27,12 @@ Suspend-PublicFolderMigrationRequest [-Identity] <PublicFolderMigrationRequestId [-Confirm] [-DomainController <Fqdn>] [-SuspendComment <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,7 +56,6 @@ This example suspends all migration requests that are in progress by using the G The Identity parameter specifies the migration request that you want to suspend. You can use the following values: - Name - - RequestGUID ```yaml @@ -75,8 +74,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -145,12 +143,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/Suspend-PublicFolderMoveRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMoveRequest.md rename to exchange/exchange-ps/exchange/Suspend-PublicFolderMoveRequest.md index ca9d9cf11c..fc298d21c8 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Suspend-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/exchange/Suspend-PublicFolderMoveRequest.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/suspend-publicfoldermoverequest +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Suspend-PublicFolderMoveRequest @@ -17,17 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Suspend-PublicFolderMoveRequest cmdlet to suspend a move request any time after the move request was created, but before it reaches the status of CompletionInProgress. You can resume the move request by using the Resume-PublicFolderMoveRequest cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Suspend-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter> [-Confirm] - [-DomainController <Fqdn>] [-SuspendComment <String>] [-WhatIf] [<CommonParameters>] +Suspend-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-SuspendComment <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,8 +62,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -129,12 +131,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Suspend-PublicFolderReplication.md b/exchange/exchange-ps/exchange/Suspend-PublicFolderReplication.md similarity index 87% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Suspend-PublicFolderReplication.md rename to exchange/exchange-ps/exchange/Suspend-PublicFolderReplication.md index a468cde22b..8819989303 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Suspend-PublicFolderReplication.md +++ b/exchange/exchange-ps/exchange/Suspend-PublicFolderReplication.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/suspend-publicfolderreplication +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfolderreplication applicable: Exchange Server 2010 title: Suspend-PublicFolderReplication schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Suspend-PublicFolderReplication @@ -17,16 +16,19 @@ This cmdlet is available only in Exchange Server 2010. Use the Suspend-PublicFolderReplication cmdlet to stop public folder replication for the organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Suspend-PublicFolderReplication [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] +Suspend-PublicFolderReplication [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,8 +44,7 @@ This example stops public folder replication for the organization. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -96,12 +97,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/mail-flow/Suspend-Queue.md b/exchange/exchange-ps/exchange/Suspend-Queue.md similarity index 83% rename from exchange/exchange-ps/exchange/mail-flow/Suspend-Queue.md rename to exchange/exchange-ps/exchange/Suspend-Queue.md index 6b98f386a4..14102cc59b 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Suspend-Queue.md +++ b/exchange/exchange-ps/exchange/Suspend-Queue.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/suspend-queue +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Suspend-Queue @@ -17,30 +16,33 @@ This cmdlet is available only in on-premises Exchange. Use the Suspend-Queue cmdlet to stop processing for a queue on a Mailbox server or an Edge Transport server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Filter ``` -Suspend-Queue -Filter <String> [-Server <ServerIdParameter>] +Suspend-Queue -Filter <String> + [-Server <ServerIdParameter>] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Identity ``` Suspend-Queue [-Identity] <QueueIdentity> [-Confirm] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Suspend-Queue cmdlet stops processing on a queue that has a status of Active or Retry. Messages being processed are delivered, but no additional messages leave the queue. When you use the Identity parameter, the queue is suspended only if the identity matches a single queue. If the identity matches more than one queue, you receive an error. To suspend more than one queue in a single operation, you must use the Filter parameter. -For instructions on how to resume suspended queues, see [Resume-Queue](https://docs.microsoft.com/powershell/module/exchange/mail-flow/resume-queue). +For instructions on how to resume suspended queues, see [Resume-Queue](https://learn.microsoft.com/powershell/module/exchange/resume-queue). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,45 +62,44 @@ This example suspends processing on all queues on the server Server1.contoso.com ## PARAMETERS -### -Filter -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://docs.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://docs.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 ("). +### -Identity +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: String -Parameter Sets: Filter +Type: QueueIdentity +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -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://docs.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity). +### -Filter +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 ("). ```yaml -Type: QueueIdentity -Parameter Sets: Identity +Type: String +Parameter Sets: Filter Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -118,11 +119,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -163,12 +161,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/devices/Test-ActiveSyncConnectivity.md b/exchange/exchange-ps/exchange/Test-ActiveSyncConnectivity.md similarity index 83% rename from exchange/exchange-ps/exchange/devices/Test-ActiveSyncConnectivity.md rename to exchange/exchange-ps/exchange/Test-ActiveSyncConnectivity.md index 50280d53e8..48f24eefda 100644 --- a/exchange/exchange-ps/exchange/devices/Test-ActiveSyncConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-ActiveSyncConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/test-activesyncconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-ActiveSyncConnectivity @@ -17,18 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Test-ActiveSyncConnectivity cmdlet to test connectivity to Microsoft Exchange ActiveSync virtual directories. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Test-ActiveSyncConnectivity [[-ClientAccessServer] <ServerIdParameter>] [[-URL] <String>] - [-AllowUnsecureAccess] [-Confirm] [-DomainController <Fqdn>] [-LightMode] [-MailboxCredential <PSCredential>] - [-MailboxServer <ServerIdParameter>] [-MonitoringContext] [-MonitoringInstance <String>] - [-ResetTestAccountCredentials] [-Timeout <UInt32>] [-TrustAnySSLCertificate] - [-UseAutodiscoverForClientAccessServer] [-WhatIf] [<CommonParameters>] + [-AllowUnsecureAccess] + [-Confirm] + [-DomainController <Fqdn>] + [-LightMode] + [-MailboxCredential <PSCredential>] + [-MailboxServer <ServerIdParameter>] + [-MonitoringContext] + [-MonitoringInstance <String>] + [-ResetTestAccountCredentials] + [-Timeout <UInt32>] + [-TrustAnySSLCertificate] + [-UseAutodiscoverForClientAccessServer] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -36,27 +45,20 @@ The Test-ActiveSyncConnectivity cmdlet tests Exchange ActiveSync connectivity by The first time you use this cmdlet, you might be required to create a test user. To create a test user, run the following command: -& $env:ExchangeInstallPath\Scripts\New-TestCasConnectivityUser.ps1 +`& $env:ExchangeInstallPath\Scripts\New-TestCasConnectivityUser.ps1` The test results are displayed on-screen. The cmdlet returns the following information. - CasServer: The Exchange server that the client connected to. - - LocalSite: The name of the local Active Directory site. - - Scenario: The operations that are tested. Values are: Options, FolderSync, First Sync, GetItemEstimate, Sync Data, Ping, and Sync Test Item. - - Result: The values returned are typically Success, Skipped, or Failure. - - Latency(MS): The time required to complete the test in milliseconds. - - Error: Any error messages that were encountered. -You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example: - -Test-ActiveSyncConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\EAS Test.html" +You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-ActiveSyncConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\EAS Test.html"`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,55 +78,69 @@ This example tests the Exchange ActiveSync connectivity for the mailbox PaulS us ## PARAMETERS -### -AllowUnsecureAccess -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. +### -ClientAccessServer +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: + +- Name +- Distinguished name (DN) +- ExchangeLegacyDN +- GUID + +You can't use this parameter with the Url parameter. ```yaml -Type: SwitchParameter +Type: ServerIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -ClientAccessServer -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: - -- Name +### -URL +The URL parameter specifies the URL that's used to connect to the Exchange ActiveSync virtual directory. -- Distinguished name (DN) +You can't use this parameter with the ClientAccessServer parameter. -- ExchangeLegacyDN +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -- GUID +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` -You can't use this parameter with the Url parameter. +### -AllowUnsecureAccess +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: ServerIdParameter +Type: SwitchParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -179,7 +195,7 @@ Accept wildcard characters: False ### -MailboxCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -195,16 +211,13 @@ Accept wildcard characters: False ``` ### -MailboxServer -The MailboxServer parameter specifies the Exchange 2016 or Exchange 2013 Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. +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: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID If you don't use this parameter, connections to all Mailbox servers in the local Active Directory site are tested. @@ -223,7 +236,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -255,7 +270,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -287,7 +304,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether to ignore Secure Sockets Layer (SSL) certificate validation failures. You don't need to specify a value with this switch. +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. @@ -304,24 +321,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -URL -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -UseAutodiscoverForClientAccessServer 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. @@ -359,12 +358,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Test-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/Test-ApplicationAccessPolicy.md similarity index 76% rename from exchange/exchange-ps/exchange/organization/Test-ApplicationAccessPolicy.md rename to exchange/exchange-ps/exchange/Test-ApplicationAccessPolicy.md index e67388d454..24d8280b0b 100644 --- a/exchange/exchange-ps/exchange/organization/Test-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/exchange/Test-ApplicationAccessPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/test-applicationaccesspolicy -applicable: Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Test-ApplicationAccessPolicy @@ -17,22 +16,19 @@ This cmdlet is available only in the cloud-based service. Use the Test-ApplicationAccessPolicy cmdlet to test access right of an application to a specific user/mailbox. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX -### Set1 ``` -Test-ApplicationAccessPolicy [-Identity] <RecipientIdParameter> -AppId <String> [<CommonParameters>] +Test-ApplicationAccessPolicy [-Identity] <RecipientIdParameter> -AppId <String> + [<CommonParameters>] ``` ## DESCRIPTION This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -56,20 +52,16 @@ This example tests access to the user RandomUser9911@AppPolicyTest2.com for the The Identity parameter specifies the recipient to test. You can use any value that uniquely identifies the recipient. For example: - Name - - Distinguished name (DN) - - Display name - - Email address - - GUID ```yaml Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -87,7 +79,7 @@ You can specify multiple app GUID values separated by commas. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -101,12 +93,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Test-ArchiveConnectivity.md b/exchange/exchange-ps/exchange/Test-ArchiveConnectivity.md similarity index 89% rename from exchange/exchange-ps/exchange/policy-and-compliance/Test-ArchiveConnectivity.md rename to exchange/exchange-ps/exchange/Test-ArchiveConnectivity.md index 9dd5610110..219f178aa0 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Test-ArchiveConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-ArchiveConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/test-archiveconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-ArchiveConnectivity @@ -17,19 +16,23 @@ This cmdlet is available only in on-premises Exchange. Use the Test-ArchiveConnectivity cmdlet to verify archive functionality for a mailbox user. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-ArchiveConnectivity [-UserSmtp] <SmtpAddress> [-Confirm] [-WhatIf] [-IncludeArchiveMRMConfiguration] - [-MessageId <String>] [<CommonParameters>] +Test-ArchiveConnectivity [-UserSmtp] <SmtpAddress> + [-Confirm] + [-IncludeArchiveMRMConfiguration] + [-MessageId <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION Running the Test-ArchiveConnectivity cmdlet validates connectivity to a user's archive mailbox. End-to-end verification includes testing whether an on-premises or cloud-based archive is provisioned for the on-premises mailbox user and whether it's enabled and logging on to the archive mailbox on behalf of the user. Successful completion of the command indicates that processes such as the Managed Folder Assistant and Outlook on the web are able to successfully access the archive mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,8 +71,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -85,14 +87,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -IncludeArchiveMRMConfiguration +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: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -101,11 +103,11 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -IncludeArchiveMRMConfiguration -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. +### -MessageId +This parameter is reserved for internal Microsoft use. ```yaml -Type: SwitchParameter +Type: String Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 @@ -117,14 +119,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MessageId -This parameter is reserved for internal Microsoft use. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. ```yaml -Type: String +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -138,12 +140,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-AssistantHealth.md b/exchange/exchange-ps/exchange/Test-AssistantHealth.md similarity index 82% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-AssistantHealth.md rename to exchange/exchange-ps/exchange/Test-AssistantHealth.md index b65a1a8f80..95868838da 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-AssistantHealth.md +++ b/exchange/exchange-ps/exchange/Test-AssistantHealth.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/test-assistanthealth +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-AssistantHealth @@ -17,14 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Test-AssistantHealth cmdlet to verify that the Microsoft Exchange Mailbox Assistants service (MSExchangeMailboxAssistants) is healthy, to recover from health issues, and to report the status of the diagnosis or recovery action. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-AssistantHealth [[-ServerName] <ServerIdParameter>] [-Confirm] [-IncludeCrashDump] - [-MaxProcessingTimeInMinutes <UInt32>] [-MonitoringContext] [-ResolveProblems] [-WhatIf] - [-WatermarkBehindWarningThreholdInMinutes <UInt32>] [<CommonParameters>] +Test-AssistantHealth [[-ServerName] <ServerIdParameter>] + [-Confirm] + [-IncludeCrashDump] + [-MaxProcessingTimeInMinutes <UInt32>] + [-MonitoringContext] + [-ResolveProblems] + [-WatermarkBehindWarningThreholdInMinutes <UInt32>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -32,7 +37,7 @@ The Mailbox Assistants service runs on all servers that have the Mailbox server By default, when you run this cmdlet, it returns the RunspaceId, events, and performance counters in a table format. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -52,11 +57,33 @@ This example detects the mailbox assistant's health on the local Mailbox server. ## PARAMETERS +### -ServerName +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +If you don't use this parameter, the command is run on the local server. + +```yaml +Type: ServerIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -73,11 +100,9 @@ Accept wildcard characters: False ``` ### -IncludeCrashDump -The IncludeCrashDump parameter specifies that the command should take an error report prior to taking any recovery actions. This parameter should only be used if running from a local computer. If you use the parameter while connected remotely, the command fails. - -The default value for this parameter is $false. +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 don't have to specify a value with this parameter. +You should only use this switch on the local computer. If you use this switch while connected remotely, the command will fail. ```yaml Type: SwitchParameter @@ -109,7 +134,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -125,14 +152,13 @@ Accept wildcard characters: False ``` ### -ResolveProblems -This ResolveProblems parameter specifies that if the command detects an issue, it attempts to fix it. This command attempts to fix the following issues: +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. -- Starts the Mailbox Assistants service if it isn't running. +This command attempts to fix the following issues: +- Starts the Mailbox Assistants service if it isn't running. - Restarts the Mailbox Assistants service if it detects that the service is hung or deadlocked for more than 15 minutes. -You don't have to specify a value with this parameter. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -146,29 +172,21 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ServerName -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 - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN +### -WatermarkBehindWarningThreholdInMinutes +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. -If you don't use this parameter, the command is run on the local server. +You can specify a value from 1 through 10080 minutes. The default value is 60 minutes. ```yaml -Type: ServerIdParameter +Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -188,35 +206,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WatermarkBehindWarningThreholdInMinutes -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. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Test-CalendarConnectivity.md b/exchange/exchange-ps/exchange/Test-CalendarConnectivity.md similarity index 83% rename from exchange/exchange-ps/exchange/client-access/Test-CalendarConnectivity.md rename to exchange/exchange-ps/exchange/Test-CalendarConnectivity.md index 46ce5f4fab..c2836a32a6 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-CalendarConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-CalendarConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-calendarconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-CalendarConnectivity @@ -17,17 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Test-CalendarConnectivity cmdlet to verify that anonymous calendar sharing is enabled and working properly. The Calendar virtual directory is a subdirectory of the Microsoft Outlook on the web virtual directories. When you run this command without any parameters, the command tests calendar connectivity against all Outlook on the web virtual directories. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-CalendarConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-LightMode] [-MailboxServer <ServerIdParameter>] [-MonitoringContext] [-ResetTestAccountCredentials] - [-TestType <OwaConnectivityTestType>] [-Timeout <UInt32>] [-TrustAnySSLCertificate] - [-VirtualDirectoryName <String>] [-WhatIf] [<CommonParameters>] +Test-CalendarConnectivity [[-ClientAccessServer] <ServerIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-LightMode] + [-MailboxServer <ServerIdParameter>] + [-MonitoringContext] + [-ResetTestAccountCredentials] + [-TestType <OwaConnectivityTestType>] + [-Timeout <UInt32>] + [-TrustAnySSLCertificate] + [-VirtualDirectoryName <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -42,22 +50,15 @@ If the server hosting the test mailbox isn't available, the command returns an e The test results are displayed on-screen. The cmdlet returns the following information. - CasServer: The Exchange server that the client connected to. - - LocalSite: The name of the local Active Directory site. - - Scenario: The operations that are tested. Values are: Logon, CalendarICS and CalendarHTML. - - Result: The values returned are typically Success, Skipped or Failure. - - Latency(MS): The time required to complete the test in milliseconds. - - Error: Any error messages that were encountered. -You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example: - -Test-CalendarConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\Calendar Test.html" +You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-CalendarConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\Calendar Test.html"`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,11 +77,8 @@ The ClientAccessServer parameter specifies the Exchange server to test. This ser You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml @@ -99,8 +97,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -149,16 +146,13 @@ Accept wildcard characters: False ``` ### -MailboxServer -The MailboxServer parameter specifies the Exchange 2016 or Exchange 2013 Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. +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: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID If you don't use this parameter, connections to all Mailbox servers in the local Active Directory site are tested. @@ -177,7 +171,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -193,7 +189,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -295,12 +293,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Test-ClientAccessRule.md b/exchange/exchange-ps/exchange/Test-ClientAccessRule.md new file mode 100644 index 0000000000..3389d80031 --- /dev/null +++ b/exchange/exchange-ps/exchange/Test-ClientAccessRule.md @@ -0,0 +1,251 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Test-ClientAccessRule + +## SYNOPSIS +> [!NOTE] +> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). + +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Test-ClientAccessRule cmdlet to test how client access rules affect access to your organization. If any of the client properties you specify for this cmdlet match any client access rules, the rules are returned in the results. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Test-ClientAccessRule -AuthenticationType <ClientAccessAuthenticationMethod> -Protocol <ClientAccessProtocol> -RemoteAddress <IPAddress> -RemotePort <Int32> -User <MailboxIdParameter> + [-Confirm] + [-OAuthClaims <Hashtable>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. + +**Note**: Currently, not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list: + +- OutlookWebApp:BasicAuthentication and AdfsAuthentication. +- ExchangeAdminCenter:BasicAuthentication and AdfsAuthentication. +- RemotePowerShell:BasicAuthentication and NonBasicAuthentication. +- ExchangeActiveSync:BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Test-ClientAccessRule -AuthenticationType BasicAuthentication -Protocol OutlookWebApp -RemoteAddress 172.17.17.26 -RemotePort 443 -User julia@contoso.com +``` + +This example tests client access by using the following client properties: + +- Authentication type: Basic +- Protocol:OutlookWebApp +- Remote address: 172.17.17.26 +- Remote port: 443 +- User: julia@contoso.com + +## PARAMETERS + +### -AuthenticationType +The AuthenticationType parameter specifies the client authentication type to test. + +Valid values for this parameter are: + +- AdfsAuthentication +- BasicAuthentication +- CertificateBasedAuthentication +- NonBasicAuthentication +- OAuthAuthentication + +In client access rules, authentication types are defined by the AnyOfAuthenticationTypes and ExceptAnyOfAuthenticationTypes parameters. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Protocol +The Protocol parameter specifies the client protocol to test. + +Valid values for this parameter are: + +- ExchangeActiveSync +- ExchangeAdminCenter +- ExchangeWebServices +- IMAP4 +- OfflineAddressBook +- OutlookAnywhere +- OutlookWebApp +- POP3 +- PowerShellWebServices +- RemotePowerShell +- REST + +In client access rules, protocol types are defined by the AnyOfProtocols and ExceptAnyOfProtocols parameters. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteAddress +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. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemotePort +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -User +The User parameter specifies the user account to test. + +For the best results, we recommend using the following values: + +- UPN: For example, `user@contoso.com` (users only). +- Domain\\SamAccountName: For example, `contoso\user`. + +Otherwise, you can use any value that uniquely identifies the user. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +In client access rules, users are defined by the UsernameMatchesAnyOfPatterns, UserRecipientFilter, and ExceptUsernameMatchesAnyOfPatterns parameters. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OAuthClaims +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Test-DataClassification.md b/exchange/exchange-ps/exchange/Test-DataClassification.md new file mode 100644 index 0000000000..7d9109fd68 --- /dev/null +++ b/exchange/exchange-ps/exchange/Test-DataClassification.md @@ -0,0 +1,149 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Test-DataClassification + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Test-DataClassification cmdlet to find the confidence and count of a sensitive information type that's found in a specified text string. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Test-DataClassification + [-ClassificationNames <String[]>] + [-DomainController <Fqdn>] + [-FileExtension <String>] + [-TestTextExtractionResults <TestTextExtractionResult[]>] + [-TextToClassify <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet lets you know the classification results that are returned by the Microsoft classification engine in specific text. The classification results include the sensitive type, its count, and confidence. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$r = Test-DataClassification -TextToClassify "Credit card information Visa: xxxx xxxx xxxx xxxx. Patient Identifier or SSN: xxx-xx-xxxx" + +$r.ClassificationResults +``` + +This example lists all sensitive info types, their count, and confidence in the specified text string. + +## PARAMETERS + +### -ClassificationNames +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 +- Id (GUID value) + +You can specify multiple values separated by commas. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileExtension +This parameter is available only in the cloud-based service. + +{{ Fill FileExtension Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TestTextExtractionResults +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 +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -TextToClassify +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access/Test-EcpConnectivity.md b/exchange/exchange-ps/exchange/Test-EcpConnectivity.md similarity index 81% rename from exchange/exchange-ps/exchange/client-access/Test-EcpConnectivity.md rename to exchange/exchange-ps/exchange/Test-EcpConnectivity.md index 503a6680ad..81cf892ecd 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-EcpConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-EcpConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-ecpconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-EcpConnectivity @@ -17,17 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Test-EcpConnectivity cmdlet to test connectivity to Exchange Control Panel (ECP) virtual directories. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-EcpConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-LightMode] [-MailboxServer <ServerIdParameter>] [-MonitoringContext] [-ResetTestAccountCredentials] - [-RSTEndpoint <String>] [-TestType <OwaConnectivityTestType>] [-Timeout <UInt32>] [-TrustAnySSLCertificate] - [-VirtualDirectoryName <String>] [-WhatIf] [<CommonParameters>] +Test-EcpConnectivity [[-ClientAccessServer] <ServerIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-LightMode] + [-MailboxServer <ServerIdParameter>] + [-MonitoringContext] + [-ResetTestAccountCredentials] + [-RSTEndpoint <String>] + [-TestType <OwaConnectivityTestType>] + [-Timeout <UInt32>] + [-TrustAnySSLCertificate] + [-VirtualDirectoryName <String>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -40,22 +49,15 @@ The first time you use this cmdlet, you might be required to create a test user. The test results are displayed on-screen. The cmdlet returns the following information. - CasServer: The Exchange server that the client connected to. - - LocalSite: The name of the local Active Directory site. - - Scenario: The operations that are tested. Values are: Logon and Sign in. - - Result: The values returned are typically Success, Skipped or Failure. - - Latency(MS): The time required to complete the test in milliseconds. - - Error: Any error messages that were encountered. -You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example: - -Test-EcpConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\EAC Test.html" +You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-EcpConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\EAC Test.html"`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,11 +76,8 @@ The ClientAccessServer parameter specifies the Exchange server to test. This ser You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml @@ -97,8 +96,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -147,16 +145,13 @@ Accept wildcard characters: False ``` ### -MailboxServer -The MailboxServer parameter specifies the Exchange 2016 or Exchange 2013 Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. +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: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID If you don't use this parameter, connections to all Mailbox servers in the local Active Directory site are tested. @@ -175,7 +170,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -191,7 +188,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -255,7 +254,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether to ignore Secure Sockets Layer (SSL) certificate validation failures. You don't need to specify a value with this switch. +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. @@ -311,12 +310,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Test-EdgeSynchronization.md b/exchange/exchange-ps/exchange/Test-EdgeSynchronization.md similarity index 84% rename from exchange/exchange-ps/exchange/mail-flow/Test-EdgeSynchronization.md rename to exchange/exchange-ps/exchange/Test-EdgeSynchronization.md index 7530c8240d..8f9a1e1fb9 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Test-EdgeSynchronization.md +++ b/exchange/exchange-ps/exchange/Test-EdgeSynchronization.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/test-edgesynchronization +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-EdgeSynchronization @@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange. Use the Test-EdgeSynchronization cmdlet to diagnose whether the subscribed Edge Transport servers have a current and accurate synchronization status. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,15 +25,21 @@ For information about the parameter sets in the Syntax section below, see [Excha Test-EdgeSynchronization -VerifyRecipient <ProxyAddress> [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Default ``` -Test-EdgeSynchronization [-ExcludeRecipientTest] [-FullCompareMode] [-MaxReportSize <Unlimited>] [-MonitoringContext <Boolean>] [-TargetServer <String>] +Test-EdgeSynchronization [-ExcludeRecipientTest] + [-FullCompareMode] + [-MaxReportSize <Unlimited>] + [-MonitoringContext <Boolean>] + [-TargetServer <String>] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -42,7 +47,7 @@ The Test-EdgeSynchronization cmdlet is a diagnostic cmdlet that provides a repor This cmdlet compares the data stored in Active Directory and the data stored in AD LDS. Any inconsistencies in data are reported in the results output by this cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -81,8 +86,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -115,7 +119,9 @@ Accept wildcard characters: False ``` ### -ExcludeRecipientTest -The ExcludeRecipientTest switch specifies whether to exclude validation of recipient data synchronization. If you include this switch, only the synchronization of configuration objects is validated. Validating that recipient data is synchronized takes longer than validating only configuration data. You don't have to include a value with this switch. +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. ```yaml Type: SwitchParameter @@ -131,7 +137,9 @@ Accept wildcard characters: False ``` ### -FullCompareMode -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. 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. +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. ```yaml Type: SwitchParameter @@ -163,7 +171,10 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -217,12 +228,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-ExchangeSearch.md b/exchange/exchange-ps/exchange/Test-ExchangeSearch.md similarity index 86% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-ExchangeSearch.md rename to exchange/exchange-ps/exchange/Test-ExchangeSearch.md index bc59c81fb4..de07b2a9a7 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-ExchangeSearch.md +++ b/exchange/exchange-ps/exchange/Test-ExchangeSearch.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/test-exchangesearch +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-ExchangeSearch @@ -17,18 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Test-ExchangeSearch cmdlet to test that Exchange Search is currently enabled and is indexing new email messages in a timely manner. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Identity ``` -Test-ExchangeSearch [[-Identity] <MailboxIdParameter>] [-Archive] +Test-ExchangeSearch [[-Identity] <MailboxIdParameter>] + [-Archive] [-Confirm] [-DomainController <Fqdn>] [-IndexingTimeoutInSeconds <Int32>] [-MonitoringContext] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Database @@ -38,7 +39,8 @@ Test-ExchangeSearch [-MailboxDatabase <DatabaseIdParameter>] [-DomainController <Fqdn>] [-IndexingTimeoutInSeconds <Int32>] [-MonitoringContext] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Server @@ -48,7 +50,8 @@ Test-ExchangeSearch [-Server <ServerIdParameter>] [-DomainController <Fqdn>] [-IndexingTimeoutInSeconds <Int32>] [-MonitoringContext] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -56,7 +59,7 @@ The Test-ExchangeSearch cmdlet creates a hidden message and an attachment in the You can use the Verbose switch to get detailed information about each step performed by the cmdlet as part of the test. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -76,8 +79,37 @@ This example tests Exchange Search results for the mailbox database on which the ## PARAMETERS +### -Identity +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +You can't use this parameter with the MailboxDatabase or Server parameters. + +```yaml +Type: MailboxIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Archive -The Archive switch specifies that the test be run against the archive mailbox for the mailbox user specified in the Identity parameter. When the Archive switch is used, you must also use the Identity parameter to specify the mailbox. +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 @@ -95,8 +127,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -128,44 +159,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -You can't use this parameter with the MailboxDatabase or Server parameters. - -```yaml -Type: MailboxIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -IndexingTimeoutInSeconds 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. @@ -183,14 +176,12 @@ Accept wildcard characters: False ``` ### -MailboxDatabase -This parameter is available or functional only in Exchange Server 2010 and 2013. +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: - Name - - Distinguished name (DN) - - GUID You can't use this parameter with the Identity or Server parameters. @@ -209,7 +200,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -228,11 +221,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can't use this parameter with the MailboxDatabase or Identity parameters. @@ -271,12 +261,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Test-FederationTrust.md b/exchange/exchange-ps/exchange/Test-FederationTrust.md similarity index 85% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Test-FederationTrust.md rename to exchange/exchange-ps/exchange/Test-FederationTrust.md index 6fe7d059ad..d8910cf09d 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Test-FederationTrust.md +++ b/exchange/exchange-ps/exchange/Test-FederationTrust.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/test-federationtrust +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-FederationTrust @@ -17,13 +16,17 @@ This cmdlet is available only in on-premises Exchange. Use the Test-FederationTrust cmdlet to verify that the federation trust is properly configured and functioning as expected. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-FederationTrust [-Confirm] [-DomainController <Fqdn>] [-MonitoringContext <Boolean>] - [-UserIdentity <RecipientIdParameter>] [-WhatIf] [<CommonParameters>] +Test-FederationTrust [-Confirm] + [-DomainController <Fqdn>] + [-MonitoringContext <Boolean>] + [-UserIdentity <RecipientIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -36,12 +39,10 @@ You can run the Test-FederationTrust cmdlet from the Exchange Management Shell, The Test-FederationTrust cmdlet runs the following series of tests to ensure that federation is working as expected: - A connection to the Microsoft Federation Gateway is established. This test ensures that communication between the local Exchange server and the Microsoft Federation Gateway is working correctly. - - Certificates are checked to ensure they're valid and can be used with the Microsoft Federation Gateway. - - A security token is requested from the Microsoft Federation Gateway. This test ensures that a token can be properly retrieved and used. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -57,8 +58,7 @@ This example validates the federation trust deployed in the Exchange organizatio ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -91,7 +91,10 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -110,15 +113,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID If you don't specify a mailbox, the command uses the default test mailbox. @@ -157,12 +155,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Test-FederationTrustCertificate.md b/exchange/exchange-ps/exchange/Test-FederationTrustCertificate.md similarity index 87% rename from exchange/exchange-ps/exchange/federation-and-hybrid/Test-FederationTrustCertificate.md rename to exchange/exchange-ps/exchange/Test-FederationTrustCertificate.md index de1412514d..d26350dd00 100644 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Test-FederationTrustCertificate.md +++ b/exchange/exchange-ps/exchange/Test-FederationTrustCertificate.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/test-federationtrustcertificate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-FederationTrustCertificate @@ -17,18 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Test-FederationTrustCertificate cmdlet to check the status of certificates that are used for federation on all Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-FederationTrustCertificate [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] +Test-FederationTrustCertificate [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The certificate used to establish a federation trust is propagated to all Exchange servers in the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,8 +46,7 @@ This example reports the status of federation certificates. ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -98,12 +99,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Test-IPAllowListProvider.md b/exchange/exchange-ps/exchange/Test-IPAllowListProvider.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Test-IPAllowListProvider.md rename to exchange/exchange-ps/exchange/Test-IPAllowListProvider.md index 34831b7fcb..4b2de63622 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Test-IPAllowListProvider.md +++ b/exchange/exchange-ps/exchange/Test-IPAllowListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/test-ipallowlistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-IPAllowListProvider @@ -17,13 +16,17 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Test-IPAllowListProvider cmdlet to test IP Allow list providers on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-IPAllowListProvider [-Identity] <IPAllowListProviderIdParameter> -IPAddress <IPAddress> [-Confirm] - [-DomainController <Fqdn>] [-Server <ServerIdParameter>] [-WhatIf] [<CommonParameters>] +Test-IPAllowListProvider [-Identity] <IPAllowListProviderIdParameter> -IPAddress <IPAddress> + [-Confirm] + [-DomainController <Fqdn>] + [-Server <ServerIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -46,9 +49,7 @@ This example tests the existing IP Allow list provider named Contoso,com by send 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 - - Distinguished name (DN) - - GUID ```yaml @@ -83,8 +84,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -122,11 +122,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -167,12 +164,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Test-IPBlockListProvider.md b/exchange/exchange-ps/exchange/Test-IPBlockListProvider.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Test-IPBlockListProvider.md rename to exchange/exchange-ps/exchange/Test-IPBlockListProvider.md index dba8052b7f..7ab51aad23 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Test-IPBlockListProvider.md +++ b/exchange/exchange-ps/exchange/Test-IPBlockListProvider.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/test-ipblocklistprovider +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-IPBlockListProvider @@ -17,13 +16,17 @@ This cmdlet is available or effective only on Edge Transport servers in on-premi Use the Test-IPBlockListProvider cmdlet to test IP Block list providers on Edge Transport servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-IPBlockListProvider [-Identity] <IPBlockListProviderIdParameter> -IPAddress <IPAddress> [-Confirm] - [-DomainController <Fqdn>] [-Server <ServerIdParameter>] [-WhatIf] [<CommonParameters>] +Test-IPBlockListProvider [-Identity] <IPBlockListProviderIdParameter> -IPAddress <IPAddress> + [-Confirm] + [-DomainController <Fqdn>] + [-Server <ServerIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -46,9 +49,7 @@ This example tests the existing IP Block list provider named Contoso.com by send 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 - - Distinguished name (DN) - - GUID ```yaml @@ -83,8 +84,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -122,11 +122,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -167,12 +164,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Test-IRMConfiguration.md b/exchange/exchange-ps/exchange/Test-IRMConfiguration.md similarity index 78% rename from exchange/exchange-ps/exchange/encryption-and-certificates/Test-IRMConfiguration.md rename to exchange/exchange-ps/exchange/Test-IRMConfiguration.md index fcdc6e07bb..c3b0a5ae4e 100644 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Test-IRMConfiguration.md +++ b/exchange/exchange-ps/exchange/Test-IRMConfiguration.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/test-irmconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Test-IRMConfiguration @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Test-IRMConfiguration cmdlet to test Information Rights Management (IRM) configuration and functionality. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -27,13 +26,14 @@ Test-IRMConfiguration [[-Identity] <OrganizationIdParameter>] -Sender <SmtpAddre [-DomainController <Fqdn>] [-Recipient <SmtpAddress[]>] [-RMSOnline] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Test-IRMConfiguration cmdlet performs a series of steps to test IRM configuration and functionality, including availability of an Active Directory Rights Management Services (AD RMS) server, prelicensing and journal report decryption. In Exchange Online organizations, it checks connectivity to RMS Online and obtains and validates the organization's Trusted Publishing Domain (TPD). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,18 +42,43 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Test-IRMConfiguration -Sender adams@contoso.com ``` -This example tests the IRM configuration for messages sent from the sender adams@contoso.com. +This example tests the IRM configuration in on-premises Exchange for messages sent from the sender adams@contoso.com. + +### Example 2 +```powershell +Test-IRMConfiguration -Sender chris@fabrikam.com -Recipient michell@fourthcoffee.com +``` + +This example tests the IRM configuration in the cloud-based service for messages sent from chris@fabrikam.com to michell@fourthcoffee.com. ## PARAMETERS +### -Identity +This parameter is available only in on-premises Exchange. + +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -Sender -The Sender parameter specifies the SMTP address of the sender to be tested. The cmdlet tests prelicensing and journal report decryption for the sender. +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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -65,15 +90,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -100,34 +124,18 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -This parameter is available only in on-premises Exchange. - -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -Recipient -The Recipient parameter specifies the SMTP address of one or more recipients. The cmdlet tests prelicensing for the specified recipients. You can specify multiple recipient addresses separated by commas. +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. -If no recipient is specified, the sender address is used as the recipient. +In on-premises Exchange, if you don't use this parameter, the sender address that's specified by the Sender parameter is used for the value of this parameter. ```yaml Type: SmtpAddress[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -145,7 +153,7 @@ The RMSOnline switch specifies whether to test connectivity from Exchange Online Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -161,7 +169,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -175,12 +183,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Test-ImapConnectivity.md b/exchange/exchange-ps/exchange/Test-ImapConnectivity.md similarity index 79% rename from exchange/exchange-ps/exchange/client-access/Test-ImapConnectivity.md rename to exchange/exchange-ps/exchange/Test-ImapConnectivity.md index 47d6fc7559..44bf2c9053 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-ImapConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-ImapConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-imapconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-ImapConnectivity @@ -17,18 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Test-ImapConnectivity cmdlet to verify that connectivity to the Microsoft Exchange IMAP4 service is working as expected. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-ImapConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-Confirm] - [-ConnectionType <ProtocolConnectionType>] [-DomainController <Fqdn>] [-LightMode] - [-MailboxCredential <PSCredential>] [-MailboxServer <ServerIdParameter>] [-MonitoringContext] - [-PerConnectionTimeout <Int32>] [-PortClientAccessServer <Int32>] [-ResetTestAccountCredentials] - [-Timeout <UInt32>] [-TrustAnySSLCertificate] [-WhatIf] [<CommonParameters>] +Test-ImapConnectivity [[-ClientAccessServer] <ServerIdParameter>] + [-Confirm] + [-ConnectionType <ProtocolConnectionType>] + [-DomainController <Fqdn>] + [-LightMode] + [-MailboxCredential <PSCredential>] + [-MailboxServer <ServerIdParameter>] + [-MonitoringContext] + [-PerConnectionTimeout <Int32>] + [-PortClientAccessServer <Int32>] + [-ResetTestAccountCredentials] + [-Timeout <UInt32>] + [-TrustAnySSLCertificate] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -41,26 +50,19 @@ The first time you use this cmdlet, you might be required to create a test user. The test results are displayed on-screen. The cmdlet returns the following information. - CasServer: The Exchange server that the client connected to. - - LocalSite: The name of the local Active Directory site. - - Scenario: The operations that are tested. Test IMAP4 Connectivity connects to the server using the IMAP4 protocol, searches for the test message and deletes it along with any messages that are older than 24 hours. - - Result: The values returned are typically Success, Skipped or Failure. - - Latency(MS): The time required to complete the test in milliseconds. - - Error: Any error messages that were encountered. -You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example: +You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-IMAPConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\IMAP Test.html"`. -Test-IMAPConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\IMAP Test.html" +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +**Note**: In Exchange 2013 or later, when you run this command to test a single mailbox on an Exchange server that isn't hosting the active mailbox database copy for the mailbox, you might see the following error message: -**Important Note**: In Exchange 2013 or later, when you run this command to test a single mailbox on an Exchange server that isn't hosting the active mailbox database copy for the mailbox, you might see the following error message: - -Unable to create MailboxSession object to access the mailbox \[user@consoto.com\]. Detailed error information: \[Microsoft.Exchange.Data.Storage.WrongServerException\]: The user and the mailbox are in different Active Directory sites. Inner error \[Microsoft.Mapi.MapiExceptionMailboxInTransit\]: MapiExceptionMailboxInTransit: Detected site violation \(hr=0x0, ec=1292\) +`Unable to create MailboxSession object to access the mailbox [user@contoso.com]. Detailed error information: [Microsoft.Exchange.Data.Storage.WrongServerException]: The user and the mailbox are in different Active Directory sites. Inner error [Microsoft.Mapi.MapiExceptionMailboxInTransit]: MapiExceptionMailboxInTransit: Detected site violation (hr=0x0, ec=1292)` When you receive this error, run the command again on the server that's hosting the active mailbox database copy to verify that IMAP works for the mailbox. @@ -88,11 +90,8 @@ The ClientAccessServer parameter specifies the Exchange server to test. This ser You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml @@ -111,8 +110,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -132,9 +130,7 @@ Accept wildcard characters: False The ConnectionType parameter specifies the type of connection that's used to connect to the IMAP4 service. Valid values are: - Plaintext - - Ssl - - Tls ```yaml @@ -187,7 +183,7 @@ Accept wildcard characters: False ### -MailboxCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -203,16 +199,13 @@ Accept wildcard characters: False ``` ### -MailboxServer -The MailboxServer parameter specifies the Exchange 2016 or Exchange 2013 Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. +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: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID If you don't use this parameter, connections to all Mailbox servers in the local Active Directory site are tested. @@ -231,7 +224,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -281,7 +276,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -315,7 +312,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether to ignore Secure Sockets Layer (SSL) certificate validation failures. You don't need to specify a value with this switch. +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. @@ -353,12 +350,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Test-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/exchange/Test-M365DataAtRestEncryptionPolicy.md new file mode 100644 index 0000000000..f166b0c365 --- /dev/null +++ b/exchange/exchange-ps/exchange/Test-M365DataAtRestEncryptionPolicy.md @@ -0,0 +1,127 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Test-M365DataAtRestEncryptionPolicy + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Test-M365DataAtRestEncryptionPolicy cmdlet to test an existing Microsoft 365 data-at-rest encryption policy. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Test-M365DataAtRestEncryptionPolicy [[-Identity] <DataEncryptionPolicyIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Test-M365DataAtRestEncryptionPolicy -Identity "Contoso Corporate" +``` + +This example tests the Microsoft 365 data-at-rest encryption policy named Contoso Corporate. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID + +You can find the existing data-at-rest encryption policies by using the Get-M365DataAtRestEncryptionPolicy cmdlet. + +```yaml +Type: DataEncryptionPolicyIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Test-MAPIConnectivity.md b/exchange/exchange-ps/exchange/Test-MAPIConnectivity.md similarity index 89% rename from exchange/exchange-ps/exchange/mailboxes/Test-MAPIConnectivity.md rename to exchange/exchange-ps/exchange/Test-MAPIConnectivity.md index 9e24cd3a20..0b615b567c 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Test-MAPIConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-MAPIConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/test-mapiconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Test-MAPIConnectivity @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Test-MapiConnectivity cmdlet to verify server functionality by logging on to the mailbox that you specify. If you don't specify a mailbox, the cmdlet logs on to the SystemMailbox on the database that you specify. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,7 +30,8 @@ Test-MAPIConnectivity -Database <DatabaseIdParameter> [-DomainController <Fqdn>] [-MonitoringContext <Boolean>] [-PerConnectionTimeout <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Identity @@ -45,7 +45,8 @@ Test-MAPIConnectivity [-Identity] <MailboxIdParameter> [-DomainController <Fqdn>] [-MonitoringContext <Boolean>] [-PerConnectionTimeout <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Server @@ -58,7 +59,8 @@ Test-MAPIConnectivity [-Server <ServerIdParameter>] [-IncludePassive] [-MonitoringContext <Boolean>] [-PerConnectionTimeout <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -69,12 +71,10 @@ The cmdlet logs on to the mailbox that you specify using the credentials of the There are three distinct parameters that you can use with the command: Database, Identity and Server: - The Database parameter takes a database identity and tests the ability to log on to the system mailbox on the specified database. - - The Identity parameter takes a mailbox identity and tests the ability to log on to a specific mailbox. - - The Server parameter takes a server identity and tests the ability to log on to each system mailbox on the specified server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -94,71 +94,60 @@ This example tests connectivity to a mailbox, specified as a domain name and use ## PARAMETERS -### -Database -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: +### -Identity +The Identity parameter specifies a mailbox to test. You can use any value that uniquely identifies the mailbox. For example: - Name - +- Alias - Distinguished name (DN) - +- Canonical DN +- Domain\\Username +- Email address - GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) -If you don't use this parameter or the Identity parameter, the command tests the SystemMailbox on each active database on the Exchange server (the local Exchange server or the server you specify with the Server parameter). +This cmdlet accepts pipeline input from the Get-Mailbox or Get-Recipient cmdlet. If you pipe the identify from the Get-Mailbox or Get-Recipient cmdlets, you don't need to use this parameter. + +If you don't use this parameter, the cmdlet tests the SystemMailbox on the database that you specify. You can't use the Identity, Database, or Server parameters in the same command. ```yaml -Type: DatabaseIdParameter -Parameter Sets: Database +Type: MailboxIdParameter +Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True -Position: Named +Position: 1 Default value: None Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies a mailbox to test. You can use any value that uniquely identifies the mailbox. For example: - -- Name +### -Database +This parameter is available only in on-premises Exchange. -- Alias +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: +- Name - Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - - GUID -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -This cmdlet accepts pipeline input from the Get-Mailbox or Get-Recipient cmdlet. If you pipe the identify from the Get-Mailbox or Get-Recipient cmdlets, you don't need to use this parameter. - -If you don't use this parameter, the cmdlet tests the SystemMailbox on the database that you specify. +If you don't use this parameter or the Identity parameter, the command tests the SystemMailbox on each active database on the Exchange server (the local Exchange server or the server you specify with the Server parameter). You can't use the Identity, Database, or Server parameters in the same command. ```yaml -Type: MailboxIdParameter -Parameter Sets: Identity +Type: DatabaseIdParameter +Parameter Sets: Database Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False @@ -201,7 +190,9 @@ Accept wildcard characters: False ``` ### -Archive -The Archive parameter specifies whether to test the MAPI connectivity of the personal archive associated with the specified mailbox. If you don't specify this parameter, only the primary mailbox is tested. +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. ```yaml Type: SwitchParameter @@ -219,8 +210,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -242,11 +232,8 @@ 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN You can only use this parameter with the Server parameter, not the Identify or Database parameters. @@ -285,7 +272,9 @@ Accept wildcard characters: False ### -IncludePassive This parameter is available only in on-premises Exchange. -Without the IncludePassive parameter, the cmdlet tests MAPI connectivity from active database copies only. Using the IncludePassive parameter, you can have the cmdlet test MAPI connectivity from all active and passive database copies. +The IncludePassive switch tests MAPI connectivity from all active and passive database copies. You don't need to specify a value with this switch. + +If you don't use this switch, the command tests MAPI connectivity from active database copies only. ```yaml Type: SwitchParameter @@ -303,7 +292,10 @@ Accept wildcard characters: False ### -MonitoringContext 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 for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -342,11 +334,8 @@ 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: - Name - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't specify this parameter, the command tests the mailbox on the local server. @@ -387,12 +376,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-MRSHealth.md b/exchange/exchange-ps/exchange/Test-MRSHealth.md similarity index 86% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-MRSHealth.md rename to exchange/exchange-ps/exchange/Test-MRSHealth.md index d0dfa97e84..c4208ccf1f 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Test-MRSHealth.md +++ b/exchange/exchange-ps/exchange/Test-MRSHealth.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/test-mrshealth +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-MRSHealth @@ -17,20 +16,26 @@ This cmdlet is available only in on-premises Exchange. Use the Test-MRSHealth cmdlet to test the health of an instance of the Microsoft Exchange Mailbox Replication service. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-MRSHealth [[-Identity] <ServerIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-MaxQueueScanAgeSeconds <Int32>] [-MonitoringContext <Boolean>] [-WhatIf] - [-MRSProxyCredentials <PSCredential>] [-MRSProxyServer <Fqdn>] [<CommonParameters>] +Test-MRSHealth [[-Identity] <ServerIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-MaxQueueScanAgeSeconds <Int32>] + [-MonitoringContext <Boolean>] + [-MRSProxyCredentials <PSCredential>] + [-MRSProxyServer <Fqdn>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Microsoft Exchange Mailbox Replication service runs on Mailbox servers. This command ensures that the Mailbox Replication service is running and that it responds to a remote procedure call (RPC) ping check. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,33 +55,39 @@ This example tests the health of the Mailbox Replication service on the Mailbox ## PARAMETERS -### -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. +### -Identity +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: -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +- Name +- Distinguished name (DN) +- ExchangeLegacyDN +- GUID -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +If you don't specify the server, the command runs on the local server. ```yaml -Type: SwitchParameter +Type: ServerIdParameter Parameter Sets: (All) -Aliases: cf +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: Fqdn +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -86,29 +97,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Distinguished name (DN) - -- ExchangeLegacyDN - -- GUID - -If you don't specify the server, the command runs on the local server. +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. ```yaml -Type: ServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -129,7 +130,10 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -144,26 +148,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -MRSProxyCredentials 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -184,9 +172,7 @@ The MRSProxyServer parameter specifies the fully qualified domain name (FQDN) of 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: - If you specify an MRSProxyServer value and you specify the source server by using the Identity parameter, the test is performed between that server and the target server specified by the MRSProxyServer parameter. - - If you specify an MRSProxyServer value and you don't specify a source server by using the Identity parameter, the test is performed between the local server and the target server specified by the MRSProxyServer parameter. - - If you don't specify an MRSProxyServer value or an Identity value, the test is performed between the Mailbox Replication service and the Mailbox Replication proxy service on the local server. ```yaml @@ -202,17 +188,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Test-Mailflow.md b/exchange/exchange-ps/exchange/Test-Mailflow.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Test-Mailflow.md rename to exchange/exchange-ps/exchange/Test-Mailflow.md index 9ba9e473e7..628848623e 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Test-Mailflow.md +++ b/exchange/exchange-ps/exchange/Test-Mailflow.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/test-mailflow +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-Mailflow @@ -17,31 +16,37 @@ This cmdlet is available only in on-premises Exchange. Use the Test-Mailflow cmdlet to diagnose whether mail can be successfully sent from and delivered to the system mailbox on a Mailbox server. You can also use this cmdlet to verify that email is sent between Mailbox servers within a defined latency threshold. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### AutoDiscoverTargetMailboxServer ``` -Test-Mailflow [[-Identity] <ServerIdParameter>] [-AutoDiscoverTargetMailboxServer] +Test-Mailflow [[-Identity] <ServerIdParameter>] + [-AutoDiscoverTargetMailboxServer] [-ActiveDirectoryTimeout <Int32>] [-Confirm] [-DomainController <Fqdn>] [-ErrorLatency <Int32>] [-ExecutionTimeout <Int32>] [-MonitoringContext <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### CrossPremises ``` -Test-Mailflow -CrossPremises <Boolean> [-ActiveDirectoryTimeout <Int32>] [-CrossPremisesExpirationTimeout <EnhancedTimeSpan>] [-CrossPremisesPendingErrorCount <Int32>] +Test-Mailflow -CrossPremises <Boolean> + [-ActiveDirectoryTimeout <Int32>] + [-CrossPremisesExpirationTimeout <EnhancedTimeSpan>] + [-CrossPremisesPendingErrorCount <Int32>] [-Confirm] [-DomainController <Fqdn>] [-ErrorLatency <Int32>] [-ExecutionTimeout <Int32>] [-MonitoringContext <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### TargetDatabase @@ -53,19 +58,22 @@ Test-Mailflow [[-Identity] <ServerIdParameter>] -TargetDatabase <DatabaseIdParam [-ErrorLatency <Int32>] [-ExecutionTimeout <Int32>] [-MonitoringContext <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### TargetEmailAddress ``` -Test-Mailflow [[-Identity] <ServerIdParameter>] -TargetEmailAddress <String> [-TargetEmailAddressDisplayName <String>] +Test-Mailflow [[-Identity] <ServerIdParameter>] -TargetEmailAddress <String> + [-TargetEmailAddressDisplayName <String>] [-ActiveDirectoryTimeout <Int32>] [-Confirm] [-DomainController <Fqdn>] [-ErrorLatency <Int32>] [-ExecutionTimeout <Int32>] [-MonitoringContext <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### TargetMailboxServer @@ -90,23 +98,23 @@ Test-Mailflow [[-Identity] <ServerIdParameter>] [-ErrorLatency <Int32>] [-ExecutionTimeout <Int32>] [-MonitoringContext <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Test-Mailflow cmdlet tests mail submission, transport, and delivery. The cmdlet verifies that each Mailbox server can successfully send itself a message. You can also use this cmdlet to verify that the system mailbox on one Mailbox server can successfully send a message to the system mailbox on another Mailbox server. A system mailbox is required on all servers that are involved in the test. -The test messages are available in the target user or system mailbox. The message subject is Test-Mailflow \<GUID\>, and the message body contains the text This is a Test-Mailflow probe message. +The test messages are available in the target user or system mailbox. The message subject is `Test-Mailflow <GUID>`, and the message body contains the text `This is a Test-Mailflow probe message`. The Test-Mailflow results are displayed on-screen. The interesting values in the results are: - TestMailflowResult: The values returned are typically Success or \*FAILURE\*. - - MessageLatencyTime: The time required to complete the test (deliver the test message). The value uses the syntax hh:mm:ss.ffff where hh = hours, mm = minutes, ss = seconds and ffff = fractions of a second. -You can write the Test-Mailflow results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding "\> \<filename\>" to the command. For example: +You can write the Test-Mailflow results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > <filename>` to the command. For example: `Test-Mailflow -AutoDiscoverTargetMailboxServer | ConvertTo-Csv > "C:\My Documents\test-mailflow 2020-05-01.csv"`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -126,8 +134,33 @@ This example tests message flow from the local Mailbox server where you're runni ## PARAMETERS +### -Identity +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 +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + +If you don't use this parameter, the local Mailbox server is used. + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -AutoDiscoverTargetMailboxServer -The AutoDiscoverTargetMailboxServer switch specifies whether to automatically populate a list of target Mailbox servers to which to send a test message. The task queries Active Directory to discover all Mailbox servers and then sends each server a test message. +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. When you use this switch, you can't use the CrossPremises, TargetDatabase, TargetEmailAddress or TargetMailboxServer parameters. @@ -168,9 +201,7 @@ Accept wildcard characters: False 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 - - Distinguished name (DN) - - GUID You can't use this parameter with the AutoDiscoverTargetMailboxServer, CrossPremises, TargetEmailAddress or TargetMailboxServer parameters. @@ -210,11 +241,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN When you use this parameter, you can't use the AutoDiscoverTargetMailboxServer, CrossPremises, TargetDatabase or TargetEmailAddress parameters. @@ -251,8 +279,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -348,34 +375,11 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN - -If you don't use this parameter, the local Mailbox server is used. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -429,12 +433,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Test-Message.md b/exchange/exchange-ps/exchange/Test-Message.md new file mode 100644 index 0000000000..c4b62c4ac7 --- /dev/null +++ b/exchange/exchange-ps/exchange/Test-Message.md @@ -0,0 +1,235 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Test-Message + +## SYNOPSIS +This cmdlet is functional only in the cloud-based service. + +Use the Test-Message cmdlet to simulate and report on the effects of mail flow rules (transport rules) and unified DLP rules on test email messages. Because this cmdlet introduces email into the DLP evaluation pipeline, actions such as Block, Moderate, etc. can take place on the test message. Related notifications will also be sent to any configured recipients. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### TransportRules +``` +Test-Message -Recipients <ProxyAddressCollection> -SendReportTo <RecipientIdParameter> [-TransportRules] + [-Confirm] + [-Force] + [-MessageFileData <Byte[]>] + [-Sender <SmtpAddress>] + [-UnifiedDlpRules] + [-WhatIf] + [<CommonParameters>] +``` + +### UnifiedDLPRules +``` +Test-Message -Recipients <ProxyAddressCollection> -SendReportTo <RecipientIdParameter> [-UnifiedDlpRules] + [-Confirm] + [-Force] + [-MessageFileData <Byte[]>] + [-Sender <SmtpAddress>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$data = [System.IO.File]::ReadAllBytes('C:\Data\test.eml') + +Test-Message -MessageFileData $data -Sender megan@contoso.com -Recipients adele@contoso.com -SendReportTo admin@contoso.com -TransportRules -UnifiedDlpRules +``` + +This example uses the test.eml message file at C:\Data to test mail flow rules and unified DLP rules for the sender megan@contoso.com to the recipient adele@contoso.com. The results report is sent to admin@contoso.com. + +## PARAMETERS + +### -Recipients +The Recipients parameter specifies the recipient email address to use for the test message. + +You can specify multiple email addresses separated by commas. + +```yaml +Type: ProxyAddressCollection +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendReportTo +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TransportRules +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 +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnifiedDlpRules +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 +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: SwitchParameter +Parameter Sets: TransportRules +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2013, Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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 +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessageFileData +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Sender +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Test-MigrationServerAvailability.md b/exchange/exchange-ps/exchange/Test-MigrationServerAvailability.md similarity index 79% rename from exchange/exchange-ps/exchange/move-and-migration/Test-MigrationServerAvailability.md rename to exchange/exchange-ps/exchange/Test-MigrationServerAvailability.md index cae27777e3..d37917bd9e 100644 --- a/exchange/exchange-ps/exchange/move-and-migration/Test-MigrationServerAvailability.md +++ b/exchange/exchange-ps/exchange/Test-MigrationServerAvailability.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/test-migrationserveravailability +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Test-MigrationServerAvailability @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Test-MigrationServerAvailability cmdlet to test the availability of the target server in preparation to perform cross-forest mailbox moves, migration of on-premises mailboxes to Exchange Online, or to migrate on-premises mailbox data from an IMAP server to Exchange Online mailboxes. For all migration types, the cmdlet attempts to verify the connection settings used to connect to the target server. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,35 +24,46 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Test-MigrationServerAvailability -Credentials <PSCredential> -EmailAddress <SmtpAddress> [-Autodiscover] [-ExchangeRemoteMove] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### ExchangeOutlookAnywhereAutodiscover ``` Test-MigrationServerAvailability -Credentials <PSCredential> -EmailAddress <SmtpAddress> [-Autodiscover] [-ExchangeOutlookAnywhere] + [-AcceptUntrustedCertificates] [-Confirm] [-MailboxPermission <MigrationMailboxPermission>] + [-Partition <MailboxIdParameter>] [-SourceMailboxLegacyDN <String>] [-TestMailbox <MailboxIdParameter>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### PSTImport ``` Test-MigrationServerAvailability -Credentials <PSCredential> -RemoteServer <Fqdn> [-FilePath <String>] [-PSTImport] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### ExchangeOutlookAnywhere ``` Test-MigrationServerAvailability -Credentials <PSCredential> -ExchangeServer <String> -RPCProxyServer <Fqdn> [-ExchangeOutlookAnywhere] + [-AcceptUntrustedCertificates] [-Authentication <AuthenticationMethod>] [-EmailAddress <SmtpAddress>] - [-MailboxPermission <MigrationMailboxPermission>] [-TestMailbox <MailboxIdParameter>] + [-MailboxPermission <MigrationMailboxPermission>] + [-TestMailbox <MailboxIdParameter>] [-SourceMailboxLegacyDN <String>] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### PublicFolder @@ -61,67 +71,96 @@ Test-MigrationServerAvailability -Credentials <PSCredential> -ExchangeServer <St Test-MigrationServerAvailability -Credentials <PSCredential> -PublicFolderDatabaseServerLegacyDN <String> -RPCProxyServer <Fqdn> -SourceMailboxLegacyDN <String> [-PublicFolder] [-Authentication <AuthenticationMethod>] [-Confirm] + [-Partition <MailboxIdParameter>] [-TestMailbox <MailboxIdParameter>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### ExchangeRemoteMove ``` -Test-MigrationServerAvailability -RemoteServer <Fqdn> [-Credentials <PSCredential>] [-ExchangeRemoteMove] +Test-MigrationServerAvailability -RemoteServer <Fqdn> + [-Credentials <PSCredential>] + [-ExchangeRemoteMove] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### TestEndpoint ``` Test-MigrationServerAvailability -Endpoint <MigrationEndpointIdParameter> [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### IMAP ``` Test-MigrationServerAvailability -RemoteServer <Fqdn> -Port <Int32> [-Imap] - [-Authentication <AuthenticationMethod>] [-Security <NIMAPSecurityMechanism] + [-AcceptUntrustedCertificates] + [-Authentication <AuthenticationMethod>] + [-Security <NIMAPSecurityMechanism] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### Gmail ``` -Test-MigrationServerAvailability -ServiceAccountKeyFileData <Byte[]> [-Gmail] [-EmailAddress <SmtpAddress>] +Test-MigrationServerAvailability -ServiceAccountKeyFileData <Byte[]> [-Gmail] + [-EmailAddress <SmtpAddress>] [-Confirm] + [-Partition <MailboxIdParameter>] [-TestMailbox <MailboxIdParameter>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Compliance ``` -Test-MigrationServerAvailability -Credentials <PSCredential> -EmailAddress <SmtpAddress> [-Compliance] [-RemoteServer <Fqdn>] +Test-MigrationServerAvailability -Credentials <PSCredential> -EmailAddress <SmtpAddress> [-Compliance] + [-RemoteServer <Fqdn>] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### MrsProxyPublicFolderToUnifiedGroup ``` -Test-MigrationServerAvailability -Credentials <PSCredential> -RemoteServer <Fqdn> [-PublicFolderToUnifiedGroup] [-TestMailbox <MailboxIdParameter>] +Test-MigrationServerAvailability -Credentials <PSCredential> -RemoteServer <Fqdn> + [-PublicFolderToUnifiedGroup] + [-TestMailbox <MailboxIdParameter>] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### LegacyPublicFolderToUnifiedGroup ``` -Test-MigrationServerAvailability -Credentials <PSCredential> -PublicFolderDatabaseServerLegacyDN <String> -RPCProxyServer <Fqdn> -SourceMailboxLegacyDN <String> [-PublicFolderToUnifiedGroup] +Test-MigrationServerAvailability -Credentials <PSCredential> -PublicFolderDatabaseServerLegacyDN <String> -RPCProxyServer <Fqdn> -SourceMailboxLegacyDN <String> + [-PublicFolderToUnifiedGroup] [-Authentication <AuthenticationMethod>] [-TestMailbox <MailboxIdParameter>] [-Confirm] - [-WhatIf] [<CommonParameters>] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ### MrsProxyPublicFolder ``` -Test-MigrationServerAvailability -Credentials <PSCredential> -RemoteServer <Fqdn> [-PublicFolder] [-Confirm] - [-WhatIf] [<CommonParameters>] +Test-MigrationServerAvailability -Credentials <PSCredential> -RemoteServer <Fqdn> + [-PublicFolder] + [-Confirm] + [-Partition <MailboxIdParameter>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -132,16 +171,14 @@ For an IMAP migration, this cmdlet uses the server's fully qualified domain name For an Exchange migration, this cmdlet uses one of the following settings to communicate with the on-premises server: - For Exchange 2003, it uses the server's FQDN and credentials for an administrator account that can access the server. - - For Exchange Server 2007 and later versions, you can connect using the Autodiscover service and the email address of an administrator account that can access the server. If the verification is successful, you can use the same settings to create a migration endpoint. For more information, see: - New-MigrationEndpoint - - New-MigrationBatch -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -154,14 +191,18 @@ For IMAP migrations, this example verifies the connection to the IMAP mail serve ### Example 2 ```powershell -$Credentials = Get-Credential; Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials +$Credentials = Get-Credential + +Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials ``` This example uses the Autodiscover and ExchangeOutlookAnywhere parameters to verify the connection to an on-premises Exchange server in preparation for migrating on-premises mailboxes to Exchange Online. You can use a similar example to test the connection settings for a staged Exchange migration or a cutover Exchange migration. ### Example 3 ```powershell -$Credentials = Get-Credential; Test-MigrationServerAvailability -ExchangeOutlookAnywhere -ExchangeServer exch2k3.contoso.com -Credentials $Credentials -RPCProxyServer mail.contoso.com -Authentication NTLM +$Credentials = Get-Credential + +Test-MigrationServerAvailability -ExchangeOutlookAnywhere -ExchangeServer exch2k3.contoso.com -Credentials $Credentials -RPCProxyServer mail.contoso.com -Authentication NTLM ``` This example verifies the connection to a server running Microsoft Exchange Server 2003 named exch2k3.contoso.com and uses NTLM for the authentication method. @@ -175,7 +216,9 @@ This example verifies the connection settings to a remote server using the setti ### Example 5 ```powershell -$MRSEndpoints = (Get-MigrationEndpoint).RemoteServer; Foreach ($MEP in $MRSEndpoints) {Test-MigrationServerAvailability -Endpoint $MEP} +$MRSEndpoints = (Get-MigrationEndpoint).Identity + +Foreach ($MEP in $MRSEndpoints) {Test-MigrationServerAvailability -Endpoint $MEP} ``` This example tests multiple existing endpoints. @@ -183,11 +226,11 @@ This example tests multiple existing endpoints. ## PARAMETERS ### -Autodiscover -The Autodiscover parameter specifies that the cmdlet 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. +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, ExchangeOutlookAnywhereAutoDiscove +Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online @@ -215,9 +258,9 @@ Accept wildcard characters: False ``` ### -Credentials -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) (user@example.com) format. +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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -293,7 +336,9 @@ Accept wildcard characters: False ### -ExchangeOutlookAnywhere This parameter is available only in the cloud-based service. -The ExchangeOutlookAnywhere parameter specifies a migration type for migrating on-premises mailboxes to Exchange Online. Use this parameter if you plan to migrate mailboxes to Exchange Online using a staged Exchange migration or a cutover Exchange migration. +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. + +Use this switch if you plan to migrate mailboxes to Exchange Online using a staged Exchange migration or a cutover Exchange migration. ```yaml Type: SwitchParameter @@ -309,7 +354,9 @@ Accept wildcard characters: False ``` ### -ExchangeRemoteMove -The ExchangeRemoteMove parameter specifies a type of migration where mailboxes are moved with full fidelity between two on-premises forests or between an on-premises forest and Exchange Online. Use this parameter 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. +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. ```yaml Type: SwitchParameter @@ -345,7 +392,9 @@ Accept wildcard characters: False ### -Imap This parameter is available only in the cloud-based service. -The Imap parameter specifies an IMAP migration as the migration type. This parameter is required when you want to migrate data from an IMAP mail server to Exchange Online mailboxes. +The Imap parameter specifies an IMAP migration type. You don't need to specify a value with this switch. + +This switch is required when you want to migrate data from an IMAP mail server to Exchange Online mailboxes. ```yaml Type: SwitchParameter @@ -363,7 +412,9 @@ Accept wildcard characters: False ### -Gmail This parameter is available only in the cloud-based service. -The Gmail parameter specifies Gmail migration as the migration type. This parameter is required when you want to migrate data from a G Suite tenant to Exchange Online mailboxes. +The Gmail parameter specifies Gmail as the migration type. You don't need to specify a value with this switch. + +This switch is required when you want to migrate data from a Google Workspace (formerly G Suite) tenant to Exchange Online mailboxes. ```yaml Type: SwitchParameter @@ -399,13 +450,15 @@ Accept wildcard characters: False ``` ### -PSTImport +This parameter is available only in on-premises Exchange. + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: PSTImport Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -415,13 +468,15 @@ Accept wildcard characters: False ``` ### -PublicFolder +This parameter is available only in the cloud-based service. + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: PublicFolder, MrsProxyPublicFolder Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: True Position: Named @@ -431,13 +486,15 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabaseServerLegacyDN +This parameter is available only in the cloud-based service. + This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Online Required: True Position: Named @@ -447,7 +504,7 @@ Accept wildcard characters: False ``` ### -PublicFolderToUnifiedGroup -The PublicFolderToUnifiedGroup switch specifies that the endpoint type is public folders to Office 365 groups. You don't need to specify a value with this switch. +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 @@ -466,9 +523,7 @@ Accept wildcard characters: False 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 - - Remote move (hybrid deployments) - - IMAP migration ```yaml @@ -520,7 +575,7 @@ 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. -Use the following format for the value of this parameter: ([System.IO.File]::ReadAllBytes(\<path of the JSON file\>)). For example: -CSVData ([System.IO.File]::ReadAllBytes("C:\\Users\\Administrator\\Desktop\\service-account.json")) +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). ```yaml Type: Byte[] @@ -566,6 +621,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AcceptUntrustedCertificates +This parameter is available only in the cloud-based service. + +{{ Fill AcceptUntrustedCertificates Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, IMAP +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Authentication This parameter is available only in the cloud-based service. @@ -589,8 +662,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -630,7 +702,6 @@ The MailboxPermission parameter specifies what permissions are assigned to the m Specify one of the following values for the account defined by the Credentials parameter: - FullAccess: The account has been assigned the Full-Access permission to the mailboxes that will be migrated. - - Admin: The account is a member of the Domain Admins group in the organization that hosts the mailboxes that will be migrated. This parameter isn't used for testing the connection to the remote server for a remote move migration or an IMAP migration. @@ -648,6 +719,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Partition +This parameter is available only in the cloud-based service. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MailboxIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Security This parameter is available only in the cloud-based service. @@ -705,12 +794,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Test-OAuthConnectivity.md b/exchange/exchange-ps/exchange/Test-OAuthConnectivity.md similarity index 83% rename from exchange/exchange-ps/exchange/organization/Test-OAuthConnectivity.md rename to exchange/exchange-ps/exchange/Test-OAuthConnectivity.md index e0c23d7e35..69c08e2c8a 100644 --- a/exchange/exchange-ps/exchange/organization/Test-OAuthConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-OAuthConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/test-oauthconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Test-OAuthConnectivity @@ -17,20 +16,25 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Test-OAuthConnectivity cmdlet to test OAuth authentication to partner applications for a user. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-OAuthConnectivity -Service <ModServiceType> -TargetUri <Uri> [-AppOnly] [-Confirm] - [-Mailbox <MailboxIdParameter>] [-OrganizationDomain <String>] [-ReloadConfig] [-UseCachedToken] [-WhatIf] +Test-OAuthConnectivity -Service <ModServiceType> -TargetUri <Uri> + [-AppOnly] + [-Confirm] + [-Mailbox <MailboxIdParameter>] + [-ReloadConfig] + [-UseCachedToken] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION -SharePoint, Lync and Skype for Business partner applications are automatically created in on-premises Exchange deployments. For the Test-OAuthConnectivity cmdlet to succeed for other partner applications, you first need to create the partner application by using the Configure-EnterpriseApplication.ps1 script. +SharePoint, Lync and Skype for Business partner applications are automatically created in on-premises Exchange deployments. For the Test-OAuthConnectivity cmdlet to succeed for other partner applications in on-premises deployments, you first need to create the partner application by using the Configure-EnterprisePartnerApplication.ps1 script that's available in the %ExchangeInstallPath%Scripts folder ($env:ExchangeInstallPath\Scripts in PowerShell). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -47,9 +51,7 @@ This example tests OAuth connectivity with Exchange for Gurinder Singh. The Service parameter specifies the partner application. Valid values for this parameter are: - EWS - - AutoD - - Generic ```yaml @@ -100,8 +102,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,23 +122,14 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -153,26 +145,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -OrganizationDomain -This parameter is available only in the cloud-based service. - -The OrganizationDomain parameter specifies the domain name of the Office 365 organization. For example, contoso.com. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ReloadConfig -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. +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. ```yaml Type: SwitchParameter @@ -224,12 +200,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Test-OrganizationRelationship.md b/exchange/exchange-ps/exchange/Test-OrganizationRelationship.md similarity index 80% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Test-OrganizationRelationship.md rename to exchange/exchange-ps/exchange/Test-OrganizationRelationship.md index f6d42a053d..79352a03a2 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Test-OrganizationRelationship.md +++ b/exchange/exchange-ps/exchange/Test-OrganizationRelationship.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/test-organizationrelationship -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Test-OrganizationRelationship @@ -17,54 +16,71 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Test-OrganizationRelationship cmdlet to verify that the organization relationship is properly configured and functioning as expected. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-OrganizationRelationship [[-Identity] <OrganizationRelationshipIdParameter>] - -UserIdentity <RecipientIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] +Test-OrganizationRelationship [[-Identity] <OrganizationRelationshipIdParameter>] -UserIdentity <RecipientIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Test-OrganizationRelationship cmdlet doesn't include any functional tests of federated sharing features, such as accessing user free/busy information or moving mailboxes between organizations. It only verifies that the configuration will allow these features to work correctly. -Before you can test an organization relationship, you must first create an organization relationship. For more information, see [Create an organization relationship](https://docs.microsoft.com/exchange/create-an-organization-relationship-exchange-2013-help). +Before you can test an organization relationship, you must first create an organization relationship. For more information, see [Create an organization relationship](https://learn.microsoft.com/exchange/create-an-organization-relationship-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Test-OrganizationRelationship -UserIdentity katherine@contoso.com -Identity contoso.com -Confirm +Test-OrganizationRelationship -UserIdentity katherine@fabrikam.com -Identity contoso.com -Confirm ``` -This example validates the organization relationship deployed in the Exchange organization and checks whether a delegation token can be retrieved for a mailbox for the external organization domain contoso.com. +This example validates the organization relationship deployed in the fabrikam.com on-premises Exchange organization and checks whether a delegation token can be retrieved for a mailbox in the external organization domain contoso.com. ## PARAMETERS +### -Identity +The Identity parameter specifies the organization relationship to be tested. You can use the following values: + +- Canonical name +- GUID +- Name + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -UserIdentity 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -76,15 +92,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -111,28 +126,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the organization relationship to be tested. You can use the following values: - -- Canonical name - -- GUID - -- Name - -```yaml -Type: OrganizationRelationshipIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. @@ -140,7 +133,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -154,12 +147,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Test-OutlookConnectivity.md b/exchange/exchange-ps/exchange/Test-OutlookConnectivity.md similarity index 79% rename from exchange/exchange-ps/exchange/client-access/Test-OutlookConnectivity.md rename to exchange/exchange-ps/exchange/Test-OutlookConnectivity.md index 776125b34c..2443888dbc 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-OutlookConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-OutlookConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-outlookconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-OutlookConnectivity @@ -17,14 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Test-OutlookConnectivity cmdlet to test end-to-end Microsoft Outlook client connectivity in the Microsoft Exchange organization. This includes testing for both Outlook Anywhere (RPC over HTTP) and MAPI over HTTP connections. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### Probe ``` -Test-OutlookConnectivity [-ProbeIdentity] <String> [-Credential <PSCredential>] [-Hostname <String>] - [-MailboxId <MailboxIdParameter>] [-RunFromServerId <ServerIdParameter>] [-TimeOutSeconds <String>] +Test-OutlookConnectivity [-ProbeIdentity] <String> + [-Credential <PSCredential>] + [-Hostname <String>] + [-MailboxId <MailboxIdParameter>] + [-RunFromServerId <ServerIdParameter>] + [-TimeOutSeconds <String>] [<CommonParameters>] ``` @@ -37,7 +40,8 @@ Test-OutlookConnectivity [[-Identity] <MailboxIdParameter>] -Protocol <Protocol> [-MonitoringContext] [-TotalTimeoutInMinutes <Int32>] [-TrustAnySslCert] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### RpcProxyServer @@ -46,15 +50,15 @@ Test-OutlookConnectivity [[-Identity] <MailboxIdParameter>] -GetDefaultsFromAuto [-Archive <Boolean>] [-Confirm] [-MailboxCredential <PSCredential>] + [-MonitoringContext] [-RpcAuthenticationType <RpcAuthenticationType>] [-RpcClientAccessServer <ClientAccessServerIdParameter>] [-RpcProxyAuthenticationType <RPCProxyAuthenticationType>] [-RpcProxyServer <ServerIdParameter>] [-TotalTimeoutInMinutes <Int32>] [-TrustAnySslCert] - [-WhatIf] [<CommonParameters>] - - [-MonitoringContext] + [-WhatIf] + [<CommonParameters>] ``` ### RpcTestType @@ -70,7 +74,8 @@ Test-OutlookConnectivity [[-Identity] <MailboxIdParameter>] -RpcTestType <RpcTes [-RpcProxyTestType <RpcProxyTestType>] [-TotalTimeoutInMinutes <Int32>] [-TrustAnySslCert] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### WSTestType @@ -82,29 +87,28 @@ Test-OutlookConnectivity [[-Identity] <MailboxIdParameter>] -WSTestType <Virtual [-MonitoringContext] [-TotalTimeoutInMinutes <Int32>] [-TrustAnySslCert] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION Running the Test-OutlookConnectivity cmdlet validates an Outlook connection defined by the provided parameters. The command is able to validate a single mailbox. -The Test-OutlookConnectivity cmdlet runs the same process as the monitoring probes. The Microsoft Exchange Health Manager (MSExchangeHM) service must be running and have created the Outlook probes on the machine that will be tested. You need to select one of the Outlook probe identities to run the test. Use the [Get-MonitoringItemIdentity](https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/Get-MonitoringItemIdentity) cmdlet to see what probes are active. +The Test-OutlookConnectivity cmdlet runs the same process as the monitoring probes. The Microsoft Exchange Health Manager (MSExchangeHM) service must be running and have created the Outlook probes on the machine that will be tested. You need to select one of the Outlook probe identities to run the test. Use the [Get-MonitoringItemIdentity](https://learn.microsoft.com/powershell/module/exchange/get-monitoringitemidentity) cmdlet to see what probes are active. This example lists the probes running in the backend services on a Mailbox server: `Get-MonitoringItemIdentity -Server MailboxServer1 -Identity outlook.protocol | ?{$_.Name -like '*probe'}`. This example lists the probes running in the client access services on a Mailbox server: `Get-MonitoringItemIdentity -Server MailboxServer1 -Identity outlook | ?{$_.Name -like '*probe'}`. -For more information on probes and the monitoring framework, see [Managed Availability](https://go.microsoft.com/fwlink/p/?LinkId=510838), [Managed Availability and Server Health](https://go.microsoft.com/fwlink/p/?LinkId=510839), and [Customizing Managed Availability](https://go.microsoft.com/fwlink/p/?LinkId=510840). +For more information on probes and the monitoring framework, see [Managed Availability](https://learn.microsoft.com/exchange/managed-availability-exchange-2013-help), [Managed Availability and Server Health](https://techcommunity.microsoft.com/t5/exchange-team-blog/managed-availability-and-server-health/ba-p/593180), and [Customizing Managed Availability](https://techcommunity.microsoft.com/t5/exchange-team-blog/customizing-managed-availability/ba-p/592164). By default, the cmdlet uses the test monitoring account attached to the specified probe. You may enter a different mailbox instead via the MailboxId parameter. The options and results follow. - MailboxId and Credential are not specified: Generic connectivity test against a test mailbox using the system's test credentials. - - MailboxId is specified, Credential is not: Connectivity test to the specific mailbox using the system's test credentials. - - MailboxId and Credential are both specified: You get a connectivity test to the specific mailbox, and also a test that the credentials provided are valid for that mailbox -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -146,28 +150,19 @@ In Exchange 2010, this example validates Outlook connectivity through RpcProxy o ## PARAMETERS ### -Identity -This parameter is available or functional only in 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the command looks for a test user in Active Directory that you previously created by using the New-TestCasConnectivityUser.ps1 script. @@ -185,8 +180,36 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -ProbeIdentity +The ProbeIdentity parameter specifies the probe to use. Valid values are: + +Outlook Anywhere (RPC over HTTP) probes: + +- `Outlook.Protocol\OutlookRpcSelfTestProbe`: Validates that the RPC/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity. +- `Outlook.Protocol\OutlookRpcDeepTestProbe`: Validates that the RPC/HTTP endpoint is working on the Mailbox server. It will attempt to connect to and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet. +- `Outlook.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>`: Validates that the RPC/HTTP endpoint is working on the Mailbox Server. It will attempt to connect to and log in to the mailbox in the specified mailbox database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, `"Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"`). + +MAPI over HTTP probes: + +- `OutlookMapiHttp.Protocol\OutlookMapiHttpSelfTestProbe`: Validates that the MAPI/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity. +- `OutlookMapiHttp.Protocol\OutlookMapiHttpDeepTestProbe`: Validates that the MAPI/HTTP endpoint is working on the Mailbox server. It will attempt to connect and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet. +- `OutlookMapiHttp.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>`: Validates that the MAPI/HTTP endpoint is working on the Mailbox Server. It will attempt to connect and log in to the mailbox in the specified database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, `"Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"`). + +```yaml +Type: String +Parameter Sets: Probe +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -GetDefaultsFromAutodiscover -This parameter is available or functional only in 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. @@ -204,7 +227,7 @@ Accept wildcard characters: False ``` ### -Protocol -This parameter is available or functional only in 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. @@ -222,12 +245,11 @@ Accept wildcard characters: False ``` ### -RpcTestType -This parameter is available or functional only in 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: - Server: The command uses the local server as the RPC endpoint. - - Array: The command looks for a ClientAccessArray object in the local Active Directory site. ```yaml @@ -244,14 +266,12 @@ Accept wildcard characters: False ``` ### -WSTestType -This parameter is available or functional only in 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: - Unknown (This is the default value.) - - Internal - - External ```yaml @@ -268,7 +288,7 @@ Accept wildcard characters: False ``` ### -Archive -This parameter is available or functional only in 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: @@ -290,12 +310,11 @@ Accept wildcard characters: False ``` ### -Confirm -This parameter is available or functional only in 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. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -314,7 +333,7 @@ Accept wildcard characters: False ### -Credential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -346,11 +365,11 @@ Accept wildcard characters: False ``` ### -MailboxCredential -This parameter is available or functional only in 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. -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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -371,23 +390,14 @@ 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: - Name - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) If you don't use this parameter, the command uses the test account. @@ -406,9 +416,11 @@ Accept wildcard characters: False ``` ### -MonitoringContext -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. -The MonitoringContext switch specifies whether the command returns additional information that can be used with Microsoft System Center Operations Manager. You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -423,47 +435,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ProbeIdentity -The ProbeIdentity parameter specifies the probe to use. Valid values are: - -Outlook Anywhere (RPC over HTTP) probes: - -- Outlook.Protocol\OutlookRpcSelfTestProbe: Validates that the RPC/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity. - -- Outlook.Protocol\OutlookRpcDeepTestProbe: Validates that the RPC/HTTP endpoint is working on the Mailbox server. It will attempt to connect to and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet. - -- Outlook.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>: Validates that the RPC/HTTP endpoint is working on the Mailbox Server. It will attempt to connect to and log in to the mailbox in the specified mailbox database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, "Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"). - -MAPI over HTTP probes: - -- OutlookMapiHttp.Protocol\OutlookMapiHttpSelfTestProbe: Validates that the MAPI/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity. - -- OutlookMapiHttp.Protocol\OutlookMapiHttpDeepTestProbe: Validates that the MAPI/HTTP endpoint is working on the Mailbox server. It will attempt to connect and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet. - -- OutlookMapiHttp.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>: Validates that the MAPI/HTTP endpoint is working on the Mailbox Server. It will attempt to connect and log in to the mailbox in the specified database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, "Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"). - -```yaml -Type: String -Parameter Sets: Probe -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -RpcAuthenticationType -This parameter is available or functional only in 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: - NTLM - - Kerberos - - Negotiate The default value is Negotiate. @@ -482,7 +460,7 @@ Accept wildcard characters: False ``` ### -RpcClientAccessServer -This parameter is available or functional only in 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. @@ -500,7 +478,7 @@ Accept wildcard characters: False ``` ### -RpcProxyAuthenticationType -This parameter is available or functional only in 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. @@ -518,7 +496,7 @@ Accept wildcard characters: False ``` ### -RpcProxyServer -This parameter is available or functional only in 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. @@ -536,13 +514,12 @@ Accept wildcard characters: False ``` ### -RpcProxyTestType -This parameter is available or functional only in 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: -- Internal: Refers to the local computer name (https://\<localcomputername\>, for example, https://CAS01). - -- External: Refers to a public namespace (the external HTTP URL on the /rpc virtual directory, for example, https://mail.contoso.com). +- Internal: Refers to the local computer name (`https://<localcomputername>`, for example, `https://CAS01`). +- External: Refers to a public namespace (the external HTTP URL on the /rpc virtual directory, for example, `https://mail.contoso.com`). ```yaml Type: RpcProxyTestType @@ -590,7 +567,7 @@ Accept wildcard characters: False ``` ### -TotalTimeoutInMinutes -This parameter is available or functional only in 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. @@ -608,9 +585,11 @@ Accept wildcard characters: False ``` ### -TrustAnySslCert -This parameter is available or functional only in 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. -The TrustAnySslCert switch specifies whether to ignore any Secure Sockets Layer (SSL) certificate warnings. 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. ```yaml Type: SwitchParameter @@ -626,7 +605,7 @@ Accept wildcard characters: False ``` ### -WhatIf -This parameter is available or functional only in 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. @@ -648,12 +627,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Test-OutlookWebServices.md b/exchange/exchange-ps/exchange/Test-OutlookWebServices.md new file mode 100644 index 0000000000..a9eae33fd1 --- /dev/null +++ b/exchange/exchange-ps/exchange/Test-OutlookWebServices.md @@ -0,0 +1,293 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Test-OutlookWebServices + +## SYNOPSIS +This cmdlet is functional only in Exchange Server 2010. + +Use the Test-OutlookWebServices cmdlet to verify the Autodiscover service settings for Microsoft Outlook on a computer running Microsoft Exchange Server 2010 that has the Client Access server role installed. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +### Default +``` +Test-OutlookWebServices [[-Identity] <RecipientIdParameter>] + [-ClientAccessServer <ClientAccessServerIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-MonitoringContext <Boolean>] + [-TargetAddress <RecipientIdParameter[]>] + [-WhatIf] + [<CommonParameters>] +``` + +### AutoDiscoverServer +``` +Test-OutlookWebServices [[-Identity] <MailboxIdParameter>] -AutoDiscoverServer <ClientAccessServerIdParameter> + [-Confirm] + [-MailboxCredential <PSCredential>] + [-TrustAnySSLCertificate] + [-WhatIf] + [<CommonParameters>] +``` + +### ClientAccessServer +``` +Test-OutlookWebServices [[-Identity] <MailboxIdParameter>] [-ClientAccessServer <ClientAccessServerIdParameter>] + [-Confirm] + [-MailboxCredential <PSCredential>] + [-TrustAnySSLCertificate] + [-WhatIf] + [<CommonParameters>] +``` + +### MonitoringContext +``` +Test-OutlookWebServices [[-Identity] <MailboxIdParameter>] [-MonitoringContext] + [-Confirm] + [-MailboxCredential <PSCredential>] + [-TrustAnySSLCertificate] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The Test-OutlookWebServices cmdlet uses a specified address to verify that the Outlook provider is configured correctly. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Test-OutlookWebServices -Identity:holly@contoso.com +``` + +This example verifies the service information that's returned to the Outlook client from the Autodiscover service for the user holly@contoso.com. The code example verifies information for the following services: + +- Availability service +- Outlook Anywhere +- Offline address book +- Unified Messaging + +The example tests for a connection to each service. The example also submits a request to the Availability service for the user holly@contoso.com to determine whether the user's free/busy information is being returned correctly from the Client Access server to the Outlook client. + +## PARAMETERS + +### -Identity +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 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AutoDiscoverServer +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: + +- Name (for example, Exchange01) +- Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com) +- Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01) +- GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942) + +You can't use this parameter with the ClientAccessServer parameter. + +```yaml +Type: ClientAccessServerIdParameter +Parameter Sets: AutoDiscoverServer +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ClientAccessServer +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. + +You can use any value that uniquely identifies the server. For example: + +- Name +- Distinguished name (DN) +- ExchangeLegacyDN +- GUID + +You can't use this parameter with the AutoDiscoverServer parameter. + +```yaml +Type: ClientAccessServerIdParameter +Parameter Sets: Default, ClientAccessServer +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -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`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailboxCredential +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). + +```yaml +Type: PSCredential +Parameter Sets: AutoDiscoverServer, ClientAccessServer, MonitoringContext +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MonitoringContext +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. + +```yaml +Type: Boolean +Parameter Sets: Default +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetAddress +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrustAnySSLCertificate +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. + +```yaml +Type: SwitchParameter +Parameter Sets: AutoDiscoverServer, ClientAccessServer, MonitoringContext +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/client-access/Test-OwaConnectivity.md b/exchange/exchange-ps/exchange/Test-OwaConnectivity.md similarity index 84% rename from exchange/exchange-ps/exchange/client-access/Test-OwaConnectivity.md rename to exchange/exchange-ps/exchange/Test-OwaConnectivity.md index 3cbe89cb46..3f6dbf78e8 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-OwaConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-OwaConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-owaconnectivity +online version: https://learn.microsoft.com/powershell/module/exchange/test-owaconnectivity applicable: Exchange Server 2010 title: Test-OwaConnectivity schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Test-OwaConnectivity @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Test-OwaConnectivity cmdlet to verify that Microsoft Office Outlook Web App is running as expected. The Test-OwaConnectivity cmdlet can be used to test Outlook Web App connectivity for all Microsoft Exchange Server 2010 virtual directories on a specified Client Access server for all mailboxes on servers running Exchange that are in the same Active Directory site. The Test-OwaConnectivity cmdlet can also be used to test the connectivity for an individual Exchange Outlook Web App URL. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,12 +30,18 @@ Test-OwaConnectivity [-URL] <String> -MailboxCredential <PSCredential> [-ResetTestAccountCredentials] [-Timeout <UInt32>] [-TrustAnySSLCertificate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Identity ``` -Test-OwaConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-MailboxServer <ServerIdParameter>] [-MonitoringContext] [-RSTEndpoint <String>] [-TestType <OwaConnectivityTestType>] [-VirtualDirectoryName <String>] +Test-OwaConnectivity [[-ClientAccessServer] <ServerIdParameter>] + [-MailboxServer <ServerIdParameter>] + [-MonitoringContext] + [-RSTEndpoint <String>] + [-TestType <OwaConnectivityTestType>] + [-VirtualDirectoryName <String>] [-AllowUnsecureAccess] [-Confirm] [-DomainController <Fqdn>] @@ -44,7 +49,8 @@ Test-OwaConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-MailboxServer [-ResetTestAccountCredentials] [-Timeout <UInt32>] [-TrustAnySSLCertificate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -62,7 +68,7 @@ If the command encounters a virtual directory that doesn't require Secure Socket The Test-OwaConnectivity cmdlet can be run as a one-time interactive task or as a scheduled task under Microsoft System Center Operations Manager 2007 control. To run the Test-OwaConnectivity cmdlet as a System Center Operations Manager 2007 task, the Client Access test mailbox must be available on the Mailbox servers that the cmdlet tests against. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,23 +88,23 @@ This example tests the connectivity of a specific Client Access server Contoso12 ## PARAMETERS -### -MailboxCredential -The MailboxCredential parameter specifies the mailbox credential for a single URL test. +### -ClientAccessServer +This parameter is available only in Exchange Server 2010 -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://go.microsoft.com/fwlink/p/?linkId=142122). +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. -The MailboxCredential parameter is required only when using the URL parameter. +Don't use this parameter with the URL parameter. ```yaml -Type: PSCredential -Parameter Sets: URL +Type: ServerIdParameter +Parameter Sets: Identity Aliases: Applicable: Exchange Server 2010 -Required: True -Position: Named +Required: False +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` @@ -122,45 +128,48 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AllowUnsecureAccess -The AllowUnsecureAccess parameter specifies whether virtual directories that don't require SSL are tested. If the AllowUnsecureAccess parameter is included, it enables virtual directories that don't require SSL to be tested. If this parameter isn't included, the command skips virtual directories that don't require SSL, and an error is generated. +### -MailboxCredential +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). + +The MailboxCredential parameter is required only when using the URL parameter. ```yaml -Type: SwitchParameter -Parameter Sets: (All) +Type: PSCredential +Parameter Sets: URL Aliases: Applicable: Exchange Server 2010 -Required: False +Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` -### -ClientAccessServer -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. +### -AllowUnsecureAccess +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. -Don't use this parameter with the URL parameter. +If you don't use this switch, the command skips virtual directories that don't require SSL, and an error is generated. ```yaml -Type: ServerIdParameter -Parameter Sets: Identity +Type: SwitchParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -227,7 +236,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter shows you what information is returned to System Center Operations Manager 2007. When Operations Manager 2007 executes the Test-OwaConnectivity cmdlet, it requires additional information to be returned. By setting this parameter to $true, you can see exactly what would be returned to Operations Manager 2007. This parameter is informational only and has no effect on Operations Manager 2007. +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). ```yaml Type: SwitchParameter @@ -243,7 +254,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -307,7 +320,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate parameter specifies whether to check an internal URL without generating an SSL certificate validation error. The TrustAnySSLCertificate parameter allows SSL certificate validation failures to not be reported. This is useful for testing internal URLs because Internet Information Services (IIS) doesn't support assigning multiple certificates for a single virtual directory. If a directory has different URLs for internal and external access and has a certificate, that certificate is usually for the external URL. This parameter lets the task check an internal URL without generating an error when the certificate doesn't match the URL. +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. ```yaml Type: SwitchParameter @@ -359,12 +374,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/client-access/Test-PopConnectivity.md b/exchange/exchange-ps/exchange/Test-PopConnectivity.md similarity index 82% rename from exchange/exchange-ps/exchange/client-access/Test-PopConnectivity.md rename to exchange/exchange-ps/exchange/Test-PopConnectivity.md index 0051ab1d21..fedc41347a 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-PopConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-PopConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-popconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-PopConnectivity @@ -17,18 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Test-PopConnectivity cmdlet to verify that the Microsoft Exchange POP3 service is working as expected. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-PopConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-Confirm] - [-ConnectionType <ProtocolConnectionType>] [-DomainController <Fqdn>] [-LightMode] - [-MailboxCredential <PSCredential>] [-MailboxServer <ServerIdParameter>] [-MonitoringContext] - [-PerConnectionTimeout <Int32>] [-PortClientAccessServer <Int32>] [-ResetTestAccountCredentials] - [-Timeout <UInt32>] [-TrustAnySSLCertificate] [-WhatIf] [<CommonParameters>] +Test-PopConnectivity [[-ClientAccessServer] <ServerIdParameter>] + [-Confirm] + [-ConnectionType <ProtocolConnectionType>] + [-DomainController <Fqdn>] + [-LightMode] + [-MailboxCredential <PSCredential>] + [-MailboxServer <ServerIdParameter>] + [-MonitoringContext] + [-PerConnectionTimeout <Int32>] + [-PortClientAccessServer <Int32>] + [-ResetTestAccountCredentials] + [-Timeout <UInt32>] + [-TrustAnySSLCertificate] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -41,22 +50,15 @@ The first time you use this cmdlet, you might be required to create a test user. The test results are displayed on-screen. The cmdlet returns the following information. - CasServer: The Exchange server that the client connected to. - - LocalSite: The name of the local Active Directory site. - - Scenario: The operations that are tested. Test POP3 Connectivity connects to the server using the POP3 protocol, searches for the test message, and deletes the test message. - - Result: The values returned are typically Success, Skipped or Failure. - - Latency(MS): The time required to complete the test in milliseconds. - - Error: Any error messages that were encountered. -You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example: +You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-PopConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\POP Test.html"`. -Test-PopConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\POP Test.html" - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,11 +84,8 @@ The ClientAccessServer parameter specifies the Exchange server to test. This ser You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID ```yaml @@ -105,8 +104,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -126,9 +124,7 @@ Accept wildcard characters: False The ConnectionType parameter specifies the type of connection that's used to connect to the POP3 service. Valid values are: - Plaintext - - Ssl - - Tls ```yaml @@ -181,7 +177,7 @@ Accept wildcard characters: False ### -MailboxCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -197,16 +193,13 @@ Accept wildcard characters: False ``` ### -MailboxServer -The MailboxServer parameter specifies the Exchange 2016 or Exchange 2013 Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. +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: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID If you don't use this parameter, connections to all Mailbox servers in the local Active Directory site are tested. @@ -225,7 +218,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -275,7 +270,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -309,7 +306,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether to ignore Secure Sockets Layer (SSL) certificate validation failures. You don't need to specify a value with this switch. +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. @@ -347,12 +344,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Test-PowerShellConnectivity.md b/exchange/exchange-ps/exchange/Test-PowerShellConnectivity.md similarity index 81% rename from exchange/exchange-ps/exchange/client-access/Test-PowerShellConnectivity.md rename to exchange/exchange-ps/exchange/Test-PowerShellConnectivity.md index df41b0ab3b..b418302280 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-PowerShellConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-PowerShellConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-powershellconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-PowerShellConnectivity @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the Test-PowerShellConnectivity cmdlet to test client connectivity to Exchange remote PowerShell virtual directories. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -33,12 +32,15 @@ Test-PowerShellConnectivity -ConnectionUri <Uri> -TestCredential <PSCredential> [-MonitoringContext] [-ResetTestAccountCredentials] [-TrustAnySSLCertificate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Identity ``` -Test-PowerShellConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-TestType <OwaConnectivityTestType>] [-VirtualDirectoryName <String>] +Test-PowerShellConnectivity [[-ClientAccessServer] <ServerIdParameter>] + [-TestType <OwaConnectivityTestType>] + [-VirtualDirectoryName <String>] [-Authentication <AuthenticationMethod>] [-Confirm] [-DomainController <Fqdn>] @@ -46,7 +48,8 @@ Test-PowerShellConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-TestTy [-MonitoringContext] [-ResetTestAccountCredentials] [-TrustAnySSLCertificate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -59,22 +62,15 @@ The first time you use this cmdlet, you might be required to create a test user. The test results are displayed on-screen. The cmdlet returns the following information. - CasServer: The Exchange server that the client connected to. - - LocalSite: The name of the local Active Directory site. - - Scenario: The operations that are tested. Values are: Logon User. - - Result: The values returned are typically Success, Skipped or Failure. - - Latency(MS): The time required to complete the test in milliseconds. - - Error: Any error messages that were encountered. -You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example: +You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-PowerShellConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\PowerShell Test.html"`. -Test-PowerShellConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\PowerShell Test.html" - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,17 +83,44 @@ This example tests the PowerShell (Default Web Site) virtual directory on the MB ### Example 2 ```powershell -$UserCredentials = Get-Credential; Test-PowerShellConnectivity -ConnectionUri https://contoso.com/powershell -TestCredential $UserCredentials -Authentication Basic +$UserCredentials = Get-Credential + +Test-PowerShellConnectivity -ConnectionUri https://contoso.com/powershell -TestCredential $UserCredentials -Authentication Basic ``` -This example tests the remote PowerShell virtual directory that's available at https://contoso.com/powershell. A mismatch between the SSL certificate and the URL isn't expected, so the TrustAnySSLCertificate switch isn't used. The virtual directory is configured to use Basic authentication. +This example tests the remote PowerShell virtual directory that's available at `https://contoso.com/powershell`. A mismatch between the SSL certificate and the URL isn't expected, so the TrustAnySSLCertificate switch isn't used. The virtual directory is configured to use Basic authentication. The credentials that are used to connect to the virtual directory are stored in the $UserCredentials variable. The test is then run as previously described. ## PARAMETERS +### -ClientAccessServer +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: + +- Name +- Distinguished name (DN) +- ExchangeLegacyDN +- GUID + +You can't use this parameter with the ConnectionUri parameter. + +```yaml +Type: ServerIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ConnectionUri -The ConnectionUri parameter specifies the URL of the remote PowerShell virtual directory to test, for example, https://contoso.com/powershell. +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. @@ -117,7 +140,7 @@ Accept wildcard characters: False ### -TestCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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). You can only use this parameter with the ConnectionUri parameter. @@ -138,15 +161,10 @@ Accept wildcard characters: False The Authentication parameter specifies the type of authentication that's used to connect. Valid values are: - Default - - Basic - - Credssp - - Digest - - Kerberos - - Negotiate ```yaml @@ -162,39 +180,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ClientAccessServer -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: - -- Name - -- Distinguished name (DN) - -- ExchangeLegacyDN - -- GUID - -You can't use this parameter with the ConnectionUri parameter. - -```yaml -Type: ServerIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - ### -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. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -227,16 +216,13 @@ Accept wildcard characters: False ``` ### -MailboxServer -The MailboxServer parameter specifies the Exchange 2016 or Exchange 2013 Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. +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: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID If you don't use this parameter, connections to all Mailbox servers in the local Active Directory site are tested. @@ -255,7 +241,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -271,7 +259,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -305,7 +295,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether to ignore Secure Sockets Layer (SSL) certificate validation failures. You don't need to specify a value with this switch. +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. @@ -361,12 +351,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/database-availability-groups/Test-ReplicationHealth.md b/exchange/exchange-ps/exchange/Test-ReplicationHealth.md similarity index 86% rename from exchange/exchange-ps/exchange/database-availability-groups/Test-ReplicationHealth.md rename to exchange/exchange-ps/exchange/Test-ReplicationHealth.md index c112a85ec7..384af71e00 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Test-ReplicationHealth.md +++ b/exchange/exchange-ps/exchange/Test-ReplicationHealth.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/test-replicationhealth +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-ReplicationHealth @@ -17,21 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Test-ReplicationHealth cmdlet to check all aspects of replication and replay, or to provide status for a specific Mailbox server in a database availability group (DAG). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-ReplicationHealth [[-Identity] <ServerIdParameter>] [-ActiveDirectoryTimeout <Int32>] [-Confirm] - [-DomainController <Fqdn>] [-MonitoringContext <Boolean>] [-OutputObjects] - [-TransientEventSuppressionWindow <UInt32>] [-WhatIf] - [-DatabaseAvailabilityGroup <DatabaseAvailabilityGroupIdParameter>] [<CommonParameters>] +Test-ReplicationHealth [[-Identity] <ServerIdParameter>] + [-ActiveDirectoryTimeout <Int32>] + [-Confirm] + [-DatabaseAvailabilityGroup <DatabaseAvailabilityGroupIdParameter>] + [-DomainController <Fqdn>] + [-MonitoringContext <Boolean>] + [-OutputObjects] + [-TransientEventSuppressionWindow <UInt32>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Test-ReplicationHealth cmdlet is designed for the proactive monitoring of continuous replication and the continuous replication pipeline, the availability of Active Manager and the health and status of the underlying cluster service, quorum and network components. The Test-ReplicationHealth cmdlet can be run locally or remotely against any Mailbox server in a DAG. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,6 +49,29 @@ This example tests the health of replication for the Mailbox server MBX1. ## PARAMETERS +### -Identity +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 +- FQDN +- Distinguished name (DN) +- ExchangeLegacyDN + +You can't use this parameter with the DatabaseAvailabilityGroup parameter. + +```yaml +Type: ServerIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + ### -ActiveDirectoryTimeout 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. @@ -63,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -80,6 +107,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DatabaseAvailabilityGroup +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 +- Distinguished name (DN) +- GUID + +You can't use this parameter with the Identity parameter. + +```yaml +Type: DatabaseAvailabilityGroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DomainController The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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 +146,10 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -160,67 +212,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- FQDN - -- Distinguished name (DN) - -- ExchangeLegacyDN - -You can't use this parameter with the DatabaseAvailabilityGroup parameter. - -```yaml -Type: ServerIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DatabaseAvailabilityGroup -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 - -- Distinguished name (DN) - -- GUID - -You can't use this parameter with the Identity parameter. - -```yaml -Type: DatabaseAvailabilityGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Test-SenderId.md b/exchange/exchange-ps/exchange/Test-SenderId.md similarity index 91% rename from exchange/exchange-ps/exchange/antispam-antimalware/Test-SenderId.md rename to exchange/exchange-ps/exchange/Test-SenderId.md index 4f258146f7..53db8aa93a 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Test-SenderId.md +++ b/exchange/exchange-ps/exchange/Test-SenderId.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/test-senderid +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-SenderId @@ -17,20 +16,24 @@ This cmdlet is available only in on-premises Exchange. Use the Test-SenderId cmdlet to test whether a specified IP address is the legitimate sending address for a specified SMTP address. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-SenderId -IPAddress <IPAddress> -PurportedResponsibleDomain <SmtpDomain> [-Confirm] - [-DomainController <Fqdn>] [-HelloDomain <String>] [-Server <ServerIdParameter>] [-WhatIf] +Test-SenderId -IPAddress <IPAddress> -PurportedResponsibleDomain <SmtpDomain> + [-Confirm] + [-DomainController <Fqdn>] + [-HelloDomain <String>] + [-Server <ServerIdParameter>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION The Test-SenderId cmdlet provides the results of a Sender ID check for the IP address and the corresponding domain name that you specify. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -78,8 +81,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -133,11 +135,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -176,12 +175,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/server-health-and-performance/Test-ServiceHealth.md b/exchange/exchange-ps/exchange/Test-ServiceHealth.md similarity index 85% rename from exchange/exchange-ps/exchange/server-health-and-performance/Test-ServiceHealth.md rename to exchange/exchange-ps/exchange/Test-ServiceHealth.md index dd087e0a90..1016e36a2c 100644 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Test-ServiceHealth.md +++ b/exchange/exchange-ps/exchange/Test-ServiceHealth.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/test-servicehealth +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-ServiceHealth @@ -17,19 +16,24 @@ This cmdlet is available only in on-premises Exchange. Use the Test-ServiceHealth cmdlet to test whether all the Microsoft Windows services that Exchange requires on a server have started. The Test-ServiceHealth cmdlet returns an error for any service required by a configured role when the service is set to start automatically and isn't currently running. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-ServiceHealth [[-Server] <ServerIdParameter>] [-ActiveDirectoryTimeout <Int32>] [-Confirm] - [-DomainController <Fqdn>] [-MonitoringContext <Boolean>] [-WhatIf] [<CommonParameters>] +Test-ServiceHealth [[-Server] <ServerIdParameter>] + [-ActiveDirectoryTimeout <Int32>] + [-Confirm] + [-DomainController <Fqdn>] + [-MonitoringContext <Boolean>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION This cmdlet isn't supported on Exchange 2013 Client Access servers (the cmdlet will return unexpected output). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -46,11 +50,8 @@ This example uses the Test-ServiceHealth command without parameters to test the 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN If you don't use this parameter, the command is run on the local server. @@ -87,8 +88,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -123,7 +123,10 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -159,12 +162,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Test-ServicePrincipalAuthorization.md b/exchange/exchange-ps/exchange/Test-ServicePrincipalAuthorization.md new file mode 100644 index 0000000000..896490cd63 --- /dev/null +++ b/exchange/exchange-ps/exchange/Test-ServicePrincipalAuthorization.md @@ -0,0 +1,148 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Test-ServicePrincipalAuthorization + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Test-ServicePrincipalAuthorization cmdlet to test the access granted by role-based access control (RBAC) for Applications. For more information, see [Role Based Access Control for Applications in Exchange Online](https://learn.microsoft.com/Exchange/permissions-exo/application-rbac). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Test-ServicePrincipalAuthorization [-Identity] <ServicePrincipalIdParameter> + [-Confirm] + [-Resource <UserIdParameter>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Test-ServicePrincipalAuthorization -Identity "DemoB" -Resource "Mailbox A" | Format-Table + +RoleName GrantedPermissions AllowedResourceScope ScopeType InScope +-------- ------------------ -------------------- --------- ------ +Application Mail.Read Mail.Read Canadian Employees CustomRecipientScope True +Application Calendars.Read Calendars.Read 4d819ce9-9257-44.. AdministrativeUnit False +Application Contacts.Read Contacts.Read Organization Organization True +``` + +This example tests if this service principal (the app named "DemoB") can exercise each of its assigned permissions against the target mailbox named "Mailbox A." The membership in the scope is indicated by the InScope column. + +### Example 2 +```powershell +PS C:\> Test-ServicePrincipalAuthorization -Identity "DemoB" | Format-Table + +RoleName GrantedPermissions AllowedResourceScope ScopeType InScope +-------- ------------------ -------------------- --------- ------ +Application Mail.Read Mail.Read Canadian Employees CustomRecipientScope Not Run +Application Calendars.Read Calendars.Read 4d819ce9-9257-44.. AdministrativeUnit Not Run +Application Contacts.Read Contacts.Read Organization Organization Not Run +``` + +This example tests the entitlement of the app named "DemoB", including which permissions it has at which scopes. Because the command doesn't use the Resource parameter, the scope membership check is not run. + +## PARAMETERS + +### -Identity +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 +- Distinguished name (DN) +- GUID +- AppId +- ServiceId + +```yaml +Type: ServicePrincipalIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Confirm +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Resource +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Test-SiteMailbox.md b/exchange/exchange-ps/exchange/Test-SiteMailbox.md similarity index 89% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Test-SiteMailbox.md rename to exchange/exchange-ps/exchange/Test-SiteMailbox.md index 89641d60cc..249202e6e8 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Test-SiteMailbox.md +++ b/exchange/exchange-ps/exchange/Test-SiteMailbox.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/test-sitemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-SiteMailbox ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Test-SiteMailbox cmdlet to test the site mailbox to Microsoft SharePoint connectivity and to test whether users have the correct permissions to use a site mailbox. This cmdlet should be used for troubleshooting and diagnostic purposes. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -28,13 +29,14 @@ Test-SiteMailbox [[-Identity] <RecipientIdParameter>] [-RequestorIdentity <RecipientIdParameter>] [-SharePointUrl <Uri>] [-UseAppTokenOnly] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION If you don't specify the RequestorIdentity parameter, the command uses the identification of the user running this command. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,35 +63,40 @@ This example tests a specific user's ability to access a SharePoint site by usin ## PARAMETERS -### -BypassOwnerCheck -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. +### -Identity +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: -If you run the command without this parameter and you aren't a member or owner of the site mailbox, then the command will fail. +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +You can't use this parameter with the SharePointUrl parameter. ```yaml -Type: SwitchParameter +Type: RecipientIdParameter Parameter Sets: (All) Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +### -BypassOwnerCheck +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. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +If you don't use this switch, and you aren't a member or owner of the site mailbox, the command will fail. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: cf +Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -99,33 +106,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID +### -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. -You can't use this parameter with the SharePointUrl parameter. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: RecipientIdParameter +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -133,15 +129,10 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID You can't use this parameter with the UseAppTokenOnly parameter. @@ -182,7 +173,7 @@ Accept wildcard characters: False ### -UseAppTokenOnly 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 parameter with the RequestorIdentity parameter. +You can't use this switch with the RequestorIdentity parameter. ```yaml Type: SwitchParameter @@ -218,12 +209,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mail-flow/Test-SmtpConnectivity.md b/exchange/exchange-ps/exchange/Test-SmtpConnectivity.md similarity index 84% rename from exchange/exchange-ps/exchange/mail-flow/Test-SmtpConnectivity.md rename to exchange/exchange-ps/exchange/Test-SmtpConnectivity.md index fd23b2a905..68097adcaf 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Test-SmtpConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-SmtpConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/test-smtpconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-SmtpConnectivity @@ -17,33 +16,32 @@ This cmdlet is available only in on-premises Exchange. Use the Test-SmtpConnectivity cmdlet to diagnose whether an SMTP connection can successfully be established to the Receive connectors on a specific server. Although you can run this cmdlet manually to verify SMTP connectivity for a specified server, it's primarily used by Microsoft System Center Operations Manager 2007 to test your transport servers' ability to receive SMTP connections to each of the bindings on all the Receive connectors on those servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-SmtpConnectivity [[-Identity] <ServerIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-MonitoringContext <Boolean>] [-WhatIf] [<CommonParameters>] +Test-SmtpConnectivity [[-Identity] <ServerIdParameter>] + [-Confirm] + [-DomainController <Fqdn>] + [-MonitoringContext <Boolean>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION When you run the Test-SmtpConnectivity cmdlet against a Mailbox server, the cmdlet attempts to establish an SMTP connection to all bindings of all Receive connectors hosted on that server. For each attempt, the cmdlet returns the following information: - Server: The name of the server that hosts the Receive connector. - - ReceiveConnector: The name of the Receive connector to which the SMTP connection was attempted. - - Binding: The binding that was configured on the Receive connector. - - EndPoint: The actual IP address and port to which the SMTP connection was attempted. - - StatusCode: The result of the connection attempt. This can be one of the following values: Success, Unable to connect, Transient error, Permanent error, External error. - - Details: The actual response received from the server being tested. If the connection attempt isn't successful, this field contains an error string. -The Test-SmtpConnectivity results are displayed on-screen. You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding "\> \<filename\>" to the command. For example: +You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > <filename>` to the command. For example: `Test-SmtpConnectivity Mailbox01 | ConvertTo-Csv > "C:\My Documents\SMTP Test.csv"`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -63,35 +61,41 @@ This example verifies SMTP connectivity for all Receive connectors on all Mailbo ## PARAMETERS -### -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. +### -Identity +The Identity parameter specifies the transport server for which the cmdlet verifies SMTP connectivity . -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. +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: -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Name +- FQDN +- Distinguished name (DN) +- Exchange Legacy DN + + If you don't use this parameter, all Receive connectors on the local server are tested. ```yaml -Type: SwitchParameter +Type: ServerIdParameter Parameter Sets: (All) -Aliases: cf +Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. +### -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. -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. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml -Type: Fqdn +Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: cf Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False @@ -101,36 +105,29 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -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: - -- Name - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - If you don't use this parameter, all Receive connectors on the local server are tested. +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. ```yaml -Type: ServerIdParameter +Type: Fqdn Parameter Sets: (All) Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean @@ -166,12 +163,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Test-SystemHealth.md b/exchange/exchange-ps/exchange/Test-SystemHealth.md similarity index 80% rename from exchange/exchange-ps/exchange/organization/Test-SystemHealth.md rename to exchange/exchange-ps/exchange/Test-SystemHealth.md index 34764b0b47..8248f8de34 100644 --- a/exchange/exchange-ps/exchange/organization/Test-SystemHealth.md +++ b/exchange/exchange-ps/exchange/Test-SystemHealth.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/test-systemhealth +online version: https://learn.microsoft.com/powershell/module/exchange/test-systemhealth applicable: Exchange Server 2010 title: Test-SystemHealth schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Test-SystemHealth @@ -17,21 +16,38 @@ This cmdlet is available only in Exchange Server 2010. Use the Test-SystemHealth cmdlet to gather data about your Microsoft Exchange system and to analyze the data according to best practices. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Test-SystemHealth [-ADCredentials <PSCredential>] [-Analyze] [-Collect] [-ConfigurationData <Byte[]>] - [-ConfigurationFileLocation <LongPath>] [-Confirm] [-Description <String>] [-DomainController <Fqdn>] - [-DownloadConfigurationUpdates] [-ExchangeCredentials <PSCredential>] [-Export] [-GenerateEvents] - [-GenerateSQMData] [-MaxThreads <Int32>] [-MergeFileLocation <LongPath>] [-OutData] - [-OutFileLocation <LongPath>] [-Roles <String[]>] [-ScanType <String>] [-ServerList <String[]>] - [-Timeout <EnhancedTimeSpan>] [-WhatIf] [<CommonParameters>] +Test-SystemHealth [-ADCredentials <PSCredential>] + [-Analyze] + [-Collect] + [-ConfigurationData <Byte[]>] + [-ConfigurationFileLocation <LongPath>] + [-Confirm] + [-Description <String>] + [-DomainController <Fqdn>] + [-DownloadConfigurationUpdates] + [-ExchangeCredentials <PSCredential>] + [-Export] + [-GenerateEvents] + [-GenerateSQMData] + [-MaxThreads <Int32>] + [-MergeFileLocation <LongPath>] + [-OutData] + [-OutFileLocation <LongPath>] + [-Roles <String[]>] + [-ScanType <String>] + [-ServerList <String[]>] + [-Timeout <EnhancedTimeSpan>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,17 +60,19 @@ This example gathers data about your Exchange system. ### Example 2 ```powershell -$temp=Test-SystemHealth -OutData; Set-Content -Value $temp.FileData -Path d:\temp\SystemHealthOutData.xml -Encoding Byte +$SysHealth = Test-SystemHealth -OutData + +[System.IO.File]::WriteAllBytes('D:\temp\SystemHealthOutData.xml', $SysHealth.FileData) ``` -This example saves the output data as a byte stream to the temporary variable $temp. Then the content is written to the file SystemHealthOutData.xml using the Set-Content cmdlet. +This example saves the output data as a byte stream to the variable named $SysHealth. The content is then written to the SystemHealthOutData.xml file in the D:\\temp folder. ## PARAMETERS ### -ADCredentials 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -70,7 +88,7 @@ Accept wildcard characters: False ``` ### -Analyze -The Analyze parameter specifies whether to enable analysis on the data gathered. A value of $true enables analysis. The default value is $true. +The Analyze switch enables analysis on the data gathered. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -86,7 +104,7 @@ Accept wildcard characters: False ``` ### -Collect -The Collect parameter specifies whether to enable data collection. A value of $true enables data collection. The default value is $true. +The Collect switch enables data collection. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -136,8 +154,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -186,7 +203,7 @@ Accept wildcard characters: False ``` ### -DownloadConfigurationUpdates -The DownloadConfigurationUpdates parameter checks for and downloads newer versions of the configuration file. The default value is $true, which checks for and downloads newer versions of the configuration file. +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 @@ -204,7 +221,7 @@ Accept wildcard characters: False ### -ExchangeCredentials 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://go.microsoft.com/fwlink/p/?linkId=142122). +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 @@ -220,7 +237,7 @@ Accept wildcard characters: False ``` ### -Export -The Export parameter causes sensitive data to be removed from the output file specified. A value of $true causes data removal. The default value is $false. +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 @@ -300,7 +317,9 @@ Accept wildcard characters: False ``` ### -OutData -The OutData switch specifies whether the output data is sent as a byte stream. For example, if you run $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" later in this topic. +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. ```yaml Type: SwitchParameter @@ -416,12 +435,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/Test-TextExtraction.md b/exchange/exchange-ps/exchange/Test-TextExtraction.md new file mode 100644 index 0000000000..43b3808f00 --- /dev/null +++ b/exchange/exchange-ps/exchange/Test-TextExtraction.md @@ -0,0 +1,140 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Test-TextExtraction + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Test-TextExtraction cmdlet to return the text from unencrypted email message files. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Test-TextExtraction [-FileData] <Byte[]> + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet doesn't work on encrypted email message files. + +The Microsoft classification engine uses the results to classify content and determine the sensitive information types in the message file. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$content = Test-TextExtraction -FileData ([System.IO.File]::ReadAllBytes('.\financial data.msg')) + +$content.ExtractedResults +``` + +This example extracts the text from the email message file named "financial data.msg" that's in the same folder where you run the command, and shows the results. + +### Example 2 +```powershell +$content = Test-TextExtraction -FileData ([System.IO.File]::ReadAllBytes('.\financial data.msg')) + +Test-DataClassification -TestTextExtractionResults $content.ExtractedResults +``` + +This example extracts the text from the email message file named "financial data.msg", stores the information in the variable named $content, and uses the variable with the Test-DataClassification cmdlet to return the sensitive information types, their confidence, and count. + +## PARAMETERS + +### -FileData +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/unified-messaging/Test-UMConnectivity.md b/exchange/exchange-ps/exchange/Test-UMConnectivity.md similarity index 86% rename from exchange/exchange-ps/exchange/unified-messaging/Test-UMConnectivity.md rename to exchange/exchange-ps/exchange/Test-UMConnectivity.md index 351d47215e..7a6b3e9a41 100644 --- a/exchange/exchange-ps/exchange/unified-messaging/Test-UMConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-UMConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/test-umconnectivity -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-UMConnectivity @@ -17,9 +16,9 @@ This cmdlet is available only in on-premises Exchange. Use the Test-UMConnectivity cmdlet to test the operation of Unified Messaging (UM) servers. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -35,12 +34,19 @@ Test-UMConnectivity -Phone <String> -PIN <String> -TUILogon <Boolean> -UMDialPla [-RemotePort <Int32>] [-Secured <Boolean>] [-Timeout <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### EndToEnd ``` -Test-UMConnectivity -Phone <String> -UMIPGateway <UMIPGatewayIdParameter> [-DiagDtmfDurationInMilisecs <Int32>] [-DiagDtmfSequence <String>] [-DiagInitialSilenceInMilisecs <Int32>] [-DiagInterDtmfDiffGapInMilisecs <String>] [-DiagInterDtmfGapInMilisecs <Int32>] [-From <String>] +Test-UMConnectivity -Phone <String> -UMIPGateway <UMIPGatewayIdParameter> + [-DiagDtmfDurationInMilisecs <Int32>] + [-DiagDtmfSequence <String>] + [-DiagInitialSilenceInMilisecs <Int32>] + [-DiagInterDtmfDiffGapInMilisecs <String>] + [-DiagInterDtmfGapInMilisecs <Int32>] + [-From <String>] [-CertificateThumbprint <String>] [-Confirm] [-DomainController <Fqdn>] @@ -49,15 +55,18 @@ Test-UMConnectivity -Phone <String> -UMIPGateway <UMIPGatewayIdParameter> [-Diag [-MonitoringContext <Boolean>] [-Secured <Boolean>] [-Timeout <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### PinReset ``` -Test-UMConnectivity -ResetPIN <Boolean> [-Confirm] +Test-UMConnectivity -ResetPIN <Boolean> + [-Confirm] [-DomainController <Fqdn>] [-MonitoringContext <Boolean>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### TuiLogonGeneral @@ -72,7 +81,8 @@ Test-UMConnectivity -TUILogonAll <Boolean> [-RemotePort <Int32>] [-Secured <Boolean>] [-Timeout <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### LocalLoop @@ -87,7 +97,8 @@ Test-UMConnectivity [-CallRouter] [-RemotePort <Int32>] [-Secured <Boolean>] [-Timeout <Int32>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -99,7 +110,7 @@ When you run this cmdlet in an on-premises Unified Messaging deployment, you nee After this task is complete, the cmdlet will have tested the operation of the Mailbox server and related telephony components. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -133,7 +144,7 @@ The Phone parameter specifies the telephone number or Session Initiation Protoco Type: String Parameter Sets: TuiLogonSpecific, EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -149,7 +160,7 @@ The PIN parameter specifies the PIN associated with the UM-enabled mailbox. Type: String Parameter Sets: TuiLogonSpecific Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -165,7 +176,7 @@ The ResetPIN parameter specifies whether to generate or regenerate a new PIN for Type: Boolean Parameter Sets: PinReset Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -181,7 +192,7 @@ The TUILogon parameter specifies whether the cmdlet tries to log on to one or mo Type: Boolean Parameter Sets: TuiLogonSpecific Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -197,7 +208,7 @@ The TUILogonAll parameter specifies whether to try to connect to all test mailbo Type: Boolean Parameter Sets: TuiLogonGeneral Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -213,7 +224,7 @@ The UMDialPlan parameter specifies the UM dial plan to be tested. This parameter Type: UMDialPlanIdParameter Parameter Sets: TuiLogonSpecific Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -229,7 +240,7 @@ The UMIPGateway parameter specifies the name of the UM IP gateway or IP PBX to u Type: UMIPGatewayIdParameter Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -245,7 +256,7 @@ The CallRouter switch specifies whether to test the Microsoft Exchange Unified M Type: SwitchParameter Parameter Sets: LocalLoop Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -261,7 +272,7 @@ The CertificateThumbprint parameter specifies the certificate thumbprint used fo Type: String Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -273,15 +284,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -297,7 +307,7 @@ The DiagDtmfDurationInMilisecs parameter specifies the duration of each digit se Type: Int32 Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -313,7 +323,7 @@ The DiagDtmfSequence parameter specifies the sequence of digits sent. Type: String Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -329,7 +339,7 @@ The DiagInitialSilenceInMilisecs parameter specifies the time period in millisec Type: Int32 Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -345,7 +355,7 @@ The DiagInterDtmfDiffGapInMilisecs parameter specifies whether to customize the Type: String Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -361,7 +371,7 @@ The DiagInterDtmfGapInMilisecs parameter specifies the time in milliseconds betw Type: Int32 Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -377,7 +387,7 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -393,7 +403,7 @@ The From parameter specifies the SIP URI or SIP address that the call originated Type: String Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -409,7 +419,7 @@ The ListenPort parameter specifies the IP port number on which to listen. If not Type: Int32 Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -425,7 +435,7 @@ The MediaSecured parameter specifies whether to use Secure RTP or RTP (unsecured Type: Boolean Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -435,13 +445,16 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values for this parameter are $true or $false. The default value is $false. If you specify the value $true, the 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). +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). +- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -457,7 +470,7 @@ The RemotePort parameter specifies the port used for the call. If not specified, Type: Int32 Parameter Sets: TuiLogonSpecific, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -473,7 +486,7 @@ The Secured parameter specifies whether the test is run in SIP Secured mode. Type: Boolean Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -489,7 +502,7 @@ The Timeout parameter specifies the length of time in seconds to wait for the te Type: Int32 Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -505,7 +518,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -519,12 +532,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/client-access/Test-WebServicesConnectivity.md b/exchange/exchange-ps/exchange/Test-WebServicesConnectivity.md similarity index 83% rename from exchange/exchange-ps/exchange/client-access/Test-WebServicesConnectivity.md rename to exchange/exchange-ps/exchange/Test-WebServicesConnectivity.md index c3eabf212a..fba4a45320 100644 --- a/exchange/exchange-ps/exchange/client-access/Test-WebServicesConnectivity.md +++ b/exchange/exchange-ps/exchange/Test-WebServicesConnectivity.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-webservicesconnectivity +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Test-WebServicesConnectivity @@ -17,15 +16,16 @@ This cmdlet is available only in on-premises Exchange. Use the Test-WebServicesConnectivity cmdlet to test client connectivity to Exchange Web Services virtual directories. -**Note**: This cmdlet works best in Exchange 2010. In Exchange 2013 or later, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX -### ClientAccessServer2010 +### Default ``` -Test-WebServicesConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-AllowUnsecureAccess] +Test-WebServicesConnectivity [[-ClientAccessServer] <ServerIdParameter>] + [-AllowUnsecureAccess] [-Confirm] [-DomainController <Fqdn>] [-LightMode] @@ -35,18 +35,19 @@ Test-WebServicesConnectivity [[-ClientAccessServer] <ServerIdParameter>] [-Allow [-Timeout <UInt32>] [-TrustAnySSLCertificate] [-UseAutodiscoverForClientAccessServer] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### AutoDiscoverServer ``` -Test-WebServicesConnectivity -AutoDiscoverServer <ClientAccessServerIdParameter> +Test-WebServicesConnectivity [[-Identity] <MailboxIdParameter>] -AutoDiscoverServer <ClientAccessServerIdParameter> [-Confirm] - [[-Identity] <MailboxIdParameter>] [-LightMode] [-MailboxCredential <PSCredential>] [-TrustAnySSLCertificate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### MonitoringContext @@ -56,7 +57,8 @@ Test-WebServicesConnectivity [[-Identity] <MailboxIdParameter>] [-MonitoringCont [-LightMode] [-MailboxCredential <PSCredential>] [-TrustAnySSLCertificate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### ClientAccessServer @@ -66,7 +68,8 @@ Test-WebServicesConnectivity [[-Identity] <MailboxIdParameter>] [-ClientAccessSe [-LightMode] [-MailboxCredential <PSCredential>] [-TrustAnySSLCertificate] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -79,20 +82,14 @@ The first time you use this cmdlet, you might be required to create a test user. The test results are displayed on-screen. The cmdlet returns the following information. - Source: Source server. - - ServiceEndpoint: Destination server. - - Scenario: The operations that are tested. Values are Autodiscover: SOAP Provider and EWS: GetFolder (full mode) or EWS: ConvertID (light mode). - - Result: The values returned are typically Success or \*FAILURE\*. - - Latency(MS): The time required to complete the test in milliseconds -You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example: +You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-WebServicesConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\EWS Test.html"`. -Test-WebServicesConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\\My Documents\\EWS Test.html" - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -111,31 +108,32 @@ This example tests the client connection to Exchange Web Services on the server ## PARAMETERS -### -AutoDiscoverServer -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: - -- Name (for example, Exchange01) - -- Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com) - -- Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01) +### -Identity +The Identity parameter specifies the mailbox to use for the test. You can use any value that uniquely identifies the mailbox. For example: -- GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942) +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) -You can't use this parameter with the ClientAccessServer parameter. +When you use this parameter, you also need to use the MailboxCredential parameter. ```yaml -Type: ClientAccessServerIdParameter -Parameter Sets: AutoDiscoverServer +Type: MailboxIdParameter +Parameter Sets: AutoDiscoverServer, MonitoringContext, ClientAccessServer Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -Required: True -Position: Named +Required: False +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` @@ -145,20 +143,17 @@ The ClientAccessServer parameter specifies the Exchange server to test. This ser You can use any value that uniquely identifies the server. For example: - Name - - Distinguished name (DN) - - ExchangeLegacyDN - - GUID You can't use this parameter with the AutoDiscoverServer parameter. ```yaml Type: ServerIdParameter -Parameter Sets: ClientAccessServer2010 +Parameter Sets: Default, ClientAccessServer Aliases: -Applicable: Exchange Server 2010 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -167,61 +162,48 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -AutoDiscoverServer +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: + +- Name (for example, Exchange01) +- Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com) +- Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01) +- GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942) + +You can't use this parameter with the ClientAccessServer parameter. + ```yaml -Type: ServerIdParameter -Parameter Sets: ClientAccessServer +Type: ClientAccessServerIdParameter +Parameter Sets: AutoDiscoverServer Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -Required: False +Required: True Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the mailbox to use for the test. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -When you use this parameter, you also need to use the MailboxCredential parameter. - ```yaml -Type: MailboxIdParameter -Parameter Sets: AutoDiscoverServer, MonitoringContext, ClientAccessServer +Type: ServerIdParameter +Parameter Sets: ClientAccessServer Aliases: Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False -Position: 1 +Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False ``` ### -AllowUnsecureAccess -This parameter is available or functional only in Exchange Server 2010. +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). +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. ```yaml Type: SwitchParameter @@ -239,8 +221,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -257,7 +238,7 @@ Accept wildcard characters: False ``` ### -DomainController -This parameter is available or functional only in 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. @@ -295,7 +276,7 @@ Accept wildcard characters: False ### -MailboxCredential 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://go.microsoft.com/fwlink/p/?linkId=142122). +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). This parameter is required when you use the Identity parameter. @@ -329,7 +310,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext -The MonitoringContext switch includes the associated monitoring events and performance counters in the 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). You don't need to specify a value with this switch. +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). ```yaml Type: SwitchParameter @@ -345,7 +328,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials -The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. 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. +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. ```yaml Type: SwitchParameter @@ -377,7 +362,7 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate -The TrustAnySSLCertificate switch specifies whether to ignore Secure Sockets Layer (SSL) certificate validation failures. You don't need to specify a value with this switch. +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. @@ -395,9 +380,9 @@ Accept wildcard characters: False ``` ### -UseAutodiscoverForClientAccessServer -This parameter is available or functional only in Exchange Server 2010. +This parameter is available only in Exchange Server 2010. -The UseAutodiscoverForClientAccessServer parameter specifies whether the test should use the Autodiscover service to locate the Client Access server. +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. ```yaml Type: SwitchParameter @@ -433,12 +418,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailboxes/Undo-SoftDeletedMailbox.md b/exchange/exchange-ps/exchange/Undo-SoftDeletedMailbox.md similarity index 79% rename from exchange/exchange-ps/exchange/mailboxes/Undo-SoftDeletedMailbox.md rename to exchange/exchange-ps/exchange/Undo-SoftDeletedMailbox.md index 8d999b60cc..50c11224ce 100644 --- a/exchange/exchange-ps/exchange/mailboxes/Undo-SoftDeletedMailbox.md +++ b/exchange/exchange-ps/exchange/Undo-SoftDeletedMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/undo-softdeletedmailbox +online version: https://learn.microsoft.com/powershell/module/exchange/undo-softdeletedmailbox applicable: Exchange Online title: Undo-SoftDeletedMailbox schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps" --- # Undo-SoftDeletedMailbox @@ -17,27 +16,31 @@ This cmdlet is available only in the cloud-based service. Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that has been deleted. Mailboxes can be recovered within 30 days of being deleted. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### PublicFolder ``` -Undo-SoftDeletedMailbox [-SoftDeletedObject] <MailboxIdParameter> [-DisplayName <String>] [-PublicFolder] +Undo-SoftDeletedMailbox [-SoftDeletedObject] <MailboxIdParameter> + [-DisplayName <String>] + [-PublicFolder] [-Confirm] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### SoftDeletedMailbox ``` -Undo-SoftDeletedMailbox [-SoftDeletedObject] <MailboxIdParameter> [-Password <SecureString>] [-WindowsLiveID <WindowsLiveId>] - [-Confirm] [-DisplayName <String>] +Undo-SoftDeletedMailbox [-SoftDeletedObject] <MailboxIdParameter> + [-Password <SecureString>] + [-WindowsLiveID <WindowsLiveId>] + [-Confirm] + [-DisplayName <String>] [-Name <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -45,7 +48,7 @@ Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that has been delete If the Microsoft account (formerly known as a Windows Live ID) wasn't deleted when the mailbox was deleted, you have to specify a new Microsoft account and password when you use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,56 +57,55 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Undo-SoftDeletedMailbox -SoftDeletedObject florencef ``` -This example recovers the deleted mailbox for the user Florence Flipo. When this mailbox was deleted, the associated Windows Live ID was also deleted. +This example recovers the deleted mailbox for the user Florence Flipo. When this mailbox was deleted, the associated Microsoft account was also deleted. ### Example 2 ```powershell -Undo-SoftDeletedMailbox bjohnson@contoso.edu -WindowsLiveID brianj@contoso.edu -Password (ConvertTo-SecureString -String 'Pa$$word1' -AsPlainText -Force) +Undo-SoftDeletedMailbox bjohnson@contoso.edu -WindowsLiveID brianj@contoso.edu -Password (Get-Credential).password ``` -This example recovers the deleted mailbox for the user Brian Johnson. When this mailbox was deleted, the associated Microsoft account (formerly known as a Windows Live ID) wasn't deleted. Note that a new Microsoft account and password have to be created to recover this mailbox. In the scenario, the old Microsoft account is retained as a proxy address for the mailbox. +This example recovers the deleted mailbox for the user Brian Johnson. When this mailbox was deleted, the associated Microsoft account wasn't deleted. Note that a new Microsoft account and password have to be created to recover this mailbox. In the scenario, the old Microsoft account is retained as a proxy address for the mailbox. ## PARAMETERS -### -PublicFolder -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. +### -SoftDeletedObject +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: SwitchParameter -Parameter Sets: PublicFolder +Type: MailboxIdParameter +Parameter Sets: (All) Aliases: Applicable: Exchange Online Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -SoftDeletedObject -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. +### -PublicFolder +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. ```yaml -Type: MailboxIdParameter -Parameter Sets: (All) +Type: SwitchParameter +Parameter Sets: PublicFolder Aliases: Applicable: Exchange Online Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -154,7 +156,11 @@ Accept wildcard characters: False ### -Password The Password parameter specifies a new password for the mailbox. -This parameter uses the syntax `(ConvertTo-SecureString -String '<password>' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. +You can use the following methods as a value for this parameter: + +- `(ConvertTo-SecureString -String '<password>' -AsPlainText -Force)`. +- Before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable (`$password`) for the value. +- `(Get-Credential).password` to be prompted to enter the password securely when you run this command. You have to include the Password parameter to recover a deleted mailbox with an existing Microsoft account (formerly known as a Windows Live ID) that wasn't deleted with the mailbox. @@ -188,7 +194,7 @@ Accept wildcard characters: False ``` ### -WindowsLiveID -The WindowsLiveID parameter specifies a new Microsoft account (formerly known as a Windows Live ID) and primary SMTP for the mailbox. The previous Microsoft account is retained as a proxy address for the mailbox. +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. @@ -210,12 +216,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Undo-SoftDeletedUnifiedGroup.md b/exchange/exchange-ps/exchange/Undo-SoftDeletedUnifiedGroup.md new file mode 100644 index 0000000000..7402d91bdb --- /dev/null +++ b/exchange/exchange-ps/exchange/Undo-SoftDeletedUnifiedGroup.md @@ -0,0 +1,123 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Undo-SoftDeletedUnifiedGroup + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Undo-SoftDeletedUnifiedGroup cmdlet to restore soft-deleted Microsoft 365 Groups in your cloud-based organization. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Undo-SoftDeletedUnifiedGroup [-SoftDeletedObject] <UnifiedGroupIdParameter> + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Microsoft 365 Groups are group objects that are available across Microsoft 365 services. + +Soft-deleted Microsoft 365 Groups are groups that have been deleted, but can be restored within 30 days of being deleted. All of the group contents can be restored within this period. After 30 days, soft-deleted Microsoft 365 Groups are marked for permanent deletion and can't be restored. + +To display all soft-deleted Microsoft 365 Groups in your organization, use the [Get-MgDirectoryDeletedItemAsGroup](https://learn.microsoft.com/powershell/module/microsoft.graph.identity.directorymanagement/get-mgdirectorydeleteditemasgroup) cmdlet in Microsoft Graph PowerShell. To permanently remove (purge) a soft-deleted Microsoft 365 Group, use the [Remove-MgDirectoryDeletedItem](https://learn.microsoft.com/powershell/module/microsoft.graph.identity.directorymanagement/remove-mgdirectorydeleteditem) cmdlet in Microsoft Graph PowerShell. + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Undo-SoftDeletedUnifiedGroup -SoftDeletedObject "Marketing Department" +``` + +This example restores the soft-deleted Microsoft 365 Group named Marketing Department. + +## PARAMETERS + +### -SoftDeletedObject +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 +- Alias +- Distinguished name (DN) +- Canonical DN +- Domain\\Username +- Email address +- GUID +- LegacyExchangeDN +- SamAccountName +- User ID or user principal name (UPN) + +**Note**: You might need to use the DistinguishedName or ExchangeGuid property to identify the soft-deleted Microsoft 365 Group, because it's possible for an active Microsoft 365 Group and a soft-deleted Microsoft 365 Group to have the same primary SMTP address. + +```yaml +Type: UnifiedGroupIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Uninstall-TransportAgent.md b/exchange/exchange-ps/exchange/Uninstall-TransportAgent.md similarity index 89% rename from exchange/exchange-ps/exchange/mail-flow/Uninstall-TransportAgent.md rename to exchange/exchange-ps/exchange/Uninstall-TransportAgent.md index 659936718b..5618a653c7 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Uninstall-TransportAgent.md +++ b/exchange/exchange-ps/exchange/Uninstall-TransportAgent.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/uninstall-transportagent +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Uninstall-TransportAgent @@ -17,25 +16,27 @@ This cmdlet is available only in on-premises Exchange. Use the Uninstall-TransportAgent cmdlet to unregister transport agents from Exchange servers. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Uninstall-TransportAgent [-Identity] <TransportAgentObjectId> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] - [-TransportService <TransportService>] [<CommonParameters>] +Uninstall-TransportAgent [-Identity] <TransportAgentObjectId> + [-Confirm] + [-DomainController <Fqdn>] + [-TransportService <TransportService>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION You can install and uninstall transport agents in the following locations: - The Transport service on Mailbox servers. - - The Front End Transport service on Mailbox servers. - - Edge Transport servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -67,8 +68,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -102,33 +102,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -TransportService 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. - - MailboxSubmission for the Mailbox Transport Submission service on Mailbox servers. - - MailboxDelivery for the Mailbox Transport Delivery service on Mailbox servers. - - FrontEnd for the Front End Transport service on Mailbox servers. - - Edge on Edge Transport servers. ```yaml @@ -144,17 +124,33 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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). ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-AddressList.md b/exchange/exchange-ps/exchange/Update-AddressList.md similarity index 87% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-AddressList.md rename to exchange/exchange-ps/exchange/Update-AddressList.md index d03c0fcfba..8c44e68434 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-AddressList.md +++ b/exchange/exchange-ps/exchange/Update-AddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/update-addresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-AddressList @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Update-AddressList cmdlet to update the recipients included in address lists. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-AddressList [-Identity] <AddressListIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] +Update-AddressList [-Identity] <AddressListIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,12 +46,9 @@ This example updates the recipients of the address list named building4 that's u 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 - - Distinguished name (DN) - - GUID - -- Path: (\\\<Name\>) or [\<Container\>\\\<Name\>) +- Path: `"\AddressListName"` or `"\ContainerName\AddressListName"` (for example, `"\All Users"` or `"\All Contacts\Marketing"`) ```yaml Type: AddressListIdParameter @@ -67,8 +66,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +119,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Update-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/Update-ComplianceCaseMember.md new file mode 100644 index 0000000000..dfbaff31dc --- /dev/null +++ b/exchange/exchange-ps/exchange/Update-ComplianceCaseMember.md @@ -0,0 +1,137 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Update-ComplianceCaseMember + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Update-ComplianceCaseMember cmdlet to replace all members of eDiscovery cases in the Microsoft Purview compliance portal. To add or remove existing members, use the Add-ComplianceCaseMember and Remove-ComplianceCaseMember cmdlets. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Update-ComplianceCaseMember [-Case] <String> -Members <String[]> + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You use eDiscovery cases to control who can create, access, and manage compliance searches in your organization. You use the New-ComplianceCase cmdlet to create eDiscovery cases. The eDiscovery Manager who created the case is automatically added as a member of the case. + +To add a member of an eDiscovery case, the user needs to be a member of the Reviewer or eDiscovery Manager role groups. When a member of the eDiscovery Manager role group is a member of an eDiscovery case, the user can: + +- Add and remove case members. +- Create and edit compliance searches associated with a case. +- Perform compliance actions (for example, export) on the results of a compliance search. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Update-ComplianceCaseMember -Case "Case 5150" -Members chris@contoso.com,michelle@contoso.com,laura@contoso.com,julia@contoso.com +``` + +This example replaces the existing members of the eDiscovery case named Case 5150 with new members. + +## PARAMETERS + +### -Case +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Members +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-DatabaseSchema.md b/exchange/exchange-ps/exchange/Update-DatabaseSchema.md similarity index 86% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-DatabaseSchema.md rename to exchange/exchange-ps/exchange/Update-DatabaseSchema.md index 7ebe819126..1ca485d6cb 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-DatabaseSchema.md +++ b/exchange/exchange-ps/exchange/Update-DatabaseSchema.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/update-databaseschema +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-DatabaseSchema @@ -15,19 +14,21 @@ monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Update-DatabaseSchema cmdlet to upgrade the database schema for one or more databases after an Exchange software update that includes database schema updates has been installed on Mailbox servers in a database availability group (DAG). Some software updates for Exchange may include database schema updates. After such an update has been installed on all members of a DAG, the administrator must run the Update-DatabaseSchema cmdlet for each database in the DAG to trigger the database schema update. The in-place database schema upgrade engine ensures that no schema updates occur until all members of the DAG have compatible versions of the software. +Use the Update-DatabaseSchema cmdlet to upgrade the database schema for one or more databases after an Exchange software update that includes database schema updates has been installed on Mailbox servers in a database availability group (DAG). Some software updates for Exchange may include database schema updates. After such an update has been installed on all members of a DAG, the administrator must run the Update-DatabaseSchema cmdlet for each database in the DAG and dismount/mount or failover the database to trigger the database schema update. The in-place database schema upgrade engine ensures that no schema updates occur until all members of the DAG have compatible versions of the software. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Update-DatabaseSchema [-Identity] <DatabaseIdParameter> -MajorVersion <UInt16> -MinorVersion <UInt16> - [-Confirm] [-WhatIf] [<CommonParameters>] + [-Confirm] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,9 +45,7 @@ This example updates the database schema for database DB1. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -97,8 +96,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -135,12 +133,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/users-and-groups/Update-DistributionGroupMember.md b/exchange/exchange-ps/exchange/Update-DistributionGroupMember.md similarity index 85% rename from exchange/exchange-ps/exchange/users-and-groups/Update-DistributionGroupMember.md rename to exchange/exchange-ps/exchange/Update-DistributionGroupMember.md index 7c839cb70b..cc94a00944 100644 --- a/exchange/exchange-ps/exchange/users-and-groups/Update-DistributionGroupMember.md +++ b/exchange/exchange-ps/exchange/Update-DistributionGroupMember.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/update-distributiongroupmember +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" --- # Update-DistributionGroupMember @@ -17,17 +16,22 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Update-DistributionGroupMember cmdlet to replace all members of distribution groups and mail-enabled security groups. To add or remove existing group members, use the Add-DistributionGroupMember and Remove-DistributionGroupMember cmdlets. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-DistributionGroupMember [-Identity] <DistributionGroupIdParameter> [-BypassSecurityGroupManagerCheck] - [-Confirm] [-DomainController <Fqdn>] [-Members <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] +Update-DistributionGroupMember [-Identity] <DistributionGroupIdParameter> + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-DomainController <Fqdn>] + [-Members <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,15 +48,10 @@ This example replaces the existing members of the distribution group name Resear 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -69,14 +68,13 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. 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: +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. -- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +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: +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. - Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. -You don't need to specify a value with this switch. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -93,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -132,21 +129,18 @@ Accept wildcard characters: False 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned. +The maximum number of entries for this parameter is 10000. + ```yaml Type: MultiValuedProperty Parameter Sets: (All) @@ -181,12 +175,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/Update-EmailAddressPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-EmailAddressPolicy.md rename to exchange/exchange-ps/exchange/Update-EmailAddressPolicy.md index 2309b81045..a5ab8316da 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-EmailAddressPolicy.md +++ b/exchange/exchange-ps/exchange/Update-EmailAddressPolicy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/update-emailaddresspolicy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-EmailAddressPolicy @@ -17,17 +16,22 @@ This cmdlet is available only in on-premises Exchange. Use the Update-EmailAddressPolicy cmdlet to apply new or updated email address policies to the affected recipients in an on-premises Exchange organization. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-EmailAddressPolicy [-Identity] <EmailAddressPolicyIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-FixMissingAlias] [-WhatIf] [-UpdateSecondaryAddressesOnly] [<CommonParameters>] +Update-EmailAddressPolicy [-Identity] <EmailAddressPolicyIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-FixMissingAlias] + [-UpdateSecondaryAddressesOnly] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,9 +48,7 @@ This example applies the email address policy named Northwest Executives to all 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 - - Distinguished name (DN) - - GUID ```yaml @@ -65,8 +67,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -116,14 +117,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -UpdateSecondaryAddressesOnly +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. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -132,14 +135,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -UpdateSecondaryAddressesOnly -The UpdateSecondaryAddressesOnly switch parameter specifies that only the proxy email addresses are updated for the recipients. The recipient's primary email address isn't updated. You don't need to specify a value with this switch. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. 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 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -153,12 +156,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/organization/Update-ExchangeHelp.md b/exchange/exchange-ps/exchange/Update-ExchangeHelp.md similarity index 77% rename from exchange/exchange-ps/exchange/organization/Update-ExchangeHelp.md rename to exchange/exchange-ps/exchange/Update-ExchangeHelp.md index bc59930217..01778dcf54 100644 --- a/exchange/exchange-ps/exchange/organization/Update-ExchangeHelp.md +++ b/exchange/exchange-ps/exchange/Update-ExchangeHelp.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/update-exchangehelp +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-ExchangeHelp @@ -17,20 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Update-ExchangeHelp cmdlet to find, download and install the latest available help topics for the Exchange Management Shell on the local computer. If an available version is found based your installed version and languages of Exchange, the cmdlet downloads and integrates the updated version of Help in the Exchange Management Shell. This cmdlet is a required substitute for the Update-Help cmdlet that's available in Windows PowerShell. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-ExchangeHelp [-Force] [<CommonParameters>] +Update-ExchangeHelp [-Force] + [<CommonParameters>] ``` ## DESCRIPTION The Update-ExchangeHelp cmdlet is available in Exchange Server 2013 or later. -You need to run the Update-ExchangeHelp cmdlet on each Exchange server. By default, the cmdlet requires an Internet connection, but you can configure an offline mode. For more information, see [Use Update-ExchangeHelp to update Exchange PowerShell help topics on Exchange servers](https://docs.microsoft.com/powershell/exchange/exchange-server/use-update-exchangehelp). +You need to run the Update-ExchangeHelp cmdlet on each Exchange server. By default, the cmdlet requires an Internet connection, but you can configure an offline mode. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,7 +44,7 @@ This example checks for the latest available version of Help for the Exchange Ma ## PARAMETERS ### -Force -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. +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. @@ -66,12 +66,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-FileDistributionService.md b/exchange/exchange-ps/exchange/Update-FileDistributionService.md similarity index 92% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-FileDistributionService.md rename to exchange/exchange-ps/exchange/Update-FileDistributionService.md index c866ac9827..869bf696a3 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-FileDistributionService.md +++ b/exchange/exchange-ps/exchange/Update-FileDistributionService.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/update-filedistributionservice +online version: https://learn.microsoft.com/powershell/module/exchange/update-filedistributionservice applicable: Exchange Server 2010 title: Update-FileDistributionService schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Update-FileDistributionService @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Update-FileDistributionService cmdlet to access the Microsoft Exchange File Distribution service to poll for offline address book (OAB), Group Metrics, and Unified Messaging (UM) configuration and data. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -26,7 +25,8 @@ Update-FileDistributionService [-Identity] <ServerIdParameter> [-Confirm] [-DomainController <Fqdn>] [-Type <String>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -34,7 +34,7 @@ The Update-FileDistributionService cmdlet forces the Microsoft Exchange File Dis If you don't use the Type parameter when running this command, OAB, Unified Messaging, and Group Metrics data are reloaded. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -65,11 +65,8 @@ This example polls Server1 for changes to Group Metrics files associated with Se 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -88,8 +85,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -127,9 +123,7 @@ The Type parameter specifies whether to reload OAB, Unified Messaging, or Group The Type parameter takes the following values: - OAB Using the OAB value forces the Exchange File Distribution service to reload its configuration and poll for new data associated with OABs. - - UM Using the UM value forces the Exchange File Distribution service to reload its configuration and poll for new data associated with Unified Messaging. - - GM Using the GM value forces the Exchange File Distribution service to reload its configuration and poll for new data associated with Group Metrics. ```yaml @@ -166,12 +160,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-GlobalAddressList.md b/exchange/exchange-ps/exchange/Update-GlobalAddressList.md similarity index 88% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-GlobalAddressList.md rename to exchange/exchange-ps/exchange/Update-GlobalAddressList.md index 927805a8fa..8fe39ea94d 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-GlobalAddressList.md +++ b/exchange/exchange-ps/exchange/Update-GlobalAddressList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/update-globaladdresslist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-GlobalAddressList @@ -17,17 +16,20 @@ This cmdlet is available only in on-premises Exchange. Use the Update-GlobalAddressList cmdlet to update the recipients included in a global address list (GAL). -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-GlobalAddressList [-Identity] <GlobalAddressListIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] +Update-GlobalAddressList [-Identity] <GlobalAddressListIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,9 +46,7 @@ This example updates the recipients in the default GAL. 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 - - Distinguished name (DN) - - GUID ```yaml @@ -65,8 +65,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -119,12 +118,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Update-HybridConfiguration.md b/exchange/exchange-ps/exchange/Update-HybridConfiguration.md new file mode 100644 index 0000000000..bb0e1ea9e9 --- /dev/null +++ b/exchange/exchange-ps/exchange/Update-HybridConfiguration.md @@ -0,0 +1,198 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Update-HybridConfiguration + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Update-HybridConfiguration cmdlet to define the credentials that are used to update the hybrid configuration object. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Update-HybridConfiguration -OnPremisesCredentials <PSCredential> -TenantCredentials <PSCredential> + [-Confirm] + [-DomainController <Fqdn>] + [-ForceUpgrade] + [-SuppressOAuthWarning] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +$OnPremisesCreds = Get-Credential + +$TenantCreds = Get-Credential + +Update-HybridConfiguration -OnPremisesCredentials $OnPremisesCreds -TenantCredentials $TenantCreds +``` + +This example defines the credentials that are used to update the hybrid configuration object and connect to the Microsoft 365 for enterprises organization. + +Use the first command to specify your on-premises organization credentials. For example, run this command and enter `<domain>\admin@contoso.com` and the associated password in the resulting Windows PowerShell Credential Request dialog box. + +Use the second command to specify your Microsoft 365 organization credentials. For example, run this command and then enter `admin@contoso.onmicrosoft.com` and the associated account password in the resulting Windows PowerShell Credential Request dialog box. + +Use the last command to define the credentials that are used to update the hybrid configuration object and connect to the Microsoft 365 organization. + +## PARAMETERS + +### -OnPremisesCredentials +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantCredentials +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] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +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: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is available only in on-premises Exchange. + +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceUpgrade +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SuppressOAuthWarning +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/database-availability-groups/Update-MailboxDatabaseCopy.md b/exchange/exchange-ps/exchange/Update-MailboxDatabaseCopy.md similarity index 91% rename from exchange/exchange-ps/exchange/database-availability-groups/Update-MailboxDatabaseCopy.md rename to exchange/exchange-ps/exchange/Update-MailboxDatabaseCopy.md index 24cf9e1dff..b7f5614479 100644 --- a/exchange/exchange-ps/exchange/database-availability-groups/Update-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/exchange/Update-MailboxDatabaseCopy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/database-availability-groups/update-mailboxdatabasecopy +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-MailboxDatabaseCopy @@ -17,21 +16,28 @@ This cmdlet is available only in on-premises Exchange. Use the Update-MailboxDatabaseCopy cmdlet to seed or reseed a mailbox database copy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ### CancelSeed ``` -Update-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> [-CancelSeed] +Update-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> + [-CancelSeed] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### Identity ``` -Update-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> [-BeginSeed] [-Force] [-Network <DatabaseAvailabilityGroupNetworkIdParameter>] [-SecondaryDatabasePartitionOnly] [-SourceServer <ServerIdParameter>] +Update-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> + [-BeginSeed] + [-Force] + [-Network <DatabaseAvailabilityGroupNetworkIdParameter>] + [-SecondaryDatabasePartitionOnly] + [-SourceServer <ServerIdParameter>] [-CatalogOnly] [-Confirm] [-DatabaseOnly] @@ -43,12 +49,14 @@ Update-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter> [-BeginSeed] [- [-NoThrottle] [-PrimaryDatabasePartitionOnly] [-SafeDeleteExistingFiles] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### ExplicitServer ``` -Update-MailboxDatabaseCopy -Server <MailboxServerIdParameter> [-MaximumSeedsInParallel <Int32>] +Update-MailboxDatabaseCopy -Server <MailboxServerIdParameter> + [-MaximumSeedsInParallel <Int32>] [-CatalogOnly] [-Confirm] [-DatabaseOnly] @@ -60,7 +68,8 @@ Update-MailboxDatabaseCopy -Server <MailboxServerIdParameter> [-MaximumSeedsInPa [-NoThrottle] [-PrimaryDatabasePartitionOnly] [-SafeDeleteExistingFiles] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -68,9 +77,9 @@ Seeding is the process in which a copy of a mailbox database is added to another The Update-MailboxDatabaseCopy cmdlet can also be used to seed a content index catalog for a mailbox database copy. When you do this, the MAPI network is used, regardless of the value you specify with the Network parameter. -You must suspend a database copy before you can update it using the Update-MailboxDatabaseCopy cmdlet. For detailed steps about how to suspend a database copy, see [Suspend or resume a mailbox database copy](https://docs.microsoft.com/Exchange/high-availability/manage-ha/suspend-resume-db-copies). +You must suspend a database copy before you can update it using the Update-MailboxDatabaseCopy cmdlet. For detailed steps about how to suspend a database copy, see [Suspend or resume a mailbox database copy](https://learn.microsoft.com/Exchange/high-availability/manage-ha/suspend-resume-db-copies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -111,35 +120,35 @@ This example performs a full server reseed of all of the databases on the Mailbo ## PARAMETERS -### -CancelSeed -The CancelSeed switch specifies whether to cancel an in-progress seeding operation. You don't need to specify a value with this switch. +### -Identity +The Identity parameter specifies the name or GUID of the mailbox database whose copy is being seeded. ```yaml -Type: SwitchParameter -Parameter Sets: CancelSeed +Type: DatabaseCopyIdParameter +Parameter Sets: CancelSeed, Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: Named +Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Identity -The Identity parameter specifies the name or GUID of the mailbox database whose copy is being seeded. +### -CancelSeed +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: DatabaseCopyIdParameter -Parameter Sets: CancelSeed, Identity +Type: SwitchParameter +Parameter Sets: CancelSeed Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True -Position: 1 +Position: Named Default value: None -Accept pipeline input: True +Accept pipeline input: False Accept wildcard characters: False ``` @@ -196,8 +205,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -264,7 +272,9 @@ Accept wildcard characters: False ``` ### -Force -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. +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. ```yaml Type: SwitchParameter @@ -384,7 +394,7 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2019 Required: False Position: Named @@ -418,7 +428,7 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2019 Required: False Position: Named @@ -433,11 +443,8 @@ The SourceServer parameter specifies the Mailbox server with a passive copy of t You can use any value that uniquely identifies the server. For example: - Name - - FQDN - - Distinguished name (DN) - - ExchangeLegacyDN ```yaml @@ -474,12 +481,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-OfflineAddressBook.md b/exchange/exchange-ps/exchange/Update-OfflineAddressBook.md similarity index 85% rename from exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-OfflineAddressBook.md rename to exchange/exchange-ps/exchange/Update-OfflineAddressBook.md index 31140d049c..c9dd29eb20 100644 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Update-OfflineAddressBook.md +++ b/exchange/exchange-ps/exchange/Update-OfflineAddressBook.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/update-offlineaddressbook +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-OfflineAddressBook @@ -17,17 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Update-OfflineAddressBook cmdlet to update the offline address books (OABs) used by Microsoft Outlook clients. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-OfflineAddressBook [-Identity] <OfflineAddressBookIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [-Force] [<CommonParameters>] +Update-OfflineAddressBook [-Identity] <OfflineAddressBookIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-Force] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -61,8 +64,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -94,14 +96,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +### -Force +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. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Aliases: +Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -110,14 +114,14 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Force -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. +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. 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 +Aliases: wi +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -131,12 +135,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolder.md b/exchange/exchange-ps/exchange/Update-PublicFolder.md similarity index 92% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolder.md rename to exchange/exchange-ps/exchange/Update-PublicFolder.md index 478e1288fd..52de562a91 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolder.md +++ b/exchange/exchange-ps/exchange/Update-PublicFolder.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/update-publicfolder +online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfolder applicable: Exchange Server 2010 title: Update-PublicFolder schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Update-PublicFolder @@ -17,7 +16,7 @@ This cmdlet is available only in Exchange Server 2010. Use the Update-PublicFolder cmdlet to start content synchronization of a public folder. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -25,11 +24,12 @@ For information about the parameter sets in the Syntax section below, see [Excha Update-PublicFolder [-Identity] <PublicFolderIdParameter> -Server <ServerIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -71,11 +71,8 @@ Accept wildcard characters: False 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -94,8 +91,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -148,12 +144,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolderHierarchy.md b/exchange/exchange-ps/exchange/Update-PublicFolderHierarchy.md similarity index 88% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolderHierarchy.md rename to exchange/exchange-ps/exchange/Update-PublicFolderHierarchy.md index a66648547d..c8bcc1dc98 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolderHierarchy.md +++ b/exchange/exchange-ps/exchange/Update-PublicFolderHierarchy.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/update-publicfolderhierarchy +online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfolderhierarchy applicable: Exchange Server 2010 title: Update-PublicFolderHierarchy schema: 2.0.0 author: chrisda ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010" --- # Update-PublicFolderHierarchy @@ -17,17 +16,20 @@ This cmdlet is available only in Exchange Server 2010. Use the Update-PublicFolderHierarchy cmdlet to start content synchronization of the public folder hierarchy. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-PublicFolderHierarchy -Server <ServerIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] +Update-PublicFolderHierarchy -Server <ServerIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -44,11 +46,8 @@ This example pipes the output of the Get-MailboxServer command to the Update-Pub 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 - - FQDN - - Distinguished name (DN) - - Exchange Legacy DN ```yaml @@ -67,8 +66,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -121,12 +119,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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=2081749). If the Output Type field is blank, the cmdlet doesn't return data. ## NOTES diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolderMailbox.md b/exchange/exchange-ps/exchange/Update-PublicFolderMailbox.md similarity index 81% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolderMailbox.md rename to exchange/exchange-ps/exchange/Update-PublicFolderMailbox.md index 513480e495..cfef60bbfd 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-PublicFolderMailbox.md +++ b/exchange/exchange-ps/exchange/Update-PublicFolderMailbox.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/update-publicfoldermailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Update-PublicFolderMailbox @@ -17,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Update-PublicFolderMailbox cmdlet to update the hierarchy for public folders. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -31,7 +30,8 @@ Update-PublicFolderMailbox [-Identity] <MailboxIdParameter> [-InvokeSynchronizer] [-ReconcileFolders] [-SuppressStatus] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ### InvokeSingleFolderSynchronizer @@ -40,13 +40,14 @@ Update-PublicFolderMailbox [-Identity] <MailboxIdParameter> -FolderId <PublicFol [-CreateAssociatedDumpster] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION -This cmdlet only needs to be used if you want to manually invoke the hierarchy synchronizer and the mailbox assistant. Both these are invoked at least once every 24 hours for each public folder mailbox in the organization. The hierarchy synchronizer is invoked every 15 minutes if any users are logged on to a secondary mailbox through Outlook or a Exchange Web Services client. +This cmdlet only needs to be used if you want to manually invoke the hierarchy synchronizer and the mailbox assistant. Both these are invoked at least once every 24 hours for each public folder mailbox in the organization. The hierarchy synchronizer is invoked every 15 minutes if any users are logged on to a secondary mailbox through Outlook or an Exchange Web Services client. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,23 +71,14 @@ This example updates all public folder mailboxes. 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -119,7 +111,7 @@ Accept wildcard characters: False ``` ### -InvokeSynchronizer -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. +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. @@ -152,8 +144,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -220,7 +211,7 @@ Accept wildcard characters: False ``` ### -FullSync -The FullSync switch specifies that you want to perform a full synchronization of the public folder mailbox. +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 @@ -236,9 +227,23 @@ Accept wildcard characters: False ``` ### -ReconcileFolders -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. Folders that exist in the secondary public folder mailbox and not in the primary will be deleted. +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. + +In Exchange Online, folders that exist in the secondary public folder mailbox and not in the primary will be moved to \NON_IPM_SUBTREE\LOST_AND_FOUND. See [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/introducing-public-folder-8220-lost-and-found-8221-functionality/ba-p/604043) for more details about LOST_AND_FOUND functionality. + +In both the scenarios, public folders that were deleted or moved to LOST_AND_FOUND can be restored using Set-PublicFolder command. + +This example restores the public folder named "Marketing" from LOST_AND_FOUND to the folder named \South + +`Get-PublicFolder \NON_IPM_SUBTREE\LOST_AND_FOUND\5773ba6a-9926-4d64-97db-63a2bdd94a5b\"Pesky Pole" | Set-PublicFolder -Path "\South"` + +This example restores the public folder named "Documents" from LOST_AND_FOUND to the folder named \Engineering + +`Set-PublicFolder -Identity \NON_IPM_SUBTREE\DUMPSTER_ROOT\DUMPSTER_EXTEND\RESERVED_1\RESERVED_1\9f32c468-4bc2-42aa-b979-16a057394b2f\Documents -Path \Engineering` -This switch should only be used for repair or troubleshooting purposes to look for differences in the public folder hierarchy that aren't detected by a regular synchronization. These undetected differences may occur in database failover or disaster recovery scenarios. You must use this switch with the InvokeSynchronizer switch. +**Note**: You should use the ReconcileFolders switch only for repair or troubleshooting purposes to look for differences in the public folder hierarchy that aren't detected by a regular synchronization. These undetected differences may occur in database failover or disaster recovery scenarios. You must use this switch with the InvokeSynchronizer switch. ```yaml Type: SwitchParameter @@ -294,12 +299,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/Update-Recipient.md b/exchange/exchange-ps/exchange/Update-Recipient.md new file mode 100644 index 0000000000..c4b96b4b18 --- /dev/null +++ b/exchange/exchange-ps/exchange/Update-Recipient.md @@ -0,0 +1,168 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Update-Recipient + +## SYNOPSIS +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. + +Use the Update-Recipient cmdlet to add Exchange attributes to recipient objects. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Update-Recipient [-Identity] <RecipientIdParameter> + [-Confirm] + [-Credential <PSCredential>] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +In on-premises Exchange, before you can run the Update-Recipient cmdlet to convert an Active Directory user object into an Exchange mailbox, you must stamp the user object with the following three mandatory Exchange attributes: + +- homeMDB +- mailNickname +- msExchHomeServerName + +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Update-Recipient -Identity "John Smith" +``` + +This example adds Exchange attributes to the mail contact that represents John Smith's mailbox. + +### Example 2 +```powershell +Get-MailContact -OrganizationalUnit "contoso.com/fabrikam.com Users" | Update-Recipient +``` + +In on-premises Exchange, this example updates all contacts in a specific organizational unit (OU). This example assumes that recipients are synchronized between two forests, contoso.com and fabrikam.com, and all the synchronized recipients from the fabrikam.com domain are stored in a specific OU called fabrikam.com Users in the contoso.com domain. + +## PARAMETERS + +### -Identity +The Identity parameter specifies the recipient that you want to update. You can use any value that uniquely identifies the recipient. For example: + +- Name +- Alias +- Distinguished name (DN) +- Canonical DN +- Email address +- GUID + +```yaml +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 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Credential +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). + +```yaml +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### 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/role-based-access-control/Update-RoleGroupMember.md b/exchange/exchange-ps/exchange/Update-RoleGroupMember.md similarity index 77% rename from exchange/exchange-ps/exchange/role-based-access-control/Update-RoleGroupMember.md rename to exchange/exchange-ps/exchange/Update-RoleGroupMember.md index c4a7404363..8c47b09f10 100644 --- a/exchange/exchange-ps/exchange/role-based-access-control/Update-RoleGroupMember.md +++ b/exchange/exchange-ps/exchange/Update-RoleGroupMember.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/update-rolegroupmember -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" --- # Update-RoleGroupMember @@ -17,13 +16,18 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Update-RoleGroupMember cmdlet to modify the members of a management role group. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-RoleGroupMember [-Identity] <RoleGroupIdParameter> [-BypassSecurityGroupManagerCheck] [-Confirm] - [-DomainController <Fqdn>] [-Members <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] +Update-RoleGroupMember [-Identity] <RoleGroupIdParameter> + [-BypassSecurityGroupManagerCheck] + [-Confirm] + [-DomainController <Fqdn>] + [-Members <MultiValuedProperty>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -35,9 +39,9 @@ If the ManagedBy property has been populated with role group managers, the user If the role group is a linked role group, you can't use the Update-RoleGroupMember cmdlet to modify members on the role group. Instead, you need to modify members on the foreign universal security group (USG) that's linked to the linked role group. To find the foreign USG that's linked to a role group, use the Get-RoleGroup cmdlet. -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). +For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -57,14 +61,16 @@ This example sets the Recipient Administrators role group membership list to Mar ### Example 3 ```powershell -Update-RoleGroupMember "Organization Management" -Members @{Add=(Get-Mailbox David).Identity, (Get-Group "Help Desk Managers").Identity; Remove=(Get-Mailbox "Christine").Identity, (Get-Mailbox "Isabel").Identity} +Update-RoleGroupMember "Organization Management" -Members @{Add=(Get-Mailbox David).Identity, (Get-Group "Help Desk Managers").Identity + +Remove=(Get-Mailbox "Christine").Identity, (Get-Mailbox "Isabel").Identity} ``` -This example adds multiple members to, and removes multiple members from, a role group without replacing all the existing members on the role group. This example makes use of multivalued property syntax that's described in the topic [Modifying multivalued properties](https://docs.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). When you use this multivalued property syntax, you must manually retrieve the Identity of the mailbox or mail-enabled security group that you want to add to or remove from the role group. Use the syntax that matches the type of object you want to add or remove: +This example adds multiple members to, and removes multiple members from, a role group without replacing all the existing members on the role group. This example makes use of multivalued property syntax that's described in the topic [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). When you use this multivalued property syntax, you must manually retrieve the Identity of the mailbox or mail-enabled security group that you want to add to or remove from the role group. Use the syntax that matches the type of object you want to add or remove: -Mailbox: If you want to add or remove a mailbox, use the syntax (Get-Mailbox "\<Alias or Name\>").Identity +Mailbox: If you want to add or remove a mailbox, use the syntax `(Get-Mailbox "<Alias or Name>").Identity`. -Mail-enabled security group: If you want to add or remove a mail-enabled security group, use the syntax (Get-Group "\<Name\>").Identity +Mail-enabled security group: If you want to add or remove a mail-enabled security group, use the syntax `(Get-Group "<Name>").Identity`. ## PARAMETERS @@ -75,7 +81,7 @@ The Identity parameter specifies the role group whose membership you want to mod Type: RoleGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: 1 @@ -85,19 +91,18 @@ Accept wildcard characters: False ``` ### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. 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: +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. -- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. +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: +- Distribution groups or mail-enabled security groups: You need to be a member of the Organization Management role group or have the Security Group Creation and Membership role assigned. - Role groups: You need to be a member of the Organization Management role group or have the Role Management role assigned. -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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -109,15 +114,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -153,7 +157,7 @@ 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, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -163,7 +167,7 @@ Accept wildcard characters: False ``` ### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. +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. @@ -171,7 +175,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -185,12 +189,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Update-SafeList.md b/exchange/exchange-ps/exchange/Update-SafeList.md similarity index 88% rename from exchange/exchange-ps/exchange/antispam-antimalware/Update-SafeList.md rename to exchange/exchange-ps/exchange/Update-SafeList.md index 4dfbfe582e..9b052ebd8b 100644 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Update-SafeList.md +++ b/exchange/exchange-ps/exchange/Update-SafeList.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/update-safelist +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-SafeList @@ -17,13 +16,18 @@ This cmdlet is available only in on-premises Exchange. Use the Update-SafeList cmdlet to update the safelist aggregation data in Active Directory. Safelist aggregation data is used in the built-in anti-spam filtering in Microsoft Exchange. EdgeSync replicates safelist aggregation data to Edge Transport servers in the perimeter network. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-SafeList [-Identity] <MailboxIdParameter> [-Confirm] [-DomainController <Fqdn>] [-EnsureJunkEmailRule] - [-IncludeDomains] [-Type <UpdateType>] [-WhatIf] +Update-SafeList [-Identity] <MailboxIdParameter> + [-Confirm] + [-DomainController <Fqdn>] + [-EnsureJunkEmailRule] + [-IncludeDomains] + [-Type <UpdateType>] + [-WhatIf] [<CommonParameters>] ``` @@ -32,7 +36,7 @@ The Update-SafeList cmdlet reads the safelist aggregation data stored on a Micro Be mindful of the network and replication traffic that may be generated when you run the Update-SafeList cmdlet. Running the command on multiple mailboxes where safelists are heavily used may generate a significant amount of traffic. We recommend that if you run the command on multiple mailboxes, you should run the command during off-peak, non-business hours. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,7 +49,9 @@ This example updates Safe Senders List data for the single user kim@contoso.com. ### Example 2 ```powershell -Set-AdServerSettings -ViewEntireForest $true; Get-Mailbox -ResultSize Unlimited -RecipientTypeDetails UserMailbox | Update-Safelist +Set-AdServerSettings -ViewEntireForest $true + +Get-Mailbox -ResultSize Unlimited -RecipientTypeDetails UserMailbox | Update-Safelist ``` This example updates safelist data for all user mailboxes in your Exchange organization. By default, the Exchange Management Shell is configured to retrieve or modify objects that reside in the domain in which the Exchange server resides. Therefore, to retrieve all the mailboxes in your Exchange organization, you must first set the scope of the Exchange Management Shell to the entire forest using the Set-AdServerSettings cmdlet. @@ -56,23 +62,14 @@ This example updates safelist data for all user mailboxes in your Exchange organ 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 - - Alias - - Distinguished name (DN) - - Canonical DN - -- \<domain name\>\\\<account name\> - +- Domain\\Username - Email address - - GUID - - LegacyExchangeDN - - SamAccountName - - User ID or user principal name (UPN) ```yaml @@ -91,8 +88,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -125,7 +121,7 @@ Accept wildcard characters: False ``` ### -EnsureJunkEmailRule -The EnsureJunkEmailRule parameter specifies whether to force the junk email rule to be turned on for the mailbox if the rule isn't turned on already. +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. @@ -143,7 +139,9 @@ Accept wildcard characters: False ``` ### -IncludeDomains -The IncludeDomains switch specifies whether to include the sender domains specified by users in Outlook in the safelist aggregation data. By default, domains specified by the senders aren't included. +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. In most cases, we don't recommend that you include domains because users may include the domains of large Internet service providers (ISPs), which could unintentionally provide addresses that may be used or spoofed by spammers. @@ -199,12 +197,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-SiteMailbox.md b/exchange/exchange-ps/exchange/Update-SiteMailbox.md similarity index 85% rename from exchange/exchange-ps/exchange/sharing-and-collaboration/Update-SiteMailbox.md rename to exchange/exchange-ps/exchange/Update-SiteMailbox.md index a59225a70f..e56a3a732f 100644 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Update-SiteMailbox.md +++ b/exchange/exchange-ps/exchange/Update-SiteMailbox.md @@ -1,23 +1,24 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/update-sitemailbox +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-SiteMailbox ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. Site mailboxes were removed from Exchange Online and SharePoint Online in 2017. +This cmdlet is available only in on-premises Exchange. Use the Update-SiteMailbox cmdlet to trigger a Microsoft SharePoint synchronization. This command synchronizes document content membership and permissions into Microsoft Exchange. You may need to perform this action when troubleshooting document or membership synchronization issues. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX @@ -29,13 +30,14 @@ Update-SiteMailbox [-Identity] <RecipientIdParameter> [-Organization <OrganizationIdParameter>] [-Server <String>] [-Target <TargetType>] - [-WhatIf] [<CommonParameters>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION If you are running this command against a site mailbox in which you aren't the owner, you need to use the BypassOwnerCheck parameter to run this cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,15 +61,10 @@ This example updates the site mailbox WinterHoliday@tailspintoys.com and perform 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 - - Alias - - Distinguished name (DN) - - Canonical DN - - Email address - - GUID ```yaml @@ -84,7 +81,9 @@ Accept wildcard characters: False ``` ### -BypassOwnerCheck -The BypassOwnerCheck parameter specifies that the user running the command in the Exchange Management Shell isn't a site mailbox owner or member. If you run the command without this parameter and you aren't the site mailbox owner or member, the command doesn't run or return any information. +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. ```yaml Type: SwitchParameter @@ -102,8 +101,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -120,7 +118,7 @@ Accept wildcard characters: False ``` ### -FullSync -The FullSync parameter specifies full sync is expensive and will have a performance impact on the Exchange system. +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 @@ -171,9 +169,7 @@ Accept wildcard characters: False 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 - - Document - - Membership If you don't specify this parameter when you run the cmdlet, this parameter value defaults to ALL. @@ -212,12 +208,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-StoreMailboxState.md b/exchange/exchange-ps/exchange/Update-StoreMailboxState.md similarity index 87% rename from exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-StoreMailboxState.md rename to exchange/exchange-ps/exchange/Update-StoreMailboxState.md index 42fda9543f..d586e3c49e 100644 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Update-StoreMailboxState.md +++ b/exchange/exchange-ps/exchange/Update-StoreMailboxState.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/update-storemailboxstate +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" --- # Update-StoreMailboxState @@ -17,19 +16,21 @@ This cmdlet is available only in on-premises Exchange. Use the Update-StoreMailboxState cmdlet to synchronize the mailbox state for a mailbox in the Exchange mailbox store with the state of the corresponding Active Directory user account. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Update-StoreMailboxState -Database <DatabaseIdParameter> -Identity <StoreMailboxIdParameter> [-Confirm] - [-WhatIf] [<CommonParameters>] +Update-StoreMailboxState -Database <DatabaseIdParameter> -Identity <StoreMailboxIdParameter> + [-Confirm] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Update-StoreMailboxState cmdlet forces the mailbox store state in the Exchange store to be synchronized with Active Directory. In some cases, it's possible that the store state for a mailbox to become out-of-sync with the state of the corresponding Active Directory user account. This can result from Active Directory replication latency. For example, if a mailbox-enabled user account is disabled in Active Directory but isn't marked as disabled in the Exchange mailbox store. In this case, running the Update-StoreMailboxState will synchronize the mailbox store state with the state of the Active Directory user account and mark the mailbox as disabled in the mailbox store. You can use this command to troubleshoot issues that may be a result when the store state for a mailbox is unexpected or if you suspect that the store state is different than the state for the corresponding Active Directory account. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -60,9 +61,7 @@ This example updates the mailbox state for all disconnected mailboxes on the mai The Database parameter specifies the mailbox database that contains the mailbox. You can use any value that uniquely identifies the database. For example: - Name - - Distinguished name (DN) - - GUID ```yaml @@ -99,8 +98,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -137,17 +135,17 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 -In a scenario where a mailbox is moved to another database, then the mailbox is immediately disabled, there is a 24-hour delay to allow for replication. +If a mailbox is moved to another database, the mailbox is immediately disabled. There's a 24-hour delay to allow for replication. -In this scenario Update-StoreMailboxState may not immediately update DisconnectState and DisconnectReason when running Get-MailboxStatistics. The mailbox statistics will update approximately 24 hours after the move. +In this scenario, Update-StoreMailboxState might not immediately update the DisconnectState and DisconnectReason properties in the output of Get-MailboxStatistics. The values will update approximately 24 hours after the move. ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md new file mode 100644 index 0000000000..f8a3ee84e0 --- /dev/null +++ b/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md @@ -0,0 +1,391 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Update-VivaModuleFeaturePolicy + +## SYNOPSIS +This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). + +Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a feature in a Viva module in Viva. + +- You can't update a policy for a particular user or group to include the entire tenant if a policy for the entire tenant already exists for the feature. Only one tenant-wide policy is supported. +- Policies assigned to a specific user or group take priority over the policy assigned to the entire tenant when determining whether a feature is enabled. If a user has multiple policies assigned for a feature (directly as a user or member of a group), the most restrictive policy applies. +- Some features only support policies that apply to the entire tenant, not specific users or groups. You can refer to supported policy scopes for a feature using the [Get-VivaModuleFeature](https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeature) cmdlet. + +Some features include the option for user controls (user opt out). Refer to the feature documentation to see if user controls are available for the feature that you intend to set a policy for. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX +``` +Update-VivaModuleFeaturePolicy -FeatureId <String> -ModuleId <String> -PolicyId <String> + [-Confirm] + [-Everyone <Boolean>] + [-IsFeatureEnabled <Boolean>] + [-IsUserControlEnabled <Boolean>] + [-IsUserOptedInByDefault <Boolean>] + [-GroupIds <String[]>] + [-Name <String>] + [-ResultSize <Unlimited>] + [-UserIds <String[]>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a feature in a Viva module in Viva. + +This cmdlet updates the attributes of the policy that you specify. These attributes include: + +- The policy name (Name parameter). +- Whether or not the policy enables the feature (IsFeatureEnabled parameter). +- Whether or not the policy enables user controls (IsUserControlEnabled parameter, only applicable to a feature policy). +- Who the policy applies to (the UserIds and GroupIds parameters or the Everyone parameter). + +You can update these attributes independently of each other. For example, if you specify the Name parameter but not the IsFeatureEnabled parameter, the name of the policy is updated but whether or not the policy enables the feature remains unchanged. + +**Important**: Values that you specify for the UserIds and/or GroupIds parameters or the Everyone parameter **overwrite** any existing users or groups. To preserve the existing users and groups, you need to specify those existing users or groups **and** any additional users or groups that you want to add. Not including existing users or groups in the command effectively removes those specific users or groups from the policy. For more information, see the examples. + +You need to use the Connect-ExchangeOnline cmdlet to authenticate. + +This cmdlet requires the .NET Framework 4.7.2 or later. + +Currently, you need to be a member of the Global Administrators role or the roles that have been assigned at the feature level to run this cmdlet. + +To learn more about assigned roles at the feature level, see [Features Available for Feature Access Management](https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management). + +To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +## EXAMPLES + +### Example 1 +```powershell +Update-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -PolicyId 3db38dfa-02a3-4039-b33a-42b0b3da029b1 -Name NewPolicyName -IsFeatureEnabled $false +``` + +This example updates the name of the specified policy and makes it so the policy does not enable the feature. + +### Example 2 +```powershell +Update-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -PolicyId 3db38dfa-02a3-4039-b33a-42b0b3da029b -GroupIds group1@contoso.com,group2@contoso.com +``` + +This example updates who the specified policy applies to. The policy now applies **only** to the specified groups, overwriting the users and groups the policy used to apply to. + +### Example 3 +```powershell +Update-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -PolicyId 3db38dfa-02a3-4039-b33a-42b0b3da029b -UserIds user1@contoso.com,user2@contoso.com +``` + +This example updates who the specified policy applies to. The policy now applies **only** to the specified users, overwriting the users and groups the policy used to apply to. + +### Example 4 +```powershell +Update-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -PolicyId 3db38dfa-02a3-4039-b33a-42b0b3da029b -Name NewPolicyName -IsFeatureEnabled $true -GroupIds group1@contoso.com,57680382-61a5-4378-85ad-f72095d4e9c3 -UserIds user1@contoso.com +``` + +This example updates the name of the specified policy, makes it so the policy enables the feature, and updates who the policy applies to. The policy now applies **only** to the specified users and groups, overwriting the users and groups the policy used to apply to. + +### Example 5 +```powershell +Update-VivaModuleFeaturePolicy -ModuleId PeopleSkills -FeatureId ShowAISkills -PolicyId 3db38dfa-02a3-4039-b33a-42b0b3da029b -IsFeatureEnabled $true -IsUserControlEnabled $true -IsUserOptedInByDefault $false +``` + +This example updates a policy for the ShowAISkills feature in Viva Skills. The policy enables the feature for the users previously added to the policy, allows user controls, and opted out users by default (Soft Disable policy). + +## PARAMETERS + +### -FeatureId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ModuleId +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyId +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. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Everyone +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. +- $false: Don't use this value. + +If you don't want to update who the policy applies to, don't use this parameter. + +Don't use this parameter with the GroupIds or UserIds parameters. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupIds +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. + +The values that you specify for this parameter or the UserIds parameter replace any existing groups. To preserve the existing groups, include them along with any new users or groups that you specify. + +You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.). + +To have the updated policy apply to all users in the organization, use the Everyone parameter with the value $true. + +**Note**: In v3.5.1-Preview2 or later of the module, this parameter supports security group object IDs (GUIDs). Previous versions of the module accept only email addresses for this parameter. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -IsFeatureEnabled +The IsFeatureEnabled parameter specifies whether the feature is enabled by the updated policy. Valid values are: + +- $true: The feature is enabled by the policy. +- $false: The feature is not enabled by the policy. + +If you don't want to update whether the feature is enabled by the policy, don't use this parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsUserControlEnabled +**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: + +- $true: User control is enabled by the policy. Users can opt out of the feature. +- $false: User control isn't enabled by the policy. Users can't opt of the feature. + +Only features that allow admins to enable and disable user controls by policy can use this parameter. If the feature doesn't support admins toggling user controls, the default value applies. See the feature documentation for more information. + +If you don't want to update whether the user control is enabled by the policy, don't use this parameter. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsUserOptedInByDefault +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: + +- $true: By default, users are opted in by the policy if the user hasn't set a preference. +- $false: By default, users are opted out by the policy if the user hasn't set a preference. + +This parameter is optional and can be used to override the default user opt-in value set in the feature metadata. + +This parameter can be set only when the IsUserControlEnabled parameter is set to $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +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. + +If you don't want to update the name of the policy, don't use this parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIds +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. + +The values that you specify for this parameter or the GroupIds parameter replace any existing users. To preserve the existing users, include them along with any new users or groups that you specify. + +You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.). + +To have the updated policy apply to all users in the organization, use the Everyone parameter with the value $true. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Exchange PowerShell](https://learn.microsoft.com/powershell/module/exchange) + +[About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2) + +[Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids) diff --git a/exchange/exchange-ps/exchange/Update-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/Update-eDiscoveryCaseAdmin.md new file mode 100644 index 0000000000..bd36987193 --- /dev/null +++ b/exchange/exchange-ps/exchange/Update-eDiscoveryCaseAdmin.md @@ -0,0 +1,115 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Update-eDiscoveryCaseAdmin + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Update-eDiscoveryCaseAdmin cmdlet to replace all existing eDiscovery Administrators in the Microsoft Purview compliance portal. To add or remove individual eDiscovery Administrators, use the Add-eDiscoveryCaseAdmin and Remove-eDiscoveryCaseAdmin cmdlets. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Update-eDiscoveryCaseAdmin -Users <String[]> + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +An eDiscovery Administrator is a member of the eDiscovery Manager role group who can view and access all eDiscovery cases in the organization. To make a user an eDiscovery Administrator, add them to the eDiscovery Manager role group by running the following command in Security & Compliance PowerShell: `Add-RoleGroupMember -Identity "eDiscovery Manager" -Member "<UserIdentity>"`. + +After the user is a member of the eDiscovery Manager role group, you can then use this cmdlet to add them to the list of eDiscovery Administrators. + +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Update-eDiscoveryCaseAdmin -Users laura@contoso.com,julia@contoso.com +``` + +This example replaces the existing eDiscovery Administrators with new users. + +## PARAMETERS + +### -Users +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 +- Distinguished name (DN) +- Canonical DN +- GUID + +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"`. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. + +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Upgrade-DistributionGroup.md b/exchange/exchange-ps/exchange/Upgrade-DistributionGroup.md new file mode 100644 index 0000000000..d0092da6bc --- /dev/null +++ b/exchange/exchange-ps/exchange/Upgrade-DistributionGroup.md @@ -0,0 +1,122 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Upgrade-DistributionGroup + +## SYNOPSIS +This cmdlet is available only in the cloud-based service. + +Use the Upgrade-DistributionGroup cmdlet to upgrade distribution groups to Microsoft 365 Groups. This cmdlet only works on distribution groups, not mail-enabled security groups. + +**Note**: Before you use this cmdlet, verify there are no email address policies that you created with the IncludeUnifiedGroupRecipients parameter; otherwise the command will fail. Remove and recreate the email address policies after you upgrade your distribution groups to Microsoft 365 Groups. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Upgrade-DistributionGroup [-DlIdentities] <MultiValuedProperty> + [-ActionType <String>] + [-ExecutingUser <RecipientIdParameter>] + [-Organization <OrganizationIdParameter>] + [<CommonParameters>] +``` + +## DESCRIPTION +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Upgrade-DistributionGroup -DlIdentities hr@contoso.com,finance@contoso.com +``` + +This example upgrades the specified distribution groups to Microsoft 365 Groups. + +## PARAMETERS + +### -DlIdentities +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. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ActionType +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExecutingUser +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Organization +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 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mail-flow/Validate-OutboundConnector.md b/exchange/exchange-ps/exchange/Validate-OutboundConnector.md similarity index 79% rename from exchange/exchange-ps/exchange/mail-flow/Validate-OutboundConnector.md rename to exchange/exchange-ps/exchange/Validate-OutboundConnector.md index af16c13056..e096f825c2 100644 --- a/exchange/exchange-ps/exchange/mail-flow/Validate-OutboundConnector.md +++ b/exchange/exchange-ps/exchange/Validate-OutboundConnector.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/validate-outboundconnector +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" --- # Validate-OutboundConnector @@ -15,28 +14,28 @@ monikerRange: "exchonline-ps || eop-ps" ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Validate-OutboundConnector cmdlet to test the settings of Outbound connectors in Office 365. +Use the Validate-OutboundConnector cmdlet to test the settings of Outbound connectors in Microsoft 365. -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). +**Note**: This cmdlet does not set the validation status or timestamp on the connector. To set these values, run the following command: `Set-OutboundConnector -Identity "<ConnectorName>" -IsValidated $true -LastValidationTimestamp (Get-Date).ToUniversalTime()`. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` Validate-OutboundConnector -Identity <OutboundConnectorIdParameter> -Recipients <MultiValuedProperty> - [-Confirm] [-WhatIf] [<CommonParameters>] + [-Confirm] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION The Validate-OutboundConnector cmdlet performs two tests on the specified connector: - SMTP connectivity to each smart host that's defined on the connector. - - Send test email messages to one or more recipients in the domain that's configured on the connector. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,9 +52,7 @@ This example tests the Outbound connector named Contoso.com Outbound Connector. 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 - - Distinguished name - - GUID ```yaml @@ -74,7 +71,7 @@ Accept wildcard characters: False ### -Recipients 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. -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". +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"`. ```yaml Type: MultiValuedProperty @@ -92,8 +89,7 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml @@ -130,12 +126,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### - ## OUTPUTS -### - ## NOTES ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Validate-RetentionRuleQuery.md b/exchange/exchange-ps/exchange/Validate-RetentionRuleQuery.md new file mode 100644 index 0000000000..c4a8ee7175 --- /dev/null +++ b/exchange/exchange-ps/exchange/Validate-RetentionRuleQuery.md @@ -0,0 +1,69 @@ +--- +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 +ms.author: chrisda +ms.reviewer: +--- + +# Validate-RetentionRuleQuery + +## SYNOPSIS +This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). + +Use the Validate-RetentionRuleQuery cmdlet to validate the Keyword Query Language (KQL) content search filters for retention rules. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +Validate-RetentionRuleQuery -KqlQueryString <String> + [<CommonParameters>] +``` + +## DESCRIPTION +To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). + +## EXAMPLES + +### Example 1 +```powershell +Validate-RetentionRuleQuery -KqlQueryString 'from:"Ann Beebe" AND subject:northwind' +``` + +This example validates the specified KQL content search filter. + +## PARAMETERS + +### -KqlQueryString +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). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Write-AdminAuditLog.md b/exchange/exchange-ps/exchange/Write-AdminAuditLog.md similarity index 85% rename from exchange/exchange-ps/exchange/policy-and-compliance-audit/Write-AdminAuditLog.md rename to exchange/exchange-ps/exchange/Write-AdminAuditLog.md index a294ae4465..3545297054 100644 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Write-AdminAuditLog.md +++ b/exchange/exchange-ps/exchange/Write-AdminAuditLog.md @@ -1,13 +1,12 @@ --- external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/write-adminauditlog -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +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 ms.author: chrisda ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" --- # Write-AdminAuditLog @@ -17,13 +16,16 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service. Use the Write-AdminAuditLog cmdlet to write a comment to the administrator audit log. -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX ``` -Write-AdminAuditLog -Comment <String> [-Confirm] - [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] +Write-AdminAuditLog -Comment <String> + [-Confirm] + [-DomainController <Fqdn>] + [-WhatIf] + [<CommonParameters>] ``` ## DESCRIPTION @@ -31,7 +33,7 @@ When the Write-AdminAuditLog cmdlet runs, the value provided in the Comment para For the Write-AdminAuditLog cmdlet to write to the audit log, it must be included in the list of cmdlets being logged by administrator audit logging. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -53,7 +55,7 @@ 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 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -65,15 +67,14 @@ Accept wildcard characters: False ### -Confirm The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -107,7 +108,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -121,12 +122,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS -### +### Input types To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. ## OUTPUTS -### +### 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 diff --git a/exchange/exchange-ps/exchange/active-directory/Get-ADPermission.md b/exchange/exchange-ps/exchange/active-directory/Get-ADPermission.md deleted file mode 100644 index c595209ef2..0000000000 --- a/exchange/exchange-ps/exchange/active-directory/Get-ADPermission.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/active-directory/get-adpermission -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Get-ADPermission -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Get-ADPermission - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Get-ADPermission cmdlet to get permissions on an Active Directory object. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Owner -``` -Get-ADPermission [-Identity] <ADRawEntryIdParameter> [-Owner] - [-DomainController <Fqdn>] [<CommonParameters>] -``` - -### AccessRights -``` -Get-ADPermission [-Identity] <ADRawEntryIdParameter> [-User <SecurityPrincipalIdParameter>] - [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors) Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://docs.microsoft.com/Exchange/permissions/permissions). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ADPermission -Identity Ed -``` - -This example returns the permissions that have been applied to the user Ed. - -### Example 2 -```powershell -Get-ADPermission "Contoso.com" -User Chris -``` - -This example returns the permissions that have been granted to the user Chris on the Contoso.com Receive connector. - -## PARAMETERS - -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -The Owner switch specifies that the owner of the object specified in the Identity parameter should be returned. If the Owner switch is used, the User parameter can't be used. - -```yaml -Type: SwitchParameter -Parameter Sets: Owner -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -The User parameter specifies that only the access control entries (ACEs) granted to the specified user on the object specified in the Identity parameter should be returned. If the User parameter is used, the Owner switch can't be used. - -If the name of the user contains spaces, enclose the name in quotation marks ("). - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: AccessRights -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/advanced-threat-protection/Disable-AntiPhishRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-AntiPhishRule.md deleted file mode 100644 index 37a019b4de..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-AntiPhishRule.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/disable-antiphishrule -applicable: Exchange Online -title: Disable-AntiPhishRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Disable-AntiPhishRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Disable-AntiPhishRule cmdlet to disable antiphish rules in your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Disable-AntiPhishRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Disable-AntiPhishRule -Identity "Engineering Department Phishing Rule" -``` - -This example disables the antiphish rule named Engineering Department Phishing Rule. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-SafeAttachmentRule.md deleted file mode 100644 index 547f57cde5..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-SafeAttachmentRule.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/disable-safeattachmentrule -applicable: Exchange Online, Exchange Online Protection -title: Disable-SafeAttachmentRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Disable-SafeAttachmentRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Disable-SafeAttachmentRule cmdlet to disable enabled Safe Attachments rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Disable-SafeAttachmentRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Disable-SafeAttachmentRule -Identity "Engineering Department Attachment Rule" -``` - -This example disables the Safe Attachments rule named Engineering Department Attachment Rule. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the enabled Safe Attachments rule that you want to disable. - -You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-SafeLinksRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-SafeLinksRule.md deleted file mode 100644 index f7abb94954..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Disable-SafeLinksRule.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/disable-safelinksrule -applicable: Exchange Online, Exchange Online Protection -title: Disable-SafeLinksRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Disable-SafeLinksRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Disable-SafeLinksRule cmdlet to disable enabled Safe Links rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Disable-SafeLinksRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Disable-SafeLinksRule -Identity "Engineering Department URL Rule" -``` - -This example disables the enabled Safe Links rule named Engineering Department URL Rule. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-AntiPhishRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-AntiPhishRule.md deleted file mode 100644 index 565e9bcdfa..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-AntiPhishRule.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/enable-antiphishrule -applicable: Exchange Online -title: Enable-AntiPhishRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Enable-AntiPhishRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Enable-AntiPhishRule cmdlet to enable antiphish rules in your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Enable-AntiPhishRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Enable-AntiPhishRule -Identity "Marketing Department Phishing Rule" -``` - -This example enables the antiphish rule named Marketing Department Phishing Rule. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-SafeAttachmentRule.md deleted file mode 100644 index afb4db11e3..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-SafeAttachmentRule.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/enable-safeattachmentrule -applicable: Exchange Online, Exchange Online Protection -title: Enable-SafeAttachmentRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Enable-SafeAttachmentRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Enable-SafeAttachmentRule cmdlet to enable disabled Safe Attachments rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Enable-SafeAttachmentRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Enable-SafeAttachmentRule -Identity "Marketing Department Attachment Rule" -``` - -This example enables the disabled Safe Attachments rule named Marketing Department Attachment Rule. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the disabled Safe Attachments rule that you want to enable. - -You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-SafeLinksRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-SafeLinksRule.md deleted file mode 100644 index f39da33fad..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Enable-SafeLinksRule.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/enable-safelinksrule -applicable: Exchange Online, Exchange Online Protection -title: Enable-SafeLinksRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Enable-SafeLinksRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Enable-SafeLinksRule cmdlet to enable disabled Safe Links rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Enable-SafeLinksRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Enable-SafeLinksRule -Identity "Marketing Department URL Rule" -``` - -This example enables the disabled Safe Links rule named Marketing Department URL Rule. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentDetail.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentDetail.md deleted file mode 100644 index f47bd2bec4..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentDetail.md +++ /dev/null @@ -1,233 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-advancedthreatprotectiondocumentdetail -applicable: Exchange Online, Exchange Online Protection -title: Get-AdvancedThreatProtectionDocumentDetail -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-AdvancedThreatProtectionDocumentDetail - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. Use the Get-AdvancedThreatProtectionDocumentDetailReport cmdlet to view the results of Office 365 Advanced Threat Protection (ATP) actions for files in SharePoint Online, OneDrive for Business and Microsoft Teams in your cloud-based organization. For more information about this feature, see article at: https://go.microsoft.com/fwlink/?linkid=857638 - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AdvancedThreatProtectionDocumentDetail [-Action <MultiValuedProperty>] [-Domain <MultiValuedProperty>] [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] [-Organization <OrganizationIdParameter>] [-Page <Int32>] [-PageSize <Int32>] [-ProbeTag <String>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -For the reporting period and organization you specify, the cmdlet returns the following information: - -- Action - -- Document Id - -- Domain - -- Event Type - -- File Hash - -- File Name - -- File Path - -- Size - -- Timestamp - -- Workload - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AdvancedThreatProtectionDocumentDetail -Organization contoso.com -StartDate "4/26/2016" -EndDate "4/28/2016" | Format-Table -``` - -This example returns the detailed report of ATP detections during the specified date range. - -## PARAMETERS - -### -Action -The Action parameter filters the results by the action taken on the attachment or link. Valid values are: - -- Allow - -- BlockAccess - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. The event type you specify must correspond to the report. For example, you can only specify "Anti-malware engine" or "Advanced Threat Protection" events for malware reports. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Organization -The Organization parameter specifies the organization for which the report is being presented. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentReport.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentReport.md deleted file mode 100644 index e1829acadc..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentReport.md +++ /dev/null @@ -1,253 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-advancedthreatprotectiondocumentreport -applicable: Exchange Online, Exchange Online Protection -title: Get-AdvancedThreatProtectionDocumentReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-AdvancedThreatProtectionDocumentReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-AdvancedThreatProtectionDocumentReport cmdlet to view the results of Office 365 Advanced Threat Protection (ATP) actions for files in SharePoint Online, OneDrive for Business and Microsoft Teams in your cloud-based organization. For more information about this feature, see article at: https://go.microsoft.com/fwlink/?linkid=857638 - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AdvancedThreatProtectionDocumentReport - [-Action <MultiValuedProperty>] - [-AggregateBy <String>] - [-Domain <MultiValuedProperty>] - [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] - [-Organization <OrganizationIdParameter>] - [-Page <Int32>] - [-PageSize <Int32>] - [-ProbeTag <String>] - [-StartDate <DateTime>] - [<CommonParameters>] -``` - -## DESCRIPTION -For the reporting period and organization you specify, the cmdlet returns the following information: - -- Action - -- Count - -- Date - -- Domain - -- Event Type - -- Workload - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AdvancedThreatProtectionTrafficReport -Organization contoso.com -StartDate "4/26/2018" -EndDate "4/28/2018" | Format-Table -``` - -This example returns the aggregated report of ATP detections for the specified organization during the specified date range. - -## PARAMETERS - -### -Action -The Action parameter filters the results by the action taken on the attachment or link. Valid values are: - -- Allow - -- BlockAccess - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AggregateBy -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -The EndDate parameter specifies the end date of the date range. - -Use the short date format which is defined in the Regional Options settings on the computer where you are 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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. The event type you specify must correspond to the report. For example, you can only specify "Anti-malware engine" or "Advanced Threat Protection" events for malware reports. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Organization -The Organization parameter specifies the organization for which the report is being presented. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -The StartDate parameter specifies the start date of the date range. - -Use the short date format which is defined in the Regional Options settings on the computer where you are 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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionTrafficReport.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionTrafficReport.md deleted file mode 100644 index 281e470ec6..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionTrafficReport.md +++ /dev/null @@ -1,331 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-advancedthreatprotectiontrafficreport -applicable: Exchange Online, Exchange Online Protection -title: Get-AdvancedThreatProtectionTrafficReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-AdvancedThreatProtectionTrafficReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-AdvancedThreatProtectionTrafficReport cmdlet to view the results of Safe Attachments and Safe Links actions in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AdvancedThreatProtectionTrafficReport [-Action <MultiValuedProperty>] [-AggregateBy <String>] - [-Direction <MultiValuedProperty>] [-DisplayBy <String>] [-Domain <MultiValuedProperty>] [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] [-Expression <Expression>] [-MalwareName <MultiValuedProperty>] - [-Page <Int32>] [-PageSize <Int32>] [-ProbeTag <String>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -For the reporting period you specify, the cmdlet returns the following information: - -- Domain - -- Date - -- Event Type - -- MalwareName - -- Action - -- Message Count - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AdvancedThreatProtectionTrafficReport -StartDate "4/26/2016" -EndDate "4/28/2016" | Format-Table -``` - -This example returns the results of Safe Attachments and Safe Links actions during the specified date range. - -## PARAMETERS - -### -Action -The Action parameter filters the results by the action taken on the attachment or link. Valid values are: - -- Allow - -- AllowRedirect - -- BlockAccess - -- BlockRedirect - -- BypassMessage - -- BypassMessageSystem - -- ContentReplaced - -- InfectedAllowed - -- ReplaceRedirect - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AggregateBy -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayBy -The DisplayBy parameter specifies how the information in the report is organized. Valid values are: - -- Action (This is the default value) - -- MalwareName - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MalwareName -The MalwareName parameter filters the results by malware payload. Valid values are: - -- Excel - -- EXE - -- Flash - -- Others - -- PDF - -- PowerPoint - -- URL - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishRule.md deleted file mode 100644 index 6ddce08459..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishRule.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-antiphishrule -applicable: Exchange Online -title: Get-AntiPhishRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-AntiPhishRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-AntiPhishRule cmdlet to view antiphish rules in your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AntiPhishRule [[-Identity] <RuleIdParameter>] [-State <RuleState>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AntiPhishRule | Format-Table Name,Priority,State -``` - -This example returns a summary list of all antiphish rules in your organization. - -### Example 2 -```powershell -Get-AntiPhishRule -Identity "Research Department Phishing Rule" -``` - -This example returns detailed information about the antiphish rule named Research Department Phishing Rule. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md deleted file mode 100644 index 470471b648..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-atppolicyforo365 -applicable: Exchange Online, Exchange Online Protection -title: Get-AtpPolicyForO365 -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-AtpPolicyForO365 - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-AtpPolicyForO365 cmdlet to view the Advanced Threat Protection (ATP) policy in Office 365. The ATP policy enables the following protections: - -- Safe Links for Office 365 ProPlus desktop clients and Office Mobile apps. - -- Safe Documents: Before a user is allowed to trust a file open in Office 365 ProPlus, the file will be verified by Microsoft Defender ATP. - -- ATP to protect files in SharePoint Online, OneDrive for Business and Microsoft Teams. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AtpPolicyForO365 [[-Identity] <AtpPolicyForO365IdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. For more information, see [Office 365 ATP Safe Links](https://docs.microsoft.com/microsoft-365/security/office-365-security/atp-safe-links). - -ATP can also protect files in SharePoint Online, OneDrive for Business and Microsoft Teams by preventing users from opening and downloading files that are identified as malicious. For more information, see [Office 365 ATP for SharePoint, OneDrive, and Microsoft Teams](https://go.microsoft.com/fwlink/p/?linkid=857638). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AtpPolicyForO365 -``` - -This example returns detailed information about the ATP policy named Default - -## PARAMETERS - -### -Identity -The Identity parameter specifies the ATP policy that you want to modify. There's only one policy named Default. - -```yaml -Type: AtpPolicyForO365IdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-MailDetailATPReport.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-MailDetailATPReport.md deleted file mode 100644 index 4a39a53b03..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-MailDetailATPReport.md +++ /dev/null @@ -1,355 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-maildetailatpreport -applicable: Exchange Online, Exchange Online Protection -title: Get-MailDetailATPReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-MailDetailATPReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MailDetailATPReport cmdlet to list details about Exchange Online Protection and Advanced Threat protection (ATP) detections in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailDetailATPReport [-Direction <MultiValuedProperty>] - [-Domain <MultiValuedProperty>] [-EndDate <DateTime>] [-EventType <MultiValuedProperty>] - [-Expression <Expression>] [-MalwareName <MultiValuedProperty>] [-MessageId <MultiValuedProperty>] - [-MessageTraceId <MultiValuedProperty>] [-Page <Int32>] [-PageSize <Int32>] [-ProbeTag <String>] - [-RecipientAddress <MultiValuedProperty>] [-SenderAddress <MultiValuedProperty>] [-StartDate <DateTime>] - [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailDetailATPReport -StartDate 7/1/2018 -EndDate 7/31/2018 -``` - -This example returns the Advanced Threat Protection actions for July, 2018. - -## PARAMETERS - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. Valid values are: - -Email phish EventTypes: - -- Advanced phish filter (Indicates a message caught by the Office 365 machine learning model.) - -- Anti-spoof: Intra-org (Indicates an internal message caught by anti-phish spoof protection.) - -- Anti-spoof: external domain (Indicates an external message caught by anti-phish spoof protection.) - -- Domain impersonation\* (Indicates a message impersonating a domain protected by an anti-phish policy.) - -- User impersonation\* (Indicates a message impersonating a user protected by an anti-phish policy.) - -- Brand impersonation (Indicates a message caught by Office 365 phish filters as impersonating a known brand.) - -- General phish filter (Indicates a message caught by basic Office 365 phish protection.) - -- Malicious URL reputation (Indicates a message with a known malicious URL caught by Office 365 phish filters.) - -- Phish ZAP (Indicates a phish or spam message detected and auto-purged after delivery.) - -Email malware EventTypes: - -- Anti-malware engine (Indicates a message caught by the Office 365 anti-malware engine.) - -- ATP safe attachments\* (Indicates a message with a malicious attachment blocked by ATP.) - -- ATP safe links\* (Indicates when a malicious link is blocked by ATP.) - -- ZAP (Indicates a message with malware detected and auto-purged after delivery.) - -- Office 365 file reputation (Indicates a message with a known malicious file blocked.) - -- Anti-malware policy file type block (Indicates when the Common Attachment Types filter blocks a file.) - -Content malware EventTypes: - -- AtpDocumentMalware\* (Indicates malicious content detected by ATP Safe Attachments in the cloud.) - -- AvDocumentMalware (Indicates malware found by the Office 365 anti-malware engine. Reporting requires ATP or E5.) - -\* These features require a standalone Office 365 ATP or E5 subscription. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MalwareName -The MalwareName parameter filters the results by malware payload. Valid values are: - -- Excel - -- EXE - -- Flash - -- Others - -- PDF - -- PowerPoint - -- URL - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageId -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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageTraceId -The MessageTraceId parameter can be used with the recipient address to uniquely identify a message trace and obtain more details. A message trace ID is generated for every message that's processed by the system. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-MailTrafficATPReport.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-MailTrafficATPReport.md deleted file mode 100644 index d82b18fdc6..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-MailTrafficATPReport.md +++ /dev/null @@ -1,339 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-mailtrafficatpreport -applicable: Exchange Online, Exchange Online Protection -title: Get-MailTrafficATPReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-MailTrafficATPReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MailTrafficATPReport cmdlet to view the results of Exchange Online Protection and Advanced Threat Protection (ATP) detections in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailTrafficATPReport [-Action <MultiValuedProperty>] [-AggregateBy <String>] - [-Direction <MultiValuedProperty>] [-Domain <MultiValuedProperty>] [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] [-Expression <Expression>] [-Page <Int32>] [-PageSize <Int32>] - [-ProbeTag <String>] [-StartDate <DateTime>] [-SummarizeBy <MultiValuedProperty>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -For the reporting period you specify, the cmdlet returns the following information: - -- Domain - -- Date - -- Event Type - -- Direction - -- Action - -- Message Count - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailTrafficATPReport -Direction Inbound -StartDate 06/13/2018 -EndDate 06/15/2018 -``` - -This example retrieves details for incoming messages between June 13, 2018 and June 15, 2018. - -### Example 2 -```powershell -Get-MailTrafficATPReport -StartDate 7/20/2018 -EndDate 7/20/2018 -Direction Outbound | Format-Table Domain,Date,EventType,Action,MessageCount -``` - -This example retrieves the statistics for outgoing messages on July 20, 2018 and displays the results in a table. Every unique combination of EventType and Action is displayed on a separate row in the table. - -### Example 3 -```powershell -Get-MailTrafficATPReport -StartDate 7/20/2018 -EndDate 7/20/2018 -Direction Outbound -SummarizeBy Domain,EventType | Format-Table Domain,Date,EventType,Action,MessageCount -``` - -This example is similar to the previous example, but now the results are summarized. Because EventType is one of the summarized values, the rows in the table now contain the unique values of Action. The total number of rows in the report is reduced and values of MessageCount are correspondingly larger on each row. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AggregateBy -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. Valid values are: - -- Message passed (Indicates a good message.) - -Email phish EventTypes: - -- Advanced phish filter (Indicates a message caught by the Office 365 machine learning model.) - -- Anti-spoof: Intra-org (Indicates an internal message caught by anti-phish spoof protection.) - -- Anti-spoof: external domain (Indicates an external message caught by anti-phish spoof protection.) - -- Domain impersonation\* (Indicates a message impersonating a domain protected by an anti-phish policy.) - -- User impersonation\* (Indicates a message impersonating a user protected by an anti-phish policy.) - -- Brand impersonation (Indicates a message caught by Office 365 phish filters as impersonating a known brand.) - -- General phish filter (Indicates a message caught by basic Office 365 phish protection.) - -- Malicious URL reputation (Indicates a message with a known malicious URL caught by Office 365 phish filters.) - -- Phish ZAP (Indicates a phish or spam message detected and auto-purged after delivery.) - -Email malware EventTypes: - -- Anti-malware engine (Indicates a message caught by the Office 365 anti-malware engine.) - -- ATP safe attachments\* (Indicates a message with a malicious attachment blocked by ATP.) - -- ATP safe links\* (Indicates when a malicious link is blocked by ATP.) - -- ZAP (Indicates a message with malware detected and auto-purged after delivery.) - -- Office 365 file reputation (Indicates a message with a known malicious file blocked.) - -- Anti-malware policy file type block (Indicates when the Common Attachment Types filter blocks a file.) - -Content malware EventTypes: - -- AtpDocumentMalware\* (Indicates malicious content detected by ATP Safe Attachments in the cloud.) - -- AvDocumentMalware (Indicates malware found by the Office 365 anti-malware engine. Reporting requires ATP/E5.) - -\* These features require a standalone Office 365 ATP or E5 subscription. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SummarizeBy -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 the Get-MailTrafficATPReport cmdlet, valid values are Action, Direction, Domain, and EventType. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-PhishFilterPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-PhishFilterPolicy.md deleted file mode 100644 index d5bb7cc8b1..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-PhishFilterPolicy.md +++ /dev/null @@ -1,243 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-phishfilterpolicy -applicable: Exchange Online, Exchange Online Protection -title: Get-PhishFilterPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-PhishFilterPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-PhishFilterPolicy cmdlet to view the spoof intelligence policy and detected spoofed sending activities in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-PhishFilterPolicy [[-Identity] <HostedConnectionFilterPolicyIdParameter>] - [-AllowedToSpoof <String>] - [-ConfidenceLevel <ConfidenceLevel>] - [-DecisionSetBy <DecisionSetBy>] - [-Detailed] - [-SpoofAllowBlockList] - [-SpoofType <String>] - [-WidgetData] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-PhishFilterPolicy cmdlet returns the following information: - -- Sender: The true sending domain that's found in the DNS record of the source email server. If no domain is found, the source email server's IP address is shown. - -- SpoofedUser: The sending email address if the domain is one of your organization's domains, or the sending domain if the domain is external. - -- NumberOfMessages: The number of messages. - -- NumberOfUserComplaints: The number of user complaints. - -- AuthenticationResult: Indicates whether the message has passed any type of email authentication (SPF, DKIM, or DMARC) (explicit or implicit). - -- LastSeen: The date when the sending email address or domain was last seen by Office 365. - -- DecisionSetBy: Specifies whether Office 365 set the spoofing policy as allowed or not allowed to spoof, or if it was set by an admin. - -- AllowedToSpoof: The three possible values are Yes (messages that contain any spoofed sender email addresses in your organization are allowed from the source email server), No (messages that contain any spoofed sender email addresses in your organization are not allowed from the source email server), and Partial (messages that contain some spoofed sender email addresses in your organization are allowed from the source email server). - -- SpoofType: Indicates whether the domain is internal to your organization or external. - -For more information about spoof intelligence, see [Learn more about spoof intelligence](https://go.microsoft.com/fwlink/p/?linkid=869584). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-PhishFilterPolicy -Detailed -SpoofType Internal -``` - -This example returns the list of senders that appear to be sending spoofed email to your organization, with the additional ConfidenceLevel and DomainPairsCountInCategory properties. - -### Example 2 -```powershell -$file = "C:\My Documents\Summary Spoofed Internal Domains and Senders.csv"; Get-PhishFilterPolicy -Detailed -SpoofType Internal | Export-CSV $file -``` - -This example exports the same list of spoofed senders to a CSV file. - -## PARAMETERS - -### -Identity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: HostedConnectionFilterPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AllowedToSpoof -The AllowedToSpoof parameter filters the results by the AllowedToSpoof property value. Valid values are: - -- Yes -- No -- Partial - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConfidenceLevel -The ConfidenceLevel parameter filters the results by the specified confidence level. Valid values are: - --Low --High - -You can only see the ConfidenceLevel value in the results when you include the Detailed switch in the command. - -```yaml -Type: ConfidenceLevel -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DecisionSetBy -The DecisionSetBy parameter filters the results by who allowed or blocked the spoofed sender. Valid values are: - --Admin --SpoofProtection - -```yaml -Type: DecisionSetBy -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Detailed -The Detailed switch specifies whether to return detailed information in the results. You don't need to specify a value with this switch. - -Specifically, this switch returns the following additional properties: - -- ConfidenceLevel -- DomainPairsCountInCategory - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpoofAllowBlockList -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpoofType -The SpoofType parameter filters the results by the type of spoofing. Valid values are: - -- Internal -- External - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WidgetData -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeAttachmentPolicy.md deleted file mode 100644 index 85cf1d1516..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeAttachmentPolicy.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-safeattachmentpolicy -applicable: Exchange Online, Exchange Online Protection -title: Get-SafeAttachmentPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-SafeAttachmentPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-SafeAttachmentPolicy cmdlet to view Safe Attachments policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SafeAttachmentPolicy [[-Identity] <SafeAttachmentPolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SafeAttachmentPolicy -``` - -This example shows a summary list of all Safe Attachments policies. - -### Example 2 -```powershell -Get-SafeAttachmentPolicy -Identity Default | Format-List -``` - -This example shows detailed information about the Safe Attachments policy named Default. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Safe Attachments policy that you want to view. - -You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: SafeAttachmentPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeAttachmentRule.md deleted file mode 100644 index 826f900178..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeAttachmentRule.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-safeattachmentrule -applicable: Exchange Online, Exchange Online Protection -title: Get-SafeAttachmentRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-SafeAttachmentRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-SafeAttachmentRule cmdlet to view Safe Attachments rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SafeAttachmentRule [[-Identity] <RuleIdParameter>] [-State <RuleState>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SafeAttachmentRule -``` - -This example returns a summary list of all Safe Attachments rules in your organization. - -### Example 2 -```powershell -Get-SafeAttachmentRule -Identity "Research Department Attachment Rule" | Format-List -``` - -This example returns detailed information about the Safe Attachments rule named Research Department Attachment Rule. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Safe Attachments rule that you want to view. - -You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -State -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeLinksPolicy.md deleted file mode 100644 index 6c04851917..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeLinksPolicy.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-safelinkspolicy -applicable: Exchange Online, Exchange Online Protection -title: Get-SafeLinksPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-SafeLinksPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-SafeLinksPolicy cmdlet to view Safe Links policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SafeLinksPolicy [[-Identity] <SafeLinksPolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SafeLinksPolicy | Format-Table Name,IsEnabled,IsDefault -``` - -This example shows a summary list of all Safe Links policies. - -### Example 2 -```powershell -Get-SafeLinksPolicy -Identity Default -``` - -This example shows detailed information about the Safe Links policy named Default. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: SafeLinksPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeLinksRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeLinksRule.md deleted file mode 100644 index 036a99ee91..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SafeLinksRule.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-safelinksrule -applicable: Exchange Online, Exchange Online Protection -title: Get-SafeLinksRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-SafeLinksRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-SafeLinksRule cmdlet to view Safe Links rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SafeLinksRule [[-Identity] <RuleIdParameter>] [-State <RuleState>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SafeLinksRule | Format-Table -Auto Name,State,Priority,SafeLinksPolicy,Comments -``` - -This example returns a summary list of all Safe Links rules in your organization. - -### Example 2 -```powershell -Get-SafeLinksRule -Identity "Research Department URL Rule" -``` - -This example returns detailed information about the Safe Links rule named Research Department URL Rule. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -State -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SpoofMailReport.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SpoofMailReport.md deleted file mode 100644 index 2c9113c60f..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-SpoofMailReport.md +++ /dev/null @@ -1,238 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-spoofmailreport -applicable: Exchange Online, Exchange Online Protection -title: Get-SpoofMailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-SpoofMailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-SpoofMailReport cmdlet to view information about insider spoofing in your cloud-based organization. Insider spoofing is where the sender's email address in an inbound message appears to represent your organization, but the actual identity of the sender is different. Insider spoofing is a common tactic that's used in phishing messages to obtain user credentials or steal money. - -This cmdlet is only available in Office 365 Enterprise E5, or with Advanced Threat Protection licenses. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SpoofMailReport [-Action <MultiValuedProperty>] [-Direction <MultiValuedProperty>] [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] [-Expression <Expression>] [-Page <Int32>] [-PageSize <Int32>] - [-ProbeTag <String>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -The spoof mail report is a feature in Advanced Threat Protection that you can use to query information about insider spoofing detections in the last 30 days. For the reporting period you specify, the Get-SpoofMailReport cmdlet returns the following information: - -- Date: Date the message was sent. - -- Event Type: Typically, this value is SpoofMail. - -- Direction: This value is Inbound. - -- Domain: The sender domain. This corresponds to one of your organization's accepted domains. - -- Action: Typically, this value is GoodMail or CaughtAsSpam. - -- Spoofed Sender: The spoofed email address or domain in your organization from which the messages appear to be coming. - -- True Sender: The organizational domain of the PTR record, or pointer record, of the sending IP address, also known as the reverse DNS address. If the sending IP address does not have a PTR record, this field will be blank and the Sender IP column will be filled in. Both columns will not be filled in at the same time. - -- Sender IP: The IP address or address range of the source messaging server. If the sending IP address does have a PTR record, this field will be blank and the True Sender column will be filled in. Both columns will not be filled in at the same time. - -- Count: The number of spoofed messages that were sent to your organization from the source messaging server during the specified time period. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SpoofMailReport -StartDate 03/01/2016 -EndDate 03/31/2016 -``` - -This example shows the insider spoofing detections in your organization during the month of March 2016. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. - -Common values for this report are GoodMail and CaughtAsSpam. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. - -You can specify multiple values separated by commas. - -The common value for this report is SpoofMail. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-UrlTrace.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Get-UrlTrace.md deleted file mode 100644 index cc43db8abf..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Get-UrlTrace.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/get-urltrace -applicable: Exchange Online, Exchange Online Protection -title: Get-UrlTrace -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-UrlTrace - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-UrlTrace cmdlet to view the results of Safe Links actions in your cloud-based organization. Currently, the date range can't be more than seven days. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-UrlTrace [-ClickId <Guid>] [-EndDate <DateTime>] [-Expression <Expression>] [-Page <Int32>] - [-PageSize <Int32>] [-RecipientAddress <MultiValuedProperty>] [-StartDate <DateTime>] - [-UrlOrDomain <MultiValuedProperty>] [-Workloads <MultiValuedProperty>] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. For more information about Advanced Threat Protection Safe Links, see [Office 365 ATP Safe Links](https://docs.microsoft.com/microsoft-365/security/office-365-security/atp-safe-links). - -The following list described the values that are returned in the output of this cmdlet: - -- ClickId: A GUID for each URL that was analyzed in a message. - -- Clicked: The date/time when the URL in the message body was clicked. Every analyzed URL click is recorded, even when a user clicks a URL in an existing message that's already been scanned. - -- UrlBlocked: The URL was detected as malicious by Safe Links (only the initial block, not subsequent clicks), or the user clicked the URL while the scan in progress (users are taken to a notification page that asks them to try again after the scan is complete). - -- UrlClicked: The URL is blocked, but the applicable Safe Links policy has the DoNotAllowClickThrough parameter value $false (click through is allowed). Updated policies aren't applied to existing messages that have already been scanned. New or updated policies are applied to new messages that were received after the policy is applied to the mailbox. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-UrlTrace -RecipientAddress "michelle@contoso.com" -StartDate "5/9/2016" -EndDate "5/11/2016" -``` - -This example returns the results of Safe Links actions during the specified time period for the user michelle@contoso.com. - -## PARAMETERS - -### -ClickId -The ClickId parameter filters the results by the URL that was scanned in the message. Each URL is represented as a GUID value. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAddress -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -UrlOrDomain -The UrlOrDomain parameter filters the results by the specified URL or domain value. - -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Workloads -The Workloads parameter filters the results by the specified workload. Valid values are: - -- Mail - -- OfficeClient - -- Other - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishPolicy.md deleted file mode 100644 index 07da11059b..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishPolicy.md +++ /dev/null @@ -1,760 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/new-antiphishpolicy -applicable: Exchange Online -title: New-AntiPhishPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# New-AntiPhishPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-AntiPhishPolicy cmdlet to create antiphish policies in your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-AntiPhishPolicy [-Name] <String> - [-AdminDisplayName <String>] - [-AuthenticationFailAction <SpoofAuthenticationFailAction>] - [-Confirm] - [-EnableAntiSpoofEnforcement <Boolean>] - [-Enabled <Boolean>] - [-EnableMailboxIntelligence <Boolean>] - [-EnableMailboxIntelligenceProtection <Boolean>] - [-EnableOrganizationDomainsProtection <Boolean>] - [-EnableSimilarDomainsSafetyTips <Boolean>] - [-EnableSimilarUsersSafetyTips <Boolean>] - [-EnableTargetedDomainsProtection <Boolean>] - [-EnableTargetedUserProtection <Boolean>] - [-EnableUnauthenticatedSender <Boolean>] - [-EnableUnusualCharactersSafetyTips <Boolean>] - [-ExcludedDomains <MultiValuedProperty>] - [-ExcludedSenders <MultiValuedProperty>] - [-ImpersonationProtectionState <ImpersonationProtectionState>] - [-MailboxIntelligenceProtectionAction <ImpersonationAction>] - [-MailboxIntelligenceProtectionActionRecipients <MultiValuedProperty>] - [-PhishThresholdLevel <Int32>] - [-PolicyTag <String>] - [-SimilarUsersSafetyTipsCustomText <String>] - [-TargetedDomainActionRecipients <MultiValuedProperty>] - [-TargetedDomainProtectionAction <ImpersonationAction>] - [-TargetedDomainsToProtect <MultiValuedProperty>] - [-TargetedUserActionRecipients <MultiValuedProperty>] - [-TargetedUserProtectionAction <ImpersonationAction>] - [-TargetedUsersToProtect <MultiValuedProperty>] - [-UnusualCharactersSafetyTipsCustomText <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Phishing messages contain fraudulent links or spoofed domains in an effort to get personal information from the recipients. - -New antiphish policies aren't valid and aren't applied until you add an antiphish rule to the policy by using the New-AntiPhishRule cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-AntiPhishPolicy -Name "Research Quarantine" -AdminDisplayName "Research department policy" -EnableOrganizationDomainsProtection $true -EnableTargetedDomainsProtection $true -TargetedDomainsToProtect fabrikam.com -TargetedDomainProtectionAction Quarantine -EnableTargetedUserProtection $true -TargetedUsersToProtect "Mai Fujito;mfujito@fabrikam.com" -TargetedUserProtectionAction Quarantine -EnableMailboxIntelligence $true -EnableMailboxIntelligenceProtection $true -MailboxIntelligenceProtectionAction Quarantine -EnableSimilarUsersSafetyTips $true -EnableSimilarDomainsSafetyTips $true -EnableUnusualCharactersSafetyTips $true -``` - -This example creates and enables an antiphish policy named Research Quarantine with the following settings: - -- The description is: Research department policy. -- Enables organization domains protection for all accepted domains, and targeted domains protection for fabrikam.com. -- Specifies Mai Fujito (mfujito@fabrikam.com) as a user to protect from impersonation. -- Enables mailbox intelligence. -- Enables mailbox intelligence protection, and specifies the quarantine action. -- Enables impersonation safety tips (impersonated domains, impersonated users, and unusual characters). - -## PARAMETERS - -### -Name -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 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuthenticationFailAction -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: - -- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -```yaml -Type: SpoofAuthenticationFailAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableAntispoofEnforcement -This setting is part of spoof protection. - -The EnableAntispoofEnforcement parameter specifies whether to enable or disable antispoofing protection for the policy. Valid values are: - -- $true: Antispoofing is enabled for the policy. This is the default and recommended value. You specify the spoofed senders to allow or block using the Set-PhishFilterPolicy cmdlet. - -- $false: Antispoofing is disabled for the policy. We only recommend this value if you have a domain that's protected by another email filtering service. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableMailboxIntelligence -This setting is part of impersonation protection. - -The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence (the first contact graph) in domain and user impersonation protection. Valid values are: - -- $true: Use mailbox intelligence in domain and user impersonation protection. - -- $false: Don't use mailbox intelligence in domain and user impersonation protection. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableMailboxIntelligenceProtection -This setting is part of impersonation protection. - -The EnableMailboxIntelligenceProtection specifies whether to enable or disable intelligence based impersonation protection. Valid values are: - -- $true: Enable intelligence based impersonation protection. - -- $false: Don't enable intelligence based impersonation protection. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableOrganizationDomainsProtection -This setting is part of impersonation protection. - -The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Office 365 organization. Valid values are: - -- $true: Domain impersonation protection is enabled for all registered domains in the Office 365 organization. - -- $false: Domain impersonation protection isn't enabled for all registered domains in the Office 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableSimilarDomainsSafetyTips -This setting is part of impersonation protection. - -The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are: - -- $true: Safety tips for similar domains are enabled. - -- $false: Safety tips for similar domains are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableSimilarUsersSafetyTips -This setting is part of impersonation protection. - -The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are: - -- $true: Safety tips for similar users are enabled. - -- $false: Safety tips for similar users are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTargetedDomainsProtection -This setting is part of impersonation protection. - -The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are: - -- $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter. - -- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTargetedUserProtection -This setting is part of impersonation protection. - -The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are: - -- $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter. - -- $false: The TargetedUsersToProtect parameter isn't used. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableUnauthenticatedSender -This setting is part of spoof protection. - -The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are: - -- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. The via tag (chris@contoso.com <u>via</u> michelle@fabrikam.com) is added if the domain in the From address (the message sender that's displayed in email clients) is different from the domain in the DKIM signature or the MAIL FROM address. - -- $false: Unauthenticated sender identification is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableUnusualCharactersSafetyTips -This setting is part of impersonation protection. - -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: - -- $true: Safety tips for unusual characters are enabled. - -- $false: Safety tips for unusual characters are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedDomains -This setting is part of impersonation protection. - -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedSenders -This setting is part of impersonation protection. - -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImpersonationProtectionState -This setting is part of impersonation protection. - -The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are: - -- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy. - -- Manual: This is the default value in custom policies that you create. - -- Off - -```yaml -Type: ImpersonationProtectionState -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxIntelligenceProtectionAction -This setting is part of impersonation protection. - -The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are: - -- NoAction: This is the default value. - -- BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -- Redirect: Redirect the message to the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter. - -```yaml -Type: ImpersonationAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxIntelligenceProtectionActionRecipients -This setting is part of impersonation protection. - -The MailboxIntelligenceProtectionActionRecipients parameter specifies the recipients to add to detected messages when the MailboxIntelligenceProtectionAction parameter is set to the value Redirect or BccMessage. - -A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhishThresholdLevel -This setting is part of advanced settings. - -The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are: - -- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. - -- 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence. - -- 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence. - -- 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyTag -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SimilarUsersSafetyTipsCustomText -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedDomainActionRecipients -This setting is part of impersonation protection. - -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. - -A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedDomainProtectionAction -This setting is part of impersonation protection. - -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: - -- NoAction: This is the default value. - -- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedDomainsToProtect -This setting is part of impersonation protection. - -The TargetedDomainsToProtect parameter specifies the domains that are included in domain impersonation protection when the EnableTargetedDomainsProtection parameter is set to $true. - -You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedUserActionRecipients -This setting is part of impersonation protection. - -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. - -A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. - - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedUserProtectionAction -This setting is part of impersonation protection. - -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: - -- NoAction: This is the default value. - -- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedUsersToProtect -This setting is part of impersonation protection. - -The TargetedUsersToProtect parameter specifies the users that are included in user impersonation protection when the EnableTargetedUserProtection parameter is set to $true. - -This parameter uses the syntax: "DisplayName;EmailAddress". - -- DisplayName specifies the display name of the user that could be a target of impersonation. This value can contain special characters. - -- EmailAddress specifies the internal or external email address that's associated with the display name. - -- You can specify multiple values by using the syntax: "DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN". The combination of DisplayName and EmailAddress needs to be unique for each value. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnusualCharactersSafetyTipsCustomText -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishRule.md deleted file mode 100644 index f12a0d8342..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishRule.md +++ /dev/null @@ -1,371 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/new-antiphishrule -applicable: Exchange Online -title: New-AntiPhishRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# New-AntiPhishRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-AntiPhishRule cmdlet to create antiphish rules in your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-AntiPhishRule [-Name] <String> -AntiPhishPolicy <String> - [-Comments <String>] - [-Confirm] - [-Enabled <Boolean>] - [-ExceptIfRecipientDomainIs <Word[]>] - [-ExceptIfSentTo <RecipientIdParameter[]>] - [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] - [-Priority <Int32>] [-RecipientDomainIs <Word[]>] - [-SentTo <RecipientIdParameter[]>] - [-SentToMemberOf <RecipientIdParameter[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to add the antiphish rule to an existing policy by using the AntiPhishPolicy parameter. You create antiphish policies by using the New-AntiPhishPolicy cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-AntiPhishRule -Name "Research Department" -AntiPhishPolicy "Research Quarantine" -SentToMemberOf "Research Department" -``` - -This example creates an antiphish rule named Research Department with the following settings: - -- The rule is associated with the antiphish policy named Research Quarantine. -- The rule applies to members of the group named Research Department. - -## PARAMETERS - -### -Name -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 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AntiPhishPolicy -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 - -- Distinguished name (DN) - -- GUID - -You can't specify the default antiphish policy. And, you can't specify an antiphish policy that's already associated with another antiphish rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comments -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the rule is enabled. Valid values are: - -- $true: The rule is enabled. This is the default value. - -- $false: The rule is disabled. - -In the properties of the rule, the value of this parameter is visible in the State property. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new rule (the 9th rule) are from 0 through 8. - -- The default value for a new rule (the 9th rule) is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeAttachmentPolicy.md deleted file mode 100644 index f181beba69..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeAttachmentPolicy.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/new-safeattachmentpolicy -applicable: Exchange Online, Exchange Online Protection -title: New-SafeAttachmentPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# New-SafeAttachmentPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-SafeAttachmentPolicy cmdlet to create Safe Attachments policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-SafeAttachmentPolicy [-Name] <String> [-Action <SafeAttachmentAction>] - [-ActionOnError <Boolean>] [-AdminDisplayName <String>] [-Confirm] [-Enable <Boolean>] - [-Redirect <Boolean>] [-RedirectAddress <SmtpAddress>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -New Safe Attachments policies aren't valid and aren't applied until you add a Safe Attachments rule to the policy by using the New-SafeAttachmentRule cmdlet. - -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-SafeAttachmentPolicy -Name "Marketing Block Attachments" -Enable $true -Redirect $true -RedirectAddress admin@contoso.com -``` - -This example creates a new Safe Attachments policy named Marketing Block Attachments with the following options: - -- The policy is enabled. - -- The action is Block. This is the default value of the Action parameter, so you don't need to specify it. - -- If Safe Attachments scanning isn't available or encounters errors, deliver the message as normal. The default value of the ActionOnError parameter is $false, so you don't need to specify it. - -- Redirect detected malware messages to admin@contoso.com. - -## PARAMETERS - -### -Name -The Name parameter specifies a unique name for the Safe Attachments 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: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Action -The Action parameter specifies the action for the Safe Attachments policy. Valid values are: - -- Allow: Deliver the email message, including the malware attachment. - -- Block: Block the email message that contains the malware attachment. This is the default value. - -- Replace: Deliver the email message, but remove the malware attachment and replace it with warning text. - -- DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [How Dynamic Delivery works](https://docs.microsoft.com/microsoft-365/security/office-365-security/dynamic-delivery-and-previewing#how-dynamic-delivery-works). - -The results of all actions are available in message trace. - -```yaml -Type: SafeAttachmentAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActionOnError -The ActionOnError parameter specifies the error handling option for Safe Attachments scanning (what to do if scanning times out or an error occurs). Valid values are: - -- $true: The action specified by the Action parameter is applied to messages even when the attachments aren't successfully scanned. - -- $false: The action specified by the Action parameter isn't applied to messages when the attachments aren't successfully scanned. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -The Enable parameter specifies whether policy is enabled. Valid values are: - -- $true: The rule or policy is enabled. - -- $false: The rule or policy is disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Redirect -The Redirect parameter specifies whether to send detected malware attachments to another email address. Valid values are: - -- $true: Malware attachments are sent to the email address specified by the RedirectAddress parameter. - -- $false: Malware attachments aren't sent to another email address. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RedirectAddress -The RedirectAddress parameter specifies the email address where detected malware attachments are sent when the Redirect parameter is set to the value $true. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeAttachmentRule.md deleted file mode 100644 index 6cf3ae3dbb..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeAttachmentRule.md +++ /dev/null @@ -1,381 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/new-safeattachmentrule -applicable: Exchange Online, Exchange Online Protection -title: New-SafeAttachmentRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# New-SafeAttachmentRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-SafeAttachmentRule cmdlet to create Safe Attachments rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-SafeAttachmentRule [-Name] <String> -SafeAttachmentPolicy <SafeAttachmentPolicyIdParameter> - [-Comments <String>] - [-Confirm] - [-Enabled <Boolean>] - [-ExceptIfRecipientDomainIs <Word[]>] - [-ExceptIfSentTo <RecipientIdParameter[]>] - [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] - [-Priority <Int32>] - [-RecipientDomainIs <Word[]>] - [-SentTo <RecipientIdParameter[]>] - [-SentToMemberOf <RecipientIdParameter[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to specify at least one condition for the rule. - -You need to add the Safe Attachments rule to an existing policy by using the SafeAttachmentPolicy parameter. You create Safe Attachments policies by using the New-SafeAttachmentPolicy cmdlet. - -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-SafeAttachmentRule -Name "Research Department Attachment Rule" -SafeAttachmentPolicy "Research Block Attachments" -SentToMemberOf "Research Department" -ExceptIfSentToMemberOf "Research Department Managers" -``` - -This example creates a new Safe Attachments rule named Research Department Attachment Rule with the following conditions: - -- The rule is associated with the Safe Attachments policy named Research Block Attachments. - -- The rule applies to members of the group named Research Department. - -- The rule doesn't apply to members of the group named Research Department Managers. - -## PARAMETERS - -### -Name -The Name parameter specifies a unique name for the Safe Attachments 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: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SafeAttachmentPolicy -The SafeAttachmentPolicy parameter specifies the Safe Attachments policy that's associated with this Safe Attachments rule. The rule defines the conditions, and the policy defines the actions. - -You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -You can't specify a Safe Attachments policy that's already associated with another Safe Attachments rule. - -```yaml -Type: SafeAttachmentPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comments -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the rule is enabled. Valid values are: - -- $true: The rule is enabled. Ths is the default value - -- $false: The rule is disabled. - -The default value is $true. - -In the properties of the rule, the value of this parameter is visible in the State property. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new rule (the 9th rule) are from 0 through 8. - -- The default value for a new rule (the 9th rule) is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeLinksPolicy.md deleted file mode 100644 index 6965abe8a7..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeLinksPolicy.md +++ /dev/null @@ -1,335 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/new-safelinkspolicy -applicable: Exchange Online, Exchange Online Protection -title: New-SafeLinksPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# New-SafeLinksPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-SafeLinksPolicy cmdlet to create Safe Links policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-SafeLinksPolicy [-Name] <String> [-AdminDisplayName <String>] [-AllowClickThrough <Boolean>] - [-Confirm] [-DoNotAllowClickThrough <Boolean>] [-DoNotRewriteUrls <MultiValuedProperty>] - [-DoNotTrackUserClicks <Boolean>] [-Enabled <Boolean>] - [-EnableForInternalSenders <Boolean>] [-ExcludedUrls <String[]>] [-IsEnabled <Boolean>] - [-ScanUrls <Boolean>] [-TrackClicks <Boolean>] [-WhatIf] [-WhiteListedUrls <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-SafeLinksPolicy -Name "Marketing Block URL" -IsEnabled $true -TrackClicks $true -``` - -This example creates a new Safe Links policy named Marketing Block URL with the following options: - -- The policy is enabled. - -- Users aren't allowed to click through to the original URL. This is the default value of the DoNotAllowClickThrough parameter, so you don't need to specify it. - -- User clicks on URLs are tracked in URL trace. - -## PARAMETERS - -### -Name -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, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowClickThrough -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotAllowClickThrough -The DoNotAllowClickThrough parameter specifies whether to allow users to click through to the original URL. Valid values are: - -- $true: The user isn't allowed to click through to the original URL. This is the default value. - -- $false: The user is allowed to click through to the original URL. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotRewriteUrls -The DoNotRewriteUrls parameter specifies a URL that's skipped by Safe Links scanning. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotTrackUserClicks -The DoNotTrackUserClicks parameter specifies whether to track user clicks related to links in email messages. Valid values are: - -- $true: User clicks aren't tracked. This is the default value. - -- $false: User clicks are tracked. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The rule or policy is enabled. - -- $false: The rule or policy is disabled. This is the default value - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableForInternalSenders -The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to internal senders. Valid values are: - -- $true: The policy is applied to internal and external senders. - -- $false: The policy is applied only to external senders. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedUrls -The ExcludedUrls parameter specifies a URL that's skipped by Safe Links scanning. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScanUrls -The ScanUrls parameter specifies whether to enable or disable the scanning of links in email messages. Valid values are: - -- $true: Scanning links in email messages is enabled. - -- $false: Scanning links in email messages is disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrackClicks -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhiteListedUrls -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeLinksRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeLinksRule.md deleted file mode 100644 index 7ac0737b46..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/New-SafeLinksRule.md +++ /dev/null @@ -1,377 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/new-safelinksrule -applicable: Exchange Online, Exchange Online Protection -title: New-SafeLinksRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# New-SafeLinksRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-SafeLinksRule cmdlet to create Safe Links rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-SafeLinksRule [-Name] <String> -SafeLinksPolicy <SafeLinksPolicyIdParameter> - [-Comments <String>] - [-Confirm] - [-Enabled <Boolean>] - [-ExceptIfRecipientDomainIs <Word[]>] - [-ExceptIfSentTo <RecipientIdParameter[]>] - [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] - [-Priority <Int32>] - [-RecipientDomainIs <Word[]>] - [-SentTo <RecipientIdParameter[]>] - [-SentToMemberOf <RecipientIdParameter[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to specify at least one condition for the rule. - -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-SafeLinksRule -Name "Research Department URL Rule" -SafeLinksPolicy "Research Block URL" -SentToMemberOf "Research Department" -ExceptIfSentToMemberOf "Research Department Managers" -``` - -This example creates a new Safe Links rule named Research Department URL Rule with the following conditions: - -- The rule is associated with the Safe Links policy named Research Block URL. - -- The rule applies to members of the group named Research Department. - -- The rule doesn't apply to members of the group named Research Department Managers. - -## PARAMETERS - -### -Name -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, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SafeLinksPolicy -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: - -- Name - -- Distinguished name (DN) - -- GUID - -You can't specify a Safe Links policy that's already associated with another Safe Links rule. - -```yaml -Type: SafeLinksPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comments -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the rule is enabled. Valid values are: - -- $true: The rule is enabled. This is the default value. - -- $false: The rule is disabled. - -In the properties of the rule, the value of this parameter is visible in the State property. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new rule (the 9th rule) are from 0 through 8. - -- The default value for a new rule (the 9th rule) is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishPolicy.md deleted file mode 100644 index e4d66a4cfe..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishPolicy.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/remove-antiphishpolicy -applicable: Exchange Online -title: Remove-AntiPhishPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Remove-AntiPhishPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-AntiPhishPolicy cmdlet to remove antiphish policies from your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-AntiPhishPolicy [-Identity] <AntiPhishPolicyIdParameter> [-Confirm] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-AntiPhishPolicy -Identity "Quarantine Policy" -``` - -This example removes the antiphish policy named Quarantine Policy. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: AntiPhishPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishRule.md deleted file mode 100644 index 583d729e2b..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishRule.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/remove-antiphishrule -applicable: Exchange Online -title: Remove-AntiPhishRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Remove-AntiPhishRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-AntiPhishRule cmdlet to remove antiphish rules from your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-AntiPhishRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-AntiPhishRule -Identity "Research Department Phishing Rule" -``` - -This examples removes the antiphish rule named Research Department Phishing Rule. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeAttachmentPolicy.md deleted file mode 100644 index f5f0f27a24..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeAttachmentPolicy.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/remove-safeattachmentpolicy -applicable: Exchange Online, Exchange Online Protection -title: Remove-SafeAttachmentPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Remove-SafeAttachmentPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-SafeAttachmentPolicy cmdlet to remove Safe Attachments policies from your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-SafeAttachmentPolicy [-Identity] <SafeAttachmentPolicyIdParameter> [-Confirm] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You can't remove the default Safe Attachments policy (the policy where the IsDefault property is True). - -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-SafeAttachmentPolicy -Identity "Block Attachments Policy" -``` - -This example removes the Safe Attachments policy named Block Attachments Policy. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Safe Attachments policy that you want to remove. - -You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: SafeAttachmentPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeAttachmentRule.md deleted file mode 100644 index 2126c3b6fb..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeAttachmentRule.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/remove-safeattachmentrule -applicable: Exchange Online, Exchange Online Protection -title: Remove-SafeAttachmentRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Remove-SafeAttachmentRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-SafeAttachmentRule cmdlet to remove Safe Attachments rules from your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-SafeAttachmentRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-SafeAttachmentRule -Identity "Research Department Attachment Rule" -``` - -This examples removes the Safe Attachments rule named Research Department Attachment Rule. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Safe Attachments rule that you want to remove. - -You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeLinksPolicy.md deleted file mode 100644 index 0c2325f108..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeLinksPolicy.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/remove-safelinkspolicy -applicable: Exchange Online, Exchange Online Protection -title: Remove-SafeLinksPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Remove-SafeLinksPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-SafeLinksPolicy cmdlet to remove Safe Links policies from your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-SafeLinksPolicy [-Identity] <SafeLinksPolicyIdParameter> [-Confirm] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You can't remove the default Safe Links policy (the policy where the IsDefault property is True). - -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-SafeLinksPolicy -Identity "Engineering Department URL Policy" -``` - -This example remove the Safe Links policy named Engineering Department URL Policy. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: SafeLinksPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeLinksRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeLinksRule.md deleted file mode 100644 index b5784f5f11..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Remove-SafeLinksRule.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/remove-safelinksrule -applicable: Exchange Online, Exchange Online Protection -title: Remove-SafeLinksRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Remove-SafeLinksRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-SafeLinksRule cmdlet to remove Safe Links rules from your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-SafeLinksRule [-Identity] <RuleIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-SafeLinksRule -Identity "Research Department URL Rule" -``` - -This examples removes the Safe Links rule named Research Department URL Rule. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md deleted file mode 100644 index 1ee588d660..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md +++ /dev/null @@ -1,758 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-antiphishpolicy -applicable: Exchange Online -title: Set-AntiPhishPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-AntiPhishPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-AntiPhishPolicy cmdlet to modify antiphish policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AntiPhishPolicy -Identity <AntiPhishPolicyIdParameter> - [-AdminDisplayName <String>] - [-AuthenticationFailAction <SpoofAuthenticationFailAction>] - [-Confirm] - [-EnableAntispoofEnforcement <Boolean>] - [-Enabled <Boolean>] - [-EnableMailboxIntelligence <Boolean>] - [-EnableMailboxIntelligenceProtection <Boolean>] - [-EnableOrganizationDomainsProtection <Boolean>] - [-EnableSimilarDomainsSafetyTips <Boolean>] - [-EnableSimilarUsersSafetyTips <Boolean>] - [-EnableTargetedDomainsProtection <Boolean>] - [-EnableTargetedUserProtection <Boolean>] - [-EnableUnauthenticatedSender <Boolean>] - [-EnableUnusualCharactersSafetyTips <Boolean>] - [-ExcludedDomains <MultiValuedProperty>] - [-ExcludedSenders <MultiValuedProperty>] - [-ImpersonationProtectionState <ImpersonationProtectionState>] - [-MailboxIntelligenceProtectionAction <ImpersonationAction>] - [-MailboxIntelligenceProtectionActionRecipients <MultiValuedProperty>] - [-MakeDefault] - [-PhishThresholdLevel <Int32>] - [-PolicyTag <String>] - [-TargetedDomainActionRecipients <MultiValuedProperty>] - [-TargetedDomainProtectionAction <ImpersonationAction>] - [-TargetedDomainsToProtect <MultiValuedProperty>] - [-TargetedUserActionRecipients <MultiValuedProperty>] - [-TargetedUserProtectionAction <ImpersonationAction>] - [-TargetedUsersToProtect <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-AntiPhishPolicy -Identity "Office365 AntiPhish Default" -AuthenticationFailAction Quarantine -``` - -This example modifies the default anti-phish policy named Office365 AntiPhish Default to quarantine spoofed messages from senders who aren't allowed to spoof. - -### Example 2 -```powershell -Set-AntiPhishPolicy -Identity "Office365 AntiPhish Default" -EnableOrganizationDomainsProtection $true -EnableTargetedDomainsProtection $true -TargetedDomainsToProtect fabrikam.com -TargetedDomainProtectionAction Quarantine -EnableTargetedUserProtection $true -TargetedUsersToProtect "Mai Fujito;mfujito@fabrikam.com" -TargetedUserProtectionAction Quarantine -EnableMailboxIntelligence $true -EnableMailboxIntelligenceProtection $true -MailboxIntelligenceProtectionAction Quarantine -EnableSimilarUsersSafetyTips $true -EnableSimilarDomainsSafetyTips $true -EnableUnusualCharactersSafetyTips $true -``` - -In Office 365 ATP, this example modifies the default anti-phish policy named Office365 AntiPhish Default with the following settings: - -- Enables organization domains protection for all accepted domains, and targeted domains protection for fabrikam.com. -- Specifies Mai Fujito (mfujito@fabrikam.com) as a user to protect from impersonation. -- Enables mailbox intelligence. -- Enables mailbox intelligence protection, and specifies the quarantine action. -- Enables impersonation safety tips (impersonated domains, impersonated users, and unusual characters). - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: AntiPhishPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -This setting is only available in Office 365 Advanced Threat 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuthenticationFailAction -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: - -- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -```yaml -Type: SpoofAuthenticationFailAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableAntispoofEnforcement -This setting is part of spoof protection. - -The EnableAntispoofEnforcement parameter specifies whether to enable or disable antispoofing protection for the policy. Valid values are: - -- $true: Antispoofing is enabled for the policy. This is the default and recommended value. You specify the spoofed senders to allow or block using the Set-PhishFilterPolicy cmdlet. - -- $false: Antispoofing is disabled for the policy. We only recommend this value if you have a domain that's protected by another email filtering service. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -This setting is only available in Office 365 Advanced Threat Protection. - -The Enabled parameter specifies whether the antiphish policy is enabled or disabled. Valid values are: - -$true: The policy is enabled. - -$false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -EnableMailboxIntelligence -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence (the first contact graph) in domain and user impersonation protection. Valid values are: - -- $true: Use mailbox intelligence in domain and user impersonation protection. - -- $false: Don't use mailbox intelligence in domain and user impersonation protection. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableMailboxIntelligenceProtection -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The EnableMailboxIntelligenceProtection specifies whether to enable or disable intelligence based impersonation protection. Valid values are: - -- $true: Enable intelligence based impersonation protection. - -- $false: Don't enable intelligence based impersonation protection. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableOrganizationDomainsProtection -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Office 365 organization. Valid values are: - -- $true: Domain impersonation protection is enabled for all registered domains in the Office 365 organization. - -- $false: Domain impersonation protection isn't enabled for all registered domains in the Office 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableSimilarDomainsSafetyTips -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are: - -- $true: Safety tips for similar domains are enabled. - -- $false: Safety tips for similar domains are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableSimilarUsersSafetyTips -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are: - -- $true: Safety tips for similar users are enabled. - -- $false: Safety tips for similar users are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTargetedDomainsProtection -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are: - -- $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter. - -- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTargetedUserProtection -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are: - -- $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter. - -- $false: The TargetedUsersToProtect parameter isn't used. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableUnauthenticatedSender -This setting is part of spoof protection. - -The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are: - -- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. The via tag (chris@contoso.com <u>via</u> michelle@fabrikam.com) is added if the domain in the From address (the message sender that's displayed in email clients) is different from the domain in the DKIM signature or the MAIL FROM address. - -- $false: Unauthenticated sender identification is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableUnusualCharactersSafetyTips -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -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: - -- $true: Safety tips for unusual characters are enabled. - -- $false: Safety tips for unusual characters are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedDomains -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedSenders -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImpersonationProtectionState -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are: - -- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy. - -- Manual: This is the default value in custom policies that you create. - -- Off - -```yaml -Type: ImpersonationProtectionState -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxIntelligenceProtectionAction -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are: - -- NoAction: This is the default value. - -- BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -- Redirect: Redirect the message to the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter. - -```yaml -Type: ImpersonationAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxIntelligenceProtectionActionRecipients -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The MailboxIntelligenceProtectionActionRecipients parameter specifies the recipients to add to detected messages when the MailboxIntelligenceProtectionAction parameter is set to the value Redirect or BccMessage. - -A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MakeDefault -This setting is only available in Office 365 Advanced Threat Protection. - -The MakeDefault switch makes the specified antiphish policy the default antiphish policy. You don't have 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). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhishThresholdLevel -This setting is only available in Office 365 Advanced Threat Protection and is part of advanced settings. - -The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are: - -- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. - -- 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence. - -- 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence. - -- 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyTag -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedDomainActionRecipients -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -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. - -A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedDomainProtectionAction -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -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: - -- NoAction: This is the default value. - -- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedDomainsToProtect -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The TargetedDomainsToProtect parameter specifies the domains that are included in domain impersonation protection when the EnableTargetedDomainsProtection parameter is set to $true. - -You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedUserActionRecipients -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -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. - -A valid value for this parameter is an email address. You can specify multiple email addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedUserProtectionAction -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -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: - -- NoAction: This is the default value. - -- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are only available to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. - -- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetedUsersToProtect -This setting is only available in Office 365 Advanced Threat Protection and is part of impersonation protection. - -The TargetedUsersToProtect parameter specifies the users that are included in user impersonation protection when the EnableTargetedUserProtection parameter is set to $true. - -This parameter uses the syntax: "DisplayName;EmailAddress". - -- DisplayName specifies the display name of the user that could be a target of impersonation. This value can contain special characters. - -- EmailAddress specifies the internal or external email address that's associated with the display name. - -- You can specify multiple values by using the syntax: "DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN". The combination of DisplayName and EmailAddress needs to be unique for each value. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishRule.md deleted file mode 100644 index ec3003c085..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishRule.md +++ /dev/null @@ -1,362 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-antiphishrule -Applicable: Exchange Online -title: Set-AntiPhishRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-AntiPhishRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-AntiPhishRule cmdlet to modify antiphish rules in your Office 365 Advanced Threat Protection (ATP) organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AntiPhishRule [-Identity] <RuleIdParameter> - [-AntiPhishPolicy <AntiPhishPolicyIdParameter>] - [-Comments <String>] - [-Confirm] - [-ExceptIfRecipientDomainIs <Word[]>] - [-ExceptIfSentTo <RecipientIdParameter[]>] - [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] - [-Name <String>] - [-Priority <Int32>] - [-RecipientDomainIs <Word[]>] - [-SentTo <RecipientIdParameter[]>] - [-SentToMemberOf <RecipientIdParameter[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-AntiPhishRule -Identity "Engineering Department Phishing Rule" -ExceptIfRecipientDomainIs fabrikam.com -``` - -This example modifies the existing antiphish rule named Engineering Department Phishing Rule to exclude messages sent to the fabrikam.com domain. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AntiPhishPolicy -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: AntiPhishPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comments -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new rule (the 9th rule) are from 0 through 8. - -- The default value for a new rule (the 9th rule) is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AtpPolicyForO365.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AtpPolicyForO365.md deleted file mode 100644 index 758df0482f..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-AtpPolicyForO365.md +++ /dev/null @@ -1,268 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-atppolicyforo365 -applicable: Exchange Online, Exchange Online Protection -title: Set-AtpPolicyForO365 -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-AtpPolicyForO365 - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-AtpPolicyForO365 cmdlet to modify the Advanced Threat Protection (ATP) policy in Office 365. The ATP policy enables the following protections: - -- Safe Links for Office 365 ProPlus desktop clients and Office Mobile apps. - -- Safe Documents: Before a user is allowed to trust a file open in Office 365 ProPlus, the file will be verified by Microsoft Defender ATP. - -- ATP to protect files in SharePoint Online, OneDrive for Business and Microsoft Teams. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AtpPolicyForO365 [[-Identity] <AtpPolicyForO365IdParameter>] - [-AllowClickThrough <Boolean>] - [-AllowSafeDocsOpen <Boolean>] - [-BlockUrls <MultiValuedProperty>] - [-Confirm] - [-EnableATPForSPOTeamsODB <Boolean>] - [-EnableSafeDocs <Boolean>] - [-EnableSafeLinksForClients <Boolean>] - [-TrackClicks <Boolean>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. For more information, see [Office 365 ATP Safe Links](https://docs.microsoft.com/microsoft-365/security/office-365-security/atp-safe-links). - -ATP can also protect files in SharePoint Online, OneDrive for Business and Microsoft Teams by preventing users from opening and downloading files that are identified as malicious. For more information, see [Office 365 ATP for SharePoint, OneDrive, and Microsoft Teams](https://go.microsoft.com/fwlink/p/?linkid=857638). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-AtpPolicyForO365 -EnableSafeLinksForClients $true -EnableATPForSPOTeamsODB $true -``` - -This example enables Safe Links for Office 365 ProPlus clients and ATP for SharePoint Online, OneDrive for Business and Microsoft Teams. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the ATP policy that you want to modify. There's only one policy named Default. - -```yaml -Type: AtpPolicyForO365IdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AllowClickThrough -The AllowClickThrough parameter specifies whether to allow users to click through to the original blocked URL in Office 365 ProPlus. Valid values are: - -- $true: Users are allowed to click through to the original URL. This is the default value. - -- $false: Users aren't allowed to click through to the original URL. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowSafeDocsOpen -The AllowSafeDocsOpen parameter specifies whether users can click through and bypass the Protected View container even when Safe Documents in Microsoft Defender Advanced Threat Protection (MDATP) 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. - -- $false: Users aren't allowed to exit Protected View in case of a malicious detection. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockUrls -The BlockUrls parameter specifies the URLs that are always blocked by Safe Links scanning. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableATPForSPOTeamsODB -The EnableATPForSPOTeamsODB parameter specifies whether ATP is enabled for SharePoint Online, OneDrive for Business and Microsoft Teams. Valid values are: - -- $true: ATP is enabled for SharePoint Online, OneDrive for Business and Microsoft Teams. - -- $false: ATP is disabled for SharePoint Online, OneDrive for Business and Microsoft Teams. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableSafeDocs -The EnableSafeDocs parameter specifies whether to enable the Safe Documents feature in the organization. Valid values are: - -- $true: Safe Documents is enabled and will upload user files to Microsoft Defender Advanced Threat Protection (MDATP) for scanning and verification. - -- $false: Safe Documents is disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableSafeLinksForClients -The EnableSafeLinksForClients parameter specifies whether Safe Links is enabled for Office 365 apps on desktop clients and on the web. Valid values are: - -- $true: Safe Links are enabled for Office 365 apps. This is the default value. - -- $false: Safe Links are disabled for Office 365 apps. - -This parameter is being replaced by EnableSafeLinksForO365Clients with the same functionality. Use which ever one is currently available in your tenant. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrackClicks -The TrackClicks parameter specifies whether to track user clicks related to blocked URLs. Valid values are: - -- $true: User clicks are tracked. This is the default value. - -- $false: User clicks aren't tracked. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md deleted file mode 100644 index 999a615b71..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-phishfilterpolicy -applicable: Exchange Online, Exchange Online Protection -title: Set-PhishFilterPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-PhishFilterPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-PhishFilterPolicy cmdlet to configure the spoof intelligence policy in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-PhishFilterPolicy [-Identity] <HostedConnectionFilterPolicyIdParameter> -SpoofAllowBlockList <String> - [-Action <SetPhishFilterPolicyAction>] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -For more information about spoof intelligence, see [Learn more about spoof intelligence](https://go.microsoft.com/fwlink/p/?linkid=869584). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-PhishFilterPolicy -Detailed | Export-CSV "C:\My Documents\Spoofed Senders.csv" -$UpdateSpoofedSenders = Get-Content -Raw "C:\My Documents\Spoofed Senders.csv" -Set-PhishFilterPolicy -Identity Default -SpoofAllowBlockList $UpdateSpoofedSenders -``` - -This example configures the spoof intelligence policy to block or allow all spoofed email messages from a source email server. - -- Step 1: Write the output of the Get-PhishFilterPolicy cmdlet to a CSV file. -- Step 2: Add or modify the SpoofedUser and AllowedToSpoof values in the CSV file, save the file, and then read the file and store it as a variable named $UpdateSpoofedSenders. -- Step 3: Use the $UpdateSpoofedSenders variable to configure the spoof intelligence policy. - -### Example 2 -```powershell -Get-PhishFilterPolicy -Detailed | Export-CSV "C:\My Documents\Spoofed Senders.csv" -$UpdateSpoofedSenders = Get-Content -Raw "C:\My Documents\Spoofed Senders.csv" -Set-PhishFilterPolicy -Identity Default -SpoofAllowBlockList $UpdateSpoofedSenders -``` - -This example configures the spoof intelligence policy to selectively block or allow some spoofed email messages from a source email server. - -- Step 1: Write the output of the Get-PhishFilterPolicy cmdlet to a CSV file. -- Step 2: Add or modify the Sender, SpoofedUser, and AllowedToSpoof values in the CSV file, save the file, and then read the CSV file and store it as a variable named $UpdateSpoofedSenders. -- Step 3: Use the $UpdateSpoofedSenders variable to configure the spoof intelligence policy. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the spoof intelligence policy that you want to modify. The only valid value is Default. - -```yaml -Type: HostedConnectionFilterPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Action -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SetPhishFilterPolicyAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpoofAllowBlockList -The SpoofAllowBlockList parameter specifies the CSV file that you want to use to configure the spoof intelligence policy. - -A valid value for this parameter reads the CSV file and stores it as a variable. For example, run the command `$SpoofedUsers = Get-Content -Raw "<PathAndFileName>.csv"`, and then use the value `$SpoofedUsers` for this parameter. - -There are two basic options for the CSV file: - -- **Block or allow all spoofed mail from the source**: You want to block or allow any and all spoofed messages from the specified message source, regardless of the spoofed email address. You can get the CSV file by running the command `Get-PhishFilterPolicy -Detailed | Export-CSV "<PathAndFileName>.csv"`. The important header fields (column headers) are: - - **Sender**: The domain of the source email server from reverse DNS lookup (PTR records), or the IP address if there aren't any PTR records. - - **AllowedToSpoof**: Indicates whether the message source is allowed to send spoofed messages. Valid values are Yes or No. - -- **Block or allow some spoofed mail from the source**: You want to block or allow some spoofed messages from the specified message source, but not others. You can get the CSV file by running the command `Get-PhishFilterPolicy -Detailed | Export-CSV "<PathAndFileName>.csv"`. The important header fields (column headers) are: - - **Sender** - - **SpoofedUser**: The spoofed email address in your organization that the messages appear to be coming from. - - **AllowedToSpoof** - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeAttachmentPolicy.md deleted file mode 100644 index 88d07a721c..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeAttachmentPolicy.md +++ /dev/null @@ -1,241 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-safeattachmentpolicy -applicable: Exchange Online, Exchange Online Protection -title: Set-SafeAttachmentPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-SafeAttachmentPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-SafeAttachmentPolicy cmdlet to modify Safe Attachments policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-SafeAttachmentPolicy [-Identity] <SafeAttachmentPolicyIdParameter> - [-Action <SafeAttachmentAction>] [-ActionOnError <Boolean>] - [-AdminDisplayName <String>] [-Confirm] [-Enable <Boolean>] [-Redirect <Boolean>] - [-RedirectAddress <SmtpAddress>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-SafeAttachmentsPolicy -Identity "Engineering Block Attachments" -Redirect $true -RedirectAddress admin@contoso.com -``` - -This example modifies the existing Safe Attachments policy named Engineering Block Attachments to redirect detected malware attachments to admin@contoso.com. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Safe Attachments policy that you want to modify. - -You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: SafeAttachmentPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Action -The Action parameter specifies the action for the Safe Attachments policy. Valid values are: - -- Allow: Deliver the email message, including the malware attachment. - -- Block: Block the email message that contains the malware attachment. This is the default value. - -- Replace: Deliver the email message, but remove the malware attachment and replace it with warning text. - -- DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [How Dynamic Delivery works](https://docs.microsoft.com/microsoft-365/security/office-365-security/dynamic-delivery-and-previewing#how-dynamic-delivery-works). - -The results of all actions are available in message trace. - -```yaml -Type: SafeAttachmentAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActionOnError -The ActionOnError parameter specifies the error handling option for Safe Attachments scanning (what to do if attachment scanning times out or an error occurs). Valid values are: - -- $true: The action specified by the Action parameter is applied to messages even when the attachments aren't successfully scanned. - -- $false: The action specified by the Action parameter isn't applied to messages when the attachments aren't successfully scanned. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -The Enable parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. - -- $false: The policy is disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Redirect -The Redirect parameter specifies whether to send detected malware attachments to another email address. Valid values are: - -- $true: Malware attachments are sent to the email address specified by the RedirectAddress parameter. - -- $false: Malware attachments aren't sent to another email address. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RedirectAddress -The RedirectAddress parameter specifies the email address where detected malware attachments are sent when the Redirect parameter is set to the value $true. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeAttachmentRule.md deleted file mode 100644 index 62c7a8d305..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeAttachmentRule.md +++ /dev/null @@ -1,371 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-safeattachmentrule -applicable: Exchange Online, Exchange Online Protection -title: Set-SafeAttachmentRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-SafeAttachmentRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-SafeAttachmentRule cmdlet to modify Safe Attachments rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-SafeAttachmentRule [-Identity] <RuleIdParameter> - [-Comments <String>] - [-Confirm] - [-ExceptIfRecipientDomainIs <Word[]>] - [-ExceptIfSentTo <RecipientIdParameter[]>] - [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] - [-Name <String>] [-Priority <Int32>] - [-RecipientDomainIs <Word[]>] - [-SafeAttachmentPolicy <SafeAttachmentPolicyIdParameter>] - [-SentTo <RecipientIdParameter[]>] - [-SentToMemberOf <RecipientIdParameter[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Attachments is a feature in Advanced Threat Protection that opens email attachments in a special hypervisor environment to detect malicious activity. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-SafeAttachmentRule -Identity "Engineering Department Attachment Rule" -ExceptIfRecipientDomainIs fabrikam.com -``` - -This example modifies the existing Safe Attachments Rule named Engineering Department Attachment Rule to exclude messages sent to the fabrikam.com domain. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Safe Attachments rule that you want to modify. - -You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Comments -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies a unique name for the Safe Attachments 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new rule (the 9th rule) are from 0 through 8. - -- The default value for a new rule (the 9th rule) is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SafeAttachmentPolicy -The SafeAttachmentPolicy parameter specifies the Safe Attachments policy that's associated with this Safe Attachments rule. The rule defines the conditions, and the policy defines the actions. - -You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -You can't specify a Safe Attachments policy that's already associated with another Safe Attachments rule. - -```yaml -Type: SafeAttachmentPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeLinksPolicy.md deleted file mode 100644 index 78d1922db0..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeLinksPolicy.md +++ /dev/null @@ -1,341 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-safelinkspolicy -applicable: Exchange Online, Exchange Online Protection -title: Set-SafeLinksPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-SafeLinksPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-SafeLinksPolicy cmdlet to modify Safe Links policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-SafeLinksPolicy [-Identity] <SafeLinksPolicyIdParameter> [-AdminDisplayName <String>] - [-AllowClickThrough <Boolean>] [-Confirm] [-DoNotAllowClickThrough <Boolean>] - [-DoNotRewriteUrls <MultiValuedProperty>] [-DoNotTrackUserClicks <Boolean>] [-Enabled <Boolean>] - [-EnableForInternalSenders <Boolean>] [-ExcludedUrls <String[]>] [-IsEnabled <Boolean>] - [-ScanUrls <Boolean>] [-TrackClicks <Boolean>] [-WhatIf] [-WhiteListedUrls <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-SafeLinksPolicy -Identity "Engineering Block URL" -TrackClicks $true -``` - -This example modifies the existing Safe Links policy named Engineering Block URL to track user clicks on URLs in URL trace. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: SafeLinksPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowClickThrough -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotAllowClickThrough -The DoNotAllowClickThrough parameter specifies whether to allow users to click through to the original URL. Valid values are: - -- $true: The user isn't allowed to click through to the original URL. This is the default value. - -- $false: The user is allowed to click through to the original URL. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotRewriteUrls -The DoNotRewriteUrls parameter specifies a URL that's skipped by Safe Links scanning. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotTrackUserClicks -The DoNotTrackUserClicks parameter specifies whether to track user clicks related to links in email messages. Valid values are: - -- $true: User clicks aren't tracked. This is the default value. - -- $false: User clicks are tracked. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableForInternalSenders -The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to internal senders. Valid values are: - -- $true: The policy is applied to internal and external senders. - -- $false: The policy is applied only to external senders. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedUrls -The ExcludedUrls parameter has been deprecated. Use the DoNotRewriteUrls parameter instead. If you have any scripts that use the ExcludedUrls parameter, update them to use the DoNotRewriteUrls parameter. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsEnabled -This parameter specifies whether the rule or policy is enabled. Valid values are: - -- $true: The rule or policy is enabled. - -- $false: The rule or policy is disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScanUrls -The ScanUrls parameter specifies whether to enable or disable the scanning of links in email messages. Valid values are: - -- $true: Scanning links in email messages is enabled. - -- $false: Scanning links in email messages is disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrackClicks -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhiteListedUrls -The WhiteListedUrls parameter has been deprecated. Use the DoNotRewriteUrls parameter instead. If you have any scripts that use the WhiteListedUrls parameter, update them to use the DoNotRewriteUrls parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeLinksRule.md b/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeLinksRule.md deleted file mode 100644 index 896d12b2af..0000000000 --- a/exchange/exchange-ps/exchange/advanced-threat-protection/Set-SafeLinksRule.md +++ /dev/null @@ -1,372 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/advanced-threat-protection/set-safelinksrule -applicable: Exchange Online, Exchange Online Protection -title: Set-SafeLinksRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-SafeLinksRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-SafeLinksRule cmdlet to create Safe Links rules in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-SafeLinksRule [-Identity] <RuleIdParameter> - [-Comments <String>] - [-Confirm] - [-ExceptIfRecipientDomainIs <Word[]>] - [-ExceptIfSentTo <RecipientIdParameter[]>] - [-ExceptIfSentToMemberOf <RecipientIdParameter[]>] - [-Name <String>] - [-Priority <Int32>] - [-RecipientDomainIs <Word[]>] - [-SafeLinksPolicy <SafeLinksPolicyIdParameter>] - [-SentTo <RecipientIdParameter[]>] - [-SentToMemberOf <RecipientIdParameter[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-SafeLinksRule -Identity "Engineering Department URL Rule" -ExceptIfRecipientDomainIs fabrikam.com -``` - -This example modifies the existing Safe Links Rule named Engineering Department URL Rule to exclude messages sent to the fabrikam.com domain. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Comments -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no exception is made for messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new rule (the 9th rule) are from 0 through 8. - -- The default value for a new rule (the 9th rule) is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition that looks for recipients 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SafeLinksPolicy -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: - -- Name - -- Distinguished name (DN) - -- GUID - -You can't specify a Safe Attachments policy that's already associated with another Safe Attachments rule. - -```yaml -Type: SafeLinksPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentToMemberOf -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you remove the group after you create the rule, no action is taken on messages that are sent to members of the group. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Delete-QuarantineMessage.md b/exchange/exchange-ps/exchange/antispam-antimalware/Delete-QuarantineMessage.md deleted file mode 100644 index 11027b6af1..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Delete-QuarantineMessage.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/delete-quarantinemessage -applicable: Exchange Online, Exchange Online Protection -title: Delete-QuarantineMessage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Delete-QuarantineMessage - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Delete-QuarantineMessage cmdlet to delete quarantine messages from your cloud-based organization - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identities -``` -Delete-QuarantineMessage -Identities <QuarantineMessageIdentity[]> [-Identity <QuarantineMessageIdentity>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### IdentityOnly -``` -Delete-QuarantineMessage -Identity <QuarantineMessageIdentity> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Delete-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 -``` - -This example deletes the quarantined message with the specified Identity value. - -### Example 2 -```powershell -$ids = Get-QuarantineMessage | select -ExpandProperty Identity; Delete-QuarantineMessage -Identity $ids[4] -``` - -This example deletes the 5th quarantined message in the list of results from Get-QuarantineMessage. The first message has the index number 0, the second has the index number 1 and so on). - -### Example 3 -```powershell -$ids = Get-QuarantineMessage | select -ExpandProperty Identity; Delete-QuarantineMessage -Identities $ids -Identity 000 -``` - -This example deletes all quarantined messages. The Identity parameter is required, but the value 000 is ignored. - -## PARAMETERS - -### -Identities -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. - -When you use this parameter, the Identity parameter is required, but the value is ignored. For example, use the value 000 for the Identity parameter. - -```yaml -Type: QuarantineMessageIdentity[] -Parameter Sets: Identities -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: IdentityOnly -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Export-QuarantineMessage.md b/exchange/exchange-ps/exchange/antispam-antimalware/Export-QuarantineMessage.md deleted file mode 100644 index c0a55158c3..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Export-QuarantineMessage.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/export-quarantinemessage -applicable: Exchange Online, Exchange Online Protection -title: Export-QuarantineMessage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Export-QuarantineMessage - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Export-QuarantineMessage cmdlet to export quarantined messages and files from your cloud-based organization. Messages are exported to .eml message files so you can open them in Outlook. - -For files that are protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams, the files are exported in Base64 format. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Export-QuarantineMessage -Identity <QuarantineMessageIdentity> [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -$e = Export-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7; $e.BodyEncoding; $e | select -ExpandProperty Eml | Out-File "C:\My Documents\Export1_ascii.eml" -Encoding ascii -``` - -This example exports the quarantined message with the specified Identity value. - -The first two commands determine the message encoding (the value of the BodyEncoding property in the output; for example, ascii). - -The third command exports the message to the specified file using the message encoding that you found in the previous commands. - -Notes: - -- The `| select -ExpandProperty Eml`" part of the command specifies the whole message, including attachments. - -- You need to use the Out-File cmdlet to write the .eml message file with the required encoding. If you use the default PowerShell redirection operator ">" to write the output file, the default encoding is Unicode, which might not match the actual message encoding. - -### Example 2 -```powershell -$e = Export-QuarantineMessage -Identity 9c6bb3e8-db9e-4823-9759-08d594179bd3\7fec89fe-41b0-ae67-4887-5bede017d111; $bytes = [Convert]::FromBase64String($e.eml); [IO.File]::WriteAllBytes("C:\My Documents\Export1.txt", $bytes) -``` - -This example exports the quarantined file with the specified Identity value. The first command exports the file to a Base 64 string. The next two commands convert the string to byte format and write it to the output file. - -## PARAMETERS - -### -Identity -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: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-BlockedSenderAddress.md b/exchange/exchange-ps/exchange/antispam-antimalware/Get-BlockedSenderAddress.md deleted file mode 100644 index 3ae5240df5..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-BlockedSenderAddress.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-blockedsenderaddress -applicable: Exchange Online, Exchange Online Protection -title: Get-BlockedSenderAddress -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-BlockedSenderAddress - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-BlockedSenderAddress cmdlet to view users in your Office 365 organization that are impacted by the protection system. These users sent multiple messages that were classified as spam, so they're blocked from sending messages. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://technet.microsoft.com/library/bb123552.aspx). - -## SYNTAX - -``` -Get-BlockedSenderAddress [-SenderAddress <SmtpAddress>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://technet.microsoft.com/library/mt432940.aspx). - -## EXAMPLES - -### Example 1 -```powershell -Get-BlockedSenderAddress -``` - -This example returns information about all blocked senders. - -### Example 2 -```powershell -Get-BlockedSenderAddress -SenderAddress laura@contoso.com -``` - -This example returns information about the blocked sender laura@contoso.com. - -## PARAMETERS - -### -SenderAddress -The SenderAddress parameter filters the results by the email address of the blocked user. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### - - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-DkimSigningConfig.md b/exchange/exchange-ps/exchange/antispam-antimalware/Get-DkimSigningConfig.md deleted file mode 100644 index 633c859ae2..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-DkimSigningConfig.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-dkimsigningconfig -applicable: Exchange Online, Exchange Online Protection -title: Get-DkimSigningConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-DkimSigningConfig - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-DkimSigningConfig cmdlet to view the DomainKeys Identified Mail (DKIM) signing policy settings for domains in a cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DkimSigningConfig [[-Identity] <DkimSigningConfigIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -DKIM in Microsoft Office 365 is an email authentication method that uses a public key infrastructure (PKI), message headers and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DkimSigningConfig -``` - -This example shows a summary list of all DKIM signing policies in your organization. - -### Example 2 -```powershell -Get-DkimSigningConfig -Identity contoso.com | Format-List -``` - -This example shows detailed information for the DKIM signing policy for contoso.com. - -## PARAMETERS - -### -Identity -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). - -- Distinguished name (DN) - -- GUID - -```yaml -Type: DkimSigningConfigIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterRule.md deleted file mode 100644 index 456d3512ea..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterRule.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-hostedcontentfilterrule -applicable: Exchange Online, Exchange Online Protection -title: Get-HostedContentFilterRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-HostedContentFilterRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-HostedContentFilterRule cmdlet to view spam filter rules (content filter rules) in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-HostedContentFilterRule [[-Identity] <RuleIdParameter>] [-State <RuleState>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-HostedContentFilterRule -``` - -This example shows a summary list of all the spam filter rules in your cloud-based organization. - -### Example 2 -```powershell -Get-HostedContentFilterRule "Contoso Recipients" | Format-List -``` - -This example retrieves details about the spam filter rule named Contoso Recipients. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -State -The State parameter filters the results by the state of the rule. Valid values are: - -- Enabled: The command returns only enabled rules. - -- Disabled: The command returns only disabled rules. - -```yaml -Type: RuleState -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/Get-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/exchange/antispam-antimalware/Get-MailboxJunkEmailConfiguration.md deleted file mode 100644 index dea0d656d4..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-MailboxJunkEmailConfiguration.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MailboxJunkEmailConfiguration - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailboxJunkEmailConfiguration cmdlet to view the junk email settings on mailboxes. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxJunkEmailConfiguration [-Identity] <MailboxIdParameter> [-Credential <PSCredential>] - [-DomainController <Fqdn>] [-ReadFromDomainController] [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -The junk email settings on the mailbox are: - -- Enable or disable the junk email rule: The junk email rule (a hidden Inbox rule named Junk E-mail Rule) controls the delivery of messages to the Junk Email folder or the Inbox based on the SCL Junk Email Folder threshold (for the organization or the mailbox) and the safelist collection on the mailbox. Users can enable or disable the junk email rule in their own mailbox by using Outlook on the web. - -- Configure the safelist collection: The safelist collection is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list. Users can configure the safelist collection on their own mailbox by using Microsoft Outlook or Outlook on the web. - -Administrators can enable or disable the junk email rule, and configure the safelist collection on a mailbox by using the Set-MailboxJunkEmailConfiguration cmdlet. For more information, see [Configure Exchange antispam settings on mailboxes](https://docs.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxJunkEmailConfiguration -Identity "David Pelton" -``` - -This example returns the junk email configuration for the user named David Pelton. - -### Example 2 -```powershell -$AllUsers = Get-Mailbox -ResultSize unlimited -RecipientTypeDetails UserMailbox; $AllUsers | foreach {Get-MailboxJunkEmailConfiguration -Identity $_.UserPrincipalName} | Where {$_.Enabled -eq $false} | Format-Table -Auto Identity,Enabled -``` - -This example returns a summary list of all mailboxes in your organization where the junk email rule is disabled. The first command stores all user mailboxes in a variable. The second command parses through the mailboxes and returns the FQDN of the mailboxes where the junk email rule is disabled. - -To return all mailboxes where the junk email rule is enabled, change the value $false to $true. To return a mixed list of mailboxes where the junk email rule is enabled and disabled, remove the "| Where {$\_.Enabled -eq $false " part of the second command. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -You can use the wildcard character (\*) to identify multiple mailboxes. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: True -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -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 -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/Get-QuarantineMessage.md b/exchange/exchange-ps/exchange/antispam-antimalware/Get-QuarantineMessage.md deleted file mode 100644 index 975ea170e2..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-QuarantineMessage.md +++ /dev/null @@ -1,437 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-quarantinemessage -applicable: Exchange Online, Exchange Online Protection -title: Get-QuarantineMessage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-QuarantineMessage - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-QuarantineMessage cmdlet to view quarantined messages and files in your cloud-based organization. - -**Not**: Quarantined files are files protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Details -``` -Get-QuarantineMessage -Identity <QuarantineMessageIdentity> [-SenderAddress <String[]>] - [<CommonParameters>] -``` - -### Summary -``` -Get-QuarantineMessage [-Direction <QuarantineMessageDirectionEnum>] - [-Domain <String[]>] - [-EndExpiresDate <DateTime>] - [-EndReceivedDate <DateTime>] - [-MessageId <String>] - [-MyItems] - [-Page <Int32>] - [-PageSize <Int32>] - [-QuarantineTypes <QuarantineMessageTypeEnum[]>] - [-RecipientAddress <String[]>] - [-Reported <Boolean>] - [-SenderAddress <String[]>] - [-StartExpiresDate <DateTime>] - [-StartReceivedDate <DateTime>] - [-Subject <String>] - [-Type <QuarantineMessageTypeEnum>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-QuarantineMessage -StartReceivedDate 06/13/2016 -EndReceivedDate 06/15/2016 -``` - -This example returns a summary list of messages quarantined between June 13, 2016 and June 15, 2016. - -### Example 2 -```powershell -Get-QuarantineMessage -PageSize 50 -Page 3 -``` - -This example presents 50 quarantined messages per page, and returns the third page of results. - -### Example 3 -```powershell -Get-QuarantineMessage -MessageID "<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>" -``` - -This example returns the quarantined message with the Message-ID value `<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>`. - -### Example 4 -```powershell -Get-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 | Format-List -``` - -This example returns detailed information for the quarantined message with the specified Identity value. - -### Example 5 -```powershell -Get-QuarantineMessage -QuarantineTypes SPOMalware | Format-List -``` - -This example returns detailed information for the files protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams. - -## PARAMETERS - -### -Identity -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 <Identity> | Format-List`. - -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: Details -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid are Inbound and Outbound. - -```yaml -Type: QuarantineMessageDirectionEnum -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -The Domain parameter filters the results by sender or recipient domain. You can specify multiple domain values separated by commas. - -```yaml -Type: String[] -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndExpiresDate -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". - -For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days. - -```yaml -Type: DateTime -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndReceivedDate -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". - -```yaml -Type: DateTime -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageId -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, `"<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"`). - -```yaml -Type: String -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MyItems -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QuarantineTypes -The QuarantineTypes parameter filters the results by what caused the message to be quarantined. Valid values are: - -- Bulk - -- HighConfPhish - -- Phish - -- Spam - -- SPOMalware (ATP only) - -- TransportRule - -You can specify multiple values separated by commas. - -You don't need to use this parameter with the Type parameter. - -For files protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams, the detection information can be found in CustomData field in the output. - -```yaml -Type: QuarantineMessageTypeEnum[] -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAddress -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: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reported -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. - -- $false: The command only returns quarantined messages that haven't been reported as false positives. - -```yaml -Type: Boolean -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartExpiresDate -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". - -For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days. - -```yaml -Type: DateTime -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartReceivedDate -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". - -```yaml -Type: DateTime -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Subject -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -The Type parameter filters the results by what caused the message to be quarantined. Valid values are: - -- Bulk - -- HighConfPhish - -- Phish - -- Spam - -- SPOMalware (ATP only) - -- TransportRule - -You don't need to use this parameter with the QuarantineTypes parameter. - -For files protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams, the detection information can be found in CustomData field in the output. - -```yaml -Type: QuarantineMessageTypeEnum -Parameter Sets: Summary -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/Get-QuarantineMessageHeader.md b/exchange/exchange-ps/exchange/antispam-antimalware/Get-QuarantineMessageHeader.md deleted file mode 100644 index 0e8ca34360..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Get-QuarantineMessageHeader.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/get-quarantinemessageheader -applicable: Exchange Online, Exchange Online Protection -title: Get-QuarantineMessageHeader -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-QuarantineMessageHeader - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-QuarantineMessageHeader cmdlet to view the message header of a quarantined message. The command will fail if the specified message is not in quarantine. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-QuarantineMessageHeader -Identity <QuarantineMessageIdentity> [<CommonParameters>] -``` - -## DESCRIPTION -Standard SMTP message header syntax is described in RFC 5322. This cmdlet displays the message header exactly as it appears in the message. Individual header fields are not unfolded. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-QuarantineMessageHeader 65ab8c7d-dcd3-4067-7c60-08d116c001c3\8b677327-0ef3-166b-e108-ff6cb380d191 -``` - -This example displays the message header of the quarantined message that has the specified Identity value. - -### Example 2 -```powershell -$qMessages = Get-QuarantineMessage; Get-QuarantineMessageHeader $qMessages[0].Identity -``` - -This example displays the message header of the first message that's returned by Get-QuarantineMessage cmdlet. - -## PARAMETERS - -### -Identity -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. - -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md deleted file mode 100644 index ae5ae6d51f..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md +++ /dev/null @@ -1,1290 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/new-hostedcontentfilterpolicy -applicable: Exchange Online, Exchange Online Protection -title: New-HostedContentFilterPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# New-HostedContentFilterPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-HostedContentFilterPolicy cmdlet to create spam filter policies (content filter policies) in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-HostedContentFilterPolicy [-Name] <String> - [-AddXHeaderValue <String>] - [-AdminDisplayName <String>] - [-AllowedSenderDomains <MultiValuedProperty>] - [-AllowedSenders <MultiValuedProperty>] - [-BlockedSenderDomains <MultiValuedProperty>] - [-BlockedSenders <MultiValuedProperty>] - [-BulkSpamAction <SpamFilteringAction>] - [-BulkThreshold <Int32>] - [-Confirm] - [-DownloadLink <Boolean>] - [-EnableEndUserSpamNotifications <Boolean>] - [-EnableLanguageBlockList <Boolean>] - [-EnableRegionBlockList <Boolean>] - [-EndUserSpamNotificationCustomFromAddress <SmtpAddress>] - [-EndUserSpamNotificationCustomFromName <String>] - [-EndUserSpamNotificationCustomSubject <String>] - [-EndUserSpamNotificationFrequency <Int32>] - [-EndUserSpamNotificationLanguage <EsnLanguage>] - [-EndUserSpamNotificationLimit <Int32>] - [-HighConfidencePhishAction <PhishFilteringAction>] - [-HighConfidenceSpamAction <SpamFilteringAction>] - [-IncreaseScoreWithBizOrInfoUrls <SpamFilteringOption>] - [-IncreaseScoreWithImageLinks <SpamFilteringOption>] - [-IncreaseScoreWithNumericIps <SpamFilteringOption>] - [-IncreaseScoreWithRedirectToOtherPort <SpamFilteringOption>] - [-InlineSafetyTipsEnabled <Boolean>] - [-LanguageBlockList <MultiValuedProperty>] - [-MarkAsSpamBulkMail <SpamFilteringOption>] - [-MarkAsSpamEmbedTagsInHtml <SpamFilteringOption>] - [-MarkAsSpamEmptyMessages <SpamFilteringOption>] - [-MarkAsSpamFormTagsInHtml <SpamFilteringOption>] - [-MarkAsSpamFramesInHtml <SpamFilteringOption>] - [-MarkAsSpamFromAddressAuthFail <SpamFilteringOption>] - [-MarkAsSpamJavaScriptInHtml <SpamFilteringOption>] - [-MarkAsSpamNdrBackscatter <SpamFilteringOption>] - [-MarkAsSpamObjectTagsInHtml <SpamFilteringOption>] - [-MarkAsSpamSensitiveWordList <SpamFilteringOption>] - [-MarkAsSpamSpfRecordHardFail <SpamFilteringOption>] - [-MarkAsSpamWebBugsInHtml <SpamFilteringOption>] - [-ModifySubjectValue <String>] - [-PhishSpamAction <SpamFilteringAction>] - [-PhishZapEnabled <Boolean> - [-QuarantineRetentionPeriod <Int32>] - [-RedirectToRecipients <MultiValuedProperty>] - [-RegionBlockList <MultiValuedProperty>] - [-SpamAction <SpamFilteringAction>] - [-SpamZapEnabled <Boolean>] - [-TestModeAction <SpamFilteringTestModeAction>] - [-TestModeBccToRecipients <MultiValuedProperty>] - [-WhatIf] - [-ZapEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://docs.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits). - -## EXAMPLES - -### Example 1 -```powershell -New-HostedContentFilterPolicy -Name "Contoso Executives" -HighConfidenceSpamAction Quarantine -SpamAction Quarantine -BulkThreshold 6 -``` - -This example creates a spam filter policy named Contoso Executives with the following settings: - -- Quarantine messages when the spam filtering verdict is spam or high confidence spam. - -- BCL 6 triggers the action for a bulk email spam filtering verdict. - -## PARAMETERS - -### -Name -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: \\, %, &, \*, +, /, =, ?, {, }, \|, \<, \>, (, ), ;, :, [, ], comma (,), or double quotation mark ("). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddXHeaderValue -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 - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -The maximum length is 255 characters, and the value can't contain spaces or colons (:). - -For example, if you enter the value `X-This-is-my-custom-header`, the X-header that's added to the message is `X-This-is-my-custom-header: This message appears to be spam.` - -If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`). - -Note that this setting is independent of the AddXHeader value of the TestModeAction parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowedSenderDomains -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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-safe-sender-lists-in-office-365). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowedSenders -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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-safe-sender-lists-in-office-365). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockedSenderDomains -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 9 (high confidence 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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-block-sender-lists-in-office-365?). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockedSenders -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 9 (high confidence 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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-block-sender-lists-in-office-365?). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BulkSpamAction -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. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In Exchange Online, the message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://docs.microsoft.com/microsoft-365/security/office-365-security/censure-that-spam-is-routed-to-each-user-s-junk-email-folder). - -- NoAction - -- Quarantine: Move the message to the quarantine. The quarantined message is available to the intended recipients and admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BulkThreshold -The BulkThreshold parameter specifies the BCL that triggers the BulkSpamAction on the message (greater than the specified value, not greater than or equal to). A valid value is an integer from 1 to 9, and the default value is 7. A higher value indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk compliant level (BCL) in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/bulk-complaint-level-values). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DownloadLink -The DownloadLink parameter shows or hides a link in end-user spam quarantine notifications to download the Junk Email Reporting Tool for Outlook. Valid values are: - -- $true: end-user spam quarantine notifications contain a link to download the Junk Email Reporting Tool for Outlook. - -- $false: end-user spam quarantine notifications don't contain the link. This is the default value. - -This parameter is only meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableEndUserSpamNotifications -The EnableEndUserSpamNotification parameter enables for disables sending end-user spam quarantine notifications. Valid values are: - -- $true: End-users periodically receive notifications when a messages that was supposed to be delivered to them was quarantined as spam. When you use this value, you can also use the EndUserSpamNotificationCustomSubject, EndUserSpamNotificationFrequency, and EndUserSpamNotificationLanguage parameters. - -- $false: end-user spam quarantine notifications are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableLanguageBlockList -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. - -- $false: Don't mark messages as spam solely based on their languages. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableRegionBlockList -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. - -- $false: Don't mark messages as spam solely based on the source country or region. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationCustomFromAddress -This parameter has been deprecated and is no longer used. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationCustomFromName -This parameter has been deprecated and is no longer used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationCustomSubject -The EndUserSpamNotificationCustomSubject parameter specifies a custom subject for end-user spam notification messages. If the value includes spaces, enclose the value in quotation marks ("). - -This parameter is meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationFrequency -The EndUserSpamNotificationFrequency parameter specifies the repeat interval in days that end-user spam quarantine notifications are sent. A valid value is an integer between 1 and 15. The default value is 3. - -This parameter is meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationLanguage -The EndUserSpamNotificationLanguage parameter specifies the language of end-user spam 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. - -The default value is Default, which means end-user spam quarantine notifications use the default language of the cloud-based organization. - -This parameter is meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: EsnLanguage -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationLimit -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HighConfidencePhishAction -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: - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is only available to admins. - -```yaml -Type: PhishFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HighConfidenceSpamAction -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). - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In Exchange Online, the message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://docs.microsoft.com/microsoft-365/security/office-365-security/censure-that-spam-is-routed-to-each-user-s-junk-email-folder). - -- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients and admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithBizOrInfoUrls -**Note**: This setting is part of Advanced Spam Filtering (ASF) and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain links to .biz or .info domains are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithImageLinks -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain image links to remote websites are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithNumericIps -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain links to IP addresses are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithRedirectToOtherPort -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InlineSafetyTipsEnabled -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. - -- $false: Safety tips are disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LanguageBlockList -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 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. - -A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Note that not all possible language codes are available as input for this parameter. - -To enter multiple values and overwrite any existing entries, use the following syntax: \<value1\>,\<value2\>,...\<valueN\>. - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -To empty the list, use the value $null. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamBulkMail -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. - -- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. - -- Test: This value is available, but isn't used for this parameter. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamEmbedTagsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \<embed\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<embed\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamEmptyMessages -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamFormTagsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \<form\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<form\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamFramesInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \<frame\> or \<iframe\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<frame\> or \<iframe\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamFromAddressAuthFail -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamJavaScriptInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamNdrBackscatter -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamObjectTagsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \<object\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<object\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamSensitiveWordList -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamSpfRecordHardFail -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamWebBugsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModifySubjectValue -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 - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhishSpamAction -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. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients (as of April, 2020) and admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhishZapEnabled -The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing messages in delivered messages in Exchange Online mailboxes. Valid values are: - -- $true: Phish ZAP is enabled. This is the default value. The result depends on the spam filtering verdict action: MoveToJmf = Read and unread phish messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine: Read and unread phish messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - -- $false: Phish ZAP is disabled. - -**Note**: Use this parameter instead of the ZapEnabled parameter. The ZapEnabled parameter will be deprecated in a future release. During the transition, the value of this parameter is inherited from the ZapEnabled parameter. After you use the PhishZapEnabled parameter or the corresponding phish ZAP setting in the admin center on an existing spam filter policy, the ZapEnabled parameter value is ignored for phish ZAP. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QuarantineRetentionPeriod -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 - -- HighConfidencePhishAction - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -A valid value is an integer between 1 and 30. The default value is 30. - -After the time period expires, the message is deleted. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RedirectToRecipients -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 - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -You can specify multiple email addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionBlockList -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. - -A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). - -To enter multiple values and overwrite any existing entries, use the following syntax: \<value1\>,\<value2\>,...\<valueN\>. - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -To empty the list, use the value $null. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpamAction -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). - -- Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In Exchange Online, the message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the k Email folder in hybrid environments](https://docs.microsoft.com/microsoft-365/security/office-365-security/censure-that-spam-is-routed-to-each-user-s-junk-email-folder). - -- Quarantine: Move the message to the quarantine. The quarantined message is available to the intended recipients and admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpamZapEnabled -The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in delivered messages in Exchange Online mailboxes. Valid values are: - -- $true: Spam ZAP is enabled. This is the default value. The result depends on the spam filtering verdict action: 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. - -- $false: Spam ZAP is disabled. - -**Note**: Use this parameter instead of the ZapEnabled parameter. The ZapEnabled parameter will be deprecated in a future release. During the transition, the value of this parameter is inherited from the ZapEnabled parameter. After you use the SpamZapEnabled parameter or the corresponding spam ZAP setting in the admin center on an existing spam filter policy, the ZapEnabled parameter value is ignored for spam ZAP. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TestModeAction -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you don't use this setting. - -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. - -- AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. - -- BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter. - -```yaml -Type: SpamFilteringTestModeAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TestModeBccToRecipients -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you don't use this setting. - -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. - -This parameter is meaningful only when the value of the TestModeAction parameter is BccMessage, and when the value of one or more IncreaseScoreWith\* or MarkAsSpam\* parameters is Test. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ZapEnabled -**Note**: This parameter will be deprecated in a future release. Use the PhishZapEnabled and SpamZapEnabled parameters instead. After you use these parameters or configure the phish ZAP or spam ZAP settings in the admin center, the value of this parameter is ignored. - -The ZapEnabled parameter specifies whether to enable ZAP for phish and spam in Exchange Online mailboxes. Valid values are: - -- $true: ZAP for phish and spam is enabled. This is the default value. - -- $false: ZAP for phish and spam is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/New-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedOutboundSpamFilterPolicy.md deleted file mode 100644 index c59e838e26..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/New-HostedOutboundSpamFilterPolicy.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/new-hostedoutboundspamfilterpolicy -applicable: Exchange Online, Exchange Online Protection -title: New-HostedOutboundSpamFilterPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# New-HostedOutboundSpamFilterPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-HostedOutboundSpamFilterPolicy cmdlet to create outbound spam filter policies in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-HostedOutboundSpamFilterPolicy [-Name] <String> - [-ActionWhenThresholdReached <OutboundRecipientLimitsExceededAction>] - [-AdminDisplayName <String>] - [-BccSuspiciousOutboundAdditionalRecipients <MultiValuedProperty>] - [-BccSuspiciousOutboundMail <Boolean>] - [-NotifyOutboundSpam <Boolean>] - [-NotifyOutboundSpamRecipients <MultiValuedProperty>] - [-RecipientLimitExternalPerHour <UInt32>] - [-RecipientLimitInternalPerHour <UInt32>] - [-RecipientLimitPerDay <UInt32>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-HostedOutboundSpamFilterPolicy -Name "Contoso Executives" -RecipientLimitExternalPerHour 400 -RecipientLimitInternalPerHour 800 -RecipientLimitPerDay 800 -ActionWhenThresholdReached BlockUser -``` - -This example creates a new outbound spam filter policy named Contoso Executives with the following settings: - -- The recipient rate limits are restricted to smaller values that the service defaults. - -- After one of the limits is reached, the user is prevented from sending messages (added to the Restricted Users portal). - -## PARAMETERS - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActionWhenThresholdReached -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. - -- BlockUser: Prevent the user from sending email messages. - -- BlockUserForToday: Prevent the user from sending email messages until the following day. This is the default value. - -```yaml -Type: OutboundRecipientLimitsExceededAction -Parameter Sets: (All) -Aliases: -Accepted values: Alert, BlockUserForToday, BlockUser -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BccSuspiciousOutboundAdditionalRecipients -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BccSuspiciousOutboundMail -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. - -- $false: No additional messages are added to outgoing spam messages. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyOutboundSpam -**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://docs.microsoft.com/microsoft-365/security/office-365-security/removing-user-from-restricted-users-portal-after-spam.md#verify-the-alert-settings-for-restricted-users). - -The NotifyOutboundSpam parameter specify whether to notify admins when outgoing spam is detected. Valid values are: - -- $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter. - -- $false: Don't send notifications. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyOutboundSpamRecipients -**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://docs.microsoft.com/microsoft-365/security/office-365-security/removing-user-from-restricted-users-portal-after-spam#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. - -The specified recipients receive notifications when the value of the NotifyOutboundSpam parameter is $true. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientLimitExternalPerHour -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 Office 365 options](https://docs.microsoft.com/microsoft-365/security/office-365-security/removing-user-from-restricted-users-portal-after-spam#verify-the-alert-settings-for-restricted-users). - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientLimitInternalPerHour -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 Office 365 options](https://docs.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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientLimitPerDay -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 Office 365 options](https://docs.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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/New-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/antispam-antimalware/New-MalwareFilterPolicy.md deleted file mode 100644 index f285d42c10..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/New-MalwareFilterPolicy.md +++ /dev/null @@ -1,616 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# New-MalwareFilterPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-MalwareFilterPolicy cmdlet to create malware filter policies in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-MalwareFilterPolicy [-Name] <String> - [-Action <MalwareFilteringAction>] - [-AdminDisplayName <String>] - [-BypassInboundMessages <Boolean>] - [-BypassOutboundMessages <Boolean>] - [-Confirm] - [-CustomAlertText <String>] - [-CustomExternalBody <String>] - [-CustomExternalSubject <String>] - [-CustomFromAddress <SmtpAddress>] - [-CustomFromName <String>] - [-CustomInternalBody <String>] - [-CustomInternalSubject <String>] - [-CustomNotifications <Boolean>] - [-DomainController <Fqdn>] - [-EnableExternalSenderAdminNotifications <Boolean>] - [-EnableExternalSenderNotifications <Boolean>] - [-EnableFileFilter <Boolean>] - [-EnableInternalSenderAdminNotifications <Boolean>] - [-EnableInternalSenderNotifications <Boolean>] - [-ExternalSenderAdminAddress <SmtpAddress>] - [-FileTypes <String[]>] - [-InternalSenderAdminAddress <SmtpAddress>] - [-WhatIf] - [-ZapEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-MalwareFilterPolicy -Name "Contoso Malware Filter Policy" -EnableInternalSenderAdminNotifications $true -InternalSenderAdminAddress admin@contoso.com -``` - -This example creates a new malware filter policy named Contoso Malware Filter Policy with the following settings: - -- Block messages that contain malware. - -- Don't notify the message sender when malware is detected in the message. - -- Notify the administrator admin@contoso.com when malware is detected in a message from an internal sender. - -## PARAMETERS - -### -Name -The Name parameter specifies a name for 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Action -The Action parameter specifies the action to take when malware is detected in a message. Valid values are: - -- DeleteMessage: Handles the message without notifying the recipients. This is the default value. In Exchange Server, the message is deleted. In the cloud-based service, the message is quarantined. - -- DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. In the cloud-based service, the message with the original attachments is also quarantined. - -- DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. In the cloud-based service, the message with the original attachments is also quarantined. - -```yaml -Type: MalwareFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassInboundMessages -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: - -- $true: Malware filtering is disabled on inbound messages. - -- $false: Malware filtering is enabled on inbound messages. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassOutboundMessages -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: - -- $true: Malware filtering is disabled on outbound messages. - -- $false: Malware filtering is enabled on outbound messages. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAlertText -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 ("). - -This parameter is only meaningful when the Action parameter value is ReplaceWithCustomAlert. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomExternalBody -The CustomExternalBody parameter specifies the body of the custom notification message for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomExternalSubject -The CustomExternalSubject parameter specifies the subject of the custom notification message for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomFromAddress -The CustomFromAddress parameter specifies the From address of the custom notification message for malware detections in messages from internal or external senders. - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomFromName -The CustomFromName parameter specifies the From name of the custom notification message for malware detections in messages from internal or external senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomInternalBody -The CustomInternalBody parameter specifies the body of the custom notification message for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomInternalSubject -The CustomInternalSubject parameter specifies the subject of the custom notification message for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomNotifications -The CustomNotifications parameter enables or disables custom notification messages for malware detections in messages from internal or external senders. Valid values are: - -- $true: When malware is detected in a message, a custom notification message is sent to the message sender. You specify the details of message using the CustomFromAddress, CustomFromName, CustomExternalSubject, CustomExternalBody, CustomInternalSubject and CustomInternalBody parameters. - -- $false: Custom notifications to the original message sender are disabled. This is the default value. Default notification messages are sent if the EnableExternalSenderNotifications and EnableInternalSenderNotifications parameters are set to $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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableExternalSenderAdminNotifications -The EnableExternalSenderAdminNotifications parameter enables or disables sending malware detection notification messages to an administrator for messages from external senders. Valid values are: - -- $true: When malware is detected in messages from external senders, send notification messages to the email address that's specified by the ExternalSenderAdminAddress parameter. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomExternalBody, and CustomExternalSubject parameters. - -- $false: When malware is detected in messages from external senders, don't send administrator notifications. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableExternalSenderNotifications -The EnableExternalSenderNotifications parameter enables or disables notification messages for malware detections in messages from external senders. Valid values are: - -- $true: When malware is detected in a message from an external sender, send them a notification message. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomExternalBody, and CustomExternalSubject parameters. - -- $false: Don't send malware detection notification messages to external message senders. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableFileFilter -The EnableFileFilter parameter enables or disables common attachment blocking (also known as the Common Attachment Types Filter). Valid values are: - -- $true: Common attachment blocking is enabled. The file types are defined by the FileTypes parameter. - -- $false: Common attachment blocking is disabled. This is the default value. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableInternalSenderAdminNotifications -The EnableInternalSenderAdminNotifications parameter enables or disables sending malware detection notification messages to an administrator for messages from internal senders. Valid values are: - -- $true: When malware is detected in messages from internal senders, send notification messages to the email address that's specified by the InternalSenderAdminAddress parameter. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomInternalBody, and CustomInternalSubject parameters. - -- $false: When malware is detected in messages from internal senders, don't send administrator notifications. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableInternalSenderNotifications -The EnableInternalSenderNotifications parameter enables or disables notification messages for malware detections in messages from internal senders. Valid values are: - -- $true: When malware is detected in a message from an internal sender, send them a notification message. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomInternalBody, and CustomInternalSubject parameters. - -- $false: Don't send malware detection notification messages to internal message senders. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalSenderAdminAddress -The ExternalSenderAdminAddress parameter specifies the email address of the administrator who will receive notifications messages when messages from external senders contain malware. Notification messages are sent to the specified email address only if the EnableExternalSenderAdminNotifications parameter is set to $true. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileTypes -The FileTypes parameter specifies the file types that are automatically blocked by common attachment blocking (also known as the Common Attachment Types Filter), regardless of content. The default values are: - -- .ace - -- .ani - -- .app - -- .docm - -- .exe - -- .jar - -- .reg - -- .scr - -- .vbe - -- .vbs - -You enable or disable common attachment blocking by using the EnableFileFilter parameter. - -Common attachment blocking uses best effort true-typing to detect the file type regardless of the file name extension. If true-typing fails or isn't supported for the specified file type, then extension matching is used. For example, .ps1 files are Windows PowerShell scripts, but their true type is text. - -To replace the existing list of file types with the values you specify, use the syntax \<FileType1\>,\<FileType2\>,...\<FileTypeN\>. To preserve existing values, be sure to include the file types that you want to keep along with the new values that you want to add. - -To add or remove file types without affecting the other file type entries, see the Examples section in the Set-MalwareFilterPolicy cmdlet topic. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalSenderAdminAddress -The InternalSenderAdminAddress parameter specifies the email address of the administrator who will receive notification messages for malware detections in messages from internal senders. - -This parameter is only meaningful if the EnableInternalSenderAdminNotifications parameter value is $true. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ZapEnabled -The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: - -- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This is the default value. - -- $false: ZAP for malware is disabled. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/Preview-QuarantineMessage.md b/exchange/exchange-ps/exchange/antispam-antimalware/Preview-QuarantineMessage.md deleted file mode 100644 index a28309e3b6..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Preview-QuarantineMessage.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/preview-quarantinemessage -applicable: Exchange Online, Exchange Online Protection -title: Preview-QuarantineMessage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Preview-QuarantineMessage - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Preview-QuarantineMessage cmdlet to preview the contents of quarantined messages in your cloud-based organization. - -**Note**: This cmdlet isn't available for files that are protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business, and Microsoft Teams. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Preview-QuarantineMessage -Identity <QuarantineMessageIdentity> [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-QuarantineMessage -MessageID <5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com> | Preview-QuarantineMessage -``` - -This example previews the quarantined message with the Message-ID value `<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>`. - -### Example 2 -```powershell -Preview-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 -``` - -This example previews the quarantined message that has the specified Identity value. - -## PARAMETERS - -### -Identity -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. - -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Release-QuarantineMessage.md b/exchange/exchange-ps/exchange/antispam-antimalware/Release-QuarantineMessage.md deleted file mode 100644 index ff1653068b..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Release-QuarantineMessage.md +++ /dev/null @@ -1,334 +0,0 @@ - --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/release-quarantinemessage -applicable: Exchange Online, Exchange Online Protection -title: Release-QuarantineMessage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Release-QuarantineMessage - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Release-QuarantineMessage cmdlet to release messages from quarantine in your cloud-based organization. You can release messages to all original recipients, or to specific recipients. - -For files that are protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams, you can unblock the files in the respective team sites and document libraries by using the Release-QuarantineMessage cmdlet so users can access, share, and download the files. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### OrgReleaseToUser -``` -Release-QuarantineMessage [-Identities <QuarantineMessageIdentity[]>] [-Identity <QuarantineMessageIdentity>] -User <String[]> - [-AllowSender] - [-Confirm] - [-Force] - [-ReportFalsePositive] - [-WhatIf] [<CommonParameters>] -``` - -### OrgReleaseToAll -``` -Release-QuarantineMessage [-Identities <QuarantineMessageIdentity[]>] [-Identity <QuarantineMessageIdentity>] [-ReleaseToAll] - [-AllowSender] - [-Confirm] - [-Delete] - [-Force] - [-ReportFalsePositive] - [-WhatIf] [<CommonParameters>] -``` - -### Identities -``` -Release-QuarantineMessage -Identities <QuarantineMessageIdentity[]> [-Identity <QuarantineMessageIdentity>] - [-AllowSender] - [-Confirm] - [-Force] - [-ReportFalsePositive] - [-WhatIf] [<CommonParameters>] -``` - -### IdentityOnly -``` -Release-QuarantineMessage -Identity <QuarantineMessageIdentity> - [-AllowSender] - [-Confirm] - [-Force] - [-ReportFalsePositive] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-QuarantineMessage -MessageID "<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>" | Release-QuarantineMessage -User julia@contoso.com -``` - -This example uses the Get-QuarantineMessage cmdlet to release the quarantined message with the Message-ID value `<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>` to an original recipient julia@contoso.com. - -### Example 2 -```powershell -Release-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 -ReleaseToAll -``` - -This example releases the quarantined message with the specified Identity value to all original recipients. - -### Example 3 -```powershell -Get-QuarantineMessage | Release-QuarantineMessage -ReleaseToAll -``` - -This example releases all messages to all original recipients. - -### Example 4 -```powershell -$q = Get-QuarantineMessage -QuarantineTypes SPOMalware; $q[-1] | Release-QuarantineMessage -ReleaseToAll -``` - -This example releases a file that was quarantined as part of Office 365 Advanced Threat Protection. The first command stores all SharePoint Online, OneDrive for Business and Microsoft Teams quarantined files in the variable $q. The second command releases the last file in the list. For more information about elements in arrays and index numbers, see [Accessing and Using Array Elements](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_arrays#accessing-and-using-array-elements). - -## PARAMETERS - -### -Identities -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. - -When you use this parameter, the Identity parameter is required, but the value is ignored. For example, use the value 000 for the Identity parameter. - -```yaml -Type: QuarantineMessageIdentity[] -Parameter Sets: Identities -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: QuarantineMessageIdentity[] -Parameter Sets: OrgReleaseToAll, OrgReleaseToUser -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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 -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: IdentityOnly -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ReleaseToAll -The ReleaseToAll switch releases the quarantined message to all original recipients. You don't need to specify a value with this switch. - -This parameter is required for the quarantine type SPOMalware. - -If you previously used the User parameter or the ReleaseToAll switch to release the quarantined message to some or all of the original recipients, those recipients are skipped when you use the ReleaseToAll switch again. - -You can't use the ReleaseToAll switch and the User parameter in the same command. - -```yaml -Type: SwitchParameter -Parameter Sets: OrgReleaseToAll -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -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. - -If you previously used the ReleaseToAll switch to release the quarantined message to all original recipients, and you later release the message again with the User parameter, any original recipients you specify with the User parameter are skipped. - -```yaml -Type: String[] -Parameter Sets: OrgReleaseToUser -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowSender -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Delete -This parameter has been deprecated and is no longer used. - -To delete quarantined messages, use the Delete-QuarantineMessage cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: OrgReleaseToAll -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to attempt the re-release of previously released messages from quarantine. You don't need to specify a value with this switch. - -You need to use this switch whenever you attempt to re-release previously released messages from quarantine. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportFalsePositive -The ReportFalsePositive switch sends a notification message indicating the specified message was not spam. You don't need to specify a value with this switch. - -This switch is only available for quarantined spam messages. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/Remove-BlockedSenderAddress.md b/exchange/exchange-ps/exchange/antispam-antimalware/Remove-BlockedSenderAddress.md deleted file mode 100644 index f9c6931e8e..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-BlockedSenderAddress.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-blockedsenderaddress -applicable: Exchange Online, Exchange Online Protection -title: Remove-BlockedSenderAddress -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Remove-BlockedSenderAddress - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-BlockedSenderAddress cmdlet to unblock users in your Office 365 organization that were impacted by the protection system. These users sent multiple messages that were classified as spam, so they were blocked from sending messages. - -**Note: There's a limit to the number of times you can unblock an Office 365 account. -If you exceed the unblock limit for a user, you'll receive an error, and you'll need to contact support to unblock the user. - -For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx). - -## SYNTAX - -``` -Remove-BlockedSenderAddress -SenderAddress <SmtpAddress> - [-Reason <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx). - -## EXAMPLES - -### Example 1 -```powershell -Remove-BlockedSenderAddress -SenderAddress julia@contoso.com -``` - -This example unblocks the user julia@contoso.com. - -## PARAMETERS - -### -SenderAddress -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 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reason -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterPolicy.md deleted file mode 100644 index 4be4142499..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterPolicy.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/remove-hostedoutboundspamfilterpolicy -applicable: Exchange Online, Exchange Online Protection -title: Remove-HostedOutboundSpamFilterPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Remove-HostedOutboundSpamFilterPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-HostedOutboundSpamFilterPolicy cmdlet to remove outbound spam filter policies from your cloud-based organization. - -When a policy is removed and there are rules associated with it, the rules are not removed when the policy is removed. This is by design. If you want to remove the associated rules, you need to do this separately via the Remove-HostedOutboundSpamFilterRule cmdlet. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-HostedOutboundSpamFilterPolicy [-Identity] <HostedOutboundSpamFilterPolicyIdParameter> [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-HostedOutboundSpamFilterPolicy -Identity "Contoso Executives" -``` - -This example removes the outbound spam filter policy named Contoso Executives. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: HostedOutboundSpamFilterPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Force -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-ContentFilterConfig.md b/exchange/exchange-ps/exchange/antispam-antimalware/Set-ContentFilterConfig.md deleted file mode 100644 index fe7d2839dc..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-ContentFilterConfig.md +++ /dev/null @@ -1,370 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-contentfilterconfig -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ContentFilterConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Set-ContentFilterConfig - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Set-ContentFilterConfig cmdlet to modify the content filter configuration on a Mailbox server or an Edge Transport server. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ContentFilterConfig [-BypassedRecipients <MultiValuedProperty>] - [-BypassedSenderDomains <MultiValuedProperty>] [-BypassedSenders <MultiValuedProperty>] [-Confirm] - [-DomainController <Fqdn>] [-Enabled <Boolean>] [-ExternalMailEnabled <Boolean>] - [-InternalMailEnabled <Boolean>] [-OutlookEmailPostmarkValidationEnabled <Boolean>] - [-QuarantineMailbox <SmtpAddress>] [-RejectionResponse <AsciiString>] [-SCLDeleteEnabled <Boolean>] - [-SCLDeleteThreshold <Int32>] [-SCLQuarantineEnabled <Boolean>] [-SCLQuarantineThreshold <Int32>] - [-SCLRejectEnabled <Boolean>] [-SCLRejectThreshold <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-ContentFilterConfig -BypassedSenderDomains woodgrovebank.com -``` - -This example specifies the sender domain woodgrovebank.com as a bypassed domain. Messages received from that domain bypass the Content Filter agent. - -### Example 2 -```powershell -Set-ContentFilterConfig -SCLQuarantineEnabled $true -SCLRejectEnabled $true -SCLDeleteEnabled $true -SCLQuarantineThreshold 5 -SCLRejectThreshold 6 -SCLDeleteThreshold 8 -QuarantineMailbox SpamQuarantineMailbox@contoso.com -RejectionResponse "Message rejected due to content restrictions" -BypassedRecipients user1@contoso.com,user2@contoso.com -``` - -This example makes the following modifications to the Content Filter agent configuration: - -It enables and configures the SCL threshold functionalities that quarantine, reject and delete messages to 5, 6 and 8 respectively. - -It specifies SpamQuarantineMailbox@contoso.com as the spam quarantine mailbox. - -It defines two users for whom the Content Filter won't process messages. - -## PARAMETERS - -### -BypassedRecipients -The BypassedRecipients parameter specifies the SMTP address values of recipients in your organization. The Content Filter agent doesn't process any content filtering for messages bound to the addresses listed on this parameter. To enter multiple SMTP addresses, separate the addresses by using a comma, for example: recipient1@contoso.com,recipient2@contoso.com. The maximum number of recipients you can input is 100. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassedSenderDomains -The BypassedSenderDomains parameter specifies domain name values of sending domains. The Content Filter agent doesn't process any content filtering for messages received from the domains listed on this parameter. To enter multiple domains, separate the addresses by using a comma, for example: contoso.com, example.com. A wildcard character (\*) can be used to specify all subdomains, for example: \*.contoso.com. The maximum number of domains you can input is 100. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassedSenders -The BypassedSenders parameter specifies the SMTP address values of senders. The Content Filter agent doesn't process any content filtering for messages received from the addresses listed on this parameter. To enter multiple SMTP addresses, separate the addresses by using a comma, for example: sender1@contoso.com, sender2@example.com. The maximum number of SMTP addresses you can input is 100. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter enables or disables the Content Filter agent 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. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalMailEnabled -The ExternalMailEnabled parameter specifies whether all messages from unauthenticated connections from sources external to your Exchange organization are passed through the Content 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 from unauthenticated connections are passed through the Content 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalMailEnabled -The InternalMailEnabled parameter specifies whether all messages from authenticated connections and from authoritative domains in your enterprise are passed through the Content 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 connections and from authoritative domains in your enterprise are passed through the Content 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutlookEmailPostmarkValidationEnabled -The OutlookEmailPostmarkValidationEnabled parameter specifies whether the Content Filter agent sends a computational puzzle to the sender's system for processing. Valid input for the OutlookEmailPostmarkValidationEnabled parameter is $true or $false. When the OutlookEmailPostmarkValidationEnabled parameter is set to $true, the Content Filter agent sends a computational puzzle to the sender's system for processing. The results of the puzzle validation are factored into the overall spam confidence level (SCL). This functionality is exposed to the Microsoft Outlook user as Outlook E-mail Postmark validation. The default setting 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QuarantineMailbox -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 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RejectionResponse -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SCLDeleteEnabled -The SCLDeleteEnabled parameter specifies whether all messages that exceed the value set in the SCLDeleteThreshold parameter are deleted. Valid input for the SCLDeleteEnabled parameter is $true or $false. The default setting is $false. When the SCLDeleteEnabled parameter is set to $true, all messages that exceed the value set in the SCLDeleteThreshold parameter are deleted. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SCLDeleteThreshold -The SCLDeleteThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SCLQuarantineEnabled -The SCLQuarantineEnabled parameter specifies whether all messages that exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter. Valid input for the SCLQuarantineEnabled parameter is $true or $false. The default setting is $false. When the SCLQuarantineEnabled parameter is set to $true, all messages that exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SCLQuarantineThreshold -The SCLQuarantineThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SCLRejectEnabled -The SCLRejectEnabled parameter specifies whether all messages that exceed the value set in the SCLRejectThreshold parameter are rejected, and an NDR is sent to the sender. Valid input for the SCLRejectEnabled parameter is $true or $false. The default setting is $false. When SCLRejectEnabled parameter is set to $true, all messages that exceed the value set in the SCLRejectThreshold parameter are rejected, and an NDR is sent to the sender. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SCLRejectThreshold -The SCLRejectThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must 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 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/Set-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md deleted file mode 100644 index 6e9668a767..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md +++ /dev/null @@ -1,1315 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-hostedcontentfilterpolicy -applicable: Exchange Online, Exchange Online Protection -title: Set-HostedContentFilterPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-HostedContentFilterPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-HostedContentFilterPolicy cmdlet to modify spam filter policies (content filter policies) in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-HostedContentFilterPolicy [-Identity] <HostedContentFilterPolicyIdParameter> - [-AddXHeaderValue <String>] - [-AdminDisplayName <String>] - [-AllowedSenderDomains <MultiValuedProperty>] - [-AllowedSenders <MultiValuedProperty>] - [-BlockedSenderDomains <MultiValuedProperty>] - [-BlockedSenders <MultiValuedProperty>] - [-BulkSpamAction <SpamFilteringAction>] - [-BulkThreshold <Int32>] - [-Confirm] - [-DownloadLink <Boolean>] - [-EnableEndUserSpamNotifications <Boolean>] - [-EnableLanguageBlockList <Boolean>] - [-EnableRegionBlockList <Boolean>] - [-EndUserSpamNotificationCustomFromAddress <SmtpAddress>] - [-EndUserSpamNotificationCustomFromName <String>] - [-EndUserSpamNotificationCustomSubject <String>] - [-EndUserSpamNotificationFrequency <Int32>] - [-EndUserSpamNotificationLanguage <EsnLanguage>] - [-EndUserSpamNotificationLimit <Int32>] - [-HighConfidencePhishAction <PhishFilteringAction>] - [-HighConfidenceSpamAction <SpamFilteringAction>] - [-IncreaseScoreWithBizOrInfoUrls <SpamFilteringOption>] - [-IncreaseScoreWithImageLinks <SpamFilteringOption>] - [-IncreaseScoreWithNumericIps <SpamFilteringOption>] - [-IncreaseScoreWithRedirectToOtherPort <SpamFilteringOption>] - [-InlineSafetyTipsEnabled <Boolean>] - [-LanguageBlockList <MultiValuedProperty>] - [-MakeDefault] - [-MarkAsSpamBulkMail <SpamFilteringOption>] - [-MarkAsSpamEmbedTagsInHtml <SpamFilteringOption>] - [-MarkAsSpamEmptyMessages <SpamFilteringOption>] - [-MarkAsSpamFormTagsInHtml <SpamFilteringOption>] - [-MarkAsSpamFramesInHtml <SpamFilteringOption>] - [-MarkAsSpamFromAddressAuthFail <SpamFilteringOption>] - [-MarkAsSpamJavaScriptInHtml <SpamFilteringOption>] - [-MarkAsSpamNdrBackscatter <SpamFilteringOption>] - [-MarkAsSpamObjectTagsInHtml <SpamFilteringOption>] - [-MarkAsSpamSensitiveWordList <SpamFilteringOption>] - [-MarkAsSpamSpfRecordHardFail <SpamFilteringOption>] - [-MarkAsSpamWebBugsInHtml <SpamFilteringOption>] - [-ModifySubjectValue <String>] - [-PhishSpamAction <SpamFilteringAction>] - [-PhishZapEnabled <Boolean> - [-QuarantineRetentionPeriod <Int32>] - [-RedirectToRecipients <MultiValuedProperty>] - [-RegionBlockList <MultiValuedProperty>] - [-SpamAction <SpamFilteringAction>] - [-SpamZapEnabled <Boolean>] - [-TestModeAction <SpamFilteringTestModeAction>] - [-TestModeBccToRecipients <MultiValuedProperty>] - [-WhatIf] - [-ZapEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://docs.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits). - -## EXAMPLES - -### Example 1 -```powershell -Set-HostedContentFilterPolicy -Identity "Contoso Executives" -HighConfidenceSpamAction Quarantine -SpamAction Quarantine -BulkThreshold 6 -``` - -This example modifies the spam filter policy named Contoso Executives with the following settings: - -- Quarantine messages when the spam filtering verdict is spam or high confidence spam. - -- BCL 6 triggers the action for a bulk email spam filtering verdict. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: HostedContentFilterPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AddXHeaderValue -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 - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -The maximum length is 255 characters, and the value can't contain spaces or colons (:). - -For example, if you enter the value `This-is-my-custom-header`, the X-header that's added to the message is `This-is-my-custom-header: This message appears to be spam.` - -If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`). - -Note that this setting is independent of the AddXHeader value of the TestModeAction parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowedSenderDomains -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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-safe-sender-lists-in-office-365). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowedSenders -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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-safe-sender-lists-in-office-365). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockedSenderDomains -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 9 (high confidence 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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-block-sender-lists-in-office-365?). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockedSenders -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 9 (high confidence 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 Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/create-block-sender-lists-in-office-365?). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BulkSpamAction -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. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In Exchange Online, the message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://docs.microsoft.com/microsoft-365/security/office-365-security/censure-that-spam-is-routed-to-each-user-s-junk-email-folder). - -- NoAction - -- Quarantine: Move the message to the quarantine. The quarantined message is available to the intended recipients and admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BulkThreshold -The BulkThreshold parameter specifies the BCL that triggers the BulkSpamAction on the message (greater than the specified value, not greater than or equal to). A valid value is an integer from 1 to 9, and the default value is 7. A higher value indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk compliant level (BCL) in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/bulk-complaint-level-values). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DownloadLink -The DownloadLink parameter shows or hides a link in end-user spam quarantine notifications to download the Junk Email Reporting Tool for Outlook. Valid values are: - -- $true: end-user spam quarantine notifications contain a link to download the Junk Email Reporting Tool for Outlook. - -- $false: end-user spam quarantine notifications don't contain the link. This is the default value. - -This parameter is only meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableEndUserSpamNotifications -The EnableEndUserSpamNotification parameter enables for disables sending end-user spam quarantine notifications. Valid values are: - -- $true: End-users periodically receive notifications when a messages that was supposed to be delivered to them was quarantined as spam. When you use this value, you can also use the EndUserSpamNotificationCustomSubject, EndUserSpamNotificationFrequency, and EndUserSpamNotificationLanguage parameters. - -- $false: end-user spam quarantine notifications are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableLanguageBlockList -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. - -- $false: Don't mark messages as spam solely based on their languages. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableRegionBlockList -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. - -- $false: Don't mark messages as spam solely based on the source country or region. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationCustomFromAddress -This parameter has been deprecated and is no longer used. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationCustomFromName -This parameter has been deprecated and is no longer used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationCustomSubject -The EndUserSpamNotificationCustomSubject parameter specifies a custom subject for end-user spam notification messages. If the value includes spaces, enclose the value in quotation marks ("). - -This parameter is meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationFrequency -The EndUserSpamNotificationFrequency parameter specifies the repeat interval in days that end-user spam quarantine notifications are sent. A valid value is an integer between 1 and 15. The default value is 3. - -This parameter is meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationLanguage -The EndUserSpamNotificationLanguage parameter specifies the language of end-user spam 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. - -The default value is Default, which means end-user spam quarantine notifications use the default language of the cloud-based organization. - -This parameter is meaningful only when the EnableEndUserSpamNotifications parameter value is $true. - -```yaml -Type: EsnLanguage -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserSpamNotificationLimit -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HighConfidencePhishAction -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: - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is only available to admins. - -```yaml -Type: PhishFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HighConfidenceSpamAction -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). - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In Exchange Online, the message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://docs.microsoft.com/microsoft-365/security/office-365-security/censure-that-spam-is-routed-to-each-user-s-junk-email-folder). - -- Quarantine: Move the message to the quarantine. The quarantined message is only available to admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithBizOrInfoUrls -**Note**: This setting is part of Advanced Spam Filtering (ASF) and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain links to .biz or .info domains are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithImageLinks -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain image links to remote websites are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithNumericIps -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain links to IP addresses are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncreaseScoreWithRedirectToOtherPort -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InlineSafetyTipsEnabled -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. - -- $false: Safety tips are disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LanguageBlockList -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 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. - -A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Note that not all possible language codes are available as input for this parameter. - -To enter multiple values and overwrite any existing entries, use the following syntax: \<value1\>,\<value2\>,...\<valueN\>. - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -To empty the list, use the value $null. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MakeDefault -The MakeDefault switch makes the specified spam filter policy the default spam filter policy. You don't have 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). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamBulkMail -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. - -- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. - -- Test: This value is available, but isn't used for this parameter. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamEmbedTagsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \<embed\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<embed\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamEmptyMessages -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamFormTagsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \<form\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<form\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamFramesInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \<frame\> or \<iframe\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<frame\> or \<iframe\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamFromAddressAuthFail -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamJavaScriptInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamNdrBackscatter -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamObjectTagsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \<object\> tags. Valid values are: - -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. - -- On: The setting is enabled. Messages that contain HTML \<object\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamSensitiveWordList -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamSpfRecordHardFail -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkAsSpamWebBugsInHtml -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you leave this setting turned off. - -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. - -- On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message. - -- Test: The action specified by the TestModeAction parameter is taken on the message. - -```yaml -Type: SpamFilteringOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModifySubjectValue -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 - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhishSpamAction -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. - -- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. The message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). - -- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients (as of April, 2020) and admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhishZapEnabled -The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing messages in delivered messages in Exchange Online mailboxes. Valid values are: - -- $true: Phish ZAP is enabled. This is the default value. The result depends on the spam filtering verdict action: MoveToJmf = Read and unread phish messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine: Read and unread phish messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - -- $false: Phish ZAP is disabled. - -**Note**: Use this parameter instead of the ZapEnabled parameter. The ZapEnabled parameter will be deprecated in a future release. During the transition, the value of this parameter is inherited from the ZapEnabled parameter. After you use the PhishZapEnabled parameter or the corresponding phish ZAP setting in the admin center on an existing spam filter policy, the ZapEnabled parameter value is ignored for phish ZAP. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QuarantineRetentionPeriod -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 - -- HighConfidencePhishAction - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -A valid value is an integer between 1 and 30. The default value is 30. - -After the time period expires, the message is deleted. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RedirectToRecipients -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 - -- HighConfidenceSpamAction - -- PhishSpamAction - -- SpamAction - -You can specify multiple email addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionBlockList -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. - -A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). - -To enter multiple values and overwrite any existing entries, use the following syntax: \<value1\>,\<value2\>,...\<valueN\>. - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -To empty the list, use the value $null. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpamAction -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). - -- Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - -- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - -- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In Exchange Online, the message is only moved if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see [Configure junk email settings on Exchange Online mailboxes in Office 365](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes). In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the k Email folder in hybrid environments](https://docs.microsoft.com/microsoft-365/security/office-365-security/censure-that-spam-is-routed-to-each-user-s-junk-email-folder). - -- Quarantine: Move the message to the quarantine. The quarantined message is available to the intended recipients and admins. - -- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. - -```yaml -Type: SpamFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpamZapEnabled -The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in delivered messages in Exchange Online mailboxes. Valid values are: - -- $true: Spam ZAP is enabled. This is the default value. The result depends on the spam filtering verdict action: 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. - -- $false: Spam ZAP is disabled. - -**Note**: Use this parameter instead of the ZapEnabled parameter. The ZapEnabled parameter will be deprecated in a future release. During the transition, the value of this parameter is inherited from the ZapEnabled parameter. After you use the SpamZapEnabled parameter or the corresponding spam ZAP setting in the admin center on an existing spam filter policy, the ZapEnabled parameter value is ignored for spam ZAP. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TestModeAction -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you don't use this setting. - -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. - -- AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. - -- BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter. - -```yaml -Type: SpamFilteringTestModeAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TestModeBccToRecipients -**Note**: This setting is part of ASF and will be deprecated. The functionality of this setting will be incorporated into other parts of the filtering stack. We recommend that you don't use this setting. - -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. - -This parameter is meaningful only when the value of the TestModeAction parameter is BccMessage, and when the value of one or more IncreaseScoreWith\* or MarkAsSpam\* parameters is Test. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ZapEnabled -**Note**: This parameter will be deprecated in a future release. Use the PhishZapEnabled and SpamZapEnabled parameters instead. After you use these parameters or configure the phish ZAP or spam ZAP settings in the admin center, the value of this parameter is ignored. - -The ZapEnabled parameter specifies whether to enable ZAP for phish and spam in Exchange Online mailboxes. Valid values are: - -- $true: ZAP for phish and spam is enabled. This is the default value. - -- $false: ZAP for phish and spam is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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 - -[Safe sender and blocked sender lists in Exchange Online](https://docs.microsoft.com/microsoft-365/security/office-365-security/safe-sender-and-blocked-sender-lists-faq) diff --git a/exchange/exchange-ps/exchange/antispam-antimalware/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/exchange/antispam-antimalware/Set-MailboxJunkEmailConfiguration.md deleted file mode 100644 index 2897f79b97..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-MailboxJunkEmailConfiguration.md +++ /dev/null @@ -1,343 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/set-mailboxjunkemailconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MailboxJunkEmailConfiguration -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-MailboxJunkEmailConfiguration - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-MailboxJunkEmailConfiguration cmdlet to configure the junk email settings on mailboxes. - -You can only use this cmdlet on a mailbox that's been opened in Outlook (in Cached Exchange mode) or Outlook on the web. If the mailbox hasn't been opened, you'll receive the error: The Junk Email configuration couldn't be set. The user needs to sign in to Outlook Web App before they can modify their Safe Senders and Recipients or Blocked Senders lists. If you want to suppress this error for bulk operations, you can add -ErrorAction SilentlyContinue to the end of the command. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MailboxJunkEmailConfiguration [-Identity] <MailboxIdParameter> - [-BlockedSendersAndDomains <MultiValuedProperty>] - [-Confirm] - [-ContactsTrusted <Boolean>] - [-DomainController <Fqdn>] - [-Enabled <Boolean>] - [-IgnoreDefaultScope] - [-TrustedListsOnly <Boolean>] - [-TrustedRecipientsAndDomains <MultiValuedProperty>] - [-TrustedSendersAndDomains <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet controls the following junk email settings on the mailbox: - -- Enable or disable the junk email rule: The junk email rule (a hidden Inbox rule named Junk E-mail Rule) controls the delivery of messages to the Junk Email folder or the Inbox based on the SCL Junk Email Folder threshold (for the organization or the mailbox) and the safelist collection on the mailbox. Users can enable or disable the junk email rule in their own mailbox by using Outlook on the web. - -- Configure the safelist collection: The safelist collection is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list. Users can configure the safelist collection on their own mailbox by using Microsoft Outlook or Outlook on the web. - -For more information, see [Configure Exchange antispam settings on mailboxes](https://docs.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MailboxJunkEmailConfiguration "David Pelton" -Enabled $false -``` - -This example disables the junk email rule configuration for the user named David Pelton. - -### Example 2 -```powershell -Set-MailboxJunkEmailConfiguration "Michele Martin" -TrustedSendersAndDomains @{Add="contoso.com","fabrikam.com"} -BlockedSendersAndDomains @{Add="jane@fourthcoffee.com"} -``` - -This example makes the following configuration changes to the safelist collection for the user named Michele Martin: - -- Adds contoso.com and fabrikam.com to the Safe Senders list without affecting other existing entries. - -- Adds jane@fourthcoffee.com to the Blocked senders list without affecting other existing entries. - -### Example 3 -```powershell -Get-MailboxJunkEmailConfiguration * | Where {$_.ContactsTrusted -eq $true} | Set-MailboxJunkEmailConfiguration -ContactsTrusted $false -``` - -This example identifies mailboxes where contacts are treated as trusted senders and then changes the junk email configuration to not treat contacts as trusted senders. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -BlockedSendersAndDomains -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContactsTrusted -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. - -- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -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. Exchange use the safelist collection of the mailbox (the Safe Senders list, Safe Recipients list, and Blocked Senders list), and the SCL Junk Email folder threshold (for the organization or the mailbox) to deliver messages to the Inbox or the Junk Email folder. - -- $false: The junk email rule is disabled in the mailbox. This value corresponds to the Outlook on the web setting: Don't move email to my Junk Email folder. Exchange doesn't use the safelist collection of the mailbox or the SCL Junk Email folder threshold to deliver messages to the Inbox or the Junk Email folder. - -You can view the status of the junk email rule by running either of the following commands to find the Enabled property value: - -- Get-MailboxJunkEmailConfiguration \<MailboxIdentity\> - -- Get-InboxRule "Junk E-mail Rule" -Mailbox \<MailboxIdentity\> -IncludeHidden - -You use the JunkEmailEnabled parameter on the Set-OwaMailboxPolicy or Set-OwaVirtualDirectory cmdlets to control the availability of the junk email settings in Outlook on the web. - -The state of the junk email rule on the mailbox doesn't affect the client-side junk email settings that are available in the Outlook Junk Email Filter. Even when the junk email rule is disabled in the mailbox, Outlook can still move messages to the Junk Email folder. For example, if Outlook determines the message is spam, or the sender is defined in the Blocked Senders list, Outlook can move the message to the Junk Email folder. For more information, see [Use Junk Email Filters to control which messages you see](https://go.microsoft.com/fwlink/p/?LinkID=797542). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedListsOnly -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. - -- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedRecipientsAndDomains -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedSendersAndDomains -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -To empty the list of email addresses and domains, use the value $null. - -Notes: - -- All email addresses in the global address list (GAL) are automatically considered as trusted senders, so you don't need to add them to the list. - -- You can't directly modify the Safe Recipients list by using this cmdlet. You use this parameter to modify the Safe Senders list, and the email addresses and domains are synchronized to the Safe Recipients list. - -- Safe domains aren't recognized in Exchange Online and Exchange Online Protection. For more information, see [KB3019657](https://go.microsoft.com/fwlink/p/?linkid=859868). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/antispam-antimalware/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilterPolicy.md deleted file mode 100644 index 1cbd37f226..0000000000 --- a/exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilterPolicy.md +++ /dev/null @@ -1,664 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/antispam-antimalware/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Set-MalwareFilterPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-MalwareFilterPolicy cmdlet to modify malware filter policies in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MalwareFilterPolicy [-Identity] <MalwareFilterPolicyIdParameter> - [-Action <MalwareFilteringAction>] - [-AdminDisplayName <String>] - [-BypassInboundMessages <Boolean>] - [-BypassOutboundMessages <Boolean>] - [-Confirm] - [-CustomAlertText <String>] - [-CustomExternalBody <String>] - [-CustomExternalSubject <String>] - [-CustomFromAddress <SmtpAddress>] - [-CustomFromName <String>] - [-CustomInternalBody <String>] - [-CustomInternalSubject <String>] - [-CustomNotifications <Boolean>] - [-DomainController <Fqdn>] - [-EnableExternalSenderAdminNotifications <Boolean>] - [-EnableExternalSenderNotifications <Boolean>] - [-EnableFileFilter <Boolean>] - [-EnableInternalSenderAdminNotifications <Boolean>] - [-EnableInternalSenderNotifications <Boolean>] - [-ExternalSenderAdminAddress <SmtpAddress>] - [-FileTypes <String[]>] - [-InternalSenderAdminAddress <SmtpAddress>] - [-MakeDefault] - [-WhatIf] - [-ZapEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MalwareFilterPolicy -Identity "Contoso Malware Filter Policy" -Action DeleteMessage -EnableInternalSenderAdminNotifications $true -InternalSenderAdminAddress admin@contoso.com -``` - -This example modifies the malware filter policy named Contoso Malware Filter Policy with the following settings: - -- Delete messages that contain malware. - -- Don't notify the message sender when malware is detected in the message. - -- Notify the administrator admin@contoso.com when malware is detected in a message from an internal sender. - -### Example 2 -```powershell -$FileTypesAdd = Get-MalwareFilterPolicy -Identity Default | select -Expand FileTypes; $FileTypesAdd += "com","bat"; Set-MalwareFilterPolicy -Identity Default -EnableFileFilter $true -FileTypes $FileTypesAdd -``` - -This example enables common attachment blocking in the malware filter policy named Default and adds the file types "com" and "bat" without affecting the other file type entries. - -### Example 3 -```powershell -$ft = Get-MalwareFilterPolicy -Identity Default -$a = [System.Collections.ArrayList]($ft.FileTypes) -$a -$a.RemoveAt(6); Set-MalwareFilterPolicy -Identity Default -FileTypes $a -``` - -This example modifies the malware filter policy named Default by removing an existing file type from common attachment blocking without affecting other file types that are already defined. - -The first three commands return the existing list of file types. The first file type in the list has the index number 0, the second has the index number 1, and so on. You use the index number to specify the file type that you want to remove. - -The last two commands remove the seventh file type that's displayed in the list. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Action -The Action parameter specifies the action to take when malware is detected in a message. Valid values are: - -- DeleteMessage: Handles the message without notifying the recipients. This is the default value. In Exchange Server, the message is deleted. In the cloud-based service, the message is quarantined. - -- DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. In the cloud-based service, the message with the original attachments is also quarantined. - -- DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. In the cloud-based service, the message with the original attachments is also quarantined. - -```yaml -Type: MalwareFilteringAction -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminDisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassInboundMessages -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: - -- $true: Malware filtering is disabled on inbound messages. - -- $false: Malware filtering is enabled on inbound messages. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassOutboundMessages -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: - -- $true: Malware filtering is disabled on outbound messages. - -- $false: Malware filtering is enabled on outbound messages. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAlertText -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 ("). - -This parameter is only meaningful when the Action parameter value is ReplaceWithCustomAlert. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomExternalBody -The CustomExternalBody parameter specifies the body of the custom notification message for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomExternalSubject -The CustomExternalSubject parameter specifies the subject of the custom notification message for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomFromAddress -The CustomFromAddress parameter specifies the From address of the custom notification message for malware detections in messages from internal or external senders. - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomFromName -The CustomFromName parameter specifies the From name of the custom notification message for malware detections in messages from internal or external senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableExternalSenderAdminNotifications - -- EnableExternalSenderNotifications - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomInternalBody -The CustomInternalBody parameter specifies the body of the custom notification message for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomInternalSubject -The CustomInternalSubject parameter specifies the subject of the custom notification message for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). - -This parameter is only meaningful when the CustomNotifications parameter value is $true, and at least one of the following parameter values is also $true: - -- EnableInternalSenderAdminNotifications - -- EnableInternalSenderNotifications - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomNotifications -The CustomNotifications parameter enables or disables custom notification messages for malware detections in messages from internal or external senders. Valid values are: - -- $true: When malware is detected in a message, a custom notification message is sent to the message sender. You specify the details of message using the CustomFromAddress, CustomFromName, CustomExternalSubject, CustomExternalBody, CustomInternalSubject and CustomInternalBody parameters. - -- $false: Custom notifications to the original message sender are disabled. This is the default value. Default notification messages are sent if the EnableExternalSenderNotifications and EnableInternalSenderNotifications parameters are set to $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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableExternalSenderAdminNotifications -The EnableExternalSenderAdminNotifications parameter enables or disables sending malware detection notification messages to an administrator for messages from external senders. Valid values are: - -- $true: When malware is detected in messages from external senders, send notification messages to the email address that's specified by the ExternalSenderAdminAddress parameter. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomExternalBody, and CustomExternalSubject parameters. - -- $false: When malware is detected in messages from external senders, don't send administrator notifications. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableExternalSenderNotifications -The EnableExternalSenderNotifications parameter enables or disables notification messages for malware detections in messages from external senders. Valid values are: - -- $true: When malware is detected in a message from an external sender, send them a notification message. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomExternalBody, and CustomExternalSubject parameters. - -- $false: Don't send malware detection notification messages to external message senders. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableFileFilter -The EnableFileFilter parameter enables or disables common attachment blocking (also known as the Common Attachment Types Filter). Valid values are: - -- $true: Common attachment blocking is enabled. The file types are defined by the FileTypes parameter. - -- $false: Common attachment blocking is disabled. This is the default value. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableInternalSenderAdminNotifications -The EnableInternalSenderAdminNotifications parameter enables or disables sending malware detection notification messages to an administrator for messages from internal senders. Valid values are: - -- $true: When malware is detected in messages from internal senders, send notification messages to the email address that's specified by the InternalSenderAdminAddress parameter. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomInternalBody, and CustomInternalSubject parameters. - -- $false: When malware is detected in messages from internal senders, don't send administrator notifications. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableInternalSenderNotifications -The EnableInternalSenderNotifications parameter enables or disables notification messages for malware detections in messages from internal senders. Valid values are: - -- $true: When malware is detected in a message from an internal sender, send them a notification message. You can customize the notification message using the CustomFromAddress, CustomFromName, CustomInternalBody, and CustomInternalSubject parameters. - -- $false: Don't send malware detection notification messages to internal message senders. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalSenderAdminAddress -The ExternalSenderAdminAddress parameter specifies the email address of the administrator who will receive notification messages for malware detections in messages from external senders. - -This parameter is only meaningful if the EnableExternalSenderAdminNotifications parameter is set to $true. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileTypes -The FileTypes parameter specifies the file types that are automatically blocked by common attachment blocking (also known as the Common Attachment Types Filter), regardless of content. The default values are: - -- .ace - -- .ani - -- .app - -- .docm - -- .exe - -- .jar - -- .reg - -- .scr - -- .vbe - -- .vbs - -You enable or disable common attachment blocking by using the EnableFileFilter parameter. - -Common attachment blocking uses best effort true-typing to detect the file type regardless of the file name extension. If true-typing fails or isn't supported for the specified file type, then extension matching is used. For example, .ps1 files are Windows PowerShell scripts, but their true type is text. - -To replace the existing list of file types with the values you specify, use the syntax \<FileType1\>,\<FileType2\>,...\<FileTypeN\>. To preserve existing values, be sure to include the file types that you want to keep along with the new values that you want to add. - -To add or remove file types without affecting the other file type entries, see the Examples section. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalSenderAdminAddress -The InternalSenderAdminAddress parameter specifies the email address of the administrator who will receive notification messages for malware detections in messages from internal senders. - -This parameter is only meaningful if the EnableInternalSenderAdminNotifications parameter value is $true. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MakeDefault -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. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ZapEnabled -The ZapEnabled parameter enables or disables zero-hour auto purge (ZAP) for malware. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: - -- $true: ZAP for malware is enabled. This is the default value. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined. - -- $false: ZAP for malware is disabled. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access-servers/Get-MapiVirtualDirectory.md b/exchange/exchange-ps/exchange/client-access-servers/Get-MapiVirtualDirectory.md deleted file mode 100644 index 587f6be23e..0000000000 --- a/exchange/exchange-ps/exchange/client-access-servers/Get-MapiVirtualDirectory.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/get-mapivirtualdirectory -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Get-MapiVirtualDirectory -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Get-MapiVirtualDirectory - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Get-MapiVirtualDirectory cmdlet to view Message Application Programming Interface (MAPI) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Server -``` -Get-MapiVirtualDirectory -Server <ServerIdParameter> - [-ADPropertiesOnly] - [-DomainController <Fqdn>] [<CommonParameters>] -``` - -### Identity -``` -Get-MapiVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>] - [-ADPropertiesOnly] - [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MapiVirtualDirectory -Server ContosoMail -``` - -This example returns a summary list of the MAPI virtual directories on the server named ContosoMail. - -### Example 2 -```powershell -Get-MapiVirtualDirectory -Identity "ContosoMail\mapi (Default Web Site)" | Format-List; Get-MapiVirtualDirectory "ContosoMail\mapi (Default Web Site)" | Format-List; Get-MapiVirtualDirectory ContosoMai\mapi* | Format-List -``` - -These examples return detailed information for the MAPI virtual directory named "mapi (Default Web Site)" on the server named ContosoMail. All three commands do the same thing. - -### Example 3 -```powershell -Get-MapiVirtualDirectory -``` - -This example returns a summary list of all MAPI virtual directories in the client access services on all Mailbox servers in the organization. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -The Name value uses the syntax "\<VirtualDirectoryName\> (\<WebsiteName\>)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \<VirtualDirectoryName\>\*. - -You can't use the Identity and Server parameters in the same command. - -```yaml -Type: VirtualDirectoryIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Server -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 - -- FQDN - -- Distinguished name (DN) - -- ExchangeLegacyDN - -You can't use the Server and Identity parameters in the same command. - -```yaml -Type: ServerIdParameter -Parameter Sets: Server -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ADPropertiesOnly -The ADPropertiesOnly switch specifies whether to return only the properties about the virtual directory stored in Active Directory. The properties stored in the Internet Information Services (IIS) metabase aren't returned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access-servers/New-PowerShellVirtualDirectory.md b/exchange/exchange-ps/exchange/client-access-servers/New-PowerShellVirtualDirectory.md deleted file mode 100644 index e8d8f1275f..0000000000 --- a/exchange/exchange-ps/exchange/client-access-servers/New-PowerShellVirtualDirectory.md +++ /dev/null @@ -1,256 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/new-powershellvirtualdirectory -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-PowerShellVirtualDirectory -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# New-PowerShellVirtualDirectory - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the New-PowerShellVirtualDirectory cmdlet to create Windows PowerShell virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-PowerShellVirtualDirectory [-Name] <String> [-BasicAuthentication <Boolean>] [-Confirm] - [-DomainController <Fqdn>] [-ExternalUrl <Uri>] [-InternalUrl <Uri>] [-RequireSSL <Boolean>] - [-Role <VirtualDirectoryRole>] [-Server <ServerIdParameter>] [-WhatIf] - [-WindowsAuthentication <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -Although it's possible to create a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-PowerShellVirtualDirectory -Name "Contoso Certificates Required" -BasicAuthentication $false -WindowsAuthentication $false -CertificateAuthentication $true -``` - -This example creates a Windows PowerShell virtual directory and configures it to accept only certificate authentication. - -## PARAMETERS - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BasicAuthentication -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalUrl -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalUrl -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireSSL -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Role -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. - -- Mailbox: Configure the virtual directory for the backend services on the Mailbox server. - -Client connections are proxied from the Client Access services to the backend services on local or remote Mailbox servers. Clients don't connect directly to the backend services. - -```yaml -Type: VirtualDirectoryRole -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Server -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 - -- FQDN - -- Distinguished name (DN) - -- ExchangeLegacyDN - -```yaml -Type: ServerIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WindowsAuthentication -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access-servers/Set-PowerShellVirtualDirectory.md b/exchange/exchange-ps/exchange/client-access-servers/Set-PowerShellVirtualDirectory.md deleted file mode 100644 index e6229f5b9d..0000000000 --- a/exchange/exchange-ps/exchange/client-access-servers/Set-PowerShellVirtualDirectory.md +++ /dev/null @@ -1,249 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access-servers/set-powershellvirtualdirectory -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-PowerShellVirtualDirectory -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Set-PowerShellVirtualDirectory - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Set-PowerShellVirtualDirectory cmdlet to modify existing Windows PowerShell virtual directories that are used in Internet Information Services (IIS) on Exchange servers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-PowerShellVirtualDirectory [-Identity] <VirtualDirectoryIdParameter> - [-BasicAuthentication <Boolean>] - [-CertificateAuthentication <Boolean>] - [-Confirm] - [-DomainController <Fqdn>] - [-ExternalUrl <Uri>] - [-InternalUrl <Uri>] - [-RequireSSL <Boolean>] - [-WhatIf] - [-WindowsAuthentication <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -Although it's possible to modify a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-PowerShellVirtualDirectory "Contoso (default Web site)" -ExternalUrl "https://www.contoso.com/powershell" -``` - -This example modifies the external URL of the Contoso Windows PowerShell virtual directory. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -The Name value uses the syntax "\<VirtualDirectoryName\> (\<WebsiteName\>)" from the properties of the virtual directory. You can specify the wildcard character (\*) instead of the default website by using the syntax \<VirtualDirectoryName\>\*. - -```yaml -Type: VirtualDirectoryIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -BasicAuthentication -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. - -- $false: Basic authentication is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CertificateAuthentication -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalUrl -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalUrl -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireSSL -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WindowsAuthentication -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. - -- $false: Integrated Windows authentication is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Get-CASMailboxPlan.md b/exchange/exchange-ps/exchange/client-access/Get-CASMailboxPlan.md deleted file mode 100644 index e884e54132..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Get-CASMailboxPlan.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-casmailboxplan -applicable: Exchange Online -title: Get-CASMailboxPlan -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CASMailboxPlan - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-CASMailboxPlan cmdlet to view Client Access services (CAS) mailbox plans in cloud-based organizations. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CASMailboxPlan [[-Identity] <MailboxPlanIdParameter>] - [-Credential <PSCredential>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -## DESCRIPTION -A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CASMailboxPlan | Format-Table -Auto DisplayName,ActiveSyncEnabled,ImapEnabled,PopEnabled,OwaMailboxPolicy -``` - -This example returns a summary list of all CAS mailbox plans in the organization. - -### Example 2 -```powershell -Get-CASMailboxPlan -Identity ExchangeOnlineEnterprise -``` - -This example returns detailed information about the specified CAS mailbox plan. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -The display name and name of the CAS mailbox plan is the same as the corresponding mailbox plan (for example, ExchangeOnlineEnterprise and ExchangeOnlineEnterprise-\<GUID\>). - -```yaml -Type: MailboxPlanIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following attributes: - -- DisplayName - -- Name - -The results are sorted in ascending order. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Get-ClientAccessRule.md b/exchange/exchange-ps/exchange/client-access/Get-ClientAccessRule.md deleted file mode 100644 index 060a08d27b..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Get-ClientAccessRule.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/get-clientaccessrule -applicable: Exchange Server 2019, Exchange Online -title: Get-ClientAccessRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# Get-ClientAccessRule - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-ClientAccessRule cmdlet to view client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ClientAccessRule [[-Identity] <ClientAccessRuleIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ClientAccessRule -``` - -This example shows a summary list of all client access rules. - -### Example 2 -```powershell -Get-ClientAccessRule "Block Client Connections from 192.168.1.0/24" | Format-List -``` - -This example retrieves details about the client access rule named "Block Client Connections from 192.168.1.0/24". - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ClientAccessRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Get-MailboxMessageConfiguration.md b/exchange/exchange-ps/exchange/client-access/Get-MailboxMessageConfiguration.md deleted file mode 100644 index a1cedab2f1..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Get-MailboxMessageConfiguration.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MailboxMessageConfiguration - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailboxMessageConfiguration cmdlet to view the Outlook on the web settings that are applied to specific mailboxes. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxMessageConfiguration [-Identity] <MailboxIdParameter> [-Credential <PSCredential>] - [-DomainController <Fqdn>] [-ReadFromDomainController] [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-MailboxMessageConfiguration cmdlet shows Outlook on the web settings for the specified mailbox. These settings are not used in Microsoft Outlook, Microsoft Exchange ActiveSync, or other email clients. These settings are applied in Outlook on the web only. Settings that contain the word Mobile are applied in Microsoft Outlook on the web for devices only. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxMessageConfiguration tony@contoso.com -``` - -This example returns the Outlook on the web settings for Tony's mailbox. - -### Example 2 -```powershell -Get-MailboxMessageConfiguration tony@contoso.com -DomainController DC1 -``` - -This example returns the Outlook on the web settings for Tony's mailbox and specifies the domain controller that's used to get those settings. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -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 -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Get-MailboxRegionalConfiguration.md b/exchange/exchange-ps/exchange/client-access/Get-MailboxRegionalConfiguration.md deleted file mode 100644 index b0bcc5d189..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Get-MailboxRegionalConfiguration.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MailboxRegionalConfiguration - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailboxRegionalConfiguration cmdlet to view the regional settings of a mailbox. You can view the date format, time format, time zone, and language of the mailbox. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxRegionalConfiguration [-Identity] <MailboxIdParameter> [-DomainController <Fqdn>] - [-VerifyDefaultFolderNameLanguage] [<CommonParameters>] -``` - -## DESCRIPTION -To modify the regional settings of a mailbox, use the [Set-MailboxRegionalConfiguration](https://docs.microsoft.com/powershell/module/exchange/client-access/set-mailboxregionalconfiguration) cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxRegionalConfiguration -Identity "Marcelo Teixeira" -``` - -This example returns the regional settings for Marcelo Teixeira's mailbox. - -### Example 2 -```powershell -Get-MailboxRegionalConfiguration -Identity "Ella Lack" -DomainController dc01.contoso.com -``` - -In on-premises Exchange, this example returns the regional settings for Ella Lack's mailbox by using the specified domain controller. - -### Example 3 -```powershell -Get-MailboxRegionalConfiguration -Identity "Alice Jakobsen" -VerifyDefaultFolderNameLanguage | Format-List -``` - -This example returns the regional settings for Alice Jakobsen's mailbox and also indicates whether the default folder names of the mailbox are localized in the locale that's specified for the mailbox. The important properties are Language and DefaultFolderNameMatchingUserLanguage. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VerifyDefaultFolderNameLanguage -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: - -- Get-MailboxRegionalConfiguration -Identity \<MailboxIdentity\> -VerifyDefaultFolderNameLanguage | Format-List - -Or - -- Get-MailboxRegionalConfiguration -Identity \<MailboxIdentity\> -VerifyDefaultFolderNameLanguage | Format-Table Language,DefaultFolderNameMatchingUserLanguage - -If you view the DefaultFolderNameMatchingUserLanguage property without using the VerifyDefaultFolderNameLanguage switch, the value is always $false, even if the default folder names are localized in the language that's specified for the mailbox. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/New-ClientAccessRule.md b/exchange/exchange-ps/exchange/client-access/New-ClientAccessRule.md deleted file mode 100644 index 8d9a031c05..0000000000 --- a/exchange/exchange-ps/exchange/client-access/New-ClientAccessRule.md +++ /dev/null @@ -1,532 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/new-clientaccessrule -applicable: Exchange Server 2019, Exchange Online -title: New-ClientAccessRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# New-ClientAccessRule - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-ClientAccessRule cmdlet to create client access rules. Client access rules help you control access to your organization based on the properties of the connection. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ClientAccessRule [-Name] <String> -Action <ClientAccessRulesAction> - [-AnyOfAuthenticationTypes <MultiValuedProperty>] - [-AnyOfClientIPAddressesOrRanges <MultiValuedProperty>] - [-AnyOfProtocols <MultiValuedProperty>] - [-Confirm] - [-DomainController <Fqdn>] - [-Enabled <Boolean>] - [-ExceptAnyOfAuthenticationTypes <MultiValuedProperty>] - [-ExceptAnyOfClientIPAddressesOrRanges <MultiValuedProperty>] - [-ExceptAnyOfProtocols <MultiValuedProperty>] - [-ExceptUsernameMatchesAnyOfPatterns <MultiValuedProperty>] - [-Priority <Int32>] [-Scope <ClientAccessRulesScope>] - [-UsernameMatchesAnyOfPatterns <MultiValuedProperty>] - [-UserRecipientFilter <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. - -Note: Currently, not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list: - -- OutlookWebApp: BasicAuthentication and AdfsAuthentication. - -- ExchangeAdminCenter: BasicAuthentication and AdfsAuthentication. - -- RemotePowerShell: BasicAuthentication and NonBasicAuthentication. - -- ExchangeActiveSync: BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-ClientAccessRule -Name AllowRemotePS -Action Allow -AnyOfProtocols RemotePowerShell -Priority 1 -``` - -This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you'll lose the ability to fix the rules yourself (you'll need to call Microsoft Customer Service and Support). - -### Example 2 -```powershell -New-ClientAccessRule -Name "Block ActiveSync" -Action DenyAccess -AnyOfProtocols ExchangeActiveSync -ExceptAnyOfClientIPAddressesOrRanges 192.168.10.1/24 -``` - -This example creates a new client access rule named Block ActiveSync that blocks access for Exchange ActiveSync clients, except for clients in the IP address range 192.168.10.1/24. - -## PARAMETERS - -### -Action -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 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies a unique name for the client access rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfAuthenticationTypes -This parameter is available 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. - -Valid values for this parameter are: - -- AdfsAuthentication - -- BasicAuthentication - -- CertificateBasedAuthentication - -- NonBasicAuthentication - -- OAuthAuthentication - -You can enter multiple values separated by commas. Don't use quotation marks. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfClientIPAddressesOrRanges -The AnyOfClientIPAddressesOrRanges parameter specifies a condition for the client access rule that's based on the client's IP address. Valid values for this parameter are: - -- A single IP address: For example, 192.168.1.1. - -- An IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.3.1/24. - -You can enter multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfProtocols -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: - -- ExchangeActiveSync - -- ExchangeAdminCenter - -- ExchangeWebServices - -- IMAP4 - -- OfflineAddressBook - -- OutlookAnywhere - -- OutlookWebApp - -- POP3 - -- PowerShellWebServices - -- RemotePowerShell - -- REST - -- UniversalOutlook (Mail and Calendar app) - -**Note**: In Exchange 2019, the only supported values are ExchangeAdminCenter and RemotePowerShell. - -You can enter multiple values separated by commas. Don't use quotation marks. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -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 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptAnyOfAuthenticationTypes -This parameter is available 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. - -Valid values for this parameter are: - -- AdfsAuthentication - -- BasicAuthentication - -- CertificateBasedAuthentication - -- NonBasicAuthentication - -- OAuthAuthentication - -You can enter multiple values separated by commas. Don't use quotation marks. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptAnyOfClientIPAddressesOrRanges -The ExceptAnyOfClientIPAddressesOrRanges parameter specifies an exception for the client access rule that's based on the client's IP address. Valid values for this parameter are: - -- A single IP address: For example, 192.168.1.1. - -- An IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.3.1/24. - -You can enter multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptAnyOfProtocols -This parameter is available 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. - -Valid values for this parameter are: - -- ExchangeActiveSync - -- ExchangeAdminCenter - -- ExchangeWebServices - -- IMAP4 - -- OfflineAddressBook - -- OutlookAnywhere - -- OutlookWebApp - -- POP3 - -- PowerShellWebServices - -- RemotePowerShell - -- REST - -- UniversalOutlook (Mail and Calendar app) - -You can enter multiple values separated by commas. Don't use quotation marks. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptUsernameMatchesAnyOfPatterns -This parameter is available 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 \<Domain\>\\\<UserName\> (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. - -You can enter multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new rule (the 9th rule) are from 0 through 8. - -- The default value for a new rule (the 9th rule) is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -The Scope parameter specifies the scope of the client access rule. Valid values are: - -- Users: The rule only applies to end-user connections. - -- All: The rule applies to all connections (end-users and middle-tier apps). - -```yaml -Type: ClientAccessRulesScope -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsernameMatchesAnyOfPatterns -This parameter is available 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 \<Domain\>\\\<UserName\> (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. - -You can enter multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: True -``` - -### -UserRecipientFilter -This parameter is available 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. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"City -eq 'Redmond'"`). - -- 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. - -- Property is a filterable property. For filterable recipient properties, see - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -The filterable properties that you can use with this parameter are: - -- City - -- Company - -- CountryOrRegion - -- CustomAttribute1 to CustomAttribute15 - -- Department - -- Office - -- PostalCode - -- StateOrProvince - -- StreetAddress - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Remove-ClientAccessRule.md b/exchange/exchange-ps/exchange/client-access/Remove-ClientAccessRule.md deleted file mode 100644 index b36e6007c8..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Remove-ClientAccessRule.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/remove-clientaccessrule -applicable: Exchange Server 2019, Exchange Online -title: Remove-ClientAccessRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# Remove-ClientAccessRule - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-ClientAccessRule cmdlet to remove client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ClientAccessRule [-Identity] <ClientAccessRuleIdParameter> - [-Confirm] - [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ClientAccessRule "Block Client Connections from 192.168.1.0/24" -``` - -This example removes the existing client access rule named "Block Connections from 192.168.1.0/24". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ClientAccessRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Set-CASMailbox.md b/exchange/exchange-ps/exchange/client-access/Set-CASMailbox.md deleted file mode 100644 index 70881af31e..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Set-CASMailbox.md +++ /dev/null @@ -1,1335 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-casmailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-CASMailbox -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-CASMailbox - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-CASMailbox cmdlet to configure client access settings on a mailbox. For example, you can configure settings for Exchange ActiveSync, Outlook, Outlook on the web, POP3, and IMAP4. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-CASMailbox [-Identity] <MailboxIdParameter> - [-ActiveSyncAllowedDeviceIDs <MultiValuedProperty>] - [-ActiveSyncBlockedDeviceIDs <MultiValuedProperty>] - [-ActiveSyncDebugLogging <Boolean>] - [-ActiveSyncEnabled <Boolean>] - [-ActiveSyncMailboxPolicy <MailboxPolicyIdParameter>] - [-ActiveSyncSuppressReadReceipt <Boolean>] - [-Confirm] - [-DisplayName <String>] - [-DomainController <Fqdn>] - [-ECPEnabled <Boolean>] - [-EmailAddresses <ProxyAddressCollection>] - [-EmwsEnabled <Boolean>] - [-EwsAllowEntourage <Boolean>] - [-EwsAllowList <MultiValuedProperty>] - [-EwsAllowMacOutlook <Boolean>] - [-EwsAllowOutlook <Boolean>] - [-EwsApplicationAccessPolicy <EwsApplicationAccessPolicy>] - [-EwsBlockList <MultiValuedProperty>] - [-EwsEnabled <Boolean>] - [-HasActiveSyncDevicePartnership <Boolean>] - [-IgnoreDefaultScope] - [-ImapEnabled <Boolean>] - [-ImapEnableExactRFC822Size <Boolean>] - [-ImapMessagesRetrievalMimeFormat <MimeTextFormat>] - [-ImapForceICalForCalendarRetrievalOption <Boolean>] - [-ImapSuppressReadReceipt <Boolean>] - [-ImapUseProtocolDefaults <Boolean>] - [-IsOptimizedForAccessibility <Boolean>] - [-MAPIBlockOutlookExternalConnectivity <Boolean>] - [-MAPIBlockOutlookNonCachedMode <Boolean>] - [-MAPIBlockOutlookRpcHttp <Boolean>] - [-MAPIBlockOutlookVersions <String>] - [-MAPIEnabled <Boolean>] - [-MapiHttpEnabled <Boolean>] - [-Name <String>] - [-OutlookMobileEnabled <Boolean>] - [-OWAEnabled <Boolean>] - [-OWAforDevicesEnabled <Boolean>] - [-OwaMailboxPolicy <MailboxPolicyIdParameter>] - [-PopEnabled <Boolean>] - [-PopEnableExactRFC822Size <Boolean>] - [-PopForceICalForCalendarRetrievalOption <Boolean>] - [-PopMessagesRetrievalMimeFormat <MimeTextFormat>] - [-PopSuppressReadReceipt <Boolean>] - [-PopUseProtocolDefaults <Boolean>] - [-PrimarySmtpAddress <SmtpAddress>] - [-PublicFolderClientAccess <Boolean>] - [-ResetAutoBlockedDevices] - [-SamAccountName <String>] - [-ShowGalAsDefaultView <Boolean>] - [-SmtpClientAuthenticationDisabled <Boolean>] - [-UniversalOutlookEnabled <Boolean>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-CASMailbox adam@contoso.com -OWAEnabled $false -PopEnabled $false -``` - -This example disables Outlook on the web and POP3 access for the user adam@contoso.com. - -### Example 2 -```powershell -Set-CASMailbox adam@contoso.com -ActiveSyncDebugLogging $true -ActiveSyncMailboxPolicy Management -``` - -This example enables Exchange ActiveSync debug logging and specifies the Exchange ActiveSync mailbox policy named Management for the user adam@contoso.com. - -### Example 3 -```powershell -Set-CASMailbox tony@contoso.com -DisplayName "Tony Smith" -MAPIBlockOutlookRpcHttp $true -``` - -This example sets the display name and disables Outlook Anywhere access for the user tony@contoso.com. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to configure. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ActiveSyncAllowedDeviceIDs -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -To clear the list of device IDs, use the value $null for this parameter. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActiveSyncBlockedDeviceIDs -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -To clear the list of device IDs, use the value $null for this parameter. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActiveSyncDebugLogging -The ActiveSyncDebugLogging parameter enables or disables Exchange ActiveSync debug logging for the mailbox. Valid input for this parameter is $true or $false. The default value is $false. - -This parameter is primarily for troubleshooting and will revert to $false in 48 hours for Exchange Online, and in 72 hours for Exchange Server. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActiveSyncEnabled -The ActiveSyncEnabled parameter enables or disables Exchange ActiveSync for the mailbox. Valid input for this parameter is $true or $false. The default value is $true. When you set this parameter to $false, the other Exchange ActiveSync settings in this cmdlet are ignored. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActiveSyncMailboxPolicy -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 - -- Distinguished name (DN) - -- GUID - -The name of the default Exchange ActiveSync mailbox policy is Default. However, to reset this parameter back to the default value, use the value $null. The value $null also changes the value of the ActiveSyncMailboxPolicyIsDefaulted property to True. If you specify the value Default for the ActiveSyncMailboxPolicy parameter, the value of the ActiveSyncMailboxPolicyIsDefaulted property remains False. - -```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: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActiveSyncSuppressReadReceipt -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. - -- $false: A read receipt is automatically returned when the user opens a message sent with a read receipt request. This is the default value. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -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 ("). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ECPEnabled -This parameter is available only in on-premises Exchange. - -The ECPEnabled parameter enables or disables access to the Exchange admin center (EAC) for the specified user. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -This parameter is available only in on-premises Exchange. - -The EmailAddresses parameter specifies all the 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://docs.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. Some examples of valid values include: - -- SMTP: The primary SMTP address. You can use this value only once in a command. - -- smtp: Other SMTP email addresses. - -- X400: X.400 addresses in on-premises Exchange. - -- X500: X.500 addresses in on-premises Exchange. - -If you don't include a \<Type\> value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. - -To specify the primary SMTP email address, you can use any of the following methods: - -- Use the \<Type\> value SMTP on the address. - -- The first email address when you don't use any \<Type\> values, or when you use multiple \<Type\> values of smtp. - -- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. - -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",..."\<Type\>:\<emailaddressN\>". - -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",...; Remove="\<Type\>:\<emailaddress2\>","\<Type\>:\<emailaddress2\>",...}. - -```yaml -Type: ProxyAddressCollection -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmwsEnabled -This parameter is available or functional only in Exchange Server 2010. - -The EmwsEnabled parameter specifies whether the Exchange Management Web Service is enabled on this Client Access server. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowEntourage -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). - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowList -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -This parameter is meaningful only when the EwsEnabled parameter is set to $true, and the EwsApplicationAccessPolicy parameter is set to EnforceAllowList. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowMacOutlook -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 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowOutlook -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsApplicationAccessPolicy -The EwsApplicationAccessPolicy parameter controls access to the mailbox by using Exchange Web Services applications. - -Valid values for this parameter are: - -- EnforceAllowList: Only applications specified in the EwsAllowList parameter are allowed to access the mailbox. - -- EnforceBlockList: Applications specified in the EwsBlockList parameter aren't allowed to access the mailbox, but any other applications can access the mailbox. - -This parameter doesn't affect access to the mailbox by using Entourage, Outlook for Mac, and Outlook. Access to the mailbox by using these clients is controlled by the EwsAllowEntourage, EwsAllowMacOutlook and EwsAllowOutlook parameters. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsBlockList -The EwsBlockList parameter specifies the Exchange Web Services applications (user agent strings) that aren't allowed to access the mailbox by 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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -This parameter is meaningful only when the EwsEnabled parameter is set to $true, and the EwsApplicationAccessPolicy parameter is set to EnforceBlockList. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsEnabled -The EwsEnabled parameter enables or disables access to the mailbox by using Exchange Web Services clients. - -Valid input for this parameter is $true or $false. The default value is $true. Note that when you set this parameter to $false, the other Exchange Web Services settings in this cmdlet are ignored. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HasActiveSyncDevicePartnership -This parameter is available or functional only in Exchange Server 2010. - -The HasActiveSyncDevicePartnership parameter specifies whether the mailbox has an ActiveSync device partnership established. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImapEnabled -The ImapEnabled parameter enables or disables access to the mailbox by using IMAP4 clients. - -Valid input for this parameter is $true or $false. The default value is $true. Note that when you set this parameter to $false, the other IMAP4 settings in this cmdlet are ignored. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImapEnableExactRFC822Size -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 for this parameter are: - -- $true: Calculate the exact message size. - -- $false: Use an estimated message size. - -The default value is $false. - -We don't recommend changing this value unless you determine that the default setting causes problems for IMAP4 clients. To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImapForceICalForCalendarRetrievalOption -The ImapForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to IMAP4 clients that access the mailbox. - -Valid values for this parameter are: - -- $true: All meeting requests are in the iCal format. - -- $false: All meeting requests appear as Outlook on the web links. - -The default value is $false. - -To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImapMessagesRetrievalMimeFormat -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 - -- 1: HtmlOnly - -- 2: HtmlAndTextAlternative - -- 3: TextEnrichedOnly - -- 4: TextEnrichedAndTextAlternative - -- 5: BestBodyFormat - -- 6: Tnef - -The default value is BestBodyFormat. - -To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImapSuppressReadReceipt -The ImapSuppressReadReceipt parameter controls the behavior of read receipts for IMAP4 clients that access the mailbox. - -Valid values for this parameter are: - -- $true: The user receives a read receipt when the recipient opens the message. - -- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. - -The default value is $false. - -To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImapUseProtocolDefaults -The ImapUseProtocolDefaults parameter specifies whether to use the IMAP4 protocol defaults for the mailbox. Valid input for this parameter is $true or $false. The default value is $true. - -You need to set the ImapUseProtocolDefaults parameter to $false when you use any of the following IMAP4 parameters: - -- ImapEnableExactRFC822Size - -- ImapForceICalForCalendarRetrievalOption - -- ImapMessagesRetrievalMimeFormat - -- ImapSuppressReadReceipt - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsOptimizedForAccessibility -This parameter is available 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: - -- $true: The mailbox is configured to use the light version of Outlook on the web. - -- $false: The mailbox isn't configured to use the light version of Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MAPIBlockOutlookNonCachedMode -This parameter is available only in on-premises Exchange. - -The MAPIBlockOutlookNonCachedMode parameter controls access to the mailbox by using Outlook in online or offline mode. - -Valid values for this parameter are: - -- $true: Only Outlook clients that are configured to use Cached Exchange Mode (offline mode) are allowed to access the mailbox. - -- $false: The state of the Cached Exchange Mode setting isn't checked before Outlook clients are allowed to access the mailbox (online mode and offline mode are allowed). - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MAPIBlockOutlookExternalConnectivity -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: - -- $true: External Outlook clients can't use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox. - -- $false: External Outlook clients can use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox. - -Note: If your organization uses the same Autodiscover URL values for internal and external clients, setting this parameter to $true won't block access for external clients. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MAPIBlockOutlookRpcHttp -This parameter is available only in on-premises Exchange. - -The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox in Outlook by using Outlook Anywhere. Valid values are: - -- $true: Access to the mailbox by using Outlook Anywhere is disabled. - -- $false: Access to the mailbox by using Outlook Anywhere is enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MAPIBlockOutlookVersions -This parameter is available only in on-premises Exchange. - -The MAPIBlockOutlookVersions parameter blocks access to the mailbox for specific versions of Outlook. - -For example, if you specify the value 15.0.4569.1503, only Outlook 2013 Service Pack 1 (SP1) or later clients are allowed to access the mailbox. Earlier versions of Outlook are blocked. - -The default value is blank. To reset this parameter, use the value $null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MAPIEnabled -The MAPIEnabled parameter enables or disables access to the mailbox by using MAPI clients (for example, Outlook). - -Valid input for this parameter is $true or $false. The default value is $true. Note that when you set this parameter to $false, the other MAPI settings in this cmdlet are ignored. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MapiHttpEnabled -This parameter is available only in on-premises Exchange. - -The MapiHttpEnabled parameter enables or disables access to the mailbox in Outlook by using MAPI over HTTP. Valid values are: - -- $true: Access to the mailbox by using MAPI over HTTP is enabled. - -- $false: Access to the mailbox by using MAPI over HTTP is disabled. - -- $null (blank): The setting isn't configured. The mailbox uses the organization setting for MAPI over HTTP (the MapiHttpEnabled parameter on the Set-OrganizationConfig cmdlet). This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 ("). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutlookMobileEnabled -This parameter is available only in the cloud-based service. - -The OutlookMobileEnabled parameter enables or disables access to the mailbox by using Outlook for iOS and Android. Valid values are: - -- $true: Access to the mailbox using Outlook for iOS and Android is enabled. This is the default value. - -- $false: Access to the mailbox using Outlook for iOS and Android is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OWAEnabled -The OWAEnabled parameter enables or disables access to the mailbox by using Outlook on the web. - -Valid input for this parameter is $true or $false. The default value is $true. Note that when you set this parameter to $false, the other Outlook on the web settings in this cmdlet are ignored. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OWAforDevicesEnabled -The OWAforDevicesEnabled parameter enables or disables access to the mailbox by using Outlook on the web for devices. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OwaMailboxPolicy -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 - -- Distinguished name (DN) - -- GUID - -The name of the default Outlook on the web mailbox policy is Default. - -```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: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopEnabled -The PopEnabled parameter enables or disables access to the mailbox by using POP3 clients. - -Valid input for this parameter is $true or $false. The default value is $true. Note that when you set this parameter to $false, the other POP3 settings in this cmdlet are ignored. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopEnableExactRFC822Size -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 for this parameter are: - -- $true: Calculate the exact message size. - -- $false: Use an estimated message size. - -The default value is $false. - -We don't recommend changing this value unless you determine that the default setting causes problems for POP3 clients. To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopForceICalForCalendarRetrievalOption -The PopForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to POP3 clients that access the mailbox. - -Valid values for this parameter are: - -- $true: All meeting requests are in the iCal format. - -- $false: All meeting requests appear as Outlook on the web links. - -The default value is $false. - -To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopMessagesRetrievalMimeFormat -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 - -- 1: HtmlOnly - -- 2: HtmlAndTextAlternative - -- 3: TextEnrichedOnly - -- 4: TextEnrichedAndTextAlternative - -- 5: BestBodyFormat - -- 6: Tnef - -The default value is BestBodyFormat. - -To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopSuppressReadReceipt -The PopSuppressReadReceipt parameter controls the behavior of read receipts for POP3 clients that access the mailbox. - -Valid values for this parameter are: - -- $true: The user receives a read receipt when the recipient opens the message. - -- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. - -The default value is $false. - -To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopUseProtocolDefaults -The PopUseProtocolDefaults parameter specifies whether to use the POP3 protocol defaults for the mailbox. - -Valid input for this parameter is $true or $false. The default value is $true. You need to set the PopUseProtocolDefaults parameter to $false when you use any of following parameters: - -- PopEnableExactRFC822Size - -- PopForceICalForCalendarRetrievalOption - -- PopMessagesRetrievalMimeFormat - -- PopSuppressReadReceipt - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimarySmtpAddress -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. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderClientAccess -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 PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is set to the value $true (the default value is $false). - -- $false: The user can't access public folders in Outlook. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResetAutoBlockedDevices -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SamAccountName -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 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowGalAsDefaultView -The ShowGalAsDefaultView parameter shows the global address list (GAL) as the default recipient picker for messages. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SmtpClientAuthenticationDisabled -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: - -- POP3 and IMAP4 clients. - -- Devices with scan to email capability. - -- Workflow applications that send email notifications. - -- Online services that send messages using internal email addresses in the organization. - -Valid values for this parameter are: - -- $true: Authenticated SMTP is disabled for the mailbox. - -- $false: Authenticated SMTP is enabled for the mailbox. - -- blank ($null): This is the default value. The authenticated SMTP setting for the mailbox is controlled by the corresponding SmtpClientAuthenticationDisabled parameter on the Set-TransportConfig cmdlet for the whole organization. By default, authenticated SMTP is enabled for the organization ($false), which means authenticated SMTP is also enabled for the mailbox. - -To selectively enable authenticated SMTP for specific mailboxes only: disable authenticated SMTP at the organizational level ($true), enable it for the specific mailboxes ($false), and leave the rest of the mailboxes with their default value ($null). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UniversalOutlookEnabled -This parameter is available only in the cloud-based service. - -The UniversalOutlookEnabled parameter enables or disables access to the mailbox by using Windows 10 Mail and Calendar. Valid values are: - -- $true: Access to the mailbox using Windows 10 Mail and Calendar is enabled. This is the default value. - -- $false: Access to the mailbox using Windows 10 Mail and Calendar is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Set-ClientAccessRule.md b/exchange/exchange-ps/exchange/client-access/Set-ClientAccessRule.md deleted file mode 100644 index a59b23e32c..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Set-ClientAccessRule.md +++ /dev/null @@ -1,556 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-clientaccessrule -applicable: Exchange Server 2019, Exchange Online -title: Set-ClientAccessRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# Set-ClientAccessRule - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-ClientAccessRule cmdlet to modify existing client access rules. Client access rules help you control access to your organization based on the properties of the connection. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ClientAccessRule [-Identity] <ClientAccessRuleIdParameter> - [-Action <ClientAccessRulesAction>] - [-AnyOfAuthenticationTypes <MultiValuedProperty>] - [-AnyOfClientIPAddressesOrRanges <MultiValuedProperty>] - [-AnyOfProtocols <MultiValuedProperty>] - [-Confirm] - [-DomainController <Fqdn>] - [-Enabled <Boolean>] - [-ExceptAnyOfAuthenticationTypes <MultiValuedProperty>] - [-ExceptAnyOfClientIPAddressesOrRanges <MultiValuedProperty>] - [-ExceptAnyOfProtocols <MultiValuedProperty>] - [-ExceptUsernameMatchesAnyOfPatterns <MultiValuedProperty>] - [-Name <String>] - [-Priority <Int32>] - [-Scope <ClientAccessRulesScope>] - [-UsernameMatchesAnyOfPatterns <MultiValuedProperty>] - [-UserRecipientFilter <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. - -Note: Not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list: - -- OutlookWebApp: BasicAuthentication and AdfsAuthentication. - -- ExchangeAdminCenter: BasicAuthentication and AdfsAuthentication. - -- RemotePowerShell: BasicAuthentication and NonBasicAuthentication. - -- ExchangeActiveSync: BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-ClientAccessRule "Allow IMAP4" -AnyOfClientIPAddressesOrRanges @{Add="172.17.17.27/16"} -``` - -This example adds the IP address range 172.17.17.27/16 to the existing client access rule named Allow IMAP4 without affecting the existing IP address values. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ClientAccessRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Action -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 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfAuthenticationTypes -This parameter is available 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. - -Valid values for this parameter are: - -- AdfsAuthentication - -- BasicAuthentication - -- CertificateBasedAuthentication - -- NonBasicAuthentication - -- OAuthAuthentication - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfClientIPAddressesOrRanges -The AnyOfClientIPAddressesOrRanges parameter specifies a condition for the client access rule that's based on the client's IP address. Valid values for this parameter are: - -- A single IP address: For example, 192.168.1.1. - -- An IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.3.1/24. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfProtocols -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: - -- ExchangeActiveSync - -- ExchangeAdminCenter - -- ExchangeWebServices - -- IMAP4 - -- OfflineAddressBook - -- OutlookAnywhere - -- OutlookWebApp - -- POP3 - -- PowerShellWebServices - -- RemotePowerShell - -- REST - -- UniversalOutlook (Mail and Calendar app) - -**Note**: In Exchange 2019, the only supported values are ExchangeAdminCenter and RemotePowerShell. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -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 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptAnyOfAuthenticationTypes -This parameter is available 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. - -Valid values for this parameter are: - -- AdfsAuthentication - -- BasicAuthentication - -- CertificateBasedAuthentication - -- NonBasicAuthentication - -- OAuthAuthentication - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptAnyOfClientIPAddressesOrRanges -The ExceptAnyOfClientIPAddressesOrRanges parameter specifies an exception for the client access rule that's based on the client's IP address. Valid values for this parameter are: - -- A single IP address: For example, 192.168.1.1. - -- An IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.3.1/24. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptAnyOfProtocols -This parameter is available 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. - -Valid values for this parameter are: - -- ExchangeActiveSync - -- ExchangeAdminCenter - -- ExchangeWebServices - -- IMAP4 - -- OfflineAddressBook - -- OutlookAnywhere - -- OutlookWebApp - -- POP3 - -- PowerShellWebServices - -- RemotePowerShell - -- REST - -- UniversalOutlook (Mail and Calendar app) - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptUsernameMatchesAnyOfPatterns -This parameter is available 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 \<Domain\>\\\<UserName\> (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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies a unique name for the client access rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -The Scope parameter specifies the scope of the client access rule. Valid values are: - -- Users: The rule only applies to end-user connections. - -- All: The rule applies to all connections (end-users and middle-tier apps). - -```yaml -Type: ClientAccessRulesScope -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsernameMatchesAnyOfPatterns -This parameter is available 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 \<Domain\>\\\<UserName\> (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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserRecipientFilter -This parameter is available 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. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"City -eq 'Redmond'"`). - -- 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. - -- Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -The filterable properties that you can use with this parameter are: - -- City - -- Company - -- CountryOrRegion - -- CustomAttribute1 to CustomAttribute15 - -- Department - -- Office - -- PostalCode - -- StateOrProvince - -- StreetAddress - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Set-MailboxCalendarConfiguration.md b/exchange/exchange-ps/exchange/client-access/Set-MailboxCalendarConfiguration.md deleted file mode 100644 index 6cff4b291f..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Set-MailboxCalendarConfiguration.md +++ /dev/null @@ -1,1029 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-mailboxcalendarconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MailboxCalendarConfiguration -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-MailboxCalendarConfiguration - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-MailboxCalendarConfiguration cmdlet to modify mailbox calendar settings for Outlook on the web. This affects how the user's calendar looks and how reminders work in Outlook on the web. This also affects settings that define how meeting invitations, responses, and notifications are sent to the user. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MailboxCalendarConfiguration [-Identity] <MailboxIdParameter> - [-AgendaMailEnabled <Boolean>] - [-AgendaPaneEnabled <Boolean>] - [-CalendarFeedsPreferredLanguage <String>] - [-CalendarFeedsPreferredRegion <String>] - [-CalendarFeedsRootPageId <String>] - [-Confirm] - [-ConversationalSchedulingEnabled <Boolean>] - [-CreateEventsFromEmailAsPrivate <Boolean>] - [-DailyAgendaMailSchedule <AgendaMailSchedule>] - [-DefaultMeetingDuration <Int32>] - [-DefaultReminderTime <TimeSpan>] - [-DiningEventsFromEmailEnabled <Boolean>] - [-DomainController <Fqdn>] - [-EntertainmentEventsFromEmailEnabled <Boolean>] - [-EventsFromEmailEnabled <Boolean>] - [-FirstWeekOfYear <FirstWeekRules>] - [-FlightEventsFromEmailEnabled <Boolean>] - [-HotelEventsFromEmailEnabled <Boolean>] - [-InvoiceEventsFromEmailEnabled <Boolean>] - [-LocalEventsEnabled <LocalEventsEnabledStatus>] - [-LocalEventsLocation <LocalEventsLocation>] - [-PackageDeliveryEventsFromEmailEnabled <Boolean>] - [-ReminderSoundEnabled <Boolean>] - [-RemindersEnabled <Boolean>] - [-RentalCarEventsFromEmailEnabled <Boolean>] - [-ShowWeekNumbers <Boolean>] - [-SkipAgendaMailOnFreeDays <Boolean>] - [-TimeIncrement <HourIncrement>] - [-UseBrightCalendarColorThemeInOwa <Boolean>] - [-WeatherEnabled <Boolean>] - [-WeatherLocationBookmark <Int32>] - [-WeatherLocations <MultiValuedProperty>] - [-WeatherUnit <WeatherTemperatureUnit>] - [-WeekStartDay <DayOfWeek>] - [-WhatIf] - [-WorkDays <DaysOfWeek>] - [-WorkingHoursEndTime <TimeSpan>] - [-WorkingHoursStartTime <TimeSpan>] - [-WorkingHoursTimeZone <ExTimeZoneValue>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Set-MailboxCalendarConfiguration cmdlet primarily allows users to manage their own calendar settings in Outlook on the web Options. However, administrators who have the Organization Management or Recipient Management management roles may configure the calendar settings for users by using this cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MailboxCalendarConfiguration -Identity peter@contoso.com -RemindersEnabled $false -``` - -This example disables the calendar reminders for the calendar of the user peter@contoso.com. - -### Example 2 -```powershell -Set-MailboxCalendarConfiguration -Identity peter@contoso.com -WorkingHoursTimeZone "Pacific Standard Time" -``` - -This example sets the time zone of the work hours' start and end times to Pacific Standard Time for the calendar of the user peter@contoso.com. - -### Example 3 -```powershell -Set-MailboxCalendarConfiguration -Identity Tony -WorkingHoursStartTime 07:00:00 -``` - -This example sets the working day's starting hour to 7 A.M. for the calendar of the user Tony. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AgendaMailEnabled -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AgendaPaneEnabled -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CalendarFeedsPreferredLanguage -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). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CalendarFeedsPreferredRegion -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 uppercase two-letter country code (for example, US for the United States). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CalendarFeedsRootPageId -This parameter is available only in the cloud-based service. - -The CalendarFeedsRootPageId parameter specifies the root page ID for calendar feeds. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConversationalSchedulingEnabled -The ConversationalSchedulingEnabled parameter specifies whether to enable or disable conversational scheduling. Valid values are: - -- $true: Conversational scheduling is enabled. This is the default value. - -- $false: Conversational scheduling is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CreateEventsFromEmailAsPrivate -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: - -- $true: Events from email are created as Private. This is the default value. - -- $false: Events from email are created as Normal (public). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DailyAgendaMailSchedule -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultMeetingDuration -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultReminderTime -The DefaultReminderTime parameter specifies the length of time before a meeting or appointment whenthe 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. - -Note that the value can't contain seconds. Valid values are: - -- 00:00:00 - -- 00:05:00 (5 minutes) - -- 00:10:00 (10 minutes) - -- 00:15:00 (15 minutes) This is the default value. - -- 00:30:00 (30 minutes) - -- 01:00:00 (1 hour) - -- 02:00:00 (2 hours) - -- 03:00:00 (3 hours) - -- 04:00:00 (4 hours) - -- 08:00:00 (8 hours) - -- 12:00:00 (12 hours) - -- 1.00:00:00 (1 day) - -- 2.00:00:00 (2 days) - -- 3.00:00:00 (3 days) - -- 7.00:00:00 (7 days) - -- 14.00:00:00 (14 days) - -This parameter is ignored when the RemindersEnabled parameter is set to $false. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiningEventsFromEmailEnabled -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: - -- $true: Create dining reservation events from email messages. This is the default value. - -- $false: Don't create dining reservation events from email messages. - -This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EntertainmentEventsFromEmailEnabled -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: - -- $true: Create entertainment reservation events from email messages. This is the default value. - -- $false: Don't create entertainment reservation events from email messages. - -This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventsFromEmailEnabled -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: - -- $true: Creating events from email messages is enabled. This is the default value. - -- $false: Creating events from email messages is disabled. - -When this setting is enabled, you can enable or disable creating specific types of events from email messages by using the following parameters: - -- DiningEventsFromEmailEnabled - -- EntertainmentEventsFromEmailEnabled - -- FlightEventsFromEmailEnabled - -- HotelEventsFromEmailEnabled - -- PackageDeliveryEventsFromEmailEnabled - -- RentalCarEventsFromEmailEnabled - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FlightEventsFromEmailEnabled -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: - -- $true: Create flight reservation events from email messages. This is the default value. - -- $false: Don't create flight reservation events from email messages. - -This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FirstWeekOfYear -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. - -- FirstFourDayWeek: Week numbers start on the first week that has at least four days. - -- FirstFullWeek: Week numbers start on the first week that has seven days. - -- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox has been moved from an earlier version of Exchange. - -You configure the first day of the week by using the WeekStartDay parameter. - -```yaml -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 -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -HotelEventsFromEmailEnabled -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: - -- $true: Create hotel reservation events from email messages. This is the default value. - -- $false: Don't create hotel reservation events from email messages. - -This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InvoiceEventsFromEmailEnabled -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: - -- $true: Creating invoices from messages is enabled. This is the default value. - -- $false: Creating invoices from messages is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalEventsEnabled -PARAMVALUE: FirstRun | Disabled | Enabled - -```yaml -Type: LocalEventsEnabledStatus -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalEventsLocation -PARAMVALUE: LocalEventsLocation - -```yaml -Type: LocalEventsLocation -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PackageDeliveryEventsFromEmailEnabled -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: - -- $true: Create package delivery events from email messages. - -- $false: Don't create package delivery events from email messages. This is the default value. - -This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemindersEnabled -The RemindersEnabled parameter enables or disables reminders for calendar items. Valid values are: - -- $true: Reminders are enabled. This is the default value. - -- $false: Reminders are disabled. - -When the reminder is first displayed is controlled by the DefaultReminderTime 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReminderSoundEnabled -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. - -- $false: No sound is played with the reminder. - -This parameter is ignored when the RemindersEnabled parameter is set 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RentalCarEventsFromEmailEnabled -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: - -- $true: Create rental car reservation events from email messages. This is the default value. - -- $false: Don't create rental car reservation events from email messages. - -This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowWeekNumbers -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. - -- $false: The week number isn't displayed. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipAgendaMailOnFreeDays -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeIncrement -The TimeIncrement parameter specifies the scale that the Outlook on the web calendar uses to show time. Valid values are: - -- FifteenMinutes - -- ThirtyMinutes (This is the default value) - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseBrightCalendarColorThemeInOwa -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. - -- $false: Use light colors in the calendar. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WeekStartDay -The WeekStartDay parameter specifies the first day of the week. Valid values are: - -- Sunday (This is the default value) - -- Monday - -- Tuesday - -- Wednesday - -- Thursday - -- Friday - -- Saturday - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WeatherEnabled -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: - -- FirstRun (This is the default value) - -- Disabled: Hide weather on the calendar. - -- Enabled: Show weather on the calendar. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WeatherLocationBookmark -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. - -A valid value for this parameter depends on the number of weather locations that are configured for the mailbox. For example, if there are 3 weather locations configured, you can specify the value 0, 1, or 2 for this parameter. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WeatherLocations -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. - -This parameter uses the syntax: LocationId:\<LocationID\>;Name:\<Name\>;Latitude:\<Latitude\>;Longitude:\<Longitude\>. For example, LocationId:105808079;Name:Redmond, WA;Latitude:47.679;Longitude:-122.132. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -For this parameter, "\<value1\>" is "LocationId:\<LocationID1\>;Name:\<Name1\>;Latitude:\<Latitude1\>;Longitude:\<Longitude1\>", and "\<value2\>" is "LocationId:\<LocationID2\>;Name:\<Name2\>;Latitude:\<Latitude2\>;Longitude:\<Longitude2\>" - -You can configure a maximum of 5 weather locations. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WeatherUnit -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: - -- Default (This is the default value) - -- Celsius - -- Fahrenheit - -```yaml -Type: WeatherTemperatureUnit -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkDays -The WorkDays parameter specifies the work days in the calendar. Valid values are: - -- None - -- AllDays - -- Weekdays (This is the default value) - -- WeekEndDays - -- Sunday - -- Monday - -- Tuesday - -- Wednesday - -- Thursday - -- Friday - -- Saturday - -You can specify multiple values separated by commas, but redundant values are ignored. For example, entering Weekdays,Monday results in the value Weekdays. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkingHoursEndTime -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. - -The default value is 17:00:00 (5:00 P.M.). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkingHoursStartTime -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. - -The default value is 08:00:00(8:00 A.M.). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkingHoursTimeZone -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"). - -To see the available values, run the following command: `$TimeZone = Get-ChildItem "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Time zones" | foreach {Get-ItemProperty $_.PSPath}; $TimeZone | sort Display | Format-Table -Auto PSChildname,Display`. - -If the value contains spaces, enclose the value in quotation marks ("). The default value is the time zone setting of the Exchange server. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Set-MailboxMessageConfiguration.md b/exchange/exchange-ps/exchange/client-access/Set-MailboxMessageConfiguration.md deleted file mode 100644 index 208f062a34..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Set-MailboxMessageConfiguration.md +++ /dev/null @@ -1,999 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-mailboxmessageconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MailboxMessageConfiguration -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-MailboxMessageConfiguration - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-MailboxMessageConfiguration cmdlet to configure the Outlook on the web settings that are applied to specific mailboxes. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MailboxMessageConfiguration [-Identity] <MailboxIdParameter> - [-AfterMoveOrDeleteBehavior <AfterMoveOrDeleteBehavior>] - [-AlwaysShowBcc <Boolean>] [-AlwaysShowFrom <Boolean>] [-AutoAddSignature <Boolean>] - [-Confirm] - [-ConversationSortOrder <ConversationSortOrder>] - [-DefaultFontColor <String>] [-DefaultFontFlags <FontFlags>] - [-DefaultFontName <String>] [-DefaultFontSize <Int32>] [-DefaultFormat <MailFormat>] - [-DomainController <Fqdn>] [-EmptyDeletedItemsOnLogoff <Boolean>] [-HideDeletedItems <Boolean>] - [-IgnoreDefaultScope] [-NewItemNotification <NewItemNotification>] - [-PreviewMarkAsReadBehavior <PreviewMarkAsReadBehavior>] [-PreviewMarkAsReadDelaytime <Int32>] - [-ReadReceiptResponse <ReadReceiptResponse>] [-SendAddressDefault <String>] - [-ShowConversationAsTree <Boolean>] [-SignatureHtml <String>] [-SignatureText <String>] [-WhatIf] - [-AutoAddSignatureOnMobile <Boolean>] [-CheckForForgottenAttachments <Boolean>] - [-EmailComposeMode <EmailComposeMode>] [-SignatureTextOnMobile <String>] - [-UseDefaultSignatureOnMobile <Boolean>] [-AutoAddSignatureOnReply <Boolean>] - [-GlobalReadingPanePosition <MailReadingPanePosition>] [-IsFavoritesFolderTreeCollapsed <Boolean>] - [-IsMailRootFolderTreeCollapsed <Boolean>] [-IsReplyAllTheDefaultResponse <Boolean>] - [-LinkPreviewEnabled <Boolean>] [-MailFolderPaneExpanded <Boolean>] - [-NavigationPaneViewOption <NavigationPaneView>] - [-PreferAccessibleContent <Boolean>] [-ShowPreviewTextInListView <Boolean>] - [-ShowReadingPaneOnFirstLoad <Boolean>] [-ShowSenderOnTopInListView <Boolean>] - [-ShowUpNext <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-MailboxMessageConfiguration cmdlet configures Outlook on the web settings for the specified mailbox. These settings include email signature, message format, message options, read receipts, reading pane, and conversations. These settings are not used in Outlook, Exchange ActiveSync, or other email clients. These settings are applied in Outlook on the web only. Settings that contain the word Mobile are applied in Outlook on the web for devices only. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MailboxMessageConfiguration kai@contoso.com -HideDeletedItems $true -``` - -This example sets items deleted from a conversation thread to not show in the list view of the conversation in Outlook on the web for Kai's mailbox. - -### Example 2 -```powershell -Set-MailboxMessageConfiguration kai@contoso.com -AlwaysShowBcc $true -``` - -This example sets the compose email message form to always show the Bcc field in Outlook on the web for Kai's mailbox. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AfterMoveOrDeleteBehavior -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 - -- OpenNextItem - -- ReturnToView - -The default value is OpenNextItem. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlwaysShowBcc -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlwaysShowFrom -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoAddSignature -The AutoAddSignature parameter specifies whether to automatically add signatures to new email messages created in Outlook on the web. Valid values are: - -- $true: Email signatures are automatically added to new messages. - -- $false: Email signatures aren't automatically added to new messages. - -The email signature specified by the SignatureText parameter is added to plain text messages. The email signature specified by the SignatureHTML parameter is added to HTML-formatted 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConversationSortOrder -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 - -- Tree - -- NewestOnTop - -- NewestOnBottom - -- ChronologicalNewestOnTop - -- ChronologicalNewestOnBottom - -- TreeNewestOnBottom - -The default value is ChronologicalNewestOnTop. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultFontColor -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultFontFlags -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 - -- Bold - -- Italic - -- Underline - -- All - -The default value is Normal. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultFontName -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultFontSize -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultFormat -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmptyDeletedItemsOnLogoff -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HideDeletedItems -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewItemNotification -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 - -- EMailToast - -- VoiceMailToast - -- FaxToast - -- None - -- All - -The default value is All. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviewMarkAsReadBehavior -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. - -- OnSelectionChange - -- Never - -The default value is OnSelectionChange. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviewMarkAsReadDelaytime -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. - -This parameter is meaningful only if you set the PreviewMarkAsReadBehavior parameter to the value Delayed. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadReceiptResponse -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 - -- AlwaysSend - -- NeverSend - -The default value is DoNotAutomaticallySend. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendAddressDefault -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. - -You can use one of the following values: - -- Blank, which is represented by the value $null. This indicates no default From address is specified. - -- The user's primary email address. For example, bob@contoso.com. - -- The GUID of a POP, IMAP, or Hotmail subscription that's configured on the user's mailbox. - -By default, no default From address is specified on the mailbox. When no default From address is specified, the default behavior is: - -- The primary email address on the mailbox is used for all new messages. - -- The To address of the incoming message is used as the From address for all replies or forwarded messages. - -You can find the available values for SendAddressDefault on a mailbox by running the command Get-SendAddress -Mailbox \<mailbox\>. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowConversationAsTree -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignatureHtml -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. - -To automatically add this email signature to HTML-formatted messages created by the user in Outlook on the web, the AutoAddSignature parameter must be set to $true. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignatureText -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. - -To automatically add the email signature to plain text messages created by the user in Outlook on the web, the AutoAddSignature parameter must be set to the value $true. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoAddSignatureOnMobile -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. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CheckForForgottenAttachments -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. - -For example, the user creates a message that includes the text "Please see the attached Word document", but the user doesn't attach a file, and clicks Send. If this value is set to $true, the user gets a warning prompt so they can go back to the message and attach a file. If this value is set to $false, the user doesn't get the warning prompt. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailComposeMode -The EmailComposeMode parameter specifies how the user creates messages in Outlook on the web. You can use the following values: - -- Inline: New messages and replies are created in the preview pane. This is the default value. - -- SeparateForm: New messages and replies are created in a new browser window. - -```yaml -Type: EmailComposeMode -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignatureTextOnMobile -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. - -To automatically add the email signature to messages created by the user in Outlook on the web for devices, the AutoAddSignatureOnMobile parameter must be set to the value $true. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultSignatureOnMobile -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. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoAddSignatureOnReply -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. - -- $false: Email signatures aren't automatically added to reply messages. - -The email signature specified by the SignatureText parameter is added to plain text messages. The email signature specified by the SignatureHTML parameter is added to HTML-formatted messages. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GlobalReadingPanePosition -The GlobalReadingPanePosition specifies the default location of the reading pane in Outlook on the web. Valid values are: - -- Off - -- Bottom - -- Right (This is the default value) - -```yaml -Type: MailReadingPanePosition -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsFavoritesFolderTreeCollapsed -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. - -- $false: The Favorites folder tree isn't collapsed by default. This is the default value - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsMailRootFolderTreeCollapsed -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. - -- $false: The Mail root folder tree isn't collapsed by default. This is the default value - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsReplyAllTheDefaultResponse -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. - -- $false: Reply All isn't the default response option for messages in the reading pane. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LinkPreviewEnabled -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. - -- $false: Link preview of URLs in email messages is disabled for the user. - -This parameter depends on the value of the LinkPreviewEnabled parameter on the Set-OrganizationConfig cmdlet, which controls the link preview behavior in Outlook on the web for the entire organization. If link preview is disabled for the organization, users can't enable it for themselves. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailFolderPaneExpanded -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. - -- $false: The Mail folder pane isn't expanded by default. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NavigationPaneViewOption -The NavigationPaneViewOption parameter specifies the default navigation pane view in Outlook on the web. Valid values are: - -- Default: This is the default value - -- MailFolders - -- PeopleFolders - -- Groups - -- PinnedMailFolders - -```yaml -Type: NavigationPaneView -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferAccessibleContent -The PreferAccessibleContent parameter specifies whether to prefer accessible content in Outlook on the web. Valid values are: - -- $true: Prefer accessible content. - -- $false: Don't prefer accessible content. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowPreviewTextInListView -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. - -- $false: Don't show preview text for messages in list view. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowReadingPaneOnFirstLoad -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. - -- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowSenderOnTopInListView -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. - -- $false: Don't show the message sender on top in list view. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowUpNext -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. - -- $false: Don't show the next upcoming event above the mail list view. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/client-access/Set-OwaMailboxPolicy.md deleted file mode 100644 index 7e2f9e3994..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Set-OwaMailboxPolicy.md +++ /dev/null @@ -1,2578 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-OwaMailboxPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-OwaMailboxPolicy cmdlet to configure existing Outlook on the web mailbox policies. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-OwaMailboxPolicy [-Identity] <MailboxPolicyIdParameter> - [-ActionForUnknownFileAndMIMETypes <AttachmentBlockingActions>] - [-ActiveSyncIntegrationEnabled <Boolean>] - [-AdditionalStorageProvidersAvailable <Boolean>] - [-AllAddressListsEnabled <Boolean>] - [-AllowCopyContactsToDeviceAddressBook <Boolean>] - [-AllowedFileTypes <MultiValuedProperty>] - [-AllowedMimeTypes <MultiValuedProperty>] - [-AllowOfflineOn <AllowOfflineOnEnum>] - [-BlockedFileTypes <MultiValuedProperty>] - [-BlockedMimeTypes <MultiValuedProperty>] - [-CalendarEnabled <Boolean>] - [-ChangePasswordEnabled <Boolean>] - [-ClassicAttachmentsEnabled <Boolean>] - [-ConditionalAccessPolicy <PolicyEnum>] - [-Confirm] - [-ContactsEnabled <Boolean>] - [-DefaultClientLanguage <Int32>] - [-DefaultTheme <String>] - [-DelegateAccessEnabled <Boolean>] - [-DirectFileAccessOnPrivateComputersEnabled <Boolean>] - [-DirectFileAccessOnPublicComputersEnabled <Boolean>] - [-DisableFacebook] - [-DisplayPhotosEnabled <Boolean>] - [-DomainController <Fqdn>] - [-ExplicitLogonEnabled <Boolean>] - [-ExternalImageProxyEnabled <Boolean>] - [-ExternalSPMySiteHostURL <String>] - [-ForceSaveAttachmentFilteringEnabled <Boolean>] - [-ForceSaveFileTypes <MultiValuedProperty>] - [-ForceSaveMimeTypes <MultiValuedProperty>] - [-ForceWacViewingFirstOnPrivateComputers <Boolean>] - [-ForceWacViewingFirstOnPublicComputers <Boolean>] - [-ForceWebReadyDocumentViewingFirstOnPrivateComputers <Boolean>] - [-ForceWebReadyDocumentViewingFirstOnPublicComputers <Boolean>] - [-FreCardsEnabled <Boolean>] - [-GlobalAddressListEnabled <Boolean>] - [-GroupCreationEnabled <Boolean>] - [-InstantMessagingEnabled <Boolean>] - [-InstantMessagingType <InstantMessagingTypeOptions>] - [-InterestingCalendarsEnabled <Boolean>] - [-InternalSPMySiteHostURL <String>] - [-IRMEnabled <Boolean>] - [-IsDefault] - [-JournalEnabled <Boolean>] - [-JunkEmailEnabled <Boolean>] - [-LinkedInEnabled <Boolean>] - [-LocalEventsEnabled <Boolean>] - [-LogonAndErrorLanguage <Int32>] - [-Name <String>] - [-NotesEnabled <Boolean>] - [-NpsMailboxPolicy <Boolean>] - [-OrganizationEnabled <Boolean>] - [-OneDriveAttachmentsEnabled <Boolean>] - [-OnSendAddinsEnabled <Boolean>] - [-OutboundCharset <OutboundCharsetOptions>] - [-OutlookBetaToggleEnabled <Boolean>] [<CommonParameters>] - [-OWALightEnabled <Boolean>] - [-OWAMiniEnabled <Boolean>] - [-PersonalAccountCalendarsEnabled <Boolean>] - [-PhoneticSupportEnabled <Boolean>] - [-PlacesEnabled <Boolean>] - [-PremiumClientEnabled <Boolean>] - [-PrintWithoutDownloadEnabled <Boolean>] - [-PublicFoldersEnabled <Boolean>] - [-RecoverDeletedItemsEnabled <Boolean>] - [-ReferenceAttachmentsEnabled <Boolean>] - [-RemindersAndNotificationsEnabled <Boolean>] - [-ReportJunkEmailEnabled <Boolean>] - [-RulesEnabled <Boolean>] - [-SatisfactionEnabled <Boolean>] - [-SaveAttachmentsToCloudEnabled <Boolean>] - [-SearchFoldersEnabled <Boolean>] - [-SetPhotoEnabled <Boolean>] - [-SetPhotoURL <String>] - [-SignaturesEnabled <Boolean>] - [-SilverlightEnabled <Boolean>] - [-SkipCreateUnifiedGroupCustomSharepointClassification <Boolean>] - [-SMimeEnabled <Boolean>] [-SpellCheckerEnabled <Boolean>] - [-TasksEnabled <Boolean>] - [-TeamSnapCalendarsEnabled <Boolean>] - [-TextMessagingEnabled <Boolean>] - [-ThemeSelectionEnabled <Boolean>] - [-ThirdPartyAttachmentsEnabled <Boolean>] - [-ThirdPartyFileProvidersEnabled <Boolean>] - [-UMIntegrationEnabled <Boolean>] - [-UNCAccessOnPrivateComputersEnabled <Boolean>] - [-UNCAccessOnPublicComputersEnabled <Boolean>] - [-UseGB18030 <Boolean>] - [-UseISO885915 <Boolean>] - [-UserVoiceEnabled <Boolean>] - [-WacEditingEnabled <Boolean>] - [-WacExternalServicesEnabled <Boolean>] - [-WacOMEXEnabled <Boolean>] - [-WacViewingOnPrivateComputersEnabled <Boolean>] - [-WacViewingOnPublicComputersEnabled <Boolean>] - [-WeatherEnabled <Boolean>] - [-WebPartsFrameOptionsType <WebPartsFrameOptions>] - [-WebReadyDocumentViewingForAllSupportedTypes <Boolean>] - [-WebReadyDocumentViewingOnPrivateComputersEnabled <Boolean>] - [-WebReadyDocumentViewingOnPublicComputersEnabled <Boolean>] - [-WebReadyDocumentViewingSupportedFileTypes <MultiValuedProperty>] - [-WebReadyDocumentViewingSupportedMimeTypes <MultiValuedProperty>] - [-WebReadyFileTypes <MultiValuedProperty>] - [-WebReadyMimeTypes <MultiValuedProperty>] - [-WhatIf] - [-WSSAccessOnPrivateComputersEnabled <Boolean>] - [-WSSAccessOnPublicComputersEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -In on-premises Exchange, the default Outlook on the web mailbox policy is named Default. In Office 365, the default Outlook on the web mailbox policy is named OwaMailboxPolicy-Default. - -Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-OwaMailboxPolicy -Identity EMEA\Contoso\Corporate -CalendarEnabled $false -``` - -This example disables access to the calendar for the mailbox policy named Corporate for the tenant Contoso in the organization EMEA. - -### Example 2 -```powershell -Set-OwaMailboxPolicy -Identity Default -TasksEnabled $false -``` - -This example disables access to the Tasks folder for the default mailbox policy in an on-premises Exchange organization. - -### Example 3 -```powershell -Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -AllowedFileTypes '.doc', '.pdf' -``` - -This example sets the allowed file type extensions to .doc and .pdf for the default mailbox policy in an Office 365 organization, allowing users to save files with those extensions locally or view them from a web browser. - -### Example 4 -```powershell -Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -UserVoiceEnabled $false -``` - -This example disables Outlook UserVoice for the default mailbox policy in Office 365. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ActionForUnknownFileAndMIMETypes -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.) - -- ForceSave - -- Block - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdditionalStorageProvidersAvailable -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: - -- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This is the default value. - -- $false: Additional storage providers are disabled in Outlook on the web. Users can't connect their additional storage providers or share files over email. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActiveSyncIntegrationEnabled -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. - -- $false: ActiveSync isn't available in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllAddressListsEnabled -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. - -- $false: Only the global address list is visible in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCopyContactsToDeviceAddressBook -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. - -- $false: Contacts can't be copied to the device's address book in Outlook on the web for devices. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowedFileTypes -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 - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -If the same file types are specified in multiple lists: - -- The Block list overrides the Allow list and the Force Save list. - -- The Force Save list overrides the Allow list. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowedMimeTypes -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 - -- image/gif - -- image/jpeg - -- image/png - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -If the same MIME types are specified in multiple lists: - -- The Allow list overrides the Block list and the Force Save list. - -- The Block list overrides the Force Save list. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOfflineOn -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: - -- PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later and Exchange Online, 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 on the Set-OwaVirtualDirectory cmdlet). - -- NoComputers: Offline mode is disabled. - -- AllComputers: Offline mode is available for public and private computer sessions. This is the default value. - -When offline mode is available, users can turn offline mode on or off themselves in Outlook Web App. For more information, see [Using Outlook Web App offline](https://go.microsoft.com/fwlink/p/?linkid=267644). - -```yaml -Type: AllowOfflineOnEnum -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockedFileTypes -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, .appref-ms, .asp, .aspx, .asx, .bas, .bat, .cdxml, .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, .pssc, .pst, .py, .pyc, .pyo, .pyw, .pyz, .pyzw, .reg, .scf, .scr, .sct, .settingcontent-ms, .shb, .shs, .theme, .tmp, .udl, .url, .vb, .vbe, .vbp, .vbs, .vsmacros, .vsw, .webpnp, .website, .ws, .wsb, .wsc, .wsf, .wsh, .xbap, .xll, .xnk - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -If the same file types are specified in multiple lists: - -- The Allow list overrides the Block list and the Force Save list. - -- The Block list overrides the Force Save list. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockedMimeTypes -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 - -- application/javascript - -- application/msaccess - -- application/prg - -- application/x-javascript - -- text/javascript - -- text/scriplet - -- x-internet-signup - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -If the same MIME types are specified in multiple lists: - -- The Allow list overrides the Block list and the Force Save list. - -- The Block list overrides the Force Save list. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CalendarEnabled -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: - -- $true: The Calendar is available in Outlook Web App. This is the default value. - -- $false: The Calendar isn't available in Outlook Web App. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChangePasswordEnabled -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: - -- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange. - -- $false: The Change password option isn't available in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClassicAttachmentsEnabled -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. - -- $false: Users can't attach local files to email messages in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalAccessPolicy -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 Azure Active Directory Portal. - -Note: When you enable a Conditional Access policy, users will no longer be able to access the light version of Outlook on the web. An error message will direct them to use the default premium experience. - -Valid values are: - -- Off: No conditional access policy is applied to Outlook on the web. This is the default value. - -- ReadOnly: Users can't download attachments to their local computer, and can't enable Offline Mode on non-compliant computers. They can still view attachments in the browser. - -- ReadOnlyPlusAttachmentsBlocked: All restrictions from ReadOnly apply, but users can't view attachments in the browser. - -```yaml -Type: PolicyEnum -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContactsEnabled -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: - -- $true: Contacts are available in Outlook Web App. This is the default value. - -- $false: Contacts aren't available in Outlook Web App. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultClientLanguage -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultTheme -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://docs.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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DelegateAccessEnabled -This parameter is available or 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: - -- $true: Delegates can open the mailbox in Outlook Web App. This is the default value. - -- $false: Delegates can't open the mailbox in Outlook Web App. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DirectFileAccessOnPrivateComputersEnabled -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. - -- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. - -By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DirectFileAccessOnPublicComputersEnabled -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. - -- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. - -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 on the Set-OwaVirtualDirectory cmdlet). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableFacebook -This parameter is available only in the cloud-based service. - -The DisableFacebook switch specifies whether users can synchronize their Facebook contacts to their Contacts folder in Outlook on the web. By default, Facebook integration is enabled. - -- To disable Facebook integration, use this switch without a value. - -- To enable Facebook integration after it's been disabled, use this exact syntax: -DisableFacebook:$false. - -Note that the value of this parameter is stored in the FacebookEnabled property in the output of the Get-OwaMailboxPolicy cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayPhotosEnabled -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. - -- $false: Users don't see sender photos in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExplicitLogonEnabled -This parameter is available 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: - -- $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. - -- $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalImageProxyEnabled -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: - -- $true: All external images are loaded through the Outlook external image proxy. This is the default value. - -- $false: All external images are loaded through the web browser. This is potentially unsafe, as the images could have mixed content or malformed images that ask for user credentials. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalSPMySiteHostURL -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 for Business to appear as regular file attachments in messages. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceSaveAttachmentFilteringEnabled -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. - -- $false: The attachments aren't filtered before they're saved. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceSaveFileTypes -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 - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -If the same file types are specified in multiple lists: - -- The Allow list overrides the Block list and the Force Save list. - -- The Block list overrides the Force Save list. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceSaveMimeTypes -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 - -- Application/octet-stream - -- Application/x-director - -- Application/x-shockwave-flash - -- text/html - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -If the same MIME types are specified in multiple lists: - -- The Allow list overrides the Block list and the Force Save list. - -- The Block list overrides the Force Save list. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceWacViewingFirstOnPrivateComputers -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. - -- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. - -By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceWacViewingFirstOnPublicComputers -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. - -- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. - -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 on the Set-OwaVirtualDirectory cmdlet). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceWebReadyDocumentViewingFirstOnPrivateComputers -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: - -- $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. - -- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. - -By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceWebReadyDocumentViewingFirstOnPublicComputers -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: - -- $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. - -- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. - -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 on the Set-OwaVirtualDirectory cmdlet). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FreCardsEnabled -This parameter is available only in the cloud-based service. - -The FreCardsEnabled parameter specifies whether the theme, signature, and phone cards are available in Outlook on the web. Valid values are: - -- $true: The theme, signature, and phone cards are visible in Outlook on the web. This is the default value. - -- $false: The theme, signature, and phone cards aren't visible in Outlook on the web. Only the introduction, time zone, and final cards are visible. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GlobalAddressListEnabled -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. - -- $false: The global address list isn't visible in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupCreationEnabled -This parameter is available or functional only in the cloud-based service. - -The GroupCreationEnabled parameter specifies whether Office 365 group creation is available in Outlook and Outlook on the web. Valid values are: - -- $true: Users can create Office 365 groups in Outlook and Outlook on the web. This is the default value. - -- $false: Users can't create Office 365 groups in Outlook and Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InstantMessagingEnabled -The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. Valid values are: - -- $true: Instant messaging is available in Outlook on the web. This is the default value. - -- $false: Instant messaging isn't available in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InstantMessagingType -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. - -- Ocs: Lync or Skype (formerly known as Office Communication Server). This is the default value in Exchange Online. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InterestingCalendarsEnabled -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: - -- $true: Interesting calendars are available in Outlook on thew web. This is the default value. - -- $false: Interesting calendars aren't available in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalSPMySiteHostURL -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 for Business to appear as regular file attachments in messages. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IRMEnabled -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. - -- $false: IRM isn't available in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefault -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JournalEnabled -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. - -- $false: The Journal folder isn't visible in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JunkEmailEnabled -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: - -- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value. - -- $false: The Junk Email folder and junk email management aren't available in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LinkedInEnabled -This parameter is available only in the cloud-based service. - -LinkedIn integration is no longer supported. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalEventsEnabled -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: - -- $true: Local events are available in Outlook on the web. - -- $false: Local events aren't available in Outlook on the web. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogonAndErrorLanguage -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. - -The default value is 0, which means the logon and error language selection is undefined. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotesEnabled -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. - -- $false: The Notes folder isn't visible in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NPSMailboxPolicy -This parameter is avaialble only in the cloud-based service. - -The NPSMailboxPolicy parameter specifies whether to enable or disable the Net Promoter Score (NPS) survey in Outlook on the web. The survey allows uses 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: - -- $true: The NPS survey is available in Outlook on the web. This is the default value. - -- $false: The NPS survey isn't available in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveAttachmentsEnabled -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. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnSendAddinsEnabled -The OnSendAddinsEnabled parameter specifies whether to enable or disable on send add-ins in Outlook on the web (add-ins that support events when a user clicks Send). Valid values are: - -- $true: On send add-ins are enabled. - -- $false: On send add-ins are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutboundCharset -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. - -- AlwaysUTF8: Always use UTF-8 encoded UNICODE characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. - -- UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutlookBetaToggleEnabled -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: - -- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This is the default value. - -- $false: Outlook on the web Preview is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OWALightEnabled -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. - -- $false: The light version of Outlook on the web is isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OWAMiniEnabled -This parameter is available or functional only in Exchange Server 2010. - -The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are: - -- $true: The mini version of Outlook Web App is available. This is the default value. - -- $false: The mini version of Outlook Web App isn't available. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PersonalAccountCalendarsEnabled -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: - -- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This is the default value. - -- $false: Users can't connect to their Outlook.com or Google Calendar in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneticSupportEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PlacesEnabled -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: - -- $true: Places is enabled. This is the default value. - -- $false: Places is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PremiumClientEnabled -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. - -- $false: The full version of Outlook Web App isn't available. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrintWithoutDownloadEnabled -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: - -- $true: Supported files can be printed without being downloaded in Outlook web app. This is the default value. - -- $false: Supported files must be downloaded before they can be printed in Outlook web app. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFoldersEnabled -This parameter is available or 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: - -- $true: Public folders are available in Outlook Web App. This is the default value. - -- $false: Public folders aren't available in Outlook Web App. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecoverDeletedItemsEnabled -This parameter is available or 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: - -- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value. - -- $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReferenceAttachmentsEnabled -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. - -- $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemindersAndNotificationsEnabled -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. - -- $false: Notifications and reminders are disabled in Outlook on the web. - -This parameter doesn't apply to the light version of Outlook Web App. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportJunkEmailEnabled -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. - -- $false: Selecting a message in the Junk Email folder and clicking Not junk \> Not junk moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking Junk \> Junk moves the message to the Junk Email folder with no 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. - -This parameter is meaningful only when the JunkEmailEnabled parameter is set 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RulesEnabled -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. - -- $false: Users can't view, create, or modify server-side rules in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SatisfactionEnabled -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. - -- $false: The satisfaction survey is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SaveAttachmentsToCloudEnabled -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. - -- $false: Users can only save regular email attachments locally. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchFoldersEnabled -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. - -- $false: Search Folders aren't visible in Outlook on the Web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SetPhotoEnabled -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. - -- $false: Users can't manage their user photo in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SetPhotoURL -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignaturesEnabled -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. - -- $false: Signatures aren't available in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SilverlightEnabled -This parameter is available or 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: - -- $true: Silverlight features are available in Outlook Web App. This is the default value. - -- $false: Silverlight features aren't available in Outlook Web App. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipCreateUnifiedGroupCustomSharepointClassification -This parameter is available only in the cloud-based service. - -The SkipCreateUnifiedGroupCustomSharepointClassification parameter specifies whether to skip a custom SharePoint page during the creation of Office 365 Groups in Outlook web app. Valid values are: - -- $true: The custom SharePoint page is skipped when a user creates an Office 365 group in Outlook on the web. This is the default value. - -- $false: The custom SharePoint page is shown when a user creates an Office 365 group in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SMimeEnabled -This parameter is available or 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: - -- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value. - -- $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated. - -**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://docs.microsoft.com/Exchange/policy-and-compliance/smime). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpellCheckerEnabled -This parameter is available or 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: - -- $true: Spell checking is available in Outlook Web App. This is the default value. - -- $false: Spell checking isn't available in Outlook Web App. - -This parameter doesn't apply to the light version of Outlook Web App. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TasksEnabled -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: - -- $true: The Tasks folder is available in Outlook Web App. This is the default value. - -- $false: The Tasks folder isn't available in Outlook Web App. - -This parameter doesn't apply to the light version of Outlook Web App. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamSnapCalendarsEnabled -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: - -- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This is the default value. - -- $false: Users can't connect to their TeamSnap calendars in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TextMessagingEnabled -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. - -- $false: Text messaging isn't available in Outlook on the web. - -This parameter doesn't apply to the light version of Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThemeSelectionEnabled -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. - -- $false: Users can't specify or change the theme in Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThirdPartyAttachmentsEnabled -This parameter is available only in the cloud-based service. - -This parameter has been deprecated and is no longer used. - -To enable or disable third party attachments in Outlook on the web, use the AdditionalStorageProvidersAvailable parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThirdPartyFileProvidersEnabled -This parameter is available only in the cloud-based service. - -This parameter has been deprecated and is no longer used. - -To enable or disable third party attachments in Outlook on the web, use the AdditionalStorageProvidersAvailable parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UMIntegrationEnabled -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. - -- $false: UM integration is disabled in Outlook on the web. - -This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). - -This parameter doesn't apply to the light version of Outlook on the web. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UNCAccessOnPrivateComputersEnabled -This parameter is available only in on-premises Exchange. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UNCAccessOnPublicComputersEnabled -This parameter is available only in on-premises Exchange. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseGB18030 -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. - -- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseISO885915 -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. - -- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserVoiceEnabled -This parameter is available 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 Office 365. Valid values are: - -- $true: Outlook UserVoice is enabled. This is the default value. - -- $false: Outlook UserVoice is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WacEditingEnabled -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. - -- $false: Users can't edit supported documents in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WacExternalServicesEnabled -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. - -- $false: External services are disabled when viewing supported documents in Outlook on the web. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WacOMEXEnabled -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. - -- $false: apps for Outlook are disabled in Outlook on the web. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WacViewingOnPrivateComputersEnabled -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. - -- $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. - -By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WacViewingOnPublicComputersEnabled -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. - -- $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. - -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 on the Set-OwaVirtualDirectory cmdlet). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WeatherEnabled -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: - -- $true: Weather is enabled. This is the default value. - -- $false: Weather is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebPartsFrameOptionsType -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. - -- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. - -- Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it. - -```yaml -Type: WebPartsFrameOptions -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebReadyDocumentViewingForAllSupportedTypes -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: - -- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value. - -- $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebReadyDocumentViewingOnPrivateComputersEnabled -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: - -- $true: WebReady Document Viewing is available in private computer sessions. This is the default value. - -- $false: WebReady Document Viewing isn't available in private computer sessions. - -By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebReadyDocumentViewingOnPublicComputersEnabled -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: - -- $true: WebReady Document Viewing is available for public computer sessions. This is the default value. - -- $false: WebReady Document Viewing isn't available for public computer sessions. - -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 on the Set-OwaVirtualDirectory cmdlet). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebReadyDocumentViewingSupportedFileTypes -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebReadyDocumentViewingSupportedMimeTypes -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebReadyFileTypes -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: - -- .doc - -- .docx - -- .dot - -- .pdf - -- .pps - -- .ppt - -- .pptx - -- .rtf - -- .xls - -- .xlsx - -You can only remove or add values from within the list of supported file types (you can't add additional values). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parameter is set to $false. Otherwise, all supported file types are available in WebReady Document Viewing. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebReadyMimeTypes -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: - -- application/msword - -- application/pdf - -- application/vnd.ms-excel - -- application/vnd.ms-powerpoint - -- application/vnd.openxmlformats-officedocument.presentationml.presentation - -- application/vnd.openxmlformats-officedocument.spreadsheetml.sheet - -- application/vnd.openxmlformats-officedocument.wordprocessingml.document - -- application/x-msexcel - -- application/x-mspowerpoint - -You can only remove or add values from within the list of supported file types (you can't add additional values). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parameter is set to $false. Otherwise, all supported MIME types are available in WebReady Document Viewing. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WSSAccessOnPrivateComputersEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WSSAccessOnPublicComputersEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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 - -[New-OwaMailboxPolicy](https://docs.microsoft.com/powershell/module/exchange/client-access/new-owamailboxpolicy) - -[Get-OwaMailboxPolicy](https://docs.microsoft.com/powershell/module/exchange/client-access/get-owamailboxpolicy) - -[Set-CASMailbox](https://docs.microsoft.com/powershell/module/exchange/client-access/set-casmailbox) - -[Outlook on the web mailbox policy procedures in Exchange Online](https://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-on-the-web/outlook-web-app-mailbox-policy-procedures) diff --git a/exchange/exchange-ps/exchange/client-access/Test-ClientAccessRule.md b/exchange/exchange-ps/exchange/client-access/Test-ClientAccessRule.md deleted file mode 100644 index 3cb9768f66..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Test-ClientAccessRule.md +++ /dev/null @@ -1,276 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-clientaccessrule -applicable: Exchange Server 2019, Exchange Online -title: Test-ClientAccessRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# Test-ClientAccessRule - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Test-ClientAccessRule cmdlet to test how client access rules affect access to your organization. If any of the client properties you specify for this cmdlet match any client access rules, the rules are returned in the results. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Test-ClientAccessRule - -AuthenticationType <ClientAccessAuthenticationMethod> - -Protocol <ClientAccessProtocol> -RemoteAddress <IPAddress> -RemotePort <Int32> -User <MailboxIdParameter> [-Confirm] - [-OAuthClaims <Hashtable>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. - -Note: Currently, not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list: - -- OutlookWebApp:BasicAuthentication and AdfsAuthentication. - -- ExchangeAdminCenter:BasicAuthentication and AdfsAuthentication. - -- RemotePowerShell:BasicAuthentication and NonBasicAuthentication. - -- ExchangeActiveSync:BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Test-ClientAccessRule -AuthenticationType BasicAuthentication -Protocol OutlookWebApp -RemoteAddress 172.17.17.26 -RemotePort 443 -User julia@contoso.com -``` - -This example tests client access by using the following client properties: - -- Authentication type: Basic - -- Protocol:OutlookWebApp - -- Remote address: 172.17.17.26 - -- Remote port: 443 - -- User: julia@contoso.com - -## PARAMETERS - -### -AuthenticationType -The AuthenticationType parameter specifies the client authentication type to test. - -Valid values for this parameter are: - -- AdfsAuthentication - -- BasicAuthentication - -- CertificateBasedAuthentication - -- NonBasicAuthentication - -- OAuthAuthentication - -In client access rules, authentication types are defined by the AnyOfAuthenticationTypes and ExceptAnyOfAuthenticationTypes parameters. - -```yaml -Type: ClientAccessAuthenticationMethod -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Protocol -The Protocol parameter specifies the client protocol to test. - -Valid values for this parameter are: - -- ExchangeActiveSync - -- ExchangeAdminCenter - -- ExchangeWebServices - -- IMAP4 - -- OfflineAddressBook - -- OutlookAnywhere - -- OutlookWebApp - -- POP3 - -- PowerShellWebServices - -- RemotePowerShell - -- REST - -In client access rules, protocol types are defined by the AnyOfProtocols and ExceptAnyOfProtocols parameters. - -```yaml -Type: ClientAccessProtocol -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteAddress -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. - -```yaml -Type: IPAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemotePort -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 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -The User parameter specifies the user account to test. You can use any value that uniquely identifies the user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -In client access rules, users are defined by the UsernameMatchesAnyOfPatterns, UserRecipientFilter, and ExceptUsernameMatchesAnyOfPatterns parameters. - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OAuthClaims -The OAuthClaims parameter specifies the OAuth claims token of a middle-tier app. - -```yaml -Type: Hashtable -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/client-access/Test-OutlookWebServices.md b/exchange/exchange-ps/exchange/client-access/Test-OutlookWebServices.md deleted file mode 100644 index 6a2cb739f9..0000000000 --- a/exchange/exchange-ps/exchange/client-access/Test-OutlookWebServices.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/test-outlookwebservices -applicable: Exchange Server 2010 -title: Test-OutlookWebServices -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010" ---- - -# Test-OutlookWebServices - -## SYNOPSIS -This cmdlet is available only in Exchange Server 2010. - -Use the Test-OutlookWebServices cmdlet to verify the Autodiscover service settings for Microsoft Outlook on a computer running Microsoft Exchange Server 2010 that has the Client Access server role installed. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Test-OutlookWebServices [[-Identity] <RecipientIdParameter>] - [-ClientAccessServer <ClientAccessServerIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-MonitoringContext <Boolean>] [-TargetAddress <RecipientIdParameter[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Test-OutlookWebServices cmdlet uses a specified address to verify that the Outlook provider is configured correctly. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Test-OutlookWebServices -Identity:holly@contoso.com -``` - -This example verifies the service information that's returned to the Outlook client from the Autodiscover service for the user holly@contoso.com. The code example verifies information for the following services: - -- Availability service - -- Outlook Anywhere - -- Offline address book - -- Unified Messaging - -The example tests for a connection to each service. The example also submits a request to the Availability service for the user holly@contoso.com to determine whether the user's free/busy information is being returned correctly from the Client Access server to the Outlook client. - -## PARAMETERS - -### -ClientAccessServer -This parameter is available or functional only in Exchange Server 2010. - -The ClientAccessServer parameter specifies the Client Access server that the client accesses. - -```yaml -Type: ClientAccessServerIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -MonitoringContext -The MonitoringContext parameter specifies whether the results of the command include monitoring events and performance counters. The two possible values for this parameter are $true or $false. If you specify $true, the results include monitoring events and performance counters, in addition to information about the MAPI transaction. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetAddress -The TargetAddress parameter specifies the recipient that's used to test whether Availability service data can be retrieved. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/client-access/set-CASMailboxPlan.md b/exchange/exchange-ps/exchange/client-access/set-CASMailboxPlan.md deleted file mode 100644 index 3fbef5593d..0000000000 --- a/exchange/exchange-ps/exchange/client-access/set-CASMailboxPlan.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/client-access/set-casmailboxplan -applicable: Exchange Online -title: Set-CASMailboxPlan -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-CASMailboxPlan - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-CASMailboxPlan cmdlet to modify Client Access services (CAS) mailbox plans in cloud-based organizations. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-CASMailboxPlan [-Identity] <MailboxPlanIdParameter> - [-ActiveSyncEnabled <Boolean>] - [-Confirm] - [-ImapEnabled <Boolean>] - [-OwaMailboxPolicy <MailboxPolicyIdParameter>] - [-PopEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-CASMailboxPlan -Identity ExchangeOnlineEnterprise -ActiveSyncEnabled $false -PopEnabled $false -``` - -This example disables Exchange ActiveSync and POP3 access to mailboxes in the CAS mailbox plan named ExchangeOnlineEnterprise. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -The display name and name of the CAS mailbox plan is the same as the corresponding mailbox plan (for example, ExchangeOnlineEnterprise and ExchangeOnlineEnterprise-\<GUID\>, respectively). - -```yaml -Type: MailboxPlanIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ActiveSyncEnabled -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. - -- $false: ActiveSync access to the mailbox is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImapEnabled -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. - -- $false: IMAP4 access to the mailbox is disabled. This is default value for ExchangeOnlineDeskless. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OwaMailboxPolicy -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 - -- Distinguished name (DN) - -- GUID - -The default value is OwaMailboxPolicy-Default. - -You can use the Get-OwaMailboxPolicy cmdlet to view the available Outlook on the web mailbox policies. - -```yaml -Type: MailboxPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopEnabled -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. - -- $false: POP3 access to the mailbox is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/devices/Get-DeviceConditionalAccessPolicy.md deleted file mode 100644 index d2f58ac8a6..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-DeviceConditionalAccessPolicy.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-deviceconditionalaccesspolicy -applicable: Office 365 Security & Compliance Center -title: Get-DeviceConditionalAccessPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DeviceConditionalAccessPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DeviceConditionalAccessPolicy cmdlet to view mobile device conditional access policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DeviceConditionalAccessPolicy [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DeviceConditionalAccessPolicy | Format-Table Name,Enabled,Priority -``` - -This example shows summary information for all mobile device conditional access policies. - -### Example 2 -```powershell -Get-DeviceConditionalAccessPolicy -Identity "Human Resources" -``` - -This example shows details about the mobile device conditional access policy named Human Resources. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/devices/Get-DeviceConditionalAccessRule.md deleted file mode 100644 index 24f0481a22..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-DeviceConditionalAccessRule.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-deviceconditionalaccessrule -applicable: Office 365 Security & Compliance Center -title: Get-DeviceConditionalAccessRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DeviceConditionalAccessRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DeviceConditionalAccessRule cmdlet to view mobile device conditional access rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DeviceConditionalAccessRule [[-Identity] <ComplianceRuleIdParameter>] [-CompareToWorkload] - [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DeviceConditionalAccessRule | Format-List Name,Disabled,Priority -``` - -This example shows a summary list of all mobile device conditional access rules. - -### Example 2 -```powershell -Get-DeviceConditionalAccessRule -Identity "Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}" -``` - -This example shows details for the mobile device conditional access rule named Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}. - -## PARAMETERS - -### -CompareToWorkload -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mobile device conditional access rule that you want to view. The name of the rule uses the syntax \<Mobile device conditional access policy name\>{\<GUID value\>}. For example, Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/devices/Get-DeviceConfigurationPolicy.md deleted file mode 100644 index 9f80cc7c89..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-DeviceConfigurationPolicy.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-deviceconfigurationpolicy -applicable: Office 365 Security & Compliance Center -title: Get-DeviceConfigurationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DeviceConfigurationPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DeviceConfigurationPolicy cmdlet to view mobile device configuration policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DeviceConfigurationPolicy [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DeviceConfigurationPolicy | Format-Table Name,Enabled,Priority -``` - -This example shows summary information for all mobile device configuration policies. - -### Example 2 -```powershell -Get-DeviceConfigurationPolicy -Identity "Engineering Group" -``` - -This example shows details about the mobile device configuration policy named Engineering Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/devices/Get-DeviceConfigurationRule.md deleted file mode 100644 index db11285776..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-DeviceConfigurationRule.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-deviceconfigurationrule -applicable: Office 365 Security & Compliance Center -title: Get-DeviceConfigurationRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DeviceConfigurationRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DeviceConfigurationRule cmdlet to view mobile device configuration rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DeviceConfigurationRule [[-Identity] <ComplianceRuleIdParameter>] [-CompareToWorkload] - [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DeviceConfigurationRule | Format-List Name,Disabled,Priority -``` - -This example shows summary information for all mobile device configuration rules. - -### Example 2 -```powershell -Get-DeviceConfigurationRule -Identity "Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}" -``` - -This example shows details about the mobile device configuration rule named Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136} - -## PARAMETERS - -### -CompareToWorkload -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mobile device configuration rule that you want to view. The name of the rule uses the syntax \<Mobile device configuration policy name\>{\<GUID value\>}. For example, Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-DevicePolicy.md b/exchange/exchange-ps/exchange/devices/Get-DevicePolicy.md deleted file mode 100644 index c44e43f32f..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-DevicePolicy.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-devicepolicy -applicable: Office 365 Security & Compliance Center -title: Get-DevicePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DevicePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DevicePolicy cmdlet to view mobile device polices (regardless of type) in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DevicePolicy [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DevicePolicy | Format-Table Name,Type,Enabled,Priority -``` - -This example shows summary information for all mobile device policies. - -### Example 2 -```powershell -Get-DevicePolicy -Identity "Engineering Group" -``` - -This example shows details about the mobile device policy named Engineering Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/devices/Get-DeviceTenantPolicy.md deleted file mode 100644 index ea8b250b4e..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-DeviceTenantPolicy.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-devicetenantpolicy -applicable: Office 365 Security & Compliance Center -title: Get-DeviceTenantPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DeviceTenantPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DeviceTenantPolicy cmdlet to view your organization's mobile device tenant policy in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DeviceTenantPolicy [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DeviceTenantPolicy -``` - -This example shows information for your organization's mobile device tenant policy. - -## PARAMETERS - -### -Identity -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: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-DeviceTenantRule.md b/exchange/exchange-ps/exchange/devices/Get-DeviceTenantRule.md deleted file mode 100644 index e31ce4af42..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-DeviceTenantRule.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-devicetenantrule -applicable: Office 365 Security & Compliance Center -title: Get-DeviceTenantRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DeviceTenantRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DeviceTenantRule cmdlet to view your organization's mobile device tenant rule in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DeviceTenantRule [[-Identity] <ComplianceRuleIdParameter>] [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DeviceTenantRule -``` - -This example shows information for your organization's mobile device tenant rule. - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Get-MobileDeviceStatistics.md b/exchange/exchange-ps/exchange/devices/Get-MobileDeviceStatistics.md deleted file mode 100644 index 1995b2a8f4..0000000000 --- a/exchange/exchange-ps/exchange/devices/Get-MobileDeviceStatistics.md +++ /dev/null @@ -1,290 +0,0 @@ ---- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/get-mobiledevicestatistics -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-MobileDeviceStatistics -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MobileDeviceStatistics - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MobileDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices. - -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXOMobileDeviceStatistics cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity -``` -Get-MobileDeviceStatistics [-Identity] <MobileDeviceIdParameter> - [-ActiveSync] - [-DomainController <Fqdn>] - [-GetMailboxLog] - [-NotificationEmailAddresses <MultiValuedProperty>] - [-OWAforDevices] - [-ShowRecoveryPassword] - [-RestApi] - [-UniversalOutlook] [<CommonParameters>] -``` - -### Mailbox -``` -Get-MobileDeviceStatistics -Mailbox <MailboxIdParameter> - [-ActiveSync] - [-DomainController <Fqdn>] - [-GetMailboxLog] - [-NotificationEmailAddresses <MultiValuedProperty>] - [-OWAforDevices] - [-ShowRecoveryPassword] - [-RestApi] - [-UniversalOutlook] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-MobileDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MobileDeviceStatistics -Identity TonySmith -``` - -This example retrieves the statistics for the mobile phone configured to synchronize with the mailbox that belongs to the user Tony Smith. - -### Example 2 -```powershell -$UserList = Get-CASMailbox -Filter "HasActiveSyncDevicePartnership -eq `$true -and -not DisplayName -like 'CAS_{*'" | Get-Mailbox; $UserList | foreach {Get-MobileDeviceStatistics -Mailbox $_.Identity} -``` - -This example uses the Get-CASMailbox cmdlet to determine who in the organization has an Exchange ActiveSync mobile device. For each mobile device, the Exchange ActiveSync device statistics are retrieved. - -**Note**: For more information about OPath filter syntax, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -### Example 3 -```powershell -Get-MobileDeviceStatistics -Mailbox TonySmith -GetMailboxLog $true -NotificationEmailAddresses "admin@contoso.com" -``` - -This example retrieves the statistics for the mobile phone configured to synchronize with the mailbox that belongs to the user Tony Smith. It also outputs the Exchange ActiveSync log file and sends it to the System Administrator at admin@contoso.com. - -## PARAMETERS - -### -Identity -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 - -- DeviceID - -You can't use this parameter with the Mailbox parameter. - -```yaml -Type: MobileDeviceIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Mailbox -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -You can't use this parameter with the Identity parameter. - -```yaml -Type: MailboxIdParameter -Parameter Sets: Mailbox -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ActiveSync -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GetMailboxLog -The GetMailboxLog parameter specifies whether to send the mailbox logs via email to the administrator running the task. If the parameter is set to $true, the command sends the mailbox logs via email to the administrator running the task. The default value of this parameter is $false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationEmailAddresses -The NotificationEmailAddresses parameter specifies an optional list of comma-separated aliases or email addresses where the mailbox logs are sent. If the GetMailboxLog parameter is set to $false, this parameter is ignored. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OWAforDevices -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowRecoveryPassword -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 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestApi -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UniversalOutlook -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/devices/New-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/devices/New-DeviceConditionalAccessPolicy.md deleted file mode 100644 index 11bc44a8f5..0000000000 --- a/exchange/exchange-ps/exchange/devices/New-DeviceConditionalAccessPolicy.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-deviceconditionalaccesspolicy -applicable: Office 365 Security & Compliance Center -title: New-DeviceConditionalAccessPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DeviceConditionalAccessPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DeviceConditionalAccessPolicy cmdlet to create mobile device conditional access policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DeviceConditionalAccessPolicy [-Name] <String> [-Comment <String>] [-Confirm] [-Enabled <Boolean>] - [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-DeviceConditionalAccessPolicy -Identity "Human Resources" -``` - -This example creates a new mobile device conditional access policy named Human Resources - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/New-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/devices/New-DeviceConfigurationPolicy.md deleted file mode 100644 index cbf5c624fc..0000000000 --- a/exchange/exchange-ps/exchange/devices/New-DeviceConfigurationPolicy.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-deviceconfigurationpolicy -applicable: Office 365 Security & Compliance Center -title: New-DeviceConfigurationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DeviceConfigurationPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DeviceConfigurationPolicy cmdlet to create mobile device configuration policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DeviceConfigurationPolicy [-Name] <String> [-Comment <String>] [-Confirm] [-Enabled <Boolean>] - [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-DeviceConfigurationPolicy -Name "Engineering Group" -``` - -This example creates a new mobile device configuration policy named Engineering Group. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/New-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/devices/New-DeviceTenantPolicy.md deleted file mode 100644 index 3dd3bcd0db..0000000000 --- a/exchange/exchange-ps/exchange/devices/New-DeviceTenantPolicy.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-devicetenantpolicy -applicable: Office 365 Security & Compliance Center -title: New-DeviceTenantPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DeviceTenantPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DeviceTenantPolicy cmdlet to create your organization's mobile device tenant policy in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DeviceTenantPolicy [-Comment <String>] [-Confirm] [-Enabled <Boolean>] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-DeviceTenantPolicy -``` - -This example creates your organization's mobile device tenant policy. You can have only one mobile device tenant policy in your organization. - -## PARAMETERS - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/New-DeviceTenantRule.md b/exchange/exchange-ps/exchange/devices/New-DeviceTenantRule.md deleted file mode 100644 index 83813bb8f2..0000000000 --- a/exchange/exchange-ps/exchange/devices/New-DeviceTenantRule.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/new-devicetenantrule -applicable: Office 365 Security & Compliance Center -title: New-DeviceTenantRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DeviceTenantRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DeviceTenantRule cmdlet to create your organization's mobile device tenant rule in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DeviceTenantRule [-ApplyPolicyTo <PolicyResourceScope>] - [-BlockUnsupportedDevices <Boolean>] [-Confirm] [-DomainController <Fqdn>] - [-ExclusionList <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-DeviceTenantRule -ExclusionList "e10214c1-49b6-47d2-b5e6-466e918648b1","6e3931bd-a716-4bb9-9a2f-093aa2c967b4" -``` - -This example creates a new mobile device tenant rule with GUIDs of the security groups named Engineering and Research and Development on the exclusion list. Members of these groups are allowed access even if they use non-compliant devices - -You can have only one mobile device tenant rule in your organization. - -## PARAMETERS - -### -ApplyPolicyTo -The ApplyPolicyTo parameter specifies where to apply the policy in your organization. Valid values for this parameter are: - -- ExchangeOnline - -- SharePointOnline - -- ExchangeAndSharePoint - -```yaml -Type: PolicyResourceScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockUnsupportedDevices -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. - -- $false: Unsupported devices are allowed. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExclusionList -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. - -You can specify multiple groups separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Remove-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/devices/Remove-DeviceConditionalAccessPolicy.md deleted file mode 100644 index 175f082f14..0000000000 --- a/exchange/exchange-ps/exchange/devices/Remove-DeviceConditionalAccessPolicy.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-deviceconditionalaccesspolicy -applicable: Office 365 Security & Compliance Center -title: Remove-DeviceConditionalAccessPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DeviceConditionalAccessPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DeviceConditionalAccessPolicy cmdlet to remove mobile device conditional access policies from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DeviceConditionalAccessPolicy [-Identity] <PolicyIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DeviceConditionalAccessPolicy -Identity "Human Resources" -``` - -This example removes the mobile device conditional access policy named Human Resources. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Remove-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/devices/Remove-DeviceConditionalAccessRule.md deleted file mode 100644 index 077395c01b..0000000000 --- a/exchange/exchange-ps/exchange/devices/Remove-DeviceConditionalAccessRule.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-deviceconditionalaccessrule -applicable: Office 365 Security & Compliance Center -title: Remove-DeviceConditionalAccessRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DeviceConditionalAccessRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DeviceConditionalAccessRule cmdlet to remove mobile device conditional access rules from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DeviceConditionalAccessRule [-Identity] <PolicyIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DeviceConditionalAccessRule "Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}" -``` - -This example removes the mobile device conditional access rule named Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mobile device conditional access rule that you want to view. The name of the rule uses the syntax \<Mobile device conditional access policy name\>{\<GUID value\>}. 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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Remove-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/devices/Remove-DeviceConfigurationPolicy.md deleted file mode 100644 index e0f421e064..0000000000 --- a/exchange/exchange-ps/exchange/devices/Remove-DeviceConfigurationPolicy.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-deviceconfigurationpolicy -applicable: Office 365 Security & Compliance Center -title: Remove-DeviceConfigurationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DeviceConfigurationPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DeviceConfigurationPolicy cmdlet to remove mobile device configuration policies from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DeviceConfigurationPolicy [-Identity] <PolicyIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DeviceConfigurationPolicy -Identity "Engineering Group" -``` - -This example removes the mobile device configuration policy named Engineering Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Remove-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/devices/Remove-DeviceConfigurationRule.md deleted file mode 100644 index 9b48adba15..0000000000 --- a/exchange/exchange-ps/exchange/devices/Remove-DeviceConfigurationRule.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-deviceconfigurationrule -applicable: Office 365 Security & Compliance Center -title: Remove-DeviceConfigurationRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DeviceConfigurationRule - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-DeviceConfigurationRule cmdlet to remove mobile device configuration rules from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DeviceConfigurationRule [-Identity] <PolicyIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DeviceConfigurationRule "Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}" -``` - -This example removes the mobile device configuration rule named Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mobile device configuration rule that you want to view. The name of the rule uses the syntax \<Mobile device configuration policy name\>{\<GUID value\>}. 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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Remove-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/devices/Remove-DeviceTenantPolicy.md deleted file mode 100644 index 3071744187..0000000000 --- a/exchange/exchange-ps/exchange/devices/Remove-DeviceTenantPolicy.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-devicetenantpolicy -applicable: Office 365 Security & Compliance Center -title: Remove-DeviceTenantPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DeviceTenantPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DeviceTenantPolicy cmdlet to remove your organization's mobile device tenant policy from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DeviceTenantPolicy [-Confirm] [-Identity <PolicyIdParameter>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DeviceTenantPolicy -``` - -This example removes your organization's mobile device tenant policy. - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Remove-DeviceTenantRule.md b/exchange/exchange-ps/exchange/devices/Remove-DeviceTenantRule.md deleted file mode 100644 index fc9881f345..0000000000 --- a/exchange/exchange-ps/exchange/devices/Remove-DeviceTenantRule.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/remove-devicetenantrule -applicable: Office 365 Security & Compliance Center -title: Remove-DeviceTenantRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DeviceTenantRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DeviceTenantRule cmdlet to remove your organization's mobile device tenant rule from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DeviceTenantRule [-Confirm] [-Identity <PolicyIdParameter>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DeviceTenantRule -``` - -This example removes the mobile device tenant rule from your organization. - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/devices/Set-DeviceConditionalAccessPolicy.md deleted file mode 100644 index 6ae8c8a2d6..0000000000 --- a/exchange/exchange-ps/exchange/devices/Set-DeviceConditionalAccessPolicy.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-deviceconditionalaccesspolicy -applicable: Office 365 Security & Compliance Center -title: Set-DeviceConditionalAccessPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DeviceConditionalAccessPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DeviceConditionalAccessPolicy cmdlet to modify mobile device conditional access policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### RetryDistribution -``` -Set-DeviceConditionalAccessPolicy [-Identity] <PolicyIdParameter> [-RetryDistribution] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Set-DeviceConditionalAccessPolicy [-Identity] <PolicyIdParameter> [-Comment <String>] [-Enabled <Boolean>] [-Force] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-DeviceConditionalAccessPolicy -Identity Executives -Enabled $false -``` - -This example disables the existing mobile device conditional access policy named Executives. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RetryDistribution -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/devices/Set-DeviceConfigurationPolicy.md deleted file mode 100644 index 10d27031d7..0000000000 --- a/exchange/exchange-ps/exchange/devices/Set-DeviceConfigurationPolicy.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-deviceconfigurationpolicy -applicable: Office 365 Security & Compliance Center -title: Set-DeviceConfigurationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DeviceConfigurationPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DeviceConfigurationPolicy cmdlet to modify mobile device configuration policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### RetryDistribution -``` -Set-DeviceConfigurationPolicy [-Identity] <PolicyIdParameter> [-RetryDistribution] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Set-DeviceConfigurationPolicy [-Identity] <PolicyIdParameter> [-Comment <String>] [-Enabled <Boolean>] [-Force] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-DeviceConfigurationPolicy -Identity "Engineering Group" -Enabled $false -``` - -This example disables the mobile device configuration policy named Engineering Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RetryDistribution -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/devices/Set-DeviceTenantPolicy.md deleted file mode 100644 index 4faece3b83..0000000000 --- a/exchange/exchange-ps/exchange/devices/Set-DeviceTenantPolicy.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-devicetenantpolicy -applicable: Office 365 Security & Compliance Center -title: Set-DeviceTenantPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DeviceTenantPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DeviceTenantPolicy cmdlet to modify your organization's mobile device tenant policy in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### RetryDistribution -``` -Set-DeviceTenantPolicy [-Identity <PolicyIdParameter>] [-RetryDistribution] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Set-DeviceTenantPolicy [-Identity <PolicyIdParameter>] [-Comment <String>] [-Enabled <Boolean>] [-Force] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-DeviceTenantPolicy -Enabled $false -``` - -This example disables your organization's mobile device tenant policy. - -## PARAMETERS - -### -RetryDistribution -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/devices/Set-DeviceTenantRule.md b/exchange/exchange-ps/exchange/devices/Set-DeviceTenantRule.md deleted file mode 100644 index 3162639645..0000000000 --- a/exchange/exchange-ps/exchange/devices/Set-DeviceTenantRule.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/devices/set-devicetenantrule -applicable: Office 365 Security & Compliance Center -title: Set-DeviceTenantRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DeviceTenantRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DeviceTenantRule cmdlet to modify your organization's mobile device tenant rule in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-DeviceTenantRule [-Identity] <ComplianceRuleIdParameter> - [-ApplyPolicyTo <PolicyResourceScope>] - [-BlockUnsupportedDevices <Boolean>] [-Confirm] [-DomainController <Fqdn>] - [-ExclusionList <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -These are the cmdlets that are used for mobile device management in the Security & Compliance Center: - -- DeviceTenantPolicy and DeviceTenantRule cmdlets: A policy that defines whether to block or allow mobile device access to Office 365 email by unsupported devices that use Exchange ActiveSync only. This setting applies to all users in your organization. Both allow and block scenarios allow reporting for unsupported devices, and you can specify exceptions to the policy based on security groups. - -- DeviceConditionalAccessPolicy and DeviceConditionalAccessRule cmdlets: Policies that control mobile device access to Office 365 for supported devices. These policies are applied to security groups. Unsupported devices are not allowed to enroll in mobile device management. - -- DeviceConfigurationPolicy and DeviceConfigurationRule cmdlets: Policies that control mobile device settings for supported devices. These policies are applied to security groups. - -- Get-DevicePolicy: Returns all mobile device management policies regardless of type (DeviceTenantPolicy, DeviceConditionalAccessPolicy or DeviceConfigurationPolicy). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-DeviceTenantRule -ExclusionList "Research and Development" -``` - -This example modifies your organization's mobile device tenant rule by replacing the current exclusion list with the security group named Research and Development. Members of this group are allowed access even if they use non-compliant devices. - -## PARAMETERS - -### -Identity -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ApplyPolicyTo -The ApplyPolicyTo parameter specifies where to apply the policy in your organization. Valid values for this parameter are: - -- ExchangeOnline - -- SharePointOnline - -- ExchangeAndSharePoint - -```yaml -Type: PolicyResourceScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockUnsupportedDevices -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. - -- $false: Unsupported devices are allowed. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExclusionList -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-EmailAddressPolicy.md deleted file mode 100644 index 526753a096..0000000000 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Get-EmailAddressPolicy.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/get-emailaddresspolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-EmailAddressPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-EmailAddressPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-EmailAddressPolicy cmdlet to view email address policies. In Exchange Online, email address policies are only available for Office 365 groups. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-EmailAddressPolicy [[-Identity] <EmailAddressPolicyIdParameter>] - [-DomainController <Fqdn>] - [-IncludeMailboxSettingOnlyPolicy] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-EmailAddressPolicy -``` - -This example returns a summary list of all email address policies in the organization. - -### Example 2 -```powershell -Get-EmailAddressPolicy -Identity "Contoso Employees" -``` - -This example returns detailed information for the email address policy named Contoso Employees. - -## PARAMETERS - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: EmailAddressPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IncludeMailboxSettingOnlyPolicy -This parameter is available or functional only in Exchange Server 2010. - -The IncludeMailboxSettingOnlyPolicy parameter retrieves Microsoft Exchange Server 2003 address policies that contain only mailbox management configuration. Microsoft Exchange Server 2010 supports both policies that contain only address policy settings and policies that contain address policy settings and mailbox management configuration. Exchange 2010 doesn't support policies that contain only mailbox management configuration, but Exchange 2003 policies that contain only mailbox management configuration are, by default, preserved and not upgraded. The IncludeMailboxSettingOnlyPolicy parameter is required to retrieve these policies. - -The attributes of address policies that contain only mailbox management configuration can't be modified in Exchange 2010. These policies can only be removed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/email-addresses-and-address-books/Set-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-EmailAddressPolicy.md deleted file mode 100644 index 5da0844cc0..0000000000 --- a/exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-EmailAddressPolicy.md +++ /dev/null @@ -1,838 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/email-addresses-and-address-books/set-emailaddresspolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-EmailAddressPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-EmailAddressPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-EmailAddressPolicy cmdlet to modify email address policies. In Exchange Online, email address policies are only available for Office 365 groups. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-EmailAddressPolicy [-Identity] <EmailAddressPolicyIdParameter> - [-ConditionalCompany <MultiValuedProperty>] - [-ConditionalCustomAttribute1 <MultiValuedProperty>] - [-ConditionalCustomAttribute10 <MultiValuedProperty>] - [-ConditionalCustomAttribute11 <MultiValuedProperty>] - [-ConditionalCustomAttribute12 <MultiValuedProperty>] - [-ConditionalCustomAttribute13 <MultiValuedProperty>] - [-ConditionalCustomAttribute14 <MultiValuedProperty>] - [-ConditionalCustomAttribute15 <MultiValuedProperty>] - [-ConditionalCustomAttribute2 <MultiValuedProperty>] - [-ConditionalCustomAttribute3 <MultiValuedProperty>] - [-ConditionalCustomAttribute4 <MultiValuedProperty>] - [-ConditionalCustomAttribute5 <MultiValuedProperty>] - [-ConditionalCustomAttribute6 <MultiValuedProperty>] - [-ConditionalCustomAttribute7 <MultiValuedProperty>] - [-ConditionalCustomAttribute8 <MultiValuedProperty>] - [-ConditionalCustomAttribute9 <MultiValuedProperty>] - [-ConditionalDepartment <MultiValuedProperty>] - [-ConditionalStateOrProvince <MultiValuedProperty>] - [-Confirm] - [-DisabledEmailAddressTemplates <ProxyAddressTemplateCollection>] - [-DomainController <Fqdn>] - [-EnabledEmailAddressTemplates <ProxyAddressTemplateCollection>] - [-EnabledPrimarySMTPAddressTemplate <String>] - [-ForceUpgrade] - [-IncludedRecipients <WellKnownRecipientType>] - [-Name <String>] - [-Priority <EmailAddressPolicyPriority>] - [-RecipientContainer <OrganizationalUnitIdParameter>] - [-RecipientFilter <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -After you use the Set-EmailAddressPolicy cmdlet to modify an email address policy in an on-premises Exchange organization, you need to use the Update-EmailAddressPolicy cmdlet to apply the updated policy to recipients. - -The Conditional parameters that are used with the IncludedRecipients parameter are subject to the following limitations: - -- The EQV operator is used for every property value, as in "Department equals Sales". Wildcards and partial matches aren't supported. - -- The OR operator is always used for multiple values of the same property, as in "Department equals Sales OR Marketing". - -- The AND operator is always used for multiple properties, as in "Department equals Sales AND Company equals Contoso". - -To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPath filter. - -You can't use this cmdlet to replace a precanned filter with a custom OPath filter, or vice-versa. You can only modify the existing filter. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-EmailAddressPolicy -Identity "Southeast Executives" -ConditionalStateOrProvince @{Add="TX"} -``` - -In on-premises Exchange, this example modifies the existing email address policy named Southeast Executives by adding the State or province value TX (Texas) to the precanned recipient filter. - -### Example 2 -```powershell -Set-EmailAddressPolicy -Identity "Contoso Corp" -DisabledEmailAddressTemplates $null -``` - -In on-premises Exchange, this example clears the disabled email address templates from the email address policy named Contoso Corp. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ConditionalCompany -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute1 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute10 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute11 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute12 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute13 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute14 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute15 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute2 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute3 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute4 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute5 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute6 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute7 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute8 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalCustomAttribute9 -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalDepartment -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalStateOrProvince -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. - -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisabledEmailAddressTemplates -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. - -Valid syntax for this parameter is \<Type\>:\<AddressFormat\>: - -- \<Type\>: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address. - -- \<AddressFormat\>: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://docs.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. - -You can specify multiple disabled email address templates separated by commas: "[\<Type1\>]:\<EmailAddress1\>","[\<Type2\>]:\<EmailAddress2\>",..."[\<TypeN\>]:\<EmailAddressN\>". - -Typically, this property is only populated by values after a migration from a previous version of Exchange. To clear these values, use the value $null for this parameter. - -```yaml -Type: ProxyAddressTemplateCollection -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnabledEmailAddressTemplates -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\>: - -- \<Type\>: A valid email address type as described in "Address types" section in [Email address policies in Exchange Server](https://docs.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, SMTP for the primary email address, and smtp for proxy addresses. - -- \<AddressFormat\>: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://docs.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. - -This parameter requires at least one template with the \<Type\> value SMTP (to define the primary SMTP email address). After that, if you don't include a \<Type\> prefix for a template, the value smtp (an SMTP proxy address) is assumed. - -You can specify multiple email address templates separated by commas: "SMTP:\<PrimarySMTPEmailAddress\>","[\<Type1\>]:\<EmailAddress1\>","[\<Type2\>]:\<EmailAddress2\>",..."[\<TypeN\>]:\<EmailAddressN\>". - -You can't use this parameter with the EnabledPrimarySMTPAddressTemplate parameter. - -In Office 365, if you use this parameter with the IncludeUnifiedGroupRecipients, you can't use variables in the email address template. - -```yaml -Type: ProxyAddressTemplateCollection -Parameter Sets: (All) -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 -``` - -### -EnabledPrimarySMTPAddressTemplate -The EnabledPrimarySMTPAddressTemplate parameter specifies the 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://docs.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. - -You can't use this parameter with the EnabledEmailAddressTemplates parameter. - -In Office 365, if you use this parameter with the IncludeUnifiedGroupRecipients, you can't use variables in the email address template. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludedRecipients -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: - -- AllRecipients: This value can be used only by itself. - -- MailboxUsers - -- MailContacts - -- MailGroups - -- MailUsers - -- Resources: This value indicates room or equipment mailboxes. - -You can specify multiple values separated by commas. When you use multiple values, the OR Boolean operator is applied. - -```yaml -Type: WellKnownRecipientType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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. - -Note: The first email address policy that identifies a recipient configures the recipient's email addresses. All other policies are ignored, even if the first policy is unapplied and can't configure the recipient's email addresses. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientContainer -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: - -- Name - -- Canonical name - -- Distinguished name (DN) - -- GUID - -If you don't use this parameter, the default value is the OU where the object was created. - -```yaml -Type: OrganizationalUnitIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientFilter -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'"`. - -- 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. - -- Property is a filterable property. For filterable properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to filter on. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -- Wildcards are valid only as the first or last character. For example, `'Sales*'` or `'*Sales'` are allowed, but `'Sa*les'` isn't allowed. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/Export-ExchangeCertificate.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Export-ExchangeCertificate.md deleted file mode 100644 index 98366bffae..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Export-ExchangeCertificate.md +++ /dev/null @@ -1,280 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/export-exchangecertificate -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Export-ExchangeCertificate -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Export-ExchangeCertificate - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Export-ExchangeCertificate cmdlet to export existing certificates and pending certificate requests (also known as certificate signing requests or CSRs) from Exchange servers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Thumbprint -``` -Export-ExchangeCertificate [-Thumbprint] <String> [-Server <ServerIdParameter>] - [-BinaryEncoded] - [-Confirm] - [-DomainController <Fqdn>] - [-FileName <String>] - [-Password <SecureString>] - [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Export-ExchangeCertificate [[-Identity] <ExchangeCertificateIdParameter>] - [-BinaryEncoded] - [-Confirm] - [-DomainController <Fqdn>] - [-FileName <String>] - [-Password <SecureString>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-ExchangeCertificate cmdlet creates the following types of files: - -- Certificate files: When you export a certificate, the command creates a PKCS #12 file. PKCS #12 is the Personal Information Exchange Syntax standard specified by RSA Laboratories. For more information, see [PKCS #12: Personal Information Exchange Syntax Standard](https://www.emc.com/emc-plus/rsa-labs/standards-initiatives/pkcs12-personal-information-exchange-syntax-standard.htm). - - To export a certificate from an Exchange server, the certificate's PrivateKeyExportable property needs to have the value True. To import an exported certificate on another Exchange server, you need to export the certificate by using the Password parameter to include the private key or chain of trust in the certificate file. The default Microsoft Exchange self-signed certificate or new self-signed certificates that you create in the Exchange admin center or by using the default settings of the New-ExchangeCertificate cmdlet aren't exportable, because the private key isn't exportable (the default value of the PrivateKeyExportable parameter is $false). - -- Certificate request files: When you export a certificate request, the command creates a PKCS #10 file. PKCS #10 is the Certification Request Syntax standard specified by RFC 2314. For more information, see [PKCS #10: Certification Request Syntax](https://www.ietf.org/rfc/rfc2314.txt). - - Typically, you export a certificate request file if you need to resubmit the certificate request to the certification authority. You can't import an exported certificate request on another server. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Export-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e -FileName "C:\Data\HT cert.pfx" -BinaryEncoded -Password (ConvertTo-SecureString -String 'P@ssw0rd1' -AsPlainText -Force) -``` - -This example exports a certificate from the local Exchange server to a file with the following settings: - -The certificate that has the thumbprint value 5113ae0233a72fccb75b1d0198628675333d010e is exported to the file C:\\Data\\HT cert.pfx. - -The exported certificate file is encoded by DER (not Base64). - -The password for the certificate file is P@ssw0rd1. - -### Example 2 -```powershell -Export-ExchangeCertificate -Thumbprint 72570529B260E556349F3403F5CF5819D19B3B58 -Server Mailbox01 -FileName "\\FileServer01\Data\Fabrikam.req" -``` - -This example exports a pending certificate request to a file with the following settings: - -The pending certificate request that has the thumbprint value 72570529B260E556349F3403F5CF5819D19B3B58 on the Exchange server named Mailbox01 is exported to the file \\\\FileServer01\\Data\\Fabrikam.req. - -The exported certificate request file is Base64 encoded, so the information that's written to the file is also displayed onscreen. - -## PARAMETERS - -### -Thumbprint -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. - -```yaml -Type: String -Parameter Sets: Thumbprint -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -BinaryEncoded -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -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. - -This parameter uses the syntax `(ConvertTo-SecureString -String '<password>' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Server -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 - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN - -If you don't use this parameter, the command is run on the local server. - -You can't use this parameter with the Identity parameter, but you can use it with the Thumbprint parameter. - -```yaml -Type: ServerIdParameter -Parameter Sets: Thumbprint -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileName -The FileName parameter specifies the name and path of the exported certificate or certificate request file. You can use a local path if the certificate or certificate request is located on the same Exchange server where you're running the command. Otherwise, use a UNC path (\\\\\<Server\>\\\<Share\>). 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the certificate or certificate request that you want to export. Valid values are: - -- \<ServerNameOrFQDN\>\\\<Thumbprint\> - -- \<Thumbprint\> - -You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. - -You can't use this parameter with the Server parameter. - -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. - -```yaml -Type: ExchangeCertificateIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Get-DataEncryptionPolicy.md deleted file mode 100644 index 65c466a12c..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-DataEncryptionPolicy.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-dataencryptionpolicy -applicable: Exchange Online -title: Get-DataEncryptionPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-DataEncryptionPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-DataEncryptionPolicy cmdlet to view data encryption policies in Exchange Online. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DataEncryptionPolicy [[-Identity] <DataEncryptionPolicyIdParameter>] [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Data encryption policy cmdlets are the Exchange Online part of service encryption with Customer Key in Office 365. For more information, see [Controlling your data in Office 365 using Customer Key](https://aka.ms/customerkey). - -You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DataEncryptionPolicy -``` - -This example returns a summary list of all data encryption policies in the organization. - -### Example 2 -```powershell -Get-DataEncryptionPolicy -Identity "Europe Mailboxes" -``` - -The example returns detailed information for the data encryption policy named Europe Mailboxes. - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: DataEncryptionPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-OMEConfiguration.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Get-OMEConfiguration.md deleted file mode 100644 index becd9d4219..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-OMEConfiguration.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-omeconfiguration -applicable: Exchange Online -title: Get-OMEConfiguration -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-OMEConfiguration - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-OMEConfiguration cmdlet to view Microsoft Office 365 Message Encryption (OME) configurations. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-OMEConfiguration [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-OMEConfiguration -``` - -This example returns a summary list of all OME configurations in the organization. - -### Example 2 -```powershell -Get-OMEConfiguration | Format-List -``` - -This example returns detailed information for all OME configurations in the organization. - -## 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/Get-OMEMessageStatus.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Get-OMEMessageStatus.md deleted file mode 100644 index 3c1544c9ff..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-OMEMessageStatus.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-omemessagestatus -applicable: Exchange Online -title: Get-OMEMessageStatus -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-OMEMessageStatus - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-OMEMessageStatus cmdlet to view the Microsoft Office 365 Message Encryption (OME) revocation status for a specific message. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-OMEMessageStatus -MessageId <String> [<CommonParameters>] -``` - -## DESCRIPTION -If encryption for the message was successfully revoked, the command will return the message: The encrypted email with the subject "\<subject\>" and Message ID "\<messageId>\" was successfully revoked. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-OMEMessageStatus -MessageId "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>" -``` - -This example returns the encryption revocation status for the specified message. - -## PARAMETERS - -### -MessageId -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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). - -You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Office 365 Security & Compliance Center. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md deleted file mode 100644 index ef11927393..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/get-rmstrustedpublishingdomain -applicable: Exchange Online -title: Get-RMSTrustedPublishingDomain -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-RMSTrustedPublishingDomain - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-RMSTrustedPublishingDomain cmdlet to view the settings of an existing trusted publishing domain (TPD) in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-RMSTrustedPublishingDomain [[-Identity] <RmsTrustedPublishingDomainIdParameter>] [-Default] [<CommonParameters>] -``` - -## DESCRIPTION -A trusted publishing domain contains the settings needed to use RMS features in your organization. For example, users can apply RMS templates to email messages. - -## EXAMPLES - -### Example 1 -```powershell -Get-RMSTrustedPublishingDomain | Format-List -``` - -This example lists all the trusted publishing domains that are configured in your organization and shows detailed information for each trusted publishing domain. - -## PARAMETERS - -### -Default -The Default switch filters the results by the default trusted publishing domain. The default trusted publishing domain displays RMS templates and provides rights protection to all new content. There can be only one default trusted publishing domain in an organization. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the trusted publishing domain. You can use any value that uniquely identifies the trusted publishing domain, for example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RmsTrustedPublishingDomainIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/Import-ExchangeCertificate.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Import-ExchangeCertificate.md deleted file mode 100644 index d49d7d6efd..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Import-ExchangeCertificate.md +++ /dev/null @@ -1,302 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/import-exchangecertificate -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Import-ExchangeCertificate -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Import-ExchangeCertificate - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Import-ExchangeCertificate cmdlet to import certificates on Exchange servers. You use this cmdlet to install certificates that were exported from other servers, and to complete pending certification requests (also known as certificate signing requests or CSRs) from certification authorities (CAs). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### FileData -``` -Import-ExchangeCertificate -FileData <Byte[]> - [-Confirm] - [-DomainController <Fqdn>] - [-FriendlyName <String>] - [-Password <SecureString>] - [-PrivateKeyExportable <Boolean>] - [-Server <ServerIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -### FileName -``` -Import-ExchangeCertificate -Instance <String[]> - [-Confirm] - [-DomainController <Fqdn>] - [-FriendlyName <String>] - [-Password <SecureString>] - [-PrivateKeyExportable <Boolean>] - [-Server <ServerIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -### Instance -``` -Import-ExchangeCertificate -FileName <String> - [-Confirm] - [-DomainController <Fqdn>] - [-FriendlyName <String>] - [-Password <SecureString>] - [-PrivateKeyExportable <Boolean>] - [-Server <ServerIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Import-ExchangeCertificate cmdlet to import the following types of certificate files on an Exchange server: - -- APKCS #7 certificate or chain of certificates file (.p7b or .p7c) that was issued by a certification authority (CA). PKCS #7 is the Cryptographic Message Syntax Standard, a syntax used for digitally signing or encrypting data using public key cryptography, including certificates. For more information, see [PKCS #7: Cryptographic Message Syntax Standard](https://go.microsoft.com/fwlink/p/?LinkID=510681). - -- A PKCS #12 certificate file (.cer, .crt, .der, .p12, or .pfx) that contains the private key. PKCS #12 is the Personal Information Exchange Syntax Standard, a file format used to store certificates with corresponding private keys that are protected by a password. The standard is specified by RSA Laboratories. For more information, see the [PKCS #12: Personal Information Exchange Syntax Standard](https://go.microsoft.com/fwlink/p/?LinkID=90249) website. - -After you import a certificate on an Exchange server, you need to assign the certificate to one or more Exchange services by using the Enable-ExchangeCertificate cmdlet. - -There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://docs.microsoft.com/Exchange/architecture/client-access/certificates). - -Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://blogs.office.com/2014/10/29/protecting-ssl-3-0-vulnerability/). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Import-ExchangeCertificate -Server Mailbox01 -FileName" \\FileServer01\Data\Exported Fabrikam Cert.pfx" -Password (ConvertTo-SecureString -String 'P@ssw0rd1' -AsPlainText -Force) -``` - -This example imports the certificate from the PKCS #12 file from \\\\FileServer01\\Data\\Exported Fabrikam Cert.pfx to the Exchange server named Mailbox01. This file requires the password P@ssw0rd1. This certificate could have been exported from another server, or issued by a certification authority. - -### Example 2 -```powershell -Import-ExchangeCertificate -FileData ([Byte[]](Get-Content -Path "C:\Certificates\Fabrikam IssuedCert.p7b" -Encoding byte -ReadCount 0)) -``` - -This example imports a chain of certificates from the PKCS #7 file C:\\Certificates\\Fabrikam IssuedCert.p7b on the local Exchange server. - -## PARAMETERS - -### -FileData -The FileData parameter specifies the contents of the certificate file that you want to import. Typically, you use this parameter for PKCS #7 text certificate files that have .p7b or .p7c filename extensions. These text files contain the text: -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- or -----BEGIN PKCS7----- and -----END PKCS7-----. - -A valid value for this parameter requires you to read the file to a byte-encoded object using the Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -You can use a local path if the certificate file is located on the Exchange server where you're running the command, and this is the same server where you want to install the certificate. Otherwise, use a UNC path (\\\\\<Server\>\\\<Share\>). - -If the value contains spaces, enclose the value in quotation marks ("). - -```yaml -Type: Byte[] -Parameter Sets: FileData -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FriendlyName -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -The Password parameter specifies the password that's required to import the certificate. - -This parameter uses the syntax `(ConvertTo-SecureString -String '<password>' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateKeyExportable -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. - -- $false: The private key isn't exportable, so you can't export the certificate from this server. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Server -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 - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN - -If you don't use this parameter, the command is run on the local server. - -```yaml -Type: ServerIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileName -The FileName parameter specifies the certificate file that you want to import. Typically, you use this parameter for PKCS #12 binary certificate files that have .cer, .crt, .der, .p12, or .pfx filename extensions. This type of binary certificate file is protected by a password when the file contains the private key or chain of trust. - -You can use a local path if the certificate file is located on the Exchange server where you're running the command, and this is the same server where you want to install the certificate. Otherwise, use a UNC path (\\\\\<Server\>\\\<Share\>). - -If the value contains spaces, enclose the value in quotation marks ("). - -```yaml -Type: String -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/Import-RMSTrustedPublishingDomain.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Import-RMSTrustedPublishingDomain.md deleted file mode 100644 index 05f703d4b8..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Import-RMSTrustedPublishingDomain.md +++ /dev/null @@ -1,324 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/import-rmstrustedpublishingdomain -applicable: Exchange Online -title: Import-RMSTrustedPublishingDomain -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Import-RMSTrustedPublishingDomain - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Import-RMSTrustedPublishingDomain cmdlet to import a trusted publishing domain (TPD) from an on-premises server running Active Directory Rights Management Services (AD RMS) or from RMS Online into your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### IntranetLicensingUrl -``` -Import-RMSTrustedPublishingDomain [-Name] <String> -ExtranetLicensingUrl <Uri> -FileData <Byte[]> -IntranetLicensingUrl <Uri> -Password <SecureString> - [-Confirm] - [-Default] - [-WhatIf] [<CommonParameters>] -``` - -### ImportFromFile -``` -Import-RMSTrustedPublishingDomain [-Name] <String> -ExtranetLicensingUrl <Uri> -FileData <Byte[]> -IntranetLicensingUrl <Uri> -Password <SecureString> [-ExtranetCertificationUrl <Uri>] [-IntranetCertificationUrl <Uri>] - [-Confirm] - [-Default] - [-WhatIf] [<CommonParameters>] -``` - -### RefreshTemplates -``` -Import-RMSTrustedPublishingDomain [-Name] <String> -FileData <Byte[]> -Password <SecureString> [-RefreshTemplates] - [-Confirm] - [-Default] - [-WhatIf] [<CommonParameters>] -``` - -### RMSOnline -``` -Import-RMSTrustedPublishingDomain [-Name] <String> [-RMSOnline] [-RefreshTemplates] - [-Confirm] - [-Default] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -A TPD contains the settings needed to use RMS features in your organization. For example, users can apply RMS templates to email messages. After you export the TPD from an on-premises AD RMS server to an XML file, you can import the XML file into your cloud-based organization. - -If the InternalLicensingEnabled parameter value is $true on the Set-IRMConfiguration cmdlet, all TPDs require a private key. If the InternalLicensingEnabled parameter value is $false, TPDs don't require a private key. However, the only RMS feature available to the organization is Outlook protection rules. Typically, TPDs without private keys are created when the AD RMS server uses a hardware-based cryptographic service provider (CSP) or a custom CSP. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Import-RMSTrustedPublishingDomain -Name "Contoso TPD" -FileData $([byte[]](Get-Content -Encoding byte -Path "C:\My Documents\Contoso.xml" -ReadCount 0)) -Password (ConvertTo-SecureString -String 'Pa$$word1' -AstPlainText -Force)-ExtranetLicensingUrl https://rms.contoso.com/_wmcs/licensing -IntranetLicensingUrl https://RMS01/_wmcs/licensing -``` - -This example imports a TPD from an AD RMS server into a cloud-based organization. The TPD uses the following values: - -- Path to exported XML file: C:\\My Documents\\Contoso.xml - -- Password of exported XML file: Pa$$word1 - -- External licensing URL: https://rms.contoso.com/\_wmcs/licensing - -- Internal licensing URL: https://RMS01/\_wmcs/licensing - -- TPD name: Contoso TPD - -## PARAMETERS - -### -ExtranetLicensingUrl -The ExtranetLicensingUrl parameter specifies the external licensing URL of the on-premises AD RMS server that's stamped into the publishing license. The publishing license specifies the users that can open the rights-protected content, under which conditions the content may be opened by the user, and the rights that each user will have to the rights-protected content. - -By default, the value of the ExtranetLicensingUrl parameter is https://\<FQDN\>/\_wmcs/licensing. - -```yaml -Type: Uri -Parameter Sets: IntranetLicensingUrl, ImportFromFile -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileData -The FileData parameter specifies the XML file you want to import. The XML file contains the TPD you exported from the on-premises AD RMS server. - -A valid value for this parameter requires you to read the file to a byte-encoded object using the Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -Type: Byte[] -Parameter Sets: IntranetLicensingUrl, ImportFromFile, RefreshTemplates -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IntranetLicensingUrl -The IntranetLicensingUrl parameter specifies the internal licensing URL of the on-premises AD RMS server that's stamped into the publishing license. The publishing license specifies the users that can open the rights-protected content, under which conditions the content may be opened by the user, and the rights that each user will have to the rights-protected content. - -By default, the value of the IntranetLicensingUrl parameter is https://\<server name\>/\_wmcs/licensing. - -```yaml -Type: Uri -Parameter Sets: IntranetLicensingUrl, ImportFromFile -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies the name of the TPD. If you use the RefreshTemplates switch, the value must match the name of the previously imported TPD. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -The Password parameter specifies the password of the TPD that you want to import. The password value must match the password in the XML file when you exported the TPD from the on-premises AD RMS server. - -This parameter uses the syntax `(ConvertTo-SecureString -String '<password>' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. - -```yaml -Type: SecureString -Parameter Sets: IntranetLicensingUrl, ImportFromFile, RefreshTemplates -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RMSOnline -The RMSOnline switch specifies that the TPD is imported from RMS Online. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: RMSOnline -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -The Default switch specifies that this is the default TPD. You don't need to specify a value with this switch. - -The default TPD displays RMS templates and provides rights protection to all new content. There can be only one default TPD in an organization. - -The first TPD you import into your organization is automatically set as the default. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtranetCertificationUrl -The ExtranetCertificationUrl parameter specifies the external certification URL of the on-premises AD RMS server that's stamped into the Rights Account Certificate (RAC). The RAC establishes a user's identity in the AD RMS system, and is used to decrypt content. - -By default, the value of the ExtranetCertificationUrl parameter is https://\<FQDN\>/\_wmcs/certification/servercertification.asmx. - -```yaml -Type: Uri -Parameter Sets: ImportFromFile -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IntranetCertificationUrl -The IntranetCertificationUrl parameter specifies the internal certification URL of the on-premises AD RMS server that's stamped into the RAC. The RAC establishes a user's identity in the AD RMS system, and is used to decrypt content. - -By default, the value of the IntranetCertificationUrl parameter is https://\<server name\>/\_wmcs/certification/servercertification.asmx. - -```yaml -Type: Uri -Parameter Sets: ImportFromFile -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RefreshTemplates -The RefreshTemplates switch specifies whether to update the RMS templates in a previously imported TPD. You don't need to specify a value with this switch. - -When you add, modify, or remove RMS templates in a TPD on the AD RMS server, you export the updated TPD to a new XML file, and import the new XML file in your cloud-based organization. The RefreshTemplates switch uses the following rules: - -- Only the FileData, Password, and Name parameters are required. The value of the Name parameter must match the name of the previously imported TPD. - -- If the new XML file doesn't contain an RMS template that was defined in the previously imported TPD, the RMS template is removed from the cloud-based organization. - -- If the new XML file contains an updated RMS template that was defined in the previously imported TPD, the RMS template settings are updated in the cloud-based organization. However, the RMS template isn't changed from Archived to Distributed or vice versa. - -- If the new XML file contains an RMS template that wasn't imported in the original TPD, the RMS template is added to the cloud-based organization in the Archived state. To make the new RMS template usable, you must change its state from Archived to Distributed using the Set-RMSTemplate cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: RefreshTemplates, RMSOnline -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/New-ExchangeCertificate.md b/exchange/exchange-ps/exchange/encryption-and-certificates/New-ExchangeCertificate.md deleted file mode 100644 index 25ae69f20d..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/New-ExchangeCertificate.md +++ /dev/null @@ -1,605 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/new-exchangecertificate -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-ExchangeCertificate -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# New-ExchangeCertificate - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the New-ExchangeCertificate cmdlet to create and renew self-signed certificates, and to create certificate requests (also known as certificate signing requests or CSRs) for new certificates and certificate renewals from a certification authority (CA). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Request -``` -New-ExchangeCertificate [-BinaryEncoded] [-GenerateRequest] [-RequestFile <String>] - [-Confirm] - [-DomainController <Fqdn>] - [-DomainName <MultiValuedProperty>] - [-Force] - [-FriendlyName <String>] - [-IncludeAcceptedDomains] - [-IncludeAutoDiscover] - [-IncludeServerFQDN] - [-IncludeServerNetBIOSName] - [-Instance <X509Certificate2>] - [-KeySize <Int32>] - [-PrivateKeyExportable <Boolean>] - [-Server <ServerIdParameter>] - [-SubjectKeyIdentifier <String>] - [-SubjectName <X500DistinguishedName>] - [-WhatIf] [<CommonParameters>] -``` - -### Certificate -``` -New-ExchangeCertificate [-Services <AllowedServices>] - [-Confirm] - [-DomainController <Fqdn>] - [-DomainName <MultiValuedProperty>] - [-Force] - [-FriendlyName <String>] - [-IncludeAcceptedDomains] - [-IncludeAutoDiscover] - [-IncludeServerFQDN] - [-IncludeServerNetBIOSName] - [-Instance <X509Certificate2>] - [-KeySize <Int32>] - [-PrivateKeyExportable <Boolean>] - [-Server <ServerIdParameter>] - [-SubjectKeyIdentifier <String>] - [-SubjectName <X500DistinguishedName>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Exchange uses certificates for SSL and TLS encryption. - -There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) services. You need to understand how these factors might affect your overall configuration. For more information, see [Digital certificates and encryption in Exchange Server](https://docs.microsoft.com/Exchange/architecture/client-access/certificates). - -Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://azure.microsoft.com/blog/protecting-against-the-ssl-3-0-vulnerability/). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-ExchangeCertificate -``` - -This example creates a self-signed certificate with the following settings: - -The Subject value is CN=\<ServerName\> (for example, CN=Mailbox01). - -The Domains (subject alternative names) value is \<ServerName\>, \<ServerFQDN\> (for example, Mailbox01,Mailbox01.contoso.com). - -The Services value is IMAP,POP,SMTP - -The Services value SMTP grants the Network Services local security group read access to the certificate's private key. - -The Services value SMTP and the Subject value that contains the server name publishes the certificate to Active Directory so that Exchange direct trust can validate the authenticity of the server for mutual TLS. - -If you don't want this certificate to replace the existing self-signed certificate that was created during Exchange setup, be sure to select "No" in the prompt that asks you overwrite the existing default SMTP certificate. - -### Example 2 -```powershell -New-ExchangeCertificate -GenerateRequest -RequestFile "C:\Cert Requests\woodgrovebank.req" -SubjectName "c=US,o=Woodgrove Bank,cn=mail.woodgrovebank.com" -DomainName autodiscover.woodgrovebank.com,mail.fabrikam.com,autodiscover.fabrikam.com -``` - -This example creates a new certificate request for a certification authority that has the following settings: - -The request is Base64 encoded. - -The output is displayed onscreen and is also written to the text file C:\\Cert Requests\\woodgrovebank.req. - -The Subject value is c=US,o=Woodgrove Bank,cn=mail.woodgrovebank.com - -The Domains (subject alternative names) value contains the additional valuesautodiscover.woodgrovebank.com,mail.fabrikam.com, and autodiscover.fabrikam.com. - -After you create the certificate request, you send the output to the CA. After you receive the certificate from the CA, you install the certificate by using the Import-ExchangeCertificate cmdlet, and you assign the certificate to Exchange services by using the Enable-ExchangeCertificate cmdlet. - -If the CA requires the certificate request in a file that's encoded by DER, use the BinaryEncoding switch. - -### Example 3 -```powershell -Get-ExchangeCertificate -Thumbprint c4248cd7065c87cb942d60f7293feb7d533a4afc | New-ExchangeCertificate -PrivateKeyExportable $true -``` - -This example renewsthe existing self-signed certificate that has the thumbprint value c4248cd7065c87cb942d60f7293feb7d533a4afc. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. Setting the PrivateKeyExportable parameter to the value $true allows the renewed self-signed certificate to be exported from the server (and imported on other servers). - -### Example 4 -```powershell -Get-ExchangeCertificate -Thumbprint 8A141F7F2BBA8041973399723BD2598D2ED2D831 | New-ExchangeCertificate -GenerateRequest -RequestFile "C:\Cert Requests\fabrikam_renewal.req" -``` - -This example creates a request to renew an existing certificate that was issued by a certification authority. The certificate request has the following settings: - -The thumbprint value of the existing certificate is 8A141F7F2BBA8041973399723BD2598D2ED2D831. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet. - -The request is Base64 encoded. - -The output is displayed onscreen and is also written to the text file C:\\Cert Requests\\fabrikam\_renewal.req. - -After you create the certificate renewal request, you send the output to the CA. After you receive the renewed certificate from the CA, you install the certificate by using the Import-ExchangeCertificate cmdlet. - -### Example 5 -```powershell -Get-ExchangeCertificate -Thumbprint c4248cd7065c87cb942d60f7293feb7d533a4afc | New-ExchangeCertificate -``` - -This example shows how to renew a self-signed certificate with a specific thumbprint value. You can obtain the thumbprint value in one of two ways. - -Select the certificate in the Exchange Administration Center and then select Edit to view properties of the certificate. The thumbprint value is shown in the Exchange Certificate window. - -Run the Get-ExchangeCertificate cmdlet to return a list of all certificates installed on the server with their thumbprint values. - -## PARAMETERS - -### -BinaryEncoded -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. - -This switch is available only when you use the GenerateRequest switch. - -For Base64 encoded requests, you send the contents of the file to the certificate authority. For requests that are encoded by DER, you send the certificate file itself. - -```yaml -Type: SwitchParameter -Parameter Sets: Request -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainName -The DomainName parameter specifies one or more FQDNs or server names for theSubject Alternative Namefield (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. - -Typically, values include server names (for example, Mailbox01) and FQDNs (for example, mail.contoso.com). You can specify multiple values separated by commas. Valuescan contain the characters a through z, 0 through 9, and the hyphen (-). The length of the domain name can't exceed 255 characters. - -The default value includes the name and FQDN of the Exchange server when both of the following conditions are true: - -- You don't use this parameter. - -- You don't use any of these parameters: IncludeAcceptedDomains, IncludeAutoDiscover, IncludeServerFQDN, or IncludeServerNetBIOSName. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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. - -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FriendlyName -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GenerateRequest -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. - -This switch, together with the RequestFile parameter, 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. - -After you install the certificate from the certification authority by using the Import-ExchangeCertificate cmdlet, you use the Enable-ExchangeCertficate cmdlet to enable the certificate for Exchange services. - -If you don't use this switch,thecommand creates a new self-signed certificate on the Exchange server. - -```yaml -Type: SwitchParameter -Parameter Sets: Request -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeAcceptedDomains -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: - -- If you've already included an accepted domain in the DomainName parameter, the value isn't duplicated in the Subject Alternative Name field. - -- For new self-signed certificates, if you don't use the Services parameter, the certificate is only assigned to SMTP. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeAutoDiscover -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: - -- autodiscover.woodgrovebank.com - -- autodiscover.woodgrovebank.co.uk - -When you use this switch: - -- If you've already included the value autodiscover.\<AcceptedDomain\> in the DomainName parameter, the value isn't duplicated in the Subject Alternative Name field. - -- For new self-signed certificates, if you don't use the Services parameter, the certificate is only assigned to SMTP. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeServerFQDN -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeServerNetBIOSName -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -This parameter 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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -KeySize -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 - -- 2048 (This is the default value) - -- 4096 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateKeyExportable -The PrivateKeyExportable parameter specifies whether the new self-signed 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. - -- $false: The private key isn't exportable, so you can't export the certificate. This is the default value. - -This parameter is only meaningful for new self-signed certificates. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestFile -The RequestFile parameter specifies the name and path of the certificate request file. The file contains the same information that's displayed on-screen when you generate a Base64 encoded certificate request (you don't use the BinaryEncoded switch). - -You can use a local path if the certificate or certificate request is located on the same Exchange server where you're running the command. Otherwise, use a UNC path (\\\\\<Server\>\\\<Share\>). If the value contains spaces, enclose the value in quotation marks ("). - -You can use this parameter only when you use the GenerateRequest switch. - -```yaml -Type: String -Parameter Sets: Request -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Server -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 - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN - -If you don't use this parameter, the command is run on the local server. - -```yaml -Type: ServerIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Services -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. - -- Federation - -- IIS - -- IMAP: Don't enable a wildcard certificate for the IMAP4 service. Instead, use the Set-ImapSettings cmdlet to configure the FQDN that clients use to connect to the IMAP4 service. - -- POP: Don't enable a wildcard certificate for the POP3 service. Instead, use the Set-PopSettings cmdlet to configure the FQDN that clients use to connect to the POP3 service. - -- SMTP: When you enable a certificate for SMTP, you're prompted to replace the default Exchange self-signed certificate that's used to encrypt SMTP traffic between internal Exchange. If you want to replace the default certificate without the confirmation prompt, use the Force switch. - -- UM: This value requires that the UMStartupMode parameter on the Set-UMService cmdlet is set to TLS or Dual. If the UMStartupMode parameter is set to the default value of TCP, you can't enable the certificate for the UM service. - -- UMCallRouter: This value requires that the UMStartupMode parameter on the Set-UMCallRouterService cmdlet is set to TLS or Dual. If the UMStartupMode parameter is set to the default value TCP, you can't enable the certificate for the UM Call Router service. - -You can specify multiple values separated by commas. The default values are IMAP,POP, and SMTP. - -You can't use this parameter with the GenerateRequest switch. - -Once you enable a certificate for a service, you can't remove the service from the certificate. - -```yaml -Type: AllowedServices -Parameter Sets: Certificate -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubjectKeyIdentifier -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubjectName -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. - -This parameter uses the syntax: [C=\<CountryOrRegion\>,S=\<StateOrProvince\>,L=LocalityOrCity,O=\<Organization\>,OU=\<Department\>],CN=\<HostNameOrFQDN\>. Although the only required value is CN=\<HostNameOrFQDN\>, you should always include C=\<CountryOrRegion\> for certificate requests, but other values might also be required by the certification authority. - -For example, if you want the certificate's subject to be mail.contoso.com in the United States, you can use any of the following values: - -- C=US,S=WA,L=Redmond,O=Contoso,OU=IT,CN=mail.contoso.com - -- C=US,O=Contoso,CN=mail.contoso.com - -- C=US,CN=mail.contoso.com - -If you don't use this parameter, the default value is the name of the Exchange server where you run the command (for example, CN=Mailbox01). - -For a subject alternative name (SAN) certificate, you should choose one of the values from the DomainName parameter to use in the SubjectName value. In fact, the CN value that you specify for SubjectName is automatically included in the DomainName values. - -For a wildcard certificate, use a SubjectName value that contains the wildcard character (\*). For example, C=US,CN=\*.contoso.com. - -```yaml -Type: X500DistinguishedName -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/New-OMEConfiguration.md b/exchange/exchange-ps/exchange/encryption-and-certificates/New-OMEConfiguration.md deleted file mode 100644 index c014e882f0..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/New-OMEConfiguration.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/New-OMEConfiguration -applicable: Exchange Online -title: New-OMEConfiguration -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# New-OMEConfiguration - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-OMEConfiguration cmdlet to create a Microsoft Office 365 Message Encryption (OME) configuration. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-OMEConfiguration [-Identity] <OrganizationIdParameter> - [-BackgroundColor <String>] - [-DisclaimerText <String>] - [-EmailText <String>] - [-ExternalMailExpiryInDays <Int32>] - [-Image <Byte[]>] - [-IntroductionText <String>] - [-OTPEnabled <Boolean>] - [-PortalText <String>] - [-ReadButtonText <String>] - [-SocialIdSignIn <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-OMEConfiguration -Identity "Contoso Marketing" -EmailText "Encrypted message enclosed." -PortalText "This portal is encrypted." -DisclaimerText "Encryption security disclaimer." -Image (Get-Content "C:\Temp\OME Logo.gif" -Encoding byte) -``` - -This example creates a new OME configuration named "Contoso Marketing" with the specified values specified. Unused parameters get the default values. - -## PARAMETERS - -### -Identity -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 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BackgroundColor -The BackgroundColor parameter specifies the background color. Valid values are: - -- An available HTML hexadecimal \(hex triplet\) color code value \(for example, 0x000000 is white\). - -- An available text value \(for example, yellow is 0x00FFFF00\). - -- $null \(blank\). This is the default value. - -For the list of available hex and text values, see [Background colors for Office 365 Message Encryption](https://support.office.com/article/1508cb35-c5ff-4523-b579-947b21d5515f). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisclaimerText -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailText -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalMailExpiryInDays -This parameter is only available 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. - -```yaml -Type: String -Parameter Sets: Int32 -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Image -The Image parameter identifies and uploads an image that will be displayed in the email message and in the Office 365 portal. - -You need to read the file to a byte-encoded object using the Get-Content cmdlet, for example, -Image (Get-Content "C:\\Temp\\OME Logo.gif" -Encoding byte) - -- Supported file formats: .png, .jpg, .bmp, or .tiff - -- Optimal size of logo file: less than 40 KB - -- Optimal dimensions of logo image: 170x70 pixels - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IntroductionText -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OTPEnabled -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. - -- $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using an Office 365 work or school account. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PortalText -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadButtonText -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialIdSignIn -The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Office 365 portal 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. - -- $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Office 365 work or school account is controlled by the OTPEnabled parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md deleted file mode 100644 index ebe4325fab..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/remove-rmstrustedpublishingdomain -applicable: Exchange Online -title: Remove-RMSTrustedPublishingDomain -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Remove-RMSTrustedPublishingDomain - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-RMSTrustedPublishingDomain cmdlet to remove an existing trusted publishing domain (TPD) from your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-RMSTrustedPublishingDomain [-Identity] <RmsTrustedPublishingDomainIdParameter> - [-Confirm] - [-Force] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -A trusted publishing domain contains the settings needed to use Rights Management Services (RMS) features in your organization. When you delete a trusted publishing domain, all existing content that's protected by the RMS templates in the trusted publishing domain becomes unreadable. Instead of deleting the trusted publishing domain, you can archive the RMS templates using the Set-RMSTemplate cmdlet. Archiving the RMS template prevents future use for encryption, but allows access to existing rights-protected content. - -If you delete the only trusted publishing domain, all RMS features are disabled in the organization. If multiple trusted publishing domains exist in your organization, you can't delete the default trusted publishing domain. You must first designate another trusted publishing domain as the default. You can change the default trusted publishing domain using the Set-RMSTrustedPublishingDomain cmdlet. - -## EXAMPLES - -### Example 1 -```powershell -Remove-RMSTrustedPublishingDomain "Contoso TPD" -``` - -This example removes the trusted publishing domain Contoso TPD from your organization. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the trusted publishing domain. You can use any value that uniquely identifies the trusted publishing domain, for example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RmsTrustedPublishingDomainIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force parameter forces the command to execute without asking for user confirmation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/Set-OMEConfiguration.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Set-OMEConfiguration.md deleted file mode 100644 index 4eaefeab34..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-OMEConfiguration.md +++ /dev/null @@ -1,302 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/set-omeconfiguration -applicable: Exchange Online -title: Set-OMEConfiguration -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-OMEConfiguration - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-OMEConfiguration cmdlet to configure Microsoft Office 365 Message Encryption (OME). - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-OMEConfiguration [-Identity] <OMEConfigurationIdParameter> - [-BackgroundColor <String>] - [-DisclaimerText <String>] - [-EmailText <String>] - [-ExternalMailExpiryInDays <Int32>] - [-Image <Byte[]>] - [-IntroductionText <String>] - [-OTPEnabled <Boolean>] - [-PortalText <String>] - [-PrivacyStatementUrl <String>] - [-ReadButtonText <String>] - [-SocialIdSignIn <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-OMEConfiguration -Identity "OME Configuration" -EmailText "Encrypted message enclosed." -PortalText "This portal is encrypted." -DisclaimerText "Encryption security disclaimer." -Image (Get-Content "C:\Temp\OME Logo.gif" -Encoding byte) -``` - -This example configures the specified values for the default OME configuration named "OME Configuration". Note the use of the Get-Content command to provide the input for the Image parameter. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the OME configuration that you want to modify. The default OME configuration has the Identity value "OME Configuration". You can also use "default". - -```yaml -Type: OMEConfigurationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -BackgroundColor -The BackgroundColor parameter specifies the background color. Valid values are: - -- An available HTML hexadecimal \(hex triplet\) color code value \(for example, 0xFFFFFF is white\). - -- An available text value \(for example, yellow is 0x00FFFF00\). - -- $null \(blank\). This is the default value. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisclaimerText -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailText -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalMailExpiryInDays -This parameter is only available 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. - -```yaml -Type: String -Parameter Sets: Int32 -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Image -The Image parameter identifies and uploads an image that will be displayed in the email message and in the Office 365 portal. - -You need to read the file to a byte-encoded object using the Get-Content cmdlet, for example, -Image (Get-Content "C:\\Temp\\OME Logo.gif" -Encoding byte) - -- Supported file formats: .png, .jpg, .bmp, or .tiff - -- Optimal size of logo file: less than 40 KB - -- Optimal dimensions of logo image: 170x70 pixels - -To remove an existing image and use the default image, use the value $null for this parameter. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IntroductionText -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OTPEnabled -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. - -- $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using an Office 365 work or school account. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PortalText -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivacyStatementUrl -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadButtonText -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialIdSignIn -The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Office 365 portal 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. - -- $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Office 365 work or school account is controlled by the OTPEnabled parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/encryption-and-certificates/Set-OMEMessageRevocation.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Set-OMEMessageRevocation.md deleted file mode 100644 index 7283d3e4b3..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-OMEMessageRevocation.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/set-omemessagerevocation -applicable: Exchange Online -title: Set-OMEMessageRevocation -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-OMEMessageRevocation - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-OMEMessageRevocation cmdlet to revoke Microsoft Office 365 Message Encryption (OME) for a message. Revoking encryption prevents the recipient from viewing the message in the Office 365 Message Encryption portal. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-OMEMessageRevocation -MessageId <String> -Revoke <Boolean> [<CommonParameters>] -``` - -## DESCRIPTION -When an email has been revoked, the recipient will get the following error when they try to view the encrypted message in the Office 365 Message Encryption portal: "The message has been revoked by the sender". - -You can revoke encrypted messages if the recipient received a link-based, branded encrypted email message. If the recipient received a native inline experience in a supported Outlook client, then you can't revoke encryption for the message. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-OMEMessageRevocation -MessageId "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>" -Revoke $true -``` - -This example revokes encryption for the specified message. - -## PARAMETERS - -### -MessageId -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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). - -You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Office 365 Security & Compliance Center. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Revoke -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 Office 365 Message Encryption portal - -- $false: Encryption for the specified message isn't revoked. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md b/exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md deleted file mode 100644 index c2b4d4c79f..0000000000 --- a/exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/encryption-and-certificates/set-rmstrustedpublishingdomain -applicable: Exchange Online -title: Set-RMSTrustedPublishingDomain -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-RMSTrustedPublishingDomain - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-RMSTrustedPublishingDomain cmdlet to configure a trusted publishing domain (TPD) in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-RMSTrustedPublishingDomain [-Identity] <RmsTrustedPublishingDomainIdParameter> - [-Confirm] - [-Default] - [-ExtranetCertificationUrl <Uri>] - [-ExtranetLicensingUrl <Uri>] - [-IntranetCertificationUrl <Uri>] - [-IntranetLicensingUrl <Uri>] - [-Name <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -A TPD contains the settings needed to use RMS features in your organization. For example, users can apply RMS templates to email messages. - -## EXAMPLES - -### Example 1 -```powershell -Set-RMSTrustedPublishingDomain "Contoso TPD" -Default -ExtranetLicensingUrl https://rms.contoso.com/_wmcs/licensing -ExtranetCertificationUrl https://rms.contoso.com/_wmcs/certification/servercertification.asmx -``` - -This example makes the following changes to the existing TPD Contoso TPD: - -- Sets Contoso TPD as the default TPD for the organization. - -- Sets the external licensing URL to https://rms.contoso.com/\_wmcs/licensing. - -- Sets the external certification URL to https://rms.contoso.com/\_wmcs/certification/servercertification.asmx - -## PARAMETERS - -### -Identity -The Identity parameter specifies the TPD. You can use any value that uniquely identifies the TPD, for example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: RmsTrustedPublishingDomainIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -The Default parameter specifies this is the default TPD. The default TPD displays RMS templates and provides rights protection to all new content. There can be only one default TPD in an organization. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtranetCertificationUrl -The ExtranetCertificationUrl parameter specifies the external certification URL of the on-premises AD RMS server that's stamped into the Rights Account Certificate (RAC). The RAC establishes a user's identity in the AD RMS system and is used to decrypt content. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtranetLicensingUrl -The ExtranetLicensingUrl parameter specifies the external licensing URL of the on-premises AD RMS server that's stamped into the publishing license. The publishing license specifies the users that can open the rights-protected content, under which conditions the content may be opened by the user, and the rights that each user will have to the rights-protected content. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IntranetCertificationUrl -The IntranetCertificationUrl parameter specifies the internal certification URL of the on-premises AD RMS server that's stamped into the RAC. The RAC establishes a user's identity in the AD RMS system and is used to decrypt content. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IntranetLicensingUrl -The IntranetLicensingUrl parameter specifies the internal licensing URL of the on-premises AD RMS server that's stamped into the publishing license. The publishing license specifies the users that can open the rights-protected content, under which conditions the content may be opened by the user, and the rights that each user will have to the rights-protected content. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies the name of the TPD. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/exchange.md b/exchange/exchange-ps/exchange/exchange.md index c8dd236aa3..8ead57cb12 100644 --- a/exchange/exchange-ps/exchange/exchange.md +++ b/exchange/exchange-ps/exchange/exchange.md @@ -2,17 +2,2853 @@ Module Name: Exchange PowerShell Module Guid: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX title: exchange -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" --- # Exchange PowerShell +## Description +Exchange PowerShell is built on Windows PowerShell technology and provides a powerful command-line interface that enables automation of administrative tasks. The following PowerShell environments are available in Exchange: + +- [Exchange Server PowerShell (Exchange Management Shell)](https://learn.microsoft.com/powershell/exchange/exchange-management-shell) +- [Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell) +- [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell) +- [Exchange Online Protection PowerShell](https://learn.microsoft.com/powershell/exchange/exchange-online-protection-powershell) + +> [!NOTE] +> For Exchange Online, Security & Compliance, and Exchange Online Protection, the module from the PowerShell Gallery that you use to connect is [ExchangeOnlineManagement](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/). For more information, see [About the Exchange Online PowerShell module](../../docs-conceptual/exchange-online-powershell-v2.md). +> +> For Exchange Server, there is no Microsoft-provided module in the PowerShell Gallery. Instead, to use PowerShell in Exchange, you have the following options: +> +> - Use the Exchange Management Shell on an Exchange server or that you've installed locally on your own computer using a **Management tools** only installation of Exchange server. For more information, see [Install the Exchange Server Management Tools](/Exchange/plan-and-deploy/post-installation-tasks/install-management-tools) and [Open the Exchange Management Shell](../../docs-conceptual/open-the-exchange-management-shell.md). +> - Use remote PowerShell from a Windows PowerShell session. For more information, see [Connect to Exchange servers using remote PowerShell](../../docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md). + +## active-directory Cmdlets +### [Add-ADPermission](Add-ADPermission.md) + +### [Dump-ProvisioningCache](Dump-ProvisioningCache.md) + +### [Get-ADPermission](Get-ADPermission.md) + +### [Get-ADServerSettings](Get-ADServerSettings.md) + +### [Get-ADSite](Get-ADSite.md) + +### [Get-AdSiteLink](Get-AdSiteLink.md) + +### [Get-DomainController](Get-DomainController.md) + +### [Get-OrganizationalUnit](Get-OrganizationalUnit.md) + +### [Get-Trust](Get-Trust.md) + +### [Get-UserPrincipalNamesSuffix](Get-UserPrincipalNamesSuffix.md) + +### [Remove-ADPermission](Remove-ADPermission.md) + +### [Reset-ProvisioningCache](Reset-ProvisioningCache.md) + +### [Set-ADServerSettings](Set-ADServerSettings.md) + +### [Set-ADSite](Set-ADSite.md) + +### [Set-AdSiteLink](Set-AdSiteLink.md) + +## defender-for-office-365 Cmdlets +### [Disable-AntiPhishRule](Disable-AntiPhishRule.md) + +### [Disable-ATPProtectionPolicyRule](Disable-ATPProtectionPolicyRule.md) + +### [Disable-SafeAttachmentRule](Disable-SafeAttachmentRule.md) + +### [Disable-SafeLinksRule](Disable-SafeLinksRule.md) + +### [Enable-AntiPhishRule](Enable-AntiPhishRule.md) + +### [Enable-ATPProtectionPolicyRule](Enable-ATPProtectionPolicyRule.md) + +### [Enable-SafeAttachmentRule](Enable-SafeAttachmentRule.md) + +### [Enable-SafeLinksRule](Enable-SafeLinksRule.md) + +### [Get-AntiPhishPolicy](Get-AntiPhishPolicy.md) + +### [Get-AntiPhishRule](Get-AntiPhishRule.md) + +### [Get-ATPBuiltInProtectionRule](Get-ATPBuiltInProtectionRule.md) + +### [Get-AtpPolicyForO365](Get-AtpPolicyForO365.md) + +### [Get-ATPProtectionPolicyRule](Get-ATPProtectionPolicyRule.md) + +### [Get-ATPTotalTrafficReport](Get-ATPTotalTrafficReport.md) + +### [Get-ContentMalwareMdoAggregateReport](Get-ContentMalwareMdoAggregateReport.md) + +### [Get-ContentMalwareMdoDetailReport](Get-ContentMalwareMdoDetailReport.md) + +### [Get-EmailTenantSettings](Get-EmailTenantSettings.md) + +### [Get-MailDetailATPReport](Get-MailDetailATPReport.md) + +### [Get-MailTrafficATPReport](Get-MailTrafficATPReport.md) + +### [Get-SafeAttachmentPolicy](Get-SafeAttachmentPolicy.md) + +### [Get-SafeAttachmentRule](Get-SafeAttachmentRule.md) + +### [Get-SafeLinksAggregateReport](Get-SafeLinksAggregateReport.md) + +### [Get-SafeLinksDetailReport](Get-SafeLinksDetailReport.md) + +### [Get-SafeLinksPolicy](Get-SafeLinksPolicy.md) + +### [Get-SafeLinksRule](Get-SafeLinksRule.md) + +### [Get-SpoofIntelligenceInsight](Get-SpoofIntelligenceInsight.md) + +### [Get-SpoofMailReport](Get-SpoofMailReport.md) + +### [New-AntiPhishPolicy](New-AntiPhishPolicy.md) + +### [New-AntiPhishRule](New-AntiPhishRule.md) + +### [New-ATPBuiltInProtectionRule](New-ATPBuiltInProtectionRule.md) + +### [New-ATPProtectionPolicyRule](New-ATPProtectionPolicyRule.md) + +### [New-SafeAttachmentPolicy](New-SafeAttachmentPolicy.md) + +### [New-SafeAttachmentRule](New-SafeAttachmentRule.md) + +### [New-SafeLinksPolicy](New-SafeLinksPolicy.md) + +### [New-SafeLinksRule](New-SafeLinksRule.md) + +### [Remove-AntiPhishPolicy](Remove-AntiPhishPolicy.md) + +### [Remove-AntiPhishRule](Remove-AntiPhishRule.md) + +### [Remove-ATPProtectionPolicyRule](Remove-ATPProtectionPolicyRule.md) + +### [Remove-SafeAttachmentPolicy](Remove-SafeAttachmentPolicy.md) + +### [Remove-SafeAttachmentRule](Remove-SafeAttachmentRule.md) + +### [Remove-SafeLinksPolicy](Remove-SafeLinksPolicy.md) + +### [Remove-SafeLinksRule](Remove-SafeLinksRule.md) + +### [Set-AntiPhishPolicy](Set-AntiPhishPolicy.md) + +### [Set-AntiPhishRule](Set-AntiPhishRule.md) + +### [Set-ATPBuiltInProtectionRule](Set-ATPBuiltInProtectionRule.md) + +### [Set-AtpPolicyForO365](Set-AtpPolicyForO365.md) + +### [Set-ATPProtectionPolicyRule](Set-ATPProtectionPolicyRule.md) + +### [Set-EmailTenantSettings](Set-EmailTenantSettings.md) + +### [Set-SafeAttachmentPolicy](Set-SafeAttachmentPolicy.md) + +### [Set-SafeAttachmentRule](Set-SafeAttachmentRule.md) + +### [Set-SafeLinksPolicy](Set-SafeLinksPolicy.md) + +### [Set-SafeLinksRule](Set-SafeLinksRule.md) + +## antispam-antimalware Cmdlets +### [Add-AttachmentFilterEntry](Add-AttachmentFilterEntry.md) + +### [Add-ContentFilterPhrase](Add-ContentFilterPhrase.md) + +### [Add-IPAllowListEntry](Add-IPAllowListEntry.md) + +### [Add-IPAllowListProvider](Add-IPAllowListProvider.md) + +### [Add-IPBlockListEntry](Add-IPBlockListEntry.md) + +### [Add-IPBlockListProvider](Add-IPBlockListProvider.md) + +### [Delete-QuarantineMessage](Delete-QuarantineMessage.md) + +### [Disable-EOPProtectionPolicyRule](Disable-EOPProtectionPolicyRule.md) + +### [Disable-HostedContentFilterRule](Disable-HostedContentFilterRule.md) + +### [Disable-HostedOutboundSpamFilterRule](Disable-HostedOutboundSpamFilterRule.md) + +### [Disable-MalwareFilterRule](Disable-MalwareFilterRule.md) + +### [Disable-ReportSubmissionRule](Disable-ReportSubmissionRule.md) + +### [Enable-AntispamUpdates](Enable-AntispamUpdates.md) + +### [Enable-EOPProtectionPolicyRule](Enable-EOPProtectionPolicyRule.md) + +### [Enable-HostedContentFilterRule](Enable-HostedContentFilterRule.md) + +### [Enable-HostedOutboundSpamFilterRule](Enable-HostedOutboundSpamFilterRule.md) + +### [Enable-MalwareFilterRule](Enable-MalwareFilterRule.md) + +### [Export-QuarantineMessage](Export-QuarantineMessage.md) + +### [Enable-ReportSubmissionRule](Enable-ReportSubmissionRule.md) + +### [Get-AgentLog](Get-AgentLog.md) + +### [Get-AggregateZapReport](Get-AggregateZapReport.md) + +### [Get-ArcConfig](Get-ArcConfig.md) + +### [Get-AttachmentFilterEntry](Get-AttachmentFilterEntry.md) + +### [Get-AttachmentFilterListConfig](Get-AttachmentFilterListConfig.md) + +### [Get-BlockedConnector](Get-BlockedConnector.md) + +### [Get-BlockedSenderAddress](Get-BlockedSenderAddress.md) + +### [Get-ConfigAnalyzerPolicyRecommendation](Get-ConfigAnalyzerPolicyRecommendation.md) + +### [Get-ContentFilterConfig](Get-ContentFilterConfig.md) + +### [Get-ContentFilterPhrase](Get-ContentFilterPhrase.md) + +### [Get-DetailZapReport](Get-DetailZapReport.md) + +### [Get-DkimSigningConfig](Get-DkimSigningConfig.md) + +### [Get-EOPProtectionPolicyRule](Get-EOPProtectionPolicyRule.md) + +### [Get-ExoPhishSimOverrideRule](Get-ExoPhishSimOverrideRule.md) + +### [Get-ExoSecOpsOverrideRule](Get-ExoSecOpsOverrideRule.md) + +### [Get-HostedConnectionFilterPolicy](Get-HostedConnectionFilterPolicy.md) + +### [Get-HostedContentFilterPolicy](Get-HostedContentFilterPolicy.md) + +### [Get-HostedContentFilterRule](Get-HostedContentFilterRule.md) + +### [Get-HostedOutboundSpamFilterPolicy](Get-HostedOutboundSpamFilterPolicy.md) + +### [Get-HostedOutboundSpamFilterRule](Get-HostedOutboundSpamFilterRule.md) + +### [Get-IPAllowListConfig](Get-IPAllowListConfig.md) + +### [Get-IPAllowListEntry](Get-IPAllowListEntry.md) + +### [Get-IPAllowListProvider](Get-IPAllowListProvider.md) + +### [Get-IPAllowListProvidersConfig](Get-IPAllowListProvidersConfig.md) + +### [Get-IPBlockListConfig](Get-IPBlockListConfig.md) + +### [Get-IPBlockListEntry](Get-IPBlockListEntry.md) + +### [Get-IPBlockListProvider](Get-IPBlockListProvider.md) + +### [Get-IPBlockListProvidersConfig](Get-IPBlockListProvidersConfig.md) + +### [Get-MailboxJunkEmailConfiguration](Get-MailboxJunkEmailConfiguration.md) + +### [Get-MalwareFilteringServer](Get-MalwareFilteringServer.md) + +### [Get-MalwareFilterPolicy](Get-MalwareFilterPolicy.md) + +### [Get-MalwareFilterRule](Get-MalwareFilterRule.md) + +### [Get-PhishSimOverridePolicy](Get-PhishSimOverridePolicy.md) + +### [Get-QuarantineMessage](Get-QuarantineMessage.md) + +### [Get-QuarantineMessageHeader](Get-QuarantineMessageHeader.md) + +### [Get-QuarantinePolicy](Get-QuarantinePolicy.md) + +### [Get-RecipientFilterConfig](Get-RecipientFilterConfig.md) + +### [Get-ReportSubmissionPolicy](Get-ReportSubmissionPolicy.md) + +### [Get-ReportSubmissionRule](Get-ReportSubmissionRule.md) + +### [Get-SecOpsOverridePolicy](Get-SecOpsOverridePolicy.md) + +### [Get-SenderFilterConfig](Get-SenderFilterConfig.md) + +### [Get-SenderIdConfig](Get-SenderIdConfig.md) + +### [Get-SenderReputationConfig](Get-SenderReputationConfig.md) + +### [Get-TeamsProtectionPolicy](Get-TeamsProtectionPolicy.md) + +### [Get-TeamsProtectionPolicyRule](Get-TeamsProtectionPolicyRule.md) + +### [Get-TenantAllowBlockListItems](Get-TenantAllowBlockListItems.md) + +### [Get-TenantAllowBlockListSpoofItems](Get-TenantAllowBlockListSpoofItems.md) + +### [New-DkimSigningConfig](New-DkimSigningConfig.md) + +### [New-EOPProtectionPolicyRule](New-EOPProtectionPolicyRule.md) + +### [New-ExoPhishSimOverrideRule](New-ExoPhishSimOverrideRule.md) + +### [New-ExoSecOpsOverrideRule](New-ExoSecOpsOverrideRule.md) + +### [New-HostedContentFilterPolicy](New-HostedContentFilterPolicy.md) + +### [New-HostedContentFilterRule](New-HostedContentFilterRule.md) + +### [New-HostedOutboundSpamFilterPolicy](New-HostedOutboundSpamFilterPolicy.md) + +### [New-HostedOutboundSpamFilterRule](New-HostedOutboundSpamFilterRule.md) + +### [New-MalwareFilterPolicy](New-MalwareFilterPolicy.md) + +### [New-MalwareFilterRule](New-MalwareFilterRule.md) + +### [New-PhishSimOverridePolicy](New-PhishSimOverridePolicy.md) + +### [New-QuarantinePermissions](New-QuarantinePermissions.md) + +### [New-QuarantinePolicy](New-QuarantinePolicy.md) + +### [New-ReportSubmissionPolicy](New-ReportSubmissionPolicy.md) + +### [New-ReportSubmissionRule](New-ReportSubmissionRule.md) + +### [New-SecOpsOverridePolicy](New-SecOpsOverridePolicy.md) + +### [New-TeamsProtectionPolicy](New-TeamsProtectionPolicy.md) + +### [New-TeamsProtectionPolicyRule](New-TeamsProtectionPolicyRule.md) + +### [New-TenantAllowBlockListItems](New-TenantAllowBlockListItems.md) + +### [New-TenantAllowBlockListSpoofItems](New-TenantAllowBlockListSpoofItems.md) + +### [Preview-QuarantineMessage](Preview-QuarantineMessage.md) + +### [Release-QuarantineMessage](Release-QuarantineMessage.md) + +### [Remove-AttachmentFilterEntry](Remove-AttachmentFilterEntry.md) + +### [Remove-BlockedConnector](Remove-BlockedConnector.md) + +### [Remove-BlockedSenderAddress](Remove-BlockedSenderAddress.md) + +### [Remove-ContentFilterPhrase](Remove-ContentFilterPhrase.md) + +### [Remove-EOPProtectionPolicyRule](Remove-EOPProtectionPolicyRule.md) + +### [Remove-ExoPhishSimOverrideRule](Remove-ExoPhishSimOverrideRule.md) + +### [Remove-ExoSecOpsOverrideRule](Remove-ExoSecOpsOverrideRule.md) + +### [Remove-HostedContentFilterPolicy](Remove-HostedContentFilterPolicy.md) + +### [Remove-HostedContentFilterRule](Remove-HostedContentFilterRule.md) + +### [Remove-HostedOutboundSpamFilterPolicy](Remove-HostedOutboundSpamFilterPolicy.md) + +### [Remove-HostedOutboundSpamFilterRule](Remove-HostedOutboundSpamFilterRule.md) + +### [Remove-IPAllowListEntry](Remove-IPAllowListEntry.md) + +### [Remove-IPAllowListProvider](Remove-IPAllowListProvider.md) + +### [Remove-IPBlockListEntry](Remove-IPBlockListEntry.md) + +### [Remove-IPBlockListProvider](Remove-IPBlockListProvider.md) + +### [Remove-MalwareFilterPolicy](Remove-MalwareFilterPolicy.md) + +### [Remove-MalwareFilterRule](Remove-MalwareFilterRule.md) + +### [Remove-PhishSimOverridePolicy](Remove-PhishSimOverridePolicy.md) + +### [Remove-QuarantinePolicy](Remove-QuarantinePolicy.md) + +### [Remove-ReportSubmissionPolicy](Remove-ReportSubmissionPolicy.md) + +### [Remove-ReportSubmissionRule](Remove-ReportSubmissionRule.md) + +### [Remove-SecOpsOverridePolicy](Remove-SecOpsOverridePolicy.md) + +### [Remove-TenantAllowBlockListItems](Remove-TenantAllowBlockListItems.md) + +### [Remove-TenantAllowBlockListSpoofItems](Remove-TenantAllowBlockListSpoofItems.md) + +### [Rotate-DkimSigningConfig](Rotate-DkimSigningConfig.md) + +### [Set-ArcConfig](Set-ArcConfig.md) + +### [Set-AttachmentFilterListConfig](Set-AttachmentFilterListConfig.md) + +### [Set-ContentFilterConfig](Set-ContentFilterConfig.md) + +### [Set-DkimSigningConfig](Set-DkimSigningConfig.md) + +### [Set-EOPProtectionPolicyRule](Set-EOPProtectionPolicyRule.md) + +### [Set-ExoPhishSimOverrideRule](Set-ExoPhishSimOverrideRule.md) + +### [Set-ExoSecOpsOverrideRule](Remove-ExoSecOpsOverrideRule.md) + +### [Set-HostedConnectionFilterPolicy](Set-HostedConnectionFilterPolicy.md) + +### [Set-HostedContentFilterPolicy](Set-HostedContentFilterPolicy.md) + +### [Set-HostedContentFilterRule](Set-HostedContentFilterRule.md) + +### [Set-HostedOutboundSpamFilterPolicy](Set-HostedOutboundSpamFilterPolicy.md) + +### [Set-HostedOutboundSpamFilterRule](Set-HostedOutboundSpamFilterRule.md) + +### [Set-IPAllowListConfig](Set-IPAllowListConfig.md) + +### [Set-IPAllowListProvider](Set-IPAllowListProvider.md) + +### [Set-IPAllowListProvidersConfig](Set-IPAllowListProvidersConfig.md) + +### [Set-IPBlockListConfig](Set-IPBlockListConfig.md) + +### [Set-IPBlockListProvider](Set-IPBlockListProvider.md) + +### [Set-IPBlockListProvidersConfig](Set-IPBlockListProvidersConfig.md) + +### [Set-MailboxJunkEmailConfiguration](Set-MailboxJunkEmailConfiguration.md) + +### [Set-MalwareFilteringServer](Set-MalwareFilteringServer.md) + +### [Set-MalwareFilterPolicy](Set-MalwareFilterPolicy.md) + +### [Set-MalwareFilterRule](Set-MalwareFilterRule.md) + +### [Set-PhishSimOverridePolicy](Set-PhishSimOverridePolicy.md) + +### [Set-QuarantinePermissions](Set-QuarantinePermissions.md) + +### [Set-QuarantinePolicy](Set-QuarantinePolicy.md) + +### [Set-RecipientFilterConfig](Set-RecipientFilterConfig.md) + +### [Set-ReportSubmissionPolicy](Set-ReportSubmissionPolicy.md) + +### [Set-ReportSubmissionRule](Set-ReportSubmissionRule.md) + +### [Set-SecOpsOverridePolicy](Set-SecOpsOverridePolicy.md) + +### [Set-SenderFilterConfig](Set-SenderFilterConfig.md) + +### [Set-SenderIdConfig](Set-SenderIdConfig.md) + +### [Set-SenderReputationConfig](Set-SenderReputationConfig.md) + +### [Set-TeamsProtectionPolicy](Set-TeamsProtectionPolicy.md) + +### [Set-TeamsProtectionPolicyRule](Set-TeamsProtectionPolicyRule.md) + +### [Set-TenantAllowBlockListItems](Set-TenantAllowBlockListItems.md) + +### [Set-TenantAllowBlockListSpoofItems](Set-TenantAllowBlockListSpoofItems.md) + +### [Test-IPAllowListProvider](Test-IPAllowListProvider.md) + +### [Test-IPBlockListProvider](Test-IPBlockListProvider.md) + +### [Test-SenderId](Test-SenderId.md) + +### [Update-SafeList](Update-SafeList.md) + +## client-access Cmdlets +### [Clear-TextMessagingAccount](Clear-TextMessagingAccount.md) + +### [Compare-TextMessagingVerificationCode](Compare-TextMessagingVerificationCode.md) + +### [Disable-PushNotificationProxy](Disable-PushNotificationProxy.md) + +### [Enable-PushNotificationProxy](Enable-PushNotificationProxy.md) + +### [Export-AutoDiscoverConfig](Export-AutoDiscoverConfig.md) + +### [Get-CASMailbox](Get-CASMailbox.md) + +### [Get-CASMailboxPlan](Get-CASMailboxPlan.md) + +### [Get-ClientAccessRule](Get-ClientAccessRule.md) + +### [Get-ImapSettings](Get-ImapSettings.md) + +### [Get-MailboxCalendarConfiguration](Get-MailboxCalendarConfiguration.md) + +### [Get-MailboxMessageConfiguration](Get-MailboxMessageConfiguration.md) + +### [Get-MailboxRegionalConfiguration](Get-MailboxRegionalConfiguration.md) + +### [Get-MailboxSpellingConfiguration](Get-MailboxSpellingConfiguration.md) + +### [Get-OutlookProvider](Get-OutlookProvider.md) + +### [Get-OwaMailboxPolicy](Get-OwaMailboxPolicy.md) + +### [Get-PopSettings](Get-PopSettings.md) + +### [Get-TextMessagingAccount](Get-TextMessagingAccount.md) + +### [New-ClientAccessRule](New-ClientAccessRule.md) + +### [New-OutlookProvider](New-OutlookProvider.md) + +### [New-OwaMailboxPolicy](New-OwaMailboxPolicy.md) + +### [Remove-ClientAccessRule](Remove-ClientAccessRule.md) + +### [Remove-OutlookProvider](Remove-OutlookProvider.md) + +### [Remove-OwaMailboxPolicy](Remove-OwaMailboxPolicy.md) + +### [Send-TextMessagingVerificationCode](Send-TextMessagingVerificationCode.md) + +### [Set-CASMailbox](Set-CASMailbox.md) + +### [Set-CASMailboxPlan](Set-CASMailboxPlan.md) + +### [Set-ClientAccessRule](Set-ClientAccessRule.md) + +### [Set-ImapSettings](Set-ImapSettings.md) + +### [Set-MailboxCalendarConfiguration](Set-MailboxCalendarConfiguration.md) + +### [Set-MailboxMessageConfiguration](Set-MailboxMessageConfiguration.md) + +### [Set-MailboxRegionalConfiguration](Set-MailboxRegionalConfiguration.md) + +### [Set-MailboxSpellingConfiguration](Set-MailboxSpellingConfiguration.md) + +### [Set-OutlookProvider](Set-OutlookProvider.md) + +### [Set-OwaMailboxPolicy](Set-OwaMailboxPolicy.md) + +### [Set-PopSettings](Set-PopSettings.md) + +### [Set-TextMessagingAccount](Set-TextMessagingAccount.md) + +### [Test-CalendarConnectivity](Test-CalendarConnectivity.md) + +### [Test-ClientAccessRule](Test-ClientAccessRule.md) + +### [Test-EcpConnectivity](Test-EcpConnectivity.md) + +### [Test-ImapConnectivity](Test-ImapConnectivity.md) + +### [Test-OutlookConnectivity](Test-OutlookConnectivity.md) + +### [Test-OutlookWebServices](Test-OutlookWebServices.md) + +### [Test-OwaConnectivity](Test-OwaConnectivity.md) + +### [Test-PopConnectivity](Test-PopConnectivity.md) + +### [Test-PowerShellConnectivity](Test-PowerShellConnectivity.md) + +### [Test-WebServicesConnectivity](Test-WebServicesConnectivity.md) + +## client-access-servers Cmdlets +### [Disable-OutlookAnywhere](Disable-OutlookAnywhere.md) + +### [Enable-OutlookAnywhere](Enable-OutlookAnywhere.md) + +### [Get-ActiveSyncVirtualDirectory](Get-ActiveSyncVirtualDirectory.md) + +### [Get-AuthRedirect](Get-AuthRedirect.md) + +### [Get-AutodiscoverVirtualDirectory](Get-AutodiscoverVirtualDirectory.md) + +### [Get-ClientAccessArray](Get-ClientAccessArray.md) + +### [Get-ClientAccessServer](Get-ClientAccessServer.md) + +### [Get-ClientAccessService](Get-ClientAccessService.md) + +### [Get-EcpVirtualDirectory](Get-EcpVirtualDirectory.md) + +### [Get-MapiVirtualDirectory](Get-MapiVirtualDirectory.md) + +### [Get-OutlookAnywhere](Get-OutlookAnywhere.md) + +### [Get-OwaVirtualDirectory](Get-OwaVirtualDirectory.md) + +### [Get-PowerShellVirtualDirectory](Get-PowerShellVirtualDirectory.md) + +### [Get-RpcClientAccess](Get-RpcClientAccess.md) + +### [Get-WebServicesVirtualDirectory](Get-WebServicesVirtualDirectory.md) + +### [New-ActiveSyncVirtualDirectory](New-ActiveSyncVirtualDirectory.md) + +### [New-AuthRedirect](New-AuthRedirect.md) + +### [New-AutodiscoverVirtualDirectory](New-AutodiscoverVirtualDirectory.md) + +### [New-ClientAccessArray](New-ClientAccessArray.md) + +### [New-EcpVirtualDirectory](New-EcpVirtualDirectory.md) + +### [New-MapiVirtualDirectory](New-MapiVirtualDirectory.md) + +### [New-OwaVirtualDirectory](New-OwaVirtualDirectory.md) + +### [New-PowerShellVirtualDirectory](New-PowerShellVirtualDirectory.md) + +### [New-RpcClientAccess](New-RpcClientAccess.md) + +### [New-WebServicesVirtualDirectory](New-WebServicesVirtualDirectory.md) + +### [Remove-ActiveSyncVirtualDirectory](Remove-ActiveSyncVirtualDirectory.md) + +### [Remove-AuthRedirect](Remove-AuthRedirect.md) + +### [Remove-AutodiscoverVirtualDirectory](Remove-AutodiscoverVirtualDirectory.md) + +### [Remove-ClientAccessArray](Remove-ClientAccessArray.md) + +### [Remove-EcpVirtualDirectory](Remove-EcpVirtualDirectory.md) + +### [Remove-MapiVirtualDirectory](Remove-MapiVirtualDirectory.md) + +### [Remove-OwaVirtualDirectory](Remove-OwaVirtualDirectory.md) + +### [Remove-PowerShellVirtualDirectory](Remove-PowerShellVirtualDirectory.md) + +### [Remove-RpcClientAccess](Remove-RpcClientAccess.md) + +### [Remove-WebServicesVirtualDirectory](Remove-WebServicesVirtualDirectory.md) + +### [Set-ActiveSyncVirtualDirectory](Set-ActiveSyncVirtualDirectory.md) + +### [Set-AuthRedirect](Set-AuthRedirect.md) + +### [Set-AutodiscoverVirtualDirectory](Set-AutodiscoverVirtualDirectory.md) + +### [Set-ClientAccessArray](Set-ClientAccessArray.md) + +### [Set-ClientAccessServer](Set-ClientAccessServer.md) + +### [Set-ClientAccessService](Set-ClientAccessService.md) + +### [Set-EcpVirtualDirectory](Set-EcpVirtualDirectory.md) + +### [Set-MapiVirtualDirectory](Set-MapiVirtualDirectory.md) + +### [Set-OutlookAnywhere](Set-OutlookAnywhere.md) + +### [Set-OwaVirtualDirectory](Set-OwaVirtualDirectory.md) + +### [Set-PowerShellVirtualDirectory](Set-PowerShellVirtualDirectory.md) + +### [Set-RpcClientAccess](Set-RpcClientAccess.md) + +### [Set-WebServicesVirtualDirectory](Set-WebServicesVirtualDirectory.md) + +## database-availability-groups Cmdlets +### [Add-DatabaseAvailabilityGroupServer](Add-DatabaseAvailabilityGroupServer.md) + +### [Add-MailboxDatabaseCopy](Add-MailboxDatabaseCopy.md) + +### [Get-DatabaseAvailabilityGroup](Get-DatabaseAvailabilityGroup.md) + +### [Get-DatabaseAvailabilityGroupNetwork](Get-DatabaseAvailabilityGroupNetwork.md) + +### [Get-MailboxDatabaseCopyStatus](Get-MailboxDatabaseCopyStatus.md) + +### [Move-ActiveMailboxDatabase](Move-ActiveMailboxDatabase.md) + +### [New-DatabaseAvailabilityGroup](New-DatabaseAvailabilityGroup.md) + +### [New-DatabaseAvailabilityGroupNetwork](New-DatabaseAvailabilityGroupNetwork.md) + +### [Remove-DatabaseAvailabilityGroup](Remove-DatabaseAvailabilityGroup.md) + +### [Remove-DatabaseAvailabilityGroupNetwork](Remove-DatabaseAvailabilityGroupNetwork.md) + +### [Remove-DatabaseAvailabilityGroupServer](Remove-DatabaseAvailabilityGroupServer.md) + +### [Remove-MailboxDatabaseCopy](Remove-MailboxDatabaseCopy.md) + +### [Restore-DatabaseAvailabilityGroup](Restore-DatabaseAvailabilityGroup.md) + +### [Resume-MailboxDatabaseCopy](Resume-MailboxDatabaseCopy.md) + +### [Set-DatabaseAvailabilityGroup](Set-DatabaseAvailabilityGroup.md) + +### [Set-DatabaseAvailabilityGroupNetwork](Set-DatabaseAvailabilityGroupNetwork.md) + +### [Set-MailboxDatabaseCopy](Set-MailboxDatabaseCopy.md) + +### [Start-DatabaseAvailabilityGroup](Start-DatabaseAvailabilityGroup.md) + +### [Stop-DatabaseAvailabilityGroup](Stop-DatabaseAvailabilityGroup.md) + +### [Suspend-MailboxDatabaseCopy](Suspend-MailboxDatabaseCopy.md) + +### [Test-ReplicationHealth](Test-ReplicationHealth.md) + +### [Update-MailboxDatabaseCopy](Update-MailboxDatabaseCopy.md) + +## devices Cmdlets +### [Clear-ActiveSyncDevice](Clear-ActiveSyncDevice.md) + +### [Clear-MobileDevice](Clear-MobileDevice.md) + +### [Export-ActiveSyncLog](Export-ActiveSyncLog.md) + +### [Get-ActiveSyncDevice](Get-ActiveSyncDevice.md) + +### [Get-ActiveSyncDeviceAccessRule](Get-ActiveSyncDeviceAccessRule.md) + +### [Get-ActiveSyncDeviceAutoblockThreshold](Get-ActiveSyncDeviceAutoblockThreshold.md) + +### [Get-ActiveSyncDeviceClass](Get-ActiveSyncDeviceClass.md) + +### [Get-ActiveSyncDeviceStatistics](Get-ActiveSyncDeviceStatistics.md) + +### [Get-ActiveSyncMailboxPolicy](Get-ActiveSyncMailboxPolicy.md) + +### [Get-ActiveSyncOrganizationSettings](Get-ActiveSyncOrganizationSettings.md) + +### [Get-DeviceConditionalAccessPolicy](Get-DeviceConditionalAccessPolicy.md) + +### [Get-DeviceConditionalAccessRule](Get-DeviceConditionalAccessRule.md) + +### [Get-DeviceConfigurationPolicy](Get-DeviceConfigurationPolicy.md) + +### [Get-DeviceConfigurationRule](Get-DeviceConfigurationRule.md) + +### [Get-DevicePolicy](Get-DevicePolicy.md) + +### [Get-DeviceTenantPolicy](Get-DeviceTenantPolicy.md) + +### [Get-DeviceTenantRule](Get-DeviceTenantRule.md) + +### [Get-MobileDevice](Get-MobileDevice.md) + +### [Get-MobileDeviceMailboxPolicy](Get-MobileDeviceMailboxPolicy.md) + +### [Get-MobileDeviceStatistics](Get-MobileDeviceStatistics.md) + +### [New-ActiveSyncDeviceAccessRule](New-ActiveSyncDeviceAccessRule.md) + +### [New-ActiveSyncMailboxPolicy](New-ActiveSyncMailboxPolicy.md) + +### [New-DeviceConditionalAccessPolicy](New-DeviceConditionalAccessPolicy.md) + +### [New-DeviceConditionalAccessRule](New-DeviceConditionalAccessRule.md) + +### [New-DeviceConfigurationPolicy](New-DeviceConfigurationPolicy.md) + +### [New-DeviceConfigurationRule](New-DeviceConfigurationRule.md) + +### [New-DeviceTenantPolicy](New-DeviceTenantPolicy.md) + +### [New-DeviceTenantRule](New-DeviceTenantRule.md) + +### [New-MobileDeviceMailboxPolicy](New-MobileDeviceMailboxPolicy.md) + +### [Remove-ActiveSyncDevice](Remove-ActiveSyncDevice.md) + +### [Remove-ActiveSyncDeviceAccessRule](Remove-ActiveSyncDeviceAccessRule.md) + +### [Remove-ActiveSyncDeviceClass](Remove-ActiveSyncDeviceClass.md) + +### [Remove-ActiveSyncMailboxPolicy](Remove-ActiveSyncMailboxPolicy.md) + +### [Remove-DeviceConditionalAccessPolicy](Remove-DeviceConditionalAccessPolicy.md) + +### [Remove-DeviceConditionalAccessRule](Remove-DeviceConditionalAccessRule.md) + +### [Remove-DeviceConfigurationPolicy](Remove-DeviceConfigurationPolicy.md) + +### [Remove-DeviceConfigurationRule](Remove-DeviceConfigurationRule.md) + +### [Remove-DeviceTenantPolicy](Remove-DeviceTenantPolicy.md) + +### [Remove-DeviceTenantRule](Remove-DeviceTenantRule.md) + +### [Remove-MobileDevice](Remove-MobileDevice.md) + +### [Remove-MobileDeviceMailboxPolicy](Remove-MobileDeviceMailboxPolicy.md) + +### [Set-ActiveSyncDeviceAccessRule](Set-ActiveSyncDeviceAccessRule.md) + +### [Set-ActiveSyncDeviceAutoblockThreshold](Set-ActiveSyncDeviceAutoblockThreshold.md) + +### [Set-ActiveSyncMailboxPolicy](Set-ActiveSyncMailboxPolicy.md) + +### [Set-ActiveSyncOrganizationSettings](Set-ActiveSyncOrganizationSettings.md) + +### [Set-DeviceConditionalAccessPolicy](Set-DeviceConditionalAccessPolicy.md) + +### [Set-DeviceConditionalAccessRule](Set-DeviceConditionalAccessRule.md) + +### [Set-DeviceConfigurationPolicy](Set-DeviceConfigurationPolicy.md) + +### [Set-DeviceConfigurationRule](Set-DeviceConfigurationRule.md) + +### [Set-DeviceTenantPolicy](Set-DeviceTenantPolicy.md) + +### [Set-DeviceTenantRule](Set-DeviceTenantRule.md) + +### [Set-MobileDeviceMailboxPolicy](Set-MobileDeviceMailboxPolicy.md) + +### [Test-ActiveSyncConnectivity](Test-ActiveSyncConnectivity.md) + +## email-addresses-and-address-books Cmdlets +### [Disable-AddressListPaging](Disable-AddressListPaging.md) + +### [Enable-AddressListPaging](Enable-AddressListPaging.md) + +### [Get-AddressBookPolicy](Get-AddressBookPolicy.md) + +### [Get-AddressList](Get-AddressList.md) + +### [Get-DetailsTemplate](Get-DetailsTemplate.md) + +### [Get-EmailAddressPolicy](Get-EmailAddressPolicy.md) + +### [Get-GlobalAddressList](Get-GlobalAddressList.md) + +### [Get-OabVirtualDirectory](Get-OabVirtualDirectory.md) + +### [Get-OfflineAddressBook](Get-OfflineAddressBook.md) + +### [Move-AddressList](Move-AddressList.md) + +### [Move-OfflineAddressBook](Move-OfflineAddressBook.md) + +### [New-AddressBookPolicy](New-AddressBookPolicy.md) + +### [New-AddressList](New-AddressList.md) + +### [New-EmailAddressPolicy](New-EmailAddressPolicy.md) + +### [New-GlobalAddressList](New-GlobalAddressList.md) + +### [New-OabVirtualDirectory](New-OabVirtualDirectory.md) + +### [New-OfflineAddressBook](New-OfflineAddressBook.md) + +### [Remove-AddressBookPolicy](Remove-AddressBookPolicy.md) + +### [Remove-AddressList](Remove-AddressList.md) + +### [Remove-EmailAddressPolicy](Remove-EmailAddressPolicy.md) + +### [Remove-GlobalAddressList](Remove-GlobalAddressList.md) + +### [Remove-OabVirtualDirectory](Remove-OabVirtualDirectory.md) + +### [Remove-OfflineAddressBook](Remove-OfflineAddressBook.md) + +### [Restore-DetailsTemplate](Restore-DetailsTemplate.md) + +### [Set-AddressBookPolicy](Set-AddressBookPolicy.md) + +### [Set-AddressList](Set-AddressList.md) + +### [Set-DetailsTemplate](Set-DetailsTemplate.md) + +### [Set-EmailAddressPolicy](Set-EmailAddressPolicy.md) + +### [Set-GlobalAddressList](Set-GlobalAddressList.md) + +### [Set-OabVirtualDirectory](Set-OabVirtualDirectory.md) + +### [Set-OfflineAddressBook](Set-OfflineAddressBook.md) + +### [Update-AddressList](Update-AddressList.md) + +### [Update-EmailAddressPolicy](Update-EmailAddressPolicy.md) + +### [Update-GlobalAddressList](Update-GlobalAddressList.md) + +### [Update-OfflineAddressBook](Update-OfflineAddressBook.md) + +## encryption-and-certificates Cmdlets +### [Enable-ExchangeCertificate](Enable-ExchangeCertificate.md) + +### [Export-ExchangeCertificate](Export-ExchangeCertificate.md) + +### [Get-DataEncryptionPolicy](Get-DataEncryptionPolicy.md) + +### [Get-ExchangeCertificate](Get-ExchangeCertificate.md) + +### [Get-IRMConfiguration](Get-IRMConfiguration.md) + +### [Get-M365DataAtRestEncryptionPolicy](Get-M365DataAtRestEncryptionPolicy.md) + +### [Get-M365DataAtRestEncryptionPolicyAssignment](Get-M365DataAtRestEncryptionPolicyAssignment.md) + +### [Get-MailboxIRMAccess](Get-MailboxIRMAccess.md) + +### [Get-OMEConfiguration](Get-OMEConfiguration.md) + +### [Get-OMEMessageStatus](Get-OMEMessageStatus.md) + +### [Get-RMSTemplate](Get-RMSTemplate.md) + +### [Get-SmimeConfig](Get-SmimeConfig.md) + +### [Import-ExchangeCertificate](Import-ExchangeCertificate.md) + +### [New-DataEncryptionPolicy](New-DataEncryptionPolicy.md) + +### [New-ExchangeCertificate](New-ExchangeCertificate.md) + +### [New-M365DataAtRestEncryptionPolicy](New-M365DataAtRestEncryptionPolicy.md) + +### [New-OMEConfiguration](New-OMEConfiguration.md) + +### [Remove-ExchangeCertificate](Remove-ExchangeCertificate.md) + +### [Remove-MailboxIRMAccess](Remove-MailboxIRMAccess.md) + +### [Remove-OMEConfiguration](Remove-OMEConfiguration.md) + +### [Set-DataEncryptionPolicy](Set-DataEncryptionPolicy.md) + +### [Set-IRMConfiguration](Set-IRMConfiguration.md) + +### [Set-M365DataAtRestEncryptionPolicy](Set-M365DataAtRestEncryptionPolicy.md) + +### [Set-M365DataAtRestEncryptionPolicyAssignment](Set-M365DataAtRestEncryptionPolicyAssignment.md) + +### [Set-MailboxIRMAccess](Set-MailboxIRMAccess.md) + +### [Set-OMEConfiguration](Set-OMEConfiguration.md) + +### [Set-OMEMessageRevocation](Set-OMEMessageRevocation.md) + +### [Set-RMSTemplate](Set-RMSTemplate.md) + +### [Set-SmimeConfig](Set-SmimeConfig.md) + +### [Test-IRMConfiguration](Test-IRMConfiguration.md) + +## federation-and-hybrid Cmdlets +### [Add-FederatedDomain](Add-FederatedDomain.md) + +### [Disable-RemoteMailbox](Disable-RemoteMailbox.md) + +### [Enable-RemoteMailbox](Enable-RemoteMailbox.md) + +### [Get-FederatedDomainProof](Get-FederatedDomainProof.md) + +### [Get-FederatedOrganizationIdentifier](Get-FederatedOrganizationIdentifier.md) + +### [Get-FederationInformation](Get-FederationInformation.md) + +### [Get-FederationTrust](Get-FederationTrust.md) + +### [Get-HybridConfiguration](Get-HybridConfiguration.md) + +### [Get-HybridMailflowDatacenterIPs](Get-HybridMailflowDatacenterIPs.md) + +### [Get-IntraOrganizationConfiguration](Get-IntraOrganizationConfiguration.md) + +### [Get-IntraOrganizationConnector](Get-IntraOrganizationConnector.md) + +### [Get-OnPremisesOrganization](Get-OnPremisesOrganization.md) + +### [Get-PendingFederatedDomain](Get-PendingFederatedDomain.md) + +### [Get-RemoteMailbox](Get-RemoteMailbox.md) + +### [New-FederationTrust](New-FederationTrust.md) + +### [New-HybridConfiguration](New-HybridConfiguration.md) + +### [New-IntraOrganizationConnector](New-IntraOrganizationConnector.md) + +### [New-OnPremisesOrganization](New-OnPremisesOrganization.md) + +### [New-RemoteMailbox](New-RemoteMailbox.md) + +### [Remove-FederatedDomain](Remove-FederatedDomain.md) + +### [Remove-FederationTrust](Remove-FederationTrust.md) + +### [Remove-HybridConfiguration](Remove-HybridConfiguration.md) + +### [Remove-IntraOrganizationConnector](Remove-IntraOrganizationConnector.md) + +### [Remove-OnPremisesOrganization](Remove-OnPremisesOrganization.md) + +### [Remove-RemoteMailbox](Remove-RemoteMailbox.md) + +### [Set-FederatedOrganizationIdentifier](Set-FederatedOrganizationIdentifier.md) + +### [Set-FederationTrust](Set-FederationTrust.md) + +### [Set-HybridConfiguration](Set-HybridConfiguration.md) + +### [Set-IntraOrganizationConnector](Set-IntraOrganizationConnector.md) + +### [Set-OnPremisesOrganization](Set-OnPremisesOrganization.md) + +### [Set-PendingFederatedDomain](Set-PendingFederatedDomain.md) + +### [Set-RemoteMailbox](Set-RemoteMailbox.md) + +### [Test-FederationTrust](Test-FederationTrust.md) + +### [Test-FederationTrustCertificate](Test-FederationTrustCertificate.md) + +### [Update-HybridConfiguration](Update-HybridConfiguration.md) + +### [Update-Recipient](Update-Recipient.md) + +## mailbox-databases-and-servers Cmdlets +### [Clean-MailboxDatabase](Clean-MailboxDatabase.md) + +### [Disable-MailboxQuarantine](Disable-MailboxQuarantine.md) + +### [Disable-MetaCacheDatabase](Disable-MetaCacheDatabase.md) + +### [Dismount-Database](Dismount-Database.md) + +### [Enable-MailboxQuarantine](Enable-MailboxQuarantine.md) + +### [Enable-MetaCacheDatabase](Enable-MetaCacheDatabase.md) + +### [Get-FailedContentIndexDocuments](Get-FailedContentIndexDocuments.md) + +### [Get-MailboxDatabase](Get-MailboxDatabase.md) + +### [Get-MailboxRepairRequest](Get-MailboxRepairRequest.md) + +### [Get-MailboxServer](Get-MailboxServer.md) + +### [Get-SearchDocumentFormat](Get-SearchDocumentFormat.md) + +### [Get-StoreUsageStatistics](Get-StoreUsageStatistics.md) + +### [Mount-Database](Mount-Database.md) + +### [Move-DatabasePath](Move-DatabasePath.md) + +### [New-MailboxDatabase](New-MailboxDatabase.md) + +### [New-MailboxRepairRequest](New-MailboxRepairRequest.md) + +### [New-SearchDocumentFormat](New-SearchDocumentFormat.md) + +### [Remove-MailboxDatabase](Remove-MailboxDatabase.md) + +### [Remove-MailboxRepairRequest](Remove-MailboxRepairRequest.md) + +### [Remove-SearchDocumentFormat](Remove-SearchDocumentFormat.md) + +### [Remove-StoreMailbox](Remove-StoreMailbox.md) + +### [Set-MailboxDatabase](Set-MailboxDatabase.md) + +### [Set-MailboxServer](Set-MailboxServer.md) + +### [Set-SearchDocumentFormat](Set-SearchDocumentFormat.md) + +### [Start-MailboxAssistant](Start-MailboxAssistant.md) + +### [Test-AssistantHealth](Test-AssistantHealth.md) + +### [Test-ExchangeSearch](Test-ExchangeSearch.md) + +### [Test-MRSHealth](Test-MRSHealth.md) + +### [Update-DatabaseSchema](Update-DatabaseSchema.md) + +### [Update-FileDistributionService](Update-FileDistributionService.md) + +### [Update-StoreMailboxState](Update-StoreMailboxState.md) + +## mailboxes Cmdlets +### [Add-MailboxFolderPermission](Add-MailboxFolderPermission.md) + +### [Add-MailboxPermission](Add-MailboxPermission.md) + +### [Add-RecipientPermission](Add-RecipientPermission.md) + +### [Connect-Mailbox](Connect-Mailbox.md) + +### [Disable-App](Disable-App.md) + +### [Disable-InboxRule](Disable-InboxRule.md) + +### [Disable-Mailbox](Disable-Mailbox.md) + +### [Disable-ServiceEmailChannel](Disable-ServiceEmailChannel.md) + +### [Disable-SweepRule](Disable-SweepRule.md) + +### [Enable-App](Enable-App.md) + +### [Enable-InboxRule](Enable-InboxRule.md) + +### [Enable-Mailbox](Enable-Mailbox.md) + +### [Enable-ServiceEmailChannel](Enable-ServiceEmailChannel.md) + +### [Enable-SweepRule](Enable-SweepRule.md) + +### [Expedite-Delicensing](Expedite-Delicensing.md) + +### [Export-MailboxDiagnosticLogs](Export-MailboxDiagnosticLogs.md) + +### [Export-RecipientDataProperty](Export-RecipientDataProperty.md) + +### [Get-App](Get-App.md) + +### [Get-CalendarDiagnosticAnalysis](Get-CalendarDiagnosticAnalysis.md) + +### [Get-CalendarDiagnosticLog](Get-CalendarDiagnosticLog.md) + +### [Get-CalendarDiagnosticObjects](Get-CalendarDiagnosticObjects.md) + +### [Get-CalendarNotification](Get-CalendarNotification.md) + +### [Get-CalendarProcessing](Get-CalendarProcessing.md) + +### [Get-Clutter](Get-Clutter.md) + +### [Get-EventsFromEmailConfiguration](Get-EventsFromEmailConfiguration.md) + +### [Get-ExternalInOutlook](Get-ExternalInOutlook.md) + +### [Get-FocusedInbox](Get-FocusedInbox.md) + +### [Get-InboxRule](Get-InboxRule.md) + +### [Get-Mailbox](Get-Mailbox.md) + +### [Get-MailboxAutoReplyConfiguration](Get-MailboxAutoReplyConfiguration.md) + +### [Get-MailboxCalendarFolder](Get-MailboxCalendarFolder.md) + +### [Get-MailboxExportRequest](Get-MailboxExportRequest.md) + +### [Get-MailboxExportRequestStatistics](Get-MailboxExportRequestStatistics.md) + +### [Get-MailboxFolder](Get-MailboxFolder.md) + +### [Get-MailboxFolderPermission](Get-MailboxFolderPermission.md) + +### [Get-MailboxFolderStatistics](Get-MailboxFolderStatistics.md) + +### [Get-MailboxImportRequest](Get-MailboxImportRequest.md) + +### [Get-MailboxImportRequestStatistics](Get-MailboxImportRequestStatistics.md) + +### [Get-MailboxLocation](Get-MailboxLocation.md) + +### [Get-MailboxPermission](Get-MailboxPermission.md) + +### [Get-MailboxPlan](Get-MailboxPlan.md) + +### [Get-MailboxRestoreRequest](Get-MailboxRestoreRequest.md) + +### [Get-MailboxRestoreRequestStatistics](Get-MailboxRestoreRequestStatistics.md) + +### [Get-MailboxSentItemsConfiguration](Get-MailboxSentItemsConfiguration.md) + +### [Get-MailboxStatistics](Get-MailboxStatistics.md) + +### [Get-MailboxUserConfiguration](Get-MailboxUserConfiguration.md) + +### [Get-MessageCategory](Get-MessageCategory.md) + +### [Get-PendingDelicenseUser](Get-PendingDelicenseUser.md) + +### [Get-Place](Get-Place.md) + +### [Get-RecipientPermission](Get-RecipientPermission.md) + +### [Get-RecoverableItems](Get-RecoverableItems.md) + +### [Get-ResourceConfig](Get-ResourceConfig.md) + +### [Get-SweepRule](Get-SweepRule.md) + +### [Get-UserPhoto](Get-UserPhoto.md) + +### [Import-RecipientDataProperty](Import-RecipientDataProperty.md) + +### [New-App](New-App.md) + +### [New-InboxRule](New-InboxRule.md) + +### [New-Mailbox](New-Mailbox.md) + +### [New-MailboxExportRequest](New-MailboxExportRequest.md) + +### [New-MailboxFolder](New-MailboxFolder.md) + +### [New-MailboxImportRequest](New-MailboxImportRequest.md) + +### [New-MailboxRestoreRequest](New-MailboxRestoreRequest.md) + +### [New-MailMessage](New-MailMessage.md) + +### [New-SiteMailbox](New-SiteMailbox.md) + +### [New-SweepRule](New-SweepRule.md) + +### [Remove-App](Remove-App.md) + +### [Remove-CalendarEvents](Remove-CalendarEvents.md) + +### [Remove-InboxRule](Remove-InboxRule.md) + +### [Remove-Mailbox](Remove-Mailbox.md) + +### [Remove-MailboxExportRequest](Remove-MailboxExportRequest.md) + +### [Remove-MailboxFolderPermission](Remove-MailboxFolderPermission.md) + +### [Remove-MailboxImportRequest](Remove-MailboxImportRequest.md) + +### [Remove-MailboxPermission](Remove-MailboxPermission.md) + +### [Remove-MailboxRestoreRequest](Remove-MailboxRestoreRequest.md) + +### [Remove-MailboxUserConfiguration](Remove-MailboxUserConfiguration.md) + +### [Remove-RecipientPermission](Remove-RecipientPermission.md) + +### [Remove-SweepRule](Remove-SweepRule.md) + +### [Remove-UserPhoto](Remove-UserPhoto.md) + +### [Restore-Mailbox](Restore-Mailbox.md) + +### [Restore-RecoverableItems](Restore-RecoverableItems.md) + +### [Resume-MailboxExportRequest](Resume-MailboxExportRequest.md) + +### [Resume-MailboxImportRequest](Resume-MailboxImportRequest.md) + +### [Resume-MailboxRestoreRequest](Resume-MailboxRestoreRequest.md) + +### [Search-Mailbox](Search-Mailbox.md) + +### [Set-App](Set-App.md) + +### [Set-CalendarNotification](Set-CalendarNotification.md) + +### [Set-CalendarProcessing](Set-CalendarProcessing.md) + +### [Set-Clutter](Set-Clutter.md) + +### [Set-EventsFromEmailConfiguration](Set-EventsFromEmailConfiguration.md) + +### [Set-ExternalInOutlook](Set-ExternalInOutlook.md) + +### [Set-FocusedInbox](Set-FocusedInbox.md) + +### [Set-InboxRule](Set-InboxRule.md) + +### [Set-Mailbox](Set-Mailbox.md) + +### [Set-MailboxAutoReplyConfiguration](Set-MailboxAutoReplyConfiguration.md) + +### [Set-MailboxCalendarFolder](Set-MailboxCalendarFolder.md) + +### [Set-MailboxExportRequest](Set-MailboxExportRequest.md) + +### [Set-MailboxFolderPermission](Set-MailboxFolderPermission.md) + +### [Set-MailboxImportRequest](Set-MailboxImportRequest.md) + +### [Set-MailboxPlan](Set-MailboxPlan.md) + +### [Set-MailboxRestoreRequest](Set-MailboxRestoreRequest.md) + +### [Set-MailboxSentItemsConfiguration](Set-MailboxSentItemsConfiguration.md) + +### [Set-Place](Set-Place.md) + +### [Set-ResourceConfig](Set-ResourceConfig.md) + +### [Set-SweepRule](Set-SweepRule.md) + +### [Set-UserPhoto](Set-UserPhoto.md) + +### [Suspend-MailboxExportRequest](Suspend-MailboxExportRequest.md) + +### [Suspend-MailboxImportRequest](Suspend-MailboxImportRequest.md) + +### [Suspend-MailboxRestoreRequest](Suspend-MailboxRestoreRequest.md) + +### [Test-MAPIConnectivity](Test-MAPIConnectivity.md) + +### [Undo-SoftDeletedMailbox](Undo-SoftDeletedMailbox.md) + +## mail-flow Cmdlets +### [Add-ResubmitRequest](Add-ResubmitRequest.md) + +### [Disable-DnssecForVerifiedDomain](Disable-DnssecForVerifiedDomain.md) + +### [Disable-IPv6ForAcceptedDomain](Disable-IPv6ForAcceptedDomain.md) + +### [Disable-SmtpDaneInbound](Disable-SmtpDaneInbound.md) + +### [Disable-TransportAgent](Disable-TransportAgent.md) + +### [Enable-DnssecForVerifiedDomain](Enable-DnssecForVerifiedDomain.md) + +### [Enable-IPv6ForAcceptedDomain](Enable-IPv6ForAcceptedDomain.md) + +### [Enable-SmtpDaneInbound](Enable-SmtpDaneInbound.md) + +### [Enable-TransportAgent](Enable-TransportAgent.md) + +### [Export-Message](Export-Message.md) + +### [Get-AcceptedDomain](Get-AcceptedDomain.md) + +### [Get-AddressRewriteEntry](Get-AddressRewriteEntry.md) + +### [Get-DeliveryAgentConnector](Get-DeliveryAgentConnector.md) + +### [Get-DnssecStatusForVerifiedDomain](Get-DnssecStatusForVerifiedDomain.md) + +### [Get-EdgeSubscription](Get-EdgeSubscription.md) + +### [Get-EdgeSyncServiceConfig](Get-EdgeSyncServiceConfig.md) + +### [Get-ForeignConnector](Get-ForeignConnector.md) + +### [Get-FrontendTransportService](Get-FrontendTransportService.md) + +### [Get-InboundConnector](Get-InboundConnector.md) + +### [Get-IPv6StatusForAcceptedDomain](Get-IPv6StatusForAcceptedDomain.md) + +### [Get-MailboxTransportService](Get-MailboxTransportService.md) + +### [Get-Message](Get-Message.md) + +### [Get-MessageTrace](Get-MessageTrace.md) + +### [Get-MessageTraceDetail](Get-MessageTraceDetail.md) + +### [Get-MessageTrackingLog](Get-MessageTrackingLog.md) + +### [Get-MessageTrackingReport](Get-MessageTrackingReport.md) + +### [Get-NetworkConnectionInfo](Get-NetworkConnectionInfo.md) + +### [Get-OutboundConnector](Get-OutboundConnector.md) + +### [Get-Queue](Get-Queue.md) + +### [Get-QueueDigest](Get-QueueDigest.md) + +### [Get-ReceiveConnector](Get-ReceiveConnector.md) + +### [Get-RemoteDomain](Get-RemoteDomain.md) + +### [Get-ResubmitRequest](Get-ResubmitRequest.md) + +### [Get-RoutingGroupConnector](Get-RoutingGroupConnector.md) + +### [Get-SendConnector](Get-SendConnector.md) + +### [Get-SmtpDaneInboundStatus](Get-SmtpDaneInboundStatus.md) + +### [Get-SystemMessage](Get-SystemMessage.md) + +### [Get-TransportAgent](Get-TransportAgent.md) + +### [Get-TransportConfig](Get-TransportConfig.md) + +### [Get-TransportPipeline](Get-TransportPipeline.md) + +### [Get-TransportServer](Get-TransportServer.md) + +### [Get-TransportService](Get-TransportService.md) + +### [Get-X400AuthoritativeDomain](Get-X400AuthoritativeDomain.md) + +### [Install-TransportAgent](Install-TransportAgent.md) + +### [New-AcceptedDomain](New-AcceptedDomain.md) + +### [New-AddressRewriteEntry](New-AddressRewriteEntry.md) + +### [New-DeliveryAgentConnector](New-DeliveryAgentConnector.md) + +### [New-EdgeSubscription](New-EdgeSubscription.md) + +### [New-EdgeSyncServiceConfig](New-EdgeSyncServiceConfig.md) + +### [New-ForeignConnector](New-ForeignConnector.md) + +### [New-InboundConnector](New-InboundConnector.md) + +### [New-OutboundConnector](New-OutboundConnector.md) + +### [New-ReceiveConnector](New-ReceiveConnector.md) + +### [New-RemoteDomain](New-RemoteDomain.md) + +### [New-RoutingGroupConnector](New-RoutingGroupConnector.md) + +### [New-SendConnector](New-SendConnector.md) + +### [New-SystemMessage](New-SystemMessage.md) + +### [New-X400AuthoritativeDomain](New-X400AuthoritativeDomain.md) + +### [Redirect-Message](Redirect-Message.md) + +### [Remove-AcceptedDomain](Remove-AcceptedDomain.md) + +### [Remove-AddressRewriteEntry](Remove-AddressRewriteEntry.md) + +### [Remove-DeliveryAgentConnector](Remove-DeliveryAgentConnector.md) + +### [Remove-EdgeSubscription](Remove-EdgeSubscription.md) + +### [Remove-ForeignConnector](Remove-ForeignConnector.md) + +### [Remove-InboundConnector](Remove-InboundConnector.md) + +### [Remove-Message](Remove-Message.md) + +### [Remove-OutboundConnector](Remove-OutboundConnector.md) + +### [Remove-ReceiveConnector](Remove-ReceiveConnector.md) + +### [Remove-RemoteDomain](Remove-RemoteDomain.md) + +### [Remove-ResubmitRequest](Remove-ResubmitRequest.md) + +### [Remove-RoutingGroupConnector](Remove-RoutingGroupConnector.md) + +### [Remove-SendConnector](Remove-SendConnector.md) + +### [Remove-SystemMessage](Remove-SystemMessage.md) + +### [Remove-X400AuthoritativeDomain](Remove-X400AuthoritativeDomain.md) + +### [Resume-Message](Resume-Message.md) + +### [Resume-Queue](Resume-Queue.md) + +### [Retry-Queue](Retry-Queue.md) + +### [Search-MessageTrackingReport](Search-MessageTrackingReport.md) + +### [Set-AcceptedDomain](Set-AcceptedDomain.md) + +### [Set-AddressRewriteEntry](Set-AddressRewriteEntry.md) + +### [Set-DeliveryAgentConnector](Set-DeliveryAgentConnector.md) + +### [Set-EdgeSyncServiceConfig](Set-EdgeSyncServiceConfig.md) + +### [Set-ForeignConnector](Set-ForeignConnector.md) + +### [Set-FrontendTransportService](Set-FrontendTransportService.md) + +### [Set-InboundConnector](Set-InboundConnector.md) + +### [Set-MailboxTransportService](Set-MailboxTransportService.md) + +### [Set-OutboundConnector](Set-OutboundConnector.md) + +### [Set-ReceiveConnector](Set-ReceiveConnector.md) + +### [Set-RemoteDomain](Set-RemoteDomain.md) + +### [Set-ResubmitRequest](Set-ResubmitRequest.md) + +### [Set-RoutingGroupConnector](Set-RoutingGroupConnector.md) + +### [Set-SendConnector](Set-SendConnector.md) + +### [Set-SystemMessage](Set-SystemMessage.md) + +### [Set-TransportAgent](Set-TransportAgent.md) + +### [Set-TransportConfig](Set-TransportConfig.md) + +### [Set-TransportServer](Set-TransportServer.md) + +### [Set-TransportService](Set-TransportService.md) + +### [Set-X400AuthoritativeDomain](Set-X400AuthoritativeDomain.md) + +### [Start-EdgeSynchronization](Start-EdgeSynchronization.md) + +### [Start-HistoricalSearch](Start-HistoricalSearch.md) + +### [Stop-HistoricalSearch](Stop-HistoricalSearch.md) + +### [Suspend-Message](Suspend-Message.md) + +### [Suspend-Queue](Suspend-Queue.md) + +### [Test-EdgeSynchronization](Test-EdgeSynchronization.md) + +### [Test-Mailflow](Test-Mailflow.md) + +### [Test-SmtpConnectivity](Test-SmtpConnectivity.md) + +### [Uninstall-TransportAgent](Uninstall-TransportAgent.md) + +### [Validate-OutboundConnector](Validate-OutboundConnector.md) + +## move-and-migration Cmdlets +### [Complete-MigrationBatch](Complete-MigrationBatch.md) + +### [Export-MigrationReport](Export-MigrationReport.md) + +### [Get-MigrationBatch](Get-MigrationBatch.md) + +### [Get-MigrationConfig](Get-MigrationConfig.md) + +### [Get-MigrationEndpoint](Get-MigrationEndpoint.md) + +### [Get-MigrationStatistics](Get-MigrationStatistics.md) + +### [Get-MigrationUser](Get-MigrationUser.md) + +### [Get-MigrationUserStatistics](Get-MigrationUserStatistics.md) + +### [Get-MoveRequest](Get-MoveRequest.md) + +### [Get-MoveRequestStatistics](Get-MoveRequestStatistics.md) + +### [Get-PublicFolderMailboxMigrationRequest](Get-PublicFolderMailboxMigrationRequest.md) + +### [Get-PublicFolderMailboxMigrationRequestStatistics](Get-PublicFolderMailboxMigrationRequestStatistics.md) + +### [Get-PublicFolderMigrationRequest](Get-PublicFolderMigrationRequest.md) + +### [Get-PublicFolderMigrationRequestStatistics](Get-PublicFolderMigrationRequestStatistics.md) + +### [Get-PublicFolderMoveRequest](Get-PublicFolderMoveRequest.md) + +### [Get-PublicFolderMoveRequestStatistics](Get-PublicFolderMoveRequestStatistics.md) + +### [New-MigrationBatch](New-MigrationBatch.md) + +### [New-MigrationEndpoint](New-MigrationEndpoint.md) + +### [New-MoveRequest](New-MoveRequest.md) + +### [New-PublicFolderMigrationRequest](New-PublicFolderMigrationRequest.md) + +### [New-PublicFolderMoveRequest](New-PublicFolderMoveRequest.md) + +### [Remove-MigrationBatch](Remove-MigrationBatch.md) + +### [Remove-MigrationEndpoint](Remove-MigrationEndpoint.md) + +### [Remove-MigrationUser](Remove-MigrationUser.md) + +### [Remove-MoveRequest](Remove-MoveRequest.md) + +### [Remove-PublicFolderMailboxMigrationRequest](Remove-PublicFolderMailboxMigrationRequest.md) + +### [Remove-PublicFolderMigrationRequest](Remove-PublicFolderMigrationRequest.md) + +### [Remove-PublicFolderMoveRequest](Remove-PublicFolderMoveRequest.md) + +### [Resume-MoveRequest](Resume-MoveRequest.md) + +### [Resume-PublicFolderMigrationRequest](Resume-PublicFolderMigrationRequest.md) + +### [Resume-PublicFolderMoveRequest](Resume-PublicFolderMoveRequest.md) + +### [Set-MigrationBatch](Set-MigrationBatch.md) + +### [Set-MigrationConfig](Set-MigrationConfig.md) + +### [Set-MigrationEndpoint](Set-MigrationEndpoint.md) + +### [Set-MigrationUser](Set-MigrationUser.md) + +### [Set-MoveRequest](Set-MoveRequest.md) + +### [Set-PublicFolderMigrationRequest](Set-PublicFolderMigrationRequest.md) + +### [Set-PublicFolderMoveRequest](Set-PublicFolderMoveRequest.md) + +### [Start-MigrationBatch](Start-MigrationBatch.md) + +### [Start-MigrationUser](Start-MigrationUser.md) + +### [Stop-MigrationBatch](Stop-MigrationBatch.md) + +### [Stop-MigrationUser](Stop-MigrationUser.md) + +### [Suspend-MoveRequest](Suspend-MoveRequest.md) + +### [Suspend-PublicFolderMailboxMigrationRequest](Suspend-PublicFolderMailboxMigrationRequest.md) + +### [Suspend-PublicFolderMigrationRequest](Suspend-PublicFolderMigrationRequest.md) + +### [Suspend-PublicFolderMoveRequest](Suspend-PublicFolderMoveRequest.md) + +### [Test-MigrationServerAvailability](Test-MigrationServerAvailability.md) + +## organization Cmdlets +### [Disable-CmdletExtensionAgent](Disable-CmdletExtensionAgent.md) + +### [Enable-CmdletExtensionAgent](Enable-CmdletExtensionAgent.md) + +### [Enable-OrganizationCustomization](Enable-OrganizationCustomization.md) + +### [Get-AccessToCustomerDataRequest](Get-AccessToCustomerDataRequest.md) + +### [Get-ApplicationAccessPolicy](Get-ApplicationAccessPolicy.md) + +### [Get-AuthConfig](Get-AuthConfig.md) + +### [Get-AuthenticationPolicy](Get-AuthenticationPolicy.md) + +### [Get-AuthServer](Get-AuthServer.md) + +### [Get-CmdletExtensionAgent](Get-CmdletExtensionAgent.md) + +### [Get-ExchangeAssistanceConfig](Get-ExchangeAssistanceConfig.md) + +### [Get-ExchangeDiagnosticInfo](Get-ExchangeDiagnosticInfo.md) + +### [Get-ExchangeServer](Get-ExchangeServer.md) + +### [Get-ExchangeServerAccessLicense](Get-ExchangeServerAccessLicense.md) + +### [Get-ExchangeServerAccessLicenseUser](Get-ExchangeServerAccessLicenseUser.md) + +### [Get-ExchangeFeature](Get-ExchangeFeature.md) + +### [Get-ExchangeSettings](Get-ExchangeSettings.md) + +### [Get-FeatureConfiguration](Get-FeatureConfiguration.md) + +### [Get-Notification](Get-Notification.md) + +### [Get-OrganizationConfig](Get-OrganizationConfig.md) + +### [Get-PartnerApplication](Get-PartnerApplication.md) + +### [Get-PerimeterConfig](Get-PerimeterConfig.md) + +### [Get-ServicePrincipal](Get-ServicePrincipal.md) + +### [Get-SettingOverride](Get-SettingOverride.md) + +### [New-ApplicationAccessPolicy](New-ApplicationAccessPolicy.md) + +### [New-AuthenticationPolicy](New-AuthenticationPolicy.md) + +### [New-AuthServer](New-AuthServer.md) + +### [New-ExchangeSettings](New-ExchangeSettings.md) + +### [New-FeatureConfiguration](New-FeatureConfiguration.md) + +### [New-PartnerApplication](New-PartnerApplication.md) + +### [New-ServicePrincipal](New-ServicePrincipal.md) + +### [New-SettingOverride](New-SettingOverride.md) + +### [Remove-ApplicationAccessPolicy](Remove-ApplicationAccessPolicy.md) + +### [Remove-AuthenticationPolicy](Remove-AuthenticationPolicy.md) + +### [Remove-AuthServer](Remove-AuthServer.md) + +### [Remove-FeatureConfiguration](Remove-FeatureConfiguration.md) + +### [Remove-PartnerApplication](Remove-PartnerApplication.md) + +### [Remove-ServicePrincipal](Remove-ServicePrincipal.md) + +### [Remove-SettingOverride](Remove-SettingOverride.md) + +### [Set-AccessToCustomerDataRequest](Set-AccessToCustomerDataRequest.md) + +### [Set-ApplicationAccessPolicy](Set-ApplicationAccessPolicy.md) + +### [Set-AuthConfig](Set-AuthConfig.md) + +### [Set-AuthenticationPolicy](Set-AuthenticationPolicy.md) + +### [Set-AuthServer](Set-AuthServer.md) + +### [Set-CmdletExtensionAgent](Set-CmdletExtensionAgent.md) + +### [Set-ExchangeAssistanceConfig](Set-ExchangeAssistanceConfig.md) + +### [Set-ExchangeFeature](Set-ExchangeFeature.md) + +### [Set-ExchangeServer](Set-ExchangeServer.md) + +### [Set-ExchangeSettings](Set-ExchangeSettings.md) + +### [Set-FeatureConfiguration](Set-FeatureConfiguration.md) + +### [Set-Notification](Set-Notification.md) + +### [Set-OrganizationConfig](Set-OrganizationConfig.md) + +### [Set-PartnerApplication](Set-PartnerApplication.md) + +### [Set-PerimeterConfig](Set-PerimeterConfig.md) + +### [Set-ServicePrincipal](Set-ServicePrincipal.md) + +### [Set-SettingOverride](Set-SettingOverride.md) + +### [Test-ApplicationAccessPolicy](Test-ApplicationAccessPolicy.md) + +### [Test-OAuthConnectivity](Test-OAuthConnectivity.md) + +### [Test-ServicePrincipalAuthorization](Test-ServicePrincipalAuthorization.md) + +### [Test-SystemHealth](Test-SystemHealth.md) + +### [Update-ExchangeHelp](Update-ExchangeHelp.md) + +## policy-and-compliance Cmdlets +### [Disable-JournalArchiving](Disable-JournalArchiving.md) + +### [Disable-JournalRule](Disable-JournalRule.md) + +### [Disable-OutlookProtectionRule](Disable-OutlookProtectionRule.md) + +### [Disable-TransportRule](Disable-TransportRule.md) + +### [Enable-JournalRule](Enable-JournalRule.md) + +### [Enable-OutlookProtectionRule](Enable-OutlookProtectionRule.md) + +### [Enable-TransportRule](Enable-TransportRule.md) + +### [Execute-AzureADLabelSync](Execute-AzureADLabelSync.md) + +### [Export-JournalRuleCollection](Export-JournalRuleCollection.md) + +### [Export-TransportRuleCollection](Export-TransportRuleCollection.md) + +### [Get-AdministrativeUnit](Get-AdministrativeUnit.md) + +### [Get-AutoSensitivityLabelPolicy](Get-AutoSensitivityLabelPolicy.md) + +### [Get-AutoSensitivityLabelRule](Get-AutoSensitivityLabelRule.md) + +### [Get-EtrLimits](Get-EtrLimits.md) + +### [Get-ExoInformationBarrierPolicy](Get-ExoInformationBarrierPolicy.md) + +### [Get-ExoInformationBarrierSegment](Get-ExoInformationBarrierSegment.md) + +### [Get-ExoInformationBarrierRelationship](Get-ExoInformationBarrierRelationship.md) + +### [Get-InformationBarrierPoliciesApplicationStatus](Get-InformationBarrierPoliciesApplicationStatus.md) + +### [Get-InformationBarrierPolicy](Get-InformationBarrierPolicy.md) + +### [Get-InformationBarrierRecipientStatus](Get-InformationBarrierRecipientStatus.md) + +### [Get-JournalRule](Get-JournalRule.md) + +### [Get-Label](Get-Label.md) + +### [Get-LabelPolicy](Get-LabelPolicy.md) + +### [Get-MessageClassification](Get-MessageClassification.md) + +### [Get-OrganizationSegment](Get-OrganizationSegment.md) + +### [Get-OutlookProtectionRule](Get-OutlookProtectionRule.md) + +### [Get-ProtectionAlert](Get-ProtectionAlert.md) + +### [Get-ReviewItems](Get-ReviewItems.md) + +### [Get-SupervisoryReviewPolicyV2](Get-SupervisoryReviewPolicyV2.md) + +### [Get-SupervisoryReviewRule](Get-SupervisoryReviewRule.md) + +### [Get-TransportRule](Get-TransportRule.md) + +### [Get-TransportRuleAction](Get-TransportRuleAction.md) + +### [Get-TransportRulePredicate](Get-TransportRulePredicate.md) + +### [Import-JournalRuleCollection](Import-JournalRuleCollection.md) + +### [Import-TransportRuleCollection](Import-TransportRuleCollection.md) + +### [Install-UnifiedCompliancePrerequisite](Install-UnifiedCompliancePrerequisite.md) + +### [Invoke-ComplianceSecurityFilterAction](Invoke-ComplianceSecurityFilterAction.md) + +### [New-AutoSensitivityLabelPolicy](New-AutoSensitivityLabelPolicy.md) + +### [New-AutoSensitivityLabelRule](New-AutoSensitivityLabelRule.md) + +### [New-InformationBarrierPolicy](New-InformationBarrierPolicy.md) + +### [New-JournalRule](New-JournalRule.md) + +### [New-Label](New-Label.md) + +### [New-LabelPolicy](New-LabelPolicy.md) + +### [New-MessageClassification](New-MessageClassification.md) + +### [New-OrganizationSegment](New-OrganizationSegment.md) + +### [New-OutlookProtectionRule](New-OutlookProtectionRule.md) + +### [New-ProtectionAlert](New-ProtectionAlert.md) + +### [New-SupervisoryReviewPolicyV2](New-SupervisoryReviewPolicyV2.md) + +### [New-SupervisoryReviewRule](New-SupervisoryReviewRule.md) + +### [New-TransportRule](New-TransportRule.md) + +### [Remove-AutoSensitivityLabelPolicy](Remove-AutoSensitivityLabelPolicy.md) + +### [Remove-AutoSensitivityLabelRule](Remove-AutoSensitivityLabelRule.md) + +### [Remove-InformationBarrierPolicy](Remove-InformationBarrierPolicy.md) + +### [Remove-JournalRule](Remove-JournalRule.md) + +### [Remove-Label](Remove-Label.md) + +### [Remove-LabelPolicy](Remove-LabelPolicy.md) + +### [Remove-MessageClassification](Remove-MessageClassification.md) + +### [Remove-OrganizationSegment](Remove-OrganizationSegment.md) + +### [Remove-OutlookProtectionRule](Remove-OutlookProtectionRule.md) + +### [Remove-ProtectionAlert](Remove-ProtectionAlert.md) + +### [Remove-SupervisoryReviewPolicyV2](Remove-SupervisoryReviewPolicyV2.md) + +### [Remove-TransportRule](Remove-TransportRule.md) + +### [Set-AutoSensitivityLabelPolicy](Set-AutoSensitivityLabelPolicy.md) + +### [Set-AutoSensitivityLabelRule](Set-AutoSensitivityLabelRule.md) + +### [Set-InformationBarrierPolicy](Set-InformationBarrierPolicy.md) + +### [Set-JournalRule](Set-JournalRule.md) + +### [Set-Label](Set-Label.md) + +### [Set-LabelPolicy](Set-LabelPolicy.md) + +### [Set-MessageClassification](Set-MessageClassification.md) + +### [Set-OrganizationSegment](Set-OrganizationSegment.md) + +### [Set-OutlookProtectionRule](Set-OutlookProtectionRule.md) + +### [Set-ProtectionAlert](Set-ProtectionAlert.md) + +### [Set-SupervisoryReviewPolicyV2](Set-SupervisoryReviewPolicyV2.md) + +### [Set-SupervisoryReviewRule](Set-SupervisoryReviewRule.md) + +### [Set-TransportRule](Set-TransportRule.md) + +### [Start-InformationBarrierPoliciesApplication](Start-InformationBarrierPoliciesApplication.md) + +### [Stop-InformationBarrierPoliciesApplication](Stop-InformationBarrierPoliciesApplication.md) + +### [Test-ArchiveConnectivity](Test-ArchiveConnectivity.md) + +## policy-and-compliance-audit Cmdlets +### [Get-AdminAuditLogConfig](Get-AdminAuditLogConfig.md) + +### [Get-AuditConfig](Get-AuditConfig.md) + +### [Get-AuditLogSearch](Get-AuditLogSearch.md) + +### [Get-MailboxAuditBypassAssociation](Get-MailboxAuditBypassAssociation.md) + +### [Get-UnifiedAuditLogRetentionPolicy](Get-UnifiedAuditLogRetentionPolicy.md) + +### [New-AdminAuditLogSearch](New-AdminAuditLogSearch.md) + +### [New-MailboxAuditLogSearch](New-MailboxAuditLogSearch.md) + +### [New-UnifiedAuditLogRetentionPolicy](New-UnifiedAuditLogRetentionPolicy.md) + +### [Remove-UnifiedAuditLogRetentionPolicy](Remove-UnifiedAuditLogRetentionPolicy.md) + +### [Search-AdminAuditLog](Search-AdminAuditLog.md) + +### [Search-MailboxAuditLog](Search-MailboxAuditLog.md) + +### [Search-UnifiedAuditLog](Search-UnifiedAuditLog.md) + +### [Set-AdminAuditLogConfig](Set-AdminAuditLogConfig.md) + +### [Set-AuditConfig](Set-AuditConfig.md) + +### [Set-MailboxAuditBypassAssociation](Set-MailboxAuditBypassAssociation.md) + +### [Set-UnifiedAuditLogRetentionPolicy](Set-UnifiedAuditLogRetentionPolicy.md) + +### [Write-AdminAuditLog](Write-AdminAuditLog.md) + +## policy-and-compliance-content-search Cmdlets +### [Get-ComplianceSearch](Get-ComplianceSearch.md) + +### [Get-ComplianceSearchAction](Get-ComplianceSearchAction.md) + +### [Get-ComplianceSecurityFilter](Get-ComplianceSecurityFilter.md) + +### [Get-MailboxSearch](Get-MailboxSearch.md) + +### [Invoke-ComplianceSearchActionStep](Invoke-ComplianceSearchActionStep.md) + +### [New-ComplianceSearch](New-ComplianceSearch.md) + +### [New-ComplianceSearchAction](New-ComplianceSearchAction.md) + +### [New-ComplianceSecurityFilter](New-ComplianceSecurityFilter.md) + +### [New-MailboxSearch](New-MailboxSearch.md) + +### [Remove-ComplianceSearch](Remove-ComplianceSearch.md) + +### [Remove-ComplianceSearchAction](Remove-ComplianceSearchAction.md) + +### [Remove-ComplianceSecurityFilter](Remove-ComplianceSecurityFilter.md) + +### [Remove-MailboxSearch](Remove-MailboxSearch.md) + +### [Set-ComplianceSearch](Set-ComplianceSearch.md) + +### [Set-ComplianceSearchAction](Set-ComplianceSearchAction.md) + +### [Set-ComplianceSecurityFilter](Set-ComplianceSecurityFilter.md) + +### [Set-MailboxSearch](Set-MailboxSearch.md) + +### [Start-ComplianceSearch](Start-ComplianceSearch.md) + +### [Start-MailboxSearch](Start-MailboxSearch.md) + +### [Stop-ComplianceSearch](Stop-ComplianceSearch.md) + +### [Stop-MailboxSearch](Stop-MailboxSearch.md) + +## policy-and-compliance-dlp Cmdlets +### [Export-ActivityExplorerData](Export-ActivityExplorerData.md) + +### [Export-DlpPolicyCollection](Export-DlpPolicyCollection.md) + +### [Get-ClassificationRuleCollection](Get-ClassificationRuleCollection.md) + +### [Get-DataClassification](Get-DataClassification.md) + +### [Get-DataClassificationConfig](Get-DataClassificationConfig.md) + +### [Get-DlpCompliancePolicy](Get-DlpCompliancePolicy.md) + +### [Get-DlpComplianceRule](Get-DlpComplianceRule.md) + +### [Get-DlpDetailReport](Get-DlpDetailReport.md) + +### [Get-DlpDetectionsReport](Get-DlpDetectionsReport.md) + +### [Get-DlpEdmSchema](Get-DlpEdmSchema.md) + +### [Get-DlpIncidentDetailReport](Get-DlpIncidentDetailReport.md) + +### [Get-DlpKeywordDictionary](Get-DlpKeywordDictionary.md) + +### [Get-DlpPolicy](Get-DlpPolicy.md) + +### [Get-DlpPolicyTemplate](Get-DlpPolicyTemplate.md) + +### [Get-DlpSensitiveInformationType](Get-DlpSensitiveInformationType.md) + +### [Get-DlpSensitiveInformationTypeRulePackage](Get-DlpSensitiveInformationTypeRulePackage.md) + +### [Get-DlpSiDetectionsReport](Get-DlpSiDetectionsReport.md) + +### [Get-PolicyConfig](Get-PolicyConfig.md) + +### [Get-PolicyTipConfig](Get-PolicyTipConfig.md) + +### [Import-DlpPolicyCollection](Import-DlpPolicyCollection.md) + +### [Import-DlpPolicyTemplate](Import-DlpPolicyTemplate.md) + +### [New-ClassificationRuleCollection](New-ClassificationRuleCollection.md) + +### [New-DataClassification](New-DataClassification.md) + +### [New-DlpCompliancePolicy](New-DlpCompliancePolicy.md) + +### [New-DlpComplianceRule](New-DlpComplianceRule.md) + +### [New-DlpEdmSchema](New-DlpEdmSchema.md) + +### [New-DlpFingerprint](New-DlpFingerprint.md) + +### [New-DlpKeywordDictionary](New-DlpKeywordDictionary.md) + +### [New-DlpPolicy](New-DlpPolicy.md) + +### [New-DlpSensitiveInformationType](New-DlpSensitiveInformationType.md) + +### [New-DlpSensitiveInformationTypeRulePackage](New-DlpSensitiveInformationTypeRulePackage.md) + +### [New-Fingerprint](New-Fingerprint.md) + +### [New-PolicyTipConfig](New-PolicyTipConfig.md) + +### [Remove-ClassificationRuleCollection](Remove-ClassificationRuleCollection.md) + +### [Remove-DataClassification](Remove-DataClassification.md) + +### [Remove-DlpCompliancePolicy](Remove-DlpCompliancePolicy.md) + +### [Remove-DlpComplianceRule](Remove-DlpComplianceRule.md) + +### [Remove-DlpEdmSchema](Remove-DlpEdmSchema.md) + +### [Remove-DlpKeywordDictionary](Remove-DlpKeywordDictionary.md) + +### [Remove-DlpPolicy](Remove-DlpPolicy.md) + +### [Remove-DlpPolicyTemplate](Remove-DlpPolicyTemplate.md) + +### [Remove-DlpSensitiveInformationType](Remove-DlpSensitiveInformationType.md) + +### [Remove-DlpSensitiveInformationTypeRulePackage](Remove-DlpSensitiveInformationTypeRulePackage.md) + +### [Remove-PolicyTipConfig](Remove-PolicyTipConfig.md) + +### [Set-ClassificationRuleCollection](Set-ClassificationRuleCollection.md) + +### [Set-DataClassification](Set-DataClassification.md) + +### [Set-DlpCompliancePolicy](Set-DlpCompliancePolicy.md) + +### [Set-DlpComplianceRule](Set-DlpComplianceRule.md) + +### [Set-DlpEdmSchema](Set-DlpEdmSchema.md) + +### [Set-DlpKeywordDictionary](Set-DlpKeywordDictionary.md) + +### [Set-DlpPolicy](Set-DlpPolicy.md) + +### [Set-DlpSensitiveInformationType](Set-DlpSensitiveInformationType.md) + +### [Set-DlpSensitiveInformationTypeRulePackage](Set-DlpSensitiveInformationTypeRulePackage.md) + +### [Set-PolicyConfig](Set-PolicyConfig.md) + +### [Set-PolicyTipConfig](Set-PolicyTipConfig.md) + +### [Test-DataClassification](Test-DataClassification.md) + +### [Test-TextExtraction](Test-TextExtraction.md) + +## policy-and-compliance-ediscovery Cmdlets +### [Add-ComplianceCaseMember](Add-ComplianceCaseMember.md) + +### [Add-eDiscoveryCaseAdmin](Add-eDiscoveryCaseAdmin.md) + +### [Get-CaseHoldPolicy](Get-CaseHoldPolicy.md) + +### [Get-CaseHoldRule](Get-CaseHoldRule.md) + +### [Get-ComplianceCase](Get-ComplianceCase.md) + +### [Get-ComplianceCaseMember](Get-ComplianceCaseMember.md) + +### [Get-eDiscoveryCaseAdmin](Get-eDiscoveryCaseAdmin.md) + +### [New-CaseHoldPolicy](New-CaseHoldPolicy.md) + +### [New-CaseHoldRule](New-CaseHoldRule.md) + +### [New-ComplianceCase](New-ComplianceCase.md) + +### [Remove-CaseHoldPolicy](Remove-CaseHoldPolicy.md) + +### [Remove-CaseHoldRule](Remove-CaseHoldRule.md) + +### [Remove-ComplianceCase](Remove-ComplianceCase.md) + +### [Remove-ComplianceCaseMember](Remove-ComplianceCaseMember.md) + +### [Remove-eDiscoveryCaseAdmin](Remove-eDiscoveryCaseAdmin.md) + +### [Set-CaseHoldPolicy](Set-CaseHoldPolicy.md) + +### [Set-CaseHoldRule](Set-CaseHoldRule.md) + +### [Set-ComplianceCase](Set-ComplianceCase.md) + +### [Update-ComplianceCaseMember](Update-ComplianceCaseMember.md) + +### [Update-eDiscoveryCaseAdmin](Update-eDiscoveryCaseAdmin.md) + +## policy-and-compliance-retention Cmdlets +### [Enable-ComplianceTagStorage](Enable-ComplianceTagStorage.md) + +### [Export-ContentExplorerData](Export-ContentExplorerData.md) + +### [Export-FilePlanProperty](Export-FilePlanProperty.md) + +### [Get-AdaptiveScope](Get-AdaptiveScope.md) + +### [Get-AppRetentionCompliancePolicy](Get-AppRetentionCompliancePolicy.md) + +### [Get-AppRetentionComplianceRule](Get-AppRetentionComplianceRule.md) + +### [Get-ComplianceRetentionEvent](Get-ComplianceRetentionEvent.md) + +### [Get-ComplianceRetentionEventType](Get-ComplianceRetentionEventType.md) + +### [Get-ComplianceTag](Get-ComplianceTag.md) + +### [Get-ComplianceTagStorage](Get-ComplianceTagStorage.md) + +### [Get-DataRetentionReport](Get-DataRetentionReport.md) + +### [Get-FilePlanPropertyAuthority](Get-FilePlanPropertyAuthority.md) + +### [Get-FilePlanPropertyCategory](Get-FilePlanPropertyCategory.md) + +### [Get-FilePlanPropertyCitation](Get-FilePlanPropertyCitation.md) + +### [Get-FilePlanPropertyDepartment](Get-FilePlanPropertyDepartment.md) + +### [Get-FilePlanPropertyReferenceId](Get-FilePlanPropertyReferenceId.md) + +### [Get-FilePlanPropertyStructure](Get-FilePlanPropertyStructur.md) + +### [Get-FilePlanPropertySubCategory](Get-FilePlanPropertySubCategory.md) + +### [Get-HoldCompliancePolicy](Get-HoldCompliancePolicy.md) + +### [Get-HoldComplianceRule](Get-HoldComplianceRule.md) + +### [Get-ManagedContentSettings](Get-ManagedContentSettings.md) + +### [Get-ManagedFolder](Get-ManagedFolder.md) + +### [Get-ManagedFolderMailboxPolicy](Get-ManagedFolderMailboxPolicy.md) + +### [Get-RecordReviewNotificationTemplateConfig](Get-RecordReviewNotificationTemplateConfig.md) + +### [Get-RegulatoryComplianceUI](Get-RegulatoryComplianceUI.md) + +### [Get-RetentionCompliancePolicy](Get-RetentionCompliancePolicy.md) + +### [Get-RetentionComplianceRule](Get-RetentionComplianceRule.md) + +### [Get-RetentionEvent](Get-RetentionEvent.md) + +### [Get-RetentionPolicy](Get-RetentionPolicy.md) + +### [Get-RetentionPolicyTag](Get-RetentionPolicyTag.md) + +### [Import-FilePlanProperty](Import-FilePlanProperty.md) + +### [Invoke-HoldRemovalAction](Invoke-HoldRemovalAction.md) + +### [New-AdaptiveScope](New-AdaptiveScope.md) + +### [New-AppRetentionCompliancePolicy](New-AppRetentionCompliancePolicy.md) + +### [New-AppRetentionComplianceRule](New-AppRetentionComplianceRule.md) + +### [New-ComplianceRetentionEvent](New-ComplianceRetentionEvent.md) + +### [New-ComplianceRetentionEventType](New-ComplianceRetentionEventType.md) + +### [New-ComplianceTag](New-ComplianceTag.md) + +### [New-FilePlanPropertyAuthority](New-FilePlanPropertyAuthority.md) + +### [New-FilePlanPropertyCategory](New-FilePlanPropertyCategory.md) + +### [New-FilePlanPropertyCitation](New-FilePlanPropertyCitation.md) + +### [New-FilePlanPropertyDepartment](New-FilePlanPropertyDepartment.md) + +### [New-FilePlanPropertyReferenceId](New-FilePlanPropertyReferenceId.md) + +### [New-FilePlanPropertySubCategory](New-FilePlanPropertySubCategory.md) + +### [New-HoldCompliancePolicy](New-HoldCompliancePolicy.md) + +### [New-HoldComplianceRule](New-HoldComplianceRule.md) + +### [New-ManagedContentSettings](New-ManagedContentSettings.md) + +### [New-ManagedFolder](New-ManagedFolder.md) + +### [New-ManagedFolderMailboxPolicy](New-ManagedFolderMailboxPolicy.md) + +### [New-RetentionCompliancePolicy](New-RetentionCompliancePolicy.md) + +### [New-RetentionComplianceRule](New-RetentionComplianceRule.md) + +### [New-RetentionPolicy](New-RetentionPolicy.md) + +### [New-RetentionPolicyTag](New-RetentionPolicyTag.md) + +### [Remove-AdaptiveScope](Remove-AdaptiveScope.md) + +### [Remove-AppRetentionCompliancePolicy](Remove-AppRetentionCompliancePolicy.md) + +### [Remove-AppRetentionComplianceRule](Remove-AppRetentionComplianceRule.md) + +### [Remove-ComplianceRetentionEventType](Remove-ComplianceRetentionEventType.md) + +### [Remove-ComplianceTag](Remove-ComplianceTag.md) + +### [Remove-FilePlanPropertyAuthority](Remove-FilePlanPropertyAuthority.md) + +### [Remove-FilePlanPropertyCategory](Remove-FilePlanPropertyCategory.md) + +### [Remove-FilePlanPropertyCitation](Remove-FilePlanPropertyCitation.md) + +### [Remove-FilePlanPropertyDepartment](Remove-FilePlanPropertyDepartment.md) + +### [Remove-FilePlanPropertyReferenceId](Remove-FilePlanPropertyReferenceId.md) + +### [Remove-FilePlanPropertySubCategory](Remove-FilePlanPropertySubCategor.md) + +### [Remove-HoldCompliancePolicy](Remove-HoldCompliancePolicy.md) + +### [Remove-HoldComplianceRule](Remove-HoldComplianceRule.md) + +### [Remove-ManagedContentSettings](Remove-ManagedContentSettings.md) + +### [Remove-ManagedFolder](Remove-ManagedFolder.md) + +### [Remove-ManagedFolderMailboxPolicy](Remove-ManagedFolderMailboxPolicy.md) + +### [Remove-RetentionCompliancePolicy](Remove-RetentionCompliancePolicy.md) + +### [Remove-RetentionComplianceRule](Remove-RetentionComplianceRule.md) + +### [Remove-RetentionPolicy](Remove-RetentionPolicy.md) + +### [Remove-RetentionPolicyTag](Remove-RetentionPolicyTag.md) + +### [Set-AdaptiveScope](Set-AdaptiveScope.md) + +### [Set-AppRetentionCompliancePolicy](Set-AppRetentionCompliancePolicy.md) + +### [Set-AppRetentionComplianceRule](Set-AppRetentionComplianceRule.md) + +### [Set-ComplianceRetentionEventType](Set-ComplianceRetentionEventType.md) + +### [Set-ComplianceTag](Set-ComplianceTag.md) + +### [Set-FilePlanPropertyAuthority](Set-FilePlanPropertyAuthorit.md) + +### [Set-FilePlanPropertyCategory](Set-FilePlanPropertyCategory.md) + +### [Set-FilePlanPropertyCitation](Set-FilePlanPropertyCitation.md) + +### [Set-FilePlanPropertyDepartment](Set-FilePlanPropertyDepartment.md) + +### [Set-FilePlanPropertyReferenceId](Set-FilePlanPropertyReferenceId.md) + +### [Set-FilePlanPropertySubCategory](Set-FilePlanPropertySubCategory.md) + +### [Set-HoldCompliancePolicy](Set-HoldCompliancePolicy.md) + +### [Set-HoldComplianceRule](Set-HoldComplianceRule.md) + +### [Set-ManagedContentSettings](Set-ManagedContentSettings.md) + +### [Set-ManagedFolder](Set-ManagedFolder.md) + +### [Set-ManagedFolderMailboxPolicy](Set-ManagedFolderMailboxPolicy.md) + +### [Set-RecordReviewNotificationTemplateConfig](Set-RecordReviewNotificationTemplateConfig.md) + +### [Set-RegulatoryComplianceUI](Set-RegulatoryComplianceUI.md) + +### [Set-RetentionCompliancePolicy](Set-RetentionCompliancePolicy.md) + +### [Set-RetentionComplianceRule](Set-RetentionComplianceRule.md) + +### [Set-RetentionPolicy](Set-RetentionPolicy.md) + +### [Set-RetentionPolicyTag](Set-RetentionPolicyTag.md) + +### [Start-ManagedFolderAssistant](Start-ManagedFolderAssistant.md) + +### [Start-RetentionAutoTagLearning](Start-RetentionAutoTagLearning.md) + +### [Stop-ManagedFolderAssistant](Stop-ManagedFolderAssistant.md) + +### [Validate-RetentionRuleQuery](Validate-RetentionRuleQuery.md) + +## powershell-v3-module Cmdlets +### [Add-VivaModuleFeaturePolicy](Add-VivaModuleFeaturePolicy.md) + +### [Add-VivaOrgInsightsDelegatedRole](Add-VivaOrgInsightsDelegatedRole.md) + +### [Connect-ExchangeOnline](Connect-ExchangeOnline.md) + +### [Connect-IPPSSession](Connect-IPPSSession.md) -Exchange PowerShell is built on Windows PowerShell technology and provides a powerful command-line interface that enables automation of administrative tasks. The following PowerShell environments are available in Exchange: +### [Disconnect-ExchangeOnline](Disconnect-ExchangeOnline.md) + +### [Get-ConnectionInformation](Get-ConnectionInformation.md) + +### [Get-DefaultTenantBriefingConfig](Get-DefaultTenantBriefingConfig.md) + +### [Get-DefaultTenantMyAnalyticsFeatureConfig](Get-DefaultTenantMyAnalyticsFeatureConfig.md) + +### [Get-EXOCasMailbox](Get-EXOCasMailbox.md) + +### [Get-EXOMailbox](Get-EXOMailbox.md) + +### [Get-EXOMailboxFolderPermission](Get-EXOMailboxFolderPermission.md) + +### [Get-EXOMailboxFolderStatistics](Get-EXOMailboxFolderStatistics.md) + +### [Get-EXOMailboxPermission](Get-EXOMailboxPermission.md) + +### [Get-EXOMailboxStatistics](Get-EXOMailboxStatistics.md) + +### [Get-EXOMobileDeviceStatistics](Get-EXOMobileDeviceStatistics.md) + +### [Get-EXORecipient](Get-EXORecipient.md) + +### [Get-EXORecipientPermission](Get-EXORecipientPermission.md) + +### [Get-MyAnalyticsFeatureConfig](Get-MyAnalyticsFeatureConfig.md) + +### [Get-UserBriefingConfig](Get-UserBriefingConfig.md) + +### [Get-VivaInsightsSettings](Get-VivaInsightsSettings.md) + +### [Get-VivaModuleFeature](Get-VivaModuleFeature.md) + +### [Get-VivaModuleFeatureEnablement](Get-VivaModuleFeatureEnablement.md) + +### [Get-VivaModuleFeaturePolicy](Get-VivaModuleFeaturePolicy.md) + +### [Get-VivaOrgInsightsDelegatedRole](Get-VivaOrgInsightsDelegatedRole.md) + +### [Remove-VivaModuleFeaturePolicy](Remove-VivaModuleFeaturePolicy.md) + +### [Remove-VivaOrgInsightsDelegatedRole](Remove-VivaOrgInsightsDelegatedRole.md) + +### [Set-DefaultTenantBriefingConfig](Set-DefaultTenantBriefingConfig.md) + +### [Set-DefaultTenantMyAnalyticsFeatureConfig](Set-DefaultTenantMyAnalyticsFeatureConfig.md) + +### [Set-MyAnalyticsFeatureConfig](Set-MyAnalyticsFeatureConfig.md) + +### [Set-UserBriefingConfig](Set-UserBriefingConfig.md) + +### [Set-VivaInsightsSettings](Set-VivaInsightsSettings.md) + +### [Update-VivaModuleFeaturePolicy](Update-VivaModuleFeaturePolicy.md) + +## reporting Cmdlets +### [Get-CompromisedUserAggregateReport](Get-CompromisedUserAggregateReport.md) + +### [Get-CompromisedUserDetailReport](Get-CompromisedUserDetailReport.md) + +### [Get-HistoricalSearch](Get-HistoricalSearch.md) + +### [Get-LogonStatistics](Get-LogonStatistics.md) + +### [Get-MailDetailDlpPolicyReport](Get-MailDetailDlpPolicyReport.md) + +### [Get-MailDetailEncryptionReport](Get-MailDetailEncryptionReport.md) + +### [Get-MailDetailTransportRuleReport](Get-MailDetailTransportRuleReport.md) + +### [Get-MailFilterListReport](Get-MailFilterListReport.md) + +### [Get-MailflowStatusReport](Get-MailflowStatusReport.md) + +### [Get-MailTrafficEncryptionReport](Get-MailTrafficEncryptionReport.md) + +### [Get-MailTrafficPolicyReport](Get-MailTrafficPolicyReport.md) + +### [Get-MailTrafficSummaryReport](Get-MailTrafficSummaryReport.md) + +### [Get-MxRecordReport](Get-MxRecordReport.md) + +### [Get-OutboundConnectorReport](Get-OutboundConnectorReport.md) + +### [Get-RecipientStatisticsReport](Get-RecipientStatisticsReport.md) + +### [Get-ReportExecutionInstance](Get-ReportExecutionInstance.md) + +### [Get-SCInsights](Get-SCInsights.md) + +### [Get-ServiceDeliveryReport](Get-ServiceDeliveryReport.md) + +### [Get-SupervisoryReviewActivity](Get-SupervisoryReviewActivity.md) + +### [Get-SupervisoryReviewOverallProgressReport](Get-SupervisoryReviewOverallProgressReport.md) + +### [Get-SupervisoryReviewPolicyReport](Get-SupervisoryReviewPolicyReport.md) + +### [Get-SupervisoryReviewReport](Get-SupervisoryReviewReport.md) + +### [Get-SupervisoryReviewTopCasesReport](Get-SupervisoryReviewTopCasesReport.md) + +### [Test-Message](Test-Message.md] + +## role-based-access-control Cmdlets +### [Add-ManagementRoleEntry](Add-ManagementRoleEntry.md) + +### [Add-RoleGroupMember](Add-RoleGroupMember.md) + +### [Get-ManagementRole](Get-ManagementRole.md) + +### [Get-ManagementRoleAssignment](Get-ManagementRoleAssignment.md) + +### [Get-ManagementRoleEntry](Get-ManagementRoleEntry.md) + +### [Get-ManagementScope](Get-ManagementScope.md) + +### [Get-RoleAssignmentPolicy](Get-RoleAssignmentPolicy.md) + +### [Get-RoleGroup](Get-RoleGroup.md) + +### [Get-RoleGroupMember](Get-RoleGroupMember.md) + +### [New-ManagementRole](New-ManagementRole.md) + +### [New-ManagementRoleAssignment](New-ManagementRoleAssignment.md) + +### [New-ManagementScope](New-ManagementScope.md) + +### [New-RoleAssignmentPolicy](New-RoleAssignmentPolicy.md) + +### [New-RoleGroup](New-RoleGroup.md) + +### [Remove-ManagementRole](Remove-ManagementRole.md) + +### [Remove-ManagementRoleAssignment](Remove-ManagementRoleAssignment.md) + +### [Remove-ManagementRoleEntry](Remove-ManagementRoleEntry.md) + +### [Remove-ManagementScope](Remove-ManagementScope.md) + +### [Remove-RoleAssignmentPolicy](Remove-RoleAssignmentPolicy.md) + +### [Remove-RoleGroup](Remove-RoleGroup.md) + +### [Remove-RoleGroupMember](Remove-RoleGroupMember.md) + +### [Set-ManagementRoleAssignment](Set-ManagementRoleAssignment.md) + +### [Set-ManagementRoleEntry](Set-ManagementRoleEntry.md) + +### [Set-ManagementScope](Set-ManagementScope.md) + +### [Set-RoleAssignmentPolicy](Set-RoleAssignmentPolicy.md) + +### [Set-RoleGroup](Set-RoleGroup.md) + +### [Update-RoleGroupMember](Update-RoleGroupMember.md) + +## server-health-and-performance Cmdlets +### [Add-GlobalMonitoringOverride](Add-GlobalMonitoringOverride.md) + +### [Add-ServerMonitoringOverride](Add-ServerMonitoringOverride.md) + +### [Get-AvailabilityReportOutage](Get-AvailabilityReportOutage.md) + +### [Get-EventLogLevel](Get-EventLogLevel.md) + +### [Get-GlobalMonitoringOverride](Get-GlobalMonitoringOverride.md) + +### [Get-HealthReport](Get-HealthReport.md) + +### [Get-MonitoringItemHelp](Get-MonitoringItemHelp.md) + +### [Get-MonitoringItemIdentity](Get-MonitoringItemIdentity.md) + +### [Get-ServerComponentState](Get-ServerComponentState.md) + +### [Get-ServerHealth](Get-ServerHealth.md) + +### [Get-ServerMonitoringOverride](Get-ServerMonitoringOverride.md) + +### [Get-ThrottlingPolicy](Get-ThrottlingPolicy.md) + +### [Get-ThrottlingPolicyAssociation](Get-ThrottlingPolicyAssociation.md) + +### [Invoke-MonitoringProbe](Invoke-MonitoringProbe.md) + +### [New-AvailabilityReportOutage](New-AvailabilityReportOutage.md) + +### [New-ThrottlingPolicy](New-ThrottlingPolicy.md) + +### [Remove-AvailabilityReportOutage](Remove-AvailabilityReportOutage.md) + +### [Remove-GlobalMonitoringOverride](Remove-GlobalMonitoringOverride.md) + +### [Remove-ServerMonitoringOverride](Remove-ServerMonitoringOverride.md) + +### [Remove-ThrottlingPolicy](Remove-ThrottlingPolicy.md) + +### [Set-AvailabilityReportOutage](Set-AvailabilityReportOutage.md) + +### [Set-EventLogLevel](Set-EventLogLevel.md) + +### [Set-ServerComponentState](Set-ServerComponentState.md) + +### [Set-ServerMonitor](Set-ServerMonitor.md) + +### [Set-ThrottlingPolicy](Set-ThrottlingPolicy.md) + +### [Set-ThrottlingPolicyAssociation](Set-ThrottlingPolicyAssociation.md) + +### [Test-ServiceHealth](Test-ServiceHealth.md) + +## sharing-and-collaboration Cmdlets +### [Add-AvailabilityAddressSpace](Add-AvailabilityAddressSpace.md) + +### [Add-PublicFolderAdministrativePermission](Add-PublicFolderAdministrativePermission.md) + +### [Add-PublicFolderClientPermission](Add-PublicFolderClientPermission.md) + +### [Disable-MailPublicFolder](Disable-MailPublicFolder.md) + +### [Enable-MailPublicFolder](Enable-MailPublicFolder.md) + +### [Get-AvailabilityAddressSpace](Get-AvailabilityAddressSpace.md) + +### [Get-AvailabilityConfig](Get-AvailabilityConfig.md) + +### [Get-MailPublicFolder](Get-MailPublicFolder.md) + +### [Get-OrganizationRelationship](Get-OrganizationRelationship.md) + +### [Get-PublicFolder](Get-PublicFolder.md) + +### [Get-PublicFolderAdministrativePermission](Get-PublicFolderAdministrativePermission.md) + +### [Get-PublicFolderClientPermission](Get-PublicFolderClientPermission.md) + +### [Get-PublicFolderDatabase](Get-PublicFolderDatabase.md) + +### [Get-PublicFolderItemStatistics](Get-PublicFolderItemStatistics.md) + +### [Get-PublicFolderMailboxDiagnostics](Get-PublicFolderMailboxDiagnostics.md) + +### [Get-PublicFolderStatistics](Get-PublicFolderStatistics.md) + +### [Get-SharingPolicy](Get-SharingPolicy.md) + +### [Get-SiteMailbox](Get-SiteMailbox.md) + +### [Get-SiteMailboxDiagnostics](Get-SiteMailboxDiagnostics.md) + +### [Get-SiteMailboxProvisioningPolicy](Get-SiteMailboxProvisioningPolicy.md) + +### [New-AvailabilityConfig](New-AvailabilityConfig.md) + +### [New-OrganizationRelationship](New-OrganizationRelationship.md) + +### [New-PublicFolder](New-PublicFolder.md) + +### [New-PublicFolderDatabase](New-PublicFolderDatabase.md) + +### [New-PublicFolderDatabaseRepairRequest](New-PublicFolderDatabaseRepairRequest.md) + +### [New-SharingPolicy](New-SharingPolicy.md) + +### [New-SiteMailboxProvisioningPolicy](New-SiteMailboxProvisioningPolicy.md) + +### [New-SyncMailPublicFolder](New-SyncMailPublicFolder.md) + +### [Remove-AvailabilityAddressSpace](Remove-AvailabilityAddressSpace.md) + +### [Remove-AvailabilityConfig](Remove-AvailabilityConfig.md) + +### [Remove-OrganizationRelationship](Remove-OrganizationRelationship.md) + +### [Remove-PublicFolder](Remove-PublicFolder.md) + +### [Remove-PublicFolderAdministrativePermission](Remove-PublicFolderAdministrativePermission.md) + +### [Remove-PublicFolderClientPermission](Remove-PublicFolderClientPermission.md) + +### [Remove-PublicFolderDatabase](Remove-PublicFolderDatabase.md) + +### [Remove-SharingPolicy](Remove-SharingPolicy.md) + +### [Remove-SiteMailboxProvisioningPolicy](Remove-SiteMailboxProvisioningPolicy.md) + +### [Remove-SyncMailPublicFolder](Remove-SyncMailPublicFolder.md) + +### [Resume-PublicFolderReplication](Resume-PublicFolderReplication.md) + +### [Set-AvailabilityConfig](Set-AvailabilityConfig.md) + +### [Set-MailPublicFolder](Set-MailPublicFolder.md) + +### [Set-OrganizationRelationship](Set-OrganizationRelationship.md) + +### [Set-PublicFolder](Set-PublicFolder.md) + +### [Set-PublicFolderDatabase](Set-PublicFolderDatabase.md) + +### [Set-SharingPolicy](Set-SharingPolicy.md) + +### [Set-SiteMailbox](Set-SiteMailbox.md) + +### [Set-SiteMailboxProvisioningPolicy](Set-SiteMailboxProvisioningPolicy.md) + +### [Suspend-PublicFolderReplication](Suspend-PublicFolderReplication.md) + +### [Test-OrganizationRelationship](Test-OrganizationRelationship.md) + +### [Test-SiteMailbox](Test-SiteMailbox.md) + +### [Update-PublicFolder](Update-PublicFolder.md) + +### [Update-PublicFolderHierarchy](Update-PublicFolderHierarchy.md) + +### [Update-PublicFolderMailbox](Update-PublicFolderMailbox.md) + +### [Update-SiteMailbox](Update-SiteMailbox.md) + +## unified-messaging Cmdlets +### [Disable-UMAutoAttendant](Disable-UMAutoAttendant.md) + +### [Disable-UMCallAnsweringRule](Disable-UMCallAnsweringRule.md) + +### [Disable-UMIPGateway](Disable-UMIPGateway.md) + +### [Disable-UMMailbox](Disable-UMMailbox.md) + +### [Disable-UMServer](Disable-UMServer.md) + +### [Disable-UMService](Disable-UMService.md) + +### [Enable-UMAutoAttendant](Enable-UMAutoAttendant.md) + +### [Enable-UMCallAnsweringRule](Enable-UMCallAnsweringRule.md) + +### [Enable-UMIPGateway](Enable-UMIPGateway.md) + +### [Enable-UMMailbox](Enable-UMMailbox.md) + +### [Enable-UMServer](Enable-UMServer.md) + +### [Enable-UMService](Enable-UMService.md) + +### [Export-UMCallDataRecord](Export-UMCallDataRecord.md) + +### [Export-UMPrompt](Export-UMPrompt.md) + +### [Get-OnlineMeetingConfiguration](Get-OnlineMeetingConfiguration.md) + +### [Get-UMActiveCalls](Get-UMActiveCalls.md) + +### [Get-UMAutoAttendant](Get-UMAutoAttendant.md) + +### [Get-UMCallAnsweringRule](Get-UMCallAnsweringRule.md) + +### [Get-UMCallDataRecord](Get-UMCallDataRecord.md) + +### [Get-UMCallRouterSettings](Get-UMCallRouterSettings.md) + +### [Get-UMCallSummaryReport](Get-UMCallSummaryReport.md) + +### [Get-UMDialPlan](Get-UMDialPlan.md) + +### [Get-UMHuntGroup](Get-UMHuntGroup.md) + +### [Get-UMIPGateway](Get-UMIPGateway.md) + +### [Get-UMMailbox](Get-UMMailbox.md) + +### [Get-UMMailboxPIN](Get-UMMailboxPIN.md) + +### [Get-UMMailboxPolicy](Get-UMMailboxPolicy.md) + +### [Get-UmServer](Get-UmServer.md) + +### [Get-UMService](Get-UMService.md) + +### [Import-UMPrompt](Import-UMPrompt.md) + +### [New-UMAutoAttendant](New-UMAutoAttendant.md) + +### [New-UMCallAnsweringRule](New-UMCallAnsweringRule.md) + +### [New-UMDialPlan](New-UMDialPlan.md) + +### [New-UMHuntGroup](New-UMHuntGroup.md) + +### [New-UMIPGateway](New-UMIPGateway.md) + +### [New-UMMailboxPolicy](New-UMMailboxPolicy.md) + +### [Remove-UMAutoAttendant](Remove-UMAutoAttendant.md) + +### [Remove-UMCallAnsweringRule](Remove-UMCallAnsweringRule.md) + +### [Remove-UMDialPlan](Remove-UMDialPlan.md) + +### [Remove-UMHuntGroup](Remove-UMHuntGroup.md) + +### [Remove-UMIPGateway](Remove-UMIPGateway.md) + +### [Remove-UMMailboxPolicy](Remove-UMMailboxPolicy.md) + +### [Set-UMAutoAttendant](Set-UMAutoAttendant.md) + +### [Set-UMCallAnsweringRule](Set-UMCallAnsweringRule.md) + +### [Set-UMCallRouterSettings](Set-UMCallRouterSettings.md) + +### [Set-UMDialPlan](Set-UMDialPlan.md) + +### [Set-UMIPGateway](Set-UMIPGateway.md) + +### [Set-UMMailbox](Set-UMMailbox.md) + +### [Set-UMMailboxPIN](Set-UMMailboxPIN.md) + +### [Set-UMMailboxPolicy](Set-UMMailboxPolicy.md) + +### [Set-UmServer](Set-UmServer.md) + +### [Set-UMService](Set-UMService.md) + +### [Test-UMConnectivity](Test-UMConnectivity.md) + +## users-and-groups Cmdlets +### [Add-DistributionGroupMember](Add-DistributionGroupMember.md) + +### [Add-UnifiedGroupLinks](Add-UnifiedGroupLinks.md) + +### [Disable-DistributionGroup](Disable-DistributionGroup.md) + +### [Disable-MailContact](Disable-MailContact.md) + +### [Disable-MailUser](Disable-MailUser.md) + +### [Enable-DistributionGroup](Enable-DistributionGroup.md) + +### [Enable-MailContact](Enable-MailContact.md) + +### [Enable-MailUser](Enable-MailUser.md) + +### [Get-Contact](Get-Contact.md) + +### [Get-DistributionGroup](Get-DistributionGroup.md) + +### [Get-DistributionGroupMember](Get-DistributionGroupMember.md) + +### [Get-DynamicDistributionGroup](Get-DynamicDistributionGroup.md) + +### [Get-DynamicDistributionGroupMember](Get-DynamicDistributionGroupMember.md) + +### [Get-EligibleDistributionGroupForMigration](Get-EligibleDistributionGroupForMigration.md) + +### [Get-Group](Get-Group.md) + +### [Get-LinkedUser](Get-LinkedUser.md) + +### [Get-MailContact](Get-MailContact.md) + +### [Get-MailUser](Get-MailUser.md) + +### [Get-Recipient](Get-Recipient.md) + +### [Get-SecurityPrincipal](Get-SecurityPrincipal.md) + +### [Get-UnifiedGroup](Get-UnifiedGroup.md) + +### [Get-UnifiedGroupLinks](Get-UnifiedGroupLinks.md) + +### [Get-User](Get-User.md) + +### [New-DistributionGroup](New-DistributionGroup.md) + +### [New-DynamicDistributionGroup](New-DynamicDistributionGroup.md) + +### [New-MailContact](New-MailContact.md) + +### [New-MailUser](New-MailUser.md) + +### [New-UnifiedGroup](New-UnifiedGroup.md) + +### [Remove-DistributionGroup](Remove-DistributionGroup.md) + +### [Remove-DistributionGroupMember](Remove-DistributionGroupMember.md) + +### [Remove-DynamicDistributionGroup](Remove-DynamicDistributionGroup.md) + +### [Remove-MailContact](Remove-MailContact.md) + +### [Remove-MailUser](Remove-MailUser.md) + +### [Remove-UnifiedGroup](Remove-UnifiedGroup.md) + +### [Remove-UnifiedGroupLinks](Remove-UnifiedGroupLinks.md) + +### [Set-Contact](Set-Contact.md) + +### [Set-DistributionGroup](Set-DistributionGroup.md) + +### [Set-DynamicDistributionGroup](Set-DynamicDistributionGroup.md) + +### [Set-Group](Set-Group.md) + +### [Set-LinkedUser](Set-LinkedUser.md) + +### [Set-MailContact](Set-MailContact.md) + +### [Set-MailUser](Set-MailUser.md) + +### [Set-UnifiedGroup](Set-UnifiedGroup.md) -- [Exchange Server PowerShell (Exchange Management Shell)](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-management-shell) +### [Set-User](Set-User.md) -- [Exchange Online PowerShell](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell) +### [Undo-SoftDeletedUnifiedGroup](Undo-SoftDeletedUnifiedGroup.md) -- [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell) +### [Update-DistributionGroupMember](Update-DistributionGroupMember.md) -- [Exchange Online Protection PowerShell](https://docs.microsoft.com/powershell/exchange/exchange-eop/exchange-online-protection-powershell) +### [Upgrade-DistributionGroup](Upgrade-DistributionGroup.md) diff --git a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridMailflow.md b/exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridMailflow.md deleted file mode 100644 index fb333ebf1c..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridMailflow.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-hybridmailflow -applicable: Exchange Online -title: Get-HybridMailflow -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-HybridMailflow - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -**Note**: This cmdlet has been deprecated and is no longer used. - -Use the Get-HybridMailflow cmdlet to view the message transport settings for a hybrid deployment. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-HybridMailflow [<CommonParameters>] -``` - -## DESCRIPTION -The Get-HybridMailflow cmdlet is used to view the configuration of message transport settings for hybrid deployments that were created with the Hybrid Configuration wizard. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-HybridMailflow -``` - -This example returns the message transport settings for the hybrid deployment. - -## 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/federation-and-hybrid/Get-HybridMailflowDatacenterIPs.md b/exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridMailflowDatacenterIPs.md deleted file mode 100644 index 303844cbd3..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridMailflowDatacenterIPs.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-hybridmailflowdatacenterips -applicable: Exchange Online -title: Get-HybridMailflowDatacenterIPs -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-HybridMailflowDatacenterIPs - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -**Note**: This cmdlet has been deprecated and is no longer used. - -Use the Get-HybridMailflowDatacenterIPs cmdlet to retrieve the IP addresses of the Microsoft Exchange Online Protection (EOP) service data centers. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-HybridMailflowDatacenterIPs [<CommonParameters>] -``` - -## DESCRIPTION -The Get-HybridMailflowDatacenterIPs cmdlet supports hybrid deployments and lists the IP addresses of EOP service data centers that support hybrid deployments. The list isn't specific to any on-premises Exchange organization. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-HybridMailflowDatacenterIPs -``` - -This example returns IP address information for EOP service data centers that support hybrid deployments. - -## 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/federation-and-hybrid/Get-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/federation-and-hybrid/Get-OnPremisesOrganization.md deleted file mode 100644 index afbcca5893..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Get-OnPremisesOrganization.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/get-onpremisesorganization -applicable: Exchange Online -title: Get-OnPremisesOrganization -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-OnPremisesOrganization - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-OnPremisesOrganization cmdlet to retrieve settings for the OnPremisesOrganization object that has been created for a hybrid deployment. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-OnPremisesOrganization [[-Identity] <OnPremisesOrganizationIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft Office 365 tenant organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. You can use the Get-OnPremisesOrganization cmdlet to view the properties of the OnPremisesOrganization object in the Office 365 tenant. - -Manual modification of this object may result in hybrid deployment misconfiguration. We strongly recommend that you use the Hybrid Configuration wizard to modify this object in the Office 365 tenant. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-OnPremisesOrganization -Identity ExchangeMail | Format-List -``` - -This example retrieves the on-premises organization settings for ExchangeMail using the Identity parameter. - -### Example 2 -```powershell -Get-OnPremisesOrganization -DomainController 'mail.contoso.com' | Format-List -``` - -This example retrieves the on-premises organization settings by using the FQDN of the domain controller. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the identity of the on-premises organization object. You can use the following values: - -- Canonical name - -- GUID - -- Name - -```yaml -Type: OnPremisesOrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/federation-and-hybrid/New-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/federation-and-hybrid/New-OnPremisesOrganization.md deleted file mode 100644 index 5bfa6b5679..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/New-OnPremisesOrganization.md +++ /dev/null @@ -1,229 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/new-onpremisesorganization -applicable: Exchange Online -title: New-OnPremisesOrganization -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# New-OnPremisesOrganization - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-OnPremisesOrganization cmdlet to create an OnPremisesOrganization object in a Microsoft Office 365 tenant. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-OnPremisesOrganization [-Name] <String> -HybridDomains <MultiValuedProperty> - -InboundConnector <InboundConnectorIdParameter> -OrganizationGuid <Guid> - -OutboundConnector <OutboundConnectorIdParameter> [-Comment <String>] [-Confirm] [-OrganizationName <String>] - [-OrganizationRelationship <OrganizationRelationshipIdParameter>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with an Office 365 tenant organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Office 365 tenant. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-OnPremisesOrganization -Name "ExchangeMail" -OrganizationGuid "a1bc23cb-3456-bcde-abcd-feb363cacc88" -HybridDomains contoso.com, sales.contoso.com -InboundConnector "Inbound to ExchangeMail" -OutboundConnector "Outbound to ExchangeMail" -``` - -This example creates the OnPremisesOrganization object ExchangeMail in an Office 365 tenant for the hybrid domains contoso.com and sales.contoso.com. - -## PARAMETERS - -### -HybridDomains -The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between an Office 365 tenant 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 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundConnector -The InboundConnector parameter specifies the name of the inbound connector configured on the Microsoft Exchange Online Protection (EOP) service for a hybrid deployment configured with an on-premises Exchange organization. - -```yaml -Type: InboundConnectorIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies a friendly name for the on-premises Exchange organization object in the Office 365 tenant. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationGuid -The OrganizationGuid parameter specifies the globally unique identifier (GUID) of the on-premises Exchange organization object in the Office 365 tenant. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutboundConnector -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: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationRelationship -The OrganizationRelationship parameter specifies the organization relationship configured by the Hybrid Configuration wizard on the Office 365 tenant as part of a hybrid deployment with an on-premises Exchange organization. This organization relationship defines the federated sharing features enabled on the Office 365 tenant. - -```yaml -Type: OrganizationRelationshipIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/federation-and-hybrid/Set-HybridMailflow.md b/exchange/exchange-ps/exchange/federation-and-hybrid/Set-HybridMailflow.md deleted file mode 100644 index 2915978a9f..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-HybridMailflow.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-hybridmailflow -applicable: Exchange Online -title: Set-HybridMailflow -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-HybridMailflow - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-HybridMailflow cmdlet to configure the message transport settings for the Microsoft Exchange Online Protection (EOP) service in a hybrid deployment. - -The Set-HybridMailflow cmdlet is only used to support hybrid deployments configured with the Hybrid Configuration wizard offered in Microsoft Exchange Server 2010 Service Pack 2 (SP2). - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-HybridMailflow [-CentralizedTransportEnabled <Boolean>] [-CertificateSubject <String>] [-Confirm] - [-InboundIPs <IPRange[]>] [-OnPremisesFQDN <Fqdn>] [-OutboundDomains <SmtpDomainWithSubdomains[]>] - [-SecureMailEnabled <Boolean>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-HybridMailflow cmdlet supports the configuration of message transport settings for hybrid deployments created with the Hybrid Configuration wizard offered in Exchange 2010 SP2. This cmdlet isn't typically used by administrators; therefore, we strongly recommend that it only be used as part of the hybrid configuration process using the Hybrid Configuration wizard. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-HybridMailflow -``` - -This example configures the message transport settings in the EOP service for a hybrid deployment. - -## PARAMETERS - -### -CentralizedTransportEnabled -The CentralizedTransportEnabled parameter specifies that the Exchange Online organization routes all outbound mail messages to external recipients to the on-premises Exchange organization. The on-premises Exchange organization then routes the messages to the external recipients. The valid input for the CentralizedTransportEnabled parameter is $true or $false. The default value is $true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -CertificateSubject -The CertificateSubject parameter specifies the principal name of the certificate used for secure mail flow between the on-premises Exchange and Exchange Online organizations. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundIPs -The InboundIPs parameter specifies the IP addresses of the on-premises mail transport servers configured as part of the hybrid deployment. These must point to either Exchange 2010 SP2 Hub Transport or Edge Transport servers. - -```yaml -Type: IPRange[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -OnPremisesFQDN -The OnPremisesFQDN parameter specifies the fully qualified domain name (FQDN) of the outbound smart host in the on-premises Exchange organization to use for centralized transport. This is either an on-premises Exchange 2010 SP2 Hub Transport or Edge Transport server. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -OutboundDomains -The OutboundDomains parameter specifies SMTP domains configured for the hybrid deployment. - -```yaml -Type: SmtpDomainWithSubdomains[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -SecureMailEnabled -The SecureMailEnabled parameter specifies that all messages sent between the on-premises Exchange and the Exchange Online organizations must use the Transport Layer Security (TLS) protocol and the assigned digital certificate. The valid input for the SecureMailEnabled parameter is $true or $false. The default value is $true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/federation-and-hybrid/Set-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/federation-and-hybrid/Set-OnPremisesOrganization.md deleted file mode 100644 index 5d7f9efe64..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Set-OnPremisesOrganization.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/set-onpremisesorganization -applicable: Exchange Online -title: Set-OnPremisesOrganization -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-OnPremisesOrganization - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-OnPremisesOrganization cmdlet to modify the parameters of the OnPremisesOrganization object on the Microsoft Office 365 tenant. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-OnPremisesOrganization [-Identity] <OnPremisesOrganizationIdParameter> [-Comment <String>] [-Confirm] - [-HybridDomains <MultiValuedProperty>] [-InboundConnector <InboundConnectorIdParameter>] - [-OrganizationName <String>] [-OrganizationRelationship <OrganizationRelationshipIdParameter>] - [-OutboundConnector <OutboundConnectorIdParameter>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with an Office 365 tenant organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Office 365 tenant. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-OnPremisesOrganization -Identity "ExchangeMail" -HybridDomains contoso.com, sales.contoso.com, legal.contoso.com -``` - -This example adds a third domain legal.contoso.com to the ExchangeMail OnPremisesOrganization object on the Office 365 tenant, which already has the contoso.com and sales.contoso.com domains. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the identity of the on-premises organization object. You can use the following values: - -- Canonical name - -- GUID - -- Name - -```yaml -Type: OnPremisesOrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Comment -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HybridDomains -The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between an Office 365 tenant 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundConnector -The InboundConnector parameter specifies the name of the inbound connector configured on the Microsoft Exchange Online Protection (EOP) service 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationRelationship -The OrganizationRelationship parameter specifies the organization relationship configured by the Hybrid Configuration wizard on the Office 365 tenant as part of a hybrid deployment with an on-premises Exchange organization. This organization relationship defines the federated sharing features enabled on the Office 365 tenant. - -```yaml -Type: OrganizationRelationshipIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutboundConnector -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/federation-and-hybrid/Update-HybridConfiguration.md b/exchange/exchange-ps/exchange/federation-and-hybrid/Update-HybridConfiguration.md deleted file mode 100644 index aa3203983e..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Update-HybridConfiguration.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Update-HybridConfiguration - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Update-HybridConfiguration cmdlet to define the credentials that are used to update the hybrid configuration object. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Update-HybridConfiguration -OnPremisesCredentials <PSCredential> -TenantCredentials <PSCredential> [-Confirm] - [-DomainController <Fqdn>] [-WhatIf] [-ForceUpgrade] [-SuppressOAuthWarning] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -$OnPremisesCreds = Get-Credential; $TenantCreds = Get-Credential; Update-HybridConfiguration -OnPremisesCredentials $OnPremisesCreds -TenantCredentials $TenantCreds -``` - -This example defines the credentials that are used to update the hybrid configuration object and connect to the Microsoft Office 365 for enterprises organization. - -Use the first command to specify your on-premises organization credentials. For example, run this command and enter \<domain\>\\admin@contoso.com and the associated password in the resulting Windows PowerShell Credential Request dialog box. - -Use the second command to specify your Office 365 for enterprises organization credentials. For example, run this command and then enter admin@contoso.onmicrosoft.com and the associated account password in the resulting Windows PowerShell Credential Request dialog box. - -Use the last command to define the credentials that are used to update the hybrid configuration object and connect to the Office 365 for enterprises organization. - -## PARAMETERS - -### -OnPremisesCredentials -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantCredentials -The TenantCredentials parameter specifies the Office 365 for enterprises organization account and password that's used to configure the hybrid configuration object. This is often the administrator account that's assigned when the Office 365 organization was created. This account must be a member of the Office 365 Global admin role. - -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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 only displayed when the existing HybridConfiguration Active Directory object version is Exchange 2010. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressOAuthWarning -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/federation-and-hybrid/Update-Recipient.md b/exchange/exchange-ps/exchange/federation-and-hybrid/Update-Recipient.md deleted file mode 100644 index 83559dd503..0000000000 --- a/exchange/exchange-ps/exchange/federation-and-hybrid/Update-Recipient.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Update-Recipient - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Update-Recipient cmdlet to add Microsoft Exchange attributes to recipient objects created by the global address list (GAL) synchronization management agent in Microsoft Forefront Identity Manager (FIM) 2010. The recipient objects you modify using this cmdlet must reside on a server running Microsoft Exchange Server 2010 or later. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Update-Recipient [-Identity] <RecipientIdParameter> [-Confirm] [-Credential <PSCredential>] - [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Because of mergers, acquisitions, or legal requirements, customers may need to deploy Exchange in a multiple Exchange forest topology. These deployments require the synchronization of recipient objects across disparate Active Directory forests. - -Microsoft provides the GAL synchronization management agent for synchronizing recipient objects. The version of the GAL synchronization management agent included in Microsoft Identity Integration Server (MIIS) 2003 was designed to work with Exchange Server 2003 and relied on the Recipient Update Service. Because the Recipient Update Service is a deprecated feature and is no longer required, the new GAL synchronization management agent included in FIM 2010 is designed to function without the Recipient Update Service. - -As part of the synchronization process, the FIM 2010 GAL synchronization management agent creates recipient objects in both Active Directory forests. After the recipients are created, the management agent uses the Update-Recipient cmdlet to add the attributes required by Microsoft Exchange to complete the provisioning of these recipients. - -In Exchange, before you can run the Update-Recipient cmdlet to convert an Active Directory user object into an Exchange mailbox, you must stamp the user object with the following three mandatory Exchange attributes: - -- homeMDB - -- mailNickname - -- msExchHomeServerName - -If you're using MIIS 2003, you must run various cmdlets to complete the provisioning process of the mail contacts created by the GAL synchronization management agent. The Update-Recipient cmdlet provides an alternate and more efficient method to do this. You can run the Update-Recipient cmdlet against the recipient objects created by the MIIS 2003 GAL synchronization management agent to complete the provisioning process. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Update-Recipient -Identity "John Smith" -``` - -This example adds Exchange attributes to the mail contact that represents John Smith's mailbox. - -### Example 2 -```powershell -Get-MailContact -OrganizationalUnit "contoso.com/fabrikam.com Users" | Update-Recipient -``` - -This example updates all contacts in a specific organizational unit (OU). This example assumes that recipients are synchronized between two forests, contoso.com and fabrikam.com, and all the synchronized recipients from the fabrikam.com domain are stored in a specific OU called fabrikam.com Users in the contoso.com domain. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the recipient that you want to update. You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mail-flow/Get-MessageTraceDetail.md b/exchange/exchange-ps/exchange/mail-flow/Get-MessageTraceDetail.md deleted file mode 100644 index 7d9833794b..0000000000 --- a/exchange/exchange-ps/exchange/mail-flow/Get-MessageTraceDetail.md +++ /dev/null @@ -1,288 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/get-messagetracedetail -applicable: Exchange Online -title: Get-MessageTraceDetail -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-MessageTraceDetail - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. Note that these detailed results are returned less quickly than the Get-MessageTrace results. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MessageTraceDetail - [-Action <MultiValuedProperty>] - [-EndDate <DateTime>] - [-Event <MultiValuedProperty>] - [-Expression <Expression>] - [-MessageId <String>] - [-MessageTraceId <Guid>] - [-Page <Int32>] - [-PageSize <Int32>] - [-ProbeTag <String>] - [-RecipientAddress <String>] - [-SenderAddress <String>] - [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use this cmdlet to search message data for the last 30 days. If you enter a time period that's older than 30 days, you won't receive an error, but the command will return no results. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MessageTrace -MessageTraceId 2bbad36aa4674c7ba82f4b307fff549f -SenderAddress john@contoso.com -StartDate 06/13/2018 -EndDate 06/15/2018 | Get-MessageTraceDetail -``` - -This example uses the Get-MessageTrace cmdlet to retrieve message trace information for messages with the Exchange Network Message ID value 2bbad36aa4674c7ba82f4b307fff549f send by john@contoso.com between June 13, 2018 and June 15, 2018, and pipelines the results to the Get-MessageTraceDetail cmdlet. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Event -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. - -- SEND: The message was sent by the service. - -- FAIL: The message failed to be delivered. - -- DELIVER: The message was delivered to a mailbox. - -- EXPAND: The message was sent to a distribution group that was expanded. - -- TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents. - -- DEFER: The message delivery was postponed and may be re-attempted later. - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageId -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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -MessageTraceId -The MessageTraceId parameter can be used with the recipient address to uniquely identify a message trace and obtain more details. A message trace ID is generated for every message that's processed by the system. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAddress -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -SenderAddress -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: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mail-flow/New-InboundConnector.md b/exchange/exchange-ps/exchange/mail-flow/New-InboundConnector.md deleted file mode 100644 index 362e99b613..0000000000 --- a/exchange/exchange-ps/exchange/mail-flow/New-InboundConnector.md +++ /dev/null @@ -1,498 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/new-inboundconnector -applicable: Exchange Online, Exchange Online Protection -title: New-InboundConnector -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# New-InboundConnector - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-InboundConnector cmdlet to create a new Inbound connector in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-InboundConnector [-Name] <String> -SenderDomains <MultiValuedProperty> - [-AssociatedAcceptedDomains <MultiValuedProperty>] - [-CloudServicesMailEnabled <Boolean>] - [-Comment <String>] - [-Confirm] - [-ConnectorSource <TenantConnectorSource>] - [-ConnectorType <TenantConnectorType>] - [-EFSkipIPs <MultiValuedProperty>] - [-EFSkipLastIP <Boolean>] - [-EFSkipMailGateway <MultiValuedProperty>] - [-EFTestMode <Boolean>] - [-Enabled <Boolean>] - [-RequireTls <Boolean>] - [-RestrictDomainsToCertificate <Boolean>] - [-RestrictDomainsToIPAddresses <Boolean>] - [-ScanAndDropRecipients <MultiValuedProperty>] - [-SenderIPAddresses <MultiValuedProperty>] - [-TlsSenderCertificateName <TlsCertificate>] - [-TreatMessagesAsInternal <Boolean>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Inbound connectors accept email messages from remote domains that require specific configuration options. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-InboundConnector -Name "Contoso Inbound Connector" -SenderDomains *.contoso.com -SenderIPAddresses 192.168.0.1/25 -RestrictDomainsToIPAddresses $true -``` - -This example creates the Inbound connector named Contoso Inbound Connector with the following properties: - -- It listens for incoming connections from the domain contoso.com and all subdomains. - -- It only accepts mail from contoso.com, and from the IP range 192.168.0.1/25. It rejects mail from contoso.com if it originates from any other IP address. - -### Example 2 -```powershell -New-InboundConnector -Name "Contoso Inbound Secure Connector" -SenderDomains *.contoso.com -SenderIPAddresses 192.168.0.1/25 -RestrictDomainsToIPAddresses $true -RequireTLS $true -TlsSenderCertificateName *.contoso.com -``` - -This example creates the Inbound connector named Contoso Inbound Secure Connector and requires TLS transmission for all messages. - -## PARAMETERS - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderDomains -The SenderDomains parameter specifies the remote domains from which this connector accepts messages, thereby limiting its scope. 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. You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssociatedAcceptedDomains -The AssociatedAcceptedDomains parameter specifies the accepted domains that the connector applies to, thereby limiting its scope. For example, you can apply the connector to a specific accepted domain in your organization, such as contoso.com. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CloudServicesMailEnabled -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://docs.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 Office 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. - -Valid values are: - -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - -- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorSource -The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values: - -- Default: The connector is manually created. - -- HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - -- Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. - -The default value for connectors you create yourself is Default. It isn't recommended that you change this value. - -```yaml -Type: TenantConnectorSource -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorType -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. - -- OnPremises: The connector services domains that are used by your on-premises organization. Use this value for accepted domains in your cloud-based organization that are also specified by the SenderDomains parameter. - -```yaml -Type: TenantConnectorType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFSkipIPs -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: - -- A single IP address: For example, 192.168.1.1. - -- An IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.3.1/24 - -You can specify multiple IP addresses or address range entries separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFSkipLastIP -The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are: - -- $true: Only the last message source is skipped. - -- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFSkipMailGateway -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFTestMode -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFUsers -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter enables or disables the connector. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireTls -The RequireTLS parameter specifies that all messages received by this connector require TLS transmission. Valid values for this parameter are $true or $false. The default value is $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictDomainsToCertificate -The RestrictDomainsToCertificate parameter specifies that Office 365 should identify incoming messages that are eligible for this connector by verifying that the remote server authenticates using a TLS certificate that has the TlsSenderCertificateName in the Subject. Valid values are $true or $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictDomainsToIPAddresses -The RestrictDomainsToIPAddresses parameter, when set to $true, automatically rejects mail from the domains specified by the SenderDomains parameter if the mail originates from an IP address that isn't specified by the SenderIPAddresses parameter. - -Valid input for this parameter is $true or $false. The default value is $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScanAndDropRecipients -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderIPAddresses -The SenderIPAddresses parameter specifies the remote IP addresses from which this connector accepts messages. You enter the IP addresses using the following syntax: - -- Single IP: For example, 192.168.1.1. - -- CIDR IP: You can use Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25. - -You can specify multiple IP addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TlsSenderCertificateName -The TlsSenderCertificateName parameter specifies the certificate used by the sender's domain when the RequireTls parameter is set to $true. Valid input for the TlsSenderCertificateName 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. - -You can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. - -```yaml -Type: TlsCertificate -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TreatMessagesAsInternal -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 Office 365. This setting allows internal mail flow between Office 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. - -- $false: Messages aren't considered internal. This is the default value. - -In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Office 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mail-flow/Remove-SystemMessage.md b/exchange/exchange-ps/exchange/mail-flow/Remove-SystemMessage.md deleted file mode 100644 index 353507c4c2..0000000000 --- a/exchange/exchange-ps/exchange/mail-flow/Remove-SystemMessage.md +++ /dev/null @@ -1,203 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/remove-systemmessage -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-SystemMessage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Remove-SystemMessage - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Remove-SystemMessage cmdlet to remove custom system messages. System messages are delivery status notifications (also known as DSNs, non-delivery reports, NDRs or bounce messages) and quota messages. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-SystemMessage [-Identity] <SystemMessageIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You can't remove a default system message that's included with Exchange. When you remove a custom system message, the message text reverts to the text in the corresponding system message (if any) that's included with Exchange. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-SystemMessage En\Internal\5.7.9 -``` - -This example removes the specified custom NDR (combination of language, audience, and enhanced status code values). - -### Example 2 -```powershell -Remove-SystemMessage En\WarningMailbox -``` - -This example removes the specified custom quota message (combination of language and quota values). - -## PARAMETERS - -### -Identity -TheIdentity 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 - -- Distinguished name (DN) - -- GUID - -The identity value of a system message uses one of these formats: - -- System messages for enhanced status codes: \<Language\>\\\<Internal \| External\>\\\<DSNcode\>. For example, En\\Internal\\5.1.2 or Ja\\External\\5.1.2. - -- System messages for quotas: \<Language\>\\\<QuotaMessageType\>. For example, En\\ProhibitSendReceiveMailBox. - -\<Language\>: For the list of supported language codes, see [Supported languages for NDRs](https://docs.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs). - -\<DSNcode\>: Valid values are 4.x.y or 5.x.y where x and y are one to three digit numbers. To see the enhanced system code values that are currently used by custom system messages, run the command Get-SystemMessage. - -\<QuotaMessageType\>: Valid value are: - -Mailbox size quotas: - -ProhibitSendReceiveMailBox: A mailbox exceeds its ProhibitSendReceiveQuota limit. - -ProhibitSendMailbox: A mailbox exceeds its ProhibitSendQuota limit. - -WarningMailbox: A mailbox exceeds its IssueWarningQuota limit when it has a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. - -WarningMailboxUnlimitedSize: A mailbox exceeds its IssueWarningQuota limit when it doesn't have a ProhibitSendQuota or ProhibitSendReceiveQuota limit configured. - -Public folder size quotas: - -ProhibitPostPublicFolder: A public folder exceeds its ProhibitPostQuota limit. - -WarningPublicFolder: A public folder exceeds its IssueWarningQuota limit when it has a ProhibitPostQuota limit configured. - -WarningPublicFolderUnlimitedSize: A public folder exceeds its IssueWarningQuota limit when it doesn't have a ProhibitPostQuota limit configured. - -Maximum number of messages in a mailbox folder: - -ProhibitReceiveMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountReceiveQuota limit. - -WarningMailboxMessagesPerFolderCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it has a MailboxMessagesPerFolderCountReceiveQuota limit configured. - -WarningMailboxMessagesPerFolderUnlimitedCount: A mailbox exceeds its MailboxMessagesPerFolderCountWarningQuota limit when it doesn't have a MailboxMessagesPerFolderCountReceiveQuota limit configured. - -Maximum number of subfolders in a mailbox folder: - -ProhibitReceiveFolderHierarchyChildrenCountCount: A mailbox exceeds its FolderHierarchyChildrenCountReceiveQuota limit. - -WarningFolderHierarchyChildrenCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it has a FolderHierarchyChildrenCountReceiveQuota limit configured. - -WarningFolderHierarchyChildrenUnlimitedCount: A mailbox exceeds its FolderHierarchyChildrenCountWarningQuota limit when it doesn't have a FolderHierarchyChildrenCountReceiveQuota limit configured. - -ProhibitReceiveFoldersCount: A mailbox exceeds its FoldersCountReceiveQuota limit. - -WarningFoldersCount: A mailbox exceeds its FoldersCountWarningQuota limit when it has a FoldersCountReceiveQuota limit configured. - -WarningFoldersCountUnlimited A mailbox exceeds its FoldersCountWarningQuota limit when it doesn't have a FoldersCountReceiveQuota limit configured. - -Maximum number of levels (depth) in a mailbox folder: - -ProhibitReceiveFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit. - -WarningFolderHierarchyDepth: A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it has a FolderHierarchyDepthReceiveQuota limit configured. - -WarningFolderHierarchyDepthUnlimited: : A mailbox exceeds its FolderHierarchyDepthWarningQuota limit when it doesn't have a FolderHierarchyDepthReceiveQuota limit configured. - -```yaml -Type: SystemMessageIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mail-flow/Set-AcceptedDomain.md b/exchange/exchange-ps/exchange/mail-flow/Set-AcceptedDomain.md deleted file mode 100644 index 785234fcfe..0000000000 --- a/exchange/exchange-ps/exchange/mail-flow/Set-AcceptedDomain.md +++ /dev/null @@ -1,313 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Set-AcceptedDomain - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-AcceptedDomain cmdlet to modify existing accepted domains in your organization. An accepted domain is any SMTP namespace for which an Exchange organization sends and receives email. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AcceptedDomain [-Identity] <AcceptedDomainIdParameter> [-AddressBookEnabled <Boolean>] - [-Confirm] [-DomainController <Fqdn>] - [-DomainType <AcceptedDomainType>] - [-MakeDefault <Boolean>] [-Name <String>] - [-OutboundOnly <Boolean>] [-PendingRemoval <Boolean>] [-WhatIf] - [-EnableNego2Authentication <Boolean>] [-MatchSubDomains <Boolean>] - [-PendingCompletion <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-AcceptedDomain -Identity Contoso -MakeDefault $true -``` - -This example makes the accepted domain Contoso the default accepted domain. - -## PARAMETERS - -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AddressBookEnabled -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: - -- $true for authoritative domains. - -- $false for internal relay domains. - -- $false for external relay domains. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainType -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. - -- InternalRelay: This is a type of non-authoritative domain. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external messaging system that's under your control. The external messaging system is responsible for generating NDRs for unresolved recipients. Use this value to treat messages that are sent to the domain as internal messages. - -- ExternalRelay: This is a type of non-authoritative domain that's available only in on-premises Exchange organizations. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external messaging system that's completely outside of your control. The external messaging system is responsible for generating NDRs for unresolved recipients. - -Note: - -For the value InternalRelay or ExternalRelay you typically use mail users or mail contacts to relay the messages to the external messaging system. Address rewriting is also available on Edge Transport servers in on-premises Exchange organizations. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MakeDefault -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. - -- $true: The accepted domain is the default domain. This is the default value for first accepted domain that's created in the organization. - -- $false: The accepted domain isn't the default domain. This the default value for subsequent accepted domains. - -The default accepted domain is used in sender email addresses when the senders have only non-SMTP email addresses (for example, X.400 addresses). Non-SMTP email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. IMCEA encapsulation uses the default domain value in the SMTP email address. - -If you don't use non-SMTP email addresses in your organization, you don't need to worry about the value of this 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 ("). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutboundOnly -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. - -The authoritative accepted domain for the on-premises deployment is configured as an internal relay accepted domain on the cloud side. If the on-premises deployment is using Exchange Online Protection, you need to set this parameter to $true for the accepted domain that represents your on-premises deployment. This parameter is used only if the DomainType parameter is set to Authoritative or InternalRelay. The default value is $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PendingRemoval -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, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableNego2Authentication -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MatchSubDomains -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 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PendingCompletion -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mail-flow/Set-InboundConnector.md b/exchange/exchange-ps/exchange/mail-flow/Set-InboundConnector.md deleted file mode 100644 index 7f51024b49..0000000000 --- a/exchange/exchange-ps/exchange/mail-flow/Set-InboundConnector.md +++ /dev/null @@ -1,512 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/set-inboundconnector -applicable: Exchange Online, Exchange Online Protection -title: Set-InboundConnector -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Set-InboundConnector - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-InboundConnector cmdlet to change an existing Inbound connector in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-InboundConnector [-Identity] <InboundConnectorIdParameter> - [-AssociatedAcceptedDomains <MultiValuedProperty>] - [-CloudServicesMailEnabled <Boolean>] - [-Comment <String>] - [-Confirm] - [-ConnectorSource <TenantConnectorSource>] - [-ConnectorType <TenantConnectorType>] - [-EFSkipIPs <MultiValuedProperty>] - [-EFSkipLastIP <Boolean>] - [-EFSkipMailGateway <MultiValuedProperty>] - [-EFTestMode <Boolean>] - [-EFUsers <MultiValuedProperty>] - [-Enabled <Boolean>] - [-Name <String>] - [-RequireTls <Boolean>] - [-RestrictDomainsToCertificate <Boolean>] - [-RestrictDomainsToIPAddresses <Boolean>] - [-ScanAndDropRecipients <MultiValuedProperty>] - [-SenderDomains <MultiValuedProperty>] - [-SenderIPAddresses <MultiValuedProperty>] - [-TlsSenderCertificateName <TlsCertificate>] - [-TreatMessagesAsInternal <Boolean>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Inbound connectors accept email messages from remote domains that require specific configuration options. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-InboundConnector "Contoso Inbound Connector" -RequireTls $true -TlsSenderCertificateName contoso.com -``` - -This example makes the following configuration changes to the existing Inbound connector named Contoso.com Inbound Connector. - -Require TLS transmission for all incoming messages on the connector. - -Require that the TLS certificate that is used to encrypt communications contain the domain name contoso.com - -## PARAMETERS - -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AssociatedAcceptedDomains -The AssociatedAcceptedDomains parameter specifies the accepted domains that the connector applies to, thereby limiting its scope. For example, you can apply the connector to a specific accepted domain in your organization, such as contoso.com. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CloudServicesMailEnabled -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://docs.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 Office 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. - -Valid values are: - -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - -- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorSource -The ConnectorSource parameter specifies how the connector was created. Valid input for this parameter includes the following values: - -- Default: The connector is manually created. - -- HybridWizard: The connector is created automatically by the Hybrid Configuration Wizard. - -- Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. - -The default value for connectors you create is Default. It isn't recommended that you change this value. - -```yaml -Type: TenantConnectorSource -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorType -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. - -- OnPremises: The connector services domains that are used by your on-premises organization. Use this value for accepted domains in your cloud-based organization that are also specified by the SenderDomains parameter. - -```yaml -Type: TenantConnectorType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFSkipIPs -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: - -- A single IP address: For example, 192.168.1.1. - -- An IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.3.1/24 - -You can specify multiple IP addresses or address range entries separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFSkipLastIP -The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are: - -- $true: Only the last message source is skipped. - -- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFSkipMailGateway -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFTestMode -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EFUsers -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter enables or disables the connector. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireTls -The RequireTLS parameter specifies that all messages received by this connector require TLS transmission. Valid values for this parameter are $true or $false. The default value is $false. When the RequireTLS parameter is set to $true, all messages received by this connector require TLS transmission. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictDomainsToCertificate -The RestrictDomainsToCertificate parameter specifies that Office 365 should identify incoming messages that are eligible for this connector by verifying that the remote server authenticates using a TLS certificate that has the TlsSenderCertificateName in the Subject. Valid values are $true or $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictDomainsToIPAddresses -The RestrictDomainsToIPAddresses parameter, when set to $true, automatically rejects mail from the domains specified by the SenderDomains parameter if the mail originates from an IP address that isn't specified by the SenderIPAddresses parameter. - -Valid input for this parameter is $true or $false. The default value is $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScanAndDropRecipients -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderDomains -The SenderDomains parameter specifies the remote domains from which this connector accepts messages, thereby limiting its scope. 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. - -You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderIPAddresses -The SenderIPAddresses parameter specifies the remote IP addresses from which this connector accepts messages. You enter the IP addresses using the following syntax: - -- Single IP: For example, 192.168.1.1. - -- CIDR IP: You can use Classless InterDomain Routing (CIDR). For example, 192.168.0.1/25. - -You can specify multiple IP addresses separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TlsSenderCertificateName -The TlsSenderCertificateName parameter specifies the certificate used by the sender's domain when the RequireTls parameter is set to $true. Valid input for the TlsSenderCertificateName 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. - -You can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. - -```yaml -Type: TlsCertificate -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TreatMessagesAsInternal -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 Office 365. This setting allows internal mail flow between Office 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. - -- $false: Messages aren't considered internal. This is the default value. - -In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Office 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mail-flow/Start-HistoricalSearch.md b/exchange/exchange-ps/exchange/mail-flow/Start-HistoricalSearch.md deleted file mode 100644 index a63a722aac..0000000000 --- a/exchange/exchange-ps/exchange/mail-flow/Start-HistoricalSearch.md +++ /dev/null @@ -1,355 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mail-flow/start-historicalsearch -applicable: Exchange Online, Exchange Online Protection -title: Start-HistoricalSearch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Start-HistoricalSearch - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Start-HistoricalSearch cmdlet to start a new historical search. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Start-HistoricalSearch -EndDate <DateTime> -ReportTitle <String> -ReportType <HistoricalSearchReportType> - -StartDate <DateTime> [-DeliveryStatus <String>] - [-Direction <MessageDirection>] - [-DLPPolicy <MultiValuedProperty>] - [-Locale <CultureInfo>] - [-MessageID <MultiValuedProperty>] - [-NotifyAddress <MultiValuedProperty>] - [-OriginalClientIP <String>] - [-RecipientAddress <MultiValuedProperty>] - [-SenderAddress <MultiValuedProperty>] - [-TransportRule <MultiValuedProperty>] - [<CommonParameters>] -``` - -## DESCRIPTION -A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are aged between 1-4 hours (depending on your environment) and 90 days old. There is a limit of 250 historical searches that you can submit in a 24 hour period; you'll be warned if you're nearing the daily quota. Cancelled searches count against the daily quota. Also, in each CSV file there is a limit of 50000 results or lines. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Start-HistoricalSearch -ReportTitle "Fabrikam Search" -StartDate 1/1/2018 -EndDate 1/7/2018 -ReportType MessageTrace -SenderAddress michelle@fabrikam.com -NotifyAddress chris@contoso.com -``` - -This example starts a new historical search named "Fabrikam Search" that has the following properties: - -- Date range: January 1, 2018 to January 7, 2018 - -- Report type: Message trace - -- Sender address: michelle@fabrikam.com - -- Internal notification email address: chris@contoso.com - -## PARAMETERS - -### -EndDate -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". - -You also need to specify at least one of the following values in the command: MessageID, RecipientAddress, or SenderAddress. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ReportTitle -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 specify at least one of the following values in the command: MessageID, RecipientAddress, or SenderAddress. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter specifies the type of historical search that you want to perform. You can use one of the following values: - -- ATPReport: Advanced Threat Protection File Types Report and Advanced Threat Protection Message Disposition Report - -- ATPV2: Exchange Online Protection and Advanced Threat Protection E-mail Malware Report. - -- ATPDocument: Advanced Threat Protection Content Malware Report for files in SharePoint, OneDrive and Microsoft Teams. - -- DLP: Data Loss Prevention Report. - -- Malware: Malware Detections Report. - -- MessageTrace: Message Trace Report. - -- MessageTraceDetail: Message Trace Details Report. - -- Phish: Exchange Online Protection and Advanced Threat Protection E-mail Phish Report. - -- SPAM: SPAM Detections Report. - -- Spoof: Spoof Mail Report. - -- TransportRule: Transport or Mail FLow Rules Report. - -- UnifiedDLP: Unified Data Loss Prevention Report. - -You also need to specify at least one of the following values in the command: MessageID, RecipientAddress, or SenderAddress. - -```yaml -Type: HistoricalSearchReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DeliveryStatus -The DeliveryStatus parameter filters the results by the delivery status of the message. You can use one of the following values: - -- Delivered - -- Expanded - -- Failed - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by the direction of the message. Valid values are: - -- All: Incoming and outgoing messages. - -- Received: Ingoing messages only. - -- Sent: Outgoing messages only. - -```yaml -Type: MessageDirection -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DLPPolicy -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Locale -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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageID -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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyAddress -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -OriginalClientIP -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: True -``` - -### -SenderAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TransportRule -The TransportRule parameter filters the results by the name of the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailbox-databases-and-servers/Remove-MailboxRepairRequest.md b/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-MailboxRepairRequest.md deleted file mode 100644 index 2f5c0735e1..0000000000 --- a/exchange/exchange-ps/exchange/mailbox-databases-and-servers/Remove-MailboxRepairRequest.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailbox-databases-and-servers/remove-mailboxrepairrequest -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-MailboxRepairRequest -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Remove-MailboxRepairRequest - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Remove-MailboxRepairRequest cmdlet to remove mailbox repair requests from a mailbox database that were created using the New-MailboxRepairRequest cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-MailboxRepairRequest [-Identity] <StoreIntegrityCheckJobIdParameter> [-Confirm] - [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You can run the Remove-MailboxRepairRequest cmdlet to remove all mailbox repair requests for a specific database, for a group of related mailbox repair requests, or for a specific mailbox repair request. Mailbox repair requests are identified by a complex GUID with the following format: \<DatabaseGuid\>\\\<RequestGuid\>\\\<JobGuid\>. The DatabaseGuid identifies the mailbox database where the mailbox being repaired is located. The RequestGuid identifies related requests that may contain more than one job if the request runs more than one task or targets more than one mailbox. The JobGuid identifies a unique job. See the examples to remove all requests on a mailbox database, remove a group of related requests that share the same RequestGuid, or remove a specific request by specifying the complete \<DatabaseGuid\>\\\<RequestGuid\>\\\<JobGuid\> value. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxDatabase -Identity "EXCH-MBX-01" | Get-MailboxRepairRequest | Remove-MailboxRepairRequest -``` - -This example removes all mailbox repair requests for the mailbox database EXCH-MBX-01. - -### Example 2 -```powershell -Get-MailboxDatabase -Identity "EXCH-MBX-02" | Get-MailboxRepairRequest | Format-List Identity; Remove-MailboxRepairRequest -Identity 5b8ca3fa-8227-427f-af04-9b4f206d611f\335c2b06-321d-4e73-b2f7-3dc2b02d0df5 -``` - -This example removes all related mailbox repair requests that have the same \<DatabaseGuid\>\\\<RequestGuid\>. The example uses the Get-MailboxRepairRequest cmdlet to display the value of the Identity parameter for all mailbox repair request for EXCH-MBX-02 mailbox database. - -### Example 3 -```powershell -Get-MailboxDatabase -Identity "EXCH-MBX-02" | Get-MailboxRepairRequest | Format-List Identity; Remove-MailboxRepairRequest -Identity 5b8ca3fa-8227-427f-af04-9b4f206d611f\189c7852-49bd-4737-a53e-6e6caa5a183c\1d8ca58a-186f-4dc6-b481-f835b548a929 -``` - -This example deletes a specific mailbox repair request by specifying the unique \<DatabaseGuid\>\\\<RequestGuid\>\\\<JobGuid\> identity value. The example also uses the Get-MailboxRepairRequest cmdlet to display the identities of all mailbox repair request for the EXCH-MBX-02 mailbox database. - -## PARAMETERS - -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Add-MailboxPermission.md b/exchange/exchange-ps/exchange/mailboxes/Add-MailboxPermission.md deleted file mode 100644 index aa31aa2b18..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Add-MailboxPermission.md +++ /dev/null @@ -1,423 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Add-MailboxPermission - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Add-MailboxPermission cmdlet to add permissions to a mailbox or to an Exchange Server 2016, Exchange Server 2019, or Exchange Online mail user. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AccessRights -``` -Add-MailboxPermission [-Identity] <MailboxIdParameter> -AccessRights <MailboxRights[]> -User <SecurityPrincipalIdParameter> - [-AutoMapping <Boolean>] - [-Confirm] - [-Deny] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-InheritanceType <ActiveDirectorySecurityInheritance>] - [-WhatIf] [<CommonParameters>] -``` - -### Owner -``` -Add-MailboxPermission [-Identity] <MailboxIdParameter> -Owner <SecurityPrincipalIdParameter> - [-Confirm] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-WhatIf] [<CommonParameters>] -``` - -### Instance -``` -Add-MailboxPermission -Instance <MailboxAcePresentationObject> - [-AccessRights <MailboxRights[]>] - [-User <SecurityPrincipalIdParameter>] - [-AutoMapping <Boolean>] - [-Confirm] - [-Deny] - [-DomainController <Fqdn>] - [[-Identity] <MailboxIdParameter>] - [-IgnoreDefaultScope] - [-InheritanceType <ActiveDirectorySecurityInheritance>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the mailbox object that's specified by the Identity parameter. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Add-MailboxPermission -Identity "Terry Adams" -User "Kevin Kelly" -AccessRights FullAccess -InheritanceType All -``` - -This example assigns the user Kevin Kelly Full Access permission to Terry Adams's mailbox. - -### Example 2 -```powershell -Add-MailboxPermission -Identity "Room 222" -Owner "Tony Smith" -``` - -This example sets the user Tony Smith as the owner of the resource mailbox named Room 222. - -### Example 3 -```powershell -Add-MailboxPermission -Identity "Jeroen Cool" -User "Mark Steele" -AccessRights FullAccess -InheritanceType All -AutoMapping $false -``` - -This example assigns the user Mark Steele Full Access permission to Jeroen Cool's mailbox, prevents Outlook from opening Jeroen Cool's mailbox when Mark Steele opens Outlook. - -### Example 4 -```powershell -Get-Mailbox -ResultSize unlimited -Filter "(RecipientTypeDetails -eq 'UserMailbox') -and (Alias -ne 'Admin')" | Add-MailboxPermission -User admin@contoso.com -AccessRights FullAccess -InheritanceType All -``` - -In Office 365, this example assigns the administrator account admin@contoso.com Full Access permission to all user mailboxes in the contoso.com Office 365 organization. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: AccessRights, Owner -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -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 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AccessRights -The AccessRights parameter specifies the permission that you want to assign to the user on the mailbox. Valid values are: - -- ChangeOwner - -- ChangePermission - -- DeleteItem - -- ExternalAccount - -- FullAccess - -- ReadPermission - -You can specify multiple values separated by commas. - -```yaml -Type: MailboxRights[] -Parameter Sets: AccessRights -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -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 -``` - -### -Instance -This parameter has been deprecated and is no longer used. - -```yaml -Type: MailboxAcePresentationObject -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Owner -The Owner parameter specifies the owner of the mailbox object. The default mailbox owner is NT AUTHORITY\\SELF. - -The owner 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 owner. For example: For example: - -- Name - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -The User parameter specifies the user that you're assigning the permission to. - -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: For example: - -- Name - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: AccessRights -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoMapping -The AutoMapping parameter specifies whether to enable or disable the auto-mapping feature in Microsoft Outlook that uses Autodiscover to automatically open other mailboxes for the user. Valid values are: - -- $true: Outlook automatically opens the mailbox where the user is assigned Full Access permission. This is the default value. - -- $false: Outlook doesn't automatically open the mailbox where the user is assigned Full Access permission. - -If you've already assign the user Full Access to the mailbox, and you want to prevent the mailbox from automatically opening in the user's Outlook, you need to remove the user's Full Access permission by using the Remove-MailboxPermission cmdlet, and then assign the permission to the user on the mailbox again, but this time include -AutoMapping $false in the command. - -```yaml -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 -Default value: $true -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Deny -The Deny switch specifies whether to deny the specified permissions to the user on the mailbox. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InheritanceType -The InheritanceType parameter specifies how permissions are inherited by folders in the mailbox. Valid values are: - -- All - -- Children - -- Descendents[sic] - -- SelfAndChildren - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Add-RecipientPermission.md b/exchange/exchange-ps/exchange/mailboxes/Add-RecipientPermission.md deleted file mode 100644 index 816b9671d0..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Add-RecipientPermission.md +++ /dev/null @@ -1,251 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/add-recipientpermission -applicable: Exchange Online -title: Add-RecipientPermission -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Add-RecipientPermission - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Add-RecipientPermission cmdlet to add SendAs permission to users in a cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Add-RecipientPermission [-Identity] <RecipientIdParameter> -AccessRights <MultiValuedProperty> - -Trustee <SecurityPrincipalIdParameter> [-SkipDomainValidationForMailContact] [-SkipDomainValidationForMailUser] [-SkipDomainValidationForSharedMailbox] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -SendAs permission allows a user or group members to send messages that appear to come from the specified mailbox, mail contact, mail user, or group. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Add-RecipientPermission "Help Desk" -AccessRights SendAs -Trustee "Ayla Kol" -``` - -This example gives the user Ayla Kol SendAs permission for the mailbox Help Desk. Ayla can send messages that appear to come directly from the Help Desk mailbox. - -## PARAMETERS - -### -AccessRights -The AccessRights parameter specifies the permission. The only value for this parameter is SendAs. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -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: - -- Mailboxes - -- Mail users - -- External contacts - -- Distribution groups - -- Dynamic distribution groups - -You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Trustee -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 - -- Mail users with a Microsoft account (formerly known as a Windows Live ID) - -- Security groups - -You can use any value that uniquely identifies the user or group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -SkipDomainValidationForMailContact -The SkipDomainValidationForMailContact switch skips the check that confirms the proxy addresses of the external contact specified by the Identity parameter are in the accepted domains 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipDomainValidationForMailUser -The SkipDomainValidationForMailUser switch skips the check that confirms the proxy addresses of the mail user specified by the Identity parameter are in the accepted domains 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipDomainValidationForSharedMailbox -The SkipDomainValidationForSharedMailbox switch skips the check that confirms the proxy addresses of the shared mailbox specified by the Identity parameter are in the accepted domains 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticAnalysis.md deleted file mode 100644 index 2e952247bb..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticAnalysis.md +++ /dev/null @@ -1,220 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-calendardiagnosticanalysis -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-CalendarDiagnosticAnalysis -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-CalendarDiagnosticAnalysis - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Get-CalendarDiagnosticAnalysis cmdlet to troubleshoot calendar-related reliability issues. You can use this cmdlet to analyze calendar item data that's recorded in the Calendar Diagnostic logs. You provide the calendar item data to this cmdlet by using the Get-CalendarDiagnosticLog cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### DefaultSet -``` -Get-CalendarDiagnosticAnalysis -CalendarLogs <CalendarLog[]> - [-DetailLevel <AnalysisDetailLevel>] - [-GlobalObjectId <String>] - [-OutputAs <OutputType>] - [<CommonParameters>] -``` - -### LocationSet -``` -Get-CalendarDiagnosticAnalysis -LogLocation <String[]> - [-DetailLevel <AnalysisDetailLevel>] - [-GlobalObjectId <String>] - [-OutputAs <OutputType>] - [<CommonParameters>] -``` - -## DESCRIPTION -The following properties of the calendar item are returned in the default output of the cmdlet (when the DetailLevel parameter is set to Basic): - -- Local Log Time - -- ItemId - -- NormalizedSubject - -- StartTime - -- EndTime - -- CalendarLogTriggerAction - -- ClientInfoString - -- OriginalLastModifiedTime - -- ClientIntent - -- CleanGlobalObjectId - -- ItemClass - -- ParentDisplay - -- Duration - -- AppointmentRecurring - -- SentRepresentingEmailAddress - -- SenderEmailAddress - -- SentRepresentingDisplayName - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -$logs = Get-CalendarDiagnosticLog -Identity oevans -MeetingID 040000008200E00074C5B7101A82E008000000009421DCCD5046CD0100000000000000001000000010B0349F6B17454685E17D9F9512E71F; Get-CalendarDiagnosticAnalysis -CalendarLogs $logs -DetailLevel Advanced | Set-Content -Path "C:\My Documents\Oscar Evans Analysis.csv" -``` - -This example gets the specified calendar item from Oscar Evans' mailbox, stores the item as a variable and writes the advanced analysis of the item to a CSV file. - -For basic analysis of the item, don't include the DetailLevel parameter, or use the value Basic instead of Advanced. - -### Example 2 -```powershell -Get-CalendarDiagnosticAnalysis -LogLocation "C:\My Documents\Exported Calendar Logs\jkozma@contoso.com" -DetailLevel Advanced -OutputAs HTML | Set-Content -Path "C:\My Documents\Jasen Kozma Analysis.html" -``` - -This example analyzes the calendar items that were exported from Jasen Kozma's mailbox by using the Get-CalendarDiagnosticLog cmdlet with the LogLocation parameter and writes the advanced analysis of the items to an HTML file. - -For basic analysis of the items, don't include the DetailLevel parameter, or use the value Basic instead of Advanced. - -## PARAMETERS - -### -CalendarLogs -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. - -Note that you can't use this parameter to analyze multiple calendar items. The value that you use for this parameter must identify a single item. - -You can't use this parameter with the LogLocation parameter. - -```yaml -Type: CalendarLog[] -Parameter Sets: DefaultSet -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogLocation -The LogLocation parameter specifies the location of the exported calendar items that you want to analyze. You can specify a local path, or a UNC path (\\\\\<Server\>\\\<Share\>\\\<User\>). If the value contains spaces, enclose the value in quotation marks ("). - -You export the calendar items to .msg files by using the Get-CalendarDiagnosticLog cmdlet with the LogLocation parameter. If the path contains multiple .msg files, all of those files are analyzed when you run Get-CalendarDiagnosticAnalysis. - -You can't use this parameter with the CalendarLogs parameter. - -```yaml -Type: String[] -Parameter Sets: LocationSet -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DetailLevel -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. - -- Advanced: 37 additional calendar item properties are returned. You should use this value only for detailed debugging information. - -```yaml -Type: AnalysisDetailLevel -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GlobalObjectId -The GlobalObjectId parameter specifies the identity of the calendar item you want to analyze. 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). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputAs -The OutputAs parameter specifies the output format of the command. Valid values are: - -- CSV (This is the default value) - -- HTML - -- XML - -```yaml -Type: OutputType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-CalendarDiagnosticObjects.md b/exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticObjects.md deleted file mode 100644 index b72b19d5f9..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticObjects.md +++ /dev/null @@ -1,392 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-calendardiagnosticobjects -applicable: Exchange Online -title: Get-CalendarDiagnosticObjects -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CalendarDiagnosticObjects - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-CalendarDiagnosticObjects cmdlet to collect a range of calendar logs. The calendar diagnostic logs track important calendar-related event data for each mailbox, and can be used to troubleshoot calendar issues that occur in mailboxes. The logs track all calendar items and meeting messages. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CalendarDiagnosticObjects [-Identity] <UnifiedGroupOrUserMailboxIdParameter> - [-CustomPropertyNames <String[]>] - [-DomainController <Fqdn>] - [-EndDate <ExDateTime>] - [-EntryId <String>] - [-ExactMatch <Boolean>] - [-ItemClass <String[]>] - [-ItemIds <String[]>] - [-MeetingId <String>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-ShouldBindToItem <Boolean>] - [-ShouldFetchRecurrenceExceptions <Boolean>] - [-StartDate <ExDateTime>] - [-Subject <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Some of the more interesting properties that are returned in the results are: - -- AppointmentState: 1 = The appointment is a meeting, 2 = The appointment has been received, 4 = The appointment has been cancelled, and 8 = the appointment is a forwarded appointment. - -- CalendarLogTriggerAction: The action that's taken on the item (for example, Create or Update). - -- ClientInfoString: The entity that made the change (for example, Client=OWA;\<AdditionalDetails\>, Client=WebServices;\<AdditionalDetails\>;, or Client=TBA;Service=MSExchangeMailboxAssistants;Action=ELCAssistant;). - -- MeetingRequestType: 1 = The meeting message is a meeting request, 65536 = The meeting message is a full update to an existing meeting, 131072 = The meeting message is an informational update to an existing meeting, 262144 = The meeting message is a silent update, 524288 = The update is outdated, or 1048576 = The meeting message is forwarded to a delegate, and the copy is marked as informational. - -- OriginalLastModifiedTime: Used as the primary sort field to order the events. - -- ResponseType: 0 = The organizer hasn't received a response, 1 = The organizer's copy of the meeting, 2 = Tentative, 3 = Accept, 4 = Decline, or 5 = The attendee hasn't responded. - -- ResponsibleUserName: The LegacyExchangeDN value of the user who made the change (for example, /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BN6PR11MB1587/cn=Microsoft System Attendant or /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=696eea97d3c449eab648920d03385efb-admin). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -Subject "Team Meeting" -ExactMatch $true -``` - -This example retrieves the calendar diagnostic logs from Pedro Pizarro's mailbox for all items where the Subject is an exact match for Team Meeting. - -### Example 2 -```powershell -$A = Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -Subject "Team Meeting" -ExactMatch $true; $A | Select-Object *,@{n='OLMT'; e={[DateTime]::Parse($_.OriginalLastModifiedTime.ToString())}} | sort OLMT | Format-Table OriginalLastModifiedTime,CalendarLogTriggerAction,ItemClass,ClientInfoString -``` - -This is the same as the previous example, but now the results are sorted by original last modified time. - -### Example 3 -```powershell -Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -MeetingID 40000008200E00074C5B7101A82E00800000000693ADAA3B5FCD201000000000000000010000000FF760A70460EAA4096B879872DF24F49 -``` - -This example retrieves the calendar diagnostic logs for Pedro Pizarro's mailbox for a meeting with the specified unique global object ID (GOID). - -### Example 4 -```powershell -Get-CalendarDiagnosticObjects -Identity "Pedro Pizarro" -Subject "Team Lunch" -StartDate 7/1/2018 -EndDate 7/31/2018 | Export-Csv "C:\My Documents\Team Lunch Meeting.csv" -NoTypeInformation -``` - -This example returns diagnostic information for meetings with the subject Team Lunch in Pedro Pizarro's mailbox in the month of July, 2018, and exports the results to the file C:\\My Documents\\Team Lunch Meeting.csv. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox or Office 365 Group whose calendar you want to view. You can use any value that uniquely identifies the mailbox or Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: UnifiedGroupOrUserMailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -CustomPropertyNames -The CustomPropertyNames parameter returns the specified calendar item custom property in the results. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: ExDateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EntryId -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExactMatch -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". - -- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This is the default value. - -A partial subject match search may not return all of the relevant calendar items. Try using an exact subject match search for more accurate results. - -You only use this parameter with the Subject parameter. - -The value of this parameter is ignored when you use the MeetingId parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ItemClass -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ItemIds -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MeetingId -The MeetingId parameter filters the results by the globally unique identifier of the calendar item. The value is the CleanGlobalObjectId property of the calendar item that's available in the output of this cmdlet, or by using other MAPI examination tools. An example value is 040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55. This value is constant throughout the lifetime of the calendar item. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShouldBindToItem -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. - -- $false: The values of large streamable properties are truncated. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShouldFetchRecurrenceExceptions -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. - -- $false: Don't Include exceptions to recurring meetings. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: ExDateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Subject -The Subject parameter identifies the calendar items by the specified text in the Subject field. The text values that you specify aren't case sensitive. If the value contains spaces, enclose the value in quotation marks. You can control whether to use exact matching by using the ExactMatch parameter - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-CalendarNotification.md b/exchange/exchange-ps/exchange/mailboxes/Get-CalendarNotification.md deleted file mode 100644 index 59c78ac997..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-CalendarNotification.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-calendarnotification -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-CalendarNotification -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-CalendarNotification - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-CalendarNotification cmdlet to return a list of all calendar notification settings for a user. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CalendarNotification [-Identity] <MailboxIdParameter> [-Credential <PSCredential>] - [-DomainController <Fqdn>] [-ReadFromDomainController] [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CalendarNotification cmdlet retrieves and displays the rules used to trigger the calendar agenda notification, reminder notification, or update notification. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CalendarNotification -Identity "TonySmith" -``` - -This example returns the calendar notification settings for the user Tony Smith using the user's alias. - -### Example 2 -```powershell -Get-CalendarNotification -Identity tony@contoso.com -ReadFromDomainController -``` - -This example returns the calendar notification settings for the user Tony Smith. - -### Example 3 -```powershell -Get-CalendarNotification -Identity "contoso\tonysmith" -``` - -This example returns the calendar notification settings for the user Tony Smith using the user's domain and name. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -The ReadFromDomainController parameter specifies whether the command should return data from the domain controller. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the amount of data returned. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-Clutter.md b/exchange/exchange-ps/exchange/mailboxes/Get-Clutter.md deleted file mode 100644 index c89dda7a92..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-Clutter.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-clutter -applicable: Exchange Online -title: Get-Clutter -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-Clutter - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-Clutter cmdlet to view Clutter settings for mailboxes in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-Clutter -Identity <MailboxIdParameter> [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-Clutter -Identity "Constancia Pena" -``` - -This example returns the Clutter settings for the user Constancia Pena. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name>\\\<account name> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-FocusedInbox.md b/exchange/exchange-ps/exchange/mailboxes/Get-FocusedInbox.md deleted file mode 100644 index 112d814658..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-FocusedInbox.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-focusedinbox -applicable: Exchange Online -title: Get-FocusedInbox -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-FocusedInbox - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-FocusedInbox cmdlet to view the Focused Inbox configuration for mailboxes in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-FocusedInbox -Identity <MailboxIdParameter> [<CommonParameters>] -``` - -## DESCRIPTION -Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-FocusedInbox -Identity julia@contoso.com -``` - -This example returns the Focused Inbox configuration for the mailbox of julia@contoso.com. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name>\\\<account name> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-Mailbox.md b/exchange/exchange-ps/exchange/mailboxes/Get-Mailbox.md deleted file mode 100644 index 8fc8660076..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-Mailbox.md +++ /dev/null @@ -1,850 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-Mailbox - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-Mailbox cmdlet to view mailbox objects and attributes, populate property pages, or supply mailbox information to other tasks. - -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXOMailbox cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnrSet -``` -Get-Mailbox [-Anr <String>] - [-Arbitration] - [-Archive] - [-AuditLog] - [-AuxAuditLog] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-InactiveMailboxOnly] - [-IncludeInactiveMailbox] - [-Migration] - [-Monitoring] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-RemoteArchive] - [-ResultSize <Unlimited>] - [-SoftDeletedMailbox] - [-SortBy <String>] - [<CommonParameters>] -``` - -### DatabaseSet -``` -Get-Mailbox [-Database <DatabaseIdParameter>] - [-Arbitration] - [-Archive] - [-AuditLog] - [-AuxAuditLog] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-Migration] - [-Monitoring] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-RemoteArchive] - [-ResultSize <Unlimited>] - [-SortBy <String>] - [<CommonParameters>] -``` - -### Identity -``` -Get-Mailbox [[-Identity] <MailboxIdParameter>] - [-Arbitration] - [-Archive] - [-AuditLog] - [-AuxAuditLog] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-InactiveMailboxOnly] - [-IncludeInactiveMailbox] - [-Migration] - [-Monitoring] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-RemoteArchive] - [-ResultSize <Unlimited>] - [-SoftDeletedMailbox] - [-SortBy <String>] - [<CommonParameters>] -``` - -### ServerSet -``` -Get-Mailbox [-Server <ServerIdParameter>] - [-Arbitration] - [-Archive] - [-AuditLog] - [-AuxAuditLog] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-Migration] - [-Monitoring] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-RemoteArchive] - [-ResultSize <Unlimited>] - [-SortBy <String>] - [<CommonParameters>] -``` - -### MailboxPlanSet -``` -Get-Mailbox [-MailboxPlan <MailboxPlanIdParameter>] - [-Archive] - [-Filter <String>] - [-GroupMailbox] - [-InactiveMailboxOnly] - [-IncludeInactiveMailbox] - [-Migration] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SoftDeletedMailbox] - [-SortBy <String>] [<CommonParameters>] -``` - -### AsyncParameterSet -``` -Get-Mailbox -Async -Properties <String[]> - [-Archive] - [-Filter <String>] - [-GroupMailbox] - [-InactiveMailboxOnly] - [-IncludeInactiveMailbox] - [-Migration] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SoftDeletedMailbox] - [-SortBy <String>] [<CommonParameters>] -``` - -## DESCRIPTION -When you use the Get-Mailbox cmdlet in on-premises Exchange environments to view the quota settings for a mailbox, you first need to check the value of the UseDatabaseQuotaDefaults property. The value True means per-mailbox quota settings are ignored, and you need to use the Get-MailboxDatabase cmdlet to see the actual values. If the UseDatabaseQuotaDefaults property is False, the per-mailbox quota settings are used, so what you see with the Get-Mailbox cmdlet are the actual quota values for the mailbox. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-Mailbox -ResultSize unlimited -``` - -This example returns a summary list of all the mailboxes in your organization. - -### Example 2 -```powershell -Get-Mailbox -OrganizationalUnit Users -``` - -This example returns a list of all the mailboxes in your organization in the Users OU. - -### Example 3 -```powershell -Get-Mailbox -Anr Chr -``` - -This example returns all the mailboxes that resolve from the ambiguous name resolution search on the string "Chr". This example returns mailboxes for users such as Chris Ashton, Christian Hess, and Christa Geller. - -### Example 4 -```powershell -Get-Mailbox -Archive -Server Mailbox01 -``` - -This example returns a summary list of all archive mailboxes on the Mailbox server named Mailbox01. - -### Example 5 -```powershell -Get-Mailbox -Identity ed@contoso.com -RemoteArchive -``` - -This example returns information about the remote archive mailbox for the user ed@contoso.com. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Arbitration -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. - -Arbitration mailboxes are system mailboxes that are used for storing different types of system data and for managing messaging approval workflow. - -To return arbitration mailboxes that are used to store audit log settings or data, don't use this switch. Instead, use the AuditLog or AuxAuditLog switches. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Archive -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 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 -``` - -### -Async -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: AsyncParameterSet -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuditLog -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. - -Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. - -To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. - -```yaml -Type: SwitchParameter -Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuxAuditLog -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. - -Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. - -To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. - -```yaml -Type: SwitchParameter -Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -This parameter is available only in on-premises Exchange. - -The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. - -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -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: - -- Name - -- Distinguished name (DN) - -- GUID - -You can't use this parameter with the Anr, Identity, or Server parameters. - -```yaml -Type: DatabaseIdParameter -Parameter Sets: DatabaseSet -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupMailbox -The GroupMailbox switch is required to return Office 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -You can't use this parameter with the Anr, Database, MailboxPlan or Server parameters. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InactiveMailboxOnly -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. - -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. - -To include active and inactive mailboxes in the results, don't use this switch. Instead, use the IncludeInactiveMailbox switch. - -```yaml -Type: SwitchParameter -Parameter Sets: AnrSet, Identity, MailboxPlanSet, AsyncParameterSet -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeInactiveMailbox -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. - -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. - -To return only inactive mailboxes in the results, don't use this switch. Instead, use the InactiveMailboxOnly switch. - -```yaml -Type: SwitchParameter -Parameter Sets: AnrSet, Identity, MailboxPlanSet, AsyncParameterSet -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxPlan -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: - -- Name - -- Alias - -- Display name - -- Distinguished name (DN) - -- GUID - -A mailbox plan specifies the permissions and features available to a mailbox user in cloud-based organizations. You can see the available mailbox plans by using the Get-MailboxPlan cmdlet. - -You can't use this parameter with the Anr or Identity parameters. - -```yaml -Type: MailboxPlanIdParameter -Parameter Sets: MailboxPlanSet -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Migration -The Migration switch is required to return 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Monitoring -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. - -Monitoring mailboxes are associated with managed availability and the Exchange Health Manager service, and have a RecipientTypeDetails property value of MonitoringMailbox. - -```yaml -Type: SwitchParameter -Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolder -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientTypeDetails -The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are: - -- DiscoveryMailbox - -- EquipmentMailbox - -- GroupMailbox - -- LegacyMailbox - -- LinkedMailbox - -- LinkedRoomMailbox - -- RoomMailbox - -- SchedulingMailbox - -- SharedMailbox - -- TeamMailbox - -- UserMailbox - -You can specify multiple values separated by commas. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteArchive -This parameter is available only in on-premises Exchange. - -The RemoteArchive switch is required to return remote archive mailboxes in the results. You don't need to specify a value with this switch. - -Remote archive mailboxes are archive mailboxes in the cloud-based service that are associated with mailbox users in on-premises Exchange organizations. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -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 -``` - -### -Server -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. - -You can use any value that uniquely identifies the server. For example: - -- Name - -- FQDN - -- Distinguished name (DN) - -- Exchange Legacy DN - -You can't use this parameter with the Anr, Database, or Identity parameters. - -The ServerName and ServerLegacyDN properties for a mailbox may not be updated immediately after a mailbox move within a database availability group (DAG). To get the most up-to-date values for these mailbox properties, run the command Get-Mailbox \<Identity\> | Get-MailboxStatistics | Format-List Name,ServerName,ServerLegacyDN. - -```yaml -Type: ServerIdParameter -Parameter Sets: ServerSet -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -SoftDeletedMailbox -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. - -Soft-deleted mailboxes are deleted mailboxes that are still recoverable. - -```yaml -Type: SwitchParameter -Parameter Sets: AnrSet, Identity, MailboxPlanSet, AsyncParameterSet -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- Alias - -- Office - -- ServerLegacyDN - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolderPermission.md deleted file mode 100644 index 03c2898e84..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolderPermission.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MailboxFolderPermission - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailboxFolderPermission cmdlet to view folder-level permissions in mailboxes. - -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxFolderPermission cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter> [-DomainController <Fqdn>] - [-User <MailboxFolderUserIdParameter>] [-GroupMailbox] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports -``` - -This example returns the current list of user permissions for the Reports subfolder in the Marketing folder in John's mailbox. - -### Example 2 -```powershell -Get-MailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports -User Ayla@contoso.com -``` - -This example returns the permissions for the same folder in John's mailbox, but only for the user Ayla. - -### Example 3 -```powershell -Get-MailboxFolderPermission -Identity john@contoso.com:\Calendar -User Ayla@contoso.com -``` - -This example returns the permissions for the Calendar folder in John's mailbox, but only for the user Ayla. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inbox\Reports`. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupMailbox -The GroupMailbox switch is required to return Office 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-MailboxFolderStatistics.md b/exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolderStatistics.md deleted file mode 100644 index 2c686f069f..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolderStatistics.md +++ /dev/null @@ -1,327 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MailboxFolderStatistics - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailboxFolderStatistics cmdlet to retrieve information about the folders in a specified mailbox, including the number and size of items in the folder, the folder name and ID, and other information. - -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxFolderStatistics cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity -``` -Get-MailboxFolderStatistics [-Identity] <GeneralMailboxOrMailUserIdParameter> [-Archive] [-DiagnosticInfo <String>] - [-DomainController <Fqdn>] [-FolderScope <Microsoft.Exchange.Data.Directory.SystemConfiguration.ElcFolderType>] - [-IncludeAnalysis] [-IncludeOldestAndNewestItems] [-IncludeSoftDeletedRecipients] [<CommonParameters>] -``` - -### AuditLog -``` -Get-MailboxFolderStatistics [-AuditLog] [-DomainController <Fqdn>] - [-FolderScope <Microsoft.Exchange.Data.Directory.SystemConfiguration.ElcFolderType>] - [[-Identity] <GeneralMailboxOrMailUserIdParameter>] [-IncludeAnalysis] - [-IncludeOldestAndNewestItems] [-DiagnosticInfo <String>] [-IncludeSoftDeletedRecipients] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -A mailbox can have hidden items that are never visible to the user and are only used by applications. The Get-MailboxFolderStatistics cmdlet can return hidden items for the following values: FolderSize, FolderAndSubfolderSize, ItemsInFolder and ItemsInFolderAndSubfolders. - -The Get-MailboxFolderStatistics cmdlet shouldn't be confused with the Get-MailboxStatistics cmdlet. - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxFolderStatistics -Identity contoso\chris -``` - -This example doesn't specify the FolderScope parameter and retrieves all the information about the user Chris in the Contoso domain. - -### Example 2 -```powershell -Get-MailboxFolderStatistics -Identity Chris -FolderScope Calendar -``` - -This example uses the FolderScope parameter to view the statistics for calendar folders for the user Chris. - -### Example 3 -```powershell -Get-MailboxFolderStatistics -Identity Ayla@contoso.com -Archive -``` - -This example uses the Archive switch to view the statistics for Ayla's archive. - -### Example 4 -```powershell -Get-MailboxFolderStatistics -Identity "Tony" -FolderScope RecoverableItems -IncludeAnalysis -``` - -This example uses the IncludeAnalysis switch to view the statistics of Tony's Recoverable Items folder. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -```yaml -Type: GeneralMailboxOrMailUserIdParameter -Parameter Sets: AuditLog -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Archive -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuditLog -This parameter is available only in on-premises Exchange. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: AuditLog -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiagnosticInfo -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FolderScope -The FolderScope parameter specifies the scope of the search by folder type. Valid parameter values include: - -- All - -- Archive - -- Calendar - -- Contacts - -- ConversationHistory - -- DeletedItems - -- Drafts - -- Inbox - -- JunkEmail - -- Journal - -- LegacyArchiveJournals - -- ManagedCustomFolder - -- NonIpmRoot - -- Notes - -- Outbox - -- Personal - -- RecoverableItems - -- RssSubscriptions - -- SentItems - -- SyncIssues - -- Tasks - -The ManagedCustomFolder value returns output for all managed custom folders. The RecoverableItems value returns output for the Recoverable Items folder and the Deletions, DiscoveryHolds, Purges, and Versions subfolders. - -```yaml -Type: Microsoft.Exchange.Data.Directory.SystemConfiguration.ElcFolderType -Parameter Sets: (All) -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 -``` - -### -IncludeAnalysis -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeOldestAndNewestItems -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeSoftDeletedRecipients -This parameter is available only in the cloud-based service. - -{{Fill IncludeSoftDeletedRecipients Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-MailboxPermission.md b/exchange/exchange-ps/exchange/mailboxes/Get-MailboxPermission.md deleted file mode 100644 index 4c2b1043f9..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-MailboxPermission.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MailboxPermission - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailboxPermission cmdlet to retrieve permissions on a mailbox. - -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXOMailboxPermission cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Owner -``` -Get-MailboxPermission [-Identity] <MailboxIdParameter> [-Owner] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -### AccessRights -``` -Get-MailboxPermission [-Identity] <MailboxIdParameter> [-User <SecurityPrincipalIdParameter>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -## DESCRIPTION -The output of this cmdlet shows the following information: - -- Identity: The mailbox in question. - -- User: The security principal (user, security group, Exchange management role group, etc.) that has permission to the mailbox. - -- AccessRights: The permission that the security principal has on the mailbox. The available values are ChangeOwner (change the owner of the mailbox), ChangePermission (change the permissions on the mailbox), DeleteItem (delete the mailbox), ExternalAccount (indicates the account isn't in the same domain), FullAccess (open the mailbox, access its contents, but can't send mail) and ReadPermission (read the permissions on the mailbox). Whether the permissions are allowed or denied is indicated in the Deny column. - -- IsInherited: Whether the permission is inherited (True) or directly assigned to the mailbox (False). Permissions are inherited from the mailbox database and/or Active Directory. Typically, directly assigned permissions override inherited permissions. - -- Deny: Whether the permission is allowed (False) or denied (True). Typically, deny permissions override allow permissions. - -By default, the following permissions are assigned to user mailboxes: - -- FullAccess and ReadPermission are directly assigned to NT AUTHORITY\\SELF. This entry gives a user permission to their own mailbox. - -- FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes. - -- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. - -- FullAccess is inherited by NT AUTHORITY\\SYSTEM and ReadPermission is inherited by NT AUTHORITY\\NETWORK. - -- FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers. - -By default, other security groups and role groups inherit permissions to mailboxes based on their location (on-premises Exchange or Office 365). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxPermission -Identity john@contoso.com | Format-List -``` - -This example returns permissions on the mailbox by its SMTP address john@contoso.com. - -### Example 2 -```powershell -Get-MailboxPermission -Identity john@contoso.com -User "Ayla" -``` - -This example returns permissions that the user Ayla has on John's mailbox. - -### Example 3 -```powershell -Get-MailboxPermission -Identity Room222 -Owner -``` - -This example returns the owner information for the resource mailbox Room222. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -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. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -The ReadFromDomainController parameter specifies that the user information is read from a domain controller in the user's domain. - -If you set the recipient scope to include all recipients in the forest, and if you don't use this parameter, it's possible that the user information is read from a global catalog with outdated information. - -If you use this parameter, multiple reads might be necessary to get the information. - -By default, the recipient scope is set to the domain that hosts your servers that run Exchange. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -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 -``` - -### -User -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: For example: - -- Name - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -You can't use this parameter with the Owner parameter. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-Place.md b/exchange/exchange-ps/exchange/mailboxes/Get-Place.md deleted file mode 100644 index 98f9da31a2..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-Place.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-place -applicable: Exchange Online -title: Get-Place -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-Place - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-Place cmdlet to view the additional metadata that was configured on room mailboxes by using the Set-Place cmdlet. The additional metadata provides a better search and room suggestion experience. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-Place [-Identity] <RecipientIdParameter> [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-Place -Identity "Conference Room 01" -``` - -This example returns summary metadata for the room mailbox named Conference Room 1. - -### Example 2 -```powershell -Get-Place -Identity "Conference Room 01" | Format-List -``` - -This example returns detailed metadata for Conference Room 1. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ResultSize -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Get-RecipientPermission.md b/exchange/exchange-ps/exchange/mailboxes/Get-RecipientPermission.md deleted file mode 100644 index 7ecbc65a20..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-RecipientPermission.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-recipientpermission -applicable: Exchange Online -title: Get-RecipientPermission -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-RecipientPermission - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-RecipientPermission cmdlet to view information about SendAs permissions that are configured for users in a cloud-based organization. - -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXORecipientPermission cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-RecipientPermission [[-Identity] <RecipientIdParameter>] [-AccessRights <MultiValuedProperty>] - [-ReadFromDomainController] [-ResultSize <Unlimited>] [-Trustee <SecurityPrincipalIdParameter>] - [<CommonParameters>] -``` - -## DESCRIPTION -When a user is given SendAs permission to another user or group, the user can send messages that appear to come from the other user or group. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-RecipientPermission -Trustee "Kim Akers" -``` - -This example lists the recipients for whom the user Kim Akers has SendAs permission. Kim can send messages that appear to come directly from the recipients. - -### Example 2 -```powershell -Get-RecipientPermission "Help Desk" -``` - -This example lists the users who have SendAs permission on the mailbox Help Desk. The users listed can send messages that appear to come directly from the Help Desk mailbox. - -## PARAMETERS - -### -AccessRights -The AccessRights parameter filters the results by permission. - -Valid input for this parameter is SendAs. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter filters the results by the target recipient. The user or group specified by the Trustee parameter can operate on this recipient. - -You can specify any type of recipient, for example: - -- Mailboxes - -- Mail users - -- External contacts - -- Distribution groups - -- Dynamic distribution groups - -You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ReadFromDomainController -The ReadFromDomainController parameter specifies that the user information is read from a domain controller in the user's domain. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Trustee -The Trustee parameter filters the results by the user or group to whom you're granting the permission. The user or group can operate on the recipient specified by the Identity parameter. - -You can specify the following types of users or groups: - -- Mailbox users - -- Mail users with a Microsoft account (formerly known as a Windows Live ID) - -- Security groups - -You can use any value that uniquely identifies the user or group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Get-SweepRule.md b/exchange/exchange-ps/exchange/mailboxes/Get-SweepRule.md deleted file mode 100644 index 51197bc591..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Get-SweepRule.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/get-sweeprule -applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-SweepRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-SweepRule - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-SweepRule cmdlet to view Sweep rules in mailboxes. Sweep rules run a regular intervals to help keep your Inbox clean. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SweepRule [[-Identity] <SweepRuleIdParameter>] [-BypassScopeCheck] [-DomainController <Fqdn>] - [-Mailbox <MailboxIdParameter>] [-Provider <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SweepRule -``` - -This example returns a summary list of all Sweep rules. - -### Example 2 -```powershell -Get-SweepRule -Mailbox julia@contoso.com -``` - -This example returns a summary list of all Sweep rules in the specified mailbox. - -### Example 3 -```powershell -Get-SweepRule -Identity "x2hlsdpGmUifjFgxxGIOJw==" -``` - -This example returns detailed information for the Sweep rule with the specified RuleId property value. - -## PARAMETERS - -### -BypassScopeCheck -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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==). - -- Exchange Online: \<mailbox alias\>\\\<RuleId\> (for example, rzaher\\x2hlsdpGmUifjFgxxGIOJw==. - -- On-premises Exchange: \<mailbox canonical name\>\\\<RuleId\> (for example, contoso.com/Users/Rick Zaher\\x2hlsdpGmUifjFgxxGIOJw==. - -```yaml -Type: SweepRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Mailbox -The Mailbox parameter filters the results by the specified mailbox. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Provider -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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Import-ContactList.md b/exchange/exchange-ps/exchange/mailboxes/Import-ContactList.md deleted file mode 100644 index 06effc5c77..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Import-ContactList.md +++ /dev/null @@ -1,210 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/import-contactlist -applicable: Exchange Online -title: Import-ContactList -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Import-ContactList - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Import-ContactList cmdlet and a .csv file to import a user's mail contacts to a cloud-based mailbox. Users can use an email client to export their contacts to a .csv file that is formatted for Microsoft Office Outlook. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Data -``` -Import-ContactList [-Identity] <MailboxIdParameter> [-CSV] -CSVData <Byte[]> - [-DateCultureName] <String> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### Stream -``` -Import-ContactList [-Identity] <MailboxIdParameter> [-CSV] -CSVStream <Stream> - [-DateCultureName] <String> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Import-ContactList cmdlet submits a request to import a list of mail contacts that are contained in a .csv file to a cloud-based mailbox. Many MAPI and Web-based email clients allow users to export contacts to a Microsoft Office Outlook .csv format. Users can then provide that .csv file to you to import contacts to their cloud-based mailbox. During the import process, Microsoft Exchange matches the column names in the header row of the .csv file to the property names of an Exchange contact. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Import-ContactList -CSV -CSVData ([System.IO.File]::ReadAllBytes("D:\Users\Administrator\Desktop\TerryAdams.csv")) -DateCultureName "en-GB" -Identity terrya@contoso.edu -``` - -This example imports a list of contacts in a .csv file named TerryAdams.csv to a mailbox for a user whose email address is terrya@contoso.edu. The date fields are parsed using the date format of "en-GB" locale (dd/MM/YYYY). - -## PARAMETERS - -### -CSV -The CSV parameter simply specifies that the contacts will be imported from a .csv file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CSVData -The CSVData parameter specifies the .csv file you want to import. Use the following syntax for this parameter: ([System.IO.File]::ReadAllBytes("\<file name and path\>")). For example, ([System.IO.File]::ReadAllBytes("C:\\My Documents\\Contacts.csv")). - -```yaml -Type: Byte[] -Parameter Sets: Data -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CSVStream -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Stream -Parameter Sets: Stream -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DateCultureName -The DateCultureName parameter specifies the culture to use for parsing date fields (e.g. Birthday and Anniversary). For example, setting the parameter to "en-GB" would lead to 01/02/2018 being parsed as February 1st, 2018, whereas setting it to "en-US" would lead to the same date being parsed as January 2nd, 2018. If the parameter is not provided, the culture of the current user is assumed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the target mailbox to which the contacts are imported. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Import-RecipientDataProperty.md b/exchange/exchange-ps/exchange/mailboxes/Import-RecipientDataProperty.md deleted file mode 100644 index 1ac2450141..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Import-RecipientDataProperty.md +++ /dev/null @@ -1,214 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Import-RecipientDataProperty - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Import-RecipientDataProperty cmdlet to add a picture or an audio file of a spoken name to a mailbox or contact. The picture and audio files display on the Global Address List property dialog box, contact card, reading pane, and meeting requests in Microsoft Outlook and Outlook on the web. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### ImportPicture -``` -Import-RecipientDataProperty [-Identity] <MailboxUserContactIdParameter> -FileData <Byte[]> [-Picture] - [-Confirm] - [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] -``` - -### ImportSpokenName -``` -Import-RecipientDataProperty [-Identity] <MailboxUserContactIdParameter> -FileData <Byte[]> [-SpokenName] - [-Confirm] - [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Importing and exporting files require a specific syntax because importing and exporting use Remote PowerShell. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Import-RecipientDataProperty -Identity "Tony Smith" -SpokenName -FileData ([Byte[]]$(Get-Content -Path "M:\AudioFiles\TonySmith.wma" -Encoding Byte -ReadCount 0)) -``` - -This example imports the audio file for Tony Smith's spoken name. - -### Example 2 -```powershell -Import-RecipientDataProperty -Identity Ayla -Picture -FileData ([Byte[]]$(Get-Content -Path "M:\Employee Photos\AylaKol.jpg" -Encoding Byte -ReadCount 0)) -``` - -This example imports the picture file for Ayla Kol. - -## PARAMETERS - -### -FileData -The FileData parameter specifies the location and file name of the picture or audio file. - -A valid value for this parameter requires you to read the file to a byte-encoded object using the Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Picture -The Picture switch specifies that the file you're importing is a picture file. You don't need to specify a value with this switch. - -The picture must be a JPEG file and shouldn't be larger than 10 kilobytes (KB). You can't use this switch with the SpokenName switch. You can only import one file type at a time. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpokenName -The SpokenName switch specifies that the file you're importing is an audio file. You don't need to specify a value with this switch. - -The maximum file size should be less than 32 KB. You can use one of the following formats: - -- WMA 9-voice - -- PCM 8-KHz, 16-bits, mono format - -You can't use this switch with the Picture switch. You can only import one file type at a time. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/New-App.md b/exchange/exchange-ps/exchange/mailboxes/New-App.md deleted file mode 100644 index 7a6462ac0c..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/New-App.md +++ /dev/null @@ -1,541 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/new-app -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-App -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# New-App - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-App cmdlet to install apps for Outlook. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### ExtensionOfficeMarketplace -``` -New-App [-Etoken <String>] [-Mailbox <MailboxIdParameter>] [-MarketplaceCorrelationID <String>] [-MarketplaceAssetID <String>] [-MarketplaceQueryMarket <String>] [-MarketplaceServicesUrl <String>] [-MarketplaceUserProfileType <String>] - [-AllowReadWriteMailbox] - [-Confirm] - [-DefaultStateForUser <DefaultStateForUser>] - [-DomainController <Fqdn>] - [-DownloadOnly] - [-Enabled <Boolean>] - [-OrganizationApp] - [-PrivateCatalog] - [-ProvidedTo <ClientExtensionProvidedTo>] - [-UserList <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### ExtensionFileData -``` -New-App [-FileData <Byte[]>] - [-AllowReadWriteMailbox] - [-Confirm] - [-DefaultStateForUser <DefaultStateForUser>] - [-DomainController <Fqdn>] - [-DownloadOnly] - [-Enabled <Boolean>] - [-Mailbox <MailboxIdParameter>] - [-OrganizationApp] - [-PrivateCatalog] - [-ProvidedTo <ClientExtensionProvidedTo>] - [-UserList <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### ExtensionFileStream -``` -New-App [-FileStream <Stream>] - [-AllowReadWriteMailbox] - [-Confirm] - [-DefaultStateForUser <DefaultStateForUser>] - [-DomainController <Fqdn>] - [-DownloadOnly] - [-Enabled <Boolean>] - [-Mailbox <MailboxIdParameter>] - [-OrganizationApp] - [-PrivateCatalog] - [-ProvidedTo <ClientExtensionProvidedTo>] - [-UserList <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### ExtensionPrivateURL -``` -New-App [-Url <Uri>] - [-AllowReadWriteMailbox] - [-Confirm] - [-DefaultStateForUser <DefaultStateForUser>] - [-DomainController <Fqdn>] - [-DownloadOnly] - [-Enabled <Boolean>] - [-Mailbox <MailboxIdParameter>] - [-OrganizationApp] - [-PrivateCatalog] - [-ProvidedTo <ClientExtensionProvidedTo>] - [-UserList <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -If the app is enabled for the entire organization, users can activate the new app when viewing mail or calendar items within Microsoft Outlook or Outlook on the web. If an installed app isn't enabled, users can enable the app from Outlook on the web Options. Similarly, administrators can enable installed apps from the Exchange admin center or by using the Enable-App or Set-App cmdlet. - -For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://docs.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of Office 365 add-ins in the Microsoft 365 admin center](https://docs.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-App -FileData ([Byte[]](Get-Content -Encoding Byte -Path "C:\Apps\FinanceTestApp.xml" -ReadCount 0)) -``` - -This example installs the Finance Test app manifest file that has been copied to the local hard disk. - -### Example 2 -```powershell -New-App -OrganizationApp -Url https://Server01.Contoso.com/apps/ContosoCRMApp/manifest.xml -ProvidedTo SpecificUsers -UserList "user1,user2,user3,user4,user5" -DefaultStateForUser Enabled -``` - -This example installs the Contoso CRM app manifest.xml from a URL on the Contoso corporate network. The Exchange server must be able to reach the target URL. This app is installed as an organization app,is made available to a specific list of users, and is enabled for those users by default. - -## PARAMETERS - -### -AllowReadWriteMailbox -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultStateForUser -The DefaultStateForUser parameter specifies the default initial state of an organization app. Valid values are: - -- Enabled: The organization app is enabled by default. - -- Disabled: The organization app is disabled by default. This is the default value. - -- AlwaysEnabled: The organization app is enabled and users can't disable it. - -You need to use the OrganizationApp switch when you use this parameter. - -```yaml -Type: DefaultStateForUser -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DownloadOnly -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -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. - -- $false: The app is hidden from all users in the organization. - -This setting overrides the ProvidedTo, UserList and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Etoken -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileData -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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -Type: Byte[] -Parameter Sets: ExtensionFileData -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileStream -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mailbox -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: For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarketplaceAssetID -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarketplaceCorrelationID -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarketplaceQueryMarket -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarketplaceServicesUrl -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarketplaceUserProfileType -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationApp -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateCatalog -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProvidedTo -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. - -- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. - -You use this parameter with the OrganizationApp switch. - -```yaml -Type: ClientExtensionProvidedTo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -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. - -```yaml -Type: Uri -Parameter Sets: ExtensionPrivateURL -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserList -The UserList parameter specifies who can use an organizational app. Valid values are mailboxes or mail users in your organization. You can use any value that uniquely identifies the user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -You use this parameter with the OrganizationApp switch. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/New-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/mailboxes/New-MailboxRestoreRequest.md deleted file mode 100644 index dcf8c6c69c..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/New-MailboxRestoreRequest.md +++ /dev/null @@ -1,1052 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# New-MailboxRestoreRequest - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-MailboxRestoreRequest cmdlet to restore a soft-deleted or disconnected mailbox. This cmdlet starts the process of moving content from the soft-deleted mailbox, disabled mailbox, or any mailbox in a recovery database into a connected primary or archive mailbox. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### MailboxLocationIDMigrationLocalMailboxRestore -``` -New-MailboxRestoreRequest -SourceDatabase <DatabaseIdParameter> -SourceStoreMailbox <StoreMailboxIdParameter> -TargetMailbox <MailboxLocationIdParameter> - [-AcceptLargeDataLoss] - [-AllowLegacyDNMismatch] - [-AssociatedMessagesCopyOption <FAICopyOption>] - [-BadItemLimit <Unlimited>] - [-BatchName <String>] - [-CompletedRequestAgeLimit <Unlimited>] - [-Confirm] - [-ConflictResolutionOption <ConflictResolutionOption>] - [-DomainController <Fqdn>] - [-ExcludeDumpster] - [-ExcludeFolders <String[]>] - [-IncludeFolders <String[]>] - [-InternalFlags <InternalMrsFlag[]>] - [-LargeItemLimit <Unlimited>] - [-Name <String>] - [-Priority <RequestPriority>] - [-RequestExpiryInterval <Unlimited>] - [-SkipMerging <SkippableMergeComponent[]>] - [-SourceRootFolder <String>] - [-Suspend] - [-SuspendComment <String>] - [-TargetIsArchive] - [-TargetRootFolder <String>] - [-TargetType <TargetTypeComponent>] - [-WhatIf] - [-WorkloadType <RequestWorkloadType>] - [<CommonParameters>] -``` - -### MailboxIDMigrationLocalMailboxRestore -``` -New-MailboxRestoreRequest -SourceDatabase <DatabaseIdParameter> -SourceStoreMailbox <StoreMailboxIdParameter> -TargetMailbox <MailboxOrMailUserIdParameter> - [-AcceptLargeDataLoss] - [-AllowLegacyDNMismatch] - [-AssociatedMessagesCopyOption <FAICopyOption>] - [-BadItemLimit <Unlimited>] - [-BatchName <String>] - [-CompletedRequestAgeLimit <Unlimited>] - [-Confirm] - [-ConflictResolutionOption <ConflictResolutionOption>] - [-DomainController <Fqdn>] - [-ExcludeDumpster] - [-ExcludeFolders <String[]>] - [-IncludeFolders <String[]>] - [-InternalFlags <InternalMrsFlag[]>] - [-LargeItemLimit <Unlimited>] - [-MRSServer <Fqdn>] - [-Name <String>] - [-Priority <RequestPriority>] - [-RequestExpiryInterval <Unlimited>] - [-SkipMerging <SkippableMergeComponent[]>] - [-SourceRootFolder <String>] - [-Suspend] - [-SuspendComment <String>] - [-TargetIsArchive] - [-TargetRootFolder <String>] - [-TargetType <TargetTypeComponent>] - [-WhatIf] - [-WorkloadType <RequestWorkloadType>] - [<CommonParameters>] -``` - -### MailboxLocationIDRemoteMailboxRestore -``` -New-MailboxRestoreRequest -RemoteCredential <PSCredential> -RemoteDatabaseGuid <Guid> -RemoteHostName <Fqdn> -RemoteRestoreType <RemoteRestoreType> -SourceStoreMailbox <StoreMailboxIdParameter> -TargetMailbox <MailboxLocationIdParameter> - [-AcceptLargeDataLoss] - [-AllowLegacyDNMismatch] - [-AssociatedMessagesCopyOption <FAICopyOption>] - [-BadItemLimit <Unlimited>] - [-BatchName <String>] - [-CompletedRequestAgeLimit <Unlimited>] - [-Confirm] - [-ConflictResolutionOption <ConflictResolutionOption>] - [-DomainController <Fqdn>] - [-ExcludeDumpster] - [-ExcludeFolders <String[]>] - [-IncludeFolders <String[]>] - [-InternalFlags <InternalMrsFlag[]>] - [-LargeItemLimit <Unlimited>] - [-Name <String>] - [-Priority <RequestPriority>] - [-RequestExpiryInterval <Unlimited>] - [-SkipMerging <SkippableMergeComponent[]>] - [-SourceRootFolder <String>] - [-Suspend] - [-SuspendComment <String>] - [-TargetIsArchive] - [-TargetRootFolder <String>] - [-TargetType <TargetTypeComponent>] - [-WhatIf] - [-WorkloadType <RequestWorkloadType>] - [<CommonParameters>] -``` - -### MailboxIDRemoteMailboxRestore -``` -New-MailboxRestoreRequest -SourceStoreMailbox <StoreMailboxIdParameter> -TargetMailbox <MailboxOrMailUserIdParameter> - [-AcceptLargeDataLoss] - [-AllowLegacyDNMismatch] - [-AssociatedMessagesCopyOption <FAICopyOption>] - [-BadItemLimit <Unlimited>] - [-BatchName <String>] - [-CompletedRequestAgeLimit <Unlimited>] - [-Confirm] - [-ConflictResolutionOption <ConflictResolutionOption>] - [-DomainController <Fqdn>] - [-ExcludeDumpster] - [-ExcludeFolders <String[]>] - [-IncludeFolders <String[]>] - [-InternalFlags <InternalMrsFlag[]>] - [-LargeItemLimit <Unlimited>] - [-Name <String>] - [-Priority <RequestPriority>] - [-SkipMerging <SkippableMergeComponent[]>] - [-SourceRootFolder <String>] - [-Suspend] - [-SuspendComment <String>] - [-TargetIsArchive] - [-TargetRootFolder <String>] - [-WhatIf] - [-WorkloadType <RequestWorkloadType>] - [<CommonParameters>] -``` - -### SourceMailbox -``` -New-MailboxRestoreRequest -SourceMailbox <MailboxLocationIdParameter> -TargetMailbox <MailboxLocationIdParameter> - [-AcceptLargeDataLoss] - [-AllowLegacyDNMismatch] - [-AssociatedMessagesCopyOption <FAICopyOption>] - [-BadItemLimit <Unlimited>] - [-BatchName <String>] - [-CompletedRequestAgeLimit <Unlimited>] - [-Confirm] - [-ConflictResolutionOption <ConflictResolutionOption>] - [-DomainController <Fqdn>] - [-ExcludeDumpster] - [-ExcludeFolders <String[]>] - [-IncludeFolders <String[]>] - [-InternalFlags <InternalMrsFlag[]>] - [-LargeItemLimit <Unlimited>] - [-Name <String>] - [-Priority <RequestPriority>] - [-RequestExpiryInterval <Unlimited>] - [-SkipMerging <SkippableMergeComponent[]>] - [-SourceIsArchive] - [-SourceRootFolder <String>] - [-Suspend] - [-SuspendComment <String>] - [-TargetIsArchive] - [-TargetRootFolder <String>] - [-TargetType <TargetTypeComponent>] - [-WhatIf] - [-WorkloadType <RequestWorkloadType>] - [<CommonParameters>] -``` - -## DESCRIPTION -When mailboxes are moved from one database to another, Exchange doesn't fully delete the mailbox from the source database immediately upon completion of the move. Instead, the mailbox in the source mailbox database is switched to a soft-deleted state, which allows mailbox data to be accessed during a mailbox restore operation by using the new MailboxRestoreRequest cmdlet set. The soft-deleted mailboxes are retained in the source database until either the deleted mailbox retention period expires or you use the Remove-StoreMailbox cmdlet to purge the mailbox. - -To view soft-deleted mailboxes, run the Get-MailboxStatistics cmdlet against a database and look for results that have a DisconnectReason with a value of SoftDeleted. For more information, see Example 1 later in this topic. - -A mailbox is marked as Disabled a short time after the Disable-Mailbox or Remove-Mailbox command completes. - -The mailbox won't be marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory has been updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database. - -Exchange retains disabled mailboxes in the mailbox database based on the deleted mailbox retention settings configured for that mailbox database. After the specified period of time, the mailbox is permanently deleted. - -To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database and look for results that have a DisconnectReason with a value of Disabled. For more information, see Example 1 later in this topic. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxStatistics -Database MBD01 | Where {$_.DisconnectReason -eq "SoftDeleted" -or $_.DisconnectReason -eq "Disabled"} | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason -``` - -To create a restore request, you must provide the DisplayName, LegacyDN, or MailboxGUID for the soft-deleted or disabled mailbox. - -This example uses the Get-MailboxStatistics cmdlet to return the DisplayName, LegacyDN, MailboxGUID, and DisconnectReason for all mailboxes on mailbox database MBD01 that have a disconnect reason of SoftDeleted or Disabled. - -### Example 2 -```powershell -New-MailboxRestoreRequest -SourceDatabase "MBD01" -SourceStoreMailbox 1d20855f-fd54-4681-98e6-e249f7326ddd -TargetMailbox Ayla -``` - -This example restores the source mailbox with the MailboxGUID 1d20855f-fd54-4681-98e6-e249f7326ddd on mailbox database MBD01 to the target mailbox with the alias Ayla. - -### Example 3 -```powershell -New-MailboxRestoreRequest -SourceDatabase "MBD01" -SourceStoreMailbox "Tony Smith" -TargetMailbox Tony@contoso.com -TargetIsArchive -``` - -This example restores the content of the source mailbox with the DisplayName of Tony Smith on mailbox database MBD01 to the archive mailbox for Tony@contoso.com. - -## PARAMETERS - -### -RemoteCredential -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: PSCredential -Parameter Sets: MailboxLocationIDRemoteMailboxRestore -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteDatabaseGuid -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: MailboxLocationIDRemoteMailboxRestore -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteHostName -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: MailboxLocationIDRemoteMailboxRestore -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteRestoreType -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: RemoteRestoreType -Parameter Sets: MailboxLocationIDRemoteMailboxRestore -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceDatabase -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: DatabaseIdParameter -Parameter Sets: MailboxLocationIDMigrationLocalMailboxRestore, MailboxIDMigrationLocalMailboxRestore -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceMailbox -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceStoreMailbox -This parameter is available only in on-premises Exchange. - -The SourceStoreMailbox parameter specifies the MailboxGUID of the source mailbox that you want to restore content from. - -You can find the MailboxGUID by running the Get-MailboxStatistics cmdlet. - -```yaml -Type: StoreMailboxIdParameter -Parameter Sets: MailboxLocationIDMigrationLocalMailboxRestore, MailboxIDMigrationLocalMailboxRestore, MailboxLocationIDRemoteMailboxRestore, MailboxIDRemoteMailboxRestore -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetMailbox -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. - -In Exchange 2016 or later and Exchange Online, this parameter is the type MailboxLocationIdParameter. - -In Exchange 2013 or earlier, this parameter is the type MailboxOrMailUserIdParameter. - -```yaml -Type: MailboxLocationIdParameter -Parameter Sets: MailboxLocationIDMigrationLocalMailboxRestore, MailboxLocationIDRemoteMailboxRestore -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: MailboxOrMailUserIdParameter -Parameter Sets: MailboxIDMigrationLocalMailboxRestore, MailboxIDRemoteMailboxRestore -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -In Exchange 2010, you need to use this switch if you set the BadItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowLegacyDNMismatch -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssociatedMessagesCopyOption -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. - -- MapByMessageClass: Find the associated message by looking up the MessageClass attribute of the source message. If there's an associated message of this class in both source and target folders, it overwrites the associated message in the target. If there isn't an associated message in the target, it creates a copy in the target. - -- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This is the default value. - -Content filtering doesn't apply to associated messages. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BadItemLimit -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. - -In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. - -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BatchName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompletedRequestAgeLimit -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: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConflictResolutionOption -The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are: - -- ForceCopy - -- KeepAll - -- KeepLatestItem - -- KeepSourceItem (This is the default value.) - -- KeepTargetItem - -- UpdateFromSource - -```yaml -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 -Default value: KeepSourceItem -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludeDumpster -The ExcludeDumpster parameter specifies whether to exclude the Recoverable Items folder. You don't have to include a value with this parameter. If you don't specify this parameter, the Recoverable Items folder is copied with the following subfolders: - -- Deletions - -- Versions - -- Purges - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludeFolders -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: - -\<FolderName\>/\*: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". - -\#\<FolderName\>\#/\*: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: - -- Inbox - -- SentItems - -- DeletedItems - -- Calendar - -- Contacts - -- Drafts - -- Journal - -- Tasks - -- Notes - -- JunkEmail - -- CommunicatorHistory - -- Voicemail - -- Fax - -- Conflicts - -- SyncIssues - -- LocalFailures - -- ServerFailures - -If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a back slash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder, but not the well-known Notes folder, use the following syntax: \\\#Notes\\\#. - -Wildcard characters can't be used in folder names. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeFolders -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: - -\<FolderName\>/\*: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, "MyProjects" or "MyProjects/FY2010". - -\#\<FolderName\>\#/\*: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, \#Inbox\# denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types: - -- Inbox - -- SentItems - -- DeletedItems - -- Calendar - -- Contacts - -- Drafts - -- Journal - -- Tasks - -- Notes - -- JunkEmail - -- CommunicationHistory - -- Voicemail - -- Fax - -- Conflicts - -- SyncIssues - -- LocalFailures - -- ServerFailures - -If the user creates a personal folder with the same name as a well-known folder and the \# symbol surrounding it, you can use a back slash (\\) as an escape character to specify that folder. For example, if a user creates a folder named \#Notes\# and you want to specify that folder, but not the well-known Notes folder, use the following syntax: \\\#Notes\\\#. - -Wildcard characters can't be used in folder names. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalFlags -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. - -```yaml -Type: InternalMrsFlag[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LargeItemLimit -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: - -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) - -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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. - -If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. - -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MRSServer -This parameter is available or functional 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. - -```yaml -Type: Fqdn -Parameter Sets: MailboxIDMigrationLocalMailboxRestore -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Lowest - -- Lower - -- Low - -- Normal (This is the default value.) - -- High - -- Higher - -- Highest - -- Emergency - -```yaml -Type: RequestPriority -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestExpiryInterval -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: - -- The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. - -- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. - -To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. - -When you use the value Unlimited, the completed request isn't automatically removed. - -```yaml -Type: Unlimited -Parameter Sets: MailboxLocationIDMigrationLocalMailboxRestore, MailboxLocationIDRemoteMailboxRestore, SourceMailbox -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipMerging -This parameter is available only in on-premises Exchange. - -The SkipMerging parameter specifies folder-related items to skip when restoring the mailbox. Use one of the following values: - -- FolderRules - -- FolderACLs - -- InitialConnectionValidation - -Use this parameter only if a restore request fails because of folder rules, folder access control lists (ACLs), or initial connection validation. - -```yaml -Type: SkippableMergeComponent[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceIsArchive -The SourceIsArchive switch specifies that the source mailbox is an archive mailbox. You can use this switch only with the SourceMailbox parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: SourceMailbox -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceRootFolder -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Suspend -The Suspend switch specifies whether to suspend the request. 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. You don't have 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuspendComment -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetIsArchive -The TargetIsArchive parameter specifies that the content is restored into the specified target mailbox's archive. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetRootFolder -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetType -The TargetType parameter specifies the type of mailbox that's the target for the restore operation. Valid values are: - -- Archive - -- MailboxLocation - -- Primary (This is the default value) - -```yaml -Type: TargetTypeComponent -Parameter Sets: MailboxLocationIDMigrationLocalMailboxRestore, MailboxLocationIDRemoteMailboxRestore, SourceMailbox -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkloadType -This parameter is available only in on-premises Exchange. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Remove-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxFolderPermission.md deleted file mode 100644 index 2f27c9130e..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxFolderPermission.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Remove-MailboxFolderPermission - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-MailboxFolderPermission cmdlet to remove folder-level permissions for users in mailboxes. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter> -User <MailboxFolderUserIdParameter> - [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You can't use this cmdlet to selectively remove permissions from a user on a mailbox folder. The cmdlet removes all permissions that are assigned to the user on the specified folder. To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-MailboxFolderPermission -Identity kim@contoso.com:\Training -User john@contoso.com -``` - -This example removes John's permissions to the Training folder in Kim's mailbox. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -Example values for the Identity parameter are john@contoso.com:\\Calendar or John:\\Marketing\\Reports. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -User -The User parameter specifies the 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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendNotificationToUser -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: - -- $true: A notification is sent. - -- $false: No notification is sent. This is the default value. - -This parameter only applies to calendar folders. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Remove-MailboxPermission.md b/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxPermission.md deleted file mode 100644 index 9eed415dba..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-MailboxPermission.md +++ /dev/null @@ -1,404 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Remove-MailboxPermission - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-MailboxPermission cmdlet to remove permissions from a user's mailbox or from an Exchange Server 2016, Exchange Server 2019 or Exchange Online mail user. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AccessRights -``` -Remove-MailboxPermission [-Identity] <MailboxIdParameter> -AccessRights <MailboxRights[]> -User <SecurityPrincipalIdParameter> - [-Confirm] - [-Deny] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-InheritanceType <ActiveDirectorySecurityInheritance>] - [-WhatIf] [<CommonParameters>] -``` - -### Instance -``` -Remove-MailboxPermission -Instance <MailboxAcePresentationObject> - [-AccessRights <MailboxRights[]>] - [-Confirm] - [-Deny] - [-DomainController <Fqdn>] [-IgnoreDefaultScope] - [[-Identity] <MailboxIdParameter>] - [-InheritanceType <ActiveDirectorySecurityInheritance>] - [-ResetDefault] - [-User <SecurityPrincipalIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -### Owner -``` -Remove-MailboxPermission [[-Identity] <MailboxIdParameter>] - [-Confirm] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-WhatIf] [<CommonParameters>] -``` - -### ClearAutoMapping -``` -Remove-MailboxPermission [-Identity] <MailboxIdParameter> [-ClearAutoMapping] - [-AccessRights <MailboxRights[]>] - [-Confirm] - [-Deny] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-InheritanceType <ActiveDirectorySecurityInheritance>] - [-User <SecurityPrincipalIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -### ResetDefault -``` -Remove-MailboxPermission [-Identity] <MailboxIdParameter> [-ResetDefault] - [-Confirm] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Remove-MailboxPermission cmdlet allows you to remove permissions from a user's mailbox, for example, removing full access to another user's mailbox. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-MailboxPermission -Identity Test1 -User Test2 -AccessRights FullAccess -InheritanceType All -``` - -This example removes user Test2's full access rights to Test1's mailbox. - -## PARAMETERS - -### -AccessRights -The AccessRights parameter specifies the rights required to perform the operation. You can use the following values: - -- FullAccess - -- SendAs - -- ExternalAccount - -- DeleteItem - -- ReadPermission - -- ChangePermission - -- ChangeOwner - -```yaml -Type: MailboxRights[] -Parameter Sets: AccessRights -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -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 -``` - -### -Identity -The Identity parameter specifies the mailbox where you are removing permissions. You can use any value that uniquely identifies the mailbox: For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -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 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: MailboxAcePresentationObject -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -User -The User parameter specifies the user mailbox that will get permissions removed. - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: AccessRights -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClearAutoMapping -This parameter is available only in the cloud-based service. - -The ClearAutoMapping switch specifies that the mailbox is automatically mapped (auto-mapped) by Autodiscover only into the mailbox owner's Outlook profile. The mailbox isn't auto-mapped to other users who have FullAccess permission to the mailbox. - -To re-add auto-mapping capability on the mailbox for other users, run the command: Add-MailboxPermission -Identity \<Mailbox\> -AccessRights FullAccess -AutoMapping $true. - -```yaml -Type: SwitchParameter -Parameter Sets: ClearAutoMapping -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Deny -The Deny parameter denies permissions to the user on the Active Directory object. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InheritanceType -The InheritanceType parameter specifies whether permissions are inherited to folders within the mailbox. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResetDefault -This parameter is available only in the cloud-based service. - -The ResetDefault switch resets the default security descriptor of the mailbox. Permissions on the mailbox are reset so only the mailbox owner has FullAccess permission to the mailbox. The following types of permissions are not affected: - -- Recipient permissions (for example, SendAs, SendOnBehalf and delegates). - -- Mailbox folder permissions assigned using the MailboxFolderPermission cmdlets. - -- Mailbox folder permissions assigned using Outlook or other MAPI clients. - -Also, because this switch removes FullAccess permission from other users on the mailbox, the mailbox is no longer auto-mapped by Autodiscover into the Outlook profiles of other users. - -```yaml -Type: SwitchParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Remove-RecipientPermission.md b/exchange/exchange-ps/exchange/mailboxes/Remove-RecipientPermission.md deleted file mode 100644 index 184d550762..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-RecipientPermission.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-recipientpermission -applicable: Exchange Online -title: Remove-RecipientPermission -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Remove-RecipientPermission - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-RecipientPermission cmdlet to remove SendAs permission from users in a cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-RecipientPermission [-Identity] <RecipientIdParameter> -AccessRights <MultiValuedProperty> - -Trustee <SecurityPrincipalIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -When a user is given SendAs permission to another user or group, the user can send messages that appear to come from the other user or group. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-RecipientPermission "Help Desk" -AccessRights SendAs -Trustee "Ayla Kol" -``` - -This example removes the SendAs permission from the user Ayla Kol for the mailbox Help Desk. Ayla can't send messages that appear to come directly from the Help Desk mailbox. - -## PARAMETERS - -### -AccessRights -The AccessRights parameter specifies the permission. - -Valid input for this parameter is SendAs. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -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: - -- Mailboxes - -- Mail users - -- External contacts - -- Distribution groups - -- Dynamic distribution groups - -You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Trustee -The Trustee parameter specifies the user or group from whom you're removing the permission. This prevents the user or group from operating on the recipients specified by the Identity parameter. - -You can specify the following types of users or groups: - -- Mailbox users - -- Mail users with a cloud-based account - -- Security groups - -You can use any value that uniquely identifies the user or group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Remove-UserPhoto.md b/exchange/exchange-ps/exchange/mailboxes/Remove-UserPhoto.md deleted file mode 100644 index ee3e37f234..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Remove-UserPhoto.md +++ /dev/null @@ -1,241 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/remove-userphoto -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-UserPhoto -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Remove-UserPhoto - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-UserPhoto cmdlet to delete the photo associated with a user's account. The user photo feature allows users to associate a picture with their account. User photos appear in on-premises and cloud-based client applications, such as Outlook on the web, Lync, Skype for Business and SharePoint. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity -``` -Remove-UserPhoto [-Identity] <MailboxIdParameter> - [-Confirm] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-WhatIf] [<CommonParameters>] -``` - -### ClearMailboxPhoto -``` -Remove-UserPhoto [-Identity] <MailboxIdParameter> [-ClearMailboxPhotoRecord] [-GroupMailbox] [-PhotoType <String>] - [-Confirm] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Remove-UserPhoto cmdlet to delete the user photo currently associated with a user's account. User photos are stored in the user's Active Directory account and in the root directory of the user's Exchange mailbox, both of which are deleted when you run this cmdlet. Administrators can also use the Exchange admin center (EAC) to delete user photos by accessing the user's Outlook on the web Options page. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-UserPhoto "Ann Beebe" -``` - -This example deletes the photo associated with Ann Beebe's user account. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ClearMailboxPhotoRecord -The ClearMailboxPhoto switch specifies that a deleted mailbox photo is considered blank instead of deleted. - -By default, when a user deletes their mailbox photo, a flag is set on the mailbox that causes subsequent photo requests to: - -- Return a blank photo. - -- Prevent searching Active Directory for a photo. - -Using this switch allows photo requests to search Active Directory for a photo. You don't have to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: ClearMailboxPhoto -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupMailbox -The GroupMailbox switch is required to modify Office 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, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhotoType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: ClearMailboxPhoto -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Set-CalendarNotification.md b/exchange/exchange-ps/exchange/mailboxes/Set-CalendarNotification.md deleted file mode 100644 index 70c32dde5c..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-CalendarNotification.md +++ /dev/null @@ -1,299 +0,0 @@ ---- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-calendarnotification -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-CalendarNotification -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-CalendarNotification - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-CalendarNotification cmdlet to set text message notifications for calendar events for a user. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-CalendarNotification [-Identity] <MailboxIdParameter> [-CalendarUpdateNotification <Boolean>] - [-CalendarUpdateSendDuringWorkHour <Boolean>] [-Confirm] [-DailyAgendaNotification <Boolean>] - [-DailyAgendaNotificationSendTime <TimeSpan>] [-DomainController <Fqdn>] [-IgnoreDefaultScope] - [-MeetingReminderNotification <Boolean>] [-MeetingReminderSendDuringWorkHour <Boolean>] - [-NextDays <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Users can receive text message notifications of changes to calendar events and daily agendas. Use the Set-CalendarNotification cmdlet to configure these notifications for a user. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-CalendarNotification -Identity "tony@contoso.com" -CalendarUpdateNotification $true -``` - -This example enables calendar updates to be sent in text messages to the user Tony Smith. - -### Example 2 -```powershell -Set-CalendarNotification -Identity "TonySmith" -CalendarUpdateNotification $true -MeetingReminderNotification $true -MeetingReminderSendDuringWorkHour $true -``` - -This example enables calendar updates and meeting reminders to be sent in text messages to the user Tony Smith. - -### Example 3 -```powershell -Set-CalendarNotification -Identity contoso\tonysmith -DailyAgendaNotification $true -``` - -This example enables a daily agenda to be sent in text messages to the user Tony Smith. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -CalendarUpdateNotification -The CalendarUpdateNotification parameter specifies whether calendar notifications are enabled for the user. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CalendarUpdateSendDuringWorkHour -The CalendarUpdateSendDuringWorkHour parameter specifies whether calendar notifications are sent during working hours. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DailyAgendaNotification -The DailyAgendaNotification parameter specifies whether a daily agenda should be sent to the user's 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DailyAgendaNotificationSendTime -The DailyAgendaNotificationSendTime parameter specifies the time to send the daily agenda. - -To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. - -For example, a time span of 2 days and 8 hours is shown: 02.08:00:00. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -The IgnoreDefaultScope parameter isn't implemented yet. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MeetingReminderNotification -The MeetingReminderNotification parameter specifies whether meeting reminders are sent to the user's 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MeetingReminderSendDuringWorkHour -The MeetingReminderSendDuringWorkHour parameter specifies whether meeting reminders are only sent during working hours. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NextDays -The NextDays parameter specifies how many days should be sent in the daily agenda. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Set-Clutter.md b/exchange/exchange-ps/exchange/mailboxes/Set-Clutter.md deleted file mode 100644 index 920671beef..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-Clutter.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-clutter -applicable: Exchange Online -title: Set-Clutter -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-Clutter - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-Clutter cmdlet to configure Clutter settings for mailboxes in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-Clutter -Identity <MailboxIdParameter> [-Enable <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-Clutter -Identity "Alexander Martinez" -Enable $false -``` - -This example disables Clutter for the user Alexander Martinez. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name>\\\<account name> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -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. - -- $false: Clutter is disabled for the mailbox. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-FocusedInbox.md b/exchange/exchange-ps/exchange/mailboxes/Set-FocusedInbox.md deleted file mode 100644 index 550ac466f6..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-FocusedInbox.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-focusedinbox -applicable: Exchange Online -title: Set-FocusedInbox -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-FocusedInbox - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-FocusedInbox cmdlet to enable or disable Focused Inbox for mailboxes in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-FocusedInbox -Identity <MailboxIdParameter> [-FocusedInboxOn <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-FocusedInbox -Identity laura@contoso.com -FocusedInboxOn $false -``` - -This example disables Focused Inbox for the mailbox of laura@contoso.com. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name>\\\<account name> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FocusedInboxOn -The FocusedInboxOn parameter enables or disables Focused Inbox for the mailbox. Valid values are: - -- $true: Focused Inbox is enabled. This is the default value. - -- $false: Focused Inbox is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxCalendarFolder.md b/exchange/exchange-ps/exchange/mailboxes/Set-MailboxCalendarFolder.md deleted file mode 100644 index 034fd1a98d..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxCalendarFolder.md +++ /dev/null @@ -1,343 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailboxcalendarfolder -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MailboxCalendarFolder -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-MailboxCalendarFolder - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-MailboxCalendarFolder cmdlet to configure calendar publishing or sharing settings on a mailbox for the visibility of calendar information to external users. To add or modify the permissions so internal users can access the calendar, use the Add-MailboxFolderPermission or Set-MailboxFolderPermission cmdlets. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MailboxCalendarFolder [-Identity] <MailboxFolderIdParameter> [-Confirm] - [-DetailLevel <DetailLevelEnumType>] [-DomainController <Fqdn>] - [-PublishDateRangeFrom <DateRangeEnumType>] - [-PublishDateRangeTo <DateRangeEnumType>] - [-PublishEnabled <Boolean>] [-ResetUrl] [-SearchableUrlEnabled <Boolean>] [-WhatIf] - [-SetAsSharingSource] [-UseHttps] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-MailboxCalendarFolder cmdlet configures publishing information. The calendar folder can be configured as follows: - -- Whether the calendar folder is enabled for publishing - -- Range of start and end calendar days to publish - -- Level of detail to publish for the calendar - -- Whether the published URL of the calendar is enabled for search on the web - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MailboxCalendarFolder -Identity kai:\Calendar -DetailLevel LimitedDetails -``` - -This example sets the level of details to publish for Kai's shared calendar to LimitedDetails, which means limited details are displayed. - -### Example 2 -```powershell -Set-MailboxCalendarFolder -Identity kai:\Calendar -SearchableUrlEnabled $true -``` - -This example enables the calendar in Kai's mailbox to be searchable on the web. - -## PARAMETERS - -### -Identity -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Calendar` - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DetailLevel -The DetailLevel parameter specifies the level of calendar detail that's published and available to anonymous users. You can use the following values: - -- AvailabilityOnly - -- LimitedDetails - -- FullDetails - -- Editor - -The default value is AvailabilityOnly. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublishDateRangeFrom -The PublishDateRangeFrom parameter specifies the number of days of calendar information to publish before the current date. You can use the following values: - -- OneDay - -- ThreeDays - -- OneWeek - -- OneMonth - -- ThreeMonths - -- SixMonths - -- OneYear - -The default value is ThreeMonths. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublishDateRangeTo -The PublishDateRangeTo parameter specifies the number of days of calendar information to publish after the current date. You can use the following values: - -- OneDay - -- ThreeDays - -- OneWeek - -- OneMonth - -- ThreeMonths - -- SixMonths - -- OneYear - -The default value is ThreeMonths. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublishEnabled -The PublishEnabled parameter specifies whether the specified calendar should be enabled for publishing. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResetUrl -The ResetUrl parameter replaces the existing non-public URL with a new URL for a calendar that has been published without being publicly searchable. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchableUrlEnabled -The SearchableUrlEnabled parameter specifies whether the published calendar URL can be searched on the web. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SetAsSharingSource -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseHttps -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Set-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/mailboxes/Set-MailboxFolderPermission.md deleted file mode 100644 index 6751384b6a..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxFolderPermission.md +++ /dev/null @@ -1,342 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-MailboxFolderPermission - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-MailboxFolderPermission cmdlet to modify folder-level permissions for users in mailboxes. This cmdlet differs from the Add-MailboxFolderPermission cmdlet in that it modifies existing permission entries. To configure calendar publishing or sharing settings for a mailbox so calendar information is visible to external users, use the Set-MailboxCalendarFolder cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter> -AccessRights <MailboxFolderAccessRight[]> - -User <MailboxFolderUserIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [-SendNotificationToUser <Boolean>] [-SharingPermissionFlags <MailboxFolderPermissionFlags>] - [<CommonParameters>] -``` - -## DESCRIPTION -In Office 365, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user will no longer be a delegate and will only have Editor permissions to the folder. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MailboxFolderPermission -Identity ayla@contoso.com:\Marketing -User ed@contoso.com -AccessRights Owner -``` - -This example overwrites Ed's existing permissions for the Marketing folder in Ayla's mailbox. Ed is now granted the Owner role on the folder. - -### Example 2 -```powershell -Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SharingPermissionFlags Delegate -SendNotificationToUser $true -``` - -In Office 365, this example resends the sharing invitation to an existing delegate without changing their effective permissions (Ed is already a delegate with Editor permissions to Ayla's mailbox). - -### Example 3 -```powershell -Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SharingPermissionFlags Delegate -``` - -In Office 365, this example removes access to private items for an existing delegate. - -### Example 4 -```powershell -Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SharingPermissionFlags None -``` - -In Office 365, this example changes an existing calendar delegate to Editor. - -### Example 5 -```powershell -Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -``` - -In Office 365, this example changes an existing user's permissions to Editor without changing their current delegate status. - -### Example 6 -```powershell -Set-MailboxFolderPermission -Identity ayla@contoso.com:\Calendar -User ed@contoso.com -AccessRights Editor -SendNotificationToUser $false -``` - -In Office 365, this example changes an existing user's permissions to Editor and removes their current delegate status. - -## PARAMETERS - -### -AccessRights -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. - -The following individual permissions are available: - -- CreateItems: The user can create items in the specified folder. - -- CreateSubfolders: The user can create subfolders in the specified folder. - -- DeleteAllItems: The user can delete all items in the specified folder. - -- DeleteOwnedItems: The user can only delete items that they created from the specified folder. - -- EditAllItems: The user can edit all items in the specified folder. - -- EditOwnedItems: The user can only edit items that they created in the specified folder. - -- FolderContact: The user is the contact for the specified public folder. - -- FolderOwner: The user is the owner of the specified folder. The user can view the folder, move the folder, and create subfolders. The user can't read items, edit items, delete items, or create items. - -- FolderVisible: The user can view the specified folder, but can't read or edit items within the specified public folder. - -- ReadItems: The user can read items within the specified folder. - -The roles that are available, along with the permissions that they assign, are described in the following list: - -- Author:CreateItems, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems - -- Contributor:CreateItems, FolderVisible - -- Editor:CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems - -- None:FolderVisible - -- NonEditingAuthor:CreateItems, FolderVisible, ReadItems - -- Owner:CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderContact, FolderOwner, FolderVisible, ReadItems - -- PublishingEditor:CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems - -- PublishingAuthor:CreateItems, CreateSubfolders, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems - -- Reviewer:FolderVisible, ReadItems - -The following roles apply specifically to calendar folders: - -- AvailabilityOnly: View only availability data - -- LimitedDetails: View availability data with subject and location - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inbox\Reports`. - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -User -The User parameter specifies the 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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendNotificationToUser -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: - -- $true: A sharing invitation is sent. - -- $false: No sharing invitation is sent. This is the default value. - -This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values: - -- AvailabilityOnly - -- LimitedDetails - -- Reviewer - -- Editor - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingPermissionFlags -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: - -- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This is the default value when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter. - -- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. - -- CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value. - -You can specify multiple values separated by commas. - -```yaml -Type: MailboxFolderPermissionFlags -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Set-MailboxPlan.md b/exchange/exchange-ps/exchange/mailboxes/Set-MailboxPlan.md deleted file mode 100644 index 2ea887d772..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-MailboxPlan.md +++ /dev/null @@ -1,422 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-mailboxplan -applicable: Exchange Online -title: Set-MailboxPlan -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-MailboxPlan - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-MailboxPlan cmdlet to modify the settings of mailbox plans in the cloud-based service. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MailboxPlan [-Identity] <MailboxPlanIdParameter> - [-Confirm] - [-Force] - [-IsDefault] - [-IssueWarningQuota <Unlimited>] - [-MaxReceiveSize <Unlimited>] - [-MaxSendSize <Unlimited>] - [-ProhibitSendQuota <Unlimited>] - [-ProhibitSendReceiveQuota <Unlimited>] - [-RetainDeletedItemsFor <EnhancedTimeSpan>] - [-RetentionPolicy <MailboxPolicyIdParameter>] - [-RoleAssignmentPolicy <MailboxPolicyIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your organization. - -Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which will apply the corresponding mailbox plan to the mailbox. - -Each mailbox plan has a corresponding Client Access services (CAS) mailbox plan with the same name and display name value. You can use the Set-CasMailboxPlan cmdlet to enable or disable POP3, IMAP4 or Exchange ActiveSync (EAS) access to new or newly-enabled mailboxes, and you can specify the Outlook on the web (formerly known as Outlook Web App) mailbox policy for the mailboxes. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MailboxPlan -Identity ExchangeOnlineEnterprise -ProhibitSendReceiveQuota 40GB -ProhibitSendQuota 39.5GB -IssueWarningQuota 39GB -``` - -This example lowers the default mailbox quotas in the mailbox plan named ExchangeOnlineEnterprise. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Display name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: MailboxPlanIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefault -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IssueWarningQuota -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. - -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxReceiveSize -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is a number up to 150 MB. The default value is 36 MB. - -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. - -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSendSize -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is a number up to 150 MB. The default value is 35 MB. - -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. - -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProhibitSendQuota -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. - -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProhibitSendReceiveQuota -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. - -The maximum value is determined by the mailbox plan. You can lower the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetainDeletedItemsFor -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. - -- Selecting the Empty Deleted Items Folder action. - -- Deleting items using Shift + Delete. - -These actions move the items to the Recoverable Items folder, into a subfolder named Deletions. - -Before the deleted item retention period expires, users can recover soft-deleted items in Outlook and Outlook on the web by using the Recover Deleted Items feature. For more information, see [Recoverable Items folder in Exchange Online](https://docs.microsoft.com/Exchange/security-and-compliance/recoverable-items-folder/recoverable-items-folder). - -To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. - -The default value is 14 days (14.00:00:00). In Exchange Online, you can increase the value to a maximum of 30 days. - -```yaml -Type: EnhancedTimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionPolicy -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 - -- Distinguished Name (DN) - -- GUID - -Retention policies consist of tags that are applied to mailbox folders and mail items to determine the period of time that the items should be retained. The default value is Default MRM Policy. - -Use the Get-RetentionPolicy cmdlet to see the available retention policies. - -```yaml -Type: MailboxPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoleAssignmentPolicy -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 - -- Distinguished name (DN) - -- GUID - -The default value is Default Role Assignment Policy. - -To see the available role assignment policies, use the Get-RoleAssignmentPolicy cmdlet. - -```yaml -Type: MailboxPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/mailboxes/Set-Place.md b/exchange/exchange-ps/exchange/mailboxes/Set-Place.md deleted file mode 100644 index bc8a46d0e6..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-Place.md +++ /dev/null @@ -1,429 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-place -applicable: Exchange Online -title: Set-Place -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-Place - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-Place cmdlet to update room mailboxes with additional metadata, which provides a better search and room suggestion experience. Note that this cmdlet works only on room mailboxes that were created in the cloud (not on synchronized room mailboxes). - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-Place [-Identity] <RecipientIdParameter> - [-AudioDeviceName <String>] - [-Building <String>] - [-Capacity <System.Int32>] - [-City <String>] - [-Confirm] - [-CountryOrRegion <CountryInfo>] - [-DisplayDeviceName <String>] - [-Floor <System.Int32>] - [-FloorLabel <String>] - [-GeoCoordinates <GeoCoordinates>] - [-IsWheelChairAccessible <Boolean>] - [-Label <String>] - [-Phone <String>] - [-PostalCode <String>] - [-State <String>] - [-Street <String>] - [-Tags <String[]>] - [-VideoDeviceName <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-Place -Identity "Conference Room 01" -IsWheelChairAccessible $true -AudioDeviceName PolyCom -VideoDeviceName "InFocus WXGA Projector" -``` - -The example adds the specified metadata to the room mailbox named Conference Room 01. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AudioDeviceName -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Building -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Capacity -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -The CountryOrRegion parameter specifies the room's country or region. - -```yaml -Type: CountryInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayDeviceName -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Floor -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FloorLabel -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GeoCoordinates -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" - -- Latitude, longitude, and altitude: For example, "47.644125;-122.122411;161.432" - -```yaml -Type: GeoCoordinates -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsWheelChairAccessible -The IsWheelChairAccessible parameter specifies whether the room is wheelchair accessible. Valid values are: - -- $true: The room is wheelchair accessible. - -- $false: The room is not wheelchair accessible. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Label -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Phone -The Phone parameter specifies the room's telephone number. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostalCode -The PostalCode parameter specifies the room's postal code. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State -The State parameter specifies the room's state or province. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Street -The Street parameter specifies the room's physical address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tags -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: \<Label1\>,\<Label2\>,...\<LabelN\>. If the labels contains spaces, enclose the value in quotation marks: "\<Label1\>","\<Label2\>",..."\<LabelN\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VideoDeviceName -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/mailboxes/Set-UserPhoto.md b/exchange/exchange-ps/exchange/mailboxes/Set-UserPhoto.md deleted file mode 100644 index a1f0a753d1..0000000000 --- a/exchange/exchange-ps/exchange/mailboxes/Set-UserPhoto.md +++ /dev/null @@ -1,382 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/mailboxes/set-userphoto -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-UserPhoto -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-UserPhoto - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-UserPhoto cmdlet to configure the user photos feature that allows users to associate a picture with their account. User photos appear in on-premises and cloud-based client applications, such as Outlook on the web, Lync, Skype for Business, and SharePoint. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### CancelPhoto -``` -Set-UserPhoto [-Identity] <MailboxIdParameter> [-Cancel] - [-Confirm] - [-GroupMailbox] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-PhotoType <String>] - [-WhatIf] [<CommonParameters>] -``` - -### UploadPhotoData -``` -Set-UserPhoto [-Identity] <MailboxIdParameter> -PictureData <Byte[]> - [-Confirm] - [-DomainController <Fqdn>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-PhotoType <String>] - [-WhatIf] [<CommonParameters>] -``` - -### UploadPreview -``` -Set-UserPhoto [-Identity] <MailboxIdParameter> [-PictureData <Byte[]>] [-PictureStream <Stream>] [-Preview] - [-Confirm] - [-DomainController <Fqdn>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-PhotoType <String>] - [-WhatIf] [<CommonParameters>] -``` - -### UploadPhotoStream -``` -Set-UserPhoto [-Identity] <MailboxIdParameter> -PictureStream <Stream> - [-Confirm] - [-DomainController <Fqdn>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-PhotoType <String>] - [-WhatIf] [<CommonParameters>] -``` - -### SavePhoto -``` -Set-UserPhoto [-Identity] <MailboxIdParameter> [-Save] - [-Confirm] - [-DomainController <Fqdn>] - [-GroupMailbox] - [-IgnoreDefaultScope] - [-PhotoType <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The user photos feature allows users to associate a picture with their account. User photos are stored in the user's Active Directory account and in the root directory of the user's Exchange mailbox. Administrators use the Set-UserPhoto cmdlet to configure user photos. Users can upload, preview, and save a user photo to their account by using the Outlook on the web Options page. When a user uploads a photo, a preview of the photo is displayed on the Outlook on the web Options page. This is the preview state, and creates the same result as running the Set-UserPhoto cmdlet using the Preview parameter. If the user clicks Save, the preview photo is saved as the user's photo. This is the same result as running the Set-UserPhoto -Save command or running both the Set-UserPhoto -Preview and Set-UserPhoto -Save commands. If the user cancels the preview photo on the Outlook on the web Options page, then the Set-UserPhoto -Cancel command is called. - -A user photo must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user's photo. Otherwise, you'll get an error message saying the user photo doesn't exist for the specified user. Alternatively, you can run the Get-UserPhoto -Preview command to view information about a preview photo. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-UserPhoto -Identity "Paul Cannon" -PictureData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\PaulCannon.jpg")) -``` - -This example uploads and saves a photo to Paul Cannon's user account using a single command. - -### Example 2 -```powershell -Set-UserPhoto -Identity "Ann Beebe" -PictureData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\AnnBeebe.jpg")) -Preview; Set-UserPhoto "Ann Beebe" -Save -``` - -This example shows how to use two commands to upload and save a preview photo to Ann Beebe's user account. The first command uploads a preview photo to Ann Beebe's user account, and the second command saves the uploaded photo as the preview photo. - -### Example 3 -```powershell -Set-UserPhoto -Identity "Ann Beebe" -Cancel -``` - -This example deletes the preview photo that was uploaded in the previous example. - -## PARAMETERS - -### -Cancel -The Cancel switch parameter 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. - -```yaml -Type: SwitchParameter -Parameter Sets: CancelPhoto -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -PictureData -The PictureData parameter specifies the photo file that will be uploaded to the user's account. - -This parameter uses the syntax ([System.IO.File]::ReadAllBytes("\<file name and path\>")). The following is an example. ([System.IO.File]::ReadAllBytes("C:\\Documents\\Pictures\\MyPhoto.jpg")). - -```yaml -Type: Byte[] -Parameter Sets: UploadPhotoData -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -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, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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 -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -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, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: SwitchParameter -Parameter Sets: UploadPreview -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Save -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, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupMailbox -The GroupMailbox switch is required to modify Office 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, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange Management Shell session and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhotoType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/move-and-migration/Get-MigrationBatch.md b/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationBatch.md deleted file mode 100644 index faf2c8b948..0000000000 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationBatch.md +++ /dev/null @@ -1,288 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-migrationbatch -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-MigrationBatch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MigrationBatch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MigrationBatch cmdlet to retrieve status information about the current migration batch. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### BatchesFromEndpoint -``` -Get-MigrationBatch [-Endpoint <MigrationEndpointIdParameter>] - [-Diagnostic] - [-DiagnosticArgument <String>] - [-DiagnosticInfo <String>] - [-DomainController <Fqdn>] - [-IncludeReport] - [-Partition <MailboxIdParameter>] - [-Status <Microsoft.Exchange.Data.Storage.Management.MigrationBatchStatus>] - [<CommonParameters>] -``` - -### Identity -``` -Get-MigrationBatch [[-Identity] <MigrationBatchIdParameter>] - [-Diagnostic] - [-DiagnosticArgument <String>] - [-DiagnosticInfo <String>] - [-DomainController <Fqdn>] - [-IncludeReport] - [-Partition <MailboxIdParameter>] - [-Status <Microsoft.Exchange.Data.Storage.Management.MigrationBatchStatus>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-MigrationBatch cmdlet displays status information about the current migration batch. This information includes the following information: - -- Status of the migration batch - -- Total number of mailboxes being migrated - -- Number of successfully completed migrations - -- Migration errors - -- Date and time when the migration was started - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MigrationBatch -Identity LocalMove2 -``` - -This example displays status information for the migration batch LocalMove2. - -### Example 2 -```powershell -Get-MigrationBatch -Endpoint exsrv1.contoso.com -``` - -This example displays information about all migration batches associated with the migration endpoint exsrv1.contoso.com. - -## PARAMETERS - -### -Diagnostic -This parameter is available only in on-premises Exchange. - -The Diagnostic switch specifies whether to return extremely detailed information in the results. Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiagnosticArgument -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiagnosticInfo -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Endpoint -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. - -```yaml -Type: MigrationEndpointIdParameter -Parameter Sets: BatchesFromEndpoint -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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. - -```yaml -Type: MigrationBatchIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IncludeReport -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Partition -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Status -The Status parameter returns a list of migration batches that have the specified status state. Use one of the following values: - -- Completed - -- CompletedWithErrors - -- Completing - -- Corrupted - -- Created - -- Failed - -- IncrementalSyncing - -- Removing - -- Starting - -- Stopped - -- Syncing - -- Stopping - -- Synced - -- SyncedwithErrors - -- Waiting - -```yaml -Type: Microsoft.Exchange.Data.Storage.Management.MigrationBatchStatus -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/move-and-migration/Get-MigrationConfig.md b/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationConfig.md deleted file mode 100644 index 97376eef42..0000000000 --- a/exchange/exchange-ps/exchange/move-and-migration/Get-MigrationConfig.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/get-migrationconfig -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-MigrationConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MigrationConfig - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MigrationConfig cmdlet to retrieve migration configuration settings on Exchange servers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MigrationConfig [-DomainController <Fqdn>] [-Partition <MailboxIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MigrationConfig -``` - -This example retrieves the settings for the migration configuration. - -## PARAMETERS - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Partition -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/move-and-migration/New-MigrationBatch.md b/exchange/exchange-ps/exchange/move-and-migration/New-MigrationBatch.md deleted file mode 100644 index 8ae31a6186..0000000000 --- a/exchange/exchange-ps/exchange/move-and-migration/New-MigrationBatch.md +++ /dev/null @@ -1,1233 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-migrationbatch -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MigrationBatch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# New-MigrationBatch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-MigrationBatch cmdlet to submit a new migration request for a batch of users. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Local -``` -New-MigrationBatch [-Local] -Name <String> -CSVData <Byte[]> [-DisallowExistingUsers] [-WorkloadType <Microsoft.Exchange.MailboxReplicationService.RequestWorkloadType>] [-WorkflowControlFlags <MigrationWorkflowControlFlags>] - [-AllowIncrementalSyncs <Boolean>] - [-AllowUnknownColumnsInCsv <Boolean>] - [-ArchiveOnly] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-BadItemLimit <Unlimited>] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DomainController <Fqdn>] - [-Locale <CultureInfo>] - [-MoveOptions <MultiValuedProperty>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-PrimaryOnly] - [-ReportInterval <Timespan>] - [-SkipMoving <MultiValuedProperty>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-StartAfter <DateTime>] - [-TargetArchiveDatabases <MultiValuedProperty>] - [-TargetDatabases <MultiValuedProperty>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -### LocalPublicFolder -``` -New-MigrationBatch -Name <String> -CSVData <Byte[]> -SourcePublicFolderDatabase <DatabaseIdParameter> - [-AllowIncrementalSyncs <Boolean>] - [-AllowUnknownColumnsInCsv <Boolean>] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-BadItemLimit <Unlimited>] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DomainController <Fqdn>] - [-LargeItemLimit <Unlimited>] - [-Locale <CultureInfo>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-ReportInterval <Timespan>] - [-SkipMerging <MultiValuedProperty>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-StartAfter <DateTime>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -### PreexistingUserIds -``` -New-MigrationBatch <MultiValuedProperty> -Name <String> [-UserIds] - [-AllowIncrementalSyncs <Boolean>] - [-AllowUnknownColumnsInCsv <Boolean>] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DisableOnCopy] - [-DomainController <Fqdn>] - [-Locale <CultureInfo>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-ReportInterval <Timespan>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-StartAfter <DateTime>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -### Preexisting -``` -New-MigrationBatch -Name <String> [-Users] <MultiValuedProperty> - [-AllowIncrementalSyncs <Boolean>] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DisableOnCopy] - [-DomainController <Fqdn>] - [-Locale <CultureInfo>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-ReportInterval <Timespan>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-StartAfter <DateTime>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -### Onboarding -``` -New-MigrationBatch -Name <String> [-CSVData <Byte[]>] [-DisallowExistingUsers] [-WorkflowControlFlags <MigrationWorkflowControlFlags>] - [-AllowIncrementalSyncs <Boolean>] - [-AllowUnknownColumnsInCsv <Boolean>] - [-ArchiveOnly] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-BadItemLimit <Unlimited>] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DomainController <Fqdn>] - [-ExcludeDumpsters] - [-ExcludeFolders <MultiValuedProperty>] - [-LargeItemLimit <Unlimited>] - [-Locale <CultureInfo>] - [-MoveOptions <MultiValuedProperty>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-PrimaryOnly] - [-ReportInterval <Timespan>] - [-SkipMerging <MultiValuedProperty>] - [-SkipMoving <MultiValuedProperty>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-SourceEndpoint <MigrationEndpointIdParameter>] - [-StartAfter <DateTime>] - [-TargetArchiveDatabases <MultiValuedProperty>] - [-TargetDatabases <MultiValuedProperty>] - [-TargetDeliveryDomain <String>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -### Offboarding -``` -New-MigrationBatch -Name <String> -CSVData <Byte[]> [-DisallowExistingUsers] - [-AllowIncrementalSyncs <Boolean>] - [-AllowUnknownColumnsInCsv <Boolean>] - [-ArchiveOnly] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-BadItemLimit <Unlimited>] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DomainController <Fqdn>] - [-LargeItemLimit <Unlimited>] - [-Locale <CultureInfo>] - [-MoveOptions <MultiValuedProperty>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-PrimaryOnly] - [-ReportInterval <Timespan>] - [-SkipMerging <MultiValuedProperty>] - [-SkipMoving <MultiValuedProperty>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-StartAfter <DateTime>] - [-TargetArchiveDatabases <MultiValuedProperty>] - [-TargetDatabases <MultiValuedProperty>] - [-TargetDeliveryDomain <String>] - [-TargetEndpoint <MigrationEndpointIdParameter>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -### PublicFolderToUnifiedGroup -``` -New-MigrationBatch -Name <String> -CSVData <Byte[]> [-PublicFolderToUnifiedGroup] - [-AllowIncrementalSyncs <Boolean>] - [-AllowUnknownColumnsInCsv <Boolean>] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-BadItemLimit <Unlimited>] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DomainController <Fqdn>] - [-LargeItemLimit <Unlimited>] - [-Locale <CultureInfo>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-ReportInterval <Timespan>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-SourceEndpoint <MigrationEndpointIdParameter>] - [-StartAfter <DateTime>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -### WorkflowTemplate -``` -New-MigrationBatch -Name <String> [-WorkflowTemplate <String>] - [-AllowIncrementalSyncs <Boolean>] - [-AllowUnknownColumnsInCsv <Boolean>] - [-AutoComplete] - [-AutoRetryCount <Int32>] - [-AutoStart] - [-CompleteAfter <DateTime>] - [-Confirm] - [-DomainController <Fqdn>] - [-Locale <CultureInfo>] - [-NotificationEmails <MultiValuedProperty>] - [-Partition <MailboxIdParameter>] - [-ReportInterval <Timespan>] - [-SkipReports] - [-SkipSteps <SkippableMigrationSteps[]>] - [-StartAfter <DateTime>] - [-TimeZone <ExTimeZoneValue>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the New-MigrationBatch cmdlet to create a migration batch to migrate mailboxes and mailbox data in one of the following migration scenarios. - -Moves in on-premises Exchange organizations - -- Local move: A local move is where you move mailboxes from one mailbox database to another. A local move occurs within a single forest. For more information, see Example 1. - -- Cross-forest enterprise move: In a cross-forest enterprise move, mailboxes are moved to a different forest. Cross-forest moves are initiated either from the target forest, which is the forest that you want to move the mailboxes to, or from the source forest, which is the forest that currently hosts the mailboxes. For more information, see Example 2. - -Onboarding and offboarding in Exchange Online - -- Onboarding remote move migration: In a hybrid deployment, you can move mailboxes from an on-premises Exchange organization to Exchange Online. This is also known as an onboarding remote move migration because you on-board mailboxes to Exchange Online. For more information, see Example 3. - -- Offboarding remote move migration: You can also perform an offboarding remote move migration, where you migrate Exchange Online mailboxes to your on-premises Exchange organization. For more information, see Example 4. - - Both onboarding and offboarding remote move migrations are initiated from your Exchange Online organization. - -- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes will be automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5. - -- Staged Exchange migration: You can also migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. This is another type of onboarding migration. Migrating mailboxes from Exchange 2010 or later versions of Exchange isn't supported using a staged migration. Prior to running a staged migration, you have to use directory synchronization or some other method to provision mail users in your Exchange Online organization. For more information, see Example 6. - -- IMAP migration: This onboarding migration type migrates mailbox data from an IMAP server (including Exchange) to Exchange Online. For an IMAP migration, you must first provision mailboxes in Exchange Online before you can migrate mailbox data. For more information, see Example 7. - -- G Suite migration: This onboarding migration type migrates mailbox data from a G Suite tenant to Exchange Online. For a G Suite migration, you must first provision mail users (or mailboxes) in Exchange Online before you can migrate mailbox data. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-MigrationBatch -Local -Name LocalMove1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\LocalMove1.csv")) -TargetDatabases MBXDB2; -Start-MigrationBatch -Identity LocalMove1 -``` - -This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes that will be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically. - -### Example 2 -```powershell -$Credentials = Get-Credential; -$MigrationEndpointSource = New-MigrationEndpoint -ExchangeRemoteMove -Name Forest1Endpoint -Autodiscover -EmailAddress administrator@forest1.contoso.com -Credentials $Credentials; -$CrossForestBatch = New-MigrationBatch -Name CrossForestBatch1 -SourceEndpoint $MigrationEndpointSource.Identity -TargetDeliveryDomain forest2.contoso.com -TargetDatabases MBXDB1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\CrossForestBatch1.csv")); Start-MigrationBatch -Identity $CrossForestBatch.Identity -``` - -This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Note that cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to. - -### Example 3 -```powershell -$Credentials = Get-Credential; -$MigrationEndpointOnPrem = New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials; -$OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $MigrationEndpointOnprem.Identity -TargetDeliveryDomain cloud.contoso.com -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\RemoteOnBoarding1.csv")); -Start-MigrationBatch -Identity $OnboardingBatch.Identity -``` - -This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes that will be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. - -### Example 4 -```powershell -$Credentials = Get-Credential; -$MigrationEndpointOnPrem = New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials; -$OffboardingBatch = New-MigrationBatch -Name RemoteOffBoarding1 -TargetEndpoint $MigrationEndpointOnprem.Identity -TargetDeliveryDomain onprem.contoso.com -TargetDatabases @(MBXDB01,MBXDB02,MBXDB03) -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\RemoteOffBoarding1.csv")); -Start-MigrationBatch -Identity $OffboardingBatch.Identity -``` - -This example creates a migration batch for an offboarding remote move migration from Exchange Online to an on-premises Exchange organization. Like an onboarding remote move, it's initiated from the Exchange Online organization. First a Migration Endpoint is created that contains information about how to connect to the on-premises organization. The endpoint is used as the TargetEndpoint when creating the migration batch, which is then started with the Start-MigrationBatch cmdlet. The TargetDatabases parameter specifies multiple on-premises databases that the migration service can select as the target database to move the mailbox to. - -### Example 5 -```powershell -$credentials = Get-Credential; -$SourceEndpoint = New-MigrationEndpoint -ExchangeOutlookAnywhere -Autodiscover -Name SourceEndpoint -EmailAddress administrator@contoso.com -Credentials $credentials; -New-MigrationBatch -Name CutoverBatch -SourceEndpoint $SourceEndpoint.Identity -TimeZone "Pacific Standard Time" -AutoStart -``` - -This example creates a migration batch for the cutover Exchange migration CutoverBatch that's automatically started. The example obtains the connection settings to the on-premises Exchange server, and then uses those connection settings to create a migration endpoint. The endpoint is then used to create the migration batch. This example also includes the optional TimeZone parameter. - -### Example 6 -```powershell -$Credentials = Get-Credential; -$MigrationEndpoint = New-MigrationEndpoint -ExchangeOutlookAnywhere -Name ContosoEndpoint -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials; -$StagedBatch1 = New-MigrationBatch -Name StagedBatch1 -SourceEndpoint $MigrationEndpoint.Identity -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\StagedBatch1.csv")); -Start-MigrationBatch -Identity $StagedBatch1.Identity -``` - -This example creates and starts a migration batch for a staged Exchange migration. The example uses the New-MigrationEndpoint cmdlet to create a migration endpoint for the on-premises Exchange server, and then uses that endpoint to create the migration batch. The migration batch is started with the Start-MigrationBatch cmdlet. - -### Example 7 -```powershell -New-MigrationEndpoint -IMAP -Name IMAPEndpoint1 -RemoteServer imap.contoso.com -Port 993; -New-MigrationBatch -Name IMAPbatch1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\IMAPmigration_1.csv")) -SourceEndpoint IMAPEndpoint1 -ExcludeFolders "Deleted Items","Junk Email" -``` - -This example creates a migration endpoint for the connection settings to the IMAP server. Then an IMAP migration batch is created that uses the CSV migration file IMAPmigration\_1.csv and excludes the contents of the Deleted Items and Junk Email folders. This migration batch is pending until it's started with the Start-MigrationBatch cmdlet. - -### Example 8 -```powershell -$Credentials = Get-Credential; -$MigrationEndpointOnPrem = New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials; -$OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $MigrationEndpointOnprem.Identity -TargetDeliveryDomain cloud.contoso.com -CSVData ([System.IO.File]::ReadAllBytes("C:\Users\Administrator\Desktop\RemoteOnBoarding1.csv")) -CompleteAfter "09/01/2018 7:00 PM"; -Start-MigrationBatch -Identity $OnboardingBatch.Identity -``` - -This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM. This method allows you to start a migration and then leave it to complete after business hours. - -## PARAMETERS - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CSVData -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://docs.microsoft.com/exchange/csv-files-for-mailbox-migration-exchange-2013-help). - -Use the following format for the value of this parameter: ([System.IO.File]::ReadAllBytes(\<path of the CSV migration file\>)). For example: -CSVData ([System.IO.File]::ReadAllBytes("C:\\Users\\Administrator\\Desktop\\MigrationBatch\_1.csv")) - -```yaml -Type: Byte[] -Parameter Sets: Local, LocalPublicFolder, Offboarding, PublicFolderToUnifiedGroup -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: SwitchParameter -Parameter Sets: Local -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcePublicFolderDatabase -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: DatabaseIdParameter -Parameter Sets: LocalPublicFolder -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserIds -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. - -To disable the migration of the users in the original migration batch, use the DisableOnCopy switch with this parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: PreexistingUserIds -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Users -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 - -New-MigrationBatch -Name "Retry Failed Users" -Users $Failed - -The users that you specify for this parameter must be defined in an existing migration batch. - -To disable the migration of the users in the original migration batch, use the DisableOnCopy switch with this parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Preexisting -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AllowIncrementalSyncs -This parameter is available only in on-premises Exchange. - -The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: - -- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This is the default value. - -- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUnknownColumnsInCsv -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. - -- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ArchiveOnly -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. - -You can use the TargetArchiveDatabases parameter to specify the database to migrate the archive mailboxes to. You can also specify the target archive database in the CSV file. If you don't specify the target archive database, the cmdlet uses the automatic mailbox distribution logic to select the database. - -```yaml -Type: SwitchParameter -Parameter Sets: Local, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoComplete -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. - -If you don't use this switch, you need to run the Complete-MigrationBatch cmdlet to finalize a migration batch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoRetryCount -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. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoStart -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BadItemLimit -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. - -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration will use Skipped Item approval semantics instead of BadItemLimit semantics. - -```yaml -Type: Unlimited -Parameter Sets: Local, LocalPublicFolder, Onboarding, Offboarding, PublicFolderToUnifiedGroup -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompleteAfter -This parameter is available 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 won't complete 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". - -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). - -To specify a date/time value for this parameter, use either of the following options: - -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableOnCopy -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 -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisallowExistingUsers -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. - -A validation warning is displayed for any pre-existing mailbox in the target destination. - -```yaml -Type: SwitchParameter -Parameter Sets: Local, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludeDumpsters -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. - -You use this switch only in public folder migrations from Exchange 2013 or later to Exchange Online. - -```yaml -Type: SwitchParameter -Parameter Sets: Onboarding -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludeFolders -This parameter is available only in the cloud-based service. - -For an IMAP migration, the ExcludeFolders parameter specifies mailbox folders that you don't want to migrate from the on-premises messaging system to the cloud-based mailboxes. Use folder names relative to the IMAP root on the on-premises mail server. Specify the value as a string array and separate multiple folder names with commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Onboarding -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LargeItemLimit -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: - -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) - -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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. - -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. - -```yaml -Type: Unlimited -Parameter Sets: LocalPublicFolder, Onboarding, Offboarding, PublicFolderToUnifiedGroup -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Locale -This parameter is available only in on-premises Exchange. - -The Locale parameter specifies the language for the migration batch. - -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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveOptions -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Local, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationEmails -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Partition -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MailboxIdParameter -Parameter Sets: Local, LocalPublicFolder, PreexistingUserIds, Preexisting, Onboarding, Offboarding, PublicFolderToUnifiedGroup, WorkflowTemplate -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimaryOnly -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. - -Note : If the users don't have archive mailboxes, don't use this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: Local, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderToUnifiedGroup -This parameter is available only in the cloud-based service. - -The PublicFolderToUnifiedGroup switch specifies a migration from public folders to Office 365 groups. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: PublicFolderToUnifiedGroup -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportInterval -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. - -This parameter should only be used in the cloud-based service. - -```yaml -Type: TimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipMerging -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: LocalPublicFolder, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipMoving -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Local, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipReports -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipSteps -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: - -- None (This is the default value) - -- SettingTargetAddress: Don't set the target email address on the source mailbox. This setting prevents mail from being forwarded from the original mailbox to the new migrated mailbox. - -This parameter is only enforced for staged Exchange migrations. - -```yaml -Type: SkippableMigrationSteps[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceEndpoint -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) - -- GUID - -This parameter defines the settings that are used to connect to the server where the source mailboxes are located. - -```yaml -Type: MigrationEndpointIdParameter -Parameter Sets: Onboarding, PublicFolderToUnifiedGroup -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartAfter -This parameter is available only in the cloud-based service. - -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". - -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). - -To specify a date/time value for this parameter, use either of the following options: - -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -```yaml -Type: DateTime -Parameter Sets: Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetArchiveDatabases -The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch will be migrated to. - -You can also specify multiple databases for the value of this parameter. The migration service selects one database as the target database to move the archive mailbox to. For example: -TargetArchiveDatabases @(MBXDB01,MBXDB02,MBXDB03) - -You can only use this parameter for local moves and remote move migrations. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Local, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDatabases -The TargetDatabases parameter specifies the identity of the database that you're moving mailboxes to. You can use the following values: - -- Database GUID - -- Database name - -If you don't specify the TargetDatabases parameter for a local move, the cmdlet uses the automatic mailbox distribution logic to select the database. - -You can also specify multiple databases for the value of this parameter. The migration service will select one as the target database to move the mailbox to. For example: -TargetDatabases @(MBXDB01,MBXDB02,MBXDB03) - -You can only use this parameter for local moves and remote move migrations. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Local, Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDeliveryDomain -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 - -```yaml -Type: String -Parameter Sets: Onboarding, Offboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetEndpoint -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) - -- GUID - -This parameter defines the settings that are used to connect to the destination server where the mailboxes will be moved. - -```yaml -Type: MigrationEndpointIdParameter -Parameter Sets: Offboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeZone -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"). - -To see the available values, run the following command: `$TimeZone = Get-ChildItem "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Time zones" | foreach {Get-ItemProperty $_.PSPath}; $TimeZone | sort Display | Format-Table -Auto PSChildname,Display`. - -If the value contains spaces, enclose the value in quotation marks ("). The default value is the time zone setting of the Exchange server. - -```yaml -Type: ExTimeZoneValue -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkflowControlFlags -The WorkflowControlFlags parameter specifies advanced controls for the steps that are performed in the migration. Valid values are: - -- None (This is the default value) - -- InjectAndForget - -- SkipSwitchover - -Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. - -```yaml -Type: MigrationWorkflowControlFlags -Parameter Sets: Local, Onboarding -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkflowTemplate -The WorkflowControlFlags 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkloadType -This parameter is available only in on-premises Exchange. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Microsoft.Exchange.MailboxReplicationService.RequestWorkloadType -Parameter Sets: Local -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/move-and-migration/New-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/move-and-migration/New-PublicFolderMoveRequest.md deleted file mode 100644 index 187f9a54b8..0000000000 --- a/exchange/exchange-ps/exchange/move-and-migration/New-PublicFolderMoveRequest.md +++ /dev/null @@ -1,409 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-publicfoldermoverequest -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-PublicFolderMoveRequest -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# New-PublicFolderMoveRequest - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the New-PublicFolderMoveRequest cmdlet to begin the process of moving public folder contents between public folder mailboxes. Moving public folders only moves the physical contents of the public folder; it doesn't change the logical hierarchy. When the move request is completed, you must run the Remove-PublicFolderMoveRequest cmdlet to remove the request or wait until the time specified in the CompletedRequestAgeLimit parameter has passed. The request must be removed before you can run another move request. - -Be aware that the target public folder mailbox will be locked while the move request is active. See the Detailed Description section below for more details. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-PublicFolderMoveRequest -Folders <PublicFolderIdParameter[]> -TargetMailbox <MailboxIdParameter> - [-AcceptLargeDataLoss] [-AllowLargeItems] [-BadItemLimit <Unlimited>] [-CompletedRequestAgeLimit <Unlimited>] - [-Confirm] [-DomainController <Fqdn>] [-InternalFlags <InternalMrsFlag[]>] [-Name <String>] - [-Priority <RequestPriority>] [-Suspend] - [-SuspendComment <String>] [-SuspendWhenReadyToComplete] [-WhatIf] - [-WorkloadType <RequestWorkloadType>] - [-RequestExpiryInterval <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox will be locked. As a result, public folders already residing in the target public folder mailbox will be inaccessible until the move request is complete. Therefore, before you begin the move request, you should make sure no users are accessing public folder data in that target public folder mailbox. - -To move the public folder mailbox to another mailbox database, use the New-MoveRequest cmdlet. To ensure that this folder is already in the target public folder mailbox, run the Update-PublicFolderMailbox cmdlet against the target public folder mailbox. You can only perform one move request at a time. You can also move public folders by using the Move-PublicFolderBranch.ps1 script. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-PublicFolderMoveRequest -Folders \DeveloperReports\CustomerEngagements -TargetMailbox DeveloperReports01 -``` - -This example begins the move request for the public folder \\CustomerEngagements from public folder mailbox DeveloperReports to DeveloperReports01. - -### Example 2 -```powershell -New-PublicFolderMoveRequest -Folders \Dev\CustomerEngagements,\Dev\RequestsforChange,\Dev\Usability -TargetMailbox DeveloperReports01 -``` - -This example begins the move request for public folders under the \\Dev public folder branch to the target public folder mailbox DeveloperReports01. - -You can also move a branch of public folders by using the Move-PublicFolderBranch.ps1 script. - -### Example 3 -```powershell -$folders = Get-PublicFolder \ -Recurse -Mailbox PUB1 -ResidentFolders | ?{$_.Name -ne "IPM_SUBTREE"} | %{$_.Identity};New-PublicFolderMoveRequest -TargetMailbox PUB2 -Folders $folders -``` - -This example moves all public folders from public folder mailbox Pub1 to public folder mailbox Pub2. - -## PARAMETERS - -### -Folders -The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, 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 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetMailbox -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -You need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowLargeItems -The AllowLargeItems parameter specifies that you can move large items only when large items are encountered. Large items are email messages with a maximum of 1,023 attachments. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BadItemLimit -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. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompletedRequestAgeLimit -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternalFlags -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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 - -- Lower - -- Low - -- Normal: This is the default value. - -- High - -- Higher - -- Highest - -- Emergency - -```yaml -Type: RequestPriority -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Suspend -The Suspend switch specifies whether to suspend the request. 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. You don't have 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuspendComment -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuspendWhenReadyToComplete -The SuspendWhenReadyToComplete switch 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: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkloadType -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestExpiryInterval -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. - -- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet. - -To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. - -When you use the value Unlimited, the completed request isn't automatically removed. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/move-and-migration/Set-MigrationUser.md b/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationUser.md deleted file mode 100644 index b72d79c4a6..0000000000 --- a/exchange/exchange-ps/exchange/move-and-migration/Set-MigrationUser.md +++ /dev/null @@ -1,284 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/set-migrationuser -applicable: Exchange Online -title: Set-MigrationUser -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-MigrationUser - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-MigrationUser cmdlet to modify the migration settings of a user in an existing migration batch. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MigrationUser [-Identity] <MigrationUserIdParameter> - [-ApproveSkippedItems] - [-BadItemLimit <Unlimited>] - [-CompleteAfter <DateTime>] - [-Confirm] - [-LargeItemLimit <Unlimited>] - [-Partition <MailboxIdParameter>] - [-StartAfter <DateTime>] - [-SyncNow] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MigrationUser -Identity laura@contoso.com -LargeItemLimit 15 -BadItemLimit 15 -``` - -This example changes the large item limit and bad item limit for the user laura@contoso.com in an existing migration batch. - -### Example 2 -```powershell -Set-MigrationUser -Identity laura@contoso.com -ApproveSkippedItems -``` - -This example approves all of the skipped items encountered for the user laura@contoso.com in an existing migration batch. - -## PARAMETERS - -### -Identity -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. - -```yaml -Type: MigrationUserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ApproveSkippedItems -This parameter is available only in the cloud-based service. - -The ApproveSkippedItems switch marks all of the skipped items discovered prior to the current 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. - -For more information about maximum message size values, see the following topic [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926). - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BadItemLimit -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. - -**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompleteAfter -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. - -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". - -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). - -To specify a date/time value for this parameter, use either of the following options: - -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LargeItemLimit -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: - -- Exchange 2016: [Message size limits in Exchange Server](https://docs.microsoft.com/Exchange/mail-flow/message-size-limits) - -- Exchange Online: [Exchange Online Limits](https://go.microsoft.com/fwlink/p/?LinkId=524926) - -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 large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. - -**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Partition -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartAfter -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. - -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". - -In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). - -To specify a date/time value for this parameter, use either of the following options: - -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SyncNow -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Start-MigrationUser.md b/exchange/exchange-ps/exchange/move-and-migration/Start-MigrationUser.md deleted file mode 100644 index e248695a68..0000000000 --- a/exchange/exchange-ps/exchange/move-and-migration/Start-MigrationUser.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/start-migrationuser -applicable: Exchange Online -title: Start-MigrationUser -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Start-MigrationUser - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Start-MigrationUser cmdlet to start the migration of a user in an existing migration batch. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Start-MigrationUser [[-Identity] <MigrationUserIdParameter>] [-Confirm] [-Partition <MailboxIdParameter>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Start-MigrationUser -Identity laura@contoso.com -``` - -This example starts the migration of the user named laura@contoso.com - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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. - -```yaml -Type: MigrationUserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Partition -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationUser.md b/exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationUser.md deleted file mode 100644 index 7db8aeebdc..0000000000 --- a/exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationUser.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/move-and-migration/stop-migrationuser -applicable: Exchange Online -title: Stop-MigrationUser -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Stop-MigrationUser - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Stop-MigrationUser cmdlet to stop the migration of a user in an existing migration batch. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Stop-MigrationUser [[-Identity] <MigrationUserIdParameter>] [-Confirm] [-Partition <MailboxIdParameter>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Stop-MigrationUser -Identity laura@contoso.com -``` - -This example stops the migration of the user laura@contoso.com. - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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. - -```yaml -Type: MigrationUserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Partition -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-AccessToCustomerDataRequest.md b/exchange/exchange-ps/exchange/organization/Get-AccessToCustomerDataRequest.md deleted file mode 100644 index 3149f30b87..0000000000 --- a/exchange/exchange-ps/exchange/organization/Get-AccessToCustomerDataRequest.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-accesstocustomerdatarequest -applicable: Exchange Online -title: Get-AccessToCustomerDataRequest -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-AccessToCustomerDataRequest - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-AccessToCustomerDataRequest cmdlet to view Office 365 customer lockbox requests that control access to your data by Microsoft support engineers. - -Note: Customer lockbox is included in the Office 365 E5 plan. If you don't have an Office 365 E5 plan, you can buy a separate customer lockbox subscription with any Office 365 Enterprise plan. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AccessToCustomerDataRequest [-ApprovalStatus <String>] [-CreatedAfter <ExDateTime>] [-RequestId <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AccessToCustomerDataRequest -``` - -This example returns a summary list of all customer lockbox request. - -### Example 2 -```powershell -Get-AccessToCustomerDataRequest -ApprovalStatus Pending -``` - -This example returns a summary list of all customer lockbox requests that have the status value Pending. - -### Example 3 -```powershell -Get-AccessToCustomerDataRequest -RequestId EXSR123456 | Format-List -``` - -This example returns detailed information the customer lockbox request EXSR123456. - -## PARAMETERS - -### -ApprovalStatus -The ApprovalStatus parameter filters the results by approval status. Valid values are: - -- Approved - -- Canceled - -- Denied - -- Pending - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CreatedAfter -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: - -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -```yaml -Type: ExDateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestId -The RequestId parameter filters the results by reference number (for example, EXSR123456). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/organization/Get-AuthenticationPolicy.md deleted file mode 100644 index 4c4a512569..0000000000 --- a/exchange/exchange-ps/exchange/organization/Get-AuthenticationPolicy.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/get-authenticationpolicy -applicable: Exchange Server 2019, Exchange Online -title: Get-AuthenticationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# Get-AuthenticationPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-AuthenticationPolicy cmdlet to view authentication policies in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AuthenticationPolicy [[-Identity] <AuthPolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AuthenticationPolicy | Format-Table -Auto Name -``` - -This example returns a summary list of all authentication policies. - -### Example 2 -```powershell -Get-AuthenticationPolicy -Identity "Engineering Group" -``` - -This example returns detailed information for the authentication policy named Engineering Group. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the authentication policy you want to view. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: AuthPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/organization/New-ApplicationAccessPolicy.md deleted file mode 100644 index 6d0d5b19e5..0000000000 --- a/exchange/exchange-ps/exchange/organization/New-ApplicationAccessPolicy.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/new-applicationaccesspolicy -applicable: Exchange Online -title: New-ApplicationAccessPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# New-ApplicationAccessPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-ApplicationAccessPolicy cmdlet to restrict or deny access for an application that is using Outlook REST APIs or Microsoft Graph APIs to a specific set of mailboxes. These policies are complimentary to the permission scopes that are declared by the application. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Set1 -``` -New-ApplicationAccessPolicy -AccessRight <ApplicationAccessPolicyRight> -AppId <String[]> -PolicyScopeGroupId <RecipientIdParameter> - [-Confirm] - [-Description <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -Use the New-ApplicationAccessPolicy cmdlet to restrict or deny access for an application that is using Outlook REST APIs or Microsoft Graph APIs to a specific set of mailboxes. These policies are complimentary to the permission scopes that are declared by the application. - -While the scope-based resource access like Mail.Read or Calendar.Read is effective to ensure that the application can only read mails or events within a mailbox and not do anything else; Application Access Policy feature allows admins to enforce limits that are based on a list of mailboxes. For example, in a global organization apps developed for one country shouldn’t have access to data from other countries or a CRM integration application should only access calendar of the Sales organization and no other departments. - -Every API request using the Outlook REST APIs or Microsoft Graph APIs to a target mailbox done by an application is verified using the following rules (in the same order): - -1. If there are multiple application access policies for the same Application and Target Mailbox pair, DenyAccess policy is prioritized over a RestrictAccess policy. - -2. If a DenyAccess policy exists for the Application and Target Mailbox, then the app's access request is denied (even if there exists a RestrictAccess policy). - -3. If there are any RestrictAccess policies that match the Application and Target Mailbox, then the app is granted access. - -4. If there are any Restrict policies for the Application, and the Target Mailbox is not a member of those policies, then application is denied access to the target mailbox. - -5. If none of the above conditions are met, then the application is granted access to the requested target mailbox. - -## EXAMPLES - -### Example 1 -```powershell -New-ApplicationAccessPolicy -AccessRight DenyAccess -AppId "3dbc2ae1-7198-45ed-9f9f-d86ba3ec35b5", "6ac794ca-2697-4137-8754-d2a78ae47d93" -PolicyScopeGroupId "Engineering Staff" -Description "Engineering Group Policy" -``` - -This example creates a new application access policy with the following settings: - -- AccessRight: DenyAccess - -- AppIDs: 3dbc2ae1-7198-45ed-9f9f-d86ba3ec35b5 and 6ac794ca-2697-4137-8754-d2a78ae47d93 - -- PolicyScopeGroupId: Engineering Staff - -- Description: Engineering Group Policy - -### Example 2 -```powershell -New-ApplicationAccessPolicy -AccessRight RestrictAccess -AppId "e7e4dbfc-046f-4074-9b3b-2ae8f144f59b" -PolicyScopeGroupId EvenUsers@AppPolicyTest2.com -Description "Restrict this app to members of security group EvenUsers." -``` - -This example creates a new application access policy with the following settings: - -- AccessRight: RestrictAccess - -- AppIDs: e7e4dbfc-046f-4074-9b3b-2ae8f144f59b - -- PolicyScopeGroupId: EvenUsers@AppPolicyTest2.com - -- Description: Restrict this app to members of security group EvenUsers. - -### Example 3 -```powershell -New-ApplicationAccessPolicy -AccessRight DenyAccess -AppId "e7e4dbfc-046f-4074-9b3b-2ae8f144f59b" -PolicyScopeGroupId OddUsers@AppPolicyTest2.com -Description "Deny this app access to members of security group OddUsers." -``` - -This example creates a new application access policy with the following settings: - -- AccessRight: DenyAccess - -- AppIDs: e7e4dbfc-046f-4074-9b3b-2ae8f144f59b - -- PolicyScopeGroupId: OddUsers@AppPolicyTest2.com - -- Description: Deny this app access to members of security group OddUsers. - -## PARAMETERS - -### -AccessRight -The AccessRight parameter specifies the permission that you want to assign in the application access policy. Valid values are: - -- RestrictAccess - -- DenyAccess - -```yaml -Type: ApplicationAccessPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AppId -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. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -PolicyScopeGroupID -The PolicyScopeGroupID parameter specifies the recipient to define in the policy. You can use any value that uniquely identifies the recipient. You can also specify a mail enabled security group to restrict/deny access to a large number of user mailboxes. -For example: - -- Name - -- Distinguished name (DN) - -- Display name - -- Email address - -- GUID - -This parameter only accepts recipients that are security principals (users or groups that can have permissions assigned to them). The following types of recipients are not security principals, so you can't use them with this parameter:: - -- Discovery mailboxes - -- Dynamic distribution groups - -- Distribution groups - -- Shared mailboxes - -To verify that a recipient is a security principal, use the syntax `Get-Recipient -Identity <RecipientIdentity> | Select-Object IsValidSecurityPrincipal`. - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn’t work on this cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/New-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/organization/New-AuthenticationPolicy.md deleted file mode 100644 index 33e1098fc9..0000000000 --- a/exchange/exchange-ps/exchange/organization/New-AuthenticationPolicy.md +++ /dev/null @@ -1,603 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/new-authenticationpolicy -applicable: Exchange Online -title: New-AuthenticationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# New-AuthenticationPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-AuthenticationPolicy cmdlet to create authentication policies in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-AuthenticationPolicy [[-Name] <String>] - [-AllowBasicAuthActiveSync] - [-AllowBasicAuthAutodiscover] - [-AllowBasicAuthImap] - [-AllowBasicAuthMapi] - [-AllowBasicAuthOfflineAddressBook] - [-AllowBasicAuthOutlookService] - [-AllowBasicAuthPop] - [-AllowBasicAuthPowershell] - [-AllowBasicAuthReportingWebServices] - [-AllowBasicAuthRpc] - [-AllowBasicAuthSmtp] - [-AllowBasicAuthWebServices] - [-BlockLegacyAuthActiveSync] - [-BlockLegacyAuthAutodiscover] - [-BlockLegacyAuthImap] - [-BlockLegacyAuthMapi] - [-BlockLegacyAuthOfflineAddressBook] - [-BlockLegacyAuthPop] - [-BlockLegacyAuthRpc] - [-BlockLegacyAuthWebServices] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-AuthenticationPolicy -Name "Engineering Group" -AllowBasicAuthImap -``` - -In Exchange Online, this example creates a new authentication policy named Engineering Group that allows Basic authentication with IMAP. - -### Example 2 -```powershell -New-AuthenticationPolicy -Name "Research and Development Group" -BlockLegacyAuthActiveSync -BlockLegacyAuthAutodiscover -BlockLegacyAuthImap -BlockLegacyAuthMapi -BlockLegacyAuthOfflineAddressBook -BlockLegacyAuthPop -BlockLegacyAuthRpc -BlockLegacyAuthWebServices -``` - -In Exchange 2019, this example creates a new authentication policy named Research and Development Group that blocks legacy authentication for the specified protocols. - -## PARAMETERS - -### -Name -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 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthActiveSync -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthAutodiscover -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthImap -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthMapi -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthOfflineAddressBook -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthOutlookService -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthPop -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthPowershell -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthReportingWebServices -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthRpc -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthSmtp -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthWebServices -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. - -By default, Basic authentication is blocked for the protocol. Use this switch to allow Basic authentication for the protocol. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthActiveSync -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. - -This switch disables the following legacy authentication methods with Exchange ActiveSync: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthAutodiscover -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. - -This switch disables the following legacy authentication methods with Autodiscover: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthImap -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. - -This switch disables the following legacy authentication methods with IMAP: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthMapi -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. - -This switch disables the following legacy authentication methods with MAPI: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthOfflineAddressBook -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. - -This switch disables the following legacy authentication methods with Offline Address Books: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthPop -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. - -This switch disables the following legacy authentication methods with POP: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthRpc -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. - -This switch disables the following legacy authentication methods with RPC: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthWebServices -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. - -This switch disables the following legacy authentication methods with EWS: - -- Basic authentication - -- Digest authentication - -- Windows authentication (NTLM and Kerberos) - -Before you disable the legacy authentication methods for this protocol, verify that hybrid Modern authentication is enabled and working in your Exchange hybrid environment, and that your email clients support Modern authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Remove-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/organization/Remove-ApplicationAccessPolicy.md deleted file mode 100644 index 0478eb8b55..0000000000 --- a/exchange/exchange-ps/exchange/organization/Remove-ApplicationAccessPolicy.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/remove-applicationaccesspolicy -applicable: Exchange Online -title: Remove-ApplicationAccessPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Remove-ApplicationAccessPolicy - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-ApplicationAccessPolicy cmdlet to remove application access policies. These changes may take up to 30 minutes to go live. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Set1 -``` -Remove-ApplicationAccessPolicy -[Identity] <ApplicationAccessPolicyIdParameter> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ApplicationAccessPolicy -Identity "596ade3a-1abe-4c5b-b7d5-a169c4b05d4a\7a774f0c-7a6f-11e0-85ad-07fb4824019b:S-1-5-21-724521725-2336880675-2689004279-1821338;8b6ce428-cca2-459a-ac50-d38bcc932258" -``` - -This example removes the specified policy. - -## PARAMETERS - -### -Identity -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 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn’t work on this cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/organization/Remove-AuthenticationPolicy.md deleted file mode 100644 index 5fb526be78..0000000000 --- a/exchange/exchange-ps/exchange/organization/Remove-AuthenticationPolicy.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/remove-authenticationpolicy -applicable: Exchange Online -title: Remove-AuthenticationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# Remove-AuthenticationPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-AuthenticationPolicy cmdlet to remove authentication policies from your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-AuthenticationPolicy [-Identity] <AuthPolicyIdParameter> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-AuthenticationPolicy -Identity "Engineering Group" -``` - -This example removes the authentication policy named "Engineering Group". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the authentication policy you want to remove. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: AuthPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-AccessToCustomerDataRequest.md b/exchange/exchange-ps/exchange/organization/Set-AccessToCustomerDataRequest.md deleted file mode 100644 index 82891e60ee..0000000000 --- a/exchange/exchange-ps/exchange/organization/Set-AccessToCustomerDataRequest.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-accesstocustomerdatarequest -applicable: Exchange Online -title: Set-AccessToCustomerDataRequest -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-AccessToCustomerDataRequest - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-AccessToCustomerDataRequest cmdlet to approve, deny, or cancel Office 365 customer lockbox requests that control access to your data by Microsoft support engineers. - -Note: Customer lockbox is included in the Office 365 E5 plan. If you don't have an Office 365 E5 plan, you can buy a separate customer lockbox subscription with any Office 365 Enterprise plan. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AccessToCustomerDataRequest -ApprovalDecision <Approve | Deny | Cancel> -RequestId <String> - [-Comment <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-AccessToCustomerDataRequest -ApprovalDecision Approve -RequestId EXSR123456 -Comment "Troubleshoot issues in Rick Hofer mailbox" -``` - -This example approves the customer lockbox request EXSR123456 with a comment. - -## PARAMETERS - -### -ApprovalDecision -The ApprovalDecision parameter specifies the approval decision for the customer lockbox request. Valid values are: - -- Approve - -- Deny - -- Cancel - -```yaml -Type: Approve | Deny | Cancel -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestId -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 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/organization/Set-AuthenticationPolicy.md deleted file mode 100644 index db69871a8e..0000000000 --- a/exchange/exchange-ps/exchange/organization/Set-AuthenticationPolicy.md +++ /dev/null @@ -1,585 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-authenticationpolicy -applicable: Exchange Online -title: Set-AuthenticationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2019 || exchonline-ps" ---- - -# Set-AuthenticationPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-AuthenticationPolicy cmdlet to modify authentication policies in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AuthenticationPolicy [-Identity] <AuthPolicyIdParameter> - [-AllowBasicAuthActiveSync] - [-AllowBasicAuthAutodiscover] - [-AllowBasicAuthImap] - [-AllowBasicAuthMapi] - [-AllowBasicAuthOfflineAddressBook] - [-AllowBasicAuthOutlookService] - [-AllowBasicAuthPop] - [-AllowBasicAuthPowershell] - [-AllowBasicAuthReportingWebServices] - [-AllowBasicAuthRpc] - [-AllowBasicAuthSmtp] - [-AllowBasicAuthWebServices] - [-BlockLegacyAuthActiveSync] - [-BlockLegacyAuthAutodiscover] - [-BlockLegacyAuthImap] - [-BlockLegacyAuthMapi] - [-BlockLegacyAuthOfflineAddressBook] - [-BlockLegacyAuthPop] - [-BlockLegacyAuthRpc] - [-BlockLegacyAuthWebServices] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-AuthenticationPolicy -Identity "Engineering Group" -AllowBasicAuthReportingWebServices -``` - -In Exchange Online, this example modifies the authentication policy named Engineering Group to allow Basic authentication for Exchange Reporting Web Services. - -### Example 2 -```powershell -Set-AuthenticationPolicy -Identity "Research and Development Group" -BlockLegacyAuthReportingWebServices:$false -``` - -In Exchange 2019, this example re-enables Basic authentication for Exchange Reporting Web Services in the authentication policy named Research and Development Group. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the authentication policy you want to modify. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: AuthPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthActiveSync -This parameter is available only in the cloud-based service. - -The AllowBasicAuthActiveSync switch specifies whether to allow Basic authentication with Exchange Active Sync. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthActiveSync:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthAutodiscover -This parameter is available only in the cloud-based service. - -The AllowBasicAuthAutodiscover switch specifies whether to allow Basic authentication with Autodiscover. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthAutodiscover:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthImap -This parameter is available only in the cloud-based service. - -The AllowBasicAuthImap switch specifies whether to allow Basic authentication with IMAP. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthImap:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthMapi -This parameter is available only in the cloud-based service. - -The AllowBasicAuthMapi switch specifies whether to allow Basic authentication with MAPI. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAutMapi:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthOfflineAddressBook -This parameter is available only in the cloud-based service. - -The AllowBasicAuthOfflineAddressBook switch specifies whether to allow Basic authentication with Offline Address Books. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthOfflineAddressBook:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthOutlookService -This parameter is available only in the cloud-based service. - -The AllowBasicAuthOutlookService switch specifies whether to allow Basic authentication with the Outlook service. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthOutlookService:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthPop -This parameter is available only in the cloud-based service. - -The AllowBasicAuthPop switch specifies whether to allow Basic authentication with POP. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthPop:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthPowershell -This parameter is available only in the cloud-based service. - -The AllowBasicAuthPowerShell switch specifies whether to allow Basic authentication with PowerShell. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthPowershell:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthReportingWebServices -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. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthReportingWebServices:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthRpc -This parameter is available only in the cloud-based service. - -The AllowBasicAuthRpc switch specifies whether to allow Basic authentication with RPC. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthRpc:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthSmtp -This parameter is available only in the cloud-based service. - -The AllowBasicAuthSmtp switch specifies whether to allow Basic authentication with SMTP. - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthSmtp:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowBasicAuthWebServices -This parameter is available only in the cloud-based service. - -The AllowBasicAuthWebServices switch specifies whether to allow Basic authentication with Exchange Web Services (EWS). - -- To allow Basic authentication for the protocol, use this switch without a value. - -- To block Basic authentication for the protocol, use this exact syntax: -AllowBasicAuthWebServices:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthActiveSync -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for ActiveSync, use this switch without a value. - -- To allow legacy authentication methods for ActiveSync, use this exact syntax: -BlockLegacyAuthActiveSync:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthAutodiscover -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for Autodiscover, use this switch without a value. - -- To allow legacy authentication methods for Autodiscover, use this exact syntax: -BlockLegacyAuthAutodiscover:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthImap -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for IMAP, use this switch without a value. - -- To allow legacy authentication methods for IMAP, use this exact syntax: -BlockLegacyAuthImap:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthMapi -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for MAPI, use this switch without a value. - -- To allow legacy authentication methods for MAPI, use this exact syntax: -BlockLegacyAuthMapi:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthOfflineAddressBook -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for Offline Address Books, use this switch without a value. - -- To allow legacy authentication methods for OfflineAddressBooks, use this exact syntax: -BlockLegacyAuthOfflineAddressBook:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthPop -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for POP, use this switch without a value. - -- To allow legacy authentication methods for POP, use this exact syntax: -BlockLegacyAuthPop:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthRpc -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for RPC, use this switch without a value. - -- To allow legacy authentication methods for RPC, use this exact syntax: -BlockLegacyAuthRpc:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockLegacyAuthWebServices -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. - -- To block Basic authentication, Digest authentication, and Windows authentication (NTLM and Kerberos) for EWS, use this switch without a value. - -- To allow legacy authentication methods for EWS, use this exact syntax: -BlockLegacyAuthWebServices:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md b/exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md deleted file mode 100644 index 02e1487d61..0000000000 --- a/exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md +++ /dev/null @@ -1,2570 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/organization/set-organizationconfig -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-OrganizationConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-OrganizationConfig - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-OrganizationConfig cmdlet to configure various settings of an Exchange organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Default -``` -Set-OrganizationConfig - [-ActivityBasedAuthenticationTimeoutEnabled <Boolean>] - [-ActivityBasedAuthenticationTimeoutInterval <EnhancedTimeSpan>] - [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled <Boolean>] - [-AppsForOfficeEnabled <Boolean>] - [-AsyncSendEnabled <Boolean>] - [-AuditDisabled <Boolean>] - [-AutodiscoverPartialDirSync <Boolean>] - [-AutoEnableArchiveMailbox <Boolean>] - [-AutoExpandingArchive] - [-BookingsEnabled <Boolean>] - [-BookingsPaymentsEnabled <Boolean>] - [-BookingsSocialSharingRestricted <Boolean>] - [-ByteEncoderTypeFor7BitCharsets <Int32>] - [-CalendarVersionStoreEnabled <Boolean>] - [-Confirm] - [-ConnectorsActionableMessagesEnabled <Boolean>] - [-ConnectorsEnabled <Boolean>] - [-ConnectorsEnabledForOutlook <Boolean>] - [-ConnectorsEnabledForSharepoint <Boolean>] - [-ConnectorsEnabledForTeams <Boolean>] - [-ConnectorsEnabledForYammer <Boolean>] - [-DefaultAuthenticationPolicy <AuthPolicyIdParameter>] - [-DefaultGroupAccessType <ModernGroupObjectType>] - [-DefaultPublicFolderAgeLimit <EnhancedTimeSpan>] - [-DefaultPublicFolderDeletedItemRetention <EnhancedTimeSpan>] - [-DefaultPublicFolderIssueWarningQuota <Unlimited>] - [-DefaultPublicFolderMaxItemSize <Unlimited>] - [-DefaultPublicFolderMovedItemRetention <EnhancedTimeSpan>] - [-DefaultPublicFolderProhibitPostQuota <Unlimited>] - [-DirectReportsGroupAutoCreationEnabled <Boolean>] - [-DistributionGroupDefaultOU <OrganizationalUnitIdParameter>] - [-DistributionGroupNameBlockedWordsList <MultiValuedProperty>] - [-DistributionGroupNamingPolicy <DistributionGroupNamingPolicy>] - [-ElcProcessingDisabled <Boolean>] - [-EndUserDLUpgradeFlowsDisabled <Boolean>] - [-EwsAllowEntourage <Boolean>] - [-EwsAllowList <MultiValuedProperty>] - [-EwsAllowMacOutlook <Boolean>] - [-EwsAllowOutlook <Boolean>] - [-EwsApplicationAccessPolicy <EwsApplicationAccessPolicy>] - [-EwsBlockList <MultiValuedProperty>] - [-EwsEnabled <Boolean>] - [-ExchangeNotificationEnabled <Boolean>] - [-ExchangeNotificationRecipients <MultiValuedProperty>] - [-FocusedInboxOn <Boolean>] - [-HierarchicalAddressBookRoot <UserContactGroupIdParameter>] - [-IPListBlocked <MultiValuedProperty>] - [-IsAgendaMailEnabled <Boolean>] - [-LeanPopoutEnabled <Boolean>] - [-LinkPreviewEnabled <Boolean>] - [-MailTipsAllTipsEnabled <Boolean>] - [-MailTipsExternalRecipientsTipsEnabled <Boolean>] - [-MailTipsGroupMetricsEnabled <Boolean>] - [-MailTipsLargeAudienceThreshold <UInt32>] - [-MailTipsMailboxSourcedTipsEnabled <Boolean>] - [-OAuth2ClientProfileEnabled <Boolean>] - [-OutlookMobileGCCRestrictionsEnabled <Boolean>] - [-OutlookMobileHelpShiftEnabled <Boolean>] - [-OutlookMobileSingleAccountEnabled <Boolean>] - [-OutlookPayEnabled <Boolean>] - [-PerTenantSwitchToESTSEnabled <Boolean>] - [-PreferredInternetCodePageForShiftJis <Int32>] - [-PublicComputersDetectionEnabled <Boolean>] - [-PublicFoldersEnabled <PublicFoldersDeployment>] - [-PublicFolderShowClientControl <Boolean>] - [-ReadTrackingEnabled <Boolean>] - [-RefreshSessionEnabled <Boolean>] - [-RemotePublicFolderMailboxes <MultiValuedProperty>] - [-RequiredCharsetCoverage <Int32>] - [-SiteMailboxCreationURL <Uri>] - [-SmtpActionableMessagesEnabled <Boolean>] - [-UnblockUnsafeSenderPromptEnabled <Boolean>] - [-VisibleMeetingUpdateProperties <String>] - [-WebPushNotificationsDisabled <Boolean>] - [-WebSuggestedRepliesDisabled <Boolean>] - [-WhatIf] [<CommonParameters>] -``` - -### AdfsAuthenticationRawConfiguration -``` -Set-OrganizationConfig [-AdfsAuthenticationConfiguration <String>] - [-ACLableSyncedObjectEnabled <Boolean>] - [-ActivityBasedAuthenticationTimeoutEnabled <Boolean>] - [-ActivityBasedAuthenticationTimeoutInterval <EnhancedTimeSpan>] - [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled <Boolean>] - [-AppsForOfficeEnabled <Boolean>] - [-AsyncSendEnabled <Boolean>] - [-ByteEncoderTypeFor7BitCharsets <Int32>] - [-Confirm] - [-ConnectorsActionableMessagesEnabled <Boolean>] - [-ConnectorsEnabled <Boolean>] - [-CustomerFeedbackEnabled <Boolean>] - [-DataClassifications <String>] - [-DefaultPublicFolderAgeLimit <EnhancedTimeSpan>] - [-DefaultPublicFolderDeletedItemRetention <EnhancedTimeSpan>] - [-DefaultPublicFolderIssueWarningQuota <Unlimited>] - [-DefaultPublicFolderMaxItemSize <Unlimited>] - [-DefaultPublicFolderMovedItemRetention <EnhancedTimeSpan>] - [-DefaultPublicFolderProhibitPostQuota <Unlimited>] - [-DistributionGroupDefaultOU <OrganizationalUnitIdParameter>] - [-DistributionGroupNameBlockedWordsList <MultiValuedProperty>] - [-DistributionGroupNamingPolicy <DistributionGroupNamingPolicy>] - [-DomainController <Fqdn>] - [-EwsAllowEntourage <Boolean>] - [-EwsAllowList <MultiValuedProperty>] - [-EwsAllowMacOutlook <Boolean>] - [-EwsAllowOutlook <Boolean>] - [-EwsApplicationAccessPolicy <EwsApplicationAccessPolicy>] - [-EwsBlockList <MultiValuedProperty>] - [-EwsEnabled <Boolean>] - [-Force] - [-HierarchicalAddressBookRoot <UserContactGroupIdParameter>] - [-Industry <IndustryType>] - [-IsAgendaMailEnabled <Boolean>] - [-IsExcludedFromOffboardMigration <Boolean>] - [-IsExcludedFromOnboardMigration <Boolean>] - [-IsFfoMigrationInProgress <Boolean>] - [-LeanPopoutEnabled <Boolean>] - [-LinkPreviewEnabled <Boolean>] - [-MailTipsAllTipsEnabled <Boolean>] - [-MailTipsExternalRecipientsTipsEnabled <Boolean>] - [-MailTipsGroupMetricsEnabled <Boolean>] - [-MailTipsLargeAudienceThreshold <UInt32>] - [-MailTipsMailboxSourcedTipsEnabled <Boolean>] - [-ManagedFolderHomepage <String>] - [-MapiHttpEnabled <Boolean>] - [-MaxConcurrentMigrations <Unlimited>] - [-MicrosoftExchangeRecipientEmailAddresses <ProxyAddressCollection>] - [-MicrosoftExchangeRecipientEmailAddressPolicyEnabled <Boolean>] - [-MicrosoftExchangeRecipientPrimarySmtpAddress <SmtpAddress>] - [-MicrosoftExchangeRecipientReplyRecipient <RecipientIdParameter>] - [-OAuth2ClientProfileEnabled <Boolean>] - [-OrganizationSummary <MultiValuedProperty>] - [-PermanentlyDeleteDisabled <Boolean>] - [-PreferredInternetCodePageForShiftJis <Int32>] - [-PublicComputersDetectionEnabled <Boolean>] - [-PublicFolderContentReplicationDisabled <Boolean>] - [-PublicFolderMailboxesLockedForNewConnections <Boolean>] - [-PublicFolderMailboxesMigrationComplete <Boolean>] - [-PublicFolderMigrationComplete <Boolean>] - [-PublicFoldersEnabled <PublicFoldersDeployment>] - [-PublicFoldersLockedForMigration <Boolean>] - [-ReadTrackingEnabled <Boolean>] - [-RefreshSessionEnabled <Boolean>] - [-RemotePublicFolderMailboxes <MultiValuedProperty>] - [-RequiredCharsetCoverage <Int32>] - [-SCLJunkThreshold <Int32>] - [-SiteMailboxCreationURL <Uri>] - [-SmtpActionableMessagesEnabled <Boolean>] - [-UMAvailableLanguages <MultiValuedProperty>] - [-UnblockUnsafeSenderPromptEnabled <Boolean>] - [-WACDiscoveryEndpoint <String>] - [-WhatIf] [<CommonParameters>] -``` - -### AdfsAuthenticationParameter -``` -Set-OrganizationConfig [-AdfsAudienceUris <MultiValuedProperty>] [-AdfsEncryptCertificateThumbprint <String>] [-AdfsIssuer <Uri>] [-AdfsSignCertificateThumbprints <MultiValuedProperty>] - [-ACLableSyncedObjectEnabled <Boolean>] - [-ActivityBasedAuthenticationTimeoutEnabled <Boolean>] - [-ActivityBasedAuthenticationTimeoutInterval <EnhancedTimeSpan>] - [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled <Boolean>] - [-AppsForOfficeEnabled <Boolean>] - [-AsyncSendEnabled <Boolean>] - [-ByteEncoderTypeFor7BitCharsets <Int32>] - [-Confirm] - [-ConnectorsActionableMessagesEnabled <Boolean>] - [-ConnectorsEnabled <Boolean>] - [-CustomerFeedbackEnabled <Boolean>] - [-DataClassifications <String>] - [-DefaultPublicFolderAgeLimit <EnhancedTimeSpan>] - [-DefaultPublicFolderDeletedItemRetention <EnhancedTimeSpan>] - [-DefaultPublicFolderIssueWarningQuota <Unlimited>] - [-DefaultPublicFolderMaxItemSize <Unlimited>] - [-DefaultPublicFolderMovedItemRetention <EnhancedTimeSpan>] - [-DefaultPublicFolderProhibitPostQuota <Unlimited>] - [-DistributionGroupDefaultOU <OrganizationalUnitIdParameter>] - [-DistributionGroupNameBlockedWordsList <MultiValuedProperty>] - [-DistributionGroupNamingPolicy <DistributionGroupNamingPolicy>] - [-DomainController <Fqdn>] - [-EwsAllowEntourage <Boolean>] - [-EwsAllowList <MultiValuedProperty>] - [-EwsAllowMacOutlook <Boolean>] - [-EwsAllowOutlook <Boolean>] - [-EwsApplicationAccessPolicy <EwsApplicationAccessPolicy>] - [-EwsBlockList <MultiValuedProperty>] - [-EwsEnabled <Boolean>] - [-ExchangeNotificationEnabled <Boolean>] - [-ExchangeNotificationRecipients <MultiValuedProperty>] - [-Force] - [-HierarchicalAddressBookRoot <UserContactGroupIdParameter>] - [-Industry <IndustryType>] - [-IsAgendaMailEnabled <Boolean>] - [-IsExcludedFromOffboardMigration <Boolean>] - [-IsExcludedFromOnboardMigration <Boolean>] - [-IsFfoMigrationInProgress <Boolean>] - [-LeanPopoutEnabled <Boolean>] - [-LinkPreviewEnabled <Boolean>] - [-MailTipsAllTipsEnabled <Boolean>] - [-MailTipsExternalRecipientsTipsEnabled <Boolean>] - [-MailTipsGroupMetricsEnabled <Boolean>] - [-MailTipsLargeAudienceThreshold <UInt32>] - [-MailTipsMailboxSourcedTipsEnabled <Boolean>] - [-ManagedFolderHomepage <String>] - [-MapiHttpEnabled <Boolean>] - [-MaxConcurrentMigrations <Unlimited>] - [-MicrosoftExchangeRecipientEmailAddresses <ProxyAddressCollection>] - [-MicrosoftExchangeRecipientEmailAddressPolicyEnabled <Boolean>] - [-MicrosoftExchangeRecipientPrimarySmtpAddress <SmtpAddress>] - [-MicrosoftExchangeRecipientReplyRecipient <RecipientIdParameter>] - [-OAuth2ClientProfileEnabled <Boolean>] - [-OrganizationSummary <MultiValuedProperty>] - [-PermanentlyDeleteDisabled <Boolean>] - [-PreferredInternetCodePageForShiftJis <Int32>] - [-PublicComputersDetectionEnabled <Boolean>] - [-PublicFolderContentReplicationDisabled <Boolean>] - [-PublicFolderMailboxesLockedForNewConnections <Boolean>] - [-PublicFolderMailboxesMigrationComplete <Boolean>] - [-PublicFolderMigrationComplete <Boolean>] - [-PublicFoldersEnabled <PublicFoldersDeployment>] - [-PublicFoldersLockedForMigration <Boolean>] - [-ReadTrackingEnabled <Boolean>] - [-RefreshSessionEnabled <Boolean>] - [-RemotePublicFolderMailboxes <MultiValuedProperty>] - [-RequiredCharsetCoverage <Int32>] - [-SCLJunkThreshold <Int32>] - [-SiteMailboxCreationURL <Uri>] - [-SmtpActionableMessagesEnabled <Boolean>] - [-UMAvailableLanguages <MultiValuedProperty>] - [-UnblockUnsafeSenderPromptEnabled <Boolean>] - [-WACDiscoveryEndpoint <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-OrganizationConfig -DistributionGroupDefaultOU Users\Groups -DistributionGroupNameBlockedWordsList curse,bad,offensive -DistributionGroupNamingPolicy "DL_<GroupName>_<Department><CountryCode>" -``` - -This example creates a distribution group naming policy using the following configuration: - -Distribution groups will be created in the Users\\Groups container. - -The words curse, bad, and offensive will be blocked from being used in distribution group names. - -All distribution groups will be prefixed with "DL\_" and suffixed with an underscore (\_) and the user's department and country code. - -### Example 2 -```powershell -Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceBlockList -EwsBlockList $null -``` - -This example allows all client applications to use REST and EWS. - -### Example 3 -```powershell -Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceBlockList -EwsBlockList "OtherApps*" -``` - -This example allows all client applications to use REST and EWS, except those that are specified by the EwsBlockList parameter. - -### Example 4 -```powershell -Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceAllowList -EwsAllowList $null -``` - -This example prevents all client applications from using REST and EWS. - -### Example 5 -```powershell -Set-OrganizationConfig -EwsApplicationAccessPolicy EnforceAllowList -EwsAllowList "CorpApp*" -``` - -This example allows only the client applications specified by the EwsAllowList parameter to use REST and EWS. - -### Example 6 -```powershell -Set-OrganizationConfig -VisibleMeetingUpdateProperties "Location,Subject,Body,AllProperties:15" -``` - -In Exchange Online, this example results in meeting updates being auto-processed (meeting update messages aren't visible in attendee Inbox folders) except any changes to meeting location, subject and body as well as any property changes within 15 minutes of the meeting start time. - -## PARAMETERS - -### -ACLableSyncedObjectEnabled -This parameter is available only in on-premises Exchange. - -The ACLableSyncedObjectEnabled parameter specifies whether remote mailboxes in hybrid environments are stamped as ACLableSyncedMailboxUser. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActivityBasedAuthenticationTimeoutEnabled -The ActivityBasedAuthenticationTimeoutEnabled parameter specifies whether the timed logoff 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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActivityBasedAuthenticationTimeoutInterval -The ActivityBasedAuthenticationTimeoutInterval parameter specifies the time span for logoff. - -You enter this value as a time span: hh:mm:ss where hh = hours, mm = minutes and ss = seconds. - -Valid values for this parameter are from 00:05:00 to 08:00:00 (5 minutes to 8 hours). The default value is 06:00:00 (6 hours). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled -The ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter specifies whether to keep single sign-on 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdfsAudienceUris -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. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -For more information about configuring AD FS claims based authentication in Exchange, see [Use AD FS claims-based authentication with Outlook on the web](https://docs.microsoft.com/Exchange/clients/outlook-on-the-web/ad-fs-claims-based-auth). - -```yaml -Type: MultiValuedProperty -Parameter Sets: AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdfsAuthenticationConfiguration -This parameter is available only in on-premises Exchange. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: AdfsAuthenticationRawConfiguration -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdfsEncryptCertificateThumbprint -This parameter is available only in on-premises Exchange. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdfsIssuer -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. - -To get this value, open Windows PowerShell on the AD FS server and run the command Get-ADFSEndpoint -AddressPath /adfs/ls | Format-List FullUrl. - -```yaml -Type: Uri -Parameter Sets: AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdfsSignCertificateThumbprints -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. - -To get the thumbprint values of the primary and secondary token-signing certificates, open Windows PowerShell on the AD FS server and run the command Get-ADFSCertificate -CertificateType "Token-signing". For more information, see [Get-ADFSCertificate](https://go.microsoft.com/fwlink/p/?linkid=392706). - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AppsForOfficeEnabled -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: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsyncSendEnabled -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. - -- $false: Async send is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuditDisabled -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: - -- $true: Mailbox auditing is disabled for the organization. - -- $false: Allow mailbox auditing in the organization. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutodiscoverPartialDirSync -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. - -After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours to fully saturate across the cloud. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoEnableArchiveMailbox -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoExpandingArchive -This parameter is available only in the cloud-based service. - -The AutoExpandingArchive switch enables the unlimited archiving feature (called auto-expanding archiving) in an Exchange Online organization. You don't need to specify a value with this switch. - -After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. Note that a user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled. - -```yaml -Type: SwitchParameter -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BookingsEnabled -This parameter is available only in the cloud-based service. - -The BookingsEnabled parameter specifies whether to enable Microsoft Bookings in an Exchange Online organization. Valid values are: - -- $true: Bookings are enabled. - -- $false: Bookings are disabled. This is the default value. - -Microsoft Bookings is an online and mobile app for small businesses who provide services to customers on an appointment basis. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BookingsPaymentsEnabled -This parameter is available only in the cloud-based service. - -The BookingsPaymentsEnabled parameter specifies whether to enable online payment node inside Bookings. Valid values are: - -- $true: Online payments are enabled. - -- $false: Online payments are disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BookingsSocialSharingRestricted -This parameter is available only in the cloud-based service. - -The BookingsSocialSharingRestricted parameter allows you to control whether, or not, your users can see social sharing options inside Bookings. Valid values are: - -- $true: Social sharing options are restricted. - -- $false: Users can see social sharing options inside Bookings. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ByteEncoderTypeFor7BitCharsets -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. - -- 1: Always use QP (quoted-printable) encoding for HTML and plain text. - -- 2: Always use Base64 encoding for HTML and plain text. - -- 5: Use QP encoding for HTML and plain text unless line wrapping is enabled in plain text. If line wrapping is enabled, use 7-bit encoding for plain text. - -- 6: Use Base64 encoding for HTML and plain text, unless line wrapping is enabled in plain text. If line wrapping is enabled in plain text, use Base64 encoding for HTML, and use 7-bit encoding for plain text. - -- 13: Always use QP encoding for HTML. Always use 7-bit encoding for plain text. - -- 14: Always use Base64 encoding for HTML. Always use 7-bit encoding for plain text. - -If no value is specified, Exchange always uses QP encoding for HTML and plain text. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CalendarVersionStoreEnabled -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorsActionableMessagesEnabled -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. - -- $false: Action buttons in connector cards are disabled. - -For more information about actionable messages in connected apps, see [Connect apps to your inbox in Outlook on the web](https://go.microsoft.com/fwlink/p/?LinkId=845310). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorsEnabled -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. - -- $false: Connectors are disabled. - -The workloads that are affected by this parameter are Outlook, SharePoint, Teams, and Yammer. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorsEnabledForOutlook -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: - -- $true: Connectors are enabled. This is the default value. - -- $false: Connectors are disabled. - -To enable and disable the ability to use connectors on specific Office 365 groups, set the value of this parameter to $true, and then use the ConnectorsEnabled switch on the Set-UnifiedGroup cmdlet. - -For more information about connectors for Outlook on the web, see [Connect apps to your inbox in Outlook on the web](https://go.microsoft.com/fwlink/p/?LinkId=845310). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorsEnabledForSharepoint -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: - -- $true: Connectors are enabled. This is the default value. - -- $false: Connectors are disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorsEnabledForTeams -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: - -- $true: Connectors are enabled. This is the default value. - -- $false: Connectors are disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorsEnabledForYammer -This parameter is available only in the cloud-based service. - -The ConnectorsEnabledForYammer parameter specifies whether to enable or disable connected apps on Yammer. Valid values are: - -- $true: Connectors are enabled. This is the default value. - -- $false: Connectors are disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomerFeedbackEnabled -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. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataClassifications -This parameter is available only in on-premises Exchange. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultAuthenticationPolicy -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 - -- Distinguished name (DN) - -- GUID - -To remove the default policy assignment for the organization, use the value $null. - -You create authentication policies with the New-AuthenticationPolicy cmdlet to block or selectively allow Basic authentication or (in Exchange 2019 CU2 or later) other legacy authentication methods. - -```yaml -Type: AuthPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultGroupAccessType -This parameter is available only in the cloud-based service. - -The DefaultGroupAccessType parameter specifies the default access type for Office 365 groups. Valid values are: - -- Public - -- Private (this is the default value) - -```yaml -Type: ModernGroupObjectType -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: Private -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultPublicFolderAgeLimit -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). - -```yaml -Type: EnhancedTimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultPublicFolderDeletedItemRetention -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: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultPublicFolderIssueWarningQuota -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -The valid input range for this parameter is from 0 through 2199023254529 bytes(2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultPublicFolderMaxItemSize -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultPublicFolderMovedItemRetention -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://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/set-publicfolder). - -```yaml -Type: EnhancedTimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultPublicFolderProhibitPostQuota -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DirectReportsGroupAutoCreationEnabled -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 Office 365 groups. Valid values are: - -- $true: The automatic creation of direct report Office 365 groups is enabled. - -- $false: The automatic creation of direct report Office 365 groups is disabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionGroupDefaultOU -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionGroupNameBlockedWordsList -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionGroupNamingPolicy -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 `"prefix<GroupName>suffix"`. The value `<GroupName>` is a literal value that you must always include. - -You can use the following user attributes. The actual values are determined by the user who creates the group: - -- `<City>` - -- `<Company>` - -- `<CountryCode>` - -- `<CountryOrRegion> - -- `<CustomAttribute1>` to `<CustomAttribute15>` - -- `<Department>` - -- `<ExtensionCustomAttribute1>` to `<ExtensionCustomAttribute5>` - -- `<Office>` - -- `<StateOrProvince>` - -- `<Title>` - -For example: `"DL_<StateOrProvince>_<GroupName>"`, `"<StateOrProvince>-<City>-<Office>-<GroupName>"` or `"<GroupName> <CustomAttribute1>"`. - -```yaml -Type: DistributionGroupNamingPolicy -Parameter Sets: (All) -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 -``` - -### -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. - -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. - -```yaml -Type: Fqdn -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ElcProcessingDisabled -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: - -- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. Note that this setting will be ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox. - -- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndUserDLUpgradeFlowsDisabled -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 Office 365 groups in an Exchange Online organization. Valid values are: - -- $true: Users can upgrade distribution groups that they own to Office 365 groups. - -- $false: Users can't upgrade distribution groups that they own to Office 365 groups. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowEntourage -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowList -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowMacOutlook -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsAllowOutlook -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsApplicationAccessPolicy -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. - -- EnforceBlockList: All applications are allowed to access EWS and REST, except for the applications specified by the EwsBlockList parameter. - -Note that if the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsBlockList -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EwsEnabled -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. - -- $false: All EWS access is disabled. - -- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This is the default value. - -This parameter has no affect on access to REST. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeNotificationEnabled -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. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeNotificationRecipients -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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FocusedInboxOn -This parameter is available only in the cloud-based service. - -The FocusedInboxOn parameter enables or disables Focused Inbox for the organization. Valid values are: - -- $true: Focused Inbox is enabled. - -- $false: Focused Inbox is disabled. - -To disable Focused Inbox on specific mailboxes, enable Focused Inbox for the organization, and then use the Set-FocusedInbox cmdlet. - -Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is available or functional only in Exchange Server 2010. - -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: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HierarchicalAddressBookRoot -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -Setting a value for this parameter enables the hierarchical address book to be automatically displayed in Outlook for the organization. - -The default value is blank. To reset this parameter, use the value $null. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Industry -This parameter is available only in on-premises Exchange. - -The Industry parameter specifies the industry that best represents your organization. - -```yaml -Type: IndustryType -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPListBlocked -This parameter is available only in the cloud-based service. - -The IPListBlocked parameter specifies the blocked IP addresses that aren't allowed to connect to Exchange Online organization. These settings affect client connections that use Basic authentication where on-premises Active Directory Federation Services (ADFS) servers federate authentication with Azure Active Directory. Note that the new settings might take up to 4 hours to fully propagate across the service. - -This parameter accepts IPv4 or IPv6 addresses in the following formats: - -- Single IP address: For example, 192.168.1.1 or fe80::39bd:88f7:6969:d223%11. - -- IP address range high-low: For example, 192.168.0.1-192.168.0.254. - -- IP address range with subnet mask: For example, 192.168.8.2(255.255.255.0). - -- Classless Inter-Domain Routing (CIDR) IP: For example, 192.168.3.1/24 or 2001:0DB8::CD3/60. - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -This parameter has a limit of approximately 1200 entries. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsAgendaMailEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsExcludedFromOffboardMigration -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. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsExcludedFromOnboardMigration -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. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsFfoMigrationInProgress -This parameter is available only in on-premises Exchange. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LeanPopoutEnabled -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. - -- $false: Lean pop-outs are disabled. This is the default value. - -Notes: - -- Lean pop-outs aren't available for messages that contain attachments or information rights management (IRM) restrictions. - -- Outlook add-ins and Skype for Business Online presence aren't available with lean pop-outs. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LinkPreviewEnabled -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. - -- $false: Link preview of URLs in email messages is not allowed. Users can't enable link preview in their Outlook on the web settings. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTipsAllTipsEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTipsExternalRecipientsTipsEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTipsGroupMetricsEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTipsLargeAudienceThreshold -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTipsMailboxSourcedTipsEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedFolderHomepage -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. - -```yaml -Type: String -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MapiHttpEnabled -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: - -- $true: Access to mailboxes by using MAPI over HTTP is enabled. This is the default value. - -- $false: Access to mailboxes by using MAPI over HTTP is disabled. - -You can use the MapiHttpEnabled parameter on the Set-CASMailbox cmdlet to override the global MAPI over HTTP settings for individual users. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxConcurrentMigrations -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. - -```yaml -Type: Unlimited -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MicrosoftExchangeRecipientEmailAddresses -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. - -Email addresses that you specify by using the MicrosoftExchangeRecipientEmailAddresses parameter replace any existing email addresses already configured. - -```yaml -Type: ProxyAddressCollection -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MicrosoftExchangeRecipientEmailAddressPolicyEnabled -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. - -If you change the value of the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter from $false to $true, any email addresses that you defined by using the MicrosoftExchangeRecipientEmailAddresses parameter are preserved. However, the value of the MicrosoftExchangeRecipientPrimarySmtpAddress parameter reverts to MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@\<Accepted Domain in Highest Priority Email Address Policy\>. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MicrosoftExchangeRecipientPrimarySmtpAddress -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. - -If you modify the value of the MicrosoftExchangeRecipientPrimarySmtpAddress parameter, the value is automatically added to the list of email addresses defined in the MicrosoftExchangeRecipientEmailAddresses parameter. - -The MicrosoftExchangeRecipientPrimarySmtpAddress parameter is meaningful only if the Exchange recipient has more than one defined SMTP email address. If the MicrosoftExchangeRecipientEmailAddresses parameter has only one defined SMTP email address, the value of the MicrosoftExchangeRecipientPrimarySmtpAddress parameter and the MicrosoftExchangeRecipientEmailAddresses parameter are the same. - -```yaml -Type: SmtpAddress -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MicrosoftExchangeRecipientReplyRecipient -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OAuth2ClientProfileEnabled -The OAuth2ClientProfileEnabled parameter enables or disables modern authentication in the Exchange organization. Valid values are: - -- $true: Modern authentication is enabled. - -- $false: Modern authentication is disabled. - -Modern authentication is based on the Active Directory Authentication Library (ADAL) and OAuth 2.0, and enables authentication features like multi-factor authentication (MFA), certificate-based authentication (CBA), and third-party SAML identity providers. - -When you enable modern authentication in Exchange Online, we recommend that you also enable it in Skype for Business Online. For more information, see [Skype for Business Online: Enable your tenant for modern authentication](https://aka.ms/SkypeModernAuth). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationSummary -This parameter is available only in on-premises Exchange. - -The OrganizationSummary parameter specifies a summarized description that best represents your organization. - -```yaml -Type: MultiValuedProperty -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutlookMobileGCCRestrictionsEnabled -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 Office 365 US Government Community Cloud (GCC) customers. Valid values are: - -- $true: Disable features that aren't FedRAMP compliant for GCC customers. This is the default value for all GCC customers. - -- $false: Enable features that aren't FedRAMP compliant for GCC customers. - -The Outlook for iOS and Android feature and services that are not FedRAMP compliant for Office 365 US Government customers include: - -- Multi-account support - -- Third-party services - -- HelpShift and in-app support - -- Any Microsoft services that are outside the Office 365 US Government Community Cloud (for example, Bing and Cortana). - - For a full list of Features and services that are not FedRAMP compliant for GCC customers, see [Services and features of Outlook for iOS and Android that aren't available for Government Community Cloud users](https://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/outlook-for-ios-and-android-in-the-government-cloud#services-and-features-not-available). - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutlookMobileHelpShiftEnabled -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutlookMobileSingleAccountEnabled -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutlookPayEnabled -This parameter is available only in the cloud-based service. - -The OutlookPayEnabled parameter enables or disables [Payments in Outlook](https://support.office.com/article/1196e7e6-c096-44f1-a18a-9df3af832a48) in the Office 365 organization. Valid values are: - -- $true: Payments in Outlook are enabled. - -- $False: Payments in Outlook are disabled. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermanentlyDeleteDisabled -This parameter is available or functional only in Exchange Server 2010. - -The PermanentlyDeleteDisabled parameter specifies whether to disable the PermanentlyDelete retention action for messaging records management (MRM). Valid values are: - -- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing polices, block the creation of policies with the PermanentlyDelete action or notify users that thePermanentlyDelete action won't actually take effect. - -- $false The PermanentlyDelete retention action is enabled. This is the default value. - -A message that's permanently deleted can't be recovered by using the Recoverable Items folder. Additionally, permanently deleted messages aren't returned by a Discovery search, unless litigation hold or single item recovery is enabled for the mailbox. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PerTenantSwitchToESTSEnabled -This parameter is available only in the cloud-based service. - -This parameter has been deprecated and is no longer used. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredInternetCodePageForShiftJis -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicComputersDetectionEnabled -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: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderContentReplicationDisabled -This parameter is available or functional 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. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderMailboxesLockedForNewConnections -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: - -- $true: Users aren't allowed to make new connections to public folder mailboxes. You use this setting during the final stages of public folder migrations. - -- $false: Users are allowed to make new connections to public folder mailboxes. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderMailboxesMigrationComplete -This parameter is available only in on-premises Exchange. - -The PublicFolderMailboxesMigrationComplete parameter is used during public folder migration. - -- $true: Queued messages are rerouted to the new destination. - -- $false (This is the default value) - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderMigrationComplete -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. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFoldersEnabled -The PublicFoldersEnabled parameter specifies how public folders are deployed in your organization. This parameter uses one of the following values. - -- Local: The public folders are deployed locally in your organization. - -- Remote: The public folders are deployed in the remote forest. - -- None: No public folders are deployed for this organization. - -```yaml -Type: PublicFoldersDeployment -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderShowClientControl -This parameter is available only in the cloud-based service. - -The PublicFolderShowClientControl parameter enables or disables access to public folders in Microsoft Outlook. Valid values are: - -- $true: Users can access public folders in Outlook if the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is set to the value $true (the default value is $false). - -- $false: User can't access public folders in Outlook. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFoldersLockedForMigration -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. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadTrackingEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RefreshSessionEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemotePublicFolderMailboxes -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: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredCharsetCoverage -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SCLJunkThreshold -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. - -```yaml -Type: Int32 -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteMailboxCreationURL -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: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SmtpActionableMessagesEnabled -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. - -- $false: Action buttons in email messages are disabled. - -```yaml -Type: Boolean -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UMAvailableLanguages -This parameter is available only in on-premises Exchange. - -This parameter has been deprecated and is no longer used. - -```yaml -Type: MultiValuedProperty -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnblockUnsafeSenderPromptEnabled -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VisibleMeetingUpdateProperties -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. - -This parameter uses the syntax: `"MeetingProperty1:MeetingStartTimeWithinXMinutes1,MeetingProperty2:MeetingStartTimeWithinXMinutes2,...MeetingPropertyN:MeetingStartTimeWithinXMinutesN"`. - -The valid meeting properties to monitor for updates are: - -- Location: The meeting location field. - -- Subject: The meeting subject or title. - -- Sensitivity: The sensitivity (privacy) of the event. - -- Body: The meeting body or description. - -- OnlineMeetingLinks: The meeting join URL. - -- AllowForwarding: The option to allow or prevent forwarding of meetings. - -- RequestResponses: The option on whether responses are requested. - -- AllowNewTimeProposals: The option to allow or prevent new time proposals. - -- ShowAs: The free/busy state of the meeting: Free, Tentative, Busy, Working elsewhere, or Away/Out of office. - -- Reminder: The reminder time. - -- AllProperties: Any meeting change. - -If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property will result in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series. - -The default value is `"Location,AllProperties:15"`: changes to the meeting location at any time, or changes to other meeting properties within 15 minutes of the meeting start time results in visible meeting update messages. - -There are three scenarios where meeting update messages are not auto-processed regardless of the values specified in this parameter (in these scenarios, attendees will always see meeting update messages in their Inbox): - -- The update contains a change to the meeting date, time, or recurrence pattern. - -- The meeting message is received for a delegated shared calendar. - -- The receiving attendee is @ mentioned in the meeting body. - -- The attendee has not yet responded to the meeting. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WACDiscoveryEndpoint -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. - -Office Online Server enables users to view supported file attachments in Outlook on the web (formerly known as Outlook Web App). - -```yaml -Type: String -Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebPushNotificationsDisabled -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: - -- $true: Web Push Notifications are disabled. - -- $false: Web Push Notifications are enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebSuggestedRepliesDisabled -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: - -- $true: Suggested Replies are disabled. - -- $false: Suggested Replies are enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Default -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-audit/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AdminAuditLogConfig.md deleted file mode 100644 index 08b78a977b..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AdminAuditLogConfig.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/get-adminauditlogconfig -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Get-AdminAuditLogConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Get-AdminAuditLogConfig - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-AdminAuditLogConfig cmdlet to view the administrator audit logging configuration settings. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AdminAuditLogConfig [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -When audit logging is enabled, a log entry is created for each cmdlet that's run, excluding Get cmdlets. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AdminAuditLogConfig | Format-List -``` - -This example displays the administrator audit logging settings. The output of the Get-AdminAuditLogConfig cmdlet is piped to the Format-List cmdlet. For more information about piping and the Format-List cmdlet, see the following topics: - -- [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) - -- [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help) - -## PARAMETERS - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-audit/Get-AuditConfig.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfig.md deleted file mode 100644 index 3b94dfd8fa..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfig.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/get-auditconfig -applicable: Office 365 Security & Compliance Center -title: Get-AuditConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-AuditConfig - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-AuditConfig cmdlet to view the auditing configuration in the Security & Compliance Center. The auditing configuration specifies where auditing is allowed in Microsoft Office 365. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AuditConfig [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-AuditConfig -``` - -This example shows the auditing configuration in the Security & Compliance Center. - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfigurationPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfigurationPolicy.md deleted file mode 100644 index ab711cdad2..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfigurationPolicy.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/get-auditconfigurationpolicy -applicable: Office 365 Security & Compliance Center -title: Get-AuditConfigurationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-AuditConfigurationPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-AuditConfigurationPolicy cmdlet to view audit configuration policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AuditConfigurationPolicy [[-Identity] <PolicyIdParameter>] [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-AuditConfigurationPolicy | Format-List Name,Enabled,Workload,Priority,*Location -``` - -This example lists summary information about all audit configuration policies. - -### Example 2 -```powershell -Get-AuditConfigurationPolicy -Identity 8d4d2060-ee8e-46a8-8d72-24922956fba5 -``` - -This examples lists details about the audit configuration policy named 8d4d2060-ee8e-46a8-8d72-24922956fba5. - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the audit configuration policy that you want to view. The name of the policy is a GUID value. For example, 8d4d2060-ee8e-46a8-8d72-24922956fba5. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfigurationRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfigurationRule.md deleted file mode 100644 index b8592b0857..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-AuditConfigurationRule.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/get-auditconfigurationrule -applicable: Office 365 Security & Compliance Center -title: Get-AuditConfigurationRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-AuditConfigurationRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-AuditConfigurationRule cmdlet to view audit configuration rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AuditConfigurationRule [[-Identity] <ComplianceRuleIdParameter>] [-DomainController <Fqdn>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-AuditConfigurationRule | Format-List Name,Workload,AuditOperation,Policy -``` - -This example lists summary information about all audit configuration rules. - -### Example 2 -```powershell -Get-AuditConfigurationRule 989a3a6c-dc40-4fa4-8307-beb3ece992e9 -``` - -This example lists details about the audit configuration rule named 989a3a6c-dc40-4fa4-8307-beb3ece992e9. - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the audit configuration rule that you want to view. The name of the rule is a GUID value. For example, 989a3a6c-dc40-4fa4-8307-beb3ece992e9. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-MailboxAuditBypassAssociation.md deleted file mode 100644 index 70c63304e9..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-MailboxAuditBypassAssociation.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-MailboxAuditBypassAssociation - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve user or computer accounts configured to bypass mailbox audit logging. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxAuditBypassAssociation [[-Identity] <MailboxAuditBypassAssociationIdParameter>] - [-DomainController <Fqdn>] [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -When you configure a user or computer account to bypass mailbox audit logging, access or actions taken by the user or computer account to any mailbox isn't logged. By bypassing trusted user or computer accounts that need to access mailboxes frequently, you can reduce the noise in mailbox audit logs. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxAuditBypassAssociation -ResultSize unlimited -``` - -This example retrieves all user or computer accounts configured for mailbox audit logging bypass. - -### Example 2 -```powershell -Get-MailboxAuditBypassAssociation -Identity "Svc-MyApplication" -``` - -This example retrieves the mailbox audit bypass association for the Svc-MyApplication account. - -## PARAMETERS - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies a user or computer account to retrieve audit logging bypass association for. - -```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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -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 -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-audit/Get-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-UnifiedAuditLogRetentionPolicy.md deleted file mode 100644 index 304584eda4..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Get-UnifiedAuditLogRetentionPolicy.md +++ /dev/null @@ -1,290 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/get-unifiedauditlogretentionpolicy -applicable: Office 365 Security & Compliance Center -title: Get-UnifiedAuditLogRetentionPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-UnifiedAuditLogRetentionPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-UnifiedAuditLogRetentionPolicy cmdlet to view the properties of the audit log retention policies in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-UnifiedAuditLogRetentionPolicy - [-Operation <String>] - [-RecordType <AuditRecordType>] - [-RetentionDuration <UnifiedAuditLogRetentionDuration>] - [-UserId <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Audit log retention policies are used to specify a retention duration for audit logs for that are generated by admin and user activity. An audit log retention policy can specify the retention duration based on the type of audited activities, the Office 365 service that activities are performed in, or the users who performed the activities. For more information, see [Manage audit log retention policies](https://docs.microsoft.com/microsoft-365/compliance/audit-log-retention-policies). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-UnifiedAuditLogRetentionPolicy | Sort-Object -Property Priority -Descending | Format-List Priority,Name,Description,RecordTypes,Operations,UserIds,RetentionDuration -``` - -This example lists the configurable properties for all audit log retention policies in your organization. The command also lists the policies in order of highest to lowest priority. - -### Example 2 -```powershell -Get-UnifiedAuditLogRetentionPolicy -RecordType ExchangeItem | Format-List Name,Description,RecordTypes,Operations,UserIds,RetentionDuration,Priority -``` - -This example lists the configurable properties for all audit log retention policies that apply to audit records the record type of ExchangeItem. - - -## PARAMETERS - -### -Operation -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://go.microsoft.com/fwlink/p/?LinkId=708432). - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordType -The RecordType parameter filters the results by the record types that are defined in the policy. Valid values are: - -- AeD - -- AirInvestigation - -- ApplicationAudit - -- AzureActiveDirectory - -- AzureActiveDirectoryAccountLogon - -- AzureActiveDirectoryStsLogon - -- CRM - -- Campaign - -- ComplianceDLPExchange - -- ComplianceDLPSharePoint - -- ComplianceDLPSharePointClassification - -- ComplianceSupervisionExchange - -- CustomerKeyServiceEncryption - -- DLPEndpoint - -- DataCenterSecurityCmdlet - -- DataGovernance - -- DataInsightsRestApiAudit - -- Discovery - -- ExchangeAdmin - -- ExchangeAggregatedOperation - -- ExchangeItem - -- ExchangeItemAggregated - -- ExchangeItemGroup - -- HRSignal - -- HygieneEvent - -- InformationBarrierPolicyApplication - -- InformationWorkerProtection - -- Kaizala - -- LabelContentExplorer - -- MIPLabel - -- MailSubmission - -- MicrosoftFlow - -- MicrosoftForms - -- MicrosoftStream - -- MicrosoftTeams - -- MicrosoftTeamsAdmin - -- MicrosoftTeamsAnalytics - -- MicrosoftTeamsDevice - -- MicrosoftTeamsShifts - -- MipAutoLabelExchangeItem - -- MipAutoLabelSharePointItem - -- MipAutoLabelSharePointPolicyLocation - -- OfficeNative - -- OneDrive - -- PowerAppsApp - -- PowerAppsPlan - -- PowerBIAudit - -- Project - -- Quarantine - -- SecurityComplianceAlerts - -- SecurityComplianceCenterEOPCmdlet - -- SecurityComplianceInsights - -- SharePoint - -- SharePointCommentOperation - -- SharePointContentTypeOperation - -- SharePointFieldOperation - -- SharePointFileOperation - -- SharePointListItemOperation - -- SharePointListOperation - -- SharePointSharingOperation - -- SkypeForBusinessCmdlets - -- SkypeForBusinessPSTNUsage - -- SkypeForBusinessUsersBlocked - -- Sway - -- SyntheticProbe - -- TeamsHealthcare - -- ThreatFinder - -- ThreatIntelligence - -- ThreatIntelligenceAtpContent - -- ThreatIntelligenceUrl - -- WorkplaceAnalytics - -- Yammer - -```yaml -Type: AuditRecordType -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter filters the policy results by the retention duration specified in the policy. Valid values are: - -- ThreeMonths - -- SixMonths - -- NineMonths - -- TwelveMonths - -```yaml -Type: UnifiedAuditLogRetentionDuration -Parameter Sets: (All) -Aliases: -Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserId -The UserIds parameter filters the policy results by the ID of the users who are specified in the policy. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AuditConfigurationPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AuditConfigurationPolicy.md deleted file mode 100644 index 6feb0d9541..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AuditConfigurationPolicy.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/new-auditconfigurationpolicy -applicable: Office 365 Security & Compliance Center -title: New-AuditConfigurationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-AuditConfigurationPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-AuditConfigurationPolicy cmdlet to create audit configuration policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-AuditConfigurationPolicy - -Workload <Workload> - [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-AuditConfigurationPolicy -Workload SharePoint -``` - -This example creates an audit configuration policy for Microsoft SharePoint Online. - -## PARAMETERS - -### -Workload -The Workload parameter specifies where auditing is allowed. Valid values are: - -- Exchange - -- InTune - -- OneDriveForBusiness - -- SharePoint - -```yaml -Type: Workload -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AuditConfigurationRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AuditConfigurationRule.md deleted file mode 100644 index 47824af80e..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-AuditConfigurationRule.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/new-auditconfigurationrule -applicable: Office 365 Security & Compliance Center -title: New-AuditConfigurationRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-AuditConfigurationRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-AuditConfigurationRule cmdlet to create audit configuration rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-AuditConfigurationRule -AuditOperation <MultiValuedProperty> - -Workload <Workload> - [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-AuditConfigurationRule -Workload SharePoint -AuditOperation Delete -``` - -This example creates a new audit configuration rule for Microsoft SharePoint Online that audits delete operations. - -## PARAMETERS - -### -AuditOperation -The AuditOperation parameter specifies the operations that are audited by the rule. Valid values are: - -- Administrate - -- CheckIn - -- CheckOut - -- Count - -- CreateUpdate - -- Delete - -- Forward - -- MoveCopy - -- PermissionChange - -- ProfileChange - -- SchemaChange - -- Search - -- SendAsOthers - -- View - -- Workflow - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Workload -The Workload parameter specifies where the audit configuration policy applies. Valid values are: - -- Exchange - -- InTune - -- OneDriveForBusiness - -- SharePoint - -```yaml -Type: Workload -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-UnifiedAuditLogRetentionPolicy.md deleted file mode 100644 index a909ac6f5d..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/New-UnifiedAuditLogRetentionPolicy.md +++ /dev/null @@ -1,385 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/new-unifiedauditlogretentionpolicy -applicable: Office 365 Security & Compliance Center -title: New-UnifiedAuditLogRetentionPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-UnifiedAuditLogRetentionPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-UnifiedAuditLogRetentionPolicy cmdlet to create audit log retention policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-UnifiedAuditLogRetentionPolicy [-Name] <String> -Priority <Int32> -RetentionDuration <UnifiedAuditLogRetentionDuration> - [-Confirm] - [-Description <String>] - [-Operations <MultiValuedProperty>] - [-RecordTypes <MultiValuedProperty>] - [-UserIds <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Audit log retention policies are used to specify a retention duration for audit logs for that are generated by admin and user activity. An audit log retention policy can specify the retention duration based on the type of audited activities, the Office 365 service that activities are performed in, or the users who performed the activities. For more information, see [Manage audit log retention policies](https://docs.microsoft.com/microsoft-365/compliance/audit-log-retention-policies). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-UnifiedAuditLogRetentionPolicy -Name "Microsoft Teams Audit Policy" -Description "One year retention policy for all Microsoft Teams activities" -RecordTypes MicrosoftTeams -RetentionDuration TwelveMonths -Priority 100 -``` - -This example creates an audit log retention policy that retains all audit logs related to Microsoft Teams events for one year. - -### Example 2 -```powershell -New-UnifiedAuditLogRetentionPolicy -Name "SearchQueryPerformed by app@sharepoint" -Description "90 day retention policy for noisy SharePoint events" -RecordTypes SharePoint -Operations SearchQueryPerformed -UserIds "app@sharepoint" -RetentionDuration ThreeMonths -Priority 10000 -``` - -This example creates an audit log retention policy that retains all audit logs for the SearchQueryPerformed activity performed by the app@sharepoint service account for 90 days. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -The Priority parameter specifies a priority value for the policy that determines the order of policy processing. A higher integer value indicates a higher priority, the value 10000 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 8 existing policies: - -- Valid priority values for the existing 8 policies are from 7 through 0. - -- Valid priority values for a new policy (the 9th policy) are from 8 through 0. - -You must use a unique priority value when creating new audit log retention policies. Any custom audit log retention policy that you create will take precedence over the default audit log retention policy. For more information, see [Advanced audit in Microsoft 365](https://docs.microsoft.com/microsoft-365/compliance/advanced-audit). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter specifies how long audit log records are kept. Valid values are: - -- ThreeMonths - -- SixMonths - -- NineMonths - -- TwelveMonths - -```yaml -Type: UnifiedAuditLogRetentionDuration -Parameter Sets: (All) -Aliases: -Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operations -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://go.microsoft.com/fwlink/p/?LinkId=708432). - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If you use this parameter, you must also use the RecordTypes parameter to specify the record type. You can't use this parameter if you've specified more than one value for the RecordTypes parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordTypes -The RecordTypes parameter specifies the audit logs of a specific record type that are retained by the policy. You can specify multiple values separated by commas. If you specify more than one value, you can't use the Operations parameter. Valid values are: - -- AeD - -- AirInvestigation - -- ApplicationAudit - -- AzureActiveDirectory - -- AzureActiveDirectoryAccountLogon - -- AzureActiveDirectoryStsLogon - -- CRM - -- Campaign - -- ComplianceDLPExchange - -- ComplianceDLPSharePoint - -- ComplianceDLPSharePointClassification - -- ComplianceSupervisionExchange - -- CustomerKeyServiceEncryption - -- DLPEndpoint - -- DataCenterSecurityCmdlet - -- DataGovernance - -- DataInsightsRestApiAudit - -- Discovery - -- ExchangeAdmin - -- ExchangeAggregatedOperation - -- ExchangeItem - -- ExchangeItemAggregated - -- ExchangeItemGroup - -- HRSignal - -- HygieneEvent - -- InformationBarrierPolicyApplication - -- InformationWorkerProtection - -- Kaizala - -- LabelContentExplorer - -- MIPLabel - -- MailSubmission - -- MicrosoftFlow - -- MicrosoftForms - -- MicrosoftStream - -- MicrosoftTeams - -- MicrosoftTeamsAdmin - -- MicrosoftTeamsAnalytics - -- MicrosoftTeamsDevice - -- MicrosoftTeamsShifts - -- MipAutoLabelExchangeItem - -- MipAutoLabelSharePointItem - -- MipAutoLabelSharePointPolicyLocation - -- OfficeNative - -- OneDrive - -- PowerAppsApp - -- PowerAppsPlan - -- PowerBIAudit - -- Project - -- Quarantine - -- SecurityComplianceAlerts - -- SecurityComplianceCenterEOPCmdlet - -- SecurityComplianceInsights - -- SharePoint - -- SharePointCommentOperation - -- SharePointContentTypeOperation - -- SharePointFieldOperation - -- SharePointFileOperation - -- SharePointListItemOperation - -- SharePointListOperation - -- SharePointSharingOperation - -- SkypeForBusinessCmdlets - -- SkypeForBusinessPSTNUsage - -- SkypeForBusinessUsersBlocked - -- Sway - -- SyntheticProbe - -- TeamsHealthcare - -- ThreatFinder - -- ThreatIntelligence - -- ThreatIntelligenceAtpContent - -- ThreatIntelligenceUrl - -- WorkplaceAnalytics - -- Yammer - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserIds -The UserIds parameter specifies the audit logs that are retained by the policy based on the ID of the user who performed the action. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-AuditConfigurationPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-AuditConfigurationPolicy.md deleted file mode 100644 index 273eb80548..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-AuditConfigurationPolicy.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/remove-auditconfigurationpolicy -applicable: Office 365 Security & Compliance Center -title: Remove-AuditConfigurationPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-AuditConfigurationPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-AuditConfigurationPolicy cmdlet to remove audit configuration policies from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-AuditConfigurationPolicy [-Identity] <PolicyIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-AuditConfigurationPolicy -Identity 8d4d2060-ee8e-46a8-8d72-24922956fba5 -``` - -This example removes the audit configuration policy named 8d4d2060-ee8e-46a8-8d72-24922956fba5. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the audit configuration policy that you want to remove. The name of the policy is a GUID value. For example, 8d4d2060-ee8e-46a8-8d72-24922956fba5. You can find the name value by running the following command: Get-AuditConfigurationPolicy | Format-List Name,Enabled,Workload,Priority,\*Location. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-AuditConfigurationRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-AuditConfigurationRule.md deleted file mode 100644 index 8ed4fa3d29..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-AuditConfigurationRule.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/remove-auditconfigurationrule -applicable: Office 365 Security & Compliance Center -title: Remove-AuditConfigurationRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-AuditConfigurationRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-AuditConfigurationRule cmdlet to remove audit configuration rules from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-AuditConfigurationRule [-Identity] <PolicyIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-AuditConfigurationRule 989a3a6c-dc40-4fa4-8307-beb3ece992e9 -``` - -This example removes the audit configuration rule named 989a3a6c-dc40-4fa4-8307-beb3ece992e9. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the audit configuration rule that you want to remove. The name of the rule is a GUID value. For example, 989a3a6c-dc40-4fa4-8307-beb3ece992e9. You can find the name value by running the following command: Get-AuditConfigurationRule | Format-List Name,Workload,AuditOperation,Policy. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-UnifiedAuditLogRetentionPolicy.md deleted file mode 100644 index afb92bca89..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Remove-UnifiedAuditLogRetentionPolicy.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/remove-unifiedauditlogretentionpolicy -applicable: Office 365 Security & Compliance Center -title: Remove-UnifiedAuditLogRetentionPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-UnifiedAuditLogRetentionPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-UnifiedAuditLogRetentionPolicy cmdlet to delete audit log retention policies. It might take up to 30 minutes for the policy to be completely removed. For more information, see [Manage audit log retention policies](https://docs.microsoft.com/microsoft-365/compliance/audit-log-retention-policies). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-UnifiedAuditLogRetentionPolicy [-Identity] <PolicyIdParameter> - [-Confirm] - [-DomainController <Fqdn>] - [-ForceDeletion] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-UnifiedAuditLogRetentionPolicy -Identity "SearchQueryPerformed by app@sharepoint" -``` - -This example deletes the audit log retention policy named "SearchQueryPerformed by app@sharepoint". - -## PARAMETERS - -### -Identity -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 - -- Distingished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-AdminAuditLog.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-AdminAuditLog.md deleted file mode 100644 index b2e4062eb1..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-AdminAuditLog.md +++ /dev/null @@ -1,326 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/search-adminauditlog -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Search-AdminAuditLog -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Search-AdminAuditLog - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Search-AdminAuditLog cmdlet to search the contents of the administrator audit log. Administrator audit logging records when a user or administrator makes a change in your organization (in the Exchange admin center or by using cmdlets). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Search-AdminAuditLog - [-Cmdlets <MultiValuedProperty>] - [-DomainController <Fqdn>] - [-EndDate <ExDateTime>] - [-ExternalAccess <Boolean>] - [-IsSuccess <Boolean>] - [-ObjectIds <MultiValuedProperty>] - [-Parameters <MultiValuedProperty>] - [-ResultSize <Int32>] - [-StartDate <ExDateTime>] - [-StartIndex <Int32>] - [-UserIds <MultiValuedProperty>] - [<CommonParameters>] -``` - -## DESCRIPTION -If you run the Search-AdminAuditLog cmdlet without any parameters, up to 1,000 log entries are returned by default. - -Note: In Exchange Online, if you don't use the StartDate or EndDate parameters, only results from the last 14 days are returned. - -For more information about the structure and properties of the audit log, [Administrator audit log structure](https://docs.microsoft.com/Exchange/policy-and-compliance/admin-audit-logging/log-structure). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Search-AdminAuditLog -Cmdlets New-RoleGroup,New-ManagementRoleAssignment -``` - -This example finds all the administrator audit log entries that contain either the New-RoleGroup or the New-ManagementRoleAssignment cmdlet. - -### Example 2 -```powershell -Search-AdminAuditLog -Cmdlets Set-Mailbox -Parameters UseDatabaseQuotaDefaults,ProhibitSendReceiveQuota,ProhibitSendQuota -StartDate 01/24/2018 -EndDate 02/12/2018 -IsSuccess $true -``` - -This example finds all the administrator audit log entries that match the following criteria: - -- Cmdlets: Set-Mailbox - -- Parameters: UseDatabaseQuotaDefaults, ProhibitSendReceiveQuota, ProhibitSendQuota - -- StartDate: 01/24/2018 - -- EndDate: 02/12/2018 - -The command completed successfully - -### Example 3 -```powershell -$LogEntries = Search-AdminAuditLog -Cmdlets Write-AdminAuditLog; $LogEntries | ForEach { $_.CmdletParameters } -``` - -This example displays all the comments written to the administrator audit log by the Write-AdminAuditLog cmdlet. - -First, store the audit log entries in a temporary variable. Then, iterate through all the audit log entries returned and display the Parameters property. - -### Example 4 -```powershell -Search-AdminAuditLog -ExternalAccess $true -StartDate 09/17/2018 -EndDate 10/02/2018 -``` - -This example returns entries in the administrator audit log of an Exchange Online organization for cmdlets run by Microsoft datacenter administrators between September 17, 2018 and October 2, 2018. - -## PARAMETERS - -### -Cmdlets -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**. - -```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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -In the results of this cmdlet, the date/time when the change was made (the cmdlet was run) is returned in the property named **RunDate**. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalAccess -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. - -- $false: Only return audit log entries where the change was made by an internal user. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsSuccess -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). - -- $false: Only return audit log entries where the change was not successful (in other words, the cmdlet did not run successfully and resulted in an error). - -In the results of this cmdlet, this property is named **Succeeded**. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ObjectIds -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 - -- Canonical distinguished name (for example, contoso.com/Users/Akia Al-Zuhairi) - -- Public folder identity (for example, \\Engineering\\Customer Discussion) - -You'll likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**. - -To enter multiple values, use the following syntax: Value1,Value2,...ValueN. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "Value 1","Value 2",..."Value N". - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Parameters -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** - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. The default value is 1000. - -The maximum results to return is 250,000. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -In the results of this cmdlet, the date/time when the change was made (the cmdlet was run) is returned in the property named **RunDate**. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartIndex -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserIds -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)). - -To enter multiple values, use the following syntax: User1,User2,...UserN. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "User 1","User 2",..."User N". - -In the results of this cmdlet, this property is named **Caller** - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-audit/Search-UnifiedAuditLog.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-UnifiedAuditLog.md deleted file mode 100644 index 86aac8befb..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-UnifiedAuditLog.md +++ /dev/null @@ -1,503 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/search-unifiedauditlog -applicable: Exchange Online -title: Search-UnifiedAuditLog -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Search-UnifiedAuditLog - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Search-UnifiedAuditLog cmdlet to search the unified audit log. This log contains events from Exchange Online, SharePoint Online, OneDrive for Business, Azure Active Directory, Microsoft Teams, Power BI, Sway, and other Office 365 services. You can search for all events in a specified date range, or you can filter the results based on specific criteria, such as the user who performed the action, the action, or the target object. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Search-UnifiedAuditLog -EndDate <ExDateTime> -StartDate <ExDateTime> - [-Formatted] - [-FreeText <String>] - [-IPAddresses <String[]>] - [-ObjectIds <String[]>] - [-Operations <String[]>] - [-RecordType <AuditRecordType>] - [-ResultSize <Int32>] - [-SessionCommand <UnifiedAuditSessionCommand>] - [-SessionId <String>] - [-SiteIds <String[]>] - [-UserIds <String[]>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Search-UnifiedAuditLog cmdlet presents pages of data based on repeated iterations of the same command. Use SessionId and SessionCommand to repeatedly run the cmdlet until you get zero returns, or hit the maximum number of results based on the session command. To gauge progress, look at the ResultIndex (hits in the current iteration) and ResultCount (hits for all iterations) properties of the data returned by the cmdlet. - -The Search-UnifiedAuditLog cmdlet is available in Exchange Online PowerShell. You can also view events from the unified auditing log by using the Office 365 Security & Compliance Center. For more information, see [Audited activities](https://go.microsoft.com/fwlink/p/?LinkId=708432). - -If you want to programmatically download data from the Office 365 audit log, we recommend that you use the Office 365 Management Activity API instead of using the Search-UnifiedAuditLog cmdlet in a PowerShell script. The Office 365 Management Activity API is a REST web service that you can use to develop operations, security, and compliance monitoring solutions for your organization. For more information, see [Office 365 Management Activity API reference](https://docs.microsoft.com/office/office-365-management-api/office-365-management-activity-api-reference). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Search-UnifiedAuditLog -StartDate 5/1/2018 -EndDate 5/2/2018 -``` - -This example searches the unified audit log for all events from May 1, 201812:00AM to May 2, 2018 12:00AM. - -Note: If you don't include a timestamp in the value for the StartDate or EndDate parameters, the default timestamp 12:00 AM (midnight) is used. - -### Example 2 -```powershell -Search-UnifiedAuditLog -StartDate "6/1/2018 8:00 AM" -EndDate "6/1/2018 6:00 PM" -RecordType ExchangeAdmin -``` - -This example searches the unified audit log for all Exchange admin events from 8:00 AM to 6:00 PM on June 1, 2018. - ->[!NOTE] -> If you use the same date for the StartDate and EndDate parameters, you have to include a timestamp; otherwise, no results will be returned because the date and time for the start and end dates will be the same. - -### Example 3 -```powershell -Search-UnifiedAuditLog -StartDate 5/1/2018 -EndDate 5/8/2018 -SessionId "UnifiedAuditLogSearch 05/08/17" -SessionCommand ReturnNextPreviewPage -``` - -This example searches the unified audit log for all events from May 1, 2018 to May 8, 2018. If you don't include a time stamp in the StartDate or EndDate parameters, The data is returned in pages as the command is rerun sequentially while using the same SessionId value. - -> [!NOTE] -> If you use the SessionCommand value ReturnLargeSet, and then you use the value ReturnNextPreviewPage for the same session ID, the results are limited to 10,000 records (not 50,000). - -### Example 4 -```powershell -Search-UnifiedAuditLog -StartDate 5/1/2018 -EndDate 5/8/2018 -RecordType SharePointFileOperation -Operations FileAccessed -SessionId "WordDocs_SharepointViews"-SessionCommand ReturnNextPreviewPage -``` - -This example searches the unified audit log for any files accessed in SharePoint Online from May 1, 2018 to May 8, 2018. The data is returned in pages as the command is rerun sequentially while using the same SessionId value. - -### Example 5 -```powershell -Search-UnifiedAuditLog -StartDate 5/1/2018 -EndDate 5/8/2018 -ObjectIDs "https://alpinehouse.sharepoint.com/sites/contoso/Departments/SM/International/Shared%20Documents/Sales%20Invoice%20-%20International.docx" -``` - -This example searches the unified audit log from May 1, 2018 to May 8, 2018 for all events relating to a specific Word document identified by its ObjectIDs value. - -## PARAMETERS - -### -EndDate -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: - -- Specify the date/time value in UTC: For example, `"2018-05-06 14:30:00z"`. - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2018 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -If you don't include a timestamp in the value for this parameter, the default timestamp is 12:00 AM (midnight) on the specified date. - -```yaml -Type: ExDateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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: - -- Specify the date/time value in UTC: For example, `"2018-05-06 14:30:00z"`. - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2018 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -If you don't include a timestamp in the value for this parameter, the default timestamp is 12:00 AM (midnight) on the specified date. - -```yaml -Type: ExDateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Formatted -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FreeText -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPAddresses -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ObjectIds -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. For Azure Active Directory operations, the object ID is the account name or GUID value of the account. - -The ObjectId value appears in the AuditData (also known as Details) property of the event. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operations -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://go.microsoft.com/fwlink/p/?LinkId=708432). - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordType -The RecordType parameter filters the log entries by record type. Valid values are: - -- AeD - -- AirInvestigation - -- ApplicationAudit - -- AzureActiveDirectory - -- AzureActiveDirectoryAccountLogon - -- AzureActiveDirectoryStsLogon - -- Campaign - -- ComplianceDLPExchange - -- ComplianceDLPSharePoint - -- ComplianceDLPSharePointClassification - -- ComplianceSupervisionExchange - -- CustomerKeyServiceEncryption - -- CRM - -- DataCenterSecurityCmdlet - -- DataGovernance - -- DataInsightsRestApiAudit - -- Discovery - -- DLPEndpoint - -- ExchangeAdmin - -- ExchangeAggregatedOperation - -- ExchangeItem - -- ExchangeItemAggregated - -- ExchangeItemGroup - -- HRSignal - -- HygieneEvent - -- InformationWorkerProtection - -- InformationBarrierPolicyApplication - -- Kaizala - -- LabelContentExplorer - -- MailSubmission - -- MicrosoftFlow - -- MicrosoftForms - -- MicrosoftTeamsAnalytics - -- MicrosoftTeams - -- MicrosoftTeamsAdmin - -- MicrosoftTeamsDevice - -- MicrosoftTeamsAddOns - -- MicrosoftStream - -- MicrosoftTeamsSettingsOperation - -- MipAutoLabelSharePointItem - -- MipAutoLabelSharePointPolicyLocation - -- MIPLabel - -- OfficeNative - -- OneDrive - -- PowerBIAudit - -- Project - -- PowerAppsApp - -- PowerAppsPlan - -- Quarantine - -- SecurityComplianceAlerts - -- SecurityComplianceCenterEOPCmdlet - -- SecurityComplianceInsights - -- SharePoint - -- SharePointCommentOperation - -- SharePointContentTypeOperation - -- SharePointFileOperation - -- SharePointFieldOperation - -- SharePointListOperation - -- SharePointListItemOperation - -- SharePointSharingOperation - -- SkypeForBusinessCmdlets - -- SkypeForBusinessPSTNUsage - -- SkypeForBusinessUsersBlocked - -- Sway - -- SyntheticProbe - -- ThreatFinder - -- ThreatIntelligence - -- ThreatIntelligenceAtpContent - -- ThreatIntelligenceUrl - -- TeamsHealthcare - -- WorkplaceAnalytics - -- Yammer - -```yaml -Type: AuditRecordType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. The default value is 100, maximum is 5,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionCommand -The SessionCommand parameter specifies how much information is returned and how it's organized. Valid values are: - -- ReturnNextPreviewPage: This value causes the cmdlet to return data sorted on date. The maximum number of records returned through use of either paging or the ResultSize parameter is 5,000 records. - -- ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. - -**Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. - -```yaml -Type: UnifiedAuditSessionCommand -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionId -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. - -For a given session ID, if you use the SessionCommand value ReturnLargeSet, and then you use the SessionCommand value ReturnNextPreviewPage, the results are limited to 10,000 records. To have all 50,000 records available, always use the ReturnLargeSet value each time your run the cmdlet for the same session ID. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteIds -The SiteIds parameter filters the log entries by site ID. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserIds -The UserIds parameter filters the log entries by the ID of the user who performed the action. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### -The OutVariable parameter accepts objects of type ArrayList. Here's an example of how to use it: - -$start = (Get-Date).AddDays(-1); $end = (Get-Date).AddDays(-0.5); $auditData = New-Object System.Collections.ArrayList; Search-UnifiedAuditLog -StartDate $start -EndDate $end -OutVariable +auditData | Out-Null - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AuditConfig.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AuditConfig.md deleted file mode 100644 index e008722ad7..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AuditConfig.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/set-auditconfig -applicable: Office 365 Security & Compliance Center -title: Set-AuditConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-AuditConfig - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-AuditConfig cmdlet to configure the auditing configuration in the Security & Compliance Center. The auditing configuration specifies where auditing is allowed in Microsoft Office 365. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AuditConfig [[-Identity] <PolicyIdParameter>] -Workload <MultiValuedProperty> [-DomainController <Fqdn>] - [-Organization <OrganizationIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-AuditConfig -Workload Exchange,SharePoint -``` - -This example sets the auditing configuration for Exchange and SharePoint. - -## PARAMETERS - -### -Workload -The Workload parameter specifies where auditing is allowed. Valid values are: - -- Exchange - -- InTune - -- OneDriveForBusiness - -- SharePoint - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Organization -This parameter is reserved for internal Microsoft use. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AuditConfigurationRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AuditConfigurationRule.md deleted file mode 100644 index c03bfed8f0..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AuditConfigurationRule.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/set-auditconfigurationrule -applicable: Office 365 Security & Compliance Center -title: Set-AuditConfigurationRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-AuditConfigurationRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-AuditConfigurationRule cmdlet to modify audit configuration rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AuditConfigurationRule [-Identity] <ComplianceRuleIdParameter> -AuditOperation <MultiValuedProperty> - [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-AuditConfigurationRule 989a3a6c-dc40-4fa4-8307-beb3ece992e9 -AuditOperation @{Add="CheckOut"} -``` - -This example modifies an existing SharePoint auditing rule. The check-out operation is added to the rule without affecting the existing operations that are already being audited. - -## PARAMETERS - -### -AuditOperation -The AuditOperation parameter specifies the operations that are audited by the rule. Valid values are: - -- Administrate - -- CheckIn - -- CheckOut - -- Count - -- CreateUpdate - -- Delete - -- Forward - -- MoveCopy - -- PermissionChange - -- ProfileChange - -- SchemaChange - -- Search - -- SendAsOthers - -- View - -- Workflow - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the audit configuration rule that you want to modify. The name of the rule is a GUID value. For example, 989a3a6c-dc40-4fa4-8307-beb3ece992e9. You can find the name value by running the following command: Get-AuditConfigurationRule | Format-List Name,Workload,AuditOperation,Policy. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-UnifiedAuditLogRetentionPolicy.md deleted file mode 100644 index 640cd430e2..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-UnifiedAuditLogRetentionPolicy.md +++ /dev/null @@ -1,392 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-audit/set-unifiedauditlogretentionpolicy -applicable: Office 365 Security & Compliance Center -title: Set-UnifiedAuditLogRetentionPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-UnifiedAuditLogRetentionPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-UnifiedAuditLogRetentionPolicy cmdlet to modify audit log retention policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-UnifiedAuditLogRetentionPolicy [-Identity] <PolicyIdParameter> -Priority <Int32> -RetentionDuration <UnifiedAuditLogRetentionDuration> - [-Confirm] - [-Description <String>] - [-Operations <MultiValuedProperty>] - [-RecordTypes <MultiValuedProperty>] - [-UserIds <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Audit log retention policies are used to specify a retention duration for audit logs for that are generated by admin and user activity. An audit log retention policy can specify the retention duration based on the type of audited activities, the Office 365 service that activities are performed in, or the users who performed the activities. For more information, see [Manage audit log retention policies](https://docs.microsoft.com/microsoft-365/compliance/audit-log-retention-policies). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-UnifiedAuditLogRetentionPolicy -Identity "eDiscovery audit retention" -RecordTypes Discovery,AeD -UserIds admin@contoso.onmicrosoft.com -RetentionDuration SixMonths -Priority 100 -``` - -This example adds the AeD (for Advanced eDiscovery events) record type to the policy. It also configures that the policy is applied only to the audit logs for activities performed only by the user admin@contoso.onmicrosoft.com. - -### Example 2 -```powershell -Set-UnifiedAuditLogRetentionPolicy -Name "SearchQueryPerformed by app@sharepoint" -Operations SearchQueryPerformed,FileAccessed -UserIds $null -RetentionDuration SixMonths -Priority 10000 -``` - -This example modifies an audit log retention policy and changes to retention duration to six months, adds an additional activity to the Operations parameter, and removes all values from the UserId property so that the policy will apply to all users. - -## PARAMETERS - -### -Identity -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 - -- Distingished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Priority -The Priority parameter specifies a priority value for the policy that determines the order of policy processing. A higher integer value indicates a higher priority, the value 10000 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 8 existing policies: - -- Valid priority values for the existing 8 policies are from 7 through 0. - -- Valid priority values for a new policy (the 9th policy) are from 8 through 0. - -You must use a unique priority value when modifying audit log retention policies. This parameter is required when modifying an audit log retention policy. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter specifies how long audit log records are kept. Valid values are: - -- ThreeMonths - -- SixMonths - -- NineMonths - -- TwelveMonths - -This parameter is required when modifying an audit log retention policy. - -```yaml -Type: UnifiedAuditLogRetentionDuration -Parameter Sets: (All) -Aliases: -Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operations -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://go.microsoft.com/fwlink/p/?LinkId=708432). - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordTypes -The RecordTypes parameter specifies the audit logs of a specific record type that are retained by the policy. The values you specify will overwrite any existing entries. Valid values are: - -- AeD - -- AirInvestigation - -- ApplicationAudit - -- AzureActiveDirectory - -- AzureActiveDirectoryAccountLogon - -- AzureActiveDirectoryStsLogon - -- CRM - -- Campaign - -- ComplianceDLPExchange - -- ComplianceDLPSharePoint - -- ComplianceDLPSharePointClassification - -- ComplianceSupervisionExchange - -- CustomerKeyServiceEncryption - -- DLPEndpoint - -- DataCenterSecurityCmdlet - -- DataGovernance - -- DataInsightsRestApiAudit - -- Discovery - -- ExchangeAdmin - -- ExchangeAggregatedOperation - -- ExchangeItem - -- ExchangeItemAggregated - -- ExchangeItemGroup - -- HRSignal - -- HygieneEvent - -- InformationBarrierPolicyApplication - -- InformationWorkerProtection - -- Kaizala - -- LabelContentExplorer - -- MIPLabel - -- MailSubmission - -- MicrosoftFlow - -- MicrosoftForms - -- MicrosoftStream - -- MicrosoftTeams - -- MicrosoftTeamsAdmin - -- MicrosoftTeamsAnalytics - -- MicrosoftTeamsDevice - -- MicrosoftTeamsShifts - -- MipAutoLabelExchangeItem - -- MipAutoLabelSharePointItem - -- MipAutoLabelSharePointPolicyLocation - -- OfficeNative - -- OneDrive - -- PowerAppsApp - -- PowerAppsPlan - -- PowerBIAudit - -- Project - -- Quarantine - -- SecurityComplianceAlerts - -- SecurityComplianceCenterEOPCmdlet - -- SecurityComplianceInsights - -- SharePoint - -- SharePointCommentOperation - -- SharePointContentTypeOperation - -- SharePointFieldOperation - -- SharePointFileOperation - -- SharePointListItemOperation - -- SharePointListOperation - -- SharePointSharingOperation - -- SkypeForBusinessCmdlets - -- SkypeForBusinessPSTNUsage - -- SkypeForBusinessUsersBlocked - -- Sway - -- SyntheticProbe - -- TeamsHealthcare - -- ThreatFinder - -- ThreatIntelligence - -- ThreatIntelligenceAtpContent - -- ThreatIntelligenceUrl - -- WorkplaceAnalytics - -- Yammer - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserIds -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. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSearch.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSearch.md deleted file mode 100644 index 4e76eda0fa..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSearch.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/get-compliancesearch -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: Get-ComplianceSearch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# Get-ComplianceSearch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-ComplianceSearch cmdlet to view estimate compliance searches in Exchange Server 2016 and in the Office 365 Security & Compliance Center. After you use the New-ComplianceSearchAction cmdlet to define a preview action for the compliance search, use the Get-ComplianceSearchAction cmdlet to view the results of the compliance search. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceSearch [[-Identity] <ComplianceSearchIdParameter>] [-Case <String>] [-DomainController <Fqdn>] - [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group and not to the Organization Management role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceSearch -``` - -This example shows a summary list of all compliance searches. - -### Example 2 -```powershell -Get-ComplianceSearch -Identity "Case 1234" | Format-List -``` - -This examples show details of the compliance search named Case 1234. - -## PARAMETERS - -### -Case -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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: - -- Name - -- JobRunId (GUID) - -You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status - -To improve the performance of this cmdlet, some compliance search properties aren't returned if you don't specify the identity of the compliance search. These properties are: - -- Items - -- Size - -- SuccessResults - -- NumBindings - -- ExchangeLocation - -- SharePointLocation - -- OneDriveLocation - -To view these properties, you need to use the Identity parameter in the command. - -```yaml -Type: ComplianceSearchIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSearchAction.md deleted file mode 100644 index e19719b103..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSearchAction.md +++ /dev/null @@ -1,254 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/get-compliancesearchaction -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: Get-ComplianceSearchAction -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# Get-ComplianceSearchAction - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-ComplianceSearchAction cmdlet to view information about compliance search actions in Exchange Server 2016 and in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity -``` -Get-ComplianceSearchAction [[-Identity] <ComplianceSearchActionIdParameter>] - [-Case <String>] - [-Details] - [-DomainController <Fqdn>] - [-IncludeCredential] - [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -### Preview -``` -Get-ComplianceSearchAction [-Preview] - [-Case <String>] - [-Details] - [-DomainController <Fqdn>] - [-IncludeCredential] - [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -### Purge -``` -Get-ComplianceSearchAction [-Purge] - [-Case <String>] - [-Details] - [-DomainController <Fqdn>] - [-IncludeCredential] - [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -### Export -``` -Get-ComplianceSearchAction [-Export] - [-Case <String>] - [-Details] - [-DomainController <Fqdn>] - [-IncludeCredential] - [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -After you create and run a compliance search using the New-ComplianceSearch cmdlet, and start the search using the Start-ComplianceSearch cmdlet, you assign a search action using the New-ComplianceSearchAction cmdlet. You use the Get-ComplianceSearchAction cmdlet to track the progress of the compliance search action. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group, and not to the Organization Management role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceSearchAction -``` - -This example shows a summary list of all compliance search actions. - -### Example 2 -```powershell -Get-ComplianceSearchAction -Identity "Case 1234_Preview" | Format-List -``` - -This example shows details about the compliance search action named "Case 1234\_Preview" - -## PARAMETERS - -### -Case -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Details -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Export -The Export switch filters the results by Export compliance search actions. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: Export -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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. - -- JobRunId (GUID) - -```yaml -Type: ComplianceSearchActionIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IncludeCredential -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Preview -The Preview switch filters the results by Preview compliance search actions. - -```yaml -Type: SwitchParameter -Parameter Sets: Preview -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Purge -The Purge switch filters the results by Purge compliance search actions. - -```yaml -Type: SwitchParameter -Parameter Sets: Purge -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSecurityFilter.md deleted file mode 100644 index 51c04be2e1..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Get-ComplianceSecurityFilter.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/get-compliancesecurityfilter -applicable: Office 365 Security & Compliance Center -title: Get-ComplianceSecurityFilter -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-ComplianceSecurityFilter - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ComplianceSecurityFilter cmdlet to view compliance security filters in the Security & Compliance Center. These filters allow specified users to search only a subset of mailboxes and SharePoint Online or OneDrive for Business sites in your Office 365 organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceSecurityFilter [-Action <ComplianceSecurityFilterActionType>] [-Confirm] - [-FilterName <String>] [-User <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Compliance security filters work with compliance searches in the Security & Compliance Center (\*-ComplianceSearch cmdlets), not In-Place eDiscovery searches in Exchange Online (\*-MailboxSearch cmdlets). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceSecurityFilter | Format-Table -Auto FilterName,Action -``` - -This example returns a summary list of all compliance security filters. - -### Example 2 -```powershell -Get-ComplianceSecurityFilter -FilterName "HR Filter" -``` - -This example returns detailed information about the compliance security filter named HR Filter. - -## PARAMETERS - -### -Action -The Action parameter filters the results by the type of search action that a filter is applied to. Valid values are: - -- All - -- Export - -- Preview - -- Purge - -- Search - -```yaml -Type: ComplianceSecurityFilterActionType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterName -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -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. - -- The value All. - -- The name of a role group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearch.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearch.md deleted file mode 100644 index e525b8e770..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearch.md +++ /dev/null @@ -1,519 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/new-compliancesearch -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: New-ComplianceSearch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# New-ComplianceSearch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-ComplianceSearch cmdlet to create compliance searches in Exchange Server 2016 and in the Office 365 Security & Compliance Center. You use this cmdlet to define the search criteria. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ComplianceSearch [-Name] <String> - [-AllowNotFoundExchangeLocationsEnabled <Boolean>] - [-Case <String>] - [-Confirm] - [-ContentMatchQuery <String>] - [-Description <String>] - [-ExchangeLocation <String[]>] - [-ExchangeLocationExclusion <String[]>] - [-Force] - [-HoldNames <String[]>] - [-IncludeUserAppContent <Boolean>] - [-Language <CultureInfo>] - [-LogLevel <ComplianceJobLogLevel>] - [-OneDriveLocation <String[]>] - [-OneDriveLocationExclusion <String[]>] - [-PublicFolderLocation <String[]>] - [-PublicFolderLocationExclusion <String[]>] - [-RefinerNames <String[]>] - [-SearchNames <String[]>] - [-SharePointLocation <String[]>] - [-SharePointLocationExclusion <String[]>] - [-StatusMailRecipients <String[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -A compliance search requires at least one location. For example, mailboxes using the ExchangeLocation parameter, or SharePoint sites using the SharePointLocation parameter. - -After you create a compliance search using the New-ComplianceSearch cmdlet, you run the search using the Start-ComplianceSearch cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group, and not to the Organization Management role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ComplianceSearch -Name "Hold Project X" -ExchangeLocation "Finance Department" -``` - -This example creates a new compliance search named Hold-Project X that searches all members of the distribution group named Finance Department. Because the search doesn't use the ContentMatchQuery parameter, all items in the mailboxes are searched. - -### Example 2 -```powershell -New-ComplianceSearch -Name "Hold-Tailspin Toys" -ExchangeLocation "Research Department" -ContentMatchQuery "'Patent' AND 'Project Tailspin Toys'" -``` - -This example creates a new compliance search named Hold-Tailspin Toys that searches all member of the distribution group named Research Department. Because the search uses the ContentMatchQuery parameter, only messages that match the query are searched. - -### Example 3 -```powershell -New-ComplianceSearch -Name "AnnBeebe-InactiveMailbox" -ExchangeLocation .annb@contoso.onmicrosoft.com -AllowNotFoundExchangeLocationsEnabled $true -``` - -This example creates a new compliance search named AnnBeebe-InactiveMailbox that searches an inactive mailbox and returns all items in the mailbox. To search inactive mailboxes, you need to use the primary SMTP address of the inactive mailbox, prepended with a period ("."). You also need to include the AllowNotFoundExchangeLocationsEnabled parameter so the search doesn't try to validate the existence of the inactive mailbox. - -## PARAMETERS - -### -Name -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowNotFoundExchangeLocationsEnabled -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. - -- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value. - -The mailbox types that are affected by the value of this parameter include: - -- Inactive mailboxes - -- Users without an Exchange Online license who use Office applications - -- Office 365 guest users - -- On-premises users whose identity is synchronized with your Office 365 organization - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Case -The Case parameter specifies the name of an eDiscovery case that the new compliance search will be associated with. If the value contains spaces, enclose the value in quotation marks. - -If the Name parameter contains spaces, the value of the ExchangeLocation parameter is cleared when you use the Case parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocation -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 Office 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter. - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -- The value All for all mailboxes. You can only use this value by itself. - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ExchangeLocationExclusion -This parameter specifies the mailboxes to exclude when you use the value All for the ExchangeLocation parameter. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HoldNames -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. - -Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeUserAppContent -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 Office 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Office 365 guest users, and on-premises users whose identity is synchronized with your Office 365 organization. Valid values are: - -- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search. - -- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogLevel -This parameter is reserved for internal Microsoft use. - -```yaml -Type: ComplianceJobLogLevel -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocationExclusion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderLocation -The PublicFolderLocation parameter specifies that you want to include all public folders in the search. You use the value All for this parameter. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderLocationExclusion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RefinerNames -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchNames -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocation -The SharePointLocation parameter specifies the SharePoint Online sites to include. You identify the site by its URL value, or you can use the value All to include all sites. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocationExclusion -This parameter specifies the SharePoint Online sites to exclude 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StatusMailRecipients -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearchAction.md deleted file mode 100644 index a2867a55e5..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearchAction.md +++ /dev/null @@ -1,757 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/new-compliancesearchaction -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: New-ComplianceSearchAction -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# New-ComplianceSearchAction - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the New-ComplianceSearchAction cmdlet to create actions for content searches in Exchange Server and in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Export -``` -New-ComplianceSearchAction [-SearchName] <String[]> [-Export] - [-ActionName <String>] - [-ArchiveFormat <ComplianceExportArchiveFormat>] - [-Confirm] - [-FileTypeExclusionsForUnindexedItems <String[]>] - [-EnableDedupe <Boolean>] - [-ExchangeArchiveFormat <ComplianceExportArchiveFormat>] - [-Force] - [-Format <ComplianceDataTransferFormat>] - [-IncludeCredential] - [-IncludeSharePointDocumentVersions <Boolean>] - [-JobOptions <Int32>] - [-NotifyEmail <String>] - [-NotifyEmailCC <String>] - [-ReferenceActionName <String>] - [-Region <String>] - [-Report] - [-RetentionReport] - [-RetryOnError] - [-Scenario <ComplianceSearchActionScenario>] - [-Scope <ComplianceExportScope>] - [-SearchNames <String[]>] - [-SharePointArchiveFormat <ComplianceExportArchiveFormat>] - [-Version <String>] - [-WhatIf] [<CommonParameters>] -``` - -### Preview -``` -New-ComplianceSearchAction [-SearchName] <String[]> [-Preview] - [-ActionName <String>] - [-Confirm] - [-Force] - [-Format <ComplianceDataTransferFormat>] - [-IncludeCredential] [-JobOptions <Int32>] - [-ReferenceActionName <String>] - [-Region <String>] - [-RetryOnError] - [-Scenario <ComplianceSearchActionScenario>] - [-SearchNames <String[]>] - [-Version <String>] - [-WhatIf] [<CommonParameters>] -``` - -### Purge -``` -New-ComplianceSearchAction [-SearchName] <String[]> [-Purge] [-PurgeType <ComplianceDestroyType>] - [-ActionName <String>] - [-Confirm] - [-Force] - [-Format <ComplianceDataTransferFormat>] - [-IncludeCredential] - [-JobOptions <Int32>] - [-Region <String>] - [-ReferenceActionName <String>] - [-RetryOnError] - [-Scenario <ComplianceSearchActionScenario>] - [-SearchNames <String[]>] - [-Version <String>] - [-WhatIf]] [<CommonParameters>] -``` - -## DESCRIPTION -After you create a content search using the New-ComplianceSearch cmdlet and run it using the Start-ComplianceSearch cmdlet, you assign a search action to the search using the New-ComplianceSearchAction cmdlet. - -In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group, and not to the Organization Management role group. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -In Office 365, the account that you use to run this cmdlet must have a valid Office 365 license assigned. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ComplianceSearchAction -SearchName "Project X" -Preview -``` - -This example creates a preview search action for the content search named Project X. - -### Example 2 -```powershell -New-ComplianceSearchAction -SearchName "Project X" -Export -``` - -This example creates an export search action for the content search named Project X. - -### Example 3 -```powershell -New-ComplianceSearchAction -SearchName "Remove Phishing Message" -Purge -PurgeType SoftDelete -``` - -This example deletes the search results returned by a content search named Remove Phishing Message. Note that unindexed items aren't deleted when you use the Purge parameter. - -### Example 4 - -``` -New-ComplianceSearchAction -SearchName "Case 321 All Sites" -Export -SharePointArchiveFormat SingleZip -``` - -This example exports the results returned by the content search named "Case 321 All Sites". The search results are compressed and exported to a single ZIP file. If the search included any Exchange locations, the search results are exported as one PST file per mailbox (the default value of the ExchangeArchiveFormat parameter). - -## PARAMETERS - -### -SearchName -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. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActionName -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ArchiveFormat -This parameter is available only in the cloud-based service. - -This parameter requires the Export role in the Security & Compliance Center. By default, the Export role is assigned only to the eDiscovery Manager role group. - -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. - -```yaml -Type: ComplianceExportArchiveFormat -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableDedupe -This parameter is available only in the cloud-based service. - -The EnableDedupe parameter eliminates duplication of messages when you export content search results. Valid values are: - -- $true: Export a single copy of a message if the same message exists in multiple folders or mailboxes. - -- $false: Export all copies of a message if the same message exists in multiple folders or mailboxes. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeArchiveFormat -This parameter is available only in the cloud-based service. - -This parameter requires the Export role in the Security & Compliance Center. By default, the Export role is assigned only to the eDiscovery Manager role group. - -The ExchangeArchiveFormat parameter specifies how to export Exchange search results. Valid values are: - -- PerUserPst: One PST file for each mailbox. This is the default value. - -- SinglePst: One PST file that contains all exported messages. - -- SingleFolderPst: One PST file with a single root folder for the entire export. - -- IndividualMessage: Export each message as an .msg message file. - -- PerUserZip: One ZIP file for each mailbox. Each ZIP file contains the exported .msg message files from the mailbox. This value corresponds to the "export files in a compressed folder" checkbox in the Security & Compliance Center. - -- SingleZip: One ZIP file for all mailboxes. The ZIP file contains all exported .msg message files from all mailboxes. This output setting is only available in PowerShell. - -To specify the format for SharePoint and OneDrive search results, use the SharePointArchiveFormat parameter. - -```yaml -Type: ComplianceExportArchiveFormat -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Export -This parameter is available only in the cloud-based service. - -This parameter requires the Export role in the Security & Compliance Center. By default, the Export role is assigned only to the eDiscovery Manager role group. - -The Export switch specifies the action for the content search is to export the full set of results that match the search criteria. You don't need to specify a value with this switch. - -To only return the information about each detected item in a report, use the Report switch. - -```yaml -Type: SwitchParameter -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileTypeExclusionsForUnindexedItems -The FileTypeExclusionsForUnindexedItems specifies the file types to exclude because they can't be indexed. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: Export -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Format -In the Security & Compliance Center, this parameter requires the Export role. By default, the Export 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: - -- FxStream: Export to PST files. This is the only option that's available when you export search results from the Security & Compliance Center. - -- Mime: Export to .eml message files. This the default value when you use cmdlets to export the search results. - -- Msg: Export to .msg message files. - -```yaml -Type: ComplianceDataTransferFormat -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeCredential -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeSharePointDocumentVersions -This parameter is available only in the cloud-based service. - -The IncludeSharePointDocumentVersions parameter specifies whether to export previous versions of the document when you use the Export switch. Valid values are: - -- $true: Export all versions of the document. - -- $false: Export only the current published version of the topic. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobOptions -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyEmail -In the Security & Compliance Center, this parameter requires the Export role. By default, the Export role is assigned only to the eDiscovery Manager role group. - -The NotifyEmail parameter specifies the email address target for the search results when you use the Export switch. - -The recipient you specify is in the To: field of the message. - -```yaml -Type: String -Parameter Sets: Export -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyEmailCC -In the Security & Compliance Center, this parameter requires the Export role. By default, the Export role is assigned only to the eDiscovery Manager role group. - -The NotifyEmailCC parameter specifies the email address target for the search results when you use the Export switch. - -The recipient you specify is in the Cc: field of the message. - -```yaml -Type: String -Parameter Sets: Export -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Preview -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. - -In the Security & Compliance Center, this parameter requires the Preview role. By default, the Preview role is assigned only to the eDiscovery Manager role group. - -```yaml -Type: SwitchParameter -Parameter Sets: Preview -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Purge -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. - -Notes: - -- A maximum of 10 items per mailbox can be removed at one time. Because the capability to search for and remove messages is intended to be an incident-response tool, this limit helps ensure that messages are quickly removed from mailboxes. This action isn't intended to clean up user mailboxes. - -- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you'll have to create separate content searches. For more information, see [Search for and delete email messages in your Office 365 organization](https://docs.microsoft.com/microsoft-365/compliance/search-for-and-delete-messages-in-your-organization). - -- Unindexed items aren't removed from mailboxes when you use this switch. - -- The value of the PurgeType parameter controls how the items are removed. - -```yaml -Type: SwitchParameter -Parameter Sets: Purge -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PurgeType -The PurgeType parameter specifies how to remove items when the action is Purge. Valid values are: - -- SoftDelete: Purged items are recoverable by users until the deleted item retention period expires. - -- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and will be permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items will be permanently removed after the deleted item retention period expires. - -```yaml -Type: ComplianceDestroyType -Parameter Sets: Purge -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReferenceActionName -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Region -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Report -This parameter is available only in the cloud-based service. - -The Report switch specifies the action for the content search is to export a report about the results (information about each item instead of the full set of results) that match the search criteria. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionReport -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. - -```yaml -Type: SwitchParameter -Parameter Sets: Export -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetryOnError -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scenario -In the Security & Compliance Center, this parameter requires the Preview role. By default, the Preview role is assigned only to the eDiscovery Manager role group. - -The Scenario parameter specifies the scenario type when you use the Export switch. Valid values are: - -- AnalyzeWithZoom: Prepare the search results for processing in Office 365 Advanced eDiscovery. - -- General: Exports the search results to the local computer. Emails are exported to .pst files. SharePoint and OneDrive for Business documents are exported in their native Office formats. - -- GenerateReportsOnly: - -- Inventory: - -- RetentionReports: - -- TriagePreview: - -```yaml -Type: ComplianceSearchActionScenario -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -The Scope parameter specifies the items to include when the action is Export. Valid values are: - -- IndexedItemsOnly - -- UnindexedItemsOnly - -- BothIndexedAndUnindexedItems - -This parameter is only meaningful for content searches where the IncludeUnindexedItemsEnabled parameter is set to $true. - -```yaml -Type: ComplianceExportScope -Parameter Sets: Export -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScopeDetails -This parameter is available only in the cloud-based service. - -This parameter requires the Export or Compliance Search roles in the Security & Compliance Center. By default, these roles are assigned only to the eDiscovery Manager role group. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: ComplianceScopeDetail[] -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchNames -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. - -You can find content search names by running the command Get-ComplianceSearch | Format-Table -Auto Name,Status. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointArchiveFormat -This parameter is available only in the cloud-based service. - -This parameter requires the Export role in the Office 365 Security & Compliance Center. By default, the Export role is assigned only to the eDiscovery Manager role group. - -The SharePointArchiveFormat parameter specifies how to export SharePoint and OneDrive search results. Valid values are: - -- IndividualMessage: Export the files uncompressed. This is the default value. - -- PerUserZip: One ZIP file for each user. Each ZIP file contains the exported files for the user. This value corresponds to the "export files in a compressed folder" checkbox in the Security & Compliance Center. - -- SingleZip: One ZIP file for all users. The ZIP file contains all exported files from all users. This output setting is only available in PowerShell. - -To specify the format for Exchange search results, use the ExchangeArchiveFormat parameter. - -```yaml -Type: ComplianceExportArchiveFormat -Parameter Sets: Export -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Version -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSecurityFilter.md deleted file mode 100644 index d3c66da3c2..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSecurityFilter.md +++ /dev/null @@ -1,301 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/new-compliancesecurityfilter -applicable: Office 365 Security & Compliance Center -title: New-ComplianceSecurityFilter -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-ComplianceSecurityFilter - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-ComplianceSecurityFilter cmdlet to create compliance security filters in the Security & Compliance Center. These filters allow specified users to search only a subset of mailboxes and SharePoint Online or OneDrive for Business sites in your Office 365 organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ComplianceSecurityFilter -Action <ComplianceSecurityFilterActionType> -FilterName <String> - -Users <MultiValuedProperty> [-Confirm] [-Description <String>] [-Filters <MultiValuedProperty>] - [-Region <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Compliance security filters work with compliance searches in the Security & Compliance Center (\*-ComplianceSearch cmdlets), not In-Place eDiscovery searches in Exchange Online (\*-MailboxSearch cmdlets). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ComplianceSecurityFilter -FilterName CountryFilter -Users annb@contoso.com -Filters "Mailbox_CountryCode -eq '124'" -Action All -``` - -This example allows the user annb to perform all compliance search actions only for mailboxes in Canada. The filter uses the ISO 3166-1 numeric country code value. - -### Example 2 -```powershell -New-ComplianceSecurityFilter -FilterName MarketingFilter -Users donh,suzanf -Filters "Mailbox_CustomAttribute1 -eq 'Marketing'" -Action Search -``` - -This example allows the users donh and suzanf to search only the mailboxes that have the value Marketing for the CustomAttribute1 mailbox property. - -### Example 3 -```powershell -New-ComplianceSecurityFilter -FilterName USDiscoveryManagers -Users "US Discovery Managers" -Filters "Mailbox_CountryCode -eq 'US'" -Action All -``` - -This example allows members of the US Discovery Managers role group to perform all compliance search actions only on mailboxes in the United States. - -### Example 4 -```powershell -$DG = Get-DistributionGroup "Ottawa Users"; New-ComplianceSecurityFilter -FilterName DGFilter -Users eDiscoveryManager -Filters "Mailbox_MemberOfGroup -eq '$($DG.DistinguishedName)'" -Action Search -``` - -This example assigns allows members of the eDiscovery Manager role group to only search the mailboxes of members of the Ottawa Users distribution group. - -This example requires you to connect to Security & Compliance Center PowerShell and Exchange Online PowerShell in the same remote PowerShell session. For instructions, see [Configure permissions filtering for Compliance Search](https://docs.microsoft.com/microsoft-365/compliance/permissions-filtering-for-content-search). - -### Example 5 -```powershell -$DG = Get-DistributionGroup "Executive Team"; New-ComplianceSecurityFilter -FilterName NoExecutivesPreview -Users all -Filters "Mailbox_MemberOfGroup -ne '$($DG.DistinguishedName)'" -Action Purge -``` - -This example prevents any user from deleting content from the mailboxes of members of the Executive Team distribution group. - -This example requires you to connect to Security & Compliance Center PowerShell and Exchange Online PowerShell in the same remote PowerShell session. For instructions, see [Configure permissions filtering for Compliance Search](https://docs.microsoft.com/microsoft-365/compliance/permissions-filtering-for-content-search). - -### Example 6 -```powershell -New-ComplianceSecurityFilter -FilterName EmailDateRestrictionFilter -Users donh@contoso.com -Filters "MailboxContent_Received -ge '01-01-2018' -and MailboxContent_Received -le '12-31-2018'" -Action All -``` - -This example restricts the user to performing all compliance search actions only on email messages sent during the calendar year 2018. - -### Example 7 -```powershell -New-ComplianceSecurityFilter -FilterName OneDriveOnly -Users "OneDrive eDiscovery Managers" -Filters "Site_Path -like 'https://contoso-my.sharepoint.com/personal*'" -Action Search -``` - -This example allows members of the OneDrive eDiscovery Managers custom role group to only search for content in OneDrive for Business locations in the organization. - -### Example 8 -```powershell -New-ComplianceSecurityFilter -FilterName DocumentDateRestrictionFilter -Users donh@contoso.com -Filters "SiteContent_LastModifiedTime -ge '01-01-2018' -and SiteContent_LastModifiedTime -le '12-31-2018'" -Action All -``` - -This example restricts the user to performing all compliance search actions on documents that were last changed sometime in the calendar year 2018. - -### Example 9 -```powershell -New-ComplianceSecurityFilter -FilterName NoEXO -Users suzanf@contoso.com -Filters "Mailbox_Alias -notlike '*'" -Action All -``` - -This example prevents the user from performing any compliance search actions on any mailbox in the organization. - -## PARAMETERS - -### -Action -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 Office 365 Advanced eDiscovery. - -- Preview: The filter is applied when previewing search results. - -- Purge: The filter is applied when purging search results. How the items are deleted is controlled by the PurgeType parameter value on the New-ComplianceSearchAction cmdlet. The default value is SoftDelete, which means the purged items are recoverable by users until the deleted items retention period expires. - -- Search: The filter is applied when running a search. - -- All: The filter is applied to all search actions. - -```yaml -Type: ComplianceSecurityFilterActionType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterName -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Users -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. - -- The value All: Assigns the filter to all users. You can only use this value by itself. - -- One or more role groups: Identify the role group by its name. You can specify multiple values separated by commas. - -You can't specify distribution groups with this parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filters -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_<MailboxPropertyName>`, where `<MailboxPropertyName>` 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://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- Mailbox content filter: Specifies the mailbox content the assigned users can search for. Valid syntax is `MailboxContent_<SearchablePropertyName>:<value>`, where `<SearchablePropertyName>` specifies a Keyword Query Language (KQL) property that can be specified in a compliance search. For example, `MailboxContent_recipients:contoso.com` allows users to only search for messages sent to recipients in the contoso.com domain. For a list of searchable message properties, see [Keyword queries for Compliance Search](https://docs.microsoft.com/microsoft-365/compliance/keyword-queries-and-search-conditions). - -- Site and site content filter: There are two SharePoint Online and OneDrive for Business site-related filters that you can create: `Site_<SearchableSiteProperty>` (specifies site-related properties. For example,`"Site_Path -eq 'https://contoso.sharepoint.com/sites/doctors'"` allows users to only search for content in the <https://contoso.sharepoint.com/sites/doctors> site collection) and `SiteContent_<SearchableSiteProperty>` (specifies content-related properties. For example, `"SiteContent_FileExtension -eq 'docx'"` allows users to only search for Word documents). For a list of searchable site properties, see [Overview of crawled and managed properties in SharePoint Server](https://go.microsoft.com/fwlink/p/?LinkId=331599). Properties marked with a Yes in the Queryable column can be used to create a site or site content filter. - -You can specify multiple filters of the same type. For example, `"Mailbox_CustomAttribute10 -eq 'FTE' -and Mailbox_MemberOfGroup -eq '$($DG.DistinguishedName)'"`. - -You have to create a search permissions filter to explicitly prevent users from searching any content location in a specific Office 365 service (such as preventing a user from searching Exchange mailboxes or SharePoint sites). In other words, creating a search permissions filter that allows a user to search all SharePoint sites in the organization doesn't prevent that user from searching mailboxes. For example, to allow a SharePoint admin to only search SharePoint sites, you have to create a create a filter that prevents them from mailboxes (see Example 9). Similarly, to allow an Exchange admin to only search mailboxes, you have to create a create a filter that prevents them from searching sites. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Region -The Region parameter specifies the satellite location for multi-geo tenants to conduct eDiscovery searches in. Valid values are: - -- APC: Asia-Pacific - -- AUS: Australia - -- CAN: Canada - -- EUR: Europe, Middle East, Africa - -- FRA: France - -- GBR: United Kingdom - -- IND: India - -- JPN: Japan - -- LAM: Latin America - -- NAM: North America - -If you don't use this parameter in a multi-geo tenant, eDiscovery searches are performed in the central location. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSearch.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSearch.md deleted file mode 100644 index cea6b76edc..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSearch.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/remove-compliancesearch -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: Remove-ComplianceSearch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# Remove-ComplianceSearch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-ComplianceSearch cmdlet to remove compliance searches from Exchange Server 2016 and from the Office 365 Security & Compliance Center. The searches must be stopped or completed. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ComplianceSearch [-Identity] <ComplianceSearchIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group and not to the Organization Management role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ComplianceSearch -Identity "Case 1234" -``` - -This example removes the compliance search named Case 1234 - -## PARAMETERS - -### -Identity -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: - -- Name - -- JobRunId (GUID) - -You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status - -```yaml -Type: ComplianceSearchIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSearchAction.md deleted file mode 100644 index d045b624bb..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSearchAction.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/remove-compliancesearchaction -applicable: Office 365 Security & Compliance Center -title: Remove-ComplianceSearchAction -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ComplianceSearchAction - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ComplianceSearch cmdlet to remove compliance search actions from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ComplianceSearchAction [-Identity] <ComplianceSearchActionIdParameter> [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ComplianceSearchAction -Identity "Case 1234_Preview" -``` - -This example the compliance search action named "Case 1234\_Preview" - -## PARAMETERS - -### -Identity -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. - -- JobRunId (GUID) - -```yaml -Type: ComplianceSearchActionIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSecurityFilter.md deleted file mode 100644 index c22d933186..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Remove-ComplianceSecurityFilter.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/remove-compliancesecurityfilter -applicable: Office 365 Security & Compliance Center -title: Remove-ComplianceSecurityFilter -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ComplianceSecurityFilter - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ComplianceSecurityFilter cmdlet to remove compliance security filters from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ComplianceSecurityFilter -FilterName <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ComplianceSecurityFilter -FilterName "HR Filter" -``` - -This example removes the compliance security filter named HR Filter. - -## PARAMETERS - -### -FilterName -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearch.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearch.md deleted file mode 100644 index 8a35480609..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearch.md +++ /dev/null @@ -1,712 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/set-compliancesearch -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: Set-ComplianceSearch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# Set-ComplianceSearch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-ComplianceSearch cmdlet to modify non-running compliance searches in Exchange Server 2016 and in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ComplianceSearch [-Identity] <ComplianceSearchIdParameter> - [-AddExchangeLocation <String[]>] - [-AddExchangeLocationExclusion <String[]>] - [-AddOneDriveLocation <String[]>] - [-AddOneDriveLocationExclusion <String[]>] - [-AddSharePointLocation <String[]>] - [-AddSharePointLocationExclusion <String[]>] - [-AllowNotFoundExchangeLocationsEnabled <Boolean>] - [-Confirm] - [-ContentMatchQuery <String>] - [-Description <String>] - [-ExchangeLocation <String[]>] - [-ExchangeLocationExclusion <String[]>] - [-Force] - [-HoldNames <String[]>] - [-IncludeUserAppContent <Boolean>] - [-Language <CultureInfo>] - [-Name <String>] - [-OneDriveLocation <String[]>] - [-OneDriveLocationExclusion <String[]>] - [-PublicFolderLocation <String[]>] - [-RefinerNames <String[]>] - [-RemoveExchangeLocation <String[]>] - [-RemoveExchangeLocationExclusion <String[]>] - [-RemoveOneDriveLocation <String[]>] - [-RemoveOneDriveLocationExclusion <String[]>] - [-RemovePublicFolderLocation <String[]>] - [-RemoveSharePointLocation <String[]>] - [-RemoveSharePointLocationExclusion <String[]>] - [-SharePointLocation <String[]>] - [-SharePointLocationExclusion <String[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group, and not to the Organization Management role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-ComplianceSearch -Identity "Project X" -ExchangeLocation All -``` - -This example changes the existing compliance search named Project X. The scope of the Exchange search is changed to all mailboxes. - -### Example 2 -```powershell -Set-ComplianceSearch -Identity "Contoso Case Search 1" -HoldNames All -ExchangeLocation $null -SharePointLocation $null -``` - -This example changes an existing compliance search that's associated with an eDiscovery case in the Office 365 Security & Compliance Center. The scope of the search is changed from searching selected mailboxes and SharePoint sites to searching all content locations that have been placed on hold in the eDiscovery case. - -### Example 3 -```powershell -Set-ComplianceSearch -Identity "China Subsidiary Search" -Language zh-CN -``` - -This example changes the language setting for an existing compliance search to Chinese. - -You might have to change the language setting if you're using non-English keywords in the search query (which is specified in the ContentMatchQuery parameter). - -## PARAMETERS - -### -Identity -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: - -- Name - -- JobRunId (GUID) - -You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status - -```yaml -Type: ComplianceSearchIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AddExchangeLocation -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 Office 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter. - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocationExclusion -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 regular user mailbox. Including other types of mailboxes (for example, inactive mailboxes or Office 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter. - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddOneDriveLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddOneDriveLocationExclusion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocation -The AddSharePointLocation parameter specifies the SharePoint Online 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. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocationExclusion -This parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowNotFoundExchangeLocationsEnabled -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. - -- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value. - -The mailbox types that are affected by the value of this parameter include: - -- Inactive mailboxes - -- Users without an Exchange Online license who use Office applications - -- Office 365 guest users - -- On-premises users whose identity is synchronized with your Office 365 organization - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocation -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 Office 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter. - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -- The value All for all mailboxes. You can only use this value by itself. - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocationExclusion -This parameter specifies the mailboxes to exclude when you use the value All for the ExchangeLocation parameter. Valid values are: - -- A regular user mailbox. Including other types of mailboxes (for example, inactive mailboxes or Office 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter. - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HoldNames -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. - -If the content locations in the compliance search include mailboxes, you also need to use the ExchangeLocation parameter with the value $null. Similarly, if the compliance search includes SharePoint sites, you also need to use the SharePointLocation parameter withthe value $null. - -Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you restart this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeUserAppContent -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 Office 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Office 365 guest users, and on-premises users whose identity is synchronized with your Office 365 organization. Valid values are: - -- $true: The cloud-based storage location for the users specified in any of the Exchange location parameters will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search. - -- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocationExclusion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderLocation -The PublicFolderLocation parameter specifies that you want to include all public folders in the search. You use the value All for this parameter. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RefinerNames -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocation -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 - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocationExclusion -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: - -- A mailbox - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, use the email address. You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveOneDriveLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveOneDriveLocationExclusion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemovePublicFolderLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocation -The RemoveSharePointLocation parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocationExclusion -This parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocation -The SharePointLocation parameter specifies the SharePoint Online sites to include. You identify the site by its URL value, or you can use the value All to include all sites. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocationExclusion -This parameter specifies the SharePoint Online sites to exclude 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearchAction.md deleted file mode 100644 index ad5018d10f..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearchAction.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/set-compliancesearchaction -applicable: Office 365 Security & Compliance Center -title: Set-ComplianceSearchAction -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-ComplianceSearchAction - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Set-ComplianceSearchAction cmdlet to change the export key on export compliance search actions in on-premises Exchange. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ComplianceSearchAction [-Identity] <ComplianceSearchActionIdParameter> [-ChangeExportKey] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group, and not to the Organization Management role group. - -## EXAMPLES - -### Example 1 -```powershell -Set-ComplianceSearchAction -Identity "Project X_Export" -ChangeExportKey -``` - -This example changes the export key on the export compliance search action named Project X\_Export. - -## PARAMETERS - -### -Identity -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). - -- JobRunId (GUID) - -```yaml -Type: ComplianceSearchActionIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ChangeExportKey -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 parameter is only meaningful on export compliance search actions. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSecurityFilter.md deleted file mode 100644 index bf2dbb524c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSecurityFilter.md +++ /dev/null @@ -1,246 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/set-compliancesecurityfilter -applicable: Office 365 Security & Compliance Center -title: Set-ComplianceSecurityFilter -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-ComplianceSecurityFilter - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-ComplianceSecurityFilter cmdlet to modify compliance security filters in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ComplianceSecurityFilter -FilterName <String> [-Action <ComplianceSecurityFilterActionType>] - [-Confirm] [-Description <String>] [-Filters <MultiValuedProperty>] [-Region <String>] - [-Users <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$filterusers = Get-ComplianceSecurityFilter -FilterName "Ottawa Users Filter"; $filterusers.users.add("pilarp@contoso.com"); Set-ComplianceSecurityFilter -FilterName OttawaUsersFilter -Users $filterusers.users -``` - -This example adds user pilarp@contoso.com to the compliance security filter named Ottawa Users Filter without affecting other users assigned to the filter. - -### Example 2 -```powershell -$filterusers = Get-ComplianceSecurityFilter -FilterName "Ottawa Users Filter"; $filterusers.users.remove("annb@contoso.com"); Set-ComplianceSecurityFilter -FilterName OttawaUsersFilter -Users $filterusers.users -``` - -This example removes user annb@contoso.com to the compliance security filter named Ottawa Users Filter without affecting other users assigned to the filter. - -## PARAMETERS - -### -FilterName -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Action -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 Office 365 Advanced eDiscovery. - -- Preview: The filter is applied when previewing search results. - -- Purge: The filter is applied when purging search results. How the items are deleted is controlled by the PurgeType parameter value on the New-ComplianceSearchAction cmdlet. The default value is SoftDelete, which means the purged items are recoverable by users until the deleted items retention period expires. - -- Search: The filter is applied when running a search. - -- All: The filter is applied to all search actions. - -```yaml -Type: ComplianceSecurityFilterActionType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filters -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_<MailboxPropertyName>`, where `<MailboxPropertyName>` 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://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- Mailbox content filter: Specifies the mailbox content the assigned users can search for. Valid syntax is `MailboxContent_<SearchablePropertyName>:<value>`, where `<SearchablePropertyName>` specifies a Keyword Query Language (KQL) property that can be specified in a compliance search. For example, `MailboxContent_recipients:contoso.com` allows users to only search for messages sent to recipients in the contoso.com domain. For a list of searchable message properties, see [Keyword queries for Compliance Search](https://docs.microsoft.com/microsoft-365/compliance/keyword-queries-and-search-conditions). - -- Site and site content filter: There are two SharePoint Online and OneDrive for Business site-related filters that you can create: `Site_<SearchableSiteProperty>` (specifies site-related properties. For example,`"Site_Path -eq 'https://contoso.sharepoint.com/sites/doctors'"` allows users to only search for content in the <https://contoso.sharepoint.com/sites/doctors> site collection) and `SiteContent_<SearchableSiteProperty>` (specifies content-related properties. For example, `"SiteContent_FileExtension -eq 'docx'"` allows users to only search for Word documents). For a list of searchable site properties, see [Overview of crawled and managed properties in SharePoint Server](https://go.microsoft.com/fwlink/p/?LinkId=331599). Properties marked with a Yes in the Queryable column can be used to create a site or site content filter. - -You can specify multiple filters of the same type. For example, `"Mailbox_CustomAttribute10 -eq 'FTE' -and Mailbox_MemberOfGroup -eq '$($DG.DistinguishedName)'"`. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Region -The Region parameter specifies the satellite location for multi-geo tenants to conduct eDiscovery searches in. Valid values are: - -- APC: Asia-Pacific - -- AUS: Australia - -- CAN: Canada - -- EUR: Europe, Middle East, Africa - -- FRA: France - -- GBR: United Kingdom - -- IND: India - -- JPN: Japan - -- LAM: Latin America - -- NAM: North America - -If you don't use this parameter in a multi-geo tenant, eDiscovery searches are performed in the central location. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Users -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. - -- The value All: Assigns the filter to all users. You can only use this value by itself. - -- One or more role groups: Identify the role group by its name. You can specify multiple values separated by commas. - -You can't specify distribution groups with this parameter. - -The values you specify will overwrite any existing entries. See the Examples section to add or remove users without affecting other existing entries. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-ComplianceSearch.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-ComplianceSearch.md deleted file mode 100644 index 986c217e14..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-ComplianceSearch.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/start-compliancesearch -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: Start-ComplianceSearch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# Start-ComplianceSearch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Start-ComplianceSearch cmdlet to start stopped, completed or not started compliance searches in Exchange Server 2016 and in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Start-ComplianceSearch [-Identity] <ComplianceSearchIdParameter> - [-Confirm] - [-Force] - [-RetryOnError] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group, and not to the Organization Management role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Start-ComplianceSearch -Identity "Case 1234" -``` - -This example starts the compliance search named Case 1234 - -## PARAMETERS - -### -Identity -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: - -- Name - -- JobRunId (GUID) - -You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status - -```yaml -Type: ComplianceSearchIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetryOnError -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Stop-ComplianceSearch.md b/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Stop-ComplianceSearch.md deleted file mode 100644 index db0d32ac09..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-content-search/Stop-ComplianceSearch.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/stop-compliancesearch -applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center -title: Stop-ComplianceSearch -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2016 || exchserver-ps-2019 || o365scc-ps" ---- - -# Stop-ComplianceSearch - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Stop-ComplianceSearch cmdlet to stop running compliance searches in Exchange Server 2016 and in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Stop-ComplianceSearch [-Identity] <ComplianceSearchIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group and not to the Organization Management role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Stop-ComplianceSearch -Identity "Case 1234" -``` - -This example stops the active compliance search named Case 1234 - -## PARAMETERS - -### -Identity -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: - -- Name - -- JobRunId (GUID) - -You can find these values by running the command Get-ComplianceSearch | Format-Table -Auto Name,JobRunId,Status - -```yaml -Type: ComplianceSearchIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2016, Exchange Server 2019, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying 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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DataClassificationConfig.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DataClassificationConfig.md deleted file mode 100644 index 67724226b2..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DataClassificationConfig.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dataclassificationconfig -applicable: Exchange Online -title: Get-DataClassificationConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-DataClassificationConfig - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-DataClassificationConfig cmdlet to view the data classification configuration for your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DataClassificationConfig [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DataClassificationConfig -``` - -This example returns the data classification configuration for your organization. - -## 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-dlp/Get-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpCompliancePolicy.md deleted file mode 100644 index e4573a7090..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpCompliancePolicy.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Get-DlpCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DlpCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DlpCompliancePolicy to view Data Loss Prevention (DLP) policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpCompliancePolicy [[-Identity] <PolicyIdParameter>] [-DistributionDetail] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpCompliancePolicy -``` - -This example displays summary information for all DLP policies in the Security & Compliance Center. - -### Example 2 -```powershell -Get-DlpCompliancePolicy -Identity "PII Limited" | Format-List -``` - -This example displays detailed information for the DLP policy named "PII Limited". - -## PARAMETERS - -### -DistributionDetail -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpComplianceRule.md deleted file mode 100644 index fa223b03cc..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpComplianceRule.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpcompliancerule -applicable: Office 365 Security & Compliance Center -title: Get-DlpComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DlpComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DlpComplianceRule to view Data Loss Prevention (DLP) rules in the Security & Compliance Center. DLP rules identify and protect sensitive information. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpComplianceRule [[-Identity] <ComplianceRuleIdParameter>] - [-IncludeExecutionRuleGuids Boolean] - [-Policy <PolicyIdParameter>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpComplianceRule -``` - -This example displays summary information for all DLP rules in the Security & Compliance Center. - -### Example 2 -```powershell -Get-DlpComplianceRule -Identity "PII SS# Custom" | Format-List -``` - -This example displays detailed information for the DLP rule named "PII SS# Custom". - -### Example 3 -```powershell -Get-DlpComplianceRule -Policy "PII Limited" -``` - -This example lists all the rules included in the DLP compliance policy named "PII Limited". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IncludeExecutionRuleGuids -{{ Fill IncludeExecutionRuleGuids Description }} - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policy -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 - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpDetailReport.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpDetailReport.md deleted file mode 100644 index 48e2f794a6..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpDetailReport.md +++ /dev/null @@ -1,311 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpdetailreport -applicable: Exchange Online -title: Get-DlpDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-DlpDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-DlpDetailReport cmdlet to list details about Data Loss Prevention (DLP) rule matches for Exchange Online, SharePoint Online, and OneDrive for Business in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpDetailReport [-Action <MultiValuedProperty>] [-Actor <MultiValuedProperty>] - [-DlpCompliancePolicy <MultiValuedProperty>] [-DlpComplianceRule <MultiValuedProperty>] [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] [-Expression <Expression>] [-Page <Int32>] [-PageSize <Int32>] - [-Source <MultiValuedProperty>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-DlpDetailReport cmdlet returns detailed information about specific DLP rule matches for the last 7 days. Although the cmdlet accepts date ranges older than 7 days, only information about the last 7 days are returned. The properties returned include: - -- Date - -- Title - -- Location - -- Severity - -- Size - -- Source - -- Actor - -- DLPPolicy - -- UserAction - -- Justification - -- SensitiveInformationType - -- SensitiveInformationCount - -- SensitiveInformationConfidence - -- EventType - -- Action - -- ObjectId - -To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpdetectionsreport) cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpDetailReport -StartDate 11/01/2018 -EndDate 11/07/2018 -``` - -The following example lists the details of all the DLP policy activities defined in your organization between the dates specified. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies. Valid values are: - -- BlockAccess - -- GenerateIncidentReport - -- NotifyUser - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Actor -The Actor parameter filters the report by the user who last modified the item. You can enter multiple users separated by commas. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DlpCompliancePolicy -The DlpCompliancePolicy parameter filters the report by the name of the DLP compliance policy. You can specify multiple policies separated by commas. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DlpComplianceRule -The DlpComplianceRule parameter filters the report by the name of the DLP compliance rule. You can specify multiple rules separated by commas. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. Valid values are: - -- DLPActionHits - -- DLPPolicyFalsePositive - -- DLPPolicyHits - -- DLPPolicyOverride - -- DLPRuleHits - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Source -The Source parameter filters the report by workload. Valid values are: - -- EXCH: Exchange Online - -- ODB: OneDrive for Business - -- SPO: SharePoint Online - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpDetectionsReport.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpDetectionsReport.md deleted file mode 100644 index 23d19b3e69..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpDetectionsReport.md +++ /dev/null @@ -1,324 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpdetectionsreport -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-DlpDetectionsReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-DlpDetectionsReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-DlpDetectionsReport cmdlet to list a summary of Data Loss Prevention (DLP) rule matches for Exchange Online, SharePoint Online and OneDrive for Business in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpDetectionsReport [-Action <MultiValuedProperty>] [-AggregateBy <String>] - [-DlpCompliancePolicy <MultiValuedProperty>] [-DlpComplianceRule <MultiValuedProperty>] [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] [-Expression <Expression>] [-Page <Int32>] [-PageSize <Int32>] - [-Source <MultiValuedProperty>] [-StartDate <DateTime>] [-SummarizeBy <MultiValuedProperty>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-DlpDetectionsReport cmdlet returns general DLP detection data that's aggregated per day. The properties returned include: - -- Date - -- DlpPolicy - -- TransportRule - -- Action - -- EventType - -- MessageCount - -- Source - -- StartDate - -- EndDate - -To see detailed information about each DLP rule match, use the Get-DlpDetailReport cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpDetectionsReport -StartDate 11/01/2018 -EndDate 11/30/2018 -``` - -This example lists the DLP activities for November, 2018. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies. Valid values are: - -- BlockAccess - -- GenerateIncidentReport - -- NotifyUser - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AggregateBy -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DlpCompliancePolicy -The DlpCompliancePolicy parameter filters the report by the name of the DLP compliance policy. You can specify multiple policies separated by commas. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DlpComplianceRule -The DlpComplianceRule parameter filters the report by the name of the DLP compliance rule. You can specify multiple rules separated by commas. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. Valid values are: - -- DLPActionHits - -- DLPPolicyFalsePositive - -- DLPPolicyHits - -- DLPPolicyOverride - -- DLPRuleHits - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Source -The Source parameter filters the report by workload. Valid values are: - -- EXCH: Exchange Online - -- ODB: OneDrive for Business - -- SPO: SharePoint Online - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SummarizeBy -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 the Get-DLPDetectionsReport cmdlet, the SummarizeBy parameter accepts the following values: - -- Action - -- DLPPolicy - -- Domain - -- EventType - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema.md deleted file mode 100644 index 86dcfacb57..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema -applicable: Office 365 Security & Compliance Center -title: Get-DlpEdmSchema -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DlpEdmSchema - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DlpEdmSchema cmdlet to view exact data match (EDM) data loss prevention (DLP) schemas in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpEdmSchema [[-Identity] <EdmStorageIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpEdmSchema -``` - -This example returns a summary list of all DLP EDM schemas in the organization. - -### Example 2 -```powershell -Get-DlpEdmSchema -Identity "Schema for Patient Records" -``` - -This example returns detailed information for the DLP EDM schema named Schema for patient Records. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -```yaml -Type: EdmStorageIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Create custom sensitive information types with Exact Data Match based classification](https://docs.microsoft.com/microsoft-365/compliance/create-custom-sensitive-information-types-with-exact-data-match-based-classification) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpKeywordDictionary.md deleted file mode 100644 index 0a24138376..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpKeywordDictionary.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpkeyworddictionary -applicable: Office 365 Security & Compliance Center -title: Get-DlpKeywordDictionary -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DlpKeywordDictionary - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DlpKeywordDictionary cmdlet to view data loss prevention (DLP) keyword dictionaries in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpKeywordDictionary [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpKeywordDictionary | Format-Table -Auto Name,Description -``` - -This example returns a summary list of all DLP keyword dictionaries. - -### Example 2 -```powershell -Get-DlpKeywordDictionary -Name "Financial Data" -``` - -This example returns detailed information about the DLP keyword dictionary named Financial Data. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpPolicy.md deleted file mode 100644 index 0a8004b930..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpPolicy.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlppolicy -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-DlpPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-DlpPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-DlpPolicy cmdlet to view information about existing data loss prevention (DLP) policies. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpPolicy [[-Identity] <DlpPolicyIdParameter>] [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpPolicy -``` - -This example returns a summary list of all DLP policies. - -### Example 2 -```powershell -Get-DlpPolicy "Employee Numbers" | Format-List -``` - -This example returns detailed information about the DLP policy named Employee Numbers. The command is piped to the Format-List cmdlet to display the detailed configuration of the specified DLP policy. - -## PARAMETERS - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the DLP policy you want to remove. 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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-dlp/Get-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationType.md deleted file mode 100644 index 8f1ce341f9..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationType.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpsensitiveinformationtype -applicable: Office 365 Security & Compliance Center -title: Get-DlpSensitiveInformationType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-DlpSensitiveInformationType - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DlpSensitiveInformationType cmdlet to list the sensitive information types that are defined for your organization in the Security & Compliance Center. Sensitive information types are used by Data Loss Prevention (DLP) rules to check for sensitive information such as social security, passport, or credit card numbers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpSensitiveInformationType [[-Identity] <SensitiveInformationTypeIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -The RecommendedConfidence property of the returned objects contains a value that represents the default (or recommended) confidence level that should be used with the corresponding sensitive information type. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpSensitiveInformationType -``` - -This example lists all the sensitive information types defined for your organization. - -### Example 2 -```powershell -Get-DlpSensitiveInformationType -Identity "Credit Card Number" | Format-List -``` - -This example lists all the properties of the sensitive information type named "Credit Card Number". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the sensitive information type that you want to view. Valid values are: - -- Name - -- Id (GUID value) - -```yaml -Type: SensitiveInformationTypeIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationTypeRulePackage.md deleted file mode 100644 index bced9bc945..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationTypeRulePackage.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpsensitiveinformationtyperulepackage -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-DlpSensitiveInformationTypeRulePackage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-DlpSensitiveInformationTypeRulePackage - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DlpSensitiveInformationTypeConfig cmdlet to view data loss prevention (DLP) sensitive information type rule packages in the Security & Compliance Center. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpSensitiveInformationTypeRulePackage [[-Identity] <SensitiveInformationTypeRuleCollectionIdParameter>] - [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DlpSensitiveInformationTypeRulePackage -``` - -This example returns a summary list of all sensitive information type rule packages in the organization. - -### Example 2 -```powershell -Get-DlpSensitiveInformationTypeRulePackage -Identity "Microsoft Rule Package" | Format-List -``` - -This example returns detailed information for the sensitive information type rule package named Microsoft Rule Package. - -## PARAMETERS - -### -Identity -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 - -- LocalizedName - -- GUID (from the Identity value) - -```yaml -Type: SensitiveInformationTypeRuleCollectionIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSiDetectionsReport.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSiDetectionsReport.md deleted file mode 100644 index 6ccf32dd7a..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpSiDetectionsReport.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/get-dlpsidetectionsreport -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-DlpSiDetectionsReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-DlpSiDetectionsReport - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DlpSiDetectionsReport cmdlet to view information about data loss prevention (DLP) sensitive information type detections in the Security & Compliance Center. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DlpSiDetectionsReport [-EndDate <DateTime>] [-SensitiveType <MultiValuedProperty>] [<CommonParameters>] -``` - -## DESCRIPTION -For the reporting period you specify, the cmdlet returns the following information: - -- Organization - -- Date - -- SensitiveType: The GUID value of the DLP sensitive information type. To match the GUID value to the name of the sensitive information type, replace \<GUID\> with the GUID value and run this command: Get-DlpSensitiveInformationType -Identity \<GUID\>. - -- DocumentCount: The number of documents that contain the detected sensitive information type. - -- ProtectionStatus: Values are Unprotected (the sensitive information type is not defined in any DLP policy) or Protected (the sensitive information type is defined in a DLP policy). - -- DlpComplianceRuleIds: The GUID value of the DLP compliance rule that detected the sensitive information type (for ProtectionStatus values of Protected). To match the GUID value to the name of the DLP compliance rule, replace \<GUID\> with the GUID value and run this command: Get-DlpComplianceRule -Identity \<GUID\>. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DLPSiDetectionsReport -``` - -This example returns all DLP sensitive information type detections. - -### Example 2 -```powershell -Get-DLPSiDetectionsReport -SensitiveType 0e9b3178-9678-47dd-a509-37222ca96b42 -StartDate 4/1/2019 -EndDate 4/8/2019 -``` - -This example returns detections for the sensitive information type 0e9b3178-9678-47dd-a509-37222ca96b42 (EU Debit Card Number) during the specified date range. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SensitiveType -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\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpCompliancePolicy.md deleted file mode 100644 index 7dc30683a2..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpCompliancePolicy.md +++ /dev/null @@ -1,409 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: New-DlpCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DlpCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DlpCompliancePolicy cmdlet to create Data Loss Prevention (DLP) policies in the Security & Compliance Center. DLP policies contain DLP rules that identify, monitor, and protect sensitive information. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DlpCompliancePolicy [-Name] <String> - [-Comment <String>] - [-Confirm] - [-ExchangeLocation <MultiValuedProperty>] - [-ExchangeSenderMemberOf <SmtpAddress[]>] - [-ExchangeSenderMemberOfException <SmtpAddress[]>] - [-Force] - [-Mode <PolicyMode>] - [-OneDriveLocation <MultiValuedProperty>] - [-OneDriveLocationException <MultiValuedProperty>] - [-Priority <Int32>] - [-SharePointLocation <MultiValuedProperty>] - [-SharePointLocationException <MultiValuedProperty>] - [-SharePointOnPremisesLocationException <MultiValuedProperty>] - [-SharePointServerLocation <MultiValuedProperty>] - [-TeamsLocation <MultiValuedProperty>] - [-TeamsLocationException <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-DlpCompliancePolicy -Name "GlobalPolicy" -SharePointLocation All -``` - -This example creates a DLP policy named GlobalPolicy that will be enforced across all SharePoint Online locations. - -### Example 2 -```powershell -New-DlpCompliancePolicy -Name "GlobalPolicy" -Comment "Primary policy" -SharePointLocation "https://my.url/","https://my.url2/" -OneDriveLocation "https://my.url3/","https://my.url4/" -Mode Enable -``` - -This example creates a DLP policy named GlobalPolicy for the specified SharePoint Online and OneDrive for Business locations. The new policy has a descriptive comment and will be enabled on creation. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocation -The ExchangeLocation parameter specifies Exchange Online mailboxes to include in the DLP policy. You can only use the value All for this parameter to include all mailboxes. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeSenderMemberOf -The ExchangeSenderMemberOf parameter specifies the distribution groups, mail-enabled security groups, or dynamic distribution groups to include in the DLP policy. You identify the group by its email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. - -You can't use this parameter to specify Office 365 Groups. - -```yaml -Type: SmtpAddress[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeSenderMemberOfException -The ExchangeSenderMemberOf parameter specifies the distribution groups, mail-enabled security groups, or dynamic distribution groups to exclude from the DLP policy. You identify the group by its email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. - -You can't use this parameter to specify Office 365 Groups. - -```yaml -Type: SmtpAddress[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mode -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. - -- Disable: The policy is disabled. - -- TestWithNotifications: No actions are taken, but notifications are sent. - -- TestWithoutNotifications: An audit mode where no actions are taken, and no notifications are sent. - -```yaml -Type: PolicyMode -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocation -The OneDriveLocation parameter specifies the OneDrive for Business sites to include. You identify the site by its URL value, or you can use the value All to include all sites. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocationException -This parameter specifies the OneDrive for Business sites to exclude 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 5 policies are from 0 through 4. - -- Valid priority values for a new 6th policy are from 0 through 5. - -- The default value for a new 6th policy is 5. - -If you modify the priority value of a policy, the position of the policy in the list changes to match the priority value you specify. In other words, if you set the priority value of a policy to the same value as an existing policy, the priority value of the existing policy and all other lower priority policies after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocation -The SharePointLocation parameter specifies the SharePoint Online sites to include. You identify the site by its URL value, or you can use the value All to include all sites. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". SharePoint Online sites can't be added to a policy until they have been indexed. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocationException -This parameter specifies the SharePoint Online sites to exclude 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointOnPremisesLocationException -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointServerLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamsLocation -The TeamsLocation parameter specifies the Teams accounts to include in the DLP policy. You identify the account by its name or email address, or you can use the value All to include all accounts. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamsLocationException -The TeamsLocation parameter specifies the Teams accounts to exclude form the DLP policy when you use the value All for the TeamsLocation parameter. You identify the account by its name or email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md deleted file mode 100644 index fbde5610fb..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md +++ /dev/null @@ -1,1483 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpcompliancerule -applicable: Office 365 Security & Compliance Center -title: New-DlpComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DlpComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DlpComplianceRule to create Data Loss Prevention (DLP) rules in the Security & Compliance Center. DLP rules define sensitive information to be protected and the actions to take on rule matches. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DlpComplianceRule [-Name] <String> -Policy <PolicyIdParameter> - [-AccessScope <AccessScope>] - [-ActivationDate <DateTime>] - [-AnyOfRecipientAddressContainsWords <MultiValuedProperty>] - [-AnyOfRecipientAddressMatchesPatterns <MultiValuedProperty>] - [-BlockAccess <Boolean>] - [-BlockAccessScope <BlockAccessScope>] - [-Comment <String>] - [-Confirm] - [-ContentContainsSensitiveInformation <PswsHashtable[]>] - [-ContentExtensionMatchesWords <MultiValuedProperty>] - [-ContentPropertyContainsWords <MultiValuedProperty>] - [-Disabled <Boolean>] - [-DocumentIsPasswordProtected <Boolean> - [-DocumentIsUnsupported <Boolean>] - [-DocumentNameMatchesPatterns <MultiValuedProperty>] - [-DocumentNameMatchesWords <MultiValuedProperty>] - [-EncryptRMSTemplate <RmsTemplateIdParameter>] - [-ExceptIfAccessScope <AccessScope>] - [-ExceptIfAnyOfRecipientAddressContainsWords <MultiValuedProperty>] - [-ExceptIfAnyOfRecipientAddressMatchesPatterns <MultiValuedProperty>] - [-ExceptIfContentContainsSensitiveInformation <PswsHashtable[]>] - [-ExceptIfContentExtensionMatchesWords <MultiValuedProperty>] - [-ExceptIfContentPropertyContainsWords <MultiValuedProperty>] - [-ExceptIfDocumentIsPasswordProtected <Boolean>] - [-ExceptIfDocumentIsUnsupported <Boolean>] - [-ExceptIfDocumentNameMatchesPatterns <MultiValuedProperty>] - [-ExceptIfDocumentNameMatchesWords <MultiValuedProperty>] - [-ExceptIfFromAddressContainsWords <MultiValuedProperty>] - [-ExceptIfFromAddressMatchesPatterns <MultiValuedProperty>] - [-ExceptIfProcessingLimitExceeded <Boolean>] - [-ExceptIfRecipientDomainIs <MultiValuedProperty>] - [-ExceptIfSenderIPRanges <MultiValuedProperty>] - [-ExceptIfSentTo <MultiValuedProperty>] - [-ExceptIfSubjectContainsWords <MultiValuedProperty>] - [-ExceptIfSubjectMatchesPatterns <MultiValuedProperty>] - [-ExpiryDate <DateTime>] - [-From <SmtpAddress[]>] - [-FromAddressContainsWords <MultiValuedProperty>] - [-FromAddressMatchesPatterns <MultiValuedProperty>] - [-FromMemberOf <SmtpAddress[]>] - [-GenerateAlert <MultiValuedProperty>] - [-GenerateIncidentReport <MultiValuedProperty>] - [-ImmutableId <Guid>] - [-IncidentReportContent <ReportContentOption[]>] - [-NotifyAllowOverride <OverrideOption[]>] - [-NotifyEmailCustomText <String>] - [-NotifyPolicyTipCustomText <String>] - [-NotifyPolicyTipCustomTextTranslations <MultiValuedProperty>] - [-NotifyUser <MultiValuedProperty>] - [-Priority <Int32>] - [-ProcessingLimitExceeded <Boolean>] - [-RecipientDomainIs <MultiValuedProperty>] - [-RemoveHeader <MultiValuedProperty>] - [-ReportSeverityLevel <RuleSeverity>] - [-RuleErrorAction <PolicyRuleErrorAction>] - [-SenderIPRanges <MultiValuedProperty>] - [-SentTo <MultiValuedProperty>] - [-SetHeader <PswsHashtable>] - [-StopPolicyProcessing <Boolean>] - [-SubjectContainsWords <MultiValuedProperty>] - [-SubjectMatchesPatterns <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Each new rule must contain one condition filter or test, and one associated action. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-DlpComplianceRule -Name "SocialSecurityRule" -Policy "USFinancialChecks" -ContentContainsSensitiveInformation @{Name="U.S. Social Security Number (SSN)"} -BlockAccess $True -``` - -This example create a new DLP compliance rule named "SocialSecurityRule" that is assigned to the "USFinancialChecks" policy. The rule checks for social security numbers and blocks access if it finds them. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policy -The Policy parameter specifies the existing DLP policy that will contain the DLP rule. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AccessScope -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 inside the organization. - -- NotInOrganization: The rule is applied to content that's accessible outside the organization. - -- None: The condition isn't used. - -```yaml -Type: AccessScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActivationDate -This parameter is reserved for internal Microsoft use. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfRecipientAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfRecipientAddressMatchesPatterns -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 10. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockAccess -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. - -- $false: Allows access to the source item that matched the rule. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockAccessScope -The BlockAccessScope parameter specifies the scope of the block access action. Valid values are: - -- All: Block access to everyone except the owner and the last modifier. - -- PerUser: Block access to external users. - -```yaml -Type: BlockAccessScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentContainsSensitiveInformation -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"}). - -Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://go.microsoft.com/fwlink/p/?LinkId=529420). - -```yaml -Type: PswsHashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentExtensionMatchesWords -The ContentExtensionMatchesWords parameter specifies a condition for the DLP 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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentPropertyContainsWords -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\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter specifies whether the DLP rule is disabled. Valid values are: - -- $true: The rule is disabled. - -- $false: The rule is enabled. This is the default value. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentIsPasswordProtected -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 only works for Office documents and .zip files. Valid values are: - -- $true: Look for password protected files. - -- $false: Don't look for password protected files. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentIsUnsupported -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. - -- $false: Don't look for unsupported files that can't be scanned. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentNameMatchesPatterns -The DocumentNameMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in the file 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 10. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentNameMatchesWords -The DocumentNameMatchesWords parameter specifies a condition for the DLP rule that looks for words or phrases in the file name of message attachments. You can specify multiple words or phrases separated by commas. - -- Single word: "no_reply" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptRMSTemplate -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. - -```yaml -Type: RmsTemplateIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfAccessScope -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 inside the organization. - -- NotInOrganization: The rule isn't applied to content that's accessible outside the organization. - -- None: The exception isn't used. - -```yaml -Type: AccessScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfAnyOfRecipientAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfAnyOfRecipientAddressMatchesPatterns -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 10. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfContentContainsSensitiveInformation -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. - -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"}). - -Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://go.microsoft.com/fwlink/p/?LinkId=529420). - -```yaml -Type: PswsHashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfContentExtensionMatchesWords -The ExceptIfContentExtensionMatchesWords parameter specifies an exception for the DLP 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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfContentPropertyContainsWords -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\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentIsPasswordProtected -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 only works for Office documents and .zip files. Valid values are: - -- $true: Look for password protected files. - -- $false: Don't look for password protected files. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentIsUnsupported -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. - -- $false: Don't look for unsupported files that can't be scanned. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentNameMatchesPatterns -The ExceptIfDocumentNameMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in the file 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 10. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentNameMatchesWords -The ExceptIfDocumentNameMatchesWords parameter specifies an exception for the DLP rule that looks for words or phrases in the file name of message attachments. You can specify multiple words or phrases separated by commas. - -- Single word: "no_reply" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfFromAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfFromAddressMatchesPatterns -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 10. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfProcessingLimitExceeded -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. - -- $false: Don't look for files where scanning couldn't complete. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception for the DLP rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSenderIPRanges -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. - -- IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. - -You can specify multiple IP addresses or ranges separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -The ExceptIfSentTo parameter specifies an exception for the DLP rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSubjectContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSubjectMatchesPatterns -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 10. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExpiryDate -This parameter is reserved for internal Microsoft use. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -From -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SmtpAddress[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FromAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FromAddressMatchesPatterns -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 10. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FromMemberOf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SmtpAddress[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GenerateAlert -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. - -- SiteAdmin - -You can specify multiple values separated by commas. - -The email message that's generated by this action contains a link to detailed information in the Security & Compliance Center (the details aren't in the email message itself). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GenerateIncidentReport -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. - -- SiteAdmin - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImmutableId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncidentReportContent -The IncidentReportContent parameter specifies the content to include in the report when you use the GenerateIncidentReport parameter. Valid values are: - -- All - -- Default - -- DetectionDetails - -- Detections - -- DocumentAuthor - -- DocumentLastModifier - -- MatchedItem - -- OriginalContent - -- RulesMatched - -- Service - -- Severity - -- Title - -You can specify multiple values separated by commas. You can only use the value All by itself. If you use the value Default, the report includes the following content: - -- DocumentAuthor - -- MatchedItem - -- RulesMatched - -- Service - -- Title - -Therefore, if you use any of these redundant values with the value Default, they will be ignored. - -```yaml -Type: ReportContentOption[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyAllowOverride -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. - -- WithoutJustification: Allows overrides without justification. - -- WithJustification: Allows overrides with justification. - -You can specify multiple values separated by commas. The values WithoutJustification and WithJustification are mutually exclusive. - -```yaml -Type: OverrideOption[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyEmailCustomText -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): - -- %%AppliedActions%%: The actions applied to the content. - -- %%ContentURL%%: The URL of the document on the SharePoint site or OneDrive for Business site. - -- %%MatchedConditions%%: The conditions that were matched by the content. Use this token to inform people of possible issues with the content. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyPolicyTipCustomText -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyPolicyTipCustomTextTranslations -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUser -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. - -- LastModifier - -- Owner - -- SiteAdmin - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new 9th rule that you add to the policy are from 0 through 8. - -- The default value for a new 9th rule that you add to the policy is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProcessingLimitExceeded -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. - -- $false: Don't look for files where scanning couldn't complete. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition for the DLP rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveHeader -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. - -You can use this action in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportSeverityLevel -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. - -- Low: This is the default value. - -- Medium - -- High - -```yaml -Type: RuleSeverity -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RuleErrorAction -The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: - -- Ignore - -- RetryThenBlock - -- Blank (the value $null): This is the default value. - -```yaml -Type: PolicyRuleErrorAction -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderIPRanges -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. - -- IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. - -You can specify multiple IP addresses or ranges separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -The SentTo parameter specifies a condition for the DLP rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SetHeader -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. - -You can use this action in DLP policies that are scoped only to Exchange. - -```yaml -Type: PswsHashtable -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StopPolicyProcessing -The StopPolicyProcessing parameter specifies an action that stops processing more DLP policy rules. Valid values are: - -- $true: Stop processing more rules. - -- $false: Continue processing more rules after this one. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubjectContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubjectMatchesPatterns -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 10. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpEdmSchema.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpEdmSchema.md deleted file mode 100644 index d6e38cb122..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpEdmSchema.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpedmschema -applicable: Office 365 Security & Compliance Center -title: New-DlpEdmSchema -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DlpEdmSchema - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DlpEdmSchema cmdlet to create exact data match (EDM)-based classification schemas in the Security & Compliance Center. Such schemas can be used with data loss prevention (DLP) policies. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DlpEdmSchema [-FileData] <Byte[]> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -For an explanation and example of the EDM schema, see [Define the schema for your database of sensitive information](https://docs.microsoft.com/microsoft-365/compliance/create-custom-sensitive-information-types-with-exact-data-match-based-classification#define-the-schema-for-your-database-of-sensitive-information). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$edmSchemaXml = Get-Content "C:\My Documents\edm.xml" -Encoding Byte -ReadCount 0; New-DlpEdmSchema -FileData $edmSchemaXml -Confirm:$true -``` - -This example creates a new DLP EDM schema. The first command reads the schema in the XML file to a variable, and the second command uses that information to create the DLP EDM schema. - -## PARAMETERS - -### -FileData -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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpFingerprint.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpFingerprint.md deleted file mode 100644 index f71c6a1703..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpFingerprint.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpfingerprint -applicable: Office 365 Security & Compliance Center -title: New-DlpFingerprint -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DlpFingerprint - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DlpFingerprint cmdlet to create document fingerprints that are used with data loss prevention (DLP) sensitive information types in the Security & Compliance Center. Because the results of New-DlpFingerprint aren't stored outside of the sensitive information type, you always run New-DlpFingerprint and New-DlpSensitiveInformationType or Set-DlpSensitiveInformationType in the same PowerShell session. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DlpFingerprint [[-FileData] <Byte[]>] -Description <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$Patent_Template = Get-Content "C:\My Documents\Contoso Patent Template.docx" -Encoding byte; $Patent_Fingerprint = New-DlpFingerprint -FileData $Patent_Template -Description "Contoso Patent Template" -``` - -This example creates a new document fingerprint based on the file C:\\My Documents\\Contoso Patent Template.docx. You store the new fingerprint as a variable so you can use it with the New-DlpSensitiveInformationType cmdlet in the same PowerShell session. - -## PARAMETERS - -### -Description -The Description parameter specifies a description for the document fingerprint. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileData -The FileData parameter specifies the file to use as a document fingerprint. - -You need to read the file to a byte-encoded object using the Get-Content cmdlet. For details, see the Examples section in this topic. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpKeywordDictionary.md deleted file mode 100644 index 5917632843..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpKeywordDictionary.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpkeyworddictionary -applicable: Office 365 Security & Compliance Center -title: New-DlpKeywordDictionary -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DlpKeywordDictionary - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DlpKeywordDictionary cmdlet to create data loss prevention (DLP) keyword dictionaries in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DlpKeywordDictionary -Name <String> [-Confirm] [-Description <String>] [-FileData <Byte[]>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary will appear in your list of sensitive information types, and you can use it in policies. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$Keywords = @("Aarskog's syndrome","Abandonment","Abasia","Abderhalden-Kaufmann-Lignac","Abdominalgia","Abduction contracture","Abetalipo proteinemia","Abiotrophy","Ablatio","ablation","Ablepharia","Abocclusion","Abolition","Aborter","Abortion","Abortus","Aboulomania","Abrami's disease","Abramo"); -$EncodedKeywords = $Keywords | ForEach-Object{[System.Text.Encoding]::UTF8.GetBytes($_+"`r`n")}; -New-DlpKeywordDictionary -Name "Diseases" -Description "Names of diseases and injuries from ICD-10-CM lexicon" -FileData $EncodedKeywords -``` - -This example creates a DLP keyword dictionary named Diseases by using the specified values. - -### Example 2 -```powershell -$Keywords = Get-Content "C:\My Documents\InappropriateTerms.txt"; -$EncodedKeywords = $Keywords | ForEach-Object{[System.Text.Encoding]::UTF8.GetBytes($_+"`r`n")}; -New-DlpKeywordDictionary -Name "Inappropriate Language" -Description "Unprofessional and inappropriate terminology" -FileData $EncodedKeywords -``` - -This example creates a DLP keyword dictionary named Inappropriate Language from the file C:\\My Documents\\InappropriateTerms.txt. The file contains one term on each line. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileData -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 UTF8. For more information, see the examples in this topic. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationType.md deleted file mode 100644 index 0c916efdda..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationType.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-dlpsensitiveinformationtype -applicable: Office 365 Security & Compliance Center -title: New-DlpSensitiveInformationType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DlpSensitiveInformationType - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DlpSensitiveInformationType cmdlet to create sensitive information type rules that use document fingerprints. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DlpSensitiveInformationType [-Name] <String> -Description <String> -Fingerprints <MultiValuedProperty> - [-SensitiveInformationTypeRuleCollectionIdentity <SensitiveInformationTypeRuleCollectionIdParameter>] [-Confirm] - [-Locale <CultureInfo>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$Employee_Template = Get-Content "C:\My Documents\Contoso Employee Template.docx" -Encoding byte -ReadCount 0; $Employee_Fingerprint = New-DlpFingerprint -FileData $Employee_Template -Description "Contoso Employee Template"; $Customer_Template = Get-Content "D:\Data\Contoso Customer Template.docx" -Encoding byte; $Customer_Fingerprint = New-DlpFingerprint -FileData $Customer_Template -Description "Contoso Customer Template"; New-DlpSensitiveInformationType -Name "Contoso Employee-Customer Confidential" -Fingerprints $Employee_Fingerprint[0],$Customer_Fingerprint[0] -Description "Message contains Contoso employee or customer information." -``` - -This example creates a new sensitive information type rule named "Contoso Employee-Customer Confidential" that uses the document fingerprints of the files C:\\My Documents\\Contoso Employee Template.docx and D:\\Data\\Contoso Customer Template.docx. - -## PARAMETERS - -### -Description -The Description parameter specifies a description for the sensitive information type rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Fingerprints -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://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/new-fingerprint) or the Examples section. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Name -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SensitiveInformationTypeRuleCollectionIdentity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: ClassificationRuleCollectionIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Locale -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://go.microsoft.com/fwlink/p/?linkId=184859). - -You can add additional language translations to the sensitive information type rule by using the Set-DlpSensitiveInformationType cmdlet. - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage.md deleted file mode 100644 index fb195bd9cd..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage -applicable: Office 365 Security & Compliance Center -title: New-DlpSensitiveInformationTypeRulePackage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-DlpSensitiveInformationTypeRulePackage - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-DlpSensitiveInformationTypeConfig cmdlet to import data loss prevention (DLP) sensitive information type rule packages in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-DlpSensitiveInformationTypeRulePackage [-FileData] <Byte[]> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell - -New-DlpSensitiveInformationTypeRulePackage -FileData ([Byte[]]$(Get-Content -Path "C:\My Documents\External Sensitive Info Type Rule Collection.xml" -Encoding Byte -ReadCount 0)) -``` - -This example imports the sensitive information type rule package C:\\My Documents\\External Sensitive Info Type Rule Collection.xml. - -## PARAMETERS - -### -FileData -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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Create custom sensitive information types with Exact Data Match based classification](https://docs.microsoft.com/microsoft-365/compliance/create-custom-sensitive-information-types-with-exact-data-match-based-classification) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpCompliancePolicy.md deleted file mode 100644 index 75a94b9941..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpCompliancePolicy.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlpcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Remove-DlpCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DlpCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DlpCompliancePolicy cmdlet to remove Data Loss Prevention (DLP) policies from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DlpCompliancePolicy [-Identity] <PolicyIdParameter> [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DlpCompliancePolicy -Identity 7e640345-1a7f-4f4e-9c17-681c070ed5e2 -``` - -This example removes a DLP policy specified by its GUID. - -### Example 2 -```powershell -Remove-DlpCompliancePolicy -Identity "PII Main Policy" -``` - -This example removes a DLP policy specified by its name. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRule.md deleted file mode 100644 index c5788f3e3f..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRule.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlpcompliancerule -applicable: Office 365 Security & Compliance Center -title: Remove-DlpComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DlpComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DlpComplianceRule cmdlet to remove Data Loss Prevention (DLP) rules from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DlpComplianceRule [-Identity] <PolicyIdParameter> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DlpComplianceRule -Identity "PII SS# Custom" -``` - -This example removes the DLP rule named "PII SS# Custom". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema.md deleted file mode 100644 index e1093c5844..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema -applicable: Office 365 Security & Compliance Center -title: Remove-DlpEdmSchema -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DlpEdmSchema - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DlpEdmSchema cmdlet to remove exact data match (EDM) data loss prevention (DLP) schemas from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DlpEdmSchema [-Identity] <EdmStorageIdParameter> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DlpEdmSchema -Identity "Schema for Patient Records" -``` - -This example removes the DLP EDM schema named Schema for Patient Records. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -```yaml -Type: EdmStorageIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Create custom sensitive information types with Exact Data Match based classification](https://docs.microsoft.com/microsoft-365/compliance/create-custom-sensitive-information-types-with-exact-data-match-based-classification) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpKeywordDictionary.md deleted file mode 100644 index 208746793d..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpKeywordDictionary.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlpkeyworddictionary -applicable: Office 365 Security & Compliance Center -title: Remove-DlpKeywordDictionary -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DlpKeywordDictionary - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DlpKeywordDictionary cmdlet to remove data loss prevention (DLP) keyword dictionaries from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DlpKeywordDictionary [-Identity] <SensitiveInformationTypeIdParameter> [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DlpKeywordDictionary -Identity "Financial Data" -``` - -This example remove the DLP keyword dictionary named Financial Data. - -## PARAMETERS - -### -Identity -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationType.md deleted file mode 100644 index ab9ed0fb44..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationType.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlpsensitiveinformationtype -applicable: Office 365 Security & Compliance Center -title: Remove-DlpSensitiveInformationType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DlpSensitiveInformationType - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DlpSensitiveInformationType cmdlet to remove sensitive information type rules that use document fingerprints. You can't use this cmdlet to remove built-in sensitive information type rules. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DlpSensitiveInformationType [-Identity] <DataClassificationIdParameter> [-Confirm] [-DomainController <Fqdn>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. - -**Note**: A "ManagementObjectNotFoundException" error means there was a synchronization problem between the Security & Compliance Center and Exchange Online. This happens when you try to remove data classifications that are being used in mail flow rules (also known as transport rules). You can remove the mail flow rule, wait for synchronization to finish, and then add the rule back. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-DlpSensitiveInformationType "Contoso Confidential" -``` - -This example removes the sensitive information type rule named "Contoso Confidential". - -## PARAMETERS - -### -Identity -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 - -- LocalizedName - -- Identity GUID value - -```yaml -Type: DataClassificationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationTypeRulePackage.md deleted file mode 100644 index 62bb6c18aa..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationTypeRulePackage.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/remove-dlpsensitiveinformationtyperulepackage -applicable: Office 365 Security & Compliance Center -title: Remove-DlpSensitiveInformationTypeRulePackage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-DlpSensitiveInformationTypeRulePackage - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-DlpSensitiveInformationTypeConfig cmdlet to remove data loss prevention (DLP) sensitive information type rule packages from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-DlpSensitiveInformationTypeRulePackage [-Identity] <SensitiveInformationTypeRuleCollectionIdParameter> - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$Rule = Get-DlpSensitiveInformationTypeRulePackage -Identity "Contoso Rule Pack"; $Rule | Remove-DlpSensitiveInformationTypeRulePackage -``` - -This example removes the third-party sensitive information type rule package named Contoso Rule Pack. The first command stores the identity of the rule package in a variable. The second command pipes the variable to the Remove-DlpSensitiveInformationTypeRulePackage cmdlet. - -## PARAMETERS - -### -Identity -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 - -- LocalizedName - -- GUID (from the Identity value) - -```yaml -Type: SensitiveInformationTypeRuleCollectionIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md deleted file mode 100644 index 81842dcf72..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md +++ /dev/null @@ -1,608 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlpcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Set-DlpCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DlpCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DlpCompliancePolicy cmdlet to modify Data Loss Prevention (DLP) policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity -``` -Set-DlpCompliancePolicy [-Identity] <PolicyIdParameter> - [-AddEndpointDlpLocation <MultiValuedProperty>] - [-AddEndpointDlpLocationException <MultiValuedProperty>] - [-AddExchangeLocation <MultiValuedProperty>] - [-AddOneDriveLocation <MultiValuedProperty>] - [-AddOneDriveLocationException <MultiValuedProperty>] - [-AddSharePointLocation <MultiValuedProperty>] - [-AddSharePointLocationException <MultiValuedProperty>] - [-AddTeamsLocation <MultiValuedProperty>] - [-AddTeamsLocationException <MultiValuedProperty>] - [-Comment <String>] - [-Confirm] - [-ExchangeSenderMemberOf <SmtpAddress[]>] - [-ExchangeSenderMemberOfException <SmtpAddress[]>] - [-Force] - [-Mode <PolicyMode>] - [-Priority <Int32>] - [-RemoveEndpointDlpLocation <MultiValuedProperty>] - [-RemoveEndpointDlpLocationException <MultiValuedProperty>] - [-RemoveExchangeLocation <MultiValuedProperty>] - [-RemoveOneDriveLocation <MultiValuedProperty>] - [-RemoveOneDriveLocationException <MultiValuedProperty>] - [-RemoveSharePointLocation <MultiValuedProperty>] - [-RemoveSharePointLocationException <MultiValuedProperty>] - [-RemoveTeamsLocation <MultiValuedProperty>] - [-RemoveTeamsLocationException <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### RetryDistribution -``` -Set-DlpCompliancePolicy [-Identity] <PolicyIdParameter> [-RetryDistribution] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-DlpCompliancePolicy -Identity "Main PII" -AddSharePointLocation "https://my.url1/","https://my.url2/" -AddOneDriveLocation "https://my.url3/","https://my.url4/" -``` - -This example adds the specified URLs to the SharePoint Online and OneDrive for Business locations for the DLP policy named Main PII without affecting the existing URL values. - -### Example 2 -```powershell -Set-DlpCompliancePolicy -Identity MainPII -Mode Disable -``` - -This example disables the "MainPII" policy. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RetryDistribution -The RetryDistribution switch redistributes the policy to all OneDrive for Business and SharePoint Online locations. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddEndpointDlpLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddEndpointDlpLocationException -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddOneDriveLocation -The AddOneDriveLocation parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddOneDriveLocationException -This parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocation -The AddSharePointLocation parameter specifies the SharePoint Online 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 Online sites can't be added to the policy until they have been indexed. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocationException -This parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddTeamsLocation -The AddTeamsLocation parameter specifies the Teams accounts to add to the list of included accounts when you aren't using the value All for the TeamsLocation parameter. You identify the account by its name or email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddTeamsLocationException -The AddTeamsLocationException parameter specifies the Teams accounts to add to the list of excluded accounts when you use the value All for the TeamsLocation parameter. You identify the account by its name or email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeSenderMemberOf -The ExchangeSenderMemberOf parameter specifies the distribution groups, mail-enabled security groups, or dynamic distribution groups to include in the DLP policy. You identify the group by its email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. - -You can't use this parameter to specify Office 365 Groups. - -```yaml -Type: SmtpAddress[] -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeSenderMemberOfException -The ExchangeSenderMemberOf parameter specifies the distribution groups, mail-enabled security groups, or dynamic distribution groups to exclude from the DLP policy. You identify the group by its email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. - -You can't use this parameter to specify Office 365 Groups. - -```yaml -Type: SmtpAddress[] -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mode -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. - -- Disable: The policy is disabled. - -- TestWithNotifications: No actions are taken, but notifications are sent. - -- TestWithoutNotifications: An audit mode where no actions are taken, and no notifications are sent. - -```yaml -Type: PolicyMode -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 5 policies are from 0 through 4. - -- Valid priority values for a new 6th policy are from 0 through 5. - -- The default value for a new 6th policy is 5. - -If you modify the priority value of a policy, the position of the policy in the list changes to match the priority value you specify. In other words, if you set the priority value of a policy to the same value as an existing policy, the priority value of the existing policy and all other lower priority policies after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveEndpointDlpLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveEndpointDlpLocationException -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocation -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveOneDriveLocation -The RemoveOneDriveLocation parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveOneDriveLocationException -This parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocation -The RemoveSharePointLocation parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocationException -This parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveTeamsLocation -The RemoveTeamsLocation parameter specifies the Teams accounts to remove from the list of included accounts when you use the value All for the TeamsLocation parameter. You identify the account by its name or email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveTeamsLocationException -The RemoveTeamsLocation parameter specifies the Teams accounts to remove from the list of excluded accounts when you aren't using the value All for the TeamsLocation parameter. You identify the account by its name or email address. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md deleted file mode 100644 index fb739f3ee9..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md +++ /dev/null @@ -1,1449 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlpcompliancerule -applicable: Office 365 Security & Compliance Center -title: Set-DlpComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DlpComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DlpComplianceRule to modify Data Loss Prevention (DLP) rules in the Security & Compliance Center. DLP rules define sensitive information to be protected and the actions to take on rule violations. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-DlpComplianceRule [-Identity] <ComplianceRuleIdParameter> - [-AccessScope <AccessScope>] - [-ActivationDate <DateTime>] - [-AnyOfRecipientAddressContainsWords <MultiValuedProperty>] - [-AnyOfRecipientAddressMatchesPatterns <MultiValuedProperty>] - [-BlockAccess <Boolean>] - [-BlockAccessScope <BlockAccessScope>] - [-Comment <String>] - [-Confirm] - [-ContentContainsSensitiveInformation <PswsHashtable[]>] - [-ContentExtensionMatchesWords <MultiValuedProperty>] - [-ContentPropertyContainsWords <MultiValuedProperty>] - [-Disabled <Boolean>] - [-DocumentIsPasswordProtected <Boolean>] - [-DocumentIsUnsupported <Boolean>] - [-DocumentNameMatchesPatterns <MultiValuedProperty>] - [-DocumentNameMatchesWords <MultiValuedProperty>] - [-EncryptRMSTemplate <RmsTemplateIdParameter>] - [-ExceptIfAccessScope <AccessScope>] - [-ExceptIfAnyOfRecipientAddressContainsWords <MultiValuedProperty>] - [-ExceptIfAnyOfRecipientAddressMatchesPatterns <MultiValuedProperty>] - [-ExceptIfContentContainsSensitiveInformation <PswsHashtable[]>] - [-ExceptIfContentExtensionMatchesWords <MultiValuedProperty>] - [-ExceptIfContentPropertyContainsWords <MultiValuedProperty>] - [-ExceptIfDocumentIsPasswordProtected <Boolean>] - [-ExceptIfDocumentIsUnsupported <Boolean>] - [-ExceptIfDocumentNameMatchesPatterns <MultiValuedProperty>] - [-ExceptIfDocumentNameMatchesWords <MultiValuedProperty>] - [-ExceptIfFromAddressContainsWords <MultiValuedProperty>] - [-ExceptIfFromAddressMatchesPatterns <MultiValuedProperty>] - [-ExceptIfProcessingLimitExceeded <Boolean>] - [-ExceptIfRecipientDomainIs <MultiValuedProperty>] - [-ExceptIfSenderIPRanges <MultiValuedProperty>] - [-ExceptIfSentTo <MultiValuedProperty>] - [-ExceptIfSubjectContainsWords <MultiValuedProperty>] - [-ExceptIfSubjectMatchesPatterns <MultiValuedProperty>] - [-ExpiryDate <DateTime>] - [-From <SmtpAddress[]>] - [-FromAddressContainsWords <MultiValuedProperty>] - [-FromAddressMatchesPatterns <MultiValuedProperty>] - [-FromMemberOf <SmtpAddress[]>] - [-GenerateAlert <MultiValuedProperty>] - [-GenerateIncidentReport <MultiValuedProperty>] - [-IncidentReportContent <ReportContentOption[]>] - [-NotifyAllowOverride <OverrideOption[]>] - [-NotifyEmailCustomText <String>] - [-NotifyPolicyTipCustomText <String>] - [-NotifyPolicyTipCustomTextTranslations <MultiValuedProperty>] - [-NotifyUser <MultiValuedProperty>] - [-Priority <Int32>] - [-ProcessingLimitExceeded <Boolean>] - [-RecipientDomainIs <MultiValuedProperty>] - [-RemoveHeader <MultiValuedProperty>] - [-ReportSeverityLevel <RuleSeverity>] - [-RuleErrorAction <PolicyRuleErrorAction>] - [-SenderIPRanges <MultiValuedProperty>] - [-SentTo <MultiValuedProperty>] - [-SetHeader <PswsHashtable>] - [-StopPolicyProcessing <Boolean>] - [-SubjectContainsWords <MultiValuedProperty>] - [-SubjectMatchesPatterns <MultiValuedProperty>] - [-ProcessingLimitExceeded <Boolean>] - [-ReportSeverityLevel <RuleSeverity>] - [-RuleErrorAction <PolicyRuleErrorAction>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-DlpComplianceRule -Identity 25bf67b6-3783-4f74-bde9-98dd40333082 -AccessScope NotInOrganization -BlockAccess $true -``` - -This example modifies the access scope and blocking behavior of a DLP compliance rule that's identified by its GUID value. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -- Id - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AccessScope -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 inside the organization. - -- NotInOrganization: The rule is applied to content that's accessible outside the organization. - -- None: The condition isn't used. - -```yaml -Type: AccessScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActivationDate -This parameter is reserved for internal Microsoft use. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfRecipientAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnyOfRecipientAddressMatchesPatterns -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 10. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockAccess -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. - -- $false: Allows access to the source item that matched the rule. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockAccessScope -The BlockAccessScope parameter specifies the scope of the block access action. Valid values are: - -- All: Block access to everyone except the owner and the last modifier. - -- PerUser: Block access to external users. - -```yaml -Type: BlockAccessScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentContainsSensitiveInformation -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"}). - -Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://go.microsoft.com/fwlink/p/?LinkId=529420). - -```yaml -Type: PswsHashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentExtensionMatchesWords -The ContentExtensionMatchesWords parameter specifies a condition for the DLP 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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentPropertyContainsWords -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\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter specifies whether the DLP rule is disabled. Valid values are: - -- $true: The rule is disabled. - -- $false: The rule is enabled. This is the default value. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentIsPasswordProtected -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 only works for Office documents and .zip files. Valid values are: - -- $true: Look for password protected files. - -- $false: Don't look for password protected files. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentIsUnsupported -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. - -- $false: Don't look for unsupported files that can't be scanned. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentNameMatchesPatterns -The DocumentNameMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in the file 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 10. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DocumentNameMatchesWords -The DocumentNameMatchesWords parameter specifies a condition for the DLP rule that looks for words or phrases in the file name of message attachments. You can specify multiple words or phrases separated by commas. - -- Single word: "no_reply" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptRMSTemplate -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. - -```yaml -Type: RmsTemplateIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfAccessScope -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 inside the organization. - -- NotInOrganization: The rule isn't applied to content that's accessible outside the organization. - -- None: The exception isn't used. - -```yaml -Type: AccessScope -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfAnyOfRecipientAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfAnyOfRecipientAddressMatchesPatterns -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 10. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfContentContainsSensitiveInformation -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. - -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"}). - -Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://go.microsoft.com/fwlink/p/?LinkId=529420). - -```yaml -Type: PswsHashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfContentExtensionMatchesWords -The ExceptIfContentExtensionMatchesWords parameter specifies an exception for the DLP 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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfContentPropertyContainsWords -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\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentIsPasswordProtected -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 only works for Office documents and .zip files. Valid values are: - -- $true: Look for password protected files. - -- $false: Don't look for password protected files. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentIsUnsupported -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. - -- $false: Don't look for unsupported files that can't be scanned. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentNameMatchesPatterns -The ExceptIfDocumentNameMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in the file 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 10. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfDocumentNameMatchesWords -The ExceptIfDocumentNameMatchesWords parameter specifies an exception for the DLP rule that looks for words or phrases in the file name of message attachments. You can specify multiple words or phrases separated by commas. - -- Single word: "no_reply" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfFromAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfFromAddressMatchesPatterns -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 10. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfProcessingLimitExceeded -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. - -- $false: Don't look for files where scanning couldn't complete. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfRecipientDomainIs -The ExceptIfRecipientDomainIs parameter specifies an exception for the DLP rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSenderIPRanges -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. - -- IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. - -You can specify multiple IP addresses or ranges separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSentTo -The ExceptIfSentTo parameter specifies an exception for the DLP rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSubjectContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExceptIfSubjectMatchesPatterns -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 10. - -You can use this exception in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExpiryDate -This parameter is reserved for internal Microsoft use. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -From -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SmtpAddress[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FromAddressContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word length is 128 characters. The maximum number of words or phrases is 50. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FromAddressMatchesPatterns -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 10. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FromMemberOf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SmtpAddress[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GenerateAlert -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. - -- SiteAdmin - -You can specify multiple values separated by commas. - -The email message that's generated by this action contains a link to detailed information in the Security & Compliance Center (the details aren't in the email message itself). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GenerateIncidentReport -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. - -- SiteAdmin - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncidentReportContent -The IncidentReportContent parameter specifies the content to include in the report when you use the GenerateIncidentReport parameter. Valid values are: - -- All - -- Default - -- Detections - -- DocumentAuthor - -- DocumentLastModifier - -- MatchedItem - -- RulesMatched - -- Service - -- Severity - -- Service - -- Title - -You can specify multiple values separated by commas. You can only use the value All by itself. If you use the value Default, the report includes the following content: - -- DocumentAuthor - -- MatchedItem - -- RulesMatched - -- Service - -- Title - -Therefore, if you use any of these redundant values with the value Default, they will be ignored. - -```yaml -Type: ReportContentOption[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyAllowOverride -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. - -- WithoutJustification: Allows overrides without justification. - -- WithJustification: Allows overrides with justification. - -You can specify multiple values separated by commas. The values WithoutJustification and WithJustification are mutually exclusive. - -```yaml -Type: OverrideOption[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyEmailCustomText -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): - -- %%AppliedActions%%: The actions applied to the content. - -- %%ContentURL%%: The URL of the document on the SharePoint site or OneDrive for Business site. - -- %%MatchedConditions%%: The conditions that were matched by the content. Use this token to inform people of possible issues with the content. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyPolicyTipCustomText -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyPolicyTipCustomTextTranslations -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUser -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. - -- LastModifier - -- Owner - -- SiteAdmin - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -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: - -- Valid priority values for the existing 8 rules are from 0 through 7. - -- Valid priority values for a new 9th rule that you add to the policy are from 0 through 8. - -- The default value for a new 9th rule that you add to the policy is 8. - -If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProcessingLimitExceeded -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. - -- $false: Don't look for files where scanning couldn't complete. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientDomainIs -The RecipientDomainIs parameter specifies a condition for the DLP rule that looks for recipients with email address in the specified domains. You can specify multiple domains separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveHeader -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. - -You can use this action in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportSeverityLevel -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. - -- Low: This is the default value. - -- Medium - -- High - -```yaml -Type: RuleSeverity -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RuleErrorAction -The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: - -- Ignore - -- RetryThenBlock - -- Blank (the value $null): This is the default value. - -```yaml -Type: PolicyRuleErrorAction -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderIPRanges -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. - -- IP address range: For example, 192.168.0.1-192.168.0.254. - -- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. - -You can specify multiple IP addresses or ranges separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SentTo -The SentTo parameter specifies a condition for the DLP rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SetHeader -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. - -You can use this action in DLP policies that are scoped only to Exchange. - -```yaml -Type: PswsHashtable -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StopPolicyProcessing -The StopPolicyProcessing parameter specifies an action that stops processing more DLP policy rules. Valid values are: - -- $true: Stop processing more rules. - -- $false: Continue processing more rules after this one. - -```yaml -Type: $true | $false -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubjectContainsWords -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" - -- Multiple words: no_reply,urgent,... - -- Multiple words and phrases: "phrase 1",word1,"phrase with , or spaces",word2,... - -The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubjectMatchesPatterns -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 10. - -You can use this condition in DLP policies that are scoped only to Exchange. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpEdmSchema.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpEdmSchema.md deleted file mode 100644 index 35ce2978d9..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpEdmSchema.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/Set-DlpEdmSchema -applicable: Office 365 Security & Compliance Center -title: Set-DlpEdmSchema -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DlpEdmSchema - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DlpEdmSchema cmdlet to modify exact data match (EDM) data loss prevention (DLP) schemas in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-DlpEdmSchema [-FileData] <Byte[]> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -For an explanation and example of the EDM schema, see [Define the schema for your database of sensitive information](https://docs.microsoft.com/microsoft-365/compliance/create-custom-sensitive-information-types-with-exact-data-match-based-classification#define-the-schema-for-your-database-of-sensitive-information). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$edmSchemaXml = Get-Content "C:\My Documents\edm.xml" -Encoding Byte -ReadCount 0; Set-DlpEdmSchema -FileData $edmSchemaXml -Confirm:$true -``` - -This example modifies a DLP EDM schema. The first command reads the schema in the XML file to a variable, and the second command uses that information to modify the DLP EDM schema. - -## PARAMETERS - -### -FileData -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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpKeywordDictionary.md deleted file mode 100644 index 781db939d5..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpKeywordDictionary.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlpkeyworddictionary -applicable: Office 365 Security & Compliance Center -title: Set-DlpKeywordDictionary -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DlpKeywordDictionary - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DlpKeywordDictionary cmdlet to modify data loss prevention (DLP) keyword dictionaries in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-DlpKeywordDictionary [-Identity] <SensitiveInformationTypeIdParameter> [-Confirm] [-Description <String>] - [-FileData <Byte[]>] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$Keywords = "Aarskog's syndrome, Abandonment, Abasia, Abderhalden-Kaufmann-Lignac, Abdominalgia, Abduction contracture, Abetalipo proteinemia, Abiotrophy, Ablatio, ablation, Ablepharia, Abocclusion, Abolition, Aborter, Abortion, Abortus, Aboulomania, Abrami's disease, Abramo"; $EncodedKeywords = [system.Text.Encoding]::UTF8.GetBytes($keywords); Set-DlpKeywordDictionary -Identity "Diseases" -FileData $EncodedKeywords -``` - -This example replaces the existing terms in the DLP keyword dictionary named Diseases with the specified values. - -### Example 2 -```powershell -$Dictionary = Get-DlpKeywordDictionary -Name "Diseases"; $Terms = $Dictionary.KeywordDictionary.split(',').trim(); $Terms += "Achylia","Acidemia","Acidocytopenia","Acidocytosis","Acidopenia","Acidosis","Aciduria","Acladiosis","Aclasis"; $Keywords = $Terms -Join ", "; $EncodedKeywords = [system.Text.Encoding]::UTF8.GetBytes($Keywords); Set-DlpKeywordDictionary -Identity "Diseases" -FileData $EncodedKeywords -``` - -This example adds the specified terms to the DLP keyword dictionary named Diseases without affecting other existing terms. - -### Example 3 -```powershell -$Dictionary = Get-DlpKeywordDictionary -Name "Diseases"; $Terms = $Dictionary.KeywordDictionary.split(',').trim(); $TermsToRemove = @('abandonment', 'ablatio'); $UpdatedTerms = $Terms | Where-Object {$_ -NotIn $TermsToRemove}; $Keywords = $UpdatedTerms -Join ", "; $EncodedKeywords = [system.Text.Encoding]::UTF8.GetBytes($Keywords); Set-DlpKeywordDictionary -Identity "Diseases" -FileData $EncodedKeywords -``` - -This example removes the specified terms from the DLP keyword dictionary named Diseases without affecting other existing terms. - -### Example 4 -```powershell -$Dictionary = Get-DlpKeywordDictionary -Name "Inappropriate Language"; $Terms = $Dictionary.KeywordDictionary.split(',').trim(); Set-Content $Terms -Path "C:\My Documents\InappropriateTerms.txt"; $UpdatedTerms = Get-Content -Path "C:\My Documents\InappropriateTerms.txt"; $Keywords = $UpdatedTerms -Join ", "; $EncodedKeywords = [system.Text.Encoding]::UTF8.GetBytes($Keywords); Set-DlpKeywordDictionary -Identity "Inappropriate Language" -FileData $EncodedKeywords -``` - -The first three commands export the terms from the existing keyword dictionary named Inappropriate Language to the file C:\\My Documents\\InappropriateTerms.txt, where each term is on a separate line. - -After you use Notepad to modify the terms and save the file, the last four commands use the file to replace the terms in the keyword dictionary. - -## PARAMETERS - -### -Identity -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileData -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 UTF8. For more information, see the examples in this topic. The maximum file size limit is 100 KB. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationType.md deleted file mode 100644 index 6741bcc6d5..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationType.md +++ /dev/null @@ -1,230 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlpsensitiveinformationtype -applicable: Office 365 Security & Compliance Center -title: Set-DlpSensitiveInformationType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DlpSensitiveInformationType - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-DlpSensitiveInformationType cmdlet to modify sensitive information type rules that use document fingerprints. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-DlpSensitiveInformationType [-Identity] <SensitiveInformationTypeIdParameter> [-Confirm] [-Description <String>] - [-DomainController <Fqdn>] [-Fingerprints <MultiValuedProperty>] [-IsDefault] [-Locale <CultureInfo>] - [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-DlpSensitiveInformationType "Contoso Confidential" -Locale fr -Name "Contoso Confidentiel" -Description "Ce message contient des informations confidentielles." -IsDefault -``` - -This example adds a French translation to the existing sensitive information type rule named "Contoso Confidential", and sets this French translation as the default. - -### Example 2 -```powershell -Set-DlpSensitiveInformationType "Contoso Confidential" -Locale es -Name $null -Description $null -``` - -This example removes the existing Spanish translation from the sensitive information type rule named "Contoso Confidential". - -### Example 3 -```powershell -$Benefits_Template = Get-Content "C:\My Documents\Contoso Benefits Template.docx" -Encoding byte -ReadCount 0; $Benefits_Fingerprint = New-DlpFingerprint -FileData $Benefits_Template -Description "Contoso Benefits Template"; $Contoso_Confidential = Get-DlpSensitiveInformationType "Contoso Confidential"; $Array = [System.Collections.ArrayList]($Contoso_Confidential.Fingerprints); $Array.Add($Benefits_FingerPrint[0]); Set-DlpSensitiveInformationType $Contoso_Confidential.Identity -FingerPrints $Array -``` - -This example modifies the existing sensitive information type rule named "Contoso Confidential" by adding a new document fingerprint for the file C:\\My Documents\\Contoso Benefits Template.docx without affecting any existing document fingerprints that are already defined. - -### Example 4 -```powershell -$cc = Get-DlpSensitiveInformationType "Contoso Confidential"; $a = [System.Collections.ArrayList]($cc.Fingerprints); $a; $a.RemoveAt(0); Set-DlpSensitiveInformationType $cc.Identity -FingerPrints $a -``` - -This example modifies the sensitive information type rule named "Contoso Confidential" by removing an existing document fingerprint without affecting other document fingerprints that are already defined. - -The first three commands return the list of document fingerprints in the sensitive information type. The first document fingerprint in the list has the index number 0, the second has the index number 1, and so on. You use the index number to specify the document fingerprint that you want to remove. The last two commands remove the first document fingerprint that's displayed in the list. - -## PARAMETERS - -### -Identity -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 - -- LocalizedName - -- Identity GUID value - -```yaml -Type: SensitiveInformationTypeIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Fingerprints -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://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefault -The IsDefault switch is used with the Locale parameter to specify the default language for the sensitive information type rule. The default Locale value is stored in the DefaultCulture property. - -When you change the default Locale value, the Name value of the sensitive information type rule changes to match the Name value that's associated with the new default locale. The original Name value when the rule was created is permanently stored the LocalizedName property. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Locale -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://go.microsoft.com/fwlink/p/?linkId=184859). - -Typically, you use the Locale parameter with the Name and Description parameters to add or remove translated names and descriptions for the sensitive information type rule. You can also use the Locale parameter with the IsDefault switch to designate an existing translated name and description as the default. Before you can remove the default translation, you need to set another translation as the default. - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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. - -The value of the Name parameter is used in the Policy Tip that's presented to users in Outlook on the web. When a translated value of the Name parameter matches the client's language, the Policy Tip is displayed in the client's language. If no translated values of the Name parameter match the client's language, the default translation that's specified by the IsDefault parameter is used for the Policy Tip. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationTypeRulePackage.md deleted file mode 100644 index ab454d4694..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationTypeRulePackage.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/set-dlpsensitiveinformationtyperulepackage -applicable: Office 365 Security & Compliance Center -title: Set-DlpSensitiveInformationTypeRulePackage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-DlpSensitiveInformationTypeRulePackage - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-DlpSensitiveInformationTypeRulePackage cmdlet to update existing data loss prevention (DLP) sensitive information type rule packages in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-DlpSensitiveInformationTypeRulePackage [-FileData] <Byte[]> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sensitive information type rule packages are used by DLP to detect sensitive content. The default sensitive information type rule package is named Microsoft Rule Package. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-DlpSensitiveInformationTypeRulePackage -FileData ([Byte[]]$(Get-Content -Path "C:\My Documents\External Sensitive Info Type Rule Collection.xml" -Encoding Byte -ReadCount 0)) -``` - -This example imports the sensitive information type rule package C:\\My Documents\\External Sensitive Info Type Rule Collection.xml. - -## PARAMETERS - -### -FileData -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 Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Add-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Add-ComplianceCaseMember.md deleted file mode 100644 index 6ccea1d8c7..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Add-ComplianceCaseMember.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/add-compliancecasemember -applicable: Office 365 Security & Compliance Center -title: Add-ComplianceCaseMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Add-ComplianceCaseMember - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Add-ComplianceCaseMember cmdlet to add an individual member to an eDiscovery case in the Security & Compliance Center. To replace all existing members, use the Update-ComplianceCaseMember cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Add-ComplianceCaseMember [-Case] <String> -Member <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You use eDiscovery cases to control who can create, access, and manage compliance searches in your organization. You use the New-ComplianceCase cmdlet to create eDiscovery cases. The eDiscovery Manager who created the case is automatically added as a member of the case. - -To add a member of an eDiscovery case, the user needs to be a member of the Reviewer or eDiscovery Manager role groups. When a member of the eDiscovery Manager role group is a member of an eDiscovery case, the user can: - -- Add and remove case members. - -- Create and edit compliance searches associated with a case. - -- Perform compliance actions (for example, export) on the results of a compliance search. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Add-ComplianceCaseMember -Case "Case 2112" -Member johnevans@contoso.com -``` - -This example adds John Evans to the eDiscovery case named Case 2112. - -## PARAMETERS - -### -Case -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Member -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Add-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Add-eDiscoveryCaseAdmin.md deleted file mode 100644 index 024919814c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Add-eDiscoveryCaseAdmin.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/add-ediscoverycaseadmin -applicable: Office 365 Security & Compliance Center -title: Add-eDiscoveryCaseAdmin -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Add-eDiscoveryCaseAdmin - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Add-eDiscoveryCaseAdmin cmdlet to add an eDiscovery Administrator in the Security & Compliance Center. To replace all existing eDiscovery Administrators, use the Update-eDiscoveryCaseAdmin cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Add-eDiscoveryCaseAdmin -User <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -An eDiscovery Administrator is member of the eDiscovery Manager role group who can also view and access all eDiscovery cases in your organization. - -To make a user an eDiscovery Administrator, the user must be assigned the Case Management role. By default, this role is assigned to the Organization Management and eDiscovery Manager role groups. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Add-eDiscoveryCaseAdmin -User michelle@contoso.com -``` - -This example adds an eDiscovery Administrator. - -## PARAMETERS - -### -User -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-CaseHoldPolicy.md deleted file mode 100644 index 17d2907886..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-CaseHoldPolicy.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/get-caseholdpolicy -applicable: Office 365 Security & Compliance Center -title: Get-CaseHoldPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-CaseHoldPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-CaseHoldPolicy to view existing case hold policies in the Security & Compliance Center. To get relevant information about how the hold was applied and the affected locations, you need to include the DistributionDetail switch. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CaseHoldPolicy [[-Identity] <PolicyIdParameter>] [-Case <String>] [-DistributionDetail] [-IncludeBindings] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-CaseHoldPolicy -Case "Contoso Legal" -``` - -This example displays detailed information for the policy that's associated with the eDiscovery case named Contoso Legal. - -### Example 2 -```powershell -Get-CaseHoldPolicy -Identity "Regulation 123 Compliance" -``` - -This example displays detailed information for the policy named "Regulation 123 Compliance". - -## PARAMETERS - -### -Case -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 - -- Identity (GUID value). - -You can find these values by running the command: Get-ComplianceCase | Format-Table -Auto Name,Status,Identity. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionDetail -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". - -The following properties are affected by this switch: - -- SharePointLocation -- ExchangeLocation -- PublicFolderLocation -- DistributionStatus -- DistributionResults -- LastStatusUpdateTime - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IncludeBindings -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-CaseHoldRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-CaseHoldRule.md deleted file mode 100644 index cc4a47fe39..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-CaseHoldRule.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/get-caseholdrule -applicable: Office 365 Security & Compliance Center -title: Get-CaseHoldRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-CaseHoldRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-CaseHoldRule to view case hold rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CaseHoldRule [[-Identity] <ComplianceRuleIdParameter>] [-Policy <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-CaseHoldRule -Identity "30 Day Rule" -``` - -This example displays detailed information for the case hold rule named "30 Day Rule". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Policy -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 - -- Distinguished name (DN) - -- GUID - -You can use this parameter with the Identity parameter in the same command. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-ComplianceCase.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-ComplianceCase.md deleted file mode 100644 index a9cdb84642..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-ComplianceCase.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/get-compliancecase -applicable: Office 365 Security & Compliance Center -title: Get-ComplianceCase -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-ComplianceCase - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ComplianceCase cmdlet to different types of compliance cases in the Security & Compliance Center and Microsoft 365 compliance center. See the CaseType parameter for a list of these case types. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceCase [-Identity] <ComplianceCaseIdParameter>] - [-CaseType <ComplianceCaseType>] - [-DomainController <Fqdn>] - [-RecentOnly] - [-RoleGroup <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceCase -``` - -This example returns a summary list of all core eDiscovery cases in the organization. - -### Example 2 -```powershell -Get-ComplianceCase -Identity "Contoso Legal" | Format-List -``` - -This example returns detailed information for the core eDiscovery case named Contoso Legal. - - -### Example 3 -```powershell -Get-ComplianceCase -CaseType AdvancedEdiscovery -``` - -This example returns a summary list of all Advanced eDiscovery cases in the organization. - -### Example 4 -```powershell -Get-ComplianceCase -CaseType DSR -RoleGroup "DSR Administrators" -``` - -This example returns a summary list of all DSR cases that the custom role group "DSR Administrators" is a member of. - -## PARAMETERS - -### -CaseType -The CaseType parameter specifies the type of compliance case that you want to view. Valid values are: - -- AdvancedEdiscovery: Advanced eDiscovery cases are used to manage legal or other types of investigations. In the Security & Compliance Center, Advanced eDiscovery cases are displayed under eDiscovery > Advanced eDiscovery. - -- ComplianceClassifier: This type of case corresponds to a trainable classifier. In the Microsoft 365 compliance center, trainable classifiers are displayed under Data classification > Trainable classifiers. - -- ComplianceWorkspace: This value is reserved for internal Microsoft use. - -- DataInvestigation: Data investigation cases are used to investigate data spillage incidents. In the Security & Compliance Center, Data investigation cases are displayed on the Data investigations page. - -- DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. In the Security & Compliance Center, DSR cases are displayed under Data privacy > Data subject requests. - -- eDiscovery: eDiscovery (also called core eDiscovery) cases are used to manage legal or other types of investigations. In the Security & Compliance Center, core eDiscovery cases are displayed under eDiscovery > eDiscovery. This is the default value. - -- InsiderRisk: Insider risk cases are use to manage insider risk management cases. In the Microsoft 365 compliance center, insider risk cases are displayed under Insider risk management > Cases. Typically, insider risk management cases are manually created in the compliance center to further investigate activity based on an risk alert. - -- InternalInvestigation: This value is reserved for internal Microsoft use. - -- SupervisionPolicy: This type of case corresponds to communication compliance policy. In the Microsoft 365 compliance center, communication compliance policies are displayed under Communication compliance > Policies. - -```yaml -Type: ComplianceCaseType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: eDiscovery -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Identity (GUID value) - -```yaml -Type: ComplianceCaseIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RecentOnly -The RecentOnly switch returns a list of the most recently modified cases of the specified case type. This switch is used to display data in the "Recently cases" widget that's displayed in the compliance centers for some of the features that use compliance case objects. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoleGroup -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 core eDiscovery cases that the role group is a member of. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-ComplianceCaseMember.md deleted file mode 100644 index 53d3c99356..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-ComplianceCaseMember.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/get-compliancecasemember -applicable: Office 365 Security & Compliance Center -title: Get-ComplianceCaseMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-ComplianceCaseMember - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ComplianceCaseMember cmdlet to view the members of eDiscovery cases in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceCaseMember -Case <String> [-DomainController <Fqdn>] [-ResultSize <Unlimited>] [-ShowCaseAdmin] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceCaseMember -Case "Fabrikam Litigation" -``` - -This examples shows the members of the eDiscovery case named Fabrikam Litigation. - -## PARAMETERS - -### -Case -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: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowCaseAdmin -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: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-eDiscoveryCaseAdmin.md deleted file mode 100644 index 4c043f4891..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Get-eDiscoveryCaseAdmin.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/get-ediscoverycaseadmin -applicable: Office 365 Security & Compliance Center -title: Get-eDiscoveryCaseAdmin -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-eDiscoveryCaseAdmin - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-eDiscoveryCaseAdmin cmdlet to view eDiscovery Administrators in the Security & Compliance Center. An eDiscovery Administrator is member of the eDiscovery Manager role group who can also view and access all eDiscovery cases in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-eDiscoveryCaseAdmin [-DomainController <Fqdn>] [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -To add or remove individual eDiscovery Administrators, use the Add-eDiscoveryCaseAdmin and Remove-eDiscoveryCaseAdmin cmdlets. To replace all existing eDiscovery Administrators, use the Update-eDiscoveryCaseAdmin cmdlet. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-eDiscoveryCaseAdmin -``` - -This example returns a summary list of all eDiscovery Administrators. - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-CaseHoldPolicy.md deleted file mode 100644 index 540bb6fe1e..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-CaseHoldPolicy.md +++ /dev/null @@ -1,257 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/new-caseholdpolicy -applicable: Office 365 Security & Compliance Center -title: New-CaseHoldPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-CaseHoldPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-CaseHoldPolicy cmdlet to create new case hold policies in the Security & Compliance Center. - -After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. If you don't create a rule for the policy, the hold won't be created, and content locations won't be placed on hold. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-CaseHoldPolicy [-Name] <String> -Case <String> [-Comment <String>] [-Confirm] [-Enabled <Boolean>] - [-ExchangeLocation <MultiValuedProperty>] [-Force] [-PublicFolderLocation <MultiValuedProperty>] - [-SharePointLocation <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-CaseHoldPolicy -Name "Regulation 123 Compliance" -Case "123 Compliance Case" -ExchangeLocation "Kitty Petersen", "Scott Nakamura" -SharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -``` - -This example creates a case hold policy named "Regulation 123 Compliance" for the mailboxes of Kitty Petersen and Scott Nakamura, and the finance SharePoint Online site for the eDiscovery case named "123 Compliance Case". - -Remember, after you create the policy, you need to create a rule for the policy by using the New-CaseHoldRule cmdlet. - -## PARAMETERS - -### -Case -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 - -- Identity (GUID value). - -You can find these values by running the command: Get-ComplianceCase | Format-Table -Auto Name,Status,Identity. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocation -The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If no mailboxes are specified, then no mailboxes are placed on hold. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocation -The SharePointLocation parameter specifies the SharePoint Online and OneDrive for Business sites to include. You identify a site by its URL value. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -Sites can't be added to the policy until they have been indexed. If no sites are specified, then no sites are placed on hold. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-CaseHoldRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-CaseHoldRule.md deleted file mode 100644 index fb693e6ca4..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-CaseHoldRule.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/new-caseholdrule -applicable: Office 365 Security & Compliance Center -title: New-CaseHoldRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-CaseHoldRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-CaseHoldRule cmdlet to create new case hold rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-CaseHoldRule [-Name] <String> -Policy <PolicyIdParameter> [-Comment <String>] [-Confirm] [-ContentMatchQuery <String>] [-Disabled <Boolean>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to add the case hold rule to an existing case hold policy using the Policy parameter. Only one rule can be added to each case hold policy. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-CaseHoldRule -Name "2016 Budget Spreadsheets" -Policy "Internal Company Policy" -ContentMatchQuery "filename:2016 budget filetype:xlsx" -``` - -This example creates a new case hold rule named 2016 Budget Spreadsheets and adds it to the existing case hold policy named "Internal Company Policy". The rule applies to Excel worksheets that contain the phrase 2016 budget, such as "2016 budget planning.xlsx" and "2016 budget review.xlsx" - -### Example 2 -```powershell -New-CaseHoldRule -Name "Contoso Case 07172018 Hold 1" -Policy "Contoso Case 07172018" -ContentMatchQuery "received:12/01/2016..12/31/2018" -``` - -This example places email messages received by the recipients between December 1, 2016 and December 31, 2018 on hold. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policy -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: - -- $true: The rule is disabled. - -- $false: The rule is enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-ComplianceCase.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-ComplianceCase.md deleted file mode 100644 index 67a2d4aa4c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-ComplianceCase.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/new-compliancecase -applicable: Office 365 Security & Compliance Center -title: New-ComplianceCase -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-ComplianceCase - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-ComplianceCase cmdlet to create eDiscovery cases in the Security & Compliance Center. You use eDiscovery cases to place content locations on hold, perform Content Searches associated with the case, and export search results. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ComplianceCase [-Name] <String> - [-CaseType <ComplianceCaseType>] - [-Confirm] - [-Description <String>] - [-DomainController <Fqdn>] - [-ExternalId <String>] - [-SecondaryCaseType <String>] - [-SourceCaseType <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ComplianceCase -Name "Fabrikam Litigation" -``` - -This example creates a new core eDiscovery case named Fabrikam Litigation. - -### Example 2 -```powershell -New-ComplianceCase -Name "Coho Case 03082020" -CaseType AdvancedEdiscovery -ExternalId "SaraDavis v. Coho Winery" -``` - -This example creates a new Advanced eDiscovery case named Coho Case 03082020 and specifies an optional case Id of "SaraDavis v. Coho Winery". - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CaseType -The CaseType parameter specifies the type of compliance case that you want to create. Valid values are: - -- AdvancedEdiscovery: Advanced eDiscovery cases are used to manage legal or other types of investigations. In the Security & Compliance Center, Advanced eDiscovery cases are displayed under eDiscovery > Advanced eDiscovery. - -- ComplianceClassifier: This type of case corresponds to a trainable classifier. In the Microsoft 365 compliance center, trainable classifiers are displayed under Data classification > Trainable classifiers. - -- ComplianceWorkspace: This value is reserved for internal Microsoft use. - -- DataInvestigation: Data investigation cases are used to investigate data spillage incidents. In the Security & Compliance Center, Data investigation cases are displayed on the Data investigations page. - -- DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. In the Security & Compliance Center, DSR cases are displayed under Data privacy > Data subject requests. - -- eDiscovery: eDiscovery (also called core eDiscovery) cases are used to manage legal or other types of investigations. In the Security & Compliance Center, core eDiscovery cases are displayed under eDiscovery > eDiscovery. This is the default value. - -- InsiderRisk: Insider risk cases are use to manage insider risk management cases. In the Microsoft 365 compliance center, insider risk cases are displayed under Insider risk management > Cases. Typically, insider risk management cases are manually created in the compliance center to further investigate activity based on an risk alert. - -- InternalInvestigation: This value is reserved for internal Microsoft use. - -- SupervisionPolicy: This type of case corresponds to communication compliance policy. In the Microsoft 365 compliance center, communication compliance policies are displayed under Communication compliance > Policies. - -```yaml -Type: ComplianceCaseType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalId -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryCaseType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceCaseType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldPolicy.md deleted file mode 100644 index 629e78475b..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldPolicy.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/remove-caseholdpolicy -applicable: Office 365 Security & Compliance Center -title: Remove-CaseHoldPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-CaseHoldPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-CaseHoldPolicy cmdlet to remove case hold policies from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-CaseHoldPolicy [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You should also remove the case hold rule that corresponds to the removed policy by using the Remove-CaseHoldRule cmdlet. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-CaseHoldPolicy -Identity "Regulation 123 Compliance" -``` - -This example removes the case hold policy named "Regulation 123 Compliance". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the case hold policy to remove. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldRule.md deleted file mode 100644 index 3d98ddc803..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldRule.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/remove-caseholdrule -applicable: Office 365 Security & Compliance Center -title: Remove-CaseHoldRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-CaseHoldRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-CaseHoldRule cmdlet to remove case hold rules from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-CaseHoldRule [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Removing a case hold rule causes the release of all Exchange mailbox and SharePoint site case holds that are associated with the rule. Removing a case hold rule also causes the corresponding case hold policy to become invalid, so you should remove it by using the Remove-CaseHoldPolicy cmdlet. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-CaseHoldRule -Identity "One Year Standard" -``` - -This example removes the case hold rule named "One Year Standard". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the case hold rule to remove. You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCase.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCase.md deleted file mode 100644 index e3081f989d..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCase.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/remove-compliancecase -applicable: Office 365 Security & Compliance Center -title: Remove-ComplianceCase -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ComplianceCase - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ComplianceCase cmdlet to remove compliance cases from the Security & Compliance Center or the Microsoft 365 compliance center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ComplianceCase [-Identity] <ComplianceCaseIdParameter> [-Confirm] [-DomainController <Fqdn>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ComplianceCase -Identity "Case 5150" -``` - -This example removes the compliance case named Case 5150 - -## PARAMETERS - -### -Identity -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 - -- Identity (GUID value) - -```yaml -Type: ComplianceCaseIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCaseMember.md deleted file mode 100644 index ddb3c59429..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCaseMember.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/remove-compliancecasemember -applicable: Office 365 Security & Compliance Center -title: Remove-ComplianceCaseMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ComplianceCaseMember - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ComplianceCaseMember cmdlet to remove a single member from an eDiscovery search in Security & Compliance Center. To replace all existing members, use the Update-ComplianceCaseMember cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ComplianceCaseMember [-Case] <String> -Member <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ComplianceCaseMember -Case "Case OU812" -Member "Jan Dryml" -``` - -This example removes Jan Dryml from the eDiscovery case named Case OU812. - -## PARAMETERS - -### -Case -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Member -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-eDiscoveryCaseAdmin.md deleted file mode 100644 index dece7c3003..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Remove-eDiscoveryCaseAdmin.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/remove-ediscoverycaseadmin -applicable: Office 365 Security & Compliance Center -title: Remove-eDiscoveryCaseAdmin -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-eDiscoveryCaseAdmin - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-eDiscoveryCaseAdmin cmdlet to remove an eDiscovery Administrator from the Security & Compliance Center. To replace all eDiscovery Administrators, use the Update-eDiscoveryCaseAdmin cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-eDiscoveryCaseAdmin -User <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -An eDiscovery Administrator is member of the eDiscovery Manager role group who can also view and access all eDiscovery cases in your organization. - -When you remove an eDiscovery Administrator, the user isn't removed from the eDiscovery Manager role group. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-eDiscoveryCaseAdmin -User chris@contoso.com -``` - -This example removes an eDiscovery Administrator. - -## PARAMETERS - -### -User -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-CaseHoldPolicy.md deleted file mode 100644 index f68160235b..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-CaseHoldPolicy.md +++ /dev/null @@ -1,359 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/set-caseholdpolicy -applicable: Office 365 Security & Compliance Center -title: Set-CaseHoldPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-CaseHoldPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-CaseHoldPolicy cmdlet to modify existing case hold policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### RetryDistribution -``` -Set-CaseHoldPolicy [-Identity] <PolicyIdParameter> [-RetryDistribution] - [-Confirm] - [-UpdateStatistics] - [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Set-CaseHoldPolicy [-Identity] <PolicyIdParameter> - [-AddExchangeLocation <MultiValuedProperty>] - [-AddPublicFolderLocation <MultiValuedProperty>] - [-AddSharePointLocation <MultiValuedProperty>] - [-Comment <String>] - [-Confirm] - [-Enabled <Boolean>] [-Force] - [-RemoveExchangeLocation <MultiValuedProperty>] - [-RemovePublicFolderLocation <MultiValuedProperty>] - [-RemoveSharePointLocation <MultiValuedProperty>] - [-UpdateStatistics] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-CaseHoldPolicy -Identity "Regulation 123 Compliance" -AddExchangeLocation "Kitty Petersen" -AddSharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -RemovePublicFolderLocation All -Comment "Added new counsel, 9/9/14" -``` - -This example makes the following changes to the existing case hold policy named "Regulation 123 Compliance": - -- Adds the mailbox for the user named Kitty Petersen. - -- Adds the SharePoint Online site https://contoso.sharepoint.com/sites/teams/finance. - -- Removes public folders. - -- Updates the comment. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RetryDistribution -The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint Online locations. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocation -The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddPublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocation -The AddSharePointLocation parameter specifies the SharePoint Online 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. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -SharePoint Online sites can't be added to the policy until they have been indexed. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocation -The RemoveExchangeLocation parameter specifies the existing mailboxes to remove from the policy. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemovePublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocation -The RemoveSharePointLocation parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UpdateStatistics -The UpdateStatistics switch specifies whether you want to update the search results for the hold. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-CaseHoldRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-CaseHoldRule.md deleted file mode 100644 index 39fbee4f3d..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Set-CaseHoldRule.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/set-caseholdrule -applicable: Office 365 Security & Compliance Center -title: Set-CaseHoldRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-CaseHoldRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-CaseHoldRule cmdlet to modify existing case hold rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-CaseHoldRule [-Identity] <ComplianceRuleIdParameter> [-Comment <String>] [-Confirm] - [-ContentDateFrom <DateTime>] [-ContentDateTo <DateTime>] [-ContentMatchQuery <String>] - [-Disabled <Boolean>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-CaseHoldRule -Identity "Internal Company Rule" -Disabled $true -``` - -This example disables the enabled case hold rule named "Internal Company Rule". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateFrom -The ContentDateFrom 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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateTo -The ContentDateTo 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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: - -- $true: The rule is disabled. - -- $false: The rule is enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Update-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Update-ComplianceCaseMember.md deleted file mode 100644 index f7627d1c79..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Update-ComplianceCaseMember.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/update-compliancecasemember -applicable: Office 365 Security & Compliance Center -title: Update-ComplianceCaseMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Update-ComplianceCaseMember - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Update-ComplianceCaseMember cmdlet to replace all members of eDiscovery cases in the Security & Compliance Center. To add or remove existing members, use the Add-ComplianceCaseMember and Remove-ComplianceCaseMember cmdlets. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Update-ComplianceCaseMember [-Case] <String> -Members <String[]> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You use eDiscovery cases to control who can create, access, and manage compliance searches in your organization. You use the New-ComplianceCase cmdlet to create eDiscovery cases. The eDiscovery Manager who created the case is automatically added as a member of the case. - -To add a member of an eDiscovery case, the user needs to be a member of the Reviewer or eDiscovery Manager role groups. When a member of the eDiscovery Manager role group is a member of an eDiscovery case, the user can: - -- Add and remove case members. - -- Create and edit compliance searches associated with a case. - -- Perform compliance actions (for example, export) on the results of a compliance search. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Update-ComplianceCaseMember -Case "Case 5150" -Members chris@contoso.com,michelle@contoso.com,laura@contoso.com,julia@contoso.com -``` - -This example replaces the existing members of the eDiscovery case named Case 5150 with new members. - -## PARAMETERS - -### -Case -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Members -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Update-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Update-eDiscoveryCaseAdmin.md deleted file mode 100644 index 37f06b7496..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/Update-eDiscoveryCaseAdmin.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-ediscovery/update-ediscoverycaseadmin -applicable: Office 365 Security & Compliance Center -title: Update-eDiscoveryCaseAdmin -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Update-eDiscoveryCaseAdmin - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Update-eDiscoveryCaseAdmin cmdlet to replace all existing eDiscovery Administrators in the Security & Compliance Center. To add or remove individual eDiscovery Administrators, use the Add-eDiscoveryCaseAdmin and Remove-eDiscoveryCaseAdmin cmdlets. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Update-eDiscoveryCaseAdmin -Users <String[]> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -An eDiscovery Administrator is member of the eDiscovery Manager role group who can also view and access all eDiscovery cases in your organization. - -To make a user an eDiscovery Administrator, the user must be assigned the Case Management role. By default, this role is assigned to the Organization Management and eDiscovery Manager role groups. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Update-eDiscoveryCaseAdmin -Users laura@contoso.com,julia@contoso.com -``` - -This example replaces the existing eDiscovery Administrators with new users. - -## PARAMETERS - -### -Users -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 - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Enable-ComplianceTagStorage.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Enable-ComplianceTagStorage.md deleted file mode 100644 index 041266f024..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Enable-ComplianceTagStorage.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/enable-compliancetagstorage -applicable: Office 365 Security & Compliance Center -title: Enable-ComplianceTagStorage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Enable-ComplianceTagStorage - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Enable-ComplianceTagStorage cmdlet to create the label policy in the Security & Compliance Center. This is a one-time operation. Labels apply retention settings to content. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Enable-ComplianceTagStorage [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -If you run this cmdlet more than once, you'll get an error that says a policy already exists. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Enable-ComplianceTagStorage -``` - -This example creates the label policy in the Security & Compliance Center. - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEvent.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEvent.md deleted file mode 100644 index 16e1d8fd13..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEvent.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEvent -applicable: Office 365 Security & Compliance Center -title: Get-ComplianceRetentionEvent -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-ComplianceRetentionEvent - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ComplianceRetentionEvent cmdlet to view compliance retention events in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceRetentionEvent [-Identity <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceRetentionEvent | Format-Table Name,Description -``` - -The example returns a summary list of all compliance retention events. - -### Example 2 -```powershell -Get-ComplianceRetentionEvent -Identity "Case 1234" -``` - -This example returns detailed information about the compliance retention event named Case 1234. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEventType.md deleted file mode 100644 index 3f98817c07..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEventType.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEventType -applicable: Office 365 Security & Compliance Center -title: Get-ComplianceRetentionEventType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-ComplianceRetentionEventType - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ComplianceRetentionEventType cmdlet to view retention event types in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceRetentionEventType [-Identity <ComplianceRuleIdParameter>] [-LoadTag] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceRetentionEventType | Format-Table Name,Priority -``` - -This example returns a summary list of all retention event types - -### Example 2 -```powershell -Get-ComplianceRetentionEventType -Identity "Fabrikam Project" -LoadTag -``` - -This example returns detailed information for the retention event type named Fabrikam Project, including the associated compliance tags. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -LoadTag -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceTag.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceTag.md deleted file mode 100644 index 02eb3dba34..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceTag.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-compliancetag -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-ComplianceTag -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-ComplianceTag - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ComplianceTag cmdlet to view labels in the Security & Compliance Center. Labels apply retention settings to content. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceTag [[-Identity] <ComplianceRuleIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceTag | Format-Table -Auto Name,Priority,RetentionAction,RetentionDuration,Workload -``` - -This example returns a summary list of all labels. - -### Example 2 -```powershell -Get-ComplianceTag -Identity "HR Content" -``` - -This example returns detailed information about the label named HR Content. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the label that you want to view. You can use any value that uniquely identifies the tag. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceTagStorage.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceTagStorage.md deleted file mode 100644 index 9ae6ec40fc..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ComplianceTagStorage.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-compliancetagstorage -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-ComplianceTagStorage -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-ComplianceTagStorage - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ComplianceTagStorage cmdlet to confirm that you've created the label policy by using the Enable-ComplianceTagStorage cmdlet. Labels apply retention settings to content. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ComplianceTagStorage [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ComplianceTagStorage -``` - -This example confirms that you've created the label policy in your organization. - -## PARAMETERS - -### -Identity -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) - -- Distinguished name (DN) - -- GUID (a different value than Name) - -However, there can be only one label policy in your organization. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-DataRetentionReport.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-DataRetentionReport.md deleted file mode 100644 index da6c61565b..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-DataRetentionReport.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-dataretentionreport -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-DataRetentionReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-DataRetentionReport - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-DataRetentionReport cmdlet to view information about data retention in the Security & Compliance Center. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DataRetentionReport - [-EndDate <DateTime>] - [-Page <Int32>] - [-PageSize <Int32>] - [-StartDate <DateTime>] - [<CommonParameters>] -``` - -## DESCRIPTION -The following properties are returned by this cmdlet: - -- Organization - -- Date - -- Action - -- DataSource - -- MessageCount - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-DataRetentionReport -StartDate 04/01/2018 -EndDate 04/30/2018 -``` - -This example lists the data detections for April, 2018. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-HoldCompliancePolicy.md deleted file mode 100644 index 6fc600b9a8..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-HoldCompliancePolicy.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-holdcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Get-HoldCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-HoldCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-HoldCompliancePolicy to view existing preservation policies in the Security & Compliance Center. - -Note: The Get-HoldCompliancePolicy cmdlet has been replaced by the Get-RetentionCompliancePolicy cmdlet. If you have scripts that use Get-HoldCompliancePolicy, update them to use Get-RetentionCompliancePolicy. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-HoldCompliancePolicy [[-Identity] <PolicyIdParameter>] [-DistributionDetail] [<CommonParameters>] -``` - -## DESCRIPTION -This list describes the properties displayed by default. - -- Name: The unique name of the policy. - -- Workload: Where the policy is applied. For example, SharePoint or Exchange. - -- Enabled: The value True means the policy is enabled. - -- Mode: The current operating mode of the policy. The possible values are Test (the content is tested, but no rules are enforced), AuditAndNotify (when content matches the conditions specified by the policy, the rule is not enforced, but notification emails are sent) or Enforce (all aspects of the policy are enabled and enforced). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-HoldCompliancePolicy -``` - -This example displays summary information for all preservation policies in your organization. - -### Example 2 -```powershell -Get-HoldCompliancePolicy -Identity "Regulation 123 Compliance" | Format-List -``` - -This example displays detailed information for the policy named "Regulation 123 Compliance". - -## PARAMETERS - -### -DistributionDetail -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-HoldComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-HoldComplianceRule.md deleted file mode 100644 index 00af7c0316..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-HoldComplianceRule.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-holdcompliancerule -applicable: Office 365 Security & Compliance Center -title: Get-HoldComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-HoldComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-HoldComplianceRule to view preservation rules in the Security & Compliance Center. - -Note: The Get-HoldComplianceRule cmdlet has been replaced by the Get-RetentionComplianceRule cmdlet. If you have scripts that use Get-HoldComplianceRule, update them to use Get-RetentionComplianceRule. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-HoldComplianceRule [[-Identity] <ComplianceRuleIdParameter>] [-Policy <PolicyIdParameter>] - [<CommonParameters>] -``` - -## DESCRIPTION -This list describes the properties that are displayed by default in the summary information. - -- Name: The unique name of the rule. - -- Disabled: The enabled or disabled status of the rule. - -- Mode: The current operating mode of the rule (for example, Enforce). - -- Comment: An administrative comment. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-HoldComplianceRule -``` - -This example displays summary information for all preservation rules in your organization. - -### Example 2 -```powershell -Get-HoldComplianceRule -Identity "30DayRule" | Format-List -``` - -This example displays detailed information for the preservation rule named "30 Day Rule". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the preservation rule you want to view. You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Policy -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 - -- Distinguished name (DN) - -- GUID - -You can use this parameter with the Identity parameter in the same command. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedFolderMailboxPolicy.md deleted file mode 100644 index 518589e0ee..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-ManagedFolderMailboxPolicy.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-managedfoldermailboxpolicy -applicable: Exchange Server 2010 -title: Get-ManagedFolderMailboxPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010" ---- - -# Get-ManagedFolderMailboxPolicy - -## SYNOPSIS -This cmdlet is available only in Exchange Server 2010. - -Use the Get-ManagedFolderMailboxPolicy cmdlet to return all attributes of one or more managed folder mailbox policies. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ManagedFolderMailboxPolicy [[-Identity] <MailboxPolicyIdParameter>] [-DomainController <Fqdn>] - [-Organization <OrganizationIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -A managed folder mailbox policy is a logical grouping of one or more managed folders. Policies are applied to mailboxes. The Get-ManagedFolderMailboxPolicy cmdlet lists one or more managed folder mailbox policies created in the Microsoft Exchange Server 2010 organization. All policies can be listed. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ManagedFolderMailboxPolicy "PM Storage Template" -``` - -This example returns all the attributes of the managed folder mailbox policy PM Storage Template. - -The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). - -## PARAMETERS - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Organization -This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see [Multi-Tenant Support](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/ff923272(v=exchg.141)). - -The Organization parameter specifies the organization in which you'll perform this action. This parameter doesn't accept wildcard characters, and you must use the exact name of the organization. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-retention/Get-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionCompliancePolicy.md deleted file mode 100644 index de86ab2062..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionCompliancePolicy.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-retentioncompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Get-RetentionCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-RetentionCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-RetentionCompliancePolicy to view existing retention policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-RetentionCompliancePolicy [[-Identity] <PolicyIdParameter>] [-DistributionDetail] [-ExcludeTeamsPolicy] [-RetentionRuleTypes] [-TeamsPolicyOnly] - [<CommonParameters>] -``` - -## DESCRIPTION -This list describes the properties that are displayed by default. - -- Name: The unique name of the policy. - -- Workload: Where the policy is applied. For example, SharePoint or Exchange. - -- Enabled: The value True means the policy is enabled. - -- Mode: The current operating mode of the policy. The possible values are Test (the content is tested, but no rules are enforced), AuditAndNotify (when content matches the conditions specified by the policy, the rule is not enforced, but notification emails are sent) or Enforce (all aspects of the policy are enabled and enforced). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-RetentionCompliancePolicy -``` - -This example displays summary information for all retention policies in your organization. - -### Example 2 -```powershell -Get-RetentionCompliancePolicy -Identity "Regulation 123 Compliance" -DistributionDetail | Format-List -``` - -This example displays detailed information for the policy named "Regulation 123 Compliance", including accurate values for the DistributionStatus and \*Location properties. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DistributionDetail -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludeTeamsPolicy -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionRuleTypes -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-RetentionCompliancePolicy -RetentionRuleTypes | Format-Table -Auto Name,RetentionRuleTypes. If you don't use the RetentionRuleTypes switch, the value appears blank. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamsPolicyOnly -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionComplianceRule.md deleted file mode 100644 index 846a9f0431..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionComplianceRule.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-retentioncompliancerule -applicable: Office 365 Security & Compliance Center -title: Get-RetentionComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-RetentionComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-RetentionComplianceRule to view retention rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-RetentionComplianceRule [[-Identity] <ComplianceRuleIdParameter>] [-Policy <PolicyIdParameter>] - [<CommonParameters>] -``` - -## DESCRIPTION -This list describes the properties that are displayed by default in the summary information. - -- Name: The unique name of the rule. - -- Disabled: The enabled or disabled status of the rule. - -- Mode: The current operating mode of the rule (for example, Enforce). - -- Comment: An administrative comment. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-RetentionComplianceRule -``` - -This example displays summary information for all retention rules in your organization. - -### Example 2 -```powershell -Get-RetentionComplianceRule -Identity "30 Day Rule" | Format-List -``` - -This example displays detailed information for the retention rule named "30 Day Rule". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the retention rule you want to view. You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Policy -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 - -- Distinguished name (DN) - -- GUID - -You can use this parameter with the Identity parameter in the same command. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionEvent.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionEvent.md deleted file mode 100644 index 9e03cbf31f..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-RetentionEvent.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/get-retentionevent -applicable: Exchange Online -title: Get-RetentionEvent -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-RetentionEvent - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-RetentionEvent cmdlet to view retention events in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-RetentionEvent [[-Identity] <EwsStoreObjectIdParameter>] [-AllStatus] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-RetentionEvent -``` - -This example returns a summary list of all retention events. - -### Example 2 -```powershell -Get-RetentionEvent -Identity x | Format-List -``` - -This example returns detailed information about retention the specified retention event. - -## PARAMETERS - -### -AllStatus -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the retention event that you want to view. - -```yaml -Type: EwsStoreObjectIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceRetentionEvent.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceRetentionEvent.md deleted file mode 100644 index ab44242af4..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceRetentionEvent.md +++ /dev/null @@ -1,244 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/New-ComplianceRetentionEvent -applicable: Office 365 Security & Compliance Center -title: New-ComplianceRetentionEvent -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-ComplianceRetentionEvent - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-ComplianceRetentionEvent cmdlet to create compliance retention events in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ComplianceRetentionEvent -Name <String> - [-AssetId <String>] - [-Comment <String>] - [-Confirm] - [-EventDateTime <DateTime>] - [-EventTags <MultiValuedProperty>] - [-EventType <ComplianceRuleIdParameter>] - [-ExchangeAssetIdQuery <String>] - [-SharePointAssetIdQuery <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ComplianceRetentionEvent -Name "Research Project Employees" -EventTag 80e0d620-13ea-4ed9-b6a6-aa883278bcca -EventType e823b782-9a07-4e30-8091-034fc01f9347 -SharePointAssetIDQuery "EmployeeNumber:123456 EmployeeNumber:456789" -``` - -This example creates a compliance retention event named Research Project Employees with the following settings: - -- EventTag: 80e0d620-13ea-4ed9-b6a6-aa883278bcca - -- EventTpe: e823b782-9a07-4e30-8091-034fc01f9347 - -- SharePointAssetIDQuery: EmployeeNumber:123456 EmployeeNumber:456789 - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssetId -The AssetId parameter specifies the Property:Value pair found in the properties of SharePoint or OneDrive for Business documents that's used for retention. For example: - -- Product codes that you can use to retain content for only a specific product. - -- Project codes that you can use to retain content for only a specific project. - -- Employee IDs that you can use to retain content for only a specific person. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventDateTime -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventTags -The EventTags parameter specifies the GUID value of the labels tha 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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeAssetIdQuery -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://go.microsoft.com/fwlink/p/?linkid=828045). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointAssetIdQuery -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 for Business documents to scope the compliance retention event. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceRetentionEventType.md deleted file mode 100644 index 8bfda8af1c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceRetentionEventType.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/New-ComplianceRetentionEventType -applicable: Office 365 Security & Compliance Center -title: New-ComplianceRetentionEventType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-ComplianceRetentionEventType - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-ComplianceRetentionEventType cmdlet to create retention event types in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ComplianceRetentionEventType -Name <String> [-Comment <String>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ComplianceRetentionEventType -Name "Fabrikam Project" -``` - -This example creates a new retention event type name Fabrikam Project - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceTag.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceTag.md deleted file mode 100644 index ddbe2aa796..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ComplianceTag.md +++ /dev/null @@ -1,364 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-compliancetag -applicable: Office 365 Security & Compliance Center -title: New-ComplianceTag -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-ComplianceTag - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-ComplianceTag cmdlet to create labels in the Security & Compliance Center. Labels apply retention settings to content. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ComplianceTag [-Name] <String> - [-Comment <String>] - [-Confirm] - [-EventType <ComplianceRuleIdParameter>] - [-FilePlanProperty <String>] - [-Force] - [-IsRecordLabel <Boolean>] - [-Notes <String>] - [-Regulatory <Boolean>] - [-RetentionAction <String>] - [-RetentionDuration <Unlimited>] - [-RetentionType <String>] - [-ReviewerEmail <SmtpAddress[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ComplianceTag -Name "HR Content" -RetentionAction Keep -RetentionDuration 1825 -RetentionType ModificationAgeInDays -``` - -This example creates a new label named HR Content with the following settings: - -- Action: Keep. - -- Duration: 5 years (1825 days) - -- Type: Modification age in days. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -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 - -- Distinguished name (DN) - -- GUID - -You can use the Get-RetentionComplianceRule cmdlet to view the available retention rules. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilePlanProperty -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 - -- Get-FilePlanPropertyCategory | Format-List Name - -- Get-FilePlanPropertyCitation | Format-List Name - -- Get-FilePlanPropertyDepartment | Format-List Name - -- Get-FilePlanPropertyReferenceId | Format-List Name - -- Get-FilePlanPropertySubCategory | Format-List Name - -A valid value for this parameter involves two steps: - -- A variable to store the file plan properties as a PSCustomObject using the following syntax: - - $Variable1=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Name"},@{Key="FilePlanPropertyCategory";Value="Name"},@{Key="FilePlanPropertySubcategory";Value="Name"},@{Key="FilePlanPropertyCitation";Value="Name"},@{Key="FilePlanPropertyReferenceId";Value="Name"},@{Key="FilePlanPropertyAuthority";Value="Name"})} - - For example: - - $retentionLabelAction=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Legal"},@{Key="FilePlanPropertyCategory";Value="Tax"},@{Key="FilePlanPropertySubcategory";Value="US_Tax"},@{Key="FilePlanPropertyCitation";Value="LegalCitation"},@{Key="FilePlanPropertyReferenceId";Value="ReferenceA"},@{Key="FilePlanPropertyAuthority";Value="Auth1"})} - -- A second variable to convert the PSCustomObject to a JSON object using the following syntax: - - $Variable2 = ConvertTo-Json $Variable1 - - For example: - - $fpStr = ConvertTo-Json $retentionLabelAction - -You use the second variable as the value for this parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsRecordLabel -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. - -- $false: The label isn't a record label. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Regulatory -{{ Fill Regulatory Description }} - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionAction -The RetentionAction parameter specifies the action for the label. Valid values are: - -- Delete - -- Keep - -- KeepAndDelete - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: - -- A positive integer. - -- The value unlimited. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionType -The RetentionType parameter specifies whether the retention duration is calculated from the content creation date, tagged date, or last modification date. Valid values are: - -- CreationAgeInDays - -- EventAgeInDays - -- ModificationAgeInDays - -- TaggedAgeInDays - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReviewerEmail -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-HoldCompliancePolicy.md deleted file mode 100644 index b1ddf0f1a3..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-HoldCompliancePolicy.md +++ /dev/null @@ -1,235 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-holdcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: New-HoldCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-HoldCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-HoldCompliancePolicy cmdlet to create new preservation policies in the Security & Compliance Center. - -Note: The New-HoldCompliancePolicy cmdlet has been replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-HoldCompliancePolicy [-Name] <String> [-Comment <String>] [-Confirm] [-Enabled <Boolean>] - [-ExchangeLocation <MultiValuedProperty>] [-Force] [-PublicFolderLocation <MultiValuedProperty>] - [-SharePointLocation <MultiValuedProperty>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -New policies are not valid and will not be applied until a preservation rule is added to the policy. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-HoldCompliancePolicy -Name "Regulation 123 Compliance" -ExchangeLocation "Kitty Petersen", "Scott Nakamura" -SharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -``` - -This example creates a preservation policy named "Regulation 123 Compliance" for the mailboxes of Kitty Petersen and Scott Nakamura, and the finance SharePoint Online site. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocation -The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If no mailboxes are specified, then no mailboxes are placed on hold. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocation -The SharePointLocation parameter specifies the SharePoint Online sites to include. You identify the site by its URL value, or you can use the value All to include all sites. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -SharePoint Online sites can't be added to the policy until they have been indexed. If no sites are specified, then no sites are placed on hold. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-HoldComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-HoldComplianceRule.md deleted file mode 100644 index aeb2f247a1..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-HoldComplianceRule.md +++ /dev/null @@ -1,260 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-holdcompliancerule -applicable: Office 365 Security & Compliance Center -title: New-HoldComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-HoldComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-HoldComplianceRule cmdlet to create new preservation rules in the Security & Compliance Center. - -Note: The New-HoldComplianceRule cmdlet has been replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-HoldComplianceRule [-Name] <String> -Policy <PolicyIdParameter> [-Comment <String>] [-Confirm] - [-ContentDateFrom <DateTime>] [-ContentDateTo <DateTime>] [-ContentMatchQuery <String>] - [-Disabled <Boolean>] [-HoldContent <Unlimited>] [-HoldDurationDisplayHint <HoldDurationHint>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The preservation rule must be added to an existing preservation policy using the Policy parameter. Only one rule can be added to each preservation policy. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-HoldComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -ContentDateFrom "09/10/14 5:00 PM" -ContentDateTo "09/10/15 5:00 PM" -HoldContent Unlimited -``` - -This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates will be held indefinitely. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policy -The Policy parameter specifies the policy to contain the rule. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateFrom -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateTo -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HoldContent -The HoldContent parameter specifies the hold duration for the preservation rule. Valid values are: - -- An integer: The hold duration in days. - -- Unlimited: The content is held indefinitely. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HoldDurationDisplayHint -The HoldDurationDisplayHint parameter specifies the units that are used to display the preservation duration in the Security & Compliance Center. Valid values are: - -- Days - -- Months - -- Years - -For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Security & Compliance Center will display 1 year as the content hold duration. - -```yaml -Type: HoldDurationHint -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedFolderMailboxPolicy.md deleted file mode 100644 index 35a0dccc85..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-ManagedFolderMailboxPolicy.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-managedfoldermailboxpolicy -applicable: Exchange Server 2010 -title: New-ManagedFolderMailboxPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010" ---- - -# New-ManagedFolderMailboxPolicy - -## SYNOPSIS -This cmdlet is available only in Exchange Server 2010. - -Use the New-ManagedFolderMailboxPolicy cmdlet to create a managed folder mailbox policy. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ManagedFolderMailboxPolicy [-Name] <String> [-Confirm] [-DomainController <Fqdn>] - [-ManagedFolderLinks <ELCFolderIdParameter[]>] [-Organization <OrganizationIdParameter>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Managed folder mailbox policies are applied to user mailboxes to control message retention settings. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -Managed custom folders are a premium feature of messaging records management (MRM). Mailboxes with policies that include managed custom folders require an Exchange Server Enterprise client access license (CAL). - -## EXAMPLES - -### Example 1 -```powershell -New-ManagedFolderMailboxPolicy -Name "My Managed Folder Mailbox Policy" -ManagedFolderLinks Inbox, MyFolder -``` - -This example creates the managed folder mailbox policy My Managed Folder Mailbox Policy, with a list of managed folders to which the managed folder mailbox policy is to be linked. - -## PARAMETERS - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedFolderLinks -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Organization -This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see [Multi-Tenant Support](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/ff923272(v=exchg.141)). - -The Organization parameter specifies the organization in which you'll perform this action. This parameter doesn't accept wildcard characters, and you must use the exact name of the organization. - -```yaml -Type: OrganizationIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-retention/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionCompliancePolicy.md deleted file mode 100644 index 84c74d2c1e..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionCompliancePolicy.md +++ /dev/null @@ -1,601 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-retentioncompliancepolicy -applicable: Office 365 Security & Compliance Center -title: New-RetentionCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-RetentionCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-RetentionCompliancePolicy cmdlet to create new retention policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Default -``` -New-RetentionCompliancePolicy [-Name] <String> - [-Comment <String>] - [-Confirm] - [-DynamicScopeLocation <MultiValuedProperty>] - [-Enabled <Boolean>] - [-ExchangeLocation <MultiValuedProperty>] - [-ExchangeLocationException <MultiValuedProperty>] - [-Force] - [-ModernGroupLocation <MultiValuedProperty>] - [-ModernGroupLocationException <MultiValuedProperty>] - [-OneDriveLocation <MultiValuedProperty>] - [-OneDriveLocationException <MultiValuedProperty>] - [-PublicFolderLocation <MultiValuedProperty>] - [-RestrictiveRetention <Boolean>] - [-SharePointLocation <MultiValuedProperty>] - [-SharePointLocationException <MultiValuedProperty>] - [-SkypeLocation <MultiValuedProperty>] - [-SkypeLocationException <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### TeamLocation -``` -New-RetentionCompliancePolicy [-Name] <String> - [-Comment <String>] - [-Confirm] - [-Enabled <Boolean>] - [-Force] - [-RestrictiveRetention <Boolean>] - [-TeamsChannelLocation <MultiValuedProperty>] - [-TeamsChannelLocationException <MultiValuedProperty>] - [-TeamsChatLocation <MultiValuedProperty>] - [-TeamsChatLocationException <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -New policies are not valid and will not be applied until a retention rule is added to the policy. In addition, at least one location parameter must be defined to create a retention policy. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-RetentionCompliancePolicy -Name "Regulation 123 Compliance" -ExchangeLocation "Kitty Petersen", "Scott Nakamura" -SharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -``` - -This example creates a retention policy named "Regulation 123 Compliance" for the mailboxes of Kitty Petersen and Scott Nakamura, and the finance SharePoint Online site. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DynamicScopeLocation -{{Fill DynamicScopeLocation Description}} - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocation -The ExchangeLocation parameter specifies the mailboxes to include. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -- The value All for all mailboxes. You can only use this value by itself. - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -If no mailboxes are specified, then no mailboxes are placed on hold. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocationException -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: - -- A mailbox - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModernGroupLocation -The ModernGroupLocation parameter specifies the Office 365 groups to include in the policy. Valid values are: - -- An Office 365 Group - -- The value All for all Office 365 groups. You can only use this value by itself. - -To identify the Office 365 Group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModernGroupLocationException -The ModernGroupLocationException parameter specifies the Office 365 groups to exclude when you're using the value All for the ModernGroupLocation parameter. - -You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocation -The OneDriveLocation parameter specifies the OneDrive for Business sites to include. You identify the site by its URL value, or you can use the value All to include all sites. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveLocationException -This parameter specifies the OneDrive for Business sites to exclude 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictiveRetention -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. - -- $false: Preservation Lock isn't enabled for the policy. This is the default value. - -After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. - -Therefore, before you lock a retention policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocation -The SharePointLocation parameter specifies the SharePoint Online sites to include. You identify the site by its URL value, or you can use the value All to include all sites. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -SharePoint Online sites can't be added to the policy until they have been indexed. If no sites are specified, then no sites are placed on hold. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharePointLocationException -This parameter specifies the SharePoint Online sites to exclude 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkypeLocation -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: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkypeLocationException -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamsChannelLocation -The TeamsChannelLocation parameter specifies the Teams to include in the policy. - -You can use any value that uniquely identifies the team. For example: - -- Name - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamsChannelLocationException -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 - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamsChatLocation -The TeamsChatLocation parameter specifies the Teams users to include in the policy. - -You can use any value that uniquely identifies the user. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamsChatLocationException -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 - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionComplianceRule.md deleted file mode 100644 index 6b6fe1709c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/New-RetentionComplianceRule.md +++ /dev/null @@ -1,367 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/new-retentioncompliancerule -applicable: Office 365 Security & Compliance Center -title: New-RetentionComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-RetentionComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-RetentionComplianceRule cmdlet to create new retention rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### ComplianceTag -``` -New-RetentionComplianceRule -ApplyComplianceTag <String> -Policy <PolicyIdParameter> [-ContentContainsSensitiveInformation <PswsHashtable[]>] - [-Confirm] - [-ContentMatchQuery <String>] - [-ExpirationDateOption <String>] - [-RetentionComplianceAction <String>] - [-WhatIf] [<CommonParameters>] -``` - -### Default -``` -New-RetentionComplianceRule [-Name] <String> -Policy <PolicyIdParameter> [-Comment <String>] [-ExcludedItemClasses <MultiValuedProperty>] [-RetentionDuration <Unlimited>] [-RetentionDurationDisplayHint <HoldDurationHint>] - [-Confirm] - [-ContentMatchQuery <String>] - [-ExpirationDateOption <String>] - [-RetentionComplianceAction <String>] - [-WhatIf] [<CommonParameters>] -``` - -### PublishComplianceTag -``` -New-RetentionComplianceRule -Policy <PolicyIdParameter> -PublishComplianceTag <String> [-Confirm] - [-ExpirationDateOption <String>] - [-RetentionComplianceAction <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The retention rule must be added to an existing retention policy using the Policy parameter. Only one rule can be added to each retention policy. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-RetentionComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -RetentionDuration Unlimited -``` - -This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content will be held indefinitely. - -## PARAMETERS - -### -ApplyComplianceTag -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. - -You can't use this parameter with the Name or PublishComplianceTag parameters. - -```yaml -Type: String -Parameter Sets: ComplianceTag -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policy -The Policy parameter specifies the policy to contain the rule. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublishComplianceTag -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. - -You can't use this parameter with the Name or ApplyComplianceTag parameters. - -```yaml -Type: String -Parameter Sets: PublishComplianceTag -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentContainsSensitiveInformation -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"}). - -Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://go.microsoft.com/fwlink/p/?LinkId=529420). - -You can use this parameter with the ApplyComplianceTag parameter. - -```yaml -Type: PswsHashtable[] -Parameter Sets: ComplianceTag -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: ComplianceTag, Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedItemClasses -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 - -- IPM.Note.Microsoft.Conversation.Voice - -- IPM.Note.Microsoft.Missed - -- IPM.Note.Microsoft.Missed.Voice - -- IPM.Note.Microsoft.Voicemail - -- IPM.Note.Microsoft.VoiceMessage.UA - -- IPM.Note.Microsoft.Voicemail.UM - -- IPM.Note.Microsoft.Voicemail.UM.CA - -You can specify multiple item class values by using the syntax "Value1","Value2",..."ValueN". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExpirationDateOption -The ExpirationDateOption parameter specifies whether the expiration date is calculated from the content creation date or last modification date. Valid values are: - -- CreationAgeInDays - -- ModificationAgeInDays - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionComplianceAction -The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: - -- Delete - -- Keep - -- KeepAndDelete - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter specifies the hold duration for the retention rule. Valid values are: - -- An integer: The hold duration in days. - -- Unlimited: The content is held indefinitely. - -```yaml -Type: Unlimited -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDurationDisplayHint -The RetentionDurationDisplayHint parameter specifies the units that are used to display the retention duration in the Security & Compliance Center. Valid values are: - -- Days - -- Months - -- Years - -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Security & Compliance Center will display 1 year as the content hold duration. - -```yaml -Type: HoldDurationHint -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ComplianceRetentionEventType.md deleted file mode 100644 index 2d7411ac7c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ComplianceRetentionEventType.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/Remove-ComplianceRetentionEventType -applicable: Office 365 Security & Compliance Center -title: Remove-ComplianceRetentionEventType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ComplianceRetentionEventType - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ComplianceRetentionEventType cmdlet to remove retention event types in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ComplianceRetentionEventType -Identity <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ComplianceRetentionEventType -Identity "Fabrikam Project" -``` - -This example remove the retention event type name Fabrikam Project - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ComplianceTag.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ComplianceTag.md deleted file mode 100644 index 1d88f73513..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-ComplianceTag.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-compliancetag -applicable: Office 365 Security & Compliance Center -title: Remove-ComplianceTag -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ComplianceTag - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ComplianceTag cmdlet to remove labels from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ComplianceTag [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -IRemove-ComplianceTag -Identity "HR Content" -``` - -This example removes the label named HR Content. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the label that you want to remove. You can use any value that uniquely identifies the tag. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-HoldCompliancePolicy.md deleted file mode 100644 index 75b12c1c84..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-HoldCompliancePolicy.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-holdcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Remove-HoldCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-HoldCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-HoldCompliancePolicy cmdlet to remove preservation policies from the Security & Compliance Center. - -Note: The Remove-HoldCompliancePolicy cmdlet has been replaced by the Remove-RetentionCompliancePolicy cmdlet. If you have scripts that use Remove-HoldCompliancePolicy, update them to use Remove-RetentionCompliancePolicy. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-HoldCompliancePolicy [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You should also remove the preservation rule that corresponds to the removed policy by using the Remove-HoldComplianceRule cmdlet. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-HoldCompliancePolicy -Identity "Regulation 123 Compliance" -``` - -This example removes the preservation policy named "Regulation 123 Compliance". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the preservation policy to remove. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-HoldComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-HoldComplianceRule.md deleted file mode 100644 index ef7988332c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-HoldComplianceRule.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-holdcompliancerule -applicable: Office 365 Security & Compliance Center -title: Remove-HoldComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-HoldComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-HoldComplianceRule cmdlet to remove preservation rules from the Security & Compliance Center. - -Note: The Remove-HoldComplianceRule cmdlet has been replaced by the Remove-RetentionComplianceRule cmdlet. If you have scripts that use Remove-HoldComplianceRule, update them to use Remove-RetentionComplianceRule. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-HoldComplianceRule [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Removing a preservation rule causes the release of all Exchange mailbox and SharePoint site preservations that are associated with the rule. Removing a preservation rule also causes the corresponding preservation policy to become invalid, so you should remove it by using the Remove-HoldCompliancePolicy cmdlet. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-HoldComplianceRule -Identity "One Year Standard" -``` - -This example removes the preservation rule named "One Year Standard". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the preservation rule to remove. You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionCompliancePolicy.md deleted file mode 100644 index 53e84fc200..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionCompliancePolicy.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-retentioncompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Remove-RetentionCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-RetentionCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-HoldCompliancePolicy cmdlet to remove retention policies from the Security & Compliance Center. This cmdlet also removes the corresponding retention rule. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -New policies are not valid and will not be applied until a retention rule is added to the policy. In addition, at least one location parameter must be defined to create a retention policy. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-RetentionCompliancePolicy -Identity "Regulation 123 Compliance" -``` - -This example removes the retention policy named "Regulation 123 Compliance". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -The ForceDeletion switch forces the removal of the retention policy. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionComplianceRule.md deleted file mode 100644 index 4be7c5f474..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Remove-RetentionComplianceRule.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/remove-retentioncompliancerule -applicable: Office 365 Security & Compliance Center -title: Remove-RetentionComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-RetentionComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-RetentionComplianceRule cmdlet to remove retention rules from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-RetentionComplianceRule [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Removing a retention rule causes the release of all Exchange mailbox and SharePoint site retentions that are associated with the rule. Removing a retention rule also causes the corresponding retention policy to become invalid, so you should remove it by using the Remove-RetentionCompliancePolicy cmdlet. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-RetentionComplianceRule -Identity "One Year Standard" -``` - -This example removes the retention rule named "One Year Standard". - -## PARAMETERS - -### -Identity -The Identity parameter specifies the retention rule to remove. You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -The ForceDeletion switch forces the removal of the retention rule. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ComplianceRetentionEventType.md deleted file mode 100644 index c8f5e65599..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ComplianceRetentionEventType.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/Set-ComplianceRetentionEventType -applicable: Office 365 Security & Compliance Center -title: Set-ComplianceRetentionEventType -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-ComplianceRetentionEventType - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-ComplianceRetentionEventType cmdlet to modify retention event types in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ComplianceRetentionEventType -Identity <ComplianceRuleIdParameter> [-Comment <String>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-ComplianceRetentionEventType -Identity "Fabrikam Project" -Comment "Case officer is Pedro Pizarro" -``` - -This example add a comment to the retention event type named Fabrikam Project - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ComplianceTag.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ComplianceTag.md deleted file mode 100644 index e29da2fd34..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-ComplianceTag.md +++ /dev/null @@ -1,278 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-compliancetag -applicable: Office 365 Security & Compliance Center -title: Set-ComplianceTag -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-ComplianceTag - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-ComplianceTag cmdlet to modify labels in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ComplianceTag [-Identity] <ComplianceRuleIdParameter> - [-Comment <String>] - [-Confirm] - [-EventType <ComplianceRuleIdParameter>] - [-FilePlanProperty <String>] - [-Force] - [-Notes <String>] - [-RetentionDuration <Unlimited>] - [-ReviewerEmail <SmtpAddress[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-ComplianceTag -Identity "HR Content" -RetentionDuration 2555 -Comment "Retain HR content for 7 years" -``` - -This example modifies the existing label named HR Content by modifying the retention duration and adding a comment. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the label that you want to modify. You can use any value that uniquely identifies the tag. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -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 - -- Distinguished name (DN) - -- GUID - -You can use the Get-RetentionComplianceRule cmdlet to view the available retention rules. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilePlanProperty -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 - -- Get-FilePlanPropertyCategory | Format-List Name - -- Get-FilePlanPropertyCitation | Format-List Name - -- Get-FilePlanPropertyDepartment | Format-List Name - -- Get-FilePlanPropertyReferenceId | Format-List Name - -- Get-FilePlanPropertySubCategory | Format-List Name - -A valid value for this parameter involves two steps: - -- A variable to store the file plan properties as a PSCustomObject using the following syntax: - - $Variable1=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Name"},@{Key="FilePlanPropertyCategory";Value="Name"},@{Key="FilePlanPropertySubcategory";Value="Name"},@{Key="FilePlanPropertyCitation";Value="Name"},@{Key="FilePlanPropertyReferenceId";Value="Name"},@{Key="FilePlanPropertyAuthority";Value="Name"})} - - For example: - - $retentionLabelAction=[PSCustomObject]@{Settings=@(@{Key="FilePlanPropertyDepartment";Value="Legal"},@{Key="FilePlanPropertyCategory";Value="Tax"},@{Key="FilePlanPropertySubcategory";Value="US_Tax"},@{Key="FilePlanPropertyCitation";Value="LegalCitation"},@{Key="FilePlanPropertyReferenceId";Value="ReferenceA"},@{Key="FilePlanPropertyAuthority";Value="Auth1"})} - -- A second variable to convert the PSCustomObject to a JSON object using the following syntax: - - $Variable2 = ConvertTo-Json $Variable1 - - For example: - - $fpStr = ConvertTo-Json $retentionLabelAction - -You use the second variable as the value for this parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: - -- A positive integer. - -- The value unlimited. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReviewerEmail -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-HoldCompliancePolicy.md deleted file mode 100644 index a055e7fa50..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-HoldCompliancePolicy.md +++ /dev/null @@ -1,343 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-holdcompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Set-HoldCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-HoldCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-HoldCompliancePolicy cmdlet to modify existing preservation policies in the Security & Compliance Center. - -Note: The Set-HoldCompliancePolicy cmdlet has been replaced by the Set-RetentionCompliancePolicy cmdlet. If you have scripts that use Set-HoldCompliancePolicy, update them to use Set-RetentionCompliancePolicy. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### RetryDistribution -``` -Set-HoldCompliancePolicy [-Identity] <PolicyIdParameter> [-RetryDistribution] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Set-HoldCompliancePolicy [-Identity] <PolicyIdParameter> - [-AddExchangeLocation <MultiValuedProperty>] - [-AddPublicFolderLocation <MultiValuedProperty>] - [-AddSharePointLocation <MultiValuedProperty>] - [-Comment <String>] - [-Confirm] - [-Enabled <Boolean>] [-Force] - [-RemoveExchangeLocation <MultiValuedProperty>] - [-RemovePublicFolderLocation <MultiValuedProperty>] - [-RemoveSharePointLocation <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-HoldCompliancePolicy -Identity "Regulation 123 Compliance" -AddExchangeLocation "Kitty Petersen" -AddSharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -RemovePublicFolderLocation All -Comment "Added new counsel, 9/9/14" -``` - -This example makes the following changes to the existing preservation policy named "Regulation 123 Compliance": - -- Adds the mailbox for the user named Kitty Petersen. - -- Adds the SharePoint Online site https://contoso.sharepoint.com/sites/teams/finance. - -- Removes public folders. - -- Updates the comment. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RetryDistribution -The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint Online locations. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocation -The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddPublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocation -The AddSharePointLocation parameter specifies the SharePoint Online 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. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -SharePoint Online sites can't be added to the policy until they have been indexed. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocation -The RemoveExchangeLocation parameter specifies the existing mailboxes to remove from the policy. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemovePublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocation -The RemoveSharePointLocation parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-HoldComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-HoldComplianceRule.md deleted file mode 100644 index 03d63798f6..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-HoldComplianceRule.md +++ /dev/null @@ -1,248 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-holdcompliancerule -applicable: Office 365 Security & Compliance Center -title: Set-HoldComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-HoldComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-HoldComplianceRule cmdlet to modify existing preservation rules in the Security & Compliance Center. - -Note: The Set-HoldComplianceRule cmdlet has been replaced by the Set-RetentionComplianceRule cmdlet. If you have scripts that use Set-HoldComplianceRule, update them to use Set-RetentionComplianceRule. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-HoldComplianceRule [-Identity] <ComplianceRuleIdParameter> [-Comment <String>] [-Confirm] - [-ContentDateFrom <DateTime>] [-ContentDateTo <DateTime>] [-ContentMatchQuery <String>] - [-Disabled <Boolean>] [-HoldContent <Unlimited>] [-HoldDurationDisplayHint <HoldDurationHint>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-HoldComplianceRule -Identity "Internal Company Rule" -HoldContent 180 -``` - -This example changes the hold duration for the existing preservation rule named "Internal Company Rule". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateFrom -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateTo -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HoldContent -The HoldContent parameter specifies the hold duration for the preservation rule. Valid values are: - -- An integer: The hold duration in days. - -- Unlimited: The content is held indefinitely. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HoldDurationDisplayHint -The HoldDurationDisplayHint parameter specifies the units that are used to display the preservation duration in the Security & Compliance Center. Valid values are Days, Months or Years. - -- Days - -- Months - -- Years - -For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Security & Compliance Center will display 1 year as the content hold duration. - -```yaml -Type: HoldDurationHint -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionCompliancePolicy.md deleted file mode 100644 index ffd5c205fa..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionCompliancePolicy.md +++ /dev/null @@ -1,977 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-retentioncompliancepolicy -applicable: Office 365 Security & Compliance Center -title: Set-RetentionCompliancePolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-RetentionCompliancePolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-RetentionCompliancePolicy cmdlet to modify existing retention policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### RetryDistribution -``` -Set-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> [-RetryDistribution] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Set-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> - [-AddExchangeLocation <MultiValuedProperty>] - [-AddExchangeLocationException <MultiValuedProperty>] - [-AddModernGroupLocation <MultiValuedProperty>] - [-AddModernGroupLocationException <MultiValuedProperty>] - [-AddOneDriveLocation <MultiValuedProperty>] - [-AddOneDriveLocationException <MultiValuedProperty>] - [-AddPublicFolderLocation <MultiValuedProperty>] - [-AddSharePointLocation <MultiValuedProperty>] - [-AddSharePointLocationException <MultiValuedProperty>] - [-AddSkypeLocation <MultiValuedProperty>] - [-AddSkypeLocationException <MultiValuedProperty>] - [-Comment <String>] - [-Confirm] - [-Enabled <Boolean>] - [-Force] - [-RemoveExchangeLocation <MultiValuedProperty>] - [-RemoveExchangeLocationException <MultiValuedProperty>] - [-RemoveModernGroupLocation <MultiValuedProperty>] - [-RemoveModernGroupLocationException <MultiValuedProperty>] - [-RemoveOneDriveLocation <MultiValuedProperty>] - [-RemoveOneDriveLocationException <MultiValuedProperty>] - [-RemovePublicFolderLocation <MultiValuedProperty>] - [-RemoveSharePointLocation <MultiValuedProperty>] - [-RemoveSharePointLocationException <MultiValuedProperty>] - [-RemoveSkypeLocation <MultiValuedProperty>] - [-RemoveSkypeLocationException <MultiValuedProperty>] - [-RestrictiveRetention <Boolean>] - [-WhatIf] [<CommonParameters>] -``` - -### TeamLocation -``` -Set-RetentionCompliancePolicy [-Identity] <PolicyIdParameter> - [-AddTeamsChannelLocation <MultiValuedProperty>] - [-AddTeamsChannelLocationException <MultiValuedProperty>] - [-AddTeamsChatLocation <MultiValuedProperty>] - [-AddTeamsChatLocationException <MultiValuedProperty>] - [-Comment <String>] - [-Confirm] - [-Enabled <Boolean>] - [-Force] - [-RemoveTeamsChannelLocation <MultiValuedProperty>] - [-RemoveTeamsChannelLocationException <MultiValuedProperty>] - [-RemoveTeamsChatLocation <MultiValuedProperty>] - [-RemoveTeamsChatLocationException <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-RetentionCompliancePolicy -Identity "Regulation 123 Compliance" -AddExchangeLocation "Kitty Petersen" -AddSharePointLocation "https://contoso.sharepoint.com/sites/teams/finance" -RemovePublicFolderLocation All -Comment "Added new counsel, 9/9/14" -``` - -This example makes the following changes to the existing retention policy named "Regulation 123 Compliance": - -- Adds the mailbox for the user named Kitty Petersen. - -- Adds the SharePoint Online site https://contoso.sharepoint.com/sites/teams/finance. - -- Removes public folders. - -- Updates the comment. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RetryDistribution -The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint Online locations. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocation -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 - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocationException -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 - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddModernGroupLocation -The AddModernGroupLocation parameter specifies the Office 365 groups to add to the list of included Office 365 groups when you aren't using the value All for the ModernGroupLocation parameter. - -You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddModernGroupLocationException -The AddModernGroupLocationException parameter specifies the Office 365 groups to add to the list of excluded Office 365 groups when you're using the value All for the ModernGroupLocation parameter. - -You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddOneDriveLocation -The AddOneDriveLocation parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddOneDriveLocationException -This parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddPublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocation -The AddSharePointLocation parameter specifies the SharePoint Online 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. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -SharePoint Online sites can't be added to the policy until they have been indexed. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSharePointLocationException -This parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSkypeLocation -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: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSkypeLocationException -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddTeamsChannelLocation -The AddTeamsChannelLocation parameter specifies the Teams to add to the policy. - -You can use any value that uniquely identifies the team. For example: - -- Name - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddTeamsChannelLocationException -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 - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddTeamsChatLocation -The AddTeamsChatLocation parameter specifies the Teams users to add to the policy. - -You can use any value that uniquely identifies the user. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddTeamsChatLocationException -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 - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The Enabled parameter specifies whether the policy is enabled. Valid values are: - -- $true: The policy is enabled. This is the default value. - -- $false: The policy is disabled. - -```yaml -Type: Boolean -Parameter Sets: Identity, TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity, TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocation -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 - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocationException -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: - -- A mailbox - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveModernGroupLocation -The RemoveModernGroupLocation parameter specifies the Office 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 Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveModernGroupLocationException -The RemoveModernGroupLocationException parameter specifies the Office 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 Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveOneDriveLocation -The RemoveOneDriveLocation parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveOneDriveLocationException -This parameter specifies the OneDrive for Business 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemovePublicFolderLocation -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocation -The RemoveSharePointLocation parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSharePointLocationException -This parameter specifies the SharePoint Online 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: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSkypeLocation -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: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSkypeLocationException -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictiveRetention -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. - -- $false: Preservation Lock isn't enabled for the policy. This is the default value. - -After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. - -Therefore, before you lock a retention policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. - -```yaml -Type: Boolean -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveTeamsChannelLocation -The RemoveTeamsChannelLocation parameter specifies the Teams to remove from the policy. - -You can use any value that uniquely identifies the team. For example: - -- Name - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveTeamsChannelLocationException -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 - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveTeamsChatLocation -The RemoveTeamsChatLocation parameter specifies the Teams users to remove from the policy. - -You can use any value that uniquely identifies the user. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveTeamsChatLocationException -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 - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: TeamLocation -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionComplianceRule.md deleted file mode 100644 index 72ca200072..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionComplianceRule.md +++ /dev/null @@ -1,356 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-retentioncompliancerule -applicable: Office 365 Security & Compliance Center -title: Set-RetentionComplianceRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-RetentionComplianceRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-RetentionComplianceRule cmdlet to modify existing retention rules in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-RetentionComplianceRule [-Identity] <ComplianceRuleIdParameter> - [-ApplyComplianceTag <String>] - [-Comment <String>] - [-Confirm] - [-ContentContainsSensitiveInformation <PswsHashtable[]>] - [-ContentDateFrom <DateTime>] - [-ContentDateTo <DateTime>] - [-ContentMatchQuery <String>] - [-ExcludedItemClasses <MultiValuedProperty>] - [-ExpirationDateOption <String>] - [-RetentionComplianceAction <String>] - [-RetentionDuration <Unlimited>] - [-RetentionDurationDisplayHint <HoldDurationHint>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-RetentionComplianceRule -Identity "Internal Company Rule" -RetentionDuration 180 RetentionDurationDisplayHint Days -``` - -This example changes the hold duration for the existing retention rule named "Internal Company Rule". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ApplyComplianceTag -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. - -You can't use this parameter with the Name or PublishComplianceTag parameters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentContainsSensitiveInformation -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"}). - -Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information types for your organization. For more information on sensitive information types, see [What the sensitive information types in Exchange look for](https://go.microsoft.com/fwlink/p/?LinkId=529420). - -```yaml -Type: PswsHashtable[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateFrom -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDateTo -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMatchQuery -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedItemClasses -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 - -- IPM.Note.Microsoft.Conversation.Voice - -- IPM.Note.Microsoft.Missed - -- IPM.Note.Microsoft.Missed.Voice - -- IPM.Note.Microsoft.Voicemail - -- IPM.Note.Microsoft.VoiceMessage.UA - -- IPM.Note.Microsoft.Voicemail.UM - -- IPM.Note.Microsoft.Voicemail.UM.CA - -You can specify multiple item class values by using the syntax "Value1","Value2",..."ValueN". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExpirationDateOption -The ExpirationDateOption parameter specifies whether the expiration date is calculated from the content creation date or last modification date. Valid values are: - -- CreationAgeInDays - -- ModificationAgeInDays - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionComplianceAction -The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: - -- Delete - -- Keep - -- KeepAndDelete - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter specifies the hold duration for the retention rule. Valid values are: - -- An integer: The hold duration in days. - -- Unlimited: The content is held indefinitely. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDurationDisplayHint -The RetentionDurationDisplayHint parameter specifies the units that are used to display the retention duration in the Security & Compliance Center. Valid values are Days, Months or Years. - -- Days - -- Months - -- Years - -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Security & Compliance Center will display 1 year as the content hold duration. - -```yaml -Type: HoldDurationHint -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionPolicy.md deleted file mode 100644 index 801a9e9c94..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Set-RetentionPolicy.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/set-retentionpolicy -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-RetentionPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-RetentionPolicy - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-RetentionPolicy cmdlet to change the properties of an existing retention policy. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-RetentionPolicy [-Identity] <MailboxPolicyIdParameter> - [-Confirm] - [-DomainController <Fqdn>] - [-Force] - [-IsDefault] - [-IsDefaultArbitrationMailbox] - [-Name <String>] - [-RetentionId <Guid>] - [-RetentionPolicyTagLinks <RetentionPolicyTagIdParameter[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-RetentionPolicy "MyPolicy" -RetentionPolicyTagLinks "MyRetentionPolicyTag" -``` - -This example modifies the policy MyPolicy to link the retention policy tag MyRetentionPolicyTag with it. - -The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters). - -## PARAMETERS - -### -Identity -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 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch overrides the confirmation prompt displayed by the cmdlet when you use the RetentionId parameter. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefault -This parameter is reserved for internal Microsoft use. - -To set the default retention policy for new mailboxes, use the RetentionPolicy parameter on the Set-MailboxPlan cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefaultArbitrationMailbox -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. - -This parameter isn't available in on-premises deployments. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionId -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionPolicyTagLinks -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance-retention/Start-ManagedFolderAssistant.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Start-ManagedFolderAssistant.md deleted file mode 100644 index 578eb8c40d..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Start-ManagedFolderAssistant.md +++ /dev/null @@ -1,297 +0,0 @@ ---- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Start-ManagedFolderAssistant - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Start-ManagedFolderAssistant cmdlet to immediately start messaging records management (MRM) processing of mailboxes that you specify. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Default -``` -Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> - [-AggMailboxCleanup] - [-DomainController <Fqdn>] - [-Confirm] - [-HoldCleanup] - [-WhatIf] [<CommonParameters>] -``` - -### HoldCleanup -``` -Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> -HoldCleanup - [-AggMailboxCleanup] - [-Confirm] - [-FullCrawl] - [-InactiveMailbox] - [-WhatIf] [<CommonParameters>] -``` - -### StopHoldCleanup -``` -Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-StopHoldCleanup] - [-AggMailboxCleanup] - [-Confirm] - [-FullCrawl] - [-InactiveMailbox] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Managed Folder Assistant uses the retention policy settings of users' mailboxes to process retention of items. This mailbox processing occurs automatically. You can use the Start-ManagedFolderAssistant cmdlet to immediately start processing the specified mailbox. - -In Exchange Server 2010 release to manufacturing (RTM), the Identity parameter specifies the Mailbox server to start the assistant and process all mailboxes on that server, and the Mailbox parameter specifies the mailbox to process. In Exchange 2010 Service Pack 1 (SP1) and later, the Mailbox parameter has been removed, and the Identity parameter accepts the mailbox or mail user to process. - -If you use these parameters in scheduled commands or scripts, we recommend that you review them and make any necessary changes. - -For more information, see [KB4032361](https://support.microsoft.com/help/4032361/messaging-records-management-and-retention-policies-in-office-365). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Start-ManagedFolderAssistant -Identity "Chris" -``` - -This example processes the mailbox for a user with the alias Chris. - -### Example 2 -```powershell -Get-Mailbox -Anr Chr -DomainController DC01 | Start-ManagedFolderAssistant -``` - -This example uses the Get-Mailbox command to retrieve all the mailboxes that resolve from the ambiguous name resolution (ANR) search on the string "Chr" in the domain DC01 (for example, users such as Chris Ashton, Christian Hess, and Christa Geller), and the results are piped to the Start-ManagedFolderAssistant cmdlet for processing. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -HoldCleanup -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://docs.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). - -```yaml -Type: SwitchParameter -Parameter Sets: HoldCleanup -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: SwitchParameter -Parameter Sets: Default -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 -``` - -### -AggMailboxCleanup -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: Default -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FullCrawl -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. - -```yaml -Type: SwitchParameter -Parameter Sets: HoldCleanup, StopHoldCleanup -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InactiveMailbox -This parameter is available only in the cloud-based service. - -The InactiveMailbox switch runs the command only inactive mailboxes. 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. - -When you use this switch, items aren't moved from the inactive mailbox to the archive mailbox. - -```yaml -Type: SwitchParameter -Parameter Sets: HoldCleanup, StopHoldCleanup -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StopHoldCleanup -This parameter is available only in the cloud-based service. - -The StopHoldCleanup parameter stops a previous hold clean-up command that was issued on the mailbox. You don't need to specify a value with this switch. - -A hold clean-up command will run until it completely scans the Recoverable Items folder for duplicate versions of items (it even continues after an interruption). In some cases, the hold clean-up command gets stuck, which can block other regular MRM tasks on the mailbox (for example, expiring items). The StopHoldCleanup switch tells MRM to abandon the stuck hold clean-up task so that regular tasks can continue. - -```yaml -Type: SwitchParameter -Parameter Sets: StopHoldCleanup -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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 - -[Export-MailboxDiagnosticLogs](https://docs.microsoft.com/powershell/module/exchange/mailboxes/Export-MailboxDiagnosticLogs) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Validate-RetentionRuleQuery.md b/exchange/exchange-ps/exchange/policy-and-compliance-retention/Validate-RetentionRuleQuery.md deleted file mode 100644 index 7da5926d0c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance-retention/Validate-RetentionRuleQuery.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-retention/validate-retentionrulequery -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Validate-RetentionRuleQuery -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Validate-RetentionRuleQuery - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Validate-RetentionRuleQuery cmdlet to validate the Keyword Query Language (KQL) content search filters for retention rules. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Validate-RetentionRuleQuery -KqlQueryString <String> [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Validate-RetentionRuleQuery -KqlQueryString 'from:"Ann Beebe" AND subject:northwind' -``` - -This example validates the specified KQL content search filter. - -## PARAMETERS - -### -KqlQueryString -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 about KQL, see [Keyword Query Language (KQL) syntax reference](https://go.microsoft.com/fwlink/p/?linkid=269603). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-JournalArchiving.md b/exchange/exchange-ps/exchange/policy-and-compliance/Disable-JournalArchiving.md deleted file mode 100644 index 970c769709..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Disable-JournalArchiving.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/disable-journalarchiving -applicable: Exchange Online -title: Disable-JournalArchiving -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Disable-JournalArchiving - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Disable-JournalArchiving cmdlet to disable journal archiving for specific users. Microsoft Office 365 journal archiving uses mailboxes in Exchange Online to record or journal messages for mailboxes in on-premises organizations. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Disable-JournalArchiving [-Identity] <MailboxIdParameter> [-Confirm] [-PreserveMailUser] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -For each on-premise mailbox that's configured for journal archiving in Office 365, a mail user (also known as a mail-enabled user) and a journal archive mailbox are created in Exchange Online. The mail user routes the incoming journaled messages from the on-premises organization, and the journal archive mailbox stores the journaled messages in the cloud. - -The Disable-JournalArchiving cmdlet removes the mail user and converts the journal archive mailbox into an inactive mailbox. The inactive mailbox remains fully available for In-place eDiscovery. - -In hybrid organizations that use DirSync, this cmdlet doesn't remove the mail user. Removal of the mail user is handled by DirSync. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Disable-JournalArchiving -Identity TimothyAmaral_Archive -``` - -This example disables the journal archiving for the user named Timothy Amaral. Timothy's journal archive mailbox in Exchange Online is named TimothyAmaral\_Archive. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreserveMailUser -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Export-TransportRuleCollection.md b/exchange/exchange-ps/exchange/policy-and-compliance/Export-TransportRuleCollection.md deleted file mode 100644 index 0df5906e19..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Export-TransportRuleCollection.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Export-TransportRuleCollection - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Export-TransportRuleCollection cmdlet to export the transport rules in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Export-TransportRuleCollection [[-Identity] <RuleIdParameter>] - [-Confirm] - [-DomainController <Fqdn>] - [-ExportLegacyRules] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-TransportRuleCollection cmdlet can be used to export the transport rule collection in your organization. The format of the exported transport rule collection changed in Exchange Server 2013. The new format can't be imported into Exchange Server 2010. - -Exporting the rules collection is a two-step process. You first export the rules collection to a variable, and then use the Set-Content cmdlet to write the data to an XML file. For more information, see [Set-Content](https://go.microsoft.com/fwlink/p/?linkId=156132). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -$file = Export-TransportRuleCollection; Set-Content -Path "C:\My Docs\Rules.xml" -Value $file.FileData -Encoding Byte -``` - -This example exports transport rules. Rule data is first exported to the variable $file, and then written to the XML file Rules.xml in the C:\\My Docs folder. - -**Note**: In PowerShell 6.0 or later, replace `-Encoding Byte` with `-AsByteStream`. - -### Example 2 -```powershell -$file = Export-TransportRuleCollection -ExportLegacyRules; Set-Content -Path "C:\MyDocs\LegacyRules.xml" -Value $file.FileData -Encoding Byte -``` - -In Exchange Server 2010, this example exports legacy transport rules created in Exchange 2007 using the ExportLegacyRules switch. The cmdlet should be run from an Exchange 2010 Hub Transport server. The exported rules collection can then be imported to Exchange 2010 using the Import-TransportRuleCollection cmdlet. - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExportLegacyRules -This parameter is available or functional 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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -This cmdlet is available only in on-premises Exchange, and is functional only in Exchange Server 2010. - -The Identity parameter specifies the name or GUID of a transport rule to be exported. - -```yaml -Type: RuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance/Get-ActivityAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-ActivityAlert.md deleted file mode 100644 index b415346eab..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-ActivityAlert.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-activityalert -applicable: Office 365 Security & Compliance Center -title: Get-ActivityAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-ActivityAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ActivityAlert cmdlet to view activity alerts in the Security & Compliance Center. Activity alerts send you email notifications when users perform specific activities in Office 365. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ActivityAlert [[-Identity] <ComplianceRuleIdParameter>] [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ActivityAlert | Format-List Disabled,Name,Description,Operation,UserId,NotifyUser -``` - -This example returns a summary list of all activity alerts. - -### Example 2 -```powershell -Get-ActivityAlert -Identity "All Mailbox Activities" -``` - -This example returns detailed information about the activity alert named All Mailbox Activities. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the activity alert that you want to view. You can use any value that uniquely identifies the activity alert. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-AdministrativeUnit.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-AdministrativeUnit.md deleted file mode 100644 index 31bb9dcf44..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-AdministrativeUnit.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-administrativeunit -applicable: Exchange Online -title: Get-AdministrativeUnit -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-AdministrativeUnit - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-AdministrativeUnit cmdlet to view administrative units, which are Azure Active Directory containers of resources. You can use administrative units to delegate administrative permissions and apply policies to different groups of users. - -Note: Administrative units are only available in Azure Active Directory Premium. You create and manage administrative units in Azure AD PowerShell. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AdministrativeUnit [[-Identity] <AdministrativeUnitIdParameter>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AdministrativeUnit -``` - -This example returns a summary list of all Azure Active Directory administrative units. - -### Example 2 -```powershell -Get-AdministrativeUnit -Identity "West Coast" | Format-List -``` - -This example returns detailed information about the administrative unit with the display name West Coast. - -## PARAMETERS - -### -Identity -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 Azure AD PowerShell) - -- ExternalDirectoryObjectId (this GUID value is the same as the ObjectId property in Azure AD PowerShell) - -- Name (GUID value) - -- Distinguished name (DN) - -- GUID (different value than Name) - -```yaml -Type: AdministrativeUnitIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierPoliciesApplicationStatus.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierPoliciesApplicationStatus.md deleted file mode 100644 index 0f57460659..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierPoliciesApplicationStatus.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-informationbarrierpoliciesapplicationstatus -applicable: Office 365 Security & Compliance Center -title: Get-InformationBarrierPoliciesApplicationStatus -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-InformationBarrierPoliciesApplicationStatus - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-InformationBarrierPoliciesApplicationStatus cmdlet to view the application status of information barrier policies. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Default (Default) -``` -Get-InformationBarrierPoliciesApplicationStatus [-All] [<CommonParameters>] -``` - -### Identity -``` -Get-InformationBarrierPoliciesApplicationStatus [[-Identity] <PolicyIdParameter>] [-All] [<CommonParameters>] -``` - -## DESCRIPTION - For more information, see [View status of information barrier policy application](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies#view-status-of-user-accounts-segments-policies-or-policy-application). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-InformationBarrierPoliciesApplicationStatus -``` - -This example returns the most recent application of information barrier policies by the Start-InformationBarrierPoliciesApplication cmdlet. - -### Example 2 -```powershell -Get-InformationBarrierPoliciesApplicationStatus -All -``` - -This example returns all applications of information barrier policies by the Start-InformationBarrierPoliciesApplication cmdlet. - -## PARAMETERS - -### -Identity -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: Office 365 Security & Compliance Center - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -All -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierPolicy.md deleted file mode 100644 index 5ca5f58f3f..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierPolicy.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-informationbarrierpolicy -applicable: Office 365 Security & Compliance Center -title: Get-InformationBarrierPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-InformationBarrierPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-InformationBarrierPolicy cmdlet to view information barrier policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### InformationBarrierDefault (Default) -``` -Get-InformationBarrierPolicy [-ExoPolicyId <Guid>] [<CommonParameters>] -``` - -### Identity -``` -Get-InformationBarrierPolicy [[-Identity] <PolicyIdParameter>] [-ExoPolicyId <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -For more information, see [Information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-InformationBarrierPolicy | Format-Table Name,State,AssignedSegment,Segments* -Auto -``` - -This example displays a summary list of all information barrier policies. - -### Example 2 -```powershell -Get-InformationBarrierPolicy -Identity HR-Sales -``` - -This example displays detailed information for the information barrier policy named HR-Sales. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -You can't use this parameter with the ExOPolicyId parameter. - -```yaml -Type: PolicyIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ExoPolicyId -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. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierRecipientStatus.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierRecipientStatus.md deleted file mode 100644 index 556ee2c1c8..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierRecipientStatus.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-informationbarrierrecipientstatus -applicable: Office 365 Security & Compliance Center -title: Get-InformationBarrierRecipientStatus -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-InformationBarrierRecipientStatus - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-InformationBarrierRecipientStatus cmdlet to return information about recipients and their relationship to information barrier policies. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-InformationBarrierRecipientStatus [-Identity] <RecipientIdParameter> [[-Identity2] <RecipientIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -The following information is returned in the output of this cmdlet: - -- A warning message that indicates whether or not the recipient is included in an information barrier policy. - -- If present, the GUID part in the ExOPolicyId property value identifies the information barrier policy that the recipient is included in. You can run the command `Get-InformationBarrierPolicy -ExOPolicyId <GUID>` to identify and view the details of the policy. - -- Basic information about the recipient (display name, alias, and last name). - -- Recipient properties that can be used in organization segments (Department, CustomAttributeN, etc.) and the current property values for the recipient. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-InformationBarrierRecipientStatus -Identity meganb -``` - -This example returns the information barrier policy information for the user meganb. - -### Example 2 -```powershell -Get-InformationBarrierRecipientStatus -Identity meganb -Identity2 alexw -``` - -This example returns the information barrier policy relationship for the users meganb and alexw. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Identity2 -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -When you include this parameter in a command, you get output for each recipient. - -You can only use this parameter with the Identity parameter; you can't use it by itself. - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes) - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-Label.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-Label.md deleted file mode 100644 index 3d88fddbb3..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-Label.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-label -applicable: Office 365 Security & Compliance Center -title: Get-Label -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-Label - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-Label cmdlet to view sensitivity labels in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-Label [[-Identity] <ComplianceRuleIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-Label -``` - -This example returns a summary list of all sensitivity labels in the organization. - -### Example 2 -```powershell -Get-Label -Identity "Engineering Group" | Format-List -``` - -This example returns detailed information for the sensitivity label named Engineering Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-LabelPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-LabelPolicy.md deleted file mode 100644 index bc2f3bb3f0..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-LabelPolicy.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-labelpolicy -applicable: Office 365 Security & Compliance Center -title: Get-LabelPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-LabelPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-LabelPolicy cmdlet to view sensitivity label policies in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-LabelPolicy [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-LabelPolicy | Format-Table Name -``` - -This example returns a summary list of all policies in the organization. - -### Example 2 -```powershell -Get-LabelPolicy -Identity "Engineering Group" | Format-List -``` - -This example returns detailed information for the policy named Engineering Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-OrganizationSegment.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-OrganizationSegment.md deleted file mode 100644 index 1415d3dbc7..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-OrganizationSegment.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-organizationsegment -applicable: Office 365 Security & Compliance Center -title: Get-OrganizationSegment -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-OrganizationSegment - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-OrganizationSegment cmdlet to view organization segments in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### OrganizationSegmentsDefault (Default) -``` -Get-OrganizationSegment [<CommonParameters>] -``` - -### Identity -``` -Get-OrganizationSegment [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -Segments are defined by using certain [attributes](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes) in Azure Active Directory. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-OrganizationSegment | Format-List Name,UserGroupFilter -``` - -This example returns a summary list of all organization segments. - -### Example 2 -```powershell -Get-OrganizationSegment -Identity "Engineering Group" -``` - -This example returns detailed information about the organization segment named Engineering Group. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the organization segment that you want to view. You can use any value that uniquely identifies the segment. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes) - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-ProtectionAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-ProtectionAlert.md deleted file mode 100644 index f9715d8f5c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-ProtectionAlert.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-protectionalert -applicable: Office 365 Security & Compliance Center -title: Get-ProtectionAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-ProtectionAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-ProtectionAlert cmdlet to view alert policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ProtectionAlert [[-Identity] <ComplianceRuleIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-ProtectionAlert | Format-List Name,Category,Comment,NotifyUser -``` - -This example returns a summary list of all alert policies. - -### Example 2 -```powershell -Get-ProtectionAlert -Identity "Malicious Email Campaign" -``` - -This example returns detailed information about the alert policy named Malicious Email Campaign. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-SupervisoryReviewPolicyV2.md deleted file mode 100644 index 4dd51e7368..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-SupervisoryReviewPolicyV2.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-supervisoryreviewpolicyv2 -applicable: Office 365 Security & Compliance Center -title: Get-SupervisoryReviewPolicyV2 -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-SupervisoryReviewPolicyV2 - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-SupervisoryReviewPolicyV2 cmdlet to view supervisory review policies in the Office 365 Security & Compliance Center. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SupervisoryReviewPolicyV2 [[-Identity] <PolicyIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-SupervisoryReviewPolicyV2 -``` - -This example returns a summary list of all supervisory review policies. - -### Example 2 -```powershell -Get-SupervisoryReviewPolicyV2 -Identity "EU Brokers Policy" | Format-List -``` - -This example returns detailed information for the supervisory review policy named EU Brokers Policy. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-SupervisoryReviewRule.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-SupervisoryReviewRule.md deleted file mode 100644 index 1c8f408133..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-SupervisoryReviewRule.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/get-supervisoryreviewrule -applicable: Office 365 Security & Compliance Center -title: Get-SupervisoryReviewRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-SupervisoryReviewRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-SupervisoryReviewRule cmdlet to modify supervisory review rules in the Office 365 Security & Compliance Center. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SupervisoryReviewRule [[-Identity] <ComplianceRuleIdParameter>] [-Policy <PolicyIdParameter>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-SupervisoryReviewRule -``` - -This example returns a summary list of all supervisory review rules. - -### Example 2 -```powershell -Get-SupervisoryReviewRule -Identity "EU Brokers Rule" | Format-List -``` - -This example returns detailed information for the supervisory review rule named EU Brokers Rule. - -### Example 3 -```powershell -Get-SupervisoryReviewRule -Policy "EU Brokers Policy" -``` - -This example returns the rule that assigned to the supervisory review policy named EU Brokers Policy. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Policy -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRule.md b/exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRule.md deleted file mode 100644 index 4ed3c6c869..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Get-TransportRule.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Get-TransportRule - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-TransportRule cmdlet to view transport rules (mail flow rules) in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-TransportRule [[-Identity] <RuleIdParameter>] [-DomainController <Fqdn>] - [-State <RuleState>] [-DlpPolicy <String>] - [-Filter <String>] [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -On Mailbox servers, this cmdlet returns all rules in the Exchange organization that are stored in Active Directory. On an Edge Transport server, this cmdlet only returns rules that are configured on the local server. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-TransportRule -``` - -This example returns a summary list of all rules in your organization. - -### Example 2 -```powershell -Get-TransportRule "Ethical Wall - Sales and Brokerage Departments" | Format-List -``` - -This example returns detailed information for the rule named "Ethical Wall - Sales and Brokerage Departments". - -For more information about pipelining, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines). For more information about how to work with the output of a command, see [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). - -### Example 3 -```powershell -Get-TransportRule -DlpPolicy "PII (U.S.)" -``` - -This example returns a summary list of the rules that enforce the DLP policy named PII (U.S.) in your organization. - -### Example 4 -```powershell -Get-TransportRule | Where {$_.DlpPolicy -ne $null} -``` - -This example returns a summary list of all rules that enforce DLP policies in your organization. - -## PARAMETERS - -### -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. - -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -State -The State parameter specifies filters the results by enabled or disabled rules. Valid values are: - -- Enabled: Only enabled rules are returned in the results. - -- Disabled: Only disabled rules are returned in the results. - -If you don't use this parameter, the command returns all rules, both enabled and disabled. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DlpPolicy -The DlpPolicy parameter filters the results by the named of the specified data loss prevention (DLP) policy. If the value contains spaces, enclose the value in quotation marks ("). - -DLP policies in your organization allow you to prevent unintentional disclosure of sensitive information. Each DLP policy is enforced using a set of transport rules. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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*'"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance/Import-JournalRuleCollection.md b/exchange/exchange-ps/exchange/policy-and-compliance/Import-JournalRuleCollection.md deleted file mode 100644 index 50fe0fc354..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Import-JournalRuleCollection.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/import-journalrulecollection -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Import-JournalRuleCollection -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Import-JournalRuleCollection - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Import-JournalRuleCollection cmdlet to import journal rules from an XML file. You can import a journal rule collection you previously exported as a backup, or import rules you exported from an older version of Exchange. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Import-JournalRuleCollection [-FileData] <Byte[]> [[-Identity] <RuleIdParameter>] [-Confirm] - [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Import-JournalRuleCollection cmdlet imports a journal rule collection you previously exported. - -Importing a journal rule collection from an XML file removes or overwrites all pre-existing journal rules in your organization. Make sure that you have a backup of your current journal rule collection before you import and overwrite your current journal rules. - -Importing file data is a two-step process. First you must load the data to a variable using the Get-Content cmdlet, and then use that variable to transmit the data to the cmdlet. - -For more information about how to export a journal rule collection to an XML file, see [Export-JournalRuleCollection](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/export-journalrulecollection). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -[Byte[]]$Data = Get-Content -Path "C:\JournalRules\ExportedJournalRules.xml" -Encoding Byte -ReadCount 0; Import-JournalRuleCollection -FileData $Data -``` - -This example imports journal rules from the XML file ExportedJournalRules.xml in a two-step process. - -The first step retrieves journal rules from the previously exported XML file ExportedJournalRules.xml using the Get-Content cmdlet, and then stores the results in the variable $Data. The second step retrieves data from the variable $Data and imports journal rules to your organization, overwriting existing journal rules. - -## PARAMETERS - -### -FileData -The FileData parameter specifies the variable name that contains the content of the XML file. - -A valid value for this parameter requires you to read the file to a byte-encoded object using the Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\). - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance/Import-TransportRuleCollection.md b/exchange/exchange-ps/exchange/policy-and-compliance/Import-TransportRuleCollection.md deleted file mode 100644 index ee35e24048..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Import-TransportRuleCollection.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Import-TransportRuleCollection - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Import-TransportRuleCollection cmdlet to import a transport rule collection. You can import a rule collection you previously exported as a backup, or import rules that you've exported from an older version of Exchange. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Import-TransportRuleCollection [-FileData] <Byte[]> - [-Confirm] - [-DomainController <Fqdn>] - [-Force] - [[-Identity] <RuleIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Importing a transport rule collection from an XML file removes or overwrites all pre-existing transport rules that were defined in your organization. Make sure that you have a backup of your current transport rule collection before you import and overwrite your current transport rules. - -Importing file data is a two-step process. First you must load the data to a variable using the Get-Content cmdlet, and then use that variable to transmit the data to the cmdlet. - -For information about how to export a transport rule collection to an XML file, see [Export-TransportRuleCollection](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/export-transportrulecollection). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -[Byte[]]$Data = Get-Content -Path "C:\TransportRules\ExportedRules.xml" -Encoding Byte -ReadCount 0; Import-TransportRuleCollection -FileData $Data -``` - -This example imports a transport rule collection from the XML file named ExportedRules.xml in the C:\\TransportRules folder. - -**Note**: In PowerShell 6.0 or later, replace `-Encoding Byte` with `-AsByteStream`. - -## PARAMETERS - -### -FileData -The FileData parameter specifies the variable name that contains the content of the XML file. The content is retrieved using the Get-Content cmdlet. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies that the command will override any errors or warnings encountered during the import operation. 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, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -This cmdlet is available only in on-premises Exchange, and is only functional in Exchange Server 2010. - -The Identity parameter specifies the transport rule to be imported. Use either the GUID or the name of the 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 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/policy-and-compliance/Install-UnifiedCompliancePrerequisite.md b/exchange/exchange-ps/exchange/policy-and-compliance/Install-UnifiedCompliancePrerequisite.md deleted file mode 100644 index 4817cbd85c..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Install-UnifiedCompliancePrerequisite.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/install-unifiedcomplianceprerequisite -applicable: Office 365 Security & Compliance Center -title: Install-UnifiedCompliancePrerequisite -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Install-UnifiedCompliancePrerequisite - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Install-UnifiedCompliancePrerequisite cmdlet to view, create, or configure the Compliance Policy Center in Microsoft SharePoint Online. The Compliance Policy Center is a site collection that's used by the Security & Compliance Center to store preservation policies that act on content in SharePoint Online sites. - -Typically, you don't need to run this cmdlet. You use this cmdlet for troubleshooting and diagnostics. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Initialize -``` -Install-UnifiedCompliancePrerequisite [-ForceInitialize] [-PolicyCenterSiteOwner <SmtpAddress>] - [<CommonParameters>] -``` - -### LoadOnly -``` -Install-UnifiedCompliancePrerequisite [-LoadOnly] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the following information about the Compliance Policy Center: - -- SharepointRootSiteUrl: This value is typically https://\<domain\>.sharepoint.com/. - -- SharepointTenantAdminUrl: This value uses the format https://\<domain\>-admin.sharepoint.com/. - -- SharepointSuccessInitializedUtc: The time that the Compliance Policy Center was last initialized in coordinated universal time (UTC). - -- SharepointPolicyCenterSiteUrl: This value is typically https://\<domain\>.sharepoint.com/sites/compliancepolicycenter. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Install-UnifiedCompliancePrerequisite -``` - -This example creates the Compliance Policy Center in SharePoint Online. If it has already been created, the command displays the current configuration information. - -### Example 2 -```powershell -Install-UnifiedCompliancePrerequisite -LoadOnly -``` - -This example loads the Compliance Policy Center using the current settings. - -### Example 3 -```powershell -Install-UnifiedCompliancePrerequisite -ForceInitialize -``` - -This example recreates the Compliance Policy Center, even if the site has already been created. - -## PARAMETERS - -### -ForceInitialize -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. - -```yaml -Type: SwitchParameter -Parameter Sets: Initialize -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoadOnly -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. - -```yaml -Type: SwitchParameter -Parameter Sets: LoadOnly -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyCenterSiteOwner -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-ActivityAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-ActivityAlert.md deleted file mode 100644 index 8067bda9fe..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-ActivityAlert.md +++ /dev/null @@ -1,583 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-activityalert -applicable: Office 365 Security & Compliance Center -title: New-ActivityAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-ActivityAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-ActivityAlert cmdlet to create activity alerts in the Security & Compliance Center. Activity alerts send you email notifications when users perform specific activities in Office 365. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnomalousOperationAuditAlert -``` -New-ActivityAlert -Multiplier <Double> -Name <String> -NotifyUser <MultiValuedProperty> [-Operation <MultiValuedProperty>] -Type <AlertType> - [-Category <AlertRuleCategory>] - [-Condition <String>] - [-Confirm] - [-Description <String>] - [-Disabled <Boolean>] - [-DomainController <Fqdn>] - [-EmailCulture <CultureInfo>] - [-RecordType <AuditRecordType>] - [-ScopeLevel <AlertScopeLevel>] - [-Severity <RuleSeverity>] - [-UserId <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### Default -``` -New-ActivityAlert -Name <String> -NotifyUser <MultiValuedProperty> -Operation <MultiValuedProperty> [-Type <AlertType>] - [-Category <AlertRuleCategory>] - [-Confirm] - [-Description <String>] - [-Disabled <Boolean>] - [-DomainController <Fqdn>] - [-EmailCulture <CultureInfo>] - [-RecordType <AuditRecordType>] - [-Severity <RuleSeverity>] - [-UserId <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### SimpleAggregationAuditAlert -``` -New-ActivityAlert -Name <String> -NotifyUser <MultiValuedProperty> [-Operation <MultiValuedProperty>] -Threshold <Int32> -TimeWindow <Int32> -Type <AlertType> - [-Category <AlertRuleCategory>] - [-Condition <String>] - [-Confirm] - [-Description <String>] - [-Disabled <Boolean>] - [-DomainController <Fqdn>] - [-EmailCulture <CultureInfo>] - [-RecordType <AuditRecordType>] - [-ScopeLevel <AlertScopeLevel>] - [-Severity <RuleSeverity>] - [-UserId <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -### ElevationOfPrivilegeAuditAlert -``` -New-ActivityAlert -Name <String> -NotifyUser <MultiValuedProperty> -Type <AlertType> - [-Category <AlertRuleCategory>] - [-Confirm] - [-Description <String>] - [-Disabled <Boolean>] - [-DomainController <Fqdn>] - [-EmailCulture <CultureInfo>] - [-RecordType <AuditRecordType>] - [-Severity <RuleSeverity>] - [-UserId <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ActivityAlert -Name "External Sharing Alert" -Operation sharinginvitationcreated -NotifyUser chrisda@contoso.com,michelle@contoso.com -UserId laura@contoso.com,julia@contoso.com -Description "Notification for external sharing events by laura@contoso.com and julia@contoso.com" -``` - -This example creates a new activity alert named External Sharing Alert that has the following properties: - -- Operation: sharinginvitationcreated. - -- NotifyUser: chrisda@contoso.com and michelle@contoso.com. - -- UserId: laura@contoso.com and julia@contoso.com. - -- Description: Notification for external sharing events by laura@contoso.com and julia@contoso.com. - -## PARAMETERS - -### -Multiplier -The Multiplier parameter specifies the number of events that trigger an activity alert. The value of this parameter indicates a multiplier from a baseline value. - -You can only use this parameter with the Type parameter value AnomalousAggregation. - -```yaml -Type: Double -Parameter Sets: AnomalousOperationAuditAlert -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies the unique name of the activity alert. 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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUser -The NotifyUser parameter specifies the email addressesfor notification messages. You can specify internal and external email addresses. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operation -The Operation parameter specifies the activity that triggers an activity alert. - -A valid value for this parameter is an activity that's available in the Office 365 audit log. For a description of these activities, see [Audited activities](https://go.microsoft.com/fwlink/p/?LinkId=824986). - -Although this parameter is technically capable of accepting multiple values separated by commas, multiple values don't work. - -You can't use this parameter if the Type parameter value is ElevationOfPrivilege. - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: MultiValuedProperty -Parameter Sets: AnomalousOperationAuditAlert, SimpleAggregationAuditAlert -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -The Threshold parameter specifies the number of events that trigger an activity alert in the time interval that's specified by the TimeWindow parameter. The minimum value for this parameter is 3. - -You can only use this parameter with the Type parameter value SimpleAggregation. - -```yaml -Type: Int32 -Parameter Sets: SimpleAggregationAuditAlert -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeWindow -The TimeWindow parameter specifies the time window in minutes that's used by the Threshold parameter. - -You can only use this parameter with the Type parameter value SimpleAggregation. - -```yaml -Type: Int32 -Parameter Sets: SimpleAggregationAuditAlert -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -The Type parameter specifies the type alert. Valid values are: - -- Custom: An alert is created for the activities you specify with the Operation parameter. Typically, you don't need to use this value (if you don't use the Type parameter, and you specify the activities with the Operations parameter, the value Custom is automatically added to the Type property). - -- ElevationOfPrivilege: An alert is created for a predefined list of elevation of privilege activities (Operation parameter values). The activities are Add-RoleGroupMember, New-ManagementRoleAssignment, Add member to role., Update-RoleGroupMember, New-RoleGroup, Set-RoleGroup, Set-Mailbox, and Set-ManagementRoleEntry. You can't use the Operation parameter when you use the ElevationOfPrivilege value (on the New-ActivityAlert or Set-ActivityAlert cmdlets). - -- SimpleAggregation: An alert is created based on the activities defined by the Operation and Condition parameters, the number of activities specified by the Threshold parameter, and the time period specified by the TimeWindow parameter. - -- AnomalousAggregation: An alert is created based the activities defined by the Operation and Condition parameters, and the number of activities specified by the Multiplier parameter. - -Note: You can't change the Type value in an existing activity alert. - -```yaml -Type: AlertType -Parameter Sets: AnomalousOperationAuditAlert, SimpleAggregationAuditAlert, ElevationOfPrivilegeAuditAlert -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: AlertType -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Category -The Category parameter specifies a category for the activity alert. Valid values are: - -- None (This is the default value) - -- DataLossPrevention - -- ThreatManagement - -- DataGovernance - -- AccessGovernance - -- Others - -```yaml -Type: AlertRuleCategory -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Condition -The Condition parameter specifies filter conditions for event aggregation. - -```yaml -Type: String -Parameter Sets: AnomalousOperationAuditAlert, SimpleAggregationAuditAlert -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -The Description parameter specifies an optional description for the activity alert. If the value contains spaces, enclose the value in quotation marks ("). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter specifies whether the activity alert is enabled or disabled. Valid values are: - -- $true: The activity alert is disabled. - -- $false: The activity alert is enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailCulture -The EmailCulture parameter specifies the language of the notification email 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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordType -The RecordType parameter specifies a record type label for the activity alert. Valid values are: - -- AeD - -- AzureActiveDirectory - -- AzureActiveDirectoryAccountLogon - -- AzureActiveDirectoryStsLogon - -- ComplianceDLPExchange - -- ComplianceDLPSharePoint - -- CRM - -- DataCenterSecurityCmdlet - -- Discovery - -- ExchangeAdmin - -- ExchangeAggregatedOperation - -- ExchangeItem - -- ExchangeItemGroup - -- MicrosoftTeams - -- OneDrive - -- PowerBIAudit - -- SecurityComplianceAlerts - -- SecurityComplianceCenterEOPCmdlet - -- SecurityComplianceInsights - -- SharePoint - -- SharePointFileOperation - -- SharePointListOperation - -- SharePointSharingOperation - -- SkypeForBusinessCmdlets - -- SkypeForBusinessPSTNUsage - -- SkypeForBusinessUsersBlocked - -- Sway - -- ThreatIntelligence - -- ThreatIntelligenceAtpContent - -- ThreatIntelligenceUrl - -- WorkplaceAnalytics - -- Yammer - -You can't use this parameter when the value of the Type parameter is ElevationOfPrivilege. - -```yaml -Type: AuditRecordType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScopeLevel -The ScopeLevel parameter specifies the scope for activity alerts that use the Type parameter values SimpleAggregation or AnomalousAggregation. Valid values are: - -- SingleUser (This is the default value) - -- AllUsers - -```yaml -Type: AlertScopeLevel -Parameter Sets: AnomalousOperationAuditAlert, SimpleAggregationAuditAlert -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Severity -The Severity parameter specifies a severity level for the activity alert. Valid values are: - -- None - -- Low (This is the default value) - -- Medium - -- High - -```yaml -Type: RuleSeverity -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserId -The UserId parameter specifies who you want to monitor. - -- If you specify a user's email address, you'll receive an email notification when the user performs the specified activity. You can specify multiple email addresses separated by commas. - -- If this parameter is blank ($null), you'll receive an email notification when any user in your organization performs the specified activity. - -You can only use this parameter with the Type parameter values Custom or ElevationOfPrivilege. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-InformationBarrierPolicy.md deleted file mode 100644 index 0399f14280..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-InformationBarrierPolicy.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy -applicable: Office 365 Security & Compliance Center -title: New-InformationBarrierPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-InformationBarrierPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-InformationBarrierPolicy cmdlet to create information barrier policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### InformationBarrierDefault (Default) -``` -New-InformationBarrierPolicy [-Name] <String> -AssignedSegment <String> - [-Comment <String>] - [-Confirm] - [-State <EopInformationBarrierPolicyState>] - [-WhatIf] [<CommonParameters>] -``` - -### OrganizationSegmentsAllowed -``` -New-InformationBarrierPolicy [-Name] <String> -AssignedSegment <String> -SegmentsAllowed <MultiValuedProperty> - [-Comment <String>] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### OrganizationSegmentsBlocked -``` -New-InformationBarrierPolicy [-Name] <String> -AssignedSegment <String> -SegmentsBlocked <MultiValuedProperty> - [-Comment <String>] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -For more information, see [Information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-InformationBarrierPolicy -Name "Sales-Research" -AssignedSegment "Sales" -SegmentsBlocked "Research" -State Inactive -``` - -This example creates an inactive policy named *Sales-Research* for a segment named *Sales*. When active and applied, this policy prevents people in *Sales* from communicating with people in the segment named *Research*. - -### Example 2 -```powershell -New-InformationBarrierPolicy -Name "Manufacturing-HR" -AssignedSegment "Manufacturing" -SegmentsAllowed "HR" -State Inactive -``` - -This example creates an inactive policy named *Manufacturing-HR* for a segment named *Manufacturing*. When active and applied, this policy allows people in *Manufacturing* to communicate only with people in the segment named *HR*. (In this example, Manufacturing can't communicate with users who aren't in HR.) - -### Example 3 -```powershell -New-InformationBarrierPolicy -Name "Research-HRManufacturing" -AssignedSegment "Research" -SegmentsAllowed "HR","Manufacturing" -State Inactive -``` - -This example creates a policy that allows the *Research* segment to communicate with only *HR* and *Manufacturing*. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignedSegment -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SegmentAllowedFilter -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: OrganizationSegmentAllowedFilter -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SegmentsAllowed -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"). - -You can't use this parameter with the SegmentsBlocked parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: OrganizationSegmentsAllowed -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SegmentsBlocked -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"). - -You can't use this parameter with the SegmentsAllowed parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: OrganizationSegmentsBlocked -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State -The State parameter specifies whether the information barrier policy is active or inactive. Valid values are: - -- Active - -- Inactive (This is the default value.) - -```yaml -Type: EopInformationBarrierPolicyState -Parameter Sets: (All) -Aliases: -Accepted values: Inactive, Active -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-Label.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-Label.md deleted file mode 100644 index 809068000f..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-Label.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-label -applicable: Office 365 Security & Compliance Center -title: New-Label -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-Label - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-Label cmdlet to create sensitivity labels in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-Label [-Name] <String> -DisplayName <String> - [-AdvancedSettings <PswsHashtable>] - [-Comment <String>] - [-Confirm] - [-LocaleSettings <<MultiValuedProperty>] - [-ParentId <ComplianceRuleIdParameter>] - [-Tooltip <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-Label -DisplayName "My New label" -Name "New Label" -``` - -This example create a new label named "New Label" with a display name "My New Label". - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the display name for the sensitivity label. The display name appears in the Microsoft Office and is used by Outlook users to select the appropriate sensitivity label before they send a message. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdvancedSettings -The AdvancedSettings parameter enables client-specific features and capabilities on the sensitivity label. The settings that you configure with this parameter only affect apps that are designed for the setting. For more information, see [How to configure advanced settings for the client by using Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations#how-to-configure-advanced-settings-for-the-client-by-using-office-365-security--compliance-center-powershell). - -```yaml -Type: PswsHashtable -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocaleSettings -The LocaleSettings parameter specifies one or more localized label name 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"}]} - -- Label Tooltips: {"localeKey":"Tooltip","Settings":[{"Key":"en-us","Value":"English Tooltip"},{"Key":"de-de",Value":"Deutscher Tooltip"},{"Key":"es-es","Value":"Tooltip Español"}]} - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ParentId -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tooltip -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-LabelPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-LabelPolicy.md deleted file mode 100644 index b92a4095b6..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-LabelPolicy.md +++ /dev/null @@ -1,297 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-labelpolicy -applicable: Office 365 Security & Compliance Center -title: New-LabelPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-LabelPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-LabelPolicy cmdlet to view sensitivity label policies in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-LabelPolicy -Name <String> -Labels <MultiValuedProperty> - [-AdvancedSettings <PswsHashtable>] - [-Comment <String>] - [-Confirm] - [-ExchangeLocationLocation <MultiValuedProperty>] - [-ExchangeLocationException <MultiValuedProperty>] - [-ModernGroupLocation <MultiValuedProperty>] - [-ModernGroupLocationException <MultiValuedProperty>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-LabelPolicy -Name "Research and Development" -Labels "R and D","R and D Management" -``` - -This example creates the sensitivity label policy named Research and Development that contains sensitivity labels named R and D and R and D Management. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Labels -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 - -- Distinguished name (DN) - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdvancedSettings -The AdvancedSettings parameter enables client-specific features and capabilities on the sensitivity label policy. The settings that you configure with this parameter only affect apps that are designed for the setting. For more information, see [How to configure advanced settings for the client by using Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations#how-to-configure-advanced-settings-for-the-client-by-using-office-365-security--compliance-center-powershell). - -```yaml -Type: PswsHashtable -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocation -The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -- The value All for all mailboxes. You can only use this value by itself. - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeLocationException -The ExchangeLocationException parameter specifies the mailboxes to exclude when you use the value All for the ExchangeLocation parameter. Valid values are: - -- A mailbox - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModernGroupLocation -The ModernGroupLocation parameter specifies the Office 365 groups to include in the policy. Valid values are: - -- An Office 365 Group - -- The value All for all Office 365 groups. You can only use this value by itself. - -To identify the Office 365 Group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModernGroupLocationException -The ModernGroupLocationException parameter specifies the Office 365 groups to exclude when you're using the value All for the ModernGroupLocation parameter. - -You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Default -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-OrganizationSegment.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-OrganizationSegment.md deleted file mode 100644 index 78d07dd144..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-OrganizationSegment.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-organizationsegment -applicable: Office 365 Security & Compliance Center -title: New-OrganizationSegment -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-OrganizationSegment - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-OrganizationSegment cmdlet to create organization segments for use with information barrier policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-OrganizationSegment [-Name] <String> -UserGroupFilter <String> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -For more information about the filterable attributes that you can use to define segments, see [Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-OrganizationSegment -Name "HR" -UserGroupFilter "Department -eq 'HR'" -``` - -In this example, a segment called HR is defined using HR, a value in the Department attribute. - -### Example 2 -```powershell -New-OrganizationSegment -Name "NotSales" -UserGroupFilter "Department -ne 'Sales'" -``` - -In this example, we defined a segment called NotSales that includes everyone who is not in Sales. The "-ne" portion of the cmdlet refers to "not equals." - -### Example 3 -```powershell -New-OrganizationSegment -Name "LocalFTE" -UserGroupFilter "Location -eq 'Local'" -and "Position -ne 'Temporary'" -``` - -In this example, we defined a segment called LocalFTE that includes people who are locally located and whose positions are not listed as Temporary. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserGroupFilter -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. - -- Property is a filterable property. For more information, see [Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -Use the same property for all of your segments, and verify that your segments don't overlap (a user must be assigned to only one segment). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes) - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-ProtectionAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-ProtectionAlert.md deleted file mode 100644 index 7948dd5722..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-ProtectionAlert.md +++ /dev/null @@ -1,576 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-protectionalert -applicable: Office 365 Security & Compliance Center -title: New-ProtectionAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-ProtectionAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-ProtectionAlert cmdlet to create alert policies in the Security & Compliance Center. Alert policies contain conditions that define the user activities to monitor, and the notification options for email alerts and entries in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-ProtectionAlert - -Category <AlertRuleCategory> - -Name <String> -NotifyUser <MultiValuedProperty> -ThreatType <ThreatAlertType> - [-AggregationType <AlertAggregationType>] [-AlertBy <MultiValuedProperty>] - [-AlertFor <MultiValuedProperty>] [-Comment <String>] [-Confirm] [-Description <String>] - [-Disabled <Boolean>] [-Filter <String>] [-NotificationCulture <CultureInfo>] - [-NotifyUserOnFilterMatch <Boolean>] [-NotifyUserSuppressionExpiryDate <DateTime>] - [-NotifyUserThrottleThreshold <Int32>] [-NotifyUserThrottleWindow <Int32>] [-Operation <MultiValuedProperty>] - [-Severity <RuleSeverity>] [-Threshold <Int32>] [-TimeWindow <Int32>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-ProtectionAlert -Name "Content search deleted" -Category Others -NotifyUser admin@contoso.com -ThreatType Activity -Operation SearchRemoved -Description "Custom alert policy to track when content searches are deleted" -AggregationType None -``` - -This example creates an alert policy that triggers an alert whenever anyone in the organization deletes a Content Search in the Office 365 Security & Compliance Center. - -## PARAMETERS - -### -Category -The Category parameter specifies a category for the alert policy. Valid values are: - -- AccessGovernance - -- DataGovernance - -- DataLossPrevention - -- ThreatManagement - -- Others - -When an activity occurs that matches the conditions of the alert policy, the alert that's generated is tagged with the category that's specified by this parameter. This allows you to track and manage alerts that have the same category setting - -```yaml -Type: AlertRuleCategory -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUser -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThreatType -The ThreatType parameter specifies the type of activities that are monitored by the alert policy. Valid values are: - -- Activity - -- Malware - -The value that you select for this parameter determines the values you can use for the AlertBy, Filter, and Operation parameters. - -You can't change this value after you create the alert policy. - -```yaml -Type: ThreatAlertType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AggregationType -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. - -- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. - -- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Office 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. - -```yaml -Type: AlertAggregationType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlertBy -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. - -- Malware: Valid values are Mail.Recipient or Mail.ThreatName. - -You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlertFor -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter enables or disables the alert policy. Valid values are: - -- $true: The alert policy is disabled. - -- $false: The alert policy is enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical `-and` operator (for example, `"Criteria1 -and Criteria2"`). - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -The filterable properties are: - -Activity - -- Activity.ClientIp - -- Activity.CreationTime - -- Activity.Item - -- Activity.ItemType - -- Activity.Operation - -- Activity.ResultStatus - -- Activity.Scope - -- Activity.SiteUrl - -- Activity.SourceFileExtension - -- Activity.SourceFileName - -- Activity.TargetUserOrGroupType - -- Activity.UserAgent - -- Activity.UserId - -- Activity.UserType - -- Activity.Workload - -Malware - -- Mail:AttachmentExtensions - -- Mail:AttachmentNames - -- Mail:CreationTime - -- Mail:DeliveryStatus - -- Mail:Direction - -- Mail:From - -- Mail:FromDomain - -- Mail:InternetMessageId - -- Mail:IsIntraOrgSpoof - -- Mail:IsMalware - -- Mail:IsSpam - -- Mail:IsThreat - -- Mail:Language - -- Mail:Recipient - -- Mail:Scl - -- Mail:SenderCountry - -- Mail:SenderIpAddress - -- Mail:Subject - -- Mail:TenantId - -- Mail:ThreatName - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationCulture -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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserOnFilterMatch -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). - -- $false: Alerts are triggered according to the specified aggregation type. This is the default value. - -You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserSuppressionExpiryDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserThrottleThreshold -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. - -- The value $null. This is the default value (no maximum number of notifications for an alert). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserThrottleWindow -The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - -- An integer. - -- The value $null. This is the default value (no interval for notification throttling). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operation -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://go.microsoft.com/fwlink/p/?LinkId=824986). - -You can specify multiple values separated by commas. - -You can only use this parameter when the ThreatType parameter has the value Activity. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Severity -The Severity parameter specifies the severity of the detection. Valid values are: - -- Low (This is the default value) - -- Medium - -- High - -```yaml -Type: RuleSeverity -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -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. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeWindow -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. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-SupervisoryReviewPolicyV2.md deleted file mode 100644 index 7afbc6ae7f..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-SupervisoryReviewPolicyV2.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-supervisoryreviewpolicyv2 -applicable: Office 365 Security & Compliance Center -title: New-SupervisoryReviewPolicyV2 -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-SupervisoryReviewPolicyV2 - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-SupervisoryReviewPolicyV2 cmdlet to create supervisory review policies in the Office 365 Security & Compliance Center. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-SupervisoryReviewPolicyV2 [-Name] <String> -Reviewers <String[]> [-Comment <String>] [-Confirm] [-Force] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-SupervisoryReviewPolicyV2 -Name "EU Brokers Policy" -Reviewers laura@contoso.com,julia@contoso.com -Comment "Created by the compliance team" -``` - -This example creates a new supervisory review policy named EU Brokers Policy. - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reviewers -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: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/New-SupervisoryReviewRule.md b/exchange/exchange-ps/exchange/policy-and-compliance/New-SupervisoryReviewRule.md deleted file mode 100644 index ee3edf1dd0..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/New-SupervisoryReviewRule.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-supervisoryreviewrule -applicable: Office 365 Security & Compliance Center -title: New-SupervisoryReviewRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# New-SupervisoryReviewRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the New-SupervisoryReviewRule cmdlet to create supervisory review rules in the Office 365 Security & Compliance Center. Supervisory review lets you define policies that capture communications in your organization so they can be examined by internal or external reviewers. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-SupervisoryReviewRule [-Name] <String> -Policy <PolicyIdParameter> [-Condition <String>] [-Confirm] - [-SamplingRate <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -New-SupervisoryReviewRule -Name "EU Brokers Rule" -Policy "EU Brokers Policy" -SamplingRate 100 -Condition "((NOT(Reviewee:US Compliance)) -AND (Reviewee:EU Brokers) -AND ((trade) -OR (insider trading)) -AND (NOT(approved by the Contoso financial team)))" -``` - -This example creates a new supervisory review rule named EU Brokers Rule with the following settings: - -- Policy: EU Brokers Policy - -- Sampling rate: 100% - -- Conditions: Supervise inbound and outbound communications for members of the EU Brokers group that contain the words trade or insider trading. - -- Exceptions: Exclude supervision for members of the EU Compliance group, or messages that contain the phrase "approved by the Contoso financial team". - -## PARAMETERS - -### -Name -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: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policy -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Condition -The Condition parameter specifies the conditions and exceptions for the rule. This parameter uses the following syntax: - -- User or group communications to supervise: "((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...)". Exceptions use the syntax "(NOT((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...))". - -- Direction: "((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal))". - -- Message contains words: "((\<Word1orPhrase1\>) -OR (\<Word2orPhrase2\>)...)". Exceptions use the syntax "(NOT((\<Word1orPhrase1\>)-OR (\<Word2orPhrase2\>)...))". - -- Any attachment contains words: "((Attachment:\<word1\>) -OR (Attachment:\<word2\>)...)". Exceptions use the syntax "(NOT((Attachment:\<word1\>)-OR (Attachment:\<word2\>)...))". - -- Any attachment has the extension: "((AttachmentName:.\<extension1\>) -OR (AttachmentName:.\<extension2\>)...)". Exceptions use the syntax "(NOT((AttachmentName:.\<extension1\>)-OR (AttachmentName:.\<extension2\>)...))". - -- Message size is larger than: "(MessageSize:\<size in B, KB, MB or GB\>)". For example "(MessageSize:300KB)". Exceptions use the syntax "(NOT(MessageSize:\<size in B, KB, MB or GB\>))". - -- Any attachment is larger than: "(AttachmentSize:\<size in B, KB, MB or GB\>)". For example "(AttachmentSize:3MB)". Exceptions use the syntax "(NOT(AttachmentSize:\<size in B, KB, MB or GB\>))". - -- Parentheses ( ) are required around the whole filter. - -- Separate multiple conditions or exception types with the -AND operator. For example, "((Reviewee:chris@contoso.com) -AND (AttachmentSize:3MB))". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SamplingRate -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-ActivityAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/Remove-ActivityAlert.md deleted file mode 100644 index b95261512b..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-ActivityAlert.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-activityalert -applicable: Office 365 Security & Compliance Center -title: Remove-ActivityAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ActivityAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ActivityAlert cmdlet to remove activity alerts from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ActivityAlert [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ActivityAlert -Identity "All Mailbox Activities" -``` - -This example removes the activity alert named All Mailbox Activities. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the activity alert that you want to remove. You can use any value that uniquely identifies the activity alert. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/Remove-InformationBarrierPolicy.md deleted file mode 100644 index b9b60de300..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-InformationBarrierPolicy.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-informationbarrierpolicy -applicable: Office 365 Security & Compliance Center -title: Remove-InformationBarrierPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-InformationBarrierPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-InformationBarrierPolicy cmdlet to remove information barrier policies from the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-InformationBarrierPolicy [-Identity] <PolicyIdParameter> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -For more information, see [Information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-InformationBarrierPolicy -Identity HR-Sales -``` - -This example removes the information barrier policy named HR-Sales. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-Label.md b/exchange/exchange-ps/exchange/policy-and-compliance/Remove-Label.md deleted file mode 100644 index 8c56aa40f0..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-Label.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-label -applicable: Office 365 Security & Compliance Center -title: Remove-Label -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-Label - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-Label cmdlet to remove sensitivity labels from your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-Label [-Identity] <ComplianceRuleIdParameter> - [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-Label -Identity "Marketing Group" -``` - -This example removes the sensitivity label named Marketing Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-LabelPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/Remove-LabelPolicy.md deleted file mode 100644 index 6e2be475c5..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-LabelPolicy.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-labelpolicy -applicable: Office 365 Security & Compliance Center -title: Remove-LabelPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-LabelPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-LabelPolicies cmdlet to remove sensitivity label policies from your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-LabelPolicy [-Identity] <PolicyIdParameter> - [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-LabelPolicy -Identity "Marketing Group" -``` - -This example removes the policy named Marketing Group. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-OrganizationSegment.md b/exchange/exchange-ps/exchange/policy-and-compliance/Remove-OrganizationSegment.md deleted file mode 100644 index 439e159e52..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-OrganizationSegment.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-organizationsegment -applicable: Office 365 Security & Compliance Center -title: Remove-OrganizationSegment -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-OrganizationSegment - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-OrganizationSegment cmdlet to remove organization segments from the Office 365 Security & Compliance Center.. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-OrganizationSegment [-Identity] <PolicyIdParameter> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-OrganizationSegment -Identity "Engineering Group" -``` - -This example removes the organization segment named Engineering Group. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes) - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-ProtectionAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/Remove-ProtectionAlert.md deleted file mode 100644 index 28d69d3006..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-ProtectionAlert.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-protectionalert -applicable: Office 365 Security & Compliance Center -title: Remove-ProtectionAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-ProtectionAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-ProtectionAlert cmdlet to remove alert policies from the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ProtectionAlert [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ProtectionAlert -Identity "External User File Activities" -``` - -This example removes the alert policy named External User File Activities. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/policy-and-compliance/Remove-SupervisoryReviewPolicyV2.md deleted file mode 100644 index 1212818dc9..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Remove-SupervisoryReviewPolicyV2.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/remove-supervisoryreviewpolicyv2 -applicable: Office 365 Security & Compliance Center -title: Remove-SupervisoryReviewPolicyV2 -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Remove-SupervisoryReviewPolicyV2 - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Remove-SupervisoryReviewPolicyV2 cmdlet to remove supervisory review policies from the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-SupervisoryReviewPolicyV2 [-Identity] <PolicyIdParameter> [-Confirm] [-ForceDeletion] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Remove-SupervisoryReviewPolicyV2 -Identity "EU Brokers Policy" -``` - -This example removes the supervisory review policy named EU Brokers Policy. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceDeletion -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-ActivityAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-ActivityAlert.md deleted file mode 100644 index fe0fa13ea0..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-ActivityAlert.md +++ /dev/null @@ -1,517 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-activityalert -applicable: Office 365 Security & Compliance Center -title: Set-ActivityAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-ActivityAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-ActivityAlert cmdlet to modify activity alerts in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ActivityAlert [-Identity] <ComplianceRuleIdParameter> - [-Category <AlertRuleCategory>] - [-Condition <String>] [-Confirm] - [-Description <String>] - [-Disabled <Boolean>] - [-DomainController <Fqdn>] - [-EmailCulture <CultureInfo>] - [-Multiplier <Double>] - [-Name <String>] - [-NotifyUser <MultiValuedProperty>] - [-Operation <MultiValuedProperty>] - [-RecordType <AuditRecordType>] - [-ScopeLevel <AlertScopeLevel>] - [-Severity <RuleSeverity>] - [-Threshold <Int32>] - [-TimeWindow <Int32>] - [-UserId <MultiValuedProperty>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -$NU = Get-ActivityAlert "Contoso Elevation of Privilege"; $NU.NotifyUser.Add("chris@fabrikam.com"); Set-ActivityAlert "Contoso Elevation of Privilege" -NotifyUser $NU.NotifyUser -``` - -This example adds the external user chris@fabrikam.com to the list of recipients that email notifications are sent to for the activity alert named Contoso Elevation of Privilege. - -Note: To remove an existing email address from the list of recipients, change the value NotifyUser.Add to NotifyUser.Remove. - -### Example 2 -```powershell -Set-ActivityAlert -Identity "External Sharing Alert" -Disabled $true -``` - -This example disables the existing activity alert named External Sharing Alert. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the activity alert that you want to modify. You can use any value that uniquely identifies the activity alert. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Category -The Category parameter specifies a category for the activity alert. Valid values are: - -- None (This is the default value) - -- DataLossPrevention - -- ThreatManagement - -- DataGovernance - -- AccessGovernance - -- Others - -```yaml -Type: AlertRuleCategory -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Condition -The Condition parameter specifies filter conditions for event aggregation. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -The Description parameter specifies an optional description for the activity alert. If the value contains spaces, enclose the value in quotation marks ("). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter specifies whether the activity alert is enabled or disabled. Valid values are: - -- $true: The activity alert is disabled. - -- $false: The activity alert is enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailCulture -The EmailCulture parameter specifies the language of the notification email 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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Multiplier -The Multiplier parameter specifies the number of events that trigger an activity alert. The value of this parameter indicates a multiplier from a baseline value. - -You can only use this parameter on activity alerts that have the Type property value AnomalousAggregation. - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUser -The NotifyUser parameter specifies the email address of the recipients who will receive the notification emails. You can specify internal and external email addresses. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -To modify the existing list of recipients, see the Examples section. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operation -The Operation parameter specifies the activities that trigger activity alerts. - -A valid value for this parameter is an activity that's available in the Office 365 audit log. For a description of these activities, see [Audited activities](https://go.microsoft.com/fwlink/p/?LinkId=824986). - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -For the syntax that you use to modify an existing list of Operations values, see the Examples section. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordType -The RecordType parameter specifies a record type label for the activity alert. Valid values are: - -- AeD - -- AzureActiveDirectory - -- AzureActiveDirectoryAccountLogon - -- AzureActiveDirectoryStsLogon - -- ComplianceDLPExchange - -- ComplianceDLPSharePoint - -- CRM - -- DataCenterSecurityCmdlet - -- Discovery - -- ExchangeAdmin - -- ExchangeAggregatedOperation - -- ExchangeItem - -- ExchangeItemGroup - -- MicrosoftTeams - -- OneDrive - -- PowerBIAudit - -- SecurityComplianceAlerts - -- SecurityComplianceCenterEOPCmdlet - -- SecurityComplianceInsights - -- SharePoint - -- SharePointFileOperation - -- SharePointListOperation - -- SharePointSharingOperation - -- SkypeForBusinessCmdlets - -- SkypeForBusinessPSTNUsage - -- SkypeForBusinessUsersBlocked - -- Sway - -- ThreatIntelligence - -- ThreatIntelligenceAtpContent - -- ThreatIntelligenceUrl - -- WorkplaceAnalytics - -- Yammer - -You can't use this parameter when the value of the Type parameter is ElevationOfPrivilege. - -```yaml -Type: AuditRecordType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScopeLevel -The ScopeLevel parameter specifies the scope for activity alerts that use the Type parameter values SimpleAggregation or AnomalousAggregation. Valid values are: - -- SingleUser (This is the default value) - -- AllUsers - -```yaml -Type: AlertScopeLevel -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Severity -The Severity parameter specifies a severity level for the activity alert. Valid values are: - -- None - -- Low (This is the default value) - -- Medium - -- High - -```yaml -Type: RuleSeverity -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -The Threshold parameter specifies the number of events that trigger an activity alert in the time interval that's specified by the TimeWindow parameter. The minimum value for this parameter is 3. - -You can only use this parameter on activity alerts that have the Type property value SimpleAggregation. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeWindow -The TimeWindow parameter specifies the time window in minutes that's used by the Threshold parameter. - -You can only use this parameter on activity alerts that have the Type property value SimpleAggregation. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserId -The UserId parameter specifies who you want to monitor. - -- If you specify a user's email address, you'll receive an email notification when the user performs the specified activity. You can specify multiple email addresses separated by commas. - -- If this parameter is blank ($null), you'll receive an email notification when any user in your organization performs the specified activity. - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -You can only use this parameter on activity alerts that have the Type property values Custom or ElevationOfPrivilege. - -For the syntax that you use to modify an existing list of UserId values, see the Examples section. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-InformationBarrierPolicy.md deleted file mode 100644 index e129448103..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-InformationBarrierPolicy.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-informationbarrierpolicy -applicable: Office 365 Security & Compliance Center -title: Set-InformationBarrierPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-InformationBarrierPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-InformationBarrierPolicy cmdlet to modify information barrier policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### OrganizationSegmentsAllowed -``` -Set-InformationBarrierPolicy -Identity <PolicyIdParameter> [-SegmentsAllowed <MultiValuedProperty>] - [-Comment <String>] - [-State <EopInformationBarrierPolicyState>] - [<CommonParameters>] -``` - -### OrganizationSegmentAllowedFilter -``` -Set-InformationBarrierPolicy -Identity <PolicyIdParameter> [-SegmentAllowedFilter <String>] - [-Comment <String>] - [-State <EopInformationBarrierPolicyState>] - [<CommonParameters>] -``` - -### OrganizationSegmentsBlocked -``` -Set-InformationBarrierPolicy -Identity <PolicyIdParameter> [-SegmentsBlocked <MultiValuedProperty>] - [-Comment <String>] - [-State <EopInformationBarrierPolicyState>] - [<CommonParameters>] -``` - -## DESCRIPTION -For more information, see [Information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies). - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-InformationBarrierPolicy -Identity 43c37853-ea10-4b90-a23d-ab8c93772471 -State Active -``` - -This example activates the specified inactive information barrier policy. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SegmentsAllowed -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"). - -You can't use this parameter with the SegmentsBlocked parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: OrganizationSegmentsAllowed -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SegmentAllowedFilter -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: OrganizationSegmentAllowedFilter -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SegmentsBlocked -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"). - -You can't use this parameter with the SegmentsAllowed parameter. - -```yaml -Type: MultiValuedProperty -Parameter Sets: OrganizationSegmentsBlocked -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State -The State parameter specifies whether the information barrier policy is active or inactive. Valid values are: - -- Active - -- Inactive - -```yaml -Type: EopInformationBarrierPolicyState -Parameter Sets: (All) -Aliases: -Accepted values: Inactive, Active -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-Label.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-Label.md deleted file mode 100644 index 4d39be5b61..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-Label.md +++ /dev/null @@ -1,293 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-label -applicable: Office 365 Security & Compliance Center -title: Set-Label -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-Label - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-Label cmdlet to modify sensitivity labels in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-Label [-Identity] <ComplianceRuleIdParameter> - [-AdvancedSettings <PswsHashtable>] - [-Comment <String>] - [-Confirm] - [-Disabled <Boolean>] - [-DisplayName <String>] - [-LocaleSettings <MultiValuedProperty>] - [-NextLabel <ComplianceRuleIdParameter>] - [-ParentId <ComplianceRuleIdParameter>] - [-PreviousLabel <ComplianceRuleIdParameter>] - [-Priority <Int32>] - [-Tooltip <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920).. - -## EXAMPLES - -### Example 1 -```powershell -Set-Label -Identity General -LocaleSettings '{"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"}]}' -``` - -This example sets the localized label name for "General" in different languages (English, German, and Spanish). - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AdvancedSettings -The AdvancedSettings parameter enables client-specific features and capabilities on the sensitivity label. The settings that you configure with this parameter only affect apps that are designed for the setting. For more information, see [How to configure advanced settings for the client by using Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations#how-to-configure-advanced-settings-for-the-client-by-using-office-365-security--compliance-center-powershell). - -```yaml -Type: PswsHashtable -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The disabled parameter specifies whether to enable or disable the sensitivity label. Valid values are: - -- $true: The label is disabled. - -- $False: The label is enabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the display name for the sensitivity label. The display name appears in the Microsoft Office and is used by Outlook users to select the appropriate sensitivity label before they send a message. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocaleSettings -The LocaleSettings parameter specifies one or more localized label name or 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"}]} - -- Label Tooltips: {"localeKey":"Tooltip","Settings":[{"Key":"en-us","Value":"English Tooltip"},{"Key":"de-de","Value":"Deutscher Tooltip"},{"Key":"es-es","Value":"Tooltip Español"}]} - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NextLabel -This parameter is reserved for internal Microsoft use. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ParentId -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviousLabel -This parameter is reserved for internal Microsoft use. - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -The Priority parameter specifies a priority value for the sensitivity label that determines the order of label processing. A lower integer value indicates a higher priority, the value 0 is the highest priority and sensitivity labels can't have the same priority value. - -Valid values and the default value for this parameter depend on the number of existing sensitivity labels. For example, if there are 8 existing labels: - -- Valid priority values for the existing 8 sensitivity labels are from 0 through 7. - -- Valid priority values for a new sensitivity label (the 9th label) are from 0 through 8. - -- The default value for a new sensitivity label (the 9th label) is 8. - -If you modify the priority value of a sensitivity label, the position of the label in the list changes to match the priority value you specify. In other words, if you set the priority value of a sensitivity label to the same value as an existing label, the priority value of the existing sensitivity label and all other lower priority labels after it is increased by 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tooltip -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-LabelPolicy.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-LabelPolicy.md deleted file mode 100644 index 9f0ba417f1..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-LabelPolicy.md +++ /dev/null @@ -1,542 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-labelpolicy -applicable: Office 365 Security & Compliance Center -title: Set-LabelPolicy -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-LabelPolicy - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-Label cmdlet to modify sensitivity label policies in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity -``` -Set-LabelPolicy [-Identity] <PolicyIdParameter> - [-AddExchangeLocation <MultiValuedProperty>] - [-AddExchangeLocationException <MultiValuedProperty>] - [-AddLabels <MultiValuedProperty>] - [-AddModernGroupLocation <MultiValuedProperty>] - [-AddModernGroupLocationException <MultiValuedProperty>] - [-AdvancedSettings <PswsHashtable>] - [-Comment <String>] - [-Confirm] - [-Enabled <Boolean>] - [-NextLabelPolicy <PolicyIdParameter>] - [-RemoveExchangeLocation <MultiValuedProperty>] - [-RemoveExchangeLocationException <MultiValuedProperty>] - [-RemoveLabels <MultiValuedProperty>] - [-RemoveModernGroupLocation <MultiValuedProperty>] - [-RemoveModernGroupLocationException <MultiValuedProperty>] - [<CommonParameters>] -``` - -### RetryDistribution -``` -Set-LabelPolicy [-Identity] <PolicyIdParameter> -RetryDistribution - [-AddLabels <MultiValuedProperty>] - [-AdvancedSettings <PswsHashtable>] - [-Confirm] - [-NextLabelPolicy <PolicyIdParameter>] - [-PreviousLabelPolicy <PolicyIdParameter>] - [-RemoveLabels <MultiValuedProperty>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-LabelPolicy -Identity "Global Policy" -AdvancedSettings @{EnableCustomPermissions="False"} -``` - -This example configures the specified advanced setting for the sensitivity label policy name Global Policy. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the policy that you want to view. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -RetryDistribution -The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint 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. - -```yaml -Type: SwitchParameter -Parameter Sets: RetryDistribution -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocation -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 - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddExchangeLocationException -The AddExchangeLocationException 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 - -- A distribution group or mail-enabled security group - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddLabels -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 - -- Distinguished name (DN) - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddModernGroupLocation -The AddModernGroupLocation parameter specifies the Office 365 groups to add to the list of included Office 365 Groups when you aren't using the value All for the ModernGroupLocation parameter. - -You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddModernGroupLocationException -The AddModernGroupLocationException parameter specifies the Office 365 groups to add to the list of excluded Office 365 Groups when you're using the value All for the ModernGroupLocation parameter. - -You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdvancedSettings -The AdvancedSettings parameter enables client-specific features and capabilities on the sensitivity label policy. The settings that you configure with this parameter only affect apps that are designed for the setting. For more information, see [How to configure advanced settings for the client by using Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations#how-to-configure-advanced-settings-for-the-client-by-using-office-365-security--compliance-center-powershell). - -```yaml -Type: PswsHashtable -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NextLabelPolicy -This parameter is reserved for internal Microsoft use. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviousLabelPolicy -This parameter is reserved for internal Microsoft use. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocation -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 - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveExchangeLocationException -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 - -- A distribution group or mail-enabled security group (all mailboxes that are currently members of the group). - -To specify a mailbox or distribution group, you can use any value that uniquely identifies it. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveLabels -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 - -- Distinguished name (DN) - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveModernGroupLocation -The RemoveModernGroupLocation parameter specifies the Office 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 Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveModernGroupLocationException -The RemoveModernGroupLocationException parameter specifies the Office 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 Office 365 Group. For example: - -- Name - -- Distinguished name (DN) - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: MultiValuedProperty -Parameter Sets: Identity -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-OrganizationSegment.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-OrganizationSegment.md deleted file mode 100644 index dd536dbeae..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-OrganizationSegment.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-organizationsegment -applicable: Office 365 Security & Compliance Center -title: Set-OrganizationSegment -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-OrganizationSegment - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-OrganizationSegment cmdlet to modify organization segments in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-OrganizationSegment [-Identity] <PolicyIdParameter> [-UserGroupFilter <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Segments are defined by using certain [attributes](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes) in Azure Active Directory. - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-OrganizationSegment -Identity c96e0837-c232-4a8a-841e-ef45787d8fcd -UserGroupFilter "Department -eq 'HRDept'" -``` - -In this example, for the segment that has the GUID c96e0837-c232-4a8a-841e-ef45787d8fcd, we updated the department name to "HRDept". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -UserGroupFilter -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. - -- Property is a filterable property. For more information, see [Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -Use the same property for all of your segments, and verify that your segments don't overlap (a user must be assigned to only one segment). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Attributes for information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-attributes) - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-ProtectionAlert.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-ProtectionAlert.md deleted file mode 100644 index 97d6ed0b1d..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-ProtectionAlert.md +++ /dev/null @@ -1,600 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-protectionalert -applicable: Office 365 Security & Compliance Center -title: Set-ProtectionAlert -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-ProtectionAlert - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-ProtectionAlert cmdlet to modify alert policies in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - - -> [!NOTE] -> You cannot use this cmdlet to edit default alert policies. You can only modify alerts you have created using New-ProtectionAlert cmdlet. - -## SYNTAX - -``` -Set-ProtectionAlert [-Identity] <ComplianceRuleIdParameter> - [-AggregationType <AlertAggregationType>] - [-AlertBy <MultiValuedProperty>] - [-AlertFor <MultiValuedProperty>] - [-Category <AlertRuleCategory>] - [-Comment <String>] - [-Confirm] - [-Description <String>] - [-Disabled <Boolean>] - [-Filter <String>] - [-Name <String>] - [-NotificationCulture <CultureInfo>] - [-NotifyUser <MultiValuedProperty>] - [-NotifyUserOnFilterMatch <Boolean>] - [-NotifyUserSuppressionExpiryDate <DateTime>] - [-NotifyUserThrottleThreshold <Int32>] - [-NotifyUserThrottleWindow <Int32>] - [-Operation <MultiValuedProperty>] - [-Severity <RuleSeverity>] - [-Threshold <Int32>] - [-TimeWindow <Int32>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-ProtectionAlert -Identity "Content search deleted" -Severity High -``` - -This example sets the Severity of the detection to High. - -### Example 2 -```powershell -Set-ProtectionAlert -Identity "Content search deleted" -NotifyUserOnFilterMatch:$true -AggregationType SimpleAggregation -Threshold 10 -TimeWindow 120 -``` - -This example modifies an alert so that even though it's configured for aggregated activity, a notification is triggered during a match for the activity. A threshold of 10 detections and a TimeWindow of two hours are also configured in the same command. - - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AggregationType -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. - -- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. - -- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Office 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. - -```yaml -Type: AlertAggregationType -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlertBy -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. - -- Malware: Valid values are Mail.Recipient or Mail.ThreatName. - -You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlertFor -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Category -The Category parameter specifies a category for the alert policy. Valid values are: - -- AccessGovernance - -- DataGovernance - -- DataLossPrevention - -- ThreatManagement - -- Others - -When an activity occurs that matches the conditions of the alert policy, the alert that's generated is tagged with the category that's specified by this parameter. This allows you to track and manage alerts that have the same category setting - -```yaml -Type: AlertRuleCategory -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disabled -The Disabled parameter enables or disables the alert policy. Valid values are: - -- $true: The alert policy is disabled. - -- $false: The alert policy is enabled. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the `-and` logical operator (for example, `"Criteria1 -and Criteria2"`). - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -The filterable properties are: - -Activity - -- Activity.ClientIp - -- Activity.CreationTime - -- Activity.Item - -- Activity.ItemType - -- Activity.Operation - -- Activity.ResultStatus - -- Activity.Scope - -- Activity.SiteUrl - -- Activity.SourceFileExtension - -- Activity.SourceFileName - -- Activity.TargetUserOrGroupType - -- Activity.UserAgent - -- Activity.UserId - -- Activity.UserType - -- Activity.Workload - -Malware - -- Mail:AttachmentExtensions - -- Mail:AttachmentNames - -- Mail:CreationTime - -- Mail:DeliveryStatus - -- Mail:Direction - -- Mail:From - -- Mail:FromDomain - -- Mail:InternetMessageId - -- Mail:IsIntraOrgSpoof - -- Mail:IsMalware - -- Mail:IsSpam - -- Mail:IsThreat - -- Mail:Language - -- Mail:Recipient - -- Mail:Scl - -- Mail:SenderCountry - -- Mail:SenderIpAddress - -- Mail:Subject - -- Mail:TenantId - -- Mail:ThreatName - -You can specify multiple criteria by using the -and comparison operator. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationCulture -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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUser -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserOnFilterMatch -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). - -- $false: Alerts are triggered according to the specified aggregation type. This is the default value. - -You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserSuppressionExpiryDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserThrottleThreshold -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. - -- The value $null. This is the default value (no maximum number of notifications for an alert). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyUserThrottleWindow -The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - -- An integer. - -- The value $null. This is the default value (no interval for notification throttling). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operation -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://go.microsoft.com/fwlink/p/?LinkId=824986). - -You can specify multiple values separated by commas. - -You can only use this parameter when the ThreatType parameter has the value Activity. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Severity -The Severity parameter specifies the severity of the detection. Valid values are: - -- Low (This is the default value) - -- Medium - -- High - -```yaml -Type: RuleSeverity -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -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. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeWindow -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. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-SupervisoryReviewPolicyV2.md deleted file mode 100644 index 7b3b42c9ce..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-SupervisoryReviewPolicyV2.md +++ /dev/null @@ -1,213 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-supervisoryreviewpolicyv2 -applicable: Office 365 Security & Compliance Center -title: Set-SupervisoryReviewPolicyV2 -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-SupervisoryReviewPolicyV2 - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-SupervisoryReviewPolicyV2 cmdlet to modify supervisory review policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-SupervisoryReviewPolicyV2 [-Identity] <PolicyIdParameter> [-AddReviewers <String[]>] [-Comment <String>] - [-Confirm] [-Force] [-RemoveReviewers <String[]>] [-RetentionPeriodInDays <Int32>] [-Reviewers <String[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-SupervisoryReviewPolicyV2 -Identity "EU Brokers" -AddReviewers chris@contoso.com,michelle@contoso.com -Comment "Updated for new EU regulations" -``` - -This example adds reviewers and updates the comment for the supervisory review policy named EU Brokers. - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AddReviewers -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comment -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveReviewers -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionPeriodInDays -The RetentionPeriodInDays parameter specifies the number of days that the messages will be retained for review. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reviewers -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. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Set-SupervisoryReviewRule.md b/exchange/exchange-ps/exchange/policy-and-compliance/Set-SupervisoryReviewRule.md deleted file mode 100644 index 5080af21df..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Set-SupervisoryReviewRule.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-supervisoryreviewrule -applicable: Office 365 Security & Compliance Center -title: Set-SupervisoryReviewRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Set-SupervisoryReviewRule - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Set-SupervisoryReviewRule cmdlet to modify supervisory review rules in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-SupervisoryReviewRule [-Identity] <ComplianceRuleIdParameter> [-Condition <String>] [-Confirm] - [-SamplingRate <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Set-SupervisoryReviewRule -Identity "EU Brokers Rule" -Conditions "((NOT(Reviewee:US Compliance)) -AND (Reviewee:EU Brokers) -AND ((trade) -OR (insider trading)) -AND (NOT(approved by the Contoso financial team)))" -``` - -This example modifies the existing rule named EU Brokers Rule with the following settings: - -- Conditions: Supervise inbound and outbound communications for members of the EU Brokers group that contain the words trade or insider trading. - -- Exceptions: Exclude supervision for members of the EU Compliance group, or messages that contain the phrase "approved by the Contoso financial team". - -## PARAMETERS - -### -Identity -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 - -- Distinguished name (DN) - -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Condition -The Condition parameter specifies the conditions and exceptions for the rule. This parameter uses the following syntax: - -- User or group communications to supervise: "((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...)". Exceptions use the syntax "(NOT((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...))". - -- Direction: "((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal))". - -- Message contains words: "((\<Word1orPhrase1\>) -OR (\<Word2orPhrase2\>)...)". Exceptions use the syntax "(NOT((\<Word1orPhrase1\>) -OR (\<Word2orPhrase2\>)...))". - -- Any attachment contains words: "((Attachment:\<word1\>) -OR (Attachment:\<word2\>)...)". Exceptions use the syntax "(NOT((Attachment:\<word1\>) -OR (Attachment:\<word2\>)...))". - -- Any attachment has the extension: "((AttachmentName:.\<extension1\>) -OR (AttachmentName:.\<extension2\>)...)". Exceptions use the syntax "(NOT((AttachmentName:.\<extension1\>) -OR (AttachmentName:.\<extension2\>)...))". - -- Message size is larger than: "(MessageSize:\<size in B, KB, MB or GB\>)". For example "(MessageSize:300KB)". Exceptions use the syntax "(NOT(MessageSize:\<size in B, KB, MB or GB\>))". - -- Any attachment is larger than: "(AttachmentSize:\<size in B, KB, MB or GB\>)". For example "(AttachmentSize:3MB)". Exceptions use the syntax "(NOT(AttachmentSize:\<size in B, KB, MB or GB\>))". - -- Parentheses ( ) are required around the whole filter. - -- Separate multiple conditions or exception types with the -AND operator. For example, "((Reviewee:chris@contoso.com) -AND (AttachmentSize:3MB))". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SamplingRate -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Start-InformationBarrierPoliciesApplication.md b/exchange/exchange-ps/exchange/policy-and-compliance/Start-InformationBarrierPoliciesApplication.md deleted file mode 100644 index bb08e5341d..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Start-InformationBarrierPoliciesApplication.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/stop-informationbarrierpoliciesapplication -applicable: Office 365 Security & Compliance Center -title: Start-InformationBarrierPoliciesApplication -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Start-InformationBarrierPoliciesApplication - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Start-InformationBarrierPoliciesApplication cmdlet to apply active information barrier policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Start-InformationBarrierPoliciesApplication [[-Identity] <PolicyIdParameter>] - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Start-InformationBarrierPoliciesApplication -``` - -This applies all active information barrier policies. - -## PARAMETERS - -### -Identity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[New-InformationBarrierPolicy](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/new-informationbarrierpolicy) diff --git a/exchange/exchange-ps/exchange/policy-and-compliance/Stop-InformationBarrierPoliciesApplication.md b/exchange/exchange-ps/exchange/policy-and-compliance/Stop-InformationBarrierPoliciesApplication.md deleted file mode 100644 index 5bc3759268..0000000000 --- a/exchange/exchange-ps/exchange/policy-and-compliance/Stop-InformationBarrierPoliciesApplication.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/stop-informationbarrierpoliciesapplication -applicable: Office 365 Security & Compliance Center -title: Stop-InformationBarrierPoliciesApplication -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Stop-InformationBarrierPoliciesApplication - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Stop-InformationBarrierPoliciesApplication cmdlet to stop the process of applying information barrier policies in the Office 365 Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Stop-InformationBarrierPoliciesApplication [-Identity] <PolicyIdParameter> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -InformationBarrierPoliciesApplication -Identity 46237888-12ca-42e3-a541-3fcb7b5231d1 -``` - -This example stops the application of information barrier policies per the policy application with the specified Identity value. - -## PARAMETERS - -### -Identity -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: Office 365 Security & Compliance Center - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch doesn't work in Office 365 Security & Compliance Center PowerShell. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS - -[Define policies for information barriers](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-policies) - -[Edit (or remove) information barrier policies](https://docs.microsoft.com/microsoft-365/compliance/information-barriers-edit-segments-policies) diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Connect-ExchangeOnline.md b/exchange/exchange-ps/exchange/powershell-v2-module/Connect-ExchangeOnline.md deleted file mode 100644 index e4d32b3620..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Connect-ExchangeOnline.md +++ /dev/null @@ -1,369 +0,0 @@ ---- -external help file: ExchangeOnlineManagement-help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/connect-exchangeonline -applicable: Exchange Online -title: Connect-ExchangeOnline -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Connect-ExchangeOnline - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Connect-ExchangeOnline cmdlet in the Exchange Online PowerShell V2 module to connect to an Exchange Online organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Connect-ExchangeOnline - [[-AzureADAuthorizationEndpointUri] <String>] - [-BypassMailboxAnchoring] - [[-ConnectionUri] <String>] - [-Credential <PSCredential>] - [[-DelegatedOrganization] <String>] - [-EnableErrorReporting] - [[-ExchangeEnvironmentName] <ExchangeEnvironment>] - [-LogDirectoryPath <String>] - [-LogLevel <String>] - [-PageSize <UInt32>] - [-Prefix <String>] - [[-PSSessionOption] <PSSessionOption>] - [-ShowProgress <Boolean>] - [-TrackPerformance <Boolean>] - [-UseMultithreading <Boolean>] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet allows you to create a remote PowerShell connection to your Exchange Online organization. You can use this cmdlet to authenticate for the new REST API-backed cmdlets in the Exchange Online PowerShell V2 module, and also for all existing Exchange Online PowerShell cmdlets (remote PowerShell cmdlets). - -## EXAMPLES - -### Example 1 -```powershell -$UserCredential = Get-Credential -Connect-ExchangeOnline -Credential $UserCredential -``` - -The first command gets the user credentials and stores them in the $UserCredential variable. - -The second command connects the current PowerShell session using the credentials in the $UserCredential, which isn't MFA enabled. Note that after the second command is complete, the password key in the $UserCredential variable becomes empty. - -After the Connect-ExchangeOnline command is successful, you can run ExO V2 module cmdlets and older remote PowerShell cmdlets. - -### Example 2 -```powershell -Connect-ExchangeOnline -UserPrincipalName chris@contoso.com -ShowProgress $true -``` - -This command connects the current PowerShell session using chris@contoso.com account, which is MFA enabled. - -After the Connect-ExchangeOnline command is successful, you can run ExO V2 module cmdlets and older remote PowerShell cmdlets. - -## PARAMETERS - -### -AzureADAuthorizationEndpointUri -The AzureADAuthorizationEndpointUri parameter specifies the Azure AD Authorization endpoint Uri that can issue OAuth2 access tokens. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassMailboxAnchoring -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 -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionUri -The ConnectionUri parameter specifies the connection endpoint for the remote PowerShell session. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DelegatedOrganization -The DelegatedOrganization parameter specifies the customer organization that you want to manage (for example, contosoelectronics.onmicrosoft.com). This parameter only works 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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableErrorReporting -The EnableErrorReporting switch enables logging errors to a local file. You don't need to specify a value with this switch. - -By default, it creates 2 files in the %TMP% folder. You can use the LogDirectoryPath parameter to specify the location of the log files. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeEnvironmentName -The ExchangeEnvironmentName specifies the Exchange Online environment. Valid values are: - -- O365China - -- O365Default (this is the default value) - -- O365GermanyCloud - -- O365USGovDoD - -- O365USGovGCCHigh - -```yaml -Type: ExchangeEnvironment -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 3 -Default value: O365Default -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogDirectoryPath -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 ("). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogLevel -The LogLevel parameter specifies the logging level. Possible values are Default and All. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Prefix -The Prefix parameter specifies an alias to add to nouns in the names of older remote PowerShell cmdlets (cmdlet with nouns that don't already start with EXO). A valid value is a text string without spaces, and you can't use the value EXO (this prefix is reserved for PowerShell V2 module cmdlets). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - - -### -PSSessionOption -The PSSessionOption parameter specifies the PowerShell session options to use in your connection to Exchange Online. You store the output of the [New-PSSessionOption](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/new-pssessionoption) command in a variable (for example, `$Options = New-PSSessionOption <Settings>`), and you use the variable name as the value for this parameter (for example, $Options). - -```yaml -Type: PSSessionOption -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowProgress -The ShowProgress parameter shows a visual progress bar in the PowerShell client module. The progress bar shows number of objects received and total number of objects requested. Valid values are: - -- $true: The progress bar is displayed. - -- $false: The progress bar isn't displayed. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrackPerformance -{{ Fill TrackPerformance Description }} - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseMultithreading -The UseMultithreading parameter specifies whether to disable or enable multi-threading in the EXO V2 module Valid values are: - -- $true: Enable multi-threading. This is the default value. - -- $false: Disable multi-threading. Note this value will degrade performance of V2 cmdlets. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -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 the first screen in authentication prompt. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOCasMailbox.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOCasMailbox.md deleted file mode 100644 index 8c08f89b75..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOCasMailbox.md +++ /dev/null @@ -1,362 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exocasmailbox -applicable: Exchange Online -title: Get-EXOCasMailbox -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXOCasMailbox - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-EXOCasMailbox cmdlet to view the Client Access settings that are configured on mailboxes. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity (Default) -``` -Get-EXOCasMailbox - [[-Identity] <String>] - [-Filter <String>] - [-ExternalDirectoryObjectId <Guid>] - [-OrganizationalUnit <String>] - [-Properties <String[]>] - [-PropertySets <PropertySet[]>] - [-ProtocolSettings] - [-ResultSize <Unlimited>] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -### Anr -``` -Get-EXOCasMailbox - [-Anr <String>] - [-Filter <String>] - [-OrganizationalUnit <String>] - [-Properties <String[]>] - [-PropertySets <PropertySet[]>] - [-ProtocolSettings] - [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns a variety of client access settings for one or more mailboxes. These settings include options for Outlook on the web, Exchange ActiveSync, POP3, and IMAP4. - -## EXAMPLES - -### Example 1 -```powershell -Get-EXOCASMailbox -Identity "JeffHay@contoso.com" -``` - -This example returns the values of the following client access settings for the user with Identity Jeffhay@contoso.com: - -- ActiveSyncEnabled - -- EwsEnabled - -- OWAEnabled - -- PopEnabled - -- ImapEnabled - -- MAPIEnabled - -- ECPEnabled - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -Type: String -Parameter Sets: Anr -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Get-EXOCasMailbox property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exocasmailbox-property-sets) and [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mailbox you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -**Note**: This parameter doesn't support Name or Alias values. - -You can't use this parameter with the Anr parameter. - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Properties -The Properties parameter specifies the properties that are returned in the output of this cmdlet. You can specify multiple values separated by commas. Wildcards ( * ) are supported. - -For more information about the available properties, see [Get-EXOCasMailbox property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exocasmailbox-property-sets). - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertySets -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) - -- ActiveSync - -- Ews - -- Imap - -- Mapi - -- Pop - -- ProtocolSettings - -- All - -You can specify multiple values separated by commas. Wildcards ( * ) are supported. - -For more information about the properties that are included in each property set, see [Get-EXOCasMailbox property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exocasmailbox-property-sets). - -```yaml -Type: PropertySet[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProtocolSettings -The ProtocolSettings switch returns the server names, TCP ports and encryption methods for the following settings: - -- ExternalImapSettings - -- InternalImapSettings - -- ExternalPopSettings - -- InternalPopSettings - -- ExternalSmtpSettings - -- InternalSmtpSettings - -To see these values, you need to use a formatting cmdlet. For example, Get-CasMailbox laura@contoso.com -ProtocolSettings | Format-List. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -The following Input parameters are not supported in Get-EXOCasMailbox: - -- IgnoreDefaultScope - -- ReadIsOptimizedForAccessibility - -- SortBy - -- GetImapProtocolLog - -- GetPopProtocolLog - -- SendLogsTo - -## OUTPUTS - -### -The following properties are removed by design from Get-EXOCasMailbox output: - -- RunspaceId - -- Servername - -- OriginatingServer - -- IsValid - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailbox.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailbox.md deleted file mode 100644 index 6ee29ca970..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailbox.md +++ /dev/null @@ -1,516 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailbox -applicable: Exchange Online -title: Get-EXOMailbox -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXOMailbox - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-EXOMailbox cmdlet to view mailbox objects and attributes, populate property pages, or supply mailbox information to other tasks. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity (Default) -``` -Get-EXOMailbox [[-Identity] <String>] - [-Archive] - [-ExternalDirectoryObjectId <Guid>] - [-Filter <String>] - [-InactiveMailboxOnly] - [-IncludeInactiveMailbox] - [-MailboxPlan <String>] - [-OrganizationalUnit <String>] - [-Properties <String[]>] - [-PropertySets <PropertySet[]>] - [-RecipientTypeDetails <String[]>] - [-ResultSize <Unlimited>] - [-SoftDeletedMailbox] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -### Anr -``` -Get-EXOMailbox [-Anr <String>] - [-Archive] - [-Filter <String>] - [-InactiveMailboxOnly] - [-IncludeInactiveMailbox] - [-MailboxPlan <String>] - [-OrganizationalUnit <String>] - [-Properties <String[]>] - [-PropertySets <PropertySet[]>] - [-RecipientTypeDetails <String[]>] - [-ResultSize <Unlimited>] - [-SoftDeletedMailbox] - [<CommonParameters>] -``` - -## DESCRIPTION -By default, this cmdlet returns a summary list (a minimum set of properties) of all mailboxes in your organization. - -## EXAMPLES - -### Example 1 -```powershell -Get-EXOMailbox -ResultSize unlimited -``` - -This example returns a summary list of all mailboxes in the organization, and includes the default set of minimum output properties. To return additional properties, use the Properties and/or PropertySets parameters. - -### Example 2 -```powershell -Get-EXOMailbox -PropertySets Archive -``` - -This example returns the Properties that are defined in Archive property set. For a complete list of these properties, see [Get-EXOMailbox property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exomailbox-property-sets). - - -### Example 3 -```powershell -Get-EXOMailbox -Properties Name,DistinguishedName,Guid -PropertySets Archive,Audit -``` - -This example returns a summary list of all mailboxes in the organization, and includes the following properties: - -- The properties in Archive and Audit property sets. - -- The Name and DistinguishedName properties. - -### Example 4 -```powershell -Get-EXOMailbox -Identity John@contoso.com -Properties DisplayName,EmailAddresses,Alias -``` - -This example returns the specified properties for the mailbox John@contoso.com. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -Type: String -Parameter Sets: Anr -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Archive -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Get-EXOMailbox property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exomailbox-property-sets) and [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mailbox you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Email address - -- GUID - -- External Directory Object ID - -- User Principal Name (UPN) - -**Note**: This parameter doesn't support Name or Alias values. - -You can't use this parameter with the Anr parameter. - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -InactiveMailboxOnly -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. - -To return both active mailboxes and inactive mailboxes in the results, don't use this switch. Instead, use the IncludeInactiveMailbox switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeInactiveMailbox -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. - -To return only inactive mailboxes in the results, don't use this switch. Instead, use the InactiveMailboxOnly switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxPlan -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 - -- Alias - -- Display name - -- Distinguished name (DN) - -- GUID - -A mailbox plan specifies the permissions and features available to a mailbox user in cloud-based organizations. You can see the available mailbox plans by using the Get-MailboxPlan cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Properties -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://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exomailbox-property-sets). - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertySets -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) - -- AddressList - -- Audit - -- Archive - -- Audit - -- Custom - -- Delivery - -- Hold - -- Moderation - -- Move - -- Policy - -- PublicFolder - -- Quota - -- Resource - -- Retention - -- SCL - -- SoftDelete - -- StatisticsSeed - -You can specify multiple values separated by commas. Wildcards ( * ) are supported. - -For more information about the properties that are included in each property set, see [Get-EXOMailbox property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exomailbox-property-sets). - -```yaml -Type: PropertySet[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientTypeDetails -The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are: - -- DiscoveryMailbox - -- EquipmentMailbox - -- GroupMailbox - -- LegacyMailbox - -- LinkedMailbox - -- LinkedRoomMailbox - -- RoomMailbox - -- SchedulingMailbox - -- SharedMailbox - -- TeamMailbox - -- UserMailbox - -You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SoftDeletedMailbox -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -The following Get-Mailbox parameters aren't available in Get-EXOMailbox: - -- PublicFolder - -- GroupMailbox - -- Migration - -- SortBy - -- Async - - -## OUTPUTS - -### -The following properties aren't included in the output of Get-EXOMailbox: - -- RunspaceId - -- Servername - -- AdminDisplayVersion - -- DelayReleaseHoldApplied - -- EnforcedTimestamps - -- Description - -- OriginatingServer - -- IsValid - -- ObjectState - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxFolderPermission.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxFolderPermission.md deleted file mode 100644 index 53ef052a39..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxFolderPermission.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxfolderpermission -applicable: Exchange Online -title: Get-EXOMailboxFolderPermission -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXOMailboxFolderPermission - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-ExOMailboxFolderPermission cmdlet to view folder-level permissions in mailboxes. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-EXOMailboxFolderPermission - [-User <String>] - [-GroupMailbox] - [[-Identity] <String>] - [-ExternalDirectoryObjectId <Guid>] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to retrieve folder level permission in the mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports -``` - -This example returns the current list of user permissions for the Reports subfolder in the Marketing folder in John's mailbox. - -### Example 2 -```powershell -Get-MailboxFolderPermission -Identity john@contoso.com:\Marketing\Reports -User Kim@contoso.com -``` - -This example returns the permissions for the same folder in John's mailbox, but only for the user Kim. - - -## PARAMETERS - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -GroupMailbox -The GroupMailbox switch is required to return Office 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mailbox folder that you want to view. This parameter uses the syntax: `<Mailbox>:\<Folder>`. For the value of \<Mailbox\>, you can use any value that uniquely identifies the mailbox. For example: - -- `<UPN>:<FolderPath>` (for example`john@contoso.com:\Calendar` or `John:\Marketing\Reports`). - -- `<ExternalDirectoryObjectId>:<FolderPath>` - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -User -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxFolderStatistics.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxFolderStatistics.md deleted file mode 100644 index 66b77bfafc..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxFolderStatistics.md +++ /dev/null @@ -1,257 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxfolderstatistics -applicable: Exchange Online -title: Get-EXOMailboxFolderStatistics -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXOMailboxFolderStatistics - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-EXOMailboxFolderStatistics cmdlet to retrieve information about the folders in a specified mailbox, including the number and size of items in the folder, the folder name and ID, and other information. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-EXOMailboxFolderStatistics - [-Archive] - [-ExternalDirectoryObjectId <Guid>] - [-Folderscope <ElcFolderType>] - [-Identity <String>] - [-IncludeAnalysis] - [-IncludeOldestAndNewestItems] - [-IncludeSoftDeletedRecipients] - [-ResultSize <Unlimited>] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -A mailbox can have hidden items that are never visible to the user and are only used by applications. The Get-EXOMailboxFolderStatistics cmdlet can return hidden items for the following values: FolderSize, FolderAndSubfolderSize, ItemsInFolder and ItemsInFolderAndSubfolders. - -Don't confuse Get-EXOMailboxFolderStatistics cmdlet (folders) with the Get-EXOMailboxStatistics cmdlet (mailboxes). - -## EXAMPLES - -### Example 1 -```powershell -Get-EXOMailboxFolderStatistics -Identity admin@contoso.com -``` - -This example returns statistics for all mailbox folders. Default is FolderScope All. - -### Example 2 -```powershell -Get-EXOMailboxFolderStatistics -Identity admin@contoso.com -FolderScope Calendar -IncludeAnalysis -IncludeOldestAndNewestItems -``` - -This example returns statistics only for calendar folders. - -## PARAMETERS - -### -Archive -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Folderscope -The FolderScope parameter specifies the scope of the search by folder type. Valid values include: - -- All - -- Archive - -- Calendar - -- Clutter - -- Contacts - -- ConversationHistory - -- DeletedItems - -- Drafts - -- Inbox - -- Journal - -- JunkEmail - -- LegacyArchiveJournals - -- ManagedCustomFolder - -- NonIpmRoot - -- Notes - -- Outbox - -- Personal - -- RecoverableItems - -- RssSubscriptions - -- SentItems - -- SyncIssues - -- Tasks - -```yaml -Type: ElcFolderType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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: - -- GUID - -- User Principal Name (UPN) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -IncludeAnalysis -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeOldestAndNewestItems -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeSoftDeletedRecipients -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxPermission.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxPermission.md deleted file mode 100644 index a637c1b30d..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxPermission.md +++ /dev/null @@ -1,238 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxpermission -applicable: Exchange Online -title: Get-EXOMailboxPermission -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXOMailboxPermission - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-EXOMailboxPermission cmdlet to retrieve permissions on a mailbox. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Default (Default) -``` -Get-EXOMailboxPermission [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -### Identity -``` -Get-EXOMailboxPermission - [-ExternalDirectoryObjectId <Guid>] - [-Identity <String>] - [-Owner] - [-ResultSize <Unlimited>] - [-SoftDeletedMailbox] - [-User <String>] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -The output of this cmdlet shows the following information: - -Identity: The mailbox in question. - -User: The security principal (user, security group, Exchange management role group, etc.) that has permission to the mailbox. - -AccessRights: The permission that the security principal has on the mailbox. The available values are ChangeOwner (change the owner of the mailbox), ChangePermission (change the permissions on the mailbox), DeleteItem (delete the mailbox), ExternalAccount (indicates the account isn't in the same domain), FullAccess (open the mailbox, access its contents, but can't send mail) and ReadPermission (read the permissions on the mailbox). Whether the permissions are allowed or denied is indicated in the Deny column. - -IsInherited: Whether the permission is inherited (True) or directly assigned to the mailbox (False). Permissions are inherited from the mailbox database and/or Active Directory. Typically, directly assigned permissions override inherited permissions. - -Deny: Whether the permission is allowed (False) or denied (True). Typically, deny permissions override allow permissions. - -By default, the following permissions are assigned to user mailboxes: - -FullAccess and ReadPermission are directly assigned to NT AUTHORITY\SELF. This entry gives a user permission to their own mailbox. - -FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes. - -ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. - -FullAccess is inherited by NT AUTHORITY\SYSTEM and ReadPermission is inherited by NT AUTHORITY\NETWORK. - -FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers. - -By default, other security groups and role groups inherit permissions to mailboxes based on their location (on-premises Exchange or Office 365). - -## EXAMPLES - -### Example 1 -```powershell -Get-EXOMailboxPermission -Identity john@contoso.com -``` - -This example return the permission the user has on mailboxes - -## PARAMETERS - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mailbox you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Owner -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SoftDeletedMailbox -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. - -```yaml -Type: SwitchParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -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: For example: - -- Name - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxStatistics.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxStatistics.md deleted file mode 100644 index d5c8667574..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMailboxStatistics.md +++ /dev/null @@ -1,218 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomailboxstatistics -applicable: Exchange Online -title: Get-EXOMailboxStatistics -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXOMailboxStatistics - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-EXOMailboxStatistics cmdlet to return information about a mailbox, such as the size of the mailbox, the number of messages it contains, and the last time it was accessed. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-EXOMailboxStatistics - [-Archive] - [-DatabaseGuid <Guid>] - [-ExchangeGuid <Guid>] - [-Identity <String>] - [-IncludeSoftDeletedRecipients] - [-Properties <String[]>] - [-PropertySets <PropertySet[]>] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You can use the detailed move history and a move report output from this cmdlet to troubleshoot a move request. To view the move history, you must pass this cmdlet as an object. Move histories are retained in the mailbox database, are numbered incrementally, and the last run move request is always numbered 0. - -You can only see move reports and move history for completed move requests. - -## EXAMPLES - -### Example 1 -```powershell -Get-EXOMailboxStatistics -Identity john@contoso.com -``` - -This example retrieves the mailbox statistics for the specified mailbox. Only the minimum set of properties are returned. - -### Example 2 -```powershell -Get-EXOMailboxStatistics -Identity john@contoso.com -Properties SystemMessageSize,SystemMessageSizeWarningQuota,SystemMessageCount -``` - -This example retrieves the minimum set of properties and the specified properties for the specified mailbox. - -## PARAMETERS - -### -Archive -The Archive switch parameter 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseGuid -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 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ExchangeGuid -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 Properies filter set to ExchangeGuid. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mailbox you want to return statistics for. You can use any value that uniquely identifies the mailbox. For example: - -- User Principal Name (UPN) - -- External Directory Object Id. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -IncludeSoftDeletedRecipients -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Properties -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://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exomailboxstatistics-property-sets). - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertySets -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) - -- All - -You can specify multiple values separated by commas. - -For more information about the properties that are included in each property set, see [Get-EXOMailboxStatistics property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exomailboxstatistics-property-sets). - -```yaml -Type: PropertySet[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMobileDeviceStatistics.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMobileDeviceStatistics.md deleted file mode 100644 index 334012f8a1..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXOMobileDeviceStatistics.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exomobiledevicestatistics -applicable: Exchange Online -title: Get-EXOMobileDeviceStatistics -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXOMobileDeviceStatistics - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-EXOMobileDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-EXOMobileDeviceStatistics - [-Mailbox <String>] - [-ActiveSync] - [-OWAforDevices] - [-RestApi] - [-UniversalOutlook] - [-Identity <String>] - [-ExternalDirectoryObjectId <Guid>] - [-UserPrincipalName <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. - -## EXAMPLES - -### Example 1 -```powershell -Get-EXOMobileDeviceStatistics -Mailbox john.doe@contoso.com -``` -Above example fetches the statstics of all devices linked to user with email john.doe@contoso.com - -### Example 2 -```powershell -Get-EXOMobileDeviceStatistics -Mailbox john.doe@contoso.com -ActiveSync -``` -Above example fetches the statstics for active sync devices linked to user with email john.doe@contoso.com - -## PARAMETERS - -### -Mailbox -This input parameter acts as Identity filter. 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 - -- User ID or user principal name (UPN) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActiveSync -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -OWAforDevices -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestApi -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UniversalOutlook -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXORecipient.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXORecipient.md deleted file mode 100644 index 86361d154b..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXORecipient.md +++ /dev/null @@ -1,407 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exorecipient -applicable: Exchange Online -title: Get-EXORecipient -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXORecipient - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-ExORecipient cmdlet to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity (Default) -``` -Get-EXORecipient - [-Filter <String>] - [-OrganizationalUnit <String>] - [-Properties <String[]>] - [-PropertySets <PropertySet[]>] - [-IncludeSoftDeletedRecipients] - [-RecipientType <String[]>] - [-RecipientTypeDetails <String[]>] - [[-Identity] <String>] - [-ExternalDirectoryObjectId <Guid>] - [-UserPrincipalName <String>] - [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -### Anr -``` -Get-EXORecipient - [-Anr <String>] - [-Filter <String>] - [-OrganizationalUnit <String>] - [-Properties <String[]>] - [-PropertySets <PropertySet[]>] - [-IncludeSoftDeletedRecipients] - [-RecipientType <String[]>] - [-RecipientTypeDetails <String[]>] - [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -## DESCRIPTION -Get-EXORecipient cmdlet can be used to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). - -## EXAMPLES - -### Example 1 -```powershell -Get-EXORecipient -ResultSize 100 -``` -Above examples returns the first 100 recipient objects in name sorted order. - -### Example 2 -```powershell -Get-EXORecipient -Identity john.doe@contosot.com -``` -Above examples returns the recipient attribute details for the user with UserPrincipalName - john.doe@contoso.com - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -Type: String -Parameter Sets: Anr -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Get-EXORecipient property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exorecipient-property-sets) and [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the recipient object that you want to view. You can use any value that uniquely identifies the recipient. For example: - -- UserPrincipalName - -- GUID - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -IncludeSoftDeletedRecipients -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Properties -The Properties parameter specifies the properties that are returned in the output of this cmdlet. You can specify multiple values separated by commas. Wildcards ( * ) are supported. - -For more information about the available properties, see [Get-EXORecipient property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exorecipient-property-sets). - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertySets -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) - -- Archive - -- Custom - -- MailboxMove - -- Policy - -For more information about the properties that are included in each property set, see [Get-EXORecipient property sets](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets#get-exorecipient-property-sets). - -```yaml -Type: PropertySet[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientType -The RecipientType parameter filters the results by the specified recipient type. Valid values are: - -- DynamicDistributionGroup - -- MailContact - -- MailNonUniversalGroup - -- MailUniversalDistributionGroup - -- MailUniversalSecurityGroup - -- MailUser - -- PublicFolder - -- UserMailbox - -You can specify multiple values separated by commas. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientTypeDetails -The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are: - -- DiscoveryMailbox - -- DynamicDistributionGroup - -- EquipmentMailbox - -- GroupMailbox - -- GuestMailUser - -- LegacyMailbox - -- LinkedMailbox - -- LinkedRoomMailbox - -- MailContact - -- MailForestContact - -- MailNonUniversalGroup - -- MailUniversalDistributionGroup - -- MailUniversalSecurityGroup - -- MailUser - -- PublicFolder - -- PublicFolderMailbox - -- RemoteEquipmentMailbox - -- RemoteRoomMailbox - -- RemoteSharedMailbox - -- RemoteTeamMailbox - -- RemoteUserMailbox - -- RoomList - -- RoomMailbox - -- SchedulingMailbox - -- SharedMailbox - -- TeamMailbox - -- UserMailbox - -You can specify multiple values separated by commas. - -The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -The UserPrincipalName parameter specifies the UPN for the mailbox you want to view (for example, navin.contoso.com). - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXORecipientPermission.md b/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXORecipientPermission.md deleted file mode 100644 index 4a4e6c2fa8..0000000000 --- a/exchange/exchange-ps/exchange/powershell-v2-module/Get-EXORecipientPermission.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://docs.microsoft.com/powershell/module/exchange/powershell-v2-module/get-exorecipientpermission -applicable: Exchange Online -title: Get-EXORecipientPermission -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: navgupta -monikerRange: "exchonline-ps" ---- - -# Get-EXORecipientPermission - -## SYNOPSIS -This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -Use the Get-EXORecipientPermission cmdlet to view information about SendAs permissions that are configured for users in a cloud-based organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Default (Default) -``` -Get-EXORecipientPermission [-Trustee <String>] - [-AccessRights <MultiValuedProperty>] - [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -### Identity -``` -Get-EXORecipientPermission [-Trustee <String>] - [-AccessRights <MultiValuedProperty>] - [[-Identity] <String>] - [-ExternalDirectoryObjectId <Guid>] - [-UserPrincipalName <String>] - [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to view/manage information about SendAs permissions that are configured for users in a cloud-based organization. Send As permission allows delegates to use the mailbox to send messages. After this permission is assigned to a delegate, any message that the delegate sends from the mailbox will appear to have been sent by the mailbox owner. However, this permission doesn't allow a delegate to sign in to the user's mailbox. It only allows users to open the mailbox. If this permission is assigned to a group, a message sent by the delegate will appear to have been sent by the group. - -## EXAMPLES - -### Example 1 -```powershell -Get-EXORecipientPermission -ResultSize 100 -``` -Above example returns recipient permission for first 100 mailbox users in the name sorted order. - -## PARAMETERS - -### -AccessRights -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -The ExternalDirectoryObjectId parameter identifies the mailbox you want to view by using the ObjectId of the mailbox in Azure Active Directory. You can use this value instead of the Identity parameter. - -```yaml -Type: Guid -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter filters the results by the target recipient. The user or group specified by the Trustee parameter can operate on this recipient. - -You can specify any type of recipient, for example: - -- Mailboxes - -- Mail users - -- External contacts - -- Distribution groups - -- Dynamic distribution groups - -You can use any value that uniquely identifies the recipient. For example: - -- External Directory Object ID - -- User Principal Name - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Trustee -The Trustee parameter filters the results by the user or group to whom you're granting the permission. The user or group can operate on the recipient specified by the Identity, UserPrincipalName, or ExternalDirectoryObjectId parameters (and you can only use the Trustee parameter with those parameters). - -**Note**: Trustee parameter can be specified only with Identity, UserPrincipalName, ExternalDirectoryObjectId parameters - -You can specify the following types of users or groups: - -- Mailbox users - -- Mail users with a Microsoft account (formerly known as a Windows Live ID) - -- Security groups - -You can use any value that uniquely identifies the user or group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- User Principal name (UPN) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-ConnectionByClientTypeDetailReport.md b/exchange/exchange-ps/exchange/reporting/Get-ConnectionByClientTypeDetailReport.md deleted file mode 100644 index df928d923f..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-ConnectionByClientTypeDetailReport.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-connectionbyclienttypedetailreport -applicable: Exchange Online -title: Get-ConnectionByClientTypeDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-ConnectionByClientTypeDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-ConnectionByClientTypeDetailReport cmdlet to view details about the different types of clients that connected to mailboxes in your organization. The client types indicate different protocols, for example, Outlook on the web, MAPI, POP3, IMAP4, Exchange ActiveSync, and Exchange Web Services. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ConnectionByClientTypeDetailReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ConnectionByClientTypeDetailReport -StartDate 06/13/2015 -EndDate 06/15/2015 -``` - -This example retrieves details about the different types of clients used to connect to mailboxes between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-ConnectionByClientTypeReport.md b/exchange/exchange-ps/exchange/reporting/Get-ConnectionByClientTypeReport.md deleted file mode 100644 index 00cb6516ba..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-ConnectionByClientTypeReport.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-connectionbyclienttypereport -applicable: Exchange Online -title: Get-ConnectionByClientTypeReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-ConnectionByClientTypeReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-ConnectionByClientTypeReport cmdlet to view a summary of the different types of clients that connected to all mailboxes in your organization. The client types indicate different protocols, for example, Outlook on the web, MAPI, POP3, IMAP4, Exchange ActiveSync, and Exchange Web Services. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ConnectionByClientTypeReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -Note: There's a 7-day lag in the client connection information that's returned by this cmdlet. For example, if you run the cmdlet on June 18, 2018, you can't retrieve information about connections made to mailboxes between June 13, 2018 and June 15, 2018. To get connection information for that date range, you need to run the cmdlet on June 22, 2018 or later. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ConnectionByClientTypeReport -StartDate 06/13/2015 -EndDate 06/15/2015 -``` - -This example retrieves a summary of the different types of clients used to connect to all mailboxes between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-CsAVConferenceTimeReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsAVConferenceTimeReport.md deleted file mode 100644 index 27f6791185..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsAVConferenceTimeReport.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csavconferencetimereport -applicable: Exchange Online -title: Get-CsAVConferenceTimeReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsAVConferenceTimeReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsAVConferenceTimeReport cmdlet to view statistics about the time in minutes that was used during audio and video conferences that were held by Skype for Business Online users in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsAVConferenceTimeReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsAVConferenceTimeReport to query information about the length of audio and video conferences held by Skype for Business Online users in the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- AVConferenceMinutes - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsAVConferenceTimeReport -ReportType Monthly -StartDate 06/01/2015 -EndDate 06/30/2015 -``` - -This example shows the time in minutes that was used during all audio and video conferences that were held by Skype for Business Online users for the month of June 2015 - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-CsActiveUserReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsActiveUserReport.md deleted file mode 100644 index 5974894999..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsActiveUserReport.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csactiveuserreport -applicable: Exchange Online -title: Get-CsActiveUserReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsActiveUserReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsActiveUserReport cmdlet to view statistics about Skype for Business Online users in your cloud-based organization. The cmdlet shows the total number of unique users that signed in and took part in at least one peer-to-peer session or conference during the specified time period. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsActiveUserReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsActiveUserReport to query information about the activities of Skype for Business Online users in the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- ActiveUsers - -- ActiveIMUsers - -- ActiveAudioUsers - -- ActiveVideoUsers - -- ActiveApplicationSharingUsers - -- ActiveFileTransferUsers - -- ActivePSTNConferencingUsers - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsActiveUserReport -ReportType Monthly -StartDate 04/01/2015 -EndDate 04/30/2015 -``` - -This example shows information about Skype for Business Online users for the month of April, 2015 - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-CsClientDeviceDetailReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsClientDeviceDetailReport.md deleted file mode 100644 index 09e29fe410..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsClientDeviceDetailReport.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csclientdevicedetailreport -applicable: Exchange Online -title: Get-CsClientDeviceDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsClientDeviceDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsClientDeviceDetailReport cmdlet to view statistics about the number of peer-to-peer sessions and conferences by users and devices that connected to Skype for Business Online in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsClientDeviceDetailReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [-UserName <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsClientDeviceDetailReport cmdlet returns the number of peer-to-peer sessions and conferences that a user participated in, and a count of what type of device they used. You can query this information for the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- UserName - -- WindowsActivities: Note that this includes activity using both Skype for Business and Skype for Business Web App clients. - -- WindowsPhoneActivities - -- AndroidActivities - -- iPhoneActivities - -- iPadActivities - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsClientDeviceDetailReport -StartDate 01/01/2015 -EndDate 01/31/2015 -``` - -This example shows activity by device for all users for the month of January. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserName -The UserName parameter filters the results by user. You identify the user by their account (for example, laura@contoso.com). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-CsClientDeviceReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsClientDeviceReport.md deleted file mode 100644 index db241d1155..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsClientDeviceReport.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csclientdevicereport -applicable: Exchange Online -title: Get-CsClientDeviceReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsClientDeviceReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsClientDeviceReport cmdlet to view statistics about the client devices that connected to Skype for Business Online in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsClientDeviceReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsClientDeviceReport cmdlet returns the monthly total of unique users that connected to the Skype for Business Online service using different types of client devices. For the reporting period you specify, the cmdlet returns the following information: - -- WindowsUsers - -- WindowsPhoneUsers - -- AndroidUsers - -- iPhoneUsers - -- iPadUsers - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get- CsClientDeviceReport -StartDate 10/01/2015 -EndDate 10/31/2015 -``` - -This example gets a report of the device usage by platform for the month of October. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-CsConferenceReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsConferenceReport.md deleted file mode 100644 index d943db9e05..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsConferenceReport.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csconferencereport -applicable: Exchange Online -title: Get-CsConferenceReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsConferenceReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsConferenceReport cmdlet to view statistics about the conferences that were held by Skype for Business Online users in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsConferenceReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsConferenceReport to query information about the type and number of conferences held by Skype for Business Online users in the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- TotalConferences - -- AVConferences - -- IMConferences - -- ApplicationSharingConferences - -- WebConferences - -- TelephonyConferences - -- PSTNConferences - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsConferenceReport -ReportType Monthly -StartDate 06/01/2015 -EndDate 06/30/2015 -``` - -This example shows information about conferences held by Skype for Business Online users for the month of June 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-CsP2PAVTimeReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsP2PAVTimeReport.md deleted file mode 100644 index ffa4fd1b28..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsP2PAVTimeReport.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csp2pavtimereport -applicable: Exchange Online -title: Get-CsP2PAVTimeReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsP2PAVTimeReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsP2PAVTimeReport cmdlet to view statistics about the audio and video time in minutes that was used during peer-to-peer (P2P) sessions that were held by Skype for Business Online users in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsP2PAVTimeReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsP2PAVTimeReport to query information about the length of audio and video conferences held by Skype for Business Online users in the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- TotalAudioMinutes - -- TotalVideoMinutes - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsP2PAVTimeReport -ReportType Monthly -StartDate 06/01/2015 -EndDate 06/30/2015 -``` - -This example shows information about the number of audio and video minutes used during P2P sessions that were held by Skype for Business Online users for the month of June 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-CsP2PSessionReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsP2PSessionReport.md deleted file mode 100644 index 369bb238e6..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsP2PSessionReport.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csp2psessionreport -applicable: Exchange Online -title: Get-CsP2PSessionReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsP2PSessionReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsP2PSessionReport cmdlet to view statistics about the peer-to-peer (P2P) sessions held by Skype for Business Online users in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsP2PSessionReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsP2PSessionReport to query information about the number and type of P2P sessions held by Skype for Business Online users in the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- TotalP2PSessions - -- P2PIMSessions - -- P2PAudioSessions - -- P2PVideoSessions - -- P2PApplicationSharingSessions - -- P2PFileTransferSessions - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsP2PSessionReport -ReportType Monthly -StartDate 06/01/2015 -EndDate 06/30/2015 -``` - -This example shows information about the P2P sessions used by Skype for Business Online users for the month of June 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-CsPSTNConferenceTimeReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsPSTNConferenceTimeReport.md deleted file mode 100644 index 11feb657b2..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsPSTNConferenceTimeReport.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-cspstnconferencetimereport -applicable: Exchange Online -title: Get-CsPSTNConferenceTimeReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsPSTNConferenceTimeReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsPSTNConferenceTimeReport cmdlet to show the number of minutes that Skype for Business Online users spent in dial-in or dial-out conferences. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsPSTNConferenceTimeReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsPSTNUsageDetailReport to query information about length of time spent in dial-in and dial-out conferences by Skype for Business Online users in the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- PSTNConferenceDialInMinutes - -- PSTNConferenceDialOutMinutes - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsPSTNConferenceTimeReport -ReportType Monthly 11/01/2015 -EndDate 12/30/2015 -``` - -This example shows the number of minutes per month that users spent in PSTN conferences for the months of November and December. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-CsPSTNUsageDetailReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsPSTNUsageDetailReport.md deleted file mode 100644 index da3b9204b5..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsPSTNUsageDetailReport.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-cspstnusagedetailreport -applicable: Exchange Online -title: Get-CsPSTNUsageDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsPSTNUsageDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsPSTNUsageDetailReport cmdlet to view public switched telephone network (PSTN) usage details for Skype for Business Online users. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsPSTNUsageDetailReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsPSTNUsageDetailReport to query information about PSTN usage details in Skype for Business Online for the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- SipUri - -- DateTimeOfCall - -- TelephoneNumber - -- CallID - -- CallType - -- Location - -- CallDuration - -- Currency - -- CallCharge - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsPSTNUsageDetailReport -StartDate 11/01/2015 -EndDate 12/30/2015 -``` - -This example shows the PSTN usage detail for users in November and December. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-CsUserActivitiesReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsUserActivitiesReport.md deleted file mode 100644 index cd58677047..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsUserActivitiesReport.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csuseractivitiesreport -applicable: Exchange Online -title: Get-CsUserActivitiesReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsUserActivitiesReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsUserActivitiesReport cmdlet to view number and type of activities that a use participated in while connected to Skype for Business Online in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsUserActivitiesReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [-UserName <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsUserActivitiesReport to query information about activities in Skype for Business Online by all users or a specified user for the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- UserName - -- LastLogonTime - -- LastActivityTime - -- TotalP2PSessions - -- TotalP2PIMSessions - -- TotalP2PAudioSessions - -- TotalP2PVideoSessions - -- TotalP2PApplicationSharingSessions - -- TotalP2PAudioSessionMinutes - -- TotalP2PVideoSessionMinutes - -- TotalOrganizedConferences - -- TotalOrganizedIMConferences - -- TotalOrganizedAVConferences - -- TotalOrganizedApplicationSharingConferences - -- TotalOrganizedWebConferences - -- TotalOrganizedDialInConferences - -- TotalOrganizedAVConferenceMinutes - -- TotalParticipatedConferences - -- TotalParticipatedIMConferences - -- TotalParticipatedAVConferences - -- TotalParticipatedApplicationSharingConferences - -- TotalParticipatedWebConferences - -- TotalParticipatedDialInConferences - -- TotalParticipatedAVConferenceMinutes - -- TotalPlacedPSTNCalls - -- TotalReceivedPSTNCalls - -- TotalPlacedPSTNCallMinutes - -- TotalReceivedPSTNCallMinutes - -- TotalMessages - -- TotalTransferredFiles - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsUserActivitiesReport -StartDate 01/01/2015 -EndDate 01/31/2015 -``` - -This example shows the activity for all users for the month of January. - -## PARAMETERS - -### -EndDate -The EndDate parameter specifies the end date of the date range. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -The StartDate parameter specifies the start date of the date range. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserName -The UserName parameter filters the results by user. You identify the user by their account (for example, laura@contoso.com). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-CsUsersBlockedReport.md b/exchange/exchange-ps/exchange/reporting/Get-CsUsersBlockedReport.md deleted file mode 100644 index 89e8cc28c4..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-CsUsersBlockedReport.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-csusersblockedreport -applicable: Exchange Online -title: Get-CsUsersBlockedReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-CsUsersBlockedReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-CsUsersBlockedReport cmdlet to view Skype for Business Online users who have been blocked due to fraudulent call activities. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-CsUsersBlockedReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You can use the Get-CsUsersBlockedReport to query information about blocked users in Skype for Business Online for the last 3 months. For the reporting period you specify, the cmdlet returns the following information: - -- ActionDate - -- SIPURI - -- ActionType - -- TelephoneNumber - -- Reason - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-CsUsersBlockedReport -StartDate 11/01/2015 -EndDate 12/30/2015 -``` - -This example shows the list of blocked users for November and December. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-GroupActivityReport.md b/exchange/exchange-ps/exchange/reporting/Get-GroupActivityReport.md deleted file mode 100644 index 94a3488f02..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-GroupActivityReport.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-groupactivityreport -applicable: Exchange Online -title: Get-GroupActivityReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-GroupActivityReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-GroupActivityReport cmdlet to view the number of distribution groups that were created and deleted in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-GroupActivityReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-GroupActivityReport -ReportType Monthly -StartDate 05/01/2015 -EndDate 05/31/2015 -``` - -This example shows the number of distribution groups created and deleted for the month of May, 2015 - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-LicenseVsUsageSummaryReport.md b/exchange/exchange-ps/exchange/reporting/Get-LicenseVsUsageSummaryReport.md deleted file mode 100644 index e5cc20e88d..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-LicenseVsUsageSummaryReport.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-licensevsusagesummaryreport -applicable: Exchange Online -title: Get-LicenseVsUsageSummaryReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-LicenseVsUsageSummaryReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-LicenseVsUsageSummaryReport cmdlet to retrieve a report that identifies the number of active users for installed software licenses (workloads). - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-LicenseVsUsageSummaryReport [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet produces a report that is intended to enable clients to track and manage the use of contracted software licenses. The output contains the following properties. - -- Date: The period being measured. - -- TenantGuid: The unique identifier for the Exchange Online tenant. - -- Workload: The workload whose users are being counted. The current workloads include: Exchange Online, SharePoint Online, Skype for Business Online, and Microsoft Yammer. - -- NonTrialEntitlements: The number of entitled users for the workload. - -- TrialEntitlements: The number of provisionally entitled (trial) users for the workload. - -- ActiveUsers: The count of active users for the workload. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-LicenseVsUsageSummaryReport -``` - -This example gets a report of the active workload users. - -## 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-MailDetailMalwareReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailDetailMalwareReport.md deleted file mode 100644 index 4d3760ff0f..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailDetailMalwareReport.md +++ /dev/null @@ -1,313 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-maildetailmalwarereport -applicable: Exchange Online, Exchange Online Protection -title: Get-MailDetailMalwareReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-MailDetailMalwareReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MailDetailMalwareReport cmdlet to view the details of messages that contained malware. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailDetailMalwareReport [-Action <MultiValuedProperty>] [-Direction <MultiValuedProperty>] - [-Domain <MultiValuedProperty>] [-EndDate <DateTime>] [-EventType <MultiValuedProperty>] - [-Expression <Expression>] [-MalwareName <MultiValuedProperty>] [-MessageId <MultiValuedProperty>] - [-MessageTraceId <MultiValuedProperty>] [-Page <Int32>] [-PageSize <Int32>] [-ProbeTag <String>] - [-RecipientAddress <MultiValuedProperty>] [-SenderAddress <MultiValuedProperty>] [-StartDate <DateTime>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailDetailMalwareReport -StartDate 06/13/2015 -EndDate 06/15/2015 -SenderAddress john@contoso.com -``` - -This example retrieves the details of messages sent by john@contoso.com that contained malware between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MalwareName -The MalwareName parameter filters the report by the name of the malware. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageId -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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageTraceId -The MessageTraceId parameter can be used with the recipient address to uniquely identify a message trace and obtain more details. A message trace ID is generated for every message that's processed by the system. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MailDetailSpamReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailDetailSpamReport.md deleted file mode 100644 index 587f63fada..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailDetailSpamReport.md +++ /dev/null @@ -1,296 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-maildetailspamreport -applicable: Exchange Online, Exchange Online Protection -title: Get-MailDetailSpamReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-MailDetailSpamReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MailDetailSpamReport cmdlet to view the details of spam messages. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailDetailSpamReport [-Action <MultiValuedProperty>] [-Direction <MultiValuedProperty>] - [-Domain <MultiValuedProperty>] [-EndDate <DateTime>] [-EventType <MultiValuedProperty>] - [-Expression <Expression>] [-MessageId <MultiValuedProperty>] [-MessageTraceId <MultiValuedProperty>] - [-Page <Int32>] [-PageSize <Int32>] [-ProbeTag <String>] [-RecipientAddress <MultiValuedProperty>] - [-SenderAddress <MultiValuedProperty>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailDetailSpamReport -StartDate 06/13/2015 -EndDate 06/15/2015 -SenderAddress john@contoso.com -``` - -This example retrieves the details of spam messages sent by john@contoso.com between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageId -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, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageTraceId -The MessageTraceId parameter can be used with the recipient address to uniquely identify a message trace and obtain more details. A message trace ID is generated for every message that's processed by the system. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SenderAddress -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MailFilterListReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailFilterListReport.md deleted file mode 100644 index 25c6f2bcb7..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailFilterListReport.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailfilterlistreport -applicable: Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Get-MailFilterListReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps || eop-ps" ---- - -# Get-MailFilterListReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MailFilterListReport cmdlet to obtain values for various parameters that can be supplied to other reporting cmdlets. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailFilterListReport [-Domain <MultiValuedProperty>] [-Expression <Expression>] [-ProbeTag <String>] - [-SelectionTarget <MultiValuedProperty>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailFilterListReport -SelectionTarget TransportRule -``` - -This example uses the Get-MailFilterListReport cmdlet to return information about transport rules. - -## PARAMETERS - -### -Domain -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SelectionTarget -The SelectionTarget parameter filters the report information by object type. Valid values for this parameter are: Actions, DlpPolicy, DlpRule, Domain, EventTypes, FindOnPremConnector or TransportRule. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MailTrafficReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailTrafficReport.md deleted file mode 100644 index 3bb789248b..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailTrafficReport.md +++ /dev/null @@ -1,375 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailtrafficreport -applicable: Exchange Online, Exchange Online Protection -title: Get-MailTrafficReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-MailTrafficReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MailTrafficReport cmdlet to view details about message traffic in your organization for the last 180 days. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailTrafficReport - [-Action <MultiValuedProperty>] - [-AggregateBy <String>] - [-Direction <MultiValuedProperty>] - [-Domain <MultiValuedProperty>] - [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] - [-Expression <Expression>] - [-Page <Int32>] - [-PageSize <Int32>] - [-ProbeTag <String>] - [-StartDate <DateTime>] - [-SummarizeBy <MultiValuedProperty>] - [<CommonParameters>] -``` - -## DESCRIPTION -You can use the EventTypes values from the Get-MailTrafficReport cmdlet to analyze what happened to messages when they were filtered by the service. The following list describes the event types for messages. - -Mail traffic summary - -- AdvancedProtectionMalware: Messages that were marked as malware by the Office 365 Advanced Threat Protection service. For details about the Advanced Threat Protection service, see [Office 365 Advanced Threat Protection service description](https://docs.microsoft.com/office365/servicedescriptions/office-365-advanced-threat-protection-service-description). - -- AtpGoodMail: Messages that were delivered after passing through the Office 365 Advanced Threat Protection service. This count shows the number of unique messages. If a message was delivered to multiple recipients, it would still count as a single message. - -- DLPMessages: Messages that matched a data loss prevention (DLP) policy. For details about data loss prevention, see [Overview of data loss prevention](https://docs.microsoft.com/microsoft-365/compliance/data-loss-prevention-policies). - -- Expire: Messages that cannot be delivered, stuck in a queue, and after some time expired. - -- GoodMail: Messages that were delivered after passing through the malware and spam filters. This count shows the number of unique messages. If a message was delivered to multiple recipients, it would still count as a single message. - -- Malware: Messages that were marked as malware. - -- Receive: Messages successfully received by the service. - -- SpoofMail: Messages that were marked as spoofed by the Office 365 anti-spoofing protection. - -- TransportRuleHits: Messages that matched a transport rule. If a message matched multiple rules, this event type would show each of the rule matches. - -- TransportRuleMessages: Messages that matched a transport rule. If a message matched multiple rules, this event type would show each of the rule matches. - -Spam detections - -- SpamIPBlock: Messages that were blocked based on the sender IP. - -- SpamDBEBFilter: Messages that were blocked based on checking the recipient against the directory. This happens when a message is addressed to an unknown recipient. - -- SpamEnvelopeBlock: Messages that were blocked based on SMTP. - -- SpamContentFiltered: Messages that passed the initial IP and SMTP filters and were filtered based on content, rules or other spam configurations. - -Spam analysis - content-filtered spam - -- Spam\_AdditionalSpamFiltered: Messages filtered based on advanced spam filters that have been enabled. For details about the advanced spam filter, see [Advanced spam filtering options](https://docs.microsoft.com/microsoft-365/security/office-365-security/advanced-spam-filtering-asf-options). - -- Spam\_BlockList: Messages that were filtered because the sender was on a spam filter block list. For more details on how to configure these lists, see [Configure your spam filter policies](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-your-spam-filter-policies). - -- Spam\_BulkFiltered: Messages that were filtered as bulk mail. See message volume breakdown by Bulk Complaint Level (BCL) for further analysis of bulk mail. For more information about bulk mail processing, see [What's the difference between junk email and bulk email?](https://docs.microsoft.com/microsoft-365/security/office-365-security/what-s-the-difference-between-junk-email-and-bulk-email). - -- Spam\_ContentScanFiltered: Messages that were filtered based on the message content. - -- Spam\_ETRFiltered: Messages that were filtered due to a transport rule. - -- Spam\_SenderBlocked: Messages that were filtered because the sender was on a block list. - -Spam analysis - non-spam messages - -- NonSpam\_AdditionalSpamFilterPassed: Messages that were passed based on advanced spam filters that have been enabled. For details about the advanced spam filters, see [Advanced spam filtering options](https://docs.microsoft.com/microsoft-365/security/office-365-security/advanced-spam-filtering-asf-options). - -- NonSpam\_AllowList: Messages that were passed because the sender was on a spam filter allow list. For more details on how to configure these lists, see [Configure your spam filter policies](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-your-spam-filter-policies). - -- NonSpam\_BulkPassed: Messages that were determined not to be bulk mail. - -- NonSpam\_ContentScanPassed: Messages that were passed by the content scan. - -- NonSpam\_ETRPassed: Messages that passed based on a transport rule. - -- NonSpam\_IntraOrg: Messages that were deemed as low risk of spam based on factors such as intra-organizational mail. - -- NonSpam\_IPAllowed: Messages that were passed because the sending IP was on the IP allow list. - -- NonSpam\_SafeSender: Messages that were passed because the sender was marked as safe. - -Bulk mail - -- BCL0: Messages that are not bulk mail are marked with Bulk Complaint Level (BCL) value of 0. For details on how to use BCL to mark messages as spam, see [Use mail flow rules to configure bulk email filtering in Exchange Online Protection](https://docs.microsoft.com/microsoft-365/security/office-365-security/use-transport-rules-to-configure-bulk-email-filtering). - -- BCL1 through BCL9: Messages with BCL rating of 1 through 9. - -Encryption - -- EncryptionManual: Messages manually encrypted by users. - -- EncryptionPolicy: Messages that matched a rule for encrypting email messages using the latest Office 365 Message Encryption (OME) capabilities. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailTrafficReport -Direction Inbound -StartDate 06/13/2015 -EndDate 06/15/2015 -``` - -This example retrieves details for incoming messages between June 13, 2015 and June 15, 2015. - -### Example 2 -```powershell -Get-MailTrafficReport -StartDate 12/12/2015 -EndDate 12/12/2015 -Direction Outbound | Format-Table Domain,Date,EventType,Action,MessageCount -``` - -This example retrieves the statistics for outgoing messages on December 12, 2015, and displays the results in a table. Every unique combination of EventType and Action is displayed on a separate row in the table. - -### Example 3 -```powershell -Get-MailTrafficReport -StartDate 12/12/2015 -EndDate 12/12/2015 -Direction Outbound -SummarizeBy Domain,EventType | Format-Table Domain,Date,EventType,Action,MessageCount -``` - -This example is similar to the previous example, but now the results are summarized. Because the EventType is one of the summarized values, the rows in the table now contain the unique values of Action. The total number of rows in the report is reduced, and values of MessageCount are correspondingly larger on each row. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering, or spam filtering. 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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AggregateBy -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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. - -If you don't use the Domain parameter, the message count for your entire organization is returned. This includes messages that were sent from or to unregistered domains that are attributed to your organization. Unregistered domains can be attributed to your organization in hybrid or EOP standalone configurations. - -Notes: - -- Messages that are sent to recipients in multiple domains are counted differently at the domain level versus the organizational level. At the domain level, the message is counted for each different domain. At the organizational level, the message is counted only once. Therefore, if you add up the total number of received messages for each domain, the value might not match the total number of received messages for the organization. - -- The Domain value is Others for messages that were sent from or to unregistered domains that are attributed to your organization (messages in domains that aren't configured as accepted domains in your organization). - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SummarizeBy -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 the Get-MailTrafficReport cmdlet, the SummarizeBy parameter accepts the values Action, Domain, and EventType. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MailTrafficTopReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailTrafficTopReport.md deleted file mode 100644 index e72985dc60..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailTrafficTopReport.md +++ /dev/null @@ -1,265 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailtraffictopreport -applicable: Exchange Online, Exchange Online Protection -title: Get-MailTrafficTopReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-MailTrafficTopReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MailTrafficTopReport cmdlet to view a report of the highest volume senders, recipients, malware recipients and spam recipients in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailTrafficTopReport [-Action <MultiValuedProperty>] [-AggregateBy <String>] - [-Direction <MultiValuedProperty>] [-Domain <MultiValuedProperty>] [-EndDate <DateTime>] - [-EventType <MultiValuedProperty>] [-Expression <Expression>] [-Page <Int32>] [-PageSize <Int32>] - [-ProbeTag <String>] [-StartDate <DateTime>] [-SummarizeBy <MultiValuedProperty>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailTrafficTopReport -StartDate 06/13/2015 -EndDate 06/15/2015 -``` - -This example shows the highest volume senders, recipients, malware recipients and spam recipients between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -Action -The Action parameter filters the report by the action taken by DLP policies, transport rules, malware filtering or spam filtering. 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. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AggregateBy -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Direction -The Direction parameter filters the results by incoming or outgoing messages. Valid values for this parameter are Inbound and Outbound. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventType -The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command Get-MailFilterListReport -SelectionTarget EventTypes. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SummarizeBy -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 the Get-MailTopTrafficReport cmdlet, the SummarizeBy parameter accepts the values Domain and EventType. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MailboxActivityReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailboxActivityReport.md deleted file mode 100644 index 51bfa6e402..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailboxActivityReport.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailboxactivityreport -applicable: Exchange Online -title: Get-MailboxActivityReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-MailboxActivityReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-MailboxActivityReport cmdlet to view the number of mailboxes created and deleted in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxActivityReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxActivityReport -ReportType Monthly -StartDate 05/01/2015 -EndDate 05/31/2015 -``` - -This example shows the number of mailboxes created and deleted for the month of May, 2015 - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MailboxUsageDetailReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailboxUsageDetailReport.md deleted file mode 100644 index e60b6cfddc..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailboxUsageDetailReport.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailboxusagedetailreport -applicable: Exchange Online -title: Get-MailboxUsageDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-MailboxUsageDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-MailboxUsageDetailReport cmdlet to view usage details about mailboxes in your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxUsageDetailReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxUsageDetailReport -StartDate 06/13/2015 -EndDate 06/15/2015 -``` - -This example retrieves details for mailboxes that were near or over the maximum mailbox size between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MailboxUsageReport.md b/exchange/exchange-ps/exchange/reporting/Get-MailboxUsageReport.md deleted file mode 100644 index f1e6a7c9e7..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MailboxUsageReport.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mailboxusagereport -applicable: Exchange Online -title: Get-MailboxUsageReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-MailboxUsageReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-MailboxUsageReport cmdlet to view the number of mailboxes in your organization that are within 25% of the maximum mailbox size, and the number of mailboxes that are over the maximum size for your organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MailboxUsageReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailboxUsageReport -StartDate 06/13/2015 -EndDate 06/15/2015 -``` - -This example retrieves the number of mailboxes that were near or over the maximum mailbox size between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-MxRecordReport.md b/exchange/exchange-ps/exchange/reporting/Get-MxRecordReport.md deleted file mode 100644 index 90d9c429f4..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-MxRecordReport.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-mxrecordreport -applicable: Exchange Online, Exchange Online Protection -title: Get-MxRecordReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-MxRecordReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-MxRecordReport cmdlet to view information about the mail exchanger (MX) records that are configured for a specified domain. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-MxRecordReport [-Domain <Fqdn>] [-Expression <Expression>] [-ProbeTag <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MxRecordReport -Domain contoso.com -``` - -This example shows the MX record information for the contoso.com domain. - -## PARAMETERS - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-O365ClientBrowserDetailReport.md b/exchange/exchange-ps/exchange/reporting/Get-O365ClientBrowserDetailReport.md deleted file mode 100644 index 6b0ba519d7..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-O365ClientBrowserDetailReport.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-o365clientbrowserdetailreport -applicable: Exchange Online -title: Get-O365ClientBrowserDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-O365ClientBrowserDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-O365ClientBrowserDetailReport cmdlet to get a detailed report of client browser use. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-O365ClientBrowserDetailReport [-Browser <String>] [-BrowserVersion <String>] [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [-WindowsLiveID <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This report provides browser details for all active users. The data contains a maximum of four browsers per user, and are aggregated daily and retained for 5 days. The properties that are returned in the results are described in the following list. - -- TenantGuid: Unique identifier of the tenant. - -- TenantName: Tenant name. - -- Date: The timestamp for the connection for the browser and version combination. - -- WindowsLiveID: User ID in the format user@domain. - -- DisplayName: User name. - -- LastAccessTime: Last date the user connected with this browser and version combination. - -- ObjectId: User object ID. - -- Browser: Browser name. - -- BrowserVersion: Browser version. - -- BrowserUsageCount: Number of days this browser and version combination was used during the period of the report - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-O365ClientBrowserDetailReport -WindowsLiveID john@contoso.com -StartDate 05/01/2016 -EndDate 05/03/2016 -``` - -This example retrieves the browser details for the user john@contoso.com between May 1, 2016 and May 3, 2016. - -### Example 2 -```powershell -Get-O365ClientBrowserDetailReport -Browser Chrome -``` - -This example retrieves the details for the Chrome browser for the current 5 day retention period (no start and end date are specified). - -## PARAMETERS - -### -Browser -The Browser parameter filters the report by browser. If you don't use this parameter, all browsers will be included. The accepted values for this parameter are: - -- IE - -- Firefox - -- Chrome - -- Safari - -- Opera - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BrowserVersion -The BrowserVersion parameter filters the report by browser version. If you don't use this parameter, all browser versions will be included in the results. This parameter accepts version numbers up to the first minor version. For example, use 11 or 11.0, not 11.0.9600.17105. Wildcards are not accepted. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WindowsLiveID -The WindowsLiveID parameter filters the report by user ID. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-O365ClientBrowserReport.md b/exchange/exchange-ps/exchange/reporting/Get-O365ClientBrowserReport.md deleted file mode 100644 index 0cfe9d5189..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-O365ClientBrowserReport.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-o365clientbrowserreport -applicable: Exchange Online -title: Get-O365ClientBrowserReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-O365ClientBrowserReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-O365ClientBrowserReport cmdlet to get a summary report of client browser use. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-O365ClientBrowserReport [-Browser <String>] [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -The report displays the client use statistics for the five most recent versions of the browsers named in the Browser parameter description. All previous browser versions are combined into a sixth category named Others. The following list describes the properties that are returned in the results. - -- TenantGuid: Unique identifier of the tenant. - -- TenantName: Tenant name. - -- Date: Last time the line item data was aggregated. - -- Browser: Browser name. - -- Version: Browser version. - -- TotalBrowserCount: Number of times a given browser and version combination connected to the service during the reporting period. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-O365ClientBrowserReport -Browser IE -``` - -This example gets the summary report of client Internet Explorer use for the 366 day data retention period (no start and end date are specified). - -### Example 2 -```powershell -Get-O365ClientBrowserReport -StartDate 06/13/2015 -EndDate 06/15/2015 -``` - -This example retrieves the client browser information for all browsers between June 13, 2015 and June 15, 2015. - -## PARAMETERS - -### -Browser -The Browser parameter filters the report by browser. If you don't use this parameter, all browsers will be included. The accepted values for this parameter are: - -- IE - -- Firefox - -- Chrome - -- Safari - -- Opera - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-O365ClientOSDetailReport.md b/exchange/exchange-ps/exchange/reporting/Get-O365ClientOSDetailReport.md deleted file mode 100644 index aa5bc805ed..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-O365ClientOSDetailReport.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-o365clientosdetailreport -applicable: Exchange Online -title: Get-O365ClientOSDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-O365ClientOSDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-O365ClientOSDetailReport cmdlet to get a detailed report of client operating system use. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-O365ClientOSDetailReport [-EndDate <DateTime>] [-OperatingSystem <String>] [-OperatingSystemVersion <String>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [-WindowsLiveID <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This report provides operating system details for all active users. The data contains a maximum of four operating systems per user, are aggregated daily and retained for 5 days. The properties that are returned in the results are described in the following list. - -- TenantGuid: Unique identifier of the tenant. - -- TenantName: Tenant name. - -- Date: The timestamp for the connection for the operating system and version combination. - -- WindowsLiveID: User ID in the format user@domain. - -- DisplayName: User name. - -- LastAccessTime: Last date the user connected with this operating system and version combination. - -- ObjectId: User object ID. - -- OperatingSystem: Operating system name. - -- Version: Operating system version. - -- OperatingSystemUsageCount: Number of days this operating system and version combination was used during the period of the report - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-O365ClientOSDetailReport -WindowsLiveID john@contoso.com -StartDate 05/01/2016 -EndDate 05/03/2016 -``` - -This example retrieves the operating system details for user John between May 1, 2016 and May 3, 2016. - -### Example 2 -```powershell -Get-O365ClientOSDetailReport -OperatingSystem Android -``` - -This example retrieves the operating system details for the Android operating system for the current 5 day retention period (no start and end date are specified). - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OperatingSystem -The OS parameter filters the report by operating system. If you don't use this parameter, all operating systems will be included. The accepted values for this parameter are: - -- Windows - -- Android - -- iOS - -- "Mac OS" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OperatingSystemVersion -The OperatingSystemVersion parameter filters the report by operating system version. If you don't use this parameter, all operating system versions will be included. The parameter accepts version numbers up to the first minor version. For example, use 6 or 6.1, not 6.1.9600. Wildcards are not accepted. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WindowsLiveID -The WindowsLiveID filters the report by user ID. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-O365ClientOSReport.md b/exchange/exchange-ps/exchange/reporting/Get-O365ClientOSReport.md deleted file mode 100644 index 7a1a2770a4..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-O365ClientOSReport.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-o365clientosreport -applicable: Exchange Online -title: Get-O365ClientOSReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-O365ClientOSReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-O365ClientOSReport cmdlet to get a summary report of client operating system use. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-O365ClientOSReport [-EndDate <DateTime>] [-OS <String>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -The report displays the client use statistics for the five most recent versions of the operating systems named in the OS parameter description. All previous operating system versions are combined into a sixth category named Others. The following list describes the properties that are returned in the results. - -- TenantGuid: Unique identifier of the tenant. - -- TenantName: Tenant name. - -- Date: Last time the line item data was aggregated. - -- OperatingSystem: Operating system name. - -- Version: Operating system version. - -- OperatingSystemUsageCount: Number of times a given operating system and version combination connected to the service during the reporting period. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-O365ClientOSReport -OS Windows -``` - -This example gets the summary report of client Windows use for the 366 day data retention period (no start and end date are specified). - -### Example 2 -```powershell -Get-O365ClientOSReport -StartDate 06/13/2013 -EndDate 06/15/2013 -``` - -This example retrieves the client operating system information between June 13, 2013 and June 15, 2013. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OS -The OS parameter filters the report by operating system. If you don't use this parameter, all operating systems will be included. The accepted values for this parameter are: - -- Windows - -- Android - -- iOS - -- "Mac OS" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-OutboundConnectorReport.md b/exchange/exchange-ps/exchange/reporting/Get-OutboundConnectorReport.md deleted file mode 100644 index 29d1e746ac..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-OutboundConnectorReport.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-outboundconnectorreport -applicable: Exchange Online, Exchange Online Protection -title: Get-OutboundConnectorReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-OutboundConnectorReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-OutboundConnectorReport cmdlet to view the Outbound connectors that are used to deliver mail to specific domains. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-OutboundConnectorReport [-Domain <Fqdn>] [-Expression <Expression>] [-ProbeTag <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-OutboundConnectorReport -Domain contoso.com -``` - -This example shows the Outbound connector that's used to deliver mail to the contoso.com domain. - -## PARAMETERS - -### -Domain -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-ReportExecutionInstance.md b/exchange/exchange-ps/exchange/reporting/Get-ReportExecutionInstance.md deleted file mode 100644 index 51ecc88c5d..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-ReportExecutionInstance.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-reportexecutioninstance -applicable: Exchange Online -title: Get-ReportExecutionInstance -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-ReportExecutionInstance - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-ReportExecutionInstance cmdlet to review the report execution instance in Exchange Online. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ReportExecutionInstance [-Identity <InstanceIdParameter>] [-ScheduleId <MultiValuedProperty>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ReportExecutionInstance | Format-Table -Auto Identity,ScheduleId,ReportStartDate,ReportEndDate -``` - -This example returns a summary list of all report execution instances. - -### Example 2 -```powershell -Get-ReportExecutionInstance -Identity 277df7c3-5b73-4409-6264-08d4a8052836 -``` - -This example returns detailed information for the specified report execution instance. - -## PARAMETERS - -### -Identity -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ScheduleId -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-SCInsights.md b/exchange/exchange-ps/exchange/reporting/Get-SCInsights.md deleted file mode 100644 index c9faadf53e..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SCInsights.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-scinsights -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-SCInsights -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-SCInsights - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-SCInsights cmdlet to view Office 365 insights information. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SCInsights [-EndDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the following output: - -- Organization: The Office 365 domain. - -- Date: The date of the even in Coordinated Universal Time (UTC). - -- InsightType - -- InsightSubType: The value All or Archive. - -- UsersCount: An integer count, or the size in megabytes for the InsightType value. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SCInsights -``` - -This example returns all insights data. - -### Example 2 -```powershell -Get-SCInsights -EndDate (Get-Date "3/3/2018 9:30 AM").ToUniversalTime() -``` - -This example return insights data for March 15, 2018. - -## PARAMETERS - -### -EndDate -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: - -- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z". - -- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see [Get-Date](https://go.microsoft.com/fwlink/p/?LinkID=113313). - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-SPOActiveUserReport.md b/exchange/exchange-ps/exchange/reporting/Get-SPOActiveUserReport.md deleted file mode 100644 index 843bc233d9..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SPOActiveUserReport.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-spoactiveuserreport -applicable: Exchange Online -title: Get-SPOActiveUserReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-SPOActiveUserReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-SpoActiveUserReport cmdlet to view statistics about Microsoft SharePoint Online users in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SPOActiveUserReport [-EndDate <DateTime>] [-ReportType <ReportType>] - [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SpoActiveUserReport -ReportType Monthly -StartDate 11/01/2015 -EndDate 11/30/2015 -``` - -This example shows information about SharePoint Online users for November, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-SPOSkyDriveProDeployedReport.md b/exchange/exchange-ps/exchange/reporting/Get-SPOSkyDriveProDeployedReport.md deleted file mode 100644 index 90ef4afbd7..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SPOSkyDriveProDeployedReport.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-sposkydriveprodeployedreport -applicable: Exchange Online -title: Get-SPOSkyDriveProDeployedReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-SPOSkyDriveProDeployedReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-SPOSkyDriveProDeployedReport cmdlet to view the number of My Site sites in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SPOSkyDriveProDeployedReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get- SPOSkyDriveProDeployedReport -ReportType Monthly -StartDate 11/01/2015 -EndDate 11/30/2015 -``` - -This example displays the number of My Sites as of November, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-SPOSkyDriveProStorageReport.md b/exchange/exchange-ps/exchange/reporting/Get-SPOSkyDriveProStorageReport.md deleted file mode 100644 index 97bba2b348..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SPOSkyDriveProStorageReport.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-sposkydriveprostoragereport -applicable: Exchange Online -title: Get-SPOSkyDriveProStorageReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-SPOSkyDriveProStorageReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-SPOSkyDriveProStorageReport cmdlet to view statistics about the space taken up (in MB) by My Sites in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SPOSkyDriveProStorageReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SPOSkyDriveProStorageReport -ReportType Monthly -StartDate 11/01/2015 -EndDate 11/30/2015 -``` - -This example shows information about the space (in MB) taken up by My Sites for November, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-SPOTeamSiteDeployedReport.md b/exchange/exchange-ps/exchange/reporting/Get-SPOTeamSiteDeployedReport.md deleted file mode 100644 index fb46ff1fb1..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SPOTeamSiteDeployedReport.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-spoteamsitedeployedreport -applicable: Exchange Online -title: Get-SPOTeamSiteDeployedReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-SPOTeamSiteDeployedReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-SPOTeamSiteDeployedReport cmdlet to view statistics about the number of team sites in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SPOTeamSiteDeployedReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SPOTeamSiteDeployedReport -ReportType Monthly -StartDate 11/01/2015 -EndDate 11/30/2015 -``` - -This example shows information about the number of team sites in the month of November, 2015 - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-SPOTeamSiteStorageReport.md b/exchange/exchange-ps/exchange/reporting/Get-SPOTeamSiteStorageReport.md deleted file mode 100644 index 3ab87b78e8..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SPOTeamSiteStorageReport.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-spoteamsitestoragereport -applicable: Exchange Online -title: Get-SPOTeamSiteStorageReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-SPOTeamSiteStorageReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-SPOTeamSiteStorageReport cmdlet to view statistics about the space taken up (in MB) by team sites in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SPOTeamSiteStorageReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SPOTeamSiteStorageReport -ReportType Monthly -StartDate 11/01/2015 -EndDate 11/30/2015 -``` - -This example shows information about the space taken up (in MB) by team sites for November, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-SPOTenantStorageMetricReport.md b/exchange/exchange-ps/exchange/reporting/Get-SPOTenantStorageMetricReport.md deleted file mode 100644 index ab195f95ee..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SPOTenantStorageMetricReport.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-spotenantstoragemetricreport -applicable: Exchange Online -title: Get-SPOTenantStorageMetricReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-SPOTenantStorageMetricReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-SPOTenantStorageMetricReport cmdlet to view statistics about the space taken up (in MB) by all sites in for your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SPOTenantStorageMetricReport [-EndDate <DateTime>] [-ReportType <ReportType>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SpoActiveUserReport -ReportType Monthly -StartDate 11/01/2015 -EndDate 11/30/2015 -``` - -This example shows information about the space taken up (in MB) by all sites for your cloud-based organization for November, 2015. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReportType -The ReportType parameter aggregates the data in the report by the value you specify. Valid values for this parameter are Daily, Weekly, Monthly and Yearly. Use the value of ReportType with appropriate values for the StartDate and EndDate parameters to review the data from a specific time period. - -```yaml -Type: ReportType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-ServiceDeliveryReport.md b/exchange/exchange-ps/exchange/reporting/Get-ServiceDeliveryReport.md deleted file mode 100644 index d8d7843176..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-ServiceDeliveryReport.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-servicedeliveryreport -applicable: Exchange Online, Exchange Online Protection -title: Get-ServiceDeliveryReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Get-ServiceDeliveryReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-ServiceDeliveryReport cmdlet to view information about the message delivery path for a specified recipient. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-ServiceDeliveryReport [-Expression <Expression>] [-ProbeTag <String>] [-Recipient <SmtpAddress>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ServiceDeliveryReport -Recipient chris@contoso.com -``` - -This example shows the delivery path information for the recipient chris@contoso.com. - -## PARAMETERS - -### -Expression -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Expression -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProbeTag -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Recipient -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-StaleMailboxDetailReport.md b/exchange/exchange-ps/exchange/reporting/Get-StaleMailboxDetailReport.md deleted file mode 100644 index f2f932d74d..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-StaleMailboxDetailReport.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-stalemailboxdetailreport -applicable: Exchange Online -title: Get-StaleMailboxDetailReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-StaleMailboxDetailReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-StaleMailboxDetailReport cmdlet to view mailboxes that haven't been accessed for at least 30 days. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-StaleMailboxDetailReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-StaleMailboxDetailReport -``` - -This example retrieves all the mailboxes that haven't been accessed for at least 30 days. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. The default value is 1000. - -This cmdlet returns a maximum of 50000 results, even when you use the value unlimited. If your organization has more than 50000 mailboxes, you can use the Select-Object and Sort-Object cmdlets in multiple commands to return all of the results. For example, if your organization has 90000 mailboxes, run the following commands: - -Get-StaleMailboxDetailReport -ResultSize unlimited | Sort-Object UserName -Unique | Select-Object TenantName,UserName,WindowsLiveID,LastLogin,DaysInactive -First 45000 | Export-Csv "C:\\Data\\First45k Stale.csv" - -Get-StaleMailboxDetailReport -ResultSize unlimited | Sort-Object UserName -Unique | Select-Object TenantName,UserName,WindowsLiveID,LastLogin,DaysInactive -Last 45000 | Export-Csv "C:\\Data\\Last45k Stale.csv" - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-StaleMailboxReport.md b/exchange/exchange-ps/exchange/reporting/Get-StaleMailboxReport.md deleted file mode 100644 index bce30c8738..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-StaleMailboxReport.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-stalemailboxreport -applicable: Exchange Online -title: Get-StaleMailboxReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-StaleMailboxReport - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet was deprecated in January, 2018. For information about the available replacement Microsoft Graph reports in Office 365, see the subtopics of [Working with Office 365 usage reports in Microsoft Graph](https://go.microsoft.com/fwlink/p/?LinkID=865135). - -Use the Get-StaleMailboxReport cmdlet to view the number of mailboxes that haven't been accessed for at least 30 days. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-StaleMailboxReport [-EndDate <DateTime>] [-ResultSize <Unlimited>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-StaleMailboxReport -``` - -This example retrieves the number of mailboxes that haven't been accessed for at least 30 days. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/reporting/Get-SupervisoryReviewOverallProgressReport.md b/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewOverallProgressReport.md deleted file mode 100644 index e9be6b9bce..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewOverallProgressReport.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-supervisoryreviewoverallprogressreport -applicable: Office 365 Security & Compliance Center -title: Get-SupervisoryReviewOverallProgressReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-SupervisoryReviewOverallProgressReport - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-SupervisoryReviewOverallProgressReport cmdlet to view the total number of supervised communications classified as Pending, Resolved, Compliant, Non-compliant, and Questionable. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SupervisoryReviewOverallProgressReport [-EndDate <System.DateTime>] [-Page <Int32>] [-PageSize <Int32>] - [-StartDate <System.DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-SupervisoryReviewOverallProgressReport | ft Pending, Resolved, Compliant, Noncompliant, Questionable -``` - -This example returns a list of the total number of supervised communications classified by status. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: System.DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: System.DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewPolicyReport.md b/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewPolicyReport.md deleted file mode 100644 index ff78b2eead..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewPolicyReport.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-supervisoryreviewpolicyreport -applicable: Exchange Online, Office 365 Security & Compliance Center -title: Get-SupervisoryReviewPolicyReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || o365scc-ps" ---- - -# Get-SupervisoryReviewPolicyReport - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-SupervisoryReviewPolicyReport cmdlet to view supervisory review policy events in the Security & Compliance Center. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SupervisoryReviewPolicyReport [-EndDate <DateTime>] [-Page <Int32>] [-PageSize <Int32>] - [-Policies <MultiValuedProperty>] [-StartDate <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -For the reporting period you specify, the Get-SupervisoryReviewPolicyReport cmdlet returns the following information: - -- Organization - -- Date - -- Policy - -- Message Type - -- Tag Type: Messages that are eligible for evaluation by the policy are `InPurview`. Messages that match the conditions of the policy are `HitPolicy`. Classifications that are manually assigned to messages by the designated reviewers using the Supervision add-in for Outlook web app are `Compliant`, `Non-compliant`, `Questionable`, and `Resolved`. Messages that match the conditions of a policy but haven't been reviewed by a designated reviewer are `Not-Reviewed`. Messages that match the conditions of a policy and have been reviewed by a designated reviewer are `New-Reviewed`. - -- Item Count - -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-SupervisoryReviewPolicyReport -StartDate 03/01/2018 -EndDate 03/31/2018 -``` - -This example returns the supervisory review policy events for the month of March, 2018. - -### Example 2 -```powershell -Get-SupervisoryReviewPolicyReport -Policies "EU Brokers Policy" -``` - -This example returns the supervisory review policy events for the policy named EU Brokers Policy. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policies -The Policies parameter filters the results by the supervisory review policy. - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewReport.md b/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewReport.md deleted file mode 100644 index b46a4ccfd8..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewReport.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-supervisoryreviewreport -applicable: Office 365 Security & Compliance Center -title: Get-SupervisoryReviewReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-SupervisoryReviewReport - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-SupervisoryReviewReport cmdlet to view supervisory review events in the Security & Compliance Center. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SupervisoryReviewReport [-EndDate <DateTime>] [-Page <Int32>] [-PageSize <Int32>] - [-Policies <MultiValuedProperty>] [-Reviewers <MultiValuedProperty>] [-StartDate <DateTime>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-SupervisoryReviewReport -StartDate 03/01/2018 -EndDate 03/31/2018 -``` - -This example returns the supervisory review events for the month of March, 2018. - -### Example 2 -```powershell -Get-SupervisoryReviewPolicyReport -Policies "US Brokers Policy" -``` - -This example returns the supervisory review events for the policy named US Brokers Policy. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policies -The Policies parameter filters the results by the supervisory review policy. - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reviewers -The Reviewers parameter filters the results by the reviewers of the supervisory review policy. - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewTopCasesReport.md b/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewTopCasesReport.md deleted file mode 100644 index c49e0561d3..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-SupervisoryReviewTopCasesReport.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-supervisoryreviewtopcasesreport -applicable: Office 365 Security & Compliance Center -title: Get-SupervisoryReviewTopCasesReport -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "o365scc-ps" ---- - -# Get-SupervisoryReviewTopCasesReport - -## SYNOPSIS -This cmdlet is available only in Office 365 Security & Compliance Center PowerShell. For more information, see [Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/office-365-scc-powershell). - -Use the Get-SupervisoryReviewTopCasesReport cmdlet to view the current status of the top supervision policies configured in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-SupervisoryReviewTopCasesReport [-EndDate <System.DateTime>] [-Page <Int32>] [-PageSize <Int32>] - [-StartDate <System.DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see [Permissions in Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=511920). - -## EXAMPLES - -### Example 1 -```powershell -Get-SupervisoryReviewTopCasesReport | Sort-Object Policy | Format-Table Policy,Pending,Total,Date -``` -This example returns detailed information on supervisory policies, including the policy name, the total number of communications under review and pending, and the date of the report. - -## PARAMETERS - -### -EndDate -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". - -```yaml -Type: System.DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Page -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize -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: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -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". - -```yaml -Type: System.DateTime -Parameter Sets: (All) -Aliases: -Applicable: Office 365 Security & Compliance Center - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-TenantAnalyticsConfig.md b/exchange/exchange-ps/exchange/reporting/Get-TenantAnalyticsConfig.md deleted file mode 100644 index b9d54e5fd8..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-TenantAnalyticsConfig.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-tenantanalyticsconfig -applicable: Exchange Online -title: Get-TenantAnalyticsConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-TenantAnalyticsConfig - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -This cmdlet has been deprecated and no longer used. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-TenantAnalyticsConfig [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet has been deprecated and no longer used. - -## EXAMPLES - -### Example 1 -```powershell -Get-TenantAnalyticsConfig -``` -This cmdlet has been deprecated and no longer used. - -## 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Get-UserAnalyticsConfig.md b/exchange/exchange-ps/exchange/reporting/Get-UserAnalyticsConfig.md deleted file mode 100644 index d551f3e1de..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Get-UserAnalyticsConfig.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/get-useranalyticsconfig -applicable: Exchange Online -title: Get-UserAnalyticsConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-UserAnalyticsConfig - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-TenantAnalyticsConfig cmdlet to view the MyAnalytics privacy settings for cloud-based users. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-UserAnalyticsConfig -Identity <RecipientIdParameter> [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-UserAnalyticsConfig -Identity KathleenReiter@Contoso.com -``` - -This example returns the MyAnalytics privacy setting for the user with email address KathleenReiter@Contoso.com. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the user that you want to view. You can use any value that uniquely identifies the user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Set-TenantAnalyticsConfig.md b/exchange/exchange-ps/exchange/reporting/Set-TenantAnalyticsConfig.md deleted file mode 100644 index 0802f4aeaf..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Set-TenantAnalyticsConfig.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/set-tenantanalyticsconfig -applicable: Exchange Online -title: Set-TenantAnalyticsConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-TenantAnalyticsConfig - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -**This cmdlet has been deprecated and no longer used.** - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### MyAnalytics -``` -Set-TenantAnalyticsConfig -MinRecipients <Int32> - [<CommonParameters>] -``` - -### TeamAnalytics -``` -Set-TenantAnalyticsConfig -MinTeamSize <Int32> -TeamAnalyticsEnabled <Boolean> - [-MinRecipients <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet has been deprecated and no longer used. - -## EXAMPLES - -### Example 1 -```powershell -Set-TenantAnalyticsConfig -``` - -This cmdlet has been deprecated and no longer used. - -## PARAMETERS - -### -MinRecipients -This cmdlet has been deprecated and no longer used. - -```yaml -Type: Int32 -Parameter Sets: MyAnalytics -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -```yaml -Type: Int32 -Parameter Sets: TeamAnalytics -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -MinTeamSize -This cmdlet has been deprecated and no longer used. - -```yaml -Type: Int32 -Parameter Sets: TeamAnalytics -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamAnalyticsEnabled -This cmdlet has been deprecated and no longer used. - -```yaml -Type: Boolean -Parameter Sets: TeamAnalytics -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/reporting/Set-UserAnalyticsConfig.md b/exchange/exchange-ps/exchange/reporting/Set-UserAnalyticsConfig.md deleted file mode 100644 index 2fd1eef832..0000000000 --- a/exchange/exchange-ps/exchange/reporting/Set-UserAnalyticsConfig.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/reporting/set-useranalyticsconfig -applicable: Exchange Online -title: Set-UserAnalyticsConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-UserAnalyticsConfig - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-UserAnalyticsConfig cmdlet to modify the MyAnalytics privacy settings for cloud-based users. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### MyAnalytics -``` -Set-UserAnalyticsConfig -Identity <RecipientIdParameter> -PrivacyMode <String> - [<CommonParameters>] -``` - -### TeamAnalytics -``` -Set-UserAnalyticsConfig -Identity <RecipientIdParameter> -TeamAnalyticsEnabled <Boolean> - [-PrivacyMode <String>] - [-TeamAnalyticsManagerViewEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-UserAnalyticsConfig -Identity "Kathleen Reiter" -PrivacyMode OptIn -``` - -This example sets the MyAnalytics privacy setting to OptIn for the user named Kathleen Reiter. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the user that you want to modify. You can use any value that uniquely identifies the user. For example: For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -PrivacyMode -The PrivacyMode parameter specifies the MyAnalytics privacy setting for the user. Valid values are: - -- Excluded - -- Opt-In - -- Opt-Out - -```yaml -Type: String -Parameter Sets: MyAnalytics -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: TeamAnalytics -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -TeamAnalyticsEnabled -PARAMVALUE: Boolean - -```yaml -Type: Boolean -Parameter Sets: TeamAnalytics -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamAnalyticsManagerViewEnabled -PARAMVALUE: Boolean - -```yaml -Type: Boolean -Parameter Sets: TeamAnalytics -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/role-based-access-control/Add-RoleGroupMember.md b/exchange/exchange-ps/exchange/role-based-access-control/Add-RoleGroupMember.md deleted file mode 100644 index e56ae4e1d6..0000000000 --- a/exchange/exchange-ps/exchange/role-based-access-control/Add-RoleGroupMember.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/add-rolegroupmember -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Add-RoleGroupMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Add-RoleGroupMember - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Add-RoleGroupMember cmdlet to add members to a management role group. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Add-RoleGroupMember [-Identity] <RoleGroupIdParameter> -Member <SecurityPrincipalIdParameter> - [-BypassSecurityGroupManagerCheck] [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -When you add a member to a role group, that mailbox, universal security group (USG), or computer is given the effective permissions provided by the management roles assigned to the role group. - -If the ManagedBy property has been populated with role group managers, the user adding a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. - -If the role group is a linked role group, you can't use the Add-RoleGroupMember cmdlet to add members to the role group. Instead, you need to add members to the foreign USG that's linked to the linked role group. To find the foreign USG that's linked to a role group, use the Get-RoleGroup cmdlet. - -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Add-RoleGroupMember "Recipient Management" -Member David -``` - -This example adds the user David to the role group Recipient Management. - -### Example 2 -```powershell -Get-User -Filter "Department -eq 'Sales' -and RecipientType -eq 'UserMailbox'" | Get-Mailbox | Add-RoleGroupMember "Sales and Marketing Group" -WhatIf -``` - -This example finds all the mailboxes that are part of the Sales department and adds them to the Sales and Marketing Group role group. Because we're using the WhatIf switch, the changes aren't written to the role group, so you can verify that the correct members will be added. - -After you've verified that the correct members will be added to the role group, remove the WhatIf switch and run the command again. - -For more information about pipelining and the WhatIf parameter, see the following topics: - -- [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) - -- WhatIf, Confirm and ValidateOnly switches - -### Example 3 -```powershell -Add-RoleGroupMember "Training Administrators" -Member "Training Assistants" -BypassSecurityGroupManagerCheck -``` - -This example adds the Training Assistants USG to the Training Administrators role group. Because the user running the command wasn't added to the ManagedBy property of the role group, the BypassSecurityGroupManagerCheck switch must be used. The user is assigned the Role Management role, which enables the user to bypass the security group manager check. - -## PARAMETERS - -### -Identity -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Member -The Member parameter specifies the mailbox, USG, or computer to add to a role group. You can only specify one member at a time. If the member name contains spaces, enclose the name in quotation marks ("). - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch enables a user who hasn't been added to the ManagedBy property to add a member to a role group. The user must be a member of the Organization Management role group or be assigned, either directly or indirectly, the Role Management role. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/role-based-access-control/Get-ManagementRole.md b/exchange/exchange-ps/exchange/role-based-access-control/Get-ManagementRole.md deleted file mode 100644 index f6af634c36..0000000000 --- a/exchange/exchange-ps/exchange/role-based-access-control/Get-ManagementRole.md +++ /dev/null @@ -1,280 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/get-managementrole -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Get-ManagementRole -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Get-ManagementRole - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-ManagementRole cmdlet to view management roles that have been created in your organization. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### GetChildren -``` -Get-ManagementRole [-Identity] <RoleIdParameter> [-GetChildren] - [-DomainController <Fqdn>] - [-RoleType <RoleType>] [<CommonParameters>] -``` - -### Recurse -``` -Get-ManagementRole [-Identity] <RoleIdParameter> [-Recurse] - [-DomainController <Fqdn>] - [-RoleType <RoleType>] [<CommonParameters>] -``` - -### Identity -``` -Get-ManagementRole [[-Identity] <RoleIdParameter>] [-Cmdlet <String>] [-CmdletParameters <String[]>] - [-DomainController <Fqdn>] - [-RoleType <RoleType>] [<CommonParameters>] -``` - -### Script -``` -Get-ManagementRole [[-Identity] <RoleIdParameter>] [-Script <String>] [-ScriptParameters <String[]>] - [-DomainController <Fqdn>] - [-RoleType <RoleType>] - [<CommonParameters>] -``` - -## DESCRIPTION -You can view management roles in several ways, from listing all the roles in your organization to listing only the child roles of a specified parent role. You can also view the details of a specific role by piping the output of the Get-ManagementRole cmdlet to the Format-List cmdlet. - -For more information about management roles, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-ManagementRole -``` - -This example lists all the roles that have been created in your organization. - -### Example 2 -```powershell -Get-ManagementRole "Mail Recipients" -Recurse -``` - -This example lists all the roles that are children of the Mail Recipients management role. The command performs a recursive query of all the child roles of the specified parent role. This recursive query finds every child role from the immediate children of the parent to the last child role in the hierarchy. In a recursive list, the parent role is also returned in the list. - -### Example 3 -```powershell -Get-ManagementRole -CmdletParameters Identity, Database -``` - -This example lists all the roles that contain both the Identity and Database parameters. Roles that contain only one parameter or the other aren't returned. - -### Example 4 -```powershell -Get-ManagementRole -RoleType UnScopedTopLevel -``` - -This example lists all the roles that have a type of UnScopedTopLevel. These roles contain custom scripts or non-Exchange cmdlets. - -### Example 5 -```powershell -Get-ManagementRole "Transport Rules" | Format-List Name, RoleType -``` - -This example retrieves only the Transport Rules role and passes the output of the Get-ManagementRole cmdlet to the Format-List cmdlet. The Format-List cmdlet then shows only the Name and RoleType properties of the Transport Rules role. For more information about pipelining and the Format-List cmdlet, see [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) and [Working with command output](https://docs.microsoft.com/exchange/working-with-command-output-exchange-2013-help). - -### Example 6 -```powershell -Get-ManagementRole "Mail Recipients" -GetChildren -``` - -This example lists the immediate children of the Mail Recipients role. Only the child roles that hold the Mail Recipients role as their parent role are returned. The Mail Recipients role isn't returned in the list. - -## PARAMETERS - -### -Identity -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 -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -GetChildren -The GetChildren parameter retrieves a list of all the roles that were created based on the parent role specified in the Identity parameter. Only the immediate child roles of the parent role are included. The GetChildren parameter can only be used with the Identity and RoleType parameters. - -```yaml -Type: SwitchParameter -Parameter Sets: GetChildren -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Recurse -The Recurse parameter retrieves a list of all the roles that were created based on the parent role specified in the Identity parameter. The role specified in the Identity parameter, its child roles, and their children are returned. The Recurse parameter can only be used with the Identity and RoleType parameters. - -```yaml -Type: SwitchParameter -Parameter Sets: Recurse -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Cmdlet -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CmdletParameters -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoleType -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://docs.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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Script -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScriptParameters -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/role-based-access-control/Get-RoleGroup.md b/exchange/exchange-ps/exchange/role-based-access-control/Get-RoleGroup.md deleted file mode 100644 index 3804ec3fa3..0000000000 --- a/exchange/exchange-ps/exchange/role-based-access-control/Get-RoleGroup.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/get-rolegroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Get-RoleGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Get-RoleGroup - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-RoleGroup cmdlet to retrieve a list of management role groups. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-RoleGroup [[-Identity] <RoleGroupIdParameter>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-ShowPartnerLinked] - [-SortBy <String>] [<CommonParameters>] -``` - -## DESCRIPTION -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-RoleGroup -``` - -This example retrieves a list of role groups. - -### Example 2 -```powershell -Get-RoleGroup "Recipient Administrators" | Format-List -``` - -This example retrieves the details for the Recipient Administrators role group. - -### Example 3 -```powershell -Get-RoleGroup -ReadFromDomainController -``` - -This example retrieves a list of role groups as seen by the domain controller closest to the user. - -### Example 4 -```powershell -Get-RoleGroup -Filter "RoleGroupType -eq 'Linked'" | Format-Table Name, LinkedGroup -``` - -This example retrieves a list of all linked role groups and the Active Directory security identifier (SID) of the foreign universal security groups (USG) that are linked to each of them. You can then use the SIDs to find the USGs so you can modify their members. - -## PARAMETERS - -### -Identity -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. - -```yaml -Type: RoleGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -You can filter on the following properties: - -- LinkedGroup - -- ManagedBy - -- Members - -- Name - -- RoleGroupType (the available values are Standard and Linked) - -- DisplayName - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowPartnerLinked -This parameter is available only in the cloud-based service. - -This ShowPartnerLinked switch specifies whether to return built-in role groups that are of type PartnerRoleGroup. Role groups of this type are used in the cloud-based services to allow partner service providers to manage their customer organizations. These role groups can't be edited and are therefore not shown by default. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/role-based-access-control/Get-RoleGroupMember.md b/exchange/exchange-ps/exchange/role-based-access-control/Get-RoleGroupMember.md deleted file mode 100644 index 1c82a0dbe5..0000000000 --- a/exchange/exchange-ps/exchange/role-based-access-control/Get-RoleGroupMember.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/get-rolegroupmember -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Get-RoleGroupMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Get-RoleGroupMember - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-RoleGroupMember cmdlet to retrieve a list of members of a management role group. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-RoleGroupMember [-Identity] <RoleGroupMemberIdParameter> [-DomainController <Fqdn>] - [-ReadFromDomainController] [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-RoleGroupMember "Recipient Administrators" -``` - -This example retrieves a list of all the members of the Recipient Administrators role group. - -### Example 2 -```powershell -Get-RoleGroupMember "Organization Administrators" -ReadFromDomainController -``` - -This example retrieves a list of all the members of the Organization Administrators role group as seen by the domain controller closest to the user running the command. - -## PARAMETERS - -### -Identity -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/role-based-access-control/Remove-ManagementRoleEntry.md b/exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRoleEntry.md deleted file mode 100644 index d0ff57308e..0000000000 --- a/exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRoleEntry.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Remove-ManagementRoleEntry - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-ManagementRoleEntry cmdlet to remove existing management role entries. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-ManagementRoleEntry [-Identity] <RoleEntryIdParameter> [-Confirm] [-DomainController <Fqdn>] [-Force] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Remove-ManagementRoleEntry cmdlet removes existing role entries. However, you can't remove role entries from built-in management roles. - -For more information about management role entries, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-ManagementRoleEntry "Tier 1 Help Desk\New-Mailbox" -``` - -This example removes the New-Mailbox role entry from the Tier 1 Help Desk role. - -### Example 2 -```powershell -Get-ManagementRoleEntry "Tier 1 Help Desk\*" | Where-Object {$_.Name -like 'New-*'} | %{Remove-ManagementRoleEntry -Identity "$($_.id)\$($_.name)"} -``` - -This example removes all the role entries that have the verb New on the Tier 1 Help Desk role by piping the output of the Get-ManagementRoleEntry cmdlet to the Where-Object cmdlet which specifies the verb filter and then, these results are being piped to Remove-ManagementRoleEntry cmdlet. - -This example forces you to acknowledge the command before proceeding. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the role entry to remove. You must specify the value of the Identity parameter in the format, \<management role\>\\\<role entry name\>, for example, ExampleRole\\Set-Mailbox. - -For more information about how management role entries work, see [Understanding management roles](https://docs.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). - -If the role entry name contains spaces, enclose the name in quotation marks ("). - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/role-based-access-control/Remove-RoleGroup.md b/exchange/exchange-ps/exchange/role-based-access-control/Remove-RoleGroup.md deleted file mode 100644 index 4e1f268f09..0000000000 --- a/exchange/exchange-ps/exchange/role-based-access-control/Remove-RoleGroup.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/remove-rolegroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Remove-RoleGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Remove-RoleGroup - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-RoleGroup cmdlet to remove a management role group. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-RoleGroup [-Identity] <RoleGroupIdParameter> [-BypassSecurityGroupManagerCheck] [-Confirm] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -When you remove a role group, all the management role assignments assigned management roles to the role group are also removed. The management roles aren't removed. Members of a removed role group can no longer manage a feature if the role group was the only means by which they were granted access to the feature. - -You can't remove built-in role groups. - -If the ManagedBy property has been populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. - -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-RoleGroup "Training Administrators" -``` - -This example removes the Training Administrators role group. - -### Example 2 -```powershell -Remove-RoleGroup "Vancouver Recipient Administrators" -BypassSecurityGroupManagerCheck -``` - -This example removes the Vancouver Recipient Administrators role group. Because the user running the command wasn't added to the ManagedBy property of the role group, the BypassSecurityGroupManagerCheck switch must be used. The user is assigned the Role Management role, which enables the user to bypass the security group manager check. - -## PARAMETERS - -### -Identity -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch enables a user who hasn't been added to the ManagedBy property to remove a role group. The user must be a member of the Organization Management role group or be assigned, either directly or indirectly, the Role Management role. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/role-based-access-control/Remove-RoleGroupMember.md b/exchange/exchange-ps/exchange/role-based-access-control/Remove-RoleGroupMember.md deleted file mode 100644 index e95236672e..0000000000 --- a/exchange/exchange-ps/exchange/role-based-access-control/Remove-RoleGroupMember.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/role-based-access-control/remove-rolegroupmember -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Remove-RoleGroupMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Remove-RoleGroupMember - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-RoleGroupMember cmdlet to remove a member of a management role group. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-RoleGroupMember [-Identity] <RoleGroupIdParameter> -Member <SecurityPrincipalIdParameter> - [-BypassSecurityGroupManagerCheck] [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -When you remove a member from a role group, that member can no longer manage the features made available by the role group if the role group is the only means by which the member is granted access to the feature. - -If the ManagedBy property has been populated with role group managers, the user removing a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. - -If the role group is a linked role group, you can't use the Remove-RoleGroupMember cmdlet to remove members from the role group. Instead, you need to remove members from the foreign universal security group (USG) linked to the linked role group. To find the foreign USG linked to a role group, use the Get-RoleGroup cmdlet. - -For more information about role groups, see [Understanding management role groups](https://docs.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-RoleGroupMember "Recipient Management" -Member David -``` - -This example removes the user David from the role group Recipient Management. - -### Example 2 -```powershell -Get-User -Filter "Department -eq 'Sales' -and -RecipientType -eq 'UserMailbox'" | Get-Mailbox | Remove-RoleGroupMember "Sales and Marketing Group" -WhatIf -``` - -This example finds all the mailboxes that are part of the Sales department and removes them from the Sales and Marketing Group role group. Because we're using the WhatIf switch, the changes aren't written to the role group, so you can verify that the correct members will be removed. - -After you've verified that the correct members will be removed the role group, remove the WhatIf switch and run the command again. - -For more information about pipelining, and the WhatIf parameter, see the following topics: - -- [About Pipelines](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines) - -- WhatIf, Confirm and ValidateOnly switches - -### Example 3 -```powershell -Remove-RoleGroupMember "Training Administrators" -Member "Training Assistants" -BypassSecurityGroupManagerCheck -``` - -This example removes the Training Assistants USG from the Training Administrators role group. Because the user running the command wasn't added to the ManagedBy property of the role group, the BypassSecurityGroupManagerCheck switch must be used. The user is assigned the Role Management role, which enables the user to bypass the security group manager check. - -## PARAMETERS - -### -Identity -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Member -The Member parameter specifies the mailbox or USG to remove from a role group. You can only specify one member at a time. If the member name contains spaces, enclose the name in quotation marks ("). - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -BypassSecurityGroupManagerCheck -The BypassSecurityGroupManagerCheck switch enables a user who hasn't been added to the ManagedBy property to remove a member from a role group. The user must be a member of the Organization Management role group or be assigned, either directly or indirectly, the Role Management role. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter doesn't work in the Office 365 Security & Compliance Center. - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/server-health-and-performance/Set-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/exchange/server-health-and-performance/Set-ThrottlingPolicyAssociation.md deleted file mode 100644 index ab33551cbc..0000000000 --- a/exchange/exchange-ps/exchange/server-health-and-performance/Set-ThrottlingPolicyAssociation.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/server-health-and-performance/set-throttlingpolicyassociation -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ThrottlingPolicyAssociation -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019" ---- - -# Set-ThrottlingPolicyAssociation - -## SYNOPSIS -This cmdlet is available only in on-premises Exchange. - -Use the Set-ThrottlingPolicyAssociation cmdlet to associate a throttling policy with a specific object. The object can be a user with a mailbox, a user without a mailbox, a contact or a computer account. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-ThrottlingPolicyAssociation [-Identity] <ThrottlingPolicyAssociationIdParameter> [-Confirm] - [-DomainController <Fqdn>] [-IgnoreDefaultScope] [-ThrottlingPolicy <ThrottlingPolicyIdParameter>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Set-ThrottlingPolicyAssociation cmdlet defines quota limits for specific objects. For example, if you notice that a user or other object is using excessive bandwidth, you can associate that object with a throttling policy that's more restrictive. - -In data center deployments, the object referred to by the Identity and ThrottlingPolicy parameters must be in the same tenant. - -For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://docs.microsoft.com/Exchange/server-health/workload-management). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-ThrottlingPolicyAssociation -Identity tonysmith -ThrottlingPolicy ITStaffPolicy -``` - -This example associates a user with a username of tonysmith to the throttling policy ITStaffPolicy that has higher limits. - -### Example 2 -```powershell -$b = Get-ThrottlingPolicy ITStaffPolicy; -Set-Mailbox -Identity tonysmith -ThrottlingPolicy $b -``` - -You don't need to use the Set-ThrottlingPolicyAssociation cmdlet to associate a user with a policy. The following commands show another way to associate tonysmith to the throttling policy ITStaffPolicy. - -## PARAMETERS - -### -Identity -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data 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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -This parameter is available or functional only in Exchange Server 2010. - -The IgnoreDefaultScope parameter instructs the command to ignore the default recipient scope setting for the Exchange Management Shell session and use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently in the default scope. Using the IgnoreDefaultScope parameter introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the distinguished name (DN) for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThrottlingPolicy -The ThrottlingPolicy parameter specifies the throttling policy that you want to be associated with the object specified by the Identity parameter. - -```yaml -Type: ThrottlingPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/sharing-and-collaboration/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/exchange/sharing-and-collaboration/Add-AvailabilityAddressSpace.md deleted file mode 100644 index dd08a83403..0000000000 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Add-AvailabilityAddressSpace.md +++ /dev/null @@ -1,249 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/add-availabilityaddressspace -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Add-AvailabilityAddressSpace -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Add-AvailabilityAddressSpace - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Add-AvailabilityAddressSpace cmdlet to create availability address space objects that are used to share free/busy data across Exchange organizations. - -The maximum number off Availability address spaces returned by Active Directory to Exchange is 100. We recommend using 100 or fewer address spaces in order for Availability lookups to work properly. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Add-AvailabilityAddressSpace -AccessMethod <AvailabilityAccessMethod> - -ForestName <String> [-Confirm] [-Credentials <PSCredential>] [-DomainController <Fqdn>] [-ProxyUrl <Uri>] - [-UseServiceAccount <Boolean>] [-WhatIf] [-TargetAutodiscoverEpr <Uri>] [<CommonParameters>] -``` - -## DESCRIPTION -In Exchange Online, you need to run the New-AvailabilityConfig cmdlet before you run the Add-AvailabilityAddressSpace cmdlet. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Add-AvailabilityAddressSpace -ForestName example.contoso.com -AccessMethod OrgWideFB -Credentials (Get-Credential) -``` - -This example is useful with an untrusted cross-forest Availability service, or if detailed cross-forest free/busy service isn't desired. Enter a username and password when you're prompted by the command. For an untrusted cross-forest configuration, make sure that the user doesn't have a mailbox. - -### Example 2 -```powershell -Add-AvailabilityAddressSpace -ForestName example.contoso.com -AccessMethod PerUserFB -Credentials (Get-Credential) -``` - -This example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest, and the specified account connects to the contoso.com forest. The specified account must be an existing account in the contoso.com forest. - -### Example 3 -```powershell -Add-AvailabilityAddressSpace -ForestName example.contoso.com -AccessMethod PerUserFB -UseServiceAccount $true -``` - -This example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest and uses the service account (typically the local system account or the computer account) to connect to the contoso.com forest. Because the service is trusted, there is no issue with authorization when the current forest tries to retrieve free/busy information from contoso.com. - -## PARAMETERS - -### -AccessMethod -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. - -- OrgWideFB: Only default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter. - -- OrgWideFBBasic: This value is reserved for internal Microsoft use. - -- InternalProxy: The request is proxied to an Exchange in the site that has a later version of Exchange. - -- PublicFolder: This value was used to access free/busy data on Exchange Server 2003 servers. - -```yaml -Type: AvailabilityAccessMethod -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForestName -The ForestName parameter specifies the SMTP domain name of the target forest for users whose free/busy data must be retrieved. If your 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 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credentials -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProxyUrl -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 its 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 value of the AccessMethod parameter to InternalProxy. - -This parameter required that you created the proper trust relationships and sharing relationships between the Exchange organizations. For more information, see [New-FederationTrust](https://docs.microsoft.com/powershell/module/exchange/federation-and-hybrid/new-federationtrust). - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseServiceAccount -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 - -- $true: The local Availability service account is used for authorization. - -- $false: The local Availability service account isn't used for authorization. You need to use the Credentials 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetAutodiscoverEpr -The TargetAutodiscoverEpr parameter specifies the Autodiscover URL of Exchange Web Services for the external organization, 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/sharing-and-collaboration/Get-AvailabilityConfig.md b/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-AvailabilityConfig.md deleted file mode 100644 index 7276faa59f..0000000000 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Get-AvailabilityConfig.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-AvailabilityConfig - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-AvailabilityConfig cmdlet to retrieve the accounts that are trusted in the cross-forest exchange of free/busy information. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-AvailabilityConfig [[-Identity] <OrganizationIdParameter>] [-DomainController <Fqdn>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-AvailabilityConfig cmdlet lists the accounts that have permissions to issue proxy availability service requests on an organizational or per-user basis. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-AvailabilityConfig -``` - -This example retrieves the accounts that are trusted in the cross-forest exchange of free/busy information. - -### Example 2 -```powershell -Get-AvailabilityConfig -Identity <AvailabilityConfig Value> -``` - -This example retrieves the accounts that are trusted in the cross-forest exchange of free/busy information. This example is scoped to return only the results of the specified Identity parameter. - -## PARAMETERS - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the availability configuration to be retrieved. - -```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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/sharing-and-collaboration/New-AvailabilityConfig.md b/exchange/exchange-ps/exchange/sharing-and-collaboration/New-AvailabilityConfig.md deleted file mode 100644 index 6858d4aff4..0000000000 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/New-AvailabilityConfig.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/new-availabilityconfig -applicable: Exchange Online -title: New-AvailabilityConfig -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# New-AvailabilityConfig - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-AvailabilityConfig cmdlet to create an availability configuration. An availability configuration specifies an existing account that's used to exchange free/busy information between organizations. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-AvailabilityConfig -OrgWideAccount <SecurityPrincipalIdParameter> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-AvailabilityConfig -OrgWideAccount "Tony Smith" -``` - -This example creates a new availability configuration. The existing account named Tony Smith will be used to exchange free/busy information between organizations. - -## PARAMETERS - -### -OrgWideAccount -The OrgWideAccount parameter specifies an account or security group that has permission to issue proxy Availability service requests on an organization-wide basis. - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/sharing-and-collaboration/Set-AvailabilityConfig.md b/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-AvailabilityConfig.md deleted file mode 100644 index 10f0ac16eb..0000000000 --- a/exchange/exchange-ps/exchange/sharing-and-collaboration/Set-AvailabilityConfig.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/sharing-and-collaboration/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-AvailabilityConfig - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-AvailabilityConfig cmdlet to set the access level for free/busy information. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-AvailabilityConfig [-Confirm] [-DomainController <Fqdn>] [-OrgWideAccount <SecurityPrincipalIdParameter>] - [-PerUserAccount <SecurityPrincipalIdParameter>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-AvailabilityConfig cmdlet defines two accounts or security groups: a per-user free/busy proxy account or group, and an organization-wide free/busy proxy account or group. These accounts and groups are trusted by all availability services in the current organization for availability proxy requests. - -For cross-forest availability services to retrieve free/busy information in the current forest, they must be using one of the specified accounts, belong to one of the specified security groups, or have a username and password for one of the specified accounts or security groups. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-AvailabilityConfig -PerUserAccount <domain name of servers group in remote forest> -``` - -This example is useful with a trusted cross-forest Availability service. If the remote forest is trusted, and a per-user free/busy proxy account or group in the remote forest is configured to use the service account, the configuration is added to the current forest to authorize the Microsoft ActiveSync request from the remote forest. - -### Example 2 -```powershell -Set-AvailabilityConfig -OrgWideAccount <ExampleCredentials> -``` - -This example is useful if the remote forest isn't trusted. Because this account is used for a cross-forest free/busy proxy account or group, minimize security vulnerabilities by using the credentials of a user who doesn't have an Exchange mailbox. When you're prompted, type the username and password. - -## PARAMETERS - -### -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. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrgWideAccount -The OrgWideAccount parameter specifies an account or security group that has permission to issue proxy Availability service requests on an organization-wide basis. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PerUserAccount -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. - -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/unified-messaging/Get-OnlineMeetingConfiguration.md b/exchange/exchange-ps/exchange/unified-messaging/Get-OnlineMeetingConfiguration.md deleted file mode 100644 index c260e96320..0000000000 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-OnlineMeetingConfiguration.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-onlinemeetingconfiguration -applicable: Exchange Online -title: Get-OnlineMeetingConfiguration -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-OnlineMeetingConfiguration - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-OnlineMeetingConfiguration cmdlet to view status and usage information about Skype Meetings and Skype for Business Online for mailboxes. Skype Meetings automatically includes Skype for Business Online conference join information in Exchange Online meeting invitations. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-OnlineMeetingConfiguration [-Identity] <MailboxIdParameter> [<CommonParameters>] -``` - -## DESCRIPTION -Exchange Online maintains a per-user cache of Skype for Business Online meeting information that's updated every 24 hours. The Get-OnlineMeetingConfiguration cmdlet provides the following information about the Skype Meetings configuration and the Skype for Business Online meeting information for the user: - -- IsAutoOnlineMeetingEnabled: Indicates if Skype Meetings is enabled for the mailbox. - -- OnlineMeetingInfo: Skype for Business Online meeting coordinates. - -- LastSyncTime: The last time Exchange Online successfully synchronized meeting coordinates from Skype for Business Online. - -- LastSuccessfulSyncTime: The last time Exchange Online successfully cleaned the cached of used Skype for Business Online meeting coordinates. - -To enable and disable Skype Meetings for an Office 365 organization, you use the EnableAutoSchedule parameter on the Set-CsCloudMeetingConfiguration cmdlet in Skype for Business Online PowerShell. After you enable Skype Meetings in the organization, you can enable or disable it on specific users by using the Grant-CsCloudMeetingPolicy cmdlet in Skype for Business Online PowerShell. For more information, see the following Skype for Business Online PowerShell topics: - -- [Set-CsCloudMeetingConfiguration](https://go.microsoft.com/fwlink/p/?LinkId=826065) - -- [Grant-CsCloudMeetingPolicy](https://go.microsoft.com/fwlink/p/?LinkId=826066) - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-OnlineMeetingConfiguration -Identity carlam@fourthcoffee.com -``` - -This example gets the Skype Meetings configuration for the specified mailbox. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/unified-messaging/Get-UMMailbox.md b/exchange/exchange-ps/exchange/unified-messaging/Get-UMMailbox.md deleted file mode 100644 index 69312786b4..0000000000 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMMailbox.md +++ /dev/null @@ -1,326 +0,0 @@ ---- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-ummailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-UMMailbox -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-UMMailbox - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-UMMailbox cmdlet to view existing mailboxes that are Unified Messaging (UM) enabled. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnrSet -``` -Get-UMMailbox [-Anr <String>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -### Identity -``` -Get-UMMailbox [[-Identity] <MailboxIdParameter>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-UMMailbox -``` - -This example displays a summary list of all the UM-enabled mailboxes in your organization. - -### Example 2 -```powershell -Get-UMMailbox -Identity tonysmith@contoso.com | Format-List -``` - -This example displays detailed information for the UM-enabled mailbox for tonysmith@contoso.com. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -This parameter is available only in on-premises Exchange. - -The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. - -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationalUnit -This parameter is available only in on-premises Exchange. - -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: OrganizationalUnitIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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: (All) -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 -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- ServerLegacyDN - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/unified-messaging/Get-UMMailboxPIN.md b/exchange/exchange-ps/exchange/unified-messaging/Get-UMMailboxPIN.md deleted file mode 100644 index eb27713f48..0000000000 --- a/exchange/exchange-ps/exchange/unified-messaging/Get-UMMailboxPIN.md +++ /dev/null @@ -1,218 +0,0 @@ ---- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/get-ummailboxpin -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-UMMailboxPIN -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-UMMailboxPin - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-UMMailboxPIN cmdlet to return information from a Unified Messaging (UM)-enabled user's mailbox. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-UMMailboxPin [[-Identity] <MailboxIdParameter>] [-Credential <PSCredential>] [-DomainController <Fqdn>] - [-IgnoreDefaultScope] [-IgnoreErrors] [-ReadFromDomainController] - [-ResultSize <Unlimited>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-UMMailboxPIN cmdlet returns information calculated from the PIN data stored in encrypted form in the user's mailbox. This cmdlet also shows whether the mailbox or user access has been locked out. - -After this task is completed, you can view information on a user's mailbox. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-UMMailboxPIN -``` - -This example displays the UM mailbox PIN-related properties for all UM-enabled users. - -### Example 2 -```powershell -Get-UMMailboxPIN -Identity tonysmith@contoso.com -``` - -This example displays the UM mailbox PIN-related properties for tonysmith@contoso.com. - -## PARAMETERS - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreErrors -The IgnoreErrors switch specifies whether errors that may occur when running this cmdlet are written as warnings. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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: (All) -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 -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/unified-messaging/Set-UMMailbox.md b/exchange/exchange-ps/exchange/unified-messaging/Set-UMMailbox.md deleted file mode 100644 index b16c0f6efa..0000000000 --- a/exchange/exchange-ps/exchange/unified-messaging/Set-UMMailbox.md +++ /dev/null @@ -1,572 +0,0 @@ ---- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/unified-messaging/set-ummailbox -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-UMMailbox -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Set-UMMailbox - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-UMMailbox cmdlet to set the Unified Messaging (UM) properties for a user who is currently UM-enabled. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-UMMailbox [-Identity] <MailboxIdParameter> [-AirSyncNumbers <MultiValuedProperty>] - [-AllowUMCallsFromNonUsers <AllowUMCallsFromNonUsersFlags>] [-AnonymousCallersCanLeaveMessages <Boolean>] - [-AutomaticSpeechRecognitionEnabled <Boolean>] [-CallAnsweringAudioCodec <AudioCodecEnum>] - [-CallAnsweringRulesEnabled <Boolean>] [-Confirm] [-DomainController <Fqdn>] - [-FaxEnabled <Boolean>] [-IgnoreDefaultScope] [-MissedCallNotificationEnabled <Boolean>] - [-Name <String>] [-OperatorNumber <String>] [-PhoneNumber <String>] [-PhoneProviderId <String>] - [-PinlessAccessToVoiceMailEnabled <Boolean>] [-PlayOnPhoneEnabled <Boolean>] - [-SubscriberAccessEnabled <Boolean>] [-TUIAccessToCalendarEnabled <Boolean>] - [-TUIAccessToEmailEnabled <Boolean>] [-UMMailboxPolicy <MailboxPolicyIdParameter>] - [-UMSMSNotificationOption <UMSMSNotificationOptions>] [-VerifyGlobalRoutingEntry] [-WhatIf] - [-ImListMigrationCompleted <Boolean>] [-VoiceMailAnalysisEnabled <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-UMMailbox cmdlet sets UM properties associated with a user who has been UM-enabled. Many of the UM properties for the user are stored on the user's mailbox, and other UM properties for the user are stored in Active Directory. - -After this task is completed, the parameters and values specified are configured on the UM mailbox. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-UMMailbox -Identity tony@contoso.com -CallAnsweringAudioCodec Wma -CallAnsweringRulesEnabled $false -FaxEnabled $false -UMSMSNotificationOption VoiceMail -``` - -This example configures a UM-enabled user, tony@contoso.com with the following settings: - -Changes the call answering audio codec to Wma - -Disables call answering rules - -Prevents him from receiving incoming faxes - -Enables voice mail notifications but not missed call notifications using text messaging - -### Example 2 -```powershell -Set-UMMailbox -Identity tony@contoso.com -TUIAccessToCalendarEnabled $false -TUIAccessToEmailEnabled $false -``` - -This example prevents the user tony@contoso.com from accessing his calendar and email when he's using Outlook Voice Access. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the mailbox tht you want to modify. You can use any value that uniquely identifies the mailbox. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AirSyncNumbers -This parameter is available or functional only in Exchange Server 2010. - -The AirSyncNumbers parameter specifies whether to register a mobile phone number with a hosted voice mail service. Each UM mailbox can have up to three numbers defined and numbers must be in E.164 format. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUMCallsFromNonUsers -The AllowUMCallsFromNonUsers parameter specifies whether to exclude the mailbox from directory searches. - -```yaml -Type: AllowUMCallsFromNonUsersFlags -Parameter Sets: (All) -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 -``` - -### -AnonymousCallersCanLeaveMessages -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutomaticSpeechRecognitionEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallAnsweringAudioCodec -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallAnsweringRulesEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FaxEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MissedCallNotificationEnabled -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OperatorNumber -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneNumber -This parameter is available only in the cloud-based service. - -The PhoneNumber parameter specifies whether to assign a phone number to a UM-enabled user. This is only used for E.164 consumer dial plans. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneProviderId -This parameter is available only in the cloud-based service. - -The PhoneProviderId parameter specifies the user's phone number and mobile service provider. This information is used to provide custom call forwarding and cancelling voice mail setup instructions based on the mobile phone provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PinlessAccessToVoiceMailEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PlayOnPhoneEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAccessEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TUIAccessToCalendarEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TUIAccessToEmailEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UMMailboxPolicy -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UMSMSNotificationOption -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VerifyGlobalRoutingEntry -This parameter is available only in the cloud-based service. - -The VerifyGlobalRoutingEntry parameter specifies the phone number has been successfully registered in the global routing database. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImListMigrationCompleted -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: - -- $true: The user's Lync or Skype for Business contact list is stored in their Exchange 2016 mailbox. This prevents you from migrating the mailbox back to an Exchange 2010 server. - -- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This is the default value. - -Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://go.microsoft.com/fwlink/p/?LinkID=313550). - -If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list has been moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VoiceMailAnalysisEnabled -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, Exchange Server 2019, Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Add-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/users-and-groups/Add-UnifiedGroupLinks.md deleted file mode 100644 index 36c390346b..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Add-UnifiedGroupLinks.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/add-unifiedgrouplinks -applicable: Exchange Online, Exchange Online Protection -title: Add-UnifiedGroupLinks -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps || eop-ps" ---- - -# Add-UnifiedGroupLinks - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Add-UnifiedGroupLinks cmdlet to add members, owners and subscribers to Office 365 groups in your cloud-based organization. To remove members, owners and subscribers, use the Remove-UnifiedGroupLinks cmdlet. To modify other properties of Office 365 groups, use the Set-UnifiedGroup cmdlet. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Add-UnifiedGroupLinks [-Identity] <UnifiedGroupIdParameter> -Links <RecipientIdParameter[]> - -LinkType <LinkType> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 groups are group objects that are available across Office 365 services. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -> [!NOTE] -> Only members can be owners of a group, so you must first add a user as member before adding it as an owner. - -## EXAMPLES - -### Example 1 -```powershell -Add-UnifiedGroupLinks -Identity "Legal Department" -LinkType Members -Links chris@contoso.com,michelle@contoso.com -``` - -This example adds members chris@contoso.com and michelle@contoso.com to the Office 365 Group named Legal Department. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Office 365 Group that you want to modify. You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: UnifiedGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Links -The Links parameter specifies the recipients to add to the Office 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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LinkType -The LinkType parameter specifies the Office 365 Group property that you want to modify. Valid values are: - -- Members - -- Owners - -- Subscribers - -```yaml -Type: LinkType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-DistributionGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Get-DistributionGroup.md deleted file mode 100644 index 6b94ea0850..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-DistributionGroup.md +++ /dev/null @@ -1,401 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Get-DistributionGroup - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-DistributionGroup cmdlet to view existing distribution groups or mail-enabled security groups. To view the members of a group, use the Get-DistributionGroupMember cmdlet. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnrSet -``` -Get-DistributionGroup [-Anr <String>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -### Identity -``` -Get-DistributionGroup [[-Identity] <DistributionGroupIdParameter>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -### ManagedBySet -``` -Get-DistributionGroup [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-ManagedBy <GeneralRecipientIdParameter>] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DistributionGroup -``` - -This examples returns a summary list of all distribution groups and mail-enabled security groups in your organization. - -### Example 2 -```powershell -Get-DistributionGroup -Identity "Marketing Reports" | Format-List -``` - -This example returns detailed information about the distribution group named Marketing Reports. - -### Example 3 -```powershell -Get-DistributionGroup -Anr marketing | Format-Table Name, ManagedBy -Auto -``` - -This example returns all distribution groups and mail-enabled security groups whose names contain the string "marketing" and shows the group owners. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedBy -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientTypeDetails -The RecipientTypeDetails parameter filters the results by the specified distribution group subtype. Valid values are: - -- MailNonUniversalGroup - -- MailUniversalDistributionGroup - -- MailUniversalSecurityGroup - -- RoomList - -You can specify multiple values separated by commas. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- Alias - -- City - -- FirstName - -- LastName - -- Office - -- ServerLegacyDN - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Get-DistributionGroupMember.md b/exchange/exchange-ps/exchange/users-and-groups/Get-DistributionGroupMember.md deleted file mode 100644 index 4e2067b70e..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-DistributionGroupMember.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Get-DistributionGroupMember - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-DistributionGroupMember cmdlet to view the members of distribution groups and mail-enabled security groups. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-DistributionGroupMember [-Identity] <DistributionGroupMemberIdParameter> [-Credential <PSCredential>] - [-DomainController <Fqdn>] [-IgnoreDefaultScope] [-ReadFromDomainController] [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -## DESCRIPTION -If your organization has multiple Active Directory domains, you may need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DistributionGroupMember -Identity "Marketing USA" -``` - -This example returns the existing distribution group members for the distribution group named Marketing USA. - -### Example 2 -```powershell -Set-ADServerSettings -ViewEntireForest $true; Get-DistributionGroupMember -Identity "Marketing Worldwide" -``` - -This example sets the scope of the search to the entire forest by running the Set-ADServerSettings cmdlet, then the Get-DistributionGroupMember cmdlet searches the entire forest for the distribution group members in the Marketing Worldwide distribution group. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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: (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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Get-DynamicDistributionGroup.md deleted file mode 100644 index b19c172f36..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-DynamicDistributionGroup.md +++ /dev/null @@ -1,392 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-dynamicdistributiongroup -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Get-DynamicDistributionGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps" ---- - -# Get-DynamicDistributionGroup - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-DynamicDistributionGroup cmdlet to view existing dynamic distribution groups. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnrSet -``` -Get-DynamicDistributionGroup [-Anr <String>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-IncludeSystemObjects] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -### Identity -``` -Get-DynamicDistributionGroup [[-Identity] <DynamicGroupIdParameter>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-IncludeSystemObjects] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -### ManagedBySet -``` -Get-DynamicDistributionGroup [-ManagedBy <GeneralRecipientIdParameter>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-IncludeSystemObjects] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] [-ResultSize <Unlimited>] - [-SortBy <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-DynamicDistributionGroup -``` - -This example returns a summary list of all dynamic distribution groups in your organization. - -### Example 2 -```powershell -Get-DynamicDistributionGroup -Identity "Marketing Department" | Format-List -``` - -This example returns detailed information about the dynamic distribution group named Marketing Department. - -### Example 3 -```powershell -Get-DynamicDistributionGroup -Anr *research* | Format-Table Name, ManagedBy -Auto -``` - -This example returns all dynamic distribution groups whose names contain the string "research" and shows the group owners. - -### Example 4 -```powershell -$FTE = Get-DynamicDistributionGroup "Full Time Employees"; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer -``` - -This example returns the members for the dynamic distribution group named Full Time Employees. The first command stores the dynamic distribution group object in the variable $FTE. The second command uses the Get-Recipient cmdlet to list the recipients that match the criteria defined for the dynamic distribution group. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: DynamicGroupIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeSystemObjects -This parameter is available only in on-premises Exchange. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedBy -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: GeneralRecipientIdParameter -Parameter Sets: ManagedBySet -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 -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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: (All) -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 -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- Alias - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Get-MailUser.md b/exchange/exchange-ps/exchange/users-and-groups/Get-MailUser.md deleted file mode 100644 index 2cb9c2915b..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-MailUser.md +++ /dev/null @@ -1,341 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Get-MailUser - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-MailUser cmdlet to view mail users and also guest users for Office 365 groups in cloud environments. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnrSet -``` -Get-MailUser [-Anr <String>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-SoftDeletedMailUser] - [-SortBy <String>] - [<CommonParameters>] -``` - -### Identity -``` -Get-MailUser [[-Identity] <MailUserIdParameter>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-ReadFromDomainController] - [-ResultSize <Unlimited>] - [-SoftDeletedMailUser] - [-SortBy <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-MailUser -``` - -This example returns a summary list of all mail users in the organization. - -### Example 2 -```powershell -Get-MailUser -Identity Ed | Format-List -``` - -This example returns detailed information for the mail user named Ed. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -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 -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -Credential -This parameter is available only in on-premises Exchange. - -The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. - -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```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 -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```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 -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -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: (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 -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- Alias - -```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 -Default value: None -Accept pipeline input: false -Accept wildcard characters: False -``` - -### -SoftDeletedMailUser -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. - -Soft-deleted mail users are deleted mail users that are still recoverable. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Get-Recipient.md b/exchange/exchange-ps/exchange/users-and-groups/Get-Recipient.md deleted file mode 100644 index b05858cc16..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-Recipient.md +++ /dev/null @@ -1,673 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-recipient -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Get-Recipient -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Get-Recipient - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-Recipient cmdlet to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). - -> [!NOTE] -> In Exchange Online PowerShell, we recommend that you use the Get-EXORecipient cmdlet instead of this cmdlet. For more information, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -In cloud environments, to return Office 365 groups, you need to use the RecipientTypeDetails parameter with the value GroupMailbox. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnrSet -``` -Get-Recipient [-Anr <String>] - [-AuthenticationType <AuthenticationType>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PropertySet <PropertySet>] - [-ReadFromDomainController] - [-RecipientType <RecipientType[]>] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SortBy <String>] - [-Capabilities <MultiValuedProperty>] - [-Database <DatabaseIdParameter>] - [-Properties <String[]>] - [-IncludeSoftDeletedRecipients] [<CommonParameters>] -``` - -### Identity -``` -Get-Recipient [[-Identity] <RecipientIdParameter>] - [-AuthenticationType <AuthenticationType>] - [-BookmarkDisplayName <String>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-IncludeBookmarkObject <Boolean>] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PropertySet <PropertySet>] - [-ReadFromDomainController] - [-RecipientType <RecipientType[]>] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SortBy <String>] - [-Capabilities <MultiValuedProperty>] - [-Properties <String[]>] - [-IncludeSoftDeletedRecipients] [<CommonParameters>] -``` - -### DatabaseSet -``` -Get-Recipient [-Database <DatabaseIdParameter>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-Properties <String[]>] - [-PropertySet <PropertySet>] - [-ReadFromDomainController] - [-RecipientType <RecipientType[]>] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-SortBy <String>] - [-IncludeSoftDeletedRecipients] [<CommonParameters>] - [<CommonParameters>] -``` - -### RecipientPreviewFilterSet -``` -Get-Recipient [-RecipientPreviewFilter <String>] - [-AuthenticationType <AuthenticationType>] - [-Capabilities <MultiValuedProperty>] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-IncludeSoftDeletedRecipients] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-Properties <String[]>] - [-PropertySet <PropertySet>] - [-ReadFromDomainController] - [-RecipientType <RecipientType[]>] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] [-SortBy <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-Recipient cmdlet may not return all object-specific properties for a recipient. To view the object-specific properties for a recipient, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox, Get-MailUser, or Get-DistributionGroup). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-Recipient -ResultSize unlimited -``` - -This example retrieves as summary list of all recipients in your organization. - -### Example 2 -```powershell -Get-Recipient -Identity "Marketing Department" | Format-List -``` - -This example returns detailed information for the recipient named Marketing Department. - -### Example 3 -```powershell -Get-Recipient -RecipientType MailContact -SortBy Office | Format-Table -Auto Office,Name -``` - -This example retrieves information about all the mail contacts in your organization and sorts them by office. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -Type: String -Parameter Sets: AnrSet -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuthenticationType -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: - -- Federated - -- Managed - -```yaml -Type: AuthenticationType -Parameter Sets: AnrSet, Identity, RecipientPreviewFilterSet -Aliases: -Applicable: Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BookmarkDisplayName -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Capabilities -This parameter is reserved for internal Microsoft use. - -```yaml -Type: MultiValuedProperty -Parameter Sets: AnrSet, Identity, RecipientPreviewFilterSet -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -This parameter is available only in on-premises Exchange. - -The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. - -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -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: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: DatabaseIdParameter -Parameter Sets: DatabaseSet -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeBookmarkObject -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeSoftDeletedRecipients -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: OrganizationalUnitIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Properties -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertySet -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, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientPreviewFilter -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 Opath filter syntax `"Property -ComparisonOperator 'Value'"` (the same syntax as the RecipientFilter parameter). - -- 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. - -- Property is a filterable property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipientfilter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: RecipientPreviewFilterSet -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientType -The RecipientType parameter filters the results by the specified recipient type. Valid values are: - -- DynamicDistributionGroup - -- MailContact - -- MailNonUniversalGroup - -- MailUniversalDistributionGroup - -- MailUniversalSecurityGroup - -- MailUser - -- PublicFolder - -- UserMailbox - -You can specify multiple values separated by commas. - -```yaml -Type: RecipientType[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientTypeDetails -The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are: - -- DiscoveryMailbox - -- DynamicDistributionGroup - -- EquipmentMailbox - -- GroupMailbox - -- GuestMailUser - -- LegacyMailbox - -- LinkedMailbox - -- LinkedRoomMailbox - -- MailContact - -- MailForestContact - -- MailNonUniversalGroup - -- MailUniversalDistributionGroup - -- MailUniversalSecurityGroup - -- MailUser - -- PublicFolder - -- PublicFolderMailbox - -- RemoteEquipmentMailbox - -- RemoteRoomMailbox - -- RemoteSharedMailbox - -- RemoteTeamMailbox - -- RemoteUserMailbox - -- RoomList - -- RoomMailbox - -- SchedulingMailbox - -- SharedMailbox - -- TeamMailbox - -- UserMailbox - -You can specify multiple values separated by commas. - -The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type. - -```yaml -Type: RecipientTypeDetails[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- Alias - -- City - -- FirstName - -- LastName - -- Office - -- ServerLegacyDN - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Get-UnifiedGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Get-UnifiedGroup.md deleted file mode 100644 index 01bd768f30..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-UnifiedGroup.md +++ /dev/null @@ -1,257 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-unifiedgroup -applicable: Exchange Online -title: Get-UnifiedGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-UnifiedGroup - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-UnifiedGroup cmdlet to view Office 365 Groups in your cloud-based organization. To view members, owners and subscribers for Office 365 Groups, use the Get-UnifiedGroupLinks cmdlet. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity (Default) -``` -Get-UnifiedGroup [[-Identity] <UnifiedGroupIdParameter>] - [-Filter <String>] - [-IncludeAllProperties] - [-IncludeSoftDeletedGroups] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -### AnrSet -``` -Get-UnifiedGroup [-Anr <String>] - [-Filter <String>] - [-IncludeAllProperties] - [-IncludeSoftDeletedGroups] - [-ResultSize <Unlimited>] - [-SortBy <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 Groups are group objects that are available across Office 365 services. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-UnifiedGroup -``` - -This example returns a summary list of all Office 365 Groups. - -### Example 2 -```powershell -Get-UnifiedGroup | Format-List DisplayName,EmailAddresses,Notes,ManagedBy,AccessType -``` - -This example returns the following information about all Office 365 Groups: - -- Display name - -- Email address - -- Description - -- Owners - -- Privacy - -### Example 3 -```powershell -Get-UnifiedGroup -Identity "Marketing Department" | Format-List -``` - -This example returns detailed information about the Office 365 Group named Marketing Department. - -### Example 4 -```powershell -Get-UnifiedGroup | Where-Object {-Not $_.ManagedBy} -``` - -This example returns Office 365 Groups that do not have an owner. - -## PARAMETERS - -### -Anr -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: AnrSet -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the Office 365 Group that you want to view. You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: UnifiedGroupIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IncludeAllProperties -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeSoftDeletedGroups -The IncludeSoftDeletedGroups switch specifies whether to include soft-deleted Office 365 groups in the results. You don't need to specify a value with this switch. - -Soft-deleted Office 365 groups are deleted groups that are still recoverable. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortBy -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- Alias - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/users-and-groups/Get-UnifiedGroupLinks.md deleted file mode 100644 index ee25736dbd..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-UnifiedGroupLinks.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-unifiedgrouplinks -applicable: Exchange Online -title: Get-UnifiedGroupLinks -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Get-UnifiedGroupLinks - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Get-UnifiedGroupLinks cmdlet to view membership and ownership information for Office 365 groups in your cloud-based organization. To view other properties for Office 365 groups, use the Get-UnifiedGroup cmdlet. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Get-UnifiedGroupLinks [-Identity] <UnifiedGroupIdParameter> -LinkType <LinkType> - [-ResultSize <Unlimited>] - [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 groups are group objects that are available across Office 365 services. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-UnifiedGroupLinks -Identity "Human Resources Department" -LinkType Members -``` - -This example show the members of the Office 365 Group named Human Resources Department - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Office 365 Group that you want to view. You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: UnifiedGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -LinkType -The LinkType parameter specifies the Office 365 Group property that you want to view. Valid values are: - -- Members - -- Owners - -- Subscribers - -- Aggregators - -- EventSubscribers - -```yaml -Type: LinkType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Get-User.md b/exchange/exchange-ps/exchange/users-and-groups/Get-User.md deleted file mode 100644 index e438a23928..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Get-User.md +++ /dev/null @@ -1,488 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/get-user -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection -title: Get-User -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || o365scc-ps || eop-ps" ---- - -# Get-User - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Get-User cmdlet to view existing user objects in your organization. This cmdlet returns all objects that have user accounts (for example, user mailboxes, mail users, and user accounts). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### AnrSet -``` -Get-User [-Anr <String>] - [-Arbitration] - [-AuditLog] - [-AuxAuditLog] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-Sortby <String>] - [<CommonParameters>] -``` - -### Identity -``` -Get-User [[-Identity] <UserIdParameter>] - [-Arbitration] - [-AuditLog] - [-AuxAuditLog] - [-Credential <PSCredential>] - [-DomainController <Fqdn>] - [-Filter <String>] - [-IgnoreDefaultScope] - [-OrganizationalUnit <OrganizationalUnitIdParameter>] - [-PublicFolder] - [-ReadFromDomainController] - [-RecipientTypeDetails <RecipientTypeDetails[]>] - [-ResultSize <Unlimited>] - [-Sortby <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-User cmdlet returns no mail-related properties for mailboxes or mail users. To view the mail-related properties for a user, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox or Get-MailUser). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-User -ResultSize unlimited -``` - -This example returns a summary list of all users in your organization. - -### Example 2 -```powershell -Get-User -Identity "Coy Damon" | Format-List -``` - -This example returns detailed information for the user named Coy Damon. - -### Example 3 -```powershell -Get-User -OrganizationalUnit "Marketing" -``` - -This example retrieves information about users in the Marketing OU. - -### Example 4 -```powershell -Get-User -Filter "Title -like '*Manager'" -``` - -This example uses the Filter parameter to retrieve information about all users that have the word Manager at the end of their title. - -## PARAMETERS - -### -Anr -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) - -- DisplayName - -- FirstName - -- LastName - -- Alias - -```yaml -Type: String -Parameter Sets: AnrSet -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Arbitration -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. - -Arbitration mailboxes are system mailboxes that are used for storing different types of system data and for managing messaging approval workflow. - -To return arbitration mailboxes that are used to store audit log settings or data, don't use this switch. Instead, use the AuditLog or AuxAuditLog switches. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuditLog -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. - -Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. - -To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuxAuditLog -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. - -Audit log mailboxes are arbitration mailboxes that are used to store audit log settings. - -To return other types of arbitration mailboxes, don't use this switch. Instead, use the Arbitration switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -This parameter is available only in on-premises Exchange. - -The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. - -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://go.microsoft.com/fwlink/p/?linkId=142122). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -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. - -- Property is a filterable property. For more information about the filterable properties, see [Filterable properties for the Filter parameter](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/filter-properties). - -- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://go.microsoft.com/fwlink/p/?LinkId=620712). - -- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`). - -You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`. - -For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/exchange-server/recipient-filters/recipient-filters#additional-opath-syntax-information). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter the user that you want to view. You can use any value that uniquely identifies the user. For example: - -- Name - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrganizationalUnit -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 - -- Canonical name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: OrganizationalUnitIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicFolder -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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadFromDomainController -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. If you run the command Set-AdServerSettings -ViewEntireForest $true to include all objects in the forest and you don't use the ReadFromDomainController switch, it's possible that information will be read from a global catalog that has outdated information. When you use the ReadFromDomainController switch, multiple reads might be necessary to get the information. You don't have to specify a value with this switch. - -By default, the recipient scope is set to the domain that hosts your Exchange servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientTypeDetails -The RecipientTypeDetails parameter filters the results by the specified user subtype. Valid values are: - -- DisabledUser - -- DiscoveryMailbox - -- EquipmentMailbox - -- GuestMailUser - -- LegacyMailbox - -- LinkedMailbox - -- LinkedUser - -- MailUser - -- PublicFolderMailbox - -- RemoteEquipmentMailbox - -- RemoteRoomMailbox - -- RemoteSharedMailbox - -- RemoteTeamMailbox - -- RemoteUserMailbox - -- RoomMailbox - -- SchedulingMailbox - -- SharedMailbox - -- TeamMailbox - -- User - -- UserMailbox - -You can specify multiple values separated by commas. - -```yaml -Type: RecipientTypeDetails[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Sortby -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\>... to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported. - -You can sort by the following properties: - -- Name - -- DisplayName - -- City - -- FirstName - -- LastName - -- Office - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Office 365 Security & Compliance Center, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/New-EOPDistributionGroup.md b/exchange/exchange-ps/exchange/users-and-groups/New-EOPDistributionGroup.md deleted file mode 100644 index 95372726be..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/New-EOPDistributionGroup.md +++ /dev/null @@ -1,246 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/new-eopdistributiongroup -applicable: Exchange Online Protection -title: New-EOPDistributionGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# New-EOPDistributionGroup - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the New-EOPDistributionGroup cmdlet to create distribution groups or mail-enabled security groups in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the New-DistributionGroup cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-EOPDistributionGroup -Name <String> [-Alias <String>] [-DisplayName <String>] [-ManagedBy <String[]>] - [-Members <String[]>] [-Notes <String>] [-PrimarySmtpAddress <SmtpAddress>] [-Type <GroupType>] - [<CommonParameters>] -``` - -## DESCRIPTION -You can use the New-EOPDistributionGroup cmdlet to create the following types of groups: - -- Mail-enabled universal security group (USG) - -- Universal distribution group - -Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Security groups are used to grant permissions to multiple users. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-EOPDistributionGroup -Name Managers -Type Security -ManagedBy "Kitty Petersen" -``` - -This example creates a mail-enabled universal security group named Managers that's managed by Kitty Petersen. - -### Example 2 -```powershell -New-EOPDistributionGroup -Name "Security Team" -ManagedBy "Tyson Fawcett" -Alias SecurityTeamThree -DisplayName "Security Team" -Notes "Security leads from each division" -PrimarySmtpAddress SecTeamThree@contoso.com -Type Distribution -Members @("Tyson Fawcett","Kitty Petersen") -``` - -This example creates a distribution group named "Security Team" and adds two users to the group. - -## PARAMETERS - -### -Name -The Name parameter specifies the name of the distribution group object. The value specified in the Name parameter is also used for the DisplayName parameter if the DisplayName parameter isn't specified. - -The Name parameter value can't exceed 64 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Alias -The Alias parameter specifies the email alias of the distribution group. The Alias parameter value is used to generate the primary SMTP email address if you don't use the PrimarySmtpAddress parameter. - -The value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the name of the distribution group in the Exchange admin center (EAC). If the DisplayName parameter isn't specified, the value of the Name parameter is used for the DisplayName parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedBy -The ManagedBy parameter specifies a user who owns the group. In Exchange Online Protection, you need to use this parameter to specify at least one group owner. You can use any value that uniquely identifies the user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can specify multiple owners by using the following syntax: @("\<user1\>","\<user2\>"...). - -The users you specify with this parameter aren't automatically added to the group. To add members to the group, use the Update-EOPDistributionGroupMember cmdlet. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Members -The Members parameter specifies the initial list of recipients (mail-enabled objects) in the distribution group. In Exchange Online Protection, the valid recipient types are: - -- Mail users - -- Distribution groups - -- Mail-enabled security groups - -You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can specify multiple recipients by using the following syntax: @("\<recipient1\>","\<recipient2\>"...). - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -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 Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimarySmtpAddress -The PrimarySmtpAddress parameter specifies the primary return SMTP email address for the distribution group. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -The Type parameter specifies the group type. Valid values are Distribution or Security. - -```yaml -Type: GroupType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/New-EOPMailUser.md b/exchange/exchange-ps/exchange/users-and-groups/New-EOPMailUser.md deleted file mode 100644 index f81e1d4ed0..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/New-EOPMailUser.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/new-eopmailuser -applicable: Exchange Online Protection -title: New-EOPMailUser -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# New-EOPMailUser - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the New-EOPMailUser cmdlet to create mail users, also known as mail-enabled users, in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the New-MailUser cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -New-EOPMailUser -MicrosoftOnlineServicesID <WindowsLiveId> -Name <String> -Password <String> [-Alias <String>] - [-DisplayName <String>] [-ExternalEmailAddress <ProxyAddress>] [-FirstName <String>] [-Initials <String>] - [-LastName <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-EOPMailUser -Name EdMeadows -MicrosoftOnlineServicesID EdMeadows@Contoso.onmicrosoft.com -ExternalEmailAddress EdMeadows@tailspintoys.com -Password (ConvertTo-SecureString -String 'Pa$$w0rd' -AsPlainText -Force) -FirstName Ed -LastName Meadows -DisplayName "Ed Meadows" -Alias edm -``` - -This example creates a mail user object for Ed Meadows while specifying several additional optional parameters and using an in-line method of password encryption. - -## PARAMETERS - -### -MicrosoftOnlineServicesID -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: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies the name of the mail user object. The value specified in the Name parameter is also used for the DisplayName parameter if the DisplayName parameter isn't specified. - -The Name parameter value can't exceed 64 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -The Password parameter the password for the mail user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Alias -The Alias parameter specifies the alias of the mail user. - -The value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the name of the mail user in the Exchange admin center (EAC). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalEmailAddress -The ExternalEmailAddress parameter specifies the user's email address that's outside of the Exchange Online Protection organization. Email messages sent to the mail user are relayed to this external address. - -```yaml -Type: ProxyAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FirstName -The FirstName parameter specifies the user's first name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Initials -The Initials parameter specifies the user's middle initials. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LastName -The LastName parameter specifies the user's last name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/New-UnifiedGroup.md b/exchange/exchange-ps/exchange/users-and-groups/New-UnifiedGroup.md deleted file mode 100644 index 42b7fb54f7..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/New-UnifiedGroup.md +++ /dev/null @@ -1,705 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/new-unifiedgroup -applicable: Exchange Online -title: New-UnifiedGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# New-UnifiedGroup - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the New-UnifiedGroup cmdlet to create Office 365 Groups in your cloud-based organization. To add members, owners, and subscribers to Office 365 Groups, use the Add-UnifiedGroupLinks cmdlet. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -### Identity (Default) -``` -New-UnifiedGroup [-AccessType <ModernGroupTypeInfo>] [-MailboxRegion <String>] - [-Alias <String>] - [-AlwaysSubscribeMembersToCalendarEvents] - [-AutoSubscribeNewMembers] - [-Classification <String>] - [-Confirm] - [-DataEncryptionPolicy <DataEncryptionPolicyIdParameter>] - [-DisplayName <String>] - [-EmailAddresses <ProxyAddressCollection>] - [-ExecutingUser <RecipientIdParameter>] - [-ExoErrorAsWarning] - [-HiddenGroupMembershipEnabled] - [-Language <CultureInfo>] - [-ManagedBy <RecipientIdParameter[]>] - [-Members <RecipientIdParameter[]>] - [-Name <String>] - [-Notes <String>] - [-Owner <RecipientIdParameter>] - [-PrimarySmtpAddress <SmtpAddress>] - [-RequireSenderAuthenticationEnabled <Boolean>] - [-SuppressWarmupMessage] - [-WhatIf] [<CommonParameters>] -``` - -### ProvisioningOptions -``` -New-UnifiedGroup [-AccessType <ModernGroupTypeInfo>] - [-Alias <String>] - [-AlwaysSubscribeMembersToCalendarEvents] - [-AutoSubscribeNewMembers] - [-Classification <String>] - [-Confirm] - [-DataEncryptionPolicy <DataEncryptionPolicyIdParameter>] - [-DisplayName <String>] - [-EmailAddresses <ProxyAddressCollection>] - [-ExecutingUser <RecipientIdParameter>] - [-ExoErrorAsWarning] - [-HiddenGroupMembershipEnabled] - [-Language <CultureInfo>] - [-ManagedBy <RecipientIdParameter[]>] - [-Members <RecipientIdParameter[]>] - [-Name <String>] - [-Notes <String>] - [-Owner <RecipientIdParameter>] - [-PrimarySmtpAddress <SmtpAddress>] - [-RequireSenderAuthenticationEnabled <Boolean>] - [-SuppressWarmupMessage] - [-WhatIf] [<CommonParameters>] -``` - -### SegmentationOption -``` -New-UnifiedGroup [-AccessType <ModernGroupTypeInfo>] [-SubscriptionEnabled] - [-Alias <String>] - [-AlwaysSubscribeMembersToCalendarEvents] - [-AutoSubscribeNewMembers] - [-Classification <String>] - [-Confirm] - [-DataEncryptionPolicy <DataEncryptionPolicyIdParameter>] - [-DisplayName <String>] - [-EmailAddresses <ProxyAddressCollection>] - [-ExecutingUser <RecipientIdParameter>] - [-ExoErrorAsWarning] - [-HiddenGroupMembershipEnabled] - [-Language <CultureInfo>] - [-ManagedBy <RecipientIdParameter[]>] - [-Members <RecipientIdParameter[]>] - [-Name <String>] - [-Notes <String>] - [-Owner <RecipientIdParameter>] - [-PrimarySmtpAddress <SmtpAddress>] - [-RequireSenderAuthenticationEnabled <Boolean>] - [-SuppressWarmupMessage] - [-WhatIf] [<CommonParameters>] -``` - -### DlMigration -``` -New-UnifiedGroup -DlIdentity <DistributionGroupIdParameter> [-ConvertClosedDlToPrivateGroup] [-DeleteDlAfterMigration] - [-Confirm] - [-ExecutingUser <RecipientIdParameter>] - [-ManagedBy <RecipientIdParameter[]>] - [-Members <RecipientIdParameter[]>] - [-Owner <RecipientIdParameter>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 Groups are group objects that are available across Office 365 services. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -New-UnifiedGroup -DisplayName "Engineering Department" -Alias engineering -``` - -This example creates a new Office 365 Group named Engineering Department. - -## PARAMETERS - -### -DlIdentity -The DlIdentity parameter specifies the distribution group (also known as a distribution list or DL) that you want to migrate to an Office 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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -All the properties and membership of the distribution group are copied to the Office 365 Group. - -The alias and proxy addresses of the distribution group are moved to the Office 365 Group, and are replaced on the distribution group by the values DLMigrated\_\<GUID\>. The original proxy addresses are copied to the ExtensionCustomAttribute5 property of the distribution group. - -Office 365 Groups don't have ReportToManager and ReportToOriginator parameters, so the values of these parameters aren't migrated from the distribution group to the Office 365 Group. The Office 365 Group behaves as if the default values of these parameters were set (ReportToManager is $false and ReportToOriginator is $true). In other words, delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the message sender and not to the owner of the Office 365 Group. - -```yaml -Type: DistributionGroupIdParameter -Parameter Sets: DlMigration -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AccessType -The AccessType parameter specifies the privacy type for the Office 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. - -- Private: The group content and conversations are only available to members of the group, and joining the group requires approval from a group owner. - -You can change the privacy type at any point in the lifecycle of the group. - -Note: Although a user needs to be a member to participate in a private group, anyone can send email to a private group, and receive replies from the private group. - -```yaml -Type: ModernGroupTypeInfo -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the Office 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -When you create an Office 365 Group without using the EmailAddresses parameter, the Alias value you specify is used to generate the primary email address (\<alias\>@\<domain\>). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. - -If you don't use the Alias parameter when you create an Office 365 Group, the value of the DisplayName parameter is used. Spaces are removed, unsupported characters are converted to question marks (?), and numbers may be added to maintain the uniqueness of the Alias value. - -The Alias value is appended with the ExternalDirectoryObjectId property value and used as the Name property value for the Office 365 Group ("Alias\_\<ExternalDirectoryObjectId\>"\). - -```yaml -Type: String -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlwaysSubscribeMembersToCalendarEvents -The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Office 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. - -- If you use this exact syntax: -AlwaysSubscribeMembersToCalendarEvents:$false, all future members that are added to the group will have their subscriptions set to ReplyOnly. - -Group members can change their own subscription settings, which can override your intended use of this switch. - -The AutoSubscribeNewMembers switch overrides this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoSubscribeNewMembers -The AutoSubscribeNewMembers switch specifies whether to automatically subscribe new members that are added to the Office 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. - -```yaml -Type: SwitchParameter -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Classification -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConvertClosedDlToPrivateGroup -The ConvertClosedDlToPrivateGroup switch specifies whether to migrate the closed distribution group to a private Office 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. - -If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group will always be migrated to a private Office 365 Group. For open distribution groups, the migrated Office 365 Group is always public, not private. - -You can only use this switch with the DlIdentity parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: DlMigration -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataEncryptionPolicy -The DataEncryptionPolicy parameter specifies the data encryption policy that's applied to the Office 365 Group. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -```yaml -Type: DataEncryptionPolicyIdParameter -Parameter Sets: Identity, SegmentationOption, ProvisioningOptions -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeleteDlAfterMigration -The DeleteDlAfterMigration switch specifies whether to delete the distribution group after it's migrated to an Office 365 Group. You don't need to specify a value with this switch. - -You can only use this switch with the DlIdentity parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: DlMigration -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the name of the Office 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 Office 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. - -```yaml -Type: String -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.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. Some examples of valid values include: - -- SMTP: The primary SMTP address. You can use this value only once in a command. - -- smtp: Other SMTP email addresses. - -- X400: X.400 addresses in on-premises Exchange. - -- X500: X.500 addresses in on-premises Exchange. - -If you don't include a \<Type\> value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. - -To specify the primary SMTP email address, you can use any of the following methods: - -- Use the \<Type\> value SMTP on the address. - -- The first email address when you don't use any \<Type\> values, or when you use multiple \<Type\> values of smtp. - -- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. - -To enter multiple proxy email addresses, use the following syntax: "\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",..."\<Type\>:\<emailaddressN\>". - -```yaml -Type: ProxyAddressCollection -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExecutingUser -This parameter is reserved for internal Microsoft use. - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExoErrorAsWarning -The ExoErrorAsWarning switch specifies that Exchange Online errors that you encounter while creating the Office 365 Group are treated as warnings, not errors. You don't need to specify a value with this switch. - -Creating Office 365 Groups involves background operations in Azure Active Directory 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 Azure Active Directory is synchronized back to Exchange Online. - -```yaml -Type: SwitchParameter -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HiddenGroupMembershipEnabled -The HiddenGroupMembershipEnabled switch specifies whether to hide the members of the Office 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, an Office 365 Group group that represents students enrolled in a class). - -Note: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group. - -```yaml -Type: SwitchParameter -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -The Language parameter specifies the language preference for the Office 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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxRegion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedBy -This parameter is reserved for internal Microsoft use. - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Members -The Members parameter specifies the recipients (mail-enabled objects) that are members of the Office 365 Group. You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 Office 365 Group \("Name\_\<RandomGUID\>"\). Now, the value of the Name property is populated by the Alias parameter value and the ExternalDirectoryObjectId property value ("Alias\_\<ExternalDirectoryObjectId\>"\). - -```yaml -Type: String -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -The Notes parameter specifies the description of the Office 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -The Owner parameter specifies the for the Office 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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimarySmtpAddress -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireSenderAuthenticationEnabled -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. - -- $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. - -```yaml -Type: Boolean -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriptionEnabled -The SubscriptionEnabled switch specifies whether subscriptions to conversations and calendar events are enabled for the Office 365 Group. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressWarmupMessage -This parameter has been deprecated and is no longer used. - -```yaml -Type: SwitchParameter -Parameter Sets: Identity, ProvisioningOptions, SegmentationOption -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-EOPDistributionGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Remove-EOPDistributionGroup.md deleted file mode 100644 index 387ae60f49..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-EOPDistributionGroup.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-eopdistributiongroup -applicable: Exchange Online Protection -title: Remove-EOPDistributionGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# Remove-EOPDistributionGroup - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the Remove-EOPDistributionGroup cmdlet to delete distribution groups or mail-enabled security groups in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Remove-DistributionGroup cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-EOPDistributionGroup [-ExternalDirectoryObjectId <String>] [-Identity <DistributionGroupIdParameter>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-EOPDistributionGroup -Identity "Security Team" -``` - -This example removes the existing Exchange Online Protection distribution group named Security Team. - -## PARAMETERS - -### -ExternalDirectoryObjectId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the distribution group or mail-enabled security group that you want to remove. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: DistributionGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-EOPMailUser.md b/exchange/exchange-ps/exchange/users-and-groups/Remove-EOPMailUser.md deleted file mode 100644 index df8532291f..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-EOPMailUser.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-eopmailuser -applicable: Exchange Online Protection -title: Remove-EOPMailUser -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# Remove-EOPMailUser - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the Remove-EOPMailUser cmdlet to remove Exchange Online Protection mail users, also known as mail-enabled users, from Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Remove-MailUser cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-EOPMailUser [-ExternalDirectoryObjectId <String>] [-Identity <MailUserIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-EOPMailUser -Identity "Ed Meadows" -``` - -This example removes the mail-enabled user named Ed Meadows. - -## PARAMETERS - -### -ExternalDirectoryObjectId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the mail user that you want to delete. You can use any value that uniquely identifies the mail user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailUserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-MailUser.md b/exchange/exchange-ps/exchange/users-and-groups/Remove-MailUser.md deleted file mode 100644 index 53e1103c31..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-MailUser.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Remove-MailUser - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Remove-MailUser cmdlet to remove existing mail users. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-MailUser [-Identity] <MailUserIdParameter> - [-Confirm] - [-DomainController <Fqdn>] - [-IgnoreDefaultScope] - [-IgnoreLegalHold] - [-KeepWindowsLiveID] - [-PermanentlyDelete] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-MailUser -Identity "Ed Meadows" -``` - -This example removes the mail user named Ed Meadows. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreLegalHold -The IgnoreLegalHold switch specifies whether to ignore the legal hold status of the user. When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed. You don't need to specify a value with this switch. - -After you disable or remove a mailbox, you can't include it in a discovery search. When you disable a mailbox, the mailbox is disconnected from the user account. Disconnected mailboxes and removed mailboxes are permanently deleted from the mailbox database after the deleted mailbox retention period expires. However, you can also remove a mailbox and purge it immediately from the mailbox database. Check with your organization's legal or Human Resources department before you disable or remove a mailbox that's on legal hold. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepWindowsLiveID -This parameter is available only in the cloud-based service. - -The KeepWindowsLiveID switch specifies whether to preserve the Microsoft account (formerly known as a Windows Live ID) that's associated with the deleted mail user. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermanentlyDelete -This parameter is available only in the cloud-based service. - -The PermanentlyDelete switch specifies whether to immediately and permanently delete (purge) the mail user, which prevents you from recovering or restoring the mail user. You don't need to specify a value with this switch. - -This switch works only on mail users that have already been deleted, but are still recoverable (known as soft-deleted mail-users), that also have a blank value for the ExternalObjectId property. - -Use the Get-MailUser cmdlet to identify the soft-deleted mail user, and then pipe the results to the Remove-MailUser cmdlet with this switch. For example, Get-MailUser -Identity Laura -SoftDeleted | Remove-MailUser -PermanentlyDelete. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Remove-UnifiedGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Remove-UnifiedGroup.md deleted file mode 100644 index 587a4a0014..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-UnifiedGroup.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-unifiedgroup -applicable: Exchange Online -title: Remove-UnifiedGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Remove-UnifiedGroup - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-UnifiedGroup cmdlet to remove Office 365 groups from your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-UnifiedGroup [-Identity] <UnifiedGroupIdParameter> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 groups are group objects that are available across Office 365 services. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-UnifiedGroup -Identity "Research Department" -``` - -This example removes the Office 365 Group named Research Department. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Office 365 Group that you want to remove. You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: UnifiedGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Remove-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/users-and-groups/Remove-UnifiedGroupLinks.md deleted file mode 100644 index 45bf2ac145..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Remove-UnifiedGroupLinks.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/remove-unifiedgrouplinks -applicable: Exchange Online -title: Remove-UnifiedGroupLinks -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Remove-UnifiedGroupLinks - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Remove-UnifiedGroupLinks cmdlet to remove members, owners and subscribers from Office 365 groups in your cloud-based organization. To add members, owners and subscribers, use the Add-UnifiedGroupLinks cmdlet. To modify other properties of Office 365 groups, use the Set-UnifiedGroup cmdlet. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Remove-UnifiedGroupLinks [-Identity] <UnifiedGroupIdParameter> -Links <RecipientIdParameter[]> - -LinkType <LinkType> - [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 groups are group objects that are available across Office 365 services. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Remove-UnifiedGroupLinks -Identity "Legal Department" -LinkType Members -Links laura@contoso.com,julia@contoso.com -``` - -This example removes members laura@contoso.com and julia@contoso.com from the Office 365 Group named Legal Department. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Office 365 Group that you want to modify. You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: UnifiedGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Links -The Links parameter specifies the recipients to remove from the Office 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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -```yaml -Type: RecipientIdParameter[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LinkType -The LinkType parameter specifies the Office 365 Group property that you want to modify. Valid values are: - -- Members - -- Owners - -- Subscribers - -- Aggregators - -- EventSubscribers - -```yaml -Type: LinkType -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPDistributionGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Set-EOPDistributionGroup.md deleted file mode 100644 index 93283abd01..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPDistributionGroup.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-eopdistributiongroup -applicable: Exchange Online Protection -title: Set-EOPDistributionGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# Set-EOPDistributionGroup - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the Set-EOPDistributionGroup cmdlet to modify the settings of distribution groups or mail-enabled security groups in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Set-DistributionGroup cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-EOPDistributionGroup [-Alias <String>] [-DisplayName <String>] [-ExternalDirectoryObjectId <String>] - [-Identity <DistributionGroupIdParameter>] [-ManagedBy <String[]>] [-PrimarySmtpAddress <SmtpAddress>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-EOPDistributionGroup -Identity "Security Team" -PrimarySmtpAddress NewSecTeamId@Contoso.com -``` - -This example changes the current SMTP address of the Security Team EOP distribution group to "NewSecTeamId@Contoso.com". - -## PARAMETERS - -### -Alias -The Alias parameter specifies the alias of the distribution group. - -The value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the name of the distribution group in the Exchange admin center (EAC). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: DistributionGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedBy -The ManagedBy parameter specifies one or more group owners. A group must have at least one owner. You can use any value that uniquely identifies the owner. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -You can specify multiple owners by using the following syntax: @("\<user1\>","\<user2\>"...). The values that you specify will overwrite the current list of owners. - -The users specified with the ManagedBy parameter aren't automatically members of the distribution group. If you want any of the owners to be added as members of the distribution group, you need to add them by using the Update-EOPDistributionGroupMember cmdlet. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimarySmtpAddress -The PrimarySmtpAddress parameter specifies the primary return SMTP email address for the distribution group. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Set-EOPGroup.md deleted file mode 100644 index 021982a44a..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPGroup.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-eopgroup -applicable: Exchange Online Protection -title: Set-EOPGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# Set-EOPGroup - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the Set-EOPGroup cmdlet to modify general group object attributes in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Set-Group cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-EOPGroup [-ExternalDirectoryObjectId <String>] [-Identity <GroupIdParameter>] [-ManagedBy <String[]>] - [-Notes <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-Group -Identity "Legal Department" -Notes "Group members updated June 1, 2018" -``` - -This example sets the Notes property to indicate the last time that the group was updated. - -## PARAMETERS - -### -ExternalDirectoryObjectId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: GroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedBy -The ManagedBy parameter specifies a user who owns the group. You can use any value that uniquely identifies the user. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can specify multiple owners by using the following syntax: @("\<user1\>","\<user2\>"...). The values that you specify will overwrite the current list of owners. - -The users you specify with this parameter aren't automatically added to the group. To add members to the group, use the Update-EOPDistributionGroupMember cmdlet. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -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 Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPMailUser.md b/exchange/exchange-ps/exchange/users-and-groups/Set-EOPMailUser.md deleted file mode 100644 index 370e334451..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPMailUser.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-eopmailuser -applicable: Exchange Online Protection -title: Set-EOPMailUser -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# Set-EOPMailUser - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the Set-EOPMailUser cmdlet to modify mail users, also known as mail-enabled users, in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Set-MailUser cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-EOPMailUser [-Alias <String>] [-DisplayName <String>] [-EmailAddresses <ProxyAddressCollection>] - [-ExternalDirectoryObjectId <String>] [-Identity <MailUserIdParameter>] - [-MicrosoftOnlineServicesID <SmtpAddress>] [-Password <String>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-EOPMailUser -Identity "Edward Meadows" -DisplayName "Ed Meadows" -``` - -This example changes the display name for the mail user Edward Meadows to "Ed Meadows." - -## PARAMETERS - -### -Alias -The Alias parameter specifies the alias of the mail user. - -The value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the display name of the mail user in the Exchange admin center (EAC). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -The EmailAddresses parameter specifies the primary email address and other proxy addresses for the mail user. This parameter uses the syntax SMTP:\<PrimaryEmailAddress\>,\<ProxyAddress\>. - -The values that you specify for this parameter overwrite any existing values. - -```yaml -Type: ProxyAddressCollection -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailUserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MicrosoftOnlineServicesID -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: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPUser.md b/exchange/exchange-ps/exchange/users-and-groups/Set-EOPUser.md deleted file mode 100644 index 7db723efd8..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-EOPUser.md +++ /dev/null @@ -1,408 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-eopuser -applicable: Exchange Online Protection -title: Set-EOPUser -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# Set-EOPUser - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the Set-EOPUser cmdlet to modify general user object attributes in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Set-User cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-EOPUser [-City <String>] [-Company <String>] [-CountryOrRegion <CountryInfo>] [-Department <String>] - [-DisplayName <String>] [-ExternalDirectoryObjectId <String>] [-Fax <String>] [-FirstName <String>] - [-HomePhone <String>] [-Identity <UserIdParameter>] [-Initials <String>] [-LastName <String>] - [-MobilePhone <String>] [-Notes <String>] [-Office <String>] [-Phone <String>] [-PostalCode <String>] - [-StateOrProvince <String>] [-StreetAddress <String>] [-Title <String>] [-WebPage <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-EOPUser -Identity "Kitty Petersen" -Company Contoso -DisplayName "Kitty Petersen" -Title "Vice President" -``` - -This example sets the company, display name, and title properties for the user Kitty Petersen. - -## PARAMETERS - -### -City -The City parameter specifies the user's city. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Company -The Company parameter specifies the user's company. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -The CountryOrRegion parameter specifies the user's country or region. - -```yaml -Type: CountryInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Department -The Department parameter specifies the user's department. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the user's display name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDirectoryObjectId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Fax -The Fax parameter specifies the user's fax number. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FirstName -The FirstName parameter specifies the user's first name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HomePhone -The HomePhone parameter specifies the user's home telephone number. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the user object that you want to modify. You can use any value that uniquely identifies the user. For example: - -- Name - -- Distinguished name (DN) - -- Canonical DN - -- GUID - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Initials -The Initials parameter specifies the user's middle initials. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LastName -The FirstName parameter specifies the user's first name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MobilePhone -The MobilePhone parameter specifies the user's primary mobile phone number. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -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 Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Office -The Office parameter specifies the user's physical office name or number. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Phone -The Phone parameter specifies the user's telephone number. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostalCode -The PostalCode parameter specifies the user's zip code or postal code. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOrProvince -The StateOrProvince parameter specifies the user's state or province. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetAddress -The StreetAddress parameter specifies the user's physical address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title -The Title parameter specifies the user's title. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebPage -The WebPage parameter specifies the user's Web page. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Set-MailUser.md b/exchange/exchange-ps/exchange/users-and-groups/Set-MailUser.md deleted file mode 100644 index 88d9030536..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-MailUser.md +++ /dev/null @@ -1,2075 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/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 -ms.author: chrisda -ms.reviewer: -monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 || exchserver-ps-2019 || exchonline-ps || eop-ps" ---- - -# Set-MailUser - -## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. - -Use the Set-MailUser cmdlet to modify mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-MailUser [-Identity] <MailUserIdParameter> - [-AcceptMessagesOnlyFrom <MultiValuedProperty>] - [-AcceptMessagesOnlyFromDLMembers <MultiValuedProperty>] - [-AcceptMessagesOnlyFromSendersOrMembers <MultiValuedProperty>] - [-Alias <String>] - [-ArbitrationMailbox <MailboxIdParameter>] - [-ArchiveGuid <Guid>] - [-ArchiveName <MultiValuedProperty>] - [-BypassModerationFromSendersOrMembers <MultiValuedProperty>] - [-Confirm] - [-CreateDTMFMap <Boolean>] - [-CustomAttribute1 <String>] - [-CustomAttribute10 <String>] - [-CustomAttribute11 <String>] - [-CustomAttribute12 <String>] - [-CustomAttribute13 <String>] - [-CustomAttribute14 <String>] - [-CustomAttribute15 <String>] - [-CustomAttribute2 <String>] - [-CustomAttribute3 <String>] - [-CustomAttribute4 <String>] - [-CustomAttribute5 <String>] - [-CustomAttribute6 <String>] - [-CustomAttribute7 <String>] - [-CustomAttribute8 <String>] - [-CustomAttribute9 <String>] - [-DataEncryptionPolicy <DataEncryptionPolicyIdParameter>] - [-DisplayName <String>] - [-DomainController <Fqdn>] - [-EmailAddressPolicyEnabled <Boolean>] - [-EmailAddresses <ProxyAddressCollection>] - [-ExchangeGuid <Guid>] - [-ExtensionCustomAttribute1 <MultiValuedProperty>] - [-ExtensionCustomAttribute2 <MultiValuedProperty>] - [-ExtensionCustomAttribute3 <MultiValuedProperty>] - [-ExtensionCustomAttribute4 <MultiValuedProperty>] - [-ExtensionCustomAttribute5 <MultiValuedProperty>] - [-ExternalEmailAddress <ProxyAddress>] - [-FederatedIdentity <String>] - [-ForceUpgrade] - [-GrantSendOnBehalfTo <MultiValuedProperty>] - [-HiddenFromAddressListsEnabled <Boolean>] - [-IgnoreDefaultScope] - [-ImmutableId <String>] - [-JournalArchiveAddress <SmtpAddress>] - [-MacAttachmentFormat <MacAttachmentFormat>] - [-MailTip <String>] - [-MailTipTranslations <MultiValuedProperty>] - [-MailboxRegion <String>] - [-MaxReceiveSize <Unlimited>] - [-MaxSendSize <Unlimited>] - [-MessageBodyFormat <MessageBodyFormat>] - [-MessageFormat <MessageFormat>] - [-MicrosoftOnlineServicesID <SmtpAddress>] - [-ModeratedBy <MultiValuedProperty>] - [-ModerationEnabled <Boolean>] - [-Name <String>] - [-Password <SecureString>] - [-PrimarySmtpAddress <SmtpAddress>] - [-RecipientLimits <Unlimited>] - [-RecoverableItemsQuota <Unlimited>] - [-RecoverableItemsWarningQuota <Unlimited>] - [-RejectMessagesFrom <MultiValuedProperty>] - [-RejectMessagesFromDLMembers <MultiValuedProperty>] - [-RejectMessagesFromSendersOrMembers <MultiValuedProperty>] - [-RemoveMailboxProvisioningConstraint] - [-RemovePicture] - [-RemoveSpokenName] - [-RequireSenderAuthenticationEnabled <Boolean>] - [-ResetPasswordOnNextLogon <Boolean>] - [-SamAccountName <String>] - [-SecondaryAddress <String>] - [-SecondaryDialPlan <UMDialPlanIdParameter>] - [-SendModerationNotifications <TransportModerationNotificationFlags>] - [-SimpleDisplayName <String>] - [-SkipDualWrite] - [-UMDtmfMap <MultiValuedProperty>] - [-UseMapiRichTextFormat <UseMapiRichTextFormat>] - [-UsePreferMessageFormat <Boolean>] - [-UserCertificate <MultiValuedProperty>] - [-UserPrincipalName <String>] - [-UserSMimeCertificate <MultiValuedProperty>] - [-WhatIf] - [-WindowsEmailAddress <SmtpAddress>] - [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-MailUser -Identity "John Woods" -ExternalEmailAddress john@tailspintoys.com -``` - -This example modifies the external email address for the mail user named John Woods. Note that the original external email address isn't kept as a proxy address. - -## PARAMETERS - -### -Identity -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -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 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AcceptMessagesOnlyFrom -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". - -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\<sender1\>","\<sender2\>"...; Remove="\<sender1\>","\<sender2\>"...}. - -The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AcceptMessagesOnlyFromDLMembers -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \<group1\>,\<group2\>,...\<groupN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<group1\>","\<group2\>",..."\<groupN\>". - -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\<group1\>","\<group2\>"...; Remove="\<group1\>","\<group2\>"...}. - -The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all groups. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AcceptMessagesOnlyFromSendersOrMembers -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. - -To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". - -To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. - -The individual senders and groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromDLMembers properties, respectively. Therefore, you can't use the AcceptMessagesOnlyFromSendersOrMembers parameter and the AcceptMessagesOnlyFrom or AcceptMessagesOnlyFromDLMembers parameters in the same command. - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. - -The value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (\<alias\>@\<domain\>). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to oe in the primary email address. - -If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: - -- Recipients with user accounts (for example, user mailboxes, and mail users): The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, helpdesk@contoso.com results in the Alias property value helpdesk. - -- Recipients without user accounts (for example, room mailboxes, mail contacts, and distribution groups): The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). - -If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). - -The Alias parameter never generates or updates the primary email address of a mail contact or a mail user. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ArbitrationMailbox -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -```yaml -Type: MailboxIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ArchiveGuid -This parameter is available only in on-premises Exchange. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ArchiveName -This parameter is available only in on-premises Exchange. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassModerationFromSendersOrMembers -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple senders and overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". - -To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="\<sender1\>","\<sender2\>"...; Remove="\<sender3\>","\<sender4\>"...}. - -This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CreateDTMFMap -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: - -- $true: A DTMF map is created for the recipient. This is the default value. - -- $false: A DTMF map isn't created for the recipient. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute1 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute10 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute11 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute12 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute13 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute14 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute15 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute2 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute3 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute4 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute5 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute6 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute7 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute8 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute9 -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataEncryptionPolicy -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: - -- Name - -- Distinguished name (DN) - -- GUID - -You can use the Get-DataEncryptionPolicy cmdlet to view the available policies. - -```yaml -Type: DataEncryptionPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is available only in on-premises Exchange. - -The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.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. Some examples of valid values include: - -- SMTP: The primary SMTP address. You can use this value only once in a command. - -- smtp: Other SMTP email addresses. - -- X400: X.400 addresses in on-premises Exchange. - -- X500: X.500 addresses in on-premises Exchange. - -If you don't include a \<Type\> value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. - -To specify the primary SMTP email address, you can use any of the following methods: - -- Use the \<Type\> value SMTP on the address. - -- The first email address when you don't use any \<Type\> values, or when you use multiple \<Type\> values of smtp. - -- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. - -The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. - -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",..."\<Type\>:\<emailaddressN\>". - -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",...; Remove="\<Type\>:\<emailaddress2\>","\<Type\>:\<emailaddress2\>",...}. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddressPolicyEnabled -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: - -- $true: Email address policies are applied to this recipient. This is the default value. - -- $false: Email address policies aren't applied to this recipient. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExchangeGuid -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute1 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute2 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute3 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute4 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute5 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalEmailAddress -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. - -When you use the ExternalEmailAddress parameter to change the external email address, the old external email address isn't kept as a proxy address. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GrantSendOnBehalfTo -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 (\<Sender\> on behalf of \<Mail user\>), 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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -By default, this parameter is blank, which means no one else has permission to send on behalf of this mail user. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HiddenFromAddressListsEnabled -The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - -- $true: The recipient isn't visible in address lists. - -- $false: The recipient is visible in address lists. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreDefaultScope -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 Management Shell session, and to use the entire forest as the scope. This allows the command to access Active Directory objects that aren't currently available in the default scope. - -Using the IgnoreDefaultScope switch introduces the following restrictions: - -- You can't use the DomainController parameter. The command uses an appropriate global catalog server automatically. - -- You can only use the DN for the Identity parameter. Other forms of identification, such as alias or GUID, aren't accepted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImmutableId -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. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JournalArchiveAddress -This parameter is available only in the cloud-based service. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MacAttachmentFormat -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) - -- UuEncode - -- AppleSingle - -- AppleDouble - -The MacAttachmentFormat and MessageFormat parameters are interdependent: - -- MessageFormat is Text: MacAttachmentFormat can be BinHex or UuEncode. - -- MessageFormat is Mime: MacAttachmentFormat can be BinHex, AppleSingle, or AppleDouble. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxRegion -This parameter is available only in the cloud-based service. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTip -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: - -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \<html\>\<body\>This mailbox is not monitored\</body\>\</html\>. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\<MailTip text\>. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTipTranslations -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: - -@{Add="\<culture 1\>:\<localized text 1\>","\<culture 2\>:\<localized text 2\>"...; Remove="\<culture 3\>:\<localized text 3\>","\<culture 4\>:\<localized text 4\>"...} - -\<culture\> is a valid ISO 639 two-letter culture code that's associated with the language. - -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxReceiveSize -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 user. Messages larger than the maximum size are rejected. - -When you enter a value, qualify the value with one of the following units: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). - -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSendSize -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 user. - -When you enter a value, qualify the value with one of the following units: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). - -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageBodyFormat -The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - -- Text - -- Html - -- TextAndHtml (This is the default value) - -The MessageFormat and MessageBodyFormat parameters are interdependent: - -- MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - -- MessageFormat is Text: MessageBodyFormat can only be Text. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MessageFormat -The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - -- Text - -- Mime (This is the default value) - -The MessageFormat and MessageBodyFormat parameters are interdependent: - -- MessageFormat is Mime: MessageBodyFormat can be Text, Html, or TextAndHtml. - -- MessageFormat is Text: MessageBodyFormat can only be Text. - -Therefore, if you want to change the MessageFormat parameter from Mime to Text, you must also change the MessageBodyFormat parameter to Text. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MicrosoftOnlineServicesID -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: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModeratedBy -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModerationEnabled -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. - -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. - -You use the ModeratedBy parameter to specify the moderators. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -This parameter is available only in the cloud-based service. - -The Password parameter allows users to change their own password. - -This parameter uses the syntax `(ConvertTo-SecureString -String '<password>' -AsPlainText -Force)`. Or, before you run this command, store the password as a variable (for example, `$password = Read-Host "Enter password" -AsSecureString`), and then use the variable name (`$password`) for this parameter. - -You can't use this parameter to change another user's password (the parameter is available only via the MyBaseOptions user role). To change another user's password, use the NewPassword parameter on the Set-MsolUserPassword cmdlet in Office 365 (Azure AD) PowerShell. For connection instructions, see [Connect to Office 365 PowerShell](https://go.microsoft.com/fwlink/p/?LinkId=614839). - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimarySmtpAddress -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. - -By default, the primary address is the same as the ExternalEmailAddress parameter value. - -If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, but that means the email addresses of the mail user are no longer automatically updated by email address policies. We recommend that you don't set the primary email address to a value other than the ExternalEmailAddress unless you're in a cross-forest scenario. - -The PrimarySmtpAddress parameter updates the primary email address and WindowsEmailAddress property to the same value. - -```yaml -Type: SmtpAddress -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecipientLimits -This parameter is available only in on-premises Exchange. - -The RecipientLimits parameter specifies the maximum number of recipients allowed in messages sent by the mail user. - -A valid value is an integer or the value unlimited. The default value is unlimited. - -The value unlimited indicates the maximum number of recipients per message for the mail user is controlled elsewhere (for example, organization, server, or connector limits). - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecoverableItemsQuota -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. - -When you enter a value, qualify the value with one of the following units: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 30 gigabytes (32212254720 bytes). - -The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecoverableItemsWarningQuota -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. - -When you enter a value, qualify the value with one of the following units: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -- TB (terabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 20 gigabytes (21474836480 bytes). - -The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RejectMessagesFrom -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". - -To add or remove senders without affecting other existing entries, use the following syntax: @{Add="\<sender1\>","\<sender2\>"...; Remove="\<sender1\>","\<sender2\>"...}. - -The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RejectMessagesFromDLMembers -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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: \<group1\>,\<group2\>,...\<groupN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<group1\>","\<group2\>",..."\<groupN\>". - -To add or remove groups without affecting other existing entries, use the following syntax: @{Add="\<group1\>","\<group2\>"...; Remove="\<group1\>","\<group2\>"...}. - -The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all groups. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RejectMessagesFromSendersOrMembers -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. - -To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". - -To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. - -The individual senders and groups you specify for this parameter are automatically copied to the RejectMessagesFrom and RejectMessagesFromDLMembers properties, respectively. Therefore, you can't use the RejectMessagesFromSendersOrMembers parameter and the RejectMessagesFrom or RejectMessagesFromDLMembers parameters in the same command. - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveMailboxProvisioningConstraint -This parameter is available only in the cloud-based service. - -{{ Fill RemoveMailboxProvisioningConstraint Description }} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemovePicture -This parameter is available only in on-premises Exchange. - -The RemovePicture switch specifies whether to remove 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. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSpokenName -This parameter is available only in on-premises Exchange. - -The RemoveSpokenName parameter specifies whether to remove the spoken name from the mail user. You don't need to specify a value with this switch. - -You can add a sound file to a mail user by using the Import-RecipientDataProperty cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireSenderAuthenticationEnabled -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. - -- $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResetPasswordOnNextLogon -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: - -- $true: The user is required to change their password then next time they successfully log on. - -- $false: The user isn't required to change their password then next time they successfully log on. This is the default value. - -You can't use this parameter to require another user to change their password (the parameter is available only via the MyBaseOptions user role). You need to use the ForceChangePassword parameter on the Set-MsolUserPassword cmdlet in Office 365 (Azure AD) PowerShell. For connection instructions, see [Connect to Office 365 PowerShell](https://go.microsoft.com/fwlink/p/?LinkId=614839). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SamAccountName -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 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryAddress -The SecondaryAddress parameter specifies the secondary address used by the Unified Messaging (UM)-enabled user. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryDialPlan -The SecondaryDialPlan parameter specifies a secondary UM dial plan to use. This parameter is provided to create a secondary proxy address. - -```yaml -Type: UMDialPlanIdParameter -Parameter Sets: (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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendModerationNotifications -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. - -- Internal: Notify senders in the organization when their messages aren't approved. - -- Never: Don't notify anyone when a message isn't approved. - -This parameter is only meaningful when moderation is enabled (the ModerationEnabled parameter has the value $true). - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SimpleDisplayName -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 - -- A - Z - -- 0 - 9 - -- "\<space\>", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipDualWrite -This parameter is available only in Exchange 2016 or later. - -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UMDtmfMap -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: - -- emailAddress:\<integers\> - -- lastNameFirstName:\<integers\> - -- firstNameLastName:\<integers\> - -To enter values that overwrite all existing entries, use the following syntax: emailAddress:\<integers\>,lastNameFirstName:\<integers\>,firstNameLastName:\<integers\>. - -If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:\<integers\>, all existing lastNameFirstName and firstNameLastName values are removed. - -To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:\<integers\>","lastNameFirstName:\<integers\>","firstNameLastName:\<integers\>"; Remove="emailAddress:\<integers\>","lastNameFirstName:\<integers\>","firstNameLastName:\<integers\>"}. - -If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:\<integers1\>","emailAddress:\<integers2\>} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseMapiRichTextFormat -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. - -- Never: TNEF is never used for any messages sent to the mail user or mail contact. TNEF messages are converted to plain text. - -- UseDefaultSettings: TNEF messages aren't specifically allowed or prevented for the mail user or mail contact. Whether TNEF messages are sent to the recipient depends on the remote domain TNEF settings (the default remote domain or a specific remote domain), or the Outlook Rich Text message settings specified by the sender in Outlook. - -The default value is UseDefaultSettings. - -```yaml -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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsePreferMessageFormat -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. - -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserCertificate -This parameter is reserved for internal Microsoft use. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserSMimeCertificate -This parameter is reserved for internal Microsoft use. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName -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. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value 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 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WindowsEmailAddress -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. - -- In environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. - -The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. - -```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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### -To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. - -## OUTPUTS - -### -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/users-and-groups/Set-UnifiedGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Set-UnifiedGroup.md deleted file mode 100644 index 113a1b216a..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Set-UnifiedGroup.md +++ /dev/null @@ -1,1245 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/set-unifiedgroup -applicable: Exchange Online -title: Set-UnifiedGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Set-UnifiedGroup - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Set-UnifiedGroup cmdlet to modify Office 365 Groups in your cloud-based organization. To modify members, owners, and subscribers of Office 365 Groups, use the Add-UnifiedGroupLinks and Remove-UnifiedGroupLinks cmdlets. - -**IMPORTANT**: You can't use this cmdlet to remove all Microsoft Online Email Routing Address (MOERA) addresses from the group. There must be at least one MOERA address attached to a group at any given point of time. To learn more about MOERA addresses, see [How the proxyAddresses attribute is populated in Azure AD](https://support.microsoft.com/help/3190357/how-the-proxyaddresses-attribute-is-populated-in-azure-ad). - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Set-UnifiedGroup [-Identity] <UnifiedGroupIdParameter> - [-AcceptMessagesOnlyFromSendersOrMembers <MultiValuedProperty>] - [-AccessType <ModernGroupTypeInfo>] - [-Alias <String>] - [-AlwaysSubscribeMembersToCalendarEvents] - [-AuditLogAgeLimit <EnhancedTimeSpan>] - [-AutoSubscribeNewMembers] - [-CalendarMemberReadOnly] - [-Classification <String>] - [-Confirm] - [-ConnectorsEnabled] - [-CustomAttribute1 <String>] - [-CustomAttribute10 <String>] - [-CustomAttribute11 <String>] - [-CustomAttribute12 <String>] - [-CustomAttribute13 <String>] - [-CustomAttribute14 <String>] - [-CustomAttribute15 <String>] - [-CustomAttribute2 <String>] - [-CustomAttribute3 <String>] - [-CustomAttribute4 <String>] - [-CustomAttribute5 <String>] - [-CustomAttribute6 <String>] - [-CustomAttribute7 <String>] - [-CustomAttribute8 <String>] - [-CustomAttribute9 <String>] - [-DataEncryptionPolicy <DataEncryptionPolicyIdParameter>] - [-DisplayName <String>] - [-EmailAddresses <ProxyAddressCollection>] - [-ExtensionCustomAttribute1 <MultiValuedProperty>] - [-ExtensionCustomAttribute2 <MultiValuedProperty>] - [-ExtensionCustomAttribute3 <MultiValuedProperty>] - [-ExtensionCustomAttribute4 <MultiValuedProperty>] - [-ExtensionCustomAttribute5 <MultiValuedProperty>] - [-ForceUpgrade] - [-GrantSendOnBehalfTo <MultiValuedProperty>] - [-HiddenFromAddressListsEnabled <Boolean>] - [-HiddenFromExchangeClientsEnabled] - [-Language <CultureInfo>] - [-MailboxRegion <String>] - [-MailTip <String>] - [-MailTipTranslations <MultiValuedProperty>] - [-MaxReceiveSize <Unlimited>] - [-MaxSendSize <Unlimited>] - [-ModeratedBy <MultiValuedProperty>] - [-ModerationEnabled <Boolean>] - [-Notes <String>] - [-PrimarySmtpAddress <SmtpAddress>] - [-RejectMessagesFromSendersOrMembers <MultiValuedProperty>] - [-RequireSenderAuthenticationEnabled <Boolean>] - [-SubscriptionEnabled] - [-UnifiedGroupWelcomeMessageEnabled] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 Groups are group objects that are available across Office 365 services. - -The HiddenGroupMembershipEnabled parameter is only available on the New-UnifiedGroup cmdlet. You can't change this setting on an existing Office 365 Group group. - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Set-UnifiedGroup -Identity "Marketing Department" -PrimarySmtpAddress marketing@contoso.com -RequireSenderAuthenticationEnabled $false -``` - -This example makes the following changes to the Office 365 Group named Marketing Department: - -- The primary email address is changed to marketing@contoso.com. - -- The Office 365 Group is allowed to receive mail from unauthenticated (external) senders. - -### Example 2 -```powershell -Set-UnifiedGroup -Identity "Legal Department" -AccessType Private -``` - -This example changes the Office 365 Group named Legal Department from a public group to a private group. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the Office 365 Group that you want to modify. You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: UnifiedGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -AcceptMessagesOnlyFromSendersOrMembers -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. - -To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AccessType -The AccessType parameter specifies the privacy type for the Office 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. - -- Private: The group content and conversations are only available to members of the group, and joining the group requires approval from a group owner. - -Note: Although a user needs to be a member to participate in a private group, anyone can send email to a private group, and receive replies from the private group. - -```yaml -Type: ModernGroupTypeInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Alias -The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the Office 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 value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', \*, +, -, /, =, ?, ^, \_, \`, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlwaysSubscribeMembersToCalendarEvents -The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Office 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. - -- If you use this exact syntax: -AlwaysSubscribeMembersToCalendarEvents:$false, all future members that are added to the group will have their subscriptions set to ReplyOnly. - -Group members can change their own subscription settings, which can override your intended use of this switch. - -The AutoSubscribeNewMembers switch overrides this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuditLogAgeLimit -The AuditLogAgeLimit parameter specifies the maximum age of audit log entries for the Office 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. - -For example, to specify 60 days for this parameter, use 60.00:00:00. - -```yaml -Type: EnhancedTimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoSubscribeNewMembers -The AutoSubscribeNewMembers switch specifies whether to automatically subscribe new members that are added to the Office 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. - -- If you don't want to subscribe new members to conversations and calendar events, use this exact syntax: -AutoSubscribeNewMembers:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CalendarMemberReadOnly -The CalendarMemberReadOnly switch specifies whether to set read-only Calendar permissions to the Office 365 Group for members of the group. - -- To set read-only Calendar permissions, use the CalendarMemberReadOnly switch without a value. - -- To remove read-only Calendar permissions, use this exact syntax: -CalendarMemberReadOnly:$false. - -To view the current value of the CalendarMemberReadOnly property on an Office 365 Group, replace \<EmailAddress\> with the email address of the group, and run this command: Get-UnifiedGroup -Identity \<EmailAddress\> -IncludeAllProperties | Format-List \*Calendar\*. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Classification -The Classification parameter specifies the classification for the Office 365 Group. You need to configure the list of available classifications in Azure Active Directory before you can specify a value for this parameter. For more information, see [Azure Active Directory cmdlets for configuring group settings](https://go.microsoft.com/fwlink/p/?LinkId=827484). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectorsEnabled -The ConnectorsEnabled specifies whether to enable the ability to use connectors for the Office 365 Group. - -- To enable connectors, use the ConnectorsEnabled switch without a value. - -- To disable connectors, use this exact syntax: -ConnectorsEnabled:$false. - -To use this switch, the value of the ConnectorsEnabled parameter on the Set-OrganizationConfig cmdlet must be set to $true (which is the default value). - -For more information about connectors for Office 365 Groups, see [Connect apps to your groups in Outlook](https://go.microsoft.com/fwlink/p/?LinkId=787545). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute1 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute10 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute11 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute12 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute13 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute14 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute15 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute2 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute3 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute4 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute5 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute6 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute7 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute8 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomAttribute9 -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataEncryptionPolicy -The DataEncryptionPolicy parameter specifies the data encryption policy that's applied to the Office 365 Group. You can use any value that uniquely identifies the policy. For example: - -- Name - -- Distinguished name (DN) - -- GUID - -To remove an existing policy, use the value $null. - -```yaml -Type: DataEncryptionPolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The DisplayName parameter specifies the name of the Office 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -The EmailAddresses parameter specifies all the 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://docs.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. Some examples of valid values include: - -- SMTP: The primary SMTP address. You can use this value only once in a command. - -- smtp: Other SMTP email addresses. - -- X400: X.400 addresses in on-premises Exchange. - -- X500: X.500 addresses in on-premises Exchange. - -If you don't include a \<Type\> value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. - -To specify the primary SMTP email address, you can use any of the following methods: - -- Use the \<Type\> value SMTP on the address. - -- The first email address when you don't use any \<Type\> values, or when you use multiple \<Type\> values of smtp. - -- Use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. - -To replace all existing proxy email addresses with the values you specify, use the following syntax: "\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",..."\<Type\>:\<emailaddressN\>". - -To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="\<Type\>:\<emailaddress1\>","\<Type\>:\<emailaddress2\>",...; Remove="\<Type\>:\<emailaddress2\>","\<Type\>:\<emailaddress2\>",...}. - -```yaml -Type: ProxyAddressCollection -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute1 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute2 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute3 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute4 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionCustomAttribute5 -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceUpgrade -The ForceUpgrade switch specifies whether to suppress 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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GrantSendOnBehalfTo -The GrantSendOnBehalfTo parameter specifies who can send on behalf of this Office 365 Group. Although messages that are sent on behalf of the group clearly show the sender in the From field (\<Sender\> on behalf of \<Office365Group\>), 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: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -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, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>". - -To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}. - -By default, this parameter is blank, which means no one else has permission to send on behalf of this Office 365 Group group. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HiddenFromAddressListsEnabled -The HiddenFromAddressListsEnabled parameter specifies whether the Office 365 Group appears in the global address list (GAL) and other address lists in your organization. Valid values are: - -- $true: The Office 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 Office 365 Group, the group will still appear in the navigation pane in Outlook and Outlook on the web if HiddenFromExchangeClientsEnabled property is **NOT** enabled. - -- $false: The Office 365 Group is visible in the GAL and other address lists. This is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HiddenFromExchangeClientsEnabled -The HiddenFromExchangeClientsEnabled switch specifies whether the Office 365 Group is hidden from Outlook clients connected to Office 365. - -- To enable this setting, you don't need to specify a value with this switch. The Office 365 Group is hidden from Outlook experiences. The group isn't visible in the Outlook left-hand navigation and isn't be visible in the global address list (GAL). The group name won't resolve during the creation 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 also can't find the group by using the Discover option in Outlook on the web. Additionally, the HiddenFromAddressListsEnabled property will also be set to true to prevent the group from showing in the GAL and in the Offline Address Book (OAB). - -- To disable this setting, use this exact syntax: -HiddenFromExchangeClientsEnabled:$false. The Office 365 Group is not hidden from Outlook experiences. The group will be visible in the GAL and other address lists. This is the default value. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -The Language parameter specifies language preference for the Office 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://go.microsoft.com/fwlink/p/?linkId=184859). - -```yaml -Type: CultureInfo -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailboxRegion -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTip -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: - -- HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: \<html\>\<body\>This mailbox is not monitored\</body\>\</html\>. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. - -- The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:\<MailTip text\>. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MailTipTranslations -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: - -@{Add="\<culture 1\>:\<localized text 1\>","\<culture 2\>:\<localized text 2\>"...; Remove="\<culture 3\>:\<localized text 3\>","\<culture 4\>:\<localized text 4\>"...} - -\<culture\> is a valid ISO 639 two-letter culture code that's associated with the language. - -For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxReceiveSize -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). - -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSendSize -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: - -- B (bytes) - -- KB (kilobytes) - -- MB (megabytes) - -- GB (gigabytes) - -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. - -A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). - -For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModeratedBy -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 - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>". - -You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModerationEnabled -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. - -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. - -You use the ModeratedBy parameter to specify the moderators. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -The Notes parameter specifies the description of the Office 365 Group. 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimarySmtpAddress -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 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RejectMessagesFromSendersOrMembers -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. - -To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: \<sender1\>,\<sender2\>,...\<senderN\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<sender1\>","\<sender2\>",..."\<senderN\>". - -To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. - -The individual senders and groups you specify for this parameter are automatically copied to the RejectMessagesFrom and RejectMessagesFromDLMembers properties, respectively. Therefore, you can't use the RejectMessagesFromSendersOrMembers parameter and the RejectMessagesFrom or RejectMessagesFromDLMembers parameters in the same command. - -By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireSenderAuthenticationEnabled -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. - -- $false: Messages are accepted from authenticated (internal) and unauthenticated (external) senders. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriptionEnabled -The SubscriptionEnabled switch specifies whether subscriptions to conversations and calendar events are enabled for the Office 365 Group. - -- To change the value to $true, use this switch without a value. - -- To change the value to $false, use this exact syntax: -SubscriptionEnabled:$false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnifiedGroupWelcomeMessageEnabled -The UnifiedGroupWelcomeMessageEnabled switch specifies whether to enable or disable sending system-generated welcome messages to users who are added as members to the Office 365 Group. - -- To enable this setting, you don't need to specify a value with this switch. - -- To disable this setting, use this exact syntax: -UnifiedGroupWelcomeMessageEnabled:$false. - -This setting is enabled by default. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Undo-SoftDeletedUnifiedGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Undo-SoftDeletedUnifiedGroup.md deleted file mode 100644 index a98e6b1724..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Undo-SoftDeletedUnifiedGroup.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/undo-softdeletedunifiedgroup -applicable: Exchange Online -title: Undo-SoftDeletedUnifiedGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Undo-SoftDeletedUnifiedGroup - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Undo-SoftDeletedUnifiedGroup cmdlet to restore soft-deleted Office 365 groups in your cloud-based organization. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Undo-SoftDeletedUnifiedGroup [-SoftDeletedObject] <UnifiedGroupIdParameter> [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Office 365 groups are group objects that are available across Office 365 services. - -Soft-deleted Office 365 groups are groups that have been deleted, but can be restored within 30 days of being deleted. All of the group contents can be restored within this period. After 30 days, soft-deleted Office 365 groups are marked for permanent deletion and can't be restored. - -To display all soft-deleted Office 365 groups in your organization, use the Get-AzureADMSDeletedGroup cmdlet in Azure Active Directory PowerShell. To permanently remove (purge) a soft-deleted Office 365 group, use the Remove-AzureADMSDeletedDirectoryObject cmdlet in Azure Active Directory PowerShell. For more information, see [Permanently delete an Office 365 group](https://support.office.com/article/b7c66b59-657a-4e1a-8aa0-8163b1f4eb54#bkmk_perm). - -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Undo-SoftDeletedUnifiedGroup -SoftDeletedObject "Marketing Department" -``` - -This example restores the soft-deleted Office 365 Group named Marketing Department. - -## PARAMETERS - -### -SoftDeletedObject -The SoftDeletedObject parameter specifies the soft-deleted Office 365 Group that you want to restore. You can use any value that uniquely identifies the Office 365 Group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- \<domain name\>\\\<account name\> - -- Email address - -- GUID - -- LegacyExchangeDN - -- SamAccountName - -- User ID or user principal name (UPN) - -Note: You might need to use the DistinguishedName or ExchangeGuid property to identify the soft-deleted Office 365 Group, because it's possible for an active Office 365 Group and a soft-deleted Office 365 Group to have the same primary SMTP address. - -```yaml -Type: UnifiedGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually 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 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Update-EOPDistributionGroupMember.md b/exchange/exchange-ps/exchange/users-and-groups/Update-EOPDistributionGroupMember.md deleted file mode 100644 index e7bab31c31..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Update-EOPDistributionGroupMember.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/update-eopdistributiongroupmember -applicable: Exchange Online Protection -title: Update-EOPDistributionGroupMember -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "eop-ps" ---- - -# Update-EOPDistributionGroupMember - -## SYNOPSIS -This cmdlet is available only in Exchange Online Protection. - -Use the Update-EOPDistributionGroupMember cmdlet to add or remove members from distribution groups and mail-enabled security groups in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Update-DistributionGroupMember cmdlet. - -Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can't use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP. - -This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible. - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Update-EOPDistributionGroupMember [-ExternalDirectoryObjectId <String>] - [-Identity <DistributionGroupIdParameter>] [-Members <String[]>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Update-EOPDistributionGroupMember -Identity "Security Team" -Members @("Kitty Petersen","Tyson Fawcett") -``` - -This example replaces the current members of the Security Team distribution group with Kitty Petersen and Tyson Fawcett. - -### Example 2 -```powershell -$CurrentMemberObjects = Get-DistributionGroupMember "Security Team"; $CurrentMemberNames = $CurrentMemberObjects | % {$_.name}; $CurrentMemberNames += "Tyson Fawcett"; Update-EOPDistributionGroupMember -Identity "Security Team" -Members $CurrentMemberNames -``` - -This example adds a new user named Tyson Fawcett to the distribution group named Security Team while preserving the current members of the group. The current member objects are retrieved in a collection, the collection is filtered to extract the names, the user "Tyson Fawcett" is added, and the updated name list replaces the current membership of the distribution group. - -## PARAMETERS - -### -ExternalDirectoryObjectId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter specifies the distribution group or mail-enabled security group that you want to update. You can use any value that uniquely identifies the group. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -```yaml -Type: DistributionGroupIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Members -The Members parameter specifies the list of recipients (mail-enabled objects) in the distribution group or mail-enabled security group. In Exchange Online Protection, the valid recipient types are: - -- Mail users - -- Distribution groups - -- Mail-enabled security groups - -You can use any value that uniquely identifies the recipient. For example: - -- Name - -- Alias - -- Distinguished name (DN) - -- Canonical DN - -- Email address - -- GUID - -To replace the current members of the group with the recipients that you specify, use the syntax @("\<recipient1\>","\<recipient2\>"...). To add new group members without affecting the existing members, see Example 2 in the Examples section. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/users-and-groups/Upgrade-DistributionGroup.md b/exchange/exchange-ps/exchange/users-and-groups/Upgrade-DistributionGroup.md deleted file mode 100644 index a9cf8ac6cd..0000000000 --- a/exchange/exchange-ps/exchange/users-and-groups/Upgrade-DistributionGroup.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://docs.microsoft.com/powershell/module/exchange/users-and-groups/upgrade-distributiongroup -applicable: Exchange Online -title: Upgrade-DistributionGroup -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: -monikerRange: "exchonline-ps" ---- - -# Upgrade-DistributionGroup - -## SYNOPSIS -This cmdlet is available only in the cloud-based service. - -Use the Upgrade-DistributionGroup cmdlet to upgrade distribution groups to Office 365 groups. This cmdlet only works on distribution groups, not mail-enabled security groups. - -Note: Before you use this cmdlet, verify there are no email address policies that you created with the IncludeUnifiedGroupRecipients parameter; otherwise the command will fail. Remove and recreate the email address policies after you upgrade your distribution groups to Office 365 groups. - -> [!NOTE] -> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2). - -For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-server/exchange-cmdlet-syntax). - -## SYNTAX - -``` -Upgrade-DistributionGroup [-DlIdentities] <MultiValuedProperty> [-ActionType <String>] - [-ExecutingUser <RecipientIdParameter>] [<CommonParameters>] -``` - -## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Upgrade-DistributionGroup -DlIdentities hr@contoso.com,finance@contoso.com -``` - -This example upgrades the specified distribution groups to Office 365 groups. - -## PARAMETERS - -### -DlIdentities -The DlIdentities parameter specifies the email address of the distribution group that you want to upgrade to an Office 365 Group. - -You can specify multiple values separated by commas. - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -ActionType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExecutingUser -This parameter is reserved for internal Microsoft use. - -```yaml -Type: RecipientIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### - -## OUTPUTS - -### - -## NOTES - -## RELATED LINKS diff --git a/exchange/mapping/MAML2Yaml/monikerMapping.json b/exchange/mapping/MAML2Yaml/monikerMapping.json new file mode 100644 index 0000000000..4e2ae5eca8 --- /dev/null +++ b/exchange/mapping/MAML2Yaml/monikerMapping.json @@ -0,0 +1,12 @@ +{ + "exchange-ps": { + "conceptualToc": "docs-conceptual/toc.yml", + "conceptualTocUrl": "/powershell/exchange/exchange-ps/toc.json", + "referenceTocUrl": "/powershell/module/exchange-ps/toc.json", + "packageRoot": "exchange-ps", + "serviceMap": "mapping/serviceMapping.json", + "modules": { + "exchange": {} + } + } +} \ No newline at end of file diff --git a/exchange/mapping/monikerMapping.json b/exchange/mapping/monikerMapping.json deleted file mode 100644 index 848fc16750..0000000000 --- a/exchange/mapping/monikerMapping.json +++ /dev/null @@ -1,11 +0,0 @@ -{ - "exchange-ps": { - "conceptualToc": "docs-conceptual/toc.yml", - "conceptualTocUrl": "/powershell/exchange/exchange-ps/toc.json", - "referenceTocUrl": "/powershell/module/exchange-ps/toc.json", - "packageRoot": "exchange-ps", - "modules": { - "exchange": {} - } - } -} \ No newline at end of file diff --git a/exchange/mapping/serviceMapping.json b/exchange/mapping/serviceMapping.json new file mode 100644 index 0000000000..b6691a949e --- /dev/null +++ b/exchange/mapping/serviceMapping.json @@ -0,0 +1,1407 @@ +{ + "Add-ADPermission": "active-directory", + "Dump-ProvisioningCache": "active-directory", + "Get-ADPermission": "active-directory", + "Get-ADServerSettings": "active-directory", + "Get-ADSite": "active-directory", + "Get-AdSiteLink": "active-directory", + "Get-DomainController": "active-directory", + "Get-OrganizationalUnit": "active-directory", + "Get-Trust": "active-directory", + "Get-UserPrincipalNamesSuffix": "active-directory", + "Remove-ADPermission": "active-directory", + "Reset-ProvisioningCache": "active-directory", + "Set-ADServerSettings": "active-directory", + "Set-ADSite": "active-directory", + "Set-AdSiteLink": "active-directory", + "Disable-AntiPhishRule": "defender-for-office-365", + "Disable-ATPProtectionPolicyRule": "defender-for-office-365", + "Disable-SafeAttachmentRule": "defender-for-office-365", + "Disable-SafeLinksRule": "defender-for-office-365", + "Enable-AntiPhishRule": "defender-for-office-365", + "Enable-ATPProtectionPolicyRule": "defender-for-office-365", + "Enable-SafeAttachmentRule": "defender-for-office-365", + "Enable-SafeLinksRule": "defender-for-office-365", + "Get-AntiPhishPolicy": "defender-for-office-365", + "Get-AntiPhishRule": "defender-for-office-365", + "Get-ATPBuiltInProtectionRule": "defender-for-office-365", + "Get-AtpPolicyForO365": "defender-for-office-365", + "Get-ATPProtectionPolicyRule": "defender-for-office-365", + "Get-ATPTotalTrafficReport": "defender-for-office-365", + "Get-ContentMalwareMdoAggregateReport": "defender-for-office-365", + "Get-ContentMalwareMdoDetailReport": "defender-for-office-365", + "Get-EmailTenantSettings": "defender-for-office-365", + "Get-MailDetailATPReport": "defender-for-office-365", + "Get-MailTrafficATPReport": "defender-for-office-365", + "Get-SafeAttachmentPolicy": "defender-for-office-365", + "Get-SafeAttachmentRule": "defender-for-office-365", + "Get-SafeLinksAggregateReport": "defender-for-office-365", + "Get-SafeLinksDetailReport": "defender-for-office-365", + "Get-SafeLinksPolicy": "defender-for-office-365", + "Get-SafeLinksRule": "defender-for-office-365", + "Get-SpoofIntelligenceInsight": "defender-for-office-365", + "Get-SpoofMailReport": "defender-for-office-365", + "New-AntiPhishPolicy": "defender-for-office-365", + "New-AntiPhishRule": "defender-for-office-365", + "New-ATPBuiltInProtectionRule": "defender-for-office-365", + "New-ATPProtectionPolicyRule": "defender-for-office-365", + "New-SafeAttachmentPolicy": "defender-for-office-365", + "New-SafeAttachmentRule": "defender-for-office-365", + "New-SafeLinksPolicy": "defender-for-office-365", + "New-SafeLinksRule": "defender-for-office-365", + "Remove-AntiPhishPolicy": "defender-for-office-365", + "Remove-AntiPhishRule": "defender-for-office-365", + "Remove-ATPProtectionPolicyRule": "defender-for-office-365", + "Remove-SafeAttachmentPolicy": "defender-for-office-365", + "Remove-SafeAttachmentRule": "defender-for-office-365", + "Remove-SafeLinksPolicy": "defender-for-office-365", + "Remove-SafeLinksRule": "defender-for-office-365", + "Set-AntiPhishPolicy": "defender-for-office-365", + "Set-AntiPhishRule": "defender-for-office-365", + "Set-ATPBuiltInProtectionRule": "defender-for-office-365", + "Set-AtpPolicyForO365": "defender-for-office-365", + "Set-ATPProtectionPolicyRule": "defender-for-office-365", + "Set-EmailTenantSettings": "defender-for-office-365", + "Set-SafeAttachmentPolicy": "defender-for-office-365", + "Set-SafeAttachmentRule": "defender-for-office-365", + "Set-SafeLinksPolicy": "defender-for-office-365", + "Set-SafeLinksRule": "defender-for-office-365", + "Add-AttachmentFilterEntry": "antispam-antimalware", + "Add-ContentFilterPhrase": "antispam-antimalware", + "Add-IPAllowListEntry": "antispam-antimalware", + "Add-IPAllowListProvider": "antispam-antimalware", + "Add-IPBlockListEntry": "antispam-antimalware", + "Add-IPBlockListProvider": "antispam-antimalware", + "Delete-QuarantineMessage": "antispam-antimalware", + "Disable-EOPProtectionPolicyRule": "antispam-antimalware", + "Disable-HostedContentFilterRule": "antispam-antimalware", + "Disable-HostedOutboundSpamFilterRule": "antispam-antimalware", + "Disable-MalwareFilterRule": "antispam-antimalware", + "Disable-ReportSubmissionRule": "antispam-antimalware", + "Enable-AntispamUpdates": "antispam-antimalware", + "Enable-EOPProtectionPolicyRule": "antispam-antimalware", + "Enable-HostedContentFilterRule": "antispam-antimalware", + "Enable-HostedOutboundSpamFilterRule": "antispam-antimalware", + "Enable-MalwareFilterRule": "antispam-antimalware", + "Export-QuarantineMessage": "antispam-antimalware", + "Enable-ReportSubmissionRule": "antispam-antimalware", + "Get-AgentLog": "antispam-antimalware", + "Get-AggregateZapReport": "antispam-antimalware", + "Get-ArcConfig": "antispam-antimalware", + "Get-AttachmentFilterEntry": "antispam-antimalware", + "Get-AttachmentFilterListConfig": "antispam-antimalware", + "Get-BlockedConnector": "antispam-antimalware", + "Get-BlockedSenderAddress": "antispam-antimalware", + "Get-ConfigAnalyzerPolicyRecommendation": "antispam-antimalware", + "Get-ContentFilterConfig": "antispam-antimalware", + "Get-ContentFilterPhrase": "antispam-antimalware", + "Get-CustomizedUserSubmission": "antispam-antimalware", + "Get-DetailZapReport": "antispam-antimalware", + "Get-DkimSigningConfig": "antispam-antimalware", + "Get-EOPProtectionPolicyRule": "antispam-antimalware", + "Get-ExoPhishSimOverrideRule": "antispam-antimalware", + "Get-ExoSecOpsOverrideRule": "antispam-antimalware", + "Get-HostedConnectionFilterPolicy": "antispam-antimalware", + "Get-HostedContentFilterPolicy": "antispam-antimalware", + "Get-HostedContentFilterRule": "antispam-antimalware", + "Get-HostedOutboundSpamFilterPolicy": "antispam-antimalware", + "Get-HostedOutboundSpamFilterRule": "antispam-antimalware", + "Get-IPAllowListConfig": "antispam-antimalware", + "Get-IPAllowListEntry": "antispam-antimalware", + "Get-IPAllowListProvider": "antispam-antimalware", + "Get-IPAllowListProvidersConfig": "antispam-antimalware", + "Get-IPBlockListConfig": "antispam-antimalware", + "Get-IPBlockListEntry": "antispam-antimalware", + "Get-IPBlockListProvider": "antispam-antimalware", + "Get-IPBlockListProvidersConfig": "antispam-antimalware", + "Get-MailboxJunkEmailConfiguration": "antispam-antimalware", + "Get-MalwareFilteringServer": "antispam-antimalware", + "Get-MalwareFilterPolicy": "antispam-antimalware", + "Get-MalwareFilterRule": "antispam-antimalware", + "Get-PhishSimOverridePolicy": "antispam-antimalware", + "Get-QuarantineMessage": "antispam-antimalware", + "Get-QuarantineMessageHeader": "antispam-antimalware", + "Get-QuarantinePolicy": "antispam-antimalware", + "Get-RecipientFilterConfig": "antispam-antimalware", + "Get-ReportSubmissionPolicy": "antispam-antimalware", + "Get-ReportSubmissionRule": "antispam-antimalware", + "Get-SecOpsOverridePolicy": "antispam-antimalware", + "Get-SenderFilterConfig": "antispam-antimalware", + "Get-SenderIdConfig": "antispam-antimalware", + "Get-SenderReputationConfig": "antispam-antimalware", + "Get-TeamsProtectionPolicy": "antispam-antimalware", + "Get-TeamsProtectionPolicyRule": "antispam-antimalware", + "Get-TenantAllowBlockListItems": "antispam-antimalware", + "Get-TenantAllowBlockListSpoofItems": "antispam-antimalware", + "New-DkimSigningConfig": "antispam-antimalware", + "New-EOPProtectionPolicyRule": "antispam-antimalware", + "New-ExoPhishSimOverrideRule": "antispam-antimalware", + "New-ExoSecOpsOverrideRule": "antispam-antimalware", + "New-HostedContentFilterPolicy": "antispam-antimalware", + "New-HostedContentFilterRule": "antispam-antimalware", + "New-HostedOutboundSpamFilterPolicy": "antispam-antimalware", + "New-HostedOutboundSpamFilterRule": "antispam-antimalware", + "New-MalwareFilterPolicy": "antispam-antimalware", + "New-MalwareFilterRule": "antispam-antimalware", + "New-PhishSimOverridePolicy": "antispam-antimalware", + "New-QuarantinePermissions": "antispam-antimalware", + "New-QuarantinePolicy": "antispam-antimalware", + "New-ReportSubmissionPolicy": "antispam-antimalware", + "New-ReportSubmissionRule": "antispam-antimalware", + "New-SecOpsOverridePolicy": "antispam-antimalware", + "New-TeamsProtectionPolicy": "antispam-antimalware", + "New-TeamsProtectionPolicyRule": "antispam-antimalware", + "New-TenantAllowBlockListItems": "antispam-antimalware", + "New-TenantAllowBlockListSpoofItems": "antispam-antimalware", + "Preview-QuarantineMessage": "antispam-antimalware", + "Release-QuarantineMessage": "antispam-antimalware", + "Remove-AttachmentFilterEntry": "antispam-antimalware", + "Remove-BlockedConnector": "antispam-antimalware", + "Remove-BlockedSenderAddress": "antispam-antimalware", + "Remove-ContentFilterPhrase": "antispam-antimalware", + "Remove-EOPProtectionPolicyRule": "antispam-antimalware", + "Remove-ExoPhishSimOverrideRule": "antispam-antimalware", + "Remove-ExoSecOpsOverrideRule": "antispam-antimalware", + "Remove-HostedContentFilterPolicy": "antispam-antimalware", + "Remove-HostedContentFilterRule": "antispam-antimalware", + "Remove-HostedOutboundSpamFilterPolicy": "antispam-antimalware", + "Remove-HostedOutboundSpamFilterRule": "antispam-antimalware", + "Remove-IPAllowListEntry": "antispam-antimalware", + "Remove-IPAllowListProvider": "antispam-antimalware", + "Remove-IPBlockListEntry": "antispam-antimalware", + "Remove-IPBlockListProvider": "antispam-antimalware", + "Remove-MalwareFilterPolicy": "antispam-antimalware", + "Remove-MalwareFilterRule": "antispam-antimalware", + "Remove-PhishSimOverridePolicy": "antispam-antimalware", + "Remove-QuarantinePolicy": "antispam-antimalware", + "Remove-ReportSubmissionPolicy": "antispam-antimalware", + "Remove-ReportSubmissionRule": "antispam-antimalware", + "Remove-SecOpsOverridePolicy": "antispam-antimalware", + "Remove-TenantAllowBlockListItems": "antispam-antimalware", + "Remove-TenantAllowBlockListSpoofItems": "antispam-antimalware", + "Rotate-DkimSigningConfig": "antispam-antimalware", + "Set-ArcConfig": "antispam-antimalware", + "Set-AttachmentFilterListConfig": "antispam-antimalware", + "Set-ContentFilterConfig": "antispam-antimalware", + "Set-DkimSigningConfig": "antispam-antimalware", + "Set-EOPProtectionPolicyRule": "antispam-antimalware", + "Set-ExoPhishSimOverrideRule": "antispam-antimalware", + "Set-ExoSecOpsOverrideRule": "antispam-antimalware", + "Set-HostedConnectionFilterPolicy": "antispam-antimalware", + "Set-HostedContentFilterPolicy": "antispam-antimalware", + "Set-HostedContentFilterRule": "antispam-antimalware", + "Set-HostedOutboundSpamFilterPolicy": "antispam-antimalware", + "Set-HostedOutboundSpamFilterRule": "antispam-antimalware", + "Set-IPAllowListConfig": "antispam-antimalware", + "Set-IPAllowListProvider": "antispam-antimalware", + "Set-IPAllowListProvidersConfig": "antispam-antimalware", + "Set-IPBlockListConfig": "antispam-antimalware", + "Set-IPBlockListProvider": "antispam-antimalware", + "Set-IPBlockListProvidersConfig": "antispam-antimalware", + "Set-MailboxJunkEmailConfiguration": "antispam-antimalware", + "Set-MalwareFilteringServer": "antispam-antimalware", + "Set-MalwareFilterPolicy": "antispam-antimalware", + "Set-MalwareFilterRule": "antispam-antimalware", + "Set-PhishSimOverridePolicy": "antispam-antimalware", + "Set-QuarantinePermissions": "antispam-antimalware", + "Set-QuarantinePolicy": "antispam-antimalware", + "Set-RecipientFilterConfig": "antispam-antimalware", + "Set-ReportSubmissionPolicy": "antispam-antimalware", + "Set-ReportSubmissionRule": "antispam-antimalware", + "Set-SecOpsOverridePolicy": "antispam-antimalware", + "Set-SenderFilterConfig": "antispam-antimalware", + "Set-SenderIdConfig": "antispam-antimalware", + "Set-SenderReputationConfig": "antispam-antimalware", + "Set-TeamsProtectionPolicy": "antispam-antimalware", + "Set-TeamsProtectionPolicyRule": "antispam-antimalware", + "Set-TenantAllowBlockListItems": "antispam-antimalware", + "Set-TenantAllowBlockListSpoofItems": "antispam-antimalware", + "Test-IPAllowListProvider": "antispam-antimalware", + "Test-IPBlockListProvider": "antispam-antimalware", + "Test-SenderId": "antispam-antimalware", + "Update-SafeList": "antispam-antimalware", + "Clear-TextMessagingAccount": "client-access", + "Compare-TextMessagingVerificationCode": "client-access", + "Disable-PushNotificationProxy": "client-access", + "Enable-PushNotificationProxy": "client-access", + "Export-AutoDiscoverConfig": "client-access", + "Get-CASMailbox": "client-access", + "Get-CASMailboxPlan": "client-access", + "Get-ClientAccessRule": "client-access", + "Get-ImapSettings": "client-access", + "Get-MailboxCalendarConfiguration": "client-access", + "Get-MailboxMessageConfiguration": "client-access", + "Get-MailboxRegionalConfiguration": "client-access", + "Get-MailboxSpellingConfiguration": "client-access", + "Get-OutlookProvider": "client-access", + "Get-OwaMailboxPolicy": "client-access", + "Get-PopSettings": "client-access", + "Get-TextMessagingAccount": "client-access", + "New-ClientAccessRule": "client-access", + "New-OutlookProvider": "client-access", + "New-OwaMailboxPolicy": "client-access", + "Remove-ClientAccessRule": "client-access", + "Remove-OutlookProvider": "client-access", + "Remove-OwaMailboxPolicy": "client-access", + "Send-TextMessagingVerificationCode": "client-access", + "Set-CASMailbox": "client-access", + "Set-CASMailboxPlan": "client-access", + "Set-ClientAccessRule": "client-access", + "Set-ImapSettings": "client-access", + "Set-MailboxCalendarConfiguration": "client-access", + "Set-MailboxMessageConfiguration": "client-access", + "Set-MailboxRegionalConfiguration": "client-access", + "Set-MailboxSpellingConfiguration": "client-access", + "Set-OutlookProvider": "client-access", + "Set-OwaMailboxPolicy": "client-access", + "Set-PopSettings": "client-access", + "Set-TextMessagingAccount": "client-access", + "Test-CalendarConnectivity": "client-access", + "Test-ClientAccessRule": "client-access", + "Test-EcpConnectivity": "client-access", + "Test-ImapConnectivity": "client-access", + "Test-OutlookConnectivity": "client-access", + "Test-OutlookWebServices": "client-access", + "Test-OwaConnectivity": "client-access", + "Test-PopConnectivity": "client-access", + "Test-PowerShellConnectivity": "client-access", + "Test-WebServicesConnectivity": "client-access", + "Disable-OutlookAnywhere": "client-access-servers", + "Enable-OutlookAnywhere": "client-access-servers", + "Get-ActiveSyncVirtualDirectory": "client-access-servers", + "Get-AuthRedirect": "client-access-servers", + "Get-AutodiscoverVirtualDirectory": "client-access-servers", + "Get-ClientAccessArray": "client-access-servers", + "Get-ClientAccessServer": "client-access-servers", + "Get-ClientAccessService": "client-access-servers", + "Get-EcpVirtualDirectory": "client-access-servers", + "Get-MapiVirtualDirectory": "client-access-servers", + "Get-OutlookAnywhere": "client-access-servers", + "Get-OwaVirtualDirectory": "client-access-servers", + "Get-PowerShellVirtualDirectory": "client-access-servers", + "Get-RpcClientAccess": "client-access-servers", + "Get-WebServicesVirtualDirectory": "client-access-servers", + "New-ActiveSyncVirtualDirectory": "client-access-servers", + "New-AuthRedirect": "client-access-servers", + "New-AutodiscoverVirtualDirectory": "client-access-servers", + "New-ClientAccessArray": "client-access-servers", + "New-EcpVirtualDirectory": "client-access-servers", + "New-MapiVirtualDirectory": "client-access-servers", + "New-OwaVirtualDirectory": "client-access-servers", + "New-PowerShellVirtualDirectory": "client-access-servers", + "New-RpcClientAccess": "client-access-servers", + "New-WebServicesVirtualDirectory": "client-access-servers", + "Remove-ActiveSyncVirtualDirectory": "client-access-servers", + "Remove-AuthRedirect": "client-access-servers", + "Remove-AutodiscoverVirtualDirectory": "client-access-servers", + "Remove-ClientAccessArray": "client-access-servers", + "Remove-EcpVirtualDirectory": "client-access-servers", + "Remove-MapiVirtualDirectory": "client-access-servers", + "Remove-OwaVirtualDirectory": "client-access-servers", + "Remove-PowerShellVirtualDirectory": "client-access-servers", + "Remove-RpcClientAccess": "client-access-servers", + "Remove-WebServicesVirtualDirectory": "client-access-servers", + "Set-ActiveSyncVirtualDirectory": "client-access-servers", + "Set-AuthRedirect": "client-access-servers", + "Set-AutodiscoverVirtualDirectory": "client-access-servers", + "Set-ClientAccessArray": "client-access-servers", + "Set-ClientAccessServer": "client-access-servers", + "Set-ClientAccessService": "client-access-servers", + "Set-EcpVirtualDirectory": "client-access-servers", + "Set-MapiVirtualDirectory": "client-access-servers", + "Set-OutlookAnywhere": "client-access-servers", + "Set-OwaVirtualDirectory": "client-access-servers", + "Set-PowerShellVirtualDirectory": "client-access-servers", + "Set-RpcClientAccess": "client-access-servers", + "Set-WebServicesVirtualDirectory": "client-access-servers", + "Add-DatabaseAvailabilityGroupServer": "database-availability-groups", + "Add-MailboxDatabaseCopy": "database-availability-groups", + "Get-DatabaseAvailabilityGroup": "database-availability-groups", + "Get-DatabaseAvailabilityGroupNetwork": "database-availability-groups", + "Get-MailboxDatabaseCopyStatus": "database-availability-groups", + "Move-ActiveMailboxDatabase": "database-availability-groups", + "New-DatabaseAvailabilityGroup": "database-availability-groups", + "New-DatabaseAvailabilityGroupNetwork": "database-availability-groups", + "Remove-DatabaseAvailabilityGroup": "database-availability-groups", + "Remove-DatabaseAvailabilityGroupNetwork": "database-availability-groups", + "Remove-DatabaseAvailabilityGroupServer": "database-availability-groups", + "Remove-MailboxDatabaseCopy": "database-availability-groups", + "Restore-DatabaseAvailabilityGroup": "database-availability-groups", + "Resume-MailboxDatabaseCopy": "database-availability-groups", + "Set-DatabaseAvailabilityGroup": "database-availability-groups", + "Set-DatabaseAvailabilityGroupNetwork": "database-availability-groups", + "Set-MailboxDatabaseCopy": "database-availability-groups", + "Start-DatabaseAvailabilityGroup": "database-availability-groups", + "Stop-DatabaseAvailabilityGroup": "database-availability-groups", + "Suspend-MailboxDatabaseCopy": "database-availability-groups", + "Test-ReplicationHealth": "database-availability-groups", + "Update-MailboxDatabaseCopy": "database-availability-groups", + "Clear-ActiveSyncDevice": "devices", + "Clear-MobileDevice": "devices", + "Export-ActiveSyncLog": "devices", + "Get-ActiveSyncDevice": "devices", + "Get-ActiveSyncDeviceAccessRule": "devices", + "Get-ActiveSyncDeviceAutoblockThreshold": "devices", + "Get-ActiveSyncDeviceClass": "devices", + "Get-ActiveSyncDeviceStatistics": "devices", + "Get-ActiveSyncMailboxPolicy": "devices", + "Get-ActiveSyncOrganizationSettings": "devices", + "Get-DeviceConditionalAccessPolicy": "devices", + "Get-DeviceConditionalAccessRule": "devices", + "Get-DeviceConfigurationPolicy": "devices", + "Get-DeviceConfigurationRule": "devices", + "Get-DevicePolicy": "devices", + "Get-DeviceTenantPolicy": "devices", + "Get-DeviceTenantRule": "devices", + "Get-MobileDevice": "devices", + "Get-MobileDeviceMailboxPolicy": "devices", + "Get-MobileDeviceStatistics": "devices", + "New-ActiveSyncDeviceAccessRule": "devices", + "New-ActiveSyncMailboxPolicy": "devices", + "New-DeviceConditionalAccessPolicy": "devices", + "New-DeviceConditionalAccessRule": "devices", + "New-DeviceConfigurationPolicy": "devices", + "New-DeviceConfigurationRule": "devices", + "New-DeviceTenantPolicy": "devices", + "New-DeviceTenantRule": "devices", + "New-MobileDeviceMailboxPolicy": "devices", + "Remove-ActiveSyncDevice": "devices", + "Remove-ActiveSyncDeviceAccessRule": "devices", + "Remove-ActiveSyncDeviceClass": "devices", + "Remove-ActiveSyncMailboxPolicy": "devices", + "Remove-DeviceConditionalAccessPolicy": "devices", + "Remove-DeviceConditionalAccessRule": "devices", + "Remove-DeviceConfigurationPolicy": "devices", + "Remove-DeviceConfigurationRule": "devices", + "Remove-DeviceTenantPolicy": "devices", + "Remove-DeviceTenantRule": "devices", + "Remove-MobileDevice": "devices", + "Remove-MobileDeviceMailboxPolicy": "devices", + "Set-ActiveSyncDeviceAccessRule": "devices", + "Set-ActiveSyncDeviceAutoblockThreshold": "devices", + "Set-ActiveSyncMailboxPolicy": "devices", + "Set-ActiveSyncOrganizationSettings": "devices", + "Set-DeviceConditionalAccessPolicy": "devices", + "Set-DeviceConditionalAccessRule": "devices", + "Set-DeviceConfigurationPolicy": "devices", + "Set-DeviceConfigurationRule": "devices", + "Set-DeviceTenantPolicy": "devices", + "Set-DeviceTenantRule": "devices", + "Set-MobileDeviceMailboxPolicy": "devices", + "Test-ActiveSyncConnectivity": "devices", + "Disable-AddressListPaging": "email-addresses-and-address-books", + "Enable-AddressListPaging": "email-addresses-and-address-books", + "Get-AddressBookPolicy": "email-addresses-and-address-books", + "Get-AddressList": "email-addresses-and-address-books", + "Get-DetailsTemplate": "email-addresses-and-address-books", + "Get-EmailAddressPolicy": "email-addresses-and-address-books", + "Get-GlobalAddressList": "email-addresses-and-address-books", + "Get-OabVirtualDirectory": "email-addresses-and-address-books", + "Get-OfflineAddressBook": "email-addresses-and-address-books", + "Move-AddressList": "email-addresses-and-address-books", + "Move-OfflineAddressBook": "email-addresses-and-address-books", + "New-AddressBookPolicy": "email-addresses-and-address-books", + "New-AddressList": "email-addresses-and-address-books", + "New-EmailAddressPolicy": "email-addresses-and-address-books", + "New-GlobalAddressList": "email-addresses-and-address-books", + "New-OabVirtualDirectory": "email-addresses-and-address-books", + "New-OfflineAddressBook": "email-addresses-and-address-books", + "Remove-AddressBookPolicy": "email-addresses-and-address-books", + "Remove-AddressList": "email-addresses-and-address-books", + "Remove-EmailAddressPolicy": "email-addresses-and-address-books", + "Remove-GlobalAddressList": "email-addresses-and-address-books", + "Remove-OabVirtualDirectory": "email-addresses-and-address-books", + "Remove-OfflineAddressBook": "email-addresses-and-address-books", + "Restore-DetailsTemplate": "email-addresses-and-address-books", + "Set-AddressBookPolicy": "email-addresses-and-address-books", + "Set-AddressList": "email-addresses-and-address-books", + "Set-DetailsTemplate": "email-addresses-and-address-books", + "Set-EmailAddressPolicy": "email-addresses-and-address-books", + "Set-GlobalAddressList": "email-addresses-and-address-books", + "Set-OabVirtualDirectory": "email-addresses-and-address-books", + "Set-OfflineAddressBook": "email-addresses-and-address-books", + "Update-AddressList": "email-addresses-and-address-books", + "Update-EmailAddressPolicy": "email-addresses-and-address-books", + "Update-GlobalAddressList": "email-addresses-and-address-books", + "Update-OfflineAddressBook": "email-addresses-and-address-books", + "Enable-ExchangeCertificate": "encryption-and-certificates", + "Export-ExchangeCertificate": "encryption-and-certificates", + "Get-DataEncryptionPolicy": "encryption-and-certificates", + "Get-ExchangeCertificate": "encryption-and-certificates", + "Get-IRMConfiguration": "encryption-and-certificates", + "Get-M365DataAtRestEncryptionPolicy": "encryption-and-certificates", + "Get-M365DataAtRestEncryptionPolicyAssignment": "encryption-and-certificates", + "Get-MailboxIRMAccess": "encryption-and-certificates", + "Get-OMEConfiguration": "encryption-and-certificates", + "Get-OMEMessageStatus": "encryption-and-certificates", + "Get-RMSTemplate": "encryption-and-certificates", + "Get-SmimeConfig": "encryption-and-certificates", + "Import-ExchangeCertificate": "encryption-and-certificates", + "New-DataEncryptionPolicy": "encryption-and-certificates", + "New-ExchangeCertificate": "encryption-and-certificates", + "New-M365DataAtRestEncryptionPolicy": "encryption-and-certificates", + "New-OMEConfiguration": "encryption-and-certificates", + "Remove-ExchangeCertificate": "encryption-and-certificates", + "Remove-MailboxIRMAccess": "encryption-and-certificates", + "Remove-OMEConfiguration": "encryption-and-certificates", + "Set-DataEncryptionPolicy": "encryption-and-certificates", + "Set-IRMConfiguration": "encryption-and-certificates", + "Set-M365DataAtRestEncryptionPolicy": "encryption-and-certificates", + "Set-M365DataAtRestEncryptionPolicyAssignment": "encryption-and-certificates", + "Set-MailboxIRMAccess": "encryption-and-certificates", + "Set-OMEConfiguration": "encryption-and-certificates", + "Set-OMEMessageRevocation": "encryption-and-certificates", + "Set-RMSTemplate": "encryption-and-certificates", + "Set-SmimeConfig": "encryption-and-certificates", + "Test-IRMConfiguration": "encryption-and-certificates", + "Test-M365DataAtRestEncryptionPolicy": "encryption-and-certificates", + "Add-FederatedDomain": "federation-and-hybrid", + "Disable-RemoteMailbox": "federation-and-hybrid", + "Enable-RemoteMailbox": "federation-and-hybrid", + "Get-FederatedDomainProof": "federation-and-hybrid", + "Get-FederatedOrganizationIdentifier": "federation-and-hybrid", + "Get-FederationInformation": "federation-and-hybrid", + "Get-FederationTrust": "federation-and-hybrid", + "Get-HybridConfiguration": "federation-and-hybrid", + "Get-HybridMailflowDatacenterIPs": "federation-and-hybrid", + "Get-IntraOrganizationConfiguration": "federation-and-hybrid", + "Get-IntraOrganizationConnector": "federation-and-hybrid", + "Get-OnPremisesOrganization": "federation-and-hybrid", + "Get-PendingFederatedDomain": "federation-and-hybrid", + "Get-RemoteMailbox": "federation-and-hybrid", + "New-FederationTrust": "federation-and-hybrid", + "New-HybridConfiguration": "federation-and-hybrid", + "New-IntraOrganizationConnector": "federation-and-hybrid", + "New-OnPremisesOrganization": "federation-and-hybrid", + "New-RemoteMailbox": "federation-and-hybrid", + "Remove-FederatedDomain": "federation-and-hybrid", + "Remove-FederationTrust": "federation-and-hybrid", + "Remove-HybridConfiguration": "federation-and-hybrid", + "Remove-IntraOrganizationConnector": "federation-and-hybrid", + "Remove-OnPremisesOrganization": "federation-and-hybrid", + "Remove-RemoteMailbox": "federation-and-hybrid", + "Set-FederatedOrganizationIdentifier": "federation-and-hybrid", + "Set-FederationTrust": "federation-and-hybrid", + "Set-HybridConfiguration": "federation-and-hybrid", + "Set-IntraOrganizationConnector": "federation-and-hybrid", + "Set-OnPremisesOrganization": "federation-and-hybrid", + "Set-PendingFederatedDomain": "federation-and-hybrid", + "Set-RemoteMailbox": "federation-and-hybrid", + "Test-FederationTrust": "federation-and-hybrid", + "Test-FederationTrustCertificate": "federation-and-hybrid", + "Update-HybridConfiguration": "federation-and-hybrid", + "Update-Recipient": "federation-and-hybrid", + "Clean-MailboxDatabase": "mailbox-databases-and-servers", + "Disable-MailboxQuarantine": "mailbox-databases-and-servers", + "Disable-MetaCacheDatabase": "mailbox-databases-and-servers", + "Dismount-Database": "mailbox-databases-and-servers", + "Enable-MailboxQuarantine": "mailbox-databases-and-servers", + "Enable-MetaCacheDatabase": "mailbox-databases-and-servers", + "Get-FailedContentIndexDocuments": "mailbox-databases-and-servers", + "Get-MailboxDatabase": "mailbox-databases-and-servers", + "Get-MailboxRepairRequest": "mailbox-databases-and-servers", + "Get-MailboxServer": "mailbox-databases-and-servers", + "Get-SearchDocumentFormat": "mailbox-databases-and-servers", + "Get-StoreUsageStatistics": "mailbox-databases-and-servers", + "Mount-Database": "mailbox-databases-and-servers", + "Move-DatabasePath": "mailbox-databases-and-servers", + "New-MailboxDatabase": "mailbox-databases-and-servers", + "New-MailboxRepairRequest": "mailbox-databases-and-servers", + "New-SearchDocumentFormat": "mailbox-databases-and-servers", + "Remove-MailboxDatabase": "mailbox-databases-and-servers", + "Remove-MailboxRepairRequest": "mailbox-databases-and-servers", + "Remove-SearchDocumentFormat": "mailbox-databases-and-servers", + "Remove-StoreMailbox": "mailbox-databases-and-servers", + "Set-MailboxDatabase": "mailbox-databases-and-servers", + "Set-MailboxServer": "mailbox-databases-and-servers", + "Set-SearchDocumentFormat": "mailbox-databases-and-servers", + "Start-MailboxAssistant": "mailbox-databases-and-servers", + "Test-AssistantHealth": "mailbox-databases-and-servers", + "Test-ExchangeSearch": "mailbox-databases-and-servers", + "Test-MRSHealth": "mailbox-databases-and-servers", + "Update-DatabaseSchema": "mailbox-databases-and-servers", + "Update-FileDistributionService": "mailbox-databases-and-servers", + "Update-StoreMailboxState": "mailbox-databases-and-servers", + "Add-MailboxFolderPermission": "mailboxes", + "Add-MailboxPermission": "mailboxes", + "Add-RecipientPermission": "mailboxes", + "Connect-Mailbox": "mailboxes", + "Disable-App": "mailboxes", + "Disable-InboxRule": "mailboxes", + "Disable-Mailbox": "mailboxes", + "Disable-ServiceEmailChannel": "mailboxes", + "Disable-SweepRule": "mailboxes", + "Enable-App": "mailboxes", + "Enable-InboxRule": "mailboxes", + "Enable-Mailbox": "mailboxes", + "Enable-ServiceEmailChannel": "mailboxes", + "Enable-SweepRule": "mailboxes", + "Expedite-Delicensing": "mailboxes", + "Export-MailboxDiagnosticLogs": "mailboxes", + "Export-RecipientDataProperty": "mailboxes", + "Get-App": "mailboxes", + "Get-CalendarDiagnosticAnalysis": "mailboxes", + "Get-CalendarDiagnosticLog": "mailboxes", + "Get-CalendarDiagnosticObjects": "mailboxes", + "Get-CalendarNotification": "mailboxes", + "Get-CalendarProcessing": "mailboxes", + "Get-Clutter": "mailboxes", + "Get-EventsFromEmailConfiguration": "mailboxes", + "Get-ExternalInOutlook": "mailboxes", + "Get-FocusedInbox": "mailboxes", + "Get-InboxRule": "mailboxes", + "Get-Mailbox": "mailboxes", + "Get-MailboxAutoReplyConfiguration": "mailboxes", + "Get-MailboxCalendarFolder": "mailboxes", + "Get-MailboxExportRequest": "mailboxes", + "Get-MailboxExportRequestStatistics": "mailboxes", + "Get-MailboxFolder": "mailboxes", + "Get-MailboxFolderPermission": "mailboxes", + "Get-MailboxFolderStatistics": "mailboxes", + "Get-MailboxImportRequest": "mailboxes", + "Get-MailboxImportRequestStatistics": "mailboxes", + "Get-MailboxLocation": "mailboxes", + "Get-MailboxPermission": "mailboxes", + "Get-MailboxPlan": "mailboxes", + "Get-MailboxRestoreRequest": "mailboxes", + "Get-MailboxRestoreRequestStatistics": "mailboxes", + "Get-MailboxSentItemsConfiguration": "mailboxes", + "Get-MailboxStatistics": "mailboxes", + "Get-MailboxUserConfiguration": "mailboxes", + "Get-MessageCategory": "mailboxes", + "Get-PendingDelicenseUser": "mailboxes", + "Get-Place": "mailboxes", + "Get-RecipientPermission": "mailboxes", + "Get-RecoverableItems": "mailboxes", + "Get-ResourceConfig": "mailboxes", + "Get-SweepRule": "mailboxes", + "Get-UserPhoto": "mailboxes", + "Import-RecipientDataProperty": "mailboxes", + "New-App": "mailboxes", + "New-InboxRule": "mailboxes", + "New-Mailbox": "mailboxes", + "New-MailboxExportRequest": "mailboxes", + "New-MailboxFolder": "mailboxes", + "New-MailboxImportRequest": "mailboxes", + "New-MailboxRestoreRequest": "mailboxes", + "New-MailMessage": "mailboxes", + "New-SiteMailbox": "mailboxes", + "New-SweepRule": "mailboxes", + "Remove-App": "mailboxes", + "Remove-CalendarEvents": "mailboxes", + "Remove-InboxRule": "mailboxes", + "Remove-Mailbox": "mailboxes", + "Remove-MailboxExportRequest": "mailboxes", + "Remove-MailboxFolderPermission": "mailboxes", + "Remove-MailboxImportRequest": "mailboxes", + "Remove-MailboxPermission": "mailboxes", + "Remove-MailboxRestoreRequest": "mailboxes", + "Remove-MailboxUserConfiguration": "mailboxes", + "Remove-RecipientPermission": "mailboxes", + "Remove-SweepRule": "mailboxes", + "Remove-UserPhoto": "mailboxes", + "Restore-Mailbox": "mailboxes", + "Restore-RecoverableItems": "mailboxes", + "Resume-MailboxExportRequest": "mailboxes", + "Resume-MailboxImportRequest": "mailboxes", + "Resume-MailboxRestoreRequest": "mailboxes", + "Search-Mailbox": "mailboxes", + "Set-App": "mailboxes", + "Set-CalendarNotification": "mailboxes", + "Set-CalendarProcessing": "mailboxes", + "Set-Clutter": "mailboxes", + "Set-EventsFromEmailConfiguration": "mailboxes", + "Set-ExternalInOutlook": "mailboxes", + "Set-FocusedInbox": "mailboxes", + "Set-InboxRule": "mailboxes", + "Set-Mailbox": "mailboxes", + "Set-MailboxAutoReplyConfiguration": "mailboxes", + "Set-MailboxCalendarFolder": "mailboxes", + "Set-MailboxExportRequest": "mailboxes", + "Set-MailboxFolderPermission": "mailboxes", + "Set-MailboxImportRequest": "mailboxes", + "Set-MailboxPlan": "mailboxes", + "Set-MailboxRestoreRequest": "mailboxes", + "Set-MailboxSentItemsConfiguration": "mailboxes", + "Set-Place": "mailboxes", + "Set-ResourceConfig": "mailboxes", + "Set-SweepRule": "mailboxes", + "Set-UserPhoto": "mailboxes", + "Suspend-MailboxExportRequest": "mailboxes", + "Suspend-MailboxImportRequest": "mailboxes", + "Suspend-MailboxRestoreRequest": "mailboxes", + "Test-MAPIConnectivity": "mailboxes", + "Undo-SoftDeletedMailbox": "mailboxes", + "Add-ResubmitRequest": "mail-flow", + "Disable-DnssecForVerifiedDomain": "mail-flow", + "Disable-IPv6ForAcceptedDomain": "mail-flow", + "Disable-SmtpDaneInbound": "mail-flow", + "Disable-TransportAgent": "mail-flow", + "Enable-DnssecForVerifiedDomain": "mail-flow", + "Enable-IPv6ForAcceptedDomain": "mail-flow", + "Enable-SmtpDaneInbound": "mail-flow", + "Enable-TransportAgent": "mail-flow", + "Export-Message": "mail-flow", + "Get-AcceptedDomain": "mail-flow", + "Get-AddressRewriteEntry": "mail-flow", + "Get-DeliveryAgentConnector": "mail-flow", + "Get-DnssecStatusForVerifiedDomain": "mail-flow", + "Get-EdgeSubscription": "mail-flow", + "Get-EdgeSyncServiceConfig": "mail-flow", + "Get-ForeignConnector": "mail-flow", + "Get-FrontendTransportService": "mail-flow", + "Get-InboundConnector": "mail-flow", + "Get-IPv6StatusForAcceptedDomain": "mail-flow", + "Get-MailboxTransportService": "mail-flow", + "Get-Message": "mail-flow", + "Get-MessageTrace": "mail-flow", + "Get-MessageTraceDetail": "mail-flow", + "Get-MessageTrackingLog": "mail-flow", + "Get-MessageTrackingReport": "mail-flow", + "Get-NetworkConnectionInfo": "mail-flow", + "Get-OutboundConnector": "mail-flow", + "Get-Queue": "mail-flow", + "Get-QueueDigest": "mail-flow", + "Get-ReceiveConnector": "mail-flow", + "Get-RemoteDomain": "mail-flow", + "Get-ResubmitRequest": "mail-flow", + "Get-RoutingGroupConnector": "mail-flow", + "Get-SendConnector": "mail-flow", + "Get-SmtpDaneInboundStatus": "mail-flow", + "Get-SystemMessage": "mail-flow", + "Get-TransportAgent": "mail-flow", + "Get-TransportConfig": "mail-flow", + "Get-TransportPipeline": "mail-flow", + "Get-TransportServer": "mail-flow", + "Get-TransportService": "mail-flow", + "Get-X400AuthoritativeDomain": "mail-flow", + "Install-TransportAgent": "mail-flow", + "New-AcceptedDomain": "mail-flow", + "New-AddressRewriteEntry": "mail-flow", + "New-DeliveryAgentConnector": "mail-flow", + "New-EdgeSubscription": "mail-flow", + "New-EdgeSyncServiceConfig": "mail-flow", + "New-ForeignConnector": "mail-flow", + "New-InboundConnector": "mail-flow", + "New-OutboundConnector": "mail-flow", + "New-ReceiveConnector": "mail-flow", + "New-RemoteDomain": "mail-flow", + "New-RoutingGroupConnector": "mail-flow", + "New-SendConnector": "mail-flow", + "New-SystemMessage": "mail-flow", + "New-X400AuthoritativeDomain": "mail-flow", + "Redirect-Message": "mail-flow", + "Remove-AcceptedDomain": "mail-flow", + "Remove-AddressRewriteEntry": "mail-flow", + "Remove-DeliveryAgentConnector": "mail-flow", + "Remove-EdgeSubscription": "mail-flow", + "Remove-ForeignConnector": "mail-flow", + "Remove-InboundConnector": "mail-flow", + "Remove-Message": "mail-flow", + "Remove-OutboundConnector": "mail-flow", + "Remove-ReceiveConnector": "mail-flow", + "Remove-RemoteDomain": "mail-flow", + "Remove-ResubmitRequest": "mail-flow", + "Remove-RoutingGroupConnector": "mail-flow", + "Remove-SendConnector": "mail-flow", + "Remove-SystemMessage": "mail-flow", + "Remove-X400AuthoritativeDomain": "mail-flow", + "Resume-Message": "mail-flow", + "Resume-Queue": "mail-flow", + "Retry-Queue": "mail-flow", + "Search-MessageTrackingReport": "mail-flow", + "Set-AcceptedDomain": "mail-flow", + "Set-AddressRewriteEntry": "mail-flow", + "Set-DeliveryAgentConnector": "mail-flow", + "Set-EdgeSyncServiceConfig": "mail-flow", + "Set-ForeignConnector": "mail-flow", + "Set-FrontendTransportService": "mail-flow", + "Set-InboundConnector": "mail-flow", + "Set-MailboxTransportService": "mail-flow", + "Set-OutboundConnector": "mail-flow", + "Set-ReceiveConnector": "mail-flow", + "Set-RemoteDomain": "mail-flow", + "Set-ResubmitRequest": "mail-flow", + "Set-RoutingGroupConnector": "mail-flow", + "Set-SendConnector": "mail-flow", + "Set-SystemMessage": "mail-flow", + "Set-TransportAgent": "mail-flow", + "Set-TransportConfig": "mail-flow", + "Set-TransportServer": "mail-flow", + "Set-TransportService": "mail-flow", + "Set-X400AuthoritativeDomain": "mail-flow", + "Start-EdgeSynchronization": "mail-flow", + "Start-HistoricalSearch": "mail-flow", + "Stop-HistoricalSearch": "mail-flow", + "Suspend-Message": "mail-flow", + "Suspend-Queue": "mail-flow", + "Test-EdgeSynchronization": "mail-flow", + "Test-Mailflow": "mail-flow", + "Test-SmtpConnectivity": "mail-flow", + "Uninstall-TransportAgent": "mail-flow", + "Validate-OutboundConnector": "mail-flow", + "Complete-MigrationBatch": "move-and-migration", + "Export-MigrationReport": "move-and-migration", + "Get-MigrationBatch": "move-and-migration", + "Get-MigrationConfig": "move-and-migration", + "Get-MigrationEndpoint": "move-and-migration", + "Get-MigrationStatistics": "move-and-migration", + "Get-MigrationUser": "move-and-migration", + "Get-MigrationUserStatistics": "move-and-migration", + "Get-MoveRequest": "move-and-migration", + "Get-MoveRequestStatistics": "move-and-migration", + "Get-PublicFolderMailboxMigrationRequest": "move-and-migration", + "Get-PublicFolderMailboxMigrationRequestStatistics": "move-and-migration", + "Get-PublicFolderMigrationRequest": "move-and-migration", + "Get-PublicFolderMigrationRequestStatistics": "move-and-migration", + "Get-PublicFolderMoveRequest": "move-and-migration", + "Get-PublicFolderMoveRequestStatistics": "move-and-migration", + "New-MigrationBatch": "move-and-migration", + "New-MigrationEndpoint": "move-and-migration", + "New-MoveRequest": "move-and-migration", + "New-PublicFolderMigrationRequest": "move-and-migration", + "New-PublicFolderMoveRequest": "move-and-migration", + "Remove-MigrationBatch": "move-and-migration", + "Remove-MigrationEndpoint": "move-and-migration", + "Remove-MigrationUser": "move-and-migration", + "Remove-MoveRequest": "move-and-migration", + "Remove-PublicFolderMailboxMigrationRequest": "move-and-migration", + "Remove-PublicFolderMigrationRequest": "move-and-migration", + "Remove-PublicFolderMoveRequest": "move-and-migration", + "Resume-MoveRequest": "move-and-migration", + "Resume-PublicFolderMigrationRequest": "move-and-migration", + "Resume-PublicFolderMoveRequest": "move-and-migration", + "Set-MigrationBatch": "move-and-migration", + "Set-MigrationConfig": "move-and-migration", + "Set-MigrationEndpoint": "move-and-migration", + "Set-MigrationUser": "move-and-migration", + "Set-MoveRequest": "move-and-migration", + "Set-PublicFolderMigrationRequest": "move-and-migration", + "Set-PublicFolderMoveRequest": "move-and-migration", + "Start-MigrationBatch": "move-and-migration", + "Start-MigrationUser": "move-and-migration", + "Stop-MigrationBatch": "move-and-migration", + "Stop-MigrationUser": "move-and-migration", + "Suspend-MoveRequest": "move-and-migration", + "Suspend-PublicFolderMailboxMigrationRequest": "move-and-migration", + "Suspend-PublicFolderMigrationRequest": "move-and-migration", + "Suspend-PublicFolderMoveRequest": "move-and-migration", + "Test-MigrationServerAvailability": "move-and-migration", + "Disable-CmdletExtensionAgent": "organization", + "Enable-CmdletExtensionAgent": "organization", + "Enable-OrganizationCustomization": "organization", + "Get-AccessToCustomerDataRequest": "organization", + "Get-ApplicationAccessPolicy": "organization", + "Get-AuthConfig": "organization", + "Get-AuthenticationPolicy": "organization", + "Get-AuthServer": "organization", + "Get-CmdletExtensionAgent": "organization", + "Get-ExchangeAssistanceConfig": "organization", + "Get-ExchangeDiagnosticInfo": "organization", + "Get-ExchangeFeature": "organization", + "Get-ExchangeServer": "organization", + "Get-ExchangeServerAccessLicense": "organization", + "Get-ExchangeServerAccessLicenseUser": "organization", + "Get-ExchangeSettings": "organization", + "Get-FeatureConfiguration": "organization", + "Get-Notification": "organization", + "Get-OrganizationConfig": "organization", + "Get-PartnerApplication": "organization", + "Get-PerimeterConfig": "organization", + "Get-ServicePrincipal": "organization", + "Get-SettingOverride": "organization", + "New-ApplicationAccessPolicy": "organization", + "New-AuthenticationPolicy": "organization", + "New-AuthServer": "organization", + "New-ExchangeSettings": "organization", + "New-FeatureConfiguration": "organization", + "New-PartnerApplication": "organization", + "New-ServicePrincipal": "organization", + "New-SettingOverride": "organization", + "Remove-ApplicationAccessPolicy": "organization", + "Remove-AuthenticationPolicy": "organization", + "Remove-AuthServer": "organization", + "Remove-FeatureConfiguration": "organization", + "Remove-PartnerApplication": "organization", + "Remove-ServicePrincipal": "organization", + "Remove-SettingOverride": "organization", + "Set-AccessToCustomerDataRequest": "organization", + "Set-ApplicationAccessPolicy": "organization", + "Set-AuthConfig": "organization", + "Set-AuthenticationPolicy": "organization", + "Set-AuthServer": "organization", + "Set-CmdletExtensionAgent": "organization", + "Set-ExchangeAssistanceConfig": "organization", + "Set-ExchangeFeature": "organization", + "Set-ExchangeServer": "organization", + "Set-ExchangeSettings": "organization", + "Set-FeatureConfiguration": "organization", + "Set-Notification": "organization", + "Set-OrganizationConfig": "organization", + "Set-PartnerApplication": "organization", + "Set-PerimeterConfig": "organization", + "Set-ServicePrincipal": "organization", + "Set-SettingOverride": "organization", + "Test-ApplicationAccessPolicy": "organization", + "Test-OAuthConnectivity": "organization", + "Test-ServicePrincipalAuthorization": "organization", + "Test-SystemHealth": "organization", + "Update-ExchangeHelp": "organization", + "Disable-JournalArchiving": "policy-and-compliance", + "Disable-JournalRule": "policy-and-compliance", + "Disable-OutlookProtectionRule": "policy-and-compliance", + "Disable-TransportRule": "policy-and-compliance", + "Enable-JournalRule": "policy-and-compliance", + "Enable-OutlookProtectionRule": "policy-and-compliance", + "Enable-TransportRule": "policy-and-compliance", + "Execute-AzureADLabelSync": "policy-and-compliance", + "Export-JournalRuleCollection": "policy-and-compliance", + "Export-TransportRuleCollection": "policy-and-compliance", + "Get-AdministrativeUnit": "policy-and-compliance", + "Get-AutoSensitivityLabelPolicy": "policy-and-compliance", + "Get-AutoSensitivityLabelRule": "policy-and-compliance", + "Get-EtrLimits": "policy-and-compliance", + "Get-ExoInformationBarrierPolicy": "policy-and-compliance", + "Get-ExoInformationBarrierRelationship": "policy-and-compliance", + "Get-ExoInformationBarrierSegment": "policy-and-compliance", + "Get-InformationBarrierPoliciesApplicationStatus": "policy-and-compliance", + "Get-InformationBarrierPolicy": "policy-and-compliance", + "Get-InformationBarrierRecipientStatus": "policy-and-compliance", + "Get-JournalRule": "policy-and-compliance", + "Get-Label": "policy-and-compliance", + "Get-LabelPolicy": "policy-and-compliance", + "Get-MessageClassification": "policy-and-compliance", + "Get-OrganizationSegment": "policy-and-compliance", + "Get-OutlookProtectionRule": "policy-and-compliance", + "Get-ProtectionAlert": "policy-and-compliance", + "Get-ReviewItems": "policy-and-compliance", + "Get-SupervisoryReviewPolicyV2": "policy-and-compliance", + "Get-SupervisoryReviewRule": "policy-and-compliance", + "Get-TransportRule": "policy-and-compliance", + "Get-TransportRuleAction": "policy-and-compliance", + "Get-TransportRulePredicate": "policy-and-compliance", + "Import-JournalRuleCollection": "policy-and-compliance", + "Import-TransportRuleCollection": "policy-and-compliance", + "Install-UnifiedCompliancePrerequisite": "policy-and-compliance", + "Invoke-ComplianceSecurityFilterAction": "policy-and-compliance", + "New-AutoSensitivityLabelPolicy": "policy-and-compliance", + "New-AutoSensitivityLabelRule": "policy-and-compliance", + "New-InformationBarrierPolicy": "policy-and-compliance", + "New-JournalRule": "policy-and-compliance", + "New-Label": "policy-and-compliance", + "New-LabelPolicy": "policy-and-compliance", + "New-MessageClassification": "policy-and-compliance", + "New-OrganizationSegment": "policy-and-compliance", + "New-OutlookProtectionRule": "policy-and-compliance", + "New-ProtectionAlert": "policy-and-compliance", + "New-SupervisoryReviewPolicyV2": "policy-and-compliance", + "New-SupervisoryReviewRule": "policy-and-compliance", + "New-TransportRule": "policy-and-compliance", + "Remove-AutoSensitivityLabelPolicy": "policy-and-compliance", + "Remove-AutoSensitivityLabelRule": "policy-and-compliance", + "Remove-InformationBarrierPolicy": "policy-and-compliance", + "Remove-JournalRule": "policy-and-compliance", + "Remove-Label": "policy-and-compliance", + "Remove-LabelPolicy": "policy-and-compliance", + "Remove-MessageClassification": "policy-and-compliance", + "Remove-OrganizationSegment": "policy-and-compliance", + "Remove-OutlookProtectionRule": "policy-and-compliance", + "Remove-ProtectionAlert": "policy-and-compliance", + "Remove-SupervisoryReviewPolicyV2": "policy-and-compliance", + "Remove-TransportRule": "policy-and-compliance", + "Set-AutoSensitivityLabelPolicy": "policy-and-compliance", + "Set-AutoSensitivityLabelRule": "policy-and-compliance", + "Set-InformationBarrierPolicy": "policy-and-compliance", + "Set-JournalRule": "policy-and-compliance", + "Set-Label": "policy-and-compliance", + "Set-LabelPolicy": "policy-and-compliance", + "Set-MessageClassification": "policy-and-compliance", + "Set-OrganizationSegment": "policy-and-compliance", + "Set-OutlookProtectionRule": "policy-and-compliance", + "Set-ProtectionAlert": "policy-and-compliance", + "Set-SupervisoryReviewPolicyV2": "policy-and-compliance", + "Set-SupervisoryReviewRule": "policy-and-compliance", + "Set-TransportRule": "policy-and-compliance", + "Start-InformationBarrierPoliciesApplication": "policy-and-compliance", + "Stop-InformationBarrierPoliciesApplication": "policy-and-compliance", + "Test-ArchiveConnectivity": "policy-and-compliance", + "Get-AdminAuditLogConfig": "policy-and-compliance-audit", + "Get-AuditConfig": "policy-and-compliance-audit", + "Get-AuditLogSearch": "policy-and-compliance-audit", + "Get-MailboxAuditBypassAssociation": "policy-and-compliance-audit", + "Get-UnifiedAuditLogRetentionPolicy": "policy-and-compliance-audit", + "New-AdminAuditLogSearch": "policy-and-compliance-audit", + "New-MailboxAuditLogSearch": "policy-and-compliance-audit", + "New-UnifiedAuditLogRetentionPolicy": "policy-and-compliance-audit", + "Remove-UnifiedAuditLogRetentionPolicy": "policy-and-compliance-audit", + "Search-AdminAuditLog": "policy-and-compliance-audit", + "Search-MailboxAuditLog": "policy-and-compliance-audit", + "Search-UnifiedAuditLog": "policy-and-compliance-audit", + "Set-AdminAuditLogConfig": "policy-and-compliance-audit", + "Set-AuditConfig": "policy-and-compliance-audit", + "Set-MailboxAuditBypassAssociation": "policy-and-compliance-audit", + "Set-UnifiedAuditLogRetentionPolicy": "policy-and-compliance-audit", + "Write-AdminAuditLog": "policy-and-compliance-audit", + "Get-ComplianceSearch": "policy-and-compliance-content-search", + "Get-ComplianceSearchAction": "policy-and-compliance-content-search", + "Get-ComplianceSecurityFilter": "policy-and-compliance-content-search", + "Get-MailboxSearch": "policy-and-compliance-content-search", + "Invoke-ComplianceSearchActionStep": "policy-and-compliance-content-search", + "New-ComplianceSearch": "policy-and-compliance-content-search", + "New-ComplianceSearchAction": "policy-and-compliance-content-search", + "New-ComplianceSecurityFilter": "policy-and-compliance-content-search", + "New-MailboxSearch": "policy-and-compliance-content-search", + "Remove-ComplianceSearch": "policy-and-compliance-content-search", + "Remove-ComplianceSearchAction": "policy-and-compliance-content-search", + "Remove-ComplianceSecurityFilter": "policy-and-compliance-content-search", + "Remove-MailboxSearch": "policy-and-compliance-content-search", + "Set-ComplianceSearch": "policy-and-compliance-content-search", + "Set-ComplianceSearchAction": "policy-and-compliance-content-search", + "Set-ComplianceSecurityFilter": "policy-and-compliance-content-search", + "Set-MailboxSearch": "policy-and-compliance-content-search", + "Start-ComplianceSearch": "policy-and-compliance-content-search", + "Start-MailboxSearch": "policy-and-compliance-content-search", + "Stop-ComplianceSearch": "policy-and-compliance-content-search", + "Stop-MailboxSearch": "policy-and-compliance-content-search", + "Export-ActivityExplorerData": "policy-and-compliance-dlp", + "Export-DlpPolicyCollection": "policy-and-compliance-dlp", + "Get-ClassificationRuleCollection": "policy-and-compliance-dlp", + "Get-DataClassification": "policy-and-compliance-dlp", + "Get-DataClassificationConfig": "policy-and-compliance-dlp", + "Get-DlpCompliancePolicy": "policy-and-compliance-dlp", + "Get-DlpComplianceRule": "policy-and-compliance-dlp", + "Get-DlpDetailReport": "policy-and-compliance-dlp", + "Get-DlpDetectionsReport": "policy-and-compliance-dlp", + "Get-DlpEdmSchema": "policy-and-compliance-dlp", + "Get-DlpIncidentDetailReport": "policy-and-compliance-dlp", + "Get-DlpKeywordDictionary": "policy-and-compliance-dlp", + "Get-DlpPolicy": "policy-and-compliance-dlp", + "Get-DlpPolicyTemplate": "policy-and-compliance-dlp", + "Get-DlpSensitiveInformationType": "policy-and-compliance-dlp", + "Get-DlpSensitiveInformationTypeRulePackage": "policy-and-compliance-dlp", + "Get-DlpSiDetectionsReport": "policy-and-compliance-dlp", + "Get-PolicyConfig": "policy-and-compliance-dlp", + "Get-PolicyTipConfig": "policy-and-compliance-dlp", + "Import-DlpPolicyCollection": "policy-and-compliance-dlp", + "Import-DlpPolicyTemplate": "policy-and-compliance-dlp", + "New-ClassificationRuleCollection": "policy-and-compliance-dlp", + "New-DataClassification": "policy-and-compliance-dlp", + "New-DlpCompliancePolicy": "policy-and-compliance-dlp", + "New-DlpComplianceRule": "policy-and-compliance-dlp", + "New-DlpComplianceRuleV2": "policy-and-compliance-dlp", + "New-DlpEdmSchema": "policy-and-compliance-dlp", + "New-DlpFingerprint": "policy-and-compliance-dlp", + "New-DlpKeywordDictionary": "policy-and-compliance-dlp", + "New-DlpPolicy": "policy-and-compliance-dlp", + "New-DlpSensitiveInformationType": "policy-and-compliance-dlp", + "New-DlpSensitiveInformationTypeRulePackage": "policy-and-compliance-dlp", + "New-Fingerprint": "policy-and-compliance-dlp", + "New-PolicyTipConfig": "policy-and-compliance-dlp", + "Remove-ClassificationRuleCollection": "policy-and-compliance-dlp", + "Remove-DataClassification": "policy-and-compliance-dlp", + "Remove-DlpCompliancePolicy": "policy-and-compliance-dlp", + "Remove-DlpComplianceRule": "policy-and-compliance-dlp", + "Remove-DlpEdmSchema": "policy-and-compliance-dlp", + "Remove-DlpKeywordDictionary": "policy-and-compliance-dlp", + "Remove-DlpPolicy": "policy-and-compliance-dlp", + "Remove-DlpPolicyTemplate": "policy-and-compliance-dlp", + "Remove-DlpSensitiveInformationType": "policy-and-compliance-dlp", + "Remove-DlpSensitiveInformationTypeRulePackage": "policy-and-compliance-dlp", + "Remove-PolicyTipConfig": "policy-and-compliance-dlp", + "Set-ClassificationRuleCollection": "policy-and-compliance-dlp", + "Set-DataClassification": "policy-and-compliance-dlp", + "Set-DlpCompliancePolicy": "policy-and-compliance-dlp", + "Set-DlpComplianceRule": "policy-and-compliance-dlp", + "Set-DlpEdmSchema": "policy-and-compliance-dlp", + "Set-DlpKeywordDictionary": "policy-and-compliance-dlp", + "Set-DlpPolicy": "policy-and-compliance-dlp", + "Set-DlpSensitiveInformationType": "policy-and-compliance-dlp", + "Set-DlpSensitiveInformationTypeRulePackage": "policy-and-compliance-dlp", + "Set-PolicyConfig": "policy-and-compliance-dlp", + "Set-PolicyTipConfig": "policy-and-compliance-dlp", + "Test-DataClassification": "policy-and-compliance-dlp", + "Test-TextExtraction": "policy-and-compliance-dlp", + "Add-ComplianceCaseMember": "policy-and-compliance-ediscovery", + "Add-eDiscoveryCaseAdmin": "policy-and-compliance-ediscovery", + "Get-CaseHoldPolicy": "policy-and-compliance-ediscovery", + "Get-CaseHoldRule": "policy-and-compliance-ediscovery", + "Get-ComplianceCase": "policy-and-compliance-ediscovery", + "Get-ComplianceCaseMember": "policy-and-compliance-ediscovery", + "Get-eDiscoveryCaseAdmin": "policy-and-compliance-ediscovery", + "New-CaseHoldPolicy": "policy-and-compliance-ediscovery", + "New-CaseHoldRule": "policy-and-compliance-ediscovery", + "New-ComplianceCase": "policy-and-compliance-ediscovery", + "Remove-CaseHoldPolicy": "policy-and-compliance-ediscovery", + "Remove-CaseHoldRule": "policy-and-compliance-ediscovery", + "Remove-ComplianceCase": "policy-and-compliance-ediscovery", + "Remove-ComplianceCaseMember": "policy-and-compliance-ediscovery", + "Remove-eDiscoveryCaseAdmin": "policy-and-compliance-ediscovery", + "Set-CaseHoldPolicy": "policy-and-compliance-ediscovery", + "Set-CaseHoldRule": "policy-and-compliance-ediscovery", + "Set-ComplianceCase": "policy-and-compliance-ediscovery", + "Update-ComplianceCaseMember": "policy-and-compliance-ediscovery", + "Update-eDiscoveryCaseAdmin": "policy-and-compliance-ediscovery", + "Enable-ComplianceTagStorage": "policy-and-compliance-retention", + "Export-ContentExplorerData": "policy-and-compliance-retention", + "Export-FilePlanProperty": "policy-and-compliance-retention", + "Get-AdaptiveScope": "policy-and-compliance-retention", + "Get-AppRetentionCompliancePolicy": "policy-and-compliance-retention", + "Get-AppRetentionComplianceRule": "policy-and-compliance-retention", + "Get-ComplianceRetentionEvent": "policy-and-compliance-retention", + "Get-ComplianceRetentionEventType": "policy-and-compliance-retention", + "Get-ComplianceTag": "policy-and-compliance-retention", + "Get-ComplianceTagStorage": "policy-and-compliance-retention", + "Get-DataRetentionReport": "policy-and-compliance-retention", + "Get-FilePlanPropertyAuthority": "policy-and-compliance-retention", + "Get-FilePlanPropertyCategory": "policy-and-compliance-retention", + "Get-FilePlanPropertyCitation": "policy-and-compliance-retention", + "Get-FilePlanPropertyDepartment": "policy-and-compliance-retention", + "Get-FilePlanPropertyReferenceId": "policy-and-compliance-retention", + "Get-FilePlanPropertyStructure": "policy-and-compliance-retention", + "Get-FilePlanPropertySubCategory": "policy-and-compliance-retention", + "Get-HoldCompliancePolicy": "policy-and-compliance-retention", + "Get-HoldComplianceRule": "policy-and-compliance-retention", + "Get-ManagedContentSettings": "policy-and-compliance-retention", + "Get-ManagedFolder": "policy-and-compliance-retention", + "Get-ManagedFolderMailboxPolicy": "policy-and-compliance-retention", + "Get-RecordReviewNotificationTemplateConfig": "policy-and-compliance-retention", + "Get-RegulatoryComplianceUI": "policy-and-compliance-retention", + "Get-RetentionCompliancePolicy": "policy-and-compliance-retention", + "Get-RetentionComplianceRule": "policy-and-compliance-retention", + "Get-RetentionEvent": "policy-and-compliance-retention", + "Get-RetentionPolicy": "policy-and-compliance-retention", + "Get-RetentionPolicyTag": "policy-and-compliance-retention", + "Import-FilePlanProperty": "policy-and-compliance-retention", + "Invoke-HoldRemovalAction": "policy-and-compliance-retention", + "New-AdaptiveScope": "policy-and-compliance-retention", + "New-AppRetentionCompliancePolicy": "policy-and-compliance-retention", + "New-AppRetentionComplianceRule": "policy-and-compliance-retention", + "New-ComplianceRetentionEvent": "policy-and-compliance-retention", + "New-ComplianceRetentionEventType": "policy-and-compliance-retention", + "New-ComplianceTag": "policy-and-compliance-retention", + "New-FilePlanPropertyAuthority": "policy-and-compliance-retention", + "New-FilePlanPropertyCategory": "policy-and-compliance-retention", + "New-FilePlanPropertyCitation": "policy-and-compliance-retention", + "New-FilePlanPropertyDepartment": "policy-and-compliance-retention", + "New-FilePlanPropertyReferenceId": "policy-and-compliance-retention", + "New-FilePlanPropertySubCategory": "policy-and-compliance-retention", + "New-HoldCompliancePolicy": "policy-and-compliance-retention", + "New-HoldComplianceRule": "policy-and-compliance-retention", + "New-ManagedContentSettings": "policy-and-compliance-retention", + "New-ManagedFolder": "policy-and-compliance-retention", + "New-ManagedFolderMailboxPolicy": "policy-and-compliance-retention", + "New-RetentionCompliancePolicy": "policy-and-compliance-retention", + "New-RetentionComplianceRule": "policy-and-compliance-retention", + "New-RetentionPolicy": "policy-and-compliance-retention", + "New-RetentionPolicyTag": "policy-and-compliance-retention", + "Remove-AdaptiveScope": "policy-and-compliance-retention", + "Remove-AppRetentionCompliancePolicy": "policy-and-compliance-retention", + "Remove-AppRetentionComplianceRule": "policy-and-compliance-retention", + "Remove-ComplianceRetentionEventType": "policy-and-compliance-retention", + "Remove-ComplianceTag": "policy-and-compliance-retention", + "Remove-FilePlanPropertyAuthority": "policy-and-compliance-retention", + "Remove-FilePlanPropertyCategory": "policy-and-compliance-retention", + "Remove-FilePlanPropertyCitation": "policy-and-compliance-retention", + "Remove-FilePlanPropertyDepartment": "policy-and-compliance-retention", + "Remove-FilePlanPropertyReferenceId": "policy-and-compliance-retention", + "Remove-FilePlanPropertySubCategory": "policy-and-compliance-retention", + "Remove-HoldCompliancePolicy": "policy-and-compliance-retention", + "Remove-HoldComplianceRule": "policy-and-compliance-retention", + "Remove-ManagedContentSettings": "policy-and-compliance-retention", + "Remove-ManagedFolder": "policy-and-compliance-retention", + "Remove-ManagedFolderMailboxPolicy": "policy-and-compliance-retention", + "Remove-RetentionCompliancePolicy": "policy-and-compliance-retention", + "Remove-RetentionComplianceRule": "policy-and-compliance-retention", + "Remove-RetentionPolicy": "policy-and-compliance-retention", + "Remove-RetentionPolicyTag": "policy-and-compliance-retention", + "Set-AdaptiveScope": "policy-and-compliance-retention", + "Set-AppRetentionCompliancePolicy": "policy-and-compliance-retention", + "Set-AppRetentionComplianceRule": "policy-and-compliance-retention", + "Set-ComplianceRetentionEventType": "policy-and-compliance-retention", + "Set-ComplianceTag": "policy-and-compliance-retention", + "Set-FilePlanPropertyAuthority": "policy-and-compliance-retention", + "Set-FilePlanPropertyCategory": "policy-and-compliance-retention", + "Set-FilePlanPropertyCitation": "policy-and-compliance-retention", + "Set-FilePlanPropertyDepartment": "policy-and-compliance-retention", + "Set-FilePlanPropertyReferenceId": "policy-and-compliance-retention", + "Set-FilePlanPropertySubCategory": "policy-and-compliance-retention", + "Set-HoldCompliancePolicy": "policy-and-compliance-retention", + "Set-HoldComplianceRule": "policy-and-compliance-retention", + "Set-ManagedContentSettings": "policy-and-compliance-retention", + "Set-ManagedFolder": "policy-and-compliance-retention", + "Set-ManagedFolderMailboxPolicy": "policy-and-compliance-retention", + "Set-RecordReviewNotificationTemplateConfig": "policy-and-compliance-retention", + "Set-RegulatoryComplianceUI": "policy-and-compliance-retention", + "Set-RetentionCompliancePolicy": "policy-and-compliance-retention", + "Set-RetentionComplianceRule": "policy-and-compliance-retention", + "Set-RetentionPolicy": "policy-and-compliance-retention", + "Set-RetentionPolicyTag": "policy-and-compliance-retention", + "Start-ManagedFolderAssistant": "policy-and-compliance-retention", + "Start-RetentionAutoTagLearning": "policy-and-compliance-retention", + "Stop-ManagedFolderAssistant": "policy-and-compliance-retention", + "Validate-RetentionRuleQuery": "policy-and-compliance-retention", + "Add-VivaModuleFeaturePolicy": "powershell-v3-module", + "Add-VivaOrgInsightsDelegatedRole": "powershell-v3-module", + "Connect-ExchangeOnline": "powershell-v3-module", + "Connect-IPPSSession": "powershell-v3-module", + "Disconnect-ExchangeOnline": "powershell-v3-module", + "Get-ConnectionInformation": "powershell-v3-module", + "Get-DefaultTenantBriefingConfig": "powershell-v3-module", + "Get-DefaultTenantMyAnalyticsFeatureConfig": "powershell-v3-module", + "Get-EXOCasMailbox": "powershell-v3-module", + "Get-EXOMailbox": "powershell-v3-module", + "Get-EXOMailboxFolderPermission": "powershell-v3-module", + "Get-EXOMailboxFolderStatistics": "powershell-v3-module", + "Get-EXOMailboxPermission": "powershell-v3-module", + "Get-EXOMailboxStatistics": "powershell-v3-module", + "Get-EXOMobileDeviceStatistics": "powershell-v3-module", + "Get-EXORecipient": "powershell-v3-module", + "Get-EXORecipientPermission": "powershell-v3-module", + "Get-MyAnalyticsFeatureConfig": "powershell-v3-module", + "Get-UserBriefingConfig": "powershell-v3-module", + "Get-VivaInsightsSettings": "powershell-v3-module", + "Get-VivaModuleFeature": "powershell-v3-module", + "Get-VivaModuleFeatureEnablement": "powershell-v3-module", + "Get-VivaModuleFeaturePolicy": "powershell-v3-module", + "Get-VivaOrgInsightsDelegatedRole": "powershell-v3-module", + "Remove-VivaModuleFeaturePolicy": "powershell-v3-module", + "Remove-VivaOrgInsightsDelegatedRole": "powershell-v3-module", + "Set-DefaultTenantBriefingConfig": "powershell-v3-module", + "Set-DefaultTenantMyAnalyticsFeatureConfig": "powershell-v3-module", + "Set-MyAnalyticsFeatureConfig": "powershell-v3-module", + "Set-UserBriefingConfig": "powershell-v3-module", + "Set-VivaInsightsSettings": "powershell-v3-module", + "Update-VivaModuleFeaturePolicy": "powershell-v3-module", + "Get-CompromisedUserAggregateReport": "reporting", + "Get-CompromisedUserDetailReport": "reporting", + "Get-HistoricalSearch": "reporting", + "Get-LogonStatistics": "reporting", + "Get-MailDetailDlpPolicyReport": "reporting", + "Get-MailDetailEncryptionReport": "reporting", + "Get-MailDetailTransportRuleReport": "reporting", + "Get-MailFilterListReport": "reporting", + "Get-MailflowStatusReport": "reporting", + "Get-MailTrafficEncryptionReport": "reporting", + "Get-MailTrafficPolicyReport": "reporting", + "Get-MailTrafficSummaryReport": "reporting", + "Get-MxRecordReport": "reporting", + "Get-OutboundConnectorReport": "reporting", + "Get-RecipientStatisticsReport": "reporting", + "Get-ReportExecutionInstance": "reporting", + "Get-SCInsights": "reporting", + "Get-ServiceDeliveryReport": "reporting", + "Get-SupervisoryReviewActivity": "reporting", + "Get-SupervisoryReviewOverallProgressReport": "reporting", + "Get-SupervisoryReviewPolicyReport": "reporting", + "Get-SupervisoryReviewReport": "reporting", + "Get-SupervisoryReviewTopCasesReport": "reporting", + "Test-Message": "reporting", + "Add-ManagementRoleEntry": "role-based-access-control", + "Add-RoleGroupMember": "role-based-access-control", + "Get-ManagementRole": "role-based-access-control", + "Get-ManagementRoleAssignment": "role-based-access-control", + "Get-ManagementRoleEntry": "role-based-access-control", + "Get-ManagementScope": "role-based-access-control", + "Get-RoleAssignmentPolicy": "role-based-access-control", + "Get-RoleGroup": "role-based-access-control", + "Get-RoleGroupMember": "role-based-access-control", + "New-ManagementRole": "role-based-access-control", + "New-ManagementRoleAssignment": "role-based-access-control", + "New-ManagementScope": "role-based-access-control", + "New-RoleAssignmentPolicy": "role-based-access-control", + "New-RoleGroup": "role-based-access-control", + "Remove-ManagementRole": "role-based-access-control", + "Remove-ManagementRoleAssignment": "role-based-access-control", + "Remove-ManagementRoleEntry": "role-based-access-control", + "Remove-ManagementScope": "role-based-access-control", + "Remove-RoleAssignmentPolicy": "role-based-access-control", + "Remove-RoleGroup": "role-based-access-control", + "Remove-RoleGroupMember": "role-based-access-control", + "Set-ManagementRoleAssignment": "role-based-access-control", + "Set-ManagementRoleEntry": "role-based-access-control", + "Set-ManagementScope": "role-based-access-control", + "Set-RoleAssignmentPolicy": "role-based-access-control", + "Set-RoleGroup": "role-based-access-control", + "Update-RoleGroupMember": "role-based-access-control", + "Add-GlobalMonitoringOverride": "server-health-and-performance", + "Add-ServerMonitoringOverride": "server-health-and-performance", + "Get-AvailabilityReportOutage": "server-health-and-performance", + "Get-EventLogLevel": "server-health-and-performance", + "Get-GlobalMonitoringOverride": "server-health-and-performance", + "Get-HealthReport": "server-health-and-performance", + "Get-MonitoringItemHelp": "server-health-and-performance", + "Get-MonitoringItemIdentity": "server-health-and-performance", + "Get-ServerComponentState": "server-health-and-performance", + "Get-ServerHealth": "server-health-and-performance", + "Get-ServerMonitoringOverride": "server-health-and-performance", + "Get-ThrottlingPolicy": "server-health-and-performance", + "Get-ThrottlingPolicyAssociation": "server-health-and-performance", + "Invoke-MonitoringProbe": "server-health-and-performance", + "New-AvailabilityReportOutage": "server-health-and-performance", + "New-ThrottlingPolicy": "server-health-and-performance", + "Remove-AvailabilityReportOutage": "server-health-and-performance", + "Remove-GlobalMonitoringOverride": "server-health-and-performance", + "Remove-ServerMonitoringOverride": "server-health-and-performance", + "Remove-ThrottlingPolicy": "server-health-and-performance", + "Set-AvailabilityReportOutage": "server-health-and-performance", + "Set-EventLogLevel": "server-health-and-performance", + "Set-ServerComponentState": "server-health-and-performance", + "Set-ServerMonitor": "server-health-and-performance", + "Set-ThrottlingPolicy": "server-health-and-performance", + "Set-ThrottlingPolicyAssociation": "server-health-and-performance", + "Test-ServiceHealth": "server-health-and-performance", + "Add-AvailabilityAddressSpace": "sharing-and-collaboration", + "Add-PublicFolderAdministrativePermission": "sharing-and-collaboration", + "Add-PublicFolderClientPermission": "sharing-and-collaboration", + "Disable-MailPublicFolder": "sharing-and-collaboration", + "Enable-MailPublicFolder": "sharing-and-collaboration", + "Get-AvailabilityAddressSpace": "sharing-and-collaboration", + "Get-AvailabilityConfig": "sharing-and-collaboration", + "Get-MailPublicFolder": "sharing-and-collaboration", + "Get-OrganizationRelationship": "sharing-and-collaboration", + "Get-PublicFolder": "sharing-and-collaboration", + "Get-PublicFolderAdministrativePermission": "sharing-and-collaboration", + "Get-PublicFolderClientPermission": "sharing-and-collaboration", + "Get-PublicFolderDatabase": "sharing-and-collaboration", + "Get-PublicFolderItemStatistics": "sharing-and-collaboration", + "Get-PublicFolderMailboxDiagnostics": "sharing-and-collaboration", + "Get-PublicFolderStatistics": "sharing-and-collaboration", + "Get-SharingPolicy": "sharing-and-collaboration", + "Get-SiteMailbox": "sharing-and-collaboration", + "Get-SiteMailboxDiagnostics": "sharing-and-collaboration", + "Get-SiteMailboxProvisioningPolicy": "sharing-and-collaboration", + "New-AvailabilityConfig": "sharing-and-collaboration", + "New-OrganizationRelationship": "sharing-and-collaboration", + "New-PublicFolder": "sharing-and-collaboration", + "New-PublicFolderDatabase": "sharing-and-collaboration", + "New-PublicFolderDatabaseRepairRequest": "sharing-and-collaboration", + "New-SharingPolicy": "sharing-and-collaboration", + "New-SiteMailboxProvisioningPolicy": "sharing-and-collaboration", + "New-SyncMailPublicFolder": "sharing-and-collaboration", + "Remove-AvailabilityAddressSpace": "sharing-and-collaboration", + "Remove-AvailabilityConfig": "sharing-and-collaboration", + "Remove-OrganizationRelationship": "sharing-and-collaboration", + "Remove-PublicFolder": "sharing-and-collaboration", + "Remove-PublicFolderAdministrativePermission": "sharing-and-collaboration", + "Remove-PublicFolderClientPermission": "sharing-and-collaboration", + "Remove-PublicFolderDatabase": "sharing-and-collaboration", + "Remove-SharingPolicy": "sharing-and-collaboration", + "Remove-SiteMailboxProvisioningPolicy": "sharing-and-collaboration", + "Remove-SyncMailPublicFolder": "sharing-and-collaboration", + "Resume-PublicFolderReplication": "sharing-and-collaboration", + "Set-AvailabilityConfig": "sharing-and-collaboration", + "Set-MailPublicFolder": "sharing-and-collaboration", + "Set-OrganizationRelationship": "sharing-and-collaboration", + "Set-PublicFolder": "sharing-and-collaboration", + "Set-PublicFolderDatabase": "sharing-and-collaboration", + "Set-SharingPolicy": "sharing-and-collaboration", + "Set-SiteMailbox": "sharing-and-collaboration", + "Set-SiteMailboxProvisioningPolicy": "sharing-and-collaboration", + "Suspend-PublicFolderReplication": "sharing-and-collaboration", + "Test-OrganizationRelationship": "sharing-and-collaboration", + "Test-SiteMailbox": "sharing-and-collaboration", + "Update-PublicFolder": "sharing-and-collaboration", + "Update-PublicFolderHierarchy": "sharing-and-collaboration", + "Update-PublicFolderMailbox": "sharing-and-collaboration", + "Update-SiteMailbox": "sharing-and-collaboration", + "Disable-UMAutoAttendant": "unified-messaging", + "Disable-UMCallAnsweringRule": "unified-messaging", + "Disable-UMIPGateway": "unified-messaging", + "Disable-UMMailbox": "unified-messaging", + "Disable-UMServer": "unified-messaging", + "Disable-UMService": "unified-messaging", + "Enable-UMAutoAttendant": "unified-messaging", + "Enable-UMCallAnsweringRule": "unified-messaging", + "Enable-UMIPGateway": "unified-messaging", + "Enable-UMMailbox": "unified-messaging", + "Enable-UMServer": "unified-messaging", + "Enable-UMService": "unified-messaging", + "Export-UMCallDataRecord": "unified-messaging", + "Export-UMPrompt": "unified-messaging", + "Get-OnlineMeetingConfiguration": "unified-messaging", + "Get-UMActiveCalls": "unified-messaging", + "Get-UMAutoAttendant": "unified-messaging", + "Get-UMCallAnsweringRule": "unified-messaging", + "Get-UMCallDataRecord": "unified-messaging", + "Get-UMCallRouterSettings": "unified-messaging", + "Get-UMCallSummaryReport": "unified-messaging", + "Get-UMDialPlan": "unified-messaging", + "Get-UMHuntGroup": "unified-messaging", + "Get-UMIPGateway": "unified-messaging", + "Get-UMMailbox": "unified-messaging", + "Get-UMMailboxPIN": "unified-messaging", + "Get-UMMailboxPolicy": "unified-messaging", + "Get-UmServer": "unified-messaging", + "Get-UMService": "unified-messaging", + "Import-UMPrompt": "unified-messaging", + "New-UMAutoAttendant": "unified-messaging", + "New-UMCallAnsweringRule": "unified-messaging", + "New-UMDialPlan": "unified-messaging", + "New-UMHuntGroup": "unified-messaging", + "New-UMIPGateway": "unified-messaging", + "New-UMMailboxPolicy": "unified-messaging", + "Remove-UMAutoAttendant": "unified-messaging", + "Remove-UMCallAnsweringRule": "unified-messaging", + "Remove-UMDialPlan": "unified-messaging", + "Remove-UMHuntGroup": "unified-messaging", + "Remove-UMIPGateway": "unified-messaging", + "Remove-UMMailboxPolicy": "unified-messaging", + "Set-UMAutoAttendant": "unified-messaging", + "Set-UMCallAnsweringRule": "unified-messaging", + "Set-UMCallRouterSettings": "unified-messaging", + "Set-UMDialPlan": "unified-messaging", + "Set-UMIPGateway": "unified-messaging", + "Set-UMMailbox": "unified-messaging", + "Set-UMMailboxPIN": "unified-messaging", + "Set-UMMailboxPolicy": "unified-messaging", + "Set-UmServer": "unified-messaging", + "Set-UMService": "unified-messaging", + "Test-UMConnectivity": "unified-messaging", + "Add-DistributionGroupMember": "users-and-groups", + "Add-UnifiedGroupLinks": "users-and-groups", + "Disable-DistributionGroup": "users-and-groups", + "Disable-MailContact": "users-and-groups", + "Disable-MailUser": "users-and-groups", + "Enable-DistributionGroup": "users-and-groups", + "Enable-MailContact": "users-and-groups", + "Enable-MailUser": "users-and-groups", + "Get-Contact": "users-and-groups", + "Get-DistributionGroup": "users-and-groups", + "Get-DistributionGroupMember": "users-and-groups", + "Get-DynamicDistributionGroup": "users-and-groups", + "Get-DynamicDistributionGroupMember": "users-and-groups", + "Get-EligibleDistributionGroupForMigration": "users-and-groups", + "Get-Group": "users-and-groups", + "Get-LinkedUser": "users-and-groups", + "Get-MailContact": "users-and-groups", + "Get-MailUser": "users-and-groups", + "Get-Recipient": "users-and-groups", + "Get-SecurityPrincipal": "users-and-groups", + "Get-UnifiedGroup": "users-and-groups", + "Get-UnifiedGroupLinks": "users-and-groups", + "Get-User": "users-and-groups", + "New-DistributionGroup": "users-and-groups", + "New-DynamicDistributionGroup": "users-and-groups", + "New-MailContact": "users-and-groups", + "New-MailUser": "users-and-groups", + "New-UnifiedGroup": "users-and-groups", + "Remove-DistributionGroup": "users-and-groups", + "Remove-DistributionGroupMember": "users-and-groups", + "Remove-DynamicDistributionGroup": "users-and-groups", + "Remove-MailContact": "users-and-groups", + "Remove-MailUser": "users-and-groups", + "Remove-UnifiedGroup": "users-and-groups", + "Remove-UnifiedGroupLinks": "users-and-groups", + "Set-Contact": "users-and-groups", + "Set-DistributionGroup": "users-and-groups", + "Set-DynamicDistributionGroup": "users-and-groups", + "Set-Group": "users-and-groups", + "Set-LinkedUser": "users-and-groups", + "Set-MailContact": "users-and-groups", + "Set-MailUser": "users-and-groups", + "Set-UnifiedGroup": "users-and-groups", + "Set-User": "users-and-groups", + "Undo-SoftDeletedUnifiedGroup": "users-and-groups", + "Update-DistributionGroupMember": "users-and-groups", + "Upgrade-DistributionGroup": "users-and-groups" +} \ No newline at end of file diff --git a/images/add_related_link.png b/images/add_related_link.png deleted file mode 100644 index 3f22beca8c..0000000000 Binary files a/images/add_related_link.png and /dev/null differ diff --git a/images/auto_fork.png b/images/auto_fork.png deleted file mode 100644 index 6d3b380625..0000000000 Binary files a/images/auto_fork.png and /dev/null differ diff --git a/images/contrib-consumption-model-orig.png b/images/contrib-consumption-model-orig.png deleted file mode 100644 index 7ac9b3d330..0000000000 Binary files a/images/contrib-consumption-model-orig.png and /dev/null differ diff --git a/images/contrib-consumption-model.png b/images/contrib-consumption-model.png deleted file mode 100644 index aab8501253..0000000000 Binary files a/images/contrib-consumption-model.png and /dev/null differ diff --git a/images/edit_icon.png b/images/edit_icon.png deleted file mode 100644 index bb87aa6e19..0000000000 Binary files a/images/edit_icon.png and /dev/null differ diff --git a/images/edit_video_capture.jpg b/images/edit_video_capture.jpg deleted file mode 100644 index b4caffa663..0000000000 Binary files a/images/edit_video_capture.jpg and /dev/null differ diff --git a/images/m365-cc-sc-edit-icon.png b/images/m365-cc-sc-edit-icon.png new file mode 100644 index 0000000000..46684dca7a Binary files /dev/null and b/images/m365-cc-sc-edit-icon.png differ diff --git a/images/open-a-pull-request-page.png b/images/open-a-pull-request-page.png new file mode 100644 index 0000000000..e61752e9fc Binary files /dev/null and b/images/open-a-pull-request-page.png differ diff --git a/images/propose-file-change.png b/images/propose-file-change.png new file mode 100644 index 0000000000..9b67cdea6e Binary files /dev/null and b/images/propose-file-change.png differ diff --git a/images/propose_file_change.png b/images/propose_file_change.png deleted file mode 100644 index 6a68423b09..0000000000 Binary files a/images/propose_file_change.png and /dev/null differ diff --git a/images/quick-update-comparing-changes-page.png b/images/quick-update-comparing-changes-page.png new file mode 100644 index 0000000000..8b75fead9d Binary files /dev/null and b/images/quick-update-comparing-changes-page.png differ diff --git a/images/quick-update-edit-button-on-github-page.png b/images/quick-update-edit-button-on-github-page.png new file mode 100644 index 0000000000..2add79f543 Binary files /dev/null and b/images/quick-update-edit-button-on-github-page.png differ diff --git a/images/quick-update-edit-button-on-learn-page.png b/images/quick-update-edit-button-on-learn-page.png new file mode 100644 index 0000000000..dfb170ad8f Binary files /dev/null and b/images/quick-update-edit-button-on-learn-page.png differ diff --git a/images/quick-update-editor-page.png b/images/quick-update-editor-page.png new file mode 100644 index 0000000000..3b7ba57f92 Binary files /dev/null and b/images/quick-update-editor-page.png differ diff --git a/images/quick-update-fork-this-repository-page.png b/images/quick-update-fork-this-repository-page.png new file mode 100644 index 0000000000..3e78555ce8 Binary files /dev/null and b/images/quick-update-fork-this-repository-page.png differ diff --git a/images/quick-update-github-edit-icon.png b/images/quick-update-github-edit-icon.png new file mode 100644 index 0000000000..ba180b5f75 Binary files /dev/null and b/images/quick-update-github-edit-icon.png differ diff --git a/images/quick-update-open-a-pull-request-page.png b/images/quick-update-open-a-pull-request-page.png new file mode 100644 index 0000000000..7087660ec9 Binary files /dev/null and b/images/quick-update-open-a-pull-request-page.png differ diff --git a/images/quick-update-propose-changes-dialog.png b/images/quick-update-propose-changes-dialog.png new file mode 100644 index 0000000000..54a2d31b33 Binary files /dev/null and b/images/quick-update-propose-changes-dialog.png differ diff --git a/images/upload_files.png b/images/upload_files.png index 2ae1b27ee2..231f5c6a78 100644 Binary files a/images/upload_files.png and b/images/upload_files.png differ diff --git a/ms-commerce/TOC.yml b/ms-commerce/TOC.yml new file mode 100644 index 0000000000..b5ef71ac32 --- /dev/null +++ b/ms-commerce/TOC.yml @@ -0,0 +1,2 @@ +- name: Index + href: index.md \ No newline at end of file diff --git a/ms-commerce/breadcrumb/toc.yml b/ms-commerce/breadcrumb/toc.yml new file mode 100644 index 0000000000..61d8fca61e --- /dev/null +++ b/ms-commerce/breadcrumb/toc.yml @@ -0,0 +1,3 @@ +- name: Docs + tocHref: / + topicHref: / \ No newline at end of file diff --git a/ms-commerce/docfx.json b/ms-commerce/docfx.json new file mode 100644 index 0000000000..87dabf8d0c --- /dev/null +++ b/ms-commerce/docfx.json @@ -0,0 +1,50 @@ +{ + "build": { + "content": [ + { + "files": [ + "**/*.md", + "**/*.yml" + ], + "exclude": [ + "**/obj/**", + "**/includes/**", + "_themes/**", + "_themes.pdf/**", + "**/docfx.json", + "_repo.en-us/**", + "README.md", + "LICENSE", + "LICENSE-CODE", + "ThirdPartyNotices.md" + ] + } + ], + "resource": [ + { + "files": [ + "**/*.png", + "**/*.jpg" + ], + "exclude": [ + "**/obj/**", + "**/includes/**", + "_themes/**", + "_themes.pdf/**", + "**/docfx.json", + "_repo.en-us/**" + ] + } + ], + "overwrite": [], + "externalReference": [], + "globalMetadata": { + "breadcrumb_path": "/powershell/breadcrumb/toc.json", + "extendBreadcrumb": true, + "feedback_system": "None" + }, + "fileMetadata": {}, + "template": [], + "dest": "ms-commerce" + } +} \ No newline at end of file diff --git a/ms-commerce/index.md b/ms-commerce/index.md new file mode 100644 index 0000000000..ac668226df --- /dev/null +++ b/ms-commerce/index.md @@ -0,0 +1 @@ +# Welcome to ms-commerce! \ No newline at end of file diff --git a/officewebapps/docfx.json b/officewebapps/docfx.json index 4eee300d92..025b927d0f 100644 --- a/officewebapps/docfx.json +++ b/officewebapps/docfx.json @@ -2,7 +2,9 @@ "build": { "content": [ { - "files": ["**/*.md"], + "files": [ + "**/*.md" + ], "src": "docs-conceptual", "version": "officewebapps-ps", "dest": "officewebapps", @@ -12,26 +14,36 @@ "README.md", "LICENSE", "LICENSE-CODE", - "ThirdPartyNotices"] + "ThirdPartyNotices" + ] }, { - "files": ["toc.yml"], + "files": [ + "toc.yml" + ], "src": "docs-conceptual", "version": "officewebapps-ps", "dest": "officewebapps/officewebapps-ps" }, { - "files": ["**/*.md"], - "src": "officewebapps-ps", - "version": "officewebapps-ps", - "dest": "module" - }, - { - "files": ["toc.yml"], - "src": "officewebapps-ps", - "version": "officewebapps-ps", - "dest": "module/officewebapps-ps" - } + "files": [ + "**/*.yml" + ], + "exclude": [ + "toc.yml" + ], + "src": "officewebapps-ps", + "version": "officewebapps-ps", + "dest": "module" + }, + { + "files": [ + "toc.yml" + ], + "src": "officewebapps-ps", + "version": "officewebapps-ps", + "dest": "module/officewebapps-ps" + } ], "resource": [ { @@ -53,16 +65,20 @@ "overwrite": [], "externalReference": [], "globalMetadata": { - "author" : "kenwith", - "ms.author" : "mikeplum", - "manager" : "laurawi", - "ms.date" : "11/28/2017", - "ms.topic" : "reference", - "ms.prod" : "office-online-server-powershell", - "ms.devlang" : "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" + "ms.service": "office-online-server-powershell", + "uhfHeaderId": "MSDocsHeader-Dev_Office", + "author": "serdarsoysal", + "ms.author": "mikeplum", + "manager": "laurawi", + "ms.date": "11/28/2017", + "ms.topic": "reference", + "products": [ + "https://authoring-docs-microsoft.poolparty.biz/devrel/e87e9701-158d-46fb-8165-fb54b7c45d88", + "https://authoring-docs-microsoft.poolparty.biz/devrel/8bce367e-2e90-4b56-9ed5-5e4e9f3a2dc3" + ], + "ms.devlang": "powershell", + "feedback_system": "Standard", + "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" }, "fileMetadata": {}, "template": [], diff --git a/officewebapps/docs-conceptual/index.md b/officewebapps/docs-conceptual/index.md index 8ac54086df..2b011f543a 100644 --- a/officewebapps/docs-conceptual/index.md +++ b/officewebapps/docs-conceptual/index.md @@ -1,9 +1,12 @@ --- -title: Office Online Server cmdlet reference +title: Office Online Server cmdlet help reference +description: "Learn about the Office Online Server PowerShell cmdlet help reference." --- -# Office Online Server cmdlet reference -Welcome to the Office Online Server PowerShell cmdlet help references. The Office Online Server cmdlets provide the command line interface for administration and management. +# Office Online Server cmdlet help reference -Here you will find all of the Office Online Server PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. +Welcome to the Office Online Server PowerShell cmdlet **Help** reference. The Office Online Server cmdlets provide the command line interface for administration and management. + +Here, you will find all of the Office Online Server PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README. + +The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page. diff --git a/officewebapps/mapping/MAML2Yaml/monikerMapping.json b/officewebapps/mapping/MAML2Yaml/monikerMapping.json new file mode 100644 index 0000000000..3c722651ec --- /dev/null +++ b/officewebapps/mapping/MAML2Yaml/monikerMapping.json @@ -0,0 +1,11 @@ +{ + "officewebapps-ps": { + "conceptualToc": "docs-conceptual/toc.yml", + "conceptualTocUrl": "/powershell/officewebapps/officewebapps-ps/toc.json", + "referenceTocUrl": "/powershell/module/officewebapps-ps/toc.json", + "packageRoot": "officewebapps-ps", + "modules": { + "officewebapps": {} + } + } +} \ No newline at end of file diff --git a/officewebapps/mapping/monikerMapping.json b/officewebapps/mapping/monikerMapping.json deleted file mode 100644 index f9897aa0d7..0000000000 --- a/officewebapps/mapping/monikerMapping.json +++ /dev/null @@ -1,11 +0,0 @@ -{ - "officewebapps-ps": { - "conceptualToc": "docs-conceptual/toc.yml", - "conceptualTocUrl": "/powershell/officewebapps/officewebapps-ps/toc.json", - "referenceTocUrl": "/powershell/module/officewebapps-ps/toc.json", - "packageRoot": "officewebapps-ps", - "modules": { - "officewebapps": {} - } - } -} \ No newline at end of file diff --git a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelBIServer.md b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelBIServer.md index 34e5b3cf95..5f8470dadc 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelBIServer.md +++ b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelBIServer.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Get-OfficeWebAppsExcelBIServer online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelUserDefinedFunction.md b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelUserDefinedFunction.md index 1eef2fe729..1af1fd7bb1 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelUserDefinedFunction.md +++ b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsExcelUserDefinedFunction.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Get-OfficeWebAppsExcelUserDefinedFunction online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsFarm.md b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsFarm.md index 9c8af3b0a2..6aceca683e 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsFarm.md +++ b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsFarm.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Get-OfficeWebAppsFarm online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsHost.md b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsHost.md index 84c57680d5..453f1006dc 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsHost.md +++ b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsHost.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Get-OfficeWebAppsHost online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsMachine.md b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsMachine.md index 2bb2e6d719..45ec6f32f5 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsMachine.md +++ b/officewebapps/officewebapps-ps/officewebapps/Get-OfficeWebAppsMachine.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Get-OfficeWebAppsMachine online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -38,7 +38,7 @@ This example returns details about the current server that is in an Office Onlin (Get-OfficeWebAppsFarm).Machines ``` -This example returns details about all servers that are in a Office Online Server farm. +This example returns details about all servers that are in an Office Online Server farm. ## PARAMETERS diff --git a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelBIServer.md b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelBIServer.md index d865a709fa..0640085f2b 100644 --- a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelBIServer.md +++ b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelBIServer.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: New-OfficeWebAppsExcelBIServer online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelUserDefinedFunction.md b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelUserDefinedFunction.md index e2edbbba6d..c631ff437e 100644 --- a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelUserDefinedFunction.md +++ b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelUserDefinedFunction.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: New-OfficeWebAppsExcelUserDefinedFunction online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsFarm.md b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsFarm.md index c9f6c09488..d2afbe0bcb 100644 --- a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsFarm.md +++ b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsFarm.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: New-OfficeWebAppsFarm online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsHost.md b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsHost.md index 594440be2d..b8b8d28dcf 100644 --- a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsHost.md +++ b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsHost.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: New-OfficeWebAppsHost online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -22,7 +22,7 @@ New-OfficeWebAppsHost -Domain <String> ## DESCRIPTION The New-OfficeWebAppsHost cmdlet adds a host domain to the list of host domains to which Office Online Server allows file operations requests, such as file retrieval, metadata retrieval, and file changes. -This list, known as the Allow List, is a security feature that prevents unwanted hosts from connecting to a Office Online Server farm and using it for file operations without your knowledge. +This list, known as the Allow List, is a security feature that prevents unwanted hosts from connecting to an Office Online Server farm and using it for file operations without your knowledge. You may any domain type including: Public, Pool, Farm, and Active Directory domain names. Just make sure that the domain you're granting access to meets your security requirements. diff --git a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsMachine.md b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsMachine.md index 7b70c7e27b..e14ee933a9 100644 --- a/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsMachine.md +++ b/officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsMachine.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: New-OfficeWebAppsMachine online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelBIServer.md b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelBIServer.md index 50c42ec44e..a77ac79a21 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelBIServer.md +++ b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelBIServer.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Remove-OfficeWebAppsExcelBIServer online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelUserDefinedFunction.md b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelUserDefinedFunction.md index ff4a32d5e6..6fb132b9ed 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelUserDefinedFunction.md +++ b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsExcelUserDefinedFunction.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Remove-OfficeWebAppsExcelUserDefinedFunction online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsHost.md b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsHost.md index bbc40268ab..24e918437f 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsHost.md +++ b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsHost.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Remove-OfficeWebAppsHost online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsMachine.md b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsMachine.md index 6ee92cce6e..eb7f54047f 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsMachine.md +++ b/officewebapps/officewebapps-ps/officewebapps/Remove-OfficeWebAppsMachine.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Remove-OfficeWebAppsMachine online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Repair-OfficeWebAppsFarm.md b/officewebapps/officewebapps-ps/officewebapps/Repair-OfficeWebAppsFarm.md index ac327af11a..fa7c33ca21 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Repair-OfficeWebAppsFarm.md +++ b/officewebapps/officewebapps-ps/officewebapps/Repair-OfficeWebAppsFarm.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Repair-OfficeWebAppsFarm online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -21,7 +21,7 @@ Repair-OfficeWebAppsFarm [-Force] [-WhatIf] [-Confirm] ``` ## DESCRIPTION -The Repair-OfficeWebAppsFarm cmdlet removes all servers flagged as unhealthy from a Office Online Server farm. +The Repair-OfficeWebAppsFarm cmdlet removes all servers flagged as unhealthy from an Office Online Server farm. This cmdlet updates the farm topology but does not clean up services and web applications on the servers that are removed. For this reason, we recommend making every effort to run the Remove-OfficeWebAppsMachine cmdlet from the unhealthy servers so that they are cleanly removed from the farm. Use the Repair-OfficeWebAppsFarm cmdlet only if the unhealthy servers have failed and you cannot run the Remove-OfficeWebAppsMachine cmdlet directly on them. diff --git a/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsExcelUserDefinedFunction.md b/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsExcelUserDefinedFunction.md index 833080488b..3f8b966834 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsExcelUserDefinedFunction.md +++ b/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsExcelUserDefinedFunction.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Set-OfficeWebAppsExcelUserDefinedFunction online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsFarm.md b/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsFarm.md index 054b967c4e..800ce67d72 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsFarm.md +++ b/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsFarm.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Set-OfficeWebAppsFarm online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsMachine.md b/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsMachine.md index 0c053e0c5c..eced821b85 100644 --- a/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsMachine.md +++ b/officewebapps/officewebapps-ps/officewebapps/Set-OfficeWebAppsMachine.md @@ -4,8 +4,8 @@ Module Name: officewebapps title: Set-OfficeWebAppsMachine online version: schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- diff --git a/repo_docs/ADVANCED.md b/repo_docs/ADVANCED.md index 5b79291b23..4dda622c87 100644 --- a/repo_docs/ADVANCED.md +++ b/repo_docs/ADVANCED.md @@ -1,200 +1,172 @@ # Contribute using tools such as Git and Visual Studio Code (advanced) ## Steps in a nutshell + 1. Fork Office PowerShell repo to your own account. 2. Clone your repo to your local development computer. -``` -git clone [URL to your forked repo] -``` + + ```DOS + git clone [URL to your forked repo] + ``` + 3. Keep your forked repo up-to-date with upstream repo. -``` -git remote add upstream https://github.com/MicrosoftDocs/office-docs-powershell.git -``` -``` -git fetch upstream -``` + + ```DOS + git remote add upstream https://github.com/MicrosoftDocs/office-docs-powershell.git + git fetch upstream + ``` + 4. Create your own working branch. -``` -git checkout -b [name of your branch] -``` + + ```DOS + git checkout -b [name of your branch] + ``` + 5. Work on content in your favorite Markdown editor. 6. Test to make sure your work matches the correct schema (use PlatyPS tool for this). 7. Merge the Master branch with your working branch (in your forked repo) and resolve any issues. -``` -git merge master [name of your branch] -``` + + ```DOS + git merge master [name of your branch] + ``` + 8. Submit a Pull Request to move your work upstream. ## Steps in more detail ### Sign In or Join GitHub -To sign in to GitHub, point your web browser to https://github.com/login. -To join GitHub for the first time, point your web browser to -https://github.com/join. +To sign in to GitHub, point your web browser to <https://github.com/login>. + +To join GitHub for the first time, point your web browser to <https://github.com/join>. -It is highly recommended to turn on two-factor authentication for security, see -https://help.github.com/articles/about-two-factor-authentication/. +It is highly recommended to turn on two-factor authentication for security, see <https://help.github.com/articles/about-two-factor-authentication/>. ### Fork the GitHub repository into your own account -Fork the GitHub project into your own account so you have a place to work on it. -To Fork the project, point your web browser to the repository at -https://github.com/MicrosoftDocs/office-docs-powershell -and then click the Fork button on the upper right corner of the repository page as shown in screenshot. +Fork the GitHub project into your own account so you have a place to work on it. To Fork the project, point your web browser to the repository at +<https://github.com/MicrosoftDocs/office-docs-powershell> and then click the Fork button on the upper right corner of the repository page as shown in screenshot. -![Image of Fork button on Github](../images/fork_button_on_github.png) +![Image of Fork button on Github.](../images/fork_button_on_github.png) -You now have your very own copy (fork) of the main Office PowerShell repository. You can see it by clicking on your profile drop-down in the upper right of the page and choosing Your Profile and then clicking the Repositories tab of your GitHub account as shown in the diagram. +You now have your very own copy (fork) of the main Office PowerShell repository. You can see it by clicking on your profile drop-down in the upper right of the page and choosing Your Profile and then clicking the Repositories tab of your GitHub account as shown in the diagram. -![View Your Forked Repos on Github](../images/view_your_forked_repos.png) +![View Your Forked Repos on Github.](../images/view_your_forked_repos.png) -Your repository is an exact copy of the original Office PowerShell repository and is located in your GitHub account. -In GitHub terms the main Office PowerShell repository is the Upstream repository and your forked version is the Downstream repository. +Your repository is an exact copy of the original Office PowerShell repository and is located in your GitHub account. In GitHub terms the main Office PowerShell repository is the Upstream repository and your forked version is the Downstream repository. -You can update your repository with the Upstream repository at any time and it is recommended to do this fairly often so that your fork doesn't get out of sync with the original. -The next section covers cloning and updating your repo with the upstream repo. +You can update your repository with the Upstream repository at any time and it is recommended to do this fairly often so that your fork doesn't get out of sync with the original. The next section covers cloning and updating your repo with the upstream repo. ### Clone your Fork to your local development machine -Now that you have your own copy of the repository on GitHub the next step is to get the actual files on your local computer so you can work with them. -To do this you clone your GitHub repository to your local computer. Here is a diagram: -![Diagram of repository flow on Github](../images/github_flow.png) +Now that you have your own copy of the repository on GitHub the next step is to get the actual files on your local computer so you can work with them. To do this you clone your GitHub repository to your local computer. Here is a diagram: + +![Diagram of repository flow on Github.](../images/github_flow.png) -Tip: You can clone your repository to muliple computers if you choose. -You just have to make sure you save your local work by pushing it back up to your repository. -And vice versa, when you start working on a new computer you have to remember to pull any changes down to your local work computer. -This will be described in more detail later on. +> [!TIP] +> You can clone your repository to multiple computers if you choose. You just have to make sure you save your local work by pushing it back up to your repository. And vice versa, when you start working on a new computer you have to remember to pull any changes down to your local work computer. This will be described in more detail later on. -There are many tools that can be used to work with GitHub. -This example uses Visual Studio Code but use whatever you prefer. -The concepts are the same. Visual Studio Code is available for -**Windows, Linux, and Mac**. -You can find it here: -https://code.visualstudio.com/ +There are many tools that can be used to work with GitHub. This example uses Visual Studio Code but use whatever you prefer. The concepts are the same. Visual Studio Code is available for **Windows, Linux, and Mac**. You can find it here: <https://code.visualstudio.com/>. -If you have Git Bash installed you can get to it from within Visual Studio Code by pressing -**Control-`** (control-backtick key which is to the left of number 1). +If you have Git Bash installed you can get to it from within Visual Studio Code by pressing **Control-`** (control-backtick key which is to the left of number 1). Using Visual Studio Code and Git Bash you can clone a repository as follows: -``` + +```DOS git clone [URL to your forked repo] ``` -For example, `git clone https://github.com/kenwith/office-docs-powershell.git` +For example, -Note that in this example my user is -**kenwith** -so I need to make sure I am cloning the Fork I created and not the upstream original. -The user is in the URL for the GitHub repo. +```DOS +git clone https://github.com/kenwith/office-docs-powershell.git +``` -Once you have cloned your repository you can use git push and git pull to push and pull your changes up to your repository. -It is best to use your own working branch so this will be covered in the next section. +Note that in this example my user is **kenwith** so I need to make sure I am cloning the Fork I created and not the upstream original. The user is in the URL for the GitHub repo. -To update your copy of the repo with the upstream copy you first need to add a remote origin and then fetch the upstream branch. -There are many ways to do this but one way is to use Git Bash as follows: -``` +Once you have cloned your repository you can use git push and git pull to push and pull your changes up to your repository. It is best to use your own working branch so this will be covered in the next section. + +To update your copy of the repo with the upstream copy you first need to add a remote origin and then fetch the upstream branch. There are many ways to do this but one way is to use Git Bash as follows: + +```DOS git remote add upstream https://github.com/MicrosoftDocs/office-docs-powershell.git -``` -``` git fetch upstream ``` -For more details, see: -- https://help.github.com/articles/configuring-a-remote-for-a-fork/ -- https://help.github.com/articles/syncing-a-fork/ +For details, see: + +- <https://help.github.com/articles/configuring-a-remote-for-a-fork/> +- <https://help.github.com/articles/syncing-a-fork/> ### Create and checkout a branch for your work -The next step is to create your own working branch. -The reason for this is so that you can pull updates from the Master branch from the upstream repository and merge your own working branch in your own Fork. -This way you can be sure when you do a Pull Request that you won't be conflicting with edits that have happened since you forked the project. + +The next step is to create your own working branch. The reason for this is so that you can pull updates from the Master branch from the upstream repository and merge your own working branch in your own Fork. This way you can be sure when you do a Pull Request that you won't be conflicting with edits that have happened since you forked the project. In the Git Bash terminal in Visual Studio Code: -``` + +```DOS git checkout -b [name of your branch] ``` -Note the -b flag creates the branch if it doesn't exist and switches to it. To checkout an existing branch leave out the -b flag. +Note the `-b` flag creates the branch if it doesn't exist and switches to it. To checkout an existing branch leave out the `-b` flag. ### Make edits to the relevant PowerShell cmdlet markdown -Open your favorite Markdown editor and edit the Markdown in your working branch. -Tip: Visual Studio Code provides a nice side-by-side view for editing Markdown content. -One side will show the Markdown source and the other side will show a preview of how the Markdown will render. -You can find this view by clicking the small icon in the upper right of Visual Studio Code that looks like a side by side view with a magnifying glass. +Open your favorite Markdown editor and edit the Markdown in your working branch. -Some important notes when editing Markdown: +> [!TIP] +> Visual Studio Code provides a nice side-by-side view for editing Markdown content. One side will show the Markdown source and the other side will show a preview of how the Markdown will render. You can find this view by clicking the small icon in the upper right of Visual Studio Code that looks like a side by side view with a magnifying glass. -Make sure your edits match the required PowerShell schema. -The schema can be found here: https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md -Any deviations will break Get-Help. -If you want to validate you can use the PlatyPS tool. -Use the New-ExternalHelp command (from PlatyPS) on your Markdown. -If there are any schema errors they will show up. +Some important notes when editing Markdown: -Since GitHub is a source control system and marks edits on a per-line basis it is important to have each sentence, or concept, on its own line. -Markdown will still show paragraphs with each sentence on its own line. -To break into another paragraph add a blank line in between the paragraphs. -Here is a great article that describes this writing system: -https://rhodesmill.org/brandon/2012/one-sentence-per-line/ +Make sure your edits match the required PowerShell schema. The schema can be found here: <https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md>. Any deviations will break **Get-Help**. If you want to validate you can use the PlatyPS tool. Use the **New-ExternalHelp** command (from PlatyPS) on your Markdown. If there are any schema errors they will show up. -Learn how to write good Markdown (which is a type of Markup language): -https://guides.github.com/features/mastering-markdown/ +Since GitHub is a source control system and marks edits on a per-line basis it is important to have each sentence, or concept, on its own line. Markdown will still show paragraphs with each sentence on its own line. To break into another paragraph add a blank line in between the paragraphs. Here is a great article that describes this writing system: <https://rhodesmill.org/brandon/2012/one-sentence-per-line/>. -More about writing content for GitHub: -https://help.github.com/categories/writing-on-github/ +Learn how to write good Markdown (which is a type of Markup language): <https://guides.github.com/features/mastering-markdown/>. -You can find the schema that the content should follow here: -https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md +More about writing content for GitHub: <https://help.github.com/categories/writing-on-github/>. +You can find the schema that the content should follow here: <https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md>. ### Merge the upstream Master branch into your branch -Merge the Master branch with your working branch (in your forked repo) and resolve any issues. -https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging -It is best practice to merge the Master branch from upstream with your working branch and not vice versa. -Then you can submit a Pull Request for your working branch and the upstream repo maintainer can merge your branch into Master without issues. +Merge the Master branch with your working branch (in your forked repo) and resolve any issues. <https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging> -Make sure that you have your working branch checked out and that your forked repo is updated with the upstream Master branch. -See the section on forking above for details. +It is best practice to merge the Master branch from upstream with your working branch and not vice versa. Then you can submit a Pull Request for your working branch and the upstream repo maintainer can merge your branch into Master without issues. + +Make sure that you have your working branch checked out and that your forked repo is updated with the upstream Master branch. See the section on forking above for details. Merge the Master branch with your working branch and then resolve issues. -``` + +```DOS git merge master [name of your branch] ``` ### Create a Pull Request -To get your work back into the upstream repo you create a Pull Request. -A Pull Request asks the maintainers of the upstream repo to pull your work into the main project. -1. To create a Pull Request, Open your web browser and navigate to the main upstream repo site at: -https://github.com/MicrosoftDocs/office-docs-powershell +To get your work back into the upstream repo you create a Pull Request. A Pull Request asks the maintainers of the upstream repo to pull your work into the main project. + +1. To create a Pull Request, Open your web browser and navigate to the main upstream repo site at: <https://github.com/MicrosoftDocs/office-docs-powershell>. 2. Click the New Pull Request button towards the top of the page. 3. Click the link to "compare across forks". 4. Select the upstream branch and your local branch. 5. Click Create Pull Request. -The repo maintainers will be notified of your Pull Request. -Your Pull Request will have its own page where you can discuss and modify your request if required. +The repo maintainers will be notified of your Pull Request. Your Pull Request will have its own page where you can discuss and modify your request if required. +## Confirm your work shows up on learn.microsoft.com -## Confirm your work shows up on docs.microsoft.com -Once your Pull Request is approved and your branch merged into Master your changes will show up on the review.docs.microsoft.com site. -Unfortunately this site requires a Microsoft login. +Once your Pull Request is approved and your branch merged into Master your changes will show up on the review.learn.microsoft.com site. Unfortunately this site requires a Microsoft login. -The next step is for a maintainer to merge the Master branch into the Live branch. -Once this is done your work will show up on docs.microsoft.com. +The next step is for a maintainer to merge the Master branch into the Live branch. Once this is done your work will show up on learn.microsoft.com. -The easiest way to find a cmdlet on docs.microsoft.com is to use the PowerShell Browser here: https://docs.microsoft.com/powershell/module -If you know a cmdlet exists but doesn't show up in the PowerShell Browser search then open an Issue (link at top of this repo). +The easiest way to find a cmdlet on learn.microsoft.com is to use the PowerShell Browser here: <https://learn.microsoft.com/powershell/module>. If you know a cmdlet exists but doesn't show up in the PowerShell Browser search then open an Issue (link at top of this repo). When the product team releases a new build your work will also show up in the Office products themselves when a user types Get-Help for the cmdlets that you worked on. ### Congratulations are in order! -You just joined an elite club of contributors to Microsoft Office documentation! -Your edits will be pulled into the product and show up under Get-Help when someone is viewing reference content for the cmdlet you edited. -See your status here: -https://github.com/MicrosoftDocs/office-docs-powershell/graphs/contributors -Don't forget to ~~brag~~ share on social media! -Sharing helps sustain the community and advertises to others to contribute to the open source content as well! +You just joined an elite club of contributors to Microsoft Office documentation! Your edits will be pulled into the product and show up under Get-Help when someone is viewing reference content for the cmdlet you edited. See your status here: <https://github.com/MicrosoftDocs/office-docs-powershell/graphs/contributors> + +Don't forget to ~~brag~~ share on social media! Sharing helps sustain the community and advertises to others to contribute to the open source content as well! diff --git a/repo_docs/FAQ.md b/repo_docs/FAQ.md index f18618444c..3cdca633fe 100644 --- a/repo_docs/FAQ.md +++ b/repo_docs/FAQ.md @@ -1,44 +1,31 @@ # Frequently Asked Questions ## What are best practices for content on GitHub? -It is best practice to keep each sentence or idea on its own line. -This is so that anyone that is reviewing a commit can quickly and easily see what changed. -If you have a giant string of text on a single line then Git just flags that entire line as a 'change'. -To learn more about this concept, see https://rhodesmill.org/brandon/2012/one-sentence-per-line/. + +It is best practice to keep each sentence or idea on its own line. This is so that anyone that is reviewing a commit can quickly and easily see what changed. If you have a giant string of text on a single line then Git just flags that entire line as a 'change'. To learn more about this concept, see https://rhodesmill.org/brandon/2012/one-sentence-per-line/. ## When will my content go live? -When you submit a Pull Request it goes through a validation check and the results are shown on the Pull Request page in GitHub. -Once the checks are completed, and there are no errors or warnings, and the appropriate sign off has been completed by the product team, a GitHub maintainer will merged the Pull Request into the Master branch on GitHub. +When you submit a Pull Request it goes through a validation check and the results are shown on the Pull Request page in GitHub. Once the checks are completed, and there are no errors or warnings, and the appropriate sign off has been completed by the product team, a GitHub maintainer will merged the Pull Request into the Master branch on GitHub. -A site located at review.docs.microsoft.com shows a mirror of the docs.microsoft.com and pulls from the Master branch. -Unfortunately the review site requires a Microsoft login at this time. -This review site provides an opportunity for Microsoft product teams, support, and other internal stakeholders to review any changes before they are pushed to the live site. +A site located at review.learn.microsoft.com shows a mirror of the learn.microsoft.com and pulls from the Master branch. Unfortunately the review site requires a Microsoft login at this time. This review site provides an opportunity for Microsoft product teams, support, and other internal stakeholders to review any changes before they are pushed to the live site. -The next step is for a GitHub maintainer to merge the Master branch into the Live branch. -Once this is complete the changes in the Pull Request will show up on docs.microsoft.com (docs.microsoft.com pulls its content from the Live branch). -There is not a set schedule for this to happen but the maintainers are good about doing this fairly quickly. +The next step is for a GitHub maintainer to merge the Master branch into the Live branch. Once this is complete the changes in the Pull Request will show up on learn.microsoft.com (learn.microsoft.com pulls its content from the Live branch). There is not a set schedule for this to happen but the maintainers are good about doing this fairly quickly. ## When does the GitHub content show up in the products with Get-Help? -The one source of truth for Office PowerShell cmdlets is the GitHub repository. -When a product team ships an update or new version they can use the PlatyPS tool to generate XML and add that to the release. +The one source of truth for Office PowerShell cmdlets is the GitHub repository. When a product team ships an update or new version they can use the PlatyPS tool to generate XML and add that to the release. -The XML contains the latest version of the reference content on GitHub. -Ideally the Online versions will always have the latest content from GitHub and the On Premises products will always have the latest help with Update-Help. -The work to make this happen is not yet done so the content is only refreshed on product team releases. +The XML contains the latest version of the reference content on GitHub. Ideally the Online versions will always have the latest content from GitHub and the On Premises products will always have the latest help with Update-Help. The work to make this happen is not yet done so the content is only refreshed on product team releases. -NOTE: For now (3/1/2018) the XML is being placed in skype/update-help. -This help is generated from the New-ExternalHelp command that is part of PlatyPS. -The 2019 release is working towards pulling help from here with Update-Help. -Stay tuned. +NOTE: For now (3/1/2018) the XML is being placed in skype/update-help. This help is generated from the New-ExternalHelp command that is part of PlatyPS. The 2019 release is working towards pulling help from here with Update-Help. Stay tuned. ## What metadata do reference topics need to have? Every cmdlet reference topic needs at least the following in the metadata field at the top of the reference article: ``` -external help file: +external help file: applicable: Skype for Business Server 2015 title: Add-CsSlaDelegates author: @@ -47,59 +34,46 @@ ms.reviewer: manager: schema: 2.0.0 ``` -The *external help file* tag is for the docs.microsoft.com infrastructure. -It can be empty but without it the build will fail. -The *applicable* tag is so that when PlatyPS is run to generate the XML that goes in the product it can only pull help content for specific product versions. -Every applicable tag is located in the [Applicable Tags](https://github.com/MicrosoftDocs/office-docs-powershell/wiki/Applicable-Tags) wiki page. -These tags have to be added to the docs.microsoft.com infrastructure. -If you try to include a tag that has not been added then the build will fail. +The *external help file* tag is for the learn.microsoft.com infrastructure. It can be empty but without it the build will fail. + +The *applicable* tag is so that when PlatyPS is run to generate the XML that goes in the product it can only pull help content for specific product versions. Every applicable tag is located in the [Applicable Tags](https://github.com/MicrosoftDocs/office-docs-powershell/wiki/Applicable-Tags) wiki page. These tags have to be added to the learn.microsoft.com infrastructure. If you try to include a tag that has not been added then the build will fail. The *title* tag is for metrics. More information about metrics coming. The *author* is the GitHub alias of the person that owns this topic. Usually the PM or sometimes a dev that owns the cmdlet. + The *ms.author* is the Microsoft alias of the same author. + The *ms.reviewer* is the Microsoft alias of someone that can approve any technical changes (if different than the author). -The *manager* is the Microsoft alias of a manager for the team that owns the cmdlet. This is useful if the person that owns the cmdlet leaves the company. The manager will be reached to in order to find the new author. +The *manager* is the Microsoft alias of a manager for the team that owns the cmdlet. This is useful if the person that owns the cmdlet leaves the company. The manager will be reached to in order to find the new author. -The *schema* tag let's the build system know what schema to use. -The 2.0.0 is the only supported schema currently. -The schema can be viewed on the PlatyPS site, see https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md. +The *schema* tag let's the build system know what schema to use. The 2.0.0 is the only supported schema currently. The schema can be viewed on the PlatyPS site, see <https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md>. -There is also metadata at the global level for the folder. -This metadata is contained in the docfx.json file of the folder. -For example, SharePoint is here: https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/docfx.json +There is also metadata at the global level for the folder. This metadata is contained in the docfx.json file of the folder. For example, SharePoint is here: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/docfx.json>. ## What is the special Table of Contents (TOC) file all about? Every folder has a special file that is a table of contents for all the files in the folder. Some examples are: -* Teams: https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/teams/teams-ps/teams/teams.md -* Skype: https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/skype/skype-ps/skype/skype.md -* SharePoint Server: https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md -Every folder must have this TOC file. -When you browse the list of cmdlets in the Reference folder this is the file you see. -For example, https://docs.microsoft.com/powershell/module/skype/?view=skype-ps. -Note that docs.microsoft.com automatically strips out the note about manually entering a description. -It ONLY strips this out if it is in the exact format given. -Any slight deviation from the format and it won't strip it out and you will see that "manually enter description" text. +- Teams: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/teams/teams-ps/teams/teams.md> +- Skype: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/skype/skype-ps/skype/skype.md> +- Exchange: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/main/exchange/exchange-ps/exchange/exchange.md> + +Every folder must have this TOC file. When you browse the list of cmdlets in the Reference folder this is the file you see. For example, <https://learn.microsoft.com/powershell/module/skype/?view=skype-ps>. Note that learn.microsoft.com automatically strips out the note about manually entering a description. It ONLY strips this out if it is in the exact format given. Any slight deviation from the format and it won't strip it out and you will see that "manually enter description" text. ## I can't find the cmdlet I am looking for, what can I do? -Finding a cmdlet can sometimes be a challenge. -This is because you might need to use cmdlets that are in various modules and across multiple products. -For example, you might need a Windows cmdlet, then an Azure cmdlet, then a SharePoint cmdlet, then an Office 365 cmdlet. +Finding a cmdlet can sometimes be a challenge. This is because you might need to use cmdlets that are in various modules and across multiple products. For example, you might need a Windows cmdlet, then an Azure cmdlet, then a SharePoint cmdlet, then an Office 365 cmdlet. -The best way to find cmdlets is to use the PowerShell Browser and search. -The PowerShell Browser searches across all products and platforms. -You can find the PowerShell Browser here: https://docs.microsoft.com/powershell/module +The best way to find cmdlets is to use the PowerShell Browser and search. The PowerShell Browser searches across all products and platforms. You can find the PowerShell Browser here: <https://learn.microsoft.com/powershell/module>. ## I am a Microsoft employee but new to GitHub, what should I do? -You can learn about working with GitHub as a Microsoft employee here: https://docs.opensource.microsoft.com/github/ +You can learn about working with GitHub as a Microsoft employee here: <https://docs.opensource.microsoft.com/github/> In a nutshell you need to create a GitHub account and link it with your Microsoft account so you can contribute openly. @@ -111,45 +85,39 @@ They try to get to these every day and verify and merge Pull Requests. If it is an emergency you can look through the merge history and see who has worked on and merged a recent version and contact them directly. -If you are a Microsoft employee you can email the distribution group which includes the maintainers of the repository. -The distribution group is Office Docs PowerShell Maintainers (od-powershell). +If you are a Microsoft employee you can email the distribution group which includes the maintainers of the repository. The distribution group is Office Docs PowerShell Maintainers (od-powershell). ## Git is getting on my nerves, do you have any advice? One of the most confusing things with Git and GitHub is that there are many, many ways to do things. -You can use the command line with a cmd prompt or you can use a command line with git bash or you can use a GUI like GitHub Desktop https://desktop.github.com/. +You can use the command line with a cmd prompt or you can use a command line with git bash or you can use a GUI like GitHub Desktop <https://desktop.github.com/>. -If you are working with the command line using Git Bash, this will help: -https://www.codeproject.com/Articles/457305/Basic-Git-Command-Line-Reference-for-Windows-Users +If you are working with the command line using Git Bash, this will help: <https://www.codeproject.com/Articles/457305/Basic-Git-Command-Line-Reference-for-Windows-Users>. Also check out Git Kraken https://www.gitkraken.com/ which has a great user interface and visualizations. ## Why are all the cmdlets for a given product in a single folder in the repo? Wouldn't it be better to put them in buckets? -GitHub is the single source of truth for Office PowerShell cmdlet reference. -There is a single reference article per cmdlet. -There is a folder for each major product area in order to create a basic structure but this isn't require for the system to work. -Each article is tagged with appropriate metadata for versioning. -Keeping things as simple as possible has a number of benefits. -For more about the design of the system, see the FAQ item *"Why is this open source project designed the way it is?"*. +GitHub is the single source of truth for Office PowerShell cmdlet reference. There is a single reference article per cmdlet. There is a folder for each major product area in order to create a basic structure but this isn't require for the system to work. Each article is tagged with appropriate metadata for versioning. Keeping things as simple as possible has a number of benefits. For more about the design of the system, see the FAQ item *"Why is this open source project designed the way it is?"*. ## Why is this open source project designed the way it is? + The system was designed to be as simple as possible in order to achieve three primary objectives. 1. Increase community engagement. There are many open source projects and every one of them is striving for community involvement. We designed the PowerShell reference project to be easily understood in order to increase community ownership and contributions. - If a person comes to a project and they cannot understand what they can do in 20-30 seconds then they are likely to bounce on to something else. - The open source PowerShell reference project was designed to break down the barriers to understanding and so someone can ‘flow’ directly into contributions once they have discovered the project. + If a person comes to a project and they cannot understand what they can do in 20-30 seconds then they are likely to bounce on to something else. + The open source PowerShell reference project was designed to break down the barriers to understanding and so someone can 'flow' directly into contributions once they have discovered the project. A vibrant and active community results in the best reference content that goes directly back into PowerShell Get-Help. - + 1. Central location for content that feeds multiple surfacing mechanisms. - The first two places the PowerShell reference content is surfaces is Get-Help in PowerShell itself and the docs.microsoft.com website. - In the future the content can also be surfaced in an iOS app, Android app, Windows Universal app, and other mechanisms. - With a simple, centralized, system for the source of truth, in GitHub, it becomes much easier to surface content using multiple mechanisms since GitHub is not tailored for once specific location, such as Get-Help. + The first two places the PowerShell reference content is surfaces is Get-Help in PowerShell itself and the learn.microsoft.com website. + In the future the content can also be surfaced in an iOS app, Android app, Windows Universal app, and other mechanisms. + With a simple, centralized, system for the source of truth, in GitHub, it becomes much easier to surface content using multiple mechanisms since GitHub is not tailored for once specific location, such as Get-Help. If the GitHub repo focused on one specific site or mechanism then surfacing from other mechanisms could become too complex or could exponentially expound the effort required. 1. Keep content fresh and up to date. @@ -158,5 +126,3 @@ The system was designed to be as simple as possible in order to achieve three pr The system was designed so that the process can be automated, perhaps with a GitHub webhook that triggers on any merge. The idea is that in the past the Get-Help content was immediately outdated once a product shipped. With the new system the content in Get-Help will always be up-to-date by running an Update-Help, or equivalent, command in PowerSHell. - - diff --git a/repo_docs/NEW_CMDLETS.md b/repo_docs/NEW_CMDLETS.md index f79bd70ad8..fbbbaaefc1 100644 --- a/repo_docs/NEW_CMDLETS.md +++ b/repo_docs/NEW_CMDLETS.md @@ -1,236 +1,182 @@ # Create new cmdlet topics + Cmdlet reference topics follow a very strict schema that's difficult to duplicate manually (remember, the topics on the web are also used for `Get-Help` from the command line). Instead, you use the open-source [platyPS](https://github.com/PowerShell/platyPS) tool to export the cmdlet and all of its properties to a markdown (.md) file from your PowerShell connection to the server or service. ## Step 1: Install platyPS -If you're running Windows 10 or Windows Server 2016, you already have Windows PowerShell 5.x installed, so installing platyPS is easy. -Run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**): +On Windows 10, Windows Server 2016, or later, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**): -``` +```powershell Install-Module -Name platyPS -Scope CurrentUser ``` -**Notes**: - -- You need platyPS v0.11.1 or later, released on or about September 13, 2018. If you have an earlier version of platyPS installed, close all open Windows PowerShell windows where the platyPS module is currently loaded (or run the command `Remove-Module platyPS`) and then run `Update-Module platyPS` from an elevated Windows PowerShell window. - -- Windows PowerShell 5.x is part of the Windows Management Framework (WMF) and can be [downloaded](https://aka.ms/wmf5download) and installed on these versions of Windows: - - - Windows Server 2012 R2 - - - Windows Server 2012 - - - Windows Server 2008 R2 SP1 - - - Windows 8.1 +If you need to install platyPS on old versions of Windows (Windows 8.1 or Windows 2012 R2 or earlier), you need to install Windows PowerShell 5.1 before you can install platyPS. For instructions, see the [Install platyPS on older versions of Windows](#install-platyps-on-older-versions-of-windows) section at the end of this article. - - Windows 7 +If you need to install platyPS on really old versions of Windows (a server running a product that lacks support for WMF 5.1 or its requirements), see the [Install platyPS on really old versions of Windows](#install-platyps-on-older-versions-of-windows) section at the end of this article. - If you need to install platyPS on an older version of Windows (for example, a server running a product that lacks support for WMF 5.x or its requirements), see the [Install platyPS on older versions of Windows](#install-platyps-on-older-versions-of-windows) section at the end of this topic. +You need platyPS v0.14.0 or later (released April 2019). If you have an earlier version of platyPS installed, close all open Windows PowerShell windows where the platyPS module is currently loaded and then run `Update-Module platyPS` from a new elevated Windows PowerShell window. Or, run the command `Remove-Module platyPS` and then run `Install-Module -Name platyPS -Scope CurrentUser` to get the current version. ## Step 2: Connect to the PowerShell environment that has the cmdlet -You probably know how to do this already, but the available workloads and connection methods are: - -- Skype for Business Online: [https://technet.microsoft.com/library/dn362795.aspx](https://technet.microsoft.com/library/dn362795.aspx) -- Microsoft Teams: [https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/](https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/) +You probably know how to do this already, but the available workloads and connection methods are: - **HINT:** Use `Upgrade-Module` and also `Uninstall-Module` depending on the module version you have installed. +- Microsoft Teams: [Install Microsoft Teams PowerShell](https://learn.microsoft.com/MicrosoftTeams/teams-powershell-install) -- SharePoint Online: [Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online) + > [!TIP] + > Use `Upgrade-Module` and also `Uninstall-Module` depending on the module version you have installed. - Exchange: - - - Exchange Online: [Connect to Exchange Online PowerShell](https://docs.microsoft.com/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell) - - - Office 365 Security & Compliance Center: [Connect to Office 365 Security & Compliance Center PowerShell](https://docs.microsoft.com/powershell/exchange/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell) - - - Exchange Online Protection: [Connect to Exchange Online Protection PowerShell](https://docs.microsoft.com/powershell/exchange/exchange-eop/connect-to-exchange-online-protection-powershell) - - - Exchange Server: [Connect to Exchange servers using remote PowerShell](https://docs.microsoft.com/powershell/exchange/exchange-server/connect-to-exchange-servers-using-remote-powershell) - -**Notes**: - -- You might need to connect to the service in an elevated Windows PowerShell prompt (required for Skype for Business Online and Teams, but not Exchange). The connection instructions topic should contain this and other connection requirements. - -- In Exchange environments, the cmdlets available to you are controlled by role-based access control (RBAC). Most cmdlets and parameters are available to administrators by default, but some aren't (for example, the "Mailbox Search" and "Mailbox Import Export" roles). + - Exchange Online PowerShell: [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell) + - Security & Compliance PowerShell: [Connect to Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-scc-powershell) + - Exchange Online Protection PowerShell: [Connect to Exchange Online Protection PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-protection-powershell) + - Exchange Server PowerShell: [Connect to Exchange servers using remote PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-servers-using-remote-powershell) + +> [!TIP] +> You might need to connect to the service in an elevated Windows PowerShell prompt (Teams and Exchange environments don't require an elevated Windows PowerShell prompt). The connection instructions article should plainly state this and other connection requirements. +> +> In Exchange and Security & Compliance PowerShell environments, the cmdlets that are available to you are controlled by role-based access control (RBAC). Most cmdlets and parameters are available to administrators by default, but some aren't (for example, the "Mailbox Search" and "Mailbox Import Export" roles. +> +> Remote PowerShell connections are deprecated in Exchange Online PowerShell and Security & Compliance PowerShell in favor of REST API connections. For more information, see the following articles: +> +> - [REST API connections in the EXO V3 module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2#rest-api-connections-in-the-exo-v3-module). +> - [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). +> - [Deprecation of Remote PowerShell (RPS) Protocol in Security & Compliance PowerShell](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432). +> +> REST API connections in the Exchange Online PowerShell V3 module incorrectly identify many parameter **Type** values as `Object` or `Object[]`. The true parameter type values are visible in product code. ## Step 3: Load platyPS in the PowerShell environment -After you've connected in PowerShell to the server or service (either in a regular Windows PowerShell window or from a specific PowerShell console shortcut), run the following command to make the platyPS cmdlets available in your session: -``` +After you've connected in PowerShell to the server or service (either in a regular Windows PowerShell window or from a specific PowerShell console shortcut), you likely don't need to do anything to make the platyPS cmdlets available to you in your session. However, it you're having issues, run the following command to manually load the platyPS module: + +```powershell Import-Module platyPS ``` ### Step 4: Find your module name -**Note**: This step is required only if you're interested in creating cmdlet reference topics for **all** available cmdlets in your product (the _Module_ parameter in `New-MarkdownHelp`). If you're going to manually specify the cmdlet names (the _Command_ parameter in `New-MarkdownHelp`), you can skip this step. + +> [!NOTE] +> This step is required only if you're interested in creating cmdlet reference articles for **all** available cmdlets in the product (using the _Module_ parameter in `New-MarkdownHelp`). If you're going to manually specify the cmdlet names (using the _Command_ parameter in `New-MarkdownHelp`), you can skip this step. platyPS needs the name of the loaded PowerShell module or snap-in that contains the cmdlets you want to update. To find the name, run the following command: -``` +```powershell Get-Module | Format-Table -Auto ``` The command returns all of the currently loaded modules or snap-ins, and the output will resemble this: -``` +```powershell ModuleType Version Name ExportedCommands ---------- ------- ---- ---------------- Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Con... Manifest 3.0.0.0 Microsoft.PowerShell.Security {ConvertFrom-SecureString, ConvertTo-SecureString, Get-Acl... Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, Add-Type, Clear-Variable, Compare-Object...} Binary 1.0.0.1 PackageManagement {Find-Package, Find-PackageProvider, Get-Package, Get-Pack... -Script 0.10.0 platyps {Get-HelpPreview, Get-MarkdownMetadata, Merge-MarkdownHelp... -Script 1.0.0.1 PowerShellGet {Find-Command, Find-DscResource, Find-Module, Find-RoleCap... -Script 1.2 PSReadline {Get-PSReadlineKeyHandler, Get-PSReadlineOption, Remove-PS... +Script 2.2.5 PowerShellGet {Find-Command, Find-DscResource, Find-Module, Find-RoleCap... +Script 2.0.0 PSReadline {Get-PSReadlineKeyHandler, Get-PSReadlineOption, Remove-PS... Script 1.0 tmp_byivwzpq.e1k {Add-AvailabilityAddressSpace, Add-DistributionGroupMember... ``` or this: -``` +```powershell ModuleType Version Name ExportedCommands ---------- ------- ---- ---------------- -Binary 16.0.7723.0 Microsoft.Online.SharePoint.PowerShell {Add-SPOGeoAdministrator, Add-SPOHubSiteAssociation, A... -Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear... -Manifest 3.0.0.0 Microsoft.PowerShell.Security {ConvertFrom-SecureString, ConvertTo-SecureString, Get... -Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, Add-Type, Clear-Variable, Compare-Object...} -Script 1.2 PSReadline {Get-PSReadlineKeyHandler, Get-PSReadlineOption, Remov... +Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Content...} +Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, Add-Type, Clear-Variable, Compare-Object...} +Script 4.2.0 MicrosoftTeams {Add-TeamChannelUser, Add-TeamUser, Connect-MicrosoftTeams, Disconnect-Microso... +Script 1.4.7 PackageManagement {Find-Package, Find-PackageProvider, Get-Package, Get-PackageProvider...} +Script 2.2.5 PowerShellGet {Find-Command, Find-DscResource, Find-Module, Find-RoleCapability...} +Script 2.0.0 PSReadline {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-PSReadLineKeyHandler, ... ``` -For services that use remote PowerShell (Skype for Business Online, Teams, Exchange Online, Security & Compliance Center, and Exchange Online Protection), the module name is a temporary value that changes every time you connect. In this output, the module name is `tmp_byivwzpq.e1k`, but yours will be different. +For services that use remote connections (Exchange), the module name is a temporary value that changes every time you connect. In the example output, the module name is `tmp_byivwzpq.e1k`, but yours will be different. -For SharePoint Online in the SharePoint Online Management Shell, the module name is always `Microsoft.Online.SharePoint.PowerShell`. +For Microsoft Teams, the module name is always `MicrosoftTeams`. Either way, take note of your module name. You'll need it in the next steps. -### Step 5: Verify your PSSession variable name -**Note**: This step is required in Exchange, Skype for Business Online and other products that use remote PowerShell in their connection instructions (one or more **xxx-xxxSession** commands are present). **If you're using SharePoint, SharePoint Online or another product that doesn't use remote PowerShell, you can skip this step**. - -Check the details of your connection instructions, but your session information is stored in a variable. For example, in the Exchange connection instructions, the variable is `$Session`. You'll use this variable name in later steps. - -**If you connected via a custom script or your remote PowerShell session variable isn't apparent, do the following steps**: - -1. Run the following command to find your session: - - ``` - Get-PSSession | Format-Table -Auto - ``` - - The output will resemble this: - - ``` - Id Name ComputerName ComputerType State ConfigurationName Availability - -- ---- ------------ ------------ ----- ----------------- ------------ - 1 WinRM1 outlook.office365.com RemoteMachine Opened Microsoft.Exchange Available - ``` - - or this: - - ``` - Id Name ComputerName ComputerType State ConfigurationName Availability - -- ---- ------------ ------------ ----- ----------------- ------------ - 1 WinRM1 admin2a.online.lync.com RemoteMachine Opened Microsoft.PowerShell Available - ``` - - **Note**: If you see multiple sessions, either start over in a new PowerShell window or confirm the session you want to use. The first connection is 1, the second is 2, and so on. - -2. Use the following syntax to store the session in a variable: - - ``` - $<VariableName> = Get-PSSession <SessionID> - ``` - - For example, using the sample output in the previous step: - - ``` - $Session = Get-PSSession 1 - ``` +### Step 5: Run platyPS to generate topic files - The variable name you choose doesn't matter, but you'll use it in later steps. - -### Step 6: Run platyPS to generate topic files You have two choices: -- **Dump _all_ cmdlets in the module/snap-in to files**: This is simple but could take a while, and you'll end up with dozens or possibly hundreds of cmdlets files you don't need. The basic syntax is: +- **Dump _all_ cmdlets in the module/snap-in to files**: This is simple but could take a while, and you'll end up with dozens or possibly hundreds of cmdlet files you don't need. The basic syntax is: + + ```powershell + New-MarkdownHelp -Module <ModuleName> -OutputFolder "<Path"> ``` - New-MarkdownHelp -Module <ModuleName> -OutputFolder "<Path"> [-Session <PSSessionVariableName>] - ``` - **Dump specific cmdlets to files**: This is a bit harder to set up, but the output is much quicker, and there are no extra topic files created. The basic syntax is: + ```powershell + New-MarkdownHelp -Command <Cmdlet> -OutputFolder "<Path"> ``` - New-MarkdownHelp -Command <Cmdlet> -OutputFolder "<Path"> [-Session <PSSessionVariableName>] - ``` - or - - ``` - $x = "<Cmdlet1>","<Cmdlet2>",..."<CmdletN>" - New-MarkdownHelp -Command $x -OutputFolder "<Path"> [-Session <PSSessionVariableName>] - ``` + or -**Notes**: + ```powershell + $x = "<Cmdlet1>","<Cmdlet2>",..."<CmdletN>" -- \<ModuleName\> is the value you found in [Step 4](#step-4-find-your-module-name) (for example, `tmp_byivwzpq.e1k` or `Microsoft.Online.SharePoint.PowerShell`). + New-MarkdownHelp -Command $x -OutputFolder "<Path"> + ``` -- \<PSSessionVariableName\> is the remote PowerShell session variable from [Step 5](#step-5-verify-your-your-pssession-variable-name) (for example, `$Session`) _and is required only if the connection instructions used remote PowerShell (one or more **xxx-xxxSession** commands)_. +**Notes**: - Failure to use the _Session_ parameter in remote PowerShell environments leads to weird results: multiple syntax blocks/parameter sets aren't recognized and are collapsed into one big block, the Type value is Object for all parameters, the Required value is False for all parameters, etc. +- \<ModuleName\> is the value you found in [Step 4](#step-4-find-your-module-name) (for example, `tmp_byivwzpq.e1k` or `MicrosoftTeams`). - If the \<Path\> location doesn't exist, it's created for you. #### Dump all cmdlets in the module/snap-in to files -This example creates topic files for all available cmdlets in the Skype for Business Online PowerShell session where the module is `tmp_byivwzpq.e1k` and the session variable is `$Session` in the folder C:\My Docs\SfBO. -``` -New-MarkdownHelp -Module tmp_byivwzpq.e1k -OutputFolder "C:\My Docs\SfBO" -Session $Session +This example creates topic files for all available cmdlets in the Microsoft Teams module `MicrosoftTeams` in the folder C:\My Docs\Teams. + +```powershell +New-MarkdownHelp -Module MicrosoftTeams -OutputFolder "C:\My Docs\Teams" ``` #### Dump specific cmdlets to files -This example creates a topic file for the cmdlet named Get-CoolFeature in the Exchange Online PowerShell session where the session variable is `$Session` in the folder "C:\My Docs\ExO". -``` -New-MarkdownHelp -Command "Get-CoolFeature" -OutputFolder "C:\My Docs\ExO" -Session $Session +This example creates a topic file for the cmdlet named **Get-CoolFeature** in the Exchange Online PowerShell session in the folder "C:\My Docs\ExO". + +```powershell +New-MarkdownHelp -Command "Get-CoolFeature" -OutputFolder "C:\My Docs\ExO" ``` -This example creates topic files for the Get-CoolFeature, New-CoolFeature, Remove-CoolFeature, and Set-CoolFeature cmdlets from the Exchange Online session where the session variable is `$Session` in the folder C:\My Docs\ExO. +This example creates topic files for the **Get-CoolFeature**, **New-CoolFeature**, **Remove-CoolFeature**, and **Set-CoolFeature** cmdlets from the Exchange Online session in the folder C:\My Docs\ExO. The first command stores the cmdlet names in a variable. The second command uses that variable to identify the cmdlets and write the output files. -``` +```powershell $NewCmdlets = "Get-CoolFeature","New-CoolFeature","Remove-CoolFeature","Set-CoolFeature" -``` +New-MarkdownHelp -Command $NewCmdlets -OutputFolder "C:\My Docs\ExO" ``` -New-MarkdownHelp -Command $NewCmdlets -OutputFolder "C:\My Docs\ExO" -Session $Session -``` -### Step 7: Document the new cmdlet -Now that you have topic files for the new cmdets, you can actually document them. The topics are plain text UTF-8 files that are formatted using [markdown](https://guides.github.com/features/mastering-markdown/). Office writers use [Visual Studio Code](https://code.visualstudio.com/) to edit topic files, but you can use Notepad or your favorite text editor. +### Step 6: Document the new cmdlet + +Now that you have topic files for the new cmdlets, you can actually document them. The topics are plain text UTF-8 files that are formatted using [markdown](https://guides.github.com/features/mastering-markdown/). Office writers use [Visual Studio Code](https://code.visualstudio.com/) to edit topic files, but you can use Notepad or your favorite text editor. These are the basic topic elements that require your attention, regardless of the product or service: - **The SYNOPSIS section**: Be brief. Use the DESCRIPTION section for less critical information. - - **The DESCRIPTION section**: More details (for example, permissions required to run the cmdlet) - - **One or more code examples in the EXAMPLES section**: The code block (only one code block) goes first, then the description text. - - **A description for every parameter in each parameter section** We highly encourage you to plagiarize existing content and formatting from other cmdlet topics in the product or service. Many parameters are common across a wide variety of cmdlets. #### Metadata in the new cmdlet + Less obvious but still important information that's often manually required in every topic is **cmdlet metadata** at the top of the topic and **parameter metadata** in every parameter section. ##### Cmdlet metadata -Every cmdlet reference topic needs at least the following in the metadata field at the top of the reference article: +Every cmdlet reference topic needs (at a minimum) the following properties in the metadata field at the top of the reference article: -``` +```text external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets +online version: https://learn.microsoft.com/powershell/module/skype/add-cssladelegates applicable: Skype for Business Server 2015 title: Add-CsSlaDelegates author: @@ -240,11 +186,11 @@ manager: schema: 2.0.0 ``` -- **external help file**: Defines which MAML/XML file the cmdlet help topic goes in for `Get-Help` at the command line. This value very product-specific, and the location is specified somewhere in product code. Some products (Skype) use only one XML file that's well-known and the same for all cmdlets; others (Exchange, SharePoint) use multiple XML files. See other topics for available values. Don't guess; a wrong value here will affect the availability of the help topic at the command line. +- **external help file**: Defines which MAML/XML file the cmdlet help topic goes in for `Get-Help` at the command line. This value very product-specific, and the location is specified somewhere in product code. Some products (Skype) use only one XML file that's well-known and the same for all cmdlets; others (Exchange) use multiple XML files. See other topics for available values. Don't guess; a wrong value here will affect the availability of the help topic at the command line. -- **Module Name**: Not used in Exchange topics (remove it). For other products, this is the module name of the product. +- **Module Name**: In Exchange topics, this value is `ExchangeOnlineManagement` for those few cmdlets that are [baked into the Exchange Online PowerShell V3 module itself](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2#cmdlets-in-the-exchange-online-powershell-module). For other products, this is the module name of the product. -- **online version**: Empty, but needs to be present. +- **online version**: This is the URL of the topic. This URL value is what makes the `Get-Help <Cmdlet> -Online` command work, so it's very important. - **applicable**: You need to add this attribute and value yourself. Notice that it starts with a lowercase 'a'. See other topics for available values. Don't invent new values here. The value **must** come from the list of predefined values. @@ -261,145 +207,169 @@ schema: 2.0.0 - **manager**: The Microsoft alias of a manager for the team that owns the cmdlet. This is useful if the person that owns the cmdlet leaves the company. The manager will be reached to in order to find the new author. ##### Parameter metadata + Here's an example of the parameter metadata that's present in every parameter section: - ```yaml - Type: String - Parameter Sets: (All) - Aliases: - Applicable: Microsoft StaffHub - Required: False - Position: 1 - Default value: None - Accept pipeline input: False - Accept wildcard characters: False - ``` +```text +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft StaffHub + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` Most of the attributes and values are generated automatically by platyPS. The ones that require manual intervention are: +- **Type**: In any environment, the values `Object` or `Object[]` are wrong. As previously described, REST API connections in the Exchange Online PowerShell V3 module incorrectly identify many parameter **Type** values as `Object` or `Object[]`. Other values like `String`, `Boolean`, and `DateTime` are detected correctly. The true parameter type values are visible in product code. + - **Applicable**: You need to add this attribute and value yourself. Notice the capital 'A'. See other topics for available values (same available values as the **applicable** attribute at the top of the topic). Don't invent new values here. The value **must** come from the list of predefined values. -- **Default value** and **Accept wildcard characters**: These attributes are present, but the values are never truthfully populated by platyPS (they're always None and False, respectively). You can correct the values if you think it's important. Otherwise, leave them as is. +- **Default value** and **Accept wildcard characters**: These attributes are present, but the values are never truthfully populated by platyPS **or any other PowerShell utility** (they're always None and False, respectively). You can correct the values if you think it's important. Otherwise, leave them as is. ### Step 8: Add the new cmdlet topic files to the repository -When you're done editing the topics, upload them to GitHub. Note that you need to fork, upload your files to your fork, then submit a Pull Request. + +When you're done editing the topics, upload them to GitHub. Note that you need to fork the repo, upload your files to your fork, and then submit a Pull Request. 1. Go to the correct location in the appropriate GitHub repository: - - Exchange: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange) + - Exchange: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange> + - Office Web Apps: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps> + - Skype: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/skype/skype-ps/skype> + - StaffHub: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/staffhub/staffhub-ps/staffhub> + - Teams: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/teams/teams-ps/teams> + - Whiteboard: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/whiteboard/whiteboard-ps/whiteboard> + - SharePoint / OneDrive: <https://github.com/MicrosoftDocs/OfficeDocs-SharePoint-PowerShell> + +2. Select **Add file** \> **Upload files** - For Exchange, you also need to go one level deeper into an appropriate subfolder. Choose wisely based on the surrounding cmdlet topics. Don't create new folders. + ![Upload file.](../images/upload_files.png) - - Office Web Apps: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps) +3. After you're done adding files, go to the **Propose changes** section at the bottom of the page: - - SharePoint Online: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-online](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-online) + - A brief title is required. By default, the title is the name of the file, but you can change it. + - Optionally, you can enter more details in the **Add an optional extended description** box. You should @ include the GitHub alias of someone who can review and approve your upload. - - SharePoint PNP: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-pnp](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-pnp) + When you're ready, click the green **Propose changes** button. - - SharePoint Server: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-server](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-server) + ![Propose file change section.](../images/propose-file-change.png) - - Skype: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/skype/skype-ps/skype](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/skype/skype-ps/skype) +4. On the **Open a pull request** page that appears, click the green **Create pull request** button. - - StaffHub: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/staffhub/staffhub-ps/staffhub](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/staffhub/staffhub-ps/staffhub) + ![Open a pull request page.](../images/open-a-pull-request-page.png) - - Teams: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/teams/teams-ps/teams](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/teams/teams-ps/teams) +5. That's it. There's nothing more for you to do. - - Whiteboard: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/whiteboard/whiteboard-ps/whiteboard](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/whiteboard/whiteboard-ps/whiteboard) +### Step 9: Add the new cmdlets to the TOC file -2. Click **Upload files** - - ![Upload file](../images/upload_files.png) +Add the cmdlet to Table of Contents (TOC) file in the GitHub repo. TOC file is the name of the module. For example: -3. After you're done adding files, go to the **Propose file change** area at the bottom of the page. Enter a title and optional description information and then click **Propose file change**. +- Exchange <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/exchange/exchange-ps/exchange/exchange.md> -4. On the next screen, click **Create pull request**. + > [!TIP] + > Exchange also uses pseudo folders to organize cmdlets. You need to add any new cmdlets in the proper location in the file: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/exchange/mapping/serviceMapping.json>. -### Step 9: Add the new cmdlets to the TOC file. -**Note**: This step isn't required for Exchange or SharePoint PNP, because there is no TOC file. +- Office Web Apps: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/officewebapps/officewebapps-ps/officewebapps/officewebapps.md> -Add the cmdlet to Table of Contents (TOC) file in the GitHub repo. TOC file is the name of the module. For example: +- Skype: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/skype/skype-ps/skype/skype.md> -- Office Web Apps: [https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/officewebapps/officewebapps-ps/officewebapps/officewebapps.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/officewebapps/officewebapps-ps/officewebapps/officewebapps.md) +- StaffHub: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/staffhub/staffhub-ps/staffhub/staffhub.md> -- SharePoint Online: [https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md) +- Teams: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/teams/teams-ps/teams/teams.md> -- SharePoint Server: [https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md) +- Whiteboard: <https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/whiteboard/whiteboard-ps/whiteboard/whiteboard.md> -- Skype: [https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/skype/skype-ps/skype/skype.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/skype/skype-ps/skype/skype.md) +In the TOC file, you can fill in a description or remove the template text line. However, if you leave the template text line make sure it's in _exactly_ the right format so it won't render as a template text. -- StaffHub: [https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/staffhub/staffhub-ps/staffhub/staffhub.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/staffhub/staffhub-ps/staffhub/staffhub.md) +The steps to edit and publish the TOC file are identical to modifying any existing topic. The instructions are [here](https://github.com/MicrosoftDocs/office-docs-powershell/blob/main/README.md) (you're starting at Step 4). -- Teams: [https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/teams/teams-ps/teams/teams.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/teams/teams-ps/teams/teams.md) +## Appendix -- Whiteboard: [https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/whiteboard/whiteboard-ps/whiteboard/whiteboard.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/whiteboard/whiteboard-ps/whiteboard/whiteboard.md) +### Reference -In the TOC file, you can fill in a description or remove the template text line. However, if you leave the template text line make sure it's in _exactly_ the right format so it won't render as a template text. +- <https://learn.microsoft.com/powershell/module/powershellget/install-module> -After you're done editing the TOC file: +- <https://learn.microsoft.com/powershell/module/powershellget/update-module> -1. Go to the **Propose file change** area at the bottom of the page. Enter a title and optional description information and then click **Propose file change**. +- <https://github.com/PowerShell/platyPS> -2. On the next screen, click **Create pull request**. +- <https://learn.microsoft.com/powershell/module/microsoft.powershell.core/get-module> -## Appendix +### Install platyPS on older versions of Windows -### Reference +> [!NOTE] +> The procedures in this section aren't required in current versions of Windows (Windows 10, Windows Server 2016, or later) or other versions of Windows where the WMF 5.1 is already installed. -- https://docs.microsoft.com/powershell/module/powershellget/install-module?view=powershell-6 +The following older versions of Windows don't automatically include Windows PowerShell 5.1, but they support it. You need to download and install the Windows Management Framework (WMF) 5.1 from <https://aka.ms/wmf5download> on these versions of Windows: -- https://docs.microsoft.com/powershell/module/powershellget/update-module?view=powershell-6 +- Windows 8.1 +- Windows Server 2012 or Windows Server 2012 R2 +- Windows 7 Service Pack 1 (SP1)<sup>1,</sup><sup>2</sup> +- Windows Server 2008 R2 SP1<sup>1,</sup><sup>2</sup> -- https://github.com/PowerShell/platyPS +- <sup>1</sup> This version of Windows has reached its end of support, and is now supported only in Azure virtual machines. +- <sup>2</sup> Windows PowerShell 5.1 on this version of Windows requires the .NET Framework 4.5 or later. For more information, see [Windows Management Framework 5.1](https://aka.ms/wmf5download). -- https://docs.microsoft.com/powershell/module/microsoft.powershell.core/get-module?view=powershell-6 +### Install platyPS on really old versions of Windows (WMF 3.0 or 4.0) +> [!NOTE] +> The procedures in this section aren't required in current versions of Windows (Windows 10, Windows Server 2016, or later) or other versions of Windows where the WMF 5.1 is already installed. -### Install platyPS on older versions of Windows +To install platyPS for use with products that require PowerShell 3.0 or 4.0 and don't initially have access to the **Install-Module** cmdlet, do the steps in this section. -**Note**: These procedures aren't required on Windows 10, Windows Server 2016, or other versions of Windows where the WMF 5.x is already installed. +1. Download and install PowerShellGet. The steps are described in [Installing PowerShellGet](https://learn.microsoft.com/powershell/scripting/gallery/installing-psget) and are summarized here as follows: -1. Download and install [PowerShellGet](https://www.microsoft.com/download/details.aspx?id=51451). + a. **PowerShell 3.0 only**: On the target computer, run the following command in an elevated Windows PowerShell window: -2. From an elevated Windows PowerShell window, run the following command: + ```powershell + [Environment]::SetEnvironmentVariable( + 'PSModulePath', + ((([Environment]::GetEnvironmentVariable('PSModulePath', 'Machine') -split ';') + "$env:ProgramFiles\WindowsPowerShell\Modules") -join ';'), 'Machine' + ) + ``` - ``` - Save-Module PowerShellGet -Path "<TargetPath>" - ``` + b. On another computer running PowerShell 5.1 or later where PowerShellGet is installed and working, open an elevated Windows PowerShell window and run the following command: - Where \<TargetPath\> is a location that's easy to find (for example, C:\Temp\PSG). + ```powershell + Save-Module PowerShellGet -Path "<ExistingPath>" + ``` - **Notes**: + Where \<ExistingPath\> is **an existing** folder/path that's easy to find (for example, `C:\Temp\PSG`). - - The target folder/path must already exist. + c. The command will create two new folders in the target path: - - The command will create two new folders in the target path: - - - PackageManagement + - `PackageManagement\<VersionFolder>\<FilesAndFolders>` + - `PowerShellGet\<VersionFolder>\<FilesAndFolders>` - - PowerShellGet + d. Move the \<FilesAndFolders\> out from under the \<VersionFolder\> and delete the now empty \<VersionFolder\> so the contents of the folders look like this: -3. Delete the following folders from your computer or move them to a remote location for safekeeping: + - `PackageManagement\<FilesAndFolders>` + - `PowerShellGet\<FilesAndFolders>` - - C:\Program Files\WindowsPowerShell\Modules\PackageManagement +2. On the target computer, delete the following folders or move them to a remote location for safekeeping: - - C:\Program Files\WindowsPowerShell\Modules\PowerShellGet + - `C:\Program Files\WindowsPowerShell\Modules\PackageManagement` + - `C:\Program Files\WindowsPowerShell\Modules\PowerShellGet` -4. In Windows Explorer, copy the PackageManagement and PowerShellGet folders FROM \<TargetPath\> TO C:\Program Files\WindowsPowerShell\Modules\ (replacing the folders you deleted in Step 3 with the new ones you downloaded in Step 2). +3. Copy the `PackageManagement` and `PowerShellGet` folders that you downloaded and fixed in Step 1b to `C:\Program Files\WindowsPowerShell\Modules` on the target computer. - You should now have the following folders again: + You should have the following folders on the target computer: - - C:\Program Files\WindowsPowerShell\Modules\PackageManagement + - `C:\Program Files\WindowsPowerShell\Modules\PackageManagement` + - `C:\Program Files\WindowsPowerShell\Modules\PowerShellGet` - - C:\Program Files\WindowsPowerShell\Modules\PowerShellGet +4. From an elevated Windows PowerShell window on the target computer, run the following command: -5. From an elevated Windows PowerShell window, run the following command: + ```powershell + Set-PSRepository -Name PSGallery -InstallationPolicy Trusted + ``` - ``` - Set-PSRepository -Name PSGallery -InstallationPolicy Trusted - ``` +5. Now you can finally install platyPS on the target computer by running the usual command: -6. Now you can finally install platyPS by running the following command: - - ``` - Install-Module -Name platyPS -Scope CurrentUser - ``` + ```powershell + Install-Module -Name platyPS -Scope CurrentUser + ``` diff --git a/repo_docs/UPDATE_CMDLETS.md b/repo_docs/UPDATE_CMDLETS.md index 2ba9667c41..0f89ae5ffa 100644 --- a/repo_docs/UPDATE_CMDLETS.md +++ b/repo_docs/UPDATE_CMDLETS.md @@ -1,7 +1,8 @@ # Update existing cmdlet topics + Manually adding new parameters to a cmdlet reference topic is doable, but there are several obstacles to overcome: -- **Add the paramter and Type value to the SYNTAX block(s)**: Easy to do if there's only one, but what if there are multiple SYNTAX blocks (also known as parameter sets)? Does the new parameter go in one, some, or all of them? And what about the parameter Type value (String? `$true | $ false`? A finite list of values?) +- **Add the parameter and Type value to the SYNTAX block(s)**: Easy to do if there's only one, but what if there are multiple SYNTAX blocks (also known as parameter sets)? Does the new parameter go in one, some, or all of them? And what about the parameter Type value (String? `$true | $ false`? A finite list of values?) - **Create a new section for each parameter**: It's easy to create the section and write the description, but again, what about the parameter Type value? And which parameter sets does it belong to? @@ -20,127 +21,119 @@ Removing parameters from topics is a manual exercise, but we'll explain the proc ## Use platyPS to add new cmdlets to existing topics ### Step 1: Install platyPS + The steps are the same as [Create new cmdlet topics](NEW_CMDLETS.md#step-1-install-platyps). ### Step 2: Connect to the PowerShell environment that has the cmdlet + You probably know how to do this already, but the available workloads and connection methods are also described in [Create new cmdlet topics](NEW_CMDLETS.md#step-2-connect-to-the-powershell-environment-that-has-the-cmdlet). +> [!NOTE] +> Remote PowerShell connections are deprecated in Exchange Online PowerShell and Security & Compliance PowerShell in favor of REST API connections. For more information, see the following articles: +> +> - [REST API connections in the EXO V3 module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2#rest-api-connections-in-the-exo-v3-module). +> - [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). +> - [Deprecation of Remote PowerShell (RPS) Protocol in Security & Compliance PowerShell](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432). +> +> REST API connections in the Exchange Online PowerShell V3 module incorrectly identify many parameter **Type** values as `Object` or `Object[]`. The true parameter type values are visible in product code. + ### Step 3: Load platyPS in the PowerShell environment + After you've connected in PowerShell to the server or service (either in a regular Windows PowerShell window or from a specific PowerShell console shortcut), run the following command to make the platyPS cmdlets available in your session: ```powershell Import-Module platyPS ``` -### Step 4: Verify your PSSession variable name -This step is the same as in [Create new cmdlet topics](NEW_CMDLETS.md#step-5-verify-your-your-pssession-variable-name). - -To recap: this step is required in Exchange, Skype for Business Online and other products that use remote PowerShell in their connection instructions (one or more **xxx-xxxSession** commands are present), and the value is most likely `$Session`. +### Step 4: Use New-MarkdownHelp to dump the latest version of the cmdlet to a file -If you're using SharePoint, SharePoint Online or another product that doesn't use remote PowerShell to connect, you can skip this step. - -### Step 5: Use New-MarkdownHelp to dump the latest version of the cmdlet to a file These instructions are the same (up to a point) as in [Create new cmdlet topics](NEW_CMDLETS.md): The basic syntax is: - ```powershell - New-MarkdownHelp -Command <Cmdlet> -OutputFolder "<Path"> [-Session <PSSessionVariableName>] - ``` +```powershell +New-MarkdownHelp -Command <Cmdlet> -OutputFolder "<Path"> +``` + +or + +```powershell +$x = "<Cmdlet1>","<Cmdlet2>",..."<CmdletN>" - or - - ```powershell - $x = "<Cmdlet1>","<Cmdlet2>",..."<CmdletN>" - New-MarkdownHelp -Command $x -OutputFolder "<Path"> [-Session <PSSessionVariableName>] - ``` +New-MarkdownHelp -Command $x -OutputFolder "<Path"> +``` - This example create a topic file for the updated cmdlet named Get-CoolFeature in the Exchange Online PowerShell session where the session variable is `$Session` in the folder "C:\My Docs\ExO". +This example create a topic file for the updated cmdlet named **Get-CoolFeature** in the Exchange Online PowerShell session in the folder "C:\My Docs\ExO". ```powershell -New-MarkdownHelp -Command "Get-CoolFeature" -OutputFolder "C:\My Docs\ExO" -Session $Session +New-MarkdownHelp -Command "Get-CoolFeature" -OutputFolder "C:\My Docs\ExO" ``` -This example creates topic files for the updated cmdlets Get-CoolFeature, New-CoolFeature, Remove-CoolFeature, and Set-CoolFeature from the Exchange Online session where the session variable is `$Session` in the folder C:\My Docs\ExO. +This example creates topic files for the updated cmdlets **Get-CoolFeature**, **New-CoolFeature**, **Remove-CoolFeature**, and **Set-CoolFeature** from the Exchange Online session in the folder C:\My Docs\ExO. The first command stores the cmdlet names in a variable. The second command uses that variable to identify the cmdlets and write the output files. ```powershell $Delta = "Get-CoolFeature","New-CoolFeature","Remove-CoolFeature","Set-CoolFeature" -``` -```powershell -New-MarkdownHelp -Command $Delta -OutputFolder "C:\My Docs\ExO" -Session $Session +New-MarkdownHelp -Command $Delta -OutputFolder "C:\My Docs\ExO" ``` -### Step 6: Document the new parameters +### Step 5: Document the new parameters + The resulting topics are plain text UTF-8 files that are formatted using [markdown](https://guides.github.com/features/mastering-markdown/). Office writers use [Visual Studio Code](https://code.visualstudio.com/) to edit topic files, but you can use Notepad or your favorite text editor. 1. Find the new parameter(s) in the SYNTAX block and the parameter sections. -2. Add a parameter description. We highly encourage you to plagiarize existing content and formatting from other cmdlet topics. Many parameters are common across a wide variety of cmdlets. - -3. Create/fill out the parameter metadata like other existing parameters in the topic. - - Here's an example of the parameter metadata that's present in every parameter section: - - ```yaml - Type: String - Parameter Sets: (All) - Aliases: - Applicable: Microsoft StaffHub - Required: False - Position: 1 - Default value: None - Accept pipeline input: False - Accept wildcard characters: False - ``` - - Most of the attributes and values are generated automatically by platyPS. The ones that require manual intervention are: +2. Add a parameter description. We highly encourage you to plagiarize existing content and formatting from other cmdlet topics. Many parameters are common across a wide variety of cmdlets. - - **Applicable**: You need to add this attribute and value yourself. Notice the capital 'A'. See other topics for available values (same available values as the **applicable** attribute at the top of the topic). Don't invent new values here. The value **must** come from the list of predefined values. - - - **Default value** and **Accept wildcard characters**: These attributes are present, but the values are never truthfully populated by platyPS (they're always None and False, respectively). You can correct the values if you think it's important. Otherwise, leave them as is. - -### Step 7: Copy your changes into the existing topic on GitHub -At this point, the steps are basically identical to [Short URL: aka.ms/office-powershell](../README.md): - -1. Go to the cmdlet topics location in the appropriate GiHub repository: +3. Create/fill out the parameter metadata like other existing parameters in the topic. - - Exchange: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange) + Here's an example of the parameter metadata that's present in every parameter section: - For Exchange, you also need to go one level deeper into an appropriate subfolder. + ```yaml + Type: String + Parameter Sets: (All) + Aliases: + Applicable: Microsoft StaffHub - - Office Web Apps: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps) + Required: False + Position: 1 + Default value: None + Accept pipeline input: False + Accept wildcard characters: False + ``` - - SharePoint Online: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-online](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-online) + Most of the attributes and values are generated automatically by platyPS. The ones that require manual intervention are: - - SharePoint PNP: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-pnp](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-pnp) + - **Type**: In any environment, the values `Object` or `Object[]` are wrong. As previously described, REST API connections in the Exchange Online PowerShell V3 module incorrectly identify many parameter **Type** values as `Object` or `Object[]`. Other values like `String`, `Boolean`, and `DateTime` are detected correctly. The true parameter type values are visible in product code. - - SharePoint Server: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-server](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/sharepoint/sharepoint-ps/sharepoint-server) + - **Applicable**: You need to add this attribute and value yourself. Notice the capital 'A'. See other topics for available values (same available values as the **applicable** attribute at the top of the topic). Don't invent new values here. The value **must** come from the list of predefined values. - - Skype: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/skype/skype-ps/skype](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/skype/skype-ps/skype) + - **Default value** and **Accept wildcard characters**: These attributes are present, but the values are never truthfully populated by platyPS **or any other PowerShell utility** (they're always None and False, respectively). You can correct the values if you think it's important. Otherwise, leave them as is. - - StaffHub: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/staffhub/staffhub-ps/staffhub](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/staffhub/staffhub-ps/staffhub) +### Step 6: Copy your changes into the existing topic on GitHub - - Teams: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/teams/teams-ps/teams](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/teams/teams-ps/teams) +1. Go to the cmdlet topics location in the appropriate GiHub repository: - - Whiteboard: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/whiteboard/whiteboard-ps/whiteboard](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/whiteboard/whiteboard-ps/whiteboard) + - Exchange: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange> + - Office Web Apps: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps> + - Skype: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/skype/skype-ps/skype> + - StaffHub: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/staffhub/staffhub-ps/staffhub> + - Teams: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/teams/teams-ps/teams> + - Whiteboard: <https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/whiteboard/whiteboard-ps/whiteboard> -2. Find the topic and click **Edit** +2. Find the existing topic and click **Edit**. 3. Copy/paste your updates (and only your updates) from your new, local copy of the topic into the existing topic (click the **Preview** tab to see what they'll look like). - **IMPORTANT**: The layout of headings and subheadings must follow a very specific schema that is required for PowerShell Get-Help. - Any deviation will throw errors in the Pull Request. The schema can be found here: https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md - -4. Once you're satisfied with your work, go to the **Propose file change** area at the bottom of the topic. Enter a title and other description information and then click **Propose file change**. - - ![Image of Propose file change on Github](../images/propose_file_change.png) + > [!IMPORTANT] + > The layout of headings and subheadings must follow a very specific schema that is required for PowerShell Get-Help. Any deviation will throw errors in the Pull Request. The schema can be found here: <https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md>. -7. On the next screen, click **Create pull request**. +4. At this point, the steps are identical to [Short URL: aka.ms/office-powershell](../README.md) (You're starting at Step 4). ## Remove existing parameters from existing topics + Removing parameters is a search and destroy mission in the existing topics on GitHub, using the basic [Editing Instructions](../README.md). The most important thing to remember: a parameter isn't gone until it's truly not available to customers. If a parameter is still available, but it's going away "in the future", it doesn't work correctly anymore, or isn't supposed to be available, it needs to remain in the topic until the product code is actually changed to remove the parameter. Until then, you can use this type of language for the parameter description: @@ -154,7 +147,5 @@ Hear me now, believe me later: Removing available parameters from a cmdlet refer After you've confirmed that the parameter in question is really gone, find and remove all references to the parameter in the topic: - The SYNTAX block(s) - - Examples - - The individual parameter sections where each parameter is described. Be sure to delete the whole section including the \`\`\`yaml part at the end (don't leave trailing \`\`\`, which is easy to do). diff --git a/sharepoint/docfx.json b/sharepoint/docfx.json deleted file mode 100644 index 487256f53d..0000000000 --- a/sharepoint/docfx.json +++ /dev/null @@ -1,77 +0,0 @@ -{ - "build": { - "content": [ - { - "files": ["**/*.md","**/**.yml"], - "src": "docs-conceptual", - "version": "sharepoint-ps", - "dest": "sharepoint", - "exclude": [ - "**/obj/**", - "**/includes/**", - "README.md", - "LICENSE", - "LICENSE-CODE", - "ThirdPartyNotices"] - }, - { - "files": ["toc.yml"], - "src": "docs-conceptual", - "version": "sharepoint-ps", - "dest": "sharepoint/sharepoint-ps" - }, - { - "files": ["**/*.md"], - "src": "sharepoint-ps", - "version": "sharepoint-ps", - "dest": "module" - }, - { - "files": ["toc.yml"], - "src": "sharepoint-ps", - "version": "sharepoint-ps", - "dest": "module/sharepoint-ps" - } - ], - "resource": [ - { - "files": [ - "**/*.png", - "**/*.jpg" - ], - "exclude": [ - "**/obj/**", - "**/includes/**" - ] - } - ], - "versions": { - "sharepoint-ps": { - "dest": "sharepoint-ps" - } - }, - "overwrite": [], - "externalReference": [], - "globalMetadata": { - "author" : "techwriter40", - "ms.author" : "kirks", - "manager" : "pamgreen", - "ms.date" : "11/28/2017", - "ms.topic" : "reference", - "ms.devlang" : "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" - }, - "fileMetadata": { - "ms.service":{ - "sharepoint-ps/sharepoint-online/*.md":"sharepoint-powershell" - }, - "ms.prod":{ - "sharepoint-ps/sharepoint-server/*.md":"sharepoint-powershell" - } - }, - "template": [], - "dest": "sharepoint-ps" - } -} diff --git a/sharepoint/docs-conceptual/index.yml b/sharepoint/docs-conceptual/index.yml deleted file mode 100644 index 88d95e6b1f..0000000000 --- a/sharepoint/docs-conceptual/index.yml +++ /dev/null @@ -1,73 +0,0 @@ -### YamlMime:Landing - -title: SharePoint PowerShell # < 60 chars -summary: Learn about using PowerShell cmdlets for SharePoint in Microsoft 365 and SharePoint Server. # < 160 chars - -metadata: - title: SharePoint PowerShell # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Use PowerShell cmdlets for SharePoint in Microsoft 365 and SharePoint Server # Required; article description that is displayed in search results. < 160 chars. - ms.service: sharepoint-online #Required; service per approved list. service slug assigned to your service by ACOM. - ms.subservice: subservice - ms.topic: landing-page # Required - ms.collection: M365-collaboration - author: kaarins #Required; your GitHub user alias, with correct capitalization. - ms.author: kaarins #Required; microsoft alias of author; optional team alias. - ms.date: 03/16/2020 #Required; mm/dd/yyyy format - localization_priority: Priority - -# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new - -landingContent: -# Cards and links should be based on top customer tasks or top subjects -# Start card title with a verb - # Card (optional) - - title: SharePoint in Microsoft 365 - linkLists: - - linkListType: reference - links: - - text: Intro to SharePoint Online Management Shell - url: sharepoint-online/introduction-sharepoint-online-management-shell.md - - text: Get started with SharePoint Online Management Shell - url: sharepoint-online/connect-sharepoint-online.md - - text: Cmdlet reference - url: /powershell/module/sharepoint-online - - text: Manage SharePoint with Office 365 PowerShell - url: /office365/enterprise/powershell/manage-sharepoint-online-with-office-365-powershell - - - # Card - - title: SharePoint Server - linkLists: - - linkListType: reference - links: - - text: Overview - url: /powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets - - text: Cmdlet reference - url: /powershell/module/sharepoint-server - - # Card - - title: SharePoint Patterns and Practices (PnP) - linkLists: - - linkListType: reference - links: - - text: Overview - url: /powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets - - text: Cmdlet reference - url: /powershell/module/sharepoint-pnp - - text: PowerShell Gallery - url: https://www.powershellgallery.com/ - - # Card - - title: Learning PowerShell - linkLists: - - linkListType: learn - links: - - text: PowerShell documentation - url: /powershell - - text: Overview - url: /powershell/scripting/overview - - text: More resources for learning PowerShell - url: /powershell/scripting/learn/more-powershell-learning - - - \ No newline at end of file diff --git a/sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md b/sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md deleted file mode 100644 index 949d5baef8..0000000000 --- a/sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Get started with the SharePoint Online Management Shell ---- - -# Get started with SharePoint Online Management Shell # - -To get started using PowerShell to manage SharePoint Online, you need to install the latest SharePoint Online Management Shell is installed and connect to SharePoint Online. - -Install the SharePoint Online Management Shell by downloading and running the [SharePoint Online Management Shell](https://go.microsoft.com/fwlink/p/?LinkId=255251) or installing the module from the [PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.Online.SharePoint.PowerShell/). Once installed, the module is available for use, and you do not need to install it again until you need features introduced in a later version. For example, you may need to install a new version for TLS 1.2 negotiation after October 2018. - -First you can check if you have already installed SharePoint Online Management Shell by running the following command in administrative mode in PowerShell. - -```ps -Get-Module -Name Microsoft.Online.SharePoint.PowerShell -ListAvailable | Select Name,Version -``` - -If your operating system is using PowerShell 5 or newer, you can install the SharePoint Online Management Shell also by running the following command in administrative mode. - -```ps -Install-Module -Name Microsoft.Online.SharePoint.PowerShell -``` - -To open the SharePoint Online Management Shell command prompt, from the **Start** screen, type **sharepoint**, and then click **SharePoint Online Management Shell**. - -<br /> - -> [!Video https://www.youtube.com/embed/TMzHAWEQjlk] - -## To connect with a user name and password ## - -1. Fill in the values for the **$adminUPN** and **$orgName** variables (replacing all the text between the quotes, including the < and > characters), and then run the following commands at the SharePoint Online Management Shell command prompt: - -``` -$adminUPN="<the full email address of a SharePoint administrator account, example: jdoe@contosotoycompany.onmicrosoft.com>" -$orgName="<name of your Office 365 organization, example: contosotoycompany>" -$userCredential = Get-Credential -UserName $adminUPN -Message "Type the password." -Connect-SPOService -Url https://$orgName-admin.sharepoint.com -Credential $userCredential - -``` - -2. When prompted with the Windows PowerShell credential request dialog box, type the password for the SharePoint admin account. - -To assign a user the SharePoint admin role, see [Assign admin roles](/microsoft-365/admin/add-users/assign-admin-roles) or [Assign roles to user accounts with Office 365 PowerShell](/office365/enterprise/powershell/assign-roles-to-user-accounts-with-office-365-powershell). - -## To connect with multifactor authentication (MFA) ## - -1. Fill in the value for the **$orgName** variable (replacing all the text between the quotes, including the < and > characters), and then run the following commands at the SharePoint Online Management Shell command prompt: - -``` -$orgName="<name of your Office 365 organization, example: contosotoycompany>" -Connect-SPOService -Url https://$orgName-admin.sharepoint.com -``` -2. When prompted with the **Microsoft SharePoint Online Management Shell** dialog box, type the account name and password for a SharePoint administrator account, and then click **Sign in**. - -3. Follow the instructions in the **Microsoft SharePoint Online Management Shell** dialog box to provide the additional authentication information, such as a verification code, and then click **Sign in**. - -You are now ready to use SharePoint Online commands. - -> [!NOTE] -> If you encounter issues trying to connect using MFA, please see [Cannot force Modern Authentication when using Connect-SPOService cmdlet in SharePoint Online Management Shell](/sharepoint/troubleshoot/security/cannot-force-modern-authentication) diff --git a/sharepoint/docs-conceptual/sharepoint-online/introduction-sharepoint-online-management-shell.md b/sharepoint/docs-conceptual/sharepoint-online/introduction-sharepoint-online-management-shell.md deleted file mode 100644 index 8bf991d822..0000000000 --- a/sharepoint/docs-conceptual/sharepoint-online/introduction-sharepoint-online-management-shell.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Intro to SharePoint Online Management Shell ---- - -# Intro to SharePoint Online Management Shell - -The SharePoint Online Management Shell is a Windows PowerShell module that you can use to manage SharePoint settings at the organization level and site collection level. Command-line operations in Windows PowerShell are composed of a series of commands. Each command uses a cmdlet and a set of settings known as parameters. For example, you use the **New-SPOSite** cmdlet to create a new site collection with a specified title, URL, owner, storage quota, and template (the parameters). - -SharePoint Online PowerShell commands can be very efficient for batch operations — for example, creating a dozen new site collections or adding hundreds of new users to a site. For more information, see [Why you need to use Office 365 PowerShell](/office365/enterprise/powershell/why-you-need-to-use-office-365-powershell). - -## Getting Started with SharePoint Online PowerShell - -To use SharePoint Online PowerShell commands, you must have the SharePoint Admin role or Global Administrator role in Office 365. - -You must install the SharePoint Online Management Shell module and connect to the SharePoint Online service. For more information, see [Connect SharePoint Online](connect-sharepoint-online.md). - -## What's the difference between SharePoint Online PowerShell commands and Office 365 PowerShell commands? - -The major and obvious difference is the nouns they use. Every SharePoint Online cmdlet will start with SPO as its noun. Conversely, Office 365 will start with MSO as its noun. - -SharePoint Online Management Shell commands manage SharePoint settings and site collections, whereas Office 365 commands manage Office 365-level tasks such as users, licenses, organization information, and services. They both manage users and groups. However, Office 365 PowerShell commands manage users and groups for all of the Office 365 services. The SharePoint Online commands manage users and groups only for SharePoint Online. - -## Should I use the SharePoint admin center or SharePoint Online PowerShell commands? - -If you are new to Office 365 and SharePoint Online and you have not done much managing of SharePoint sites or users, the SharePoint admin center is a good place to start. - -After you get familiar with SharePoint sites and users, try using SharePoint Online PowerShell commands, especially when you want to manage lots of site collections or users. - -> [!NOTE] -> For the complete list of SharePoint Online cmdlets, see [SharePoint Online PowerShell](https://docs.microsoft.com/powershell/module/sharepoint-online/?view=sharepoint-ps) - -## How do I get permissions and set up the environment? - -To use SharePoint Online PowerShell commands, you must be a SharePoint admin in your organization. For info about installing the SharePoint Online Management Shell module and connecting to the SharePoint Online service, see [Get started with SharePoint Online Management Shell](connect-sharepoint-online.md) diff --git a/sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md b/sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md deleted file mode 100644 index 57095843e1..0000000000 --- a/sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md +++ /dev/null @@ -1,659 +0,0 @@ ---- -title: PnP PowerShell Overview ---- - -# PnP PowerShell overview - -SharePoint Patterns and Practices (PnP) contains a library of PowerShell commands (PnP PowerShell) that allows you to perform complex provisioning and artifact management actions towards SharePoint. The commands use CSOM and can work against both SharePoint Online as SharePoint On-Premises. - -![SharePoint Patterns and Practices](https://devofficecdn.azureedge.net/media/Default/PnP/sppnp.png) - -_**Applies to:** SharePoint Online | SharePoint 2016 | SharePoint 2013_ - -## Installation # - -There are 3 ways to install the cmdlets. We recommend, where possible, to install them from the [PowerShell Gallery](https://www.powershellgallery.com). Alternatively you can download the setup files or run a PowerShell script to download the PowerShellGet module and install the cmdlets subsequently. - -### PowerShell Gallery ### -If you main OS is Windows 10, or if you have [PowerShellGet](https://github.com/powershell/powershellget) installed, you can run the following commands to install the PowerShell cmdlets: - -|**SharePoint Version**|**Command to install**| -|------------------|------------------| -|SharePoint Online|```Install-Module SharePointPnPPowerShellOnline ```| -|SharePoint 2016|```Install-Module SharePointPnPPowerShell2016```| -|SharePoint 2013|```Install-Module SharePointPnPPowerShell2013```| - -*Notice*: if you install the latest PowerShellGet from Github, you might receive an error message stating ->PackageManagement\Install-Package : The version 'x.x.x.x' of the module 'SharePointPnPPowerShellOnline' being installed is not catalog signed. - -In order to install the cmdlets when you get this error specify the -SkipPublisherCheck switch with the Install-Module cmdlet, e.g. ```Install-Module SharePointPnPPowerShellOnline -SkipPublisherCheck -AllowClobber``` - -### Setup files ## -You can download setup files from the [releases](https://github.com/sharepoint/pnp-powershell/releases) section of the PnP PowerShell repository. These files will up be updated on a monthly basis. Run the install and restart any open instances of PowerShell to use the cmdlets. - -### Installation script ## -This is an alternative for installation on machines that have at least PowerShell v3 installed. You can find the version of PowerShell by opening PowerShell and running ```$PSVersionTable.PSVersion```. The value for ```Major``` should be above 3. - -To install the cmdlets you can run the below command which will install PowerShell Package Management and then install the PowerShell Modules from the PowerShell Gallery. - -```powershell -Invoke-Expression (New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/sharepoint/PnP-PowerShell/master/Samples/Modules.Install/Install-SharePointPnPPowerShell.ps1') -``` - -## Updating ## -Every month a new release will be made available of the PnP PowerShell Cmdlets. If you earlier installed the cmdlets using the setup file, simply download the [latest version](https://github.com/SharePoint/PnP-PowerShell/releases/latest) and run the setup. This will update your existing installation. - -If you have installed the cmdlets using PowerShellGet with ```Install-Module``` from the PowerShell Gallery then you will be able to use the following command to install the latest updated version: - -```powershell -Update-Module SharePointPnPPowerShell* -``` - -This will automatically load the module after starting PowerShell 3.0. - -You can check the installed PnP-PowerShell versions with the following command: - -```powershell -Get-Module SharePointPnPPowerShell* -ListAvailable | Select-Object Name,Version | Sort-Object Version -Descending -``` - -## Getting Started # - -To use the library you first need to connect to your tenant: - -```powershell -Connect-PnPOnline –Url https://yoursite.sharepoint.com –Credentials (Get-Credential) -``` - -Notice: if you use multi-factor authentication on your tenant, use - -```powershell -Connect-PnPOnline -Url https://yoursite.sharepoint.com -UseWebLogin -``` - -To view all cmdlets, enter - -```powershell -Get-Command -Module *PnP* -``` - -At the following links you will find a few videos on how to get started with the cmdlets: - -* https://channel9.msdn.com/blogs/OfficeDevPnP/PnP-Web-Cast-Introduction-to-Office-365-PnP-PowerShell -* https://channel9.msdn.com/blogs/OfficeDevPnP/Introduction-to-PnP-PowerShell-Cmdlets -* https://channel9.msdn.com/blogs/OfficeDevPnP/PnP-Webcast-PnP-PowerShell-Getting-started-with-latest-updates - -### Setting up credentials ## -See this [wiki page](https://github.com/SharePoint/PnP-PowerShell/wiki/How-to-use-the-Windows-Credential-Manager-to-ease-authentication-with-PnP-PowerShell) for more information on how to use the Windows Credential Manager to setup credentials that you can use in unattended scripts - -## Cmdlet overview - - -### Apps -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Add-PnPApp.md)** |Add/uploads an available app to the app catalog|SharePoint Online, SharePoint 2019 -**[Get‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Get-PnPApp.md)** |Returns the available apps from the app catalog|SharePoint Online, SharePoint 2019 -**[Install‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Install-PnPApp.md)** |Installs an available app from the app catalog|SharePoint Online, SharePoint 2019 -**[Publish‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Publish-PnPApp.md)** |Publishes/Deploys/Trusts an available app in the app catalog|SharePoint Online, SharePoint 2019 -**[Remove‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Remove-PnPApp.md)** |Removes an app from the app catalog|SharePoint Online, SharePoint 2019 -**[Uninstall‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Uninstall-PnPApp.md)** |Uninstalls an available add-in from the site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Unpublish‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Unpublish-PnPApp.md)** |Unpublishes/retracts an available add-in from the app catalog|SharePoint Online, SharePoint 2019 -**[Update‑PnPApp](../../sharepoint-ps/sharepoint-pnp/Update-PnPApp.md)** |Updates an available app from the app catalog|SharePoint Online, SharePoint 2019 -**[Get‑PnPAppInstance](../../sharepoint-ps/sharepoint-pnp/Get-PnPAppInstance.md)** |Returns a SharePoint AddIn Instance|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Uninstall‑PnPAppInstance](../../sharepoint-ps/sharepoint-pnp/Uninstall-PnPAppInstance.md)** |Removes an app from a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPApplicationCustomizer](../../sharepoint-ps/sharepoint-pnp/Add-PnPApplicationCustomizer.md)** |Adds a SharePoint Framework client side extension application customizer|SharePoint Online, SharePoint 2019 -**[Get‑PnPApplicationCustomizer](../../sharepoint-ps/sharepoint-pnp/Get-PnPApplicationCustomizer.md)** |Returns all SharePoint Framework client side extension application customizers|SharePoint Online, SharePoint 2019 -**[Remove‑PnPApplicationCustomizer](../../sharepoint-ps/sharepoint-pnp/Remove-PnPApplicationCustomizer.md)** |Removes a SharePoint Framework client side extension application customizer|SharePoint Online, SharePoint 2019 -**[Set‑PnPApplicationCustomizer](../../sharepoint-ps/sharepoint-pnp/Set-PnPApplicationCustomizer.md)** |Updates a SharePoint Framework client side extension application customizer|SharePoint Online, SharePoint 2019 -**[Import‑PnPAppPackage](../../sharepoint-ps/sharepoint-pnp/Import-PnPAppPackage.md)** |Adds a SharePoint Addin to a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Sync‑PnPAppToTeams](../../sharepoint-ps/sharepoint-pnp/Sync-PnPAppToTeams.md)** |Synchronize an app from the tenant app catalog to the Microsoft Teams app catalog|SharePoint Online -**[Grant‑PnPTenantServicePrincipalPermission](../../sharepoint-ps/sharepoint-pnp/Grant-PnPTenantServicePrincipalPermission.md)** |Explicitly grants a specified permission to the "SharePoint Online Client" service principal|SharePoint Online - - -### Base Cmdlets -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Request‑PnPAccessToken](../../sharepoint-ps/sharepoint-pnp/Request-PnPAccessToken.md)** |Requests an OAuth Access token|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPAppAuthAccessToken](../../sharepoint-ps/sharepoint-pnp/Get-PnPAppAuthAccessToken.md)** |Returns the access token|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPAuthenticationRealm](../../sharepoint-ps/sharepoint-pnp/Get-PnPAuthenticationRealm.md)** |Returns the authentication realm|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPAzureCertificate](../../sharepoint-ps/sharepoint-pnp/Get-PnPAzureCertificate.md)** |Get PEM values and manifest settings for an existing certificate (.pfx) for use when using CSOM via an app-only ADAL application. See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/SharePoint.ConnectUsingAppPermissions for a sample on how to get started. KeyCredentials contains the ADAL app manifest sections. Certificate contains the PEM encoded certificate. PrivateKey contains the PEM encoded private key of the certificate.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPAzureCertificate](../../sharepoint-ps/sharepoint-pnp/New-PnPAzureCertificate.md)** |Generate a new 2048bit self-signed certificate and manifest settings for use when using CSOM via an app-only ADAL application. See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/SharePoint.ConnectUsingAppPermissions for a sample on how to get started. KeyCredentials contains the ADAL app manifest sections. Certificate contains the PEM encoded certificate. PrivateKey contains the PEM encoded private key of the certificate.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPConnection](../../sharepoint-ps/sharepoint-pnp/Get-PnPConnection.md)** |Returns the current context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPContext](../../sharepoint-ps/sharepoint-pnp/Get-PnPContext.md)** |Returns the current context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPContext](../../sharepoint-ps/sharepoint-pnp/Set-PnPContext.md)** |Set the ClientContext|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPException](../../sharepoint-ps/sharepoint-pnp/Get-PnPException.md)** |Returns the last exception that occurred|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPHealthScore](../../sharepoint-ps/sharepoint-pnp/Get-PnPHealthScore.md)** |Retrieves the healthscore of the site given in his Url parameter or from the current connection if the Url parameter is not provided|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -**[Connect‑PnPOnline](../../sharepoint-ps/sharepoint-pnp/Connect-PnPOnline.md)** |Connect to a SharePoint site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Disconnect‑PnPOnline](../../sharepoint-ps/sharepoint-pnp/Disconnect-PnPOnline.md)** |Disconnects the context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPProperty](../../sharepoint-ps/sharepoint-pnp/Get-PnPProperty.md)** |Returns a previously not loaded property of a ClientObject|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Invoke‑PnPQuery](../../sharepoint-ps/sharepoint-pnp/Invoke-PnPQuery.md)** |Executes the currently queued actions|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Invoke‑PnPSPRestMethod](../../sharepoint-ps/sharepoint-pnp/Invoke-PnPSPRestMethod.md)** |Invokes a REST request towards a SharePoint site|SharePoint Online -**[Add‑PnPStoredCredential](../../sharepoint-ps/sharepoint-pnp/Add-PnPStoredCredential.md)** |Adds a credential to the Windows Credential Manager|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPStoredCredential](../../sharepoint-ps/sharepoint-pnp/Get-PnPStoredCredential.md)** |Get a credential|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPStoredCredential](../../sharepoint-ps/sharepoint-pnp/Remove-PnPStoredCredential.md)** |Removes a credential|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPTraceLog](../../sharepoint-ps/sharepoint-pnp/Set-PnPTraceLog.md)** |Turn log tracing on or off|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Branding -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPCustomAction](../../sharepoint-ps/sharepoint-pnp/Add-PnPCustomAction.md)** |Adds a custom action|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPCustomAction](../../sharepoint-ps/sharepoint-pnp/Get-PnPCustomAction.md)** |Return user custom actions|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPCustomAction](../../sharepoint-ps/sharepoint-pnp/Remove-PnPCustomAction.md)** |Removes a custom action|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPHomePage](../../sharepoint-ps/sharepoint-pnp/Get-PnPHomePage.md)** |Return the homepage|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPHomePage](../../sharepoint-ps/sharepoint-pnp/Set-PnPHomePage.md)** |Sets the home page of the current web.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPJavaScriptBlock](../../sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptBlock.md)** |Adds a link to a JavaScript snippet/block to a web or site collection|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPJavaScriptLink](../../sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptLink.md)** |Adds a link to a JavaScript file to a web or sitecollection, valid only for SharePoint classic site experience.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPJavaScriptLink](../../sharepoint-ps/sharepoint-pnp/Get-PnPJavaScriptLink.md)** |Returns all or a specific custom action(s) with location type ScriptLink|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPJavaScriptLink](../../sharepoint-ps/sharepoint-pnp/Remove-PnPJavaScriptLink.md)** |Removes a JavaScript link or block from a web or sitecollection|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPMasterPage](../../sharepoint-ps/sharepoint-pnp/Get-PnPMasterPage.md)** |Returns the URLs of the default Master Page and the custom Master Page.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPMasterPage](../../sharepoint-ps/sharepoint-pnp/Set-PnPMasterPage.md)** |Set the masterpage|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPMinimalDownloadStrategy](../../sharepoint-ps/sharepoint-pnp/Set-PnPMinimalDownloadStrategy.md)** |Activates or deactivates the minimal downloading strategy.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPNavigationNode](../../sharepoint-ps/sharepoint-pnp/Add-PnPNavigationNode.md)** |Adds an item to a navigation element|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPNavigationNode](../../sharepoint-ps/sharepoint-pnp/Get-PnPNavigationNode.md)** |Returns all or a specific navigation node|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPNavigationNode](../../sharepoint-ps/sharepoint-pnp/Remove-PnPNavigationNode.md)** |Removes a menu item from either the quicklaunch or top navigation|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Disable‑PnPResponsiveUI](../../sharepoint-ps/sharepoint-pnp/Disable-PnPResponsiveUI.md)** |Deactivate the PnP Response UI add-on|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Enable‑PnPResponsiveUI](../../sharepoint-ps/sharepoint-pnp/Enable-PnPResponsiveUI.md)** |Activates the PnP Response UI Add-on|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPTheme](../../sharepoint-ps/sharepoint-pnp/Get-PnPTheme.md)** |Returns the current theme/composed look of the current web.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPTheme](../../sharepoint-ps/sharepoint-pnp/Set-PnPTheme.md)** |Sets the theme of the current web.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPWebTheme](../../sharepoint-ps/sharepoint-pnp/Set-PnPWebTheme.md)** |Sets the theme of the current web.|SharePoint Online - - -### Client-Side Pages -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPAvailableClientSideComponents](../../sharepoint-ps/sharepoint-pnp/Get-PnPAvailableClientSideComponents.md)** |Gets the available client side components on a particular page|SharePoint Online, SharePoint 2019 -**[Move‑PnPClientSideComponent](../../sharepoint-ps/sharepoint-pnp/Move-PnPClientSideComponent.md)** |Moves a Client-Side Component to a different section/column|SharePoint Online, SharePoint 2019 -**[Add‑PnPClientSidePage](../../sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePage.md)** |Adds a Client-Side Page|SharePoint Online, SharePoint 2019 -**[ConvertTo‑PnPClientSidePage](../../sharepoint-ps/sharepoint-pnp/ConvertTo-PnPClientSidePage.md)** |Converts a classic page (wiki or web part page) into a Client-Side Page|SharePoint Online -**[Get‑PnPClientSidePage](../../sharepoint-ps/sharepoint-pnp/Get-PnPClientSidePage.md)** |Gets a modern site page|SharePoint Online, SharePoint 2019 -**[Remove‑PnPClientSidePage](../../sharepoint-ps/sharepoint-pnp/Remove-PnPClientSidePage.md)** |Removes a Client-Side Page|SharePoint Online, SharePoint 2019 -**[Set‑PnPClientSidePage](../../sharepoint-ps/sharepoint-pnp/Set-PnPClientSidePage.md)** |Sets parameters of a Client-Side Page|SharePoint Online, SharePoint 2019 -**[Save‑PnPClientSidePageConversionLog](../../sharepoint-ps/sharepoint-pnp/Save-PnPClientSidePageConversionLog.md)** |Persists the current client side page conversion log data to the loggers linked to the last used page transformation run. Needs to be used in conjunction with the -LogSkipFlush flag on the ConvertTo-PnPClientSidePage cmdlet|SharePoint Online -**[Export‑PnPClientSidePageMapping](../../sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePageMapping.md)** |Get's the built-in maping files or a custom mapping file for your publishing portal page layouts. These mapping files are used to tailor the page transformation experience.|SharePoint Online -**[Add‑PnPClientSidePageSection](../../sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePageSection.md)** |Adds a new section to a Client-Side page|SharePoint Online, SharePoint 2019 -**[Add‑PnPClientSideText](../../sharepoint-ps/sharepoint-pnp/Add-PnPClientSideText.md)** |Adds a text element to a client-side page.|SharePoint Online, SharePoint 2019 -**[Add‑PnPClientSideWebPart](../../sharepoint-ps/sharepoint-pnp/Add-PnPClientSideWebPart.md)** |Adds a Client-Side Web Part to a client-side page|SharePoint Online, SharePoint 2019 - - -### Content Types -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPContentType](../../sharepoint-ps/sharepoint-pnp/Add-PnPContentType.md)** |Adds a new content type|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPContentType](../../sharepoint-ps/sharepoint-pnp/Get-PnPContentType.md)** |Retrieves a content type|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPContentType](../../sharepoint-ps/sharepoint-pnp/Remove-PnPContentType.md)** |Removes a content type from a web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPContentTypeFromList](../../sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromList.md)** |Removes a content type from a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPContentTypePublishingHubUrl](../../sharepoint-ps/sharepoint-pnp/Get-PnPContentTypePublishingHubUrl.md)** |Returns the url to Content Type Publishing Hub|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPContentTypeToList](../../sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToList.md)** |Adds a new content type to a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPDefaultContentTypeToList](../../sharepoint-ps/sharepoint-pnp/Set-PnPDefaultContentTypeToList.md)** |Sets the default content type for a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPFieldFromContentType](../../sharepoint-ps/sharepoint-pnp/Remove-PnPFieldFromContentType.md)** |Removes a site column from a content type|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPFieldToContentType](../../sharepoint-ps/sharepoint-pnp/Add-PnPFieldToContentType.md)** |Adds an existing site column to a content type|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Diagnostic utilities -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Measure‑PnPList](../../sharepoint-ps/sharepoint-pnp/Measure-PnPList.md)** |Returns statistics on the list object|SharePoint Online, SharePoint 2016, SharePoint 2019 -**[Measure‑PnPResponseTime](../../sharepoint-ps/sharepoint-pnp/Measure-PnPResponseTime.md)** |Gets statistics on response time for the specified endpoint by sending probe requests|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Measure‑PnPWeb](../../sharepoint-ps/sharepoint-pnp/Measure-PnPWeb.md)** |Returns statistics on the web object|SharePoint Online, SharePoint 2016, SharePoint 2019 - - -### Document Sets -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Remove‑PnPContentTypeFromDocumentSet](../../sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromDocumentSet.md)** |Removes a content type from a document set|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPContentTypeToDocumentSet](../../sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToDocumentSet.md)** |Adds a content type to a document set|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPDocumentSet](../../sharepoint-ps/sharepoint-pnp/Add-PnPDocumentSet.md)** |Creates a new document set in a library.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPDocumentSetField](../../sharepoint-ps/sharepoint-pnp/Set-PnPDocumentSetField.md)** |Sets a site column from the available content types to a document set|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPDocumentSetTemplate](../../sharepoint-ps/sharepoint-pnp/Get-PnPDocumentSetTemplate.md)** |Retrieves a document set template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Event Receivers -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPEventReceiver](../../sharepoint-ps/sharepoint-pnp/Add-PnPEventReceiver.md)** |Adds a new remote event receiver|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPEventReceiver](../../sharepoint-ps/sharepoint-pnp/Get-PnPEventReceiver.md)** |Return registered eventreceivers|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPEventReceiver](../../sharepoint-ps/sharepoint-pnp/Remove-PnPEventReceiver.md)** |Remove an eventreceiver|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Features -Cmdlet|Description|Platform -:-----|:----------|:------- -**[New‑PnPExtensibilityHandlerObject](../../sharepoint-ps/sharepoint-pnp/New-PnPExtensibilityHandlerObject.md)** |Creates an ExtensibilityHandler Object, to be used by the Get-PnPProvisioningTemplate cmdlet|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Disable‑PnPFeature](../../sharepoint-ps/sharepoint-pnp/Disable-PnPFeature.md)** |Disables a feature|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Enable‑PnPFeature](../../sharepoint-ps/sharepoint-pnp/Enable-PnPFeature.md)** |Enables a feature|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPFeature](../../sharepoint-ps/sharepoint-pnp/Get-PnPFeature.md)** |Returns all activated or a specific activated feature|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Fields -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPField](../../sharepoint-ps/sharepoint-pnp/Add-PnPField.md)** |Add a field|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPField](../../sharepoint-ps/sharepoint-pnp/Get-PnPField.md)** |Returns a field from a list or site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPField](../../sharepoint-ps/sharepoint-pnp/Remove-PnPField.md)** |Removes a field from a list or a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPField](../../sharepoint-ps/sharepoint-pnp/Set-PnPField.md)** |Changes one or more properties of a field in a specific list or for the whole web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPFieldFromXml](../../sharepoint-ps/sharepoint-pnp/Add-PnPFieldFromXml.md)** |Adds a field to a list or as a site column based upon a CAML/XML field definition|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPTaxonomyField](../../sharepoint-ps/sharepoint-pnp/Add-PnPTaxonomyField.md)** |Add a taxonomy field|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPView](../../sharepoint-ps/sharepoint-pnp/Set-PnPView.md)** |Change view properties|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Files and Folders -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPFile](../../sharepoint-ps/sharepoint-pnp/Add-PnPFile.md)** |Uploads a file to Web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Copy‑PnPFile](../../sharepoint-ps/sharepoint-pnp/Copy-PnPFile.md)** |Copies a file or folder to a different location, currently there is a 200MB file size limit for the file to be copied.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Find‑PnPFile](../../sharepoint-ps/sharepoint-pnp/Find-PnPFile.md)** |Finds a file in the virtual file system of the web.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPFile](../../sharepoint-ps/sharepoint-pnp/Get-PnPFile.md)** |Downloads a file.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Move‑PnPFile](../../sharepoint-ps/sharepoint-pnp/Move-PnPFile.md)** |Moves a file to a different location|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPFile](../../sharepoint-ps/sharepoint-pnp/Remove-PnPFile.md)** |Removes a file.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Rename‑PnPFile](../../sharepoint-ps/sharepoint-pnp/Rename-PnPFile.md)** |Renames a file in its current location|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPFileCheckedIn](../../sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedIn.md)** |Checks in a file|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPFileCheckedOut](../../sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedOut.md)** |Checks out a file|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Reset‑PnPFileVersion](../../sharepoint-ps/sharepoint-pnp/Reset-PnPFileVersion.md)** |Resets a file to its previous version|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPFolder](../../sharepoint-ps/sharepoint-pnp/Add-PnPFolder.md)** |Creates a folder within a parent folder|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPFolder](../../sharepoint-ps/sharepoint-pnp/Get-PnPFolder.md)** |Return a folder object|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Move‑PnPFolder](../../sharepoint-ps/sharepoint-pnp/Move-PnPFolder.md)** |Move a folder to another location in the current web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPFolder](../../sharepoint-ps/sharepoint-pnp/Remove-PnPFolder.md)** |Deletes a folder within a parent folder|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Rename‑PnPFolder](../../sharepoint-ps/sharepoint-pnp/Rename-PnPFolder.md)** |Renames a folder|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Resolve‑PnPFolder](../../sharepoint-ps/sharepoint-pnp/Resolve-PnPFolder.md)** |Returns a folder from a given site relative path, and will create it if it does not exist.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPFolderItem](../../sharepoint-ps/sharepoint-pnp/Get-PnPFolderItem.md)** |List content in folder|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Copy‑PnPItemProxy](../../sharepoint-ps/sharepoint-pnp/Copy-PnPItemProxy.md)** |Proxy cmdlet for using Copy-Item between SharePoint provider and FileSystem provider|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Move‑PnPItemProxy](../../sharepoint-ps/sharepoint-pnp/Move-PnPItemProxy.md)** |Proxy cmdlet for using Move-Item between SharePoint provider and FileSystem provider|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Information Management -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPLabel](../../sharepoint-ps/sharepoint-pnp/Get-PnPLabel.md)** |Gets the Office 365 retention label/tag of the specified list or library (if applicable)|SharePoint Online -**[Reset‑PnPLabel](../../sharepoint-ps/sharepoint-pnp/Reset-PnPLabel.md)** |Resets a label/tag on the specified list or library to None|SharePoint Online -**[Set‑PnPLabel](../../sharepoint-ps/sharepoint-pnp/Set-PnPLabel.md)** |Sets a label/tag on the specified list or library. Use Reset-PnPLabel to remove the label again.|SharePoint Online -**[Get‑PnPListInformationRightsManagement](../../sharepoint-ps/sharepoint-pnp/Get-PnPListInformationRightsManagement.md)** |Get the site closure status of the site which has a site policy applied|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPListInformationRightsManagement](../../sharepoint-ps/sharepoint-pnp/Set-PnPListInformationRightsManagement.md)** |Get the site closure status of the site which has a site policy applied|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPSiteClosure](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteClosure.md)** |Get the site closure status of the site which has a site policy applied|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPSiteClosure](../../sharepoint-ps/sharepoint-pnp/Set-PnPSiteClosure.md)** |Opens or closes a site which has a site policy applied|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPSitePolicy](../../sharepoint-ps/sharepoint-pnp/Set-PnPSitePolicy.md)** |Sets a site policy|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPSitePolicy](../../sharepoint-ps/sharepoint-pnp/Get-PnPSitePolicy.md)** |Retrieves all or a specific site policy|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Lists -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Clear‑PnPDefaultColumnValues](../../sharepoint-ps/sharepoint-pnp/Clear-PnPDefaultColumnValues.md)** |Clear default column values for a document library|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPDefaultColumnValues](../../sharepoint-ps/sharepoint-pnp/Get-PnPDefaultColumnValues.md)** |Gets the default column values for all folders in document library|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPDefaultColumnValues](../../sharepoint-ps/sharepoint-pnp/Set-PnPDefaultColumnValues.md)** |Sets default column values for a document library|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPFolderPermission](../../sharepoint-ps/sharepoint-pnp/Set-PnPFolderPermission.md)** |Sets folder permissions. Use Get-PnPRoleDefinition to retrieve all available roles you can add or remove using this cmdlet.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPList](../../sharepoint-ps/sharepoint-pnp/Get-PnPList.md)** |Returns a List object|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPList](../../sharepoint-ps/sharepoint-pnp/New-PnPList.md)** |Creates a new list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPList](../../sharepoint-ps/sharepoint-pnp/Remove-PnPList.md)** |Deletes a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPList](../../sharepoint-ps/sharepoint-pnp/Set-PnPList.md)** |Updates list settings|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPListItem](../../sharepoint-ps/sharepoint-pnp/Add-PnPListItem.md)** |Adds an item to the list and sets the creation time to the current date and time. The author is set to the current authenticated user executing the cmdlet. In order to set the author to a different user, please refer to Set-PnPListItem.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPListItem](../../sharepoint-ps/sharepoint-pnp/Get-PnPListItem.md)** |Retrieves list items|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPListItem](../../sharepoint-ps/sharepoint-pnp/Remove-PnPListItem.md)** |Deletes an item from a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPListItem](../../sharepoint-ps/sharepoint-pnp/Set-PnPListItem.md)** |Updates a list item|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPListItemPermission](../../sharepoint-ps/sharepoint-pnp/Set-PnPListItemPermission.md)** |Sets list item permissions. Use Get-PnPRoleDefinition to retrieve all available roles you can add or remove using this cmdlet.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Move‑PnPListItemToRecycleBin](../../sharepoint-ps/sharepoint-pnp/Move-PnPListItemToRecycleBin.md)** |Moves an item from a list to the Recycle Bin|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPListPermission](../../sharepoint-ps/sharepoint-pnp/Set-PnPListPermission.md)** |Sets list permissions|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Request‑PnPReIndexList](../../sharepoint-ps/sharepoint-pnp/Request-PnPReIndexList.md)** |Marks the list for full indexing during the next incremental crawl|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPView](../../sharepoint-ps/sharepoint-pnp/Add-PnPView.md)** |Adds a view to a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPView](../../sharepoint-ps/sharepoint-pnp/Get-PnPView.md)** |Returns one or all views from a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPView](../../sharepoint-ps/sharepoint-pnp/Remove-PnPView.md)** |Deletes a view from a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Management API -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPManagementApiAccessToken](../../sharepoint-ps/sharepoint-pnp/Get-PnPManagementApiAccessToken.md)** |Gets an access token for the Office 365 Management API|SharePoint Online -**[Get‑PnPUnifiedAuditLog](../../sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedAuditLog.md)** |Gets unified audit logs from the Office 365 Management API. Requires the Azure Active Directory application permission 'ActivityFeed.Read'.|SharePoint Online - - -### Microsoft Graph -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPDeletedUnifiedGroup](../../sharepoint-ps/sharepoint-pnp/Get-PnPDeletedUnifiedGroup.md)** |Gets one deleted Office 365 Group (aka Unified Group) or a list of deleted Office 365 Groups|SharePoint Online -**[Remove‑PnPDeletedUnifiedGroup](../../sharepoint-ps/sharepoint-pnp/Remove-PnPDeletedUnifiedGroup.md)** |Permanently removes one deleted Office 365 Group (aka Unified Group)|SharePoint Online -**[Restore‑PnPDeletedUnifiedGroup](../../sharepoint-ps/sharepoint-pnp/Restore-PnPDeletedUnifiedGroup.md)** |Restores one deleted Office 365 Group (aka Unified Group)|SharePoint Online -**[Add‑PnPSiteClassification](../../sharepoint-ps/sharepoint-pnp/Add-PnPSiteClassification.md)** |Adds one ore more site classification values to the list of possible values. Requires a connection to the Microsoft Graph.|SharePoint Online -**[Disable‑PnPSiteClassification](../../sharepoint-ps/sharepoint-pnp/Disable-PnPSiteClassification.md)** |Disables Site Classifications for the tenant. Requires a connection to the Microsoft Graph.|SharePoint Online -**[Enable‑PnPSiteClassification](../../sharepoint-ps/sharepoint-pnp/Enable-PnPSiteClassification.md)** |Enables Site Classifications for the tenant. Requires a connection to the Microsoft Graph.|SharePoint Online -**[Get‑PnPSiteClassification](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteClassification.md)** |Returns the defined Site Classifications for the tenant. Requires a connection to the Microsoft Graph.|SharePoint Online -**[Remove‑PnPSiteClassification](../../sharepoint-ps/sharepoint-pnp/Remove-PnPSiteClassification.md)** |Removes one or more existing site classification values from the list of available values. Requires a connection to the Microsoft Graph|SharePoint Online -**[Update‑PnPSiteClassification](../../sharepoint-ps/sharepoint-pnp/Update-PnPSiteClassification.md)** |Updates Site Classifications for the tenant. Requires a connection to the Microsoft Graph.|SharePoint Online -**[Get‑PnPUnifiedGroup](../../sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroup.md)** |Gets one Office 365 Group (aka Unified Group) or a list of Office 365 Groups. Requires the Azure Active Directory application permission 'Group.Read.All'.|SharePoint Online -**[New‑PnPUnifiedGroup](../../sharepoint-ps/sharepoint-pnp/New-PnPUnifiedGroup.md)** |Creates a new Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permission 'Group.ReadWrite.All'.|SharePoint Online -**[Remove‑PnPUnifiedGroup](../../sharepoint-ps/sharepoint-pnp/Remove-PnPUnifiedGroup.md)** |Removes one Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permission 'Group.ReadWrite.All'.|SharePoint Online -**[Set‑PnPUnifiedGroup](../../sharepoint-ps/sharepoint-pnp/Set-PnPUnifiedGroup.md)** |Sets Office 365 Group (aka Unified Group) properties. Requires the Azure Active Directory application permission 'Group.ReadWrite.All'.|SharePoint Online -**[Get‑PnPUnifiedGroupMembers](../../sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupMembers.md)** |Gets members of a particular Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permissions 'Group.Read.All' and 'User.Read.All'.|SharePoint Online -**[Get‑PnPUnifiedGroupOwners](../../sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupOwners.md)** |Gets owners of a particular Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permissions 'Group.Read.All' and 'User.Read.All'.|SharePoint Online - - -### Provisioning -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Export‑PnPClientSidePage](../../sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePage.md)** |Exports a Client Side Page to a PnP Provisioning Template|SharePoint Online -**[Add‑PnPDataRowsToProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Add-PnPDataRowsToProvisioningTemplate.md)** |Adds datarows to a list inside a PnP Provisioning Template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPFileFromProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Remove-PnPFileFromProvisioningTemplate.md)** |Removes a file from a PnP Provisioning Template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPFileToProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md)** |Adds a file to a PnP Provisioning Template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Convert‑PnPFolderToProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Convert-PnPFolderToProvisioningTemplate.md)** |Creates a pnp package file of an existing template xml, and includes all files in the current folder|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPListFoldersToProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Add-PnPListFoldersToProvisioningTemplate.md)** |Adds folders to a list in a PnP Provisioning Template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Export‑PnPListToProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Export-PnPListToProvisioningTemplate.md)** |Exports one or more lists to provisioning template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningTemplate.md)** |Adds a PnP Provisioning Template object to a tenant template|SharePoint Online -**[Apply‑PnPProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Apply-PnPProvisioningTemplate.md)** |Applies a site template to a web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Convert‑PnPProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Convert-PnPProvisioningTemplate.md)** |Converts a provisioning template to an other schema version|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningTemplate.md)** |Generates a provisioning site template from a web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplate.md)** |Creates a new provisioning template object|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Read‑PnPProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Read-PnPProvisioningTemplate.md)** |Loads/Reads a PnP file from the file system or a string|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Save‑PnPProvisioningTemplate](../../sharepoint-ps/sharepoint-pnp/Save-PnPProvisioningTemplate.md)** |Saves a PnP site template to the file system|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPProvisioningTemplateFromFolder](../../sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplateFromFolder.md)** |Generates a provisioning template from a given folder, including only files that are present in that folder|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPProvisioningTemplateMetadata](../../sharepoint-ps/sharepoint-pnp/Set-PnPProvisioningTemplateMetadata.md)** |Sets metadata of a provisioning template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPTenantSequence](../../sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequence.md)** |Adds a tenant sequence object to a tenant template|SharePoint Online -**[Get‑PnPTenantSequence](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequence.md)** |Returns one ore more provisioning sequence object(s) from a tenant template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPTenantSequence](../../sharepoint-ps/sharepoint-pnp/New-PnPTenantSequence.md)** |Creates a new tenant sequence object|SharePoint Online -**[New‑PnPTenantSequenceCommunicationSite](../../sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceCommunicationSite.md)** |Creates a communication site object|SharePoint Online -**[Add‑PnPTenantSequenceSite](../../sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSite.md)** |Adds a existing tenant sequence site object to a tenant template|SharePoint Online -**[Get‑PnPTenantSequenceSite](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequenceSite.md)** |Returns one ore more sites from a tenant template|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPTenantSequenceSubSite](../../sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSubSite.md)** |Adds a tenant sequence sub site object to a tenant sequence site object|SharePoint Online -**[New‑PnPTenantSequenceTeamNoGroupSite](../../sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSite.md)** |Creates a new team site without an Office 365 group in-memory object|SharePoint Online -**[New‑PnPTenantSequenceTeamNoGroupSubSite](../../sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSubSite.md)** |Creates a team site subsite with no Office 365 group object|SharePoint Online -**[New‑PnPTenantSequenceTeamSite](../../sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamSite.md)** |Creates a team site object|SharePoint Online -**[Apply‑PnPTenantTemplate](../../sharepoint-ps/sharepoint-pnp/Apply-PnPTenantTemplate.md)** |Applies a tenant template to the current tenant. You must be a SharePoint Online global administrator to run the cmdlet.|SharePoint Online -**[Get‑PnPTenantTemplate](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantTemplate.md)** |Generates a provisioning tenant template from a site. If the site is a hubsite any connected site will be included.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPTenantTemplate](../../sharepoint-ps/sharepoint-pnp/New-PnPTenantTemplate.md)** |Creates a new tenant template object|SharePoint Online -**[Read‑PnPTenantTemplate](../../sharepoint-ps/sharepoint-pnp/Read-PnPTenantTemplate.md)** |Loads/Reads a PnP tenant template from the file system and returns an in-memory instance of this template.|SharePoint Online -**[Save‑PnPTenantTemplate](../../sharepoint-ps/sharepoint-pnp/Save-PnPTenantTemplate.md)** |Saves a PnP provisioning hierarchy to the file system|SharePoint Online -**[Test‑PnPTenantTemplate](../../sharepoint-ps/sharepoint-pnp/Test-PnPTenantTemplate.md)** |Tests a tenant template for invalid references|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Publishing -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Set‑PnPAvailablePageLayouts](../../sharepoint-ps/sharepoint-pnp/Set-PnPAvailablePageLayouts.md)** |Sets the available page layouts for the current site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPDefaultPageLayout](../../sharepoint-ps/sharepoint-pnp/Set-PnPDefaultPageLayout.md)** |Sets a specific page layout to be the default page layout for a publishing site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPHtmlPublishingPageLayout](../../sharepoint-ps/sharepoint-pnp/Add-PnPHtmlPublishingPageLayout.md)** |Adds a HTML based publishing page layout|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPMasterPage](../../sharepoint-ps/sharepoint-pnp/Add-PnPMasterPage.md)** |Adds a Masterpage|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPPublishingImageRendition](../../sharepoint-ps/sharepoint-pnp/Add-PnPPublishingImageRendition.md)** |Adds an Image Rendition if the Name of the Image Rendition does not already exist. This prevents creating two Image Renditions that share the same name.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPPublishingImageRendition](../../sharepoint-ps/sharepoint-pnp/Get-PnPPublishingImageRendition.md)** |Returns all image renditions or if Identity is specified a specific one|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPPublishingImageRendition](../../sharepoint-ps/sharepoint-pnp/Remove-PnPPublishingImageRendition.md)** |Removes an existing image rendition|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPPublishingPage](../../sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPage.md)** |Adds a publishing page|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPPublishingPageLayout](../../sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPageLayout.md)** |Adds a publishing page layout|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPWikiPage](../../sharepoint-ps/sharepoint-pnp/Add-PnPWikiPage.md)** |Adds a wiki page|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPWikiPage](../../sharepoint-ps/sharepoint-pnp/Remove-PnPWikiPage.md)** |Removes a wiki page|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWikiPageContent](../../sharepoint-ps/sharepoint-pnp/Get-PnPWikiPageContent.md)** |Gets the contents/source of a wiki page|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPWikiPageContent](../../sharepoint-ps/sharepoint-pnp/Set-PnPWikiPageContent.md)** |Sets the contents of a wikipage|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Records Management -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPInPlaceRecordsManagement](../../sharepoint-ps/sharepoint-pnp/Get-PnPInPlaceRecordsManagement.md)** |Returns if the place records management feature is enabled.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPInPlaceRecordsManagement](../../sharepoint-ps/sharepoint-pnp/Set-PnPInPlaceRecordsManagement.md)** |Activates or deactivates in the place records management feature.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Disable‑PnPInPlaceRecordsManagementForSite](../../sharepoint-ps/sharepoint-pnp/Disable-PnPInPlaceRecordsManagementForSite.md)** |Disables in place records management for a site.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Enable‑PnPInPlaceRecordsManagementForSite](../../sharepoint-ps/sharepoint-pnp/Enable-PnPInPlaceRecordsManagementForSite.md)** |Enables in place records management for a site.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Clear‑PnPListItemAsRecord](../../sharepoint-ps/sharepoint-pnp/Clear-PnPListItemAsRecord.md)** |Undeclares a list item as a record|SharePoint Online -**[Set‑PnPListItemAsRecord](../../sharepoint-ps/sharepoint-pnp/Set-PnPListItemAsRecord.md)** |Declares a list item as a record, for more information, see https://docs.microsoft.com/sharepoint/governance/records-management-in-sharepoint-server|SharePoint Online -**[Test‑PnPListItemIsRecord](../../sharepoint-ps/sharepoint-pnp/Test-PnPListItemIsRecord.md)** |Checks if a list item is a record|SharePoint Online -**[Get‑PnPListRecordDeclaration](../../sharepoint-ps/sharepoint-pnp/Get-PnPListRecordDeclaration.md)** |Returns the manual record declaration settings for a list|SharePoint Online -**[Set‑PnPListRecordDeclaration](../../sharepoint-ps/sharepoint-pnp/Set-PnPListRecordDeclaration.md)** |The RecordDeclaration parameter supports 4 values: AlwaysAllowManualDeclaration NeverAllowManualDeclaration UseSiteCollectionDefaults |SharePoint Online - - -### Search -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPSearchConfiguration](../../sharepoint-ps/sharepoint-pnp/Get-PnPSearchConfiguration.md)** |Returns the search configuration|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPSearchConfiguration](../../sharepoint-ps/sharepoint-pnp/Remove-PnPSearchConfiguration.md)** |Remove the search configuration|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPSearchConfiguration](../../sharepoint-ps/sharepoint-pnp/Set-PnPSearchConfiguration.md)** |Sets the search configuration|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPSearchCrawlLog](../../sharepoint-ps/sharepoint-pnp/Get-PnPSearchCrawlLog.md)** |Returns entries from the SharePoint search crawl log. Make sure you are granted access to the crawl log via the SharePoint search admin center at https://<tenant>-admin.sharepoint.com/_layouts/15/searchadmin/crawllogreadpermission.aspx in order to run this cmdlet.|SharePoint Online -**[Submit‑PnPSearchQuery](../../sharepoint-ps/sharepoint-pnp/Submit-PnPSearchQuery.md)** |Executes an arbitrary search query against the SharePoint search index|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPSearchSettings](../../sharepoint-ps/sharepoint-pnp/Get-PnPSearchSettings.md)** |Retrieves search settings for a site|SharePoint Online -**[Set‑PnPSearchSettings](../../sharepoint-ps/sharepoint-pnp/Set-PnPSearchSettings.md)** |Sets search settings for a site|SharePoint Online -**[Get‑PnPSiteSearchQueryResults](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteSearchQueryResults.md)** |Executes a search query to retrieve indexed site collections|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### SharePoint Recycle Bin -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Clear‑PnPRecycleBinItem](../../sharepoint-ps/sharepoint-pnp/Clear-PnPRecycleBinItem.md)** |Permanently deletes all or a specific recycle bin item|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPRecycleBinItem](../../sharepoint-ps/sharepoint-pnp/Get-PnPRecycleBinItem.md)** |Returns the items in the recycle bin from the context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Move‑PnPRecycleBinItem](../../sharepoint-ps/sharepoint-pnp/Move-PnPRecycleBinItem.md)** |Moves all items or a specific item in the first stage recycle bin of the current site collection to the second stage recycle bin|SharePoint Online -**[Restore‑PnPRecycleBinItem](../../sharepoint-ps/sharepoint-pnp/Restore-PnPRecycleBinItem.md)** |Restores the provided recycle bin item to its original location|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPTenantRecycleBinItem](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantRecycleBinItem.md)** |Returns all modern and classic site collections in the tenant scoped recycle bin|SharePoint Online - - -### SharePoint WebHooks -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPWebhookSubscription](../../sharepoint-ps/sharepoint-pnp/Add-PnPWebhookSubscription.md)** |Adds a new Webhook subscription|SharePoint Online -**[Remove‑PnPWebhookSubscription](../../sharepoint-ps/sharepoint-pnp/Remove-PnPWebhookSubscription.md)** |Removes a Webhook subscription from the resource|SharePoint Online -**[Set‑PnPWebhookSubscription](../../sharepoint-ps/sharepoint-pnp/Set-PnPWebhookSubscription.md)** |Updates a Webhook subscription|SharePoint Online -**[Get‑PnPWebhookSubscriptions](../../sharepoint-ps/sharepoint-pnp/Get-PnPWebhookSubscriptions.md)** |Gets all the Webhook subscriptions of the resource|SharePoint Online - - -### Sites -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Set‑PnPAppSideLoading](../../sharepoint-ps/sharepoint-pnp/Set-PnPAppSideLoading.md)** |Enables the App SideLoading Feature on a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPAuditing](../../sharepoint-ps/sharepoint-pnp/Get-PnPAuditing.md)** |Get the Auditing setting of a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPAuditing](../../sharepoint-ps/sharepoint-pnp/Set-PnPAuditing.md)** |Set Auditing setting for a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Enable‑PnPCommSite](../../sharepoint-ps/sharepoint-pnp/Enable-PnPCommSite.md)** |Enables the modern communication site experience on a classic team site.|SharePoint Online -**[Test‑PnPOffice365GroupAliasIsUsed](../../sharepoint-ps/sharepoint-pnp/Test-PnPOffice365GroupAliasIsUsed.md)** |Tests if a given alias is already used used|SharePoint Online -**[Add‑PnPRoleDefinition](../../sharepoint-ps/sharepoint-pnp/Add-PnPRoleDefinition.md)** |Adds a Role Defintion (Permission Level) to the site collection in the current context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPRoleDefinition](../../sharepoint-ps/sharepoint-pnp/Get-PnPRoleDefinition.md)** |Retrieves a Role Definitions of a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPRoleDefinition](../../sharepoint-ps/sharepoint-pnp/Remove-PnPRoleDefinition.md)** |Remove a Role Definition from a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPSite](../../sharepoint-ps/sharepoint-pnp/Get-PnPSite.md)** |Returns the current site collection from the context.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPSite](../../sharepoint-ps/sharepoint-pnp/Set-PnPSite.md)** |Sets Site Collection properties.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPSiteCollectionAdmin](../../sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAdmin.md)** |Adds one or more users as site collection administrators to the site collection in the current context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPSiteCollectionAdmin](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionAdmin.md)** |Returns the current site collection administrators of the site collection in the current context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPSiteCollectionAdmin](../../sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAdmin.md)** |Removes one or more users as site collection administrators from the site collection in the current context|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Install‑PnPSolution](../../sharepoint-ps/sharepoint-pnp/Install-PnPSolution.md)** |Installs a sandboxed solution to a site collection. WARNING! This method can delete your composed look gallery due to the method used to activate the solution. We recommend you to only to use this cmdlet if you are okay with that.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Uninstall‑PnPSolution](../../sharepoint-ps/sharepoint-pnp/Uninstall-PnPSolution.md)** |Uninstalls a sandboxed solution from a site collection|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPTeamsTeam](../../sharepoint-ps/sharepoint-pnp/Add-PnPTeamsTeam.md)** |Adds a Teams team to an existing, group connected, site collection|SharePoint Online - - -### Taxonomy -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPSiteCollectionTermStore](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionTermStore.md)** |Returns the site collection term store|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Export‑PnPTaxonomy](../../sharepoint-ps/sharepoint-pnp/Export-PnPTaxonomy.md)** |Exports a taxonomy to either the output or to a file.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Import‑PnPTaxonomy](../../sharepoint-ps/sharepoint-pnp/Import-PnPTaxonomy.md)** |Imports a taxonomy from either a string array or a file|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPTaxonomyFieldValue](../../sharepoint-ps/sharepoint-pnp/Set-PnPTaxonomyFieldValue.md)** |Sets a taxonomy term value in a listitem field|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPTaxonomyItem](../../sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomyItem.md)** |Returns a taxonomy item|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPTaxonomyItem](../../sharepoint-ps/sharepoint-pnp/Remove-PnPTaxonomyItem.md)** |Removes a taxonomy item|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPTaxonomySession](../../sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomySession.md)** |Returns a taxonomy session|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPTerm](../../sharepoint-ps/sharepoint-pnp/Get-PnPTerm.md)** |Returns a taxonomy term|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPTerm](../../sharepoint-ps/sharepoint-pnp/New-PnPTerm.md)** |Creates a taxonomy term|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPTermGroup](../../sharepoint-ps/sharepoint-pnp/Get-PnPTermGroup.md)** |Returns a taxonomy term group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPTermGroup](../../sharepoint-ps/sharepoint-pnp/New-PnPTermGroup.md)** |Creates a taxonomy term group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPTermGroup](../../sharepoint-ps/sharepoint-pnp/Remove-PnPTermGroup.md)** |Removes a taxonomy term group and all its containing termsets|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Import‑PnPTermGroupFromXml](../../sharepoint-ps/sharepoint-pnp/Import-PnPTermGroupFromXml.md)** |Imports a taxonomy TermGroup from either the input or from an XML file.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Export‑PnPTermGroupToXml](../../sharepoint-ps/sharepoint-pnp/Export-PnPTermGroupToXml.md)** |Exports a taxonomy TermGroup to either the output or to an XML file.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPTermLabel](../../sharepoint-ps/sharepoint-pnp/New-PnPTermLabel.md)** |Creates a localized label for a taxonomy term|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPTermSet](../../sharepoint-ps/sharepoint-pnp/Get-PnPTermSet.md)** |Returns a taxonomy term set|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Import‑PnPTermSet](../../sharepoint-ps/sharepoint-pnp/Import-PnPTermSet.md)** |Imports a taxonomy term set from a file in the standard format.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPTermSet](../../sharepoint-ps/sharepoint-pnp/New-PnPTermSet.md)** |Creates a taxonomy term set|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Tenant Administration -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPAccessToken](../../sharepoint-ps/sharepoint-pnp/Get-PnPAccessToken.md)** |Returns the current OAuth Access token|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Register‑PnPAppCatalogSite](../../sharepoint-ps/sharepoint-pnp/Register-PnPAppCatalogSite.md)** |Creates a new App Catalog Site and sets this site as the Tenant App Catalog|SharePoint Online -**[Get‑PnPHideDefaultThemes](../../sharepoint-ps/sharepoint-pnp/Get-PnPHideDefaultThemes.md)** |Returns if the default / OOTB themes should be visible to users or not.|SharePoint Online -**[Set‑PnPHideDefaultThemes](../../sharepoint-ps/sharepoint-pnp/Set-PnPHideDefaultThemes.md)** |Defines if the default / OOTB themes should be visible to users or not.|SharePoint Online -**[Get‑PnPHomeSite](../../sharepoint-ps/sharepoint-pnp/Get-PnPHomeSite.md)** |Returns the home site url for your tenant|SharePoint Online -**[Remove‑PnPHomeSite](../../sharepoint-ps/sharepoint-pnp/Remove-PnPHomeSite.md)** |Removes the currently set site as the home site|SharePoint Online -**[Set‑PnPHomeSite](../../sharepoint-ps/sharepoint-pnp/Set-PnPHomeSite.md)** |Sets the home site for your tenant|SharePoint Online -**[Get‑PnPHubSite](../../sharepoint-ps/sharepoint-pnp/Get-PnPHubSite.md)** |Retrieve all or a specific hubsite.|SharePoint Online -**[Register‑PnPHubSite](../../sharepoint-ps/sharepoint-pnp/Register-PnPHubSite.md)** |Registers a site as a hubsite|SharePoint Online -**[Set‑PnPHubSite](../../sharepoint-ps/sharepoint-pnp/Set-PnPHubSite.md)** |Sets hub site properties|SharePoint Online -**[Unregister‑PnPHubSite](../../sharepoint-ps/sharepoint-pnp/Unregister-PnPHubSite.md)** |Unregisters a site as a hubsite|SharePoint Online -**[Add‑PnPHubSiteAssociation](../../sharepoint-ps/sharepoint-pnp/Add-PnPHubSiteAssociation.md)** |Connects a site to a hubsite.|SharePoint Online -**[Remove‑PnPHubSiteAssociation](../../sharepoint-ps/sharepoint-pnp/Remove-PnPHubSiteAssociation.md)** |Disconnects a site from a hubsite.|SharePoint Online -**[Get‑PnPHubSiteChild](../../sharepoint-ps/sharepoint-pnp/Get-PnPHubSiteChild.md)** |Retrieves all sites linked to a specific hub site|SharePoint Online -**[Grant‑PnPHubSiteRights](../../sharepoint-ps/sharepoint-pnp/Grant-PnPHubSiteRights.md)** |Grant additional permissions to the permissions already in place to associate sites to Hub Sites for one or more specific users|SharePoint Online -**[Revoke‑PnPHubSiteRights](../../sharepoint-ps/sharepoint-pnp/Revoke-PnPHubSiteRights.md)** |Revoke permissions to the permissions already in place to associate sites to Hub Sites for one or more specific users|SharePoint Online -**[Get‑PnPKnowledgeHubSite](../../sharepoint-ps/sharepoint-pnp/Get-PnPKnowledgeHubSite.md)** |Gets the Knowledge Hub Site URL for your tenant|SharePoint Online -**[Remove‑PnPKnowledgeHubSite](../../sharepoint-ps/sharepoint-pnp/Remove-PnPKnowledgeHubSite.md)** |Removes the Knowledge Hub Site setting for your tenant|SharePoint Online -**[Set‑PnPKnowledgeHubSite](../../sharepoint-ps/sharepoint-pnp/Set-PnPKnowledgeHubSite.md)** |Sets the Knowledge Hub Site for your tenant|SharePoint Online -**[Add‑PnPOffice365GroupToSite](../../sharepoint-ps/sharepoint-pnp/Add-PnPOffice365GroupToSite.md)** |Groupifies a classic team site by creating an Office 365 group for it and connecting the site with the newly created group|SharePoint Online -**[Add‑PnPOrgAssetsLibrary](../../sharepoint-ps/sharepoint-pnp/Add-PnPOrgAssetsLibrary.md)** |Adds a given document library as a organizational asset source|SharePoint Online -**[Get‑PnPOrgAssetsLibrary](../../sharepoint-ps/sharepoint-pnp/Get-PnPOrgAssetsLibrary.md)** |Returns the list of all the configured organizational asset libraries|SharePoint Online -**[Remove‑PnPOrgAssetsLibrary](../../sharepoint-ps/sharepoint-pnp/Remove-PnPOrgAssetsLibrary.md)** |Removes a given document library as a organizational asset source|SharePoint Online -**[Add‑PnPOrgNewsSite](../../sharepoint-ps/sharepoint-pnp/Add-PnPOrgNewsSite.md)** |Adds the site as an organization news source in your tenant|SharePoint Online -**[Get‑PnPOrgNewsSite](../../sharepoint-ps/sharepoint-pnp/Get-PnPOrgNewsSite.md)** |Returns the list of all the configured organizational news sites.|SharePoint Online -**[Remove‑PnPOrgNewsSite](../../sharepoint-ps/sharepoint-pnp/Remove-PnPOrgNewsSite.md)** |Removes a given site from the list of organizational news sites.|SharePoint Online -**[Initialize‑PnPPowerShellAuthentication](../../sharepoint-ps/sharepoint-pnp/Initialize-PnPPowerShellAuthentication.md)** |Initializes a Azure AD App and optionally creates a new self-signed certificate to use with the application registration.|SharePoint Online -**[Disable‑PnPPowerShellTelemetry](../../sharepoint-ps/sharepoint-pnp/Disable-PnPPowerShellTelemetry.md)** |Disables PnP PowerShell telemetry tracking|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Enable‑PnPPowerShellTelemetry](../../sharepoint-ps/sharepoint-pnp/Enable-PnPPowerShellTelemetry.md)** |Enables PnP PowerShell telemetry tracking.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPPowerShellTelemetryEnabled](../../sharepoint-ps/sharepoint-pnp/Get-PnPPowerShellTelemetryEnabled.md)** |Returns true if the PnP PowerShell Telemetry has been enabled.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPSite](../../sharepoint-ps/sharepoint-pnp/New-PnPSite.md)** |Creates either a communication site or an Office 365 group-connected team site|SharePoint Online -**[Add‑PnPSiteCollectionAppCatalog](../../sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAppCatalog.md)** |Adds a Site Collection scoped App Catalog to a site|SharePoint Online -**[Remove‑PnPSiteCollectionAppCatalog](../../sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAppCatalog.md)** |Removes a Site Collection scoped App Catalog from a site|SharePoint Online -**[Add‑PnPSiteDesign](../../sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesign.md)** |Creates a new Site Design on the current tenant.|SharePoint Online -**[Get‑PnPSiteDesign](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesign.md)** |Retrieve Site Designs that have been registered on the current tenant.|SharePoint Online -**[Invoke‑PnPSiteDesign](../../sharepoint-ps/sharepoint-pnp/Invoke-PnPSiteDesign.md)** |Apply a Site Design to an existing site. * Requires Tenant Administration Rights *|SharePoint Online -**[Remove‑PnPSiteDesign](../../sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesign.md)** |Removes a Site Design|SharePoint Online -**[Set‑PnPSiteDesign](../../sharepoint-ps/sharepoint-pnp/Set-PnPSiteDesign.md)** |Updates a Site Design on the current tenant.|SharePoint Online -**[Get‑PnPSiteDesignRights](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRights.md)** |Returns the principals with design rights on a specific Site Design|SharePoint Online -**[Grant‑PnPSiteDesignRights](../../sharepoint-ps/sharepoint-pnp/Grant-PnPSiteDesignRights.md)** |Grants the specified principals rights to use the site design.|SharePoint Online -**[Revoke‑PnPSiteDesignRights](../../sharepoint-ps/sharepoint-pnp/Revoke-PnPSiteDesignRights.md)** |Revokes the specified principals rights to use the site design.|SharePoint Online -**[Get‑PnPSiteDesignRun](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRun.md)** |Retrieves a list of site designs applied to a specified site collection. If the WebUrl parameter is not specified we show the list of designs applied to the current site. The returned output includes the ID of the scheduled job, the web and site IDs, and the site design ID, version, and title.|SharePoint Online -**[Get‑PnPSiteDesignRunStatus](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRunStatus.md)** |Retrieves and displays a list of all site script actions executed for a specified site design applied to a site.|SharePoint Online -**[Add‑PnPSiteDesignTask](../../sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesignTask.md)** |This command is used to apply a published site design to a specified site collection target. It schedules the operation, allowing for the application of larger site scripts (Invoke-PnPSiteDesign is limited to 30 actions and subactions). This command is intended to replace Invoke-PnPSiteDesign and is useful when you need to apply a large number of actions or multiple site scripts.|SharePoint Online -**[Get‑PnPSiteDesignTask](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignTask.md)** |Used to retrieve a scheduled site design script. It takes the ID of the scheduled site design task and the URL for the site where the site design is scheduled to be applied.|SharePoint Online -**[Remove‑PnPSiteDesignTask](../../sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesignTask.md)** |Removes a Site Design Task. If the execution of the associated site script has already started the execution will not be terminated.|SharePoint Online -**[Add‑PnPSiteScript](../../sharepoint-ps/sharepoint-pnp/Add-PnPSiteScript.md)** |Creates a new Site Script on the current tenant.|SharePoint Online -**[Get‑PnPSiteScript](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteScript.md)** |Retrieve Site Scripts that have been registered on the current tenant.|SharePoint Online -**[Remove‑PnPSiteScript](../../sharepoint-ps/sharepoint-pnp/Remove-PnPSiteScript.md)** |Removes a Site Script|SharePoint Online -**[Set‑PnPSiteScript](../../sharepoint-ps/sharepoint-pnp/Set-PnPSiteScript.md)** |Updates an existing Site Script on the current tenant.|SharePoint Online -**[Get‑PnPSiteScriptFromList](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromList.md)** |Generates a Site Script from an existing list|SharePoint Online -**[Get‑PnPSiteScriptFromWeb](../../sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromWeb.md)** |Generates a Site Script from an existing site|SharePoint Online -**[Get‑PnPStorageEntity](../../sharepoint-ps/sharepoint-pnp/Get-PnPStorageEntity.md)** |Retrieve Storage Entities / Farm Properties from either the Tenant App Catalog or from the current site if it has a site scope app catalog.|SharePoint Online -**[Remove‑PnPStorageEntity](../../sharepoint-ps/sharepoint-pnp/Remove-PnPStorageEntity.md)** |Remove Storage Entities / Farm Properties from either the tenant scoped app catalog or the current site collection if the site has a site collection scoped app catalog|SharePoint Online -**[Set‑PnPStorageEntity](../../sharepoint-ps/sharepoint-pnp/Set-PnPStorageEntity.md)** |Set Storage Entities / Farm Properties in either the tenant scoped app catalog or the site collection app catalog.|SharePoint Online -**[Get‑PnPTenant](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenant.md)** |Returns organization-level site collection properties|SharePoint Online -**[Set‑PnPTenant](../../sharepoint-ps/sharepoint-pnp/Set-PnPTenant.md)** |Sets organization-level site collection properties|SharePoint Online -**[Clear‑PnPTenantAppCatalogUrl](../../sharepoint-ps/sharepoint-pnp/Clear-PnPTenantAppCatalogUrl.md)** |Removes the url of the tenant scoped app catalog. It will not delete the site collection itself.|SharePoint Online -**[Get‑PnPTenantAppCatalogUrl](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantAppCatalogUrl.md)** |Retrieves the url of the tenant scoped app catalog|SharePoint Online -**[Set‑PnPTenantAppCatalogUrl](../../sharepoint-ps/sharepoint-pnp/Set-PnPTenantAppCatalogUrl.md)** |Sets the url of the tenant scoped app catalog|SharePoint Online -**[Get‑PnPTenantCdnEnabled](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnEnabled.md)** |Retrieves if the Office 365 Content Delivery Network has been enabled.|SharePoint Online -**[Set‑PnPTenantCdnEnabled](../../sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnEnabled.md)** |Enables or disabled the public or private Office 365 Content Delivery Network (CDN).|SharePoint Online -**[Add‑PnPTenantCdnOrigin](../../sharepoint-ps/sharepoint-pnp/Add-PnPTenantCdnOrigin.md)** |Adds a new origin to the public or private content delivery network (CDN).|SharePoint Online -**[Get‑PnPTenantCdnOrigin](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnOrigin.md)** |Returns the current registered origins from the public or private content delivery network (CDN).|SharePoint Online -**[Remove‑PnPTenantCdnOrigin](../../sharepoint-ps/sharepoint-pnp/Remove-PnPTenantCdnOrigin.md)** |Removes an origin from the Public or Private content delivery network (CDN).|SharePoint Online -**[Get‑PnPTenantCdnPolicies](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnPolicies.md)** |Returns the CDN Policies for the specified CDN (Public | Private).|SharePoint Online -**[Set‑PnPTenantCdnPolicy](../../sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnPolicy.md)** |Sets the CDN Policies for the specified CDN (Public | Private).|SharePoint Online -**[Get‑PnPTenantId](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantId.md)** |Returns the Tenant ID|SharePoint Online -**[Clear‑PnPTenantRecycleBinItem](../../sharepoint-ps/sharepoint-pnp/Clear-PnPTenantRecycleBinItem.md)** |Permanently deletes a site collection from the tenant scoped recycle bin|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Restore‑PnPTenantRecycleBinItem](../../sharepoint-ps/sharepoint-pnp/Restore-PnPTenantRecycleBinItem.md)** |Restores a site collection from the tenant scoped recycle bin|SharePoint Online -**[Disable‑PnPTenantServicePrincipal](../../sharepoint-ps/sharepoint-pnp/Disable-PnPTenantServicePrincipal.md)** |Enables the current tenant's "SharePoint Online Client" service principal.|SharePoint Online -**[Enable‑PnPTenantServicePrincipal](../../sharepoint-ps/sharepoint-pnp/Enable-PnPTenantServicePrincipal.md)** |Enables the current tenant's "SharePoint Online Client" service principal.|SharePoint Online -**[Get‑PnPTenantServicePrincipal](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipal.md)** |Returns the current tenant's "SharePoint Online Client" service principal.|SharePoint Online -**[Revoke‑PnPTenantServicePrincipalPermission](../../sharepoint-ps/sharepoint-pnp/Revoke-PnPTenantServicePrincipalPermission.md)** |Revokes a permission that was previously granted to the "SharePoint Online Client" service principal.|SharePoint Online -**[Get‑PnPTenantServicePrincipalPermissionGrants](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionGrants.md)** |Gets the collection of permission grants for the "SharePoint Online Client" service principal|SharePoint Online -**[Approve‑PnPTenantServicePrincipalPermissionRequest](../../sharepoint-ps/sharepoint-pnp/Approve-PnPTenantServicePrincipalPermissionRequest.md)** |Approves a permission request for the current tenant's "SharePoint Online Client" service principal|SharePoint Online -**[Deny‑PnPTenantServicePrincipalPermissionRequest](../../sharepoint-ps/sharepoint-pnp/Deny-PnPTenantServicePrincipalPermissionRequest.md)** |Denies a permission request for the current tenant's "SharePoint Online Client" service principal|SharePoint Online -**[Get‑PnPTenantServicePrincipalPermissionRequests](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionRequests.md)** |Gets the collection of permission requests for the "SharePoint Online Client" service principal|SharePoint Online -**[Get‑PnPTenantSite](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantSite.md)** |Retrieve site information.|SharePoint Online, SharePoint 2016, SharePoint 2019 -**[New‑PnPTenantSite](../../sharepoint-ps/sharepoint-pnp/New-PnPTenantSite.md)** |Creates a new (classic) site collection for the current tenant|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPTenantSite](../../sharepoint-ps/sharepoint-pnp/Remove-PnPTenantSite.md)** |Removes a site collection|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPTenantSite](../../sharepoint-ps/sharepoint-pnp/Set-PnPTenantSite.md)** |Set site information.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPTenantTheme](../../sharepoint-ps/sharepoint-pnp/Add-PnPTenantTheme.md)** |Adds or updates a theme to the tenant.|SharePoint Online -**[Get‑PnPTenantTheme](../../sharepoint-ps/sharepoint-pnp/Get-PnPTenantTheme.md)** |Returns all or a specific theme|SharePoint Online -**[Remove‑PnPTenantTheme](../../sharepoint-ps/sharepoint-pnp/Remove-PnPTenantTheme.md)** |Removes a theme|SharePoint Online -**[Get‑PnPTimeZoneId](../../sharepoint-ps/sharepoint-pnp/Get-PnPTimeZoneId.md)** |Returns a time zone ID|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWebTemplates](../../sharepoint-ps/sharepoint-pnp/Get-PnPWebTemplates.md)** |Returns the available web templates|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### User and group management -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPAlert](../../sharepoint-ps/sharepoint-pnp/Add-PnPAlert.md)** |Adds an alert for a user to a list|SharePoint Online, SharePoint 2019 -**[Get‑PnPAlert](../../sharepoint-ps/sharepoint-pnp/Get-PnPAlert.md)** |Returns registered alerts for a user.|SharePoint Online, SharePoint 2019 -**[Remove‑PnPAlert](../../sharepoint-ps/sharepoint-pnp/Remove-PnPAlert.md)** |Removes an alert for a user|SharePoint Online, SharePoint 2019 -**[Get‑PnPGroup](../../sharepoint-ps/sharepoint-pnp/Get-PnPGroup.md)** |Returns a specific SharePoint group or all SharePoint groups in site.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPGroup](../../sharepoint-ps/sharepoint-pnp/New-PnPGroup.md)** |Adds group to the Site Groups List and returns a group object|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPGroup](../../sharepoint-ps/sharepoint-pnp/Remove-PnPGroup.md)** |Removes a group from a web.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPGroup](../../sharepoint-ps/sharepoint-pnp/Set-PnPGroup.md)** |Updates a group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPGroupMembers](../../sharepoint-ps/sharepoint-pnp/Get-PnPGroupMembers.md)** |Retrieves all members of a group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPGroupPermissions](../../sharepoint-ps/sharepoint-pnp/Get-PnPGroupPermissions.md)** |Returns the permissions for a specific SharePoint group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPGroupPermissions](../../sharepoint-ps/sharepoint-pnp/Set-PnPGroupPermissions.md)** |Adds and/or removes permissions of a specific SharePoint group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPUser](../../sharepoint-ps/sharepoint-pnp/Get-PnPUser.md)** |Returns site users of current web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPUser](../../sharepoint-ps/sharepoint-pnp/New-PnPUser.md)** |Adds a user to the built-in Site User Info List and returns a user object|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPUser](../../sharepoint-ps/sharepoint-pnp/Remove-PnPUser.md)** |Removes a specific user from the site collection User Information List|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPUserFromGroup](../../sharepoint-ps/sharepoint-pnp/Remove-PnPUserFromGroup.md)** |Removes a user from a group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPUserToGroup](../../sharepoint-ps/sharepoint-pnp/Add-PnPUserToGroup.md)** |Adds a user to a group|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### User Profiles -Cmdlet|Description|Platform -:-----|:----------|:------- -**[New‑PnPPersonalSite](../../sharepoint-ps/sharepoint-pnp/New-PnPPersonalSite.md)** |Office365 only: Creates a personal / OneDrive For Business site|SharePoint Online -**[New‑PnPUPABulkImportJob](../../sharepoint-ps/sharepoint-pnp/New-PnPUPABulkImportJob.md)** |Submit up a new user profile bulk import job.|SharePoint Online -**[Get‑PnPUPABulkImportStatus](../../sharepoint-ps/sharepoint-pnp/Get-PnPUPABulkImportStatus.md)** |Get user profile bulk import status.|SharePoint Online -**[Get‑PnPUserProfileProperty](../../sharepoint-ps/sharepoint-pnp/Get-PnPUserProfileProperty.md)** |You must connect to the tenant admin website (https://:<tenant>-admin.sharepoint.com) with Connect-PnPOnline in order to use this cmdlet. |SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPUserProfileProperty](../../sharepoint-ps/sharepoint-pnp/Set-PnPUserProfileProperty.md)** |Office365 only: Uses the tenant API to retrieve site information. You must connect to the tenant admin website (https://:<tenant>-admin.sharepoint.com) with Connect-PnPOnline in order to use this command. |SharePoint Online - - -### Utilities -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Send‑PnPMail](../../sharepoint-ps/sharepoint-pnp/Send-PnPMail.md)** |Sends an email using the Office 365 SMTP Service or SharePoint, depending on the parameters specified. See detailed help for more information.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Web Parts -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Get‑PnPClientSideComponent](../../sharepoint-ps/sharepoint-pnp/Get-PnPClientSideComponent.md)** |Retrieve one or more Client-Side components from a site page|SharePoint Online, SharePoint 2019 -**[Remove‑PnPClientSideComponent](../../sharepoint-ps/sharepoint-pnp/Remove-PnPClientSideComponent.md)** |Removes a Client-Side component from a page|SharePoint Online, SharePoint 2019 -**[Set‑PnPClientSideText](../../sharepoint-ps/sharepoint-pnp/Set-PnPClientSideText.md)** |Set Client-Side Text Component properties|SharePoint Online, SharePoint 2019 -**[Set‑PnPClientSideWebPart](../../sharepoint-ps/sharepoint-pnp/Set-PnPClientSideWebPart.md)** |Set Client-Side Web Part properties|SharePoint Online, SharePoint 2019 -**[Get‑PnPWebPart](../../sharepoint-ps/sharepoint-pnp/Get-PnPWebPart.md)** |Returns a web part definition object|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPWebPart](../../sharepoint-ps/sharepoint-pnp/Remove-PnPWebPart.md)** |Removes a web part from a page|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWebPartProperty](../../sharepoint-ps/sharepoint-pnp/Get-PnPWebPartProperty.md)** |Returns a web part property|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPWebPartProperty](../../sharepoint-ps/sharepoint-pnp/Set-PnPWebPartProperty.md)** |Sets a web part property|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPWebPartToWebPartPage](../../sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWebPartPage.md)** |Adds a web part to a web part page in a specified zone|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPWebPartToWikiPage](../../sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWikiPage.md)** |Adds a web part to a wiki page in a specified table row and column|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWebPartXml](../../sharepoint-ps/sharepoint-pnp/Get-PnPWebPartXml.md)** |Returns the web part XML of a web part registered on a site|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Webs -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Set‑PnPIndexedProperties](../../sharepoint-ps/sharepoint-pnp/Set-PnPIndexedProperties.md)** |Marks values of the propertybag to be indexed by search. Notice that this will overwrite the existing flags, i.e. only the properties you define with the cmdlet will be indexed.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPIndexedProperty](../../sharepoint-ps/sharepoint-pnp/Add-PnPIndexedProperty.md)** |Marks the value of the propertybag key specified to be indexed by search.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPIndexedProperty](../../sharepoint-ps/sharepoint-pnp/Remove-PnPIndexedProperty.md)** |Removes a key from propertybag to be indexed by search. The key and it's value remain in the propertybag, however it will not be indexed anymore.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPIndexedPropertyKeys](../../sharepoint-ps/sharepoint-pnp/Get-PnPIndexedPropertyKeys.md)** |Returns the keys of the property bag values that have been marked for indexing by search|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPPropertyBag](../../sharepoint-ps/sharepoint-pnp/Get-PnPPropertyBag.md)** |Returns the property bag values.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPPropertyBagValue](../../sharepoint-ps/sharepoint-pnp/Remove-PnPPropertyBagValue.md)** |Removes a value from the property bag|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPPropertyBagValue](../../sharepoint-ps/sharepoint-pnp/Set-PnPPropertyBagValue.md)** |Sets a property bag value|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Request‑PnPReIndexWeb](../../sharepoint-ps/sharepoint-pnp/Request-PnPReIndexWeb.md)** |Marks the web for full indexing during the next incremental crawl|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPRequestAccessEmails](../../sharepoint-ps/sharepoint-pnp/Get-PnPRequestAccessEmails.md)** |Returns the request access e-mail addresses|SharePoint Online -**[Set‑PnPRequestAccessEmails](../../sharepoint-ps/sharepoint-pnp/Set-PnPRequestAccessEmails.md)** |Sets Request Access Email on a web|SharePoint Online -**[Get‑PnPSubWebs](../../sharepoint-ps/sharepoint-pnp/Get-PnPSubWebs.md)** |Returns the subwebs of the current web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWeb](../../sharepoint-ps/sharepoint-pnp/Get-PnPWeb.md)** |Returns the current web object|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[New‑PnPWeb](../../sharepoint-ps/sharepoint-pnp/New-PnPWeb.md)** |Creates a new subweb under the current web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPWeb](../../sharepoint-ps/sharepoint-pnp/Remove-PnPWeb.md)** |Removes a subweb in the current web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPWeb](../../sharepoint-ps/sharepoint-pnp/Set-PnPWeb.md)** |Sets properties on a web|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Invoke‑PnPWebAction](../../sharepoint-ps/sharepoint-pnp/Invoke-PnPWebAction.md)** |Executes operations on web, lists and list items.|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Set‑PnPWebPermission](../../sharepoint-ps/sharepoint-pnp/Set-PnPWebPermission.md)** |Set permissions|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -### Workflows -Cmdlet|Description|Platform -:-----|:----------|:------- -**[Add‑PnPWorkflowDefinition](../../sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowDefinition.md)** |Adds a workflow definition|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWorkflowDefinition](../../sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowDefinition.md)** |Returns a workflow definition|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPWorkflowDefinition](../../sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowDefinition.md)** |Removes a workflow definition|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWorkflowInstance](../../sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowInstance.md)** |Get workflow instances|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Resume‑PnPWorkflowInstance](../../sharepoint-ps/sharepoint-pnp/Resume-PnPWorkflowInstance.md)** |Resume a workflow|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Start‑PnPWorkflowInstance](../../sharepoint-ps/sharepoint-pnp/Start-PnPWorkflowInstance.md)** |Starts a workflow instance on a list item|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Stop‑PnPWorkflowInstance](../../sharepoint-ps/sharepoint-pnp/Stop-PnPWorkflowInstance.md)** |Stops a workflow instance|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Add‑PnPWorkflowSubscription](../../sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowSubscription.md)** |Adds a workflow subscription to a list|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Get‑PnPWorkflowSubscription](../../sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowSubscription.md)** |Return a workflow subscription|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -**[Remove‑PnPWorkflowSubscription](../../sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowSubscription.md)** |Remove workflow subscription|SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online - - -## Additional resources -<a name="bk_addresources"> </a> - -- [SharePoint PnP PowerShell on GitHub](https://github.com/SharePoint/PnP-PowerShell) diff --git a/sharepoint/docs-conceptual/sharepoint-server/sharepoint-server-cmdlets.md b/sharepoint/docs-conceptual/sharepoint-server/sharepoint-server-cmdlets.md deleted file mode 100644 index bdd48c69c5..0000000000 --- a/sharepoint/docs-conceptual/sharepoint-server/sharepoint-server-cmdlets.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: SharePoint Server Cmdlets ---- - -# SharePoint Server Cmdlets - -For a listing of the SharePoint Server cmdlets, see [SharePoint Server cmdlets](../../sharepoint-ps/sharepoint-server/sharepoint-server.md) - -## Accessing PowerShell for SharePoint Server ## - -After you install SharePoint Server, applicable PowerShell cmdlets are available in the SharePoint 2016 Management Shell. You can manage most aspects of SharePoint Server in the SharePoint Management Shell. You can create new site collections, web applications, user accounts, service applications, proxies, and more. Commands that you type in the SharePoint Management Shell return SharePoint objects that are based on the Microsoft .NET Framework. You can apply these objects as input to subsequent commands or store the objects in local variables for later use. - -With the SharePoint Management Shell, you do not have to register the snap-in that contains the cmdlets. Registration of the Microsoft.SharePoint.PowerShell.dll module for SharePoint Server cmdlets is automatic, as a result of the **Add-PSSnapin Microsoft.SharePoint.PowerShell** line in the SharePoint.ps1 file that is located in %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\<version>\Config\PowerShell\Registration, where version "15" equals SharePoint Server 2013, and version "16" equals SharePoint Server 2016. To use the PowerShell console, you must register this snap-in manually. - -Whether you use the SharePoint Management Shell or the PowerShell console, you can also load additional snap-ins. - -> [!NOTE] -> The SharePoint Management Shell and the PowerShell console also differ in the use of the **ReuseThread** option, which defines how the threading model is used. The SharePoint Management Shell's use is defined by this line, {Host.Runspace.ThreadOptions = "ReuseThread"}, which is in the SharePoint.ps1 file. For more information, see [PS Thread Options](/dotnet/api/system.management.automation.runspaces.psthreadoptions). - -## Permissions ## - -Before you can use the Add-SPShellAdmin cmdlet to grant permissions for users to run SharePoint Server cmdlets, verify that you meet all of the following minimum requirements: - -* You must have membership in the **securityadmin** fixed server role on the SQL Server instance. -* You must be a member of the Administrators group on the server on which you are running the PowerShell cmdlet. - -> [!NOTE] -> If these permissions are not satisfied, contact your Setup administrator or SQL Server administrator to request these permissions. - -For additional information about PowerShell permissions, see [Add-SPShellAdmin](../../sharepoint-ps/sharepoint-server/Add-SPShellAdmin.md). - -If you do not have membership in the **SharePoint_Shell_Access** role or **WSS_Admin_WPG** local group, use the **Add-SPShellAdmin** cmdlet to add the **WSS_Admin_WPG** group in all front-end web servers in the SharePoint farm and the **SharePoint_Shell_Access** role. If the SQL Server database does not have a **SharePoint_Shell_Access** role, the role is automatically created when you run the **Add-SPShellAdmin** cmdlet. After you run the **Add-SPShellAdmin** cmdlet, users can run SharePoint PowerShell cmdlets in a multiple-server farm environment. - -**NOTE:** When you install SharePoint Server, the user account from which you run the installation is granted the appropriate permissions to run PowerShell cmdlets. If any users have not been added to run a PowerShell cmdlet, you can use the **Add-SPShellAdmin** cmdlet to add them. - -To see a list of all of the **SPShellAdmin** cmdlets, from a PowerShell command prompt, type _Get-Command -Noun SPShellAdmin_. - -## Scripts and execution policies ## - -Although you can use Microsoft PowerShell to perform a single administrative task, you can also use a script to automate a series of tasks. A script is a text file that contains one or more Microsoft PowerShell commands. Microsoft PowerShell scripts have a .ps1 file name extension. - -To run scripts, the minimum required execution policy for SharePoint Server is **RemoteSigned**, although the default policy for PowerShell is Restricted. If the policy is left as Restricted, the SharePoint Management Shell will change the policy for PowerShell to RemoteSigned. This means that you must select **Run as administrator** to start the SharePoint Management Shell with elevated administrative permission. This change will apply to all PowerShell sessions. For more information, see [ExecutionPolicy Enumeration](/dotnet/api/microsoft.powershell.executionpolicy). - -For additional information about scripts and execution policies, see [about_scripts](/powershell/module/microsoft.powershell.core/about/about_scripts) and [About Execution Policies](/powershell/module/microsoft.powershell.core/about/about_execution_policies). - diff --git a/sharepoint/docs-conceptual/toc.yml b/sharepoint/docs-conceptual/toc.yml deleted file mode 100644 index f65925cf94..0000000000 --- a/sharepoint/docs-conceptual/toc.yml +++ /dev/null @@ -1,13 +0,0 @@ -- name: SharePoint PowerShell - href: index.yml -- name: SharePoint in Microsoft 365 - items: - - name: Intro to SharePoint Online Management Shell - href: sharepoint-online/introduction-sharepoint-online-management-shell.md - - name: Get started with SharePoint Online Management Shell - href: sharepoint-online/connect-sharepoint-online.md -- name: SharePoint PnP - href: sharepoint-pnp/sharepoint-pnp-cmdlets.md -- name: SharePoint Server - href: sharepoint-server/sharepoint-server-cmdlets.md - diff --git a/sharepoint/mapping/monikerMapping.json b/sharepoint/mapping/monikerMapping.json deleted file mode 100644 index f6808a117f..0000000000 --- a/sharepoint/mapping/monikerMapping.json +++ /dev/null @@ -1,13 +0,0 @@ -{ - "sharepoint-ps": { - "conceptualToc": "docs-conceptual/toc.yml", - "conceptualTocUrl": "/powershell/sharepoint/sharepoint-ps/toc.json", - "referenceTocUrl": "/powershell/module/sharepoint-ps/toc.json", - "packageRoot": "sharepoint-ps", - "modules": { - "sharepoint-online": {}, - "sharepoint-server": {}, - "sharepoint-pnp": {} - } - } -} \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOGeoAdministrator.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOGeoAdministrator.md deleted file mode 100644 index bedd4ed4ac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOGeoAdministrator.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spogeoadministrator -applicable: SharePoint Online -title: Add-SPOGeoAdministrator -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOGeoAdministrator - -## SYNOPSIS - -Adds a new SharePoint user or security group as GeoAdministrator to a multi-geo tenant. - -## SYNTAX - -```powershell -Add-SPOGeoAdministrator -UserPrincipalName <string> -GroupAlias <string> -ObjectId <guid> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet requires a connection to a multi-geo tenant to run correctly. -You must be a SharePoint Online global Administrator to run this cmdlet. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Add-SPOGeoAdministrator -UserPrincipalName admin@contoso.onmicrosoft.com -``` - -Adds the user **admin\@contoso.onmicrosoft.com** as administrator to the SharePoint Online multi-geo tenant. - -## PARAMETERS - -### -GroupAlias - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: Group -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ObjectId - -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: ObjectId -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: User -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOGeoAdministrator](Get-SPOGeoAdministrator.md) - -[Remove-SPOGeoAdministrator](Remove-SPOGeoAdministrator.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubSiteAssociation.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubSiteAssociation.md deleted file mode 100644 index 6ca5580b35..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubSiteAssociation.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spohubsiteassociation -applicable: SharePoint Online -title: Add-SPOHubSiteAssociation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOHubSiteAssociation - -## SYNOPSIS - -Associates a site with a hub site. - -## SYNTAX - -```powershell -Add-SPOHubSiteAssociation [-Site] <SpoSitePipeBind> -HubSite <SpoHubSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to associate a site with a hub site. - -## EXAMPLES - -### Example 1 - -```powershell -Add-SPOHubSiteAssociation https://contoso.sharepoint.com/sites/Research -HubSite https://contoso.sharepoint.com/sites/Marketing -``` - -This example associates the research site with the marketing hub site. - -## PARAMETERS - -### -Site - -URL of the site to join to the hub site. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -HubSite - -URL of the hub site. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES - -If the site or hub site doesn't exist, this cmdlet returns a "File not found" error. - -If the site is already a hub site, this cmdlet returns a "This site is already a HubSite" error. diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubToHubAssociation.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubToHubAssociation.md deleted file mode 100644 index 164eec92e8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubToHubAssociation.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spohubtohubassociation -applicable: SharePoint Online -title: Add-SPOHubToHubAssociation -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Add-SPOHubToHubAssociation - -## SYNOPSIS - -Associates a hub site to a hub site. -Note: This feature is currently in preview and may not be available in your tenant. - -## SYNTAX - -```powershell -Add-SPOHubToHubAssociation [-Source] <SpoHubSitePipeBind> -Target <SpoHubSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to associate a hub site to a hub site. - -## EXAMPLES - -### Example 1 - -```powershell -Add-SPOHubToHubAssociation -Source 7b6fd3a3-b029-4eb0-8e00-ba4a3949807d -Target 43a36572-37ec-45c3-9058-061a2db4cd26 -``` - -This example associates the source hub site with the HubSiteId 7b6fd3a3-b029-4eb0-8e00-ba4a3949807d with the target hub site with the HubSiteId 43a36572-37ec-45c3-9058-061a2db4cd26. - -## PARAMETERS - -### -Source - -HubSiteId of the Source Hub site to be associated with the Target Hub Site. - -```yaml -Type: SpoHubSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Target - -HubSiteId of the Target Hub to associate the source Hub to. - -```yaml -Type: SpoHubSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES -"SPOHubToHubAssociation is just a placeholder and not yet ready for production. diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOOrgAssetsLibrary.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOOrgAssetsLibrary.md deleted file mode 100644 index 621a380ff8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOOrgAssetsLibrary.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spoorgassetslibrary -applicable: SharePoint Online -title: Add-SPOOrgAssetsLibrary -author: Maralesfahanpoor -ms.author: maesfaha -ms.reviewer: -manager: paulac -schema: 2.0.0 ---- - -# Add-SPOOrgAssetsLibrary - -## SYNOPSIS - -Designates a library to be used as a central location for organization assets across the tenant. - -## SYNTAX - -```powershell -Add-SPOOrgAssetsLibrary -LibraryUrl <String> [-ThumbnailUrl <String>] [-OrgAssetType <OrgAssetType>] [-CdnType <SPOTenantCdnType>] -[<CommonParameters>] -``` - -## DESCRIPTION - -The Add-SPOOrgAssetsLibrary cmdlet designates a library to be a central location for organization assets across the tenant. Once this cmdlet is run, assets stored within this library are available to sites across the tenant. The name publicly displayed for the library will be the name of the library on the SharePoint site. Note that it may take from a couple of hours to a day for changes to be reflected. - -## EXAMPLES - -### Example 1 - -This example adds <https://contoso.sharepoint.com/sites/branding/Assets> as a designated library for organization assets. Assets is the name of the SharePoint library added and will be the name publicly displayed for the library. The thumbnail publicly displayed for the library is contosologo.jpg, from that same library. - -```powershell -Add-SPOOrgAssetsLibrary -LibraryURL https://contoso.sharepoint.com/sites/branding/Assets -ThumbnailURL https://contoso.sharepoint.com/sites/branding/Assets/contosologo.jpg -``` - -## PARAMETERS - -### -CdnType - -Specifies the CDN type. The valid values are public or private. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Accepted values: Public, Private - -Required: False -Position: Named -Default value: Private -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LibraryUrl - -Indicates the absolute URL of the library to be designated as a central location for organization assets. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrgAssetType - -Indicates the type of content in this library. Currently supported values are ImageDocumentLibrary, which is set by default, and OfficeTemplateLibrary. - -```yaml -Type: OrgAssetType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Accepted values: ImageDocumentLibrary, OfficeTemplateLibrary - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThumbnailUrl - -Indicates the URL of the background image used when the library is publicly displayed. If no thumbnail URL is indicated, the card will have a gray background. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoorgassetslibrary?view=sharepoint-ps) - -[Set-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/set-spoorgassetslibrary?view=sharepoint-ps) - -[Remove-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spoorgassetslibrary?view=sharepoint-ps) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteCollectionAppCatalog.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteCollectionAppCatalog.md deleted file mode 100644 index 3758543f16..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteCollectionAppCatalog.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spositecollectionappcatalog -applicable: SharePoint Online -title: Add-SPOSiteCollectionAppCatalog -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Add-SPOSiteCollectionAppCatalog - -## SYNOPSIS - -Adds a Site Collection scoped App Catalog to a site. - -## SYNTAX - -```powershell -Add-SPOSiteCollectionAppCatalog -Site <SpoSitePipeBind> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to add a site collection scoped app catalog to the specified site. - -## EXAMPLES - -### Example 1 - -```powershell -Add-SPOSiteCollectionAppCatalog -Site "https://contoso.sharepoint.com/sites/FinanceTeamsite" -``` - -This example adds a SiteCollection app catalog to the specified site. - -## PARAMETERS - -### -Site - -Url of the site to add the app catalog to. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesign.md deleted file mode 100644 index 49a79d1ca6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesign.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spositedesign -applicable: SharePoint Online -title: Add-SPOSiteDesign -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOSiteDesign - -## SYNOPSIS - -Creates a new site design available to users when they create a new site from the SharePoint home page. - -## SYNTAX - -```powershell -Add-SPOSiteDesign - -Title <string> - -WebTemplate <string> - -SiteScripts <SPOSiteScriptPipeBind[]> - [-Description <string>] - [-PreviewImageUrl <string>] - [-PreviewImageAltText <string>] - [-IsDefault] - [<CommonParameters>] -``` - -## DESCRIPTION - -Creates a new site design available to users when they create a new site from the SharePoint home page. - -## EXAMPLES - -### Example 1 - -This example creates a new site design. - -```powershell -Add-SPOSiteDesign ` - -Title "Contoso customer tracking" ` - -WebTemplate "64" ` - -SiteScripts "<ID>" ` - -Description "Tracks key customer data in a list" ` - -PreviewImageUrl "https://contoso.sharepoint.com/SiteAssets/site-preview.png" ` - -PreviewImageAltText "site preview" -``` - -## PARAMETERS - -### -Title - -The display name of the site design. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebTemplate - -Identifies which base template to add the design to. Use the value **64** for the Team site template, and the value **68** for the Communication site template. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteScripts - -An array of one or more site scripts. Each is identified by an ID. The scripts run in the order listed. - -```yaml -Type: SPOSiteScriptPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -The display description of the site design. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviewImageUrl - -The URL of a preview image. If none is specified, SharePoint uses a generic image. Recommended size is 400 x 421 pixels. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviewImageAltText - -The alt text description of the image for accessibility. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefault - -A switch that if provided, applies the site design to the default site template. For more information, see [Customize a default site design](https://docs.microsoft.com/sharepoint/dev/declarative-customization/customize-default-site-design). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesignTask.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesignTask.md deleted file mode 100644 index 0cb1095c39..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesignTask.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spositedesigntask -applicable: SharePoint Online -title: Add-SPOSiteDesignTask -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOSiteDesignTask - -## SYNOPSIS - -Similar to Invoke-SPOSiteDesign, this command is used to apply a published site design to a specified site collection target. It schedules the operation, allowing for the application of larger site scripts (Invoke-SPOSiteDesign is limited to 30 actions and subactions). - -The supported site templates you can apply a site design to include: "modern" team site (with O365 group), "modern" team site (without an O365 group); communication site; classic team site; and classic publishing site. - -## SYNTAX - -```powershell -Add-SPOSiteDesignTask -SiteDesignId <guid> -WebUrl <string> [<CommonParameters>] -``` - -## DESCRIPTION - -This command is used to apply a published site design to a specified site collection target. It schedules the operation, allowing for the application of larger site scripts (Invoke-SPOSiteDesign is limited to 30 actions and subactions). - -This command is intended to replace Invoke-SPOSiteDesign and is useful when you need to apply a large number of actions or multiple site scripts. - -> [!NOTE] -> This command only creates the request. To check on the job status or to view details of the scheduled run, use the commands in the related section below. - -## EXAMPLES - -### Example 1 - -This example applies a site design that includes two site scripts - totaling over 30 site script actions. Executing the commands will schedule the site design to be queued and run against the designated site collection. - -```powershell -Add-SPOSiteDesignTask -SiteDesignId 501z8c32-4147-44d4-8607-26c2f67cae82 -WebUrl "https://contoso.sharepoint.com/sites/projectawesome" -``` - -## PARAMETERS - -### -SiteDesignId - -The ID of the site design to apply. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebUrl - -The URL of the site collection where the site design will be applied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPOSiteDesignTask](https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositedesigntask?view=sharepoint-ps) - -[Invoke-SPOSiteDesign](https://docs.microsoft.com/powershell/module/sharepoint-online/invoke-spositedesign?view=sharepoint-ps) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteScript.md deleted file mode 100644 index 5f41477ad5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteScript.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spositescript -applicable: SharePoint Online -title: Add-SPOSiteScript -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOSiteScript - -## SYNOPSIS - -Uploads a new site script for use either directly or in a site design. - -## SYNTAX - -```powershell -Add-SPOSiteScript -Title <string> -Content <string> [-Description <string>] [<CommonParameters>] -``` - -## DESCRIPTION - -Uploads a new site script for use either directly or in a site design. - -## EXAMPLES - -### Example 1 - -This example adds a new site logo from the following script in a file. - -```json -{ - "$schema": "schema.json", - "actions": [ - { - "verb": "setSiteLogo", - "url": "https://contoso.sharepoint.com/SiteAssets/company-logo.png" - } - ] -} -``` - -```powershell -Get-Content 'c:\scripts\site-script.json' -Raw | Add-SPOSiteScript -Title "Customer logo" -Description "Applies customer logo for customer sites" -``` - -### Example 2 - -This example sets the external sharing capabilities of the site to the ExternalUserAndGuestSharing option. We also add a site design for a Communication site (68) which uses this script. - -```powershell -$script = @' -{ - "$schema": "schema.json", - "actions": [ - { - "verb": "setSiteExternalSharingCapability", - "capability": "ExternalUserAndGuestSharing" - } - ], - "bindata": { }, - "version": 1 - }; -'@ - -Add-SPOSiteScript -Title "External User and Guest Sharing site script" -Description "A site script to manage the -guest access of a site" -Content $script -``` - -```powershell -Id : ea9e3a52-7c12-4da8-a901-4912be8a76bc -Title : External User and Guest Sharing site script -Description : A site script to manage theguest access of a site -Content : -Version : 0 -``` - -```powershell -Add-SPOSiteDesign -Title "Communication Site with External Users and Guest Sharing" -WebTemplate "68" -SiteScripts "ea9e3a52-7c12-4da8-a901-4912be8a76bc" -``` - -## PARAMETERS - -### -Title - -The display name of the site design. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Content - -The JSON value that describes the script. For more information, see the [JSON reference](https://docs.microsoft.com/sharepoint/dev/declarative-customization/site-design-json-schema). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -A description of the script. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOTenantCdnOrigin.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOTenantCdnOrigin.md deleted file mode 100644 index d075b8e97c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOTenantCdnOrigin.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spotenantcdnorigin -applicable: SharePoint Online -title: Add-SPOTenantCdnOrigin -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOTenantCdnOrigin - -## SYNOPSIS - -Configures a new origin to public or private content delivery network (CDN). Requires Tenant administrator permissions. - -## SYNTAX - -```powershell -Add-SPOTenantCdnOrigin -CdnType <SPOTenantCdnType> [-Confirm] -OriginUrl <String> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Configures a new origin to public or private CDN, on either Tenant level or on a single Site level. Effectively, a tenant admin points out to a document library, or a folder in the document library and requests that content in that library should be retrievable by using a CDN. - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -## EXAMPLES - -### Example 1 - -``` -Add-SPOTenantCdnOrigin -CdnType public -OriginUrl /sites/site/subfolder -``` - -This example configures a public CDN on a site level. - -## PARAMETERS - -### -CdnType - -Specifies the CDN type. The valid values are: public or private. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) -Aliases: -Accepted values: Public, Private -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OriginUrl - -Specifies a path to the doc library to be configured. It can be provided in two ways: relative path, or a mask. - -Relative-Relative path depends on the OriginScope. If the originScope is Tenant, a path must be a relative path under the tenant root. If the originScope is Site, a path must be a relative path under the given Site. The path must point to the valid Document Library or a folder within a document library. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).> - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOTheme.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOTheme.md deleted file mode 100644 index bb8d0f88a3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOTheme.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spotheme -applicable: SharePoint Online -title: Add-SPOTheme -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOTheme - -## SYNOPSIS - -Creates a new custom theme, or overwrites an existing theme to modify its settings. - -## SYNTAX - -```powershell -Add-SPOTheme -Identity <SpoThemePipeBind> -IsInverted <bool> -Overwrite -Palette <SpoThemePalettePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -The **Add-SPOTheme** cmdlet creates a new theme or updates an existing theme. The color palette settings can be passed as either a hash table or a dictionary. - -Adding a theme does not apply the theme to any sites. It adds the theme to your tenant store, and then the theme is available in the list of themes under the **Change the look** option for modern pages. - -## EXAMPLES - -### Example 1 - -In this example, a new theme named `"Custom Cyan"` is created, with color palette settings that are various shades of cyan. Note that the settings are passed as a hash table. - -```powershell -$themepalette = @{ - "themePrimary" = "#00ffff"; - "themeLighterAlt" = "#f3fcfc"; - "themeLighter" = "#daffff"; - "themeLight" = "#affefe"; - "themeTertiary" = "#76ffff"; - "themeSecondary" = "#39ffff"; - "themeDarkAlt" = "#00c4c4"; - "themeDark" = "#009090"; - "themeDarker" = "#005252"; - "neutralLighterAlt" = "#f8f8f8"; - "neutralLighter" = "#f4f4f4"; - "neutralLight" = "#eaeaea"; - "neutralQuaternaryAlt" = "#dadada"; - "neutralQuaternary" = "#d0d0d0"; - "neutralTertiaryAlt" = "#c8c8c8"; - "neutralTertiary" = "#a6a6a6"; - "neutralSecondaryAlt" = "#767676"; - "neutralSecondary" = "#666666"; - "neutralPrimary" = "#333"; - "neutralPrimaryAlt" = "#3c3c3c"; - "neutralDark" = "#212121"; - "black" = "#000000"; - "white" = "#fff"; - "primaryBackground" = "#fff"; - "primaryText" = "#333" - } - -Add-SPOTheme -Identity "Custom Cyan" -Palette $themepalette -IsInverted $false -``` - -> [!NOTE] -> Prior to the December 2017 release of the SPO Management Shell, the **Add-SPOTheme** cmdlet required that color palette settings be passed as a dictionary. We recommend that you use the latest version of the SPO Management Shell, or use the `HashToDictionary` function to convert a hash table to a dictionary if needed. - -### Example 2 - -If you want to update an existing theme (to modify some of its color settings, for example), use the same syntax as shown previously, but add the `-Overwrite` flag to the **Add-SPOTheme** cmdlet. - -```powershell -Add-SPOTheme -Identity "Custom Cyan" -Palette $themepalette -IsInverted $false -Overwrite -``` - -## PARAMETERS - -### -Identity - -```yaml -Type: SpoThemePalettePipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsInverted - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: None -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Overwrite - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: None -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Palette - -```yaml -Type: SpoThemePalettePipeBind -Parameter Sets: (All) -Aliases: None -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -## OUTPUTS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOUser.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOUser.md deleted file mode 100644 index f0682d5f7e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOUser.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/add-spouser -applicable: SharePoint Online -title: Add-SPOUser -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Add-SPOUser - -## SYNOPSIS - -Adds an existing Office 365 user or an Office 365 security group to a SharePoint group. - -## SYNTAX - -```powershell -Add-SPOUser -Group <String> -LoginName <String> -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Along with the group memberships that are normally required to run Windows PowerShell, you must be a SharePoint Online global administrator and a site collection administrator to use the `Add-SPOUser` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Add-SPOUser -Site https://contoso.sharepoint.com/sites/sc1 -LoginName joe.healy@contoso.com -Group "SC1 Owners" -``` - -Example 1 adds a user who has the e-mail address joe.healy@contoso.com to the group "SC1 Owners" in the site collection <https://contoso.sharepoint.com/sites/sc1.> - -### ------------ Example 2 -------------------- - -```powershell -Add-SPOUser -Site https://contoso.sharepoint.com -LoginName melissa.kerr@contoso.com -Group "Team Site Members" -``` - -Example 2 adds a user who has the e-mail address melissa.kerr@contoso.com to the group "Team Site Members" in the site collection <https://contoso.sharepoint.com.> - -## PARAMETERS - -### -Group - -Specifies the name of the SharePoint group to add the user or the security group to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoginName - -Specifies the login name of the user to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the URL of the site collection to which you want to add the user. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - [Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[New-SPOSiteGroup](New-SPOSiteGroup.md) - -[Get-SPOUser](Get-SPOUser.md) - -[Set-SPOUser](Set-SPOUser.md) - -[Remove-SPOUser](Remove-SPOUser.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Approve-SPOTenantServicePrincipalPermissionGrant.md b/sharepoint/sharepoint-ps/sharepoint-online/Approve-SPOTenantServicePrincipalPermissionGrant.md deleted file mode 100644 index 3fcdbdbcd4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Approve-SPOTenantServicePrincipalPermissionGrant.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/approve-spotenantserviceprincipalpermissiongrant -applicable: SharePoint Online -title: Approve-SPOTenantServicePrincipalPermissionGrant -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Approve-SPOTenantServicePrincipalPermissionGrant - -## SYNOPSIS - -Approves a permission request for the current tenant's "SharePoint Online Client" service principal. - -## SYNTAX - -### Default - -```powershell -Approve-SPOTenantServicePrincipalPermissionGrant -Resource <string> -Scope <string> -``` - -## DESCRIPTION - -Adds a permission for the current tenant's "SharePoint Online Client" service principal. Can be used to add needed permissions to the service principal without specifically requesting them in the SharePoint Framework solution file (sppkg). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell - Approve-SPOTenantServicePrincipalPermissionGrant -Resource "Microsoft Graph" -Scope "Mail.Read" -``` - -Adds a permission scope for the 'Microsoft Graph' resource with scope claim 'Mail.Read'. - -## PARAMETERS - -### -Resource - -Resource of the permission request to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope - -Scope of the permission request to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Approve-SPOTenantServicePrincipalPermissionRequest.md b/sharepoint/sharepoint-ps/sharepoint-online/Approve-SPOTenantServicePrincipalPermissionRequest.md deleted file mode 100644 index 0498589407..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Approve-SPOTenantServicePrincipalPermissionRequest.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/approve-spotenantserviceprincipalpermissionrequest -applicable: SharePoint Online -title: Approve-SPOTenantServicePrincipalPermissionRequest -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Approve-SPOTenantServicePrincipalPermissionRequest - -## SYNOPSIS - -Approves a permission request for the current tenant's "SharePoint Online Client" service principal - -## SYNTAX - -### Default - -```powershell -Approve-SPOTenantServicePrincipalPermissionRequest -RequestId <Guid> -``` - -## DESCRIPTION - -Approves a permission request for the current tenant's "SharePoint Online Client" service principal - -The return value of a successful call is a permission grant object. See [the "Permission grant object" section of the -Get-SPOTenantServicePrincipalPermissionGrants help documentation](Get-SPOTenantServicePrincipalPermissionGrants.md) -for more information about a permission grant object. - -To get the collection of permission grants for the "SharePoint Online Client" service principal, use the -[Get-SPOTenantServicePrincipalPermissionGrants](Get-SPOTenantServicePrincipalPermissionGrants.md) command. - -Approving a permission request also removes that request from the list of permission requests. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell -$requests = Get-SPOTenantServicePrincipalPermissionRequests -$requestToApprove = $requests | ? { $_.Resource -eq 'Office 365 SharePoint Online' -and $_.Scope -eq 'MyFiles.Read' } | Select-Object -First 1 - -if ($requestToApprove -ne $null) -{ - Approve-SPOTenantServicePrincipalPermissionRequest -RequestId $requestToApprove.Id -} -``` - -Approves the permission request for the 'Office 365 SharePoint Online' resource with scope claim 'MyFiles.Read'. -If there is no request with those properties, then no approve action will be taken. - -## PARAMETERS - -### -RequestId - -The ID of the permission request to approve - -```yaml -Type: Guid - -Required: True -Position: Named -Accept pipeline input: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Connect-SPOService.md b/sharepoint/sharepoint-ps/sharepoint-online/Connect-SPOService.md deleted file mode 100644 index d2695437e3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Connect-SPOService.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/connect-sposervice -applicable: SharePoint Online -title: Connect-SPOService -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Connect-SPOService - -## SYNOPSIS - -Connects a SharePoint Online global administrator to a SharePoint Online connection (the SharePoint Online Administration Center). -This cmdlet must be run before any other SharePoint Online cmdlets can run. - -## SYNTAX - -### AuthenticationUrl - -```powershell -Connect-SPOService -AuthenticationUrl <String> [-ClientTag <String>] [-Credential <CredentialCmdletPipeBind>] - -Url <UrlCmdletPipeBind> [<CommonParameters>] -``` - -### AuthenticationLocation - -```powershell -Connect-SPOService [-ClientTag <String>] [-Credential <CredentialCmdletPipeBind>] - [-Region <AADCrossTenantAuthenticationLocation>] -Url <UrlCmdletPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -The `Connect-SPOService` cmdlet connects a SharePoint Online global administrator to the SharePoint Online Administration Center. - -Only a single SharePoint Online service connection is maintained from any single Windows PowerShell session. -In other words, this is a per-organization administrator connection. -Running the `Connect-SPOService` cmdlet twice implicitly disconnects the previous connection. -The Windows PowerShell session will be set to serve the new SharePoint Online global administrator specified. - -A delegated partner administrator has to swap connections for different organizations within the same Windows PowerShell session. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Connect-SPOService -Url https://contoso-admin.sharepoint.com -credential admin@contoso.com -``` - -Example 1 shows how a SharePoint Online global administrator with credential admin@contoso.com connects to a SharePoint Online Administration Center that has the URL <https://contoso-admin.sharepoint.com.> - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -$username = "admin@contoso.sharepoint.com" -$password = "password" -$cred = New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $userName, $(convertto-securestring $Password -asplaintext -force) -Connect-SPOService -Url https://contoso-admin.sharepoint.com -Credential $cred -``` - -Example 2 shows how a SharePoint Online global administrator with a username and password connects to a SharePoint Online Administration Center that has the URL <https://contoso-admin.sharepoint.com.> - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -Connect-SPOService -Url https://contoso-admin.sharepoint.com -``` - -Prompts for credentials. This is required if the account is using multi-factor authentication. - -## PARAMETERS - -### -AuthenticationUrl - -Location for AAD Cross-Tenant Authentication service. Can be optionally used if non-default Cross-Tenant Authentication Service is used. - -```yaml -Type: String -Parameter Sets: AuthenticationUrl -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClientTag - -Permits appending a client tag to existing client tag. Used optionally in the CSOM http traffic to identify used script or solution. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential - -Specifies the credentials to use to connect. If no credentials are presented, a dialog will prompt for the credentials. The credentials must be those of a SharePoint Online global administrator who can access the SharePoint Online Administration Center site. - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Region - -The valid values are: Default | ITAR | Germany | China - -The default value is "default". - -> [!NOTE] -> The ITAR value is for United States Government cloud tenancies only. - -```yaml -Type: AADCrossTenantAuthenticationLocation -Parameter Sets: AuthenticationLocation -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url - -Specifies the URL of the SharePoint Online Administration Center site. - -```yaml -Type: UrlCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Disconnect-SPOService](Disconnect-SPOService.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationEncryptedPackage.md b/sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationEncryptedPackage.md deleted file mode 100644 index a07b3a1792..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationEncryptedPackage.md +++ /dev/null @@ -1,190 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/convertto-spomigrationencryptedpackage -applicable: SharePoint Online -title: ConvertTo-SPOMigrationEncryptedPackage -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# ConvertTo-SPOMigrationEncryptedPackage - -## SYNOPSIS - -Use this Cmdlet to convert your XML files into a new encrypted migration package. - -## SYNTAX - -### ImplicitSourceParameterSet - -```powershell -ConvertTo-SPOMigrationEncryptedPackage -EncryptionParameters <EncryptionParameters> -MigrationSourceLocations <MigrationPackageLocation> [-NoLogFile] -TargetFilesPath <String> -TargetPackagePath <String> [<CommonParameters>] -``` - -### ExplicitSourceParameterSet - -```powershell -ConvertTo-SPOMigrationEncryptedPackage -EncryptionParameters <EncryptionParameters> [-NoLogFile] - -SourceFilesPath <String> -SourcePackagePath <String> -TargetFilesPath <String> -TargetPackagePath <String> - [<CommonParameters>] -``` - -## DESCRIPTION - -This command convert the XML file on your temporary XML folder files into a new set of targeted migration encrypted metadata files to the target directory. - -## EXAMPLES - -### Example 1 - -```powershell -ConvertTo-SPOMigrationEncryptedPackage -EncryptionParameters SHA256 -MigrationSourceLocations $MigrationPackageLocation -NoLogFile -TargetFilesPath $TargetFilesPath -TargetPackagePath $TargetPackagePath -``` - -Changes a migration package to a migration encrypted package on the "migrationSourceLocations" , with log file on the current tenant - -### Example 2 - -```powershell -ConvertTo-SPOMigrationEncryptedPackage -EncryptionParameters SHA384 -MigrationSourceLocations $MigrationPackageLocation -TargetFilesPath $TargetFilesPath -TargetPackagePath $TargetPackagePath -``` - -Same as example1 but without log file and using an encryption type SHA384 - -## PARAMETERS - -### -EncryptionParameters - -Parameters of the encryption, it doesn't accept wildcard characters. -It accepts parameters like SHA384, SHA256, etc. - -```yaml -Type: EncryptionParameters -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MigrationSourceLocations - -Possible Source locations to migrate - -```yaml -Type: MigrationPackageLocation -Parameter Sets: ImplicitSourceParameterSet -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -Switch Parameter to determine if you should get or not a log file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceFilesPath - -Defines the temporary Path where are located the XML source files. - -```yaml -Type: String -Parameter Sets: ExplicitSourceParameterSet -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcePackagePath - -Defines the source package path location. - -```yaml -Type: String -Parameter Sets: ExplicitSourceParameterSet -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetFilesPath - -Defines the temporary Path where are located the XML source files. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetPackagePath - -Defines the source package path location of the package to be encrypted. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[ConvertTo-SPOMigrationTargetedPackage](ConvertTo-SPOMigrationTargetedPackage.md) -[Migrate to SharePoint Online using PowerShell](https://docs.microsoft.com/sharepointmigration/overview-spmt-ps-cmdlets) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationTargetedPackage.md b/sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationTargetedPackage.md deleted file mode 100644 index 6184aef713..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationTargetedPackage.md +++ /dev/null @@ -1,313 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/convertto-spomigrationtargetedpackage -applicable: SharePoint Online -title: ConvertTo-SPOMigrationTargetedPackage -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# ConvertTo-SPOMigrationTargetedPackage - -## SYNOPSIS - -Use this cmdlet to convert your XML files into a new migration package. - -## SYNTAX - -### DocumentLibraryImport - -```powershell -ConvertTo-SPOMigrationTargetedPackage [-SourceFilesPath] <String> [-SourcePackagePath] <String> [[-OutputPackagePath] <String>] [-TargetWebUrl] <String> [-AzureADUserCredentials <CredentialCmdletPipeBind>] -Credentials <CredentialCmdletPipeBind> [-NoAzureADLookup] [-NoLogFile] [-ParallelImport] [-PartitionSizeInBytes <Int64>] -TargetDocumentLibraryPath <String> [-TargetDocumentLibrarySubFolderPath <String>] [-TargetEnvironment <TargetEnvironment>] [-UserMappingFile <String>] [<CommonParameters>] -``` - -### ListImport - -```powershell -ConvertTo-SPOMigrationTargetedPackage [-SourceFilesPath] <String> [-SourcePackagePath] <String> [[-OutputPackagePath] <String>] [-TargetWebUrl] <String> [-AzureADUserCredentials <CredentialCmdletPipeBind>] -Credentials <CredentialCmdletPipeBind> [-NoAzureADLookup] [-NoLogFile] [-ParallelImport] [-PartitionSizeInBytes <Int64>] [-TargetEnvironment <TargetEnvironment>] -TargetListPath <String> [-UserMappingFile <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to create a migration package from one Library to Another Library in form of a package. It converts the XML files and saves them as a new set of targeted migration package metadata files to the target directory. - -## EXAMPLES - -### Example 1 - -This example shows how to convert a package to a targeted one by looking up data in the target site collection. It uses the '-ParallelImport' parameter to boost file share migration performance. -```Powershell -$finalPackages = ConvertTo-SPOMigrationTargetedPackage -ParallelImport -SourceFilesPath $sourceFiles -SourcePackagePath $sourcePackage -OutputPackagePath $targetPackage -Credentials $cred -TargetWebUrl $targetWeb -TargetDocumentLibraryPath $targetDocLib -``` - -## PARAMETERS - -### -AzureADUserCredentials - -Receives Azure Active Directory User Credentials - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credentials - -Fill out the Regular Credentials (Get-Credential) - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoAzureADLookup - -Switch parameter that says if the command should or should not look up for Azure AD. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -Switch Parameter to determine if you should get or not a log file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputPackagePath - -Output package path - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ParallelImport - -Switch parameter to boost file share migration performance. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionSizeInBytes - -Define the partition size in Bytes where it will be located the target package. - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceFilesPath - -Defines the temporary Path where are located the XML source files. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcePackagePath - -Defines the source package path location. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDocumentLibraryPath - -Defines the target document library path. - -```yaml -Type: String -Parameter Sets: DocumentLibraryImport -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDocumentLibrarySubFolderPath - -Defines the target document library subfolder path. - -```yaml -Type: String -Parameter Sets: DocumentLibraryImport -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetEnvironment - -Defines the Target environment: Production, ProductionChina, None or OnPremises. - -```yaml -Type: TargetEnvironment -Parameter Sets: (All) -Aliases: -Accepted values: Production, ProductionChina, None, OnPremises -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetListPath - -Defines the Target list path - -```yaml -Type: String -Parameter Sets: ListImport -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetWebUrl - -Defines the Target Web URL of the package. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserMappingFile - -Defines the file mapping of the user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[ConvertTo-SPOMigrationEncryptedPackage](ConvertTo-SPOMigrationEncryptedPackage.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Deny-SPOTenantServicePrincipalPermissionRequest.md b/sharepoint/sharepoint-ps/sharepoint-online/Deny-SPOTenantServicePrincipalPermissionRequest.md deleted file mode 100644 index 1441221afa..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Deny-SPOTenantServicePrincipalPermissionRequest.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/deny-spotenantserviceprincipalpermissionrequest -applicable: SharePoint Online -title: Deny-SPOTenantServicePrincipalPermissionRequest -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Deny-SPOTenantServicePrincipalPermissionRequest - -## SYNOPSIS - -Denies a permission request for the current tenant's "SharePoint Online Client" service principal - -## SYNTAX - -### Default - -```powershell -Deny-SPOTenantServicePrincipalPermissionRequest -RequestId <Guid> -``` - -## DESCRIPTION - -Denies a permission request for the current tenant's "SharePoint Online Client" service principal - -Denying a permission request removes that request from the list of permission requests. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell -$requests = Get-SPOTenantServicePrincipalPermissionRequests -$requestToDeny = $requests | ? { $_.Resource -eq 'Office 365 SharePoint Online' -and $_.Scope -eq 'MyFiles.Read' } | Select-Object -First 1 - -if ($requestToDeny -ne $null) -{ - Deny-SPOTenantServicePrincipalPermissionRequest -RequestId $requestToDeny.Id -} -``` - -Denies the permission request for the 'Office 365 SharePoint Online' resource with scope claim 'MyFiles.Read'. -If there is no request with those properties, then no deny action will be taken. - -## PARAMETERS - -### -RequestId - -The ID of the permission request to deny - -```yaml -Type: Guid - -Required: True -Position: Named -Accept pipeline input: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Disable-SPOTenantServicePrincipal.md b/sharepoint/sharepoint-ps/sharepoint-online/Disable-SPOTenantServicePrincipal.md deleted file mode 100644 index d25e6df374..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Disable-SPOTenantServicePrincipal.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/disable-spotenantserviceprincipal -applicable: SharePoint Online -title: Disable-SPOTenantServicePrincipal -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Disable-SPOTenantServicePrincipal - -## SYNOPSIS - -Disables the current tenant's "SharePoint Online Client" service principal. - -## SYNTAX - -```powershell -Disable-SPOTenantServicePrincipal -``` - -## DESCRIPTION - -Disables the current tenant's "SharePoint Online Client" service principal. - -When the service principal's account is disabled, clients and components that use this service principal -will not be able to request an access token for this service principal. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell -Disable-SPOTenantServicePrincipal -``` - -Disables the current tenant's "SharePoint Online Client" service principal. diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Disconnect-SPOService.md b/sharepoint/sharepoint-ps/sharepoint-online/Disconnect-SPOService.md deleted file mode 100644 index 68959d69c4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Disconnect-SPOService.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/disconnect-sposervice -applicable: SharePoint Online -title: Disconnect-SPOService -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Disconnect-SPOService - -## SYNOPSIS - -Disconnects from a SharePoint Online service. - -## SYNTAX - -```powershell -Disconnect-SPOService [<CommonParameters>] -``` - -## DESCRIPTION - -The `Disconnect-SPOService` cmdlet explicitly disconnects a previously created SharePoint Online service connection. - -Global administrators can disconnect the service by running the `Disconnect-SPOService` cmdlet or by running the `Connect-SPOService` cmdlet to initiate another connection. -For more information, see `Connect-SPOService`. - -Even after a connection is terminated, operations that were started before the connection is terminated will run to completion. -In other words, long-running operations will not be terminated by running the `Disconnect-SPOService` cmdlet or the `Connect-SPOService` cmdlet. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Disconnect-SPOService -``` - -This example disconnects the service for the tenant. - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Connect-SPOService](Connect-SPOService.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOCommSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOCommSite.md deleted file mode 100644 index 61459cb12e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOCommSite.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/enable-spocommsite -applicable: SharePoint Online -title: Enable-SPOCommSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Enable-SPOCommSite - -## SYNOPSIS - -Enables the modern communication site experience on an existing site. - -**At this time, based on early adopter feedback, we have decided to postpone rolling out this feature. We apologize for any inconvenience and will communicate a new schedule via Message Center, once it is available. You can also check [Microsoft 365 Roadmap](https://www.microsoft.com/microsoft-365/roadmap) for latest updates to this feature.** - -## SYNTAX - -```powershell -Enable-SPOCommSite [-SiteUrl] <string> [-DesignPackageId] <GUID> -``` - -## DESCRIPTION - -Use this cmdlet to enable the modern communication site experience at the classic root site of a tenant. You must use the SharePoint admin powershell version 8715.1200 or greater. Use of this cmdlet is subject to rollout of capability. - -**Current limitations** - -1. This cmdlet can only be run on the root site of a tenant. Typically the root site url is <https://tenantname.sharepoint.com> -2. The root site should not currently have the classic publishing feature enabled (at the site or web level). [What is classic publishing feature?](https://support.office.com/article/enable-publishing-features-479677a6-8b33-4ac7-907d-071c1c7e4518) -3. The root site **should not have had** the classic publishing feature enabled in the past (at the site or web level) -4. The site must have quick launch site navigation enabled. [How do I do this?](https://support.office.com/article/customize-site-navigation-c040f014-acbb-4c98-8174-48428cf02b25#bm1a) - -**On successful execution of the cmdlet, customers can expect** - -1. A new modern home page will be created for the root site (only the root site web, not subsites of the root site if there are any) -2. Full width pages with horizontal nav will be available (top nav from classic view will be hidden, can be seen in classic pages like the site settings page) -3. NoScript will be turned ON -4. Minor Versioning on the Site Pages library will be enabled -5. Site Pages will be the default content type in the Site Pages library -6. No change in permissions or content in the root site - -## EXAMPLES - -### Example 1 - -```powershell -Enable-SPOCommSite -SiteUrl https://contoso.sharepoint.com -``` - -This example enables the communication site experience at this <https://contoso.sharepoint.com> site. - -### Example 2 - -```powershell -$orgName="<tenantname>" -$rootSiteURL = "<Root site URL>" -Connect-SPOService -Url https://$orgName-admin.sharepoint.com -Enable-SPOCommSite -SiteUrl $rootSiteURL -``` - -**STEP BY STEP INSTRUCTIONS** - -1. Install latest SharePoint Online Management Shell (version 8715.1200 or greater) from [here](https://www.microsoft.com/en-us/download/details.aspx?id=35588). If you have an older version installed, please uninstall it from Windows Add/Remove programs and then install the latest version. Alternatively, if you have used Install-Module Microsoft.Online.SharePoint.PowerShell to install the SharePoint Online Management Shell, you can run Update-Module Microsoft.Online.SharePoint.PowerShell to update the PowerShell module to the latest available version. -2. Make sure you have the SharePoint admin credentials for the tenant -3. Make sure you have the correct root site URL. Typically its <https://tenantname.sharepoint.com> -4. Copy the above PowerShell command(s) into a notepad and fill in the missing details denoted by <> -5. Open SharePoint Online Management Shell from your computer -6. Execute the PowerShell commands from your notepad - -**TROUBLESHOOTING** - -**Error case 1: Wrong credentials** - -If the SharePoint admin user credentials is wrong or invalid, you will see this error: - ->*Connect-SPOService : The sign-in name or password does not match one in the Microsoft account system.* - -**Error case 2: Feature is not yet enabled for your tenant** - -The use of this cmdlet is subject to the feature rollout. If the feature is not yet available for your tenant, the cmdlet will not execute and will show this error: - ->*Enable-SPOCommSite : The requested operation is part of an experimental feature that is not supported in the current environment.* - -**Error case 3: Site URL input is not of root site** - -Currently only the root site of a tenant is supported for this cmdlet. IF the site URL input is wrong, you will see this error: - ->*Enable-SPOCommSite : The site provided is not the root site collection. Please provide a valid root site URL.* - -**Error case 4: Site URL input is invalid** - -If the site URL input points to a site that does not exist, you will see the following error message: - ->*Enable-SPOCommSite : File Not Found.* - -**Error case 5: Classic publishing feature is currently enabled** - -We do not support root site that currently have or have had in the past enabled the classic publishing features. If you see this error, your root site is not eligible for this feature enablement - ->*Enable-SPOCommSite : The operation cannot be performed because the Publishing feature is enabled on the site.* - -## PARAMETERS - -### -SiteUrl - -URL of the site for enabling the modern communication site experience. **This is a required parameter** - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DesignPackageId - -GUID identifying the [communication site design](https://support.office.com/article/what-is-a-sharepoint-communication-site-94a33429-e580-45c3-a090-5512a8070732). **This is not a required input.** If no input is provided, the topic design will be applied to the new home page. here are the IDs for the supported design packages: - -1. Topic: 96c933ac-3698-44c7-9f4a-5fd17d71af9e -2. Showcase: 6142d2a0-63a5-4ba0-aede-d9fefca2c767 -3. Blank: f6cc5403-0d63-442e-96c0-285923709ffc - -```yaml -Type: GUID -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: 96c933ac-3698-44c7-9f4a-5fd17d71af9e -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOTenantServicePrincipal.md b/sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOTenantServicePrincipal.md deleted file mode 100644 index e5ec4a7ac7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOTenantServicePrincipal.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/enable-spotenantserviceprincipal -applicable: SharePoint Online -title: Enable-SPOTenantServicePrincipal -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Enable-SPOTenantServicePrincipal - -## SYNOPSIS - -Enables the current tenant's "SharePoint Online Client" service principal. - -## SYNTAX - -```powershell -Enable-SPOTenantServicePrincipal [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Enables the current tenant's "SharePoint Online Client" service principal. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell -Enable-SPOTenantServicePrincipal -``` - -Enables the current tenant's "SharePoint Online Client" service principal. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md b/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md deleted file mode 100644 index 877c86db48..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Online.SharePoint.PowerShell.dll-Help.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/export-spoquerylogs -applicable: SharePoint Online -title: Export-SPOQueryLogs -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - - -# Export-SPOQueryLogs - -## SYNOPSIS - -Export query logs for a user in an Office 365 tenant. - -## SYNTAX - -```powershell -Export-SPOQueryLogs [-StartTime <DateTime>] -LoginName <String> -OutputFolder <String> [<CommonParameters>] -``` - -## DESCRIPTION - -Export the query logs for a user in an Office 365 tenant. The result of the export is stored in the current working folder or a specified folder, in the two files loginName_queries.csv and loginName_personalQueries.csv. - -The output of the queries.csv will be for example: - -| QueryTime | QueryText | -| ------------- | ------------- | -| 5/31/2018 09:16 | Querytext1 | -| 5/31/2018 08:16 | Querytext2 | - -You have to be a tenant admin to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Export-SPOQueryLogs -LoginName user1@contoso.sharepoint.com -``` - -Example 1 exports the query log for a user who has the e-mail address user1@contoso.sharepoint.com to the two files user1@contoso.sharepoint.com_queries.csv and user1@contoso.sharepoint.com_personalQueries.csv, in the current working folder. - -### ------------ Example 2 -------------------- - -````powershell -Export-SPOQueryLogs -LoginName user1@contoso.sharepoint.com -StartTime "2018-10-21" -OutputFolder "c:\users\contosoadmin\Documents" -``` - -Example 2 exports the query log from the starting time 21. October 2018, for a user who has the e-mail address user1@contoso.sharepoint.com, to the two files user1@contoso.sharepoint.com_queries.csv and user1@contoso.sharepoint.com_personalQueries.csv, in the folder c:\users\contosoadmin\Documents. - -## PARAMETERS - -### -LoginName - -Specifies the login name of the user to export. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputFolder - -Target folder where the CSV file is generated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartTime - -Specifies from which point of time to export the logs from. Use the date format YYYY-MM-DD. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell?view=sharepoint-ps) - -[Set up the SharePoint Online Management Shell Windows PowerShell environment](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserInfo.md b/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserInfo.md deleted file mode 100644 index 45f33cdc24..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserInfo.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/export-spouserinfo -applicable: SharePoint Online -title: Export-SPOUserInfo -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Export-SPOUserInfo - -## SYNOPSIS - -Export user information from site user information list. - -## SYNTAX - -```powershell -Export-SPOUserInfo -LoginName <String> -Site <SpoSitePipeBind> -OutputFolder <String> [<CommonParameters>] -``` - -## DESCRIPTION - -Export user information from site user information list. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Export-SPOUserInfo -LoginName joe.healy@contoso.com -site https://contoso.sharepoint.com/sites/sc1 -OutputFolder "C:\users\admin\exportfolder" -``` - -Example 1 exports a user data who has the e-mail address joe.healy@contoso.com from the site collection <https://contoso.sharepoint.com/sites/sc1> to folder C:\users\admin\exportfolder. - -### ------------ Example 2 -------------------- - -```powershell -$sites = Get-SPOSite -IncludePersonalSite $true -$user = "joe.healy@contoso.com" -foreach ($site in $sites) -{ -Export-SPOUserInfo -LoginName $user -site $site.Url -OutputFolder -"C:\users\admin\exportfolder" -} -``` - -Example 2 exports user data who has email address joe.healy@contoso.com from all site collections to folder C:\users\admin\exportfolder. - -## PARAMETERS - -### -LoginName - -Specifies the login name of the user to export. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the URL of the site collection to which you want to export the user. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputFolder - -Target folder where the CSV file is generated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[New-SPOSiteGroup](New-SPOSiteGroup.md) - -[Get-SPOUser](Get-SPOUser.md) - -[Set-SPOUser](Set-SPOUser.md) - -[Remove-SPOUser](Remove-SPOUser.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserProfile.md b/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserProfile.md deleted file mode 100644 index f70b2ab528..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserProfile.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/export-spouserprofile -applicable: SharePoint Online -title: Export-SPOUserProfile -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Export-SPOUserProfile - -## SYNOPSIS - -Export user profile data to csv file. - -## SYNTAX - -```powershell -Export-SPOUserProfile -LoginName <String> -OutputFolder <String> [<CommonParameters>] -``` - -## DESCRIPTION - -Export user profile data to csv file. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Export-SPOUserProfile -LoginName joe.healy@contoso.com -OutputFolder "C:\users\admin\exportfolder" -``` - -Example 1 exports user data who has the e-mail address joe.healy@contoso.com to a folder "C:\users\admin\exportfolder". - -## PARAMETERS - -### -LoginName - -Specifies the login name of the user who's data is exported. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputFolder - -Specifies the output folder location where the CSV file is created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Export-SPOUserInfo](Export-SPOUserInfo.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppErrors.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppErrors.md deleted file mode 100644 index b4deb5e208..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppErrors.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoapperrors -applicable: SharePoint Online -title: Get-SPOAppErrors -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOAppErrors - -## SYNOPSIS - -Returns application errors. - -## SYNTAX - -```powershell -Get-SPOAppErrors [-EndTimeInUtc <DateTime>] -ProductId <Guid> [-StartTimeInUtc <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Get-SPOAppErrors` cmdlet returns application monitoring errors (if available) for the application that is specified by ProductId between StartTimeInUtc in Coordinated Universal Time (UTC) and EndTimeInUtc in UTC. - -Based on server configuration, errors are available for a limited time. -The default is seven days. -Older errors are purged. -Date time values that are older than 50 years or later than 20 years from today are considered invalid - -Each error includes the error message, time in UTC that error happened, the site where the error happened, and the error type. -Values for error type are as follows: 0 - None, 1 - Install Error, 2 - Upgrade Error, 3 - Runtime Error. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Get-SPOAppErrors -ProductId ba51729b-e017-409d-681a-66f1dd18f0f4 -``` - -This example returns a collection of monitoring error message(s) for application whose GUID is ba51729b-e017-409d-681a-66f1dd18f0f4. - -## PARAMETERS - -### -EndTimeInUtc - -Specifies the end time in UTC to search for monitoring errors. If no end time is given, the default value current time in UTC is used. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProductId - -Specifies the application's GUID. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartTimeInUtc - -Specifies the start time in UTC to search for monitoring errors (for example, 01032011:12:00). If no start time is given, the default value 72 hours before the current time is used. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppInfo](Get-SPOAppInfo.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppInfo.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppInfo.md deleted file mode 100644 index 53ec23a094..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppInfo.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoappinfo -applicable: SharePoint Online -title: Get-SPOAppInfo -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOAppInfo - -## SYNOPSIS - -Returns all installed applications. - -## SYNTAX - -```powershell -Get-SPOAppInfo [[-ProductId] <Guid>] [[-Name] <String>] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Get-SPOAppInfo` cmdlet gets all the installed applications from an external marketplace or from the App Catalog that contain Name in their application names or the installed application with mentioned ProductId. ProductId takes precedence if not empty. - -Either ProductId or Name must be given. Name is ignored if ProductId is specified. - -The returned collection of installed applications contains Product ID (GUID), Product name and Source. Values for source type are as follows: 0 = App Catalog and 1 = Marketplace. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832.> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Get-SPOAppInfo -Name "Excel Service" -``` - -Example 1 returns all the installed applications from the external marketplace or from the App Catalog that contain "Excel Service" in their application names. - -### ------------ Example 2 -------------------- - -```powershell -Get-SPOAppInfo -ProductId 6751729b-e017-409d-681a-66f1dd18f0ff -``` - -Example 2 returns the installed application that has the GUID 6751729b-e017-409d-681a-66f1dd18f0ff. - -### ------------ Example 3 -------------------- - -```powershell -Get-SPOAppInfo -Name " " | Sort Name -``` - -Example 3 returns all the installed applications that have a space in the name and sorts them in ascending order. - -## PARAMETERS - -### -Name - -Specifies the application's name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProductId - -Specifies the application's GUID. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBrowserIdleSignOut.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBrowserIdleSignOut.md deleted file mode 100644 index 87f98ad137..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBrowserIdleSignOut.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spobrowseridlesignout -applicable: SharePoint Online -title: Get-SPOBrowserIdleSignOut -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOBrowserIdleSignOut - -## SYNOPSIS - -. - -## SYNTAX - -```powershell -Get-SPOBrowserIdleSignOut [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to retrieve the current configuration values for Idle session sign-out policy, the time at which users are warned and subsequently signed out of Office 365 after a period of browser inactivity in SharePoint and OneDrive. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOBrowserIdleSignOut -``` - -This example retrieves the current configuration values for Idle session sign-out - -## 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBuiltInDesignPackageVisibility.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBuiltInDesignPackageVisibility.md deleted file mode 100644 index bf3e6cc0d8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBuiltInDesignPackageVisibility.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spobuiltindesignpackagevisibility -applicable: SharePoint Online -title: Get-SPOBuiltInDesignPackageVisibility -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOBuiltInDesignPackageVisibility - -## SYNOPSIS - -Gets the visibility of the available built-in Design Packages. - -## SYNTAX - -```powershell -Get-SPOBuiltInDesignPackageVisibility [-DesignPackage <DesignPackageType>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to retrieve the current visibility state of each built-in design package. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOBuiltInDesignPackageVisibility -DesignPackage Showcase -``` - -This example retrieves the current visibility state of Showcase built-in design package. - -### Example 2 - -```powershell -Get-SPOBuiltInDesignPackageVisibility -``` - -This example retrieves the current visibility state of each built-in design package. - -## PARAMETERS - -### -DesignPackage - -Name of the design package, available names are -- Topic -- Showcase -- Blank -- TeamSite - -```yaml -Type: DesignPackageType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoMoveReport.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoMoveReport.md deleted file mode 100644 index 9afac222a0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoMoveReport.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spocrossgeomovereport -applicable: SharePoint Online -title: Get-SPOCrossGeoMoveReport -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOCrossGeoMoveReport - -## SYNOPSIS - -Provides a report of objects moved between geo locations. - -## SYNTAX - -```powershell -Get-SPOCrossGeoMoveReport -MoveJobType <JobType> [-Limit <uint32>] [-MoveStartTime <datetime>] [-MoveEndTime <datetime>] [-MoveState <MoveState>] [-MoveDirection <MoveDirection>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to return a report of objects moved between geo locations based on the specified parameters. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOCrossGeoMoveReport -MoveJobType SiteMove -MoveState Failed -``` - -This example returns the failed site moves between geo locations. - -## PARAMETERS - -### -MoveJobType - -The type of job to limit the report to. Valid values are: - -* GroupMove -* SiteMove -* UserMove - -```yaml -Type: JobType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit - -Limit the number of items to return for the report. - -```yaml -Type: uint32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveStartTime - -The start time to limit the move report to. - -```yaml -Type: datetime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveEndTime - -The end time to limit the move report to. - -```yaml -Type: datetime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveState - -The type of state to limit the report to. Valid values are: - -* All -* Failed -* InProgress -* NotStarted -* NotSupported -* Queued -* Rescheduled -* Stopped -* Success - -```yaml -Type: MoveState -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveDirection - -The direction of the move to limit the report to. Valid values are: - -* All -* MoveIn -* MoveOut - -```yaml -Type: MoveDirection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoMovedUsers.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoMovedUsers.md deleted file mode 100644 index e0031c8cea..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoMovedUsers.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spocrossgeomovedusers -applicable: SharePoint Online -title: Get-SPOCrossGeoMovedUsers -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOCrossGeoMovedUsers - -## SYNOPSIS - -In a multi-geo tenant returns the SharePoint Online user (or users) that had been moved. - -## SYNTAX - -```powershell -Get-SPOCrossGeoMovedUsers -Direction <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet allows you to get the moved users out and in the current SPO Site. It requires a connection to a multi-geo tenant to run correctly. You must be a SharePoint Online global Administrator to get the moved users out and in the current SPO site. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOCrossGeoMovedUsers -Direction MoveIn -``` - -Get the cross users that have been moved in the current SPO site - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Get-SPOCrossGeoMovedUsers -Direction MoveOut -``` - -Get the cross users that have been moved out the current SPO site - -## PARAMETERS - -### -Direction - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Accepted values: MoveIn, MoveOut -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoUsers.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoUsers.md deleted file mode 100644 index a82a00a365..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOCrossGeoUsers.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spocrossgeousers -applicable: SharePoint Online -title: Get-SPOCrossGeoUsers -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOCrossGeoUsers - -## SYNOPSIS - -Returns the SharePoint Online users in a multi-geo tenant that match the criteria. - -## SYNTAX - -```Powershell -Get-SPOCrossGeoUsers -ValidDataLocation <Boolean> [<CommonParameters>] -``` - -## DESCRIPTION - -The Get-SPOCrossGeoUsers cmdlet is used to return the SharePoint Online users that match a given criteria. The ValidDataLocation parameter is a switch used to validate the location of the data. This cmdlet requires a connection to a multi-geo tenant to run correctly. You must be a SharePoint Online global Administrator to run this cmdlet. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```Powershell -Get-SPOCrossGeoUsers -ValidDataLocation -``` - -Returns all of the SharePoint Online users in a multi-geo tenant and validates the data location. - -### -----------------------EXAMPLE 2----------------------------- - -```Powershell -Get-SPOCrossGeoUsers -``` - -Returns all of the SharePoint Online users in a multi-geo tenant without validating data location. - -## PARAMETERS - -### -ValidDataLocation - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[ConvertTo-SPOMigrationTargetedPackage](ConvertTo-SPOMigrationTargetedPackage.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPODataEncryptionPolicy.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPODataEncryptionPolicy.md deleted file mode 100644 index c2c0369f1c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPODataEncryptionPolicy.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spodataencryptionpolicy -applicable: SharePoint Online -title: Get-SPODataEncryptionPolicy -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPODataEncryptionPolicy - -## SYNOPSIS - -. - -## SYNTAX - -```powershell -Get-SPODataEncryptionPolicy [-Identity] <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-DataEncryptionPolicy cmdlet to view customer encryption status for your geo tenant. - -For more information, see [Controlling your data in Office 365 using Customer Key](https://docs.microsoft.com/en-us/microsoft-365/compliance/controlling-your-data-using-customer-key) - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPODataEncryptionPolicy -Identity https://contoso-admin.sharepoint.com -``` - -The output from this cmdlet includes: - -- The URI of the primary key. - -- The URI of the secondary key. - -- The encryption status for the geo. Possible states include: - - - **Unregistered:** Customer Key encryption has not yet been applied. - - - **Registering:** Customer Key encryption has been applied and your files are in the process of being encrypted. If your geo is in this state, you'll also be shown information on what percentage of sites in the geo are complete so that you can monitor encryption progress. - - - **Registered:** Customer Key encryption has been applied, and all files in all sites have been encrypted. - - - **Rolling:** A key roll is in progress. If your geo is in this state, you'll also be shown information on what percentage of sites have completed the key roll operation so that you can monitor progress. - -## PARAMETERS - -### -Identity - -Specifies the URL of the admin site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPODeletedSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPODeletedSite.md deleted file mode 100644 index 69a9cd1831..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPODeletedSite.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spodeletedsite -applicable: SharePoint Online -title: Get-SPODeletedSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPODeletedSite - -## SYNOPSIS - -Returns all deleted site collections from the Recycle Bin. - -## SYNTAX - -### ParameterSetPersonalSitesOnly - -```powershell -Get-SPODeletedSite [[-Identity] <SpoSitePipeBind>] [-IncludeOnlyPersonalSite] [-Limit <String>] [<CommonParameters>] -``` - -### ParameterSetAllSites - -```powershell -Get-SPODeletedSite [[-Identity] <SpoSitePipeBind>] [-IncludePersonalSite] [-Limit <String>] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Get-SPODeletedSite` cmdlet returns all deleted site collections that match the given criteria from the Recycle Bin. - -By default the cmdlet only returns site and site collections that are not Personal Sites (My Sites). -To include personal sites, use the IncludePersonalSite parameter. -To return only Personal Sites, use the IncludeOnlyPersonalSite parameter. - -These two Switch Parameters are in different parameter sets, so you can only use either one of them but not both. - -This action does not restore these returned sites or site collection. -It only returns their properties so that you can see what sites or site collections have been deleted. -To restore the site or site collections, forward the results to the `Restore-SPODeletedSite` cmdlet in the pipeline. - -You must be a SharePoint Online global administrator and a site collection administrator for the deleted site collections to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Get-SPODeletedSite -IncludePersonalSite -``` - -The command in this example returns all deleted site collections from the Recycle Bin including Personal Sites. - -## PARAMETERS - -### -IncludeOnlyPersonalSite - -Use this switch parameter to only include Personal Sites in the returned results. - -```yaml -Type: SwitchParameter -Parameter Sets: ParameterSetPersonalSitesOnly -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the URL of the deleted site collection to be returned. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IncludePersonalSite - -Use this switch parameter to include Personal Sites with the returned results. - -```yaml -Type: SwitchParameter -Parameter Sets: ParameterSetAllSites -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit - -Specifies the maximum number of site collections to return. -It can be any number. -To retrieve all site collections, use ALL. -The default value is 200. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Restore-SPODeletedSite](Restore-SPODeletedSite.md) - -[Remove-SPODeletedSite](Remove-SPODeletedSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.md deleted file mode 100644 index 5b275955e6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoexternaluser -applicable: SharePoint Online -title: Get-SPOExternalUser -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOExternalUser - -## SYNOPSIS - -Returns external users in the tenant. - -## SYNTAX - -```powershell -Get-SPOExternalUser [[-Position] <Int32>] [[-PageSize] <Int32>] [[-Filter] <String>] [[-SortOrder] <SortOrder>] [[-SiteUrl] <String>] [-ShowOnlyUsersWithAcceptingAccountNotMatchInvitedAccount <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Get-SPOExternalUser` cmdlet returns external users that are located in the tenant based on specified criteria. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251832](https://go.microsoft.com/fwlink/p/?LinkId=251832). - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOExternalUser -Position 0 -PageSize 2 -``` - -Example 1 returns the first two external users in the collection. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Get-SPOExternalUser -Position 2 -PageSize 2 -``` - -Example 2 returns two external users from the third page of the collection. - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -Get-SPOExternalUser -Position 0 -PageSize 30 -SiteUrl https://contoso.sharepoint.com -``` - -Example 3 returns the first 30 users that match the SiteUrl <https://contoso.sharepoint.com>. - -## PARAMETERS - -### -Filter - -Limits the results to only those users whose first name, last name, or email address begins with the text in the string using a case-insensitive comparison. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSize - -Specifies the maximum number of users to be returned in the collection. - -The value must be less than or equal to 50. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Position - -Use to specify the zero-based index of the position in the sorted collection of the first result to be returned. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteUrl - -Specifies the site to retrieve external users for. - -If no site is specified, the external users for all sites are returned. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortOrder - -Specifies the sort results in Ascending or Descending order on the SPOUser.Email property should occur. - -```yaml -Type: SortOrder -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowOnlyUsersWithAcceptingAccountNotMatchInvitedAccount - -Shows users who have accepted an invite but not using the account the invite was sent to. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Remove-SPOExternalUser](Remove-SPOExternalUser.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.md deleted file mode 100644 index 5dddabc167..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spogeoadministrator -applicable: SharePoint Online -title: Get-SPOGeoAdministrator -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOGeoAdministrator - -## SYNOPSIS - -This cmdlet returns the SharePoint Online user or security group accounts with global administrative privileges in the current Multi-Geographics tenant. - -## SYNTAX - -```powershell -Get-SPOGeoAdministrator [<CommonParameters>] -``` - -## DESCRIPTION - -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets [https://go.microsoft.com/fwlink/?LinkID=187810](https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Get-SPOGeoAdministrator` cmdlet has a single parameter set and matches a user or a list of users which has the ability to do changes globally in the geo location that you are connected to. - -Running this cmdlet on a non-multi-geo tenant organization will return error -4. - -You must be a SharePoint Online or global administrator and you must have a the Multi-Geo Capabilities in Office 365 service plan to run the `Get-SPOGeoAdministrator` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251832](https://go.microsoft.com/fwlink/p/?LinkId=251832). - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOGeoAdministrator -``` - -This cmdlet will output a SharePoint Online user or security group that is Multi-Geographic administrators on the current multi-geo tenant. - -## 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/?LinkID=113216). - -## RELATED LINKS - -[Add or remove a geo administrator](https://docs.microsoft.com/Office365/Enterprise/add-a-sharepoint-geo-admin) - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Add-SPOGeoAdministrator](Add-SPOGeoAdministrator.md) - -[Remove-SPOGeoAdministrator](Remove-SPOGeoAdministrator.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoMoveCrossCompatibilityStatus.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoMoveCrossCompatibilityStatus.md deleted file mode 100644 index 7f73c785e0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoMoveCrossCompatibilityStatus.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spogeomovecrosscompatibilitystatus -applicable: SharePoint Online -title: Get-SPOGeoMoveCrossCompatibilityStatus -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOGeoMoveCrossCompatibilityStatus - -## SYNOPSIS - -This cmdlet returns the compatibility status between geographic locations. - -## SYNTAX - -```powershell -Get-SPOGeoMoveCrossCompatibilityStatus [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet returns the compatibility between sites and locations for a move in a multi-geo SharePoint Online tenant. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Get-SPOGeoMoveCrossCompatibilityStatus -``` - -Get the compatibility status for all locations. - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.md deleted file mode 100644 index 3598bb28a3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spogeostoragequota -applicable: SharePoint Online -title: Get-SPOGeoStorageQuota -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOGeoStorageQuota - -## SYNOPSIS - -This cmdlet gets the storage quota on a multi-geo tenant. - -## SYNTAX - -```Powershell -Get-SPOGeoStorageQuota [-AllLocations] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet shows the storage on the current location or all locations in a multi-geo tenant. - -This Cmdlet requires a connection to a multi-geo tenant to run correctly. You must be a SharePoint Online global Administrator to get the storage on current location or all locations in a multi-geo SPO tenant. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```Powershell -Get-SPOGeoStorageQuota -AllLocations -``` - -Get the storage size quota of all locations. - -### -----------------------EXAMPLE 2----------------------------- - -```Powershell -Get-SPOGeoStorageQuota -``` - -Get the storage size quota of the current location. - -## PARAMETERS - -### -AllLocations - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Set-SPOGeoStorageQuota](set-SPOGeoStorageQuota.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHideDefaultThemes.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHideDefaultThemes.md deleted file mode 100644 index 8030cfec76..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHideDefaultThemes.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spohidedefaultthemes -applicable: SharePoint Online -title: Get-SPOHideDefaultThemes -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOHideDefaultThemes - -## SYNOPSIS - -Queries the current SPOHideDefaultThemes setting. SPO stands for SharePoint Online. - -## DESCRIPTION - -The **Get-SPOHideDefaultThemes** cmdlet retrieves the current **Set-SPOHideDefaultThemes** setting. You might want to use this cmdlet in a PowerShell script to read the setting and then take different actions based on whether the default themes are hidden. This cmdlet does not have any parameters. - -> [!NOTE] -> This cmdlet was named **Get-HideDefaultThemes** until the December 2017 release of the SPO Management Shell. We recommend that you use the latest version of the PowerShell cmdlets. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOHideDefaultThemes -``` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Set-SPOHideDefaultThemes](Set-SPOHideDefaultThemes.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHomeSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHomeSite.md deleted file mode 100644 index 819c82cac2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHomeSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spohomesite -applicable: SharePoint Online -title: Get-SPOHomeSite -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOHomeSite - -## SYNOPSIS - -Returns the home site url for your tenant. - -## SYNTAX - -```powershell -Get-SPOHomeSite [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to get the home site url for your tenant. - -## EXAMPLES - -### Example 1 - -```powershell -Get-PnPHomeSite -``` - -This example returns the home site url for your tenant. - -## 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHubSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHubSite.md deleted file mode 100644 index 9965ff0448..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHubSite.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spohubsite -applicable: SharePoint Online -title: Get-SPOHubSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOHubSite - -## SYNOPSIS - -Lists hub sites or hub site information. - -## SYNTAX - -```powershell -Get-SPOHubSite [-Identity] <SpoHubSitePipeBind> -[<CommonParameters>] -``` - -## DESCRIPTION - -Lists all hub sites found on the SharePoint tenant. If you provide **-Identity** the cmdlet returns detailed information about the specific hub. You can find which hub a site is associated with by providing the site's identity with this cmdlet. - -If the hub site doesn't exist, this cmdlet returns a "File not found" error. - -> [!NOTE] -> If a deleted hub site appears in the output of this cmdlet you may not have run [Unregister-SPOHubSite](https://docs.microsoft.com/powershell/module/sharepoint-online/unregister-spohubsite) on the deleted hub site. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOHubSite -``` - -This example lists all hub sites in the tenant. - -### Example 2 - -```powershell -Get-SPOHubSite -Identity https://contoso.sharepoint.com/sites/online-marketing - -ID : 44252d09-62c4-4913-9eb0-a2a8b8d7f863 -Title : Marketing Hub -SiteId : 44252d09-62c4-4913-9eb0-a2a8b8d7f863 -SiteUrl : https://contoso.sharepoint.com/sites/Marketing -LogoUrl : https://contoso.sharepoint.com/sites/Marketing/SiteAssets/hublogo.png -Description : Hub for the Marketing division -Permissions : {Wilke, Nestor} -SiteDesignId : 00000000-0000-0000-0000-000000000000 -RequiresJoinApproval : False -HideNameInNavigation : False -``` - -This example begins with the online-marketing site. The cmdlet finds the associated hub site, which is marketing. Then it lists all the details about the marketing hub site. - -## PARAMETERS - -### -Identity - -URL of the hub site. If not specified, the cmdlet lists all hub sites in the tenant. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMigrationJobProgress.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMigrationJobProgress.md deleted file mode 100644 index dab89d4f5a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMigrationJobProgress.md +++ /dev/null @@ -1,238 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spomigrationjobprogress -applicable: SharePoint Online -title: Get-SPOMigrationJobProgress -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOMigrationJobProgress - -## SYNOPSIS - -This cmdlet lets you report on SPO migration jobs that are in progress. - -## SYNTAX - -### AzureLocationsInline - -```powershell -Get-SPOMigrationJobProgress -AzureQueueUri <String> -Credentials <CredentialCmdletPipeBind> - [-DontWaitForEndJob] [-EncryptionParameters <EncryptionParameters>] [-JobIds <Guid[]>] [-NoLogFile] - [-TargetWebUrl <String>] [<CommonParameters>] -``` - -### AzureLocationsImplicit - -``` -Get-SPOMigrationJobProgress -Credentials <CredentialCmdletPipeBind> [-DontWaitForEndJob] - [-EncryptionParameters <EncryptionParameters>] [-JobIds <Guid[]>] - -MigrationPackageAzureLocations <MigrationPackageAzureLocations> [-NoLogFile] [-TargetWebUrl <String>] - [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet lets you report on SPO migration jobs that are in progress. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -$myQueueUri = <uri to azure report queue> - -Get-SPOMigrationJobProgress -AzureQueueUri $myQueueUri -``` - -This will report on ALL jobs within the report queue. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -$jobIds = @(<jobid1>,<jobId2>....) - -Get-SPOMigrationJobProgress -AzureQueueUri $myQueueUri -JobIds $jobIds -``` - -This will report only jobs defined within the $jobIds collection from the report queue. - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -$targetWebUrl = <myTargetWebUrl> -$creds = <my site credentials> - -Get-SPOMigrationJobProgress - AzureQueueUri $myQueueUri - TargetWebUrl $targetWebUrl -Credentials $creds -``` - -This will report on any currently queued or in progress jobs and wait for all jobs to complete. - -### -----------------------EXAMPLE 4----------------------------- - -```powershell -$targetWebUrl = <myTargetWebUrl> -$creds = <my site credentials> - -Get-SPOMigrationJobProgress - AzureQueueUri $myQueueUri - TargetWebUrl $targetWebUrl -Credentials $creds -DontWaitForJobEnd -``` - -This will report on any currently queued or in progress jobs and not wait for all jobs to complete. - -## PARAMETERS - -### -AzureQueueUri - -An optional fully qualified URL and SAS token representing the Azure Storage Reporting Queue where import operations will list events during import. - -```yaml -Type: String -Parameter Sets: AzureLocationsInline -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credentials - -Optional credentials of a site collection administrator to use to connect to the site collection. The credentials should supply the username in UPN format (e.g. user@company.onmicrosoft.com). If this property is not set, the current tenant admin credentials from the session's previous call to `Connect-SPOService` will be used to connect to the site collection. - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DontWaitForEndJob - -Tells the cmdlet to not wait for the job to end. It will only process as many messages as are currently in the queue and then terminate. If this flag is set to $false, it will wait for the job to end before terminating. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptionParameters - -PARAMVALUE: EncryptionParameters - -```yaml -Type: EncryptionParameters -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobIds - -Id of a previously created migration job that exists on the target site collection. - -```yaml -Type: Guid[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MigrationPackageAzureLocations - -A set of fully qualified URLs and SAS tokens representing the Azure Blob Storage containers that hold the package content and metadata files and an optional Azure Storage Reporting Queue. This object is returned during successful processing of the `Set-SPOMigrationPackageAzureSource` - -```yaml -Type: MigrationPackageAzureLocations -Parameter Sets: AzureLocationsImplicit -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -Indicates to not create a log file. The default is to create a new CopyMigrationPackage log file within the directory specified within the SourcePackagePath parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetWebUrl - -The fully qualified target web URL where the package will be imported into. This must include the same TargetWebURL that was used during `ConvertTo-SPOMigrationTargetedPackage`. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMigrationJobStatus.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMigrationJobStatus.md deleted file mode 100644 index 77671f9867..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMigrationJobStatus.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spomigrationjobstatus -applicable: SharePoint Online -title: Get-SPOMigrationJobStatus -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOMigrationJobStatus - -## SYNOPSIS - -Use this cmdlet to monitor the status of a submitted SharePoint Online migration job. - -## SYNTAX - -```powershell -Get-SPOMigrationJobStatus -Credentials <CredentialCmdletPipeBind> [-JobId <Guid>] [-NoLogFile] - -TargetWebUrl <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet will check the status of a migration job. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -$targetWebUrl = "https://contoso.sharepoint.com/sites/migrationtest" -$credentials = Get-Credential -Get-SPOMigrationJobStatus -TargetWebUrl $targetWebUrl -Credentials $credentials -JobId "779c4b3b-ec24-4705-bb58-c38f4329418c" -``` - -Get the status of your SPO Migration Job. -You can obtain the Job id when submit package data to create new SPO migration job via the Invoke-SPOMigrationEncryptUploadSubmit cmdlet - -## PARAMETERS - -### -Credentials - -The credentials of a site collection administrator to use to connect to the site collection. The credentials should supply the username in UPN format (e.g. user@company.onmicrosoft.com). If this property is not set, the current tenant admin credentials from the session's previous call to `Connect-SPOService` will be used to connect to the site collection. - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobId - -(optional) The ID of a migration job that exists on the target site collection. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -(optional) Indicates to not create a log file. The default is to create a new DeleteMigrationJob log file within the current directory. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetWebUrl - -The fully qualified target web URL where the package will be imported. This must include the same TargetWebUrl that was used during `ConvertTo-SPOMigrationTargetedPackage`. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMultiGeoCompanyAllowedDataLocation.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMultiGeoCompanyAllowedDataLocation.md deleted file mode 100644 index 0e69ed4d88..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMultiGeoCompanyAllowedDataLocation.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spomultigeocompanyalloweddatalocation -applicable: SharePoint Online -title: Get-SPOMultiGeoCompanyAllowedDataLocation -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOMultiGeoCompanyAllowedDataLocation - -## SYNOPSIS - -Returns the SharePoint Online Multi geo allowed data locations. - -## SYNTAX - -```powershell -Get-SPOMultiGeoCompanyAllowedDataLocation [<CommonParameters>] -``` - -## DESCRIPTION - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOMultiGeoCompanyAllowedDataLocation -``` - -This example returns the SharePoint Online Multi geo allowed data locations. - -## 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMultiGeoExperience.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMultiGeoExperience.md deleted file mode 100644 index efc2819cce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOMultiGeoExperience.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spomultigeoexperience -applicable: SharePoint Online -title: Get-SPOMultiGeoExperience -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOMultiGeoExperience - -## SYNOPSIS - -. - -## SYNTAX - -```powershell -Get-SPOMultiGeoExperience [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to get the multi geo experience mode. For more information see [Enabling SharePoint Multi-Geo in your satellite geo location](https://docs.microsoft.com/office365/enterprise/enabling-sp-multigeo-satellite-geolocation) - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOMultiGeoExperience -``` - -This example will show you whether the geo location is in SPO or ODB mode. - -## 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgAssetsLibrary.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgAssetsLibrary.md deleted file mode 100644 index 8a18210ae5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgAssetsLibrary.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoorgassetslibrary -applicable: SharePoint Online -title: Get-SPOOrgAssetsLibrary -author: Maralesfahanpoor -ms.author: maesfaha -ms.reviewer: -manager: paulac -schema: 2.0.0 ---- - -# Get-SPOOrgAssetsLibrary - -## SYNOPSIS - -Displays information about all libraries designated as locations for organization assets. - -## SYNTAX - -```powershell -Get-SPOOrgAssetsLibrary [<CommonParameters>] -``` - -## DESCRIPTION - -The Get-SPOOrgAssetsLibrary cmdlet displays information about all libraries designated as locations for organization assets. - -Once this cmdlet is run, it will display the name and URL of the site where assets are originally stored, as well as the display name, server relative library URL, list ID, OrgAssetType and thumbnail URL for any associated libraries. - -## EXAMPLES - -### Example 1 - -This example displays the name and URL of the site where assets are originally stored. It also provides a list of any associated libraries and shows the respective display name, server relative library URL, list ID, OrgAssetType and thumbnail URL. - -```powershell -Get-SPOOrgAssetsLibrary -``` - -## PARAMETERS - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/add-spoorgassetslibrary?view=sharepoint-ps) - -[Set-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/set-spoorgassetslibrary?view=sharepoint-ps) - -[Remove-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spoorgassetslibrary?view=sharepoint-ps) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgNewsSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgNewsSite.md deleted file mode 100644 index 9630054aab..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgNewsSite.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoorgnewssite -applicable: SharePoint Online -title: Get-SPOOrgNewsSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen ---- - -# Get-SPOOrgNewsSite - -## SYNOPSIS - -Lists URLs of all the configured organizational news sites. Requires Tenant administrator permissions. - -## SYNTAX - -```powershell -Get-SPOOrgNewsSite [<CommonParameters>] -``` - -## DESCRIPTION - -Lists URLs of all the organizational authoritative news sites. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Get-SPOOrgNewsSite -``` - -The example returns a list of organizational news sites from the Tenant. - -## 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-SPOOrgNewsSite](Set-SPOOrgNewsSite.md) - -[Remove-SPOOrgNewsSite](Remove-SPOOrgNewsSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPublicCdnOrigins.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPublicCdnOrigins.md deleted file mode 100644 index c53c9bdc10..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPublicCdnOrigins.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spopubliccdnorigins -applicable: SharePoint Online -title: Get-SPOPublicCdnOrigins -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOPublicCdnOrigins - -## SYNOPSIS - -This cmdlet returns a list of CDN Origins in your SharePoint Online Tenant - -## SYNTAX - -```powershell -Get-SPOPublicCdnOrigins [<CommonParameters>] -``` - -## DESCRIPTION - -List CDN Origins in your Tenant by id or url. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOPublicCdnOrigins | Fl - -Id : 16530053476cf3efe88b499076356d0205504b2451688c20a65d561c951783e0859ac590 -Url : HTTPS:/CONTOSO.SHAREPOINT.COM/SITES/CDN/CDNFILESLIBRARY -``` - -This example returns a list of CDN Origins. - -## 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[New-SPOPublicCdnOrigin](New-SPOPublicCdnOrigin.md) - -[Remove-SPOPublicCdnOrigin](Remove-SPOPublicCdnOrigin.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSite.md deleted file mode 100644 index 1ccb4776af..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSite.md +++ /dev/null @@ -1,268 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-sposite -applicable: SharePoint Online -title: Get-SPOSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSite - -## SYNOPSIS - -Returns one or more site collections. - -## SYNTAX - -### ParamSet1 - -```powershell -Get-SPOSite [[-Identity] <SpoSitePipeBind>] [-Detailed] [-Limit <String>] [<CommonParameters>] -``` - -### ParamSet2 - -```powershell -Get-SPOSite [-Detailed] [-Filter <String>] [-IncludePersonalSite <Boolean>] [-Limit <String>] - [-Template <String>] [<CommonParameters>] -``` - -### ParamSet3 - -```powershell -Get-SPOSite [-Identity] <SpoSitePipeBind> [-DisableSharingForNonOwnersStatus] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets. - -The `Get-SPOSite` cmdlet retrieves and returns properties of all site collections that match the given criteria. - -With version 5361 of the SharePoint Online Management Shell, you may experience the following: - -Additional site collections are now displayed. For example, all group and video sites along with team sites will be displayed. - -The Detailed parameter has been deprecated. It will continue to work with earlier versions - -> [!NOTE] -> Site collections in the Recycle Bin will not be retrieved by using the `Get-SPOSite` cmdlet. - -You need to be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [Intro to SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell?view=sharepoint-ps). - -> [!NOTE] -> If Site Collection Storage Management is enabled for the tenant, you will not be able to set quota and will have a generic error returned. To workaround this issue, set the site collection storage management to "manual" temporarily, set your quotas and then set the site collection storage management setting back to its original setting. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOSite -``` - -Example 1 returns all site collections. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Get-SPOSite -Identity https://contoso.sharepoint.com -``` - -Example 2 lists the site collection with detailed properties. - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -Get-SPOSite -Identity https://contoso.sharepoint.com -DisableSharingForNonOwnersStatus -``` - -Example 3 Updates status on if the non owners of a site collection can share the site collection (does not set this value). - -### -----------------------EXAMPLE 4----------------------------- - -```powershell -Get-SPOSite -Template GROUP#0 -IncludePersonalSite:$false -``` - -This example enumerates Group Site Collections in a tenant. - -### -----------------------EXAMPLE 5----------------------------- - -```powershell -Get-SPOSite -Identity https://contoso.sharepoint.com/sites/groupname -detailed |fl -``` - -This example gets quota details for a Group Site. - -## PARAMETERS - -### -Detailed - -Use this parameter to get additional property information on a site collection. You will notice a slower response time when the Detailed parameter is used. - -The following properties are returned: - ---ResourceUsageCurrent - ---ResourceUsageAverage - ---StorageUsageCurrent - ---LockIssue - ---WebsCount - ---CompatibilityLevel - ---AllowSelfServiceUpgrade - ---SiteDefinedSharingCapability-returns the stored value of the site policy. - ---SharingCapability --returns the effective access level (the site policy and the tenant policy combined. - -```yaml -Type: SwitchParameter -Parameter Sets: ParamSet1, ParamSet2 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableSharingForNonOwnersStatus - -This parameter prevents non-owners from sharing. - -> [!NOTE] -> This parameter is available only in SharePoint Online Management Shell Version 16.0.4613.1211 or later. - -```yaml -Type: SwitchParameter -Parameter Sets: ParamSet3 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter - -Specifies the script block of the server-side filter to apply. The type must be a valid filter name and value must be in the form `{$_PropertyName <operator> "filterValue"}`. Valid operators are as follows: eq, ne, like, notlike. - Currently, you can filter by these properties: Owner, Template, LockState, Url. - -> [!NOTE] -> The operator values are case-sensitive. - -```yaml -Type: String -Parameter Sets: ParamSet2 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the URL of the site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IncludePersonalSite - -Displays personal sites when value is set to $true. - -The values are $true and $false. By default, the value is $false which means no personal sites will be returned. - -```yaml -Type: Boolean -Parameter Sets: ParamSet2 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit - -Specifies the maximum number of site collections to return. It can be any number. To retrieve all site collections, use ALL. The default value is 200. - -```yaml -Type: String -Parameter Sets: ParamSet1, ParamSet2 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template - -Displays sites of a specific template. For example, STS, STS#0 or STS#1. - -```yaml -Type: String -Parameter Sets: ParamSet2 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Online.SharePoint.PowerShell.SpoSitePipeBind - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteCollectionAppCatalogs.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteCollectionAppCatalogs.md deleted file mode 100644 index 56767c7970..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteCollectionAppCatalogs.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositecollectionappcatalogs -applicable: SharePoint Online -title: Get-SPOSiteCollectionAppCatalogs -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOSiteCollectionAppCatalogs - -## SYNOPSIS - -Use this cmdlet to get the Site Collection App Catalog. - -## SYNTAX - -```powershell - Get-SPOSiteCollectionAppCatalogs [-Site] <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to get the Site Collection App Catalog. For more information, see [Use the App Catalog to make custom business apps available for your SharePoint environment](https://docs.microsoft.com/sharepoint/use-app-catalog) - -## EXAMPLES - -### Example 1 - -```powershell - Get-SPOSiteCollectionAppCatalogs -Site https://contoso.sharepoint.com/sites/Research -``` - -This example returns the Site Collection App Catalog for the site <https://contoso.sharepoint.com/sites/Research.> - -## PARAMETERS - -### -Site - -Url of the site - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteContentMoveState.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteContentMoveState.md deleted file mode 100644 index d3837bb086..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteContentMoveState.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositecontentmovestate -applicable: SharePoint Online -title: Get-SPOSiteContentMoveState -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteContentMoveState - -## SYNOPSIS - -This Cmdlet allows a SharePoint administrators to check the status of a site or group move. - -## SYNTAX - -### GroupName - -```powershell -Get-SPOSiteContentMoveState [-GroupName] <String> [<CommonParameters>] -``` - -### SourceSiteUrl - -```powershell -Get-SPOSiteContentMoveState [-SourceSiteUrl] <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This command gets the information and the status of a move request of a user between sites in a SharePoint Online Multi Geo tenant. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOSiteContentMoveState -GroupName "group@contoso.com" -``` - -Gets the status of the site content for the group "group@contoso.com" - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Get-SPOSiteContentMoveState -SourceSiteUrl $siteurl -``` - -Gets the status of the site content give on the variable $siteurl - -## PARAMETERS - -### -GroupName - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: GroupName -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceSiteUrl - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: SourceSiteUrl -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDataEncryptionPolicy.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDataEncryptionPolicy.md deleted file mode 100644 index 9f02c1c6c0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDataEncryptionPolicy.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositedataencryptionpolicy -applicable: SharePoint Online -title: Get-SPOSiteDataEncryptionPolicy -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOSiteDataEncryptionPolicy - -## SYNOPSIS - -Validates the encryption of a Group Site, Team Site, or OneDrive for Business site if a Customer Key has been registered for the site. - -## SYNTAX - -```powershell -Get-SPOSiteDataEncryptionPolicy [-Identity] <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -When a Customer Key has been configured in the Azure tenant, it is possible to set and subsequently verify the encryption status of a SharePoint Online or OneDrive for Business site. This cmdlet verifies the encryption status of the particular site. - -This cmdlet will return an error if the Azure tenant has not been configured with a Customer Key. See the Related Links section for more information on how to configure the Customer Key. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOSiteDataEncryptionPolicy https://contoso.sharepoint.com/sites/Research -``` - -Verifies the encryption of the site https://contoso.sharepoint.com/sites/Research. - -## PARAMETERS - -### -Identity - -The URL of the Site Collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## OUTPUTS -### System.String - -The URI of the primary key. - -### System.String - -The URI of the secondary key. - -### System.Object - -The encryption status for the geo. Possible states include: - -* Unregistered: Customer Key encryption has not yet been applied. -* Registering: Customer Key encryption has been applied and your files are in the process of being encrypted. If your geo is in this state, you'll also be shown information on what percentage of sites in the geo are complete so that you can monitor encryption progress. -* Registered: Customer Key encryption has been applied, and all files in all sites have been encrypted. -* Rolling: A key roll is in progress. If your geo is in this state, you'll also be shown information on what percentage of sites have completed the key roll operation so that you can monitor progress. - -## RELATED LINKS - -[Register-SPODataEncryptionPolicy](https://docs.microsoft.com/powershell/module/sharepoint-online/register-spodataencryptionpolicy) - -[Controlling your data in Office 365 using Customer Key](https://docs.microsoft.com/microsoft-365/compliance/controlling-your-data-using-customer-key) - -[Office 365: Setting up Customer Key for SharePoint Online and OneDrive for Business](https://docs.microsoft.com/microsoft-365/compliance/controlling-your-data-using-customer-key#office-365-setting-up-customer-key-for-sharepoint-online-and-onedrive-for-business) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesign.md deleted file mode 100644 index 099aa77e85..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesign.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositedesign -applicable: SharePoint Online -title: Get-SPOSiteDesign -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteDesign - -## SYNOPSIS - -Gets details about site designs that are on the SharePoint tenant. You can specify an ID of a specific site design to retrieve. If there are no parameters listed, details about all site designs are listed. - -## SYNTAX - -```powershell -Get-SPOSiteDesign [[-Identity] <SPOSiteDesignPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION - -Gets details about site designs that are on the SharePoint tenant. You can specify an ID of a specific site design to retrieve. If there are no parameters listed, details about all site designs are listed. - -## EXAMPLES - -### Example 1 - -This example and sample response show how to get site design details. - -```powershell -Get-SPOSiteDesign 44252d09-62c4-4913-9eb0-a2a8b8d7f863 - -Id : 44252d09-62c4-4913-9eb0-a2a8b8d7f863 -Title : Contoso - Team Project -WebTemplate : 64 -SiteScriptIds : {1306913c-8463-42ca-bd63-efad0fcdbba4} -Description : Use this design to apply Contoso theme and create - custom lists and add to nav -``` - -## PARAMETERS - -### -Identity - -The ID of the site design to retrieve. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRights.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRights.md deleted file mode 100644 index b47bef9d0f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRights.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositedesignrights -applicable: SharePoint Online -title: Get-SPOSiteDesignRights -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteDesignRights - -## SYNOPSIS - -Displays a list of principals and their rights for usage of the site design. This can be used to determine the scope that your site design has with users on the tenant. - -## SYNTAX - -```powershell -Get-SPOSiteDesignRights [-Identity] <SPOSiteDesignPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Displays a list of principals and their rights for usage of the site design. This can be used to determine the scope that your site design has with users on the tenant. - -## EXAMPLES - -### Example 1 - -This example gets the rights for a site design. - -```powershell -Get-SPOSiteDesignRights 607aed52-6d61-490a-b692-c0f58a6981a1 - -DisplayName PrincipalName Rights ------------ ------------- ------ -Nestor Wilke i:0#.f|membership|nestorw@contoso.onmicrosoft.com View -``` - -## PARAMETERS - -### -Identity - -The ID of the site design to get scoping information. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRun.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRun.md deleted file mode 100644 index 7d3801bd50..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRun.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.Online.SharePoint.PowerShell.dll-Help.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositedesignrun -applicable: SharePoint Online -title: Get-SPOSiteDesignRun -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteDesignRun - -## SYNOPSIS - -Retrieves a list of site designs applied to a specified site collection. - -## SYNTAX - -```powershell -Get-SPOSiteDesignRun [-WebUrl] <String> [[-SiteDesignId] <SPOSiteDesignPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION - -Retrieves a list of site designs applied to a specified site collection. The WebUrl is required to know which site collection to query. The returned output includes the ID of the scheduled job, the web and site IDs, and the site design ID, version, and title. - -## EXAMPLES - -### ------------ Example 1 -------------------- - -This example would return a list of the site designs applied to the specified site. Providing a specific site design ID will return the details for just that applied site design. - -```powershell -PS C:\> Get-SPOSiteDesignRun -WebUrl "https://contoso.sharepoint.com/sites/project-playbook" - -Id: | sean530z-55a3-4804-8b0a-80578626d6ef -SiteDesignId: | sean530b-4133-444e-9e31-fb0c07f69d3a -WebId: | 4f8509cd-7972-44d0-a14a-3c8ad69ee50f -SiteId: | d5d19d7c-sean-4625-9461-281bfc8a9ece -SiteDesignVersion: | 3 -SiteDesignTitle: | Contoso Project Playbook -``` - -## PARAMETERS - -### -SiteDesignId - -The ID of a specific site design. Use this optional parameter if you wish to only return details on a specific site design run. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebUrl - -The Url of the site collection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Online.SharePoint.PowerShell.SPOSiteDesignPipeBind - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPOSiteDesignRunStatus](Get-SPOSiteDesignRunStatus.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRunStatus.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRunStatus.md deleted file mode 100644 index 7fa2e661d6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignRunStatus.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.Online.SharePoint.PowerShell.dll-Help.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositedesignrunstatus -applicable: SharePoint Online -title: Get-SPOSiteDesignRunStatus -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteDesignRunStatus - -## SYNOPSIS - -Retrieves and displays a list of all site script actions executed for a specified site design applied to a site. - -## SYNTAX - -```powershell -Get-SPOSiteDesignRunStatus [-Run] <SPOSiteDesignRun> [<CommonParameters>] -``` - -## DESCRIPTION - -Retrieves and displays a list of all site script actions executed for a specified site design applied to a site. - -## EXAMPLES - -### Example 1 - -This example gets the run for a specific site design applied to a site and sets it to a variable. This variable is then passed into the command -run parameter. The result is a display of all the site script actions applied for that site design run, including the script action title and outcome. - -```powershell -$myrun = Get-SPOSiteDesignRun -WebUrl "https://contoso.sharepoint.com/sites/project-playbook" -SiteDesignId cefd782e-sean-4814-a68a-b33b116c302f - -Get-SPOSiteDesignRunStatus -Run $myrun - -OrdinalIndex: | 0 -SiteScriptId: | sean530b-4133-444e-9e31-fb0c07f69d3a -SiteScriptTitle: | project tracker script for contoso legal -SiteScriptIndex: | 0 -ActionIndex: | 0 -ActionTitle: | Add principal contoso legal team to SPGroup Owners. -ActionKey: | 4f8509cd-0000-0000-0000-00000000 -OutcomeCode: | Success -OutcomeText: | - -OrdinalIndex: | 1 -SiteScriptId: | sean530b-4133-444e-9e31-abc123abc123 -SiteScriptTitle: | project tracker script for contoso legal -SiteScriptIndex: | 0 -ActionIndex: | 1 -ActionTitle: | Apply theme Contoso Legal. -ActionKey: | 4f8509cd-0000-0000-0000-00000000 -OutcomeCode: | Success -OutcomeText: | -``` - -## PARAMETERS - -### -Run - -The site design run for the desired set of script action details. - -```yaml -Type: SPOSiteDesignRun -Parameter Sets: (All) -Aliases: - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Online.SharePoint.PowerShell.SPOSiteDesignRun - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPOSiteDesignRun](Get-SPOSiteDesignRun.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignTask.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignTask.md deleted file mode 100644 index 119d47d12b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDesignTask.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositedesigntask -applicable: SharePoint Online -title: Get-SPOSiteDesignTask -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteDesignTask - -## SYNOPSIS - -Cmdlet to get a scheduled site design script. - -## SYNTAX - -```powershell -Get-SPOSiteDesignTask -Identity <guid> -WebUrl <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Used to retrieve a scheduled site design script. It takes the ID of the scheduled site design and the URL fo the SPWeb where the site design is scheduled to be applied. - -> [!NOTE] -> This command only retrieves a previously scheduled request. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOSiteDesignTask -Identity 501z8c32-4147-44d4-8607-26c2f67cae82 -WebUrl "https://contoso.sharepoint.com/sites/projectawesome" -``` - -This example returns a scheduled site design whose ID is 501z8c32-4147-44d4-8607-26c2f67cae82 and which was applied on the site <https://contoso.sharepoint.com/sites/projectawesome>. - -## PARAMETERS - -### -Identity - -The ID of the scheduled site design to apply. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebUrl - -The URL of the site collection where the site design will be applied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## RELATED LINKS - -[Add-SPOSiteDesignTask](Get-SPOSiteDesignTask.md) - -[Get-SPOSiteDesignRun](Get-SPOSiteDesignRun.md) - -[Get-SPOSiteDesignRunStatus](Get-SPOSiteDesignRunStatus.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteGroup.md deleted file mode 100644 index 4f03cac332..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteGroup.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositegroup -applicable: SharePoint Online -title: Get-SPOSiteGroup -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteGroup - -## SYNOPSIS - -Gets all the groups on the specified site collection. - -## SYNTAX - -```powershell -Get-SPOSiteGroup [-Group <String>] [-Limit <Int32>] -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use the `Get-SPOSiteGroup` cmdlet to get all the groups on the specified site collection by using the Site parameter. - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [SharePoint Online PowerShell](https://docs.microsoft.com/powershell/module/sharepoint-online/index). - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOSiteGroup -Site https://contoso.sharepoint.com/sites/siteA -``` - -This example returns all the groups on the specified site collection <https://contoso.sharepoint.com/sites/siteA.> - -## PARAMETERS - -### -Group - -Specifies the group name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit - -Specifies the maximum number of site collections to return. To retrieve all of the site collections, use Limit ALL. The default value is 200. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the site collection scope. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Set-SPOSiteGroup](Set-SPOSiteGroup.md) - -[Remove-SPOSiteGroup](Remove-SPOSiteGroup.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteRenameState.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteRenameState.md deleted file mode 100644 index e8833c4b1e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteRenameState.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositerenamestate -applicable: SharePoint Online -title: Get-SPOSiteRenameState -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOSiteRenameState - -## SYNOPSIS - -Returns the current rename job state of a SharePoint Online Site. - -## SYNTAX - -### SourceSiteUrl - -```powershell -Get-SPOSiteRenameState -Identity <SpoSitePipeBind> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### RenameReport - -```powershell -Get-SPOSiteRenameState [-State <RenameState>] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to return the current rename job state of a SharePoint Online Site. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOSiteRenameState -Identity https://contoso.sharepoint.com/sites/ContosoWeb1 -``` - -This example returns the rename job state of ContosoWeb1 Site. - -### Example 2 - -```powershell -Get-SPOSiteRenameState -State InProgress -``` - -This example returns rename jobs that are in InProgress state. - -## PARAMETERS - -### -Identity - -The urls of the site to be renamed. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: SourceSiteUrl -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State - -The state of the rename job, possible values are - -- Success - -- InProgress - -- Fail - -```yaml -Type: RenameState -Parameter Sets: RenameReport, ParentId -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScript.md deleted file mode 100644 index 0c1e9538c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScript.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositescript -applicable: SharePoint Online -title: Get-SPOSiteScript -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteScript - -## SYNOPSIS - -Displays information about existing site scripts. When no parameter is provided, this cmdlet returns the **Id**, **Title**, **Description**, and **Version** of each site script. When a site script ID is provided, this cmdlet also returns the **Content**, which is the JSON of the site script. - -## SYNTAX - -```powershell -Get-SPOSiteScript [[-Identity] <SPOSiteScriptPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION - -Displays information about existing site scripts. When no parameter is provided, this cmdlet returns the **Id**, **Title**, **Description**, and **Version** of each site script. When a site script ID is provided, this cmdlet also returns the **Content**, which is the JSON of the site script. - -## EXAMPLES - -### Example 1 - -This example shows how to get script information for a specific script ID. - -```powershell -Get-SPOSiteScript 07702c07-0485-426f-b710-4704241caad9 - -Id : 07702c07-0485-426f-b710-4704241caad9 -Title : Contoso theme -Description : -Content : { - "$schema": "schema.json", - "actions": [ - { - "verb": "applyTheme", - "themeName": "Custom Cyan" - } - ], - "bindata": { }, - "version": 1 - } -Version : 1 -``` - -## PARAMETERS - -### -Identity - -The ID of the site script to get information about. - -```yaml -Type: SPOSiteScriptPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromList.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromList.md deleted file mode 100644 index d0047b4aaa..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromList.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositescriptfromlist -applicable: SharePoint Online -title: Get-SPOSiteScriptFromList -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOSiteScriptFromList - -## SYNOPSIS - -Creates site script syntax from an existing SharePoint list. - -## SYNTAX - -```powershell -Get-SPOSiteScriptFromList -ListUrl <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Uses an existing SharePoint list to output a JSON blob that can be used to create a site script for use in a site design. - -## EXAMPLES - -### Example 1 - -This example creates the site script output from an existing list - and writes it to a variable. This variable is then referenced to create a site script. - -```powershell -$extracted = Get-SPOSiteScriptFromList -ListUrl "https://contoso.sharepoint.com/sites/strategy/customer-contacts" -Add-SPOSiteScript ` - -Title "Contoso Customer Tracker" - -Description "This creates a customer contact list" - -Content $extracted -``` - -## PARAMETERS - -### -ListUrl - -The url of the list to be referenced for the JSON output. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromWeb.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromWeb.md deleted file mode 100644 index d612838b29..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromWeb.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositescriptfromweb -applicable: SharePoint Online -title: Get-SPOSiteScriptFromWeb -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOSiteScriptFromWeb - -## SYNOPSIS - -Creates site script syntax from an existing SharePoint site. - -## SYNTAX - -```powershell -Get-SPOSiteScriptFromWeb [-WebUrl] <string> [-IncludedLists <string[]>] [-IncludeBranding] [-IncludeTheme] [-IncludeRegionalSettings] [-IncludeSiteExternalSharingCapability] [-IncludeLinksToExportedItems] [<CommonParameters>] -``` - -## DESCRIPTION - -Uses an existing SharePoint site to output a JSON blob that can be used to create a site script for use in a site design. - -## EXAMPLES - -### Example 1 - -This example creates the site script output from an existing site - and writes it to a variable. This variable is then referenced to create a site script. - -```powershell -C:\> $extracted = Get-SPOSiteScriptFromWeb ` - -WebUrl https://contoso.sharepoint.com/sites/template ` - -IncludeBranding ` - -IncludeTheme ` - -IncludeRegionalSettings ` - -IncludeSiteExternalSharingCapability ` - -IncludeLinksToExportedItems ` - -IncludedLists ("Shared Documents", "Lists/Project Activities") -C:\> Add-SPOSiteScript ` - -Title "Contoso template site" ` - -Description "This is a copy of a site collection." ` - -Content $extracted -``` - -## PARAMETERS - -### -WebUrl - -The url that starts with HTTPS of the site to retrieve the site script. - -```yaml -Type: string -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludedLists - -An array of one or more lists. Each is identified by the list url. - -```yaml -Type: string[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeBranding - -A switch that if provided, extracts the configuration of the site's branding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeTheme - -A switch that if provided, extracts the site's custom theme by using the themeJson property. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeRegionalSettings - -A switch that if provided, extracts the site's regional settings. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeSiteExternalSharingCapability - -A switch that if provided, extracts the site's external sharing capability. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeLinksToExportedItems - -A switch that if provided, extracts navigation links. In order to export navigation links pointing to lists, the list needs to be included in the request as well. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteUserInvitations.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteUserInvitations.md deleted file mode 100644 index 6786325086..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteUserInvitations.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spositeuserinvitations -applicable: SharePoint Online -title: Get-SPOSiteUserInvitations -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOSiteUserInvitations - -## SYNOPSIS - -. - -## SYNTAX - -```powershell -Get-SPOSiteUserInvitations [-Site] <SpoSitePipeBind> [-EmailAddress] <string> [<CommonParameters>] -``` - -## DESCRIPTION - -. - -## EXAMPLES - -### Example 1 - -```powershell - -``` - -. - -## PARAMETERS - -### -Site - -. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddress - -. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOStorageEntity.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOStorageEntity.md deleted file mode 100644 index 047135eb66..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOStorageEntity.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spostorageentity -applicable: SharePoint Online -title: Get-SPOStorageEntity -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOStorageEntity - -## SYNOPSIS - -Tenant properties allow tenant administrators to add properties in the app catalog that can be read by various SharePoint Framework components. Because tenant properties are stored in the tenant app catalog, you must provide the tenant app catalog site collection URL or the site collection app catalog URL in the following cmdlets. -This cmdlet is used to get a value in the property bag. - -## SYNTAX - -```powershell -Get-SPOStorageEntity [-Site] <SpoSitePipeBind> [-Key] <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to get a value in the property bag. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOStorageEntity -Site "https://tenant-name.sharepoint.com/sites/app-catalog" -Key "MyCustomValues" -``` - -This example returns the whole entry in the property bag. - -## PARAMETERS - -### -Site - -URL to the tenant or site collection app catalog. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Key - -The key in the property bag that should be returned. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenant.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenant.md deleted file mode 100644 index 421688cab1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenant.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenant -applicable: SharePoint Online -title: Get-SPOTenant -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenant - -## SYNOPSIS - -Returns SharePoint Online organization properties. - -## SYNTAX - -```powershell -Get-SPOTenant [<CommonParameters>] -``` - -## DESCRIPTION - -The `Get-SPOTenant` cmdlet returns organization-level site collection properties such as StorageQuota, StorageQuotaAllocated, ResourceQuota, ResourceQuotaAllocated and SiteCreationMode. - -Currently, there are no parameters for this cmdlet. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Get-SPOTenant -``` - -This example returns the organization-level site collection properties such as StorageQuota, StorageQuotaAllocated, ResourceQuota, ResourceQuotaAllocated, SiteCreationMode and OneDriveStorageQuota. - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnEnabled.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnEnabled.md deleted file mode 100644 index a00ef29c9f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnEnabled.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantcdnenabled -applicable: SharePoint Online -title: Get-SPOTenantCdnEnabled -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantCdnEnabled - -## SYNOPSIS - -Returns whether Public content delivery network (CDN) or Private CDN is enabled on the tenant level. Requires Tenant administrator permissions. - -## SYNTAX - -```powershell -Get-SPOTenantCdnEnabled -CdnType <SPOTenantCdnType> [<CommonParameters>] -``` - -## DESCRIPTION - -Returns whether Public content delivery network (CDN) or Private CDN is enabled on the tenant level. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOTenantCdnEnabled -CdnType Public -``` - -The example returns a CDN with a type of public. - -## PARAMETERS - -### -CdnType - -Specifies the CDN type. The valid values are Public or Private. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) -Aliases: -Accepted values: Public, Private -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnOrigins.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnOrigins.md deleted file mode 100644 index 5695b21abe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnOrigins.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantcdnorigins -applicable: SharePoint Online -title: Get-SPOTenantCdnOrigins -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantCdnOrigins - -## SYNOPSIS - -Lists all the configured origins under the tenancy or under a given site. Requires Tenant administrator permissions. - -## SYNTAX - -```powershell -Get-SPOTenantCdnOrigins -CdnType <SPOTenantCdnType> [<CommonParameters>] -``` - -## DESCRIPTION - -Lists all the configured origins under the tenancy or under a given site. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOTenantCdnOrigins -CdnType Public -``` - -The example returns a list of origins from the Tenant. - -## PARAMETERS - -### -CdnType - -Specifies the CDN type. The valid values are: Public or Private. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) -Aliases: -Accepted values: Public, Private -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnPolicies.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnPolicies.md deleted file mode 100644 index 7dd1079c2a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantCdnPolicies.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantcdnpolicies -applicable: SharePoint Online -title: Get-SPOTenantCdnPolicies -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantCdnPolicies - -## SYNOPSIS - -Get the public or private Policies applied on your SharePoint Online Tenant. Requires Tenant administrator permissions. - -## SYNTAX - -```powershell -Get-SPOTenantCdnPolicies -CdnType <SPOTenantCdnType> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet gets the public or private policies applied to a SharePoint Online organization tenant. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOTenantCdnPolicies -CdnType Public -``` - -This example returns public CDN policies of your tenant. - -### Example 2 - -```powershell -Get-SPOTenantCdnPolicies -CdnType Private -``` - -This example returns private CDN policies of your tenant. - -## PARAMETERS - -### -CdnType - -Type of CDN on the current SPO Tenant (Public,Private) - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) -Aliases: -Accepted values: Public, Private -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Set-SPOTenantCdnEnabled](Set-SPOTenantCdnEnabled.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantContentTypeReplicationParameters.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantContentTypeReplicationParameters.md deleted file mode 100644 index 68f07c48bb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantContentTypeReplicationParameters.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantcontenttypereplicationparameters -applicable: SharePoint Online -title: Get-SPOTenantContentTypeReplicationParameters -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantContentTypeReplicationParameters - -## SYNOPSIS - -Gets content types for replication parameters - -## SYNTAX - -```powershell -Get-SPOTenantContentTypeReplicationParameters [<CommonParameters>] -``` - -## DESCRIPTION - -Before you run the cmdlets, please use `Connect-SPOService` to connect to SharePoint Online first. -This Cmdlets gets the content types that are being replicated from primary location to satellite - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOTenantContentTypeReplicationParameters -``` - -Gets content types for replication parameters - -## 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/?LinkID=113216). - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOTenantTaxonomyReplicationParameters](Get-SPOTenantTaxonomyReplicationParameters.md) - -[Set-SPOTenantTaxonomyReplicationParameters](Set-SPOTenantTaxonomyReplicationParameters.md) - -[Set-SPOTenantContentTypeReplicationParameters](Set-SPOTenantContentTypeReplicationParameters.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantLogEntry.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantLogEntry.md deleted file mode 100644 index 0731a39c14..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantLogEntry.md +++ /dev/null @@ -1,213 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantlogentry -applicable: SharePoint Online -title: Get-SPOTenantLogEntry -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantLogEntry - -## SYNOPSIS - -Retrieves SharePoint Online company logs. This cmdlet is reserved for internal Microsoft use. - -## SYNTAX - -### CorrelationId - -```powershell -Get-SPOTenantLogEntry [[-StartTimeInUtc] <DateTime>] [[-EndTimeInUtc] <DateTime>] [[-MaxRows] <UInt32>] - -CorrelationId <Guid> [<CommonParameters>] -``` - -### Source - -```powershell -Get-SPOTenantLogEntry [[-StartTimeInUtc] <DateTime>] [[-EndTimeInUtc] <DateTime>] [[-MaxRows] <UInt32>] - -Source <Int32> [<CommonParameters>] -``` - -### User - -```powershell -Get-SPOTenantLogEntry [[-StartTimeInUtc] <DateTime>] [[-EndTimeInUtc] <DateTime>] [[-MaxRows] <UInt32>] - -User <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets. - -The `Get-SPOTenantLogEntry` cmdlet cannot retrieve all SharePoint Online errors. This cmdlet retrieves a subset of errors that happen due to external systems. - -For Beta 2, the only company logs available are for Business Connectivity Services (BCS). - -> [!NOTE] -> If you do not use any parameter, the first 1000 rows in descending time range are returned. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832.> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOTenantLogEntry -``` - -This example retrieves all logs that are available. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Get-SPOTenantLogEntry -MaxRows 500 -``` - -This example retrieves the first 500 log entries. - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -$endTimeinUTC = Get-SPOTenantLogLastAvailableTimeInUtc -$startTimeinUTC = $endTimeinUTC.AddDays(-14) -$tenantlogs = Get-SPOTenantLogEntry -StartTimeinUtc $startTimeinUTC -EndTimeinUTC $endTimeinUTC -``` - -This example retrieves log entries recorded over that previous 14 days. - -### -----------------------EXAMPLE 4----------------------------- - -```powershell -$endTimeinUTC = Get-SPOTenantLogLastAvailableTimeInUtc -$startTimeinUTC = $endTimeinUTC.AddDays(-14) -$tenantlogs = Get-SPOTenantLogEntry -StartTimeinUtc $startTimeinUTC -EndTimeinUTC $endTimeinUTC -CorrelationId e2c2be70-6382-4ce7-8a44-ae7dadff5597 -``` - -This example retrieves log entries recorded over that previous 14 days that have the CorrelationId of "e2c2be70-6382-4ce7-8a44-ae7dadff5597". - -## PARAMETERS - -### -CorrelationId - -Specifies the Correlation ID as a filter. - -```yaml -Type: Guid -Parameter Sets: CorrelationId -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndTimeInUtc - -Specifies the end time in UTC to search for logs. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxRows - -Specifies the maximum number of rows in the descending order of timestamp. The value must be less than 5000. The default value is 1000. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Source - -Specifies the component that logs the errors. - -```yaml -Type: Int32 -Parameter Sets: Source -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartTimeInUtc - -Specifies the start time in Coordinated Universal Time (UTC) to search for the logs (for example, 01032011:12:00). - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User - -Specifies the log-on identity as a filter. - -```yaml -Type: String -Parameter Sets: User -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantLogLastAvailableTimeInUtc.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantLogLastAvailableTimeInUtc.md deleted file mode 100644 index 836cc44f98..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantLogLastAvailableTimeInUtc.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantloglastavailabletimeinutc -applicable: SharePoint Online -title: Get-SPOTenantLogLastAvailableTimeInUtc -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantLogLastAvailableTimeInUtc - -## SYNOPSIS - -Returns the most recent time when the SharePoint Online organization logs were collected. - -## SYNTAX - -```powershell -Get-SPOTenantLogLastAvailableTimeInUtc [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet retrieves the time in Coordinated Universal Time (UTC) when the logs were last collected. -After you know the time, you can use the `Get-SPOTenantLogEntry` cmdlet to retrieve the logs. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOTenantLogLastAvailableTimeInUtc -``` - -This example returns the time in UTC when the SharePoint Online organization logs were most recently collected. - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOTenantLogEntry](Get-SPOTenantLogEntry.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelation.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelation.md deleted file mode 100644 index 93b46e3689..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelation.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/Get-SPOTenantOrgRelation -applicable: SharePoint Online -title: Get-SPOTenantOrgRelation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantOrgRelation - -## SYNOPSIS - -{{ Fill in the Synopsis }} - -## SYNTAX - -```powershell -Get-SPOTenantOrgRelation [<CommonParameters>] -``` - -## DESCRIPTION - -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 - -```powershell - Get-SPOTenantOrgRelation -``` - -{{ Add example description here }} - -## 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByPartner.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByPartner.md deleted file mode 100644 index 70b64a493e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByPartner.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/Get-SPOTenantOrgRelationByPartner -applicable: SharePoint Online -title: Get-SPOTenantOrgRelationByPartner -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - - -# Get-SPOTenantOrgRelationByPartner - -## SYNOPSIS - -{{ Fill in the Synopsis }} - -## SYNTAX - -```powershell -Get-SPOTenantOrgRelationByPartner [-PartnerCompanyId] <Guid> [[-PartnerInstanceId] <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION - -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 - -```powershell - -``` - -{{ Add example description here }} - -## PARAMETERS - -### -PartnerCompanyId - -{{ Fill PartnerCompanyId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerInstanceId - -{{ Fill PartnerInstanceId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByScenario.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByScenario.md deleted file mode 100644 index e85dd4b129..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByScenario.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/Get-SPOTenantOrgRelationByScenario -applicable: SharePoint Online -title: Get-SPOTenantOrgRelationByScenario -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantOrgRelationByScenario - -## SYNOPSIS - -{{ Fill in the Synopsis }} - -## SYNTAX - -```powershell -Get-SPOTenantOrgRelationByScenario [-Scenario] <OrgRelationScenario> [-PartnerRole] <OrgRelationRole> - [<CommonParameters>] -``` - -## DESCRIPTION - -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 - -```powershell -PS C:\> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -PartnerRole - -{{ Fill PartnerRole Description }} - -```yaml -Type: OrgRelationRole -Parameter Sets: (All) -Aliases: -Accepted values: None, Source, Target - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scenario - -{{ Fill Scenario Description }} - -```yaml -Type: OrgRelationScenario -Parameter Sets: (All) -Aliases: -Accepted values: None, MnA - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantServicePrincipalPermissionGrants.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantServicePrincipalPermissionGrants.md deleted file mode 100644 index 46d5c6ff7a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantServicePrincipalPermissionGrants.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantserviceprincipalpermissiongrants -applicable: SharePoint Online -title: Get-SPOTenantServicePrincipalPermissionGrants -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantServicePrincipalPermissionGrants - -## SYNOPSIS - -Gets the collection of permission grants for the "SharePoint Online Client" service principal - -## SYNTAX - -### Default - -```powershell -Get-SPOTenantServicePrincipalPermissionGrants -``` - -## DESCRIPTION - -Gets the collection of permission grants for the "SharePoint Online Client" service principal. - -A permission grant contains the following properties: - -- ClientId: The objectId of the service principal granted consent to impersonate the user when accessing the resource (represented by the resourceId). - -- ConsentType: Whether consent was provided by the administrator on behalf of the organization or whether consent was provided by an individual. The possible values are "AllPrincipals" or "Principal". - -- ObjectId: The unique identifier for the permission grant. - -- _(Coming soon)_ Resource: The resource to which access has been granted. - -- ResourceId: The objectId of the resource service principal to which access has been granted. - -- Scope: The value of the scope claim that the resource application should expect in the OAuth 2.0 access token. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell -Get-SPOTenantServicePrincipalPermissionGrants -``` - -Gets the collection of permission grants for the "SharePoint Online Client" service principal. diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantServicePrincipalPermissionRequests.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantServicePrincipalPermissionRequests.md deleted file mode 100644 index 01d6e24b26..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantServicePrincipalPermissionRequests.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantserviceprincipalpermissionrequests -applicable: SharePoint Online -title: Get-SPOTenantServicePrincipalPermissionRequests -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantServicePrincipalPermissionRequests - -## SYNOPSIS - -Gets the collection of permission requests for the "SharePoint Online Client" service principal - -## SYNTAX - -### Default - -```powershell -Get-SPOTenantServicePrincipalPermissionRequests -``` - -## DESCRIPTION - -Gets the collection of permission requests for the "SharePoint Online Client" service principal. - -Permission request object - -A permission request contains the following properties: - -- Id: The identifier of the request. - -- Resource: The resource that the application requires access to. - -- Scope: The value of the scope claim that the resource application should expect in the OAuth 2.0 access token. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell -Get-SPOTenantServicePrincipalPermissionRequests -``` - -Gets the collection of permission requests for the "SharePoint Online Client" service principal. diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantSyncClientRestriction.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantSyncClientRestriction.md deleted file mode 100644 index b3191d071d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantSyncClientRestriction.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenantsyncclientrestriction -applicable: SharePoint Online -title: Get-SPOTenantSyncClientRestriction -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantSyncClientRestriction - -## SYNOPSIS - -Returns the current configuration status. - -## SYNTAX - -```powershell -Get-SPOTenantSyncClientRestriction [<CommonParameters>] -``` - -## DESCRIPTION - -You must be a SharePoint Online global administrator to run the cmdlet. - -Requires a valid `Connect-SPOService` context to identify the tenant. For information on how to connect to the tenant, see `Connect-SPOService`. - -The `Get-SPOTenantSyncClientRestriction` cmdlet returns whether the TenantRestrictionEnabled property is true or false and DomainGUIDs that are currently in the safe recipient list which is represented by the AllowedDomainList property. - -The `Get-SPOTenantSyncClientRestriction` cmdlet also returns the current state of the BlockMacSync parameter. - -The `Get-SPOTenantSyncClientRestriction` cmdlet also returns the current state of the GrooveBlockOption parameter. - -The `Get-SPOTenantSyncClientRestriction` cmdlet does not have any parameters. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOTenantSyncClientRestriction -``` - -This example returns a current boolean value of the TenantRestrictionEnabled and BlockMacSync properties and a current set list of domains GUIDs in the AllowedDomainList property. - -## 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantTaxonomyReplicationParameters.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantTaxonomyReplicationParameters.md deleted file mode 100644 index cda2a8edd6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantTaxonomyReplicationParameters.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotenanttaxonomyreplicationparameters -applicable: SharePoint Online -title: Get-SPOTenantTaxonomyReplicationParameters -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTenantTaxonomyReplicationParameters - -## SYNOPSIS - -Get the replication parameters to manage Multi-Geo taxonomy replication. - -## SYNTAX - -```powershell -Get-SPOTenantTaxonomyReplicationParameters [<CommonParameters>] -``` - -## DESCRIPTION - -Before using this cmdlet, make sure you connect to Sharepoint Online using [Connect-SPOService](Connect-SPOService.md) and the desirable satellite location URL as the -Url parameter. - -This Cmdlet gets the replication parameters and it works to get the replication taxonomy in a Multi-Geo tenant. -It works with the [Set-SPOTenantTaxonomyReplicationParameters](Set-SPOTenantTaxonomyReplicationParameters.md) to set the parameters. - -Get the sites to be replicated in a Multi-Geo taxonomy replication. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOTenantTaxonomyReplicationParameters -``` - -Gets the replication groups that are being replicated on the current tenant. - -## 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/?LinkID=113216). - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Set-SPOTenantTaxonomyReplicationParameters](Set-SPOTenantTaxonomyReplicationParameters.md) - -[Get-SPOTenantContentTypeReplicationParameters](Get-SPOTenantContentTypeReplicationParameters.md) - -[Set-SPOTenantContentTypeReplicationParameters](Set-SPOTenantContentTypeReplicationParameters.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTheme.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTheme.md deleted file mode 100644 index a24b33832d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTheme.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spotheme -applicable: SharePoint Online -title: Get-SPOTheme -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOTheme - -## SYNOPSIS - -Retrieves settings for an existing theme. - -## DESCRIPTION - -The **Get-SPOTheme** cmdlet returns the settings for a named existing theme, or for all uploaded themes if no name is provided. - -## EXAMPLES - -### Example 1 - -This example shows how to use the **Get-SPOTheme** cmdlet to return the settings for the `"Custom Cyan"` theme created in the example for the **Add-SPOTheme** cmdlet. Note that this example uses the PowerShell `ConvertTo-Json` filter to display the theme in JSON format. - -```powershell -Get-SPOTheme -Name "Custom Cyan" | ConvertTo-Json -``` - -```powershell -{ - "Name": "Custom Cyan", - "Palette": { - "themeLight": "#affefe", - "themeTertiary": "#76ffff", - "black": "#000000", - "neutralSecondary": "#666666", - "neutralTertiaryAlt": "#c8c8c8", - "themeSecondary": "#39ffff", - "themeDarker": "#005252", - "primaryBackground": "#fff", - "neutralQuaternary": "#d0d0d0", - "neutralPrimaryAlt": "#3c3c3c", - "neutralPrimary": "#333", - "themeDark": "#009090", - "themeLighter": "#daffff", - "neutralTertiary": "#a6a6a6", - "neutralQuaternaryAlt": "#dadada", - "themeLighterAlt": "#f3fcfc", - "white": "#fff", - "neutralSecondaryAlt": "#767676", - "neutralLighter": "#f4f4f4", - "neutralLight": "#eaeaea", - "neutralDark": "#212121", - "themeDarkAlt": "#00c4c4", - "neutralLighterAlt": "#f8f8f8", - "primaryText": "#333", - "themePrimary": "#00ffff" - }, - "IsInverted": false -} -``` - -### Example 2 - -To return all uploaded themes, use the **Get-SPOTheme** command with no arguments. - -```powershell -Get-SPOTheme -``` - -<!--(Commenting out this image because I don't see a way to have images in this location) - -This is an example of the output from this command. - -![Get-SPOTheme example](../../images/Get-SPOTheme-example.png)--> - -## INPUTS - -## OUTPUTS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroup.md deleted file mode 100644 index 9fa95322a5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroup.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spounifiedgroup -applicable: SharePoint Online -title: Get-SPOUnifiedGroup -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOUnifiedGroup - -## SYNOPSIS - -Retrieves the Preferred Data Location for the specified Office 365 Group. - -## SYNTAX - -```powershell -Get-SPOUnifiedGroup [-GroupAlias] <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Retrieves the Preferred Data Location (PDL) for the specified Office 365 Group. The customer tenant must be multi-geo enabled. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOUnifiedGroup -GroupAlias EUTeam -``` -Returns the PDL for the Office 365 Group named 'EUTeam'. - -## PARAMETERS - -### -GroupAlias - -The alias of the Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES - -## RELATED LINKS - -[Move a SharePoint site to a different geo location](https://docs.microsoft.com/office365/enterprise/move-sharepoint-between-geo-locations) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroupMoveState.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroupMoveState.md deleted file mode 100644 index 9211c76dbb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroupMoveState.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spounifiedgroupmovestate -applicable: SharePoint Online -title: Get-SPOUnifiedGroupMoveState -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Get-SPOUnifiedGroupMoveState - -## SYNOPSIS - -Returns the state of an Office 365 Group move between Preferred Data Locations. - -## SYNTAX - -```powershell -Get-SPOUnifiedGroupMoveState [-GroupAlias] <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Retrieves the state of the Office 365 Group move to the Preferred Data Location (PDL) for the specified. The customer tenant must be multi-geo enabled. - -## EXAMPLES - -### Example 1 - -```powershell -Get-SPOUnifiedGroupMoveState -GroupAlias EUTeam -``` - -Returns the status of the move between geos for the Office 365 Group named 'EUTeam'. - -## PARAMETERS - -### -GroupAlias - -The alias of the Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## OUTPUTS - -### System.Object - -The move status for the Office 365 Group. Possible values are: - -* Ready to Trigger: The move has not started. -* Scheduled: The move is in queue but has not yet started. -* InProgress (n/4): The move is in progress in one of the following states: Validation (1/4), Backup (2/4), Restore (3/4), Cleanup (4/4). -* Success: The move has completed successfully. -* Failed: The move failed. - -## NOTES - -You can also apply the `-Verbose` option to see additional information about the move. - -## RELATED LINKS - -[Move a SharePoint site to a different geo location](https://docs.microsoft.com/office365/enterprise/move-sharepoint-between-geo-locations) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUser.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUser.md deleted file mode 100644 index 32ed9fa3b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUser.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spouser -applicable: SharePoint Online -title: Get-SPOUser -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOUser - -## SYNOPSIS - -Returns the SharePoint Online user or security group accounts that match a given search criteria. - -## SYNTAX - -### ByGroup - -```powershell -Get-SPOUser [-Group <String>] [-Limit <String>] -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -### All - -```powershell -Get-SPOUser [-Limit <String>] -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -### ByLogin - -```powershell -Get-SPOUser [-LoginName <String>] -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (<https://go.microsoft.com/fwlink/?LinkID=187810).> - -The `Get-SPOUser` cmdlet matches one and only one user or security group. - -You must be a SharePoint Online global administrator and a site collection administrator to run the `Get-SPOUser` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOUser -Site https://contoso.sharepoint.com/sites/finance -``` - -Example 1 returns all user or security group accounts from the site collection <https://contoso.sharepoint.com/sites/finance.> - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Get-SPOUser -Site https://contoso.sharepoint.com/sites/finance -LoginName melissa.kerr@contoso.com -``` - -Example 2 returns one user or security group account whose user name is HYPERLINK "mailto:melissa.kerr@contoso.com" melissa.kerr@contoso.com from the site collection <https://contoso.sharepoint.com/sites/finance.> - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -Get-SPOUser -Site https://contoso.sharepoint.com/sites/finance -Group "Team Site Members" -``` - -Example 3 returns one user or security group account inside group Team Site Members from the site collection <https://contoso.sharepoint.com/sites/finance.> - -## PARAMETERS - -### -Group - -Specifies the group to get the users from. - -```yaml -Type: String -Parameter Sets: ByGroup -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit - -Specifies the maximum number of users returned. The default value is to return 500 users. To return all users specify the value "All". - -```yaml -Type: String -Parameter Sets: ByGroup, All -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoginName - -Specifies the user name. - -```yaml -Type: String -Parameter Sets: ByLogin -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the URL of the site collection to get the user from. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Remove-SPOUser](Remove-SPOUser.md) - -[Set-SPOUser](Set-SPOUser.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserAndContentMoveState.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserAndContentMoveState.md deleted file mode 100644 index dcd5d2aa64..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserAndContentMoveState.md +++ /dev/null @@ -1,235 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spouserandcontentmovestate -applicable: SharePoint Online -title: Get-SPOUserAndContentMoveState -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOUserAndContentMoveState - -## SYNOPSIS - -This cmdlet allows a SharePoint administrators to check the status of a user or site move across geo locations. - -## SYNTAX - -### MoveReport - -```powershell -Get-SPOUserAndContentMoveState [-Limit <UInt32>] [-MoveDirection <Direction>] [-MoveEndTime <DateTime>] - [-MoveStartTime <DateTime>] [-MoveState <State>] [<CommonParameters>] -``` - -### OdbMoveId - -```powershell -Get-SPOUserAndContentMoveState -OdbMoveId <Guid> [<CommonParameters>] -``` - -### UserPrincipalName - -```powershell -Get-SPOUserAndContentMoveState -UserPrincipalName <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This command gets the information and the status of a move request of a user between sites in a SharePoint Online Multi Geo tenant. - -The following are the available move states: - -|Status|Description| -| --- | --- | -|NotStarted| The move has not started. | -|InProgress| The move is in progress in one of the following states: Validation, Backup, Restore, Cleanup.| -|Success| The move has completed successfully.| -|Failed|The move failed.| - -## EXAMPLES - -### Example 1 - -```Powershell -Get-SPOUserAndContentMoveState -OdbMoveId b298219e-3440-10b8-8931-46e805e2b85b -``` - -Obtain the move state by OneDrive Move Job ID - -### Example 2 - -```Powershell -Get-SPOUserAndContentMoveState -MoveState NotStarted -``` - -Getting which moves are being done in a particular state -### Example 3 - -```Powershell -Get-SPOUserAndContentMoveState -MoveDirection All -``` - -Gives you the output for users moving in and out from the geo location you are logged into - -### Example 4 - -```Powershell -Get-SPOUserAndContentMoveState -MoveDirection In -``` - -Gives you the output for users moving into the geo location that you are logged into - -### Example 5 - -```Powershell -Get-SPOUserAndContentMoveState -MoveDirection Out -``` - -Gives you the output for users moving out from the geo location that you are logged into - -### Example 6 - -```Powershell -Get-SPOUserAndContentMoveState -UserPrincipalName jezz@contoso.com -``` - -Obtains the status of the move for jezz@contoso.com - -## PARAMETERS - -### -Limit - -Get the limit of user on a single call of the parameter - -```yaml -Type: UInt32 -Parameter Sets: MoveReport -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveDirection - -Allows you to define the direction of the user move in relation to your current SharePoint location - -```yaml -Type: Direction -Parameter Sets: MoveReport -Aliases: -Accepted values: All, MoveIn, MoveOut -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveEndTime - -Allows you to obtain the moves that are scheduled to end by a particular time, as defined in UTC - -```yaml -Type: DateTime -Parameter Sets: MoveReport -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveStartTime - -Allows you to obtain the moves that are scheduled to begin at a particular time, as defined in UTC - -```yaml -Type: DateTime -Parameter Sets: MoveReport -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveState - -Move State current status. - -```yaml -Type: State -Parameter Sets: MoveReport -Aliases: -Accepted values: All, NotStarted, Scheduled, InProgress, Stopped, Success, Failed -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OdbMoveId - -Onedrive GUID MoveID that you get when you start a job. - -```yaml -Type: Guid -Parameter Sets: OdbMoveId -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName - -User Principal name is the unique property on Azure AD for each user. - -```yaml -Type: String -Parameter Sets: UserPrincipalName -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Start-SPOUserAndContentMove](Start-SPOUserAndContentMove.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserOneDriveLocation.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserOneDriveLocation.md deleted file mode 100644 index 8d122a1f78..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserOneDriveLocation.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spouseronedrivelocation -applicable: SharePoint Online -title: Get-SPOUserOneDriveLocation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOUserOneDriveLocation - -## SYNOPSIS - -This cmdlet will return the user principal name, current location, and corresponding OneDrive for Business url, and the site ID. This cmdlet only supports Multi-Geo OneDrive sites. - -## SYNTAX - -```powershell -Get-SPOUserOneDriveLocation -UserPrincipalName <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This command will return information about the OneDrive location for the specified user. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOUserOneDriveLocation -UserPrincipalName admin@contoso.com -``` - -Get the current location the user's OneDrive location, url, and site ID. - -## PARAMETERS - -### -UserPrincipalName - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOWebTemplate.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOWebTemplate.md deleted file mode 100644 index 58c0952197..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOWebTemplate.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/get-spowebtemplate -applicable: SharePoint Online -title: Get-SPOWebTemplate -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOWebTemplate - -## SYNOPSIS - -Displays all site templates that match the given identity. - -## SYNTAX - -```powershell -Get-SPOWebTemplate [[-LocaleId] <UInt32>] [-CompatibilityLevel <Int32>] [-Name <String>] [-Title <String>] - [<CommonParameters>] -``` - -## DESCRIPTION - -The `Get-SPOWebTemplate` cmdlet displays all site templates that match the given identity and are available in SharePoint Online. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832.> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Get-SPOWebTemplate -``` - -Example 1 returns all the site templates in the language of the administrator site. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Get-SPOWebTemplate -LocaleID 1036 -``` - -Example 2 returns a list of all the French site templates. - -## PARAMETERS - -### -CompatibilityLevel - -Specifies the compatibility level of the site template. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocaleId - -Specifies the Locale ID of the site template. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the name of the site template. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title - -Specifies the Locale ID of the site template. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Grant-SPOHubSiteRights.md b/sharepoint/sharepoint-ps/sharepoint-online/Grant-SPOHubSiteRights.md deleted file mode 100644 index 81568ad7be..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Grant-SPOHubSiteRights.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/grant-spohubsiterights -applicable: SharePoint Online -title: Grant-SPOHubSiteRights -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Grant-SPOHubSiteRights - -## SYNOPSIS - -Grants rights to users or mail-enabled security groups to associate their site with a hub site. - -## SYNTAX - -```powershell -Grant-SPOHubSiteRights [-Identity] <SpoHubSitePipeBind> -Principals - <string[]> -Rights {Join} [<CommonParameters>] -``` - -## DESCRIPTION - -Applies permissions to a set of users or mail-enabled security groups. Use this cmdlet to scope visibility of who can associate their site with the hub site when using the SharePoint user interface. Hub sites are public by default. Once you set permissions, only those groups or users you specified can associate their site with the hub site. - -To view which users or groups have permissions to a site, use the [Get-SPOHubSite](Get-SPOHubSite.md) cmdlet. - -## EXAMPLES - -### Example 1 - -```powershell -Grant-SPOHubSiteRights https://contoso.sharepoint.com/sites/Marketing --Principals nestorw@contoso.onmicrosoft.com --Rights Join -``` - -This example shows how to grant rights to Nestor (a user at the fictional Contoso site) to associate his sites with the marketing hub site. - -## PARAMETERS - -### -Identity - -URL of the hub site. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Principals - -One or more principles to add permissions for. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Rights - -Always set to the value **Join**. Any user or group with **Join** permissions can view and join the hub site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Grant-SPOSiteDesignRights.md b/sharepoint/sharepoint-ps/sharepoint-online/Grant-SPOSiteDesignRights.md deleted file mode 100644 index 0a9105019f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Grant-SPOSiteDesignRights.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/grant-spositedesignrights -applicable: SharePoint Online -title: Grant-SPOSiteDesignRights -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Grant-SPOSiteDesignRights - -## SYNOPSIS - -Used to apply permissions to a set of users or a security group, effectively scoping the visibility of the site design in the UX. They start off public, but after you set permissions, only those groups or users with permissions can access the site design. - -## SYNTAX - -```powershell -Grant-SPOSiteDesignRights - [-Identity] <SPOSiteDesignPipeBind> - -Principals <string[]> - -Rights {View} - [<CommonParameters>] -``` - -## DESCRIPTION - -Used to apply permissions to a set of users or a security group, effectively scoping the visibility of the site design in the UX. They start off public, but after you set permissions, only those groups or users with permissions can access the site design. - -## EXAMPLES - -### Example 1 - -This example shows how to grant view rights on a site design to Nestor (a user at the fictional Contoso site). - -```powershell -Grant-SPOSiteDesignRights ` - -Identity 44252d09-62c4-4913-9eb0-a2a8b8d7f863 ` - -Principals "nestorw@contoso.onmicrosoft.com" ` - -Rights View -``` - -## PARAMETERS - -### -Identity - -The ID of the site design to get scoping information. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Principals - -One or more principles to add permissions for. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Rights - -Always set to the value **View**. Any user or group with view permissions can view and use the site design. - -```yaml -Type: SPOSiteDesignPrincipalRights -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOMigrationEncryptUploadSubmit.md b/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOMigrationEncryptUploadSubmit.md deleted file mode 100644 index 50256ef7f9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOMigrationEncryptUploadSubmit.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/invoke-spomigrationencryptuploadsubmit -applicable: SharePoint Online -title: Invoke-SPOMigrationEncryptUploadSubmit -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Invoke-SPOMigrationEncryptUploadSubmit - -## SYNOPSIS - -Creates a new migration job in the target site collection - -## SYNTAX - -### ImplicitSourceParameterSet - -```powershell -Invoke-SPOMigrationEncryptUploadSubmit -Credentials <CredentialCmdletPipeBind> - -MigrationSourceLocations <MigrationPackageLocation> [-NoLogFile] -TargetWebUrl <String> [<CommonParameters>] -``` - -### ExplicitSourceParameterSet - -```powershell -Invoke-SPOMigrationEncryptUploadSubmit -Credentials <CredentialCmdletPipeBind> [-NoLogFile] - -SourceFilesPath <String> -SourcePackagePath <String> -TargetWebUrl <String> [<CommonParameters>] -``` - -## DESCRIPTION - -Creates a new migration job in the target site collection, and then returns a GUID representing the JobID. This command will upload encrypted source files and manifests into temporary Azure blob storage per job. - -## EXAMPLES - -### Example 1 - -```powershell -$job = Invoke-SPOMigrationEncryptUploadSubmit -SourceFilesPath $sourceFiles -SourcePackagePath $spoPackagePath -Credentials $cred -TargetWebUrl $targetWebUrl -``` - -This example shows how to submit package data to create a new migration job - -### Example 2 - -```Powershell -$sourceFiles = "sourceFiles" -$spoPackagePath = "packagePath" -$credentials = Get-Credential -$targetweburl = "https://contoso.sharepoint.com/" -Invoke-SPOMigrationEncryptUploadSubmit -SourceFilesPath $sourceFiles -SourcePackagePath $spoPackagePath -Credentials $credentials -TargetWebUrl $targetweburl -``` - -This example shows how to submit package data to create a new migration job. - -This article contains the steps on how to create this package: <https://support.office.com/en-us/article/upload-on-premises-content-to-sharepoint-online-using-powershell-cmdlets-555049c6-15ef-45a6-9a1f-a1ef673b867c> - -### Example 3 - -This example shows how to submit package data to create new migration jobs for parallel import. - -```Powershell -$jobs = $finalPackages | % {Invoke-SPOMigrationEncryptUploadSubmit -SourceFilesPath $_.FilesDirectory.FullName -SourcePackagePath $_.PackageDirectory.FullName -Credentials $cred -TargetWebUrl $targetWeb} -``` - -## PARAMETERS - -### -Credentials - -Parameter to fill out credentials of the SPO tenant. - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MigrationSourceLocations - -Migration Location where the package lies. - -```yaml -Type: MigrationPackageLocation -Parameter Sets: ImplicitSourceParameterSet -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -Controls if a log will be created or not - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceFilesPath - -Source files Path, string - -```yaml -Type: String -Parameter Sets: ExplicitSourceParameterSet -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcePackagePath - -Source Package Path. - -```yaml -Type: String -Parameter Sets: ExplicitSourceParameterSet -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetWebUrl - -Target web URL - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Upload on-premises content to SharePoint Online using PowerShell cmdlets](https://support.office.com/en-us/article/upload-on-premises-content-to-sharepoint-online-using-powershell-cmdlets-555049c6-15ef-45a6-9a1f-a1ef673b867c) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteDesign.md deleted file mode 100644 index 1a8d0a1a55..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteDesign.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/invoke-spositedesign -applicable: SharePoint Online -title: Invoke-SPOSiteDesign -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Invoke-SPOSiteDesign - -## SYNOPSIS - -Applies a published site design to a specified site collection target. This allows a site design to be applied to an existing site collection. The supported site templates you can apply a site design to include: "modern" team site (with O365 group), "modern" team site (without an O365 group); communication site; classic team site; and classic publishing site. - -## SYNTAX - -```powershell -Invoke-SPOSiteDesign - [-Identity] - -WebUrl <string> - [<CommonParameters>] -``` - -## DESCRIPTION - -Applies a published site design to a specified site collection target. This allows a site design to be applied to an existing site collection. - -## EXAMPLES - -### Example 1 - -This example applies a site design whose script creates two lists, formats several of the columns, adds the lists to the site navigation, and then joins the site to an existing hub site. - -```powershell -Invoke-SPOSiteDesign -Identity 501z8c32-4147-44d4-8607-26c2f67cae82 -WebUrl "https://contoso.sharepoint.com/sites/projectgo" - -Title Outcome ----------------------------------------------- ------- -Create or update list Project Activities Success -Update list description Success -Create column Project Status Success -Create column Effort (days) Success -Set custom formatter for field Project Status Success -Set custom formatter for field Effort (days) Success -Create or update list Project Collateral Success -Create column Due Date Success -Set custom formatter for field Due Date Success -Add Project Activities to left nav Success -Add Project Collateral to left nav Success -Add to Hub Site Success -``` - -## PARAMETERS - -### -Identity - -The ID of the site design to apply. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebUrl - -The URL of the site collection where the site design will be applied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteSwap.md b/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteSwap.md deleted file mode 100644 index 05ac090626..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteSwap.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/invoke-spositeswap -applicable: SharePoint Online -title: Invoke-SPOSiteSwap -schema: 2.0.0 -author: WayneEwington -ms.author: waynewin -ms.reviewer: ---- - -# Invoke-SPOSiteSwap - -## SYNOPSIS - -Invokes a job to swap the location of a site with another site while archiving the original site. - -## SYNTAX - -```Powershell -Invoke-SPOSiteSwap - -SourceUrl <string> - -TargetUrl <string> - -ArchiveUrl <string> - [-DisableRedirection] - [-Force] - [-NoWait] - [<CommonParameters>] -``` - -## DESCRIPTION - -Swaps the location of a source site with a target site while archiving the original target site. - -When the swap is initiated, the target site is moved to the archive location and the source site is moved to the target location. By default, a site redirect is created at the source location that will redirect traffic to the target location. - -If the target is the root site at <https://tenant-name.sharepoint.com,> then the following preparation activities should be performed prior to performing the swap: - -1. Any Featured links defined in SharePoint Start Page at <https://tenant-name.sharepoint.com/_layouts/15/sharepoint.aspx> will not be displayed after performing the swap. If required, the Featured links should be documented so they can be manually recreated after the swap. -2. Functionality such as external sharing and application interfaces are dependent on the policies and permissions defined at the root site. Review the source site to ensure that it has the required policies and permissions as per the existing root site. This includes external sharing settings as well as site permissions. -3. Larger tenants that have more than ~10,000 licenses may also need to run the [Page Diagnostic Tool](https://docs.microsoft.com/office365/enterprise/page-diagnostics-for-spo) against the source site. Any analysis results that have the category Attention required (Red) or Improvement opprtunities (Orange) will need to be remediated before performing the swap. - -The source and target sites can't be connected to an Office 365 group. They also can't be hub sites or associated with a hub. -If a site is a hub site, unregister it as a hub site, swap the root site, and then register the site as a hub site. If a site is associated with a hub, disassociate the site, swap the root site, and then reassociate the site. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Invoke-SPOSiteSwap -SourceUrl https://contoso.sharepoint.com/sites/CommunicationSite -TargetUrl https://contoso.sharepoint.com -ArchiveUrl https://contoso.sharepoint.com/sites/Archive -``` - -Archives the existing site at <https://contoso.sharepoint.com> to <https://contoso.sharepoint.com/sites/Archive> and moves <https://contoso.sharepoint.com/sites/CommunicationSite> to <https://contoso.sharepoint.com.> A site redirect will be created at <https://contoso.sharepoint.com/sites/CommunicationSite> that will redirect any requests to <https://contoso.sharepoint.com.> - -### EXAMPLE 2 - -```powershell -Invoke-SPOSiteSwap -SourceUrl https://contoso.sharepoint.com/sites/SearchSite -TargetUrl https://contoso.sharepoint.com/search -ArchiveUrl https://contoso.sharepoint.com/sites/Archive -``` - -Archives the existing Search Center site at <https://contoso.sharepoint.com/search> to <https://contoso.sharepoint.com/sites/Archive> and moves the <https://contoso.sharepoint.com/sites/SearchSite> to <https://contoso.sharepoint.com/search.> A site redirect be created at <https://contoso.sharepoint.com/sites/SearchSite> that will redirect any requests to <https://contoso.sharepoint.com/search.> - -### EXAMPLE 3 - -```powershell -Invoke-SPOSiteSwap -SourceUrl https://contoso.sharepoint.com/sites/CommunicationSite -TargetUrl https://contoso.sharepoint.com -ArchiveUrl https://contoso.sharepoint.com/sites/Archive -DisableRedirection -``` - -Archives the existing site at <https://contoso.sharepoint.com> to <https://contoso.sharepoint.com/sites/Archive> and moves <https://contoso.sharepoint.com/sites/CommunicationSite> to <https://contoso.sharepoint.com.> A site redirect will not be created at <https://contoso.sharepoint.com/sites/CommunicationSite.> - -### EXAMPLE 4 - -```powershell -Invoke-SPOSiteSwap -SourceUrl https://contoso.sharepoint.com/sites/SearchSite -TargetUrl https://contoso.sharepoint.com/search -ArchiveUrl https://contoso.sharepoint.com/sites/Archive -Force -``` - -Archives the existing Search Center site at <https://contoso.sharepoint.com/search> to <https://contoso.sharepoint.com/sites/Archive> and moves the <https://contoso.sharepoint.com/sites/SearchSite> to <https://contoso.sharepoint.com/search.> A site redirect be created at <https://contoso.sharepoint.com/sites/SearchSite> that will redirect any requests to <https://contoso.sharepoint.com/search.> Any warnings identified by the Page Diagnostic Tool will be ignored and the swap will be initiated. However, any errors identified by the Page Diagnostic Tool will still prevent the swap from being initiated. - -## PARAMETERS - -### -SourceUrl - -URL of the source site. The site at this location must exist before performing the swap. - -If the target is the root site at <https://tenant-name.sharepoint.com> then the source site must be either a Team Site (STS#0), a Modern Team Site (STS#3), or a Communication Site (SITEPAGEPUBLISHING#0). - -If the target is the search center site at <https://tenant-name.sharepoint.com/search> then the source site must be either a Search Center Site (SRCHCEN#0) or a Basic Search Center Site (SRCHCENTERLITE#0). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetUrl - -URL of the target site that the source site will be swapped to. The site at this location must exist before performing the swap. - -The target site must be either: - -- The root site at <https://tenant-name.sharepoint.com;> or -- The search center site at <https://tenant-name.sharepoint.com/search.> - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ArchiveUrl - -URL that the target site will be archived to. There should be no existing site, including a deleted site in the Recycle Bin, at this location before performing the swap. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableRedirection - -Disables the site redirect from being created at the Source URL location. - -```yaml -Type: Switch Parameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - -Overrides and ignores any warnings that have been identified by the Page Diagnostic Tool that are preventing a swap from being initiated. -Any errors identified by the Page Diagnostic Tool will still always prevent a swap from being initiated regardless of this parameter. - -```yaml -Type: Switch Parameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoWait - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Switch Parameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) -[Modernize your root site](https://docs.microsoft.com/sharepoint/modern-root-site) -[Manage site redirects](https://docs.microsoft.com/sharepoint/manage-site-redirects) -[Page Diagnostic Tool](https://docs.microsoft.com/office365/enterprise/page-diagnostics-for-spo) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPODataConnectionSetting.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPODataConnectionSetting.md deleted file mode 100644 index 12756fb8ce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPODataConnectionSetting.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-spodataconnectionsetting -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: New-SPODataConnectionSetting -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPODataConnectionSetting - -## SYNOPSIS - -Creates a new Business Data Connectivity service connection. - -## SYNTAX - -```powershell -New-SPODataConnectionSetting -AuthenticationMode <ODataAuthenticationMode> -ServiceAddressURL <Uri> - -ServiceContext <SPServiceContextPipeBind> -Name <String> [-AssignmentCollection <SPAssignmentCollection>] - [-ExtensionProvider <String>] [-SecureStoreTargetApplicationId <String>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the `New-SPODataConnectionSetting` cmdlet to create a new Business Data Connectivity service connection and its associated metadata properties in the farm. -To see the metadata settings, use the `Get-SPODataConnectionSettingMetaData` cmdlet. - -This cmdlet applies to an on-premises environment only. -You cannot use this command in the SharePoint Online Management Shell. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251831> (<https://go.microsoft.com/fwlink/p/?LinkId=251831).> - -## EXAMPLES - -### ------------------EXAMPLE------------------ - -```powershell -New-SPODataConnectionSetting -Name "ContosoServiceApp" -ServiceContext "http://contoso/" -ServiceAddressURL "https://expensereporting.cloudapp.net/expensereporting.svc" -AuthenticationMode "Credentials" -SecureStoreTargetApplicationId "DallasUserName" -``` - -This example creates a new Business Data Connectivity service connection named ContosoServiceApp. - -In this process, a Microsoft Business Connectivity Services connection metadata object is created. - -## PARAMETERS - -### -AuthenticationMode - -Specifies the type of authentication mode required for the Business Connectivity Services connection. - -The value for the authentication mode is any one of the following options: - -```yaml -Type: ODataAuthenticationMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceAddressURL - -Specifies the URL for the OData service. -The URL does not have be Internet facing. -This is the final destination from which data is retrieved. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext - -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object. -An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the name of the Business Connectivity Services connection object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExtensionProvider - -{{Fill ExtensionProvider Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureStoreTargetApplicationId - -Specifies the Secure Store Target Application ID. -Works in conjunction with the AuthenticationMode parameter. - -The value for the SecureStoreTargetApplicationId parameter is any one of the following options: - ---Credentials ---WindowsCredentials ---DigestCredentials ---ClientCertificate - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPODataConnectionSetting](Get-SPODataConnectionSetting.md) - -[Remove-SPODataConnectionSetting](Remove-SPODataConnectionSetting.md) - -[Set-SPODataConnectionSetting](Set-SPODataConnectionSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationEncryptionParameters.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationEncryptionParameters.md deleted file mode 100644 index acec63f17e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationEncryptionParameters.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-spomigrationencryptionparameters -applicable: SharePoint Online -title: New-SPOMigrationEncryptionParameters -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOMigrationEncryptionParameters - -## SYNOPSIS - -Creates a new random encryption key for a migration job or package. - -## SYNTAX - -```powershell -New-SPOMigrationEncryptionParameters [<CommonParameters>] -``` - -## DESCRIPTION - -Creates a random encryption key for submission of a migration job or creation of a migration package. For use with [`Submit-SPOMigrationJob`](), [`ConvertTo-SPOMigrationEncryptedPackage`](ConvertTo-SPOMigrationEncryptedPackage.md), and [`Set-SPOMigrationPackageAzureSource`](Set-SPOMigrationPackageAzureSource.md) in the `-EncryptedParameter` parameter for each cmdlet. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -$o = New-SPOMigrationEncryptionParameters -``` - -Outputs a random encryption key and saves it in the `$o` variable. - -## 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/?LinkID=113216). - -## OUTPUTS - -### System.Byte - -EncryptionKey: The randomly generated encryption key using [System.Security.Cryptography.AesCryptoServiceProvider](https://docs.microsoft.com/dotnet/api/system.security.cryptography.aescryptoserviceprovider) class. - -### Microsoft.Online.SharePoint.Migration.SPMigrationJobEncryptionMethod - -EncryptionMethod: The encryption algorithm used to generate the EncryptionKey. Currently hardcoded to AES256BC. - -## RELATED LINKS - -[Submit-SPOMigrationjob](Submit-SPOMigrationJob.md) - -[ConvertTo-SPOMigrationEncryptedPackage](ConvertTo-SPOMigrationEncryptedPackage.md) - -[Set-SPOMigrationPackageAzureSource](Set-SPOMigrationPackageAzureSource.md) - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationPackage.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationPackage.md deleted file mode 100644 index 194d6dff72..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationPackage.md +++ /dev/null @@ -1,253 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-spomigrationpackage -applicable: SharePoint Online -title: New-SPOMigrationPackage -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOMigrationPackage - -## SYNOPSIS - -Cmdlet to create a new migration package based on source files in a local or network shared folder. - -## SYNTAX - -```powershell -New-SPOMigrationPackage [-SourceFilesPath] <String> [-OutputPackagePath] <String> [[-TargetWebUrl] <String>] - [[-TargetDocumentLibraryPath] <String>] [[-TargetDocumentLibrarySubFolderPath] <String>] [-IgnoreHidden] - [-IncludeFileSharePermissions] [-NoAzureADLookup] [-NoLogFile] [-ReplaceInvalidCharacters] - [<CommonParameters>] -``` - -## DESCRIPTION - -Cmdlet to create a new migration package based on source files in a local or network shared folder. - -> [!NOTE] -> Limits on the SPO package size and file size -> -> | Limit | Max Size (Gb) | Description | -> | :---: | :---: | :---: | -> | Package Size | 2-4 | The whole package can't exceed 4Gb | -> | File Size | 2 | A single file inside the source folder can't exceed 2 Gb. | -> | Target Size | -| target site should remain non-accessible to end user until migration is complete| -> [!NOTE] -> Limits on HTTP Get -> -> | Limit | API Get (chars) | Description | -> | :---: | :---: | :---: | -> | Action GET on API | 260 chars | The size of the API GET request can't exceed 260 chars| - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -New-SPOMigrationPackage -SourceFilesPath \\fileserver\share\folder1 -OutputPackagePath d:\MigrationPackages\Folder1_SrcPkg - -New-SPOMigrationPackage -SourceFilesPath \\fileserver\share\folder1 -OutputPackagePath d:\MigrationPackages\Folder1_SrcPkg -TargetWebUrl https://contoso.sharepoint.com/sites/TargetSite/TargetWeb -TargetDocumentLibraryPath "Shared Documents" -TargetDocumentLibrarySubFolderPath "Sub Folder/Target Folder" -``` - -This example creates a new set of migration source package metadata files, using default URL values, in the d:\MigrationPackages\Folder1_SrcPkg directory based on content files found in the \\fileserver\share\folder1 source location. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -New-SPOMigrationPackage -SourceFilesPath \\fileserver\share\folder1 -OutputPackagePath d:\MigrationPackages\Folder1_SrcPkg -TargetWebUrl https://contoso.sharepoint.com/sites/TargetSite/TargetWeb -TargetDocumentLibraryPath "Shared Documents" -``` - -This example creates a new set of migration source package metadata files in the d:\MigrationPackages\Folder1_SrcPkg directory based on content files found in the \\fileserver\share\folder1 source location. The package is prepared using the document library path "https://contoso.sharepoint.com/sites/TargetSite/TargetWeb/Shared%20Documents". - -## PARAMETERS - -### -IgnoreHidden - -Switch to ignore hidden files and folders. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeFileSharePermissions - -Used to include permissions and sharing information into the generated manifest files in the package metadata. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoAzureADLookup - -Switch to not lookup local user accounts in Azure Active Directory. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -Used to not create a log file. The default is to create a new CreateMigrationPackage log file within the directory specified within the OutputPackagePath parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputPackagePath - -The directory location where the output package metadata files will be saved. If the directory does not exist, it will be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReplaceInvalidCharacters - -Switch to replace characters in file and folder names that would be invalid in SharePoint Online. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceFilesPath - -The directory location where the source content files exist. This directory will be enumerated to create the package metadata files. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDocumentLibraryPath - -The web relative document library to use as the document library part of the base URL in the package metadata. If this is not supplied, "Documents" will be used within the package metadata instead. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDocumentLibrarySubFolderPath - -Specifies the document library relative subfolder to use as the folder path part of the base URL in the package metadata. If this is not provided, no value will be used within the package metadata. The files will be homed under the document library root. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetWebUrl - -The fully qualified web URL to use as the web address part of the base URL in the package metadata. If this is not provided, "<http://fileserver/sites/user"> will be used instead within the package metadata. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOPublicCdnOrigin.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOPublicCdnOrigin.md deleted file mode 100644 index 569d6c5c8a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOPublicCdnOrigin.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-spopubliccdnorigin -applicable: SharePoint Online -title: New-SPOPublicCdnOrigin -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOPublicCdnOrigin - -## SYNOPSIS - -Creates a new public CDN on a document library in your Sharepoint Online Tenant - -## SYNTAX - -```powershell -New-SPOPublicCdnOrigin [-Url] <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This Cmdlet creates a new Public CDN Origin in your SPO Tenant - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -New-SPOPublicCdnOrigin -URL https://contoso.sharepoint.com/sites/CDN/CDNFilesLibrary/ -``` - -This example shows how to you can setup a new Public CDN on a document library in your SharePoint online tenant. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url - -Specify the URL that will be enabled for Public CDN in your tenant - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## NOTES - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOPublicCdnOrigins](Get-SPOPublicCdnOrigins.md) - -[Remove-SPOPublicCdnOrigin](Remove-SPOPublicCdnOrigin.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSdnProvider.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSdnProvider.md deleted file mode 100644 index be5ec82b4b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSdnProvider.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-sposdnprovider -applicable: SharePoint Online -title: New-SPOSdnProvider -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOSdnProvider - -## SYNOPSIS - -Adds a new Software-Defined Networking (SDN) provider - -## SYNTAX - -```powershell -New-SPOSdnProvider [-Identity] <String> [-License] <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This Cmdlet creates a new Software-Defined Networking, and it receives two parameters, the Identity (ID) of the Hive and the License key of the Hive. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -New-SPOSdnProvider -ID "Hive" -License "<Hive license key>" -``` - -This example creates the Hive for a SDN Provider. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -License - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Remove-SPOSdnProvider](Remove-SPOSdnProvider.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSite.md deleted file mode 100644 index c053ac412b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSite.md +++ /dev/null @@ -1,253 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-sposite -applicable: SharePoint Online -title: New-SPOSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOSite - -## SYNOPSIS - -Creates a new SharePoint Online site collection for the current company. - -## SYNTAX - -```powershell -New-SPOSite [-CompatibilityLevel <Int32>] [-LocaleId <UInt32>] [-NoWait] -Owner <String> - [-ResourceQuota <Double>] -StorageQuota <Int64> [-Template <String>] [-TimeZoneId <Int32>] [-Title <String>] - -Url <UrlCmdletPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -The `New-SPOSite` cmdlet creates a new site collection for the current company. -However, creating a new SharePoint Online site collection fails if a deleted site with the same URL exists in the Recycle Bin. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832>. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -New-SPOSite -Url https://contoso.sharepoint.com/sites/mynewsite -Owner joe.healy@contoso.com -StorageQuota 1000 -Title "My new site collection" -``` - -Example 1 creates a new site collection for the current company with specified site URL, title and owner. The storage quota is set to 1000 megabytes. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -New-SPOSite -Url https://contoso.sharepoint.com/sites/mynewsite -Owner joe.healy@contoso.com -StorageQuota 1000 -CompatibilityLevel 15 -LocaleID 1033 -ResourceQuota 300 -Template "STS#0" -TimeZoneId 13 -Title "My new site collection" -``` - -Example 2 creates a new site collection for the current company with specified site URL, title, owner and template. The storage quota is set to 1000 megabytes and the resource quota is set to 300 megabytes. The template compatibility level is set to 15 which means that the site collection only supports the SharePoint 2013 template. The language is set to English - United States (LocaleID = 1033) and the time zone is set to (GMT-08:00) Pacific Time (US and Canada) (TimeZone = 13). - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -New-SPOSite -Url https://contoso.sharepoint.com/sites/accounting -Owner admin@contoso.com -StorageQuota 100 -NoWait -ResourceQuota 50 -Template STS#0 -``` - -Example 3 creates a new site collection for the current company with specified site URL, owner and template. The storage quota is set to 100 megabytes and the resource quota is set to 50 megabytes. This cmdlet is executed immediately without delay. - -## PARAMETERS - -### -CompatibilityLevel - -Specifies the version of templates to use when you are creating a new site collection. This value sets the initial CompatibilityLevel value for the site collection. The values for this parameter can be SharePoint Server. When this parameter is not specified, the CompatibilityLevel will be by default the highest possible version for the Web application. - -> [!NOTE] -> For SharePoint Online Preview, it can only be set to "14" or "15". "14" indicates SharePoint 2010 Products, "15" indicates SharePoint 2013. Other values are not valid and will cause error. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocaleId - -Specifies the language of this site collection. For more information, see Locale IDs Assigned by Microsoft (<https://go.microsoft.com/fwlink/p/?LinkId=242911>). The Template and LocaleId parameters must be a valid combination as returned from the `Get-SPOWebTemplate` cmdlet. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoWait - -Specifies to continue executing script immediately. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner - -Specifies the user name of the site collection's primary owner. The owner must be a email-enabled user instead of a security group or an email-enabled security group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResourceQuota - -Specifies the quota for this site collection in Sandboxed Solutions units. This value must not exceed the company's aggregate available Sandboxed Solutions quota. The default value is 0. For more information, see Resource Usage Limits on Sandboxed Solutions in SharePoint (<https://msdn.microsoft.com/en-us/library/gg615462.aspx).> Note that this parameter is now obsolete and has been deprecated. - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StorageQuota - -Specifies the storage quota for this site collection in megabytes. This value must not exceed the company's available quota. - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template - -Specifies the site collection template type. Use the `Get-SPOWebTemplate` cmdlet to get the list of valid templates. If no template is specified, one can be added later. The Template and LocaleId parameters must be a valid combination as returned from the `Get-SPOWebTemplate` cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeZoneId - -Specifies the time zone of the site collection. For more information, see SPRegionalSettings.TimeZones Property (<https://go.microsoft.com/fwlink/p/?LinkId=242912).> - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title - -Specifies the title of the site collection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url - -Specifies the full URL of the new site collection. It must be in a valid managed path in the company's site. For example, for company contoso, valid managed paths are <https://contoso.sharepoint.com/sites> and <https://contoso.sharepoint.com/teams.> - -```yaml -Type: UrlCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOSite](Get-SPOSite.md) - -[Set-SPOSite](Set-SPOSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSiteGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSiteGroup.md deleted file mode 100644 index 108121a21e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOSiteGroup.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-spositegroup -applicable: SharePoint Online -title: New-SPOSiteGroup -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOSiteGroup - -## SYNOPSIS - -Creates a new group in a SharePoint Online site collection. - -## SYNTAX - -```powershell -New-SPOSiteGroup -Group <String> -PermissionLevels <String[]> -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -A SharePoint group is a set of individual users. -SharePoint groups enable you to manage sets of users instead of individual users. - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -New-SPOSiteGroup -Site https://contoso.sharepoint.com/sites/siteA -Group "Project Leads" -PermissionLevels "Full Control" -``` - -This example creates a group named Project Leads with the Full Control permission level on the site collection <https://contoso.sharepoint.com/sites/siteA.> - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -New-SPOSiteGroup -Site https://contoso.sharepoint.com/sites/marketing -Group "NewGroupName" -PermissionLevels "Design" -``` - -This example creates a group named NewGroupName with the Design permission level on the site collection <https://contoso.sharepoint.com/sites/marketing.> - -## PARAMETERS - -### -Group - -Specifies the name of the group to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionLevels - -Specifies the permission levels to grant to the newly created group. It can be any permission level that exists on the site collection on which the group is being created. - -> [!NOTE] -> Permission Levels, are defined on the top-level site of the site collection, please see [How to create and edit permission levels](https://docs.microsoft.com/sharepoint/how-to-create-and-edit-permission-levels) for more information. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the site collection to add the group to. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[New-SPOSite](New-SPOSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOTenantOrgRelation.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOTenantOrgRelation.md deleted file mode 100644 index cbe2787196..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOTenantOrgRelation.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/New-SPOTenantOrgRelation -applicable: SharePoint Online -title: New-SPOTenantOrgRelation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOTenantOrgRelation - -## SYNOPSIS - -{{ Fill in the Synopsis }} - -## SYNTAX - -```poowershell -New-SPOTenantOrgRelation [-Scenario] <OrgRelationScenario> [-PartnerRole] <OrgRelationRole> [-PartnerCompanyId] <Guid> [-PartnerInstanceId <Guid>] [-PartnerSiteSubscriptionId <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION - -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 - -```powershell -PS C:\> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -PartnerCompanyId - -{{ Fill PartnerCompanyId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerInstanceId - -{{ Fill PartnerInstanceId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerRole - -{{ Fill PartnerRole Description }} - -```yaml -Type: OrgRelationRole -Parameter Sets: (All) -Aliases: -Accepted values: None, Source, Target - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerSiteSubscriptionId - -{{ Fill PartnerSiteSubscriptionId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scenario - -{{ Fill Scenario Description }} - -```yaml -Type: OrgRelationScenario -Parameter Sets: (All) -Aliases: -Accepted values: None, MnA - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy.md deleted file mode 100644 index c907834fc7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/new-sponlineapplicationprincipalmanagementserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy - -## SYNOPSIS - -Creates a new SharePoint Online management Application Proxy Name - -## SYNTAX - -```powershell -New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] -Name <String> - -OnlineTenantUri <String> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This Cmdlet is used to create a new Application Proxy name, for example usually when you run [this script](https://www.microsoft.com/en-us/download/confirmation.aspx?id=51490) you onboard your SharePoint Online (SPO) tenant and your SharePoint server cloud SSA to cloud hybrid search. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy -Name $SPO_MANAGEMENT_APPPROXY_NAME -OnlineTenantUri $PortalUrl -DefaultProxyGroup -``` - -Found the proxies for the tenant on the variable $PortalUrl on the Default Proxy Group. - -## PARAMETERS - -### -AssignmentCollection - -After the creation of the new Principal Management Service Application proxy assign it to the collection. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup - -Search Proxies on the default Proxy Group - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -SPO Management AppProxy Name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlineTenantUri - -Define the online Tenant URI. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Start-SPOUserAndContentMove](Start-SPOUserAndContentMove.md) - -[Full Download to Hybrid Scripts](https://www.microsoft.com/en-us/download/confirmation.aspx?id=51490) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Register-SPODataEncryptionPolicy.md b/sharepoint/sharepoint-ps/sharepoint-online/Register-SPODataEncryptionPolicy.md deleted file mode 100644 index 6b2556283c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Register-SPODataEncryptionPolicy.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/register-spodataencryptionpolicy -applicable: SharePoint Online -title: Register-SPODataEncryptionPolicy -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Register-SPODataEncryptionPolicy - -## SYNOPSIS - -Cmdlet to register customer encryption status for your geo tenant. -For more information, see [Controlling your data in Office 365 using Customer Key](https://docs.microsoft.com/microsoft-365/compliance/controlling-your-data-using-customer-key) - -## SYNTAX - -```powershell -Register-SPODataEncryptionPolicy [-Identity] <SpoSitePipeBind> -PrimaryKeyVaultName <string> -PrimaryKeyName <string> -PrimaryKeyVersion <guid> -SecondaryKeyVaultName <string> -SecondaryKeyName <string> -SecondaryKeyVersion <guid> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Update-DataEncryptionPolicy cmdlet to register customer encryption status for your geo tenant. -For more information, see [Controlling your data in Office 365 using Customer Key](https://docs.microsoft.com/microsoft-365/compliance/controlling-your-data-using-customer-key) - -## EXAMPLES - -### Example 1 - -```powershell -Register-SPODataEncryptionPolicy -Identity https://contoso.sharepoint.com -PrimaryKeyVaultName <string> -PrimaryKeyName <string> -PrimaryKeyVersion <KeyVersion> -``` - -This example registers the DEP used with SharePoint Online and OneDrive for Business to start using the given primary key - -## PARAMETERS - -### -Identity - -Specifies the URL of the admin site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimaryKeyVaultName - -The name of the primary key vault - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimaryKeyName - -The name of the primary key - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimaryKeyVersion - -The version of the primary key - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryKeyVaultName - -The name of the secondary key vault - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryKeyName - -The name of the secondary key - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryKeyVersion - -The version of the secondary key - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. - -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. - -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Register-SPOHubSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Register-SPOHubSite.md deleted file mode 100644 index a0b1aaf42b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Register-SPOHubSite.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/register-spohubsite -applicable: SharePoint Online -title: Register-SPOHubSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Register-SPOHubSite - -## SYNOPSIS - -Enables the hub site feature on a site to make it a hub site. For more information visit [SharePoint hub sites overview](https://docs.microsoft.com/sharepoint/dev/features/hub-site/hub-site-overview). - -## SYNTAX - -```powershell -Register-SPOHubSite -Site <SpoSitePipeBind> -Principals <string[]> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to register an existing site collection as a hub site. - -> [!IMPORTANT] -> A maximum of 2000 hub sites may be created per tenant, with 'unlimited' number of site collections associated to a hub site. -> [!NOTE] -> It can take up to 2-4 hours for the changes to appear. - -## EXAMPLES - -### Example 1 - -```powershell -Register-SPOHubSite https://contoso.sharepoint.com/sites/Marketing -Principals $null -``` - -This example registers the marketing site on Contoso as hub site without setting any principals for it. - -## PARAMETERS - -### -Site - -Specifies the URL of the site collection to which to enable the hub site features. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Principals - -Specifies One or more principles (user or group) to be granted rights to the specified HubSite. Can be used to filter who can associate sites to this hub site. - -```yaml -Type: string[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## NOTES - -If the site doesn't exist, this cmdlet returns a "File not found" error. - -If the site is already a hub site, this cmdlet returns a "This site is already a HubSite" error. - -If the site is already associated with another hub site, this cmdlet returns a "This site is currently associated with a HubSite" error. You'll need to run the [Remove-SPOHubSiteAssociation](Remove-SPOHubSiteAssociation.md) cmdlet first before you can make the site a hub site. diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPODataConnectionSetting.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPODataConnectionSetting.md deleted file mode 100644 index cd0ae78a40..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPODataConnectionSetting.md +++ /dev/null @@ -1,211 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spodataconnectionsetting -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Remove-SPODataConnectionSetting -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPODataConnectionSetting - -## SYNOPSIS - -Removes a Business Connectivity Services connection. - -## SYNTAX - -### Identity - -```powershell -Remove-SPODataConnectionSetting [-Identity] <ODataConnectionSettings> - -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -### Name - -```powershell -Remove-SPODataConnectionSetting -ServiceContext <SPServiceContextPipeBind> -Name <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (<https://go.microsoft.com/fwlink/?LinkID=187810).> - -Use the `Remove-SPODataConnectionSetting` cmdlet to remove a Business Connectivity Services connection for a particular Business Connectivity Services service application in the farm. - -The metadata object associated with the Business Connectivity Services connection is also deleted. - -This cmdlet applies to an on-premises environment only. -You cannot use this command in the SharePoint Online Management Shell. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251831> (<https://go.microsoft.com/fwlink/p/?LinkId=251831).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Remove-SPODataConnectionSetting -ServiceContext "http://contoso/" -Name "ContosoServiceApp" -``` - -This example removes the Business Connectivity Services connection named ContosoServiceApp. -Metadata properties are also removed. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Remove-SPODataConnectionSetting -ServiceContext "http://contoso/" -Name "ContosoServiceApp-metadata" -``` - -This example removes the Business Connectivity Services connection metadata named ContosoServiceApp. - -The associated Business Connectivity Services connection object is also removed. - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -$ConnectionVariable = Get-SPODataConnectionSettingMetadata -ServiceContext http://contoso -Name "ContosoServiceApp" - -Remove-SPODataConnectionSetting -Identity $ConnectionVariable -ServiceContext "http://contoso/" -``` - -This example removes the Business Connectivity Services and its associated metadata connection named ContosoServiceApp. - -## PARAMETERS - -### -Identity - -Specifies the OData Connection Settings object. - -```yaml -Type: ODataConnectionSettings -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceContext - -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object. -An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the name of the existing Business Connectivity Services connection. - -```yaml -Type: String -Parameter Sets: Name -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPODataConnectionSetting](Get-SPODataConnectionSetting.md) - -[New-SPODataConnectionSetting](New-SPODataConnectionSetting.md) - -[Set-SPODataConnectionSetting](Set-SPODataConnectionSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPODeletedSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPODeletedSite.md deleted file mode 100644 index 8aa83411a0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPODeletedSite.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spodeletedsite -applicable: SharePoint Online -title: Remove-SPODeletedSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPODeletedSite - -## SYNOPSIS - -Removes a SharePoint Online deleted site collection from the Recycle Bin. - -## SYNTAX - -```powershell -Remove-SPODeletedSite [-Confirm] -Identity <SpoSitePipeBind> [-NoWait] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Remove-SPODeletedSite` cmdlet permanently removes a SharePoint Online deleted site collection from the Recycle Bin. - -You must be a SharePoint Administrator or Global Administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -**Note**: As of today, the modern admin center UI does not allow permanent deletion of group connected site, but the use of this cmdlet does allow the deletion, but when this occurs it does not delete the associated group, just the site. - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- - -```powershell -Remove-SPODeletedSite -Identity https://contoso.sharepoint.com/sites/sitetoremove -``` - -This example removes a SharePoint Online deleted site collection named <https://contoso.sharepoint.com/sites/sitetoremove> from the Recycle Bin and deletes it permanently. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the URL of the site collection to remove. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NoWait - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Remove-SPOSite](Remove-SPOSite.md) - -[Get-SPODeletedSite](Get-SPODeletedSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOExternalUser.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOExternalUser.md deleted file mode 100644 index cfb758ba31..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOExternalUser.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spoexternaluser -applicable: SharePoint Online -title: Remove-SPOExternalUser -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOExternalUser - -## SYNOPSIS - -Removes a collection of external users from the tenancy's folder. - -## SYNTAX - -```powershell -Remove-SPOExternalUser [-Confirm] -UniqueIDs <String[]> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Remove-SPOExternalUser` cmdlet permanently removes a collection of external users from the tenancy's folder. - -Users who are removed lose access to all tenant resources. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- - -```powershell -$user = Get-SPOExternalUser -Filter someone@example.com -Remove-SPOExternalUser -UniqueIDs @($user.UniqueId) -``` - -This example removes a specific external user who has the address "someone@example.com". Organization members may still see the external user name displayed in the Shared With dialog, but the external user will not be able to sign in and will not be able to access any tenant resources. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UniqueIDs - -Specifies an ID that can be used to identify an external user based on their Windows Live ID. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOExternalUser](Get-SPOExternalUser.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOGeoAdministrator.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOGeoAdministrator.md deleted file mode 100644 index 9b520f0d9c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOGeoAdministrator.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spogeoadministrator -applicable: SharePoint Online -title: Remove-SPOGeoAdministrator -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOGeoAdministrator - -## SYNOPSIS - -Removes a new SharePoint user or security Group in the current Multi-Geo Tenant. - -## SYNTAX - -```powershell -Remove-SPOGeoAdministrator [-LoginName] <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains a single parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (<https://go.microsoft.com/fwlink/?LinkID=187810).> - -The `Remove-SPOGeoAdministrator` cmdlet matches a user or a security group and remove the GeoAdministrator privileges in the SharePoint Organization. - -You must be a SharePoint Online global administrator, and you must have a Multi-Geo Tenant to run the `Remove-SPOGeoAdministrator` cmdlet successfully. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOGeoAdministrator contosoadmin -``` - -Remove the GeoAdministrator privileges to the user contosoadmin of the SharePoint Online multi-geo tenant. - -### Example 2 - -```powershell -Remove-SPOGeoAdministrator -LoginName contosoadmin -``` - -Same as example 1, but using the LoginName parameter explicitly. - -## PARAMETERS - -### -LoginName - -It's the user Principal Name or UPN of a user. Typically the username that he uses to log in. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Add-SPOGeoAdministrator](Add-SPOGeoAdministrator.md) - -[Get-SPOGeoAdministrator](Get-SPOGeoAdministrator.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHomeSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHomeSite.md deleted file mode 100644 index 51262dd965..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHomeSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spohomesite -applicable: SharePoint Online -title: Remove-SPOHomeSite -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Remove-SPOHomeSite - -## SYNOPSIS - -Removes the current SharePoint Online Home site setting. - -## SYNTAX - -```powershell -Remove-SPOHomeSite [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to remove the current SharePoint Online Home Site setting. - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOHomeSite -``` - -This example removes the current SharerPoint Online Home Site setting. - -## 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHubSiteAssociation.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHubSiteAssociation.md deleted file mode 100644 index 446a8beebf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHubSiteAssociation.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spohubsiteassociation -applicable: SharePoint Online -title: Remove-SPOHubSiteAssociation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOHubSiteAssociation - -## SYNOPSIS - -Removes a site from its associated hub site. - -## SYNTAX - -```powershell -Remove-SPOHubSiteAssociation [-Site] <SpoSitePipeBind> -[<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to remove an association between a site and a hub site. - -> [!IMPORTANT] -> This cmdlet is currently in preview and is subject to change. It is not currently supported for use in production environments. - -If the site or hub site doesn't exist, this cmdlet returns a "File not found" error. - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOHubSiteAssociation https://contoso.sharepoint.com/sites/Research -``` - -This example removes the research site from the marketing hub site. - -## PARAMETERS - -### -Site - -URL of the site to remove from the hub site. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHubToHubAssociation.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHubToHubAssociation.md deleted file mode 100644 index c142302bee..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHubToHubAssociation.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spohubtohubassociation -applicable: SharePoint Online -title: Remove-SPOHubToHubAssociation -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Remove-SPOHubToHubAssociation - -## SYNOPSIS - -Removes the selected hub site from its parent hub. - -## SYNTAX - -```powershell -Remove-SPOHubToHubAssociation [-HubSite] <SpoHubSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to remove the selected hub site from its parent hub. - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOHubToHubAssociation -HubSite https://contoso.sharepoint.com/sites/Research -``` - -This example removes <https://contoso.sharepoint.com/sites/Research> from its parent Hub. - -## PARAMETERS - -### -Hubsite - -Url of the Hub site to be removed from its parent Hub. - -```yaml -Type: SpoHubSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMigrationJob.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMigrationJob.md deleted file mode 100644 index 0db6d0cb22..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMigrationJob.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spomigrationjob -applicable: SharePoint Online -title: Remove-SPOMigrationJob -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOMigrationJob - -## SYNOPSIS - -Cmdlet to remove a previously created migration job from the specified site collection. - -## SYNTAX - -```powershell -Remove-SPOMigrationJob [-TargetWebUrl] <String> [-JobId] <Guid> -Credentials <CredentialCmdletPipeBind> - [-NoLogFile] [<CommonParameters>] -``` - -## DESCRIPTION - -Cmdlet to remove a previously created migration job from the specified site collection. - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- - -```powershell -Remove-SPOMigrationJob -JobId 4da9e777-3e38-4804-96d9-ddeebe7dfa79 -TargetUrl https://contoso.sharepoint.com/sites/TargetSite -``` - -This example removes the specified migration job from the site collection "<https://contoso.sharepoint.com/sites/TargetSite".> - -## PARAMETERS - -### -Credentials - -Optional credentials of a site collection administrator to use to connect to the site collection. The credentials should supply the username in UPN format (e.g. user@company.onmicrosoft.com). If this property is not set, the current tenant admin credentials from the session's previous call to `Connect-SPOService` will be used to connect to the site collection. - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobId - -Id of a previously created migration job that exists on the target site collection. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -Indicates to not create a log file. The default is to create a new DeleteMigrationJob log file within the current directory. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetWebUrl - -The fully qualified URL of the site collection where the job will be deleted if found. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMultiGeoCompanyAllowedDataLocation.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMultiGeoCompanyAllowedDataLocation.md deleted file mode 100644 index 17a937bb96..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMultiGeoCompanyAllowedDataLocation.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spomultigeocompanyalloweddatalocation -applicable: SharePoint Online -title: Remove-SPOMultiGeoCompanyAllowedDataLocation -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Remove-SPOMultiGeoCompanyAllowedDataLocation - -## SYNOPSIS - -Use this cmdlet to remove a multi geo allowed location. - -## SYNTAX - -```powershell -Remove-SPOMultiGeoCompanyAllowedDataLocation [-Location] <string> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Removes a specified multi-geo location that was previously allowed by [Set-SPOMultiGeoCompanyAllowedDataLocation](Set-SPOMultiGeoCompanyAllowedDataLocation.md). - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOMultiGeoCompanyAllowedDataLocation -Location AUS -``` -Removes AUS (Australia) as an allowed mutli-geo location. - -## PARAMETERS - -### -Location - -The Preferred Data Location (PDL) to remove. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES - -## RELATED LINKS - -[Set-SPOMultiGeoCompanyAllowedDataLocation](Set-SPOMultiGeoCompanyAllowedDataLocation.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOOrgAssetsLibrary.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOOrgAssetsLibrary.md deleted file mode 100644 index 883be53c14..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOOrgAssetsLibrary.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spoorgassetslibrary -applicable: SharePoint Online -title: Remove-SPOOrgAssetsLibrary -author: Maralesfahanpoor -ms.author: maesfaha -ms.reviewer: -manager: paulac -schema: 2.0.0 ---- - -# Remove-SPOOrgAssetsLibrary - -## SYNOPSIS - -Removes a library that was designated as a central location for organization assets across the tenant. - -## SYNTAX - -```powershell -Remove-SPOOrgAssetsLibrary [-LibraryUrl <String>] [-ListId <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION - -The Remove-SPOOrgAssetsLibrary cmdlet removes a library that was designated as a central location for organization assets across the tenant. Once this cmdlet is run, this library will no longer be accessible from the "Your organization" tab in the file picker. When running the cmdlet, either the library URL or library ID (not both) needs to be indicated. - -Once the library is removed, CDN will still be enabled for this library. To disable CDN for this library, use Remove-SPOTenantCdnOrigin with the server relative URL (example: /sites/branding/assets). - -## EXAMPLES - -### Example 1 - -This example removes https://contoso.sharepoint.com/sites/branding/Assets as a designated library using the library ID. Assets within this library will no longer be accessible from the "Your organization" tab in the file picker. - -```powershell -Remove-SPOOrgAssetsLibrary -ListId 58454454-6546-6466-9769-646464623988 -``` - -## PARAMETERS - -### -LibraryUrl - -Indicates the server relative URL of the library to be removed as a central location for organization assets. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ListId - -Indicates the library ID for the library to be removed as a central location for organization assets. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/add-spoorgassetslibrary?view=sharepoint-ps) - -[Set-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/set-spoorgassetslibrary?view=sharepoint-ps) - -[Get-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoorgassetslibrary?view=sharepoint-ps) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOOrgNewsSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOOrgNewsSite.md deleted file mode 100644 index 584fa82079..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOOrgNewsSite.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spoorgnewssite -applicable: SharePoint Online -title: Remove-SPOOrgNewsSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen ---- - -# Remove-SPOOrgNewsSite - -## SYNOPSIS - -Removes a given site from the list of organizational news sites based on its URL in your Sharepoint Online Tenant - -## SYNTAX - -```powershell -Remove-SPOOrgNewsSite -OrgNewsSiteUrl <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet will remove a site from list of organizational news sites based on its URL. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Remove-SPOOrgNewsSite -OrgNewsSiteUrl https://contoso.sharepoint.com/sites/Marketing -``` - -This example removes <https://contoso.sharepoint.com/sites/Marketing> from the list of organizational news sites. - -## PARAMETERS - -### -OrgNewsSiteUrl - -The URL of a site to be marked as an organizational news site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Get-SPOOrgNewsSite](Get-SPOOrgNewsSite.md) - -[Set-SPOOrgNewsSite](Set-SPOOrgNewsSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOPublicCdnOrigin.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOPublicCdnOrigin.md deleted file mode 100644 index e28eed6dce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOPublicCdnOrigin.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spopubliccdnorigin -applicable: SharePoint Online -title: Remove-SPOPublicCdnOrigin -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOPublicCdnOrigin - -## SYNOPSIS - -Removes a given public CDN origin based on its identity (id) in your Sharepoint Online Tenant - -## SYNTAX - -```powershell -Remove-SPOPublicCdnOrigin [-Identity] <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet will remove a Public CDN Origin based on its identity. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -#Get a list of CDN origins - -Get-SPOPublicCdnOrigins -Id Url --- --- -11270051ee79e73829f6e7a3ee5d900d49c4fc5901645c642b799ecb62787a5069ca80fb HTTPS://CONTOSO.SHAREPOINT.COM/SITES/CDN... -#then remove the CDN by Identity id GUID. -Remove-SPOPublicCdnOrigin -Identity 11270051ee79e73829f6e7a3ee5d900d49c4fc5901645c642b799ecb62787a5069ca80fb -``` - -This example returns a list of CDN origins and then removes an origin based on the identity. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -It's the unique identifier of the Public CDN path, it can be queried using the Cmdlet Get-SpoPublicCdnOrigins - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Add-SPOGeoAdministrator](Add-SPOGeoAdministrator.md) - -[New-SPOPublicCdnOrigin](New-SPOPublicCdnOrigin.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSdnProvider.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSdnProvider.md deleted file mode 100644 index 8cc9c06dbd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSdnProvider.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-sposdnprovider -applicable: SharePoint Online -title: Remove-SPOSdnProvider -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOSdnProvider - -## SYNOPSIS - -Removes Software-Defined Networking (SDN) Support in your SharePoint Online tenant - -## SYNTAX - -```powershell -Remove-SPOSdnProvider [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Removes SDN Support in your SharePoint Online tenant - -## EXAMPLES - -### EXAMPLE 1 - -```yaml -Remove-SPOSdnProvider -Confirm:false -``` - -This command removes the SDN support for your Online Tenant without confirmation. - -### -----------------------EXAMPLE 2----------------------------- - -```yaml -Remove-SPOSdnProvider -Confirm:true -WhatIf -``` - -This command will prompt for a confirmation before "simulating" that it will remove the support for SDN in the current SPO tenant (-WhatIf) - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[New-SPOSdnProvider](New-SPOSdnProvider.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSite.md deleted file mode 100644 index f3d8e7eda6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSite.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-sposite -applicable: SharePoint Online -title: Remove-SPOSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOSite - -## SYNOPSIS - -Sends a SharePoint Online site collection to the SharePoint Online Recycle Bin. - -## SYNTAX - -```powershell -Remove-SPOSite [-Confirm] -Identity <SpoSitePipeBind> [-NoWait] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Remove-SPOSite` cmdlet does not delete a site collection from the site collections list permanently. -Instead, the removed site collection is moved to the Recycle Bin. -You can use the `Restore-SPODeletedSite`cmdlet to restore a site collection from the Recycle Bin. -To delete a site collection permanently, first move the site collection to the Recycle Bin by using the `Remove-SPOSite` cmdlet and then delete it from the Recycle Bin by using the `Remove-SPODeletedSite` cmdlet. - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Remove-SPOSite -Identity https://contoso.sharepoint.com/sites/site1 -NoWait -``` - -This example immediately removes the site collection named <https://contoso.sharepoint.com/sites/site1> from the site collections list and moves it to the Recycle Bin. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the URL of the site collection to remove. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NoWait - -Specifies to continue executing script immediately. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Remove-SPODeletedSite](Remove-SPODeletedSite.md) - -[Restore-SPODeletedSite](Restore-SPODeletedSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteCollectionAppCatalog.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteCollectionAppCatalog.md deleted file mode 100644 index 088898e478..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteCollectionAppCatalog.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spositecollectionappcatalog -applicable: SharePoint Online -title: Remove-SPOSiteCollectionAppCatalog -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Remove-SPOSiteCollectionAppCatalog - -## SYNOPSIS - -Removes the site collection app catalog. - -## SYNTAX - -```powershell -Remove-SPOSiteCollectionAppCatalog [-Site] <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to remove the site collection app catalog. - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOSiteCollectionAppCatalog -Site https://contoso.sharepoint.com/sites/Research -``` - -This example removes the site collection app catalog from the site <https://contoso.sharepoint.com/sites/Research.> - -## PARAMETERS - -### -Site - -Url of the site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteCollectionAppCatalogById.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteCollectionAppCatalogById.md deleted file mode 100644 index 79618f9c81..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteCollectionAppCatalogById.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spositecollectionappcatalogbyid -applicable: SharePoint Online -title: Remove-SPOSiteCollectionAppCatalogById -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Remove-SPOSiteCollectionAppCatalogById - -## SYNOPSIS - -Removes the site collection app catalog by the id of the site collection. - -## SYNTAX - -```powershell -Remove-SPOSiteCollectionAppCatalogById -SiteId <guid> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to remove the site collection app catalog by the id of the site collection. - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOSiteCollectionAppCatalogById -SiteId bdbd7458-8199-4e99-87ca-15fe9dc17a86 -``` - -This example removes the site collection app catalog from the site with the id 'bdbd7458-8199-4e99-87ca-15fe9dc17a86'. - -## PARAMETERS - -### -SiteId - -Guid of the site collection. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteDesign.md deleted file mode 100644 index a8307d1fae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteDesign.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spositedesign -applicable: SharePoint Online -title: Remove-SPOSiteDesign -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOSiteDesign - -## SYNOPSIS - -Removes a site design. It no longer appears in the UI for creating a new site. - -## SYNTAX - -```powershell - Remove-SPOSiteDesign - [-Identity] <SPOSiteDesignPipeBind> - [<CommonParameters>] -``` - -## DESCRIPTION - -Removes a site design. It no longer appears in the UI for creating a new site. - -## EXAMPLES - -### Example 1 - -This example shows how to remove a site design. - -```powershell -Remove-SPOSiteDesign 21209d88-38de-4844-9823-f1f600a1179a -``` - -## PARAMETERS - -### -Identity - -The ID of the site design to remove. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteDesignTask.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteDesignTask.md deleted file mode 100644 index 4f0e41a146..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteDesignTask.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: Microsoft.Online.SharePoint.PowerShell.dll-Help.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spositedesigntask -applicable: SharePoint Online -title: Remove-SPOSiteDesignTask -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOSiteDesignTask - -## SYNOPSIS - -Command to remove a scheduled site design script. - -## SYNTAX - -```powershell -Remove-SPOSiteDesignTask - -Identity <guid> - [<CommonParameters>] -``` - -## DESCRIPTION - -Removes a scheduled site design by providing the site design ID. If the execution of the associated site script has already started the execution will not be terminated. - -> [!NOTE] -> This command only removes a scheduled request. To check on the job status or to view details of the scheduled run, use the commands in the related section below. - -## EXAMPLES - -### Example 1 - -This example removes a previously scheduled site design. - -```powershell -Remove-SPOSiteDesignTask -Identity 501z8c32-4147-44d4-8607-26c2f67cae82 -``` - -## PARAMETERS - -### -Identity - -The ID of the site design to apply. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## RELATED LINKS - -[Get-SPOSiteDesignTask](Get-SPOSiteDesignTask.md) - -[Get-SPOSiteDesignRun](Get-SPOSiteDesignRun.md) - -[Get-SPOSiteDesignRunStatus](Get-SPOSiteDesignRunStatus.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteGroup.md deleted file mode 100644 index 22d052cd02..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteGroup.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spositegroup -applicable: SharePoint Online -title: Remove-SPOSiteGroup -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOSiteGroup - -## SYNOPSIS - -Removes a SharePoint Online group from a site collection. - -## SYNTAX - -```powershell -Remove-SPOSiteGroup -Identity <String> -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use the `Remove-SPOSiteGroup` cmdlet to remove a group from a site collection by specifying the name of the group in the Identity parameter. - -You must be a SharePoint Online global administrator and a site collection administrator to run the `Remove-SPOSiteGroup` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- - -```powershell -Remove-SPOSiteGroup -Site https://contoso.sharepoint.com/sites/marketing -Identity GroupToRemove -``` - -This example removes a group named GroupToRemove from the site collection <https://contoso.sharepoint.com/sites/marketing.> - -## PARAMETERS - -### -Identity - -Specifies the name of the group to remove. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the site collection to remove the group from. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOSiteGroup](Get-SPOSiteGroup.md) - -[New-SPOSiteGroup](New-SPOSiteGroup.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteScript.md deleted file mode 100644 index 6a8bd2c963..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteScript.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spositescript -applicable: SharePoint Online -title: Remove-SPOSiteScript -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOSiteScript - -## SYNOPSIS - -Removes a site script. - -## SYNTAX - -```powershell -Remove-SPOSiteScript [-Identity] <SPOSiteScriptPipeBind> [<CommonParameters>] -``` - -## EXAMPLES - -### Example 1 - -This example shows how to remove a site design. - -```powershell -Remove-SPOSiteScript 5ea28194-6fe7-4e2c-ba84-c409368278e2 -``` - -## DESCRIPTION - -Removes a site script. - -## PARAMETERS - -### -Identity - -The ID of the site script to remove. - -```yaml -Type: SPOSiteScriptPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteUserInvitations.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteUserInvitations.md deleted file mode 100644 index b824ec95a5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOSiteUserInvitations.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spositeuserinvitations -applicable: SharePoint Online -title: Remove-SPOSiteUserInvitations -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Remove-SPOSiteUserInvitations - -## SYNOPSIS - -. - -## SYNTAX - -```powershell -Remove-SPOSiteUserInvitations [-Site] <SpoSitePipeBind> [-EmailAddress] <string> [-CountOnly] [<CommonParameters>] -``` - -## DESCRIPTION - -. - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOSiteUserInvitations -Site https://contoso.sharepoint.com/sites/Research -EmailAddress "someone@contoso.com" -``` - -This example removes the user with the mail address "someone@contoso.com" from the site with the url <https://contoso.sharepoint.com/sites/Research.> - -## PARAMETERS - -### -Site - -Specifies the URL of the site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddress - -Email Address of the user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountOnly - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOStorageEntity.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOStorageEntity.md deleted file mode 100644 index d1cbfb1c74..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOStorageEntity.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spostorageentity -applicable: SharePoint Online -title: Remove-SPOStorageEntity -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Remove-SPOStorageEntity - -## SYNOPSIS - -Tenant properties allow tenant administrators to add properties in the app catalog that can be read by various SharePoint Framework components. Because tenant properties are stored in the tenant app catalog, you must provide the tenant app catalog site collection URL or the site collection app catalog URL in the following cmdlets. -This cmdLet is used to remove a value in the property bag. - -## SYNTAX - -```powershell -Remove-SPOStorageEntity [-Site] <SpoSitePipeBind> [-Key] <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to remove a value within the property bag. - -## EXAMPLES - -### Example 1 - -```powershell -Remove-SPOStorageEntity "https://tenant-name.sharepoint.com/sites/app-catalog" -Key "MyCustomValue" -``` - -This example removes the value of my custom value. - -## PARAMETERS - -### -Site - -URL to the tenant or site collection app catalog. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Key - -The key in the property bag that should be removed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantCdnOrigin.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantCdnOrigin.md deleted file mode 100644 index 7c24d72ff3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantCdnOrigin.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spotenantcdnorigin -applicable: SharePoint Online -title: Remove-SPOTenantCdnOrigin -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOTenantCdnOrigin - -## SYNOPSIS - -Removes a new origin from the Public or Private content delivery network (CDN). Requires Tenant administrator permissions. - -## SYNTAX - -```powershell -Remove-SPOTenantCdnOrigin -CdnType <SPOTenantCdnType> [-Confirm] -OriginUrl <String> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Removes a new origin from the Public or Private content delivery network (CDN). - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Remove-SPOTenantCdnOrigin -CdnType Public -OriginUrl sites/pubsite/siteassets/subfolder -``` - -The example removes a CDN from a tenant level. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Remove-SPOTenantCdnOrigin -CdnType Public -OriginScope Site -Site https://contoso.sharepoint.com/sites/pubsite -OriginUrl siteassets/subfolder -``` - -The example removes a CDN from a site level. - -## PARAMETERS - -### -CdnType - -Specifies the CDN type. The valid values are: Public or Private. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) -Aliases: -Accepted values: Public, Private -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OriginUrl - -Specifies a path to the doc library to be configured. It can be provided in two ways: relative path, or a mask. - -Relative-Relative path depends on the OriginScope. If the originScope is Tenant, a path must be a relative path under the tenant root. If the originScope is Site, a path must be a relative path under the given Site. The path must point to the valid Document Library or a folder with a document library. - -Any asset stored under the path provided (in the container itself or any of its subfolders) will be exposed via CDN - -Mask - Mask allows to configure a partial URL match. It must start with */, and must not include * anywhere else. I.e. an origin "*/masterpages" will expose all the assets under all the masterpages libraries, either under the tenant root (means, anywhere in the tenancy) or in the given site collection, depends on the OriginScope parameter. Equally, */masterpages/subfolder will enable items in "subfolder" and below. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantOrgRelation.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantOrgRelation.md deleted file mode 100644 index 24cfd935c8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantOrgRelation.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/Remove-SPOTenantOrgRelation -applicable: SharePoint Online -title: Remove-SPOTenantOrgRelation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- -# Remove-SPOTenantOrgRelation - -## SYNOPSIS - -{{ Fill in the Synopsis }} - -## SYNTAX - -```powershell -Remove-SPOTenantOrgRelation [-Scenario] <OrgRelationScenario> [-PartnerRole] <OrgRelationRole> [-PartnerCompanyId] <Guid> [-PartnerInstanceId <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION - -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 - -```powershell -PS C:\> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -PartnerCompanyId - -{{ Fill PartnerCompanyId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerInstanceId - -{{ Fill PartnerInstanceId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerRole - -{{ Fill PartnerRole Description }} - -```yaml -Type: OrgRelationRole -Parameter Sets: (All) -Aliases: -Accepted values: None, Source, Target - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scenario - -{{ Fill Scenario Description }} - -```yaml -Type: OrgRelationScenario -Parameter Sets: (All) -Aliases: -Accepted values: None, MnA - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantSyncClientRestriction.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantSyncClientRestriction.md deleted file mode 100644 index b9cdd2f072..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantSyncClientRestriction.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spotenantsyncclientrestriction -applicable: SharePoint Online -title: Remove-SPOTenantSyncClientRestriction -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOTenantSyncClientRestriction - -## SYNOPSIS - -Disables the feature for the tenancy. - -## SYNTAX - -```powershell -Remove-SPOTenantSyncClientRestriction [<CommonParameters>] -``` - -## DESCRIPTION - -You must be a SharePoint Online global administrator to run the cmdlet. - -Requires a valid `Connect-SPOService` context to identify the tenant. For information on how to connect to the tenant, see `Connect-SPOService`. - -The `Remove-SPOTenantSyncClientRestriction` cmdlet disables the feature for tenancy, but does not remove any present domain GUID entries from the safe sender recipient list. After the `Remove-SPOTenantSyncClientRestriction` cmdlet is run it can take up to 24 hours for change to take effect. This parameter will also remove any values set from the GrooveBlockOption parameter for syncing. - -The `Remove-SPOTenantSyncClientRestriction` cmdlet does not have any parameters. - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- - -```powershell -Remove-SPOTenantSyncClientRestriction -``` - -This example returns the value of False for the TenantRestrictionEnabled property. - -## 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTheme.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTheme.md deleted file mode 100644 index b30dc3bdef..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTheme.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spotheme -applicable: SharePoint Online -title: Remove-SPOTheme -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOTheme - -## SYNOPSIS - -Removes a theme from the theme gallery. - -## SYNTAX - -```powershell -Remove-SPOTheme [-Identity] <SpoThemePipeBind> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -The **Remove-SPOTheme** cmdlet removes a theme from your tenant store. - -## EXAMPLES - -### Example 1 - -This example removes the `"Custom Cyan"` theme that was used in the previous examples for the **Add-SPOTheme** and **Get-SPOTheme** cmdlets. - -```powershell -Remove-SPOTheme -Name "Custom Cyan" -``` - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -{{ Fill Identity Description }} - -```yaml -Type: SpoThemePipeBind -Parameter Sets: (All) -Aliases: Name - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### Microsoft.Online.SharePoint.PowerShell.SpoThemePipeBind - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUser.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUser.md deleted file mode 100644 index 59b117f855..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUser.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spouser -applicable: SharePoint Online -title: Remove-SPOUser -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOUser - -## SYNOPSIS - -Removes a user or a security group from a site collection or a group. - -## SYNTAX - -```powershell -Remove-SPOUser [-Group <String>] -LoginName <String> -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -You must be a SharePoint Online global administrator and a site collection administrator to run the `Remove-SPOUser` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- - -```powershell -Remove-SPOUser -Site https://contoso.sharepoint.com/sites/sc1 -LoginName joe.healy@contoso.com -Group "SC1 Owners" -``` - -This example removes a user who has the email address joe.healy@contoso.com from the group SC1 Owners in the site collection <https://contoso.sharepoint.com/sites/sc1.> - -## PARAMETERS - -### -Group - -Specifies the group to remove the user from. If not specified, the cmdlet removes the user from all groups. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoginName - -Specifies the user name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the site collection to remove the user from. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOUser](Get-SPOUser.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUserInfo.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUserInfo.md deleted file mode 100644 index 8faea921d0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUserInfo.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spouserinfo -applicable: SharePoint Online -title: Remove-SPOUserInfo -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOUserInfo - -## SYNOPSIS - -Removes user from user information list of specific site collection. - -## SYNTAX - -```powershell -Remove-SPOUserInfo -LoginName <String> -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Can be used to remove user from user information lists of the specific site collections. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Remove-SPOUserInfo -LoginName joe.healy@contoso.com -Site https://contoso.sharepoint.com/sites/sc1 -``` - -Example 1 removes a user who has the e-mail address joe.healy@contoso.com from the user information list of <https://contoso.sharepoint.com/sites/sc1> site collection. - -## PARAMETERS - -### -LoginName - -Specifies the login name of the user to removed from user information list. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the URL of the site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPOUserProfile](Remove-SPOUserProfile.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUserProfile.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUserProfile.md deleted file mode 100644 index 12002c296b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUserProfile.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spouserprofile -applicable: SharePoint Online -title: Remove-SPOUserProfile -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Remove-SPOUserProfile - -## SYNOPSIS - -Remove user profile from the tenant. - -## SYNTAX - -```powershell -Remove-SPOUserProfile -LoginName <String> [<CommonParameters>] -``` - -## DESCRIPTION - -Can be used to remove the SharePoint user profile from the tenant. - -> [!NOTE] -> The User must be first be deleted from AAD before the user profile can be deleted. You can use the Azure AD cmdlet Remove-AzureADUser for this action - -## EXAMPLES - -### ------------ Example 1 -------------------- - -```powershell -Remove-SPOUserProfile -LoginName joe.healy@contoso.com -``` - -Example 1 removes a user who has the e-mail address joe.healy@contoso.com from the SharePoint Online User Profiles of the particular tenant. - -## PARAMETERS - -### -LoginName - -Specifies the login name of the user which user profile is deleted. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPOUserInfo](Remove-SPOUserInfo.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Repair-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Repair-SPOSite.md deleted file mode 100644 index 83cacdd057..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Repair-SPOSite.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/repair-sposite -applicable: SharePoint Online -title: Repair-SPOSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Repair-SPOSite - -## SYNOPSIS - -Checks and repairs the site collection and its contents. - -## SYNTAX - -```powershell -Repair-SPOSite [-Confirm] -Identity <SpoSitePipeBind> [-RuleId <Guid>] [-RunAlways] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -The `Repair-SPOSite` cmdlet runs one or all site collection health checks on the site collection and its contents. -This cmdlet will make changes if issues are found and automatically repairable. - -The cmdlet reports the health check rules with a summary of the results. -The rules might not support automatic repair. -Tests without repair mode can be initiated by running the `Test-SPOSite` cmdlet. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Repair-SPOSite https://contoso.sharepoint.com/sites/marketing -``` - -This example runs all the site collection health checks in repair mode on the <https://contoso.sharepoint.com/sites/marketing> site collection. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Repair-SPOSite https://contoso.sharepoint.com/sites/marketing -RuleID "ee967197-ccbe-4c00-88e4-e6fab81145e1" -``` - -This example runs the Missing Galleries Check rule in repair mode on the <https://contoso.sharepoint.com/sites/marketing> site collection. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the SharePoint Online site collection on which to run the repairs. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RuleId - -Specifies a health check rule to run. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RunAlways - -Displays a message that explains the effect of the command instead of executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Test-SPOSite](Test-SPOSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md deleted file mode 100644 index dd1fa3e21f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/request-spopersonalsite -applicable: SharePoint Online -title: Request-SPOPersonalSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Request-SPOPersonalSite - -## SYNOPSIS - -Requests that one or more users be enqueued for a Personal Site to be created. - -## SYNTAX - -```powershell -Request-SPOPersonalSite [-NoWait] -UserEmails <String[]> [<CommonParameters>] -``` - -## DESCRIPTION - -The `Request-SPOPersonalSite` cmdlet requests that the users specified be enqueued so that a Personal Site be created for each. The actual Personal site is created by a Timer Job later. - -> [!NOTE] -> • You must specify a string array of user logins that contains one or more valid user email (logins) and cannot contain any empty fields. The command will stop if it encounters any empty strings in the array. A maximum of 200 users can be specified. <br/><br/>• The actor executing this cmdlet must be at least assigned the SharePoint Online administrator role and have been assigned a SharePoint Online license to be able to provision the OneDrive for Business sites. The users who the sites will be provisioned for must also have a SharePoint license assigned. <br/><br/>• This cmdlet is NOT OneDrive Multi-Geo aware. If you need to request Personal Sites for Multi-Geo enabled tenants, you must run this cmdlet for users in the region their data is to be hosted in. To retrieve users with a specific PDL, use the following sample: `Get-MSOLUser | Where {$_.PreferredDataLocation -eq "EUR"}`. - -## EXAMPLES - -### ----------------------EXAMPLE 1----------------------- - -```powershell -$emails = "user1@contoso.com", "user2@contoso.com" -Request-SPOPersonalSite -UserEmails $emails -``` - -This example requests that two users to be enqueued for the creation of a Personal Site. - -### ----------------------EXAMPLE 2----------------------- - -```powershell -Request-SPOPersonalSite -UserEmails $emails -``` - -This example requests that many users to be queued for the creation of a Personal Site. The users are previously defined using the variable $emails. - -## PARAMETERS - -### -NoWait - -Continues without the status being polled. Polling the action can slow it's progress if lots of user emails are specified. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserEmails - -Specifies one or more user logins to be enqueued for the creation of a Personal Site. The Personal site is created by a Timer Job later. You can specify between 1 and 200 users. -> [!NOTE] -> If you are Pre-Provisioning OneDrive for Many Users, it might take up to 24 hours for the OneDrive locations to be created. If a user's OneDrive isn't ready after 24 hours, please contact Support. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String[] - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Request-SPOUpgradeEvaluationSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Request-SPOUpgradeEvaluationSite.md deleted file mode 100644 index 2fdcec85a8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Request-SPOUpgradeEvaluationSite.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/request-spoupgradeevaluationsite -applicable: SharePoint Online -title: Request-SPOUpgradeEvaluationSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Request-SPOUpgradeEvaluationSite - -## SYNOPSIS - -Requests to create a copy of an existing site collection for the purposes of validating the effects of upgrade without affecting the original site. - -## SYNTAX - -```powershell -Request-SPOUpgradeEvaluationSite [-Confirm] -Identity <SpoSitePipeBind> [-NoEmail] [-NoUpgrade] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -The `Request-SPOUpgradeEvaluationSite` cmdlet lets the SharePoint Online global administrator request a copy of an existing site collection for the purposes of validating the effects of upgrade without affecting the original site. - -A request for an upgrade evaluation site is not automatically processed. -Instead, it is scheduled to occur on the background when it causes the least effect on the service. - -You must be a SharePoint Online global administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Request-SPOUpgradeEvaluationSite https://contoso.sharepoint.com/sites/marketing -``` - -Example 1 requests a site upgrade evaluation for the marketing site <https://contoso.sharepoint.com/sites/marketing> using the default options of sending an email message and automatically trying to upgrade the evaluation site. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Request-SPOUpgradeEvaluationSite https://contoso.sharepoint.com/sites/marketing -NoEmail $true -NoUpgrade $true -``` - -This example requests a site upgrade evaluation for the marketing site <https://contoso.sharepoint.com/sites/marketing.> It specifies to not send email messages and not automatically try upgrade of the evaluation site. By using the cmdlet in this way, a SharePoint Online global administrator can make changes to the upgrade evaluation site before starting the actual upgrade. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the SharePoint Online site collection for which you want to request a copy for the new Upgrade or Evaluation site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NoEmail - -Specifies that the system not send the requester and site collection administrators an email message at the end of the upgrade evaluation site creation process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoUpgrade - -Specifies that the system not perform an upgrade as part of the evaluation site creation process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Upgrade-SPOSite](Upgrade-SPOSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Restore-SPODataEncryptionPolicy.md b/sharepoint/sharepoint-ps/sharepoint-online/Restore-SPODataEncryptionPolicy.md deleted file mode 100644 index a74f3acc86..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Restore-SPODataEncryptionPolicy.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/restore-spodataencryptionpolicy -applicable: SharePoint Online -title: Restore-SPODataEncryptionPolicy -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Restore-SPODataEncryptionPolicy - -## SYNOPSIS - -. - -## SYNTAX - -```powershell -Restore-SPODataEncryptionPolicy [-Identity] <SpoSitePipeBind> -PrimaryKeyVaultName <string> -PrimaryKeyName <string> -PrimaryKeyVersion <guid> -SecondaryKeyVaultName <string> -SecondaryKeyName <string> -SecondaryKeyVersion <guid> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to . - -## EXAMPLES - -### Example 1 - -```powershell - -``` - -This example. - -## PARAMETERS - -### -Identity - -URL of the site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimaryKeyVaultName - -. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimaryKeyName - -. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrimaryKeyVersion - -. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryKeyVaultName - -. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryKeyName - -. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryKeyVersion - -. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Restore-SPODeletedSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Restore-SPODeletedSite.md deleted file mode 100644 index 416cff7133..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Restore-SPODeletedSite.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/restore-spodeletedsite -applicable: SharePoint Online -title: Restore-SPODeletedSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Restore-SPODeletedSite - -## SYNOPSIS - -Restores a SharePoint Online deleted site collection from the Recycle Bin. - -## SYNTAX - -```powershell -Restore-SPODeletedSite -Identity <SpoSitePipeBind> [-NoWait] [<CommonParameters>] -``` - -## DESCRIPTION - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- - -```powershell -Restore-SPODeletedSite -Identity https://contoso.sharepoint.com/sites/arecycledsite -``` - -This example restores a SharePoint Online deleted site collection named "<https://contoso.sharepoint.com/sites/arecycledsite"> from the Recycle Bin. - -## PARAMETERS - -### -Identity - -Specifies the URL of the site collection to restore. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NoWait - -Specifies to continue executing script immediately. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPODeletedSite](Get-SPODeletedSite.md) - -[Remove-SPODeletedSite](Remove-SPODeletedSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOHubSiteRights.md b/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOHubSiteRights.md deleted file mode 100644 index f22f13c2ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOHubSiteRights.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/revoke-spohubsiterights -applicable: SharePoint Online -title: Revoke-SPOHubSiteRights -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Revoke-SPOHubSiteRights - -## SYNOPSIS - -Revokes rights for specified principals to a hub. - -## SYNTAX - -```powershell -Revoke-SPOHubSiteRights [-Identity] <SpoHubSitePipeBind> -Principals <string[]> [<CommonParameters>] -``` - -## DESCRIPTION - -Revokes rights for specified principals to the given hub site. The specified principals will no longer be able to associate sites with the hub. To find which principals have access to a hub site, use the [Get-SPOHubSite](Get-SPOHubSite.md) cmdlet. - -> [!NOTE] -> If the hub site doesn't exist, this cmdlet returns a "File not found" error. - -## EXAMPLES - -### Example 1 - -```powershell -Revoke-SPOHubSiteRights https://contoso.sharepoint.com/sites/Marketing ` --Principals "nestorw@contoso.onmicrosoft.com" -``` - -This example shows how to revoke rights so that Nestor can no longer join sites to the Marketing hub site. - -## PARAMETERS - -### -Identity - -URL of the hub site. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: HubSite -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Principals - -One or more principles to revoke the permissions for. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOSiteDesignRights.md b/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOSiteDesignRights.md deleted file mode 100644 index fcf4b25b4b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOSiteDesignRights.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/revoke-spositedesignrights -applicable: SharePoint Online -title: Revoke-SPOSiteDesignRights -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Revoke-SPOSiteDesignRights - -## SYNOPSIS - -Revokes rights for specified principals from a site design. - -## SYNTAX - -```powershell -Revoke-SPOSiteDesignRights [-Identity] <SPOSiteDesignPipeBind> -Principals <string[]> [<CommonParameters>] -``` - -## DESCRIPTION - -Revokes rights for specified principals from a site design. - -## EXAMPLES - -### Example 1 - -This example shows how to revoke rights to a site design for Nestor. - -```powershell -Revoke-SPOSiteDesignRights 44252d09-62c4-4913-9eb0-a2a8b8d7f863 ` - -Principals "nestorw@contoso.onmicrosoft.com" -``` - -## PARAMETERS - -### -Identity - -The ID of the site design from which to revoke rights. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Principals - -One or more principals to revoke rights on the specified site design. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOTenantServicePrincipalPermission.md b/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOTenantServicePrincipalPermission.md deleted file mode 100644 index 53599e5d41..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOTenantServicePrincipalPermission.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/revoke-spotenantserviceprincipalpermission -applicable: SharePoint Online -title: Revoke-SPOTenantServicePrincipalPermission -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- -# Revoke-SPOTenantServicePrincipalPermission - -## SYNOPSIS - -Revokes a permission that was previously granted to the "SharePoint Online Client" service principal - -## SYNTAX - -### Default - -```powershell -Revoke-SPOTenantServicePrincipalPermission -ObjectId <String> -``` - -## DESCRIPTION - -Revokes a permission that was previously granted to the "SharePoint Online Client" service principal. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ - -```powershell -$grants = Get-SPOTenantServicePrincipalPermissionGrants -$grantToRemove = $grants | ? { $_.Resource -eq 'Office 365 SharePoint Online' -and $_.Scope -eq 'MyFiles.Read' } | Select-Object -First 1 - -if ($grantToRemove -ne $null) -{ - Revoke-SPOTenantServicePrincipalPermission -ObjectId $grantToRemove.ObjectId -} -``` - -Revokes the permission associated with the 'Office 365 SharePoint Online' resource and with scope claim 'MyFiles.Read'. -If there is no permission with those properties, then no revoke action will be taken. - -## PARAMETERS - -### -ObjectId - -The Object ID of the permission grant to revoke - -```yaml -Type: string - -Required: True -Position: Named -Accept pipeline input: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOUserSession.md b/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOUserSession.md deleted file mode 100644 index c46ea6f89b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOUserSession.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/revoke-spousersession -applicable: SharePoint Online -title: Revoke-SPOUserSession -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Revoke-SPOUserSession - -## SYNOPSIS - -Provides IT administrators the ability to invalidate a particular users' O365 sessions across all their devices. - -## SYNTAX - -```powershell -Revoke-SPOUserSession [-User] <String> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -You must be a SharePoint Online global administrator to run the cmdlet. - -Requires a valid `Connect-SPOService` context to identify the tenant. For information about how to connect to the tenant, see `Connect-SPOService`. - -When the cmdlet is ran the following will occur: - -User will be signed out of browser, desktop and mobile applications accessing Office 365 resources across all devices. - -Will not be applicable for guest users. - -Possible results for this cmdlet are: - -Result | Reason ---- | --- -Warning : We couldn't find the user@contoso.com. Check for typos and try again. | Invalid input for -User parameter. -We successfully signed out <user> from all devices. | Successful instantaneous revocation. -It can take up to an hour to sign out <user> from all devices. | Successful non-instantaneous revocation. -Sorry, something went wrong and we couldn't sign out <user> from any device. | The cmdlet did not successfully execute. -The cmdlet will be available in the future, but it isn't ready for use in your organization yet. | The cmdlet has been disabled for the tenant. - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- - -```powershell -Revoke-SPOUserSession -User user1@contoso.com -``` - -This example signs out user1 in the contoso tenancy from all devices. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User - -Specifies a user name. For example, user1@contoso.com - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBrowserIdleSignOut.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBrowserIdleSignOut.md deleted file mode 100644 index 849064f2b1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBrowserIdleSignOut.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spobrowseridlesignout -applicable: SharePoint Online -title: Set-SPOBrowserIdleSignOut -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOBrowserIdleSignOut - -## SYNOPSIS - -. - -## SYNTAX - -```powershell -Set-SPOBrowserIdleSignOut [-Enabled] <Boolean> [[-WarnAfter] <TimeSpan>] [[-SignOutAfter] <TimeSpan>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to set the current configuration values for Idle session sign-out, the time at which users are warned and subsequently signed out of Office 365 after a period of browser inactivity in SharePoint and OneDrive - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOBrowserIdleSignOut -Enabled:$true -WarnAfter "0.00:45:00" -SignOutAfter "0.01:00:00" -``` - -This example enables the browser idle sign-out policy, sets a warning at 45 minutes and signs out users after a period of 60 minutes of browser inactivity. - -### Example 2 - -```powershell -Set-SPOBrowserIdleSignOut -Enabled:$true -WarnAfter (New-TimeSpan -Minutes 45) -SignOutAfter (New-TimeSpan -Hours 1) -``` - -This example enables the browser idle sign-out policy, sets a warning at 45 minutes and signs out users after a period of 60 minutes of browser inactivity. This example leverages the use of New-TimeSpan cmdlet to create the required timespan values. - -## PARAMETERS - -### -Enabled - -Enables the browser idle sign-out policy - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignOutAfter - -Specifies a time interval. -This parameter is used to specify a time value for **Get-SPOBrowserIdleSignOut** parameters such as *SignOutAfter*. -Specify the time interval in the following format: - -\[-\]D.H:M:S.F - -where: - -- D = Days (0 to 10675199) -- H = Hours (0 to 23) -- M = Minutes (0 to 59) -- S = Seconds (0 to 59) -- F = Fractions of a second (0 to 9999999) - -```yaml -Type: TimeSpan -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarnAfter - -Specifies a time interval. -This parameter is used to specify a time value for **Get-SPOBrowserIdleSignOut** parameters such as *WarnAfter*. -Specify the time interval in the following format: - -\[-\]D.H:M:S.F - -where: - -- D = Days (0 to 10675199) -- H = Hours (0 to 23) -- M = Minutes (0 to 59) -- S = Seconds (0 to 59) -- F = Fractions of a second (0 to 9999999) - -```yaml -Type: TimeSpan -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBuiltInDesignPackageVisibility.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBuiltInDesignPackageVisibility.md deleted file mode 100644 index f245a57fac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBuiltInDesignPackageVisibility.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spobuiltindesignpackagevisibility -applicable: SharePoint Online -title: Set-SPOBuiltInDesignPackageVisibility -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOBuiltInDesignPackageVisibility - -## SYNOPSIS - -Sets the visibility of the available built-in Design Packages at moment of site creation. - -## SYNTAX - -```powershell -Set-SPOBuiltInDesignPackageVisibility [-IsVisible] <Boolean> [-DesignPackage] <DesignPackageType> [<CommonParameters>] -``` - -## DESCRIPTION - -Sets the visibility of the available built-in Design Packages. For more information, see [Moving from Publishing sites to Communication sites](https://docs.microsoft.com/sharepoint/publishing-sites-classic-to-modern-experience) - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOBuiltInDesignPackageVisibility -DesignPackage Showcase -IsVisible:$false -``` - -This example sets the visibility of Showcase design package to false. - -## PARAMETERS - -### -DesignPackage - -Name of the design package, available names are -- Topic -- Showcase -- Blank -- TeamSite - -```yaml -Type: DesignPackageType -Parameter Sets: (All) -Aliases: -Accepted values: None, Topic, Showcase, Blank, TeamSite - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsVisible - -Determines if the design package is visible - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPODataConnectionSetting.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPODataConnectionSetting.md deleted file mode 100644 index e125d2bbcd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPODataConnectionSetting.md +++ /dev/null @@ -1,296 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spodataconnectionsetting -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Set-SPODataConnectionSetting -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPODataConnectionSetting - -## SYNOPSIS - -Sets or updates global properties for a Microsoft Business Connectivity Services connection. - -## SYNTAX - -### Identity - -```powershell -Set-SPODataConnectionSetting [-Identity] <ODataConnectionSettings> -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationMode <ODataAuthenticationMode>] [-Confirm] - [-ExtensionProvider <String>] [-SecureStoreTargetApplicationId <String>] [-ServiceAddressURL <Uri>] [-WhatIf] - [<CommonParameters>] -``` - -### Name - -```powershell -Set-SPODataConnectionSetting -ServiceContext <SPServiceContextPipeBind> -Name <String> - [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationMode <ODataAuthenticationMode>] [-Confirm] - [-ExtensionProvider <String>] [-SecureStoreTargetApplicationId <String>] [-ServiceAddressURL <Uri>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (<https://go.microsoft.com/fwlink/?LinkID=187810).> - -Use the `Set-SPODataConnectionSetting` cmdlet to update the properties of an existing connection for a specific Business Connectivity Services service application. - -This cmdlet applies to an on-premises environment only. -You cannot use this command in the SharePoint Online Management Shell. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251831> (<https://go.microsoft.com/fwlink/p/?LinkId=251831).> - -## EXAMPLES - -### -------------EXAMPLE 1----------- - -```powershell -Set-SPODataConnectionSetting -Name "ContosoServiceApp" -ServiceContext "http://contoso/" -AuthenticationMode "PassThrough" -``` - -This example updates the properties of Business Connectivity Services connection named ContosoServiceApp. - -### -------------EXAMPLE 2----------- - -```powershell -$ConnectionVariable = Get-SPODataConnectionSetting -ServiceContext http://contoso -Name "ContosoServiceApp" - -Set-SPODataConnectionSetting -Identity $ConnectionVariable -AuthenticationMode "PassThrough" -``` - -This example updates the properties of the Business Connectivity Services service connection named ContosoServiceApp. - -### -------------EXAMPLE 3----------- - -```powershell -Set-SPODataConnectionSetting -Name "ContosoServiceApp" -ServiceContext "http://contoso/" -AuthenticationMode "PassThrough" -ExtensionProvider "" -``` - -This example updates the properties of Business Connectivity Services connection named ContosoServiceApp, the authentication mode has been changed and extension provider value has been cleared. - -## PARAMETERS - -### -Identity - -Specifies the OData Connection Settings object. - -```yaml -Type: ODataConnectionSettings -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceContext - -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object: An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the name of the existing Business Connectivity Services connection. - -```yaml -Type: String -Parameter Sets: Name -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationMode - -Specifies the type of authentication mode that is required for the Business Connectivity Services connection. - -The value for the authentication mode is any one of the following options: - ---PassThrough ---RevertToSelf ---Credentials ---WindowsCredentials ---DigestCredentials ---ClientCertificate ---Anonymous - -```yaml -Type: ODataAuthenticationMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtensionProvider - -{{Fill ExtensionProvider Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureStoreTargetApplicationId - -Specifies the Secure Store Target Application ID. -Works in conjunction with the AuthenticationMode parameter. - -The value for the SecureStoreTargetApplicationId parameter is any one of the following options: - ---Credentials ---WindowsCredentials ---DigestCredentials ---ClientCertificate - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceAddressURL - -Specifies the URL for the OData service. -The URL does not have to be Internet facing. -This is the final destination from which data is retrieved. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPODataConnectionSetting](Get-SPODataConnectionSetting.md) - -[New-SPODataConnectionSetting](New-SPODataConnectionSetting.md) - -[Remove-SPODataConnectionSetting](Remove-SPODataConnectionSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPODataConnectionSettingMetadata.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPODataConnectionSettingMetadata.md deleted file mode 100644 index 81bc8f5ef8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPODataConnectionSettingMetadata.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spodataconnectionsettingmetadata -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Set-SPODataConnectionSettingMetadata -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPODataConnectionSettingMetadata - -## SYNOPSIS - -Updates properties for the metadata of a Business Connectivity Services connection. - -## SYNTAX - -### Identity - -```powershell -Set-SPODataConnectionSettingMetadata [-Identity] <ODataConnectionSettings> -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationMode <ODataAuthenticationMode>] [-Confirm] [-SecureStoreTargetApplicationId <String>] [-ServiceAddressMetadataURL <Uri>] [-WhatIf] [<CommonParameters>] -``` - -### Name - -```powershell -Set-SPODataConnectionSettingMetadata -ServiceContext <SPServiceContextPipeBind> -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationMode <ODataAuthenticationMode>] [-Confirm] [-SecureStoreTargetApplicationId <String>] [-ServiceAddressMetadataURL <Uri>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (<https://go.microsoft.com/fwlink/?LinkID=187810).> - -Use the `Set-SPODataConnectionSettingMetaData` cmdlet to update properties for a Business Connectivity Services connection for a Business Connectivity Services service application in the farm. - -This cmdlet applies to an on-premises environment only. -You cannot use this command in the SharePoint Online Management Shell. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251831> (<https://go.microsoft.com/fwlink/p/?LinkId=251831).> - -## EXAMPLES - -### --------------EXAMPLE 1------------- - -```powershell -Set-SPODataConnectionSettingMetadata -Name "ContosoServiceApp" -ServiceContext "http://contoso/" -AuthenticationMode "PassThrough" -``` - -This example updates the authentication mode of the metadata of Business Connectivity Services connection named ContosoServiceApp. - -### --------------EXAMPLE 2------------- - -```powershell -$ConnectionVariable = Get-SPODataConnectionSettingMetadata -ServiceContext http://contoso -Name "ContosoServiceApp" - -Set-SPODataConnectionSettingMetadata -Identity $ConnectionVariable -AuthenticationMode "PassThrough" -``` - -This example updates the Metadata properties of the Business Connectivity Services connection named ContosoServiceApp. - -## PARAMETERS - -### -Identity - -Specifies the OData Connection Settings object. - -```yaml -Type: ODataConnectionSettings -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceContext - -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or an SPSite object. -An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the name of the existing Business Connectivity Services connection. - -```yaml -Type: String -Parameter Sets: Name -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationMode - -Specifies the type of authentication mode that the Business Connectivity Services connection requires. - -The value for the authentication mode is any one of the following options: - ---PassThrough ---RevertToSelf ---Credentials ---WindowsCredentials ---DigestCredentials ---ClientCertificate ---Anonymous - -```yaml -Type: ODataAuthenticationMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureStoreTargetApplicationId - -Specifies the Secure Store Target Application ID. -Works in conjunction with the AuthenticationMode parameter. - -The value for the SecureStoreTargetApplicationId parameter is any one of the following options: - ---Credentials ---WindowsCredentials ---DigestCredentials ---ClientCertificate - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceAddressMetadataURL - -Specifies the metadata URL for the OData service. -This URL does not have to be Internet facing. -If a value is not specified for a connection, a default value is used. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPODataConnectionSettingMetaData](Get-SPODataConnectionSettingMetaData.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOGeoStorageQuota.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOGeoStorageQuota.md deleted file mode 100644 index 4a3533e0b6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOGeoStorageQuota.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spogeostoragequota -applicable: SharePoint Online -title: Set-SPOGeoStorageQuota -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOGeoStorageQuota - -## SYNOPSIS - -This Cmdlet sets the Storage quota on a multi-geo tenant. - -## SYNTAX - -```powershell -Set-SPOGeoStorageQuota -GeoLocation <String> -StorageQuotaMB <Int64> [<CommonParameters>] -``` - -## DESCRIPTION - -This Cmdlet sets the storage quota, in megabytes, on a particular geo-location. Additionally, it requires a connection to a multi-geo tenant to run correctly. You must be a SharePoint Online global Administrator. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Set-SPOGeoStorageQuota -GeoLocation EASTUS -StorageQuotaMB 512 -``` - -Sets the SharePoint Online Storage Quota on the EAST US location to 512 MB. - -### EXAMPLE 2 - -```powershell -Set-SPOGeoStorageQuota -GeoLocation NORTHCENTRALUS -StorageQuotaMB 1024 -``` - -Sets the SharePoint Online Storage Quota on the **NORTH CENTRAL US** location to 1 TeraBytes (1Tb). - -## PARAMETERS - -### -GeoLocation - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StorageQuotaMB - -PARAMVALUE: Int64 - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOGeoStorageQuota](Get-SPOGeoStorageQuota.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHideDefaultThemes.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHideDefaultThemes.md deleted file mode 100644 index 3554682220..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHideDefaultThemes.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spohidedefaultthemes -applicable: SharePoint Online -title: Set-SPOHideDefaultThemes -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOHideDefaultThemes - -## SYNOPSIS - -Specifies whether the default themes should be available. - -## SYNTAX - -```powershell -Set-SPOHideDefaultThemes [-HideDefaultThemes] <Boolean> [<CommonParameters>] -``` - -## DESCRIPTION - -The **Set-SPOHideDefaultThemes** cmdlet is used to specify whether the default themes that come with SharePoint should be included in the theme picker list. For example, you might want to create custom themes for your sites and then remove the default themes to ensure that all pages use your custom themes. - -After creating the `"Custom Cyan"` theme, hiding the default themes leaves only the one custom theme in the themes list under **Change the look**. - -Specify the setting as either `$true` to hide the default themes, or `$false` (the default setting) to allow use of the default themes. - -> [!NOTE] -> This cmdlet was named **Set-HideDefaultThemes** until the December 2017 release of the SPO Management Shell. We recommend that you use the latest version of the PowerShell cmdlets. -> [!TIP] -> Allows you to hide or show **ALL** default themes, no any particular ones. -> [!NOTE] -> This cmdlet hides the default themes on **Modern Sites**. You cannot hide the default themes on Classic Sites. - -## EXAMPLES - -### Example 1 - -In this example, the cmdlet hides the default themes. - -```powershell -Set-SPOHideDefaultThemes $true -``` - -### Example 2 - -In this example, the cmdlet restores the default themes to the theme picker list. - -```powershell -Set-SPOHideDefaultThemes $false -``` - -## PARAMETERS - -### -HideDefaultThemes - -{{ Fill HideDefaultThemes Description }} - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOHideDefaultThemes](Get-SPOHideDefaultThemes.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHomeSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHomeSite.md deleted file mode 100644 index 73e71e878f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHomeSite.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spohomesite -applicable: SharePoint Online -title: Set-SPOHomeSite -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Set-SPOHomeSite - -## SYNOPSIS - -Sets a SharePoint Site as a Home Site. - -## SYNTAX - -```powershell -Set-SPOHomeSite [-HomeSiteUrl] <String> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to set a SharePoint Site as a Home Site. A home site is a communication site that you create and set as the top landing page for all users in your intranet. For more information, see [Set up a home site for your organization](https://docs.microsoft.com/SharePoint/home-site) - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOHomeSite -HomeSiteUrl "https://contoso.sharepoint.com/sites/homesite" -``` - -This example set the site collection at *<https://contoso.sharepoint.com/sites/homesite>* as SharePoint Online Home Site. - -## PARAMETERS - -### -HomeSiteUrl - -The Url of the site collection to be the home site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHubSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHubSite.md deleted file mode 100644 index a7e267ec8f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHubSite.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spohubsite -applicable: SharePoint Online -title: Set-SPOHubSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOHubSite - -## SYNOPSIS - -Sets the hub site information such as name, logo, and description. - -## SYNTAX - -```powershell -Set-SPOHubSite [-Identity] <SpoHubSitePipeBind> [-Title <string>] [-LogoUrl <string>] [-Description <string>] [-SiteDesignId <guid>] [-RequiresJoinApproval <bool>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to set properties such as name, logo, and description. These properties appear for the hub in the SharePoint user interface. - -If the hub site doesn't exist, this cmdlet returns a "File not found" error. - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOHubSite https://contoso.sharepoint.com/sites/Marketing ` --Title "Marketing Hub" ` --LogoUrl https://contoso.sharepoint.com/sites/Marketing/SiteAssets/hublogo.png ` --Description "Hub for the Marketing division" -``` - -This example updates the name of the hub displayed in the SharePoint user interface. It also updates the logo used in the hub navigation, and specifies an optional description for the hub. - -## PARAMETERS - -### -Identity - -URL of the hub site. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: HubSite -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title - -The display name of the hub. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogoUrl - -The URL of a logo to use in the hub navigation. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -A description of the hub site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteDesignId - -Site Design ID, for example db752673-18fd-44db-865a-aa3e0b28698e - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiresJoinApproval - -Determines if joining a Hub site requires approval. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMigrationPackageAzureSource.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMigrationPackageAzureSource.md deleted file mode 100644 index 149fa41e24..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMigrationPackageAzureSource.md +++ /dev/null @@ -1,337 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spomigrationpackageazuresource -applicable: SharePoint Online -title: Set-SPOMigrationPackageAzureSource -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOMigrationPackageAzureSource - -## SYNOPSIS - -Cmdlet to create Azure containers, upload migration package files into the appropriate containers and snapshot the uploaded content. - -## SYNTAX - -### ImplicitSourceExplicitAzure - -```powershell -Set-SPOMigrationPackageAzureSource -AccountKey <String> -AccountName <String> [-AzureQueueName <String>] - [-EncryptionMetaInfo <MigrationFileEncryptionInfo[]>] [-EncryptionParameters <EncryptionParameters>] - [-FileContainerName <String>] -MigrationSourceLocations <MigrationPackageLocation> [-NoLogFile] - [-NoSnapshotCreation] [-NoUpload] [-Overwrite] [-PackageContainerName <String>] [<CommonParameters>] -``` - -### ExplicitSourceExplicitAzure - -```powershell -Set-SPOMigrationPackageAzureSource -AccountKey <String> -AccountName <String> [-AzureQueueName <String>] - [-EncryptionMetaInfo <MigrationFileEncryptionInfo[]>] [-EncryptionParameters <EncryptionParameters>] - [-FileContainerName <String>] [-NoLogFile] [-NoSnapshotCreation] [-NoUpload] [-Overwrite] - [-PackageContainerName <String>] -SourceFilesPath <String> -SourcePackagePath <String> [<CommonParameters>] -``` - -### ImplicitSourceImplicitAzure - -```powershell -Set-SPOMigrationPackageAzureSource [-EncryptionMetaInfo <MigrationFileEncryptionInfo[]>] - [-EncryptionParameters <EncryptionParameters>] - -MigrationPackageAzureLocations <MigrationPackageAzureLocations> - -MigrationSourceLocations <MigrationPackageLocation> [-NoLogFile] [-NoSnapshotCreation] [-NoUpload] - [-Overwrite] [<CommonParameters>] -``` - -### ExplicitSourceImplicitAzure - -```powershell -Set-SPOMigrationPackageAzureSource [-EncryptionMetaInfo <MigrationFileEncryptionInfo[]>] - [-EncryptionParameters <EncryptionParameters>] - -MigrationPackageAzureLocations <MigrationPackageAzureLocations> [-NoLogFile] [-NoSnapshotCreation] - [-NoUpload] [-Overwrite] -SourceFilesPath <String> -SourcePackagePath <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets. - -This cmdlet returns a Microsoft.Online.SharePoint.Migration. MigrationPackageAzureLocations object, which can be used as a source for this cmdlet or, more commonly, as a source for the `Submit-SPOMigrationJob` cmdlet. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -$azurelocations = Set-SPOMigrationPackageAzureSource -SourcePath \\fileserver\share\folder1 -OutputPackagePath d:\MigrationPackages\Folder1_TgtPkg -FileContainerUri migration-files -PackageContainerUri migration-package -AccountName migrationstore -AccountKey "nmcXQ+1NctB7BlRVm+8+qWUn6GUFIH7E5ZQPThcjg8SfFWTJ34HthyOEoROwxHYIajpOYxYDt7qUwSEBQlLWoA==" -``` - -This example creates migration package containers in Azure storage using the supplied account credentials, uploads the package files into them, snapshots the files and lastly returns the connection strings to a PowerShell variable. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Set-SPOMigrationPackageAzureSource -SourcePath \\fileserver\share\folder1 -OutputPackagePath d:\MigrationPackages\Folder1_TgtPkg -MigrationPackageAzureLocations $azurelocations -AccountName migrationstore -AccountKey "nmcXQ+1NctB7BlRVm+8+qWUn6GUFIH7E5ZQPThcjg8SfFWTJ34HthyOEoROwxHYIajpOYxYDt7qUwSEBQlLWoA==" -NoUpload -``` - -This example uses existing migration package containers in Azure storage to snapshot previously uploaded files and then returns the connection strings to a PowerShell variable. - -## PARAMETERS - -### -AccountKey - -The account key for the Azure Storage account. - -```yaml -Type: String -Parameter Sets: ImplicitSourceExplicitAzure, ExplicitSourceExplicitAzure -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AccountName - -The account name for the Azure Storage account. - -```yaml -Type: String -Parameter Sets: ImplicitSourceExplicitAzure, ExplicitSourceExplicitAzure -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AzureQueueName - -An optional name of the Azure Storage Reporting Queue where import operations lists events during import. This value must be in lower case and conform to Azure's queue naming rules. - -```yaml -Type: String -Parameter Sets: ImplicitSourceExplicitAzure, ExplicitSourceExplicitAzure -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptionMetaInfo - -PARAMVALUE: MigrationFileEncryptionInfo[] - -```yaml -Type: MigrationFileEncryptionInfo[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptionParameters - -PARAMVALUE: EncryptionParameters - -```yaml -Type: EncryptionParameters -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileContainerName - -The optional name of the Azure Blob Storage container that will be created if it does not currently exist. It will hold the uploaded package content files. The value must be in lower case and conform to Azure's container naming rules. If this not supplied a name will be generated using the format <GUID>-files. - -```yaml -Type: String -Parameter Sets: ImplicitSourceExplicitAzure, ExplicitSourceExplicitAzure -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MigrationPackageAzureLocations - -A set of fully qualified URLs and SAS tokens representing the Azure Blob Storage containers that hold the package content and metadata files and an optional Azure Storage Reporting Queue. This object is returned during successful processing of the `Set-SPOMigrationPackageAzureSource` - -```yaml -Type: MigrationPackageAzureLocations -Parameter Sets: ImplicitSourceImplicitAzure, ExplicitSourceImplicitAzure -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MigrationSourceLocations - -PARAMVALUE: MigrationPackageLocation - -```yaml -Type: MigrationPackageLocation -Parameter Sets: ImplicitSourceExplicitAzure, ImplicitSourceImplicitAzure -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile - -Indicates to not create a log file. The default is to create a new CopyMigrationPackage log file within the directory specified within the SourcePackagePath parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoSnapshotCreation - -Indicates to not perform snapshots on the content in the containers. The default is to snapshot each of the packages files in the containers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoUpload - -Indicates to not upload the package files. The default is to upload all the package files. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Overwrite - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PackageContainerName - -The optional name of the Azure Blob Storage container that will be created if it does not currently exist. It will hold the uploaded package metadata files. The value must be in lower case and conform to Azure's container naming rules. If this not supplied a name will be generated using the format <GUID>-package. - -```yaml -Type: String -Parameter Sets: ImplicitSourceExplicitAzure, ExplicitSourceExplicitAzure -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceFilesPath - -The directory location where the package's source content files exist. - -```yaml -Type: String -Parameter Sets: ExplicitSourceExplicitAzure, ExplicitSourceImplicitAzure -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcePackagePath - -The directory location where the package's metadata files exist. - -```yaml -Type: String -Parameter Sets: ExplicitSourceExplicitAzure, ExplicitSourceImplicitAzure -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMultiGeoCompanyAllowedDataLocation.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMultiGeoCompanyAllowedDataLocation.md deleted file mode 100644 index e0360b1465..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMultiGeoCompanyAllowedDataLocation.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spomultigeocompanyalloweddatalocation -applicable: SharePoint Online -title: Set-SPOMultiGeoCompanyAllowedDataLocation -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Set-SPOMultiGeoCompanyAllowedDataLocation - -## SYNOPSIS - -Adds a multi-geo allowed location. - -## SYNTAX - -```powershell -Set-SPOMultiGeoCompanyAllowedDataLocation [-Location] <string> [-InitialDomain] <string> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to set the multi-geo allowed locations. - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOMultiGeoCompanyAllowedDataLocation -Location AUS -Domain contoso.com -``` - -Sets AUS (Australia) as an allowed multi-geo location for the domain contoso.com. - -## PARAMETERS - -### -Location - -The Preferred Data Location (PDL) to allow. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InitialDomain - -Sets the initial domain to assocate with the specified data location. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES - -## RELATED LINKS - -[Remove-SPOMultiGeoCompanyAllowedDataLocation](https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spomultigeocompanyalloweddatalocation) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMultiGeoExperience.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMultiGeoExperience.md deleted file mode 100644 index c326931521..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOMultiGeoExperience.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spomultigeoexperience -applicable: SharePoint Online -title: Set-SPOMultiGeoExperience -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Set-SPOMultiGeoExperience - -## SYNOPSIS - -. - -## SYNTAX - -```powershell - Set-SPOMultiGeoExperience [-AllInstances] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to set a get location into SPO mode. This upgrade action is not reversible. For more information see [Enabling SharePoint Multi-Geo in your satellite geo location](https://docs.microsoft.com/office365/enterprise/enabling-sp-multigeo-satellite-geolocation) - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOMultiGeoExperience -``` - -This example will upgrade your instance's multi-geo experience to include SharePoint Online Multi-Geo. This operation usually takes about an hour while we perform various publish backs in the service and re-stamp your tenant. - -## PARAMETERS - -### -AllInstances - -. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOOrgAssetsLibrary.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOOrgAssetsLibrary.md deleted file mode 100644 index 3f66af40e6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOOrgAssetsLibrary.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spoorgassetslibrary -applicable: SharePoint Online -title: Set-SPOOrgAssetsLibrary -author: Maralesfahanpoor -ms.author: maesfaha -ms.reviewer: -manager: paulac -schema: 2.0.0 ---- - -# Set-SPOOrgAssetsLibrary - -## SYNOPSIS - -Updates information for a library that is designated as a location for organization assets. - -## SYNTAX - -```powershell -Set-SPOOrgAssetsLibrary -LibraryUrl <String> -ThumbnailUrl <String> [<CommonParameters>] -``` - -## DESCRIPTION - -The Set-SPOOrgAssetsLibrary cmdlet updates information for a library that is designated as a location for organization assets. Updating the thumbnail URL is currently supported. - -## EXAMPLES - -### Example 1 - -This example updates the thumbnail URL publicly displayed for the library to contosologo2.jpg. - -```powershell -Set-SPOOrgAssetsLibrary -LibraryURL sites/branding/Assets -ThumbnailURL https://contoso.sharepoint.com/sites/branding/Assets/contosologo2.jpg -``` - -### Example 2 - -This example removes the thumbnail URL that was previously set for the library. - -```powershell -Set-SPOOrgAssetsLibrary -LibraryURL sites/branding/Assets -ThumbnailURL "" -``` - -## PARAMETERS - -### -LibraryUrl - -Indicates the server relative URL of the library to be modified. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThumbnailUrl - -Indicates the URL of the background image used when the library is publicly displayed. If no thumbnail URL is indicated, the card will have a gray background. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/add-spoorgassetslibrary?view=sharepoint-ps) - -[Get-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/get-spoorgassetslibrary?view=sharepoint-ps) - -[Remove-SPOOrgAssetsLibrary](https://docs.microsoft.com/powershell/module/sharepoint-online/remove-spoorgassetslibrary?view=sharepoint-ps) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOOrgNewsSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOOrgNewsSite.md deleted file mode 100644 index c3a533583a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOOrgNewsSite.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spoorgnewssite -applicable: SharePoint Online -title: Set-SPOOrgNewsSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen ---- - -# Set-SPOOrgNewsSite - -## SYNOPSIS - -Marks a site as one of multiple possible tenant's organizational news sites. Requires Global administrator or SharePoint administrator permissions. - -## SYNTAX - -```powershell -Set-SPOOrgNewsSite -OrgNewsSiteUrl <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to mark a site as an organizational authoritative news site. Such sites get primary treatment in the SharePoint user interface. - -If a site with specified URL doesn't exist, this cmdlet returns a "File not found" error. - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOOrgNewsSite -OrgNewsSiteUrl https://contoso.sharepoint.com/sites/Marketing -``` - -This example marks <https://contoso.sharepoint.com/sites/Marketing> as an organizational news site. - -## PARAMETERS - -### -OrgNewsSiteUrl - -The URL of a site to be marked as an organizational news site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## RELATED LINKS - -[Remove-SPOOrgNewsSite](Remove-SPOOrgNewsSite.md) - -[Get-SPOOrgNewsSite](Get-SPOOrgNewsSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md deleted file mode 100644 index ba52c45675..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md +++ /dev/null @@ -1,862 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-sposite -applicable: SharePoint Online -title: Set-SPOSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOSite - -## SYNOPSIS - -Sets or updates one or more properties' values for a site collection. - -## SYNTAX - -### ParamSet1 - -```powershell -Set-SPOSite [-Identity] <SpoSitePipeBind> [-AllowSelfServiceUpgrade <Boolean>] [-Confirm] - [-DenyAddAndCustomizePages <Boolean>] [-LocaleId <UInt32>] [-LockState <String>] [-NoWait] [-Owner <String>] - [-ResourceQuota <Double>] [-ResourceQuotaWarningLevel <Double>] - [-SandboxedCodeActivationCapability <SandboxedCodeActivationCapabilities>] - [-SharingCapability <SharingCapabilities>] [-StorageQuota <Int64>] [-StorageQuotaWarningLevel <Int64>] - [-Title <String>] [-WhatIf] [-BlockDownloadOfNonViewableFiles <Boolean>] - [-CommentsOnSitePagesDisabled <Boolean>] [-SocialBarOnSitePagesDisabled <Boolean>] - [-DisableAppViews <AppViewsPolicy>] - [-DisableCompanyWideSharingLinks <CompanyWideSharingLinksPolicy>] [-DisableFlows <FlowsPolicy>] - [-RestrictedToGeo <RestrictedToRegion>] [-SharingAllowedDomainList <String>] - [-SharingBlockedDomainList <String>] [-SharingDomainRestrictionMode <SharingDomainRestrictionModes>] - [-ShowPeoplePickerSuggestionsForGuestUsers <Boolean>] [-StorageQuotaReset] - [-DefaultSharingLinkType] [-DefaultLinkPermission] [-DefaultLinkToExistingAccess] - [-ConditionalAccessPolicy <SPOConditionalAccessPolicyType>] [-LimitedAccessFileType <SPOLimitedAccessFileType>] [-AllowEditing <Boolean>] [-AnonymousLinkExpirationInDays <Int32>] [-OverrideTenantAnonymousLinkExpirationPolicy <Boolean>] [-SensitivityLabel <String>][<CommonParameters>] -``` - -### ParamSet2 - -```powershell -Set-SPOSite [-Identity] <SpoSitePipeBind> -EnablePWA <Boolean> [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### ParamSet3 - -```powershell -Set-SPOSite [-Identity] <SpoSitePipeBind> [-Confirm] [-DisableSharingForNonOwners] [-WhatIf] - [<CommonParameters>] -``` - -### ParamSet4 (valid for Group Site Collection) - -```powershell -Set-SPOSite [-Identity] <SpoSitePipeBind> [-AllowSelfServiceUpgrade <Boolean>] [-Confirm] - [-DenyAddAndCustomizePages <Boolean>] [-LocaleId <UInt32>] [-LockState <String>] [-NoWait] [-Owner <String>] - [-ResourceQuota <Double>] [-ResourceQuotaWarningLevel <Double>] - [-SandboxedCodeActivationCapability <SandboxedCodeActivationCapabilities>] - [-SharingCapability <SharingCapabilities>] [-StorageQuota <Int64>] [-StorageQuotaWarningLevel <Int64>] - [<CommonParameters>] -``` - -## DESCRIPTION - -For any parameters that are passed in, the `Set-SPOSite` cmdlet sets or updates the setting for the site collection identified by parameter Identity. - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832.> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com/sites/site1 -Owner joe.healy@contoso.com -NoWait -``` - -Example 1 updates the owner of site collection <https://contoso.sharepoint.com/sites/site1> to the person whose email address is joe.healy@contoso.com. This cmdlet is executed immediately without delay. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com/sites/site1 -ResourceQuota 0 -StorageQuota 1024 -``` - -Example 2 updates the settings of site collection <https://contoso.sharepoint.com/sites/site1.> The storage quota is updated to 1024 megabytes (1 GB) and the resource quota is updated to 0 megabytes. - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com -StorageQuota 1500 -StorageQuotaWarningLevel 1400 -``` - -This example updates the settings of site collection <https://contoso.sharepoint.com.> The storage quota is updated to 1500 megabytes and the storage quota warning level is updated to 1400 megabytes. - -### -----------------------EXAMPLE 4----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com -DisableSharingForNonOwners -``` - -Example 4 prevents non-owners of a site from inviting new users to the site. - -### -----------------------EXAMPLE 5----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com/sites/groupname -StorageQuota 3000 -StorageQuotaWarningLevel 2000 -``` - -This example sets the quota for the site. - -> [!NOTE] -> If Site Collection Storage Management is enabled for the tenant, you will not be able to set quota and will have a generic error returned. To workaround this issue, set the site collection storage management to "manual" temporarily, set your quotas and then set the site collection storage management setting back to its original setting. - -### -----------------------EXAMPLE 6----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com/sites/site1 -EnablePWA $true -``` - -Example 6 enables the site "site1" to create Project Web Applications (PWA). - -### -----------------------EXAMPLE 7----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com/sites/site1 -SharingCapability ExternalUserSharingOnly -Set-SPOSite -Identity https://contoso.sharepoint.com/sites/site1 -SharingDomainRestrictionMode AllowList -SharingAllowedDomainList "contoso.com" -``` - -Example 7 sets the Sharing Capability to allow external users who accept sharing invitations and sign in as authenticated users, and then specifies an email domain that is allowed for sharing with the external collaborators. - - -## PARAMETERS - -### -EnablePWA - -Determines whether site can include Project Web App. -For more information about Project Web App, see Plan SharePoint groups in Project Server. - -```yaml -Type: Boolean -Parameter Sets: ParamSet2 -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the URL of the site collection to update. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AllowSelfServiceUpgrade - -Determines whether site collection administrators can upgrade their site collections. - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DenyAddAndCustomizePages - -Determines whether the Add And Customize Pages right is denied on the site collection. -For more information about permission levels, see User permissions and permission levels in SharePoint. - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableSharingForNonOwners - -This parameter prevents non-owners from invited new users to the site. - -This parameter is available only in SharePoint Online Management Shell Version 16.0.4613.1211 or later. - -```yaml -Type: SwitchParameter -Parameter Sets: ParamSet3 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocaleId - -Specifies the language of this site collection. -For more information, see Locale IDs Assigned by Microsoft (<https://go.microsoft.com/fwlink/p/?LinkId=242911).> - -```yaml -Type: UInt32 -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LockState - -Sets the lock state on a site. -Valid values are: NoAccess, ReadOnly and Unlock. -When the lock state of a site is ReadOnly, a message will appear on the site stating that the site is under maintenance and it is read-only. -When the lock state of a site is NoAccess, all traffic to the site will be blocked. -If parameter NoAccessRedirectUrl in the `Set-SPOTenant` cmdlet is set, traffic to sites that have a lock state NoAccess will be redirected to that URL. -If parameter NoAccessRedirectUrl is not set, a 403 error will be returned. -It isn't possible to set the lock state on the root site collection. - -```yaml -Type: String -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoWait - -Specifies to continue executing script immediately. - -```yaml -Type: SwitchParameter -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner - -Specifies the owner of the site collection. - -```yaml -Type: String -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResourceQuota - -Specifies the resource quota in megabytes of the site collection. -The default value is 0. -For more information, see Resource Usage Limits on Sandboxed Solutions in SharePoint (<https://msdn.microsoft.com/en-us/library/gg615462.aspx).> - -```yaml -Type: Double -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResourceQuotaWarningLevel - -Specifies the warning level in megabytes of the site collection to warn the site collection administrator that the site is approaching the resource quota. - -```yaml -Type: Double -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SensitivityLabel - -Used to specify the unique identifier (GUID) of the SensitivityLabel. - -```yaml -Type: String -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SandboxedCodeActivationCapability - -PARAMVALUE: Unknown | Check | Disabled | Enabled - -```yaml -Type: SandboxedCodeActivationCapabilities -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingCapability - -Determines what level of sharing is available for the site. -The possible values are: Disabled - don't allow sharing outside your organization, ExistingExternalUserSharingOnly - Allow sharing only with the external users that already exist in your organization's directory, ExternalUserSharingOnly - allow external users who accept sharing invitations and sign in as authenticated users, or ExternalUserAndGuestSharing - allow sharing with all external users, and by using anonymous access links. - -For more information about sharing, see Turn external sharing on or off for SharePoint Online (<https://docs.microsoft.com/sharepoint/turn-external-sharing-on-or-off).> - -```yaml -Type: SharingCapabilities -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StorageQuota - -Specifies the storage quota in megabytes of the site collection. - -```yaml -Type: Int64 -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StorageQuotaWarningLevel - -Specifies the warning level in megabytes of the site collection to warn the site collection administrator that the site is approaching the storage quota. - -```yaml -Type: Int64 -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title - -Specifies the title of the site collection. - -```yaml -Type: String -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowLimitedAccess - -{{Fill AllowLimitedAccess Description}} - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockDownloadOfNonViewableFiles - -{{Fill BlockDownloadOfNonViewableFiles Description}} - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CommentsOnSitePagesDisabled - -Use this parameter to disable Comments section on Site Pages. -The parameter can't be used for Groups Site Collections. - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialBarOnSitePagesDisabled - -Disables or enables the Social Bar for Site Collection. - -The Social Bar will appear on all modern SharePoint pages with the exception of the home page of a site. It will give users the ability to like a page, see the number of views, likes, and comments on a page, and see the people who have liked a page. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableAppViews - -PARAMVALUE: Unknown | Disabled | NotDisabled - -```yaml -Type: AppViewsPolicy -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableCompanyWideSharingLinks - -PARAMVALUE: Unknown | Disabled | NotDisabled - -```yaml -Type: CompanyWideSharingLinksPolicy -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableFlows - -PARAMVALUE: Unknown | Disabled | NotDisabled - -```yaml -Type: FlowsPolicy -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictedToGeo - -PARAMVALUE: NoRestriction | BlockMoveOnly | BlockFull | Unknown - -```yaml -Type: RestrictedToRegion -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingAllowedDomainList - -Specifies a list of email domains that is allowed for sharing with the external collaborators. Use the space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -For additional information about how to restrict a domain sharing, see Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business. - -```yaml -Type: String -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingBlockedDomainList - -Specifies a list of email domains that is blocked or prohibited for sharing with the external collaborators. Use space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -For additional information about how to restrict a domain sharing, see Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business. - -```yaml -Type: String -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingDomainRestrictionMode - -Specifies the external sharing mode for domains. - -The following values are: - -None - -AllowList - -BlockList - -For additional information about how to restrict a domain sharing, see Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business. - -```yaml -Type: SharingDomainRestrictionModes -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowPeoplePickerSuggestionsForGuestUsers - -To enable the option to search for existing guest users at Site Collection Level, set this parameter to $true. - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StorageQuotaReset - -Resets the OneDrive for Business storage quota to the tenant's new default storage space. - -```yaml -Type: SwitchParameter -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultSharingLinkType - -The default link type for the site collection - -PARAMVALUE: None | AnonymousAccess | Internal | Direct - -None - Respect the organization default sharing link type -AnonymousAccess - Sets the default sharing link for this site to an Anonymous Access or Anyone link -Internal - Sets the default sharing link for this site to the "organization" link or company shareable link -Direct - Sets the default sharing link for this site to the "Specific people" link - -```yaml -Type: SharingLinkType -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultLinkToExistingAccess - -When set to TRUE, the DefaultSharingLinkType will be overriden and the default sharing link will a People with Existing Access link (which does not modify permissions). When set to FALSE (the default), the default sharing link type is controlled by the DefaultSharingLinkType parameter - -PARAMVALUE: $true | $false - - -```yaml -Type: SharingLinkType -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultLinkPermission - -The default link permission for the site collection - -PARAMVALUE: None | View | Edit - -None - Respect the organization default link permission -View - Sets the default link permission for the site to "view" permissions -Edit - Sets the default link permission for the site to "edit" permissions - -```yaml -Type: SharingPermissionType -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverrideTenantAnonymousLinkExpirationPolicy - -Choose whether to override the anonymous or anyone link expiration policy on this site - -PARAMVALUE: None | False | True - -None - Respect the organization-level policy for anonymous or anyone link expiration -False - Respect the organization-level policy for anonymous or anyone link expiration -True - Override the organization-level policy for anonymous or anyone link expiration (can be more or less restrictive) - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnonymousLinkExpirationInDays - -Specifies all anonymous/anyone links that have been created (or will be created) will expire after the set number of days. Only applies if OverrideTenantAnonymousLinkExpirationPolicy is set to true. - -To remove the expiration requirement, set the value to zero (0). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalAccessPolicy - -Please read [Control access from unmanaged devices](https://docs.microsoft.com/sharepoint/control-access-from-unmanaged-devices ) documentation here to understand Conditional Access Policy usage in SharePoint Online. - -PARAMVALUE: AllowFullAccess | AllowLimitedAccess | BlockAccess - -```yaml -Type: SPOConditionalAccessPolicyType -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: AllowFullAccess -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowEditing - -Prevents users from editing Office files in the browser and copying and pasting Office file contents out of the browser window. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LimitedAccessFileType - -The following parameters can be used with -ConditionalAccessPolicy AllowLimitedAccess for both the organization-wide setting and the site-level setting. --OfficeOnlineFilesOnly: Allows users to preview only Office files in the browser. This option increases security but may be a barrier to user productivity. --LimitedAccessFileType WebPreviewableFiles (default): Allows users to preview Office files and other file types (such as PDF files and images) in the browser. Note that the contents of file types other than Office files are handled in the browser. This option optimizes for user productivity but offers less security for files that aren't Office files. --LimitedAccessFileType OtherFiles: Allows users to download files that can't be previewed, such as .zip and .exe. This option offers less security. - -PARAMVALUE: OfficeOnlineFilesOnly | WebPreviewableFiles | OtherFiles - -```yaml -Type: SPOLimitedAccessFileType -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: WebPreviewableFiles -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Set-SPOTenant](Set-SPOTenant.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteDesign.md deleted file mode 100644 index 50577f371c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteDesign.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spositedesign -applicable: SharePoint Online -title: Set-SPOSiteDesign -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOSiteDesign - -## SYNOPSIS - -Updates a previously uploaded site design. - -## SYNTAX - -```powershell -Set-SPOSiteDesign - [-Identity <SPOSiteDesignPipeBind>] - [-Title <string>] - [-WebTemplate <string>] - [-SiteScripts <SPOSiteScriptPipeBind[]>] - [-Description <string>] - [-PreviewImageUrl <string>] - [-PreviewImageAltText <string>] - [-IsDefault] - [<CommonParameters>] -``` - -## EXAMPLES - -### Example 1 - -This example updates a previously created site design. - -```powershell -Set-SPOSiteDesign ` - -Identity 44252d09-62c4-4913-9eb0-a2a8b8d7f863 ` - -Title "Contoso customer tracking - version 2" ` - -WebTemplate "68" ` - -Description "Updated site design for list schema that tracks key customer data in a list" ` - -PreviewImageUrl "https://contoso.sharepoint.com/SiteAssets/site-preview.png" ` - -PreviewImageAltText "site preview - version 2" -``` - -## DESCRIPTION - -Updates a previously uploaded site design. - -## PARAMETERS - -### -Identity - -The site design Id. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title - -The display name of the site design. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebTemplate - -Identifies which base template to add the design to. Use the value **64** for the Team site template, and the value **68** for the Communication site template. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteScripts - -An array of one or more site scripts. Each is identified by an ID. The scripts run in the order listed. - -```yaml -Type: SPOSiteScriptPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -The display description of the site design. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviewImageUrl - -The URL of a preview image. If none is specified, SharePoint uses a generic image. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreviewImageAltText - -The alt text description of the image for accessibility. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDefault - -A switch that if provided, applies the site design to the default site template. For more information, see [Customize a default site design](https://docs.microsoft.com/sharepoint/dev/declarative-customization/customize-default-site-design). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteGroup.md deleted file mode 100644 index b9510fde0f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteGroup.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spositegroup -applicable: SharePoint Online -title: Set-SPOSiteGroup -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOSiteGroup - -## SYNOPSIS - -Updates the SharePoint Online owner and permission levels on a group inside a site collection. - -## SYNTAX - -```powershell -Set-SPOSiteGroup -Identity <String> [-Name <String>] [-Owner <String>] [-PermissionLevelsToAdd <String[]>] - [-PermissionLevelsToRemove <String[]>] -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -You must be a SharePoint Online global administrator and a site collection administrator to run the `Set-SPOSiteGroup` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Set-SPOSiteGroup -Site https://contoso.sharepoint.com/sites/siteA -Identity "ProjectViewers" -PermissionLevelsToRemove "Full Control" -PermissionLevelsToAdd "View Only" -``` - -Example 1 changes permission level of the ProjectViewers group inside site collection <https://contoso.sharepoint.com/sites/siteA> from Full Control to View Only. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Set-SPOSiteGroup -Site https://contoso.sharepoint.com -Identity "ProjectViewers" -Owner Melissa.kerr@contoso.com -``` - -Example 2 sets Melissa.kerr@contoso.com as the owner of the ProjectViewers group. - -## PARAMETERS - -### -Identity - -Specifies the name of the group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the new name of the group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner - -Specifies the owner (individual or a security group) of the group to be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionLevelsToAdd - -Specifies the permission levels to grant to the group. - -> [!NOTE] -> Permission levels are defined by SharePoint Online global administrators from SharePoint Online Administration Center. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionLevelsToRemove - -Specifies the permission levels to remove from the group. - -> [!NOTE] -> Permission levels are defined by SharePoint Online global administrators from SharePoint Online Administration Center. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the site collection the group belongs to. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOSiteGroup](Get-SPOSiteGroup.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteOffice365Group.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteOffice365Group.md deleted file mode 100644 index c51f2ceb16..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteOffice365Group.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spositeoffice365group -applicable: SharePoint Online -title: Set-SPOSiteOffice365Group -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOSiteOffice365Group - -## SYNOPSIS - -Connects a top-level SPO site collection to a new Office 365 Group. - -## SYNTAX - -```powershell -Set-SPOSiteOffice365Group - -Site <string> - -DisplayName <string> - -Alias <string> - [-IsPublic] - [-Description <string>] - [-Classification <string>] - [-KeepOldHomepage] - [<CommonParameters>] -``` - -## DESCRIPTION - -Connects a top-level SPO site collection to a new Office 365 Group. You must be a SharePoint Online global administrator to run the cmdlet. - -> [!IMPORTANT] -> This cmdlet is currently in preview and is subject to change. It is not currently supported for use in production environments. - -If the site doesn't exist, this cmdlet returns a "File not found" error. - -## EXAMPLES - -### Example 1 - -This example creates a new Office 365 Group named "site1group" and connects site collection <https://contoso.sharepoint.com/sites/site1> to it. The group will privacy set to "Private" and Classification set to "Highly Confidential". - -```powershell -Set-SPOSiteOffice365Group -Site https://contoso.sharepoint.com/sites/site1 -DisplayName "site1group" -Alias "site1group" -Classification "Highly Confidential" -``` - -### Example 2 - -This example creates a new Office 365 Group named "classicsite" and connects site collection <https://contoso.sharepoint.com/sites/classicsite> to it. It will keep the old home page from the classic site. - -```powershell -Set-SPOSiteOffice365Group -Site https://contoso.sharepoint.com/sites/classicsite -DisplayName "Classic Site" -Alias "classicsite" -KeepOldHomepage -``` - -## PARAMETERS - -### -Site - -The site collection being connected to new Office 365 Group. - -```yaml -Type: Microsoft.Online.SharePoint.PowerShell.SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName - -Specifies the name of the new Office 365 Group that will be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Alias - -Specifies the email alias for the new Office 365 Group that will be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -Specifies the group's description. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsPublic - -Determines the Office 365 Group's privacy setting. If switch is included, the group will be public, otherwise it will be private. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Classification - -Specifies the classification value, if classifications are set for the organization. If no value is provided, the default classification will be set, if one is configured. - -See [Azure Active Directory cmdlets for configuring group settings](https://go.microsoft.com/fwlink/?LinkID=827484) and follow the steps in the Create settings at the directory level to define the classification for Office 365 groups. - -See [Manage Office 365 Groups with PowerShell](https://support.office.com/en-us/article/Manage-Office-365-Groups-with-PowerShell-aeb669aa-1770-4537-9de2-a82ac11b0540) for more information. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepOldHomepage - -For sites that already have a modern page set as homepage, you can specify whether you want to keep it as the homepage. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteScript.md deleted file mode 100644 index 761da6b6a8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteScript.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spositescript -applicable: SharePoint Online -title: Set-SPOSiteScript -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOSiteScript - -## SYNOPSIS - -Updates a previously uploaded site script. - -## SYNTAX - -```powershell -Set-SPOSiteScript - -Identity <SPOSiteScriptPipeBind> - -Title <string> - -Content <string> - [-Description <string>] - [-Version <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION - -Updates a previously uploaded site script. - -## EXAMPLES - -### Example 1 - -This example updates a previously created site script. Any site designs referencing it execute the updated script. - -```powershell -$newnavscript = @' -{ - "$schema": "schema.json", - "actions": [ - { - "verb": "addNavLink", - "url": "/Custom Library", - "displayName": "Custom Library Updated", - "isWebRelative": true - }, - { - "verb": "addNavLink", - "url": "/Lists/Custom List", - "displayName": "Custom List Updated", - "isWebRelative": true - }, - { - "verb": "applyTheme", - "themeName": "Contoso Explorers" - } - ], - "bindata": { }, - "version": 2 -}; -'@ - -Set-SPOSiteScript -Identity edaec4ec-71e2-4026-ac1e-6686bb30190d -Content $newnavscript -Version 2 - -``` - -## PARAMETERS - -### -Identity - -The id of the site design. - -```yaml -Type: SPOSiteDesignPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title - -The display name of the site design. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Content - -The JSON value that describes the script. For more information, see the [JSON reference](https://docs.microsoft.com/sharepoint/dev/declarative-customization/site-design-json-schema). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -A description of the script. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Version - -A version number of the script. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -## OUTPUTS - -## NOTES diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOStorageEntity.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOStorageEntity.md deleted file mode 100644 index f26a46dcac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOStorageEntity.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spostorageentity -applicable: SharePoint Online -title: Set-SPOStorageEntity -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOStorageEntity - -## SYNOPSIS - -Tenant properties allow tenant administrators to add properties in the app catalog that can be read by various SharePoint Framework components. Because tenant properties are stored in the tenant app catalog, you must provide the tenant app catalog site collection URL or the site collection app catalog URL in the following cmdlets. - -## SYNTAX - -```powershell -Set-SPOStorageEntity -Site <SpoSitePipeBind> -Key <string> -Value <string> -Comments <string> -Description <string> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdLet is used to set a value in the property bag. - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOStorageEntity -Site "https://tenant-name.sharepoint.com/sites/app-catalog" -Key "MyCustomKey" -Value "{'MyKey':1234}" -Comments "This is an example" -Description "This is an example" -``` - -This example adds an entry to the property bag. - -## PARAMETERS - -### -Site - -URL to the tenant or site collection app catalog. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Key - -The key in the property bag that should be removed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Value - -Value to be set. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Comments - -Comment for this property bag entry. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -Description of the property. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md deleted file mode 100644 index d76b66e5f4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md +++ /dev/null @@ -1,1696 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spotenant -applicable: SharePoint Online -title: Set-SPOTenant -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOTenant - -## SYNOPSIS - -Sets properties on the SharePoint Online organization. - -## SYNTAX - -```powershell -Set-SPOTenant [-ApplyAppEnforcedRestrictionsToAdHocRecipients <Boolean>] - [-BccExternalSharingInvitations <Boolean>] - [-BccExternalSharingInvitationsList <String>] - [-BlockDownloadLinksFileType <BlockDownloadLinksFileTypes>] - [-DisplayStartASiteOption <Boolean>] - [-EnableAIPIntegration <Boolean>] - [-EnableMinimumVersionRequirement <Boolean>] - [-EnablePromotedFileHandlers <Boolean>] - [-ExternalServicesEnabled <Boolean>] - [-MarkNewFilesSensitiveByDefault <SensitiveByDefaultState>] - [-MaxCompatibilityLevel <Int32>] - [-MinCompatibilityLevel <Int32>] - [-NoAccessRedirectUrl <String>] - [-OfficeClientADALDisabled <Boolean>] - [-ProvisionSharedWithEveryoneFolder <Boolean>] - [-RequireAcceptingAccountMatchInvitedAccount <Boolean>] - [-SearchResolveExactEmailOrUPN <Boolean>] - [-SharingCapability <SharingCapabilities>] - [-ShowAllUsersClaim <Boolean>] - [-ShowEveryoneClaim <Boolean>] - [-ShowEveryoneExceptExternalUsersClaim <Boolean>] - [-SignInAccelerationDomain <String>] - [-StartASiteFormUrl <String>] - [-UsePersistentCookiesForExplorerView <Boolean>] - [-CommentsOnSitePagesDisabled <Boolean>] - [-CommentsOnFilesDisabled <Boolean>] - [-SocialBarOnSitePagesDisabled <Boolean>] - [-DefaultLinkPermission <SharingPermissionType>] - [-DefaultSharingLinkType <SharingLinkType>] - [-DisabledWebPartIds <Guid>] - [-DisallowInfectedFileDownload <Boolean>] - [-EnableGuestSignInAcceleration <Boolean>] - [-FileAnonymousLinkType <AnonymousLinkType>] - [-FilePickerExternalImageSearchEnabled <Boolean>] - [-FolderAnonymousLinkType <AnonymousLinkType>] - [-IPAddressAllowList <String>] - [-IPAddressEnforcement <Boolean>] - [-IPAddressWACTokenLifetime <Int32>] - [-LegacyAuthProtocolsEnabled <Boolean>] - [-NotificationsInOneDriveForBusinessEnabled <Boolean>] - [-NotificationsInSharePointEnabled <Boolean>] - [-NotifyOwnersWhenInvitationsAccepted <Boolean>] - [-NotifyOwnersWhenItemsReshared <Boolean>] - [-ODBAccessRequests <SharingState>] - [-ODBMembersCanShare <SharingState>] - [-OneDriveForGuestsEnabled <Boolean>] - [-OneDriveStorageQuota <Int64>] - [-OrphanedPersonalSitesRetentionPeriod <Int32>] - [-OwnerAnonymousNotification <Boolean>] - [-PermissiveBrowserFileHandlingOverride <Boolean>] - [-PreventExternalUsersFromResharing <Boolean>] - [-PublicCdnAllowedFileTypes <String>] - [-PublicCdnEnabled <Boolean>] - [-RequireAnonymousLinksExpireInDays <Int32>] - [-SharingAllowedDomainList <String>] - [-SharingBlockedDomainList <String>] - [-SharingDomainRestrictionMode <SharingDomainRestrictionModes>] - [-ShowPeoplePickerSuggestionsForGuestUsers <Boolean>] - [-SpecialCharactersStateInFileFolderNames <SpecialCharactersState>] - [-SyncPrivacyProfileProperties <Boolean>] - [-UseFindPeopleInPeoplePicker <Boolean>] - [-UserVoiceForFeedbackEnabled <Boolean>] - [-ContentTypeSyncSiteTemplatesList MySites [-ExcludeSiteTemplate]] - [-CustomizedExternalSharingServiceUrl <String>] - [-ConditionalAccessPolicy <SPOConditionalAccessPolicyType>] - [-ConditionalAccessPolicyErrorHelpLink <String>] - [-LimitedAccessFileType <SPOLimitedAccessFileType>] - [-AllowDownloadingNonWebViewableFiles <Boolean>] - [-AllowCommentsTextOnEmailEnabled <Boolean>] - [-AllowEditing <Boolean>] - [-EnableAzureADB2BIntegration <Boolean>] - [-ExternalUserExpirationRequired <Boolean>] - [-ExternalUserExpireInDays <Int32>] - [-EmailAttestationRequired <Boolean>] - [-EmailAttestationReAuthDays <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION - -You can use the `Set-SPOTenant` cmdlet to enable external services and to specify the versions in which site collections can be created. -You can also use the `Set-SPOSite` cmdlet together with the `Set-SPOTenant` cmdlet to block access to a site in your organization and redirect traffic to another site. - -You must be a SharePoint Online global administrator to run the cmdlet. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Set-SPOSite -Identity https://contoso.sharepoint.com/sites/team1 -LockState NoAccess -Set-SPOTenant -NoAccessRedirectUrl 'https://www.contoso.com/' -``` - -This example blocks access to <https://contoso.sharepoint.com/sites/team1> and redirects traffic to <https://www.contoso.com.> - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Set-SPOTenant -ShowEveryoneExceptExternalUsersClaim $false -``` - -This example hides the "Everyone Except External Users" claim in People Picker. - -### -----------------------EXAMPLE 3----------------------------- - -```powershell -Set-SPOTenant -ShowAllUsersClaim $false -``` - -This example hides the "All Users" claim group in People Picker. - -### -----------------------EXAMPLE 4----------------------------- - -```powershell -Set-SPOTenant -UsePersistentCookiesForExplorerView $true -``` - -This example enables the use of special persisted cookie for Open with Explorer. - -### -----------------------EXAMPLE 5----------------------------- - -```powershell -Set-SPOTenant -LegacyAuthProtocolsEnabled $True -``` - -This example enables legacy authentication protocols on the tenant. This can help to enable login in situations where the admin users get an error like "Cannot contact web site '<https://contoso-admin.sharepoint.com/'> or the web site does not support SharePoint Online credentials. The response status code is 'Unauthorized'.", and the underlying error is "Access denied. Before opening files in this location, you must first browse to the web site and select the option to login automatically." - -### -----------------------EXAMPLE 6------------------------------ - -```powershell -Set-SPOTenant -ContentTypeSyncSiteTemplatesList MySites -``` - -This example enables Content Type Hub to push content types to all OneDrive for Business sites. There is no change in Content Type Publishing behavior for other sites. - -### -----------------------EXAMPLE 7------------------------------- - -```powershell -Set-SPOTenant -ContentTypeSyncSiteTemplatesList MySites -ExcludeSiteTemplate -``` - -This example stops publishing content types to OneDrive for Business sites. - -### -----------------------EXAMPLE 8------------------------------- - -```powershell -Set-SPOTenant -SearchResolveExactEmailOrUPN $true -``` - -This example disables starts with for all users/partial name search functionality for all SharePoint users, except SharePoint Admins. - -### -----------------------EXAMPLE 9------------------------------- - -```powershell -Set-SPOTenant -UseFindPeopleInPeoplePicker $true -``` - -This example enables tenant admins to enable ODB and SPO to respect Exchange supports Address Book Policy (ABP) policies in the people picker. - -### -----------------------EXAMPLE 10------------------------------- - -```powershell -Set-SPOTenant -ShowPeoplePickerSuggestionsForGuestUsers $true -``` - -This example enable the option to search for existing guest users at Tenant Level. - -## PARAMETERS - -### -ApplyAppEnforcedRestrictionsToAdHocRecipients - -When the feature is enabled, all guest users are subject to conditional access policy. By default guest users who are accessing SharePoint Online files with pass code are exempt from the conditional access policy. - -The valid values are: - -- False (default) - Guest access users are exempt from conditional access policy. -- True - Conditional access policy is also applied to guest users. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BccExternalSharingInvitations - -When the feature is enabled, all external sharing invitations that are sent will blind copy the e-mail messages listed in the BccExternalSharingsInvitationList. - -The valid values are: - -- False (default) - BCC for external sharing is disabled. -- True - All external sharing invitations that are sent will blind copy the e-mail messages listed in the BccExternalSharingsInvitationList. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BccExternalSharingInvitationsList - -Specifies a list of e-mail addresses to be BCC'd when the BCC for External Sharing feature is enabled. -Multiple addresses can be specified by creating a comma separated list with no spaces. - -The valid values are: - -- "" (default) - Blank by default, this will also clear any value that has been set. -- Single or Multiple e-mail addresses - joe@contoso.com or joe@contoso.com,bob@contoso.com - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockDownloadLinksFileType - -The valid values are: - -- WebPreviewableFiles -- ServerRenderedFilesOnly - -```yaml -Type: BlockDownloadLinksFileTypes -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: WebPreviewableFiles -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayStartASiteOption - -Determines whether tenant users see the Start a Site menu option. - -The valid values are: - -- True (default) - Tenant users will see the Start a Site menu option. -- False - Start a Site is hidden from the menu. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableAIPIntegration - -This parameter enables SharePoint to process the content of files stored in SharePoint and OneDrive with sensitivity labels that include encryption. (Currently in public preview). For more information, see [Enable sensitivity labels for Office files in SharePoint and OneDrive (public preview)](https://docs.microsoft.com/microsoft-365/compliance/sensitivity-labels-sharepoint-onedrive-files). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableMinimumVersionRequirement - -This parameter was used to opt-out of the versioning setting update. It has no effect as of today as versioning setting has already been rolled out. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnablePromotedFileHandlers - -This parameter is reserved for Microsoft internal use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MarkNewFilesSensitiveByDefault - -If external sharing is turned on, sensitive content could be shared and accessed by guests before the Office DLP rule finishes processing, you can address this issue by configuring this parameter. -Possible values are -- BlockExternalSharing: Prevents guests from accessing newly added files until at least one Office DLP policy scans the content of the file. -- AllowExternalSharing: Disables this feature. - -For more information see [Mark new files as sensitive by default](https://docs.microsoft.com/sharepoint/sensitive-by-default). - -```yaml -Type: SensitiveByDefaultState -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: AllowExternalSharing -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalServicesEnabled - -Enables external services for a tenant. -External services are defined as services that are not in the Office 365 datacenters. - -The valid values are: - -- True (default) - External services are enabled for the tenant. -- False - External services that are outside of the Office 365 datacenters cannot interact with SharePoint. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxCompatibilityLevel - -Specifies the upper bound on the compatibility level for new sites. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MinCompatibilityLevel - -Specifies the lower bound on the compatibility level for new sites. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoAccessRedirectUrl - -Specifies the URL of the redirected site for those site collections which have the locked state "NoAccess." - -The valid values are: - -- "" (default) - Blank by default, this will also remove or clear any value that has been set. -- Full URL - Example: <https://contoso.sharepoint.com/Pages/Locked.aspx> - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OfficeClientADALDisabled - -When set to true this will disable the ability to use Modern Authentication that leverages ADAL across the tenant. - -The valid values are: - -- False (default) - Modern Authentication is enabled/allowed. -- True - Modern Authentication via ADAL is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProvisionSharedWithEveryoneFolder - -Creates a Shared with Everyone folder in every user's new OneDrive for Business document library. - -The valid values are: - -- True (default) - The Shared with Everyone folder is created. -- False - No folder is created when the site and OneDrive for Business document library is created. - -The default behavior of the Shared with Everyone folder changed in August 2015. -For additional information about the change, see Provision the Shared with Everyone folder in OneDrive for Business (<https://support.office.com/en-us/article/Provision-the-Shared-with-Everyone-folder-in-OneDrive-for-Business-6bb02c91-fd0b-42ba-9457-3921cb6dc5b2?ui=en-US&rs=en-US&ad=US)> - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireAcceptingAccountMatchInvitedAccount - -Ensures that an external user can only accept an external sharing invitation with an account matching the invited email address. - -Administrators who desire increased control over external collaborators should consider enabling this feature. - -Note, this only applies to new external users accepting new sharing invitations. Also, the resource owner must share with an organizational or Microsoft account or the external user will be unable to access the resource. - -The valid values are: - -- False (default) - When a document is shared with an external user, bob@contoso.com, it can be accepted by any user with access to the invitation link in the original e-mail. -- True - User must accept this invitation with bob@contoso.com. - -> [!NOTE] -> If this functionality is turned off (value is False), it is possible for the external/guest users you invite to your Azure AD, to log in using their personal, non-work accounts either on purpose, or by accident (they might have a pre-existing, signed in session already active in the browser window they use to accept your invitation). -> [!NOTE] -> Even though setting the value is instant (if you first run **Set-SPOTenant -RequireAcceptingAccountMatchInvitedAccount $True**, and then **Get-SPOTenant -RequireAcceptingAccountMatchInvitedAccount**, True should be returned), the functionality isn't turned on immediately. It may take up to 24 hours to take effect. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchResolveExactEmailOrUPN - -Removes the search capability from People Picker. Note, recently resolved names will still appear in the list until browser cache is cleared or expired. This also does not allow SharePoint users to search for security groups or SharePoint groups. - -SharePoint Administrators will still be able to use starts with or partial name matching when enabled. - -The valid values are: - -- False (default) - Starts with / partial name search functionality is available. -- True - Disables starts with for all users/partial name search functionality for all SharePoint users, except SharePoint Admins. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingCapability - -Determines what level of sharing is available for the site. - -The valid values are: - -- ExternalUserAndGuestSharing (default) - External user sharing (share by email) and guest link sharing are both enabled. -- Disabled - External user sharing (share by email) and guest link sharing are both disabled. -ExternalUserSharingOnly - External user sharing (share by email) is enabled, but guest link sharing is disabled. - -For more information about sharing, see Manage external sharing for your SharePoint online environment (<https://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/manage-external-sharing-for-your-sharepoint-online-environment-HA102849864.aspx).> - -```yaml -Type: SharingCapabilities -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: ExternalUserAndGuestSharing -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowAllUsersClaim - -Enables the administrator to hide the All Users claim groups in People Picker. - -When users share an item with "All Users (x)", it is accessible to all organization members in the tenant's Azure Active Directory who have authenticated with via this method. When users share an item with "All Users (x)" it is accessible to all organization members in the tenant that used NTLM to authentication with SharePoint. - -Note, the All Users (authenticated) group is equivalent to the Everyone claim, and shows as Everyone. -To change this, see -ShowEveryoneClaim. - -The valid values are: - -- True (default) - The All Users claim groups are displayed in People Picker. -- False - The All Users claim groups are hidden in People Picker. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowEveryoneClaim - -Enables the administrator to hide the Everyone claim in the People Picker. -When users share an item with Everyone, it is accessible to all authenticated users in the tenant's Azure Active Directory, including any active external users who have previously accepted invitations. - -Note, that some SharePoint system resources such as templates and pages are required to be shared to Everyone and this type of sharing does not expose any user data or metadata. - -The valid values are: - -- True (default) - The Everyone claim group is displayed in People Picker. -- False - The Everyone claim group is hidden from the People Picker. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowEveryoneExceptExternalUsersClaim - -Enables the administrator to hide the "Everyone except external users" claim in the People Picker. -When users share an item with "Everyone except external users", it is accessible to all organization members in the tenant's Azure Active Directory, but not to any users who have previously accepted invitations. - -The valid values are: - -- True (default) - The Everyone except external users is displayed in People Picker. -- False - The Everyone except external users claim is not visible in People Picker. - -```yaml -Type: Boolean - -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInAccelerationDomain - -Specifies the home realm discovery value to be sent to Azure Active Directory (AAD) during the user sign-in process. - -When the organization uses a third-party identity provider, this prevents the user from seeing the Azure Active Directory Home Realm Discovery web page and ensures the user only sees their company's Identity Provider's portal. -This value can also be used with Azure Active Directory Premium to customize the Azure Active Directory login page. - -Acceleration will not occur on site collections that are shared externally. - -This value should be configured with the login domain that is used by your company (that is, example@contoso.com). - -If your company has multiple third-party identity providers, configuring the sign-in acceleration value will break sign-in for your organization. - -The valid values are: - -- "" (default) - Blank by default, this will also remove or clear any value that has been set. -- Login Domain - For example: "contoso.com" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartASiteFormUrl - -Specifies URL of the form to load in the Start a Site dialog. - -The valid values are: - -- "" (default) - Blank by default, this will also remove or clear any value that has been set. -- Full URL - Example: "<https://contoso.sharepoint.com/path/to/form"> - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsePersistentCookiesForExplorerView - -Lets SharePoint issue a special cookie that will allow this feature to work even when "Keep Me Signed In" is not selected. - -"Open with Explorer" requires persisted cookies to operate correctly. -When the user does not select "Keep Me Signed in" at the time of sign-in, "Open with Explorer" will fail. - -This special cookie expires after 30 minutes and cannot be cleared by closing the browser or signing out of SharePoint Online. -To clear this cookie, the user must log out of their Windows session. - -The valid values are: - -- False (default) - No special cookie is generated and the normal Office 365 sign-in length/timing applies. -- True - Generates a special cookie that will allow "Open with Explorer" to function if the "Keep Me Signed In" box is not checked at sign-in. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CommentsOnSitePagesDisabled - -Disables or enables commenting functionality on the site pages. -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CommentsOnFilesDisabled - -Disables or enables commenting functionality on the files. -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialBarOnSitePagesDisabled - -Disables or enables the Social Bar. - -The Social Bar will appear on all modern SharePoint pages with the exception of the home page of a site. It will give users the ability to like a page, see the number of views, likes, and comments on a page, and see the people who have liked a page. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultLinkPermission - -Lets administrators choose the default permission of the link in the sharing dialog box in OneDrive for Business and SharePoint Online. This applies to anonymous access, internal and direct links. - -The valid values are None (non settable), View and Edit. - -```yaml -Type: SharingPermissionType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultSharingLinkType - -Lets administrators choose what type of link appears is selected in the "Get a link" sharing dialog box in OneDrive for Business and SharePoint Online. - -For additional information about how to change the default link type, see Change the default link type when users get links for sharing. - -> [!NOTE] -> Setting this value to "none" will default "get a link" to the most permissive link available (that is, if anonymous links are enabled, the default link will be anonymous access; if they are disabled then the default link will be internal. - -The valid values are: - -- None - Respect the organization default sharing link type -- Direct - Sets the default sharing link for this site to the Specific people link -- Internal - Sets the default sharing link for this site to the organization link or company shareable link -- AnonymousAccess - Sets the default sharing link for this site to an Anonymous Access or Anyone link - -```yaml -Type: SharingLinkType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisabledWebPartIds - -PARAMVALUE: <Guid>[,<Guid>,...] - -Allows administrators prevent certain, specific web parts from being added to pages or rendering on pages on which they were previously added. Currently, only Amazon Kindle, YouTube and Twitter web parts can be disabled in such a manner. - -To disable a specific web part you need to enter its GUID as the parameter: Amazon Kindle (46698648-fcd5-41fc-9526-c7f7b2ace919), YouTube (544dd15b-cf3c-441b-96da-004d5a8cea1d), Twitter (f6fdf4f8-4a24-437b-a127-32e66a5dd9b4). If you are looking for a GUID for any other web part, easiest way to achieve is to place the web part on a SharePoint page and move to maintenance mode. See more details around the [web part maintenance mode from Microsoft Support](https://support.office.com/en-us/article/Open-and-use-the-Web-Part-Maintenance-Page-EFF9CE22-D04A-44DD-AE83-AC29A5E396C2). - -You can enter in multiple GUIDs by using a comma to separate them. To view a list of disabled web parts, use Get-SPOTenant to get DisabledWebPartIds. - -To re-enable some disabled web parts, use the Set-SPOTenant with the -DisabledWebPartIds parameter and corresponding GUIDs that you still want to keep disabling. To re-enable all disabled web parts, use Set-SPOTenant -DisabledWebPartIds @(). - -```yaml -Type: Guid[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisallowInfectedFileDownload - -Prevents the Download button from being displayed on the Virus Found warning page. - -Accepts a value of true (enabled) to hide the Download button or false (disabled) to display the Download button. By default this feature is set to false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableGuestSignInAcceleration - -Accelerates guest-enabled site collections as well as member-only site collections when the SignInAccelerationDomain parameter is set. - -> [!NOTE] -> If enabled, your identity provider must be capable of authenticating guest users. If it is not, guest users will be unable to log in and access content that was shared with them. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileAnonymousLinkType - -Anonymous access links can allow recipients to only view or view and edit. The value can be set separately for folders and separately for files. - -PARAMVALUE: None | View | Edit - -```yaml -Type: AnonymousLinkType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilePickerExternalImageSearchEnabled - -For Webparts that support inserting images, like for example Image or Hero webpart, the Web search (Powered by Bing) option will be available if enabled (the default). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FolderAnonymousLinkType - -Anonymous access links can allow recipients to only view or view and edit. - -PARAMVALUE: None | View | Edit - -```yaml -Type: AnonymousLinkType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPAddressAllowList - -Configures multiple IP addresses or IP address ranges (IPv4 or IPv6), that are recognized as trusted. - -Use commas to separate multiple IP addresses or IP address ranges. Verify there are no overlapping IP addresses and ensure IP ranges use Classless Inter-Domain Routing (CIDR) notation. For example, 172.16.0.0, 192.168.1.0/27. - -> [!NOTE] -> The IPAddressAllowList parameter only lets administrators set IP addresses or ranges that are recognized as trusted. To only grant access from these IP addresses or ranges, set the IPAddressEnforcement parameter to $true. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPAddressEnforcement - -Allows access from network locations that are defined by an administrator. - -The values are $true and $false. The default value is $false which means the setting is disabled. - -Before the IPAddressEnforcement parameter is set, make sure you add a valid IPv4 or IPv6 address to the IPAddressAllowList parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPAddressWACTokenLifetime - -Allows to set the session timeout. If you are a tenant administrator and you begin IP address enforcement for OneDrive for Business in Office 365, this enforcement automatically activates a tenant parameter IPAddressWACTokenLifetime. The default value is 15 minutes, when IP Address Enforcement is True. - -PARAMVALUE: Int32 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LegacyAuthProtocolsEnabled - -By default this value is set to $True, which means that authentication using legacy protocols is enabled. - -Setting this parameter to $False prevents Office clients using non-modern authentication protocols from accessing SharePoint Online resources. - -- True - Enables Office clients using non-modern authentication protocols (such as, Forms-Based Authentication (FBA) or Identity Client Runtime Library (IDCRL)) to access SharePoint resources. -- False - Prevents Office clients using non-modern authentication protocols from accessing SharePoint Online resources. - -> [!NOTE] -> • This may also prevent third-party apps from accessing SharePoint Online resources. <br/> Also, this will also block apps using the SharePointOnlineCredentials class to access SharePoint Online resources. For additional information about SharePointOnlineCredentials, see SharePointOnlineCredentials class. <br/><br/>• The change is not instant. It might take up to 24 hours to be applied. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationsInOneDriveForBusinessEnabled - -Enables or disables notifications in OneDrive for Business. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationsInSharePointEnabled - -Enables or disables notifications in SharePoint. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyOwnersWhenInvitationsAccepted - -When this parameter is set to $true and when an external user accepts an invitation to a resource in a user's OneDrive for Business, the OneDrive for Business owner is notified by e-mail. - -For additional information about how to configure notifications for external sharing, see Configure notifications for external sharing for OneDrive for Business. - -The valid values are $true and $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotifyOwnersWhenItemsReshared - -When this parameter is set to $true and another user re-shares a document from a user's OneDrive for Business, the OneDrive for Business owner is notified by e-mail. - -For additional information about how to configure notifications for external sharing, see Configure notifications for external sharing for OneDrive for Business. - -The valid values are $true and $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ODBAccessRequests - -Lets administrators set policy on access requests and requests to share in OneDrive for Business. - -The valid values are: - -- On - Users without permission to share can trigger sharing requests to the OneDrive for Business owner when they attempt to share. Also, users without permission to a file or folder can trigger access requests to the OneDrive for Business owner when they attempt to access an item they do not have permissions to. -- Off - Prevent access requests and requests to share on OneDrive for Business. -- Unspecified - Let each OneDrive for Business owner enable or disable access requests and requests to share on their OneDrive. - -```yaml -Type: SharingState -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ODBMembersCanShare - -Lets administrators set policy on re-sharing behavior in OneDrive for Business. - -The valid values are: - -- On - Users with edit permissions can re-share. -- Off - Only OneDrive for Business owner can share. The value of ODBAccessRequests defines whether a request to share gets sent to the owner. -- Unspecified - Let each OneDrive for Business owner enable or disable re-sharing behavior on their OneDrive. - -```yaml -Type: SharingState -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveForGuestsEnabled - -Lets OneDrive for Business creation for administrator managed guest users. Administrator managed Guest users use credentials in the resource tenant to access the resources. - -The valid values are: - -- $true - Administrator managed Guest users can be given OneDrives, provided needed licenses are assigned. -- $false - Administrator managed Guest users can't be given OneDrives as functionality is turned off. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OneDriveStorageQuota - -Sets a default OneDrive for Business storage quota for the tenant. It will be used for new OneDrive for Business sites created. - -A typical use will be to reduce the amount of storage associated with OneDrive for Business to a level below what the License entitles the users. For example, it could be used to set the quota to 10 gigabytes (GB) by default. - -If value is set to 0, the parameter will have no effect. - -If the value is set larger than the Maximum allowed OneDrive for Business quota, it will have no effect. - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrphanedPersonalSitesRetentionPeriod - -Specifies the number of days after a user's Active Directory account is deleted that their OneDrive for Business content will be deleted. - -The value range is in days, between 30 and 3650. The default value is 30. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OwnerAnonymousNotification - -Enables or disables owner anonymous notification. If enabled, an email notification will be sent to the OneDrive for Business owners when an anonymous links are created or changed. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissiveBrowserFileHandlingOverride - -Enables the Permissive browser file handling. By default, the browser file handling is set to Strict. The Strict setting adds headers that force the browser to download certain types of files. The forced download improves security by disallowing the automatic execution of Web content. When the setting is set to Permissive, no headers are added and certain types of files can be executed in the browser instead of download. - -The valid values are: - -- True - Enable the Permissive browser file handling setting. -- False - Keep the default Strict browser file handling setting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreventExternalUsersFromResharing - -Prevents external users from resharing files, folders, and sites that they do not own. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicCdnAllowedFileTypes - -Sets public CDN allowed file types, if the public CDN is enabled. - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PublicCdnEnabled - -Enables or disables the public CDN. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireAnonymousLinksExpireInDays - -Specifies all anonymous links that have been created (or will be created) will expire after the set number of days. - -To remove the expiration requirement, set the value to zero (0). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingAllowedDomainList - -Specifies a list of email domains that is allowed for sharing with the external collaborators. Use the space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -For additional information about how to restrict a domain sharing, see [Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business](https://support.office.com/en-US/article/Restricted-Domains-Sharing-in-Office-365-SharePoint-Online-and-OneDrive-for-Business-5d7589cd-0997-4a00-a2ba-2320ec49c4e9). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingBlockedDomainList - -Specifies a list of email domains that is blocked or prohibited for sharing with the external collaborators. Use space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -For additional information about how to restrict a domain sharing, see [Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business](https://support.office.com/en-US/article/Restricted-Domains-Sharing-in-Office-365-SharePoint-Online-and-OneDrive-for-Business-5d7589cd-0997-4a00-a2ba-2320ec49c4e9). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingDomainRestrictionMode - -Specifies the external sharing mode for domains. - -The valid values are: - -- None -- AllowList - Users will be able to share with external collaborators coming only from that email domain. -- BlockList - Users will be able to share with all external collaborators apart from the ones on the BlockedDomainList. - -For additional information about how to restrict a domain sharing, see [Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business](https://support.office.com/en-US/article/Restricted-Domains-Sharing-in-Office-365-SharePoint-Online-and-OneDrive-for-Business-5d7589cd-0997-4a00-a2ba-2320ec49c4e9). - -```yaml -Type: SharingDomainRestrictionModes -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowPeoplePickerSuggestionsForGuestUsers - -Shows people picker suggestions for guest users. To enable the option to search for existing guest users at Tenant Level, set this parameter to $true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpecialCharactersStateInFileFolderNames - -Permits the use of special characters in file and folder names in SharePoint Online and OneDrive for Business document libraries. - -> [!NOTE] -> The only two characters that can be managed at this time are the # and % characters. - -The valid values are: - -- NoPreference - Support for feature will be enabled by Microsoft on your Office 365 tenant. -- Allowed - Lets the # and % characters in file and folder names in SharePoint Online and OneDrive for Business document libraries. -- Disallowed - Disallows the # and % characters in file and folder names in SharePoint Online and OneDrive for Business document libraries. - -```yaml -Type: SpecialCharactersState -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SyncPrivacyProfileProperties - -This parameter enables the synchronization of privacy profile properties. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseFindPeopleInPeoplePicker - -This feature enables tenant admins to enable ODB and SPO to respect Exchange supports Address Book Policy (ABP) policies in the people picker. - -> [!NOTE] -> When set to $true, users aren't able to share with security groups or SharePoint groups. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserVoiceForFeedbackEnabled - -Enables or disables the User Voice Feedback button. - -PARAMVALUE: $true | $false - -When set to $true, the "Feedback" link will be shown at the bottom of all modern SharePoint Online pages. The "Feedback" link will allow the end user to fill out a feedback form inside SharePoint Online which will then create an entry in the public SharePoint UserVoice topic. - -When set to $false, feedback link will not be shown anymore. It may take up to an hour for a change of this property to be reflected consistently throughout your tenant. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: $true -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomizedExternalSharingServiceUrl - -Specifies a URL that will be appended to the error message that is surfaced when a user is blocked from sharing externally by policy. This URL can be used to direct users to internal portals to request help or to inform them about your organization's policies. An example value is "<https://www.contoso.com/sharingpolicies".> - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentTypeSyncSiteTemplatesList MySites [-ExcludeSiteTemplate] - -By default Content Type Hub will no longer push content types to OneDrive for Business sites (formerly known as MySites). - -In case you want the Content Type Hub to push content types to OneDrive for Business sites, use: `Set-SPOTenant -ContentTypeSyncSiteTemplatesList MySites`. - -When the feature is enabled, the Content Type Hub will push content types to OneDrive for Business sites. - -Once you have enabled Content Type publishing to OneDrive for Business sites, you can disable it later using: `Set-SPOTenant -ContentTypeSyncSiteTemplatesList MySites -ExcludeSiteTemplate`. - -### -ConditionalAccessPolicy - -Please read [Control access from unmanaged devices](https://docs.microsoft.com/sharepoint/control-access-from-unmanaged-devices ) documentation here to understand Conditional Access Policy usage in SharePoint Online. - -PARAMVALUE: AllowFullAccess | AllowLimitedAccess | BlockAccess - -```yaml -Type: SPOConditionalAccessPolicyType -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: AllowFullAccess -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConditionalAccessPolicyErrorHelpLink - -A Link for help when Conditional Access Policy blocks a user. This should be in a valid URL format. A valid URL format that begins with http:// or https://. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowDownloadingNonWebViewableFiles - -This paramater has been deprecated. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCommentsTextOnEmailEnabled - -When this parameter is true, the email notification that a user receives when is mentioned, includes the surrounding document context. Set it to false to disable this feature. - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowEditing - -Prevents users from editing Office files in the browser and copying and pasting Office file contents out of the browser window. - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableAzureADB2BIntegration - -Enables the preview for OneDrive and SharePoint integration with Azure AD B2B. For more information see <http://aka.ms/spo-b2b-integration> - -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LimitedAccessFileType - -Allows users to preview only Office files in the browser. This option increases security, but may be a barrier to user productivity. - -The following parameters can be used with `-ConditionalAccessPolicy AllowLimitedAccess` for both the organization-wide setting and the site-level setting. - -- OfficeOnlineFilesOnly: Allows users to preview only Office files in the browser. This option increases security but may be a barrier to user productivity. -- LimitedAccessFileType WebPreviewableFiles (default): Allows users to preview Office files in the browser. This option optimizes for user productivity but offers less security for files that aren't Office files. **Warning:** This option is known to cause problems with PDF and image file types because they can be required to be downloaded to the end user's machine to render in the browser. Plan the use of this control carefully. Otherwise, your users could be faced with unexpected "Access Denied" errors. -- LimitedAccessFileType OtherFiles: Allows users to download files that can't be previewed, such as .zip and .exe. This option offers less security. - -PARAMVALUE: OfficeOnlineFilesOnly | WebPreviewableFiles | OtherFiles - -```yaml -Type: SPOLimitedAccessFileType -Parameter Sets: ParamSet1 -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: WebPreviewableFiles -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalUserExpirationRequired - -Specifies whether to enable the external user expiration policy, where external users will be expired and removed from the site collection in a given number of days. - -> [!NOTE] -> Once the policy is enabled, expiration values will be set on external users as they join a site collection (via sharing links or via direct access). When the policy is disabled, it will no longer set expiration values on users, but it will not automatically clear expiration values set on existing users. The users can then have their expiration value cleared by a site collection administrator if required. - -The valid values are: -True - Enables the Policy. -False (default) - Disables the policy. - -```yaml -Type: Boolean - -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalUserExpireInDays - -Specifies the number of days before an external user will expire and be removed from the site collection if the policy is enabled. Value can be from 30 to 730 days. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAttestationRequired - -Sets email attestation to required. - -```yaml -Type: Boolean - -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAttestationReAuthDays - -Sets the number of days for email attestation re-authentication. Value can be from 1 to 365 days. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Upgrade-SPOSite](Upgrade-SPOSite.md) - -[Set-SPOSite](Set-SPOSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantCdnEnabled.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantCdnEnabled.md deleted file mode 100644 index ade6f811df..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantCdnEnabled.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spotenantcdnenabled -applicable: SharePoint Online -title: Set-SPOTenantCdnEnabled -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOTenantCdnEnabled - -## SYNOPSIS - -Enables or disables Public content delivery network (CDN) or Private CDN on the tenant level. Requires Tenant administrator permissions. - -## SYNTAX - -```powershell -Set-SPOTenantCdnEnabled [-CdnType <SPOTenantCdnTypeClient>] [-Confirm] [-Enable <Boolean>] [-NoDefaultOrigins] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Enables or disables Public content delivery network (CDN) or Private CDN on the tenant level. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Set-SPOTenantCdnEnabled -CdnType public -Enable $true -``` - -The example enables a CDN. - -## PARAMETERS - -### -CdnType - -Specifies the CDN type. The valid values are: public or private. - -```yaml -Type: SPOTenantCdnTypeClient -Parameter Sets: (All) -Aliases: -Accepted values: Public, Private, Both -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable - -Specifies if the CDN is enabled. - -The valid values are: $True and $False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoDefaultOrigins - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Set-SPOTenantCdnEnabled](Set-SPOTenantCdnEnabled.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantCdnPolicy.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantCdnPolicy.md deleted file mode 100644 index ae740e83de..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantCdnPolicy.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spotenantcdnpolicy -applicable: SharePoint Online -title: Set-SPOTenantCdnPolicy -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOTenantCdnPolicy - -## SYNOPSIS - -Sets the content delivery network (CDN) policies from the tenant level. - -## SYNTAX - -```powershell -Set-SPOTenantCdnPolicy -CdnType <SPOTenantCdnType> -PolicyType <SPOTenantCdnPolicyType> -PolicyValue <String> [<CommonParameters>] -``` - -## DESCRIPTION - -{{Fill in the Description}} - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- - -```powershell -Set-SPOTenantCdnPolicy -CdnType Public -PolicyType IncludeFileExtensions -PolicyValue "CSS,EOT,GIF,ICO,JPEG,JPG,JS,MAP,PNG,SVG,TTF,WOFF,BMP" -``` - -This example sets a CDN to a public type with a policy value of listed extensions. - -### --------------------EXAMPLE 2--------------------- - -```powershell -Set-SPOTenantCdnPolicy -CdnType Public -PolicyType ExcludeRestrictedSiteClassifications -PolicyValue "Confidential,Restricted" -``` - -This example sets a CDN to a public type with a policy value of valid site classifications. - -## PARAMETERS - -### -CdnType - -The CdnType parameter specifies the CDN type. The valid values are Public or Private. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) -Aliases: -Accepted values: Public, Private -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyType - -{{Fill PolicyType Description}} - -```yaml -Type: SPOTenantCdnPolicyType -Parameter Sets: (All) -Aliases: -Accepted values: IncludeFileExtensions, ExcludeRestrictedSiteClassifications, ExcludeIfNoScriptDisabled -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyValue - -{{Fill PolicyValue Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantContentTypeReplicationParameters.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantContentTypeReplicationParameters.md deleted file mode 100644 index 05cdda628e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantContentTypeReplicationParameters.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spotenantcontenttypereplicationparameters -applicable: SharePoint Online -title: Set-SPOTenantContentTypeReplicationParameters -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOTenantContentTypeReplicationParameters - -## SYNOPSIS - -Select content types for replication - -## SYNTAX - -### ReplicateAllContentTypes - -```powershell -Set-SPOTenantContentTypeReplicationParameters [-ReplicateAllContentTypes] [<CommonParameters>] -``` - -### ReplicateSelectedContentTypes - -```powershell -Set-SPOTenantContentTypeReplicationParameters -ReplicatedContentTypes <String[]> [<CommonParameters>] -``` - -## DESCRIPTION - -Before you run the cmdlets, please use 'Connect-SPOService' to connect to SharePoint Online first. -By default, all published content types in primary location will be replicated to satellite. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Set-SPOTenantContentTypeReplicationParameters -ReplicatedContentTypes "ct1","ct2" -``` - -Tenant admin can use this cmdlet to select only some content types only for replicating to overwrite default settings - -### EXAMPLE 2 - -```powershell -Set-SPOTenantContentTypeReplicationParameters -ReplicateAllContentTypes -``` - -Tenant admin can also reset to replicate all the content types. - -## PARAMETERS - -### -ReplicateAllContentTypes - -The ReplicateAllContentTypes parameter specifies whether all content types should be replicated. - -```yaml -Type: SwitchParameter -Parameter Sets: ReplicateAllContentTypes -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReplicatedContentTypes - -{{Fill ReplicatedContentTypes Description}} - -```yaml -Type: String[] -Parameter Sets: ReplicateSelectedContentTypes -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOTenantTaxonomyReplicationParameters](Get-SPOTenantTaxonomyReplicationParameters.md) - -[Set-SPOTenantTaxonomyReplicationParameters](Set-SPOTenantTaxonomyReplicationParameters.md) - -[Get-SPOTenantContentTypeReplicationParameters](Get-SPOTenantContentTypeReplicationParameters.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantSyncClientRestriction.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantSyncClientRestriction.md deleted file mode 100644 index 73470ee3b3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantSyncClientRestriction.md +++ /dev/null @@ -1,295 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spotenantsyncclientrestriction -applicable: SharePoint Online -title: Set-SPOTenantSyncClientRestriction -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOTenantSyncClientRestriction - -## SYNOPSIS - -Controls tenant-wide options and restrictions specific to syncing files. - -## SYNTAX - -### Blocking - -```powershell -Set-SPOTenantSyncClientRestriction [-BlockMacSync] [-DomainGuids <String>] [-Enable] [<CommonParameters>] -``` - -### ReportProblemDialogFeature - -```powershell -Set-SPOTenantSyncClientRestriction -DisableReportProblemDialog <Boolean> [<CommonParameters>] -``` - -### FileExclusion - -```powershell -Set-SPOTenantSyncClientRestriction [-ExcludedFileExtensions <String>] [<CommonParameters>] -``` - -### GrooveBlockOptions - -```powershell -Set-SPOTenantSyncClientRestriction [-GrooveBlockOption <String>] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [Cmdlet Parameter Sets](https://msdn.microsoft.com/library/dd878348(VS.85).aspx). - -You must be a SharePoint Online global administrator to run the cmdlet. - -Requires a valid Connect-SPOService context to identify the tenant. For information on how to connect to the tenant, see [Connect-SPOService](Connect-SPOService.md) - -The **Set-SPOTenantSyncClientRestriction** cmdlet is used to control a variety of tenant-wide administrative settings related to syncing files from OneDrive and SharePoint. You may use it to: - -* Set restrictions on whether users can sync items to non-domain joined machines, control the list of allowed domains, and manage whether Mac clients (which do not support domain join) can sync. - -* Prevents files with specific extensions from being synced. - -* Controls whether users can continue to sync OneDrive for Business libraries with the old OneDrive for Business sync client. - -**Restrict non-domain joined machines from syncing** - -The **Set-SPOTenantSyncClientRestriction** cmdlet can be used to enable the feature for tenancy and set the domain GUIDs in the safe recipients list. When this feature is enabled it can take up to 24 hours for the change to take effect. However, any changes to the safe domains list are reflected within five minutes. - -The **Set-SPOTenantSyncClientRestriction** cmdlet applies both to existing Microsoft OneDrive for Business sync client (Groove.exe) and the Microsoft OneDrive for Business Next Generation Sync Client (OneDrive.exe). OneDrive.exe is the new sync client that will sync both consumer and business accounts. - -> [!IMPORTANT] -> The new OneDrive for Business Next Generation Sync Client lets you connect and sync files from your OneDrive for Business. You can add a work or school account to the new OneDrive for Business sync client and sync all your files in OneDrive to your computer. For more information, see [Improve your OneDrive sync experience](https://go.microsoft.com/fwlink/p/?LinkId=717436). - -When the feature is enabled the following will occur: - -* All OneDrive for Business Sync client requests originating from a domain that is not on the safe recipients list will be blocked. -* All Microsoft OneDrive Mac Sync client and Mac Beta client requests will not be blocked by default. -* Microsoft OneDrive mobile apps are not blocked when this feature is enabled. -* Regardless whether a computer is managed by a device management solution, a sync relationship will not be established unless they are joined to a domain in the Safe Recipient List. -* Any files that have been previously been synced down to your computer will not be deleted. -* When this feature is enabled, please be aware the following upload behavior: - - * New or existing files added to the client will still be uploaded to the server and will not be blocked. - * Regardless if the computer is joined to a domain which is set in the Safe Recipient List. - * Regardless if the computer is joined to a domain which is not set in the Safe Recipient List. - * And for all non-domain joined computers. - -* Microsoft OneDrive for Business sync client prior to version 15.0.4693.1000 will stop syncing existing libraries. - -> [!IMPORTANT] -> In order to explicitly block Microsoft OneDrive client for Mac or OneDrive for Business Next Generation Sync Client on Mac OS X, please run the **Set-SPOTenantSyncClientRestriction** cmdlet with the **BlockMacSync** parameter set to true. For more information about the Next Generation Sync Client for Mac OS X, see [Get started with the new OneDrive sync client on Mac OS X](https://go.microsoft.com/fwlink/?LinkID=717727). -> [!IMPORTANT] -> There is a known OneDrive for Business sync client issue where syncing is being blocked even if a computer is joined to a domain which is set in the Safe Recipient List. To resolve this behavior, obtain the 15.0.4719.1000 version or higher of the sync client, see [May 12, 2015, update for OneDrive for Business](https://support.microsoft.com/en-us/kb/2986244/). -> [!NOTE] -> To determine the version of your Sync client, see [What version of the sync client am I using?](https://support.office.com/en-us/article/Which-version-of-OneDrive-am-I-using-19246eae-8a51-490a-8d97-a645c151f2ba). - -* The latest OneDrive for Business sync client can be downloaded from [Download OneDrive for Windows](https://go.microsoft.com/fwlink/?LinkID=404119&clcid=0x409) or [How to install OneDrive for Business for SharePoint and SharePoint Online](https://go.microsoft.com/fwlink/?LinkID=321300&clcid=0x409). - -> [!IMPORTANT] -> This capability doesn't support Microsoft Azure Active Directory (AD) Joined or Workplace Joined devices. - -For additional information about how to troubleshoot the OneDrive for Business sync client, see [How to switch from an MSI installation of OneDrive for Business (formerly SkyDrive Pro) standalone to a Click-To-Run installation of OneDrive for Business (formerly SkyDrive Pro) standalone](https://go.microsoft.com/fwlink/?LinkId=526386&clcid=0x409). - -**Block specific file extensions from syncing** - -The **Set-SPOTenantSyncClientRestriction** cmdlet can be used to configure a list of file extensions that should not be synced by the OneDrive sync client, such as .PST files. - -Any file extension may be blocked using this feature, but note that it may take up to 24 hours for a change to take affect across all user devices. When this feature is enabled, users syncing any file that is in the exclusion list will see an error message informing them of the block. - -> [!IMPORTANT] -> This feature is only supported by the new OneDrive for Business sync client. To determine the version of your Sync client, see [What version of the sync client am I using?](https://support.office.com/en-us/article/Which-version-of-OneDrive-am-I-using-19246eae-8a51-490a-8d97-a645c151f2ba). - -**Control whether users can use the old OneDrive for Business sync client** - -The **Set-SPOTenantSyncClientRestriction** cmdlet can be used to configure your tenant to allow or disallow users from using the old OneDrive for Business sync client to sync OneDrive for Business libraries. - -This feature is controlled on an opt-out model which lets users to continue syncing with the old sync client, you may choose to opt out of the Groove block. - -When this feature is enabled, the old OneDrive for Business sync client will stop syncing the user's OneDrive contents. OneDrive for Business users who are still using the old OneDrive for Business sync client will see an error message and will be prompted to launch and configure the new OneDrive for Business sync client. If they do not yet have the new client installed, they will have the opportunity to download and install it. - -If you opt out, users will be able to resume syncing with the old OneDrive for Business Sync client. -Note that it may take up to an hour for this change to be reflected. - -> [!NOTE] -> This feature only applies to syncing a user's own OneDrive for Business sites. Team Sites and shared content from other people's OneDrive for Business sites will continue to sync with the old OneDrive for Business sync client. - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- - -```powershell -Set-SPOTenantSyncClientRestriction -Enable -DomainGuids "786548DD-877B-4760-A749-6B1EFBC1190A; 877564FF-877B-4760-A749-6B1EFBC1190A" -``` - -This example enables the feature for the tenancy and adds the domains GUIDs to the safe recipient list. - -### --------------------EXAMPLE 2------------------ - -```powershell -Set-SPOTenantSyncClientRestriction -Enable -DomainGuids "786548DD-877B-4760-A749-6B1EFBC1190A; 877564FF-877B-4760-A749-6B1EFBC1190A" -BlockMacSync:$true -``` - -This example turns on the Block Mac sync functionality. - -### --------------------EXAMPLE 3------------------ - -```powershell -Set-SPOTenantSyncClientRestriction -ExcludedFileExtensions "pptx;docx;xlsx" -``` - -This example blocks syncing of PowerPoint, Word, and Excel file types using the new sync client (OneDrive.exe). - -### --------------------EXAMPLE 4------------------ - -```powershell -Set-SPOTenantSyncClientRestriction -ExcludedFileExtensions "" -``` - -This example clears the ExcludedFileExtension list and lets all file types synced with the new client (OneDrive.exe). - -### --------------------EXAMPLE 5------------------ - -```powershell -Set-SPOTenantSyncClientRestriction -GrooveBlockOption "OptOut" -``` - -This example allows users in a tenant to continue syncing OneDrive for Business libraries with the old OneDrive for Business sync client. - -### --------------------EXAMPLE 6------------------ - -```powershell -Set-SPOTenantSyncClientRestriction -GrooveBlockOption "HardOptIn" -``` - -This example blocks users in a tenant from syncing OneDrive for Business libraries using the old OneDrive for Business sync client. Users will be prompted to upgrade to the new client. - -## PARAMETERS - -### -BlockMacSync - -Block Mac sync clients-- the Beta version and the new sync client (OneDrive.exe). -The values for this parameter are True and False. The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: Blocking -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableReportProblemDialog - -```yaml -Type: Boolean -Parameter Sets: ReportProblemDialogFeature -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainGuids - -Sets the domain GUID to add to the safe recipient list. Requires a minimum of 1 domain GUID. The maximum number of domain GUIDs allowed are 125. - -```yaml -Type: String -Parameter Sets: Blocking -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable - -Enables the feature to block sync originating from domains that are not present in the safe recipients list. - -```yaml -Type: SwitchParameter -Parameter Sets: Blocking -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedFileExtensions - -Blocks certain file types from syncing with the new sync client (OneDrive.exe). - -> [!NOTE] -> It may take up to one hour for changes to take effect. - -```yaml -Type: String -Parameter Sets: FileExclusion -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GrooveBlockOption - -Controls whether or not a tenant's users can sync OneDrive for Business libraries with the old OneDrive for Business sync client. -The valid values are **OptOut, HardOptin, and SoftOptin**. - -```yaml -Type: String -Parameter Sets: GrooveBlockOptions -Aliases: -Accepted values: OptOut, HardOptIn, SoftOptIn -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantTaxonomyReplicationParameters.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantTaxonomyReplicationParameters.md deleted file mode 100644 index 13c1499090..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantTaxonomyReplicationParameters.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spotenanttaxonomyreplicationparameters -applicable: SharePoint Online -title: Set-SPOTenantTaxonomyReplicationParameters -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOTenantTaxonomyReplicationParameters - -## SYNOPSIS - -Select groups for replication - -## SYNTAX - -### ReplicateAllGroups - -```powershell -Set-SPOTenantTaxonomyReplicationParameters [-ReplicateAllGroups] [<CommonParameters>] -``` - -### ReplicateSelectedGroups - -```powershell -Set-SPOTenantTaxonomyReplicationParameters -ReplicatedGroups <String[]> [<CommonParameters>] -``` - -## DESCRIPTION - -Before using this cmdlet, make sure you connect to Sharepoint Online using [Connect-SPOService](Connect-SPOService.md) and the desirable satellite location URL as the -Url parameter. - -By default, all global groups except system/search/people/sitecollection in primary location will be replicated to -satellite. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Set-SPOTenantTaxonomyReplicationParameters -ReplicatedGroups "group1","group2" -``` - -Tenant admin can use this cmdlet to select some groups only for replicating to overwrite default settings. - -### EXAMPLE 2 - -```powershell -Set-SPOTenantTaxonomyReplicationParameters -ReplicateAllGroups -``` - -Tenant admin can also reset to replicate all the groups. - -## PARAMETERS - -### -ReplicateAllGroups - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: ReplicateAllGroups -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReplicatedGroups - -PARAMVALUE: String[] - -```yaml -Type: String[] -Parameter Sets: ReplicateSelectedGroups -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOTenantTaxonomyReplicationParameters](Get-SPOTenantTaxonomyReplicationParameters.md) - -[Get-SPOTenantContentTypeReplicationParameters](Get-SPOTenantContentTypeReplicationParameters.md) - -[Set-SPOTenantContentTypeReplicationParameters](Set-SPOTenantContentTypeReplicationParameters.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUnifiedGroup.md deleted file mode 100644 index 13b4f36a4a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUnifiedGroup.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spounifiedgroup -applicable: SharePoint Online -title: Set-SPOUnifiedGroup -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Set-SPOUnifiedGroup - -## SYNOPSIS - -Sets the Preferred Data Location (PDL) for the specified Office 365 Group. The customer tenant must be multi-geo enabled. - -## SYNTAX - -```powershell -Set-SPOUnifiedGroup [-GroupAlias] <string> [-PreferredDataLocation] <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to set the Preferred Data Location for an Office 365 Group. - -## EXAMPLES - -### Example 1 - -```powershell -Set-SPOUnifiedGroup -GroupAlias EUTeam -PreferredDataLocation EUR -``` - -Sets the PDL for the Office 365 Group named 'EUTeam' to EUR (Europe). - -## PARAMETERS - -### -GroupAlias - -The alias of the Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredDataLocation - -The Preferred Data Location for the Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## NOTES - -## RELATED LINKS - -[Get-SPOUnifiedGroup](https://docs.microsoft.com/powershell/module/sharepoint-online/get-spounifiedgroup) - -[Move a SharePoint site to a different geo location](https://docs.microsoft.com/office365/enterprise/move-sharepoint-between-geo-locations) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUser.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUser.md deleted file mode 100644 index 801117a778..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUser.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spouser -applicable: SharePoint Online -title: Set-SPOUser -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOUser - -## SYNOPSIS - -Configures properties on an existing user. - -## SYNTAX - -```powershell -Set-SPOUser -IsSiteCollectionAdmin <Boolean> -LoginName <String> -Site <SpoSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -Use the `Set-SPOUser` cmdlet to configure properties of an existing user. -That is, to add or remove a user as a SharePoint Online site collection administrator. - -You must have the SharePoint Online Administrator or Global Administrator role to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### --------------------EXAMPLE--------------------- - -```powershell -Set-SPOUser -Site https://contoso.sharepoint.com/sites/marketing -LoginName melissa.kerr@contoso.com -IsSiteCollectionAdmin $true -``` - -This example makes melissa.kerr@contoso.com a SharePoint Online site collection administrator on <https://contoso.sharepoint.com/sites/marketing.> - -## PARAMETERS - -### -IsSiteCollectionAdmin - -Specifies whether the user is a site collection administrator. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoginName - -Specifies the user name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site - -Specifies the full URL of the site collection. It must be in a valid managed path in the company's site. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOUser](Get-SPOUser.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOWebTheme.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOWebTheme.md deleted file mode 100644 index 775b8eb55a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOWebTheme.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/set-spowebtheme -applicable: SharePoint Online -title: Set-SPOWebTheme -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Set-SPOWebTheme - -## SYNOPSIS - -Sets the theme for a SharePoint site. - -## SYNTAX - -```powershell -Set-SPOWebTheme [-Theme] <SpoThemePipeBind> [-Web] <SpoSitePipeBind> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to set the custom theme for a Site - -## EXAMPLES - -### Example 1 - -```powershell - Set-SPOWebTheme -Theme "Custom cyan" -Web https://contoso.sharepoint.com/sites/Contoso1 -``` - -This example sets the "Custom Cyan" theme to the https://contoso.sharepoint.com/sites/Contoso1 site. - -## PARAMETERS - -### -Theme - -Name of the theme or SPOTheme object - -```yaml -Type: SpoThemePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Web -Url of the site - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteContentMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteContentMove.md deleted file mode 100644 index d495c8bdc9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteContentMove.md +++ /dev/null @@ -1,218 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/start-spositecontentmove -applicable: SharePoint Online -title: Start-SPOSiteContentMove -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Start-SPOSiteContentMove - -## SYNOPSIS - -Start a job to move a particular user or group of users to be moved across geo locations relative to the one that executes the command - -## SYNTAX - -### UrlAndDestinationDataLocation - -```powershell -Start-SPOSiteContentMove [-Url] <String> [-DestinationDataLocation] <String> - [[-PreferredMoveBeginDate] <DateTime>] [[-PreferredMoveEndDate] <DateTime>] [[-Reserved] <String>] - [-ValidationOnly] [<CommonParameters>] -``` - -### GroupNameAndDestinationDataLocation - -```powershell -Start-SPOSiteContentMove [-GroupName] <String> [-DestinationDataLocation] <String> - [[-PreferredMoveBeginDate] <DateTime>] [[-PreferredMoveEndDate] <DateTime>] [[-Reserved] <String>] - [-ValidationOnly] [<CommonParameters>] -``` - -### UrlAndDestinationUrl - -```powershell -Start-SPOSiteContentMove [-Url] <String> [-DestinationUrl] <String> [[-PreferredMoveBeginDate] <DateTime>] - [[-PreferredMoveEndDate] <DateTime>] [[-Reserved] <String>] [-ValidationOnly] [<CommonParameters>] -``` - -## DESCRIPTION - -This command starts the information and the status of a move request of a user between sites in a SharePoint Online Multi Geo tenant. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Start-SPOSiteContentMove -Url https://contosoenergy.sharepoint.com/sites/hr -DestinationDataLocation EUR -PreferredMoveBeginDate ((Get-Date).AddHours(1)) -PreferredMoveEndDate ((Get-Date).AddHour(12)) -``` - -Starts the movement of the content on <https://contosoenergy.sharepoint.com/sites/hr> to the EUR destination preferred to start 1 hour ahead from now, until 12 hours to that relative time. - -### EXAMPLE 2 - -```powershell -Start-SPOSiteContentMove -GroupName group@contoso.com -DestinationDataLocation JPN -``` - -Starts the movement of a group of users called group@contoso.com to the JPN location - -### EXAMPLE 3 - -```powershell -Start-SPOSiteContentMove -Url https://contosoenergy.sharepoint.com/sites/hr -DestinationUrl https://contosoenergyEUR.sharepoint.com/sites/hr -``` - -Starts the movement from <https://contosoenergy.sharepoint.com/sites/hr> and set it to the location <https://contosoenergyEUR.sharepoint.com/sites/hr> - -## PARAMETERS - -### -DestinationDataLocation - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: UrlAndDestinationDataLocation, GroupNameAndDestinationDataLocation -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DestinationUrl - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: UrlAndDestinationUrl -Aliases: -Applicable: SharePoint Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupName - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: GroupNameAndDestinationDataLocation -Aliases: -Applicable: SharePoint Online -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMoveBeginDate - -PARAMVALUE: DateTime - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMoveEndDate - -PARAMVALUE: DateTime - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reserved - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url - -Destination URL where the move will take place - -```yaml -Type: String -Parameter Sets: UrlAndDestinationDataLocation, UrlAndDestinationUrl -Aliases: -Applicable: SharePoint Online -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidationOnly - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Start-SPOSiteRename](Start-SPOSiteRename.md) - -[Stop-SPOUserAndContentMove](Stop-SPOUserAndContentMove.md) - -[Get-SPOUserAndContentMoveState](Get-SPOUserAndContentMoveState.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteRename.md b/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteRename.md deleted file mode 100644 index 50421130ce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteRename.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/start-spositerename -applicable: SharePoint Online -title: Start-SPOSiteRename -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Start-SPOSiteRename - -## SYNOPSIS - -> [!NOTE] -> This Feature is part of the Admin Center Preview. If your tenant is not part of the Admin Center Preview, you will get an error when trying to run this cmdlet. - -Starts a job to rename a site. You can change the title, the URL or both of a particular site on a SharePoint Online collection - -## SYNTAX - -```Powershell -Start-SPOSiteRename [-Identity] <SpoSitePipeBind> [-NewSiteUrl] <string> [[-NewSiteTitle] <string>] - [[-SuppressMarketplaceAppCheck]] [[-SuppressWorkflow2013Check]] [[-Reserved] <string>] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION - -This command starts a rename of a site on a SharePoint Online site into a new title, name and url. Also allows you to simulate the run using the -WhatIf parameter as well as -SuppressWorkflow2013Check and SuppressMarketplaceAppCheck switch parameters. - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -$url="https://<tenant>.sharepoint.com/site/samplesite" -$NewSiteUrl="https://<tenant>.sharepoint.com/site/renamed" -Start-SPOSiteRename -Identity $url -NewSiteUrl $NewSiteUrl -``` - -Starts the rename of the SPO site with name "samplesite" to "renamed" without modifying the title. - -### EXAMPLE 2 - -```powershell -$url="https://<tenant>.sharepoint.com/site/samplesite" -$NewSiteUrl="https://<tenant>.sharepoint.com/site/renamed" -$newTitle="New Title" -Start-SPOSiteRename -Identity $url -NewSiteUrl $NewSiteUrl -NewSiteTitle $newTitle -``` - -Starts the rename of the SPO site with name "samplesite" to "renamed" modifying the title of the site to "New Title" - -### EXAMPLE 3 - -```powershell -$url="https://<tenant>.sharepoint.com/site/samplesite" -$NewSiteUrl="https://<tenant>.sharepoint.com/site/renamed" -$newTitle="New Title" -Start-SPOSiteRename -Identity $url -NewSiteUrl $NewSiteUrl -NewSiteTitle $newTitle -SuppressMarketplaceAppCheck -SuppressWorkflow2013Check -WhatIf -``` - -Starts the **simulation** rename of the SPO site with name "samplesite" to "renamed" modifying the title of the site to "New Title" without MarketPlaceAppCheck and without WorkFlow2013Check - -## PARAMETERS - -### -Identity - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewSiteUrl - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: Default -Applicable: SharePoint Online - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewSiteTitle - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressMarketplaceAppCheck - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressWorkflow2013Check - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reserved - -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Simulation of what would happened if you run the script without modifying anything. - -```yaml -Type: String -Parameter Sets: UrlAndDestinationDataLocation, UrlAndDestinationUrl -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Start-SPOUserAndContentMove](Start-SPOUserAndContentMove.md) - -[Stop-SPOUserAndContentMove](Stop-SPOUserAndContentMove.md) - -[Get-SPOUserAndContentMoveState](Get-SPOUserAndContentMoveState.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUnifiedGroupMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUnifiedGroupMove.md deleted file mode 100644 index 1b4b47511a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUnifiedGroupMove.md +++ /dev/null @@ -1,233 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/start-spounifiedgroupmove -applicable: SharePoint Online -title: Start-SPOUnifiedGroupMove -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Start-SPOUnifiedGroupMove - -## SYNOPSIS - -Initiates the move of an Office 365 Group to a new geo location - -## SYNTAX - -```powershell -Start-SPOUnifiedGroupMove [-GroupAlias] <String> [-DestinationDataLocation] <String> [[-PreferredMoveBeginDate] <DateTime>] [[-PreferredMoveEndDate] <DateTime>] [[-Reserved] <String>] [-ValidationOnly] [-Force] [-SuppressMarketplaceAppCheck] [-SuppressWorkflow2013Check] [-SuppressAllWarnings] [-SuppressBcsCheck] [<CommonParameters>] -``` - -## DESCRIPTION - -Initiates the move of an Office 365 Group to a new geo location. The administrator may set a preferred start and end time for the move, however the preferred end time is not guaranteed. The customer tenant must be multi-geo enabled. - -## EXAMPLES - -### Example 1 - -```powershell -Start-SPOUnifiedGroupMove -GroupAlias EUTeam -DestinationDataLocation EUR -``` - -Starts the move of Office 365 Group EUTeam to the Preferred Data Location EUR (Europe). - -## PARAMETERS - -### -DestinationDataLocation - -The destination location for the Office 365 Group move. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - -Force the cmdlet to run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupAlias - -The alias of the Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMoveBeginDate - -The move will likely begin at this specified time. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMoveEndDate - -The move will likely be completed by this specified time, on a best effort basis. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reserved - -{{ Fill Reserved Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressAllWarnings - -Suppress all warning messages. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 9 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressBcsCheck - -Suppress checking of Business Connectivity Services used with the associated Office 365 Group Team site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 10 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressMarketplaceAppCheck - -Suppress checking compatibility of marketplace SharePoint Add-ins deployed to the associated Office 365 Group Team site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 7 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressWorkflow2013Check - -Suppress checking compatibility of SharePoint 2013 Workflows deployed to the associated Office 365 Group Team site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 8 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidationOnly - -This parameter will force the cmdlet to execute only validation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Move a SharePoint site to a different geo location](https://docs.microsoft.com/office365/enterprise/move-sharepoint-between-geo-locations) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUserAndContentMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUserAndContentMove.md deleted file mode 100644 index 71a90fd47f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUserAndContentMove.md +++ /dev/null @@ -1,211 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/start-spouserandcontentmove -applicable: SharePoint Online -title: Start-SPOUserAndContentMove -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Start-SPOUserAndContentMove - -## SYNOPSIS - -Starts the ability to move a user closer to their sites. - -## SYNTAX - -```powershell -Start-SPOUserAndContentMove [-UserPrincipalName] <String> [-DestinationDataLocation] <String> - [[-PreferredMoveBeginDate] <DateTime>] [[-PreferredMoveEndDate] <DateTime>] [-OverwriteOdb] - [[-Notify] <String>] [[-Reserved] <String>] [-ValidationOnly] [<CommonParameters>] -``` - -## DESCRIPTION - -In a multi-geo company, this cmdlet requires a multi-geo tenant to work, and enables the ability to move a user closer to their sites - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Start-SPOUserAndContentMove -UserPrincipalName username@contoso.com -DestinationDataLocation EUR -``` - -This example moves the user username@contoso.com from the current location, example NA to the European Site (EUR) - -### EXAMPLE 2 - -```powershell -Start-SPOUserAndContentMove -UserPrincipalName username@contoso.com -DestinationDataLocation EUR -``` - -This example moves the user username@contoso.com from the current location, example NA to the European Site (EUR) - -### EXAMPLE 3 - -```powershell -Start-SPOUserAndContentMove -UserPrincipalName username@contoso.com -DestinationDataLocation EUR -``` - -This example moves the user username@contoso.com from the current location, example NA to the European Site (EUR) - -## PARAMETERS - -### -DestinationDataLocation - -Defines the new destination of the user that you want to move. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notify - -Makes a SPO notification that the user is being move - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverwriteOdb - -Switch parameter to Overwrite the information into the DB - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMoveBeginDate - -Specifies what is the preferred Date and time to start the job - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMoveEndDate - -Specifies what is the preferred Date and time to stop the job - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reserved - -This parameter will only check for reserved users to be moved near to their sites - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 7 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserPrincipalName - -UserPrincipalName or UPN defined for the specific user on the SPO tenant - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidationOnly - -This parameter will force the cmdlet to execute only validation - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: 8 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Start-SPOSiteRename](Start-SPOSiteRename.md) - -[Start-SPOUserAndContentMove](Start-SPOUserAndContentMove.md) - -[Stop-SPOUserAndContentMove](Stop-SPOUserAndContentMove.md) - -[Get-SPOUserAndContentMoveState](Get-SPOUserAndContentMoveState.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOSiteContentMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOSiteContentMove.md deleted file mode 100644 index f0760ad5cb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOSiteContentMove.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/stop-spositecontentmove -applicable: SharePoint Online -title: Stop-SPOSiteContentMove -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Stop-SPOSiteContentMove - -## SYNOPSIS - -Stops a job to move a particular user or group of users to be moved across geo locations relative to the one that executes the command. - -## SYNTAX - -```powershell -Stop-SPOSiteContentMove [-SourceSiteUrl] <string> [<CommonParameters>] -``` - -## DESCRIPTION - -Use this cmdlet to . - -## EXAMPLES - -### Example 1 - -```powershell -Stop-SPOSiteContentMove -SourceSiteUrl https://contoso.sharepoint.com/sites/Research -``` - -This example stops the move job for the specified site. - -## PARAMETERS - -### -SourceSiteUrl - -{{ Fill SourceSiteUrl Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOUserAndContentMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOUserAndContentMove.md deleted file mode 100644 index ddda0cdae7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOUserAndContentMove.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/stop-spouserandcontentmove -applicable: SharePoint Online -title: Stop-SPOUserAndContentMove -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Stop-SPOUserAndContentMove - -## SYNOPSIS - -In a Multi-Geo company, stops the ability to move a user's content related objects in a SharePoint Online Tenant - -## SYNTAX - -```powershell -Stop-SPOUserAndContentMove [-UserPrincipalName] <String> [<CommonParameters>] -``` - -## DESCRIPTION - -Stops the ability to move a user's content related objects in a Sharepoint Online Tenant - -## EXAMPLES - -### EXAMPLE 1 - -```powershell -Stop-SPOUserAndContentMove -UserPrincipalName "TesIser@contoso.com" -``` - -This example stops the ability to moves the movement of the objects for the "TesIser@contoso.com" in the current Tenant - -### EXAMPLE 2 - -```powershell -Stop-SPOUserAndContentMove "TesIser@contoso.com" -``` - -Equivalent to the one above - -## PARAMETERS - -### -UserPrincipalName - -UserPrincipalName or UPN defined for the specific user on the SPO tenant - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429) - -[SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Start-SPOUserAndContentMove](Start-SPOUserAndContentMove.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Submit-SPOMigrationJob.md b/sharepoint/sharepoint-ps/sharepoint-online/Submit-SPOMigrationJob.md deleted file mode 100644 index 61f9319166..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Submit-SPOMigrationJob.md +++ /dev/null @@ -1,213 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/submit-spomigrationjob -applicable: SharePoint Online -title: Submit-SPOMigrationJob -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Submit-SPOMigrationJob - -## SYNOPSIS - -Cmdlet to submit a new migration job referenced to a previously uploaded package in Azure Blob storage into to a site collection. - -## SYNTAX - -### AzureLocationsInline - -```powershell -Submit-SPOMigrationJob [-TargetWebUrl] <String> [-FileContainerUri] <String> [-PackageContainerUri] <String> - [-AzureQueueUri <String>] -Credentials <CredentialCmdletPipeBind> - [-EncryptionParameters <EncryptionParameters>] [-NoLogFile] [<CommonParameters>] -``` - -### AzureLocationsPipebind - -```powershell -Submit-SPOMigrationJob [-TargetWebUrl] <String> - [-MigrationPackageAzureLocations] <MigrationPackageAzureLocations> -Credentials <CredentialCmdletPipeBind> - [-EncryptionParameters <EncryptionParameters>] [-NoLogFile] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets. - -This cmdlet returns a GUID value which represents the MigrationJobId, or returns an empty GUID if the job was not successfully created. - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Submit-SPOMigrationJob -TargetUrl https://contoso.sharepoint.com/sites/TargetSite/TargetWeb -FileContainerUri "https://migrationstore.blob.core.windows.net/migration-files?sv=2014-02-14&sr=c&sig=THTTJoeGHysxRLgv22j473XYS2blH1YAVIdsfWrPhq8=&se=2015-04-06T05:09:36Z&sp=rl" -PackageContainerUri "https://migrationstore.blob.core.windows.net/migration-package?sv=2014-02-14&sr=c&sig=2PCBJtiXsVWiK5GrY7jBEdyEAwtunQNJLH8uo6I0+Ew=&se=2015-04-06T05:09:37Z&sp=rwl" -``` - -This example creates a new migration job in the target site collection for the web at the URL '<https://contoso.sharepoint.com/sites/TargetSite/TargetWeb'.> The migration job includes information about the file and package metadata Azure Storage containers that are passed into the command. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Submit-SPOMigrationJob -TargetUrl https://contoso.sharepoint.com/sites/TargetSite/TargetWeb -MigrationPackageAzureLocations $azurelocations -``` - -This example creates a new migration job in the target site collection for the web at the URL '<https://contoso.sharepoint.com/sites/TargetSite/TargetWeb'.> The migration job includes information about the file and package metadata Azure Storage containers that are passed into the command. - -## PARAMETERS - -### -AzureQueueUri - -An optional fully qualified URL and SAS token representing the Azure Storage Reporting Queue where import operations will list events during import. - -```yaml -Type: String -Parameter Sets: AzureLocationsInline -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credentials - -Optional credentials of a site collection administrator to use to connect to the site collection. The credentials should supply the username in UPN format (e.g. user@company.onmicrosoft.com). If this property is not set, the current tenant admin credentials from the session's previous call to `Connect-SPOService` will be used to connect to the site collection. - -```yaml -Type: CredentialCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptionParameters - -PARAMVALUE: EncryptionParameters - -```yaml -Type: EncryptionParameters -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileContainerUri - -A fully qualified URL and SAS token representing the Azure Blob Storage container that holds the package content files. - -```yaml -Type: String -Parameter Sets: AzureLocationsInline -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MigrationPackageAzureLocations - -A set of fully qualified URLs and SAS tokens representing the Azure Blob Storage containers that hold the package content and metadata files and an optional Azure Storage Reporting Queue. This object is returned during successful processing of the `Set-SPOMigrationPackageAzureSource` cmdlet. - -```yaml -Type: MigrationPackageAzureLocations -Parameter Sets: AzureLocationsPipebind -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NoLogFile - -Indicates to not create a log file. The default is to create a new CreateMigrationJob log file within the current directory. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PackageContainerUri - -A fully qualified URL and SAS token representing the Azure Blob Storage container that holds the package metadata files. - -```yaml -Type: String -Parameter Sets: AzureLocationsInline -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetWebUrl - -The fully qualified target web URL where the package will be imported into. This must include the same TargetWebURL that was used during `ConvertTo-SPOMigrationTargetedPackage`. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Online.SharePoint.Migration.MigrationPackageAzureLocations - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Test-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Test-SPOSite.md deleted file mode 100644 index 0bbea96e7a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Test-SPOSite.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/test-sposite -applicable: SharePoint Online -title: Test-SPOSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Test-SPOSite - -## SYNOPSIS - -Tests a SharePoint Online site collection. - -## SYNTAX - -```powershell -Test-SPOSite -Identity <SpoSitePipeBind> [-RuleId <Guid>] [-RunAlways] [<CommonParameters>] -``` - -## DESCRIPTION - -The `Test-SPOSite` cmdlet runs one or all site collection health checks on the site collection and its contents. -Tests are intended not to make any changes except in repair mode, which can be initiated by running the `Repair-SPOSite` cmdlet. -This cmdlet reports the rules together with a summary of the results. - -You must be a SharePoint Online global administrator to run the `Test-SPOSite` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Test-SPOSite https://contoso.sharepoint.com/sites/marketing -``` - -This example runs all the site collection health checks on the <https://contoso.sharepoint.com/sites/marketing> site collection. - -## PARAMETERS - -### -Identity - -Specifies the SharePoint Online site collection to test. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RuleId - -Specifies the health check rule to run. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RunAlways - -Displays a message that states the effect of the command instead of executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Get-SPOAppErrors](Get-SPOAppErrors.md) - -[Get-SPOSite](Get-SPOSite.md) - -[New-SPOSite](New-SPOSite.md) - -[Repair-SPOSite](Repair-SPOSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Unregister-SPOHubSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Unregister-SPOHubSite.md deleted file mode 100644 index fa8ee8f305..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Unregister-SPOHubSite.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/unregister-spohubsite -applicable: SharePoint Online -title: Unregister-SPOHubSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Unregister-SPOHubSite - -## SYNOPSIS - -Disables the hub site feature on a site. - -## SYNTAX - -```powershell -Unregister-SPOHubSite [-Identity] <SpoHubSitePipeBind> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Disables the hub site feature on a site so that it is no longer a hub site. Associated sites may still appear associated for up to an hour. If you want to speed up the process, use the Remove-SPOHubSiteAssociation cmdlet to remove the associated sites first. - -> [!NOTE] -> If the site doesn't exist, this cmdlet returns a "File not found" error. - -## EXAMPLES - -### Example 1 - -```powershell -Unregister-SPOHubSite -Identity <guid> -``` - -This example removes a site from the hub site list based on unique hub identifier (<guid>). - -### Example 2 - -```powershell -Unregister-SPOHubSite -Identity https://contoso.sharepoint.com/sites/Marketing -``` - -This example disables the hub feature on the marketing site. - -## PARAMETERS - -### -Identity - -Guid based identifier or URL of the site to disable the hub site feature. If hub site has been already deleted, you will need to use a Guid based identifier to remove the site from the list of hub sites. - -```yaml -Type: SpoHubSitePipeBind -Parameter Sets: (All) -Aliases: HubSite -Applicable: SharePoint Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/sharepoint/sharepoint-ps/sharepoint-online/Update-SPODataEncryptionPolicy.md b/sharepoint/sharepoint-ps/sharepoint-online/Update-SPODataEncryptionPolicy.md deleted file mode 100644 index f33a519ace..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Update-SPODataEncryptionPolicy.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/update-spodataencryptionpolicy -applicable: SharePoint Online -title: Update-SPODataEncryptionPolicy -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Update-SPODataEncryptionPolicy - -## SYNOPSIS - -Updates customer encryption status for a geo tenant. - -## SYNTAX - -```powershell -Update-SPODataEncryptionPolicy [-Identity] <SpoSitePipeBind> [-KeyVaultName] <String> [-KeyName] <String> [-KeyVersion] <Guid> [-KeyType] <CustomerKeyVaultKeyType> [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Update-DataEncryptionPolicy cmdlet to update customer encryption status for your geo tenant. -For more information, see [Controlling your data in Office 365 using Customer Key](https://docs.microsoft.com/en-us/microsoft-365/compliance/controlling-your-data-using-customer-key) - -## EXAMPLES - -### Example 1 - -```powershell -Update-SPODataEncryptionPolicy -Identity https://contoso-admin.sharepoint.com -KeyVaultName <ReplacementKeyVaultName> -KeyName <ReplacementKeyName> -KeyVersion <ReplacementKeyVersion> -KeyType Primary -``` - -This example updates the DEP used with SharePoint Online and OneDrive for Business to start using the new key - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the URL of the admin site collection. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -KeyName - -The name of the key - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeyType - -The type of the key, possible values are - -- Primary -- Secondary - -```yaml -Type: CustomerKeyVaultKeyType -Parameter Sets: (All) -Aliases: -Accepted values: Primary, Secondary - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeyVaultName - -The name of the Azure Key Vault Name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeyVersion - -The version of the key - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### Microsoft.Online.SharePoint.PowerShell.SpoSitePipeBind - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Update-UserType.md b/sharepoint/sharepoint-ps/sharepoint-online/Update-UserType.md deleted file mode 100644 index 6c84c7cb9a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Update-UserType.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/update-usertype -applicable: SharePoint Online -title: Update-UserType -schema: 2.0.0 -author: -ms.author: -ms.reviewer: ---- - -# Update-UserType - -## SYNOPSIS - -Updates the specified user's UserType value from Azure AD. - -## SYNTAX - -```powershell -Update-UserType [-LoginName] <String> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet retrieves the UserType value of the specified user and updates the UserType across all SharePoint Online sites in the Office 365 tenant. This can be used, for example, to convert a Guest user to a standard (Member) user if the user's UserType was previously updated in Azure AD. - -## EXAMPLES - -### Example 1 - -```powershell -Update-UserType -LoginName jdoe@contoso.com -``` - -Updates the jdoe@contoso.com's UserType on all SharePoint Online sites in the tenant based on the UserType value in Azure AD. - -## PARAMETERS - -### -LoginName - -The login name of the target user to update across SharePoint Online. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Properties of an Azure Active Directory B2B collaboration user](https://docs.microsoft.com/azure/active-directory/b2b/user-properties) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Upgrade-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Upgrade-SPOSite.md deleted file mode 100644 index 3a3ceb72ae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Upgrade-SPOSite.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/upgrade-sposite -applicable: SharePoint Online -title: Upgrade-SPOSite -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Upgrade-SPOSite - -## SYNOPSIS - -Starts the upgrade process on a site collection. - -## SYNTAX - -```powershell -Upgrade-SPOSite [-Confirm] -Identity <SpoSitePipeBind> [-NoEmail] [-QueueOnly] [-VersionUpgrade] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -The `Upgrade-SPOSite` cmdlet activates the upgrade process for the specified SharePoint Online site collection. -This cmdlet can also be used to resume failed upgrades. - -When upgrade is initiated, it can either be a build-to-build or version-to-version upgrade. -The default is build-to-build upgrade. -When in version-to-version upgrade, site collection health checks are first run in repair mode to ensure that the site collection can be upgraded successfully. - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at <https://go.microsoft.com/fwlink/p/?LinkId=251832> (<https://go.microsoft.com/fwlink/p/?LinkId=251832).> - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- - -```powershell -Upgrade-SPOSite -Identity https://contoso.sharepoint.com/sites/marketing -``` - -Example 1 runs a build-to-build upgrade of the existing site collection <https://contoso.sharepoint.com/sites/marketing.> The CompatibilityLevel property associated with the site collection is not changed by this operation. For more information about CompatibilityLevel, see `New-SPOSite`. - -### -----------------------EXAMPLE 2----------------------------- - -```powershell -Upgrade-SPOSite -Identity https://contoso.sharepoint.com/sites/marketing -VersionUpgrade -``` - -Example 2 runs a version-to-version upgrade of the existing site collection <https://contoso.sharepoint.com/sites/marketing.> The CompatibilityLevel property associated with the site collection is changed to a value of SharePoint 2013 by this operation. For more information about CompatibilityLevel, see `New-SPOSite`. - -## PARAMETERS - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -Specifies the SharePoint Online site collection to upgrade. - -```yaml -Type: SpoSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NoEmail - -Specifies that the system not send the requester and site collection administrators a notification e-mail message at the end of the upgrade process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueueOnly - -Adds the site collection to the upgrade queue. The upgrade does not occur immediately. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VersionUpgrade - -Specifies whether to perform a version-to-version upgrade on the site collection. When this parameter is set, it internally triggers any available build-to-build upgrade associated with the current site collection operating mode and continues with version-to-version upgrade. When this parameter is not set, it triggers only build-to-build upgrade on the site collection. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Getting started with SharePoint Online Management Shell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) - -[Request-SPOUpgradeEvaluationSite](Request-SPOUpgradeEvaluationSite.md) - -[New-SPOSite](New-SPOSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Verify-SPOTenantOrgRelation.md b/sharepoint/sharepoint-ps/sharepoint-online/Verify-SPOTenantOrgRelation.md deleted file mode 100644 index e014fdc991..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/Verify-SPOTenantOrgRelation.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Online.SharePoint.PowerShell -online version: https://docs.microsoft.com/powershell/module/sharepoint-online/Verify-SPOTenantOrgRelation -applicable: SharePoint Online -title: Verify-SPOTenantOrgRelation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- -# Verify-SPOTenantOrgRelation - -## SYNOPSIS - -{{ Fill in the Synopsis }} - -## SYNTAX - -```powershell -Verify-SPOTenantOrgRelation [-Scenario] <OrgRelationScenario> [-PartnerRole] <OrgRelationRole> [-PartnerCompanyId] <Guid> [-PartnerInstanceId <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION - -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 - -```powershell -PS C:\> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -PartnerCompanyId - -{{ Fill PartnerCompanyId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerInstanceId - -{{ Fill PartnerInstanceId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartnerRole - -{{ Fill PartnerRole Description }} - -```yaml -Type: OrgRelationRole -Parameter Sets: (All) -Aliases: -Accepted values: None, Source, Target - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scenario - -{{ Fill Scenario Description }} - -```yaml -Type: OrgRelationScenario -Parameter Sets: (All) -Aliases: -Accepted values: None, MnA - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md b/sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md deleted file mode 100644 index 36014c88d1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md +++ /dev/null @@ -1,518 +0,0 @@ ---- -Module Name: SharePoint Online PowerShell -Module Guid: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -title: sharepoint-online -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# SharePoint Online PowerShell - -## Description - -The following cmdlet references are for SharePoint Online. - -## sharepoint-online Cmdlets - -### [Add-SPOGeoAdministrator](Add-SPOGeoAdministrator.md) - -{{Manually Enter Add-SPOGeoAdministrator Description Here}} - -### [Add-SPOHubSiteAssociation](Add-SPOHubSiteAssociation.md) - -{{Manually Enter Add-SPOHubSiteAssociation Description Here}} - -### [Add-SPOOrgAssetsLibrary](Add-SPOOrgAssetsLibrary.md) - -{{Manually Enter Add-SPOOrgAssetsLibrary Description Here}} - -### [Add-SPOSiteDesign](Add-SPOSiteDesign.md) - -{{Manually Enter Add-SPOSiteDesign Description Here}} - -### [Add-SPOSiteDesign](Add-SPOSiteDesignTask.md) - -{{Manually Enter Add-SPOSiteDesignTask Description Here}} - -### [Add-SPOSiteScript](Add-SPOSiteScript.md) - -{{Manually Enter Add-SPOSiteScript Description Here}} - -### [Add-SPOTenantCdnOrigin](Add-SPOTenantCdnOrigin.md) - -{{Manually Enter Add-SPOTenantCdnOrigin Description Here}} - -### [Add-SPOTheme](Add-SPOTheme.md) - -{{Manually Enter Add-SPOTheme Description Here}} - -### [Add-SPOUser](Add-SPOUser.md) - -{{Manually Enter Add-SPOUser Description Here}} - -### [Approve-SPOTenantServicePrincipalPermissionRequest](Approve-SPOTenantServicePrincipalPermissionRequest.md) - -{{Manually Enter Approve-SPOTenantServicePrincipalPermissionRequest Description Here}} - -### [Connect-SPOService](Connect-SPOService.md) - -{{Manually Enter Connect-SPOService Description Here}} - -### [Deny-SPOTenantServicePrincipalPermissionRequest](Deny-SPOTenantServicePrincipalPermissionRequest.md) - -{{Manually Enter Deny-SPOTenantServicePrincipalPermissionRequest Description Here}} - -### [Disable-SPOTenantServicePrincipal](Disable-SPOTenantServicePrincipal.md) - -{{Manually Enter Connect-SPOService Description Here}} - -### [Disconnect-SPOService](Disconnect-SPOService.md) - -{{Manually Enter Disconnect-SPOService Description Here}} - -### [Enable-SPOTenantServicePrincipal](Enable-SPOTenantServicePrincipal.md) - -{{Manually Enter Enable-SPOTenantServicePrincipal Description Here}} - -### [Enable-SPOCommSite](Enable-SPOCommSite.md) - -{{Manually Enter Enable-SPOCommSite Description Here}} - -### [Export-SPOUserInfo](Export-SPOUserInfo.md) - -{{Manually Enter Export-SPOUserInfo Description Here}} - -### [Get-SPOAppErrors](Get-SPOAppErrors.md) - -{{Manually Enter Get-SPOAppErrors Description Here}} - -### [Get-SPOAppInfo](Get-SPOAppInfo.md) - -{{Manually Enter Get-SPOAppInfo Description Here}} - -### [Get-SPOCrossGeoMovedUsers](Get-SPOCrossGeoMovedUsers.md) - -{{Manually Enter Get-SPOCrossGeoMovedUsers Description Here}} - -### [Get-SPOCrossGeoUsers](Get-SPOCrossGeoUsers.md) - -{{Manually Enter Get-SPOCrossGeoUsers Description Here}} - -### [Get-SPODataConnectionSetting](Get-SPODataConnectionSetting.md) - -{{Manually Enter Get-SPODataConnectionSetting Description Here}} - -### [Get-SPODataConnectionSettingMetadata](Get-SPODataConnectionSettingMetadata.md) - -{{Manually Enter Get-SPODataConnectionSettingMetadata Description Here}} - -### [Get-SPODeletedSite](Get-SPODeletedSite.md) - -{{Manually Enter Get-SPODeletedSite Description Here}} - -### [Get-SPOExternalUser](Get-SPOExternalUser.md) - -{{Manually Enter Get-SPOExternalUser Description Here}} - -### [Get-SPOGeoAdministrator](Get-SPOGeoAdministrator.md) - -{{Manually Enter Get-SPOGeoAdministrators Description Here}} - -### [Get-SPOGeoMoveCompatibilityStatus](Get-SPOGeoMoveCompatibilityStatus.md) - -{{Manually Enter Get-SPOGeoMoveCompatibilityStatus Description Here}} - -### [Get-SPOGeoStorageQuota](Get-SPOGeoStorageQuota.md) - -{{Manually Enter Get-SPOGeoStorageQuota Description Here}} - -### [Get-SPOHideDefaultThemes](Get-SPOHideDefaultThemes.md) - -{{Manually Enter Get-SPOHideDefaultThemes Description Here}} - -### [Get-SPOHubSite](Get-SPOHubSite.md) - -{{Manually Enter Get-SPOHubSite Description Here}} - -### [Get-SPOMigrationJobProgress](Get-SPOMigrationJobProgress.md) - -{{Manually Enter Get-SPOMigrationJobProgress Description Here}} - -### [Get-SPOMigrationJobStatus](Get-SPOMigrationJobStatus.md) - -{{Manually Enter Get-SPOMigrationJobStatus Description Here}} - -### [Get-SPOOrgAssetsLibrary](Get-SPOOrgAssetsLibrary.md) - -{{Manually Enter Get-SPOOrgAssetsLibrary Description Here}} - -### [Get-SPOPublicCdnOrigins](Get-SPOPublicCdnOrigins.md) - -{{Manually Enter Get-SPOPublicCdnOrigins Description Here}} - -### [Get-SPOSite](Get-SPOSite.md) - -{{Manually Enter Get-SPOSite Description Here}} - -### [Get-SPOSiteContentMoveState](Get-SPOSiteContentMoveState.md) - -{{Manually Enter Get-SPOSiteContentMoveState Description Here}} - -### [Get-SPOSiteDesign](Get-SPOSiteDesign.md) - -{{Manually Enter Get-SPOSiteDesign Description Here}} - -### [Get-SPOSiteDesignRun](Get-SPOSiteDesignRun.md) - -{{Manually Enter Get-SPOSiteDesignRights Description Here}} - -### [Get-SPOSiteDesignRunStatus](Get-SPOSiteDesignRunStatus.md) - -{{Manually Enter Get-SPOSiteDesignRights Description Here}} - -### [Get-SPOSiteDesignRights](Get-SPOSiteDesignRights.md) - -{{Manually Enter Get-SPOSiteDesignRights Description Here}} - -### [Get-SPOSiteDesignTask](Get-SPOSiteDesignTask.md) - -{{Manually Enter Add-SPOSiteDesign Description Here}} - -### [Get-SPOSiteGroup](Get-SPOSiteGroup.md) - -{{Manually Enter Get-SPOSiteGroup Description Here}} - -### [Get-SPOSiteScript](Get-SPOSiteScript.md) - -{{Manually Enter Get-SPOSiteScript Description Here}} - -### [Get-SPOSiteScriptFromList](Get-SPOSiteScriptFromList.md) - -{{Manually Enter Get-SPOSiteScript Description Here}} - -### [Get-SPOTenant](Get-SPOTenant.md) - -{{Manually Enter Get-SPOTenant Description Here}} - -### [Get-SPOTenantCdnEnabled](Get-SPOTenantCdnEnabled.md) - -{{Manually Enter Get-SPOTenantCdnEnabled Description Here}} - -### [Get-SPOTenantCdnOrigins](Get-SPOTenantCdnOrigins.md) - -{{Manually Enter Get-SPOTenantCdnOrigins Description Here}} - -### [Get-SPOTenantCdnPolicies](Get-SPOTenantCdnPolicies.md) - -{{Manually Enter Get-SPOTenantCdnPolicies Description Here}} - -### [Get-SPOTenantContentTypeReplicationParameters](Get-SPOTenantContentTypeReplicationParameters.md) - -{{Manually Enter Get-SPOTenantContentTypeReplicationParameters Description Here}} - -### [Get-SPOTenantLogEntry](Get-SPOTenantLogEntry.md) - -{{Manually Enter Get-SPOTenantLogEntry Description Here}} - -### [Get-SPOTenantLogLastAvailableTimeInUtc](Get-SPOTenantLogLastAvailableTimeInUtc.md) - -{{Manually Enter Get-SPOTenantLogLastAvailableTimeInUtc Description Here}} - -### [Get-SPOTenantServicePrincipalPermissionGrants](Get-SPOTenantServicePrincipalPermissionGrants.md) - -{{Manually Enter Get-SPOTenantServicePrincipalPermissionGrants Description Here}} - -### [Get-SPOTenantServicePrincipalPermissionRequests](Get-SPOTenantServicePrincipalPermissionRequests.md) - -{{Manually Enter Get-SPOTenantServicePrincipalPermissionRequests Description Here}} - -### [Get-SPOTenantSyncClientRestriction](Get-SPOTenantSyncClientRestriction.md) - -{{Manually Enter Get-SPOTenantSyncClientRestriction Description Here}} - -### [Get-SPOTenantTaxonomyReplicationParameters](Get-SPOTenantTaxonomyReplicationParameters.md) - -{{Manually Enter Get-SPOTenantTaxonomyReplicationParameters Description Here}} - -### [Get-SPOTheme](Get-SPOTheme.md) - -{{Manually Enter Get-SPOTheme Description Here}} - -### [Get-SPOUser](Get-SPOUser.md) - -{{Manually Enter Get-SPOUser Description Here}} - -### [Get-SPOUserAndContentMoveState](Get-SPOUserAndContentMoveState.md) - -{{Manually Enter Get-SPOUserAndContentMoveState Description Here}} - -### [Get-SPOUserOneDriveLocation](Get-SPOUserOneDriveLocation.md) - -{{Manually Enter Get-SPOUserOneDriveLocation Description Here}} - -### [Get-SPOWebTemplate](Get-SPOWebTemplate.md) - -{{Manually Enter Get-SPOWebTemplate Description Here}} - -### [Grant-SPOHubSiteRights](Grant-SPOHubSiteRights.md) - -{{Manually Enter Grant-SPOHubSiteRights Description Here}} - -### [Grant-SPOSiteDesignRights](Grant-SPOSiteDesignRights.md) - -{{Manually Enter Grant-SPOSiteDesignRights Description Here}} - -### [Invoke-SPOMigrationEncryptUploadSubmit](Invoke-SPOMigrationEncryptUploadSubmit.md) - -{{Manually Enter Invoke-SPOMigrationEncryptUploadSubmit Description Here}} - -### [Invoke-SPOSiteDesign](Invoke-SPOSiteDesign.md) - -{{Manually Enter Invoke-SPOSiteDesign Description Here}} - -### [Invoke-SPOSiteSwap](Invoke-SPOSiteSwap.md) - -{{Manually Enter Invoke-SPOSiteSwap Description Here}} - -### [New-SPODataConnectionSetting](New-SPODataConnectionSetting.md) - -{{Manually Enter New-SPODataConnectionSetting Description Here}} - -### [New-SPOMigrationEncryptionParameters](New-SPOMigrationEncryptionParameters.md) - -{{Manually Enter New-SPOMigrationEncryptionParameters Description Here}} - -### [New-SPOMigrationPackage](New-SPOMigrationPackage.md) - -{{Manually Enter New-SPOMigrationPackage Description Here}} - -### [New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy](New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy.md) - -{{Manually Enter New-SPOnlineApplicationPrincipalManagementServiceApplicationProxy Description Here}} - -### [New-SPOPublicCdnOrigin](New-SPOPublicCdnOrigin.md) - -{{Manually Enter New-SPOPublicCdnOrigin Description Here}} - -### [New-SPOSdnProvider](New-SPOSdnProvider.md) - -{{Manually Enter New-SPOSdnProvider Description Here}} - -### [New-SPOSite](New-SPOSite.md) - -{{Manually Enter New-SPOSite Description Here}} - -### [New-SPOSiteGroup](New-SPOSiteGroup.md) - -{{Manually Enter New-SPOSiteGroup Description Here}} - -### [Register-SPOHubSite](Register-SPOHubSite.md) - -{{Manually Enter Register-SPOHubSite Description Here}} - -### [Remove-SPODataConnectionSetting](Remove-SPODataConnectionSetting.md) - -{{Manually Enter Remove-SPODataConnectionSetting Description Here}} - -### [Remove-SPODeletedSite](Remove-SPODeletedSite.md) - -{{Manually Enter Remove-SPODeletedSite Description Here}} - -### [Remove-SPOExternalUser](Remove-SPOExternalUser.md) - -{{Manually Enter Remove-SPOExternalUser Description Here}} - -### [Remove-SPOGeoAdministrator](Remove-SPOGeoAdministrator.md) - -{{Manually Enter Remove-SPOGeoAdministrator Description Here}} - -### [Remove-SPOHubSiteAssociation](Remove-SPOHubSiteAssociation.md) - -{{Manually Enter Remove-SPOHubSiteAssociation Description Here}} - -### [Remove-SPOMigrationJob](Remove-SPOMigrationJob.md) - -{{Manually Enter Remove-SPOMigrationJob Description Here}} - -### [Remove-SPOOrgAssetsLibrary](Remove-SPOOrgAssetsLibrary.md) - -{{Manually Enter Remove-SPOOrgAssetsLibrary Description Here}} - -### [Remove-SPOPublicCdnOrigin](Remove-SPOPublicCdnOrigin.md) - -{{Manually Enter Remove-SPOPublicCdnOrigin Description Here}} - -### [Remove-SPOSdnProvider](Remove-SPOSdnProvider.md) - -{{Manually Enter Remove-SPOSdnProvider Description Here}} - -### [Remove-SPOSite](Remove-SPOSite.md) - -{{Manually Enter Remove-SPOSite Description Here}} - -### [Remove-SPOSiteDesign](Remove-SPOSiteDesign.md) - -{{Manually Enter Remove-SPOSiteDesign Description Here}} - -### [Remove-SPOSiteDesignTask](Remove-SPOSiteDesignTask.md) - -{{Manually Enter Remove-SPOSiteDesign Description Here}} - -### [Remove-SPOSiteGroup](Remove-SPOSiteGroup.md) - -{{Manually Enter Remove-SPOSiteGroup Description Here}} - -### [Remove-SPOSiteScript](Remove-SPOSiteScript.md) - -{{Manually Enter Remove-SPOSiteScript Description Here}} - -### [Remove-SPOTenantCdnOrigin](Remove-SPOTenantCdnOrigin.md) - -{{Manually Enter Remove-SPOTenantCdnOrigin Description Here}} - -### [Remove-SPOTenantSyncClientRestriction](Remove-SPOTenantSyncClientRestriction.md) - -{{Manually Enter Remove-SPOTenantSyncClientRestriction Description Here}} - -### [Remove-SPOTheme](Remove-SPOTheme.md) - -{{Manually Enter Remove-SPOTheme Description Here}} - -### [Remove-SPOUser](Remove-SPOUser.md) - -{{Manually Enter Remove-SPOUser Description Here}} - -### [Repair-SPOSite](Repair-SPOSite.md) - -{{Manually Enter Repair-SPOSite Description Here}} - -### [Request-SPOPersonalSite](Request-SPOPersonalSite.md) - -{{Manually Enter Request-SPOPersonalSite Description Here}} - -### [Request-SPOUpgradeEvaluationSite](Request-SPOUpgradeEvaluationSite.md) - -{{Manually Enter Request-SPOUpgradeEvaluationSite Description Here}} - -### [Restore-SPODeletedSite](Restore-SPODeletedSite.md) - -{{Manually Enter Restore-SPODeletedSite Description Here}} - -### [Revoke-SPOHubSiteRights](Revoke-SPOHubSiteRights.md) - -{{Manually Enter Revoke-SPOHubSiteRights Description Here}} - -### [Revoke-SPOSiteDesignRights](Revoke-SPOSiteDesignRights.md) - -{{Manually Enter Revoke-SPOSiteDesignRights Description Here}} - -### [Revoke-SPOTenantServicePrincipalPermission](Revoke-SPOTenantServicePrincipalPermission.md) - -{{Manually Enter Revoke-SPOTenantServicePrincipalPermission Description Here}} - -### [Revoke-SPOUserSession](Revoke-SPOUserSession.md) - -{{Manually Enter Revoke-SPOUserSession Description Here}} - -### [Set-SPODataConnectionSetting](Set-SPODataConnectionSetting.md) - -{{Manually Enter Set-SPODataConnectionSetting Description Here}} - -### [Set-SPODataConnectionSettingMetadata](Set-SPODataConnectionSettingMetadata.md) - -{{Manually Enter Set-SPODataConnectionSettingMetadata Description Here}} - -### [Set-SPOGeoStorageQuota](Set-SPOGeoStorageQuota.md) - -{{Manually Enter Set-SPOGeoStorageQuota Description Here}} - -### [Set-SPOHideDefaultThemes](Set-SPOHideDefaultThemes.md) - -{{Manually Enter Set-SPOHideDefaultThemes Description Here}} - -### [Set-SPOHubSite](Set-SPOHubSite.md) - -{{Manually Enter Set-SPOHubSite Description Here}} - -### [Set-SPOMigrationPackageAzureSource](Set-SPOMigrationPackageAzureSource.md) - -{{Manually Enter Set-SPOMigrationPackageAzureSource Description Here}} - -### [Set-SPOOrgAssetsLibrary](Set-SPOOrgAssetsLibrary.md) - -{{Manually Enter Set-SPOOrgAssetsLibrary Description Here}} - -### [Set-SPOSite](Set-SPOSite.md) - -{{Manually Enter Set-SPOSite Description Here}} - -### [Set-SPOSiteDesign](Set-SPOSiteDesign.md) - -{{Manually Enter Set-SPOSiteDesign Description Here}} - -### [Set-SPOSiteGroup](Set-SPOSiteGroup.md) - -{{Manually Enter Set-SPOSiteGroup Description Here}} - -### [Set-SPOSiteScript](Set-SPOSiteScript.md) - -{{Manually Enter Set-SPOSiteScript Description Here}} - -### [Set-SPOTenant](Set-SPOTenant.md) - -{{Manually Enter Set-SPOTenant Description Here}} - -### [Set-SPOTenantCdnEnabled](Set-SPOTenantCdnEnabled.md) - -{{Manually Enter Set-SPOTenantCdnEnabled Description Here}} - -### [Set-SPOTenantCdnPolicy](Set-SPOTenantCdnPolicy.md) - -{{Manually Enter Set-SPOTenantCdnPolicy Description Here}} - -### [Set-SPOTenantContentTypeReplicationParameters](Set-SPOTenantContentTypeReplicationParameters.md) - -{{Manually Enter Set-SPOTenantContentTypeReplicationParameters Description Here}} - -### [Set-SPOTenantSyncClientRestriction](Set-SPOTenantSyncClientRestriction.md) - -{{Manually Enter Set-SPOTenantSyncClientRestriction Description Here}} - -### [Set-SPOTenantTaxonomyReplicationParameters](Set-SPOTenantTaxonomyReplicationParameters.md) - -{{Manually Enter Set-SPOTenantTaxonomyReplicationParameters Description Here}} - -### [Set-SPOUser](Set-SPOUser.md) - -{{Manually Enter Set-SPOUser Description Here}} - -### [Start-SPOSiteContentMove](Start-SPOSiteContentMove.md) - -{{Manually Enter Start-SPOSiteContentMove Description Here}} - -### [Start-SPOUserAndContentMove](Start-SPOUserAndContentMove.md) - -{{Manually Enter Start-SPOUserAndContentMove Description Here}} - -### [Stop-SPOUserAndContentMove](Stop-SPOUserAndContentMove.md) - -{{Manually Enter Stop-SPOUserAndContentMove Description Here}} - -### [Submit-SPOMigrationJob](Submit-SPOMigrationJob.md) - -{{Manually Enter Submit-SPOMigrationJob Description Here}} - -### [Test-SPOSite](Test-SPOSite.md) - -{{Manually Enter Test-SPOSite Description Here}} - -### [Unregister-SPOHubSite](Unregister-SPOHubSite.md) - -{{Manually Enter Unregister-SPOHubSite Description Here}} - -### [Upgrade-SPOSite](Upgrade-SPOSite.md) - -{{Manually Enter Upgrade-SPOSite Description Here}} - -<!--updated March 6, 2018; moved cmdlets from https://docs.microsoft.com/sharepoint/dev/declarative-customization/site-design-powershell; added items from TOC that were missing on this page--> diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPAlert.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPAlert.md deleted file mode 100644 index 036c7627bd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPAlert.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpalert -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Add-PnPAlert ---- - -# Add-PnPAlert - -## SYNOPSIS -Adds an alert for a user to a list - -## SYNTAX - -```powershell -Add-PnPAlert -List <ListPipeBind> - [-Title <String>] - [-User <UserPipeBind>] - [-DeliveryMethod <AlertDeliveryChannel>] - [-ChangeType <AlertEventType>] - [-Frequency <AlertFrequency>] - [-Filter <AlertFilter>] - [-Time <DateTime>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPAlert -List "Demo List" -``` - -Adds a new alert to the "Demo List" for the current user. - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPAlert -Title "Daily summary" -List "Demo List" -Frequency Daily -ChangeType All -Time (Get-Date -Hour 11 -Minute 00 -Second 00) -``` - -Adds a daily alert for the current user at the given time to the "Demo List". Note: a timezone offset might be applied so please verify on your tenant that the alert indeed got the right time. - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPAlert -Title "Alert for user" -List "Demo List" -User "i:0#.f|membership|Alice@contoso.onmicrosoft.com" -``` - -Adds a new alert for user "Alice" to the "Demo List". Note: Only site owners and admins are permitted to set alerts for other users. - -## PARAMETERS - -### -ChangeType -Alert change type - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AlertEventType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DeliveryMethod -Alert delivery method - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AlertDeliveryChannel -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Filter -Alert filter - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AlertFilter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Frequency -Alert frequency - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AlertFrequency -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Title or Url of the list. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Time -Alert time (if frequency is not immediate) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: DateTime -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -Alert title - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -User -User to create the alert for (User ID, login name or actual User object). Skip this parameter to create an alert for the current user. Note: Only site owners can create alerts for other users. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: UserPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.AlertCreationInformation - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApp.md deleted file mode 100644 index ee455eff4f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApp.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpapp -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Add-PnPApp ---- - -# Add-PnPApp - -## SYNOPSIS -Add/uploads an available app to the app catalog - -## SYNTAX - -### Add only -```powershell -Add-PnPApp -Path <String> - [-Scope <AppCatalogScope>] - [-Overwrite [<SwitchParameter>]] - [-Timeout <Int>] - [-Connection <SPOnlineConnection>] -``` - -### Add and Publish -```powershell -Add-PnPApp -Path <String> - -Publish [<SwitchParameter>] - [-SkipFeatureDeployment [<SwitchParameter>]] - [-Scope <AppCatalogScope>] - [-Overwrite [<SwitchParameter>]] - [-Timeout <Int>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPApp -Path ./myapp.sppkg -``` - -This will upload the specified app package to the app catalog - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPApp -Path ./myapp.sppkg -Publish -``` - -This will upload the specified app package to the app catalog and deploy/trust it at the same time. - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPApp -Path ./myapp.sppkg -Scope Site -Publish -``` - -This will upload the specified app package to the site collection app catalog and deploy/trust it at the same time. - -## PARAMETERS - -### -Overwrite -Overwrites the existing app package if it already exists - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Specifies the Id or an actual app metadata instance - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: Add only, Add and Publish - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Publish -This will deploy/trust an app into the app catalog - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: Add and Publish - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipFeatureDeployment - - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: Add and Publish - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Timeout -Specifies the timeout in seconds. Defaults to 200. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.ALM.AppMetadata - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApplicationCustomizer.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApplicationCustomizer.md deleted file mode 100644 index 75bfdfd824..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApplicationCustomizer.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpapplicationcustomizer -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Add-PnPApplicationCustomizer ---- - -# Add-PnPApplicationCustomizer - -## SYNOPSIS -Adds a SharePoint Framework client side extension application customizer - -## SYNTAX - -```powershell -Add-PnPApplicationCustomizer -ClientSideComponentId <GuidPipeBind> - [-Title <String>] - [-Description <String>] - [-Sequence <Int>] - [-Scope <CustomActionScope>] - [-ClientSideComponentProperties <String>] - [-ClientSideHostProperties <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a SharePoint Framework client side extension application customizer by registering a user custom action to a web or sitecollection - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPApplicationCustomizer -Title "CollabFooter" -ClientSideComponentId c0ab3b94-8609-40cf-861e-2a1759170b43 -ClientSideComponentProperties "{`"sourceTermSet`":`"PnP-CollabFooter-SharedLinks`",`"personalItemsStorageProperty`":`"PnP-CollabFooter-MyLinks`"} -``` - -Adds a new application customizer to the current web. This requires that a SharePoint Framework solution has been deployed containing the application customizer specified in its manifest. Be sure to run Install-PnPApp before trying this cmdlet on a site. - -## PARAMETERS - -### -ClientSideComponentId -The Client Side Component Id of the SharePoint Framework client side extension application customizer found in the manifest - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ClientSideComponentProperties -The Client Side Component Properties of the application customizer. Specify values as a json string : "{Property1 : 'Value1', Property2: 'Value2'}" - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClientSideHostProperties -The Client Side Host Properties of the application customizer. Specify values as a json string : "{'preAllocatedApplicationCustomizerTopHeight': '50', 'preAllocatedApplicationCustomizerBottomHeight': '50'}" - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description of the application customizer - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scope -The scope of the CustomAction to add to. Either Web or Site; defaults to Web. 'All' is not valid for this command. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Sequence -Sequence of this application customizer being injected. Use when you have a specific sequence with which to have multiple application customizers being added to the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the application customizer - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePage.md deleted file mode 100644 index 9633ccc19a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePage.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpclientsidepage -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Add-PnPClientSidePage ---- - -# Add-PnPClientSidePage - -## SYNOPSIS -Adds a Client-Side Page - -## SYNTAX - -```powershell -Add-PnPClientSidePage -Name <String> - [-LayoutType <ClientSidePageLayoutType>] - [-PromoteAs <ClientSidePagePromoteType>] - [-ContentType <ContentTypePipeBind>] - [-CommentsEnabled [<SwitchParameter>]] - [-Publish [<SwitchParameter>]] - [-HeaderLayoutType <ClientSidePageHeaderLayoutType>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPClientSidePage -Name "NewPage" -``` - -Creates a new Client-Side page named 'NewPage' - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPClientSidePage -Name "NewPage" -ContentType "MyPageContentType" -``` - -Creates a new Client-Side page named 'NewPage' and sets the content type to the content type specified - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPClientSidePage -Name "NewPageTemplate" -PromoteAs Template -``` - -Creates a new Client-Side page named 'NewPage' and saves as a template to the site. - -### ------------------EXAMPLE 4------------------ -```powershell -Add-PnPClientSidePage -Name "Folder/NewPage" -``` - -Creates a new Client-Side page named 'NewPage' under 'Folder' folder and saves as a template to the site. - -### ------------------EXAMPLE 5------------------ -```powershell -Add-PnPClientSidePage -Name "NewPage" -HeaderLayoutType ColorBlock -``` - -Creates a new Client-Side page named 'NewPage' using the ColorBlock header layout - -## PARAMETERS - -### -CommentsEnabled -Enables or Disables the comments on the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ContentType -Specify either the name, ID or an actual content type. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HeaderLayoutType -Type of layout used for the header - -Only applicable to: SharePoint Online - -```yaml -Type: ClientSidePageHeaderLayoutType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LayoutType -Specifies the layout type of the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePageLayoutType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -Specifies the name of the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -PromoteAs -Allows to promote the page for a specific purpose (HomePage | NewsPage) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePromoteType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Publish -Publishes the page once it is saved. Applicable to libraries set to create major and minor versions. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePageSection.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePageSection.md deleted file mode 100644 index e9fa2bffc2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePageSection.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpclientsidepagesection -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Add-PnPClientSidePageSection ---- - -# Add-PnPClientSidePageSection - -## SYNOPSIS -Adds a new section to a Client-Side page - -## SYNTAX - -```powershell -Add-PnPClientSidePageSection -Page <ClientSidePagePipeBind> - -SectionTemplate <CanvasSectionTemplate> - [-Order <Int>] - [-ZoneEmphasis <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPClientSidePageSection -Page "MyPage" -SectionTemplate OneColumn -``` - -Adds a new one-column section to the Client-Side page 'MyPage' - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPClientSidePageSection -Page "MyPage" -SectionTemplate ThreeColumn -Order 10 -``` - -Adds a new Three columns section to the Client-Side page 'MyPage' with an order index of 10 - -### ------------------EXAMPLE 3------------------ -```powershell -$page = Add-PnPClientSidePage -Name "MyPage" -PS> Add-PnPClientSidePageSection -Page $page -SectionTemplate OneColumn -``` - -Adds a new one column section to the Client-Side page 'MyPage' - -### ------------------EXAMPLE 4------------------ -```powershell -$page = Add-PnPClientSidePage -Name "MyPage" -PS> Add-PnPClientSidePageSection -Page $page -SectionTemplate OneColumn -ZoneEmphasis 2 -``` - -Adds a new one column section to the Client-Side page 'MyPage' and sets the background to 2 (0 is no background, 3 is highest emphasis) - -## PARAMETERS - -### -Order -Sets the order of the section. (Default = 1) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Page -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SectionTemplate -Specifies the columns template to use for the section. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: CanvasSectionTemplate -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ZoneEmphasis -Sets the background of the section (default = 0) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideText.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideText.md deleted file mode 100644 index 75fef560db..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideText.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpclientsidetext -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Add-PnPClientSideText ---- - -# Add-PnPClientSideText - -## SYNOPSIS -Adds a text element to a client-side page. - -## SYNTAX - -### Default -```powershell -Add-PnPClientSideText -Page <ClientSidePagePipeBind> - -Text <String> - [-Order <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Positioned -```powershell -Add-PnPClientSideText -Page <ClientSidePagePipeBind> - -Text <String> - -Section <Int> - -Column <Int> - [-Order <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a new text element to a section on a client-side page. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPClientSideText -Page "MyPage" -Text "Hello World!" -``` - -Adds the text 'Hello World!' to the Client-Side Page 'MyPage' - -## PARAMETERS - -### -Column -Sets the column where to insert the text control. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Positioned - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Order -Sets the order of the text control. (Default = 1) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Default, Positioned - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Page -The name of the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: Default, Positioned - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Section -Sets the section where to insert the text control. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Positioned - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Text -Specifies the text to display in the text area. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: Default, Positioned - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideWebPart.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideWebPart.md deleted file mode 100644 index 01c362b1b7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideWebPart.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpclientsidewebpart -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Add-PnPClientSideWebPart ---- - -# Add-PnPClientSideWebPart - -## SYNOPSIS -Adds a Client-Side Web Part to a client-side page - -## SYNTAX - -### Default with built-in web part -```powershell -Add-PnPClientSideWebPart -Page <ClientSidePagePipeBind> - -DefaultWebPartType <DefaultClientSideWebParts> - [-WebPartProperties <PropertyBagPipeBind>] - [-Order <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Default with 3rd party web part -```powershell -Add-PnPClientSideWebPart -Page <ClientSidePagePipeBind> - -Component <ClientSideComponentPipeBind> - [-WebPartProperties <PropertyBagPipeBind>] - [-Order <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Positioned with built-in web part -```powershell -Add-PnPClientSideWebPart -Page <ClientSidePagePipeBind> - -DefaultWebPartType <DefaultClientSideWebParts> - -Section <Int> - -Column <Int> - [-WebPartProperties <PropertyBagPipeBind>] - [-Order <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Positioned with 3rd party web part -```powershell -Add-PnPClientSideWebPart -Page <ClientSidePagePipeBind> - -Component <ClientSideComponentPipeBind> - -Section <Int> - -Column <Int> - [-WebPartProperties <PropertyBagPipeBind>] - [-Order <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a client-side web part to an existing client-side page. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPClientSideWebPart -Page "MyPage" -DefaultWebPartType BingMap -``` - -Adds a built-in Client-Side component 'BingMap' to the page called 'MyPage' - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPClientSideWebPart -Page "MyPage" -Component "HelloWorld" -``` - -Adds a Client-Side component 'HelloWorld' to the page called 'MyPage' - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPClientSideWebPart -Page "MyPage" -Component "HelloWorld" -Section 1 -Column 2 -``` - -Adds a Client-Side component 'HelloWorld' to the page called 'MyPage' in section 1 and column 2 - -## PARAMETERS - -### -Column -Sets the column where to insert the web part control. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Positioned with built-in web part, Positioned with 3rd party web part - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Component -Specifies the component instance or Id to add. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSideComponentPipeBind -Parameter Sets: Default with 3rd party web part, Positioned with 3rd party web part - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DefaultWebPartType -Defines a default web part type to insert. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: DefaultClientSideWebParts -Parameter Sets: Default with built-in web part, Positioned with built-in web part - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Order -Sets the order of the web part control. (Default = 1) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Default with built-in web part, Default with 3rd party web part, Positioned with built-in web part, Positioned with 3rd party web part - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Page -The name of the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: Default with built-in web part, Default with 3rd party web part, Positioned with built-in web part, Positioned with 3rd party web part - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Section -Sets the section where to insert the web part control. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Positioned with built-in web part, Positioned with 3rd party web part - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -WebPartProperties -The properties of the web part - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: PropertyBagPipeBind -Parameter Sets: Default with built-in web part, Default with 3rd party web part, Positioned with built-in web part, Positioned with 3rd party web part - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentType.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentType.md deleted file mode 100644 index f271a64f50..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentType.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpcontenttype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPContentType ---- - -# Add-PnPContentType - -## SYNOPSIS -Adds a new content type - -## SYNTAX - -```powershell -Add-PnPContentType -Name <String> - [-ContentTypeId <String>] - [-Description <String>] - [-Group <String>] - [-ParentContentType <ContentType>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPContentType -Name "Project Document" -Description "Use for Contoso projects" -Group "Contoso Content Types" -ParentContentType $ct -``` - -This will add a new content type based on the parent content type stored in the $ct variable. - -## PARAMETERS - -### -ContentTypeId -If specified, in the format of 0x0100233af432334r434343f32f3, will create a content type with the specific ID - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -Specifies the description of the new content type - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Group -Specifies the group of the new content type - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -Specify the name of the new content type - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ParentContentType -Specifies the parent of the new content type - -```yaml -Type: ContentType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.ContentType - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToDocumentSet.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToDocumentSet.md deleted file mode 100644 index 7648ef4fff..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToDocumentSet.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpcontenttypetodocumentset -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPContentTypeToDocumentSet ---- - -# Add-PnPContentTypeToDocumentSet - -## SYNOPSIS -Adds a content type to a document set - -## SYNTAX - -```powershell -Add-PnPContentTypeToDocumentSet -ContentType <ContentTypePipeBind[]> - -DocumentSet <DocumentSetPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPContentTypeToDocumentSet -ContentType "Test CT" -DocumentSet "Test Document Set" -``` - -This will add the content type called 'Test CT' to the document set called ''Test Document Set' - -### ------------------EXAMPLE 2------------------ -```powershell -$docset = Get-PnPDocumentSetTemplate -Identity "Test Document Set" -$ct = Get-PnPContentType -Identity "Test CT" -Add-PnPContentTypeToDocumentSet -ContentType $ct -DocumentSet $docset -``` - -This will add the content type called 'Test CT' to the document set called ''Test Document Set' - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPContentTypeToDocumentSet -ContentType 0x0101001F1CEFF1D4126E4CAD10F00B6137E969 -DocumentSet 0x0120D520005DB65D094035A241BAC9AF083F825F3B -``` - -This will add the content type called 'Test CT' to the document set called ''Test Document Set' - -## PARAMETERS - -### -ContentType -The content type object, name or id to add. Either specify name, an id, or a content type object. - -```yaml -Type: ContentTypePipeBind[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DocumentSet -The document set object or id to add the content type to. Either specify a name, a document set template object, an id, or a content type object - -```yaml -Type: DocumentSetPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToList.md deleted file mode 100644 index 2d104ecd72..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToList.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpcontenttypetolist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPContentTypeToList ---- - -# Add-PnPContentTypeToList - -## SYNOPSIS -Adds a new content type to a list - -## SYNTAX - -```powershell -Add-PnPContentTypeToList -List <ListPipeBind> - -ContentType <ContentTypePipeBind> - [-DefaultContentType [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPContentTypeToList -List "Documents" -ContentType "Project Document" -DefaultContentType -``` - -This will add an existing content type to a list and sets it as the default content type - -## PARAMETERS - -### -ContentType -Specifies the content type that needs to be added to the list - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DefaultContentType -Specify if the content type needs to be the default content type or not - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -Specifies the list to which the content type needs to be added - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPCustomAction.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPCustomAction.md deleted file mode 100644 index 1e3fff5b0e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPCustomAction.md +++ /dev/null @@ -1,298 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpcustomaction -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPCustomAction ---- - -# Add-PnPCustomAction - -## SYNOPSIS -Adds a custom action - -## SYNTAX - -### Client Side Component Id -```powershell -Add-PnPCustomAction -Name <String> - -Title <String> - -Location <String> - -ClientSideComponentId <GuidPipeBind> - [-Sequence <Int>] - [-RegistrationId <String>] - [-RegistrationType <UserCustomActionRegistrationType>] - [-Scope <CustomActionScope>] - [-ClientSideComponentProperties <String>] - [-ClientSideHostProperties <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Default -```powershell -Add-PnPCustomAction -Name <String> - -Title <String> - -Description <String> - -Group <String> - -Location <String> - [-Sequence <Int>] - [-Url <String>] - [-ImageUrl <String>] - [-CommandUIExtension <String>] - [-RegistrationId <String>] - [-Rights <PermissionKind[]>] - [-RegistrationType <UserCustomActionRegistrationType>] - [-Scope <CustomActionScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a user custom action to a web or sitecollection. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$cUIExtn = "<CommandUIExtension><CommandUIDefinitions><CommandUIDefinition Location=""Ribbon.List.Share.Controls._children""><Button Id=""Ribbon.List.Share.GetItemsCountButton"" Alt=""Get list items count"" Sequence=""11"" Command=""Invoke_GetItemsCountButtonRequest"" LabelText=""Get Items Count"" TemplateAlias=""o1"" Image32by32=""_layouts/15/images/placeholder32x32.png"" Image16by16=""_layouts/15/images/placeholder16x16.png"" /></CommandUIDefinition></CommandUIDefinitions><CommandUIHandlers><CommandUIHandler Command=""Invoke_GetItemsCountButtonRequest"" CommandAction=""javascript: alert('Total items in this list: '+ ctx.TotalListItems);"" EnabledScript=""javascript: function checkEnable() { return (true);} checkEnable();""/></CommandUIHandlers></CommandUIExtension>" - -Add-PnPCustomAction -Name 'GetItemsCount' -Title 'Invoke GetItemsCount Action' -Description 'Adds custom action to custom list ribbon' -Group 'SiteActions' -Location 'CommandUI.Ribbon' -CommandUIExtension $cUIExtn -``` - -Adds a new custom action to the custom list template, and sets the Title, Name and other fields with the specified values. On click it shows the number of items in that list. Notice: escape quotes in CommandUIExtension. - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPCustomAction -Title "CollabFooter" -Name "CollabFooter" -Location "ClientSideExtension.ApplicationCustomizer" -ClientSideComponentId c0ab3b94-8609-40cf-861e-2a1759170b43 -ClientSideComponentProperties "{`"sourceTermSet`":`"PnP-CollabFooter-SharedLinks`",`"personalItemsStorageProperty`":`"PnP-CollabFooter-MyLinks`"} -``` - -Adds a new application customizer to the site. This requires that an SPFX solution has been deployed containing the application customizer specified. Be sure to run Install-PnPApp before trying this cmdlet on a site. - -## PARAMETERS - -### -ClientSideComponentId -The Client Side Component Id of the custom action - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: Client Side Component Id - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ClientSideComponentProperties -The Client Side Component Properties of the custom action. Specify values as a json string : "{Property1 : 'Value1', Property2: 'Value2'}" - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: Client Side Component Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClientSideHostProperties -The Client Side Host Properties of the custom action. Specify values as a json string : "{'preAllocatedApplicationCustomizerTopHeight': '50', 'preAllocatedApplicationCustomizerBottomHeight': '50'}" - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Client Side Component Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CommandUIExtension -XML fragment that determines user interface properties of the custom action - -```yaml -Type: String -Parameter Sets: Default - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description of the custom action - -```yaml -Type: String -Parameter Sets: Default - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Group -The group where this custom action needs to be added like 'SiteActions' - -```yaml -Type: String -Parameter Sets: Default - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ImageUrl -The URL of the image associated with the custom action - -```yaml -Type: String -Parameter Sets: Default - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Location -The actual location where this custom action need to be added like 'CommandUI.Ribbon' - -```yaml -Type: String -Parameter Sets: Default, Client Side Component Id - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Name -The name of the custom action - -```yaml -Type: String -Parameter Sets: Default, Client Side Component Id - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -RegistrationId -The identifier of the object associated with the custom action. - -```yaml -Type: String -Parameter Sets: Default, Client Side Component Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RegistrationType -Specifies the type of object associated with the custom action - -```yaml -Type: UserCustomActionRegistrationType -Parameter Sets: Default, Client Side Component Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Rights -A string array that contain the permissions needed for the custom action - -```yaml -Type: PermissionKind[] -Parameter Sets: Default - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scope -The scope of the CustomAction to add to. Either Web or Site; defaults to Web. 'All' is not valid for this command. - -```yaml -Type: CustomActionScope -Parameter Sets: Default, Client Side Component Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Sequence -Sequence of this CustomAction being injected. Use when you have a specific sequence with which to have multiple CustomActions being added to the page. - -```yaml -Type: Int -Parameter Sets: Default, Client Side Component Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the custom action - -```yaml -Type: String -Parameter Sets: Default, Client Side Component Id - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -The URL, URI or ECMAScript (JScript, JavaScript) function associated with the action - -```yaml -Type: String -Parameter Sets: Default - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[UserCustomAction](https://docs.microsoft.com/en-us/previous-versions/office/sharepoint-server/ee539583(v=office.15))[BasePermissions](https://docs.microsoft.com/en-us/previous-versions/office/sharepoint-server/ee543321(v=office.15)) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDataRowsToProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDataRowsToProvisioningTemplate.md deleted file mode 100644 index 5ed3160abe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDataRowsToProvisioningTemplate.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpdatarowstoprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPDataRowsToProvisioningTemplate ---- - -# Add-PnPDataRowsToProvisioningTemplate - -## SYNOPSIS -Adds datarows to a list inside a PnP Provisioning Template - -## SYNTAX - -```powershell -Add-PnPDataRowsToProvisioningTemplate -Path <String> - -List <ListPipeBind> - [-Query <String>] - [-Fields <String[]>] - [-TokenizeUrls [<SwitchParameter>]] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-IncludeSecurity [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPDataRowsToProvisioningTemplate -Path template.pnp -List 'PnPTestList' -Query '<View></View>' -Fields 'Title','Choice' -``` - -Adds datarows from the provided list to the PnP Provisioning Template at the provided location - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPDataRowsToProvisioningTemplate -Path template.pnp -List 'PnPTestList' -Query '<View></View>' -Fields 'Title','Choice' -IncludeSecurity -``` - -Adds datarows from the provided list to the PnP Provisioning Template at the provided location - -## PARAMETERS - -### -Fields -The fields to retrieve. If not specified all fields will be loaded in the returned list object. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeSecurity -A switch to include ObjectSecurity information. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: 5 -Accept pipeline input: False -``` - -### -List -The list to query - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Path -Filename of the .PNP Open XML site template to read from, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Query -The CAML query to execute against the list. Defaults to all items. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while loading the template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -TokenizeUrls -If set, this switch will try to tokenize the values with web and site related tokens - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDocumentSet.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDocumentSet.md deleted file mode 100644 index 750c24b900..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDocumentSet.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpdocumentset -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPDocumentSet ---- - -# Add-PnPDocumentSet - -## SYNOPSIS -Creates a new document set in a library. - -## SYNTAX - -```powershell -Add-PnPDocumentSet -List <ListPipeBind> - -Name <String> - -ContentType <ContentTypePipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPDocumentSet -List "Documents" -ContentType "Test Document Set" -Name "Test" -``` - -This will add a new document set based upon the 'Test Document Set' content type to a list called 'Documents'. The document set will be named 'Test' - -## PARAMETERS - -### -ContentType -The name of the content type, its ID or an actual content object referencing to the document set - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The name of the list, its ID or an actual list object from where the document set needs to be added - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Name -The name of the document set - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPEventReceiver.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPEventReceiver.md deleted file mode 100644 index 7158e7c4d6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPEventReceiver.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpeventreceiver -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPEventReceiver ---- - -# Add-PnPEventReceiver - -## SYNOPSIS -Adds a new remote event receiver - -## SYNTAX - -```powershell -Add-PnPEventReceiver -Name <String> - -Url <String> - -EventReceiverType <EventReceiverType> - -Synchronization <EventReceiverSynchronization> - [-List <ListPipeBind>] - [-SequenceNumber <Int>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPEventReceiver -List "ProjectList" -Name "TestEventReceiver" -Url https://yourserver.azurewebsites.net/eventreceiver.svc -EventReceiverType ItemAdded -Synchronization Asynchronous -``` - -This will add a new remote event receiver that is executed after an item has been added to the ProjectList list - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPEventReceiver -Name "TestEventReceiver" -Url https://yourserver.azurewebsites.net/eventreceiver.svc -EventReceiverType WebAdding -Synchronization Synchronous -``` - -This will add a new remote event receiver that is executed while a new subsite is being created - -## PARAMETERS - -### -EventReceiverType -The type of the event receiver like ItemAdded, ItemAdding. See https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.eventreceivertype.aspx for the full list of available types. - -```yaml -Type: EventReceiverType -Parameter Sets: (All) -Aliases: Type - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The list object or name where the remote event receiver needs to be added. If omitted, the remote event receiver will be added to the web. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -The name of the remote event receiver - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -SequenceNumber -The sequence number where this remote event receiver should be placed - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Synchronization -The synchronization type: Asynchronous or Synchronous - -```yaml -Type: EventReceiverSynchronization -Parameter Sets: (All) -Aliases: Sync - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -The URL of the remote event receiver web service - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.EventReceiverDefinition - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPField.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPField.md deleted file mode 100644 index 6ea7eb3f48..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPField.md +++ /dev/null @@ -1,283 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpfield -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPField ---- - -# Add-PnPField - -## SYNOPSIS -Add a field - -## SYNTAX - -### Add field by XML to list -```powershell -Add-PnPField [-AddToDefaultView [<SwitchParameter>]] - [-Required [<SwitchParameter>]] - [-Group <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Add field reference to list -```powershell -Add-PnPField -List <ListPipeBind> - -Field <FieldPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Add field to list -```powershell -Add-PnPField -DisplayName <String> - -InternalName <String> - -Type <FieldType> - [-List <ListPipeBind>] - [-Id <GuidPipeBind>] - [-AddToDefaultView [<SwitchParameter>]] - [-Required [<SwitchParameter>]] - [-Group <String>] - [-ClientSideComponentId <GuidPipeBind>] - [-ClientSideComponentProperties <String>] - [-Choices <String[]>] - [-Formula <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Add field to web -```powershell -Add-PnPField -DisplayName <String> - -InternalName <String> - -Type <FieldType> - [-Id <GuidPipeBind>] - [-ClientSideComponentId <GuidPipeBind>] - [-ClientSideComponentProperties <String>] - [-Choices <String[]>] - [-Formula <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a field to a list or as a site column - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPField -Type Calculated -InternalName "C1" -DisplayName "C1" -Formula ="[Title]" -``` - -Adds a new calculated site column with the formula specified - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPField -List "Demo list" -DisplayName "Location" -InternalName "SPSLocation" -Type Choice -Group "Demo Group" -AddToDefaultView -Choices "Stockholm","Helsinki","Oslo" -``` - -This will add a field of type Choice to the list "Demo List". - -### ------------------EXAMPLE 3------------------ -```powershell -PS:>Add-PnPField -List "Demo list" -DisplayName "Speakers" -InternalName "SPSSpeakers" -Type MultiChoice -Group "Demo Group" -AddToDefaultView -Choices "Obiwan Kenobi","Darth Vader", "Anakin Skywalker" -``` - -This will add a field of type Multiple Choice to the list "Demo List". (you can pick several choices for the same item) - -## PARAMETERS - -### -AddToDefaultView -Switch Parameter if this field must be added to the default view - -```yaml -Type: SwitchParameter -Parameter Sets: Add field to list, Add field by XML to list - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Choices -Specify choices, only valid if the field type is Choice - -```yaml -Type: String[] -Parameter Sets: Add field to list - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -ClientSideComponentId -The Client Side Component Id to set to the field - -Only applicable to: SharePoint Online - -```yaml -Type: GuidPipeBind -Parameter Sets: Add field to list, Add field to web - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClientSideComponentProperties -The Client Side Component Properties to set to the field - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Add field to list, Add field to web - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisplayName -The display name of the field - -```yaml -Type: String -Parameter Sets: Add field to list, Add field to web - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Field -The name of the field, its ID or an actual field object that needs to be added - -```yaml -Type: FieldPipeBind -Parameter Sets: Add field reference to list - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Formula -Specify the formula. Only available if the field type is Calculated - -```yaml -Type: String -Parameter Sets: Add field to list - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Group -The group name to where this field belongs to - -```yaml -Type: String -Parameter Sets: Add field to list, Add field by XML to list - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Id -The ID of the field, must be unique - -```yaml -Type: GuidPipeBind -Parameter Sets: Add field to list, Add field to web - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -InternalName -The internal name of the field - -```yaml -Type: String -Parameter Sets: Add field to list, Add field to web - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The name of the list, its ID or an actual list object where this field needs to be added - -```yaml -Type: ListPipeBind -Parameter Sets: Add field to list, Add field reference to list - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Required -Switch Parameter if the field is a required field - -```yaml -Type: SwitchParameter -Parameter Sets: Add field to list, Add field by XML to list - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Type -The type of the field like Choice, Note, MultiChoice. For a complete list of field types visit https://docs.microsoft.com/dotnet/api/microsoft.sharepoint.client.fieldtype - -```yaml -Type: FieldType -Parameter Sets: Add field to list, Add field to web - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Field - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldFromXml.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldFromXml.md deleted file mode 100644 index 64044d4f2b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldFromXml.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpfieldfromxml -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPFieldFromXml ---- - -# Add-PnPFieldFromXml - -## SYNOPSIS -Adds a field to a list or as a site column based upon a CAML/XML field definition - -## SYNTAX - -```powershell -Add-PnPFieldFromXml -FieldXml <String> - [-List <ListPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$xml = '<Field Type="Text" Name="PSCmdletTest" DisplayName="PSCmdletTest" ID="{27d81055-f208-41c9-a976-61c5473eed4a}" Group="Test" Required="FALSE" StaticName="PSCmdletTest" />' -Add-PnPFieldFromXml -FieldXml $xml -``` - -Adds a field with the specified field CAML code to the site. - -### ------------------EXAMPLE 2------------------ -```powershell -$xml = '<Field Type="Text" Name="PSCmdletTest" DisplayName="PSCmdletTest" ID="{27d81055-f208-41c9-a976-61c5473eed4a}" Group="Test" Required="FALSE" StaticName="PSCmdletTest" />' -Add-PnPFieldFromXml -List "Demo List" -FieldXml $xml -``` - -Adds a field with the specified field CAML code to the list "Demo List". - -## PARAMETERS - -### -FieldXml -CAML snippet containing the field definition. See http://msdn.microsoft.com/en-us/library/office/ms437580(v=office.15).aspx - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -List -The name of the list, its ID or an actual list object where this field needs to be added - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Field - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Field CAML](http://msdn.microsoft.com/en-us/library/office/ms437580(v=office.15).aspx) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldToContentType.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldToContentType.md deleted file mode 100644 index 9a0caa3217..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldToContentType.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpfieldtocontenttype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPFieldToContentType ---- - -# Add-PnPFieldToContentType - -## SYNOPSIS -Adds an existing site column to a content type - -## SYNTAX - -```powershell -Add-PnPFieldToContentType -Field <FieldPipeBind> - -ContentType <ContentTypePipeBind> - [-Required [<SwitchParameter>]] - [-Hidden [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPFieldToContentType -Field "Project_Name" -ContentType "Project Document" -``` - -This will add an existing site column with an internal name of "Project_Name" to a content type called "Project Document" - -## PARAMETERS - -### -ContentType -Specifies which content type a field needs to be added to - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Field -Specifies the field that needs to be added to the content type - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Hidden -Specifies whether the field should be hidden or not - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Required -Specifies whether the field is required or not - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFile.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFile.md deleted file mode 100644 index e633d45fb7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFile.md +++ /dev/null @@ -1,341 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpfile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPFile ---- - -# Add-PnPFile - -## SYNOPSIS -Uploads a file to Web - -## SYNTAX - -### Upload file -```powershell -Add-PnPFile -Path <String> - -Folder <String> - [-NewFileName <String>] - [-Checkout [<SwitchParameter>]] - [-CheckInComment <String>] - [-Approve [<SwitchParameter>]] - [-ApproveComment <String>] - [-Publish [<SwitchParameter>]] - [-PublishComment <String>] - [-UseWebDav [<SwitchParameter>]] - [-Values <Hashtable>] - [-ContentType <ContentTypePipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Upload file from stream -```powershell -Add-PnPFile -FileName <String> - -Stream <Stream> - -Folder <String> - [-Checkout [<SwitchParameter>]] - [-CheckInComment <String>] - [-Approve [<SwitchParameter>]] - [-ApproveComment <String>] - [-Publish [<SwitchParameter>]] - [-PublishComment <String>] - [-UseWebDav [<SwitchParameter>]] - [-Values <Hashtable>] - [-ContentType <ContentTypePipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPFile -Path c:\temp\company.master -Folder "_catalogs/masterpage" -``` - -This will upload the file company.master to the masterpage catalog - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPFile -Path .\displaytemplate.html -Folder "_catalogs/masterpage/display templates/test" -``` - -This will upload the file displaytemplate.html to the test folder in the display templates folder. If the test folder does not exist it will create it. - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPFile -Path .\sample.doc -Folder "Shared Documents" -Values @{Modified="1/1/2016"} -``` - -This will upload the file sample.doc to the Shared Documents folder. After uploading it will set the Modified date to 1/1/2016. - -### ------------------EXAMPLE 4------------------ -```powershell -Add-PnPFile -FileName sample.doc -Folder "Shared Documents" -Stream $fileStream -Values @{Modified="1/1/2016"} -``` - -This will add a file sample.doc with the contents of the stream into the Shared Documents folder. After adding it will set the Modified date to 1/1/2016. - -### ------------------EXAMPLE 5------------------ -```powershell -Add-PnPFile -Path sample.doc -Folder "Shared Documents" -ContentType "Document" -Values @{Modified="1/1/2016"} -``` - -This will add a file sample.doc to the Shared Documents folder, with a ContentType of 'Documents'. After adding it will set the Modified date to 1/1/2016. - -### ------------------EXAMPLE 6------------------ -```powershell -Add-PnPFile -Path sample.docx -Folder "Documents" -Values @{Modified="1/1/2016"; Created="1/1/2017"; Editor=23} -``` - -This will add a file sample.docx to the Documents folder and will set the Modified date to 1/1/2016, Created date to 1/1/2017 and the Modified By field to the user with ID 23. To find out about the proper user ID to relate to a specific user, use Get-PnPUser. - -### ------------------EXAMPLE 7------------------ -```powershell -Add-PnPFile -Path sample.docx -Folder "Documents" -NewFileName "differentname.docx" -``` - -This will upload a local file sample.docx to the Documents folder giving it the filename differentname.docx on SharePoint - -## PARAMETERS - -### -Approve -Will auto approve the uploaded file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ApproveComment -The comment added to the approval. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CheckInComment -The comment added to the checkin. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Checkout -If versioning is enabled, this will check out the file first if it exists, upload the file, then check it in again. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ContentType -Use to assign a ContentType to the file. - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -FileName -Name for file - -```yaml -Type: String -Parameter Sets: Upload file from stream - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Folder -The destination folder in the site - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -NewFileName -Filename to give the file on SharePoint - -```yaml -Type: String -Parameter Sets: Upload file - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -The local file path. - -```yaml -Type: String -Parameter Sets: Upload file - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Publish -Will auto publish the file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PublishComment -The comment added to the publish action. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Stream -Stream with the file contents - -```yaml -Type: Stream -Parameter Sets: Upload file from stream - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -UseWebDav - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Values -Use the internal names of the fields when specifying field names. - -Single line of text: -Values @{"Title" = "Title New"} - -Multiple lines of text: -Values @{"MultiText" = "New text\n\nMore text"} - -Rich text: -Values @{"MultiText" = "<strong>New</strong> text"} - -Choice: -Values @{"Choice" = "Value 1"} - -Number: -Values @{"Number" = "10"} - -Currency: -Values @{"Number" = "10"} - -Currency: -Values @{"Currency" = "10"} - -Date and Time: -Values @{"DateAndTime" = "03/10/2015 14:16"} - -Lookup (id of lookup value): -Values @{"Lookup" = "2"} - -Multi value lookup (id of lookup values as array 1): -Values @{"MultiLookupField" = "1","2"} - -Multi value lookup (id of lookup values as array 2): -Values @{"MultiLookupField" = 1,2} - -Multi value lookup (id of lookup values as string): -Values @{"MultiLookupField" = "1,2"} - -Yes/No: -Values @{"YesNo" = $false} - -Person/Group (id of user/group in Site User Info List or email of the user, separate multiple values with a comma): -Values @{"Person" = "user1@domain.com","21"} - -Managed Metadata (single value with path to term): -Values @{"MetadataField" = "CORPORATE|DEPARTMENTS|FINANCE"} - -Managed Metadata (single value with id of term): -Values @{"MetadataField" = "fe40a95b-2144-4fa2-b82a-0b3d0299d818"} with Id of term - -Managed Metadata (multiple values with paths to terms): -Values @{"MetadataField" = "CORPORATE|DEPARTMENTS|FINANCE","CORPORATE|DEPARTMENTS|HR"} - -Managed Metadata (multiple values with ids of terms): -Values @{"MetadataField" = "fe40a95b-2144-4fa2-b82a-0b3d0299d818","52d88107-c2a8-4bf0-adfa-04bc2305b593"} - -Hyperlink or Picture: -Values @{"Hyperlink" = "https://github.com/OfficeDev/,%20OfficePnp"} - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.File - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md deleted file mode 100644 index 67d9ecbc47..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpfiletoprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPFileToProvisioningTemplate ---- - -# Add-PnPFileToProvisioningTemplate - -## SYNOPSIS -Adds a file to a PnP Provisioning Template - -## SYNTAX - -### Remove File -```powershell -Add-PnPFileToProvisioningTemplate -Path <String> - -SourceUrl <String> - [-Container <String>] - [-FileLevel <FileLevel>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-FileOverwrite [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Local File -```powershell -Add-PnPFileToProvisioningTemplate -Path <String> - -Source <String> - -Folder <String> - [-Container <String>] - [-FileLevel <FileLevel>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-FileOverwrite [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPFileToProvisioningTemplate -Path template.pnp -Source $sourceFilePath -Folder $targetFolder -``` - -Adds a file to a PnP Site Template - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPFileToProvisioningTemplate -Path template.xml -Source $sourceFilePath -Folder $targetFolder -``` - -Adds a file reference to a PnP Site XML Template - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPFileToProvisioningTemplate -Path template.pnp -Source "./myfile.png" -Folder "folderinsite" -FileLevel Published -FileOverwrite:$false -``` - -Adds a file to a PnP Site Template, specifies the level as Published and defines to not overwrite the file if it exists in the site. - -### ------------------EXAMPLE 4------------------ -```powershell -Add-PnPFileToProvisioningTemplate -Path template.pnp -Source $sourceFilePath -Folder $targetFolder -Container $container -``` - -Adds a file to a PnP Site Template with a custom container for the file - -### ------------------EXAMPLE 5------------------ -```powershell -Add-PnPFileToProvisioningTemplate -Path template.pnp -SourceUrl "Shared%20Documents/ProjectStatus.docs" -``` - -Adds a file to a PnP Provisioning Template retrieved from the currently connected site. The url can be server relative or web relative. If specifying a server relative url has to start with the current site url. - -## PARAMETERS - -### -Container -The target Container for the file to add to the in-memory template, optional argument. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 3 -Accept pipeline input: False -``` - -### -FileLevel -The level of the files to add. Defaults to Published - -```yaml -Type: FileLevel -Parameter Sets: (All) - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -FileOverwrite -Set to overwrite in site, Defaults to true - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: 5 -Accept pipeline input: False -``` - -### -Folder -The target Folder for the file to add to the in-memory template. - -```yaml -Type: String -Parameter Sets: Local File - -Required: True -Position: 2 -Accept pipeline input: False -``` - -### -Path -Filename of the .PNP Open XML site template to read from, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Source -The file to add to the in-memory template, optionally including full path. - -```yaml -Type: String -Parameter Sets: Local File - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -SourceUrl -The file to add to the in-memory template, specifying its url in the current connected Web. - -```yaml -Type: String -Parameter Sets: Remove File - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while loading the template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFolder.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFolder.md deleted file mode 100644 index dc154cbb86..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFolder.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpfolder -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPFolder ---- - -# Add-PnPFolder - -## SYNOPSIS -Creates a folder within a parent folder - -## SYNTAX - -```powershell -Add-PnPFolder -Name <String> - -Folder <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPFolder -Name NewFolder -Folder _catalogs/masterpage -``` - -This will create the folder NewFolder in the masterpage catalog - -## PARAMETERS - -### -Folder -The parent folder in the site - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Name -The folder name - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHtmlPublishingPageLayout.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHtmlPublishingPageLayout.md deleted file mode 100644 index a1b063aa42..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHtmlPublishingPageLayout.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnphtmlpublishingpagelayout -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPHtmlPublishingPageLayout ---- - -# Add-PnPHtmlPublishingPageLayout - -## SYNOPSIS -Adds a HTML based publishing page layout - -## SYNTAX - -```powershell -Add-PnPHtmlPublishingPageLayout -SourceFilePath <String> - -Title <String> - -Description <String> - -AssociatedContentTypeID <String> - [-DestinationFolderHierarchy <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPHtmlPublishingPageLayout -Title 'Our custom page layout' -SourceFilePath 'customlayout.aspx' -Description 'A custom page layout' -AssociatedContentTypeID 0x01010901 -``` - -Uploads the pagelayout 'customlayout.aspx' from the current location to the current site as a 'web part page' pagelayout - -## PARAMETERS - -### -AssociatedContentTypeID -Associated content type ID - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Description -Description for the page layout - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DestinationFolderHierarchy -Folder hierarchy where the HTML page layouts will be deployed - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SourceFilePath -Path to the file which will be uploaded - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -Title for the page layout - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHubSiteAssociation.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHubSiteAssociation.md deleted file mode 100644 index 56a60c4e7c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHubSiteAssociation.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnphubsiteassociation -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPHubSiteAssociation ---- - -# Add-PnPHubSiteAssociation - -## SYNOPSIS -Connects a site to a hubsite. - -## SYNTAX - -```powershell -Add-PnPHubSiteAssociation -Site <SitePipeBind> - -HubSite <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Connects an existing site to a hubsite - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPHubSiteAssociation -Site https://tenant.sharepoint.com/sites/mysite -HubSite https://tenant.sharepoint.com/sites/hubsite -``` - -This example adds the specified site to the hubsite. - -## PARAMETERS - -### -HubSite -The hubsite to connect the site to - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Site -The site to connect to the hubsite - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPIndexedProperty.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPIndexedProperty.md deleted file mode 100644 index 01af37ea89..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPIndexedProperty.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpindexedproperty -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPIndexedProperty ---- - -# Add-PnPIndexedProperty - -## SYNOPSIS -Marks the value of the propertybag key specified to be indexed by search. - -## SYNTAX - -```powershell -Add-PnPIndexedProperty -Key <String> - [-List <ListPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Key -Key of the property bag value to be indexed - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -List -The list object or name where to set the indexed property - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptBlock.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptBlock.md deleted file mode 100644 index 622f5c7706..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptBlock.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpjavascriptblock -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPJavaScriptBlock ---- - -# Add-PnPJavaScriptBlock - -## SYNOPSIS -Adds a link to a JavaScript snippet/block to a web or site collection - -## SYNTAX - -```powershell -Add-PnPJavaScriptBlock -Name <String> - -Script <String> - [-Sequence <Int>] - [-Scope <CustomActionScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Specify a scope as 'Site' to add the custom action to all sites in a site collection. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPJavaScriptBlock -Name myAction -script '<script>Alert("This is my Script block");</script>' -Sequence 9999 -Scope Site -``` - -Add a JavaScript code block to all pages within the current site collection under the name myAction and at order 9999 - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPJavaScriptBlock -Name myAction -script '<script>Alert("This is my Script block");</script>' -``` - -Add a JavaScript code block to all pages within the current web under the name myAction - -## PARAMETERS - -### -Name -The name of the script block. Can be used to identify the script with other cmdlets or coded solutions - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Key - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope -The scope of the script to add to. Either Web or Site, defaults to Web. 'All' is not valid for this command. - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Script -The javascript block to add to the specified scope - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Sequence -A sequence number that defines the order on the page - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptLink.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptLink.md deleted file mode 100644 index 7d7c109608..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPJavaScriptLink.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpjavascriptlink -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPJavaScriptLink ---- - -# Add-PnPJavaScriptLink - -## SYNOPSIS -Adds a link to a JavaScript file to a web or sitecollection, valid only for SharePoint classic site experience. - -## SYNTAX - -```powershell -Add-PnPJavaScriptLink -Name <String> - -Url <String[]> - [-Sequence <Int>] - [-Scope <CustomActionScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Creates a custom action that refers to a JavaScript file - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPJavaScriptLink -Name jQuery -Url https://code.jquery.com/jquery.min.js -Sequence 9999 -Scope Site -``` - -Injects a reference to the latest v1 series jQuery library to all pages within the current site collection under the name jQuery and at order 9999 - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPJavaScriptLink -Name jQuery -Url https://code.jquery.com/jquery.min.js -``` - -Injects a reference to the latest v1 series jQuery library to all pages within the current web under the name jQuery - -## PARAMETERS - -### -Name -Name under which to register the JavaScriptLink - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Key - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope -Defines if this JavaScript file will be injected to every page within the current site collection or web. All is not allowed in for this command. Default is web. - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Sequence -Sequence of this JavaScript being injected. Use when you have a specific sequence with which to have JavaScript files being added to the page. I.e. jQuery library first and then jQueryUI. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -URL to the JavaScript file to inject - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPListFoldersToProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPListFoldersToProvisioningTemplate.md deleted file mode 100644 index 282757a021..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPListFoldersToProvisioningTemplate.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnplistfolderstoprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPListFoldersToProvisioningTemplate ---- - -# Add-PnPListFoldersToProvisioningTemplate - -## SYNOPSIS -Adds folders to a list in a PnP Provisioning Template - -## SYNTAX - -```powershell -Add-PnPListFoldersToProvisioningTemplate -Path <String> - -List <ListPipeBind> - [-Recursive [<SwitchParameter>]] - [-IncludeSecurity [<SwitchParameter>]] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPListFoldersToProvisioningTemplate -Path template.pnp -List 'PnPTestList' -``` - -Adds top level folders from a list to an existing template and returns an in-memory PnP Site Template - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPListFoldersToProvisioningTemplate -Path template.pnp -List 'PnPTestList' -Recursive -``` - -Adds all folders from a list to an existing template and returns an in-memory PnP Site Template - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPListFoldersToProvisioningTemplate -Path template.pnp -List 'PnPTestList' -Recursive -IncludeSecurity -``` - -Adds all folders from a list with unique permissions to an in-memory PnP Site Template - -## PARAMETERS - -### -IncludeSecurity -A switch to include ObjectSecurity information. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: 5 -Accept pipeline input: False -``` - -### -List -The list to query - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 2 -Accept pipeline input: False -``` - -### -Path -Filename of the .PNP Open XML site template to read from, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Recursive -A switch parameter to include all folders in the list, or just top level folders. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while loading the template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: 6 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPListItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPListItem.md deleted file mode 100644 index 3e7288df36..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPListItem.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnplistitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPListItem ---- - -# Add-PnPListItem - -## SYNOPSIS -Adds an item to the list and sets the creation time to the current date and time. The author is set to the current authenticated user executing the cmdlet. In order to set the author to a different user, please refer to Set-PnPListItem. - -## SYNTAX - -```powershell -Add-PnPListItem -List <ListPipeBind> - [-ContentType <ContentTypePipeBind>] - [-Values <Hashtable>] - [-Folder <String>] - [-Label <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPListItem -List "Demo List" -Values @{"Title" = "Test Title"; "Category"="Test Category"} -``` - -Adds a new list item to the "Demo List", and sets both the Title and Category fields with the specified values. Notice, use the internal names of fields. - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPListItem -List "Demo List" -ContentType "Company" -Values @{"Title" = "Test Title"; "Category"="Test Category"} -``` - -Adds a new list item to the "Demo List", sets the content type to "Company" and sets both the Title and Category fields with the specified values. Notice, use the internal names of fields. - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPListItem -List "Demo List" -Values @{"MultiUserField"="user1@domain.com","user2@domain.com"} -``` - -Adds a new list item to the "Demo List" and sets the user field called MultiUserField to 2 users. Separate multiple users with a comma. - -### ------------------EXAMPLE 4------------------ -```powershell -Add-PnPListItem -List "Demo List" -Values @{"Title"="Sales Report"} -Folder "projects/europe" -``` - -Adds a new list item to the "Demo List". It will add the list item to the europe folder which is located in the projects folder. Folders will be created if needed. - -### ------------------EXAMPLE 5------------------ -```powershell -Add-PnPListItem -List "Demo List" -Values @{"Title"="Sales Report"} -Label "Public" -``` - -Adds a new list item to the "Demo List". Sets the retention label to "Public" if it exists on the site. - -## PARAMETERS - -### -ContentType -Specify either the name, ID or an actual content type. - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Folder -The list relative URL of a folder. E.g. "MyFolder" for a folder located in the root of the list, or "MyFolder/SubFolder" for a folder located in the MyFolder folder which is located in the root of the list. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Label -The name of the retention label. - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Values -Use the internal names of the fields when specifying field names. - -Single line of text: -Values @{"Title" = "Title New"} - -Multiple lines of text: -Values @{"MultiText" = "New text\n\nMore text"} - -Rich text: -Values @{"MultiText" = "<strong>New</strong> text"} - -Choice: -Values @{"Choice" = "Value 1"} - -Number: -Values @{"Number" = "10"} - -Currency: -Values @{"Number" = "10"} - -Currency: -Values @{"Currency" = "10"} - -Date and Time: -Values @{"DateAndTime" = "03/13/2015 14:16"} - -Lookup (id of lookup value): -Values @{"Lookup" = "2"} - -Multi value lookup (id of lookup values as array 1): -Values @{"MultiLookupField" = "1","2"} - -Multi value lookup (id of lookup values as array 2): -Values @{"MultiLookupField" = 1,2} - -Multi value lookup (id of lookup values as string): -Values @{"MultiLookupField" = "1,2"} - -Yes/No: -Values @{"YesNo" = $false} - -Person/Group (id of user/group in Site User Info List or email of the user, separate multiple values with a comma): -Values @{"Person" = "user1@domain.com","21"} - -Managed Metadata (single value with path to term): -Values @{"MetadataField" = "CORPORATE|DEPARTMENTS|FINANCE"} - -Managed Metadata (single value with id of term): -Values @{"MetadataField" = "fe40a95b-2144-4fa2-b82a-0b3d0299d818"} with Id of term - -Managed Metadata (multiple values with paths to terms): -Values @{"MetadataField" = "CORPORATE|DEPARTMENTS|FINANCE","CORPORATE|DEPARTMENTS|HR"} - -Managed Metadata (multiple values with ids of terms): -Values @{"MetadataField" = "fe40a95b-2144-4fa2-b82a-0b3d0299d818","52d88107-c2a8-4bf0-adfa-04bc2305b593"} - -Hyperlink or Picture: -Values @{"Hyperlink" = "https://github.com/OfficeDev/,%20OfficePnp"} - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.ListItem - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPMasterPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPMasterPage.md deleted file mode 100644 index 96d6c45865..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPMasterPage.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpmasterpage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPMasterPage ---- - -# Add-PnPMasterPage - -## SYNOPSIS -Adds a Masterpage - -## SYNTAX - -```powershell -Add-PnPMasterPage -SourceFilePath <String> - -Title <String> - -Description <String> - [-DestinationFolderHierarchy <String>] - [-UIVersion <String>] - [-DefaultCssFile <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPMasterPage -SourceFilePath "page.master" -Title "MasterPage" -Description "MasterPage for Web" -DestinationFolderHierarchy "SubFolder" -``` - -Adds a MasterPage from the local file "page.master" to the folder "SubFolder" in the Masterpage gallery. - -## PARAMETERS - -### -DefaultCssFile -Default CSS file for the MasterPage, this Url is SiteRelative - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -Description for the Masterpage - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DestinationFolderHierarchy -Folder hierarchy where the MasterPage will be deployed - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SourceFilePath -Path to the file which will be uploaded - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -Title for the Masterpage - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -UIVersion -UIVersion of the Masterpage. Default = 15 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.File - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPNavigationNode.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPNavigationNode.md deleted file mode 100644 index 144c325b40..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPNavigationNode.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpnavigationnode -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPNavigationNode ---- - -# Add-PnPNavigationNode - -## SYNOPSIS -Adds an item to a navigation element - -## SYNTAX - -```powershell -Add-PnPNavigationNode -Location <NavigationType> - -Title <String> - [-Url <String>] - [-Parent <Int>] - [-First [<SwitchParameter>]] - [-External [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a menu item to either the quicklaunch or top navigation - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPNavigationNode -Title "Contoso" -Url "http://contoso.sharepoint.com/sites/contoso/" -Location "QuickLaunch" -``` - -Adds a navigation node to the quicklaunch. The navigation node will have the title "Contoso" and will link to the url "http://contoso.sharepoint.com/sites/contoso/" - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPNavigationNode -Title "Contoso USA" -Url "http://contoso.sharepoint.com/sites/contoso/usa/" -Location "QuickLaunch" -Parent 2012 -``` - -Adds a navigation node to the quicklaunch. The navigation node will have the title "Contoso USA", will link to the url "http://contoso.sharepoint.com/sites/contoso/usa/" and will have the node with id 2012 as a parent navigation node. - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPNavigationNode -Title "Contoso" -Url "http://contoso.sharepoint.com/sites/contoso/" -Location "QuickLaunch" -First -``` - -Adds a navigation node to the quicklaunch, as the first item. The navigation node will have the title "Contoso" and will link to the url "http://contoso.sharepoint.com/sites/contoso/" - -### ------------------EXAMPLE 4------------------ -```powershell -Add-PnPNavigationNode -Title "Contoso Pharmaceuticals" -Url "http://contoso.sharepoint.com/sites/contosopharma/" -Location "QuickLaunch" -External -``` - -Adds a navigation node to the quicklaunch. The navigation node will have the title "Contoso Pharmaceuticals" and will link to the external url "http://contoso.sharepoint.com/sites/contosopharma/" - -### ------------------EXAMPLE 5------------------ -```powershell -Add-PnPNavigationNode -Title "Wiki" -Location "QuickLaunch" -Url "wiki/" -``` - -Adds a navigation node to the quicklaunch. The navigation node will have the title "Wiki" and will link to Wiki library on the selected Web. - -## PARAMETERS - -### -External -Indicates the destination URL is outside of the site collection. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -First -Add the new menu item to beginning of the collection. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Location -The location of the node to add. Either TopNavigationBar, QuickLaunch, SearchNav - -```yaml -Type: NavigationType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Parent -The key of the parent. Leave empty to add to the top level - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the node to add - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -The url to navigate to when clicking the new menu item. This can either be absolute or relative to the Web. Fragments are not supported. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.NavigationNode - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOffice365GroupToSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOffice365GroupToSite.md deleted file mode 100644 index aa5c1079ac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOffice365GroupToSite.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpoffice365grouptosite -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPOffice365GroupToSite ---- - -# Add-PnPOffice365GroupToSite - -## SYNOPSIS -Groupifies a classic team site by creating an Office 365 group for it and connecting the site with the newly created group - -## SYNTAX - -```powershell -Add-PnPOffice365GroupToSite -Url <String> - -Alias <String> - -DisplayName <String> - [-Description <String>] - [-Classification <String>] - [-IsPublic [<SwitchParameter>]] - [-KeepOldHomePage [<SwitchParameter>]] - [-HubSiteId <GuidPipeBind>] - [-Owners <String[]>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows you to add an Office 365 Unified group to an existing classic site collection. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPOffice365GroupToSite -Url "https://contoso.sharepoint.com/sites/FinanceTeamsite" -Alias "FinanceTeamsite" -DisplayName = "My finance team site group" -``` - -This will add a group called MyGroup to the current site collection - -## PARAMETERS - -### -Alias -Specifies the alias of the group. Cannot contain spaces. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Classification -Specifies the classification of the group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The optional description of the group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisplayName -The display name of the group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -HubSiteId -If specified the site will be associated to the hubsite as identified by this id - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IsPublic -Specifies if the group is public. Defaults to false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -KeepOldHomePage -Specifies if the current site home page is kept. Defaults to false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owners -The array UPN values of the group's owners. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -Url of the site to be connected to an Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOrgAssetsLibrary.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOrgAssetsLibrary.md deleted file mode 100644 index bf7debcf1d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOrgAssetsLibrary.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnporgassetslibrary -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPOrgAssetsLibrary ---- - -# Add-PnPOrgAssetsLibrary - -## SYNOPSIS -Adds a given document library as a organizational asset source - -## SYNTAX - -```powershell -Add-PnPOrgAssetsLibrary -LibraryUrl <String> - [-ThumbnailUrl <String>] - [-CdnType <SPOTenantCdnType>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a given document library as an organizational asset source in your Sharepoint Online Tenant. All organizational asset sources you add must reside in the same site collection. Document libraries specified as organizational asset must be enabled as an Office 365 CDN source, either as private or public. It may take some time before this change will be reflected in the webinterface. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPOrgAssetsLibrary -LibraryUrl https://yourtenant.sharepoint.com/sites/branding/logos -``` - -Adds the document library with the url "logos" located in the sitecollection at "https://yourtenant.sharepoint.com/sites/branding" as an organizational asset not specifying a thumbnail image for it and enabling the document library as a public Office 365 CDN source - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPOrgAssetsLibrary -LibraryUrl https://yourtenant.sharepoint.com/sites/branding/logos -ThumbnailUrl https://yourtenant.sharepoint.com/sites/branding/logos/thumbnail.jpg -``` - -Adds the document library with the url "logos" located in the sitecollection at "https://yourtenant.sharepoint.com/sites/branding" as an organizational asset specifying the thumbnail image "thumbnail.jpg" residing in the same document library for it and enabling the document library as a public Office 365 CDN source - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPOrgAssetsLibrary -LibraryUrl https://yourtenant.sharepoint.com/sites/branding/logos -CdnType Private -``` - -Adds the document library with the url "logos" located in the sitecollection at "https://yourtenant.sharepoint.com/sites/branding" as an organizational asset not specifying a thumbnail image for it and enabling the document library as a private Office 365 CDN source - -## PARAMETERS - -### -CdnType -Indicates what type of Office 365 CDN source the document library will be added to - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LibraryUrl -The full url of the document library to be marked as one of organization's assets sources - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ThumbnailUrl -The full url to an image that should be used as a thumbnail for showing this source. The image must reside in the same site as the document library you specify. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOrgNewsSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOrgNewsSite.md deleted file mode 100644 index f24c7b6aad..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPOrgNewsSite.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnporgnewssite -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPOrgNewsSite ---- - -# Add-PnPOrgNewsSite - -## SYNOPSIS -Adds the site as an organization news source in your tenant - -## SYNTAX - -```powershell -Add-PnPOrgNewsSite -OrgNewsSiteUrl <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPOrgNewsSite -OrgNewsSiteUrl https://yourtenant.sharepoint.com/sites/news -``` - -Adds the site as one of multiple possible tenant's organizational news sites - -## PARAMETERS - -### -OrgNewsSiteUrl -The url of the site to be marked as one of organization's news sites - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningTemplate.md deleted file mode 100644 index 5f8ba3b421..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningTemplate.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpprovisioningtemplate -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPProvisioningTemplate ---- - -# Add-PnPProvisioningTemplate - -## SYNOPSIS -Adds a PnP Provisioning Template object to a tenant template - -## SYNTAX - -```powershell -Add-PnPProvisioningTemplate -SiteTemplate <ProvisioningTemplate> - -TenantTemplate <ProvisioningHierarchy> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnpProvisioningTemplate -TenantTemplate $tenanttemplate -SiteTemplate $sitetemplate -``` - -Adds an existing site template to an existing tenant template object - -## PARAMETERS - -### -SiteTemplate -The template to add to the tenant template - -```yaml -Type: ProvisioningTemplate -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TenantTemplate -The tenant template to add the template to - -```yaml -Type: ProvisioningHierarchy -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingImageRendition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingImageRendition.md deleted file mode 100644 index 7ec2f024ed..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingImageRendition.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnppublishingimagerendition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPPublishingImageRendition ---- - -# Add-PnPPublishingImageRendition - -## SYNOPSIS -Adds an Image Rendition if the Name of the Image Rendition does not already exist. This prevents creating two Image Renditions that share the same name. - -## SYNTAX - -```powershell -Add-PnPPublishingImageRendition -Name <String> - -Width <Int> - -Height <Int> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPPublishingImageRendition -Name "MyImageRendition" -Width 800 -Height 600 -``` - - - -## PARAMETERS - -### -Height -The height of the Image Rendition. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Name -The display name of the Image Rendition. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Width -The width of the Image Rendition. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPage.md deleted file mode 100644 index 0425a5de6b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPage.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnppublishingpage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPPublishingPage ---- - -# Add-PnPPublishingPage - -## SYNOPSIS -Adds a publishing page - -## SYNTAX - -### WithTitle -```powershell -Add-PnPPublishingPage -PageName <String> - -PageTemplateName <String> - [-Title <String>] - [-FolderPath <String>] - [-Publish [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPPublishingPage -PageName 'OurNewPage' -Title 'Our new page' -PageTemplateName 'ArticleLeft' -``` - -Creates a new page based on the pagelayout 'ArticleLeft' - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPPublishingPage -PageName 'OurNewPage' -Title 'Our new page' -PageTemplateName 'ArticleLeft' -Folder '/Pages/folder' -``` - -Creates a new page based on the pagelayout 'ArticleLeft' with a site relative folder path - -## PARAMETERS - -### -FolderPath -The site relative folder path of the page to be added - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Folder - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PageName -The name of the page to be added as an aspx file - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Name - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PageTemplateName -The name of the page layout you want to use. Specify without the .aspx extension. So 'ArticleLeft' or 'BlankWebPartPage' - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Publish -Publishes the page. Also Approves it if moderation is enabled on the Pages library. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the page - -```yaml -Type: String -Parameter Sets: WithTitle - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPageLayout.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPageLayout.md deleted file mode 100644 index 1145da5d1a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPPublishingPageLayout.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnppublishingpagelayout -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPPublishingPageLayout ---- - -# Add-PnPPublishingPageLayout - -## SYNOPSIS -Adds a publishing page layout - -## SYNTAX - -```powershell -Add-PnPPublishingPageLayout -SourceFilePath <String> - -Title <String> - -Description <String> - -AssociatedContentTypeID <String> - [-DestinationFolderHierarchy <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPPublishingPageLayout -Title 'Our custom page layout' -SourceFilePath 'customlayout.aspx' -Description 'A custom page layout' -AssociatedContentTypeID 0x01010901 -``` - -Uploads the pagelayout 'customlayout.aspx' to the current site as a 'web part page' pagelayout - -## PARAMETERS - -### -AssociatedContentTypeID -Associated content type ID - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Description -Description for the page layout - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DestinationFolderHierarchy -Folder hierarchy where the html page layouts will be deployed - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SourceFilePath -Path to the file which will be uploaded - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -Title for the page layout - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPRoleDefinition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPRoleDefinition.md deleted file mode 100644 index eb1559fd62..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPRoleDefinition.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnproledefinition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPRoleDefinition ---- - -# Add-PnPRoleDefinition - -## SYNOPSIS -Adds a Role Defintion (Permission Level) to the site collection in the current context - -## SYNTAX - -```powershell -Add-PnPRoleDefinition -RoleName <String> - [-Clone <RoleDefinitionPipeBind>] - [-Include <PermissionKind[]>] - [-Exclude <PermissionKind[]>] - [-Description <String>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows adding a custom Role Defintion (Permission Level) to the site collection in the current context. It does not replace or remove existing Role Definitions. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPRoleDefinition -RoleName "CustomPerm" -``` - -Creates additional permission level with no permission flags enabled. - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPRoleDefinition -RoleName "NoDelete" -Clone "Contribute" -Exclude DeleteListItems -``` - -Creates additional permission level by cloning "Contribute" and removes flags DeleteListItems - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPRoleDefinition -RoleName "AddOnly" -Clone "Contribute" -Exclude DeleteListItems, EditListItems -``` - -Creates additional permission level by cloning "Contribute" and removes flags DeleteListItems and EditListItems - -### ------------------EXAMPLE 4------------------ -```powershell -$roleDefinition = Get-PnPRoleDefinition -Identity "Contribute" -Add-PnPRoleDefinition -RoleName "AddOnly" -Clone $roleDefinition -Exclude DeleteListItems, EditListItems -``` - -Creates additional permission level by cloning "Contribute" and removes flags DeleteListItems and EditListItems - -## PARAMETERS - -### -Clone -An existing permission level or the name of an permission level to clone as base template. - -```yaml -Type: RoleDefinitionPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -Optional description for the new permission level. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Exclude -Specifies permission flags(s) to disable. Please visit https://docs.microsoft.com/previous-versions/office/sharepoint-csom/ee536458(v%3Doffice.15) for the PermissionKind enum - -```yaml -Type: PermissionKind[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Include -Specifies permission flags(s) to enable. Please visit https://docs.microsoft.com/previous-versions/office/sharepoint-csom/ee536458(v%3Doffice.15) for the PermissionKind enum - -```yaml -Type: PermissionKind[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RoleName -Name of new permission level. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteClassification.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteClassification.md deleted file mode 100644 index ffb6455f9a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteClassification.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpsiteclassification -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPSiteClassification ---- - -# Add-PnPSiteClassification - -## SYNOPSIS -Adds one ore more site classification values to the list of possible values. Requires a connection to the Microsoft Graph. - -## SYNTAX - -```powershell -Add-PnPSiteClassification -Classifications <String> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Add-PnPSiteClassification -Classifications "Top Secret" -``` - -Adds the "Top Secret" classification to the already existing classification values. - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Add-PnPSiteClassification -Classifications "Top Secret","HBI" -``` - -Adds the "Top Secret" and the "For Your Eyes Only" classification to the already existing classification values. - -## PARAMETERS - -### -Classifications - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAdmin.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAdmin.md deleted file mode 100644 index 0d08874487..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAdmin.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpsitecollectionadmin -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPSiteCollectionAdmin ---- - -# Add-PnPSiteCollectionAdmin - -## SYNOPSIS -Adds one or more users as site collection administrators to the site collection in the current context - -## SYNTAX - -```powershell -Add-PnPSiteCollectionAdmin -Owners <UserPipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows adding one to many users as site collection administrators to the site collection in the current context. It does not replace or remove existing site collection administrators. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPSiteCollectionAdmin -Owners "user@contoso.onmicrosoft.com" -``` - -This will add user@contoso.onmicrosoft.com as an additional site collection owner to the site collection in the current context - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPSiteCollectionAdmin -Owners @("user1@contoso.onmicrosoft.com", "user2@contoso.onmicrosoft.com") -``` - -This will add user1@contoso.onmicrosoft.com and user2@contoso.onmicrosoft.com as additional site collection owners to the site collection in the current context - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPUser | ? Title -Like "*Doe" | Add-PnPSiteCollectionAdmin -``` - -This will add all users with their title ending with "Doe" as additional site collection owners to the site collection in the current context - -## PARAMETERS - -### -Owners -Specifies owner(s) to add as site collection administrators. They will be added as additional site collection administrators to the site in the current context. Existing administrators will stay. Can be both users and groups. - -```yaml -Type: UserPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAppCatalog.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAppCatalog.md deleted file mode 100644 index d67eeb4bf8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteCollectionAppCatalog.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpsitecollectionappcatalog -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPSiteCollectionAppCatalog ---- - -# Add-PnPSiteCollectionAppCatalog - -## SYNOPSIS -Adds a Site Collection scoped App Catalog to a site - -## SYNTAX - -```powershell -Add-PnPSiteCollectionAppCatalog -Site <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPSiteCollectionAppCatalog -Site "https://contoso.sharepoint.com/sites/FinanceTeamsite" -``` - -This will add a SiteCollection app catalog to the specified site - -## PARAMETERS - -### -Site -Url of the site to add the app catalog to. - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesign.md deleted file mode 100644 index 9a91dc60d4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesign.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpsitedesign -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPSiteDesign ---- - -# Add-PnPSiteDesign - -## SYNOPSIS -Creates a new Site Design on the current tenant. - -## SYNTAX - -```powershell -Add-PnPSiteDesign -Title <String> - -SiteScriptIds <GuidPipeBind[]> - -WebTemplate <SiteWebTemplate> - [-Description <String>] - [-IsDefault [<SwitchParameter>]] - [-PreviewImageAltText <String>] - [-PreviewImageUrl <String>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPSiteDesign -Title "My Company Design" -SiteScriptIds "e84dcb46-3ab9-4456-a136-66fc6ae3d3c5","6def687f-0e08-4f1e-999c-791f3af9a600" -Description "My description" -WebTemplate TeamSite -``` - -Adds a new Site Design, with the specified title and description. When applied it will run the scripts as referenced by the IDs. Use Get-PnPSiteScript to receive Site Scripts. The WebTemplate parameter specifies that this design applies to Team Sites. - -## PARAMETERS - -### -Description -The description of the site design - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IsDefault -Specifies if the site design is a default site design - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PreviewImageAltText -Sets the text for the preview image - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PreviewImageUrl -Sets the url to the preview image - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SiteScriptIds -An array of guids of site scripts - -```yaml -Type: GuidPipeBind[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the site design - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -WebTemplate -Specifies the type of site to which this design applies - -```yaml -Type: SiteWebTemplate -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesignTask.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesignTask.md deleted file mode 100644 index 040f6e574b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteDesignTask.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpsitedesigntask -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPSiteDesignTask ---- - -# Add-PnPSiteDesignTask - -## SYNOPSIS -This command is used to apply a published site design to a specified site collection target. It schedules the operation, allowing for the application of larger site scripts (Invoke-PnPSiteDesign is limited to 30 actions and subactions). -This command is intended to replace Invoke-PnPSiteDesign and is useful when you need to apply a large number of actions or multiple site scripts. - -## SYNTAX - -```powershell -Add-PnPSiteDesignTask -SiteDesignId <GuidPipeBind> - [-WebUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPSiteDesignTask -SiteDesignId 501z8c32-4147-44d4-8607-26c2f67cae82 -``` - -This example applies a site design the currently connected to site. Executing the commands will schedule the site design to be queued and run against the designated site collection. - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPSiteDesignTask -SiteDesignId 501z8c32-4147-44d4-8607-26c2f67cae82 -WebUrl "https://contoso.sharepoint.com/sites/project" -``` - -This example applies a site design to the designated site. Executing the commands will schedule the site design to be queued and run against the designated site collection. - -## PARAMETERS - -### -SiteDesignId -The ID of the site design to apply. - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -WebUrl -The URL of the site collection where the site design will be applied. If not specified the design will be applied to the site you connected to with Connect-PnPOnline. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteScript.md deleted file mode 100644 index 8055346b8a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPSiteScript.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpsitescript -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPSiteScript ---- - -# Add-PnPSiteScript - -## SYNOPSIS -Creates a new Site Script on the current tenant. - -## SYNTAX - -```powershell -Add-PnPSiteScript -Title <String> - -Content <String> - [-Description <String>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPSiteScript -Title "My Site Script" -Description "A more detailed description" -Content $script -``` - -Adds a new Site Script, where $script variable contains the script. - -## PARAMETERS - -### -Content -A JSON string containing the site script - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Description -The description of the site script - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the site script - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPStoredCredential.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPStoredCredential.md deleted file mode 100644 index df4155f281..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPStoredCredential.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpstoredcredential -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPStoredCredential ---- - -# Add-PnPStoredCredential - -## SYNOPSIS -Adds a credential to the Windows Credential Manager - -## SYNTAX - -```powershell -Add-PnPStoredCredential -Name <String> - -Username <String> - [-Password <SecureString>] -``` - -## DESCRIPTION -Adds an entry to the Windows Credential Manager. If you add an entry in the form of the URL of your tenant/server PnP PowerShell will check if that entry is available when you connect using Connect-PnPOnline. If it finds a matching URL it will use the associated credentials. - -If you add a Credential with a name of "https://yourtenant.sharepoint.com/" it will find a match when you connect to "https://yourtenant.sharepoint.com/" but also when you connect to "https://yourtenant.sharepoint.com/sites/demo1". Of course you can specify more granular entries, allow you to automatically provide credentials for different URLs. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPStoredCredential -Name https://tenant.sharepoint.com -Username yourname@tenant.onmicrosoft.com -``` - -You will be prompted to specify the password and a new entry will be added with the specified values - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPStoredCredential -Name https://tenant.sharepoint.com -Username yourname@tenant.onmicrosoft.com -Password (ConvertTo-SecureString -String "YourPassword" -AsPlainText -Force) -``` - -A new entry will be added with the specified values - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPStoredCredential -Name https://tenant.sharepoint.com -Username yourname@tenant.onmicrosoft.com -Password (ConvertTo-SecureString -String "YourPassword" -AsPlainText -Force) -Connect-PnPOnline -Url https://tenant.sharepoint.com/sites/mydemosite -``` - -A new entry will be added with the specified values, and a subsequent connection to a sitecollection starting with the entry name will be made. Notice that no password prompt will occur. - -## PARAMETERS - -### -Name -The credential to set - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Password -If not specified you will be prompted to enter your password. -If you want to specify this value use ConvertTo-SecureString -String 'YourPassword' -AsPlainText -Force - -```yaml -Type: SecureString -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Username - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTaxonomyField.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTaxonomyField.md deleted file mode 100644 index c4a4e8a591..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTaxonomyField.md +++ /dev/null @@ -1,237 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnptaxonomyfield -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPTaxonomyField ---- - -# Add-PnPTaxonomyField - -## SYNOPSIS -Add a taxonomy field - -## SYNTAX - -### Id -```powershell -Add-PnPTaxonomyField -DisplayName <String> - -InternalName <String> - [-TaxonomyItemId <GuidPipeBind>] - [-List <ListPipeBind>] - [-Group <String>] - [-Id <GuidPipeBind>] - [-AddToDefaultView [<SwitchParameter>]] - [-MultiValue [<SwitchParameter>]] - [-Required [<SwitchParameter>]] - [-FieldOptions <AddFieldOptions>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Path -```powershell -Add-PnPTaxonomyField -TermSetPath <String> - -DisplayName <String> - -InternalName <String> - [-TermPathDelimiter <String>] - [-List <ListPipeBind>] - [-Group <String>] - [-Id <GuidPipeBind>] - [-AddToDefaultView [<SwitchParameter>]] - [-MultiValue [<SwitchParameter>]] - [-Required [<SwitchParameter>]] - [-FieldOptions <AddFieldOptions>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds a taxonomy/managed metadata field to a list or as a site column. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPTaxonomyField -DisplayName "Test" -InternalName "Test" -TermSetPath "TestTermGroup|TestTermSet" -``` - -Adds a new taxonomy field called "Test" that points to the TestTermSet which is located in the TestTermGroup - -## PARAMETERS - -### -AddToDefaultView -Switch Parameter if this field must be added to the default view - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisplayName -The display name of the field - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -FieldOptions -Specifies the control settings while adding a field. See https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.addfieldoptions.aspx for details - -```yaml -Type: AddFieldOptions -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Group -The group name to where this field belongs to - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Id -The ID for the field, must be unique - -```yaml -Type: GuidPipeBind -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -InternalName -The internal name of the field - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The list object or name where this field needs to be added - -```yaml -Type: ListPipeBind -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MultiValue -Switch Parameter if this Taxonomy field can hold multiple values - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Required -Switch Parameter if the field is a required field - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TaxonomyItemId -The ID of the Taxonomy item - -```yaml -Type: GuidPipeBind -Parameter Sets: Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermPathDelimiter -The path delimiter to be used, by default this is '|' - -```yaml -Type: String -Parameter Sets: Path - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermSetPath -The path to the term that this needs to be bound - -```yaml -Type: String -Parameter Sets: Path - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Field - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTeamsTeam.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTeamsTeam.md deleted file mode 100644 index bc95ff6813..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTeamsTeam.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpteamsteam -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPTeamsTeam ---- - -# Add-PnPTeamsTeam - -## SYNOPSIS -Adds a Teams team to an existing, group connected, site collection - -## SYNTAX - -```powershell -Add-PnPTeamsTeam [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows you to add a Teams team to an existing, Office 365 group connected, site collection. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPTeamsTeam -``` - -This create a teams team for the connected site collection - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantCdnOrigin.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantCdnOrigin.md deleted file mode 100644 index 3d7f846ee9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantCdnOrigin.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnptenantcdnorigin -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPTenantCdnOrigin ---- - -# Add-PnPTenantCdnOrigin - -## SYNOPSIS -Adds a new origin to the public or private content delivery network (CDN). - -## SYNTAX - -```powershell -Add-PnPTenantCdnOrigin -OriginUrl <String> - -CdnType <SPOTenantCdnType> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Add a new origin to the public or private CDN, on either Tenant level or on a single Site level. Effectively, a tenant admin points out to a document library, or a folder in the document library and requests that content in that library should be retrievable by using a CDN. - -You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPTenantCdnOrigin -OriginUrl /sites/site/subfolder -CdnType Public -``` - -This example configures a public CDN on site level. - -## PARAMETERS - -### -CdnType -Specifies the CDN type. The valid values are: public or private. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -OriginUrl -Specifies a path to the doc library to be configured. It can be provided in two ways: relative path, or a mask. - -Relative-Relative path depends on the OriginScope. If the originScope is Tenant, a path must be a relative path under the tenant root. If the originScope is Site, a path must be a relative path under the given Site. The path must point to the valid Document Library or a folder with a document library. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequence.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequence.md deleted file mode 100644 index f3a1a14290..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequence.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnptenantsequence -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPTenantSequence ---- - -# Add-PnPTenantSequence - -## SYNOPSIS -Adds a tenant sequence object to a tenant template - -## SYNTAX - -```powershell -Add-PnPTenantSequence -Template <ProvisioningHierarchy> - -Sequence <ProvisioningSequence> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPTenantSequence -Template $mytemplate -Sequence $mysequence -``` - -Adds an existing sequence object to an existing template object - -### ------------------EXAMPLE 2------------------ -```powershell -New-PnPTenantSequence -Id "MySequence" | Add-PnPTenantSequence -Template $template -``` - -Creates a new instance of a provisioning sequence object and sets the Id to the value specified, then the sequence is added to an existing template object - -## PARAMETERS - -### -Sequence -Optional Id of the sequence - -```yaml -Type: ProvisioningSequence -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Template -The template to add the sequence to - -```yaml -Type: ProvisioningHierarchy -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSite.md deleted file mode 100644 index 9e0967a449..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSite.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnptenantsequencesite -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPTenantSequenceSite ---- - -# Add-PnPTenantSequenceSite - -## SYNOPSIS -Adds a existing tenant sequence site object to a tenant template - -## SYNTAX - -```powershell -Add-PnPTenantSequenceSite -Site <ProvisioningSitePipeBind> - -Sequence <ProvisioningSequence> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPTenantSequenceSite -Site $myteamsite -Sequence $mysequence -``` - -Adds an existing site object to an existing template sequence - -## PARAMETERS - -### -Sequence -The sequence to add the site to - -```yaml -Type: ProvisioningSequence -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Site - - -```yaml -Type: ProvisioningSitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSubSite.md deleted file mode 100644 index 25fdc4875e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantSequenceSubSite.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnptenantsequencesubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPTenantSequenceSubSite ---- - -# Add-PnPTenantSequenceSubSite - -## SYNOPSIS -Adds a tenant sequence sub site object to a tenant sequence site object - -## SYNTAX - -```powershell -Add-PnPTenantSequenceSubSite -SubSite <TeamNoGroupSubSite> - -Site <SiteCollection> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPTenantSequenceSubSite -Site $mysite -SubSite $mysubsite -``` - -Adds an existing subsite object to an existing sequence site object - -## PARAMETERS - -### -Site -The site to add the subsite to - -```yaml -Type: SiteCollection -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -SubSite -The subsite to add - -```yaml -Type: TeamNoGroupSubSite -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantTheme.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantTheme.md deleted file mode 100644 index f12d81b330..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPTenantTheme.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnptenanttheme -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPTenantTheme ---- - -# Add-PnPTenantTheme - -## SYNOPSIS -Adds or updates a theme to the tenant. - -## SYNTAX - -```powershell -Add-PnPTenantTheme -Identity <ThemePipeBind> - -Palette <ThemePalettePipeBind> - -IsInverted <Boolean> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Adds or updates a theme to the tenant. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$themepalette = @{ - "themePrimary" = "#00ffff"; - "themeLighterAlt" = "#f3fcfc"; - "themeLighter" = "#daffff"; - "themeLight" = "#affefe"; - "themeTertiary" = "#76ffff"; - "themeSecondary" = "#39ffff"; - "themeDarkAlt" = "#00c4c4"; - "themeDark" = "#009090"; - "themeDarker" = "#005252"; - "neutralLighterAlt" = "#f8f8f8"; - "neutralLighter" = "#f4f4f4"; - "neutralLight" = "#eaeaea"; - "neutralQuaternaryAlt" = "#dadada"; - "neutralQuaternary" = "#d0d0d0"; - "neutralTertiaryAlt" = "#c8c8c8"; - "neutralTertiary" = "#a6a6a6"; - "neutralSecondaryAlt" = "#767676"; - "neutralSecondary" = "#666666"; - "neutralPrimary" = "#333"; - "neutralPrimaryAlt" = "#3c3c3c"; - "neutralDark" = "#212121"; - "black" = "#000000"; - "white" = "#fff"; - "primaryBackground" = "#fff"; - "primaryText" = "#333" - } -PS:>Add-PnPTenantTheme -Identity "MyCompanyTheme" -Palette $themepalette -IsInverted $false -``` - -This example adds a theme to the current tenant. - -## PARAMETERS - -### -Identity -The name of the theme to add or update - -```yaml -Type: ThemePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -IsInverted -If the theme is inverted or not - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Palette -The palette to add. See examples for more information. - -```yaml -Type: ThemePalettePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPUserToGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPUserToGroup.md deleted file mode 100644 index 146c9afe95..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPUserToGroup.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpusertogroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPUserToGroup ---- - -# Add-PnPUserToGroup - -## SYNOPSIS -Adds a user to a group - -## SYNTAX - -### Internal -```powershell -Add-PnPUserToGroup -LoginName <String> - -Identity <GroupPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### External -```powershell -Add-PnPUserToGroup -Identity <GroupPipeBind> - -EmailAddress <String> - [-SendEmail [<SwitchParameter>]] - [-EmailBody <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPUserToGroup -LoginName user@company.com -Identity 'Marketing Site Members' -``` - -Add the specified user to the group "Marketing Site Members" - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPUserToGroup -LoginName user@company.com -Identity 5 -``` - -Add the specified user to the group with Id 5 - -## PARAMETERS - -### -EmailAddress -The email address of the user - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: External - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -EmailBody - - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: External - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The group id, group name or group object to add the user to. - -```yaml -Type: GroupPipeBind -Parameter Sets: Internal, External - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -LoginName -The login name of the user - -```yaml -Type: String -Parameter Sets: Internal - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -SendEmail - - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: External - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPView.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPView.md deleted file mode 100644 index 95da7ec324..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPView.md +++ /dev/null @@ -1,206 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpview -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPView ---- - -# Add-PnPView - -## SYNOPSIS -Adds a view to a list - -## SYNTAX - -```powershell -Add-PnPView -List <ListPipeBind> - -Title <String> - -Fields <String[]> - [-Query <String>] - [-ViewType <ViewType>] - [-RowLimit <UInt32>] - [-Personal [<SwitchParameter>]] - [-SetAsDefault [<SwitchParameter>]] - [-Paged [<SwitchParameter>]] - [-Aggregations <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPView -List "Demo List" -Title "Demo View" -Fields "Title","Address" -``` - -Adds a view named "Demo view" to the "Demo List" list. - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPView -List "Demo List" -Title "Demo View" -Fields "Title","Address" -Paged -``` - -Adds a view named "Demo view" to the "Demo List" list and makes sure there's paging on this view. - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPView -List "Demo List" -Title "Demo View" -Fields "Title","Address" -Aggregations "<FieldRef Name='Title' Type='COUNT'/>" -``` - -Adds a view named "Demo view" to the "Demo List" list and sets the totals (aggregations) to Count on the Title field. - -## PARAMETERS - -### -Aggregations -A valid XML fragment containing one or more Aggregations - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Fields -A list of fields to add. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The ID or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Paged -If specified, the view will have paging. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Personal -If specified, a personal view will be created. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Query -A valid CAML Query. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RowLimit -The row limit for the view. Defaults to 30. - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SetAsDefault -If specified, the view will be set as the default view for the list. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the view. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ViewType -The type of view to add. - -```yaml -Type: ViewType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.View - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWebPartPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWebPartPage.md deleted file mode 100644 index 243e92e9b7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWebPartPage.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpwebparttowebpartpage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPWebPartToWebPartPage ---- - -# Add-PnPWebPartToWebPartPage - -## SYNOPSIS -Adds a web part to a web part page in a specified zone - -## SYNTAX - -### XML -```powershell -Add-PnPWebPartToWebPartPage -Xml <String> - -ServerRelativePageUrl <String> - -ZoneId <String> - -ZoneIndex <Int> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### FILE -```powershell -Add-PnPWebPartToWebPartPage -Path <String> - -ServerRelativePageUrl <String> - -ZoneId <String> - -ZoneIndex <Int> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPWebPartToWebPartPage -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -Path "c:\myfiles\listview.webpart" -ZoneId "Header" -ZoneIndex 1 -``` - -This will add the web part as defined by the XML in the listview.webpart file to the specified page in the specified zone and with the order index of 1 - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPWebPartToWebPartPage -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -XML $webpart -ZoneId "Header" -ZoneIndex 1 -``` - -This will add the web part as defined by the XML in the $webpart variable to the specified page in the specified zone and with the order index of 1 - -## PARAMETERS - -### -Path -A path to a web part file on a the file system. - -```yaml -Type: String -Parameter Sets: FILE - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -Server Relative Url of the page to add the web part to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Xml -A string containing the XML for the web part. - -```yaml -Type: String -Parameter Sets: XML - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ZoneId -The Zone Id where the web part must be placed - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ZoneIndex -The Zone Index where the web part must be placed - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWikiPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWikiPage.md deleted file mode 100644 index eba566ea63..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebPartToWikiPage.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpwebparttowikipage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPWebPartToWikiPage ---- - -# Add-PnPWebPartToWikiPage - -## SYNOPSIS -Adds a web part to a wiki page in a specified table row and column - -## SYNTAX - -### XML -```powershell -Add-PnPWebPartToWikiPage -Xml <String> - -ServerRelativePageUrl <String> - -Row <Int> - -Column <Int> - [-AddSpace [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### FILE -```powershell -Add-PnPWebPartToWikiPage -Path <String> - -ServerRelativePageUrl <String> - -Row <Int> - -Column <Int> - [-AddSpace [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPWebPartToWikiPage -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -Path "c:\myfiles\listview.webpart" -Row 1 -Column 1 -``` - -This will add the web part as defined by the XML in the listview.webpart file to the specified page in the first row and the first column of the HTML table present on the page - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPWebPartToWikiPage -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -XML $webpart -Row 1 -Column 1 -``` - -This will add the web part as defined by the XML in the $webpart variable to the specified page in the first row and the first column of the HTML table present on the page - -## PARAMETERS - -### -AddSpace -Must there be a extra space between the web part - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Column -Column number where the web part must be placed - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Path -A path to a web part file on a the file system. - -```yaml -Type: String -Parameter Sets: FILE - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Row -Row number where the web part must be placed - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -Full server relative url of the web part page, e.g. /sites/demo/sitepages/home.aspx - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Xml -A string containing the XML for the web part. - -```yaml -Type: String -Parameter Sets: XML - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebhookSubscription.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebhookSubscription.md deleted file mode 100644 index a745fa7fee..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWebhookSubscription.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpwebhooksubscription -applicable: SharePoint Online -schema: 2.0.0 -title: Add-PnPWebhookSubscription ---- - -# Add-PnPWebhookSubscription - -## SYNOPSIS -Adds a new Webhook subscription - -## SYNTAX - -```powershell -Add-PnPWebhookSubscription -NotificationUrl <String> - [-List <ListPipeBind>] - [-ExpirationDate <DateTime>] - [-ClientState <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPWebhookSubscription -List MyList -NotificationUrl https://my-func.azurewebsites.net/webhook -``` - -Add a Webhook subscription for the specified notification Url on the list MyList - -### ------------------EXAMPLE 2------------------ -```powershell -Add-PnPWebhookSubscription -List MyList -NotificationUrl https://my-func.azurewebsites.net/webhook -ExpirationDate "2017-09-01" -``` - -Add a Webhook subscription for the specified notification Url on the list MyList with an expiration date set on September 1st, 2017 - -### ------------------EXAMPLE 3------------------ -```powershell -Add-PnPWebhookSubscription -List MyList -NotificationUrl https://my-func.azurewebsites.net/webhook -ExpirationDate "2017-09-01" -ClientState "Hello State!" -``` - -Add a Webhook subscription for the specified notification Url on the list MyList with an expiration date set on September 1st, 2017 with a specific client state - -## PARAMETERS - -### -ClientState -A client state information that will be passed through notifications - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExpirationDate -The date at which the Webhook subscription will expire. (Default: 6 months from today) - -```yaml -Type: DateTime -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The list object or name where the Webhook subscription will be added to - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NotificationUrl -The URL of the Webhook endpoint that will be notified of the change - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.Entities.WebhookSubscription - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWikiPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWikiPage.md deleted file mode 100644 index e0bf42b361..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWikiPage.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpwikipage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPWikiPage ---- - -# Add-PnPWikiPage - -## SYNOPSIS -Adds a wiki page - -## SYNTAX - -### WithContent -```powershell -Add-PnPWikiPage -Content <String> - -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### WithLayout -```powershell -Add-PnPWikiPage -Layout <WikiPageLayout> - -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPWikiPage -PageUrl '/sites/demo1/pages/wikipage.aspx' -Content 'New WikiPage' -``` - -Creates a new wiki page '/sites/demo1/pages/wikipage.aspx' and sets the content to 'New WikiPage' - -## PARAMETERS - -### -Content - - -```yaml -Type: String -Parameter Sets: WithContent - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Layout - - -```yaml -Type: WikiPageLayout -Parameter Sets: WithLayout - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -The server relative page URL - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowDefinition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowDefinition.md deleted file mode 100644 index 57b39ce821..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowDefinition.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpworkflowdefinition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPWorkflowDefinition ---- - -# Add-PnPWorkflowDefinition - -## SYNOPSIS -Adds a workflow definition - -## SYNTAX - -```powershell -Add-PnPWorkflowDefinition -Definition <WorkflowDefinition> - [-DoNotPublish [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPWorkflowDefinition -Definition $wfdef -``` - -Adds an existing workflow definition, retrieved by Get-PnPWorkflowDefinition, to a site. - -## PARAMETERS - -### -Definition -The workflow definition to add. - -```yaml -Type: WorkflowDefinition -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DoNotPublish -Overrides the default behavior, which is to publish workflow definitions. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.Guid - -Returns the Id of the workflow definition - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowSubscription.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowSubscription.md deleted file mode 100644 index f5c4f67d31..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPWorkflowSubscription.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/add-pnpworkflowsubscription -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Add-PnPWorkflowSubscription ---- - -# Add-PnPWorkflowSubscription - -## SYNOPSIS -Adds a workflow subscription to a list - -## SYNTAX - -```powershell -Add-PnPWorkflowSubscription -Name <String> - -DefinitionName <String> - -List <ListPipeBind> - -HistoryListName <String> - -TaskListName <String> - [-StartManually [<SwitchParameter>]] - [-StartOnCreated [<SwitchParameter>]] - [-StartOnChanged [<SwitchParameter>]] - [-AssociationValues <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Add-PnPWorkflowSubscription -Name MyWorkflow -DefinitionName SendMessageWf -list $list -``` - -Adds an Workflow with the name 'SendMessageWf' to the list $list. - -### ------------------EXAMPLE 2------------------ -```powershell -$list | Add-PnPWorkflowSubscription -Name MyWorkflow -DefinitionName SendMessageWf -``` - -Adds an Workflow with the name "SendMessageWf" to the list $list. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPList -Identity "MyCustomList" | Add-PnPWorkflowSubscription -Name MyWorkflow -DefinitionName SendMessageWf -``` - -Adds an Workflow with the name "SendMessageWf" to the list "MyCustomList". - -## PARAMETERS - -### -AssociationValues - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefinitionName -The name of the workflow definition - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -HistoryListName -The name of the History list - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The list to add the workflow to - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Name -The name of the subscription - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -StartManually -Switch if the workflow should be started manually, default value is 'true' - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StartOnChanged -Should the workflow run when an item is changed - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StartOnCreated -Should the workflow run when an new item is created - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TaskListName -The name of the task list - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPProvisioningTemplate.md deleted file mode 100644 index 619e15653e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPProvisioningTemplate.md +++ /dev/null @@ -1,320 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/apply-pnpprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Apply-PnPProvisioningTemplate ---- - -# Apply-PnPProvisioningTemplate - -## SYNOPSIS -Applies a site template to a web - -## SYNTAX - -### Instance -```powershell -Apply-PnPProvisioningTemplate [-InputInstance <ProvisioningTemplate>] - [-TemplateId <String>] - [-ResourceFolder <String>] - [-OverwriteSystemPropertyBagValues [<SwitchParameter>]] - [-IgnoreDuplicateDataRowErrors [<SwitchParameter>]] - [-ProvisionContentTypesToSubWebs [<SwitchParameter>]] - [-ProvisionFieldsToSubWebs [<SwitchParameter>]] - [-ClearNavigation [<SwitchParameter>]] - [-Parameters <Hashtable>] - [-Handlers <Handlers>] - [-ExcludeHandlers <Handlers>] - [-ExtensibilityHandlers <ExtensibilityHandler[]>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Path -```powershell -Apply-PnPProvisioningTemplate -Path <String> - [-TemplateId <String>] - [-ResourceFolder <String>] - [-OverwriteSystemPropertyBagValues [<SwitchParameter>]] - [-IgnoreDuplicateDataRowErrors [<SwitchParameter>]] - [-ProvisionContentTypesToSubWebs [<SwitchParameter>]] - [-ProvisionFieldsToSubWebs [<SwitchParameter>]] - [-ClearNavigation [<SwitchParameter>]] - [-Parameters <Hashtable>] - [-Handlers <Handlers>] - [-ExcludeHandlers <Handlers>] - [-ExtensibilityHandlers <ExtensibilityHandler[]>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Apply-PnPProvisioningTemplate -Path template.xml -``` - -Applies a site template in XML format to the current web. - -### ------------------EXAMPLE 2------------------ -```powershell -Apply-PnPProvisioningTemplate -Path template.xml -ResourceFolder c:\provisioning\resources -``` - -Applies a site template in XML format to the current web. Any resources like files that are referenced in the template will be retrieved from the folder as specified with the ResourceFolder parameter. - -### ------------------EXAMPLE 3------------------ -```powershell -Apply-PnPProvisioningTemplate -Path template.xml -Parameters @{"ListTitle"="Projects";"parameter2"="a second value"} -``` - -Applies a site template in XML format to the current web. It will populate the parameter in the template the values as specified and in the template you can refer to those values with the {parameter:<key>} token. - -For instance with the example above, specifying {parameter:ListTitle} in your template will translate to 'Projects' when applying the template. These tokens can be used in most string values in a template. - -### ------------------EXAMPLE 4------------------ -```powershell -Apply-PnPProvisioningTemplate -Path template.xml -Handlers Lists, SiteSecurity -``` - -Applies a site template in XML format to the current web. It will only apply the lists and site security part of the template. - -### ------------------EXAMPLE 5------------------ -```powershell -Apply-PnPProvisioningTemplate -Path template.pnp -``` - -Applies a site template from a pnp package to the current web. - -### ------------------EXAMPLE 6------------------ -```powershell -Apply-PnPProvisioningTemplate -Path https://tenant.sharepoint.com/sites/templatestorage/Documents/template.pnp -``` - -Applies a site template from a pnp package stored in a library to the current web. - -### ------------------EXAMPLE 7------------------ -```powershell - -$handler1 = New-PnPExtensibilityHandlerObject -Assembly Contoso.Core.Handlers -Type Contoso.Core.Handlers.MyExtensibilityHandler1 -$handler2 = New-PnPExtensibilityHandlerObject -Assembly Contoso.Core.Handlers -Type Contoso.Core.Handlers.MyExtensibilityHandler2 -Apply-PnPProvisioningTemplate -Path NewTemplate.xml -ExtensibilityHandlers $handler1,$handler2 -``` - -This will create two new ExtensibilityHandler objects that are run while provisioning the template - -### ------------------EXAMPLE 8------------------ -```powershell -Apply-PnPProvisioningTemplate -Path .\ -InputInstance $template -``` - -Applies a site template from an in-memory instance of a ProvisioningTemplate type of the PnP Core Component, reading the supporting files, if any, from the current (.\) path. The syntax can be used together with any other supported parameters. - -### ------------------EXAMPLE 9------------------ -```powershell -Apply-PnPProvisioningTemplate -Path .\template.xml -TemplateId "MyTemplate" -``` - -Applies the ProvisioningTemplate with the ID "MyTemplate" located in the template definition file template.xml. - -## PARAMETERS - -### -ClearNavigation -Override the RemoveExistingNodes attribute in the Navigation elements of the template. If you specify this value the navigation nodes will always be removed before adding the nodes in the template - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExcludeHandlers -Allows you to run all handlers, excluding the ones specified. - -```yaml -Type: Handlers -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExtensibilityHandlers -Allows you to specify ExtensbilityHandlers to execute while applying a template - -```yaml -Type: ExtensibilityHandler[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Handlers -Allows you to only process a specific part of the template. Notice that this might fail, as some of the handlers require other artifacts in place if they are not part of what your applying. Visit https://docs.microsoft.com/dotnet/api/officedevpnp.core.framework.provisioning.model.handlers for possible values. - -```yaml -Type: Handlers -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IgnoreDuplicateDataRowErrors -Ignore duplicate data row errors when the data row in the template already exists. - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -InputInstance -Allows you to provide an in-memory instance of the ProvisioningTemplate type of the PnP Core Component. When using this parameter, the -Path parameter refers to the path of any supporting file for the template. - -```yaml -Type: ProvisioningTemplate -Parameter Sets: Instance - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OverwriteSystemPropertyBagValues -Specify this parameter if you want to overwrite and/or create properties that are known to be system entries (starting with vti_, dlc_, etc.) - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Parameters -Allows you to specify parameters that can be referred to in the template by means of the {parameter:<Key>} token. See examples on how to use this parameter. - -```yaml -Type: Hashtable -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Path to the xml or pnp file containing the provisioning template. - -```yaml -Type: String -Parameter Sets: Path - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -ProvisionContentTypesToSubWebs -If set content types will be provisioned if the target web is a subweb. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ProvisionFieldsToSubWebs -If set fields will be provisioned if the target web is a subweb. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ResourceFolder -Root folder where resources/files that are being referenced in the template are located. If not specified the same folder as where the provisioning template is located will be used. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateId -ID of the template to use from the xml file containing the provisioning template. If not specified and multiple ProvisioningTemplate elements exist, the last one will be used. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while applying a template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPTenantTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPTenantTemplate.md deleted file mode 100644 index fc34494195..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPTenantTemplate.md +++ /dev/null @@ -1,275 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/apply-pnptenanttemplate -applicable: SharePoint Online -schema: 2.0.0 -title: Apply-PnPTenantTemplate ---- - -# Apply-PnPTenantTemplate - -## SYNOPSIS -Applies a tenant template to the current tenant. You must have the **Office 365 Global Admin** administrative role to run this cmdlet successfully. - -## SYNTAX - -### By Path -```powershell -Apply-PnPTenantTemplate -Path <String> - [-SequenceId <String>] - [-ResourceFolder <String>] - [-Handlers <Handlers>] - [-ExcludeHandlers <Handlers>] - [-ExtensibilityHandlers <ExtensibilityHandler[]>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-Parameters <Hashtable>] - [-OverwriteSystemPropertyBagValues [<SwitchParameter>]] - [-IgnoreDuplicateDataRowErrors [<SwitchParameter>]] - [-ProvisionContentTypesToSubWebs [<SwitchParameter>]] - [-ProvisionFieldsToSubWebs [<SwitchParameter>]] - [-ClearNavigation [<SwitchParameter>]] - [-Configuration <ApplyConfigurationPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### By Object -```powershell -Apply-PnPTenantTemplate -Template <ProvisioningHierarchy> - [-SequenceId <String>] - [-ResourceFolder <String>] - [-Handlers <Handlers>] - [-ExcludeHandlers <Handlers>] - [-ExtensibilityHandlers <ExtensibilityHandler[]>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-Parameters <Hashtable>] - [-OverwriteSystemPropertyBagValues [<SwitchParameter>]] - [-IgnoreDuplicateDataRowErrors [<SwitchParameter>]] - [-ProvisionContentTypesToSubWebs [<SwitchParameter>]] - [-ProvisionFieldsToSubWebs [<SwitchParameter>]] - [-ClearNavigation [<SwitchParameter>]] - [-Configuration <ApplyConfigurationPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Apply-PnPTenantTemplate -Path myfile.pnp -``` - -Will read the tenant template from the filesystem and will apply the sequences in the template - -### ------------------EXAMPLE 2------------------ -```powershell -Apply-PnPTenantTemplate -Path myfile.pnp -SequenceId "mysequence" -``` - -Will read the tenant template from the filesystem and will apply the specified sequence in the template - -### ------------------EXAMPLE 3------------------ -```powershell -Apply-PnPTenantTemplate -Path myfile.pnp -Parameters @{"ListTitle"="Projects";"parameter2"="a second value"} -``` - -Applies a tenant template to the current tenant. It will populate the parameter in the template the values as specified and in the template you can refer to those values with the {parameter:<key>} token. - -For instance with the example above, specifying {parameter:ListTitle} in your template will translate to 'Projects' when applying the template. These tokens can be used in most string values in a template. - -## PARAMETERS - -### -ClearNavigation -Override the RemoveExistingNodes attribute in the Navigation elements of the template. If you specify this value the navigation nodes will always be removed before adding the nodes in the template - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Configuration -Specify a JSON configuration file to configure the extraction progress. - -```yaml -Type: ApplyConfigurationPipeBind -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExcludeHandlers -Allows you to run all handlers, excluding the ones specified. - -```yaml -Type: Handlers -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExtensibilityHandlers -Allows you to specify ExtensbilityHandlers to execute while applying a template - -```yaml -Type: ExtensibilityHandler[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Handlers -Allows you to only process a specific part of the template. Notice that this might fail, as some of the handlers require other artifacts in place if they are not part of what your applying. - -```yaml -Type: Handlers -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IgnoreDuplicateDataRowErrors -Ignore duplicate data row errors when the data row in the template already exists. - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OverwriteSystemPropertyBagValues -Specify this parameter if you want to overwrite and/or create properties that are known to be system entries (starting with vti_, dlc_, etc.) - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Parameters -Allows you to specify parameters that can be referred to in the tenant template by means of the {parameter:<Key>} token. See examples on how to use this parameter. - -```yaml -Type: Hashtable -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Path to the xml or pnp file containing the tenant template. - -```yaml -Type: String -Parameter Sets: By Path - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -ProvisionContentTypesToSubWebs -If set content types will be provisioned if the target web is a subweb. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ProvisionFieldsToSubWebs -If set fields will be provisioned if the target web is a subweb. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ResourceFolder -Root folder where resources/files that are being referenced in the template are located. If not specified the same folder as where the tenant template is located will be used. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SequenceId - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Template - - -```yaml -Type: ProvisioningHierarchy -Parameter Sets: By Object - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while applying a template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Approve-PnPTenantServicePrincipalPermissionRequest.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Approve-PnPTenantServicePrincipalPermissionRequest.md deleted file mode 100644 index 8c5eaa33c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Approve-PnPTenantServicePrincipalPermissionRequest.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/approve-pnptenantserviceprincipalpermissionrequest -applicable: SharePoint Online -schema: 2.0.0 -title: Approve-PnPTenantServicePrincipalPermissionRequest ---- - -# Approve-PnPTenantServicePrincipalPermissionRequest - -## SYNOPSIS -Approves a permission request for the current tenant's "SharePoint Online Client" service principal - -## SYNTAX - -```powershell -Approve-PnPTenantServicePrincipalPermissionRequest -RequestId <GuidPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Approves a permission request for the current tenant's "SharePoint Online Client" service principal - -The return value of a successful call is a permission grant object. - -To get the collection of permission grants for the "SharePoint Online Client" service principal, use the Get-PnPTenantServicePrincipalPermissionGrants command. - -Approving a permission request also removes that request from the list of permission requests. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RequestId - - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPDefaultColumnValues.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPDefaultColumnValues.md deleted file mode 100644 index 01bbf8350c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPDefaultColumnValues.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/clear-pnpdefaultcolumnvalues -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Clear-PnPDefaultColumnValues ---- - -# Clear-PnPDefaultColumnValues - -## SYNOPSIS -Clear default column values for a document library - -## SYNTAX - -```powershell -Clear-PnPDefaultColumnValues -List <ListPipeBind> - -Field <FieldPipeBind> - [-Folder <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Clear default column values for a document library, per folder, or for the root folder if the folder parameter has not been specified. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Clear-PnPDefaultColumnValues -List Documents -Field MyField -``` - -Clears the default value for the field MyField on a library - -### ------------------EXAMPLE 2------------------ -```powershell -Clear-PnPDefaultColumnValues -List Documents -Field MyField -Folder A -``` - -Clears the default value for the field MyField on the folder A on a library - -## PARAMETERS - -### -Field -The internal name, id or a reference to a field - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Folder -A library relative folder path, if not specified it will set the default column values on the root folder of the library ('/') - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Name or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPListItemAsRecord.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPListItemAsRecord.md deleted file mode 100644 index a9328f5d67..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPListItemAsRecord.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/clear-pnplistitemasrecord -applicable: SharePoint Online -schema: 2.0.0 -title: Clear-PnPListItemAsRecord ---- - -# Clear-PnPListItemAsRecord - -## SYNOPSIS -Undeclares a list item as a record - -## SYNTAX - -```powershell -Clear-PnPListItemAsRecord -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Clear-PnPListItemAsRecord -List "Documents" -Identity 4 -``` - -Undeclares the document in the documents library with id 4 as a record - -## PARAMETERS - -### -Identity -The ID of the listitem, or actual ListItem object - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPTenantAppCatalogUrl.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPTenantAppCatalogUrl.md deleted file mode 100644 index 587c2e576f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPTenantAppCatalogUrl.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/clear-pnptenantappcatalogurl -applicable: SharePoint Online -schema: 2.0.0 -title: Clear-PnPTenantAppCatalogUrl ---- - -# Clear-PnPTenantAppCatalogUrl - -## SYNOPSIS -Removes the url of the tenant scoped app catalog. It will not delete the site collection itself. - -## SYNTAX - -```powershell -Clear-PnPTenantAppCatalogUrl [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Clear-PnPTenantAppCatalogUrl -``` - -Removes the url of the tenant scoped app catalog - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPTenantRecycleBinItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPTenantRecycleBinItem.md deleted file mode 100644 index b1c9cf1855..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnPTenantRecycleBinItem.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/clear-pnptenantrecyclebinitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Clear-PnPTenantRecycleBinItem ---- - -# Clear-PnPTenantRecycleBinItem - -## SYNOPSIS -Permanently deletes a site collection from the tenant scoped recycle bin - -## SYNTAX - -```powershell -Clear-PnPTenantRecycleBinItem -Url <String> - [-Wait [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -The Clear-PnPTenantRecycleBinItem cmdlet allows a site collection that has been deleted and still exists in the tenant recycle bin to be permanently deleted from the recycle bin as well. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Clear-PnPTenantRecycleBinItem -Url https://tenant.sharepoint.com/sites/contoso -``` - -This will permanently delete site collection with the url 'https://tenant.sharepoint.com/sites/contoso' from the tenant recycle bin - -### ------------------EXAMPLE 2------------------ -```powershell -Clear-PnPTenantRecycleBinItem -Url https://tenant.sharepoint.com/sites/contoso -Wait -``` - -This will permanently delete site collection with the url 'https://tenant.sharepoint.com/sites/contoso' from the tenant recycle bin and will wait with executing further PowerShell commands until the operation has completed - -## PARAMETERS - -### -Force -If provided, no confirmation will be asked to permanently delete the site collection from the tenant recycle bin - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -Url of the site collection to permanently delete from the tenant recycle bin - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Wait -If provided, the PowerShell execution will halt until the operation has completed - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnpRecycleBinItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnpRecycleBinItem.md deleted file mode 100644 index 63fc3b2fc1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnpRecycleBinItem.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/clear-pnprecyclebinitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Clear-PnPRecycleBinItem ---- - -# Clear-PnPRecycleBinItem - -## SYNOPSIS -Permanently deletes all or a specific recycle bin item - -## SYNTAX - -### All -```powershell -Clear-PnPRecycleBinItem [-All [<SwitchParameter>]] - [-SecondStageOnly [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### Identity -```powershell -Clear-PnPRecycleBinItem -Identity <RecycleBinItemPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPRecycleBinItem | ? FileLeafName -like "*.docx" | Clear-PnpRecycleBinItem -``` - -Permanently deletes all the items in the first and second stage recycle bins of which the file names have the .docx extension - -### ------------------EXAMPLE 2------------------ -```powershell -Clear-PnpRecycleBinItem -Identity 72e4d749-d750-4989-b727-523d6726e442 -``` - -Permanently deletes the recycle bin item with Id 72e4d749-d750-4989-b727-523d6726e442 from the recycle bin - -### ------------------EXAMPLE 3------------------ -```powershell -Clear-PnpRecycleBinItem -Identity $item -Force -``` - -Permanently deletes the recycle bin item stored under variable $item from the recycle bin without asking for confirmation from the end user first - -## PARAMETERS - -### -All -Clears all items - -```yaml -Type: SwitchParameter -Parameter Sets: All - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -If provided, no confirmation will be asked to permanently delete the recycle bin item - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Id of the recycle bin item or the recycle bin item itself to permanently delete - -```yaml -Type: RecycleBinItemPipeBind -Parameter Sets: Identity - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -SecondStageOnly -If provided, only all the items in the second stage recycle bin will be cleared - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: All - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Connect-PnPMicrosoftGraph.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Connect-PnPMicrosoftGraph.md deleted file mode 100644 index 79a52bb4a8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Connect-PnPMicrosoftGraph.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/connect-pnpmicrosoftgraph -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 ---- - -# Connect-PnPMicrosoftGraph - -## SYNOPSIS -Connect to the Microsoft Graph - -## SYNTAX - -### Scope -```powershell -Connect-PnPMicrosoftGraph -Scopes <String[]> -``` - -### AAD -```powershell -Connect-PnPMicrosoftGraph -AppId <String> - -AppSecret <String> - -AADDomain <String> -``` - -## DESCRIPTION -Uses the Microsoft Authentication Library (Preview) to connect to Azure AD and to get an OAuth 2.0 Access Token to consume the Microsoft Graph API - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPMicrosoftGraph -Scopes $arrayOfScopes -``` - -Connects to Azure AD and gets and OAuth 2.0 Access Token to consume the Microsoft Graph API including the declared permission scopes. The available permission scopes are defined at the following URL: https://graph.microsoft.io/en-us/docs/authorization/permission_scopes - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPMicrosoftGraph -AppId '<id>' -AppSecret '<secret>' -AADDomain 'contoso.onmicrosoft.com' -``` - -Connects to the Microsoft Graph API using application permissions via an app's declared permission scopes. See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/Graph.ConnectUsingAppPermissions for a sample on how to get started. - -## PARAMETERS - -### -AADDomain -The AAD where the O365 app is registered. Eg.: contoso.com, or contoso.onmicrosoft.com. - -```yaml -Type: String -Parameter Sets: AAD - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -AppId -The client id of the app which gives you access to the Microsoft Graph API. - -```yaml -Type: String -Parameter Sets: AAD - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -AppSecret -The app key of the app which gives you access to the Microsoft Graph API. - -```yaml -Type: String -Parameter Sets: AAD - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scopes -The array of permission scopes for the Microsoft Graph API. - -```yaml -Type: String[] -Parameter Sets: Scope - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Connect-PnPOnline.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Connect-PnPOnline.md deleted file mode 100644 index fd1a01023e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Connect-PnPOnline.md +++ /dev/null @@ -1,1102 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/connect-pnponline -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Connect-PnPOnline ---- - -# Connect-PnPOnline - -## SYNOPSIS -Connect to a SharePoint site - -## SYNTAX - -### Main -```powershell -Connect-PnPOnline -Url <String> - [-ReturnConnection [<SwitchParameter>]] - [-Credentials <CredentialPipeBind>] - [-CurrentCredentials [<SwitchParameter>]] - [-UseAdfs [<SwitchParameter>]] - [-UseAdfsCert [<SwitchParameter>]] - [-Kerberos [<SwitchParameter>]] - [-LoginProviderName <String>] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-AuthenticationMode <ClientAuthenticationMode>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-Scopes <String[]>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### Access Token -```powershell -Connect-PnPOnline -AccessToken <String> - [-ReturnConnection [<SwitchParameter>]] - [-Url <String>] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### PnP Office 365 Management Shell to the Microsoft Graph -```powershell -Connect-PnPOnline -Graph [<SwitchParameter>] - [-LaunchBrowser [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### Microsoft Graph using Scopes -```powershell -Connect-PnPOnline -Scopes <String[]> - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### WebLogin -```powershell -Connect-PnPOnline -Url <String> - -UseWebLogin [<SwitchParameter>] - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-Scopes <String[]>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### SPO Management Shell Credentials -```powershell -Connect-PnPOnline -Url <String> - -SPOManagementShell [<SwitchParameter>] - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-ClearTokenCache [<SwitchParameter>]] - [-Scopes <String[]>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### PnP O365 Management Shell / DeviceLogin -```powershell -Connect-PnPOnline -Url <String> - -PnPO365ManagementShell [<SwitchParameter>] - [-ReturnConnection [<SwitchParameter>]] - [-LaunchBrowser [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### Token -```powershell -Connect-PnPOnline -Url <String> - -AppId <String> - -AppSecret <String> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-Realm <String>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-AzureEnvironment <AzureEnvironment>] - [-Scopes <String[]>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### Azure Active Directory -```powershell -Connect-PnPOnline -Url <String> - -ClientId <String> - -RedirectUri <String> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-ClearTokenCache [<SwitchParameter>]] - [-AzureEnvironment <AzureEnvironment>] - [-Scopes <String[]>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### App-Only with Azure Active Directory -```powershell -Connect-PnPOnline -Url <String> - -ClientId <String> - -Tenant <String> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-CertificatePath <String>] - [-CertificateBase64Encoded <String>] - [-Certificate <X509Certificate2>] - [-CertificatePassword <SecureString>] - [-AzureEnvironment <AzureEnvironment>] - [-Scopes <String[]>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### App-Only with Azure Active Directory using X502 certificates -```powershell -Connect-PnPOnline -Url <String> - -ClientId <String> - -Tenant <String> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-AzureEnvironment <AzureEnvironment>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### Microsoft Graph using Azure Active Directory -```powershell -Connect-PnPOnline -AppId <String> - -AppSecret <String> - -AADDomain <String> - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### High Trust using a X509Certificate2 object. -```powershell -Connect-PnPOnline -Url <String> - -ClientId <String> - -HighTrustCertificate <X509Certificate2> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-HighTrustCertificateIssuerId <String>] - [-UserName <String>] - [-NoTelemetry [<SwitchParameter>]] -``` - -### App-Only with Azure Active Directory using certificate from certificate store by thumbprint -```powershell -Connect-PnPOnline -Url <String> - -ClientId <String> - -Tenant <String> - -Thumbprint <String> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-AzureEnvironment <AzureEnvironment>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -### High Trust using a certificate from a PFX file. -```powershell -Connect-PnPOnline -Url <String> - -ClientId <String> - -HighTrustCertificatePath <String> - -HighTrustCertificatePassword <String> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-HighTrustCertificateIssuerId <String>] - [-UserName <String>] - [-NoTelemetry [<SwitchParameter>]] -``` - -### App-Only with Azure Active Directory using certificate as PEM strings -```powershell -Connect-PnPOnline -Url <String> - -ClientId <String> - -Tenant <String> - -PEMCertificate <String> - -PEMPrivateKey <String> - [-ReturnConnection [<SwitchParameter>]] - [-MinimalHealthScore <Int>] - [-RetryCount <Int>] - [-RetryWait <Int>] - [-RequestTimeout <Int>] - [-CreateDrive [<SwitchParameter>]] - [-DriveName <String>] - [-CertificatePassword <SecureString>] - [-AzureEnvironment <AzureEnvironment>] - [-TenantAdminUrl <String>] - [-SkipTenantAdminCheck [<SwitchParameter>]] - [-IgnoreSslErrors [<SwitchParameter>]] - [-NoTelemetry [<SwitchParameter>]] -``` - -## DESCRIPTION -If no credentials have been specified, and the CurrentCredentials parameter has not been specified, you will be prompted for credentials. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -``` - -This will prompt for username and password and creates a context for the other PowerShell commands to use. When a generic credential is added to the Windows Credential Manager with https://contoso.sharepoint.com, PowerShell will not prompt for username and password. - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -Credentials (Get-Credential) -``` - -This will prompt for username and password and creates a context for the other PowerShell commands to use. - -### ------------------EXAMPLE 3------------------ -```powershell -Connect-PnPOnline -Url http://yourlocalserver -CurrentCredentials -``` - -This will use the current user credentials and connects to the server specified by the Url parameter. - -### ------------------EXAMPLE 4------------------ -```powershell -Connect-PnPOnline -Url http://yourlocalserver -Credentials 'O365Creds' -``` - -This will use credentials from the Windows Credential Manager, as defined by the label 'O365Creds'. - -### ------------------EXAMPLE 5------------------ -```powershell -Connect-PnPOnline -Url http://yourlocalserver -Credentials (Get-Credential) -UseAdfs -``` - -This will prompt for username and password and creates a context using ADFS to authenticate. - -### ------------------EXAMPLE 6------------------ -```powershell -Connect-PnPOnline -Url http://yourlocalserver -UseAdfsCert -``` - -This will enable you to select a certificate to create a context using ADFS to authenticate. - -### ------------------EXAMPLE 7------------------ -```powershell -Connect-PnPOnline -Url https://yourserver -Credentials (Get-Credential) -CreateDrive -cd SPO:\\ -dir -``` - -This will prompt you for credentials and creates a context for the other PowerShell commands to use. It will also create a SPO:\\ drive you can use to navigate around the site - -### ------------------EXAMPLE 8------------------ -```powershell -Connect-PnPOnline -Url https://yourserver -Credentials (Get-Credential) -AuthenticationMode FormsAuthentication -``` - -This will prompt you for credentials and creates a context for the other PowerShell commands to use. It assumes your server is configured for Forms Based Authentication (FBA) - -### ------------------EXAMPLE 9------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.de -AppId 344b8aab-389c-4e4a-8fa1-4c1ae2c0a60d -AppSecret a3f3faf33f3awf3a3sfs3f3ss3f4f4a3fawfas3ffsrrffssfd -AzureEnvironment Germany -``` - -This will authenticate you to the German Azure environment using the German Azure endpoints for authentication - -### ------------------EXAMPLE 10------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -SPOManagementShell -``` - -This will authenticate you using the SharePoint Online Management Shell application - -### ------------------EXAMPLE 11------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -PnPO365ManagementShell -``` - -This will authenticate you using the PnP O365 Management Shell Multi-Tenant application. A browser window will have to be opened where you have to enter a code that is shown in your PowerShell window. - -### ------------------EXAMPLE 12------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -PnPO365ManagementShell -LaunchBrowser -``` - -This will authenticate you using the PnP O365 Management Shell Multi-Tenant application. A browser window will automatically open and the code you need to enter will be automatically copied to your clipboard. - -### ------------------EXAMPLE 13------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -AccessToken $myaccesstoken -``` - -This will authenticate you using the provided access token - -### ------------------EXAMPLE 14------------------ -```powershell -Connect-PnPOnline -Scopes "Mail.Read","Files.Read" -``` - -Connects to Azure AD and gets and OAuth 2.0 Access Token to consume the Microsoft Graph API including the declared permission scopes. The available permission scopes are defined at the following URL: https://docs.microsoft.com/en-us/graph/permissions-reference - -### ------------------EXAMPLE 15------------------ -```powershell -Connect-PnPOnline -AppId '<id>' -AppSecret '<secret>' -AADDomain 'contoso.onmicrosoft.com' -``` - -Connects to the Microsoft Graph API using application permissions via an app's declared permission scopes. See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/Graph.ConnectUsingAppPermissions for a sample on how to get started. - -### ------------------EXAMPLE 16------------------ -```powershell -certutil.exe -csp 'Microsoft Enhanced RSA and AES Cryptographic Provider' -v -p 'password' -importpfx -user c:\HighTrust.pfx NoRoot -Connect-PnPOnline -Url https://yourserver -ClientId <id> -HighTrustCertificate (Get-Item Cert:\CurrentUser\My\<thumbprint>) -``` - -Connect to an on-premises SharePoint environment using a high trust certificate, stored in the Personal certificate store of the current user. - -### ------------------EXAMPLE 17------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -ClientId '<id>' -Tenant 'contoso.onmicrosoft.com' -CertificatePath c:\absolute-path\to\pnp.pfx -CertificatePassword <if needed> -``` - -Connects to SharePoint using app-only tokens via an app's declared permission scopes. See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/SharePoint.ConnectUsingAppPermissions for a sample on how to get started. - -### ------------------EXAMPLE 18------------------ -```powershell -Connect-PnPOnline -ClientId <id> -CertificatePath 'c:\mycertificate.pfx' -CertificatePassword (ConvertTo-SecureString -AsPlainText 'myprivatekeypassword' -Force) -Url https://contoso.sharepoint.com -Tenant 'contoso.onmicrosoft.com' -``` - -Connects using an Azure Active Directory registered application using a locally available certificate containing a private key. See https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread for a sample on how to get started. - -### ------------------EXAMPLE 19------------------ -```powershell -Connect-PnPOnline -Url https://yourserver -ClientId 763d5e60-b57e-426e-8e87-b7258f7f8188 -HighTrustCertificatePath c:\HighTrust.pfx -HighTrustCertificatePassword 'password' -HighTrustCertificateIssuerId 6b9534d8-c2c1-49d6-9f4b-cd415620bca8 -``` - -Connect to an on-premises SharePoint environment using a high trust certificate stored in a .PFX file. - -### ------------------EXAMPLE 20------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -ClientId '<id>' -Tenant 'contoso.onmicrosoft.com' -Thumbprint 34CFAA860E5FB8C44335A38A097C1E41EEA206AA -``` - -Connects to SharePoint using app-only tokens via an app's declared permission scopes. See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/SharePoint.ConnectUsingAppPermissions for a sample on how to get started. - -### ------------------EXAMPLE 21------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -ClientId '<id>' -Tenant 'contoso.onmicrosoft.com' -PEMCertificate <PEM string> -PEMPrivateKey <PEM string> -CertificatePassword <if needed> -``` - -Connects to SharePoint using app-only tokens via an app's declared permission scopes. See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/SharePoint.ConnectUsingAppPermissions for a sample on how to get started. - -### ------------------EXAMPLE 22------------------ -```powershell -Connect-PnPOnline -ClientId <id> -CertificateBase64Encoded 'xxxx' -CertificatePassword (ConvertTo-SecureString -AsPlainText 'myprivatekeypassword' -Force) -Url https://contoso.sharepoint.com -Tenant 'contoso.onmicrosoft.com' -``` - -Connects using an Azure Active Directory registered application using a certificate containing a private key encoded in base 64 such as received in an Azure Function when using Azure KeyVault. See https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread for a sample on how to get started. - -### ------------------EXAMPLE 23------------------ -```powershell -Connect-PnPOnline -Url https://contoso.sharepoint.com -ClientId '<id>' -Tenant 'contoso.onmicrosoft.com' -Certificate <X509Certificate2> -``` - -Connects to SharePoint using app-only auth in combination with a certificate. See https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread#using-this-principal-in-your-powershell-script-using-the-pnp-sites-core-library for a sample on how to get started. - -### ------------------EXAMPLE 24------------------ -```powershell -Connect-PnPOnline -ClientId <id> -Certificate $cert -CertificatePassword (ConvertTo-SecureString -AsPlainText 'myprivatekeypassword' -Force) -Url https://contoso.sharepoint.com -Tenant 'contoso.onmicrosoft.com' -``` - -Connects using an Azure Active Directory registered application using a certificate instance containing a private key. See https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread for a sample on how to get started. - -## PARAMETERS - -### -AADDomain -The AAD where the O365 app is registered. Eg.: contoso.com, or contoso.onmicrosoft.com. - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Microsoft Graph using Azure Active Directory - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -AccessToken -Connect with an existing Access Token - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Access Token - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -AppId -The Application Client ID to use. - -```yaml -Type: String -Parameter Sets: Token, Microsoft Graph using Azure Active Directory - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -AppSecret -The Application Client Secret to use. - -```yaml -Type: String -Parameter Sets: Token, Microsoft Graph using Azure Active Directory - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -AuthenticationMode -Specify to use for instance use forms based authentication (FBA) - -```yaml -Type: ClientAuthenticationMode -Parameter Sets: Main - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AzureEnvironment -The Azure environment to use for authentication, the defaults to 'Production' which is the main Azure environment. - -Only applicable to: SharePoint Online - -```yaml -Type: AzureEnvironment -Parameter Sets: Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Certificate -X509Certificate2 reference containing the private key to authenticate the requests to SharePoint Online - -Only applicable to: SharePoint Online - -```yaml -Type: X509Certificate2 -Parameter Sets: App-Only with Azure Active Directory - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CertificateBase64Encoded -Base64 Encoded X509Certificate2 certificate containing the private key to authenticate the requests to SharePoint Online such as retrieved in Azure Functions from Azure KeyVault - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: App-Only with Azure Active Directory - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CertificatePassword -Password to the certificate (*.pfx) - -Only applicable to: SharePoint Online - -```yaml -Type: SecureString -Parameter Sets: App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CertificatePath -Path to the certificate containing the private key (*.pfx) - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: App-Only with Azure Active Directory - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClearTokenCache -Clears the token cache. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Azure Active Directory, SPO Management Shell Credentials - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClientId -The Client ID of the Azure AD Application - -```yaml -Type: String -Parameter Sets: Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -CreateDrive -If you want to create a PSDrive connected to the URL - -```yaml -Type: SwitchParameter -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Credentials -Credentials of the user to connect with. Either specify a PSCredential object or a string. In case of a string value a lookup will be done to the Generic Credentials section of the Windows Credentials in the Windows Credential Manager for the correct credentials. - -```yaml -Type: CredentialPipeBind -Parameter Sets: Main - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CurrentCredentials -If you want to connect with the current user credentials - -```yaml -Type: SwitchParameter -Parameter Sets: Main - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DriveName -Name of the PSDrive to create (default: SPO) - -```yaml -Type: String -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Graph -Log in using the PnP O365 Management Shell application towards the Graph. You will be asked to consent to: - -* Read and write managed metadata -* Have full control of all site collections -* Read user profiles -* Invite guest users to the organization -* Read and write all groups -* Read and write directory data -* Read and write identity providers -* Access the directory as you - - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: PnP Office 365 Management Shell to the Microsoft Graph - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -HighTrustCertificate -The certificate which has been registered in SharePoint as a Trusted Security Token issuer to use for the High Trust connection. Note that CNG key storage providers are not supported. - -Only applicable to: SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 - -```yaml -Type: X509Certificate2 -Parameter Sets: High Trust using a X509Certificate2 object. - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -HighTrustCertificateIssuerId -The IssuerID under which the certificate has been registered in SharePoint as a Trusted Security Token issuer to use for the High Trust connection. Uses the ClientID if not specified. - -Only applicable to: SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 - -```yaml -Type: String -Parameter Sets: High Trust using a X509Certificate2 object., High Trust using a certificate from a PFX file. - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HighTrustCertificatePassword -The password of the private key certificate (.pfx) to use for the High Trust connection - -Only applicable to: SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 - -```yaml -Type: String -Parameter Sets: High Trust using a certificate from a PFX file. - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -HighTrustCertificatePath -The path to the private key certificate (.pfx) to use for the High Trust connection - -Only applicable to: SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 - -```yaml -Type: String -Parameter Sets: High Trust using a certificate from a PFX file. - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -IgnoreSslErrors -Ignores any SSL errors. To be used i.e. when connecting to a SharePoint farm using self signed certificates or using a certificate authority not trusted by this machine. - -```yaml -Type: SwitchParameter -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, Microsoft Graph using Azure Active Directory, Microsoft Graph using Scopes, PnP Office 365 Management Shell to the Microsoft Graph, SPO Management Shell Credentials - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Kerberos -Authenticate using Kerberos to an on-premises ADFS instance. - -```yaml -Type: SwitchParameter -Parameter Sets: Main - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LaunchBrowser -Launch a browser automatically and copy the code to enter to the clipboard - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: PnP O365 Management Shell / DeviceLogin, PnP Office 365 Management Shell to the Microsoft Graph - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LoginProviderName -The name of the ADFS trusted login provider - -```yaml -Type: String -Parameter Sets: Main - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MinimalHealthScore -Specifies a minimal server healthscore before any requests are executed. - -```yaml -Type: Int -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NoTelemetry -In order to help to make PnP PowerShell better, we can track anonymous telemetry. We track the version of the cmdlets you are using, which cmdlet you are executing and which version of SharePoint you are connecting to. Use Disable-PnPPowerShellTelemetry to turn this off in general or use the -NoTelemetry switch to turn it off for that session. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PEMCertificate -PEM encoded certificate - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: App-Only with Azure Active Directory using certificate as PEM strings - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PEMPrivateKey -PEM encoded private key for the certificate - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: App-Only with Azure Active Directory using certificate as PEM strings - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PnPO365ManagementShell -Log in using the PnP O365 Management Shell application. You will be asked to consent to: - -* Read and write managed metadata -* Have full control of all site collections -* Read user profiles -* Invite guest users to the organization -* Read and write all groups -* Read and write directory data -* Read and write identity providers -* Access the directory as you - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: PnP O365 Management Shell / DeviceLogin - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Realm -Authentication realm. If not specified will be resolved from the url specified. - -```yaml -Type: String -Parameter Sets: Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RedirectUri -The Redirect URI of the Azure AD Application - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Azure Active Directory - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -RequestTimeout -The request timeout. Default is 1800000 - -```yaml -Type: Int -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RetryCount -Defines how often a retry should be executed if the server healthscore is not sufficient. Default is 10 times. - -```yaml -Type: Int -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RetryWait -Defines how many seconds to wait before each retry. Default is 1 second. - -```yaml -Type: Int -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ReturnConnection -Returns the connection for use with the -Connection parameter on cmdlets. - -```yaml -Type: SwitchParameter -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token, PnP O365 Management Shell / DeviceLogin - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Scopes -The array of permission scopes for the Microsoft Graph API. - -Only applicable to: SharePoint Online - -```yaml -Type: String[] -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, SPO Management Shell Credentials, Microsoft Graph using Scopes - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipTenantAdminCheck -Should we skip the check if this site is the Tenant admin site. Default is false - -```yaml -Type: SwitchParameter -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials, Access Token - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SPOManagementShell -Log in using the SharePoint Online Management Shell application - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: SPO Management Shell Credentials - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Tenant -The Azure AD Tenant name,e.g. mycompany.onmicrosoft.com - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory, App-Only with Azure Active Directory using X502 certificates - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TenantAdminUrl -The url to the Tenant Admin site. If not specified, the cmdlets will assume to connect automatically to https://<tenantname>-admin.sharepoint.com where appropriate. - -```yaml -Type: String -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, App-Only with Azure Active Directory using X502 certificates, SPO Management Shell Credentials - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Thumbprint -Certificate thumbprint - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: App-Only with Azure Active Directory using certificate from certificate store by thumbprint - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -The Url of the site collection to connect to. - -```yaml -Type: String -Parameter Sets: Main, Token, WebLogin, Azure Active Directory, App-Only with Azure Active Directory, App-Only with Azure Active Directory using certificate as PEM strings, App-Only with Azure Active Directory using X502 certificates, App-Only with Azure Active Directory using certificate from certificate store by thumbprint, SPO Management Shell Credentials, Access Token, PnP O365 Management Shell / DeviceLogin - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -UseAdfs -If you want to connect to your on-premises SharePoint farm using ADFS - -```yaml -Type: SwitchParameter -Parameter Sets: Main - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UseAdfsCert -If you want to connect to your SharePoint farm using ADFS with Certificate Authentication - -```yaml -Type: SwitchParameter -Parameter Sets: Main - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UserName -Name of the user (login name) on whose behalf to create the access token. Supported input formats are SID and User Principal Name (UPN) in the format user@domain.local. If the parameter is not specified, an App Only Context is created. - -Only applicable to: SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 - -```yaml -Type: String -Parameter Sets: High Trust using a X509Certificate2 object., High Trust using a certificate from a PFX file. - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UseWebLogin -If you want to connect to SharePoint with browser based login. This is required when you have multi-factor authentication (MFA) enabled. - -```yaml -Type: SwitchParameter -Parameter Sets: WebLogin - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Convert-PnPFolderToProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Convert-PnPFolderToProvisioningTemplate.md deleted file mode 100644 index 137a60e7b6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Convert-PnPFolderToProvisioningTemplate.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/convert-pnpfoldertoprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Convert-PnPFolderToProvisioningTemplate ---- - -# Convert-PnPFolderToProvisioningTemplate - -## SYNOPSIS -Creates a pnp package file of an existing template xml, and includes all files in the current folder - -## SYNTAX - -```powershell -Convert-PnPFolderToProvisioningTemplate -Out <String> - [-Force [<SwitchParameter>]] - [-Folder <String>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Convert-PnPFolderToProvisioningTemplate -Out template.pnp -``` - -Creates a pnp package file of an existing template xml, and includes all files in the current folder - -### ------------------EXAMPLE 2------------------ -```powershell -Convert-PnPFolderToProvisioningTemplate -Out template.pnp -Folder c:\temp -``` - -Creates a pnp package file of an existing template xml, and includes all files in the c:\temp folder - -## PARAMETERS - -### -Folder -Folder to process. If not specified the current folder will be used. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Convert-PnPProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Convert-PnPProvisioningTemplate.md deleted file mode 100644 index e61ba8727d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Convert-PnPProvisioningTemplate.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/convert-pnpprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Convert-PnPProvisioningTemplate ---- - -# Convert-PnPProvisioningTemplate - -## SYNOPSIS -Converts a provisioning template to an other schema version - -## SYNTAX - -```powershell -Convert-PnPProvisioningTemplate -Path <String> - [-Out <String>] - [-Encoding <Encoding>] - [-Force [<SwitchParameter>]] - [-ToSchema <XMLPnPSchemaVersion>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Convert-PnPProvisioningTemplate -Path template.xml -``` - -Converts a provisioning template to the latest schema and outputs the result to current console. - -### ------------------EXAMPLE 2------------------ -```powershell -Convert-PnPProvisioningTemplate -Path template.xml -Out newtemplate.xml -``` - -Converts a provisioning template to the latest schema and outputs the result the newtemplate.xml file. - -### ------------------EXAMPLE 3------------------ -```powershell -Convert-PnPProvisioningTemplate -Path template.xml -Out newtemplate.xml -ToSchema V201512 -``` - -Converts a provisioning template to the latest schema using the 201512 schema and outputs the result the newtemplate.xml file. - -## PARAMETERS - -### -Encoding -The encoding type of the XML file, Unicode is default - -```yaml -Type: Encoding -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Path to the xml file containing the site template - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -ToSchema -The schema of the output to use, defaults to the latest schema - -```yaml -Type: XMLPnPSchemaVersion -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Encoding](https://msdn.microsoft.com/en-us/library/system.text.encoding_properties.aspx) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/ConvertTo-PnPClientSidePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/ConvertTo-PnPClientSidePage.md deleted file mode 100644 index 6b851d2be9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/ConvertTo-PnPClientSidePage.md +++ /dev/null @@ -1,708 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/convertto-pnpclientsidepage -applicable: SharePoint Online -schema: 2.0.0 -title: ConvertTo-PnPClientSidePage ---- - -# ConvertTo-PnPClientSidePage - -## SYNOPSIS -Converts a classic page (wiki or web part page) into a Client-Side Page - -## SYNTAX - -```powershell -ConvertTo-PnPClientSidePage -Identity <PagePipeBind> - [-Library <String>] - [-Folder <String>] - [-WebPartMappingFile <String>] - [-Overwrite [<SwitchParameter>]] - [-TakeSourcePageName [<SwitchParameter>]] - [-ReplaceHomePageWithDefault [<SwitchParameter>]] - [-AddPageAcceptBanner [<SwitchParameter>]] - [-SkipItemLevelPermissionCopyToClientSidePage [<SwitchParameter>]] - [-SkipUrlRewriting [<SwitchParameter>]] - [-SkipDefaultUrlRewriting [<SwitchParameter>]] - [-UrlMappingFile <String>] - [-ClearCache [<SwitchParameter>]] - [-CopyPageMetadata [<SwitchParameter>]] - [-AddTableListImageAsImageWebPart [<SwitchParameter>]] - [-UseCommunityScriptEditor [<SwitchParameter>]] - [-SummaryLinksToHtml [<SwitchParameter>]] - [-TargetWebUrl <String>] - [-LogType <ClientSidePageTransformatorLogType>] - [-LogFolder <String>] - [-LogSkipFlush [<SwitchParameter>]] - [-LogVerbose [<SwitchParameter>]] - [-DontPublish [<SwitchParameter>]] - [-KeepPageCreationModificationInformation [<SwitchParameter>]] - [-SetAuthorInPageHeader [<SwitchParameter>]] - [-PostAsNews [<SwitchParameter>]] - [-DisablePageComments [<SwitchParameter>]] - [-PublishingPage [<SwitchParameter>]] - [-BlogPage [<SwitchParameter>]] - [-DelveBlogPage [<SwitchParameter>]] - [-DelveKeepSubTitle [<SwitchParameter>]] - [-PageLayoutMapping <String>] - [-PublishingTargetPageName <String>] - [-TargetPageName <String>] - [-TargetPageFolder <String>] - [-TargetPageFolderOverridesDefaultFolder [<SwitchParameter>]] - [-RemoveEmptySectionsAndColumns [<SwitchParameter>]] - [-TargetConnection <SPOnlineConnection>] - [-SkipUserMapping [<SwitchParameter>]] - [-UserMappingFile <String>] - [-TermMappingFile <String>] - [-SkipTermStoreMapping [<SwitchParameter>]] - [-LDAPConnectionString <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Overwrite -``` - -Converts a wiki/web part page named 'somepage' to a client side page - -### ------------------EXAMPLE 2------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Overwrite -WebPartMappingFile c:\contoso\webpartmapping.xml -``` - -Converts a wiki/web part page named 'somepage' to a client side page using a custom provided mapping file - -### ------------------EXAMPLE 3------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Overwrite -AddPageAcceptBanner -``` - -Converts a wiki/web part page named 'somepage' to a client side page and adds the page accept banner web part on top of the page. This requires that the SPFX solution holding the web part (https://github.com/SharePoint/sp-dev-modernization/blob/master/Solutions/PageTransformationUI/assets/sharepointpnp-pagetransformation-client.sppkg?raw=true) has been installed to the tenant app catalog - -### ------------------EXAMPLE 4------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Overwrite -CopyPageMetadata -``` - -Converts a wiki/web part page named 'somepage' to a client side page, including the copying of the page metadata (if any) - -### ------------------EXAMPLE 5------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -PublishingPage -Overwrite -TargetWebUrl https://contoso.sharepoint.com/sites/targetmodernsite -``` - -Converts a publishing page named 'somepage' to a client side page in the https://contoso.sharepoint.com/sites/targetmodernsite site - -### ------------------EXAMPLE 6------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -PublishingPage -Overwrite -TargetConnection $target -``` - -Converts a publishing page named 'somepage' to a client side page in the site specified by the TargetConnection connection. This allows to read a page in one environment (on-premises, tenant A) and create in another online location (tenant B) - -### ------------------EXAMPLE 7------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Library "SiteAssets" -Folder "Folder1" -Overwrite -``` - -Converts a web part page named 'somepage' living inside the SiteAssets library in a folder named folder1 into a client side page - -### ------------------EXAMPLE 8------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Folder "<root>" -Overwrite -``` - -Converts a web part page named 'somepage' living inside the root of the site collection (so outside of a library) - -### ------------------EXAMPLE 9------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Overwrite -TargetWebUrl https://contoso.sharepoint.com/sites/targetmodernsite -``` - -Converts a wiki/web part page named 'somepage' to a client side page in the https://contoso.sharepoint.com/sites/targetmodernsite site - -### ------------------EXAMPLE 10------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -LogType File -LogFolder c:\temp -LogVerbose -Overwrite -``` - -Converts a wiki/web part page named 'somepage' and creates a log file in c:\temp using verbose logging - -### ------------------EXAMPLE 11------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -LogType SharePoint -LogSkipFlush -``` - -Converts a wiki/web part page named 'somepage' and creates a log file in SharePoint but skip the actual write. Use this option to make multiple ConvertTo-PnPClientSidePage invocations create a single log - -### ------------------EXAMPLE 12------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "My post title" -BlogPage -LogType Console -Overwrite -TargetWebUrl https://contoso.sharepoint.com/sites/targetmodernsite -``` - -Converts a blog page with a title starting with 'my post title' to a client side page in the https://contoso.sharepoint.com/sites/targetmodernsite site - -### ------------------EXAMPLE 13------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "My post title" -DelveBlogPage -LogType Console -Overwrite -TargetWebUrl https://contoso.sharepoint.com/sites/targetmodernsite -``` - -Converts a Delve blog page with a title starting with 'my post title' to a client side page in the https://contoso.sharepoint.com/sites/targetmodernsite site - -### ------------------EXAMPLE 14------------------ -```powershell -ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -PublishingPage -Overwrite -TargetConnection $target -UserMappingFile c:\\temp\user_mapping_file.csv -``` - -Converts a publishing page named 'somepage' to a client side page in the site specified by the TargetConnection connection. This allows to read a page in on-premises environment and create in another online locations including using specific user mappings between the two environments. - -## PARAMETERS - -### -AddPageAcceptBanner -Adds the page accept banner web part. The actual web part is specified in webpartmapping.xml file - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AddTableListImageAsImageWebPart -When an image lives inside a table/list then it's also created as separate image web part underneath that table/list by default. Use this switch set to $false to change that - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -BlogPage -I'm transforming a blog page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClearCache -Clears the cache. Can be needed if you've installed a new web part to the site and want to use that in a custom webpartmapping file. Restarting your PS session has the same effect - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CopyPageMetadata -Copies the page metadata to the created modern page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DelveBlogPage -I'm transforming a Delve blog page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DelveKeepSubTitle -Transform the possible sub title as topic header on the modern page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisablePageComments -Disable comments for the created modern page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DontPublish -Don't publish the created modern page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Folder -The folder to load the provided page from. If not provided all folders are searched - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Identity -The name of the page to convert - -```yaml -Type: PagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -KeepPageCreationModificationInformation -Keep the author, editor, created and modified information from the source page (when source page lives in SPO) - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LDAPConnectionString -Specifies a LDAP connection string e.g. LDAP://OU=Users,DC=Contoso,DC=local - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Library -The name of the library containing the page. If SitePages then please omit this parameter - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -LogFolder -Folder in where the log file will be created (if LogType==File) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LogSkipFlush -By default each cmdlet invocation will result in a log file, use the -SkipLogFlush to delay the log flushing. The first call without -SkipLogFlush will then write all log entries to a single log - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LogType -Allows to generate a transformation log (File | SharePoint) - -```yaml -Type: ClientSidePageTransformatorLogType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LogVerbose -Configure logging to include verbose log entries - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Overwrite -Overwrites page if already existing - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PageLayoutMapping -Path and name of the page layout mapping file driving the publishing page transformation - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -PostAsNews -Post the created, and published, modern page as news - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PublishingPage -I'm transforming a publishing page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PublishingTargetPageName -Name for the target page (only applies to publishing page transformation) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RemoveEmptySectionsAndColumns -Remove empty sections and columns after transformation of the page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ReplaceHomePageWithDefault -Replaces a home page with a default stock modern home page - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SetAuthorInPageHeader -Set's the author of the source page as author in the modern page header (when source page lives in SPO) - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipDefaultUrlRewriting -Set this flag to prevent the default URL rewriting while you still want to do URL rewriting using a custom URL mapping file - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipItemLevelPermissionCopyToClientSidePage -By default the item level permissions on a page are copied to the created client side page. Use this switch to prevent the copy - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipTermStoreMapping -Disables term mapping during transformation - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipUrlRewriting -If transforming cross site then by default urls in html and summarylinks are rewritten for the target site. Set this flag to prevent that - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipUserMapping -Disables user mapping during transformation - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SummaryLinksToHtml -By default summarylinks web parts are replaced by QuickLinks, but you can transform to plain html by setting this switch - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TakeSourcePageName -Created client side page takes name from previous classic page. Classic page gets renamed to previous_<Page>.aspx - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TargetConnection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TargetPageFolder -Folder to create the target page in (will be used in conjunction with auto-generated folders that ensure page name uniqueness) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TargetPageFolderOverridesDefaultFolder -When setting a target page folder then the target page folder overrides possibly default folder path (e.g. in the source page lived in a folder) instead of being appended to it - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TargetPageName -Name for the target page (only applies when doing cross site page transformation) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TargetWebUrl -Url of the target web that will receive the modern page. Defaults to null which means in-place transformation - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermMappingFile -Specifies a taxonomy term mapping file - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UrlMappingFile -File holding custom URL mapping definitions - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UseCommunityScriptEditor -Uses the community script editor (https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor) as replacement for the classic script editor web part - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UserMappingFile -Specifies a user mapping file - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -WebPartMappingFile -Path and name of the web part mapping file driving the transformation - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Copy-PnPFile.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Copy-PnPFile.md deleted file mode 100644 index 7ffce6ce9f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Copy-PnPFile.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/copy-pnpfile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Copy-PnPFile ---- - -# Copy-PnPFile - -## SYNOPSIS -Copies a file or folder to a different location, currently there is a 200MB file size limit for the file to be copied. - -## SYNTAX - -### SOURCEURL -```powershell -Copy-PnPFile -SourceUrl <String> - -TargetUrl <String> - [-OverwriteIfAlreadyExists [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-SkipSourceFolderName [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/company.docx -TargetUrl /sites/otherproject/Documents/company.docx -``` - -Copies a file named company.docx located in a document library called Documents in the current site to the site collection otherproject. If a file named company.docx already exists, it won't perform the copy. - -### ------------------EXAMPLE 2------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/company.docx -TargetUrl Documents/company2.docx -``` - -Copies a file named company.docx located in a document library called Documents to a new document named company2.docx in the same library. - -### ------------------EXAMPLE 3------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/company.docx -TargetUrl Documents2/company.docx -``` - -Copies a file named company.docx located in a document library called Documents to a document library called Documents2 in the same site. - -### ------------------EXAMPLE 4------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/company.docx -TargetUrl Subsite/Documents/company2.docx -``` - -Copies a file named company.docx located in a document library called Documents to the document library named Document in a subsite named Subsite as a new document named company2.docx. - -### ------------------EXAMPLE 5------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/company.docx -TargetUrl Subsite/Documents -``` - -Copies a file named company.docx located in a document library called Documents to the document library named Document in a subsite named Subsite keeping the file name. - -### ------------------EXAMPLE 6------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/company.docx -TargetUrl /sites/otherproject/Documents/company.docx -OverwriteIfAlreadyExists -``` - -Copies a file named company.docx located in a document library called Documents in the current site to the site collection otherproject. If a file named company.docx already exists, it will still perform the copy and replace the original company.docx file. - -### ------------------EXAMPLE 7------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/MyDocs -TargetUrl /sites/otherproject/Documents -OverwriteIfAlreadyExists -``` - -Copies a folder named MyDocs in the document library called Documents located in the current site to the site collection otherproject. If the MyDocs folder exist it will copy into it, if not it will be created. - -### ------------------EXAMPLE 8------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/MyDocs -TargetUrl /sites/otherproject/Documents -SkipSourceFolderName -OverwriteIfAlreadyExists -``` - -Copies a folder named MyDocs in the document library called Documents located in the current site to the root folder of the library named Documents in the site collection otherproject. - -### ------------------EXAMPLE 9------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/MyDocs -TargetUrl /sites/otherproject/Documents/MyDocs -SkipSourceFolderName -OverwriteIfAlreadyExists -``` - -Copies a folder named MyDocs in the MyDocs folder of the library named Documents. If the MyDocs folder does not exists, it will be created. - -### ------------------EXAMPLE 10------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl Documents/MyDocs -TargetUrl /sites/otherproject/Documents/MyDocs -OverwriteIfAlreadyExists -``` - -Copies a folder named MyDocs in the root of the library named Documents. If the MyDocs folder exists in the target, a subfolder also named MyDocs is created. - -### ------------------EXAMPLE 11------------------ -```powershell -PS:>Copy-PnPFile -SourceUrl SubSite1/Documents/company.docx -TargetUrl SubSite2/Documents -``` - -Copies a file named company.docx in the library named Documents in SubSite1 to the library named Documents in SubSite2. - -## PARAMETERS - -### -Force -If provided, no confirmation will be requested and the action will be performed - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OverwriteIfAlreadyExists -If provided, if a file already exists at the TargetUrl, it will be overwritten. If omitted, the copy operation will be canceled if the file already exists at the TargetUrl location. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipSourceFolderName -If the source is a folder, the source folder name will not be created, only the contents within it. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SourceUrl -Site relative Url specifying the file or folder to copy. - -```yaml -Type: String -Parameter Sets: SOURCEURL -Aliases: SiteRelativeUrl - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TargetUrl -Server relative Url where to copy the file or folder to. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Copy-PnPItemProxy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Copy-PnPItemProxy.md deleted file mode 100644 index ece91bf7ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Copy-PnPItemProxy.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/copy-pnpitemproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Copy-PnPItemProxy ---- - -# Copy-PnPItemProxy - -## SYNOPSIS -Proxy cmdlet for using Copy-Item between SharePoint provider and FileSystem provider - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Deny-PnPTenantServicePrincipalPermissionRequest.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Deny-PnPTenantServicePrincipalPermissionRequest.md deleted file mode 100644 index 65aad33fb3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Deny-PnPTenantServicePrincipalPermissionRequest.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/deny-pnptenantserviceprincipalpermissionrequest -applicable: SharePoint Online -schema: 2.0.0 -title: Deny-PnPTenantServicePrincipalPermissionRequest ---- - -# Deny-PnPTenantServicePrincipalPermissionRequest - -## SYNOPSIS -Denies a permission request for the current tenant's "SharePoint Online Client" service principal - -## SYNTAX - -```powershell -Deny-PnPTenantServicePrincipalPermissionRequest -RequestId <GuidPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Denies a permission request for the current tenant's "SharePoint Online Client" service principal - -Denying a permission request removes that request from the list of permission requests. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RequestId - - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPFeature.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPFeature.md deleted file mode 100644 index 7080eba5c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPFeature.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/disable-pnpfeature -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Disable-PnPFeature ---- - -# Disable-PnPFeature - -## SYNOPSIS -Disables a feature - -## SYNTAX - -```powershell -Disable-PnPFeature -Identity <GuidPipeBind> - [-Force [<SwitchParameter>]] - [-Scope <FeatureScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Deactivates a feature that was active on a site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Disable-PnPFeature -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will disable the feature with the id "99a00f6e-fb81-4dc7-8eac-e09c6f9132fe" - -### ------------------EXAMPLE 2------------------ -```powershell -Disable-PnPFeature -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Force -``` - -This will disable the feature with the id "99a00f6e-fb81-4dc7-8eac-e09c6f9132fe" with force. - -### ------------------EXAMPLE 3------------------ -```powershell -Disable-PnPFeature -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Web -``` - -This will disable the feature with the id "99a00f6e-fb81-4dc7-8eac-e09c6f9132fe" with the web scope. - -## PARAMETERS - -### -Force -Specifies whether to continue if an error occurs when deactivating the feature. - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The id of the feature to disable. - -```yaml -Type: GuidPipeBind -Parameter Sets: __AllParameterSets - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Scope -Specify the scope of the feature to deactivate, either Web or Site. Defaults to Web. - -```yaml -Type: FeatureScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPInPlaceRecordsManagementForSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPInPlaceRecordsManagementForSite.md deleted file mode 100644 index b00e0c84d5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPInPlaceRecordsManagementForSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/disable-pnpinplacerecordsmanagementforsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Disable-PnPInPlaceRecordsManagementForSite ---- - -# Disable-PnPInPlaceRecordsManagementForSite - -## SYNOPSIS -Disables in place records management for a site. - -## SYNTAX - -```powershell -Disable-PnPInPlaceRecordsManagementForSite [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Disable-PnPInPlaceRecordsManagementForSite -``` - -The in place records management feature will be disabled - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPPowerShellTelemetry.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPPowerShellTelemetry.md deleted file mode 100644 index 6dd492863f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPPowerShellTelemetry.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/disable-pnppowershelltelemetry -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Disable-PnPPowerShellTelemetry ---- - -# Disable-PnPPowerShellTelemetry - -## SYNOPSIS -Disables PnP PowerShell telemetry tracking - -## SYNTAX - -```powershell -Disable-PnPPowerShellTelemetry [-Force [<SwitchParameter>]] -``` - -## DESCRIPTION -Disables PnP PowerShell telemetry tracking - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Disable-PnPPowerShellTelemetry -``` - -Will prompt you to confirm to disable telemetry tracking. - -### ------------------EXAMPLE 2------------------ -```powershell -Disable-PnPPowerShellTelemetry -Force -``` - -Will disable telemetry tracking without prompting. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPResponsiveUI.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPResponsiveUI.md deleted file mode 100644 index 25977ecc05..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPResponsiveUI.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/disable-pnpresponsiveui -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Disable-PnPResponsiveUI ---- - -# Disable-PnPResponsiveUI - -## SYNOPSIS -Deactivate the PnP Response UI add-on - -## SYNTAX - -```powershell -Disable-PnPResponsiveUI [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Disables the PnP Responsive UI implementation on a classic SharePoint Site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Disable-PnPResponsiveUI -``` - -If enabled previously, this will remove the PnP Responsive UI from a site. - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPSiteClassification.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPSiteClassification.md deleted file mode 100644 index 3d06ce6f85..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPSiteClassification.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/disable-pnpsiteclassification -applicable: SharePoint Online -schema: 2.0.0 -title: Disable-PnPSiteClassification ---- - -# Disable-PnPSiteClassification - -## SYNOPSIS -Disables Site Classifications for the tenant. Requires a connection to the Microsoft Graph. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Disable-PnPSiteClassification -``` - -Disables Site Classifications for your tenant. - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPTenantServicePrincipal.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPTenantServicePrincipal.md deleted file mode 100644 index 8d9c8d0b0b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Disable-PnPTenantServicePrincipal.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/disable-pnptenantserviceprincipal -applicable: SharePoint Online -schema: 2.0.0 -title: Disable-PnPTenantServicePrincipal ---- - -# Disable-PnPTenantServicePrincipal - -## SYNOPSIS -Enables the current tenant's "SharePoint Online Client" service principal. - -## SYNTAX - -```powershell -Disable-PnPTenantServicePrincipal [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Enables the current tenant's "SharePoint Online Client" service principal. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Disconnect-PnPOnline.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Disconnect-PnPOnline.md deleted file mode 100644 index 9460946346..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Disconnect-PnPOnline.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/disconnect-pnponline -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Disconnect-PnPOnline ---- - -# Disconnect-PnPOnline - -## SYNOPSIS -Disconnects the context - -## SYNTAX - -```powershell -Disconnect-PnPOnline [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Disconnects the current context and requires you to build up a new connection in order to use the Cmdlets again. Using Connect-PnPOnline to connect to a different site has the same effect. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Disconnect-PnPOnline -``` - -This will disconnect you from the server. - -## PARAMETERS - -### -Connection -Connection to be used by cmdlet - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPCommSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPCommSite.md deleted file mode 100644 index b5b05172f7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPCommSite.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnpcommsite -applicable: SharePoint Online -schema: 2.0.0 -title: Enable-PnPCommSite ---- - -# Enable-PnPCommSite - -## SYNOPSIS -Enables the modern communication site experience on a classic team site. - -## SYNTAX - -```powershell -Enable-PnPCommSite [-DesignPackageId <String>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command will enable the modern site experience on a classic team site. The site must be the root site of the site collection. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Enable-PnPCommSite -``` - -Enables the modern communication site experience on a classic team site - -### ------------------EXAMPLE 2------------------ -```powershell -Enable-PnPCommSite -DesignPackageId 6142d2a0-63a5-4ba0-aede-d9fefca2c767 -``` - -Enables the modern communication site experience on a classic team site, allowing to specify the design package to be applied - -## PARAMETERS - -### -DesignPackageId -The id (guid) of the design package to apply: 96c933ac-3698-44c7-9f4a-5fd17d71af9e (Topic = default), 6142d2a0-63a5-4ba0-aede-d9fefca2c767 (Showcase) or f6cc5403-0d63-442e-96c0-285923709ffc (Blank) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPFeature.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPFeature.md deleted file mode 100644 index f74c012937..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPFeature.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnpfeature -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Enable-PnPFeature ---- - -# Enable-PnPFeature - -## SYNOPSIS -Enables a feature - -## SYNTAX - -```powershell -Enable-PnPFeature -Identity <GuidPipeBind> - [-Force [<SwitchParameter>]] - [-Scope <FeatureScope>] - [-Sandboxed [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Enable-PnPFeature -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will enable the feature with the id "99a00f6e-fb81-4dc7-8eac-e09c6f9132fe" - -### ------------------EXAMPLE 2------------------ -```powershell -Enable-PnPFeature -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Force -``` - -This will enable the feature with the id "99a00f6e-fb81-4dc7-8eac-e09c6f9132fe" with force. - -### ------------------EXAMPLE 3------------------ -```powershell -Enable-PnPFeature -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Web -``` - -This will enable the feature with the id "99a00f6e-fb81-4dc7-8eac-e09c6f9132fe" with the web scope. - -## PARAMETERS - -### -Force -Specifies whether to overwrite an existing feature with the same feature identifier. This parameter is ignored if there are no errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The id of the feature to enable. - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Sandboxed -Specify this parameter if the feature you're trying to activate is part of a sandboxed solution. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scope -Specify the scope of the feature to activate, either Web or Site. Defaults to Web. - -```yaml -Type: FeatureScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPInPlaceRecordsManagementForSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPInPlaceRecordsManagementForSite.md deleted file mode 100644 index 0e8409343c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPInPlaceRecordsManagementForSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnpinplacerecordsmanagementforsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Enable-PnPInPlaceRecordsManagementForSite ---- - -# Enable-PnPInPlaceRecordsManagementForSite - -## SYNOPSIS -Enables in place records management for a site. - -## SYNTAX - -```powershell -Enable-PnPInPlaceRecordsManagementForSite [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Enable-PnPInPlaceRecordsManagementForSite -``` - -The in place records management feature will be enabled and the in place record management will be enabled in all locations with record declaration allowed by all contributors and undeclaration by site admins - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPPowerShellTelemetry.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPPowerShellTelemetry.md deleted file mode 100644 index 1864503fcc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPPowerShellTelemetry.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnppowershelltelemetry -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Enable-PnPPowerShellTelemetry ---- - -# Enable-PnPPowerShellTelemetry - -## SYNOPSIS -Enables PnP PowerShell telemetry tracking. - -## SYNTAX - -```powershell -Enable-PnPPowerShellTelemetry [-Force [<SwitchParameter>]] -``` - -## DESCRIPTION -In order to help to make PnP PowerShell better, we can track anonymous telemetry. We track the version of the cmdlets you are using, which cmdlet you are executing and which version of SharePoint you are connecting to. Use Disable-PnPPowerShellTelemetry to turn this off, alternative, use the -NoTelemetry switch on Connect-PnPOnline to turn it off for that session. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Enable-PnPPowerShellTelemetry -``` - -Will prompt you to confirm to enable telemetry tracking. - -### ------------------EXAMPLE 2------------------ -```powershell -Enable-PnPPowerShellTelemetry -Force -``` - -Will enable telemetry tracking without prompting. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPResponsiveUI.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPResponsiveUI.md deleted file mode 100644 index c343f42c92..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPResponsiveUI.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnpresponsiveui -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Enable-PnPResponsiveUI ---- - -# Enable-PnPResponsiveUI - -## SYNOPSIS -Activates the PnP Response UI Add-on - -## SYNTAX - -```powershell -Enable-PnPResponsiveUI [-InfrastructureSiteUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Enables the PnP Responsive UI implementation on a classic SharePoint Site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Enable-PnPResponsiveUI -``` - -Will upload a CSS file, a JavaScript file and adds a custom action to the root web of the current site collection, enabling the responsive UI on the site collection. The CSS and JavaScript files are located in the style library, in a folder called SP.Responsive.UI. - -## PARAMETERS - -### -InfrastructureSiteUrl -A full URL pointing to an infrastructure site. If specified, it will add a custom action pointing to the responsive UI JS code in that site. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPSiteClassification.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPSiteClassification.md deleted file mode 100644 index 21e9cf059a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPSiteClassification.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnpsiteclassification -applicable: SharePoint Online -schema: 2.0.0 -title: Enable-PnPSiteClassification ---- - -# Enable-PnPSiteClassification - -## SYNOPSIS -Enables Site Classifications for the tenant. Requires a connection to the Microsoft Graph. - -## SYNTAX - -```powershell -Enable-PnPSiteClassification -Classifications <String> - -DefaultClassification <String> - [-UsageGuidelinesUrl <String>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Enable-PnPSiteClassification -Classifications "HBI","LBI","Top Secret" -DefaultClassification "LBI" -``` - -Enables Site Classifications for your tenant and provides three classification values. The default value will be set to "LBI" - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Enable-PnPSiteClassification -Classifications "HBI","LBI","Top Secret" -UsageGuidelinesUrl https://aka.ms/sppnp -``` - -Enables Site Classifications for your tenant and provides three classification values. The usage guideliness will be set to the specified URL. - -## PARAMETERS - -### -Classifications - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DefaultClassification - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -UsageGuidelinesUrl - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPTenantServicePrincipal.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPTenantServicePrincipal.md deleted file mode 100644 index dc2adadebc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPTenantServicePrincipal.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnptenantserviceprincipal -applicable: SharePoint Online -schema: 2.0.0 -title: Enable-PnPTenantServicePrincipal ---- - -# Enable-PnPTenantServicePrincipal - -## SYNOPSIS -Enables the current tenant's "SharePoint Online Client" service principal. - -## SYNTAX - -```powershell -Enable-PnPTenantServicePrincipal [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Enables the current tenant's "SharePoint Online Client" service principal. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePage.md deleted file mode 100644 index 00e8d8a97f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePage.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/export-pnpclientsidepage -applicable: SharePoint Online -schema: 2.0.0 -title: Export-PnPClientSidePage ---- - -# Export-PnPClientSidePage - -## SYNOPSIS -Exports a Client Side Page to a PnP Provisioning Template - -## SYNTAX - -```powershell -Export-PnPClientSidePage -Identity <ClientSidePagePipeBind> - [-PersistBrandingFiles [<SwitchParameter>]] - [-Out <String>] - [-Force [<SwitchParameter>]] - [-Configuration <ExtractConfigurationPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Export-PnPClientSidePage -Identity Home.aspx -``` - -Exports the page 'Home.aspx' to a new PnP Provisioning Template - -## PARAMETERS - -### -Configuration -Specify a JSON configuration file to configure the extraction progress. - -```yaml -Type: ExtractConfigurationPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Specify to override the question to overwrite a file if it already exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The name of the page - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Out -If specified the template will be saved to the file specified with this parameter. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PersistBrandingFiles -If specified referenced files will be exported to the current folder. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePageMapping.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePageMapping.md deleted file mode 100644 index 32b9a86c7d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPClientSidePageMapping.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/export-pnpclientsidepagemapping -applicable: SharePoint Online -schema: 2.0.0 -title: Export-PnPClientSidePageMapping ---- - -# Export-PnPClientSidePageMapping - -## SYNOPSIS -Get's the built-in maping files or a custom mapping file for your publishing portal page layouts. These mapping files are used to tailor the page transformation experience. - -## SYNTAX - -```powershell -Export-PnPClientSidePageMapping [-BuiltInWebPartMapping [<SwitchParameter>]] - [-BuiltInPageLayoutMapping [<SwitchParameter>]] - [-CustomPageLayoutMapping [<SwitchParameter>]] - [-PublishingPage <PagePipeBind>] - [-AnalyzeOOBPageLayouts [<SwitchParameter>]] - [-Folder <String>] - [-Overwrite [<SwitchParameter>]] - [-Logging [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Export-PnPClientSidePageMapping -BuiltInPageLayoutMapping -CustomPageLayoutMapping -Folder c:\\temp -Overwrite -``` - -Exports the built in page layout mapping and analyzes the current site's page layouts and exports these to files in folder c:\temp - -### ------------------EXAMPLE 2------------------ -```powershell -Export-PnPClientSidePageMapping -CustomPageLayoutMapping -PublishingPage mypage.aspx -Folder c:\\temp -Overwrite -``` - -Analyzes the page layout of page mypage.aspx and exports this to a file in folder c:\temp - -### ------------------EXAMPLE 3------------------ -```powershell -Export-PnPClientSidePageMapping -BuiltInWebPartMapping -Folder c:\\temp -Overwrite -``` - -Exports the built in webpart mapping to a file in folder c:\temp. Use this a starting basis if you want to tailer the web part mapping behavior. - -## PARAMETERS - -### -AnalyzeOOBPageLayouts -Set this flag if you also want to analyze the OOB page layouts...typically these are covered via the default mapping, but if you've updated these page layouts you might want to analyze them again - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -BuiltInPageLayoutMapping -Exports the builtin pagelayout mapping file (only needed for publishing page transformation) - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -BuiltInWebPartMapping -Exports the builtin web part mapping file - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CustomPageLayoutMapping -Analyzes the pagelayouts in the current publishing portal and exports them as a pagelayout mapping file - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Folder -The folder to created the mapping file(s) in - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Logging -Outputs analyser logging to the console - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Overwrite -Overwrites existing mapping files - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PublishingPage -The name of the publishing page to export a page layout mapping file for - -```yaml -Type: PagePipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPListToProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPListToProvisioningTemplate.md deleted file mode 100644 index aaf0ce810d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPListToProvisioningTemplate.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/export-pnplisttoprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Export-PnPListToProvisioningTemplate ---- - -# Export-PnPListToProvisioningTemplate - -## SYNOPSIS -Exports one or more lists to provisioning template - -## SYNTAX - -```powershell -Export-PnPListToProvisioningTemplate -List <String> - [-Out <String>] - [-Force [<SwitchParameter>]] - [-OutputInstance [<SwitchParameter>]] - [-Schema <XMLPnPSchemaVersion>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Export-PnPListToProvisioningTemplate -Out template.xml -List "Documents" -``` - -Extracts a list to a new provisioning template including the list specified by title or ID. - -### ------------------EXAMPLE 2------------------ -```powershell -Export-PnPListToProvisioningTemplate -Out template.pnp -List "Documents","Events" -``` - -Extracts a list to a new provisioning template Office Open XML file, including the lists specified by title or ID. - -## PARAMETERS - -### -Force -Overwrites the output file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -Specify the lists to extract, either providing their ID or their Title. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -OutputInstance -Returns the template as an in-memory object, which is an instance of the ProvisioningTemplate type of the PnP Core Component. It cannot be used together with the -Out parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Schema -The schema of the output to use, defaults to the latest schema - -```yaml -Type: XMLPnPSchemaVersion -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPTaxonomy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPTaxonomy.md deleted file mode 100644 index 47eb8e8c13..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPTaxonomy.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/export-pnptaxonomy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Export-PnPTaxonomy ---- - -# Export-PnPTaxonomy - -## SYNOPSIS -Exports a taxonomy to either the output or to a file. - -## SYNTAX - -### TermSet -```powershell -Export-PnPTaxonomy [-TermSetId <GuidPipeBind>] - [-TermStoreName <String>] - [-Lcid <Int>] - [-IncludeID [<SwitchParameter>]] - [-Path <String>] - [-Force [<SwitchParameter>]] - [-Delimiter <String>] - [-Encoding <Encoding>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Export-PnPTaxonomy -``` - -Exports the full taxonomy to the standard output - -### ------------------EXAMPLE 2------------------ -```powershell -Export-PnPTaxonomy -Path c:\output.txt -``` - -Exports the full taxonomy the file output.txt - -### ------------------EXAMPLE 3------------------ -```powershell -Export-PnPTaxonomy -Path c:\output.txt -TermSetId f6f43025-7242-4f7a-b739-41fa32847254 -``` - -Exports the term set with the specified id - -### ------------------EXAMPLE 4------------------ -```powershell -Export-PnPTaxonomy -Path c:\output.txt -TermSetId f6f43025-7242-4f7a-b739-41fa32847254 -Lcid 1044 -``` - -Exports the term set with the specified id using Norwegian labels - -## PARAMETERS - -### -Delimiter -The path delimiter to be used, by default this is '|' - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Encoding -Defaults to Unicode - -```yaml -Type: Encoding -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeID -If specified will include the ids of the taxonomy items in the output. Format: <label>;#<guid> - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lcid -Specify the language code for the exported terms - -```yaml -Type: Int -Parameter Sets: TermSet - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -File to export the data to. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermSetId -If specified, will export the specified termset only - -```yaml -Type: GuidPipeBind -Parameter Sets: TermSet - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermStoreName -Term store to export; if not specified the default term store is used. - -```yaml -Type: String -Parameter Sets: TermSet - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPTermGroupToXml.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPTermGroupToXml.md deleted file mode 100644 index 41cefa4fdf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Export-PnPTermGroupToXml.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/export-pnptermgrouptoxml -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Export-PnPTermGroupToXml ---- - -# Export-PnPTermGroupToXml - -## SYNOPSIS -Exports a taxonomy TermGroup to either the output or to an XML file. - -## SYNTAX - -```powershell -Export-PnPTermGroupToXml [-Identity <Id, Title or TermGroup>] - [-Out <String>] - [-FullTemplate [<SwitchParameter>]] - [-Encoding <Encoding>] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Export-PnPTermGroupToXml -``` - -Exports all term groups in the default site collection term store to the standard output - -### ------------------EXAMPLE 2------------------ -```powershell -Export-PnPTermGroupToXml -Out output.xml -``` - -Exports all term groups in the default site collection term store to the file 'output.xml' in the current folder - -### ------------------EXAMPLE 3------------------ -```powershell -Export-PnPTermGroupToXml -Out c:\output.xml -Identity "Test Group" -``` - -Exports the term group with the specified name to the file 'output.xml' located in the root folder of the C: drive. - -### ------------------EXAMPLE 4------------------ -```powershell -$termgroup = Get-PnPTermGroup -GroupName Test -$termgroup | Export-PnPTermGroupToXml -Out c:\output.xml -``` - -Retrieves a termgroup and subsequently exports that term group to a the file named 'output.xml' - -## PARAMETERS - -### -Encoding -Defaults to Unicode - -```yaml -Type: Encoding -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -FullTemplate -If specified, a full provisioning template structure will be returned - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID or name of the termgroup - -```yaml -Type: Id, Title or TermGroup -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Out -File to export the data to. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Find-PnPFile.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Find-PnPFile.md deleted file mode 100644 index abb0b987ce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Find-PnPFile.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/find-pnpfile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Find-PnPFile ---- - -# Find-PnPFile - -## SYNOPSIS -Finds a file in the virtual file system of the web. - -## SYNTAX - -### Web -```powershell -Find-PnPFile -Match <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### List -```powershell -Find-PnPFile -Match <String> - -List <ListPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Folder -```powershell -Find-PnPFile -Match <String> - -Folder <FolderPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Find-PnPFile -Match *.master -``` - -Will return all masterpages located in the current web. - -### ------------------EXAMPLE 2------------------ -```powershell -Find-PnPFile -List "Documents" -Match *.pdf -``` - -Will return all pdf files located in given list. - -### ------------------EXAMPLE 3------------------ -```powershell -Find-PnPFile -Folder "Shared Documents/Sub Folder" -Match *.docx -``` - -Will return all docx files located in given folder. - -## PARAMETERS - -### -Folder -Folder object or relative url of a folder to query - -```yaml -Type: FolderPipeBind -Parameter Sets: Folder - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -List title, url or an actual List object to query - -```yaml -Type: ListPipeBind -Parameter Sets: List - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Match -Wildcard query - -```yaml -Type: String -Parameter Sets: Web, List, Folder - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.File - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAccessToken.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAccessToken.md deleted file mode 100644 index 5eabaf62f0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAccessToken.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpaccesstoken -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPAccessToken ---- - -# Get-PnPAccessToken - -## SYNOPSIS -Returns the current OAuth Access token - -## SYNTAX - -```powershell -Get-PnPAccessToken [-Decoded [<SwitchParameter>]] -``` - -## DESCRIPTION -Gets the OAuth 2.0 Access Token to consume the Microsoft Graph API - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAccessToken -``` - -Gets the OAuth 2.0 Access Token to consume the Microsoft Graph API - -## PARAMETERS - -### -Decoded -Returns the access token in a decoded manner - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAlert.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAlert.md deleted file mode 100644 index 7483d35d1b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAlert.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpalert -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Get-PnPAlert ---- - -# Get-PnPAlert - -## SYNOPSIS -Returns registered alerts for a user. - -## SYNTAX - -```powershell -Get-PnPAlert [-List <ListPipeBind>] - [-User <UserPipeBind>] - [-Title <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAlert -``` - -Returns all registered alerts for the current user - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPAlert -List "Demo List" -``` - -Returns all alerts registered on the given list for the current user. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPAlert -List "Demo List" -User "i:0#.f|membership|Alice@contoso.onmicrosoft.com" -``` - -Returns all alerts registered on the given list for the specified user. - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPAlert -Title "Demo Alert" -``` - -Returns all alerts with the given title for the current user. Title comparison is case sensitive. - -## PARAMETERS - -### -List -The ID, Title or Url of the list. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Title -Retrieve alerts with this title. Title comparison is case sensitive. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -User -User to retrieve the alerts for (User ID, login name or actual User object). Skip this parameter to retrieve the alerts for the current user. Note: Only site owners can retrieve alerts for other users. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: UserPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPApp.md deleted file mode 100644 index aa192b30b3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPApp.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpapp -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Get-PnPApp ---- - -# Get-PnPApp - -## SYNOPSIS -Returns the available apps from the app catalog - -## SYNTAX - -```powershell -Get-PnPApp [-Identity <AppMetadataPipeBind>] - [-Scope <AppCatalogScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPApp -``` - -This will return all available apps from the tenant app catalog. It will list the installed version in the current site. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPApp -Scope Site -``` - -This will return all available apps from the site collection scoped app catalog. It will list the installed version in the current site. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPApp -Identity 2646ccc3-6a2b-46ef-9273-81411cbbb60f -``` - -This will retrieve the specific app from the app catalog. - -## PARAMETERS - -### -Identity -Specifies the Id of an app which is available in the app catalog - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<OfficeDevPnP.Core.ALM.AppMetadata> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAppAuthAccessToken.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAppAuthAccessToken.md deleted file mode 100644 index 3929d65056..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAppAuthAccessToken.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpappauthaccesstoken -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPAppAuthAccessToken ---- - -# Get-PnPAppAuthAccessToken - -## SYNOPSIS -Returns the access token - -## SYNTAX - -```powershell -Get-PnPAppAuthAccessToken [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns the access token from the current client context (only works with App-Only authentication) - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$accessToken = Get-PnPAppAuthAccessToken -``` - -This will put the access token from current context in the $accessToken variable. Will only work in App authentication flow (App+user or App-Only) - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAppInstance.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAppInstance.md deleted file mode 100644 index c505a15581..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAppInstance.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpappinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPAppInstance ---- - -# Get-PnPAppInstance - -## SYNOPSIS -Returns a SharePoint AddIn Instance - -## SYNTAX - -### -```powershell -Get-PnPAppInstance [-Includes <String[]>] - [-Identity <AppPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns a SharePoint App/Addin that has been installed in the current site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAppInstance -``` - -This will return all addin instances in the site. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPAppInstance -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will return an addin instance with the specified id. - -## PARAMETERS - -### -Identity -Specifies the Id of the App Instance - -```yaml -Type: AppPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<Microsoft.SharePoint.Client.AppInstance> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPApplicationCustomizer.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPApplicationCustomizer.md deleted file mode 100644 index 07b7034101..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPApplicationCustomizer.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpapplicationcustomizer -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Get-PnPApplicationCustomizer ---- - -# Get-PnPApplicationCustomizer - -## SYNOPSIS -Returns all SharePoint Framework client side extension application customizers - -## SYNTAX - -### Custom Action Id -```powershell -Get-PnPApplicationCustomizer [-Identity <GuidPipeBind>] - [-Scope <CustomActionScope>] - [-ThrowExceptionIfCustomActionNotFound [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### -```powershell -Get-PnPApplicationCustomizer [-Includes <String[]>] - [-Scope <CustomActionScope>] - [-ThrowExceptionIfCustomActionNotFound [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Client Side Component Id -```powershell -Get-PnPApplicationCustomizer -ClientSideComponentId <GuidPipeBind> - [-Scope <CustomActionScope>] - [-ThrowExceptionIfCustomActionNotFound [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns all SharePoint Framework client side extension application customizers registered on the current web and/or site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPApplicationCustomizer -``` - -Returns the custom action representing the SharePoint Framework client side extension registrations registered on the current site collection and web. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPApplicationCustomizer -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -``` - -Returns the custom action representing the SharePoint Framework client side extension registration with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2'. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPApplicationCustomizer -ClientSideComponentId aa66f67e-46c0-4474-8a82-42bf467d07f2 -Scope Web -``` - -Returns the custom action(s) being registered for a SharePoint Framework solution having the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2' in its manifest from the current web. - -## PARAMETERS - -### -ClientSideComponentId -The Client Side Component Id of the SharePoint Framework client side extension application customizer found in the manifest for which existing custom action(s) should be removed - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: Client Side Component Id - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Identity -Identity of the SharePoint Framework client side extension application customizer to return. Omit to return all SharePoint Frameworkclient side extension application customizer. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: Custom Action Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Scope -Scope of the SharePoint Framework client side extension application customizer, either Web, Site or All to return both (all is the default) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ThrowExceptionIfCustomActionNotFound -Switch parameter if an exception should be thrown if the requested SharePoint Frameworkclient side extension application customizer does not exist (true) or if omitted, nothing will be returned in case the SharePoint Framework client side extension application customizer does not exist - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAuditing.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAuditing.md deleted file mode 100644 index 82e96e0325..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAuditing.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpauditing -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPAuditing ---- - -# Get-PnPAuditing - -## SYNOPSIS -Get the Auditing setting of a site - -## SYNTAX - -```powershell -Get-PnPAuditing [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAuditing -``` - -Gets the auditing settings of the current site - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Audit - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAuthenticationRealm.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAuthenticationRealm.md deleted file mode 100644 index caf9be21ed..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAuthenticationRealm.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpauthenticationrealm -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPAuthenticationRealm ---- - -# Get-PnPAuthenticationRealm - -## SYNOPSIS -Returns the authentication realm - -## SYNTAX - -```powershell -Get-PnPAuthenticationRealm [-Url <String>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Gets the authentication realm for the current web - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAuthenticationRealm -``` - -This will get the authentication realm for the current connected site - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPAuthenticationRealm -Url https://contoso.sharepoint.com -``` - -This will get the authentication realm for https://contoso.sharepoint.com - -## PARAMETERS - -### -Url -Specifies the URL of the site - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAvailableClientSideComponents.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAvailableClientSideComponents.md deleted file mode 100644 index 29d0cdacee..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAvailableClientSideComponents.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpavailableclientsidecomponents -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Get-PnPAvailableClientSideComponents ---- - -# Get-PnPAvailableClientSideComponents - -## SYNOPSIS -Gets the available client side components on a particular page - -## SYNTAX - -```powershell -Get-PnPAvailableClientSideComponents -Page <ClientSidePagePipeBind> - [-Component <ClientSideComponentPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAvailableClientSideComponents -Page "MyPage.aspx" -``` - -Gets the list of available client side components on the page 'MyPage.aspx' - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPAvailableClientSideComponents $page -``` - -Gets the list of available client side components on the page contained in the $page variable - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPAvailableClientSideComponents -Page "MyPage.aspx" -ComponentName "HelloWorld" -``` - -Gets the client side component 'HelloWorld' if available on the page 'MyPage.aspx' - -## PARAMETERS - -### -Component -Specifies the component instance or Id to look for. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSideComponentPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Page -The name of the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAzureADManifestKeyCredentials.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAzureADManifestKeyCredentials.md deleted file mode 100644 index f5bed80434..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAzureADManifestKeyCredentials.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpazureadmanifestkeycredentials -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 ---- - -# Get-PnPAzureADManifestKeyCredentials - -## SYNOPSIS -Return the JSON Manifest snippet for Azure Apps - -## SYNTAX - -```powershell -Get-PnPAzureADManifestKeyCredentials -CertPath <String> -``` - -## DESCRIPTION -Creates the JSON snippet that is required for the manifest JSON file for Azure WebApplication / WebAPI apps - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAzureADManifestKeyCredentials -CertPath .\mycert.cer -``` - -Output the JSON snippet which needs to be replaced in the application manifest file - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPAzureADManifestKeyCredentials -CertPath .\mycert.cer | Set-Clipboard -``` - -Output the JSON snippet which needs to be replaced in the application manifest file and copies it to the clipboard - -## PARAMETERS - -### -CertPath -Specifies the path to the certificate like .\mycert.cer - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -Outputs a JSON formatted string - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAzureCertificate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAzureCertificate.md deleted file mode 100644 index ce6973739a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAzureCertificate.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpazurecertificate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPAzureCertificate ---- - -# Get-PnPAzureCertificate - -## SYNOPSIS -Get PEM values and manifest settings for an existing certificate (.pfx) for use when using CSOM via an app-only ADAL application. - -See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/SharePoint.ConnectUsingAppPermissions for a sample on how to get started. - -KeyCredentials contains the ADAL app manifest sections. - -Certificate contains the PEM encoded certificate. - -PrivateKey contains the PEM encoded private key of the certificate. - -## SYNTAX - -```powershell -Get-PnPAzureCertificate -CertificatePath <String> - [-CertificatePassword <SecureString>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPAzureCertificate -CertificatePath "mycert.pfx" -``` - -This will output PEM values and ADAL app manifest settings for the certificate mycert.pfx. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPAzureCertificate -CertificatePath "mycert.pfx" -CertificatePassword (ConvertTo-SecureString -String "YourPassword" -AsPlainText -Force) -``` - -This will output PEM values and ADAL app manifest settings for the certificate mycert.pfx which has the password YourPassword. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPAzureCertificate -CertificatePath "mycert.cer" | clip -``` - -Output the JSON snippet which needs to be replaced in the application manifest file and copies it to the clipboard - -## PARAMETERS - -### -CertificatePassword -Password to the certificate (*.pfx) - -```yaml -Type: SecureString -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CertificatePath -Path to the certificate (*.pfx) - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPClientSideComponent.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPClientSideComponent.md deleted file mode 100644 index 24a3bf21b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPClientSideComponent.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpclientsidecomponent -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Get-PnPClientSideComponent ---- - -# Get-PnPClientSideComponent - -## SYNOPSIS -Retrieve one or more Client-Side components from a site page - -## SYNTAX - -```powershell -Get-PnPClientSideComponent -Page <ClientSidePagePipeBind> - [-InstanceId <GuidPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows the retrieval of the components placed on a modern sitepage along with its properties. Note that for a newly created modern site, the Home.aspx page will not be returning any components. This is because the underlying CanvasContent1 will not be populated until the homepage has been edited and published. The reason for this behavior is to allow for the default homepage to be able to be updated by Microsoft as long as it hasn't been modified. For any other site page or after editing and publishing the homepage, this command will return the correct components as they are positioned on the site page. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPClientSideComponent -Page Home -``` - -Returns all controls defined on the given page. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPClientSideComponent -Page Home -InstanceId a2875399-d6ff-43a0-96da-be6ae5875f82 -``` - -Returns a specific control defined on the given page. - -## PARAMETERS - -### -InstanceId -The instance id of the component - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Page -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPClientSidePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPClientSidePage.md deleted file mode 100644 index 5b887af11f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPClientSidePage.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpclientsidepage -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Get-PnPClientSidePage ---- - -# Get-PnPClientSidePage - -## SYNOPSIS -Gets a modern site page - -## SYNTAX - -```powershell -Get-PnPClientSidePage -Identity <ClientSidePagePipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows the retrieval of a modern sitepage along with its properties and contents on it. Note that for a newly created modern site, the Columns and Sections of the Home.aspx page will not be filled according to the actual site page contents. This is because the underlying CanvasContent1 will not be populated until the homepage has been edited and published. The reason for this behavior is to allow for the default homepage to be able to be updated by Microsoft as long as it hasn't been modified. For any other site page or after editing and publishing the homepage, this command will return the correct columns and sections as they are positioned on the site page. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPClientSidePage -Identity "MyPage.aspx" -``` - -Gets the Modern Page (Client-Side) named 'MyPage.aspx' in the current SharePoint site - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPClientSidePage "MyPage" -``` - -Gets the Modern Page (Client-Side) named 'MyPage.aspx' in the current SharePoint site - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPClientSidePage "Templates/MyPageTemplate" -``` - -Gets the Modern Page (Client-Side) named 'MyPageTemplate.aspx' from the templates folder of the Page Library in the current SharePoint site - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPClientSidePage -Identity "MyPage.aspx" -Web (Get-PnPWeb -Identity "Subsite1") -``` - -Gets the Modern Page (Client-Side) named 'MyPage.aspx' from the subsite named 'Subsite1' - -## PARAMETERS - -### -Identity -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPConnection.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPConnection.md deleted file mode 100644 index 801cde75ef..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPConnection.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpconnection -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPConnection ---- - -# Get-PnPConnection - -## SYNOPSIS -Returns the current context - -## DESCRIPTION -Returns a PnP PowerShell Connection for use with the -Connection parameter on other cmdlets. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$ctx = Get-PnPConnection -``` - -This will put the current connection for use with the -Connection parameter on other cmdlets. - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContentType.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContentType.md deleted file mode 100644 index a2c0ddad26..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContentType.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpcontenttype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPContentType ---- - -# Get-PnPContentType - -## SYNOPSIS -Retrieves a content type - -## SYNTAX - -```powershell -Get-PnPContentType [-Identity <ContentTypePipeBind>] - [-List <ListPipeBind>] - [-InSiteHierarchy [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPContentType -``` - -This will get a listing of all available content types within the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPContentType -InSiteHierarchy -``` - -This will get a listing of all available content types within the site collection - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPContentType -Identity "Project Document" -``` - -This will get the content type with the name "Project Document" within the current context - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPContentType -List "Documents" -``` - -This will get a listing of all available content types within the list "Documents" - -## PARAMETERS - -### -Identity -Name or ID of the content type to retrieve - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -InSiteHierarchy -Search site hierarchy for content types - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -List to query - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.ContentType - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContentTypePublishingHubUrl.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContentTypePublishingHubUrl.md deleted file mode 100644 index 7bb044b4df..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContentTypePublishingHubUrl.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpcontenttypepublishinghuburl -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPContentTypePublishingHubUrl ---- - -# Get-PnPContentTypePublishingHubUrl - -## SYNOPSIS -Returns the url to Content Type Publishing Hub - -## SYNTAX - -```powershell -Get-PnPContentTypePublishingHubUrl [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$url = Get-PnPContentTypePublishingHubUrl -Connect-PnPOnline -Url $url -Get-PnPContentType - -``` - -This will retrieve the url to the content type hub, connect to it, and then retrieve the content types form that site - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContext.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContext.md deleted file mode 100644 index 247b7e71cb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPContext.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpcontext -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPContext ---- - -# Get-PnPContext - -## SYNOPSIS -Returns the current context - -## DESCRIPTION -Returns a Client Side Object Model context - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$ctx = Get-PnPContext -``` - -This will put the current context in the $ctx variable. - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPOnline -Url $siteAurl -Credentials $credentials -$ctx = Get-PnPContext -Get-PnPList # returns the lists from site specified with $siteAurl -Connect-PnPOnline -Url $siteBurl -Credentials $credentials -Get-PnPList # returns the lists from the site specified with $siteBurl -Set-PnPContext -Context $ctx # switch back to site A -Get-PnPList # returns the lists from site A -``` - - - -## OUTPUTS - -### Microsoft.SharePoint.Client.ClientContext - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPCustomAction.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPCustomAction.md deleted file mode 100644 index c8fc40b717..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPCustomAction.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpcustomaction -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPCustomAction ---- - -# Get-PnPCustomAction - -## SYNOPSIS -Return user custom actions - -## SYNTAX - -### -```powershell -Get-PnPCustomAction [-Includes <String[]>] - [-Identity <GuidPipeBind>] - [-Scope <CustomActionScope>] - [-ThrowExceptionIfCustomActionNotFound [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns all or a specific user custom action - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPCustomAction -``` - -Returns all custom actions of the current site. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPCustomAction -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -``` - -Returns the custom action with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2'. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPCustomAction -Scope web -``` - -Returns all custom actions for the current web object. - -## PARAMETERS - -### -Identity -Identity of the CustomAction to return. Omit to return all CustomActions. - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Scope -Scope of the CustomAction, either Web, Site or All to return both - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ThrowExceptionIfCustomActionNotFound -Switch parameter if an exception should be thrown if the requested CustomAction does not exist (true) or if omitted, nothing will be returned in case the CustomAction does not exist - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<Microsoft.SharePoint.Client.UserCustomAction> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDefaultColumnValues.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDefaultColumnValues.md deleted file mode 100644 index c2da78c064..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDefaultColumnValues.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpdefaultcolumnvalues -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPDefaultColumnValues ---- - -# Get-PnPDefaultColumnValues - -## SYNOPSIS -Gets the default column values for all folders in document library - -## SYNTAX - -```powershell -Get-PnPDefaultColumnValues -List <ListPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Gets the default column values for a document library, per folder. Supports both text, people and taxonomy fields. - -## PARAMETERS - -### -List -The ID, Name or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDeletedUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDeletedUnifiedGroup.md deleted file mode 100644 index a3f99168dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDeletedUnifiedGroup.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpdeletedunifiedgroup -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPDeletedUnifiedGroup ---- - -# Get-PnPDeletedUnifiedGroup - -## SYNOPSIS -Gets one deleted Office 365 Group (aka Unified Group) or a list of deleted Office 365 Groups - -## SYNTAX - -```powershell -Get-PnPDeletedUnifiedGroup [-Identity <UnifiedGroupPipeBind>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPDeletedUnifiedGroup -``` - -Retrieves all deleted Office 365 Groups - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPDeletedUnifiedGroup -Identity 38b32e13-e900-4d95-b860-fb52bc07ca7f -``` - -Retrieves a specific deleted Office 365 Group based on its ID - -## PARAMETERS - -### -Identity -The Identity of the Office 365 Group. - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDocumentSetTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDocumentSetTemplate.md deleted file mode 100644 index c17f74b87f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPDocumentSetTemplate.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpdocumentsettemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPDocumentSetTemplate ---- - -# Get-PnPDocumentSetTemplate - -## SYNOPSIS -Retrieves a document set template - -## SYNTAX - -### -```powershell -Get-PnPDocumentSetTemplate -Identity <DocumentSetPipeBind> - [-Includes <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPDocumentSetTemplate -Identity "Test Document Set" -``` - -This will get the document set template with the name "Test Document Set" - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPDocumentSetTemplate -Identity "0x0120D520005DB65D094035A241BAC9AF083F825F3B" -``` - -This will get the document set template with the id "0x0120D520005DB65D094035A241BAC9AF083F825F3B" - -## PARAMETERS - -### -Identity -Either specify a name, an id, a document set template object or a content type object - -```yaml -Type: DocumentSetPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.DocumentSet.DocumentSetTemplate - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPEventReceiver.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPEventReceiver.md deleted file mode 100644 index 9bf842b49b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPEventReceiver.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpeventreceiver -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPEventReceiver ---- - -# Get-PnPEventReceiver - -## SYNOPSIS -Return registered eventreceivers - -## SYNTAX - -### List -```powershell -Get-PnPEventReceiver [-List <ListPipeBind>] - [-Identity <EventReceiverPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### -```powershell -Get-PnPEventReceiver [-Includes <String[]>] - [-Identity <EventReceiverPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns all registered or a specific eventreceiver - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPEventReceiver -``` - -This will return all registered event receivers on the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPEventReceiver -Identity fb689d0e-eb99-4f13-beb3-86692fd39f22 -``` - -This will return the event receiver with the provided ReceiverId "fb689d0e-eb99-4f13-beb3-86692fd39f22" from the current web - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPEventReceiver -Identity MyReceiver -``` - -This will return the event receiver with the provided ReceiverName "MyReceiver" from the current web - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPEventReceiver -List "ProjectList" -``` - -This will return all registered event receivers in the provided "ProjectList" list - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPEventReceiver -List "ProjectList" -Identity fb689d0e-eb99-4f13-beb3-86692fd39f22 -``` - -This will return the event receiver in the provided "ProjectList" list with with the provided ReceiverId "fb689d0e-eb99-4f13-beb3-86692fd39f22" - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPEventReceiver -List "ProjectList" -Identity MyReceiver -``` - -This will return the event receiver in the "ProjectList" list with the provided ReceiverName "MyReceiver" - -## PARAMETERS - -### -Identity -The Guid of the event receiver - -```yaml -Type: EventReceiverPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -List -The list object from which to get the event receiver object - -```yaml -Type: ListPipeBind -Parameter Sets: List - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.EventReceiverDefinition - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPException.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPException.md deleted file mode 100644 index 1f9b0c71c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPException.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpexception -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPException ---- - -# Get-PnPException - -## SYNOPSIS -Returns the last exception that occurred - -## SYNTAX - -```powershell -Get-PnPException [-All [<SwitchParameter>]] -``` - -## DESCRIPTION -Returns the last exception which can be used while debugging PnP Cmdlets - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPException -``` - -Returns the last exception - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPException -All -``` - -Returns all exceptions that occurred - -## PARAMETERS - -### -All -Show all exceptions - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFeature.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFeature.md deleted file mode 100644 index 3b2e3a36bc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFeature.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpfeature -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPFeature ---- - -# Get-PnPFeature - -## SYNOPSIS -Returns all activated or a specific activated feature - -## SYNTAX - -### -```powershell -Get-PnPFeature [-Includes <String[]>] - [-Identity <FeaturePipeBind>] - [-Scope <FeatureScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPFeature -``` - -This will return all activated web scoped features - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPFeature -Scope Site -``` - -This will return all activated site scoped features - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPFeature -Identity fb689d0e-eb99-4f13-beb3-86692fd39f22 -``` - -This will return a specific activated web scoped feature - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPFeature -Identity fb689d0e-eb99-4f13-beb3-86692fd39f22 -Scope Site -``` - -This will return a specific activated site scoped feature - -## PARAMETERS - -### -Identity -The feature ID or name to query for, Querying by name is not supported in version 15 of the Client Side Object Model - -```yaml -Type: FeaturePipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Scope -The scope of the feature. Defaults to Web. - -```yaml -Type: FeatureScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<Microsoft.SharePoint.Client.Feature> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPField.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPField.md deleted file mode 100644 index 81216124d6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPField.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpfield -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPField ---- - -# Get-PnPField - -## SYNOPSIS -Returns a field from a list or site - -## SYNTAX - -### -```powershell -Get-PnPField [-Includes <String[]>] - [-List <ListPipeBind>] - [-Identity <FieldPipeBind>] - [-Group <String>] - [-InSiteHierarchy [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPField -``` - -Gets all the fields from the current site - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPField -List "Demo list" -Identity "Speakers" -``` - -Gets the speakers field from the list Demo list - -## PARAMETERS - -### -Group -Filter to the specified group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The field object or name to get - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -InSiteHierarchy -Search site hierarchy for fields - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The list object or name where to get the field from - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Field - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFile.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFile.md deleted file mode 100644 index b081ba16e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFile.md +++ /dev/null @@ -1,237 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpfile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPFile ---- - -# Get-PnPFile - -## SYNOPSIS -Downloads a file. - -## SYNTAX - -### Return as file object -```powershell -Get-PnPFile -Url <String> - [-AsFileObject [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Return as list item -```powershell -Get-PnPFile -Url <String> - [-AsListItem [<SwitchParameter>]] - [-ThrowExceptionIfFileNotFound [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Return as string -```powershell -Get-PnPFile -Url <String> - [-AsString [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Save to local path -```powershell -Get-PnPFile -Url <String> - -AsFile [<SwitchParameter>] - [-Path <String>] - [-Filename <String>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPFile -Url /sites/project/_catalogs/themes/15/company.spcolor -``` - -Retrieves the file and downloads it to the current folder - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPFile -Url /sites/project/_catalogs/themes/15/company.spcolor -Path c:\temp -FileName company.spcolor -AsFile -``` - -Retrieves the file and downloads it to c:\temp\company.spcolor - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPFile -Url /sites/project/_catalogs/themes/15/company.spcolor -AsString -``` - -Retrieves the file and outputs its contents to the console - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPFile -Url /sites/project/_catalogs/themes/15/company.spcolor -AsFile -``` - -Retrieves the file and returns it as a File object - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPFile -Url /sites/project/_catalogs/themes/15/company.spcolor -AsListItem -``` - -Retrieves the file and returns it as a ListItem object - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPFile -Url _catalogs/themes/15/company.spcolor -Path c:\temp -FileName company.spcolor -AsFile -``` - -Retrieves the file by site relative URL and downloads it to c:\temp\company.spcolor - -## PARAMETERS - -### -AsFile - - -```yaml -Type: SwitchParameter -Parameter Sets: Save to local path - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -AsFileObject -Retrieve the file contents as a file object. - -```yaml -Type: SwitchParameter -Parameter Sets: Return as file object - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AsListItem -Returns the file as a listitem showing all its properties - -```yaml -Type: SwitchParameter -Parameter Sets: Return as list item - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AsString -Retrieve the file contents as a string - -```yaml -Type: SwitchParameter -Parameter Sets: Return as string - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Filename -Name for the local file - -```yaml -Type: String -Parameter Sets: Save to local path - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Overwrites the file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: Save to local path - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Local path where the file should be saved - -```yaml -Type: String -Parameter Sets: Save to local path - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ThrowExceptionIfFileNotFound -If provided in combination with -AsListItem, a System.ArgumentException will be thrown if the file specified in the -Url argument does not exist. Otherwise it will return nothing instead. - -```yaml -Type: SwitchParameter -Parameter Sets: Return as list item - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -The URL (server or site relative) to the file - -```yaml -Type: String -Parameter Sets: Return as file object, Return as list item, Save to local path, Return as string -Aliases: ServerRelativeUrl,SiteRelativeUrl - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.File - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFolder.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFolder.md deleted file mode 100644 index 9d300291e4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFolder.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpfolder -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPFolder ---- - -# Get-PnPFolder - -## SYNOPSIS -Return a folder object - -## SYNTAX - -### -```powershell -Get-PnPFolder [-Includes <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Folder By Url -```powershell -Get-PnPFolder -Url <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Folders In List -```powershell -Get-PnPFolder -List <ListPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Retrieves a folder if it exists or all folders inside a provided list or library. Use Resolve-PnPFolder to create the folder if it does not exist. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPFolder -Url "Shared Documents" -``` - -Returns the folder called 'Shared Documents' which is located in the root of the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPFolder -Url "/sites/demo/Shared Documents" -``` - -Returns the folder called 'Shared Documents' which is located in the root of the current web - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPFolder -List "Shared Documents" -``` - -Returns the folder(s) residing inside a folder called 'Shared Documents' - -## PARAMETERS - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -List -Name, ID or instance of a list or document library to retrieve the folders residing in it for. - -```yaml -Type: ListPipeBind -Parameter Sets: Folders In List - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Url -Site or server relative URL of the folder to retrieve. In the case of a server relative url, make sure that the url starts with the managed path as the current web. - -```yaml -Type: String -Parameter Sets: Folder By Url -Aliases: RelativeUrl - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Folder - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Resolve-PnPFolder](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/sharepoint/sharepoint-ps/sharepoint-pnp/Resolve-PnPFolder.md) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFolderItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFolderItem.md deleted file mode 100644 index f7c2acf12f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPFolderItem.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpfolderitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPFolderItem ---- - -# Get-PnPFolderItem - -## SYNOPSIS -List content in folder - -## SYNTAX - -### Folder via url -```powershell -Get-PnPFolderItem [-FolderSiteRelativeUrl <String>] - [-ItemType <String>] - [-ItemName <String>] - [-Recursive [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Folder via pipebind -```powershell -Get-PnPFolderItem [-Identity <FolderPipeBind>] - [-ItemType <String>] - [-ItemName <String>] - [-Recursive [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPFolderItem -FolderSiteRelativeUrl "SitePages" -``` - -Returns the contents of the folder SitePages which is located in the root of the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPFolderItem -FolderSiteRelativeUrl "SitePages" -ItemName "Default.aspx" -``` - -Returns the file 'Default.aspx' which is located in the folder SitePages which is located in the root of the current web - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPFolderItem -FolderSiteRelativeUrl "SitePages" -ItemType Folder -``` - -Returns all folders in the folder SitePages which is located in the root of the current web - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPFolderItem -FolderSiteRelativeUrl "SitePages" -ItemType File -``` - -Returns all files in the folder SitePages which is located in the root of the current web - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPFolderItem -FolderSiteRelativeUrl "SitePages" -Recursive -``` - -Returns all files and folders, including contents of any subfolders, in the folder SitePages which is located in the root of the current web - -## PARAMETERS - -### -FolderSiteRelativeUrl -The site relative URL of the folder to retrieve - -```yaml -Type: String -Parameter Sets: Folder via url - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Identity -A folder instance to the folder to retrieve - -```yaml -Type: FolderPipeBind -Parameter Sets: Folder via pipebind - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -ItemName -Optional name of the item to retrieve - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ItemType -The type of contents to retrieve, either File, Folder or All (default) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Recursive -A switch parameter to include contents of all subfolders in the specified folder - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroup.md deleted file mode 100644 index 608e2db9d9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroup.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPGroup ---- - -# Get-PnPGroup - -## SYNOPSIS -Returns a specific SharePoint group or all SharePoint groups in site. - -## SYNTAX - -### ByName -```powershell -Get-PnPGroup [-Identity <GroupPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Members -```powershell -Get-PnPGroup [-AssociatedMemberGroup [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Visitors -```powershell -Get-PnPGroup [-AssociatedVisitorGroup [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Owners -```powershell -Get-PnPGroup [-AssociatedOwnerGroup [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### -```powershell -Get-PnPGroup [-Includes <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPGroup -``` - -Returns all SharePoint groups in a site - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPGroup -Identity 'My Site Users' -``` - -This will return the group called 'My Site Users' in if available in the current site - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPGroup -AssociatedMemberGroup -``` - -This will return the current members group for the site - -## PARAMETERS - -### -AssociatedMemberGroup -Retrieve the associated member group - -```yaml -Type: SwitchParameter -Parameter Sets: Members - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AssociatedOwnerGroup -Retrieve the associated owner group - -```yaml -Type: SwitchParameter -Parameter Sets: Owners - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AssociatedVisitorGroup -Retrieve the associated visitor group - -```yaml -Type: SwitchParameter -Parameter Sets: Visitors - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Get a specific group by name - -```yaml -Type: GroupPipeBind -Parameter Sets: ByName -Aliases: Name - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<Microsoft.SharePoint.Client.Group> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroupMembers.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroupMembers.md deleted file mode 100644 index b96d42abd6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroupMembers.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpgroupmembers -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPGroupMembers ---- - -# Get-PnPGroupMembers - -## SYNOPSIS -Retrieves all members of a group - -## SYNTAX - -```powershell -Get-PnPGroupMembers -Identity <GroupPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command will return all the users that are a member of the provided SharePoint Group - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPGroupMembers -Identity 'Marketing Site Members' -``` - -Returns all the users that are a member of the group 'Marketing Site Members' in the current sitecollection - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPGroup | Get-PnPGroupMembers -``` - -Returns all the users that are a member of any of the groups in the current sitecollection - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPGroup | ? Title -Like 'Marketing*' | Get-PnPGroupMembers -``` - -Returns all the users that are a member of any of the groups of which their name starts with the word 'Marketing' in the current sitecollection - -## PARAMETERS - -### -Identity -A group object, an ID or a name of a group - -```yaml -Type: GroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.User - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroupPermissions.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroupPermissions.md deleted file mode 100644 index ae5b58abd4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPGroupPermissions.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpgrouppermissions -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPGroupPermissions ---- - -# Get-PnPGroupPermissions - -## SYNOPSIS -Returns the permissions for a specific SharePoint group - -## SYNTAX - -### ByName -```powershell -Get-PnPGroupPermissions -Identity <GroupPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPGroupPermissions -Identity 'My Site Members' -``` - -Returns the permissions for the SharePoint group with the name 'My Site Members' - -## PARAMETERS - -### -Identity -Get the permissions of a specific group by name - -```yaml -Type: GroupPipeBind -Parameter Sets: ByName -Aliases: Name - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.RoleDefinitionBindingCollection - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHealthScore.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHealthScore.md deleted file mode 100644 index e57e824047..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHealthScore.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnphealthscore -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -schema: 2.0.0 -title: Get-PnPHealthScore ---- - -# Get-PnPHealthScore - -## SYNOPSIS -Retrieves the healthscore of the site given in his Url parameter or from the current connection if the Url parameter is not provided - -## DESCRIPTION -Retrieves the current X-SharePointHealthScore value of the server, or CPU, on which your SharePoint instance runs. X-SharePointHealthScore is a value between 0 and 10, where 0 indicates the server is idle and 10 indicates the server is very busy. For more information visit https://docs.microsoft.com/office365/enterprise/diagnosing-performance-issues-with-sharepoint-online and https://docs.microsoft.com/openspecs/sharepoint_protocols/ms-wsshp/c60ddeb6-4113-4a73-9e97-26b5c3907d33. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPHealthScore -``` - -This will retrieve the current health score of the server. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPHealthScore -Url https://contoso.sharepoint.com -``` - -This will retrieve the current health score for the url https://contoso.sharepoint.com. - -## OUTPUTS - -### System.Int32 - -Returns a int value representing the current health score value of the server. - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHideDefaultThemes.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHideDefaultThemes.md deleted file mode 100644 index d5a13279de..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHideDefaultThemes.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnphidedefaultthemes -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPHideDefaultThemes ---- - -# Get-PnPHideDefaultThemes - -## SYNOPSIS -Returns if the default / OOTB themes should be visible to users or not. - -## SYNTAX - -```powershell -Get-PnPHideDefaultThemes [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns if the default themes are visible. Use Set-PnPHideDefaultThemes to change this value. - -You must be a SharePoint Online global administrator to run the cmdlet. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPHideDefaultThemes -``` - -This example returns the current setting if the default themes should be visible - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHomePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHomePage.md deleted file mode 100644 index bb8b4e86d3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHomePage.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnphomepage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPHomePage ---- - -# Get-PnPHomePage - -## SYNOPSIS -Return the homepage - -## SYNTAX - -```powershell -Get-PnPHomePage [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns the URL to the page set as home page - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPHomePage -``` - -Will return the URL of the home page of the web. - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHomeSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHomeSite.md deleted file mode 100644 index c399dc9aa8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHomeSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnphomesite -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPHomeSite ---- - -# Get-PnPHomeSite - -## SYNOPSIS -Returns the home site url for your tenant - -## SYNTAX - -```powershell -Get-PnPHomeSite [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPHomeSite -``` - -Returns the home site url for your tenant - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHubSite.md deleted file mode 100644 index e11b608f9d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHubSite.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnphubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPHubSite ---- - -# Get-PnPHubSite - -## SYNOPSIS -Retrieve all or a specific hubsite. - -## SYNTAX - -```powershell -Get-PnPHubSite [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPHubSite -``` - -Returns all hubsite properties - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPHubSite -Identity https://contoso.sharepoint.com/sites/myhubsite -``` - -Returns the properties of the specified hubsite - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHubSiteChild.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHubSiteChild.md deleted file mode 100644 index 16bf371999..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHubSiteChild.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnphubsitechild -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPHubSiteChild ---- - -# Get-PnPHubSiteChild - -## SYNOPSIS -Retrieves all sites linked to a specific hub site - -## SYNTAX - -```powershell -Get-PnPHubSiteChild -Identity <HubSitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Retrieves all sites linked to a specific hub site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPHubChildSite -Identity https://contoso.sharepoint.com/sites/myhubsite -``` - -Returns the sites having configured the provided hub site as their hub site - -## PARAMETERS - -### -Identity -The URL of the hubsite for which to receive the sites refering to it - -```yaml -Type: HubSitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPInPlaceRecordsManagement.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPInPlaceRecordsManagement.md deleted file mode 100644 index 9a803566c3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPInPlaceRecordsManagement.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpinplacerecordsmanagement -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPInPlaceRecordsManagement ---- - -# Get-PnPInPlaceRecordsManagement - -## SYNOPSIS -Returns if the place records management feature is enabled. - -## SYNTAX - -```powershell -Get-PnPInPlaceRecordsManagement [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPInPlaceRecordsManagement -``` - -Returns if $true if in place records management is active - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPIndexedPropertyKeys.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPIndexedPropertyKeys.md deleted file mode 100644 index 2d5c86da9b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPIndexedPropertyKeys.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpindexedpropertykeys -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPIndexedPropertyKeys ---- - -# Get-PnPIndexedPropertyKeys - -## SYNOPSIS -Returns the keys of the property bag values that have been marked for indexing by search - -## SYNTAX - -```powershell -Get-PnPIndexedPropertyKeys [-List <ListPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -List -The list object or name from where to get the indexed properties - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPJavaScriptLink.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPJavaScriptLink.md deleted file mode 100644 index 057b4f8ef5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPJavaScriptLink.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpjavascriptlink -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPJavaScriptLink ---- - -# Get-PnPJavaScriptLink - -## SYNOPSIS -Returns all or a specific custom action(s) with location type ScriptLink - -## SYNTAX - -```powershell -Get-PnPJavaScriptLink [-Name <String>] - [-Scope <CustomActionScope>] - [-ThrowExceptionIfJavaScriptLinkNotFound [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPJavaScriptLink -``` - -Returns all web scoped JavaScript links - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPJavaScriptLink -Scope All -``` - -Returns all web and site scoped JavaScript links - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPJavaScriptLink -Scope Web -``` - -Returns all Web scoped JavaScript links - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPJavaScriptLink -Scope Site -``` - -Returns all Site scoped JavaScript links - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPJavaScriptLink -Name Test -``` - -Returns the web scoped JavaScript link named Test - -## PARAMETERS - -### -Name -Name of the Javascript link. Omit this parameter to retrieve all script links - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Key - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Scope of the action, either Web, Site or All to return both, defaults to Web - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ThrowExceptionIfJavaScriptLinkNotFound -Switch parameter if an exception should be thrown if the requested JavaScriptLink does not exist (true) or if omitted, nothing will be returned in case the JavaScriptLink does not exist - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.UserCustomAction - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPKnowledgeHubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPKnowledgeHubSite.md deleted file mode 100644 index 1afa0127ab..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPKnowledgeHubSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpknowledgehubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPKnowledgeHubSite ---- - -# Get-PnPKnowledgeHubSite - -## SYNOPSIS -Gets the Knowledge Hub Site URL for your tenant - -## SYNTAX - -```powershell -Get-PnPKnowledgeHubSite [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPKnowledgeHubSite -``` - -Returns the Knowledge Hub Site Url for your tenant - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPLabel.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPLabel.md deleted file mode 100644 index 0d68d316e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPLabel.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnplabel -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPLabel ---- - -# Get-PnPLabel - -## SYNOPSIS -Gets the Office 365 retention label/tag of the specified list or library (if applicable) - -## SYNTAX - -```powershell -Get-PnPLabel -List <ListPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPLabel -List "Demo List" -``` - -This gets the Office 365 retention label which is set to a list or a library. - -## PARAMETERS - -### -List -The ID or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPList.md deleted file mode 100644 index 9ebe9efc95..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPList.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnplist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPList ---- - -# Get-PnPList - -## SYNOPSIS -Returns a List object - -## SYNTAX - -### -```powershell -Get-PnPList [-Includes <String[]>] - [-Identity <ListPipeBind>] - [-ThrowExceptionIfListNotFound [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPList -``` - -Returns all lists in the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPList -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -Returns a list with the given id. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPList -Identity Lists/Announcements -``` - -Returns a list with the given url. - -## PARAMETERS - -### -Identity -The ID, name or Url (Lists/MyList) of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -ThrowExceptionIfListNotFound -Switch parameter if an exception should be thrown if the requested list does not exist (true) or if omitted, nothing will be returned in case the list does not exist - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.List - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListInformationRightsManagement.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListInformationRightsManagement.md deleted file mode 100644 index 3eff5e3533..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListInformationRightsManagement.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnplistinformationrightsmanagement -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPListInformationRightsManagement ---- - -# Get-PnPListInformationRightsManagement - -## SYNOPSIS -Get the site closure status of the site which has a site policy applied - -## SYNTAX - -```powershell -Get-PnPListInformationRightsManagement -List <ListPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPListInformationRightsManagement -List "Documents" -``` - -Returns Information Rights Management (IRM) settings for the list. See 'Get-Help Set-PnPListInformationRightsManagement -Detailed' for more information about the various values. - -## PARAMETERS - -### -List - - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListItem.md deleted file mode 100644 index 1e67e60e70..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListItem.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnplistitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPListItem ---- - -# Get-PnPListItem - -## SYNOPSIS -Retrieves list items - -## SYNTAX - -### By Id -```powershell -Get-PnPListItem -List <ListPipeBind> - [-Id <Int>] - [-Fields <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### By Unique Id -```powershell -Get-PnPListItem -List <ListPipeBind> - [-UniqueId <GuidPipeBind>] - [-Fields <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### By Query -```powershell -Get-PnPListItem -List <ListPipeBind> - [-Query <String>] - [-FolderServerRelativeUrl <String>] - [-PageSize <Int>] - [-ScriptBlock <ScriptBlock>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### All Items -```powershell -Get-PnPListItem -List <ListPipeBind> - [-FolderServerRelativeUrl <String>] - [-Fields <String[]>] - [-PageSize <Int>] - [-ScriptBlock <ScriptBlock>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPListItem -List Tasks -``` - -Retrieves all list items from the Tasks list - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPListItem -List Tasks -Id 1 -``` - -Retrieves the list item with ID 1 from the Tasks list - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPListItem -List Tasks -UniqueId bd6c5b3b-d960-4ee7-a02c-85dc6cd78cc3 -``` - -Retrieves the list item with unique id bd6c5b3b-d960-4ee7-a02c-85dc6cd78cc3 from the tasks lists - -### ------------------EXAMPLE 4------------------ -```powershell -(Get-PnPListItem -List Tasks -Fields "Title","GUID").FieldValues -``` - -Retrieves all list items, but only includes the values of the Title and GUID fields in the list item object - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPListItem -List Tasks -Query "<View><Query><Where><Eq><FieldRef Name='GUID'/><Value Type='Guid'>bd6c5b3b-d960-4ee7-a02c-85dc6cd78cc3</Value></Eq></Where></Query></View>" -``` - -Retrieves all list items based on the CAML query specified - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPListItem -List Tasks -PageSize 1000 -``` - -Retrieves all list items from the Tasks list in pages of 1000 items - -### ------------------EXAMPLE 7------------------ -```powershell -Get-PnPListItem -List Tasks -PageSize 1000 -ScriptBlock { Param($items) $items.Context.ExecuteQuery() } | % { $_.BreakRoleInheritance($true, $true) } -``` - -Retrieves all list items from the Tasks list in pages of 1000 items and breaks permission inheritance on each item - -### ------------------EXAMPLE 8------------------ -```powershell -Get-PnPListItem -List Samples -FolderServerRelativeUrl "/sites/contosomarketing/Lists/Samples/Demo" -``` - -Retrieves all list items from the Demo folder in the Samples list located in the contosomarketing site collection - -## PARAMETERS - -### -Fields -The fields to retrieve. If not specified all fields will be loaded in the returned list object. - -```yaml -Type: String[] -Parameter Sets: All Items, By Id, By Unique Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -FolderServerRelativeUrl -The server relative URL of a list folder from which results will be returned. - -```yaml -Type: String -Parameter Sets: By Query, All Items - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Id -The ID of the item to retrieve - -```yaml -Type: Int -Parameter Sets: By Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The list to query - -```yaml -Type: ListPipeBind -Parameter Sets: __AllParameterSets - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -PageSize -The number of items to retrieve per page request. - -```yaml -Type: Int -Parameter Sets: All Items, By Query - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Query -The CAML query to execute against the list - -```yaml -Type: String -Parameter Sets: By Query - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ScriptBlock -The script block to run after every page request. - -```yaml -Type: ScriptBlock -Parameter Sets: All Items, By Query - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UniqueId -The unique id (GUID) of the item to retrieve - -```yaml -Type: GuidPipeBind -Parameter Sets: By Unique Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.ListItem - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListRecordDeclaration.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListRecordDeclaration.md deleted file mode 100644 index 98b8fd5247..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListRecordDeclaration.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnplistrecorddeclaration -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPListRecordDeclaration ---- - -# Get-PnPListRecordDeclaration - -## SYNOPSIS -Returns the manual record declaration settings for a list - -## SYNTAX - -```powershell -Get-PnPListRecordDeclaration -List <ListPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPListRecordDeclaration -List "Documents" -``` - -Returns the record declaration setting for the list "Documents" - -## PARAMETERS - -### -List -The list to retrieve the record declaration settings for - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPManagementApiAccessToken.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPManagementApiAccessToken.md deleted file mode 100644 index a17e9dd9ba..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPManagementApiAccessToken.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpmanagementapiaccesstoken -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPManagementApiAccessToken ---- - -# Get-PnPManagementApiAccessToken - -## SYNOPSIS -Gets an access token for the Office 365 Management API - -## SYNTAX - -```powershell -Get-PnPManagementApiAccessToken -TenantId <String> - -ClientId <String> - -ClientSecret <String> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPManagementApiAccessToken -TenantId $tenantId -ClientId $clientId -ClientSecret $clientSecret) -``` - -Retrieves access token for the Office 365 Management API - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPOnline -AccessToken (Get-PnPManagementApiAccessToken -TenantId $tenantId -ClientId $clientId -ClientSecret $clientSecret) -``` - -Connects to the Office 365 Management API using an access token for the Office 365 Management API - -## PARAMETERS - -### -ClientId -The App\Client ID of the app which gives you access to the Office 365 Management API - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ClientSecret -The Client Secret of the app which gives you access to the Office 365 Management API - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TenantId -The Tenant ID to connect to the Office 365 Management API - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPMasterPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPMasterPage.md deleted file mode 100644 index 5747904eb6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPMasterPage.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpmasterpage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPMasterPage ---- - -# Get-PnPMasterPage - -## SYNOPSIS -Returns the URLs of the default Master Page and the custom Master Page. - -## SYNTAX - -```powershell -Get-PnPMasterPage [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPNavigationNode.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPNavigationNode.md deleted file mode 100644 index b46ffaa7fc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPNavigationNode.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpnavigationnode -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPNavigationNode ---- - -# Get-PnPNavigationNode - -## SYNOPSIS -Returns all or a specific navigation node - -## SYNTAX - -### All nodes by location -```powershell -Get-PnPNavigationNode [-Location <NavigationType>] - [-Tree [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### A single node by ID -```powershell -Get-PnPNavigationNode [-Id <Int>] - [-Tree [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPNavigationNode -``` - -Returns all navigation nodes in the quicklaunch navigation - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPNavigationNode -Location QuickLaunch -``` - -Returns all navigation nodes in the quicklaunch navigation - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPNavigationNode -Location TopNavigationBar -``` - -Returns all navigation nodes in the top navigation bar - -### ------------------EXAMPLE 4------------------ -```powershell -$node = Get-PnPNavigationNode -Id 2030 -PS> $children = $node.Children -``` - -Returns the selected navigation node and retrieves any children - -## PARAMETERS - -### -Id -The Id of the node to retrieve - -```yaml -Type: Int -Parameter Sets: A single node by ID - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Location -The location of the nodes to retrieve. Either TopNavigationBar, QuickLaunch - -```yaml -Type: NavigationType -Parameter Sets: All nodes by location - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Tree -Show a tree view of all navigation nodes - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPOrgAssetsLibrary.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPOrgAssetsLibrary.md deleted file mode 100644 index 7d811dde53..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPOrgAssetsLibrary.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnporgassetslibrary -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPOrgAssetsLibrary ---- - -# Get-PnPOrgAssetsLibrary - -## SYNOPSIS -Returns the list of all the configured organizational asset libraries - -## SYNTAX - -```powershell -Get-PnPOrgAssetsLibrary [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPOrgAssetsLibrary -``` - -Returns the list of all the configured organizational asset sites - -### ------------------EXAMPLE 2------------------ -```powershell -(Get-PnPOrgAssetsLibrary)[0].OrgAssetsLibraries[0].LibraryUrl.DecodedUrl -``` - -Returns the server relative url of the first document library which has been flagged as organizational asset library, i.e. "sites/branding/logos" - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPOrgNewsSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPOrgNewsSite.md deleted file mode 100644 index fe23f8df93..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPOrgNewsSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnporgnewssite -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPOrgNewsSite ---- - -# Get-PnPOrgNewsSite - -## SYNOPSIS -Returns the list of all the configured organizational news sites. - -## SYNTAX - -```powershell -Get-PnPOrgNewsSite [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPOrgNewsSite -``` - -Returns the list of all the configured organizational news sites. - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPowerShellTelemetryEnabled.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPowerShellTelemetryEnabled.md deleted file mode 100644 index f6c3e9bcce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPowerShellTelemetryEnabled.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnppowershelltelemetryenabled -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPPowerShellTelemetryEnabled ---- - -# Get-PnPPowerShellTelemetryEnabled - -## SYNOPSIS -Returns true if the PnP PowerShell Telemetry has been enabled. - -## SYNTAX - -```powershell -Get-PnPPowerShellTelemetryEnabled [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -In order to help to make PnP PowerShell better, we can track anonymous telemetry. We track the version of the cmdlets you are using, which cmdlet you are executing and which version of SharePoint you are connecting to. Use Disable-PnPPowerShellTelemetry to turn this off, alternative, use the -NoTelemetry switch on Connect-PnPOnline to turn it off for that session. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPPowerShellTelemetryEnabled -``` - -Will return true of false. - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProperty.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProperty.md deleted file mode 100644 index 7c9e37224a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProperty.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpproperty -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPProperty ---- - -# Get-PnPProperty - -## SYNOPSIS -Returns a previously not loaded property of a ClientObject - -## SYNTAX - -```powershell -Get-PnPProperty -ClientObject <ClientObject> - -Property <String[]> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Will populate properties of an object and optionally, if needed, load the value from the server. If one property is specified its value will be returned to the output. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell - -$web = Get-PnPWeb -Get-PnPProperty -ClientObject $web -Property Id, Lists -$web.Lists -``` - -Will load both the Id and Lists properties of the specified Web object. - -### ------------------EXAMPLE 2------------------ -```powershell - -$list = Get-PnPList -Identity 'Site Assets' -Get-PnPProperty -ClientObject $list -Property Views -``` - -Will load the views object of the specified list object and return its value to the output. - -## PARAMETERS - -### -ClientObject -Specifies the object where the properties of should be retrieved - -```yaml -Type: ClientObject -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Property -The properties to load. If one property is specified its value will be returned to the output. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.ClientObject - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPropertyBag.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPropertyBag.md deleted file mode 100644 index 93d21d2c3c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPropertyBag.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnppropertybag -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPPropertyBag ---- - -# Get-PnPPropertyBag - -## SYNOPSIS -Returns the property bag values. - -## SYNTAX - -```powershell -Get-PnPPropertyBag [-Key <String>] - [-Folder <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPPropertyBag -``` - -This will return all web property bag values - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPPropertyBag -Key MyKey -``` - -This will return the value of the key MyKey from the web property bag - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPPropertyBag -Folder /MyFolder -``` - -This will return all property bag values for the folder MyFolder which is located in the root of the current web - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPPropertyBag -Folder /MyFolder -Key vti_mykey -``` - -This will return the value of the key vti_mykey from the folder MyFolder which is located in the root of the current web - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPPropertyBag -Folder / -Key vti_mykey -``` - -This will return the value of the key vti_mykey from the root folder of the current web - -## PARAMETERS - -### -Folder -Site relative url of the folder. See examples for use. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Key -Key that should be looked up - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### SharePointPnP.PowerShell.Commands.PropertyBagValue - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningTemplate.md deleted file mode 100644 index c3850a1fd2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningTemplate.md +++ /dev/null @@ -1,535 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPProvisioningTemplate ---- - -# Get-PnPProvisioningTemplate - -## SYNOPSIS -Generates a provisioning site template from a web - -## SYNTAX - -```powershell -Get-PnPProvisioningTemplate [-Out <String>] - [-IncludeAllTermGroups [<SwitchParameter>]] - [-IncludeSiteCollectionTermGroup [<SwitchParameter>]] - [-IncludeSiteGroups [<SwitchParameter>]] - [-IncludeTermGroupsSecurity [<SwitchParameter>]] - [-IncludeSearchConfiguration [<SwitchParameter>]] - [-PersistBrandingFiles [<SwitchParameter>]] - [-PersistPublishingFiles [<SwitchParameter>]] - [-IncludeNativePublishingFiles [<SwitchParameter>]] - [-IncludeHiddenLists [<SwitchParameter>]] - [-IncludeAllClientSidePages [<SwitchParameter>]] - [-SkipVersionCheck [<SwitchParameter>]] - [-PersistMultiLanguageResources [<SwitchParameter>]] - [-ResourceFilePrefix <String>] - [-Handlers <Handlers>] - [-ExcludeHandlers <Handlers>] - [-ExtensibilityHandlers <ExtensibilityHandler[]>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-ContentTypeGroups <String[]>] - [-Force [<SwitchParameter>]] - [-Encoding <Encoding>] - [-TemplateDisplayName <String>] - [-TemplateImagePreviewUrl <String>] - [-TemplateProperties <Hashtable>] - [-OutputInstance [<SwitchParameter>]] - [-ExcludeContentTypesFromSyndication [<SwitchParameter>]] - [-ListsToExtract <String>] - [-Configuration <ExtractConfigurationPipeBind>] - [-Schema <XMLPnPSchemaVersion>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -``` - -Extracts a provisioning template in Office Open XML from the current web. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.xml -``` - -Extracts a provisioning template in XML format from the current web. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -Schema V201503 -``` - -Extracts a provisioning template in Office Open XML from the current web and saves it in the V201503 version of the schema. - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -IncludeAllTermGroups -``` - -Extracts a provisioning template in Office Open XML from the current web and includes all term groups, term sets and terms from the Managed Metadata Service Taxonomy. - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -IncludeSiteCollectionTermGroup -``` - -Extracts a provisioning template in Office Open XML from the current web and includes the term group currently (if set) assigned to the site collection. - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -PersistBrandingFiles -``` - -Extracts a provisioning template in Office Open XML from the current web and saves the files that make up the composed look to the same folder as where the template is saved. - -### ------------------EXAMPLE 7------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -Handlers Lists, SiteSecurity -``` - -Extracts a provisioning template in Office Open XML from the current web, but only processes lists and site security when generating the template. - -### ------------------EXAMPLE 8------------------ -```powershell - -$handler1 = New-PnPExtensibilityHandlerObject -Assembly Contoso.Core.Handlers -Type Contoso.Core.Handlers.MyExtensibilityHandler1 -$handler2 = New-PnPExtensibilityHandlerObject -Assembly Contoso.Core.Handlers -Type Contoso.Core.Handlers.MyExtensibilityHandler2 -Get-PnPProvisioningTemplate -Out NewTemplate.xml -ExtensibilityHandlers $handler1,$handler2 -``` - -This will create two new ExtensibilityHandler objects that are run during extraction of the template - -### ------------------EXAMPLE 9------------------ -Only supported on SP2016, SP2019 and SP Online -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -PersistMultiLanguageResources -``` - -Extracts a provisioning template in Office Open XML from the current web, and for supported artifacts it will create a resource file for each supported language (based upon the language settings of the current web). The generated resource files will be named after the value specified in the Out parameter. For instance if the Out parameter is specified as -Out 'template.xml' the generated resource file will be called 'template.en-US.resx'. - -### ------------------EXAMPLE 10------------------ -Only supported on SP2016, SP2019 and SP Online -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -PersistMultiLanguageResources -ResourceFilePrefix MyResources -``` - -Extracts a provisioning template in Office Open XML from the current web, and for supported artifacts it will create a resource file for each supported language (based upon the language settings of the current web). The generated resource files will be named 'MyResources.en-US.resx' etc. - -### ------------------EXAMPLE 11------------------ -```powershell -$template = Get-PnPProvisioningTemplate -OutputInstance -``` - -Extracts an instance of a provisioning template object from the current web. This syntax cannot be used together with the -Out parameter, but it can be used together with any other supported parameters. - -### ------------------EXAMPLE 12------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -ContentTypeGroups "Group A","Group B" -``` - -Extracts a provisioning template in Office Open XML from the current web, but only processes content types from the to given content type groups. - -### ------------------EXAMPLE 13------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -ExcludeContentTypesFromSyndication -``` - -Extracts a provisioning template in Office Open XML from the current web, excluding content types provisioned through content type syndication (content type hub), in order to prevent provisioning errors if the target also provision the content type using syndication. - -### ------------------EXAMPLE 14------------------ -```powershell -Get-PnPProvisioningTemplate -Out template.pnp -ListsToExtract "Title of List One","95c4efd6-08f4-4c67-94ae-49d696ba1298","Title of List Three" -``` - -Extracts a provisioning template in Office Open XML from the current web, including only the lists specified by title or ID. - -## PARAMETERS - -### -Configuration -Specify a JSON configuration file to configure the extraction progress. - -```yaml -Type: ExtractConfigurationPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ContentTypeGroups -Allows you to specify from which content type group(s) the content types should be included into the template. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Encoding -The encoding type of the XML file, Unicode is default - -```yaml -Type: Encoding -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExcludeContentTypesFromSyndication -Specify whether or not content types issued from a content hub should be exported. By default, these content types are included. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExcludeHandlers -Allows you to run all handlers, excluding the ones specified. - -```yaml -Type: Handlers -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExtensibilityHandlers -Allows you to specify ExtensibilityHandlers to execute while extracting a template. - -```yaml -Type: ExtensibilityHandler[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Handlers -Allows you to only process a specific type of artifact in the site. Notice that this might result in a non-working template, as some of the handlers require other artifacts in place if they are not part of what your extracting. For possible values for this parameter visit https://docs.microsoft.com/dotnet/api/officedevpnp.core.framework.provisioning.model.handlers - -```yaml -Type: Handlers -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeAllClientSidePages -If specified all client side pages will be included - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeAllTermGroups -If specified, all term groups will be included. Overrides IncludeSiteCollectionTermGroup. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeHiddenLists -If specified hidden lists will be included in the template - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeNativePublishingFiles -If specified, out of the box / native publishing files will be saved. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeSearchConfiguration -If specified the template will contain the current search configuration of the site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeSiteCollectionTermGroup -If specified, all the site collection term groups will be included. Overridden by IncludeAllTermGroups. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeSiteGroups -If specified all site groups will be included. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeTermGroupsSecurity -If specified all the managers and contributors of term groups will be included. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ListsToExtract -Specify the lists to extract, either providing their ID or their Title. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -OutputInstance -Returns the template as an in-memory object, which is an instance of the ProvisioningTemplate type of the PnP Core Component. It cannot be used together with the -Out parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PersistBrandingFiles -If specified the files used for masterpages, sitelogo, alternate CSS and the files that make up the composed look will be saved. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PersistMultiLanguageResources -If specified, resource values for applicable artifacts will be persisted to a resource file - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PersistPublishingFiles -If specified the files used for the publishing feature will be saved. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ResourceFilePrefix -If specified, resource files will be saved with the specified prefix instead of using the template name specified. If no template name is specified the files will be called PnP-Resources.<language>.resx. See examples for more info. - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Schema -The schema of the output to use, defaults to the latest schema - -```yaml -Type: XMLPnPSchemaVersion -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -SkipVersionCheck -During extraction the version of the server will be checked for certain actions. If you specify this switch, this check will be skipped. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateDisplayName -It can be used to specify the DisplayName of the template file that will be extracted. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateImagePreviewUrl -It can be used to specify the ImagePreviewUrl of the template file that will be extracted. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateProperties -It can be used to specify custom Properties for the template file that will be extracted. - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while extracting a template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Encoding](https://msdn.microsoft.com/en-us/library/system.text.encoding_properties.aspx) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningTemplateFromGallery.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningTemplateFromGallery.md deleted file mode 100644 index e7f2eecd84..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningTemplateFromGallery.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpprovisioningtemplatefromgallery -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 ---- - -# Get-PnPProvisioningTemplateFromGallery - -## SYNOPSIS -Retrieves or searches provisioning templates from the PnP Template Gallery - -## SYNTAX - -### Identity -```powershell -Get-PnPProvisioningTemplateFromGallery [-Identity <Guid>] - [-Path <String>] - [-Force [<SwitchParameter>]] -``` - -### Search -```powershell -Get-PnPProvisioningTemplateFromGallery [-Search <String>] - [-TargetPlatform <TargetPlatform>] - [-TargetScope <TargetScope>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPProvisioningTemplateFromGallery -``` - -Retrieves all templates from the gallery - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPProvisioningTemplateFromGallery -Search "Data" -``` - -Searches for a templates containing the word 'Data' in the Display Name - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPProvisioningTemplateFromGallery -Identity ae925674-8aa6-438b-acd0-d2699a022edd -``` - -Retrieves a template with the specified ID - -### ------------------EXAMPLE 4------------------ -```powershell -$template = Get-PnPProvisioningTemplateFromGallery -Identity ae925674-8aa6-438b-acd0-d2699a022edd -Apply-PnPProvisioningTemplate -InputInstance $template -``` - -Retrieves a template with the specified ID and applies it to the site. - -### ------------------EXAMPLE 5------------------ -```powershell -$template = Get-PnPProvisioningTemplateFromGallery -Identity ae925674-8aa6-438b-acd0-d2699a022edd -Path c:\temp -``` - -Retrieves a template with the specified ID and saves the template to the specified path - -## PARAMETERS - -### -Force - - -```yaml -Type: SwitchParameter -Parameter Sets: Identity - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity - - -```yaml -Type: Guid -Parameter Sets: Identity - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path - - -```yaml -Type: String -Parameter Sets: Identity - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Search - - -```yaml -Type: String -Parameter Sets: Search - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TargetPlatform - - -```yaml -Type: TargetPlatform -Parameter Sets: Search - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TargetScope - - -```yaml -Type: TargetScope -Parameter Sets: Search - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPublishingImageRendition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPublishingImageRendition.md deleted file mode 100644 index 28064bd458..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPPublishingImageRendition.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnppublishingimagerendition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPPublishingImageRendition ---- - -# Get-PnPPublishingImageRendition - -## SYNOPSIS -Returns all image renditions or if Identity is specified a specific one - -## SYNTAX - -```powershell -Get-PnPPublishingImageRendition [-Identity <ImageRenditionPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPPublishingImageRendition -``` - -Returns all Image Renditions - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPPublishingImageRendition -Identity "Test" -``` - -Returns the image rendition named "Test" - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPPublishingImageRendition -Identity 2 -``` - -Returns the image rendition where its id equals 2 - -## PARAMETERS - -### -Identity -Id or name of an existing image rendition - -```yaml -Type: ImageRenditionPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Publishing.ImageRendition - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRecycleBinItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRecycleBinItem.md deleted file mode 100644 index e0b29c6e5a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRecycleBinItem.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnprecyclebinitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPRecycleBinItem ---- - -# Get-PnPRecycleBinItem - -## SYNOPSIS -Returns the items in the recycle bin from the context - -## SYNTAX - -### Identity -```powershell -Get-PnPRecycleBinItem [-Identity <GuidPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### FirstStage -```powershell -Get-PnPRecycleBinItem [-FirstStage [<SwitchParameter>]] - [-RowLimit <Int>] - [-Connection <SPOnlineConnection>] -``` - -### SecondStage -```powershell -Get-PnPRecycleBinItem [-SecondStage [<SwitchParameter>]] - [-RowLimit <Int>] - [-Connection <SPOnlineConnection>] -``` - -### All -```powershell -Get-PnPRecycleBinItem [-RowLimit <Int>] - [-Connection <SPOnlineConnection>] -``` - -### -```powershell -Get-PnPRecycleBinItem [-Includes <String[]>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPRecycleBinItem -``` - -Returns all items in both the first and the second stage recycle bins in the current site collection - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPRecycleBinItem -Identity f3ef6195-9400-4121-9d1c-c997fb5b86c2 -``` - -Returns all a specific recycle bin item by id - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPRecycleBinItem -FirstStage -``` - -Returns all items in only the first stage recycle bin in the current site collection - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPRecycleBinItem -SecondStage -``` - -Returns all items in only the second stage recycle bin in the current site collection - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPRecycleBinItem -RowLimit 10000 -``` - -Returns items in recycle bin limited by number of results - -## PARAMETERS - -### -FirstStage -Return all items in the first stage recycle bin - -```yaml -Type: SwitchParameter -Parameter Sets: FirstStage - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Returns a recycle bin item with a specific identity - -```yaml -Type: GuidPipeBind -Parameter Sets: Identity - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -RowLimit -Limits return results to specified amount - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: Int -Parameter Sets: FirstStage, SecondStage, All - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SecondStage -Return all items in the second stage recycle bin - -```yaml -Type: SwitchParameter -Parameter Sets: SecondStage - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.RecycleBinItem - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRequestAccessEmails.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRequestAccessEmails.md deleted file mode 100644 index 51ccd28db5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRequestAccessEmails.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnprequestaccessemails -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPRequestAccessEmails ---- - -# Get-PnPRequestAccessEmails - -## SYNOPSIS -Returns the request access e-mail addresses - -## SYNTAX - -```powershell -Get-PnPRequestAccessEmails [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPRequestAccessEmails -``` - -This will return all the request access e-mail addresses for the current web - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<System.String> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRoleDefinition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRoleDefinition.md deleted file mode 100644 index 57012206b2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPRoleDefinition.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnproledefinition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPRoleDefinition ---- - -# Get-PnPRoleDefinition - -## SYNOPSIS -Retrieves a Role Definitions of a site - -## SYNTAX - -```powershell -Get-PnPRoleDefinition [-Identity <RoleDefinitionPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPRoleDefinition -``` - -Retrieves the Role Definitions (Permission Levels) settings of the current site - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPRoleDefinition -Identity Read -``` - -Retrieves the specified Role Definition (Permission Level) settings of the current site - -## PARAMETERS - -### -Identity -The name of a role definition to retrieve. - -```yaml -Type: RoleDefinitionPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.RoleDefinition - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchConfiguration.md deleted file mode 100644 index 4a5ce077ab..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchConfiguration.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsearchconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSearchConfiguration ---- - -# Get-PnPSearchConfiguration - -## SYNOPSIS -Returns the search configuration - -## SYNTAX - -### Xml -```powershell -Get-PnPSearchConfiguration [-Path <String>] - [-Scope <SearchConfigurationScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### OutputFormat -```powershell -Get-PnPSearchConfiguration [-OutputFormat <OutputFormat>] - [-Scope <SearchConfigurationScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSearchConfiguration -``` - -Returns the search configuration for the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSearchConfiguration -Scope Site -``` - -Returns the search configuration for the current site collection - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSearchConfiguration -Scope Subscription -``` - -Returns the search configuration for the current tenant - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPSearchConfiguration -Path searchconfig.xml -Scope Subscription -``` - -Returns the search configuration for the current tenant and saves it to the specified file - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPSearchConfiguration -Scope Site -OutputFormat ManagedPropertyMappings -``` - -Returns all custom managed properties and crawled property mapping at the current site collection - -## PARAMETERS - -### -OutputFormat -Output format for of the configuration. Defaults to complete XML - -```yaml -Type: OutputFormat -Parameter Sets: OutputFormat - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Local path where the search configuration will be saved - -```yaml -Type: String -Parameter Sets: Xml - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scope -Scope to use. Either Web, Site, or Subscription. Defaults to Web - -```yaml -Type: SearchConfigurationScope -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -Does not return a string when the -Path parameter has been specified. - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchCrawlLog.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchCrawlLog.md deleted file mode 100644 index cb45fc54d5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchCrawlLog.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsearchcrawllog -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSearchCrawlLog ---- - -# Get-PnPSearchCrawlLog - -## SYNOPSIS -Returns entries from the SharePoint search crawl log. Make sure you are granted access to the crawl log via the SharePoint search admin center at https://<tenant>-admin.sharepoint.com/_layouts/15/searchadmin/crawllogreadpermission.aspx in order to run this cmdlet. - -## SYNTAX - -```powershell -Get-PnPSearchCrawlLog [-LogLevel <LogLevel>] - [-RowLimit <Int>] - [-Filter <String>] - [-ContentSource <ContentSource>] - [-StartDate <DateTime>] - [-EndDate <DateTime>] - [-RawFormat [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSearchCrawlLog -``` - -Returns the last 100 crawl log entries for site content. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSearchCrawlLog -Filter "https://<tenant>-my.sharepoint.com/personal" -``` - -Returns the last 100 crawl log entries for OneDrive content. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSearchCrawlLog -ContentSource UserProfiles -``` - -Returns the last 100 crawl log entries for user profiles. - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPSearchCrawlLog -ContentSource UserProfiles -Filter "mikael" -``` - -Returns the last 100 crawl log entries for user profiles with the term "mikael" in the user principal name. - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPSearchCrawlLog -ContentSource Sites -LogLevel Error -RowLimit 10 -``` - -Returns the last 10 crawl log entries with a state of Error for site content. - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPSearchCrawlLog -EndDate (Get-Date).AddDays(-100) -``` - -Returns the last 100 crawl log entries up until 100 days ago. - -### ------------------EXAMPLE 7------------------ -```powershell -Get-PnPSearchCrawlLog -RowFilter 3 -RawFormat -``` - -Returns the last 3 crawl log entries showing the raw crawl log data. - -## PARAMETERS - -### -ContentSource -Content to retrieve (Sites, User Profiles). Defaults to Sites. - -```yaml -Type: ContentSource -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EndDate -End date to stop getting entries from. Default to current time. - -```yaml -Type: DateTime -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Filter -Filter to limit what is being returned. Has to be a URL prefix for SharePoint content, and part of a user principal name for user profiles. Wildcard characters are not supported. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LogLevel -Filter what log entries to return (All, Success, Warning, Error). Defaults to All - -```yaml -Type: LogLevel -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RawFormat -Show raw crawl log data - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RowLimit -Number of entries to return. Defaults to 100. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StartDate -Start date to start getting entries from. Defaults to start of time. - -```yaml -Type: DateTime -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchSettings.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchSettings.md deleted file mode 100644 index 78d0e0bb0e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchSettings.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsearchsettings -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSearchSettings ---- - -# Get-PnPSearchSettings - -## SYNOPSIS -Retrieves search settings for a site - -## SYNTAX - -```powershell -Get-PnPSearchSettings [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSearchSettings -``` - -Retrieve search settings for the site - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSite.md deleted file mode 100644 index e2ecab38c4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSite.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSite ---- - -# Get-PnPSite - -## SYNOPSIS -Returns the current site collection from the context. - -## SYNTAX - -### -```powershell -Get-PnPSite [-Includes <String[]>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSite -``` - -Gets the current site - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSite -Includes RootWeb,ServerRelativeUrl -``` - -Gets the current site specifying to include RootWeb and ServerRelativeUrl properties. For the full list of properties see https://docs.microsoft.com/previous-versions/office/sharepoint-server/ee538579(v%3doffice.15) - -## PARAMETERS - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Site - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteClassification.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteClassification.md deleted file mode 100644 index c4bdb3faee..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteClassification.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsiteclassification -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteClassification ---- - -# Get-PnPSiteClassification - -## SYNOPSIS -Returns the defined Site Classifications for the tenant. Requires a connection to the Microsoft Graph. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Get-PnPSiteClassification -``` - -Returns the currently set site classifications for the tenant. - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteClosure.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteClosure.md deleted file mode 100644 index e23a586e66..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteClosure.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsiteclosure -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteClosure ---- - -# Get-PnPSiteClosure - -## SYNOPSIS -Get the site closure status of the site which has a site policy applied - -## SYNTAX - -```powershell -Get-PnPSiteClosure [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteClosure -``` - -Get the site closure status of the site. - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionAdmin.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionAdmin.md deleted file mode 100644 index d6fb0fe877..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionAdmin.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitecollectionadmin -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteCollectionAdmin ---- - -# Get-PnPSiteCollectionAdmin - -## SYNOPSIS -Returns the current site collection administrators of the site collection in the current context - -## SYNTAX - -```powershell -Get-PnPSiteCollectionAdmin [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command will return all current site collection administrators of the site collection in the current context - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteCollectionAdmin -``` - -This will return all the current site collection administrators of the site collection in the current context - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionTermStore.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionTermStore.md deleted file mode 100644 index e384a4ee8a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteCollectionTermStore.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitecollectiontermstore -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteCollectionTermStore ---- - -# Get-PnPSiteCollectionTermStore - -## SYNOPSIS -Returns the site collection term store - -## SYNTAX - -```powershell -Get-PnPSiteCollectionTermStore [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteCollectionTermStore -``` - -Returns the site collection term store. - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.TermStore - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesign.md deleted file mode 100644 index 2dcff159ca..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesign.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitedesign -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteDesign ---- - -# Get-PnPSiteDesign - -## SYNOPSIS -Retrieve Site Designs that have been registered on the current tenant. - -## SYNTAX - -```powershell -Get-PnPSiteDesign [-Identity <TenantSiteDesignPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteDesign -``` - -Returns all registered site designs - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteDesign -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -``` - -Returns a specific registered site designs - -## PARAMETERS - -### -Identity -If specified will retrieve the specified site design - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRights.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRights.md deleted file mode 100644 index bc302cdba3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRights.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitedesignrights -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteDesignRights ---- - -# Get-PnPSiteDesignRights - -## SYNOPSIS -Returns the principals with design rights on a specific Site Design - -## SYNTAX - -```powershell -Get-PnPSiteDesignRights -Identity <TenantSiteDesignPipeBind> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteDesignRights -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -``` - -Returns the principals with rights on a specific site design - -## PARAMETERS - -### -Identity -The ID of the Site Design to receive the rights for - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRun.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRun.md deleted file mode 100644 index 580c6defc4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRun.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitedesignrun -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteDesignRun ---- - -# Get-PnPSiteDesignRun - -## SYNOPSIS -Retrieves a list of site designs applied to a specified site collection. If the WebUrl parameter is not specified we show the list of designs applied to the current site. The returned output includes the ID of the scheduled job, the web and site IDs, and the site design ID, version, and title. - -## SYNTAX - -```powershell -Get-PnPSiteDesignRun [-SiteDesignId <GuidPipeBind>] - [-WebUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteDesignRun -``` - -This example returns a list of the site designs applied to the current site. Providing a specific site design ID will return the details for just that applied site design. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteDesignRun -WebUrl https://mytenant.sharepoint.com/sites/project -``` - -This example returns a list of the site designs applied to the specified site. Providing a specific site design ID will return the details for just that applied site design. - -## PARAMETERS - -### -SiteDesignId -The ID of the site design to apply. - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -WebUrl -The URL of the site collection where the site design will be applied. If not specified the design will be applied to the site you connected to with Connect-PnPOnline. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRunStatus.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRunStatus.md deleted file mode 100644 index b997837038..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignRunStatus.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitedesignrunstatus -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteDesignRunStatus ---- - -# Get-PnPSiteDesignRunStatus - -## SYNOPSIS -Retrieves and displays a list of all site script actions executed for a specified site design applied to a site. - -## SYNTAX - -```powershell -Get-PnPSiteDesignRunStatus -Run <TenantSiteDesignRun> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$myrun = Get-PnPSiteDesignRun -WebUrl "https://contoso.sharepoint.com/sites/project-playbook" -SiteDesignId cefd782e-sean-4814-a68a-b33b116c302f -Get-PnPSiteDesignRunStatus -Run $myrun -``` - -This example gets the run for a specific site design applied to a site and sets it to a variable. This variable is then passed into the command -Run parameter. The result is a display of all the site script actions applied for that site design run, including the script action title and outcome. - -## PARAMETERS - -### -Run -The site design run for the desired set of script action details. - -```yaml -Type: TenantSiteDesignRun -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignTask.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignTask.md deleted file mode 100644 index dfb97cfdef..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteDesignTask.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitedesigntask -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteDesignTask ---- - -# Get-PnPSiteDesignTask - -## SYNOPSIS -Used to retrieve a scheduled site design script. It takes the ID of the scheduled site design task and the URL for the site where the site design is scheduled to be applied. - -## SYNTAX - -```powershell -Get-PnPSiteDesignTask [-Identity <TenantSiteDesignTaskPipeBind>] - [-WebUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteDesignTask -Identity 501z8c32-4147-44d4-8607-26c2f67cae82 -``` - -This example retrieves a site design task given the provided site design task id - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteDesignTask -``` - -This example retrieves all site design tasks currently scheduled on the current site - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSiteDesignTask -WebUrl "https://contoso.sharepoint.com/sites/project" -``` - -This example retrieves all site design tasks currently scheduled on the provided site - -## PARAMETERS - -### -Identity -The ID of the site design task to retrieve. - -```yaml -Type: TenantSiteDesignTaskPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -WebUrl -The URL of the site collection where the site design will be applied. If not specified the site design tasks will be returned for the site you connected to with Connect-PnPOnline. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSitePolicy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSitePolicy.md deleted file mode 100644 index 01eb4468fb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSitePolicy.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitepolicy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSitePolicy ---- - -# Get-PnPSitePolicy - -## SYNOPSIS -Retrieves all or a specific site policy - -## SYNTAX - -```powershell -Get-PnPSitePolicy [-AllAvailable [<SwitchParameter>]] - [-Name <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSitePolicy -``` - -Retrieves the current applied site policy. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSitePolicy -AllAvailable -``` - -Retrieves all available site policies. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSitePolicy -Name "Contoso HBI" -``` - -Retrieves an available site policy with the name "Contoso HBI". - -## PARAMETERS - -### -AllAvailable -Retrieve all available site policies - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -Retrieves a site policy with a specific name - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.Entities.SitePolicyEntity - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScript.md deleted file mode 100644 index 8c5a47823c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScript.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitescript -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteScript ---- - -# Get-PnPSiteScript - -## SYNOPSIS -Retrieve Site Scripts that have been registered on the current tenant. - -## SYNTAX - -```powershell -Get-PnPSiteScript [-Identity <TenantSiteScriptPipeBind>] - [-SiteDesign <TenantSiteDesignPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteScript -``` - -Returns all registered site scripts - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteScript -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -``` - -Returns a specific registered site script - -## PARAMETERS - -### -Identity -If specified will retrieve the specified site script - -```yaml -Type: TenantSiteScriptPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -SiteDesign -If specified will retrieve the site scripts for this design - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromList.md deleted file mode 100644 index 24543777e9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromList.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitescriptfromlist -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteScriptFromList ---- - -# Get-PnPSiteScriptFromList - -## SYNOPSIS -Generates a Site Script from an existing list - -## SYNTAX - -```powershell -Get-PnPSiteScriptFromList -Url <String> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows a Site Script to be generated off of an existing list on your tenant. Connect to your SharePoint Online Admin site before executing this command. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteScriptFromList -Url https://contoso.sharepoint.com/sites/teamsite/lists/MyList -``` - -Returns the generated Site Script JSON from the list "MyList" at the provided Url - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteScriptFromList -Url "https://contoso.sharepoint.com/sites/teamsite/Shared%20Documents" -``` - -Returns the generated Site Script JSON from the default document library at the provided Url - -## PARAMETERS - -### -Url -Specifies the URL of the list to generate a Site Script from - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromWeb.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromWeb.md deleted file mode 100644 index 28c631f404..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteScriptFromWeb.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitescriptfromweb -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteScriptFromWeb ---- - -# Get-PnPSiteScriptFromWeb - -## SYNOPSIS -Generates a Site Script from an existing site - -## SYNTAX - -### All components -```powershell -Get-PnPSiteScriptFromWeb -Url <String> - [-IncludeAll [<SwitchParameter>]] - [-Lists <String[]>] - [-Connection <SPOnlineConnection>] -``` - -### Specific components -```powershell -Get-PnPSiteScriptFromWeb -Url <String> - [-IncludeBranding [<SwitchParameter>]] - [-IncludeLinksToExportedItems [<SwitchParameter>]] - [-IncludeRegionalSettings [<SwitchParameter>]] - [-IncludeSiteExternalSharingCapability [<SwitchParameter>]] - [-IncludeTheme [<SwitchParameter>]] - [-Lists <String[]>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows a Site Script to be generated off of an existing site on your tenant. Connect to your SharePoint Online Admin site before executing this command. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteScriptFromWeb -Url https://contoso.sharepoint.com/sites/teamsite -IncludeAll -``` - -Returns the generated Site Script JSON containing all supported components from the site at the provided Url - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteScriptFromWeb -Url https://contoso.sharepoint.com/sites/teamsite -IncludeAll -Lists "Shared Documents","Lists\MyList" -``` - -Returns the generated Site Script JSON containing all supported components from the site at the provided Url including the lists "Shared Documents" and "MyList" - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSiteScriptFromWeb -Url https://contoso.sharepoint.com/sites/teamsite -IncludeBranding -IncludeLinksToExportedItems -``` - -Returns the generated Site Script JSON containing the branding and navigation links from the site at the provided Url - -## PARAMETERS - -### -IncludeAll -If specified will include all supported components into the Site Script - -```yaml -Type: SwitchParameter -Parameter Sets: All components - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeBranding -If specified will include the branding of the site into the Site Script - -```yaml -Type: SwitchParameter -Parameter Sets: Specific components - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeLinksToExportedItems -If specified will include navigation links into the Site Script - -```yaml -Type: SwitchParameter -Parameter Sets: Specific components - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeRegionalSettings -If specified will include the regional settings into the Site Script - -```yaml -Type: SwitchParameter -Parameter Sets: Specific components - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeSiteExternalSharingCapability -If specified will include the external sharing configuration into the Site Script - -```yaml -Type: SwitchParameter -Parameter Sets: Specific components - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeTheme -If specified will include the branding of the site into the Site Script - -```yaml -Type: SwitchParameter -Parameter Sets: Specific components - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lists -Allows specifying one or more site relative URLs of lists that should be included into the Site Script, i.e. "Shared Documents","List\MyList" - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -Specifies the URL of the site to generate a Site Script from - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteSearchQueryResults.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteSearchQueryResults.md deleted file mode 100644 index dbe0536143..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSiteSearchQueryResults.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsitesearchqueryresults -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSiteSearchQueryResults ---- - -# Get-PnPSiteSearchQueryResults - -## SYNOPSIS -Executes a search query to retrieve indexed site collections - -## SYNTAX - -### Limit -```powershell -Get-PnPSiteSearchQueryResults [-StartRow <Int>] - [-MaxResults <Int>] - [-Query <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### All -```powershell -Get-PnPSiteSearchQueryResults [-All [<SwitchParameter>]] - [-Query <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSiteSearchQueryResults -``` - -Returns the top 500 site collections indexed by SharePoint Search - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteSearchQueryResults -Query "WebTemplate:STS" -``` - -Returns the top 500 site collections indexed by SharePoint Search which have are based on the STS (Team Site) template - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSiteSearchQueryResults -Query "WebTemplate:SPSPERS" -``` - -Returns the top 500 site collections indexed by SharePoint Search which have are based on the SPSPERS (MySite) template, up to the MaxResult limit - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPSiteSearchQueryResults -Query "Title:Intranet*" -``` - -Returns the top 500 site collections indexed by SharePoint Search of which the title starts with the word Intranet - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPSiteSearchQueryResults -MaxResults 10 -``` - -Returns the top 10 site collections indexed by SharePoint Search - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPSiteSearchQueryResults -All -``` - -Returns absolutely all site collections indexed by SharePoint Search - -## PARAMETERS - -### -All -Automatically page results until the end to get more than 500 sites. Use with caution! - -```yaml -Type: SwitchParameter -Parameter Sets: All - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MaxResults -Maximum amount of search results to return. Default and max is 500 search results. - -```yaml -Type: Int -Parameter Sets: Limit - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Query -Search query in Keyword Query Language (KQL) to execute to refine the returned sites. If omitted, all indexed sites will be returned. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -StartRow -Search result item to start returning the results from. Useful for paging. Leave at 0 to return all results. - -```yaml -Type: Int -Parameter Sets: Limit - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<System.Object> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPStorageEntity.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPStorageEntity.md deleted file mode 100644 index 36587abb9d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPStorageEntity.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpstorageentity -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPStorageEntity ---- - -# Get-PnPStorageEntity - -## SYNOPSIS -Retrieve Storage Entities / Farm Properties from either the Tenant App Catalog or from the current site if it has a site scope app catalog. - -## SYNTAX - -```powershell -Get-PnPStorageEntity [-Key <String>] - [-Scope <StorageEntityScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPStorageEntity -``` - -Returns all site storage entities/farm properties - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPStorageEntity -Key MyKey -``` - -Returns the storage entity/farm property with the given key. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPStorageEntity -Scope Site -``` - -Returns all site collection scoped storage entities - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPStorageEntity -Key MyKey -Scope Site -``` - -Returns the storage entity from the site collection with the given key - -## PARAMETERS - -### -Key -The key of the value to retrieve. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scope -Defines the scope of the storage entity. Defaults to Tenant. - -```yaml -Type: StorageEntityScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPStoredCredential.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPStoredCredential.md deleted file mode 100644 index f9fd583e21..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPStoredCredential.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpstoredcredential -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPStoredCredential ---- - -# Get-PnPStoredCredential - -## SYNOPSIS -Get a credential - -## SYNTAX - -```powershell -Get-PnPStoredCredential -Name <String> - [-Type <CredentialType>] -``` - -## DESCRIPTION -Returns a stored credential from the Windows Credential Manager - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPStoredCredential -Name O365 -``` - -Returns the credential associated with the specified identifier - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPStoredCredential -Name testEnvironment -Type OnPrem -``` - -Gets the credential associated with the specified identifier from the credential manager and then will return a credential that can be used for on-premises authentication - -## PARAMETERS - -### -Name -The credential to retrieve. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Type -The object type of the credential to return from the Credential Manager. Possible values are 'O365', 'OnPrem' or 'PSCredential' - -```yaml -Type: CredentialType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSubWebs.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSubWebs.md deleted file mode 100644 index 1f8ea04060..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSubWebs.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpsubwebs -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPSubWebs ---- - -# Get-PnPSubWebs - -## SYNOPSIS -Returns the subwebs of the current web - -## SYNTAX - -### -```powershell -Get-PnPSubWebs [-Includes <String[]>] - [-Identity <WebPipeBind>] - [-Recurse [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPSubWebs -``` - -Retrieves all subsites of the current context returning the Id, Url, Title and ServerRelativeUrl of each subsite in the output - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSubWebs -Recurse -``` - -Retrieves all subsites of the current context and all of their nested child subsites returning the Id, Url, Title and ServerRelativeUrl of each subsite in the output - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSubWebs -Recurse -Includes "WebTemplate","Description" | Select ServerRelativeUrl, WebTemplate, Description -``` - -Retrieves all subsites of the current context and shows the ServerRelativeUrl, WebTemplate and Description properties in the resulting output - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPSubWebs -Identity Team1 -Recurse -``` - -Retrieves all subsites of the subsite Team1 and all of its nested child subsites returning the Id, Url, Title and ServerRelativeUrl of each subsite in the output - -## PARAMETERS - -### -Identity -If provided, only the subsite with the provided Id, GUID or the Web instance will be returned - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Recurse -If provided, recursion through all subsites and their children will take place to return them as well - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Web - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomyItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomyItem.md deleted file mode 100644 index f5e59351a6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomyItem.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptaxonomyitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTaxonomyItem ---- - -# Get-PnPTaxonomyItem - -## SYNOPSIS -Returns a taxonomy item - -## SYNTAX - -```powershell -Get-PnPTaxonomyItem -TermPath <String> - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -TermPath -The path, delimited by | of the taxonomy item to retrieve, alike GROUPLABEL|TERMSETLABEL|TERMLABEL - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Term - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.TaxonomyItem - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomySession.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomySession.md deleted file mode 100644 index 0926d15c90..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTaxonomySession.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptaxonomysession -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTaxonomySession ---- - -# Get-PnPTaxonomySession - -## SYNOPSIS -Returns a taxonomy session - -## SYNTAX - -```powershell -Get-PnPTaxonomySession [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.TaxonomySession - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenant.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenant.md deleted file mode 100644 index f70e6928b5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenant.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenant -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenant ---- - -# Get-PnPTenant - -## SYNOPSIS -Returns organization-level site collection properties - -## SYNTAX - -```powershell -Get-PnPTenant [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns organization-level site collection properties such as StorageQuota, StorageQuotaAllocated, ResourceQuota, -ResourceQuotaAllocated, and SiteCreationMode. - -Currently, there are no parameters for this cmdlet. - -You must have the SharePoint Online admin or Global admin role to run the cmdlet. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenant -``` - -This example returns all tenant settings - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantAppCatalogUrl.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantAppCatalogUrl.md deleted file mode 100644 index cbac01bd97..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantAppCatalogUrl.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantappcatalogurl -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantAppCatalogUrl ---- - -# Get-PnPTenantAppCatalogUrl - -## SYNOPSIS -Retrieves the url of the tenant scoped app catalog - -## SYNTAX - -```powershell -Get-PnPTenantAppCatalogUrl [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantAppCatalogUrl -``` - -Returns the url of the tenant scoped app catalog site collection - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnEnabled.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnEnabled.md deleted file mode 100644 index fb42e1dff7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnEnabled.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantcdnenabled -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantCdnEnabled ---- - -# Get-PnPTenantCdnEnabled - -## SYNOPSIS -Retrieves if the Office 365 Content Delivery Network has been enabled. - -## SYNTAX - -```powershell -Get-PnPTenantCdnEnabled -CdnType <SPOTenantCdnType> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Enables or disabled the public or private Office 365 Content Delivery Network (CDN). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantCdnEnabled -CdnType Public -``` - -Returns the enabled status of the specified CDN - -## PARAMETERS - -### -CdnType -The type of cdn to retrieve the origins from - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnOrigin.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnOrigin.md deleted file mode 100644 index 33fe78572e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnOrigin.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantcdnorigin -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantCdnOrigin ---- - -# Get-PnPTenantCdnOrigin - -## SYNOPSIS -Returns the current registered origins from the public or private content delivery network (CDN). - -## SYNTAX - -```powershell -Get-PnPTenantCdnOrigin -CdnType <SPOTenantCdnType> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns the current registered origins from the public or private content delivery network (CDN). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantCdnOrigin -CdnType Public -``` - -Returns the configured CDN origins for the specified CDN type - -## PARAMETERS - -### -CdnType -The type of cdn to retrieve the origins from - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnPolicies.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnPolicies.md deleted file mode 100644 index 9d7e6b2431..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantCdnPolicies.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantcdnpolicies -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantCdnPolicies ---- - -# Get-PnPTenantCdnPolicies - -## SYNOPSIS -Returns the CDN Policies for the specified CDN (Public | Private). - -## SYNTAX - -```powershell -Get-PnPTenantCdnPolicies -CdnType <SPOTenantCdnType> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Enables or disabled the public or private Office 365 Content Delivery Network (CDN). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantCdnPolicies -CdnType Public -``` - -Returns the policies for the specified CDN type - -## PARAMETERS - -### -CdnType -The type of cdn to retrieve the policies from - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantId.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantId.md deleted file mode 100644 index cf8f16886e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantId.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantid -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantId ---- - -# Get-PnPTenantId - -## SYNOPSIS -Returns the Tenant ID - -## SYNTAX - -```powershell -Get-PnPTenantId [-TenantUrl <String>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantId -``` - -Returns the current Tenant Id. A valid connection with Connect-PnPOnline is required. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTenantId -TenantUrl https://contoso.sharepoint.com -``` - -Returns the Tenant ID for the specified tenant. Can be executed without a connecting first with Connect-PnPOnline - -## PARAMETERS - -### -TenantUrl - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantRecycleBinItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantRecycleBinItem.md deleted file mode 100644 index df4e8afbc4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantRecycleBinItem.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantrecyclebinitem -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantRecycleBinItem ---- - -# Get-PnPTenantRecycleBinItem - -## SYNOPSIS -Returns all modern and classic site collections in the tenant scoped recycle bin - -## SYNTAX - -```powershell -Get-PnPTenantRecycleBinItem [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command will return all the items in the tenant recycle bin for the Office 365 tenant you are connected to. Be sure to connect to the SharePoint Online Admin endpoint (https://yourtenantname-admin.sharepoint.com) in order for this command to work. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantRecycleBinItem -``` - -Returns all modern and classic site collections in the tenant scoped recycle bin - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.Online.SharePoint.TenantAdministration.DeletedSiteProperties - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequence.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequence.md deleted file mode 100644 index a2022517f8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequence.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantsequence -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantSequence ---- - -# Get-PnPTenantSequence - -## SYNOPSIS -Returns one ore more provisioning sequence object(s) from a tenant template - -## SYNTAX - -```powershell -Get-PnPTenantSequence -Template <ProvisioningHierarchy> - [-Identity <ProvisioningSequencePipeBind>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantSequence -Template $myTemplateObject -``` - -Returns all sequences from the specified tenant template - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTenantSequence -Template $myTemplateObject -Identity "mysequence" -``` - -Returns the specified sequence from the specified tenant template - -## PARAMETERS - -### -Identity -Optional Id of the sequence - -Only applicable to: SharePoint Online - -```yaml -Type: ProvisioningSequencePipeBind -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Template -The template to retrieve the sequence from - -Only applicable to: SharePoint Online - -```yaml -Type: ProvisioningHierarchy -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequenceSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequenceSite.md deleted file mode 100644 index 431cc48349..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSequenceSite.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantsequencesite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantSequenceSite ---- - -# Get-PnPTenantSequenceSite - -## SYNOPSIS -Returns one ore more sites from a tenant template - -## SYNTAX - -```powershell -Get-PnPTenantSequenceSite -Sequence <ProvisioningSequence> - [-Identity <ProvisioningSitePipeBind>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantSequenceSite -Sequence $mysequence -``` - -Returns all sites from the specified sequence - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTenantSequenceSite -Sequence $mysequence -Identity 8058ea99-af7b-4bb7-b12a-78f93398041e -``` - -Returns the specified site from the specified sequence - -## PARAMETERS - -### -Identity -Optional Id of the site - -Only applicable to: SharePoint Online - -```yaml -Type: ProvisioningSitePipeBind -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Sequence -The sequence to retrieve the site from - -Only applicable to: SharePoint Online - -```yaml -Type: ProvisioningSequence -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipal.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipal.md deleted file mode 100644 index 63add9c48b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipal.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantserviceprincipal -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantServicePrincipal ---- - -# Get-PnPTenantServicePrincipal - -## SYNOPSIS -Returns the current tenant's "SharePoint Online Client" service principal. - -## SYNTAX - -```powershell -Get-PnPTenantServicePrincipal [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns the current tenant's "SharePoint Online Client" service principal. - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionGrants.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionGrants.md deleted file mode 100644 index 83cab82302..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionGrants.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantserviceprincipalpermissiongrants -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantServicePrincipalPermissionGrants ---- - -# Get-PnPTenantServicePrincipalPermissionGrants - -## SYNOPSIS -Gets the collection of permission grants for the "SharePoint Online Client" service principal - -## SYNTAX - -```powershell -Get-PnPTenantServicePrincipalPermissionGrants [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Gets the collection of permission grants for the "SharePoint Online Client" service principal. - -A permission grant contains the following properties: - -* ClientId: The objectId of the service principal granted consent to impersonate the user when accessing the resource(represented by the resourceId). -* ConsentType: Whether consent was provided by the administrator on behalf of the organization or whether consent was provided by an individual.The possible values are "AllPrincipals" or "Principal". -* ObjectId: The unique identifier for the permission grant. -* Resource: The resource to which access has been granted (Coming soon) -* ResourceId: The objectId of the resource service principal to which access has been granted. -* Scope: The value of the scope claim that the resource application should expect in the OAuth 2.0 access token. - - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionRequests.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionRequests.md deleted file mode 100644 index 4046996abf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantServicePrincipalPermissionRequests.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantserviceprincipalpermissionrequests -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantServicePrincipalPermissionRequests ---- - -# Get-PnPTenantServicePrincipalPermissionRequests - -## SYNOPSIS -Gets the collection of permission requests for the "SharePoint Online Client" service principal - -## SYNTAX - -```powershell -Get-PnPTenantServicePrincipalPermissionRequests [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Gets the collection of permission requests for the "SharePoint Online Client" service principal. - -Permission request object - -A permission request contains the following properties: - -* Id: The identifier of the request. -* Resource: The resource that the application requires access to. -* Scope: The value of the scope claim that the resource application should expect in the OAuth 2.0 access token. - - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSite.md deleted file mode 100644 index 511134ccf6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantSite.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenantsite -applicable: SharePoint Online, SharePoint 2016, SharePoint 2019 -schema: 2.0.0 -title: Get-PnPTenantSite ---- - -# Get-PnPTenantSite - -## SYNOPSIS -Retrieve site information. - -## SYNTAX - -```powershell -Get-PnPTenantSite [-Url <String>] - [-Template <String>] - [-Detailed [<SwitchParameter>]] - [-IncludeOneDriveSites [<SwitchParameter>]] - [-Filter <String>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Use this cmdlet to retrieve site information from your tenant administration. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantSite -``` - -Returns all site collections - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTenantSite -Url http://tenant.sharepoint.com/sites/projects -``` - -Returns information about the project site - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPTenantSite -Detailed -``` - -Returns all sites with the full details of these sites - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPTenantSite -IncludeOneDriveSites -``` - -Returns all sites including all OneDrive for Business sites - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPTenantSite -IncludeOneDriveSites -Filter "Url -like '-my.sharepoint.com/personal/'" -``` - -Returns all OneDrive for Business sites - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPTenantSite -Template SITEPAGEPUBLISHING#0 -``` - -Returns all Communication sites - -### ------------------EXAMPLE 7------------------ -```powershell -Get-PnPTenantSite -Filter "Url -like 'sales'" -``` - -Returns all sites including 'sales' in the url - -## PARAMETERS - -### -Detailed -By default, not all returned attributes are populated. This switch populates all attributes. It can take several seconds to run. Without this, some attributes will show default values that may not be correct. - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Filter -Specifies the script block of the server-side filter to apply. See https://technet.microsoft.com/en-us/library/fp161380.aspx - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeOneDriveSites -By default, the OneDrives are not returned. This switch includes all OneDrives. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Template -By default, all sites will be returned. Specify a template value alike "STS#0" here to filter on the template - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -The URL of the site - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Identity - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.Online.SharePoint.TenantAdministration.SiteProperties - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantTemplate.md deleted file mode 100644 index a78fc2cdb3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantTemplate.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenanttemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantTemplate ---- - -# Get-PnPTenantTemplate - -## SYNOPSIS -Generates a provisioning tenant template from a site. If the site is a hubsite any connected site will be included. - -## SYNTAX - -### Extract a template to a file -```powershell -Get-PnPTenantTemplate -Out <String> - [-SiteUrl <String>] - [-Force [<SwitchParameter>]] - [-Configuration <ExtractConfigurationPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Extract a template as an object -```powershell -Get-PnPTenantTemplate -AsInstance [<SwitchParameter>] - [-SiteUrl <String>] - [-Configuration <ExtractConfigurationPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantTemplate -Out tenanttemplate.xml -``` - -Extracts a tenant template - -## PARAMETERS - -### -AsInstance -Returns the template as an in-memory object, which is an instance of the ProvisioningHierarchy type of the PnP Core Component. It cannot be used together with the -Out parameter. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Extract a template as an object - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Configuration -Specify a JSON configuration file to configure the extraction progress. - -Only applicable to: SharePoint Online - -```yaml -Type: ExtractConfigurationPipeBind -Parameter Sets: Extract a template to a file, Extract a template as an object - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Extract a template to a file - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Extract a template to a file - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -SiteUrl - - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Extract a template to a file, Extract a template as an object - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantTheme.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantTheme.md deleted file mode 100644 index bf73780550..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTenantTheme.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptenanttheme -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPTenantTheme ---- - -# Get-PnPTenantTheme - -## SYNOPSIS -Returns all or a specific theme - -## SYNTAX - -```powershell -Get-PnPTenantTheme [-Name <String>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns all or a specific tenant theme. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTenantTheme -``` - -Returns all themes - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTenantTheme -Name "MyCompanyTheme" -``` - -Returns the specified theme - -## PARAMETERS - -### -Name -The name of the theme to retrieve - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTerm.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTerm.md deleted file mode 100644 index 1ab768ac7f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTerm.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpterm -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTerm ---- - -# Get-PnPTerm - -## SYNOPSIS -Returns a taxonomy term - -## SYNTAX - -### -```powershell -Get-PnPTerm [-Includes <String[]>] - [-IncludeChildTerms [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### By Term Id -```powershell -Get-PnPTerm -Identity <Id, Name or Object> - [-TermStore <Id, Name or Object>] - [-IncludeChildTerms [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### By Termset -```powershell -Get-PnPTerm -TermSet <Id, Title or TaxonomyItem> - -TermGroup <Id, Title or TermGroup> - [-Identity <Id, Name or Object>] - [-TermStore <Id, Name or Object>] - [-Recursive [<SwitchParameter>]] - [-IncludeChildTerms [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTerm -TermSet "Departments" -TermGroup "Corporate" -``` - -Returns all term in the termset "Departments" which is in the group "Corporate" from the site collection termstore - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTerm -Identity "Finance" -TermSet "Departments" -TermGroup "Corporate" -``` - -Returns the term named "Finance" in the termset "Departments" from the termgroup called "Corporate" from the site collection termstore - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPTerm -Identity ab2af486-e097-4b4a-9444-527b251f1f8d -TermSet "Departments" -TermGroup "Corporate" -``` - -Returns the term named with the given id, from the "Departments" termset in a term group called "Corporate" from the site collection termstore - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPTerm -Identity "Small Finance" -TermSet "Departments" -TermGroup "Corporate" -Recursive -``` - -Returns the term named "Small Finance", from the "Departments" termset in a term group called "Corporate" from the site collection termstore even if it's a subterm below "Finance" - -### ------------------EXAMPLE 5------------------ -```powershell -$term = Get-PnPTerm -Identity "Small Finance" -TermSet "Departments" -TermGroup "Corporate" -Include Labels -$term.Labels -``` - -Returns all the localized labels for the term named "Small Finance", from the "Departments" termset in a term group called "Corporate" - -## PARAMETERS - -### -Identity -The Id or Name of a Term - -```yaml -Type: Id, Name or Object -Parameter Sets: By Term Id, By Termset - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -IncludeChildTerms -Includes the hierarchy of child terms if available - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Recursive -Find the first term recursively matching the label in a term hierarchy. - -```yaml -Type: SwitchParameter -Parameter Sets: By Termset - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermGroup -Name of the termgroup to check. - -```yaml -Type: Id, Title or TermGroup -Parameter Sets: By Termset - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TermSet -Name of the termset to check. - -```yaml -Type: Id, Title or TaxonomyItem -Parameter Sets: By Termset - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TermStore -Term store to check; if not specified the default term store is used. - -```yaml -Type: Id, Name or Object -Parameter Sets: By Term Id, By Termset - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.Term - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTermGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTermGroup.md deleted file mode 100644 index 6383530c16..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTermGroup.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptermgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTermGroup ---- - -# Get-PnPTermGroup - -## SYNOPSIS -Returns a taxonomy term group - -## SYNTAX - -### -```powershell -Get-PnPTermGroup [-Includes <String[]>] - [-Identity <Id, Title or TaxonomyItem>] - [-TermStore <Id, Name or Object>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTermGroup -``` - -Returns all Term Groups in the site collection termstore - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTermGroup -Identity "Departments" -``` - -Returns the termgroup named "Departments" from the site collection termstore - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPTermGroup -Identity ab2af486-e097-4b4a-9444-527b251f1f8d -``` - -Returns the termgroup with the given ID from the site collection termstore - -## PARAMETERS - -### -Identity -Name of the taxonomy term group to retrieve. - -```yaml -Type: Id, Title or TaxonomyItem -Parameter Sets: (All) -Aliases: GroupName - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -TermStore -Term store to check; if not specified the default term store is used. - -```yaml -Type: Id, Name or Object -Parameter Sets: (All) -Aliases: TermStoreName - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.TermGroup - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTermSet.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTermSet.md deleted file mode 100644 index e9258829dc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTermSet.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptermset -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTermSet ---- - -# Get-PnPTermSet - -## SYNOPSIS -Returns a taxonomy term set - -## SYNTAX - -### -```powershell -Get-PnPTermSet -TermGroup <Id, Title or TermGroup> - [-Includes <String[]>] - [-Identity <Id, Name or Object>] - [-TermStore <Id, Name or Object>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTermSet -TermGroup "Corporate" -``` - -Returns all termsets in the group "Corporate" from the site collection termstore - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTermSet -Identity "Departments" -TermGroup "Corporate" -``` - -Returns the termset named "Departments" from the termgroup called "Corporate" from the site collection termstore - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPTermSet -Identity ab2af486-e097-4b4a-9444-527b251f1f8d -TermGroup "Corporate -``` - -Returns the termset with the given id from the termgroup called "Corporate" from the site collection termstore - -## PARAMETERS - -### -Identity -The Id or Name of a termset - -```yaml -Type: Id, Name or Object -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -TermGroup -Name of the term group to check. - -```yaml -Type: Id, Title or TermGroup -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TermStore -Term store to check; if not specified the default term store is used. - -```yaml -Type: Id, Name or Object -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.TermSet - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTheme.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTheme.md deleted file mode 100644 index 5eaa2ff218..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTheme.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptheme -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTheme ---- - -# Get-PnPTheme - -## SYNOPSIS -Returns the current theme/composed look of the current web. - -## SYNTAX - -```powershell -Get-PnPTheme [-DetectCurrentComposedLook [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTheme -``` - -Returns the current composed look of the current web. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTheme -DetectCurrentComposedLook -``` - -Returns the current composed look of the current web, and will try to detect the currently applied composed look based upon the actual site. Without this switch the cmdlet will first check for the presence of a property bag variable called _PnP_ProvisioningTemplateComposedLookInfo that contains composed look information when applied through the provisioning engine or the Set-PnPTheme cmdlet. - -## PARAMETERS - -### -DetectCurrentComposedLook -Specify this switch to not use the PnP Provisioning engine based composed look information but try to detect the current composed look as is. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.Entities.ThemeEntity - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTimeZoneId.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTimeZoneId.md deleted file mode 100644 index 6e01c0cb45..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTimeZoneId.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnptimezoneid -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPTimeZoneId ---- - -# Get-PnPTimeZoneId - -## SYNOPSIS -Returns a time zone ID - -## SYNTAX - -```powershell -Get-PnPTimeZoneId [-Match <String>] -``` - -## DESCRIPTION -In order to create a new classic site you need to specify the timezone this site will use. Use the cmdlet to retrieve a list of possible values. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPTimeZoneId -``` - -This will return all time zone IDs in use by Office 365. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTimeZoneId -Match Stockholm -``` - -This will return the time zone IDs for Stockholm - -## PARAMETERS - -### -Match -A string to search for like 'Stockholm' - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -## OUTPUTS - -### List<SharePointPnP.PowerShell.Commands.GetTimeZoneId+Zone> - -Returns a list of matching zones. Use the ID property of the object for use in New-SPOTenantSite - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUPABulkImportStatus.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUPABulkImportStatus.md deleted file mode 100644 index 6096a8d7d3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUPABulkImportStatus.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpupabulkimportstatus -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPUPABulkImportStatus ---- - -# Get-PnPUPABulkImportStatus - -## SYNOPSIS -Get user profile bulk import status. - -## SYNTAX - -```powershell -Get-PnPUPABulkImportStatus [-JobId <GuidPipeBind>] - [-IncludeErrorDetails [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Retrieve information about the status of submitted user profile bulk upload jobs. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPUPABulkImportStatus -``` - -This will list the status of all submitted user profile bulk import jobs. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPUPABulkImportStatus -IncludeErrorDetails -``` - -This will list the status of all submitted user profile bulk import jobs, and if it contains an error it will include the error log messages if present. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPUPABulkImportStatus -JobId <guid> -``` - -This will list the status for the specified import job. - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPUPABulkImportStatus -JobId <guid> -IncludeErrorDetails -``` - -This will list the status for the specified import job, and if it contains an error it will include the error log messages if present. - -## PARAMETERS - -### -IncludeErrorDetails -Include error log details - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -JobId -The instance id of the job - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedAuditLog.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedAuditLog.md deleted file mode 100644 index 6fc8ab0a03..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedAuditLog.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpunifiedauditlog -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPUnifiedAuditLog ---- - -# Get-PnPUnifiedAuditLog - -## SYNOPSIS -Gets unified audit logs from the Office 365 Management API. Requires the Azure Active Directory application permission 'ActivityFeed.Read'. - -## SYNTAX - -### Logs by date -```powershell -Get-PnPUnifiedAuditLog [-ContentType <AuditContentType>] - [-StartTime <DateTime>] - [-EndTime <DateTime>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPUnifiedAuditLog -ContentType SharePoint -StartTime (Get-Date).AddDays(-1) -EndTime (Get-Date).AddDays(-2) -``` - -Retrieves the audit logs of SharePoint happening between the current time yesterday and the current time the day before yesterday - -## PARAMETERS - -### -ContentType -Content type of logs to be retrieved, should be one of the following: AzureActiveDirectory, Exchange, SharePoint, General, DLP. - -```yaml -Type: AuditContentType -Parameter Sets: Logs by date - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EndTime -End time of logs to be retrieved. Start time and end time must both be specified (or both omitted) and must be less than or equal to 24 hours apart. - -```yaml -Type: DateTime -Parameter Sets: Logs by date - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StartTime -Start time of logs to be retrieved. Start time and end time must both be specified (or both omitted) and must be less than or equal to 24 hours apart, with the start time prior to end time and start time no more than 7 days in the past. - -```yaml -Type: DateTime -Parameter Sets: Logs by date - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroup.md deleted file mode 100644 index b673e1f708..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroup.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpunifiedgroup -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPUnifiedGroup ---- - -# Get-PnPUnifiedGroup - -## SYNOPSIS -Gets one Office 365 Group (aka Unified Group) or a list of Office 365 Groups. Requires the Azure Active Directory application permission 'Group.Read.All'. - -## SYNTAX - -```powershell -Get-PnPUnifiedGroup [-Identity <UnifiedGroupPipeBind>] - [-ExcludeSiteUrl [<SwitchParameter>]] - [-IncludeClassification [<SwitchParameter>]] - [-IncludeHasTeam [<SwitchParameter>]] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPUnifiedGroup -``` - -Retrieves all the Office 365 Groups - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPUnifiedGroup -Identity $groupId -``` - -Retrieves a specific Office 365 Group based on its ID - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPUnifiedGroup -Identity $groupDisplayName -``` - -Retrieves a specific or list of Office 365 Groups that start with the given DisplayName - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPUnifiedGroup -Identity $groupSiteMailNickName -``` - -Retrieves a specific or list of Office 365 Groups for which the email starts with the provided mail nickName - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPUnifiedGroup -Identity $group -``` - -Retrieves a specific Office 365 Group based on its object instance - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPUnifiedGroup -IncludeIfHasTeam -``` - -Retrieves all the Office 365 Groups and checks for each of them if it has a Microsoft Team provisioned for it - -## PARAMETERS - -### -ExcludeSiteUrl -Exclude fetching the site URL for Office 365 Groups. This speeds up large listings. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The Identity of the Office 365 Group. - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeClassification -Include Classification value of Office 365 Groups. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IncludeHasTeam -Include a flag for every Office 365 Group if it has a Microsoft Team provisioned for it. This will slow down the retrieval of Office 365 Groups so only use it if you need it. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupMembers.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupMembers.md deleted file mode 100644 index fc58a24be1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupMembers.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpunifiedgroupmembers -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPUnifiedGroupMembers ---- - -# Get-PnPUnifiedGroupMembers - -## SYNOPSIS -Gets members of a particular Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permissions 'Group.Read.All' and 'User.Read.All'. - -## SYNTAX - -```powershell -Get-PnPUnifiedGroupMembers -Identity <UnifiedGroupPipeBind> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPUnifiedGroupMembers -Identity $groupId -``` - -Retrieves all the members of a specific Office 365 Group based on its ID - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPUnifiedGroupMembers -Identity $group -``` - -Retrieves all the members of a specific Office 365 Group based on the group's object instance - -## PARAMETERS - -### -Identity -The Identity of the Office 365 Group. - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupOwners.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupOwners.md deleted file mode 100644 index f4f657a546..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroupOwners.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpunifiedgroupowners -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPUnifiedGroupOwners ---- - -# Get-PnPUnifiedGroupOwners - -## SYNOPSIS -Gets owners of a particular Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permissions 'Group.Read.All' and 'User.Read.All'. - -## SYNTAX - -```powershell -Get-PnPUnifiedGroupOwners -Identity <UnifiedGroupPipeBind> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPUnifiedGroupOwners -Identity $groupId -``` - -Retrieves all the owners of a specific Office 365 Group based on its ID - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPUnifiedGroupOwners -Identity $group -``` - -Retrieves all the owners of a specific Office 365 Group based on the group's object instance - -## PARAMETERS - -### -Identity -The Identity of the Office 365 Group. - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUser.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUser.md deleted file mode 100644 index 5a517eba32..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUser.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpuser -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPUser ---- - -# Get-PnPUser - -## SYNOPSIS -Returns site users of current web - -## SYNTAX - -```powershell -Get-PnPUser [-Identity <UserPipeBind>] - [-WithRightsAssigned [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command will return all users that exist in the current site collection's User Information List - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPUser -``` - -Returns all users from the User Information List of the current site collection regardless if they currently have rights to access the current site - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPUser -Identity 23 -``` - -Returns the user with Id 23 from the User Information List of the current site collection - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPUser -Identity "i:0#.f|membership|user@tenant.onmicrosoft.com" -``` - -Returns the user with LoginName i:0#.f|membership|user@tenant.onmicrosoft.com from the User Information List of the current site collection - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPUser | ? Email -eq "user@tenant.onmicrosoft.com" -``` - -Returns the user with e-mail address user@tenant.onmicrosoft.com from the User Information List of the current site collection - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPUser -WithRightsAssigned -``` - -Returns only those users from the User Information List of the current site collection who currently have any kind of access rights given either directly to the user or Active Directory Group or given to the user or Active Directory Group via membership of a SharePoint Group to the current site - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPUser -WithRightsAssigned -Web subsite1 -``` - -Returns only those users from the User Information List of the current site collection who currently have any kind of access rights given either directly to the user or Active Directory Group or given to the user or Active Directory Group via membership of a SharePoint Group to subsite 'subsite1' - -## PARAMETERS - -### -Identity -User ID or login name - -```yaml -Type: UserPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -WithRightsAssigned -If provided, only users that currently have any kinds of access rights assigned to the current site collection will be returned. Otherwise all users, even those who previously had rights assigned, but not anymore at the moment, will be returned as the information is pulled from the User Information List. Only works if you don't provide an -Identity. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.User - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUserProfileProperty.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUserProfileProperty.md deleted file mode 100644 index 9c982a3af9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUserProfileProperty.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpuserprofileproperty -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPUserProfileProperty ---- - -# Get-PnPUserProfileProperty - -## SYNOPSIS -You must connect to the tenant admin website (https://:<tenant>-admin.sharepoint.com) with Connect-PnPOnline in order to use this cmdlet. - - -## SYNTAX - -```powershell -Get-PnPUserProfileProperty -Account <String[]> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Requires a connection to a SharePoint Tenant Admin site. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPUserProfileProperty -Account 'user@domain.com' -``` - -Returns the profile properties for the specified user - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPUserProfileProperty -Account 'user@domain.com','user2@domain.com' -``` - -Returns the profile properties for the specified users - -## PARAMETERS - -### -Account -The account of the user, formatted either as a login name, or as a claims identity, e.g. i:0#.f|membership|user@domain.com - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.UserProfiles.PersonProperties - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPView.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPView.md deleted file mode 100644 index ec54d1fe64..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPView.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpview -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPView ---- - -# Get-PnPView - -## SYNOPSIS -Returns one or all views from a list - -## SYNTAX - -### -```powershell -Get-PnPView -List <ListPipeBind> - [-Includes <String[]>] - [-Identity <ViewPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPView -List "Demo List" -``` - -Returns all views associated from the specified list - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPView -List "Demo List" -Identity "Demo View" -``` - -Returns the view called "Demo View" from the specified list - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPView -List "Demo List" -Identity "5275148a-6c6c-43d8-999a-d2186989a661" -``` - -Returns the view with the specified ID from the specified list - -## PARAMETERS - -### -Identity -The ID or name of the view - -```yaml -Type: ViewPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -List -The ID or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.View - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWeb.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWeb.md deleted file mode 100644 index fe59155d59..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWeb.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpweb -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWeb ---- - -# Get-PnPWeb - -## SYNOPSIS -Returns the current web object - -## SYNTAX - -### -```powershell -Get-PnPWeb [-Includes <String[]>] - [-Identity <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWeb -``` - -This will return the current web - -## PARAMETERS - -### -Identity -The guid of the web or web object - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Web - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPart.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPart.md deleted file mode 100644 index 400fd01315..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPart.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpwebpart -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWebPart ---- - -# Get-PnPWebPart - -## SYNOPSIS -Returns a web part definition object - -## SYNTAX - -```powershell -Get-PnPWebPart -ServerRelativePageUrl <String> - [-Identity <WebPartPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWebPart -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -``` - -Returns all webparts defined on the given page. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWebPart -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -Identity a2875399-d6ff-43a0-96da-be6ae5875f82 -``` - -Returns a specific web part defined on the given page. - -## PARAMETERS - -### -Identity -The identity of the web part, this can be the web part guid or a web part object - -```yaml -Type: WebPartPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -ServerRelativePageUrl -Full server relative URL of the web part page, e.g. /sites/mysite/sitepages/home.aspx - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<Microsoft.SharePoint.Client.WebParts.WebPartDefinition> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPartProperty.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPartProperty.md deleted file mode 100644 index 15b7d9398d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPartProperty.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpwebpartproperty -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWebPartProperty ---- - -# Get-PnPWebPartProperty - -## SYNOPSIS -Returns a web part property - -## SYNTAX - -```powershell -Get-PnPWebPartProperty -ServerRelativePageUrl <String> - -Identity <GuidPipeBind> - [-Key <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWebPartProperty -ServerRelativePageUrl /sites/demo/sitepages/home.aspx -Identity ccd2c98a-c9ae-483b-ae72-19992d583914 -``` - -Returns all properties of the web part. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWebPartProperty -ServerRelativePageUrl /sites/demo/sitepages/home.aspx -Identity ccd2c98a-c9ae-483b-ae72-19992d583914 -Key "Title" -``` - -Returns the title property of the web part. - -## PARAMETERS - -### -Identity -The id of the web part - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Key -Name of a single property to be returned - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -Full server relative URL of the web part page, e.g. /sites/mysite/sitepages/home.aspx - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPartXml.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPartXml.md deleted file mode 100644 index 95509b605d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebPartXml.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpwebpartxml -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWebPartXml ---- - -# Get-PnPWebPartXml - -## SYNOPSIS -Returns the web part XML of a web part registered on a site - -## SYNTAX - -```powershell -Get-PnPWebPartXml -ServerRelativePageUrl <String> - -Identity <WebPartPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWebPartXml -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -Identity a2875399-d6ff-43a0-96da-be6ae5875f82 -``` - -Returns the web part XML for a given web part on a page. - -## PARAMETERS - -### -Identity -Id or title of the web part. Use Get-PnPWebPart to retrieve all web part Ids - -```yaml -Type: WebPartPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -Full server relative url of the web part page, e.g. /sites/mysite/sitepages/home.aspx - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebTemplates.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebTemplates.md deleted file mode 100644 index bfa29d19b3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebTemplates.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpwebtemplates -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWebTemplates ---- - -# Get-PnPWebTemplates - -## SYNOPSIS -Returns the available web templates - -## SYNTAX - -```powershell -Get-PnPWebTemplates [-Lcid <UInt32>] - [-CompatibilityLevel <Int>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Will list all available templates one can use to create a site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWebTemplates -``` - - - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWebTemplates -LCID 1033 -``` - -Returns all webtemplates for the Locale with ID 1033 (English) - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPWebTemplates -CompatibilityLevel 15 -``` - -Returns all webtemplates for the compatibility level 15 - -## PARAMETERS - -### -CompatibilityLevel -The version of SharePoint - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lcid -The language ID. For instance: 1033 for English. - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.Online.SharePoint.TenantAdministration.SPOTenantWebTemplateCollection - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Locale IDs](http://go.microsoft.com/fwlink/p/?LinkId=242911Id=242911) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebhookSubscriptions.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebhookSubscriptions.md deleted file mode 100644 index b52a1c9879..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWebhookSubscriptions.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpwebhooksubscriptions -applicable: SharePoint Online -schema: 2.0.0 -title: Get-PnPWebhookSubscriptions ---- - -# Get-PnPWebhookSubscriptions - -## SYNOPSIS -Gets all the Webhook subscriptions of the resource - -## SYNTAX - -```powershell -Get-PnPWebhookSubscriptions [-List <ListPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWebhookSubscriptions -List MyList -``` - -Gets all Webhook subscriptions of the list MyList - -## PARAMETERS - -### -List -The list object or name to get the Webhook subscriptions from - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.Entities.WebhookSubscription - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWikiPageContent.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWikiPageContent.md deleted file mode 100644 index 3f42200e07..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWikiPageContent.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpwikipagecontent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWikiPageContent ---- - -# Get-PnPWikiPageContent - -## SYNOPSIS -Gets the contents/source of a wiki page - -## SYNTAX - -```powershell -Get-PnPWikiPageContent -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWikiPageContent -PageUrl '/sites/demo1/pages/wikipage.aspx' -``` - -Gets the content of the page '/sites/demo1/pages/wikipage.aspx' - -## PARAMETERS - -### -ServerRelativePageUrl -The server relative URL for the wiki page - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowDefinition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowDefinition.md deleted file mode 100644 index 050ddaef1d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowDefinition.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpworkflowdefinition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWorkflowDefinition ---- - -# Get-PnPWorkflowDefinition - -## SYNOPSIS -Returns a workflow definition - -## SYNTAX - -```powershell -Get-PnPWorkflowDefinition [-Name <String>] - [-PublishedOnly [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns a workflow definition - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWorkflowDefinition -Name MyWorkflow -``` - -Gets a Workflow with the name "MyWorkflow". - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWorkflowDefinition -Name MyWorkflow -PublishedOnly $false -``` - -Gets a Workflow with the name "MyWorkflow" that is published. - -## PARAMETERS - -### -Name -The name of the workflow - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -PublishedOnly -Return only the published workflows - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.WorkflowServices.WorkflowDefinition - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowInstance.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowInstance.md deleted file mode 100644 index d83c8fc5de..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowInstance.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpworkflowinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWorkflowInstance ---- - -# Get-PnPWorkflowInstance - -## SYNOPSIS -Get workflow instances - -## SYNTAX - -```powershell -Get-PnPWorkflowInstance -List <ListPipeBind> - -ListItem <ListItemPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Gets all workflow instances - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWorkflowInstance -List "My Library" -ListItem $ListItem -``` - -Retrieves workflow instances running against the provided item on list "My Library" - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWorkflowInstance -List "My Library" -ListItem 2 -``` - -Retrieves workflow instances running against the provided item with 2 in the list "My Library" - -## PARAMETERS - -### -List -The List for which workflow instances should be retrieved - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -ListItem -The List Item for which workflow instances should be retrieved - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowSubscription.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowSubscription.md deleted file mode 100644 index 1aab759887..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWorkflowSubscription.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/get-pnpworkflowsubscription -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Get-PnPWorkflowSubscription ---- - -# Get-PnPWorkflowSubscription - -## SYNOPSIS -Return a workflow subscription - -## SYNTAX - -```powershell -Get-PnPWorkflowSubscription [-Name <String>] - [-List <ListPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns a workflow subscriptions from a list - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Get-PnPWorkflowSubscription -Name MyWorkflow -``` - -Gets an Workflow subscription with the name "MyWorkflow". - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWorkflowSubscription -Name MyWorkflow -list $list -``` - -Gets an Workflow subscription with the name "MyWorkflow" from the list $list. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPList -identity "MyList" | Get-PnPWorkflowSubscription -Name MyWorkflow -``` - -Gets an Workflow subscription with the name "MyWorkflow" from the list "MyList". - -## PARAMETERS - -### -List -A list to search the association for - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -Name -The name of the workflow - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.WorkflowServices.WorkflowSubscription - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPHubSiteRights.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPHubSiteRights.md deleted file mode 100644 index f60f9c1457..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPHubSiteRights.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/grant-pnphubsiterights -applicable: SharePoint Online -schema: 2.0.0 -title: Grant-PnPHubSiteRights ---- - -# Grant-PnPHubSiteRights - -## SYNOPSIS -Grant additional permissions to the permissions already in place to associate sites to Hub Sites for one or more specific users - -## SYNTAX - -```powershell -Grant-PnPHubSiteRights [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Grant-PnPHubSiteRights -Identity https://contoso.sharepoint.com/sites/hubsite -Principals "myuser@mydomain.com","myotheruser@mydomain.com" -``` - -This example shows how to grant rights to myuser and myotheruser to associate their sites with the provided Hub Site - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPSiteDesignRights.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPSiteDesignRights.md deleted file mode 100644 index 062ccfa24a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPSiteDesignRights.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/grant-pnpsitedesignrights -applicable: SharePoint Online -schema: 2.0.0 -title: Grant-PnPSiteDesignRights ---- - -# Grant-PnPSiteDesignRights - -## SYNOPSIS -Grants the specified principals rights to use the site design. - -## SYNTAX - -```powershell -Grant-PnPSiteDesignRights -Identity <TenantSiteDesignPipeBind> - -Principals <String[]> - [-Rights <TenantSiteDesignPrincipalRights>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Grant-PnPSiteDesignRights -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -Principals "myuser@mydomain.com","myotheruser@mydomain.com" -``` - -Grants the specified principals View rights on the site design specified - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteDesign -Title "MySiteDesign" -SiteScriptIds 438548fd-60dd-42cf-b843-2db506c8e259 -WebTemplate TeamSite | Grant-PnPSiteDesignRights -Principals "myuser@mydomain.com","myotheruser@mydomain.com" -``` - -Grants the specified principals View rights on the site design specified - -## PARAMETERS - -### -Identity -The site design to use. - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Principals -One or more principals to grant rights to. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Rights -The rights to set. Defaults to 'View' - -```yaml -Type: TenantSiteDesignPrincipalRights -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPTenantServicePrincipalPermission.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPTenantServicePrincipalPermission.md deleted file mode 100644 index ba13744e25..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Grant-PnPTenantServicePrincipalPermission.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/grant-pnptenantserviceprincipalpermission -applicable: SharePoint Online -schema: 2.0.0 -title: Grant-PnPTenantServicePrincipalPermission ---- - -# Grant-PnPTenantServicePrincipalPermission - -## SYNOPSIS -Explicitly grants a specified permission to the "SharePoint Online Client" service principal - -## SYNTAX - -```powershell -Grant-PnPTenantServicePrincipalPermission -Scope <String> - -Resource <String> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Grant-PnPTenantServicePrincipalPermission -Scope "Group.Read.All" -Resource "Microsoft Graph" -``` - -This will explicitly grant the Group.Read.All permission on the Microsoft Graph resource - -## PARAMETERS - -### -Resource -The resource to grant the permission for - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope -The scope to grant the permission for - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.ALM.AppMetadata - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPAppPackage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPAppPackage.md deleted file mode 100644 index 2a4de3f0fd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPAppPackage.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/import-pnpapppackage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Import-PnPAppPackage ---- - -# Import-PnPAppPackage - -## SYNOPSIS -Adds a SharePoint Addin to a site - -## SYNTAX - -```powershell -Import-PnPAppPackage -Path <String> - [-Force [<SwitchParameter>]] - [-LoadOnly [<SwitchParameter>]] - [-Locale <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This commands requires that you have an addin package to deploy - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Import-PnPAppPackage -Path c:\files\demo.app -LoadOnly -``` - -This will load the addin in the demo.app package, but will not install it to the site. - - -### ------------------EXAMPLE 2------------------ -```powershell -Import-PnPAppPackage -Path c:\files\demo.app -Force -``` - -This load first activate the addin sideloading feature, upload and install the addin, and deactivate the addin sideloading feature. - - -## PARAMETERS - -### -Force -Will forcibly install the app by activating the addin sideloading feature, installing the addin, and deactivating the sideloading feature - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LoadOnly -Will only upload the addin, but not install it - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Locale -Will install the addin for the specified locale - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Path pointing to the .app file - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.AppInstance - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTaxonomy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTaxonomy.md deleted file mode 100644 index 2ab6d301cc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTaxonomy.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/import-pnptaxonomy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Import-PnPTaxonomy ---- - -# Import-PnPTaxonomy - -## SYNOPSIS -Imports a taxonomy from either a string array or a file - -## SYNTAX - -### Direct -```powershell -Import-PnPTaxonomy [-Terms <String[]>] - [-Lcid <Int>] - [-TermStoreName <String>] - [-Delimiter <String>] - [-SynchronizeDeletions [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### File -```powershell -Import-PnPTaxonomy -Path <String> - [-Lcid <Int>] - [-TermStoreName <String>] - [-Delimiter <String>] - [-SynchronizeDeletions [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Import-PnPTaxonomy -Terms 'Company|Locations|Stockholm' -``` - -Creates a new termgroup, 'Company', a termset 'Locations' and a term 'Stockholm' - -### ------------------EXAMPLE 2------------------ -```powershell -Import-PnPTaxonomy -Terms 'Company|Locations|Stockholm|Central','Company|Locations|Stockholm|North' -``` - -Creates a new termgroup, 'Company', a termset 'Locations', a term 'Stockholm' and two subterms: 'Central', and 'North' - -### ------------------EXAMPLE 3------------------ -```powershell -Import-PnPTaxonomy -Path ./mytaxonomyterms.txt -``` - -Imports the taxonomy from the file specified. Each line has to be in the format TERMGROUP|TERMSET|TERM. See example 2 for examples of the format. - -## PARAMETERS - -### -Delimiter -The path delimiter to be used, by default this is '|' - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lcid - - -```yaml -Type: Int -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Specifies a file containing terms per line, in the format as required by the Terms parameter. - -```yaml -Type: String -Parameter Sets: File - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -SynchronizeDeletions -If specified, terms that exist in the termset, but are not in the imported data, will be removed. - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Terms -An array of strings describing termgroup, termset, term, subterms using a default delimiter of '|'. - -```yaml -Type: String[] -Parameter Sets: Direct - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -TermStoreName -Term store to import to; if not specified the default term store is used. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTermGroupFromXml.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTermGroupFromXml.md deleted file mode 100644 index 062eaf79fd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTermGroupFromXml.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/import-pnptermgroupfromxml -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Import-PnPTermGroupFromXml ---- - -# Import-PnPTermGroupFromXml - -## SYNOPSIS -Imports a taxonomy TermGroup from either the input or from an XML file. - -## SYNTAX - -### XML -```powershell -Import-PnPTermGroupFromXml [-Xml <String>] - [-Connection <SPOnlineConnection>] -``` - -### File -```powershell -Import-PnPTermGroupFromXml [-Path <String>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Import-PnPTermGroupFromXml -Xml $xml -``` - -Imports the XML based termgroup information located in the $xml variable - -### ------------------EXAMPLE 2------------------ -```powershell -Import-PnPTermGroupFromXml -Path input.xml -``` - -Imports the XML file specified by the path. - -## PARAMETERS - -### -Path -The XML File to import the data from - -```yaml -Type: String -Parameter Sets: File - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Xml -The XML to process - -```yaml -Type: String -Parameter Sets: XML - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTermSet.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTermSet.md deleted file mode 100644 index e56196ba9b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Import-PnPTermSet.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/import-pnptermset -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Import-PnPTermSet ---- - -# Import-PnPTermSet - -## SYNOPSIS -Imports a taxonomy term set from a file in the standard format. - -## SYNTAX - -```powershell -Import-PnPTermSet -GroupName <String> - -Path <String> - [-TermSetId <Guid>] - [-SynchronizeDeletions [<SwitchParameter>]] - [-IsOpen <Boolean>] - [-Contact <String>] - [-Owner <String>] - [-TermStoreName <String>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -The format of the file is the same as that used by the import function in the web interface. A sample file can be obtained from the web interface. - -This is a CSV file, with the following headings: - - Term Set Name,Term Set Description,LCID,Available for Tagging,Term Description,Level 1 Term,Level 2 Term,Level 3 Term,Level 4 Term,Level 5 Term,Level 6 Term,Level 7 Term - -The first data row must contain the Term Set Name, Term Set Description, and LCID, and should also contain the first term. - -It is recommended that a fixed GUID be used as the termSetId, to allow the term set to be easily updated (so do not pass Guid.Empty). - -In contrast to the web interface import, this is not a one-off import but runs synchronization logic allowing updating of an existing Term Set. When synchronizing, any existing terms are matched (with Term Description and Available for Tagging updated as necessary), any new terms are added in the correct place in the hierarchy, and (if synchronizeDeletions is set) any terms not in the imported file are removed. - -The import file also supports an expanded syntax for the Term Set Name and term names (Level 1 Term, Level 2 Term, etc). These columns support values with the format 'Name | GUID', with the name and GUID separated by a pipe character (note that the pipe character is invalid to use within a taxonomy item name). This expanded syntax is not required, but can be used to ensure all terms have fixed IDs. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Import-PnPTermSet -GroupName 'Standard Terms' -Path 'C:\\Temp\\ImportTermSet.csv' -SynchronizeDeletions -``` - -Creates (or updates) the term set specified in the import file, in the group specified, removing any existing terms not in the file. - -### ------------------EXAMPLE 2------------------ -```powershell -Import-PnPTermSet -TermStoreName 'My Term Store' -GroupName 'Standard Terms' -Path 'C:\\Temp\\ImportTermSet.csv' -TermSetId '{15A98DB6-D8E2-43E6-8771-066C1EC2B8D8}' -``` - -Creates (or updates) the term set specified in the import file, in the term store and group specified, using the specified ID. - -### ------------------EXAMPLE 3------------------ -```powershell -Import-PnPTermSet -GroupName 'Standard Terms' -Path 'C:\\Temp\\ImportTermSet.csv' -IsOpen $true -Contact 'user@example.org' -Owner 'user@example.org' -``` - -Creates (or updates) the term set specified in the import file, setting the IsOpen, Contact, and Owner properties as specified. - -## PARAMETERS - -### -Contact -Contact for the term set; if not specified, the existing setting is retained. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -GroupName -Group to import the term set to; an error is returned if the group does not exist. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -IsOpen -Whether the term set should be marked open; if not specified, then the existing setting is not changed. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owner -Owner for the term set; if not specified, the existing setting is retained. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Path -Local path to the file containing the term set to import, in the standard format (as the 'sample import file' available in the Term Store Administration). - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -SynchronizeDeletions -If specified, the import will remove any terms (and children) previously in the term set but not in the import file; default is to leave them. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermSetId -GUID to use for the term set; if not specified, or the empty GUID, a random GUID is generated and used. - -```yaml -Type: Guid -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermStoreName -Term store to import into; if not specified the default term store is used. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Initialize-PnPPowerShellAuthentication.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Initialize-PnPPowerShellAuthentication.md deleted file mode 100644 index 6072e5f2cd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Initialize-PnPPowerShellAuthentication.md +++ /dev/null @@ -1,223 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/initialize-pnppowershellauthentication -applicable: SharePoint Online -schema: 2.0.0 -title: Initialize-PnPPowerShellAuthentication ---- - -# Initialize-PnPPowerShellAuthentication - -## SYNOPSIS -Initializes a Azure AD App and optionally creates a new self-signed certificate to use with the application registration. - -## SYNTAX - -### Generate Certificate -```powershell -Initialize-PnPPowerShellAuthentication -ApplicationName <String> - -Tenant <String> - [-CommonName <String>] - [-OutPath <String>] - [-Store <StoreLocation>] - [-Scopes <String[]>] - [-Country <String>] - [-State <String>] - [-Locality <String>] - [-Organization <String>] - [-OrganizationUnit <String>] - [-ValidYears <Int>] - [-CertificatePassword <SecureString>] -``` - -### Existing Certificate -```powershell -Initialize-PnPPowerShellAuthentication -CertificatePath <String> - -ApplicationName <String> - -Tenant <String> - [-Scopes <String[]>] - [-CertificatePassword <SecureString>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Initialize-PnPPowerShellAuthentication -ApplicationName TestApp -Tenant yourtenant.onmicrosoft.com -Store CurrentUser -``` - -Creates a new Azure AD Application registration, creates a new self signed certificate, and adds it to the local certificate store. It will upload the certificate to the azure app registration and it will request the following permissions: Sites.FullControl.All, Group.ReadWrite.All, User.Read.All - -## PARAMETERS - -### -ApplicationName -The name of the Azure AD Application to create - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -CertificatePassword -Optional certificate password - -```yaml -Type: SecureString -Parameter Sets: Generate Certificate, Existing Certificate - -Required: False -Position: 8 -Accept pipeline input: False -``` - -### -CertificatePath -Password for the certificate being created - -```yaml -Type: String -Parameter Sets: Existing Certificate - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -CommonName -Common Name (e.g. server FQDN or YOUR name). defaults to 'pnp.contoso.com' - -```yaml -Type: String -Parameter Sets: Generate Certificate - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Country -Country Name (2 letter code) - -```yaml -Type: String -Parameter Sets: Generate Certificate - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -Locality -Locality Name (eg, city) - -```yaml -Type: String -Parameter Sets: Generate Certificate - -Required: False -Position: 3 -Accept pipeline input: False -``` - -### -Organization -Organization Name (eg, company) - -```yaml -Type: String -Parameter Sets: Generate Certificate - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -OrganizationUnit -Organizational Unit Name (eg, section) - -```yaml -Type: String -Parameter Sets: Generate Certificate - -Required: False -Position: 5 -Accept pipeline input: False -``` - -### -OutPath -Folder to create certificate files in (.CER and .PFX) - -```yaml -Type: String -Parameter Sets: Generate Certificate - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scopes -Specify which permissions scopes to request. - -```yaml -Type: String[] -Parameter Sets: Generate Certificate - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -State -State or Province Name (full name) - -```yaml -Type: String -Parameter Sets: Generate Certificate - -Required: False -Position: 2 -Accept pipeline input: False -``` - -### -Store -Local Certificate Store to add the certificate to - -```yaml -Type: StoreLocation -Parameter Sets: Generate Certificate - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Tenant -The identifier of your tenant, e.g. mytenant.onmicrosoft.com - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ValidYears -Number of years until expiration (default is 10, max is 30) - -```yaml -Type: Int -Parameter Sets: Generate Certificate - -Required: False -Position: 7 -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Install-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Install-PnPApp.md deleted file mode 100644 index d19ad1577d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Install-PnPApp.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/install-pnpapp -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Install-PnPApp ---- - -# Install-PnPApp - -## SYNOPSIS -Installs an available app from the app catalog - -## SYNTAX - -```powershell -Install-PnPApp -Identity <AppMetadataPipeBind> - [-Scope <AppCatalogScope>] - [-Wait [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Install-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will install an app that is available in the tenant scoped app catalog, specified by the id, to the current site. - -### ------------------EXAMPLE 2------------------ -```powershell -Install-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Site -``` - -This will install an app that is available in the site collection scoped app catalog, specified by the id, to the current site. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe | Install-PnPApp -``` - -This will install the given app from the tenant scoped app catalog into the site. - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Site | Install-PnPApp -``` - -This will install the given app from the site collection scoped app catalog into the site. - -## PARAMETERS - -### -Identity -Specifies the Id or an actual app metadata instance - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Wait -If specified the execution will pause until the app has been installed in the site. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Install-PnPSolution.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Install-PnPSolution.md deleted file mode 100644 index 0b5bf6c82d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Install-PnPSolution.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/install-pnpsolution -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Install-PnPSolution ---- - -# Install-PnPSolution - -## SYNOPSIS -Installs a sandboxed solution to a site collection. WARNING! This method can delete your composed look gallery due to the method used to activate the solution. We recommend you to only to use this cmdlet if you are okay with that. - -## SYNTAX - -```powershell -Install-PnPSolution -PackageId <GuidPipeBind> - -SourceFilePath <String> - [-MajorVersion <Int>] - [-MinorVersion <Int>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Install-PnPSolution -PackageId c2f5b025-7c42-4d3a-b579-41da3b8e7254 -SourceFilePath mypackage.wsp -``` - -Installs the package to the current site - -## PARAMETERS - -### -MajorVersion -Optional major version of the solution, defaults to 1 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MinorVersion -Optional minor version of the solution, defaults to 0 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PackageId -ID of the solution, from the solution manifest - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -SourceFilePath -Path to the sandbox solution package (.WSP) file - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPQuery.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPQuery.md deleted file mode 100644 index aea87980c8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPQuery.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/invoke-pnpquery -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Invoke-PnPQuery ---- - -# Invoke-PnPQuery - -## SYNOPSIS -Executes the currently queued actions - -## SYNTAX - -```powershell -Invoke-PnPQuery [-RetryCount <Int>] - [-RetryWait <Int>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Executes any queued actions / changes on the SharePoint Client Side Object Model Context - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Invoke-PnPQuery -RetryCount 5 -``` - -This will execute any queued actions / changes on the SharePoint Client Side Object Model Context and will retry 5 times in case of throttling. - -### ------------------EXAMPLE 2------------------ -```powershell -Invoke-PnPQuery -RetryWait 10 -``` - -This will execute any queued actions / changes on the SharePoint Client Side Object Model Context and delay the execution for 10 seconds before it retries the execution. - -## PARAMETERS - -### -RetryCount -Number of times to retry in case of throttling. Defaults to 10. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RetryWait -Delay in seconds. Defaults to 1. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPSPRestMethod.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPSPRestMethod.md deleted file mode 100644 index ec6af2bb54..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPSPRestMethod.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/invoke-pnpsprestmethod -applicable: SharePoint Online -schema: 2.0.0 -title: Invoke-PnPSPRestMethod ---- - -# Invoke-PnPSPRestMethod - -## SYNOPSIS -Invokes a REST request towards a SharePoint site - -## SYNTAX - -```powershell -Invoke-PnPSPRestMethod -Url <String> - [-Method <HttpRequestMethod>] - [-Content <Object>] - [-ContentType <String>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Invokes a REST request towards a SharePoint site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Invoke-PnPSPRestMethod -Url /_api/web -``` - -This example executes a GET request towards the current site collection and returns the properties of the current web - -### ------------------EXAMPLE 2------------------ -```powershell -$output = Invoke-PnPSPRestMethod -Url '/_api/web/lists?$select=Id,Title' -$output.value -``` - -This example executes a GET request towards the current site collection and returns the id and title of all the lists and outputs them to the console. Notice the use of single quotes. If you want to use double quotes (") then you will have to escape the $ character with a backtick: `$ - -### ------------------EXAMPLE 3------------------ -```powershell -$item = @{Title="Test"} -Invoke-PnPSPRestMethod -Method Post -Url "/_api/web/lists/GetByTitle('Test')/items" -Content $item -``` - -This example creates a new item in the list 'Test' and sets the title field to 'Test' - -### ------------------EXAMPLE 4------------------ -```powershell -$item = "{'Title':'Test'}" -Invoke-PnPSPRestMethod -Method Post -Url "/_api/web/lists/GetByTitle('Test')/items" -Content $item -``` - -This example creates a new item in the list 'Test' and sets the title field to 'Test' - -### ------------------EXAMPLE 5------------------ -```powershell -$item = "{ '__metadata': { 'type': 'SP.Data.TestListItem' }, 'Title': 'Test'}" -Invoke-PnPSPRestMethod -Method Post -Url "/_api/web/lists/GetByTitle('Test')/items" -Content $item -ContentType "application/json;odata=verbose" -``` - -This example creates a new item in the list 'Test' and sets the title field to 'Test' - -## PARAMETERS - -### -Content -A string or object to send - -```yaml -Type: Object -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ContentType -The content type of the object to send. Defaults to 'application/json' - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Method -The Http method to execute. Defaults to GET. - -```yaml -Type: HttpRequestMethod -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Url -The url to execute. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPSiteDesign.md deleted file mode 100644 index 790728f168..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPSiteDesign.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/invoke-pnpsitedesign -applicable: SharePoint Online -schema: 2.0.0 -title: Invoke-PnPSiteDesign ---- - -# Invoke-PnPSiteDesign - -## SYNOPSIS -Apply a Site Design to an existing site. * Requires Tenant Administration Rights * - -## SYNTAX - -```powershell -Invoke-PnPSiteDesign -Identity <TenantSiteDesignPipeBind> - [-WebUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Invoke-PnPSiteDesign -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -``` - -Applies the specified site design to the current site. - -### ------------------EXAMPLE 2------------------ -```powershell -Invoke-PnPSiteDesign -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -WebUrl https://contoso.sharepoint.com/sites/mydemosite -``` - -Applies the specified site design to the specified site. - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSiteDesign | ?{$_.Title -eq "Demo"} | Invoke-PnPSiteDesign -``` - -Applies the specified site design to the specified site. - -## PARAMETERS - -### -Identity -The Site Design Id or an actual Site Design object to apply - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -WebUrl -The URL of the web to apply the site design to. If not specified it will default to the current web based upon the URL specified with Connect-PnPOnline. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPWebAction.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPWebAction.md deleted file mode 100644 index 5009e6f985..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Invoke-PnPWebAction.md +++ /dev/null @@ -1,286 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/invoke-pnpwebaction -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Invoke-PnPWebAction ---- - -# Invoke-PnPWebAction - -## SYNOPSIS -Executes operations on web, lists and list items. - -## SYNTAX - -```powershell -Invoke-PnPWebAction [-Webs <Web[]>] - [-WebAction <Web>] - [-ShouldProcessWebAction <Web>] - [-PostWebAction <Web>] - [-ShouldProcessPostWebAction <Web>] - [-WebProperties <String[]>] - [-ListAction <List>] - [-ShouldProcessListAction <List>] - [-PostListAction <List>] - [-ShouldProcessPostListAction <List>] - [-ListProperties <String[]>] - [-ListItemAction <ListItem>] - [-ShouldProcessListItemAction <ListItem>] - [-ListItemProperties <String[]>] - [-SubWebs [<SwitchParameter>]] - [-DisableStatisticsOutput [<SwitchParameter>]] - [-SkipCounting [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Invoke-PnPWebAction -ListAction ${function:ListAction} -``` - -This will call the function ListAction on all the lists located on the current web. - -### ------------------EXAMPLE 2------------------ -```powershell -Invoke-PnPWebAction -ShouldProcessListAction ${function:ShouldProcessList} -ListAction ${function:ListAction} -``` - -This will call the function ShouldProcessList, if it returns true the function ListAction will then be called. This will occur on all lists located on the current web - -## PARAMETERS - -### -DisableStatisticsOutput -Will not output statistics after the operation - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ListAction -Function to be executed on the list. There is one input parameter of type List - -```yaml -Type: List -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ListItemAction -Function to be executed on the list item. There is one input parameter of type ListItem - -```yaml -Type: ListItem -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ListItemProperties -The properties to load for list items. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ListProperties -The properties to load for list. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PostListAction -Function to be executed on the list, this will trigger after list items have been processed. There is one input parameter of type List - -```yaml -Type: List -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PostWebAction -Function to be executed on the web, this will trigger after lists and list items have been processed. There is one input parameter of type Web - -```yaml -Type: Web -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShouldProcessListAction -Function to be executed on the web that would determine if ListAction should be invoked, There is one input parameter of type List and the function should return a boolean value - -```yaml -Type: List -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShouldProcessListItemAction -Function to be executed on the web that would determine if ListItemAction should be invoked, There is one input parameter of type ListItem and the function should return a boolean value - -```yaml -Type: ListItem -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShouldProcessPostListAction -Function to be executed on the web that would determine if PostListAction should be invoked, There is one input parameter of type List and the function should return a boolean value - -```yaml -Type: List -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShouldProcessPostWebAction -Function to be executed on the web that would determine if PostWebAction should be invoked, There is one input parameter of type Web and the function should return a boolean value - -```yaml -Type: Web -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShouldProcessWebAction -Function to be executed on the web that would determine if WebAction should be invoked, There is one input parameter of type Web and the function should return a boolean value - -```yaml -Type: Web -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipCounting -Will skip the counting process; by doing this you will not get an estimated time remaining - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SubWebs -Specify if sub webs will be processed - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -WebAction -Function to be executed on the web. There is one input parameter of type Web - -```yaml -Type: Web -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -WebProperties -The properties to load for web. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Webs -Webs you want to process (for example different site collections), will use Web parameter if not specified - -```yaml -Type: Web[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPList.md deleted file mode 100644 index a1ae0e693c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPList.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/measure-pnplist -applicable: SharePoint Online, SharePoint 2016, SharePoint 2019 -schema: 2.0.0 -title: Measure-PnPList ---- - -# Measure-PnPList - -## SYNOPSIS -Returns statistics on the list object - -## SYNTAX - -### -```powershell -Measure-PnPList -Identity <ListPipeBind> - [-Includes <String[]>] - [-ItemLevel [<SwitchParameter>]] - [-BrokenPermissions [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Measure-PnPList "Documents" -``` - -Gets statistics on Documents document library - -### ------------------EXAMPLE 2------------------ -```powershell -Measure-PnPList "Documents" -BrokenPermissions -ItemLevel -``` - -Displays items and folders with broken permissions inside Documents library - -## PARAMETERS - -### -BrokenPermissions -Show items with broken permissions - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity - - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Includes -Specify properties to include when retrieving objects from the server. - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -ItemLevel -Show item level statistics - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPResponseTime.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPResponseTime.md deleted file mode 100644 index cfa4787a7f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPResponseTime.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/measure-pnpresponsetime -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Measure-PnPResponseTime ---- - -# Measure-PnPResponseTime - -## SYNOPSIS -Gets statistics on response time for the specified endpoint by sending probe requests - -## SYNTAX - -```powershell -Measure-PnPResponseTime [-Url <DiagnosticEndpointPipeBind>] - [-Count <UInt32>] - [-WarmUp <UInt32>] - [-Timeout <UInt32>] - [-Histogram <UInt32>] - [-Mode <MeasureResponseTimeMode>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Measure-PnPResponseTime -Count 100 -Timeout 20 -``` - -Calculates statistics on sequence of 100 probe requests, sleeps 20ms between probes - -### ------------------EXAMPLE 2------------------ -```powershell -Measure-PnPResponseTime "/Pages/Test.aspx" -Count 1000 -``` - -Calculates statistics on response time of Test.aspx by sending 1000 requests with default sleep time between requests - -### ------------------EXAMPLE 3------------------ -```powershell -Measure-PnPResponseTime $web -Count 1000 -WarmUp 10 -Histogram 20 -Timeout 50 | Select -expa Histogram | % {$_.GetEnumerator() | Export-Csv C:\Temp\responsetime.csv -NoTypeInformation} -``` - -Builds histogram of response time for the home page of the web and exports to CSV for later processing in Excel - -## PARAMETERS - -### -Count -Number of probe requests to send - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Histogram -Number of buckets in histogram in output statistics - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Mode -Response time measurement mode. RoundTrip - measures full request round trip. SPRequestDuration - measures server processing time only, based on SPRequestDuration HTTP header. Latency - difference between RoundTrip and SPRequestDuration - -```yaml -Type: MeasureResponseTimeMode -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Timeout -Idle timeout between requests to avoid request throttling - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url - - -```yaml -Type: DiagnosticEndpointPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -WarmUp -Number of warm up requests to send before start calculating statistics - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPWeb.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPWeb.md deleted file mode 100644 index af4c2851a6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Measure-PnPWeb.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/measure-pnpweb -applicable: SharePoint Online, SharePoint 2016, SharePoint 2019 -schema: 2.0.0 -title: Measure-PnPWeb ---- - -# Measure-PnPWeb - -## SYNOPSIS -Returns statistics on the web object - -## SYNTAX - -```powershell -Measure-PnPWeb [-Identity <WebPipeBind>] - [-Recursive [<SwitchParameter>]] - [-IncludeHiddenList [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Measure-PnPWeb -``` - -Gets statistics on the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Measure-PnPWeb $web -Recursive -``` - -Gets statistics on the provided web including all its subwebs - -## PARAMETERS - -### -Identity - - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -IncludeHiddenList -Include hidden lists in statistics calculation - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Recursive -Iterate all sub webs recursively - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019, SharePoint Server 2016 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPClientSideComponent.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPClientSideComponent.md deleted file mode 100644 index ab1b544e02..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPClientSideComponent.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/move-pnpclientsidecomponent -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Move-PnPClientSideComponent ---- - -# Move-PnPClientSideComponent - -## SYNOPSIS -Moves a Client-Side Component to a different section/column - -## SYNTAX - -### Move to other section -```powershell -Move-PnPClientSideComponent -Section <Int> - -Page <ClientSidePagePipeBind> - -InstanceId <GuidPipeBind> - [-Position <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Move to other column -```powershell -Move-PnPClientSideComponent -Column <Int> - -Page <ClientSidePagePipeBind> - -InstanceId <GuidPipeBind> - [-Position <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Move within a column -```powershell -Move-PnPClientSideComponent -Position <Int> - -Page <ClientSidePagePipeBind> - -InstanceId <GuidPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Move to other section and column -```powershell -Move-PnPClientSideComponent -Section <Int> - -Column <Int> - -Page <ClientSidePagePipeBind> - -InstanceId <GuidPipeBind> - [-Position <Int>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Moves a Client-Side Component to a different location on the page. Notice that the sections and or columns need to be present before moving the component. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Move-PnPClientSideComponent -Page Home -InstanceId a2875399-d6ff-43a0-96da-be6ae5875f82 -Section 1 -``` - -Moves the specified component to the first section of the page. - -### ------------------EXAMPLE 2------------------ -```powershell -Move-PnPClientSideComponent -Page Home -InstanceId a2875399-d6ff-43a0-96da-be6ae5875f82 -Column 2 -``` - -Moves the specified component to the second column of the current section. - -### ------------------EXAMPLE 3------------------ -```powershell -Move-PnPClientSideComponent -Page Home -InstanceId a2875399-d6ff-43a0-96da-be6ae5875f82 -Section 1 -Column 2 -``` - -Moves the specified component to the first section of the page into the second column. - -### ------------------EXAMPLE 4------------------ -```powershell -Move-PnPClientSideComponent -Page Home -InstanceId a2875399-d6ff-43a0-96da-be6ae5875f82 -Section 1 -Column 2 -Position 2 -``` - -Moves the specified component to the first section of the page into the second column and sets the column to position 2 in the list of webparts. - -## PARAMETERS - -### -Column -The column to move the web part to - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Move to other column, Move to other section and column - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -InstanceId -The instance id of the control. Use Get-PnPClientSideControl retrieve the instance ids. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Page -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Position -Change to order of the web part in the column - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Move to other column, Move to other section, Move to other section and column, Move within a column - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Section -The section to move the web part to - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: Move to other section, Move to other section and column - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPFile.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPFile.md deleted file mode 100644 index da1efed516..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPFile.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/move-pnpfile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Move-PnPFile ---- - -# Move-PnPFile - -## SYNOPSIS -Moves a file to a different location - -## SYNTAX - -### Server Relative -```powershell -Move-PnPFile -ServerRelativeUrl <String> - -TargetUrl <String> - [-OverwriteIfAlreadyExists [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Site Relative -```powershell -Move-PnPFile -SiteRelativeUrl <String> - -TargetUrl <String> - [-OverwriteIfAlreadyExists [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -PS:>Move-PnPFile -ServerRelativeUrl /sites/project/Documents/company.docx -TargetUrl /sites/otherproject/Documents/company.docx -``` - -Moves a file named company.docx located in the document library called Documents located in the projects sitecollection under the managed path sites to the site collection otherproject located in the managed path sites. If a file named company.aspx already exists, it won't perform the move. - -### ------------------EXAMPLE 2------------------ -```powershell -PS:>Move-PnPFile -SiteRelativeUrl Documents/company.aspx -TargetUrl /sites/otherproject/Documents/company.docx -``` - -Moves a file named company.docx located in the document library called Documents located in the current site to the Documents library in the site collection otherproject located in the managed path sites. If a file named company.aspx already exists, it won't perform the move. - -### ------------------EXAMPLE 3------------------ -```powershell -PS:>Move-PnPFile -ServerRelativeUrl /sites/project/Documents/company.docx -TargetUrl /sites/otherproject/Documents/company.docx -OverwriteIfAlreadyExists -``` - -Moves a file named company.docx located in the document library called Documents located in the projects sitecollection under the managed path sites to the site collection otherproject located in the managed path sites. If a file named company.aspx already exists, it will still perform the move and replace the original company.aspx file. - -## PARAMETERS - -### -Force -If provided, no confirmation will be requested and the action will be performed - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OverwriteIfAlreadyExists -If provided, if a file already exists at the TargetUrl, it will be overwritten. If omitted, the move operation will be canceled if the file already exists at the TargetUrl location. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativeUrl -Server relative Url specifying the file to move. Must include the file name. - -```yaml -Type: String -Parameter Sets: Server Relative - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SiteRelativeUrl -Site relative Url specifying the file to move. Must include the file name. - -```yaml -Type: String -Parameter Sets: Site Relative - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TargetUrl -Server relative Url where to move the file to. Must include the file name. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPFolder.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPFolder.md deleted file mode 100644 index f2fe0e77fc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPFolder.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/move-pnpfolder -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Move-PnPFolder ---- - -# Move-PnPFolder - -## SYNOPSIS -Move a folder to another location in the current web - -## SYNTAX - -```powershell -Move-PnPFolder -Folder <String> - -TargetFolder <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Move-PnPFolder -Folder Documents/Reports -TargetFolder 'Archived Reports' -``` - -This will move the folder Reports in the Documents library to the 'Archived Reports' library - -### ------------------EXAMPLE 2------------------ -```powershell -Move-PnPFolder -Folder 'Shared Documents/Reports/2016/Templates' -TargetFolder 'Shared Documents/Reports' -``` - -This will move the folder Templates to the new location in 'Shared Documents/Reports' - -## PARAMETERS - -### -Folder -The folder to move - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TargetFolder -The new parent location to which the folder should be moved to - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Folder - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPItemProxy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPItemProxy.md deleted file mode 100644 index a987f56ed5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPItemProxy.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/move-pnpitemproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Move-PnPItemProxy ---- - -# Move-PnPItemProxy - -## SYNOPSIS -Proxy cmdlet for using Move-Item between SharePoint provider and FileSystem provider - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPListItemToRecycleBin.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPListItemToRecycleBin.md deleted file mode 100644 index 68b0df822e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnPListItemToRecycleBin.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/move-pnplistitemtorecyclebin -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Move-PnPListItemToRecycleBin ---- - -# Move-PnPListItemToRecycleBin - -## SYNOPSIS -Moves an item from a list to the Recycle Bin - -## SYNTAX - -```powershell -Move-PnPListItemToRecycleBin -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Move-PnPListItemToRecycleBin -List "Demo List" -Identity "1" -Force -``` - -Moves the listitem with id "1" from the "Demo List" list to the Recycle Bin. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the listitem, or actual ListItem object - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnpRecycleBinItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnpRecycleBinItem.md deleted file mode 100644 index 575a8d603c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Move-PnpRecycleBinItem.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/move-pnprecyclebinitem -applicable: SharePoint Online -schema: 2.0.0 -title: Move-PnPRecycleBinItem ---- - -# Move-PnPRecycleBinItem - -## SYNOPSIS -Moves all items or a specific item in the first stage recycle bin of the current site collection to the second stage recycle bin - -## SYNTAX - -```powershell -Move-PnPRecycleBinItem [-Identity <RecycleBinItemPipeBind>] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Move-PnpRecycleBinItem -``` - -Moves all the items in the first stage recycle bin of the current site collection to the second stage recycle bin - -### ------------------EXAMPLE 2------------------ -```powershell -Move-PnpRecycleBinItem -Identity 26ffff29-b526-4451-9b6f-7f0e56ba7125 -``` - -Moves the item with the provided ID in the first stage recycle bin of the current site collection to the second stage recycle bin without asking for confirmation first - -### ------------------EXAMPLE 3------------------ -```powershell -Move-PnpRecycleBinItem -Force -``` - -Moves all the items in the first stage recycle bin of the current context to the second stage recycle bin without asking for confirmation first - -## PARAMETERS - -### -Force -If provided, no confirmation will be asked to move the first stage recycle bin items to the second stage - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -If provided, moves the item with the specific ID to the second stage recycle bin - -```yaml -Type: RecycleBinItemPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPAzureCertificate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPAzureCertificate.md deleted file mode 100644 index 01b19a183f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPAzureCertificate.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpazurecertificate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPAzureCertificate ---- - -# New-PnPAzureCertificate - -## SYNOPSIS -Generate a new 2048bit self-signed certificate and manifest settings for use when using CSOM via an app-only ADAL application. - -See https://github.com/SharePoint/PnP-PowerShell/tree/master/Samples/SharePoint.ConnectUsingAppPermissions for a sample on how to get started. - -KeyCredentials contains the ADAL app manifest sections. - -Certificate contains the PEM encoded certificate. - -PrivateKey contains the PEM encoded private key of the certificate. - -## SYNTAX - -```powershell -New-PnPAzureCertificate [-CommonName <String>] - [-Country <String>] - [-State <String>] - [-Locality <String>] - [-Organization <String>] - [-OrganizationUnit <String>] - [-OutPfx <String>] - [-OutCert <String>] - [-ValidYears <Int>] - [-CertificatePassword <SecureString>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPAzureCertificate -OutPfx pnp.pfx -OutCert pnp.cer -``` - -This will generate a default self-signed certificate named "pnp.contoso.com" valid for 10 years and output a pfx and cer file. - -### ------------------EXAMPLE 2------------------ -```powershell -New-PnPAzureCertificate -CommonName "My Certificate" -ValidYears 30 -``` - -This will output a certificate named "My Certificate" which expires in 30 years from now. - -## PARAMETERS - -### -CertificatePassword -Optional certificate password - -```yaml -Type: SecureString -Parameter Sets: (All) - -Required: False -Position: 8 -Accept pipeline input: False -``` - -### -CommonName -Common Name (e.g. server FQDN or YOUR name) [pnp.contoso.com] - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Country -Country Name (2 letter code) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -Locality -Locality Name (eg, city) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 3 -Accept pipeline input: False -``` - -### -Organization -Organization Name (eg, company) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -OrganizationUnit -Organizational Unit Name (eg, section) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 5 -Accept pipeline input: False -``` - -### -OutCert -Filename to write to, optionally including full path (.cer) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 6 -Accept pipeline input: False -``` - -### -OutPfx -Filename to write to, optionally including full path (.pfx) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 6 -Accept pipeline input: False -``` - -### -State -State or Province Name (full name) - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 2 -Accept pipeline input: False -``` - -### -ValidYears -Number of years until expiration (default is 10, max is 30) - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: 7 -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPExtensibilityHandlerObject.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPExtensibilityHandlerObject.md deleted file mode 100644 index 00b7076bd4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPExtensibilityHandlerObject.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpextensibilityhandlerobject -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPExtensibilityHandlerObject ---- - -# New-PnPExtensibilityHandlerObject - -## SYNOPSIS -Creates an ExtensibilityHandler Object, to be used by the Get-PnPProvisioningTemplate cmdlet - -## SYNTAX - -```powershell -New-PnPExtensibilityHandlerObject -Assembly <String> - -Type <String> - [-Configuration <String>] - [-Disabled [<SwitchParameter>]] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell - -$handler = New-PnPExtensibilityHandlerObject -Assembly Contoso.Core.Handlers -Type Contoso.Core.Handlers.MyExtensibilityHandler -Get-PnPProvisioningTemplate -Out NewTemplate.xml -ExtensibilityHandlers $handler -``` - -This will create a new ExtensibilityHandler object that is run during extraction of the template - -## PARAMETERS - -### -Assembly -The full assembly name of the handler - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Configuration -Any configuration data you want to send to the handler - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Disabled -If set, the handler will be disabled - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Type -The type of the handler - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.Framework.Provisioning.Model.ExtensibilityHandler - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPGroup.md deleted file mode 100644 index 03594fb82f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPGroup.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPGroup ---- - -# New-PnPGroup - -## SYNOPSIS -Adds group to the Site Groups List and returns a group object - -## SYNTAX - -```powershell -New-PnPGroup -Title <String> - [-Description <String>] - [-Owner <String>] - [-AllowRequestToJoinLeave [<SwitchParameter>]] - [-AutoAcceptRequestToJoinLeave [<SwitchParameter>]] - [-AllowMembersEditMembership [<SwitchParameter>]] - [-DisallowMembersViewMembership [<SwitchParameter>]] - [-RequestToJoinEmail <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPGroup -Title "My Site Users" -``` - - - -## PARAMETERS - -### -AllowMembersEditMembership -A switch parameter that specifies whether group members can modify membership in the group - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AllowRequestToJoinLeave -A switch parameter that specifies whether to allow users to request membership in the group and to allow users to request to leave the group - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AutoAcceptRequestToJoinLeave -A switch parameter that specifies whether users are automatically added or removed when they make a request - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description for the group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisallowMembersViewMembership -A switch parameter that disallows group members to view membership. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owner -The owner for the group, which can be a user or another group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RequestToJoinEmail -The e-mail address to which membership requests are sent - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The Title of the group - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Group - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPList.md deleted file mode 100644 index 3eaf7b81f0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPList.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnplist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPList ---- - -# New-PnPList - -## SYNOPSIS -Creates a new list - -## SYNTAX - -```powershell -New-PnPList -Title <String> - -Template <ListTemplateType> - [-Url <String>] - [-Hidden [<SwitchParameter>]] - [-EnableVersioning [<SwitchParameter>]] - [-EnableContentTypes [<SwitchParameter>]] - [-OnQuickLaunch [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPList -Title Announcements -Template Announcements -``` - -Create a new announcements list - -### ------------------EXAMPLE 2------------------ -```powershell -New-PnPList -Title "Demo List" -Url "lists/DemoList" -Template Announcements -``` - -Create an announcements list with a title that is different from the url - -### ------------------EXAMPLE 3------------------ -```powershell -New-PnPList -Title HiddenList -Template GenericList -Hidden -``` - -Create a new custom list and hides it from the SharePoint UI - -## PARAMETERS - -### -EnableContentTypes -Switch parameter if content types should be enabled on this list - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableVersioning -Switch parameter if versioning should be enabled - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Hidden -Switch parameter if list should be hidden from the SharePoint UI - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OnQuickLaunch -Switch parameter if this list should be visible on the QuickLaunch - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Template -The type of list to create. - -```yaml -Type: ListTemplateType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -The Title of the list - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -If set, will override the url of the list. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPPersonalSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPPersonalSite.md deleted file mode 100644 index 0ca9ea6968..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPPersonalSite.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnppersonalsite -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPPersonalSite ---- - -# New-PnPPersonalSite - -## SYNOPSIS -Office365 only: Creates a personal / OneDrive For Business site - -## SYNTAX - -```powershell -New-PnPPersonalSite -Email <String[]> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$users = ('katiej@contoso.onmicrosoft.com','garth@contoso.onmicrosoft.com') - New-PnPPersonalSite -Email $users -``` - -Creates a personal / OneDrive For Business site for the 2 users in the variable $users - -## PARAMETERS - -### -Email -The UserPrincipalName (UPN) of the users - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplate.md deleted file mode 100644 index e17e05bdf1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplate.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPProvisioningTemplate ---- - -# New-PnPProvisioningTemplate - -## SYNOPSIS -Creates a new provisioning template object - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$template = New-PnPProvisioningTemplate -``` - -Creates a new instance of a site template object. - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplateFromFolder.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplateFromFolder.md deleted file mode 100644 index b2dbd851da..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplateFromFolder.md +++ /dev/null @@ -1,237 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpprovisioningtemplatefromfolder -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPProvisioningTemplateFromFolder ---- - -# New-PnPProvisioningTemplateFromFolder - -## SYNOPSIS -Generates a provisioning template from a given folder, including only files that are present in that folder - -## SYNTAX - -```powershell -New-PnPProvisioningTemplateFromFolder [-Out <String>] - [-Folder <String>] - [-Match <String>] - [-ContentType <ContentTypePipeBind>] - [-Properties <Hashtable>] - [-AsIncludeFile [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Encoding <Encoding>] - [-TargetFolder <String>] - [-Schema <XMLPnPSchemaVersion>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.xml -``` - -Creates an empty provisioning template, and includes all files in the current folder. - -### ------------------EXAMPLE 2------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.xml -Folder c:\temp -``` - -Creates an empty provisioning template, and includes all files in the c:\temp folder. - -### ------------------EXAMPLE 3------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.xml -Folder c:\temp -Match *.js -``` - -Creates an empty provisioning template, and includes all files with a JS extension in the c:\temp folder. - -### ------------------EXAMPLE 4------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.xml -Folder c:\temp -Match *.js -TargetFolder "Shared Documents" -``` - -Creates an empty provisioning template, and includes all files with a JS extension in the c:\temp folder and marks the files in the template to be added to the 'Shared Documents' folder - -### ------------------EXAMPLE 5------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.xml -Folder c:\temp -Match *.js -TargetFolder "Shared Documents" -ContentType "Test Content Type" -``` - -Creates an empty provisioning template, and includes all files with a JS extension in the c:\temp folder and marks the files in the template to be added to the 'Shared Documents' folder. It will add a property to the item for the content type. - -### ------------------EXAMPLE 6------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.xml -Folder c:\temp -Match *.js -TargetFolder "Shared Documents" -Properties @{"Title" = "Test Title"; "Category"="Test Category"} -``` - -Creates an empty provisioning template, and includes all files with a JS extension in the c:\temp folder and marks the files in the template to be added to the 'Shared Documents' folder. It will add the specified properties to the file entries. - -### ------------------EXAMPLE 7------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.pnp -``` - -Creates an empty provisioning template as a pnp package file, and includes all files in the current folder - -### ------------------EXAMPLE 8------------------ -```powershell -New-PnPProvisioningTemplateFromFolder -Out template.pnp -Folder c:\temp -``` - -Creates an empty provisioning template as a pnp package file, and includes all files in the c:\temp folder - -## PARAMETERS - -### -AsIncludeFile -If specified, the output will only contain the <pnp:Files> element. This allows the output to be included in another template. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ContentType -An optional content type to use. - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Encoding -The encoding type of the XML file, Unicode is default - -```yaml -Type: Encoding -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Folder -Folder to process. If not specified the current folder will be used. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Force -Overwrites the output file if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Match -Optional wildcard pattern to match filenames against. If empty all files will be included. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Properties -Additional properties to set for every file entry in the generated template. - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Schema -The schema of the output to use, defaults to the latest schema - -```yaml -Type: XMLPnPSchemaVersion -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -TargetFolder -Target folder to provision to files to. If not specified, the current folder name will be used. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Encoding](https://docs.microsoft.com/dotnet/api/system.text.encoding) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPSite.md deleted file mode 100644 index f46fe6166a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPSite.md +++ /dev/null @@ -1,333 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpsite -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPSite ---- - -# New-PnPSite - -## SYNOPSIS -Creates either a communication site or an Office 365 group-connected team site - -## SYNTAX - -### Communication Site with Built-In Site Design -```powershell -New-PnPSite -Title <String> - -Url <String> - -Type <SiteType> - [-Description <String>] - [-Classification <String>] - [-Owner <String>] - [-AllowFileSharingForGuestUsers [<SwitchParameter>]] - [-SiteDesign <CommunicationSiteDesign>] - [-Lcid <UInt32>] - [-HubSiteId <GuidPipeBind>] - [-Wait [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### Team Site -```powershell -New-PnPSite -Title <String> - -Alias <String> - -Type <SiteType> - [-Lcid <UInt32>] - [-Description <String>] - [-Classification <String>] - [-IsPublic <String>] - [-Owners <String[]>] - [-HubSiteId <GuidPipeBind>] - [-Wait [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### Communication Site with Custom Design -```powershell -New-PnPSite -Title <String> - -Url <String> - -SiteDesignId <GuidPipeBind> - -Type <SiteType> - [-Description <String>] - [-Classification <String>] - [-Owner <String>] - [-AllowFileSharingForGuestUsers [<SwitchParameter>]] - [-Lcid <UInt32>] - [-HubSiteId <GuidPipeBind>] - [-Wait [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -The New-PnPSite cmdlet creates a new site collection for the current tenant. Currently only 'modern' sites like Communication Site and the Modern Office 365 group-connected team sites are supported. If you want to create a classic site, use New-PnPTenantSite. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -``` - -This will create a new Communications Site collection with the title 'Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso' - -### ------------------EXAMPLE 2------------------ -```powershell -New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -SiteDesign Showcase -``` - -This will create a new Communications Site collection with the title 'Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso'. It will use the 'Showcase' design for the site. - -### ------------------EXAMPLE 3------------------ -```powershell -New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -SiteDesignId ae2349d5-97d6-4440-94d1-6516b72449ac -``` - -This will create a new Communications Site collection with the title 'Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso'. It will use the specified custom site design for the site. - -### ------------------EXAMPLE 4------------------ -```powershell -New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -Classification "HBI" -``` - -This will create a new Communications Site collection with the title 'Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso'. The classification for the site will be set to "HBI" - -### ------------------EXAMPLE 5------------------ -```powershell -New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -ShareByEmailEnabled -``` - -This will create a new Communications Site collection with the title 'Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso'. Allows owners to invite users outside of the organization. - -### ------------------EXAMPLE 6------------------ -```powershell -New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -Lcid 1040 -``` - -This will create a new Communications Site collection with the title 'Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso' and sets the default language to Italian. - -### ------------------EXAMPLE 7------------------ -```powershell -New-PnPSite -Type TeamSite -Title 'Team Contoso' -Alias contoso -``` - -This will create a new Modern Team Site collection with the title 'Team Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso' or 'https://tenant.sharepoint.com/teams/contoso' based on the managed path configuration in the SharePoint Online Admin portal. - -### ------------------EXAMPLE 8------------------ -```powershell -New-PnPSite -Type TeamSite -Title 'Team Contoso' -Alias contoso -IsPublic -``` - -This will create a new Modern Team Site collection with the title 'Team Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso' or 'https://tenant.sharepoint.com/teams/contoso' based on the managed path configuration in the SharePoint Online Admin portal and sets the site to public. - -### ------------------EXAMPLE 9------------------ -```powershell -New-PnPSite -Type TeamSite -Title 'Team Contoso' -Alias contoso -Lcid 1040 -``` - -This will create a new Modern Team Site collection with the title 'Team Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso' or 'https://tenant.sharepoint.com/teams/contoso' based on the managed path configuration in the SharePoint Online Admin portal and sets the default language of the site to Italian. - -## PARAMETERS - -### -Alias -Specifies the alias of the new site collection which represents the part of the URL that will be assigned to the site behind 'https://tenant.sharepoint.com/sites/' or 'https://tenant.sharepoint.com/teams/' based on the managed path configuration in the SharePoint Online Admin portal, this parameter only applies to Modern Team Sites - -```yaml -Type: String -Parameter Sets: Team Site - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -AllowFileSharingForGuestUsers -Specifies if guest users can share files in the new site collection - -```yaml -Type: SwitchParameter -Parameter Sets: Communication Site with Built-In Site Design - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Classification -Specifies the classification of the new site collection - -```yaml -Type: String -Parameter Sets: Communication Site with Built-In Site Design - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Description -Specifies the description of the new site collection - -```yaml -Type: String -Parameter Sets: Communication Site with Built-In Site Design - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -HubSiteId -If specified the site will be associated to the hubsite as identified by this id - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IsPublic -Specifies if new site collection is public. Defaults to false. - -```yaml -Type: String -Parameter Sets: Team Site - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Lcid -Specifies the language of the new site collection. Defaults to the current language of the web connected to. - -```yaml -Type: UInt32 -Parameter Sets: Communication Site with Built-In Site Design - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Owner -Specifies the owner of the site. Specify the value as a string array: "user@domain.com" - -```yaml -Type: String -Parameter Sets: Communication Site with Built-In Site Design - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Owners -Specifies the owners of the site. Specify the value as a string array: "user@domain.com","anotheruser@domain.com" - -```yaml -Type: String[] -Parameter Sets: Team Site - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -SiteDesign -Specifies the site design of the new site collection. Defaults to 'Topic' - -```yaml -Type: CommunicationSiteDesign -Parameter Sets: Communication Site with Built-In Site Design - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -SiteDesignId -Specifies the site design id to use for the new site collection. If specified will override SiteDesign - -```yaml -Type: GuidPipeBind -Parameter Sets: Communication Site with Custom Design - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Title -Specifies the title of the new site collection - -```yaml -Type: String -Parameter Sets: Communication Site with Built-In Site Design - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Type -Specifies with type of site to create. - -```yaml -Type: SiteType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -Specifies the full url of the new site collection, this parameter only applies to Communications Sites - -```yaml -Type: String -Parameter Sets: Communication Site with Built-In Site Design - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Wait -If specified the cmdlet will wait until the site has been fully created and all site artifacts have been provisioned by SharePoint. Notice that this can take a while. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### System.String - -Returns the url of the newly created site collection - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequence.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequence.md deleted file mode 100644 index a405ea47ce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequence.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptenantsequence -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPTenantSequence ---- - -# New-PnPTenantSequence - -## SYNOPSIS -Creates a new tenant sequence object - -## SYNTAX - -```powershell -New-PnPTenantSequence [-Id <String>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$sequence = New-PnPTenantSequence -``` - -Creates a new instance of a tenant sequence object. - -### ------------------EXAMPLE 2------------------ -```powershell -$sequence = New-PnPTenantSequence -Id "MySequence" -``` - -Creates a new instance of a tenant sequence object and sets the Id to the value specified. - -## PARAMETERS - -### -Id -Optional Id of the sequence - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceCommunicationSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceCommunicationSite.md deleted file mode 100644 index 8a1f7958cb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceCommunicationSite.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptenantsequencecommunicationsite -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPTenantSequenceCommunicationSite ---- - -# New-PnPTenantSequenceCommunicationSite - -## SYNOPSIS -Creates a communication site object - -## SYNTAX - -```powershell -New-PnPTenantSequenceCommunicationSite -Url <String> - -Title <String> - [-Language <UInt32>] - [-Owner <String>] - [-Description <String>] - [-Classification <String>] - [-SiteDesignId <String>] - [-HubSite [<SwitchParameter>]] - [-AllowFileSharingForGuestUsers [<SwitchParameter>]] - [-TemplateIds <String[]>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$site = New-PnPTenantSequenceCommunicationSite -Url "/sites/mycommunicationsite" -Title "My Team Site" -``` - -Creates a new communication site object with the specified variables - -## PARAMETERS - -### -AllowFileSharingForGuestUsers - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Classification - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HubSite - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Language - - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owner - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SiteDesignId - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateIds - - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSite.md deleted file mode 100644 index 23347a29a7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSite.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptenantsequenceteamnogroupsite -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPTenantSequenceTeamNoGroupSite ---- - -# New-PnPTenantSequenceTeamNoGroupSite - -## SYNOPSIS -Creates a new team site without an Office 365 group in-memory object - -## SYNTAX - -```powershell -New-PnPTenantSequenceTeamNoGroupSite -Url <String> - -Title <String> - -TimeZoneId <UInt32> - [-Language <UInt32>] - [-Owner <String>] - [-Description <String>] - [-HubSite [<SwitchParameter>]] - [-TemplateIds <String[]>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$site = New-PnPTenantSequenceTeamNoGroupSite -Url "/sites/MyTeamSite" -Title "My Team Site" -``` - -Creates a new team site object with the specified variables - -## PARAMETERS - -### -Description - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HubSite - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Language - - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owner - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateIds - - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TimeZoneId - - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSubSite.md deleted file mode 100644 index 842ec52c2b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamNoGroupSubSite.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptenantsequenceteamnogroupsubsite -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPTenantSequenceTeamNoGroupSubSite ---- - -# New-PnPTenantSequenceTeamNoGroupSubSite - -## SYNOPSIS -Creates a team site subsite with no Office 365 group object - -## SYNTAX - -```powershell -New-PnPTenantSequenceTeamNoGroupSubSite -Url <String> - -Title <String> - -TimeZoneId <UInt32> - [-Language <UInt32>] - [-Description <String>] - [-TemplateIds <String[]>] - [-QuickLaunchDisabled [<SwitchParameter>]] - [-UseDifferentPermissionsFromParentSite [<SwitchParameter>]] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$site = New-PnPTenantSequenceTeamNoGroupSubSite -Url "MyTeamSubsite" -Title "My Team Site" -TimeZoneId 4 -``` - -Creates a new team site subsite object with the specified variables - -## PARAMETERS - -### -Description - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Language - - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -QuickLaunchDisabled - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateIds - - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TimeZoneId - - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -UseDifferentPermissionsFromParentSite - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamSite.md deleted file mode 100644 index 120bfffb95..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSequenceTeamSite.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptenantsequenceteamsite -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPTenantSequenceTeamSite ---- - -# New-PnPTenantSequenceTeamSite - -## SYNOPSIS -Creates a team site object - -## SYNTAX - -```powershell -New-PnPTenantSequenceTeamSite -Alias <String> - -Title <String> - [-Description <String>] - [-DisplayName <String>] - [-Classification <String>] - [-Public [<SwitchParameter>]] - [-HubSite [<SwitchParameter>]] - [-TemplateIds <String[]>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$site = New-PnPTenantSequenceTeamSite -Alias "MyTeamSite" -Title "My Team Site" -``` - -Creates a new team site object with the specified variables - -## PARAMETERS - -### -Alias - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Classification - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisplayName - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HubSite - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Public - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateIds - - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSite.md deleted file mode 100644 index 9210da1a8a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSite.md +++ /dev/null @@ -1,227 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptenantsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPTenantSite ---- - -# New-PnPTenantSite - -## SYNOPSIS -Creates a new (classic) site collection for the current tenant - -## SYNTAX - -```powershell -New-PnPTenantSite -Title <String> - -Url <String> - -Owner <String> - -TimeZone <Int> - [-Lcid <UInt32>] - [-Template <String>] - [-ResourceQuota <Double>] - [-ResourceQuotaWarningLevel <Double>] - [-StorageQuota <Int>] - [-StorageQuotaWarningLevel <Int>] - [-RemoveDeletedSite [<SwitchParameter>]] - [-Wait [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -The New-PnPTenantSite cmdlet creates a new site collection for the current company. However, creating a new SharePoint -Online site collection fails if a deleted site with the same URL exists in the Recycle Bin. If you want to use this command for an on-premises farm, please refer to http://blogs.msdn.com/b/vesku/archive/2014/06/09/provisioning-site-collections-using-sp-app-model-in-on-premises-with-just-csom.aspx - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPTenantSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -Owner user@example.org -TimeZone 4 -Template STS#0 -``` - -This will add a site collection with the title 'Contoso', the url 'https://tenant.sharepoint.com/sites/contoso', the timezone 'UTC+01:00',the owner 'user@example.org' and the template used will be STS#0, a TeamSite - -### ------------------EXAMPLE 2------------------ -```powershell -New-PnPTenantSite -Title Contoso -Url /sites/contososite -Owner user@example.org -TimeZone 4 -Template STS#0 -``` - -This will add a site collection with the title 'Contoso', the url 'https://tenant.sharepoint.com/sites/contososite' of which the base part will be picked up from your current connection, the timezone 'UTC+01:00', the owner 'user@example.org' and the template used will be STS#0, a TeamSite - -## PARAMETERS - -### -Force -Do not ask for confirmation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lcid -Specifies the language of this site collection. For more information, see Locale IDs Assigned by Microsoft: https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splanguage.lcid.aspx. To get the list of supported languages use: (Get-PnPWeb -Includes RegionalSettings.InstalledLanguages).RegionalSettings.InstalledLanguages - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owner -Specifies the user name of the site collection's primary owner. The owner must be a user instead of a security group or an email-enabled security group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -RemoveDeletedSite -Specifies if any existing site with the same URL should be removed from the recycle bin - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ResourceQuota -Specifies the quota for this site collection in Sandboxed Solutions units. This value must not exceed the company's aggregate available Sandboxed Solutions quota. The default value is 0. For more information, see Resource Usage Limits on Sandboxed Solutions in SharePoint 2010 : http://msdn.microsoft.com/en-us/library/gg615462.aspx. - -```yaml -Type: Double -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ResourceQuotaWarningLevel -Specifies the warning level for the resource quota. This value must not exceed the value set for the ResourceQuota parameter - -```yaml -Type: Double -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StorageQuota -Specifies the storage quota for this site collection in megabytes. This value must not exceed the company's available quota. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StorageQuotaWarningLevel -Specifies the warning level for the storage quota in megabytes. This value must not exceed the values set for the StorageQuota parameter - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Template -Specifies the site collection template type. Use the Get-PnPWebTemplates cmdlet to get the list of valid templates. If no template is specified, one can be added later. The Template and LocaleId parameters must be a valid combination as returned from the Get-PnPWebTemplates cmdlet. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TimeZone -Use Get-PnPTimeZoneId to retrieve possible timezone values - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -Specifies the title of the new site collection - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -Specifies the full URL of the new site collection. It must be in a valid managed path in the company's site. For example, for company contoso, valid managed paths are https://contoso.sharepoint.com/sites and https://contoso.sharepoint.com/teams. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Wait - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Locale IDs](http://go.microsoft.com/fwlink/p/?LinkId=242911Id=242911)[Resource Usage Limits on Sandboxed Solutions in SharePoint 2010](http://msdn.microsoft.com/en-us/library/gg615462.aspx.)[Creating on-premises site collections using CSOM](http://blogs.msdn.com/b/vesku/archive/2014/06/09/provisioning-site-collections-using-sp-app-model-in-on-premises-with-just-csom.aspx) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantTemplate.md deleted file mode 100644 index 956b59112d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantTemplate.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptenanttemplate -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPTenantTemplate ---- - -# New-PnPTenantTemplate - -## SYNOPSIS -Creates a new tenant template object - -## SYNTAX - -```powershell -New-PnPTenantTemplate [-Author <String>] - [-Description <String>] - [-DisplayName <String>] - [-Generator <String>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -$template = New-PnPTenantTemplate -``` - -Creates a new instance of a tenant template object. - -## PARAMETERS - -### -Author - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisplayName - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Generator - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTerm.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTerm.md deleted file mode 100644 index b04d630199..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTerm.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpterm -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPTerm ---- - -# New-PnPTerm - -## SYNOPSIS -Creates a taxonomy term - -## SYNTAX - -```powershell -New-PnPTerm -Name <String> - -TermSet <Id, Title or TaxonomyItem> - -TermGroup <Id, Title or TermGroup> - [-Id <Guid>] - [-Lcid <Int>] - [-Description <String>] - [-CustomProperties <Hashtable>] - [-LocalCustomProperties <Hashtable>] - [-TermStore <Id, Name or Object>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPTerm -TermSet "Departments" -TermGroup "Corporate" -Name "Finance" -``` - -Creates a new taxonomy term named "Finance" in the termset Departments which is located in the "Corporate" termgroup - -## PARAMETERS - -### -CustomProperties -Custom Properties - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -Descriptive text to help users understand the intended use of this term. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Id -The Id to use for the term; if not specified, or the empty GUID, a random GUID is generated and used. - -```yaml -Type: Guid -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lcid -The locale id to use for the term. Defaults to the current locale id. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LocalCustomProperties -Custom Properties - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -The name of the term. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -TermGroup -The termgroup to create the term in. - -```yaml -Type: Id, Title or TermGroup -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -TermSet -The termset to add the term to. - -```yaml -Type: Id, Title or TaxonomyItem -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TermStore -Term store to check; if not specified the default term store is used. - -```yaml -Type: Id, Name or Object -Parameter Sets: __AllParameterSets -Aliases: TermStoreName - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.Term - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermGroup.md deleted file mode 100644 index 0be093cb98..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermGroup.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptermgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPTermGroup ---- - -# New-PnPTermGroup - -## SYNOPSIS -Creates a taxonomy term group - -## SYNTAX - -```powershell -New-PnPTermGroup -Name <String> - [-Id <Guid>] - [-Description <String>] - [-TermStore <Id, Name or Object>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPTermGroup -GroupName "Countries" -``` - -Creates a new taxonomy term group named "Countries" - -## PARAMETERS - -### -Description -Description to use for the term group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Id -GUID to use for the term group; if not specified, or the empty GUID, a random GUID is generated and used. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: GroupId - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -Name of the taxonomy term group to create. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: GroupName - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -TermStore -Term store to add the group to; if not specified the default term store is used. - -```yaml -Type: Id, Name or Object -Parameter Sets: (All) -Aliases: TermStoreName - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.TermGroup - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermLabel.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermLabel.md deleted file mode 100644 index a6f0157e88..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermLabel.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptermlabel -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPTermLabel ---- - -# New-PnPTermLabel - -## SYNOPSIS -Creates a localized label for a taxonomy term - -## SYNTAX - -```powershell -New-PnPTermLabel -Term <Id, Title or TaxonomyItem> - -Name <String> - -Lcid <Int> - [-IsDefault [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Creates a localized label for a taxonomy term. Use Get-PnPTerm -Include Labels to request the current labels on a taxonomy term. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPTermLabel -Name "Finanzwesen" -Lcid 1031 -Term (Get-PnPTerm -Identity "Finance" -TermSet "Departments" -TermGroup "Corporate") -``` - -Creates a new localized taxonomy label in German (LCID 1031) named "Finanzwesen" for the term "Finance" in the termset Departments which is located in the "Corporate" termgroup - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTerm -Identity "Finance" -TermSet "Departments" -TermGroup "Corporate" | New-PnPTermLabel -Name "Finanzwesen" -Lcid 1031 -``` - -Creates a new localized taxonomy label in German (LCID 1031) named "Finanzwesen" for the term "Finance" in the termset Departments which is located in the "Corporate" termgroup - -## PARAMETERS - -### -IsDefault -Makes this new label the default label - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lcid -The locale id to use for the localized term - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Name -The localized name of the term - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Term -The term to add the localized label to - -```yaml -Type: Id, Title or TaxonomyItem -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.Label - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermSet.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermSet.md deleted file mode 100644 index 043392fecc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTermSet.md +++ /dev/null @@ -1,206 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnptermset -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPTermSet ---- - -# New-PnPTermSet - -## SYNOPSIS -Creates a taxonomy term set - -## SYNTAX - -```powershell -New-PnPTermSet -Name <String> - -TermGroup <Id, Title or TermGroup> - [-Id <Guid>] - [-Lcid <Int>] - [-Contact <String>] - [-Description <String>] - [-IsOpenForTermCreation [<SwitchParameter>]] - [-IsNotAvailableForTagging [<SwitchParameter>]] - [-Owner <String>] - [-StakeHolders <String[]>] - [-CustomProperties <Hashtable>] - [-TermStore <Id, Name or Object>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPTermSet -Name "Department" -TermGroup "Corporate" -``` - -Creates a new termset named "Department" in the group named "Corporate" - -## PARAMETERS - -### -Contact -An e-mail address for term suggestion and feedback. If left blank the suggestion feature will be disabled. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CustomProperties - - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -Descriptive text to help users understand the intended use of this term set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Id -The Id to use for the term set; if not specified, or the empty GUID, a random GUID is generated and used. - -```yaml -Type: Guid -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IsNotAvailableForTagging -By default a term set is available to be used by end users and content editors of sites consuming this term set. Specify this switch to turn this off - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IsOpenForTermCreation -When a term set is closed, only metadata managers can add terms to this term set. When it is open, users can add terms from a tagging application. Not specifying this switch will make the term set closed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Lcid -The locale id to use for the term set. Defaults to the current locale id. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -The name of the termset. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Owner -The primary user or group of this term set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StakeHolders -People and groups in the organization that should be notified before major changes are made to the term set. You can enter multiple users or groups. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermGroup -Name, id or actually termgroup to create the termset in. - -```yaml -Type: Id, Title or TermGroup -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -TermStore -Term store to check; if not specified the default term store is used. - -```yaml -Type: Id, Name or Object -Parameter Sets: (All) -Aliases: TermStoreName - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Taxonomy.TermSet - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUPABulkImportJob.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUPABulkImportJob.md deleted file mode 100644 index e08855b804..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUPABulkImportJob.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpupabulkimportjob -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPUPABulkImportJob ---- - -# New-PnPUPABulkImportJob - -## SYNOPSIS -Submit up a new user profile bulk import job. - -## SYNTAX - -```powershell -New-PnPUPABulkImportJob -Folder <String> - -Path <String> - -UserProfilePropertyMapping <Hashtable> - -IdProperty <String> - [-IdType <ImportProfilePropertiesUserIdType>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -See https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/bulk-user-profile-update-api-for-sharepoint-online for information on the API and how the bulk import process works. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -@" - { - "value": [ - { - "IdName": "mikaels@contoso.com", - "Department": "PnP", - }, - { - "IdName": "vesaj@contoso.com", - "Department": "PnP", - } - ] -} -"@ > profiles.json - -New-PnPUPABulkImportJob -Folder "Shared Documents" -Path profiles.json -IdProperty "IdName" -UserProfilePropertyMapping @{"Department"="Department"} -``` - -This will submit a new user profile bulk import job to SharePoint Online. - -## PARAMETERS - -### -Folder -Site or server relative URL of the folder to where you want to store the import job file. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -IdProperty -The name of the identifying property in your file. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 3 -Accept pipeline input: False -``` - -### -IdType -The type of profile identifier (Email/CloudId/PrincipalName). Defaults to Email. - -```yaml -Type: ImportProfilePropertiesUserIdType -Parameter Sets: (All) - -Required: False -Position: 4 -Accept pipeline input: False -``` - -### -Path -The local file path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -UserProfilePropertyMapping -Specify user profile property mapping between the import file and UPA property names. - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: True -Position: 2 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUnifiedGroup.md deleted file mode 100644 index d1ccdf8962..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUnifiedGroup.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpunifiedgroup -applicable: SharePoint Online -schema: 2.0.0 -title: New-PnPUnifiedGroup ---- - -# New-PnPUnifiedGroup - -## SYNOPSIS -Creates a new Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permission 'Group.ReadWrite.All'. - -## SYNTAX - -```powershell -New-PnPUnifiedGroup -DisplayName <String> - -Description <String> - -MailNickname <String> - [-Owners <String[]>] - [-Members <String[]>] - [-IsPrivate [<SwitchParameter>]] - [-GroupLogoPath <String>] - [-CreateTeam [<SwitchParameter>]] - [-Force [<SwitchParameter>]] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPUnifiedGroup -DisplayName $displayName -Description $description -MailNickname $nickname -``` - -Creates a public Office 365 Group with all the required properties - -### ------------------EXAMPLE 2------------------ -```powershell -New-PnPUnifiedGroup -DisplayName $displayName -Description $description -MailNickname $nickname -Owners $arrayOfOwners -Members $arrayOfMembers -``` - -Creates a public Office 365 Group with all the required properties, and with a custom list of Owners and a custom list of Members - -### ------------------EXAMPLE 3------------------ -```powershell -New-PnPUnifiedGroup -DisplayName $displayName -Description $description -MailNickname $nickname -IsPrivate -``` - -Creates a private Office 365 Group with all the required properties - -### ------------------EXAMPLE 4------------------ -```powershell -New-PnPUnifiedGroup -DisplayName $displayName -Description $description -MailNickname $nickname -Owners $arrayOfOwners -Members $arrayOfMembers -IsPrivate -``` - -Creates a private Office 365 Group with all the required properties, and with a custom list of Owners and a custom list of Members - -## PARAMETERS - -### -CreateTeam -Creates a MS Teams team associated with created group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The Description of the Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DisplayName -The Display Name of the Office 365 Group. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -GroupLogoPath -The path to the logo file of to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IsPrivate -Makes the group private when selected. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MailNickname -The Mail Nickname of the Office 365 Group. Cannot contain spaces. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Members -The array UPN values of the group's members. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owners -The array UPN values of the group's owners. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUser.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUser.md deleted file mode 100644 index 744af855f6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUser.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpuser -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPUser ---- - -# New-PnPUser - -## SYNOPSIS -Adds a user to the built-in Site User Info List and returns a user object - -## SYNTAX - -```powershell -New-PnPUser -LoginName <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPUser -LoginName user@company.com -``` - -Adds a new user with the login user@company.com to the current site - -## PARAMETERS - -### -LoginName -The users login name (user@company.com) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: LogonName - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.User - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPWeb.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPWeb.md deleted file mode 100644 index 34e02125a7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPWeb.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/new-pnpweb -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: New-PnPWeb ---- - -# New-PnPWeb - -## SYNOPSIS -Creates a new subweb under the current web - -## SYNTAX - -```powershell -New-PnPWeb -Title <String> - -Url <String> - -Template <String> - [-Description <String>] - [-Locale <Int>] - [-BreakInheritance [<SwitchParameter>]] - [-InheritNavigation [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -New-PnPWeb -Title "Project A Web" -Url projectA -Description "Information about Project A" -Locale 1033 -Template "STS#0" -``` - -Creates a new subweb under the current web with URL projectA - -## PARAMETERS - -### -BreakInheritance -By default the subweb will inherit its security from its parent, specify this switch to break this inheritance - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description of the new web - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -InheritNavigation -Specifies whether the site inherits navigation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Locale -The language id of the new web. default = 1033 for English - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Template -The site definition template to use for the new web, e.g. STS#0. Use Get-PnPWebTemplates to fetch a list of available templates - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the new web - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -The URL of the new web - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Web - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Publish-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Publish-PnPApp.md deleted file mode 100644 index 3b861602cf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Publish-PnPApp.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/publish-pnpapp -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Publish-PnPApp ---- - -# Publish-PnPApp - -## SYNOPSIS -Publishes/Deploys/Trusts an available app in the app catalog - -## SYNTAX - -```powershell -Publish-PnPApp -Identity <AppMetadataPipeBind> - [-SkipFeatureDeployment [<SwitchParameter>]] - [-Scope <AppCatalogScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Publish-PnPApp -Identity 2646ccc3-6a2b-46ef-9273-81411cbbb60f -``` - -This will deploy/trust an app into the app catalog. Notice that the app needs to be available in the tenant scoped app catalog - -### ------------------EXAMPLE 2------------------ -```powershell -Publish-PnPApp -Identity 2646ccc3-6a2b-46ef-9273-81411cbbb60f -Scope Site -``` - -This will deploy/trust an app into the app catalog. Notice that the app needs to be available in the site collection scoped app catalog - -## PARAMETERS - -### -Identity -Specifies the Id of the app - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipFeatureDeployment - - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPProvisioningTemplate.md deleted file mode 100644 index 20c05ffcff..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPProvisioningTemplate.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/read-pnpprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Read-PnPProvisioningTemplate ---- - -# Read-PnPProvisioningTemplate - -## SYNOPSIS -Loads/Reads a PnP file from the file system or a string - -## SYNTAX - -### By Path -```powershell -Read-PnPProvisioningTemplate -Path <String> - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] -``` - -### By XML -```powershell -Read-PnPProvisioningTemplate -Xml <String> - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Read-PnPProvisioningTemplate -Path template.pnp -``` - -Loads a PnP file from the file system - -### ------------------EXAMPLE 2------------------ -```powershell -Read-PnPProvisioningTemplate -Path template.pnp -TemplateProviderExtensions $extensions -``` - -Loads a PnP file from the file system using some custom template provider extensions while loading the file. - -### ------------------EXAMPLE 3------------------ -```powershell -Read-PnPProvisioningTemplate -Xml $xml -``` - -Reads a PnP Provisioning template from a string containing the XML of a provisioning template - -## PARAMETERS - -### -Path -Filename to read from, optionally including full path. - -```yaml -Type: String -Parameter Sets: By Path - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while loading the template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Xml -Variable to read from, containing the valid XML of a provisioning template. - -```yaml -Type: String -Parameter Sets: By XML - -Required: True -Position: 1 -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPTenantTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPTenantTemplate.md deleted file mode 100644 index 3d369dc5e3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPTenantTemplate.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/read-pnptenanttemplate -applicable: SharePoint Online -schema: 2.0.0 -title: Read-PnPTenantTemplate ---- - -# Read-PnPTenantTemplate - -## SYNOPSIS -Loads/Reads a PnP tenant template from the file system and returns an in-memory instance of this template. - -## SYNTAX - -```powershell -Read-PnPTenantTemplate -Path <String> - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Read-PnPTenantTemplate -Path template.pnp -``` - -Reads a PnP tenant template file from the file system and returns an in-memory instance - -## PARAMETERS - -### -Path -Filename to read from, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while loading the template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Register-PnPAppCatalogSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Register-PnPAppCatalogSite.md deleted file mode 100644 index b10a238b59..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Register-PnPAppCatalogSite.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/register-pnpappcatalogsite -applicable: SharePoint Online -schema: 2.0.0 -title: Register-PnPAppCatalogSite ---- - -# Register-PnPAppCatalogSite - -## SYNOPSIS -Creates a new App Catalog Site and sets this site as the Tenant App Catalog - -## SYNTAX - -```powershell -Register-PnPAppCatalogSite -Url <String> - -Owner <String> - -TimeZoneId <Int> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Register-PnPAppCatalogSite -Url https://yourtenant.sharepoint.com/sites/appcatalog -Owner admin@domain.com -TimeZoneId 4 -``` - -This will create a new appcatalog site if no app catalog is already present. Use -Force to create a new appcatalog site if one has already been registered. If using the same URL as an existing one and Force is present, the current/existing appcatalog site will be deleted. - -## PARAMETERS - -### -Force -If specified, and an app catalog is already present, a new app catalog site will be created. If the same URL is used the existing/current app catalog site will be deleted first. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owner -The login account of the user designated to be the admin for the site, e.g. user@domain.com - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TimeZoneId -Use Get-PnPTimeZoneId to retrieve possible timezone values - -```yaml -Type: Int -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Url -The full url of the app catalog site to be created, e.g. https://yourtenant.sharepoint.com/sites/appcatalog - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Register-PnPHubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Register-PnPHubSite.md deleted file mode 100644 index cf89a22cce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Register-PnPHubSite.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/register-pnphubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Register-PnPHubSite ---- - -# Register-PnPHubSite - -## SYNOPSIS -Registers a site as a hubsite - -## SYNTAX - -```powershell -Register-PnPHubSite -Site <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Registers a site as a hubsite - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Register-PnPHubSite -Site https://tenant.sharepoint.com/sites/myhubsite -``` - -This example registers the specified site as a hubsite - -## PARAMETERS - -### -Site -The site to register as a hubsite - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPAlert.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPAlert.md deleted file mode 100644 index c6d04425d4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPAlert.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpalert -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Remove-PnPAlert ---- - -# Remove-PnPAlert - -## SYNOPSIS -Removes an alert for a user - -## SYNTAX - -```powershell -Remove-PnPAlert -Identity <AlertPipeBind> - [-User <UserPipeBind>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPAlert -Identity 641ac67f-0ce0-4837-874a-743c8f8572a7 -``` - -Removes the alert with the specified ID for the current user - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPAlert -Identity 641ac67f-0ce0-4837-874a-743c8f8572a7 -User "i:0#.f|membership|Alice@contoso.onmicrosoft.com" -``` - -Removes the alert with the specified ID for the user specified - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The alert id, or the actual alert object to remove. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AlertPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -User -User to remove the alert for (User ID, login name or actual User object). Skip this parameter to use the current user. Note: Only site owners can remove alerts for other users. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: UserPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPApp.md deleted file mode 100644 index b1b017a820..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPApp.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpapp -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Remove-PnPApp ---- - -# Remove-PnPApp - -## SYNOPSIS -Removes an app from the app catalog - -## SYNTAX - -```powershell -Remove-PnPApp -Identity <AppMetadataPipeBind> - [-Scope <AppCatalogScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will remove the specified app from the tenant scoped app catalog - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Site -``` - -This will remove the specified app from the site collection scoped app catalog - -## PARAMETERS - -### -Identity -Specifies the Id of the Addin Instance - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPApplicationCustomizer.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPApplicationCustomizer.md deleted file mode 100644 index a435d4f99f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPApplicationCustomizer.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpapplicationcustomizer -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Remove-PnPApplicationCustomizer ---- - -# Remove-PnPApplicationCustomizer - -## SYNOPSIS -Removes a SharePoint Framework client side extension application customizer - -## SYNTAX - -### Custom Action Id -```powershell -Remove-PnPApplicationCustomizer [-Identity <UserCustomActionPipeBind>] - [-Scope <CustomActionScope>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Client Side Component Id -```powershell -Remove-PnPApplicationCustomizer -ClientSideComponentId <GuidPipeBind> - [-Scope <CustomActionScope>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes a SharePoint Framework client side extension application customizer by removing a user custom action from a web or sitecollection - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPCustomAction -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -``` - -Removes the custom action representing the client side extension registration with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2'. - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPCustomAction -ClientSideComponentId aa66f67e-46c0-4474-8a82-42bf467d07f2 -Scope web -``` - -Removes the custom action(s) being registered for a SharePoint Framework solution having the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2' in its manifest from the current web. - -## PARAMETERS - -### -ClientSideComponentId -The Client Side Component Id of the SharePoint Framework client side extension application customizer found in the manifest for which existing custom action(s) should be removed - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: Client Side Component Id - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Force -Use the -Force flag to bypass the confirmation question - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The id or name of the CustomAction representing the client side extension registration that needs to be removed or a CustomAction instance itself - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: UserCustomActionPipeBind -Parameter Sets: Custom Action Id - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Define if the CustomAction representing the client side extension registration is to be found at the web or site collection scope. Specify All to allow deletion from either web or site collection (default). - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPClientSideComponent.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPClientSideComponent.md deleted file mode 100644 index 4eee5333ed..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPClientSideComponent.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpclientsidecomponent -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Remove-PnPClientSideComponent ---- - -# Remove-PnPClientSideComponent - -## SYNOPSIS -Removes a Client-Side component from a page - -## SYNTAX - -```powershell -Remove-PnPClientSideComponent -Page <ClientSidePagePipeBind> - -InstanceId <GuidPipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPClientSideComponent -Page Home -InstanceId a2875399-d6ff-43a0-96da-be6ae5875f82 -``` - -Removes the control specified from the page. - -## PARAMETERS - -### -Force -If specified you will not receive the confirmation question - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -InstanceId -The instance id of the component - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Page -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPClientSidePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPClientSidePage.md deleted file mode 100644 index ac571ecb67..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPClientSidePage.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpclientsidepage -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Remove-PnPClientSidePage ---- - -# Remove-PnPClientSidePage - -## SYNOPSIS -Removes a Client-Side Page - -## SYNTAX - -```powershell -Remove-PnPClientSidePage -Identity <ClientSidePagePipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPClientSidePage -Identity "MyPage" -``` - -Removes the Client-Side page named 'MyPage.aspx' - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPClientSidePage -Identity "Templates/MyPageTemplate" -``` - -Removes the specified Client-Side page which is located in the Templates folder of the Site Pages library. - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPClientSidePage $page -``` - -Removes the specified Client-Side page which is contained in the $page variable. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentType.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentType.md deleted file mode 100644 index 73e6e2d9da..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentType.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpcontenttype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPContentType ---- - -# Remove-PnPContentType - -## SYNOPSIS -Removes a content type from a web - -## SYNTAX - -```powershell -Remove-PnPContentType -Identity <ContentTypePipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPContentType -Identity "Project Document" -``` - -This will remove a content type called "Project Document" from the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPContentType -Identity "Project Document" -Force -``` - -This will remove a content type called "Project Document" from the current web with force - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The name or ID of the content type to remove - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromDocumentSet.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromDocumentSet.md deleted file mode 100644 index 0dd632ec2f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromDocumentSet.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpcontenttypefromdocumentset -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPContentTypeFromDocumentSet ---- - -# Remove-PnPContentTypeFromDocumentSet - -## SYNOPSIS -Removes a content type from a document set - -## SYNTAX - -```powershell -Remove-PnPContentTypeFromDocumentSet -ContentType <ContentTypePipeBind> - -DocumentSet <DocumentSetPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPContentTypeFromDocumentSet -ContentType "Test CT" -DocumentSet "Test Document Set" -``` - -This will remove the content type called 'Test CT' from the document set called ''Test Document Set' - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPContentTypeFromDocumentSet -ContentType 0x0101001F1CEFF1D4126E4CAD10F00B6137E969 -DocumentSet 0x0120D520005DB65D094035A241BAC9AF083F825F3B -``` - -This will remove the content type with ID '0x0101001F1CEFF1D4126E4CAD10F00B6137E969' from the document set with ID '0x0120D520005DB65D094035A241BAC9AF083F825F3B' - -## PARAMETERS - -### -ContentType -The content type to remove. Either specify name, an id, or a content type object. - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DocumentSet -The document set to remove the content type from. Either specify a name, a document set template object, an id, or a content type object - -```yaml -Type: DocumentSetPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromList.md deleted file mode 100644 index 8e8ea41048..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPContentTypeFromList.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpcontenttypefromlist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPContentTypeFromList ---- - -# Remove-PnPContentTypeFromList - -## SYNOPSIS -Removes a content type from a list - -## SYNTAX - -```powershell -Remove-PnPContentTypeFromList -List <ListPipeBind> - -ContentType <ContentTypePipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPContentTypeFromList -List "Documents" -ContentType "Project Document" -``` - -This will remove a content type called "Project Document" from the "Documents" list - -## PARAMETERS - -### -ContentType -The name of a content type, its ID or an actual content type object that needs to be removed from the specified list. - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The name of the list, its ID or an actual list object from where the content type needs to be removed from - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPCustomAction.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPCustomAction.md deleted file mode 100644 index d4500b10bf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPCustomAction.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpcustomaction -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPCustomAction ---- - -# Remove-PnPCustomAction - -## SYNOPSIS -Removes a custom action - -## SYNTAX - -```powershell -Remove-PnPCustomAction [-Identity <UserCustomActionPipeBind>] - [-Scope <CustomActionScope>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPCustomAction -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -``` - -Removes the custom action with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2'. - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPCustomAction -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -Scope web -``` - -Removes the custom action with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2' from the current web. - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPCustomAction -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -Force -``` - -Removes the custom action with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2' without asking for confirmation. - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPCustomAction -Scope All | ? Location -eq ScriptLink | Remove-PnPCustomAction -``` - -Removes all custom actions that are ScriptLinks - -## PARAMETERS - -### -Force -Use the -Force flag to bypass the confirmation question - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The id or name of the CustomAction that needs to be removed or a CustomAction instance itself - -```yaml -Type: UserCustomActionPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Define if the CustomAction is to be found at the web or site collection scope. Specify All to allow deletion from either web or site collection. - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPDeletedUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPDeletedUnifiedGroup.md deleted file mode 100644 index c0a7b030e1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPDeletedUnifiedGroup.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpdeletedunifiedgroup -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPDeletedUnifiedGroup ---- - -# Remove-PnPDeletedUnifiedGroup - -## SYNOPSIS -Permanently removes one deleted Office 365 Group (aka Unified Group) - -## SYNTAX - -```powershell -Remove-PnPDeletedUnifiedGroup -Identity <UnifiedGroupPipeBind> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPDeletedUnifiedGroup -Identity 38b32e13-e900-4d95-b860-fb52bc07ca7f -``` - -Permanently removes a deleted Office 365 Group based on its ID - -### ------------------EXAMPLE 2------------------ -```powershell -$group = Get-PnPDeletedUnifiedGroup -Identity 38b32e13-e900-4d95-b860-fb52bc07ca7f -Remove-PnPDeletedUnifiedGroup -Identity $group -``` - -Permanently removes the provided deleted Office 365 Group - -## PARAMETERS - -### -Identity -The Identity of the deleted Office 365 Group - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPEventReceiver.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPEventReceiver.md deleted file mode 100644 index 1e14414211..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPEventReceiver.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpeventreceiver -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPEventReceiver ---- - -# Remove-PnPEventReceiver - -## SYNOPSIS -Remove an eventreceiver - -## SYNTAX - -### List -```powershell -Remove-PnPEventReceiver -Identity <EventReceiverPipeBind> - [-List <ListPipeBind>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes/unregisters a specific eventreceiver - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPEventReceiver -Identity fb689d0e-eb99-4f13-beb3-86692fd39f22 -``` - -This will remove the event receiver with ReceiverId "fb689d0e-eb99-4f13-beb3-86692fd39f22" from the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPEventReceiver -List ProjectList -Identity fb689d0e-eb99-4f13-beb3-86692fd39f22 -``` - -This will remove the event receiver with ReceiverId "fb689d0e-eb99-4f13-beb3-86692fd39f22" from the "ProjectList" list - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPEventReceiver -List ProjectList -Identity MyReceiver -``` - -This will remove the event receiver with ReceiverName "MyReceiver" from the "ProjectList" list - -### ------------------EXAMPLE 4------------------ -```powershell -Remove-PnPEventReceiver -List ProjectList -``` - -This will remove all event receivers from the "ProjectList" list - -### ------------------EXAMPLE 5------------------ -```powershell -Remove-PnPEventReceiver -``` - -This will remove all event receivers from the current site - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPEventReceiver | ? ReceiverUrl -Like "*azurewebsites.net*" | Remove-PnPEventReceiver -``` - -This will remove all event receivers from the current site which are pointing to a service hosted on Azure Websites - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The Guid of the event receiver on the list - -```yaml -Type: EventReceiverPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -List -The list object from where to remove the event receiver object - -```yaml -Type: ListPipeBind -Parameter Sets: List - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPField.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPField.md deleted file mode 100644 index b4c2853b2a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPField.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpfield -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPField ---- - -# Remove-PnPField - -## SYNOPSIS -Removes a field from a list or a site - -## SYNTAX - -```powershell -Remove-PnPField -Identity <FieldPipeBind> - [-Force [<SwitchParameter>]] - [-List <ListPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPField -Identity "Speakers" -``` - -Removes the speakers field from the site columns - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPField -List "Demo list" -Identity "Speakers" -``` - -Removes the speakers field from the list Demo list - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The field object or name to remove - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -List -The list object or name where to remove the field from - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: 1 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFieldFromContentType.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFieldFromContentType.md deleted file mode 100644 index 6c1cc0db57..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFieldFromContentType.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpfieldfromcontenttype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPFieldFromContentType ---- - -# Remove-PnPFieldFromContentType - -## SYNOPSIS -Removes a site column from a content type - -## SYNTAX - -```powershell -Remove-PnPFieldFromContentType -Field <FieldPipeBind> - -ContentType <ContentTypePipeBind> - [-DoNotUpdateChildren [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPFieldFromContentType -Field "Project_Name" -ContentType "Project Document" -``` - -This will remove the site column with an internal name of "Project_Name" from a content type called "Project Document" - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPFieldFromContentType -Field "Project_Name" -ContentType "Project Document" -DoNotUpdateChildren -``` - -This will remove the site column with an internal name of "Project_Name" from a content type called "Project Document". It will not update content types that inherit from the "Project Document" content type. - -## PARAMETERS - -### -ContentType -The content type where the field is to be removed from - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -DoNotUpdateChildren -If specified, inherited content types will not be updated - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Field -The field to remove - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFile.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFile.md deleted file mode 100644 index c3611eb4c3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFile.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpfile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPFile ---- - -# Remove-PnPFile - -## SYNOPSIS -Removes a file. - -## SYNTAX - -### Server Relative -```powershell -Remove-PnPFile -ServerRelativeUrl <String> - [-Recycle [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Site Relative -```powershell -Remove-PnPFile -SiteRelativeUrl <String> - [-Recycle [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -PS:>Remove-PnPFile -ServerRelativeUrl /sites/project/_catalogs/themes/15/company.spcolor -``` - -Removes the file company.spcolor - -### ------------------EXAMPLE 2------------------ -```powershell -PS:>Remove-PnPFile -SiteRelativeUrl _catalogs/themes/15/company.spcolor -``` - -Removes the file company.spcolor - -### ------------------EXAMPLE 3------------------ -```powershell -PS:>Remove-PnPFile -SiteRelativeUrl _catalogs/themes/15/company.spcolor -Recycle -``` - -Removes the file company.spcolor and saves it to the Recycle Bin - -## PARAMETERS - -### -Force - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Recycle - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativeUrl -Server relative URL to the file - -```yaml -Type: String -Parameter Sets: Server Relative - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SiteRelativeUrl -Site relative URL to the file - -```yaml -Type: String -Parameter Sets: Site Relative - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFileFromProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFileFromProvisioningTemplate.md deleted file mode 100644 index e00011a353..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFileFromProvisioningTemplate.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpfilefromprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPFileFromProvisioningTemplate ---- - -# Remove-PnPFileFromProvisioningTemplate - -## SYNOPSIS -Removes a file from a PnP Provisioning Template - -## SYNTAX - -```powershell -Remove-PnPFileFromProvisioningTemplate -Path <String> - -FilePath <String> - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPFileFromProvisioningTemplate -Path template.pnp -FilePath filePath -``` - -Removes a file from an in-memory PnP Provisioning Template - -## PARAMETERS - -### -FilePath -The relative File Path of the file to remove from the in-memory template - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Path -Filename to read the template from, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while saving the template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: 2 -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFolder.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFolder.md deleted file mode 100644 index e94b56034c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPFolder.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpfolder -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPFolder ---- - -# Remove-PnPFolder - -## SYNOPSIS -Deletes a folder within a parent folder - -## SYNTAX - -```powershell -Remove-PnPFolder -Name <String> - -Folder <String> - [-Recycle [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPFolder -Name NewFolder -Folder _catalogs/masterpage -``` - -Removes the folder 'NewFolder' from '_catalogsmasterpage' - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPFolder -Name NewFolder -Folder _catalogs/masterpage -Recycle -``` - -Removes the folder 'NewFolder' from '_catalogsmasterpage' and is saved in the Recycle Bin - -## PARAMETERS - -### -Folder -The parent folder in the site - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Force - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -The folder name - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Recycle - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPGroup.md deleted file mode 100644 index f2f382bda4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPGroup.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPGroup ---- - -# Remove-PnPGroup - -## SYNOPSIS -Removes a group from a web. - -## SYNTAX - -```powershell -Remove-PnPGroup [-Identity <GroupPipeBind>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPGroup -Identity "My Users" -``` - -Removes the group "My Users" - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -A group object, an ID or a name of a group to remove - -```yaml -Type: GroupPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPHomeSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPHomeSite.md deleted file mode 100644 index 937e125572..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPHomeSite.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnphomesite -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPHomeSite ---- - -# Remove-PnPHomeSite - -## SYNOPSIS -Removes the currently set site as the home site - -## SYNTAX - -```powershell -Remove-PnPHomeSite [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPHomeSite -``` - -Removes the currently set site as the home site - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPHubSiteAssociation.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPHubSiteAssociation.md deleted file mode 100644 index 6388a061fb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPHubSiteAssociation.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnphubsiteassociation -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPHubSiteAssociation ---- - -# Remove-PnPHubSiteAssociation - -## SYNOPSIS -Disconnects a site from a hubsite. - -## SYNTAX - -```powershell -Remove-PnPHubSiteAssociation -Site <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Disconnects an site from a hubsite - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPHubSiteAssociation -Site https://tenant.sharepoint.com/sites/mysite -``` - -This example adds the specified site to the hubsite. - -## PARAMETERS - -### -Site -The site to disconnect from its hubsite - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPIndexedProperty.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPIndexedProperty.md deleted file mode 100644 index 0507b9772f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPIndexedProperty.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpindexedproperty -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPIndexedProperty ---- - -# Remove-PnPIndexedProperty - -## SYNOPSIS -Removes a key from propertybag to be indexed by search. The key and it's value remain in the propertybag, however it will not be indexed anymore. - -## SYNTAX - -```powershell -Remove-PnPIndexedProperty -Key <String> - [-List <ListPipeBind>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPIndexedProperty -key "MyIndexProperty" -``` - -Removes the Indexed property "MyIndexProperty" from the current web - -## PARAMETERS - -### -Key -Key of the property bag value to be removed from indexing - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -List -The list object or name from where to remove the indexed properties - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPJavaScriptLink.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPJavaScriptLink.md deleted file mode 100644 index 50f04d40c3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPJavaScriptLink.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpjavascriptlink -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPJavaScriptLink ---- - -# Remove-PnPJavaScriptLink - -## SYNOPSIS -Removes a JavaScript link or block from a web or sitecollection - -## SYNTAX - -```powershell -Remove-PnPJavaScriptLink [-Identity <UserCustomActionPipeBind>] - [-Force [<SwitchParameter>]] - [-Scope <CustomActionScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPJavaScriptLink -Identity jQuery -``` - -Removes the injected JavaScript file with the name jQuery from the current web after confirmation - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPJavaScriptLink -Identity jQuery -Scope Site -``` - -Removes the injected JavaScript file with the name jQuery from the current site collection after confirmation - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPJavaScriptLink -Identity jQuery -Scope Site -Confirm:$false -``` - -Removes the injected JavaScript file with the name jQuery from the current site collection and will not ask for confirmation - -### ------------------EXAMPLE 4------------------ -```powershell -Remove-PnPJavaScriptLink -Scope Site -``` - -Removes all the injected JavaScript files from the current site collection after confirmation for each of them - -### ------------------EXAMPLE 5------------------ -```powershell -Remove-PnPJavaScriptLink -Identity faea0ce2-f0c2-4d45-a4dc-73898f3c2f2e -Scope All -``` - -Removes the injected JavaScript file with id faea0ce2-f0c2-4d45-a4dc-73898f3c2f2e from both the Web and Site scopes - -### ------------------EXAMPLE 6------------------ -```powershell -Get-PnPJavaScriptLink -Scope All | ? Sequence -gt 1000 | Remove-PnPJavaScriptLink -``` - -Removes all the injected JavaScript files from both the Web and Site scope that have a sequence number higher than 1000 - -## PARAMETERS - -### -Force -Use the -Force flag to bypass the confirmation question - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Name or id of the JavaScriptLink to remove. Omit if you want to remove all JavaScript Links. - -```yaml -Type: UserCustomActionPipeBind -Parameter Sets: (All) -Aliases: Key,Name - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Define if the JavaScriptLink is to be found at the web or site collection scope. Specify All to allow deletion from either web or site collection. - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPKnowledgeHubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPKnowledgeHubSite.md deleted file mode 100644 index fccd2b5caf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPKnowledgeHubSite.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpknowledgehubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPKnowledgeHubSite ---- - -# Remove-PnPKnowledgeHubSite - -## SYNOPSIS -Removes the Knowledge Hub Site setting for your tenant - -## SYNTAX - -```powershell -Remove-PnPKnowledgeHubSite [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPKnowledgeHubSite -``` - -Removes the Knowledge Hub Site setting for your tenant - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPList.md deleted file mode 100644 index baedc9a127..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPList.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnplist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPList ---- - -# Remove-PnPList - -## SYNOPSIS -Deletes a list - -## SYNTAX - -```powershell -Remove-PnPList -Identity <ListPipeBind> - [-Recycle [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPList -Identity Announcements -``` - -Removes the list named 'Announcements'. Asks for confirmation. - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPList -Identity Announcements -Force -``` - -Removes the list named 'Announcements' without asking for confirmation. - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPList -Title Announcements -Recycle -``` - -Removes the list named 'Announcements' and saves to the Recycle Bin - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID or Title of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Recycle -Defines if the list should be moved to recycle bin or directly deleted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPListItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPListItem.md deleted file mode 100644 index e2813fb630..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPListItem.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnplistitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPListItem ---- - -# Remove-PnPListItem - -## SYNOPSIS -Deletes an item from a list - -## SYNTAX - -```powershell -Remove-PnPListItem -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-Recycle [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPListItem -List "Demo List" -Identity "1" -Force -``` - -Removes the listitem with id "1" from the "Demo List" list. - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPListItem -List "Demo List" -Identity "1" -Force -Recycle -``` - -Removes the listitem with id "1" from the "Demo List" list and saves it in the Recycle Bin. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the listitem, or actual ListItem object - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Recycle - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPNavigationNode.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPNavigationNode.md deleted file mode 100644 index 904198c634..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPNavigationNode.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpnavigationnode -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPNavigationNode ---- - -# Remove-PnPNavigationNode - -## SYNOPSIS -Removes a menu item from either the quicklaunch or top navigation - -## SYNTAX - -### Remove a node by ID -```powershell -Remove-PnPNavigationNode -Identity <NavigationNodePipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### All Nodes -```powershell -Remove-PnPNavigationNode -All [<SwitchParameter>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPNavigationNode -Identity 1032 -``` - -Removes the navigation node with the specified id - -### ------------------EXAMPLE 2------------------ -```powershell -$nodes = Get-PnPNavigationNode -QuickLaunch -PS:>$nodes | Select-Object -First 1 | Remove-PnPNavigationNode -Force -``` - -Retrieves all navigation nodes from the Quick Launch navigation, then removes the first node in the list and it will not ask for a confirmation - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPNavigationNode -Title Recent -Location QuickLaunch -``` - -Will remove the recent navigation node from the quick launch in the current web. - -### ------------------EXAMPLE 4------------------ -```powershell -Remove-PnPNavigationNode -Title Home -Location TopNavigationBar -Force -``` - -Will remove the home navigation node from the top navigation bar without prompting for a confirmation in the current web. - -### ------------------EXAMPLE 5------------------ -```powershell -Get-PnPNavigationNode -Location QuickLaunch | Remove-PnPNavigationNode -Force -``` - -Will remove all the navigation nodes from the quick launch bar without prompting for a confirmation in the current web. - -## PARAMETERS - -### -All -Specifying the All parameter will remove all the nodes from specified Location. - -```yaml -Type: SwitchParameter -Parameter Sets: All Nodes - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The Id or node object to delete - -```yaml -Type: NavigationNodePipeBind -Parameter Sets: Remove a node by ID - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPOrgAssetsLibrary.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPOrgAssetsLibrary.md deleted file mode 100644 index 4a13253b75..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPOrgAssetsLibrary.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnporgassetslibrary -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPOrgAssetsLibrary ---- - -# Remove-PnPOrgAssetsLibrary - -## SYNOPSIS -Removes a given document library as a organizational asset source - -## SYNTAX - -```powershell -Remove-PnPOrgAssetsLibrary -LibraryUrl <String> - [-ShouldRemoveFromCdn <Boolean>] - [-CdnType <SPOTenantCdnType>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes a given document library as a organizational asset source based on its server relative URL in your Sharepoint Online Tenant. It will not remove the document library itself. It may take some time before this change will be reflected in the webinterface. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPOrgAssetsLibrary -LibraryUrl "sites/branding/logos" -``` - -This example removes the document library with the url "logos" residing in the sitecollection with the url "sites/branding/logos" from the list with organizational assets keeping it as an Office 365 CDN source - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPOrgAssetsLibrary -LibraryUrl "sites/branding/logos" -ShouldRemoveFromCdn $true -``` - -This example removes the document library with the url "logos" residing in the sitecollection with the url "sites/branding/logos" from the list with organizational assets also removing it as a Public Office 365 CDN source - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPOrgAssetsLibrary -LibraryUrl "sites/branding/logos" -ShouldRemoveFromCdn $true -CdnType Private -``` - -This example removes the document library with the url "logos" residing in the sitecollection with the url "sites/branding/logos" from the list with organizational assets also removing it as a Private Office 365 CDN source - -## PARAMETERS - -### -CdnType -Indicates what type of Office 365 CDN source the document library that will no longer be flagged as an organizational asset was of - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LibraryUrl -The server relative url of the document library flagged as organizational asset which you want to remove, i.e. "sites/branding/logos" - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ShouldRemoveFromCdn -Boolean indicating if the document library that will no longer be flagged as an organizational asset also needs to be removed as an Office 365 CDN source - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPOrgNewsSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPOrgNewsSite.md deleted file mode 100644 index e1acae3878..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPOrgNewsSite.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnporgnewssite -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPOrgNewsSite ---- - -# Remove-PnPOrgNewsSite - -## SYNOPSIS -Removes a given site from the list of organizational news sites. - -## SYNTAX - -```powershell -Remove-PnPOrgNewsSite -OrgNewsSiteUrl <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes a given site from the list of organizational news sites based on its URL in your Sharepoint Online Tenant. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPOrgNewsSite -OrgNewsSiteUrl https://tenant.sharepoint.com/sites/mysite -``` - -This example removes the specified site from list of organization's news sites. - -## PARAMETERS - -### -OrgNewsSiteUrl -The site to be removed from list of organization's news sites - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPPropertyBagValue.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPPropertyBagValue.md deleted file mode 100644 index 30922d9189..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPPropertyBagValue.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnppropertybagvalue -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPPropertyBagValue ---- - -# Remove-PnPPropertyBagValue - -## SYNOPSIS -Removes a value from the property bag - -## SYNTAX - -```powershell -Remove-PnPPropertyBagValue -Key <String> - [-Folder <String>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPPropertyBagValue -Key MyKey -``` - -This will remove the value with key MyKey from the current web property bag - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPPropertyBagValue -Key MyKey -Folder /MyFolder -``` - -This will remove the value with key MyKey from the folder MyFolder which is located in the root folder of the current web - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPPropertyBagValue -Key MyKey -Folder / -``` - -This will remove the value with key MyKey from the root folder of the current web - -## PARAMETERS - -### -Folder -Site relative url of the folder. See examples for use. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Key -Key of the property bag value to be removed - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPPublishingImageRendition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPPublishingImageRendition.md deleted file mode 100644 index 561f1d891c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPPublishingImageRendition.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnppublishingimagerendition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPPublishingImageRendition ---- - -# Remove-PnPPublishingImageRendition - -## SYNOPSIS -Removes an existing image rendition - -## SYNTAX - -```powershell -Remove-PnPPublishingImageRendition -Identity <ImageRenditionPipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPPublishingImageRendition -Name "MyImageRendition" -Width 800 -Height 600 -``` - - - -## PARAMETERS - -### -Force -If provided, no confirmation will be asked to remove the Image Rendition. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The display name or id of the Image Rendition. - -```yaml -Type: ImageRenditionPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPRoleDefinition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPRoleDefinition.md deleted file mode 100644 index d08e2fc326..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPRoleDefinition.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnproledefinition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPRoleDefinition ---- - -# Remove-PnPRoleDefinition - -## SYNOPSIS -Remove a Role Definition from a site - -## SYNTAX - -```powershell -Remove-PnPRoleDefinition -Identity <RoleDefinitionPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPRoleDefinition -Identity MyRoleDefinition -``` - -Removes the specified Role Definition (Permission Level) from the current site - -## PARAMETERS - -### -Force -Do not ask for confirmation to delete the role definition - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The identity of the role definition, either a RoleDefinition object or a the name of roledefinition - -```yaml -Type: RoleDefinitionPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSearchConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSearchConfiguration.md deleted file mode 100644 index 8cd494f786..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSearchConfiguration.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpsearchconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPSearchConfiguration ---- - -# Remove-PnPSearchConfiguration - -## SYNOPSIS -Remove the search configuration - -## SYNTAX - -### Config -```powershell -Remove-PnPSearchConfiguration -Configuration <String> - [-Scope <SearchConfigurationScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Path -```powershell -Remove-PnPSearchConfiguration -Path <String> - [-Scope <SearchConfigurationScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPSearchConfiguration -Configuration $config -``` - -Remove the search configuration for the current web (does not remove managed property mappings) - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPSearchConfiguration -Configuration $config -Scope Site -``` - -Remove the search configuration for the current site collection (does not remove managed property mappings) - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPSearchConfiguration -Configuration $config -Scope Subscription -``` - -Remove the search configuration for the current tenant (does not remove managed property mappings) - -### ------------------EXAMPLE 4------------------ -```powershell -Remove-PnPSearchConfiguration -Path searchconfig.xml -Scope Subscription -``` - -Reads the search configuration from the specified XML file and remove it for the current tenant (does not remove managed property mappings) - -## PARAMETERS - -### -Configuration -Search configuration string - -```yaml -Type: String -Parameter Sets: Config - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Path -Path to a search configuration - -```yaml -Type: String -Parameter Sets: Path - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope - - -```yaml -Type: SearchConfigurationScope -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteClassification.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteClassification.md deleted file mode 100644 index 01ace42505..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteClassification.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpsiteclassification -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPSiteClassification ---- - -# Remove-PnPSiteClassification - -## SYNOPSIS -Removes one or more existing site classification values from the list of available values. Requires a connection to the Microsoft Graph - -## SYNTAX - -```powershell -Remove-PnPSiteClassification -Classifications <String> - [-Confirm [<SwitchParameter>]] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Remove-PnPSiteClassification -Classifications "HBI" -``` - -Removes the "HBI" site classification from the list of available values. - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Remove-PnPSiteClassification -Classifications "HBI", "Top Secret" -``` - -Removes the "HBI" site classification from the list of available values. - -## PARAMETERS - -### -Classifications - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Confirm -Specifying the Confirm parameter will allow the confirmation question to be skipped - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAdmin.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAdmin.md deleted file mode 100644 index 5cc519f227..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAdmin.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpsitecollectionadmin -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPSiteCollectionAdmin ---- - -# Remove-PnPSiteCollectionAdmin - -## SYNOPSIS -Removes one or more users as site collection administrators from the site collection in the current context - -## SYNTAX - -```powershell -Remove-PnPSiteCollectionAdmin -Owners <UserPipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows removing one to many users as site collection administrators from the site collection in the current context. All existing site collection administrators not included in this command will remain site collection administrator. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPSiteCollectionAdmin -Owners "user@contoso.onmicrosoft.com" -``` - -This will remove user@contoso.onmicrosoft.com as a site collection owner from the site collection in the current context - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPSiteCollectionAdmin -Owners @("user1@contoso.onmicrosoft.com", "user2@contoso.onmicrosoft.com") -``` - -This will remove user1@contoso.onmicrosoft.com and user2@contoso.onmicrosoft.com as site collection owners from the site collection in the current context - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPUser | ? Title -Like "*Doe" | Remove-PnPSiteCollectionAdmin -``` - -This will remove all users with their title ending with "Doe" as site collection owners from the site collection in the current context - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPSiteCollectionAdmin | Remove-PnPSiteCollectionAdmin -``` - -This will remove all existing site collection administrators from the site collection in the current context - -## PARAMETERS - -### -Owners -Specifies owner(s) to remove as site collection administrators. Can be both users and groups. - -```yaml -Type: UserPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAppCatalog.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAppCatalog.md deleted file mode 100644 index cbd1dae795..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteCollectionAppCatalog.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpsitecollectionappcatalog -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPSiteCollectionAppCatalog ---- - -# Remove-PnPSiteCollectionAppCatalog - -## SYNOPSIS -Removes a Site Collection scoped App Catalog from a site - -## SYNTAX - -```powershell -Remove-PnPSiteCollectionAppCatalog -Site <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Notice that this will not remove the App Catalog list and its contents from the site. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPSiteCollectionAppCatalog -Site "https://contoso.sharepoint.com/sites/FinanceTeamsite" -``` - -This will remove a SiteCollection app catalog from the specified site - -## PARAMETERS - -### -Site -Url of the site to remove the app catalog from. - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesign.md deleted file mode 100644 index 70f7aff326..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesign.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpsitedesign -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPSiteDesign ---- - -# Remove-PnPSiteDesign - -## SYNOPSIS -Removes a Site Design - -## SYNTAX - -```powershell -Remove-PnPSiteDesign -Identity <TenantSiteDesignPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPSiteDesign -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -``` - -Removes the specified site design - -## PARAMETERS - -### -Force -If specified you will not be asked to confirm removing the specified Site Design - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the site design to remove - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesignTask.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesignTask.md deleted file mode 100644 index 7edc0984bb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteDesignTask.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpsitedesigntask -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPSiteDesignTask ---- - -# Remove-PnPSiteDesignTask - -## SYNOPSIS -Removes a Site Design Task. If the execution of the associated site script has already started the execution will not be terminated. - -## SYNTAX - -```powershell -Remove-PnPSiteDesignTask -Identity <TenantSiteDesignTaskPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPSiteDesignTask -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -``` - -Removes the specified site design task - -## PARAMETERS - -### -Force -If specified you will not be asked to confirm removing the specified Site Design - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the site design to remove - -```yaml -Type: TenantSiteDesignTaskPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteScript.md deleted file mode 100644 index 93505286c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPSiteScript.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpsitescript -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPSiteScript ---- - -# Remove-PnPSiteScript - -## SYNOPSIS -Removes a Site Script - -## SYNTAX - -```powershell -Remove-PnPSiteScript -Identity <TenantSiteScriptPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPSiteScript -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -``` - -Removes the specified site script - -## PARAMETERS - -### -Force -If specified you will not be asked to confirm removing the specified Site Script - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the Site Script to remove - -```yaml -Type: TenantSiteScriptPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPStorageEntity.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPStorageEntity.md deleted file mode 100644 index 8a09076559..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPStorageEntity.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpstorageentity -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPStorageEntity ---- - -# Remove-PnPStorageEntity - -## SYNOPSIS -Remove Storage Entities / Farm Properties from either the tenant scoped app catalog or the current site collection if the site has a site collection scoped app catalog - -## SYNTAX - -```powershell -Remove-PnPStorageEntity -Key <String> - [-Scope <StorageEntityScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPStorageEntity -Key MyKey -``` - -Removes an existing storage entity / farm property - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPStorageEntity -Key MyKey -Scope Site -``` - -Removes an existing storage entity from the current site collection - -## PARAMETERS - -### -Key -The key of the value to remove. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope -Defines the scope of the storage entity. Defaults to Tenant. - -```yaml -Type: StorageEntityScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPStoredCredential.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPStoredCredential.md deleted file mode 100644 index 266692c3d9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPStoredCredential.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpstoredcredential -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPStoredCredential ---- - -# Remove-PnPStoredCredential - -## SYNOPSIS -Removes a credential - -## SYNTAX - -```powershell -Remove-PnPStoredCredential -Name <String> - [-Force [<SwitchParameter>]] -``` - -## DESCRIPTION -Removes a stored credential from the Windows Credential Manager - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPStoredCredential -Name https://tenant.sharepoint.com -``` - -Removes the specified credential from the Windows Credential Manager - -## PARAMETERS - -### -Force -If specified you will not be asked for confirmation - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -The credential to remove - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTaxonomyItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTaxonomyItem.md deleted file mode 100644 index ccaabd17f0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTaxonomyItem.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnptaxonomyitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPTaxonomyItem ---- - -# Remove-PnPTaxonomyItem - -## SYNOPSIS -Removes a taxonomy item - -## SYNTAX - -```powershell -Remove-PnPTaxonomyItem -TermPath <String> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Force - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TermPath -The path, delimited by | of the taxonomy item to remove, alike GROUPLABEL|TERMSETLABEL|TERMLABEL - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Term - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantCdnOrigin.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantCdnOrigin.md deleted file mode 100644 index 492ac7a6b3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantCdnOrigin.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnptenantcdnorigin -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPTenantCdnOrigin ---- - -# Remove-PnPTenantCdnOrigin - -## SYNOPSIS -Removes an origin from the Public or Private content delivery network (CDN). - -## SYNTAX - -```powershell -Remove-PnPTenantCdnOrigin -OriginUrl <String> - -CdnType <SPOTenantCdnType> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes an origin from the Public or Private content delivery network (CDN). - -You must be a SharePoint Online global administrator to run the cmdlet. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPTenantCdnOrigin -OriginUrl /sites/site/subfolder -CdnType Public -``` - -This example removes the specified origin from the public CDN - -## PARAMETERS - -### -CdnType -The cdn type to remove the origin from. - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -OriginUrl -The origin to remove. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantSite.md deleted file mode 100644 index 175d655267..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantSite.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnptenantsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPTenantSite ---- - -# Remove-PnPTenantSite - -## SYNOPSIS -Removes a site collection - -## SYNTAX - -```powershell -Remove-PnPTenantSite -Url <String> - [-SkipRecycleBin [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes a site collection which is listed in your tenant administration site. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPTenantSite -Url https://tenant.sharepoint.com/sites/contoso -``` - -This will remove the site collection with the url 'https://tenant.sharepoint.com/sites/contoso' and put it in the recycle bin. - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPTenantSite -Url https://tenant.sharepoint.com/sites/contoso -Force -SkipRecycleBin -``` - -This will remove the site collection with the url 'https://tenant.sharepoint.com/sites/contoso' with force and it will skip the recycle bin. - -### ------------------EXAMPLE 3------------------ -```powershell -Remove-PnPTenantSite -Url https://tenant.sharepoint.com/sites/contoso -FromRecycleBin -``` - -This will remove the site collection with the url 'https://tenant.sharepoint.com/sites/contoso' from the recycle bin. - -## PARAMETERS - -### -Force -Do not ask for confirmation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SkipRecycleBin -Do not add to the tenant scoped recycle bin when selected. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: SkipTrash - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -Specifies the full URL of the site collection that needs to be deleted - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantTheme.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantTheme.md deleted file mode 100644 index 6c06966127..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTenantTheme.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnptenanttheme -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPTenantTheme ---- - -# Remove-PnPTenantTheme - -## SYNOPSIS -Removes a theme - -## SYNTAX - -```powershell -Remove-PnPTenantTheme -Identity <ThemePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes the specified theme from the tenant configuration - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPTenantTheme -Name "MyCompanyTheme" -``` - -Removes the specified theme. - -## PARAMETERS - -### -Identity -The name of the theme to retrieve - -```yaml -Type: ThemePipeBind -Parameter Sets: (All) -Aliases: Name - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTermGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTermGroup.md deleted file mode 100644 index d371619de8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPTermGroup.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnptermgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPTermGroup ---- - -# Remove-PnPTermGroup - -## SYNOPSIS -Removes a taxonomy term group and all its containing termsets - -## SYNTAX - -```powershell -Remove-PnPTermGroup -GroupName <String> - [-TermStoreName <String>] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Force - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -GroupName -Name of the taxonomy term group to delete. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TermStoreName -Term store to use; if not specified the default term store is used. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUnifiedGroup.md deleted file mode 100644 index 18686d1aaa..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUnifiedGroup.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpunifiedgroup -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPUnifiedGroup ---- - -# Remove-PnPUnifiedGroup - -## SYNOPSIS -Removes one Office 365 Group (aka Unified Group). Requires the Azure Active Directory application permission 'Group.ReadWrite.All'. - -## SYNTAX - -```powershell -Remove-PnPUnifiedGroup -Identity <UnifiedGroupPipeBind> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPUnifiedGroup -Identity $groupId -``` - -Removes an Office 365 Group based on its ID - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPUnifiedGroup -Identity $group -``` - -Removes the provided Office 365 Group - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPUnifiedGroup | ? Visibility -eq "Public" | Remove-PnPUnifiedGroup -``` - -Removes all the public Office 365 Groups - -## PARAMETERS - -### -Identity -The Identity of the Office 365 Group - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUser.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUser.md deleted file mode 100644 index 1c54b39207..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUser.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpuser -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPUser ---- - -# Remove-PnPUser - -## SYNOPSIS -Removes a specific user from the site collection User Information List - -## SYNTAX - -```powershell -Remove-PnPUser -Identity <UserPipeBind> - [-Force [<SwitchParameter>]] - [-Confirm [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command will allow the removal of a specific user from the User Information List - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPUser -Identity 23 -``` - -Remove the user with Id 23 from the User Information List of the current site collection - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPUser -Identity i:0#.f|membership|user@tenant.onmicrosoft.com -``` - -Remove the user with LoginName i:0#.f|membership|user@tenant.onmicrosoft.com from the User Information List of the current site collection - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPUser | ? Email -eq "user@tenant.onmicrosoft.com" | Remove-PnPUser -``` - -Remove the user with e-mail address user@tenant.onmicrosoft.com from the User Information List of the current site collection - -### ------------------EXAMPLE 4------------------ -```powershell -Remove-PnPUser -Identity i:0#.f|membership|user@tenant.onmicrosoft.com -Confirm:$false -``` - -Remove the user with LoginName i:0#.f|membership|user@tenant.onmicrosoft.com from the User Information List of the current site collection without asking to confirm the removal first - -## PARAMETERS - -### -Confirm -Specifying the Confirm parameter will allow the confirmation question to be skipped - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Force -Specifying the Force parameter will skip the confirmation question - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -User ID or login name - -```yaml -Type: UserPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.User - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUserFromGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUserFromGroup.md deleted file mode 100644 index d842eeeb80..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPUserFromGroup.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpuserfromgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPUserFromGroup ---- - -# Remove-PnPUserFromGroup - -## SYNOPSIS -Removes a user from a group - -## SYNTAX - -```powershell -Remove-PnPUserFromGroup -LoginName <String> - -Identity <GroupPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPUserFromGroup -LoginName user@company.com -GroupName 'Marketing Site Members' -``` - -Removes the user user@company.com from the Group 'Marketing Site Members' - -## PARAMETERS - -### -Identity -A group object, an ID or a name of a group - -```yaml -Type: GroupPipeBind -Parameter Sets: (All) -Aliases: GroupName - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -LoginName -A valid login name of a user (user@company.com) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: LogonName - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPView.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPView.md deleted file mode 100644 index 6f785447d8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPView.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpview -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPView ---- - -# Remove-PnPView - -## SYNOPSIS -Deletes a view from a list - -## SYNTAX - -```powershell -Remove-PnPView -Identity <ViewPipeBind> - -List <ListPipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPView -List "Demo List" -Identity "All Items" -``` - -Removes the view with title "All Items" from the "Demo List" list. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID or Title of the view. - -```yaml -Type: ViewPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -List -The ID or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWeb.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWeb.md deleted file mode 100644 index af35e46ea8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWeb.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpweb -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPWeb ---- - -# Remove-PnPWeb - -## SYNOPSIS -Removes a subweb in the current web - -## SYNTAX - -### ByUrl -```powershell -Remove-PnPWeb -Url <String> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### ByIdentity -```powershell -Remove-PnPWeb -Identity <WebPipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPWeb -Url projectA -``` - -Remove a web - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPWeb -Identity 5fecaf67-6b9e-4691-a0ff-518fc9839aa0 -``` - -Remove a web specified by its ID - -### ------------------EXAMPLE 3------------------ -```powershell -Get-PnPSubWebs | Remove-PnPWeb -Force -``` - -Remove all subwebs and do not ask for confirmation - -## PARAMETERS - -### -Force -Do not ask for confirmation to delete the subweb - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Identity/Id/Web object to delete - -```yaml -Type: WebPipeBind -Parameter Sets: ByIdentity - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Url -The site relative url of the web, e.g. 'Subweb1' - -```yaml -Type: String -Parameter Sets: ByUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWebPart.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWebPart.md deleted file mode 100644 index 2996f783f6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWebPart.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpwebpart -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPWebPart ---- - -# Remove-PnPWebPart - -## SYNOPSIS -Removes a web part from a page - -## SYNTAX - -### ID -```powershell -Remove-PnPWebPart -Identity <GuidPipeBind> - -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### NAME -```powershell -Remove-PnPWebPart -Title <String> - -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPWebPart -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -Identity a2875399-d6ff-43a0-96da-be6ae5875f82 -``` - -This will remove the web part specified by ID to the specified page in the first row and the first column of the HTML table present on the page - -### ------------------EXAMPLE 2------------------ -```powershell -Remove-PnPWebPart -ServerRelativePageUrl "/sites/demo/sitepages/home.aspx" -Title MyWebpart -``` - -This will remove the web part specified by title to the specified page in the first row and the first column of the HTML table present on the page - -## PARAMETERS - -### -Identity -The Guid of the web part - -```yaml -Type: GuidPipeBind -Parameter Sets: ID - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -Server relative url of the web part page, e.g. /sites/demo/sitepages/home.aspx - -```yaml -Type: String -Parameter Sets: __AllParameterSets -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -The name of the web part - -```yaml -Type: String -Parameter Sets: NAME -Aliases: Name - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWebhookSubscription.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWebhookSubscription.md deleted file mode 100644 index 53ffc2ed46..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWebhookSubscription.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpwebhooksubscription -applicable: SharePoint Online -schema: 2.0.0 -title: Remove-PnPWebhookSubscription ---- - -# Remove-PnPWebhookSubscription - -## SYNOPSIS -Removes a Webhook subscription from the resource - -## SYNTAX - -```powershell -Remove-PnPWebhookSubscription -Identity <WebhookSubscriptionPipeBind> - [-List <ListPipeBind>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPWebhookSubscription -List MyList -Identity ea1533a8-ff03-415b-a7b6-517ee50db8b6 -``` - -Removes the Webhook subscription with the specified id from the list MyList - -### ------------------EXAMPLE 2------------------ -```powershell -$subscriptions = Get-PnPWebhookSubscriptions -List MyList -Remove-PnPWebhookSubscription -Identity $subscriptions[0] -List MyList -``` - -Removes the first Webhook subscription from the list MyList - -### ------------------EXAMPLE 3------------------ -```powershell -$subscriptions = Get-PnPWebhookSubscriptions -List MyList -$subscriptions[0] | Remove-PnPWebhookSubscription -List MyList -``` - -Removes the first Webhook subscription from the list MyList - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The identity of the Webhook subscription to remove - -```yaml -Type: WebhookSubscriptionPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -List -The list object or name which the Webhook subscription will be removed from - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.Entities.WebhookSubscription - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWikiPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWikiPage.md deleted file mode 100644 index 4c7b29620a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWikiPage.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpwikipage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPWikiPage ---- - -# Remove-PnPWikiPage - -## SYNOPSIS -Removes a wiki page - -## SYNTAX - -### SERVER -```powershell -Remove-PnPWikiPage -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### SITE -```powershell -Remove-PnPWikiPage -SiteRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPWikiPage -PageUrl '/pages/wikipage.aspx' -``` - -Removes the page '/pages/wikipage.aspx' - -## PARAMETERS - -### -ServerRelativePageUrl - - -```yaml -Type: String -Parameter Sets: SERVER -Aliases: PageUrl - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SiteRelativePageUrl - - -```yaml -Type: String -Parameter Sets: SITE - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowDefinition.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowDefinition.md deleted file mode 100644 index d5b7d919ae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowDefinition.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpworkflowdefinition -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPWorkflowDefinition ---- - -# Remove-PnPWorkflowDefinition - -## SYNOPSIS -Removes a workflow definition - -## SYNTAX - -```powershell -Remove-PnPWorkflowDefinition -Identity <WorkflowDefinitionPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPWorkflowDefinition -Identity $wfDef -``` - -Removes the workflow, retrieved by Get-PnPWorkflowDefinition, from the site. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWorkflowDefinition -Name MyWorkflow | Remove-PnPWorkflowDefinition -``` - -Get the workflow MyWorkFlow and remove from the site. - -## PARAMETERS - -### -Identity -The definition to remove - -```yaml -Type: WorkflowDefinitionPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowSubscription.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowSubscription.md deleted file mode 100644 index d1ab1a9a9f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWorkflowSubscription.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/remove-pnpworkflowsubscription -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Remove-PnPWorkflowSubscription ---- - -# Remove-PnPWorkflowSubscription - -## SYNOPSIS -Remove workflow subscription - -## SYNTAX - -```powershell -Remove-PnPWorkflowSubscription -Identity <WorkflowSubscriptionPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes a previously registered workflow subscription - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Remove-PnPWorkflowSubscription -identity $wfSub -``` - -Removes the workflowsubscription, retrieved by Get-PnPWorkflowSubscription. - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPWorkflowSubscription -Name MyWorkflow | Remove-PnPWorkflowSubscription -``` - -Get the workflowSubscription MyWorkFlow and remove it. - -## PARAMETERS - -### -Identity -The subscription to remove - -```yaml -Type: WorkflowSubscriptionPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Rename-PnPFile.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Rename-PnPFile.md deleted file mode 100644 index 79ff928d99..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Rename-PnPFile.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/rename-pnpfile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Rename-PnPFile ---- - -# Rename-PnPFile - -## SYNOPSIS -Renames a file in its current location - -## SYNTAX - -### SERVER -```powershell -Rename-PnPFile -ServerRelativeUrl <String> - -TargetFileName <String> - [-OverwriteIfAlreadyExists [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### SITE -```powershell -Rename-PnPFile -SiteRelativeUrl <String> - -TargetFileName <String> - [-OverwriteIfAlreadyExists [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -PS:>Rename-PnPFile -ServerRelativeUrl /sites/project/Documents/company.docx -TargetFileName mycompany.docx -``` - -Renames a file named company.docx located in the document library called Documents located in the projects sitecollection under the managed path sites to mycompany.docx. If a file named mycompany.aspx already exists, it won't perform the rename. - -### ------------------EXAMPLE 2------------------ -```powershell -PS:>Rename-PnPFile -SiteRelativeUrl Documents/company.aspx -TargetFileName mycompany.docx -``` - -Renames a file named company.docx located in the document library called Documents located in the current site to mycompany.aspx. If a file named mycompany.aspx already exists, it won't perform the rename. - -### ------------------EXAMPLE 3------------------ -```powershell -PS:>Rename-PnPFile -ServerRelativeUrl /sites/project/Documents/company.docx -TargetFileName mycompany.docx -OverwriteIfAlreadyExists -``` - -Renames a file named company.docx located in the document library called Documents located in the projects sitecollection under the managed path sites to mycompany.aspx. If a file named mycompany.aspx already exists, it will still perform the rename and replace the original mycompany.aspx file. - -## PARAMETERS - -### -Force -If provided, no confirmation will be requested and the action will be performed - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OverwriteIfAlreadyExists -If provided, if a file already exist with the provided TargetFileName, it will be overwritten. If omitted, the rename operation will be canceled if a file already exists with the TargetFileName file name. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativeUrl -Server relative Url specifying the file to rename. Must include the file name. - -```yaml -Type: String -Parameter Sets: SERVER - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SiteRelativeUrl -Site relative Url specifying the file to rename. Must include the file name. - -```yaml -Type: String -Parameter Sets: SITE - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TargetFileName -File name to rename the file to. Should only be the file name and not include the path to its location. Use Move-PnPFile to move the file to another location. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Rename-PnPFolder.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Rename-PnPFolder.md deleted file mode 100644 index 89f6c93dd1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Rename-PnPFolder.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/rename-pnpfolder -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Rename-PnPFolder ---- - -# Rename-PnPFolder - -## SYNOPSIS -Renames a folder - -## SYNTAX - -```powershell -Rename-PnPFolder -Folder <String> - -TargetFolderName <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Rename-PnPFolder -Folder Documents/Reports -TargetFolderName 'Archived Reports' -``` - -This will rename the folder Reports in the Documents library to 'Archived Reports' - -## PARAMETERS - -### -Folder -The folder to rename - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TargetFolderName -The new folder name - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPAccessToken.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPAccessToken.md deleted file mode 100644 index adbfe7681f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPAccessToken.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/request-pnpaccesstoken -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Request-PnPAccessToken ---- - -# Request-PnPAccessToken - -## SYNOPSIS -Requests an OAuth Access token - -## SYNTAX - -```powershell -Request-PnPAccessToken [-ClientId <String>] - [-Resource <String>] - [-Scopes <String>] - [-Decoded [<SwitchParameter>]] - [-SetAsCurrent [<SwitchParameter>]] - [-Credentials <PSCredential>] - [-TenantUrl <String>] -``` - -## DESCRIPTION -Returns an access token using the password grant, using the PnP O365 Management Shell client id by default and the AllSites.FullControl scope by default. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Request-PnPAccessToken -``` - -Returns the access token using the default client id and scope - -### ------------------EXAMPLE 2------------------ -```powershell -Request-PnPAccessToken -ClientId 26e29fec-aa10-4f99-8381-d96cddc650c2 -``` - -Returns the access token using the specified client id and the default scope of AllSites.FullControl - -### ------------------EXAMPLE 3------------------ -```powershell -Request-PnPAccessToken -ClientId 26e29fec-aa10-4f99-8381-d96cddc650c2 -Scopes Group.ReadWrite.All -``` - -Returns the access token using the specified client id and the specified scope - -### ------------------EXAMPLE 4------------------ -```powershell -Request-PnPAccessToken -ClientId 26e29fec-aa10-4f99-8381-d96cddc650c2 -Scopes Group.ReadWrite.All, AllSites.FullControl -``` - -Returns the access token using the specified client id and the specified scopes - -### ------------------EXAMPLE 5------------------ -```powershell -$token = Request-PnPAccessToken -ClientId 26e29fec-aa10-4f99-8381-d96cddc650c2 -Resource https://contoso.sharepoint.com -Credentials (Get-Credential) -TenantUrl https://contoso.sharepoint.com - Connect-PnPOnline -AccessToken $token -``` - -Returns the access token using the specified client id and the specified scopes while using the credentials and tenanturl specified to authentication against Azure AD - -## PARAMETERS - -### -ClientId -The Azure Application Client Id to use to retrieve the token. Defaults to the PnP Office 365 Management Shell - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Credentials -Optional credentials to use when retrieving the access token. If not present you need to connect first with Connect-PnPOnline. - -Only applicable to: SharePoint Online - -```yaml -Type: PSCredential -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Decoded -Returns the token in a decoded / human readible manner - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Resource -The scopes to retrieve the token for. Defaults to AllSites.FullControl - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scopes -The scopes to retrieve the token for. Defaults to AllSites.FullControl - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SetAsCurrent -Set this token as the current token to use when performing Azure AD based authentication requests with PnP PowerShell - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TenantUrl -Optional tenant URL to use when retrieving the access token. The Url should be in the shape of https://yourtenant.sharepoint.com. See examples for more info. - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPReIndexList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPReIndexList.md deleted file mode 100644 index 2002111ac3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPReIndexList.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/request-pnpreindexlist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Request-PnPReIndexList ---- - -# Request-PnPReIndexList - -## SYNOPSIS -Marks the list for full indexing during the next incremental crawl - -## SYNTAX - -```powershell -Request-PnPReIndexList -Identity <ListPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Request-PnPReIndexList -Identity "Demo List" -``` - - - -## PARAMETERS - -### -Identity -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPReIndexWeb.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPReIndexWeb.md deleted file mode 100644 index 85a43d7b38..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Request-PnPReIndexWeb.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/request-pnpreindexweb -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Request-PnPReIndexWeb ---- - -# Request-PnPReIndexWeb - -## SYNOPSIS -Marks the web for full indexing during the next incremental crawl - -## SYNTAX - -```powershell -Request-PnPReIndexWeb [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Reset-PnPFileVersion.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Reset-PnPFileVersion.md deleted file mode 100644 index 8dc0aa83e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Reset-PnPFileVersion.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/reset-pnpfileversion -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Reset-PnPFileVersion ---- - -# Reset-PnPFileVersion - -## SYNOPSIS -Resets a file to its previous version - -## SYNTAX - -```powershell -Reset-PnPFileVersion -ServerRelativeUrl <String> - [-CheckinType <CheckinType>] - [-CheckInComment <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Reset-PnPFileVersion -ServerRelativeUrl "/sites/test/office365.png" -``` - - - -### ------------------EXAMPLE 2------------------ -```powershell -Reset-PnPFileVersion -ServerRelativeUrl "/sites/test/office365.png" -CheckinType MajorCheckin -Comment "Restored to previous version" -``` - - - -## PARAMETERS - -### -CheckInComment -The comment added to the checkin. Defaults to 'Restored to previous version'. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CheckinType -The check in type to use. Defaults to Major. - -```yaml -Type: CheckinType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativeUrl -The server relative URL of the file. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Reset-PnPLabel.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Reset-PnPLabel.md deleted file mode 100644 index ccc6ed1fca..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Reset-PnPLabel.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/reset-pnplabel -applicable: SharePoint Online -schema: 2.0.0 -title: Reset-PnPLabel ---- - -# Reset-PnPLabel - -## SYNOPSIS -Resets a label/tag on the specified list or library to None - -## SYNTAX - -```powershell -Reset-PnPLabel -List <ListPipeBind> - [-SyncToItems <Boolean>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Reset-PnPLabel -List "Demo List" -``` - -This resets an O365 label on the specified list or library to None - -### ------------------EXAMPLE 2------------------ -```powershell -Reset-PnPLabel -List "Demo List" -SyncToItems $true -``` - -This resets an O365 label on the specified list or library to None and resets the label on all the items in the list and library except Folders and where the label has been manually or previously automatically assigned - -## PARAMETERS - -### -List -The ID or Url of the list - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SyncToItems -Reset label on existing items in the library - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Resolve-PnPFolder.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Resolve-PnPFolder.md deleted file mode 100644 index 8cc1817a68..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Resolve-PnPFolder.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/resolve-pnpfolder -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Resolve-PnPFolder ---- - -# Resolve-PnPFolder - -## SYNOPSIS -Returns a folder from a given site relative path, and will create it if it does not exist. - -## SYNTAX - -### -```powershell -Resolve-PnPFolder -SiteRelativePath <String> - [-Includes <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Returns a folder from a given site relative path, and will create it if it does not exist. If you do not want the folder to be created, for instance just to test if a folder exists, use Get-PnPFolder - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Resolve-PnPFolder -SiteRelativePath "demofolder/subfolder" -``` - -Creates a folder called subfolder in a folder called demofolder located in the root folder of the site. If the folder hierarchy does not exist, it will be created. - -## PARAMETERS - -### -Includes -Specify properties to include when retrieving objects from the server. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -SiteRelativePath -Site Relative Folder Path - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Web -The web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Folder - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Get-PnPFolder](https://github.com/OfficeDev/PnP-PowerShell/blob/master/Documentation/GetPnPFolder.md) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnPDeletedUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnPDeletedUnifiedGroup.md deleted file mode 100644 index 52f2f1e95c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnPDeletedUnifiedGroup.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/restore-pnpdeletedunifiedgroup -applicable: SharePoint Online -schema: 2.0.0 -title: Restore-PnPDeletedUnifiedGroup ---- - -# Restore-PnPDeletedUnifiedGroup - -## SYNOPSIS -Restores one deleted Office 365 Group (aka Unified Group) - -## SYNTAX - -```powershell -Restore-PnPDeletedUnifiedGroup -Identity <UnifiedGroupPipeBind> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Restore-PnPDeletedUnifiedGroup -Identity 38b32e13-e900-4d95-b860-fb52bc07ca7f -``` - -Restores a deleted Office 365 Group based on its ID - -### ------------------EXAMPLE 2------------------ -```powershell -$group = Get-PnPDeletedUnifiedGroup -Identity 38b32e13-e900-4d95-b860-fb52bc07ca7f -Restore-PnPDeletedUnifiedGroup -Identity $group -``` - -Restores the provided deleted Office 365 Group - -## PARAMETERS - -### -Identity -The Identity of the deleted Office 365 Group - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnPTenantRecycleBinItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnPTenantRecycleBinItem.md deleted file mode 100644 index d0e676070a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnPTenantRecycleBinItem.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/restore-pnptenantrecyclebinitem -applicable: SharePoint Online -schema: 2.0.0 -title: Restore-PnPTenantRecycleBinItem ---- - -# Restore-PnPTenantRecycleBinItem - -## SYNOPSIS -Restores a site collection from the tenant scoped recycle bin - -## SYNTAX - -```powershell -Restore-PnPTenantRecycleBinItem -Url <String> - [-Wait [<SwitchParameter>]] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -The Restore-PnPTenantRecycleBinItem cmdlet allows a site collection that has been deleted and still exists in the tenant recycle bin to be restored to its original location. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Restore-PnPTenantRecycleBinItem -Url https://tenant.sharepoint.com/sites/contoso -``` - -This will restore the deleted site collection with the url 'https://tenant.sharepoint.com/sites/contoso' to its original location - -### ------------------EXAMPLE 2------------------ -```powershell -Restore-PnPTenantRecycleBinItem -Url https://tenant.sharepoint.com/sites/contoso -Wait -``` - -This will restore the deleted site collection with the url 'https://tenant.sharepoint.com/sites/contoso' to its original location and will wait with executing further PowerShell commands until the site collection restore has completed - -## PARAMETERS - -### -Force -If provided, no confirmation will be asked to restore the site collection from the tenant recycle bin - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -Url of the site collection to restore from the tenant recycle bin - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Wait -If provided, the PowerShell execution will halt until the site restore process has completed - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnpRecycleBinItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnpRecycleBinItem.md deleted file mode 100644 index 5aeb81e879..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnpRecycleBinItem.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/restore-pnprecyclebinitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Restore-PnPRecycleBinItem ---- - -# Restore-PnPRecycleBinItem - -## SYNOPSIS -Restores the provided recycle bin item to its original location - -## SYNTAX - -### Identity -```powershell -Restore-PnPRecycleBinItem -Identity <RecycleBinItemPipeBind> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### All -```powershell -Restore-PnPRecycleBinItem -All [<SwitchParameter>] - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Restore-PnpRecycleBinItem -Identity 72e4d749-d750-4989-b727-523d6726e442 -``` - -Restores the recycle bin item with Id 72e4d749-d750-4989-b727-523d6726e442 to its original location - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPRecycleBinItem | ? -Property LeafName -like "*.docx" | Restore-PnpRecycleBinItem -``` - -Restores all the items in the first and second stage recycle bins to their original location of which the filename ends with the .docx extension - -## PARAMETERS - -### -All -If provided all items will be stored - -```yaml -Type: SwitchParameter -Parameter Sets: All - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Force -If provided, no confirmation will be asked to restore the recycle bin item - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Id of the recycle bin item or the recycle bin item object itself to restore - -```yaml -Type: RecycleBinItemPipeBind -Parameter Sets: Identity - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Resume-PnPWorkflowInstance.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Resume-PnPWorkflowInstance.md deleted file mode 100644 index 58819616dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Resume-PnPWorkflowInstance.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/resume-pnpworkflowinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Resume-PnPWorkflowInstance ---- - -# Resume-PnPWorkflowInstance - -## SYNOPSIS -Resume a workflow - -## SYNTAX - -```powershell -Resume-PnPWorkflowInstance -Identity <WorkflowInstancePipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Resumes a previously stopped workflow instance - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Resume-PnPWorkflowInstance -identity $wfInstance -``` - -Resumes the workflow instance, this can be the Guid of the instance or the instance itself. - -## PARAMETERS - -### -Identity -The instance to resume - -```yaml -Type: WorkflowInstancePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPHubSiteRights.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPHubSiteRights.md deleted file mode 100644 index 86de2a0f58..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPHubSiteRights.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/revoke-pnphubsiterights -applicable: SharePoint Online -schema: 2.0.0 -title: Revoke-PnPHubSiteRights ---- - -# Revoke-PnPHubSiteRights - -## SYNOPSIS -Revoke permissions to the permissions already in place to associate sites to Hub Sites for one or more specific users - -## SYNTAX - -```powershell -Revoke-PnPHubSiteRights [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Revoke-PnPHubSiteRights -Identity https://contoso.sharepoint.com/sites/hubsite -Principals "myuser@mydomain.com","myotheruser@mydomain.com" -``` - -This example shows how to revoke the rights of myuser and myotheruser to associate their sites with the provided Hub Site - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPSiteDesignRights.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPSiteDesignRights.md deleted file mode 100644 index 6538161365..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPSiteDesignRights.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/revoke-pnpsitedesignrights -applicable: SharePoint Online -schema: 2.0.0 -title: Revoke-PnPSiteDesignRights ---- - -# Revoke-PnPSiteDesignRights - -## SYNOPSIS -Revokes the specified principals rights to use the site design. - -## SYNTAX - -```powershell -Revoke-PnPSiteDesignRights -Identity <TenantSiteDesignPipeBind> - -Principals <String[]> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Revoke-PnPSiteDesignRights -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd -Principals "myuser@mydomain.com","myotheruser@mydomain.com" -``` - -Revokes rights to the specified principals on the site design specified - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPSiteDesign -Identity 5c73382d-9643-4aa0-9160-d0cba35e40fd | Revoke-PnPSiteDesignRights -Principals "myuser@mydomain.com","myotheruser@mydomain.com" -``` - -Revokes rights to the specified principals on the site design specified - -## PARAMETERS - -### -Identity -The site design to use. - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Principals -One or more principals to revoke. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPTenantServicePrincipalPermission.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPTenantServicePrincipalPermission.md deleted file mode 100644 index c4bb7bbea2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Revoke-PnPTenantServicePrincipalPermission.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/revoke-pnptenantserviceprincipalpermission -applicable: SharePoint Online -schema: 2.0.0 -title: Revoke-PnPTenantServicePrincipalPermission ---- - -# Revoke-PnPTenantServicePrincipalPermission - -## SYNOPSIS -Revokes a permission that was previously granted to the "SharePoint Online Client" service principal. - -## SYNTAX - -```powershell -Revoke-PnPTenantServicePrincipalPermission -ObjectId <String> - [-Force [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Revokes a permission that was previously granted to the "SharePoint Online Client" service principal. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ObjectId - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPClientSidePageConversionLog.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPClientSidePageConversionLog.md deleted file mode 100644 index af99acb343..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPClientSidePageConversionLog.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/save-pnpclientsidepageconversionlog -applicable: SharePoint Online -schema: 2.0.0 -title: Save-PnPClientSidePageConversionLog ---- - -# Save-PnPClientSidePageConversionLog - -## SYNOPSIS -Persists the current client side page conversion log data to the loggers linked to the last used page transformation run. Needs to be used in conjunction with the -LogSkipFlush flag on the ConvertTo-PnPClientSidePage cmdlet - -## SYNTAX - -```powershell -Save-PnPClientSidePageConversionLog [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Save-PnPClientSidePageConversionLog -``` - -Persists the current client side page conversion log data to the loggers linked to the last used page transformation run. Needs to be used in conjunction with the -LogSkipFlush flag on the ConvertTo-PnPClientSidePage cmdlet - -## PARAMETERS - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPProvisioningTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPProvisioningTemplate.md deleted file mode 100644 index c3b3fc4c94..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPProvisioningTemplate.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/save-pnpprovisioningtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Save-PnPProvisioningTemplate ---- - -# Save-PnPProvisioningTemplate - -## SYNOPSIS -Saves a PnP site template to the file system - -## SYNTAX - -```powershell -Save-PnPProvisioningTemplate -Template <ProvisioningTemplatePipeBind> - -Out <String> - [-Schema <XMLPnPSchemaVersion>] - [-Force [<SwitchParameter>]] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Save-PnPProvisioningTemplate -Template .\template.xml -Out .\template.pnp -``` - -Saves a PnP provisioning template to the file system as a PnP file. - -### ------------------EXAMPLE 2------------------ -```powershell -$template = Read-PnPProvisioningTemplate -Path template.xml -Save-PnPProvisioningTemplate -Template $template -Out .\template.pnp -``` - -Saves a PnP site template to the file system as a PnP file. The schema used will the latest released schema when creating the PnP file regardless of the original schema - -### ------------------EXAMPLE 3------------------ -```powershell -$template = Read-PnPProvisioningTemplate -Path template.xml -Save-PnPProvisioningTemplate -Template $template -Out .\template.pnp -Schema V202002 -``` - -Saves a PnP site template to the file system as a PnP file and converts the template in the PnP file to the specified schema. - -### ------------------EXAMPLE 4------------------ -```powershell -Read-PnPProvisioningTemplate -Path template.xml | Save-PnPProvisioningTemplate -Out .\template.pnp -``` - -Saves a PnP site template to the file system as a PnP file. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Schema -The optional schema to use when creating the PnP file. Always defaults to the latest schema. - -```yaml -Type: XMLPnPSchemaVersion -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Template -Allows you to provide an in-memory instance of the ProvisioningTemplate type of the PnP Core Component. When using this parameter, the -Out parameter refers to the path for saving the template and storing any supporting file for the template. - -```yaml -Type: ProvisioningTemplatePipeBind -Parameter Sets: (All) -Aliases: InputInstance - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -TemplateProviderExtensions -Allows you to specify the ITemplateProviderExtension to execute while saving a template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPTenantTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPTenantTemplate.md deleted file mode 100644 index 824b8f3a86..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPTenantTemplate.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/save-pnptenanttemplate -applicable: SharePoint Online -schema: 2.0.0 -title: Save-PnPTenantTemplate ---- - -# Save-PnPTenantTemplate - -## SYNOPSIS -Saves a PnP provisioning hierarchy to the file system - -## SYNTAX - -```powershell -Save-PnPTenantTemplate -Template <ProvisioningHierarchyPipeBind> - -Out <String> - [-Schema <XMLPnPSchemaVersion>] - [-Force [<SwitchParameter>]] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Save-PnPTenantTemplate -Template template.xml -Out .\tenanttemplate.pnp -``` - -Saves a PnP tenant template to the file system - -### ------------------EXAMPLE 2------------------ -```powershell -$template = Read-PnPTenantTemplate -Path template.xml -Save-PnPTenantTemplate -Template $template -Out .\template.pnp -``` - -Saves a PnP tenant template to the file system as a PnP file. The schema used will the latest released schema when creating the PnP file regardless of the original schema - -### ------------------EXAMPLE 3------------------ -```powershell -$template = Read-PnPTenantTemplate -Path template.xml -Save-PnPTenantTemplate -Template $template -Out .\template.pnp -Schema V202002 -``` - -Saves a PnP tenant template to the file system as a PnP file and converts the template in the PnP file to the specified schema. - -### ------------------EXAMPLE 4------------------ -```powershell -Read-PnPTenantTemplate -Path template.xml | Save-PnPTenantTemplate -Out .\template.pnp -``` - -Saves a PnP tenant template to the file system as a PnP file. - -## PARAMETERS - -### -Force -Specifying the Force parameter will skip the confirmation question. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Out -Filename to write to, optionally including full path. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Schema -The optional schema to use when creating the PnP file. Always defaults to the latest schema. - -```yaml -Type: XMLPnPSchemaVersion -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Template -Allows you to provide an in-memory instance of a Tenant Template or a filename of a template file in XML format. When using this parameter, the -Out parameter refers to the path for saving the template and storing any supporting file for the template. - -```yaml -Type: ProvisioningHierarchyPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Send-PnPMail.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Send-PnPMail.md deleted file mode 100644 index 710e5e18e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Send-PnPMail.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/send-pnpmail -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Send-PnPMail ---- - -# Send-PnPMail - -## SYNOPSIS -Sends an email using the Office 365 SMTP Service or SharePoint, depending on the parameters specified. See detailed help for more information. - -## SYNTAX - -```powershell -Send-PnPMail -To <String[]> - -Subject <String> - -Body <String> - [-Server <String>] - [-From <String>] - [-Password <String>] - [-Cc <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Send-PnPMail -To address@tenant.sharepointonline.com -Subject test -Body test -``` - -Sends an e-mail using the SharePoint SendEmail method using the current context. E-mail is sent from the system account and can only be sent to accounts in the same tenant - -### ------------------EXAMPLE 2------------------ -```powershell -Send-PnPMail -To address@contoso.com -Subject test -Body test -From me@tenant.onmicrosoft.com -Password xyz -``` - -Sends an e-mail via Office 365 SMTP and requires a from address and password. E-mail is sent from the from user and can be sent to both internal and external addresses. - -### ------------------EXAMPLE 3------------------ -```powershell -Send-PnPMail -To address@contoso.com -Subject test -Body test -From me@server.net -Password xyz -Server yoursmtp.server.net -``` - -Sends an e-mail via a custom SMTP server and requires a from address and password. E-mail is sent from the from user. - -## PARAMETERS - -### -Body -Body of the email - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Cc -List of recipients on CC - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -From -If using from address, you also have to provide a password - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Password -If using a password, you also have to provide the associated from address - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Server - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Subject -Subject of the email - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -To -List of recipients - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAppSideLoading.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAppSideLoading.md deleted file mode 100644 index 58b4fc689b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAppSideLoading.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpappsideloading -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPAppSideLoading ---- - -# Set-PnPAppSideLoading - -## SYNOPSIS -Enables the App SideLoading Feature on a site - -## SYNTAX - -### On -```powershell -Set-PnPAppSideLoading -On [<SwitchParameter>] - [-Connection <SPOnlineConnection>] -``` - -### Off -```powershell -Set-PnPAppSideLoading -Off [<SwitchParameter>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPAppSideLoading -On -``` - -This will turn on App side loading - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPAppSideLoading -Off -``` - -This will turn off App side loading - -## PARAMETERS - -### -Off - - -```yaml -Type: SwitchParameter -Parameter Sets: Off - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -On - - -```yaml -Type: SwitchParameter -Parameter Sets: On - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPApplicationCustomizer.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPApplicationCustomizer.md deleted file mode 100644 index e6cbe3fb19..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPApplicationCustomizer.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpapplicationcustomizer -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Set-PnPApplicationCustomizer ---- - -# Set-PnPApplicationCustomizer - -## SYNOPSIS -Updates a SharePoint Framework client side extension application customizer - -## SYNTAX - -### Custom Action Id -```powershell -Set-PnPApplicationCustomizer [-Identity <UserCustomActionPipeBind>] - [-Scope <CustomActionScope>] - [-Title <String>] - [-Description <String>] - [-Sequence <Int>] - [-ClientSideComponentProperties <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Client Side Component Id -```powershell -Set-PnPApplicationCustomizer [-ClientSideComponentId <GuidPipeBind>] - [-Scope <CustomActionScope>] - [-Title <String>] - [-Description <String>] - [-Sequence <Int>] - [-ClientSideComponentProperties <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Updates a SharePoint Framework client side extension application customizer by updating its custom action. Only the properties that will be provided will be updated. Others will remain as they are. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPCustomAction -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -``` - -Updates the custom action representing the client side extension registration with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2'. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPCustomAction -ClientSideComponentId aa66f67e-46c0-4474-8a82-42bf467d07f2 -Scope web -ClientSideComponentProperties "{`"sourceTermSet`":`"PnP-CollabFooter-SharedLinks`",`"personalItemsStorageProperty`":`"PnP-CollabFooter-MyLinks`"} -``` - -Updates the custom action(s) properties being registered for a SharePoint Framework solution having the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2' in its manifest from the current web. - -## PARAMETERS - -### -ClientSideComponentId -The Client Side Component Id of the SharePoint Framework client side extension application customizer found in the manifest for which existing custom action(s) should be updated - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: Client Side Component Id - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClientSideComponentProperties -The Client Side Component Properties of the application customizer to update. Specify values as a json string : "{Property1 : 'Value1', Property2: 'Value2'}". Omit to not update this property. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description of the application customizer. Omit to not update this property. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The id or name of the CustomAction representing the client side extension registration that needs to be updated or a CustomAction instance itself - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: UserCustomActionPipeBind -Parameter Sets: Custom Action Id - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Define if the CustomAction representing the client side extension registration is to be found at the web or site collection scope. Specify All to update the component on both web and site collection level. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: CustomActionScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Sequence -Sequence of this application customizer being injected. Use when you have a specific sequence with which to have multiple application customizers being added to the page. Omit to not update this property. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the application customizer. Omit to not update this property. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAuditing.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAuditing.md deleted file mode 100644 index 0d59ff425d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAuditing.md +++ /dev/null @@ -1,234 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpauditing -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPAuditing ---- - -# Set-PnPAuditing - -## SYNOPSIS -Set Auditing setting for a site - -## SYNTAX - -### Specific flags -```powershell -Set-PnPAuditing [-RetentionTime <Int>] - [-TrimAuditLog [<SwitchParameter>]] - [-EditItems [<SwitchParameter>]] - [-CheckOutCheckInItems [<SwitchParameter>]] - [-MoveCopyItems [<SwitchParameter>]] - [-DeleteRestoreItems [<SwitchParameter>]] - [-EditContentTypesColumns [<SwitchParameter>]] - [-SearchContent [<SwitchParameter>]] - [-EditUsersPermissions [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### Enable all -```powershell -Set-PnPAuditing -EnableAll [<SwitchParameter>] - [-RetentionTime <Int>] - [-TrimAuditLog [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### Disable All -```powershell -Set-PnPAuditing -DisableAll [<SwitchParameter>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPAuditing -EnableAll -``` - -Enables all auditing settings for the current site - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPAuditing -DisableAll -``` - -Disables all auditing settings for the current site - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPAuditing -RetentionTime 7 -``` - -Sets the audit log trimming to 7 days, this also enables the automatic trimming of the audit log - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPAuditing -TrimAuditLog -``` - -Enables the automatic trimming of the audit log - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPAuditing -RetentionTime 7 -CheckOutCheckInItems -MoveCopyItems -SearchContent -``` - -Sets the audit log trimming to 7 days, this also enables the automatic trimming of the audit log. - -Do auditing for: -- Checking out or checking in items -- Moving or copying items to another location in the site -- Searching site content - -## PARAMETERS - -### -CheckOutCheckInItems -Audit checking out or checking in items - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DeleteRestoreItems -Audit deleting or restoring items - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableAll -Disable all audit flags - -```yaml -Type: SwitchParameter -Parameter Sets: Disable All - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -EditContentTypesColumns -Audit editing content types and columns - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EditItems -Audit editing items - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EditUsersPermissions -Audit editing users and permissions - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableAll -Enable all audit flags - -```yaml -Type: SwitchParameter -Parameter Sets: Enable all - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -MoveCopyItems -Audit moving or copying items to another location in the site. - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RetentionTime -Set the retention time - -```yaml -Type: Int -Parameter Sets: Specific flags, Enable all - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SearchContent -Audit searching site content - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TrimAuditLog -Trim the audit log - -```yaml -Type: SwitchParameter -Parameter Sets: Specific flags, Enable all - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAvailablePageLayouts.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAvailablePageLayouts.md deleted file mode 100644 index bc929d1582..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPAvailablePageLayouts.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpavailablepagelayouts -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPAvailablePageLayouts ---- - -# Set-PnPAvailablePageLayouts - -## SYNOPSIS -Sets the available page layouts for the current site - -## SYNTAX - -### SPECIFIC -```powershell -Set-PnPAvailablePageLayouts -PageLayouts <String[]> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### ALL -```powershell -Set-PnPAvailablePageLayouts -AllowAllPageLayouts [<SwitchParameter>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### INHERIT -```powershell -Set-PnPAvailablePageLayouts -InheritPageLayouts [<SwitchParameter>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -AllowAllPageLayouts -An array of page layout files to set as available page layouts for the site. - -```yaml -Type: SwitchParameter -Parameter Sets: ALL - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -InheritPageLayouts -Set the available page layouts to inherit from the parent site. - -```yaml -Type: SwitchParameter -Parameter Sets: INHERIT - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PageLayouts -An array of page layout files to set as available page layouts for the site. - -```yaml -Type: String[] -Parameter Sets: SPECIFIC - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSidePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSidePage.md deleted file mode 100644 index 2d555133ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSidePage.md +++ /dev/null @@ -1,293 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpclientsidepage -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Set-PnPClientSidePage ---- - -# Set-PnPClientSidePage - -## SYNOPSIS -Sets parameters of a Client-Side Page - -## SYNTAX - -### Custom Header -```powershell -Set-PnPClientSidePage -Identity <ClientSidePagePipeBind> - [-ServerRelativeImageUrl <String>] - [-TranslateX <Double>] - [-TranslateY <Double>] - [-Name <String>] - [-Title <String>] - [-LayoutType <ClientSidePageLayoutType>] - [-PromoteAs <ClientSidePagePromoteType>] - [-CommentsEnabled [<SwitchParameter>]] - [-Publish [<SwitchParameter>]] - [-HeaderType <ClientSidePageHeaderType>] - [-ContentType <ContentTypePipeBind>] - [-ThumbnailUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPClientSidePage -Identity "MyPage" -LayoutType Home -Title "My Page" -``` - -Updates the properties of the Client-Side page named 'MyPage' - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPClientSidePage -Identity "MyPage" -CommentsEnabled -``` - -Enables the comments on the Client-Side page named 'MyPage' - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPClientSidePage -Identity "MyPage" -CommentsEnabled:$false -``` - -Disables the comments on the Client-Side page named 'MyPage' - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPClientSidePage -Identity "MyPage" -HeaderType Default -``` - -Sets the header of the page to the default header - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPClientSidePage -Identity "MyPage" -HeaderType None -``` - -Removes the header of the page - -### ------------------EXAMPLE 6------------------ -```powershell -Set-PnPClientSidePage -Identity "MyPage" -HeaderType Custom -ServerRelativeImageUrl "/sites/demo1/assets/myimage.png" -TranslateX 10.5 -TranslateY 11.0 -``` - -Sets the header of the page to custom header, using the specified image and translates the location of the image in the header given the values specified - -## PARAMETERS - -### -CommentsEnabled -Enables or Disables the comments on the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ContentType -Specify either the name, ID or an actual content type. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HeaderType -Sets the page header type - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePageHeaderType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The name/identity of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -LayoutType -Sets the layout type of the page. (Default = Article) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePageLayoutType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Name -Sets the name of the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PromoteAs -Allows to promote the page for a specific purpose (None | HomePage | NewsArticle | Template) - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePromoteType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Publish -Publishes the page once it is saved. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativeImageUrl -The URL of the image to show in the header - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: Custom Header - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -ThumbnailUrl -Thumbnail Url - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -Sets the title of the page. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TranslateX -A value defining how to translate the image on the x-axis - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Double -Parameter Sets: Custom Header - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -TranslateY -A value defining how to translate the image on the y-axis - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: Double -Parameter Sets: Custom Header - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSideText.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSideText.md deleted file mode 100644 index 7f4e504ca8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSideText.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpclientsidetext -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Set-PnPClientSideText ---- - -# Set-PnPClientSideText - -## SYNOPSIS -Set Client-Side Text Component properties - -## SYNTAX - -```powershell -Set-PnPClientSideText -Page <ClientSidePagePipeBind> - -InstanceId <GuidPipeBind> - -Text <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets the rendered text in existing client side text component - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSetClientSideText -Page Home -InstanceId a2875399-d6ff-43a0-96da-be6ae5875f82 -Text "MyText" -``` - -Sets the text of the client side text component. - -## PARAMETERS - -### -InstanceId -The instance id of the text component - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Page -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Text -Text to set - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSideWebPart.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSideWebPart.md deleted file mode 100644 index 4626655c2b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPClientSideWebPart.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpclientsidewebpart -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Set-PnPClientSideWebPart ---- - -# Set-PnPClientSideWebPart - -## SYNOPSIS -Set Client-Side Web Part properties - -## SYNTAX - -```powershell -Set-PnPClientSideWebPart -Page <ClientSidePagePipeBind> - -Identity <ClientSideWebPartPipeBind> - [-Title <String>] - [-PropertiesJson <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets specific client side web part properties. Notice that the title parameter will only set the -internal- title of web part. The title which is shown in the UI will, if possible, have to be set using the PropertiesJson parameter. Use Get-PnPClientSideComponent to retrieve the instance id and properties of a web part. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPClientSideWebPart -Page Home -Identity a2875399-d6ff-43a0-96da-be6ae5875f82 -PropertiesJson $myproperties -``` - -Sets the properties of the client side web part given in the $myproperties variable. - -## PARAMETERS - -### -Identity -The identity of the web part. This can be the web part instance id or the title of a web part - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSideWebPartPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Page -The name of the page - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: ClientSidePagePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -PropertiesJson -Sets the properties as a JSON string. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Title -Sets the internal title of the web part. Notice that this will NOT set a visible title. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPContext.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPContext.md deleted file mode 100644 index 328297f2eb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPContext.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpcontext -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPContext ---- - -# Set-PnPContext - -## SYNOPSIS -Set the ClientContext - -## SYNTAX - -```powershell -Set-PnPContext -Context <ClientContext> -``` - -## DESCRIPTION -Sets the Client Context to use by the cmdlets, which allows easy context switching. See examples for details. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Url $siteAurl -Credentials $credentials -$ctx = Get-PnPContext -Get-PnPList # returns the lists from site specified with $siteAurl -Connect-PnPOnline -Url $siteBurl -Credentials $credentials -Get-PnPList # returns the lists from the site specified with $siteBurl -Set-PnPContext -Context $ctx # switch back to site A -Get-PnPList # returns the lists from site A -``` - - - -## PARAMETERS - -### -Context -The ClientContext to set - -```yaml -Type: ClientContext -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: True -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultColumnValues.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultColumnValues.md deleted file mode 100644 index 4d829da63b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultColumnValues.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpdefaultcolumnvalues -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPDefaultColumnValues ---- - -# Set-PnPDefaultColumnValues - -## SYNOPSIS -Sets default column values for a document library - -## SYNTAX - -```powershell -Set-PnPDefaultColumnValues -List <ListPipeBind> - -Field <FieldPipeBind> - -Value <String[]> - [-Folder <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets default column values for a document library, per folder, or for the root folder if the folder parameter has not been specified. Supports both text and taxonomy fields. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPDefaultColumnValues -List Documents -Field TaxKeyword -Value "Company|Locations|Stockholm" -``` - -Sets a default value for the enterprise keywords field on a library to a term called "Stockholm", located in the "Locations" term set, which is part of the "Company" term group - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPDefaultColumnValues -List Documents -Field TaxKeyword -Value "15c4c4e4-4b67-4894-a1d8-de5ff811c791" -``` - -Sets a default value for the enterprise keywords field on a library to a term with the id "15c4c4e4-4b67-4894-a1d8-de5ff811c791". You need to ensure the term is valid for the field. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPDefaultColumnValues -List Documents -Field MyTextField -Value "DefaultValue" -Folder "My folder" -``` - -Sets a default value for the MyTextField text field on the folder "My folder" in a library to a value of "DefaultValue" - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPDefaultColumnValues -List Documents -Field MyPeopleField -Value "1;#Foo Bar" -``` - -Sets a default value for the MyPeopleField people field on a library to a value of "Foo Bar" using the id from the user information list. - -### ------------------EXAMPLE 5------------------ -```powershell -$user = New-PnPUser -LoginName foobar@contoso.com -Set-PnPDefaultColumnValues -List Documents -Field MyPeopleField -Value "$($user.Id);#$($user.LoginName)" -``` - -Sets a default value for the MyPeopleField people field on a library to a value of "Foo Bar" using the id from the user information list. - -### ------------------EXAMPLE 6------------------ -```powershell -$user1 = New-PnPUser -LoginName user1@contoso.com -$user2 = New-PnPUser -LoginName user2@contoso.com -Set-PnPDefaultColumnValues -List Documents -Field MyMultiPeopleField -Value "$($user1.Id);#$($user1.LoginName)","$($user2.Id);#$($user2.LoginName)" -``` - -Sets a default value for the MyMultiPeopleField people field on a library to a value of "User 1" and "User 2" using the id from the user information list. - -## PARAMETERS - -### -Field -The internal name, id or a reference to a field - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Folder -A library relative folder path, if not specified it will set the default column values on the root folder of the library ('/') - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Name or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Value -A list of values. In case of a text field the values will be concatenated, separated by a semi-colon. In case of a taxonomy field multiple values will added. In case of people field multiple values will be added. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultContentTypeToList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultContentTypeToList.md deleted file mode 100644 index 593f9e516a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultContentTypeToList.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpdefaultcontenttypetolist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPDefaultContentTypeToList ---- - -# Set-PnPDefaultContentTypeToList - -## SYNOPSIS -Sets the default content type for a list - -## SYNTAX - -```powershell -Set-PnPDefaultContentTypeToList -List <ListPipeBind> - -ContentType <ContentTypePipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPDefaultContentTypeToList -List "Project Documents" -ContentType "Project" -``` - -This will set the Project content type (which has already been added to a list) as the default content type - -## PARAMETERS - -### -ContentType -The content type object that needs to be set as the default content type on the list. Content Type needs to be present on the list. - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The name of a list, an ID or the actual list object to update - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultPageLayout.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultPageLayout.md deleted file mode 100644 index 9ace2e31d1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDefaultPageLayout.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpdefaultpagelayout -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPDefaultPageLayout ---- - -# Set-PnPDefaultPageLayout - -## SYNOPSIS -Sets a specific page layout to be the default page layout for a publishing site - -## SYNTAX - -### TITLE -```powershell -Set-PnPDefaultPageLayout -Title <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### INHERIT -```powershell -Set-PnPDefaultPageLayout -InheritFromParentSite [<SwitchParameter>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPDefaultPageLayout -Title projectpage.aspx -``` - -Sets projectpage.aspx to be the default page layout for the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPDefaultPageLayout -Title test/testpage.aspx -``` - -Sets a page layout in a folder in the Master Page & Page Layout gallery, such as _catalog/masterpage/test/testpage.aspx, to be the default page layout for the current web - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPDefaultPageLayout -InheritFromParentSite -``` - -Sets the default page layout to be inherited from the parent site - -## PARAMETERS - -### -InheritFromParentSite -Set the default page layout to be inherited from the parent site. - -```yaml -Type: SwitchParameter -Parameter Sets: INHERIT - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -Title of the page layout - -```yaml -Type: String -Parameter Sets: TITLE - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDocumentSetField.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDocumentSetField.md deleted file mode 100644 index 42a2e6e932..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPDocumentSetField.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpdocumentsetfield -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPDocumentSetField ---- - -# Set-PnPDocumentSetField - -## SYNOPSIS -Sets a site column from the available content types to a document set - -## SYNTAX - -```powershell -Set-PnPDocumentSetField -DocumentSet <DocumentSetPipeBind> - -Field <FieldPipeBind> - [-SetSharedField [<SwitchParameter>]] - [-SetWelcomePageField [<SwitchParameter>]] - [-RemoveSharedField [<SwitchParameter>]] - [-RemoveWelcomePageField [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPDocumentSetField -Field "Test Field" -DocumentSet "Test Document Set" -SetSharedField -SetWelcomePageField -``` - -This will set the field, available in one of the available content types, as a Shared Field and as a Welcome Page Field. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPDocumentSetField -Field "Test Field" -DocumentSet "Test Document Set" -RemoveSharedField -RemoveWelcomePageField -``` - -This will remove the field, available in one of the available content types, as a Shared Field and as a Welcome Page Field. - -## PARAMETERS - -### -DocumentSet -The document set in which to set the field. Either specify a name, a document set template object, an id, or a content type object - -```yaml -Type: DocumentSetPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Field -The field to set. The field needs to be available in one of the available content types. Either specify a name, an id or a field object - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -RemoveSharedField -Removes the field as a Shared Field - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RemoveWelcomePageField -Removes the field as a Welcome Page Field - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SetSharedField -Set the field as a Shared Field - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SetWelcomePageField -Set the field as a Welcome Page field - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPField.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPField.md deleted file mode 100644 index 21e4c36e16..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPField.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpfield -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPField ---- - -# Set-PnPField - -## SYNOPSIS -Changes one or more properties of a field in a specific list or for the whole web - -## SYNTAX - -```powershell -Set-PnPField -Identity <FieldPipeBind> - -Values <Hashtable> - [-List <ListPipeBind>] - [-UpdateExistingLists [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPField -Identity AssignedTo -Values @{JSLink="customrendering.js";Group="My fields"} -``` - -Updates the AssignedTo field on the current web to use customrendering.js for the JSLink and sets the group name the field is categorized in to "My Fields". Lists that are already using the AssignedTo field will not be updated. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPField -Identity AssignedTo -Values @{JSLink="customrendering.js";Group="My fields"} -UpdateExistingLists -``` - -Updates the AssignedTo field on the current web to use customrendering.js for the JSLink and sets the group name the field is categorized in to "My Fields". Lists that are already using the AssignedTo field will also be updated. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPField -List "Tasks" -Identity "AssignedTo" -Values @{JSLink="customrendering.js"} -``` - -Updates the AssignedTo field on the Tasks list to use customrendering.js for the JSLink - -## PARAMETERS - -### -Identity -The field object, internal field name (case sensitive) or field id to update - -```yaml -Type: FieldPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -List -The list object, name or id where to update the field. If omitted the field will be updated on the web. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: True -``` - -### -UpdateExistingLists -If provided, the field will be updated on existing lists that use it as well. If not provided or set to $false, existing lists using the field will remain unchanged but new lists will get the updated field. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Values -Hashtable of properties to update on the field. Use the syntax @{property1="value";property2="value"}. - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Field - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedIn.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedIn.md deleted file mode 100644 index 74f100785e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedIn.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpfilecheckedin -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPFileCheckedIn ---- - -# Set-PnPFileCheckedIn - -## SYNOPSIS -Checks in a file - -## SYNTAX - -```powershell -Set-PnPFileCheckedIn -Url <String> - [-CheckinType <CheckinType>] - [-Comment <String>] - [-Approve [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -PS:>Set-PnPFileCheckedIn -Url "/Documents/Contract.docx" -``` - -Checks in the file "Contract.docx" in the "Documents" library - -### ------------------EXAMPLE 2------------------ -```powershell -PS:>Set-PnPFileCheckedIn -Url "/Documents/Contract.docx" -CheckinType MinorCheckin -Comment "Smaller changes" -``` - -Checks in the file "Contract.docx" in the "Documents" library as a minor version and adds the check in comment "Smaller changes" - -## PARAMETERS - -### -Approve -Approve file - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CheckinType -The check in type to use. Defaults to Major - -```yaml -Type: CheckinType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Comment -The check in comment - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -The server relative url of the file to check in - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedOut.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedOut.md deleted file mode 100644 index 3815607b66..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFileCheckedOut.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpfilecheckedout -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPFileCheckedOut ---- - -# Set-PnPFileCheckedOut - -## SYNOPSIS -Checks out a file - -## SYNTAX - -```powershell -Set-PnPFileCheckedOut -Url <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -PS:>Set-PnPFileCheckedOut -Url "/sites/testsite/subsite/Documents/Contract.docx" -``` - -Checks out the file "Contract.docx" in the "Documents" library. - -## PARAMETERS - -### -Url -The server relative url of the file to check out - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFolderPermission.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFolderPermission.md deleted file mode 100644 index 1d3190bcbd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPFolderPermission.md +++ /dev/null @@ -1,220 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpfolderpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPFolderPermission ---- - -# Set-PnPFolderPermission - -## SYNOPSIS -Sets folder permissions. Use Get-PnPRoleDefinition to retrieve all available roles you can add or remove using this cmdlet. - -## SYNTAX - -### Inherit -```powershell -Set-PnPFolderPermission -List <ListPipeBind> - -Identity <FolderPipeBind> - [-InheritPermissions [<SwitchParameter>]] - [-SystemUpdate [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Group -```powershell -Set-PnPFolderPermission -Group <GroupPipeBind> - -List <ListPipeBind> - -Identity <FolderPipeBind> - [-AddRole <String>] - [-RemoveRole <String>] - [-ClearExisting [<SwitchParameter>]] - [-SystemUpdate [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### User -```powershell -Set-PnPFolderPermission -User <String> - -List <ListPipeBind> - -Identity <FolderPipeBind> - [-AddRole <String>] - [-RemoveRole <String>] - [-ClearExisting [<SwitchParameter>]] - [-SystemUpdate [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPFolderPermission -List 'Shared Documents' -Identity 'Shared Documents\Folder' -User 'user@contoso.com' -AddRole 'Contribute' -``` - -Adds the 'Contribute' permission to the user 'user@contoso.com' for the folder named 'Folder' located in the root of the library 'Shared Documents' - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPFolderPermission -List 'Documents' -Identity 'Shared Documents\Folder\Subfolder' -User 'user@contoso.com' -RemoveRole 'Contribute' -``` - -Removes the 'Contribute' permission to the user 'user@contoso.com' for the folder named 'Subfolder' located in the folder 'Folder' which is located in the root of the library 'Shared Documents' - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPFolderPermission -List 'Documents' -Identity 'Shared Documents\Folder' -User 'user@contoso.com' -AddRole 'Contribute' -ClearExisting -``` - -Adds the 'Contribute' permission to the user 'user@contoso.com' for the folder named 'Folder' located in the root of the library 'Shared Documents' and removes all other permissions - -### ------------------EXAMPLE 4------------------ -```powershell -Get-PnPFolder -Url 'Shared Documents\Folder' | Set-PnPFolderPermission -List 'Documents' -InheritPermissions -``` - -Resets permissions for the folder named 'Folder' located in the root of the library 'Shared Documents' to inherit permissions from the library 'Shared Documents' - -## PARAMETERS - -### -AddRole -The role that must be assigned to the group or user - -```yaml -Type: String -Parameter Sets: User, Group - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClearExisting -Clear all existing permissions - -```yaml -Type: SwitchParameter -Parameter Sets: User, Group - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Group - - -```yaml -Type: GroupPipeBind -Parameter Sets: Group - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the folder, the server relative URL to the folder or actual Folder object - -```yaml -Type: FolderPipeBind -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -InheritPermissions -Inherit permissions from the parent, removing unique permissions - -```yaml -Type: SwitchParameter -Parameter Sets: Inherit - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Title or Url of the list the folder is part of - -```yaml -Type: ListPipeBind -Parameter Sets: __AllParameterSets - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -RemoveRole -The role that must be removed from the group or user - -```yaml -Type: String -Parameter Sets: User, Group - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SystemUpdate -Update the folder permissions without creating a new version or triggering MS Flow. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -User - - -```yaml -Type: String -Parameter Sets: User - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPGroup.md deleted file mode 100644 index 314baa3a4f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPGroup.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpgroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPGroup ---- - -# Set-PnPGroup - -## SYNOPSIS -Updates a group - -## SYNTAX - -```powershell -Set-PnPGroup -Identity <GroupPipeBind> - [-SetAssociatedGroup <AssociatedGroupType>] - [-AddRole <String>] - [-RemoveRole <String>] - [-Title <String>] - [-Owner <String>] - [-Description <String>] - [-AllowRequestToJoinLeave <Boolean>] - [-AutoAcceptRequestToJoinLeave <Boolean>] - [-AllowMembersEditMembership <Boolean>] - [-OnlyAllowMembersViewMembership <Boolean>] - [-RequestToJoinEmail <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPGroup -Identity 'My Site Members' -SetAssociatedGroup Members -``` - -Sets the SharePoint group with the name 'My Site Members' as the associated members group - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPGroup -Identity 'My Site Members' -Owner 'site owners' -``` - -Sets the SharePoint group with the name 'site owners' as the owner of the SharePoint group with the name 'My Site Members' - -## PARAMETERS - -### -AddRole -Name of the permission set to add to this SharePoint group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AllowMembersEditMembership -A switch parameter that specifies whether group members can modify membership in the group - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AllowRequestToJoinLeave -A switch parameter that specifies whether to allow users to request membership in the group and to allow users to request to leave the group - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AutoAcceptRequestToJoinLeave -A switch parameter that specifies whether users are automatically added or removed when they make a request - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description for the group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -A group object, an ID or a name of a group - -```yaml -Type: GroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -OnlyAllowMembersViewMembership -A switch parameter that specifies whether only group members are allowed to view the list of members in the group - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owner -The owner for the group, which can be a user or another group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RemoveRole -Name of the permission set to remove from this SharePoint group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RequestToJoinEmail -The e-mail address to which membership requests are sent - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SetAssociatedGroup -One of the associated group types (Visitors, Members, Owners - -```yaml -Type: AssociatedGroupType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title for the group - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPGroupPermissions.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPGroupPermissions.md deleted file mode 100644 index e41ddae997..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPGroupPermissions.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpgrouppermissions -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPGroupPermissions ---- - -# Set-PnPGroupPermissions - -## SYNOPSIS -Adds and/or removes permissions of a specific SharePoint group - -## SYNTAX - -### ByName -```powershell -Set-PnPGroupPermissions -Identity <GroupPipeBind> - [-List <ListPipeBind>] - [-AddRole <String[]>] - [-RemoveRole <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPGroupPermissions -Identity 'My Site Members' -AddRole Contribute -``` - -Adds the 'Contribute' permission to the SharePoint group with the name 'My Site Members' - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPGroupPermissions -Identity 'My Site Members' -RemoveRole 'Full Control' -AddRole 'Read' -``` - -Removes the 'Full Control' from and adds the 'Contribute' permissions to the SharePoint group with the name 'My Site Members' - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPGroupPermissions -Identity 'My Site Members' -AddRole @('Contribute', 'Design') -``` - -Adds the 'Contribute' and 'Design' permissions to the SharePoint group with the name 'My Site Members' - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPGroupPermissions -Identity 'My Site Members' -RemoveRole @('Contribute', 'Design') -``` - -Removes the 'Contribute' and 'Design' permissions from the SharePoint group with the name 'My Site Members' - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPGroupPermissions -Identity 'My Site Members' -List 'MyList' -RemoveRole @('Contribute') -``` - -Removes the 'Contribute' permissions from the list 'MyList' for the group with the name 'My Site Members' - -## PARAMETERS - -### -AddRole -Name of the permission set to add to this SharePoint group - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Get the permissions of a specific group by name - -```yaml -Type: GroupPipeBind -Parameter Sets: ByName -Aliases: Name - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -List -The list to apply the command to. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RemoveRole -Name of the permission set to remove from this SharePoint group - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHideDefaultThemes.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHideDefaultThemes.md deleted file mode 100644 index 5a1f5e5918..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHideDefaultThemes.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnphidedefaultthemes -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPHideDefaultThemes ---- - -# Set-PnPHideDefaultThemes - -## SYNOPSIS -Defines if the default / OOTB themes should be visible to users or not. - -## SYNTAX - -```powershell -Set-PnPHideDefaultThemes -HideDefaultThemes <Boolean> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Use this cmdlet to hide or show the default themes to users - -You must be a SharePoint Online global administrator to run the cmdlet. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPHideDefaultThemes -HideDefaultThemes $true -``` - -This example hides the default themes - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPHideDefaultThemes -HideDefaultThemes $false -``` - -This example shows the default themes - -## PARAMETERS - -### -HideDefaultThemes -Defines if the default themes should be visible or hidden - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHomePage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHomePage.md deleted file mode 100644 index 2e3042092b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHomePage.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnphomepage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPHomePage ---- - -# Set-PnPHomePage - -## SYNOPSIS -Sets the home page of the current web. - -## SYNTAX - -```powershell -Set-PnPHomePage -RootFolderRelativeUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPHomePage -RootFolderRelativeUrl SitePages/Home.aspx -``` - -Sets the home page to the home.aspx file which resides in the SitePages library - -## PARAMETERS - -### -RootFolderRelativeUrl -The root folder relative url of the homepage, e.g. 'sitepages/home.aspx' - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Path - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHomeSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHomeSite.md deleted file mode 100644 index 9958eaf38e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHomeSite.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnphomesite -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPHomeSite ---- - -# Set-PnPHomeSite - -## SYNOPSIS -Sets the home site for your tenant - -## SYNTAX - -```powershell -Set-PnPHomeSite -Url <String> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPHomeSite -Url https://yourtenant.sharepoint.com/sites/myhome -``` - -Sets the home site to the provided site collection url - -## PARAMETERS - -### -Url -The url of the site to set as the home site - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHubSite.md deleted file mode 100644 index 752997fcc2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHubSite.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnphubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPHubSite ---- - -# Set-PnPHubSite - -## SYNOPSIS -Sets hub site properties - -## SYNTAX - -```powershell -Set-PnPHubSite [-SiteDesignId <GuidPipeBind>] - [-HideNameInNavigation [<SwitchParameter>]] - [-RequiresJoinApproval [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Allows configuring a hub site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPHubSite -Identity https://tenant.sharepoint.com/sites/myhubsite -Title "My New Title" -``` - -Sets the title of the hub site - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPHubSite -Identity https://tenant.sharepoint.com/sites/myhubsite -Description "My updated description" -``` - -Sets the description of the hub site - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPHubSite -Identity https://tenant.sharepoint.com/sites/myhubsite -SiteDesignId df8a3ef1-9603-44c4-abd9-541aea2fa745 -``` - -Sets the site design which should be applied to sites joining the the hub site - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPHubSite -Identity https://tenant.sharepoint.com/sites/myhubsite -LogoUrl "https://tenant.sharepoint.com/SiteAssets/Logo.png" -``` - -Sets the logo of the hub site - -## PARAMETERS - -### -HideNameInNavigation - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RequiresJoinApproval - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SiteDesignId -GUID of the SharePoint Site Design which should be applied when a site joins the hub site - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPInPlaceRecordsManagement.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPInPlaceRecordsManagement.md deleted file mode 100644 index 6fa923ac50..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPInPlaceRecordsManagement.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpinplacerecordsmanagement -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPInPlaceRecordsManagement ---- - -# Set-PnPInPlaceRecordsManagement - -## SYNOPSIS -Activates or deactivates in the place records management feature. - -## SYNTAX - -### Enable or Disable -```powershell -Set-PnPInPlaceRecordsManagement -Enabled <Boolean> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPInPlaceRecordsManagement -Enabled $true -``` - -Activates In Place Records Management - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPInPlaceRecordsManagement -Enabled $false -``` - -Deactivates In Place Records Management - -## PARAMETERS - -### -Enabled - - -```yaml -Type: Boolean -Parameter Sets: Enable or Disable - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPIndexedProperties.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPIndexedProperties.md deleted file mode 100644 index 578827650f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPIndexedProperties.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpindexedproperties -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPIndexedProperties ---- - -# Set-PnPIndexedProperties - -## SYNOPSIS -Marks values of the propertybag to be indexed by search. Notice that this will overwrite the existing flags, i.e. only the properties you define with the cmdlet will be indexed. - -## SYNTAX - -```powershell -Set-PnPIndexedProperties -Keys <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Keys - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPKnowledgeHubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPKnowledgeHubSite.md deleted file mode 100644 index 9541dbb15d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPKnowledgeHubSite.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpknowledgehubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPKnowledgeHubSite ---- - -# Set-PnPKnowledgeHubSite - -## SYNOPSIS -Sets the Knowledge Hub Site for your tenant - -## SYNTAX - -```powershell -Set-PnPKnowledgeHubSite -KnowledgeHubSiteUrl <String> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPKnowledgeHubSite -KnowledgeHubSiteUrl https://yoursite.sharepoint.com/sites/knowledge -``` - -Sets the Knowledge Hub Site for your tenant - -## PARAMETERS - -### -KnowledgeHubSiteUrl - - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPLabel.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPLabel.md deleted file mode 100644 index 759fe6cc82..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPLabel.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplabel -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPLabel ---- - -# Set-PnPLabel - -## SYNOPSIS -Sets a label/tag on the specified list or library. Use Reset-PnPLabel to remove the label again. - -## SYNTAX - -```powershell -Set-PnPLabel -List <ListPipeBind> - -Label <String> - [-SyncToItems <Boolean>] - [-BlockDeletion <Boolean>] - [-BlockEdit <Boolean>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPLabel -List "Demo List" -Label "Project Documentation" -``` - -This sets an O365 label on the specified list or library. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPLabel -List "Demo List" -Label "Project Documentation" -SyncToItems $true -``` - -This sets an O365 label on the specified list or library and sets the label to all the items in the list and library as well. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPLabel -List "Demo List" -Label "Project Documentation" -BlockDelete $true -BlockEdit $true -``` - -This sets an O365 label on the specified list or library. Next, it also blocks the ability to either edit or delete the item. - -## PARAMETERS - -### -BlockDeletion -Block deletion of items in the library. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -BlockEdit -Block editing of items in the library. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Label -The name of the label. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -List -The ID or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SyncToItems -Apply label to existing items in the library. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPList.md deleted file mode 100644 index 7305d3c0c8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPList.md +++ /dev/null @@ -1,329 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPList ---- - -# Set-PnPList - -## SYNOPSIS -Updates list settings - -## SYNTAX - -```powershell -Set-PnPList -Identity <ListPipeBind> - [-EnableContentTypes <Boolean>] - [-BreakRoleInheritance [<SwitchParameter>]] - [-ResetRoleInheritance [<SwitchParameter>]] - [-CopyRoleAssignments [<SwitchParameter>]] - [-ClearSubscopes [<SwitchParameter>]] - [-Title <String>] - [-Description <String>] - [-Hidden <Boolean>] - [-ForceCheckout <Boolean>] - [-ListExperience <ListExperience>] - [-EnableAttachments <Boolean>] - [-EnableFolderCreation <Boolean>] - [-EnableVersioning <Boolean>] - [-EnableMinorVersions <Boolean>] - [-MajorVersions <UInt32>] - [-MinorVersions <UInt32>] - [-EnableModeration <Boolean>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPList -Identity "Demo List" -EnableContentTypes $true -``` - -Switches the Enable Content Type switch on the list - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPList -Identity "Demo List" -Hidden $true -``` - -Hides the list from the SharePoint UI. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPList -Identity "Demo List" -EnableVersioning $true -``` - -Turns on major versions on a list - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPList -Identity "Demo List" -EnableVersioning $true -MajorVersions 20 -``` - -Turns on major versions on a list and sets the maximum number of Major Versions to keep to 20. - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPList -Identity "Demo Library" -EnableVersioning $true -EnableMinorVersions $true -MajorVersions 20 -MinorVersions 5 -``` - -Turns on major versions on a document library and sets the maximum number of Major versions to keep to 20 and sets the maximum of Minor versions to 5. - -### ------------------EXAMPLE 6------------------ -```powershell -Set-PnPList -Identity "Demo List" -EnableAttachments $true -``` - -Turns on attachments on a list - -## PARAMETERS - -### -BreakRoleInheritance -If used the security inheritance is broken for this list - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClearSubscopes -If used the unique permissions are cleared from child objects and they can inherit role assignments from this object - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CopyRoleAssignments -If used the roles are copied from the parent web - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description of the list - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableAttachments -Enable or disable attachments. Set to $true to enable, $false to disable. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableContentTypes -Set to $true to enable content types, set to $false to disable content types - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableFolderCreation -Enable or disable folder creation. Set to $true to enable, $false to disable. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableMinorVersions -Enable or disable minor versions versioning. Set to $true to enable, $false to disable. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableModeration -Enable or disable whether content approval is enabled for the list. Set to $true to enable, $false to disable. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableVersioning -Enable or disable versioning. Set to $true to enable, $false to disable. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ForceCheckout -Enable or disable force checkout. Set to $true to enable, $false to disable. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Hidden -Hide the list from the SharePoint UI. Set to $true to hide, $false to show. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ListExperience -Set the list experience: Auto, NewExperience or ClassicExperience - -Only applicable to: SharePoint Online - -```yaml -Type: ListExperience -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MajorVersions -Maximum major versions to keep - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MinorVersions -Maximum minor versions to keep - -```yaml -Type: UInt32 -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ResetRoleInheritance -If used the security inheritance is reset for this list (inherited from parent) - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the list - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListInformationRightsManagement.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListInformationRightsManagement.md deleted file mode 100644 index 969626bdd9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListInformationRightsManagement.md +++ /dev/null @@ -1,305 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplistinformationrightsmanagement -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPListInformationRightsManagement ---- - -# Set-PnPListInformationRightsManagement - -## SYNOPSIS -Get the site closure status of the site which has a site policy applied - -## SYNTAX - -```powershell -Set-PnPListInformationRightsManagement -List <ListPipeBind> - [-Enable <Boolean>] - [-EnableExpiration <Boolean>] - [-EnableRejection <Boolean>] - [-AllowPrint <Boolean>] - [-AllowScript <Boolean>] - [-AllowWriteCopy <Boolean>] - [-DisableDocumentBrowserView <Boolean>] - [-DocumentAccessExpireDays <Int>] - [-DocumentLibraryProtectionExpireDate <DateTime>] - [-EnableDocumentAccessExpire <Boolean>] - [-EnableDocumentBrowserPublishingView <Boolean>] - [-EnableGroupProtection <Boolean>] - [-EnableLicenseCacheExpire <Boolean>] - [-LicenseCacheExpireDays <Int>] - [-GroupName <String>] - [-PolicyDescription <String>] - [-PolicyTitle <String>] - [-TemplateId <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPListInformationRightsManagement -List "Documents" -Enabled $true -``` - -Enables Information Rights Management (IRM) on the list. - -## PARAMETERS - -### -AllowPrint -Sets a value indicating whether the viewer can print the downloaded document. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AllowScript -Sets a value indicating whether the viewer can run a script on the downloaded document. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AllowWriteCopy -Sets a value indicating whether the viewer can write on a copy of the downloaded document. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableDocumentBrowserView -Sets a value indicating whether to block Office Web Application Companion applications (WACs) from showing this document. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DocumentAccessExpireDays -Sets the number of days after which the downloaded document will expire. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DocumentLibraryProtectionExpireDate -Sets the date after which the Information Rights Management (IRM) protection of this document library will stop. - -```yaml -Type: DateTime -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Enable -Specifies whether Information Rights Management (IRM) is enabled for the list. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableDocumentAccessExpire -Sets a value indicating whether the downloaded document will expire. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableDocumentBrowserPublishingView -Sets a value indicating whether to enable Office Web Application Companion applications (WACs) to publishing view. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableExpiration -Specifies whether Information Rights Management (IRM) expiration is enabled for the list. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableGroupProtection -Sets a value indicating whether the permission of the downloaded document is applicable to a group. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableLicenseCacheExpire -Sets whether a user must verify their credentials after some interval. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableRejection -Specifies whether Information Rights Management (IRM) rejection is enabled for the list. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -GroupName -Sets the group name (email address) that the permission is also applicable to. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LicenseCacheExpireDays -Sets the number of days that the application that opens the document caches the IRM license. When these elapse, the application will connect to the IRM server to validate the license. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The list to set Information Rights Management (IRM) settings for. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PolicyDescription -Sets the permission policy description. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PolicyTitle -Sets the permission policy title. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateId - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItem.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItem.md deleted file mode 100644 index 70a3ab0887..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItem.md +++ /dev/null @@ -1,203 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplistitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPListItem ---- - -# Set-PnPListItem - -## SYNOPSIS -Updates a list item - -## SYNTAX - -```powershell -Set-PnPListItem -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-ContentType <ContentTypePipeBind>] - [-Values <Hashtable>] - [-SystemUpdate [<SwitchParameter>]] - [-Label <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPListItem -List "Demo List" -Identity 1 -Values @{"Title" = "Test Title"; "Category"="Test Category"} -``` - -Sets fields value in the list item with ID 1 in the "Demo List". It sets both the Title and Category fields with the specified values. Notice, use the internal names of fields. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPListItem -List "Demo List" -Identity 1 -ContentType "Company" -Values @{"Title" = "Test Title"; "Category"="Test Category"} -``` - -Sets fields value in the list item with ID 1 in the "Demo List". It sets the content type of the item to "Company" and it sets both the Title and Category fields with the specified values. Notice, use the internal names of fields. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPListItem -List "Demo List" -Identity $item -Values @{"Title" = "Test Title"; "Category"="Test Category"} -``` - -Sets fields value in the list item which has been retrieved by for instance Get-PnPListItem. It sets the content type of the item to "Company" and it sets both the Title and Category fields with the specified values. Notice, use the internal names of fields. - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPListItem -List "Demo List" -Identity 1 -Label "Public" -``` - -Sets the retention label in the list item with ID 1 in the "Demo List". - -## PARAMETERS - -### -ContentType -Specify either the name, ID or an actual content type - -```yaml -Type: ContentTypePipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the listitem, or actual ListItem object - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Label -The name of the retention label. - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -SystemUpdate -Update the item without creating a new version. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Values -Use the internal names of the fields when specifying field names. - -Single line of text: -Values @{"TextField" = "Title New"} - -Multiple lines of text: -Values @{"MultiTextField" = "New text\n\nMore text"} - -Rich text: -Values @{"MultiTextField" = "<strong>New</strong> text"} - -Choice: -Values @{"ChoiceField" = "Value 1"} - -Number: -Values @{"NumberField" = "10"} - -Currency: -Values @{"NumberField" = "10"} - -Currency: -Values @{"CurrencyField" = "10"} - -Date and Time: -Values @{"DateAndTimeField" = "03/13/2015 14:16"} - -Lookup (id of lookup value): -Values @{"LookupField" = "2"} - -Multi value lookup (id of lookup values as array 1): -Values @{"MultiLookupField" = "1","2"} - -Multi value lookup (id of lookup values as array 2): -Values @{"MultiLookupField" = 1,2} - -Multi value lookup (id of lookup values as string): -Values @{"MultiLookupField" = "1,2"} - -Yes/No: -Values @{"YesNoField" = $false} - -Person/Group (id of user/group in Site User Info List or email of the user, separate multiple values with a comma): -Values @{"PersonField" = "user1@domain.com","21"} - -Managed Metadata (single value with path to term): -Values @{"MetadataField" = "CORPORATE|DEPARTMENTS|FINANCE"} - -Managed Metadata (single value with id of term): -Values @{"MetadataField" = "fe40a95b-2144-4fa2-b82a-0b3d0299d818"} with Id of term - -Managed Metadata (multiple values with paths to terms): -Values @{"MetadataField" = ("CORPORATE|DEPARTMENTS|FINANCE","CORPORATE|DEPARTMENTS|HR")} - -Managed Metadata (multiple values with ids of terms): -Values @{"MetadataField" = ("fe40a95b-2144-4fa2-b82a-0b3d0299d818","52d88107-c2a8-4bf0-adfa-04bc2305b593")} - -Hyperlink or Picture: -Values @{"HyperlinkField" = "https://github.com/OfficeDev/,%20OfficePnp"} - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.ListItem - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItemAsRecord.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItemAsRecord.md deleted file mode 100644 index 4ad023bed1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItemAsRecord.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplistitemasrecord -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPListItemAsRecord ---- - -# Set-PnPListItemAsRecord - -## SYNOPSIS -Declares a list item as a record, for more information, see https://docs.microsoft.com/sharepoint/governance/records-management-in-sharepoint-server - -## SYNTAX - -```powershell -Set-PnPListItemAsRecord -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-DeclarationDate <DateTime>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPListItemAsRecord -List "Documents" -Identity 4 -``` - -Declares the document in the documents library with id 4 as a record - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPListItemAsRecord -List "Documents" -Identity 4 -DeclarationDate $date -``` - -Declares the document in the documents library with id as a record - -## PARAMETERS - -### -DeclarationDate -The declaration date - -```yaml -Type: DateTime -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the listitem, or actual ListItem object - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItemPermission.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItemPermission.md deleted file mode 100644 index 2f56a8a91f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListItemPermission.md +++ /dev/null @@ -1,220 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplistitempermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPListItemPermission ---- - -# Set-PnPListItemPermission - -## SYNOPSIS -Sets list item permissions. Use Get-PnPRoleDefinition to retrieve all available roles you can add or remove using this cmdlet. - -## SYNTAX - -### Inherit -```powershell -Set-PnPListItemPermission -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-InheritPermissions [<SwitchParameter>]] - [-SystemUpdate [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Group -```powershell -Set-PnPListItemPermission -Group <GroupPipeBind> - -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-AddRole <String>] - [-RemoveRole <String>] - [-ClearExisting [<SwitchParameter>]] - [-SystemUpdate [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### User -```powershell -Set-PnPListItemPermission -User <String> - -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-AddRole <String>] - [-RemoveRole <String>] - [-ClearExisting [<SwitchParameter>]] - [-SystemUpdate [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPListItemPermission -List 'Documents' -Identity 1 -User 'user@contoso.com' -AddRole 'Contribute' -``` - -Adds the 'Contribute' permission to the user 'user@contoso.com' for listitem with id 1 in the list 'Documents' - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPListItemPermission -List 'Documents' -Identity 1 -User 'user@contoso.com' -RemoveRole 'Contribute' -``` - -Removes the 'Contribute' permission to the user 'user@contoso.com' for listitem with id 1 in the list 'Documents' - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPListItemPermission -List 'Documents' -Identity 1 -User 'user@contoso.com' -AddRole 'Contribute' -ClearExisting -``` - -Adds the 'Contribute' permission to the user 'user@contoso.com' for listitem with id 1 in the list 'Documents' and removes all other permissions - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPListItemPermission -List 'Documents' -Identity 1 -InheritPermissions -``` - -Resets permissions for listitem with id 1 to inherit permissions from the list 'Documents' - -## PARAMETERS - -### -AddRole -The role that must be assigned to the group or user - -```yaml -Type: String -Parameter Sets: User, Group - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClearExisting -Clear all existing permissions - -```yaml -Type: SwitchParameter -Parameter Sets: User, Group - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Group - - -```yaml -Type: GroupPipeBind -Parameter Sets: Group - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID of the listitem, or actual ListItem object - -```yaml -Type: ListItemPipeBind -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -InheritPermissions -Inherit permissions from the list, removing unique permissions - -```yaml -Type: SwitchParameter -Parameter Sets: Inherit - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: __AllParameterSets - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -RemoveRole -The role that must be removed from the group or user - -```yaml -Type: String -Parameter Sets: User, Group - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SystemUpdate -Update the item permissions without creating a new version or triggering MS Flow. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -User - - -```yaml -Type: String -Parameter Sets: User - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListPermission.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListPermission.md deleted file mode 100644 index ccee1c7275..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListPermission.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplistpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPListPermission ---- - -# Set-PnPListPermission - -## SYNOPSIS -Sets list permissions - -## SYNTAX - -### Group -```powershell -Set-PnPListPermission -Group <GroupPipeBind> - -Identity <ListPipeBind> - [-AddRole <String>] - [-RemoveRole <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### User -```powershell -Set-PnPListPermission -User <String> - -Identity <ListPipeBind> - [-AddRole <String>] - [-RemoveRole <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPListPermission -Identity 'Documents' -User 'user@contoso.com' -AddRole 'Contribute' -``` - -Adds the 'Contribute' permission to the user 'user@contoso.com' for the list 'Documents' - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPListPermission -Identity 'Documents' -User 'user@contoso.com' -RemoveRole 'Contribute' -``` - -Removes the 'Contribute' permission to the user 'user@contoso.com' for the list 'Documents' - -## PARAMETERS - -### -AddRole -The role that must be assigned to the group or user - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Group - - -```yaml -Type: GroupPipeBind -Parameter Sets: Group - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Identity -The ID or Title of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -RemoveRole -The role that must be removed from the group or user - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -User - - -```yaml -Type: String -Parameter Sets: User - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListRecordDeclaration.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListRecordDeclaration.md deleted file mode 100644 index 8a572a723d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListRecordDeclaration.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnplistrecorddeclaration -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPListRecordDeclaration ---- - -# Set-PnPListRecordDeclaration - -## SYNOPSIS -The RecordDeclaration parameter supports 4 values: - -AlwaysAllowManualDeclaration -NeverAllowManualDeclaration -UseSiteCollectionDefaults - - -## SYNTAX - -```powershell -Set-PnPListRecordDeclaration -List <ListPipeBind> - [-ManualRecordDeclaration <EcmListManualRecordDeclaration>] - [-AutoRecordDeclaration <Boolean>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPListRecordDeclaration -List "Documents" -ManualRecordDeclaration NeverAllowManualDeclaration -``` - -Sets the manual record declaration to never allow - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPListRecordDeclaration -List "Documents" -AutoRecordDeclaration $true -``` - -Turns on auto record declaration for the list - -## PARAMETERS - -### -AutoRecordDeclaration -Defines if you want to set auto record declaration on the list - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The List to set the manual record declaration settings for - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ManualRecordDeclaration -Defines the manual record declaration setting for the lists - -```yaml -Type: EcmListManualRecordDeclaration -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPMasterPage.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPMasterPage.md deleted file mode 100644 index 0bc2e0cf12..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPMasterPage.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpmasterpage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPMasterPage ---- - -# Set-PnPMasterPage - -## SYNOPSIS -Set the masterpage - -## SYNTAX - -### Server Relative -```powershell -Set-PnPMasterPage [-MasterPageServerRelativeUrl <String>] - [-CustomMasterPageServerRelativeUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Site Relative -```powershell -Set-PnPMasterPage [-MasterPageSiteRelativeUrl <String>] - [-CustomMasterPageSiteRelativeUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets the default master page of the current web. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPMasterPage -MasterPageServerRelativeUrl /sites/projects/_catalogs/masterpage/oslo.master -``` - -Sets the master page based on a server relative URL - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPMasterPage -MasterPageServerRelativeUrl /sites/projects/_catalogs/masterpage/oslo.master -CustomMasterPageServerRelativeUrl /sites/projects/_catalogs/masterpage/oslo.master -``` - -Sets the master page and custom master page based on a server relative URL - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPMasterPage -MasterPageSiteRelativeUrl _catalogs/masterpage/oslo.master -``` - -Sets the master page based on a site relative URL - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPMasterPage -MasterPageSiteRelativeUrl _catalogs/masterpage/oslo.master -CustomMasterPageSiteRelativeUrl _catalogs/masterpage/oslo.master -``` - -Sets the master page and custom master page based on a site relative URL - -## PARAMETERS - -### -CustomMasterPageServerRelativeUrl -Specifies the custom Master page URL based on the server relative URL - -```yaml -Type: String -Parameter Sets: Server Relative -Aliases: CustomMasterPageUrl - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CustomMasterPageSiteRelativeUrl -Specifies the custom Master page URL based on the site relative URL - -```yaml -Type: String -Parameter Sets: Site Relative - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MasterPageServerRelativeUrl -Specifies the Master page URL based on the server relative URL - -```yaml -Type: String -Parameter Sets: Server Relative -Aliases: MasterPageUrl - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MasterPageSiteRelativeUrl -Specifies the Master page URL based on the site relative URL - -```yaml -Type: String -Parameter Sets: Site Relative - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPMinimalDownloadStrategy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPMinimalDownloadStrategy.md deleted file mode 100644 index 957bf197ae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPMinimalDownloadStrategy.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpminimaldownloadstrategy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPMinimalDownloadStrategy ---- - -# Set-PnPMinimalDownloadStrategy - -## SYNOPSIS -Activates or deactivates the minimal downloading strategy. - -## SYNTAX - -### On -```powershell -Set-PnPMinimalDownloadStrategy -On [<SwitchParameter>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Off -```powershell -Set-PnPMinimalDownloadStrategy -Off [<SwitchParameter>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Activates or deactivates the minimal download strategy feature of a site - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPMinimalDownloadStrategy -Off -``` - -Will deactivate minimal download strategy (MDS) for the current web. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPMinimalDownloadStrategy -On -``` - -Will activate minimal download strategy (MDS) for the current web. - -## PARAMETERS - -### -Force -Specifies whether to overwrite (when activating) or continue (when deactivating) an existing feature with the same feature identifier. This parameter is ignored if there are no errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Off -Turn minimal download strategy off - -```yaml -Type: SwitchParameter -Parameter Sets: Off - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -On -Turn minimal download strategy on - -```yaml -Type: SwitchParameter -Parameter Sets: On - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPPropertyBagValue.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPPropertyBagValue.md deleted file mode 100644 index 22a5b2e1cc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPPropertyBagValue.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnppropertybagvalue -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPPropertyBagValue ---- - -# Set-PnPPropertyBagValue - -## SYNOPSIS -Sets a property bag value - -## SYNTAX - -### Folder -```powershell -Set-PnPPropertyBagValue -Key <String> - -Value <String> - [-Folder <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Web -```powershell -Set-PnPPropertyBagValue -Key <String> - -Value <String> - -Indexed [<SwitchParameter>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPPropertyBagValue -Key MyKey -Value MyValue -``` - -This sets or adds a value to the current web property bag - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPPropertyBagValue -Key MyKey -Value MyValue -Folder / -``` - -This sets or adds a value to the root folder of the current web - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPPropertyBagValue -Key MyKey -Value MyValue -Folder /MyFolder -``` - -This sets or adds a value to the folder MyFolder which is located in the root folder of the current web - -## PARAMETERS - -### -Folder -Site relative url of the folder. See examples for use. - -```yaml -Type: String -Parameter Sets: Folder - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Indexed - - -```yaml -Type: SwitchParameter -Parameter Sets: Web - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Key - - -```yaml -Type: String -Parameter Sets: Web, Folder - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Value - - -```yaml -Type: String -Parameter Sets: Web, Folder, - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPProvisioningTemplateMetadata.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPProvisioningTemplateMetadata.md deleted file mode 100644 index 99b0624da3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPProvisioningTemplateMetadata.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpprovisioningtemplatemetadata -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPProvisioningTemplateMetadata ---- - -# Set-PnPProvisioningTemplateMetadata - -## SYNOPSIS -Sets metadata of a provisioning template - -## SYNTAX - -```powershell -Set-PnPProvisioningTemplateMetadata -Path <String> - [-TemplateDisplayName <String>] - [-TemplateImagePreviewUrl <String>] - [-TemplateProperties <Hashtable>] - [-TemplateProviderExtensions <ITemplateProviderExtension[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPProvisioningTemplateMetadata -Path template.xml -TemplateDisplayName "DisplayNameValue" -``` - -Sets the DisplayName property of a site template in XML format. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPProvisioningTemplateMetadata -Path template.pnp -TemplateDisplayName "DisplayNameValue" -``` - -Sets the DisplayName property of a site template in Office Open XML format. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPProvisioningTemplateMetadata -Path template.xml -TemplateImagePreviewUrl "Full URL of the Image Preview" -``` - -Sets the Url to the preview image of a site template in XML format. - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPProvisioningTemplateMetadata -Path template.pnp -TemplateImagePreviewUrl "Full URL of the Image Preview" -``` - -Sets the to the preview image of a site template in Office Open XML format. - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPProvisioningTemplateMetadata -Path template.xml -TemplateProperties @{"Property1" = "Test Value 1"; "Property2"="Test Value 2"} -``` - -Sets the property 'Property1' to the value 'Test Value 1' of a site template in XML format. - -### ------------------EXAMPLE 6------------------ -```powershell -Set-PnPProvisioningTemplateMetadata -Path template.pnp -TemplateProperties @{"Property1" = "Test Value 1"; "Property2"="Test Value 2"} -``` - -Sets the property 'Property1' to the value 'Test Value 1' of a site template in Office Open XML format. - -## PARAMETERS - -### -Path -Path to the xml or pnp file containing the site template. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -TemplateDisplayName -It can be used to specify the DisplayName of the template file that will be updated. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateImagePreviewUrl -It can be used to specify the ImagePreviewUrl of the template file that will be updated. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateProperties -It can be used to specify custom Properties for the template file that will be updated. - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TemplateProviderExtensions -Allows you to specify ITemplateProviderExtension to execute while extracting a template. - -```yaml -Type: ITemplateProviderExtension[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPRequestAccessEmails.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPRequestAccessEmails.md deleted file mode 100644 index 048510f868..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPRequestAccessEmails.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnprequestaccessemails -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPRequestAccessEmails ---- - -# Set-PnPRequestAccessEmails - -## SYNOPSIS -Sets Request Access Email on a web - -## SYNTAX - -```powershell -Set-PnPRequestAccessEmails [-Emails <String[]>] - [-Disabled [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Enables or disables access requests to be sent and configures which e-mail address should receive these requests. The web you apply this on must have unique rights. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPRequestAccessEmails -Emails someone@example.com -``` - -This will enable requesting access and send the requests to the provided e-mail address - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPRequestAccessEmails -Disabled -``` - -This will disable the ability to request access to the site - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPRequestAccessEmails -Disabled:$false -``` - -This will enable the ability to request access to the site and send the requests to the default owners of the site - -## PARAMETERS - -### -Disabled -Enables or disables access to be requested - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Emails -Email address to send the access requests to - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSearchConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSearchConfiguration.md deleted file mode 100644 index 72936451f0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSearchConfiguration.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpsearchconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPSearchConfiguration ---- - -# Set-PnPSearchConfiguration - -## SYNOPSIS -Sets the search configuration - -## SYNTAX - -### Config -```powershell -Set-PnPSearchConfiguration -Configuration <String> - [-Scope <SearchConfigurationScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### Path -```powershell -Set-PnPSearchConfiguration -Path <String> - [-Scope <SearchConfigurationScope>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSearchConfiguration -Configuration $config -``` - -Sets the search configuration for the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPSearchConfiguration -Configuration $config -Scope Site -``` - -Sets the search configuration for the current site collection - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPSearchConfiguration -Configuration $config -Scope Subscription -``` - -Sets the search configuration for the current tenant - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPSearchConfiguration -Path searchconfig.xml -Scope Subscription -``` - -Reads the search configuration from the specified XML file and sets it for the current tenant - -## PARAMETERS - -### -Configuration -Search configuration string - -```yaml -Type: String -Parameter Sets: Config - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Path -Path to a search configuration - -```yaml -Type: String -Parameter Sets: Path - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope - - -```yaml -Type: SearchConfigurationScope -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSearchSettings.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSearchSettings.md deleted file mode 100644 index 405f0bb83f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSearchSettings.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpsearchsettings -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPSearchSettings ---- - -# Set-PnPSearchSettings - -## SYNOPSIS -Sets search settings for a site - -## SYNTAX - -```powershell -Set-PnPSearchSettings [-SearchBoxInNavBar <SearchBoxInNavBarType>] - [-SearchPageUrl <String>] - [-SearchScope <SearchScopeType>] - [-Scope <SearchSettingsScope>] - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSearchSettings -SearchBoxInNavBar Hidden -Scope Site -``` - -Hide the suite bar search box on all pages and sites in the site collection - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPSearchSettings -SearchBoxInNavBar Hidden -Scope Web -``` - -Hide the suite bar search box on all pages in the current site - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPSearchSettings -SearchPageUrl "https://contoso.sharepoint.com/sites/mysearch/SitePages/search.aspx" -``` - -Redirect the suite bar search box in the site to a custom URL - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPSearchSettings -SearchPageUrl "" -``` - -Clear the suite bar search box URL and revert to the default behavior - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPSearchSettings -SearchPageUrl "https://contoso.sharepoint.com/sites/mysearch/SitePages/search.aspx" -Scope Site -``` - -Redirect classic search to a custom URL - -### ------------------EXAMPLE 6------------------ -```powershell -Set-PnPSearchSettings -SearchScope Tenant -``` - -Set default behavior of the suite bar search box to show tenant wide results instead of site or hub scoped results - -### ------------------EXAMPLE 7------------------ -```powershell -Set-PnPSearchSettings -SearchScope Hub -``` - -Set default behavior of the suite bar search box to show hub results instead of site results on an associated hub site - -## PARAMETERS - -### -Force -Do not ask for confirmation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Scope -Scope to apply the setting to. Possible values: Web (default), Site\r\n\r\nFor a root site, the scope does not matter. - -```yaml -Type: SearchSettingsScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SearchBoxInNavBar -Set the scope of which the suite bar search box shows. Possible values: Inherit, AllPages, ModernOnly, Hidden - -```yaml -Type: SearchBoxInNavBarType -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SearchPageUrl -Set the URL where the search box should redirect to. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SearchScope -Set the search scope of the suite bar search box. Possible values: DefaultScope, Tenant, Hub, Site - -```yaml -Type: SearchScopeType -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSite.md deleted file mode 100644 index f7221264c6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSite.md +++ /dev/null @@ -1,387 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPSite ---- - -# Set-PnPSite - -## SYNOPSIS -Sets Site Collection properties. - -## SYNTAX - -### Set Properties -```powershell -Set-PnPSite [-Classification <String>] - [-DisableFlows [<SwitchParameter>]] - [-LogoFilePath <String>] - [-Sharing <SharingCapabilities>] - [-StorageMaximumLevel <Int>] - [-StorageWarningLevel <Int>] - [-AllowSelfServiceUpgrade [<SwitchParameter>]] - [-NoScriptSite [<SwitchParameter>]] - [-Owners <String>] - [-CommentsOnSitePagesDisabled [<SwitchParameter>]] - [-DefaultLinkPermission <SharingPermissionType>] - [-DefaultSharingLinkType <SharingLinkType>] - [-DisableAppViews <AppViewsPolicy>] - [-DisableCompanyWideSharingLinks <CompanyWideSharingLinksPolicy>] - [-DisableSharingForNonOwners [<SwitchParameter>]] - [-LocaleId <UInt32>] - [-RestrictedToGeo <RestrictedToRegion>] - [-SocialBarOnSitePagesDisabled [<SwitchParameter>]] - [-Identity <String>] - [-Connection <SPOnlineConnection>] -``` - -### Set Lock State -```powershell -Set-PnPSite [-LockState <SiteLockState>] - [-Wait [<SwitchParameter>]] - [-Identity <String>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSite -Classification "HBI" -``` - -Sets the current site classification to HBI - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPSite -Classification $null -``` - -Unsets the current site classification - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPSite -DisableFlows -``` - -Disables Microsoft Flow for this site, and also hides the Flow button from the ribbon - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPSite -DisableFlows:$false -``` - -Enables Microsoft Flow for this site - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPSite -LogoFilePath c:\images\mylogo.png -``` - -Sets the logo if the site is a modern team site - -## PARAMETERS - -### -AllowSelfServiceUpgrade -Specifies if the site administrator can upgrade the site collection - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Classification -The classification to set - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: String -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CommentsOnSitePagesDisabled -Specifies if comments on site pages are enabled or disabled - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefaultLinkPermission -Specifies the default link permission for the site collection. None - Respect the organization default link permission. View - Sets the default link permission for the site to "view" permissions. Edit - Sets the default link permission for the site to "edit" permissions - -Only applicable to: SharePoint Online - -```yaml -Type: SharingPermissionType -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefaultSharingLinkType -Specifies the default link type for the site collection. None - Respect the organization default sharing link type. AnonymousAccess - Sets the default sharing link for this site to an Anonymous Access or Anyone link. Internal - Sets the default sharing link for this site to the "organization" link or company shareable link. Direct - Sets the default sharing link for this site to the "Specific people" link - -Only applicable to: SharePoint Online - -```yaml -Type: SharingLinkType -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableAppViews - - -Only applicable to: SharePoint Online - -```yaml -Type: AppViewsPolicy -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableCompanyWideSharingLinks - - -Only applicable to: SharePoint Online - -```yaml -Type: CompanyWideSharingLinksPolicy -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableFlows -Disables Microsoft Flow for this site - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableSharingForNonOwners -Specifies to prevent non-owners from inviting new users to the site - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Url - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LocaleId -Specifies the language of this site collection. - -```yaml -Type: UInt32 -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LockState -Sets the lockstate of a site - -Only applicable to: SharePoint Online - -```yaml -Type: SiteLockState -Parameter Sets: Set Lock State - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LogoFilePath -Sets the logo of the site if it concerns a modern team site. Provide a full path to a local image file on your disk which you want to use as the site logo. The logo will be uploaded automatically to SharePoint. If you want to set the logo for a classic site, use Set-PnPWeb -SiteLogoUrl. - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NoScriptSite -Specifies if a site allows custom script or not. See https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off-1f2c515f-5d7e-448a-9fd7-835da935584f for more information. - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties -Aliases: DenyAndAddCustomizePages - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owners -Specifies owner(s) to add as site collection administrators. They will be added as additional site collection administrators. Existing administrators will stay. Can be both users and groups. - -```yaml -Type: String -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RestrictedToGeo -Specifies the Geo/Region restrictions of this site. - -Only applicable to: SharePoint Online - -```yaml -Type: RestrictedToRegion -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Sharing -Specifies what the sharing capabilities are for the site. Possible values: Disabled, ExternalUserSharingOnly, ExternalUserAndGuestSharing, ExistingExternalUserSharingOnly - -Only applicable to: SharePoint Online - -```yaml -Type: SharingCapabilities -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SocialBarOnSitePagesDisabled -Disables or enables the Social Bar for Site Collection. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StorageMaximumLevel -Specifies the storage quota for this site collection in megabytes. This value must not exceed the company's available quota. - -Only applicable to: SharePoint Online - -```yaml -Type: Int -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StorageWarningLevel -Specifies the warning level for the storage quota in megabytes. This value must not exceed the values set for the StorageMaximumLevel parameter - -Only applicable to: SharePoint Online - -```yaml -Type: Int -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Wait -Wait for the operation to complete - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Set Lock State - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteClosure.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteClosure.md deleted file mode 100644 index 2fbdb27ded..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteClosure.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpsiteclosure -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPSiteClosure ---- - -# Set-PnPSiteClosure - -## SYNOPSIS -Opens or closes a site which has a site policy applied - -## SYNTAX - -```powershell -Set-PnPSiteClosure -State <ClosureState> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSiteClosure -State Open -``` - -This opens a site which has been closed and has a site policy applied. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPSiteClosure -State Closed -``` - -This closes a site which is open and has a site policy applied. - -## PARAMETERS - -### -State -The state of the site - -```yaml -Type: ClosureState -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteDesign.md deleted file mode 100644 index 53e304c171..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteDesign.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpsitedesign -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPSiteDesign ---- - -# Set-PnPSiteDesign - -## SYNOPSIS -Updates a Site Design on the current tenant. - -## SYNTAX - -```powershell -Set-PnPSiteDesign -Identity <TenantSiteDesignPipeBind> - [-Title <String>] - [-SiteScriptIds <GuidPipeBind[]>] - [-Description <String>] - [-IsDefault [<SwitchParameter>]] - [-PreviewImageAltText <String>] - [-PreviewImageUrl <String>] - [-WebTemplate <SiteWebTemplate>] - [-Version <Int>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSiteDesign -Identity 046e2e76-67ba-46ca-a5f6-8eb418a7821e -Title "My Updated Company Design" -``` - -Updates an existing Site Design and sets a new title. - -### ------------------EXAMPLE 2------------------ -```powershell -$design = Get-PnPSiteDesign -Identity 046e2e76-67ba-46ca-a5f6-8eb418a7821e -Set-PnPSiteDesign -Identity $design -Title "My Updated Company Design" -``` - -Updates an existing Site Design and sets a new title. - -## PARAMETERS - -### -Description -The description of the site design - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The guid or an object representing the site design - -```yaml -Type: TenantSiteDesignPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -IsDefault -Specifies if the site design is a default site design - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PreviewImageAltText -Sets the text for the preview image - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PreviewImageUrl -Sets the url to the preview image - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SiteScriptIds -An array of guids of site scripts - -```yaml -Type: GuidPipeBind[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the site design - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Version -Specifies the version of the design - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -WebTemplate -Specifies the type of site to which this design applies - -```yaml -Type: SiteWebTemplate -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSitePolicy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSitePolicy.md deleted file mode 100644 index e580cd9f62..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSitePolicy.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpsitepolicy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPSitePolicy ---- - -# Set-PnPSitePolicy - -## SYNOPSIS -Sets a site policy - -## SYNTAX - -```powershell -Set-PnPSitePolicy -Name <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSitePolicy -Name "Contoso HBI" -``` - -This applies a site policy with the name "Contoso HBI" to the current site. The policy needs to be available in the site. - -## PARAMETERS - -### -Name -The name of the site policy to apply - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteScript.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteScript.md deleted file mode 100644 index bfd35667e7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSiteScript.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpsitescript -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPSiteScript ---- - -# Set-PnPSiteScript - -## SYNOPSIS -Updates an existing Site Script on the current tenant. - -## SYNTAX - -```powershell -Set-PnPSiteScript -Identity <TenantSiteScriptPipeBind> - [-Title <String>] - [-Description <String>] - [-Content <String>] - [-Version <Int>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPSiteScript -Identity f1d55d9b-b116-4f54-bc00-164a51e7e47f -Title "My Site Script" -``` - -Updates an existing Site Script and changes the title. - -### ------------------EXAMPLE 2------------------ -```powershell -$script = Get-PnPSiteScript -Identity f1d55d9b-b116-4f54-bc00-164a51e7e47f -Set-PnPSiteScript -Identity $script -Title "My Site Script" -``` - -Updates an existing Site Script and changes the title. - -## PARAMETERS - -### -Content -A JSON string containing the site script - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description of the site script - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The guid or an object representing the site script - -```yaml -Type: TenantSiteScriptPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Title -The title of the site script - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Version -Specifies the version of the site script - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPStorageEntity.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPStorageEntity.md deleted file mode 100644 index 93aaef91a5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPStorageEntity.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpstorageentity -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPStorageEntity ---- - -# Set-PnPStorageEntity - -## SYNOPSIS -Set Storage Entities / Farm Properties in either the tenant scoped app catalog or the site collection app catalog. - -## SYNTAX - -```powershell -Set-PnPStorageEntity -Key <String> - -Value <String> - [-Comment <String>] - [-Description <String>] - [-Scope <StorageEntityScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPStorageEntity -Key MyKey -Value "MyValue" -Comment "My Comment" -Description "My Description" -``` - -Sets an existing or adds a new storage entity / farm property at tenant level. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPStorageEntity -Scope Site -Key MyKey -Value "MyValue" -Comment "My Comment" -Description "My Description" -``` - -Sets an existing or adds a new storage entity site collection level. - -## PARAMETERS - -### -Comment -The comment to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The description to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Key -The key of the value to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Scope -Defines the scope of the storage entity. Defaults to Tenant. - -```yaml -Type: StorageEntityScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Value -The value to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTaxonomyFieldValue.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTaxonomyFieldValue.md deleted file mode 100644 index 8ee1325eda..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTaxonomyFieldValue.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptaxonomyfieldvalue -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPTaxonomyFieldValue ---- - -# Set-PnPTaxonomyFieldValue - -## SYNOPSIS -Sets a taxonomy term value in a listitem field - -## SYNTAX - -### ITEMS -```powershell -Set-PnPTaxonomyFieldValue -ListItem <ListItem> - -InternalFieldName <String> - [-Terms <Hashtable>] - [-Connection <SPOnlineConnection>] -``` - -### ITEM -```powershell -Set-PnPTaxonomyFieldValue -TermId <GuidPipeBind> - -ListItem <ListItem> - -InternalFieldName <String> - [-Label <String>] - [-Connection <SPOnlineConnection>] -``` - -### PATH -```powershell -Set-PnPTaxonomyFieldValue -TermPath <String> - -ListItem <ListItem> - -InternalFieldName <String> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTaxonomyFieldValue -ListItem $item -InternalFieldName 'Department' -TermId 863b832b-6818-4e6a-966d-2d3ee057931c -``` - -Sets the field called 'Department' to the value of the term with the ID specified - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPTaxonomyFieldValue -ListItem $item -InternalFieldName 'Department' -TermPath 'CORPORATE|DEPARTMENTS|HR' -``` - -Sets the field called 'Department' to the term called HR which is located in the DEPARTMENTS termset, which in turn is located in the CORPORATE termgroup. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPTaxonomyFieldValue -ListItem $item -InternalFieldName 'Department' -Terms @{"TermId1"="Label1";"TermId2"="Label2"} -``` - -Sets the field called 'Department' with multiple terms by ID and label. You can refer to those terms with the {ID:label} token. - -## PARAMETERS - -### -InternalFieldName -The internal name of the field - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Label -The Label value of the term - -```yaml -Type: String -Parameter Sets: ITEM - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ListItem -The list item to set the field value to - -```yaml -Type: ListItem -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TermId -The Id of the Term - -```yaml -Type: GuidPipeBind -Parameter Sets: ITEM - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -TermPath -A path in the form of GROUPLABEL|TERMSETLABEL|TERMLABEL - -```yaml -Type: String -Parameter Sets: PATH - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Terms -Allows you to specify terms with key value pairs that can be referred to in the template by means of the {id:label} token. See examples on how to use this parameter. - -```yaml -Type: Hashtable -Parameter Sets: ITEMS - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenant.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenant.md deleted file mode 100644 index ee8b83d8c9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenant.md +++ /dev/null @@ -1,1020 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptenant -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPTenant ---- - -# Set-PnPTenant - -## SYNOPSIS -Sets organization-level site collection properties - -## SYNTAX - -```powershell -Set-PnPTenant [-MinCompatibilityLevel <Int>] - [-MaxCompatibilityLevel <Int>] - [-ExternalServicesEnabled <Boolean>] - [-NoAccessRedirectUrl <String>] - [-SharingCapability <SharingCapabilities>] - [-DisplayStartASiteOption <Boolean>] - [-StartASiteFormUrl <String>] - [-ShowEveryoneClaim <Boolean>] - [-ShowAllUsersClaim <Boolean>] - [-ShowEveryoneExceptExternalUsersClaim <Boolean>] - [-SearchResolveExactEmailOrUPN <Boolean>] - [-OfficeClientADALDisabled <Boolean>] - [-LegacyAuthProtocolsEnabled <Boolean>] - [-RequireAcceptingAccountMatchInvitedAccount <Boolean>] - [-ProvisionSharedWithEveryoneFolder <Boolean>] - [-SignInAccelerationDomain <String>] - [-EnableGuestSignInAcceleration <Boolean>] - [-UsePersistentCookiesForExplorerView <Boolean>] - [-BccExternalSharingInvitations <Boolean>] - [-BccExternalSharingInvitationsList <String>] - [-UserVoiceForFeedbackEnabled <Boolean>] - [-PublicCdnEnabled <Boolean>] - [-PublicCdnAllowedFileTypes <String>] - [-RequireAnonymousLinksExpireInDays <Int>] - [-SharingAllowedDomainList <String>] - [-SharingBlockedDomainList <String>] - [-SharingDomainRestrictionMode <SharingDomainRestrictionModes>] - [-OneDriveStorageQuota <Int>] - [-OneDriveForGuestsEnabled <Boolean>] - [-IPAddressEnforcement <Boolean>] - [-IPAddressAllowList <String>] - [-IPAddressWACTokenLifetime <Int>] - [-UseFindPeopleInPeoplePicker <Boolean>] - [-DefaultSharingLinkType <SharingLinkType>] - [-ODBMembersCanShare <SharingState>] - [-ODBAccessRequests <SharingState>] - [-PreventExternalUsersFromResharing <Boolean>] - [-ShowPeoplePickerSuggestionsForGuestUsers <Boolean>] - [-FileAnonymousLinkType <AnonymousLinkType>] - [-FolderAnonymousLinkType <AnonymousLinkType>] - [-NotifyOwnersWhenItemsReshared <Boolean>] - [-NotifyOwnersWhenInvitationsAccepted <Boolean>] - [-NotificationsInOneDriveForBusinessEnabled <Boolean>] - [-NotificationsInSharePointEnabled <Boolean>] - [-OwnerAnonymousNotification <Boolean>] - [-CommentsOnSitePagesDisabled <Boolean>] - [-SocialBarOnSitePagesDisabled <Boolean>] - [-OrphanedPersonalSitesRetentionPeriod <Int>] - [-DisallowInfectedFileDownload <Boolean>] - [-DefaultLinkPermission <SharingPermissionType>] - [-ConditionalAccessPolicy <SPOConditionalAccessPolicyType>] - [-AllowDownloadingNonWebViewableFiles <Boolean>] - [-AllowEditing <Boolean>] - [-ApplyAppEnforcedRestrictionsToAdHocRecipients <Boolean>] - [-FilePickerExternalImageSearchEnabled <Boolean>] - [-EmailAttestationRequired <Boolean>] - [-EmailAttestationReAuthDays <Int>] - [-HideDefaultThemes <Boolean>] - [-DisabledWebPartIds <Guid[]>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets organization-level site collection properties such as StorageQuota, StorageQuotaAllocated, ResourceQuota, -ResourceQuotaAllocated, and SiteCreationMode. - -You must have the SharePoint Online admin or Global admin role to run the cmdlet. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTenantSite -Identity https://contoso.sharepoint.com/sites/team1 -LockState NoAccess -Set-PnPTenant -NoAccessRedirectUrl 'http://www.contoso.com/' -``` - -This example blocks access to https://contoso.sharepoint.com/sites/team1 and redirects traffic to http://www.contoso.com. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPTenant -ShowEveryoneExceptExternalUsersClaim $false -``` - -This example hides the "Everyone Except External Users" claim in People Picker. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPTenant -ShowAllUsersClaim $false -``` - -This example hides the "All Users" claim group in People Picker. - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPTenant -UsePersistentCookiesForExplorerView $true -``` - -This example enables the use of special persisted cookie for Open with Explorer. - -## PARAMETERS - -### -AllowDownloadingNonWebViewableFiles - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -AllowEditing - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ApplyAppEnforcedRestrictionsToAdHocRecipients - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -BccExternalSharingInvitations -When the feature is enabled, all external sharing invitations that are sent will blind copy the e-mail messages listed in the BccExternalSharingInvitationsList. - -The valid values are: -False (default) - BCC for external sharing is disabled. -True - All external sharing invitations that are sent will blind copy the e-mail messages listed in the BccExternalSharingInvitationsList. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -BccExternalSharingInvitationsList -Specifies a list of e-mail addresses to be BCC'd when the BCC for External Sharing feature is enabled. -Multiple addresses can be specified by creating a comma separated list with no spaces. - -The valid values are: -"" (default) - Blank by default, this will also clear any value that has been set. -Single or Multiple e-mail addresses - joe@contoso.com or joe@contoso.com,bob@contoso.com - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CommentsOnSitePagesDisabled - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ConditionalAccessPolicy - - -```yaml -Type: SPOConditionalAccessPolicyType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefaultLinkPermission - - -```yaml -Type: SharingPermissionType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefaultSharingLinkType -Lets administrators choose what type of link appears is selected in the “Get a link” sharing dialog box in OneDrive for Business and SharePoint Online. - -For additional information about how to change the default link type, see Change the default link type when users get links for sharing. - -Note: -Setting this value to “none” will default “get a link” to the most permissive link available (that is, if anonymous links are enabled, the default link will be anonymous access; if they are disabled then the default link will be internal. - -The values are: None Direct Internal AnonymousAccess - -```yaml -Type: SharingLinkType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisabledWebPartIds -Guids of out of the box modern web part id's to hide - -```yaml -Type: Guid[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisallowInfectedFileDownload -Prevents the Download button from being displayed on the Virus Found warning page. - -Accepts a value of true (enabled) to hide the Download button or false (disabled) to display the Download button. By default this feature is set to false. - - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisplayStartASiteOption -Determines whether tenant users see the Start a Site menu option. - -The valid values are: -True (default) - Tenant users will see the Start a Site menu option. -False - Start a Site is hidden from the menu. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EmailAttestationReAuthDays - - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EmailAttestationRequired - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableGuestSignInAcceleration -Accelerates guest-enabled site collections as well as member-only site collections when the SignInAccelerationDomain parameter is set. - -Note: -If enabled, your identity provider must be capable of authenticating guest users. If it is not, guest users will be unable to log in and access content that was shared with them. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ExternalServicesEnabled -Enables external services for a tenant. -External services are defined as services that are not in the Office 365 datacenters. - -The valid values are: -True (default) - External services are enabled for the tenant. -False - External services that are outside of the Office 365 datacenters cannot interact with SharePoint. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -FileAnonymousLinkType - - -```yaml -Type: AnonymousLinkType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -FilePickerExternalImageSearchEnabled - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -FolderAnonymousLinkType - - -```yaml -Type: AnonymousLinkType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HideDefaultThemes -Defines if the default themes are visible or hidden - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IPAddressAllowList -Configures multiple IP addresses or IP address ranges (IPv4 or IPv6). - -Use commas to separate multiple IP addresses or IP address ranges. Verify there are no overlapping IP addresses and ensure IP ranges use Classless Inter-Domain Routing (CIDR) notation. For example, 172.16.0.0, 192.168.1.0/27. - -Note: -The IPAddressAllowList parameter only lets administrators set IP addresses or ranges that are recognized as trusted. To only grant access from these IP addresses or ranges, set the IPAddressEnforcement parameter to $true. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IPAddressEnforcement -Allows access from network locations that are defined by an administrator. - -The values are $true and $false. The default value is $false which means the setting is disabled. - -Before the IPAddressEnforcement parameter is set, make sure you add a valid IPv4 or IPv6 address to the IPAddressAllowList parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IPAddressWACTokenLifetime - - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LegacyAuthProtocolsEnabled -By default this value is set to $true. - -Setting this parameter prevents Office clients using non-modern authentication protocols from accessing SharePoint Online resources. - -A value of $true - Enables Office clients using non-modern authentication protocols(such as, Forms-Based Authentication (FBA) or Identity Client Runtime Library (IDCRL)) to access SharePoint resources. - -A value of $false - Prevents Office clients using non-modern authentication protocols from accessing SharePoint Online resources. - -Note: -This may also prevent third-party apps from accessing SharePoint Online resources.Also, this will also block apps using the SharePointOnlineCredentials class to access SharePoint Online resources.For additional information about SharePointOnlineCredentials, see SharePointOnlineCredentials class. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MaxCompatibilityLevel -Specifies the upper bound on the compatibility level for new sites. - -```yaml -Type: Int -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MinCompatibilityLevel -Specifies the lower bound on the compatibility level for new sites. - -```yaml -Type: Int -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NoAccessRedirectUrl -Specifies the URL of the redirected site for those site collections which have the locked state "NoAccess" - -The valid values are: -""(default) - Blank by default, this will also remove or clear any value that has been set. -Full URL - Example: https://contoso.sharepoint.com/Pages/Locked.aspx - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NotificationsInOneDriveForBusinessEnabled - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NotificationsInSharePointEnabled - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NotifyOwnersWhenInvitationsAccepted -When this parameter is set to $true and when an external user accepts an invitation to a resource in a user’s OneDrive for Business, the OneDrive for Business owner is notified by e-mail. - -For additional information about how to configure notifications for external sharing, see Configure notifications for external sharing for OneDrive for Business. - -The values are $true and $false. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NotifyOwnersWhenItemsReshared -When this parameter is set to $true and another user re-shares a document from a user’s OneDrive for Business, the OneDrive for Business owner is notified by e-mail. - -For additional information about how to configure notifications for external sharing, see Configure notifications for external sharing for OneDrive for Business. - -The values are $true and $false. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ODBAccessRequests -Lets administrators set policy on access requests and requests to share in OneDrive for Business. - -Values: - -On- Users without permission to share can trigger sharing requests to the OneDrive for Business owner when they attempt to share. Also, users without permission to a file or folder can trigger access requests to the OneDrive for Business owner when they attempt to access an item they do not have permissions to. - -Off- Prevent access requests and requests to share on OneDrive for Business. - -Unspecified- Let each OneDrive for Business owner enable or disable access requests and requests to share on their OneDrive. - -```yaml -Type: SharingState -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ODBMembersCanShare -Lets administrators set policy on re-sharing behavior in OneDrive for Business. - -Values: - -On- Users with edit permissions can re-share. - -Off- Only OneDrive for Business owner can share. The value of ODBAccessRequests defines whether a request to share gets sent to the owner. - -Unspecified- Let each OneDrive for Business owner enable or disable re-sharing behavior on their OneDrive. - -```yaml -Type: SharingState -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OfficeClientADALDisabled -When set to true this will disable the ability to use Modern Authentication that leverages ADAL across the tenant. - -The valid values are: -False (default) - Modern Authentication is enabled/allowed. -True - Modern Authentication via ADAL is disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OneDriveForGuestsEnabled -Lets OneDrive for Business creation for administrator managed guest users. Administrator managed Guest users use credentials in the resource tenant to access the resources. - -The valid values are the following: - -$true-Administrator managed Guest users can be given OneDrives, provided needed licenses are assigned. - -$false- Administrator managed Guest users can't be given OneDrives as functionality is turned off. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OneDriveStorageQuota -Sets a default OneDrive for Business storage quota for the tenant. It will be used for new OneDrive for Business sites created. - -A typical use will be to reduce the amount of storage associated with OneDrive for Business to a level below what the License entitles the users. For example, it could be used to set the quota to 10 gigabytes (GB) by default. - -If value is set to 0, the parameter will have no effect. - -If the value is set larger than the Maximum allowed OneDrive for Business quota, it will have no effect. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OrphanedPersonalSitesRetentionPeriod -Specifies the number of days after a user's Active Directory account is deleted that their OneDrive for Business content will be deleted. - -The value range is in days, between 30 and 3650. The default value is 30. - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -OwnerAnonymousNotification - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PreventExternalUsersFromResharing - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ProvisionSharedWithEveryoneFolder -Creates a Shared with Everyone folder in every user's new OneDrive for Business document library. - -The valid values are: -True (default) - The Shared with Everyone folder is created. -False - No folder is created when the site and OneDrive for Business document library is created. - -The default behavior of the Shared with Everyone folder changed in August 2015. -For additional information about the change, see Provision the Shared with Everyone folder in OneDrive for Business (https://support.office.com/en-us/article/Provision-the-Shared-with-Everyone-folder-in-OneDrive-for-Business-6bb02c91-fd0b-42ba-9457-3921cb6dc5b2?ui=en-US&rs=en-US&ad=US) - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PublicCdnAllowedFileTypes - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PublicCdnEnabled - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RequireAcceptingAccountMatchInvitedAccount -Ensures that an external user can only accept an external sharing invitation with an account matching the invited email address. - -Administrators who desire increased control over external collaborators should consider enabling this feature. - -Note, this only applies to new external users accepting new sharing invitations. Also, the resource owner must share with an organizational or Microsoft account or the external user will be unable to access the resource. - -The valid values are: -False (default) - When a document is shared with an external user, bob@contoso.com, it can be accepted by any user with access to the invitation link in the original e-mail. -True - User must accept this invitation with bob@contoso.com. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RequireAnonymousLinksExpireInDays -Specifies all anonymous links that have been created (or will be created) will expire after the set number of days . - -To remove the expiration requirement, set the value to zero (0). - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SearchResolveExactEmailOrUPN -Removes the search capability from People Picker. Note, recently resolved names will still appear in the list until browser cache is cleared or expired. - -SharePoint Administrators will still be able to use starts with or partial name matching when enabled. - -The valid values are: -False (default) - Starts with / partial name search functionality is available. -True - Disables starts with / partial name search functionality for all SharePoint users, except SharePoint Admins. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingAllowedDomainList -Specifies a list of email domains that is allowed for sharing with the external collaborators. Use the space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -For additional information about how to restrict a domain sharing, see Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingBlockedDomainList -Specifies a list of email domains that is blocked or prohibited for sharing with the external collaborators. Use space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -For additional information about how to restrict a domain sharing, see Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingCapability -Determines what level of sharing is available for the site. - -The valid values are: -ExternalUserAndGuestSharing (default) - External user sharing (share by email) and guest link sharing are both enabled. Disabled - External user sharing (share by email) and guest link sharing are both disabled. -ExternalUserSharingOnly - External user sharing (share by email) is enabled, but guest link sharing is disabled. - -For more information about sharing, see Manage external sharing for your SharePoint online environment (http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/manage-external-sharing-for-your-sharepoint-online-environment-HA102849864.aspx). - -```yaml -Type: SharingCapabilities -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingDomainRestrictionMode -Specifies the external sharing mode for domains. - -The following values are: None AllowList BlockList - -For additional information about how to restrict a domain sharing, see Restricted Domains Sharing in Office 365 SharePoint Online and OneDrive for Business. - -```yaml -Type: SharingDomainRestrictionModes -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShowAllUsersClaim -Enables the administrator to hide the All Users claim groups in People Picker. - -When users share an item with "All Users (x)", it is accessible to all organization members in the tenant's Azure Active Directory who have authenticated with via this method. When users share an item with "All Users (x)" it is accessible to all organization members in the tenant that used NTLM to authentication with SharePoint. - -Note, the All Users(authenticated) group is equivalent to the Everyone claim, and shows as Everyone.To change this, see - ShowEveryoneClaim. - -The valid values are: -True(default) - The All Users claim groups are displayed in People Picker. -False - The All Users claim groups are hidden in People Picker. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShowEveryoneClaim -Enables the administrator to hide the Everyone claim in the People Picker. -When users share an item with Everyone, it is accessible to all authenticated users in the tenant's Azure Active Directory, including any active external users who have previously accepted invitations. - -Note, that some SharePoint system resources such as templates and pages are required to be shared to Everyone and this type of sharing does not expose any user data or metadata. - -The valid values are: -True (default) - The Everyone claim group is displayed in People Picker. -False - The Everyone claim group is hidden from the People Picker. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShowEveryoneExceptExternalUsersClaim -Enables the administrator to hide the "Everyone except external users" claim in the People Picker. -When users share an item with "Everyone except external users", it is accessible to all organization members in the tenant's Azure Active Directory, but not to any users who have previously accepted invitations. - -The valid values are: -True(default) - The Everyone except external users is displayed in People Picker. -False - The Everyone except external users claim is not visible in People Picker. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ShowPeoplePickerSuggestionsForGuestUsers - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SignInAccelerationDomain -Specifies the home realm discovery value to be sent to Azure Active Directory (AAD) during the user sign-in process. - -When the organization uses a third-party identity provider, this prevents the user from seeing the Azure Active Directory Home Realm Discovery web page and ensures the user only sees their company's Identity Provider's portal. -This value can also be used with Azure Active Directory Premium to customize the Azure Active Directory login page. - -Acceleration will not occur on site collections that are shared externally. - -This value should be configured with the login domain that is used by your company (that is, example@contoso.com). - -If your company has multiple third-party identity providers, configuring the sign-in acceleration value will break sign-in for your organization. - -The valid values are: -"" (default) - Blank by default, this will also remove or clear any value that has been set. -Login Domain - For example: "contoso.com" - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SocialBarOnSitePagesDisabled - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StartASiteFormUrl -Specifies URL of the form to load in the Start a Site dialog. - -The valid values are: -"" (default) - Blank by default, this will also remove or clear any value that has been set. -Full URL - Example: "https://contoso.sharepoint.com/path/to/form" - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UseFindPeopleInPeoplePicker -Note: -When set to $true, users aren't able to share with security groups or SharePoint groups. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UsePersistentCookiesForExplorerView -Lets SharePoint issue a special cookie that will allow this feature to work even when "Keep Me Signed In" is not selected. - -"Open with Explorer" requires persisted cookies to operate correctly. -When the user does not select "Keep Me Signed in" at the time of sign -in, "Open with Explorer" will fail. - -This special cookie expires after 30 minutes and cannot be cleared by closing the browser or signing out of SharePoint Online.To clear this cookie, the user must log out of their Windows session. - -The valid values are: -False(default) - No special cookie is generated and the normal Office 365 sign -in length / timing applies. -True - Generates a special cookie that will allow "Open with Explorer" to function if the "Keep Me Signed In" box is not checked at sign -in. - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UserVoiceForFeedbackEnabled - - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantAppCatalogUrl.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantAppCatalogUrl.md deleted file mode 100644 index 422cd32444..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantAppCatalogUrl.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptenantappcatalogurl -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPTenantAppCatalogUrl ---- - -# Set-PnPTenantAppCatalogUrl - -## SYNOPSIS -Sets the url of the tenant scoped app catalog - -## SYNTAX - -```powershell -Set-PnPTenantAppCatalogUrl -Url <String> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTenantAppCatalogUrl -Url https://yourtenant.sharepoint.com/sites/appcatalog -``` - -Sets the tenant scoped app catalog to the provided site collection url - -## PARAMETERS - -### -Url -The url of the site to set as the tenant scoped app catalog - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnEnabled.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnEnabled.md deleted file mode 100644 index d81602ccc5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnEnabled.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptenantcdnenabled -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPTenantCdnEnabled ---- - -# Set-PnPTenantCdnEnabled - -## SYNOPSIS -Enables or disabled the public or private Office 365 Content Delivery Network (CDN). - -## SYNTAX - -```powershell -Set-PnPTenantCdnEnabled -Enable <Boolean> - -CdnType <CdnType> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Enables or disabled the public or private Office 365 Content Delivery Network (CDN). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTenantCdnEnabled -CdnType Public -Enable $true -``` - -This example sets the Public CDN enabled. - -## PARAMETERS - -### -CdnType -The type of cdn to enable or disable - -```yaml -Type: CdnType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Enable -Specify to enable or disable - -```yaml -Type: Boolean -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnPolicy.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnPolicy.md deleted file mode 100644 index 7bf563227a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnPolicy.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptenantcdnpolicy -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPTenantCdnPolicy ---- - -# Set-PnPTenantCdnPolicy - -## SYNOPSIS -Sets the CDN Policies for the specified CDN (Public | Private). - -## SYNTAX - -```powershell -Set-PnPTenantCdnPolicy -CdnType <SPOTenantCdnType> - -PolicyType <SPOTenantCdnPolicyType> - -PolicyValue <String> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets the CDN Policies for the specified CDN (Public | Private). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTenantCdnPolicy -CdnType Public -PolicyType IncludeFileExtensions -PolicyValue "CSS,EOT,GIF,ICO,JPEG,JPG,JS,MAP,PNG,SVG,TTF,WOFF" -``` - -This example sets the IncludeFileExtensions policy to the specified value. - -## PARAMETERS - -### -CdnType -The type of cdn to retrieve the policies from - -```yaml -Type: SPOTenantCdnType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PolicyType -The type of the policy to set - -```yaml -Type: SPOTenantCdnPolicyType -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PolicyValue -The value of the policy to set - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantSite.md deleted file mode 100644 index 6c581e268f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantSite.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptenantsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPTenantSite ---- - -# Set-PnPTenantSite - -## SYNOPSIS -Set site information. - -## SYNTAX - -### Set Properties -```powershell -Set-PnPTenantSite -Url <String> - [-Title <String>] - [-LocaleId <UInt32>] - [-AllowSelfServiceUpgrade [<SwitchParameter>]] - [-Owners <String>] - [-DenyAddAndCustomizePages [<SwitchParameter>]] - [-SharingCapability <SharingCapabilities>] - [-StorageMaximumLevel <Int>] - [-StorageWarningLevel <Int>] - [-DefaultLinkPermission <SharingPermissionType>] - [-DefaultSharingLinkType <SharingLinkType>] - [-SharingAllowedDomainList <String>] - [-SharingBlockedDomainList <String>] - [-BlockDownloadOfNonViewableFiles [<SwitchParameter>]] - [-SharingDomainRestrictionMode <SharingDomainRestrictionModes>] - [-CommentsOnSitePagesDisabled [<SwitchParameter>]] - [-DisableAppViews <AppViewsPolicy>] - [-DisableCompanyWideSharingLinks <CompanyWideSharingLinksPolicy>] - [-DisableFlows <FlowsPolicy>] - [-Wait [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -### Set Lock State -```powershell -Set-PnPTenantSite -Url <String> - [-LockState <SiteLockState>] - [-Wait [<SwitchParameter>]] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets site properties for existing sites. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTenantSite -Url https://contoso.sharepoint.com -Title "Contoso Website" -Sharing Disabled -``` - -This will set the title of the site collection with the URL 'https://contoso.sharepoint.com/' to 'Contoso Website' and disable sharing on this site collection. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPTenantSite -Url https://contoso.sharepoint.com -Title "Contoso Website" -StorageWarningLevel 8000 -StorageMaximumLevel 10000 -``` - -This will set the title of the site collection with the URL 'https://contoso.sharepoint.com/' to 'Contoso Website', set the storage warning level to 8GB and set the storage maximum level to 10GB. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPTenantSite -Url https://contoso.sharepoint.com/sites/sales -Owners "user@contoso.onmicrosoft.com" -``` - -This will add user@contoso.onmicrosoft.com as an additional site collection owner at 'https://contoso.sharepoint.com/sites/sales'. - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPTenantSite -Url https://contoso.sharepoint.com/sites/sales -Owners @("user1@contoso.onmicrosoft.com", "user2@contoso.onmicrosoft.com") -``` - -This will add user1@contoso.onmicrosoft.com and user2@contoso.onmicrosoft.com as additional site collection owners at 'https://contoso.sharepoint.com/sites/sales'. - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPTenantSite -Url https://contoso.sharepoint.com/sites/sales -NoScriptSite:$false -``` - -This will enable script support for the site 'https://contoso.sharepoint.com/sites/sales' if disabled. - -## PARAMETERS - -### -AllowSelfServiceUpgrade -Specifies if the site administrator can upgrade the site collection - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -BlockDownloadOfNonViewableFiles -Specifies if non web viewable files can be downloaded. - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CommentsOnSitePagesDisabled -Specifies if comments on site pages are enabled - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefaultLinkPermission -Specifies the default link permission for the site collection. None - Respect the organization default link permission. View - Sets the default link permission for the site to "view" permissions. Edit - Sets the default link permission for the site to "edit" permissions - -Only applicable to: SharePoint Online - -```yaml -Type: SharingPermissionType -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefaultSharingLinkType -Specifies the default link type for the site collection. None - Respect the organization default sharing link type. AnonymousAccess - Sets the default sharing link for this site to an Anonymous Access or Anyone link. Internal - Sets the default sharing link for this site to the "organization" link or company shareable link. Direct - Sets the default sharing link for this site to the "Specific people" link - -Only applicable to: SharePoint Online - -```yaml -Type: SharingLinkType -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DenyAddAndCustomizePages -Determines whether the Add And Customize Pages right is denied on the site collection. For more information about permission levels, see User permissions and permission levels in SharePoint. - -```yaml -Type: SwitchParameter -Parameter Sets: Set Properties -Aliases: NoScriptSite - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableAppViews -- - -Only applicable to: SharePoint Online - -```yaml -Type: AppViewsPolicy -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableCompanyWideSharingLinks -- - -Only applicable to: SharePoint Online - -```yaml -Type: CompanyWideSharingLinksPolicy -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisableFlows -- - -Only applicable to: SharePoint Online - -```yaml -Type: FlowsPolicy -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LocaleId -Specifies the language of this site collection. For more information, see Locale IDs Assigned by Microsoft (https://go.microsoft.com/fwlink/p/?LinkId=242911). - -```yaml -Type: UInt32 -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LockState -Sets the lockstate of a site - -Only applicable to: SharePoint Online - -```yaml -Type: SiteLockState -Parameter Sets: Set Lock State - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owners -Specifies owner(s) to add as site collection administrators. They will be added as additional site collection administrators. Existing administrators will stay. Can be both users and groups. - -```yaml -Type: String -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingAllowedDomainList -Specifies a list of email domains that is allowed for sharing with the external collaborators. Use the space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingBlockedDomainList -Specifies a list of email domains that is blocked for sharing with the external collaborators. Use the space character as the delimiter for entering multiple values. For example, "contoso.com fabrikam.com". - -Only applicable to: SharePoint Online - -```yaml -Type: String -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingCapability -Specifies what the sharing capabilities are for the site. Possible values: Disabled, ExternalUserSharingOnly, ExternalUserAndGuestSharing, ExistingExternalUserSharingOnly - -Only applicable to: SharePoint Online - -```yaml -Type: SharingCapabilities -Parameter Sets: Set Properties -Aliases: Sharing - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SharingDomainRestrictionMode -Specifies the external sharing mode for domains. - -Only applicable to: SharePoint Online - -```yaml -Type: SharingDomainRestrictionModes -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StorageMaximumLevel -Specifies the storage quota for this site collection in megabytes. This value must not exceed the company's available quota. - -Only applicable to: SharePoint Online - -```yaml -Type: Int -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StorageWarningLevel -Specifies the warning level for the storage quota in megabytes. This value must not exceed the values set for the StorageMaximumLevel parameter - -Only applicable to: SharePoint Online - -```yaml -Type: Int -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title -Specifies the title of the site - -```yaml -Type: String -Parameter Sets: Set Properties - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -Specifies the URL of the site - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Wait -Wait for the operation to complete - -Only applicable to: SharePoint Online - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTheme.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTheme.md deleted file mode 100644 index b331a1da83..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTheme.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptheme -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPTheme ---- - -# Set-PnPTheme - -## SYNOPSIS -Sets the theme of the current web. - -## SYNTAX - -```powershell -Set-PnPTheme [-ColorPaletteUrl <String>] - [-FontSchemeUrl <String>] - [-BackgroundImageUrl <String>] - [-ResetSubwebsToInherit [<SwitchParameter>]] - [-UpdateRootWebOnly [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION - Sets the theme of the current web, if any of the attributes is not set, that value will be set to null - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTheme -``` - -Removes the current theme and resets it to the default. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPTheme -ColorPaletteUrl _catalogs/theme/15/company.spcolor -``` - - - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPTheme -ColorPaletteUrl _catalogs/theme/15/company.spcolor -BackgroundImageUrl 'style library/background.png' -``` - - - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPTheme -ColorPaletteUrl _catalogs/theme/15/company.spcolor -BackgroundImageUrl 'style library/background.png' -ResetSubwebsToInherit -``` - -Sets the theme to the web, and updates all subwebs to inherit the theme from this web. - -## PARAMETERS - -### -BackgroundImageUrl -Specifies the Background Image Url based on the site or server relative url - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ColorPaletteUrl -Specifies the Color Palette Url based on the site or server relative url - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -FontSchemeUrl -Specifies the Font Scheme Url based on the site or server relative url - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ResetSubwebsToInherit -Resets subwebs to inherit the theme from the rootweb - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -UpdateRootWebOnly -Updates only the rootweb, even if subwebs are set to inherit the theme. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTraceLog.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTraceLog.md deleted file mode 100644 index 66dbcc8548..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTraceLog.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnptracelog -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPTraceLog ---- - -# Set-PnPTraceLog - -## SYNOPSIS -Turn log tracing on or off - -## SYNTAX - -### On -```powershell -Set-PnPTraceLog -On [<SwitchParameter>] - [-LogFile <String>] - [-WriteToConsole [<SwitchParameter>]] - [-Level <LogLevel>] - [-Delimiter <String>] - [-IndentSize <Int>] - [-AutoFlush <Boolean>] -``` - -### Off -```powershell -Set-PnPTraceLog -Off [<SwitchParameter>] -``` - -## DESCRIPTION -Defines if tracing should be turned on. PnP Core, which is the foundation of these cmdlets, uses the standard Trace functionality of .NET. With this cmdlet you can turn capturing of this trace to a log file on or off. Notice that basically only the Provisioning Engine writes to the tracelog which means that cmdlets related to the engine will produce output. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPTraceLog -On -LogFile traceoutput.txt -``` - -This turns on trace logging to the file 'traceoutput.txt' and will capture events of at least 'Information' level. - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPTraceLog -On -LogFile traceoutput.txt -Level Debug -``` - -This turns on trace logging to the file 'traceoutput.txt' and will capture debug events. - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPTraceLog -On -LogFile traceoutput.txt -Level Debug -Delimiter "," -``` - -This turns on trace logging to the file 'traceoutput.txt' and will write the entries as comma separated. Debug events are captured. - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPTraceLog -Off -``` - -This turns off trace logging. It will flush any remaining messages to the log file. - -## PARAMETERS - -### -AutoFlush -Auto flush the trace log. Defaults to true. - -```yaml -Type: Boolean -Parameter Sets: On - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Delimiter -If specified the trace log entries will be delimited with this value. - -```yaml -Type: String -Parameter Sets: On - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -IndentSize -Indents in the tracelog will be with this amount of characters. Defaults to 4. - -```yaml -Type: Int -Parameter Sets: On - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Level -The level of events to capture. Possible values are 'Debug', 'Error', 'Warning', 'Information'. Defaults to 'Information'. - -```yaml -Type: LogLevel -Parameter Sets: On - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -LogFile -The path and filename of the file to write the trace log to. - -```yaml -Type: String -Parameter Sets: On - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Off -Turn off tracing to log file. - -```yaml -Type: SwitchParameter -Parameter Sets: Off - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -On -Turn on tracing to log file - -```yaml -Type: SwitchParameter -Parameter Sets: On - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -WriteToConsole -Turn on console trace output. - -```yaml -Type: SwitchParameter -Parameter Sets: On - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPUnifiedGroup.md deleted file mode 100644 index c14bdfde52..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPUnifiedGroup.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpunifiedgroup -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPUnifiedGroup ---- - -# Set-PnPUnifiedGroup - -## SYNOPSIS -Sets Office 365 Group (aka Unified Group) properties. Requires the Azure Active Directory application permission 'Group.ReadWrite.All'. - -## SYNTAX - -```powershell -Set-PnPUnifiedGroup -Identity <UnifiedGroupPipeBind> - [-DisplayName <String>] - [-Description <String>] - [-Owners <String[]>] - [-Members <String[]>] - [-IsPrivate [<SwitchParameter>]] - [-GroupLogoPath <String>] - [-CreateTeam [<SwitchParameter>]] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPUnifiedGroup -Identity $group -DisplayName "My Displayname" -``` - -Sets the display name of the group where $group is a Group entity - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPUnifiedGroup -Identity $groupId -Descriptions "My Description" -DisplayName "My DisplayName" -``` - -Sets the display name and description of a group based upon its ID - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPUnifiedGroup -Identity $group -GroupLogoPath ".\MyLogo.png" -``` - -Sets a specific Office 365 Group logo. - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPUnifiedGroup -Identity $group -IsPrivate:$false -``` - -Sets a group to be Public if previously Private. - -### ------------------EXAMPLE 5------------------ -```powershell -Set-PnPUnifiedGroup -Identity $group -Owners demo@contoso.com -``` - -Sets demo@contoso.com as owner of the group. - -## PARAMETERS - -### -CreateTeam -Creates a MS Teams team associated with created group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description -The Description of the group to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DisplayName -The DisplayName of the group to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -GroupLogoPath -The path to the logo file of to set. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The Identity of the Office 365 Group. - -```yaml -Type: UnifiedGroupPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -IsPrivate -Makes the group private when selected. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Members -The array UPN values of members to set to the group. Note: Will replace members. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Owners -The array UPN values of owners to set to the group. Note: Will replace owners. - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPUserProfileProperty.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPUserProfileProperty.md deleted file mode 100644 index 3debbda845..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPUserProfileProperty.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpuserprofileproperty -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPUserProfileProperty ---- - -# Set-PnPUserProfileProperty - -## SYNOPSIS -Office365 only: Uses the tenant API to retrieve site information. - -You must connect to the tenant admin website (https://:<tenant>-admin.sharepoint.com) with Connect-PnPOnline in order to use this command. - - -## SYNTAX - -### Single -```powershell -Set-PnPUserProfileProperty -Value <String> - -Account <String> - -PropertyName <String> - [-Connection <SPOnlineConnection>] -``` - -### Multi -```powershell -Set-PnPUserProfileProperty -Values <String[]> - -Account <String> - -PropertyName <String> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Requires a connection to a SharePoint Tenant Admin site. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPUserProfileProperty -Account 'user@domain.com' -Property 'SPS-Location' -Value 'Stockholm' -``` - -Sets the SPS-Location property for the user as specified by the Account parameter - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPUserProfileProperty -Account 'user@domain.com' -Property 'MyProperty' -Values 'Value 1','Value 2' -``` - -Sets the MyProperty multi value property for the user as specified by the Account parameter - -## PARAMETERS - -### -Account -The account of the user, formatted either as a login name, or as a claims identity, e.g. i:0#.f|membership|user@domain.com - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PropertyName -The property to set, for instance SPS-Skills or SPS-Location - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Value -The value to set in the case of a single value property - -```yaml -Type: String -Parameter Sets: Single - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Values -The values set in the case of a multi value property, e.g. "Value 1","Value 2" - -```yaml -Type: String[] -Parameter Sets: Multi - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPView.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPView.md deleted file mode 100644 index 2b5b3ad2f8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPView.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpview -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPView ---- - -# Set-PnPView - -## SYNOPSIS -Change view properties - -## SYNTAX - -```powershell -Set-PnPView -Identity <ViewPipeBind> - [-List <ListPipeBind>] - [-Values <Hashtable>] - [-Fields <String[]>] - [-Aggregations <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets one or more properties of an existing view, see here https://docs.microsoft.com/previous-versions/office/sharepoint-server/ee543328(v=office.15) for the list of view properties. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPView -List "Tasks" -Identity "All Tasks" -Values @{JSLink="hierarchytaskslist.js|customrendering.js";Title="My view"} -``` - -Updates the "All Tasks" view on list "Tasks" to use hierarchytaskslist.js and customrendering.js for the JSLink and changes the title of the view to "My view" - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPList -Identity "Tasks" | Get-PnPView | Set-PnPView -Values @{JSLink="hierarchytaskslist.js|customrendering.js"} -``` - -Updates all views on list "Tasks" to use hierarchytaskslist.js and customrendering.js for the JSLink - -### ------------------EXAMPLE 3------------------ -```powershell -Set-PnPView -List "Documents" -Identity "Corporate Documents" -Fields "Title","Created" -``` - -Updates the Corporate Documents view on the Documents library to have two fields - -### ------------------EXAMPLE 4------------------ -```powershell -Set-PnPView -List "Documents" -Identity "Corporate Documents" -Fields "Title","Created" -Aggregations "<FieldRef Name='Title' Type='COUNT'/>" -``` - -Updates the Corporate Documents view on the Documents library and sets the totals (aggregations) to Count on the Title field - -## PARAMETERS - -### -Aggregations -A valid XML fragment containing one or more Aggregations - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Fields -An array of fields to use in the view. Notice that specifying this value will remove the existing fields - -```yaml -Type: String[] -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The Id, Title or instance of the view - -```yaml -Type: ViewPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -List -The Id, Title or Url of the list - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: False -``` - -### -Values -Hashtable of properties to update on the view. Use the syntax @{property1="value";property2="value"}. - -```yaml -Type: Hashtable -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### Microsoft.SharePoint.Client.Field - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWeb.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWeb.md deleted file mode 100644 index 40d3eb46db..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWeb.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpweb -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPWeb ---- - -# Set-PnPWeb - -## SYNOPSIS -Sets properties on a web - -## SYNTAX - -```powershell -Set-PnPWeb [-SiteLogoUrl <String>] - [-AlternateCssUrl <String>] - [-Title <String>] - [-Description <String>] - [-MasterUrl <String>] - [-CustomMasterUrl <String>] - [-HeaderLayout <HeaderLayoutType>] - [-HeaderEmphasis <SPVariantThemeType>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets properties on a web - -## PARAMETERS - -### -AlternateCssUrl - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CustomMasterUrl - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Description - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HeaderEmphasis - - -Only applicable to: SharePoint Online - -```yaml -Type: SPVariantThemeType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HeaderLayout - - -Only applicable to: SharePoint Online - -```yaml -Type: HeaderLayoutType -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MasterUrl - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SiteLogoUrl -Sets the logo of the web to the current url. If you want to set the logo to a modern team site, use Set-PnPSite -LogoFilePath. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Title - - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebPartProperty.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebPartProperty.md deleted file mode 100644 index 8ea3e33f22..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebPartProperty.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpwebpartproperty -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPWebPartProperty ---- - -# Set-PnPWebPartProperty - -## SYNOPSIS -Sets a web part property - -## SYNTAX - -```powershell -Set-PnPWebPartProperty -ServerRelativePageUrl <String> - -Identity <GuidPipeBind> - -Key <String> - -Value <PSObject> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPWebPartProperty -ServerRelativePageUrl /sites/demo/sitepages/home.aspx -Identity ccd2c98a-c9ae-483b-ae72-19992d583914 -Key "Title" -Value "New Title" -``` - -Sets the title property of the web part. - -## PARAMETERS - -### -Identity -The Guid of the web part - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Key -Name of a single property to be set - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -Full server relative url of the web part page, e.g. /sites/demo/sitepages/home.aspx - -```yaml -Type: String -Parameter Sets: (All) -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Value -Value of the property to be set - -```yaml -Type: PSObject -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebPermission.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebPermission.md deleted file mode 100644 index 560a12bb59..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebPermission.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpwebpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPWebPermission ---- - -# Set-PnPWebPermission - -## SYNOPSIS -Set permissions - -## SYNTAX - -### Group -```powershell -Set-PnPWebPermission -Group <GroupPipeBind> - [-AddRole <String[]>] - [-RemoveRole <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### User -```powershell -Set-PnPWebPermission -User <String> - [-AddRole <String[]>] - [-RemoveRole <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### GroupByWebIdentity -```powershell -Set-PnPWebPermission -Identity <WebPipeBind> - -Group <GroupPipeBind> - [-AddRole <String[]>] - [-RemoveRole <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### UserByWebIdentity -```powershell -Set-PnPWebPermission -Identity <WebPipeBind> - -User <String> - [-AddRole <String[]>] - [-RemoveRole <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### GroupByWebUrl -```powershell -Set-PnPWebPermission -Url <String> - -Group <GroupPipeBind> - [-AddRole <String[]>] - [-RemoveRole <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### UserByWebUrl -```powershell -Set-PnPWebPermission -Url <String> - -User <String> - [-AddRole <String[]>] - [-RemoveRole <String[]>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets web permissions - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPWebPermission -Url projectA -User 'user@contoso.com' -AddRole 'Contribute' -``` - -Adds the 'Contribute' permission to the user 'user@contoso.com' for a web, specified by its site relative url - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPWebPermission -Identity 5fecaf67-6b9e-4691-a0ff-518fc9839aa0 -User 'user@contoso.com' -RemoveRole 'Contribute' -``` - -Removes the 'Contribute' permission to the user 'user@contoso.com' for a web, specified by its ID - -## PARAMETERS - -### -AddRole -The role that must be assigned to the group or user - -```yaml -Type: String[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Group - - -```yaml -Type: GroupPipeBind -Parameter Sets: Group, GroupByWebIdentity, GroupByWebUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Identity -Identity/Id/Web object - -```yaml -Type: WebPipeBind -Parameter Sets: GroupByWebIdentity, UserByWebIdentity - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -RemoveRole -The role that must be removed from the group or user - -```yaml -Type: String[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Url -The site relative url of the web, e.g. 'Subweb1' - -```yaml -Type: String -Parameter Sets: GroupByWebUrl, UserByWebUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -User - - -```yaml -Type: String -Parameter Sets: User, UserByWebIdentity, UserByWebUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebTheme.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebTheme.md deleted file mode 100644 index 00edcae314..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebTheme.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpwebtheme -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPWebTheme ---- - -# Set-PnPWebTheme - -## SYNOPSIS -Sets the theme of the current web. - -## SYNTAX - -```powershell -Set-PnPWebTheme [-Theme <ThemePipeBind>] - [-WebUrl <String>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Sets the theme of the current web. * Requires Tenant Administration Rights * - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPWebTheme -Theme MyTheme -``` - -Sets the theme named "MyTheme" to the current web - -### ------------------EXAMPLE 2------------------ -```powershell -Get-PnPTenantTheme -Name "MyTheme" | Set-PnPWebTheme -``` - -Sets the theme named "MyTheme" to the current web - -## PARAMETERS - -### -Theme -Specifies the Color Palette Url based on the site or server relative url - -```yaml -Type: ThemePipeBind -Parameter Sets: (All) - -Required: False -Position: 0 -Accept pipeline input: True -``` - -### -WebUrl -The URL of the web to apply the theme to. If not specified it will default to the current web based upon the URL specified with Connect-PnPOnline. - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebhookSubscription.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebhookSubscription.md deleted file mode 100644 index c3c2bf3fa3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebhookSubscription.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpwebhooksubscription -applicable: SharePoint Online -schema: 2.0.0 -title: Set-PnPWebhookSubscription ---- - -# Set-PnPWebhookSubscription - -## SYNOPSIS -Updates a Webhook subscription - -## SYNTAX - -```powershell -Set-PnPWebhookSubscription -Subscription <WebhookSubscriptionPipeBind> - [-List <ListPipeBind>] - [-NotificationUrl <String>] - [-ExpirationDate <DateTime>] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Set-PnPWebhookSubscription -List MyList -Subscription ea1533a8-ff03-415b-a7b6-517ee50db8b6 -NotificationUrl https://my-func.azurewebsites.net/webhook -``` - -Updates an existing Webhook subscription with the specified id on the list MyList with a new Notification Url - -### ------------------EXAMPLE 2------------------ -```powershell -Set-PnPWebhookSubscription -List MyList -Subscription ea1533a8-ff03-415b-a7b6-517ee50db8b6 -NotificationUrl https://my-func.azurewebsites.net/webhook -ExpirationDate "2017-09-01" -``` - -Updates an existing Webhook subscription with the specified id on the list MyList with a new Notification Url and a new expiration date - -### ------------------EXAMPLE 3------------------ -```powershell -$subscriptions = Get-PnPWebhookSubscriptions -List MyList -$updated = $subscriptions[0] -$updated.ExpirationDate = "2017-10-01" -Set-PnPWebhookSubscription -List MyList -Subscription $updated -``` - -Updates the Webhook subscription from the list MyList with a modified subscription object. -Note: The date will be converted to Universal Time - -## PARAMETERS - -### -ExpirationDate -The date at which the Webhook subscription will expire. (Default: 6 months from today) - -```yaml -Type: DateTime -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -List -The list object or name from which the Webhook subscription will be modified - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -NotificationUrl -The URL of the Webhook endpoint that will be notified of the change - -```yaml -Type: String -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Subscription -The identity of the Webhook subscription to update - -```yaml -Type: WebhookSubscriptionPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### OfficeDevPnP.Core.Entities.WebhookSubscription - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWikiPageContent.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWikiPageContent.md deleted file mode 100644 index 7998e9db5d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWikiPageContent.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/set-pnpwikipagecontent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Set-PnPWikiPageContent ---- - -# Set-PnPWikiPageContent - -## SYNOPSIS -Sets the contents of a wikipage - -## SYNTAX - -### STRING -```powershell -Set-PnPWikiPageContent -Content <String> - -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### FILE -```powershell -Set-PnPWikiPageContent -Path <String> - -ServerRelativePageUrl <String> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## PARAMETERS - -### -Content - - -```yaml -Type: String -Parameter Sets: STRING - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Path - - -```yaml -Type: String -Parameter Sets: FILE - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -ServerRelativePageUrl -Site Relative Page Url - -```yaml -Type: String -Parameter Sets: FILE, STRING -Aliases: PageUrl - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Start-PnPWorkflowInstance.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Start-PnPWorkflowInstance.md deleted file mode 100644 index e9615619fd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Start-PnPWorkflowInstance.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/start-pnpworkflowinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Start-PnPWorkflowInstance ---- - -# Start-PnPWorkflowInstance - -## SYNOPSIS -Starts a workflow instance on a list item - -## SYNTAX - -```powershell -Start-PnPWorkflowInstance -Subscription <WorkflowSubscriptionPipeBind> - -ListItem <ListItemPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Start-PnPWorkflowInstance -Subscription $subscription -ListItem $item -``` - -Starts a workflow instance on the specified list item - -### ------------------EXAMPLE 2------------------ -```powershell -Start-PnPWorkflowInstance -Subscription $subscription -ListItem 2 -``` - -Starts a workflow instance on the specified list item - -## PARAMETERS - -### -ListItem -The list item to start the workflow against - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: 1 -Accept pipeline input: False -``` - -### -Subscription -The workflow subscription to start - -```yaml -Type: WorkflowSubscriptionPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Stop-PnPWorkflowInstance.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Stop-PnPWorkflowInstance.md deleted file mode 100644 index e2c88b6fe9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Stop-PnPWorkflowInstance.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/stop-pnpworkflowinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Stop-PnPWorkflowInstance ---- - -# Stop-PnPWorkflowInstance - -## SYNOPSIS -Stops a workflow instance - -## SYNTAX - -```powershell -Stop-PnPWorkflowInstance -Identity <WorkflowInstancePipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Stop-PnPWorkflowInstance -identity $wfInstance -``` - -Stops the workflow Instance - -## PARAMETERS - -### -Force -Forcefully terminate the workflow instead of cancelling. Works on errored and non-responsive workflows. Deletes all created tasks. Does not notify participants. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -The instance to stop - -```yaml -Type: WorkflowInstancePipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Submit-PnPSearchQuery.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Submit-PnPSearchQuery.md deleted file mode 100644 index 4ace084d2b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Submit-PnPSearchQuery.md +++ /dev/null @@ -1,423 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/submit-pnpsearchquery -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Submit-PnPSearchQuery ---- - -# Submit-PnPSearchQuery - -## SYNOPSIS -Executes an arbitrary search query against the SharePoint search index - -## SYNTAX - -### Limit -```powershell -Submit-PnPSearchQuery -Query <String> - [-StartRow <Int>] - [-MaxResults <Int>] - [-TrimDuplicates <Boolean>] - [-Properties <Hashtable>] - [-Refiners <String>] - [-Culture <Int>] - [-QueryTemplate <String>] - [-SelectProperties <String[]>] - [-RefinementFilters <String[]>] - [-SortList <Hashtable>] - [-RankingModelId <String>] - [-ClientType <String>] - [-CollapseSpecification <String>] - [-HiddenConstraints <String>] - [-TimeZoneId <Int>] - [-EnablePhonetic <Boolean>] - [-EnableStemming <Boolean>] - [-EnableQueryRules <Boolean>] - [-SourceId <Guid>] - [-ProcessBestBets <Boolean>] - [-ProcessPersonalFavorites <Boolean>] - [-RelevantResults [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -### All -```powershell -Submit-PnPSearchQuery -Query <String> - [-All [<SwitchParameter>]] - [-TrimDuplicates <Boolean>] - [-Properties <Hashtable>] - [-Refiners <String>] - [-Culture <Int>] - [-QueryTemplate <String>] - [-SelectProperties <String[]>] - [-RefinementFilters <String[]>] - [-SortList <Hashtable>] - [-RankingModelId <String>] - [-ClientType <String>] - [-CollapseSpecification <String>] - [-HiddenConstraints <String>] - [-TimeZoneId <Int>] - [-EnablePhonetic <Boolean>] - [-EnableStemming <Boolean>] - [-EnableQueryRules <Boolean>] - [-SourceId <Guid>] - [-ProcessBestBets <Boolean>] - [-ProcessPersonalFavorites <Boolean>] - [-RelevantResults [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Submit-PnPSearchQuery -Query "finance" -``` - -Returns the top 500 items with the term finance - -### ------------------EXAMPLE 2------------------ -```powershell -Submit-PnPSearchQuery -Query "Title:Intranet*" -MaxResults 10 -``` - -Returns the top 10 items indexed by SharePoint Search of which the title starts with the word Intranet - -### ------------------EXAMPLE 3------------------ -```powershell -Submit-PnPSearchQuery -Query "Title:Intranet*" -All -``` - -Returns absolutely all items indexed by SharePoint Search of which the title starts with the word Intranet - -### ------------------EXAMPLE 4------------------ -```powershell -Submit-PnPSearchQuery -Query "Title:Intranet*" -Refiners "contentclass,FileType(filter=6/0/*)" -``` - -Returns absolutely all items indexed by SharePoint Search of which the title starts with the word Intranet, and return refiners for contentclass and FileType managed properties - -## PARAMETERS - -### -All -Automatically page results until the end to get more than 500. Use with caution! - -```yaml -Type: SwitchParameter -Parameter Sets: All - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ClientType -Specifies the name of the client which issued the query. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -CollapseSpecification -Limit the number of items per the collapse specification. See https://docs.microsoft.com/en-us/sharepoint/dev/general-development/customizing-search-results-in-sharepoint#collapse-similar-search-results-using-the-collapsespecification-property for more information. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Culture -The locale for the query. - -```yaml -Type: Int -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnablePhonetic -Specifies whether the phonetic forms of the query terms are used to find matches. - -```yaml -Type: Boolean -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableQueryRules -Specifies whether Query Rules are enabled for this query. - -```yaml -Type: Boolean -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -EnableStemming -Specifies whether stemming is enabled. - -```yaml -Type: Boolean -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -HiddenConstraints -The keyword query’s hidden constraints. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MaxResults -Maximum amount of search results to return. Default and max per page is 500 search results. - -```yaml -Type: Int -Parameter Sets: Limit - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ProcessBestBets -Determines whether Best Bets are enabled. - -```yaml -Type: Boolean -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -ProcessPersonalFavorites -Determines whether personal favorites data is processed or not. - -```yaml -Type: Boolean -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Properties -Extra query properties. Can for example be used for Office Graph queries. - -```yaml -Type: Hashtable -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Query -Search query in Keyword Query Language (KQL). - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -QueryTemplate -Specifies the query template that is used at run time to transform the query based on user input. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RankingModelId -The identifier (ID) of the ranking model to use for the query. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RefinementFilters -The set of refinement filters used. - -```yaml -Type: String[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Refiners -The list of refiners to be returned in a search result. - -```yaml -Type: String -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -RelevantResults -Specifies whether only relevant results are returned - -```yaml -Type: SwitchParameter -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SelectProperties -The list of properties to return in the search results. - -```yaml -Type: String[] -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SortList -The list of properties by which the search results are ordered. - -```yaml -Type: Hashtable -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -SourceId -Specifies the identifier (ID or name) of the result source to be used to run the query. - -```yaml -Type: Guid -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -StartRow -Search result item to start returning the results from. Useful for paging. Leave at 0 to return all results. - -```yaml -Type: Int -Parameter Sets: Limit - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TimeZoneId -The identifier for the search query time zone. - -```yaml -Type: Int -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -TrimDuplicates -Specifies whether near duplicate items should be removed from the search results. - -```yaml -Type: Boolean -Parameter Sets: __AllParameterSets - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## OUTPUTS - -### List<System.Object> - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Sync-PnPAppToTeams.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Sync-PnPAppToTeams.md deleted file mode 100644 index af58ec7fc0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Sync-PnPAppToTeams.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/sync-pnpapptoteams -applicable: SharePoint Online -schema: 2.0.0 -title: Sync-PnPAppToTeams ---- - -# Sync-PnPAppToTeams - -## SYNOPSIS -Synchronize an app from the tenant app catalog to the Microsoft Teams app catalog - -## SYNTAX - -```powershell -Sync-PnPAppToTeams -Identity <AppMetadataPipeBind> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Sync-PnPAppToTeams -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will synchronize the given app with the Microsoft Teams app catalog - -## PARAMETERS - -### -Identity -Specifies the Id of the Addin Instance - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPListItemIsRecord.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPListItemIsRecord.md deleted file mode 100644 index aab66a9834..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPListItemIsRecord.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/test-pnplistitemisrecord -applicable: SharePoint Online -schema: 2.0.0 -title: Test-PnPListItemIsRecord ---- - -# Test-PnPListItemIsRecord - -## SYNOPSIS -Checks if a list item is a record - -## SYNTAX - -```powershell -Test-PnPListItemIsRecord -List <ListPipeBind> - -Identity <ListItemPipeBind> - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Test-PnPListItemIsRecord -List "Documents" -Identity 4 -``` - -Returns true if the document in the documents library with id 4 is a record - -## PARAMETERS - -### -Identity -The ID of the listitem, or actual ListItem object - -```yaml -Type: ListItemPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -List -The ID, Title or Url of the list. - -```yaml -Type: ListPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPOffice365GroupAliasIsUsed.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPOffice365GroupAliasIsUsed.md deleted file mode 100644 index 4a20b3875d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPOffice365GroupAliasIsUsed.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/test-pnpoffice365groupaliasisused -applicable: SharePoint Online -schema: 2.0.0 -title: Test-PnPOffice365GroupAliasIsUsed ---- - -# Test-PnPOffice365GroupAliasIsUsed - -## SYNOPSIS -Tests if a given alias is already used used - -## SYNTAX - -```powershell -Test-PnPOffice365GroupAliasIsUsed -Alias <String> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -This command allows you to test if a provided alias is used or free, helps decide if it can be used as part of connecting an Office 365 Unified group to an existing classic site collection. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Test-PnPOffice365GroupAliasIsUsed -Alias "MyGroup" -``` - -This will test if the alias MyGroup is already used - -## PARAMETERS - -### -Alias -Specifies the alias of the group. Cannot contain spaces. - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPTenantTemplate.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPTenantTemplate.md deleted file mode 100644 index 85d531bfa5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPTenantTemplate.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/test-pnptenanttemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Test-PnPTenantTemplate ---- - -# Test-PnPTenantTemplate - -## SYNOPSIS -Tests a tenant template for invalid references - -## SYNTAX - -```powershell -Test-PnPTenantTemplate -Template <ProvisioningHierarchy> - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Test-PnPTenantTemplate -Template $myTemplate -``` - -Checks for valid template references - -## PARAMETERS - -### -Template -The in-memory template to test - -Only applicable to: SharePoint Online - -```yaml -Type: ProvisioningHierarchy -Parameter Sets: __AllParameterSets - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPApp.md deleted file mode 100644 index 0ece85f702..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPApp.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/uninstall-pnpapp -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Uninstall-PnPApp ---- - -# Uninstall-PnPApp - -## SYNOPSIS -Uninstalls an available add-in from the site - -## SYNTAX - -```powershell -Uninstall-PnPApp -Identity <AppMetadataPipeBind> - [-Scope <AppCatalogScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Uninstall-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will uninstall the specified app from the current site. - -### ------------------EXAMPLE 2------------------ -```powershell -Uninstall-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Site -``` - -This will uninstall the specified app from the current site. Notice that the app was original installed from the site collection appcatalog. - -## PARAMETERS - -### -Identity -Specifies the Id of the Addin Instance - -Only applicable to: SharePoint Online - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPAppInstance.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPAppInstance.md deleted file mode 100644 index 6cfc5c034d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPAppInstance.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/uninstall-pnpappinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Uninstall-PnPAppInstance ---- - -# Uninstall-PnPAppInstance - -## SYNOPSIS -Removes an app from a site - -## SYNTAX - -```powershell -Uninstall-PnPAppInstance -Identity <AppPipeBind> - [-Force [<SwitchParameter>]] - [-Web <WebPipeBind>] - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Removes an add-in/app that has been installed to a site. - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Uninstall-PnPAppInstance -Identity $appinstance -``` - -Uninstalls the app instance which was retrieved with the command Get-PnPAppInstance - -### ------------------EXAMPLE 2------------------ -```powershell -Uninstall-PnPAppInstance -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -Uninstalls the app instance with the ID '99a00f6e-fb81-4dc7-8eac-e09c6f9132fe' - -### ------------------EXAMPLE 3------------------ -```powershell -Uninstall-PnPAppInstance -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -force -``` - -Uninstalls the app instance with the ID '99a00f6e-fb81-4dc7-8eac-e09c6f9132fe' and do not ask for confirmation - -## PARAMETERS - -### -Force -Do not ask for confirmation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Identity -Appinstance or Id of the addin to remove. - -```yaml -Type: AppPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: True -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Web -This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web. - -```yaml -Type: WebPipeBind -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPSolution.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPSolution.md deleted file mode 100644 index 47f1717483..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPSolution.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/uninstall-pnpsolution -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, SharePoint Online -schema: 2.0.0 -title: Uninstall-PnPSolution ---- - -# Uninstall-PnPSolution - -## SYNOPSIS -Uninstalls a sandboxed solution from a site collection - -## SYNTAX - -```powershell -Uninstall-PnPSolution -PackageId <GuidPipeBind> - -PackageName <String> - [-MajorVersion <Int>] - [-MinorVersion <Int>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Uninstall-PnPSolution -PackageId c2f5b025-7c42-4d3a-b579-41da3b8e7254 -PackageName mypackage.wsp -``` - -Removes the package to the current site - -## PARAMETERS - -### -MajorVersion -Optional major version of the solution, defaults to 1 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -MinorVersion -Optional minor version of the solution, defaults to 0 - -```yaml -Type: Int -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -PackageId -ID of the solution, from the solution manifest - -```yaml -Type: GuidPipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -PackageName -Filename of the WSP file to uninstall - -```yaml -Type: String -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Unpublish-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Unpublish-PnPApp.md deleted file mode 100644 index 829cf69035..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Unpublish-PnPApp.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/unpublish-pnpapp -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Unpublish-PnPApp ---- - -# Unpublish-PnPApp - -## SYNOPSIS -Unpublishes/retracts an available add-in from the app catalog - -## SYNTAX - -```powershell -Unpublish-PnPApp -Identity <AppMetadataPipeBind> - [-Scope <AppCatalogScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Unpublish-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will retract, but not remove, the specified app from the tenant app catalog - -### ------------------EXAMPLE 2------------------ -```powershell -Unpublish-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Site -``` - -This will retract, but not remove, the specified app from the site collection app catalog - -## PARAMETERS - -### -Identity -Specifies the Id of the Addin Instance - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Unregister-PnPHubSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Unregister-PnPHubSite.md deleted file mode 100644 index 03314b9fea..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Unregister-PnPHubSite.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/unregister-pnphubsite -applicable: SharePoint Online -schema: 2.0.0 -title: Unregister-PnPHubSite ---- - -# Unregister-PnPHubSite - -## SYNOPSIS -Unregisters a site as a hubsite - -## SYNTAX - -```powershell -Unregister-PnPHubSite -Site <SitePipeBind> - [-Connection <SPOnlineConnection>] -``` - -## DESCRIPTION -Registers a site as a hubsite - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Unregister-PnPHubSite -Site https://tenant.sharepoint.com/sites/myhubsite -``` - -This example unregisters the specified site as a hubsite - -## PARAMETERS - -### -Site -The site to unregister as a hubsite - -```yaml -Type: SitePipeBind -Parameter Sets: (All) - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Update-PnPApp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Update-PnPApp.md deleted file mode 100644 index 8184ec826d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Update-PnPApp.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/update-pnpapp -applicable: SharePoint Online, SharePoint 2019 -schema: 2.0.0 -title: Update-PnPApp ---- - -# Update-PnPApp - -## SYNOPSIS -Updates an available app from the app catalog - -## SYNTAX - -```powershell -Update-PnPApp -Identity <AppMetadataPipeBind> - [-Scope <AppCatalogScope>] - [-Connection <SPOnlineConnection>] -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Update-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -``` - -This will update an already installed app if a new version is available in the tenant app catalog. Retrieve a list all available apps and the installed and available versions with Get-PnPApp - -### ------------------EXAMPLE 2------------------ -```powershell -Update-PnPApp -Identity 99a00f6e-fb81-4dc7-8eac-e09c6f9132fe -Scope Site -``` - -This will update an already installed app if a new version is available in the site collection app catalog. Retrieve a list all available apps and the installed and available versions with Get-PnPApp -Scope Site - -## PARAMETERS - -### -Identity -Specifies the Id or an actual app metadata instance - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppMetadataPipeBind -Parameter Sets: (All) - -Required: True -Position: 0 -Accept pipeline input: True -``` - -### -Scope -Defines which app catalog to use. Defaults to Tenant - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: AppCatalogScope -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Connection -Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection. - -Only applicable to: SharePoint Online, SharePoint Server 2019 - -```yaml -Type: SPOnlineConnection -Parameter Sets: (All) - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Update-PnPSiteClassification.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Update-PnPSiteClassification.md deleted file mode 100644 index 4be7afe6eb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/Update-PnPSiteClassification.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: -online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/update-pnpsiteclassification -applicable: SharePoint Online -schema: 2.0.0 -title: Update-PnPSiteClassification ---- - -# Update-PnPSiteClassification - -## SYNOPSIS -Updates Site Classifications for the tenant. Requires a connection to the Microsoft Graph. - -## SYNTAX - -### Specific -```powershell -Update-PnPSiteClassification [-Classifications <String>] - [-DefaultClassification <String>] - [-UsageGuidelinesUrl <String>] -``` - -### Settings -```powershell -Update-PnPSiteClassification -Settings <SiteClassificationsSettings> -``` - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Update-PnPSiteClassification -Classifications "HBI","Top Secret" -``` - -Replaces the existing values of the site classification settings - -### ------------------EXAMPLE 2------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Update-PnPSiteClassification -DefaultClassification "LBI" -``` - -Sets the default classification value to "LBI". This value needs to be present in the list of classification values. - -### ------------------EXAMPLE 3------------------ -```powershell -Connect-PnPOnline -Scopes "Directory.ReadWrite.All" -Update-PnPSiteClassification -UsageGuidelinesUrl https://aka.ms/sppnp -``` - -sets the usage guideliness URL to the specified URL. - -## PARAMETERS - -### -Classifications -A list of classifications, separated by commas. E.g. "HBI","LBI","Top Secret" - -```yaml -Type: String -Parameter Sets: Specific - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -DefaultClassification -The default classification to be used. The value needs to be present in the list of possible classifications - -```yaml -Type: String -Parameter Sets: Specific - -Required: False -Position: Named -Accept pipeline input: False -``` - -### -Settings -A settings object retrieved by Get-PnPSiteClassification - -```yaml -Type: SiteClassificationsSettings -Parameter Sets: Settings - -Required: True -Position: Named -Accept pipeline input: False -``` - -### -UsageGuidelinesUrl -The UsageGuidelinesUrl. Set to "" to clear. - -```yaml -Type: String -Parameter Sets: Specific - -Required: False -Position: Named -Accept pipeline input: False -``` - -## RELATED LINKS - -[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp) \ No newline at end of file diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/sharepoint-pnp.md b/sharepoint/sharepoint-ps/sharepoint-pnp/sharepoint-pnp.md deleted file mode 100644 index 1dd6e261d6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-pnp/sharepoint-pnp.md +++ /dev/null @@ -1,1027 +0,0 @@ ---- -Module Name: SharePoint PnP PowerShell -Module Guid: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -title: sharepoint-pnp ---- - -# SharePoint PnP PowerShell - -## Description - -The following cmdlet references are for SharePoint PnP. - -## sharepoint-pnp Cmdlets - -## [Add-PnPSiteCollectionAdmin](Add-PnPSiteCollectionAdmin.md) -{{Manually Enter Add-PnPSiteCollectionAdmin Description Here}} - -### [Add-PnPSiteCollectionAppCatalog](Add-PnPSiteCollectionAppCatalog.md) -{{Manually Enter Add-PnPSiteCollectionAppCatalog Description Here}} - -### [Add-PnPSiteDesign](Add-PnPSiteDesign.md) -{{Manually Enter Add-PnPSiteDesign Description Here}} - -### [Add-PnPSiteDesignTask](Add-PnPSiteDesignTask.md) -{{Manually Enter Add-PnPSiteDesignTask Description Here}} - -### [Add-PnPSiteScript](Add-PnPSiteScript.md) -{{Manually Enter Add-PnPSiteScript Description Here}} - -### [Add-PnPStoredCredential](Add-PnPStoredCredential.md) -{{Manually Enter Add-PnPStoredCredential Description Here}} - -### [Add-PnPTaxonomyField](Add-PnPTaxonomyField.md) -{{Manually Enter Add-PnPTaxonomyField Description Here}} - -### [Add-PnPTenantCdnOrigin](Add-PnPTenantCdnOrigin.md) -{{Manually Enter Add-PnPTenantCdnOrigin Description Here}} - -### [Add-PnPTenantSequence](Add-PnPTenantSequence.md) -{{Manually Enter Add-PnPTenantSequence Description Here}} - -### [Add-PnPTenantSequenceSite](Add-PnPTenantSequenceSite.md) -{{Manually Enter Add-PnPTenantSequenceSite Description Here}} - -### [Add-PnPTenantSequenceSubSite](Add-PnPTenantSequenceSubSite.md) -{{Manually Enter Add-PnPTenantSequenceSubSite Description Here}} - -### [Add-PnPTenantTheme](Add-PnPTenantTheme.md) -{{Manually Enter Add-PnPTenantTheme Description Here}} - -### [Add-PnPUserToGroup](Add-PnPUserToGroup.md) -{{Manually Enter Add-PnPUserToGroup Description Here}} - -### [Add-PnPView](Add-PnPView.md) -{{Manually Enter Add-PnPView Description Here}} - -### [Add-PnPWebhookSubscription](Add-PnPWebhookSubscription.md) -{{Manually Enter Add-PnPWebhookSubscription Description Here}} - -### [Add-PnPWebPartToWebPartPage](Add-PnPWebPartToWebPartPage.md) -{{Manually Enter Add-PnPWebPartToWebPartPage Description Here}} - -### [Add-PnPWebPartToWikiPage](Add-PnPWebPartToWikiPage.md) -{{Manually Enter Add-PnPWebPartToWikiPage Description Here}} - -### [Add-PnPWikiPage](Add-PnPWikiPage.md) -{{Manually Enter Add-PnPWikiPage Description Here}} - -### [Add-PnPWorkflowDefinition](Add-PnPWorkflowDefinition.md) -{{Manually Enter Add-PnPWorkflowDefinition Description Here}} - -### [Add-PnPWorkflowSubscription](Add-PnPWorkflowSubscription.md) -{{Manually Enter Add-PnPWorkflowSubscription Description Here}} - -### [Apply-PnPProvisioningTemplate](Apply-PnPProvisioningTemplate.md) -{{Manually Enter Apply-PnPProvisioningTemplate Description Here}} - -### [Apply-PnPTenantTemplate](Apply-PnPTenantTemplate.md) -{{Manually Enter Apply-PnPTenantTemplate Description Here}} - -### [Approve-PnPTenantServicePrincipalPermissionRequest](Approve-PnPTenantServicePrincipalPermissionRequest.md) -{{Manually Enter Approve-PnPTenantServicePrincipalPermissionRequest Description Here}} - -### [Clear-PnPDefaultColumnValues](Clear-PnPDefaultColumnValues.md) -{{Manually Enter Clear-PnPDefaultColumnValues Description Here}} - -### [Clear-PnPListItemAsRecord](Clear-PnPListItemAsRecord.md) -{{Manually Enter Clear-PnPListItemAsRecord Description Here}} - -### [Clear-PnpRecycleBinItem](Clear-PnpRecycleBinItem.md) -{{Manually Enter Clear-PnpRecycleBinItem Description Here}} - -### [Clear-PnPTenantRecycleBinItem](Clear-PnPTenantRecycleBinItem.md) -{{Manually Enter Clear-PnPTenantRecycleBinItem Description Here}} - -### [Connect-PnPMicrosoftGraph](Connect-PnPMicrosoftGraph.md) -{{Manually Enter Connect-PnPMicrosoftGraph Description Here}} - -### [Connect-PnPOnline](Connect-PnPOnline.md) -{{Manually Enter Connect-PnPOnline Description Here}} - -### [Convert-PnPFolderToProvisioningTemplate](Convert-PnPFolderToProvisioningTemplate.md) -{{Manually Enter Convert-PnPFolderToProvisioningTemplate Description Here}} - -### [Convert-PnPProvisioningTemplate](Convert-PnPProvisioningTemplate.md) -{{Manually Enter Convert-PnPProvisioningTemplate Description Here}} - -### [ConvertTo-PnPClientSidePage](ConvertTo-PnPClientSidePage.md) -{{Manually Enter ConvertTo-PnPClientSidePage Description Here}} - -### [Copy-PnPFile](Copy-PnPFile.md) -{{Manually Enter Copy-PnPFile Description Here}} - -### [Copy-PnPItemProxy](Copy-PnPItemProxy.md) -{{Manually Enter Copy-PnPItemProxy Description Here}} - -### [Deny-PnPTenantServicePrincipalPermissionRequest](Deny-PnPTenantServicePrincipalPermissionRequest.md) -{{Manually Enter Deny-PnPTenantServicePrincipalPermissionRequest Description Here}} - -### [Disable-PnPFeature](Disable-PnPFeature.md) -{{Manually Enter Disable-PnPFeature Description Here}} - -### [Disable-PnPInPlaceRecordsManagementForSite](Disable-PnPInPlaceRecordsManagementForSite.md) -{{Manually Enter Disable-PnPInPlaceRecordsManagementForSite Description Here}} - -### [Disable-PnPPowerShellTelemetry](Disable-PnPPowerShellTelemetry.md) -{{Manually Enter Disable-PnPPowerShellTelemetry Description Here}} - -### [Disable-PnPResponsiveUI](Disable-PnPResponsiveUI.md) -{{Manually Enter Disable-PnPResponsiveUI Description Here}} - -### [Disable-PnPSiteClassification](Disable-PnPSiteClassification.md) -{{Manually Enter Disable-PnPSiteClassification Description Here}} - -### [Disable-PnPTenantServicePrincipal](Disable-PnPTenantServicePrincipal.md) -{{Manually Enter Disable-PnPTenantServicePrincipal Description Here}} - -### [Disconnect-PnPOnline](Disconnect-PnPOnline.md) -{{Manually Enter Disconnect-PnPOnline Description Here}} - -### [Enable-PnPFeature](Enable-PnPFeature.md) -{{Manually Enter Enable-PnPFeature Description Here}} - -### [Enable-PnPInPlaceRecordsManagementForSite](Enable-PnPInPlaceRecordsManagementForSite.md) -{{Manually Enter Enable-PnPInPlaceRecordsManagementForSite Description Here}} - -### [Enable-PnPPowerShellTelemetry](Enable-PnPPowerShellTelemetry.md) -{{Manually Enter Enable-PnPPowerShellTelemetry Description Here}} - -### [Enable-PnPResponsiveUI](Enable-PnPResponsiveUI.md) -{{Manually Enter Enable-PnPResponsiveUI Description Here}} - -### [Enable-PnPSiteClassification](Enable-PnPSiteClassification.md) -{{Manually Enter Enable-PnPSiteClassification Description Here}} - -### [Enable-PnPTenantServicePrincipal](Enable-PnPTenantServicePrincipal.md) -{{Manually Enter Enable-PnPTenantServicePrincipal Description Here}} - -### [Export-PnPClientSidePage](Export-PnPClientSidePage.md) -{{Manually Enter Export-PnPClientSidePage Description Here}} - -### [Export-PnPTaxonomy](Export-PnPTaxonomy.md) -{{Manually Enter Export-PnPTaxonomy Description Here}} - -### [Export-PnPTermGroupToXml](Export-PnPTermGroupToXml.md) -{{Manually Enter Export-PnPTermGroupToXml Description Here}} - -### [Find-PnPFile](Find-PnPFile.md) -{{Manually Enter Find-PnPFile Description Here}} - -### [Get-PnPAccessToken](Get-PnPAccessToken.md) -{{Manually Enter Get-PnPAccessToken Description Here}} - -### [Get-PnPAlert](Get-PnPAlert.md) -{{Manually Enter Get-PnPAlert Description Here}} - -### [Get-PnPApp](Get-PnPApp.md) -{{Manually Enter Get-PnPApp Description Here}} - -### [Get-PnPAppAuthAccessToken](Get-PnPAppAuthAccessToken.md) -{{Manually Enter Get-PnPAppAuthAccessToken Description Here}} - -### [Get-PnPAppInstance](Get-PnPAppInstance.md) -{{Manually Enter Get-PnPAppInstance Description Here}} - -### [Get-PnPAuditing](Get-PnPAuditing.md) -{{Manually Enter Get-PnPAuditing Description Here}} - -### [Get-PnPAuthenticationRealm](Get-PnPAuthenticationRealm.md) -{{Manually Enter Get-PnPAuthenticationRealm Description Here}} - -### [Get-PnPAvailableClientSideComponents](Get-PnPAvailableClientSideComponents.md) -{{Manually Enter Get-PnPAvailableClientSideComponents Description Here}} - -### [Get-PnPAzureADManifestKeyCredentials](Get-PnPAzureADManifestKeyCredentials.md) -{{Manually Enter Get-PnPAzureADManifestKeyCredentials Description Here}} - -### [Get-PnPAzureCertificate](Get-PnPAzureCertificate.md) -{{Manually Enter Get-PnPAzureCertificate Description Here}} - -### [Get-PnPClientSideComponent](Get-PnPClientSideComponent.md) -{{Manually Enter Get-PnPClientSideComponent Description Here}} - -### [Get-PnPClientSidePage](Get-PnPClientSidePage.md) -{{Manually Enter Get-PnPClientSidePage Description Here}} - -### [Get-PnPConnection](Get-PnPConnection.md) -{{Manually Enter Get-PnPConnection Description Here}} - -### [Get-PnPContentType](Get-PnPContentType.md) -{{Manually Enter Get-PnPContentType Description Here}} - -### [Get-PnPContentTypePublishingHubUrl](Get-PnPContentTypePublishingHubUrl.md) -{{Manually Enter Get-PnPContentTypePublishingHubUrl Description Here}} - -### [Get-PnPContext](Get-PnPContext.md) -{{Manually Enter Get-PnPContext Description Here}} - -### [Get-PnPCustomAction](Get-PnPCustomAction.md) -{{Manually Enter Get-PnPCustomAction Description Here}} - -### [Get-PnPDefaultColumnValues](Get-PnPDefaultColumnValues.md) -{{Manually Enter Get-PnPDefaultColumnValues Description Here}} - -### [Get-PnPDocumentSetTemplate](Get-PnPDocumentSetTemplate.md) -{{Manually Enter Get-PnPDocumentSetTemplate Description Here}} - -### [Get-PnPEventReceiver](Get-PnPEventReceiver.md) -{{Manually Enter Get-PnPEventReceiver Description Here}} - -### [Get-PnPException](Get-PnPException.md) -{{Manually Enter Get-PnPException Description Here}} - -### [Get-PnPFeature](Get-PnPFeature.md) -{{Manually Enter Get-PnPFeature Description Here}} - -### [Get-PnPField](Get-PnPField.md) -{{Manually Enter Get-PnPField Description Here}} - -### [Get-PnPFile](Get-PnPFile.md) -{{Manually Enter Get-PnPFile Description Here}} - -### [Get-PnPFolder](Get-PnPFolder.md) -{{Manually Enter Get-PnPFolder Description Here}} - -### [Get-PnPFolderItem](Get-PnPFolderItem.md) -{{Manually Enter Get-PnPFolderItem Description Here}} - -### [Get-PnPGroup](Get-PnPGroup.md) -{{Manually Enter Get-PnPGroup Description Here}} - -### [Get-PnPGroupMembers](Get-PnPGroupMembers.md) -{{Manually Enter Get-PnPGroupMembers Description Here}} - -### [Get-PnPGroupPermissions](Get-PnPGroupPermissions.md) -{{Manually Enter Get-PnPGroupPermissions Description Here}} - -### [Get-PnPHealthScore](Get-PnPHealthScore.md) -{{Manually Enter Get-PnPHealthScore Description Here}} - -### [Get-PnPHideDefaultThemes](Get-PnPHideDefaultThemes.md) -{{Manually Enter Get-PnPHideDefaultThemes Description Here}} - -### [Get-PnPHomePage](Get-PnPHomePage.md) -{{Manually Enter Get-PnPHomePage Description Here}} - -### [Get-PnPHubSite](Get-PnPHubSite.md) -{{Manually Enter Get-PnPHubSite Description Here}} - -### [Get-PnPIndexedPropertyKeys](Get-PnPIndexedPropertyKeys.md) -{{Manually Enter Get-PnPIndexedPropertyKeys Description Here}} - -### [Get-PnPInPlaceRecordsManagement](Get-PnPInPlaceRecordsManagement.md) -{{Manually Enter Get-PnPInPlaceRecordsManagement Description Here}} - -### [Get-PnPJavaScriptLink](Get-PnPJavaScriptLink.md) -{{Manually Enter Get-PnPJavaScriptLink Description Here}} - -### [Get-PnPLabel](Get-PnPLabel.md) -{{Manually Enter Get-PnPLabel Description Here}} - -### [Get-PnPList](Get-PnPList.md) -{{Manually Enter Get-PnPList Description Here}} - -### [Get-PnPListInformationRightsManagement](Get-PnPListInformationRightsManagement.md) -{{Manually Enter Get-PnPListInformationRightsManagement Description Here}} - -### [Get-PnPListItem](Get-PnPListItem.md) -{{Manually Enter Get-PnPListItem Description Here}} - -### [Get-PnPListRecordDeclaration](Get-PnPListRecordDeclaration.md) -{{Manually Enter Get-PnPListRecordDeclaration Description Here}} - -### [Get-PnPMasterPage](Get-PnPMasterPage.md) -{{Manually Enter Get-PnPMasterPage Description Here}} - -### [Get-PnPNavigationNode](Get-PnPNavigationNode.md) -{{Manually Enter Get-PnPNavigationNode Description Here}} - -### [Get-PnPPowerShellTelemetryEnabled](Get-PnPPowerShellTelemetryEnabled.md) -{{Manually Enter Get-PnPPowerShellTelemetryEnabled Description Here}} - -### [Get-PnPProperty](Get-PnPProperty.md) -{{Manually Enter Get-PnPProperty Description Here}} - -### [Get-PnPPropertyBag](Get-PnPPropertyBag.md) -{{Manually Enter Get-PnPPropertyBag Description Here}} - -### [Get-PnPProvisioningTemplate](Get-PnPProvisioningTemplate.md) -{{Manually Enter Get-PnPProvisioningTemplate Description Here}} - -### [Get-PnPProvisioningTemplateFromGallery](Get-PnPProvisioningTemplateFromGallery.md) -{{Manually Enter Get-PnPProvisioningTemplateFromGallery Description Here}} - -### [Get-PnPPublishingImageRendition](Get-PnPPublishingImageRendition.md) -{{Manually Enter Get-PnPPublishingImageRendition Description Here}} - -### [Get-PnPRecycleBinItem](Get-PnPRecycleBinItem.md) -{{Manually Enter Get-PnPRecycleBinItem Description Here}} - -### [Get-PnPRequestAccessEmails](Get-PnPRequestAccessEmails.md) -{{Manually Enter Get-PnPRequestAccessEmails Description Here}} - -### [Get-PnPRoleDefinition](Get-PnPRoleDefinition.md) -{{Manually Enter Get-PnPRoleDefinition Description Here}} - -### [Get-PnPSearchConfiguration](Get-PnPSearchConfiguration.md) -{{Manually Enter Get-PnPSearchConfiguration Description Here}} - -### [Get-PnPSearchCrawlLog](Get-PnPSearchCrawlLog.md) -{{Manually Enter Get-PnPSearchCrawlLog Description Here}} - -### [Get-PnPSite](Get-PnPSite.md) -{{Manually Enter Get-PnPSite Description Here}} - -### [Get-PnPSiteClassification](Get-PnPSiteClassification.md) -{{Manually Enter Get-PnPSiteClassification Description Here}} - -### [Get-PnPSiteClosure](Get-PnPSiteClosure.md) -{{Manually Enter Get-PnPSiteClosure Description Here}} - -### [Get-PnPSiteCollectionAdmin](Get-PnPSiteCollectionAdmin.md) -{{Manually Enter Get-PnPSiteCollectionAdmin Description Here}} - -### [Get-PnPSiteCollectionTermStore](Get-PnPSiteCollectionTermStore.md) -{{Manually Enter Get-PnPSiteCollectionTermStore Description Here}} - -### [Get-PnPSiteDesign](Get-PnPSiteDesign.md) -{{Manually Enter Get-PnPSiteDesign Description Here}} - -### [Get-PnPSiteDesignRights](Get-PnPSiteDesignRights.md) -{{Manually Enter Get-PnPSiteDesignRights Description Here}} - -### [Get-PnPSiteDesignRun](Get-PnPSiteDesignRun.md) -{{Manually Enter Get-PnPSiteDesignRun Description Here}} - -### [Get-PnPSiteDesignRunStatus](Get-PnPSiteDesignRunStatus.md) -{{Manually Enter Get-PnPSiteDesignRunStatus Description Here}} - -### [Get-PnPSiteDesignTask](Get-PnPSiteDesignTask.md) -{{Manually Enter Get-PnPSiteDesignTask Description Here}} - -### [Get-PnPSitePolicy](Get-PnPSitePolicy.md) -{{Manually Enter Get-PnPSitePolicy Description Here}} - -### [Get-PnPSiteScript](Get-PnPSiteScript.md) -{{Manually Enter Get-PnPSiteScript Description Here}} - -### [Get-PnPSiteSearchQueryResults](Get-PnPSiteSearchQueryResults.md) -{{Manually Enter Get-PnPSiteSearchQueryResults Description Here}} - -### [Get-PnPStorageEntity](Get-PnPStorageEntity.md) -{{Manually Enter Get-PnPStorageEntity Description Here}} - -### [Get-PnPStoredCredential](Get-PnPStoredCredential.md) -{{Manually Enter Get-PnPStoredCredential Description Here}} - -### [Get-PnPSubWebs](Get-PnPSubWebs.md) -{{Manually Enter Get-PnPSubWebs Description Here}} - -### [Get-PnPTaxonomyItem](Get-PnPTaxonomyItem.md) -{{Manually Enter Get-PnPTaxonomyItem Description Here}} - -### [Get-PnPTaxonomySession](Get-PnPTaxonomySession.md) -{{Manually Enter Get-PnPTaxonomySession Description Here}} - -### [Get-PnPTenant](Get-PnPTenant.md) -{{Manually Enter Get-PnPTenant Description Here}} - -### [Get-PnPTenantAppCatalogUrl](Get-PnPTenantAppCatalogUrl.md) -{{Manually Enter Get-PnPTenantAppCatalogUrl Description Here}} - -### [Get-PnPTenantCdnEnabled](Get-PnPTenantCdnEnabled.md) -{{Manually Enter Get-PnPTenantCdnEnabled Description Here}} - -### [Get-PnPTenantCdnOrigin](Get-PnPTenantCdnOrigin.md) -{{Manually Enter Get-PnPTenantCdnOrigin Description Here}} - -### [Get-PnPTenantCdnPolicies](Get-PnPTenantCdnPolicies.md) -{{Manually Enter Get-PnPTenantCdnPolicies Description Here}} - -### [Get-PnPTenantRecycleBinItem](Get-PnPTenantRecycleBinItem.md) -{{Manually Enter Get-PnPTenantRecycleBinItem Description Here}} - -### [Get-PnPTenantSequence](Get-PnPTenantSequence.md) -{{Manually Enter Get-PnPTenantSequence Description Here}} - -### [Get-PnPTenantSequenceSite](Get-PnPTenantSequenceSite.md) -{{Manually Enter Get-PnPTenantSequenceSite Description Here}} - -### [Get-PnPTenantServicePrincipal](Get-PnPTenantServicePrincipal.md) -{{Manually Enter Get-PnPTenantServicePrincipal Description Here}} - -### [Get-PnPTenantServicePrincipalPermissionGrants](Get-PnPTenantServicePrincipalPermissionGrants.md) -{{Manually Enter Get-PnPTenantServicePrincipalPermissionGrants Description Here}} - -### [Get-PnPTenantServicePrincipalPermissionRequests](Get-PnPTenantServicePrincipalPermissionRequests.md) -{{Manually Enter Get-PnPTenantServicePrincipalPermissionRequests Description Here}} - -### [Get-PnPTenantSite](Get-PnPTenantSite.md) -{{Manually Enter Get-PnPTenantSite Description Here}} - -### [Get-PnPTenantTheme](Get-PnPTenantTheme.md) -{{Manually Enter Get-PnPTenantTheme Description Here}} - -### [Get-PnPTerm](Get-PnPTerm.md) -{{Manually Enter Get-PnPTerm Description Here}} - -### [Get-PnPTermGroup](Get-PnPTermGroup.md) -{{Manually Enter Get-PnPTermGroup Description Here}} - -### [Get-PnPTermSet](Get-PnPTermSet.md) -{{Manually Enter Get-PnPTermSet Description Here}} - -### [Get-PnPTheme](Get-PnPTheme.md) -{{Manually Enter Get-PnPTheme Description Here}} - -### [Get-PnPTimeZoneId](Get-PnPTimeZoneId.md) -{{Manually Enter Get-PnPTimeZoneId Description Here}} - -### [Get-PnPUnifiedGroup](Get-PnPUnifiedGroup.md) -{{Manually Enter Get-PnPUnifiedGroup Description Here}} - -### [Get-PnPUnifiedGroupMembers](Get-PnPUnifiedGroupMembers.md) -{{Manually Enter Get-PnPUnifiedGroupMembers Description Here}} - -### [Get-PnPUnifiedGroupOwners](Get-PnPUnifiedGroupOwners.md) -{{Manually Enter Get-PnPUnifiedGroupOwners Description Here}} - -### [Get-PnPUPABulkImportStatus](Get-PnPUPABulkImportStatus.md) -{{Manually Enter Get-PnPUPABulkImportStatus Description Here}} - -### [Get-PnPUser](Get-PnPUser.md) -{{Manually Enter Get-PnPUser Description Here}} - -### [Get-PnPUserProfileProperty](Get-PnPUserProfileProperty.md) -{{Manually Enter Get-PnPUserProfileProperty Description Here}} - -### [Get-PnPView](Get-PnPView.md) -{{Manually Enter Get-PnPView Description Here}} - -### [Get-PnPWeb](Get-PnPWeb.md) -{{Manually Enter Get-PnPWeb Description Here}} - -### [Get-PnPWebhookSubscriptions](Get-PnPWebhookSubscriptions.md) -{{Manually Enter Get-PnPWebhookSubscriptions Description Here}} - -### [Get-PnPWebPart](Get-PnPWebPart.md) -{{Manually Enter Get-PnPWebPart Description Here}} - -### [Get-PnPWebPartProperty](Get-PnPWebPartProperty.md) -{{Manually Enter Get-PnPWebPartProperty Description Here}} - -### [Get-PnPWebPartXml](Get-PnPWebPartXml.md) -{{Manually Enter Get-PnPWebPartXml Description Here}} - -### [Get-PnPWebTemplates](Get-PnPWebTemplates.md) -{{Manually Enter Get-PnPWebTemplates Description Here}} - -### [Get-PnPWikiPageContent](Get-PnPWikiPageContent.md) -{{Manually Enter Get-PnPWikiPageContent Description Here}} - -### [Get-PnPWorkflowDefinition](Get-PnPWorkflowDefinition.md) -{{Manually Enter Get-PnPWorkflowDefinition Description Here}} - -### [Get-PnPWorkflowInstance](Get-PnPWorkflowInstance.md) -{{Manually Enter Get-PnPWorkflowInstance Description Here}} - -### [Get-PnPWorkflowSubscription](Get-PnPWorkflowSubscription.md) -{{Manually Enter Get-PnPWorkflowSubscription Description Here}} - -### [Grant-PnPHubSiteRights](Grant-PnPHubSiteRights.md) -{{Manually Enter Grant-PnPHubSiteRights Description Here}} - -### [Grant-PnPSiteDesignRights](Grant-PnPSiteDesignRights.md) -{{Manually Enter Grant-PnPSiteDesignRights Description Here}} - -### [Grant-PnPTenantServicePrincipalPermission](Grant-PnPTenantServicePrincipalPermission.md) -{{Manually Enter Grant-PnPTenantServicePrincipalPermission Description Here}} - -### [Import-PnPAppPackage](Import-PnPAppPackage.md) -{{Manually Enter Import-PnPAppPackage Description Here}} - -### [Import-PnPTaxonomy](Import-PnPTaxonomy.md) -{{Manually Enter Import-PnPTaxonomy Description Here}} - -### [Import-PnPTermGroupFromXml](Import-PnPTermGroupFromXml.md) -{{Manually Enter Import-PnPTermGroupFromXml Description Here}} - -### [Import-PnPTermSet](Import-PnPTermSet.md) -{{Manually Enter Import-PnPTermSet Description Here}} - -### [Install-PnPApp](Install-PnPApp.md) -{{Manually Enter Install-PnPApp Description Here}} - -### [Install-PnPSolution](Install-PnPSolution.md) -{{Manually Enter Install-PnPSolution Description Here}} - -### [Invoke-PnPQuery](Invoke-PnPQuery.md) -{{Manually Enter Invoke-PnPQuery Description Here}} - -### [Invoke-PnPSiteDesign](Invoke-PnPSiteDesign.md) -{{Manually Enter Invoke-PnPSiteDesign Description Here}} - -### [Invoke-PnPWebAction](Invoke-PnPWebAction.md) -{{Manually Enter Invoke-PnPWebAction Description Here}} - -### [Measure-PnPList](Measure-PnPList.md) -{{Manually Enter Measure-PnPList Description Here}} - -### [Measure-PnPResponseTime](Measure-PnPResponseTime.md) -{{Manually Enter Measure-PnPResponseTime Description Here}} - -### [Measure-PnPWeb](Measure-PnPWeb.md) -{{Manually Enter Measure-PnPWeb Description Here}} - -### [Move-PnPClientSideComponent](Move-PnPClientSideComponent.md) -{{Manually Enter Move-PnPClientSideComponent Description Here}} - -### [Move-PnPFile](Move-PnPFile.md) -{{Manually Enter Move-PnPFile Description Here}} - -### [Move-PnPFolder](Move-PnPFolder.md) -{{Manually Enter Move-PnPFolder Description Here}} - -### [Move-PnPItemProxy](Move-PnPItemProxy.md) -{{Manually Enter Move-PnPItemProxy Description Here}} - -### [Move-PnPListItemToRecycleBin](Move-PnPListItemToRecycleBin.md) -{{Manually Enter Move-PnPListItemToRecycleBin Description Here}} - -### [Move-PnpRecycleBinItem](Move-PnpRecycleBinItem.md) -{{Manually Enter Move-PnpRecycleBinItem Description Here}} - -### [New-PnPAzureCertificate](New-PnPAzureCertificate.md) -{{Manually Enter New-PnPAzureCertificate Description Here}} - -### [New-PnPExtensibilityHandlerObject](New-PnPExtensibilityHandlerObject.md) -{{Manually Enter New-PnPExtensibilityHandlerObject Description Here}} - -### [New-PnPGroup](New-PnPGroup.md) -{{Manually Enter New-PnPGroup Description Here}} - -### [New-PnPList](New-PnPList.md) -{{Manually Enter New-PnPList Description Here}} - -### [New-PnPPersonalSite](New-PnPPersonalSite.md) -{{Manually Enter New-PnPPersonalSite Description Here}} - -### [New-PnPProvisioningTemplate](New-PnPProvisioningTemplate.md) -{{Manually Enter New-PnPProvisioningTemplate Description Here}} - -### [New-PnPProvisioningTemplateFromFolder](New-PnPProvisioningTemplateFromFolder.md) -{{Manually Enter New-PnPProvisioningTemplateFromFolder Description Here}} - -### [New-PnPSite](New-PnPSite.md) -{{Manually Enter New-PnPSite Description Here}} - -### [New-PnPTenantSequence](New-PnPTenantSequence.md) -{{Manually Enter New-PnPTenantSequence Description Here}} - -### [New-PnPTenantSequenceCommunicationSite](New-PnPTenantSequenceCommunicationSite.md) -{{Manually Enter New-PnPTenantSequenceCommunicationSite Description Here}} - -### [New-PnPTenantSequenceTeamNoGroupSite](New-PnPTenantSequenceTeamNoGroupSite.md) -{{Manually Enter New-PnPTenantSequenceTeamNoGroupSite Description Here}} - -### [New-PnPTenantSequenceTeamNoGroupSubSite](New-PnPTenantSequenceTeamNoGroupSubSite.md) -{{Manually Enter New-PnPTenantSequenceTeamNoGroupSubSite Description Here}} - -### [New-PnPTenantSequenceTeamSite](New-PnPTenantSequenceTeamSite.md) -{{Manually Enter New-PnPTenantSequenceTeamSite Description Here}} - -### [New-PnPTenantSite](New-PnPTenantSite.md) -{{Manually Enter New-PnPTenantSite Description Here}} - -### [New-PnPTenantTemplate](New-PnPTenantTemplate.md) -{{Manually Enter New-PnPTenantTemplate Description Here}} - -### [New-PnPTerm](New-PnPTerm.md) -{{Manually Enter New-PnPTerm Description Here}} - -### [New-PnPTermGroup](New-PnPTermGroup.md) -{{Manually Enter New-PnPTermGroup Description Here}} - -### [New-PnPTermSet](New-PnPTermSet.md) -{{Manually Enter New-PnPTermSet Description Here}} - -### [New-PnPUnifiedGroup](New-PnPUnifiedGroup.md) -{{Manually Enter New-PnPUnifiedGroup Description Here}} - -### [New-PnPUPABulkImportJob](New-PnPUPABulkImportJob.md) -{{Manually Enter New-PnPUPABulkImportJob Description Here}} - -### [New-PnPUser](New-PnPUser.md) -{{Manually Enter New-PnPUser Description Here}} - -### [New-PnPWeb](New-PnPWeb.md) -{{Manually Enter New-PnPWeb Description Here}} - -### [Publish-PnPApp](Publish-PnPApp.md) -{{Manually Enter Publish-PnPApp Description Here}} - -### [Read-PnPProvisioningTemplate](Read-PnPProvisioningTemplate.md) -{{Manually Enter Read-PnPProvisioningTemplate Description Here}} - -### [Read-PnPTenantTemplate](Read-PnPTenantTemplate.md) -{{Manually Enter Read-PnPTenantTemplate Description Here}} - -### [Register-PnPHubSite](Register-PnPHubSite.md) -{{Manually Enter Register-PnPHubSite Description Here}} - -### [Remove-PnPAlert](Remove-PnPAlert.md) -{{Manually Enter Remove-PnPAlert Description Here}} - -### [Remove-PnPApp](Remove-PnPApp.md) -{{Manually Enter Remove-PnPApp Description Here}} - -### [Remove-PnPClientSideComponent](Remove-PnPClientSideComponent.md) -{{Manually Enter Remove-PnPClientSideComponent Description Here}} - -### [Remove-PnPClientSidePage](Remove-PnPClientSidePage.md) -{{Manually Enter Remove-PnPClientSidePage Description Here}} - -### [Remove-PnPContentType](Remove-PnPContentType.md) -{{Manually Enter Remove-PnPContentType Description Here}} - -### [Remove-PnPContentTypeFromDocumentSet](Remove-PnPContentTypeFromDocumentSet.md) -{{Manually Enter Remove-PnPContentTypeFromDocumentSet Description Here}} - -### [Remove-PnPContentTypeFromList](Remove-PnPContentTypeFromList.md) -{{Manually Enter Remove-PnPContentTypeFromList Description Here}} - -### [Remove-PnPCustomAction](Remove-PnPCustomAction.md) -{{Manually Enter Remove-PnPCustomAction Description Here}} - -### [Remove-PnPEventReceiver](Remove-PnPEventReceiver.md) -{{Manually Enter Remove-PnPEventReceiver Description Here}} - -### [Remove-PnPField](Remove-PnPField.md) -{{Manually Enter Remove-PnPField Description Here}} - -### [Remove-PnPFieldFromContentType](Remove-PnPFieldFromContentType.md) -{{Manually Enter Remove-PnPFieldFromContentType Description Here}} - -### [Remove-PnPFile](Remove-PnPFile.md) -{{Manually Enter Remove-PnPFile Description Here}} - -### [Remove-PnPFileFromProvisioningTemplate](Remove-PnPFileFromProvisioningTemplate.md) -{{Manually Enter Remove-PnPFileFromProvisioningTemplate Description Here}} - -### [Remove-PnPFolder](Remove-PnPFolder.md) -{{Manually Enter Remove-PnPFolder Description Here}} - -### [Remove-PnPGroup](Remove-PnPGroup.md) -{{Manually Enter Remove-PnPGroup Description Here}} - -### [Remove-PnPHubSiteAssociation](Remove-PnPHubSiteAssociation.md) -{{Manually Enter Remove-PnPHubSiteAssociation Description Here}} - -### [Remove-PnPIndexedProperty](Remove-PnPIndexedProperty.md) -{{Manually Enter Remove-PnPIndexedProperty Description Here}} - -### [Remove-PnPJavaScriptLink](Remove-PnPJavaScriptLink.md) -{{Manually Enter Remove-PnPJavaScriptLink Description Here}} - -### [Remove-PnPList](Remove-PnPList.md) -{{Manually Enter Remove-PnPList Description Here}} - -### [Remove-PnPListItem](Remove-PnPListItem.md) -{{Manually Enter Remove-PnPListItem Description Here}} - -### [Remove-PnPNavigationNode](Remove-PnPNavigationNode.md) -{{Manually Enter Remove-PnPNavigationNode Description Here}} - -### [Remove-PnPPropertyBagValue](Remove-PnPPropertyBagValue.md) -{{Manually Enter Remove-PnPPropertyBagValue Description Here}} - -### [Remove-PnPPublishingImageRendition](Remove-PnPPublishingImageRendition.md) -{{Manually Enter Remove-PnPPublishingImageRendition Description Here}} - -### [Remove-PnPRoleDefinition](Remove-PnPRoleDefinition.md) -{{Manually Enter Remove-PnPRoleDefinition Description Here}} - -### [Remove-PnPSearchConfiguration](Remove-PnPSearchConfiguration.md) -{{Manually Enter Remove-PnPSearchConfiguration Description Here}} - -### [Remove-PnPSiteClassification](Remove-PnPSiteClassification.md) -{{Manually Enter Remove-PnPSiteClassification Description Here}} - -### [Remove-PnPSiteCollectionAdmin](Remove-PnPSiteCollectionAdmin.md) -{{Manually Enter Remove-PnPSiteCollectionAdmin Description Here}} - -### [Remove-PnPSiteCollectionAppCatalog](Remove-PnPSiteCollectionAppCatalog.md) -{{Manually Enter Remove-PnPSiteCollectionAppCatalog Description Here}} - -### [Remove-PnPSiteDesign](Remove-PnPSiteDesign.md) -{{Manually Enter Remove-PnPSiteDesign Description Here}} - -### [Remove-PnPSiteDesignTask](Remove-PnPSiteDesignTask.md) -{{Manually Enter Remove-PnPSiteDesignTask Description Here}} - -### [Remove-PnPSiteScript](Remove-PnPSiteScript.md) -{{Manually Enter Remove-PnPSiteScript Description Here}} - -### [Remove-PnPStorageEntity](Remove-PnPStorageEntity.md) -{{Manually Enter Remove-PnPStorageEntity Description Here}} - -### [Remove-PnPStoredCredential](Remove-PnPStoredCredential.md) -{{Manually Enter Remove-PnPStoredCredential Description Here}} - -### [Remove-PnPTaxonomyItem](Remove-PnPTaxonomyItem.md) -{{Manually Enter Remove-PnPTaxonomyItem Description Here}} - -### [Remove-PnPTenantCdnOrigin](Remove-PnPTenantCdnOrigin.md) -{{Manually Enter Remove-PnPTenantCdnOrigin Description Here}} - -### [Remove-PnPTenantSite](Remove-PnPTenantSite.md) -{{Manually Enter Remove-PnPTenantSite Description Here}} - -### [Remove-PnPTenantTheme](Remove-PnPTenantTheme.md) -{{Manually Enter Remove-PnPTenantTheme Description Here}} - -### [Remove-PnPTermGroup](Remove-PnPTermGroup.md) -{{Manually Enter Remove-PnPTermGroup Description Here}} - -### [Remove-PnPUnifiedGroup](Remove-PnPUnifiedGroup.md) -{{Manually Enter Remove-PnPUnifiedGroup Description Here}} - -### [Remove-PnPUser](Remove-PnPUser.md) -{{Manually Enter Remove-PnPUser Description Here}} - -### [Remove-PnPUserFromGroup](Remove-PnPUserFromGroup.md) -{{Manually Enter Remove-PnPUserFromGroup Description Here}} - -### [Remove-PnPView](Remove-PnPView.md) -{{Manually Enter Remove-PnPView Description Here}} - -### [Remove-PnPWeb](Remove-PnPWeb.md) -{{Manually Enter Remove-PnPWeb Description Here}} - -### [Remove-PnPWebhookSubscription](Remove-PnPWebhookSubscription.md) -{{Manually Enter Remove-PnPWebhookSubscription Description Here}} - -### [Remove-PnPWebPart](Remove-PnPWebPart.md) -{{Manually Enter Remove-PnPWebPart Description Here}} - -### [Remove-PnPWikiPage](Remove-PnPWikiPage.md) -{{Manually Enter Remove-PnPWikiPage Description Here}} - -### [Remove-PnPWorkflowDefinition](Remove-PnPWorkflowDefinition.md) -{{Manually Enter Remove-PnPWorkflowDefinition Description Here}} - -### [Remove-PnPWorkflowSubscription](Remove-PnPWorkflowSubscription.md) -{{Manually Enter Remove-PnPWorkflowSubscription Description Here}} - -### [Rename-PnPFile](Rename-PnPFile.md) -{{Manually Enter Rename-PnPFile Description Here}} - -### [Rename-PnPFolder](Rename-PnPFolder.md) -{{Manually Enter Rename-PnPFolder Description Here}} - -### [Request-PnPReIndexList](Request-PnPReIndexList.md) -{{Manually Enter Request-PnPReIndexList Description Here}} - -### [Request-PnPReIndexWeb](Request-PnPReIndexWeb.md) -{{Manually Enter Request-PnPReIndexWeb Description Here}} - -### [Reset-PnPFileVersion](Reset-PnPFileVersion.md) -{{Manually Enter Reset-PnPFileVersion Description Here}} - -### [Resolve-PnPFolder](Resolve-PnPFolder.md) -{{Manually Enter Resolve-PnPFolder Description Here}} - -### [Restore-PnpRecycleBinItem](Restore-PnpRecycleBinItem.md) -{{Manually Enter Restore-PnpRecycleBinItem Description Here}} - -### [Restore-PnPTenantRecycleBinItem](Restore-PnPTenantRecycleBinItem.md) -{{Manually Enter Restore-PnPTenantRecycleBinItem Description Here}} - -### [Resume-PnPWorkflowInstance](Resume-PnPWorkflowInstance.md) -{{Manually Enter Resume-PnPWorkflowInstance Description Here}} - -### [Revoke-PnPSiteDesignRights](Revoke-PnPSiteDesignRights.md) -{{Manually Enter Revoke-PnPSiteDesignRights Description Here}} - -### [Revoke-PnPTenantServicePrincipalPermission](Revoke-PnPTenantServicePrincipalPermission.md) -{{Manually Enter Revoke-PnPTenantServicePrincipalPermission Description Here}} - -### [Save-PnPProvisioningTemplate](Save-PnPProvisioningTemplate.md) -{{Manually Enter Save-PnPProvisioningTemplate Description Here}} - -### [Save-PnPTenantTemplate](Save-PnPTenantTemplate.md) -{{Manually Enter Save-PnPTenantTemplate Description Here}} - -### [Send-PnPMail](Send-PnPMail.md) -{{Manually Enter Send-PnPMail Description Here}} - -### [Set-PnPAppSideLoading](Set-PnPAppSideLoading.md) -{{Manually Enter Set-PnPAppSideLoading Description Here}} - -### [Set-PnPAuditing](Set-PnPAuditing.md) -{{Manually Enter Set-PnPAuditing Description Here}} - -### [Set-PnPAvailablePageLayouts](Set-PnPAvailablePageLayouts.md) -{{Manually Enter Set-PnPAvailablePageLayouts Description Here}} - -### [Set-PnPClientSidePage](Set-PnPClientSidePage.md) -{{Manually Enter Set-PnPClientSidePage Description Here}} - -### [Set-PnPClientSideText](Set-PnPClientSideText.md) -{{Manually Enter Set-PnPClientSideText Description Here}} - -### [Set-PnPClientSideWebPart](Set-PnPClientSideWebPart.md) -{{Manually Enter Set-PnPClientSideWebPart Description Here}} - -### [Set-PnPContext](Set-PnPContext.md) -{{Manually Enter Set-PnPContext Description Here}} - -### [Set-PnPDefaultColumnValues](Set-PnPDefaultColumnValues.md) -{{Manually Enter Set-PnPDefaultColumnValues Description Here}} - -### [Set-PnPDefaultContentTypeToList](Set-PnPDefaultContentTypeToList.md) -{{Manually Enter Set-PnPDefaultContentTypeToList Description Here}} - -### [Set-PnPDefaultPageLayout](Set-PnPDefaultPageLayout.md) -{{Manually Enter Set-PnPDefaultPageLayout Description Here}} - -### [Set-PnPDocumentSetField](Set-PnPDocumentSetField.md) -{{Manually Enter Set-PnPDocumentSetField Description Here}} - -### [Set-PnPField](Set-PnPField.md) -{{Manually Enter Set-PnPField Description Here}} - -### [Set-PnPFileCheckedIn](Set-PnPFileCheckedIn.md) -{{Manually Enter Set-PnPFileCheckedIn Description Here}} - -### [Set-PnPFileCheckedOut](Set-PnPFileCheckedOut.md) -{{Manually Enter Set-PnPFileCheckedOut Description Here}} - -### [Set-PnPGroup](Set-PnPGroup.md) -{{Manually Enter Set-PnPGroup Description Here}} - -### [Set-PnPGroupPermissions](Set-PnPGroupPermissions.md) -{{Manually Enter Set-PnPGroupPermissions Description Here}} - -### [Set-PnPHideDefaultThemes](Set-PnPHideDefaultThemes.md) -{{Manually Enter Set-PnPHideDefaultThemes Description Here}} - -### [Set-PnPHomePage](Set-PnPHomePage.md) -{{Manually Enter Set-PnPHomePage Description Here}} - -### [Set-PnPHubSite](Set-PnPHubSite.md) -{{Manually Enter Set-PnPHubSite Description Here}} - -### [Set-PnPIndexedProperties](Set-PnPIndexedProperties.md) -{{Manually Enter Set-PnPIndexedProperties Description Here}} - -### [Set-PnPInPlaceRecordsManagement](Set-PnPInPlaceRecordsManagement.md) -{{Manually Enter Set-PnPInPlaceRecordsManagement Description Here}} - -### [Set-PnPLabel](Set-PnPLabel.md) -{{Manually Enter Set-PnPLabel Description Here}} - -### [Set-PnPList](Set-PnPList.md) -{{Manually Enter Set-PnPList Description Here}} - -### [Set-PnPListInformationRightsManagement](Set-PnPListInformationRightsManagement.md) -{{Manually Enter Set-PnPListInformationRightsManagement Description Here}} - -### [Set-PnPListItem](Set-PnPListItem.md) -{{Manually Enter Set-PnPListItem Description Here}} - -### [Set-PnPListItemAsRecord](Set-PnPListItemAsRecord.md) -{{Manually Enter Set-PnPListItemAsRecord Description Here}} - -### [Set-PnPListItemPermission](Set-PnPListItemPermission.md) -{{Manually Enter Set-PnPListItemPermission Description Here}} - -### [Set-PnPListPermission](Set-PnPListPermission.md) -{{Manually Enter Set-PnPListPermission Description Here}} - -### [Set-PnPListRecordDeclaration](Set-PnPListRecordDeclaration.md) -{{Manually Enter Set-PnPListRecordDeclaration Description Here}} - -### [Set-PnPMasterPage](Set-PnPMasterPage.md) -{{Manually Enter Set-PnPMasterPage Description Here}} - -### [Set-PnPMinimalDownloadStrategy](Set-PnPMinimalDownloadStrategy.md) -{{Manually Enter Set-PnPMinimalDownloadStrategy Description Here}} - -### [Set-PnPPropertyBagValue](Set-PnPPropertyBagValue.md) -{{Manually Enter Set-PnPPropertyBagValue Description Here}} - -### [Set-PnPProvisioningTemplateMetadata](Set-PnPProvisioningTemplateMetadata.md) -{{Manually Enter Set-PnPProvisioningTemplateMetadata Description Here}} - -### [Set-PnPRequestAccessEmails](Set-PnPRequestAccessEmails.md) -{{Manually Enter Set-PnPRequestAccessEmails Description Here}} - -### [Set-PnPSearchConfiguration](Set-PnPSearchConfiguration.md) -{{Manually Enter Set-PnPSearchConfiguration Description Here}} - -### [Set-PnPSite](Set-PnPSite.md) -{{Manually Enter Set-PnPSite Description Here}} - -### [Set-PnPSiteClosure](Set-PnPSiteClosure.md) -{{Manually Enter Set-PnPSiteClosure Description Here}} - -### [Set-PnPSiteDesign](Set-PnPSiteDesign.md) -{{Manually Enter Set-PnPSiteDesign Description Here}} - -### [Set-PnPSitePolicy](Set-PnPSitePolicy.md) -{{Manually Enter Set-PnPSitePolicy Description Here}} - -### [Set-PnPSiteScript](Set-PnPSiteScript.md) -{{Manually Enter Set-PnPSiteScript Description Here}} - -### [Set-PnPStorageEntity](Set-PnPStorageEntity.md) -{{Manually Enter Set-PnPStorageEntity Description Here}} - -### [Set-PnPTaxonomyFieldValue](Set-PnPTaxonomyFieldValue.md) -{{Manually Enter Set-PnPTaxonomyFieldValue Description Here}} - -### [Set-PnPTenant](Set-PnPTenant.md) -{{Manually Enter Set-PnPTenant Description Here}} - -### [Set-PnPTenantCdnEnabled](Set-PnPTenantCdnEnabled.md) -{{Manually Enter Set-PnPTenantCdnEnabled Description Here}} - -### [Set-PnPTenantCdnPolicy](Set-PnPTenantCdnPolicy.md) -{{Manually Enter Set-PnPTenantCdnPolicy Description Here}} - -### [Set-PnPTenantSite](Set-PnPTenantSite.md) -{{Manually Enter Set-PnPTenantSite Description Here}} - -### [Set-PnPTheme](Set-PnPTheme.md) -{{Manually Enter Set-PnPTheme Description Here}} - -### [Set-PnPTraceLog](Set-PnPTraceLog.md) -{{Manually Enter Set-PnPTraceLog Description Here}} - -### [Set-PnPUnifiedGroup](Set-PnPUnifiedGroup.md) -{{Manually Enter Set-PnPUnifiedGroup Description Here}} - -### [Set-PnPUserProfileProperty](Set-PnPUserProfileProperty.md) -{{Manually Enter Set-PnPUserProfileProperty Description Here}} - -### [Set-PnPView](Set-PnPView.md) -{{Manually Enter Set-PnPView Description Here}} - -### [Set-PnPWeb](Set-PnPWeb.md) -{{Manually Enter Set-PnPWeb Description Here}} - -### [Set-PnPWebhookSubscription](Set-PnPWebhookSubscription.md) -{{Manually Enter Set-PnPWebhookSubscription Description Here}} - -### [Set-PnPWebPartProperty](Set-PnPWebPartProperty.md) -{{Manually Enter Set-PnPWebPartProperty Description Here}} - -### [Set-PnPWebPermission](Set-PnPWebPermission.md) -{{Manually Enter Set-PnPWebPermission Description Here}} - -### [Set-PnPWebTheme](Set-PnPWebTheme.md) -{{Manually Enter Set-PnPWebTheme Description Here}} - -### [Set-PnPWikiPageContent](Set-PnPWikiPageContent.md) -{{Manually Enter Set-PnPWikiPageContent Description Here}} - -### [Start-PnPWorkflowInstance](Start-PnPWorkflowInstance.md) -{{Manually Enter Start-PnPWorkflowInstance Description Here}} - -### [Stop-PnPWorkflowInstance](Stop-PnPWorkflowInstance.md) -{{Manually Enter Stop-PnPWorkflowInstance Description Here}} - -### [Submit-PnPSearchQuery](Submit-PnPSearchQuery.md) -{{Manually Enter Submit-PnPSearchQuery Description Here}} - -### [Test-PnPListItemIsRecord](Test-PnPListItemIsRecord.md) -{{Manually Enter Test-PnPListItemIsRecord Description Here}} - -### [Test-PnPOffice365GroupAliasIsUsed](Test-PnPOffice365GroupAliasIsUsed.md) -{{Manually Enter Test-PnPOffice365GroupAliasIsUsed Description Here}} - -### [Test-PnPTenantTemplate](Test-PnPTenantTemplate.md) -{{Manually Enter Test-PnPTenantTemplate Description Here}} - -### [Uninstall-PnPApp](Uninstall-PnPApp.md) -{{Manually Enter Uninstall-PnPApp Description Here}} - -### [Uninstall-PnPAppInstance](Uninstall-PnPAppInstance.md) -{{Manually Enter Uninstall-PnPAppInstance Description Here}} - -### [Uninstall-PnPSolution](Uninstall-PnPSolution.md) -{{Manually Enter Uninstall-PnPSolution Description Here}} - -### [Unpublish-PnPApp](Unpublish-PnPApp.md) -{{Manually Enter Unpublish-PnPApp Description Here}} - -### [Unregister-PnPHubSite](Unregister-PnPHubSite.md) -{{Manually Enter Unregister-PnPHubSite Description Here}} - -### [Update-PnPApp](Update-PnPApp.md) -{{Manually Enter Update-PnPApp Description Here}} - -### [Update-PnPSiteClassification](Update-PnPSiteClassification.md) -{{Manually Enter Update-PnPSiteClassification Description Here}} diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-DatabaseToAvailabilityGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-DatabaseToAvailabilityGroup.md deleted file mode 100644 index 120cde8990..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-DatabaseToAvailabilityGroup.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-databasetoavailabilitygroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-DatabaseToAvailabilityGroup -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-DatabaseToAvailabilityGroup - -## SYNOPSIS -Adds one or more SharePoint databases to a SQL Server Availability Group - -## SYNTAX - -### Default -``` -Add-DatabaseToAvailabilityGroup [-AGName] <String> [-AssignmentCollection <SPAssignmentCollection>] - -DatabaseName <String> [-FileShare <String>] [<CommonParameters>] -``` - -### AllDatabases -``` -Add-DatabaseToAvailabilityGroup [-AGName] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-FileShare <String>] [-ProcessAllDatabases] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Add-DatabaseToAvailabilityGroup cmdlet to add an availability group to the farm. - -## EXAMPLES - -### Example 1 -``` -Add-DatabaseToAvailabilityGroup -AGName MyAvailabilityGroup -DatabaseName WSS_Content -FileShare \\backup\share\ -``` - -This example adds the database WSS_Content to the availability group named "MyAvailabilityGroup". - -### Example 2 -``` -Add-DatabaseToAvailabilityGroup -AGName MyAvailabilityGroup -ProcessAllDatabases -FileShare \\backup\share\ -``` - -This example adds all SharePoint databases attached to the farm to the availability group named "MyAvailabilityGroup" - -## PARAMETERS - -### -AGName -The name of the availability group from which the databases are being added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE:** When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseName -The name of the database to be added to the availability group. -**Note:** This parameter should not be used in conjunction with the **ProcessAllDatabases** parameter. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileShare -When a database is being added to the availability group, backup / restores are done from this location to propagate the database to all replicas. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProcessAllDatabases -Adds all databases from the current SharePoint farm into the availability group. - -```yaml -Type: SwitchParameter -Parameter Sets: AllDatabases -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchResource.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchResource.md deleted file mode 100644 index 1dd0afba9d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchResource.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-fastsearchresource -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Add-FASTSearchResource ---- - -# Add-FASTSearchResource - -## SYNOPSIS -Uploads a resource to the resource store. - -## SYNTAX - -``` -Add-FASTSearchResource [-Path] <String> [-FilePath] <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet uploads a specified file, located in the local environment, to the Microsoft FAST Search Server 2010 for SharePoint resource store. -The location of the resource store is typically specified in %FASTSEARCH%/etc/Admin.config (where %FASTSEARCH% is the FAST Search Server 2010 for SharePoint installation folder.) Specify a unique location of the resource in the upload URI. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>Add-FASTSearchResource dictionaries\spellcheck\check_en.aut c:\check_en.aut -``` - -This example uploads the file c:\check_en.aut to dictionaries\spellcheck\check_en.aut to the resource store. - -## PARAMETERS - -### -Path -Partial URI within the resource store where the file will be uploaded. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: ResourceURI -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilePath -Path of the local resource to be uploaded. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchResource](Get-FASTSearchResource.md) - -[Remove-FASTSearchResource](Remove-FASTSearchResource.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchSpelltuning.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchSpelltuning.md deleted file mode 100644 index e48782a276..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchSpelltuning.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-fastsearchspelltuning -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Add-FASTSearchSpelltuning ---- - -# Add-FASTSearchSpelltuning - -## SYNOPSIS -Enables the spell tuning processor, used to fine-tune a spell check dictionary. - -## SYNTAX - -``` -Add-FASTSearchSpelltuning [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet activates alignment of the spell checking dictionary with the index, so that spell checking dictionaries are built from content that is fed into the index (not from standardized spelling dictionaries). - -The Did You Mean feature is dictionary based; when spell tuning is activated, Did You Mean only suggests terms that are actually in the index. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### (FAST Server for SharePoint 2010) -``` - -``` - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSpelltuningStatus](Get-FASTSearchSpelltuningStatus.md) - -[Remove-FASTSearchSpelltuning](Remove-FASTSearchSpelltuning.md) - -[Reset-FASTSearchSpelltuning](Reset-FASTSearchSpelltuning.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPAppDeniedEndpoint.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPAppDeniedEndpoint.md deleted file mode 100644 index e5d9e7906c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPAppDeniedEndpoint.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spappdeniedendpoint -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPAppDeniedEndpoint -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPAppDeniedEndpoint - -## SYNOPSIS - -Adds a relative URL endpoint of a server to the list of app-denied endpoints. - - - -## SYNTAX - -``` -Add-SPAppDeniedEndpoint [-Endpoint] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Add-SPAppDeniedEndpoint cmdlet to add a relative URL endpoint of a server to the list of app-denied endpoints in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE------------- -``` -Add-SPAppDeniedEndpoint -Endpoint "/_vti_bin/contoso/service.asmx" -``` - -This example adds the "/_vti_bin/contoso/service.asmx" endpoint to the list of denied endpoints for apps. -Apps will not be able to access this endpoint. - -## PARAMETERS - -### -Endpoint -Specifies a relative URL endpoint of a server that is added to the list of app-denied endpoints. -Apps will not be able to access relative URL endpoints of a server that exist in the app-denied endpoint list. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-SPAppDeniedEndpoints](Clear-SPAppDeniedEndpoints.md) - -[Get-SPAppDeniedEndpoints](Get-SPAppDeniedEndpoints.md) - -[Remove-SPAppDeniedEndpoint](Remove-SPAppDeniedEndpoint.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPClaimTypeMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPClaimTypeMapping.md deleted file mode 100644 index a31476b3d1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPClaimTypeMapping.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spclaimtypemapping -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPClaimTypeMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPClaimTypeMapping - -## SYNOPSIS - -Adds a claim mapping to a trusted security token service (STS) identity provider. - - - -## SYNTAX - -``` -Add-SPClaimTypeMapping [-Identity] <SPClaimMappingPipeBind> - [-TrustedIdentityTokenIssuer] <SPTrustedIdentityTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPClaimTypeMapping cmdlet adds a claim type mapping rule to a security token service (STS) identity provider from a farm trust STS authentication provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>Get-SPTrustedIdentityProvider -Name "LiveIDSTS" | Add-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier" -IncomingClaimTypeDisplayName "PUID" -LocalClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/thumbprint" -``` - -This example adds a claim mapping to a trusted identity token issuer. - -## PARAMETERS - -### -Identity -Specifies the STS for the farm that will issue the security token for the identity provider. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a claim mapping rule (for example, ClaimMap1); or an instance of a valid SPClaimMapping object. - -```yaml -Type: SPClaimMappingPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -TrustedIdentityTokenIssuer -Specifies the farm trust Token Issuer (STS authentication provider). - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of an authentication provider (for example, MyIDprovider1); or an instance of a valid SPTrustedIdentityTokenIssuer object. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Force -Overwrites the claim mapping rule if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPDiagnosticsPerformanceCounter.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPDiagnosticsPerformanceCounter.md deleted file mode 100644 index fab1e0ffa1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPDiagnosticsPerformanceCounter.md +++ /dev/null @@ -1,291 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spdiagnosticsperformancecounter -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPDiagnosticsPerformanceCounter -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPDiagnosticsPerformanceCounter - -## SYNOPSIS - -Adds a new instance of a performance counter to a Web front end computer or a database server. - - - -## SYNTAX - -### AddCounter -``` -Add-SPDiagnosticsPerformanceCounter [-Category] <String> -Counter <String> [-AllInstances] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseServer] [-WebFrontEnd] [-WhatIf] - [<CommonParameters>] -``` - -### AddInstance -``` -Add-SPDiagnosticsPerformanceCounter [-Category] <String> [-Counter <String>] -Instance <String> [-AllInstances] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseServer] [-WebFrontEnd] [-WhatIf] - [<CommonParameters>] -``` - -### AddMultipleCounters -``` -Add-SPDiagnosticsPerformanceCounter [-Category] <String> [-Instance <String>] [-AllInstances] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseServer] [-WebFrontEnd] [-WhatIf] - -CounterList <String[]> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Add-SPDiagnosticsPerformanceCounter cmdlet adds a performance counter to a front end Web server or a database server. -A performance counter is read and recorded in the usage database. -By default, the new performance counter is added to the database servers in the farm. - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -C:\PS>Add-SPDiagnosticsPerformanceCounter -category ASP.NET -Counter "Requests Queued" -``` - -This example adds the counter that has the name ASP.NET\Requests Queued on front end Web servers. - -### ------------------EXAMPLE 2------------------ -``` -C:\PS>Add-SPDiagnosticsPerformanceCounter -category PhysicalDisk -counter "Avg. Disk Queue Length" -allinstances -``` - -This example adds all instances of the counter PhysicalDisk in the category Avg. -Disk Queue Length on front end Web servers. - -### ------------------EXAMPLE 3------------------ -``` -C:\PS>Add-SPDiagnosticsPerformanceCounter -category Processor -counter "% Processor Time" -instance "_Total" -databaseserver -``` - -This example adds the _Total instance of the counter % Processor Time in the category Processor on database servers. - -## PARAMETERS - -### -Category -Specifies the category of performance counter to add to the target Web front end computer or database server. - -The type must be a valid name of a category of performance counters; for example, ASP.NET, PhysicalDisk, or Processor. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Counter -Specifies the type of counter to add to the target Web front end computer or database server. - -The type must be a valid name of counter type; for example, Requests Queued, Avg. -Disk Queue Length, and % Processor Time. - -```yaml -Type: String -Parameter Sets: AddCounter -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: AddInstance -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Instance -Specifies the display name of the new performance counter. - -The type must be a valid name of a performance counter instance; for example Total_PerfCounter. - -```yaml -Type: String -Parameter Sets: AddInstance -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: AddMultipleCounters -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AllInstances -Collects all instances of a counter category and type on the target Web front end computer or database server. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Adds the specified performance counter to all database servers in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WebFrontEnd -Adds the specified performance counter to all Web front end computers in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CounterList -{{Fill CounterList Description}} - -```yaml -Type: String[] -Parameter Sets: AddMultipleCounters -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPDistributedCacheServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPDistributedCacheServiceInstance.md deleted file mode 100644 index 1ebfa4ebe7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPDistributedCacheServiceInstance.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spdistributedcacheserviceinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPDistributedCacheServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPDistributedCacheServiceInstance - -## SYNOPSIS - -Adds an instance of the distributed cache service to a local server. - - - -## SYNTAX - -### (Default) -``` -Add-SPDistributedCacheServiceInstance [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### CacheSizeSet -``` -Add-SPDistributedCacheServiceInstance [-AssignmentCollection <SPAssignmentCollection>] [-CacheSizeInMB <Int32>] - [<CommonParameters>] -``` - -### LocalServerRoleSet -``` -Add-SPDistributedCacheServiceInstance [-AssignmentCollection <SPAssignmentCollection>] [-Role <SPServerRole>] - [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [Cmdlet Parameter Sets](https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Add-SPDistributedCacheServiceInstance cmdlet to add an instance of the distributed cache server to a local server. This is required to start the AppFabric service. - - - -## EXAMPLES - -### Example 1 -``` -Add-SPDistributedCacheServiceInstance -``` - -This example adds an instance of the distributed cache service to a local server. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheSizeInMB -Specifies the amount of RAM to allocate for the Distributed Cache service instance. - -If this parameter is not specified, the default value will be used. - -```yaml -Type: Int32 -Parameter Sets: CacheSizeSet -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Role -Specifies the type of server role that the Distributed Cache service instance should be configured for. - -This parameter is typically used when you are going to do a server role conversion to the specified server role. - -The valid values are: - -* SingleServerFarm -* DistributedCache -* WebFrontEndWithDistributedCache - -```yaml -Type: SPServerRole -Parameter Sets: LocalServerRoleSet -Aliases: -Accepted values: DistributedCache, SingleServerFarm, WebFrontEndWithDistributedCache -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Remove-SPDistributedCacheServiceInstance](Remove-SPDistributedCacheServiceInstance.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPEduClassMember.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPEduClassMember.md deleted file mode 100644 index f392d5f0c5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPEduClassMember.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-speduclassmember -applicable: SharePoint Server 2013 -title: Add-SPEduClassMember -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPEduClassMember - -## SYNOPSIS -Not in use - -## SYNTAX - -``` -Add-SPEduClassMember [-AssignmentCollection <SPAssignmentCollection>] -ClassId <String> -Role <String> - -Site <SPSitePipeBind> -UserAlias <String> [<CommonParameters>] -``` - -## DESCRIPTION -Not in use - -## EXAMPLES - -### Example 1 -``` -Not in use -``` - - -## PARAMETERS - -### -AssignmentCollection -Not in use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClassId -Not in use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Role -Not in use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Site -Not in use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -UserAlias -Not in use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPEduUser.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPEduUser.md deleted file mode 100644 index 72dbde8ad0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPEduUser.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-speduuser -applicable: SharePoint Server 2013 -title: Add-SPEduUser -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPEduUser - -## SYNOPSIS -Do not use - -## SYNTAX - -``` -Add-SPEduUser [-AssignmentCollection <SPAssignmentCollection>] [-FirstName <String>] [-LastName <String>] - -Role <String> -Site <SPSitePipeBind> -UserAlias <String> [-UserEmail <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use - -## EXAMPLES - -### Example 1 -``` -Do not use -``` - - - -## PARAMETERS - -### -AssignmentCollection -Do not use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -FirstName -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -LastName -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Role -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Site -Do not use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -UserAlias -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -UserEmail -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPInfoPathUserAgent.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPInfoPathUserAgent.md deleted file mode 100644 index 1cd8709180..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPInfoPathUserAgent.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spinfopathuseragent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPInfoPathUserAgent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPInfoPathUserAgent - -## SYNOPSIS -Adds a user agent to a farm. - -## SYNTAX - -``` -Add-SPInfoPathUserAgent [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPInfoPathUserAgent cmdlet creates a user agent to receive the .xml file that contains the data of the form for indexing. -The user agent receives the InfoPath 2013 files from InfoPath Forms Services in SharePoint Server instead of Web pages in response to an HTTP request. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE----------------- -``` -C:\PS>Add-SPInfoPathUserAgent -Name "NewAgent" -``` - -This example creates a new agent named NewAgent. - -## PARAMETERS - -### -Name -Specifies the name of the user agent to receive InfoPath 2013 files. -These user agents represent search bots that are commonly used in an enterprise environment. -If a different search technology is being used and InfoPath 2013 files are not being indexed, you can add additional search bots for that technology to the collection. - -The type must be a valid file name; for example UserAgentName1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPPluggableSecurityTrimmer.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPPluggableSecurityTrimmer.md deleted file mode 100644 index 9bb81925a9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPPluggableSecurityTrimmer.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-sppluggablesecuritytrimmer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPPluggableSecurityTrimmer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPPluggableSecurityTrimmer - -## SYNOPSIS -Adds a pluggable security trimmer to a Profile service application proxy. - -## SYNTAX - -``` -Add-SPPluggableSecurityTrimmer -UserProfileApplicationProxyId <Guid> -PlugInId <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-QualifiedTypeName <String>] [-WhatIf] - [-CustomProperties <NameValueCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Add-SPPluggableSecurityTrimmer cmdlet to add a specified pluggable security trimmer to a User Profile service application proxy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE 1-------------------- -``` -C:\PS>$proxy = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq 'User Profile Service Application Proxy'} -C:\PS>Add-SPPluggableSecurityTrimmer -UserProfileApplicationProxyId $proxy.Id -PlugInId 0 -``` - -This example adds a pluggable security trimmer that is related to the User Profile service application proxy. - -## PARAMETERS - -### -UserProfileApplicationProxyId -Specifies the ID of the User Profile service application proxy to which you are adding the pluggable security trimmer. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PlugInId -The index of the pluggable security trimmer must have an integer value greater than or equal to zero. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QualifiedTypeName -Specifies the qualified type name of the class that implements the pluggable security trimmer. - -The type must be a valid qualified type name, in the form Microsoft.Office.Server.SocialData.SocialSecurityTrimmer,Microsoft.Office.Server.UserProfiles,Version=14.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomProperties -{{Fill CustomProperties Description}} - -```yaml -Type: NameValueCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPProfileLeader.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPProfileLeader.md deleted file mode 100644 index cba58125fb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPProfileLeader.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spprofileleader -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPProfileLeader -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPProfileLeader - -## SYNOPSIS -Adds a company leader. - -## SYNTAX - -``` -Add-SPProfileLeader [-ProfileServiceApplicationProxy] <SPServiceApplicationProxyPipeBind> - [-Name] <SPProfileLeaderPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server 2010 Service Pack 1 (SP1). - -Use the `Add-SPProfileLeader` cmdlet to add a user as the company leader in the User Profile Service Application. - -For additional information about SPProfileLeader cmdlets, see the \*-SPProfileLeader Windows PowerShell cmdlets in SharePoint Server https://go.microsoft.com/fwlink/p/?LinkId=226295. - -After you use the `Add-SPProfileLeader` cmdlet to add a company leader, you have to complete a full crawl of your content sources for the changes to take effect. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251831. - -## EXAMPLES - -### ---------EXAMPLE------------ -``` -C:\PS>$upaProxy = Get-SPServiceApplicationProxy | where {$_.TypeName -eq 'User Profile Service Application Proxy'} -C:\PS>Add-SPProfileLeader -ProfileServiceApplicationProxy $upaProxy -Name "contoso\janedoe" -``` - -This example adds a company leader named Jane Doe. - -## PARAMETERS - -### -ProfileServiceApplicationProxy -Specifies the name of the User Profile Service Application Proxy to use. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the account name to be added as a leader for the new User Profile Service application. -For example, contoso\janedoe. - -```yaml -Type: SPProfileLeaderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPProfileSyncConnection.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPProfileSyncConnection.md deleted file mode 100644 index 3d6a3c4806..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPProfileSyncConnection.md +++ /dev/null @@ -1,368 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spprofilesyncconnection -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPProfileSyncConnection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPProfileSyncConnection - -## SYNOPSIS -Adds a synchronization connection. - -## SYNTAX - -``` -Add-SPProfileSyncConnection [-ProfileServiceApplication] <SPServiceApplicationPipeBind> - -ConnectionDomain <String> -ConnectionForestName <String> -ConnectionPassword <SecureString> - -ConnectionSynchronizationOU <String> -ConnectionUserName <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-ConnectionClaimIDMapAttribute <String>] - [-ConnectionClaimProviderIdValue <String>] [-ConnectionClaimProviderTypeValue <String>] - [-ConnectionNamingContext <String>] [-ConnectionPort <Int32>] [-ConnectionServerName <String>] - [-ConnectionUseSSL <Boolean>] [-WhatIf] [-ConnectionFilterOutUnlicensed <Boolean>] - [-ConnectionUseDisabledFilter <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Use the Add-SPProfileSyncConnection cmdlet to add a User Profile synchronization connection. - -For additional information about profile synchronization connections, see - -This cmdlet only works with Active Directory Synchronization Connections - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE----------- -``` -Add-SPProfileSyncConnection -ProfileServiceApplication 888ds256-9ad9-53a9-f135-99eecd245670b -ConnectionForestName "fabrikam.com"-ConnectionDomain "Fabrikam" -ConnectionUserName "Testupa" -ConnectionPassword convertto-securestring "Password1" -asplaintext -force -ConnectionSynchronizationOU "OU=SharePoint Users,DC=fabrikam,DC=com" -``` - -This example adds a user from the fabrikam domain using a specific user profile service application. - -## PARAMETERS - -### -ProfileServiceApplication -Specifies the name of the User Profile service application. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ConnectionDomain -Specifies the NetBIOS name of the domain you are connecting to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionForestName -Specifies the fully qualified domain name (FQDN) of the forest you are connecting to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionPassword -Specifies the password of the account used for directory connection. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionSynchronizationOU -Specifies the top level organizational unit (OU) that you would like to synchronize. -The value must be a domain name and you can only include one container per command. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionUserName -Specifies the user name to be used for the synchronization connection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionClaimIDMapAttribute -Specifies the Claims ID used by the Claim Provider, that is, samAccountName. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionClaimProviderIdValue -Specifies the Claims Provider ID or Name for an authentication type while a Web App is configured. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionClaimProviderTypeValue -Specifies the Authentication claim Provider that will be used to encode the User Profile accounts names. -For example, Windows/Forms etc. -This means if a user logs in using the given Authentication Type, then a profile can be found by looking up a claim encoded credentials. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionNamingContext -Specifies the naming context of the directory information tree to connect to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionPort -Specifies the port to be used to connect to the directory service. -The default port is 389. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionServerName -Specifies the name of the domain controller to connect to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionUseSSL -Specifies if the connection to the directory service must be over SSL. - -The valid values are: $True or $False - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionFilterOutUnlicensed -Do not use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionUseDisabledFilter -Filters out disabled accounts. - ->[!NOTE] -This will only filter out accounts which are in a disabled state prior to being imported. It will not filter out accounts which have been disabled after importing. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingMachineInfo.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingMachineInfo.md deleted file mode 100644 index 711dfe50ff..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingMachineInfo.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-sproutingmachineinfo -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPRoutingMachineInfo -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPRoutingMachineInfo - -## SYNOPSIS - -Adds a new routing target to the farm. - - - -## SYNTAX - -``` -Add-SPRoutingMachineInfo [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> [-Name] <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Availability <SPRoutingMachineAvailability>] - [-OutgoingPort <Int32>] [-OutgoingScheme <SPRoutingOutgoingScheme>] [-StaticWeight <Double>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Add-SPRoutingMachineInfo cmdlet to add a new routing target to the farm by using the RequestManagementSettings and Name parameters. - -## EXAMPLES - -### -------------EXAMPLE-------------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -C:\PS>Add-SPRoutingMachineInfo -RequestManagementSettings $rm -Name <MachineName> -Availability Available - -C:\PS> -``` - -This example adds a routing target for a specified identity to the farm. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to add to the routing target. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the computer to add to the route. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Availability -Specifies whether or not the added computer will be available for routing. - -The valid values are: - ---Available ---Unavailable - -```yaml -Type: SPRoutingMachineAvailability -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutgoingPort -Specifies the port used by Request Manager to make an outgoing connection. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutgoingScheme -Determines the Http scheme of outgoing connections. - -The valid values are: - ---SameAsIncoming ---Http ---Https - -```yaml -Type: SPRoutingOutgoingScheme -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StaticWeight -Specifies the static weight of a computer routing that is used by Request Manager. -If the static weight is higher, more requests will be routed to the computer. - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPRoutingMachineInfo](Get-SPRoutingMachineInfo.md) - -[Remove-SPRoutingMachineInfo](Remove-SPRoutingMachineInfo.md) - -[Set-SPRoutingMachineInfo](Set-SPRoutingMachineInfo.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingMachinePool.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingMachinePool.md deleted file mode 100644 index a990271595..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingMachinePool.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-sproutingmachinepool -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPRoutingMachinePool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPRoutingMachinePool - -## SYNOPSIS - -Adds a new machine pool. - - - -## SYNTAX - -``` -Add-SPRoutingMachinePool [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> [-Name] <String> - [-AssignmentCollection <SPAssignmentCollection>] [-MachineTargets <SPRoutingRuleTargetPipeBind[]>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Add-SPRoutingMachinePool cmdlet to add a machine pool by using the RequestManagementSettings and Name parameters. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE-------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -C:\PS>Add-SPRoutingMachinePool -RequestManagementSettings $rm -Name <MachineName> -``` - -This example adds a machine pool. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to add to the routing machine pool. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of machine pool. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MachineTargets -Specifies the routing targets collection that the machine pool will contain. - -```yaml -Type: SPRoutingRuleTargetPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPRoutingMachinePool](Get-SPRoutingMachinePool.md) - -[Remove-SPRoutingMachinePool](Remove-SPRoutingMachinePool.md) - -[Set-SPRoutingMachinePool](Set-SPRoutingMachinePool.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingRule.md deleted file mode 100644 index 10c365af7d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPRoutingRule.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-sproutingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPRoutingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPRoutingRule - -## SYNOPSIS - -Adds a routing rule. - - - -## SYNTAX - -``` -Add-SPRoutingRule [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> [-Name] <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Criteria <SPRequestManagementRuleCriteriaPipeBind[]>] - [-ExecutionGroup <Int32>] [-Expiration <DateTime>] [-MachinePool <SPRoutingMachinePoolPipeBind>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPRoutingRule cmdlet adds a routing rule for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE-------- -``` -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -C:\PS>Get-SPRoutingRule -RequestManagementSettings $rm - -C:\PS>$machines=Get-SPRoutingMachineInfo -RequestManagementSettings $rm - -C:\PS>Add-SPRoutingMachinePool -RequestManagementSettings $rm -Name <Name of Pool> -MachineTargets $machines -``` - -This examples adds a routing rule to the farm by using the $rm and $machines variables. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to add to the routing rule. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Criteria -Specifies the criteria for the rule to match. - -```yaml -Type: SPRequestManagementRuleCriteriaPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExecutionGroup -Specifies the group in which the rule will be placed. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expiration -Specifies the expiration date and time of the rule. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MachinePool -Specifies the pool of machines to which a request will be routed if the created rule is matched. - -```yaml -Type: SPRoutingMachinePoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPRoutingRule](Get-SPRoutingRule.md) - -[Remove-SPRoutingRule](Remove-SPRoutingRule.md) - -[Set-SPRoutingRule](Set-SPRoutingRule.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPScaleOutDatabase.md deleted file mode 100644 index d6e7d29db5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPScaleOutDatabase.md +++ /dev/null @@ -1,217 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPScaleOutDatabase - -## SYNOPSIS - -Adds an existing scale-out database to the specified service application. - - - -## SYNTAX - -``` -Add-SPScaleOutDatabase -DatabaseName <String> -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseCredentials <PSCredential>] - [-DatabaseFailoverServer <String>] [-DatabaseServer <String>] [-WhatIf] [-DeferUpgradeActions] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Add-SPScaleOutDatabase cmdlet to add an existing scale-out database to the specified service application by using the ServiceApplication parameter or creates a new scale-out database and adds it to the specified service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE------------ -``` -C:\PS>$serviceApplication = Get-SPServiceApplication -Name "AppManagement" - -C:\PS>Add-SPScaleOutDatabase -ServiceApplication $serviceApplication -``` - -This example adds a new or existing scale out database into a specific service application. - -## PARAMETERS - -### -DatabaseName -Specifies the name of the database to add to the specified service application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the service application of the scale-out databases. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the owner's credentials of the scale-out database to be added to the service application. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseFailoverServer -The name of the failover server for the scale-out database to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -The name of the server hosting the scale-out database to be added. -If a value is not provided, the default database server will be used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -{{Fill DeferUpgradeActions Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPScaleOutDatabase](Get-SPScaleOutDatabase.md) - -[Remove-SPScaleOutDatabase](Remove-SPScaleOutDatabase.md) - -[Split-SPScaleOutDatabase](Split-SPScaleOutDatabase.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSecureStoreSystemAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSecureStoreSystemAccount.md deleted file mode 100644 index 4339382c31..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSecureStoreSystemAccount.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spsecurestoresystemaccount -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPSecureStoreSystemAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPSecureStoreSystemAccount - -## SYNOPSIS -Adds an account to a designated list. - -## SYNTAX - -``` -Add-SPSecureStoreSystemAccount [-AccountName] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Add-SPSecureStoreSystemAccount cmdlet to add a user to a list that of accounts which will be considered a system account. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE---------- -``` -C:\PS>Add-SPSecureStoreSystemAccount -AccountName contoso\jdoe -``` - -This example adds the account name jdoe. - -## PARAMETERS - -### -AccountName -Specifies the account name to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPSecureStoreSystemAccount](Get-SPSecureStoreSystemAccount.md) - -[Remove-SPSecureStoreSystemAccount](Remove-SPSecureStoreSystemAccount.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPServerScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPServerScaleOutDatabase.md deleted file mode 100644 index a18f1e779e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPServerScaleOutDatabase.md +++ /dev/null @@ -1,227 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spserverscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPServerScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPServerScaleOutDatabase - -## SYNOPSIS - -Adds an existing scale-out content database to the specified service application. - - -## SYNTAX - -``` -Add-SPServerScaleOutDatabase -DatabaseName <String> -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseCredentials <PSCredential>] - [-DatabaseFailoverServer <String>] [-DatabaseServer <String>] [-WhatIf] [-DeferUpgradeActions] - [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Add-SPServerScaleOutDatabase cmdlet to add an existing scale-out database to the specified service application by using the ServiceApplication parameter or creates a new scale-out database and adds it to the specified service application. - -## EXAMPLES - -### -------------EXAMPLE------------ -``` -$serviceApplication = Get-SPServiceApplication -Name "AppManagement" -Add-SPServerScaleOutDatabase -ServiceApplication $serviceApplication -``` - -This example adds a new or existing scale out database into a specific service application. - - -## PARAMETERS - -### -DatabaseName - -Specifies the name of the database to add to the specified service application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication - -Specifies the service application of the scale-out databases. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials - -Specifies the owner's credentials of the scale-out database to be added to the service application. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseFailoverServer - -The name of the failover server for the scale-out database to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer - -The name of the server hosting the scale-out database to be added. -If a value is not provided, the default database server will be used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies whether upgrade actions are deferred duringi an Upgrade process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPServerScaleOutDatabase](Get-SPServerScaleOutDatabase.md) - -[Remove-SPServerScaleOutDatabase](Remove-SPServerScaleOutDatabase.md) - -[Split-SPServerScaleOutDatabase](Split-SPServerScaleOutDatabase.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPServiceApplicationProxyGroupMember.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPServiceApplicationProxyGroupMember.md deleted file mode 100644 index 0d7e2aa304..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPServiceApplicationProxyGroupMember.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spserviceapplicationproxygroupmember -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPServiceApplicationProxyGroupMember -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPServiceApplicationProxyGroupMember - -## SYNOPSIS - -Adds a member to the service application proxy group. - - - -## SYNTAX - -``` -Add-SPServiceApplicationProxyGroupMember [-Identity] <SPServiceApplicationProxyGroupPipeBind> - [-Member] <SPServiceApplicationProxyPipeBind[]> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPServiceApplicationProxyGroupMember cmdlet adds a member to the service application proxy group. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -match 'User Profile Service Application Proxy'} -Add-SPServiceApplicationProxyGroupMember RemoteProxyGroup -Member $proxy -``` - -This example adds a select service application proxy to the service application proxy group named RemoteProxyGroup. - -The service application proxy group GUID is unique to every farm. -You can run Get-SPServiceApplicationProxyGroup | Select Name,Id to see the GUID of the serviceapplication proxy groups. -Use this result for any other SPServiceApplicationProxyGroup cmdlets. - -## PARAMETERS - -### -Identity -Specifies the service application proxy group to which to add the member. - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Member -Specifies an array of members to add to the service application proxy group. - -```yaml -Type: SPServiceApplicationProxyPipeBind[] -Parameter Sets: (All) -Aliases: Proxy -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPShellAdmin.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPShellAdmin.md deleted file mode 100644 index 316d122757..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPShellAdmin.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spshelladmin -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPShellAdmin -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPShellAdmin - -## SYNOPSIS - -Adds a user to the SharePoint_Shell_Access role for the specified database. - - - -## SYNTAX - -``` -Add-SPShellAdmin [-UserName] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-database <SPDatabasePipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -When you run this cmdlet to add a user to the SharePoint_Shell_Access role, you must have membership in the securityadmin fixed server role on the SQL Server instance, membership in the db_owner fixed database role on all affected databases, and local administrative permission on the local computer. - -This cmdlet is intended only to be used with a database that uses Windows authentication. -There is no need to use this cmdlet for databases that use SQL authentication; in fact, doing so may result in an error message. - -Use the Add-SPShellAdmin cmdlet to add a user to the SharePoint_Shell_Access role as follows: - ---If you specify only the user, the user is added to the role for the farm configuration database. - ---If you use the database parameter, the user is added to the role on the farm configuration database, the Central Administration content database, and the specified database. Using the database parameter is the preferred method because most of the administrative operations require access to the Central Administration content database. - -The user is added to the WSS_Admin_WPG group on all Web servers when the user is added to the SharePoint_Shell_Access role. -If the target database does not have a SharePoint_Shell_Access role, the role is automatically created. - -In order to use Windows PowerShell for SharePoint Products, a user must be a member of the SharePoint_Shell_Access role on the configuration database and a member of the WSS_ADMIN_WPG local group on the computer where SharePoint Products is installed. - -However, the result of running this cmdlet is that the user specified with the UserName parameter will have the **SPDataAccess** role, if it exists, or db_owner role, if the SPDataAccess role does not exist, on the affected databases as described above. Therefore, you should carefully plan which users are given this access. - -Therefore, you should carefully plan which users are given this access. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - -## EXAMPLES - -### -------------------EXAMPLE 1------------------------- -``` -Add-SPShellAdmin -UserName CONTOSO\User1 -``` - -This example adds a new user named User1 to the SharePoint_Shell_Access role in the farm configuration database only, and also ensures the user is added to the WSS_Admin_WPG local group on each server in the farm. - -### -------------------EXAMPLE 2------------------------- -``` -Add-SPShellAdmin -UserName CONTOSO\User1 -database 4251d855-3c15-4501-8dd1-98f960359fa6 -``` - -This example adds a new user named User1 to the SharePoint_Shell_Access role in both the specified content database and the configuration database by passing a database GUID to the cmdlet. - -### -------------------EXAMPLE 3------------------------- -``` -Get-SPDatabase | Where-Object {$_.WebApplication -like "SPAdministrationWebApplication"} | Add-SPShellAdmin CONTOSO\User1 -``` - -This example adds a new user named User1 to the SharePoint_Shell_Access role in both the specified Central Administration content database and the configuration database. - -### -------------------EXAMPLE 4------------------------- -``` -Get-SPDatabase | ?{$_.Name -eq "WSS_Content"} | Add-SPShellAdmin -Username CONTOSO\User1 -``` - -This example adds a new user named User1 to the SharePoint_Shell_Access role of both the specified content database and the configuration database by passing the name of the database to the cmdlet. - -## PARAMETERS - -### -UserName -Specifies the name of the user to add to the SharePoint_Shell_Access role in the target database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -database -Specifies the GUID of the database or the Database object that includes the SharePoint_Shell_Access role to which you want to add the user. -If the database parameter is not specified, the configuration database is used. -The farm configuration database is always included, even if you specify another database. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSiteSubscriptionFeaturePackMember.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSiteSubscriptionFeaturePackMember.md deleted file mode 100644 index 56af3fa21f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSiteSubscriptionFeaturePackMember.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spsitesubscriptionfeaturepackmember -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPSiteSubscriptionFeaturePackMember -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPSiteSubscriptionFeaturePackMember - -## SYNOPSIS - -Adds a feature to a SharePoint Feature set. - - - -## SYNTAX - -``` -Add-SPSiteSubscriptionFeaturePackMember [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> - -FeatureDefinition <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPSiteSubscriptionFeaturePackMember cmdlet adds features to the provided SharePoint Feature set. -Feature sets are an Allow List of SharePoint Features that can be associated with any site subscription. -If a Feature set is assigned to a site subscription, only the SPFeatures object in that Feature set are available for use on the site collections and Web sites that are members of the site subscription. -Feature sets contain a list of the GUIDs of each Feature that are on the Allow List for associated site subscriptions. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE---------------- -``` -$fp = New-SPSiteSubscriptionFeaturePack -Get-SPFeature -limit all | Where{ $_.Scope -eq "WEB" } | Add-SPSiteSubscriptionFeaturePackMember -id $fp -$fp = Get-SPSiteSubscriptionFeaturePack $fp -``` - -This example creates a Feature set and adds all Web site scoped Features to the set. - -The Feature set is refreshed in the last line so that the local object has the correct values. - -## PARAMETERS - -### -Identity -Specifies the Feature set object or GUID to which the given SharePoint Feature is added. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a Feature set (for example, FeatureSet1); or an instance of a valid SPFeatureSet object. - -```yaml -Type: SPSiteSubscriptionFeaturePackPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -FeatureDefinition -Specifies the Feature definition, name, or GUID to add to the Feature set. - -```yaml -Type: SPFeatureDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSiteSubscriptionProfileConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSiteSubscriptionProfileConfig.md deleted file mode 100644 index f21792aa57..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSiteSubscriptionProfileConfig.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spsitesubscriptionprofileconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPSiteSubscriptionProfileConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPSiteSubscriptionProfileConfig - -## SYNOPSIS -Adds a new site subscription to a User Profile Service application. - -## SYNTAX - -### Default -``` -Add-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-MySiteHostLocation <SPSitePipeBind>] -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SynchronizationOU <String>] [-WhatIf] - [<CommonParameters>] -``` - -### MySiteSettings -``` -Add-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> - -MySiteHostLocation <SPSitePipeBind> -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-MySiteManagedPath <SPPrefixPipeBind>] - [-SiteNamingConflictResolution <String>] [-SynchronizationOU <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Add-SPSiteSubscriptionProfileConfig cmdlet adds a new site subscription to a User Profile Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE------------------ -``` -$sub = Get-SPSiteSubscription https://contoso/my -$proxy = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq 'User Profile Service Application Proxy'} -Add-SPSiteSubscriptionProfileConfig -Identity $sub -ProfileServiceApplicationProxy $proxy -MySiteHostLocation https://contoso/my -$sub = New-SPSiteSubscription -``` - -This example creates a new User Profile Service application tenant. - -## PARAMETERS - -### -Identity -Specifies the proxy of the User Profile Service application to add the site subscription to. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a User Profile Service application proxy (for example, UserProfileSvcProxy1); or an instance of a valid SPServiceApplicationProxy object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MySiteHostLocation -Specifies the site collection where the My Site host for the site subscription is provisioned. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -```yaml -Type: SPSitePipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the identifier for the User Profile Service Application proxy where the tenant is to be created. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MySiteManagedPath -Specifies the managed path where personal sites will be created. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: SPPrefixPipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteNamingConflictResolution -Specifies the format to use to name personal sites. - -Use one of the following integer values: - -1 Personal site collections are to be named based on user names without any conflict resolution. -For example, https://portal_site/location/username/ - -2 Personal site collections are to be based on user names with conflict resolution by using domain names. -For example, .../username/ or .../domain_username/ - -3 Personal site collections are to be named by using domain and user name always, to avoid any conflicts. -For example, https://portal_site/location/domain_username/ - -The default value is 1 (do not resolve conflicts). - -```yaml -Type: String -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SynchronizationOU -Specifies the organizational unit serving the site subscription. - -The type must be a valid name of an organizational unit; for example, OrgUnit1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSolution.md deleted file mode 100644 index 7e9b5671e3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPSolution.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spsolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPSolution - -## SYNOPSIS - -Uploads a SharePoint solution package to the farm. - -## SYNTAX - -``` -Add-SPSolution [-LiteralPath] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Language <UInt32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPSolution cmdlet adds a SharePoint solution package to the farm. -This cmdlet does not deploy the uploaded SharePoint solution. -Use the Install-SPSolution cmdlet to deploy the SharePoint solution in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Add-SPSolution -LiteralPath c:\contoso_solution.wsp -``` - -This example adds the SharePoint solution in the file contoso_solution.wsp to the farm. - -## PARAMETERS - -### -LiteralPath -Specifies the path to the solution package. - -The type must be a valid path in either of the following forms: - -- C:\folder_name -- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Specifies the language pack to install with the solution package. - -The type must be a valid language identifier; for example, 1033. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPThrottlingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPThrottlingRule.md deleted file mode 100644 index 63c36c7ec7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPThrottlingRule.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spthrottlingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPThrottlingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPThrottlingRule - -## SYNOPSIS - -Adds a new throttling rule. - - - -## SYNTAX - -``` -Add-SPThrottlingRule [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> [-Name] <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Criteria <SPRequestManagementRuleCriteriaPipeBind[]>] - [-Expiration <DateTime>] [-Threshold <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPThrottlingRule cmdlet adds a new throttling rule for the farm by using the Name and RequestManagementSettings parameters. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE--------- -``` -$web=Get-SPWebApplication -Identity <URL of web application> -$rm=Get-SPRequestManagementSettings -Identity $web -$c=New-SPRequestManagementRuleCriteria -Value http -Property url -MatchType startswith -CaseSensitive $false -Add-SPThrottlingRule -RequestManagementSettings $rm -Name <Rule Name> -Criteria $c -Threshold 4 -``` - -This example adds a throttling rule for a specified identity by using the $rm and $c variables. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to add. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the throttling rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Criteria -Specifies the criteria for the rule to match. - -```yaml -Type: SPRequestManagementRuleCriteriaPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expiration -Specifies the expiration date and time of the rule. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -Specifies a value between 0 and 10 which defines the maximum threshold for throttling. -The Request Manager will remove routing targets if their Health-Score becomes greater than this value. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPThrottlingRule](Get-SPThrottlingRule.md) - -[Remove-SPThrottlingRule](Remove-SPThrottlingRule.md) - -[Set-SPThrottlingRule](Set-SPThrottlingRule.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPUserLicenseMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPUserLicenseMapping.md deleted file mode 100644 index 479b36b6e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPUserLicenseMapping.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spuserlicensemapping -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPUserLicenseMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPUserLicenseMapping - -## SYNOPSIS - -Maps a security group, forms-based role, or claim to a SharePoint user license. - - - -## SYNTAX - -``` -Add-SPUserLicenseMapping - -Mapping <System.Collections.Generic.List`1[Microsoft.SharePoint.PowerShell.SPUserLicenseMapping]> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Add-SPUserLicenseMapping cmdlet maps a claim, Active Directory Domain Services (AD DS) security group, or forms-based role to a SharePoint user license for a farm or web application. -To specify a mapping to a specific web application, use the WebApplication parameter. -If you do not specify parameters, mapping applies to the entire SharePoint farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1------------------- -``` -$a = New-SPUserLicenseMapping -SecurityGroup yoursecuritygroup -License Enterprise -Add-SPUserLicenseMapping -Mapping $a -``` - -This example adds user mappings for the entire farm. - -## PARAMETERS - -### -Mapping -```yaml -Type: List<Microsoft.SharePoint.PowerShell.SPUserLicenseMapping> -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Disable-SPUserLicensing](Disable-SPUserLicensing.md) - -[Enable-SPUserLicensing](Enable-SPUserLicensing.md) - -[Get-SPUserLicenseMapping](Get-SPUserLicenseMapping.md) - -[Remove-SPUserLicenseMapping](Remove-SPUserLicenseMapping.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPUserSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Add-SPUserSolution.md deleted file mode 100644 index b41580c8d7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Add-SPUserSolution.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/add-spusersolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Add-SPUserSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Add-SPUserSolution - -## SYNOPSIS - -Uploads a new sandboxed solution to the solution gallery. - - - -## SYNTAX - -``` -Add-SPUserSolution [-LiteralPath] <String> -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Add-SPUserSolution cmdlet uploads a new sandboxed solution package to the solution gallery. -This cmdlet does not activate the uploaded sandboxed solution; to activate the solution in the site collection, use the Install-SPUserSolution cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE--------------------- -``` -Add-SPUserSolution -LiteralPath c:\contoso_solution.wsp -Site https://sitename -``` - -This example adds the sandboxed solution c:\contoso_solution.wsp to the site https://sitename. - -## PARAMETERS - -### -LiteralPath -Specifies the path to the sandboxed solution package. - -The type must be a valid path in either of the following forms: - -- C:\folder_name -- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Specifies the site collection where the sandboxed solution is to be added. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSiteobject. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPConfigurationDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPConfigurationDatabase.md deleted file mode 100644 index a4bd76080f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPConfigurationDatabase.md +++ /dev/null @@ -1,223 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/backup-spconfigurationdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Backup-SPConfigurationDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Backup-SPConfigurationDatabase - -## SYNOPSIS - -Performs a farm-level configuration-only backup. - - - -## SYNTAX - -### DefaultSet -``` -Backup-SPConfigurationDatabase -Directory <String> [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-Item <String>] - [<CommonParameters>] -``` - -### ShowTree -``` -Backup-SPConfigurationDatabase [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-Item <String>] - [-ShowTree] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Backup-SPConfigurationDatabase cmdlet performs a configuration-only backup of the current farm or a configuration-only backup of a separate configuration database which is not attached to the current farm. -If you wish to perform a configuration-only backup of the current farm, there is no need to specify the DatabaseServer and DatabaseName parameters. -However, using the Backup-SPFarm cmdlet with the ConfigurationOnly parameter is recommended for such a scenario. - -An example of a configuration backup is an administrator creates a farm configuration template which then can be applied to other SharePoint farms by performing a restore using the Restore-SPFarm cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251831. - -## EXAMPLES - -### -------------------EXAMPLE 1-------------------- -``` -Backup-SPConfigurationDatabase -DatabaseName SharePoint_Config -DatabaseServer SqlServer1 -Directory \\server\share\Backup -ShowTree -``` - -This example displays components that are available for inclusion in a configuration-only backup. - -### -------------------EXAMPLE 2-------------------- -``` -Backup-SPConfigurationDatabase -DatabaseName SharePoint_Config -DatabaseServer SqlServer1 -Directory \\server\share\Backup -Verbose -``` - -This example performs a configuration-only backup with verbose output. - -## PARAMETERS - -### -Directory -Specifies the path where SharePoint Products stores the backup package it generates. -If you have a computer on which SQL Server and an instance of SharePoint Products are installed, you can use local drive paths. -This includes a basic installation. -However, if SQL Server and SharePoint Products are installed on multiple computers or if you have multiple servers running SharePoint Products, you must use Universal Naming Convention (UNC) share paths so that the SQL Server database and search components are written to the same location; for example, \\\\computer_name\volume\Backup). - -Multiple backup packages can be stored in the same location. -This is the same path that you pass to the Directory parameter of the Restore-SPFarm cmdlet. - -The type must be either of the valid paths: - -- C:\folder_name -- \\\\server_name\folder_name - -The spbr* folders are automatically created. - -```yaml -Type: String -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the ID and password that corresponds to the administrator user name for the SQL Server database. - -This parameter should only be specified if SQL authentication is used to connect to the database. -If Windows authentication is used to connect to the database, then this parameter should not be specified. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the configuration database name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the SQL database server that contains the configuration database. -The default value is the local computer name. - -The type must be a valid database server; for example, DS. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Item -Indicates the part of the farm to back up. -You may use the full farm path notation as displayed by the ShowTree parameter or the name of the target component in the path if the component has a unique name. -If multiple items match the name, the full path must be provided. -Surround the item or path in quotation marks if it contains a space. - -If the Item parameter is not specified, the entire farm configuration is backed up. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowTree -Displays which objects in the farm will be backed up based on the other parameters passed to the backup cmdlet, namely the Item parameter. -Items that will be excluded from the backup based on the other parameters passed to the Backup-SPConfigurationDatabase cmdlet will be preceded with an asterisk character (*). -Items that cannot be backed up will be enclosed in square brackets (\[ \]). -A backup will not be performed if the ShowTree parameter is present. - -```yaml -Type: SwitchParameter -Parameter Sets: ShowTree -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPEnterpriseSearchServiceApplicationIndex.md b/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPEnterpriseSearchServiceApplicationIndex.md deleted file mode 100644 index c89718e523..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPEnterpriseSearchServiceApplicationIndex.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/backup-spenterprisesearchserviceapplicationindex -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Backup-SPEnterpriseSearchServiceApplicationIndex -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Backup-SPEnterpriseSearchServiceApplicationIndex - -## SYNOPSIS -Takes a backup of the search index to a specified backup location. - -## SYNTAX - -### RunBackup -``` -Backup-SPEnterpriseSearchServiceApplicationIndex [-Phase] <Int32> - [-SearchApplication] <SearchServiceApplication> [-BackupFolder] <String> [-BackupHandleFile] <String> - [[-Retries] <Int32>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [-PeerToPeer] - [-SpecifiedBackupHandle <String>] [<CommonParameters>] -``` - -### AbortBackup -``` -Backup-SPEnterpriseSearchServiceApplicationIndex [-SearchApplication] <SearchServiceApplication> - [-BackupHandleFile] <String> [[-Retries] <Int32>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [-Abort] [-PeerToPeer] [-SpecifiedBackupHandle <String>] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet will take a backup of the search index to a specified backup location. -The cmdlet has to be run in two phases. -Phase one will take a backup of what is present in the index at the time that the backup cmdlet is run. -Phase two will take a differential backup of what was added to the index after you started the first phase index backup. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Backup-SPEnterpriseSearchServiceApplicationIndex -Phase 1 -SearchApplication $ssa -BackupFolder "\\backuphost\backupfolder" -BackupHandleFile "\\backuphost\backupfolder\backuphandle.txt" -Retries 3 -``` - -This example starts a Phase 1 backup of the search index for the default search application, and stores the backup at the location \\\\backuphost\backupfolder. -The cmdlet stores a handle file backuphandle.txt that is used by the second phase cmdlet. - -### ------------------EXAMPLE 2------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Backup-SPEnterpriseSearchServiceApplicationIndex -Phase 1 $ssa -BackupFolder "\\backuphost\backupfolder" -BackupHandleFile "\\backuphost\backupfolder\backuphandle.txt" -Retries 3 -``` - -This example checks the backup status and progress by re-running the cmdlet for Phase 1. - -### ------------------EXAMPLE 3------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Backup-SPEnterpriseSearchServiceApplicationIndex -Phase 2 -SearchApplication $ssa -BackupFolder "\\backuphost\backupfolder" -BackupHandleFile "\\backuphost\backupfolder\backuphandle.txt" -Retries 3 -``` - -This example starts the Phase 2 of the search index backup by using the same backup location and backup handle file as used for Phase 1. -The Search Service Application must be paused before the second phase can be started. - -## PARAMETERS - -### -Phase -Specifies the phase of the backup job. - -```yaml -Type: Int32 -Parameter Sets: RunBackup -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Name of the search service application to be backed up - -```yaml -Type: SearchServiceApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BackupFolder -Full UNC path of the backup files should be written. - -```yaml -Type: String -Parameter Sets: RunBackup -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BackupHandleFile -Specifies a file handle for an ongoing backup job. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Retries -Number of times to retry if temporary failure occurs. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Abort -{{Fill Abort Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: AbortBackup -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PeerToPeer -{{Fill PeerToPeer Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpecifiedBackupHandle -{{Fill SpecifiedBackupHandle Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPFarm.md b/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPFarm.md deleted file mode 100644 index c59f4186a4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPFarm.md +++ /dev/null @@ -1,328 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/backup-spfarm -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Backup-SPFarm -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Backup-SPFarm - -## SYNOPSIS - -Creates a backup of an individual database, Web application, or the entire farm. - - - -## SYNTAX - -### DefaultSet -``` -Backup-SPFarm -BackupMethod <String> -Directory <String> [-AssignmentCollection <SPAssignmentCollection>] - [-BackupThreads <Int32>] [-ConfigurationOnly] [-Force] [-Item <String>] [-Percentage <Int32>] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -### ShowTree -``` -Backup-SPFarm [-ShowTree] [-AssignmentCollection <SPAssignmentCollection>] [-ConfigurationOnly] - [-Item <String>] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Backup-SPFarm cmdlet creates a backup for the entire farm or individual components within the farm. -It can also be used to back up just the configuration settings of a farm to be used as a farm template for other SharePoint farms. -If you want to back up a single site collection, use the Backup-SPSite cmdlet. - -To see the available objects to backup, use the `-ShowTree` parameter set. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Backup-SPFarm -Directory \\file_server\share\Backup -BackupMethod full -ConfigurationOnly -``` - -This example backs up the configuration settings of the farm to the \\\\file_server\share\Backup directory. - -### --------------------EXAMPLE 2--------------------- -``` -Backup-SPFarm -ShowTree -Item "Microsoft SharePoint Foundation Web Application" -Verbose -``` - -This example shows which components of the farm would be backed up under the "Microsoft SharePoint Foundation Web Application" node, but do not actually back them up. - -### --------------------EXAMPLE 3--------------------- -``` -Backup-SPFarm -Directory C:\Backup -BackupMethod full -BackupThreads 10 -Force -``` - -This example performs a backup of a farm using 10 threads and forces the backup to be saved to the C:\Backup directory even though SharePoint estimates that it does not have sufficient space available. - -### --------------------EXAMPLE 4--------------------- -``` -Backup-SPFarm -ShowTree -``` - -This example shows you the available objects to backup with `Backup-SPFarm`. - -## PARAMETERS - -### -BackupMethod -Specifies the type of backup file to be created. - -If a backup is performed with the -ShowTree parameter, then the BackupMethod parameter is not used. - -A full backup is a backup of all the selected data. -A differential backup is a backup of all the selected data that has changed since the last full backup. -If an item does not support differential backup, then a full backup is performed for that item instead. - -The type must be either of the following: - -- Full -- Differential - -```yaml -Type: String -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Directory -Specifies the path where SharePoint Products stores the backup package it generates. -If you have a computer on which SQL Server and an instance of SharePoint Products are installed, you can use local drive paths. -This includes a basic installation. -However, if SQL Server and SharePoint Products are installed on multiple computers or if you have multiple servers running SharePoint Products, you must use Universal Naming Convention (UNC) share paths so that the SQL Server database and search components are written to the same location; for example, \\\\computer_name\volume\Backup). - -Multiple backup packages can be stored in the same location. -This is the same path that you pass to the Directory parameter of the Restore-SPFarm cmdlet. - -The type must be either of the valid paths: - -- C:\folder_name -- \\\\server_name\folder_name - -The spbr* folders are automatically created. - -```yaml -Type: String -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowTree -Displays which objects in the farm will be backed up based on the other parameters passed to the Backup-SPFarm cmdelt, namely the Item parameter. -Items that will be excluded from the backup based on the other parameters passed to the Backup-SPFarm cmdlet will be preceded with an asterisk character (*). -Items that cannot be backed up will be enclosed in square brackets (\[ \]). -A backup will not be performed if the ShowTree parameter is present. - -```yaml -Type: SwitchParameter -Parameter Sets: ShowTree -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BackupThreads -Specifies the number of threads to be used during the backup. -The fewer the threads, the easier the backup log file is to read and understand. -The more the threads, the more components that can be backed up in parallet, potentially resulting in a faster backup operation. -The minimum value is 1 and the maximum value is 10. - -The default value is 3. - -If a backup is performed with the -ShowTree parameter, then the BackupMethod parameter is not used. - -```yaml -Type: Int32 -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConfigurationOnly -If set, the backup will contain configuration settings only (no data) for each of the objects to be backed up. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Specifies to proceed with a backup operation even if the estimation is that the backup directory does not have sufficient space to hold the entire backup. - -If a backup is performed with the ShowTree parameter, then the Force parameter is not used. - -```yaml -Type: SwitchParameter -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Item -Indicates the part of the farm to back up. -You might use the full farm path notation as displayed by the ShowTree parameter or the name of the target component in the path if the component has a unique name. -If multiple items are included in the same match, the full path must be provided. -By default, the top node is selected. -Surround the item or path in quotation marks if it contains a space. -If this parameter is not specified, the entire farm is backed up. - -The type must be a valid item; for example, Farm\Microsoft SharePoint Foundation Web Application\SharePoint - 80. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Percentage -Requests progress updates about the backup operation to be displayed in increments of that percentage; for example, a value of 5 displays backup progress updates at every 5 percent completed, and a value of 10 displays backup progress updates at every 10 percent completed. -To have progress outputs displayed, you must specify the Verbose parameter. - -This percentage is not precise and the actual progress updates might be lower or higher than requested. -Progress updates are always recorded in the backup log file. - -The percentage value is not prcesie and the actual progress updates might be lower or higher than requested. - -The default value is 5. -For a very large database, 1 is the recommended value. - -Valid values are an integer value between 1 and 100. - -```yaml -Type: Int32 -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPSite.md deleted file mode 100644 index 86e54bb278..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Backup-SPSite.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/backup-spsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Backup-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Backup-SPSite - -## SYNOPSIS - -Performs a backup of a site collection. - - - -## SYNTAX - -``` -Backup-SPSite [-Identity] <SPSitePipeBind> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-WhatIf] [-UseABSDocStreamInfo] [<CommonParameters>] -``` - -## DESCRIPTION -The Backup-SPSite cmdlet performs a backup of the site collection when the Identity parameter is used. - -By default, the site collection will be set to read-only for the duration of the backup to reduce the potential for user activity during the backup operation to corrupt the backup. -If you have SQL Server Enterprise Edition, we recommend that UseSqlSnapshot parameter be used because this ensures a valid backup while it allows users to continue reading and writing to the site collection during the backup. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE 1-------------------- -``` -Backup-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak -``` - -This example backs up a site collection at https://server_name/sites/site_name to the C:\Backup\site_name.bak file. - - -### -------------------EXAMPLE 2-------------------- -``` -Get-SPSiteAdministration https://server_name/sites/site_name | Backup-SPSite -Path C:\Backup\site_name.bak -``` - -This example backs up a site collection at https://server_name/sites/site_name to the C:\Backup\site_name.bak file. -Same result as Example 1, but a different way of performing the operation. - -### -------------------EXAMPLE 3-------------------- -``` -Backup-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak -UseSqlSnapshot -``` - -This example backs up a site collection using database snapshots to ensure backup integrity. - -### -------------------EXAMPLE 4-------------------- -``` -Backup-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak -NoSiteLock -``` - -This example backs up a site collection and prevents placing the site into a read only mode during the backup phase. Use the -NoSiteLock parameter when backing up a site in production where it is desirable to not place the site into a read only mode while the backup takes place. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site collection to be backed up. - -For example, a valid URL, such as https://server_name/sites/site_name or a GUID such as, "01234567-89ab-cdef-0123-456789abcdef" - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the full path to the backup file (that is, C:\Backup\site_name.bak. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Specify to overwrite an existing backup file if it already exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoSiteLock -Specifies the site collection to remain read and write during the backup. - -If the NoSiteLock parameter is not specified, then a site collection that has a site collection lock setting of "none" or "no additions" will be temporarily set to "read only" while the site collection backup is performed. -Once the backup has completed, the site collection lock will return to its original state. -The backup package will record the original site collection lock state so that it is restored to that state. - -If users are writing to the site collection while the site collection is being backed up, then the NoSiteLock parameter is not recommended for potential impact to backup integrity - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseSqlSnapshot -Specifies a SQL Database Snapshot will be created when the backup begins, and all site collection data will be retrieved directly from the database snapshot. -This snapshot will be deleted automatically when the backup completes - -The UseSqlSnapshot parameter is recommended if the database server hosting your content database supports database snapshots such as SQL Server Enterprise Edition and SQL Server Developer Edition. -This is because it will ensure a valid backup while allowing users to continue reading and writing to the site collection during the backup. -It is not necessary to specify the NoSiteLock parameter when specifying the UseSqlSnapshot parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseABSDocStreamInfo -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-FASTSearchContentCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-FASTSearchContentCollection.md deleted file mode 100644 index 0fbc494d11..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-FASTSearchContentCollection.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-fastsearchcontentcollection -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Clear-FASTSearchContentCollection ---- - -# Clear-FASTSearchContentCollection - -## SYNOPSIS -Clears the content of a Microsoft FAST Search Server 2010 for SharePoint content collection. - -## SYNTAX - -``` -Clear-FASTSearchContentCollection [-Name] <String> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes from the index all items that are associated with the specified collection without removing the collection. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>Clear-FASTSearchContentCollection -Name newscollection -``` - -This example clears the content of the "newscollection" content collection. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>Clear-FASTSearchContentCollection -Name newscollection -Force -``` - -This example clears the content of the "newscollection" content collection. -The user does not have to confirm the operation. - -## PARAMETERS - -### -Name -The name of the content collection to clear. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. - -If Confirm is false (-Confirm:$false), you will not be prompted. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is equal to or greater than the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings so the user is not asked to confirm the operation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchContentCollection](New-FASTSearchContentCollection.md) - -[Remove-FASTSearchContentCollection](Remove-FASTSearchContentCollection.md) - -[Get-FASTSearchContentCollection](Get-FASTSearchContentCollection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPAppDeniedEndpointList.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPAppDeniedEndpointList.md deleted file mode 100644 index 67f9c78a06..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPAppDeniedEndpointList.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spappdeniedendpointlist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPAppDeniedEndpointList -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPAppDeniedEndpointList - -## SYNOPSIS - -Remove all app-denied endpoints in the farm. - -## SYNTAX - -``` -Clear-SPAppDeniedEndpointList [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Clear-SPAppDeniedEndpoint cmdlet to remove all app-denied endpoints in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ------------EXAMPLE--------- -``` -Clear-SPAppDeniedEndpoint -``` - -This example removes all app-denied endpoints from the farm. - - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPAppDeniedEndpointList](Get-SPAppDeniedEndpointList.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPBusinessDataCatalogEntityNotificationWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPBusinessDataCatalogEntityNotificationWeb.md deleted file mode 100644 index e361de7043..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPBusinessDataCatalogEntityNotificationWeb.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spbusinessdatacatalogentitynotificationweb -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPBusinessDataCatalogEntityNotificationWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPBusinessDataCatalogEntityNotificationWeb - -## SYNOPSIS - -Clears the entity notification site. - - - -## SYNTAX - -``` -Clear-SPBusinessDataCatalogEntityNotificationWeb -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Clear-SPBusinessDataCatalogEntityNotificationWeb cmdlet to clear the entity notification site for the given service context. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE----------- -``` -Clear-SPBusinessDataCatalogEntityNotificationWeb -ServiceContext "http://contoso/" -``` - -This example clears the entity notification site for the service context corresponding to the site http://contoso. - -## PARAMETERS - -### -ServiceContext -Specifies the dervice context for which the entity notification web has to be cleared. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPBusinessDataCatalogEntityNotificationWeb](Get-SPBusinessDataCatalogEntityNotificationWeb.md) - -[Set-SPBusinessDataCatalogEntityNotificationWeb](Set-SPBusinessDataCatalogEntityNotificationWeb.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPContentDatabaseSyncData.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPContentDatabaseSyncData.md deleted file mode 100644 index aa27d80ca1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPContentDatabaseSyncData.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spcontentdatabasesyncdata -applicable: SharePoint Server 2019 -title: Clear-SPContentDatabaseSyncData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPContentDatabaseSyncData - -## SYNOPSIS -Clears synchronization information from the content databases that have not been synchronized since the mentioned number of days. - -## SYNTAX - -``` -Clear-SPContentDatabaseSyncData [-DaysSinceLastProfileSync] <Int32>] - [-AssignmentCollection <SPAssignmentCollection>] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Use the **Clear-SPContentDatabaseSyncData** to clear synchronization information from the content databases that has not been synchronized since the mentioned number of days, which can be passed as a parameter. - -## EXAMPLES - -### EXAMPLE 1 -```powershell - Clear-SPContentDatabaseSyncData -DaysSinceLastProfileSync 12 -``` - -This example resets synchronization information from the content databases that have not been synchronized for more than or equal to 12 days, without prompting for user confirmation. - -## PARAMETERS - -### -DaysSinceLastProfileSync -Specifies the least number of days by which the databases are old. - -The default value of this parameter is 0. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2019 -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - - - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPDistributedCacheItem.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPDistributedCacheItem.md deleted file mode 100644 index 91c92bde2b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPDistributedCacheItem.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spdistributedcacheitem -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPDistributedCacheItem -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPDistributedCacheItem - -## SYNOPSIS - -Clears cached items from the distributed cache server. - - - -## SYNTAX - -``` -Clear-SPDistributedCacheItem [-ContainerType] <SPDistributedCacheContainerType> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Clear-SPDistributedCacheItems cmdlet to clear cached items from the distributed cache server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE------ -``` -Clear-SPDistributedCacheItem -ContainerType DistributedLogonTokenCache -``` - -This example removes all the cache items for distributed token cache. - -## PARAMETERS - -### -ContainerType - -Specifies the container type to clear. - -The valid values for SharePoint Server 2013 and SharePoint Server 2016 are the following: - -DistributedDefaultCache, DistributedAccessCache, DistributedActivityFeedCache, DistributedBouncerCache, DistributedLogonTokenCache, DistributedServerToAppServerAccessTokenCache, DistributedSearchCache, DistributedSecurityTrimmingCache, DistributedActivityFeedLMTCache, DistributedViewStateCache - -Additional valid values for SharePoint Server 2016 are the following: - -DistributedSharedWithUserCache, DistributedUnifiedGroupsCache, DistributedFileLockThrottlerCache, -DistributedResourceTallyCache, DistributedHealthScoreCache, DistributedClientSideAppUpdateTimeCache - - -```yaml -Type: SPDistributedCacheContainerType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPLogLevel.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPLogLevel.md deleted file mode 100644 index b2cb74d1e9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPLogLevel.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-sploglevel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPLogLevel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPLogLevel - -## SYNOPSIS - -Resets the Windows event logging and trace logging to their default values. - - - -## SYNTAX - -``` -Clear-SPLogLevel [-AssignmentCollection <SPAssignmentCollection>] [-Identity <String[]>] - [-InputObject <PSObject>] [<CommonParameters>] -``` - -## DESCRIPTION -The Clear-SPLogLevel cmdlet resets the Windows event logging and trace logging levels for the specified categories to the default values. -If the Identity parameter is not provided, all categories are affected. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Clear-SPLogLevel -Identity Cat1 -``` - -This example resets the log levels for a single category. - -### --------------EXAMPLE 2----------------- -``` -"Cat1", "Cat2", "Cat3" | Clear-SPLogLevel -``` - -This example resets the log levels for multiple categories. - -### --------------EXAMPLE 3----------------- -``` -Get-SPLogLevel | Clear-SPLogLevel -``` - -This example resets the log levels for all categories. - -### --------------EXAMPLE 4----------------- -``` -Clear-SPLogLevel -Identity "SharePoint Server:Database" -``` - -This example resets the log level for the specific category in the SharePoint Server area only. This is useful when more than one area uses the same named category. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the name(s) of the category or set of categories to set the throttle for; for example, "Unified Logging Service". -If the Identity parameter is not specified, the event throttling setting is applied to all categories in the farm. - -Providing an invalid category is a non-terminating error and will be ignored. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InputObject -Specifies the result of the InputObject parameter to be piped. -The value can be a string in a format identical to the Identity parameter, or can be an SPDiagnosticsCategory object. -The user can retrieve one or more categories from the Get-SPLogLevel cmdlet, modify their values, and then pipe the results to the Set-SPLogLevel cmdlet. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPMetadataWebServicePartitionData.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPMetadataWebServicePartitionData.md deleted file mode 100644 index 8b4cbd5502..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPMetadataWebServicePartitionData.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spmetadatawebservicepartitiondata -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPMetadataWebServicePartitionData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPMetadataWebServicePartitionData - -## SYNOPSIS -Removes all data for a site subscription on a metadata Web service application. - -## SYNTAX - -### Default -``` -Clear-SPMetadataWebServicePartitionData [-Identity] <SPSiteSubscriptionPipeBind> - [-ServiceProxy] <SPMetadataServiceProxyCmdletPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-FromContentDatabase <SPContentDatabasePipeBind>] [-FromServiceDatabase] [<CommonParameters>] -``` - -### ServiceContext -``` -Clear-SPMetadataWebServicePartitionData [-ServiceProxy] <SPMetadataServiceProxyCmdletPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] -ServiceContext <SPServiceContextPipeBind> - [-FromContentDatabase <SPContentDatabasePipeBind>] [-FromServiceDatabase] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Clear-SPMetadataWebServicePartitionData cmdlet to clear all data for a site subscription on a metadata Web service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE--------------- -``` -Clear-SPMetadataWebServicePartitionData -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -``` - -This example removes data for a site subscription on a Metadata Service application. - -## PARAMETERS - -### -Identity -Specifies the site subscription configuration to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscriptionConfig1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceProxy -Specifies the service proxy for the service application that contains the site subscription. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of the service application proxy (for example, ServiceAppProxy1); or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceContext -{{Fill ServiceContext Description}} - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: ServiceContext -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -FromContentDatabase -{{Fill FromContentDatabase Description}} - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FromServiceDatabase -{{Fill FromServiceDatabase Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPPerformancePointServiceApplicationTrustedLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPPerformancePointServiceApplicationTrustedLocation.md deleted file mode 100644 index c6dbd10f20..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPPerformancePointServiceApplicationTrustedLocation.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spperformancepointserviceapplicationtrustedlocation -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPPerformancePointServiceApplicationTrustedLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPPerformancePointServiceApplicationTrustedLocation - -## SYNOPSIS -Clears all the trusted locations for a PerformancePoint Service application identity. - -## SYNTAX - -``` -Clear-SPPerformancePointServiceApplicationTrustedLocation - -ServiceApplication <SPPerformancePointMonitoringServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-TrustedLocationType <TrustedFileType>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Clear-SPPerformancePointServiceApplicationTrustedLocation cmdlet removes all the trusted locations for a PerformancePoint Service application. -Use the TrustedLocationType parameter to remove only the trusted locations for a trusted location type. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Clear-SPPerformancePointServiceApplicationTrustedLocation -ServiceApplication My_Service_Application -``` - -This example removes trusted locations from the Service application named, My_Service_Application. - -## PARAMETERS - -### -ServiceApplication -Specifies the PerformancePoint Service application that contains the trusted locations. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointMonitoringServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedLocationType -Specifies the type of trusted locations to clear. -If the TrustedLocationType parameter is not specified, this cmdlet clears all the trusted locations for the specified PerformancePoint Service application. - -The type must be one of the following: content, data source. - -```yaml -Type: TrustedFileType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseDeletedDataSubRange.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseDeletedDataSubRange.md deleted file mode 100644 index 55e8e33783..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseDeletedDataSubRange.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spscaleoutdatabasedeleteddatasubrange -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPScaleOutDatabaseDeletedDataSubRange -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPScaleOutDatabaseDeletedDataSubRange - -## SYNOPSIS - -Clears all partitions inside the specified deleted subrange. - - - -## SYNTAX - -``` -Clear-SPScaleOutDatabaseDeletedDataSubRange -Database <SPDatabasePipeBind> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Clear-SPScaleOutDatabaseDeletedDataSubRange cmdlet to clear all partitions inside the specified deleted subrange that are contained within a specified scale-out database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE-------------- -``` -$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -$state = Get-SPScaleOutDatabaseDataState -Database $database -Set-SPScaleOutDatabaseDataSubRange -Database $database -Range $state.Range -SubRangePoint $state.Range.RangeEnd -SubRangeMode Deleted -IsUpperSubRange $false -$state = Get-SPScaleOutDatabaseDataState -Database $database -Clear-SPScaleOutDatabaseDeletedDataSubRange -Database $database -Range $state.Range -IsUpperSubRange $false -``` - -This example creates a deleted subrange that starts from the data range start point and ends at the data range end point on the first scale-out database of the specified service application. -The example then clears that subrange and all data in the partitions in the subrange. - -## PARAMETERS - -### -Database -Specifies the scale-out database to clear the deleted subrange from. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsUpperSubRange -Specifies whether the subrange with deleted mode is on the upper or lower side of the data range. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Range -Specifies the expected data range of the scale-out database. - -```yaml -Type: SPScaleOutDataRange -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPScaleOutDatabaseDataSubRange](Set-SPScaleOutDatabaseDataSubRange.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseLog.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseLog.md deleted file mode 100644 index f5993ce0c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseLog.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spscaleoutdatabaselog -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPScaleOutDatabaseLog -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPScaleOutDatabaseLog - -## SYNOPSIS - -Clears all scale-out logs. - -## SYNTAX - -``` -Clear-SPScaleOutDatabaseLog -Database <SPDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-LogEntryTimeout <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Clear-SPScaleOutDatabaseLog cmdlet clears all scale-out logs in the specified scale-out database unless there is a scale-out log entry newer than the specified time-out value. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE------- -``` -$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -Clear-SPScaleOutDatabaseLog -Database $database -LogEntryTimeout 30 -``` - -This example removes all scale-out log entries in the first scale-out database of the specified service application unless there is a scale-out log entry which is more recent than 30 minutes. - -## PARAMETERS - -### -Database -Specifies the scale-out database from which to clear the logs. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogEntryTimeout -Specifies the time-out value in minutes for the log entries. -If there is at least one log entry which is more recent than this value, no log entries will be deleted. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseTenantData.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseTenantData.md deleted file mode 100644 index d736745d6f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPScaleOutDatabaseTenantData.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spscaleoutdatabasetenantdata -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPScaleOutDatabaseTenantData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPScaleOutDatabaseTenantData - -## SYNOPSIS - -Removes all data related to the specified site subscription. - - - -## SYNTAX - -``` -Clear-SPScaleOutDatabaseTenantData -ServiceApplication <SPServiceApplicationPipeBind> - -SiteSubscriptionId <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Clear-SPScaleOutDatabaseTenantData cmdlet removes all data related to the specified site subscription from the specified service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE--------- -``` -Clear-SPScaleOutDatabaseTenantData -ServiceApplication $serviceApplication -SiteSubscriptionId "5CAF2F99-A75F-4239-B9CD-7FE63D1CE904" -``` - -This example clears all data related to the site subscription with id 5CAF2F99-A75F-4239-B9CD-7FE63D1CE904 from the specified service application. - -## PARAMETERS - -### -ServiceApplication -Specifies the service application in which to clear data. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptionId -Specifies the site subscription id of the site subscription in which to clear data. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Export-SPScaleOutDatabaseTenantData](Export-SPScaleOutDatabaseTenantData.md) - -[Import-SPScaleOutDatabaseTenantData](Import-SPScaleOutDatabaseTenantData.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSecureStoreCredentialMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSecureStoreCredentialMapping.md deleted file mode 100644 index ae260c3dbb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSecureStoreCredentialMapping.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spsecurestorecredentialmapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPSecureStoreCredentialMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPSecureStoreCredentialMapping - -## SYNOPSIS -Deletes a credential mapping from a Secure Store Service application. - -## SYNTAX - -### AllApplications -``` -Clear-SPSecureStoreCredentialMapping [-All] -Principal <SPClaim> -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### OneApplication -``` -Clear-SPSecureStoreCredentialMapping -Identity <SPSecureStoreApplication> -Principal <SPClaim> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Clear-SPSecureStoreCredentialMapping cmdlet deletes a credential mapping from a Secure Store application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApplication" -$userClaim = New-SPClaimsPrincipal -Identity "CONTOSO\janedoe" -IdentityType WindowsSamAccountName -Clear-SPSecureStoreCredentialMapping -Identity $ssApp -Principal $userClaim -``` - -This example deletes the credential mapping from the target application ContosoTargetApplication for the user with alias johndoe and domain CONTOSO. - -## PARAMETERS - -### -All -Specifies that the principal is deleted from all Secure Store applications. - -```yaml -Type: SwitchParameter -Parameter Sets: AllApplications -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the Secure Store application (that contains the principal) from which to delete the credential mapping. - -```yaml -Type: SPSecureStoreApplication -Parameter Sets: OneApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Principal -Specifies the SPClaims object that contains the principal. - -```yaml -Type: SPClaim -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context for which the credential mapping will be deleted. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: AllApplications -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSecureStoreDefaultProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSecureStoreDefaultProvider.md deleted file mode 100644 index 0cd11b237b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSecureStoreDefaultProvider.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spsecurestoredefaultprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPSecureStoreDefaultProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPSecureStoreDefaultProvider - -## SYNOPSIS -Clears the secure store provider. - -## SYNTAX - -``` -Clear-SPSecureStoreDefaultProvider [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Clear-SPSecureStoreDefaultProvider cmdlet clears the secure store provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Clear-SPSecureStoreDefaultProvider -``` - -This example clears the secure store provider. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseDeletedDataSubRange.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseDeletedDataSubRange.md deleted file mode 100644 index f3109b4455..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseDeletedDataSubRange.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spserverscaleoutdatabasedeleteddatasubrange -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPServerScaleOutDatabaseDeletedDataSubRange -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPServerScaleOutDatabaseDeletedDataSubRange - -## SYNOPSIS - -Clears all partitions inside the specified deleted subrange. - - -## SYNTAX - -``` -Clear-SPServerScaleOutDatabaseDeletedDataSubRange -Database <SPDatabasePipeBind> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Clear-SPServerScaleOutDatabaseDeletedDataSubRange cmdlet to clear all partitions inside the specified deleted subrange that are contained within a specified scale-out database. - - - -## EXAMPLES - -### --------------EXAMPLE-------------- -``` -$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -$state = Get-SPServerScaleOutDatabaseDataState -Database $database -Set-SPServerScaleOutDatabaseDataSubRange -Database $database -Range $state.Range -SubRangePoint $state.Range.RangeEnd -SubRangeMode Deleted -IsUpperSubRange $false -$state = Get-SPServerScaleOutDatabaseDataState -Database $database -Clear-SPServerScaleOutDatabaseDeletedDataSubRange -Database $database -Range $state.Range -IsUpperSubRange $false -``` - -This example creates a deleted subrange that starts from the data range start point and ends at the data range end point on the first scale-out database of the specified service application. -The example then clears that subrange and all data in the partitions in the subrange. - - -## PARAMETERS - -### -Database - -Specifies the scale-out database to clear the deleted subrange from. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsUpperSubRange - -Specifies whether the subrange with deleted mode is on the upper or lower side of the data range. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Range - -Specifies the expected data range of the scale-out database. - -```yaml -Type: SPScaleOutDataRange -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-SPServerScaleOutDatabaseDataSubRange](Set-SPServerScaleOutDatabaseDataSubRange.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseLog.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseLog.md deleted file mode 100644 index a2483b6119..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseLog.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spserverscaleoutdatabaselog -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPServerScaleOutDatabaseLog -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPServerScaleOutDatabaseLog - -## SYNOPSIS - -Clears all scale-out logs in the specified scale-out database unless there is a scale-out log entry newer than the specified time-out value. - - -## SYNTAX - -``` -Clear-SPServerScaleOutDatabaseLog -Database <SPDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-LogEntryTimeout <Int32>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Clear-SPServerScaleOutDatabaseLog cmdlet clears all scale-out logs in the specified scale-out database unless there is a scale-out log entry newer than the specified time-out value. - -## EXAMPLES - -### -----------EXAMPLE------- -``` -$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -Clear-SPServerScaleOutDatabaseLog -Database $database -LogEntryTimeout 30 -``` - -This example removes all scale-out log entries in the first scale-out database of the specified service application unless there is a scale-out log entry which is more recent than 30 minutes. - - -## PARAMETERS - -### -Database - -Specifies the scale-out database from which to clear the logs. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogEntryTimeout - -Specifies the time-out value in minutes for the log entries. -If there is at least one log entry which is more recent than this value, no log entries will be deleted. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseTenantData.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseTenantData.md deleted file mode 100644 index 90b8575ccc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPServerScaleOutDatabaseTenantData.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spserverscaleoutdatabasetenantdata -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPServerScaleOutDatabaseTenantData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPServerScaleOutDatabaseTenantData - -## SYNOPSIS - -Removes all data related to the specified site subscription. - -## SYNTAX - -``` -Clear-SPServerScaleOutDatabaseTenantData -ServiceApplication <SPServiceApplicationPipeBind> - -SiteSubscriptionId <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Clear-SPServerScaleOutDatabaseTenantData cmdlet removes all data related to the specified site subscription from the specified service application. - - - - -## EXAMPLES - -### ------------EXAMPLE--------- -``` -Clear-SPServerScaleOutDatabaseTenantData -ServiceApplication $serviceApplication -SiteSubscriptionId "5CAF2F99-A75F-4239-B9CD-7FE63D1CE904" -``` - -This example clears all data related to the site subscription with id 5CAF2F99-A75F-4239-B9CD-7FE63D1CE904 from the specified service application. - -## PARAMETERS - -### -ServiceApplication - -Specifies the service application in which to clear data. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptionId - -Specifies the site subscription id of the site subscription in which to clear data. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Export-SPServerScaleOutDatabaseTenantData](Export-SPServerScaleOutDatabaseTenantData.md) - -[Import-SPServerScaleOutDatabaseTenantData](Import-SPServerScaleOutDatabaseTenantData.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSiteSubscriptionBusinessDataCatalogConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSiteSubscriptionBusinessDataCatalogConfig.md deleted file mode 100644 index 1815aad85a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Clear-SPSiteSubscriptionBusinessDataCatalogConfig.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/clear-spsitesubscriptionbusinessdatacatalogconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Clear-SPSiteSubscriptionBusinessDataCatalogConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Clear-SPSiteSubscriptionBusinessDataCatalogConfig - -## SYNOPSIS - -Deletes all data from the Business Data Connectivity Metadata Store for a specified partition. - - - -## SYNTAX - -``` -Clear-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Clear-SPSiteSubscriptionBusinessDataCatalogConfig cmdlet deletes all models and data from the Business Data Connectivity Metadata Store for a specified service partition. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Clear-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext http://contoso -``` - -This example deletes all data from the Business Data Connectivity Metadata Store for the specified site. - -## PARAMETERS - -### -ServiceContext -Specifies the service context for which the Business Data Connectivity models are deleted. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Connect-SPConfigurationDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Connect-SPConfigurationDatabase.md deleted file mode 100644 index d38944f692..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Connect-SPConfigurationDatabase.md +++ /dev/null @@ -1,208 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/connect-spconfigurationdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Connect-SPConfigurationDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Connect-SPConfigurationDatabase - -## SYNOPSIS - -Connects the local server computer to a farm. - - - -## SYNTAX - -``` -Connect-SPConfigurationDatabase [-DatabaseName] <String> [-SkipRegisterAsDistributedCacheHost] - [-Passphrase] <SecureString> -DatabaseServer <String> [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseCredentials <PSCredential>] [-DatabaseFailOverPartner <String>] [-LocalServerRole <SPServerRole>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Connect-SPConfigurationDatabase cmdlet connects the current server to the specified configuration database. - -Essentially, this cmdlet connects the server to the farm. -If the current computer cannot be connected to a farm, the following error message is displayed: - -"This machine is already connected to a SharePoint farm. -See: Dismount-SPConfigurationDatabase" - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Connect-SPConfigurationDatabase -DatabaseServer "ServerName\InstanceName" -DatabaseName "SharePointConfigurationDatabaseName" -Passphrase (ConvertTo-SecureString "MyP@ssw0rd" -AsPlainText -Force) -Start-Service SPTimerv4 -``` - -This example joins the local server computer to a farm that is configured to use the database SharePointConfigurationDatabase on an instance of SQL Server by using the name ServerName\InstanceName with the passphrase MyP@ssw0rd. - -## PARAMETERS - -### -DatabaseName -Specifies the name of the configuration database to which to connect the server. - -The type must be a valid database name; for example, DB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the server on which to create the configuration database. -The default value is the local computer name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Passphrase -Specifies the secure password phrase for connecting the current server to the configuration database. - -The type must be a valid secure string; for example, MyBDCApp1serverkey. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 9 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -SkipRegisterAsDistributedCacheHost -By default all the servers in the farm are registered as a cache host (that is, DistributedCacheService is running by default). - -Use this parameter to not register the server computer as a distributed cache host. -If you want to have a dedicated cache host, then use this parameter to make sure that caching service is not installed on the computer. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 10 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL authentication. -If this parameter is not specified, the current user is used. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DatabaseFailOverPartner -Specifies the Database Mirroring partner for a SQL Server instance. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalServerRole -Specifies the MinRole assigned to the local server. - -```yaml -Type: SPServerRole -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Convert-SPWebApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Convert-SPWebApplication.md deleted file mode 100644 index 0824092698..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Convert-SPWebApplication.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/convert-spwebapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Convert-SPWebApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Convert-SPWebApplication - -## SYNOPSIS - -Converts the authentication mode of a web application. - - - -## SYNTAX - -``` -Convert-SPWebApplication -Identity <SPWebApplicationPipeBind> -From <String> -To <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Force] [-RetainPermissions] [-Database <SPContentDatabase>] - [-MapList <String>] [-SiteSubsriptionId <Guid>] [-SkipPolicies] [-SkipSites] - [-SourceSkipList <String>] [-TrustedProvider <SPTrustedIdentityTokenIssuerPipeBind>] - [-LoggingDirectory <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Convert-SPWebApplication cmdlet to convert the authentication mode of a Web application to Windows Claims authentication mode and migrate the user accounts in the content database to claims encoded values. - -When retaining permissions, users within Sites are only converted if the source account is enabled and queryable by SharePoint. For example, if the Active Directory account is deleted or disabled prior to a Classic Windows to Windows Claims conversion, the account in the database will not be updated to the Claims format. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE 1------- -``` -Convert-SPWebApplication -Identity "https://<webappurl>" -To Claims -RetainPermissions -``` - -This example converts a web application specified by the Identity parameter to use the claim authentication mode. - -### ------------EXAMPLE 2------- -``` -Convert-SPWebApplication -Identity "https://<webappurl>" -From Legacy -To Claims -RetainPermissions -``` - -This example converts a web application specified by the Identity parameter from Classic Windows authentication to Claims authentication mode while retaining permissions. The -From parameter is required after security update MS04-022 or the April 2014 Cumulative Update for SharePoint Server 2013 is applied. This is required for all versions of SharePoint Server 2016. - -## PARAMETERS - -### -Identity -Specifies the URL of the web application that you want to convert, for example: https://mysite/app1 - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -From -Specifies the authentication method to convert from. - -Valid values for this parameter are as follows. - -Legacy, Claims-Windows, Claims-Trusted-Default - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -To -Specifies the authentication method to convert to. - -Valid values for this parameter are as follows. - -Claims, Claims-Windows, Claims-Trusted-Default, Claims-SharePoint-Online - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Force -Forces the conversion of the web application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetainPermissions -Specifies the account under which the cmdlet is run and retains the permission in the web application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -Specifies the name of the content database to migrate. - -```yaml -Type: SPContentDatabase -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MapList -Specifies a file containing as list of rows in the following format: user-key, migrated-user-name, migrated-user-key. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubsriptionId -Specifies the GUID fo the Site Subscription. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipPolicies -Specifies the SPWebApplication security policies will not be migrated. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipSites -Specifies the SPWebApplication's SPSites will not be migrated. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceSkipList -Specifies a file containing as list of rows in the following format: user-key. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedProvider -When you migrate from a trusted login provider this is how you specify which trusted login provider. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoggingDirectory -Specifies a directory where verbose logs about the results of the migration will be written. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPAccessServicesDatabaseCredentials.md b/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPAccessServicesDatabaseCredentials.md deleted file mode 100644 index 32bfe490d0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPAccessServicesDatabaseCredentials.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/copy-spaccessservicesdatabasecredentials -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Copy-SPAccessServicesDatabaseCredentials -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Copy-SPAccessServicesDatabaseCredentials - -## SYNOPSIS -{{Fill in the Synopsis}} - -## SYNTAX - -``` -Copy-SPAccessServicesDatabaseCredentials [-AppUrl] <String> [-AssignmentCollection <SPAssignmentCollection>] - -ServerCredential <NetworkCredential> -ServiceContext <SPServiceContextPipeBind> -SourceServer <String> - -TargetServer <String> [<CommonParameters>] -``` - -## DESCRIPTION -{{Fill in the Description}} - -## EXAMPLES - -### Example 1 -``` - {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -AppUrl -{{Fill AppUrl Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServerCredential -{{Fill ServerCredential Description}} - -```yaml -Type: NetworkCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -{{Fill ServiceContext Description}} - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SourceServer -{{Fill SourceServer Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetServer -{{Fill TargetServer Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPActivitiesToWorkflowService.md b/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPActivitiesToWorkflowService.md deleted file mode 100644 index dbf228bc81..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPActivitiesToWorkflowService.md +++ /dev/null @@ -1,180 +0,0 @@ ---- -external help file: Microsoft.SharePoint.WorkflowServices.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/copy-spactivitiestoworkflowservice -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Copy-SPActivitiesToWorkflowService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Copy-SPActivitiesToWorkflowService - -## SYNOPSIS -Copies the Workflow Activities from SharePoint to Workflow Manager. Activities are defined within Microsoft provided or custom coded assemblies. - - - -## SYNTAX - -``` -Copy-SPActivitiesToWorkflowService [-ActivityName <String>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Credential <ICredentials>] [-Force <Boolean>] [-WhatIf] [-WorkflowServiceAddress <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Copies Workflow activities from SharePoint Server to Workflow Manager. - -## EXAMPLES - -### Example 1 -``` -$credential = [System.Net.CredentialCache]::DefaultNetworkCredentials -$site = Get-SPSite <siteurl> -$proxy = Get-SPWorkflowServiceApplicationProxy -$svcAddress = $proxy.GetWorkflowServiceAddress($site) -Copy-SPActivitiesToWorkflowService -WorkflowServiceAddress $svcAddress -Credential $credential -Force $true -``` - - -Copies the Workflow activities from SharePoint to the Workflow Manager farm using the specified Site Collection URL as a reference. - - -## PARAMETERS - -### -ActivityName -Copies a specific ActivityName. If not specified, all Activities are copied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -The credential used to connect to Workflow Manager. - -```yaml -Type: ICredentials -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces a specific Activity to be copied to Workflow Manager. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkflowServiceAddress -The Workflow Manager farm endpoint URL. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPBusinessDataCatalogAclToChildren.md b/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPBusinessDataCatalogAclToChildren.md deleted file mode 100644 index d06227be48..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPBusinessDataCatalogAclToChildren.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/copy-spbusinessdatacatalogacltochildren -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Copy-SPBusinessDataCatalogAclToChildren -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Copy-SPBusinessDataCatalogAclToChildren - -## SYNOPSIS - -Copies a set of permissions of a Business Data Connectivity Metadata Store metadata object to its child objects. - - - -## SYNTAX - -``` -Copy-SPBusinessDataCatalogAclToChildren -MetadataObject <MetadataObject> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Copy-SPBusinessDataCatalogAclToChildren cmdlet copies a set of rights of a Business Data Connectivity metadata object to its child objects. - -Any principals and their rights will be lost from the child metadata objects. -Make sure that the parent metadata object has the final permissions you want, or make sure to append them to the child object again after you run this cmdlet. - -Running this cmdlet on a BdcObjectType BdcCatalog (Business Data Connectivity Metadata Store) will propagate to: - -- BDC Models -- External Systems -- External Content Types -- Methods -- Method Instances - -Running this cmdlet on a BdcObjectType Model (Business Data Connectivity Model) will propagate to: - -- Nothing; this type has no child metadata objects - -Running this cmdlet on a BdcObjectType LobSystem (External System) will propagate to: - -- External Content Types -- Methods -- Method Instances - -Running this cmdlet on a BdcObjectType Entity (External Content Type) will propagate to: - -- Methods -- Method Instances - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ExternalSystem = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "LobSystem" -ServiceContext https://contoso -Name "ContosoDatabase" -``` - -This example looks at the principals (users) and their corresponding rights given for the External System metadata object, and overwrites the permissions of its child metadata objects with these same principals and rights. - -Any principals and their rights will be lost from the child metadata objects. -Make sure that the parent metadata object has the final permissions you want, or make sure to append them to the child object again after you run this cmdlet. - -## PARAMETERS - -### -MetadataObject -Specifies the Business Data Connectivity metadata object. - -```yaml -Type: MetadataObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPContentTypes.md b/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPContentTypes.md deleted file mode 100644 index fb0f04eca0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPContentTypes.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/copy-spcontenttypes -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Copy-SPContentTypes -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Copy-SPContentTypes - -## SYNOPSIS -Specifies content types for replicating from on-premises to SharePoint Online (SPO) environment. - -## SYNTAX - -``` -Copy-SPContentTypes [-AssignmentCollection <SPAssignmentCollection>] [-AuthEndpoint <String>] - -ContentTypeNames <String[]> -Credential <PSCredential> [-GraphApiEndPoint <String>] -LocalSiteUrl <Uri> - -LocalTermStoreName <String> -RemoteSiteUrl <Uri> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used in hybrid scenarios with SharePoint Online to copy Content Types from an on-premises farm to SharePoint Online. - -## EXAMPLES - -### Example 1 -``` -Copy-SPContentTypes -LocalSiteUrl https://localsite/ -LocalTermStoreName "managed metadata service application proxy" -RemoteSiteUrl https://contoso.sharepoint.com/ -ContentTypeNames @("ContentTypeA", "ContentTypeB") -Credential (Get-Credential) -``` - -This example migrates the specified content types named: ContentTypeA, ContentTypeB on the local site https://localsite/ whose term store named "managed metadata service application proxy" to the hub site of remote site https://contoso.sharepoint.com/. If the remote site is a hub site, the migration target will be itself. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthEndpoint -Specifies the AuthEndpoint to use, but not the default one. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentTypeNames -Specifies the content type names to be migrated. Can be in a form of an array. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Credential -Specifies the administrator account credential of the target SharePoint Online site. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -GraphApiEndPoint -Specifies the GraphApiEndpoint to use, but not the default one. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalSiteUrl -Specifies the migration source. Can be a local site or a local hubsite. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -LocalTermStoreName -Specifies the name of the local term store of the local site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -RemoteSiteUrl -Specifies the migration target. You can input a remote site url or remote hub site url, both will be processed to be the hub site url. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Uri -System.String -System.String[] -System.Management.Automation.PSCredential -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPSideBySideFiles.md b/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPSideBySideFiles.md deleted file mode 100644 index 02fc454ebb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPSideBySideFiles.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/copy-spsidebysidefiles -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Copy-SPSideBySideFiles -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Copy-SPSideBySideFiles - -## SYNOPSIS -Copy side by side files. - -## SYNTAX - -``` -Copy-SPSideBySideFiles [-AssignmentCollection <SPAssignmentCollection>] [-LogFile <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -In SharePoint Server 2016, zero down time in-place upgrade is available. If the PSConfig.exe file is used during an upgrade and copy SideBySide files fail, you can use the **Copy-SPSideBySideFiles** cmdlet to copy SideBySide files. If you use Microsoft PowerShell scripts instead of PSConfig.exe to perform an upgrade, please run the **Copy-SPSideBySideFiles** cmdlet to copy SideBySide files. - -## EXAMPLES - -### Example 1 -``` -Copy-SPSideBySideFiles -LogFile "C:\CopySideBySideFiles.log" -``` - -This example copies SideBySide files and writes a log data of the copy process to the CopySideBySideFiles.log file. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -LogFile -Specifies the fully-qualified logfile name of SideBySide copy operation. If LogFile is not specified, the logfile will be placed in default SharePoint log files folder. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPSite.md deleted file mode 100644 index 135e62d346..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPSite.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/copy-spsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Copy-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Copy-SPSite - -## SYNOPSIS - -Makes a copy of a site collection. - - - -## SYNTAX - -``` -Copy-SPSite [-Identity] <SPSitePipeBind> [-TargetUrl] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-DestinationDatabase <SPContentDatabasePipeBind>] [-HostHeaderWebApplication <String>] [-PreserveSiteId] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Copy-SPSite cmdlet to make a copy of a site collection from an implied source content database to a specified destination content database. - -The copy of the site collection has a new URL and a new SiteID. -When you have database snapshot capabilities on a computer runningSQL Server, a temporary snapshot of the source database is created for the duration of the copy to prevent any data changes during the copy process. -If you do not have database snapshot capabilities on the server running SQL Server, you can back up the source and restore it to the destination to get the same result. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE------------- -``` -Copy-SPSite https://contoso/sites/OldTeam -DestinationDatabase WSS_Content -TargetUrl https://contoso/sites/NewTeam -``` - -This example makes a copy of the https://contoso/sites/OldTeam site collection from its database to the WSS_Content database with the new URL, https://contoso/sites/NewTeam and a new Site ID. - -## PARAMETERS - -### -Identity -Specifies the site collection to copy. -This can be a valid URL or GUID. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -TargetUrl -The URL that will be used for the destination copy of the site collection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DestinationDatabase -Specifies the location where the copy will be sent to. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostHeaderWebApplication -Use when the site collection is a host-named site collection that allows the site to land on the correct web application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreserveSiteId -Specifies if the SiteID is to be saved or not. - -The valid values are True and False. The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Test-SPSite](Test-SPSite.md) - -[Repair-SPSite](Repair-SPSite.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPTaxonomyGroups.md b/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPTaxonomyGroups.md deleted file mode 100644 index 151ac812fe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Copy-SPTaxonomyGroups.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/copy-sptaxonomygroups -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Copy-SPTaxonomyGroups -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Copy-SPTaxonomyGroups - -## SYNOPSIS -Copies Managed Metadata Taxonomy Groups from SharePoint on-premises to SharePoint Online. - -## SYNTAX - -``` -Copy-SPTaxonomyGroups [-AssignmentCollection <SPAssignmentCollection>] [-AuthEndpoint <String>] - -Credential <PSCredential> [-GraphApiEndpoint <String>] -GroupNames <String[]> -LocalSiteUrl <Uri> - -LocalTermStoreName <String> -RemoteSiteUrl <Uri> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Copy-SPTaxonomyGroups cmdlet to copy specified Metadata groups from an on-premises environment to SharePoint Online in a Hybrid SharePoint setup. SharePoint Online becomes the authoritative source for the copied Taxonomy Group. All updates to the Taxonomy Group must be made in SharePoint Online. Once a Taxonomy Group is copied, it cannot be re-copied. - -## EXAMPLES - -### Example 1 -``` -$credential = Get-Credential -Copy-SPTaxonomyGroups -LocalTermStoreName "Managed Metadata Service Application Proxy" -LocalSiteUrl "https://sharepoint/" -RemoteSiteUrl "https://contoso.sharepoint.com/" -GroupNames "Group1","Group2" -Credential $credential -``` - -This example copies two taxonomy groups "Group1" and "Group2" from local Term Store to the remote Term Store in "https://contoso.com/". These two sites have been enabled with Hybrid Taxonomy. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthEndpoint -Specifies the Azure Active Directory Graph API authentication endpoint. By default, the well-known endpoint will be used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -Specifies the Taxonomy Term Store administrator credential of remote SharePoint Online Term Store. - -Writes data to remote Term Store, so a Term Store Administrator's credential is needed to perform the operations. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -GraphApiEndpoint -Specifies the Azure Active Directory Graph API endpoint. By default, the well-known endpoint will be used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupNames -Specifies the name array of Taxonomy groups in local on-premises term store that will be copied to remote SharePoint Online Term store. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -LocalSiteUrl -Specifies the Url of local SharePoint on-premises site that contains the local Taxonomy Term Store. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -LocalTermStoreName -Specifies the name of local Taxonomy Term Store in the SharePoint on-premises farm. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -RemoteSiteUrl -Specifies the Url of remote SharePoint Online site that contains remote Taxonomy Term Store. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -System.Uri -System.String[] -System.Management.Automation.PSCredential -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-ProjectServerLicense.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-ProjectServerLicense.md deleted file mode 100644 index 2101b10375..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-ProjectServerLicense.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-projectserverlicense -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Disable-ProjectServerLicense -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-ProjectServerLicense - -## SYNOPSIS -If the farm has Project Server enabled, this cmdlet will disable the Project Server functionality across the farm. All Project Web App sites will be read only and will still contain any data that existed before the license was disabled. New Project Web App sites cannot be created. - -## SYNTAX - -``` -Disable-ProjectServerLicense [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Disables Project Server functionality across the farm. - -## EXAMPLES - -### Example 1 -``` - Disable-ProjectServerLicense -``` - -This example disables Project Server functionality for the entire farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPAppAutoProvision.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPAppAutoProvision.md deleted file mode 100644 index 02d22c6fe1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPAppAutoProvision.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spappautoprovision -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPAppAutoProvision -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPAppAutoProvision - -## SYNOPSIS - -Disables automatic provisioning of an app. - - - -## SYNTAX - -``` -Disable-SPAppAutoProvision [-AssignmentCollection <SPAssignmentCollection>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Disable-SPAppAutoProvision cmdlet to disable automatic provisioning of an app to the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1-------------- -``` -Disable-SPAppAutoProvision -``` - -This example disables app auto provisioning for the farm. -The app auto provisioning is enabled by default. -This setting overrides site subscription level setting. - -### ---------------EXAMPLE 2-------------- -``` -C:\PS>$subscription = Get-SPSiteSubscription https://Contoso.com - -Disable-SPAppAutoProvision -SiteSubscription $subscription -``` - -This example disables app auto provisioning for the site subscription for Contoso.Com site. -The app auto provisioning is enabled by default. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site collection for which auto provisioning is to be disabled. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Enable-SPAppAutoProvision](Enable-SPAppAutoProvision.md) - -[Get-SPAppAutoProvisionConnection](Get-SPAppAutoProvisionConnection.md) - -[Set-SPAppAutoProvisionConnection](Set-SPAppAutoProvisionConnection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPBusinessDataCatalogEntity.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPBusinessDataCatalogEntity.md deleted file mode 100644 index 42164d01ef..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPBusinessDataCatalogEntity.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spbusinessdatacatalogentity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPBusinessDataCatalogEntity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPBusinessDataCatalogEntity - -## SYNOPSIS - -Deactivates an External Content type in the Business Data Connectivity Metadata Store. - - - -## SYNTAX - -``` -Disable-SPBusinessDataCatalogEntity -Identity <Entity> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Disable-SPBusinessDataCatalogEntity cmdlet deactivates an External Content type in the Business Data Connectivity Metadata Store. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$entityToDisable = Get-SPBusinessDataCatalogMetadataObject -Namespace "Contoso" -Name "Customer" -BdcObjectType "Entity" -ServiceContext http://contoso -Disable-SPBusinessDataCatalogEntity -Identity $entityToDisable -``` - -This example deactivates the External Content type of the name Customer in the Contoso. -Note that the terms External Content type and Entity refer to the same object type, and the term Disable refers to the same action as the Business Data Connectivity term Deactivate. - -## PARAMETERS - -### -Identity -Specifies the External Content type in the Business Data Connectivity Metadata Store to deactivate. - -```yaml -Type: Entity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPFeature.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPFeature.md deleted file mode 100644 index ed21fc3c70..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPFeature.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spfeature -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPFeature -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPFeature - -## SYNOPSIS - -Disables an installed SharePoint Feature at a given scope. - - - -## SYNTAX - -``` -Disable-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Force] [-Url <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Disable-SPFeature cmdlet disables a SharePoint Feature at the given scope. -If the scope of the Feature is the farm, the URL is not needed. -Otherwise, provide the URL at which this Feature is to be deactivated (explicit scope is not needed). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Disable-SPFeature -identity "MyCustom" -URL https://somesite -``` - -This example disables the "MyCustom" Web site scoped feature at https://somesite. - -### --------------EXAMPLE 2----------------- -``` -C:\PS>$w = Get-SPWeb https://somesite/myweb | ForEach{ $_.URL } -Get-SPFeature -Web $w |%{ Disable-SPFeature -Identity $_ -URL $w} -``` - -This example disables all features in the subsite at https://somesite/myweb. - -You do not need to use the SPAssignment cmdlets in this case because the Web object is not stored -- only the string value for the URL. - -## PARAMETERS - -### -Identity -Specifies the name of the Feature or GUID to disable. - -The type must be the name of the Feature folder located in the 14\Template\Features folder or GUID, in the format 21d186e1-7036-4092-a825-0eb6709e9281. - -```yaml -Type: SPFeatureDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces a Feature to be disabled. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Specifies the URL of the Web application, site collection, or Web site to which the Feature is being disabled. - -The type must be a valid URL, such as https://server_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPHealthAnalysisRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPHealthAnalysisRule.md deleted file mode 100644 index 10ecbd8a86..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPHealthAnalysisRule.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-sphealthanalysisrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPHealthAnalysisRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPHealthAnalysisRule - -## SYNOPSIS - -Disables health analyzer rules. - - - -## SYNTAX - -``` -Disable-SPHealthAnalysisRule [-Identity] <SPHealthAnalysisRuleInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Disable-SPHealthAnalysisRule cmdlet to disable a health analyzer rule. - -The SPHealthAnalysisRule cmdlets were first introduced in the February 2011 Cumulative Update, which is available for download as follows: - ---Description of the SharePoint Foundation Cumulative Update Server Hotfix Package (SharePoint Foundation server-package) (https://support.microsoft.com/kb/2475880) ---Description of the SharePoint Server Cumulative Update Server Hotfix Package (MOSS server-package (https://support.microsoft.com/kb/2475878) - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE 1--------------------------- -``` -Disable-SPHealthAnalysisRule -Identity "CustomRule" -``` - -This example disables the health analyzer rule named CustomRule. - -## PARAMETERS - -### -Identity -Specifies the name or GUID of the health analyzer rule to disable. - -The type must be a valid name; an instance of a valid SPHealthAnalysisRule object, or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPHealthAnalysisRuleInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPInfoPathFormTemplate.md deleted file mode 100644 index 3036ed9c0c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPInfoPathFormTemplate - -## SYNOPSIS -Deactivates a InfoPath form template from the specified site collection. - -## SYNTAX - -``` -Disable-SPInfoPathFormTemplate [-Identity] <SPFormTemplatePipeBind> -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Disable-SPInfoPathFormTemplate cmdlet deactivates the InfoPath form template that is specified in the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Disable-SPInfoPathFormTemplate -Identity "FormTemplate.xsn" -Site https://testSite -``` - -This example deactivates an InfoPath form template from a site collection named TestSite. - -## PARAMETERS - -### -Identity -Specifies the InfoPath form template to disable. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a form template (for example, InfoPathFormTemplate1); a valid name of a form template files (for example, FormTemplateFile1.xsn); or an instance of a valid SPFormTemplate object. - -```yaml -Type: SPFormTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Specifies the site collection that contains the InfoPath form template to deactivate. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: Url -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md deleted file mode 100644 index d42ae7342d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spprojectactivedirectoryenterpriseresourcepoolsync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync - -## SYNOPSIS -Disables Timer Job execution of the Active Directory Enterprise Resource Pool synchronization. - -## SYNTAX - -``` -Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync [-Url] <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Active Directory Enterprise Resource Pool synchronization is used to create or update multiple Project Server enterprise resources at the same time. -Project Server enterprise resources can also be automatically activated and deactivated based on group membership in the Active Directory directory service. -For example, new employees in your department can automatically be added as Project Server enterprise resources as long as they are in the Active Directory group selected for synchronization. -Conversely, employees who are removed from the Active Directory group have their Project Server accounts deactivated upon synchronization. - -Enterprise Resource Pool synchronization also updates enterprise resource properties with the most current data from Active Directory. -For example, an employee's name and e-mail address may change because of marriage. -As long as the change is made in Active Directory and the user is in the linked group, the change occurs in the user's Enterprise Resource properties when synchronization occurs. - -The Enterprise Resource Pool can be mapped to a single Active Directory group for synchronization. -However, this Active Directory group can contain nested groups whose members are also synchronized. - -The following actions can occur during the Enterprise Resource Pool synchronization process: - -- A new Project Server enterprise resource and corresponding user account can be created based on an Active Directory account. -- An active Project Server resource/user account can be deactivated. -- An existing Project Server user account's metadata (for example, name, e-mail address, and so on) can be updated if it has changed in Active Directory. -- A previously inactive Project Server resource/user account can be reactivated. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync https://localhost/pwa -``` - -This example disables Timer Job execution of the Active Directory Enterprise Resource Pool synchronization on https://localhost/pwa. - -## PARAMETERS - -### -Url -Specifies the URL of the Project Web App (PWA) instance to disable Active Directory Enterprise Resource Sync. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync](Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEmailNotification.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEmailNotification.md deleted file mode 100644 index 7de18fce37..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEmailNotification.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spprojectemailnotification -applicable: Project Server 2016, Project Server 2019 -title: Disable-SPProjectEmailNotification -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPProjectEmailNotification - -## SYNOPSIS -Turns off the Project Web App site level setting for email notifications in Project Server. - -## SYNTAX - -``` -Disable-SPProjectEmailNotification [-Url] <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Turns off the Project Web App site level setting for email notifications in Project Server. - -## EXAMPLES - -### Example 1 -``` -Disable-SPProjectEmailNotification -Url https://pwa_site -``` - -Disables Project Server email notifications on the Project Web App site, https://pwa_site. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the Project Web App site. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEnterpriseProjectTaskSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEnterpriseProjectTaskSync.md deleted file mode 100644 index 4242876477..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEnterpriseProjectTaskSync.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spprojectenterpriseprojecttasksync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Disable-SPProjectEnterpriseProjectTaskSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPProjectEnterpriseProjectTaskSync - -## SYNOPSIS -Disables task sync between Project Web App and the associated project site. Once this is disabled, tasks created in the enterprise project in Project Web App will no longer sync to the task list on the project site associated with the project. This feature is disabled by default. - -## SYNTAX - -``` -Disable-SPProjectEnterpriseProjectTaskSync [-AssignmentCollection <SPAssignmentCollection>] -Url <Uri> - [<CommonParameters>] -``` - -## DESCRIPTION -Disables task sync between Project Web App and the associated project site. - -## EXAMPLES - -### Example 1 -``` -Disable-SPProjectEnterpriseProjectTaskSync -Url https://pwa_site -``` - -Disables Project Server task sync on the Project Web App site, https://pwa_site. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the PWA site. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectQueueStatsMonitoring.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectQueueStatsMonitoring.md deleted file mode 100644 index 0c8e6d1c9a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectQueueStatsMonitoring.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spprojectqueuestatsmonitoring -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Disable-SPProjectQueueStatsMonitoring -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPProjectQueueStatsMonitoring - -## SYNOPSIS -Disables monitoring Project Server queue statistics. - -## SYNTAX - -``` -Disable-SPProjectQueueStatsMonitoring [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Disables monitoring Project Server queue statistics. - -## EXAMPLES - -### Example 1 -``` -Disable-SPProjectQueueStatsMonitoring -``` - -Disables monitoring Project Server queue statistics. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPSessionStateService.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPSessionStateService.md deleted file mode 100644 index d147374372..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPSessionStateService.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spsessionstateservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPSessionStateService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPSessionStateService - -## SYNOPSIS -Turns off the session state service on the farm. - -## SYNTAX - -``` -Disable-SPSessionStateService [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Disable-SPSessionStateService cmdlet turns off the session state service. -If your farm does not depend on session state service, we recommend that you disable it. - -When session state is disabled, some SharePoint Server services, components, and third-party components no longer function. -Changing this property modifies the Web.config file on every content Web application on every server in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Disable-SPSessionStateService -``` - -This example turns off ASP.NET session state on the farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPSingleSignOn.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPSingleSignOn.md deleted file mode 100644 index 93bba4a3d4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPSingleSignOn.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spsinglesignon -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPSingleSignOn -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPSingleSignOn - -## SYNOPSIS -Disables the single sign-on (SSO) Service on a farm server. - -## SYNTAX - -``` -Disable-SPSingleSignOn -ServerName <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Disable-SPSingleSignOn cmdlet to disable the SSO Service on a farm server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Disable-SPSingleSignOn myOldSSO -ServerName CONTOSO -``` - -This example turns off the SSO Service on the server named CONTOSO. - -## PARAMETERS - -### -ServerName -Specifies the name of the server in which the service is running. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPTimerJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPTimerJob.md deleted file mode 100644 index 10e2c268a6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPTimerJob.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-sptimerjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPTimerJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPTimerJob - -## SYNOPSIS - -Disables a timer job. - - - -## SYNTAX - -``` -Disable-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Disable-SPTimerJob cmdlet disables a timer job. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE----------------------- -``` -Disable-SPTimerJob job-ceip-datacollection -``` - -This example disables the timer job named job-ceip-datacollection. - -## PARAMETERS - -### -Identity -Specifies the timer job to disable. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a timer job (for example, TimerJob1); or an instance of a valid SPTimerJob object. - -```yaml -Type: SPTimerJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPUserLicensing.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPUserLicensing.md deleted file mode 100644 index db97197710..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPUserLicensing.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spuserlicensing -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPUserLicensing -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPUserLicensing - -## SYNOPSIS - -Disables user license enforcement. - - - -## SYNTAX - -``` -Disable-SPUserLicensing [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Disable-SPUserLicensing cmdlet disables user license enforcement on the SharePoint farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1------------------- -``` -Disable-SPUserLicensing -``` - -This example disables user license enforcement on the SharePoint farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPUserSolutionAllowList.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPUserSolutionAllowList.md deleted file mode 100644 index 41381b5d93..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPUserSolutionAllowList.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spusersolutionallowlist -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPUserSolutionAllowList -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPUserSolutionAllowList - -## SYNOPSIS -Disables the user managed solutions gallery capability on the farm. - -## SYNTAX - -``` -Disable-SPUserSolutionAllowList [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Disables the user managed solutions gallery capability on the farm. - -## EXAMPLES - -### Example 1 -``` -Disable-SPUserSolutionAllowList -``` - -Disables the user managed solutions gallery capability on the farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPWebApplicationHttpThrottling.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPWebApplicationHttpThrottling.md deleted file mode 100644 index d2c329acb6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPWebApplicationHttpThrottling.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spwebapplicationhttpthrottling -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPWebApplicationHttpThrottling -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPWebApplicationHttpThrottling - -## SYNOPSIS - -Turns off network throttling for a Web application. - - - -## SYNTAX - -``` -Disable-SPWebApplicationHttpThrottling [-Identity] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Disable-SPWebApplicationHttpThrottling cmdlet turns off network throttling for a Web application. -This operation prompts you to confirm that you want to turn off network throttling. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Disable-SPWebApplicationHTTPThrottling https://sitename -``` - -This example disables network throttling on the Web application https://sitename. - -## PARAMETERS - -### -Identity -Turns off network throttling on the specified SharePoint Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPWebTemplateForSiteMaster.md b/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPWebTemplateForSiteMaster.md deleted file mode 100644 index 2b7d919a1a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disable-SPWebTemplateForSiteMaster.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disable-spwebtemplateforsitemaster -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Disable-SPWebTemplateForSiteMaster -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disable-SPWebTemplateForSiteMaster - -## SYNOPSIS -Disables the site master in the farm. - -## SYNTAX - -``` -Disable-SPWebTemplateForSiteMaster [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <Int32>] -Template <SPWebTemplatePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Disable-SPWebTemplateForSiteMaster cmdlet to disable a site master in the farm. - -## EXAMPLES - -### Example 1 -``` -Disable-SPWebTemplateForSiteMaster -Template STS#0 -``` - -This example disables the template in the site master of a farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. This value sets the initial CompatibilityLevel value for the site collection. - -When this parameter is not specified, the CompatibilityLevel parameter will default to the highest possible version for the web application depending on the SiteCreationMode setting. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the name of the template. For example, SPSPERS#2. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Disconnect-SPConfigurationDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Disconnect-SPConfigurationDatabase.md deleted file mode 100644 index 426d0860b6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Disconnect-SPConfigurationDatabase.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/disconnect-spconfigurationdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Disconnect-SPConfigurationDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Disconnect-SPConfigurationDatabase - -## SYNOPSIS - -Disconnects the local server computer from the farm. - - - -## SYNTAX - -``` -Disconnect-SPConfigurationDatabase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Disconnect-SPConfigurationDatabase cmdlet disconnects the active server computer from the SharePoint configuration database. -This operation removes the server computer from the farm. -The configuration database must be disconnected before the database can be removed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Disconnect-SPConfigurationDatabase -Confirm:$false -``` - -This example removes the local server computer from a farm without prompting for user confirmation. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPContentDatabase.md deleted file mode 100644 index 15d3d4cca5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPContentDatabase.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/dismount-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Dismount-SPContentDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Dismount-SPContentDatabase - -## SYNOPSIS - -Detaches a content database from its currently associated Web application. - - - -## SYNTAX - -``` -Dismount-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Dismount-SPContentDatabase cmdlet to detatch the given content database from its currently associated Web application. -This cmdlet will not delete the content database. -Use the Remove-SPContentDatabase cmdlet to delete a content database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1------------ -``` -Dismount-SPContentDatabase 12345678-90ab-cdef-1234-567890abcdef -``` - -This example detaches the content database with the GUID 12345678-90ab-cdef-1234-567890abcdef from its current parent Web application. - -### --------------EXAMPLE 2------------ -``` -Get-SPContentDatabase -WebApplication https://sitename | Dismount-SPContentDatabase -WhatIf -``` - -This example detaches all content databases from the Web application on port 80 of the local machine. -Remove the WhatIf parameter to perform the operation. - -## PARAMETERS - -### -Identity -Specifies the content database to detach. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint content database (for example, SPContentDB1); or an instance of a valid SPContentDatabase object. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPSiteMapDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPSiteMapDatabase.md deleted file mode 100644 index 50790e0531..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPSiteMapDatabase.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/dismount-spsitemapdatabase -applicable: SharePoint Server 2016 -title: Dismount-SPSiteMapDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Dismount-SPSiteMapDatabase - -## SYNOPSIS -Do not use. - -## SYNTAX - -``` -Dismount-SPSiteMapDatabase [-DatabaseId] <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use. - -## EXAMPLES - -### ------------EXAMPLE------------------ -``` - -``` - -Do not use. - -## PARAMETERS - -### -AssignmentCollection -Do not use. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseId -Do not use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPStateServiceDatabase.md deleted file mode 100644 index 1037539c03..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPStateServiceDatabase.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/dismount-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Dismount-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Dismount-SPStateServiceDatabase - -## SYNOPSIS -Removes the association to a state service database from the farm without dropping the database in the Microsoft SQL Server database. - -## SYNTAX - -``` -Dismount-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Dismount-SPStateServiceDatabase cmdlet removes a state service database from a service application and deletes the associated SharePoint object. -This cmdlet does not delete or alter the state service database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Dismount-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -``` - -This example removes the association between the SharePoint farm and the SQL Server database without dropping the SQL Server database. - -### --------------EXAMPLE 2----------------- -``` -Get-SPStateServiceDatabase -ServiceApplication F9168C5E-CEB2-4faa-B6B -F-329BF39FA1E4 | Dismount-SPStateServiceDatabase -``` - -This example dismounts a single database because only the Identity parameter is used. - -## PARAMETERS - -### -Identity -Specifies the state service database to remove from the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a state database (for example, StateSvcDB1); or an instance of a valid SPStateServiceDatabase object. - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-ProjectServerLicense.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-ProjectServerLicense.md deleted file mode 100644 index 20816f5356..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-ProjectServerLicense.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-projectserverlicense -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Enable-ProjectServerLicense -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-ProjectServerLicense - -## SYNOPSIS -Enables all Project Server functionality in the farm. The cmdlet depends on the farm having a valid SharePoint Server license (trials are allowed). Any existing Project Web App sites will become read/write. A Project Server Trial key will only be accepted if the farm has never had a Project Server trial key previously. - -## SYNTAX - -``` -Enable-ProjectServerLicense [-Key] <String> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Enables Project Server functionality on the farm. - -## EXAMPLES - -### Example 1 -``` -Enable-ProjectServerLicense -Key XXXXX-XXXXX-XXXXX-XXXXX-XXXXX -``` - -This example enables all Project Server functionality in the farm. The type of license being enabled (full or trial) depends on the key that is passed in. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Key -License key (trial or full). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPAppAutoProvision.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPAppAutoProvision.md deleted file mode 100644 index adeba05354..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPAppAutoProvision.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spappautoprovision -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPAppAutoProvision -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPAppAutoProvision - -## SYNOPSIS - -Enables automatic provisioning of an app. - -## SYNTAX - -``` -Enable-SPAppAutoProvision [-AssignmentCollection <SPAssignmentCollection>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Enable-SPAppAutoProvision cmdlet to enable automatic provisioning of an app to the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1-------- -``` -Enable-SPAppAutoProvision -``` - -This example enables auto provisioning for the farm. -The app auto provisioning is enabled by default. -This setting overrides site subscription level setting. - -### --------------EXAMPLE 2-------- -``` -C:\PS>$subscription = Get-SPSiteSubscription https://Contoso.com -Enable-SPAppAutoProvision -SiteSubscription $subscription -``` - -This example enables app auto provisioning for the site subscription for Contoso.Com site. -The app auto provisioning is enabled by default. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site collection for which auto provisioning is to be enabled. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Disable-SPAppAutoProvision](Disable-SPAppAutoProvision.md) - -[Get-SPAppAutoProvisionConnection](Get-SPAppAutoProvisionConnection.md) - -[Set-SPAppAutoProvisionConnection](Set-SPAppAutoProvisionConnection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPBusinessDataCatalogEntity.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPBusinessDataCatalogEntity.md deleted file mode 100644 index cadf8d6cf4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPBusinessDataCatalogEntity.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spbusinessdatacatalogentity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPBusinessDataCatalogEntity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPBusinessDataCatalogEntity - -## SYNOPSIS - -Activates an External Content type in the Business Data Connectivity Metadata Store. - - - -## SYNTAX - -``` -Enable-SPBusinessDataCatalogEntity -Identity <Entity> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Enable-SPBusinessDataCatalogEntity cmdlet activates an External Content type in the Business Data Connectivity Metadata Store. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$entityToEnable = Get-SPBusinessDataCatalogMetadataObject -Namespace "Contoso" -Name "Customer" -BdcObjectType "Entity" -ServiceContext http://contoso -Enable-SPBusinessDataCatalogEntity -Identity $entityToEnable -``` - -This example activates the External Content type with the name Customer in the Contoso namespace on the site http://contoso. -Note that the terms External Content type and Entity refer to the same object type. - -## PARAMETERS - -### -Identity -Specifies the External Content type in the Business Data Connectivity Metadata Store to activate. - -```yaml -Type: Entity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPFeature.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPFeature.md deleted file mode 100644 index 897a45f02b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPFeature.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spfeature -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPFeature -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPFeature - -## SYNOPSIS - -Enables an installed SharePoint Feature at the given scope. - -## SYNTAX - -### SiteFeature -``` -Enable-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Force] [-PassThru] [-Url <String>] [-WhatIf] [<CommonParameters>] -``` - -### FarmFeatureDefinition -``` -Enable-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Force] [-PassThru] [-WhatIf] [-CompatibilityLevel <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The Enable-SPFeature cmdlet enables an installed feature at the given scope. -If the feature is a farm feature, no URL is needed. -Otherwise, provide the URL where the feature is to be enabled and it will be enabled at the proper scope based on the Feature definition. - -This cmdlet has no output unless the PassThru parameter is provided, in which case the SPFeatureDefinition object for the newly enabled feature is returned. - -If you try to use the Url parameter on a farm-scoped feature, you receive the following error message: - -The feature '\<feature name\>' applies to the entire farm; the Url parameter cannot be used with farm-scoped features. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Enable-SPFeature -identity "MyCustom" -URL https://somesite -``` - -This example enables the "MyCustom" site scoped SharePoint Feature at https://somesite. - -### --------------EXAMPLE 2----------------- -``` -C:\PS>$w = Get-SPWeb https://somesite/myweb | ForEach{ $_.URL } -Get-SPFeature -Web $w |%{ Enable-SPFeature -Identity $_ -URL $w} -``` - -This example enables all SharePoint Features in the subsite at https://somesite/myweb. - -## PARAMETERS - -### -Identity -Specifies the name of the Feature or GUID to uninstall. - -The type must be the name of the Feature folder located in the 14\Template\Features folder or GUID, in the form 21d186e1-7036-4092-a825-0eb6709e9281. - -```yaml -Type: SPFeatureDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces the activation of a Feature. -This causes any custom code associated with the Feature to rerun. - -> [!NOTE] -> Please be aware `-Force` will not work if you updated the feature with Update-SPSolution. In this case you have to disable feature first with `Disable-SPFeature` and then enable it back with `Enable-SPFeature` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -If provided, the cmdlet outputs the Feature definition object after enable. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Specifies the URL of the Web application, site collection, or Web site for which the Feature is being activated. - -The type must be a valid URL; for example, https://server_name. - -```yaml -Type: String -Parameter Sets: SiteFeature -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel -{{Fill CompatibilityLevel Description}} - -```yaml -Type: Int32 -Parameter Sets: FarmFeatureDefinition -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPHealthAnalysisRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPHealthAnalysisRule.md deleted file mode 100644 index 20df83f84c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPHealthAnalysisRule.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-sphealthanalysisrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPHealthAnalysisRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPHealthAnalysisRule - -## SYNOPSIS - -Enables a health analyzer rule. - - - -## SYNTAX - -``` -Enable-SPHealthAnalysisRule [-Identity] <SPHealthAnalysisRuleInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Enable-SPHealthAnalysisRule cmdlet to enable a health analyzer rule. - -The SPHealthAnalysisRule cmdlets were first introduced in the February 2011 Cumulative Update, which is available for download as follows: - ---Description of the SharePoint Foundation Cumulative Update Server Hotfix Package (SharePoint Foundation server-package) (https://support.microsoft.com/kb/2475880) ---Description of the SharePoint Server Cumulative Update Server Hotfix Package (MOSS server-package (https://support.microsoft.com/kb/2475878) - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE 1--------------------------- -``` -Enable-SPHealthAnalysisRule -Identity "CustomRule" -``` - -This example enables the health analyzer rule named CustomRule. - -## PARAMETERS - -### -Identity -Specifies the name or GUID of the health analyzer rule to enable. - -The type must be a valid name, an instance of a valid SPHealthAnalysisRule object, or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPHealthAnalysisRuleInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPInfoPathFormTemplate.md deleted file mode 100644 index f817aa3a70..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spinfopathformtemplate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPInfoPathFormTemplate - -## SYNOPSIS -Activates a InfoPath form template in the specified site collection. - -## SYNTAX - -``` -Enable-SPInfoPathFormTemplate [-Identity] <SPFormTemplatePipeBind> -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Enable-SPInfoPathFormTemplate cmdlet activates an InfoPath form template to the SharePoint site collection specified in the Site parameter. -This cmdlet returns a new InfoPath form template. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Enable-SPInfoPathFormTemplate -Identity "FormTemplate.xsn" -Site "https://testsite/" -``` - -This example activates an InfoPath form template to a site collection named TestSite. - -## PARAMETERS - -### -Identity -Specifies the InfoPath form template to activate. -The form template must be an administrator-approved, browser-enabled form template that is available on the server farm. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a form template (for example, InfoPathFormTemplate1); a valid name of a form template files (for example, FormTemplateFile1.xsn); or an instance of a valid SPFormTemplate object. - -```yaml -Type: SPFormTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Specifies the site collection that contains the InfoPath form template to activate. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: url -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md deleted file mode 100644 index 1133f18750..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spprojectactivedirectoryenterpriseresourcepoolsync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync - -## SYNOPSIS -Enables Timer Job execution of the Active Directory Enterprise Resource Pool synchronization. - -## SYNTAX - -``` -Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync [-Url] <Uri> - [-GroupUids] <System.Collections.Generic.IEnumerable`1[System.Guid]> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Active Directory Enterprise Resource Pool synchronization is used to create or update multiple Project Server enterprise resources at the same time. -Project Server enterprise resources can also be automatically activated and deactivated based on group membership in the Active Directory directory service. -For example, new employees in your department can automatically be added as Project Server enterprise resources as long as they are in the Active Directory group selected for synchronization. -Conversely, employees who are removed from the Active Directory group have their Project Server accounts deactivated upon synchronization. - -Enterprise Resource Pool synchronization also updates enterprise resource properties with the most current data from Active Directory. -For example, an employee's name and e-mail address may change because of marriage. -As long as the change is made in Active Directory and the user is in the linked group, the change occurs in the user's Enterprise Resource properties when synchronization occurs. - -The Enterprise Resource Pool can be mapped to a single Active Directory group for synchronization. -However, this Active Directory group can contain nested groups whose members are also synchronized. - -The following actions can occur during the Enterprise Resource Pool synchronization process: - -- A new Project Server enterprise resource and corresponding user account can be created based on an Active Directory account. -- An active Project Server resource/user account can be deactivated. -- An existing Project Server user account's metadata (for example, name, e-mail address, and so on) can be updated if it has changed in Active Directory. -- A previously inactive Project Server resource/user account can be reactivated. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### ------------ Example 1 -------------------- -``` -$groupGuids = Get-ADGroup -Filter {Name -eq 'Domain Users' -or Name -eq 'Domain Admins'} | select ObjectGuid #Active Directory PowerShell Module required -[Guid[]]$groupUids = $groupGuids[0].ObjectGuid,$groupGuids[1].ObjectGuid -Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync -Url https://pwa_site -GroupUids $groupUids -``` - -Retrieves the ObjectGuid values of the Domain Users and Domain Admins Active Directory groups and adds them to the Active Directory Enterprise Resource Pool Synchronization on the Project Web Apps site, https://pwa_site. - -## PARAMETERS - -### -Url -Specifies the URL of the Project Web App instance to enable Active Directory Enterprise Resource Sync. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupUids -The Active Directory Group GUID to synchronize the Enterprise Resource Pool with. - -```yaml -Type: System.Collections.Generic.IEnumerable`1[System.Guid] -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync](Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md) - -[Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync](Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectEmailNotification.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectEmailNotification.md deleted file mode 100644 index 8a907faec0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectEmailNotification.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spprojectemailnotification -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Enable-SPProjectEmailNotification -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPProjectEmailNotification - -## SYNOPSIS -Turns on the Project Web App site level setting for email notifications in Project Server. - -## SYNTAX - -``` -Enable-SPProjectEmailNotification [-Url] <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Turns on the Project Web App site level setting for email notifications in Project Server. - -## EXAMPLES - -### Example 1 -``` -Enable-SPProjectEmailNotification -Url https://pwa_site -``` - -Enables Project Server email notifications on the Project Web App site, https://pwa_site. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -NOTE: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the Project Web App site. -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectEnterpriseProjectTaskSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectEnterpriseProjectTaskSync.md deleted file mode 100644 index c991e7966e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectEnterpriseProjectTaskSync.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spprojectenterpriseprojecttasksync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Enable-SPProjectEnterpriseProjectTaskSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPProjectEnterpriseProjectTaskSync - -## SYNOPSIS -Enables task sync between Project Web App and the associated project site. Once this is enabled, tasks created in the enterprise project in Project Web App will sync to the task list on the project site associated with the project. This feature is disabled by default. - -If you enable this feature, the restrictions that come with SharePoint lists, such as the maximum number of items supported before throttling, apply. - -Syncing tasks uses the queue and can affect performance. You should enable it only if you really need it. - -## SYNTAX - -``` -Enable-SPProjectEnterpriseProjectTaskSync [-AssignmentCollection <SPAssignmentCollection>] -Url <Uri> - [<CommonParameters>] -``` - -## DESCRIPTION -Enables task sync between Project Web App and the associated project site. - -## EXAMPLES - -### Example 1 -``` -Enable-SPProjectEnterpriseProjectTaskSync -Url https://pwa_site -``` - -Enables Project Task sync on the Project Web Apps site, https://pwa_site. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the PWA site. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectQueueStatsMonitoring.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectQueueStatsMonitoring.md deleted file mode 100644 index 56c73758b1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPProjectQueueStatsMonitoring.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spprojectqueuestatsmonitoring -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Enable-SPProjectQueueStatsMonitoring -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPProjectQueueStatsMonitoring - -## SYNOPSIS -Enables monitoring Project Server queue statistics. - -## SYNTAX - -``` -Enable-SPProjectQueueStatsMonitoring [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Enables monitoring Project Server queue statistics. - -## EXAMPLES - -### Example 1 -``` -Enable-SPProjectQueueStatsMonitoring -``` - -Enables monitoring Project Server queue statistics. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPSessionStateService.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPSessionStateService.md deleted file mode 100644 index 4aa92b6a8e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPSessionStateService.md +++ /dev/null @@ -1,215 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spsessionstateservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPSessionStateService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPSessionStateService - -## SYNOPSIS -Creates a session state database and turns on the session state service. - -## SYNTAX - -### AdvancedProvision -``` -Enable-SPSessionStateService -DatabaseName <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DatabaseCredentials <PSCredential>] [-DatabaseServer <String>] [-SessionTimeout <Int32>] [-WhatIf] - [<CommonParameters>] -``` - -### DefaultProvision -``` -Enable-SPSessionStateService [-DefaultProvision] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SessionTimeout <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Enable-SPSessionStateService cmdlet creates a session state database, installs the ASP.NET session state schema, and updates the Web.config files on the farm to turn on the session state service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Enable-SPSessionStateService -DefaultProvision -``` - -This example enables a ASP.NET session state on a SharePoint Server farm that uses the defaults (database hosted on the configuration database SQL Server, using Windows authentication, 60-minute session time-out). - -### --------------EXAMPLE 2----------------- -``` -Enable-SPSessionStateService -DatabaseName "Session State Database" -DatabaseServer "localhost" -SessionTimeout 120 -``` - -This example enables a ASP.NET session state on a SharePoint Server farm that uses a custom database name, database server, session time-out of 120 minutes, and Windows credentials (due to the lack of a DatabaseCredentials parameter). - -## PARAMETERS - -### -DatabaseName -Specifies the name of the database for the session state service. - -The type must be a valid name of a SQL Server database; for example, SessionStateDB1. - -```yaml -Type: String -Parameter Sets: AdvancedProvision -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProvision -Specifies that the default provisioning settings are used. -The default provisioning settings are: Windows Authentication, Auto SQL Server (configuration database), and Auto Catalog Name. - -```yaml -Type: SwitchParameter -Parameter Sets: DefaultProvision -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the database credentials for SQL Authentication used to access the session state service database. -If this parameter is not specified, Windows authentication is used. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: AdvancedProvision -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the host SQL Server for the state service database. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: AdvancedProvision -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionTimeout -Specifies the time, in minutes, that a ASP .NET session state service will remain active with no user activity. -The default value is 60. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPTimerJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPTimerJob.md deleted file mode 100644 index 0ad95d1c65..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPTimerJob.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-sptimerjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPTimerJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPTimerJob - -## SYNOPSIS - -Enables a timer job. - - - -## SYNTAX - -``` -Enable-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Enable-SPTimerJob cmdlet enables a timer job. -A timer job must be enabled before it can be started. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE--------------------- -``` -Get-SPTimerJob job-ceip-datacollection | Enable-SPTimerJob -``` - -This example enables the timer job named job-ceip-datacollection. - -## PARAMETERS - -### -Identity -Specifies the timer job to enable. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a timer job (for example, TimerJob1); or an instance of a valid SPTimerJob object. - -```yaml -Type: SPTimerJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPUserLicensing.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPUserLicensing.md deleted file mode 100644 index 1130fc0806..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPUserLicensing.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spuserlicensing -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPUserLicensing -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPUserLicensing - -## SYNOPSIS - -Enables user-license enforcement. - - - -## SYNTAX - -``` -Enable-SPUserLicensing [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Enable-SPUserLicensing cmdlet enables user-license enforcement on the SharePoint farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE------------------ -``` -Enable-SPUserLicensing -``` - -This example enables user-license enforcement on the SharePoint farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPUserSolutionAllowList.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPUserSolutionAllowList.md deleted file mode 100644 index b1748c6002..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPUserSolutionAllowList.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spusersolutionallowlist -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPUserSolutionAllowList -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPUserSolutionAllowList - -## SYNOPSIS -Enables the user managed solutions gallery capability on the farm. - -## SYNTAX - -``` -Enable-SPUserSolutionAllowList [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Enables the user managed solutions gallery capability on the farm. - -## EXAMPLES - -### Example 1 -``` -Enable-SPUserSolutionAllowList -``` - -This example enables a user managed solutions gallery on the entire farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPWebApplicationHttpThrottling.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPWebApplicationHttpThrottling.md deleted file mode 100644 index 98535ed0e5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPWebApplicationHttpThrottling.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spwebapplicationhttpthrottling -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPWebApplicationHttpThrottling -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPWebApplicationHttpThrottling - -## SYNOPSIS - -Turns on network throttling for a Web application. - - - -## SYNTAX - -``` -Enable-SPWebApplicationHttpThrottling [-Identity] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Enable-SPWebApplicationHttpThrottling cmdlet turns on network throttling for a Web application. -This operation prompts you to confirm that you want to turn on network throttling. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Enable-SPWebApplicationHttpThrottling https://sitename -``` - -This example enables network throttling on the https://sitename Web application. - -## PARAMETERS - -### -Identity -Turns on network throttling on the specified SharePoint Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPWebTemplateForSiteMaster.md b/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPWebTemplateForSiteMaster.md deleted file mode 100644 index 66c2fee860..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Enable-SPWebTemplateForSiteMaster.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/enable-spwebtemplateforsitemaster -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Enable-SPWebTemplateForSiteMaster -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Enable-SPWebTemplateForSiteMaster - -## SYNOPSIS -Creates a template for a site master. - -## SYNTAX - -``` -Enable-SPWebTemplateForSiteMaster [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <Int32>] -Template <SPWebTemplatePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Enable-SPWebTemplateEnabledForSiteMaster cmdlet to create a site master in the database. - -## EXAMPLES - -### Example 1 -``` -Enable-SPWebTemplateForSiteMaster -Template STS#0 -CompatibilityLevel 15 -``` - -This example creates a site master in the database using the Team Site template. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. This value sets the initial CompatibilityLevel value for the site collection. - -When this parameter is not specified, the CompatibilityLevel parameter will default to the highest possible version for the web application depending on the SiteCreationMode setting. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the name of the template. For example, SPSPERS#2. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPAccessServicesDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPAccessServicesDatabase.md deleted file mode 100644 index c4f72972c0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPAccessServicesDatabase.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spaccessservicesdatabase -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPAccessServicesDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPAccessServicesDatabase - -## SYNOPSIS -Exports an Access Services Database to a DACPAC via the Data-Tier Framework. - -## SYNTAX - -``` -Export-SPAccessServicesDatabase [-AssignmentCollection <SPAssignmentCollection>] -DatabaseName <String> - -ServerReferenceId <Guid> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet exports an Access Services Database to a DACPAC. The cmdlet requires the Data-Tier Framework to be installed on the SharePoint server where the cmdlet is run. The Data-Tier Framework packages can be found at [Microsoft® SQL Server® Data-Tier Application Framework (17.4.1 GA DacFx)](https://www.microsoft.com/en-us/download/details.aspx?id=56508). Install the following MSI from the download: - -EN\x86\DacFramework.msi - -Note: The x86 package is required. The x64 package is not compatible with this cmdlet. - -See more information about Data-Tier Framework at [Data-tier Applications](https://docs.microsoft.com/sql/relational-databases/data-tier-applications/data-tier-applications). - -## EXAMPLES - -### Example 1 -``` -$contentdb = Get-SPContentDatabase ContentDbName -$accessDb = Get-SPAccessServicesDatabase -ContentDb $contentdb -EA 0 | Select -First 1 -Export-SPAccessServicesDatabase -DatabaseName $accessDb.DatabaseName -ServerReferenceId $accessDb.ServerReferenceId | Set-Content -Path C:\accessDb.bacpac -Encoding Byte -``` - -This cmdlet retrieves the first Access Database from the specified Content Database and exports the Access Database to a BACPAC. This BACPAC file can then be imported via SQL Server Management Studio to restore the Access Database. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseName -The name of the Access Database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServerReferenceId -The ServerReferenceId used for the Access Database. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -System.Guid -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPAppPackage.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPAppPackage.md deleted file mode 100644 index 2f67c76297..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPAppPackage.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spapppackage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPAppPackage -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPAppPackage - -## SYNOPSIS - -Exports an app package. - -## SYNTAX - -``` -Export-SPAppPackage -App <SPApp> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Export-SPAppPackage cmdlet to export an app package from the content database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------- -``` -C:\PS>$instance = Get-SPAppInstance -AppInstanceId $instance.Id -Export-SPAppPackage -App $instance.App -Path .\exported.spapp -``` - -This example exports an app package to the \exported.spapp location. - -## PARAMETERS - -### -App -Specifies the App for which to export the package. - -```yaml -Type: SPApp -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Specifies the path of the exported file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Import-SPAppPackage](Import-SPAppPackage.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPBusinessDataCatalogModel.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPBusinessDataCatalogModel.md deleted file mode 100644 index ec877aa18e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPBusinessDataCatalogModel.md +++ /dev/null @@ -1,234 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spbusinessdatacatalogmodel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPBusinessDataCatalogModel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPBusinessDataCatalogModel - -## SYNOPSIS - -Exports a Business Data Connectivity Model. - - - -## SYNTAX - -``` -Export-SPBusinessDataCatalogModel -Identity <MetadataObject> -Path <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Force] [-LocalizedNamesIncluded] [-ModelsIncluded] - [-PermissionsIncluded] [-PropertiesIncluded] [-ProxiesIncluded] [-SettingId <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-SPBusinessDataCatalogModel cmdlet exports a Business Data Connectivity Model. -There are two types of Business Data Connectivity models: Model type (.bdcm) and Resource type (.bdcr). -The Model type contains the base XML metadata, and can also include resource properties. -The Resource type includes only resource properties. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$Model = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Model" -Name "ContosoModel" -ServiceContext http://contoso -Export-SPBusinessDataCatalogModel -Identity $Model -Path "C:\folder\model.bdcm" -``` - -This example gets a Business Data Connectivity Model from the Business Data Connectivity Metadata Store and exports it to the location specified with the name model and using the bdcm file extension. - -## PARAMETERS - -### -Identity -Specifies the Business Data Connectivity Metadata Store metadata object from which to export the Business Data Connectivity Model. - -```yaml -Type: MetadataObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the path and name to use to create the export file. - -The type must be a valid path in either of the following forms: - -- C:\folder_name \file.bdcm -- \\\\server_name\folder_name \file.bdcm -- ...\folder_name\file.bdcm - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Force -Overwrites the output file if the file exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalizedNamesIncluded -Specifies that names for business data fields in multiple languages are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModelsIncluded -Specifies that models are included in the exported Business Data Connectivity Model file. -A model contains the base XML metadata for a system. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionsIncluded -Specifies that permissions from the Business Data Connectivity Model are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertiesIncluded -Specifies that properties from the application definition are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProxiesIncluded -Specifies that proxies for Business Data Connectivity Service applications are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SettingId -Specifies the custom environment settings model slice to export. - -The type must be a valid string that identifies a model slice; for example, ModelSlice1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPEnterpriseSearchTopology.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPEnterpriseSearchTopology.md deleted file mode 100644 index 9899728ce8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPEnterpriseSearchTopology.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spenterprisesearchtopology -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPEnterpriseSearchTopology -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPEnterpriseSearchTopology - -## SYNOPSIS -Saves an existing search topology. - -## SYNTAX - -``` -Export-SPEnterpriseSearchTopology -Filename <String> -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-SPEnterpriseSearchTopology cmdlet exports the topology for a shared search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Export-SPEnterpriseSearchTopology -SearchApplication $ssa -Filename topology.xml -``` - -This example exports the topology to a file named topology.xml in the search service application referenced by $ssa. - -## PARAMETERS - -### -Filename -Specifies the path and file name to use to create the topology XML file. - -The type must be a valid path, in the form MyFeature\Feature.xml. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application with the topology to export. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchTopology](New-SPEnterpriseSearchTopology.md) - -[Get-SPEnterpriseSearchTopology](Get-SPEnterpriseSearchTopology.md) - -[Set-SPEnterpriseSearchTopology](Set-SPEnterpriseSearchTopology.md) - -[Remove-SPEnterpriseSearchTopology](Remove-SPEnterpriseSearchTopology.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPInfoPathAdministrationFiles.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPInfoPathAdministrationFiles.md deleted file mode 100644 index 80ec9206e8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPInfoPathAdministrationFiles.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spinfopathadministrationfiles -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPInfoPathAdministrationFiles -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPInfoPathAdministrationFiles - -## SYNOPSIS -Saves InfoPath form templates on the SharePoint Central Administration Web site and .udcx files to a .cab file. - -## SYNTAX - -``` -Export-SPInfoPathAdministrationFiles [-Path] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Identity <SPFormsServicePipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-SPInfoPathAdministrationFiles cmdlet saves all InfoPath form templates (.xsn files) and universal data connections (.udcx files) that are located on the Central Administration page. -The backup package includes all workflow forms in InfoPath that were deployed by an administrator and not included with SharePoint Server, and includes browser forms that were deployed by an administrator. -The backup package is output to the specified .cab file. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Export-SPInfoPathAdministrationFiles -path d:\file.cab -``` - -This example saves all InfoPath form templates (.xsn files) and universal data connections (.udcx files) located on the SharePoint Central Administration Web site in a compressed cabinet file named file.cab. - -## PARAMETERS - -### -Path -Specifies the location and name of the output .cab file. - -The type must be a valid file path, in the form \\\\ipadmin\folder\backups1\ipfsfiles.cab. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the site collection that contains the InfoPath form template and Central Administration .udcx files to export. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPFormsServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPMetadataWebServicePartitionData.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPMetadataWebServicePartitionData.md deleted file mode 100644 index bda365a1c8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPMetadataWebServicePartitionData.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spmetadatawebservicepartitiondata -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPMetadataWebServicePartitionData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPMetadataWebServicePartitionData - -## SYNOPSIS -Exports the data from a metadata Web service for a site subscription. - -## SYNTAX - -``` -Export-SPMetadataWebServicePartitionData [-Identity] <SPSiteSubscriptionPipeBind> - [-ServiceProxy] <SPMetadataServiceProxyCmdletPipeBind> -Path <String> - [-AssignmentCollection <SPAssignmentCollection>] [-NoCompression] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Export-SPMetadataWebServicePartitionData cmdlet to export the data from a metadata Web service that is associated with the specified site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE-------------- -``` -Export-SPMetadataWebServicePartitionData -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -Path "\\server_name\folder_name\file_name.cab" -``` - -This example creates a backup of data for a specific site subscription on a Metadata Service application. - -## PARAMETERS - -### -Identity -Specifies the site subscription to export. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscriptionConfig1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceProxy -Specifies the service proxy for the service application that contains the site subscription. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of the service application proxy (for example, ServiceAppProxy1); or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the path and file name for the file to create from the exported data. - -The type must be a valid path in either of the following forms: - -- C:\folder_name\subscription_export -- \\\\server_name\folder_name\file_name.cab - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NoCompression -{{Fill NoCompression Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPPerformancePointContent.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPPerformancePointContent.md deleted file mode 100644 index 9b95448125..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPPerformancePointContent.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spperformancepointcontent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPPerformancePointContent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPPerformancePointContent - -## SYNOPSIS -Exports a Performance Point Server (PPS) dashboard. - -## SYNTAX - -``` -Export-SPPerformancePointContent [-AssignmentCollection <SPAssignmentCollection>] -ExportFileUrl <String> - -ItemUrls <Array> [<CommonParameters>] -``` - -## DESCRIPTION -The Export-SPPerformancePointContent exports a PPS dashboard and its dependencies from a CMP file that can then be used to import to another server. - -## EXAMPLES - -### Example 1 -``` -Export-SPPerformancePointContent -ItemUrls https://contoso/sites/marketing/default.aspx -ExportFileURL "https://contoso/bicenter/SharedDocuments/bi/dashboard1.cmp" -``` - -This example exports a dashboard at the location specified with the ItemUrls parameter. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExportFileUrl -Output name and path of the CMP file to which the data will be stored. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ItemUrls -The URL to the dashboard to be migrated or to the additional content URLs. - -```yaml -Type: Array -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPScaleOutDatabaseTenantData.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPScaleOutDatabaseTenantData.md deleted file mode 100644 index cbe817ab2f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPScaleOutDatabaseTenantData.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spscaleoutdatabasetenantdata -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPScaleOutDatabaseTenantData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPScaleOutDatabaseTenantData - -## SYNOPSIS - -Exports the data of the specified subscription. - - - -## SYNTAX - -``` -Export-SPScaleOutDatabaseTenantData -FilePath <String> -ServiceApplication <SPServiceApplicationPipeBind> - -SiteSubscriptionId <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Export-SPScaleOutDatabaseTenantData cmdlet to export the data of the specified subscription id to the specified file from the specified service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE------- -``` -Export-SPScaleOutDatabaseTenantData -FilePath "C:\TenantData.dat" -ServiceApplication $serviceApplication -SiteSubscriptionId "5CAF2F99-A75F-4239-B9CD-7FE63D1CE904" -``` - -This example exports data for the site subscription with id 5CAF2F99-A75F-4239-B9CD-7FE63D1CE904 to the file at C:\ TenantData.dat, from the specified service application. - -## PARAMETERS - -### -FilePath -Specifies the output path for the file to export the data to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the service application to export the data from. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptionId -Specifies the site subscription id of the site subscription to export the data from. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overwrites an existing data file without prompting for confirmation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-SPScaleOutDatabaseTenantData](Clear-SPScaleOutDatabaseTenantData.md) - -[Import-SPScaleOutDatabaseTenantData](Import-SPScaleOutDatabaseTenantData.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPServerScaleOutDatabaseTenantData.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPServerScaleOutDatabaseTenantData.md deleted file mode 100644 index 9f45a3d5d2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPServerScaleOutDatabaseTenantData.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spserverscaleoutdatabasetenantdata -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPServerScaleOutDatabaseTenantData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPServerScaleOutDatabaseTenantData - -## SYNOPSIS - -Exports the data of the specified subscription. - -## SYNTAX - -``` -Export-SPServerScaleOutDatabaseTenantData [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -FilePath <String> [-Force] -ServiceApplication <SPServiceApplicationPipeBind> -SiteSubscriptionId <Guid> - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Export-SPServerScaleOutDatabaseTenantData cmdlet to export the data of the specified subscription id to the specified file from the specified service application. - - -## EXAMPLES - -### ----------EXAMPLE------- -``` -Export-SPServerScaleOutDatabaseTenantData -FilePath "C:\TenantData.dat" -ServiceApplication $serviceApplication -SiteSubscriptionId "5CAF2F99-A75F-4239-B9CD-7FE63D1CE904" -``` - -This example exports data for the site subscription with id 5CAF2F99-A75F-4239-B9CD-7FE63D1CE904 to the file at C:\ TenantData.dat, from the specified service application. - -## PARAMETERS - -### -AssignmentCollection -{{Fill AssignmentCollection Description}} - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilePath -{{Fill FilePath Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{Fill Force Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -{{Fill ServiceApplication Description}} - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptionId -{{Fill SiteSubscriptionId Description}} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Clear-SPServerScaleOutDatabaseTenantData](Clear-SPServerScaleOutDatabaseTenantData.md) - -[Import-SPServerScaleOutDatabaseTenantData](Import-SPServerScaleOutDatabaseTenantData.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPSiteSubscriptionBusinessDataCatalogConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPSiteSubscriptionBusinessDataCatalogConfig.md deleted file mode 100644 index 800a537db4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPSiteSubscriptionBusinessDataCatalogConfig.md +++ /dev/null @@ -1,248 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spsitesubscriptionbusinessdatacatalogconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPSiteSubscriptionBusinessDataCatalogConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPSiteSubscriptionBusinessDataCatalogConfig - -## SYNOPSIS - -Exports all data from the Business Data Connectivity Metadata Store associated with a partition. - - - -## SYNTAX - -``` -Export-SPSiteSubscriptionBusinessDataCatalogConfig -Path <String> -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-LocalizedNamesIncluded] - [-ModelsIncluded] [-PermissionsIncluded] [-PropertiesIncluded] [-ProxiesIncluded] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The SPSiteSubscriptionBusinessDataCatalogConfig cmdlet exports all data from the Business Data Connectivity Metadata Store associated with a specified partition. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Export-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext http://contoso -Path "C:\folder\exportedFile.xml" -``` - -This example exports the data file named exportedFile.xml. - -## PARAMETERS - -### -Path -Specifies the path and name to use to create the export file. - -The type must be a valid path in either of the following forms: - -- C:\folder_name\file.xml -- \\\\server_name\folder_name\file.xml -- ...\folder_name\file.xml - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context of the data to be exported. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service context (for example, http://ServiceContext1); or an instance of a valid SPServiceContext object. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overwrites the output file if the file exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalizedNamesIncluded -Specifies that names for business data fields in multiple languages are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModelsIncluded -Specifies that Business Data Connectivity models are included in the exported file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionsIncluded -Specifies that permissions from the Business Data Connectivity Models are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertiesIncluded -Specifies that properties from the Business Data Connectivity Models are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProxiesIncluded -Specifies that proxies for Business Data Connectivity Service applications are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPSiteSubscriptionSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPSiteSubscriptionSettings.md deleted file mode 100644 index edbc0881dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPSiteSubscriptionSettings.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spsitesubscriptionsettings -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPSiteSubscriptionSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPSiteSubscriptionSettings - -## SYNOPSIS - -Creates a backup file of site subscription data. - - - -## SYNTAX - -``` -Export-SPSiteSubscriptionSettings [-Identity] <SPSiteSubscriptionPipeBind> -Path <String> [-AdminProperties] - [-AssignmentCollection <SPAssignmentCollection>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-SPSiteSubscriptionSettings cmdlet generates a backup file of all settings in the subscription data store for the given site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Export-SPSiteSubscriptionSettings -Identity "https://sitecollection/" -Path "C:\siteCollection_sitesubscriptionsettings.txt" -``` - -The example backs up the subscription settings store of https://siteCollection. - - -### --------------EXAMPLE 2----------------- -``` -C:\PS>$site = Get-SPSite https://siteCollection -Export-SPSiteSubscriptionSettings -Identity $site.SiteSubscription -Path "C:\siteCollection_sitesubscriptionsettings.txt" -``` - -The example backs up the subscription settings store of https://siteCollection using the Site Subscription object. - -## PARAMETERS - -### -Identity -Specifies the ID of the site subscription from which to back up data. - -The type must be a valid URL, in the form https://server_name or a Site Subscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the location of the output file. - -The type must be a valid path; for example, C:/backupfile.back.. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminProperties -Specifies that only administrator subscription properties are exported. -If this parameter is not set, only non-administrator subscription properties are exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Force -Forces the output backup file (if provided) to overwrite any existing file at the given path. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPTagsAndNotesData.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPTagsAndNotesData.md deleted file mode 100644 index dfaf38176b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPTagsAndNotesData.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-sptagsandnotesdata -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPTagsAndNotesData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPTagsAndNotesData - -## SYNOPSIS -Exports the SharePoint Newsfeed tags and notes from the SharePoint database to a ZIP file. - -## SYNTAX - -``` -Export-SPTagsAndNotesData [-Site] <SPSitePipeBind> [-FilePath] <String> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-SPTagsAndNotesData cmdlet exports the SharePoint Newsfeed tags and notes from the SharePoint database. -The tags and notes are written into separate files, and then the two are compressed and added to the ZIP file you specify. - -## EXAMPLES - -### ----------------EXAMPLE----------------- -``` -Export-SPTagsAndNotesData -Site https://site.contoso.com -FilePath C:\TagsAndNotes.zip -``` - -This example creates a new ZIP file called TagsAndNotes.zip, on the root of C: drive, exports tags and notes from the SharePoint database for the site https://site.contoso.com, and adds the resulting files to the TagsAndNotes.zip file - -## PARAMETERS - -### -Site -URL of the root site where you want to export the tags and notes from. - -You must specify a valid URL to an existing SharePoint root site. -For example: https://site.contoso.com - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -FilePath -File name, including full path, that you want export the tags and notes to. - -The cmdlet will create a new ZIP file with the name you specified. -If the file already exists, the cmdlet won't perform the export and will ask you to specify a new file name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -{{Fill AssignmentCollection Description}} - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Export-SPWeb.md deleted file mode 100644 index 2b2501a584..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Export-SPWeb.md +++ /dev/null @@ -1,375 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/export-spweb -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Export-SPWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Export-SPWeb - -## SYNOPSIS - -Exports a site, list, or library. - - - -## SYNTAX - -``` -Export-SPWeb [-Identity] <SPWebPipeBind> -Path <String> [-AppLogFilePath <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-CompressionSize <Int32>] [-Confirm] [-Force] [-HaltOnError] - [-HaltOnWarning] [-IncludeUserSecurity] [-IncludeVersions <SPIncludeVersions>] [-ItemUrl <String>] - [-NoFileCompression] [-NoLogFile] [-UseSqlSnapshot] [-WhatIf] [-IncludeAlerts] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-SPWeb cmdlet exports a site, list, or library. -The capability to export from a library is a new feature in SharePoint. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE-----------------------. -``` -Export-SPWeb https://site -Path "C:\Temp\export.cmp" -``` - -This example exports the site at https://site/ to a file called site export.cmp in the current directory. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the Web to be exported. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint site (for example, MySPSite1); or an instance of a valid SPWeb object. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the name of the export file. - -If the NoFileCompression parameter is used, a directory must be specified; otherwise, any file format is valid. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AppLogFilePath -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompressionSize -Sets the maximum file size for the compressed export files. -If the total size of the exported package is greater than this size, the exported package will be split into multiple files. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forcefully overwrites the export package if it already exists. - -The type must be either of the following values: - --True - --False - -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HaltOnError -Stops the export process when an error occurs. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HaltOnWarning -Stops the export process when a warning occurs. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeUserSecurity - -Preserves the user security settings. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeVersions -Indicates the type of file and list item version history to be included in the export operation. -If the IncludeVersions parameter is absent, the Export-SPWeb cmdlet by default uses a value of 1. - -The type must be any one of the following versions: - --Last major version for files and list items (default) - --The current version, either the last major version or the last minor version - --Last major and last minor version for files and list items - --All versions for files and list items - -Valid values are: - -All, CurrentVersion, LastMajor, LastMajorAndMinor - -```yaml -Type: SPIncludeVersions -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ItemUrl -Specifies the URL of the Web application, GUID, or object to be exported. - -The type must be a valid URL; for example, https://server_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoFileCompression -Either enables or disables file compression in the export package. -The export package is stored in the folder specified by the Path parameter or Identity parameter. -We recommend that you use this parameter for performance reasons. -If compression is enabled, the export process can increase by approximately 30 percent. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile -Suppresses the generation of an export log file. -If this parameter is not specified, the Export-SPWeb cmdlet will generate an export log file in the same location as the export package. -The log file uses Unified Logging Service (ULS). - -It is recommended to use this parameter. -However, for performance reasons, you might not want to generate a log file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseSqlSnapshot -Specifies a SQL Database Snapshot will be created when the export process begins, and all exported data will be retrieved directly from the database snapshot. -This snapshot will be automatically deleted when export completes. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeAlerts -Indicates if alerts are turned on. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-AvailabilityGroupStatus.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-AvailabilityGroupStatus.md deleted file mode 100644 index d819526090..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-AvailabilityGroupStatus.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-availabilitygroupstatus -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-AvailabilityGroupStatus -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-AvailabilityGroupStatus - -## SYNOPSIS -Returns one or more objects representing the availability groups known to the SharePoint farm. - -## SYNTAX - -``` -Get-AvailabilityGroupStatus [-AssignmentCollection <SPAssignmentCollection>] [-Identity <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Returns one or more objects representing the availability groups known to the SharePoint farm. - -## EXAMPLES - -### Example 1 -``` -Get-AvailabilityGroupStatus -Identity MyAvailabilityGroup - -``` - -This example returns an availability group named "MyAvailabilityGroup". - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -NOTE: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Finds the availability group whose name property matches this string. Otherwise, returns all availability groups. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchContentCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchContentCollection.md deleted file mode 100644 index 1501c30a0c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchContentCollection.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchcontentcollection -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchContentCollection ---- - -# Get-FASTSearchContentCollection - -## SYNOPSIS -Retrieves Microsoft FAST Search Server 2010 for SharePoint content collections. - -## SYNTAX - -``` -Get-FASTSearchContentCollection [[-Name] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves all FAST Search Server 2010 for SharePoint content collections. -When a collection name is specified, a single collection is retrieved, if it exists. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchContentCollection -``` - -This example retrieves all FAST Search Server 2010 for SharePoint content collections. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchContentCollection -Name newscollection -``` - -This example retrieves the "newscollection" content collection. - -## PARAMETERS - -### -Name -The name of the FAST Search Server 2010 for SharePoint collection to retrieve. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-FASTSearchContentCollection](Clear-FASTSearchContentCollection.md) - -[New-FASTSearchContentCollection](New-FASTSearchContentCollection.md) - -[Remove-FASTSearchContentCollection](Remove-FASTSearchContentCollection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchDocumentProcessingPipeline.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchDocumentProcessingPipeline.md deleted file mode 100644 index 4ab3c9f3b2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchDocumentProcessingPipeline.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchdocumentprocessingpipeline -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchDocumentProcessingPipeline ---- - -# Get-FASTSearchDocumentProcessingPipeline - -## SYNOPSIS -Retrieves FAST Search Server 2010 for SharePoint document processing pipelines. - -## SYNTAX - -``` -Get-FASTSearchDocumentProcessingPipeline [[-Name] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -A document processing pipeline consists of multiple processing stages that an item goes through before being indexed for searching. -Item processing includes adding/removing/modifying metadata, linguistic processing, language detection. -This cmdlet retrieves all FAST Search Server 2010 for SharePoint document processing pipelines. -When one pipeline name is specified, a single pipeline is retrieved if it exists. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchDocumentProcessingPipeline -``` - -This example retrieves all FAST Search Server 2010 for SharePoint document processing pipelines. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchDocumentProcessingPipeline -Name "Office14 (webcluster)" -``` - -This example retrieves a single FAST Search Server 2010 for SharePoint document processing pipeline named "Office14 (webcluster)". - -## PARAMETERS - -### -Name -The name of the document processing pipeline to retrieve. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCategory.md deleted file mode 100644 index e6e2b12015..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCategory.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchmetadatacategory -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchMetadataCategory ---- - -# Get-FASTSearchMetadataCategory - -## SYNOPSIS -Retrieves a crawled property category. - -## SYNTAX - -``` -Get-FASTSearchMetadataCategory [[-Name] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a category object from the installation. -If no name is specified, it retrieves all categories in the system. - -A category contains several crawled properties that are grouped together for setting properties that are common to them all. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchMetadataCategory -``` - -This example returns all available categories. -This is the default behavior if you do not specify any parameters. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchMetadataCategory -Name SharePoint -``` - -This example returns one specific category, the "SharePoint" category. - -### ---------------EXAMPLE 3----------------- -``` -Get-FASTSearchMetadataCategory -Name m* -``` - -This example returns all categories with a name that begins with "m". -Matching is case-insensitive. - -### ---------------EXAMPLE 4----------------- -``` -$category = Get-FASTSearchMetadataCategory -Name "Enterprise Crawler" -$category.GetAllCrawledProperties()|ForEach-Object {$_.Name} -``` - -This example returns all crawled properties that are mapped to the category named "Enterprise Crawler". -The example first retrieves the category, and then calls the category's GetAllCrawledProperties() function to list its crawled properties. -It then iterates over the list of crawled properties and selects the name of each crawled property. - -## PARAMETERS - -### -Name -The name of the category to retrieve. -If no category is specified, all categories are returned. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: CategoryName, N -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-FASTSearchMetadataCategory](Remove-FASTSearchMetadataCategory.md) - -[Set-FASTSearchMetadataCategory](Set-FASTSearchMetadataCategory.md) - -[New-FASTSearchMetadataCategory](New-FASTSearchMetadataCategory.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCrawledProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCrawledProperty.md deleted file mode 100644 index 7bbfbabe29..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCrawledProperty.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchmetadatacrawledproperty -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchMetadataCrawledProperty ---- - -# Get-FASTSearchMetadataCrawledProperty - -## SYNOPSIS -Retrieves a crawled property from Microsoft FAST Search Server 2010 for SharePoint. - -## SYNTAX - -``` -Get-FASTSearchMetadataCrawledProperty [[-Name] <String>] [-Count <Int32>] [-Filter <String>] [-Offset <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a crawled property from the FAST Search Server 2010 for SharePoint system. -If the cmdlet is called without any parameters, it returns all crawled properties in the system. -The order of the returned crawled property list is fixed, and multiple calls return the same ordered list as long as no new crawled properties have been added. - -Get-FASTSearchMetadataCrawledProperty supports several ways of looking up properties. -Run with a single parameter or with a named parameter (using Name), the cmdlet retrieves crawled properties with that exact name, if any exist. -The Name parameter supports wildcards. -Alternatively, a filter can be specified (using the Filter parameter) to search the crawled properties and to return any crawled property with a name that includes the filter value. -The filter option does not support wildcards. - -Retrieving crawled properties with the Filter parameter is much more efficient than using the Name parameter. - -To paginate a set of results from this cmdlet, use an Offset and Count to control the number of returned results. - -Offset and Count are calculated before either filter or named matching is done. -This means that if a crawled property falls outside the \[Offset,Offset+Count\] range, it will not be returned. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchMetadataCrawledProperty -``` - -Calling Get-FASTSearchMetadataCrawledProperty without any parameters returns all known crawled properties in the FAST Search Server 2010 for SharePoint system. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchMetadataCrawledProperty -Name viewurl -``` - -This example retrieves a crawled property with the exact name "viewurl". - -### ---------------EXAMPLE 3----------------- -``` -Get-FASTSearchMetadataCrawledProperty -filter 4 -``` - -This example retrieves and returns any crawled property that includes a "4" in its name. - -### ---------------EXAMPLE 4----------------- -``` -Get-FASTSearchMetadataCrawledproperty -filter url -count 2 -``` - -This example retrieves the first two crawled properties with the name "url". - -### ---------------EXAMPLE 5----------------- -``` -Get-FASTSearchMetadataCrawledproperty |ForEach-Object{ if ($_.IsMappedToContents) {$_.Name} } -``` - -This example returns the names of all crawled properties that have the IsMappedToContents parameter set to "true". -The example first retrieves all configured crawled properties, and then iterates over them to find those with IsMappedToContents set to "true" - -### ---------------EXAMPLE 6----------------- -``` -Get-FASTSearchMetadataCrawledproperty -offset 0 -count 2 -Get-FASTSearchMetadataCrawledproperty -offset 2 -count 2 -Get-FASTSearchMetadataCrawledproperty -offset 4 -count 2 -``` - -This example generates a list of two crawled properties each time the cmdlet is run. -The Offset is increased by the Count value to start returning crawled properties where the last run ended. - -### ---------------EXAMPLE 7----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchMetadataCrawledProperty -filter url| where-object {($_.Name -eq "url") -and ($_.VariantType -eq 31) -and ($_.Propset -eq "63e90878-0292-490d-8b7c-f3905a8b65fd")} -``` - -This example lists all potential matches to a named crawled property, and then selects the exact crawled property by iterating over the result set and picking out the result that also matches both the requested property set and variant type. -The command returns the "url" crawled property in the "Enterprise Crawler" category. - -## PARAMETERS - -### -Name -The name of crawled property to retrieve. - -The Name parameter supports wildcards. -Combine the Name parameter with the Offset and Count parameters to control the range that is searched. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Count -The maximum number of crawled properties to return (starting from the first returned crawled property, or from the index given by the Offset parameter). - -If the Filter or Name parameter is specified, these will only be applied after the result set has been narrowed down to the range \[Offset, Offset + Count\]. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -The term used to search for configured crawled properties. - -The Filter parameter does not support wildcards. -Matching is case-insensitive, and matches a string anywhere within the name attribute of the crawled property. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Offset -The offset in the result set from which to start returning results. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataCrawledProperty](New-FASTSearchMetadataCrawledProperty.md) - -[Set-FASTSearchMetadataCrawledProperty](Set-FASTSearchMetadataCrawledProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCrawledPropertyMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCrawledPropertyMapping.md deleted file mode 100644 index 3a1fc81d4a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataCrawledPropertyMapping.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchmetadatacrawledpropertymapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchMetadataCrawledPropertyMapping ---- - -# Get-FASTSearchMetadataCrawledPropertyMapping - -## SYNOPSIS -Retrieves a list of crawled properties mapped to a managed property. - -## SYNTAX - -### Name -``` -Get-FASTSearchMetadataCrawledPropertyMapping [-Name] <String> [<CommonParameters>] -``` - -### ManagedProperty -``` -Get-FASTSearchMetadataCrawledPropertyMapping -ManagedProperty <ManagedProperty> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a list of the crawled properties that are mapped to a managed property. -The managed property can be specified with the Name parameter or by a ManagedPropertyImpl object as returned by Get-FASTSearchMetadataManagedProperty (using the ManagedProperty parameter). - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -C:\PS>Get-FASTSearchMetadataCrawledPropertyMapping -Name title -``` - -This example returns a list of crawled properties that are mapped to the managed property named "title". - -### ---------------EXAMPLE 2----------------- -``` -$managedproperty = Get-FASTSearchMetadataManagedProperty -name title -Get-FASTSearchMetadataCrawledPropertyMapping -ManagedProperty $managedproperty -``` - -This example first retrieves a ManagedPropertyImpl object, and then uses it to look up the corresponding crawled property mappings. -It returns all crawled properties that are set up to map content into this managed property. - -### ---------------EXAMPLE 3----------------- -``` -$crawledproperty = Get-FASTSearchmetadataCrawledProperty -name title -$crawledproperty.GetMappedManagedProperties() -``` - -These commands are the opposite of Get-FASTSearchMetdataCrawledPropertyMapping; they find all managed properties that have a mapping for a specific crawled property. -This is useful when assessing how modifying a crawled property will impact the search index. - -## PARAMETERS - -### -Name -The name of a managed property for finding crawled properties. - -```yaml -Type: String -Parameter Sets: Name -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ManagedProperty -The managed property object for finding crawled properties. - -```yaml -Type: ManagedProperty -Parameter Sets: ManagedProperty -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataCrawledPropertyMapping](New-FASTSearchMetadataCrawledPropertyMapping.md) - -[Remove-FASTSearchMetadataCrawledPropertyMapping](Remove-FASTSearchMetadataCrawledPropertyMapping.md) - -[Set-FASTSearchMetadataCrawledPropertyMapping](Set-FASTSearchMetadataCrawledPropertyMapping.md) - -[Get-FASTSearchMetadataCrawledProperty](Get-FASTSearchMetadataCrawledProperty.md) - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataFullTextIndex.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataFullTextIndex.md deleted file mode 100644 index c643b8373b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataFullTextIndex.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchmetadatafulltextindex -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchMetadataFullTextIndex ---- - -# Get-FASTSearchMetadataFullTextIndex - -## SYNOPSIS -Retrieves a full text index. - -## SYNTAX - -``` -Get-FASTSearchMetadataFullTextIndex [[-Name] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a full text index object. -The full text indexes are the searchable content of a Microsoft FAST Search Server 2010 for SharePoint system. -Although it is also possible to search on a specific managed property without using a full text index, full relevancy calculation is only done when searching in full text indexes. - -If no name is specified, all full text indexes are retrieved. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchMetadataFullTextIndex -Name content -``` - -This example retrieves the full text index named "content". - -## PARAMETERS - -### -Name -The name of the full text index to retrieve. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: FullTextIndexName, N -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataFullTextIndex](New-FASTSearchMetadataFullTextIndex.md) - -[Remove-FASTSearchMetadataFullTextIndex](Remove-FASTSearchMetadataFullTextIndex.md) - -[Set-FASTSearchMetadataFullTextIndex](Set-FASTSearchMetadataFullTextIndex.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataFullTextIndexMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataFullTextIndexMapping.md deleted file mode 100644 index 08b2d914e5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataFullTextIndexMapping.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchmetadatafulltextindexmapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchMetadataFullTextIndexMapping ---- - -# Get-FASTSearchMetadataFullTextIndexMapping - -## SYNOPSIS -Retrieves mappings between managed properties and the full text indexes. - -## SYNTAX - -``` -Get-FASTSearchMetadataFullTextIndexMapping [-FullTextIndex <FullTextIndex>] - [-ManagedProperty <ManagedProperty>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves mappings from managed properties to full text indexes. -These mappings control which managed properties are included in each full text index. - -Running Get-FASTSearchMetadataFullTextIndexMapping with only a managed property as a parameter (the ManagedProperty parameter) returns all mappings to full text indexes in which the managed property is included. - -Running Get-FASTSearchMetadataFullTextIndexMapping with only a full text index as a parameter (the FullTextIndex parameter) returns all mappings from managed properties that are included in the full text index - -Running Get-FASTSearchMetadataFullTextIndexMapping with both the ManagedProperty and the FullTextIndex parameters returns a single FullTextIndexMappingImpl object for that exact mapping, if it exists in the Microsoft FAST Search Server 2010 for SharePoint system. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -$fulltextindex = Get-FASTSearchMetadataFullTextIndex -name content -Get-FASTSearchMetadataFullTextIndexMapping -fulltextindex $fulltextindex| ForEach-Object {$_.ManagedProperty.Name} -``` - -This example retrieves the full text index mappings for the full text index "content". -It then iterates over the mappings and outputs the names of the managed properties included in the full text index. - -### ---------------EXAMPLE 2----------------- -``` -$title = Get-FASTSearchMetadataManagedProperty -name title -Get-FASTSearchMetadataFullTextIndexMapping -managedproperty $title -``` - -This example retrieves all full text indexes where the managed property named "title" is included. - -The specified managed property is mapped to both "content" and "thirdfulltextindex", showing that there is no limit to how many full text indexes a managed property can be part of. - -## PARAMETERS - -### -FullTextIndex -The full text index specified to retrieve mappings. - -```yaml -Type: FullTextIndex -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ManagedProperty -The managed property specified to retrieve mappings. - -```yaml -Type: ManagedProperty -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataFullTextIndexMapping](New-FASTSearchMetadataFullTextIndexMapping.md) - -[Remove-FASTSearchMetadataFullTextIndexMapping](Remove-FASTSearchMetadataFullTextIndexMapping.md) - -[Set-FASTSearchMetadataFullTextIndexMapping](Set-FASTSearchMetadataFullTextIndexMapping.md) - -[Get-FASTSearchMetadataFullTextIndex](Get-FASTSearchMetadataFullTextIndex.md) - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataManagedProperty.md deleted file mode 100644 index b2e7c52693..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataManagedProperty.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchmetadatamanagedproperty -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchMetadataManagedProperty ---- - -# Get-FASTSearchMetadataManagedProperty - -## SYNOPSIS -Retrieves a managed property with the specified name. - -## SYNTAX - -``` -Get-FASTSearchMetadataManagedProperty [[-Name] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This command retrieves managed properties that match the input parameter. -If wildcards are used, the command may return more than one managed property. - -A managed property is a piece of information (such as title, author, etc.) that is stored for each item in the index. - -See Set-FASTSearchMetadataManagedProperty for details about the managed property parameters and how to configure them. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchMetadataManagedProperty -name title -``` - -This example retrieves a managed property named "title". -It returns an object representing the managed property. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchMetadataManagedProperty -name content* -``` - -This example returns all managed properties with names starting with "content". -It returns a list of managed property objects. - -## PARAMETERS - -### -Name -The name of the managed property to retrieve. -This option supports wildcards, and the matching is case-insensitive. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: ManagedPropertyName, N -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataManagedProperty](New-FASTSearchMetadataManagedProperty.md) - -[Set-FASTSearchMetadataManagedProperty](Set-FASTSearchMetadataManagedProperty.md) - -[Remove-FASTSearchMetadataManagedProperty](Remove-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataRankProfile.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataRankProfile.md deleted file mode 100644 index 284369c3e5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchMetadataRankProfile.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchmetadatarankprofile -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchMetadataRankProfile ---- - -# Get-FASTSearchMetadataRankProfile - -## SYNOPSIS -Retrieves rank profiles from the Microsoft FAST Search Server 2010 for SharePoint system. - -## SYNTAX - -``` -Get-FASTSearchMetadataRankProfile [[-Name] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves rank profiles which match the Name parameter. -A rank profile is a weighting scheme for calculating relevance, specifying how each relevance component should be weighted when calculating an item's relevance. - -See Set-FASTSearchMetadataRankProfile for details about rank profile parameters. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchMetadataRankProfile -Name newdefault -``` - -This example retrieves the rank profile named "newdefault". - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchMetadataRankProfile -Name *?default -``` - -This example retrieves all rank profiles that match the pattern "*?default". -It will not match the default rankprofile named "default". - -## PARAMETERS - -### -Name -The name of the rank profile to retrieve. -This option supports wildcards, and matching is case-insensitive. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: RankProfileName, N -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataRankProfile](New-FASTSearchMetadataRankProfile.md) - -[Remove-FASTSearchMetadataRankProfile](Remove-FASTSearchMetadataRankProfile.md) - -[Set-FASTSearchMetadataRankProfile](Set-FASTSearchMetadataRankProfile.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchResource.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchResource.md deleted file mode 100644 index 511a0195a8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchResource.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchresource -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchResource ---- - -# Get-FASTSearchResource - -## SYNOPSIS -Downloads a resource from the resource store. - -## SYNTAX - -``` -Get-FASTSearchResource [-Path] <String> [-FilePath] <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet downloads a specified file located in the Microsoft FAST Search Server 2010 for SharePoint resource store to the local environment. -The location of the resource store is typically specified in %FASTSEARCH%/etc/Admin.config (where %FASTSEARCH% is the FAST Search Server 2010 for SharePoint installation folder.) - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchResource dictionaries\spellcheck\check_en.aut c:\check_en.aut -``` - -This example downloads dictionaries\spellcheck\check_en.aut from the resource store to c:\check_en.aut. - -## PARAMETERS - -### -Path -Partial URI within the resource store where the file needs to be downloaded from. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: ResourceURI -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilePath -Path to download the resource. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-FASTSearchResource](Remove-FASTSearchResource.md) - -[Add-FASTSearchResource](Add-FASTSearchResource.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSearchSettingGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSearchSettingGroup.md deleted file mode 100644 index 16dc72a41b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSearchSettingGroup.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsearchsettinggroup -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSearchSettingGroup ---- - -# Get-FASTSearchSearchSettingGroup - -## SYNOPSIS -Retrieves Microsoft FAST Search Server 2010 for SharePoint search setting groups. - -## SYNTAX - -``` -Get-FASTSearchSearchSettingGroup [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves one or all FAST Search Server 2010 for SharePoint search setting groups. -When a group name is specified, a single group is retrieved, if it exists. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSearchSettingGroup -``` - -This example retrieves all FAST Search Server 2010 for SharePoint search setting groups. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSearchSettingGroup -Name marketinggroup -``` - -This example retrieves the "marketinggroup" search setting group. - -## PARAMETERS - -### -Name -The name of the search setting group to retrieve. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchSearchSettingGroup](New-FASTSearchSearchSettingGroup.md) - -[Remove-FASTSearchSearchSettingGroup](Remove-FASTSearchSearchSettingGroup.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityAliaser.md deleted file mode 100644 index 3b7d69d8dc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityAliaser.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityAliaser ---- - -# Get-FASTSearchSecurityAliaser - -## SYNOPSIS -Gets a security principal aliaser. - -## SYNTAX - -``` -Get-FASTSearchSecurityAliaser [[-Identity] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet gets a regular expression or XML principal aliaser. -If the Identity parameter is not specified, it gets a list of all aliasers. - -A principal aliaser maps users from one user store into users in other user stores. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityAliaser -``` - -This example gets a list of all XML and regular expression principal aliasers. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityAliaser -Identity xmlalias4 -``` - -This example gets the principal aliaser with the ID "xmlalias4". - -## PARAMETERS - -### -Identity -The identity of a regular expression or XML aliaser to get. - -If not specified, the cmdlet gets a list of all aliasers. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-FASTSearchSecurityAliaser](Remove-FASTSearchSecurityAliaser.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityCCTKServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityCCTKServer.md deleted file mode 100644 index 5494ff2818..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityCCTKServer.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecuritycctkserver -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityCCTKServer ---- - -# Get-FASTSearchSecurityCCTKServer - -## SYNOPSIS -Gets the CCTK server general setting. - -## SYNTAX - -``` -Get-FASTSearchSecurityCCTKServer [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet gets the configuration setting for the server that handles CCTK requests. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityCCTKServer -``` - -This example retrieves the configuration setting for the server that handles CCTK requests. - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityCCTKServer](Set-FASTSearchSecurityCCTKServer.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityClaimsUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityClaimsUserStore.md deleted file mode 100644 index e01a0c2d12..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityClaimsUserStore.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityclaimsuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityClaimsUserStore ---- - -# Get-FASTSearchSecurityClaimsUserStore - -## SYNOPSIS -Get the claims security user store. - -## SYNTAX - -``` -Get-FASTSearchSecurityClaimsUserStore [[-Identity] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a specific claims user store. - -If the Identity parameter is not specified, the cmdlet gets a list of all claims user stores. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityClaimsUserStore -Identity clm -``` - -This example retrieves the claims user store with the identity "clm". - -## PARAMETERS - -### -Identity -The identity of a claims user store to display. - -If an Identity is not specified, all claims user stores are displayed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityClaimsUserStore](Set-FASTSearchSecurityClaimsUserStore.md) - -[New-FASTSearchSecurityClaimsUserStore](New-FASTSearchSecurityClaimsUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityCompleteGroupExpansion.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityCompleteGroupExpansion.md deleted file mode 100644 index 1581ec51d6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityCompleteGroupExpansion.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecuritycompletegroupexpansion -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityCompleteGroupExpansion ---- - -# Get-FASTSearchSecurityCompleteGroupExpansion - -## SYNOPSIS -Gets complete group expansion information for a user. - -## SYNTAX - -``` -Get-FASTSearchSecurityCompleteGroupExpansion [-Identity] <String> [-User] <String> [-ExtraProperties] - [[-XmlFile] <String>] [[-Worker] <WorkerPoolNode>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet gets troubleshooting information for group expansions and aliaser processing performed to create the user search security filter. - -The group expansion information contains the user, expanded groups that contain the user (i.e., the user is a member of the group), and all groups that contain other expanded groups. - -The aliaser procession information contains all mapped to users and groups based on the regular expression and XML aliaser mapping definitions. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityCompleteGroupExpansion -Identity ln1 -User user1 -``` - -This example retrieves complete group expansion information for "user1" in the user store "ln1", showing all equivalent users and groups in all user stores, by finding all parents and processing all aliaser mappings. - -## PARAMETERS - -### -Identity -The identity of the user store containing the user to expand. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -User -The user or group identifier to expand. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ExtraProperties -If specified, the command gets the extra properties for all principals (user and groups) returned by the resolve. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -XmlFile -The absolute path to an XML file which is accessible and writable from the security manager. -If specified, complete expansion information is written as XML to this file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Worker -The optional Worker parameter specifies the WorkerPoolNode object for the security worker that is to handle the request. - -```yaml -Type: WorkerPoolNode -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityDecodedSid.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityDecodedSid.md deleted file mode 100644 index 78222668e5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityDecodedSid.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecuritydecodedsid -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityDecodedSid ---- - -# Get-FASTSearchSecurityDecodedSid - -## SYNOPSIS -Gets the user identifier and SID from the encoded security identifier. - -## SYNTAX - -``` -Get-FASTSearchSecurityDecodedSid [-EncodedSID] <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet decodes an encoded security identifier (SID) and returns the user/group identifier (the common name) and Windows SID. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityDecodedSid -EncodedSID aebaaaaaaaaakiaaaaaccaqaaa -``` - -This example retrieves the Windows SID and user or group identifier for an encoded security identifier. - -## PARAMETERS - -### -EncodedSID -The encoded extended security identifier that will be decoded. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityEncodedSid](Get-FASTSearchSecurityEncodedSid.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityDefaultUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityDefaultUserStore.md deleted file mode 100644 index 10d433681c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityDefaultUserStore.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecuritydefaultuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityDefaultUserStore ---- - -# Get-FASTSearchSecurityDefaultUserStore - -## SYNOPSIS -Gets the default user store general setting. - -## SYNTAX - -``` -Get-FASTSearchSecurityDefaultUserStore [[-Worker] <WorkerPoolNode>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet gets the identity of the default user store that users and groups are looked up in. -The purpose of the command is to determine the user's or group's document access if the user store identity is not specified when looking up the user or group. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityDefaultUserStore -``` - -This example gets the identity of the default user store. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityWorkerNode workerserver | Get-FASTSearchSecurityDefaultUserStore -``` - -This example gets the default user store's general setting information for the security worker with a server name of "workerserver". - -## PARAMETERS - -### -Worker -The optional Worker parameter specifies the WorkerPoolNode object for the security worker that is to handle the request. - -```yaml -Type: WorkerPoolNode -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityDefaultUserStore](Set-FASTSearchSecurityDefaultUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityEncodedSid.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityEncodedSid.md deleted file mode 100644 index 090493f7dc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityEncodedSid.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityencodedsid -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityEncodedSid ---- - -# Get-FASTSearchSecurityEncodedSid - -## SYNOPSIS -Gets the encoded extended security identifier. - -## SYNTAX - -``` -Get-FASTSearchSecurityEncodedSid [[-SID] <String>] [[-User] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns a Base64 encoded security identifier for a user, group, or Windows SID (Windows security identifier). - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityEncodedSid -SID S-1-5-7 -``` - -This example returns an encoded security identifier and user name for the Windows SID, "5-1-5-7". - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityEncodedSid -User users -``` - -This example returns the encoded security identifier for the Windows built-in "Users" group. - -## PARAMETERS - -### -SID -The Windows security identifier to encode. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -User -The user or group identifier to encode. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityDecodedSid](Get-FASTSearchSecurityDecodedSid.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityGeneralSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityGeneralSettings.md deleted file mode 100644 index b3c3d8d5f8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityGeneralSettings.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecuritygeneralsettings -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityGeneralSettings ---- - -# Get-FASTSearchSecurityGeneralSettings - -## SYNOPSIS -Gets the security general settings. - -## SYNTAX - -``` -Get-FASTSearchSecurityGeneralSettings [[-Worker] <WorkerPoolNode>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves configuration information for general security settings, such as: - --- Default user store ID - --- CCTK server port number - --- CCTK server enabled - --- Default log level - --- Log level namespaces - --- Public Filter FQL - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityGeneralSettings | fl -``` - -This example retrieves the configuration setting for all the general security settings and formats the information as a list. - -## PARAMETERS - -### -Worker -The optional Worker parameter specifies the WorkerPoolNode object for the security worker that is to handle the request. - -```yaml -Type: WorkerPoolNode -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityLogLevel.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityLogLevel.md deleted file mode 100644 index 14d5032601..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityLogLevel.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityloglevel -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityLogLevel ---- - -# Get-FASTSearchSecurityLogLevel - -## SYNOPSIS -Gets the log level general setting. - -## SYNTAX - -``` -Get-FASTSearchSecurityLogLevel [[-Worker] <WorkerPoolNode>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves the configuration information for the log level general setting. -The log level controls the type of information that is logged by the security system. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityLogLevel -``` - -This example gets the configuration information for the log level's general setting, specifying the data logged by the security system. - -## PARAMETERS - -### -Worker -The optional Worker parameter specifies the WorkerPoolNode object for the security worker that is to handle the request. - -```yaml -Type: WorkerPoolNode -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityLogLevel](Set-FASTSearchSecurityLogLevel.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityLotusNotesUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityLotusNotesUserStore.md deleted file mode 100644 index 8c1407d6ed..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityLotusNotesUserStore.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecuritylotusnotesuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityLotusNotesUserStore ---- - -# Get-FASTSearchSecurityLotusNotesUserStore - -## SYNOPSIS -Gets a Lotus Notes user store. - -## SYNTAX - -``` -Get-FASTSearchSecurityLotusNotesUserStore [[-Identity] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a specific Lotus Notes user store. -If the Identity parameter is not specified, the cmdlet gets a list of all Lotus Notes user stores. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityLotusNotesUserStore -Identity ln1 -``` - -This example gets the Lotus Notes user store with the identity "ln1". - -## PARAMETERS - -### -Identity -The identity of the Lotus Notes user store to get. -If not specified, a list of all Lotus Notes user stores is returned. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchSecurityLotusNotesUserStore](New-FASTSearchSecurityLotusNotesUserStore.md) - -[Set-FASTSearchSecurityLotusNotesUserStore](Set-FASTSearchSecurityLotusNotesUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityPublicFilter.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityPublicFilter.md deleted file mode 100644 index d9de5a208e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityPublicFilter.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecuritypublicfilter -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityPublicFilter ---- - -# Get-FASTSearchSecurityPublicFilter - -## SYNOPSIS -Gets the public filter general setting. - -## SYNTAX - -``` -Get-FASTSearchSecurityPublicFilter [[-Worker] <WorkerPoolNode>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves the public filter general setting configuration information. -The public filter is the search security filter that is used to find documents that all users have access to. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityPublicFilter -``` - -This example gets the security public filter's general setting configuration information. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityWorkerNode workerserver | Get-FASTSearchSecurityPublicFilter -``` - -This example gets the security public filter's general setting configuration information for a security worker with the server name of "workerserver". - -## PARAMETERS - -### -Worker -The optional Worker parameter specifies the WorkerPoolNode object for the security worker that is to handle the request. - -```yaml -Type: WorkerPoolNode -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityPublicFilter](Set-FASTSearchSecurityPublicFilter.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityRegexAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityRegexAliaser.md deleted file mode 100644 index 0ef18ca9d1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityRegexAliaser.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityregexaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityRegexAliaser ---- - -# Get-FASTSearchSecurityRegexAliaser - -## SYNOPSIS -Gets a regular expression principal aliaser. - -## SYNTAX - -``` -Get-FASTSearchSecurityRegexAliaser [[-Identity] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a regular expression aliaser. -A regular expression aliaser maps users/groups from one user store to users/groups in other user stores, based on a regular expression pattern. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityRegexAliaser -Identity regex1 -``` - -This example retrieves a regular expression aliaser with an identity of "regex1". - -## PARAMETERS - -### -Identity -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchSecurityRegexAliaser](New-FASTSearchSecurityRegexAliaser.md) - -[Set-FASTSearchSecurityRegexAliaser](Set-FASTSearchSecurityRegexAliaser.md) - -[New-FASTSearchSecurityRegexAliaserPattern](New-FASTSearchSecurityRegexAliaserPattern.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserFilter.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserFilter.md deleted file mode 100644 index d507c01d22..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserFilter.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityuserfilter -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityUserFilter ---- - -# Get-FASTSearchSecurityUserFilter - -## SYNOPSIS -Gets a user's search security filter. - -## SYNTAX - -``` -Get-FASTSearchSecurityUserFilter [-Identity] <String> [-User] <String> [[-Worker] <WorkerPoolNode>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves the user search security filter containing all groups that the user has access to. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityUserFilter -Identity ln1 -User user1 -``` - -This example gets the search security filter for user "user1" in user store "ln1". - -## PARAMETERS - -### -Identity -The identity of the user store containing the user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -User -The identifier of the user or group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Worker -The optional Worker parameter specifies the WorkerPoolNode object for the security worker that is to handle the request. - -```yaml -Type: WorkerPoolNode -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserStore.md deleted file mode 100644 index d55d253d3e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserStore.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityUserStore ---- - -# Get-FASTSearchSecurityUserStore - -## SYNOPSIS -Gets a user store. - -## SYNTAX - -``` -Get-FASTSearchSecurityUserStore [[-Identity] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a security user store. If the Identity parameter is not specified, it gets a list of all user stores. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityUserStore -Identity ln1 -``` - -This example gets the user store with an identity of "ln1". - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityUserStore -``` - -This example gets a list of all user stores. - -## PARAMETERS - -### -Identity -The identity of the user store to get. -If not specified, the cmdlet gets a list of all user stores. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-FASTSearchSecurityUserStore](Remove-FASTSearchSecurityUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserStoreGroupExpansion.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserStoreGroupExpansion.md deleted file mode 100644 index d9c3b58afb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityUserStoreGroupExpansion.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityuserstoregroupexpansion -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityUserStoreGroupExpansion ---- - -# Get-FASTSearchSecurityUserStoreGroupExpansion - -## SYNOPSIS -Gets all groups in a user store that the specified user is a member of. - -## SYNTAX - -``` -Get-FASTSearchSecurityUserStoreGroupExpansion [-Identity] <String> [-User] <String> - [[-Worker] <WorkerPoolNode>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet gets all the groups in a user store that the user is a member of, and all the groups that any owning group is a member of. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityUserStoreGroupExpansion -Identity ln1 -User user1 -``` - -This example gets all the groups in the "ln1" user store that are parents, grand-parents, etc. -of the "user1" user. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityWorkerNode workerserver | Get-FASTSearchSecurityUserStoreGroupExpansion -Identity ln2 -User user1 -``` - -This example gets all the groups in the "ln2" user store from the worker with a server name of "workerserver" that are parents, grand-parents, etc. -of the "user1" user. - -## PARAMETERS - -### -Identity -The identity of the user store to look in. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -User -The user or group identifier to look up. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Worker -The optional Worker parameter specifies the WorkerPoolNode object for the security worker that is to handle the request. - -```yaml -Type: WorkerPoolNode -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityWorkerNode.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityWorkerNode.md deleted file mode 100644 index 58a1e973c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityWorkerNode.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityworkernode -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityWorkerNode ---- - -# Get-FASTSearchSecurityWorkerNode - -## SYNOPSIS -Gets status information about a security worker or workers. - -## SYNTAX - -``` -Get-FASTSearchSecurityWorkerNode [[-Identity] <String>] [-Active] [-Dead] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves the URI and status for a security worker or a group of workers. -A security worker is the Windows service that generates user search security filters. -The cmdlet's function changes depending upon the parameter values: - --- If Identity is specified, the command gets the worker associated with the given URI. - --- If Active is specified, the command gets a list of all active workers. - --- If Dead is specified, the command gets a list of all inactive workers. - --- If none of these parameters are specified, the command returns a list of all workers. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityWorkerNode -Identity localhost -``` - -This example gets the status and complete URI for the worker with "localhost" in its URI. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityWorkerNode -``` - -This example returns a list of all workers, both active and inactive. - -## PARAMETERS - -### -Identity -The identity of the worker to get. -This is a URI or a partial URI, the server name for example. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Active -If specified, get a list of all active workers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Dead -If specified, get a list of all inactive workers. -A worker is "dead" if it does not respond to requests from the security manager. -This may occur if a worker machine goes down, or if there are network problems. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityXMLAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityXMLAliaser.md deleted file mode 100644 index fe31f2a42a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSecurityXMLAliaser.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchsecurityxmlaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSecurityXMLAliaser ---- - -# Get-FASTSearchSecurityXMLAliaser - -## SYNOPSIS -Gets a security principal aliaser. - -## SYNTAX - -``` -Get-FASTSearchSecurityXMLAliaser [[-Identity] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet gets a regular expression or XML principal aliaser. -If the Identity parameter is not specified, it gets a list of all aliasers. - -A principal aliaser maps users from one user store into users in other user stores. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSecurityAliaser -``` - -This example gets a list of all XML and regular expression principal aliasers. - -### ---------------EXAMPLE 2----------------- -``` -Get-FASTSearchSecurityAliaser -Identity xmlalias4 -``` - -This example gets the principal aliaser with the ID xmlalias4. - -## PARAMETERS - -### -Identity -The identity of a regular expression or XML aliaser to get. -If not specified, the cmdlet gets a list of all aliasers. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchSecurityXMLAliaser](New-FASTSearchSecurityXMLAliaser.md) - -[Set-FASTSearchSecurityXMLAliaser](Set-FASTSearchSecurityXMLAliaser.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSpelltuningStatus.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSpelltuningStatus.md deleted file mode 100644 index 0aa346e706..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSpelltuningStatus.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-fastsearchspelltuningstatus -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Get-FASTSearchSpelltuningStatus ---- - -# Get-FASTSearchSpelltuningStatus - -## SYNOPSIS -Retrieves the status of spell tuning. - -## SYNTAX - -``` -Get-FASTSearchSpelltuningStatus [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the status of the automated alignment of the spell checking dictionary with the index; spell tuning is either active or inactive. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-FASTSearchSpelltuningStatus -``` - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Reset-FASTSearchSpelltuning](Reset-FASTSearchSpelltuning.md) - -[Add-FASTSearchSpelltuning](Add-FASTSearchSpelltuning.md) - -[Remove-FASTSearchSpelltuning](Remove-FASTSearchSpelltuning.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-ProjectServerLicense.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-ProjectServerLicense.md deleted file mode 100644 index 13b04cb716..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-ProjectServerLicense.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-projectserverlicense -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-ProjectServerLicense -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-ProjectServerLicense - -## SYNOPSIS -Retrieves the status of the license for Project Server. If the current license is a trial, it will also indicate the expiry date and if it has expired. - -## SYNTAX - -``` -Get-ProjectServerLicense [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Retrieves the status of the license for Project Server. If the current license is a trial, it will also indicate the expiry date and if it has expired. - -## EXAMPLES - -### Example 1 -``` -Get-ProjectServerLicense -``` - -Gets the status of the Project Server license and when it was activated. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the -objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServiceApplication.md deleted file mode 100644 index f62ed8d738..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServiceApplication.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: microsoft.office.access.services.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spaccessserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAccessServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAccessServiceApplication - -## SYNOPSIS -Returns an Access Services application or a collection of Access Services applications. - -## SYNTAX - -``` -Get-SPAccessServiceApplication [[-Identity] <SPAccessServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPAccessServiceApplication cmdlet retrieves an Access Services application. -If an identity is not specified, the cmdlet returns the collection of Access Services applications that are in the farm. -The properties returned from this cmdlet are read-only. -If changes need to be made, use the Set-SPAccessServiceApplication cmdlet. -These changes affect all computers in the farm in which this Access Services application runs. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE 1---------------- -``` -Get-SPAccessServiceApplication -identity "MyAccessService" -``` - -This example displays an Access Services application named MyAccessService. - -### ------------EXAMPLE 2---------------- -``` -Get-SPAccessServiceApplication | where {$_.recordsintablemax -gt 10000} -``` - -This example displays every Access Services application that run in the farm, which allows more than 10,000 records in a table. - -### ------------EXAMPLE 3---------------- -``` -Get-SPAccessServiceApplication -``` - -This example displays every Access Services application in the farm. - -## PARAMETERS - -### -Identity -Specifies the Access Services application to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPAccessServiceApplication object. - -```yaml -Type: SPAccessServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesApplication.md deleted file mode 100644 index 8a26dd7822..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesApplication.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spaccessservicesapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAccessServicesApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAccessServicesApplication - -## SYNOPSIS - -Gets an Access Services Service Application. - - -## SYNTAX - -``` -Get-SPAccessServicesApplication [[-Identity] <SPServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION - -Returns Access Services service applications available in the farm. - - -## EXAMPLES - -### Example 1 -``` - -$sa = Get-SPServiceApplication| ?{$_.TypeName -eq 'Access Services Web Service Application'} -Get-SPAccessServicesApplication -Identity $sa - -``` -Returns the Access Services application using a service application pipebind. - -### Example 2 -``` -Get-SPAccessServicesApplication -Identity 0d1da6e4-5cd6-4ccf-9ae1-ace2e964223a -``` - -Returns the Access Services application with the specified GUID. - - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity - -Must be in the form of a Service Application pipe bind or a GUID. - - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabase.md deleted file mode 100644 index c2b0d31a49..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabase.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spaccessservicesdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAccessServicesDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAccessServicesDatabase - -## SYNOPSIS -Returns an Access Services database. - -## SYNTAX - -``` -Get-SPAccessServicesDatabase [[-Identity] <AccessServicesDatabasePipeBind>] - [[-ContentDb] <SPContentDatabasePipeBind>] [[-AccessAppsOnly] <Boolean>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Returns an Access Services database. - -## EXAMPLES - -### Example 1 -``` -Get-SPAccessServicesDatabase -Identity https://apps-eec88dc5f597c6.contoso-apps.com/sites/team/accessApp -``` -Using the App Web, this example returns the Access database named 'accessApp'. - -### Example 2 -``` -Get-SPAccessServicesDatabase -ContentDb WSS_Content -``` -This example returns all Access databases associated with sites in the content database, WSS_Content. - -## PARAMETERS - -### -AccessAppsOnly -Returns only Access Apps. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ContentDb -The Content Database to return Access Apps from. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -The URL to the Access App. Must be the App Web URL. - -```yaml -Type: AccessServicesDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Access.Services.PowerShell.AccessServicesDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPContentDatabasePipeBind -System.Boolean -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServer.md deleted file mode 100644 index b51674598b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServer.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spaccessservicesdatabaseserver -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAccessServicesDatabaseServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAccessServicesDatabaseServer - -## SYNOPSIS -Returns SQL Server instances associated with Access Services. - -## SYNTAX - -### GetSingleDatabaseServerParamterSet -``` -Get-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> [<CommonParameters>] -``` - -### GetDatabaseServersParameterSet -``` -Get-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Returns the SQL Server instances that are available for use with Access Services. - -## EXAMPLES - -### Example 1 -``` -Get-SPAccessServicesDatabaseServer -``` - -Returns all SQL Server instances available for use. - - -### Example 2 -``` -Get-SPAccessServicesDatabaseServer -DatabaseServer ACCSQL -ServiceContext https://siteUrl -DatabaseServergroup DEFAULT -``` - -Returns the database server ACCSQL from the DEFAULT database server group using the service context from https://siteUrl. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies an existing Database Server associated with Access Services. - -```yaml -Type: AccessServicesDatabaseServerPipeBind -Parameter Sets: GetSingleDatabaseServerParamterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerGroup -The name of the database server group. - -```yaml -Type: AccessServicesDatabaseServerGroupPipeBind -Parameter Sets: GetSingleDatabaseServerParamterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: AccessServicesDatabaseServerGroupPipeBind -Parameter Sets: GetDatabaseServersParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context to retrieve Access Services database server information from. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServerGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServerGroup.md deleted file mode 100644 index 50a87cdeae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServerGroup.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spaccessservicesdatabaseservergroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAccessServicesDatabaseServerGroup -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAccessServicesDatabaseServerGroup - -## SYNOPSIS -Returns a database server group. - -## SYNTAX - -``` -Get-SPAccessServicesDatabaseServerGroup [-ServiceContext] <SPServiceContextPipeBind> - [[-DatabaseServerGroup] <AccessServicesDatabaseServerGroupPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Returns a database server group associated with the given service context. - -## EXAMPLES - -### Example 1 -``` -Get-SPAccessServicesDatabaseServerGroup -ServiceContext http://siteUrl -``` -Returns the database server group associated with the site, http://siteUrl. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseServerGroup -The name of the database server group. - -```yaml -Type: AccessServicesDatabaseServerGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context to retrieve Access Services database server information from. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.Office.Access.Services.PowerShell.AccessServicesDatabaseServerGroupPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServerGroupMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServerGroupMapping.md deleted file mode 100644 index 581c8620ff..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServerGroupMapping.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spaccessservicesdatabaseservergroupmapping -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAccessServicesDatabaseServerGroupMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAccessServicesDatabaseServerGroupMapping - -## SYNOPSIS -Returns the mapping of the database server group. - -## SYNTAX - -``` -Get-SPAccessServicesDatabaseServerGroupMapping [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet shows the current mapping of the database server group associated with a specific service context. - -## EXAMPLES - -### Example 1 -``` -Get-SPAccessServicesDatabaseServerGroupMapping -ServiceContext http://siteUrl -``` - -Outputs the database server group associated with the site, http://siteUrl. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context to retrieve Access Services database server information from. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAlternateURL.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAlternateURL.md deleted file mode 100644 index 0c9b5f2a56..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAlternateURL.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spalternateurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAlternateURL -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAlternateURL - -## SYNOPSIS - -Returns all alternate URLs that match a given set of criteria. - - - -## SYNTAX - -### ResourceName -``` -Get-SPAlternateURL [[-Identity] <SPAlternateUrlPipeBind>] -ResourceName <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Zone <SPUrlZone>] [<CommonParameters>] -``` - -### WebApplication -``` -Get-SPAlternateURL [[-Identity] <SPAlternateUrlPipeBind>] -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Zone <SPUrlZone>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPAlternateURL cmdlet returns all alternate URLs that match the scope given by either the optional Identity parameter or by a combination of the optional WebApplication, Zone, or Resource parameters. -Each criterion that is added narrows the scope. -If no criteria are specified then all alternate URLs are returned. - -If the Identity parameter is used, only the specific matching alternate URL is returned. -If no alternate URL with the given identity exists at the given scope, nothing is returned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPAlternateURL -WebApplication https://sitename -``` - -This example displays all the alternate URLs on a given Web application. - -### --------------EXAMPLE 2----------------- -``` -Get-SPAlternateURL -ResourceName "MyResource" -``` - -This example displays all the alternate URLs for a given resource. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the alternate URL to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or a valid URL, in the form https://server_name. - -```yaml -Type: SPAlternateUrlPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ResourceName -Specifies the name of the resource from which to list alternate URLs. - -```yaml -Type: String -Parameter Sets: ResourceName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the Web application from which to list alternate URLs. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Zone -Specifies one of the five zones with which the alternate URLs is associated. - -Must be a valid zone: Default, Intranet, Internet, Extranet, or Custom - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppAcquisitionConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppAcquisitionConfiguration.md deleted file mode 100644 index 6d0503b4da..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppAcquisitionConfiguration.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappacquisitionconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppAcquisitionConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppAcquisitionConfiguration - -## SYNOPSIS - -Returns app acquisition settings. - -## SYNTAX - -### MarketplaceSettingsInSiteSubscription -``` -Get-SPAppAcquisitionConfiguration -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### MarketplaceSettingsInWebApplication -``` -Get-SPAppAcquisitionConfiguration [-AssignmentCollection <SPAssignmentCollection>] - -WebApplication <SPWebApplicationPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets [https://go.microsoft.com/fwlink/?LinkID=187810](https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Get-SPAppAcquisitionConfiguration` cmdlet to return app acquisition settings from the SharePoint Storeor App Catalog. - -## EXAMPLES - -### ------------EXAMPLE 1------- -``` -Get-SPAppAcquisitionConfiguration -WebApplication https://localhost -``` - -This example returns app acquisition settings for the specified web application. - - -### ------------EXAMPLE 2------- -``` -Get-SPAppAcquisitionConfiguration -SiteSubscription https://localhost/sites/SharePointOnlineAdmin -``` - -This example returns app acquisition settings for the specified tenant. - -## PARAMETERS - -### -SiteSubscription - -Specifies the site collection for which app acquisition settings are to be returned. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: MarketplaceSettingsInSiteSubscription -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication - -Specifies the web application for which app acquisition settings are to be returned. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: MarketplaceSettingsInWebApplication -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPWebApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-SPAppAcquisitionConfiguration](Set-SPAppAcquisitionConfiguration.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppAutoProvisionConnection.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppAutoProvisionConnection.md deleted file mode 100644 index 2fb2c0f5de..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppAutoProvisionConnection.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappautoprovisionconnection -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppAutoProvisionConnection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppAutoProvisionConnection - -## SYNOPSIS - -Returns provision connection settings for an app. - - - -## SYNTAX - -``` -Get-SPAppAutoProvisionConnection [-AssignmentCollection <SPAssignmentCollection>] - [-ConnectionType <ConnectionTypes>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAppAutoProvisionConnection cmdlet to return the provision connection settings for an app. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1---------- -``` -Get-SpAppAutoProvisionConnection -``` - -This example returns the entire app auto provisioning connection information for the default site subscription. - -### ---------------EXAMPLE 2---------- -``` -$subscription = Get-SPSiteSubscription https://Contoso.com -Get-SPAppAutoProvisionConnection -SiteSubscription $subscription -ConnectionType RemoteWebHost -``` - -This example returns the remote web host app auto provisioning connection information for the site subscription for Contoso.com site - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ConnectionType -Specifies the connection type to provision the app. - -```yaml -Type: ConnectionTypes -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site collection from which to return the provision connection. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPAppAutoProvisionConnection](Set-SPAppAutoProvisionConnection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDeniedEndpointList.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDeniedEndpointList.md deleted file mode 100644 index 790a4121a6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDeniedEndpointList.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappdeniedendpointlist -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppDeniedEndpointList -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppDeniedEndpointList - -## SYNOPSIS - -Returns the app-denied endpoint list for the entire farm. - - - -## SYNTAX - -``` -Get-SPAppDeniedEndpointList [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-SPAppEndpoint cmdlet to return the app-denied endpoint list for the entire farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------EXAMPLE---------- -``` -Get-SPAppDeniedEndpoint -``` - -This example returns all the app-denied endpoints within the farm. - - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Clear-SPAppDeniedEndpointList](Clear-SPAppDeniedEndpointList.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDisablingConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDisablingConfiguration.md deleted file mode 100644 index 389381ea73..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDisablingConfiguration.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappdisablingconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppDisablingConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppDisablingConfiguration - -## SYNOPSIS - -Returns the disable sync list state for an app. - -## SYNTAX - -``` -Get-SPAppDisablingConfiguration [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-SPAppDisablingConfiguration cmdlet to return the disable sync list state for an app. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### -------------EXAMPLE------- -``` -Get-SPAppDisablingConfiguration -``` - -This example returns disable list sync state of a pp. - - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-SPAppDisablingConfiguration](Set-SPAppDisablingConfiguration.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDomain.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDomain.md deleted file mode 100644 index 53ab85c439..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppDomain.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappdomain -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppDomain -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppDomain - -## SYNOPSIS - -Returns the domain used to host apps. - - - -## SYNTAX - -``` -Get-SPAppDomain [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAppDomain cmdlet to return the domain used to host apps in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Get-SPAppDomain -``` - -This example returns the domain name that hosts apps in the entire farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPAppDomain](Set-SPAppDomain.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppHostingQuotaConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppHostingQuotaConfiguration.md deleted file mode 100644 index 0bf8cd98b7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppHostingQuotaConfiguration.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spapphostingquotaconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppHostingQuotaConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppHostingQuotaConfiguration - -## SYNOPSIS -Returns the hosting quotas for an app. - -## SYNTAX - -``` -Get-SPAppHostingQuotaConfiguration [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - -SiteSubscription <SPSiteSubscriptionPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Get-SPAppHostingQuotaConfiguration` cmdlet to return the hosting quotas for a specified app by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715](https://go.microsoft.com/fwlink/p/?LinkId=671715). - -## EXAMPLES - -### --------------EXAMPLE 1--------- -``` -Get-SPAppHostingQuotaConfiguration -Identity '586d4a32-98c3-42ce-80be-3c76c10c250c' -``` - -This example returns the hosted app quota associated to SiteSubscriptionID "586d4a32-98c3-42ce-80be-3c76c10c250c". - -### --------------EXAMPLE 1--------- -``` -Get-SPSiteSubscription | Get-SPAppHostingQuotaConfiguration -Identity $_ -``` - -This example returns the hosted app quota associated for all site subscriptions in the farm. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site subscription from which to get site collections. - -The type must be a valid URL, in the form, https://server_name or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-SPAppHostingQuotaConfiguration](Set-SPAppHostingQuotaConfiguration.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppInstance.md deleted file mode 100644 index 103a3d9a29..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppInstance.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppInstance - -## SYNOPSIS - -Returns the metadata for an instance of an app. - -## SYNTAX - -### IdentityParameterSet -``` -Get-SPAppInstance -Identity <SPAppInstance> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### SiteAndIdParameterSet -``` -Get-SPAppInstance -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] -AppInstanceId <Guid> - [<CommonParameters>] -``` - -### WebParameterSet -``` -Get-SPAppInstance [-App <SPApp>] [-AssignmentCollection <SPAssignmentCollection>] -Web <SPWebPipeBind> - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Get-AppInstance cmdlet to get a collection of app instances that are installed on an SPWeb object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE 1----------- -``` -Get-SPAppInstance -Web https://localhost -``` - -This example returns a collection if more than one app is installed on https://localhost. -If only one app is installed, a single object is returned. - -### -----------EXAMPLE 2----------- -``` -Get-SPAppInstance -AppInstanceId $instance.Id -``` - -This example returns the ID of an instance of an app. - -## PARAMETERS - -### -Identity -Specifies the App instance for which to find metadata. - -```yaml -Type: SPAppInstance -Parameter Sets: IdentityParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Sets the query scope to a site. - -Subsites are not included. - -```yaml -Type: SPSitePipeBind -Parameter Sets: SiteAndIdParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -App -Specifies the App. - -This parameter returns metadata for all instances of an app. - -```yaml -Type: SPApp -Parameter Sets: WebParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AppInstanceId -Specifies the App Instance ID to display. - -```yaml -Type: Guid -Parameter Sets: SiteAndIdParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Web -Specifies the SPWeb object. - -```yaml -Type: SPWebPipeBind -Parameter Sets: WebParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Restart-SPAppInstanceJobs](Restart-SPAppInstanceJobs.md) - -[Uninstall-SPAppInstance](Uninstall-SPAppInstance.md) - -[Update-SPAppInstance](Update-SPAppInstance.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppPrincipal.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppPrincipal.md deleted file mode 100644 index fa0c52f5d9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppPrincipal.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappprincipal -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppPrincipal -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppPrincipal - -## SYNOPSIS - -Displays a specific app principal object. - - - -## SYNTAX - -``` -Get-SPAppPrincipal -NameIdentifier <String> -Site <SPWebPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAppPrincipal cmdlet to display a specific app principal object from the SharePoint app registry. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE-------- -``` -Get-SPAppPrincipal -NameIdentifier "00000003-0000-0ff1-ce00-000000000000@f686d426-8d16-42db-81b7-cb578e110ccd" -``` - -This example returns the app principal for a specified ID. - -## PARAMETERS - -### -NameIdentifier -Specifies the app principal's name identifier to search for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Register-SPAppPrincipal](Register-SPAppPrincipal.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppScaleProfile.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppScaleProfile.md deleted file mode 100644 index 0d92908dad..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppScaleProfile.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappscaleprofile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppScaleProfile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppScaleProfile - -## SYNOPSIS - -Returns settings for an app profile. - -## SYNTAX - -``` -Get-SPAppScaleProfile [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAppScaleProfile cmdlet to return settings for an app profile. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Get-SPAppScaleProfile -``` - -This example returns the farm level app scale profile. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPAppScaleProfile](Set-SPAppScaleProfile.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppSiteSubscriptionName.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppSiteSubscriptionName.md deleted file mode 100644 index 82239334d2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppSiteSubscriptionName.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappsitesubscriptionname -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppSiteSubscriptionName -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppSiteSubscriptionName - -## SYNOPSIS - -Returns the name of the specified site subscription. - - - -## SYNTAX - -``` -Get-SPAppSiteSubscriptionName [-AssignmentCollection <SPAssignmentCollection>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAppSiteSubscriptionName cmdlet to return the name of the specified site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE 1------- -``` -Get-SPAppSiteSubscriptionName -``` - -This example returns the name of the default site subscription. - -### ------------EXAMPLE 2------- -``` -Get-SPAppSiteSubscriptionName -SiteSubscription https://www.contoso.com -``` - -This example returns the name of the site subscription for SPSite https://www.contoso.com - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the SPSiteSubscription object or the SPSiteSubscription Id or the URL of an SPSite. -If this parameter is not specified, then the default site subscription is used. -All SharePoint SPSites are members of the default site subscription if they have not been specifically assigned a site subscription. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPAppSiteSubscriptionName](Set-SPAppSiteSubscriptionName.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStateSyncLastRunTime.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStateSyncLastRunTime.md deleted file mode 100644 index 83781487dc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStateSyncLastRunTime.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappstatesynclastruntime -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppStateSyncLastRunTime -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppStateSyncLastRunTime - -## SYNOPSIS - -Returns the latest time the app state update job was invoked. - - - -## SYNTAX - -``` -Get-SPAppStateSyncLastRunTime [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAppStateSyncLastRunTime cmdlet to return the latest time the app state update job was invoked. -The app state update job updates the app states in SharePoint from the marketplace including app updates. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE------------ -``` -Get-SPAppStateSyncLastRunTime -``` - -This example returns the latest time the app state update job was invoked. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStateUpdateInterval.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStateUpdateInterval.md deleted file mode 100644 index 6c84b3ca63..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStateUpdateInterval.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappstateupdateinterval -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppStateUpdateInterval -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppStateUpdateInterval - -## SYNOPSIS - -Returns the interval in hours between updates of the app state update job. - -## SYNTAX - -``` -Get-SPAppStateUpdateInterval [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAppStateUpdateInterval cmdlet to return the interval in hours between updates of the app state update job. -The app state update job updates the app states, including app updates, in SharePoint based on information in the SharePoint Store. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE------- -``` -Get-SPAppStateUpdateInterval -``` - -This example returns the app state update timer job invocation interval in hours. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPAppStateUpdateInterval](Set-SPAppStateUpdateInterval.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStoreConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStoreConfiguration.md deleted file mode 100644 index 1130d53d58..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStoreConfiguration.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappstoreconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppStoreConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppStoreConfiguration - -## SYNOPSIS - -Returns app SharePoint Store settings. - -## SYNTAX - -``` -Get-SPAppStoreConfiguration [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-SPAppStoreConfiguration cmdlet to return all apps and their associated SharePoint Store settings. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE------- -``` -Get-SPAppStoreConfiguration -``` - -This example returns the settings for all of the apps. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-SPAppStoreConfiguration](Set-SPAppStoreConfiguration.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStoreWebServiceConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStoreWebServiceConfiguration.md deleted file mode 100644 index aa00c1b33b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStoreWebServiceConfiguration.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spappstorewebserviceconfiguration -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAppStoreWebServiceConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAppStoreWebServiceConfiguration - -## SYNOPSIS -Returns properties of a SharePoint Store app. - -## SYNTAX - -``` -Get-SPAppStoreWebServiceConfiguration [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Get-SPAppStoreWebServiceConfiguration` cmdlet to return property settings or SharePoint Store apps. - -This cmdlet is not intended for the IT Pro audience. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715](https://go.microsoft.com/fwlink/p/?LinkId=671715). - -## EXAMPLES - -### Example 1 -``` -Get-SPAppStoreWebServiceConfiguration -``` - -This example returns the product type and version for a SharePoint Store app. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAuthenticationProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAuthenticationProvider.md deleted file mode 100644 index 47adcd3fce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAuthenticationProvider.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spauthenticationprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAuthenticationProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAuthenticationProvider - -## SYNOPSIS - -Returns an authentication provider. - - - -## SYNTAX - -``` -Get-SPAuthenticationProvider [[-Identity] <SPAuthenticationProviderPipeBind>] - [-WebApplication] <SPWebApplicationPipeBind> [-Zone] <SPUrlZone> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPAuthenticationProvider cmdlet returns an authentication provider on a specified Web application zone. -The following are the standard authentication providers available for SharePoint Products: NTLM, Classic NTLM, Negotiate, and Classic Negotiate. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE 1----------------- -``` -Get-SPAuthenticationProvider -WebApplication https://webAppUrl -Zone Default -``` - -This example retrieves the authentication provider in the Default zone of the Web Application 'https://webappurl/'. - -## PARAMETERS - -### -Identity -Specifies the authentication provider to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint authentication provider (for example, NTLM); or an instance of a valid SPAuthenticationProvider object. - -```yaml -Type: SPAuthenticationProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Returns the content databases for the specified Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Zone -Specifies the Web application zone or zones for which to return the authentication provider. - -The type must be any one of the valid zones: Default, Intranet, Internet, Extranet, or Custom. - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAuthenticationRealm.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAuthenticationRealm.md deleted file mode 100644 index 09dc1f563b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPAuthenticationRealm.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spauthenticationrealm -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPAuthenticationRealm -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPAuthenticationRealm - -## SYNOPSIS - -Returns the authentication realms. - -## SYNTAX - -``` -Get-SPAuthenticationRealm [[-ServiceContext] <SPServiceContextPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPAuthenticationRealm cmdlet to display the authentication realms of the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE------------- -``` -Get-SPAuthenticationRealm -``` - -This example displays the authentication realms in the entire farm. - -## PARAMETERS - -### -ServiceContext -Specifies the service context for which the realm needs to be displayed. -For example, $root.web. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPAuthenticationRealm](Set-SPAuthenticationRealm.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBackupHistory.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBackupHistory.md deleted file mode 100644 index c6dfd77d5a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBackupHistory.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spbackuphistory -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPBackupHistory -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPBackupHistory - -## SYNOPSIS - -Returns a history of backup and restore operations. - - - -## SYNTAX - -``` -Get-SPBackupHistory -Directory <String> [-AssignmentCollection <SPAssignmentCollection>] [-ShowBackup] - [-ShowRestore] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPBackupHistory cmdlet reads a history of backup and restore operations that have been run. -Specifies whether you want to display only the backup history, only the restore history, or all of the history. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------- -``` -Get-SPBackupHistory -Directory \\file_server\share\Backup -``` - -This example returns all farm backup and restore operations that have been run for the \\\\file_server\share\Backup directory. - -### ------------------EXAMPLE 2----------------- -``` -Get-SPBackupHistory -Directory C:\Backup -ShowBackup -``` - -This example returns all of the farm backup operations that have been run for the C:\Backup directory. - -### ------------------EXAMPLE 3----------------- -``` -(Get-SPBackupHistory -Directory C:\Backup -ShowBackup)[0].SelfId | Restore-SPFarm -Directory C:\Backup -RestoreMethod overwrite -``` - -This example gets all of the farm backup operations that have been run for the C:\Backup directory, finds the most recent backup, and then passes its backup GUID to the Restore-SPFarm cmdlet. -The Restore-SPFarm cmdlet will then perform an overwrite restore from that backup package. - -## PARAMETERS - -### -Directory -Specifies the path where the SharePoint Products backup packages generated from a farm backup have been stored. - -The type must be a valid path in either of the following forms: - -- C:\folder_name -- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ShowBackup -Filters the output so that the history of backup operations only is displayed. -If both the ShowBackup and the ShowRestore parameters are not specified, the history of both backup and restore operations is displayed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowRestore -Filters the output so that the history of restore operations only is displayed. -If both the ShowBackup and the ShowRestore parameters are absent, the history of both backup and restore operations is displayed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBingMapsBlock.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBingMapsBlock.md deleted file mode 100644 index 7980353618..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBingMapsBlock.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spbingmapsblock -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPBingMapsBlock -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPBingMapsBlock - -## SYNOPSIS - -Returns Bing Maps blocked status. - - - -## SYNTAX - -``` -Get-SPBingMapsBlock [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPBingMapsBlock cmdlet to return true or false on whether Bing Maps are blocked in all locales. -This cmdlet will return an object, and "BlockBingMapsInAllLocales" property will return True or False. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE----------- -``` -Get-SPBingMapsBlock -``` - -This example returns an object, and BlockBingMapsInAllLocales property will return True or False on whether Bing Maps are blocked in all locales. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPBingMapsBlock](Set-SPBingMapsBlock.md) - -[Get-SPBingMapsKey](Get-SPBingMapsKey.md) - -[Set-SPBingMapskey](Set-SPBingMapskey.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBingMapsKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBingMapsKey.md deleted file mode 100644 index 956c58a229..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBingMapsKey.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spbingmapskey -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPBingMapsKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPBingMapsKey - -## SYNOPSIS - -Returns the Bing Maps key. - - - -## SYNTAX - -``` -Get-SPBingMapsKey [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPBingMapsKey cmdlet to return the current Bing Maps key for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE----------- -``` -Get-SPBingMapsKey -``` - -This example returns the Bing Maps key for the farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPBingMapskey](Set-SPBingMapskey.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBrowserCustomerExperienceImprovementProgram.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBrowserCustomerExperienceImprovementProgram.md deleted file mode 100644 index 3719a5158b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBrowserCustomerExperienceImprovementProgram.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spbrowsercustomerexperienceimprovementprogram -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPBrowserCustomerExperienceImprovementProgram -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPBrowserCustomerExperienceImprovementProgram - -## SYNOPSIS - -Returns the current opt-in state for the browser Customer Experience Improvement Program. - - - -## SYNTAX - -### Farm -``` -Get-SPBrowserCustomerExperienceImprovementProgram [-Farm] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### SiteSubscription -``` -Get-SPBrowserCustomerExperienceImprovementProgram -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### WebApplication -``` -Get-SPBrowserCustomerExperienceImprovementProgram -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPBrowserCustomerExperienceImprovementProgram cmdlet reads the current opt-in state for the browser Customer Experience Improvement Program. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Get-SPBrowserCustomerExperienceImprovementProgram -WebApplication https://WebAppexample1 -``` - -This example returns the current Customer Experience Improvement Program opt-in state for the Web application, WebAppexample1. - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPSiteSubscription https://SiteSubscription1 | Get-SPBrowserCustomerExperienceImprovementProgram -``` - -The following example returns the Customer Experience Improvement Program opt-in state for the site subscription, SiteSubscription1. - -## PARAMETERS - -### -Farm -Specifies that the opt-in state for the farm is returned by this cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: Farm -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Returns the opt-in state for the specified site subscription. - -The type must be a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscription1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Returns the opt-in state for the specified SharePoint Web application. - -The type must be a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogEntityNotificationWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogEntityNotificationWeb.md deleted file mode 100644 index a918b626a9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogEntityNotificationWeb.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spbusinessdatacatalogentitynotificationweb -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPBusinessDataCatalogEntityNotificationWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPBusinessDataCatalogEntityNotificationWeb - -## SYNOPSIS - -Returns the entity notification site. - - - -## SYNTAX - -``` -Get-SPBusinessDataCatalogEntityNotificationWeb -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPBusinessDataCatalogEntityNotificationWeb cmdlet to return the entity notification site that can receive and forward external system notifications. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------EXAMPLE----------- -``` -Get-SPBusinessDataCatalogEntityNotificationWeb -ServiceContext "http://contoso/" -``` - -This example returns the entity notification site for the site collection at http://contoso. - -## PARAMETERS - -### -ServiceContext -Specifies the service context for which the entity notification web has to be returned. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-SPBusinessDataCatalogEntityNotificationWeb](Clear-SPBusinessDataCatalogEntityNotificationWeb.md) - -[Set-SPBusinessDataCatalogEntityNotificationWeb](Set-SPBusinessDataCatalogEntityNotificationWeb.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogMetadataObject.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogMetadataObject.md deleted file mode 100644 index a3e0566078..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogMetadataObject.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spbusinessdatacatalogmetadataobject -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPBusinessDataCatalogMetadataObject -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPBusinessDataCatalogMetadataObject - -## SYNOPSIS - -Returns a Business Data Connectivity Metadata Store metadata object. - - - -## SYNTAX - -``` -Get-SPBusinessDataCatalogMetadataObject -BdcObjectType <PSBdcObjectType> - -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] - [-Namespace <String>] [-ContainingLobSystem <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPBusinessDataCatalogMetadataObject cmdlet reads a Business Data Connectivity Metadata Store metadata object from a Business Data Connectivity Service application. - -Output for this cmdlet can be a series of objects. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Model" -Name "ContosoModel" -ServiceConext http://contoso -``` - -This example gets a metadata object of type Model with the name ContosoModel from the Business Data Connectivity Metadata Store on the given site. - -## PARAMETERS - -### -BdcObjectType -Specifies the type of the metadata object to return. - -The type must be one of the following valid metadata object types: Catalog, Model, LobSystem, LobSystemInstance, or Entity. - -```yaml -Type: PSBdcObjectType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context of the Business Data Connectivity Metadata Store metadata object to return. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the metadata object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Namespace -Specifies the namespace of the metadata object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContainingLobSystem -Specifies the name of the LobSystem. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogThrottleConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogThrottleConfig.md deleted file mode 100644 index c44f9546df..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPBusinessDataCatalogThrottleConfig.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spbusinessdatacatalogthrottleconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPBusinessDataCatalogThrottleConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPBusinessDataCatalogThrottleConfig - -## SYNOPSIS - -Returns the throttling configuration for a Business Data Connectivity Service application. - - - -## SYNTAX - -### FileBackedProvided -``` -Get-SPBusinessDataCatalogThrottleConfig [-FileBacked] -Scope <ThrottleScope> -ThrottleType <ThrottleType> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### ProxyProvided -``` -Get-SPBusinessDataCatalogThrottleConfig -Scope <ThrottleScope> - -ServiceApplicationProxy <SPServiceApplicationProxyPipeBind> -ThrottleType <ThrottleType> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPBusinessDataCatalogThrottleConfig cmdlet reads the throttling configuration for a Business Data Connectivity Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottleType Items -ServiceApplicationProxy $contosoServAppProxy -``` - -This example returns the throttling information that is related to database items for the given service application. - -## PARAMETERS - -### -FileBacked -Requests the throttling configuration for file backed metadata catalogs. - -```yaml -Type: SwitchParameter -Parameter Sets: FileBackedProvided -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Returns the throttling configuration for the specified the scope. - -The type must be one of the following: Wcf, WebService, Database, Global, or Custom. - -```yaml -Type: ThrottleScope -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplicationProxy -Specifies the Business Data Connectivity Service application proxy that contains the throttling configuration to get. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: ProxyProvided -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThrottleType -Returns the throttling configuration for the specified throttle type. - -The type must be one of the following: None, Items, Size, Connections, or Timeout. - -```yaml -Type: ThrottleType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPCertificateAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPCertificateAuthority.md deleted file mode 100644 index bd2418e3ac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPCertificateAuthority.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spcertificateauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPCertificateAuthority -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPCertificateAuthority - -## SYNOPSIS - -Returns the SharePoint certificate authority (CA). - - - -## SYNTAX - -``` -Get-SPCertificateAuthority [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPCertificateAuthority cmdlet returns the SharePoint certificate authority (CA). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPCertificateAuthority -``` - -This example gets the certificate authority. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimProvider.md deleted file mode 100644 index f95dedb42e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimProvider.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spclaimprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPClaimProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPClaimProvider - -## SYNOPSIS - -Returns a claim provider. - - - -## SYNTAX - -``` -Get-SPClaimProvider [[-Identity] <SPClaimProviderPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPClaimProvider cmdlet returns a claim provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPClaimProvider -Identity "MyClaimProvider" | Set-SPClaimProvider -Enabled $false -``` - -This example disables the claim provider MyClaimProvider. - -## PARAMETERS - -### -Identity -Specifies the claim provider to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a claim provider (for example, MyClaimProvider1); or an instance of a valid SPClaimProvider object. - -```yaml -Type: SPClaimProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimProviderManager.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimProviderManager.md deleted file mode 100644 index 45b163f5ac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimProviderManager.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spclaimprovidermanager -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPClaimProviderManager -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPClaimProviderManager - -## SYNOPSIS - -Returns a claim provider manager. - - - -## SYNTAX - -``` -Get-SPClaimProviderManager [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPClaimProviderManager cmdlet reads a claim provider manager. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE-------- -``` -Get-SPClaimProviderManager -``` - -This example returns a claim provider manager for the farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimTypeEncoding.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimTypeEncoding.md deleted file mode 100644 index e886c3780e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPClaimTypeEncoding.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spclaimtypeencoding -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPClaimTypeEncoding -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPClaimTypeEncoding - -## SYNOPSIS - -Returns a list of all the types of claims. - -## SYNTAX - -``` -Get-SPClaimTypeEncoding [-AssignmentCollection <SPAssignmentCollection>] [-ClaimType <String>] - [-EncodingCharacter <Char>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-SPClaimTypeEncoding cmdlet to return the following: - - --- A list of all the types of claims that are registered in the farm - --- The Unicode character that will be encoded when the SPClaim.ToEncodedString method is invoked - --- The SPClaim.ClaimType property is set to a valid value - - -For additional information about the SPClaim methods and properties, see M:Microsoft.SharePoint.Administration.Claims.SPClaim.ToEncodedString and P:Microsoft.SharePoint.Administration.Claims.SPClaim.ClaimType respectively. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1-------- -``` -Get-SPClaimTypeEncoding -``` - -This example returns a list of all types of claima in the farm. - -### --------------EXAMPLE 2-------- -``` -Get-SPClaimTypeEncoding -ClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/country" -``` - -This example returns a specific claim type by using the ClaimType parameter. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClaimType -Specifies an encoding character that is mapped to a type of input claim. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncodingCharacter -Specifies a type of claim that is mapped to an input character. - -```yaml -Type: Char -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPClaimTypeEncoding](New-SPClaimTypeEncoding.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPConnectedServiceApplicationInformation.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPConnectedServiceApplicationInformation.md deleted file mode 100644 index 64e1814c59..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPConnectedServiceApplicationInformation.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spconnectedserviceapplicationinformation -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPConnectedServiceApplicationInformation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPConnectedServiceApplicationInformation - -## SYNOPSIS -Returns the health of the service application proxy. - -## SYNTAX - -``` -Get-SPConnectedServiceApplicationInformation [[-ServiceApplicationProxy] <SPServiceApplicationProxyPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Get-SPConnectedServiceApplicationInformation` cmdlet checks whether the proxy to a service application is in good health. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715](https://go.microsoft.com/fwlink/p/?LinkId=671715). - -## EXAMPLES - -### Example 1 -``` -$validProxy = $false -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq "User Profile Service Application Proxy"} -$proxyHealth = Get-SPConnectedServiceApplicationInformation -ServiceApplicationProxy $proxy -if(($proxyHealth -ne $null) -and ($proxyHealth.ApplicationAddressesState -eq "UpToDate")) { - $validProxy = $true - } else { - $validProxy = $false - } -$validProxy -``` - -This example checks the health of the service application proxy server. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplicationProxy -Specifies the name of the service application proxy. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationProxyPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabase.md deleted file mode 100644 index aed7f5e482..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabase.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPContentDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPContentDatabase - -## SYNOPSIS - -Returns one or more content databases. - - - -## SYNTAX - -### DefaultSet -``` -Get-SPContentDatabase [[-Identity] <SPContentDatabasePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-NoStatusFilter] [<CommonParameters>] -``` - -### ContentDatabasesOfSite -``` -Get-SPContentDatabase -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### AllContentDatabasesInWebApplication -``` -Get-SPContentDatabase -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-NoStatusFilter] [<CommonParameters>] -``` -### ContentDatabasesSinceLastProfileSync -``` -Get-SPContentDatabase -DaysSinceLastProfileSync <Int32> [-NoStatusFilter] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### Unattached -``` -Get-SPContentDatabase [-AssignmentCollection <SPAssignmentCollection>] [-ConnectAsUnattachedDatabase] - [-DatabaseCredentials <PSCredential>] -DatabaseName <String> -DatabaseServer <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPContentDatabase cmdlet returns the specified content databases. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE 1------------ -``` -Get-SPContentDatabase -WebApplication https://webAppUrl -``` - -This example returns all content databases used by the sitename Web application. - -### ----------------EXAMPLE 2------------ -``` -Get-SPContentDatabase -Site https://siteUrl -``` - -This example returns the content database that contains the site collection at https://siteUrl. - -### ----------------EXAMPLE 3------------ -``` -PS C:\>Get-SPContentDatabase -DaysSinceLastProfileSync 7 -``` -This example returns all content databases that were last synchronized with the User Profile service 7 or more days ago. Content databases that were last synchronized with the User Profile service less than 7 days ago would not be returned. - -## PARAMETERS - -### -Identity -Specifies a specific content database to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint content database (for example, SPContentDB1); or an instance of a valid SPContentDatabase object. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Returns the content database for the specified site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: ContentDatabasesOfSite -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Returns the content databases for the specified Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: AllContentDatabasesInWebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ConnectAsUnattachedDatabase -Specifies that only unattached databases in the farm are returned. - -```yaml -Type: SwitchParameter -Parameter Sets: Unattached -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Server Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: Unattached -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database in the farm. - -```yaml -Type: String -Parameter Sets: Unattached -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the database server in the farm. - -```yaml -Type: String -Parameter Sets: Unattached -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### -DaysSinceLastProfileSync -Specifies the minimum number of days since the User Profile service last synchronized the content database. - -```yaml -Type: Int32 -Parameter Sets: ContentDatabasesSinceLastProfileSync -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - - -### -NoStatusFilter -Specifies whether a status filter is turned on. - -The valid values are True or False. The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: DefaultSet, AllContentDatabasesInWebApplication -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabaseOrphanedData.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabaseOrphanedData.md deleted file mode 100644 index 7c0780aa47..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabaseOrphanedData.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spcontentdatabaseorphaneddata -applicable: SharePoint Server 2019 -title: Get-SPContentDatabaseOrphanedData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPContentDatabaseOrphanedData - -## SYNOPSIS -Gets orphaned data in content database. - - -## SYNTAX - -``` -Get-SPContentDatabaseOrphanedData [-Identity] <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - - -## DESCRIPTION -Use the **Get-SPContentDatabaseOrphanedData** to display orphaned objects. - -## EXAMPLES - -### EXAMPLE 1 -```powershell - Get-SPContentDatabase "WSS_Content" | Get-SPContentDatabaseOrphanedData -``` -This example gets orphan objects in content database named "WSS_Content". - -## PARAMETERS - -### -Identity -Specifies the GUID of the content database to get. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2019 -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## RELATED LINKS - - - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDeploymentJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDeploymentJob.md deleted file mode 100644 index 838c4bee48..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDeploymentJob.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spcontentdeploymentjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPContentDeploymentJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPContentDeploymentJob - -## SYNOPSIS -Returns a content deployment job or a collection of content deployment jobs. - -## SYNTAX - -``` -Get-SPContentDeploymentJob [[-Identity] <SPContentDeploymentJobPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Path <SPContentDeploymentPathPipeBind>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPContentDeploymentJob cmdlet reads the specified content deployment job. -If the Identity parameter is not specified, this cmdlet returns the collection of content deployment jobs on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Get-SPContentDeploymentJob -Identity 'Job 1' -``` - -This example returns the content deployment job called Job 1. - -## PARAMETERS - -### -Identity -Specifies the content deployment job to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment job (for example, DeployJob1); or an instance of a valid SPContentDeploymentJob object. - -```yaml -Type: SPContentDeploymentJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies that content deployment jobs for only the specified content deployment path are returned. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment job (for example; DeployPath1); or an instance of a valid SPContentDeploymentPath object. - -```yaml -Type: SPContentDeploymentPathPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDeploymentPath.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDeploymentPath.md deleted file mode 100644 index 64491fe90c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDeploymentPath.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spcontentdeploymentpath -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPContentDeploymentPath -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPContentDeploymentPath - -## SYNOPSIS -Returns a content deployment path or a collection of content deployment paths. - -## SYNTAX - -``` -Get-SPContentDeploymentPath [[-Identity] <SPContentDeploymentPathPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPContentDeploymentPath cmdlet reads the specified content deployment path. -If the Identity parameter is not specified, this cmdlet returns the collection of content deployment paths on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE-------------- -``` -Get-SPContentDeploymentPath -Identity 'Path 1' -``` - -This example returns the content deployment path named Path 1. - -## PARAMETERS - -### -Identity -Specifies the content deployment path to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment path (for example, DeployPath1); or an instance of a valid SPContentDeploymentJob object. - -```yaml -Type: SPContentDeploymentPathPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPCustomLayoutsPage.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPCustomLayoutsPage.md deleted file mode 100644 index 97d54af0f5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPCustomLayoutsPage.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spcustomlayoutspage -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPCustomLayoutsPage -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPCustomLayoutsPage - -## SYNOPSIS - -Returns a mapping to a custom layout page. - - - -## SYNTAX - -``` -Get-SPCustomLayoutsPage -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Identity <SPCustomPage>] [-CompatibilityLevel <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPCustomLayoutsPagecmdlet cmdlet returns a mapping to a custom layout page in a Web application. -If the Identity parameter is not specified, this cmdlet returns the collection of mappings for all custom layout pages. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Get-SPCustomLayoutsPage -Identity '_layouts/accessdenied.aspx' -WebApplication 'https://webappurl/' -``` - -This example returns the mapping of the AccessDenied layout page in the Web application. - -## PARAMETERS - -### -WebApplication -Specifies the SharePoint Web application that contains the custom layout page. - -The type must be a valid URL, in the form https://webAppUrl; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the custom layout page to get. - -The type must be one of the following: None, AccessDenied, Confirmation, Error, Login, RequestAccess, Signout, or WebDeleted. - -```yaml -Type: SPCustomPage -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. This value sets the initial CompatibilityLevel value for the site collection. When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the web application depending on the CompatibilityRange setting. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDataConnectionFile.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDataConnectionFile.md deleted file mode 100644 index 9213a0a9c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDataConnectionFile.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdataconnectionfile -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDataConnectionFile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDataConnectionFile - -## SYNOPSIS -Returns a data connection file or a collection of data connection files. - -## SYNTAX - -``` -Get-SPDataConnectionFile [[-Identity] <SPDataConnectionFilePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPDataConnectionFile cmdlet gets a specified data connection file or a collection of data connection files. -If the Identity parameter is not specified, the cmdlet returns the collection of data connection files for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1-------------- -``` -Get-SPDataConnectionFile -``` - -This example lists the Identity, DisplayName, and WebAccessible properties ofeach .udcx file. - -### ---------------EXAMPLE 2-------------- -``` -C:\PS>"Sample.udcx" | Get-SPDataConnectionFile -``` - -This example lists the Identity, DisplayName, and WebAccessible properties of the specified file, named Sample.udcx. - -### ---------------EXAMPLE 3-------------- -``` -Get-SPDataConnectionFile | where {$_.Category -eq "Category1"} -``` - -This example lists the Identity, DisplayName, and WebAccessible properties of all .udcx files with the specified Category. - -## PARAMETERS - -### -Identity -Specifies the data file connection to get. - -The type must be a valid GUID, in form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a data connection file (for example, DataConnectionFileName1.udcx); or an instance of a valid SPDataConnectionFile object. - -```yaml -Type: SPDataConnectionFilePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDataConnectionFileDependent.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDataConnectionFileDependent.md deleted file mode 100644 index 869dd2d06a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDataConnectionFileDependent.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdataconnectionfiledependent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDataConnectionFileDependent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDataConnectionFileDependent - -## SYNOPSIS -Returns deployed forms on the server dependent on a universal data connection. - -## SYNTAX - -``` -Get-SPDataConnectionFileDependent [-Identity] <SPDataConnectionFilePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPDataConnectionFileDependent returns all administrator deployed forms that depend on a specified universal data connection (.udc) file located in the central data connection store. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPDataConnectionFileDependant -Identity 'FileName.udcx' -``` - -This example displays a list of deployed forms with a specified name. - -## PARAMETERS - -### -Identity -Specifies the data connection file to get. - -The type must be a valid GUID, in form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a data connection file (for example, DataConnectionFileName1.udcx); or an instance of a valid SPDataConnectionFile object. - -```yaml -Type: SPDataConnectionFilePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDatabase.md deleted file mode 100644 index e20f8ea334..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDatabase.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDatabase - -## SYNOPSIS - -Retrieves all properties of a database. - - - -## SYNTAX - -### DefaultParameterSet -``` -Get-SPDatabase [[-Identity] <SPDatabasePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### ServerParameterSet -``` -Get-SPDatabase -ServerInstance <SPDatabaseServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### NameParameterSet -``` -Get-SPDatabase [-AssignmentCollection <SPAssignmentCollection>] -Name <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPDatabase cmdlet displays all public properties of a database to the current window. -If the Identity parameter is specified, only properties of that ID are displayed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Get-SPDatabase | ?{$_.TypeName -eq 'Microsoft.Office.Server.Administration.ProfileDatabase'} -``` - -This example gets the Profile database used by the User Profile Service Application. - -### --------------------EXAMPLE 2--------------------- -``` -Get-SPDatabase -Name 'Profile DB' -``` - -This example gets the Profile database by name. Applies to SharePoint Server 2016, SharePoint Server 2019 only. - -## PARAMETERS - -### -Identity -Specifies the name of the database to display public properties. - -The type must be a valid GUID, in the form 1234-3456-567kg. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: DefaultParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServerInstance -Specifies the name of the SQL instance that contains the database in either the form "Server" for a default SQL instance or "Server\Instance" for a named SQL instance. - -```yaml -Type: SPDatabaseServiceInstancePipeBind -Parameter Sets: ServerParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the database. - -```yaml -Type: String -Parameter Sets: NameParameterSet -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDeletedSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDeletedSite.md deleted file mode 100644 index c39c672f22..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDeletedSite.md +++ /dev/null @@ -1,263 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdeletedsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDeletedSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDeletedSite - -## SYNOPSIS - -Gets a list of deleted site collections. - - - -## SYNTAX - -``` -Get-SPDeletedSite [-Identity] <SPDeletedSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-ContentDatabase <SPContentDatabasePipeBind>] [-DateTimeFrom <String>] [-DateTimeTo <String>] - [-Limit <String>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Use the Get-SPDeletedSite cmdlet to display a list of deleted site collections by using the Identity parameter. -If no parameter is specified, then all deleted site collections in the farm are displayed. Deleted Sites are sites in the process of gradual delete. For more information on gradual delete, see [Remove-SPSite](https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsite?view=sharepoint-ps). - -Unlike the Get-SPSite cmdlet that uses the host name and scheme for the Identity parameter (that is, https://server_name), the value of the identity parameter for all SPDeletedSite cmdlets use a server-relative URL. -Typically, the forward slash character (/) begins the relative URL and also denotes the root site. - -For additional information about a server-relative URL or understanding general concepts about absolute and relative URLs, see Server-relative URL Property (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsite.serverrelativeurl.aspx) or Understanding Absolute and Relative URL Addresses (https://msdn.microsoft.com/en-us/library/bb208688(office.12).aspx). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1--------------------- -``` -Get-SPDeletedSite -Identity 610857cb-8414-4a89-8bf3-ad3628f6c86c -``` - -This example gets a specific deleted site collection by using a site ID. - -### ------------------EXAMPLE 2--------------------- -``` -Get-SPDeletedSite "/" -``` - -This example gets a deleted site collection from the root site. - -### ------------------EXAMPLE 3--------------------- -``` -Get-SPDeletedSite '/Site/cat*' -``` - -This example matches a deleted site collection that contains any combination with the string "cat". -The asterisk (*) wildcard character requests a match for multiple characters. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site collection to get. - -The identity can be either a valid server-relative URL in the form /sites/site_name or a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPDeletedSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the GUID of the content database from which to list site collections. - -The type must be a valid database name in the form SPContentDB01 or a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DateTimeFrom -The type must be a valid DateTime format that is culture-specific to the administrative language, such as 2/16/2007 12:15:12 for English-US. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DateTimeTo -The type must be a valid DateTime format that is culture-specific to the administrative language, such as 2/16/2007 12:15:12 for English-US. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit -Limits the maximum number of site collections to return. -The default value is 1000. - -The type must be a valid non-negative number. -Specify ALL to return all site collections for the given scope. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site subscription from which to get site collections. - -The type must be a valid URL in the form https://server_name or a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the Web application from which to list sites. - -The type must be a valid URL in the form https://server_name; a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh; or the Web application name, for example, WebApplication1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDesignerSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDesignerSettings.md deleted file mode 100644 index c58659be0c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDesignerSettings.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdesignersettings -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDesignerSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDesignerSettings - -## SYNOPSIS - -Displays SharePoint Designer features. - - - -## SYNTAX - -``` -Get-SPDesignerSettings [-WebApplication] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPDesignerSettings cmdlet determines whether SharePoint Designer features are enabled on the specified Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE------------------------ -``` -Get-SPDesignerSettings -webapplication https://contoso -``` - -This example retrieves the SharePoint Designer settings for the Web application, https://contoso. - -## PARAMETERS - -### -WebApplication -Specifies the Web application in which the settings apply. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticConfig.md deleted file mode 100644 index 14757bf999..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticConfig.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdiagnosticconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDiagnosticConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDiagnosticConfig - -## SYNOPSIS - -Retrieves ULS diagnostic configuration values of the farm. - - - -## SYNTAX - -``` -Get-SPDiagnosticConfig [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPDiagnoticConfig cmdlet retrieves ULS diagnostic configuration values of the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPDiagnosticConfig -``` - -This example returns all diagnostic configuration values. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticsPerformanceCounter.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticsPerformanceCounter.md deleted file mode 100644 index 6a22202482..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticsPerformanceCounter.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdiagnosticsperformancecounter -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDiagnosticsPerformanceCounter -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDiagnosticsPerformanceCounter - -## SYNOPSIS - -Returns a collection of performance counters. - - - -## SYNTAX - -``` -Get-SPDiagnosticsPerformanceCounter [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseServer] - [-WebFrontEnd] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPDiagnosticsPerformanceCounter cmdlet returns the collection of performance counters that are read and recorded in the usage database. -If neither the DatabaseServer or WebFrontEnd parameters are specified, this cmdlet returns the performance counters on the front end Web servers and database servers in the farm. - -To distinguish counters that are collected on database servers and counters that are collected on front end Web servers, note that counters that are collected on database servers have a Provider Name of job-diagnostics-performance-counter-sql-provider, and counters that are collected on front end Web servers have a Provider Name of job-diagnostics-performance-counter-wfe-provider. - -The Get-SPDiagnosticsPerformanceCounter cmdlet is only available by using Windows PowerShell. -There is no user interface. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPDiagnosticsPerformanceCounter -``` - -This example gets the performance counter settings for front end Web servers and database servers. - -### ------------------EXAMPLE 2------------------ -``` -Get-SPDiagnosticsPerformanceCounter -WebFrontEnd -``` - -This example gets the performance counter settings for front end Web servers. - -### ------------------EXAMPLE 3------------------ -``` -Get-SPDiagnosticsPerformanceCounter -DatabaseServer -``` - -This example gets the performance counter settings for database servers. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseServer -Returns performance counters collected for the database servers in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebFrontEnd -Returns performance counters collected for the front end Web servers in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticsProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticsProvider.md deleted file mode 100644 index ac26ccd7e9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDiagnosticsProvider.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdiagnosticsprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDiagnosticsProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDiagnosticsProvider - -## SYNOPSIS - -Returns a diagnostics provider. - - - -## SYNTAX - -``` -Get-SPDiagnosticsProvider [[-Identity] <SPDiagnosticsProviderPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPDiagnosticsProvider cmdlet reads the specified diagnostics provider. -If the Identity parameter is not specified, this cmdlet returns the collection diagnostics providers in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Get-SPDiagnosticsProvider -``` - -This example returns all the diagnostics providers in the farm. - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPDiagnosticsProvider job-diagnostics-event-log-provider -``` - -This example returns the event log diagnostics provider. - -## PARAMETERS - -### -Identity -Specifies the diagnostics provider to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a diagnostic provider (for example, DiagnosticsProv1); or an instance of a valid SPDiagnosticsProvider object. - -```yaml -Type: SPDiagnosticsProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDistributedCacheClientSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDistributedCacheClientSetting.md deleted file mode 100644 index 255a7e848e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPDistributedCacheClientSetting.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spdistributedcacheclientsetting -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPDistributedCacheClientSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPDistributedCacheClientSetting - -## SYNOPSIS - -Returns distributed cache settings from usage. - - - -## SYNTAX - -``` -Get-SPDistributedCacheClientSetting [-ContainerType] <SPDistributedCacheContainerType> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPDistributedCacheClientSettings cmdlet to return distributed cache settings from usage. -Usage can be any type of cache that the ContainerType parameter specifies. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE-------- -``` -Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache -``` - -This example returns the Distributed Cache client settings for DistributedLogonTokenCache. - -## PARAMETERS - -### -ContainerType - -Specifies the container type to clear. - -The valid values are the following: - --DistributedDefaultCache - --DistributedAccessCache - --DistributedActivityFeedCache - --DistributedBouncerCache - --DistributedLogonTokenCache - --DistributedServerToAppServerAccessTokenCache - --DistributedSearchCache - --DistributedSecurityTrimmingCache - --DistributedActivityFeedLMTCache - --DistributedViewStateCache - - - -```yaml -Type: SPDistributedCacheContainerType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPDistributedCacheClientSetting](Set-SPDistributedCacheClientSetting.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEduServiceSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEduServiceSetting.md deleted file mode 100644 index 9f857518c4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEduServiceSetting.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-speduservicesetting -applicable: SharePoint Server 2013 -title: Get-SPEduServiceSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEduServiceSetting - -## SYNOPSIS -Do not use - -## SYNTAX - -``` -Get-SPEduServiceSetting [-Service] <Services> [-AssignmentCollection <SPAssignmentCollection>] - -Site <SPSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Do not use - -## EXAMPLES - -### Example 1 -``` -Do not use -``` - - - -## PARAMETERS - -### -AssignmentCollection -Do not use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Service -Do not use - -```yaml -Type: Services -Parameter Sets: (All) -Aliases: -Accepted values: Lync, Exchange, StudyGroup -Applicable: SharePoint Server 2013 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Do not use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchAdministrationComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchAdministrationComponent.md deleted file mode 100644 index 48a71ef6ae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchAdministrationComponent.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchadministrationcomponent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchAdministrationComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchAdministrationComponent - -## SYNOPSIS -Returns the administration component for a search service application. - -## SYNTAX - -``` -Get-SPEnterpriseSearchAdministrationComponent [-AssignmentCollection <SPAssignmentCollection>] - -SearchApplication <SearchServiceApplicationPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchAdmininstrationComponent cmdlet retrieves an administration component for a search service application in order to update or delete it. - -For permissions and the most current information about search cmdlets, see the online documentation, [https://go.microsoft.com/fwlink/?LinkId=163185](https://go.microsoft.com/fwlink/?LinkId=163185). - -## EXAMPLES - -### Example 1 -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $ssa -``` - -This example obtains an object reference to the administration component of a search service application named Search Service Application. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the administration component. - -The type must be a valid name (GUID), in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Server.Search.Cmdlet.SearchServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchComponent.md deleted file mode 100644 index e013eb0bd9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchComponent.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcomponent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchComponent - -## SYNOPSIS - -Retrieves one or all search components in a given search topology. - - - -## SYNTAX - -``` -Get-SPEnterpriseSearchComponent [[-Identity] <SearchComponentPipeBind>] - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves the search component with the specified identity from the given search topology. -If an identity is not provided, all search components in the given search topology will be retrieved. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchComponent -SearchTopology '56e6651d-ecdd-4105-bb65-6a83b6155525' -Identity '06e6651d-ecdd-4105-bb65-6a83b6155525' -SearchApplication $ssa -``` - -This example retrieves the search component with the identity 06e6651d-ecdd-4105-bb65-6a83b6155525 from the search topology with identity 56e6651d-ecdd-4105-bb65-6a83b6155525 in the search service application referenced by $ssa. - -### ------------------EXAMPLE 2----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchComponent -SearchTopology '56e6651d-ecdd-4105-bb65-6a83b6155525' -SearchApplication $ssa -``` - -This example retrieves all search components from the search topology with the identity 56e6651d-ecdd-4105-bb65-6a83b6155525 in the search service application referenced by $ssa. - -## PARAMETERS - -### -Identity -Specifies the identity for a search component. - -```yaml -Type: SearchComponentPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology from which to retrieve the search component/search components. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology and search component/search components. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchContentEnrichmentConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchContentEnrichmentConfiguration.md deleted file mode 100644 index 01740214f3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchContentEnrichmentConfiguration.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcontentenrichmentconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchContentEnrichmentConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchContentEnrichmentConfiguration - -## SYNOPSIS - -Returns the content enrichment configuration for the specified search service application. - - - -## SYNTAX - -``` -Get-SPEnterpriseSearchContentEnrichmentConfiguration -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the ContentEnrichmentConfiguration object for the SearchServiceApplication. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchContentEnrichmentConfiguration -SearchApplication $ssa -``` - -This example retrieves the ContentEnrichmentConfiguration object from the default SearchServiecApplication. - -## PARAMETERS - -### -SearchApplication -Specifies the SearchServiceApplication that contains the ContentEnrichmentConfiguration. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPEnterpriseSearchContentEnrichmentConfiguration](Set-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[New-SPEnterpriseSearchContentEnrichmentConfiguration](New-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[Remove-SPEnterpriseSearchContentEnrichmentConfiguration](Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlContentSource.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlContentSource.md deleted file mode 100644 index f92d3209c5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlContentSource.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcrawlcontentsource -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchCrawlContentSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchCrawlContentSource - -## SYNOPSIS -Returns a crawl content source. - -## SYNTAX - -``` -Get-SPEnterpriseSearchCrawlContentSource [[-Identity] <ContentSourcePipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchCrawlContentSource cmdlet reads the content source when the rules of content source are created, updated, or deleted, or reads a CrawlContentSource object when the search functionality is initially configured and after any new content source is added. - -If the Identity parameter is not specified, this cmdlet returns the content source collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $ssa -Identity 'Local SharePoint Sites' -``` - -This example retrieves the default content source for the search service application, 'Search Service Application'. - -## PARAMETERS - -### -Identity -Specifies the content source to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a ContentSource object (for example, ContentSource1); or an instance of a valid ContentSource object. - -```yaml -Type: ContentSourcePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the content source. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlCustomConnector.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlCustomConnector.md deleted file mode 100644 index 7f780c8df3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlCustomConnector.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcrawlcustomconnector -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchCrawlCustomConnector -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchCrawlCustomConnector - -## SYNOPSIS -Returns a CustomConnector object type. - -## SYNTAX - -``` -Get-SPEnterpriseSearchCrawlCustomConnector -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Protocol <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Identity parameter displays a custom connector for a specified Web application. -If no parameters are specified, all the objects of the CustomConnector object type are returned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE---------------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchCrawlCustomConnector -SearchApplication $ssa -Protocol 'http://' -``` - -This example obtains a reference to all custom crawl connectors for the http:// protocol for a search service application named 'Search Service Application'. - -## PARAMETERS - -### -SearchApplication -Specifies the Search application with which the CustomConnector objects are associated. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Protocol -Specifies the string version of the protocol for which to return the CustomConnector object, for example, "dctm://" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlDatabase.md deleted file mode 100644 index 615632c37d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlDatabase.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcrawldatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchCrawlDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchCrawlDatabase - -## SYNOPSIS -Returns a crawl store. - -## SYNTAX - -``` -Get-SPEnterpriseSearchCrawlDatabase [[-Identity] <CrawlStorePipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchCrawlDatabase cmdlet returns a CrawlStore object for use during configuration and when a crawl database for a search service application is modified or deleted. -A crawl database stores crawl history data for a search service application. - -If the Identity parameter is not specified, this cmdlet returns the crawl database collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE------------------- -``` -Get-SPEnterpriseSearchCrawlDatabase -SearchApplication 'Search Service Application' -Identity CrawlDB_1 -``` - -This example gets a reference to the crawl database CrawlDB_1 from the search service application named 'Search Service Application'. - -## PARAMETERS - -### -Identity -Specifies the crawl database to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a CrawlStore object, in the form CrawlStore1; or an instance of a valid CrawlStore object. - -```yaml -Type: CrawlStorePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl database. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlExtension.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlExtension.md deleted file mode 100644 index 0d291b9364..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlExtension.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcrawlextension -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchCrawlExtension -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchCrawlExtension - -## SYNOPSIS -Returns the file types to be included in the content index. - -## SYNTAX - -``` -Get-SPEnterpriseSearchCrawlExtension [[-Identity] <ExtensionPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchCrawlExtension cmdlet returns any or all file extensions in the index for a search application. - -Run this cmdlet at the initial search configuration, and after any new IFilter interface is added to read the rule when you create, update, or delete the extension rule. -If the Identity parameter is not specified, this cmdlet returns the crawl extension collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### Add code example. -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchCrawlExtension -Identity 'pdf' -SearchApplication $ssa -``` - -This example checks whether the pdf file type is included in the file types to be included in the content index. - -## PARAMETERS - -### -Identity -Specifies the file name extension to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid file name extension (for example, .xml); or an instance of a valid CrawlExtension object. - -```yaml -Type: ExtensionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the extension collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlLogReadPermission.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlLogReadPermission.md deleted file mode 100644 index 8347ac0126..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlLogReadPermission.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcrawllogreadpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchCrawlLogReadPermission -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchCrawlLogReadPermission - -## SYNOPSIS -Retrieves the list of users with permission to access the crawl log information. - -## SYNTAX - -``` -Get-SPEnterpriseSearchCrawlLogReadPermission -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -Only the Search Service Application administrator can use the Get-SPEnterpriseSearchCrawlLogReadPermission cmdlet. - -The Search Service Application administrator uses the cmdlet to retrieve a list of users with permission to view the crawl log information. -The administrator can choose to limit this list to users with permission to view crawl log information from a particular tenant. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------EXAMPLE-------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchCrawlLogReadPermission -SearchApplication $ssa -Tenant '00000000-0000-0000-0000-000000000001' -``` - -This example retrieves a list of users who have permission to view the crawl log information for a tenant with id '00000000-0000-0000-0000-000000000001' on the search application referenced by `$ssa`. - -## PARAMETERS - -### -SearchApplication -Specifies the name of the search application for which to list crawl log permissions. -The type must be a valid GUID, of the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the list of users shall be within the scope of this tenant. -The type must be a valid GUID of the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPEnterpriseSearchCrawlLogReadPermission](Set-SPEnterpriseSearchCrawlLogReadPermission.md) - -[Remove-SPEnterpriseSearchCrawlLogReadPermission](Remove-SPEnterpriseSearchCrawlLogReadPermission.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlMapping.md deleted file mode 100644 index 736ac5699f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlMapping.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcrawlmapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchCrawlMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchCrawlMapping - -## SYNOPSIS -Returns a crawl mapping for the search application. - -## SYNTAX - -``` -Get-SPEnterpriseSearchCrawlMapping [[-Identity] <CrawlMappingPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchCrawlMapping cmdlet reads a CrawlMapping object when one of the crawl mapping rules is created, updated, or deleted. -Run this cmdlet when the search is initially configured, and when access is changed through a different mechanism to create the crawl mapping rule; for example, when a rule is changed to use file:\\\\ rather than http://. - -If the Identity parameter is not specified, this cmdlet returns the crawl mapping collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------ EXAMPLE ------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchCrawlMapping -SearchApplication $ssa -``` - -This example returns the crawl mappings for the search application 'Search Service Application'. - -## PARAMETERS - -### -Identity -Specifies the crawl mapping to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://crawlmap1; or an instance of a valid CrawlMapping object. - -```yaml -Type: CrawlMappingPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl mapping collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlRule.md deleted file mode 100644 index c8e75d2d22..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchCrawlRule.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchcrawlrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchCrawlRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchCrawlRule - -## SYNOPSIS -Accesses crawl rules. - -## SYNTAX - -``` -Get-SPEnterpriseSearchCrawlRule [[-Identity] <CrawlRulePipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPEnterpriseSearchCrawlRule cmdlet for a search administrator to run this procedure to retrieve the crawl rule when the crawl rule is updated or deleted. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchCrawlRule -SearchApplication $ssa -Identity https://webAppUrl -``` - -This example uses the `Get-SPEnterpriseSearchCrawlRule` cmdlet to retrieve a crawl rule. - -### ---------------EXAMPLE 2--------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchCrawlRule -SearchApplication $searchApp | ?{$_.Path -like '*example*'} -``` - -This example returns a list of crawl rules with paths that contain the word example from the search service application named 'Search Service Application'. - -## PARAMETERS - -### -Identity -Specifies the search crawl rule path. - -A valid URL, such as "https://webappurl/", or an instance of a valid CrawlRule object - -```yaml -Type: CrawlRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl rule. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchFileFormat.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchFileFormat.md deleted file mode 100644 index 0facc5c488..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchFileFormat.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchfileformat -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchFileFormat -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchFileFormat - -## SYNOPSIS - -Retrieves all parseable file formats. - - - -## SYNTAX - -``` -Get-SPEnterpriseSearchFileFormat [[-Identity] <DocumentParserFileFormatPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION - -The Get-SPEnterpriseSearchFileFormat cmdlet returns the file format information for a given format ID. -If no format ID is provided, the cmdlet returns all the parseable file formats. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### -------------EXAMPLE 1------------- -``` -C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchFileFormat -SearchApplication $ssa -``` - -This example uses the Get-SPEnterpriseSearchFileFormat to retrieve all parseable file formats in the search service application referenced by $ssa. - -### -------------EXAMPLE 2------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchFileFormat -SearchApplication $ssa -Identity DOCX -``` - -This example uses the Get-SPEnterpriseSearchFileFormat cmdlet to retrieve information about the file format DOCX in the search service application referenced by `$ssa`. - -## PARAMETERS - -### -Identity -Specifies the format ID for which to retrieve file format information. - -```yaml -Type: DocumentParserFileFormatPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication - -Specifies the search application for which to retrieve file format information. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchFileFormat](New-SPEnterpriseSearchFileFormat.md) - -[Set-SPEnterpriseSearchFileFormatState](Set-SPEnterpriseSearchFileFormatState.md) - -[Remove-SPEnterpriseSearchFileFormat](Remove-SPEnterpriseSearchFileFormat.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchHostController.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchHostController.md deleted file mode 100644 index 442c30dddf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchHostController.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchhostcontroller -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchHostController -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchHostController - -## SYNOPSIS -Lists the specified or all search host controllers in the farm. - -## SYNTAX - -``` -Get-SPEnterpriseSearchHostController [-AssignmentCollection <SPAssignmentCollection>] - [-SearchServiceInstance <SearchServiceInstancePipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet lists the specified or all SearchHostControllers in the farm. -The SearchHostController is related to the SearchServiceInstance, where the SearchHostController manages the search components that run on a server, and maintains a local repository for linguistic dictionaries. -The search components retrieve the linguistic dictionaries from the PrimaryHostController. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPEnterpriseSearchHostController -``` - -This example retrieves a list of all HostControllers in the farm with their status (primary/secondary) and repository version. - -### ------------------EXAMPLE 2------------------ -``` -$ssi = Get-SPEnterpriseSearchServiceInstance -Local -Get-SPEnterpriseSearchHostController -SearchServiceInstance $ssi -``` - -This example retrieves the status information for the SearchHostController on the local server. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchServiceInstance -The Search Service instance of the server from where the SearchHostController object is returned. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLanguageResourcePhrase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLanguageResourcePhrase.md deleted file mode 100644 index 66420d285c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLanguageResourcePhrase.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchlanguageresourcephrase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchLanguageResourcePhrase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchLanguageResourcePhrase - -## SYNOPSIS -Returns a language resource phrase. - -## SYNTAX - -``` -Get-SPEnterpriseSearchLanguageResourcePhrase [-AssignmentCollection <SPAssignmentCollection>] - [-Identity <LanguageResourcePhrasePipeBind>] [-Language <String>] [-Mapping <String>] - -Owner <SearchObjectOwner> -SearchApplication <SearchServiceApplicationPipeBind> [-SourceId <Guid>] - [-Type <LanguageResourceType>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchLanguageResourcePhrase cmdlet reads a LanguageResourcePhrase object when the language resource phrase is created or deleted. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication 'Search Service Application' -Get-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $ssa -Language 'en-us' -Type QuerySuggestionBlockList -``` - -This example returns all language resource entries for the en-us language in the QuerySuggestionBlockList type. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity - -Specifies the language resource phrase to get. - -The type must be a string; a valid name of a language resource phrase (for example, LanguageResourcePhrase1); or an instance of a valid LanguageResourcePhrase object. - - - -```yaml -Type: LanguageResourcePhrasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language - -Filters to return phrases of a specified source language. - -The type must be a valid name of a language; for example, en-us or ja-jp. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mapping - -Allows a term or phrase to be mapped to another term or phrase. -For example, the nickname "John" could be mapped to "Jonathan". - -This parameter only applies to nicknames and substitutions. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner - -Specifies the search object owner that defines the scope at which the corresponding LanguageResourcePhrase is created. - -The owner must be one of the following valid levels: - -- Search Service Application -- Site Subscription -- Site Collection -- Site - - - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication - -Specifies the search application that contains the language resources. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SourceId - -Identifies the search result source for which the LanguageResourcePhrase applies to. - - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type - -Filters to return phrases of a specified type. - -The type must be one of the following valid types of phrases: - -- QuerySuggestionBlockList -- QuerySuggestionAlwaysSuggest -- Nickname -- QuerySuggestionSubstitution - - - -```yaml -Type: LanguageResourceType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLinguisticComponentsStatus.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLinguisticComponentsStatus.md deleted file mode 100644 index acfeaaf934..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLinguisticComponentsStatus.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchlinguisticcomponentsstatus -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchLinguisticComponentsStatus -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchLinguisticComponentsStatus - -## SYNOPSIS -Returns the status of the linguistic query and document processing components. - -## SYNTAX - -``` -Get-SPEnterpriseSearchLinguisticComponentsStatus [[-Identity] <LinguisticComponentsStatusPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns an object that represents the operational status of the linguistic query and document processing components. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SpEnterpriseSearchLinguisticComponentsStatus -SearchApplication $ssa -``` - -This example gets the current status of the linguistic query and document processing components from the default SearchServiceApplication. - -## PARAMETERS - -### -Identity -An object that represents the current status of the linguistic components. - -```yaml -Type: LinguisticComponentsStatusPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the linguistic processing components. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPEnterpriseSearchLinguisticComponentsStatus](Set-SPEnterpriseSearchLinguisticComponentsStatus.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLinksDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLinksDatabase.md deleted file mode 100644 index cfdf54b159..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchLinksDatabase.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchlinksdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchLinksDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchLinksDatabase - -## SYNOPSIS -Retrieves a reference to a links database. - -## SYNTAX - -``` -Get-SPEnterpriseSearchLinksDatabase [[-Identity] <LinksStorePipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchLinksDatabase cmdlet returns a LinksStore object for use during configuration and when a links database for a search service application is modified or deleted. -A links database stores query logging and search analytics data for a search service application. -If the Identity parameter is not specified, this cmdlet returns all links databases for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------EXAMPLE--------- -``` -Get-SPEnterpriseSearchLinksDatabase -Identity LinksDB_1 -SearchApplication 'Search Service Application' -``` - -This example gets a reference to the links database LinksDB_1 from the search service application 'Search Service Application'. - -## PARAMETERS - -### -Identity -Specifies the links database to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a LinksStore object, in the form LinksStore1; or an instance of a valid LinksStore object. - -```yaml -Type: LinksStorePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the links database. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchLinksDatabase](New-SPEnterpriseSearchLinksDatabase.md) - -[Set-SPEnterpriseSearchLinksDatabase](Set-SPEnterpriseSearchLinksDatabase.md) - -[Remove-SPEnterpriseSearchLinksDatabase](Remove-SPEnterpriseSearchLinksDatabase.md) - -[Move-SPEnterpriseSearchLinksDatabases](Move-SPEnterpriseSearchLinksDatabases.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataCategory.md deleted file mode 100644 index e08022db6a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataCategory.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchmetadatacategory -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchMetadataCategory -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchMetadataCategory - -## SYNOPSIS -Returns a crawled property category. - -## SYNTAX - -``` -Get-SPEnterpriseSearchMetadataCategory [[-Identity] <CategoryPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-SiteCollection <Guid>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads a MetadataCategory object when the category is created, updated, or deleted. -You should run this cmdlet when the initial search is configured, and after a new crawled property category is discovered during a crawl. -SPEnterpriseSearchMetadataCategory represents a category in the enterprise search metadata property schema. - -If the Identity parameter is not specified, this cmdlet returns the metadata category collection for the specified search service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchMetadataCategory -SearchApplication $ssa -``` - -This example retrieves the metadata category collection of a search service application for the default search service application. - -## PARAMETERS - -### -Identity -Specifies the metadata category to retrieve. - -The type must a valid search application name, for example, MetadataCategory1, or an instance of a valid Category object. - -```yaml -Type: CategoryPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the enterprise search metadata categories. - -The type must a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the metadata categories returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the metadata categories returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataCrawledProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataCrawledProperty.md deleted file mode 100644 index f5ecaf0880..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataCrawledProperty.md +++ /dev/null @@ -1,233 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchmetadatacrawledproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchMetadataCrawledProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchMetadataCrawledProperty - -## SYNOPSIS -Returns a crawled property. - -## SYNTAX - -``` -Get-SPEnterpriseSearchMetadataCrawledProperty [-AssignmentCollection <SPAssignmentCollection>] - [-Category <CategoryPipeBind>] [-Limit <String>] [-Name <String>] [-PropSet <Guid>] - -SearchApplication <SearchServiceApplicationPipeBind> [-SiteCollection <Guid>] [-Tenant <Guid>] - [-VariantType <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads a CrawledProperty object for a crawled property that was created or updated. -You should run this cmdlet when the search functionality is configured for the first time, and after new crawled properties are discovered during a crawl. -If the Name parameter is not specified, this cmdlet returns all crawled properties for the specified category for the specified search application. -If neither the Name nor the Category parameter is specified, this cmdlet returns all crawled properties for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $ssa -Identity People -Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Category $cat -Limit 1 -``` - -This example returns the first crawled property in the PeopleSearch_Scope metadata category for the default search service application. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Category - -Specifies the metadata category of the crawled property to return. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a metadata category, for example, MetadataCategory1, or an instance of a valid Category object. - -```yaml -Type: CategoryPipeBind -Parameter Sets: (All) -Aliases: c -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit - -Specifies the maximum number of items to return. - -Specify ALL to return all possible results. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the crawled property to retrieve. - -The type must be a valid crawled property name, for example "urn:schemas-microsoft-com:sharepoint:portal:profile:UserName" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropSet - -Specifies to return crawled properties that use the specified property set. -A property set belongs to one crawled property category. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: p -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication - -Specifies the search application that contains the crawled property. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteCollection - -Specifies that the crawled properties returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -Specifies that the crawled properties returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VariantType - -Specifies to return crawled properties that use the specified variant type. - -The type must be an integer that specifies the variant data type of the property set. - - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: vt -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataManagedProperty.md deleted file mode 100644 index 83ba6b7622..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataManagedProperty.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchmetadatamanagedproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchMetadataManagedProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchMetadataManagedProperty - -## SYNOPSIS -Returns a managed property. - -## SYNTAX - -``` -Get-SPEnterpriseSearchMetadataManagedProperty [[-Identity] <ManagedPropertyPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Limit <String>] [-SiteCollection <Guid>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads a ManagedProperty object for managed properties that are created or updated. - -If the Identity parameter is not specified, this cmdlet returns the managed property collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $ssa -Identity UserName -``` - -This example retrieves the managed property UserName from the default search service application. - -## PARAMETERS - -### -Identity -Specifies the managed property to retrieve. - -The type must be a valid name of metadata property, for example MetadataProperty1, or an instance of a valid ManagedProperty object. - -```yaml -Type: ManagedPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the managed property collection. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Limit -Specifies the maximum number of managed properties to return. -Specify ALL to return all possible results. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the managed properties returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the managed properties returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataMapping.md deleted file mode 100644 index 8588027800..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataMapping.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchmetadatamapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchMetadataMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchMetadataMapping - -## SYNOPSIS -Returns the current status of a managed property mapping. - -## SYNTAX - -``` -Get-SPEnterpriseSearchMetadataMapping -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CrawledProperty <CrawledPropertyPipeBind>] - [-ManagedProperty <ManagedPropertyPipeBind>] [-SiteCollection <Guid>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads a Mapping object when a managed property mapping is created, updated, or deleted. -SPEnterpriseSearchMetadataMapping represents a category of a mapping between a managed property and one or more crawled properties in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $ssa -Identity UserName -Get-SPEnterpriseSearchMetadataMapping -SearchApplication $ssa -ManagedProperty $mp -``` - -This example lists all crawled properties mapped to the managed property UserName for the default search service application. - -## PARAMETERS - -### -SearchApplication -Specifies the search application that contains the metadata mapping. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CrawledProperty -Specifies the crawled property from which to return mappings. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid URL in the form https://server_name, or an instance of a valid CrawledProperty object. - -```yaml -Type: CrawledPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -Specifies the managed property from which to return mappings. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a managed property, for example, ManagedProperty1, or an instance of a valid ManagedProperty object. - -```yaml -Type: ManagedPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the metadata mappings returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the metadata mappings returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchOwner.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchOwner.md deleted file mode 100644 index 25a4d5de21..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchOwner.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchowner -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchOwner -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchOwner - -## SYNOPSIS -Retrieves the search object owner. - -## SYNTAX - -``` -Get-SPEnterpriseSearchOwner [[-Identity] <SearchObjectOwner>] -Level <SearchObjectLevel> - [-AssignmentCollection <SPAssignmentCollection>] [-SPWeb <SPWebPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchOwner cmdlet retrieves the search object owner. -Get-SPEnterpriseSearchOwner provides scoping context to other cmdlets such as SPEnterpriseSearchResultItemType. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------EXAMPLE-------- -``` -Get-SPEnterpriseSearchOwner -Level SPSite -``` - -This example shows how to retrieve the tenant owner of a search object at the SPSite level. - -## PARAMETERS - -### -Identity -Specifies the search object owner to retrieve. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Level -Specifies whether the owner object resides at the SPWeb, SPSite, SPSite Subscription, or SSA level. - -```yaml -Type: SearchObjectLevel -Parameter Sets: (All) -Aliases: l -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SPWeb -Specifies the SPWeb or SPSite in which this object resides. -It is only needed if Level is equal to SPWeb or SPSite. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchPropertyRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchPropertyRule.md deleted file mode 100644 index 1a13012b5e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchPropertyRule.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchpropertyrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchPropertyRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchPropertyRule - -## SYNOPSIS -Returns a property rule instance, which can be used in result item types. - -## SYNTAX - -``` -Get-SPEnterpriseSearchPropertyRule [-PropertyName] <String> [-Operator] <DefaultOperator> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchPropertyRule cmdlet returns an instance of a property rule, given the specified condition. -The value for the condition is set in a separate step. -Such a rule can be used in result item types, to group the results based on the condition of a result property. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------EXAMPLE-------- -``` -$rule = Get-SPEnterpriseSearchPropertyRule -PropertyName 'ContentTypeId' -Operator 'StartsWith' -$rule.AddValue('0x010063C2F478ACC511DFB869B5BFDFD720851252') -``` - -This example returns a rule for the property "ContentTypeId", where the condition is that the property shall start with a specific value. - -The second step specifies the value that the property shall start with. - -## PARAMETERS - -### -PropertyName -Specifies the name of the property that the rule concerns. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operator -Specifies the operation to apply to the property, for example "Starts with". - -```yaml -Type: DefaultOperator -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchPropertyRuleCollection](Get-SPEnterpriseSearchPropertyRuleCollection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchPropertyRuleCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchPropertyRuleCollection.md deleted file mode 100644 index eeb67cf938..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchPropertyRuleCollection.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchpropertyrulecollection -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchPropertyRuleCollection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchPropertyRuleCollection - -## SYNOPSIS -Returns the collection of rules that are applied to search results. - -## SYNTAX - -``` -Get-SPEnterpriseSearchPropertyRuleCollection [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchPropertyRuleCollection cmdlet returns the collection of rules that are applied to search results. -Rules can be added and removed from the rule collection. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------EXAMPLE-------- -``` -$rule = Get-SPEnterpriseSearchPropertyRule -PropertyName 'ContentTypeId' -Operator 'StartsWith' -$rule.AddValue('0x010063C2F478ACC511DFB869B5BFDFD720851252') -$ruleCollection = Get-SPEnterpriseSearchPropertyRuleCollection -$ruleCollection.Add($rule) -``` - -This example returns a rule for the result property "ContentTypeId", the rule specifies that this property must start with the value "0x010063C2F478ACC511DFB869B5BFDFD720851252". - -Thereafter the example returns the rule collection, and adds the rule to the rule collection. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchPropertyRule](Get-SPEnterpriseSearchPropertyRule.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsService.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsService.md deleted file mode 100644 index d27ad04446..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsService.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchqueryandsitesettingsservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryAndSiteSettingsService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryAndSiteSettingsService - -## SYNOPSIS -Returns the search manager service. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryAndSiteSettingsService [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryAndSiteSettingsService cmdlet returns a manager service. -A manager service is the endpoint for the search service application to process queries and site administration requests from the search service application proxy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$qssService = Get-SPEnterpriseSearchQUeryAndSiteSettingsService -``` - -This example obtains a reference to the query and site settings service. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md deleted file mode 100644 index 739441c566..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchqueryandsitesettingsserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance - -## SYNOPSIS -Returns the service manager service instance. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance - [[-Identity] <SearchQueryAndSiteSettingsServiceInstancePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Local] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance cmdlet returns the service manager service instance when a search manager service is started or stopped. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -C:\PS>$qqssSvcInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local -``` - -This example obtain a reference to the query and site setting service instance on the local farm. - -### ------------------EXAMPLE 2------------------ -``` -C:\PS>$qssSvcInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity myServer -``` - -This example obtain a reference to the query and site setting service instance from a specific server name. - -## PARAMETERS - -### -Identity -Specifies the search manager service instance to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid server name on which search manager service instance runs; or an instance of a valid SearchManagerServiceInstance object. - -```yaml -Type: SearchQueryAndSiteSettingsServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Local -Specifies that the service manager service instance for the current search server is returned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy.md deleted file mode 100644 index 4c33dfe508..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchqueryandsitesettingsserviceproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy - -## SYNOPSIS -Returns the search manager service proxy. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy cmdlet reads the SearchQueryAndSiteSettingsServiceProxy object when a search Web service manager service is started or stopped. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$qssSvcProxy = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy -``` - -This example obtains a reference to the query and site settings service proxy. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAuthority.md deleted file mode 100644 index f8420a5639..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryAuthority.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchqueryauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryAuthority -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryAuthority - -## SYNOPSIS -Returns an authoritative page. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryAuthority [[-Identity] <AuthorityPagePipeBind>] -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryAuthority cmdlet reads a QueryAuthority object when the authoritative page is created or deleted or when the query rank is modified. - -If the Identity parameter is not specified, this cmdlet returns the authority page collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -Get-SPEnterpriseSearchQueryAuthority -Identity 'https://contoso.com/' -SearchApplication $ssa -``` - -This example obtains the authoritative page for the URL https://contoso.com from the search service application named 'Search Service Application'. - -### ------------------EXAMPLE 2------------------ -``` -Get-SPEnterpriseSearchQueryAuthority -SearchApplication 'Search Service Application' -``` - -This example obtains the collection of query authority pages from a search service application named 'Search Service Application'. - -## PARAMETERS - -### -Identity -Specifies the query authority to get. - -The type must be a valid URL, in the form https://server_name; or an instance of a valid AuthorityPage object. - -```yaml -Type: AuthorityPagePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding Query Authority is created.The owner must be one of the following valid levels:- Search Service Application- Site Subscription - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the authority page to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryDemoted.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryDemoted.md deleted file mode 100644 index 146216ab96..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryDemoted.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchquerydemoted -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryDemoted -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryDemoted - -## SYNOPSIS -Returns a demoted site rule. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryDemoted [[-Identity] <DemotedPipeBind>] -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryDemoted cmdlet reads the DemotedSite object when a demoted site rule is created or deleted, or when the demoted site rule is updated to modify the query rank. - -If the Identity parameter is not specified, this cmdlet returns the demoted site rule collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$demotedRule = Get-SPEnterpriseSearchQueryDemoted -Identity https://somesite.com -SearchApplication 'Search Service Application' -Remove-SPEnterpriseSearchQueryDemoted -Identity $demotedRule -SearchApplication 'Search Service Application' -``` - -This example obtains a reference to a site demotion rule for the URL https://somesite.com, and removes it. - -## PARAMETERS - -### -Identity -Specifies the demoted site rule to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance a valid Demoted object. - -```yaml -Type: DemotedPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding Demoted object is created.The owner must be one of the following valid levels:- Search Service Application- Site Subscription - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the demoted site rule collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryKeyword.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryKeyword.md deleted file mode 100644 index f279cbb104..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryKeyword.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchquerykeyword -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryKeyword -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryKeyword - -## SYNOPSIS -Returns a keyword term. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryKeyword [[-Identity] <KeywordPipeBind>] -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryKeyword cmdlet reads a QueryKeyword object when the keyword rule is created, updated, or deleted. - -If the Identity parameter is not specified, this cmdlet returns the query keyword collection from the specified search application. - -You can use this cmdlet for keywords in site collections that are in SharePoint Server mode. -You cannot use this cmdlet after a site collection is upgraded to SharePoint Server mode because keywords and Best Bets are automatically migrated to query rules. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchQueryKeyword -Identity Engineering -Site https://myserver/sites/engineering | Set-SPEnterpriseSearchQueryKeyword -StartDate "12/25/2009" -EndDate "12/24/2010" -Site https://myserver/sites/engineering -``` - -This example gets a reference to the keyword with the term Engineering from the site https://myserver/sites/engineering and sets the start dates and end dates for the keyword. - -## PARAMETERS - -### -Identity -Specifies the keyword term to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid string that contains a keyword term (for example, KeywordTerm1); or an instance of a valid Keyword object. - -```yaml -Type: KeywordPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Filters to return keywords with the specified results URL. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryScope.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryScope.md deleted file mode 100644 index 17e4f0e171..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryScope.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchqueryscope -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryScope -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryScope - -## SYNOPSIS -Returns a query results scope. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryScope [[-Identity] <ScopePipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Url <Uri>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryScope cmdlet reads a QueryScope object when the shared scope is created or deleted, or when the definition of the shared scope is updated. - -If the Identity parameter is not specified, this cmdlet returns the query scope collection from the specified search application. - -In SharePoint Server, result sources provide the functionality that scopes provided in SharePoint Server. - -During an upgrade from SharePoint Server, to retain legacy settings, shared scopes are automatically migrated. -However, these scopes are read-only after the migration. -This cmdlet can be used to read a shared scope that has been migrated. - -During an upgrade from SharePoint Server, to preserve legacy settings, local scopes are also automatically migrated when the corresponding sites or site collections are migrated. -In a SharePoint Server farm, the scopes of a site or site collection that is in SharePoint Server mode are read-write, whereas the scopes of a site or site collection after upgrade to SharePoint Server mode are read-only. -This cmdlet can be used to read a migrated local scope in either situation. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPenterpriseSearchServiceApplication -Identity 'Search service Application' -Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa | Set-SPEnterpriseSearchQueryScope -Description "Business critical sites to index" -CompilationType 1 -AlternateResultsPage https://altServer -``` - -This example obtains a reference to the scope named MustCrawl on the search application named MySSA, and changes the description, compilation type, and alternate access URL. - -## PARAMETERS - -### -Identity -Specifies the results scope to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope (for example, Scope1); or an instance of a valid Scope object. - -```yaml -Type: ScopePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -Filters to return scopes for the specified results URL. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryScopeRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryScopeRule.md deleted file mode 100644 index 7ad1e92322..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQueryScopeRule.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchqueryscoperule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQueryScopeRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQueryScopeRule - -## SYNOPSIS -Returns a shared scope rule. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQueryScopeRule [[-Identity] <ScopeRulePipeBind>] -Scope <ScopePipeBind> [-Url <Uri>] - [-AssignmentCollection <SPAssignmentCollection>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchQueryScopeRule cmdlet reads a QueryScopeRule object when the shared scope rule is created, updated, or deleted. -SPEnterpriseSearchQueryScopeRule represents a query result scope rule that can be applied to a scope. - -In SharePoint Server, result sources provide the functionality that scopes provided in SharePoint Server. - -During an upgrade from SharePoint Server, to retain legacy settings, shared scopes are automatically migrated. -However, these scopes are read-only after the migration. -This cmdlet can be used to read a scope rule of a shared scope that has been migrated. - -During an upgrade from SharePoint Server, to preserve legacy settings, local scopes are also automatically migrated when the corresponding sites or site collections are migrated. -In a SharePoint Server farm, the scopes of a site or site collection that is in SharePoint Server mode are read-write, whereas the scopes of a site or site collection after upgrade to SharePoint Server mode are read-only. -This cmdlet can be used to read a scope rule of a migrated local scope in either situation. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa -Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url https://criticalSite | Set-SPEnterpriseSearchQueryScopeRule -Url https://criticalSite -UrlScopeRuleType Url -``` - -This example gets a reference to a scope rule for the URL https://criticalSite, and sets its rule type to URL. - -## PARAMETERS - -### -Identity -Specifies the scope rule to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope rule (for example, ScopeRule1); or an instance of a valid ScopeRule object. - -```yaml -Type: ScopeRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Returns query scope rules for the specified scope. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope (for example, Scope1); or an instance of a valid Scope object. - -```yaml -Type: ScopePipeBind -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The type must be a valid URL, in the form https://server_name. - -Returns query scope rules for the specified results URL. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope rule collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQuerySpellingCorrection.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQuerySpellingCorrection.md deleted file mode 100644 index ccb2e8663a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQuerySpellingCorrection.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchqueryspellingcorrection -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQuerySpellingCorrection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQuerySpellingCorrection - -## SYNOPSIS -Returns the object that exposes the Query Spelling Correction (QSC) configuration. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQuerySpellingCorrection [[-Identity] <QuerySpellingCorrectionPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the object that exposes the QSC configuration parameters. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchQuerySpellingCorrection -SearchApplication $ssa -``` - -Returns the current configuration for the Query Spelling Correction component for the default search service application. - -## PARAMETERS - -### -Identity -Specifies an object that represents the current status for the query spelling correction. - -```yaml -Type: QuerySpellingCorrectionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication - -Specifies the search service application that contains the query spelling correction parameters. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQuerySuggestionCandidates.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQuerySuggestionCandidates.md deleted file mode 100644 index d4dae54fe2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchQuerySuggestionCandidates.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchquerysuggestioncandidates -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchQuerySuggestionCandidates -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchQuerySuggestionCandidates - -## SYNOPSIS -Returns a list of queries. - -## SYNTAX - -``` -Get-SPEnterpriseSearchQuerySuggestionCandidates -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-SourceId <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPEnterpriseSearchQuerySuggestionCandidates cmdlet to return a list of popular queries that can be displayed in a related queries Web Part. -The list gives the administrator a chance to review potential queries and add some of them to the related queries list. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE------------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchQuerySuggestionCandidates -SearchApplication $ssa -``` - -This example returns popular search queries by using the search application contained in the variable $searchapp. - -## PARAMETERS - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding LanguageResourcePhrase is created. - -The owner must be one of the following valid levels: - -- Search Service Application -- Site Subscription -- Site Collection -- Site - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query topology. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SourceId -Identifies the search result source for which the LanguageResourcePhrase applies to. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchRankingModel.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchRankingModel.md deleted file mode 100644 index d614222535..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchRankingModel.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchrankingmodel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchRankingModel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchRankingModel - -## SYNOPSIS -Returns a ranking model. - -## SYNTAX - -``` -Get-SPEnterpriseSearchRankingModel [[-Identity] <RankingModelPipeBind>] -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads the RankingModel object when a ranking model is created, removed, or updated. - -If the Identity parameter is not specified or the identity does not match any of the ranking models in the collection, all rank models for the search application are returned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -$owner = Get-SPEnterpriseSearchOwner -Level ssa -Get-SPEnterpriseSearchRankingModel -Identity '8f6fd0bc-06f9-43cf-bbab-08c377e083f4' -SearchApplication $ssa -Owner $owner -``` - -This example retrieves the ranking model on the search service application level with the identity 8f6fd0bc-06f9-43cf-bbab-08c377e083f4 for the search application Search Service Application. - -### ------------------EXAMPLE 2------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" -$owner = Get-SPEnterpriseSearchOwner -Level ssa -Get-SPEnterpriseSearchRankingModel -SearchApplication $ssa -Owner $owner -``` - -This example retrieves all ranking models defined on the search service application level for the search application Search Service Application. - -## PARAMETERS - -### -Identity -Specifies the ranking model to retrieve. - -The type must be a valid GUID in the form 8f6fd0bc-06f9-43cf-bbab-08c377e083f4, or an instance of a valid RankingModel object. - -```yaml -Type: RankingModelPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the scope where the ranking model is available. -The available scopes are: SSA, Tenant, Site Collection or Site. -A ranking model can be available in multiple scopes. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the ranking model. - -The type must be a valid GUID in the form 9bf36458-fc99-4f7b-b060-867e5a63adce, a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchResultItemType.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchResultItemType.md deleted file mode 100644 index 2e72f90c7e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchResultItemType.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchresultitemtype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchResultItemType -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchResultItemType - -## SYNOPSIS -Retrieves result item types. - -## SYNTAX - -``` -Get-SPEnterpriseSearchResultItemType [[-Identity] <ResultItemTypePipeBind>] -Owner <SearchObjectOwner> - [-AssignmentCollection <SPAssignmentCollection>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [-SearchApplicationProxy <SearchServiceApplicationProxyPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION - -The Get-SPEnterpriseSearchResultItemType cmdlet retrieves the result item types that exist for the specified owner. - -Result item types enable you to change the look of search results based on the type of result. -You start by defining a collection of rules, which will be evaluated against the properties of results. -Then you define the display template to use for rendering that type of result. -Once you have created the result item type, results matching the rules of the result item type will render using the specified display template. - -Example use cases: - -- Change the look of results for a particular file name extension, for example Word documents. -- Change the look of a particular content type in search results. -- Change the look of results from a particular author. -- Add a result action to results from a particular result source as part of a custom search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### --------EXAMPLE-------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$tenantOwner = Get-SPEnterpriseSearchOwner -Level SPSite -Get-SPEnterpriseSearchResultItemType -Owner $tenantOwner -SearchApplication $ssa -``` - -This example retrieves the result item types that are defined for the owner referenced by $tenantowner for the search application referenced by $ssa. - -Although SearchApplication and SearchApplicationProxy are optional parameters, this cmdlet requires use of one of them. - -## PARAMETERS - -### -Identity -Specifies the result item type to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: ResultItemTypePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the result item type is created. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the name of the search application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplicationProxy -Specifies the proxy of the search application that contains the result item type. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application proxy name (for example, SearchAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchResultItemType](New-SPEnterpriseSearchResultItemType.md) - -[Set-SPEnterpriseSearchResultItemType](Set-SPEnterpriseSearchResultItemType.md) - -[Remove-SPEnterpriseSearchResultItemType](Remove-SPEnterpriseSearchResultItemType.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchResultSource.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchResultSource.md deleted file mode 100644 index 82f66827e3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchResultSource.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchresultsource -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchResultSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchResultSource - -## SYNOPSIS -Retrieves a result source. - -## SYNTAX - -``` -Get-SPEnterpriseSearchResultSource [[-Identity] <ResultSourcePipeBind>] -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet retrieves a result source object. - -If the Identity parameter is not specified, this cmdlet returns the result source collection for the specified search object owner. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831] (https://go.microsoft.com/fwlink/p/?LinkId=251831). - - - -## EXAMPLES - -### -------------- Example 1: Get result source by name -------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -$owner = Get-SPEnterpriseSearchOwner -Level SSA -Get-SPEnterpriseSearchResultSource -Identity "Local SharePoint Results" -SearchApplication $ssa -Owner $owner -``` - -This example retrieves the search service application level result source with the name "Local SharePoint Results". - - -### -------------- Example 2: Get result source by id -------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -$owner = Get-SPEnterpriseSearchOwner -Level SSA -Get-SPEnterpriseSearchResultSource -Identity 8413cd39-2156-4e00-b54d-11efd9abdB89 -SearchApplication $ssa -Owner $owner -``` - -This example retrieves the search service application level result source with the id 8413cd39-2156-4e00-b54d-11efd9abdB89. - -### -------------- Example 3: Get all result sources under SSA -------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -$owner = Get-SPEnterpriseSearchOwner -Level SSA -Get-SPEnterpriseSearchResultSource -SearchApplication $ssa -Owner $owner -``` - -This example retrieves all the search service application level result sources. - -## PARAMETERS - -### -Identity -Specifies the result source to retrieve. - -The type must be a valid GUID string, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a result source (for example, "Local SharePoint Results"); or an instance of a valid Source object. - -If not specified, the result source collection for the specified search object owner is returned. - -```yaml -Type: ResultSourcePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding result source is available. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchResultSource](New-SPEnterpriseSearchResultSource.md) - -[Set-SPEnterpriseSearchResultSource](Set-SPEnterpriseSearchResultSource.md) - -[Remove-SPEnterpriseSearchResultSource](Remove-SPEnterpriseSearchResultSource.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchSecurityTrimmer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchSecurityTrimmer.md deleted file mode 100644 index 39a272f003..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchSecurityTrimmer.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchsecuritytrimmer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchSecurityTrimmer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchSecurityTrimmer - -## SYNOPSIS -Returns a custom security trimmer. - -## SYNTAX - -``` -Get-SPEnterpriseSearchSecurityTrimmer [[-Identity] <SecurityTrimmerPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the SecurityTrimmer. -A custom security trimmer trims search results before the results are returned to the user. - -If the Identity parameter is not specified, this cmdlet returns the security trimmer collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -Get-SPEnterpriseSearchSecurityTrimmer -SearchApplication $ssa -``` - -This example obtains the pluggable security trimmers registered in the search service application MySSA. - -## PARAMETERS - -### -Identity -Specifies the pluggable security trimmer used for the specified search application. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid SecurityTrimmer object. - -```yaml -Type: SecurityTrimmerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the security trimmer. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchService.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchService.md deleted file mode 100644 index 4aad1b460b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchService.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchService - -## SYNOPSIS -Returns the search service for the farm. - -## SYNTAX - -``` -Get-SPEnterpriseSearchService [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the SearchService object when the search service is updated or deleted. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchService -``` - -This example obtains a reference to the search service of the current farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index 5427955667..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Returns the search service application for a farm. - -## SYNTAX - -``` -Get-SPEnterpriseSearchServiceApplication [[-Identity] <SearchServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves the SearchServiceApplication object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchServiceApplication -Identity 'Search Service Application' -``` - -This example obtains a reference to a search service application named 'Search Service Application'. - -## PARAMETERS - -### -Identity -Specifies the search service application to retrieve. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a search service application (for example, MySearchApp); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplicationBackupStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplicationBackupStore.md deleted file mode 100644 index b174b19b04..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplicationBackupStore.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchserviceapplicationbackupstore -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchServiceApplicationBackupStore -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchServiceApplicationBackupStore - -## SYNOPSIS - -Retrieves information about the search service application backup files. - - - -## SYNTAX - -``` -Get-SPEnterpriseSearchServiceApplicationBackupStore [-BackupFolder] <String> [-Name] <String> - [[-BackupId] <String>] [-UseMostRecent] [-IsVerbose] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet returns information about the search databases and index files in a specified search service application backup location. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------- -``` -Get-SPEnterpriseSearchServiceApplicationBackupStore -BackupFolder \\sample\backup -Name "Search Service Application" -BackupId 3222ad97-91ad-471f-a764-780ec1f05f74 -``` - -This example retrieves the backup of the search databases and index files that are located at \\\\sample\backup with the backup id 3222ad97-91ad-471f-a764-780ec1f05f74 from the search service application Search Service Application. - -### ------------------EXAMPLE 2----------------- -``` -Get-SPEnterpriseSearchServiceApplicationBackupStore -BackupFolder \\sample\backup -Name "Search Service Application" -UseMostRecent -``` - -This example retrieves the most recently taken backup of the search databases and index files that are located at \\\\sample\backup from the search service application Search Service Application. - -## PARAMETERS - -### -BackupFolder -Specifies the full file path of the backup files. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the name of the search service application from which to retrieve the related backup information. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BackupId -Specifies the GUID of the backup in the referred package. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -UseMostRecent -A switch to specify if the most recent backup should be used. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsVerbose -A switch to specify if messages should be printed out when the cmdlet is running. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplicationProxy.md deleted file mode 100644 index 42d12983ab..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceApplicationProxy.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchServiceApplicationProxy - -## SYNOPSIS -Returns the search service application proxy. - -## SYNTAX - -``` -Get-SPEnterpriseSearchServiceApplicationProxy [[-Identity] <SearchServiceApplicationProxyPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads the SearchServiceApplicationProxy object when the search service application proxy is created updated or deleted. -If the Identity parameter is not specified, this cmdlet returns the search service application proxy collection for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$proxy = Get-SPEnterpriseSearchServiceApplicationProxy -Identity 'Search Service Application Proxy' -``` - -This example obtains a reference to a search service application proxy with the name 'Search Service Application Proxy'. - -## PARAMETERS - -### -Identity -Specifies the search service application proxy to retrieve. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a search service application proxy (for example, SearchServiceAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceInstance.md deleted file mode 100644 index d6b11a6d9d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchServiceInstance.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchServiceInstance - -## SYNOPSIS -Returns the search service instance for a farm. - -## SYNTAX - -``` -Get-SPEnterpriseSearchServiceInstance [[-Identity] <SearchServiceInstancePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Local] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns the SearchServiceInstance object when the object is created, updated, or deleted. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPEnterpriseSearchServiceInstance -Local -``` - -This example obtains a reference to the local search service instance. - -### ------------------EXAMPLE 2------------------ -``` -Get-SPEnterpriseSearchServiceInstance | ?{$_.Server -match 'SP01'} -``` - -This example obtains a reference to the search service instance on the SharePoint server named 'SP01'. - -## PARAMETERS - -### -Identity -Specifies the search service instance to return. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a query server (for example, MyQueryServer); or an instance of a valid SearchServiceInstance object. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Local -Returns the search service instance for the current search server. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchSiteHitRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchSiteHitRule.md deleted file mode 100644 index 6f31135036..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchSiteHitRule.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchsitehitrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchSiteHitRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchSiteHitRule - -## SYNOPSIS -Returns the shared site hit rule. - -## SYNTAX - -``` -Get-SPEnterpriseSearchSiteHitRule [[-Identity] <SiteHitRulePipeBind>] [-SearchService <SearchServicePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPEnterpriseSearchSiteHitRule cmdlet reads a SiteHitRule object when the site hit rule is created, updated, or deleted. -A SiteHitRule object sets how many crawler sessions (threads) can simultaneously crawl the given site. - -If the Identity parameter is not specified, this cmdlet returns the site hit rule collection for the specified search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$shRule = Get-SPEnterpriseSearchSiteHitRule -Identity MySiteHitRule -``` - -The following example obtains a reference to the site hit rule with the name MySiteHitRule. - -## PARAMETERS - -### -Identity -Specifies the site hit rule to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid SiteHitRule object. - -```yaml -Type: SiteHitRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchService -Specifies the search service that hosts the crawler with the specified shared site search rules. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchStatus.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchStatus.md deleted file mode 100644 index 94041d6b16..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchStatus.md +++ /dev/null @@ -1,285 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchstatus -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchStatus -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchStatus - -## SYNOPSIS -Retrieves diagnostics information for the search components. - -## SYNTAX - -``` -Get-SPEnterpriseSearchStatus -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Component <String>] [-Constellation] [-Detailed] - [-DetailSearchRuntime] [-HealthReport] [-JobStatus] [-Primary] [-Text] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet retrieves diagnostic information for all or specified search components in the active topology of a Search Service Application. - -If you don't specify any of the optional parameters, the cmdlet will retrieve the health status of all the search components within the Search Service Application. -Each search component will have one of the following states: - -- Active: The search component is running OK -- Degraded: The search component is in a status where it cannot perform all operations correctly. The reason for the degraded status is typically a transient situation related to a restart or network issues. -- Failed: The search component is not running. This status indicated that the component cannot perform operations correctly. -- Unknown: The component can't be reached. The reason for the unknown status is typically hardware or communication issues. - -If you have defined more than one Index component for a partition in your search topology, this cmdlet will indicate which index component that has the Primary role for this partition. - -You can use the cmdlet to output the following additional information: - -- List the status of background activities (batch jobs) initiated by the search components -- List the status of background activities (batch jobs) initiated by the search components -- List detailed diagnostic information for the index component -- Debug information that may be used by Microsoft for detailed issue resolution - -If you don't want to iterate over the output in a script, use the Text parameter. -If you do not use the Text parameter, the cmdlet will output a set of objects that have the following properties: - -- string Name: the name of a search component, a health report item or a constellation property -- string State: the status of the search component -- string Level: when you are using the HealthReport parameter, this property indicates the importance level of each health report item (Error, Warning, Info, Verbose) -- string Message: additional information that is provided as a text string -- ReadOnlyDictionary\<string,string\>Details: dictionary name/value pairs that provide additional diagnostic information - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchStatus -Text -``` - -This example retrieves a list that has diagnostics information about all search components of the default Search Service Application. - -### ------------------EXAMPLE 2------------------ -``` -Get-SPEnterpriseSearchStatus -SearchApplication 'Search Service Application' -JobStatus -Text -``` - -This example retrieves the background activity job status for the search analytics timer jobs. - -### ------------------EXAMPLE 3------------------ -``` -Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchStatus -HealthReport -Component IndexComponent1 -Text -``` - -This example retrieves the diagnostic information for the index component named IndexComponent1. - -## PARAMETERS - -### -SearchApplication -Specifies the search service application that contains the search components. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Component - -Specifies the name of the search component. -This parameter is only used in association with the HealthReport and Primary parameter. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Constellation - -Specifies if internal diagnostic information for the search topology should be provided. -This parameter should only be used for debugging. - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Detailed -Specifies the level of detail for the HealthReport parameter. -When this parameter is used, the cmdlet will also output verbose diagnostic information. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DetailSearchRuntime - -Specifies if internal diagnostic information for the search runtime should be provided. -This parameter should only be used for debugging. - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HealthReport - -Specifies if diagnostic information for the search component should be provided. -When using this parameter, you must specify the component name using the Component parameter. - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobStatus -Specifies if status information for the Search Analytics and Usage Analytics timer jobs should be provided. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Primary - -Specifies if the Admin component has the Primary role. -When using this parameter, you must specify the component name using the Component parameter. -Returns true if the Admin Component has the Primary role. - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Text - -Specifies if the print output from this cmdlet should be outputted in a format that is convenient for reading. -If not used, this cmdlet outputs a SearchStatusInfo object. - -When using this parameter, the output is printed to the console and cannot be piped to a file or another program. - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchTopology.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchTopology.md deleted file mode 100644 index 89220a8b19..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchTopology.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchtopology -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchTopology -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchTopology - -## SYNOPSIS -Retrieves one or all search topologies that belong to a given search service application. - -## SYNTAX - -``` -Get-SPEnterpriseSearchTopology [[-Identity] <SearchTopologyPipeBind>] - -SearchApplication <SearchServiceApplicationPipeBind> [-Active] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves a given search topology, the active search topology, or all search topologies that belong to a given search service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchTopology -SearchApplication $ssa -``` - -This example retrieves all search topologies of the search service application referenced by $ssa. - -### ------------------EXAMPLE 2------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active -``` - -This example retrieves the active search topology of the search service application referenced by $ssa. - -### ------------------EXAMPLE 3------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Identity '10fa59cb-4b32-4fe6-8f8d-065388df201e' -``` - -This example retrieves search topology with the identity 10fa59cb-4b32-4fe6-8f8d-065388df201e of the search service application referenced by $ssa. - -## PARAMETERS - -### -Identity -Specifies the search topology to retrieve. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application to which the search topology belongs. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Active -Specifies that the active search topology should be returned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchTopology](New-SPEnterpriseSearchTopology.md) - -[Set-SPEnterpriseSearchTopology](Set-SPEnterpriseSearchTopology.md) - -[Remove-SPEnterpriseSearchTopology](Remove-SPEnterpriseSearchTopology.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchVssDataPath.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchVssDataPath.md deleted file mode 100644 index 43e4351088..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchVssDataPath.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spenterprisesearchvssdatapath -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPEnterpriseSearchVssDataPath -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPEnterpriseSearchVssDataPath - -## SYNOPSIS -Retrieves the index paths for all active search index components on the current server. - -## SYNTAX - -``` -Get-SPEnterpriseSearchVssDataPath [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet retrieves the index paths for all active index components on the current server. -This list is required as input by the Search VSS Writer in order to perform VSS backup of the current server. -This cmdlet will typically be called from a VSS script, and rarely used directly. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -Get-SPEnterpriseSearchVssDataPath -``` - -This example gets the index paths for all active index components on the current server. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelBIServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelBIServer.md deleted file mode 100644 index d9141b44b5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelBIServer.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spexcelbiserver -applicable: SharePoint Server 2013 -title: Get-SPExcelBIServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPExcelBIServer - -## SYNOPSIS - -Returns the server ID of the instance of Analysis Services. - -## SYNTAX - -``` -Get-SPExcelBIServer [[-Identity] <SPExcelBIServerPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPExcelBIServer cmdlet to return the server ID of the instance of Analysis Servicesthat has been configured as a data model server in Excel Services. - -## EXAMPLES - -### Example 1 -``` -Get-SPExcelBIServer -ExcelServiceApplication 'Excel Service Application' -``` - -This example displays the name of the Excel Service application named 'Excel Service Application'. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the ExcelServiceApplication identity. - -```yaml -Type: SPExcelBIServerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Excel.Server.Cmdlet.SPExcelServiceApplicationPipeBind -Microsoft.Office.Excel.Server.Cmdlet.SPExcelBIServerPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelBlockedFileType.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelBlockedFileType.md deleted file mode 100644 index 7164dc5545..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelBlockedFileType.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spexcelblockedfiletype -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Get-SPExcelBlockedFileType -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPExcelBlockedFileType - -## SYNOPSIS -Returns a file type or list of file types that are prevented from loading. - -## SYNTAX - -``` -Get-SPExcelBlockedFileType [[-Identity] <SPExcelBlockedFileTypePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPExcelBlockedFileType cmdlet reads a file type or a list of file types that cannot be loaded in Excel Services Application. Excel Services Application does not load any files that correspond to a file type in this list. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### Example 1 -``` -Get-SPExcelBlockedFileType -ExcelServiceApplication 'Excel Service Application' -``` - -This example retrieves all blocked file types for the service application named 'Excel Service Application'. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPBlockedExcelFileType list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel -Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the Excel Services Application Web service application that contains the SPBlockedExcelFileType list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel -Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelBlockedFileTypePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Excel.Server.Cmdlet.SPExcelBlockedFileTypePipeBind -Microsoft.Office.Excel.Server.Cmdlet.SPExcelServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelDataConnectionLibrary.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelDataConnectionLibrary.md deleted file mode 100644 index de48a1aa97..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelDataConnectionLibrary.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spexceldataconnectionlibrary -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Get-SPExcelDataConnectionLibrary -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPExcelDataConnectionLibrary - -## SYNOPSIS -Returns a trusted data connection library or a list of trusted data connection libraries. - -## SYNTAX - -``` -Get-SPExcelDataConnectionLibrary [[-Identity] <SPExcelDCLPipeBind>] - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPExcelDataConnectionLibrary cmdlet gets a library of data connection files that Excel Services Application and the Excel client use to connect to an external data source. -Excel Services Application loads data connection files only if they are stored in a data connection library that is in the list of trusted data connection libraries. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -Get-SPExcelserviceapplication -Identity "MyExcelService" | Get-SPExcelDataConnectionLibrary -``` - -This example displays all the data connection libraries that connection files can be loaded by an Excel Services Application Web service application. - -### --------------EXAMPLE 2-------------- -``` -Get-SPExcelserviceapplication -identity "MyExcelService" | Get-SPExcelDataConnectionLibrary | where {$_.Description.Contains("Sales Cube")} -``` - -This example displays all the data connection libraries that have descriptions containing the words Sales Cube from the specified Excel Services Application Web service application. - -## PARAMETERS - -### -Identity -Specifies the DataConnectionLibrary object to return. -If the identity parameter is not specified, this cmdlet returns all the data connection libraries that have connection files that can be loaded by Excel Services Application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a data connection library (for example, DataConnectionLib1); a valid URL, in the form https://server_name; or an instance of a valid SPExcelDCL object. - -```yaml -Type: SPExcelDCLPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelDataConnectionLibrary list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelDataProvider.md deleted file mode 100644 index 662b810cf7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelDataProvider.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spexceldataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Get-SPExcelDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPExcelDataProvider - -## SYNOPSIS -Returns a safe data provider or a list of safe data providers. - -## SYNTAX - -``` -Get-SPExcelDataProvider -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPExcelDataProvider cmdlet reads a safe data provider or a list of safe data providers for an Excel Services Application. -Excel Services Application refreshes external data connections only if the data provider for the connection is on the list of safe data providers. -Excel Services Application includes a set of common data providers on this list. -Therefore, using cmdlets to modify safe data providers is typically done only in custom data connection scenarios. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE--------------------- -``` -Get-SPExcelServiceApplication -Identity "ExcelServices" | Get-SPExcelDataProvider | where {$_.ProviderID -eq "SQLOLEDB"} -``` - -This example displays the data provider with the provider identifier (ID) SQLOLEDB from the list of data providers that is on the MyExcelService application. -To select a specific provider from the list of safe providers, you must pipe a where clause that can filter the list of providers. - -### --------------EXAMPLE-------------- -``` -Get-SPExcelDataProvider -ExcelServiceApplication "Excel Services" | format-table -``` - -This example displays a list of safe data providers for the specific Excel Services Application Web service application, and then formats the results of the data providers in a table. - -## PARAMETERS - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelDataProvider list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelFileLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelFileLocation.md deleted file mode 100644 index 3f528e8fc8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelFileLocation.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spexcelfilelocation -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Get-SPExcelFileLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPExcelFileLocation - -## SYNOPSIS -Returns a trusted file location or a list of trusted file locations. - -## SYNTAX - -``` -Get-SPExcelFileLocation [[-Identity] <SPExcelFileLocationPipeBind>] - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPExcelFileLocation cmdlet gets locations from which Excel Services Application loads workbooks. -Excel Services Application loads only workbooks that are stored in a trusted file location. -Properties of trusted file locations control how workbooks can be used when loaded by Excel Services Application. -Excel Services Application always enforces the properties that are defined by the trusted file location from which a workbook was loaded. -The properties of the trusted file location to use are determined through comparison of the file path for the workbook with the address of the trusted file location. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelFileLocation -``` - -This example displays a list of trusted file locations for the Excel Services Application Web service application named MyExcelService. - -### --------------EXAMPLE 2-------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelFileLocation | Format-list * -``` - -This example displays a list of trusted file locations for the Excel Services Application Web service application named MyExcelService, and then formats the list of properties into a table. - -### --------------EXAMPLE 3-------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelFileLocation | where {$_.ExternalDataAllowed -ne "None"} -``` - -This example displays a list of trusted file locations that allow external data connectivity for the Excel Services Application Web service application named MyExcelService. - -## PARAMETERS - -### -Identity -Specifies the SPExcelFileLocation object to return. -If the Identity parameter is not specified, the cmdlet returns all the file locations in the specified. -Excel Services Application Web service application. - -The type must be a valid string that identifies the file location, in the form https://myPortal/myTeam; a valid string that identifies the path, in the form C:\folder_name; a valid UNC path to a trusted location in the form, \\\\computer_name\share; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPExcelFileLocation object. - -```yaml -Type: SPExcelFileLocationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelServiceApplication.md deleted file mode 100644 index bedb52d8da..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelServiceApplication.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spexcelserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Get-SPExcelServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPExcelServiceApplication - -## SYNOPSIS -Returns an SPExcelServiceApplication object. - -## SYNTAX - -``` -Get-SPExcelServiceApplication [[-Identity] <SPExcelServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPExcelServiceApplication cmdlet retrieves an SPExcelServiceApplication object. -If the object returned by this cmdlet is changed, the change affects all instances of the specified Excel Services Application Web service application in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -Get-SPExcelServiceApplication "MyExcelServices" -``` - -This example displays the Excel Services Application Web service application named MyExcelServices. - -### --------------EXAMPLE 2-------------- -``` -Get-SPExcelServiceApplication -``` - -This example displays every Excel Services Application Web service application that runs in the farm. - -### --------------EXAMPLE 3-------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | format-list * -``` - -This example displays Excel Services Application Web service application named MyExcelService, and then displays all of its settings in a list format. - -## PARAMETERS - -### -Identity -Specifies the ExcelServiceApplication object to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelUserDefinedFunction.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelUserDefinedFunction.md deleted file mode 100644 index e2279ef227..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelUserDefinedFunction.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spexceluserdefinedfunction -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Get-SPExcelUserDefinedFunction -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPExcelUserDefinedFunction - -## SYNOPSIS -Returns a user-defined function or a collection of user-defined functions. - -## SYNTAX - -``` -Get-SPExcelUserDefinedFunction [[-Identity] <SPExcelUDFPipeBind>] - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPExcelUserDefinedFunction cmdlet reads a user-defined function and its properties, or returns the collection of user-defined functions for an Excel Services Application Web service application. -Excel Services Application uses only user-defined functions that are in the list of user-defined functions. -User-defined functions are managed code assemblies that can be called from an Excel Services Application workbook by using standard Excel Services Application formula syntax. -The assemblies can perform custom logic or other actions, such as refreshing data. -Windows PowerShell cmdlets operate on the entries in the user-defined function list, but do not operate on the assemblies. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelUserDefinedFunction -Identity SampleCompany.SampleApplication.SampleUdf -``` - -This example displays the user-defined function named SampleCompany.SampleApplication.SampleUdf from the list of user-defined functions that is in the Excel Services Application Web service application named MyExcelService. - -### --------------EXAMPLE 2-------------- -``` -Get-SPExcelServiceApplication | Get-SPExcelUserDefinedFunction | format-list -``` - -This example displays every user-defined function for every Excel Services Application Web service application in the farm, and then displays the results in a list. - -## PARAMETERS - -### -Identity -Specifies the UserDefinedFunction object to get. -If the Identity parameter is not specified, the cmdlet returns all of the functions in the user defined functions list. - -The type must be a valid name of the code assembly (for example, SampleCompany.SampleApplication.SampleUdf); or an instance of a valid SPExcelUDF object. - -```yaml -Type: SPExcelUDFPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelUserDefinedFunction list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFarm.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFarm.md deleted file mode 100644 index 8d7f0a056b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFarm.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spfarm -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPFarm -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPFarm - -## SYNOPSIS - -Returns the local SharePoint farm. - - - -## SYNTAX - -``` -Get-SPFarm [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPFarm cmdlet returns the local SharePoint farm. -No parameters are used. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -``` -C:\PS>$f = Get-SPFarm -``` - -This example stores the local farm in a variable. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFarmConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFarmConfig.md deleted file mode 100644 index 756a40f9c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFarmConfig.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spfarmconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPFarmConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPFarmConfig - -## SYNOPSIS - -Returns a global property or a collection of global properties for the local farm. - - - -## SYNTAX - -``` -Get-SPFarmConfig [-AssignmentCollection <SPAssignmentCollection>] [-ServiceConnectionPoint] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPFarmConfig cmdlet retrieves global settings for the local farm that are not members of the SPFarm object. -This cmdlet creates a new PSCustomObject object from the collection of properties returned from the local farm, and then adds this object to the pipeline. - -The PSCustomObject object can be read, or modified and passed to the Set-SPFarmConfig cmdlet to change parameter values. - -The properties collected in the PSCustomObject object must be farm-wide settings, and must be configurable only once for the entire farm. - -The parameter name added to the PSCustomObject object must match exactly the input parameter name for the Set-SPFarmConfig cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - -## EXAMPLES - -### -------------EXAMPLE---------------- -``` -$a = Get-SPFarmConfig -$a.AjaxTimeout = 200 -$a | Set-SPFarmConfig -``` - -This example uses the Get-SPFarmConfig cmdlet to add the Ajax Timeout setting to the PSCustomObject object, sets the value for Ajax Timeout, and then passes PSCustomObject to the Set-SPFarmConfig cmdlet to change the Ajax Timeout setting. Ajax Timeout, a farm-wide setting, is a member of the SPWebService object and cannot be accessed with a Windows PowerShell cmdlet. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceConnectionPoint -Gets the information stored in the current farm's service connection point in Active Directory. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFeature.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFeature.md deleted file mode 100644 index 5bf3ddc0ba..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPFeature.md +++ /dev/null @@ -1,252 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spfeature -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPFeature -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPFeature - -## SYNOPSIS - -Returns the SharePoint Features based on a given scope. - - - -## SYNTAX - -### FarmFeatures -``` -Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Farm] [-Limit <String>] [<CommonParameters>] -``` - -### SiteFeatures -``` -Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Limit <String>] [-Site <SPSitePipeBind>] [-Sandboxed] [<CommonParameters>] -``` - -### WebFeatures -``` -Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Limit <String>] [-Web <SPWebPipeBind>] [<CommonParameters>] -``` - -### WebApplicationFeatures -``` -Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Limit <String>] [-WebApplication <SPWebApplicationPipeBind>] [<CommonParameters>] -``` - -### FarmFeatureDefinitions -``` -Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Limit <String>] [-CompatibilityLevel <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. - -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets [https://go.microsoft.com/fwlink/?LinkID=18781](https://go.microsoft.com/fwlink/?LinkID=187810). - -All parameter sets take the Identity parameter, which can be either the relative path of the SharePoint Feature (considered the feature name) or the GUID of a Feature definition. - -If the Identity parameter is provided, the cmdlets attempt to find the given Feature definition or instance for the given scope. -If no parameters are specified, all installed features are returned. - -The Get-SPFeature cmdlet behaves differently at each scope, returning the enabled Features at each level. -If no scope is provided, all installed Features are returned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPFeature -Limit ALL | Where-Object {$_.Scope -eq "SITE"} -``` -This example returns a list of all installed SITE scoped Features. - -### --------------EXAMPLE 2----------------- -``` -Get-SPSite https://somesite | Get-SPWeb -Limit ALL |%{ Get-SPFeature -Web $_ } | Select DisplayName,ID -Unique -``` - -This example returns the name and identifier (ID) of each uniquely enabled Feature on every SPWeb object in the site collection at https://somesite. - -## PARAMETERS - -### -Identity -Specifies the name of the Feature to retrieve. - -The type must be the full or partial name, in the form Feature1, or a GUID, in the form 1234-4567-9879, of the Feature to get. - -```yaml -Type: SPFeatureDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Farm -Specifies that if this parameter is used, only enabled farm Features are displayed. - -```yaml -Type: SwitchParameter -Parameter Sets: FarmFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit -Limits the display results. If "All" is specified, all Features are displayed. - -The type must be a valid number greater than 0. The default value is 200. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Specifies the name of the site collection from which to get enabled Features. - -The type must be a valid URL for a site collection, in the form https://server_name . - -```yaml -Type: SPSitePipeBind -Parameter Sets: SiteFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Web -Specifies the URL or GUID of the Web. - -The type must be a valid URL, in the form https://server_name , or a GUID, in the form 1234-5678-9876-0987. - -```yaml -Type: SPWebPipeBind -Parameter Sets: WebFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the name of the Web application from which to get enabled Features. - -The type must be a valid URL to the Web application in the form https://server_name . - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplicationFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. This value sets the initial CompatibilityLevel value for the site collection. When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the web application depending on the CompatibilityRange setting. - -```yaml -Type: Int32 -Parameter Sets: FarmFeatureDefinitions -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Sandboxed -Specifies to retrieve Sandbox features. - -```yaml -Type: SwitchParameter -Parameter Sets: SiteFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPHealthAnalysisRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPHealthAnalysisRule.md deleted file mode 100644 index 27653f5c49..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPHealthAnalysisRule.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sphealthanalysisrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPHealthAnalysisRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPHealthAnalysisRule - -## SYNOPSIS - -Gets a health analyzer rule. - - - -## SYNTAX - -``` -Get-SPHealthAnalysisRule [-Identity] <SPHealthAnalysisRuleInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Get-SPHealthAnalysisRule cmdlet to return a list of a health analyzer rules. -To return a specify health analyzer rule, use the Identity parameter; otherwise, all health analyzer rules will be returned. - -The SPHealthAnalysisRule cmdlets were first introduced in the February 2011 Cumulative Update, which is available for download as follows: - ---Description of the SharePoint Foundation Cumulative Update Server Hotfix Package (SharePoint Foundation server-package) (https://support.microsoft.com/kb/2475880) ---Description of the SharePoint Server Cumulative Update Server Hotfix Package (MOSS server-package (https://support.microsoft.com/kb/2475878) - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE 1--------------------------- -``` -Get-SPHealthAnalysisRule -Identity "CustomRule" -``` - -This example returns the health analyzer rule named CustomRule. - -## PARAMETERS - -### -Identity -Specifies the name or GUID of the health analyzer rule to get. - -The type must be a valid name, an instance of a valid SPHealthAnalysisRule object, or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPHealthAnalysisRuleInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPHelpCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPHelpCollection.md deleted file mode 100644 index 97d7c60e8b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPHelpCollection.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sphelpcollection -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPHelpCollection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPHelpCollection - -## SYNOPSIS - -Returns Help collection files. - - - -## SYNTAX - -``` -Get-SPHelpCollection [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPHelpCollection cmdlet reads the specified Help collection files. -If the Name parameter is not specified, this cmdlet returns all installed Help collection files. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPHelpCollection -``` - -This example gets all installed Help collection files. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the Help collection files to get. - -The type must be a valid name of a Help collection folder; for example, HelpDocs1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPIRMSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPIRMSettings.md deleted file mode 100644 index 87786b2f53..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPIRMSettings.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spirmsettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPIRMSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPIRMSettings - -## SYNOPSIS - -Returns the Information Rights Management (IRM) settings. - - - -## SYNTAX - -``` -Get-SPIRMSettings [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPIRMSettings cmdlet to display IRM settings for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE---------------- -``` -Get-SPIRMSettings -``` - -This example returns IRM settings for the entire farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPIRMSettings](Set-SPIRMSettings.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathFormTemplate.md deleted file mode 100644 index 43cf60cbe7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPInfoPathFormTemplate - -## SYNOPSIS -Returns a InfoPath form template. - -## SYNTAX - -``` -Get-SPInfoPathFormTemplate [[-Identity] <SPFormTemplatePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPInfoPathFormTemplate cmdlet reads a specific InfoPath form template or the collection of templates. -If the Identity parameter is not specified, the cmdlet returns the collection of InfoPath form templates for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1-------------- -``` -Get-SPInfoPathFormTemplate -``` - -This example lists the Identity, DisplayName, and FormTemplateStatus property for each admininstrator-deployed InfoPath form template. - -### ---------------EXAMPLE 2-------------- -``` -C:\PS>"SomeFormTemplate.xsn" | Get-SPInfoPathFormTemplate | format-list -``` - -This example lists all the properties of the specified InfoPath form template. - -## PARAMETERS - -### -Identity -Specifies the InfoPath form template to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a form template (for example, InfoPathFormTemplate1); a valid name of a form template files (for example, FormTemplateFile1.xsn); or an instance of a valid SPFormTemplate object. - -```yaml -Type: SPFormTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathFormsService.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathFormsService.md deleted file mode 100644 index cc752120b4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathFormsService.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spinfopathformsservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPInfoPathFormsService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPInfoPathFormsService - -## SYNOPSIS -Returns the InfoPath Forms Services in SharePoint Server settings that are in the farm. - -## SYNTAX - -``` -Get-SPInfoPathFormsService [-AssignmentCollection <SPAssignmentCollection>] - [-Identity <SPFormsServicePipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPInfoPathFormsService cmdlet reads the settings for the InfoPath Forms Services in SharePoint Server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE---------------- -``` -Get-SPInfoPathFormsService -``` - -This example displays the InfoPath Forms Services settings for the entire farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the InfoPath Forms Services settings to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a forms service (for example, FormsService1); or an instance of a valid SPFormsService object. - -```yaml -Type: SPFormsServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathUserAgent.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathUserAgent.md deleted file mode 100644 index 0961634646..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathUserAgent.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spinfopathuseragent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPInfoPathUserAgent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPInfoPathUserAgent - -## SYNOPSIS -Returns a user agent or all the currently defined user agents for the farm. - -## SYNTAX - -``` -Get-SPInfoPathUserAgent [[-Identity] <SPUserAgentPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPInfoPathUserAgent cmdlet reads the user agent specified in Identity. -If the Identity parameter is not specified, this cmdlet returns the collection of user agents for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPInfoPathUserAgent -``` - -This example displays a list of user agents in the entire farm. - -## PARAMETERS - -### -Identity -Specifies the user agent to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a user agent (for example, UserAgent1; or an instance of a valid SPUserAgent object. - -```yaml -Type: SPUserAgentPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathWebServiceProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathWebServiceProxy.md deleted file mode 100644 index 7b89fea5aa..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInfoPathWebServiceProxy.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spinfopathwebserviceproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPInfoPathWebServiceProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPInfoPathWebServiceProxy - -## SYNOPSIS -Returns the Web proxy settings for the Web application. - -## SYNTAX - -``` -Get-SPInfoPathWebServiceProxy [-Identity] <SPWebServiceProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPInfoPathWebServiceProxy cmdlet reads the Web proxy settings for the SharePoint Web application specified in Identity. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPInfoPathWebServiceProxy -Identity "https://server_name/" -``` - -This example displays the Web service proxy settings for a specified Web application. - -## PARAMETERS - -### -Identity -Specifies the SharePoint Web application to get. - -The type must be a valid URL, in the form https://server_name, or a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPWebServiceProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInsightsConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInsightsConfig.md deleted file mode 100644 index ea493686de..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInsightsConfig.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spinsightsconfig -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPInsightsConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPInsightsConfig - -## SYNOPSIS -Returns the uploader.xml and Microsoft.Office.BigData.DataLoader.exe.config files from the Configuration database. - -## SYNTAX - -``` -Get-SPInsightsConfig [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Returns the uploader.xml and Microsoft.Office.BigData.DataLoader.exe.config files from the Configuration database. - -## EXAMPLES - -### Example 1 -``` -$config = Get-SPInsightsConfig -$xml = $config.UploaderXml -$config.UploaderXml = $xml -$config.Update() -Stop-SPService -Identity "Microsoft SharePoint Insights" -Start-SPService -Identity "Microsoft SharePoint Insights" -``` - -This example returns and modifies the config.uploader.xml file. It then restarts the SharePoint Insights service on all servers in order to commit the changes. - -### Example 2 -``` -$config = Get-SPInsightsConfig -$odlExeConfig = $config.OdlExeConfig -$config.OdlExeConfig = $odlExeConfig -$config.Update() -Stop-SPService -Identity "Microsoft SharePoint Insights" -Start-SPService -Identity "Microsoft SharePoint Insights" -``` - -This example returns and modifies the config.uploader.xml file. It then restarts the SharePoint Insights service on all servers in order to commit the changes. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInternalAppStateSyncLastRunTime.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInternalAppStateSyncLastRunTime.md deleted file mode 100644 index 1aef7cb6bf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInternalAppStateSyncLastRunTime.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spinternalappstatesynclastruntime -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPInternalAppStateSyncLastRunTime -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPInternalAppStateSyncLastRunTime - -## SYNOPSIS - -Returns the latest time the internal app state update job was invoked. - - - -## SYNTAX - -``` -Get-SPInternalAppStateSyncLastRunTime [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPInternalAppStateSyncLastRunTime cmdlet to return the latest time the internal app state update job was invoked. -The internal app state update job gets app upgrades from the internal app directory and sets them on app instances. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE----------- -``` -Get-SPInternalAppStateSyncLastRunTime -``` - -This example returns the latest time the internal app state update job was invoked. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInternalAppStateUpdateInterval.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInternalAppStateUpdateInterval.md deleted file mode 100644 index 1e2a310ad4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPInternalAppStateUpdateInterval.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spinternalappstateupdateinterval -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPInternalAppStateUpdateInterval -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPInternalAppStateUpdateInterval - -## SYNOPSIS - -Returns the interval in hours between updates of the internal app state update job. - - - -## SYNTAX - -``` -Get-SPInternalAppStateUpdateInterval [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPInternalAppStateUpdateInterval cmdlet to return the interval in hours between updates of the internal app state update job. -The internal app state update job gets app upgrades from the internal app directory and sets them on app instances. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE----------- -``` -Get-SPInternalAppStateUpdateInterval -``` - -This example returns the interval in hours between updates of the internal app state update job. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPInternalAppStateUpdateInterval](Set-SPInternalAppStateUpdateInterval.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPLogEvent.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPLogEvent.md deleted file mode 100644 index 9a542e5277..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPLogEvent.md +++ /dev/null @@ -1,239 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-splogevent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPLogEvent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPLogEvent - -## SYNOPSIS - -Returns results from a Unified Logging Service (ULS) trace log. - - - -## SYNTAX - -### Directory -``` -Get-SPLogEvent [-AssignmentCollection <SPAssignmentCollection>] [-AsString] [-ContextKey <String[]>] - [-Directory <String>] [-MinimumLevel <String>] [-EndTime <DateTime>] [-StartTime <DateTime>] - [<CommonParameters>] -``` - -### File -``` -Get-SPLogEvent [-AssignmentCollection <SPAssignmentCollection>] [-AsString] [-ContextKey <String[]>] - [-MinimumLevel <String>] [-EndTime <DateTime>] [-File <String>] [-StartTime <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPLogEvent cmdlet returns records from a ULS trace log file that match the criteria. -If no parameters are specified, all records from all log files are returned. -Use the StartTime and EndTime parameters to filter on a time range. -The use of these parameters is recommended to optimize performance of this cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPLogEvent -MinimumLevel "Warning" -``` - -This example returns all log entries equal to or more severe than Warning from the default log directory. - -### --------------EXAMPLE 2----------------- -``` -Get-SPLogEvent -Directory "C:\Logs" | Where-Object {$_.Level -eq "Warning"} -``` - -This example returns all warning entries from log files in the C:\Logs directory. - -### --------------EXAMPLE 3----------------- -``` -Get-SPLogEvent -StartTime "12/04/2007 17:00" -EndTime "12/04/2007 18:00" -``` - -This example returns error entries that occurred during a particular time range, which is culture-specific to the United States. - -### --------------EXAMPLE 4----------------- -``` -Get-SPLogEvent -ContextKey @("UserName" ,"SiteName") -``` - -This example returns the contents of the most recent log file and adds the specified context key data. - -### --------------EXAMPLE 5----------------- -``` -Get-SPLogEvent | Where-Object {$_.Level -eq "Error" -and {$_.Area -eq "SharePoint Foundation "} -``` - -This example returns all error entries related to SharePoint Foundation. - -### --------------EXAMPLE 6----------------- -``` -Get-SPLogEvent -ContextKey @("Name") | %{$_.ToString() + "'t" + $_.Context["Name"]} -``` - -This example returns the contents of the log file and adds context data. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AsString -Returns each record as a separate string - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContextKey -Specifies that context data should be added to the results for the specified Context Keys, for example: `-ContextKey @("UserName", "SiteName")`. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Directory -Lists log files from an alternate directory (any directory other than the configured LogLocation directory). - -```yaml -Type: String -Parameter Sets: Directory -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MinimumLevel -Returns records at or above the specified level. -The valid values are Error or Warning. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndTime -The type must be a valid DateTime format that is culture-specific to the administrative language, such as 2/16/2007 12:15:12 for English-US. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -File -Specifies a specific file to query records from. - -```yaml -Type: String -Parameter Sets: File -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartTime -The type must be a valid DateTime format that is culture-specific to the administrative language, such as 2/16/2007 12:15:12 for English-US. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPLogLevel.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPLogLevel.md deleted file mode 100644 index 9f5b5cf091..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPLogLevel.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sploglevel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPLogLevel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPLogLevel - -## SYNOPSIS - -Returns a list of objects or diagnostic levels. - - - -## SYNTAX - -``` -Get-SPLogLevel [-AssignmentCollection <SPAssignmentCollection>] [-Identity <String[]>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPLogLevel cmdlet displays a list of objects or diagnostic levels based on the criteria specified. -If no parameter is specified, a list of all diagnostic levels for all categories is returned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPLogLevel -``` - -This example displays throttle levels for all categories. - -### --------------EXAMPLE 2----------------- -``` -Get-SPLogLevel -Identity "Category1" -``` - -This example displays the throttle level for the Category1 category. - -### --------------EXAMPLE 3----------------- -``` -C:\PS>"Cat1", "Cat2", "Cat3" | Get-SpLogLevel -``` - -This example displays the throttle level for multiple categories. - -### --------------EXAMPLE 4----------------- -``` -Get-SPLogLevel -Identity "Area:*" -``` - -This example displays the throttle level for all categories in one area. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies a valid category name; for example, Backup and Restore, or Administration. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPManagedAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPManagedAccount.md deleted file mode 100644 index 76ea5b01a4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPManagedAccount.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spmanagedaccount -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPManagedAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPManagedAccount - -## SYNOPSIS - -Retrieves accounts registered in the configuration database. - - - -## SYNTAX - -### Server -``` -Get-SPManagedAccount [[-Identity] <SPManagedAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Server <SPServerPipeBind>] [<CommonParameters>] -``` - -### Service -``` -Get-SPManagedAccount [[-Identity] <SPManagedAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Service <SPServicePipeBind>] [<CommonParameters>] -``` - -### WebApplication -``` -Get-SPManagedAccount [[-Identity] <SPManagedAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-WebApplication <SPWebApplicationPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPManagedAccount cmdlet returns the managed accounts that match the given scope. -The scope can be any one of the following values: Web application, service, or server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPManagedAccount -``` - -This example displays all the managed accounts in the farm. - -## PARAMETERS - -### -Identity -Specifies the full name or partial name of the managed accounts to retrieve. - -The type must be a valid account name, in the form Domain\User, or a GUID, in the form 1234-3456-09876. - -```yaml -Type: SPManagedAccountPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Server -Specifies the scope to a server. - -```yaml -Type: SPServerPipeBind -Parameter Sets: Server -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Service -Specifies the scope to a service. - -```yaml -Type: SPServicePipeBind -Parameter Sets: Service -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the scope to a Web application. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPManagedPath.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPManagedPath.md deleted file mode 100644 index 3b925d3dc6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPManagedPath.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spmanagedpath -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPManagedPath -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPManagedPath - -## SYNOPSIS - -Returns all managed paths that match the given criteria. - - - -## SYNTAX - -### HostHeader -``` -Get-SPManagedPath [[-Identity] <SPPrefixPipeBind>] [-HostHeader] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### WebApplication -``` -Get-SPManagedPath [[-Identity] <SPPrefixPipeBind>] -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPManagedPath cmdlet returns the SharePoint managed path that matches the provided Identity for either a Web application, site collection or for all host-named site collections. -If an Identity parameter is not provided, all managed paths for the given scope are returned. - -Host-named sites (no matter the Web application in which they are contained) share a single set of managed paths. -Use the HostHeader parameter to return host-named site collections-scoped managed paths. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPManagedPath -WebApplication https://sitename -``` - -This example returns all managed paths for the specified Web application. - -### --------------EXAMPLE 2----------------- -``` -Get-SPManagedPath -identity "Sites" -HostHeader -``` - -This example gets the Sites managed path from the host-named site collections-scoped managed paths. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the managed path to return. - -The type must be a valid URL, in the https://server_name or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPPrefixPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostHeader -If provided, the managed paths returned are for the host-named sites in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: HostHeader -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL or GUID of the Web application from which to get the managed path. - -The type must be a valid URL, in the form https://server_name, or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMetadataServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMetadataServiceApplication.md deleted file mode 100644 index 97ccbbcd85..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMetadataServiceApplication.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spmetadataserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPMetadataServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPMetadataServiceApplication - -## SYNOPSIS -Returns a managed metadata service application. - -## SYNTAX - -``` -Get-SPMetadataServiceApplication [-Identity] <SPMetadataServiceCmdletPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPMetadataServiceApplication cmdlet to retrieve a specified managed metadata service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE----------------- -``` -Get-SPMetadataServiceApplication -Identity "ManagedMetadataServiceApp1" -``` - -This example retrieves an existing managed metadata service application. - -## PARAMETERS - -### -Identity -Specifies the managed metadata service application to get. - -The type must be a valid GUID or the name of a valid managed metadata service application. - -```yaml -Type: SPMetadataServiceCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMetadataServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMetadataServiceApplicationProxy.md deleted file mode 100644 index e6cf8ec754..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMetadataServiceApplicationProxy.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spmetadataserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPMetadataServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPMetadataServiceApplicationProxy - -## SYNOPSIS -Returns an existing connection to a managed metadata service application, which is also known as a proxy, to the managed metadata service application. - -## SYNTAX - -``` -Get-SPMetadataServiceApplicationProxy [-Identity] <SPMetadataServiceProxyCmdletPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPMetadataServiceApplicationProxy cmdlet to get a specified connection to a managed metadata service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE------------- -``` -Get-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1" -``` - -This example retrieves an existing connection to a managed metadata service application. - -## PARAMETERS - -### -Identity -Specifies the service application proxy to read. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of the service application proxy (for example, ServiceAppProxy1); or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMicrofeedOptions.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMicrofeedOptions.md deleted file mode 100644 index 819b95cbdc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMicrofeedOptions.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spmicrofeedoptions -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPMicrofeedOptions -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPMicrofeedOptions - -## SYNOPSIS -Returns the feed cache settings for the current user profile application. - -## SYNTAX - -``` -Get-SPMicrofeedOptions [-AssignmentCollection <SPAssignmentCollection>] - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Returns the feed cache settings for the current user profile application. - -## EXAMPLES - -### Example 1 -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Get-SPMicrofeedOptions -ProfileServiceApplicationProxy $proxy -``` - -This example returns cache feed settings from the specified User Profile Service Application Proxy. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the unique identifier for the proxy. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationProxyPipeBind -Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMobileMessagingAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMobileMessagingAccount.md deleted file mode 100644 index 83d7dba5b9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPMobileMessagingAccount.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spmobilemessagingaccount -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPMobileMessagingAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPMobileMessagingAccount - -## SYNOPSIS - -Retrieves mobile messaging accounts for the specified Web application. - - - -## SYNTAX - -``` -Get-SPMobileMessagingAccount [[-Identity] <SPMobileMessagingAccountPipeBind>] - -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPMobileMessagingAccount cmdlet retrieves the specified mobile messaging accounts for the specified Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPMobileMessagingAccount -WebApplication https://sitename -``` - -This example retrieves the current mobile account settings information of the Web application https://sitename. - -## PARAMETERS - -### -Identity -Specifies whether to return either Short Message Service (SMS) or Multimedia Messaging Service (MMS) account information. -Valid values are:SMS and MMS. -If you do not specify this parameter, account information is returned for both SMS and MMS. - -```yaml -Type: SPMobileMessagingAccountPipeBind -Parameter Sets: (All) -Aliases: ServiceType, AccountType -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the identity of the Web application to delete. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid Web application name (for example, WebApplication1212); or a valid name (for example, WebApp2423). - -You either must specify WebApplication or must use the HostHeader switch and specify the full URL in the Identity parameter. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPO365LinkSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPO365LinkSettings.md deleted file mode 100644 index 077e2ad680..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPO365LinkSettings.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spo365linksettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPO365LinkSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPO365LinkSettings - -## SYNOPSIS -Gets hybrid configurations. - -## SYNTAX - -``` -Get-SPO365LinkSettings [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the **Get-SPO365LinkSettings** cmdlet to display current hybrid configurations in the farm. - -## EXAMPLES - -### EXAMPLE 1 -```powershell -$gc = Start-SPAssignment -Get-SPO365LinkSettings -AssignmentCollection $gc -Stop-SPAssignment $gc -``` - -This example returns all hybrid configurations. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## RELATED LINKS - -[Set-SPO365LinkSettings](Set-SPO365LinkSettings.md) - -[Test-SPO365LinkSettings](Test-SPO365LinkSettings.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md deleted file mode 100644 index ced4dabeb8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spodataconnectionsetting -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Get-SPODataConnectionSetting -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPODataConnectionSetting - -## SYNOPSIS - -Returns Business Connectivity Services OData connection properties. - - -## SYNTAX - -``` -Get-SPODataConnectionSetting -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Get-SPODataConnectionSetting` cmdlet to display Business Connectivity Services OData connection properties for a specified Business Connectivity Services connection. - -If the name of the connection is not specified by using the Name parameter, this cmdlet will return the list of the connections for the specified BDC service context. - -This cmdlet applies to an on-premises environment only. -You cannot use this command in the SharePoint Online Management Shell. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- -``` -Get-SPODataConnectionSetting -ServiceContext "http://contoso/" -Name "ContosoServiceApp" -``` - -This example returns properties of the BCS connection named ContosoServiceApp - -### -----------------------EXAMPLE 2----------------------------- -``` -Get-SPODataConnectionSetting -ServiceContext "http://contoso/" -``` - -This example returns a list of BCS connections for the service context named http://contoso - - -## PARAMETERS - -### -ServiceContext -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object. -An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the Business Connectivity Services connection object. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPODataConnectionSetting](New-SPODataConnectionSetting.md) - -[Remove-SPODataConnectionSetting](Remove-SPODataConnectionSetting.md) - -[Set-SPODataConnectionSetting](Set-SPODataConnectionSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSettingMetadata.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSettingMetadata.md deleted file mode 100644 index 6abcb5ae48..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSettingMetadata.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: sharepointonline.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spodataconnectionsettingmetadata -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Get-SPODataConnectionSettingMetadata -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPODataConnectionSettingMetadata - -## SYNOPSIS - -Returns a Business Data Connectivity service metadata object. - - -## SYNTAX - -``` -Get-SPODataConnectionSettingMetadata -ServiceContext <SPServiceContextPipeBind> -Name <String> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Get-SPODataConnectionSettingMetaData` cmdlet to return a Business Data Connectivity service metadata object for a specific Business Connectivity Services service application. - -This cmdlet applies to an on-premises environment only. -You cannot use this command in the SharePoint Online Management Shell. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251831 (https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- -``` -Get-SPODataConnectionSettingMetadata -ServiceContext "http://contoso/" -Name "ContosoServiceApp" -``` - -This example displays metadata properties of BCS connection named ContosoServiceApp - - -## PARAMETERS - -### -ServiceContext -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object. -An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the Business Connectivity Services connection whose metadata properties the user wants to see displayed. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPODataConnectionSettingMetaData](Set-SPODataConnectionSettingMetaData.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPOfficeStoreAppsDefaultActivation.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPOfficeStoreAppsDefaultActivation.md deleted file mode 100644 index e07955f13c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPOfficeStoreAppsDefaultActivation.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spofficestoreappsdefaultactivation -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Get-SPOfficeStoreAppsDefaultActivation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Get-SPOfficeStoreAppsDefaultActivation - -## SYNOPSIS - -Returns the properties of apps for Office. - - -## SYNTAX - -### AppsForOfficeSettingsInSiteSubscription -``` -Get-SPOfficeStoreAppsDefaultActivation -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### AppsForOfficeSettingsInWebApplication -``` -Get-SPOfficeStoreAppsDefaultActivation -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Get-SPOfficeStoreAppsDefaultActivation` cmdlet to return settings for apps for Office that run in a specific web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251831 (https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- -``` -Get-SPOfficeStoreAppsDefaultActivation -WebApplication https://sphvm-8044 -``` - -This examples returns the setting for the web application https://sphvm-8044. - -### -----------------------EXAMPLE 2----------------------------- -``` -Get-SPOfficeStoreAppsDefaultActivation -SiteSubscription efca5b88-b3a3-448d-afbc-ef620f4744f1 -``` - -This examples returns the Subscription ID setting for the tenant - -## PARAMETERS - -### -SiteSubscription -Specifies the Site Group to which the settings apply. - - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: AppsForOfficeSettingsInSiteSubscription -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the web application to which the setting applies. - - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: AppsForOfficeSettingsInWebApplication -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPOfficeStoreAppsDefaultActivation](Set-SPOfficeStoreAppsDefaultActivation.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPendingUpgradeActions.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPendingUpgradeActions.md deleted file mode 100644 index 53fef8e072..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPendingUpgradeActions.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sppendingupgradeactions -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPPendingUpgradeActions -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPPendingUpgradeActions - -## SYNOPSIS - -Displays pending upgrade actions. - - - -## SYNTAX - -``` -Get-SPPendingUpgradeActions [-RootObject] <IUpgradable> [-AssignmentCollection <SPAssignmentCollection>] - [-Recursive] [-SkipSiteUpgradeActionInfo] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPPendingUpgradeActions cmdlet to display the current pending upgrade actions for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE------- -``` -Get-SPFarm | Get-SPPendingUpgradeActions -Recursive -``` - -## PARAMETERS - -### -RootObject -Specifies a SharePoint object where you check for which upgrade actions are outstanding for that object based on its current upgrade status. - -This object must be inherited from IUpgradable. - -```yaml -Type: IUpgradable -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Recursive -Specifies whether to perform the same pending upgrade action checks on each IUpgradable object that occurs under the RootObject parameter that is specified. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipSiteUpgradeActionInfo -Specifies to not include pending upgrade actions for all child objects of a content database. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPerformancePointServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPerformancePointServiceApplication.md deleted file mode 100644 index 42253957cd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPerformancePointServiceApplication.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spperformancepointserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPPerformancePointServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPPerformancePointServiceApplication - -## SYNOPSIS -Returns a PerformancePoint Service application object and properties. - -## SYNTAX - -``` -Get-SPPerformancePointServiceApplication [[-Identity] <SPPerformancePointMonitoringServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPPerformancePointServiceApplication cmdlet to read a PerformancePoint Service application object and properties. -If the Identity parameter is not specified, the cmdlet returns the collection of PerformancePoint Service applications in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE------------------ -``` -Get-SPPerformancePointServiceApplication "PPSApp_01" -``` - -This example gets a PerformancePoint Service application named PPSApp_01. - -## PARAMETERS - -### -Identity -Specifies the PerformancePoint Service application to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointMonitoringServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPerformancePointServiceApplicationTrustedLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPerformancePointServiceApplicationTrustedLocation.md deleted file mode 100644 index a80e6b3717..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPerformancePointServiceApplicationTrustedLocation.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spperformancepointserviceapplicationtrustedlocation -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPPerformancePointServiceApplicationTrustedLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPPerformancePointServiceApplicationTrustedLocation - -## SYNOPSIS -Returns a trusted location object and properties for a PerformancePoint Service application. - -## SYNTAX - -``` -Get-SPPerformancePointServiceApplicationTrustedLocation [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Identity <SPPerformancePointMonitoringServiceApplicationTrustedLocationPipeBind>] - [-ServiceApplication <SPPerformancePointMonitoringServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPPerformancePointMonitoringServiceApplicationTrustedLocation cmdlet to read a trusted location object and properties. -If the Identity parameter is not specified, this cmdlet returns the list of all trusted locations and their properties for a PerformancePoint Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------------EXAMPLE---------------------- -``` -Get-SPPerformancePointServiceApplication PPSApp_01 | Get-SPPerformancePointServiceApplicationTrustedLocation -Identity $_.ID | select * -``` - -This example retrieves TrustedLocation information for the PPSApp_01 PerformancePoint Service application. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the trusted location to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPPerformancePointMonitoringServiceApplicationTrustedLocation object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationTrustedLocationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the PerformancePoint Service application that contains the trusted location. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointMonitoringServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPluggableSecurityTrimmer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPluggableSecurityTrimmer.md deleted file mode 100644 index 372fb1ffae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPPluggableSecurityTrimmer.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sppluggablesecuritytrimmer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPPluggableSecurityTrimmer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPPluggableSecurityTrimmer - -## SYNOPSIS -Gets pluggable security trimmers added to a profile service application proxy. - -## SYNTAX - -``` -Get-SPPluggableSecurityTrimmer -UserProfileApplicationProxyId <Guid> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPPluggableSecurityTrimmer cmdlet to list the pluggable security trimmers that have been added to a User Profile service application proxy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE--------------------- -``` -$pr = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq 'User Profile Service Application Proxy'} -Get-SPPluggableSecurityTrimmer -UserProfileApplicationProxyId $pr.Id -``` - -This example gets a list of the pluggable security trimmers that are associated with the User Profile service application proxy. - -## PARAMETERS - -### -UserProfileApplicationProxyId -Specifies the ID of the User Profile service application proxy to which the pluggable security trimmers have been added. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProcessAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProcessAccount.md deleted file mode 100644 index 042753b99a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProcessAccount.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprocessaccount -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPProcessAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProcessAccount - -## SYNOPSIS - -Returns a system account or a managed account. - - - -## SYNTAX - -### LocalService -``` -Get-SPProcessAccount [-AssignmentCollection <SPAssignmentCollection>] [-LocalService] [<CommonParameters>] -``` - -### LocalSystem -``` -Get-SPProcessAccount [-AssignmentCollection <SPAssignmentCollection>] [-LocalSystem] [<CommonParameters>] -``` - -### NetworkService -``` -Get-SPProcessAccount [-AssignmentCollection <SPAssignmentCollection>] [-NetworkService] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPProcessAccount cmdlet returns a system account or a managed account and creates the SPProcessAccountPipeBind object. -All operations that can accept an account can accept the SPProcessAccountPipeBind in place of the SPManagedAccountPipeBind. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Get-SPProcessAccount -NetworkService -``` - -This example creates the SPProcessAccountPipeBind type by using the NetworkService account. - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPProcessAccount -NetworkService | New-SPServiceApplicationPool -Account $_ -``` - -This example creates an SPServiceApplicationPool account by using the NetworkService account returned by the Get-SPProcessAccount cmdlet. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -LocalService -Returns the LocalService account. - -```yaml -Type: SwitchParameter -Parameter Sets: LocalService -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalSystem -Returns the LocalSystem account. - -```yaml -Type: SwitchParameter -Parameter Sets: LocalSystem -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetworkService -Returns the NetworkService account. - -```yaml -Type: SwitchParameter -Parameter Sets: NetworkService -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProduct.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProduct.md deleted file mode 100644 index e129fcc7fd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProduct.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spproduct -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPProduct -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProduct - -## SYNOPSIS - -Returns a list of the SharePoint-related products installed in the farm and the versions of all updates installed for each product. - - - -## SYNTAX - -### Local -``` -Get-SPProduct [-AssignmentCollection <SPAssignmentCollection>] [-Local] [<CommonParameters>] -``` - -### Server -``` -Get-SPProduct [-AssignmentCollection <SPAssignmentCollection>] [-Server <SPServerPipeBind>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPProduct cmdlet returns a list of the SharePoint-related products installed in the farm and the versions of all updates installed for each product. -By default this cmdlet returns the list of SharePoint-related products installed in the farm. -Use the Local parameter to get only information about the local server or for a specific server to get the list, use the Server parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPProduct -Local -``` - -This example displays the SharePoint-related products installed on the local server. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Local -Returns product and update information for only the local computer. -If you use the Local parameter, you cannot use the Server parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: Local -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Server -Returns product and update information for a specified server. -If you use the Server parameter, you cannot use the Local parameter. - -```yaml -Type: SPServerPipeBind -Parameter Sets: Server -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProfileLeader.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProfileLeader.md deleted file mode 100644 index b435f54e5f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProfileLeader.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprofileleader -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPProfileLeader -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProfileLeader - -## SYNOPSIS -Returns the current company leaders. - -## SYNTAX - -``` -Get-SPProfileLeader [-ProfileServiceApplicationProxy] <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Use the Get-SPProfileLeader cmdlet to display the current company leaders. - -For additional information about SPProfileLeader cmdlets, see The *-SPProfileLeader Windows PowerShell cmdlets in SharePoint Server SP1 (https://go.microsoft.com/fwlink/p/?LinkId=226295) (https://go.microsoft.com/fwlink/p/?LinkId=226295). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE----------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Get-SPProfileLeader -ProfileServiceApplicationProxy $proxy -``` - -This example returns a company leader from the specific user profile service application as indicated by the variable, $upaProxy. - -## PARAMETERS - -### -ProfileServiceApplicationProxy -Specifies the name of the User Profile Service Application Proxy to use. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProfileServiceApplicationSecurity.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProfileServiceApplicationSecurity.md deleted file mode 100644 index c0b0ec5a7c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProfileServiceApplicationSecurity.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprofileserviceapplicationsecurity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPProfileServiceApplicationSecurity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProfileServiceApplicationSecurity - -## SYNOPSIS -Returns permission and identity information. - -## SYNTAX - -``` -Get-SPProfileServiceApplicationSecurity -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [-Type <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPProfileServiceApplicationSecurity cmdlet to display permission and identity information for the following User Profile objects: - -- Read individual My Sites -- Use Personal Features -- Use Social Features -- Create Personal Site - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE-------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -PS Get-SPProfileServiceApplicationSecurity -ProfileServiceApplicationProxy $proxy -Type MySiteReaderACL -``` - -This example displays MySite information on UPA Proxy 1. - -## PARAMETERS - -### -ProfileServiceApplicationProxy -Specifies the unique identifier for the proxy. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Type -Specifies the type of object to display. - -The type is any one of the following values: - -- MySiteReaderACL -- MySiteHostReaderACL -- UserACL - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectDatabaseQuota.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectDatabaseQuota.md deleted file mode 100644 index b59df83706..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectDatabaseQuota.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectdatabasequota -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectDatabaseQuota -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectDatabaseQuota - -## SYNOPSIS -Microsoft internal use only. - -## SYNTAX - -``` -Get-SPProjectDatabaseQuota -Url <Uri> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Microsoft internal use only. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### ------------ Example 1 -------------------- -``` - -``` - -## PARAMETERS - -### -Url -Microsoft internal use only. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Microsoft internal use only. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectDatabaseUsage.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectDatabaseUsage.md deleted file mode 100644 index a47c58d81e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectDatabaseUsage.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectdatabaseusage -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectDatabaseUsage -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectDatabaseUsage - -## SYNOPSIS -Returns an approximate size, in megabytes (MB) of the Project Web App data used in the content database. - -## SYNTAX - -``` -Get-SPProjectDatabaseUsage [-AssignmentCollection <SPAssignmentCollection>] -Url <Uri> [<CommonParameters>] -``` - -## DESCRIPTION -Returns an approximate size, in megabytes (MB) of the Project Web App data used in the content database. - -## EXAMPLES - -### Example 1 -``` -Get-SPProjectDatabaseUsage -Url https://contoso.com/sites/pwa -``` - -This example shows the size of the Project Web App data in the content data for the Project Web App site at https://contoso.com/sites/pwa. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the Project Web App site collection. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectEnterpriseProjectTaskSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectEnterpriseProjectTaskSync.md deleted file mode 100644 index f66c86ae79..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectEnterpriseProjectTaskSync.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectenterpriseprojecttasksync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectEnterpriseProjectTaskSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectEnterpriseProjectTaskSync - -## SYNOPSIS -Returns whether the task list sync between Project Web App and project sites is enabled or disabled. This cmdlet returns a value only if the feature has previously been enabled or disabled. - -## SYNTAX - -``` -Get-SPProjectEnterpriseProjectTaskSync [-AssignmentCollection <SPAssignmentCollection>] -Url <Uri> - [<CommonParameters>] -``` - -## DESCRIPTION -Returns whether the task list sync between Project Web App and project sites is enabled or disabled. This cmdlet returns a value only if the feature has previously been enabled or disabled. - -## EXAMPLES - -### Example 1 -``` -Get-SPProjectEnterpriseProjectTaskSync -Url https://contoso/sites/PWA -``` - -This example shows the syntax for getting the task sync status for the Project Web App site at https://contoso/sites/PWA. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the PWA site. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectEventServiceSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectEventServiceSettings.md deleted file mode 100644 index c76ed98fe1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectEventServiceSettings.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojecteventservicesettings -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectEventServiceSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectEventServiceSettings - -## SYNOPSIS -Returns the settings for the Microsoft Project Server Events Service. There is currently only one setting which is the port that the service listens on for requests. - -## SYNTAX - -``` -Get-SPProjectEventServiceSettings [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Returns the settings for the Microsoft Project Server Events Service. There is currently only one setting which is the port that the service listens on for requests. - -## EXAMPLES - -### Example 1 -``` -Get-SPProjectEventServiceSettings -``` - -This example shows what port the service is listening on. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectIsEmailNotificationEnabled.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectIsEmailNotificationEnabled.md deleted file mode 100644 index aad80dd8c8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectIsEmailNotificationEnabled.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectisemailnotificationenabled -applicable: Project Server 2016, Project Server 2019 -title: Get-SPProjectIsEmailNotificationEnabled -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectIsEmailNotificationEnabled - -## SYNOPSIS -Returns the Project Web App site level setting for email notifications. True if notifications is turned on, False otherwise. - -## SYNTAX - -``` -Get-SPProjectIsEmailNotificationEnabled [-Url] <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Returns the Project Web App site level setting for email notifications. True if notifications is turned on, False otherwise. - -## EXAMPLES - -### Example 1 -``` -Get-SPProjectIsEmailNotificationEnabled -Url https://contoso/sites/pwa -``` - -Returns the status of email notifications for the PWA site https://contoso/sites/pwa. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the Project Web App site. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectOdataConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectOdataConfiguration.md deleted file mode 100644 index 37ca7b2044..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectOdataConfiguration.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectodataconfiguration -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectOdataConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectOdataConfiguration - -## SYNOPSIS -Returns the settings for how the OData service is configured for an instance of Project Web App. - -## SYNTAX - -``` -Get-SPProjectOdataConfiguration [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPProjectOdataConfiguration cmdlet returns the settings for how the OData service is configured for an instance of Project Web App. -It returns the current settings for a list of parameters that specify paging, the enabling of various querying functionality, whether MaxResultsPerCollection has been enabled, and whether verbose errors are enabled. -The cmdlet can also be used to return an itemized list of entities that have an override specified for their maximum page size. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### ----------------------EXAMPLE 1----------------------- -``` -Get-SPProjectOdataConfiguration -``` - -This example returns the OData configuration for the instance of Project Web App. - -### ----------------------EXAMPLE 2----------------------- -``` -C:\PS>(Get-SPProjectOdataConfiguration).EntitySetsWithMaxPAgeSizeOverride -``` - -This example returns the list of entities that have the MaxPageSizeOverride option configured. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectPCSSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectPCSSettings.md deleted file mode 100644 index 596abe6c32..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectPCSSettings.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectpcssettings -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectPCSSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectPCSSettings - -## SYNOPSIS -Gets the settings for the Project Calculation Engine on the Project Server. - -## SYNTAX - -``` -Get-SPProjectPCSSettings [-ServiceApplication <PsiServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPProjectPCSSettings cmdlet lets users read the settings that control the operations of the Project Calculation Engine on Project Server. -The cmdlet requires you to identify the Project Server Service Application. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Get-SPProjectPCSSettings -sa "Project Service Application" -``` - -This example reads the settings for the Project Calculation Engine running on the "Project Service Application" service application. - -## PARAMETERS - -### -ServiceApplication -The Project Server Service Application for which the settings are to be read. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectPermissionMode.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectPermissionMode.md deleted file mode 100644 index e0466e5def..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectPermissionMode.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectpermissionmode -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectPermissionMode -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectPermissionMode - -## SYNOPSIS -Returns the permission mode for a Project Web App (PWA) instance. - -## SYNTAX - -``` -Get-SPProjectPermissionMode [-Url] <Uri> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPProjectPermissionMode cmdlet returns the presently configured permission mode for the provided PWA instance. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------EXAMPLE 1------------------- -``` -Get-SPProjectPermissionMode -Url https://AppServer/pwa -``` - -This example returns the permission mode setting for a PWA instance. - -## PARAMETERS - -### -Url -Specifies the URL of the PWA instance for which you want to retrieve the permission mode. - -The type must be a valid URL, in the form https://\<ServerName\>/\<PWASite\>. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPProjectPermissionMode](Set-SPProjectPermissionMode.md) - -[Invoke-SPProjectActiveDirectoryGroupSync](Invoke-SPProjectActiveDirectoryGroupSync.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectQueueSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectQueueSettings.md deleted file mode 100644 index 4e89ea2495..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectQueueSettings.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectqueuesettings -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectQueueSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectQueueSettings - -## SYNOPSIS -Returns a list of all Project Server Queue settings and their current values for the specified Project Server Service Application. - -## SYNTAX - -``` -Get-SPProjectQueueSettings [-ServiceApplication <PsiServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Returns a list of all Project Server Queue settings and their current values for a specific Project Server Service Application. -Settings returned include the following: - -- MaxDegreeOfConcurrency -- MsgRetryInterval -- MsgRetryLimit -- SqlRetryInterval -- SqlRetryLimit -- SqlCommandTimeout -- CleanupSuccessAgeLimit -- CleanupNonSuccessAgeLimit -- PeriodicTasksInterval -- QueueTimeout -- MaxConnections - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Get-SPProjectQueueSettings -ServiceApplication "Project Service Application" -``` - -This example retrieves the queue settings for the "Project Service Application" service application. - -## PARAMETERS - -### -ServiceApplication -Specifies the Project Server service application to target. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefg; a valid name of a Project Server Service Application (for example, ProjectServiceApp1); or an instance of a valid PsiServiceApplication object. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectWebInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectWebInstance.md deleted file mode 100644 index d3c3b690d9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPProjectWebInstance.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spprojectwebinstance -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Get-SPProjectWebInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPProjectWebInstance - -## SYNOPSIS -Returns an instance of a Project Web App site. - -## SYNTAX - -``` -Get-SPProjectWebInstance [-ServiceApplication <PsiServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Url <Uri>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPProjectWebInstance cmdlet returns an instance of a Project Web App site, including the following information: - -- ID (GUID) -- Service application name -- Parent web app -- Project Web App URL -- Locale identifier (LCID) -- Admin account -- Project Web App database server -- Database name for the Project Web App database -- Provisioning status -- Report center status -- Site ID (GUID) - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Get-SPProjectWebInstance -Url https://server/pwa -``` - -This example returns the properties for a Project Web App instance at https://server/pwa. - -## PARAMETERS - -### -ServiceApplication -Specifies the name of the Project Server service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Project Web App instance (for example, ProjectWebApp1); or an instance of a valid PsiServiceApplication object. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -Specifies the URL of the Project Web App instance to get. - -The type must be a valid URL, in the form https://\<server_name\>/\<PWA_name\>. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRequestManagementSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRequestManagementSettings.md deleted file mode 100644 index ca15d0a880..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRequestManagementSettings.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sprequestmanagementsettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPRequestManagementSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPRequestManagementSettings - -## SYNOPSIS - -Returns a Request Manager object. - - - -## SYNTAX - -``` -Get-SPRequestManagementSettings [-Identity] <SPRequestManagementSettingsPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPRequestManagementSettings cmdlet returns a Request Manager object which is base for performing any request manager management operation. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE------- -``` -Get-SPRequestManagementSettings -Identity <GUID> -``` - -This example returns a request manager object for a specified identity. - -## PARAMETERS - -### -Identity -Specifies the web-application for which a user wants to enable routing or throttling. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPRequestManagementSettings](Set-SPRequestManagementSettings.md) - -[New-SPRequestManagementRuleCriteria](New-SPRequestManagementRuleCriteria.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingMachineInfo.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingMachineInfo.md deleted file mode 100644 index fa906364b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingMachineInfo.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sproutingmachineinfo -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPRoutingMachineInfo -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPRoutingMachineInfo - -## SYNOPSIS - -Returns all the routing targets. - - - -## SYNTAX - -``` -Get-SPRoutingMachineInfo [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Availability <SPRoutingMachineAvailability>] - [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPRoutingMachineInfo cmdlet to return all the routing targets that are being used by the Request Manager object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE------------ -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -Get-SPRoutingMachineInfo -RequestManagementSettings $rm -``` - -This example returns a routing target for a specified identity. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to return. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Availability -Specifies whether or not the specified computer will be available for routing. -If no value is specified, all computers are returned. - -The values for this parameter are filtered based on availability. - -The valid values are: - ---Available ---Unavailable - -```yaml -Type: SPRoutingMachineAvailability -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the computer for which you want to return routing information. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingMachineInfo](Add-SPRoutingMachineInfo.md) - -[Remove-SPRoutingMachineInfo](Remove-SPRoutingMachineInfo.md) - -[Set-SPRoutingMachineInfo](Set-SPRoutingMachineInfo.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingMachinePool.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingMachinePool.md deleted file mode 100644 index 4f83137a6c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingMachinePool.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sproutingmachinepool -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPRoutingMachinePool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPRoutingMachinePool - -## SYNOPSIS - -Returns all available routing pools. - - - -## SYNTAX - -``` -Get-SPRoutingMachinePool [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPRoutingMachinePool cmdlet to return all available routing pools by using the RequestManagementSettings parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE--------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -Get-SPRoutingMachinePool -RequestManagementSettings $rm -``` - -This example returns a routing pool for the specified identity. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to return. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the machine pool to return. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingMachinePool](Add-SPRoutingMachinePool.md) - -[Remove-SPRoutingMachinePool](Remove-SPRoutingMachinePool.md) - -[Set-SPRoutingMachinePool](Set-SPRoutingMachinePool.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingRule.md deleted file mode 100644 index 4258739487..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPRoutingRule.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sproutingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPRoutingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPRoutingRule - -## SYNOPSIS - -Returns all routing rules. - - - -## SYNTAX - -``` -Get-SPRoutingRule [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPRoutingRule cmdlet to return routing rules for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE------------ -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -Get-SPRoutingRule -RequestManagementSettings $rm -``` - -This example returns a routing rule for the farm. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to return. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the rule to return. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingRule](Add-SPRoutingRule.md) - -[Remove-SPRoutingRule](Remove-SPRoutingRule.md) - -[Set-SPRoutingRule](Set-SPRoutingRule.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabase.md deleted file mode 100644 index db4ea3e725..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabase.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPScaleOutDatabase - -## SYNOPSIS - -Returns all scale-out database objects. - - - -## SYNTAX - -``` -Get-SPScaleOutDatabase -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPScaleOutDatabase cmdlet to returns all scale-out database objects for the specified service application. - -A scale-out database is a database which implements the Shared Service Database Scale Out Generic Protocol. -For additional information about the Database Scale Out Generic Protocol, see SharePoint Shared Service Database Scale Out Generic Protocol Specification (https://msdn.microsoft.com/en-us/library/hh656675(office.12).aspx) - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE-------------- -``` -C:\PS>$serviceApplication = Get-SPServiceApplication -Name "AppManagement" - -Get-SPScaleOutDatabase -ServiceApplication $serviceApplication -``` - -This example gets all scale-out databases for the given service application by using the $serviceApplication variable. - -## PARAMETERS - -### -ServiceApplication -Specifies the service application of the scale-out databases. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPScaleOutDatabase](Add-SPScaleOutDatabase.md) - -[Remove-SPScaleOutDatabase](Remove-SPScaleOutDatabase.md) - -[Split-SPScaleOutDatabase](Split-SPScaleOutDatabase.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseDataState.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseDataState.md deleted file mode 100644 index 705c47966e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseDataState.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spscaleoutdatabasedatastate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPScaleOutDatabaseDataState -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPScaleOutDatabaseDataState - -## SYNOPSIS - -Returns the state information about the specified scale-out database. - - - -## SYNTAX - -### UnattachedDatabase -``` -Get-SPScaleOutDatabaseDataState -ConnectionString <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-IsAzureDatabase] [-WhatIf] [<CommonParameters>] -``` - -### AttachedDatabase -``` -Get-SPScaleOutDatabaseDataState -Database <SPDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Get-SPScaleOutDatabaseDataState cmdlet to return state information about the specified scale-out database or about the database which will be connected with the specified connection string. -The database state information includes total count of partitions, total weight of the partitions, the range and the subranges of the database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE-------------- -``` -C:\PS>$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication - -C:\PS>$database = $databases[0] - -Get-SPScaleOutDatabaseDataState -Database $database -``` - -This example gets the data state of the scale-out database for the first scale-out database of the given service application. - -## PARAMETERS - -### -ConnectionString -Specifies the connection string for the scale-out database from which to return the state information. - -```yaml -Type: String -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -Specifies the scale-out database to return the state information about. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: AttachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsAzureDatabase -Specifies whether the state information of the scale-out database is in the form of a Microsoft SQL Azure Database. - -```yaml -Type: SwitchParameter -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseInconsistency.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseInconsistency.md deleted file mode 100644 index 36e7809816..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseInconsistency.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spscaleoutdatabaseinconsistency -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPScaleOutDatabaseInconsistency -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPScaleOutDatabaseInconsistency - -## SYNOPSIS - -Displays all inconsistencies related to scale-out databases' ranges. - - - -## SYNTAX - -``` -Get-SPScaleOutDatabaseInconsistency -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPScaleOutDatabaseInconsistency cmdlet to return all inconsistencies related to scale out databases' ranges and subranges for a specified service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE-------------- -``` -C:\PS>$serviceApplication = Get-SPServiceApplication -Name "AppManagement" - -Get-SPScaleOutDatabaseInconsistency -ServiceApplication $serviceApplication -``` - -This example gets all the scale-out inconsistencies for the given service application. - -## PARAMETERS - -### -ServiceApplication -Specifies the service application for which to return the scale-out inconsistencies. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseLogEntry.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseLogEntry.md deleted file mode 100644 index 7cb08cf097..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPScaleOutDatabaseLogEntry.md +++ /dev/null @@ -1,213 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spscaleoutdatabaselogentry -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPScaleOutDatabaseLogEntry -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPScaleOutDatabaseLogEntry - -## SYNOPSIS - -Queries a scale-out database for scale-out logs. - - - -## SYNTAX - -``` -Get-SPScaleOutDatabaseLogEntry -Count <Int32> -Database <SPDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-CorrelationId <Guid>] - [-MajorAction <SPScaleOutDatabaseMajorAction>] [-RangeLimitPoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPScaleOutDatabaseLogEntry cmdlet to query a scale-out database for scale-out logs that include specified criteria. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE----------- -``` -C:\PS>$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication - -C:\PS>$database = $databases[0] - -Get-SPScaleOutDatabaseLogEntry -Database $database -Count 10 -MajorAction DataMove -``` - -This example gets the 10 most recent scale-out log entries from the first scale-out database of the given service application. - -## PARAMETERS - -### -Count -Specifies the number of scale-out log entries to return. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -Specifies the scale-out database from which to return the scale-out logs - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CorrelationId -Specifies the correlation id of the scale-out logs to be returned. -Correlation id of the log entries that belong to the same major action are the same. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MajorAction -Specifies the major action of the scale-out log entries to be returned. -The values are the following: - -DataMove -A data migration operation between two scale-out databases. - -Recovery -Any data recovery operation that is performed to recover from a failure. - -```yaml -Type: SPScaleOutDatabaseMajorAction -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RangeLimitPoint - -Specifies the range limit point of the scale-out log entries to be returned. - -The range limit point has different meaning depending on the action that records the log entry. - ---If the action is to create, change or delete a data subrange, the range limit point represents the following: ---If the action targets a lower data subrange, the range limit point represents the start point of that lower data subrange. ---If the action targets an upper data subrange, the range limit point represents the end point of that upper data subrange. ---If the action is to extend a data range, the range limit point represents the following: ---If the action extends the start point of the data range, range limit point represents the new start point of the data range. ---If the action extends the end point of the data range, range limit point represents the new end point of the data range. - - - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecureStoreApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecureStoreApplication.md deleted file mode 100644 index 0537446c9a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecureStoreApplication.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsecurestoreapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSecureStoreApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSecureStoreApplication - -## SYNOPSIS -Returns a Secure Store application. - -## SYNTAX - -### NameSet -``` -Get-SPSecureStoreApplication -Name <String> -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### AllSet -``` -Get-SPSecureStoreApplication -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-All] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPSecureStoreApplication cmdlet returns a Secure Store application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApplication" -``` - -This example gets the Secure Store application for the target application with the name ContosoTargetApplication. - -### ------------------EXAMPLE 2------------------ -``` -Get-SPSecureStoreApplication -ServiceContext http://contoso -All -``` - -This example returns all of the Secure Store applications http://contoso. - -## PARAMETERS - -### -Name -Specifies the name of the Secure Store application to get. - -```yaml -Type: String -Parameter Sets: NameSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context for the local Secure Store application to connect to. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -All -Returns all secure store applications for the given Service Context. - -```yaml -Type: SwitchParameter -Parameter Sets: AllSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecureStoreSystemAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecureStoreSystemAccount.md deleted file mode 100644 index 63699d823c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecureStoreSystemAccount.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsecurestoresystemaccount -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSecureStoreSystemAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSecureStoreSystemAccount - -## SYNOPSIS -Returns a list of users from a designated list. - -## SYNTAX - -``` -Get-SPSecureStoreSystemAccount [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPSecureStoreSystemAccount cmdlet to return a list of user accounts which are considered to be a system account. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE---------- -``` -Get-SPSecureStoreSystemAccount -``` - -This example returns a list of user accounts for the secure store system. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPSecureStoreSystemAccount](Add-SPSecureStoreSystemAccount.md) - -[Remove-SPSecureStoreSystemAccount](Remove-SPSecureStoreSystemAccount.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecurityTokenServiceConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecurityTokenServiceConfig.md deleted file mode 100644 index ffa70a1f00..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSecurityTokenServiceConfig.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsecuritytokenserviceconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSecurityTokenServiceConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSecurityTokenServiceConfig - -## SYNOPSIS - -Returns the security token service (STS) for the farm. - - - -## SYNTAX - -``` -Get-SPSecurityTokenServiceConfig [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPSecurityTokenServiceConfig cmdlet reads the security token service (STS) for the farm. -An STS authenticates security tokens in incoming SOAP messages. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Set-SPSecurityTokenServiceConfig -ServiceTokenLifetime 1000 -``` - -This example gets the security token service (STS) for the farm and sets the expiration for the service token cache to 1000 minutes. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServer.md deleted file mode 100644 index cf169d4531..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServer.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserver -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServer - -## SYNOPSIS -Returns the server or servers in the farm that match the given identity. - - -## SYNTAX - -``` -Get-SPServer [[-Identity] <SPServerPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPServer cmdlet returns the SPServer object for the given identity (if it exists in the farm). -If no parameters are specified, the cmdlet returns all servers in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPServer -``` - -This example returns all servers in the local farm in a list. - -### --------------EXAMPLE 2----------------- -``` -Get-SPServer | Where{ $_.NeedsUpgrade -eq $TRUE} -``` - -This example returns a list of all servers in the farm that need an upgrade. - -## PARAMETERS - -### -Identity -Specifies the address of the server to return. - -```yaml -Type: SPServerPipeBind -Parameter Sets: (All) -Aliases: Address -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabase.md deleted file mode 100644 index 26b3166730..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabase.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserverscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServerScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServerScaleOutDatabase - -## SYNOPSIS - -Returns all scale-out database objects. - - - -## SYNTAX - -``` -Get-SPServerScaleOutDatabase -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-SPServerScaleOutDatabase cmdlet to return all scale-out database objects for the specified service application. - -A scale-out database is a database which implements the Shared Service Database Scale Out Generic Protocol. -For more information, see SharePoint Shared Service Database Scale Out Generic Protocol Specification (https://go.microsoft.com/fwlink/p/?LinkId=273867) - - - - -## EXAMPLES - -### ----------EXAMPLE-------------- -``` -C:\PS>$serviceApplication = Get-SPServiceApplication -Name "AppManagement" - -Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication -``` - -This example gets all scale-out databases for the given service application by using the $serviceApplication variable. - - -## PARAMETERS - -### -ServiceApplication - -Specifies the service application of the scale-out databases. - - - - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Add-SPServerScaleOutDatabase](Add-SPServerScaleOutDatabase.md) - -[Remove-SPServerScaleOutDatabase](Remove-SPServerScaleOutDatabase.md) - -[Split-SPServerScaleOutDatabase](Split-SPServerScaleOutDatabase.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseDataState.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseDataState.md deleted file mode 100644 index ecdc221d00..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseDataState.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserverscaleoutdatabasedatastate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServerScaleOutDatabaseDataState -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServerScaleOutDatabaseDataState - -## SYNOPSIS - -Returns the state information about the specified scale-out database. - - - - -## SYNTAX - -### UnattachedDatabase -``` -Get-SPServerScaleOutDatabaseDataState -ConnectionString <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-IsAzureDatabase] [-WhatIf] [<CommonParameters>] -``` - -### AttachedDatabase -``` -Get-SPServerScaleOutDatabaseDataState -Database <SPDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Get-SPServerScaleOutDatabaseDataState cmdlet to return state information about the specified scale-out database or about the database which will be connected with the specified connection string. -The database state information includes total count of partitions, total weight of the partitions, the range and the subranges of the database. - - - - -## EXAMPLES - -### ----------------EXAMPLE-------------- -``` -C:\PS>$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication - -C:\PS>$database = $databases[0] - -Get-SPServerScaleOutDatabaseDataState -Database $database -``` - -This example gets the data state of the scale-out database for the first scale-out database of the given service application. - - -## PARAMETERS - -### -ConnectionString - -Specifies the connection string for the scale-out database from which to return the state information. - - - - - -```yaml -Type: String -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database - -Specifies the scale-out database for which the command returns state information. - - - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: AttachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsAzureDatabase - -Specifies whether the state information of the scale-out database is in the form of a Microsoft Windows Azure SQL Database. - - - - - -```yaml -Type: SwitchParameter -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseInconsistency.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseInconsistency.md deleted file mode 100644 index 4df1cddfd0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseInconsistency.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserverscaleoutdatabaseinconsistency -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServerScaleOutDatabaseInconsistency -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServerScaleOutDatabaseInconsistency - -## SYNOPSIS - -Displays all inconsistencies related to scale-out databases' ranges. - - - - -## SYNTAX - -``` -Get-SPServerScaleOutDatabaseInconsistency -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-SPServerScaleOutDatabaseInconsistency cmdlet to return all inconsistencies related to scale out databases' ranges and subranges for a specified service application. - - - - -## EXAMPLES - -### -------------EXAMPLE-------------- -``` -C:\PS>$serviceApplication = Get-SPServiceApplication -Name "AppManagement" - -Get-SPServerScaleOutDatabaseInconsistency -ServiceApplication $serviceApplication -``` - -This example gets all the scale-out inconsistencies for the given service application. - -## PARAMETERS - -### -ServiceApplication - -Specifies the service application for which to return the scale-out inconsistencies. - - - - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseLogEntry.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseLogEntry.md deleted file mode 100644 index 51169d74a5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServerScaleOutDatabaseLogEntry.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserverscaleoutdatabaselogentry -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServerScaleOutDatabaseLogEntry -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServerScaleOutDatabaseLogEntry - -## SYNOPSIS - -Queries a scale-out database for scale-out logs. - - - -## SYNTAX - -``` -Get-SPServerScaleOutDatabaseLogEntry -Count <Int32> -Database <SPDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-CorrelationId <Guid>] - [-MajorAction <SPScaleOutDatabaseMajorAction>] [-RangeLimitPoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Get-SPServerScaleOutDatabaseLogEntry cmdlet to query a scale-out database for scale-out logs that include specified criteria. - - - -## EXAMPLES - -### -------------EXAMPLE----------- -``` -C:\PS>$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication - -C:\PS>$database = $databases[0] - -Get-SPServerScaleOutDatabaseLogEntry -Database $database -Count 10 -MajorAction DataMove -``` - -This example gets the 10 most recent scale-out log entries from the first scale-out database of the given service application. - - -## PARAMETERS - -### -Count - -Specifies the number of scale-out log entries to return. - - - - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database - -Specifies the scale-out database from which to return the scale-out logs - - - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CorrelationId - -Specifies the correlation id of the scale-out logs to be returned. -Correlation id of the log entries that belong to the same major action are the same. - - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MajorAction - -Specifies the major action of the scale-out log entries to be returned. -The values are the following: - -DataMove -A data migration operation between two scale-out databases. - -Recovery -Any data recovery operation that is performed to recover from a failure. - - - - -```yaml -Type: SPScaleOutDatabaseMajorAction -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RangeLimitPoint - -Specifies the range limit point of the scale-out log entries to be returned. - -The range limit point has different meaning depending on the action that records the log entry. - - - - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPService.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPService.md deleted file mode 100644 index 1c08f388c3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPService.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spservice -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPService - -## SYNOPSIS -Gets a service in the farm. - -## SYNTAX - -``` -Get-SPService [[-Identity] <SPServicePipeBind>] [-All] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPService cmdlet gets a service in the farm. - -## EXAMPLES - -### Example 1 -``` -Get-SPService -Identity 'Microsoft SharePoint Server Diagnostics Service' -``` - -This example gets the Microsoft SharePoint Server Diagnostics Service in the farm. - -## PARAMETERS - -### -All -Specifies all services in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the name of the service to get. - -```yaml -Type: SPServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServicePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplication.md deleted file mode 100644 index 49ca22d3c4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplication.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceApplication - -## SYNOPSIS - -Returns the specified service application. - - - -## SYNTAX - -``` -Get-SPServiceApplication [[-Identity] <SPServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPServiceApplication cmdlet returns the service application specified by the Identity parameter. -If no parameter is specified, the cmdlet returns all service applications in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1---------------------- -``` -Get-SPServiceApplication -``` - -This example returns all service applications in the farm. - -### ------------------EXAMPLE 2---------------------- -``` -Get-SPServiceApplication -Identity e2c2be70-6382-4ce7-8a44-ae7dadff5597 -``` - -This example returns the service application that has the Identity "e2c2be70-6382-4ce7-8a44-ae7dadff5597". - -### ------------------EXAMPLE 3---------------------- -``` -Get-SPServiceApplication -Name AccountingServiceApp -``` - -This example returns the service application that has the friendly name "AccountingServiceApp". - -You can use either the Identity or the Name parameter but if you use both, the command will process the Identity first and ignore the Name. - -## PARAMETERS - -### -Identity -Specifies the GUID of the service application to get. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the friendly name of the new usage application.The type must be a valid name of a usage application; for example, UsageApplication1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationEndpoint.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationEndpoint.md deleted file mode 100644 index c8d7980b8d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationEndpoint.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserviceapplicationendpoint -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceApplicationEndpoint -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceApplicationEndpoint - -## SYNOPSIS - -Returns the endpoint of a service application. - - - -## SYNTAX - -### Identity -``` -Get-SPServiceApplicationEndpoint [-Identity] <SPServiceEndpointPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### Name -``` -Get-SPServiceApplicationEndpoint -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPServiceApplicationEndpoint cmdlet sets the host of a service endpoint. -Use the second parameter set and do not specify the Name parameter to return a collection of all endpoints for the specified service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE-------------------- -``` -Get-SPServiceApplicationEndpoint -ServiceApplication "ServiceSubApp1" -``` - -This example returns the SPServiceEndpoint object based on the specified service application. - -## PARAMETERS - -### -Identity -Specifies the service endpoint to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URI of an endpoint address, in the form https://sitename:8003/servicemodelsamples/service; or an instance of a valid SPServiceEndpoint object. - -```yaml -Type: SPServiceEndpointPipeBind -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubscriptionSettingsApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: Name -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the service application endpoint. - -The type must be a valid name of an service application endpoint; for example, SvcAppEndpoint1. - -```yaml -Type: String -Parameter Sets: Name -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationPool.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationPool.md deleted file mode 100644 index 61f7615828..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationPool.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserviceapplicationpool -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceApplicationPool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceApplicationPool - -## SYNOPSIS - -Returns the specified Internet Information Services (IIS) application pool. - - - -## SYNTAX - -``` -Get-SPServiceApplicationPool [[-Identity] <SPIisWebServiceApplicationPoolPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPServiceApplicationPool cmdlet returns the IIS application pool specified by the Identity parameter, or returns all application pools if the Identity parameter is not specified. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPServiceApplicationPool -``` - -This example returns all the service application pools in the farm. - -## PARAMETERS - -### -Identity -Specifies the name or identifier (ID) of the application pool to get. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationProxy.md deleted file mode 100644 index fc9dc98f67..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationProxy.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceApplicationProxy - -## SYNOPSIS - -Returns an instance of the specified service application proxy. - - - -## SYNTAX - -``` -Get-SPServiceApplicationProxy [[-Identity] <SPServiceApplicationProxyPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPServiceApplicationProxy cmdlet returns an instance of the service application proxy specified by the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPServiceApplicationProxy -``` - -This example retrieves all the service application proxies in the farm. - -## PARAMETERS - -### -Identity -Specifies the GUID of the service application proxy to return. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationProxyGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationProxyGroup.md deleted file mode 100644 index f8b44a2b17..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationProxyGroup.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserviceapplicationproxygroup -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceApplicationProxyGroup -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceApplicationProxyGroup - -## SYNOPSIS - -Returns the proxy group for the specified service application. - - - -## SYNTAX - -### Identity -``` -Get-SPServiceApplicationProxyGroup [[-Identity] <SPServiceApplicationProxyGroupPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### Default identity -``` -Get-SPServiceApplicationProxyGroup [-Default] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPServiceApplicationProxyGroup cmdlet displays a list of the proxy groups in the farm. -To display a specific proxy group, use the Identity parameter. -If no parameter value is specified, a list of all proxy groups is displayed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPServiceApplicationProxyGroup -``` - -This example retrieves all of the service application proxy groups in the farm. - -## PARAMETERS - -### -Identity -Specifies the name or the GUID of the proxy group. - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Default -Returns the default service proxy group for the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: Default identity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationSecurity.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationSecurity.md deleted file mode 100644 index 9ae0d12aef..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceApplicationSecurity.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserviceapplicationsecurity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceApplicationSecurity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceApplicationSecurity - -## SYNOPSIS - -Returns the SPObjectSecurity object for a service application. - - - -## SYNTAX - -``` -Get-SPServiceApplicationSecurity [-Identity] <SPServiceApplicationPipeBind> [-Admin] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPServiceApplicationSecurity cmdlet returns a security object for the specified service application. -Use this cmdlet with the Grant-SPObjectSecurity and Set-SPServiceApplicationSecurity cmdlets to manage security for a service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$security = Get-SPServiceApplicationSecurity $serviceApp -Admin -Grant-SPObjectSecurity $security $principal "Full Control" -Set-SPServiceApplicationSecurity $serviceApp -Admin $security -``` - -This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on a service application, and adds a new user principal to that ACL. -The new user is an administrator for the service application $serviceApp. - -## PARAMETERS - -### -Identity -Specifies the service application to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application (for example, SearchServiceApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Admin -Returns the access control list (ACL) that contains the administrators list of the service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceContext.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceContext.md deleted file mode 100644 index 971e9b35c9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceContext.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spservicecontext -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceContext -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceContext - -## SYNOPSIS - -Returns a service context. - - - -## SYNTAX - -### Site -``` -Get-SPServiceContext [-Site] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### SiteSubscription -``` -Get-SPServiceContext -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPServiceContext cmdlet returns a service context or a collection of service contexts. -Specify the Site parameter to return an individual service context, or specify the SiteSubscription parameter to return a collection of service contexts. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE--------------- -``` -C:\PS>$sitesub = Get-SPSiteSubscription https://my.contoso.com/ - -Get-SPServiceContext $sitesub -``` - -This example returns the service context for a site in a hosted environment. - -## PARAMETERS - -### -Site -Returns the service context for only the Web application that contains the specified site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: Site -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Returns all of the service contexts for all Web applications in which the specified site subscription has site collections. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscriptionConfig1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceHostConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceHostConfig.md deleted file mode 100644 index d6594fe4e6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceHostConfig.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spservicehostconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceHostConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceHostConfig - -## SYNOPSIS - -Returns the common Web service settings. - - - -## SYNTAX - -``` -Get-SPServiceHostConfig [-AssignmentCollection <SPAssignmentCollection>] [-Default] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPServiceHostConfig returns the common Web service settings. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE------------------- -``` -Get-SPServiceHostConfig -``` - -This example displays the Web service settings. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Default -This parameter has no effect. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceInstance.md deleted file mode 100644 index c8d37634fd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPServiceInstance.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPServiceInstance - -## SYNOPSIS - -Returns the services instance for a specific server or the entire farm. - - - -## SYNTAX - -### Identity -``` -Get-SPServiceInstance [[-Identity] <SPServiceInstancePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-All] [<CommonParameters>] -``` - -### Server -``` -Get-SPServiceInstance -Server <SPServerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-All] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPServiceInstance cmdlet returns the services instance specified by the Identity parameter for a specific server. -If the Server parameter is not specified, the Get-SPServiceInstance cmdlet returns results for the entire farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPServiceInstance -Server ServerA -``` - -This example displays the service instances from a given server. - -## PARAMETERS - -### -Identity -Specifies the GUID of the service instance. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPServiceInstancePipeBind -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Server -Specifies the server from which to return the service instance. - -```yaml -Type: SPServerPipeBind -Parameter Sets: Server -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -All -Returns all services instance in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSessionStateService.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSessionStateService.md deleted file mode 100644 index b616a30ba1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSessionStateService.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsessionstateservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSessionStateService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSessionStateService - -## SYNOPSIS -Returns the properties of the session state service, including time-out and database settings. - -## SYNTAX - -``` -Get-SPSessionStateService [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPSessionStateService cmdlet reads the properties of the session state service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPSessionStateService -``` - -This example returns the current configuration of the session state service. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPShellAdmin.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPShellAdmin.md deleted file mode 100644 index 9c51657878..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPShellAdmin.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spshelladmin -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPShellAdmin -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPShellAdmin - -## SYNOPSIS - -Returns the names of all users who have the SharePoint_Shell_Access role. - - - -## SYNTAX - -``` -Get-SPShellAdmin [[-database] <SPDatabasePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPShellAdmin cmdlet to return the names of all users who have the SharePoint_Shell_Access role in a database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE---------------------- -``` -Get-SPShellAdmin -database 4251d855-3c15-4501-8dd1-98f960359fa6 -``` - -This example returns the name of each user who has the SharePoint_Shell_Access role in the database specified. - -## PARAMETERS - -### -database -Specifies the GUID of the database or the Database Object that includes the SharePoint_Shell_Access role whose user names you want to display. -If the database parameter is not specified, the configuration database is used. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSite.md deleted file mode 100644 index 6b5589db4b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSite.md +++ /dev/null @@ -1,386 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSite - -## SYNOPSIS - -Returns all site collections that match the specified criteria. - - - -## SYNTAX - -### AllSitesInIdentity -``` -Get-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <Int32>] [-Confirm] [-Filter <ScriptBlock>] [-Limit <String>] [-Regex] [-WhatIf] - [<CommonParameters>] -``` - -### AllSitesInContentDB -``` -Get-SPSite -ContentDatabase <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <Int32>] [-Confirm] [-Filter <ScriptBlock>] [-Limit <String>] [-WhatIf] - [-NeedsB2BUpgrade] [<CommonParameters>] -``` - -### AllSitesInSiteSubscription -``` -Get-SPSite -SiteSubscription <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <Int32>] [-Confirm] [-Filter <ScriptBlock>] [-Limit <String>] [-WhatIf] - [<CommonParameters>] -``` - -### AllSitesInWebApplication -``` -Get-SPSite [-AssignmentCollection <SPAssignmentCollection>] [-CompatibilityLevel <Int32>] [-Confirm] - [-Filter <ScriptBlock>] [-Limit <String>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPSite cmdlet returns either a single site that matches the Identity parameter, or all the sites that match the Filter parameter for the specified scope. -The scopes are the WebApplication, ContentDatabase , and SiteSubscription parameters. -If none of these scopes is provided, the scope is the farm. -If the scope is specified with no Filter parameter, all sites in that scope are returned. - -The Identity parameter supports providing a partial URL that ends in a wildcard character (*). -All site collections that match this partial URL for the specified scope are returned. -Additionally, if the Regex parameter is provided, the Identity parameter is treated as a regular expression and any site collection with a URL provided in the given scope that matches the expression is returned. - -The Filter parameter is a server-side filter for certain site collection properties that are stored in the content database; without the Filter parameter, filtering on these properties is a slow process. -These site collection properties are Owner, SecondaryOwner, and LockState. -The Filter parameter is a script block that uses the same syntax as a Where-Object statement, but is run on the server for faster results. - -Valid values for LockState are: Unlock, NoAdditions, ReadOnly, NoAccess. - -It is important to note that every site collection that the Get-SPSite cmdlet returns is automatically destroyed at the end of the pipeline. -To store the results of Get-SPSite in a local variable, use the Start-SPAssignment and Stop-SPAssignment cmdlets to avoid memory leaks. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1--------------------- -``` -Get-SPSite 'https://<site name>' | Get-SPWeb -Limit All | Select Title -``` - -This example gets the collection of subweb titles in site collection at https://\<site name\>. - -### ------------------EXAMPLE 2--------------------- -``` -Get-SPSite -ContentDatabase "b399a366-d899-4cff-8a9b-8c0594ee755f" | Format-Table -Property Url, Owner, SecondaryOwner -``` - -This example gets a subset of data from all sites in the content database b399a366-d899-4cff-8a9b-8c0594ee755f. - -### ------------------EXAMPLE 3--------------------- -``` -Start-SPAssignment -Global - -$s = Get-SPSite -Identity https://<MyApp>/Sites/Site1 - -$s.Url - -Stop-SPAssignment -Global -``` - -This example gets the sites specified by the Identity parameter and inserts the results in the variable s - -The previous example uses the Global method of assignment collection. -The Global method is easy to use but the contents of this object grows quickly. -Be careful not to run a Get-SPSite command that returns many results while global assignment is enabled. - -### ------------------EXAMPLE 4--------------------- -``` -$GC = Start-SPAssignment -$Sites = $GC | Get-SPSite -Filter {$_.Owner -eq "DOMAIN\JDow"} -Limit 50 -Stop-SPAssignment $GC -``` - -This example gets the first 50 sites owned by user DOMAIN\JDow by using a server-side query, and assigns them to a local variable. - -This example uses advanced assignment collection methods. - -### ------------------EXAMPLE 5--------------------- -``` -Get-SPWebApplication https://<site name> | Get-SPSite -Limit All |ForEach-Object {$sum=0}{ $sum+=$_.Usage.Storage }{$sum} -``` - -This example shows a command that returns the sum of the disk space usage for all sites in a given web application. - -### ------------------EXAMPLE 6--------------------- -``` -Get-SPSite -Identity "https://localserver/(my|personal)/sites" -Regex -``` - -This example returns all sites that match the given regular expression. - -The Quotes on the Identity parameter are required when the Regex parameter is used. - -### ------------------EXAMPLE 7--------------------- -``` -Get-SPSite https://<site name>/sites/teams/* -Limit 100 -``` - -This example gets up to 100 of the sites under the URL https://sitename/sites/teams. - -### ------------------EXAMPLE 8--------------------- -``` -Get-SPSite | select url, @{Expression={$_.Usage.Storage}} -``` - -This example gets the amount of storage used by a site collection, by using the storage field of the .UsageInfo property. - -### ------------------EXAMPLE 9--------------------- -``` -Get-SPSite -Limit all -CompatibilityLevel 14 -``` - -This example returns all SharePoint Server mode site collections. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site collection to get. - -The type must be a valid URL, in the form, https://server_name or https://server_name/sites/sitename, or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPSitePipeBind -Parameter Sets: AllSitesInIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the GUID of the content database from which to list site collections. - -The type must be a valid database name, in the form, SPContentDB01, or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: AllSitesInContentDB -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site subscription from which to get site collections. - -The type must be a valid URL, in the form, https://server_name or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: AllSitesInSiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. -This value sets the initial CompatibilityLevel value for the site collection. -The values for this parameter can be either SharePoint Server or SharePoint Server. -When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the web application depending on the SiteCreationMode setting. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -Specifies the script block of the server-side filter to apply. - -The type must be a valid filter name and value in the form {$_PropertyName \<operator\> "filterValue"}. - -Valid operators are: EQ, NE, LIKE, NOTLIKE. - -```yaml -Type: ScriptBlock -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit -Limits the maximum number of site collections to return. -The default value is 200. - -The type must be a valid non-negative number. -Specify ALL to return all site collections for the given scope. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Regex -When used, the URL provided for the Identity parameter is treated as a regular expression. - -```yaml -Type: SwitchParameter -Parameter Sets: AllSitesInIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the web application from which to list sites. - -The type must be a valid URL, in the form, https://server_name, a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh); or the name of the web application (for example, WebApplication1212). - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: AllSitesInWebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NeedsB2BUpgrade -Specifies whether the site needs to be upgraded. - -The valid values are True and False. - -```yaml -Type: SwitchParameter -Parameter Sets: AllSitesInContentDB -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteAdministration.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteAdministration.md deleted file mode 100644 index 3b5e3a5f6e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteAdministration.md +++ /dev/null @@ -1,315 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsiteadministration -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteAdministration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteAdministration - -## SYNOPSIS - -Returns a site administration object that allows farm administrators to view certain information about site collections to which they might not have access. - - - -## SYNTAX - -### AllSitesInIdentity -``` -Get-SPSiteAdministration [-Identity] <SPSiteAdministrationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Filter <ScriptBlock>] [-Limit <String>] [-Regex] - [-WhatIf] [<CommonParameters>] -``` - -### AllSitesInContentDB -``` -Get-SPSiteAdministration -ContentDatabase <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Filter <ScriptBlock>] [-Limit <String>] - [-WhatIf] [<CommonParameters>] -``` - -### AllSitesInSiteSubscription -``` -Get-SPSiteAdministration -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Filter <ScriptBlock>] [-Limit <String>] - [-WhatIf] [<CommonParameters>] -``` - -### AllSitesInWebApplication -``` -Get-SPSiteAdministration [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Filter <ScriptBlock>] - [-Limit <String>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPSiteAdminitration cmdlet returns a site administration object that allows farm administrators to view certain information about site collections to which they might not have access. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPSiteAdministration | Select -Property Url, OwnerLoginName, @{Name="Storage";Expression={$_.Quota.StorageMaximumLevel}} -``` - -This example gets a subset of data from all of the sites in the content database with the URL b399a366-d899-4cff-8a9b-8c0594ee755f (farm administrator does not require access). -This command uses the calculated property Storage to display the maximum storage value for the content database. - -### ------------------EXAMPLE 2------------------ -``` -Start-SPAssignment -Global -$s = Get-SPSiteAdministration -Identity https://MyApp/Sites/Site1 -$s.Url -Stop-SPAssignment -Global -``` - -This example gets the site collections specified by the Identity parameter and inserts the results into the variable s. -This example uses the Global method of garbage collection. -This method is easier to use but grows quickly. -Do not run a Get-SPSite command that returns many results while global assignment is on. - -### ------------------EXAMPLE 3------------------- -``` -C:\PS>$GC = Start-SPAssignment -$Sites = $GC | Get-SPSiteAdministration -Filter {$_.Owner -eq "DOMAIN\JDoe"} -Limit 50 -Stop-SPAssignment $GC -``` - -This example gets the first 50 sites owned by user DOMAIN\JDoe by using a server-side query, and assigns the returned sites to a local variable. -This command uses advanced assignment collection methods. - -### ------------------EXAMPLE 4------------------ -``` -Get-SPWebApplication https://sitename | Get-SPSiteAdministration -Limit All |ForEach-Object {$sum=0}{ $sum+=$_.DiskUsed }{$sum} -``` - -This command returns the sum of the disk space usage for all sites in the specified Web application. - -### ------------------EXAMPLE 5------------------ -``` -Get-SPWebApplication https://sitename | Get-SPSiteAdministration -Limit ALL | Select URL -``` - -This example gets the URLs for all site collections in a Web application. - -### ------------------EXAMPLE 6------------------ -``` -Get-SPSiteAdministration -identity "https://localserver/(my|personal)/sites" -Regex -``` - -This example returns all sites that match the given regular expression. -The quotation marks around the value specified for the Identity parameter are required when using the Regex flag. - -### ------------------EXAMPLE 7------------------ -``` -Get-SPSite "https://sitename/sites/teams/*" -Limit 100 -``` - -This example gets up to 100 of the sites under the URL https://sitename/sites/teams. - -## PARAMETERS - -### -Identity -Specifies the URL (full or partial) or GUID of the site collection to retrieve. - -The type must be a valid URL, in the form https://server_name, or a GUID, in the form 1234-456-987fg. - -```yaml -Type: SPSiteAdministrationPipeBind -Parameter Sets: AllSitesInIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the URL (full or partial) or GUID of the site collection to retrieve. - -The type must be a valid URL, in the form https://server_name, or a GUID, in the form, 1234-456-987fg. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: AllSitesInContentDB -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site group from which to get site collections. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; an SPSite (object or URL) of a site collection that is a member of the site subscription; or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: AllSitesInSiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -Specifies the script block of the server-side filter to apply. - -The type must be a valid filter name and a value in the form { $_ PropertyName \<operator \> "filterValue"}} - -```yaml -Type: ScriptBlock -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit -Limits the maximum number of site collections to return. -The default value is 200. - -The type must be a valid non-negative number. -Provide ALL to return all site collections for the given scope. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Regex -Enabling this switch causes the URL provided for the Identity parameter to be treated as a regular expression. - -```yaml -Type: SwitchParameter -Parameter Sets: AllSitesInIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the Web application from which to list sites. - -The type must be a valid URL, in the form https://server_name; a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh); or the Web application name (for example, WebApplication1212). - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: AllSitesInWebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteMapDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteMapDatabase.md deleted file mode 100644 index d090869830..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteMapDatabase.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitemapdatabase -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteMapDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteMapDatabase - -## SYNOPSIS -Do not use - -## SYNTAX - -``` -Get-SPSiteMapDatabase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Do not use - -## EXAMPLES - -### Example 1 -``` -Do not use -``` - -Do not use - -## PARAMETERS - -### -AssignmentCollection -Do not use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteMaster.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteMaster.md deleted file mode 100644 index fe79b3b249..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteMaster.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitemaster -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteMaster -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteMaster - -## SYNOPSIS -Returns site master information. - -## SYNTAX - -``` -Get-SPSiteMaster [-ContentDatabase] <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPSiteMaster cmdlet to display site master information in the farm. - -Typically the following information is displayed: - -* ContentDatabase - -* SiteId - -* TemplateName - -* Language - -* CompatibilityLevel - -* FeaturesToActivateOnCopy - -## EXAMPLES - -### Example 1 -``` -Get-SPSiteMaster -ContentDatabase WSS_Content -``` - -This example returns the site master in the database WSS_Content. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the name of the database to get the list of Site Masters. For example, WSS_Content. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPContentDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscription.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscription.md deleted file mode 100644 index 0767e8ffcf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscription.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitesubscription -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteSubscription -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteSubscription - -## SYNOPSIS - -Returns the site subscription for the given URL or all site subscriptions in the local farm. - - - -## SYNTAX - -``` -Get-SPSiteSubscription [[-Identity] <SPSiteSubscriptionPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPSiteSubscription cmdlet returns the site subscription for the given URL when the Identity parameter is used. -If no parameter is specified, all unique site subscriptions in the farm are listed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE---------------------- -``` -C:\PS>$SiteSub = Get-SPSiteSubscription https://Contoso.com - -C:\PS>$SiteSub = Get-SPSite https://contoso.com | Get-SPSiteSubscription -``` - -This example retrieves the site subscription for https://Contoso.com. - -## PARAMETERS - -### -Identity -Specifies the ID of the subscription. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionConfig.md deleted file mode 100644 index 698485e4e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionConfig.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitesubscriptionconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteSubscriptionConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteSubscriptionConfig - -## SYNOPSIS - -Returns the configuration properties of a site subscription. - - - -## SYNTAX - -``` -Get-SPSiteSubscriptionConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPSiteSubscriptionConfig cmdlet returns the configuration properties of a site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE--------------- -``` -Get-SPSiteSubscriptionConfig https://contoso.com | Select FeatureSet -``` - -This example gets the feature set ID for the site subscription that contains the Web site https://contoso.com. - -## PARAMETERS - -### -Identity -Specifies the site subscription configuration to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; an SPSite (object or URL) of a site collection that is a member of the site subscription; or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionEdiscoveryHub.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionEdiscoveryHub.md deleted file mode 100644 index 22e3a7b985..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionEdiscoveryHub.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitesubscriptionediscoveryhub -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteSubscriptionEdiscoveryHub -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteSubscriptionEdiscoveryHub - -## SYNOPSIS -Displays the eDiscovery hub for a site subscription. - -## SYNTAX - -``` -Get-SPSiteSubscriptionEdiscoveryHub [-Identity] <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPSiteSubscriptionEdiscoveryHub cmdlet to display the site collection configured as the eDiscovery hub for the specified site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE---------------------- -``` -Get-SPSiteSubscriptionEdiscoveryHub -Identity https://contoso.com -``` - -This example displays the eDiscovery hub for the specified site collection. - -## PARAMETERS - -### -Identity -Specifies the URL of the site collections to the eDiscovery hub. -Can pipe the result from the Get-SPSiteSubscription cmdlet. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionEdiscoverySearchScope.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionEdiscoverySearchScope.md deleted file mode 100644 index b0f1f21d19..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionEdiscoverySearchScope.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitesubscriptionediscoverysearchscope -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteSubscriptionEdiscoverySearchScope -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteSubscriptionEdiscoverySearchScope - -## SYNOPSIS -Displays the search scope for the eDiscovery hub of the specified site collection. - -## SYNTAX - -``` -Get-SPSiteSubscriptionEdiscoverySearchScope [-Identity] <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPSiteSubscriptionEdiscoverySearchScope cmdlet to retrieve the search scope that has been configured for the eDiscovery hub of the specified site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE-------------------- -``` -Get-SPSiteSubscriptionEdiscoverySearchScope -Identity https://contoso.com -``` - -This example displays the search scope for the eDiscovery hub for the specified site collection. - -## PARAMETERS - -### -Identity -Specifies the URL to the group of site collections that contained the search scope. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionFeaturePack.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionFeaturePack.md deleted file mode 100644 index 032217ddfc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionFeaturePack.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitesubscriptionfeaturepack -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteSubscriptionFeaturePack -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteSubscriptionFeaturePack - -## SYNOPSIS - -Retrieves available SharePoint Feature sets or the Feature set assigned to a given site subscription. - - - -## SYNTAX - -### FeaturePack -``` -Get-SPSiteSubscriptionFeaturePack [[-Identity] <SPSiteSubscriptionFeaturePackPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### SiteSubscription -``` -Get-SPSiteSubscriptionFeaturePack [-AssignmentCollection <SPAssignmentCollection>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPSiteSubscriptionFeaturePack cmdlet retrieves available SharePoint Feature sets or the Feature set assigned to a given site subscription. - -Be careful when you assign Feature sets to variables because changes to the Feature set are not reflected until the variable is refreshed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get- SPSiteSubscriptionFeaturePack -``` - -This example returns all defined Feature sets in the local farm. - -### ------------------EXAMPLE 2------------------ -``` -Get-SPSiteSubscriptionFeaturePack -SiteSubscription https://contoso.com | ForEach{ $_.FeatureDefinitions } -``` - -This example returns the list (name, ID, and scope) of all Features allowed in the Feature set that is currently assigned to the site subscription of https://contoso.com. - -## PARAMETERS - -### -Identity -Specifies a valid name or GUID of the Feature set. - -```yaml -Type: SPSiteSubscriptionFeaturePackPipeBind -Parameter Sets: FeaturePack -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -If provided, ensures that the returned Feature set is the Feature set that is currently assigned to the given site subscription. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionIRMConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionIRMConfig.md deleted file mode 100644 index 085caf16fb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionIRMConfig.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitesubscriptionirmconfig -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteSubscriptionIRMConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteSubscriptionIRMConfig - -## SYNOPSIS - -Gets the Information Rights Management (IRM) settings. - - - -## SYNTAX - -``` -Get-SPSiteSubscriptionIRMConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPSiteSubscriptionIRMConfig cmdlet to display IRM setting information for a specified tenant when the Identity parameter is used. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE----------- -``` -site = Get-SPSite https://myspserver - -C:\PS>$subscription = $site.SiteSubscription - -Get-SPSiteSubscriptionIRMConfig -Identity $subscription -``` - -This example gets the IRM settings for a specified tenant by using the Identity parameter. - -## PARAMETERS - -### -Identity -Specifies the site subscription for a particular tenant. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPSiteSubscriptionIRMConfig](Set-SPSiteSubscriptionIRMConfig.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionMetadataConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionMetadataConfig.md deleted file mode 100644 index aaa8a3ca84..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteSubscriptionMetadataConfig.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsitesubscriptionmetadataconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteSubscriptionMetadataConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteSubscriptionMetadataConfig - -## SYNOPSIS -Returns the site subscription configuration settings for a Metadata Service application. - -## SYNTAX - -``` -Get-SPSiteSubscriptionMetadataConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-ServiceProxy] <SPMetadataServiceProxyCmdletPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPSiteSubscriptionMetadataConfig cmdlet to read the site subscription configuration settings for a specified shared service application for the Metadata Service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -Get-SPSiteSubscriptionMetadataConfig -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -``` - -This example retrieves the site subscription-specific settings for an existing partitioned Metadata Service application. - -## PARAMETERS - -### -Identity -Specifies the site subscription to read. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscriptionConfig1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceProxy -Specifies the proxy of the metadata Service application for the site subscription. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of the service application proxy (for example, ServiceAppProxy1); or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteURL.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteURL.md deleted file mode 100644 index 4711a8b4c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteURL.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsiteurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteURL -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteURL - -## SYNOPSIS - -Displays all URL mappings for the site. - - - -## SYNTAX - -``` -Get-SPSiteURL [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPSiteUrl cmdlet to display all the URL mappings of the site by using the Identity parameter. - -The Get-SPSiteUrl cmdlet only applies to the root site collection for a host name, that is https://www.contoso.com. -This cmdlet cannot be directly run against a managed path site collection underneath the root, that is, https://www.contoso.com/sites/test. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE---------- -``` -C:\PS>$site = Get-SPSite 'https://www.contoso.com/' - -Get-SPSiteURL -Identity $site -``` - -This example displays all the URLs that bind to the site collection, https://www.contoso.com. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site collection to display. -Must be the root site collection of a host name. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPSiteUrl](Remove-SPSiteUrl.md) - -[Set-SPSiteUrl](Set-SPSiteUrl.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteUpgradeSessionInfo.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteUpgradeSessionInfo.md deleted file mode 100644 index 549173b6ad..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSiteUpgradeSessionInfo.md +++ /dev/null @@ -1,213 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsiteupgradesessioninfo -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSiteUpgradeSessionInfo -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSiteUpgradeSessionInfo - -## SYNOPSIS - -Manage or report site upgrade. - - - -## SYNTAX - -### ContentDB -``` -Get-SPSiteUpgradeSessionInfo -ContentDatabase <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-HideWaiting] [-ShowCompleted] [-ShowFailed] - [-ShowInProgress] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -### Site -``` -Get-SPSiteUpgradeSessionInfo -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Get-SPSiteUpgradeSessionInfo cmdlet to manage or report site upgrade of the farm. - -This cmdlet has two modes, get upgrade information for a specific SPSite object or for a given content database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE 1---------- -``` -C:\PS>$db = Get-SPContentDatabase -Identity wss_content - -Get-SPSiteUpgradeSessionInfo -ContentDatabase $db -``` - -This example returns siteupgradeinfo for every SPContentDatabase returned from Get-SPContentDatabase cmdlet. - -### -----------EXAMPLE 2---------- -``` -C:\PS>$site=Get-SPSite -Identity https://localhost - -Get-SPSiteUpgradeSessionInfo -Site $site -``` - -This example returns siteupgradeinfo for every SPSite object returned from Get-SPSite cmdlet. - -## PARAMETERS - -### -ContentDatabase -Specifies the GUID of the content database from which to list site collections.The type must be a valid database name, in the form SPContentDB01, or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: ContentDB -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -```yaml -Type: SPSitePipeBind -Parameter Sets: Site -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -HideWaiting -Specifies to hide site collections that upgrade has not started. - -```yaml -Type: SwitchParameter -Parameter Sets: ContentDB -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowCompleted -Specifies to show site collections that has completed upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: ContentDB -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowFailed -Specifies to show site collections that have failed upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: ContentDB -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowInProgress -Displays site collections that are in the process of being upgraded. - -```yaml -Type: SwitchParameter -Parameter Sets: ContentDB -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies to limit the result to site collections within the site subscription. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: ContentDB -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPSiteUpgradeSessionInfo](Remove-SPSiteUpgradeSessionInfo.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSolution.md deleted file mode 100644 index 77f05023b8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPSolution.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spsolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPSolution - -## SYNOPSIS - -Returns a specified SharePoint solution. - - - -## SYNTAX - -``` -Get-SPSolution [[-Identity] <SPSolutionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPSolution cmdlet returns a specified SharePoint solution. -If the Identity parameter is not specified, this cmdlet returns the collection of all installed SharePoint solutions in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPSolution -``` - -This example returns the collection of all installed SharePoint solutions in the farm. - -## PARAMETERS - -### -Identity -Specifies the SharePoint solution to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint solution (for example, SPSolution1); or an instance of a valid SPSolution object. - -```yaml -Type: SPSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceApplication.md deleted file mode 100644 index 84be05fbc5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceApplication.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spstateserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPStateServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPStateServiceApplication - -## SYNOPSIS -Returns state service applications on the farm. - -## SYNTAX - -``` -Get-SPStateServiceApplication [[-Identity] <SPStateServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPStateServiceApplication cmdlet returns a state service application on the farm. -If the Identity parameter is not specified, this cmdlet returns the collection of all state service applications on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPStateServiceApplication -``` - -This example displays all state service applications in the farm. - -### --------------EXAMPLE 2----------------- -``` -Get-SPStateServiceApplication -Identity "StateServiceApp1" -``` - -This example displays a specific state service application in the farm. - -## PARAMETERS - -### -Identity -Specifies the state service application to get. - -The type must be a valid name of a state service application (for example, StateServiceApp1) or a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPStateServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceApplicationProxy.md deleted file mode 100644 index 56ca4afa8c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceApplicationProxy.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spstateserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPStateServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPStateServiceApplicationProxy - -## SYNOPSIS -Returns state service application proxies on the farm. - -## SYNTAX - -``` -Get-SPStateServiceApplicationProxy [[-Identity] <SPStateServiceApplicationProxyPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPStateServiceApplicationProxy cmdlet returns a state service application proxy on the farm. -If the Identity parameter is not specified, this cmdlet returns the collection of all state service application proxies on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPStateServiceApplicationProxy -``` - -This example displays all the state service application proxies on the farm. - -### --------------EXAMPLE 2----------------- -``` -Get-SPStateServiceApplicationProxy -Identity 81dc50e0-c0f9-4d2c-8284-bb03bb1ea676 -``` - -This example displays a specific state service application proxy on the farm. - -## PARAMETERS - -### -Identity -Specifies the state service application proxy to get. - -The type must be a valid name of a state service application proxy (for example, StateServiceProxy); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPStateServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceDatabase.md deleted file mode 100644 index 1d7b272151..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPStateServiceDatabase.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPStateServiceDatabase - -## SYNOPSIS -Returns a state service database. - -## SYNTAX - -### Default -``` -Get-SPStateServiceDatabase [[-Identity] <SPStateDatabasePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### ServiceApplication -``` -Get-SPStateServiceDatabase [[-ServiceApplication] <SPStateServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPStateServiceDatabase cmdlet returns a state service database on the farm. -If the Identity parameter is not specified, this cmdlet returns the collection of all state service databases on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1---------------- -``` -Get-SPStateServiceDatabase -``` - -This example displays all of the state service databases on the farm. - -### --------------EXAMPLE 2-------------- -``` -Get-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -``` - -This example displays a specific state service database in the farm. - -### --------------EXAMPLE 3-------------- -``` -Get-SPStateServiceDatabase -ServiceApplication "StateServiceApp1" -``` - -This example displays all state service databases associated with a specific service. - -## PARAMETERS - -### -Identity -Specifies the state service database to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh or an instance of a valid SPStateServiceDatabase object (for example, StateSvcDB1). - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: Default -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplication -Filters to return only the state service database associated with the specified state service application. - -The type must be a valid name of a state service application (for example, StateServiceApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPStateServiceApplication object. - -```yaml -Type: SPStateServiceApplicationPipeBind -Parameter Sets: ServiceApplication -Aliases: Application -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTaxonomySession.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTaxonomySession.md deleted file mode 100644 index b667e08b37..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTaxonomySession.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptaxonomysession -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTaxonomySession -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTaxonomySession - -## SYNOPSIS -Returns a TaxonomySession object. - -## SYNTAX - -``` -Get-SPTaxonomySession -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPTaxonomySession cmdlet to get a TaxonomySession object. -A TaxonomySession object contains the set of metadata term stores for a taxonomy session. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE-------------------- -``` -C:\PS>$session = Get-SPTaxonomySession -Site "https://sitename/" -``` - -This example retrieves a TaxonomySession object, which can be used to access term stores associated with the Web application for a site. - -## PARAMETERS - -### -Site -Specifies the SharePoint site mapped to the set of metadata term stores for the taxonomy session. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPThrottlingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPThrottlingRule.md deleted file mode 100644 index 471ff801c8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPThrottlingRule.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spthrottlingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPThrottlingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPThrottlingRule - -## SYNOPSIS - -Returns all throttling rules. - - - -## SYNTAX - -``` -Get-SPThrottlingRule [-RequestManagementSettings] <SPRequestManagementSettingsPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPThrottlingRule cmdlet to return all the throttling rules from the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE-------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -Get-SPThrottlingRule -RequestManagementSettings $rm -``` - -This example returns throttling rules for the farm by using the $rm and $web variables. - -## PARAMETERS - -### -RequestManagementSettings -Specifies the name of the request management settings object to return. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the throttling rule to return. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPThrottlingRule](Add-SPThrottlingRule.md) - -[Remove-SPThrottlingRule](Remove-SPThrottlingRule.md) - -[Set-SPThrottlingRule](Set-SPThrottlingRule.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTimerJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTimerJob.md deleted file mode 100644 index 9a4181c7d4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTimerJob.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptimerjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTimerJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTimerJob - -## SYNOPSIS - -Returns timer jobs. - -## SYNTAX - -``` -Get-SPTimerJob [[-Identity] <SPTimerJobPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Type <String>] [-WebApplication <SPWebApplicationPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPTimerJob cmdlet reads a specified timer job, timer jobs of a specified type, or timer jobs defined for a specified scope. - -If no parameters are specified, this cmdlet returns all timer job definitions for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES -### ---------------------EXAMPLE 01--------------------- -``` -Get-SPTimerJob -WebApplication "https://servername/" | select Name, DisplayName -``` - -This example displays all timer jobs for a specified Web application. - -### ---------------------EXAMPLE 02--------------------- -```powershell -Get-SPTimerJob | select -ExpandProperty HistoryEntries -``` -The above example will show you timer job run history - -## PARAMETERS - -### -Identity -Specifies the timer job to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a timer job (for example, TimerJob1); or an instance of a valid SPTimerJob object. - -```yaml -Type: SPTimerJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Type -Filters to return timer jobs of a specified type. - -The type must be a name of a valid timer job type; for example, TimerJob1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Filters to return timer jobs defined for the scope of a specified SharePoint Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTopologyServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTopologyServiceApplication.md deleted file mode 100644 index bffdfc5938..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTopologyServiceApplication.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.TopologyService-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptopologyserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTopologyServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTopologyServiceApplication - -## SYNOPSIS - -Displays properties of the topology service application for the current farm. - - - -## SYNTAX - -``` -Get-SPTopologyServiceApplication [[-Identity] <SPTopologyWebServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPTopologyServiceApplication cmdlet displays the advanced properties of an application when the Identity parameter is used. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPTopologyServiceApplication -``` - -This example displays properties of the topology service application for the current farm. - -## PARAMETERS - -### -Identity -Specifies the GUID of the application. - -The type must be a valid GUID, in the form 1234-4567-098jhj. - -```yaml -Type: SPTopologyWebServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTopologyServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTopologyServiceApplicationProxy.md deleted file mode 100644 index fc6d9e91e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTopologyServiceApplicationProxy.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.TopologyService-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptopologyserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTopologyServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTopologyServiceApplicationProxy - -## SYNOPSIS - -Retrieves the topology service application proxy. - - - -## SYNTAX - -``` -Get-SPTopologyServiceApplicationProxy [[-Identity] <SPTopologyWebServiceProxyPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPTopologyServiceApplicationProxy cmdlet retrieves the local topology service application proxy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPTopologyServiceApplicationProxy -``` - -This example displays the topology service application proxy in the farm. - -## PARAMETERS - -### -Identity -Specifies the GUID of the application proxy. - -The type must be a valid GUID, in the form 1234-4567-098jhj. - -```yaml -Type: SPTopologyWebServiceProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTranslationThrottlingSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTranslationThrottlingSetting.md deleted file mode 100644 index ff2c740826..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTranslationThrottlingSetting.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Translation.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptranslationthrottlingsetting -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTranslationThrottlingSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTranslationThrottlingSetting - -## SYNOPSIS -Gets time duration settings. - -## SYNTAX - -``` -Get-SPTranslationThrottlingSetting [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Farm <SPFarm>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPTranslationThrottlingSetting cmdlet to display the time duration for timer jobs. - -## EXAMPLES - -### Example 1 -``` -Get-SPTranslationThrottlingSetting -``` - -This example displays all the time duration and timer jobs for the farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE:** When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -``yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Farm -Specifies the farm - -```yaml -Type: SPFarm -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedIdentityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedIdentityTokenIssuer.md deleted file mode 100644 index 5fdba9330e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedIdentityTokenIssuer.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptrustedidentitytokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTrustedIdentityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTrustedIdentityTokenIssuer - -## SYNOPSIS - -Returns an identity provider. - - - -## SYNTAX - -``` -Get-SPTrustedIdentityTokenIssuer [[-Identity] <SPTrustedIdentityTokenIssuerPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPTrustedIdentityTokenIssuer cmdlet returns an identity provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------------EXAMPLE 1------------------------ -``` -C:\PS>$trustedsts = Get-SPTrustedIdentityTokenIssuer "LiveIDSTS" -``` - -This example gets a trusted identity token issuer. - -## PARAMETERS - -### -Identity -Specifies the identity provider to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of identity provider (for example, LiveID STS); or an instance of a valid SPIdentityProvider object. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedRootAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedRootAuthority.md deleted file mode 100644 index a327d95749..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedRootAuthority.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptrustedrootauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTrustedRootAuthority -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTrustedRootAuthority - -## SYNOPSIS - -Returns a trusted root authority. - - - -## SYNTAX - -``` -Get-SPTrustedRootAuthority [[-Identity] <SPTrustedRootAuthorityPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPTrustedRootAuthority cmdlet returns a trusted root authority. -If a certificate file is used, it must have only one X509 certificate without private keys, otherwise an exception is raised. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$rootauthority=Get-SPTrustedRootAuthority -Identity "WFEFarm1" -``` - -This example creates a new trusted root authority, WFEFarm1. - -## PARAMETERS - -### -Identity -Specifies the trusted root authority to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a trusted root authority (for example, WFEFarm1); or an instance of a valid SPTrustedRootAuthority object. - -```yaml -Type: SPTrustedRootAuthorityPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedSecurityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedSecurityTokenIssuer.md deleted file mode 100644 index d3b7aa6f64..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedSecurityTokenIssuer.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptrustedsecuritytokenissuer -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTrustedSecurityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTrustedSecurityTokenIssuer - -## SYNOPSIS - -Returns the trusted security token issuer object. - - - -## SYNTAX - -``` -Get-SPTrustedSecurityTokenIssuer [[-Identity] <SPTrustedSecurityTokenServicePipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPTrustedSecurityTokenService cmdlet to return the trusted security token issuer by using the Identity parameter. -This cmdlet returns the T:Microsoft.SharePoint.Administration.Claims.SPSecurityTokenServiceManager object. -The properties on this object can be set by using the Set-SPTrustedSecurityTokenIssuer cmdlet and then updated back to the object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE---------- -``` -Get-SPTrustedSecurityTokenService -``` - -This example displays all trusted security token service objects from the farm. - -## PARAMETERS - -### -Identity -Specifies the ID of the trusted security token issuer object that you want to return. -If you do not specify this parameter, the cmdlet returns all the objects. - -```yaml -Type: SPTrustedSecurityTokenServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPTrustedSecurityTokenIssuer](New-SPTrustedSecurityTokenIssuer.md) - -[Remove-SPTrustedSecurityTokenIssuer](Remove-SPTrustedSecurityTokenIssuer.md) - -[Set-SPTrustedSecurityTokenIssuer](Set-SPTrustedSecurityTokenIssuer.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedServiceTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedServiceTokenIssuer.md deleted file mode 100644 index c12f8499f6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPTrustedServiceTokenIssuer.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-sptrustedservicetokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPTrustedServiceTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPTrustedServiceTokenIssuer - -## SYNOPSIS - -Returns the object that represents the farm trust. - - - -## SYNTAX - -``` -Get-SPTrustedServiceTokenIssuer [[-Identity] <SPTrustedServiceTokenIssuerPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPTrustedServiceTokenIssuer cmdlet returns the object that represents the farm trust. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPTrustedServiceTokenIssuer "WFEFarm1" -``` - -This example gets the trusted services token issuer WFEFarm1. - -## PARAMETERS - -### -Identity -Specifies the trusted service token issuer to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a trusted service token issuer (for example, WFEFarm1); or an instance of a valid SPTrustedRootAuthority object. - -```yaml -Type: SPTrustedServiceTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUpgradeActions.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUpgradeActions.md deleted file mode 100644 index 6d63378db5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUpgradeActions.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spupgradeactions -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUpgradeActions -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUpgradeActions - -## SYNOPSIS - -Returns all upgrade actions. - - - -## SYNTAX - -``` -Get-SPUpgradeActions [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPUpgradeActions cmdlet to return all upgrade actions (that is, detail on the action name, type, target object type, schema version, and compatibility level) within the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE------------ -``` -Get-SPUpgradeActions -``` - -This example returns all upgrade actions within the farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageApplication.md deleted file mode 100644 index eed68f359d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageApplication.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spusageapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUsageApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUsageApplication - -## SYNOPSIS - -Returns a specified usage application. - - - -## SYNTAX - -``` -Get-SPUsageApplication [[-Identity] <SPUsageApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-UsageService <SPUsageServicePipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUsageApplication cmdlet return a specified usage application. -If the Identity parameter is not specified, the cmdlet returns the local usage application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE------------------ -``` -Get-SPUsageApplication -Identity "Usage and Health data collection" -``` - -This example returns the usage application named, Usage and Health data collection - -## PARAMETERS - -### -Identity -Specifies the usage application to get. -If the Identity parameter is not specified, the cmdlet returns the local usage application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage application (for example, UsageApplication1); or an instance of a valid SPUsageApplication object. - -```yaml -Type: SPUsageApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -UsageService -Filters to return the usage application with the specified parent SPUsageService object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage service (for example, UsageService1); or an instance of a valid SPUsageService object. - -```yaml -Type: SPUsageServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageDefinition.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageDefinition.md deleted file mode 100644 index 61511b69eb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageDefinition.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spusagedefinition -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUsageDefinition -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUsageDefinition - -## SYNOPSIS - -Returns a usage definition object. - - - -## SYNTAX - -``` -Get-SPUsageDefinition [[-Identity] <SPUsageDefinitionPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUsageDefinition cmdlet reads a usage definition object. -If the Identity parameter is not specified, this cmdlet returns the collection of usage definitions in the farm. -A usage definition object defines a specific type of usage. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE----------------- -``` -Get-SPUsageDefinition -Identity "Page Requests" -``` - -This example returns the SPRequestUsage provider on the local farm. - -## PARAMETERS - -### -Identity -Specifies the usage definition object to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage definition (for example, SiteSubscriptionConfig1); or an instance of a valid SPUsageDefinition object. - -```yaml -Type: SPUsageDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageService.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageService.md deleted file mode 100644 index 1b9de2d352..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUsageService.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spusageservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUsageService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUsageService - -## SYNOPSIS - -Returns a usage service. - - - -## SYNTAX - -``` -Get-SPUsageService [[-Identity] <SPUsageServicePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUsageService cmdlet returns the specified usage service. -If the Identity parameter is not specified, the cmdlet returns the local usage service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE------------------------- -``` -Get-SPUsageService -Identity 57055d99-9914-4af6-a3bf-7b76e3f231c2 -``` - -This example returns a SPUsageService object of the specified ID. - -## PARAMETERS - -### -Identity -Specifies the usage service to get. -If the Identity parameter is not specified, the cmdlet returns the local usage service. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage service (for example, UsageService1); or an instance of a valid SPUsageService object. - -```yaml -Type: SPUsageServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUser.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUser.md deleted file mode 100644 index d7c9d05c64..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUser.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spuser -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUser -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUser - -## SYNOPSIS - -Returns the user account or accounts that match a given search criteria. - - - -## SYNTAX - -``` -Get-SPUser [[-Identity] <SPUserPipeBind>] -Web <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Group <SPGroupPipeBind>] [-Limit <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUser cmdlet returns all SharePoint user accounts that match the scope given by the Identity, Web, or Group parameters. - -The Identity parameter can use the alias of a user for returning exact matches. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPUser -Web 'https://sharepoint.contoso.com/' -Group 'Viewers' -``` - -This example returns all members of the SharePoint group Viewers on the site https://sharepoint.contoso.com. - - -### ------------------EXAMPLE 2------------------ -``` -Get-SPUser -Identity 'i:0#.w|contoso\jdoe' -Web 'https://sharepoint.contoso.com/' -``` - -This example returns the specific user identified via Windows Claims on the site https://sharepoint.contoso.com. - -### ------------------EXAMPLE 3------------------ -``` -Get-SPUser -Identity 'contoso\jdoe' -Web 'https://sharepoint.contoso.com/' -``` - -This example returns the specific user identified via Classic Windows authentication on the site https://sharepoint.contoso.com. - -## PARAMETERS - -### -Identity -Specifies the ID or login name of the user to be returned. - -The type must be a valid ID or login name, such as the format of 'CONTOSO\jdoe' for Classic Windows Authentication or 'i:0#.w|CONTOSO\jdoe' for Windows Claims. - -```yaml -Type: SPUserPipeBind -Parameter Sets: (All) -Aliases: UserAlias -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Web -Specifies the Web site to be used as a scope. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint Foundation Web site (for example, MySPSite1); or an instance of a valid SPWeb object. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Group -Specifies the user group to which the new user belongs. - -```yaml -Type: SPGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit -Specifies the maximum number of users to return. -The default value is 500. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicense.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicense.md deleted file mode 100644 index ca6adfdd5b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicense.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spuserlicense -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUserLicense -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUserLicense - -## SYNOPSIS - -Returns the list of supported SharePoint user licenses. - - - -## SYNTAX - -``` -Get-SPUserLicense [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUserLicense cmdlet returns the list of supported SharePoint user licenses in the SharePoint farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE------------------- -``` -Get-SPUserLicense -``` - -This example returns the list of supported SharePoint user licenses for the SharePoint farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicenseMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicenseMapping.md deleted file mode 100644 index 8254aefdc7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicenseMapping.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spuserlicensemapping -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUserLicenseMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUserLicenseMapping - -## SYNOPSIS - -Returns the claim-to-user license mappings. - - - -## SYNTAX - -``` -Get-SPUserLicenseMapping [-AssignmentCollection <SPAssignmentCollection>] - [-WebApplication <SPWebApplicationPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUserLicenseMapping cmdlet returns the claim-to-user license mappings for the entire SharePoint farm or a specific web application. - -Getting the mappings for the entire farm does not retrieve any specific mappings on a web application. - -If you specify no parameters, the license mappings for the entire farm are returned. -To display the license mappings for a specific web application, use the WebApplication parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- -``` -Get-SPUserLicenseMapping -``` - -This example returns all claim-to-user license mappings for the entire SharePoint farm. - -### ---------------EXAMPLE 2 ----------------- -``` -Get-SPUserLicenseMapping -WebApplication "SharePoint - 80" -``` - -This example returns all claim-to-user license mappings for the web application with the name "SharePoint - 80". - -### ---------------EXAMPLE 3 ----------------- -``` -Get-SPUserLicenseMapping -WebApplication https://<server_name>/sitename -``` - -This example returns all claim-to-user license mappings for the Web application with the URL https://\<server_name\>/sites/sitename. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, web application name, or instance of a web application object from which to get the user license mappings. -The type must be an URL in the form https://server_name or https://server_name/sites/sitename, a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh), a web application name (that is, SharePoint - 80), or an instance of a web application object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPUserLicenseMapping](Add-SPUserLicenseMapping.md) - -[Remove-SPUserLicenseMapping](Remove-SPUserLicenseMapping.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicensing.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicensing.md deleted file mode 100644 index ae1fec683c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserLicensing.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spuserlicensing -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUserLicensing -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUserLicensing - -## SYNOPSIS - -Returns the state of user-license enforcement. - - - -## SYNTAX - -``` -Get-SPUserLicensing [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUserLicensing cmdlet returns the state of user-license enforcement for an entire SharePoint farm. - -If user-license enforcement is enabled on a SharePoint farm, the return value is true. -Otherwise the value is false. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE------------- -``` -Get-SPUserLicensing -``` - -This example returns the state of user-license enforcement on the SharePoint farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Disable-SPUserLicensing](Disable-SPUserLicensing.md) - -[Enable-SPUserLicensing](Enable-SPUserLicensing.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSettingsProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSettingsProvider.md deleted file mode 100644 index e567f0abc3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSettingsProvider.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spusersettingsprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUserSettingsProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUserSettingsProvider - -## SYNOPSIS - -Returns a list of User Settings Providers installed on the farm. - - - -## SYNTAX - -``` -Get-SPUserSettingsProvider [[-Identity] <SPUserSettingsProviderPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPUserSettingsProvider cmdlet to return a list of User Settings Providers. -To return a list of a specific user setting provider, use the Identity parameter. -Otherwise, the list for the entire farm is returned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE-------- -``` -C:\PS>$provider = Get-SPUserSettingsProvider - -C:\PS>$site = Get-SPSite -Identity https://someserver - -C:\PS>$user = $site.RootWeb.CurrentUser - -C:\PS>$ctx = $provider.GetProviderContext($user) - -C:\PS>$provider.GetUserRegionalSettings($ctx,$user) -``` - -This example returns the regional settings for a specified user. - -## PARAMETERS - -### -Identity -Specifies the GUID ID for a User Settings Provider. - -```yaml -Type: SPUserSettingsProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPUserSettingsProvider](New-SPUserSettingsProvider.md) - -[Remove-SPUserSettingsProvider](Remove-SPUserSettingsProvider.md) - -[Get-SPUserSettingsProviderManager](Get-SPUserSettingsProviderManager.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSettingsProviderManager.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSettingsProviderManager.md deleted file mode 100644 index 146e216268..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSettingsProviderManager.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spusersettingsprovidermanager -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUserSettingsProviderManager -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUserSettingsProviderManager - -## SYNOPSIS - -Returns the User Settings Provider Manager. - - - -## SYNTAX - -``` -Get-SPUserSettingsProviderManager [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPUserSettingsProviderManager cmdlet to return the User Settings Provider Manager for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE-------- -``` -Get-SPUserSettingsProviderManager -``` - -This example returns the User Settings Provider Manager for the farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPUserSettingsProvider](Get-SPUserSettingsProvider.md) - -[New-SPUserSettingsProvider](New-SPUserSettingsProvider.md) - -[Remove-SPUserSettingsProvider](Remove-SPUserSettingsProvider.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSolution.md deleted file mode 100644 index 4fa1142b29..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSolution.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spusersolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUserSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUserSolution - -## SYNOPSIS - -Returns a specified sandboxed solution. - - - -## SYNTAX - -``` -Get-SPUserSolution [[-Identity] <SPUserSolutionPipeBind>] -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPUserSolution cmdlet returns a specified sandboxed solution. -If the Identity parameter is not specified, this cmdlet returns the collection of sandboxed solutions in the site collection. -A user solution is a sandboxed solution. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE--------------------- -``` -Get-SPUserSolution -Site https://sitename -``` - -This example displays information about sandboxed solutions in the site https://sitename. - -## PARAMETERS - -### -Identity -Specifies the sandboxed solution to get. - -The type must be a valid name of a user solution (for example, UserSolution1); or an instance of a valid SPUserSolution object. - -```yaml -Type: SPUserSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Specifies the site collection that contains the sandboxed solution. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSolutionAllowList.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSolutionAllowList.md deleted file mode 100644 index fd26c45dd5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPUserSolutionAllowList.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spusersolutionallowlist -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPUserSolutionAllowList -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPUserSolutionAllowList - -## SYNOPSIS -Gets the user managed solutions gallery configured on the specified web application. - -## SYNTAX - -``` -Get-SPUserSolutionAllowList [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -WebApplication <SPWebApplicationPipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Gets the user managed solutions gallery configured on the specified web application. - -## EXAMPLES - -### Example 1 -``` -Get-SPUserSolutionAllowList -WebApplication https://webAppUrl -``` -This example gets the user managed solutions gallery on the web application with root https://webAppUrl. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the web application to search for the user solution allow list. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioExternalData.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioExternalData.md deleted file mode 100644 index 83b79b16e9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioExternalData.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spvisioexternaldata -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPVisioExternalData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPVisioExternalData - -## SYNOPSIS -Returns the settings for external data connections for a Visio Services application. - -## SYNTAX - -``` -Get-SPVisioExternalData -VisioServiceApplication <SPVisioServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPVisioExternalData cmdlet reads the service settings for managing settings that are related to connecting to external data. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------------ -``` -Get-SPVisioExternalData -VisioServiceApplication "VGS1" -``` - -This example gets settings related to external data for a Visio Services application. - -### ------------------EXAMPLE 2------------------------ -``` -Get-SPVisioServiceApplication -identity "VGS1" | Get-SPVisioExternalData -``` - -This example uses a pipe bind to get settings related to external data for a Visio Services application. - -## PARAMETERS - -### -VisioServiceApplication -Specifies the Visio Services application that contains the SPVisioExternalData object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioPerformance.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioPerformance.md deleted file mode 100644 index 80c9c79abf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioPerformance.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spvisioperformance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPVisioPerformance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPVisioPerformance - -## SYNOPSIS -Returns the Visio Services settings for the performance of a Visio Services application. - -## SYNTAX - -``` -Get-SPVisioPerformance -VisioServiceApplication <SPVisioServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPVisioPerformance cmdlet reads the service settings for managing and configuring peformance for a Visio Services application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE---------------------- -``` -Get-SPVisioPerformance -VisioServiceApplication "VGS1" -``` - -This example gets settings related to performance for a Visio Services application. - -## PARAMETERS - -### -VisioServiceApplication -Specifies the Visio Services application that contains the SPVisioPerformance object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioSafeDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioSafeDataProvider.md deleted file mode 100644 index c56ea5c6f6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioSafeDataProvider.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spvisiosafedataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPVisioSafeDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPVisioSafeDataProvider - -## SYNOPSIS -Returns the settings of a safe data provider for a Visio Services application. - -## SYNTAX - -``` -Get-SPVisioSafeDataProvider -VisioServiceApplication <SPVisioServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-DataProviderId <String>] [-DataProviderType <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPVisioSafeDataProvider cmdlet retrieves the settings of the safe provider for a Visio Services application. -If the DataProviderID parameter is not specified, this cmdlet returns the collection of safe providers in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE 1---------------------- -``` -Get-SPVisioSafeDataProvider -VisioServiceApplication "VGS1" -``` - -This example returns a list of safe data providers for a specific Visio Services application. - -### -------------------EXAMPLE 2---------------------- -``` -Get-SPVisioSafeDataProvider -VisioServiceApplication "VGS1" -DataProviderID "SQLOLEDB" -DataProviderType 1 -``` - -This example returns information about a specified safe data provider for a specific Visio Services application. - -## PARAMETERS - -### -VisioServiceApplication -Specifies the Visio Services application that contains the SPVisioSafeDataProvider object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DataProviderId -Specifies the safe data provider to get. -The combination of DataProviderID and DataProviderType uniquely identify a data provider for a Visio Graphics Service application. -The string that identifies the data provider can be a maximum of 255 alphanumeric characters. - -The type must be a valid string that identifies the data provider; for example, VisioDataProvider1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataProviderType -Specifies the supported type of the data provider to get. -Custom data types are supported; for example, Excel services. - -The type must be a valid identity of a data provider type. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioServiceApplication.md deleted file mode 100644 index 966a7d4402..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioServiceApplication.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spvisioserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPVisioServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPVisioServiceApplication - -## SYNOPSIS -Returns properties of a Visio Services application or a collection of Visio Services applications. - -## SYNTAX - -``` -Get-SPVisioServiceApplication [[-Identity] <SPVisioServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPVisioServiceApplication cmdlet retrieves the settings of the specified Visio Services application. -If the Identity parameter is not specified, this cmdlet returns the collection of Visio Services applications in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------------EXAMPLE 1------------------------- -``` -Get-SPVisioServiceApplication -``` - -This example returns a collection of all Visio Services applications in the farm. - -### -----------------------EXAMPLE 2------------------------- -``` -Get-SPVisioServiceApplication "VGS1" -``` - -This example returns properties of the VGS1 Visio Services application. - -## PARAMETERS - -### -Identity -Specifies the Visio Services application to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioServiceApplicationProxy.md deleted file mode 100644 index e401b128d4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPVisioServiceApplicationProxy.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spvisioserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPVisioServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPVisioServiceApplicationProxy - -## SYNOPSIS -Returns properties of a Visio Services application proxy or a collection of Visio Services application proxies. - -## SYNTAX - -``` -Get-SPVisioServiceApplicationProxy [[-Identity] <SPVisioServiceApplicationProxyPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPVisioServiceApplicationProxy cmdlet reads the settings of a Visio Services application proxy. -If the Identity parameter is not specified, this cmdlet returns the collection of Visio Services application proxies on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE 1--------------------- -``` -Get-SPVisioServiceApplicationProxy -``` - -This example returns a list of Visio Services application proxies. - -### ----------------EXAMPLE 2--------------------- -``` -Get-SPVisioServiceApplicationProxy "Connection to VGS2" -``` - -This example returns settings for a Visio Services application proxy. - -## PARAMETERS - -### -Identity -Specifies the Visio Services application proxy to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPIBinding.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPIBinding.md deleted file mode 100644 index 523feada12..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPIBinding.md +++ /dev/null @@ -1,190 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwopibinding -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWOPIBinding -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWOPIBinding - -## SYNOPSIS - -Returns a list of bindings that were created by using New-SPWOPIBinding on the current SharePoint farm where this cmdlet is run. - - - -## SYNTAX - -``` -Get-SPWOPIBinding [-Action <String>] [-Application <String>] [-AssignmentCollection <SPAssignmentCollection>] - [-Extension <String>] [-ProgId <String>] [-Server <String>] [-WOPIZone <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWOPIBinding returns a list of bindings that were created by using New-SPWOPIBinding on the current SharePoint farm where this cmdlet is run. -Results include actions, applications, file types and zones that are configured for a WOPI application (such as a server that runs Office Web Apps Server). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Get-SPWOPIBinding -Server "Server.corp.Contoso.com" -``` - -This example returns a list of bindings that were created on the current SharePoint farm where this cmdlet is run for the WOPI application "Server.corp.Contoso.com." The WOPI application may be the server that runs Office Web Apps Server. - -### --------------EXAMPLE 2----------------- -``` -Get-SPWOPIZone | Get-SPWOPIBinding -``` - -This example returns a list of bindings that were created on the current SharePoint farm where this cmdlet is run for the zone configured for the WOPI application. - -## PARAMETERS - -### -Action -Specifies the action to return bindings for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Application -Specifies the application to return bindings for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Extension -Specifies the file name extension to return bindings for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProgId -Specifies the programmatic identifier (ProgID) for an application to return bindings for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Server -Specifies the name of WOPI application (such as a server that runs Office Web Apps Server) to return bindings for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WOPIZone -Specifies the zone to return bindings for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[New-SPWOPIBinding](New-SPWOPIBinding.md) - -[Set-SPWOPIBinding](Set-SPWOPIBinding.md) - -[Remove-SPWOPIBinding](Remove-SPWOPIBinding.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPISuppressionSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPISuppressionSetting.md deleted file mode 100644 index d77089a6d4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPISuppressionSetting.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwopisuppressionsetting -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWOPISuppressionSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWOPISuppressionSetting - -## SYNOPSIS - -Returns the suppression settings on the current SharePoint farm where this cmdlet is run. - - - -## SYNTAX - -``` -Get-SPWOPISuppressionSetting [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWOPISuppressionSetting cmdlet returns the suppression settings on the current SharePoint farm where this cmdlet is run. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPWOPISuppressionSetting -``` - -This example returns all the suppression settings on the current SharePoint farm where this cmdlet is run. -The suppression settings returned include the DocType and WOPIAction. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[New-SPWOPISuppressionSetting](New-SPWOPISuppressionSetting.md) - -[Remove-SPWOPISuppressionSetting](Remove-SPWOPISuppressionSetting.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPIZone.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPIZone.md deleted file mode 100644 index a23bef0a3f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWOPIZone.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwopizone -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWOPIZone -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWOPIZone - -## SYNOPSIS - -Returns the zone that is configured on the current SharePoint farm for the WOPI application to use. - - - -## SYNTAX - -``` -Get-SPWOPIZone [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWOPIZone returns the zone that is configured on the current SharePoint farm for the WOPI application (such as a server that runs Office Web Apps Server) to use. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPWOPIZone -``` - -This example returns the zone that is configured for the WOPI application (such as a server that runs Office Web Apps Server) to use. -Return values may be "internal-http," "internal-https," "external-http" or "external-https." - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[Set-SPWOPIZone](Set-SPWOPIZone.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWeb.md deleted file mode 100644 index ccd363643b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWeb.md +++ /dev/null @@ -1,238 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spweb -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWeb - -## SYNOPSIS - -Returns all subsites that match the given criteria. - - - -## SYNTAX - -``` -Get-SPWeb [[-Identity] <SPWebPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Filter <ScriptBlock>] [-Limit <String>] [-Regex] [-Site <SPSitePipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWeb cmdlet returns all subsites that match the scope given by the Identity parameter. -All subsites that meet the criteria are returned. - -The Identity can be either the full URL or a relative path. -If you specify a relative path, you must also specify the Site parameter to identify the site collection from which to return the subsite. - -The Identity parameter also supports providing a partial URL that ends in a wildcard character (*). -All subsites that match this partial URL for the specified scope are returned. -Additionally, if the Regex parameter is provided, the Identity parameter is treated as a regular expression and any subweb with a URL provided in the given scope that matches the expression is returned. - -The Filter parameter is a server-side filter for certain subsite properties that are stored in the content database; without the Filter parameter, filtering on these properties is a slow process. -These subsite properties are Template and Title. -The Filter parameter is a script block that uses the same syntax as a Where-Object statement, but is run server-side for faster results. - -It is important to note that every site collection returned by the Get-SPWeb cmdlet is automatically disposed of at the end of the pipeline. -To store the results of Get-SPWeb in a local variable, the Start-SPAssignment and Stop-SPAssignment cmdlets must be used to avoid memory leaks. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE 1---------------------- -``` -Get-SPWeb -site https://sitename/sites/site1 -``` - -This example returns all the subwebs in a given site collection. - -### --------------------EXAMPLE 2---------------------- -``` -Get-SPWeb -Site https://sitename/sites/site1 -filter {$_.Template -eq "STS#0"} -``` - -This example displays all subsites that use the "STS#0" template. - -### --------------------EXAMPLE 3---------------------- -``` -Start-SPAssignment -Global - -C:\PS>$w = Get-SPWeb https://sitename - -C:\PS>$w.set_SiteLogoUrl("https://pathtoimage/test.jpg") - -C:\PS>$w.Update() - -Stop-SPAssignment -Global -``` - -This example demonstrates how to save a subsite as a variable and to call object model methods on the SPAssignment object. - -## PARAMETERS - -### -Identity -Specifies the name or full or partial URL of the subsite. -If you use a relative path, you must specify the Site parameter. - -A valid URL in the form https://server_name or a relative path in the form of /SubSites/MySubSite. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -Specifies the server-side filter to use for the specified scope. - -The type must be a valid filter in the form {filterName \<operator\> "filterValue"}. - -```yaml -Type: ScriptBlock -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Limit -Limits the maximum number of subsites to return. -The default value is 200. -To return all sites, enter ALL - -The type must be a valid number greater than 0 or ALL. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Regex -Specifies the URL that is provided by the Identity parameter is treated as a regular expression. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Specifies the URL or GUID of the site collection from which to list subsites. - -The type must be a valid URL, in the form of https://server_name; a GUID, in the form 1234-5678-9807, or an SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplication.md deleted file mode 100644 index 9dab5dfccc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplication.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwebapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWebApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWebApplication - -## SYNOPSIS - -Returns all Web applications that match the given criteria. - - - -## SYNTAX - -``` -Get-SPWebApplication [[-Identity] <SPWebApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-IncludeCentralAdministration] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWebApplication cmdlet returns all Web applications that match the scope given by the Identity parameter. -The Identity can be the name of the name, URL, or GUID of the Web application. -If no Identity is specified, all Web applications are returned. - -The Central Administration Web application is only returned if its exact identity is provided or the IncludeCentralAdministration flag is provided. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1---------------------- -``` -C:\PS>$w = Get-SPWebApplication https://sitename -``` - -This example gets the Web application for https://sitename and stores it in a variable. - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPWebApplication -IncludeCentralAdministration | Where { $_.DefaultServerComment -eq "SharePoint Central Administration v4"} | Format-List * -``` - -This example displays all public properties on the SharePoint Central Administration Web application in list format. - -## PARAMETERS - -### -Identity -Specifies the name, URL, or GUID of the Web application. - -The type must be a valid URL, in the form https://server_name; a GUID, in the form 1234-5678-9876-0987; or a valid name, in the form SPWebApplication - 1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IncludeCentralAdministration -Includes the Central Administration Web application in the collection of Web applications that can be returned. -The IncludeCentral Administration parameter must still meet any other filters provided. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplicationAppDomain.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplicationAppDomain.md deleted file mode 100644 index 30c9c101b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplicationAppDomain.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwebapplicationappdomain -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWebApplicationAppDomain -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWebApplicationAppDomain - -## SYNOPSIS - -Returns all app domains for a specific web application. - -## SYNTAX - -### ResourceName -``` -Get-SPWebApplicationAppDomain [[-Identity] <SPAppDomainPipeBind>] -AppDomain <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Zone <SPUrlZone>] [<CommonParameters>] -``` - -### WebApplication -``` -Get-SPWebApplicationAppDomain [[-Identity] <SPAppDomainPipeBind>] -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Zone <SPUrlZone>] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Get-SPWebApplicationAppDoman cmdlet to return all app domains for a specific web application or for all web applications. If you do not specify parameters, the default zone is used. - -## EXAMPLES - -### -----------EXAMPLE 1--------- -``` -Get-SPWebApplicationAppDomain -``` - -Returns a list of SPAppDomain objects, one for each of the app domains for all web applications in the farm. - -### -----------EXAMPLE 2--------- -``` -Get-SPWebApplicationAppDomain -Zone Default -``` - -Returns a list of SPAppDomain objects, one for each of the app domains for the Default zone for all web applications in the farm. - -### -----------EXAMPLE 3--------- -``` -Get-SPWebApplicationAppDomain -WebApplication https://www.contoso.com -``` - -Returns a list of SPAppDomain objects, one for each of all the app domains for the specified web application for all zones. - -### -----------EXAMPLE 4--------- -``` -Get-SPWebApplicationAppDomain -AppDomain contosoapps.com -``` - -Returns a list of SPAppDomain objects, one for each web application and zone pair that shares the specified app domain. - -## PARAMETERS - -### -Identity - -Specifies the string of a domain name (that is, contoso.com) or a SPAppDomain object. - -```yaml -Type: SPAppDomainPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AppDomain - -Specifies the URI of the app domain. - -```yaml -Type: String -Parameter Sets: ResourceName -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication - -Specifies the GUID, URI, or name of the web application for which the app domain is being configured. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Zone - -Specifies the security zone to which the app domain will be assigned. - -* Default - -* Intranet - -* Internet - -* Extranet - -* Custom - -If no value is specified, Default is applied. - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.Administration.SPAppCmdlets.SPAppDomainPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[New-SPWebApplicationAppDomain](New-SPWebApplicationAppDomain.md) - -[Remove-SPWebApplicationAppDomain](Remove-SPWebApplicationAppDomain.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplicationHttpThrottlingMonitor.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplicationHttpThrottlingMonitor.md deleted file mode 100644 index 19d701bc90..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebApplicationHttpThrottlingMonitor.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwebapplicationhttpthrottlingmonitor -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWebApplicationHttpThrottlingMonitor -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWebApplicationHttpThrottlingMonitor - -## SYNOPSIS - -Returns all counters and their associated Health Score bucket values for network throttling on a Web application. - - - -## SYNTAX - -``` -Get-SPWebApplicationHttpThrottlingMonitor [-Identity] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWebApplicationHttpThrottlingMonitor cmdlet reads all counters for network throttling on a Web application. -This cmdlet returns a list that contains all of the performance counters and their associated Health Score bucket values. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$s = get-SPWebApplicationHTTPThrottlingMonitors https://sharepoint -``` - -This example gets all performance counters that are being read in the network throttling monitor for the https://sharepoint Web application. - -## PARAMETERS - -### -Identity -Returns throttling performance counter settings for the specified SharePoint Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebPartPack.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebPartPack.md deleted file mode 100644 index 3f83391b79..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebPartPack.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwebpartpack -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWebPartPack -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWebPartPack - -## SYNOPSIS - -Returns the Web Part packages that were installed for the specified scope. - - - -## SYNTAX - -``` -Get-SPWebPartPack [[-Identity] <String>] [-AssignmentCollection <SPAssignmentCollection>] [-GlobalOnly] - [-WebApplication <SPWebApplicationPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWebPartPack cmdlet returns the installed Web Part packages that match the Identity parameter. -The scope of results can be narrowed by using the optional WebApplication parameter. -The scope does not include any Web Part packages installed in the global assembly cache (GAC) unless the GlobalOnly parameter is used. -If this parameter is used, only Web Part packages that have been installed in the GAC are returned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPWebPartPack -WebApplication http://zsharepoint2:80 -``` - -This example returns all Web Part packages that have been installed on the Web application on port 80 in local farm. - -## PARAMETERS - -### -Identity -Specifies the full or partial name of the Web Part package from the configuration database. - -The type must be a valid name of a Web Part package; for example, MyWebPartPackage. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -GlobalOnly -Returns only Web Part packages that are installed in the global assembly cache (GAC). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the Web application from which to list Web Part packages. -If no Web application is specified, the specified Web Part packages will be returned from all Web applications. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebTemplate.md deleted file mode 100644 index 09c70514b5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebTemplate.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwebtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWebTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWebTemplate - -## SYNOPSIS - -Displays all globally installed site templates that match the given identity. - - - -## SYNTAX - -``` -Get-SPWebTemplate [[-Identity] <SPWebTemplatePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <UInt32>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-SPWebTemplate cmdlet displays all installed site templates that match the full or partial identity that was given. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -C:\PS>$template = Get-SPWebTemplate "STS#0" - -New-SPSite https://contoso.com -OwnerAlias "DOMAIN\JDOE" -Template $template -``` - -This example creates a site collection by using the team site Web template (ID=STS#0). - -### --------------EXAMPLE 2----------------- -``` -Get-SPWebTemplate "STS*" -``` - -This example displays basic information about all the STS templates. - -## PARAMETERS - -### -Identity -Specifies the name of the Web template to display. - -The type must be the ID or full or partial name of the Web template. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. -This value sets the initial CompatibilityLevel value for the site collection. -The values for this parameter can be either SharePoint Server or SharePoint Server. -When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the Web application depending on the SiteCreationMode setting - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebTemplatesEnabledForSiteMaster.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebTemplatesEnabledForSiteMaster.md deleted file mode 100644 index b83665dc32..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWebTemplatesEnabledForSiteMaster.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spwebtemplatesenabledforsitemaster -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWebTemplatesEnabledForSiteMaster -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWebTemplatesEnabledForSiteMaster - -## SYNOPSIS -Returns a list of site master web templates. - -## SYNTAX - -``` -Get-SPWebTemplatesEnabledForSiteMaster [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-SPWebTemplatesEnabledForSiteMaster cmdlet to display a full list of site master web templates in the farm. - -## EXAMPLES - -### Example 1 -``` -Get-SPWebTemplatesEnabledForSiteMaster -``` - -This example displays all the site master web templates in a farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWorkflowConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWorkflowConfig.md deleted file mode 100644 index f86d074c49..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWorkflowConfig.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spworkflowconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWorkflowConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWorkflowConfig - -## SYNOPSIS - -Returns workflow settings for the specified Web application. - - - -## SYNTAX - -### SiteCollection -``` -Get-SPWorkflowConfig [-SiteCollection] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### WebApplication -``` -Get-SPWorkflowConfig [-WebApplication] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Get-SPWorkflowConfig cmdlet returns workflow settings for the Web application specified by the WebApplication parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPWorkFlowConfig -webapplication https://sitename -``` - -This example gets workflow settings for the specified Web application (https://sitename). - -To get farm-level workflow settings for event delivery time-out, postpone threshold, and batch size, use the Get-SPFarmConfig cmdlet. - -## PARAMETERS - -### -SiteCollection -Specifies the name or URL of the site collection. - -The only other parameter that is used with the SiteCollection parameter is the DeclarativeWorkflowsEnabled parameter. -No other parameters are used. - -```yaml -Type: SPSitePipeBind -Parameter Sets: SiteCollection -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the name or URL of the Web application. - -The type must be a valid name, in the form WebApplication-1212, or a URL, in the form https://server_name/WebApplication-1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWorkflowServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWorkflowServiceApplicationProxy.md deleted file mode 100644 index e38f966ac6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Get-SPWorkflowServiceApplicationProxy.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.SharePoint.WorkflowServices.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/get-spworkflowserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Get-SPWorkflowServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Get-SPWorkflowServiceApplicationProxy - -## SYNOPSIS -Returns the Workflow Service Application Proxy. - -## SYNTAX - -``` -Get-SPWorkflowServiceApplicationProxy [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Returns the Workflow Service Application Proxy. - -## EXAMPLES - -### Example 1 -``` -Get-SPWorkflowServiceApplicationProxy -``` -Returns the Workflow Service Application Proxy. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Grant-SPBusinessDataCatalogMetadataObject.md b/sharepoint/sharepoint-ps/sharepoint-server/Grant-SPBusinessDataCatalogMetadataObject.md deleted file mode 100644 index d032cc1e88..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Grant-SPBusinessDataCatalogMetadataObject.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/grant-spbusinessdatacatalogmetadataobject -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Grant-SPBusinessDataCatalogMetadataObject -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Grant-SPBusinessDataCatalogMetadataObject - -## SYNOPSIS - -Grants a right to a principal for the specified Business Data Connectivity Metadata Store metadata object. - - - -## SYNTAX - -``` -Grant-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> -Principal <SPClaim> -Right <PSBdcRight> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SettingId <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Grant-SPBusinessDataCatalogMetadataObject cmdlet grants the right to a specified principal (user) for a Business Data Connectivity Metadata Store metadata object. -This cmdlet checks to verify that the Identity parameter is a valid IndividuallySecurableMetadata object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$claimJohn = New-SPClaimsPrincipal -Identity "CONTOSO\johndoe" -IdentityType WindowsSamAccountName -$Model = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Model" -ServiceContext http://contoso -Name "ContosoModel" -Grant-SPBusinessDataCatalogMetadataObject -Identity $Model -Principal $claimJohn -Right Edit -``` - -This example gives Edit permissions to the user with the identity johndoe on domain CONTOSO, for the model metadata object with the name ContosoModel. - -## PARAMETERS - -### -Identity -Specifies the Business Data Connectivity Metadata Store metadata object that contains the principal. - -```yaml -Type: MetadataObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Principal -Specifies the principal to whom the rights apply. - -The type must be a claim. - -```yaml -Type: SPClaim -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Right -Specifies the right to grant the principal. - -The type must be one of the following valid PSBdcRight object types: All, Execute, Edit, SetPermissions, or SelectableInClients. - -```yaml -Type: PSBdcRight -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SettingId -Specifies the model slice for which to grant the right. - -The type must be a valid string that identifies a model slice; for example, ModelSlice1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Grant-SPObjectSecurity.md b/sharepoint/sharepoint-ps/sharepoint-server/Grant-SPObjectSecurity.md deleted file mode 100644 index 6402f725b7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Grant-SPObjectSecurity.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/grant-spobjectsecurity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Grant-SPObjectSecurity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Grant-SPObjectSecurity - -## SYNOPSIS - -Adds a new security principal to an SPObjectSecurity object. - - - -## SYNTAX - -``` -Grant-SPObjectSecurity [-Identity] <SPObjectSecurity> [-Principal] <SPClaim> [-Rights] <String[]> - [-AssignmentCollection <SPAssignmentCollection>] [-Replace] [<CommonParameters>] -``` - -## DESCRIPTION -The Grant-SPObjectSecurity cmdlet adds a new security principal, such as a user, to a SPObjectSecurity object. -An SPObjectSecurity object is a common object that is used to represent the security access control list (ACL) of SharePoint administrative objects, in particular, service applications. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$principal = New-SPClaimsPrincipal "CONTOSO\JaneDoe" -IdentityType WindowsSamAccountName -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'User Profile Service Application'} -$security = Get-SPServiceApplicationSecurity $sa -Admin -Grant-SPObjectSecurity $security $principal "Full Control" -Set-SPServiceApplicationSecurity $sa -Admin $security -``` - -This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on the User Profile Service Application and adds a new user principal to that ACL. - -The new user is an administrator for the service application $serviceApp. - -## PARAMETERS - -### -Identity -Specifies the SPObjectSecurity object to which the new security principal is added. -You can use the Get-SPServiceApplicationSecurity cmdlet to get a SPObjectSecurity object . - -```yaml -Type: SPObjectSecurity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Principal -Specifies the principal to whom the rights apply. - -The type must a valid name a principal; for example, Full Control. - -```yaml -Type: SPClaim -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Rights -Specifies the rights granted to the principal. - -The type must a valid array of strings that represents the rights granted to the principal. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Replace -Replaces the existing rights on the SPObjectSecurity object with the new rights specified. -If this parameter is not specified, the new rights are added to the existing rights. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPAccessServicesDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPAccessServicesDatabase.md deleted file mode 100644 index ac488bc706..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPAccessServicesDatabase.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spaccessservicesdatabase -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPAccessServicesDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPAccessServicesDatabase - -## SYNOPSIS -Imports an Access Services Database to a DACPAC via the Data-Tier Framework. - -## SYNTAX - -``` -Import-SPAccessServicesDatabase [-AssignmentCollection <SPAssignmentCollection>] -Bacpac <Byte[]> - -DatabaseName <String> -ServerReferenceId <Guid> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet exports an Access Services Database to a DACPAC. The cmdlet requires the Data-Tier Framework to be installed on the SharePoint server where the cmdlet is run. The Data-Tier Framework packages can be found at [Microsoft® SQL Server® Data-Tier Application Framework (17.4.1 GA DacFx)](https://www.microsoft.com/en-us/download/details.aspx?id=56508). Install the following MSI from the download: - -EN\x86\DacFramework.msi - -Note: The x86 package is required. The x64 package is not compatible with this cmdlet. - -See more information about Data-Tier Framework at [Data-tier Applications](https://docs.microsoft.com/sql/relational-databases/data-tier-applications/data-tier-applications). - -## EXAMPLES - -### Example 1 -``` -$accessDb = Get-SPAccessServicesDatabaseServer -ServiceContext http://site_url -DatabaseServer SQLSERVERNAME -DatabaseServerGroup DEFAULT -Import-SPAccessServicesDatabase -DatabaseName accessDatabaseName -ServerReferenceId $accessDb.ServerReferenceId -Bacpac (Get-Content -Path C:\accessDb.bacpac -Encoding Byte) -``` - -This example gets the ServerReferenceId value of the SQL Server for the Access Services Service Application; -DatabaseServerGroup is set to the value DEFAULT by default. The next step is to import the bacpac file to a byte array and finally, import the Access Services Database as the specified SQL database name to the specified SQL Server. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Bacpac -A byte array of the bacpac file. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseName -The name of the database to create from the bacpac file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServerReferenceId -The ServerReferenceId to be used for the Access Database. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -System.Guid -System.Byte[] -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPAppPackage.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPAppPackage.md deleted file mode 100644 index 6d6072cabe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPAppPackage.md +++ /dev/null @@ -1,203 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spapppackage -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPAppPackage -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPAppPackage - -## SYNOPSIS - -Imports an app package. - -## SYNTAX - -``` -Import-SPAppPackage -Path <String> -Source <SPAppSource> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [-AssetId <String>] [-ContentMarket <String>] -Site <SPSitePipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Import-SPAppPackage cmdlet to import an app package from the content database and create an app inside the site collection by using the SiteCollection parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE---------- -``` -Import-SPAppPackage -Path .\feature-upgrade-v1.spapp -Site https://localhost -Source ([microsoft.sharepoint.administration.spappsource]::ObjectModel) -``` - -This example imports an app package. - -## PARAMETERS - -### -Path -Specifies the path of the input file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Source -Defines the source of the app. The source indicates where the app package originates from, for example, if the app was built by a developer but did not reside on the SharePoint Marketplace, you might use the CorporateCatalog source. - -The following are valid values: - -InvalidSource, Marketplace, CorporateCatalog, DeveloperSite, ObjectModel, RemoteObjectModel - -The following are valid sources (not parameters of -Source) of the app: - ---SharePoint Store (Marketplace) - ---App catalog (CorporateCatalog) - ---SharePointService - Indicates apps that were built in place with SharePoint features, for example Access Services (ObjectModel) - - -```yaml -Type: SPAppSource -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssetId -Specifies the Asset Id to import. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentMarket -Specifies the name of the content market. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Specifies the SPSite object to import. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Export-SPAppPackage](Export-SPAppPackage.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPBusinessDataCatalogDotNetAssembly.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPBusinessDataCatalogDotNetAssembly.md deleted file mode 100644 index a4abd53540..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPBusinessDataCatalogDotNetAssembly.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spbusinessdatacatalogdotnetassembly -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPBusinessDataCatalogDotNetAssembly -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPBusinessDataCatalogDotNetAssembly - -## SYNOPSIS - -Imports a .NET Connectivity assembly. - - - -## SYNTAX - -``` -Import-SPBusinessDataCatalogDotNetAssembly -LobSystem <LobSystem> -Path <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DependentAssemblyPaths <String[]>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPBusinessDataCatalogDotNetAssembly cmdlet imports a .NET Connectivity Assembly that corresponds to a .NET Assembly Connector and LobSystem in the metadata store. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE 1---------------- -``` -Import-SPBusinessDataCatalogDotNetAssembly -LobSystem $ContosoDB -Path "c:\Folder\Assembly.dll" -``` - -This example imports the assembly Assembly. - -### -----------------EXAMPLE 2---------------- -``` -Import-SPBusinessDataCatalogDotNetAssembly -LobSystem $ContosoDB -Path "c:\Folder\Assembly.dll" -DependentAssemblyPaths "c:\Folder\Assembly2.dll","c:\Folder\Assembly3.dll" -``` - -This example imports the assembly Assembly, and also imports the dependent assemblies Assembly2 and Assembly3. - -## PARAMETERS - -### -LobSystem -Specifies the LobSystem that the assembly corresponds to. - -```yaml -Type: LobSystem -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Specifies the path to the primary assembly. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DependentAssemblyPaths -Specifies a list of paths to dependent assemblies. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPBusinessDataCatalogModel.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPBusinessDataCatalogModel.md deleted file mode 100644 index a03d4bf24b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPBusinessDataCatalogModel.md +++ /dev/null @@ -1,282 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spbusinessdatacatalogmodel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPBusinessDataCatalogModel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPBusinessDataCatalogModel - -## SYNOPSIS - -Imports a Business Data Connectivity Model. - -## SYNTAX - -### Catalog -``` -Import-SPBusinessDataCatalogModel -Identity <MetadataObject> -Path <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-LocalizedNamesIncluded] - [-ModelsIncluded] [-PermissionsIncluded] [-PropertiesIncluded] [-SettingId <String>] [-WhatIf] - [<CommonParameters>] -``` - -### ServiceContext -``` -Import-SPBusinessDataCatalogModel -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Force] [-LocalizedNamesIncluded] [-ModelsIncluded] [-PermissionsIncluded] [-PropertiesIncluded] - [-SettingId <String>] [-WhatIf] -ServiceContext <SPServiceContextPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPBusinessDataCatalogModel cmdlet imports a Business Data Connectivity Model. -There are two types of Business Data Connectivity models: Model type (.bdcm) and Resource type (.bdcr). -The Model type contains the base XML metadata, and can also include resource properties. -The Resource type includes only resource properties. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$MetadataStore = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Catalog" -ServiceConext https://contoso -Import-SPBusinessDataCatalogModel -Path "C:\folder\model.bdcm" -Identity $MetadataStore -``` - -This example gets the Business Data Connectivity Metadata Store and then imports a Business Data Connectivity Model of Model type to it from the path specified with the name model. - -### ------------------EXAMPLE 2------------------ -``` -Import-SPBusinessDataCatalogModel -Path "C:\Program Files\Duet Enterprise\2.0\BDC Models\Reporting.en-us.bdcr -Identity $bdcCatalog -ModelsIncluded:$false -``` - -This example imports a resource only file by using the ModelsIncluded parameter. - -## PARAMETERS - -### -Identity -Specifies the Business Data Connectivity Metadata Store metadata object to import to. - -```yaml -Type: MetadataObject -Parameter Sets: Catalog -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the path and name to use. - -The type must be a valid path in either of the following forms: - -- C:\folder_name\file.bdcm -- \\\\server_name\folder_name\file.bdcm -- ...\folder_name\file.bdcm - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overwrites the Business Data Connectivity Model if the file exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalizedNamesIncluded -Specifies that names for business data fields in multiple languages are imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModelsIncluded -Specifies that models are included in the imported Business Data Connectivity Model file. -A model contains the base XML metadata for a system. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionsIncluded -Specifies that permissions from the Business Data Connectivity Model are imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertiesIncluded -Specifies that properties from the Business Data Connectivity Model are imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SettingId -Specifies the custom environment settings model slice to import. - -The type must be a valid string that identifies a model slice; for example, ModelSlice1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context to set. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: ServiceContext -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchCustomExtractionDictionary.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchCustomExtractionDictionary.md deleted file mode 100644 index a2cc7b11de..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchCustomExtractionDictionary.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spenterprisesearchcustomextractiondictionary -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPEnterpriseSearchCustomExtractionDictionary -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPEnterpriseSearchCustomExtractionDictionary - -## SYNOPSIS - -Imports a custom extraction dictionary. - -## SYNTAX - -``` -Import-SPEnterpriseSearchCustomExtractionDictionary -DictionaryName <String> -FileName <String> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet imports a custom extraction dictionary from a .cvs file and deploys it to the extraction sub flow. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$searchApp = Get-SPEnterpriseSearchServiceApplication -Import-SPEnterpriseSearchCustomExtractionDictionary -SearchApplication $searchApp -Filename c:\transfer\entity_extraction.csv -DictionaryName Microsoft.UserDictionaries.EntityExtraction.Custom.Word.1 -``` - -This example imports the custom extraction dictionary that is located at c:\transfer to the default search service application. -The entries of this dictionary will be matched in a case-insensitive way against the terms in the documents being indexed. - -## PARAMETERS - -### -DictionaryName -Specifies the name of the target dictionary. -The name must be one of the following 12 predefined dictionaries. -The name signifies the "case sensitivity" and "token matching" behavior. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileName - -Specifies the file path of the .cvs file to be imported - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication - -Specifies the search service application to which the custom extraction dictionary should be imported. - - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchPopularQueries.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchPopularQueries.md deleted file mode 100644 index e6de5f96fd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchPopularQueries.md +++ /dev/null @@ -1,212 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spenterprisesearchpopularqueries -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPEnterpriseSearchPopularQueries -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPEnterpriseSearchPopularQueries - -## SYNOPSIS -Imports queries from a comma-separated list. -The search box will suggest these queries as users type. - -## SYNTAX - -``` -Import-SPEnterpriseSearchPopularQueries -ResultSource <Source> - -SearchApplicationProxy <SearchServiceApplicationProxyPipeBind> -Web <SPWeb> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Filename <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPEnterpriseSearchPopularQueries cmdlet imports queries from a comma-separated list. -As the user types a query in the search box, the search box will suggest queries from the comma-separated list. -The search box bases these suggestions on: - -- The SPWeb the search box is located on. -- The Result Source configured on the search box. - -For example, if the search box is located on the "Engineering" SPWeb, the suggested queries will differ from if the search box is located on the "Management" SPWeb. -Likewise, if the Result Source on the search box is "Local SharePoint Results", the suggested queries will differ from if the Result Source is "Conversations". - -The comma-separated list must consist of one line per query, where each line contains the following items: - -Query Text. -The actual query expression. - -Query Count. -The number of times this query was executed. - -Click Count. -The number of times any user clicked any result for this query. - -LCID. -The locale identifier (LCID) for the language of the query. - -Each line must use the formatting: Query Text,Query Count,Click Count,LCID. -For example, Company store,100,80,1033. -For suggestions to appear in the search box, the Click Count value must be more than five. -The search box ranks query suggestions by their Click Count values (approximately). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------EXAMPLE-------- -``` -$ssap = Get-SPEnterpriseSearchServiceApplicationProxy -$hostname = hostname -$web = get-spsite | get-spweb | where {$_.Url-eq "https://$hostname/"} -$owner = new-object Microsoft.Office.Server.Search.Administration.SearchObjectOwner -ArgumentList @([Microsoft.Office.Server.Search.Administration.SearchObjectLevel]::SPWeb,$web) -$mgr = new-object Microsoft.Office.Server.Search.Administration.Query.FederationManager -ArgumentList $ssap -$source = $mgr.GetSourceByName("Local SharePoint Results", $owner) -Import-SPEnterpriseSearchPopularQueries -SearchApplicationProxy $ssap -Filename C:\input.txt -ResultSource $source -Web $web -``` - -This example uses the Import-SPEnterpriseSearchPopularQueries cmdlet to import the queries file that is named C:\input.txt and associate with it the Result Source referenced by $source and the SPWeb referenced by $web. -The example defines the variable $web as the SPWeb with URL https://hostname, and the variable $source as the Result Source named "Local SharePoint Results" at the SPWeb referenced by $web. - -## PARAMETERS - -### -ResultSource -Specifies the Result Source to associate with the imported queries. -The type must be an instance of a valid Source object. - -```yaml -Type: Source -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplicationProxy -Specifies the proxy for the search application to which the queries file should be imported. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application proxy name (for example, SearchAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Web -Specifies the SPWeb to associate with the imported queries. -The type must be an instance of a valid SPWeb object. - -```yaml -Type: SPWeb -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filename -Specifies the full UNC (Universal Naming Convention) path of the file to import. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchThesaurus.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchThesaurus.md deleted file mode 100644 index 81d0042a6d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchThesaurus.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spenterprisesearchthesaurus -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPEnterpriseSearchThesaurus -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPEnterpriseSearchThesaurus - -## SYNOPSIS -Deploys the dictionary to the thesaurus component in the query processing flow. - -## SYNTAX - -``` -Import-SPEnterpriseSearchThesaurus -FileName <String> -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet imports a thesaurus dictionary using a .cvs file, and deploys it to the query processing flow. -A previously deployed thesaurus is overwritten by an import of a new .cvs file. - -NOTE: If an empty .cvs file is imported, an empty thesaurus will be deployed. -No synonyms will then be added to the queries. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication -Import-SPEnterpriseSearchThesaurus -SearchApplication $searchApp -Filename -\\host\share\thesaurus.csv -``` - -This example imports a thesaurus dictionary .cvs file named thesaurus.csv that is located at \\\\host\share to the default search service application. - -## PARAMETERS - -### -FileName -Specifies the full UNC (Universal Naming Convention) path of the .cvs file to be imported. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application to which the thesaurus dictionary should be imported - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchTopology.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchTopology.md deleted file mode 100644 index e341221754..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPEnterpriseSearchTopology.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spenterprisesearchtopology -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPEnterpriseSearchTopology -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPEnterpriseSearchTopology - -## SYNOPSIS -Imports and activates a topology from an XML file. - -## SYNTAX - -``` -Import-SPEnterpriseSearchTopology -Filename <String> -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPEnterpriseSearchTopology cmdlet imports from an XML file the topology for a shared search application. -The Export-SPEnterpriseSearchTopology cmdlet is used to save a search topology. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Import-SPEnterpriseSearchTopology -SearchApplication $ssa -Filename .\topology.xml -``` - -This example imports a topology from a file named topology.xml to the default search service application. - -## PARAMETERS - -### -Filename -Specifies the path and file name of the topology XML file to import. - -The type must be a valid path, in the form MyFeature\Feature.xml. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application to which to apply the topology. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchTopology](New-SPEnterpriseSearchTopology.md) - -[Get-SPEnterpriseSearchTopology](Get-SPEnterpriseSearchTopology.md) - -[Set-SPEnterpriseSearchTopology](Set-SPEnterpriseSearchTopology.md) - -[Remove-SPEnterpriseSearchTopology](Remove-SPEnterpriseSearchTopology.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPInfoPathAdministrationFiles.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPInfoPathAdministrationFiles.md deleted file mode 100644 index 5881388130..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPInfoPathAdministrationFiles.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spinfopathadministrationfiles -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPInfoPathAdministrationFiles -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPInfoPathAdministrationFiles - -## SYNOPSIS -Imports InfoPath form templates and .udcx files that are located on the SharePoint Central Administration Web site. - -## SYNTAX - -``` -Import-SPInfoPathAdministrationFiles [-Path] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Identity <SPFormsServicePipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPInfoPathAdministrationFiles cmdlet imports InfoPath form templates (.xsn files) and universal data connections (.udcx files) that are located on the SharePoint Central Administration Web site into the specified InfoPath Forms Services service. -This cmdlet imports from a backup package that includes all workflow forms in InfoPath that were deployed by an administrator and not included with SharePoint Foundation, and browser forms that were deployed by an administrator. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Import-SPInfoPathAdministrationFiles -path "backupfiles.cab" -``` - -This example imports form templates (XSN files) and universal data connections (UDCX files) located on the SharePoint Central Administration Web site into the specified Forms service. - -## PARAMETERS - -### -Path -Specifies the location of the .cab file to import. - -The type must be a valid file path, in the form \\\\ipadmin\folder\backups1\ipfsfiles.cab. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the destination InfoPath Forms Services service for the import. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a forms service (for example, FormsService1); or an instance of a valid SPFormsService object. - -```yaml -Type: SPFormsServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPMetadataWebServicePartitionData.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPMetadataWebServicePartitionData.md deleted file mode 100644 index 0b7878418f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPMetadataWebServicePartitionData.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spmetadatawebservicepartitiondata -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPMetadataWebServicePartitionData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPMetadataWebServicePartitionData - -## SYNOPSIS -Restores the data for a site subscription. - -## SYNTAX - -``` -Import-SPMetadataWebServicePartitionData [-Identity] <SPSiteSubscriptionPipeBind> - [-ServiceProxy] <SPMetadataServiceProxyCmdletPipeBind> -Path <String> - [-AssignmentCollection <SPAssignmentCollection>] [-OverwriteExisting] [-NoCompression] - [-ToContentDatabase <SPContentDatabasePipeBind>] [-ToServiceDatabase] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Import-SPMetadataWebServicePartitionData cmdlet to restore data for a site subscription to a shared service application for the Metadata Service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE---------------------- -``` -$subscription = Get-SPSIteSubscription -Identity https://site_url -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'Managed Metadata Service Connection'} -Import-SPMetadataWebServicePartitionData -Identity $subscription -ServiceProxy $proxy -Path "\\server_name\folder_name\file_name.cab" -``` - -This example restores a backup of Metadata Service application data for a specific site subscription on a Metadata Service application. - -## PARAMETERS - -### -Identity -Specifies the site subscription to import. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscriptionConfig1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceProxy -Specifies the proxy for the service application that contains the site subscription. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of the service application proxy (for example, ServiceAppProxy1); or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the path and name of the subscription data file to import. - -The type must be a valid path in either of the following forms: - -- C:\folder_name\formtemplate_name -- \\\\server_name\folder_name\file_name.cab - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -OverwriteExisting -Specifies whether to overwrite the existing site subscription data, if it exists. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoCompression -{{Fill NoCompression Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ToContentDatabase -{{Fill ToContentDatabase Description}} - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ToServiceDatabase -{{Fill ToServiceDatabase Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPPerformancePointContent.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPPerformancePointContent.md deleted file mode 100644 index 2f88389e86..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPPerformancePointContent.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spperformancepointcontent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPPerformancePointContent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPPerformancePointContent - -## SYNOPSIS -Imports a Performance Point Server (PPS) dashboard. - -## SYNTAX - -``` -Import-SPPerformancePointContent [-AssignmentCollection <SPAssignmentCollection>] -DatasourceMap <Hashtable> - -ImportFileUrl <String> -LocationMap <Hashtable> -MasterPageUrl <String> -SiteDestination <SPWebPipeBind> - [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPPerformancePointContent imports a PPS dashboard and its dependencies from a CMP file that can then be used to import to another server. - -## EXAMPLES - -### Example 1 -``` -$ContentList = @{"/bi/Dashboard Content" = "/biprod/Dashboard Content"; "/bi/My Projects" = "/biprod/My Projects"} -$DatasourceList = @{"/bi/DataConnections/AdventureWorks.ppsdc" = "/myBi/libraries/DataConnections/AdventureWorks_prod.ppsdc"; "/bi/DataConnections/AW 2008 Cubes4.ppsdc" = "/myBi/libraries/DataConnections/AW 2008 Cubes3.ppsdc"; "/sales/DataConnections/Excel DS.ppsdc" = "/marketing/PPS Data Sources/PDW 2010.ppsdc"} -Import-SPPerformancePointContent -ImportFileURL "https://contoso.com/biprod/DocumentLibrary/Dashboard1.cmp" -SiteDestination "https://contoso.com/biprod/" -LocationMap $ContentList -DatasourceMap $DatasourceList -MasterPage "marketing and sales.master" -``` - -This example imports a dashboard by using the $Datasourcelist and $ContentList variables. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatasourceMap -Maps existing or adds new data sources to destination library. - -```yaml -Type: Hashtable -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImportFileUrl -Path and Name of the CMP file created in the export command. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationMap -Maps the locations between source lists and destination lists. - -```yaml -Type: Hashtable -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MasterPageUrl -Specifies which master page to use for imported dashboards. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteDestination -Specifies the site to which the dashboard will be deployed. Also used to determine the location of the import Key Performance Indicator (KPI). - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPWebPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPScaleOutDatabaseTenantData.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPScaleOutDatabaseTenantData.md deleted file mode 100644 index 7f865d0c86..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPScaleOutDatabaseTenantData.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spscaleoutdatabasetenantdata -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPScaleOutDatabaseTenantData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPScaleOutDatabaseTenantData - -## SYNOPSIS - -Imports data from the specified subscription id. - - - -## SYNTAX - -``` -Import-SPScaleOutDatabaseTenantData -FilePath <String> -ServiceApplication <SPServiceApplicationPipeBind> - -SiteSubscriptionId <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Import-SPScaleOutDatabaseTenantData cmdlet to import data from the specified file for the specified subscription id to the specified service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE---------- -``` -Import-SPScaleOutDatabaseTenantData -FilePath "C:\TenantData.dat" -ServiceApplication $serviceApplication -SiteSubscriptionId "5CAF2F99-A75F-4239-B9CD-7FE63D1CE904" -``` - -This example imports data from the file at C:\TenantData.dat, to the specified service application and marks all the imported data with the site subscription id 5CAF2F99-A75F-4239-B9CD-7FE63D1CE904. - -## PARAMETERS - -### -FilePath -Specifies the absolute path to the data file. - -An absolute path includes the root directory and all sub-directories. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the service application to import the data to. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptionId -Specifies the site subscription id to import the data from. -This value will replace the site subscription id value from the data file. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-SPScaleOutDatabaseTenantData](Clear-SPScaleOutDatabaseTenantData.md) - -[Export-SPScaleOutDatabaseTenantData](Export-SPScaleOutDatabaseTenantData.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPServerScaleOutDatabaseTenantData.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPServerScaleOutDatabaseTenantData.md deleted file mode 100644 index 11feab0d83..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPServerScaleOutDatabaseTenantData.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spserverscaleoutdatabasetenantdata -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPServerScaleOutDatabaseTenantData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPServerScaleOutDatabaseTenantData - -## SYNOPSIS - -Imports data from the specified subscription id. - -## SYNTAX - -``` -Import-SPServerScaleOutDatabaseTenantData -FilePath <String> -ServiceApplication <SPServiceApplicationPipeBind> - -SiteSubscriptionId <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Import-SPServerPScaleOutDatabaseTenantData cmdlet to import data from the specified file for the specified subscription id to the specified service application. - -## EXAMPLES - -### -------------EXAMPLE---------- -``` -Import-SPServerScaleOutDatabaseTenantData -FilePath "C:\TenantData.dat" -ServiceApplication $serviceApplication -SiteSubscriptionId "5CAF2F99-A75F-4239-B9CD-7FE63D1CE904" -``` - -This example imports data from the file at C:\TenantData.dat, to the specified service application and marks all the imported data with the site subscription id 5CAF2F99-A75F-4239-B9CD-7FE63D1CE904. - - -## PARAMETERS - -### -FilePath - -Specifies the absolute path to the data file. - -An absolute path includes the root directory and all sub-directories. - - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication - -Specifies the service application to import the data to. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptionId - -Specifies the site subscription id to import the data from. -This value will replace the site subscription id value from the data file. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Clear-SPServerScaleOutDatabaseTenantData](Clear-SPServerScaleOutDatabaseTenantData.md) - -[Export-SPServerScaleOutDatabaseTenantData](Export-SPServerScaleOutDatabaseTenantData.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPSiteSubscriptionBusinessDataCatalogConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPSiteSubscriptionBusinessDataCatalogConfig.md deleted file mode 100644 index bb89fa7b3d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPSiteSubscriptionBusinessDataCatalogConfig.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spsitesubscriptionbusinessdatacatalogconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPSiteSubscriptionBusinessDataCatalogConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPSiteSubscriptionBusinessDataCatalogConfig - -## SYNOPSIS - -Imports data associated with an exported file that contains all data associated with the Business Data Connectivity Metadata Store for a given partition. - - - -## SYNTAX - -``` -Import-SPSiteSubscriptionBusinessDataCatalogConfig -Path <String> -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-LocalizedNamesIncluded] [-ModelsIncluded] - [-PermissionsIncluded] [-PropertiesIncluded] [-ProxiesIncluded] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Import-SPSiteSubscriptionBusinessDataCatalogConfig cmdlet to import a data file that contains Business Data Connecitivity models and all data associated with the Business Data Connectivity Metadata Store for a given partition. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE--------------------------- -``` -Import-SPSiteSubscriptionBusinessDataCatalogConfig -Path "C:\folder\importFile.xml" -ServiceContext http://contoso -``` - -This example imports the data file named importFile.xml. - -## PARAMETERS - -### -Path -Specifies the path and name to use to create the export file.The type must be a valid path in either of the following forms: - -C:\folder_name - -\\\\server_name\folder_name - -..\folder_name\file.xml - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context of the data to be exported. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service context (for example, http://ServiceContext1); or an instance of a valid SPServiceContext object. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalizedNamesIncluded -Specifies that names for business data fields in multiple languages be imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ModelsIncluded -Specifies that Business Data Connectivity models be included in the imported file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionsIncluded -Specifies that permissions from the Business Data Connectivity model be exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertiesIncluded -Specifies that properties from the Business Data Connectivity model be imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProxiesIncluded -Specifies that proxies for Business Data Connectivity Service Applications be exported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPSiteSubscriptionSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPSiteSubscriptionSettings.md deleted file mode 100644 index 3296ee486e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPSiteSubscriptionSettings.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spsitesubscriptionsettings -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPSiteSubscriptionSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPSiteSubscriptionSettings - -## SYNOPSIS - -Restores a backup of subscription site settings to the given subscription identifier. - -## SYNTAX - -``` -Import-SPSiteSubscriptionSettings [-Identity] <SPSiteSubscriptionPipeBind> -Path <String> [-AdminProperties] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPSiteSubscriptionSettings cmdlet restores a backup of subscription site settings to the given subscription identifier when the Identity parameter is used. -To overwrite existing settings, use the Force parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -$subscription = Get-SPSiteSubscription https://site_url -Import-SPSiteSubscriptionSettings -Identity $subscription -Path "C:\backups\contoso_settings_file.bak" -Force -``` - -This example restores the subscription settings store of contoso.com. - -## PARAMETERS - -### -Identity -Specifies the ID of the subscription to restore . - -The type must be a valid URL, in the form https://site_url, or a GUID, in the form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the location of the input file. - -The type must be a valid path, in the form C:\filename.bak. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminProperties -Specifies that only administrator subscription properties are imported. -If this parameter is not set, only non-administrator subscription properties are imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -If a setting key already exists, determines whether the value must be overwritten with the value in the backup file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Import-SPWeb.md deleted file mode 100644 index c9b011dead..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Import-SPWeb.md +++ /dev/null @@ -1,338 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/import-spweb -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Import-SPWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Import-SPWeb - -## SYNOPSIS - -Imports a web, list, or library. - - - -## SYNTAX - -``` -Import-SPWeb [-Identity] <SPWebPipeBind> -Path <String> [-ActivateSolutions] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-HaltOnError] [-HaltOnWarning] - [-IncludeUserCustomAction <SPIncludeUserCustomAction>] [-IncludeUserSecurity] [-NoFileCompression] - [-NoLogFile] [-UpdateVersions <SPUpdateVersions>] [-WhatIf] [-PreserveDeletedUserMetadataReferences] - [<CommonParameters>] -``` - -## DESCRIPTION -The Import-SPWeb cmdlet imports a web, list, or library. -The capability to import from a library is a new feature in SharePoint Products. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE---------------------- -``` -Import-SPWeb https://site -Path export.cmp -UpdateVersions Overwrite -``` - -This example imports the contents of export.cmp into a site at https://site, overwriting the versioned content on the site with the contents of the export.cmp file. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the Web to import into. - -The type must be a valid URL, GUID, or object; for example, a valid URL, in the form https://server_name, or a GUID, in the form, 1234-4567-5678a. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies the name of the import file. - -If the NoFileCompression parameter is used, a directory must be specified; otherwise, any file format is valid. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ActivateSolutions -Specifies whether user solutions are activated during import. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter has no function in this cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HaltOnError -Stops the import process when an error occurs. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HaltOnWarning -Stops the import process when a warning occurs. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeUserCustomAction -Specifies whether User Custom Actions are included during import. - -Valid values are: - -All, None - -```yaml -Type: SPIncludeUserCustomAction -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeUserSecurity - -Preserves the user security settings. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoFileCompression -Either enables or disables file compression in the import package. -The import package is stored in the folder specified by the Path parameter or Identity parameter. -We recommend that you use this parameter for performance reasons. -If compression is enabled, the import process can increase by approximately 30 percent. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoLogFile -Suppresses the generation of an import log file. -If this parameter is absent, the Import-SPWeb cmdlet will generate an export log file in the same location as the export package. -The log file uses Unified Logging Service (ULS). - -We recommend that you use this parameter. -However, for performance reasons, you might not want to generate a log file. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UpdateVersions -Indicates how to resolve situations where a file to be imported to a site already exists in that site. -If the UpdateVersions parameter is absent, the import operation by default uses a value of 1 (Append). - -The type must be any one of the following: - --Append, which adds new versions to the current file - --Overwrite the file and all of its versions (delete then insert) - --Ignore the file if it exists on the destination - -The default value is Add new versions to the current file. - -Valid values are: - -Append, Ignore, Overwrite - -```yaml -Type: SPUpdateVersions -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreserveDeletedUserMetadataReferences -Attempts to opulates the 'Author' ('Created By') field for items even if the SPUser object was marked as deleted on the destination site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Initialize-SPResourceSecurity.md b/sharepoint/sharepoint-ps/sharepoint-server/Initialize-SPResourceSecurity.md deleted file mode 100644 index 7e4af4f2c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Initialize-SPResourceSecurity.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/initialize-spresourcesecurity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Initialize-SPResourceSecurity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Initialize-SPResourceSecurity - -## SYNOPSIS - -Enforces resource security on the local server. - - - -## SYNTAX - -``` -Initialize-SPResourceSecurity [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Initialize-SPResourceSecurity cmdlet enforces resource security on the local server. -This cmdlet enforces security for all resources, including files, folders, and registry keys. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Initialize-SPResourceSecurity -``` - -This example enforces resource security on the local server. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Initialize-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Initialize-SPStateServiceDatabase.md deleted file mode 100644 index 6c8fcd1da2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Initialize-SPStateServiceDatabase.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/initialize-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Initialize-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Initialize-SPStateServiceDatabase - -## SYNOPSIS -Installs the state database schema into a state service database. - -## SYNTAX - -``` -Initialize-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Initialize-SPStateServiceDatabase cmdlet installs the session state database schema in an empty state service database. -The current user's credentials are used to create the state database schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -$db = Get-SPStateServiceDatabase -Identity StateServceDbName -Initialize-SPStateServiceDatabase -Identity $db -``` - -This example installs the state service database schema into the database associated with the provided identity. - -## PARAMETERS - -### -Identity -Specifies the state service database to initialize. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a state database (for example, StateSvcDB1); or an instance of a valid SPStateServiceDatabase object. - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-FASTSearchAdminDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-FASTSearchAdminDatabase.md deleted file mode 100644 index d6aa3804e4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-FASTSearchAdminDatabase.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-fastsearchadmindatabase -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Install-FASTSearchAdminDatabase ---- - -# Install-FASTSearchAdminDatabase - -## SYNOPSIS -Installs the database used by the Microsoft FAST Search Server 2010 for SharePoint administration services. - -## SYNTAX - -``` -Install-FASTSearchAdminDatabase [-DbConnection <String>] [-DbName <String>] [-DbServer <String>] [-Force] - [-Upgrade <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet installs the database used by the FAST Search Server 2010 for SharePoint administration services. -This cmdlet is primarily called during installation, by the FAST Search Server 2010 for SharePoint installer. - -The administration database default name is "FASTSearchAdminDatabase" and should be located in the Microsoft SQL Server instance specified by the DbServer or DbConnection parameters. - -In addition to performing an initial installation of the database schema, this cmdlet can also: - --- Reinstall (destructively) the database schema if it already exists. --- Upgrade the database schema from an earlier version. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Install-FASTSearchAdminDatabase -DbConnection "Data Source=sqlserver.contoso.com;Database=FASTSearchAdminDatabase;integrated Security=True;" -``` - -This example installs the database schema in the database server specified by the connection string. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Install-FASTSearchAdminDatabase -Upgrade -DbServer "sqlserver.contoso.com" -``` - -This example upgrades the database schema already installed in the FAST Search Server 2010 for SharePoint administration database on the given SQL Server instance. - -### ---------------EXAMPLE 3----------------- (FAST Server for SharePoint 2010) -``` -Install-FASTSearchAdminDatabase -Force -DbServer "sqlserver.contoso.com" -``` - -This example deletes and reinstalls the database schema already installed in the FAST Search Server 2010 for SharePoint administration database on the given SQL Server instance. - -## PARAMETERS - -### -DbConnection -Specifies the database connection string for the FAST Search Server 2010 for SharePoint administration database, in the same format as the ConnectionString property of the System.Data.SqlClient.SqlConnection .NET Framework type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DbName -Specifies the name of the FAST Search Server 2010 for SharePoint administration database. - -The name only takes effect when used in conjunction with the DbServer parameter, not the DbConnection parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DbServer -Specifies the database server instance that contains the FAST Search Server 2010 for SharePoint administration database. - -Only one of the DbServer and DbConnection parameters must be specified. -Using DbServer with a value of sqlserver.contoso.com is equivalent to using DbConnection with the value "Data Source=sqlserver.contoso.com;Database=FASTSearchAdminDatabase;integrated Security=True" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force parameter specifies that the FAST Search Server 2010 for SharePoint administration database already exists, but should be reinstalled. - -This will delete all data that already exists in the database. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Upgrade -Specifies that the FAST Search Server 2010 for SharePoint administration database already exists and that it should be upgraded, because it uses an older version of the database schema. - -The upgrade process will attempt to migrate all data to the new database schema. - -It is strongly recommended that you back up the database before performing this operation. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Uninstall-FASTSearchAdminDatabase](Uninstall-FASTSearchAdminDatabase.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPApp.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPApp.md deleted file mode 100644 index f474987a49..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPApp.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spapp -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPApp -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPApp - -## SYNOPSIS - -Installs an instance of an app. - - - -## SYNTAX - -``` -Install-SPApp -Identity <SPApp> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - -Web <SPWebPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Install-SPApp cmdlet to install an instance of an app within a web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE------------ -``` -$spapp = Import-SPAppPackage -Path .\feature-upgrade-v1.spapp -Site https://site_url -Source ([microsoft.sharepoint.administration.spappsource]::ObjectModel) -Install-SPApp -Web https://site_url -Identity $spapp -``` - -This example installs an app by first importing the app package, and then installing it. - -## PARAMETERS - -### -Identity -Specifies the app to install. -The App object is created by using the Import-SPAppPackage cmdlet. - -```yaml -Type: SPApp -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Web -Specifies the SPWeb object of the app. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Import-SPAppPackage](Import-SPAppPackage.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPApplicationContent.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPApplicationContent.md deleted file mode 100644 index fd4f6ae2c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPApplicationContent.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spapplicationcontent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPApplicationContent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPApplicationContent - -## SYNOPSIS - -Copies shared application data to existing Web application folders. - - - -## SYNTAX - -``` -Install-SPApplicationContent [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The Install-SPApplicationContent cmdlet copies shared application data to existing Web application folders. - -This cmdlet does not take any parameters. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------EXAMPLE-------------------- -``` -Install-SPApplicationContent -``` - -This example copies data to a Web application in the existing folders. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -During a Cummulative Update installation if you face a situation where the full PSConfig cannot run then this cmdlet should be executed on all SharePoint servers to keep the Farm in a supported state. - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPDataConnectionFile.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPDataConnectionFile.md deleted file mode 100644 index cd4f418f2f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPDataConnectionFile.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spdataconnectionfile -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPDataConnectionFile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPDataConnectionFile - -## SYNOPSIS -Installs the provided data connection file. - -## SYNTAX - -``` -Install-SPDataConnectionFile [-Path] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Category <String>] [-Confirm] [-Overwrite] [-WebAccessible] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Install-SPDataConnectionFile cmdlet installs the provided data connection file. -If the specified data connection file exists, the user is prompted to replace the existing file. - -This cmdlet does not create a new file. -Instead, it creates a new data connection file object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Install-SPDataConnectionFile -Path 'C:\folder\sample.udcx' -Category "Install" -WebAccessible $true -``` - -This example uploads a data connection file to a specified category. - -This cmdlet is equivalent to the Upload Data Connection File user interface setting that is located on the Manage Data Connection Files page of the SharePoint Central Administration Web site. - -## PARAMETERS - -### -Path -Specifies the full path to the name of the file in the data connection store. - -The type must be the name of a valid data connection file; for example, C:\foldername\myconnection.udcx. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Category -Sets an arbitrary category on the file which can be used to group the files. -The category name can have a maximum of 255 characters. - -The type must be a valid string value; for example, Category1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Overwrite -Overwrites the existing data connection file. -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebAccessible -Specifies that the universal data connection file can be accessed by using the Web service. -If False, only the Forms Server can retrieve the universal data connection files internally. -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPEduSites.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPEduSites.md deleted file mode 100644 index 69bf5fa604..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPEduSites.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spedusites -applicable: SharePoint Server 2013 -title: Install-SPEduSites -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPEduSites - -## SYNOPSIS -Do not use - -## SYNTAX - -``` -Install-SPEduSites [-WebApplication] <SPWebApplicationPipeBind> [-MySiteHost] <SPSitePipeBind> - [-SearchCenter] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use - -## EXAMPLES - -### Example 1 -``` -Do not use -``` - - - -## PARAMETERS - -### -AssignmentCollection -Do not use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MySiteHost -Do not use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -SearchCenter -Do not use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Do not use - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPWebApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPFeature.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPFeature.md deleted file mode 100644 index 7a88bc9d53..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPFeature.md +++ /dev/null @@ -1,260 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spfeature -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPFeature -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPFeature - -## SYNOPSIS - -Installs a SharePoint Feature by using the Feature.xml file. - - - -## SYNTAX - -### PathSet -``` -Install-SPFeature [-Path] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <Int32>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -### AllExistingFeatures -``` -Install-SPFeature [-AllExistingFeatures] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] - [-SolutionId <String>] [-WhatIf] [<CommonParameters>] -``` - -### ScanForFeatures -``` -Install-SPFeature [-ScanForFeatures] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] - [-SolutionId <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Install-SPFeature cmdlet installs a specific SPFeature by providing, in the Identity parameter, the relative path from the version-specific common FEATURES folder to the feature. -The version-specific FEATURES folder is "$env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\" if the site collection is in 14 mode, and "$env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES\" if the site collection is in 15 mode. -The SharePoint Feature's files must already be put in the proper directory, either manually or by using a solution installer. - -If the value of the AllExistingFeatures parameter is true, the file system is scanned and all new features that are in both FEATURES folders are installed. -This is generally only used during deployment and upgrade. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Install-SPFeature -path "MyCustomFeature" -``` - -This example installs a new feature at $env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES\MyCustomFeature/feature.xml. - -### --------------EXAMPLE 2----------------- -``` -Install-SPFeature -AllExistingFeatures -Whatif -``` - -This example shows the unregistered features that are available on the file system and that are installed if this command is run without the WhatIf parameter. -This is commonly done after an upgrade process. - -### --------------EXAMPLE 3----------------- -``` -Install-SPFeature -path "MyCustomFeature" -CompatibilityLevel 14 -``` - -This example installs a new feature at $env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\MyCustomFeature\feature.xml. - -### --------------EXAMPLE 4----------------- -``` -Install-SPFeature -path "MyCustomFeature" -CompatibilityLevel 15 -``` - -This example installs a new feature at $env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES\MyCustomFeature\feature.xml. - -## PARAMETERS - -### -Path -Specifies an authentic file path; for example, MyFeature. - -The path to feature must be a literal path to the 14\Template\Features directory. -The feature.xml file name is implied and does not need to be provided. - -If the path to the feature is not found , the following error message is displayed: "Failed to find the XML file at location 14\Template\Features\\\<file path\>." - -```yaml -Type: String -Parameter Sets: PathSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AllExistingFeatures -Scans for existing, but unregistered features, and then registers them with the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: AllExistingFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScanForFeatures -Scans and then displays a feature. -The ScanForFeatures parameter does not install a feature. - -```yaml -Type: SwitchParameter -Parameter Sets: ScanForFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of feature to install. -When the version is not specified it will default to the web applications MaxVersion value. - -The values for this can be either 14 or 15. - -```yaml -Type: Int32 -Parameter Sets: PathSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces the installation of an already installed feature. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SolutionId -Specifies the solution ID of the features. -If the SolutionId parameter is not provided, all solution IDs are scanned. - -```yaml -Type: String -Parameter Sets: AllExistingFeatures, ScanForFeatures -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPHelpCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPHelpCollection.md deleted file mode 100644 index cfe5750a64..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPHelpCollection.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-sphelpcollection -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPHelpCollection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPHelpCollection - -## SYNOPSIS - -Installs the provided Help site collection files in the current farm. - - - -## SYNTAX - -### InstallAll -``` -Install-SPHelpCollection [-All] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### InstallOne -``` -Install-SPHelpCollection -LiteralPath <String> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Install-SPHelpCollection cmdlet installs the Help site collection files for SharePoint Products in the current farm. -Use the LiteralPath parameter to install specific custom Help collection files. -If the LiteralPath parameter is not specified, all available Help in the Help site collection is installed and existing Help collection files are overwritten. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Install-SPHelpCollection -LiteralPath 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\HCCab\1033\OSSAdmin.cab' -``` - -This example installs the specified help collection in the current farm. - -## PARAMETERS - -### -All -If the LiteralPath parameter is not specified, specifies that all Help Collection CABs under %Program Files%\Common Files\Microsoft Shared\Web Server Extensions\14\HCCab\\\<LCID\> in the Help site collection are installed, and existing Help collections are overwritten. - -```yaml -Type: SwitchParameter -Parameter Sets: InstallAll -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LiteralPath -Specifies the exact path to a specific custom Help file in the Help site collection cab file. - -The type must be a valid path in either of the following forms: - -- C:\folder_name -- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: InstallOne -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPInfoPathFormTemplate.md deleted file mode 100644 index 418c42aa87..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPInfoPathFormTemplate - -## SYNOPSIS -Installs an InfoPath form template on a farm. - -## SYNTAX - -``` -Install-SPInfoPathFormTemplate [-Path] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-EnableGradualUpgrade] [-NoWait] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Install-SPInfoPathFormTemplate cmdlet installs an InfoPath form template on a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - - -### ---------------EXAMPLE 1-------------- -``` -Install-SPInfoPathFormTemplate -Path c:\Form.xsn -``` - -This example installs a single form template to the farm. - -### ---------------EXAMPLE 2-------------- -``` -"FormTemplateFirst.xsn", "FormTemplateSecond.xsn", "FormTemplateThird.xsn" | Install-SPInfoPathFormTemplate -``` - -This example installs multiple form templates on a farm. - -## PARAMETERS - -### -Path -Specifies the path and name of the form template to install. - -The type must be a valid path and file name of a form template, in the form: - -- C:\folder_name\formtemplate_name -- \\\\server_name\folder_name\formtemplate_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableGradualUpgrade -Specifies that the new form can be gradually upgraded. - -- If specified and the form template file exists, the form template is gradually upgraded and is then used for new sessions only. -- If not specified and the form template does not exist, the form is overwritten during an upgrade and is then used for exisiting and new sessions. -- If specified and the form template file does not exist, ignore the switch. -- If not specified and the file exists, the user is prompted to upgrade and to use the gradual upgrade if the upgrade is allowed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoWait -Specifies that the form template is installed in the background and that the progress of the installation not be shown. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPService.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPService.md deleted file mode 100644 index 20f9b44ebb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPService.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPService - -## SYNOPSIS - -Installs and provisions services on a farm. - - - -## SYNTAX - -``` -Install-SPService [-AssignmentCollection <SPAssignmentCollection>] [-Provision] [<CommonParameters>] -``` - -## DESCRIPTION -The Install-SPService cmdlet installs and optionally provisions services on a farm. -This cmdlet installs all services, service instances, and service proxies specified in the registry on the local server computer. -Use this cmdlet in a script that you build to install and deploy a SharePoint farm or to install a custom developed service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Install-SPService -``` - -This example installs all services, service instances and service proxies specified in the registry on the local server computer. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Provision -Specifies default settings when installing a standalone service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPSolution.md deleted file mode 100644 index 01b660e47d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPSolution.md +++ /dev/null @@ -1,369 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spsolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPSolution - -## SYNOPSIS - -Deploys an installed SharePoint solution in the farm. - - - -## SYNTAX - -### Deploy -``` -Install-SPSolution [-Identity] <SPSolutionPipeBind> [-AllWebApplications] - [-AssignmentCollection <SPAssignmentCollection>] [-CASPolicies] [-CompatibilityLevel <String>] [-Confirm] - [-Force] [-FullTrustBinDeployment] [-GACDeployment] [-Language <UInt32>] [-Local] [-Time <String>] - [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -### Synchronize -``` -Install-SPSolution [[-Identity] <SPSolutionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Language <UInt32>] [-Synchronize] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://docs.microsoft.com/powershell/scripting/developer/cmdlet/cmdlet-parameter-sets?view=powershell-5.1). - -The Install-SPSolution cmdlet deploys an installed SharePoint solution in the farm. -Use the Add-SPSolution cmdlet to install a SharePoint solution package in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Install-SPSolution -Identity contoso_solution.wsp -GACDeployment -``` - -This example deploys the installed SharePoint solution contoso_solution.wsp in the farm and specifies that GAC can be deployed for the new SharePoint solution. - -### ------------------EXAMPLE 2------------------ -``` -Install-SPSolution -Identity contoso_solution.wsp -GACDeployment -CompatibilityLevel {14,15} -``` - -This example deploys the installed SharePoint solution installs a previously added solution so it can be used correctly in both 14 and 15 mode site collections. - -## PARAMETERS - -### -Identity -Specifies the SharePoint solution to deploy. - -The value must be an authentic GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; an authentic name of a SharePoint solution (for example, SPSolution1); or an instance of an authentic SPSolution object. - -```yaml -Type: SPSolutionPipeBind -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -```yaml -Type: SPSolutionPipeBind -Parameter Sets: Synchronize -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AllWebApplications -Specifies that the new SharePoint solution is deployed for all SharePoint web applications in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CASPolicies -Specifies that code access security (CAS) policies can be deployed for the new SharePoint solution. - -```yaml -Type: SwitchParameter -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel - -Specifies whether to install into the solution, into a specific version directory based on CompatibilityLevel. The default behavior if this parameter is not specified is to install the solution only to the version directory based on the version tracked in the manifest of the solution's cab file. - -Valid values are: - ---14 - ---15 - ---14,15 - -```yaml -Type: String -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces the deployment of the new SharePoint solution. - -```yaml -Type: SwitchParameter -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FullTrustBinDeployment -Specifies that full trust Bin deployment is permitted. -This parameter is to be used if the solution is fully trusted. - -Bin assembly is an assembly installed into the bin directory of the virtual server. -The assembly in the package will have DeploymentTarget=WebApplication attribute set. -For additional information about bin assembly, see Assembly Element - -```yaml -Type: SwitchParameter -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GACDeployment -Specifies that global assembly cache (GAC) can be deployed for the new SharePoint solution. - -```yaml -Type: SwitchParameter -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Specifies a language for the solution when a solution language package is deployed. -If this parameter is not specified, zero ("0") is assumed. -Use zero for solutions that are valid for all languages. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Local -Deploys the solution on the active server. - -```yaml -Type: SwitchParameter -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Synchronize -Synchronizes all solutions or the specified solution in the local farm. - -```yaml -Type: SwitchParameter -Parameter Sets: Synchronize -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Time -Specifies when the solution will be deployed. -The default value is immediate deployment. - -The type must be a valid DateTime value, in the form 2010, 5, 1. - -```yaml -Type: String -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication - -Deploys the SharePoint solution for the specified SharePoint web application. - -The value must be in one of the following forms: - ---An authentic GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh - ---An authentic name of a SharePoint web application (for example, MyOfficeApp1) - ---An instance of an authentic SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: Deploy -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPUserSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPUserSolution.md deleted file mode 100644 index 60491c6478..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPUserSolution.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spusersolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPUserSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPUserSolution - -## SYNOPSIS - -Activates a sandboxed solution in a site collection. - - - -## SYNTAX - -``` -Install-SPUserSolution [-Identity] <SPUserSolutionPipeBind> -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Install-SPUserSolution cmdlet activates a sandboxed solution in a site collection. -A user solution is a sandboxed solution. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE--------------------- -``` -Install-SPUserSolution -Identity contoso_solution.wsp -Site https://sitename -``` - -This example activates the sandboxed solution contoso_solution.wsp in the site https://sitename. - -## PARAMETERS - -### -Identity -Specifies the sandboxed solution to activate. - -The type must be a valid name of a sandboxed solution (for example, UserSolution1); or an instance of a valid SPUserSolution object. - -```yaml -Type: SPUserSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Activates the sandboxed solution for the specified site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPWebPartPack.md b/sharepoint/sharepoint-ps/sharepoint-server/Install-SPWebPartPack.md deleted file mode 100644 index 77bc995fc7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Install-SPWebPartPack.md +++ /dev/null @@ -1,244 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/install-spwebpartpack -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Install-SPWebPartPack -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Install-SPWebPartPack - -## SYNOPSIS - -Installs the specified Web Part package to the specified location. - -## SYNTAX - -### UseFileName -``` -Install-SPWebPartPack [-LiteralPath] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Force] [-GlobalInstall] [-Language <UInt32>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] - [-CompatibilityLevel <String>] [<CommonParameters>] -``` - -### UseName -``` -Install-SPWebPartPack [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] - [-GlobalInstall] [-Language <UInt32>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] - [-CompatibilityLevel <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Install-SPWebPartPack cmdlet installs the Web Part package, at the LiteralPath parameter location, in the local farm. -The Web Part package can be installed in a specific Web application by using the WebApplication parameter. -If a Web application is not specified, the Web Part package is installed in all Web applications. - -Use the Language parameter to specify a package language. - -Use the GlobalInstall parameter to install the package to the global assembly cache (GAC). -Assemblies in the GAC are granted FullTrust permission, which gives this package full access to all system-wide resources. - -Use the Force parameter to install the package to overwrite any existing Web Part package with the same name or installed in the same location. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Install-SPWebPartPack "MyCustomWebPartPack" -LiteralPath "C:\mywebpart.wpp" -GlobalInstall -``` - -This example installs the Web Part Package with the name MyCustomWebPartPack globally in the farm from the path c:/mywebpart.wpp. - -## PARAMETERS - -### -LiteralPath -Specifies the exact path to the Web Part package. - -```yaml -Type: String -Parameter Sets: UseFileName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the Web Part package to install. - -```yaml -Type: String -Parameter Sets: UseName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overwrites any existing Web Part package with the same name or installed in the same location. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GlobalInstall -Installs the Web Part package in the global assembly cache (GAC) rather than in the /bin directory of each Web application. -This installation makes the Web Part globally accessible on the servers. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Specifies the language ID for the Web Part package. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the Web application on which to install the Web Part pack. -If no Web application is specified, the Web Part pack is installed on all Web applications. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. This value sets the initial CompatibilityLevel value for the site collection. When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the web application depending on the SiteCreationMode setting. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md deleted file mode 100644 index 3e3a509635..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/invoke-spprojectactivedirectoryenterpriseresourcepoolsync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync - -## SYNOPSIS -Triggers Active Directory Enterprise Resource Pool synchronization on the specified instance of Project Web App. - -## SYNTAX - -``` -Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync [-Url] <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Active Directory Enterprise Resource Pool synchronization is used to create or update multiple Project Server enterprise resources at the same time. -Project Server enterprise resources can also be automatically activated and deactivated based on group membership in the Active Directory directory service. -For example, new employees in your department can automatically be added as Project Server enterprise resources as long as they are in the Active Directory group selected for synchronization. -Conversely, employees who are removed from the Active Directory group have their Project Server accounts deactivated upon synchronization. - -Enterprise Resource Pool synchronization also updates enterprise resource properties with the most current data from Active Directory. -For example, an employee's name and e-mail address may change because of marriage. -As long as the change is made in Active Directory and the user is in the linked group, the change occurs in the user's Enterprise Resource properties when synchronization occurs. - -The Enterprise Resource Pool can be mapped to a single Active Directory group for synchronization. -However, this Active Directory group can contain nested groups whose members are also synchronized. - -The following actions can occur during the Enterprise Resource Pool synchronization process: - -- A new Project Server enterprise resource and corresponding user account can be created based on an Active Directory account. -- An active Project Server resource/user account can be deactivated. -- An existing Project Server user account's metadata (for example, name, e-mail address, and so on) can be updated if it has changed in Active Directory. -- A previously inactive Project Server resource/user account can be reactivated. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync https://localhost/pwa -``` - -This example triggers an Active Directory Enterprise Resource Pool synchronization for the instance of Project Web App located at https://localhost/pwa. - -## PARAMETERS - -### -Url -Specifies the URL of the Project Web App instance where you want to invoke a synchronization. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync](Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Invoke-SPProjectActiveDirectoryGroupSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Invoke-SPProjectActiveDirectoryGroupSync.md deleted file mode 100644 index 2e75f7960a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Invoke-SPProjectActiveDirectoryGroupSync.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/invoke-spprojectactivedirectorygroupsync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Invoke-SPProjectActiveDirectoryGroupSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Invoke-SPProjectActiveDirectoryGroupSync - -## SYNOPSIS -Manually starts the synchronization job to synchronize Project Server group membership with the specified Active Directory groups. - -## SYNTAX - -``` -Invoke-SPProjectActiveDirectoryGroupSync [-Url] <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -In Project Server permission mode, groups can be created to assign permissions and synced with Active Directory groups to determine group membership. -The Invoke-SPProjectActiveDirectoryGroupSync cmdlet manually starts the job that synchronizes the group membership from Active Directory into Project Server. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------EXAMPLE 1------------------- -``` -Invoke-SPProjectActiveDirectoryGroupSync -Url https://AppServer/pwa -``` - -This example synchronizes group membership for the specified PWA instance. - -## PARAMETERS - -### -Url -Specifies the URL of the Project Web App (PWA) instance where you want to start the Active Directory sync. - -The type must be a valid URL, in the form https://\<ServerName\>/\<PWAName\>. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPProjectPermissionMode](Get-SPProjectPermissionMode.md) - -[Set-SPProjectPermissionMode](Set-SPProjectPermissionMode.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Merge-SPLogFile.md b/sharepoint/sharepoint-ps/sharepoint-server/Merge-SPLogFile.md deleted file mode 100644 index 4637ab5d7b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Merge-SPLogFile.md +++ /dev/null @@ -1,394 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/merge-splogfile -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Merge-SPLogFile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Merge-SPLogFile - -## SYNOPSIS - -Combines trace log entries from all farm computers into a single log file on the local computer. - - - -## SYNTAX - -``` -Merge-SPLogFile -Path <String> [-Area <String[]>] [-AssignmentCollection <SPAssignmentCollection>] - [-Category <String[]>] [-ContextFilter <String[]>] [-Correlation <Guid[]>] [-EndTime <DateTime>] - [-EventID <String[]>] [-ExcludeNestedCorrelation] [-Level <String>] [-Message <String[]>] [-Overwrite] - [-Process <String[]>] [-StartTime <DateTime>] [-ThreadID <UInt32[]>] [<CommonParameters>] -``` - -## DESCRIPTION -The Merge-SPLogFile cmdlet returns records from Unified Logging Service (ULS) trace log files on each farm server that match the criteria, and writes the results to a new log file on the local computer. -If no results are returned, a warning is written to the Windows PowerShell console window. - -We recommend that you filter by using the StartTime and EndTime parameters to optimize performance of this cmdlet. -Some filtering parameters such as Process, Area, Category, EventID and Message support wildcards. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -``` - -This example merges the last hour of log data from all farm computers with no filtering. - -### --------------EXAMPLE 2----------------- -``` -Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Area Search -``` - -This example merges the last hour of log data from the Search area. - -### --------------EXAMPLE 3----------------- -``` -Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Area "SharePoint Foundation","Web Analytics Services" -``` - -This example merges the last hour of log data from the SharePoint Foundation and Web Analytics Services areas. - -### --------------EXAMPLE 4----------------- -``` -Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Level High -``` - -This example merges the log data of level High or higher. - -### --------------EXAMPLE 5----------------- -``` -Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -StartTime "06/09/2008 16:00" -EndTime "06/09/2008 16:15" -``` - -This example merges the log data for events in a particular time range, which is culture-specific to the United States. - -### --------------EXAMPLE 6----------------- -``` -Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Message "*permission changed*" -``` - -This example merges the log data for events with permission changed in the message text. - -### --------------EXAMPLE 7----------------- -``` -Merge-SPLogFile -Overwrite -Path d:\1.log -ContextFilter "name=timer job*" -Area "*search*" -``` - -This example merges the log data for all search timer jobs. - -### --------------EXAMPLE 8----------------- -``` -Merge-SPLogFile -Overwrite -Path d:\2.log -ContextFilter "user=contoso?joeuser" -``` - -This example shows how to merge the log data for all user names that have a contoso\joeuser or Contoso/joeuser format. - -## PARAMETERS - -### -Path -Specifies the path and file name to which to write the merged log file. -Relative paths are supported. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Area -Specifies the area name to filter on. - -The type must be a valid name; for example, SharePoint Foundation. - -The use of wildcards is supported. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Category -Specifies the category ID to filter on. - -The type must be a valid category name; for example, category1. - -The use of wildcards is supported. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContextFilter -Specifies a filter for trace entries in a particular context in the form key=value, for example, user=contoso\joeuser. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Correlation -Specifies the correlation ID to filter on. -The type must be a valid GUID, in the form F0BB0790-4323-A153-096F-ABCDC80E24D4. - -```yaml -Type: Guid[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndTime -Specifies the end time of the log entries returned. - -The type must be a valid DateTime format that is culture-specific to the administrative language, such as 2/16/2007 12:15:12 for English-US. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventID -Specifies the Event ID to filter on. -The use of wildcards is supported. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludeNestedCorrelation -Excludes nested correlation values in the results. -This parameter is only used when filtering results by using the ContextFilter parameter - -By default, records returned from the ContextFilter parameter include all related records in addition to the records that match the filter. -Specifying this option includes only the records that match the filter and excludes any related records. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Level -Specifies the level name to filter on. - -Results include the specified level and everything more severe. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Message -Specifies the message text to filter on. - -The type must be valid text. -Text with spaces should be enclosed with quotation marks; for example, "This is a test." - -The use of wildcards is supported. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Overwrite -Overwrites the log file if it already exists at the specified path. - -The type must be either of the following values: - -- $True -- $False - -The default value is $False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Process -Specifies the process name to filter on. - -The use of wildcards is supported. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartTime -Specifies the start time of the log entries returned. - -The type must be a valid DateTime format that is culture-specific to the administrative language, such as 2/16/2007 12:15:12 for English-US. - -The default is one hour prior to the current time on the local computer. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThreadID -Specifies the thread ID to filter on. - -The type must be a valid integer from 0 through 4,294,967,295. - -```yaml -Type: UInt32[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Merge-SPUsageLog.md b/sharepoint/sharepoint-ps/sharepoint-server/Merge-SPUsageLog.md deleted file mode 100644 index 409ed8a0b1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Merge-SPUsageLog.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/merge-spusagelog -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Merge-SPUsageLog -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Merge-SPUsageLog - -## SYNOPSIS -Returns records from usage log files. - -## SYNTAX - -``` -Merge-SPUsageLog [-Identity] <SPUsageDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-DiagnosticLogPath <String>] [-EndTime <DateTime>] [-OverWrite] [-Partial] [-Servers <String[]>] - [-StartTime <DateTime>] [<CommonParameters>] -``` - -## DESCRIPTION -The Merge-SPUsageLog cmdlet returns records from usage log files on each farm server that match the criteria, and writes the results to pipeline. - -The command gathers, filters, and aggregates logs base on user specified criteria, we recommend that you filter by using the StartTime and EndTime parameters to optimize performance of this cmdlet. - -You should at least specify a usage type. For information on valid usage types, see Get-SPUsageDefinition. - -This cmdlet requires PowerShell Remoting to be enabled. - -## EXAMPLES - -### Example 1 -``` -Merge-SPUsageLog -Identity 'Timer Jobs' -Servers SPSERVER1 -``` - -Merges the Usage log for the Usage Definition 'Timer Jobs' from the specified server and outputs to the PowerShell console. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DiagnosticLogPath -Specifies the file to write diagnostic information to. A relative path is supported. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndTime -Specifies the end time of the log entries returned. - -The type must be a valid DateTime format that is culture-specific to the administrative language, that is, 2/16/2007 12:15:12 for English-US. - -The default value is the current time. - -If you want to specify UTC time, you must add a "Z" to the end of the parameter. For example, "2016-06-15 03:29:18.199 Z". If the "Z" is not specify, local computer time will be displayed instead of UTC. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the name of usage log file. - -```yaml -Type: SPUsageDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -OverWrite -Overwrites the diagnostic log file if it already exists at the specified path. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Partial -Not used. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Servers -The server address or addresses to filter on. - -To obtain a list of valid addresses in the farm use Get-SPServer | Select Address. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartTime -Specifies the start time of the log entries returned. - -The type must be a valid DateTime format that is culture-specific to the administrative language, such as "2/16/2007 12:15:12" for English-US. - -The default value is one hour prior to the current time on the local computer. - -If you want to specify UTC time, you must add a "Z" to the end of the parameter. For example, "2016-06-15 03:29:18.199 Z". If the "Z" is not specify, local computer time will be displayed instead of UTC. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPUsageDefinitionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPDatabase.md deleted file mode 100644 index 7b93c2e06f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPDatabase.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/migrate-spdatabase -applicable: SharePoint Server 2016 -title: Migrate-SPDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Migrate-SPDatabase - -## SYNOPSIS -Do not use. - -## SYNTAX - -### SiteSubscription -``` -Migrate-SPDatabase [-Identity] <SPDatabasePipeBind> [-DestinationDatabase] <SPContentDatabasePipeBind> - [-SiteSubscription] <SPSiteSubscriptionPipeBind> [-ServiceType] <ServiceExtensionType> [-Overwrite] - [-UseLinkedSqlServer] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -### SiteCollection -``` -Migrate-SPDatabase [-Identity] <SPDatabasePipeBind> [-SiteCollection] <SPSitePipeBind> - [-ServiceType] <ServiceExtensionType> [-Overwrite] [-UseLinkedSqlServer] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use. - -## EXAMPLES - -### Example 1 -``` -#Do not use. -``` - -Do not use. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DestinationDatabase -Do not use. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2016 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Do not use. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Overwrite -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceType -Do not use. - -```yaml -Type: ServiceExtensionType -Parameter Sets: (All) -Aliases: -Accepted values: DefaultDatabase, Project, UserProfile, SiteSubscription, BDC, Securityobjects, Taxonomy, AppManagement, All -Applicable: SharePoint Server 2016 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Do not use. - -```yaml -Type: SPSitePipeBind -Parameter Sets: SiteCollection -Aliases: -Applicable: SharePoint Server 2016 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Do not use. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2016 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseLinkedSqlServer -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPProjectDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPProjectDatabase.md deleted file mode 100644 index 233f1eeab6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPProjectDatabase.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/migrate-spprojectdatabase -applicable: Project Server 2016, Project Server 2019 -title: Migrate-SPProjectDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Migrate-SPProjectDatabase - -## SYNOPSIS -Copies the data from the Project Server 2013 database into the corresponding SharePoint Server 2016, SharePoint Server 2019 content database containing the migrated site collection. - -## SYNTAX - -``` -Migrate-SPProjectDatabase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] -DatabaseName <String> - [-DatabaseServer <String>] [-FailoverPartner <String>] [-Overwrite] [-SQLLogon <PSCredential>] - -SiteCollection <SPSitePipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Copies the data from the Project Server 2013 database into the corresponding SharePoint Server 2016, SharePoint Server 2019 content database containing the migrated site collection. - -Both the Project Server 2013 database and the SharePoint Server 2016, SharePoint Server 2019 database must be on the same instance of SQL -Server and the SharePoint farm account must have full access to the Project Server 2013 database. During the migration process the Project Server 2013 database will be modified and cannot be mounted back to a Project Server 2013. -## EXAMPLES - -### Example 1 -``` -Migrate-SPProjectDatabase -Name ProjectDB1 -SiteCollection "https://contoso1/sites/PWA" -``` - -This example will look for a Project Server 2013 database named ProjectDB1 on the same instance of SQL Server where the content database containing https://contoso1/sites/PWA is located. The data will be upgraded and copied into the site collection. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -The name of the Project Server 2013 database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -The name of the instance of SQL Server hosting the Project Server 2013 database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverPartner -The name of the SQL Server failover partner for the Project Server 2013 database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Overwrite -Specifies to overwrite any Project data from previous attempts. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SQLLogon -SQL Server authentication credentials if needed. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -The URL of the site collection to which you want to copy the Project data. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPProjectResourcePlans.md b/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPProjectResourcePlans.md deleted file mode 100644 index 874db2b144..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Migrate-SPProjectResourcePlans.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/migrate-spprojectresourceplans -applicable: Project Server 2016, Project Server 2019 -title: Migrate-SPProjectResourcePlans -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Migrate-SPProjectResourcePlans - -## SYNOPSIS -Migrates the published resource plan assignment data to engagements. Run after data migration has been completed from Project Server 2013 to Project Server 2016, Project Server 2019. - -## SYNTAX - -``` -Migrate-SPProjectResourcePlans [-Url] <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Migrates the published resource plan assignment data to engagements. Run after data migration has been completed from Project Server 2013 to Project Server 2016, Project Server 2019. - -## EXAMPLES - -### Example 1 -``` -Migrate-SPProjectResourcePlans -Url https://pwa_site -``` -Migrates the Project Resource Plans on the Project Web App site https://pwa_site. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -The URL of the Project Web App site. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPContentDatabase.md deleted file mode 100644 index 40dc2f3763..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPContentDatabase.md +++ /dev/null @@ -1,404 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/mount-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Mount-SPContentDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Mount-SPContentDatabase - -## SYNOPSIS - -Attaches an existing content database to the farm. - - - -## SYNTAX - -``` -Mount-SPContentDatabase [-Name] <String> [-WebApplication] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-AssignNewDatabaseId] [-ChangeSyncKnowledge] [-Confirm] - [-ClearChangeLog] [-DatabaseCredentials <PSCredential>] [-DatabaseServer <String>] [-MaxSiteCount <Int32>] - [-NoB2BSiteUpgrade] [-SkipIntegrityChecks] [-WarningSiteCount <Int32>] [-WhatIf] - [-DatabaseAccessCredentials <PSCredential>] [-DatabaseFailoverServer <String>] [-SkipSiteUpgrade] - [-UseLatestSchema] [<CommonParameters>] -``` - -## DESCRIPTION -The Mount-SPContentDatabase cmdlet attaches an existing content database to the farm. -If the database being mounted requires an upgrade, this cmdlet will cause the database to be upgraded. - -The default behavior of this cmdlet causes an upgrade of the schema of the database and initiates upgraded builds for all site collections within the specified content database if required. -To prevent initiation of upgraded builds of site collections, use the NoB2BSiteUpgrade parameter. -This cmdlet does not trigger version-to-version upgrade of any site collections. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE 1--------------------- -``` -Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication https://sitename -``` - -This example mounts an existing database to the sitename web application. -If upgrades are required, it triggers database schema upgrade and then performs only build-to-build upgrade actions on existing site collections if required. -This operation does not changed the CompatibilityLevel for existing site collections in this database. - -### -----------------EXAMPLE 2--------------------- -``` -Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication https://sitename -NoB2BSiteUpgrade -``` - -This example mounts an existing database to the sitename web application but it prevents any site upgrades from occurring. -If upgrades are required, it triggers database schema upgrades only and no build-to-build upgrade actions are performed on any site collections. -This operation does not change the CompatibilityLevel for existing site collections in this database. - -## PARAMETERS - -### -Name -Specifies the existing content database to attach to the farm. - -The type must be a valid name of a SharePoint content database; for example, SPContentDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Attaches the content database to the specified SharePoint web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignNewDatabaseId -Creates a new database ID automatically when the content database is attached. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChangeSyncKnowledge -Database attach will cause all Groove sync client to re-synchronize their content. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClearChangeLog -Clears any pending changes from the change log in the content database. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the content database specified in the Name parameter. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSiteCount -Specifies the maximum number of web sites that can use the content database. - -The type must be a positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UpdateUserExperience -Determines whether the content databases should upgrade to the latest user interface. By default, the user interface will not change during upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - - -### -NoB2BSiteUpgrade -Specifies not to upgrade all child objects when performing a build-to-build upgrade. -This parameter has no effect when a version-to-version upgrade is specified. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipIntegrityChecks -Specifies the upgrade process not to run the internal integrity checks such as missing templates, and orphan detection as part of the upgrade process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarningSiteCount -Specifies the number of sites that can be created before a warning event is generated and the owner of the site collection is notified. - -The type must be a positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseAccessCredentials -Specifies the credential that belong to SPDataAccess role. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseFailoverServer -Specifies the name of the database server to be mirrored. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipSiteUpgrade -Specifies to not upgrade all site objects when performing upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: NoB2BSiteUpgrade -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseLatestSchema -Specifies to use the latest schema. In an on-premises environment, this parameter has no effect. - -There are two values $True and $False. - -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPSiteMapDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPSiteMapDatabase.md deleted file mode 100644 index 98c2ca3cae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPSiteMapDatabase.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/mount-spsitemapdatabase -applicable: SharePoint Server 2016 -title: Mount-SPSiteMapDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Mount-SPSiteMapDatabase - -## SYNOPSIS -Mounts a Site Map database. Do not use. - -## SYNTAX - -``` -Mount-SPSiteMapDatabase [-DatabaseName] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DatabaseCredentials <PSCredential>] [-DatabaseFailoverServer <String>] -DatabaseServer <String> [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Do not use. - -## EXAMPLES - -### Example 1 -``` -#Do not use. -``` - -Do not use. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Do not use. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseFailoverServer -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPStateServiceDatabase.md deleted file mode 100644 index aac2e19cd4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Mount-SPStateServiceDatabase.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/mount-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Mount-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Mount-SPStateServiceDatabase - -## SYNOPSIS -Attaches an existing state service database to the farm. - -## SYNTAX - -``` -Mount-SPStateServiceDatabase [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseCredentials <PSCredential>] [-DatabaseServer <String>] - [-ServiceApplication <SPStateServiceApplicationPipeBind>] [-Weight <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The Mount-SPStateServiceDatabase cmdlet attaches an existing state service database to the farm. -If the session state database schema is not installed in the state service database, use the Initialize-SPStateServiceDatabase cmdlet to install the schema after the state service database has been mounted. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Mount-SPStateServiceDatabase -Name "statedata1" -DatabaseServer "localhost" -``` - -This example associates a SharePoint Server farm with a SQL Server database. - -This example is used in least privilege scenarios when an administrator cannot create databases in SQL. -The database must already exist and be empty. -The database cannot be used until the Initialize-SPStateServiceDatabase cmdlet is run, so errors could occur with this example. - -### --------------EXAMPLE 2----------------- -``` -Mount-SPStateServiceDatabase -Name "statedata1" -DatabaseServer "localhost" -ServiceApplication "ServiceApp1" -Weight 10 | Initialize-SPStateServiceDatabase -``` - -This example associates a SharePoint Server farm with a SQL Server database, at the same time that it also associates the database with a service application and gives a weight of 10. -The result is immediately piped to the Initialize-SPStateServiceDatabase cmdlet so that the database can be used. - -## PARAMETERS - -### -Name -Specifies the database name that is created in the SQL Server database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the database credentials for SQL Authentication used to access the state service database. -If this parameter is not specified, Windows authentication is used. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the state service database. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the state service application to which to add the state database. - -The type must be a valid name of a state service application (for example, StateServiceApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPStateServiceApplication object. - -```yaml -Type: SPStateServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Weight -Specifies the weight for the state database used to load balance the allocation of new data. -The default value is 1. - -The type must be a valid integer in the range of 1 to 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPAppManagementData.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPAppManagementData.md deleted file mode 100644 index f6860ffdc8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPAppManagementData.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spappmanagementdata -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPAppManagementData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPAppManagementData - -## SYNOPSIS -Do Not Use - -## SYNTAX - -``` -Move-SPAppManagementData [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-OverWrite] - -SiteSubscriptionId <Guid> -SourceAppManagementDatabase <SPDatabasePipeBind> - -TargetContentDatabase <SPContentDatabasePipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Do Not Use - -## EXAMPLES - -### Example 1 -``` -Do Not Use -``` - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverWrite -Do Not Use - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptionId -Do Not Use -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceAppManagementDatabase -Do Not Use -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetContentDatabase -Do Not Use - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPBlobStorageLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPBlobStorageLocation.md deleted file mode 100644 index b4600690cd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPBlobStorageLocation.md +++ /dev/null @@ -1,212 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spblobstoragelocation -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPBlobStorageLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPBlobStorageLocation - -## SYNOPSIS - -Copies a content database to a new location by using Remote BLOB Storage (RBS). - - - -## SYNTAX - -``` -Move-SPBlobStorageLocation [-SourceDatabase] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DestinationDatabase <String>] [-DestinationDataSourceInstance <String>] [-Dir <String>] - [-VerboseMod <Boolean>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Move-SPBlobStorageLocation cmdlet to use Remote BLOB Storage (RBS) to copy a content database to an instance of a SQL Server database. -The database size limitation for SQL Server is 4 gigabytes (GB). -If a content database is greater than 4 GB, the database cannot be copied directly to a SQL Server database instance. -The Move-SPBlobStorageLocation cmdlet uses the advantage of RBS and copies databases larger than 4 GB. -RBS stores the data on the local hard disk and keeps the links to the data in the database, which results in a smaller database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------EXAMPLE 1----------------------- -``` -Move-SPBlobStorageLocation WSS_Content -``` - -This example copies the content database named WSS_Content from the Windows Internal Database to the same database name in SQL Server 2008 Express by using RBS. - -### -------------------EXAMPLE 2----------------------- -``` -Move-SPBlobStorageLocation WSS_Content -DestinationDatabase WSS_V4_Content -BackupDatabase WSSBackupDB -VerboseMod:$true -``` - -This example copies the content database named WSS_Content from the Windows Internal Database to a database in SQL Server 2008 Express. -The name of the new database will be WSS_V4_Content. -During the move, the backup file name will be WSSBackupDB. -The output of this command displays log information to the Command Prompt window. - -## PARAMETERS - -### -SourceDatabase -Specifies the name of the Windows Internal Database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DestinationDatabase -Specifies the name of the migrated database. -If the DestinationDatabase parameter is not specified, the SourceDatabase parameter is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DestinationDataSourceInstance -Specifies the name of the instance of the destination database. -The value in the SourceDatabase parameter is migrated to this instance. -The name of the instance of the database should be SQL Server with Service Pack 1 (SP1) and Cumulative Update 2 version or higher. -If the DestinationDataSourceInstance parameter is not specified, the local host name is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Dir -Used for all disk operations, including storing temporary backups and database (.mdf) files of a migrated database. -If the Dir parameter is not specified, a default directory of the destination SQL Server instance is used. -The free space in this directory should be at least two times the size of the source database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VerboseMod -Generates verbose log output to be displayed in the Command Prompt window. -If the VerboseMod parameter is not specified, no output is displayed. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPDeletedSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPDeletedSite.md deleted file mode 100644 index cdb3cf2315..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPDeletedSite.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spdeletedsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPDeletedSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPDeletedSite - -## SYNOPSIS - -Moves deleted site collections from one content database to another. - - - -## SYNTAX - -``` -Move-SPDeletedSite [-Identity] <SPDeletedSitePipeBind> -DestinationDatabase <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-ContentDatabase <SPContentDatabasePipeBind>] - [-RbsProviderMapping <Hashtable>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Move-SPDeletedSite cmdlet to move data in a specified site collection from its current content database to the content database specified by the DestinationDatabase parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------EXAMPLE---------- -``` -Move-SPDeletedSite -Identity 610857cb-8414-4a89-8bf3-ad3628f6c86c -DestinationDatabase "ContentDB2" -``` - -This example moves deleted site collections from the specified GUID to the database named "ContentDB2". - -## PARAMETERS - -### -Identity -Specifies the identity of the site collection to be moved. -For example, https://servername/sites/sitename. - -```yaml -Type: SPDeletedSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DestinationDatabase -Specifies the content database that the site collection should be moved to. -For example, ContentDB2. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the SQL Server content database where the site collection data will be stored. -If no content database is specified, the content database with the greatest unused site collection capacity and whose database status is ready will be used. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RbsProviderMapping -Used to move a Remote BLOB Storage (RBS)-enabled site collection from one RBS-enabled content database to another RBS-enabled content database without moving the underlying Binary Large Object (BLOB) content. -If the content database has more than one RBS provider associated with it, you must specify all providers. -The same providers must be enabled on the target content database and the source content database. - -```yaml -Type: Hashtable -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the Web application from which to list sites. - -The type must be a valid URL in the form https://server_name; a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh; or the Web application name, for example, WebApplication1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPEnterpriseSearchLinksDatabases.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPEnterpriseSearchLinksDatabases.md deleted file mode 100644 index fdfe6b0ccd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPEnterpriseSearchLinksDatabases.md +++ /dev/null @@ -1,217 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spenterprisesearchlinksdatabases -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPEnterpriseSearchLinksDatabases -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPEnterpriseSearchLinksDatabases - -## SYNOPSIS -Moves data across links databases. - -## SYNTAX - -``` -Move-SPEnterpriseSearchLinksDatabases [-SearchApplication] <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-RepartitioningId <Guid>] - [-SourceStores <LinksStore[]>] [-TargetStores <LinksStore[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Move-SPEnterpriseSearchLinksDatabases cmdlet moves data across a given list of links databases during farm configuration and scale out, to improve the performance and resource load of the farm. -Once the move has started, the cmdlet will return a unique identifier, the RepartitioningId. -Use this identifier to retrigger if the current run fails. -After the move has finished, the old databases can be removed. - -A links database stores query logging and analytics information. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------EXAMPLE-------- -``` -$ssa = Get-SPEnterpriseSearchServiceapplication -$ssa | New-SPEnterpriseSearchLinksDatabase -DatabaseName "links1" -$ssa | New-SPEnterpriseSearchLinksDatabase -DatabaseName "links2" -$ssa | New-SPEnterpriseSearchLinksDatabase -DatabaseName "links3" -$dbs = $ssa | Get-SPEnterpriseSearchLinksDatabase -$ssa | Move-SPEnterpriseSearchLinksDatabases -TargetStores $dbs -``` - -This example adds 3 new links databases and uses Move-SPEnterpriseSearchLinksDatabases to move data from the current links databases into new databases. - -## PARAMETERS - -### -SearchApplication - -Specifies the search application that contains the links database. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -Specifies the search application that contains the links database. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RepartitioningId - -Resumes the move with this identifier. - - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceStores - -Specifies a source list of databases. -If this parameter is not specified then all currently existing links databases will be used as a source list. - - - -```yaml -Type: LinksStore[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStores - -Specifies a target list of databases. -If this parameter is not specified then all currently existing links databases will be used as a target list. - - - -```yaml -Type: LinksStore[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216 (https://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchLinksDatabase](New-SPEnterpriseSearchLinksDatabase.md) - -[Set-SPEnterpriseSearchLinksDatabase](Set-SPEnterpriseSearchLinksDatabase.md) - -[Get-SPEnterpriseSearchLinksDatabase](Get-SPEnterpriseSearchLinksDatabase.md) - -[Remove-SPEnterpriseSearchLinksDatabase](Remove-SPEnterpriseSearchLinksDatabase.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPProfileManagedMetadataProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPProfileManagedMetadataProperty.md deleted file mode 100644 index 11f0b8a3b2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPProfileManagedMetadataProperty.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spprofilemanagedmetadataproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPProfileManagedMetadataProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPProfileManagedMetadataProperty - -## SYNOPSIS -Moves multiple-string values into a term set. - -## SYNTAX - -``` -Move-SPProfileManagedMetadataProperty -Identity <String> - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-AvailableForTagging] [-Confirm] [-TermSetName <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Move-SPProfileManagedMetadataProperty cmdlet to move multiple-string or single-string property values into a term set that you specify. -If you do not specify a term set, the values are moved into the Keywords term set. -Any new values you add to the property after running the cmdlet will be moved into the term set that you specified. - -After a user profile application has been upgraded from Office SharePoint Server, single-string and multiple-string value properties are not available for use unless the Move-SPProfileManagedMetadataProperty cmdlet is run to map them to term sets within Managed Metadata Service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE------------------ -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Move-SPProfileManagedMetadataProperty -ProfileServiceApplicationProxy $proxy -Identity SPS-Interests -TermSetName Interests -AvailableForTagging -``` - -This example moves values from the SPS-Interests property into a new term set called Interests and marks that term set as available for tagging. - -## PARAMETERS - -### -Identity -Specifies the name of the profile property that needs to be migrated to the taxonomy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the name of the User Profile Service Application Proxy to use. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AvailableForTagging -Determines whether the terms in the resulting term set can be used for Managed Metadata tagging. -If a term set has more than 30,000 terms, using it for Managed Metadata tagging may lead to performance issues on the client computer. -Because a majority of the profile properties may have more than 30,000 terms, the default value is No. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TermSetName -When specified, the term set name is created. -If the TermSetName parameter is not specified, the property is mapped to the Keywords term set in Managed Metadata Service. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPSite.md deleted file mode 100644 index 05c62962dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPSite.md +++ /dev/null @@ -1,218 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPSite - -## SYNOPSIS - -Moves site collections from one content database to another. - - - -## SYNTAX - -``` -Move-SPSite [-Identity] <SPSitePipeBind> -DestinationDatabase <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-RbsProviderMapping <Hashtable>] [-WhatIf] - [-CopyEvents <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION - -The Move-SPSite cmdlet moves the data in the specified site collection from its current content database to the content database specified by the DestinationDatabase parameter. - -A no-access lock is applied to the site collection to prevent users from altering data within the site collection while the move is taking place. - -Once the move is complete, the site collection is returned to its original lock state. - -An IIS reset is required for the site move to take effect. - -The destination content database specified must already exist, must be attached to the same SQL Server as the site collection's current content database, and must be attached to the site collection's current Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ---------------------EXAMPLE 1----------------------- -``` -Move-SPSite https://servername/sites/sitename -DestinationDatabase ContentDb2 -``` - -This example moves the site collection https://servername/sites/sitename to the content database ContentDb2. - -### ---------------------EXAMPLE 2----------------------- -``` -Get-SPSite -ContentDatabase ContentDb1 | Move-SPSite -DestinationDatabase ContentDb2 -``` - -This example moves all site collections in ContentDb1 to ContentDb2. - -### ---------------------EXAMPLE 3----------------------- -``` -Get-SPSiteAdministration | where { $_.OwnerLoginName -eq "DOMAIN\username" } | Move-SPSite -DestinationDatabase ContentDb2 -``` - -This example moves all site collections where DOMAIN\username is the site collection owner to ContentDb2. -The Get-SPSiteAdministration cmdlet is used instead of the Get-SPSite cmdlet because you must have permission within the site collection to access the properties of the SPSite object. -You can access the properties of the SPSiteAdministration object as a SharePoint farm administrator. - -### ---------------------EXAMPLE 4----------------------- -``` -Move-SPSite -Identity siteUrl -DestinationDatabase databaseName -RbsProviderMapping - @{"sourceProvider1"="targetProvider1", "sourceProvider2"="targetProvider2"} -``` - -This example moves an RBS-enabled site collection from one RBS-enabled content database to another RBS-enabled content database, sourceProvider1 is the source RBS provider and targetProvider1 is the target RBS provider. - -## PARAMETERS - -### -Identity -Specifies the identity of the site collection to be moved. -For example, https://servername/sites/sitename. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DestinationDatabase -Specifies the content database that the site collection should be moved to. -For example, ContentDB2. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RbsProviderMapping -This parameter was added in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Used to move an RBS-enabled site collection from one RBS-enabled content database to another RBS-enabled content database without moving the underlying BLOB content. -If the content database has more than one RBS provider associated with it, you must specify all providers. -The same providers must be enabled on the target content database and the source content database. - -```yaml -Type: Hashtable -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CopyEvents -Specifies if events need to be copied. - -The valid values are True or False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPSocialComment.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPSocialComment.md deleted file mode 100644 index d9ccebf077..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPSocialComment.md +++ /dev/null @@ -1,180 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spsocialcomment -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPSocialComment -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPSocialComment - -## SYNOPSIS -Moves social comments. - -## SYNTAX - -``` -Move-SPSocialComment [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-NewUrl <String>] - [-OldUrl <String>] -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server 2010 with Service Pack 1 (SP1) and SharePoint Foundation 2010 with Service Pack 1 (SP1). - -Use the Move-SPSocialComment cmdlet to move social comments from one page to another page. - -This cmdlet does not move Tags or Ratings. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference (https://go.microsoft.com/fwlink/p/?LinkId=671715). - -## EXAMPLES - -### Example 1 -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Move-SPSocialComments -ProfileServiceApplicationProxy $proxy -OldUrl "https://contoso/Pages/oldtest.aspx" -NewUrl "https://contoso/Pages/newtest.aspx" -``` - -This example moves social comments from oldtest.aspx to newtest.aspx. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewUrl -Specifies the target URI to which the social notes will be moved. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OldUrl -Specifies the source URI from which the social notes will be moved. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the proxy of the User Profile Service application that contains the site subscription to delete.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application proxy (for example, UserProfileSvcProxy1); or an instance of a valid SPServiceApplicationProxy object. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. - -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationProxyPipeBind -Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPUser.md b/sharepoint/sharepoint-ps/sharepoint-server/Move-SPUser.md deleted file mode 100644 index 968a62e864..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Move-SPUser.md +++ /dev/null @@ -1,180 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/move-spuser -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Move-SPUser -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Move-SPUser - -## SYNOPSIS - -Migrates a user account in SharePoint Products. - - - -## SYNTAX - -``` -Move-SPUser [-Identity] <SPUserPipeBind> -NewAlias <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-IgnoreSID] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Move-SPUser cmdlet migrates user access from one domain user account to another. -If an entry for the new login name already exists, the entry is marked for deletion to make way for the migration. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$user = Get-SPUser -Identity "DOMAIN\JaneDoe" -Web https://webUrl -Move-SPUser -Identity $user -NewAlias "Domain\JaneSmith" -IgnoreSid -``` - -This example migrates DOMAIN\JaneDoe to the new account of DOMAIN\JaneSmith. - -### ------------------EXAMPLE 2------------------ -``` -$user = Get-SPUser -Identity "DomainA\JaneDoe" -Web https://webUrl -Move-SPUser -Identity $user -NewAlias "DomainB\JaneDoe" -``` - -This example migrates DOMAIN\JaneDoe from DomainA to the new account of DOMAINB\JaneDoe in DomainB with SID History enabled. - -### ------------------EXAMPLE 3------------------ -``` -$user = Get-SPUser -Identity "i:0#.w|DOMAIN\JaneDoe" -Web https://webUrl -Move-SPUser -Identity $user -NewAlias "i:0#.w|Domain\JaneSmith" -IgnoreSid -``` - -This example migrates DOMAIN\JaneDoe to the new account of DOMAIN\JaneSmith when using Windows Claims. `-IgnoreSid` must always be used with `Move-SPUser` when using a Claims Identity, such as Windows Claims. - -## PARAMETERS - -### -Identity -Specifies the `SPUser` object retrieved via `Get-SPUser`. - -The type must be a valid `SPUser` object. - -```yaml -Type: SPUserPipeBind -Parameter Sets: (All) -Aliases: UserAlias -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NewAlias -Specifies the new login name of the user account. - -The type must be a valid login name, in the form DOMAIN\username. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreSID -Indicates (if present) that Active Directory will not be queried for the SID history attribute to ensure that the new login name is correspondent to the old login name. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchContentCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchContentCollection.md deleted file mode 100644 index ec924fa921..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchContentCollection.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchcontentcollection -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchContentCollection ---- - -# New-FASTSearchContentCollection - -## SYNOPSIS -Creates a new Microsoft FAST Search Server 2010 for SharePoint content collection. - -## SYNTAX - -``` -New-FASTSearchContentCollection [-Name] <String> [[-Description] <String>] [[-Pipeline] <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new FAST Search Server 2010 for SharePoint content collection. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchContentCollection -Name newscollection -``` - -This example creates a new FAST Search Server 2010 for SharePoint content collection named "newscollection". - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchContentCollection -Name newscollection -Description "A collection for news content" -``` - -This example creates a new content collection named "newscollection", and attaches a description to it. - -### ---------------EXAMPLE 3----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchContentCollection -Name newscollection -Description "A collection for news content" -Pipeline "Office14 (webcluster)" -``` - -This example creates a new content collection, and uses the FAST Search Server 2010 for SharePoint document processing pipeline "Office14 (webcluster)" to feed content to the content collection. - -## PARAMETERS - -### -Name -The name of the FAST Search Server 2010 for SharePoint content collection to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A description of the content collection to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Pipeline -The FAST Search Server 2010 for SharePoint document processing pipeline used to feed content to the content collection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-FASTSearchContentCollection](Clear-FASTSearchContentCollection.md) - -[Remove-FASTSearchContentCollection](Remove-FASTSearchContentCollection.md) - -[Get-FASTSearchContentCollection](Get-FASTSearchContentCollection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCategory.md deleted file mode 100644 index 1cfaa6581c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCategory.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchmetadatacategory -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchMetadataCategory ---- - -# New-FASTSearchMetadataCategory - -## SYNOPSIS -Creates a new category for crawled properties. - -## SYNTAX - -``` -New-FASTSearchMetadataCategory -Name <String> -Propset <Guid> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new category for crawled properties. -A category is identified by its name and its property set global unique identifier (GUID). - -All crawled properties that are members of a category share the same property set GUID as the category. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$guid = [guid]::NewGuid() -New-FASTSearchMetadataCategory -Name ExampleCategory -Propset $guid -``` - -This example creates a category named "ExampleCategory" with a new GUID generated by the system. -New crawled properties can then be mapped to this category by specifying the GUID when calling New-FASTSearchMetadataCrawledProperty or Set-FASTSearchMetadataCrawledProperty. - -See Set-FASTSearchMetadataCategory for descriptions of category properties. - -## PARAMETERS - -### -Name -The name of the new category. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Propset -The property set Global Unique Identifier (GUID) assigned to this category. -A GUID is a 128-bit integer that has a very low probability of being duplicated. -The GUID can be specified either in the form of a System.Guid object, or as a 128-bit integer with the format "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx". -A crawled property can only be mapped to one category at a time. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataCategory](Get-FASTSearchMetadataCategory.md) - -[Remove-FASTSearchMetadataCategory](Remove-FASTSearchMetadataCategory.md) - -[Set-FASTSearchMetadataCategory](Set-FASTSearchMetadataCategory.md) - -[New-FASTSearchMetadataCrawledProperty](New-FASTSearchMetadataCrawledProperty.md) - -[Set-FASTSearchMetadataCrawledProperty](Set-FASTSearchMetadataCrawledProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledProperty.md deleted file mode 100644 index 01165053b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledProperty.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchmetadatacrawledproperty -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchMetadataCrawledProperty ---- - -# New-FASTSearchMetadataCrawledProperty - -## SYNOPSIS -Creates a new crawled property. - -## SYNTAX - -``` -New-FASTSearchMetadataCrawledProperty -Name <String> -Propset <Guid> -VariantType <Int32> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new crawled property. -A crawled property is a piece of metadata extracted from content sources and fed to the Microsoft FAST Search Server 2010 for SharePoint system. -For example, the title of a Web page would normally be a crawled property. - -A crawled property is uniquely defined by three properties: - --- The name of the crawled property. --- The property set to which the crawled property is mapped, specified as a GUID (Global Unique Identifier). The GUID identifies which category the crawled property belongs to. A crawled property must be a member of a category. --- The variant type of the crawled property, which specifies the crawled property's data type. - -To include content in the full text indexes, crawled properties must be mapped to managed properties. -If a crawled property has IsMappedToContents set to "true", then the crawled property will automatically be added to the default searchable index (the full text index called "content"). -A newly created crawled property has its IsMappedToContents parameter set to the same value as the mapped-to category's MapToContents parameter. - -See New-FASTSearchMetadataCategory for information about creating a new category for crawled properties. - -See Set-FASTSearchMetadataCrawledProperty for information about changing the properties of an existing crawled property. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$guid = [guid]::NewGuid() -New-FASTSearchMetadataCategory -Name MoreWeb -Propset $guid -New-FASTSearchMetadataCrawledProperty -Name ExtendedTitle -Propset $guid -Varianttype 31 -``` - -This example first creates a new category named "MoreWeb", and then creates a new crawled property "ExtendedTitle" that is mapped to the "MoreWeb" category (because it has the same property set value). -The data type of the crawled property is a Unicode string (VT_LPWSTR, variant type 31). - -The new category gets the property set value "e20d8de2-0b5c-46f8-993d-6cdacbda5164", which was randomly generated by the System.GUID.NewGuid() method. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchMetadataCrawledProperty | Where-Object -filterscript { $_.CategoryName -eq "Web"} -New-FASTSearchMetadataCrawledProperty -Name Internaltitle -varianttype 31 -Propset d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1 -``` - -This example adds a new crawled property to an existing catalog of crawled properties. -The new crawled property is named "Internaltitle", added to the "Web" category. -It is variant type 31, a Unicode string in the user default locale. - -The "Web" category has several property set GUIDs. -Investigating with the command: - -Get-FASTSearchMetadataCrawledProperty | Where-Object -filterscript { $_.CategoryName -eq "Web"} - -reveals that the "DESCRIPTION" crawled property, which is a type similar to the crawled property to add, has the property set value "d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1". -This property set is chosen for the new crawled property. - -To use this crawled property, you must configure the connector or feeding application to send a value with the same name, variant type, and property set. - -## PARAMETERS - -### -Name -The name of the new crawled property. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Propset -The property set GUID of the new crawled property. - -The GUID controls which category the crawled property belongs to. -A GUID (Global Unique Identifier) is a 128-bit integer that has a very low probability of being duplicated. -The GUID can be specified either as a System.Guid object, or as an integer having the format "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx". - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VariantType -An integer value specifying the data type of the crawled property. -See https://go.microsoft.com/fwlink/?LinkId=163232 (https://go.microsoft.com/fwlink/?LinkId=163232) for a list of common variant types. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchMetadataCrawledProperty](Set.FASTSearchMetadataCrawledProperty.md) - -[Get-FASTSearchMetadataCrawledProperty](Get-FASTSearchMetadataCrawledProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledPropertyMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledPropertyMapping.md deleted file mode 100644 index 43b49d0be2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledPropertyMapping.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchmetadatacrawledpropertymapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchMetadataCrawledPropertyMapping ---- - -# New-FASTSearchMetadataCrawledPropertyMapping - -## SYNOPSIS -Creates a new mapping from a crawled property to a managed property. - -## SYNTAX - -``` -New-FASTSearchMetadataCrawledPropertyMapping -CrawledProperty <CrawledProperty> - -ManagedProperty <ManagedProperty> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet maps a crawled property to a managed property and stores the crawled content in the Microsoft FAST Search Server 2010 for SharePoint index. - -You can map a crawled property to multiple managed properties. -If you map multiple crawled properties to a single managed property, use the managed property's MergeCrawledProperties parameter to control whether or not the crawled properties are merged into the managed property or just overwritten. -See Set-FASTSearchMetadataManagedProperty for more information. - -When you map a crawled property into a managed property, the variant type of the crawled property is converted into the available data types in FAST Search Server 2010 for SharePoint. -See https://go.microsoft.com/fwlink/?LinkId=163233 (https://go.microsoft.com/fwlink/?LinkId=163233) for details about this conversion, and which variant types can be converted into native FAST Search Server 2010 for SharePoint types. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$sitetitle_managedproperty = Get-FASTSearchMetadataManagedProperty -Name sitetitle -$internaltitle_crawledproperty = Get-FASTSearchMetadataCrawledProperty -name internaltitle -New-FASTSearchMetadataCrawledPropertyMapping -Managedproperty $sitetitle_managedproperty -crawledproperty $internaltitle_crawledproperty -``` - -This example adds a mapping from the crawled property "internaltitle" (here part of the Web category) to the managed property "sitetitle". - -Note that both the crawled property and the managed property already exist, and these commands only add the mapping. -As a result, the crawled property "internaltitle" will now be mapped to "sitetitle" and stored in the FAST Search Server 2010 for SharePoint system. -The managed property can then be included in a full text index to make it searchable. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$extended_title = New-FASTSearchMetadataManagedproperty -name ExtendedTitle -Type 1 -$title = Get-FASTSearchMetadataManagedProperty -name title -$title.GetCrawledPropertyMappings() | ForEach-Object { New-FASTSearchMetadataCrawledPropertyMapping -ManagedProperty $extended_title -CrawledProperty $_ } -``` - -This example adds a new managed property named "ExtendedTitle", and maps to "ExtendedProperty" all crawled properties that are normally mapped to the managed property named "title". -The original "title" managed property is not changed, to avoid changing the current behavior of the search system. - -This example first generates a list of crawled property objects mapped to the original "title" managed property. -Then the example iterates over this list using ForEach-Object to add each of them to the new "ExtendedTitle" managed property. -More crawled properties can be added to this new managed property later without impacting the "title" managed property. - -## PARAMETERS - -### -CrawledProperty -The crawled property that is mapped to a managed property. - -```yaml -Type: CrawledProperty -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -The managed property to which a crawled property is mapped. - -```yaml -Type: ManagedProperty -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataCrawledPropertyMapping](Get-FASTSearchMetadataCrawledPropertyMapping.md) - -[Remove-FASTSearchMetadataCrawledPropertyMapping](Remove-FASTSearchMetadataCrawledPropertyMapping.md) - -[Set-FASTSearchMetadataCrawledPropertyMapping](Set-FASTSearchMetadataCrawledPropertyMapping.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataFullTextIndex.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataFullTextIndex.md deleted file mode 100644 index 25a86a84b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataFullTextIndex.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchmetadatafulltextindex -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchMetadataFullTextIndex ---- - -# New-FASTSearchMetadataFullTextIndex - -## SYNOPSIS -Creates a new full text index. - -## SYNTAX - -``` -New-FASTSearchMetadataFullTextIndex -Description <String> -Name <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new full text index in Microsoft FAST Search Server 2010 for SharePoint. -A full text index can be searched by specifying the full text index name in a query. -For example: "extracontent:car" searches for the term "car" in the full text index named "extracontent". -If no full text index is specified, the default full text index is used. -A relevancy score is calculated when searching the full text index, according to the rank profile specified in the query (or the default rank profile, if no rank profile is specified). - -See Set-FASTSearchMetadataFullTextIndex for details about changing the default full text index for searching. - -See Set-FASTSearchMetadataRankProfile for more details about rank profiles. - -Use New-FASTSearchMetadataFullTextIndexMapping to create mappings from managed properties to a new full text index. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchMetadataFullTextIndex -Name CommonSharePoint -Description "Content from the common SharePoint site." -``` - -This example creates a new full text index named "CommonSharePoint". -After it has been created, you can map managed properties into the full text index. -See New-FASTSearchMetadataFullTextIndexMapping for details about mapping properties into a full text index. - -## PARAMETERS - -### -Description -Description of the full text index, including the type of content or which connector feeds the data. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Name of the new full text index. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-FASTSearchMetadataFullTextIndex](Remove-FASTSearchMetadataFullTextIndex.md) - -[Set-FASTSearchMetadataFullTextIndex](Set-FASTSearchMetadataFullTextIndex.md) - -[Get-FASTSearchMetadataFullTextIndex](Get-FASTSearchMetadataFullTextIndex.md) - -[Set-FASTSearchMetadataRankProfile](Set-FASTSearchMetadataRankProfile.md) - -[New-FASTSearchMetadataFullTextIndexMapping](New-FASTSearchMetadataFullTextIndexMapping.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataFullTextIndexMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataFullTextIndexMapping.md deleted file mode 100644 index d849b97124..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataFullTextIndexMapping.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchmetadatafulltextindexmapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchMetadataFullTextIndexMapping ---- - -# New-FASTSearchMetadataFullTextIndexMapping - -## SYNOPSIS -Creates a new mapping from a managed property into the full text index. - -## SYNTAX - -``` -New-FASTSearchMetadataFullTextIndexMapping -FullTextIndex <FullTextIndex> -Level <Int32> - -ManagedProperty <ManagedProperty> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet adds the content of a managed property to a full text index by mapping the managed property into the full text index. -The mapping is only applicable to new content; existing content must be re-fed to appear in this full text index. - -The managed properties are ordered by a concept called importance level. -If the number of matching documents for a query term is greater than the StopWordThreshold for the rank profile in use, the Microsoft FAST Search Server 2010 for SharePoint system retries the query, limiting the managed properties searched to those from a higher importance level. - -Importance level 1 (the first level that will be used in a query) includes managed properties from all levels 1 and up. -Importance level 2 includes levels 2 and up. -The maximum level is 7. - -This process is called drilling. -See Set-FASTSearchMetadataRankProfile for more information about StopWordThreshold. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$title = Get-FASTSearchMetadataManagedProperty -name title -$fulltextindex = Get-FASTSearchMetadataFullTextIndex -Name thirdfulltextindex -New-FASTSearchMetadataFullTextIndexMapping -ManagedProperty $title -FullTextIndex $fulltextindex -Level 3 -``` - -This example maps the managed property called "title" into the full text index named "thirdfulltextindex" at level 3. - -After this mapping is made, the content must be re-fed to populate the full text index. - -## PARAMETERS - -### -FullTextIndex -The full text index to add the mapping to. - -```yaml -Type: FullTextIndex -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Level -The importance level of this managed property. -Allowed values are 1 through 7. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: ImportanceLevel, L -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -The managed property being mapped to the full text index. - -```yaml -Type: ManagedProperty -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-FASTSearchMetadataFullTextIndexMapping](Remove-FASTSearchMetadataFullTextIndexMapping.md) - -[Set-FASTSearchMetadataFullTextIndexMapping](Set-FASTSearchMetadataFullTextIndexMapping.md) - -[Get-FASTSearchMetadataFullTextIndexMapping](Get-FASTSearchMetadataFullTextIndexMapping.md) - -[Set-FASTSearchMetadataRankProfile](Set-FASTSearchMetadataRankProfile.md) - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - -[Get-FASTSearchMetadataFullTextIndex](Get-FASTSearchMetadataFullTextIndex.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataManagedProperty.md deleted file mode 100644 index eae56c7203..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataManagedProperty.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchmetadatamanagedproperty -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchMetadataManagedProperty ---- - -# New-FASTSearchMetadataManagedProperty - -## SYNOPSIS -Creates a new managed property. - -## SYNTAX - -``` -New-FASTSearchMetadataManagedProperty -Name <String> -Type <Int32> [-Description <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new managed property in the Microsoft FAST Search Server 2010 for SharePoint system. -The managed property can be one of the following data types: - --- Text: UTF-8 encoded text string --- Integer: Signed 64 bit integer --- Boolean: true / false --- Float: Double-precision 64-bit floating point, as specified in IEEE-754 --- Decimal: Integer with up to 27 decimals (number of decimals is set through the DecimalPlaces parameter of the managed property; see Set-FASTSearchMetadataManagedProperty). --- Datetime: Date range in ISO8601 format. Valid date range is -29000-01-01T00:00:00,000 to 29000-12-31T23:59:59,999. Managed properties which have the type datetime always have sorting enabled. - -See https://go.microsoft.com/fwlink/?LinkId=163234 (https://go.microsoft.com/fwlink/?LinkId=163234) for more detailed information about the valid value ranges for each of these data types, and how illegal values are handled. - -For IEEE-754, see https://ieeexplore.ieee.org/servlet/opac?punumber=2355 (https://ieeexplore.ieee.org/servlet/opac?punumber=2355). - -For details about the options that can be set on a managed property, see Set-FASTSearchMetadataManagedProperty. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchMetadataManagedProperty -name integervalue -type 2 -description "A managed property for integer values" -``` - -This example creates a managed property called "integervalue" of type 2 (integer). -To further change the settings on the managed property, see Set-FASTSearchMetadataManagedProperty. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$managedproperty = New-FASTSearchMetadataManagedProperty -Name webtitle -type 1 -description "Titles from RSS and Sitemap Files" -$rsstitle = Get-FASTSearchMetadataCrawledProperty -Name rss.title -$sitetitle = Get-FASTSearchMetadataCrawledProperty -Name sitemap.title -New-FASTSearchMetadataCrawledPropertyMapping -ManagedProperty $managedproperty -CrawledProperty $rsstitle -New-FASTSearchMetadataCrawledPropertyMapping -ManagedProperty $managedproperty -CrawledProperty $sitetitle -$content_fulltextindex = Get-FASTSearchMetadataFullTextIndex -name content -New-FASTSearchMetadataFullTextIndexMapping -FullTextIndex $content_fulltextindex -ManagedProperty $managedproperty -level 7 -``` - -This example shows a complete work-flow for making a new managed property and mapping a crawled property to it. -It creates a new managed property called "webtitle" to which it maps the crawled properties "rss.title" and "sitemap.title". -The "webtitle" managed property is then mapped into the full text index "content" at importance level 7. - -After this, you can feed documents (not shown here) with the crawled properties "rss.title" and "sitemap.title", and they will appear in the "webtitle" managed property. -This managed property is then searchable as part of the full text index named "content". - -To make the managed property searchable on its own, see Set-FASTSearchMetadataManagedProperty-Queryable. - -## PARAMETERS - -### -Name -The name of the new managed property. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -An integer representing the data type of the new managed property. -Valid values are: - --- 1 (Text) --- 2 (Integer) --- 3 (Boolean) --- 4 (Float) --- 5 (Decimal) --- 6 (Datetime) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A text description of the managed property explaining what the managed property is used for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - -[Set-FASTSearchMetadataManagedProperty](Set-FASTSearchMetadataManagedProperty.md) - -[Remove-FASTSearchMetadataManagedProperty](Remove-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataRankProfile.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataRankProfile.md deleted file mode 100644 index a54d76985a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataRankProfile.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchmetadatarankprofile -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchMetadataRankProfile ---- - -# New-FASTSearchMetadataRankProfile - -## SYNOPSIS -Creates a new rank profile to calculate relevance in queries. - -## SYNTAX - -``` -New-FASTSearchMetadataRankProfile -Name <String> [-Template <RankProfile>] [<CommonParameters>] -``` - -## DESCRIPTION -A rank profile controls the relevancy calculation for a query. -It consists of several components which are weighted so that the relevancy calculation fits the content. -See Set-FASTSearchMetadataRankProfile for more details. - -A rank profile can either be created with default values, or based on another existing rank profile using the Template parameter. - -The rank profile is typically specified as part of a query. -If no rank profile is specified in the query, the default rank profile is used. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchMetadataRankProfile -Name newrankdistribution -``` - -This example adds a new rank profile based on the default settings. -The new rank profile is called "newrankdistribution". - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$rankprofile_template = Get-FASTSearchMetadataRankProfile -Name newrankdistribution -New-FASTSearchMetadataRankProfile -Template $rankprofile_template -Name ExtraRankProfile -``` - -This example adds a new rank profile based on an existing rank profile called "newrankdistribution". - -### ---------------EXAMPLE 3----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$new_rank_profile = New-FASTSearchMetadataRankProfile -Name ImprovedDefault -$new_rank_profile.makeDefault() -``` - -This example specifies a new rank profile to use as the default rank profile for the FAST Search Server 2010 for SharePoint. - -## PARAMETERS - -### -Name -The name of the new rank profile. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: RankProfileName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -An object representing the rank profile that will serve as a template in creating the new rank profile. - -```yaml -Type: RankProfile -Parameter Sets: (All) -Aliases: RankProfileTemplate, T -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-FASTSearchMetadataRankProfile](Remove-FASTSearchMetadataRankProfile.md) - -[Set-FASTSearchMetadataRankProfile](Set-FASTSearchMetadataRankProfile.md) - -[Get-FASTSearchMetadataRankProfile](Get-FASTSearchMetadataRankProfile.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSearchSettingGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSearchSettingGroup.md deleted file mode 100644 index d6ba297269..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSearchSettingGroup.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchsearchsettinggroup -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchSearchSettingGroup ---- - -# New-FASTSearchSearchSettingGroup - -## SYNOPSIS -Creates a new Microsoft FAST Search Server 2010 for SharePoint search setting group. - -## SYNTAX - -``` -New-FASTSearchSearchSettingGroup -Name <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new FAST Search Server 2010 for SharePoint search setting group. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchSearchSettingGroup -Name marketinggroup -``` - -This example creates a new FAST Search Server 2010 for SharePoint search setting group named "marketinggroup". - -## PARAMETERS - -### -Name -The name of the search setting group to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSearchSettingGroup](Get-FASTSearchSearchSettingGroup.md) - -[Remove-FASTSearchSearchSettingGroup](Remove-FASTSearchSearchSettingGroup.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityClaimsUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityClaimsUserStore.md deleted file mode 100644 index 6711978dff..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityClaimsUserStore.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchsecurityclaimsuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchSecurityClaimsUserStore ---- - -# New-FASTSearchSecurityClaimsUserStore - -## SYNOPSIS -Creates a FAST Search Server 2010 for SharePoint security user store to provide security for claims content. - -## SYNTAX - -``` -New-FASTSearchSecurityClaimsUserStore [-Identity] <String> [[-Description] <String>] [[-Issuer] <String>] - [-ObjectToClone <ClaimsUserStore>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet configures extended security for claims content. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchSecurityClaimsUserStore -Identity clm -``` - -This example creates a new security claims user store with a user store Identity of "clm". - -This example uses default values for all parameters except the required Identity parameter. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchSecurityClaimsUserStore -Identity clm | New-FASTSearchSecurityClaimsUserStore -Identity cl2 -``` - -This example creates a new security claims user store with an identity of "cl2" using all properties from the claims user store "clm" as a baseline. -The New-FASTSearchSecurityClaimsUserStore cmdlet uses the ObjectToClone value on the pipeline as input to the New cmdlet. - -## PARAMETERS - -### -Identity -The user store identity. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A brief explanation of the user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Issuer -The Microsoft SharePoint Server Security Token Service (STS) claims provider that issued the claims. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ObjectToClone -A claims user store object whose property values are used as a baseline to create another claims user store. - -```yaml -Type: ClaimsUserStore -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityClaimsUserStore](Get-FASTSearchSecurityClaimsUserStore.md) - -[Set-FASTSearchSecurityClaimsUserStore](Set-FASTSearchSecurityClaimsUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityLotusNotesUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityLotusNotesUserStore.md deleted file mode 100644 index b55688f178..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityLotusNotesUserStore.md +++ /dev/null @@ -1,285 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchsecuritylotusnotesuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchSecurityLotusNotesUserStore ---- - -# New-FASTSearchSecurityLotusNotesUserStore - -## SYNOPSIS -Creates a FAST Search Server 2010 for SharePoint security user store to provide security for Lotus Notes content. - -## SYNTAX - -``` -New-FASTSearchSecurityLotusNotesUserStore [-Identity] <String> - [[-NonIndexableCharacterEncodingPrefix] <String>] [[-NonIndexableCharacterPattern] <String>] - [[-Description] <String>] [[-UseDenyOnDefault] <Boolean>] [[-UseDocumentSecurity] <Boolean>] - [[-UseWildcardSecurity] <Boolean>] [[-UseViewSecurity] <Boolean>] [[-AllowPrefix] <String>] - [[-DenyPrefix] <String>] [[-NonIndexableCharacterHandling] <String>] [-ObjectToClone <LotusNotesUserStore>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet configures FAST Search Server 2010 for SharePoint security for Lotus Notes content. - -A Lotus Notes security user store uses a user-dependent query filter that is applied to each query to enforce the defined access control policies based on indexed values. -The Lotus Notes security user store search filter requires that the user has read access to both the item and the database to view a specific item. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -new-FASTSearchSecurityLotusNotesUserStore ln1 -``` - -This example creates a new security Lotus Notes user store with a user store identity of "ln1". - -This example uses default values for all parameters except the required Identity parameter. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchSecurityLotusNotesUserStore -Identity ln1 | New-FASTSearchSecurityLotusNotesUserStore -Identity ln3 -UseViewSecurity $true -``` - -This example creates a new Lotus Notes user store with an identity of "ln3" and enables view level security. -The New-FASTSearchSecurityLotusNotesUserStore command uses the ObjectToClone object on the pipeline as input to the New command for default parameter values. - -## PARAMETERS - -### -Identity -User store identity. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Description -A brief explanation of the user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -UseDenyOnDefault -If true, support for default access with deny on users/groups is enabled on database level security. - -You must enable this filter for an inverse security model: first grant access to everyone, and then explicitly deny access to certain groups or users. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -UseDocumentSecurity -If true, item security is enabled (i.e., the filter contains an item level security condition). - -If set to false, item level security is ignored; only database level security (and possibly view security) is used. - -If items always inherit the ACLs of the database, you can turn off this option. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -UseWildcardSecurity -If true, database access through wildcard group entry (starting with */) is enabled. - -If set to false, the wildcard check is ignored. -Only normal groups are checked against the database ACL. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -UseViewSecurity -If true, view security is enabled (i.e., the filter contains a view level security condition). - -If set to false, view level security is ignored; only database level security (and possibly item security) is used. - -If views always inherit the ACLs of the database, or if views are not indexed, you can turn off this option. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 6 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AllowPrefix -A string value prepended to the document ACL to control which items the user is allowed access to and which items will be returned in the query. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 7 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DenyPrefix -A string value prepended to the ACL to control which items the user is denied access to and which items are not returned from the query. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 8 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -NonIndexableCharacterHandling -Specifies what to do with ACL values that match the NonIndexableCharacterRegExPattern regular expression. - -Valid values: - --- encode - The ACL is encoded into a single searchable term. --- encodeWithPrefix - The value of NonIndexableEncodedPrefix is concatenated with the ACL to be encoded, producing a single searchable term. --- remove - The ACL is removed from both allowing and denying access. Specify "remove" if the ACL is never used to deny access. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -NonIndexableCharacterEncodingPrefix -If NonIndexableCharacterHandling is set to encodeWithPrefix, this parameter specifies the prefix added to the encoded ACL. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 10 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -NonIndexableCharacterPattern -Specifies a regular expression pattern used to detect non-indexable characters in an ACL. - -Identities matching this regular expression pattern will be processed based on NonIndexableCharacterHandling. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 11 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ObjectToClone -A Lotus Notes user store object whose property values are used as a baseline for the Lotus Notes user store being created. - -```yaml -Type: LotusNotesUserStore -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityLotusNotesUserStore](Set-FASTSearchSecurityLotusNotesUserStore.md) - -[Get-FASTSearchSecurityLotusNotesUserStore](Get-FASTSearchSecurityLotusNotesUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityRegexAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityRegexAliaser.md deleted file mode 100644 index 74f1402f79..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityRegexAliaser.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchsecurityregexaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchSecurityRegexAliaser ---- - -# New-FASTSearchSecurityRegexAliaser - -## SYNOPSIS -Creates a regular expression aliaser. - -## SYNTAX - -``` -New-FASTSearchSecurityRegexAliaser [-InputUserStoreId] <String> [-OutputUserStoreIds] <String[]> - [-Patterns] <System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Security.Config.RegExAliasPatternMapConfig]> - [[-Identity] <String>] [[-CaseSensitive] <Boolean>] [[-UnicodeCaseSensitive] <Boolean>] - [-ObjectToClone <SecurityRegexAliaser>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a regular expression aliaser to map users/groups from one user store to users/groups in other user stores, based on a regular expression pattern. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchSecurityRegexAliaserPattern -Regex .* -MapToUsername \1 | New-FASTSearchSecurityRegexAliaser -Identity regex1 -InputUserStoreId ln1 -OutputUserStoreIds ln2 -``` - -This example creates a regular expression aliaser pattern object and pipes it into a New-FASTSearchSecurityRegexAliaser cmdlet to create a regular expression aliaser. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchSecurityRegexAliaserPattern -Regex .* -MapToUsername \1 | New-FASTSearchSecurityRegexAliaser -InputUserStoreId ln1 -OutputUserStoreIds ln2,ln3 -CaseSensitive $False -UnicodeCaseSensitive $False -``` - -This example creates a regular expression aliaser pattern object and pipes it into a New-FASTSearchSecurityRegexAliaser cmdlet to create a regular expression aliaser. -The example sets the case-sensitive flags so pattern matching is performed in a case-insensitive manner. -The OutputUserStoreIds parameter maps users/groups to two user stores: "ln2" and "ln3". -The example generates the aliaser identity. - -## PARAMETERS - -### -InputUserStoreId -The identity of the mapped-from user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -OutputUserStoreIds -A comma-separated list of mapped-to user store identities. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Patterns -A list of RegExAliasPatternMapConfig instances containing the regular expression patterns used for the mapping. - -```yaml -Type: System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Security.Config.RegExAliasPatternMapConfig] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Identity -The identity of the aliaser. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CaseSensitive -Specifies whether the regular expression patterns defined in the RegExAliasPatternMapConfig list are matched based on case sensitivity matching rules. -The default is true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -UnicodeCaseSensitive -Specifies whether the regular expressions patterns defined in the RegExAliasPatternMapConfig list are matched based on Unicode case sensitivity matching rules. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 6 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ObjectToClone -A SecurityRegexAliaser object whose property values are used for the SecurityRegexAliaser aliaser being created. - -```yaml -Type: SecurityRegexAliaser -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityRegexAliaser](Set-FASTSearchSecurityRegexAliaser.md) - -[Get-FASTSearchSecurityRegexAliaser](Get-FASTSearchSecurityRegexAliaser.md) - -[New-FASTSearchSecurityRegexAliaserPattern](New-FASTSearchSecurityRegexAliaserPattern.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityRegexAliaserPattern.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityRegexAliaserPattern.md deleted file mode 100644 index 11286e4402..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityRegexAliaserPattern.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchsecurityregexaliaserpattern -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchSecurityRegexAliaserPattern ---- - -# New-FASTSearchSecurityRegexAliaserPattern - -## SYNOPSIS -Creates a new regular expression pattern for a regex principal aliaser. - -## SYNTAX - -``` -New-FASTSearchSecurityRegexAliaserPattern [-Regex] <String> [-MapToUsername] <String> - [[-InputPropertyName] <String>] - [-Patterns <System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Security.Config.RegExAliasPatternMapConfig]>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new regular expression pattern that can be added to the list of patterns for a regular expression based principal aliaser. -This cmdlet creates a regular expression pattern that is used by and input to the New-FASTSearchSecurityRegexAliaser and Set-FASTSearchSecurityRegexAliaser cmdlets. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchSecurityRegexAliaserPattern -Regex .* -InputPropertyName mail -MapToUsername "\1" -``` - -This example creates a regular expression pattern that can be used to map the "mail" property of a Microsoft user store to identities in other user stores. - -Use the regex pattern configuration object output from this command for the value of a pattern's parameter in a New-FASTSearchSecurityRegexAliaser or a Set-FASTSearchSecurityRegexAliaser cmdlet. - -## PARAMETERS - -### -Regex -The regular expression pattern that determines if the user or group should be mapped to another user store. -This regular expression pattern may contain regular expression groups that may be used in the generation of the MapToUsername value. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MapToUsername -The user or group name to look to. -This can also contain regular expression group replacements using the syntax: - -\# - -where # is the group capture index. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InputPropertyName -The user/group property name this regular expression pattern is matched against. - -The InputPropertyName is one of the following: - --- $PRINCIPAL_REFERENCE_ID - The identifier of the user or group. This is the default. --- $PRINCIPAL_REFERENCE_ALIAS - The alias of the user or group. - -Any other property of the user or group. -Refer to your specific user store for other properties that the user store exposes. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Patterns -A list of RegExAliasPatternMapConfig objects. -The RegExAliasPatternMapConfig being created is added to this list. - -```yaml -Type: System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Security.Config.RegExAliasPatternMapConfig] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityRegexAliaser](Get-FASTSearchSecurityRegexAliaser.md) - -[New-FASTSearchSecurityRegexAliaser](New-FASTSearchSecurityRegexAliaser.md) - -[Set-FASTSearchSecurityRegexAliaser](Set-FASTSearchSecurityRegexAliaser.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityXMLAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityXMLAliaser.md deleted file mode 100644 index 00b335b220..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchSecurityXMLAliaser.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-fastsearchsecurityxmlaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: New-FASTSearchSecurityXMLAliaser ---- - -# New-FASTSearchSecurityXMLAliaser - -## SYNOPSIS -Creates an XML principal aliaser. - -## SYNTAX - -``` -New-FASTSearchSecurityXMLAliaser [-InputUserStoreId] <String> [-OutputUserStoreIds] <String[]> - [[-Identity] <String>] [[-InputPropertyName] <String>] [-ObjectToClone <SecurityXMLAliaser>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates an XML aliaser to map users and groups from one user store to users and groups in other user stores, based on an XML mapping file. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchSecurityXMLAliaser -InputUserStoreId win -OutputUserStoreIds ln3 -InputPropertyName mail -``` - -This example creates an XML principal aliaser to map the mail property of a Microsoft user store to users and groups in another user store. - -Use the Set-FASTSearchSecurityXMLAliaser cmdlet to upload the XML mapping file. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchSecurityAliaser xmlalias2 | New-FASTSearchSecurityXMLAliaser -Identity myxmlalias -OutputUserStoreIds ln2 -``` - -This example creates an XML principal aliaser based on an existing XML aliaser but sets the output user store IDs to 'ln2'. - -Use the Set-FASTSearchSecurityXMLAliaser cmdlet to upload an XML mapping file with desired mappings for the new aliaser. - -## PARAMETERS - -### -InputUserStoreId -The identity of the mapped-from user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -OutputUserStoreIds -A comma-separated list of mapped-to user store identities. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Identity -The identity of the aliaser. -An identity is generated if the parameter is not specified. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -InputPropertyName -The user/group property name this regular expression pattern is matched against. - -The InputPropertyName is one of the following: - --- $PRINCIPAL_REFERENCE_ID - The identifier of the user or group. This is the default. - -Be sure to enclose in single quotes: '$PRINCIPAL_REFERENCE_ID' - --- $PRINCIPAL_REFERENCE_ALIAS - The alias of the user or group. - -Be sure to enclose in single quotes: '$PRINCIPAL_REFERENCE_NAME' - -Any other property of the user or group. -Refer to your specific user store for other properties that the user store exposes. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ObjectToClone -A SecurityXMLAliaserobject whose property values are copied as a baseline in the creation of another SecurityXMLAliaser aliaser. - -```yaml -Type: SecurityXMLAliaser -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-FASTSearchSecurityXMLAliaser](Set-FASTSearchSecurityXMLAliaser.md) - -[Get-FASTSearchSecurityXMLAliaser](Get-FASTSearchSecurityXMLAliaser.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServiceApplication.md deleted file mode 100644 index 67f0f8188d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServiceApplication.md +++ /dev/null @@ -1,475 +0,0 @@ ---- -external help file: microsoft.office.access.services.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spaccessserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAccessServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAccessServiceApplication - -## SYNOPSIS -Creates a new instance of an Access Services application in SharePoint Server. - -## SYNTAX - -``` -New-SPAccessServiceApplication [-Name <String>] -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CacheTimeout <Int32>] [-ColumnsMax <Int32>] [-Confirm] - [-Default] [-NonRemotableQueriesAllowed] [-OrderByMax <Int32>] [-OuterJoinsAllowed] - [-OutputCalculatedColumnsMax <Int32>] [-PrivateBytesMax <Int32>] [-RecordsInTableMax <Int32>] - [-RequestDurationMax <Int32>] [-RowsMax <Int32>] [-SessionMemoryMax <Int32>] - [-SessionsPerAnonymousUserMax <Int32>] [-SessionsPerUserMax <Int32>] [-SourcesMax <Int32>] - [-TemplateSizeMax <Int32>] [-WhatIf] [-ApplicationLogSizeMax <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPAccessServiceApplication cmdlet creates a new instance of an Access Services application in SharePoint Server 2010, SharePoint Server 2013. -After you create a new Access Services application, use the Set-SPAccessServiceApplication cmdlet to modify its global settings. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE 1---------------- -``` -New-SPAccessServiceApplication -Name "MyAccessService" -SPIisWebServiceApplicationPool MyAppPool -``` - -This example creates a new instance of Access Services named MyAccessService that runs under the application pool named MyAppPool. - -### ------------EXAMPLE 2---------------- -``` -New-SPAccessServiceApplication -Name "MyAccessService" -SPIisWebServiceApplicationPool MyAppPool -SessionsPerUserMax 25 -``` - -This example creates a new instance of Access Services named MyAccessService that runs under the application pool named MyAppPool, which allows up to 25 sessions per user on each back end application server machine on which Access Services runs. - -## PARAMETERS - -### -Name -Specifies the display name of the Access Services application to create. -The name can contain a maximum of 128 characters and can contain the comma (,), equal sign (=), or colon (:) characters provided they are enclosed in quotation marks. - -The type must be a valid name of an Access Services application; for example, AccessSrvApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing Internet Information Services (IIS) application pool to run the Web service in for the new Access Services application. - -The type must be a valid instance of a SPIisWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheTimeout -Specifies the number of seconds that a data cache will remain active on Access Services with no user activity. -Valid values include: -1, cache never times out; 1 to 2073600, cache remains active from 1 second to 24 days. - -The type must be the integers -1, or an integer in the range of 1 to 2073600 (24 days). -The default value is 300. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ColumnsMax -Specifies the maximum number of columns that a list involved in a query can contain, or that the output of the query can contain. -The default value is 30. - -The type must be an integer in the range of 1 to 255 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -Specifies that the service application is associated with Web applications by adding this service application's proxy to the farm's default proxy list. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NonRemotableQueriesAllowed -Specifies that queries that cannot be remoted to the database tier can run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrderByMax -Specifies the maximum number of Order By clauses in the query. -The default value is 4. - -The type must be an integer in the range of 1 to 8. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OuterJoinsAllowed -Specifies that left and right outer joins are supported. -Inner joins are always supported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputCalculatedColumnsMax -Specifies the maximum number of calculated columns that can be included in the output as a part of the query. -Calculated columns in the underlying list are not included. -The default value is 10. - -The type must be an integer in the range of 1 to 32. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateBytesMax -Specifies the maximum private bytes in megabytes (MB) that can be used by Access Services. -When set to -1, Access Services defaults to 75 percent of physical memory on the machine. -Valid values are -1 (no limit), and from 1 to any positive integer.The default value is -1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordsInTableMax -Specifies the maximum number of records allowed for a table in the Access Services application. -Valid values include: -1, no limit, and 1 to any positive integer. -The default value is 500000. - -The type must be the integer -1, or an integer in the range of 1 to MaxInt. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestDurationMax -Specifies the maximum number of seconds that a request to perform an operation can use before the request times out. -Valid values include: -1, no limit, 1 to 2073600, cache remains active 1 second to 24 days. -The default value is 30. - -The type must be the integer -1, or an integer in the range of 1 to 2073600 (24 days) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RowsMax -Specifies the maximum number of rows that a list involved in a query can have, or that the output of the query can have. -The default value is 50000. - -The type must be an integer in the range of 1 to 200000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionMemoryMax -Specifies the maximum allowable size, in megabytes, of an individual session. -Valid values include 0, disable property, and 1 to 4095. -The default value is 64. - -The type must be the integer 0, or an integer in the range of 1 to 4095. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerAnonymousUserMax -Specifies the maximum number of sessions allowed per user. -If this maximum is reached, the oldest session will be deleted when a new session is started. -Valid values include: -1, no limit, and 1 to any positive integer. -The default value is 10. - -The type must be the integer -1, or an integer in the range of 1 to MaxInt. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerUserMax -Specifies the maximum number of sessions allowed per user. -If this maximum is reached, the oldest session will be deleted when a new session is started. -Valid values include: -1, no limit, and 1 to any positive integer. -The default value is 10. - -The type must be the integer -1, or an integer in the range of 1 to MaxInt. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcesMax -Specifies the maximum number of lists that can be used as input to a query at one time. -The default value is 8. - -The type must be an integer in the range of 1 to 20. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TemplateSizeMax -The maximum allowable size in megabytes allowed for Access templates (.accdt file files) uploaded into the solution gallery. -Valid values: -1(no limit), from 1 to any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationLogSizeMax -Specifies the maximum number of records for an Access Services Application Log list. Valid valies: -1 to maxint. 0 means none are allowed. The default value is 3000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesApplication.md deleted file mode 100644 index 7389bc4251..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesApplication.md +++ /dev/null @@ -1,390 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spaccessservicesapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAccessServicesApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAccessServicesApplication - -## SYNOPSIS -Creates an Access Services Service Application. - -## SYNTAX - -### DefaultParameterSet -``` -New-SPAccessServicesApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CacheTimeout <Int32>] [-Confirm] -DatabaseServer <String> - [-DatabaseServerCredentials <PSCredential>] [-Default] [-Encrypt <Boolean>] [-Hosted <Boolean>] - [-Name <String>] [-PrivateBytesMax <Int32>] [-QueryTimeout <Int32>] [-RecoveryPointObjective <Int32>] - [-RequestDurationMax <Int32>] [-SessionsPerAnonymousUserMax <Int32>] [-SessionsPerUserMax <Int32>] - [-TrustServerCertificate <Boolean>] [-WhatIf] [<CommonParameters>] -``` - -### NoApplicationServerParameterSet -``` -New-SPAccessServicesApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CacheTimeout <Int32>] [-Confirm] [-Default] - [-Hosted <Boolean>] [-Name <String>] [-PrivateBytesMax <Int32>] [-QueryTimeout <Int32>] - [-RecoveryPointObjective <Int32>] [-RequestDurationMax <Int32>] [-SessionsPerAnonymousUserMax <Int32>] - [-SessionsPerUserMax <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates an Access Services Service Application. - -## EXAMPLES - -### Example 1 -``` -New-SPAccessServicesApplication -DatabaseServer SQLServerName -ApplicationPool 'SharePoint Web Services Default' -Name 'Access Services Service Application' -Default -``` - -Creates an Access Services Service Application. - -## PARAMETERS - -### -ApplicationPool -Specifies the existing IIS application pool in which to run the Web service for the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheTimeout -The maximum time (in seconds) that a data cache can remain available, as measured from the end of each request for data in that cache. - -Valid values: -1 (indicates no limit); 1 through 2073600 (24 days). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid SQL Server host name; for example, SERVER\Database. - -```yaml -Type: String -Parameter Sets: DefaultParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerCredentials -Specifies the credentials used to log into the database server. - -```yaml -Type: PSCredential -Parameter Sets: DefaultParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -Add to default Service Application Proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: DefaultParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: SwitchParameter -Parameter Sets: NoApplicationServerParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Encrypt -Specifies to use SSL encryption between Access Services and the SQL Server hosting Access Services databases. - -```yaml -Type: Boolean -Parameter Sets: DefaultParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Hosted - -Not used. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the Access Services Service Application to create. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateBytesMax -The maximum number of private bytes (in MB) allocated by the Access Services process. - -Valid values: -1 (the limit is set to 50% of physical memory on the machine), any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueryTimeout -Maximum time in seconds for a database command or query to execute before it is cancelled. - -Valid values: 0 (indicates no limit); 1 through 2073600 (24 days). Recommended value is 60. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecoveryPointObjective - -Not used. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestDurationMax -The maximum duration (in seconds) allowed for a request from an application. - -Valid values: -1 (indicates no limit); 1 through 2073600 (24 days). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerAnonymousUserMax -The maximum number of sessions allowed per anonymous user. If this maximum is hit the oldest session will be deleted when a new session is started. - -Valid values: -1 (no limit), 1 to any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerUserMax -The maximum number of sessions allowed per user. If a user has this many sessions and starts a new session, the user's oldest session is deleted. - -Valid values: -1 (no limit), from 1 to any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustServerCertificate -Sets a value that indicates whether the channel will be encrypted while bypassing walking the certificate chain to validate trust. - -```yaml -Type: Boolean -Parameter Sets: DefaultParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPIisWebServiceApplicationPoolPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesApplicationProxy.md deleted file mode 100644 index 29b9091b5c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesApplicationProxy.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spaccessservicesapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAccessServicesApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAccessServicesApplicationProxy - -## SYNOPSIS -Creates a Proxy for an Access Services Service Application. - -## SYNTAX - -``` -New-SPAccessServicesApplicationProxy [-application] <SPServiceApplication> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a Proxy for an Access Services Service Application. -## EXAMPLES - -### Example 1 -``` -$sa = New-SPAccessServicesApplication -DatabaseServer spag.lab.cobaltatom.com -ApplicationPool 'SharePoint Web Services Default' -Name 'Access Services Service Application' -Default -New-SPAccessServicesApplicationProxy -application $sa -``` - -This example creates an Access Services Application, placing it into the `$sa` variable. Using the `$sa` variable, it is then used to create the Access Services Service Application Proxy. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -application -Specifies the Access Services Service Application to create a proxy for. - -```yaml -Type: SPServiceApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.Administration.SPServiceApplication -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesDatabaseServer.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesDatabaseServer.md deleted file mode 100644 index 4f958e22d2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAccessServicesDatabaseServer.md +++ /dev/null @@ -1,379 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spaccessservicesdatabaseserver -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAccessServicesDatabaseServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAccessServicesDatabaseServer - -## SYNOPSIS -Adds a server to host Access Services databases. - -## SYNTAX - -``` -New-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-AvailableForCreate <Boolean>] [-Confirm] - [-DatabaseServerCredentials <PSCredential>] [-DatabaseServerGroupName <String>] -DatabaseServerName <String> - [-Encrypt <Boolean>] [-Exclusive <Boolean>] [-SecondaryDatabaseServerName <String>] - [-ServerReferenceId <Guid>] [-TrustServerCertificate <Boolean>] [-UserDomain <String>] - [-ValidateServer <Boolean>] [-WhatIf] [-LoginType <LoginType>] [-State <DatabaseServerStates>] - [-StateOwner <ServerStateOwner>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet adds additional Access Services database servers to host Access Services databases. - -## EXAMPLES - -### Example 1 -``` -New-SPAccessServicesDatabaseServer -ServiceContext https://siteUrl -DatabaseServerName SQLSVR01 -ValidateServer:$true -``` - -This example adds the SQL Server named SQLSVR01 as an Access Services database server using the context of the site, https://siteUrl. This also validates SQLSVR01 is capable of hosting Access Services databases. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AvailableForCreate -Indicates whether or not the SQL Server is available to create Access Services databases on. The default value is true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerCredentials -Specifies the credentials used to connect to the SQL Server. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerGroupName -Specifies the Access Services database group name. The default value is DEFAULT. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerName -Specifies the name of the SQL Server to add. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Encrypt -Specifies to use SSL encryption between Access Services and the SQL Server hosting Access Services databases. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Exclusive -If the SQL Server has AvaliableForCreate set to False, this will update it to True. If the SQL Server Id does not match the database server Id and the server has AvailableForCreate set to True, this will set AvailableForCreate to False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryDatabaseServerName -Specifies a secondary SQL Server to associate to the new SQL Server. This is used for disaster recovery purposes. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServerReferenceId -Provide a specific Server Reference Id. By default, a Server Reference Id is generated automatically when the SQL Server is added. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context to retrieve Access Services information from. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -TrustServerCertificate -Sets a value that indicates whether the channel will be encrypted while bypassing walking the certificate chain to validate trust. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserDomain -Specifies the domain to use for credentials. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidateServer -Validates the SQL Server is in a supported state to host Access Services databases. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoginType -Indicates the login type. Valid values are: - -* ApplicationLogin - -* LocalDBApplicationLogin - -* ServerLogin - -* StorageAccountLogon - -* WindowsAzureServerLogin - -The default value is ServerLogin. - -```yaml -Type: LoginType -Parameter Sets: (All) -Aliases: -Accepted values: ApplicationLogin, LocalDBApplicationLogin, ServerLogin, StorageAccountLogon, WindowsAzureServerLogin -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State -Indicates the availability of the SQL Server to be added. Valid values are: - -* Active - -* Locked - -* Reserved - -The default value is Active. - -```yaml -Type: DatabaseServerStates -Parameter Sets: (All) -Aliases: -Accepted values: Active, Locked, Reserved -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOwner -Specifies the state owner. Valid values are: - -* NoOwner - -* TenantMove - -The default value is NoOwner. - -```yaml -Type: ServerStateOwner -Parameter Sets: (All) -Aliases: -Accepted values: NoOwner, TenantMove -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAlternateURL.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAlternateURL.md deleted file mode 100644 index 43bdf1522d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAlternateURL.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spalternateurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAlternateURL -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAlternateURL - -## SYNOPSIS - -Creates a new public or internal URL for the specified Web application zone or resource. - - - -## SYNTAX - -### WebApplication -``` -New-SPAlternateURL [-Url] <String> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Internal] [-WhatIf] [-Zone <SPUrlZone>] - [<CommonParameters>] -``` - -### ResourceName -``` -New-SPAlternateURL [-Url] <String> -ResourceName <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Internal] [-WhatIf] [-Zone <SPUrlZone>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The New-SPAlternateUrl cmdlet creates a new public or internal URL for the specified Web application zone or resource. -Use the ResourceName parameter if the alternate URL is for an external resource. - -Each Web application can be associated with a collection of mappings between internal and public URLs. -Both internal and public URLs consist of the protocol and domain portion of the full URL; for example, https://www.fabrikam.com. -Users type a public URL to get to the SharePoint site, and that URL appears in the links on the pages. -Internal URLs are in the URL requests that are sent to the SharePoint site. -Many internal URLs can be associated with a single public URL in multiserver farms; for example, when a load balancer routes requests to specific IP addresses to various servers in the load-balancing cluster. - -Each Web application supports five collections of mappings per URL; the five collections correspond to five zones (default, intranet, extranet, Internet, and custom). -When the Web application receives a request for an internal URL in a particular zone, links on the pages returned to the user have the public URL for that zone. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -#create the public URL -New-SPAlternateURL https://www.contoso.com -Zone "Internet" - -#create the internal URL -New-SPAlternateURL https://sharepoint.contoso.com -Zone "Internet" -internal -``` - -This example translates incoming requests for https://www.contoso.com into https://sharepoint.contoso.com (on the Internet zone). - -When a reverse proxy is being set up to handle public URL SSL termination, alternate access mappings must be configured to handle the URL translation. - -## PARAMETERS - -### -Url -Specifies the public URL that users access to sign in to the Web application. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the name, URL, or GUID of the Web application for which to create the mapping. - -The type must be a valid name, URL, in the form WebApplication-1212, https://server_name, or GUID, in the form 1234-5678-9876-0987. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResourceName -Specifies the resource name, if the alternate URL is for an external resource. -If no value is specified, the value is left blank. - -```yaml -Type: String -Parameter Sets: ResourceName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Internal -Makes this alternate URL an internal URL. -If this parameter is not provided, the URL is a public URL. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Zone -Specifies one of the five zones with which the alternate URL is associated. - -The type must be a valid zone: Default, Intranet, Internet, Extranet, or Custom. - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAppManagementServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAppManagementServiceApplication.md deleted file mode 100644 index e3e31815c3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAppManagementServiceApplication.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spappmanagementserviceapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAppManagementServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAppManagementServiceApplication - -## SYNOPSIS - -Creates an App Management Service application. - - - -## SYNTAX - -``` -New-SPAppManagementServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseCredentials <PSCredential>] - [-DatabaseName <String>] [-DatabaseServer <String>] [-FailoverDatabaseServer <String>] [-Name <String>] - [-WhatIf] [-DeferUpgradeActions] [<CommonParameters>] -``` - -## DESCRIPTION -Use the New-SPAppManagementServiceApplication cmdlet to create an App Management Service application with the specified name on the specified application pool with a single database which specified parameters create. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE---------- -``` -New-SPAppManagementServiceApplication -Name AppManagement -DatabaseServer MyDatabaseServer -DatabaseName AppManagementDB -ApplicationPool MyServiceAppPool -``` - -This example creates an App Management Service application named AppManagement with a database server MyDatabaseServer and database name AppManagementDB. -The new service application will run under the app pool named MyServiceAppPool - -## PARAMETERS - -### -ApplicationPool -Specifies the application pool of the service application. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the credentials to use when creating the service application database. -These credentials will have owner rights on the newly created service application database. -If a value is not provided, the current user's credentials are used by default. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the service application database to be created. -If a value is not provided, a default database name is provided. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the server of the service application database to be created, If a value is not provided, the default database server is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the failover server of the service application database to be created, If a value is not provided, there will not be a failover server for the service application database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the service application to be created. -If not provided, the default name is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies if the upgrade process is to be deferred and manually completed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPAppManagementServiceApplicationProxy](New-SPAppManagementServiceApplicationProxy.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAppManagementServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAppManagementServiceApplicationProxy.md deleted file mode 100644 index 1762f3fd30..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAppManagementServiceApplicationProxy.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spappmanagementserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAppManagementServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAppManagementServiceApplicationProxy - -## SYNOPSIS - -Creates an App Management Service application proxy. - - - -## SYNTAX - -### ServiceApplication -``` -New-SPAppManagementServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Name <String>] [-UseDefaultProxyGroup] [-WhatIf] - [<CommonParameters>] -``` - -### Uri -``` -New-SPAppManagementServiceApplicationProxy -Uri <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Name <String>] [-UseDefaultProxyGroup] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the New-SPAppManagementServiceApplicationProxy cmdlet to create an App Management Service application proxy with the specified name for the specified App Management Service application or the specified endpoint. -Depending on the parameter value, it also adds the new proxy to the default proxy group. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE------------- -``` -$sa = New-SPAppManagementServiceApplication -Name AppManagement -DatabaseServer MyDatabaseServer -DatabaseName AppManagementDB -ApplicationPool MyServiceAppPool -New-SPAppManagementServiceApplicationProxy -Name AppManagementProxy -UseDefaultProxyGroup -ServiceApplication $sa -``` - -This example creates a new App Management Service application proxy named AppManagementProxy for the specified service application and adds the new App Management Service application proxy to the default proxy group. - -## PARAMETERS - -### -ServiceApplication -Specifies the App Management Service application for which you are creating the service application proxy. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: ServiceApplication -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Uri -Specifies the endpoint URI of the App Management Service application in which to create the service application proxy. - -```yaml -Type: String -Parameter Sets: Uri -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the service application proxy to be created. -If a value is not provided, a default name is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultProxyGroup -Specifies whether to add the newly created service application proxy to the default proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPAppManagementServiceApplication](New-SPAppManagementServiceApplication.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAuthenticationProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAuthenticationProvider.md deleted file mode 100644 index 43ec5ac0ad..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAuthenticationProvider.md +++ /dev/null @@ -1,238 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spauthenticationprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAuthenticationProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAuthenticationProvider - -## SYNOPSIS - -Creates a new authentication provider in the farm. - - - -## SYNTAX - -### Forms -``` -New-SPAuthenticationProvider -ASPNETMembershipProvider <String> -ASPNETRoleProviderName <String> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### Trusted -``` -New-SPAuthenticationProvider -TrustedIdentityTokenIssuer <SPTrustedIdentityTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### Windows -``` -New-SPAuthenticationProvider [-AllowAnonymous] [-AssignmentCollection <SPAssignmentCollection>] - [-DisableKerberos] [-UseBasicAuthentication] [-UseWindowsIntegratedAuthentication] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The New-SPAuthenticationProvider cmdlet creates a new authentication provider in the farm. - ---NTLM, Classic NTLM, Negotiate, and Classic Negotiate can be set only in a web application. ---For ASP.NET Membership Provider or Role providers, no objects are persisted. The object is created and used for setting this type of Authentication provider in a web application. ---For STS Authentication providers, an object is created and persisted in the SPFarm object. - -You cannot use classic NTLM with any claims-based authentication type. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------------------EXAMPLE1------------------ -``` -$ap = New-SPAuthenticationProvider -UseWindowsIntegratedAuthentication -Set-SPWebApplication -Name "Claims Windows Web App" -ApplicationPool "Claims App Pool" -ApplicationPoolAccount "redmond\appool" -Url http://<servername> -Port 80 -AuthenticationProvider $ap -``` - -This example creates a Windows claims authentication provider. - -### ---------------------------EXAMPLE2------------------ -``` -$ap = New-SPAuthenticationProvider -ASPNETMembershipProvider "membership" -ASPNETRoleProviderName "rolemanager" -Set-SPWebApplication -Name "Claims Windows Web App" -ApplicationPool "Claims App Pool" -ApplicationPoolAccount "redmond\appool" -Url http://<servername> -Port 80 -AuthenticationProvider $ap -``` - -This example creates an authentication provider that is based on the ASP.NET membership role provider. - -### ---------------------------EXAMPLE3------------------ -``` -$ap = New-SPAuthenticationProvider -TrustedIdentityTokenIssuer | Get-SPTrustedIdentityTokenIssuer "LiveIDSTS" -Set-SPWebApplication -Name "Claims Windows Web App" -ApplicationPool "Claims App Pool" -ApplicationPoolAccount "redmond\appool" -Url http://<servername> -Port 80 -AuthenticationProvider $ap -``` - -This example creates a trusted token issuer authentication provider. - -## PARAMETERS - -### -ASPNETMembershipProvider -Specifies the name of the membership provider. - -The value must be a valid name of an ASP.NET membership provider; for example, myMembershipProvider. - -```yaml -Type: String -Parameter Sets: Forms -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ASPNETRoleProviderName -Specifies the name of the role provider. - -The value must be a valid name of an ASP.NET role provider; for example, myRoleProvider. - -```yaml -Type: String -Parameter Sets: Forms -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedIdentityTokenIssuer -Specifies the identity of the authentication provider. - -The value must be in one of the following forms: - ---A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh ---A valid name of a TrustedIdentityTokenIssuer (for example, myRoleProvider) ---An instance of a valid SPTrustedIdentityTokenIssuer object - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: Trusted -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowAnonymous -Specifies whether the web application allows anonymous access. - -```yaml -Type: SwitchParameter -Parameter Sets: Windows -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DisableKerberos -Specifies whether the web application disables Kerberos authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: Windows -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseBasicAuthentication -Specifies whether the web application uses Basic authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: Windows -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseWindowsIntegratedAuthentication -Specifies whether the web application uses Integrated Windows authentication. - -```yaml -Type: SwitchParameter -Parameter Sets: Windows -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAzureAccessControlServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPAzureAccessControlServiceApplicationProxy.md deleted file mode 100644 index b9bcd6b92c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPAzureAccessControlServiceApplicationProxy.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spazureaccesscontrolserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPAzureAccessControlServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPAzureAccessControlServiceApplicationProxy - -## SYNOPSIS - -Creates a new service application proxy group. - - - -## SYNTAX - -``` -New-SPAzureAccessControlServiceApplicationProxy -MetadataServiceEndpointUri <String> -Name <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the New-SPAzureAccessContrlServiceApplicationProxy cmdlet to create a new service application proxy group for the Azure Control service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE-------------- -``` -New-SPAzureAccessControlServiceApplicationProxy -Name "ACS" -metadataEndpointUri "http://test/" -DefaultProxyGroup -``` - -This example creates a proxy group named ACS which will be added to the default proxy group. - -## PARAMETERS - -### -MetadataServiceEndpointUri -Specifies the URL of the Azure Access Control Service's metadata document. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the proxy that you want to create. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies whether the proxy needs to be added to the default proxy group. - -We recommend that you add the proxy to the default proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPBECWebServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPBECWebServiceApplicationProxy.md deleted file mode 100644 index a70e121abd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPBECWebServiceApplicationProxy.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spbecwebserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPBECWebServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPBECWebServiceApplicationProxy - -## SYNOPSIS -Do not use. - -## SYNTAX - -``` -New-SPBECWebServiceApplicationProxy [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DefaultProxyGroup] -Name <String> -ServiceEndpointUri <String> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------ Example 1 -------------------- -``` - -``` - -## PARAMETERS - -### -AssignmentCollection -Do not use. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceEndpointUri -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPBusinessDataCatalogServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPBusinessDataCatalogServiceApplication.md deleted file mode 100644 index 51a29e1a58..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPBusinessDataCatalogServiceApplication.md +++ /dev/null @@ -1,301 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spbusinessdatacatalogserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPBusinessDataCatalogServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPBusinessDataCatalogServiceApplication - -## SYNOPSIS - -Creates a new Business Data Connectivity service application in the farm. - - - -## SYNTAX - -``` -New-SPBusinessDataCatalogServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-DatabaseName <String>] [-DatabaseServer <String>] [-Name <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseCredentials <PSCredential>] - [-DatabasePassword <SecureString>] [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] - [-PartitionMode] [-Sharing] [-WhatIf] [-DeferUpgradeActions] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPBusinessDataCatalogServiceApplication cmdlet creates a new Business Data Connectivity service application in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPBusinessDataCatalogServiceApplication -ApplicationPool "SharePoint Web Services Default" -DatabaseName "ContosoBdcDB" -DatabaseServer "CONTOSO\SharePoint" -Name "ContosoServiceApp" -``` - -This example creates a Business Data Connectivity service application named ContosoServiceApp. -In this process it uses the SharePoint Web Services Default application pool and creates a database named ContosoBdcDB. - -## PARAMETERS - -### -ApplicationPool -Specifies the IIS application pool to use for the new Business Data Connectivity service application. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name for the Business Data Connectivity database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid SQL Server host name; for example, SERVER\Database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies a display name for the new Business Data Connectivity service application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Server Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user specified in DatabaseUserName. -Use this parameter only if SQL Server Authentication is used to access the Business Data Connectivity database. - -The type must be a valid password. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user name to use for connecting to the database. -Use this parameter only if SQL Server Authentication is used to access the Business Data Connectivity database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host server for the failover database server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restricts data by subscription ID. -This property cannot be changed after the service application is created. - -This property has no effect on SharePoint Server 2019. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Sharing -Specifies that the Business Data Connectivity application is published and shared across the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies if the upgrade process is to be deferred and manually completed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPBusinessDataCatalogServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPBusinessDataCatalogServiceApplicationProxy.md deleted file mode 100644 index 7653f044cb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPBusinessDataCatalogServiceApplicationProxy.md +++ /dev/null @@ -1,206 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spbusinessdatacatalogserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPBusinessDataCatalogServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPBusinessDataCatalogServiceApplicationProxy - -## SYNOPSIS - -Creates a new Business Data Connectivity service application proxy in the farm. - -## SYNTAX - -### PipeBind -``` -New-SPBusinessDataCatalogServiceApplicationProxy [-Name <String>] - -ServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DefaultProxyGroup] [-WhatIf] [<CommonParameters>] -``` - -### Uri -``` -New-SPBusinessDataCatalogServiceApplicationProxy [-Name <String>] -Uri <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-WhatIf] [-PartitionMode] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The New-SPBusinessDataCatalogServiceApplicationProxy cmdlet creates a new Business Data Connectivity service application proxy for a Business Data Connectivity service application in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$sa = New-SPBusinessDataCatalogServiceApplication -ApplicationPool "SharePoint Web Services Default" -DatabaseName "ContosoBdcDB" -DatabaseServer "CONTOSO\SharePoint" -Name "ContosoServiceApp" -New-SPBusinessDataCatalogServiceApplicationProxy -Name "ContosoServiceAppProxy" -ServiceApplication $sa -``` - -This example creates a new Business Data Connectivity service application proxy with the name ContosoServiceAppProxy for the given service application. - -## PARAMETERS - -### -Name -Specifies a display name for the new Business Data Connectivity service application proxy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the Business Data Connectivity service application associated with the new proxy. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: PipeBind -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Uri -Specifies the URI of a remote service application to which to connect. - -The type must be a valid URI, in the form file:\\\\server_name\sitedocs. - -```yaml -Type: Uri -Parameter Sets: Uri -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the service application proxy is added to the default proxy group for the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies if partition mode is to be turned on. - -The valid values are True and False. The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: Uri -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPCentralAdministration.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPCentralAdministration.md deleted file mode 100644 index 8ec50c1910..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPCentralAdministration.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spcentraladministration -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPCentralAdministration -schema: 2.0.0 ---- - -# New-SPCentralAdministration - -## SYNOPSIS - -Creates a new SharePoint Central Administration Web application. - - - -## SYNTAX - -``` -New-SPCentralAdministration [[-Port] <Int32>] [[-WindowsAuthProvider] <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-SecureSocketsLayer] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPCentralAdministration cmdlet creates a new Central Administration Web application and starts the central administration service on the local computer. -Central Administration is available only on computers where this service runs. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -New-SPCentralAdministration -WindowsAuthProvider NTLM -Port 8080 -``` - -This example creates the Central Administration site at port 8080 on the local farm using NTLM authentication. - - -### ------------------EXAMPLE 2----------------------- -``` -New-SPCentralAdministration -WindowsAuthProvider Kerberos -Port 443 -SecureSocketsLayer -``` - -This example creates the Central Administration site using SSL on port 443 with Kerberos authentication. - - -## PARAMETERS - -### -Port -Specifies the port number for Central Administration. -If no port is specified, a nonconflicting port number is auto-generated. - -The type must be a valid port number. - -If you specify a port number that has already been assigned, IIS does not start the new site until you change either the port number of the new site or the port number of the old site. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -WindowsAuthProvider -Specifies the authorization provider for this Web application. -If no authentication provider is specified, the default value NTLM is used. - -The type must be one of two values: Kerberos or NTLM. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SecureSocketsLayer -Enables Secure Socket Layer (SSL) encryption for the specified port. If you choose to use SSL, you must assign a server certificate to the Central Administration IIS web site by using the IIS administration tools. The Central Administration web application won't be accessible until you do this. - -The default value is False. - -If this parameter is omitted or set to False the Central Administration site will use HTTP for the specified port. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimProvider.md deleted file mode 100644 index 4848e85e15..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimProvider.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spclaimprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPClaimProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPClaimProvider - -## SYNOPSIS - -Registers a new claim provider in the farm. - - - -## SYNTAX - -``` -New-SPClaimProvider -AssemblyName <String> -Description <String> -DisplayName <String> -Type <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Default] [-Enabled] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPClaimProvider cmdlet registers a new claim provider in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -New-SPClaimProvider -Name "MyClaimProvider" -Type "MyClaimProvider.Providers.CustomProvider" -AllWebApplications -``` - -This example registers a claim provider in the farm. - -### ------------------EXAMPLE 2------------------ -``` -New-SPClaimProvider -Name "MyClaimProvider" -Type "MyClaimProvider.Providers.CustomProvider" -Scope (Get-SPWebApplication https://test) -``` - -This example registers a claim provider scoped to a given Web application. - -## PARAMETERS - -### -AssemblyName -The type must be a valid name of an assembly; for example, ClaimAssembly1. - -Specifies the name of the assembly with the claim provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the claim provider. - -The type must be a valid name of an assembly; for example, ClaimAssembly1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -Specifies the display name of the new claim provider. - -The type must be a valid name of a claim provider; for example, ClaimProvider1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type of the claim. - -The type must be a valid name of a claim type; for example MyClaimProvider.Providers.CustomProvider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Default -Specifies that the claim provider applies to all Web applications and zones. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -Turns on the claim provider. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimTypeEncoding.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimTypeEncoding.md deleted file mode 100644 index 1ac4c6cbac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimTypeEncoding.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spclaimtypeencoding -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPClaimTypeEncoding -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPClaimTypeEncoding - -## SYNOPSIS - -Registers a new type of claim. - - - -## SYNTAX - -``` -New-SPClaimTypeEncoding -ClaimType <String> -EncodingCharacter <Char> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the New-SPClaimTypeEncoding cmdlet to register the following: - ---A new type of claim - ---The Unicode character to which it should be encoded when the SPClaim.ToEncodedString method is invoked - ---The SPClaim.ClaimType property is set to a valid valu -e - -For more information about the SPClaim methods and properties, see M:Microsoft.SharePoint.Administration.Claims.SPClaim.ToEncodedString and P:Microsoft.SharePoint.Administration.Claims.SPClaim.ClaimType respectively. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ------------EXAMPLE------- -``` -New-SPClaimTypeEncoding -EncodingCharacter '1' -ClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/country" -``` - -This example registers a new type of claim. - -## PARAMETERS - -### -ClaimType -Specifies the type of claim for which you want to create a mapping. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncodingCharacter -Specifies the Unicode character to which you want to create a mapping. - -```yaml -Type: Char -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses confirmation messages to any claim type that is added. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPClaimTypeEncoding](Get-SPClaimTypeEncoding.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimTypeMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimTypeMapping.md deleted file mode 100644 index 73ff0896af..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimTypeMapping.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spclaimtypemapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPClaimTypeMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPClaimTypeMapping - -## SYNOPSIS - -Creates a claim mapping rule for a security token service (STS) identity provider. - -## SYNTAX - -``` -New-SPClaimTypeMapping [-IncomingClaimType] <String> [-IncomingClaimTypeDisplayName] <String> - [[-LocalClaimType] <String>] [-AssignmentCollection <SPAssignmentCollection>] [-SameAsIncoming] - [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPClaimTypeMapping cmdlet creates a claim mapping rule for a security token service (STS) identity provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE 1---------------------------- -``` -$map1 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" -IncomingClaimTypeDisplayName "EmailAddress" -SameAsIncoming -$map2 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier" -IncomingClaimTypeDisplayName "PUID" -LocalClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/thumbprint" -New-SPTrustedIdentityTokenIssuer -Name "LiveIDSTS" -Description "LiveID Provider" -Realm "urn:domain.company.com" -ImportTrustCertificate $cert -ClaimsMappings $map1[,$map2..] -SignInUrl "https://login.live.com/login.srf" -IdentifierClaim $map2.InputClaimType -``` - -This example creates a claim map from an incoming token to a SharePoint token. - -## PARAMETERS - -### -IncomingClaimType -Specifies the URI of the incoming claim type. - -The type must be a valid URI, in the form http://schemas.microsoft.com/email. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncomingClaimTypeDisplayName -Specifies the display name of the incoming claim type. - -The type must be a valid name of an incoming claim type; for example, Email. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalClaimType -Specifies the URI of the local claim type. -If the SameAsIncoming parameter is False, this is a required parameter. - -The type must be a valid URI, in the form http://schemas.microsoft.com/email. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SameAsIncoming -Specifies that the claim type specified in the IncomingClaimType parameter is used for the LocalClaimType parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimsPrincipal.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimsPrincipal.md deleted file mode 100644 index 86104c6555..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimsPrincipal.md +++ /dev/null @@ -1,300 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spclaimsprincipal -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPClaimsPrincipal -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPClaimsPrincipal - -## SYNOPSIS - -Creates a claims principal. - - - -## SYNTAX - -### STSIdentity -``` -New-SPClaimsPrincipal [-ClaimValue] <String> [[-ClaimType] <String>] - [-TrustedIdentityTokenIssuer] <SPTrustedIdentityTokenIssuerPipeBind> [-IdentifierClaim] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### ClaimProvider -``` -New-SPClaimsPrincipal [-ClaimValue] <String> [-ClaimType] <String> - [-AssignmentCollection <SPAssignmentCollection>] -ClaimProvider <SPClaimProvider> [<CommonParameters>] -``` - -### BasicClaim -``` -New-SPClaimsPrincipal [-EncodedClaim] <String> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### IdentityType -``` -New-SPClaimsPrincipal [-Identity] <String> [-IdentityType] <SPIdentifierTypes> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### TrustIdentity -``` -New-SPClaimsPrincipal [-Identity] <String> [-TrustedIdentityTokenIssuer] <SPTrustedIdentityTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The New-SPClaimsPrincipal cmdlet creates a claims principal. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------------EXAMPLE 1----------------------------- -``` -New-SPSite https://sitename/sites/newsite -owner (New-SPClaimsPrincipal contoso\johndoe -TrustedIdentityTokenIssuer "NTLM") -``` - -This example creates a claim principal for a Windows user. - -### -------------------------EXAMPLE 2----------------------------- -``` -New-SPSite https://localhost/sites/newsite -owner (New-SPClaimsPrincipal contoso\allusers -TrustedIdentityTokenIssuer "NTLM") -``` - -This example creates a claim principal for a Windows group. - -### -------------------------EXAMPLE 3----------------------------- -``` -New-SPSite https://sitename/sites/newsite -owner (New-SPClaimsPrincipal -ClaimValue "john@contoso.com" -ClaimType Email -TrustedIdentityTokenIssuer "LiveID STS" -IdentifierClaim Yes) -``` - -This example creates a claim principal for a trusted identity token issuer claim. - -### -------------------------EXAMPLE 4----------------------------- -``` -$ip = New-SPIdentityProvider -ASPNetMembershipProvider "myMembershipProvider" -ASPNetRoleProvider "myRoleProvider" -New-SPSite https://sitename/sites/newsite -owner (New-SPClaimsPrincipal "john@contoso.com" -TrustedIdentityTokenIssuer $ip) -``` - -This example creates a claim principal for a ASPNet Membership User. - -### -------------------------EXAMPLE 5----------------------------- -``` -New-SPSite https://sitename/sites/newsite -owner (New-SPClaimsPrincipal "Sales Manager Role" -IdentityProvider "myRoleProvider") -``` - -This example creates a claim principal for a ASPNet Role. - -### -------------------------EXAMPLE 6----------------------------- -``` -$cp = New-SPClaimsPrincipal -Identity "redmond\SiteOwner" -IdentityType 1 -New-SPSite https://servername:port -OwnerAlias $cp.ToEncodedString() -Template "STS#0" -``` - -This example creates a claim principal for a Basic Claim Role, which is also called an encoded claim). - -## PARAMETERS - -### -ClaimValue -Specifies the claim value of the claims object. -The claims value specifies the user, group, or computer that the claim is authenticating. - -The type must be a valid claim value; for example, john@contoso.com. - -```yaml -Type: String -Parameter Sets: STSIdentity, ClaimProvider -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -EncodedClaim -Converts a simple claim to a full encoded claim. - -The type must be a valid claim value; for example, i:001w|redmond\user. - -```yaml -Type: String -Parameter Sets: BasicClaim -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the name of the new claims principal. - -The type must be a valid name of a claims principal. - -```yaml -Type: String -Parameter Sets: IdentityType, TrustIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClaimType -Specifies the type of claim to create. -The value I indicates a unique user identity claim, and the value C indicates all other claims. - -The type must be either of the following values: I or C. - -```yaml -Type: String -Parameter Sets: STSIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: ClaimProvider -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedIdentityTokenIssuer -Specifies the ID of the authentication provider. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of an Authentication provider (for example, MyAuthprovider1); or an instance of a valid SPTrustedIdentityTokenIssuer object. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: STSIdentity, TrustIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IdentityType -Specifies the type of the new claims principal. - -The type must be one of the following: WindowsSamAccountName, WindowsSecurityGroupSid, FormsUser, FormsRole, or EncodedClaim. - -```yaml -Type: SPIdentifierTypes -Parameter Sets: IdentityType -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IdentifierClaim -Specifies if the new claim is an identity claim. - -```yaml -Type: SwitchParameter -Parameter Sets: STSIdentity -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClaimProvider -Specifies the security token service identity provider that will contain the claims principal. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of identity provider (for example, MyIDprovider1); or an instance of a valid SPIdentityProvider object. - -```yaml -Type: SPClaimProvider -Parameter Sets: ClaimProvider -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPConfigurationDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPConfigurationDatabase.md deleted file mode 100644 index cf41803694..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPConfigurationDatabase.md +++ /dev/null @@ -1,333 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spconfigurationdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPConfigurationDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPConfigurationDatabase - -## SYNOPSIS - -Creates a new configuration database. - - - -## SYNTAX - -``` -New-SPConfigurationDatabase [-DatabaseName] <String> [-DatabaseServer] <String> [[-DirectoryDomain] <String>] - [[-DirectoryOrganizationUnit] <String>] [[-AdministrationContentDatabaseName] <String>] - [[-DatabaseCredentials] <PSCredential>] [-FarmCredentials] <PSCredential> [-Passphrase] <SecureString> - [-SkipRegisterAsDistributedCacheHost] [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseFailOverServer <String>] [-LocalServerRole <SPServerRole>] [-ServerRoleOptional] - [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPConfigurationDatabase cmdlet creates a new configuration database on the specified database server. -This is the central database for a new SharePoint farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -New-SPConfigurationDatabase -DatabaseName "SharePointConfigDB1" -DatabaseServer "SQL-01" -Passphrase (ConvertTo-SecureString "MyPassword" -AsPlainText -force) -FarmCredentials (Get-Credential) -``` - -This example prompts the user to provide user credentials for the default Farm Administrator account. - -### ------------------EXAMPLE 2----------------------- -``` -New-SPConfigurationDatabase -DatabaseName "SharePointConfigDB1" -DatabaseServer "SQL-01" -Passphrase (ConvertTo-SecureString "MyPassword" -AsPlainText -force) -FarmCredentials (Get-Credential) -SkipRegisterAsDistributedCacheHost -``` - -This example prompts the user to provide user credentials for the default Farm Administrator account and skips registering the server as Distributed Cache host. Applies to SharePoint Server 2013 and SharePoint Server 2016, SharePoint Server 2019 only. - -### ------------------EXAMPLE 3----------------------- -``` -New-SPConfigurationDatabase -DatabaseName "SharePointConfigDB1" -DatabaseServer "SQL-01" -Passphrase (ConvertTo-SecureString "MyPassword" -AsPlainText -force) -FarmCredentials (Get-Credential) -LocalServerRole Custom -``` - -This example prompts the user to provide user credentials for the default Farm Administrator account and sets the Server Role to Custom. Applies to SharePoint Server 2016, SharePoint Server 2019 only. - -## PARAMETERS - -### -DatabaseName -Specifies the name of the new configuration database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the database server on which to create the configuration database. -If no value is specified, the default value is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -DirectoryDomain -Specifies the directory domain for the new farm. -If no domain is specified, the domain in which the local computer is located is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DirectoryOrganizationUnit -Specifies the directory organizational unit for the new configuration database. -If no organizational unit is specified, the organizational unit in which the local computer is located is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AdministrationContentDatabaseName -Specifies the name for the Central Administration content database for the new farm. -If no name is specified, a default name is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the Credential object for the database user. -Use this parameter if you use SQL Server Authentication. -If no database credentials are provided, Windows authentication is used. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 6 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -FarmCredentials -Specifies credentials for the Farm Administrator account. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 7 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Passphrase -Specifies the secure password phrase for the new farm. -This passphrase is used to join other machines to this farm. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 8 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -SkipRegisterAsDistributedCacheHost -By default all the servers in the farm are registered as a cache host (that is, DistributedCacheService is running by default). - -Use this parameter to not register the server computer as a distributed cache host. -If you want to have a dedicated cache host, then use this parameter to make sure that caching service is not installed on the computer. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 9 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseFailOverServer -Specifies the SQL Server Database Mirror partner server for the Configuration and Central Administration database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -LocalServerRole -Specifies the Server Role. Valid options for all versions of SharePoint Server 2016, SharePoint Server 2019 are: -`Custom`, `SingleServerFarm`, `Application`, `WebFrontEnd`, `DistributedCache`, `Search` - -With the addition of Feature Pack 1, new options include: -`ApplicationWithSearch`, `WebFrontEndWithDistributedCache ` - -```yaml -Type: SPServerRole -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServerRoleOptional -Configures the farm to not require a server role to be specified. If no server role is specified, the server defaults to the Custom role. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteMapDatabaseName -Do not use. Specifies the database name of the Site Map site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteMapDatabaseServer -Do not use. Specifies the database server name of the Site Map site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDatabase.md deleted file mode 100644 index c6cac2a31b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDatabase.md +++ /dev/null @@ -1,301 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPContentDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPContentDatabase - -## SYNOPSIS - -Creates a new content database and attaches it to the specified Web application. - - - -## SYNTAX - -``` -New-SPContentDatabase [-Name] <String> [-WebApplication] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-AssignNewDatabaseId] [-Confirm] [-ClearChangeLog] - [-DatabaseCredentials <PSCredential>] [-DatabaseServer <String>] [-MaxSiteCount <Int32>] - [-WarningSiteCount <Int32>] [-WhatIf] [-ChangeSyncKnowledge] [-DatabaseAccessCredentials <PSCredential>] - [-UseLatestSchema] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPContentDatabase cmdlet creates a new content database and attaches it to the specified Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE-------------------- -``` -New-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication https://sitename -``` - -This example creates a new content database for the sitename Web application. - -## PARAMETERS - -### -Name -Specifies the new content database to create within the farm. - -The type must be a valid name of a SharePoint content database; for example, SPContentDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Attaches the content database to the specified SharePoint Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignNewDatabaseId -Creates a new database ID automatically when the content database is attached. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClearChangeLog -Clears any pending changes from the change log in the content database. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Server Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the content database specified in the Name parameter. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSiteCount -Specifies the maximum number of Web sites that can use the content database. - -The type must be a positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarningSiteCount -Specifies the number of sites that can be created before a warning event is generated and the owner of the site collection is notified. - -The type must be a positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChangeSyncKnowledge -Specifies Groove sync client to resync their content when a Content Database attach is used. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseAccessCredentials -Specifies the credential for the SPDataAccess role. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseLatestSchema -Specifies to use the latest schema. In an on-premises environment, this parameter will have no effect at all. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDeploymentJob.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDeploymentJob.md deleted file mode 100644 index e6cb4deb47..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDeploymentJob.md +++ /dev/null @@ -1,325 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spcontentdeploymentjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPContentDeploymentJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPContentDeploymentJob - -## SYNOPSIS -Creates a content deployment job. - -## SYNTAX - -``` -New-SPContentDeploymentJob -Name <String> -SPContentDeploymentPath <SPContentDeploymentPathPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] - [-EmailAddresses <String[]>] [-EmailNotifications <ContentDeploymentNotificationSettings>] - [-HostingSupportEnabled] [-IncrementalEnabled] [-Schedule <String>] [-ScheduleEnabled] - [-Scope <SPWebPipeBind[]>] [-SqlSnapshotSetting <ContentDeploymentSqlSnapshotSetting>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPContentDeploymentJob cmdlet adds a new content deployment job to a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPContentDeploymentPath "Path 1" | New-SPContentDeploymentJob -Name "Deployment Job" -SPContentDeploymentPath $_ -IncrementalEnabled:$true -ScheduleEnabled:$false -``` - -This example creates a new content deployment job called Deployment Job by using the deployment path Path 1. -The job is configured to be an incremental job with no schedule. - -## PARAMETERS - -### -Name -Specifies the name of the new content deployment job. - -The type must be a valid name of a content deployment job; for example, DeployJob1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SPContentDeploymentPath -Specifies the deployment path to associate with the new deployment job. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment job (for example; DeployJob1); or an instance of a valid SPContentDeploymentJob object. - -```yaml -Type: SPContentDeploymentPathPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description for the content deployment job. -The name can be a maximum of 4096 alphanumeric characters. - -The type must be a valid string. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -Specifies the e-mail addresses of individuals who receive notification e-mails about this ContentDeploymentJob object. - -The type must be a list of valid e-mail addresses. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailNotifications -Specifies how e-mail notifications are sent about this ContentDeploymentJob object. - -The type must be one of the following: - --Never specifies that e-mail notifications will not be sent when a job succeeds or fails. - -- SendEmailOnSuccess specifies that e-mail notifications will be sent if a content deployment job succeeds. -- SendEmailOnFailure specifies that e-mail notifications will be sent if a content deployment job fails. -- SendEmailOnAlways specifies that e-mail notifications will be sent when a job succeeds or fails. - -```yaml -Type: ContentDeploymentNotificationSettings -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostingSupportEnabled -Enables special hosting- behavior. -The default value is False. - -Normally, a content deployment job is enabled or disabled by using the SharePoint Central Administration Web site. -However, in the case of hosting, the tenant administrator does not have permissions to access the Central Administration page to configure jobs. -Therefore, when the HostingSupportEnabled parameter is set to True, the hoster creates the job, so that tenants can enable or disable their deployment jobs from their tenant administration site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncrementalEnabled -Specifies that only incremental changes are deployed to the destination site collection. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Schedule -Sets the schedule for the deployment job. - -The type must be a valid SPSchedule object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScheduleEnabled -Specifies to enable the schedule for the deployment job. -If the schedule is not enabled the job can be run only manually. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Sets the scope of the deployment job. -SPSites passed in must exist in the current path of the source site collection. -The default scope is the entire site collection. -Valid values include an SPWeb object or an array of SPWeb objects. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint Foundation Web site (for example, MySPSite1); or an instance of a valid SPWeb object. - -```yaml -Type: SPWebPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SqlSnapshotSetting -Creates a database snapshot of the source SharePoint Foundation content database to use for the export process. - -The type must be one of the following values: - -- None -- CreateNew - -The CreateNew value requires thatSQL Server Enterprise Edition be installed. - -```yaml -Type: ContentDeploymentSqlSnapshotSetting -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDeploymentPath.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDeploymentPath.md deleted file mode 100644 index 7209a8cc5f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPContentDeploymentPath.md +++ /dev/null @@ -1,387 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spcontentdeploymentpath -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPContentDeploymentPath -schema: 2.0.0 ---- - -# New-SPContentDeploymentPath - -## SYNOPSIS -Creates a new content deployment path. - -## SYNTAX - -``` -New-SPContentDeploymentPath -DestinationCentralAdministrationURL <Uri> -DestinationSPSite <String> - -DestinationSPWebApplication <Uri> -Name <String> -PathAccount <PSCredential> -SourceSPSite <SPSitePipeBind> - -SourceSPWebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Authentication <PathAuthenticationOption>] [-CompressionEnabled] [-Confirm] - [-DeploySecurityInformation <SPIncludeSecurity>] [-DeployUserNamesEnabled] [-Description <String>] - [-EventReceiversEnabled] [-KeepTemporaryFilesOptions <TemporaryFilesOption>] [-PathEnabled] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPContentDeploymentPath cmdlet adds a new content deployment path for a content deployment job. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE---------------------- -``` -C:\PS>$source = Get-SPSite "http://source/" - -C:\PS>$credentials=Get-Credential - -New-SPContentDeploymentPath -Name "Deployment Path" -SourceSPWebApplication $source.WebApplication -SourceSPSite $source DestinationCentralAdministrationURL "http://destination:8080/" -DestinationSPWebApplication "http://destination/" -DestinationSPSite "http://destination/" -KeepTemporaryFilesOptions "Failure" -PathAccount $credentials -PathEnabled:$true -``` - -This example creates a new deployment path called Deployment Path that connects a source at http://source to a destination at http://destination. -The path is enabled and configured to keep temporary files on job failure. - -## PARAMETERS - -### -DestinationCentralAdministrationURL -Specifies the SharePoint Central Administration URL for the destination farm. - -The type must be a valid URL, in the form http://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DestinationSPSite -Specifies the destination site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form http://server_name; or an instance of a valid SPSite object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DestinationSPWebApplication -Specifies the destination Web application. - -The type must be a valid URL, in the form http://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new content deployment path. - -The type must be a valid name of a content deployment path; for example, DeployPath1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PathAccount -Specifies the user ID that is an administrator on the Central Administration page on the destination farm. - -The type must be a valid SharePoint user. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceSPSite -Specifies the source site collection for the deployment path. -Must be a site collection in the source specified in the SourceSPWebApplication parameter. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form http://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceSPWebApplication -Specifies the source Web application for the deployment path. - -The type must be a valid URL, in the form http://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Authentication -Sets the Windows-based authentication type that the source front-end Web server uses to communicate with the destination Web application. - -The type must be one of the following values: WindowsAuth or BasicAuth. - -```yaml -Type: PathAuthenticationOption -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompressionEnabled -Turns on compression during the export. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeploySecurityInformation -Specifies the user and group information to include during the export operation for this content deployment path. -The default value is All. - -The type must be one of the following values: None, All, or WssOnly- Applies only SharePoint Foundation security settings. -Includes user memberships and role assignments such as default roles, for example, Web Designer or any custom roles that extend from the default roles. -The access control list (ACL) for each object is migrated. -No user information defined in the DAP or LDAP servers is included. - -```yaml -Type: SPIncludeSecurity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeployUserNamesEnabled -Specifies whether to include user names during a deployment. - -Valid values are one of the following: - -- $True Retains the original author and editor information, time and date stamp, and user lookup value. -- $False Retains the original date and time stamp, but replaces the author and editor data with the System Account, and replaces the user lookup value with an empty string (""). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Sets the description for the content deployment path. -The description can contain a maximum of 4096 alphanumeric characters. - -The type must be a valid string. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventReceiversEnabled -Turns on event receivers during import. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepTemporaryFilesOptions -Specifies that temporary files are kept after content deployment is finished. - -The type must be one of the following values: Never, Always, or OnFailure. - -```yaml -Type: TemporaryFilesOption -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PathEnabled -Enables the new content deployment path. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEduClass.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEduClass.md deleted file mode 100644 index ce850ffc64..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEduClass.md +++ /dev/null @@ -1,249 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-speduclass -applicable: SharePoint Server 2013 -title: New-SPEduClass -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEduClass - -## SYNOPSIS -Do not use - -## SYNTAX - -``` -New-SPEduClass [-AssignmentCollection <SPAssignmentCollection>] [-Building <String>] -ClassId <String> - -ClassName <String> [-DayOfWeek <String>] [-EndDate <DateTime>] [-EndTime <String>] [-Room <String>] - -Site <SPSitePipeBind> [-StartDate <DateTime>] [-StartTime <String>] [-Year <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use - -## EXAMPLES - -### Example 1 -``` -Do not use -``` - - - -## PARAMETERS - -### -AssignmentCollection -Do not use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Building -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ClassId -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ClassName -{Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -DayOfWeek -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -EndDate -Do not use - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -EndTime -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Room -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Site -Do not use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -StartDate -Do not use - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -StartTime -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Year -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -Microsoft.SharePoint.PowerShell.SPSitePipeBind -System.Nullable`1[[System.DateTime, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]] -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchAdminComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchAdminComponent.md deleted file mode 100644 index 36dd17119c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchAdminComponent.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchadmincomponent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchAdminComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchAdminComponent - -## SYNOPSIS -Creates a new admin component for the given topology and search service instance. - -## SYNTAX - -``` -New-SPEnterpriseSearchAdminComponent -SearchServiceInstance <SearchServiceInstancePipeBind> - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new search admin component and adds it to an inactive search topology in a specific search service instance. -The change is effectuated when the search topology is enabled. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$si = Get-SPEnterpriseSearchServiceInstance -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -New-SPEnterpriseSearchAdminComponent -SearchTopology $topology -SearchServiceInstance $si -SearchApplication $ssa -``` - -This example adds a new Search Administration Component to the inactive topology for the existing Search Service Application. - -## PARAMETERS - -### -SearchServiceInstance - -Specifies the search service instance that will host the new admin component. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology where the new admin component should be added. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchAnalyticsProcessingComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchAnalyticsProcessingComponent.md deleted file mode 100644 index af1a6825d2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchAnalyticsProcessingComponent.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchanalyticsprocessingcomponent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchAnalyticsProcessingComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchAnalyticsProcessingComponent - -## SYNOPSIS -Creates a new analytics processing component for the given topology and search service instance. - -## SYNTAX - -``` -New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchServiceInstance <SearchServiceInstancePipeBind> - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new analytics processing component and adds it to an inactive search topology in a specific search service instance. -The change is effectuated when the search topology is enabled. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$si = Get-SPEnterpriseSearchServiceInstance -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $topology -SearchServiceInstance $si -SearchApplication $ssa -``` - -This example adds a new Search Analytics Processing Component to the inactive topology for the existing Search Service Application. - -## PARAMETERS - -### -SearchServiceInstance - -Specifies the search service instance that will host the new analytics processing component. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology where the new analytics processing component should be added. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchContentEnrichmentConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchContentEnrichmentConfiguration.md deleted file mode 100644 index 0382292f1a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchContentEnrichmentConfiguration.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcontentenrichmentconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchContentEnrichmentConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchContentEnrichmentConfiguration - -## SYNOPSIS -Creates a new ContentEnrichmentConfiguration object. - -## SYNTAX - -``` -New-SPEnterpriseSearchContentEnrichmentConfiguration [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new ContentEnrichmentConfiguration object that the user can change. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$config = New-SPEnterpriseSearchContentEnrichmentConfiguration -``` - -This example creates a new ContentEnrichmentConfiguration object. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchContentEnrichmentConfiguration](Get-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[Set-SPEnterpriseSearchContentEnrichmentConfiguration](Set-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[Remove-SPEnterpriseSearchContentEnrichmentConfiguration](Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchContentProcessingComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchContentProcessingComponent.md deleted file mode 100644 index 8790505899..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchContentProcessingComponent.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcontentprocessingcomponent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchContentProcessingComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchContentProcessingComponent - -## SYNOPSIS -Creates a new content processing component for the given topology and search service instance. - -## SYNTAX - -``` -New-SPEnterpriseSearchContentProcessingComponent -SearchServiceInstance <SearchServiceInstancePipeBind> - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new content processing component and adds it to an inactive search topology in a specific search service instance. -The change is effectuated when the search topology is enabled. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$si = Get-SPEnterpriseSearchServiceInstance -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $topology -SearchServiceInstance $si -SearchApplication $ssa -``` - -This example adds a new Search Content Processing Component to the inactive topology for the existing Search Service Application. - -## PARAMETERS - -### -SearchServiceInstance - -Specifies the search service instance that will host the new content processing component. - - - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology where the new content processing component should be added. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlComponent.md deleted file mode 100644 index 5d2b1abfc8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlComponent.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcrawlcomponent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchCrawlComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchCrawlComponent - -## SYNOPSIS -Creates a new crawl component for the given topology and search service instance. - -## SYNTAX - -``` -New-SPEnterpriseSearchCrawlComponent -SearchServiceInstance <SearchServiceInstancePipeBind> - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new crawl component and adds it to an inactive search topology in a specific search service instance. -The change is effectuated when the search topology is enabled. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$si = Get-SPEnterpriseSearchServiceInstance -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -New-SPEnterpriseSearchCrawlComponent -SearchTopology $topology -SearchServiceInstance $si -SearchApplication $ssa -``` - -This example adds a new Search Crawl Component to the inactive topology for the existing Search Service Application. - -## PARAMETERS - -### -SearchServiceInstance - -Specifies the search service instance that will host the new crawl component. - - - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology where the new crawl component should be added. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlContentSource.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlContentSource.md deleted file mode 100644 index b037df192d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlContentSource.md +++ /dev/null @@ -1,372 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcrawlcontentsource -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchCrawlContentSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchCrawlContentSource - -## SYNOPSIS -Creates a content source for a Search service application. - -## SYNTAX - -``` -New-SPEnterpriseSearchCrawlContentSource [-AssignmentCollection <SPAssignmentCollection>] - [-BDCApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm] - [-CrawlPriority <CrawlPriority>] [-CustomProtocol <String>] [-LOBSystemSet <String[]>] - [-MaxPageEnumerationDepth <Int32>] [-MaxSiteEnumerationDepth <Int32>] -Name <String> - -SearchApplication <SearchServiceApplicationPipeBind> [-SharePointCrawlBehavior <SharePointCrawlBehavior>] - [-StartAddresses <String>] [-Tag <String>] -Type <ContentSourceType> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPEnterpriseSearchCrawlContentSource cmdlet creates a new content source. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchCrawlContentSource -SearchApplication $ssa -Type File -name FileServer -StartAddresses file://someserver/public -``` - -This example creates a new content source of type file to crawl a file system. - -## PARAMETERS - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BDCApplicationProxyGroup - -Specifies the proxy to use for a business type content source. -This proxy group must contain a default Business Data Connectivity Metadata Store proxy. - - - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlPriority - -Specifies the priority of this content source. - -The value must be one of the following integers: 1= Normal, 2=High. - - - -```yaml -Type: CrawlPriority -Parameter Sets: (All) -Aliases: p -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomProtocol - -Specifies the custom protocol, handled by the custom connector, to use for this content source. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LOBSystemSet - -Specifies a comma-separated list of Business Data Connectivity metadata store system names and system instance names for a business type content source. - - - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxPageEnumerationDepth - -Specifies, for a web or custom type content source, the number of page hops that the crawler can make from the start address to a content item. - - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSiteEnumerationDepth - -Specifies, for a web or custom type content source, the number of site hops that the crawler can take from the start address to a content item. - - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name - -Specifies the name of the content source to create. - -The type must be a valid name of a ContentSource object (for example, ContentSource1). - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication - -Specifies the search application that contains the content source. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid Search service application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SharePointCrawlBehavior - -Specifies crawl behavior for a sharepoint type content source. -The behavior can be either: - -CrawlSites to crawl only particular site collections. - -CrawlVirtualServers to crawl the entire server and all site collections on the server. - - - -```yaml -Type: SharePointCrawlBehavior -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartAddresses - -Specifies the comma-separated list of URLs at which to start a crawl for this content source. - -The type must be a valid URL, in the form https://server_name. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: s -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tag - -Specifies the URL for the page to modify the settings for a custom content source. -The string that specifies the URL can contain a maximum of 1,024 characters. - -The type must be a valid URL, in the form https://server_name. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type - -Specifies the name of the content source type. -The value Business is for the Business Data Connectivity metadata store. -The value Exchange is for Microsoft Exchange public folders. -The value Custom is for a custom content source type. - -The type must be the valid name of a content source type; for example, custom. - - - -```yaml -Type: ContentSourceType -Parameter Sets: (All) -Aliases: t -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlCustomConnector.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlCustomConnector.md deleted file mode 100644 index b9148d3dc7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlCustomConnector.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcrawlcustomconnector -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchCrawlCustomConnector -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchCrawlCustomConnector - -## SYNOPSIS -Registers a protocol for custom crawling. - -## SYNTAX - -``` -New-SPEnterpriseSearchCrawlCustomConnector -ModelFilePath <String> -Protocol <String> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPEnterpriseSearchCrawlCustomConnector cmdlet registers, for a search system, the protocol that is used to crawl the custom repository. - -If the Name parameter is not provided, in the administration application user interface (UI) the name protocol identifies the protocol specified. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchCrawlCustomConnector -SearchApplication $ssa -ModelFilePath \\models\myFileTypeModel.mft -Protocol "mftml://" -``` - -This example creates a custom connector for a file type whose model is located at \\\\models\myFileTypeModel.mft and has the protocol name mftml://. - -## PARAMETERS - -### -ModelFilePath -Specifies the path to a model file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Protocol -Specifies the string version of the protocol; for example, dctm://. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that is associated with the protocol. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name of the custom connector that appears on the SharePoint Central Administration Web site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlDatabase.md deleted file mode 100644 index fd20e0ae0f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlDatabase.md +++ /dev/null @@ -1,214 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcrawldatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchCrawlDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchCrawlDatabase - -## SYNOPSIS -Creates a crawl database which can be added to a search service application. - -## SYNTAX - -``` -New-SPEnterpriseSearchCrawlDatabase -DatabaseName <String> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] - [-FailoverDatabaseServer <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPEnterpriseSearchCrawlDatabase cmdlet is used during initial configuration and farm scale-out to create a new crawl database, which can be added to a search service application. -A crawl database stores crawl history for a search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchCrawlDatabase -SearchApplication $ssa -DatabaseName newCrawlDB -``` - -This example creates a new crawl database named newCrawlDB for the mySearchServiceApp search service application. - -## PARAMETERS - -### -DatabaseName -Specifies the name of the database to create for the crawl database. - -The type must be a valid name of a SQL Server database; for example, CrawlStoreDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl database. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the name of the password for the Microsoft SQL Server database server. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the account name specified in the Database Server parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Server that is used for failover when SQL Server mirroring is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlExtension.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlExtension.md deleted file mode 100644 index ae728f5cf2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlExtension.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcrawlextension -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchCrawlExtension -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchCrawlExtension - -## SYNOPSIS -Adds an extension rule to a Search service application. - -## SYNTAX - -``` -New-SPEnterpriseSearchCrawlExtension [[-Name] <String>] -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The New-SPEnterpriseSearchCrawlExtension cmdlet adds a file name extension to the list of file types that you want to include in the index. -After a new IFilter is registered, run this cmdlet so that the new file type will be crawled. -If a file type is added without registering an associated IFilter, only the file properties will be crawled and included in the index. -After you run this cmdlet, you must run a full crawl of all content sources that might contain this file type to guarantee that files of this type are in the index. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchCrawlExtension -Name "pdf" -SearchApplication $ssa -``` - -This example adds the PDF file type to the list of file name extensions to include in the index. - -## PARAMETERS - -### -Name -Specifies the new file name extension. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the extension collection. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid search application name (for example, SearchApp1), or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlMapping.md deleted file mode 100644 index 55fde44732..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlMapping.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcrawlmapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchCrawlMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchCrawlMapping - -## SYNOPSIS -Creates a crawl mapping rule for a shared search application. - -## SYNTAX - -``` -New-SPEnterpriseSearchCrawlMapping [-Url] <String> -SearchApplication <SearchServiceApplicationPipeBind> - -Target <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -The New-SPEnterpriseSearchCrawlMapping cmdlet is run when the search functionality is initially configured, and when access is changed through a different mechanism to create the crawl mapping rule; for example, when a rule is changed to use file:\\\\ rather than http://. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchCrawlMapping -SearchApplication $ssa -Url "file://location1" -Target "https://location2/" -``` - -This example will change the query results link from the file share where the item was crawled to the Web site location from which the item can be browsed. - -## PARAMETERS - -### -Url -Specifies the source URI for the crawl mapping. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl mapping collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Target -Specifies the target URI for the crawl mapping to get. - -The type must be a valid URI; for example, file:\\\\ server_name\sitedocs. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: t -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlRule.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlRule.md deleted file mode 100644 index 311c850586..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchCrawlRule.md +++ /dev/null @@ -1,358 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchcrawlrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchCrawlRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchCrawlRule - -## SYNOPSIS -Creates a new crawl rule. - - -## SYNTAX - -``` -New-SPEnterpriseSearchCrawlRule [-AccountName <String>] [-AccountPassword <SecureString>] - [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationType <CrawlRuleAuthenticationType>] - [-Confirm] [-ContentClass <String>] [-CrawlAsHttp <Boolean>] [-FollowComplexUrls <Boolean>] - [-IsAdvancedRegularExpression <Boolean>] -Path <String> [-PluggableSecurityTimmerId <Int32>] - [-Priority <Int32>] -SearchApplication <SearchServiceApplicationPipeBind> [-SuppressIndexing <Boolean>] - -Type <CrawlRuleType> [-WhatIf] [<CommonParameters>] -``` - - -## DESCRIPTION -The `New-SPEnterpriseSearchCrawlRule` cmdlet creates special rules for crawling items that are contained in the specified path. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchCrawlRule -SearchApplication $ssa -Path https://ExampleSharePointSite -CrawlAsHttp 1 -Type InclusionRule -``` - -This example creates an inclusion type crawl rule for the site at https://ExampleSharePointSite. -The rule specifies that the site be crawled as an HTTP site. - - -## PARAMETERS - -### -AccountName -Specifies the account to use when applying the crawl rule. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AccountPassword -Specifies the account to use when applying the crawl rule. - - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationType -Specifies one of the following authentication types to access matching URLs: - -BasicAccountRuleAccess -- Specifies the account name and password that are required for this authentication type. - -CertificateRuleAccess -- Specifies the valid client certificate name that is required for this authentication type. - -NTLMAccountRuleAccess -- Specifies the account name for integrated authentication. - -FormRuleAccess -- Specifies a valid URL for HTTP POST or HTTP GET, public and private parameters, and a list of error pages that are used by this authentication type. - -CookieRuleAccess -- Specifies private parameters and a list of error pages that are used by this authentication type. - -AnonymousAccess-- Specifies that the matching URLs have to be accessed anonymously. - - -```yaml -Type: CrawlRuleAuthenticationType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentClass -Specifies the string that is sent to the protocol handler for any content that matches the crawl rule. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlAsHttp -Specifies whether the crawler should crawl content from a hierarchical content source as HTTP content. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FollowComplexUrls -Specifies whether the index engine should crawl content with URLs that contain a question mark (?). - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsAdvancedRegularExpression -Specifies whether the rule has a full regular expression syntax. - -The default value is False. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Specifies a unique path to which a crawl rule applies. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PluggableSecurityTimmerId -{{Fill PluggableSecurityTimmerId Description}} - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -Defines where in the list of crawl rules this crawl rule should be applied. - -The priority value cannot be less than 0 or greater than or equal to the number of crawl rules for the search application. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the Search application that is associated with the crawl rule to be modified. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SuppressIndexing -Specifies whether the crawler should exclude the content of items that this rule applies to from the content index. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type of crawl rule. -A value of zero (0) includes the rule, a value of 1 excludes the rule. - - -```yaml -Type: CrawlRuleType -Parameter Sets: (All) -Aliases: t -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchFileFormat.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchFileFormat.md deleted file mode 100644 index 500f32bc8f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchFileFormat.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchfileformat -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchFileFormat -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchFileFormat - -## SYNOPSIS -Adds a new file format to the parsing system. - - -## SYNTAX - -``` -New-SPEnterpriseSearchFileFormat [-FormatId] <String> [-FormatName] <String> [-MimeType] <String> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPEnterpriseSearchFileFormat` cmdlet adds a new file format and a corresponding file name extension to the search parsing system. -This binds the file format to a filter-based format handler in the search parsing system. -Thus, the search parsing system can only parse the new file format if the user has installed a corresponding filter-based format handler, an IFilter, for the new file format. -If the installed IFilter registers more than one file name extension, the user must use the `New-SPEnterpriseSearchFileFormat` cmdlet to add a new file format to the parsing system for each of these file name extensions. -The user must also ensure that the file name extension of the new file format is a member of the file-type inclusion list. -The file-type inclusion list specifies which files that are crawled, based on their file name extensions. -The system will only consider the new file format after a restart of the content processing components. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchFileFormat -SearchApplication $ssa -FormatId foo -FormatName FooApp -MimeType "text/foo" -``` - -This example uses the `New-SPEnterpriseSearchFileFormat` cmdlet to add a new file format FooApp with the belonging file name extension foo to the parsing system in the search service application referenced by $ssa - - -## PARAMETERS - -### -FormatId -Specifies the file name extension of the format to add. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FormatName -Specifies the name of the format to add. - -Usually this is the name of the application handling the format. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MimeType -Specifies the mime type of the format to add. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application for which to add the new file format. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchFileFormat](Get-SPEnterpriseSearchFileFormat.md) - -[Set-SPEnterpriseSearchFileFormatState](Set-SPEnterpriseSearchFileFormatState.md) - -[Remove-SPEnterpriseSearchFileFormat](Remove-SPEnterpriseSearchFileFormat.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchIndexComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchIndexComponent.md deleted file mode 100644 index 51c3e87852..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchIndexComponent.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchindexcomponent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchIndexComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchIndexComponent - -## SYNOPSIS -Creates a new index component for the given topology and search service instance. - - -## SYNTAX - -``` -New-SPEnterpriseSearchIndexComponent -SearchServiceInstance <SearchServiceInstancePipeBind> - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-IndexPartition <UInt32>] [-RootDirectory <String>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new index component and adds it to an inactive search topology in a specific search service instance. -The change is effectuated when the search topology is enabled. - - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$si = Get-SPEnterpriseSearchServiceInstance -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -New-SPEnterpriseSearchIndexComponent -SearchTopology $topology -SearchServiceInstance $si -SearchApplication $ssa -IndexPartition 1 -RootDirectory E:\Index -``` - -This example adds a new Search Index Component to the inactive topology for the existing Search Service Application. The directory of the Index Component is set to E:\Index with a Partition number of 1. - - -## PARAMETERS - -### -SearchServiceInstance -Specifies the search service instance that will host the new index component. - - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology where the new index component should be added. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IndexPartition -Specifies the index partition number to assign to the new search index component. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RootDirectory -Specifies the root directory that will hold the index location for the new search index component. -This is needed if you want to isolate the index on dedicated discs in order to avoid I/O contention with other parts of the system, other system sharing the same disks, or because you do not want to risk the index filling up the OS disk (generally C: ) - -If you specify the root directory to be the root of a volume, e.g. -E:, the index will not be cleaned up if you delete the SSA. -You will then have to delete the SSA manually. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLanguageResourcePhrase.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLanguageResourcePhrase.md deleted file mode 100644 index 16aa34d863..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLanguageResourcePhrase.md +++ /dev/null @@ -1,257 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchlanguageresourcephrase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchLanguageResourcePhrase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchLanguageResourcePhrase - -## SYNOPSIS -Adds a language resource phrase to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchLanguageResourcePhrase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -Language <String> [-Mapping <String>] -Name <String> -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-SourceId <Guid>] -Type <LanguageResourceType> - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPEnterpriseSearchLanguageResourcePhrase` cmdlet adds a query keyword phrase to a shared search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $ssa -Language en-us -Type QuerySuggestionBlockList -Name secret -``` - -This example adds a new entry to the QuerySuggestionBlockList for the en-us language. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Adds the phrase for the specified source language. - -The type must be a valid name of a language; for example, en-us or ja-jp. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mapping -Allows a term or phrase to be mapped to another term or phrase. -For example, the nickname "John" could be mapped to "Jonathan". - -This parameter only applies to nicknames and substitutions. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the term to add to the list specified in the Type parameter. - -The type must be a valid name of a language resource phrase (for example, LanguageResourcePhrase1). - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding LanguageResourcePhrase is created. - -The owner must be one of the following valid levels: - -- Search Service Application -- Site Subscription -- Site Collection -- Site - - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the language resources. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SourceId -Identifies the search result source for which the LanguageResourcePhrase applies to. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type of the new phrase. - -The type must be one of the following valid types of phrases: - -- QuerySuggestionBlockList -- QuerySuggestionAlwaysSuggest -- Nickname -- QuerySuggestionSubstitution - - -```yaml -Type: LanguageResourceType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLinksDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLinksDatabase.md deleted file mode 100644 index 69c7a79dbd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLinksDatabase.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchlinksdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchLinksDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchLinksDatabase - -## SYNOPSIS -Creates a new links database for a search service application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchLinksDatabase -DatabaseName <String> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] - [-FailoverDatabaseServer <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPEnterpriseSearchLinksDatabase` cmdlet during initial configuration and farm scale out to create a new links database, which can be added to a search service application. -A links database stores query logging and analytics information. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchLinksDatabase -DatabaseName LinksDB_1 -SearchApplication $ssa -``` - -This example adds a new links database LinksDB_1 to the search service application. - - -## PARAMETERS - -### -DatabaseName -Specifies the links database to obtain. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a LinksStore object, in the form LinksStore1; or an instance of a valid LinksStore object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the links database. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password of the account to connect to the database. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the server to use for the host SQL database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the name of the account to connect to the database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the server to use for failover in the case of SQL Server mirroring. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPEnterpriseSearchLinksDatabase](Set-SPEnterpriseSearchLinksDatabase.md) - -[Get-SPEnterpriseSearchLinksDatabase](Get-SPEnterpriseSearchLinksDatabase.md) - -[Remove-SPEnterpriseSearchLinksDatabase](Remove-SPEnterpriseSearchLinksDatabase.md) - -[Repartition-SPEnterpriseSearchLinksDatabases](Repartition-SPEnterpriseSearchLinksDatabases.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataCategory.md deleted file mode 100644 index a8d8f421b1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataCategory.md +++ /dev/null @@ -1,229 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchmetadatacategory -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchMetadataCategory -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchMetadataCategory - -## SYNOPSIS -Adds a crawled property category to a search service application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchMetadataCategory [-AssignmentCollection <SPAssignmentCollection>] - [-AutoCreateNewManagedProperties <Boolean>] [-Confirm] [-DiscoverNewProperties <Boolean>] - [-MapToContents <Boolean>] -Name <String> [-PropSet <Guid>] - -SearchApplication <SearchServiceApplicationPipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates the new crawled property category. -SPEnterpriseSearchMetadataCategory represents a category in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$guid = [System.Guid]::NewGuid() -New-SPEnterpriseSearchMetadataCategory -SearchApplication $ssa -Name MyCategory -DiscoverNewProperties $true -PropSet $guid -``` - -This example adds a new metadata category named MyCategory to the default search service application. -The DiscoverNewProperties parameter is set to true. -Therefore, new crawled properties will be added to the MyCategory metadata category and the unique category identifier is set with the PropSet parameter. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AutoCreateNewManagedProperties -Specifies that when a new crawled property in this category is found, a corresponding managed property is created and mapped to this new crawled property. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: auto -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiscoverNewProperties -Specifies that if there are unknown properties in this category, these new properties are discovered during a crawl. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MapToContents -Specifies that all crawled properties of type string are mapped to corresponding managed properties of this category. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: m -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the identity of the new metadata category. - -The type must be a valid name of a metadata category, for example, MetadataCategory1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropSet -Creates a new metadata category with the specified property set. - -Note that the specified property set is the identifier of the category. -Therefore, two categories cannot share a property set. - -The type must be a valid GUID that specifies the property set, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: p -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the enterprise search metadata categories. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataCrawledProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataCrawledProperty.md deleted file mode 100644 index 208e099b47..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataCrawledProperty.md +++ /dev/null @@ -1,292 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchmetadatacrawledproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchMetadataCrawledProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchMetadataCrawledProperty - -## SYNOPSIS -Adds a crawled property. - - -## SYNTAX - -``` -New-SPEnterpriseSearchMetadataCrawledProperty [-AssignmentCollection <SPAssignmentCollection>] - -Category <CategoryPipeBind> [-Confirm] [-IsMappedToContents <Boolean>] -IsNameEnum <Boolean> -Name <String> - -PropSet <Guid> -SearchApplication <SearchServiceApplicationPipeBind> [-SiteCollection <Guid>] - [-Tenant <Guid>] -VariantType <Int32> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used when the search functionality is configured for the first time and to add new crawled properties after the first configuration. -SPEnterpriseSearchMetadataCrawledProperty represents a crawled property in the enterprise search metadata property schema. -Or, crawled properties are automatically created during regular crawls (see SPEnterpriseSearchMetadataCategory). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $ssa -Identity People -$crawlprop = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Category $cat -Limit 1 -New-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Name "MyCrawlProp" -PropSet $crawlprop.PropSet -Category $crawlprop.CategoryName -IsNameEnum $false -VariantType $crawlprop.VariantType -IsMappedToContents $false -``` - -This example maps the new crawled property MyCrawlProp to the People metadata category for the default search service application. -The mapping uses the constraints from the existing People category. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Category -Specifies to which metadata category the crawled property should be added - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a metadata category, for example, MetadataCategory1, or an instance of a valid Category object. - - -```yaml -Type: CategoryPipeBind -Parameter Sets: (All) -Aliases: c -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsMappedToContents -Specifies that the crawled property should be mapped to managed properties. -Specify true to map a crawled property to a managed property. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: im -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsNameEnum -Specifies whether the crawled property name is of type integer. -Specified by true or false. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: ie -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the identity of the new crawled property. - -The type must be a valid crawled property name, for example "urn:schemas-microsoft-com:sharepoint:portal:profile:UserName" - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropSet -Specifies the property set that belongs to an existing category. - -A valid GUID that specifies the property set, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: p -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawled property. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the crawled properties returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the crawled properties returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VariantType -Adds the crawled property as the specified variant type. -For more information about valid values for this property, see VARIANT Type Constants (https://go.microsoft.com/fwlink/p/?LinkId=143322&clcid=0x409) (https://go.microsoft.com/fwlink/p/?LinkId=143322&clcid=0x409). - -The type must be an integer that specifies the variant data type of the property set. - -> [!NOTE] -> This parameter is required although the value is not used in SharePoint Server 2013 through SharePoint Server 2019. You will see an Obsolete warning when running the cmdlet. You may ignore this message. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: vt -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataManagedProperty.md deleted file mode 100644 index 353b5f4578..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataManagedProperty.md +++ /dev/null @@ -1,491 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchmetadatamanagedproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchMetadataManagedProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchMetadataManagedProperty - -## SYNOPSIS -Adds a managed property to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchMetadataManagedProperty [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DefaultForQueryIndependentRank <UInt32>] [-Description <String>] [-EnabledForQueryIndependentRank <Boolean>] - [-EnabledForScoping <Boolean>] [-FullTextQueriable <Boolean>] [-IncludeInAlertSignature <Boolean>] - [-IncludeInMd5 <Boolean>] -Name <String> [-NameNormalized <Boolean>] [-NoWordBreaker <Boolean>] - [-Queryable <Boolean>] [-RemoveDuplicates <Boolean>] [-RespectPriority <Boolean>] [-Retrievable <Boolean>] - [-SafeForAnonymous <Boolean>] -SearchApplication <SearchServiceApplicationPipeBind> [-SiteCollection <Guid>] - [-Tenant <Guid>] -Type <Int32> [-UserFlags <Int16>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new managed property. -SPEnterpriseSearchMetadataManagedProperty represents a managed property in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchMetadataManagedProperty -Name AboutMeUpdate -SearchApplication $ssa -Type 4 -``` - -This example creates a new managed property named AboutMeUpdate in the default search service application and sets it type to DateTime. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultForQueryIndependentRank -Specifies that the managed property is mandatory when it is used in query-independent rank (relevance). - - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: def -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Adds a description to the metadata managed property. - -The type must be a valid string. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnabledForQueryIndependentRank -Specifies that the managed property is mandatory when it is used in the custom ranking model for the query-independent work of ranking. - -The type must be one of the following query-independent ranking features in the custom model XML: - -- queryIndependentFeature -- categoryFeature -- languageFeature - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: qir -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnabledForScoping -Specifies that the managed property can be used in a scope definition. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: e -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FullTextQueriable -Specifies that the managed property can be used in enterprise search SQL queries. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: f -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeInAlertSignature -Specifies whether this managed property should be included in the alert signature. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: ia -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeInMd5 -Specifies that the managed property is included in the hash used by the crawler to determine whether a document has changed. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: im5 -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new managed property. - -The type must be a valid name of a managed property, for example, ManagedProperty1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NameNormalized -Specifies if the values of the managed property should be normalized, that is, enable to return results independent of letter casing and diacritics used in the query. -If value is set to true, the values are normalized. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: nn -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoWordBreaker -Specifies that the values for this managed property are processed by a word breaker. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: nw -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Queryable -Specifies whether this managed property is queryable or not. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: q -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveDuplicates -Specifies that duplicate values for the managed property are removed. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: rd -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RespectPriority -Specifies that when a mapped crawled property contains multiple values and RespectPriority is set to true, only the first mapped crawled property is copied. -Otherwise, all mapped crawled properties that have a value are copied. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: rp -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Retrievable -Specifies whether this managed property is retrievable or not. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: r -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SafeForAnonymous -Specifies whether it is acceptable to display the contents of the property in search results for anonymous searches. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: sfa -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the managed property collection. - -The type must be a valid search application name (for example, SearchApp1), or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the managed properties returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the managed properties returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the data type of the new managed property. - -The type must be one of the following data types: - -1 = Text - -2 = Integer - -3 = Decimal - -4 = DateTime - -5 = YesNo - -6 = Binary - -7 = Double - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: t -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserFlags -Reserved for future use. - - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataMapping.md deleted file mode 100644 index c9824e729d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchMetadataMapping.md +++ /dev/null @@ -1,210 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchmetadatamapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchMetadataMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchMetadataMapping - -## SYNOPSIS -Adds a managed property mapping. - - -## SYNTAX - -``` -New-SPEnterpriseSearchMetadataMapping -CrawledProperty <CrawledPropertyPipeBind> - -ManagedProperty <ManagedPropertyPipeBind> -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SiteCollection <Guid>] [-Tenant <Guid>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet maps a crawled property to a managed property. -SPEnterpriseSearchMetadataMapping represents a snapshot of a mapping between a managed property and one or more crawled properties in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $ssa -Identity UserName -$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $ssa -Identity People -$cp = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Category $cat -Limit 1 -$ncp = New-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Name "MyCrawlProp" -PropSet $cp.PropSet -Category $cp.CategoryName -IsNameEnum $false -VariantType $cp.VariantType -IsMappedToContents $true -New-SPEnterpriseSearchMetadataMapping -SearchApplication $ssa -ManagedProperty $mp -CrawledProperty $ncp -``` - -This example maps the created crawled property MyCrawlProp to the managed property UserName for the default search service application. - ->![NOTE] ->The VarientType parameter is marked as obsolete but is still required when executing the `New-SPEnterpriseSearchMetadataCrawledProperty` cmdlet. - - -## PARAMETERS - -### -CrawledProperty -Specifies the crawled property to map. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid URL in the form https://server_name, or an instance of a valid CrawledProperty object. - -```yaml -Type: CrawledPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -Specifies the managed property to which the crawled property should be mapped. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a managed property, for example, ManagedProperty1, or an instance of a valid ManagedProperty object. - -```yaml -Type: ManagedPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the metadata mapping. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the metadata mapping returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the metadata mapping returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryAuthority.md deleted file mode 100644 index f1965d5760..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryAuthority.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchqueryauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchQueryAuthority -schema: 2.0.0 ---- - -# New-SPEnterpriseSearchQueryAuthority - -## SYNOPSIS -Adds an authoritative page to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchQueryAuthority [-Url] <String> -Level <Single> -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPEnterpriseSearchQueryAuthority` cmdlet adds an authoritative page to adjust query rank. -SPEnterpriseSearchQueryAuthority represents authoritative sites that rank higher in relevance than demoted sites, which are de-emphasized in relevance. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchQueryAuthority -SearchApplication $ssa -Url https://contoso.com -Level 1.5 -``` - -This example designates the URL https://contoso.com as an authoritative page with a relative importance of 1.5. - - -## PARAMETERS - -### -Url -Specifies the query authority page to create. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Level -Specifies the level of the new authoritative page. -Authoritative pagesare expert pages that link to the most relevant information. -A search service application can have multiple authoritative pages. -The Level property is used to specify the relative relevance adjustment of the authoritative pages. -This parameter may receive a floating point value of 0.0 - 2.0, where 0.0 has the most positive impact on relevance. - -```yaml -Type: Single -Parameter Sets: (All) -Aliases: l -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding Query Authority is created. The owner must be one of the following valid levels:- Search Service Application- Site Subscription - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the authority page collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryDemoted.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryDemoted.md deleted file mode 100644 index 373d2275a6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryDemoted.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchquerydemoted -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchQueryDemoted -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchQueryDemoted - -## SYNOPSIS -Adds a demoted site rule to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchQueryDemoted [-Url] <String> -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPEnterpriseSearchQueryDemoted` cmdlet adjusts query rank by adding a demoted site rule to the shared search application. -Query demoted sites are de-emphasized in relevance. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchQueryDemoted -Url https://examplesite -SearchApplication $ssa -``` - -This example adds a demoted site rule for the URL https://examplesite.com to a search service application. - - -## PARAMETERS - -### -Url -Specifies the identity of the new demoted site rule. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding Demoted object is created. The owner must be one of the following valid levels:- Search Service Application- Site Subscription - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the demoted site rule collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryKeyword.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryKeyword.md deleted file mode 100644 index 2d9141a517..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryKeyword.md +++ /dev/null @@ -1,254 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchquerykeyword -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchQueryKeyword -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchQueryKeyword - -## SYNOPSIS -Adds a keyword term to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchQueryKeyword [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Contact <String>] [-Definition <String>] [-EndDate <DateTime>] [-ReviewDate <DateTime>] - -Site <SPSitePipeBind> [-StartDate <DateTime>] -Term <String> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPEnterpriseSearchQueryKeyword` cmdlet changes query results by creating a new keyword. -A query keyword is a query component of a query topology. -SPEnterpriseSearchQueryKeyword represents relevance setting through keywords. - -You can use this cmdlet for keywords in site collections that are in SharePoint Server. -You cannot use this cmdlet after a site collection is upgraded to SharePoint Server because keywords and Best Bets are automatically migrated to query rules. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPEnterpriseSearchQueryKeyword -Term Tangible -Site https://myserver/sites/team -``` - -This example creates a new query keyword for the site https://myserver/sites/team with the term Tangible. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Contact -Specifies the user name associated with the new keyword. - -The type must be a valid user name; for example, KeywordUser1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: c -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Definition -Specifies the definition of the new keyword term. - -The type must be a valid string; for example, a keyword term definition. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -Specifies the expiration date of the keyword term. -The default value is MaxDate. - -The type must be a valid DateTime type, in the form 2010,12,05. - - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: e -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReviewDate -Specifies the review date of the keyword term. -The default value is MaxDate. - -The type must be a valid date, in the form 2010,12,05. - - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: r -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Associates the new keyword term to the specified results URL. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -Specifies the activation date for the keyword term. -The default value is the current date. - -The type must be a valid date, in the form 2010,12,05. - - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: s -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Term -Specifies the keyword term to create. - -The type must be a valid string that contains a keyword term (for example, KeywordTerm1). - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryProcessingComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryProcessingComponent.md deleted file mode 100644 index 172ebf6198..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryProcessingComponent.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchqueryprocessingcomponent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchQueryProcessingComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchQueryProcessingComponent - -## SYNOPSIS -Creates a new query processing component for the given topology and search service instance. - - -## SYNTAX - -``` -New-SPEnterpriseSearchQueryProcessingComponent -SearchServiceInstance <SearchServiceInstancePipeBind> - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new query processing component and adds it to an inactive search topology in a specific search service instance. -The change is effectuated when the search topology is enabled. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$si = Get-SPEnterpriseSearchServiceInstance -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $topology -SearchServiceInstance $si -SearchApplication $ssa -``` -This example adds a new Search Query Processing Component to the inactive topology for the existing Search Service Application. - -## PARAMETERS - -### -SearchServiceInstance -Specifies the search service instance that will host the new query processing component. - - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology where the new query processing component should be added. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryScope.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryScope.md deleted file mode 100644 index 8c27cc6144..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryScope.md +++ /dev/null @@ -1,272 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchqueryscope -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchQueryScope -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchQueryScope - -## SYNOPSIS -Adds a query results scope to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchQueryScope [-AlternateResultsPage <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-CompilationType <Int32>] [-Confirm] -Description <String> - -DisplayInAdminUI <Boolean> [-ExtendedSearchFilter <String>] -Name <String> [-OwningSiteUrl <Uri>] - -SearchApplication <SearchServiceApplicationPipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -After you upgrade a Search service application to SharePoint Server, you can view shared scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for shared scopes after upgrade. -However, you can convert shared scopes to result sources, which serve a similar purpose. -Similarly, after you upgrade a SharePoint Server site collection to SharePoint Server mode, you can view local scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for local scopes after you upgrade a site collection. -However, you can convert local scopes to result sources, which serve a similar purpose. - -Use the `New-SPEnterpriseSearchQueryScope` cmdlet to create a new shared scope. -SPEnterpriseSearchQueryScope represents a query results scope used by all shared search applications on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchQueryScope -Name MustCrawl -Description "Sites we must crawl" -DisplayInAdminUI $true -SearchApplication $ssa -``` - -This example adds a scope named MustCrawl that will be displayed in the administration UI to the search service application named MySSA. - - -## PARAMETERS - -### -AlternateResultsPage -Specifies the location to display results for the new query scope. - -The type must be a valid URL, in the form https://server_name. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: a -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompilationType -Specifies the compilation type of the new scope. -The value 0 specifies the conditionally compiled scope type and the value 1 specifies the always compiled scope type. - -The type must be either of the following: 0 or 1. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: type -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Adds a description of the new query scope. - -The type must be a valid string; for example, a description of a query scope. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayInAdminUI -Specifies that the new scope is displayed in the administration application user interface (UI). -The default setting is to hide the new scope in the administration application UI. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: disp -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtendedSearchFilter -{{Fill ExtendedSearchFilter Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: f -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the identity of the scope to create. - -The type must be a valid name of a scope (for example, Scope1). - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OwningSiteUrl -Specifies the SharePoint site that is associated with the new scope. - -The type must be a valid SharePoint site URL, in the form https://server_name. - - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryScopeRule.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryScopeRule.md deleted file mode 100644 index 54837c3159..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchQueryScopeRule.md +++ /dev/null @@ -1,279 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchqueryscoperule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchQueryScopeRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchQueryScopeRule - -## SYNOPSIS -Adds a shared scope rule to a query scope. - - -## SYNTAX - -``` -New-SPEnterpriseSearchQueryScopeRule -RuleType <String> -Scope <ScopePipeBind> -Url <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-FilterBehavior <String>] - [-ManagedProperty <ManagedPropertyPipeBind>] [-MatchingString <String>] [-PropertyValue <String>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-UrlScopeRuleType <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -After you upgrade a Search service application to SharePoint Server, you can view shared scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for shared scopes after upgrade. -However, you can convert shared scopes to result sources, which serve a similar purpose. -Similarly, after you upgrade a SharePoint Server site collection to SharePoint Server mode, you can view local scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for local scopes after you upgrade a site collection. -However, you can convert local scopes to result sources, which serve a similar purpose. - -The `New-SPEnterpriseSearchQueryScopeRule` cmdlet creates a new shared scope rule. -SPEnterpriseSearchQueryScopeRule represents a query results scope rule that can be applied to a scope. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -C:\PS>$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa -New-SPEnterpriseSearchQueryScopeRule -Scope $scope -RuleType AllContent -Url https://criticalSite -``` - -This example creates a new scope rule of type AllContent for the URL https://criticalSite. - - -## PARAMETERS - -### -RuleType -Specifies the type of scope rule to create. - -The type must be one of the following values: AllContent, Url, or PropertyQuery. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: type -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Applies the query scope rule to the specified scope. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope (for example, Scope1); or an instance of a valid Scope object. - -```yaml -Type: ScopePipeBind -Parameter Sets: (All) -Aliases: s -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -Specifies the results URL that is associated with the query scope rule. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterBehavior -Specifies the type of scope rule to create for the query scope. -The default value is Include. - -The type must be one of the following values: Exclude, Include, or Require. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: f -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -Specifies the managed property to use for the PropertyQuery scope rule. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a managed property (for example, ManagedProperty1); or an instance of a valid ManagedProperty object. - -```yaml -Type: ManagedPropertyPipeBind -Parameter Sets: (All) -Aliases: mname -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MatchingString -Specifies the string to use when matching the URL rule type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: text -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertyValue -Specifies the property value to use when matching the PropertyQuery rule type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: value -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope rule collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UrlScopeRuleType -Specifies the value to use when matching the URL rule type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: ut -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchRankingModel.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchRankingModel.md deleted file mode 100644 index b2337f58e0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchRankingModel.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchrankingmodel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchRankingModel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchRankingModel - -## SYNOPSIS -Adds a ranking model to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchRankingModel -Owner <SearchObjectOwner> -RankingModelXML <String> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet adds a new ranking model to the assignment collection. -The name, description and identifier (ID) for the new ranking model are contained in the .xml file specified in RankingModelXML. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$owner = Get-SPEnterpriseSearchOwner -Level SPWeb -SPWeb https://sharepoint/team -[String]$rankmodel = Get-Content .\rankModel.xml -New-SPEnterpriseSearchRankingModel -SearchApplication $ssa -Owner $owner -RankingModelXML $rankmodel -``` - -This example creates a ranking model for the site https://sharepoint/team for the search service application Search Service Application from the file rankModel.xml which is stored in the current directory. - - -## PARAMETERS - -### -Owner -Specifies the scope where the ranking model is available. -The available scopes are: SSA, Tenant, Site Collection or Site. -A ranking model can be available in multiple scopes. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RankingModelXML -Specifies the name of the XML representation of the new ranking model. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the ranking model. - -The type must be a valid GUID in the 9bf36458-fc99-4f7b-b060-867e5a63adce, a valid search application name (for example, SearchApp1), or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchResultItemType.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchResultItemType.md deleted file mode 100644 index 51486a6fef..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchResultItemType.md +++ /dev/null @@ -1,399 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchresultitemtype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchResultItemType -schema: 2.0.0 ---- - -# New-SPEnterpriseSearchResultItemType - -## SYNOPSIS -Creates a new result item type. - - -## SYNTAX - -### New -``` -New-SPEnterpriseSearchResultItemType [-Name] <String> [-Rules] <PropertyRuleCollection> - [[-RulePriority] <Int32>] [[-DisplayProperties] <String>] [[-SourceID] <Guid>] [-DisplayTemplateUrl] <String> - -Owner <SearchObjectOwner> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-OptimizeForFrequentUse <Boolean>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [-SearchApplicationProxy <SearchServiceApplicationProxyPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -### Copy -``` -New-SPEnterpriseSearchResultItemType [[-Name] <String>] [[-Rules] <PropertyRuleCollection>] - [[-RulePriority] <Int32>] [[-DisplayProperties] <String>] [[-SourceID] <Guid>] - [[-DisplayTemplateUrl] <String>] -ExistingResultItemType <ResultItemTypePipeBind> - -ExistingResultItemTypeOwner <SearchObjectOwner> -Owner <SearchObjectOwner> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-OptimizeForFrequentUse <Boolean>] - [-SearchApplication <SearchServiceApplicationPipeBind>] - [-SearchApplicationProxy <SearchServiceApplicationProxyPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPEnterpriseSearchResultItemType` cmdlet to create a new result item type. - -Result item types enable you to change the look of search results based on the type of result. -You start by defining a collection of rules, which will be evaluated against the properties of results. -Then you define the display template to use for rendering that type of result. -Once you have created the result item type, results matching the rules of the result item type will render using the specified display template. - -Example use cases: - -- Change the look of results for a particular file name extension, for example Word documents. -- Change the look of a particular content type in search results. -- Change the look of results from a particular author. -- Add a result action to results from a particular result source as part of a custom search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$rule = Get-SPEnterpriseSearchPropertyRule -PropertyName "ContentTypeId" -Operator "StartsWith" -$rule.AddValue('0x010063C2F478ACC511DFB869B5BFDFD720851252') -$ruleCollection = Get-SPEnterpriseSearchPropertyRuleCollection -$ruleCollection.Add($rule) -$displayProperties = "WorkId,Rank,Title,Size,Path,Description,SiteName,HitHighlightedSummary,HitHighlightedProperties,ViewsLifeTime" -$displaytemplateUrl = "~sitecollection/_catalogs/masterpage/Display Templates/Search/Item_MyCustomDisplayTemplate.js" -$web = Get-SPWeb https://webUrl -$tenantOwner = Get-SPEnterpriseSearchOwner -Level SPSite -SPWeb $web -$proxy = Get-SPEnterpriseSearchServiceApplicationProxy -New-SPEnterpriseSearchResultItemType -SearchApplicationProxy $proxy ` ->> -Name "CustomResultType" ` ->> -Rules $ruleCollection ` ->> -RulePriority 1 ` ->> -DisplayProperties $displayProperties ` ->> -DisplayTemplateUrl $displaytemplateUrl ` ->> -Owner $tenantOwner -``` - -This example first defines the rule to apply to the search results in order to target results with a specific property and adds the rule to the rule collection. - -Thereafter the example defines the properties of the result that shall be displayed and the URL to the display template governing the appearance of the rendered results. - -Finally, the example defines the rule item type by its name, the rule collection, the display properties, the display template and the tenant owner. - -## PARAMETERS - -### -Name -Specifies the name of the result item type. - -```yaml -Type: String -Parameter Sets: New -Aliases: n -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: Copy -Aliases: n -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Rules -Specifies the collection of rules to evaluate the result properties against. - -```yaml -Type: PropertyRuleCollection -Parameter Sets: New -Aliases: rule -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: PropertyRuleCollection -Parameter Sets: Copy -Aliases: rule -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RulePriority -Specifies which priority the collection of rules has compared to other rules. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: priority -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayProperties -Specifies which result properties to display. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: dp -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceID -Identifies the search result source that the result item type applies to. -Leave this parameter blank to apply to all result sources. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: sid -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayTemplateUrl -Specifies the URL of the display template that shall be used for rendering the results. -Specify an absolute URL. - -```yaml -Type: String -Parameter Sets: New -Aliases: url -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 7 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: Copy -Aliases: url -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 7 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExistingResultItemType -Specifies an existing result item type to which new rules or displayed properties can be added. - -```yaml -Type: ResultItemTypePipeBind -Parameter Sets: Copy -Aliases: copy -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExistingResultItemTypeOwner -Specifies the search object owner that defines the scope at which an existing result item type was created. - -```yaml -Type: SearchObjectOwner -Parameter Sets: Copy -Aliases: eo -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the result item type is created. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OptimizeForFrequentUse -Enable this flag if you always want the properties of this result item type to be requested, regardless of whether the result type is triggered. -This will improve performance as long as it is only enabled on the most frequently used result item types. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: opt -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the result item type. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplicationProxy -Specifies the proxy of the search application that contains the result item type. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application proxy name (for example, SearchAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPEnterpriseSearchResultItemType](Set-SPEnterpriseSearchResultItemType.md) - -[Get-SPEnterpriseSearchResultItemType](Get-SPEnterpriseSearchResultItemType.md) - -[Remove-SPEnterpriseSearchResultItemType](Remove-SPEnterpriseSearchResultItemType.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) - -[Get-SPEnterpriseSearchPropertyRule](Get-SPEnterpriseSearchPropertyRule.md) - -[Get-SPEnterpriseSearchPropertyRuleCollection](Get-SPEnterpriseSearchPropertyRuleCollection.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchResultSource.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchResultSource.md deleted file mode 100644 index bcd5d6593a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchResultSource.md +++ /dev/null @@ -1,404 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchresultsource -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchResultSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchResultSource - -## SYNOPSIS -Creates a new result source. - - -## SYNTAX - -``` -New-SPEnterpriseSearchResultSource [-AssignmentCollection <SPAssignmentCollection>] - [-AuthenticationType <FederationAuthType>] [-AutoDiscover <Boolean>] [-Confirm] [-Description <String>] - [-MakeDefault <Boolean>] -Name <String> -Owner <SearchObjectOwner> [-Password <String>] -ProviderId <Guid> - [-QueryTemplate <String>] [-RemoteUrl <String>] -SearchApplication <SearchServiceApplicationPipeBind> - [-SsoId <String>] [-UserName <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a result source. -Use result sources to scope search results and federate queries to external sources, such as internet search engines. -After defining a result source, configure search web parts and query rule actions to use it. -Result Sources replace Search Scopes, which are now deprecated. -This cmdlet supports the same create operations as are supported through the "Manage Result Sources" page in Central Administration, except the operations "Form Authentication" and "Cookie Authentication". -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$owner = Get-SPEnterpriseSearchOwner -Level SSA -New-SPEnterpriseSearchResultSource -SearchApplication $ssa -Owner $owner -ProviderId fa947043-6046-4f97-9714-40d4c113963d -Name "Custom SharePoint Result Source" -``` - -This example creates a new search service application level result source, named "Custom SharePoint Result Source". - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationType -Specifies the authentication type of the new result source. - -A specific set of authentication types are supported for each search provider type and, if parameter is not specified, the authentication type will default based on search provider type. - -This cmdlet supports the following set of authentication mechanisms and corresponding types: Default SharePoint Authentication (FederationAuthType.LocalNTAuth), Basic Authentication (FederationAuthType.SingleAccountBasicAuth - specify UserName and Password), Default Remote SharePoint Authentication (FederationAuthType.PerUserBasicAuth), Single Sign On (FederationAuthType.SSO - requires SsoId to be specified), Anonymous (FederationAuthType.Anonymous), Digest Authentication (FederationAuthType.SingleAccountDigest - specify UserName and Password), NTLM Application Pool Identity (FederationAuthType.ApplicationPoolIdentity), NTLM User Name and Password (FederationAuthType.SingleAccountNTLM - specify UserName and Password). - -When using a Local SharePoint Search/Local SharePoint People Search provider, then FederationAuthType.LocalNTAuth (default) and FederationAuthType.SingleAccountBasicAuth are supported. - -When using a Remote SharePoint Search/Remote SharePoint People Search provider, then FederationAuthType.PerUserBasicAuth (default) and FederationAuthType.SSO are supported. - -When using OpenSearch 1.0/1.1 search provider, then the following authentication types are supported: FederationAuthType.Anonymous (default), FederationAuthType.SingleAccountBasicAuth, FederationAuthType.SingleAccountDigest, FederationAuthType.SingleAccountNTLM, and FederationAuthType.ApplicationPoolIdentity. - -All authentication types are listed in the enum FederationAuthType. - - -```yaml -Type: FederationAuthType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoDiscover -Specifies whether to use automatic discovery of the Exchange server endpoint for the new result source. - -Setting value to true ($true) states that automatic discovery should be used. -If not specified or set to false ($false), automatic discovery will not be used. - -Only applicable when using an Exchange search provider. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the new result source. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MakeDefault -Specifies whether the new result source should be set as default or not, for the scope specified by the Owner parameter. - -Setting value to true ($true) states that the result source should be set as default. -If not specified or set to false, the new result source will not be set as default. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new result source. - -Names must be unique at each administrative level. - -For example, two result sources in a site cannot share a name, but one in a site and one provided by the site collection can. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding result source is created. - - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -Specifies the password of the user credentials to use to connect to the new result source. - -Used when authentication type (AuthenticationType) is set to a type that consumes user credentials (FederationAuthType.SingleAccountBasicAuth, FederationAuthType.SingleAccountDigest or FederationAuthType.SingleAccountNTLM). - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProviderId -Specifies the search provider to be used by the new result source. - -Is specified as a Guid or GUID string, which must be one of the following: FA947043-6046-4F97-9714-40D4C113963D (Local SharePoint Search), E4BCC058-F133-4425-8FFC-1D70596FFD33 (Local SharePoint People Search), 1E0C8601-2E5D-4CCB-9561-53743B5DBDE7 (Remote SharePoint Search), E377CAAA-FCAF-4a1b-B7A1-E69A506A07AA (Remote SharePoint People Search), 3A17E140-1574-4093-BAD6-E19CDF1C0122 (Exchange Search), 3A17E140-1574-4093-BAD6-E19CDF1C0121 (OpenSearch 1.0/1.1). - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueryTemplate -Specifies the query transformation template of the new result source. - -Incoming queries are changed according to the template, to use this new query text instead. -Include the incoming query in the new text by using the query variable "{searchTerms}". -Use this to scope results. - -For example, to only return OneNote items, set the new text to "{searchTerms} fileextension=one". -Then, an incoming query "sharepoint" becomes "sharepoint fileextension=one". -Default value is {searchTerms}. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteUrl -Specifies the connection URL template of the new result source. - -Must be set when using a search provider that consumes it: Remote SharePoint Search, Remote SharePoint People Search, OpenSearch 1.0/1.1 and Exchange (if AutoDiscover is not turned on). - -When using other search providers the parameter is ignored. - -For Remote SharePoint Search/Remote SharePoint People Search, specify the address of the root site collection of the remote SharePoint farm. - -For OpenSearch 1.0/1.1, specify the URL of the OpenSearch source. - -Include the query in the URL by using the query variable "{searchTerms}", which will be automatically replaced with the query. -For Exchange, specify the Exchange EWS URL from which to retrieve results. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SsoId -Specifies the reverse proxy certificate Secure Store Id to use to connect to the new result source. - -Must be specified if authentication type (AuthenticationType) is set to FederationAuthType.SSO (Single Sign On). - -If you are connecting to your intranet through a reverse proxy, enter the SSO Id of the Single Sign On entry which stores the certificate used to authenticate against the reverse proxy. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserName -Specifies the user name of the user credentials to use to connect to the new result source. - -Used when authentication type (AuthenticationType) is set to a type that consumes user credentials (FederationAuthType.SingleAccountBasicAuth, FederationAuthType.SingleAccountDigest or FederationAuthType.SingleAccountNTLM). - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchResultSource](Get-SPEnterpriseSearchResultSource.md) - -[Set-SPEnterpriseSearchResultSource](Set-SPEnterpriseSearchResultSource.md) - -[Remove-SPEnterpriseSearchResultSource](Remove-SPEnterpriseSearchResultSource.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchSecurityTrimmer.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchSecurityTrimmer.md deleted file mode 100644 index 5388b54810..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchSecurityTrimmer.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchsecuritytrimmer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchSecurityTrimmer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchSecurityTrimmer - -## SYNOPSIS -Adds a custom security trimmer to a shared search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchSecurityTrimmer [-Id] <Int32> [-RulePath <String>] - -SearchApplication <SearchServiceApplicationPipeBind> -TypeName <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Properties <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new object to configure the security trimmer. -SPEnterpriseSearchSecurityTrimmer represents a security trimmer that performs customized security trimming of search results at query time, when the results are returned to the user. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchSecurityTrimmer -SearchApplication $ssa -TypeName "SearchCustomSecurityTrimmer.CustomSecurityTrimmerPost, SearchCustomSecurityTrimmer, Version=1.0.0.0, Culture=neutral, PublicKeyToken=48e046c834625a88, processorArchitecture=MSIL" -Id 1 -``` - -This example adds a new custom security trimmer for trimming the returned result set. This new security trimmer is added to the search application by using the id 1. The strong named assembly contains the class CustomSecurityTrimmerPost, which implements the ISecurityTrimmerPost interface. - - -## PARAMETERS - -### -Id -Specifies the identity of the security trimmer to use for the specified search application. - -If this parameter specifies an existing custom security trimmer, the trimmer will be removed and replaced with the custom trimmer. - -Remove the existing trimmer before you add a new one. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RulePath -Specifies the content path where the security trimmer will be applied. - -The string must be a valid URI in the form file:\\\\server_name\content, and it must correspond to an existing crawl rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Adds the security trimmer to the specified search application. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -TypeName -Specifies the strong named assembly name of a security trimmer type. -The strong name must refer to a type whose assembly is deployed to the global assembly cache on a query server and that type must implement the ISecurityTrimmerPre, ISecurityTrimmerPost or ISecurityTrimmer2 interface. -Security trimming can be done in two places: before query execution (ISecurityTrimmerPre) or after the results set has returned (ISecurityTrimmerPost or ISecurityTrimmer2). -For how to reference a strong name assembly, see https://msdn.microsoft.com/en-us/library/s1sx4kfb.aspx (https://msdn.microsoft.com/en-us/library/s1sx4kfb.aspx) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Properties -Specifies the name-value pairs that specify the configuration properties. - -The type must be in the following name/value pair format: Name1~Value1~Name2~Value2~ - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index fb4be69f20..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,294 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Adds a search service application to a farm. - - -## SYNTAX - -``` -New-SPEnterpriseSearchServiceApplication [[-Name] <String>] - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] - [-DatabaseUsername <String>] [-Partitioned] [-WhatIf] - [-AdminApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-CloudIndex <Boolean>] - [-FailoverDatabaseServer <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used when the search functionality is first configured or when a new shared search application is added to a farm. -SPEnterpriseSearchServiceApplication represents a self-contained aggregation of indexed content and properties available for search and provides an anchor class for setting global search properties. -A farm can include multiple search service applications. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$appPool = New-SPServiceApplicationPool -Name 'SharePoint Web Services Default' -Account 'CONTOSO\ServiceApps' -New-SPEnterpriseSearchServiceApplication -Name "Search Service Application" -ApplicationPool $appPool -``` - -This example creates a new search service application named NewSSA in a new application pool. - -A search service application that is created in this manner will have active search topology, but no search components. - - -## PARAMETERS - -### -Name -Specifies the names of the new search application. - -The type must be a valid name of a search application, for example, SearchApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the IIS application pool to use for the new search application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL of a search application, in the form https://server_name; or an instance of a valid SPIisWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database to create for the new search application. - -The type must be a valid name of a SQL Server database, for example, SearchAppDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user ID that is used for accessing the search application database on SQL Server. - -The type must be a valid password. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid SQL Server host name, for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user ID to use for accessing the search application SQL Server database. - -The type must be a valid user name, for example, SearchUserName1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Partitioned -Specifies that the search service application uses web-hosted mode. -Web-hosted mode segregates results for a given hosted subscription. - -This property has no effect on SharePoint Server 2019. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminApplicationPool -Specifies the application pool to be used with the SearchAdminWebServiceApplication that is associated with SearchServiceApplication. If not specified, ApplicationPool will be used. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CloudIndex -When CloudIndex is true, this becomes a cloud Search service application that crawls on premises content in a cloud hybrid search solution. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the SQL server that hosts the mirror instances of search databases. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchServiceApplicationProxy.md deleted file mode 100644 index e9ab9f25bb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchServiceApplicationProxy.md +++ /dev/null @@ -1,215 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchServiceApplicationProxy - -## SYNOPSIS -Adds a new search application proxy to a farm. - - -## SYNTAX - -### SSA -``` -New-SPEnterpriseSearchServiceApplicationProxy [[-Name] <String>] - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-MergeWithDefaultPartition] [-Partitioned] [-WhatIf] [<CommonParameters>] -``` - -### Uri -``` -New-SPEnterpriseSearchServiceApplicationProxy [[-Name] <String>] -Uri <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-MergeWithDefaultPartition] [-Partitioned] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -This cmdlet creates a proxy for a search service application. -The search service application proxy can be used by a web application or another service consumer to use the functionality that is provided by the search application. - -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://msdn.microsoft.com/en-us/library/dd878348(VS.85).aspx). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchServiceApplicationProxy -Name 'Search Service Application Proxy' -SearchApplication $ssa -``` - -This example adds a search service application proxy to a search service application. - - -## PARAMETERS - -### -Name -Specifies the display name of the search application proxy to create. - -The type must be a valid string, for example, SearchAppProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the URI to the search application to use for search. - -The type must be a valid URI, in the form file:\\\\server_name\searchapp. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: SSA -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Uri -Specifies the URI to the search application to use for search. - -The type must be a valid URI, in the form file:\\\\server_name\searchapp. - -```yaml -Type: String -Parameter Sets: Uri -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MergeWithDefaultPartition -Merges the index partition for the proxy with the default index partition collection for the search service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Partitioned -Specifies that the search service application must use web-hosted mode. -web-hosted mode segregates results for a given hosted subscription. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchSiteHitRule.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchSiteHitRule.md deleted file mode 100644 index 93fef491fb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchSiteHitRule.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchsitehitrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchSiteHitRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchSiteHitRule - -## SYNOPSIS -Adds a new site hit rule for a search application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchSiteHitRule -Behavior <String> -HitRate <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SearchService <SearchServicePipeBind>] [-WhatIf] - -Name <String> [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPEnterpriseSearchSiteHitRule` cmdlet sets the maximum limits for crawling a site. -The new site hit rule is used by all search service applications on the current farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------EXAMPLE------------------ -``` -New-SPEnterpriseSearchSiteHitRule -Name myHost -Behavior 0 -HitRate 40 -``` - -This example creates a new site hit rule on the myHost host that limits to 40 the number of simultaneous requests. - - -## PARAMETERS - -### -Name -The name of the host to which the site hit rule should be applied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Behavior -Defines a rule to be followed when the farm's search service crawls the given site. - -If a value of zero is specified, the hit rate is the maximum number of simultaneous requests. If a value of 1 is specified, then hit rate is the number of seconds to delay between requests to the server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HitRate -Value to use for maximum requests or seconds of delay, according to behavior. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchService -Specifies the search service in the farm that hosts the crawl. - -The type must be an instance of a valid SearchService object; otherwise, the local service on the server that hosts the Windows PowerShell cmdlet will be used. - -```yaml -Type: SearchServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchTopology.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchTopology.md deleted file mode 100644 index ae7c14a466..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchTopology.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spenterprisesearchtopology -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPEnterpriseSearchTopology -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPEnterpriseSearchTopology - -## SYNOPSIS -Creates a new search topology in the given search service application. - - -## SYNTAX - -``` -New-SPEnterpriseSearchTopology -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Clone] [-Confirm] - [-SearchTopology <SearchTopologyPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new, inactive search topology in the given search service application. -If the Clone switch is used, a cloned topology is created. -Otherwise, an empty topology is created. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -New-SPEnterpriseSearchTopology -SearchApplication $ssa -``` - -This example creates a new, empty search topology in the search service application referenced by $ssa. - - -### ------------------EXAMPLE 2------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone -SearchTopology $topology -``` - -This example creates a new search topology in the search service application referenced by $ssa by cloning the existing topology referenced by $topology. - - -## PARAMETERS - -### -SearchApplication -Specifies the search application to which the search topology will belong. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Clone -Specifies that the new search topology is to be created by cloning an existing search topology. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Specifies that the new search topology is to be created by cloning an existing search topology. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the existing search topology of which the new topology will be a clone. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchTopology](Get-SPEnterpriseSearchTopology.md) - -[Set-SPEnterpriseSearchTopology](Set-SPEnterpriseSearchTopology.md) - -[Remove-SPEnterpriseSearchTopology](Remove-SPEnterpriseSearchTopology.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelBIServer.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelBIServer.md deleted file mode 100644 index a60013473c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelBIServer.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spexcelbiserver -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: New-SPExcelBIServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPExcelBIServer - -## SYNOPSIS - - -Configures -Analysis Services servers to work with Excel Services. - - - -## SYNTAX - -``` -New-SPExcelBIServer [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> -ServerId <String> [-WhatIf] [<CommonParameters>] -``` - - -## DESCRIPTION -Use the New-SPExcelBIServer cmldet to configure Analysis Services servers to work with Excel Services. - - - - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPExcelBIServer -ExcelServiceApplication "MyExcel" -ServerID "MSS01" -``` - -This example configures the analysis server to work the Excel Service application named MyExcel and ServerID of MSS01. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE:** When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the Analysis server - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ServerId - -The name of the Analysis Services server - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Excel.Server.Cmdlet.SPExcelServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelBlockedFileType.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelBlockedFileType.md deleted file mode 100644 index d836df5048..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelBlockedFileType.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spexcelblockedfiletype -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: New-SPExcelBlockedFileType -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPExcelBlockedFileType - -## SYNOPSIS -Adds a file type to the list of file types that Excel Services Application prevents from loading. - - -## SYNTAX - -``` -New-SPExcelBlockedFileType -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> -FileType <FileType> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPExcelBlockedFileType` cmdlet adds an entry to the list of file types that Excel Services Application prevents from loading. -Excel Services Application does not load any files that correspond to a file type that is on this list. -The specified file type is prevented from loading by all instances of Excel Services Application for the specified Excel Services Application Web service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$sa = Get-SPExcelServiceApplication -New-SPExcelBlockedFileType -FileType XLSM -ExcelServiceApplication $sa -``` - -This example adds an entry for XLSM to the list of file types that Excel Services Application currently prevents from loading. - - -## PARAMETERS - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPBlockedExcelFileType list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -FileType -Specifies the file types that are blocked from loading. - -The type must be one of the following file extensions: XLSX, XLSB, or XLSM. - -```yaml -Type: FileType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelDataConnectionLibrary.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelDataConnectionLibrary.md deleted file mode 100644 index de34ee72d5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelDataConnectionLibrary.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spexceldataconnectionlibrary -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: New-SPExcelDataConnectionLibrary -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPExcelDataConnectionLibrary - -## SYNOPSIS -Adds a new data connection library to Excel Services Application. - - -## SYNTAX - -``` -New-SPExcelDataConnectionLibrary -Address <String> -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPExcelDataConnectionLibrary` cmdlet adds a data connection library to the list of trusted data connection libraries for an Excel Services Application Web service application. -Excel Services Application loads only data connection files that are stored in a data connection library that is on the list of trusted data connection libraries. -Data connection libraries contain data connection files, which contain all the resources that Excel Services Application and the Excel client require to connect to an external data source. -Data connection libraries enable you to reuse and share data connections. -Data connections can be loaded by using information from the workbook file; however, using a data connection library to load data connections allows data connections to be managed separately from workbooks. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$sa = Get-SPExcelServiceApplication -New-SPExcelDataConnectionLibrary -Address "https://portal/site/salesDCL" -Description "This is the DCL where all the connections to the sales data are stored." -ExcelServiceApplication $sa -``` - -This example adds a new data connection library (DCL) and then sets its description to the list of trusted data connection libraries that is in the Excel Services Application Web service application named MyExcelService. - -Workbooks can use connection files stored in that library to refresh data on the Excel Services Application Web service application. - - -## PARAMETERS - -### -Address -Specifies the address of the data connection library. -The address must be unique in the list of trusted data connection libraries. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelDataConnectionLibrary list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a friendly description for the data connection library. - -The type must be a valid string; for example, this is a custom OLEDB provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelDataProvider.md deleted file mode 100644 index 78d27c5635..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelDataProvider.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spexceldataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: New-SPExcelDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPExcelDataProvider - -## SYNOPSIS -Adds a new safe data provider to Excel Services Application. - - -## SYNTAX - -``` -New-SPExcelDataProvider -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> -ProviderId <String> - -ProviderType <DataProviderType> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Description <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPExcelDataProvider` cmdlet adds a data provider to the list of safe data providers in an Excel Services Application Web service application. -Excel Services Application refreshes external data connections only if the data provider for a connection is on the list of safe data providers. -Excel Services Application includes a set of common data providers on this list. -Therefore, using cmdlets to modify safe data providers typically occurs only in custom data connection scenarios. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPExcelServiceApplication -identity "MyExcelService" | New-SPExcelDataProvider -providerID "CustomOLEDB" -ProviderType OleDb -description "This is a custom OLEDB provider" -``` - -This example adds a new custom OLEDB data provider to the list of safe data providers for the Excel Services Application Web service application named MyExcelService. - - -### ------------------EXAMPLE 2------------------ -``` -Get-SPExcelServiceApplication | New-SPExcelDataProvider -providerID "CustomOLEDB" -ProviderType OleDb -description "This is a custom OLEDB provider" -``` - -This example adds a new custom OLEDB data provider to the list of safe data providers for all Excel Services Application Web service application in the farm. - - -## PARAMETERS - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelDataProvider list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ProviderId -Specifies the name of the provider. -This ID should be present in the connection strings generated by this provider and the ID must be unique for the provider type. - -The type must be a valid name of a provider; for example CustomOLEDB. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProviderType -Specifies the supported type of data provider to add to safe provider list. - -The type must be one of the following: OleDb, Odbc, or OdbcDsn. - -```yaml -Type: DataProviderType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a friendly description for the new data provider. - -The type must be a valid string; for example, "This is a custom OLEDB provider". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelFileLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelFileLocation.md deleted file mode 100644 index 1a8e22c450..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelFileLocation.md +++ /dev/null @@ -1,604 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spexcelfilelocation -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: New-SPExcelFileLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPExcelFileLocation - -## SYNOPSIS -Adds a new trusted location to Excel Services Application. - - -## SYNTAX - -``` -New-SPExcelFileLocation -Address <String> -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> - [-AbortOnRefreshOnOpenFail] [-AssignmentCollection <SPAssignmentCollection>] - [-AutomaticVolatileFunctionCacheLifetime <Int32>] [-ChartAndImageSizeMax <Int32>] - [-ConcurrentDataRequestsPerSessionMax <Int32>] [-Confirm] [-DefaultWorkbookCalcMode <DefaultWorkbookCalcMode>] - [-Description <String>] [-DisplayGranularExtDataErrors] [-ExternalDataAllowed <AllowExternalData>] - [-IncludeChildren] [-LocationType <LocationType>] [-ManualExtDataCacheLifetime <Int32>] - [-NewWorkbookSessionTimeout <Int32>] [-PeriodicExtDataCacheLifetime <Int32>] [-RequestDurationMax <Int32>] - [-RESTExternalDataAllowed] [-SessionTimeout <Int32>] [-ShortSessionTimeout <Int32>] [-UdfsAllowed] - [-WarnOnDataRefresh] [-WhatIf] [-WorkbookSizeMax <Int32>] [-ChartRenderDurationMax <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPExcelFileLocation` cmdlet adds a new location to the list of trusted file locations in an Excel Services Application Web service application. -Excel Services Application loads only workbooks that are stored in a trusted file location. -Properties of trusted file locations control how workbooks can be used when loaded on Excel Services Application. -Excel Services Application always enforces the properties defined by the trusted file location from which a workbook was loaded. -The properties that the trusted file location uses are determined through comparison of the file path for the workbook with the Address parameter of the trusted file location. - -The longest match takes precedence. -For example, if https://portal/site/ and https://portal/site/subsite are trusted locations and you load a workbook from the subsite, the application uses the properties from the subsite trusted location because it has the longest matching address. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Get-SPExcelServiceApplication -identity "MyExcelService" | New-SPExcelFileLocation -address "https://myportal/myTeam" -includechildren -locationType SharePoint -description "This is my team's site on myPortal." -workbooksizemax 50 -externaldataallowed DclAndEmbedded -WarnOnDataRefresh:$false -``` - -This example adds a new trusted file location to the list of trusted file locations that is in the Excel Services Application Web service application named MyExcelService. - -This example enables workbooks to load from any child or subfolder that starts with https://myPortal/myTeam. -All workbooks loaded from this location must be smaller than 50 megabytes (MB) in size. -The workbooks can refresh external data by using connections that are embedded in the workbook file or stored in a data connection library. -A warning message that the workbook is attempting to refresh external data will not be displayed. - - -### ------------------EXAMPLE 2------------------ -``` -Get-SPExcelServiceApplication -identity "MyExcelService" | New-SPExcelFileLocation -address https://myPortal/myTeam/managers -locationType SharePoint -description "This is the manager's subsite for myTeam." -``` - -This example adds a new trusted file location to the list of trusted file locations that is in the Excel Services Application Web service application named MyExcelService with a given address and description. - - -## PARAMETERS - -### -Address -Specifies a Web folder, or file directory from which Excel Services Application can load workbooks. - -The type must be a valid URL, in the form https://myPortal/myTeam; or a valid UNC path in form, \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AbortOnRefreshOnOpenFail -Specifies that the loading of a Excel Services Application file automatically fails if an automatic data refresh operation fails when the file is opened. -The load is failed only if the following conditions are true: - -- The user has SharePoint Product and Technologies read-only permissions to the file. -- The workbook file has data connections that are refreshed automatically when the Excel Services Application file is opened. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AutomaticVolatileFunctionCacheLifetime -Specifies the maximum time, in seconds, that a computed value for a volatile function is cached for automatic recalculations. -Valid values include: - --1 Calculates once when the workbook loads. - -0 Always calculates. - -1 to 2073600 Caches 1 second to 24 days. -The default integer value is 300. - -The type must be the integers -1 or 0, or an integer value in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChartAndImageSizeMax -Specifies the maximum size, in megabytes, of a chart or image that can be opened. -The default value is 1. - -The type must be a valid integer greater than 0. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConcurrentDataRequestsPerSessionMax -Specifies the maximum number of concurrent external data requests allowed in each session. -If a session must issue more than this number of requests, additional requests must be queued. -The scope of this setting is the logical server. -The default value is 5. - -The type must be a positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultWorkbookCalcMode -Specifies the calculation mode of workbooks. -Settings other than File override the workbook settings. -The default setting is File. - -The type must be one of the following: File, Manual, Auto, or AutoDataTables. - -```yaml -Type: DefaultWorkbookCalcMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a friendly description for the new file location. - -The type must be a valid string; for example, this is the file location of the monthly sales reports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayGranularExtDataErrors -Displays granular error messages for external data failures for files in this location. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDataAllowed -Specifies the type of external data access allowed for workbooks. -None specifies that data refresh is disabled. -Dcl specifies that data is refreshed only when it uses a connection file in a trusted data connection library. -DclandEmbedded specifies that a data connection library can be used but is not required. -The scope of this setting is the trusted location. -The default value is None. - -The type must be any of the following settings: - -None - -Dcl - -DclAndEmbedded - -```yaml -Type: AllowExternalData -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeChildren -Indicates that subordinate URLs, directories and libraries are trusted. -For example, if the trusted file location is https://portal and IncludeChildren is true, https://portal/subSite is also trusted, as is any URL subordinate to the URL specified in Address. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationType -Specifies the type of location. -Location type indicates how Excel Services Application retrieves files from the location specified in Address. -The default setting is the SharePoint type. -The default value is SharePoint. - -The type must be one of the following: SharePoint, UNC, or HTTP. - -```yaml -Type: LocationType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManualExtDataCacheLifetime -Specifies the time, in seconds, that Excel Services Application waits before it re-issues a manual, or user-initiated, external data request. -During this time period, the results from the previous external data request can be returned from an external data cache. -The default value is 300. - -The valid values are any one of the following items: - --1 Never refresh after first query.1 to 2073600- Caches 1 second to 24 days. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewWorkbookSessionTimeout -Specifies the time, in seconds, that a session for a new, unsaved, workbook remains active on Excel Services Application with no user activity. -Valid values include the following: - --1 Session never expires. - -0 Session expires at the end of a single request. - -1 to 2073600 Remains active 1 second to 24 days. -The default value is 1800. - -The type must be -1, 0, or an integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PeriodicExtDataCacheLifetime -Specifies the time, in seconds, that Excel Services Application waits before it re-issues an on-open or periodic (that is, automatic) external data request. -During this time period, the results from the previous external data request can be returned from an external data cache. -A value of -1 specifies never to refresh after the first query. -The default value is 300. - -The type must be -1, 0, or integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestDurationMax -Specifies the maximum duration, in seconds, for a single request in a session. -After this time elapses, the request times out. -The default value is 300. - -The type must be -1 (no limit) or an integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RESTExternalDataAllowed -Specifies whether requests from the Representational State Transfer (REST) Application Programming Interface (API) are permitted to refresh external data connections. -The RESTExternalDataAllowed parameter has no effect if ExternalDataAllowed parameter is set to None. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionTimeout -Specifies the time, in seconds, that a session remains active on Excel Services Application with no user activity. -Valid values include the following: - --1 Session never expires. - -0 session expires at the end of a single request. - -1 to 2073600 Remains active 1 second to 24 days. -The default value is 300. - -The type must be -1, 0, or an integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShortSessionTimeout -Specifies the time, in seconds, that a user has to make the initial interaction with a spreadsheet. -After this time has elapsed, if the user is not active, the session is closed. -The value must always be less than SessionTimeout. -If the ShortSessionTimeout value is greater than or equal to SessionTimeout, an error is returned. -The default value is 75. - -The type must be -1 or an integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UdfsAllowed -Specifies that user-defined functions can be called by workbooks that are loaded from the trusted file location that is specified in Address. - -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarnOnDataRefresh -Specifies that a warning is displayed to the user on the first refresh of data for the workbook. -The default value is True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookSizeMax -Specifies the maximum size, in megabytes, of a workbook that can be loaded. -The default value is 10. - -The type must be an integer value in the range of 1 to 2000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChartRenderDurationMax -{{Fill ChartRenderDurationMax Description}} - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelServiceApplication.md deleted file mode 100644 index 9b44133f93..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelServiceApplication.md +++ /dev/null @@ -1,567 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spexcelserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: New-SPExcelServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPExcelServiceApplication - -## SYNOPSIS -Creates a new instance of Excel Services Application. - - -## SYNTAX - -### ExistingTargetApplicationParameterSet -``` -New-SPExcelServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-Name <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-CachingOfUnusedFilesEnable] [-Confirm] - [-CrossDomainAccessAllowed] [-Default] [-EncryptedUserConnectionRequired <EncryptedConnectionMode>] - [-ExternalDataConnectionLifetime <Int32>] [-FileAccessMethod <FileAccessMethod>] - [-LoadBalancingScheme <LoadBalancingScheme>] [-MemoryCacheThreshold <Int32>] [-PrivateBytesMax <Int32>] - [-SessionsPerUserMax <Int32>] [-SiteCollectionAnonymousSessionsMax <Int32>] - [-TerminateProcessOnAccessViolation] [-ThrottleAccessViolationsPerSiteCollection <Int32>] - [-UnattendedAccountApplicationId <String>] [-UnusedObjectAgeMax <Int32>] [-WhatIf] [-WorkbookCache <String>] - [-WorkbookCacheSizeMax <Int32>] [-UseEffectiveUserName] [-WorkbookModelUsageTracker <String>] - [<CommonParameters>] -``` - -### NewTargetApplicationParameterSet -``` -New-SPExcelServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-Name <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-CachingOfUnusedFilesEnable] [-Confirm] - [-CrossDomainAccessAllowed] [-Default] [-EncryptedUserConnectionRequired <EncryptedConnectionMode>] - [-ExternalDataConnectionLifetime <Int32>] [-FileAccessMethod <FileAccessMethod>] - [-LoadBalancingScheme <LoadBalancingScheme>] [-MemoryCacheThreshold <Int32>] [-PrivateBytesMax <Int32>] - [-SessionsPerUserMax <Int32>] [-SiteCollectionAnonymousSessionsMax <Int32>] - [-TerminateProcessOnAccessViolation] [-ThrottleAccessViolationsPerSiteCollection <Int32>] - [-UnusedObjectAgeMax <Int32>] [-WhatIf] [-WorkbookCache <String>] [-WorkbookCacheSizeMax <Int32>] - [-UnattendedServiceAccount <PSCredential>] [-UseEffectiveUserName] [-WorkbookModelUsageTracker <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPExcelServiceApplication` cmdlet creates a new Excel Services Application Web service application with new settings. -After you create a new Excel Services Application Web service application, you can use the `Set-SPExcelServiceApplication` cmdlet to modify the global settings of the new application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -New-SPExcelServiceApplication -Name "MyExcelService" -ApplicationPool "SharePoint Services" -``` - -This example creates a new instance of Excel Services Application with the display name MyExcelService. - - -### ------------------EXAMPLE 2------------------ -``` -New-SPExcelServiceApplication -Name "My Excel Service" -ApplicationPool "SharePoint Services" -SessionsPerUserMax 5 -``` - -This example creates a new instance of Excel Services Application with the display name My Excel Service and allows only five sessions per user for each back-end application server computer that is running Excel Services Application. - - -## PARAMETERS - -### -ApplicationPool -Specifies the existing IIS application pool to run the Web service in for the new Excel Service application. - -The type must be a valid SPIisWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies a friendly name for the new Excel Services Application Web service application. -The name that you use must be a unique name of an Excel Services Application Web service application that is in this farm. -The name can be a maximum of 128 characters. -The default value is Service_numofapplications+1. - -The type must be a valid string; for example, MyExcelServiceApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CachingOfUnusedFilesEnable -Specifies that files that are no longer used by Excel Services Application can remain in the cache for later use. -The default is true when the parameter is not specified on the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrossDomainAccessAllowed -Specifies that trusted workbooks and data connection files can be requested and rendered by Web Parts or pages that reside in other HTTP domains. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -Specifies that the proxy for this service application is added to the default proxy group of the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptedUserConnectionRequired -Requires that encryption is used between the end user and the Excel Services Application server. -The scope of this setting is the logical server. -The default value is None. - -The type must be one of the following: None or Connection. - -```yaml -Type: EncryptedConnectionMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDataConnectionLifetime -Specifies the maximum number of seconds that an external data connection can remain open in the connection pool. -Valid values include: - --1 Never recycle - -1 to 2073600 Remain active 1 second to 24 days. - -The default value is 1800. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileAccessMethod -Specifies the authentication method that Excel Services Application uses to retrieve files. -UseFileAccessAccount specifies that all workbooks always use the credentials of the service account running Excel Services Application. -UseImpersonation specifies that Excel Services Application retrieves the workbook files as the user who is making the request. -The default value is UseImpersonation. - -The type must be one of the following: UseImpersonation or UseFileAccessAccount. - -```yaml -Type: FileAccessMethod -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoadBalancingScheme -Specifies the load-balancing schema that is used by the Excel Services Application Web service application for sending requests to different back-end computers that are running Excel Calculation Services. -The default value is WorkbookURL. - -The type must be one of the following: RoundRobin, Local, or WorkbookURL. - -```yaml -Type: LoadBalancingScheme -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MemoryCacheThreshold -Specifies the percentage of the maximum private bytes that can be allocated to inactive objects. -When the memory cache threshold is exceeded, cached objects that are not currently in use are released. -Setting this value to 0 disables caching of inactive objects. -The default value is 90. - -The type must be an integer in the range of 0 to 95. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateBytesMax -Specifies the maximum private bytes, in megabytes, used by Excel Services Application. -When set to -1, the maximum private bytes defaults to 50 percent of physical memory on the computer. -Valid values include -1 for no limit, and any positive integer. -The default value is -1. - -The type must be -1 or any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerUserMax -Specifies the maximum number of sessions allowed for a user. -If a user reaches this maximum, the oldest session will be deleted when a new session is started. -Valid values include -1 for no limit, and any positive integer. -The default value is 25. - -The type must be -1 or any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollectionAnonymousSessionsMax -Specifies the maximum number of anonymous sessions allowed per site collection. -A value of 0 specifies that no anonymous sessions are allowed. -Valid values include -1 for no limit, 0 to disable the setting, or any positive integer. -The default value is 25. - -The type must be -1, 0, or any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TerminateProcessOnAccessViolation -Terminates Excel Services Application when an access violation occurs in the process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThrottleAccessViolationsPerSiteCollection -Specifies that if a workbook causes an access violation error on Excel Services Application, all files that originate from that workbook's site collection are blocked from loading for the specified period (in seconds). -Existing sessions for files on that site collection are unaffected. -Valid values include 0 to disable the setting, and the range of 1 to 2073600 seconds (24 days). -The default value is 0. - -The type must be an integer value in the range of 0 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnattendedAccountApplicationId -Specifies that the application ID that is used to look up the unattended service account credentials from the secure store service specified by UnattendedAccountSecureServiceAppName. -The secure store service is contacted when this parameter is set and specific error cases occur. -Valid values are alphanumeric strings with a maximum of 256 characters. -The default value is an empty string. - -The type must be a valid string of alphanumeric characters; for example, UnattendedServiceAccountID. - -The unattended account is a single account that all workbooks can use to refresh data. -An unattended account is required when workbook connections specify None for authentication, or when any non-Windows credentials are used to refresh data. - -```yaml -Type: String -Parameter Sets: ExistingTargetApplicationParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnusedObjectAgeMax -Specifies the maximum amount of time, in minutes, that objects not currently used in a session are kept in the memory cache. -Valid values include -1 for no maximum setting, and a positive integer in the range of 1 to 34560 minutes (24 days). -The default value is -1. - -The type must be -1, or an integer in the range of 1 to 34560. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookCache -Specifies the local file system location of the cache that is used for storing workbooks used by Excel Services Application. - -If no value is specified, then the default value is a subdirectory in the system temporary directory. - -The type must be a valid path in either of the following forms: - --- C:\folder_name --- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookCacheSizeMax -Specifies the maximum allowable size, in megabytes, of an individual session. -The default value is 0. - -The type must be any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnattendedServiceAccount -{{Fill UnattendedServiceAccount Description}} - -```yaml -Type: PSCredential -Parameter Sets: NewTargetApplicationParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseEffectiveUserName -{{Fill UseEffectiveUserName Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookModelUsageTracker -{{Fill WorkbookModelUsageTracker Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelUserDefinedFunction.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelUserDefinedFunction.md deleted file mode 100644 index ba8914a4d9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPExcelUserDefinedFunction.md +++ /dev/null @@ -1,214 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spexceluserdefinedfunction -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: New-SPExcelUserDefinedFunction -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPExcelUserDefinedFunction - -## SYNOPSIS -Adds a new user-defined function to Excel Services Application. - - -## SYNTAX - -``` -New-SPExcelUserDefinedFunction -Assembly <String> -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> - [-AssemblyLocation <AssemblyLocation>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Description <String>] [-Enable] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPExcelUserDefinedFunction` cmdlet adds a user-defined function to an Excel Services Application Web service application. -Excel Services Application uses only user-defined functions that have an entry in the list of user-defined functions. -User-defined functions are managed code assemblies that can be called from an Excel Services Application workbook by using standard Excel Services Application formula syntax. -The assemblies can perform custom logic or other actions, such as refresh data. -Windows PowerShell cmdlets operate on the entries that are in the list of user-defined functions, but they do not operate on the assemblies. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPExcelServiceApplication | New-SPExcelUserDefinedFunction -Assembly "SampleCompany.SampleApplication.SampleUdf" -AssemblyLocation GAC -``` - -This example adds the SampleComany.SampleApplication.SampleUdf file to every Excel Services Application Web service application in the farm. - -The user-defined function assembly is deployed to the global assembly cache (GAC). - - -## PARAMETERS - -### -Assembly -Specifies the strongly typed name of the assembly. -The name must be unique in the list of user-defined functions. -The name can be a maximum of 4096 alphanumeric characters. - -The type must be a string of alphanumeric characters; for example: - --- SampleCompany.SampleApplication.SampleUdf --- C:\UDFs\SampleUdf.dll --- \\\\MyNetworkServer\UDFs\SampleUdf.dll - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the list of user-defined functions. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssemblyLocation -Specifies the location where the assembly is stored. -The default value is GAC. - -The type must be one of the following: GAC or LocalFile. - -```yaml -Type: AssemblyLocation -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a friendly description for the user-defined function. -The name can be a maximum of 4096 alphanumeric characters. -The default value is an empty string. - -The type must be a valid string of alphanumeric characters; for example, this is the user-defined function for consolidation reports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -Activates the user-defined function for use with Excel Services Application. -The default value is True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPLogFile.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPLogFile.md deleted file mode 100644 index c054b60d42..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPLogFile.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-splogfile -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPLogFile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPLogFile - -## SYNOPSIS -Creates a new log file. - - -## SYNTAX - -``` -New-SPLogFile [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPLogFile` cmdlet ends the current log file and starts a new log file. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPLogFile -``` - -This example ends the current log file and starts a new log file. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPManagedAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPManagedAccount.md deleted file mode 100644 index c30b044620..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPManagedAccount.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spmanagedaccount -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPManagedAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPManagedAccount - -## SYNOPSIS -Registers a new managed account. - - -## SYNTAX - -``` -New-SPManagedAccount [-Credential] <PSCredential> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - - -## DESCRIPTION -The `New-SPManagedAccount` cmdlet registers a new managed account for the specified Credential or Username and Password. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$cred = Get-Credential -New-SPManagedAccount -Credential $cred -``` - -This example adds a new managed account to the farm by using credentials that are prompted. - - -## PARAMETERS - -### -Credential -Indicates the Credential object that specifies the credentials of the new managed account. -If you use Credential, you cannot specify Username and Password. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPManagedPath.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPManagedPath.md deleted file mode 100644 index 2d7bea2e12..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPManagedPath.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spmanagedpath -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPManagedPath -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPManagedPath - -## SYNOPSIS -Creates a new managed path for the given Web application for all host header site collections. - - -## SYNTAX - -### HostHeader -``` -New-SPManagedPath [-RelativeURL] <String> [-HostHeader] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Explicit] [-WhatIf] [<CommonParameters>] -``` - -### WebApplication -``` -New-SPManagedPath [-RelativeURL] <String> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Explicit] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `New-SPManagedPath` cmdlet adds a new managed path to a given Web application or for use with all host header site collections. -If the HostHeader switch is provided, the managed path is shared among all host-named site collections; otherwise, a Web application must be specified to create this managed path within. -The relative URL is a partial URL that represents the managed path. -When the slash mark (/) is used, the root is defined. -If the Explicit parameter is not provided, the new managed path is a wildcard path. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPManagedPath "Teams" -WebApplication "https://somesite/" -``` - -This example creates a Teams managed path for a given Web application (https://somesite). - - -## PARAMETERS - -### -RelativeURL -Specifies the relative URL for the new managed path. - -The type must be a valid partial URL such as site or sites/teams/. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -HostHeader -If this parameter is provided, this managed path applies to all host header site collections. - -```yaml -Type: SwitchParameter -Parameter Sets: HostHeader -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the Web application group to add this path. - -The type must be a valid URL, in the form https://server_name, or a GUID, in the form 1234-5678-0987645a. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Explicit -Specifies whether the managed path is explicit or wildcard. - -If not provided, the managed path is a wildcard path. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPMarketplaceWebServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPMarketplaceWebServiceApplicationProxy.md deleted file mode 100644 index 925b032127..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPMarketplaceWebServiceApplicationProxy.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spmarketplacewebserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPMarketplaceWebServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPMarketplaceWebServiceApplicationProxy - -## SYNOPSIS -Creates a service application proxy for the app identity data web service. - - -## SYNTAX - -``` -New-SPMarketplaceWebServiceApplicationProxy -Name <String> -ServiceEndpointUri <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPMarketplaceWebServiceApplicationProxy` cmdlet to create a service application proxy for the app identity data web service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPMarketplaceWebServiceApplicationProxy -Name ApplicationIdentityData -ServiceEndpointUri http://server:7800/ApplicationIdentityData.svc -DefaultProxyGroup -``` - -This example adds a proxy named ApplicationIdentityData to the app identity web service. - - -## PARAMETERS - -### -Name -Specifies the name of the service application proxy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceEndpointUri -Specifies the URI of the app identity data web service. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies whether to add the service application proxy to the default proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPMetadataServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPMetadataServiceApplication.md deleted file mode 100644 index fd74c01b4b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPMetadataServiceApplication.md +++ /dev/null @@ -1,526 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spmetadataserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPMetadataServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPMetadataServiceApplication - -## SYNOPSIS -Creates a new managed metadata service application. - - -## SYNTAX - -### NoQuota -``` -New-SPMetadataServiceApplication -Name <String> [-AdministratorAccount <String>] - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-CacheTimeCheckInterval <Int32>] [-Confirm] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] - [-DatabaseServer <String>] [-FailoverDatabaseServer <String>] [-FullAccessAccount <String>] [-HubUri <String>] - [-MaxChannelCache <Int32>] [-PartitionMode] [-ReadAccessAccount <String>] [-RestrictedAccount <String>] - [-SyndicationErrorReportEnabled] [-WhatIf] [-DisablePartitionQuota] [-DeferUpgradeActions] - [<CommonParameters>] -``` - -### Quota -``` -New-SPMetadataServiceApplication -Name <String> [-AdministratorAccount <String>] - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-CacheTimeCheckInterval <Int32>] [-Confirm] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] - [-DatabaseServer <String>] [-FailoverDatabaseServer <String>] [-FullAccessAccount <String>] [-HubUri <String>] - [-MaxChannelCache <Int32>] [-PartitionMode] [-ReadAccessAccount <String>] [-RestrictedAccount <String>] - [-SyndicationErrorReportEnabled] [-WhatIf] -GroupsPerPartition <Int32> -LabelsPerPartition <Int32> - -PropertiesPerPartition <Int32> -TermSetsPerPartition <Int32> -TermsPerPartition <Int32> - [-DeferUpgradeActions] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPMetadataServiceApplication` cmdlet to create a new managed metadata service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE 1------------- -``` -New-SPMetadataServiceApplication -Name "MetadataServiceApp1" -ApplicationPool "AppPool1" -DatabaseName "MetadataDB1" -``` - -This example creates a new managed metadata service application. - - -### -------------------EXAMPLE 2------------- -``` -New-SPMetadataServiceApplication -Name "MetadataServiceApp2" -ApplicationPool "AppPool1" -DatabaseName "MetadataDB2" -HubUri "https://sitename/" -SyndicationErrorReportEnabled -``` - -This example creates a new managed metadata service application and specifies a content type hub to be used for syndication. -It also enables error reporting during syndication. - - -### -------------------EXAMPLE 3------------- -``` -New-SPMetadataServiceApplication -Name "MetadataServiceApp3" -ApplicationPool "AppPool1" -DatabaseName "MetadataDB3" -PartitionMode -``` - -This example creates a new managed metadata service application that is partitioned, for use by sites in a subscription. - - -## PARAMETERS - -### -Name -Specifies the name of the service application to create. -The name can contain a maximum of 128 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AdministratorAccount -A comma-separated list of user accounts or service accounts in the format \<domain\>\\\<account\> that may create and run the service application. -The accounts must already exist. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies an existing IIS application pool in which to run the new managed metadata service application. - -The value must be a GUID that is the identity of an SPServiceApplicationPool object; the name of an existing application pool, or an instance of an SPServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheTimeCheckInterval -Specifies an interval, in seconds, that a front-end Web Server should wait before asking the application server for changes. -This value is set per timer job, client application, or Web application. - -The mininum value is 1, and there is no maximum value. -The default value is 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL authentication. - -If SQL authentication is to be used, either DatabaseCredentials must be specified or both the DatabaseUserName and DatabasePassword parameters must be set. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database to create for the new managed metadata service application. - -The type must be a valid name of a SQL Server database; for example MeatadataDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid name of a SQL Server database; for example SqlServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host server for the failover database server. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FullAccessAccount -Specifies a comma-separated set of application pool accounts in the format \<domain\>\\\<account\> that will be given read/write permission to the managed metadata service's term store and content type gallery. -The accounts must already exist. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HubUri -Specifies the fully qualified URL of the site collection that contains the content type gallery that the service will provide access to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxChannelCache -Specifies the maximum number of Windows Communication Foundation (WCF) channels that a front-end Web server should hold open to the application server. - -This value is set per timer job, client application, or Web application. - -The minimum value is 0, and there is no maximum value. The default value is 4. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restrict data by subscription. - -Note This property cannot be changed after the service application has been created. - -This property has no effect on SharePoint Server 2019. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadAccessAccount -Specifies a comma-separated set of application pool accounts in the format \<domain\>\\\<account\> that will be given read-only permission to the managed metadata service's term store and content type gallery. - -The accounts must already exist. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictedAccount -Specifies a comma-separated set of application pool accounts in the format \<domain\>\\\<account\> that will be given permission to read the managed metadata service's term store and content type gallery; and permission to write to open term sets and local term sets and to create new enterprise keywords. - -The accounts must already exist. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SyndicationErrorReportEnabled -Enables reporting of errors when content types are imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisablePartitionQuota -Disables partition quotas. - -```yaml -Type: SwitchParameter -Parameter Sets: NoQuota -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupsPerPartition -Sets the maximum number of Term Groups per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LabelsPerPartition -Sets the maximum number of Labels per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertiesPerPartition -Sets the maximum number of Properties per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TermSetsPerPartition -Sets the maximum number of Term Sets per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TermsPerPartition -Sets the maximum number of Terms per partition. -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies if the upgrade process is to be deferred and manually completed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPMetadataServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPMetadataServiceApplicationProxy.md deleted file mode 100644 index 1dd98ed97f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPMetadataServiceApplicationProxy.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spmetadataserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPMetadataServiceApplicationProxy -schema: 2.0.0 ---- - -# New-SPMetadataServiceApplicationProxy - -## SYNOPSIS -Creates a new connection to a managed metadata service application. - - -## SYNTAX - -``` -New-SPMetadataServiceApplicationProxy -Name <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-ContentTypePushdownEnabled] [-ContentTypeSyndicationEnabled] [-DefaultProxyGroup] - [-DefaultKeywordTaxonomy] [-DefaultSiteCollectionTaxonomy] [-PartitionMode] - [-ServiceApplication <SPMetadataServiceCmdletPipeBind>] [-Uri <String>] [-WhatIf] [<CommonParameters>] -``` - - -## DESCRIPTION -Use the `New-SPMetadataServiceApplicationProxy` cmdlet to create a new connection to a managed metadata service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE 1---------------- -``` -New-SPMetadataServiceApplicationProxy -Name "MetadataServiceProxy1" -ServiceApplication "MetadataServiceApp1" -``` - -This example creates a connection to a managed metadata service application in the local farm. - - -### -------------------EXAMPLE 2---------------- -``` -New-SPMetadataServiceApplicationProxy -Name "MetadataServiceProxy3" -ServiceApplication "MetadataServiceApp3" -PartitionMode -``` - -This example creates a partitioned connection to a managed metadata service application in the local farm. - - -## PARAMETERS - -### -Name -Specifies the display name of the service application proxy to create. -The name can contain a maximum of 128 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentTypePushdownEnabled -Specifies that existing instances of changed content types in subsites and libraries will be updated. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentTypeSyndicationEnabled -Specifies that this connection will provide access to the content types that are associated with the managed metadata service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the connection be added to the default proxy group for the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultKeywordTaxonomy -Specifies that new enterprise keywords will be stored in the term store associated with the managed metadata service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultSiteCollectionTaxonomy -Specifies that the term set that is created when you create a new managed metadata column will be stored in the term store associated with the managed metadata application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restrict data by subscription. - -This property cannot be changed after the service application proxy has been created. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the local managed metadata service application to connect to. -The service application must exist on the local farm. - -The type must be a valid GUID; a valid name of the service application; or an instance of a valid SPMetadataServiceApplication object. - -```yaml -Type: SPMetadataServiceCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Uri -Specifies the URI of a remote managed metadata service application to connect to. - -To specify the managed metadata service application that this proxy is connecting to, you must set only the URI parameter or only the ServiceApplication parameter. - -The type must be a valid URL, in the form urn:schemas-microsoft-com:sharepoint:service:fa5c65ebed244a15817768825004f3a7#authority=urn:uuid:acdd6deff6sd4bb899f5beb42051bf3b7&authority=https:// \<server\>:32844/Topology/topology.svc. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplication.md deleted file mode 100644 index 84d52f8f47..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplication.md +++ /dev/null @@ -1,714 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spperformancepointserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPPerformancePointServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPPerformancePointServiceApplication - -## SYNOPSIS -Creates a new service application for the PerformancePoint Service. - - -## SYNTAX - -``` -New-SPPerformancePointServiceApplication [-Name] <String> - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AnalyticQueryCellMax <Int32>] - [-AnalyticQueryLoggingEnabled <Boolean>] [-ApplicationCacheEnabled <Boolean>] - [-ApplicationCacheMinimumHitCount <Int32>] [-ApplicationProxyCacheEnabled <Boolean>] - [-AssignmentCollection <SPAssignmentCollection>] [-CommentsDisabled <Boolean>] [-CommentsScorecardMax <Int32>] - [-Confirm] [-DatabaseFailoverServer <String>] [-DatabaseName <String>] [-DatabaseServer <String>] - [-DatabaseSQLAuthenticationCredential <PSCredential>] [-DataSourceQueryTimeoutSeconds <Int32>] - [-DecompositionTreeMaximum <Int32>] [-ElementCacheSeconds <Int32>] [-FilterRememberUserSelectionsDays <Int32>] - [-FilterTreeMembersMax <Int32>] [-IndicatorImageCacheSeconds <Int32>] [-MSMQEnabled <Boolean>] - [-MSMQName <String>] [-SelectMeasureMaximum <Int32>] [-SessionHistoryHours <Int32>] - [-ShowDetailsInitialRows <Int32>] [-ShowDetailsMaxRows <Int32>] [-ShowDetailsMaxRowsDisabled <Boolean>] - [-TrustedContentLocationsRestricted <Boolean>] [-TrustedDataSourceLocationsRestricted <Boolean>] [-WhatIf] - [-AnalyticResultCacheMinimumHitCount <Int32>] [-DataSourceUnattendedServiceAccountTargetApplication <String>] - [-FilterSearchResultsMax <Int32>] [-UseEffectiveUserName <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPPerformancePointServiceApplication` cmdlet creates a new PerformancePoint Service on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE------------------------ -``` -New-SPPerformancePointServiceApplication -Name PPS_Application_01 -ApplicationPool PPS_Application_Pool_01 -``` - -This example creates a new PerformancePoint Service application named PPSApp_01 and sets it to run under an application pool named PPS_Application_Pool_01. - - -## PARAMETERS - -### -Name -Specifies the name of the new PerformancePoint Service application. - -The type must be a valid name of a PerformancePoint Service application; for example, PerfPointApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing IIS application pool to run the Web service in for the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AnalyticQueryCellMax -Specifies the maximum number of returned cells in an analytic grid. - -A valid integer value from 1 through 1,000,000,000. -The default value is 100,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnalyticQueryLoggingEnabled -Turns on verbose logging of query events. - -The type must be one of the following: True or False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationCacheEnabled -Specifies whether the rendered output cache on the application server is on (True) or off (False). -The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationCacheMinimumHitCount -Specifies the minimum number of times rendered output must be requested before it is added to cache. -The default value is 2. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationProxyCacheEnabled -Specifies rendered output cache on the front end Web server. -The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CommentsDisabled -Specifies that users can add comments to scorecard cells. - -The type must be one of the following: true or false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CommentsScorecardMax -Specifies the maximum number of comments that can be added to a scorecard. -The default value is 1000. - -The type must be an integer value from 1 through 1,000,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseFailoverServer -Specifies the name of the database server that contains the PerformancePoint Services database that must be mirrored. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the PerformancePoint Services database that will be created when the service application is provisioned. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the database server where the PerformancePoint Services database will be created. -This should be the same server name that is used for the SharePoint content and configuration databases. - -The value may be written as SQL instance\server if it is not referring to the default instance. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseSQLAuthenticationCredential -Determines whether to use Windows authentication or SQL Server authentication when connecting to a PerformancePoint Services database. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataSourceQueryTimeoutSeconds -Specifies the time, in seconds, before a data source query times out. -The default value is 300. - -The type must be an integer value in the range of 1 to 36,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DecompositionTreeMaximum -Specifies the maximum number of items (per level) returned to the decomposition tree visualization. - -A valid integer value from 1 through 1,000,000. -The default value is 25. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ElementCacheSeconds -Specifies the first class object cache expiration time. -The default value is 15. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterRememberUserSelectionsDays -Specifies the number of days that user filter selections are remembered. -The default value is 90. - -The type must be an integer value from 1 through 10,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterTreeMembersMax -Specifies the maximum number of records to show in filter treeview control. -The default value is 500. - -The type must be an integer value from 1 through 100,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IndicatorImageCacheSeconds -Specifies the time, in seconds, that key performance indicator (KPI) icons are cached. -The default value is 10. - -The type must be an integer value from 1 through 3,600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MSMQEnabled -Specifies that notifications are sent to Microsoft Message Queuing (MSMQ) on content change. - -The type must be one of the following: true or false. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MSMQName -Specifies the name of the queue. -The queue name can contain a maximum of 380 characters, and cannot contain the following characters: CR (ASCII 13), LF (ASCII 10), backslash (\\), plus sign (+, comma (,), or quotation marks (""). - -The type must be a valid MSMQ name; for example, MessageQueue1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SelectMeasureMaximum -Specifies the maximum number of measures to show in a dashboard Select Measure control. -The default value is 1000. - -The type must be an integer value from 1 through 1,000,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionHistoryHours -Specifies the number of hours between clearing expired user navigation history. -The default value is 2. - -The type must be an integer value from 1 through 48. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowDetailsInitialRows -Specifies the initial number of rows to retrieve for show details. -The default value is 1,000. - -The type must be an integer value from 1 through 100,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowDetailsMaxRows -Specifies the maximum number of rows to retrieve for show details. - -The type must be an integer value from 1 through 1,000,000. -The default value is 10,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowDetailsMaxRowsDisabled -Turns off the ShowDetailsInitialRows setting. -If set to True, Analysis Services controls limit. - -The type must be one of the following: True or False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedContentLocationsRestricted -Specifies that only specified locations are trusted. -The default setting is false (trust all content locations). - -The type must be one of the following: True or False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedDataSourceLocationsRestricted -Specifies that only specified locations are trusted. -The default setting is false (trust all data source locations). - -The type must be one of the following: True or False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnalyticResultCacheMinimumHitCount -The minimum number of times an analytic report needs to be accessed before caching starts happening. - -The default value is 0. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: harePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataSourceUnattendedServiceAccountTargetApplication -The name of the Secure Store Application that will be used by default to access data sources. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterSearchResultsMax -The maximum number of items to return on a Dashboard when viewing a filter. - -The default value is 5000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseEffectiveUserName -Enables the use of the Analysis Services Effective User Name feature. - -The type must be one of the following: True or False. The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplicationProxy.md deleted file mode 100644 index ad45378263..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplicationProxy.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spperformancepointserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPPerformancePointServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPPerformancePointServiceApplicationProxy - -## SYNOPSIS -Creates a proxy for a PerformancePoint Service application. - - -## SYNTAX - -``` -New-SPPerformancePointServiceApplicationProxy [-Name] <String> - -ServiceApplication <SPPerformancePointMonitoringServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Default] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPPerformancePointServiceApplicationProxy` cmdlet creates a proxy for a PerformancePoint Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE-------------------- -``` -New-SPPerformancePointServiceApplicationProxy -Name PPS_Application_Proxy_01 -ServiceApplication PPS_Application_01 -Default -``` - -This example creates a new PerformancePoint Service application proxy named PPS_Application_Proxy_01, associated with the service application named PPS_Application_01 and is added to the Default proxy group. - - -## PARAMETERS - -### -Name -Specifies the name of the PerformancePoint Service application proxy to create. - -The type must be a valid name of a PerformancePoint Service application proxy; for example, PerfPointAppProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the PerformancePoint Service application that is associated with the new service application proxy. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointMonitoringServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -Specifies that the new application proxy will be added to the default service application proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplicationTrustedLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplicationTrustedLocation.md deleted file mode 100644 index e9165fc318..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPerformancePointServiceApplicationTrustedLocation.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spperformancepointserviceapplicationtrustedlocation -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPPerformancePointServiceApplicationTrustedLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPPerformancePointServiceApplicationTrustedLocation - -## SYNOPSIS -Creates a new trusted location for a PerformancePoint Service application. - - -## SYNTAX - -``` -New-SPPerformancePointServiceApplicationTrustedLocation - -ServiceApplication <SPPerformancePointMonitoringServiceApplicationPipeBind> - -TrustedLocationType <TrustedFileType> -Type <RepositoryLocationType> -Url <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPPerformancePointServiceApplicationTrustedLocation` cmdlet creates a new trusted location for a PerformancePoint Service application. -The new trusted location can be a Content or Data Source trusted location type and is enforced only when it is enabled in the PerformancePoint Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE--------------------- -``` -New-SPPerformancePointServiceApplicationTrustedLocation -ServiceApplication PPSApp_01 -url "https://some_valid_site_url/" -Type Site -TrustedLocationType Content -``` - -This example creates a new TrustedLocation for the PPSApp_01 service application. -This creates a Content trusted location of type Site with the specified URL. - - -## PARAMETERS - -### -ServiceApplication -Specifies the PerformancePoint Service application to which the new trusted location will be added. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointMonitoringServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -TrustedLocationType -Specifies the type of trusted locations to create. -If TrustedLocationType is not specified, this cmdlet creates all the trusted locations for the specified PerformancePoint Service application. - -The type must be one of the following: Content or Data Source. - -```yaml -Type: TrustedFileType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type of trusted location. - -The type must be one of the following: Site Collection, Site, Document Library, List - -```yaml -Type: RepositoryLocationType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Specifies the URL of the trusted location site, site collection, site, document library, or list. -The type must be a valid URL, in the form https://server_name, or https://server_name/sitecollection/site/list. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the new safe data provider. - -The type must be a valid string with a maximum of 4096 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPowerPointConversionServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPPowerPointConversionServiceApplication.md deleted file mode 100644 index 96e6ef8036..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPowerPointConversionServiceApplication.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Powerpoint.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sppowerpointconversionserviceapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPPowerPointConversionServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPPowerPointConversionServiceApplication - -## SYNOPSIS -Creates a PowerPoint Conversion Service application. - - -## SYNTAX - -``` -New-SPPowerPointConversionServiceApplication [-Name] <String> - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - - -## DESCRIPTION -Use the `New-SPPowerPointConversionServiceApplication` cmdlet to create a new instance of a PowerPoint Conversion Service application by using the Name parameter. - -After the PowerPoint Conversion Service application is created, you can convert PowerPoint presentations to various formats. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPPowerPointConversionServiceApplication -Name "MyWorkgroupPPTApp" -ApplicationPool "SharePoint Web Services Default" -``` - -This example creates a new instance of the PowerPoint Conversion Service application named MyWorkgroupPPTApp and assigns it to the default application pool. - - -## PARAMETERS - -### -Name -Specifies the name of the PowerPoint Conversion Service application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Assigns an application pool that Internet Information Services (IIS) will use for this service application. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPPowerPointConversionServiceApplicationProxy](New-SPPowerPointConversionServiceApplicationProxy.md) - -[Set-SPPowerPointConversionServiceApplication](Set-SPPowerPointConversionServiceApplication.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPowerPointConversionServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPPowerPointConversionServiceApplicationProxy.md deleted file mode 100644 index d3affd75d0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPPowerPointConversionServiceApplicationProxy.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Powerpoint.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sppowerpointconversionserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPPowerPointConversionServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPPowerPointConversionServiceApplicationProxy - -## SYNOPSIS -Creates a PowerPoint Conversion Service application proxy. - - -## SYNTAX - -``` -New-SPPowerPointConversionServiceApplicationProxy [-Name] <String> - -ServiceApplication <SPPowerPointConversionServiceApplicationPipeBind> [-AddToDefaultGroup] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPPowerPointConversionServiceApplicationProxy` cmdlet to create a PowerPoint Conversion Service application proxy. -The service application proxy is instantiated on the front-end web server and acts as an intermediary between the client computer and the service application back end. - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPPowerPointConversionServiceApplicationProxy -Name "MyWorkgroupPPTAppProxy" -ServiceApplication "MyWorkgroupPPTApp" -AddtoDefaultGroup -``` - -This example creates a new instance of the PowerPoint Conversion Service application proxy named MyWorkgroupPPTAppProxy, binds it to the MyWorkgroupPPTApp service application and then adds it to the default service application proxy group - - -## PARAMETERS - -### -Name -Specifies the name of the service application proxy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the name of the service application to bind. - -```yaml -Type: SPPowerPointConversionServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AddToDefaultGroup -Adds the newly created proxy to the default service application proxy group. -If not specified, the proxy is not added to a group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPPowerPointConversionServiceApplication](New-SPPowerPointConversionServiceApplication.md) - -[Set-SPPowerPointConversionServiceApplication](Set-SPPowerPointConversionServiceApplication.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProfileServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPProfileServiceApplication.md deleted file mode 100644 index a9e5b595c5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProfileServiceApplication.md +++ /dev/null @@ -1,494 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spprofileserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPProfileServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPProfileServiceApplication - -## SYNOPSIS -Adds a User Profile Service Application to a farm. - - -## SYNTAX - -### Default -``` -New-SPProfileServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-Name <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-MySiteHostLocation <SPSitePipeBind>] - [-PartitionMode] [-ProfileDBCredentials <PSCredential>] [-ProfileDBName <String>] [-ProfileDBServer <String>] - [-ProfileSyncDBCredentials <PSCredential>] [-ProfileDBFailoverServer <String>] [-ProfileSyncDBName <String>] - [-ProfileSyncDBServer <String>] [-ProfileSyncDBFailoverServer <String>] [-SocialDBCredentials <PSCredential>] - [-SocialDBName <String>] [-SocialDBServer <String>] [-SocialDBFailoverServer <String>] [-WhatIf] - [-DeferUpgradeActions] [<CommonParameters>] -``` - -### MySiteSettings -``` -New-SPProfileServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-Name <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] -MySiteHostLocation <SPSitePipeBind> - [-MySiteManagedPath <SPPrefixPipeBind>] [-PartitionMode] [-ProfileDBCredentials <PSCredential>] - [-ProfileDBName <String>] [-ProfileDBServer <String>] [-ProfileSyncDBCredentials <PSCredential>] - [-ProfileDBFailoverServer <String>] [-ProfileSyncDBName <String>] [-ProfileSyncDBServer <String>] - [-ProfileSyncDBFailoverServer <String>] [-SiteNamingConflictResolution <String>] - [-SocialDBCredentials <PSCredential>] [-SocialDBName <String>] [-SocialDBServer <String>] - [-SocialDBFailoverServer <String>] [-WhatIf] [-DeferUpgradeActions] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. - -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `New-SPProfileServiceApplication` cmdlet adds and creates a new profile service application, or creates an instance of a profile service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPProfileServiceApplication -Name 'User Profile Service Application' -ApplicationPool 'SharePoint Web Services Default' -ProfileDBName Profile -SocialDBName Social -ProfileSyncDBname Sync -``` - -This example creates a new User Profile Service application. - - -## PARAMETERS - -### -ApplicationPool -Specifies the existing IIS application pool in which to run the Web service for the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the display name for the new User Profile Service application. -The name must be a unique name of a User Profile Service application in this farm. -The name can be a maximum of 64 characters. - -The type must be a valid name of a service application; for example, UserProfileSvcApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MySiteHostLocation -Specifies the site collection where the My Site will be created. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -```yaml -Type: SPSitePipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MySiteManagedPath -Specifies the managed path where personal sites will be created. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: SPPrefixPipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restrict data by site group. -After the PartitionMode parameter is set and the service application is created, it cannot be changed. - -This property has no effect on SharePoint Server 2019. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileDBCredentials -Specifies the set of security credentials, such as a user name and a password, that is used to connect to the User Profile database that this cmdlet creates. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileDBName -Specifies the name of the database where the User Profile database is created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileDBServer -Specifies the database where the User Profile database will be created. - -The type must be a valid name of a SQL Server database; for example, ProfileAppDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileSyncDBCredentials -Specifies the set of security credentials, such as a user name and a password, that will be used to connect to the Profile Sync database that is specified in the ProfileSyncDBName parameter. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileDBFailoverServer -Associates a content database with a specific failover server that is used in conjunction with SQL Server database mirroring. -The server name is the required value. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileSyncDBName -Specifies the database where the Profile Sync database will be created. - -The type must be a valid name of a SQL Server database; for example, ProfileSyncAppDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileSyncDBServer -Specifies the database server that will host the Profile Sync database that is specified in the ProfileSyncDBName parameter. - -The type must be a valid name of a SQL Server host; for example, SQLServerProfileSyncHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileSyncDBFailoverServer -Associates a Profile Sync database with a specific failover server that is used in conjunction with SQL Server database mirroring. -The server name is the required value. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteNamingConflictResolution -Specifies the format to use to name personal sites. - -Use one of the following integer values: - -1 Personal site collections are to be based on user names without any conflict resolution. -For example, https://portal_site/location/username/ - -2 Personal site collections are to be based on user names with conflict resolution by using domain names. -For example, .../username/ or .../domain_username/ - -3 Personal site collections are to be named by using domain and user name always, to avoid any conflicts. -For example, https://portal_site/location/domain_username/ - -The default value is 1 (do not resolve conflicts). - -```yaml -Type: String -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialDBCredentials -The set of security credentials, including a user name and a password, that is used to connect to the Social database that this cmdlet creates. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialDBName -Specifies the database where the Social database will be created. - -The type must be a valid name of a SQL Server host; for example, SQLServerSocialHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialDBServer -Specifies the database server that will host the Social database that is specified in SocialDBName. - -The type must be a valid name of a SQL Server host; for example, SQLServerSocialHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialDBFailoverServer -Associates a Social database with a specific failover server that is used in conjunction with SQL Server database mirroring. -The server name is the required value. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies if the upgrade process is to be deferred and manually completed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProfileServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPProfileServiceApplicationProxy.md deleted file mode 100644 index 023843cceb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProfileServiceApplicationProxy.md +++ /dev/null @@ -1,211 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spprofileserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPProfileServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPProfileServiceApplicationProxy - -## SYNOPSIS -Creates a User Profile Service application proxy on the local farm. - - -## SYNTAX - -### Application -``` -New-SPProfileServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-Name <String>] - [-PartitionMode] [-WhatIf] [<CommonParameters>] -``` - -### Uri -``` -New-SPProfileServiceApplicationProxy -Uri <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DefaultProxyGroup] [-Name <String>] [-PartitionMode] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `New-SPProfileServiceApplicationProxy` creates a User Profile Service application proxy on the local farm. -The proxy is added to the default proxy group for the local farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$sa = New-SPProfileServiceApplication -Name 'User Profile Service Application' -ApplicationPool 'SharePoint Web Services Default' -ProfileDBName Profile -SocialDBName Social -ProfileSyncDBname Sync -New-SPProfileServiceApplicationProxy -Name 'User Profile Service Application Proxy' -ServiceApplication $sa -DefaultProxyGroup -``` - -This example creates a new User Profile Service application proxy. - - -## PARAMETERS - -### -ServiceApplication -Specifies the local User Profile Service application that is associated with the new proxy. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription User Profile Service application (for example, ProfileSvcApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: Application -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Uri -The URI of the remote user profile service application this proxy should communicate with. -This value is required only if you plan to connect a User Profile Service application from a remote farm. - -```yaml -Type: Uri -Parameter Sets: Uri -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the User Profile Service application proxy be added to the default proxy group for the local farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name for the new User Profile Service application. -The name that you use must be a unique name of a User Profile Service application in this farm. -The name can be a maximum of 128 characters. - -The type must be a name of a valid User Profile Service application proxy; for example, UserProfileSvcProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restrict data by site group. -After the PartitionMode parameter is set and the service application is created, it cannot be changed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProjectServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPProjectServiceApplication.md deleted file mode 100644 index eb64b703ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProjectServiceApplication.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spprojectserviceapplication -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: New-SPProjectServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPProjectServiceApplication - -## SYNOPSIS -Creates a new Project Server Service application. - - -## SYNTAX - -``` -New-SPProjectServiceApplication [-Name] <String> -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Proxy] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPProjectServiceApplication` cmdlet creates a new Project Server Service application. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -New-SPProjectServiceApplication -Name "PsiApplication" -ApplicationPool "PsiApplicationPool" -Proxy -``` - -This example creates a Project Server Service application with the name PsiApplication and an application pool with the name PsiApplicationPool and it creates a Project Server Service application proxy for the application. - - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPIisWebServiceApplicationPool "PsiApplicationPool" | New-SPProjectServiceApplication -Name "PsiApplication" -``` - -This example creates a Project Server Service application with the name PsiApplication. -The result is piped using an application pool object. - - -## PARAMETERS - -### -ApplicationPool -Specifies the existing IIS application pool to run the Web service in for the new service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new Project Server Service application. - -The type must be a valid name of a Project Server Service application; for example, ProjectWebApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Proxy -Specifies that a proxy for new service application is automatically created. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProjectServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPProjectServiceApplicationProxy.md deleted file mode 100644 index fc27e3855d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPProjectServiceApplicationProxy.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spprojectserviceapplicationproxy -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: New-SPProjectServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPProjectServiceApplicationProxy - -## SYNOPSIS -Creates a proxy for a Project Server Service application. - - -## SYNTAX - -``` -New-SPProjectServiceApplicationProxy [-Name] <String> -ServiceApplication <PsiServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPProjectServiceApplicationProxy` cmdlet creates a proxy for a Project Server Service application. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### -------------------EXAMPLE 1------------------ -``` -New-SPProjectServiceApplicationProxy -Name PsiApplicationProxy -ServiceApplication PsiApplication -``` - -This example creates a Project Server Service application proxy with the name PsiApplicationProxy for the application PsiApplication. - - -### -------------------EXAMPLE 2------------------ -``` -Get-SPServiceApplication | ?{ $_.Name -eq "PsiApplication" } | New-SPProjectServiceApplicationProxy -Name "PsiApplicationProxy" -Default -``` - -This example creates a Project Server Service application proxy with the name PsiApplicationProxy for the application PsiApplication and adds the proxy to the Default proxy group. - - -## PARAMETERS - -### -Name -Specifies the name of the new proxy. - -The type must be a valid name of a Project Server Service application proxy; for example, ProjectSvcProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the Project Server Service application to associate with the new proxy. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Project Server service application (for example, ProjectWebApp1); or an instance of a valid PsiServiceApplication object. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPRequestManagementRuleCriteria.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPRequestManagementRuleCriteria.md deleted file mode 100644 index 07dca8b487..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPRequestManagementRuleCriteria.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sprequestmanagementrulecriteria -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPRequestManagementRuleCriteria -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPRequestManagementRuleCriteria - -## SYNOPSIS -Creates criteria for the rule to match. - - -## SYNTAX - -### CustomPropertyParameterSet -``` -New-SPRequestManagementRuleCriteria [-Value] <String> [-CustomHeader] <String> [-CaseSensitive] - [[-MatchType] <SPRequestManagementRuleMatchType>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -### StandardParameterSet -``` -New-SPRequestManagementRuleCriteria [-Value] <String> [-Property] <SPRequestManagementRulePropertyType> - [-CaseSensitive] [[-MatchType] <SPRequestManagementRuleMatchType>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `New-SPRequestManagementRuleCriteria` cmdlet to create criteria for the rule to match. - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPRequestManagementRuleCriteria -Property Host -Value Client01 -MatchType Equals -``` - -This example creates a new rule that matches the Host 'Client01'. - -## PARAMETERS - -### -Value -Specifies a value for the rule to match. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomHeader -Specifies the custom header for the rule. - -```yaml -Type: String -Parameter Sets: CustomPropertyParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Property -Specifies a header for a value to match. - -The following are the valid values: - ---Url - ---Urlreferrer - ---UserAgent - ---Host - ---IP - ---HttpMethod - ---SoapAction - ---CustomHeader - -```yaml -Type: SPRequestManagementRulePropertyType -Parameter Sets: StandardParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CaseSensitive -Specifies whether or not the match is case sensitive. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MatchType -Defines operators for the match. - -The following are the valid values: - ---Equals - ---Regex - ---StartsWith - ---EndsWith - -```yaml -Type: SPRequestManagementRuleMatchType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPRequestManagementSettings](Get-SPRequestManagementSettings.md) - -[Set-SPRequestManagementSettings](Set-SPRequestManagementSettings.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreApplication.md deleted file mode 100644 index 495e904cad..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreApplication.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsecurestoreapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSecureStoreApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSecureStoreApplication - -## SYNOPSIS -Creates a new Secure Store application. - - -## SYNTAX - -``` -New-SPSecureStoreApplication -ServiceContext <SPServiceContextPipeBind> -TargetApplication <TargetApplication> - [-Administrator <SPClaim[]>] [-AssignmentCollection <SPAssignmentCollection>] - [-CredentialsOwnerGroup <SPClaim[]>] -Fields <TargetApplicationField[]> [-TicketRedeemer <SPClaim[]>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPSecureStoreApplication` cmdlet creates a new Secure Store application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$usernameField = New-SPSecureStoreApplicationField -Name "UserName" -Type WindowsUserName -Masked:$false -$passwordField = New-SPSecureStoreApplicationField -Name "Password" -Type WindowsPassword -Masked:$true -$fields = $usernameField,$passwordField -$userClaim = New-SPClaimsPrincipal -Identity "CONTOSO\janedoe" -IdentityType WindowsSamAccountName -$contosoTargetApp = New-SPSecureStoreTargetApplication -Name "ContosoTargetApplication" -FriendlyName "Contoso Target Application" -ApplicationType Group -New-SPSecureStoreApplication -ServiceContext http://contoso -TargetApplication $contosoTargetApp -Fields $fields -Administrator $userClaim -``` - -This example creates a new group target application ContosoTargetApplication and then a new application for that target application. This new application has two fields; UserName of type WindowsUserName and Password of type WindowsPassword. The user with identity janedoe on the CONTOSO domain is set as the target application administrator. - - -## PARAMETERS - -### -ServiceContext -Specifies the service context for the target application. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetApplication -Specifies information about the target application. -For example, the TargetApplication object includes data values for application name, display name, contact info, enable ticketing flag and URL address to set the credential. -The schema for the TargetApplication object is defined in the ISecureSToreProviderExtended interface that exposes the target application metadata. - -```yaml -Type: TargetApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Administrator -Specifies the administrator of the new Secure Store application. - -```yaml -Type: SPClaim[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CredentialsOwnerGroup -Specifies the claims object for the groups that own the group credentials. - -```yaml -Type: SPClaim[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Fields -Specifies the field information for the application. -The default fields are username and password. - -```yaml -Type: TargetApplicationField[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TicketRedeemer -Specifies the ticket redeemer claim value. - -```yaml -Type: SPClaim[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreApplicationField.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreApplicationField.md deleted file mode 100644 index efe5259412..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreApplicationField.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsecurestoreapplicationfield -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSecureStoreApplicationField -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSecureStoreApplicationField - -## SYNOPSIS -Creates a new Secure Store application fields object. - - -## SYNTAX - -``` -New-SPSecureStoreApplicationField [-Masked] -Name <String> -Type <SecureStoreCredentialType> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPSecureStoreApplicationField` cmdlet creates a new Secure Store application field object for a target application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPSecureStoreApplicationField -Name "UserName" -Type WindowsUserName -Masked:$false -``` - -This example creates a new credential field of type WindowsUserName with the name UserName and the masked property (which when true will hide characters as they are typed in by the user) set to false. -This cmdlet is typically used in conjunction with the `New-SPSecureStoreApplication` cmdlet. - - -## PARAMETERS - -### -Masked -Masks the visible characters that are typed in the field. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new target application field. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type of credential field to add to a target application. - -The type must be one of the following: UserName, Password, Pin, Key, Generic, WindowsUserName, or WindowsPassword. - -```yaml -Type: SecureStoreCredentialType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreServiceApplication.md deleted file mode 100644 index 31c9833738..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreServiceApplication.md +++ /dev/null @@ -1,328 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsecurestoreserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSecureStoreServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSecureStoreServiceApplication - -## SYNOPSIS -Creates a new Secure Store Service application in the farm. - - -## SYNTAX - -``` -New-SPSecureStoreServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AuditingEnabled] [-Name <String>] [-AssignmentCollection <SPAssignmentCollection>] - [-AuditlogMaxSize <Int32>] [-Confirm] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] - [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] - [-FailoverDatabaseServer <String>] [-PartitionMode] [-Sharing] [-WhatIf] [-DeferUpgradeActions] - [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPSecureStoreServiceApplication` cmdlet creates a new Secure Store Service application in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -New-SPSecureStoreServiceApplication -ApplicationPool 'SharePoint Web Services Default' -AuditingEnabled:$false -DatabaseName 'Secure Store' -Name 'Secure Store Service Application' -``` - -This example creates a new Secure Store Service application with the name Contoso Secure Store with auditing disabled and creates a database with the name ContosoSSDatabase on the given database server for use with the service application. - - -## PARAMETERS - -### -ApplicationPool -Specifies the existing IIS application pool to run the Web service in for the new service application. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuditingEnabled -Turns on auditing for the Secure Store Service. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new Secure Store Service application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuditlogMaxSize -Specifies the number of days to retain the audit log. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL authentication. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the Secure Store service database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user specified in DatabaseUserName. -Use this parameter only if SQL authentication is used to access the metadata service application database. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user name to use for connecting to the database for the Secure Store service application. -Use this parameter only if SQL authentication is used to access the service application database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host server for the failover database server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restricts data by subscription ID. -This property cannot be changed after the service application is created. - -This property has no effect on SharePoint Server 2019. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Sharing -Specifies that the Secure Store service application is published and shared across the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies if the upgrade process is to be deferred and manually completed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreServiceApplicationProxy.md deleted file mode 100644 index 7e7f0ae70e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreServiceApplicationProxy.md +++ /dev/null @@ -1,208 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsecurestoreserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSecureStoreServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSecureStoreServiceApplicationProxy - -## SYNOPSIS -Creates a new Secure Store Service application proxy in the farm. - - -## SYNTAX - -### PipeBind -``` -New-SPSecureStoreServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-Name <String>] [-WhatIf] - [<CommonParameters>] -``` - -### Uri -``` -New-SPSecureStoreServiceApplicationProxy -Uri <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DefaultProxyGroup] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `New-SPSecureStoreServiceApplicationProxy` cmdlet creates a new Secure Store Service application proxy for a Secure Store Service application in the farm. - -The `New-SPSecureStoreServiceApplicationProxy` cmdlet does not specify whether the service application proxy is partitioned or not. -If you want to specify a partitioned service application proxy, a partitioned service application can be created by using the `New-SPSecureStoreServiceApplication` cmdlet. -The result of the `New-SPSecureStoreServiceApplication` cmdlet can be passed to the `New-SPSecureStoreServiceApplicationProxy` cmdlet. -Similarly, if you want to specify an unpartitioned service application proxy, an unpartitioned service application can be created by using the `New-SPSecureStoreServiceApplication` cmdlet. -The result of the `New-SPSecureStoreServiceApplication` cmdlet can be passed to the `New-SPSecureStoreServiceApplicationProxy` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$sa = New-SPSecureStoreServiceApplication -ApplicationPool 'SharePoint Web Services Default' -AuditingEnabled:$false -DatabaseName 'Secure Store' -Name 'Secure Store Service Application' -New-SPSecureStoreServiceApplicationProxy -Name 'Secure Store Service Application Proxy' -ServiceApplication $sa -``` - -This example creates a new Secure Store Service application and proxy. - - -### ------------------EXAMPLE 2------------------ -``` -$nameofproxy = "Connection to: HostedSecureStoreInParentFarm" -$proxy = Get-SPServiceApplicationProxy | where {$_ -match $nameofproxy} -$prop = $proxy.Properties -$type = $prop["Microsoft.Office.Server.Utilities.SPPartitionOptions"].GetType() -$partition = [enum]::Parse( $type, 1 ) -$prop["Microsoft.Office.Server.Utilities.SPPartitionOptions"] = $partition -$proxy.Update() -``` - -This example converts an unpartitioned secure store service application proxy in the child to a partitioned one. - - -## PARAMETERS - -### -ServiceApplication -Specifies the local Secure Store Service application associated with the new proxy. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: PipeBind -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Uri -Specifies the URI of a remote Secure Store Service application associated with the new proxy. - -The type must be a valid URI, in the form file:\\\\server_name\sitedocs. - -```yaml -Type: Uri -Parameter Sets: Uri -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the service application proxy be added to the farm's default proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new service application proxy to create. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreTargetApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreTargetApplication.md deleted file mode 100644 index 7617ccb07c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSecureStoreTargetApplication.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsecurestoretargetapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSecureStoreTargetApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSecureStoreTargetApplication - -## SYNOPSIS -Creates a new Secure Store target application. - - -## SYNTAX - -``` -New-SPSecureStoreTargetApplication -ApplicationType <TargetApplicationType> -FriendlyName <String> - -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-ContactEmail <String>] - [-SetCredentialsUri <Uri>] [-TimeoutInMinutes <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPSecureStoreTargetApplication` cmdlet creates a new Secure Store Target application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -New-SPSecureStoreTargetApplication -Name "ContosoTargetApplication" -FriendlyName "Contoso Target Application" -ApplicationType Group -``` - -This example creates a new group type target application with the given name and friendly display name. - - -## PARAMETERS - -### -ApplicationType -Specifies the type of target application. - -The type must be one of the following: Individual, Group, IndividualWithTicketing, GroupWithTicketing, RestrictedIndividual, or RestrictedGroup. - -```yaml -Type: TargetApplicationType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FriendlyName -Specifies the name of the new target application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name of the new target application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ContactEmail -Specifies the contact information for the target application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SetCredentialsUri -Specifies the URI for setting the user application credentials. - -The type must be a valid URI, in the form file:\\\\server_name\sitedocs. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutInMinutes -The time, in minutes, a ticket is valid if it is not redeemed by the target application. -Make sure that the ticket time-out value is long enough to last between the time when the ticket is issued to the time that it is redeemed The default value is 2. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPServiceApplicationPool.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPServiceApplicationPool.md deleted file mode 100644 index 24aa8b3557..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPServiceApplicationPool.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spserviceapplicationpool -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPServiceApplicationPool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPServiceApplicationPool - -## SYNOPSIS -Creates a new Web service application pool. - - -## SYNTAX - -``` -New-SPServiceApplicationPool [-Name] <String> [-Account] <SPProcessAccountPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPServiceApplicationPool` cmdlet creates a new Web service application pool in Internet Information Services (IIS). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE----------------------- -``` -New-SPServiceApplicationPool -Name 'SharePoint Web Services Default' -Account (Get-SPManagedAccount 'contoso\serviceAccount') -``` - -This example creates a new Web service application pool. - -For the Account parameter, the name of a managed account in the farm can be given. -Use the `Get-SPManagedAccount` cmdlet to view the existing managed account in the farm. -Also, a process account from the output of the `Get-SPProcessAccount` cmdlet can be used. - - -## PARAMETERS - -### -Name -Specifies the name of the new Web service application pool. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Account -Specifies the credentials that will be the identity of the new application pool. - -```yaml -Type: SPProcessAccountPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPServiceApplicationProxyGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPServiceApplicationProxyGroup.md deleted file mode 100644 index 293f77732c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPServiceApplicationProxyGroup.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spserviceapplicationproxygroup -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPServiceApplicationProxyGroup -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPServiceApplicationProxyGroup - -## SYNOPSIS -Creates a new service application proxy group. - - -## SYNTAX - -``` -New-SPServiceApplicationProxyGroup [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPServiceApplicationProxyGroup` cmdlet creates a new service application proxy group specified by the Name parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPServiceApplicationProxyGroup -Name RemoteProxyGroup -``` - -This example creates a new service application proxy with the name RemoteProxyGroup. - - -## PARAMETERS - -### -Name -Specifies the name of the new service application proxy group. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSite.md deleted file mode 100644 index 2803a8f157..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSite.md +++ /dev/null @@ -1,465 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSite - -## SYNOPSIS -Creates a new site collection at the specified URL. - - -## SYNTAX - -``` -New-SPSite [-Url] <String> -OwnerAlias <SPUserPipeBind> [-AdministrationSiteType <SPAdministrationSiteType>] - [-AssignmentCollection <SPAssignmentCollection>] [-CompatibilityLevel <Int32>] [-Confirm] - [-ContentDatabase <SPContentDatabasePipeBind>] [-Description <String>] - [-HostHeaderWebApplication <SPWebApplicationPipeBind>] [-Language <UInt32>] [-Name <String>] - [-OverrideCompatibilityRestriction] [-OwnerEmail <String>] [-QuotaTemplate <SPQuotaTemplatePipeBind>] - [-SecondaryEmail <String>] [-SecondaryOwnerAlias <SPUserPipeBind>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-Template <SPWebTemplatePipeBind>] [-WhatIf] - [-CreateFromSiteMaster] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPSite` cmdlet creates a new site collection with the URL and owner that the Url and OwnerAlias parameters. -This cmdlet can create site collections in either the SharePoint Server mode which uses the legacy versions of templates and features, or can be created in SharePoint Server mode which uses the new versions of templates and features. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -New-SPSite https://webApp/sites/test -OwnerAlias "DOMAIN\JDoe" -Language 1033 -Template STS#0 -``` - -This example creates an English site collection at https://\<site name\>/sites/test that is owned by user DOMAIN\Jdow. - - -### ------------------EXAMPLE 2----------------------- -``` -$w = Get-SPWebApplication https://webApp -New-SPSite https://www.contoso.com -OwnerAlias "DOMAIN\jdow" -HostHeaderWebApplication $w -Name "Contoso" -Template STS#0 -``` - -This example creates a host-named site collection. -Because the template is provided, the root web of this site collection will be created. - - -### ------------------EXAMPLE 3----------------------- -``` -Get-SPWebTemplate | Where{ $_.Title -eq "Team Site" } | ForEach-Object{ New-SPSite https://<site name</sites/test -OwnerAlias DOMAIN\jdow -Template $_ } -``` - -This example creates a site collection by using the "Team Site" Web template. - - -### ------------------EXAMPLE 4----------------------- -``` -New-SPSite -URL https://webApp/sites/testsite -OwnerAlias "DOMAIN\JDow" -Language 1033 -CompatibilityLevel 14 -Template STS#0 -``` - -This example creates an English 14 mode site collection by using the Team site template at https://\<site name\>/sites/testsite that is owned by user DOMAIN\Jdow - - -## PARAMETERS - -### -Url -Specifies the URL that the new site collection uses. - -If the URL is not a host header site, the URL must start with the web application URL. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -OwnerAlias -Specifies the user login name of the site owner. - -The type must be a valid user alias, in the form, Domain\username. - -```yaml -Type: SPUserPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdministrationSiteType -Specifies the site type. - -Valid values are None or TentantAdministration. - -```yaml -Type: SPAdministrationSiteType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. - -This value sets the initial CompatibilityLevel value for the site collection. - -When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the web application depending on the SiteCreationMode setting. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the name or GUID of the content database in which to create the new site. If no content database is specified, the site collection is selected automatically. - -The type must be a valid database name in the form, SiteContent1212, or a GUID in the form, 1234-5678-9807. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Describes the new site. - -If no value is specified, the value is left blank. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostHeaderWebApplication -Specifies that if the URL provided is to be a host-named site collection, the HostHeaderWebApplication parameter must be the name, URL, GUID, or SPWebApplication object for the web application in which this site collection is created. - -If no value is specified, the value is left blank. - -The type must be a valid name in one of the following forms: - ---A WebApplication - ---A URL (for example, https://server_name) - ---A GUID (for example, 1234-5678-9876-0987) - - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Specifies the language ID for the new site collection. - -If no language is specified, the site collection is created with the same language that was specified when the product was installed. - -This must be a valid language identifier (LCID). - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the title of the new site collection. - -If no name is specified, the default name is applied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverrideCompatibilityRestriction -Specifies whether to use compatibility restriction for site. - -The valid values are True or False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OwnerEmail -Specifies the email address of site owner. -If no value is specified, the value is left blank. - -The type must be a email address in the form, someone@example.com. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QuotaTemplate -Specifies the quota template for the new site.The template must exist already. - -If no template is specified, no quota is applied. - -```yaml -Type: SPQuotaTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryEmail -Specifies the email address of the secondary site owner. If no value is specified, the value is left blank. - -The type must be a email address, in the form, someone@example.com. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryOwnerAlias -Specifies the user login credentials of the secondary site owner. - -If no value is specified, the value is left blank. - -The type must be a valid user alias, in the form, Domain\username. - -```yaml -Type: SPUserPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the Site Group to get site collections. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the Web template for the root web of the new site collection. - -The template must be already installed. - -If no template is specified, no template is provisioned. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CreateFromSiteMaster -Specifies whether to create a new site using the Site Master. - -The valid values are True or False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteMaster.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteMaster.md deleted file mode 100644 index 89bcdc30a5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteMaster.md +++ /dev/null @@ -1,190 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsitemaster -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSiteMaster -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSiteMaster - -## SYNOPSIS -Creates a site master. - - -## SYNTAX - -``` -New-SPSiteMaster [-ContentDatabase] <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CompatibilityLevel <Int32>] [-Confirm] [-Language <UInt32>] - -Template <SPWebTemplatePipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the New-SPSiteMaster cmdlet to create a site master information in the farm. - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPSiteMaster -ContentDatabase WSS_Content -Template STS#0 -``` - -This example creates a site master in the database WSS_Content. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. This value sets the initial CompatibilityLevel value for the site collection. - -When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the web application depending on the SiteCreationMode setting. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the name of the database to create the site master in. For example, WSS_Content. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Language -Specifies the locale ID to use. For example, use 1033 for English. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the name of the template. - -The values are the following: - --- SPSPERS#2 - --- SPSPERS#6 - --- SPSPERS#7 - --- SPSPERS#8 - --- SPSPERS#9 - --- SPSPERS#10 - --- STS#0 - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPContentDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteSubscription.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteSubscription.md deleted file mode 100644 index 722fba6168..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteSubscription.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsitesubscription -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSiteSubscription -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSiteSubscription - -## SYNOPSIS -Creates a new site subscription. - - -## SYNTAX - -``` -New-SPSiteSubscription [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPSiteSubscription` cmdlet creates a new subscription to which the SPSites object can belong. -Sites that are members of a site subscription can share settings and configuration information. -A site collection can be a member of only one site subscription and once set, cannot be changed. - -Site subscriptions are not persisted in a database until used in conjunction with either an SPSite or the Site Subscription Settings Service. -After a site subscription is applied to any site collection in the farm, the site subscription can be retrieved by using the `Get-SPSiteSubscription` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` - -$subscription = New-SPSiteSubscription - -``` - -This example creates a new site subscription. - - -### ------------------EXAMPLE 2----------------------- -``` -$subscription = New-SPSiteSubscription -Set-SPSite -Identity https://siteUrl -SiteSubscription $subscription -``` - -This example creates a new Site Subscription and sets it on the site collection https://siteUrl. - - -### ------------------EXAMPLE 3----------------------- -``` -New-SPSite -URL https://siteUrl -OwnerAlias "DOMAIN\JDow" -Language 1033 -SiteSubscription (New-SPSiteSubscription) -``` - -This example creates a new Site Collection at https://siteUrl along with a new Site Subscription. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteSubscriptionFeaturePack.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteSubscriptionFeaturePack.md deleted file mode 100644 index cd9774d499..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteSubscriptionFeaturePack.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsitesubscriptionfeaturepack -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSiteSubscriptionFeaturePack -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSiteSubscriptionFeaturePack - -## SYNOPSIS -Creates a new SharePoint Feature set that can be used to limit the features available to a site subscription. - - -## SYNTAX - -``` -New-SPSiteSubscriptionFeaturePack [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPSiteSubscriptionFeaturePack` cmdlet to create a new SharePoint Feature set that limits the Features available to a specified site subscription. - -SharePoint Feature sets are on an Allow List of SharePoint Features that can be associated with any site subscription. -If a Feature set is assigned to a site subscription, only SPFeatures objects in that Feature set are available for use on the site collections and Webs that are members of the site subscription. -Feature sets contain a list of the GUIDs of each Feature that is on an Allow List for associated site subscriptions. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` - -$fs = New-SPSiteSubscriptionFeaturePack - -``` - -This example creates a new SharePoint Feature Pack and stores it in a variable. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceApplication.md deleted file mode 100644 index 6e461c09ef..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceApplication.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spstateserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPStateServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPStateServiceApplication - -## SYNOPSIS -Creates a new state service application. - - -## SYNTAX - -``` -New-SPStateServiceApplication [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Database <SPStateDatabasePipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPStateServiceApplication` cmdlet creates a new state service application on the farm. -A state service application is the container for state service databases. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -$db = New-SPStateServiceDatabase -Name 'StateSvcDB1' -New-SPStateServiceApplication -Name 'State Service' -Database $db -``` - -This example creates a new state service database and a state service application associated with the database. - -## PARAMETERS - -### -Name -Specifies the name of the new service application. - -The type must be a valid name of a service application; for example, StateSvcApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Database -Specifies the state service database that is associated with the new service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a state database (for example, StateSvcDB1); or an instance of a valid SPStateServiceDatabase object. - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceApplicationProxy.md deleted file mode 100644 index 365e5f83ce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceApplicationProxy.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spstateserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPStateServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPStateServiceApplicationProxy - -## SYNOPSIS -Creates a proxy for a state service application. - - -## SYNTAX - -``` -New-SPStateServiceApplicationProxy [-ServiceApplication] <SPStateServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-DefaultProxyGroup] [-Name <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPStateServiceApplicationProxy` cmdlet creates a proxy for a state service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE------------------- -``` -$db = New-SPStateServiceDatabase -Name 'State Service' -$sa = New-SPStateServiceApplication -Name 'State Service' -Database $db -New-SPStateServiceApplicationProxy -Name 'State Service Proxy' -ServiceApplication $sa -DefaultProxyGroup -``` - -This example creates a State Service database and Service Application. It then associates a new State Service Proxy with the State Service application and adds it to the Default proxy group. - - -## PARAMETERS - -### -ServiceApplication -Specifies the state service application to associate with the new proxy. - -The type must be a valid name of a state service application (for example, StateServiceApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPStateServiceApplication object. - -```yaml -Type: SPStateServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the service application proxy is added to the farm's default proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name of the new proxy. - -The type must be a valid name of a SQL Server database; for example, SessionStateDB1. -Service application proxy; for example, StateSvcAppProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceDatabase.md deleted file mode 100644 index f101be5839..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPStateServiceDatabase.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPStateServiceDatabase - -## SYNOPSIS -Creates and provisions a new state service database and installs the state database schema into it. - - -## SYNTAX - -``` -New-SPStateServiceDatabase [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseCredentials <PSCredential>] [-DatabaseServer <String>] - [-ServiceApplication <SPStateServiceApplicationPipeBind>] [-Weight <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPStateServiceDatabase` cmdlet creates and a new state service database. -This cmdlet installs the session state database schema in the state service database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -New-SPStateServiceDatabase -Name 'State Service' -``` - -This example creates a new state service database. - -## PARAMETERS - -### -Name -Specifies the name for the state service database that is stored in SQL Server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the database credentials for SQL Authentication used to access the state service database. -If this parameter is not specified, Windows authentication is used. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the state service database. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the state service application to add the state database to. - -The type must be a valid name of a state service application (for example, StateServiceApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPStateServiceApplication object. - -```yaml -Type: SPStateServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Weight -Specifies the weight for the state database. -The default value is 1. - -This parameter is used when new rows of data are allocated among the collection of databases that are associated with a service application - -The type must be a valid integer in the range of 1 to 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSubscriptionSettingsServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSubscriptionSettingsServiceApplication.md deleted file mode 100644 index 94d73db1ab..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSubscriptionSettingsServiceApplication.md +++ /dev/null @@ -1,244 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsubscriptionsettingsserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSubscriptionSettingsServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSubscriptionSettingsServiceApplication - -## SYNOPSIS -Creates a new subscription settings service application. - - -## SYNTAX - -``` -New-SPSubscriptionSettingsServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseCredentials <PSCredential>] - [-DatabaseName <String>] [-DatabaseServer <String>] [-FailoverDatabaseServer <String>] [-Name <String>] - [-WhatIf] [-DeferUpgradeActions] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPSubscriptionSettingsServiceApplication` cmdlet to create a subscription settings service application that can be used to store settings that are shared across all site collections in a single site subscription. -This cmdlet is used only in an environment where site subscriptions are used to delegate administration or partition services that are used for storing settings that are shared across all site collections in a single site subscription. -This cmdlet is used only in an environment where site subscriptions are used to delegate administration or partition services. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------EXAMPLE--------------- -``` - -$sa = New-SPSubscriptionSettingsServiceApplication -ApplicationPool 'SharePoint Web Services Default' -Name 'Subscriptions Settings Service Application' -DatabaseName 'Subscription' -New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $sa - -``` - -This example creates a Subscriptions Settings Service application. - -## PARAMETERS - -### -ApplicationPool -Specifies the IIS application pool to use for the new subscription settings application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Server Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the subscription settings database. - -If not provided, one will be generated. - -The type must be a valid name of a SQL Server database; for example, SubscriptionSettingsApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host SQL Server instance for the database specified in the DatabaseName parameter. -If not provided, the default database server will be used. - -The type must be a valid SQL Server instance name; for example, SQLServerHost1. - -The type must be a valid name of a SQL Server database; for example, SubscriptionSettingsApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host SQL Server instance for the failover database server. - -The type must be a valid SQL Server instance name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the friendly name of the new subscription settings service. - -The type must be a valid name of a subscription settings service application; for example, SubscriptionSettingsApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies if the upgrade process is to be deferred and manually completed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSubscriptionSettingsServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPSubscriptionSettingsServiceApplicationProxy.md deleted file mode 100644 index 9551ce194f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPSubscriptionSettingsServiceApplicationProxy.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spsubscriptionsettingsserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPSubscriptionSettingsServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPSubscriptionSettingsServiceApplicationProxy - -## SYNOPSIS -Creates an application proxy to a subscription settings service application. - - -## SYNTAX - -### ServiceApplication -``` -New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### Uri -``` -New-SPSubscriptionSettingsServiceApplicationProxy -Uri <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `New-SPSubscriptionSettingsServiceApplicationProxy` cmdlet to create an application proxy to a subscription settings service application. -This is required for the local farm to consume a subscription settings service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------------- -``` -$sa = New-SPSubscriptionSettingsServiceApplication -ApplicationPool 'SharePoint Web Services Default' -Name 'Subscriptions Settings Service Application' -DatabaseName 'Subscription' -New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $sa -``` - -This example creates a new Subscription Settings Service application and proxy. - -## PARAMETERS - -### -ServiceApplication -Specifies the subscription settings service application associated with the new proxy. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubscriptionSettingsApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: ServiceApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Uri -Specifies the address of the subscription settings service application to associate the new application proxy with. - -The type must be a valid URI, in the form file:\\\\server_name\sitedocs. - -```yaml -Type: String -Parameter Sets: Uri -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTranslationServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPTranslationServiceApplication.md deleted file mode 100644 index 73aca61618..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTranslationServiceApplication.md +++ /dev/null @@ -1,264 +0,0 @@ ---- -external help file: Microsoft.Office.TranslationServices.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sptranslationserviceapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPTranslationServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPTranslationServiceApplication - -## SYNOPSIS -Provisions a new instance of the Machine Translation service. - - -## SYNTAX - -``` -New-SPTranslationServiceApplication [-Name] <String> -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseCredential <PSCredential>] - [-DatabaseName <String>] [-DatabaseServer <String>] [-Default] [-FailoverDatabaseServer <String>] - [-PartitionMode] [-WhatIf] [-DeferUpgradeActions] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPTranslationServiceApplication` cmdlet to provision a new instance of the Machine Translation service on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------EXAMPLE--------------- -``` -New-SPTranslationServiceApplication -Name TranslationService -ApplicationPool 'SharePoint Web Services Default' -DatabaseServer Server1 -DatabaseName TranslationServiceDatabase -``` - -This example creates a Machine Translation service application named TranslationService which will run in the SharePoint Web Services Default service application pool. -The database will be called TranslationServiceDatabase and will be hosted on the Server1 SQL server instance. - - -## PARAMETERS - -### -Name -Specifies the unique identifier of Translation Service instance to be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the managed application pool that the instance of Translation Service will run in. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredential -Specifies the SQL Server credentials used for this Translation Service instance. -This parameter to be used only used for SQL authentication; if not present, Windows authentication is used instead. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the database name which is to be used for this Translation Service instance. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the database server which is to be used for this Translation Service instance. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -Determines whether or not the proxy for this service application should be added to the default proxy group for this Web application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the SQL server instance that will be used as a backup to the primary SQL Server instance. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Restricts this service to behave uniquely on a partitioned set of site collections. -This cannot be changed after the application is provisioned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Specifies if the upgrade process is to be deferred and manually completed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPTranslationServiceApplication](Set-SPTranslationServiceApplication.md) - -[New-SPTranslationServiceApplicationProxy](New-SPTranslationServiceApplicationProxy.md) - -[Set-SPTranslationServiceApplicationProxy](Set-SPTranslationServiceApplicationProxy.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTranslationServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPTranslationServiceApplicationProxy.md deleted file mode 100644 index f982000426..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTranslationServiceApplicationProxy.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -external help file: Microsoft.Office.TranslationServices.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sptranslationserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPTranslationServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPTranslationServiceApplicationProxy - -## SYNOPSIS -Creates a Machine Translation Service application proxy on the local farm. - - -## SYNTAX - -### ConnectLocal -``` -New-SPTranslationServiceApplicationProxy -Name <String> - -ServiceApplication <TranslationServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DefaultProxyGroup] [-PartitionMode] [-WhatIf] [<CommonParameters>] -``` - -### ConnectRemote -``` -New-SPTranslationServiceApplicationProxy -Name <String> -Uri <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-PartitionMode] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `New-SPTranslationServiceApplicationProxy` cmdlet creates a Machine Translation Service application proxy on the local farm. -The proxy is added to the default proxy group for the local farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------EXAMPLE--------- -``` -$sa = New-SPTranslationServiceApplication -Name TranslationService -ApplicationPool 'SharePoint Web Services Default' -DatabaseServer Server1 -DatabaseName TranslationServiceDatabase -New-SPTranslationServiceApplicationProxy -Name TranslationServiceProxy -ServiceApplication $sa -DefaultProxyGroup -``` - -This example creates a Machine Translation Service application and proxy in the default proxy group named TranslationServiceProxy. - - -## PARAMETERS - -### -Name -Specifies the display name for the new Machine Translation Service application. -The name that you use must be a unique name of a Machine Translation Service application in this farm. -The name can be a maximum of 128 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the local Machine Translation Service application that is associated with the new proxy. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Machine Translation Service application (for example, MachTrans1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: TranslationServiceApplicationPipeBind -Parameter Sets: ConnectLocal -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Uri -Specifies the URI of the remote machine translation service application this proxy should communicate with. -This value is required only if you plan to connect a Machine Translation Service application from a remote farm. - -```yaml -Type: String -Parameter Sets: ConnectRemote -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the Machine Translation Service application proxy be added to the default proxy group for the local farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restrict data by site group. -After the PartitionMode parameter is set and the service application is created, it cannot be changed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPTranslationServiceApplication](New-SPTranslationServiceApplication.md) - -[Set-SPTranslationServiceApplication](Set-SPTranslationServiceApplication.md) - -[Set-SPTranslationServiceApplicationProxy](Set-SPTranslationServiceApplicationProxy.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedIdentityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedIdentityTokenIssuer.md deleted file mode 100644 index 9e72d51cd7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedIdentityTokenIssuer.md +++ /dev/null @@ -1,378 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sptrustedidentitytokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPTrustedIdentityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPTrustedIdentityTokenIssuer - -## SYNOPSIS -Creates an identity provider in the farm. - - -## SYNTAX - -### BasicParameterSet -``` -New-SPTrustedIdentityTokenIssuer -ClaimsMappings <SPClaimMappingPipeBind[]> -Description <String> - -IdentifierClaim <String> -Name <String> -Realm <String> -SignInUrl <String> - [-AssignmentCollection <SPAssignmentCollection>] [-ClaimProvider <SPClaimProviderPipeBind>] - [-ImportTrustCertificate <X509Certificate2>] [-UseWReply] [-Confirm] [-RegisteredIssuerName <String>] - [-SignOutUrl <String>] [-WhatIf] [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -New-SPTrustedIdentityTokenIssuer -ClaimsMappings <SPClaimMappingPipeBind[]> -Description <String> - -IdentifierClaim <String> -Name <String> -Realm <String> -SignInUrl <String> - [-AssignmentCollection <SPAssignmentCollection>] [-ClaimProvider <SPClaimProviderPipeBind>] - -MetadataEndPoint <Uri> [-UseWReply] [-Confirm] [-SignOutUrl <String>] [-WhatIf] [<CommonParameters>] -``` - -### ActiveDirectoryBackedParameterSet -``` -New-SPTrustedIdentityTokenIssuer -Description <String> -Name <String> -Realm <String> -SignInUrl <String> - [-AssignmentCollection <SPAssignmentCollection>] [-ImportTrustCertificate <X509Certificate2>] [-UseWReply] - [-Confirm] [-IdentifierClaimIs <String>] [-RegisteredIssuerName <String>] [-SignOutUrl <String>] - [-UseDefaultConfiguration] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPTrustedIdentityTokenIssuer` cmdlet creates an identity provider in the farm. -This object is created and used only for setting this type of identity provider in a Web application. -The specified claim type cannot be NTLM, Classic NTLM, Negotiate, or Classic Negotiate. -For ASP.NET Membership provider or Role providers, no objects are persisted. -For security token service (STS) identity providers, this cmdlet creates and persists the identity provider object in the SPFarm object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------- EXAMPLE--------------------------- -``` -New-SPTrustedIdentityTokenIssuer -Name "LiveIDSTS" - Description "LiveID STS" -Certificate (Get-ChildItem "cert:Certificates (LocalComputer)\Personal\Certificates -Name "LiveID Cert") -SignInUrl https://int.contoso.com/ -IdentifierClaim "http://schemas.contoso.com/2007/05/Claims/Puid" -``` - -This example creates a new identity provider in the farm named LiveIDSTS. - - -## PARAMETERS - -### -ClaimsMappings -Specifies the mapping of the claims from the original token to the SharePoint token. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a claim mapping rule (for example, Email); or an instance of a valid SPClaimMapping object. - -```yaml -Type: SPClaimMappingPipeBind[] -Parameter Sets: BasicParameterSet, MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a description for the new identity provider. - -The type must be a valid string; for example, LiveID STS. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IdentifierClaim -Specifies which claim type from the trusted STS will be used for the new identity provider. - -The type must be a valid claim type from the trusted STS; for example, http://schemas.microsoft.com/2007/05/Claims/Puid. - -```yaml -Type: String -Parameter Sets: BasicParameterSet, MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new identity provider. - -The type must be a valid name of an identity provider; for example, LiveIDSTS. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Realm -Specifies the realm, or resource partition, associated with this trust. - -The type must be a name of a valid realm; for example, MD_REALM. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInUrl -Specifies the sign-in URLs for this trusted STS identity provider. - -The type must be a valid URL, in the form https://int.live.com/. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClaimProvider -Specifies the IP STS that can resolve and search claims for claims people picker. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of identity provider (for example, MyIDprovider1); or an instance of a valid SPIdentityProvider object. - -```yaml -Type: SPClaimProviderPipeBind -Parameter Sets: BasicParameterSet, MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImportTrustCertificate -Specifies the X.509 certificate object from trusted authentication provider farm. - -The type must be a name of a valid X.509 certificate; for example, Certificate1. - -```yaml -Type: X509Certificate2 -Parameter Sets: BasicParameterSet, ActiveDirectoryBackedParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -Specifies the URI for the metadata endpoint of the trusted provider. - -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseWReply -Includes a WReply with the token request. - -WReply is a URL at the relying party to which the requestor is redirected once sign-out processing is complete. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IdentifierClaimIs -Specifies which of the default mapped claims should be used as the identifier claim. - -Only used if the UseDefaultConfiguration parameter is set to true, otherwise use the IdentifierClaim parameter. - -```yaml -Type: String -Parameter Sets: ActiveDirectoryBackedParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegisteredIssuerName -Specifies the Registered Issuer Name instead of not using the metadata endpoint. - -```yaml -Type: String -Parameter Sets: BasicParameterSet, ActiveDirectoryBackedParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignOutUrl -Specifies the sign out URI for the trusted provider. This lets SharePoint to sign the user out from the trusted provider when they sign out from SharePoint. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SSharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultConfiguration -Specifies if the default set of claim mappings should be used. - -If UseDefaultConfiguration parameter is used, then the IdentifierClaimIs parameter must be used. - -```yaml -Type: SwitchParameter -Parameter Sets: ActiveDirectoryBackedParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedRootAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedRootAuthority.md deleted file mode 100644 index 8cc05a0652..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedRootAuthority.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sptrustedrootauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPTrustedRootAuthority -schema: 2.0.0 ---- - -# New-SPTrustedRootAuthority - -## SYNOPSIS -Creates a trusted root authority. - - -## SYNTAX - -### ManualUpdateCertificateParameterSet -``` -New-SPTrustedRootAuthority [-Name] <String> -Certificate <X509Certificate2> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -New-SPTrustedRootAuthority [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -MetadataEndPoint <Uri> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPTrustedRootAuthority` cmdlet creates a trusted root authority. -If a certificate file is used, it must have only one X509 certificate without private keys, otherwise an exception is raised. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx -New-SPTrustedRootAuthority -Name "WFEFarm1" -Certificate $cert -``` - -This example creates a new trusted root authority, WFEFarm1. - - -## PARAMETERS - -### -Name -Specifies the name of the trusted root authority to create. - -The value must be a valid name of a trusted root authority; for example, WFEFarm1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Certificate -Specifies the X.509 certificate of the trusted root authority. - -The value must be a name of a valid X.509 certificate; for example, Certificate1. - -```yaml -Type: X509Certificate2 -Parameter Sets: ManualUpdateCertificateParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -Specifies the Uri of the metadata endpoint. - -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedSecurityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedSecurityTokenIssuer.md deleted file mode 100644 index b67f9346dc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedSecurityTokenIssuer.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sptrustedsecuritytokenissuer -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPTrustedSecurityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPTrustedSecurityTokenIssuer - -## SYNOPSIS -Creates a trust between a server to server principal. - - -## SYNTAX - -### ImportCertificateParameterSet -``` -New-SPTrustedSecurityTokenIssuer [-Name] <String> -Certificate <X509Certificate2> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-IsTrustBroker] - [-RegisteredIssuerName <String>] [-WhatIf] [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -New-SPTrustedSecurityTokenIssuer [-Name] <String> -MetadataEndPoint <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-IsTrustBroker] - [-RegisteredIssuerName <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `New-SPTrustedSecurityTokenIssuer` cmdlet to establish a trust between a server to server principal. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------EXAMPLE----------- -``` -New-SPTrustedSecurityTokenIssuer -Name "SPFarmA" -MetadataEndPoint https://mysite/my/_layouts/metadata/test/1/ -isSelfIssuer "false" -``` - -This example creates a new trusted security token named SPFarmA. - - -## PARAMETERS - -### -Name -Specifies the name of the issuer. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Certificate -Specifies the X509Certificate object that represents the public key of the signing certificate of the security token issuer. - -```yaml -Type: X509Certificate2 -Parameter Sets: ImportCertificateParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -Specifies the URI for the metadata endpoint of the issuer. - -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the issuer. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsTrustBroker -Specifies whether the trust is established with a self-issuer partner app (that is, Exchange Server or Lync). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegisteredIssuerName -Specifies the name of the registered token issuer instead of using metadata endpoint. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPTrustedSecurityTokenIssuer](Get-SPTrustedSecurityTokenIssuer.md) - -[Remove-SPTrustedSecurityTokenIssuer](Remove-SPTrustedSecurityTokenIssuer.md) - -[Set-SPTrustedSecurityTokenIssuer](Set-SPTrustedSecurityTokenIssuer.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedServiceTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedServiceTokenIssuer.md deleted file mode 100644 index d4fda71557..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPTrustedServiceTokenIssuer.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-sptrustedservicetokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPTrustedServiceTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPTrustedServiceTokenIssuer - -## SYNOPSIS -Creates a trust with a SharePoint farm. - - -## SYNTAX - -### ImportCertificateParameterSet -``` -New-SPTrustedServiceTokenIssuer [-Name] <String> -Certificate <X509Certificate2> - [-AssignmentCollection <SPAssignmentCollection>] [-Description <String>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -New-SPTrustedServiceTokenIssuer [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Description <String>] [-Confirm] -MetadataEndPoint <Uri> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPTrustedServiceTokenIssuer` cmdlet creates a trust with a SharePoint farm. -If a certificate file is used, it must have only one X509 certificate without private keys, otherwise an exception is raised. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx -New-SPTrustedServiceTokenIssuer -Name "WFEFarm1" -Description "WFE Farm 1" -Certificate $cert -``` - -This example shows how to create a new SharePoint Farm trust using the trust certificate from a file. - - -## PARAMETERS - -### -Name -Specifies the name of the trust. - -The type must be a valid name of a trusted service issuer; for example, WFEFarmTrust1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Certificate -The type must be a name of a valid X.509 certificate; for example, Certificate1. - -Specifies the X.509 certificate object from trusted authentication provider farm. - -```yaml -Type: X509Certificate2 -Parameter Sets: ImportCertificateParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Description -Specifies a description for the trust. - -The type must be a valid string; for example, WFE Farm Trust1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -Specifies the URI for the metadata endpoint of the trusted provider. - -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUsageApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPUsageApplication.md deleted file mode 100644 index 8a8de2cb3a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUsageApplication.md +++ /dev/null @@ -1,240 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spusageapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPUsageApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPUsageApplication - -## SYNOPSIS -Creates a new usage application. - - -## SYNTAX - -``` -New-SPUsageApplication [[-Name] <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] - [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] [-UsageService <SPUsageServicePipeBind>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPUsageApplication` cmdlet creates a new usage application in the local farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE------------------------- -``` -New-SPUsageApplication -Name "Usage Application For Farm ABC" -``` - -This example creates a new usage application for the specified name. - - -## PARAMETERS - -### -Name -Specifies the friendly name of the new usage application. - -The type must be a valid name of a usage application; for example, UsageApplication1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the logging database. -If the logging database does not exist, a logging database is automatically created. - -The type must be a valid name of a SQL Server database; for example, UsageLogDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user specified in DatabaseUserName. -Use this parameter only if SQL Server Authentication is used to access the logging database. - -The type must be a valid password. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the SPServer object where the logging database is created. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; the IP address of a server computer, in the form 208.77.188.166; a valid name of a SQL Server host service (for example, SQLServerHost1); or an instance of a valid SPServer object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user name to use for connecting to the logging database. -Use this parameter only if SQL Server Authentication is used to access the logging database. - -The type must be a valid user name; for example, UserName1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host SQL Server instance for the failover database server. - -The type must be a valid SQL Server instance name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsageService -Filters to return the usage application with the specified parent SPUsageService object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage service (for example, UsageService1); or an instance of a valid SPUsageService object. - -```yaml -Type: SPUsageServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUsageLogFile.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPUsageLogFile.md deleted file mode 100644 index d31cd8ef66..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUsageLogFile.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spusagelogfile -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPUsageLogFile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPUsageLogFile - -## SYNOPSIS -Starts a new usage log file on the current server computer. - - -## SYNTAX - -``` -New-SPUsageLogFile [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPUsageLogFile` cmdlet starts a new usage log file on the current server computer. -The usage data in memory is flushed to the current usage log file before the new log file is created. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE------------------- -``` -New-SPUsageLogFile -``` - -This example terminates the current usage log file and creates a new one. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUser.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPUser.md deleted file mode 100644 index c7f3b1ef18..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUser.md +++ /dev/null @@ -1,244 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spuser -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPUser -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPUser - -## SYNOPSIS -Adds an existing user to a SharePoint site with the designated permissions. - - -## SYNTAX - -``` -New-SPUser [-UserAlias] <String> -Web <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DisplayName <String>] [-Email <String>] [-Group <SPGroupPipeBind>] [-PermissionLevel <String[]>] - [-SiteCollectionAdmin] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPUser` cmdlet adds an existing user to a SharePoint web site with the designated permissions. -This user has the given permissions in all subsites that inherit permissions. -The user account must already exist in the user directory. - -If your environment is in Active Directory mode, the user must already exist in Active Directory Domain Services (AD DS) and only the UserAlias parameter is required; all other fields are pulled from AD DS. -If only an alias is given and the farm is in Active Directory Account Create mode, the Email parameter is also required. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1---------------------- -``` -New-SPUser -UserAlias 'Contoso\Jdow'-DisplayName 'Jane Dow' -Web https://contoso.com -``` - -This example adds a new user named Jane Dow to the Contoso domain. - - -### ------------------EXAMPLE 2---------------------- -``` -Get-SPWeb https://sitename | New-SPUser -UserAlias Contoso\Jdow -``` - -This example adds Contoso\Jdow to all webs in the https://sitename site collection. -Because this site collection uses inherited permissions, only the top-level web site needs to be touched. - - -## PARAMETERS - -### -UserAlias -Specifies the user alias from Active Directory Domain Services (AD DS). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Web -Specifies the URL or GUID of the web on which to create this user. - -The type must be a valid URL, in the form https://server_name, or a GUID, in the form 1234-5678-9876-0987. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -Specifies a string that contains the display name of the user. - -The type must be a valid user name; for example, Joe. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Email -Specifies the email address of the new user. - -The type must be a valid email address, in the form someone@contoso.com. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Group -Specifies the user group to which the new user belongs. - -```yaml -Type: SPGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PermissionLevel -Adds a user to a permission level. - -The type must be a valid permission level for the web application; for example, Full Control, Read, Contribute, or All. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollectionAdmin -Specifies whether to add the user as an administrator to the site collection. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserLicenseMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserLicenseMapping.md deleted file mode 100644 index 98f425a818..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserLicenseMapping.md +++ /dev/null @@ -1,318 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spuserlicensemapping -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPUserLicenseMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPUserLicenseMapping - -## SYNOPSIS -Creates a license mapping object. - - -## SYNTAX - -### TrustIdentity -``` -New-SPUserLicenseMapping -Claim <SPClaim> -License <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -### ClaimsValues -``` -New-SPUserLicenseMapping -ClaimType <String> -License <String> -OriginalIssuer <String> -Value <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-ValueType <String>] - [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -### FormsAuth -``` -New-SPUserLicenseMapping -License <String> -Role <String> -RoleProviderName <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WebApplication <SPWebApplicationPipeBind>] - [-WhatIf] [<CommonParameters>] -``` - -### WindowsAuth -``` -New-SPUserLicenseMapping -License <String> -SecurityGroup <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WebApplication <SPWebApplicationPipeBind>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `New-SPUserLicenseMapping` cmdlet to create a new license mapping object. -This cmdlet must be used first before the `Add-SPUserLicenseMapping` cmdlet can be used. - -The object created by using the `New-SPUserLicenseMapping` cmdlet is stored in memory and is not written to any database in SharePoint Server. -After the object is created you can pipe the result to the `Add-SPUserLicenseMapping` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------- EXAMPLE---------------------------) -``` -$a = New-SPUserLicenseMapping -SecurityGroup EntSecGroup -License Enterprise -$a | Add-SPUserLicenseMapping -``` - -This example creates a license mapping object for the Active Directory secured group named 'EntSecGroup' and then pipes the result to the `Add-SPUserLicenseMapping` cmdlet. - - -## PARAMETERS - -### -Claim -Specifies the claims principal to license. -The value must be an authentic claims principal. - -```yaml -Type: SPClaim -Parameter Sets: TrustIdentity -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClaimType -Specifies the type of the claim. -The value must be an authentic name of a claim type. - -```yaml -Type: String -Parameter Sets: ClaimsValues -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -License -Specifies the name of a supported SharePoint user license. -For the full list of supported licenses on a SharePoint farm, see the `Get-SPUserLicense` cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -OriginalIssuer -Specifies the original issuer of the claim. -The value must be the authentic name of an original issuer. - -```yaml -Type: String -Parameter Sets: ClaimsValues -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Role -Specifies the name of a forms-based role. -The value must be an authentic name of a forms-based role. - -```yaml -Type: String -Parameter Sets: FormsAuth -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoleProviderName -Specifies the name of a role provider. -The value must be an authentic name of a role provider. - -```yaml -Type: String -Parameter Sets: FormsAuth -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecurityGroup -Specifies the name of an AD DS security group. -The value must be a name of an Active Directory security group. - -```yaml -Type: String -Parameter Sets: WindowsAuth -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Value -Specifies the value of the claim. -The value must be an authentic claim value. - -```yaml -Type: String -Parameter Sets: ClaimsValues -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValueType -Specifies the value type of the claim. -The value must be an authentic name of a claim value type. - -```yaml -Type: String -Parameter Sets: ClaimsValues -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, web application name, or web application object instance where the mapping is to be added. -If you omit this parameter, the mapping is applied to the entire farm. - -The type must be an URL in the form http://server_name or http://server_name/sites/sitename, a GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh), a name of a web application (for example, SharePoint - 80), or an instance of a web application object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPUserLicenseMapping](Add-SPUserLicenseMapping.md) - -[Get-SPUserLicenseMapping](Get-SPUserLicenseMapping.md) - -[Remove-SPUserLicenseMapping](Remove-SPUserLicenseMapping.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserSettingsProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserSettingsProvider.md deleted file mode 100644 index f898551c43..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserSettingsProvider.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spusersettingsprovider -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPUserSettingsProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPUserSettingsProvider - -## SYNOPSIS -Adds a new User Settings Provider. - - -## SYNTAX - -``` -New-SPUserSettingsProvider -AssemblyName <String> -DisplayName <String> -Type <String> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPUserSettingsProvider` cmdlet to add a new User Settings Provider to the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------- EXAMPLE--------------------------- -``` -New-SPUserSettingsProvider -DisplayName "My User Settings Provider" -AssemblyName MyProvider.dll -Type MyProvider -``` - -This example adds a user setting provider with a display name of "My User Settings Provider" which uses the MyProvider.dll file. - - -## PARAMETERS - -### -AssemblyName -Specifies the assembly name for the provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -Specifies the display name to use for this provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type name to use for this provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPUserSettingsProvider](Get-SPUserSettingsProvider.md) - -[Remove-SPUserSettingsProvider](Remove-SPUserSettingsProvider.md) - -[Get-SPUserSettingsProviderManager](Get-SPUserSettingsProviderManager.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserSolutionAllowList.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserSolutionAllowList.md deleted file mode 100644 index 3ab8142666..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPUserSolutionAllowList.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spusersolutionallowlist -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPUserSolutionAllowList -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPUserSolutionAllowList - -## SYNOPSIS -Creates a user managed solutions gallery. - - -## SYNTAX - -``` -New-SPUserSolutionAllowList [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] -ListTitle <String> - -Site <SPSitePipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a user managed solutions gallery. - - -## EXAMPLES - -### ----------------------- EXAMPLE--------------------------- -``` -New-SPUserSolutionAllowList -Site https://contoso/sites/site1 -ListTitle "Allow List" -``` -This example creates a user managed solutions gallery named "Allow List" under the root web of the site collection at https://contoso/sites/site1. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ListTitle -Specifies the title of the user solution allow list to create. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Specifies the site collection where the user solution allow list will be created. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioSafeDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioSafeDataProvider.md deleted file mode 100644 index eebcf725c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioSafeDataProvider.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spvisiosafedataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPVisioSafeDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPVisioSafeDataProvider - -## SYNOPSIS -Adds a new data provider to a Visio Services application. - - -## SYNTAX - -``` -New-SPVisioSafeDataProvider -DataProviderId <String> -DataProviderType <Int32> - -VisioServiceApplication <SPVisioServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Description <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPVisioSafeDataProvider` cmdlet adds a new data provider to the list of safe data providers for a Visio Services application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE------------------------ -``` -New-SPVisioSafeDataProvider -VisioServiceApplication "VGS1" -DataProviderID "CustomProvider" -DataProviderType 5 -Description "Custom Data Provider" -``` - -This example creates a new safe data provider for a specified Visio Services application. - - -## PARAMETERS - -### -DataProviderId -Specifies the name of the data provider to create. -The combination of DataProviderID and DataProviderType uniquely identify a data provider for a Visio Services application. -The string that identifies the data provider can be a maximum of 255 alphanumeric characters. - -The type must be a valid string that identifies the data provider; for example, VisioDataProvider1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataProviderType -The type must be a valid identity of a data provider type. - -Specifies the supported type of the data provider to add. -Custom data types are supported; for example, Excel Services. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VisioServiceApplication -Specifies the Visio Services application in which to add the new safe data provider. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the new safe data provider. - -The type must be a string with a maximum of 4096 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioServiceApplication.md deleted file mode 100644 index 6d7228c441..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioServiceApplication.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spvisioserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPVisioServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPVisioServiceApplication - -## SYNOPSIS -Adds a new Visio Services application to a farm. - - -## SYNTAX - -``` -New-SPVisioServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AddToDefaultGroup] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPVisioServiceApplication` cmdlet adds a new Visio Services application to a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------EXAMPLE 1--------------------- -``` -New-SPVisioServiceApplication -Identity 'Visio Graphics Service Application' -ApplicationPool 'SharePoint Web Services Default' -CreateDefaultProxy -``` - -This example creates a new Visio Services application named 'Visio Graphics Service Application' and also creates a service application proxy associated with it. - - -## PARAMETERS - -### -ApplicationPool -Specifies the existing IIS application pool in which to run the Web service for the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AddToDefaultGroup -Specifies that a default proxy is created for the new Visio Services application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the Visio Services application to create. - -The type must be a valid name of a Visio Service application; for example, MyVisioService1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioServiceApplicationProxy.md deleted file mode 100644 index 803f2b4d08..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPVisioServiceApplicationProxy.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spvisioserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPVisioServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPVisioServiceApplicationProxy - -## SYNOPSIS -Adds a new Visio Services application proxy to a farm. - - -## SYNTAX - -``` -New-SPVisioServiceApplicationProxy -ServiceApplication <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPVisioServiceApplicationProxy` cmdlet adds a new Visio Services application proxy to a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE------------------------ -``` -$sa = New-SPVisioServiceApplication -Identity 'Visio Graphics Service Application' -ApplicationPool 'SharePoint Web Services Default' -New-SPVisioServiceApplicationProxy -Identity 'Visio Graphics Service Application Proxy' -ServiceApplication $sa -``` - -This example creates a new Visio Services application proxy connected to a Visio Services application. - - -## PARAMETERS - -### -ServiceApplication -Specifies the Visio Services application that is associated with the application proxy. - -The type must be a valid name of a Visio Services application; for example, MyVisioService1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the Visio Services application proxy to create. - -The type must be a valid name of a Visio Services application; for example, MyVisioService1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWOPIBinding.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWOPIBinding.md deleted file mode 100644 index 0af0929120..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWOPIBinding.md +++ /dev/null @@ -1,260 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spwopibinding -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWOPIBinding -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWOPIBinding - -## SYNOPSIS -Creates a new binding to associate file name extensions or applications with actions on the current SharePoint farm where this cmdlet is run. - - -## SYNTAX - -``` -New-SPWOPIBinding -ServerName <String> [-Action <String>] [-AllowHTTP] [-Application <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Extension <String>] [-FileName <String>] - [-ProgId <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPWOPIBinding` cmdlet associates file name extensions or applications to actions on the current SharePoint farm where this cmdlet is run. -Each binding allows you to use the WOPI application to view or edit files in your SharePoint library. -For example, when a user sees a Word document in a SharePoint document list, the SharePoint list will display the available options to view or edit the document based on the actions that are bound to Word on that SharePoint farm. - -To use a WOPI application, such as a server that runs Office Web Apps Server, for Office Web Apps, you must run this cmdlet on the SharePoint farm before you can use the Office Web Apps. - -If you run `New-SPWOPIBinding` for an application or file name extension where the binding (or association) already exists, the cmdlet will fail. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -New-SPWOPIBinding -ServerName "Server.corp.Contoso.com" -``` - -This example creates bindings for all the applications and file name extensions that the WOPI application supports on the current SharePoint farm where this cmdlet is run. - -### ------------------EXAMPLE 2----------------------- -``` -New-SPWOPIBinding -ServerName "Server.corp.Contoso.com" -Application "Excel" -``` - -This example associates Excel with all the actions that the WOPI application supports for Excel on the current SharePoint farm where this cmdlet is run. - - -## PARAMETERS - -### -ServerName -Specifies the name or fully qualified domain name (FQDN) of the WOPI application (such as a server that runs Office Web Apps Server). - -This can also be an FQDN of a load balanced endpoint for multiple Office Web Apps servers. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Action -Specifies the action to bind. - -For example, "view," "edit," and "embedview." For a list of actions that the WOPI application supports, run `Get-SPWOPIBinding`. -Typically, you will not use this parameter. - -If you specify some actions but not others, some SharePoint features may not work. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowHTTP -Specifies that the cmdlet can use HTTP for discovery of what the WOPI application supports. - -If this is specified as True, the discovery information from the WOPI application will be sent on a nonsecure connection. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Application -Specifies applications to bind. - -Possible applications are as follows: "Word," "Excel," "PowerPoint," or "OneNote." Run `Get-SPWOPIBinding` to get the full list of application the WOPI application supports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Extension -Specifies the file name extensions to bind. - -Run `Get-SPWOPIBinding` to get the list of file name extensions the WOPI application supports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileName -Specifies the path of the xml file that contains the discover information for the WOPI application. - -You can load discovery information from an xml file instead of requesting from the WOPI application directly. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProgId -Specifies the programmatic identifier (ProgID) for an application to bind. - -Run `Get-SPWOPIBinding` to get the list of ProgIDs that the WOPI application supports. - -You may only want to use this parameter to associate an action to an OneNote folder. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[Get-SPWOPIBinding](Get-SPWOPIBinding.md) - -[Set-SPWOPIBinding](Set-SPWOPIBinding.md) - -[Remove-SPWOPIBinding](Remove-SPWOPIBinding.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWOPISuppressionSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWOPISuppressionSetting.md deleted file mode 100644 index 8f1e6a4c5c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWOPISuppressionSetting.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spwopisuppressionsetting -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWOPISuppressionSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWOPISuppressionSetting - -## SYNOPSIS -Disables Office Web Apps for the action, file name extension, or programmatic identifier that you've specified on the current SharePoint farm. - - -## SYNTAX - -``` -New-SPWOPISuppressionSetting [-Action <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Extension <String>] [-ProgId <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPWOPISuppressionSetting` cmdlet turns off Office Web Apps for the action, file name extension, or programmatic identifier (ProgId) that you've specified on the current SharePoint farm. -The cmdlet does this without removing the discovery information or the ability for users to use the SharePoint Share by link feature to send a link to a document and allow the recipient to use Office Web Apps for that document type. -You may have to use this cmdlet if you want to use Excel Services to view Excel workbooks instead of the WOPI application (for example Office Web Apps Server). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPWOPISuppressionSetting -Extension "XLSX" -Action "view" -New-SPWOPISuppressionSetting -Extension "XLS" -Action "view" -``` - -This example turns off the ability of a user to use Office Web Apps to view Excel workbooks that have file name extensions ".xlsx" or ".xls". - - -## PARAMETERS - -### -Action -Specifies the action to suppress for a given extension or programmatic identifier (ProgId). - -For example, "view," "edit," and "embedview." For a full list of actions, run `Get-SPWOPIBinding`. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Extension -Specifies the file name extension to suppress. - -Run `Get-SPWOPIBinding` to get the list of file name extensions the WOPI application supports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProgId -Specifies the programmatic identifier (ProgId) for an application to suppress. - -Run `Get-SPWOPIBinding` to get the list of ProgIds that the WOPI application supports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters`. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[Get-SPWOPISuppressionSetting](Get-SPWOPISuppressionSetting.md) - -[Remove-SPWOPISuppressionSetting](Remove-SPWOPISuppressionSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWeb.md deleted file mode 100644 index 81348d2d57..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWeb.md +++ /dev/null @@ -1,269 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spweb -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWeb - -## SYNOPSIS -Creates a new site in an existing site collection. - - -## SYNTAX - -``` -New-SPWeb [-Url] <String> [-Language <UInt32>] [-Template <SPWebTemplatePipeBind>] [-Name <String>] - [-Description <String>] [-AddToQuickLaunch] [-UniquePermissions] [-AddToTopNav] [-UseParentTopNav] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPWeb` cmdlet creates a new site in the existing site collection specified by the Url parameter. -You can create a site with a specific default language by specifying the Language parameter. -If no language is specified, the site is created with the same language that was specified when the product was installed. -You can create a site from a specific template by specifying the Template parameter. -If no template is specified, the site is created and the template can be provided later or by the first user to log on. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPWeb https://somesite/subweb1 -Template "STS#0" -``` - -This example creates a new subsite by using the Team Site template at the provided URL (https://somesite/subweb1). -The Team Site template is a value referenced as the variable STS#0 for the Template parameter. - - -## PARAMETERS - -### -Url -Specifies the URL where the new site is to be created. -The URL must be inside an existing site collection. -The URL must be a valid URL, in the form https://server_name/site1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Language -Specifies the language template identifier for the new site. -If no language is specified, the site is created with the same language that was specified when the product was installed. - -The type must be a valid language identifier (LCID). - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the Web template for the new site. -The template must already exist. -If no template is specified, no template is applied and a template can be selected later. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the title of the new site. -If no title is specified, the default title is applied. -The default title is configured for each template. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Describes the new site. -If no description is specified, the entry is left blank. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddToQuickLaunch -Adds this site to the Quick Launch. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UniquePermissions -Specifies that this site is to be created with unique permissions. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddToTopNav -Adds this site to the top-level navigation bar. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseParentTopNav -Specifies that the same top-level navigation bar as the parent site is to be used for this site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplication.md deleted file mode 100644 index 6f539c2c64..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplication.md +++ /dev/null @@ -1,460 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spwebapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWebApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWebApplication - -## SYNOPSIS -Creates a new Web application within the local farm. - - -## SYNTAX - -``` -New-SPWebApplication -ApplicationPool <String> -Name <String> - [-AdditionalClaimProvider <SPClaimProviderPipeBind[]>] [-AllowAnonymousAccess] - [-ApplicationPoolAccount <SPProcessAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-AuthenticationMethod <String>] [-AuthenticationProvider <SPAuthenticationProviderPipeBind[]>] [-Confirm] - [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] - [-HostHeader <String>] [-Path <String>] [-Port <UInt32>] [-SecureSocketsLayer] - [-ServiceApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] - [-SignInRedirectProvider <SPTrustedIdentityTokenIssuerPipeBind>] [-SignInRedirectURL <String>] [-Url <String>] - [-UserSettingsProvider <SPUserSettingsProviderPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new Web application specified by the Name parameter. -The user specified by the DatabaseCredentials parameter must be a member of the dbcreator fixed server role on the database server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -New-SPWebApplication -Name "Contoso Internet Site" -Port 80 -HostHeader sharepoint.contoso.com -URL "http://www.contoso.com/" -ApplicationPool "ContosoAppPool" -ApplicationPoolAccount (Get-SPManagedAccount "DOMAIN\wa") -``` - -This example creates a new Web application by using an internal host header of sharepoint.contoso.com and a public URL of http://www.contoso.com. - -### ------------------EXAMPLE 2----------------------- -``` -New-SPWebApplication -Name "Contoso Internet Site" -Port 443 -SecureSocketsLayer -HostHeader sharepoint.contoso.com -URL "https://www.contoso.com/" -ApplicationPool "ContosoAppPool" -ApplicationPoolAccount (Get-SPManagedAccount "DOMAIN\wa") -``` - -This example creates a new SSL enabled Web application by using an internal host header of sharepoint.contoso.com and a public URL of https://www.contoso.com. - -### ------------------EXAMPLE 3----------------------- -``` -$ap = New-SPAuthenticationProvider -New-SPWebApplication -Name "Contoso Internet Site" -URL "https://www.contoso.com/" -Port 443 --ApplicationPool "ContosoAppPool" --ApplicationPoolAccount (Get-SPManagedAccount "DOMAIN\wa") --AuthenticationProvider $ap -SecureSocketsLayer -``` - -Creates a Windows Claims web application at the URL https://www.contoso.com using the domain account domain\wa. - -## PARAMETERS - -### -ApplicationPool -Specifies the name of an application pool to use; for example, SharePoint - 1213. -If an application pool with the name provided does not exist, the ApplicationPoolAccount parameter must be provided and a new application pool will be created. -If no value is specified, the default application pool will be used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new Web application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AdditionalClaimProvider -Adds a specific claim provider to the defined Web application. - -```yaml -Type: SPClaimProviderPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowAnonymousAccess -Allows anonymous access to the Web application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPoolAccount -Specifies the user account that this application pool will run as. -Use the `Get-SPIisWebServicApplicationPool` cmdlet to use a system account. - -```yaml -Type: SPProcessAccountPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationMethod -Uses Kerberos or NTLM to specify the authentication method. -If no value is specified, the default NTLM is applied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuthenticationProvider -Specifies the authentication provider or providers that apply to a Web application. - -```yaml -Type: SPAuthenticationProviderPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the Windows PowerShell Credential object for the database user account. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the initial content database for the new Web application. - -The type must be a valid database name; for example, ContentDB1. -If no value is specified, a value in the format WSS_Content_\<GUID\> is auto-generated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the database server name. -The type must be a valid database server name, in the form SQL1; where named instances are used, the format can appear as server\server. -The default SQL server instance is used if a value is not provided. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostHeader -Specifies a valid URL assigned to the Web application that must correlate to the alternate access mapping configuration, in the form server_name. - -When the HostHeader parameter is present, the value of this field is the internal URL for the Web application. -The Url parameter is used to specify the public URL.If no value is specified, the value is left blank. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Specifies the physical directory for the new Web application in the virtual directories folder. -The type is a valid path, in the form C:\Inetpub\wwwroot\MyWebApplication. -If no value is specified, the value %wwwroot%\wss\VirtualDirectories\\\<portnumber\> is applied. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Port -Specifies the port on which this Web application can be accessed. -This can be any valid port number. -If no port is specified, a nonconflicting port number is automatically generated. - -If you specify a port number that has already been assigned, IIS does not start the new site until you change either the port number of the new site or the port number of the old site. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureSocketsLayer -Enables Secure Sockets Layer (SSL) encryption for this Web application. -If you choose to use SSL, you must add the certificate on each server by using the IIS administration tools. -Until this is done, the Web application will be inaccessible from this IIS Web site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplicationProxyGroup -Specifies a custom service application proxy group for the Web application to use. -The Web application will use the proxies in this proxy group to connect to service applications. -If this parameter is not specified, the default proxy group for the farm is used. - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: (All) -Aliases: ProxyGroup -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInRedirectProvider -Sets the sign-in redirect URL to point to the URL that is defined in the specified authentication provider. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInRedirectURL -Specifies the sign-in redirect URL for the Web application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Specifies the load-balanced URL for the Web application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserSettingsProvider -Provides access to external user settings provider. - -```yaml -Type: SPUserSettingsProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplicationAppDomain.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplicationAppDomain.md deleted file mode 100644 index 5d05621ecf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplicationAppDomain.md +++ /dev/null @@ -1,225 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spwebapplicationappdomain -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWebApplicationAppDomain -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWebApplicationAppDomain - -## SYNOPSIS - -Creates an AppDomain entry. - - -## SYNTAX - -``` -New-SPWebApplicationAppDomain [-AppDomain] <String> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Port <Int32>] [-SecureSocketsLayer] [-WhatIf] - [-Zone <SPUrlZone>] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the New-SPWebApplicationAppDomain cmdlet to create an AppDomain entry. If you specify a port, the cmdlet adds a port binding to the Internet Information Services (IIS) site corresponding to the Web Application/Zone combination. - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- - -```powershell -New-SPWebApplicationAppDomain -AppDomain contosoapps.com -WebApplication https://www.contoso.com -``` - -Creates a new app domain for apps for SharePoint for the specified web application in the default zone. - -### ------------------EXAMPLE 2----------------------- - -```powershell -New-SPWebApplicationAppDomain -AppDomain contosoapps.com -WebApplication https://www.contoso.com -Zone Internet -Port 10000 -``` - -Creates a new app domain for apps for SharePoint for the specified web application in the internet zone at port 10000. - -## PARAMETERS - -### -AppDomain - -Specifies the URI of the app domain. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication - -Specifies the GUID, URI, or name of the web application for which the app domain is being configured. - - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm - -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Port - -Specifies the IIS port number to which the app domain will be assigned. If no value is specified, the same port used by the web application for the zone is applied. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureSocketsLayer - -Specifies that the app domain will use Secured Sockets Layer (SSL) security. If no value is specified, no SSL security will be used. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf - -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Zone - -Specifies the security zone to which the app domain will be assigned. - -* Default - -* Intranet - -* Internet - -* Extranet - -* Custom - -If no value is specified, Default is applied. - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String - -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPWebApplicationAppDomain](Get-SPWebApplicationAppDomain.md) - -[Remove-SPWebApplicationAppDomain](Remove-SPWebApplicationAppDomain.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplicationExtension.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplicationExtension.md deleted file mode 100644 index 5a90f4b4ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWebApplicationExtension.md +++ /dev/null @@ -1,353 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spwebapplicationextension -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWebApplicationExtension -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWebApplicationExtension - -## SYNOPSIS -Creates a new zone instance for the Web application. - - -## SYNTAX - -``` -New-SPWebApplicationExtension [-Identity] <SPWebApplicationPipeBind> -Name <String> -Zone <SPUrlZone> - [-AdditionalClaimProvider <SPClaimProviderPipeBind[]>] [-AllowAnonymousAccess] - [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationMethod <String>] - [-AuthenticationProvider <SPAuthenticationProviderPipeBind[]>] [-Confirm] [-HostHeader <String>] - [-Path <String>] [-Port <UInt32>] [-SecureSocketsLayer] - [-SignInRedirectProvider <SPTrustedIdentityTokenIssuerPipeBind>] [-SignInRedirectURL <String>] [-Url <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPWebApplicationExtension` cmdlet creates a new zone instance for the Web application. -This is also known as extending a Web application and allows alternate permissions to be configured for the same content that is available in the existing Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Get-SPWebApplication http://sitename | New-SPWebApplicationExtension -Name "ExtranetSite" -SecureSocketsLayer -Zone "Extranet" -URL "https://extranet.sitename.com/" -``` - -This example extends the given Web application at http://sitename to the Extranet zone for SSL use. - - -## PARAMETERS - -### -Identity -Specifies the Web application to extend. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new IIS Web site in the Web application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Zone -Specifies one of the five zones with which the internal URL of this new extension is to be associated. -This zone cannot already be in use. - -The type must be any one of the following values: Default, Intranet, Internet, Extranet, or Custom - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdditionalClaimProvider -Adds a specific claim provider to the defined Web application. - -```yaml -Type: SPClaimProviderPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowAnonymousAccess -Allows anonymous access to the Web application zone. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationMethod -Uses Kerberos or NTLM to specify the authentication method. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuthenticationProvider -Specifies the authentication provider(s) that applies to a Web apllication. - -```yaml -Type: SPAuthenticationProviderPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostHeader -Specifies a valid URL assigned to the Web application by that must correlate to the alternate access mapping configuration, in the form http://server_name. - -When the HostHeader parameter is present, the value of this field is the internal URL for the Web application. -The Url parameter is used to specify the public URL. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Specifies the physical directory for the new Web site (in the virtual directories folder). -The type is a valid path, in the form C:\Inetpub\wwwroot\MyWebApplication. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Port -Specifies the application port. -Can be any valid port number. - -If no port is specified, a nonconflicting port number is automatically generated. - -If you specify a port number that is already assigned, IIS does not start the new site until you change either the port number of the new site or the port number of the old site. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureSocketsLayer -Enables Secure Sockets Layer (SSL) encryption for this Web application. -If you use SSL, you must add the certificate on each server by using the IIS administration tools. -Until this is done, the Web application is inaccessible from this IIS Web site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInRedirectProvider -Sets the sign-in redirect URL to point to the URL that is defined in the specified authentication provider. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInRedirectURL -Specifies the sign-in redirect URL for the Web application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Specifies the load-balanced URL for the Web application zone. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWordConversionServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWordConversionServiceApplication.md deleted file mode 100644 index b3142886e3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWordConversionServiceApplication.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -external help file: Microsoft.Office.Word.Server.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spwordconversionserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWordConversionServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWordConversionServiceApplication - -## SYNOPSIS -Creates a new instance of a Word Automation Services application on the farm. - - -## SYNTAX - -``` -New-SPWordConversionServiceApplication [-Name] <String> - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DatabaseCredential <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-Default] - [-PartitionMode] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `New-SPWordConversionServiceApplication` cmdlet creates a new instance of a Word Automation Services application on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPWordConversionServiceApplication -Name 'Word Conversion Services' -ApplicationPool 'SharePoint Web Services Default' -DatabaseName 'Word' -``` - -This example creates a new Word Automation Services application named Word Conversion Services in an existing application pool named SharePoint Web Services Default. - - -## PARAMETERS - -### -Name -Specifies the name of the new Word Automation Services application. - -The type must be a valid name of a Word Automation Services application; for example, WordSvcApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing IIS-managed application pool in which this instance of Word Automation Services runs. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredential -Specifies the credentials to use for connecting to the database for the Word Automation Services application. -Use this parameter only if SQL Server Authentication is used to access the service application database. - -When the DatabaseCredential parameter is specified, the DatabaseName and DatabaseServer parameters are required. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database to create for the new Word Automation Services application. - -The type must be a valid SQL database name; for example, MetadataDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the Word Automation Services database. - -The type must be a valid SQL database server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Default -Specifies that the service application proxy is added to the farm's default proxy group for this Web application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that this service behaves uniquely on a partitioned set of site collections. -This property cannot be changed after the application is provisioned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkManagementServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkManagementServiceApplication.md deleted file mode 100644 index 1485d0a55d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkManagementServiceApplication.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Office.Server.WorkManagement.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spworkmanagementserviceapplication -applicable: SharePoint Server 2013 -title: New-SPWorkManagementServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWorkManagementServiceApplication - -## SYNOPSIS -Creates a new Work Management Service application. - - -## SYNTAX - -``` -New-SPWorkManagementServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> -Name <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Proxy] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPWorkManagementServiceApplication` cmdlet to create a new Work Management Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -Note: This functionality has been removed from SharePoint Server 2016, SharePoint Server 2019, but the cmdlet is still present in the product. - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPWorkManagementServiceApplication -Name 'Work Management Service Application' -ApplicationPool 'SharePoint Web Services Default' -``` - -This example creates a new Work Management Service Application using the Application Pool named SharePoint Web Services Default. - - -## PARAMETERS - -### -ApplicationPool -Specifies the name of an application pool to use; for example, SharePoint - 1213. -If no value is specified, the default application pool is used. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the Work Management Service application to be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. - -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Proxy -Specifies whether to add the Work Management Service application to the proxy group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPWorkManagementServiceApplicationProxy](New-SPWorkManagementServiceApplicationProxy.md) - -[Set-SPWorkManagementServiceApplication](Set-SPWorkManagementServiceApplication.md) - -[Set-SPWorkManagementServiceApplicationProxy](Set-SPWorkManagementServiceApplicationProxy.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkManagementServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkManagementServiceApplicationProxy.md deleted file mode 100644 index 2bb60d09fe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkManagementServiceApplicationProxy.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -external help file: Microsoft.Office.Server.WorkManagement.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spworkmanagementserviceapplicationproxy -applicable: SharePoint Server 2013 -title: New-SPWorkManagementServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWorkManagementServiceApplicationProxy - -## SYNOPSIS -Creates a new Work Management Service application proxy. - - -## SYNTAX - -``` -New-SPWorkManagementServiceApplicationProxy -Name <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DefaultProxyGroup] [-ServiceApplication <SPWorkManagementServiceCmdletPipeBind>] [-Uri <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `New-SPWorkManagementServiceApplicationProxy` cmdlet to create a new Work Management Service application proxy object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -Note: This functionality has been removed from SharePoint Server 2016, SharePoint Server 2019, but the cmdlet is still present in the product. - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$sa = New-SPWorkManagementServiceApplication -Name 'Work Management Service Application' -ApplicationPool 'SharePoint Web Services Default' -New-SPWorkManagementServiceApplicationProxy -name 'Work Management Service Application Proxy' -ServiceApplication $sa -``` - -This example creates a new SPWorkManagementServiceApplicationProxy called Work Management Service Application Proxy mapped to the "Work Management Service Application" Service Application. - - -## PARAMETERS - -### -Name -Specifies the display name for the new Work Management Service application proxy. -The name that you use must be a unique name of a Work Management Service application proxy in the farm. -The maximum length is 128 characters. - -The value must be a name of a valid Work Management Service application proxy; for example, WorkMgmtSvcProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the Work Management Service application proxy be added to the default proxy group for the local farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the local Work Management Service application that is associated with the new proxy. - -The value must be in one of the following forms: - ---A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh - ---A valid name of a Work Management Service application (for example, WorkManServ1) - ---An instance of a valid SPServiceApplication object - -```yaml -Type: SPWorkManagementServiceCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Uri -Specifies the URI of a remote Work Management service application to connect to. - -To specify the Work Management service application that this proxy is connecting to, you must set only the URI parameter or only the ServiceApplication parameter. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPWorkManagementServiceApplication](New-SPWorkManagementServiceApplication.md) - -[Set-SPWorkManagementServiceApplication](Set-SPWorkManagementServiceApplication.md) - -[Set-SPWorkManagementServiceApplicationProxy](Set-SPWorkManagementServiceApplicationProxy.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkflowServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkflowServiceApplicationProxy.md deleted file mode 100644 index e9af112a76..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/New-SPWorkflowServiceApplicationProxy.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.WorkflowServices.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/new-spworkflowserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: New-SPWorkflowServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# New-SPWorkflowServiceApplicationProxy - -## SYNOPSIS -Creates a proxy to connect to Workflow Manager. - - -## SYNTAX - -``` -New-SPWorkflowServiceApplicationProxy [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-PartitionMode] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a proxy to connect to Workflow Manager. - -Note: Consider using the cmdlet `Register-SPWorkflowService` instead which binds a Workflow Manager farm and creates the Workflow Service Proxy. - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -New-SPWorkflowServiceApplicationProxy -``` - -Creates a Workflow Service Application Proxy. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies that the service application restrict data by subscription. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Pause-SPProjectWebInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Pause-SPProjectWebInstance.md deleted file mode 100644 index cfced1b385..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Pause-SPProjectWebInstance.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/pause-spprojectwebinstance -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Pause-SPProjectWebInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Pause-SPProjectWebInstance - -## SYNOPSIS -Switches the specified instance of Project Web App to read-only, preventing any changes from being made through the Project Server PSI or CSOM. - - -## SYNTAX - -``` -Pause-SPProjectWebInstance [-Identity] <ProjectInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Switches the specified instance of Project Web App to read-only, preventing any changes from being made through the Project Server Interface (PSI) or Client Server Object Model (CSOM). While in this state the database is not actually read-only and the Queue service can still write to the database, but it will not pick up any new jobs to process. This cmdlet is used to allow the queue to empty out before an administrator switches the database to read-only. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Project Application Services'} -$instance = Get-SPProjectWebInstance -ServiceApplication $sa -Pause-SPProjectWebInstance -Identity $instance -``` - -Pauses the Project Web Server Instance in the Project Web Application Service Application. - -## PARAMETERS - -### -Identity -Specifies the instance of Project Web App to be switched to read-only mode. -It can be the unique id of the instance, the URL of the Project Web App site, the site collection object that contains the Project Web App site (an SPSite), or the Project Web App instance object itself (a PSSite). - -```yaml -Type: ProjectInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Resume-SPProjectWebInstance](Resume-SPProjectWebInstance.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Publish-SPServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Publish-SPServiceApplication.md deleted file mode 100644 index 22e01c7b0f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Publish-SPServiceApplication.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/publish-spserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Publish-SPServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Publish-SPServiceApplication - -## SYNOPSIS -Shares the specified local service application outside the farm. - - -## SYNTAX - -``` -Publish-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-InfoLink <Uri>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Publish-SPServiceApplication` cmdlet publishes the local service application, specified by the Identity parameter, outside the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Publish-SPServiceApplication 053c34be-d251-488c-8e94-644eae94da26 -Description "Connect to this TestServiceApplcation of you want to use FeatureA in your farm" -InfoLink https://testurl -``` - -This example publishes a service application to another farm. - -The service application GUID is unique to every farm. -You can run the `Get-SPServiceApplication` cmdlet to see the GUID of the service applications and then use the result from the `Get-SPServiceApplication` cmdlet for other SPServiceApplication cmdlets; for example, `Grant-SPServiceApplication`. - - -## PARAMETERS - -### -Identity -Specifies the GUID of the service application to share outside the farm. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Describes the service application to share outside the farm. -If no value is specified, the value is left blank. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InfoLink -Specifies the link to more information about the service application to share outside the farm. -If no link is specified, no link is made available. - -The type must be a valid URL, in the form https://server_name/Site_Name/page_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Receive-SPServiceApplicationConnectionInfo.md b/sharepoint/sharepoint-ps/sharepoint-server/Receive-SPServiceApplicationConnectionInfo.md deleted file mode 100644 index 16692694c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Receive-SPServiceApplicationConnectionInfo.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.SharePoint.TopologyService-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/receive-spserviceapplicationconnectioninfo -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Receive-SPServiceApplicationConnectionInfo -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Receive-SPServiceApplicationConnectionInfo - -## SYNOPSIS -Configures this farm to receive service information from another farm. - - -## SYNTAX - -``` -Receive-SPServiceApplicationConnectionInfo [-FarmUrl] <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [-Filter <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Receive-SPServiceApplicationConnectionInfo` cmdlet retrieves the list of service applications published by another farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Receive-SPServiceApplicationConnectionInfo -FarmUrl https://FarmB/topology/topology.svc -``` - -This example retreives a list of service applications published by a given farm. - -The FarmURL parameter can be obtained by the `Get-SPTopologyServiceApplication` cmdlet. - - -## PARAMETERS - -### -FarmUrl -Specifies the URL of the farm from which to receive service application information. - -The type must be a valid URL, in the form https://site_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Filter -Specifies a filter to use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Register-SPAppPrincipal.md b/sharepoint/sharepoint-ps/sharepoint-server/Register-SPAppPrincipal.md deleted file mode 100644 index 0fea222b65..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Register-SPAppPrincipal.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/register-spappprincipal -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Register-SPAppPrincipal -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Register-SPAppPrincipal - -## SYNOPSIS -Lets an on-premises administrator register an app principal. - -## SYNTAX - -``` -Register-SPAppPrincipal -DisplayName <String> -NameIdentifier <String> -Site <SPWebPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Register-SPAppPrincipal` cmdlet to let an on-premises farm administrator to register an app principal management service. - - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251831(https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$site = Get-SPSite "https://<urlofsite>" -Register-SPAppPrincipal -site $site.RootWeb -NameIdentifier "00000003-0000-0ff1-ce00-000000000000@f686d426-8d16-42db-81b7-cb578e110ccd" -DisplayName "Contoso" -``` - -This example registers the app principal named Contoso. - - -## PARAMETERS - -### -DisplayName -Specifies the friendly name to use for the app principal that is being registered. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NameIdentifier -Specifies the app principal's name identifier that needs to be added to the app management service. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -{{Fill Site Description}} - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppPrincipal](Get-SPAppPrincipal.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Register-SPWorkflowService.md b/sharepoint/sharepoint-ps/sharepoint-server/Register-SPWorkflowService.md deleted file mode 100644 index d4cbe0a5c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Register-SPWorkflowService.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: Microsoft.SharePoint.WorkflowServices.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/register-spworkflowservice -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Register-SPWorkflowService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Register-SPWorkflowService - -## SYNOPSIS -Registers a Workflow Manager farm with the SharePoint farm. - - -## SYNTAX - -``` -Register-SPWorkflowService [-AllowOAuthHttp] [-AssignmentCollection <SPAssignmentCollection>] [-Force] - [-PartitionMode] -SPSite <SPSitePipeBind> [-ScopeName <String>] -WorkflowHostUri <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet registers a Workflow Manager farm with the SharePoint farm in order to allow users to leverage SharePoint 2013 workflows. - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Register-SPWorkflowService -SPSite https://site_name -WorkflowHostUri https://workflow.contoso.com:12290 -ScopeName SharePoint -``` -Registers the Workflow Manager farm located at https://workflow.contoso.com:12290 with the SharePoint farm using https://site_name as a reference. A custom Scope named 'SharePoint' is used. - -## PARAMETERS - -### -AllowOAuthHttp -Allows connecting to Workflow Manager using HTTP rather than HTTPS. This is not recommended for security. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Force -Forces the registration, even if previously registered. Will overwrite the existing Scope. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionMode -Specifies to use a SharePoint multi-tenancy features when registering Workflow Manager. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SPSite -The Site Collection used as a reference to register Workflow Manager with the SharePoint farm. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScopeName -The name of the scope in Workflow Manager to use. if not specified, the default Scope will be used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkflowHostUri -The URI on which the Workflow Manager is hosted. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-DatabaseFromAvailabilityGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-DatabaseFromAvailabilityGroup.md deleted file mode 100644 index a86bba0c90..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-DatabaseFromAvailabilityGroup.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-databasefromavailabilitygroup -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-DatabaseFromAvailabilityGroup -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-DatabaseFromAvailabilityGroup - -## SYNOPSIS -Removes one or more SharePoint databases from an availability group in SQL Server. - - -## SYNTAX - -### Default -``` -Remove-DatabaseFromAvailabilityGroup [-AGName] <String> [-AssignmentCollection <SPAssignmentCollection>] - -DatabaseName <String> [-Force] [-KeepSecondaryData] [<CommonParameters>] -``` - -### AllDatabases -``` -Remove-DatabaseFromAvailabilityGroup [-AGName] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Force] [-KeepSecondaryData] [-ProcessAllDatabases] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [https://msdn.microsoft.com/library/dd878348(VS.85).aspx](https://msdn.microsoft.com/library/dd878348(VS.85).aspx). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-DatabaseFromAvailabilityGroup -AGName MyAvailabilityGroup -DatabaseName WSS_Content -``` - -This example removes the availability group named "MyAvailabilityGroup" from the WSS_Content database. - - -## PARAMETERS - -### -AGName -The name of the availability group from which the databases are being removed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseName -The name of the database to be removed from the availability group. - -NOTE: This parameter should not be used in conjunction with the ProcessAllDatabases parameter. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces a remove from the group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepSecondaryData -Specifies that copies of the databases on the replicas in the availability group will not be deleted. Otherwise, those database copies will be dropped. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProcessAllDatabases -Removes all databases from the current SharePoint farm into the availability group. - -```yaml -Type: SwitchParameter -Parameter Sets: AllDatabases -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchContentCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchContentCollection.md deleted file mode 100644 index fad32f49cd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchContentCollection.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchcontentcollection -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchContentCollection ---- - -# Remove-FASTSearchContentCollection - -## SYNOPSIS -Deletes a Microsoft FAST Search Server 2010 for SharePoint content collection. - -## SYNTAX - -``` -Remove-FASTSearchContentCollection [-Name] <String> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a FAST Search Server 2010 for SharePoint content collection. -All items in the collection will be deleted. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchContentCollection -Name newscollection -Force -``` - -This example removes the content collection named "newscollection" without asking the user to confirm the operation. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchContentCollection -Name newscollection -WhatIf -``` - -This example describes what would happen if you executed the Remove-FASTSearchContentCollection cmdlet. - -## PARAMETERS - -### -Name -The name of the content collection to delete. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. - -If Confirm is false (-Confirm:$false), you will not be prompted. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is equal to or greater than the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings so the user is not asked to confirm the operation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-FASTSearchContentCollection](Clear-FASTSearchContentCollection.md) - -[New-FASTSearchContentCollection](New-FASTSearchContentCollection.md) - -[Get-FASTSearchContentCollection](Get-FASTSearchContentCollection.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCategory.md deleted file mode 100644 index 99c90a4cb2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCategory.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchmetadatacategory -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchMetadataCategory ---- - -# Remove-FASTSearchMetadataCategory - -## SYNOPSIS -Removes a crawled property category from the installation. - -## SYNTAX - -### Name -``` -Remove-FASTSearchMetadataCategory [-Name] <String> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -### Category -``` -Remove-FASTSearchMetadataCategory -Category <Category> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a crawled property category from your installation. -The cmdlet takes either the name of the category (Name parameter) or a category object (Category parameter). - -All crawled properties mapped to this category are also removed. -To avoid deleting crawled properties belonging to a category that you are about to remove, first map all crawled properties that you wish to save to a different property set using the Set-FASTSearchMetadataCrawledProperty cmdlet. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchMetadataCategory -name Sharepoint -``` - -This example deletes the category named "Sharepoint". -Confirmation of the operation is requested. -All crawled properties mapped to the "SharePoint" category are also removed. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$category = Get-FASTSearchMetadataCategory -name Office -Remove-FASTSearchMetadataCategory -category $category -force -``` - -This example deletes a crawled property category (stored as $category). -Since Force is specified, confirmation of the operation is not required. - -## PARAMETERS - -### -Name -The name of the category to delete. - -```yaml -Type: String -Parameter Sets: Name -Aliases: CategoryName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Category -A category object to be deleted. - -```yaml -Type: Category -Parameter Sets: Category -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. - -If Confirm is false (-Confirm $false), confirmation prompting is not used. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is equal to or greater than the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings, so that confirmation of the operation is not required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataCategory](Get-FASTSearchMetadataCategory.md) - -[Set-FASTSearchMetadataCategory](Set-FASTSearchMetadataCategory.md) - -[New-FASTSearchMetadataCategory](New-FASTSearchMetadataCategory.md) - -[Set-FASTSearchMetadataCrawledProperty](Set-FASTSearchMetadataCrawledProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCrawledPropertyMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCrawledPropertyMapping.md deleted file mode 100644 index 1718ecee4b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCrawledPropertyMapping.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchmetadatacrawledpropertymapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchMetadataCrawledPropertyMapping ---- - -# Remove-FASTSearchMetadataCrawledPropertyMapping - -## SYNOPSIS -Removes a crawled-property-to-managed-property mapping. - -## SYNTAX - -``` -Remove-FASTSearchMetadataCrawledPropertyMapping -CrawledProperty <CrawledProperty> - -ManagedProperty <ManagedProperty> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes the mapping of a crawled property to a managed property. -Both the managed property and the crawled property still exist after the mapping is removed. - -The cmdlet parameters are both objects, and must be retrieved separately. - -The content must be recrawled/re-fed for the search index to reflect that the mapping was removed. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -$title = Get-FASTSearchMetadataManagedProperty -name title -$crawledproperties = $title.GetCrawledPropertyMappings() -$crawledproperties # To List the output before the removal -Remove-FASTSearchMetadataCrawledPropertyMapping -managedproperty $title -crawledproperty $crawledproperties[4] -$crawledproperties # To list the output after the removal -``` - -This example removes the mapping of the crawled property "sitemap.title" to the managed property "title". - -This example calls the GetCrawledPropertyMappings() method call exposed by the managed property, but you could also find the crawled property by using Get-FASTSearchMetadataCrawledProperty. -The return value from GetCrawledPropertyMappings() is an array of crawled properties, of which the last is the "sitemap.title" crawled property mapping. -The last of the crawled properties (array index 4) has the mapping removed from it by calling Remove-FASTSearchMetadataCrawledPropertyMapping. - -## PARAMETERS - -### -CrawledProperty -The crawled property which is having a mapping removed. -The object can be retrieved by using Get-FASTSearchMetadataCrawledProperty, or by using the GetCrawledPropertyMappings() method call on a managed property object. - -```yaml -Type: CrawledProperty -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -The managed property object which is having a mapping removed. -The object can be retrieved by using the Get-FASTSearchMetadataManagedPropertycmdlet. - -```yaml -Type: ManagedProperty -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. -If Confirm is false (-Confirm:$false), confirmation prompting is not used. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is equal to or greater than the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings, so that confirmation of the operation is not required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataCrawledPropertyMapping](Get-FASTSearchMetadataCrawledPropertyMapping.md) - -[New-FASTSearchMetadataCrawledPropertyMapping](New-FASTSearchMetadataCrawledPropertyMapping.md) - -[Set-FASTSearchMetadataCrawledPropertyMapping](Set-FASTSearchMetadataCrawledPropertyMapping.md) - -[Get-FASTSearchMetadataCrawledProperty](Get-FASTSearchMetadataCrawledProperty.md) - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataFullTextIndex.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataFullTextIndex.md deleted file mode 100644 index e77a0e5d80..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataFullTextIndex.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchmetadatafulltextindex -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchMetadataFullTextIndex ---- - -# Remove-FASTSearchMetadataFullTextIndex - -## SYNOPSIS -Removes a full text index from the Microsoft FAST Search Server 2010 for SharePoint system. - -## SYNTAX - -### FullTextIndex -``` -Remove-FASTSearchMetadataFullTextIndex -FullTextIndex <FullTextIndex> [-Confirm] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -### Name -``` -Remove-FASTSearchMetadataFullTextIndex -Name <String> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes a full text index. -The content of the index is removed and is no longer searchable. -The managed properties mapped to the full text index are still available and can be mapped to other or new full text indexes. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchMetadataFullTextIndex -name secondarycontent -``` - -This example removes the full text index named "secondarycontent" from the FAST Search Server 2010 for SharePoint system. -The cmdlet asks for confirmation as long as neither the Force parameter is used or the $ConfirmPreference environment is set to a higher value than HIGH. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$index=Get-FASTSearchMetadataFullTextIndex -name secondarycontent -Remove-FASTSearchMetadataFullTextIndex -FullTextIndex $index -force -``` - -This example removes the full text index represented by the $index variable. -Since the Force parameter is specified, confirmation of the index removal is not used. - -## PARAMETERS - -### -FullTextIndex -A full text index object representing the full text index to remove. - -```yaml -Type: FullTextIndex -Parameter Sets: FullTextIndex -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Name -The name of the full text index to remove. - -```yaml -Type: String -Parameter Sets: Name -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. -If Confirm is false (-Confirm:$false), confirmation prompting is not used. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is equal to or greater than the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings, so that confirmation of the operation is not required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataFullTextIndex](New-FASTSearchMetadataFullTextIndex.md) - -[Set-FASTSearchMetadataFullTextIndex](Set-FASTSearchMetadataFullTextIndex.md) - -[Get-FASTSearchMetadataFullTextIndex](Get-FASTSearchMetadataFullTextIndex.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataFullTextIndexMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataFullTextIndexMapping.md deleted file mode 100644 index 5c0f2a0dae..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataFullTextIndexMapping.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchmetadatafulltextindexmapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchMetadataFullTextIndexMapping ---- - -# Remove-FASTSearchMetadataFullTextIndexMapping - -## SYNOPSIS -Removes a managed-property-to-full-text-index mapping. - -## SYNTAX - -``` -Remove-FASTSearchMetadataFullTextIndexMapping [-Mapping] <FullTextIndexMapping> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes the mapping of a managed property to a full text index. -The managed properties are not affected, and can still be mapped to other full text indexes. - -The content must be recrawled/re-fed to reflect that managed properties have been removed from full text indexes. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -$fulltextindex = Get-FASTSearchMetadataFullTextIndex -Name content -$managedproperty = Get-FASTSearchMetadataManagedProperty -Name CreatedBy -$fulltextindexmapping = Get-FASTSearchMetadataFullTextIndexMapping -ManagedProperty $managedproperty -FullTextIndex $fulltextindex -Remove-FASTSearchMetadataFullTextIndexMapping -mapping $fulltextindexmapping -``` - -This example removes the mapping of the managed property "CreatedBy" from the full text index "content". -Since the cmdlet takes an object of the mapping, the example first retrieves the mapping using Get-FASTSearchMetadataFullTextIndexMapping. - -## PARAMETERS - -### -Mapping -An object representing the full text index mapping to be removed. - -```yaml -Type: FullTextIndexMapping -Parameter Sets: (All) -Aliases: FullTextIndexMapping, M -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataFullTextIndexMapping](New-FASTSearchMetadataFullTextIndexMapping.md) - -[Set-FASTSearchMetadataFullTextIndexMapping](Set-FASTSearchMetadataFullTextIndexMapping.md) - -[Get-FASTSearchMetadataFullTextIndexMapping](Get-FASTSearchMetadataFullTextIndexMapping.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataManagedProperty.md deleted file mode 100644 index 79ee7e737c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataManagedProperty.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchmetadatamanagedproperty -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchMetadataManagedProperty ---- - -# Remove-FASTSearchMetadataManagedProperty - -## SYNOPSIS -Removes a managed property from the Microsoft FAST Search Server 2010 for SharePoint system. - -## SYNTAX - -### Name -``` -Remove-FASTSearchMetadataManagedProperty [-Name] <String> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -### ManagedProperty -``` -Remove-FASTSearchMetadataManagedProperty -ManagedProperty <ManagedProperty> [-Confirm] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This command removes a managed property and its content from the FAST Search Server 2010 for SharePoint system. -If the managed property is mapped into any full text indexes, the mapping is also removed. -If there are any crawled property mappings to this managed property, those mappings are also removed. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchMetadataManagedProperty -Name title -``` - -This example removes the managed property named "title" from the system. -It will ask for confirmation before going through with the removal unless Force is specified. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -$createdby = Get-FASTSearchMetadataManagedProperty -name CreatedBy -Remove-FASTSearchMetadataManagedProperty -ManagedProperty $createdby -Force -``` - -This example removes the managed property represented by the object $managedproperty. -The object is retrieved by calling Get-FASTSearchMetaDataManagedProperty, but any other call that returns a ManagedPropertyImpl object is acceptable. - -No confirmation is required, since the Force parameter is specified. - -## PARAMETERS - -### -Name -The name of the managed property to remove. - -```yaml -Type: String -Parameter Sets: Name -Aliases: ManagedPropertyName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ManagedProperty -An object that represents the managed property to remove. - -```yaml -Type: ManagedProperty -Parameter Sets: ManagedProperty -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. -If Confirm is false (-Confirm:$false), confirmation prompting is not used. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is equal to or greater than the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings, so that confirmation of the operation is not required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - -[New-FASTSearchMetadataManagedProperty](New-FASTSearchMetadataManagedProperty.md) - -[Set-FASTSearchMetadataManagedProperty](Set-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataRankProfile.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataRankProfile.md deleted file mode 100644 index 8ae6899154..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataRankProfile.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchmetadatarankprofile -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchMetadataRankProfile ---- - -# Remove-FASTSearchMetadataRankProfile - -## SYNOPSIS -Removes a rank profile from the Microsoft FAST Search Server 2010 for SharePoint system. - -## SYNTAX - -### Name -``` -Remove-FASTSearchMetadataRankProfile [-Name] <String> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -### RankProfile -``` -Remove-FASTSearchMetadataRankProfile -RankProfile <RankProfile> [-Confirm] [-Force] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes a rank profile from the FAST Search Server 2010 for SharePoint system. - -A rank profile controls relevance calculation when searching a full text index. -If a deleted rank profile is specified when searching, then the default rank profile is used. - -The default rank profile cannot be deleted. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchMetadataRankProfile -Name webcontent -``` - -This example removes the rank profile "webcontent". - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -$rankprofile = Get-FASTSearchMetadataRankProfile -Name newrankprofile -Remove-FASTSearchMetadataRankProfile -Force -RankProfile $rankprofile -``` - -This example deletes the rank profile object which represents the rank profile named "newrankprofile". - -No confirmation is required, since the Force parameter is specified. - -## PARAMETERS - -### -Name -The name of the rank profile to remove. - -```yaml -Type: String -Parameter Sets: Name -Aliases: RankProfileName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -RankProfile -An object representing the rank profile to remove. - -```yaml -Type: RankProfile -Parameter Sets: RankProfile -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. - -If Confirm is false (-Confirm:$false), confirmation prompting is not used. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is greater than or equal to the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings, so that confirmation of the operation is not required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataRankProfile](New-FASTSearchMetadataRankProfile.md) - -[Set-FASTSearchMetadataRankProfile](Set-FASTSearchMetadataRankProfile.md) - -[Get-FASTSearchMetadataRankProfile](Get-FASTSearchMetadataRankProfile.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchResource.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchResource.md deleted file mode 100644 index e7555b068b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchResource.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchresource -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchResource ---- - -# Remove-FASTSearchResource - -## SYNOPSIS -Deletes a resource from the resource store. - -## SYNTAX - -``` -Remove-FASTSearchResource [-Path] <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a specified file located in the Microsoft FAST Search Server 2010 for SharePoint resource store. -The location of the resource store is typically specified in %FASTSEARCH%/etc/Admin.config (where %FASTSEARCH% is the FAST Search Server 2010 for SharePoint installation folder.) - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchResource dictionaries\spellcheck\check_en.aut -``` - -This example deletes the resource dictionaries\spellcheck\check_en.aut from the resource store. - -## PARAMETERS - -### -Path -Partial URI within the resource store of the file which will be deleted. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: ResourceURI -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchResource](Get-FASTSearchResource.md) - -[Add-FASTSearchResource](Add-FASTSearchResource.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSearchSettingGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSearchSettingGroup.md deleted file mode 100644 index d835efe82f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSearchSettingGroup.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchsearchsettinggroup -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchSearchSettingGroup ---- - -# Remove-FASTSearchSearchSettingGroup - -## SYNOPSIS -Deletes a Microsoft FAST Search Server 2010 for SharePoint search setting group. - -## SYNTAX - -``` -Remove-FASTSearchSearchSettingGroup -Name <String> [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a FAST Search Server 2010 for SharePoint search setting group. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchSearchSettingGroup -Name marketinggroup -``` - -This example deletes the "marketinggroup" search setting group. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchSearchSettingGroup -Name marketinggroup -Force -``` - -This example deletes the "marketinggroup" search setting group without being prompted to confirm the operation. - -### ---------------EXAMPLE 3----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchSearchSettingGroup -Name marketinggroup -WhatIf -``` - -This example describes what would happen if you executed the Remove-FASTSearchSearchSettingGroup cmdlet. - -## PARAMETERS - -### -Name -The name of the search setting group to delete. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated. - -If Confirm is false (-Confirm:$false), you will not be prompted. - -In cases where Confirm is not specified, the cmdlet will prompt if the $ConfirmPreference shell variable is equal to or greater than the ConfirmImpact setting of the cmdlet (HIGH). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Overrides any user prompting settings so the user is not asked to confirm the operation. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchSearchSettingGroup](New-FASTSearchSearchSettingGroup.md) - -[Get-FASTSearchSearchSettingGroup](Get-FASTSearchSearchSettingGroup.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSecurityAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSecurityAliaser.md deleted file mode 100644 index 54d062f56e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSecurityAliaser.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchsecurityaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchSecurityAliaser ---- - -# Remove-FASTSearchSecurityAliaser - -## SYNOPSIS -Removes a security aliaser. - -## SYNTAX - -``` -Remove-FASTSearchSecurityAliaser [-Identity] <String> [[-SecurityAliaserToRemove] <SecurityAliaser>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a regular expression or XML aliaser. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchSecurityAliaser -Identity xmlalias2 -``` - -This example deletes an XML aliaser. -A prompt is displayed to confirm the request. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchSecurityAliaser -Identity xmlalias4 -Confirm:$False -``` - -This example deletes an XML aliaser without displaying a prompt. - -## PARAMETERS - -### -Identity -The identity of the regular expression or XML aliaser to remove. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -SecurityAliaserToRemove -A SecurityXMLAliaser or SecurityRegexAliaser object whose identity is used as the aliaser identity to remove. - -```yaml -Type: SecurityAliaser -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 10000 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated and you must confirm the remove request. - -To suppress user prompting, set the confirm parameter to false. -For example: -confirm:$false - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityAliaser](Get-FASTSearchSecurityAliaser.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSecurityUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSecurityUserStore.md deleted file mode 100644 index 02bd431aac..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSecurityUserStore.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchsecurityuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchSecurityUserStore ---- - -# Remove-FASTSearchSecurityUserStore - -## SYNOPSIS -Removes a user store. - -## SYNTAX - -``` -Remove-FASTSearchSecurityUserStore [-Identity] <String> [[-SecurityUserStoreToRemove] <SecurityUserStore>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a security user store. -The user store may be a Lotus Notes, Microsoft, or claims user store. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchSecurityUserStore -Identity wn1 -``` - -This example deletes the "wn1" user store. -A prompt is displayed to confirm the request. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchSecurityLotusNotesUserStore ln2 | remove-FASTSearchSecurityUserStore -``` - -This example deletes the user store specified by a piped SecurityUserStoreToRemove instance. -A prompt is displayed to confirm the request. - -## PARAMETERS - -### -Identity -The identity of the user store to remove. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -SecurityUserStoreToRemove -A MicrosoftUserStore, LotusNotesUserStore, or ClaimsUserStore instance whose identity is used to remove the user store. - -```yaml -Type: SecurityUserStore -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Activates user prompting to confirm the operation. -If set, prompting is activated and you must confirm the remove request. - -To suppress user prompting, set the confirm parameter to false. -For example: -confirm:$false - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: get-help about_commonparameters - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityUserStore](Get-FASTSearchSecurityUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSpelltuning.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSpelltuning.md deleted file mode 100644 index f6c9fe7dfa..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSpelltuning.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-fastsearchspelltuning -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Remove-FASTSearchSpelltuning ---- - -# Remove-FASTSearchSpelltuning - -## SYNOPSIS -Disables spell tuning. - -## SYNTAX - -``` -Remove-FASTSearchSpelltuning [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet disables the alignment of the spell check dictionaries with indexed content. -This cmdlet stops the generation of new dictionaries, and the Did You Mean feature will only use content that was fed into the index before this cmdlet was run. - -After disabling the dictionary-index alignment, use the Reset-FASTSearchSpelltuning cmdlet to return to the out-of-the-box spelling dictionaries. -Did You Mean will then make suggestions based on standard spell checking dictionaries, not on indexed content. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### (FAST Server for SharePoint 2010) -``` -Remove-FASTSearchSpelltuning -``` - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSpelltuningStatus](Get-FASTSearchSpelltuningStatus.md) - -[Reset-FASTSearchSpelltuning](Reset-FASTSearchSpelltuning.md) - -[Add-FASTSearchSpelltuning](Add-FASTSearchSpelltuning.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAccessServicesDatabaseServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAccessServicesDatabaseServer.md deleted file mode 100644 index b8edab4b0f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAccessServicesDatabaseServer.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spaccessservicesdatabaseserver -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPAccessServicesDatabaseServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPAccessServicesDatabaseServer - -## SYNOPSIS -{{Fill in the Synopsis}} - - -## SYNTAX - -``` -Remove-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -{{Fill in the Description}} - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` - {{ Add example code here }} -``` - -{{ Add example description here }} - - -## PARAMETERS - -### -AssignmentCollection -{{Fill AssignmentCollection Description}} - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -{{Fill DatabaseServer Description}} - -```yaml -Type: AccessServicesDatabaseServerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerGroup -{{Fill DatabaseServerGroup Description}} - -```yaml -Type: AccessServicesDatabaseServerGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{Fill Force Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -{{Fill ServiceContext Description}} - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPActivityFeedItems.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPActivityFeedItems.md deleted file mode 100644 index 440921586e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPActivityFeedItems.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spactivityfeeditems -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPActivityFeedItems -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPActivityFeedItems - -## SYNOPSIS -Removes activity events from the published and consolidated tables. - - -## SYNTAX - -``` -Remove-SPActivityFeedItems [-AllItems <Boolean>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-ID <Int64>] -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-SearchText <String>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Remove-SPActivityFeedItems cmdlet to remove an activity event. - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$upaProxy = Get-SPServiceApplicationProxy 1232b6f7-b9ff-99ad-0cd0-fg1g67h981aq -$upaProxy = Get-SPServiceApplicationProxy 1232b6f7-b9ff-99ad-0cd0-fg1g67h981aq -``` - -This example removes the specific user profile service application. - - -## PARAMETERS - -### -AllItems -Specifies whether to delete events.A value of "1" deletes all events. -A value of "0", no events are deleted.The default value is 0 (zero). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ID -Limits events deleted to those which match the specified ActivityEventID. - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the proxy of the User Profile Service application that contains the site subscription to delete.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application proxy (for example, UserProfileSvcProxy1); or an instance of a valid SPServiceApplicationProxy object. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchText -Limits events deleted to those which contain SearchText in the string. - -Note that the SearchText will apply to *all* of the XML text saved in SQL representing this activity. The text seen in a browser window may be saved in a different representation in SQL. For example, a ">" feed symbol may be represented as ">" text in SQL, so the SearchText should reference ">" instead of ">". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. - -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationProxyPipeBind -Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAlternateURL.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAlternateURL.md deleted file mode 100644 index 666f0b2b9f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAlternateURL.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spalternateurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPAlternateURL -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPAlternateURL - -## SYNOPSIS -Completely deletes the specified alternate URL. - - -## SYNTAX - -``` -Remove-SPAlternateURL [-Identity] <SPAlternateUrlPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPAlternateUrl` cmdlet completely deletes the alternate URL specified by the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Remove-SPAlternateURL -WebApplication https://sitename -Zone Extranet -``` - -This example deletes the extranet URL for the given Web application. - - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPWebApplication |%{ Get-SPAlternateURL -WebApplication $_ -Zone "Extranet" } | Remove-SPAlternateURL -``` - -This example removes all extranet alternate URLs in the farm. - - -## PARAMETERS - -### -Identity -Specifies the identity of the alternate URL to delete. -The identity can be either a valid URL, in the form https://server_name, or a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPAlternateUrlPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAppDeniedEndpoint.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAppDeniedEndpoint.md deleted file mode 100644 index 48bdaf32c8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAppDeniedEndpoint.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spappdeniedendpoint -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPAppDeniedEndpoint -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPAppDeniedEndpoint - -## SYNOPSIS -Removes a relative URL endpoint of a server from the list of app-denied endpoints. - - -## SYNTAX - -``` -Remove-SPAppDeniedEndpoint [-Endpoint] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPAppDeniedEndpoint` cmdlet to remove a relative URL endpoint of a server from the list of app-denied endpoints. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPAppDeniedEndpoint -Endpoint "/_vti_bin/contoso/service.asmx" -``` - -This example removes the "/_vti_bin/contoso/service.asmx" endpoint from the list of denied endpoints for apps. -Apps will be able to access this endpoint because it is being removed from the app-denied endpoint list. - - -## PARAMETERS - -### -Endpoint -Specifies a relative URL endpoint of a server that will be removed from the list of app-denied endpoints. -Apps will not be able to access relative URL endpoints of a server that exist in the app-denied endpoint list. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPAppDeniedEndpoint](Remove-SPAppDeniedEndpoint.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAppPrincipalPermission.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAppPrincipalPermission.md deleted file mode 100644 index 8949f9a903..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAppPrincipalPermission.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spappprincipalpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPAppPrincipalPermission -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPAppPrincipalPermission - -## SYNOPSIS -Removes the permissions on a specified app principal. - - -## SYNTAX - -``` -Remove-SPAppPrincipalPermission -AppPrincipal <SPAppPrincipal> -Scope <SPCmdletAppPrincipalPermissionScope> - -Site <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [-DisableAppOnlyPolicy] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPAppPrincipalPermission` cmdlet to remove the permissions on a specified app principal for a given scope (that is, SharePoint Online, site collection, or web). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------EXAMPLE------------ -``` -$clientID = "11111111-2222-3333-4444-555555555555" -$site = Get-SPSite http://siteUrl -$realm = Get-SPAuthenticationRealm -ServiceContext $site -$appIdentifier = $clientID + "@" + $realm -$appPrincipal = Get-SPAppPrincipal -NameIdentifier $appIdentifier -Web $site.RootWeb -Remove-AppPrincipalPermission -AppPrincipal $appPrincipal -site $site.RootWeb -Scope Site -``` - -This example removes the App Principal permission from the site collection scope. - - -## PARAMETERS - -### -AppPrincipal -Specifies the AppPrincipal object to remove. - -```yaml -Type: SPAppPrincipal -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Scope -Specifies the scope to which to apply the principal permission. - -The value is any of the following scopes: - ---Site - ---SiteCollection - ---SiteSubscription - -```yaml -Type: SPCmdletAppPrincipalPermissionScope -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Specifies the site (that is, SPWeb object) to remove. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableAppOnlyPolicy -Disables the app only policy. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPAppPrincipalPermission](Set-SPAppPrincipalPermission.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPApplicationCredentialKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPApplicationCredentialKey.md deleted file mode 100644 index eebf988174..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPApplicationCredentialKey.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spapplicationcredentialkey -applicable: SharePoint Server 2019 -title: Remove-SPApplicationCredentialKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPApplicationCredentialKey - -## SYNOPSIS -Removes the application credential key from the local server. - - -## SYNTAX - -``` -Remove-SPApplicationCredentialKey [-AssignmentCollection <SPAssignmentCollection>] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - - -## DESCRIPTION -Use the **Remove-SPApplicationCredentialKey** cmdlet to remove the application credential key from the local server. The application credential key is used by certain features to encrypt and decrypt passwords. - -## EXAMPLES - -### EXAMPLE -```powershell - Remove-SPApplicationCredentialKey -Confirm:$false -``` -This example removes the application credential key from the local server without prompting for user confirmation. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## RELATED LINKS - -[Set-ApplicationCredentialKey](Set-ApplicationCredentialKey.md) - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPBusinessDataCatalogModel.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPBusinessDataCatalogModel.md deleted file mode 100644 index 28748f5218..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPBusinessDataCatalogModel.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spbusinessdatacatalogmodel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPBusinessDataCatalogModel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPBusinessDataCatalogModel - -## SYNOPSIS -Deletes a Business Data Connectivity Model. - - -## SYNTAX - -``` -Remove-SPBusinessDataCatalogModel -Identity <MetadataObject> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPBusinessDataCatalogModel` cmdlet deletes a Business Data Connectivity Model. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$modelFile = Get-SPBusinessDataCatalogMetadataObject -Name "ContosoModel" -BdcObjectType Model -ServiceContext http://contoso - -Remove-SPBusinessDataCatalogModel -Identity $modelFile -``` - -This example removes the Business Data Connectivity Model file named ContosoModel. - - -## PARAMETERS - -### -Identity -Specifies the Business Data Connectivity Metadata Store metadata object to remove. - -```yaml -Type: MetadataObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPCentralAdministration.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPCentralAdministration.md deleted file mode 100644 index 389f7c1327..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPCentralAdministration.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spcentraladministration -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPCentralAdministration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPCentralAdministration - -## SYNOPSIS -Removes the SharePoint Central Administration web site from the local server. - - -## SYNTAX - -``` -Remove-SPCentralAdministration [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Removes the SharePoint Central Administration web site from the local server. - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPCentralAdministration -``` -This example removes the Central Administration web site from the local server. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPClaimProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPClaimProvider.md deleted file mode 100644 index 2d330d2b45..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPClaimProvider.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spclaimprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPClaimProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPClaimProvider - -## SYNOPSIS -Unregisters a claim provider. - - -## SYNTAX - -``` -Remove-SPClaimProvider [-Identity] <SPClaimProviderPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPClaimProvider` cmdlet unregisters a claim provider. -If the unregistered claim provider was assigned to a trusted identity token issuer, the trusted token issuer will use the default (system) claim provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove - SPClaimProvider -Identity "12345678-90ab-cdef-1234-567890bcdefgh" -``` - -This example removes a claim provider from the farm - - -## PARAMETERS - -### -Identity -Specifies the claim provider to unregister. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a claim provider (for example, MyClaimProvider1); or an instance of a valid SPClaimProvider object. - -```yaml -Type: SPClaimProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPClaimTypeMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPClaimTypeMapping.md deleted file mode 100644 index e97cb1e2fb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPClaimTypeMapping.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spclaimtypemapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPClaimTypeMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPClaimTypeMapping - -## SYNOPSIS -Deletes a claim type mapping rule for a security token service (STS) identity provider. - - -## SYNTAX - -``` -Remove-SPClaimTypeMapping [-Identity] <SPClaimMappingPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] -TrustedIdentityTokenIssuer <SPTrustedIdentityTokenIssuerPipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPClaimMapping` cmdlet deletes a claim type mapping rule from a farm trust STS identity provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE------------------------- -``` -Remove-SPClaimMapping "Email" | Get-SPIdentityProvider "LiveIDSTS" -``` - -This example removes an identity provider named LiveIDSTS. - - -## PARAMETERS - -### -Identity -Specifies the claim mapping to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a claim mapping rule (for example, Email); or an instance of a valid SPClaimMapping object. - -```yaml -Type: SPClaimMappingPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedIdentityTokenIssuer -Specifies the token issuer or a valid SPTrustedIdentityTokenIssuerPipeBind object. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPConfigurationDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPConfigurationDatabase.md deleted file mode 100644 index 1437a8826c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPConfigurationDatabase.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spconfigurationdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPConfigurationDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPConfigurationDatabase - -## SYNOPSIS -Permanently removes a configuration database. - - -## SYNTAX - -``` -Remove-SPConfigurationDatabase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPConfigurationDatabase` cmdlet permanently removes the farm's configuration database. -The configuration database must be already dismounted from any associated farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Remove-SPConfigurationDatabase -``` - -This example permanently deletes a configuration database from a farm. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDatabase.md deleted file mode 100644 index dcd8964ddf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDatabase.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPContentDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPContentDatabase - -## SYNOPSIS -Deletes a content database. - -## SYNTAX - -``` -Remove-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPContentDatabase` cmdlet deletes a content database permanently from SQL Server. -In situations where data needs to be persisted, use the `Dismount-SPContentDatabase` cmdlet. -This will remove the content database from SharePoint Products but not from SQL Server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE--------------------- -``` -Remove-SPContentDatabase WSS_Content -``` - -This example deletes the content database named 'WSS_Content'. - -### -----------------EXAMPLE--------------------- -``` -Remove-SPContentDatabase WSS_Content -Confirm:$false -Force -``` - -This example deletes the content database named 'WSS_Content' without asking any confirmation. - -## PARAMETERS - -### -Identity -Specifies the content database to delete. - -The type must be a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint content database (for example, SPContentDB1); or an instance of a valid SPContentDatabase object. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Specifies the force of a removal. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDeploymentJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDeploymentJob.md deleted file mode 100644 index 97a02623bf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDeploymentJob.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spcontentdeploymentjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPContentDeploymentJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPContentDeploymentJob - -## SYNOPSIS -Removes a content deployment job. - - -## SYNTAX - -``` -Remove-SPContentDeploymentJob [-Identity] <SPContentDeploymentJobPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPContentDeploymentJob` cmdlet removes a content deployment job. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE------------------ -``` -Remove-SPContentDeploymentJob -Identity "DeployJob1" -``` - -This example removes a deployment job named DeployJob1. - - -## PARAMETERS - -### -Identity -Specifies the content deployment job to remove. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment job (for example; DeployJob1); or an instance of a valid SPContentDeploymentJob object. - -```yaml -Type: SPContentDeploymentJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDeploymentPath.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDeploymentPath.md deleted file mode 100644 index e2875d7a77..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPContentDeploymentPath.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spcontentdeploymentpath -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPContentDeploymentPath -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPContentDeploymentPath - -## SYNOPSIS -Removes a content deployment path. - - -## SYNTAX - -``` -Remove-SPContentDeploymentPath [-Identity] <SPContentDeploymentPathPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPContentDeploymentPath` cmdlet removes a content deployment path. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE----------------------- -``` -Remove-SPContentDeploymentPath -Path1 -``` - -This example removes a content path named Path1. - - -## PARAMETERS - -### -Identity -Specifies the content deployment path to remove. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment path (for example; DeployPath1); or an instance of a valid SPContentDeploymentPath object. - -```yaml -Type: SPContentDeploymentPathPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDeletedSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDeletedSite.md deleted file mode 100644 index 146ca02d5b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDeletedSite.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spdeletedsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPDeletedSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPDeletedSite - -## SYNOPSIS -Removes a deleted site collection. - - -## SYNTAX - -``` -Remove-SPDeletedSite [-Identity] <SPDeletedSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-ContentDatabase <SPContentDatabasePipeBind>] [-WebApplication <SPWebApplicationPipeBind>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Use the `Remove-SPDeletedSite` cmdlet to permanently remove a deleted site collection from the farm. - -Unlike the `Remove-SPSite` cmdlet that uses the host name and scheme for the Identity parameter (that is, https://server_name), the value of the identity parameter for all SPDeletedSite cmdlets use a server-relative URL. -Typically, the forward slash character (/) begins the relative URL and also denotes the root site. - -For additional information about a server-relative URL or understanding general concepts about absolute and relative URLs, see Server Relative URL Property (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsite.serverrelativeurl.aspx) or Understanding Absolute and Relative URL Addresses (https://msdn.microsoft.com/en-us/library/bb208688(office.12).aspx). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Remove-SPDeletedSite -Identity 610857cb-8414-4a89-8bf3-ad3628f6c86c -``` - -This example permanently removes a specific deleted site collection by using a site ID. - - -## PARAMETERS - -### -Identity -Specifies the identity of the deleted site collection to permanently delete. -The identity can be either a valid server-relative URL in the form /sites/site_name; a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an SPDeletedSite object. - -```yaml -Type: SPDeletedSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the GUID of the content database from which to list site collections. - -The type must be a valid database name in the form SPContentDB01 or a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the Web application from which to list sites. - -The type must be a valid URL in the form https://server_name; a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh; or the Web application name, for example, WebApplication1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDiagnosticsPerformanceCounter.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDiagnosticsPerformanceCounter.md deleted file mode 100644 index c6217d4710..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDiagnosticsPerformanceCounter.md +++ /dev/null @@ -1,220 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spdiagnosticsperformancecounter -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPDiagnosticsPerformanceCounter -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPDiagnosticsPerformanceCounter - -## SYNOPSIS -Removes an instance of a performance counter. - - -## SYNTAX - -``` -Remove-SPDiagnosticsPerformanceCounter [-Category] <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Counter <String>] [-DatabaseServer] [-Instance <String>] [-WebFrontEnd] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPDiagnosticsPerformanceCounter` cmdlet removes performance counters from the collection of performance counters that are read and recorded in the usage database. -This cmdlet can also be used to remove entire categories and types of counters from the collection. -If either the DatabaseServer or WebFrontEnd parameters are not specified, this cmdlet removes the specified performance counters on the front end Web servers in the farm. - -The `Remove-SPDiagnosticsPerformanceCounter` cmdlet is only available by using Windows PowerShell. -There is no user interface. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Remove-SPDiagnosticsPerformanceCounter -category ASP.NET -``` - -This example removes all the counters in the category ASP.NET on front end Web servers. - - -### ------------------EXAMPLE 2------------------ -``` -Remove-SPDiagnosticsPerformanceCounter -category ASP.NET -Counter "Requests Queued" -``` - -This example removes the counters in the category ASP.NET that have requests queued on front end Web servers. - - -### ------------------EXAMPLE 3------------------ -``` -Remove-SPDiagnosticsPerformanceCounter -category Processor -counter "% Processor Time" -instance "_Total" -databaseserver -``` - -This example removes the counters of the _Total instance, with the counter % Processor Time in the category Processor on database servers. - - -## PARAMETERS - -### -Category -Specifies the category of performance counters to remove. - -The type must be a valid name of a category of performance counters; for example, ASP.NET, PhysicalDisk, or Processor. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Counter -Specifies the type of counter to remove. -If this parameter is not specified, this cmdlet removes all performance counters of the specified category. - -The type must be a valid name of counter type; for example, Requests Queued, Avg. -Disk Queue Length, and % Processor Time. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DatabaseServer -Removes the specified performance counters that are collected on the database servers in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Instance -Specifies the instance name of the performance counter to remove. -If this parameter is not specified, this cmdlet removes all instances of the specified performance counter. - -The type must be a valid name of a performance counter instance; for example Total_PerfCounter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WebFrontEnd -Removes performance counters that are collected on the front end Web servers in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDistributedCacheServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDistributedCacheServiceInstance.md deleted file mode 100644 index a6ec286704..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPDistributedCacheServiceInstance.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spdistributedcacheserviceinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPDistributedCacheServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPDistributedCacheServiceInstance - -## SYNOPSIS -Removes an instance of the distributed cache service from a local server. - -## SYNTAX - -``` -Remove-SPDistributedCacheServiceInstance [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Remove-SPDistributedCacheServiceInstance cmdlet to remove an instance of the distributed cache service from a local server. This is required to stop the AppFabric service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715](https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPDistributedCacheServiceInstance -``` - -This example removes an instance of a distributed cache. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Add-SPDistributedCacheServiceInstance](Add-SPDistributedCacheServiceInstance.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEduClassMember.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEduClassMember.md deleted file mode 100644 index c7ea1b41b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEduClassMember.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-speduclassmember -applicable: SharePoint Server 2013 -title: Remove-SPEduClassMember -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEduClassMember - -## SYNOPSIS -Do not use - - -## SYNTAX - -``` -Remove-SPEduClassMember [-AssignmentCollection <SPAssignmentCollection>] -ClassId <String> - -Site <SPSitePipeBind> -UserAlias <String> [<CommonParameters>] -``` - -## DESCRIPTION -Do not use - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Do not use -``` - -## PARAMETERS - -### -AssignmentCollection -Do not use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClassId -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Site -Do not use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -UserAlias -Do not use - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchComponent.md deleted file mode 100644 index d2f14c01d0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchComponent.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcomponent -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchComponent - -## SYNOPSIS -Removes the specified search component from the given search topology. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchComponent [-Identity] <SearchComponentPipeBind> - -SearchTopology <SearchTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes the specified search component from an inactive search topology. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Identity 10fa59cb-4b32-4fe6-8f8d-065388df201e -Remove-SPEnterpriseSearchComponent -SearchTopology $topology -Identity c1642176-b9ae-4096-834c-080da5fba90e -``` - -This example removes the search component with identity c1642176-b9ae-4096-834c-080da5fba90e from the search topology with identity 10fa59cb-4b32-4fe6-8f8d-065388df201e from the default search application. - - -## PARAMETERS - -### -Identity -Specifies the identity for a search component - -```yaml -Type: SearchComponentPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchTopology -Specifies the search topology from which to retrieve the search component/search components. - - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the search topology and search component/search components. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md deleted file mode 100644 index 222b6caa7b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcontentenrichmentconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchContentEnrichmentConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchContentEnrichmentConfiguration - -## SYNOPSIS -Removes the current content enrichment configuration from the search service application. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchContentEnrichmentConfiguration -SearchApplication <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes the current content enrichment configuration from the SearchServiceApplication. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Remove-SPEnterpriseSearchContentEnrichmentConfiguration -SearchApplication $ssa -``` - -This example removes the content enrichment configuration from the default search service application. - - -## PARAMETERS - -### -SearchApplication -Specifies the SearchServiceApplication that contains content enrichment configuration. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchContentEnrichmentConfiguration](Get-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[Set-SPEnterpriseSearchContentEnrichmentConfiguration](Set-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[New-SPEnterpriseSearchContentEnrichmentConfiguration](New-SPEnterpriseSearchContentEnrichmentConfiguration.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlContentSource.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlContentSource.md deleted file mode 100644 index 54f2732fb1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlContentSource.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcrawlcontentsource -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchCrawlContentSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchCrawlContentSource - -## SYNOPSIS -Deletes a specified crawl content source from a search application. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchCrawlContentSource` cmdlet deletes a specified crawl content source from a service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" -$topo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -New-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -clone -CrawlTopology $topo -$newtopo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -Identity 11111111-1111-1111-1111-111111111111 -$cc = Get-SPEnterpriseSearchCrawlComponent -CrawlTopology $newtopo -Identity 22222222-2222-2222-2222-222222222222 -$cc | Remove-SPEnterpriseSearchCrawlComponent -$newtopo | Set-SPEnterpriseSearchCrawlTopology -Active -``` - -This example creates a new, inactive, crawl topology, removes a crawl component from it and activates the new crawl topology. - - -## PARAMETERS - -### -Identity -The crawl content source to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a ContentSource object (for example, ContentSource1); or an instance of a valid ContentSource object. - -```yaml -Type: ContentSourcePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl content source. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlCustomConnector.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlCustomConnector.md deleted file mode 100644 index f87d78a197..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlCustomConnector.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcrawlcustomconnector -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchCrawlCustomConnector -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchCrawlCustomConnector - -## SYNOPSIS -Removes a CustomConnector object. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchCrawlCustomConnector -Identity <SPCustomConnectorPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - -SearchApplication <SearchServiceApplicationPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -The `Get-SPEnterpriseSearchCrawlCustomConnector` selects the custom connector or connectors and then pipes them to the `Remove-SPEnterpriseSearchCrawlCustomConnector` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchCrawlCustomConnector -SearchApplication MySearchServiceApp" - Identity "dctm://" | Remove-SPEnterpriseSearchCrawlCustomConnector -``` - -This example removes a custom connector for the dctm:// protocol from the MySearchServiceApp search service application. - - -## PARAMETERS - -### -Identity -Specifies the CustomConnector object to remove. -The Identity parameter must be an instance of a valid CustomConnector object. - -```yaml -Type: SPCustomConnectorPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplicationobject. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlDatabase.md deleted file mode 100644 index 5aa9db2c16..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlDatabase.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcrawldatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchCrawlDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchCrawlDatabase - -## SYNOPSIS -Deletes a crawl database. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchCrawlDatabase [-Identity] <CrawlStorePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchCrawlDatabase` cmdlet deletes a specified crawl database from a search service application. -A crawl database stores crawl history for a search service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPEnterpriseSearchCrawlDatabase -Identity CrawlDB-0 --SearchApplication mySearchServiceApp -``` - -This example removes the CrawlDB-0 crawl database from the mySearchServiceApp search service application. - - -## PARAMETERS - -### -Identity -Specifies the crawl database to delete. - -A valid crawl database name, in the form CrawlStore1; or a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid CrawlStore object. - -```yaml -Type: CrawlStorePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl database collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlExtension.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlExtension.md deleted file mode 100644 index c53a8eae25..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlExtension.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcrawlextension -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchCrawlExtension -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchCrawlExtension - -## SYNOPSIS -Removes a file name extension from the list of files that can be crawled. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchCrawlExtension [-Identity] <ExtensionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchCrawlExtension` cmdlet prevents files with this extension from being crawled. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" -$searchapp | Get-SPEnterpriseSearchCrawlExtension "pdf" | Remove-SPEnterpriseSearchCrawlExtension -``` - -This example removes the PDF IFilter and removes the pdf file extension from the list of file types to include in the content index. - - -## PARAMETERS - -### -Identity -The file name extension to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid file name extension (for example, .xml); or an instance of a valid CrawlExtension object. - -```yaml -Type: ExtensionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the extension collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlLogReadPermission.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlLogReadPermission.md deleted file mode 100644 index 08a80b384e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlLogReadPermission.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcrawllogreadpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchCrawlLogReadPermission -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchCrawlLogReadPermission - -## SYNOPSIS -Removes permission to view crawl log information. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchCrawlLogReadPermission [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Identity <CrawlLogReadPermissionPipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [-Tenant <Guid>] [-UserNames <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Only the Search Service Application administrator can use this cmdlet. - -The `Remove-SPEnterpriseSearchCrawlLogReadPermission` cmdlet removes the permission to view crawl log information for one or more users. -The administrator can choose to restrict this removal to a particular tenant. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$crawlLogPermission = Get-SPEnterpriseSearchCrawlLogReadPermission -SearchApplication $ssa -Tenant "00000000-0000-0000-0000-000000000001" -Remove-SPEnterpriseSearchCrawlLogReadPermission -Identity $crawlLogPermission -UserNames "contoso\user1;contoso\user2" -``` - -This example removes user1 and user2 from the list of users referenced by $crawlLogPermission. -$crawlLogPermission is the list of users who have permission to view the crawl log information from the tenant with id "00000000-0000-0000-0000-000000000001" on the search application referenced by $ssa. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the crawl log permissions list from which to remove the user(s). - -```yaml -Type: CrawlLogReadPermissionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl log. -The type must be a valid GUID, of the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Specifies the tenant for which the user permissions shall be removed. -The type must be a valid GUID of the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserNames -Specifies the user names that shall no longer have permission to view the crawl log information. -Separate names with semi-colons. - -Specifies the user names that no longer shall have permission to view the crawl log information. -Use the form "domain\username". -When adding several user names, separate names with semi-colons. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPEnterpriseSearchCrawlLogReadPermission](Set-SPEnterpriseSearchCrawlLogReadPermission.md) - -[Get-SPEnterpriseSearchCrawlLogReadPermission](Get-SPEnterpriseSearchCrawlLogReadPermission.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlMapping.md deleted file mode 100644 index 73d685e9e2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlMapping.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcrawlmapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchCrawlMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchCrawlMapping - -## SYNOPSIS -Deletes a crawl mapping. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchCrawlMapping [-Identity] <CrawlMappingPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchCrawlMapping` cmdlet deletes a crawl mapping from the crawl mapping collection. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchapp = Get-SPEnterpriseSearchServiceApplication "Sample Search Service Application" -$mappingtodelete = Get-SPEnterpriseSearchCrawlContentSource -Identity "somemapping" -mappingtodelete | Remove-SPEnterpriseSearchCrawlMapping -``` - -This example removes a crawl mapping from a search application. - - -## PARAMETERS - -### -Identity -The crawl mapping to delete. - -A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid CrawlMapping object. - -```yaml -Type: CrawlMappingPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl mapping collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlRule.md deleted file mode 100644 index 2d50dc5303..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchCrawlRule.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchcrawlrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchCrawlRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchCrawlRule - -## SYNOPSIS -Deletes a crawl rule. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchCrawlRule [-Identity] <CrawlRulePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchCrawlRule` cmdlet deletes a crawl rule that is used to crawl content for a content source. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp -Remove-SPEnterpriseSearchCrawlRule -Identity https://mySPSite -SearchApplication $searchApp -``` - -This example removes a crawl rule pertaining to the path https://mySPSite from the mySearchServiceApp search service application. - - -## PARAMETERS - -### -Identity -The crawl rule to delete. - -A valid crawl rule URL, such as https://server_name, or an instance of a valid CrawlRule object. - -```yaml -Type: CrawlRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -The search application that contains the crawl rule collection. - -A valid search application name, such as SearchApp1, or a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchFileFormat.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchFileFormat.md deleted file mode 100644 index d181cd8c68..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchFileFormat.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchfileformat -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchFileFormat -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchFileFormat - -## SYNOPSIS -Removes support for parsing a file format. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchFileFormat [-Identity] <DocumentParserFileFormatPipeBind> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchFileFormat` removes a file format from the search parsing system. -The search parsing system will only consider the change after a restart of the content processing components. -Afterwards the search parsing system will stop parsing the file format. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Remove-SPEnterpriseSearchFileFormat -SearchApplication $ssa -Identity foo -``` - -This example uses the `Remove-SPEnterpriseSearchFileFormat` cmdlet to remove the file format with the belonging file name extension foo in the search service application referenced by $ssa. - - -## PARAMETERS - -### -Identity -Specifies the identification of the format to be removed. - - -```yaml -Type: DocumentParserFileFormatPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the file format. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchFileFormat](New-SPEnterpriseSearchFileFormat.md) - -[Get-SPEnterpriseSearchFileFormat](Get-SPEnterpriseSearchFileFormat.md) - -[Set-SPEnterpriseSearchFileFormatState](Set-SPEnterpriseSearchFileFormatState.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchLanguageResourcePhrase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchLanguageResourcePhrase.md deleted file mode 100644 index 2fb0e5ac0b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchLanguageResourcePhrase.md +++ /dev/null @@ -1,260 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchlanguageresourcephrase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchLanguageResourcePhrase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchLanguageResourcePhrase - -## SYNOPSIS -Deletes a language resource phrase from a shared search application. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchLanguageResourcePhrase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -Identity <LanguageResourcePhrasePipeBind> [-Language <String>] [-Mapping <String>] -Owner <SearchObjectOwner> - [-SearchApplication <SearchServiceApplicationPipeBind>] [-SourceId <Guid>] [-Type <LanguageResourceType>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchLanguageResourcePhrase` cmdlet deletes one or more language resource phrases from the collection of language resource phrases in a shared search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" -$obsoletephrase = Get-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $searchapp -Language en-us -Type QuerySuggestionBlockList -Identity secret -$obsoletephrase | Remove-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $searchapp -Type QuerySuggestionBlockList -Language en-us -``` - -This example removes a language resource item on the QuerySuggestionBlockList for the en-us language. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The language resource phrase to delete. - -The type must be a string; a valid name of a language resource phrase (for example, LanguageResourcePhrase1); or an instance of a valid LanguageResourcePhrase object. - - -```yaml -Type: LanguageResourcePhrasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Language -Deletes phrases of the specified language only. - -The type must be a valid name of a language; for example, en_us. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mapping -Allows a term or phrase to be mapped to another term or phrase. -For example, the nickname "John" could be mapped to "Jonathan". - -This parameter only applies to nicknames and substitutions. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding LanguageResourcePhrase is created. - -The owner must be one of the following valid levels: - -- Search Service Application - -- Site Subscription - -- Site Collection - -- Site - - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the language resources. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceId -Identifies the search result source for which the LanguageResourcePhrase applies to. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Constrains to delete phrases of specified type. - -The type must be one of the following valid types of phrases: - -- QuerySuggestionBlockList - -- QuerySuggestionAlwaysSuggest - -- Nickname - -- QuerySuggestionSubstitution - - -```yaml -Type: LanguageResourceType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchLinksDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchLinksDatabase.md deleted file mode 100644 index 8784fa0bb4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchLinksDatabase.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchlinksdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchLinksDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchLinksDatabase - -## SYNOPSIS -Deletes a links database. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchLinksDatabase [-Identity] <LinksStorePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchLinksDatabase` cmdlet deletes a specified links database from a search service application. -A links database stores query logging and analytics information. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$linksDatabase = $ssa | Get-SPEnterpriseSearchLinksDatabase Links2 -Remove-SPEnterpriseSearchLinksDatabase -Identity $linksDatabase -``` - -This example removes the links database referenced by $linksDatabase. -$linksDatabase is the identity of the links database Links2 on the search service application referenced by $ssa. - - -## PARAMETERS - -### -Identity -Specifies the links database to delete. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a LinksStore object, in the form LinksStore1; or an instance of a valid LinksStore object. - -```yaml -Type: LinksStorePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the links database. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchLinksDatabase](New-SPEnterpriseSearchLinksDatabase.md) - -[Set-SPEnterpriseSearchLinksDatabase](Set-SPEnterpriseSearchLinksDatabase.md) - -[Get-SPEnterpriseSearchLinksDatabase](Get-SPEnterpriseSearchLinksDatabase.md) - -[Move-SPEnterpriseSearchLinksDatabases](Move-SPEnterpriseSearchLinksDatabases.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataCategory.md deleted file mode 100644 index 8fa1bf7138..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataCategory.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchmetadatacategory -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchMetadataCategory -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchMetadataCategory - -## SYNOPSIS -Deletes a crawled property category. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchMetadataCategory [-Identity] <CategoryPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a crawled property category. -You should use this cmdlet after a crawl to delete unused or unwanted categories from the metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchapp = Get-SPEnterpriseSearchServiceApplication -Remove-SPEnterpriseSearchMetadataCategory -Identity MyCategory -SearchApplication $searchapp -``` - -This example removes the metadata category named MyCategory for the default search service application. - - -## PARAMETERS - -### -Identity -Specifies the metadata category to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a metadata category, for example, MetadataCategory1, or an instance of a valid Category object. - -Note that if only a name for a category is specified, a SearchApplication must also be specified. - -```yaml -Type: CategoryPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the enterprise search metadata property schema. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataManagedProperty.md deleted file mode 100644 index ffd40cdd1a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataManagedProperty.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchmetadatamanagedproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchMetadataManagedProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchMetadataManagedProperty - -## SYNOPSIS -Deletes a metadata managed property. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchMetadataManagedProperty [-Identity] <ManagedPropertyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-SiteCollection <Guid>] [-Tenant <Guid>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a specified managed property from the managed property collection. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchapp = Get-SPEnterpriseSearchServiceApplication -$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity AboutMeUpdate -Remove-SPEnterpriseSearchMetadataManagedProperty -Identity $mp -``` - -This example removes the managed property AboutMeUpdate from the default search service application. - - -## PARAMETERS - -### -Identity -Specifies the managed property to delete. - -The type must be a valid name of a managed property, for example ManagedProperty1, or an instance of a valid ManagedProperty object. - -Note that if only a name of a managed property is specified, a SearchApplication must also be specified. - -```yaml -Type: ManagedPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the managed property collection. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the managed properties returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the managed properties returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataMapping.md deleted file mode 100644 index 29c5034d59..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchMetadataMapping.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchmetadatamapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchMetadataMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchMetadataMapping - -## SYNOPSIS -Deletes a metadata mapping from a managed property. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchMetadataMapping [-Identity] <MappingPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes mappings from a managed property. -A metadata mapping is the mapping between a managed property and one or more crawled properties in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$searchapp = Get-SPEnterpriseSearchServiceApplication -$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $searchapp -Identity People -$cp = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Category $cat -Limit 1 -$mycp = New-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Name "MyCrawlProp" -PropSet $cp.PropSet -Category $cp.CategoryName -IsNameEnum $false -VariantType $cp.VariantType -$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity UserName -New-SPEnterpriseSearchMetadataMapping -SearchApplication $searchapp -ManagedProperty $mp -CrawledProperty $mycp -# Retrieve the new mapping -$map = Get-SPEnterpriseSearchMetadataMapping -SearchApplication $searchapp -ManagedProperty $mp -CrawledProperty $mycp -Remove-SPEnterpriseSearchMetadataMapping -Identity $map -confirm:$false -``` - -This example removes an existing mapping between the managed property UserName and the crawled property MyCrawlProp (see `Set-SPEnterpriseSearchMetadataMapping`) for the default search service application. - - -## PARAMETERS - -### -Identity -Specifies the metadata mapping to delete. - -The type must be a valid URL, in the form https://server_name, or an instance of a valid Mapping object. - -```yaml -Type: MappingPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the managed property collection. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryAuthority.md deleted file mode 100644 index f4e6974715..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryAuthority.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchqueryauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchQueryAuthority -schema: 2.0.0 ---- - -# Remove-SPEnterpriseSearchQueryAuthority - -## SYNOPSIS -Deletes an authoritative page. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchQueryAuthority [-Identity] <AuthorityPagePipeBind> -Owner <SearchObjectOwner> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchQueryAuthority` cmdlet adjusts query rank by deleting an authoritative page. -SPEnterpriseSearchQueryAuthority represents authoritative sites that rank higher in relevance than demoted sites, which are de-emphasized in relevance. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPEnterpriseSearchQueryAuthority -Identity https://contoso.com -SearchApplication MySSA -``` - -This example removes the query authority URL https://contoso.com from the search service application named MySSA. - - -## PARAMETERS - -### -Identity -Specifies the query authority page to delete. - -The type must be a valid URL, in the form https://server_name; or an instance a valid AuthorityPage object. - -```yaml -Type: AuthorityPagePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding Query Authority is created.The owner must be one of the following valid levels:- Search Service Application- Site Subscription - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the authoritative page collection to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid Search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryDemoted.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryDemoted.md deleted file mode 100644 index 6d456d1053..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryDemoted.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchquerydemoted -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchQueryDemoted -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchQueryDemoted - -## SYNOPSIS -Deletes a demoted site rule. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchQueryDemoted [-Identity] <DemotedPipeBind> -Owner <SearchObjectOwner> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchQueryDemoted` cmdlet adjusts query rank by deleting a demoted site rule from the demoted site collection. -Query demoted sites are de-emphasized in relevance. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$demotedRule = Get-SPEnterpriseSearchQueryDemoted -Identity https://somesite.com -SearchApplication MySSA -$demotedRule | Remove-SPEnterpriseSearchQueryDemoted -``` - -This example obtains a reference to a site demotion rule for the URL https://somesite.com and removes it. - - -## PARAMETERS - -### -Identity -Specifies the demoted site rule to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid Demoted object. - -```yaml -Type: DemotedPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding Demoted object is created. The owner must be one of the following valid levels:- Search Service Application- Site Subscription - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the demoted site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryKeyword.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryKeyword.md deleted file mode 100644 index 434779a789..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryKeyword.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchquerykeyword -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchQueryKeyword -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchQueryKeyword - -## SYNOPSIS -Deletes a query keyword. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchQueryKeyword [-Identity] <KeywordPipeBind> -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchQueryKeyword` cmdlet deletes unused or unwanted keywords from the query keyword collection. - -You cannot use this cmdlet after a site collection is upgraded to SharePoint Server because keywords and Best Bets are automatically migrated to query rules. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchQueryKeyword -Identity Engineering -Site https://myserver/sites/engineering | Remove-SPEnterpriseSearchQueryKeyword -Site https://myserver/sites/engineering -``` - -This example removes the Engineering keyword from the site collection at https://myserver/sites/engineering. - - -## PARAMETERS - -### -Identity -Specifies the keyword term to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid string that contains a keyword term (for example, KeywordTerm1); or an instance of a valid Keyword object. - -```yaml -Type: KeywordPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Filters to delete keywords from the specified site collection of results. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryScope.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryScope.md deleted file mode 100644 index 1cd6bd5818..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryScope.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchqueryscope -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchQueryScope -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchQueryScope - -## SYNOPSIS -Deletes a query scope. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchQueryScope [-Identity] <ScopePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-Url <Uri>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -After you upgrade a Search service application to SharePoint Server, you can view shared scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for shared scopes after upgrade. -However, you can convert shared scopes to result sources, which serve a similar purpose. -Similarly, after you upgrade a SharePoint Server site collection to SharePoint Server, you can view local scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for local scopes after you upgrade a site collection. -However, you can convert local scopes to result sources, which serve a similar purpose. - -The `Remove-SPEnterpriseSearchQueryScope` cmdlet deletes one or more specified shared scopes from the query scope collection. -A query scope represents a query results scope used by all shared search applications on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPenterpriseSearchServiceApplication -Identity MySSA -Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa | Remove-SPEnterpriseSearchQueryScope -``` - -This example removes a scope named MustCrawl from a search service application named MySSA. - - -## PARAMETERS - -### -Identity -Specifies the query scope to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope (for example, Scope1); or an instance of a valid Scope object. - -```yaml -Type: ScopePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope collection. - -The type must be a valid GUID, of the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Filters to delete scopes of the specified results URL. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryScopeRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryScopeRule.md deleted file mode 100644 index 295866b25a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchQueryScopeRule.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchqueryscoperule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchQueryScopeRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchQueryScopeRule - -## SYNOPSIS -Deletes query results scope rules. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchQueryScopeRule [-Identity] <ScopeRulePipeBind> -Url <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Scope <ScopePipeBind>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -After you upgrade a Search service application to SharePoint Server, you can view shared scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for shared scopes after upgrade. -However, you can convert shared scopes to result sources, which serve a similar purpose. -Similarly, after you upgrade a SharePoint Server site collection to SharePoint Server, you can view local scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for local scopes after you upgrade a site collection. -However, you can convert local scopes to result sources, which serve a similar purpose. - -The `Remove-SPEnterpriseSearchQueryScopeRule` cmdlet deletes one or more shared scope rules from the scope rule collection. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA" -$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa -Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url https://criticalSite | Remove-SPEnterpriseSearchQueryScopeRule -Url https://criticalSite -``` - -This example removes a scope rule for the URL https://criticalSite from a search service application named MySSA. - - -## PARAMETERS - -### -Identity -Specifies the scope rule to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope rule (for example, ScopeRule1); or an instance of a valid ScopeRule object. - -```yaml -Type: ScopeRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -Filters to delete query scope rules for the specified results URL. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Filters to delete multiple rules for a specified scope. - -The type must be a valid string that identifies the scope; for example, Scope1. - -```yaml -Type: ScopePipeBind -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope rule collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchRankingModel.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchRankingModel.md deleted file mode 100644 index 32929582b8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchRankingModel.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchrankingmodel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchRankingModel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchRankingModel - -## SYNOPSIS -Deletes a ranking model. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchRankingModel [-Identity] <RankingModelPipeBind> -Owner <SearchObjectOwner> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a specified ranking model. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" -$owner = Get-SPEnterpriseSearchOwner -Level ssa -Remove-SPEnterpriseSearchRankingModel -Identity 8f6fd0bc-06f9-43cf-bbab-08c377e083f4 -SearchApplication $ssa -Owner $owner -``` - -This example removes the ranking model for the search service application with the identity 8f6fd0bc-06f9-43cf-bbab-08c377e083f4. - - -### ------------------EXAMPLE 2------------------ -``` -$owner = Get-SPEnterpriseSearchOwner -Level ssa -$MyRanking = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" | Get-SPEnterpriseSearchRankingModel -Owner $owner -Remove-SPEnterpriseSearchRankingModel -Identity $MyRanking -Owner $owner -``` - -This example removes the ranking model object MyRanking from the search service application Search Service Application. - - -## PARAMETERS - -### -Identity -Specifies the ranking model to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid RankingModel object. - -```yaml -Type: RankingModelPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Owner -Specifies the scope where the ranking model is available. -The available scopes are: SSA, Tenant, Site Collection or Site. -A ranking model can be available in multiple scopes. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the ranking model. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchResultItemType.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchResultItemType.md deleted file mode 100644 index 48164a35da..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchResultItemType.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchresultitemtype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchResultItemType -schema: 2.0.0 ---- - -# Remove-SPEnterpriseSearchResultItemType - -## SYNOPSIS -Removes a result item type for a search object owner. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchResultItemType [-Identity] <ResultItemTypePipeBind> -Owner <SearchObjectOwner> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] - [-SearchApplicationProxy <SearchServiceApplicationProxyPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchResultItemType` cmdlet removes a user-created result item type, given a result type identity and a search owner. -You cannot use this cmdlet to remove the built-in result item types that are included with SharePoint products. - -Result item types enable you to change the look of search results based on the type of result. -You start by defining a collection of rules, which will be evaluated against the properties of results. -Then you define the display template to use for rendering that type of result. -Once you have created the result item type, results matching the rules of the result item type will display using the specified display template. - -Example use cases: - -- Change the look of results for a particular file name extension, for example Word documents. - -- Change the look of a particular content type in search results. - -- Change the look of results from a particular author. - -- Add a result action to results from a particular result source as part of a custom search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$web = Get-SPWeb "UrlOfTheSite" -$tenantOwner = Get-SPEnterpriseSearchOwner -Level SPSite -SPWeb $web -$searchapp = Get-SPEnterpriseSearchServiceApplication -$resultType = Get-SPEnterpriseSearchResultItemType -Owner $tenantOwner -SearchApplication $searchapp -Remove-SPEnterpriseSearchResultItemType -Identity $resultType -Owner $tenantOwner -SearchApplication $searchapp -``` - -This example first defines variables for the URL of the site, the search owner and search application. -It then retrieves the result item type and checks whether the result item type is a built-in result item type or not. -If $resultType.BuiltIn returns false, the result item type is not built-in and you can modify it. -Next, the example removes the result item type referenced by $resultType for the owner referenced by $tenantOwner. - -## PARAMETERS - -### -Identity -Specifies the result item type to update. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: ResultItemTypePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the result item type is created. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the name of the search application. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplicationProxy -Specifies the proxy of the search application that contains the result item type. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application proxy name (for example, SearchAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchResultItemType](New-SPEnterpriseSearchResultItemType.md) - -[Set-SPEnterpriseSearchResultItemType](Set-SPEnterpriseSearchResultItemType.md) - -[Get-SPEnterpriseSearchResultItemType](Get-SPEnterpriseSearchResultItemType.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchResultSource.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchResultSource.md deleted file mode 100644 index 3efa51006a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchResultSource.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchresultsource -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchResultSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchResultSource - -## SYNOPSIS -Deletes a result source. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchResultSource [-Identity] <ResultSourcePipeBind> -Owner <SearchObjectOwner> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a specified result source. -This cmdlet supports the same delete operations as are supported through the "Manage Result Sources" page in Central Administration. -The result source cannot be a built-in source (a built-in source has the BuiltIn property set to true). -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" -$owner = Get-SPEnterpriseSearchOwner -Level SSA -Remove-SPEnterpriseSearchResultSource -Identity "Custom SharePoint Result Source" -SearchApplication $ssa -Owner $owner -``` - -This example deletes the search service application level result source with the name "Custom SharePoint Result Source". - - -### ------------------EXAMPLE 2------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" -$owner = Get-SPEnterpriseSearchOwner -Level SSA -Remove-SPEnterpriseSearchResultSource -Identity 12345678-90ab-cdef-1234-567890bcdefgh -SearchApplication $ssa -Owner $owner -``` - -This example deletes the search service application level result source with the id 12345678-90ab-cdef-1234-567890bcdefgh. - - -### ------------------EXAMPLE 3------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" -$owner = Get-SPEnterpriseSearchOwner -Level SSA -$resultSource = Get-SPEnterpriseSearchResultSource -Identity "Custom SharePoint Result Source" -SearchApplication $ssa -Owner $owner -Remove-SPEnterpriseSearchResultSource -Identity $resultSource -SearchApplication $ssa -Owner $owner -``` - -This example deletes the search service application level result source with the name "Custom SharePoint Result Source", by specifying a Source instance. - - -## PARAMETERS - -### -Identity -Specifies the result source to delete. -The result source cannot be a built in source. -The type must be a valid GUID string, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a result source (for example, "Custom SharePoint Result Source"); or an instance of a valid Source object. - - -```yaml -Type: ResultSourcePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding result source is available. - - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchResultSource](New-SPEnterpriseSearchResultSource.md) - -[Get-SPEnterpriseSearchResultSource](Get-SPEnterpriseSearchResultSource.md) - -[Set-SPEnterpriseSearchResultSource](Set-SPEnterpriseSearchResultSource.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchSecurityTrimmer.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchSecurityTrimmer.md deleted file mode 100644 index e25a7f8f85..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchSecurityTrimmer.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchsecuritytrimmer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchSecurityTrimmer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchSecurityTrimmer - -## SYNOPSIS -Deletes a custom security trimmer. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchSecurityTrimmer [[-Identity] <SecurityTrimmerPipeBind>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes the customized security trimmer that is used for a search application's query results. -A custom security trimmer trims search results before the results are returned to the user. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchSecurityTrimmer -SearchApplication MySSA | Remove-SPEnterpriseSearchSecurityTrimmer -``` - -This example removes the security trimmer registered in the search service application named MySSA. - - -## PARAMETERS - -### -Identity -Specifies the security trimmer to delete. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid SecurityTrimmer object. - -```yaml -Type: SecurityTrimmerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the security trimmer. - -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index 2ded2a4097..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Deletes a search service application. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-RemoveData] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes a specified SearchServiceApplication from a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPEnterpriseSearchServiceApplication -Identity MySSA -``` - -This example removes the search service application named MySSA from the farm. - - -## PARAMETERS - -### -Identity -Specifies the search service application to delete. - -A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveData -Specifies that all search databases and index files associated with the search service application to be deleted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplicationProxy.md deleted file mode 100644 index 9a89b6dbf4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplicationProxy.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchServiceApplicationProxy - -## SYNOPSIS -Deletes a search service application proxy. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchServiceApplicationProxy [-Identity] <SearchServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes the specified search service application proxy from a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPEnterpriseSearchServiceApplicationProxy -Identity SearchProxy -``` - -This example removes a search service application proxy named SearchProxy. - - -## PARAMETERS - -### -Identity -Specifies the search service application proxy to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application proxy (for example, ServiceAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplicationSiteSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplicationSiteSettings.md deleted file mode 100644 index 18b9dde4c6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchServiceApplicationSiteSettings.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchserviceapplicationsitesettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchServiceApplicationSiteSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchServiceApplicationSiteSettings - -## SYNOPSIS -Cleans up search settings for a particular site collection, subscription, or search application. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchServiceApplicationSiteSettings [-Identity] <SiteSettingsPipeBind> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-TenantId <Guid>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPEnterpriseSearchServiceApplicationSiteSettings` cmdlet to remove all search settings for the specified site collection, subscription, or search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$app = Get-SPEnterpriseSearchServiceApplication -$GC = Start-SPAssignment -$s = $GC | Get-SPSite UrlOfASiteCollection -Remove-SPEnterpriseSearchServiceApplicationSiteSettings -Identity $s.ID.ToString() -SearchApplication $app -Stop-SPAssignment $GC -``` - -This example removes the search settings for the site collection referenced by $s in the search application referenced by $app. -$s is the site collection with URL "UrlOfSiteCollection" and $s.ID.ToString() is the string representation of the site ID. - - -## PARAMETERS - -### -Identity -Specifies the site collection to remove search settings from. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SiteSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the name of the search application. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -Specifies the tenant from which to remove search settings. -The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings](Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchSiteHitRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchSiteHitRule.md deleted file mode 100644 index 3656b5e502..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchSiteHitRule.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchsitehitrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchSiteHitRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchSiteHitRule - -## SYNOPSIS -Deletes a site hit rule. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchSiteHitRule [-Identity] <SiteHitRulePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SearchService <SearchServicePipeBind>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchSiteHitRule` cmdlet deletes the site hit rule that controls the number of threads used to crawl a given site. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------- -``` -Remove-SPEnterpriseSearchSiteHitRule -Identity myHost -``` - -This example removes a site hit rule for the myHost host. - - -## PARAMETERS - -### -Identity -The rule that is used for the specified site. - -The type must be a valid site hit rule host or an instance of a valid SiteHitRule object. - -```yaml -Type: SiteHitRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchService -Specifies the search service in the farm that hosts the crawl. - -The type must be an instance of a valid SearchService object; otherwise, the local service on the server that hosts the Windows PowerShell cmdlet is used. - -```yaml -Type: SearchServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTenantConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTenantConfiguration.md deleted file mode 100644 index 14b6c460cf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTenantConfiguration.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchtenantconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchTenantConfiguration -schema: 2.0.0 ---- - -# Remove-SPEnterpriseSearchTenantConfiguration - -## SYNOPSIS -Removes all tenant specific search settings. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchTenantConfiguration [-SiteSubscriptionId] <Guid> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPEnterpriseSearchTenantConfigurationcmdlet` removes all tenant specific search settings. -The removed settings are: query Rules, result types, result sources, managed metadata, ranking models, search dictionaries, authoritative pages, query suggestion settings, client types and the default search center. -Use this cmdlet when removing tenants and in conjunction with moving tenants. -When moving a tenant, copy the tenant configuration from the source to the destination and then use this cmdlet to remove the tenant configuration from the source farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Remove-SPEnterpriseSearchTenantConfiguration -SiteSubscriptionId "00000000-0000-0000-0000-000000000001" -SearchApplication $ssa -``` - -This example uses Remove-SPEnterpriseSearchTenantConfiguration to remove all tenant specific settings from the search service application referenced by $ssa. - - -## PARAMETERS - -### -SiteSubscriptionId -Specifies the site subscription of the tenant. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: Identity -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the name of the search application that contains the tenant configuration. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTenantSchema.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTenantSchema.md deleted file mode 100644 index 64cb4c1010..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTenantSchema.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchtenantschema -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchTenantSchema -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchTenantSchema - -## SYNOPSIS -Removes a defined search schema. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchTenantSchema [-Identity] <TenantSchemaPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-SiteCollection <Guid>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes a search schema. -Use this cmdlet to remove an unused or unwanted search schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -[Guid]$guid = "909b84cb-90f2-4a1b-8df4-22547a9b2227" -Remove-SPEnterpriseSearchTenantSchema -Identity $guid -SearchApplication $ssa -``` - -This example removes the search schema for the tenant with GUID 909b84cb-90f2-4a1b-8df4-22547a9b2227. - - -## PARAMETERS - -### -Identity -Specifies the tenant of the search schema to be removed. - -The type must be a valid GUID, in string form, that identifies the tenant in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -The tenant GUID can be found in the Search Service Application database, in the folder \Databases\Search_Service_Application\Tables\dbo.MSSTenant. - -```yaml -Type: TenantSchemaPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the enterprise search schema to be removed. - -The type must be a valid search application name (for example, SearchApp1), or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the search schema to be removed is within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTopology.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTopology.md deleted file mode 100644 index dd6a8abae7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchTopology.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spenterprisesearchtopology -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPEnterpriseSearchTopology -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPEnterpriseSearchTopology - -## SYNOPSIS -Removes an inactive search topology from a search service application. - - -## SYNTAX - -``` -Remove-SPEnterpriseSearchTopology [-Identity] <SearchTopologyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes the given inactive search topology from the search service application to which it belongs. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Identity 4b32-4fe6-8f8d-065388df201e -Remove-SPEnterpriseSearchTopology -Identity $topology -``` - -This example removes a search topology with the identity 4b32-4fe6-8f8d-065388df201e. - - -### ------------------EXAMPLE 2------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Remove-SPEnterpriseSearchTopology -Identity $topo -SearchApplication $ssa -``` - -This example removes the search topology referenced by $topo in the search service application referenced by $ssa. - - -## PARAMETERS - -### -Identity -Specifies the search topology to retrieve. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application to which the search topology belongs. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchTopology](Get-SPEnterpriseSearchTopology.md) - -[New-SPEnterpriseSearchTopology](New-SPEnterpriseSearchTopology.md) - -[Set-SPEnterpriseSearchTopology](Set-SPEnterpriseSearchTopology.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelBIServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelBIServer.md deleted file mode 100644 index 1e33018263..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelBIServer.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spexcelbiserver -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Remove-SPExcelBIServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPExcelBIServer - -## SYNOPSIS - -Removes an instance of Analysis Services. - - -## SYNTAX - -``` -Remove-SPExcelBIServer [-Identity] <SPExcelBIServerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION - -Use the Remove-SPExcelBIServer cmdlet to remove an instance of Analysis Services from the Allow List of BI servers to be used with -Excel Services. - - - - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Remove-SPExcelBIServer -ExcelServiceApplication "MyExcel" - -``` - -This example removes the instance of the anaylsis services that uses the Excel Service Application named, "MyExcel". - - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the ExcelServiceApplication identity. - -```yaml -Type: SPExcelBIServerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Excel.Server.Cmdlet.SPExcelBIServerPipeBind -Microsoft.Office.Excel.Server.Cmdlet.SPExcelServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelBlockedFileType.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelBlockedFileType.md deleted file mode 100644 index adbd2cec88..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelBlockedFileType.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spexcelblockedfiletype -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Remove-SPExcelBlockedFileType -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPExcelBlockedFileType - -## SYNOPSIS -Removes an entry from the list of file types that are prevented from loading on Excel Services Application. - - -## SYNTAX - -``` -Remove-SPExcelBlockedFileType [-Identity] <SPExcelBlockedFileTypePipeBind> - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPExcelBlockedExcelFileType` cmdlet removes an entry from the list of file types that are prevented from loading on an Excel Services Application Web service application. -Excel Services Application does not load any file types that correspond to a file type that is on this list. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | Remove-SPExcelBlockedExcelFileType -FileType XLSX -``` - -This example removes the .xlsx file name extensions from the list of file types that are prevented from loading by Excel Services Application. - -After the .xlsx file name extension is removed from the list, these extensions are allowed to load in Excel Services Application. - - -## PARAMETERS - -### -Identity -Specifies the file type to remove from the list of blocked file types. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; one of the following file types: XLSX, XLSB, XLSM; or an instance of a valid SPExcelBlockedFileType object. - -```yaml -Type: SPExcelBlockedFileTypePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPBlockedExcelFileType list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelDataConnectionLibrary.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelDataConnectionLibrary.md deleted file mode 100644 index 608db1330a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelDataConnectionLibrary.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spexceldataconnectionlibrary -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Remove-SPExcelDataConnectionLibrary -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPExcelDataConnectionLibrary - -## SYNOPSIS -Removes a data connection library from Excel Services Application. - - -## SYNTAX - -``` -Remove-SPExcelDataConnectionLibrary [-Identity] <SPExcelDCLPipeBind> - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPExcelDataConnectionLibrary` cmdlet removes a library from the Excel Services Application trusted data connection libraries list. -Excel Services Application loads data connection files only if they are stored in a data connection library that is on the trusted data connection libraries list. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Get-SPExcelServiceApplication | Get-SPExcelDataConnectionLibrary | Remove-SPExcelDataConnectionLibrary -``` - -This example removes all data connection libraries from all Excel Services Application running in the farm. - -Connection files are no longer loaded from any libraries. -Workbooks that depend on any connection files might not refresh data. - - -## PARAMETERS - -### -Identity -Specifies the data connection library to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a data connection library (for example, DataConnectionLib1); a valid URL, in the form https://server_name; or an instance of a valid SPExcelDCL object. - -```yaml -Type: SPExcelDCLPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelDataConnectionLibrary list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelDataProvider.md deleted file mode 100644 index 321cd26410..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelDataProvider.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spexceldataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Remove-SPExcelDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPExcelDataProvider - -## SYNOPSIS -Removes a data provider from Excel Services Application. - - -## SYNTAX - -``` -Remove-SPExcelDataProvider [-Identity] <SPExcelDataProviderPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPExcelDataProvider` cmdlet removes a data provider that is stored on the list of safe data providers. -Excel Services Application refreshes external data connections only if the data provider for that connection is on the list of safe data providers. -Excel Services Application includes a set of common data providers on this list, so using cmdlets to modify safe data providers is typically done only in custom data connection scenarios. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -C:\PS>$provider = Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelDataProvider | { where {$_.providerID -eq "MyCustomProvider"} - -Remove-SPExcelDataProvider $provider -``` - -This example removes a custom data provider from the list of safe data providers that is on the Excel Services Application Web service application named MyExcelService. - -Excel Services Application will no longer refresh any data connections that use this data provider. - - -## PARAMETERS - -### -Identity -Specifies the SPExcelDataProvider object to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid SPExcelDataProvider object. - -```yaml -Type: SPExcelDataProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelFileLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelFileLocation.md deleted file mode 100644 index 4197d91782..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelFileLocation.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spexcelfilelocation -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Remove-SPExcelFileLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPExcelFileLocation - -## SYNOPSIS -Removes a trusted file location from Excel Services Application. - - -## SYNTAX - -``` -Remove-SPExcelFileLocation [-Identity] <SPExcelFileLocationPipeBind> - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPExcelFileLocation` cmdlet removes a location from the list of trusted file locations. -Excel Services Application loads only workbooks that are stored in a trusted file location. -Properties of trusted file locations control how workbooks can be used when loaded on Excel Services Application. -Excel Services Application always enforces the properties defined by the trusted file location from which a workbook was loaded. -The properties used by the trusted file location are determined by comparing the file path for the workbook with the Address parameter of the trusted file location. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Get-SPExcelServiceApplication | Get-SPExcelFileLocation | where {$_.Address -ne "http://"} | Remove-SPExcelFileLocation -``` - -This example removes all nondefault trusted file locations from every Excel Services Application Web service application in the farm. - - -## PARAMETERS - -### -Identity -Specifies the FileLocation object to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid string that identifies the file location, in the form https://myPortal/myTeam; a valid string that identifies the path, in the form C:\folder_name; or an instance of a valid SPExcelFileLocation object. - -```yaml -Type: SPExcelFileLocationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelUserDefinedFunction.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelUserDefinedFunction.md deleted file mode 100644 index da06a554f7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPExcelUserDefinedFunction.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spexceluserdefinedfunction -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Remove-SPExcelUserDefinedFunction -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPExcelUserDefinedFunction - -## SYNOPSIS -Removes a user-defined function from Excel Services Application. - - -## SYNTAX - -``` -Remove-SPExcelUserDefinedFunction [-Identity] <SPExcelUDFPipeBind> - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPExcelUserDefinedFunction` cmdlet removes a user-defined function from the list of user-defined functions. -User-defined functions are managed code assemblies that can be called from an Excel Services Application workbook by using standard Excel Services Application formula syntax. -The assemblies can perform custom logic or other actions, such as refresh data. -The Windows PowerShell cmdlets operate on the entries in the user-defined function list, but do not operate on the assemblies. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Get-SPExcelServiceApplication | Remove-SPExcelUserDefinedFunction -Identity "SampleCompany.SampleApplication.SampleUdf" -``` - -This example removes the SampleCompany.SampleApplication.SampleUdf user-defined function from the list of user-defined functions for every Excel Services Application Web service application in the farm. - - -## PARAMETERS - -### -Identity -Specifies the SPExcelUserDefinedFunction object that you want to remove. - -The type must be a valid name of the code assembly (for example, SampleCompany.SampleApplication.SampleUdf); or an instance of a valid SPExcelUDF object. - -```yaml -Type: SPExcelUDFPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the list of user-defined functions. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPInfoPathUserAgent.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPInfoPathUserAgent.md deleted file mode 100644 index 36f07b9080..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPInfoPathUserAgent.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spinfopathuseragent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPInfoPathUserAgent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPInfoPathUserAgent - -## SYNOPSIS -Removes a user agent. - - -## SYNTAX - -``` -Remove-SPInfoPathUserAgent [-Identity] <SPUserAgentPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPIPUserAgent` cmdlet removes a specified user agent from the user agent collection on a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Remove-SPInfoPathUserAgent -Identity "UserAgentName" -``` - -This example removes a user agent. - - -## PARAMETERS - -### -Identity -Specifies the name of the user agent to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a user agent (for example, UserAgent1; or an instance of a valid SPUserAgent object. - -```yaml -Type: SPUserAgentPipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPManagedAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPManagedAccount.md deleted file mode 100644 index 1484dbdf2e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPManagedAccount.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spmanagedaccount -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPManagedAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPManagedAccount - -## SYNOPSIS -Removes a managed account registration from the farm. - - -## SYNTAX - -``` -Remove-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -NewPassword <SecureString> - [-AssignmentCollection <SPAssignmentCollection>] [-ChangePassword] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Remove-SPManagedAccount` cmdlet removes account registration from the configuration database within the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE------------------- -``` -Remove-SPManagedAccount -Identity DOMAIN\ServiceAcct -``` - -This example removes the DOMAIN\ServiceAcct managed account from the farm. - - -## PARAMETERS - -### -Identity -Specifies the full name or partial name of the managed accounts to retrieve. - -The type must be a valid account name, in the form Domain\User, or a GUID, in the form 1234-3456-09876. - -```yaml -Type: SPManagedAccountPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NewPassword -Specifies a secure string for the new password (that is, $MySecureString). Works in conjunction with the ChangePassword parameter. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ChangePassword -Specifies whether a password is to be changed. -Works in conjunction with the NewPassword parameter. -When the ChangePassword value is set, a secure string value is required for the NewPassword parameter (that is, $MySecureString). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPManagedPath.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPManagedPath.md deleted file mode 100644 index 2fb9f2bc16..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPManagedPath.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spmanagedpath -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPManagedPath -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPManagedPath - -## SYNOPSIS -Deletes the specified managed path from the specified host header or Web application. - - -## SYNTAX - -### HostHeader -``` -Remove-SPManagedPath [-Identity] <SPPrefixPipeBind> [-HostHeader] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### WebApplication -``` -Remove-SPManagedPath [-Identity] <SPPrefixPipeBind> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Remove-SPManagedPath` cmdlet deletes the managed path specified by the Identity parameter from the host header or the Web application. -The Identity must be the partial URL of the managed path to be deleted. - -If you are using host-named site collections, specify the HostHeader parameter. -To delete a host-named site collection managed path, provide the HostHeader switch. -Otherwise, you must specify the Web application that contains the managed path to be deleted. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE 1---------------------------- -``` -Remove-SPManagedPath "sites" -HostHeader -``` - -This example removes the sites managed path from the list of host-named site collection managed paths. - -Depending on the confirmation level of the local system, the preceding example can prompt prior to execution. - - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPWebApplication | Remove-SPManagedPath "personal" -confirm:$false -``` - -This example removes the personal managed path from all Web applications in the farm. -This command does not prompt for confirmation. - - -## PARAMETERS - -### -Identity -Specifies the name of the managed path to delete. -For example, in the URL https://sitename/sites/site1, "sites" is the name of the managed path. - -```yaml -Type: SPPrefixPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -HostHeader -Specifies that the Identity is a host header managed path. - -```yaml -Type: SwitchParameter -Parameter Sets: HostHeader -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the identity of the Web application that hosts the managed path to delete. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid Web application name (for example, WebApplication1212); or a valid name, in the form WebApp2423. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplication.md deleted file mode 100644 index 819b059848..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplication.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spperformancepointserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPPerformancePointServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPPerformancePointServiceApplication - -## SYNOPSIS -Deletes a PerformancePoint Service application from a farm. - - -## SYNTAX - -``` -Remove-SPPerformancePointServiceApplication - [-Identity] <SPPerformancePointMonitoringServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPPerformancePointServiceApplication` cmdlet deletes a PerformancePoint Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE----------------- -``` -Remove-SPPerformancePointServiceApplication -Identity PPSApp_01 -``` - -This example removes the PPSApp_01 PerformancePoint Service application. - - -## PARAMETERS - -### -Identity -Specifies the PerformancePoint Service application to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointMonitoringServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `et-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplicationProxy.md deleted file mode 100644 index fd5c0f6de1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplicationProxy.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spperformancepointserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPPerformancePointServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPPerformancePointServiceApplicationProxy - -## SYNOPSIS -Deletes the proxy for a PerformancePoint Service application. - - -## SYNTAX - -``` -Remove-SPPerformancePointServiceApplicationProxy - [-Identity] <SPPerformancePointMonitoringServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPPerformancePointServiceApplicationProxy` cmdlet deletes the proxy for a PerformancePoint Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE-------------------- -``` -Remove-SPPerformancePointServiceApplicationProxy -Identity PPS_Application_Proxy_01 -``` - -This example removes the PPS_Application_Proxy_01 application proxy from its associated PerformancePoint Service application. - - -## PARAMETERS - -### -Identity -Specifies the PerformancePoint Service application proxy to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application proxy (for example, PerfPointAppProxy1); or an instance of a valid SPPerformancePointMonitoringServiceApplicationProxy object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplicationTrustedLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplicationTrustedLocation.md deleted file mode 100644 index 412cb3b002..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPerformancePointServiceApplicationTrustedLocation.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spperformancepointserviceapplicationtrustedlocation -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPPerformancePointServiceApplicationTrustedLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPPerformancePointServiceApplicationTrustedLocation - -## SYNOPSIS -Removes a single trusted location from a PerformancePoint Service application. - - -## SYNTAX - -``` -Remove-SPPerformancePointServiceApplicationTrustedLocation - -Identity <SPPerformancePointMonitoringServiceApplicationTrustedLocationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPPerformancePointServiceApplicationTrustedLocation` cmdlet deletes a single trusted location from a PerformancePoint Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------------EXAMPLE-------------------- -``` -Remove-SPPerformancePointServiceApplicationTrustedLocation -Identity <Valid GUID of a Trusted Location in an Application> -``` - -This example removes a Trusted Location having the specified GUID from a PerformancePoint Service Application. - - -## PARAMETERS - -### -Identity -Specifies the trusted location to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPPerformancePointMonitoringServiceApplicationTrustedLocation object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationTrustedLocationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPluggableSecurityTrimmer.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPluggableSecurityTrimmer.md deleted file mode 100644 index 403d54bfcd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPPluggableSecurityTrimmer.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sppluggablesecuritytrimmer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPPluggableSecurityTrimmer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPPluggableSecurityTrimmer - -## SYNOPSIS -Removes a pluggable security trimmer from a profile service application proxy. - - -## SYNTAX - -``` -Remove-SPPluggableSecurityTrimmer -UserProfileApplicationProxyId <Guid> -PlugInId <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPPluggableSecurityTrimmer` cmdlet to remove a specified pluggable security trimmer from a User Profile service application proxy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE 1---------------------- -``` -$pr = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Remove-SPPluggableSecurityTrimmer -UserProfileApplicationProxyId $pr.Id -PlugInId 0 -``` - -This example removes a pluggable security trimmer. - - -### -----------------EXAMPLE 2---------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Remove-SPPluggableSecurityTrimmer -UserProfileApplicationProxyId $proxy.Id -PlugInId 0 -``` - -This example turns off security trimming in a User Profile Service Application. - - -## PARAMETERS - -### -UserProfileApplicationProxyId -Specifies the ID of the User Profile service application proxy from which the pluggable security trimmer is removed. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PlugInId -The index of the pluggable security trimmer must have an integer value greater than or equal to zero. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProfileLeader.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProfileLeader.md deleted file mode 100644 index 633d6f3bd2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProfileLeader.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spprofileleader -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPProfileLeader -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPProfileLeader - -## SYNOPSIS -Remove a company leader. - - -## SYNTAX - -``` -Remove-SPProfileLeader [-ProfileServiceApplicationProxy] <SPServiceApplicationProxyPipeBind> - [-Name] <SPProfileLeaderPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Use the `Remove-SPProfileLeader` cmdlet to remove a user as the company leader. - -For additional information about SPProfileLeader cmdlets, see The *-SPProfileLeader Windows PowerShell cmdlets in SharePoint Server SP1 (https://go.microsoft.com/fwlink/p/?LinkId=226295) (https://go.microsoft.com/fwlink/p/?LinkId=226295). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Remove-SPProfileLeader -ProfileServiceApplicationProxy $proxy -Name "contoso\janedow" -``` - -This example removes the user "Jane Dow" from the leaders list for a specific user profile service application. - - -## PARAMETERS - -### -ProfileServiceApplicationProxy -Specifies the name of the User Profile Service Application Proxy to use. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the account name to be removed as a leader for the new User Profile Service application. -For example, Contoso\Joe. - -```yaml -Type: SPProfileLeaderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProfileSyncConnection.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProfileSyncConnection.md deleted file mode 100644 index 9eb2a2cefb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProfileSyncConnection.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spprofilesyncconnection -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPProfileSyncConnection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPProfileSyncConnection - -## SYNOPSIS -Removes a synchronization connection. - - -## SYNTAX - -``` -Remove-SPProfileSyncConnection [-ProfileServiceApplication] <SPServiceApplicationPipeBind> - -ConnectionDomain <String> -ConnectionForestName <String> -ConnectionPassword <SecureString> - -ConnectionSynchronizationOU <String> -ConnectionUserName <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-ConnectionNamingContext <String>] - [-ConnectionServerName <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Use the `Remove-SPProfileSyncConnection` cmdlet to remove a User Profile synchronization connection. - -This cmdlet only works with Active Directory Synchronization Connections - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Remove-SPProfileSyncConnection -ProfileServiceApplication 888ds256-9ad9-53a9-f135-99eecd245670b -ConnectionDomain "Fabrikam" -ConnectionUserName "Testupa" -ConnectionPassword convertto-securestring "Password1" -asplaintext -force -ConnectionSynchronizationOU "OU=SharePoint Users,DC=fabrikam,DC=com" -``` - -This example removes a user from the fabrikam domain using a specific user profile service application. - - -## PARAMETERS - -### -ProfileServiceApplication -Specifies the name of the User Profile service application. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ConnectionDomain -Specifies the NetBIOS name of the domain you are connecting to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionForestName -Specifies the forest name you are connecting to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionPassword -Specifies the password of the account used for directory connection. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionSynchronizationOU -Specifies the top level organizational unit (OU) that you would like to synchronize. -The value must be a domain name and you can only include one container per command. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionUserName -Specifies the user name to be used for the synchronization connection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionNamingContext -Specifies the naming context of the directory information tree to connect to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionServerName -Specifies the name of the connection server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProjectWebInstanceData.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProjectWebInstanceData.md deleted file mode 100644 index 379202b124..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProjectWebInstanceData.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spprojectwebinstancedata -applicable: Project Server 2016, Project Server 2019 -title: Remove-SPProjectWebInstanceData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPProjectWebInstanceData - -## SYNOPSIS -Disassociates a Site Collection with the Project Server instance. - - -## SYNTAX - -``` -Remove-SPProjectWebInstanceData [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -SiteCollection <SPSitePipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet disassociates the Project Server instance from the specified Site Collection, disabling the PWA Feature and removing Project content. - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Remove-SPProjectWebInstanceData -SiteCollection https://contoso/sites/pwa -``` - -This example disassociates https://contoso/sites/pwa from the Project Server instance. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -The site collection to disassociate from the Project Server instance. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingMachineInfo.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingMachineInfo.md deleted file mode 100644 index f91b0ca3cd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingMachineInfo.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sproutingmachineinfo -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPRoutingMachineInfo -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPRoutingMachineInfo - -## SYNOPSIS -Removes an external routing target. - - -## SYNTAX - -``` -Remove-SPRoutingMachineInfo [-Identity] <SPRoutingMachineInfoPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPRoutingMachineInfo` cmdlet to remove an external routing target by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------EXAMPLE------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -C:\PS>$M=Get-SPRoutingMachineInfo -RequestManagementSettings $rm -Name <MachineName> - -Remove-SPRoutingMachineInfo -Identity $M -``` - -This example removes a routing target for a specified identity. - - -## PARAMETERS - -### -Identity -Specifies the computer object that Request Manager will remove. - -```yaml -Type: SPRoutingMachineInfoPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingMachineInfo](Add-SPRoutingMachineInfo.md) - -[Get-SPRoutingMachineInfo](Get-SPRoutingMachineInfo.md) - -[Set-SPRoutingMachineInfo](Set-SPRoutingMachineInfo.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingMachinePool.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingMachinePool.md deleted file mode 100644 index 4145791e32..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingMachinePool.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sproutingmachinepool -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPRoutingMachinePool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPRoutingMachinePool - -## SYNOPSIS -Removes a routing pool from Request Manager. - - -## SYNTAX - -``` -Remove-SPRoutingMachinePool [-Identity] <SPRoutingMachinePoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPRoutingMachinePool` cmdlet to remove a routing pool from the Request Manager object by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -C:\PS>$pool=Get-SPRoutingMachinePool -RequestManagementSettings $rm - -Remove-SPRoutingMachinePool -Identity $pool -``` - -This example removes a routing pool for the specified identity by using the $pool variable. - - -## PARAMETERS - -### -Identity -Specifies the Request Manager object to remove. - -```yaml -Type: SPRoutingMachinePoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingMachinePool](Add-SPRoutingMachinePool.md) - -[Get-SPRoutingMachinePool](Get-SPRoutingMachinePool.md) - -[Set-SPRoutingMachinePool](Set-SPRoutingMachinePool.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingRule.md deleted file mode 100644 index 6332e634c9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPRoutingRule.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sproutingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPRoutingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPRoutingRule - -## SYNOPSIS -Removes a routing rule. - - -## SYNTAX - -``` -Remove-SPRoutingRule [-Identity] <SPRoutingRulePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPRoutingRule` cmdlet removes a routing rule by using the Identity parameter. -If the Identity parameter is not specified, the routing rules for the entire farm are removed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -Get-SPRoutingRule -RequestManagementSettings $rm - -C:\PS>$machines=Get-SPRoutingMachineInfo -RequestManagementSettings $rm - -C:\PS>$pool=Add-SPRoutingMachinePool -RequestManagementSettings $rm -Name <Name of Pool> -MachineTargets $machines - -C:\PS>$c=New-SPRequestManagementRuleCriteria -Value http -Property url -MatchType startswith -CaseSensitive $false - -C:\PS>$rule=Add-SPRoutingRule -RequestManagementSettings $rm -Name <Rule Name> -Criteria $c -MachinePool $pool - -Remove-SPRoutingRule -Identity $rule -``` - -This example removes a routing for a specified identity by using the $rule variable. - - -## PARAMETERS - -### -Identity -Specifies the rule object to remove. - -```yaml -Type: SPRoutingRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingRule](Add-SPRoutingRule.md) - -[Get-SPRoutingRule](Get-SPRoutingRule.md) - -[Set-SPRoutingRule](Set-SPRoutingRule.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPScaleOutDatabase.md deleted file mode 100644 index 81726a5c73..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPScaleOutDatabase.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPScaleOutDatabase - -## SYNOPSIS -Removes a specific scale-out database. - - -## SYNTAX - -``` -Remove-SPScaleOutDatabase -Database <SPDatabasePipeBind> -ServiceApplication <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DeleteData] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPScaleOutDatabase` cmdlet to remove a specific scale-out database from a specified service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -C:\PS>$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication - -C:\PS>$database = $databases[0] - -Remove-SPScaleOutDatabase -ServiceApplication $serviceApplication -Database $database -``` - -This example removes the specified scale-out database from the specified service application. - - -## PARAMETERS - -### -Database -Specifies the scale-out database to remove. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the service application of the scale-out database to remove. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeleteData -Specifies whether to delete data when the scale out database is removed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPScaleOutDatabase](Add-SPScaleOutDatabase.md) - -[Get-SPScaleOutDatabase](Get-SPScaleOutDatabase.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSecureStoreApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSecureStoreApplication.md deleted file mode 100644 index 5bfee5ea70..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSecureStoreApplication.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsecurestoreapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSecureStoreApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSecureStoreApplication - -## SYNOPSIS -Deletes a Secure Store application. - - -## SYNTAX - -``` -Remove-SPSecureStoreApplication -Identity <SPSecureStoreApplication> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSecureStoreApplication` cmdlet deletes a Secure Store application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApp" | Remove -SPSecureStoreApplication -``` - -This example removes the specified application and target. - - -## PARAMETERS - -### -Identity -Specifies the Secure Store application to delete. - -```yaml -Type: SPSecureStoreApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSecureStoreSystemAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSecureStoreSystemAccount.md deleted file mode 100644 index 16b19467a0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSecureStoreSystemAccount.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsecurestoresystemaccount -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSecureStoreSystemAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSecureStoreSystemAccount - -## SYNOPSIS -Removes a user account from a designated list. - - -## SYNTAX - -``` -Remove-SPSecureStoreSystemAccount [-Identity] <SPSecureStoreSystemAccountPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPSecureStoreSystemAccount` cmdlet to remove a user account from a designated list of accounts which will be considered a system account. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE 1----------------------------- -``` -Remove-SPSecureStoreSystemAccount -Identity contoso\jdoe -``` - -This example removes a specific user name jdoe by using the Identity parameter. - - -### -----------------------EXAMPLE 2----------------------------- -``` -Get-SPSecureStoreSystemAccount | Where-Object -filter {$_.AccountName -eq 'Contoso\admin'} | Remove-SPSecureStoreSystemAccount -``` - -This example removes the admin, user from the contoso domain by filtering the results from the `Get-SPSecureStoreSystemAccount` cmdlet. - - -## PARAMETERS - -### -Identity -Specifies the name, object, or GUID to remove. - -```yaml -Type: SPSecureStoreSystemAccountPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPSecureStoreSystemAccount](Add-SPSecureStoreSystemAccount.md) - -[Get-SPSecureStoreSystemAccount](Get-SPSecureStoreSystemAccount.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServerScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServerScaleOutDatabase.md deleted file mode 100644 index 4e53c72340..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServerScaleOutDatabase.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spserverscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPServerScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPServerScaleOutDatabase - -## SYNOPSIS -Removes a specific scale-out database. - - -## SYNTAX - -``` -Remove-SPServerScaleOutDatabase -Database <SPDatabasePipeBind> - -ServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DeleteData] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Remove-SPServerScaleOutDatabase cmdlet to remove a specific scale-out database from a specified service application. - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Managed Metadata Service'} -$database = Get-SPServerScaleOutDatabase -ServiceApplication $sa -Remove-SPServerScaleOutDatabase -Database $database -ServiceApplication $sa -``` - -This example removes the specified scale-out database from the Managed Metadata Service application. - - -## PARAMETERS - -### -Database -Specifies the scale-out database to remove. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the service application of the scale-out database to remove. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeleteData -Specifies whether to delete data when the scale out database is removed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Add-SPServerScaleOutDatabase](Add-SPServerScaleOutDatabase.md) - -[Get-SPServerScaleOutDatabase](Get-SPServerScaleOutDatabase.md) - -[Split-SPServerScaleOutDatabase](Split-SPServerScaleOutDatabase.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplication.md deleted file mode 100644 index eb6154bf74..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplication.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPServiceApplication - -## SYNOPSIS -Deletes the specified service application on the local server. - - -## SYNTAX - -``` -Remove-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-RemoveData] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPServiceApplication` cmdlet deletes the specified service application from the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------------- -``` -Remove-SPServiceApplication 053c34be-d251-488c-8e94-644eae94da26 -RemoveData -``` - -This example deletes the service application and its database. - -The service application GUID is unique to every farm. -You can run the `Get-SPServiceApplication` cmdlet to see the GUID of the service applications and then use the result from the `Get-SPServiceApplication` cmdlet for other SPServiceApplication cmdlets; for example, or `Publish-SPServiceApplication`. - - -## PARAMETERS - -### -Identity -Specifies the GUID of the service application to remove. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveData -Deletes all databases and other data associated with the service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationPool.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationPool.md deleted file mode 100644 index 559ec37883..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationPool.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spserviceapplicationpool -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPServiceApplicationPool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPServiceApplicationPool - -## SYNOPSIS -Completely deletes the specified Web service application pool. - - -## SYNTAX - -``` -Remove-SPServiceApplicationPool [-Identity] <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPServiceApplicationPool` cmdlet completely deletes the specified Web service application pool. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Remove-SPServiceApplicationPool TestServiceWebApplicationPool -``` - -This example deletes the selected service application pool. - - -## PARAMETERS - -### -Identity -Specifies the identity of the Web service application pool to delete. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxy.md deleted file mode 100644 index ce72f0057d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxy.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPServiceApplicationProxy - -## SYNOPSIS -Deletes the specified service application proxy. - - -## SYNTAX - -``` -Remove-SPServiceApplicationProxy [-Identity] <SPServiceApplicationProxyPipeBind> [-RemoveData] [-Confirm] - [-WhatIf] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPServiceApplicationProxy` cmdlet deletes the service application proxy specified by the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Remove-SPServiceApplicationProxy $proxy -``` - -This example deletes the User Profile Service Application proxy. - -## PARAMETERS - -### -Identity -Specifies the GUID of the service application proxy to remove. - -The type must be a GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RemoveData -Deletes all databases and other data associated with the service application proxy. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxyGroup.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxyGroup.md deleted file mode 100644 index 4dd9478e26..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxyGroup.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spserviceapplicationproxygroup -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPServiceApplicationProxyGroup -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPServiceApplicationProxyGroup - -## SYNOPSIS -Completely deletes the specified service application proxy group. - - -## SYNTAX - -``` -Remove-SPServiceApplicationProxyGroup [-Identity] <SPServiceApplicationProxyGroupPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Completely deletes the specified service application proxy group. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE------------------------- -``` -Remove-SPServiceApplicationProxyGroup RemoteProxyGroup -``` - -This example deletes the service application proxy group named RemoteProxyGroup. - -The service application proxy group GUID is unique to every farm. -You can run `Get-SPServiceApplicationProxyGroup | Select Name,Id` to see the GUID of the service application proxy groups. -Use this result for any other SPServiceApplicationProxyGroup cmdlets. - - -## PARAMETERS - -### -Identity -The identity of the service application proxy group to delete. - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxyGroupMember.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxyGroupMember.md deleted file mode 100644 index 1273eb470a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPServiceApplicationProxyGroupMember.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spserviceapplicationproxygroupmember -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPServiceApplicationProxyGroupMember -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPServiceApplicationProxyGroupMember - -## SYNOPSIS -Removes one or more proxies from the specified service application proxy group. - - -## SYNTAX - -``` -Remove-SPServiceApplicationProxyGroupMember [-Identity] <SPServiceApplicationProxyGroupPipeBind> - [-Member] <SPServiceApplicationProxyPipeBind[]> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPServiceApplicationProxyGroupMember` cmdlet removes one or more proxies from the specified service application proxy group. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Remove-SPServiceApplicationProxyGroupMember RemoteProxyGroup -Member babab30e-8e3a-428b-8ff4-4d5c8f455e6d -``` - -This example removes a service application proxy from the selected service application proxy group named RemoteProxyGroup. - -The service application proxy group GUID is unique to every farm. -You can run `Get-SPServiceApplicationProxyGroup | Select Name,Id` to see the GUID of the service application proxy groups. -Use this result for any other SPServiceApplicationProxyGroup cmdlets. - - -## PARAMETERS - -### -Identity -Specifies the identity of the service application proxy group from which to remove the member or members. - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Member -Specifies the member or members to remove from the service application proxy group. - -```yaml -Type: SPServiceApplicationProxyPipeBind[] -Parameter Sets: (All) -Aliases: Proxy -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPShellAdmin.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPShellAdmin.md deleted file mode 100644 index 379d655602..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPShellAdmin.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spshelladmin -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPShellAdmin -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPShellAdmin - -## SYNOPSIS -Removes a user from the SharePoint_Shell_Access role. - - -## SYNTAX - -``` -Remove-SPShellAdmin [-UserName] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-database <SPDatabasePipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPShellAdmin` cmdlet to remove a user from the SharePoint_Shell_Access role in a specified database. - -When you use this cmdlet to remove a user from the role, you do not remove the user from the WSS_ADMIN_WPG group in the target database. - -When you run this cmdlet to add a user to the SharePoint_Shell_Access role, the user must have the following security permissions: - -- Security_Admin role access on the instance of SQL Server and the db_owner role in the database. -- Administrative permission to the local computer. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------------EXAMPLE----------------------------- -``` -Remove-SPShellAdmin -UserName CONTOSO\User1 -database 4251d855-3c15-4501-8dd1-98f960359fa6 -``` - -This example removes an existing user named User1 from the SharePoint_Shell_Access role in the database specified. - - -## PARAMETERS - -### -UserName -Specifies the name of the user you want to remove from the SharePoint_Shell_Access role in the specified database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -database -Specifies the GUID of the database or the Database Object that includes the SharePoint_Shell_Access role from which the user is to be removed. -If the database parameter is not specified, the configuration database is used. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSite.md deleted file mode 100644 index 7989ef134f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSite.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSite - -## SYNOPSIS -Completely deletes an existing site collection and all subsites. - - -## SYNTAX - -``` -Remove-SPSite [-Identity] <SPSitePipeBind> [-DeleteADAccounts] [-GradualDelete] - [-CheckComplianceFlags <Boolean>] [-AssignmentCollection <SPAssignmentCollection>] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -The **Remove-SPSite** cmdlet completely deletes an existing site collection and all subsites. -This operation cannot be undone. - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Remove-SPSite -Identity 'https://sitename/' -GradualDelete -Confirm:$False -``` - -This example removes the given site collection and all included sites by using GradualDelete which places the site in the site recycle bin; confirmation has been suppressed. - -### ------------------EXAMPLE 2----------------------- -``` -Remove-SPSite -Identity 'https://sitename/' -``` - -This example immediately deletes the site and it's contents from the farm. - -## PARAMETERS - -### -Identity -Specifies the identity of the site to delete. -The identity can be either a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` -### -DeleteADAccounts -Forces deletion of user accounts from Active Directory Domain Services (AD DS). -This applies when in AD DS account creation mode and the value of this parameter is True, AD DS accounts associated with the site collection are also deleted from AD DS. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### -CheckComplianceFlags -Specifies if compliance flags are enabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeleteADAccounts -Forces deletion of user accounts from Active Directory Domain Services (AD DS). - -This applies when in AD DS account creation mode and the value of this parameter is True, AD DS accounts associated with the site collection are also deleted from AD DS. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GradualDelete -If provided, occurs gradually to use less system load. - -This operation is strongly recommended for deleting very large sites. This option places the site in the site recycle bin instead of immediately deleting the site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteMaster.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteMaster.md deleted file mode 100644 index e61f608509..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteMaster.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitemaster -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteMaster -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteMaster - -## SYNOPSIS -Removes a site master. - -## SYNTAX -``` -Remove-SPSiteMaster [-ContentDatabase] <SPContentDatabasePipeBind> [-SiteId] <Guid> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Remove-SPSiteMaster cmdlet to remove a site master from the database. - -## EXAMPLES -### -----------------------EXAMPLE----------------------------- -``` -$master = Get-SPSiteMaster -ContentDatabase WSS_Content | Select -First 1 -Remove-SPSiteMaster -ContentDatabase WSS_Content -SiteId $master.SiteId -``` - -This example removes the first Site Master found in the WSS_Content database. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the name of the database to remove the site master. For example, WSS_Content. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -SiteId -Specifies the ID of the Site Master to remove. For example, ff480534-7e64-44a5-b7e3-7c418624cdf6. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPContentDatabasePipeBind -System.Guid -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscription.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscription.md deleted file mode 100644 index da3edadc34..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscription.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitesubscription -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteSubscription -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteSubscription - -## SYNOPSIS -Removes data stored in a subscription settings service application for a set of site subscriptions. - - -## SYNTAX - -``` -Remove-SPSiteSubscription [-Identity] <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSiteSubscription` cmdlet removes a site subscription along with all contained site collections and settings. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Remove-SPSiteSubscription "https://contoso.com/" -``` - -This example removes all data for the contoso.com site subscription (site collections, site subscription and settings). - - -## PARAMETERS - -### -Identity -Specifies the site subscription settings service application that contains the service data to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubscriptionSettingsApp1); or an instance of a valid SPSubscriptionSettingsServiceApplication object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces the removal of a site subscription and is the only way to stop this command from prompting for confirmation. - -The type must be either of the following values: - -- True -- False - -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionBusinessDataCatalogConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionBusinessDataCatalogConfig.md deleted file mode 100644 index b6109710b5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionBusinessDataCatalogConfig.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitesubscriptionbusinessdatacatalogconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteSubscriptionBusinessDataCatalogConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteSubscriptionBusinessDataCatalogConfig - -## SYNOPSIS -Removes the Business Data Connectivity Metadata Store for a partition. - - -## SYNTAX - -``` -Remove-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSiteSubscriptionBusinessDataCatalogConfig` cmdlet removes the Business Data Connectivity Metadata Store and all associated data for a specified partition. -To completely remove a partition and the data that it contains, run the `Clear-SPSiteSubscriptionBusinessDataCatalogConfig` cmdlet to remove the data from the Business Data Connectivity Metadata Store and then run the `Remove-SPSiteSubscriptionBusinessDataCatalogConfig` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext http://contoso -``` - -This example removes the Business Data Connectivity Metadata Store for the partition http://contoso. - - -## PARAMETERS - -### -ServiceContext -Specifies the service context of the Business Data Connectivity Metadata Store to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service context (for example, http://ServiceContext1); or an instance of a valid SPServiceContext object. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionFeaturePack.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionFeaturePack.md deleted file mode 100644 index a00a4691b5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionFeaturePack.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitesubscriptionfeaturepack -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteSubscriptionFeaturePack -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteSubscriptionFeaturePack - -## SYNOPSIS -Removes a SharePoint Feature set from a site subscription. - - -## SYNTAX - -``` -Remove-SPSiteSubscriptionFeaturePack [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSiteSubscriptionFeaturePack` cmdlet removes a SharePoint Feature set by specifying the GUID or Feature set object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE------------------------ -``` -Remove-SPFeatureSet -Identity "30daa535-b0fe-4d10-84b0-fb04029d161a" -``` - -This example removes a SharePoint Feature set that has the ID 30daa535-b0fe-4d10-84b0-fb04029d161a. - - -## PARAMETERS - -### -Identity -Specifies the Feature set object to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a feature set (for example, FeatureSet1); or an instance of a valid SPFeatureSet object. - -```yaml -Type: SPSiteSubscriptionFeaturePackPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionFeaturePackMember.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionFeaturePackMember.md deleted file mode 100644 index 3d5816d011..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionFeaturePackMember.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitesubscriptionfeaturepackmember -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteSubscriptionFeaturePackMember -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteSubscriptionFeaturePackMember - -## SYNOPSIS -Removes a feature definition from the provided SharePoint Feature set. - - -## SYNTAX - -### AllFeatureDefinitions -``` -Remove-SPSiteSubscriptionFeaturePackMember [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> - [-AllFeatureDefinitions] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -### SingleFeatureDefinition -``` -Remove-SPSiteSubscriptionFeaturePackMember [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> - -FeatureDefinition <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Remove-SPSiteSubscriptionFeaturePackMember` cmdlet removes the provided FeatureDefinition parameter from the feature set specified by the Identity parameter. -If the AllFeatureDefinitions flag is provided, all feature definitions are removed from the given Feature set. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -C:\PS>$FS = Get-SPSiteSubscriptionFeaturePack "30daa535-b0fe-4d10-84b0-fb04029d161a" - -Remove-SPSiteSubscriptionFeaturePackMember -Identity $fs -FeatureDefinition (Get-SPFeature "PublishingSite") -``` - -This example removes the PublishingSite feature from the Feature set that has ID 30daa535-b0fe-4d10-84b0-fb04029d161a. - - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPSiteSubscriptionFeaturePack "30daa535-b0fe-4d10-84b0-fb04029d161a" | Remove-SPSiteSubscriptionFeaturePackMember -AllFeatureDefinitions -``` - -This example removes all features from the Feature set 30daa535-b0fe-4d10-84b0-fb04029d161a. - - -## PARAMETERS - -### -Identity -Specifies the Feature set from which to remove a feature. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a feature set (for example, FeatureSet1); or an instance of a valid SPFeatureSet object. - -```yaml -Type: SPSiteSubscriptionFeaturePackPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AllFeatureDefinitions -Clears all features from the Feature set. - -```yaml -Type: SwitchParameter -Parameter Sets: AllFeatureDefinitions -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FeatureDefinition -Specifies the feature definition to be removed. - -```yaml -Type: SPFeatureDefinitionPipeBind -Parameter Sets: SingleFeatureDefinition -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionMetadataConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionMetadataConfig.md deleted file mode 100644 index a97f832179..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionMetadataConfig.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitesubscriptionmetadataconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteSubscriptionMetadataConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteSubscriptionMetadataConfig - -## SYNOPSIS -Removes site subscription configuration settings. - - -## SYNTAX - -``` -Remove-SPSiteSubscriptionMetadataConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-ServiceProxy] <SPMetadataServiceProxyCmdletPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPSiteSubscriptionMetadataConfig` cmdlet to remove the site subscription-specific configuration settings for a specified Metadata Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE------------------- -``` -Remove-SPSiteSubscriptionMetadataConfig -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -``` - -This example removes the site subscription-specific settings from an existing partitioned Metadata Service application. - - -## PARAMETERS - -### -Identity -Specifies the site subscription for which to remove the Metadata Service application settings. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscriptionConfig1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceProxy -Specifies the local metadata service proxy for the service application containing the site subscription-specific settings. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of the service application proxy (for example, ServiceAppProxy1); or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionProfileConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionProfileConfig.md deleted file mode 100644 index 8273a90c08..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionProfileConfig.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitesubscriptionprofileconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteSubscriptionProfileConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteSubscriptionProfileConfig - -## SYNOPSIS -Deletes a site subscription from a User Profile Service application. - - -## SYNTAX - -### Default -``` -Remove-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### ServiceContext -``` -Remove-SPSiteSubscriptionProfileConfig -ServiceContext <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSiteSubscriptionProfileConfig` cmdlet deletes a site subscription from a User Profile Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------EXAMPLE----------------- -``` -$sub = Get-SPSiteSubscription https://contoso/my -$pr = Get-SPServiceApplicationProxy | ?{$_.DisplayName.Contains(PartitionedUserProfileApplication_Proxy)} -Remove-SPSiteSubscriptionProfileConfig -Identity $sub -ProfileServiceApplicationProxy $pr -``` - -This example removes tenant data. - - -## PARAMETERS - -### -Identity -Specifies the proxy of the User Profile Service application that contains the site subscription to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application proxy (for example, UserProfileSvcProxy1); or an instance of a valid SPServiceApplicationProxy object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Name of the proxy of the User Profile Service application. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context for the User Profile service application to connect to. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: ServiceContext -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionSettings.md deleted file mode 100644 index cd38a72e03..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteSubscriptionSettings.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsitesubscriptionsettings -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteSubscriptionSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteSubscriptionSettings - -## SYNOPSIS -Removes the settings service data for a specified site subscription, or finds and removes orphaned data. - - -## SYNTAX - -### FindAllOrphans -``` -Remove-SPSiteSubscriptionSettings [-Identity] <SPServiceApplicationPipeBind> [-FindAllOrphans] - [-AlternativeSiteSubscriptions <Guid[]>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] - [-WhatIf] [<CommonParameters>] -``` - -### SpecifySiteSubscriptions -``` -Remove-SPSiteSubscriptionSettings [-Identity] <SPServiceApplicationPipeBind> -SiteSubscriptions <Guid[]> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Remove-SPSiteSubscriptionSettings` cmdlet deletes site subscription stored data for the specified site subscription. -If the FindAllOrphans parameter is specified, this cmdlet locates any data in the service application that does not exist in the list of local site subscriptions or the alternate list of subscriptions. - -The set of site subscriptions can be specified directly, or discovered by comparing data in the service application to the set of existing site subscriptions which finds the data set that corresponds to nonexistent site subscriptions. - -If this cmdlet is run on a federated service application without specifying the complete list of site subscription IDs for the AlternativeSiteSubscriptions parameter, data loss can result. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------EXAMPLE 1-------------- -``` -Remove-SPSiteSubscriptionSettings -FindAllOrphans -Whatif -``` - -This example finds all orphans and displays them on the screen. -Remove the WhatIf parameter to remove these extra settings. - - -### ------------EXAMPLE 2-------------- -``` -Remove-SPSubscriptionSettingsServiceApplication -FindAllOrphans -AlternativeSiteSubscriptions $SubscriptionList -``` - -Use this example if the service application is consumed by a remote farm and you want the clean orphaned site subscription settings data (an array of all site subscriptions whose data must remain in the service application is assigned to the $SubscriptionList variable. - - -## PARAMETERS - -### -Identity -Specifies the site subscription settings service application that contains the service data to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubscriptionSettingsApp1); or an instance of a valid SPSubscriptionSettingsServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -FindAllOrphans -Specifies that orphaned settings stores in the service application are deleted. - -```yaml -Type: SwitchParameter -Parameter Sets: FindAllOrphans -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscriptions -Specifies the site subscriptions with the settings service data to delete. - -The type must be an array of valid GUIDs. - -```yaml -Type: Guid[] -Parameter Sets: SpecifySiteSubscriptions -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AlternativeSiteSubscriptions -Specifies the complete collection or comma-separated list of site subscriptions that should exist in the settings service application. -Any data not matching the items in this list will be removed. - -This parameter is important when the FindAllOrphans parameter is used. -The value specified for AlternativeSiteSubscriptions parameter is stating that any site subscriptions not on the local farm will be deleted, unless an alternate list of site subscriptions is given. - -The type must be an array of valid GUIDs. - -```yaml -Type: Guid[] -Parameter Sets: FindAllOrphans -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Automatically bypasses the secondary warning provided by the cmdlet prior to the operation. - -```yaml -Type: SwitchParameter -Parameter Sets: FindAllOrphans -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteURL.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteURL.md deleted file mode 100644 index 2f73029612..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteURL.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsiteurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteURL -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteURL - -## SYNOPSIS -Removes an URL mapping from the site. - - -## SYNTAX - -``` -Remove-SPSiteURL [-Url] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSiteUrl` cmdlet removes an URL mapping from the site. - -The `Remove-SPSiteUrl` cmdlet only applies to the root site collection for a host name, that is, https://www.contoso.com. -This cmdlet cannot be directly run against a managed path site collection underneath the root, that is, https://www.contoso.com/sites/test. - -You cannot remove the primary URL for a given site collection, which is typically defined as the first URL in the default zone. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Remove-SPSiteURL -Url https://contoso.sharepoint.com -``` - -This example removes the URL from the site collection, https://contoso.sharepoint.com. - - -## PARAMETERS - -### -Url -Specifies the URL to remove. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPSiteUrl](Get-SPSiteUrl.md) - -[Set-SPSiteUrl](Set-SPSiteUrl.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteUpgradeSessionInfo.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteUpgradeSessionInfo.md deleted file mode 100644 index 7dd19b0502..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSiteUpgradeSessionInfo.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsiteupgradesessioninfo -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSiteUpgradeSessionInfo -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSiteUpgradeSessionInfo - -## SYNOPSIS -Removes an SPSite object from upgrade. - - -## SYNTAX - -``` -Remove-SPSiteUpgradeSessionInfo [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPSiteUpgradeSessionInfo` cmdlet to remove an SPSite object from the upgrade queue. - -If the site is not in the upgrade queue, the returned value is Null. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------EXAMPLE------------- -``` -Get-SPSite | Remove-SPSiteUpgradeSessionInfo -``` - -This example removes the SPSite objects from the farm. - - -## PARAMETERS - -### -Identity -Specifies the site from which to remove the site collections. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPSiteUpgradeSessionInfo](Get-SPSiteUpgradeSessionInfo.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSocialItemByDate.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSocialItemByDate.md deleted file mode 100644 index ef81f6b6a5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSocialItemByDate.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsocialitembydate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSocialItemByDate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSocialItemByDate - -## SYNOPSIS -Deletes tags, notes, or ratings. - - -## SYNTAX - -``` -Remove-SPSocialItemByDate -EndDate <DateTime> - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-RemoveComments <Boolean>] - [-RemoveRatings <Boolean>] [-RemoveTags <Boolean>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPSocialItemByDate` cmdlet to delete, tags, notes, ratings created before a particular date. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Remove-SPSocialItemByDate -RemoveTags 1 -ProfileServiceApplicationProxy c6681d53-e6c4-432f-9f31-22d3de81b00c -EndDate 9/15/2009 -``` - -This example removes tags before 9/15/09 from the specified User Profile Service Application Proxy. - - -## PARAMETERS - -### -EndDate -Specifies the date before which data is to be deleted. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the unique identifier for the proxy. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveComments -When this parameter is specified, comments will be removed. - -Valid values for this parameter are: - --- $True --- $False - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveRatings -When this parameter is specified, ratings will be removed. - -Valid values for this parameter are: - ---$True ---$False - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveTags -When this parameter is specified, tags will be removed. - -Valid values for this parameter are: - ---$True ---$False - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSolution.md deleted file mode 100644 index a0e253f04a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSolution.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSolution - -## SYNOPSIS -Removes a SharePoint solution from a farm. - - -## SYNTAX - -``` -Remove-SPSolution [-Identity] <SPSolutionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Force] [-Language <UInt32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSolution` cmdlet deletes a SharePoint solution from a farm. -Before you use this cmdlet, you must use the `Uninstall-SPSolution` cmdlet to retract the solution files from the front-end Web server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPSolution -Identity contoso_solution.wsp -``` - -This example removes the SharePoint solution contoso_solution.wsp. - - -## PARAMETERS - -### -Identity -Specifies the SharePoint solution to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint solution (for example, SPSolution1); or an instance of a valid SPSolution object. - -```yaml -Type: SPSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces the removal of the SharePoint solution. -You can use this parameter to remove SharePoint solutions that have been added to the server, even if they have not been deployed by using the `Install-SPSolution` cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Removes the language pack for the specified language. - -The type must be a valid language identifier; for example, 1033. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSolutionDeploymentLock.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSolutionDeploymentLock.md deleted file mode 100644 index 226f63407f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPSolutionDeploymentLock.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spsolutiondeploymentlock -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPSolutionDeploymentLock -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPSolutionDeploymentLock - -## SYNOPSIS -Removes the solution deployment lock for a server. - - -## SYNTAX - -``` -Remove-SPSolutionDeploymentLock [[-Identity] <SPServerPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPSolutionDeploymentLock` cmdlet removes the solution deployment lock for a server. -If the Identity parameter is not specified, this cmdlet removes the solution deployment lock for all servers in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPSolutionDeploymentLock -``` - -This example removes the solution deployment lock for all servers in the farm. - - -## PARAMETERS - -### -Identity -Specifies the server for which the solution deployment lock is to be removed. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; the IP address of a server computer, in the form 208.77.188.166; a valid name of a SQL Server host service (for example, SQLServerHost1); or an instance of a valid SPServer object. - -```yaml -Type: SPServerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPStateServiceDatabase.md deleted file mode 100644 index 4ea7336e4d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPStateServiceDatabase.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPStateServiceDatabase - -## SYNOPSIS -Removes a state service database from a state service application and drops it from the SQL Server. - - -## SYNTAX - -``` -Remove-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPStateServiceDatabase` cmdlet removes a state service database from a state service application and deletes the database. -To remove a state service database and not delete the database, use the `Dismount-SPStateServiceDatabase` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Remove-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -``` - -This example removes the specified database from a SharePoint Server farm and drops the database from the SQL Server (data loss). - - -## PARAMETERS - -### -Identity -Specifies the state service database to remove. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a state database (for example, StateSvcDB1); or an instance of a valid SPStateServiceDatabase object. - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPThrottlingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPThrottlingRule.md deleted file mode 100644 index 734104bc8c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPThrottlingRule.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spthrottlingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPThrottlingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPThrottlingRule - -## SYNOPSIS -Removes a throttling rule. - - -## SYNTAX - -``` -Remove-SPThrottlingRule [-Identity] <SPThrottlingRulePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPThrottlingRule` cmdlet to remove a throttling rule from the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -C:\PS>$c=New-SPRequestManagementRuleCriteria -Value http -Property url -MatchType startswith -CaseSensitive $false - -C:\PS>$throttlingrule=Add-SPThrottlingRule -RequestManagementSettings $rm -Name <Rule Name> -Criteria $c -Threshold 4 - -Remove-SPThrottlingRule -Identity $throttlingrule -``` - -This example removes a throttling rule for a specified identity by using the $throttlingrule variable. - - -## PARAMETERS - -### -Identity -Specifies the throttling rule object to remove. - -```yaml -Type: SPThrottlingRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPThrottlingRule](Add-SPThrottlingRule.md) - -[Get-SPThrottlingRule](Get-SPThrottlingRule.md) - -[Set-SPThrottlingRule](Set-SPThrottlingRule.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTranslationServiceJobHistory.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTranslationServiceJobHistory.md deleted file mode 100644 index 27c2cacc25..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTranslationServiceJobHistory.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -external help file: Microsoft.Office.TranslationServices.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sptranslationservicejobhistory -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPTranslationServiceJobHistory -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPTranslationServiceJobHistory - -## SYNOPSIS -Removes Machine Translation service jobs. - - -## SYNTAX - -``` -Remove-SPTranslationServiceJobHistory [-Identity] <TranslationServiceApplicationPipeBind> [-AllPartitions] - [-AssignmentCollection <SPAssignmentCollection>] [-BeforeDate <DateTime>] [-Confirm] [-IncludeActiveJobs] - [-JobId <Guid>] [-PartitionId <Guid>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPTranslationServiceJobHistory` cmdlet to remove a machine translation service job from the job history database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE-------------- -``` -Remove-SPTranslationServiceJobHistory TranslationService -BeforeDate 2012/01/31 -``` - -This example removes all jobs completed before 2012/01/31 in the database associated with the Machine Translation Service application named TranslationService. - - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the instance of the Machine Translation service to remove. - -The type must be a valid URL, in the form https://server_name or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: TranslationServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AllPartitions -Removes all the jobs from the database given other parameters. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BeforeDate -Specifies all expired jobs before a given date. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeActiveJobs -Specifies expired jobs which contain active translations. -By default, jobs are not deleted if a translation is active. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobId -Specifies only a job Id and its items to expire. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PartitionId -Specifies only a partition Id and its items to expire. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedIdentityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedIdentityTokenIssuer.md deleted file mode 100644 index 7db7f82cbb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedIdentityTokenIssuer.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sptrustedidentitytokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPTrustedIdentityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPTrustedIdentityTokenIssuer - -## SYNOPSIS -Deletes a Security Token Service (STS) identity provider from the farm. - - -## SYNTAX - -``` -Remove-SPTrustedIdentityTokenIssuer [-Identity] <SPTrustedIdentityTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPTrustedIdentityTokenIssuer` cmdlet deletes a Security Token service (STS) identity provider from the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE-------------------- -``` -Remove-SPTrustedIdentityTokenIssuer "LiveIDSTS" -``` - -This example removes an identity provider named LiveIDSTS from the farm. - - -## PARAMETERS - -### -Identity -Specifies the identity provider to remove. - -The type must be one of the following forms: - ---A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh ---A valid name of identity provider (for example, LiveID STS) ---An instance of a valid SPIdentityProvider object - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedRootAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedRootAuthority.md deleted file mode 100644 index d695cc6ddf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedRootAuthority.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sptrustedrootauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPTrustedRootAuthority -schema: 2.0.0 ---- - -# Remove-SPTrustedRootAuthority - -## SYNOPSIS -Deletes a trusted root authority. - - -## SYNTAX - -``` -Remove-SPTrustedRootAuthority [-Identity] <SPTrustedRootAuthorityPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPTrustedRootAuthority` cmdlet deletes a trusted root authority from a signing certificate store. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPTrustedRootAuthority -Name "WFEFarm1" -``` - -This example removes the trusted root authority WFEFarm1. - - -## PARAMETERS - -### -Identity -Specifies the trusted root authority to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a trusted root authority (for example, WFEFarm1); or an instance of a valid SPTrustedRootAuthority object. - -```yaml -Type: SPTrustedRootAuthorityPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedSecurityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedSecurityTokenIssuer.md deleted file mode 100644 index eb6fd49578..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedSecurityTokenIssuer.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sptrustedsecuritytokenissuer -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPTrustedSecurityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPTrustedSecurityTokenIssuer - -## SYNOPSIS -Removes the trusted security token service object. - - -## SYNTAX - -``` -Remove-SPTrustedSecurityTokenIssuer [-Identity] <SPTrustedSecurityTokenServicePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPTrustedSecurityTokenService` cmdlet to remove the trusted security token service object by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Remove-SPTrustedSecurityTokenService -Identity FarmA -``` - -This example removes the trusted security token issuer object named FarmA from the farm. - - -## PARAMETERS - -### -Identity -Specifies the ID of the trusted security token issuer object to be removed. - -```yaml -Type: SPTrustedSecurityTokenServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPTrustedSecurityTokenIssuer](Get-SPTrustedSecurityTokenIssuer.md) - -[New-SPTrustedSecurityTokenIssuer](New-SPTrustedSecurityTokenIssuer.md) - -[Set-SPTrustedSecurityTokenIssuer](Set-SPTrustedSecurityTokenIssuer.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedServiceTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedServiceTokenIssuer.md deleted file mode 100644 index 3714423394..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedServiceTokenIssuer.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-sptrustedservicetokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPTrustedServiceTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPTrustedServiceTokenIssuer - -## SYNOPSIS -Deletes the object that represents the farm trust. - - -## SYNTAX - -``` -Remove-SPTrustedServiceTokenIssuer [-Identity] <SPTrustedServiceTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPTrustedServiceTokenIssuer` cmdlet deletes the object that represents the farm trust. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Remove-SPTrustedServiceTokenIssuer "WFE Farm 2" -``` - -This example deletes the trusted service token issuer WFE Farm 2. - - -## PARAMETERS - -### -Identity -Specifies the trusted service token issuer to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a trusted service token issuer (for example, WFEFarm1); or an instance of a valid SPTrustedRootAuthority object. - -```yaml -Type: SPTrustedServiceTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUsageApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUsageApplication.md deleted file mode 100644 index 598b8b5b09..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUsageApplication.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spusageapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPUsageApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPUsageApplication - -## SYNOPSIS -Removes a usage application from the local farm. - - -## SYNTAX - -``` -Remove-SPUsageApplication [-Identity] <SPUsageApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-RemoveData] - [-UsageService <SPUsageServicePipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPUsageApplication` cmdlet deletes a usage application from the local farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE-------------------- -``` -Remove-SPUsageApplication -Identity "Usage and Health data collection" -RemoveData -``` - -This example removes the existing usage application and the associated logging DB. - - -## PARAMETERS - -### -Identity -Specifies the usage application to delete. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage application (for example, UsageApplication1); or an instance of a valid SPUsageApplication object. - -```yaml -Type: SPUsageApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveData -Specifies that the logging database is also removed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsageService -Reserved for future use. - -```yaml -Type: SPUsageServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUser.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUser.md deleted file mode 100644 index 53bc57200b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUser.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spuser -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPUser -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPUser - -## SYNOPSIS -Removes a user from a Web site. - - -## SYNTAX - -``` -Remove-SPUser [-Identity] <SPUserPipeBind> -Web <SPWebPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Group <SPGroupPipeBind>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPUser` cmdlet specifies the identity and user group from which a user is to be removed. -The `Remove-SPUser` cmdlet does not remove the user from Active Directory Domain Services (AD DS). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Remove-SPUser "Contoso\jdoe" -web https://test/web1 - -Get-SPWeb "https://test/web1" | Remove-SPUser "Contoso\jdoe" -``` - -This example removes the user (Contoso\jdoe) from the Web application https://test/web1. - - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPSite https://contoso.com |Get-SPWeb |Remove-SPUser "Contoso\jdoe" -``` - -This syntax removes the user (Contoso\Jdoe) from every Web in a site collection located at https://contoso.com. - - -## PARAMETERS - -### -Identity -Specifies the GUID, the user name, or SPUser object to remove. - -The type must be a valid GUID of the user, in the form 1234-5678-9876-0987. - -```yaml -Type: SPUserPipeBind -Parameter Sets: (All) -Aliases: UserAlias -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Web -Specifies the name of the URL or GUID from which the user is to be removed. -This parameter is needed only if the identity provided is the user name. - -The type must be a valid URL, in the form https://server_name, or a GUID, in the form 1234-5678-9807. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Group -The user only gets removed from that group. -Otherwise, the user gets removed from the site. - -```yaml -Type: SPGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserLicenseMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserLicenseMapping.md deleted file mode 100644 index d9c418821f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserLicenseMapping.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spuserlicensemapping -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPUserLicenseMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPUserLicenseMapping - -## SYNOPSIS -Removes a claim-to-SharePoint user license mapping. - - -## SYNTAX - -``` -Remove-SPUserLicenseMapping -Identity <System.Collections.Generic.List`1[System.Guid]> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPUserLicenseMapping` cmdlet uses the Identity parameter to remove a claim-to-SharePoint user license mapping. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------EXAMPLE--------------- -``` -Remove-SPUserLicenseMapping -Identity e69ba7cc-4be0-4723-ad63-58d06173afff -``` - -This example removes the claim-to-license mapping that has the unique ID, e69ba7cc-4be0-4723-ad63-58d06173afff. - - -## PARAMETERS - -### -Identity -Specifies the unique ID of a claim-to-license mapping. -The type must be a valid GUID (that is, e69ba7cc-4be0-4723-ad63-58d06173afff). - -```yaml -Type: System.Collections.Generic.List`1[System.Guid] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPUserLicenseMapping](Add-SPUserLicenseMapping.md) - -[Get-SPUserLicenseMapping](Get-SPUserLicenseMapping.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserSettingsProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserSettingsProvider.md deleted file mode 100644 index 7ff567c021..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserSettingsProvider.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spusersettingsprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPUserSettingsProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPUserSettingsProvider - -## SYNOPSIS -Removes a User Settings Provider. - - -## SYNTAX - -``` -Remove-SPUserSettingsProvider [-Identity] <SPUserSettingsProviderPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Remove-SPUserSettingsProvider` cmdlet to remove a User Settings Provider from the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Remove-SPUserSettingsProvider -Identity "234bf0ed-70db-4158-a332-4dfd683b4148" -``` - -This example removes a specific User Settings Provider by using the GUID, 234bf0ed-70db-4158-a332-4dfd683b4148. - - -## PARAMETERS - -### -Identity -Specifies the GUID ID for a User Settings Provider to remove. - -```yaml -Type: SPUserSettingsProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPUserSettingsProvider](Get-SPUserSettingsProvider.md) - -[New-SPUserSettingsProvider](New-SPUserSettingsProvider.md) - -[Get-SPUserSettingsProviderManager](Get-SPUserSettingsProviderManager.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserSolution.md deleted file mode 100644 index 0d951078fc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPUserSolution.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spusersolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPUserSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPUserSolution - -## SYNOPSIS -Removes a sandboxed solution from the solution gallery. - - -## SYNTAX - -``` -Remove-SPUserSolution [-Identity] <String> -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPUserSolution` cmdlet completely removes a sandboxed solution from the solution gallery. -Before you can remove the sandboxed solution from the solution gallery, you must deactivate it by using the `Uninstall-SPUserSolution` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------EXAMPLE---------------------- -``` -Remove-SPUserSolution -Identity contoso_solution.wsp -Site https://sitename -``` - -This example removes the sandboxed solution contoso_solution.wsp from the site https://sitename. - - -## PARAMETERS - -### -Identity -Specifies the sandboxed solution to remove. - -The type must be a valid name of a sandboxed solution (for example, UserSolution1); or an instance of a valid SPUserSolution object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Remove the sandboxed solution from the specified site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPVisioSafeDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPVisioSafeDataProvider.md deleted file mode 100644 index 8c79976aa0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPVisioSafeDataProvider.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spvisiosafedataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPVisioSafeDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPVisioSafeDataProvider - -## SYNOPSIS -Removes a data provider from a Visio Services application. - - -## SYNTAX - -``` -Remove-SPVisioSafeDataProvider -DataProviderId <String> -DataProviderType <Int32> - -VisioServiceApplication <SPVisioServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPVisioSafeDataProvider` cmdlet deletes the safe data provider that is specified in the DataProviderID parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE------------------------ -``` -Remove-SPVisioSafeDataProvider -VisioServiceApplication "VGS1" -DataProviderID "CustomProvider" -DataProviderType 5 -``` - -This example removes a safe data provider for a specified Visio Services application. - - -## PARAMETERS - -### -DataProviderId -Specifies the name of the data provider to delete. -The combination of DataProviderID and DataProviderType uniquely identifies a data provider for a Visio Services application. -The string that identifies the data provider can be a maximum of 255 alphanumeric characters. - -The type must be a valid string that identifies the data provider. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -DataProviderType -Specifies the supported type of the data provider to delete. - -The type must be a valid identity of a data provider type. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -VisioServiceApplication -Specifies the Visio Services application that contains the SPVisioSafeDataProvider object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWOPIBinding.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWOPIBinding.md deleted file mode 100644 index 3980221fd5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWOPIBinding.md +++ /dev/null @@ -1,291 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spwopibinding -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPWOPIBinding -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPWOPIBinding - -## SYNOPSIS -Removes bindings for applications, file name extensions and their associated actions on the current SharePoint farm where this cmdlet is run. - - -## SYNTAX - -### Identity -``` -Remove-SPWOPIBinding [[-Identity] <SPWopiBindingPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### Filter -``` -Remove-SPWOPIBinding [-Action <String>] [-Application <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Extension <String>] [-ProgId <String>] - [-Server <String>] [-WhatIf] [-WOPIZone <String>] [<CommonParameters>] -``` - -### RemoveAll -``` -Remove-SPWOPIBinding [-All] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPWOPIBinding` cmdlet removes bindings for applications, file name extensions and their associated actions on the current SharePoint farm where this cmdlet is run. -After you run this cmdlet, you can use `New-SPWOPIBinding` to re-create the bindings as needed. -If you remove all the bindings for an application, users cannot use Office Web Apps or the SharePoint Share by link feature for that application. -If you remove all the bindings on the SharePoint farm where this cmdlet is run, users cannot use Office Web Apps or the SharePoint Share by link feature for any applications in the SharePoint library. - -If you want to stop using Office Web Apps for default clicks, but must preserve the bindings' discovery information and the ability for users to use the SharePoint Share by link feature to send a link to a document and allow the recipient to use Office Web Apps for that document type, use the `New-SPWOPISuppression` cmdlet instead. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Remove-SPWOPIBinding -Application "Excel" -``` - -This example removes all bindings for Excel on the current SharePoint farm where this cmdlet is run. - - -### --------------EXAMPLE 2----------------- -``` -Remove-SPWOPIBinding -All:$true -``` - -This example removes all bindings on the current SharePoint farm where this cmdlet is run. - - -### --------------EXAMPLE 3----------------- -``` -Get-SPWOPIBinding -Action "MobileView" | Remove-SPWOPIBinding -``` - -This example removes all bindings for Office Mobile Web Apps on the current SharePoint farm where this cmdlet is run. - - -## PARAMETERS - -### -Identity -Specifies the binding. - -```yaml -Type: SPWopiBindingPipeBind -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Action -Specifies the action to remove bindings for. -For example, "view," "edit," and "embedview." For a list of actions run `Get-SPWOPIBinding`. -Most typically you will not use this parameter. -If you specify some actions but not others, some features in SharePoint may not work. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -All -Removes all bindings. - -```yaml -Type: SwitchParameter -Parameter Sets: RemoveAll -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Application -Specifies application to remove bindings for. -Possible applications are as follows: "Word," "Excel," "PowerPoint," or "OneNote." Run `Get-SPWOPIBinding` to get the list of applications. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters`. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Extension -Specifies the file name extensions to remove bindings for. -Run `Get-SPWOPIBinding` to get the list of file name extensions. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProgId -Specifies the programmatic identifier (ProgID) for an application to remove bindings for. -Run `Get-SPWOPIBinding` to get the list of ProgIDs. -You may only want to use this parameter to remove bindings for OneNote. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Server -Specifies the name of WOPI application (like Office Web Apps Server) to remove bindings for. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WOPIZone -Specifies the zone to remove bindings for. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[New-SPWOPIBinding](New-SPWOPIBinding.md) - -[Get-SPWOPIBinding](Get-SPWOPIBinding.md) - -[Set-SPWOPIBinding](Set-SPWOPIBinding.md) - -[New-SPWOPISuppressionSetting](New-SPWOPISuppressionSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWOPISuppressionSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWOPISuppressionSetting.md deleted file mode 100644 index d1472be199..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWOPISuppressionSetting.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spwopisuppressionsetting -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPWOPISuppressionSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPWOPISuppressionSetting - -## SYNOPSIS -Removes the suppression settings for a file name extension or programmatic ID and action on the current SharePoint farm where this cmdlet is run. - - -## SYNTAX - -### DocTypeAndAction -``` -Remove-SPWOPISuppressionSetting [-Action <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Extension <String>] [-ProgId <String>] [-WhatIf] [<CommonParameters>] -``` - -### Identity -``` -Remove-SPWOPISuppressionSetting [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Identity <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPWOPISuppressionSetting` cmdlet removes the suppression settings for a file name extension or programmatic indentifier (ProgID) and action on the current SharePoint farm where this cmdlet is run. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Remove-SPWOPISuppressionSetting -Extension "XLSX" -Action "view" -``` - -This example removes suppression settings for viewing Excel workbooks that have the file name extension ".xlsx." - - -### --------------EXAMPLE 2----------------- -``` -Get-SPWOPISuppressionSetting | Remove-SPWOPISuppressionSetting -``` - -This example removes all suppression settings on the current SharePoint farm where this cmdlet is run. - - -## PARAMETERS - -### -Action -Specifies the action for a given file name extension or programmatic identifier (ProgId). -For example, "view," "edit," and "embedview." - -```yaml -Type: String -Parameter Sets: DocTypeAndAction -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters`. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Extension -Specifies the file name extension. -Run `Get-SPWOPIBinding` to get the list of file name extensions the WOPI application supports. - -```yaml -Type: String -Parameter Sets: DocTypeAndAction -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies a string that represents a SPWOPISuppressionSetting. -Run `Get-SPWOPISuppressionSetting` to see examples of such strings. - -```yaml -Type: String -Parameter Sets: Identity -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ProgId -Specifies the programmatic identifier (ProgID) for an application to suppress. -Run `Get-SPWOPIBinding` to get the list of ProgIDs that the WOPI application supports. - -```yaml -Type: String -Parameter Sets: DocTypeAndAction -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[New-SPWOPISuppressionSetting](New-SPWOPISuppressionSetting.md) - -[Get-SPWOPISuppressionSetting](Get-SPWOPISuppressionSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWeb.md deleted file mode 100644 index 92bcbe48a2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWeb.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spweb -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPWeb - -## SYNOPSIS -Completely deletes the specified Web. - - -## SYNTAX - -``` -Remove-SPWeb [-Identity] <SPWebPipeBind> [-Recycle] [-CheckComplianceFlags <Boolean>] - [-AssignmentCollection <SPAssignmentCollection>] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The **Remove-SPWeb** cmdlet completely deletes the Web specified by the Identity parameter. - -Deleting the top level Web site of a site collection causes the entire site collection to be removed. - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Remove-SPWeb https://sitename/subsite -``` - -This example completely deletes a subsite. - - -## PARAMETERS - -### -Identity -Specifies the identity of the Web to delete. - -The type must be a valid full URL, in the form https://server_name/site_name, or an SPWeb object. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` -### -CheckComplianceFlags -Specifies if compliance flags are enabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Recycle -Specifies if the SPWeb object should be recycled. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWebApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWebApplication.md deleted file mode 100644 index 75991ed7ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWebApplication.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spwebapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPWebApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPWebApplication - -## SYNOPSIS -Deletes the specified Web application. - - -## SYNTAX - -### RemoveZoneOfWebApp -``` -Remove-SPWebApplication [-Identity] <SPWebApplicationPipeBind> -Zone <SPUrlZone> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DeleteIISSite] [-WhatIf] [<CommonParameters>] -``` - -### RemoveWebApp -``` -Remove-SPWebApplication [-Identity] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DeleteIISSite] [-RemoveContentDatabases] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Remove-SPWebApplication` cmdlet deletes the Web application specified by the Identity and Zone parameters. -If no zone is provided, the entire Web application and all zones are removed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Get-SPWebApplication https://sitename | Remove-SPWebApplication -Zone "Internet" -Confirm -``` - -This example prompts and then removes the Internet zone Web application extension on the Web application at https://sitename. -This command does not remove the content databases or the IIS Web site. - - -### ------------------EXAMPLE 2----------------------- -``` -Remove-SPWebApplication https://sitename -Confirm -DeleteIISSite -RemoveContentDatabases -``` - -This example permanently removes the Web application, all content databases and the IIS Web site at https://sitename - - -## PARAMETERS - -### -Identity -Specifies the URL or name of the Web application to delete. - -The type must be a valid URL, in the form https://server_name, or a valid name, in the form WebApplication-1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Zone -Specifies one of the five zones to be removed. -If this parameter is not provided, all Web application zones are removed. - -The type must be any one of the following values: Default, Intranet, Internet, Extranet, or Custom. - -```yaml -Type: SPUrlZone -Parameter Sets: RemoveZoneOfWebApp -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeleteIISSite -Deletes the associated IIS Web sites. -If this parameter is not provided, the IIS site is not removed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveContentDatabases -Permanently deletes all associated content databases. -If this parameter is not provided, no content databases are removed. - -```yaml -Type: SwitchParameter -Parameter Sets: RemoveWebApp -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWebApplicationAppDomain.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWebApplicationAppDomain.md deleted file mode 100644 index 54adb7f703..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWebApplicationAppDomain.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spwebapplicationappdomain -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPWebApplicationAppDomain -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPWebApplicationAppDomain - -## SYNOPSIS -Deletes the AppDomain. - -## SYNTAX - -``` -Remove-SPWebApplicationAppDomain [-Identity] <SPAppDomainPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Remove-SPWebApplicationAppDomain cmdlet to delete the AppDomain for a specified zone or to delete all the app domains for the web application if no zone is specified. - -This cmdlet also deletes the Internet Information Services (IIS) port binding if any was added for the WebApp/Zone combination. - -## EXAMPLES - -### ----------------------EXAMPLE 1----------------------- -``` -Remove-SPWebApplicationAppDomain -WebApplication https://www.contoso.com -``` -Removes all of the app domains for the specified web application. - -### ----------------------EXAMPLE 2----------------------- -``` -Remove-SPWebApplicationAppDomain -WebApplication https://www.contoso.com -Zone Internet -``` -Removes the app domains for the internet zone for the specified web application. - -## PARAMETERS - -### -Identity -Specifies the string of a domain name (that is, contoso.com) or a SPAppDomain object to remove. - -```yaml -Type: SPAppDomainPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.Administration.SPAppCmdlets.SPAppDomainPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPWebApplicationAppDomain](Get-SPWebApplicationAppDomain.md) - -[New-SPWebApplicationAppDomain](New-SPWebApplicationAppDomain.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWordConversionServiceJobHistory.md b/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWordConversionServiceJobHistory.md deleted file mode 100644 index 097334e5fe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Remove-SPWordConversionServiceJobHistory.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -external help file: Microsoft.Office.Word.Server.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/remove-spwordconversionservicejobhistory -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Remove-SPWordConversionServiceJobHistory -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Remove-SPWordConversionServiceJobHistory - -## SYNOPSIS -Removes entries from the Word Automation Services job history database. - - -## SYNTAX - -``` -Remove-SPWordConversionServiceJobHistory [-Identity] <WordServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-BeforeDate <DateTime>] [-Confirm] [-IncludeActiveJobs] - [-JobId <Guid>] [-SubscriptionId <Guid>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-SPWordConversionServiceJobHistory` cmdlet removes entries from the Word Automation Services job history database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------------EXAMPLE 1------------------------ -``` -Get-SPServiceApplication -Name TestWordServer | Remove-SPWordConversionServiceJobHistory -BeforeDate 1/1/2009 -``` - -This example deletes all the items in the database before 1/1/2009. - - -### ---------------------EXAMPLE 2------------------------ -``` -Get-SPServiceApplication -Name TestWordServer | Remove-SPWordConversionServiceJobHistory -JobId 00000000-0000-0112-08FF-63927635FEF1 -IncludeActiveJobs -``` - -This example deletes the job with the specified ID, even if it is still processing. - - -## PARAMETERS - -### -Identity -Specifies the Word Automation Services application to be processed. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Word Automation Services application (for example, WordSvcApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: WordServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BeforeDate -Specifies that only jobs started before this date are to be removed. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeActiveJobs -Specifies that jobs that contain active conversions can be removed. -By default, jobs that have active conversions are not removed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobId -Specifies that only the job with the specified ID is to be removed. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriptionId -Specifies that only jobs corresponding to this subscription ID are to be removed. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Rename-SPServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Rename-SPServer.md deleted file mode 100644 index 17fa96f326..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Rename-SPServer.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/rename-spserver -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Rename-SPServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Rename-SPServer - -## SYNOPSIS -Renames a server that is currently connected to the farm. - - -## SYNTAX - -``` -Rename-SPServer [-Identity] <SPServerPipeBind> -Name <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Rename-SPServer` cmdlet changes the name of the server for internal use within SharePoint Products. -The server itself must be manually renamed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Rename-SPServer -Identity "wfb1" -Name "WFE1" -``` - -This example changes the name of the SharePoint server wfb1 to WFE1. - - -## PARAMETERS - -### -Identity -Specifies the original name of the server. - -The type must be a URL, in the form https://server_name, or a GUID, in the form 1234-4567-987gb. - -```yaml -Type: SPServerPipeBind -Parameter Sets: (All) -Aliases: Address -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the new name of the server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPManagedAccountDeployment.md b/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPManagedAccountDeployment.md deleted file mode 100644 index 5333c5f899..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPManagedAccountDeployment.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/repair-spmanagedaccountdeployment -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Repair-SPManagedAccountDeployment -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Repair-SPManagedAccountDeployment - -## SYNOPSIS -Repairs the local managed account credential deployment. - - -## SYNTAX - -``` -Repair-SPManagedAccountDeployment [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Repair-SPManagedAccountDeployment` cmdlet to repair the local deployment of managed account credentials deployment on a server for the rare cases that the managed accounts service credentials are in a broken state. -It re-deploys each local service and Web applications credentials and also determines if the passphrase is not correct on the server and repairs provides warnings accordingly. -The `Repair-SPManagedAccountDeployment` cmdlet should not be used as part of the regular credential update process, but should be one of the first troubleshooting steps, specifically if a servers' services are failing to start when other servers' services are working correctly. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Repair-SPManagedAccountDeployment -``` - -This example repairs the deployment of credentials on all services and Web application associated with managed account (s) on the local server. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPProjectWebInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPProjectWebInstance.md deleted file mode 100644 index 48a42e81ce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPProjectWebInstance.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/repair-spprojectwebinstance -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Repair-SPProjectWebInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Repair-SPProjectWebInstance - -## SYNOPSIS -Re-queues specific Project Server queue items that may have fallen out of the queue. - - -## SYNTAX - -``` -Repair-SPProjectWebInstance [-Identity] <ProjectInstancePipeBind> -RepairRule <ProjectSiteHealthRuleName> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Repair-SPProjectWebInstance` cmdlet re-queues specific Project Server queue items that may have fallen out of the queue. -This includes triggers that may have been missed and queue jobs that were enqueued on a server that was subsequently removed from the farm. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Repair-SPProjectWebInstance -Identity https://contoso-appsrv/PWA -RepairRule QueueMissingTriggers -``` - -This example enqueues any missing triggers for the Project Web App instance at https://contoso-appsrv/PWA. - - -## PARAMETERS - -### -Identity -The identity of the instance of Project Web App. - -```yaml -Type: ProjectInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RepairRule -Valid values: QueueMissingTriggers searches the Project Web App for any triggers that might have been missed; QueueStaleServerGroups re-queues any jobs that were picked up by a server that was subsequently removed from the farm. - -```yaml -Type: ProjectSiteHealthRuleName -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Test-SPProjectWebInstance](Test-SPProjectWebInstance.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPSite.md deleted file mode 100644 index 5b747d13bb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Repair-SPSite.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/repair-spsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Repair-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Repair-SPSite - -## SYNOPSIS -Activates the RunRepairs method against the referenced SPSite object. - - -## SYNTAX - -``` -Repair-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-RuleId <Guid>] [-RunAlways] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Repair-SPSite` cmdlet runs one or all site collection health checks on the site collection and its contents. -This cmdlet automatically repairs issues that it finds. - -Run the `Test-SPSite` cmdlet for reports of rules which were run and a summary of the results. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------EXAMPLE 1--------------- -``` -Repair-SPSite https://<site name>/sites/testsite -``` - -This example runs all the site collection health checks in repair mode on the https://\<site name\>/sites/testsite site collection. - - -### ------------EXAMPLE 2--------------- -``` -Repair-SPSite https://<site name>/sites/testsite -Rule "ee967197-ccbe-4c00-88e4-e6fab81145e1" -``` - -This example runs just the "Missing Galleries Check" in repair mode on the https://\<site name\>/sites/testsite site collection. - - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site to run a repair. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RuleId -Specifies the specific site health rule to run instead of running all applicable rules at once. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RunAlways -Forces a rule to run even if a health check was run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Test-SPSite](Test-SPSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Request-SPUpgradeEvaluationSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Request-SPUpgradeEvaluationSite.md deleted file mode 100644 index 48820d0fcc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Request-SPUpgradeEvaluationSite.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/request-spupgradeevaluationsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Request-SPUpgradeEvaluationSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Request-SPUpgradeEvaluationSite - -## SYNOPSIS -Requests an upgrade evaluation site for a specified site. - - -## SYNTAX - -``` -Request-SPUpgradeEvaluationSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Email] [-NoUpgrade] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Request-SPUpgradeEvaluationSite` cmdlet to initiate a request to create temporary copy of a site collection at an auto-generated URL and upgrade the site collection to a newer experience. -Users can view the site to see how their site will work in the new experience. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -$site=Get-SPSite https://contoso.com/sites/TeamSite1 -Request-SPUpgradeEvaluationSite $site -NoUpgrade -Email -``` - -This example requests an upgrade evaluation site the specified contoso.com team site. - - -## PARAMETERS - -### -Identity -Specifies the SPSite object for the new upgrade evaluation site collection. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Email -Specifies not to send the requester and site collection administrators a notification email when the upgrade evaluation site is ready. -The default value is not to send an email message. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoUpgrade -Specifies not to perform an upgrade as part of the process that creates the upgrade evaluation site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPAccessServicesDatabasePassword.md b/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPAccessServicesDatabasePassword.md deleted file mode 100644 index 207af932dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPAccessServicesDatabasePassword.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/reset-spaccessservicesdatabasepassword -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Reset-SPAccessServicesDatabasePassword -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Reset-SPAccessServicesDatabasePassword - -## SYNOPSIS -Resets the specified Access Services Database password with a randomly generated password. - -## SYNTAX - -``` -Reset-SPAccessServicesDatabasePassword [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] -Database <AccessServicesDatabasePipeBind> - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Resets the specified Access Services Database password with a randomly generated password. - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -$contentdb = Get-SPContentDatabase ContentDbName -$db = Get-SPAccessServicesDatabase -ContentDb $contentdb -EA 0 | select -First 1 -Reset-SPAccessServicesDatabasePassword -Database $db -ServiceContext http://site_url -``` - -Resets the database password for the specified Access Database. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -The specified Access Services database. - -```yaml -Type: AccessServicesDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context for the local Access Services application to connect to. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Access.Services.PowerShell.AccessServicesDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectEventServiceSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectEventServiceSettings.md deleted file mode 100644 index 1af3d02ff5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectEventServiceSettings.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/reset-spprojecteventservicesettings -applicable: Project Server 2016, Project Server 2019 -title: Reset-SPProjectEventServiceSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Reset-SPProjectEventServiceSettings - -## SYNOPSIS -Resets the Microsoft Project Server Events Service 2016 settings to the default values. The Microsoft Project Server Events Service 2016 needs to be restarted for the changes to take effect. - - -## SYNTAX - -``` -Reset-SPProjectEventServiceSettings [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Resets the Microsoft Project Server Events Service 2016 settings to the default values. The Microsoft Project Server Events Service 2016 needs to be restarted for the changes to take effect. - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Reset-SPProjectEventServiceSettings -``` - -Resets the Microsoft Project Server Events Service 2016 settings to the default values. The Microsoft Project Server Events Service 2016 needs to be restarted for the changes to take effect. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectPCSSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectPCSSettings.md deleted file mode 100644 index 305be2371b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectPCSSettings.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/reset-spprojectpcssettings -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Reset-SPProjectPCSSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Reset-SPProjectPCSSettings - -## SYNOPSIS -Resets the settings for the Project Calculation Engine on Project Server. - - -## SYNTAX - -``` -Reset-SPProjectPCSSettings [-ServiceApplication <PsiServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Reset-SPProjectPCSSettings` cmdlet lets you reset the settings that control the operations of the Project Calculation Engine on Project Server. -The cmdlet requires you to identify the Project Server service application. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Project Application Services'} -Reset-SPProjectPCSSettings -ServiceApplication $sa -``` - -This cmdlet resets the settings for the Project Calculation Engine that is running on a Project Server Service Application. - - -## PARAMETERS - -### -ServiceApplication -The Project Server service application for which the settings are to be read. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectQueueSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectQueueSettings.md deleted file mode 100644 index a554daaf28..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPProjectQueueSettings.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/reset-spprojectqueuesettings -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Reset-SPProjectQueueSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Reset-SPProjectQueueSettings - -## SYNOPSIS -Resets all Project Server Queue settings to their default values for a specific Project Server Service Application. - - -## SYNTAX - -``` -Reset-SPProjectQueueSettings [-ServiceApplication <PsiServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Resets all Project Server Queue settings to their default values for a specific Project Server Service Application. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Project Application Services'} -Reset-SPProjectQueueSettings -ServiceApplication $sa -``` - -This example resets the queue settings for a Project Server Service Application service application. - - -## PARAMETERS - -### -ServiceApplication -Specifies the Project Server service application to target. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name for a Project Server service application (for example, ProjectServiceApp1); or an instance of a valid PsiServiceApplication object. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -{{Fill AssignmentCollection Description}} - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPProjectQueueSettings](Set-SPProjectQueueSettings.md) - -[Get-SPProjectQueueSettings](Get-SPProjectQueueSettings.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPSites.md b/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPSites.md deleted file mode 100644 index 472e590a47..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Reset-SPSites.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/reset-spsites -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Reset-SPSites -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Reset-SPSites - -## SYNOPSIS -Synchronizes the content database with the configuration database of the farm. - -## SYNTAX - -``` -Reset-SPSites [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Reset-SPSites cmdlet synchronizes the content database with the configuration database of the farm with respect to what site collections actually exist in the content database. - -It also ensures that all site collections in the content database are registered in the configuration database and removes any site collection references in the configuration database if the site collection does not exist in the content database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference (https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -$contentdb = Get-SPContentDatabase ContentDbName -Reset-SPSites -Identity $contentDb -``` - -Synchronizes the sites in the content database named ContentDbName with the configuration database. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies a specific content database. This could either be ID or Name of the content database or a valid instance of a content database. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPContentDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Restart-SPAppInstanceJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Restart-SPAppInstanceJob.md deleted file mode 100644 index 44aeab6f20..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Restart-SPAppInstanceJob.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/restart-spappinstancejob -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Restart-SPAppInstanceJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Restart-SPAppInstanceJob - -## SYNOPSIS -Restarts an app instance. - -## SYNTAX - -``` -Restart-SPAppInstanceJob -AppInstance <SPAppInstance> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Restart-SPAppInstanceJob cmdlet to restart an app instance. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference (https://go.microsoft.com/fwlink/p/?LinkId=671715). - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -$instance = Get-SPAppInstance -Web https://site_url | ?{$_.Title -eq 'Contoso App'} -Restart-SPAppInstanceJob -AppInstance $instance -``` - -Restarts the App Instance for the App named 'Contoso App' on https://site_url. - -## PARAMETERS - -### -AppInstance -Specifies the app instance object to restart. - -```yaml -Type: SPAppInstance -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPDeletedSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPDeletedSite.md deleted file mode 100644 index ea69c9d48a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPDeletedSite.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/restore-spdeletedsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Restore-SPDeletedSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Restore-SPDeletedSite - -## SYNOPSIS -Restores a deleted site collection. - - -## SYNTAX - -``` -Restore-SPDeletedSite [-Identity] <SPDeletedSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-ContentDatabase <SPContentDatabasePipeBind>] [-WebApplication <SPWebApplicationPipeBind>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -Use the `Restore-SPDeletedSite` cmdlet to restore a previously deleted site collection. - -Unlike the `Restore-SPSite` cmdlet that uses the host name and scheme for the Identity parameter (that is, https://server_name), the value of the identity parameter for all SPDeletedSite cmdlets use a server-relative URL. -Typically, the forward slash character (/) begins the relative URL and also denotes the root site. - -For additional information about a server-relative URL or understanding general concepts about absolute and relative URLs, see Server-relative URL Property (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsite.serverrelativeurl.aspx) or Understanding Absolute and Relative URL Addresses (https://msdn.microsoft.com/en-us/library/bb208688(office.12).aspx). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE 1---------------------- -``` -$deletedSite = Get-SPDeletedSite /sites/site_name -Restore-SPDeletedSite -Identity $deletedSite -``` - -This example restores a specific deleted site collection by using the site ID. - - -## PARAMETERS - -### -Identity -Specifies the identity of the deleted site collection to be restored. -The identity can be either a valid server-relative URL in the form /sites/site_name; a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an SPDeletedSite object. - -A site collection must not already exist at the URL location to perform a restore. - -```yaml -Type: SPDeletedSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the SQL Server content database where the site collection data will be stored. -If no content database is specified, the content database with the greatest unused site collection capacity and whose database status is ready will be used. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the Web application from which to list sites. - -The type must be a valid URL in the form https://server_name; a valid GUID, for example, 12345678-90ab-cdef-1234-567890bcdefgh; or the Web application name, for example, WebApplication1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index 98d125d9bb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,328 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/restore-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Restore-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Restore-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Restores third-party backup of a search application. - - -## SYNTAX - -### Config -``` -Restore-SPEnterpriseSearchServiceApplication [-Name] <String> - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> - -AdminSearchServiceInstance <SearchServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] -DatabaseName <String> [-DatabasePassword <SecureString>] -DatabaseServer <String> - [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] [-WhatIf] [<CommonParameters>] -``` - -### Full -``` -Restore-SPEnterpriseSearchServiceApplication [-Name] <String> - -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-KeepId] [-WhatIf] -TopologyFile <String> [-DeferUpgradeActions] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. - -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -This cmdlet is used by third parties to create a search application that uses existing data. - -Some third parties back up the application data and have to restore the application later. So, the data is restored and uses the `Restore-SPEnterpriseSearchServiceApplication` cmdlet to create a new search application that uses the restored data. - -This cmdlet supports parameter sets. - -The first set of parameters is for Application Configuration Attach mode and the second set of parameters is for Search Application Attach mode. - -Application Configuration Attach mode only restores configuration data that is stored in the administration database. -However, Search Application Attach restores configuration, topology and all crawled data. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------------EXAMPLE 1----------------------- -``` -$searchInstance = Get-SPEnterpriseSearchServiceInstance -local -$applicationPool = New-SPServiceApplicationPool -Name "SearchServiceApplicationPool" -Account "domain\username" -Restore-SPEnterpriseSearchServiceApplication -Name "SearchServiceApplication" -ApplicationPool $applicationPool -AdminSearchServiceInstance $searchInstance -DatabaseName "SearchServiceApplication_Admindb" -DatabaseServer "SQLServer1" -``` - -This example uses Application Configuration Attach mode to restore configuration data. - - -### ----------------------EXAMPLE 2----------------------- -``` -$applicationPool = New-SPServiceApplicationPool -Name "SearchServiceApplicationPool" -Account "domain\username" -Restore-SPEnterpriseSearchServiceApplication -Name "SearchServiceApplication" -ApplicationPool $applicationPool -TopologyFile "C:\TopologyFile.xml" -``` - -This example uses Search Application Attach mode to restore topology data in the file that is named topology.xml. - - -## PARAMETERS - -### -Name -Specifies the new Search application name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the application pool for the query web service. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdminSearchServiceInstance -Specifies the search service instance to be used with the administration component. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: Config -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database to create for the restoring the search application. - -The type must be a valid name of a SQL Server database, for example, RestoreDB1. - -```yaml -Type: String -Parameter Sets: Config -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the name of the password for the database server on the SQL Server. - -```yaml -Type: SecureString -Parameter Sets: Config -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid SQL Server host name, for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: Config -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the account name that is specified in the Database Server parameter. - -```yaml -Type: String -Parameter Sets: Config -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Use this parameter if you want the administration database to use a failover database server. - -```yaml -Type: String -Parameter Sets: Config -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepId -Specifies if the search service application ID's from the topology .xml file should be used for the restored search service application. - -```yaml -Type: SwitchParameter -Parameter Sets: Full -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TopologyFile -Specifies the path of the .XML file that contains the application topology information. - -```yaml -Type: String -Parameter Sets: Full -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeferUpgradeActions -Prevents database schema update during restore. Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: Full -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPEnterpriseSearchServiceApplicationIndex.md b/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPEnterpriseSearchServiceApplicationIndex.md deleted file mode 100644 index 0f43bad118..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPEnterpriseSearchServiceApplicationIndex.md +++ /dev/null @@ -1,250 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/restore-spenterprisesearchserviceapplicationindex -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Restore-SPEnterpriseSearchServiceApplicationIndex -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Restore-SPEnterpriseSearchServiceApplicationIndex - -## SYNOPSIS -Restores the search index from the specified backup files. - - -## SYNTAX - -### Restore -``` -Restore-SPEnterpriseSearchServiceApplicationIndex [-SearchApplication] <SearchServiceApplication> - [-BackupFolder] <String> [-AllReplicas] [-AllowMove] [[-Retries] <Int32>] [[-RetryPauseSeconds] <Int32>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### RestoreProgress -``` -Restore-SPEnterpriseSearchServiceApplicationIndex [-SearchApplication] <SearchServiceApplication> - [-Handle] <String> [[-Retries] <Int32>] [[-RetryPauseSeconds] <Int32>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -This cmdlet will clear the complete search index for a specified search service application and replace it with the search index from the specified backup files. - -This cmdlet supports parameter sets. -The first set of parameters is for Application Configuration Attach mode and the second set of parameters is for Search Application Attach mode. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$handle = Restore-SPEnterpriseSearchServiceApplicationIndex -SearchApplication $ssa -BackupFolder "\\sample\backup\spbr0000" -Restore-SPEnterpriseSearchServiceApplicationIndex -SearchApplication $ssa -Handle $handle -``` - -This example starts a restore of the search index in the default search service application from a backup located at \\\\sample\backup\spbr0000. - - -### ------------------EXAMPLE 2------------------ -``` -$handle = Restore-SPEnterpriseSearchServiceApplicationIndex -SearchApplication $ssa -BackupFolder "\\sample\backup\spbr0000" -Restore-SPEnterpriseSearchServiceApplicationIndex -SearchApplication "Search Service Application" -Handle $handle -``` - -This example checks the status of the running job to restore of the search index in the search service application Search Service Application with the handle $handle . - - -## PARAMETERS - -### -SearchApplication -Specifies the search service application that contains the index files that should be restored. - -```yaml -Type: SearchServiceApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BackupFolder -Specifies the full file path of the backup files. - -```yaml -Type: String -Parameter Sets: Restore -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Handle -A handle returned from an initial call using Parameter set 1. - -```yaml -Type: String -Parameter Sets: RestoreProgress -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllReplicas -Specifies a switch to restore all replicas, not just the primary. - -```yaml -Type: SwitchParameter -Parameter Sets: Restore -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMove -Specifies a switch to move instead of copying files when restoring. -Moving may be faster than copying. - - -```yaml -Type: SwitchParameter -Parameter Sets: Restore -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Retries -Specifies the number of times to retry if temporary failure occurs. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetryPauseSeconds -Seconds to pause between retries if temporary failure occurs. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPFarm.md b/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPFarm.md deleted file mode 100644 index 5584c86be5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPFarm.md +++ /dev/null @@ -1,369 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/restore-spfarm -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Restore-SPFarm -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Restore-SPFarm - -## SYNOPSIS -Restores one or more items from a backup. - - -## SYNTAX - -### DefaultSet -``` -Restore-SPFarm -Directory <String> -RestoreMethod <String> [-AssignmentCollection <SPAssignmentCollection>] - [-BackupId <Guid>] [-ConfigurationOnly] [-Confirm] [-FarmCredentials <PSCredential>] [-Force] [-Item <String>] - [-NewDatabaseServer <String>] [-Percentage <Int32>] [-RestoreThreads <Int32>] [-WhatIf] [<CommonParameters>] -``` - -### ShowTree -``` -Restore-SPFarm -Directory <String> [-ShowTree] [-AssignmentCollection <SPAssignmentCollection>] - [-BackupId <Guid>] [-ConfigurationOnly] [-Confirm] [-Item <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Restore-SPFarm` cmdlet restores one or more items from a backup such as an individual database, Web application, or the entire farm. -This cmdlet can also be used to apply a farm template to the entire farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE 1----------------------- -``` -Restore-SPFarm -Directory \\file_server\share\Backup -BackupId 12345678-90ab-cdef-1234-567890abcdef -RestoreMethod new -ConfigurationOnly -``` - -This example restores the configuration settings from the backup package in the \\\\file_server\share\Backup directory to the farm. - - -### -------------------EXAMPLE 2----------------------- -``` -Restore-SPFarm -ShowTree -Directory \\file_server\share\Backup -BackupId 12345678-90ab-cdef-1234-567890abcdef -Item "Microsoft SharePoint Foundation Web Application" -Verbose -``` - -This example show which components of the farm would be restored under the Microsoft SharePoint Foundation Web Application node, but does not actually restore them. - - -### -------------------EXAMPLE 3----------------------- -``` -Restore-SPFarm -Directory C:\Backup -BackupId 12345678-90ab-cdef-1234-567890abcdef -RestoreMethod overwrite -RestoreThreads 10 -Force -``` - -This example restores a farm by using 10 threads and suppresses the overwrite warning. - - -## PARAMETERS - -### -Directory -Specifies the path where SharePoint Products stored the backup package. -If you have a computer on which SQL Server and an instance of SharePoint Products are installed, you can use local drive paths. -This includes a basic installation. -However, if SQL Server and SharePoint Products are installed on multiple computers, you must use Universal Naming Convention (UNC) share paths so that the SQL Server and SharePoint Products can read from the same location (for example, \\\\computer_name \volume\Backup). - -The type must be either of the valid paths: - -- C:\folder_name -- \\\\server_name\folder_name - -The spbr* folders are created automatically. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestoreMethod -Specifies the method of restore to perform. - -The valid values are: - -- New; Specifies a new location to restore the content and is intended to be used when restoring to a different farm. Additional prompts will be presented to specify the new settings. -- Overwrite; Restores content and settings to their original locations and is intended to be used when restoring to the same farm it was backed up from. If the Overwrite parameter is used, a confirmation prompt is displayed. If you want the confirmation prompt suppressed, use the Force parameter. - -```yaml -Type: String -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowTree -Displays which objects in the farm will be restored based on the other parameters passed to the `Restore-SPFarm` cmdlet namely the Item and ConfigurationOnly parameters. -Items that will be excluded from the restore based on the other parameters passed to the `Restore-SPFarm` cmdlet will be preceded with an asterisk (*). -Items that cannot be restored will be enclosed in square brackets (\[ \]). -A restore operation will not be performed if the ShowTree parameter is present. - -```yaml -Type: SwitchParameter -Parameter Sets: ShowTree -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BackupId -Specifies the GUID of the backup package that is to be restored. -Each backup package has a unique GUID associated with it. -The GUID can be seen by using the `Get-SPBackupHistory` cmdlet to view the backup history. -If this parameter is not specified, the most recent backup package in the path that is specified with the Directory parameter is used. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890abcdef. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ConfigurationOnly -Specifies settings only (no data) will be restored from the backup package and applied to objects on the destination farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FarmCredentials -Specifies the credentials that will be used for all components being restored. -For example, the application pool credentials for Web applications being restored. -If an application pool being restored already exists in the farm, the credentials specified by the FarmCredentials parameter is ignored when restoring that application pool. - -```yaml -Type: PSCredential -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Force -Suppresses the prompt warning that you will overwrite components when you perform an overwrite restore operation. - -```yaml -Type: SwitchParameter -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Item -Indicates the part of the backup package to be restored. -You can use the full farm path notation as displayed by the ShowTree parameter or the name of the target component in the path if it has a unique name. -If multiple items match the name, the full path must be provided. -Surround the item or path in double quotation marks if it contains a space. -If this parameter is absent, the entire backup package is restored. - -The type must be a valid item, such as: - -Farm\Microsoft SharePoint Foundation Web Application\SharePoint - 80 - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewDatabaseServer -Specifies a valid SQL Database Server name. -If specified, will be used as a default Database Server name for all databases within the restore operation. - -This parameter is only valid when restoring as new. -It is not valid for overwrite restores. - -```yaml -Type: String -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Percentage -Requests that progress updates about the restore operation be displayed in increments of that percentage. -For example, a value of 5 displays restore progress updates at every 5 percent completed, and a value of 10 displays restore progress updates at every 10 percent completed. - -Note: Progress will only be displayed in the output if the -Verbose parameter is specified. -Otherwise, you may see the progress in the restore log file. - -This percentage is not precise and the actual progress updates might be lower or higher than requested. - -For a very large database, 1 is the recommended value. - -The type must be an integer value between 1 and 100. - -The default value is 5. - -```yaml -Type: Int32 -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestoreThreads -The number of threads that should be used during the restore. - -The fewer the restore threads, the easier it is to understand the restore log. -However, the more restore threads, the more components can be restored in parallel, potentially resulting in a faster restore. - -The valid range is between 1 and 10. -The default value is 3. - -```yaml -Type: Int32 -Parameter Sets: DefaultSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPSite.md deleted file mode 100644 index fefee88554..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Restore-SPSite.md +++ /dev/null @@ -1,299 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/restore-spsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Restore-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Restore-SPSite - -## SYNOPSIS -Restores a site collection. - - -## SYNTAX - -### DatabaseFromPipebind -``` -Restore-SPSite [-Identity] <String> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-ContentDatabase <SPContentDatabasePipeBind>] [-Force] [-GradualDelete] [-HostHeaderWebApplication <String>] - [-WhatIf] [-PreserveSiteID] [<CommonParameters>] -``` - -### DatabaseParameter -``` -Restore-SPSite [-Identity] <String> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DatabaseName <String>] [-DatabaseServer <String>] [-Force] [-GradualDelete] - [-HostHeaderWebApplication <String>] [-WhatIf] [-PreserveSiteID] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Restore-SPSite` cmdlet performs a restoration of the site collection to a location specified by the Identity parameter. -A content database may only contain one copy of a site collection. -If a site collection is backed up and restored to a different URL location within the same Web application, an additional content database must be available to hold the restored copy of the site collection. - - -## EXAMPLES - -### ----------------------EXAMPLE 1---------------------- -``` -Restore-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak -``` - -This example restores a site collection from the backup file C:\Backup\site_name.bak to the site collection URL https://server_name/sites/site_name. - - -### ----------------------EXAMPLE 2---------------------- -``` -Restore-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak -Force -DatabaseServer SQLBE1 -DatabaseName SQLDB1 -``` - -This example restores a site collection backup from the backup file C:\Backup\site_name.bak, but overwrites the existing site collection at https://server_name/sites/site_name while specifying that the site collection must be stored in a specific content database. - - -### ----------------------EXAMPLE 3---------------------- -``` -Restore-SPSite https://www.example.com -Path \\file_server\share\site_name.bak -HostHeaderWebApplication https://server_name -``` - -This example restores a site collection backup from the backup file \\\\file_server\share\site_name.bak to the host-named site collection https://www.example.com on the Web application https://server_name. - - -## PARAMETERS - -### -Identity -Specifies the URL location to which the site collection is restored. - -A site collection does not have to already exist at the URL location to perform a restore. -However, you must specify a valid URL location that a site collection can be created. -If a site collection already exists at the specified URL location, you must specify the Force parameter to overwrite it. - -The type must be a valid URL, in the form https://server_name/sites/site_name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -Specifies a valid path to the location of the backup. -For example, C:\Backup\site_name.bak. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentDatabase -Specifies the SQL Server content database where the site collection data will be stored. -If no content database is specified, the content database with the greatest unused site collection capacity and whose database status is ready will be used. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: DatabaseFromPipebind -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the SQL Server content database where the site collection data will be stored. -If no content database is specified, the content database with the greatest unused site collection capacity and whose database status is ready will be used. - -The type must be a valid database name, in the form SQLDB1. - -```yaml -Type: String -Parameter Sets: DatabaseParameter -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the SQL Server containing the content database specified by the DatabaseName parameter. - -The type must be a valid database server name, in the form SQLBE1 and needs to be used in conjunction with the DatabaseName parameter. - -```yaml -Type: String -Parameter Sets: DatabaseParameter -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Specifies that the existing site collection at the URL location is to be overwritten by this restoration. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GradualDelete -Specifies that the site collection being overwritten with the Force parameter should be gradually deleted over time by a timer job instead of all at once, which reduces its impact on SharePoint Products and SQL Server performance. -This option is recommended for large site collections. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostHeaderWebApplication -A valid URL assigned to the Web application by using alternate access mapping, such as https://server_name - -Restores a site collection as a host-named site collection instead of a path-based site collection. -When the HostHeaderWebApplication parameter is present, the value of the Identity parameter is the URL of the host-named site collection and the value of the HostHeaderWebApplication parameter is the URL of the Web application that will hold the host-named site collection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreserveSiteID -Preserves the original Site ID instead of creating a new one. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index 29925cc355..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/resume-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Resume-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Resume-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Resumes a search service application that was suspended. - -## SYNTAX - -``` -Resume-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads the SearchServiceApplication object and moves it from the Paused for: External Request status to the Resumed status. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA -$ssa | Resume-SPEnterpriseSearchServiceApplication -``` - -This example obtains a reference to a search service application named MySSA and then resumes it. - -## PARAMETERS - -### -Identity -Specifies the search service application to resume. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, MyQueryServer); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPProjectWebInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPProjectWebInstance.md deleted file mode 100644 index 275718780e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPProjectWebInstance.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/resume-spprojectwebinstance -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Resume-SPProjectWebInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Resume-SPProjectWebInstance - -## SYNOPSIS -Switches the specified instance of Project Web App to read-write mode, allowing users to change data again. - -## SYNTAX - -``` -Resume-SPProjectWebInstance [-Identity] <ProjectInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Switches the specified instance of Project Web App to read-write mode, allowing users to change data again. -This cmdlet does not set the database itself to read-write. -The database must be set to read-write before you run this cmdlet, or this cmdlet will fail. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Project Application Services'} -$instance = Get-SPProjectWebInstance -ServiceApplication $sa -Resume-SPProjectWebInstance -Identity $instance -``` - -Resumes the Project Web Server Instance in the Project Web Application Service Application. - -## PARAMETERS - -### -Identity -Specifies the instance of Project Web App to be switched to read-write mode. -It can be the unique id of the instance, the URL of the Project Web App site, the site collection object that contains the Project Web App site (an SPSite), or the Project Web App instance object itself (a PSSite). - -```yaml -Type: ProjectInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Pause-SPProjectWebInstance](Pause-SPProjectWebInstance.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPStateServiceDatabase.md deleted file mode 100644 index 57e27f910a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Resume-SPStateServiceDatabase.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/resume-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Resume-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Resume-SPStateServiceDatabase - -## SYNOPSIS -Resumes a paused state service database so that new rows of data are received. - - -## SYNTAX - -``` -Resume-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Resume-SPStateServiceDatabase` cmdlet resumes a paused state service database, an operation that adds the state service database to the set of databases that can receive new data as required by SharePoint Server applications. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE------------------ -``` -$db = Get-SPStateServiceDatabase -Identity StateServceDbName -Resume-SPStateServiceDatabase -Identity $db -``` - -This example resumes a paused state service database. - - -## PARAMETERS - -### -Identity -Specifies the state service database to resume. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a state database (for example, StateSvcDB1); or an instance of a valid SPStateServiceDatabase object. - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Revoke-SPBusinessDataCatalogMetadataObject.md b/sharepoint/sharepoint-ps/sharepoint-server/Revoke-SPBusinessDataCatalogMetadataObject.md deleted file mode 100644 index d424c883fb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Revoke-SPBusinessDataCatalogMetadataObject.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/revoke-spbusinessdatacatalogmetadataobject -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Revoke-SPBusinessDataCatalogMetadataObject -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Revoke-SPBusinessDataCatalogMetadataObject - -## SYNOPSIS -Revokes a right to a principal in the specified Business Data Connectivity Metadata Store metadata object. - - -## SYNTAX - -``` -Revoke-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> -Principal <SPClaim> -Right <PSBdcRight> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SettingId <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Revoke-SPBusinessDataCatalogMetadataObject` cmdlet revokes a right granted to a principal user in the specified Business Data Connectivity Metadata Store metadata object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$claimJohn = New-SPClaimsPrincipal -Identity "CONTOSO\johndoe" -IdentityType WindowsSamAccountName -$MetadataObject = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "LobSystem" -ServiceContext http://contoso -Name "ContosoDatabase" -Revoke-SPBusinessDataCatalogMetadataObject -Identity $MetadataObject -Principal $claimJohn -Right "Execute" -``` - -This example removes the execute right from the External System with the name ContosoDatabase for the user with the identity of johndoe on the domain CONTOSO. - - -## PARAMETERS - -### -Identity -Specifies the Business Data Connectivity Metadata Store metadata object that contains the principal. - -```yaml -Type: MetadataObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Principal -Specifies the principal to whom the rights apply. - -The type must be a claim. - -```yaml -Type: SPClaim -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Right -Specifies the right to revoke the principal. - -The type must be one of the following valid PSBdcRight object types: All, Execute, Edit, SetPermissions, or SelectableInClients. - -```yaml -Type: PSBdcRight -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SettingId -Specifies the custom environment settings model slice for which to revoke the right. - -The type must be a valid string that identifies a model slice; for example, ModelSlice1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Revoke-SPObjectSecurity.md b/sharepoint/sharepoint-ps/sharepoint-server/Revoke-SPObjectSecurity.md deleted file mode 100644 index 504e8a8d39..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Revoke-SPObjectSecurity.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/revoke-spobjectsecurity -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Revoke-SPObjectSecurity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Revoke-SPObjectSecurity - -## SYNOPSIS -Removes a security principal from a SPObjectSecurity object. - - -## SYNTAX - -### RevokeOne -``` -Revoke-SPObjectSecurity [-Identity] <SPObjectSecurity> [-Principal] <SPClaim> [[-Rights] <String[]>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### RevokeAll -``` -Revoke-SPObjectSecurity [-Identity] <SPObjectSecurity> [-All] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Revoke-SPObjectSecurity` cmdlet to remove a security principal, such as a user, from a SPObjectSecurity object. -An SPObjectSecurity object is a common object that is used to represent the security access control list (ACL) of SharePoint administrative objects, in particular service applications. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251831 (https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$security = Get-SPServiceApplicationSecurity $serviceApp -Admin -Revoke-SPObjectSecurity $security "domain\user" -Set-SPServiceApplicationSecurity $serviceApp -Admin $security -``` - -This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on a service application and removes a user from that ACL. -The removed an administrator for the service application $serviceApp. - - -## PARAMETERS - -### -Identity -Specifies the SPObjectSecurity object from which the security principal is removed. -You can use the `Get-SPServiceApplicationSecurity` cmdlet to get a SPObjectSecurity object . - -```yaml -Type: SPObjectSecurity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Principal -Specifies the principal for whom the rights are removed. - -The type must a valid name a principal; for example, Full Control. - -```yaml -Type: SPClaim -Parameter Sets: RevokeOne -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Rights -Specifies the rights of the principal to revoke. - -The type must a valid array of strings that represents the rights of the principal to revoke. - -```yaml -Type: String[] -Parameter Sets: RevokeOne -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -All -Specifies that all security principals are removed from the specified SPObjectSecurity object. - -```yaml -Type: SwitchParameter -Parameter Sets: RevokeAll -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchConfiguration.md deleted file mode 100644 index 0eb1c57afa..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchConfiguration.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchconfiguration -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchConfiguration ---- - -# Set-FASTSearchConfiguration - -## SYNOPSIS -Configures the local instance of Microsoft FAST Search Server 2010 for SharePoint. - -## SYNTAX - -``` -Set-FASTSearchConfiguration [-LogFile <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet configures the local instance of FAST Search Server 2010 for SharePoint. - -FAST Search Server 2010 for SharePoint must be installed, but not running, on the local machine before you run this cmdlet. - -If you are not running this cmdlet on the admin node in the FAST Search Server 2010 for SharePoint installation, make sure that the admin node is started before you run this cmdlet. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FastSearchConfiguration -LogFile C:\log.txt -``` - -This example configures the local machine and writes the log output to C:\log.txt. - -## PARAMETERS - -### -LogFile -Specifies the full path of a file where all log messages will be written. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchIPSec.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchIPSec.md deleted file mode 100644 index 8130617e22..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchIPSec.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchipsec -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchIPSec ---- - -# Set-FASTSearchIPSec - -## SYNOPSIS -Configures local Internet Protocol security (IPsec) for Microsoft FAST Search Server 2010 for SharePoint. - -## SYNTAX - -### Create -``` -Set-FASTSearchIPSec [-Create] -Password <SecureString> -UserName <String> [-LogFile <String>] - [<CommonParameters>] -``` - -### Remove -``` -Set-FASTSearchIPSec [-Remove] [-LogFile <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet deletes or creates firewall rules to configure IP security for the local machine. - -FAST Search Server 2010 for SharePoint must be installed on the local machine before you run this cmdlet. - -If you are not running this cmdlet on the admin node in the FAST Search Server 2010 for SharePoint installation, make sure that the admin node is started before you run this cmdlet. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchIPSec -Create -UserName user1 -Password xxx -``` - -This example sets up Internet Protocol security on the local machine. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchIPSec -Remove -``` - -This example removes Internet Protocol security rules from the local machine. - -## PARAMETERS - -### -Create -Specifies that IPsec rules will be created. - -```yaml -Type: SwitchParameter -Parameter Sets: Create -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -Specifies the password of the domain user that can look up machines in the domain controller. - -```yaml -Type: SecureString -Parameter Sets: Create -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Remove -Specifies that IPsec rules will be deleted. - -```yaml -Type: SwitchParameter -Parameter Sets: Remove -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserName -Specifies the username of the domain user that can look up machines in the domain controller. - -```yaml -Type: String -Parameter Sets: Create -Aliases: User -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogFile -Specifies the full path of a file where all log messages will be written. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCategory.md deleted file mode 100644 index d8436cb821..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCategory.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchmetadatacategory -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchMetadataCategory ---- - -# Set-FASTSearchMetadataCategory - -## SYNOPSIS -Updates the settings of a crawled property category. - -## SYNTAX - -### Category -``` -Set-FASTSearchMetadataCategory -Category <Category> [-MapToContents <Boolean>] - [-DiscoverNewProperties <Boolean>] [-NewName <String>] [<CommonParameters>] -``` - -### Name -``` -Set-FASTSearchMetadataCategory -Name <String> [-MapToContents <Boolean>] [-DiscoverNewProperties <Boolean>] - [-NewName <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet changes the settings of a crawled property category. -A category is a group of crawled properties, and the properties of the category control the default behavior of the member crawled properties. - -If MapToContents is set to "true" on a crawled property category, new crawled properties added to a category are mapped to the "content" full text index. -The names of the crawled properties mapped to the "content" full text index are added to the crawledpropertynames managed property. -You can override this action by setting the crawled property's IsMappedToContents parameter to "false". - -You can call the cmdlet with either the name of the category (Name parameter), or with a category object (Category parameter). - -You can also use the cmdlet to rename a category. - -You can only map a crawled property to one category at a time. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchMetadataCategory -Name Titles -DiscoverNewProperties 1 -MapToContents 1 -``` - -With this example, all new crawled properties for the category "Titles" are automatically discovered and added to the category. -A crawled property is considered a member of the category if it has the same property set as the category. - -This example also sets MapToContents so that new crawled properties are mapped to the "content" full text index. -If you do not want a newly discovered crawled property made available through the full text index, override this action by setting the specific crawled property's IsMappedToContents parameter to false. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchMetadataCategory -Name ExtendedTitle -Newname Titles -``` - -This example changes the name of the category "ExtendedTitle" to "Titles". - -## PARAMETERS - -### -Category -Specifies the category to be changed. - -```yaml -Type: Category -Parameter Sets: Category -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Name -The name of the category to update. - -```yaml -Type: String -Parameter Sets: Name -Aliases: CategoryName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -MapToContents -If this parameter is set to true, all newly created or discovered properties (if automatic discovery is enabled) are added to the "content" full text index. - -The name of each crawled property is added to the "crawledpropertynames" managed property. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiscoverNewProperties -If this parameter is set to true, previously unknown crawled properties mapped to this category (having the same property set identifier) are created and added to the category. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewName -The new name for the category. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataCategory](Get-FASTSearchMetadataCategory.md) - -[Remove-FASTSearchMetadataCategory](Remove-FASTSearchMetadataCategory.md) - -[New-FASTSearchMetadataCategory](New-FASTSearchMetadataCategory.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCrawledProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCrawledProperty.md deleted file mode 100644 index 18252603df..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCrawledProperty.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchmetadatacrawledproperty -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchMetadataCrawledProperty ---- - -# Set-FASTSearchMetadataCrawledProperty - -## SYNOPSIS -Updates the properties of a crawled property. - -## SYNTAX - -### CrawledProperty -``` -Set-FASTSearchMetadataCrawledProperty -CrawledProperty <CrawledProperty> [-Propset <Guid>] - [-VariantType <Int32>] [-IsMappedToContents <Boolean>] [<CommonParameters>] -``` - -### Name -``` -Set-FASTSearchMetadataCrawledProperty -Name <String> [-Propset <Guid>] [-VariantType <Int32>] - [-IsMappedToContents <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet specifies if a crawled property should be automatically indexed as part of the default full text index, "content". - -When the IsMappedToContents parameter is set to "true", the crawled property is added to the default searchable index. - -To find the crawled property to update, specify a crawled property object, or the combination of name, property set, and variant type. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$description = Get-FASTSearchMetadataCrawledProperty -Name Description -$description # Before -Set-FASTSearchMetadataCrawledProperty -CrawledProperty $description -IsMappedToContents 1 -$description # After -``` - -This example automatically maps a crawled property to the full text index "content", making the content of the crawled property searchable. - -## PARAMETERS - -### -CrawledProperty -An object representing the crawled property to update. - -```yaml -Type: CrawledProperty -Parameter Sets: CrawledProperty -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Name -The name of the crawled property to update. - -```yaml -Type: String -Parameter Sets: Name -Aliases: CrawledPropertyName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Propset -The property set GUID of the crawled property which is being updated. - -The GUID controls which category the crawled property is part of. -A GUID (Global Unique Identifier) is a 128-bit integer that has a very low probability of being duplicated. -The accepted GUID format is "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" or a System.Guid object. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VariantType -An integer value specifying the variant type of the updated crawled property. - -See https://go.microsoft.com/fwlink/?LinkId=163232 (https://go.microsoft.com/fwlink/?LinkId=163232) for a list of common variant types. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsMappedToContents -This Boolean parameter specifies whether or not the content of the crawled property should be automatically mapped into the default full text index. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataCrawledProperty](New-FASTSearchMetadataCrawledProperty.md) - -[Get-FASTSearchMetadataCrawledProperty](Get-FASTSearchMetadataCrawledProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCrawledPropertyMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCrawledPropertyMapping.md deleted file mode 100644 index 7853bc21b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataCrawledPropertyMapping.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchmetadatacrawledpropertymapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchMetadataCrawledPropertyMapping ---- - -# Set-FASTSearchMetadataCrawledPropertyMapping - -## SYNOPSIS -Specifies which crawled properties map into specific managed properties. - -## SYNTAX - -### ManagedProperty -``` -Set-FASTSearchMetadataCrawledPropertyMapping - -CrawledPropertyMapping <System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Administration.Schema.CrawledProperty]> - -ManagedProperty <ManagedProperty> [<CommonParameters>] -``` - -### Name -``` -Set-FASTSearchMetadataCrawledPropertyMapping - -CrawledPropertyMapping <System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Administration.Schema.CrawledProperty]> - -Name <String> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet replaces a managed property's crawled property mappings with a set of mappings specified as a parameter (CrawledPropertyMapping). -All other existing crawled property mappings for the managed property are removed. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$title = Get-FASTSearchMetadataManagedProperty -Name title -$extendedtitle = Get-FASTSearchMetadataManagedProperty -name extendedtitle -$mappings_for_title = $title.GetCrawledPropertyMappings() -Set-FASTSearchMetadataCrawledPropertyMapping -CrawledPropertyMapping $mappings_for_title -ManagedProperty $extendedtitle -``` - -This example adds the crawled property mappings from the managed property "title" to the managed property "extendedtitle". - -The example first retrieves a list of the crawled property mappings for the managed property named "title" using the GetCrawledPropertyMappings(). -It then calls Set-FASTSearchMetadataCrawledPropertyMapping with this list as a parameter. -This replaces any existing crawled property mappings for the managed property "extendedtitle". - -## PARAMETERS - -### -CrawledPropertyMapping -The list of crawled property mappings applied to the specified managed property. -The order in the list controls which crawled property is used when multiple crawled properties exist. -The list must consist of one or more Microsoft.SharePoint.Search.Extended.Administration.Schema.CrawledPropertyImpl objects. - -```yaml -Type: System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Administration.Schema.CrawledProperty] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -An object representing a managed property. - -```yaml -Type: ManagedProperty -Parameter Sets: ManagedProperty -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Name -The name of the managed property whose crawled property mappings you are updating. - -```yaml -Type: String -Parameter Sets: Name -Aliases: ManagedPropertyName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataCrawledPropertyMapping](Get-FASTSearchMetadataCrawledPropertyMapping.md) - -[New-FASTSearchMetadataCrawledPropertyMapping](New-FASTSearchMetadataCrawledPropertyMapping.md) - -[Remove-FASTSearchMetadataCrawledPropertyMapping](Remove-FASTSearchMetadataCrawledPropertyMapping.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataFullTextIndex.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataFullTextIndex.md deleted file mode 100644 index a8b2d1dc17..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataFullTextIndex.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchmetadatafulltextindex -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchMetadataFullTextIndex ---- - -# Set-FASTSearchMetadataFullTextIndex - -## SYNOPSIS -Updates the properties of a full text index. - -## SYNTAX - -### FullTextIndex -``` -Set-FASTSearchMetadataFullTextIndex -FullTextIndex <FullTextIndex> [-Description <String>] - [-StemmingEnabled <Boolean>] [<CommonParameters>] -``` - -### Name -``` -Set-FASTSearchMetadataFullTextIndex -Name <String> [-Description <String>] [-StemmingEnabled <Boolean>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet enables/disables stemming and changes the description of a full text index. - -Stemming is the process of reducing words to their base form or expanding to all known forms to increase recall. -Whether stemming is done through reduction or expansion depends on the language in which the content is written. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchMetadataFullTextIndex -name content -description "Central content repository" -``` - -This example updates the description of the existing full text index named "content". - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchMetadataFullTextIndex -Name content -StemmingEnabled 1 -``` - -This example enables stemming on the full text index named "content". -The content of the full text index must be recrawled/re-fed for this change to take effect. - -## PARAMETERS - -### -FullTextIndex -An object representing the full text index to be updated. - -```yaml -Type: FullTextIndex -Parameter Sets: FullTextIndex -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Name -Name of the full text index to be updated. - -```yaml -Type: String -Parameter Sets: Name -Aliases: FullTextIndexName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Description -A new description to use for the full text index. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StemmingEnabled -Enables or disables stemming for this full text index. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataFullTextIndex](New-FASTSearchMetadataFullTextIndex.md) - -[Remove-FASTSearchMetadataFullTextIndex](Remove-FASTSearchMetadataFullTextIndex.md) - -[Get-FASTSearchMetadataFullTextIndex](Get-FASTSearchMetadataFullTextIndex.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataFullTextIndexMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataFullTextIndexMapping.md deleted file mode 100644 index 5769c61c80..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataFullTextIndexMapping.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchmetadatafulltextindexmapping -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchMetadataFullTextIndexMapping ---- - -# Set-FASTSearchMetadataFullTextIndexMapping - -## SYNOPSIS -Updates the importance level of an existing full text index mapping. - -## SYNTAX - -``` -Set-FASTSearchMetadataFullTextIndexMapping -Level <Int32> -Mapping <FullTextIndexMapping> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet changes the importance level of an existing full text index mapping. - -Managed properties are mapped according to an importance level. -If the number of matching documents for a query term is higher than the StopWordThreshold for the rank profile in use, the Microsoft FAST Search Server 2010 for SharePoint system retries the query while limiting the search to managed properties belonging to a higher importance level than the one previously tried. - -It repeats this process until it finds a level where the query term count is lower than StopWordThreshold. - -Importance level 1 (the first that will be used) includes all levels from 1 and up. -Importance level 2 includes all levels 2 and up. -The maximum level is 7. - -This process is called drilling. -See Set-FASTSearchMetadataRankProfile for more information about StopWordThreshold. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$content = get-fastsearchmetadatafulltextindex -name content -$sitetitle = Get-FASTSearchMetadataManagedProperty -name sitetitle -$sitetitle_fulltextindexmapping = Get-FASTSearchMetadataFullTextIndexMapping -managedproperty $sitetitle -fulltextindex $content -Set-FASTSearchMetadataFullTextIndexMapping -mapping $sitetitle_fulltextindexmapping -level 7 -``` - -This example looks up a full text index mapping for a managed property named "SiteTitle" and moves it from importance level 1 to importance level 7. - -The example first retrieves the full text index object for "content" and the managed property object for "sitetitle". -It then uses these objects to get the full text index mapping object with the Get-FASTSearchMetadataFullTextIndexMapping cmdlet. -Finally, the example calls the Set-FASTSearchMetadataFullTextIndexMapping cmdlet to update the level. - -## PARAMETERS - -### -Level -The importance level to use for this mapping. -Valid values are 1 through 7. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: ImportanceLevel, L -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mapping -The full text index object to update. - -```yaml -Type: FullTextIndexMapping -Parameter Sets: (All) -Aliases: FullTextIndexMapping, M -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataFullTextIndexMapping](New-FASTSearchMetadataFullTextIndexMapping.md) - -[Remove-FASTSearchMetadataFullTextIndexMapping](Remove-FASTSearchMetadataFullTextIndexMapping.md) - -[Get-FASTSearchMetadataFullTextIndexMapping](Get-FASTSearchMetadataFullTextIndexMapping.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataManagedProperty.md deleted file mode 100644 index 178794cd77..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataManagedProperty.md +++ /dev/null @@ -1,360 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchmetadatamanagedproperty -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchMetadataManagedProperty ---- - -# Set-FASTSearchMetadataManagedProperty - -## SYNOPSIS -Updates the features of a managed property. - -## SYNTAX - -### ManagedProperty -``` -Set-FASTSearchMetadataManagedProperty -ManagedProperty <ManagedProperty> [-Description <String>] - [-MergeCrawledProperties <Boolean>] [-Queryable <Boolean>] [-RefinementEnabled <Boolean>] - [-SortableType <Int32>] [-SummaryType <Int32>] [-StemmingEnabled <Boolean>] [-DecimalPlaces <Int32>] - [-MaxIndexSize <Int32>] [-MaxResultSize <Int32>] [-IsMapped <Boolean>] [<CommonParameters>] -``` - -### Name -``` -Set-FASTSearchMetadataManagedProperty -Name <String> [-Description <String>] - [-MergeCrawledProperties <Boolean>] [-Queryable <Boolean>] [-RefinementEnabled <Boolean>] - [-SortableType <Int32>] [-SummaryType <Int32>] [-StemmingEnabled <Boolean>] [-DecimalPlaces <Int32>] - [-MaxIndexSize <Int32>] [-MaxResultSize <Int32>] [-IsMapped <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the properties/features of an existing managed property. - -Several of these changes require that the content be recrawled/re-fed to take full effect. -If, for example, a managed property is made searchable (Queryable) it will only become searchable after the content is updated. -During the recrawl/re-feed, the new content will be searchable, while the old will not. - -For properties such as whether the managed property should have sorting enabled (SortableType), the managed property defaults to the value '0' until the content has been re-fed/recrawled. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$title = Get-FASTSearchMetadataManagedProperty -name title -Set-FASTSearchMetadataManagedProperty -ManagedProperty $title -Refinement 1 -``` - -This example enables refinement for the managed property "title". -Content must be re-fed/recrawled to populate the refinement. -Until it is populated, the refinement defaults to having no value. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$title = Get-FASTSearchMetadataManagedProperty -name title -Set-FASTSearchMetadataManagedProperty -ManagedProperty $title -Queryable 1 -``` - -This example enables searching against the "title" managed property. -A front-end application can search in the specified managed property using the syntax: "title:\<search terms\>". - -Relevancy is not calculated for such queries (unlike searches against the full text indexes), and only the quality component of the relevancy score is available. - -The content must be recrawled/re-fed for this to take effect. - -### ---------------EXAMPLE 3----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$title = Get-FASTSearchMetadataManagedProperty -name title -Set-FASTSearchMetadataManagedProperty -ManagedProperty $title -SummaryType 1 -``` - -This example changes the summary type for the managed property named "title" from dynamic to static. -A static summary type means that the entire contents of the managed property is returned as part of the item summary. - -The content must be recrawled/re-fed for this to take effect. - -## PARAMETERS - -### -ManagedProperty -The managed property object to modify. - -```yaml -Type: ManagedProperty -Parameter Sets: ManagedProperty -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Name -The name of the managed property to modify. - -```yaml -Type: String -Parameter Sets: Name -Aliases: ManagedPropertyName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Description -A text string describing the managed property's use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MergeCrawledProperties -This Boolean value controls whether or not multiple crawled properties mapped to this managed property are merged when multiple crawled properties are present in the input. - -If not set, only the first element of the first non-empty crawled property is stored in the managed property. -The one that is chosen is the crawled property that was mapped to the managed property first. - -The content must be re-fed/recrawled for this change to take effect. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Queryable -This Boolean value specifies whether or not the managed property is directly searchable on its own (and not only as part of a full text index). - -If not set, it can only be searched when included in a full text index. - -The content must be recrawled/re-fed again for this change to take effect. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RefinementEnabled -This Boolean value specifies whether or not a refiner is available for the managed property. - -Refiners group search results based on the values of individual managed properties from the complete result set of a query. -Refiners are often used to navigate the result set in the front-end application. - -After enabling refinement on a managed property, the content must be recrawled/re-fed for the change to take effect. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortableType -The sorting type of the managed property. -Valid values are: - --- 0 ("sorting disabled") specifies that the managed property is not sortable. --- 1 ("sorting enabled") specifies that the managed property is sortable. --- 2 ("latent sorting") specifies that the managed property is prepared for sorting, but must be changed to "sorting enabled" for sorting to be supported. - -In contrast to switching from "sorting disabled" to "sorting enabled", this does not require reprocessing of data. - -Setting sorting to latent on a managed property can help reduce memory resource usage, while keeping the option of enabling sorting quickly at a later date. - -If a managed property is changed from "sorting disabled" to "sorting enabled", the sort value will default to 0 for all documents that have not been recrawled/re-fed. - -Managed properties of the type datetime always have sorting enabled. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SummaryType -The type of summary to return for the managed property. -Valid values are: - --- 0 (summary disabled), no content is returned for this managed property. --- 1 (static), the full value of the managed property is returned. --- 2 (dynamic), hit highlighting is done on the content of the managed property based on the query terms, and a hit highlighted summary is returned. - -The content must be recrawled/re-fed for any change in this setting to take effect, except when disabling summary generation. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StemmingEnabled -Enables or disables stemming for the managed property. - -Stemming is the process of reducing words to their base form, or expanding to all known forms, to increase recall. -Whether stemming is done through reduction or expansion depends on the content language. - -The content must be recrawled/re-fed for this to take effect. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DecimalPlaces -This integer parameter specifies how many decimal places should be used for the managed property. - -A higher number of decimals provides a more precise result, but reduces the minimum and maximum number size that can be stored in the managed property. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxIndexSize -This integer parameter sets the maximum number of kilobytes indexed for the managed property. - -Valid values range from 0 through 2097151 (2GB). - -The measured value equals the data stored prior to indexing and is slightly larger than the effective number of kilobytes that is searchable for the managed property. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxResultSize -This integer parameter sets the maximum number of kilobytes that can be returned for this managed property. - -If a managed property's content is longer than this, then the returned version of the managed property is truncated to the specified value. - -Valid values are from 0 through 2097151 (2GB). - -If the summary type of the managed property is dynamic, then this size refers to the size of the source data used for generating the hit highlighted summary. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsMapped -This Boolean parameter specifies whether or not the managed property is mapped to support Alternate Access Mappings in SharePoint. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - -[New-FASTSearchMetadataManagedProperty](New-FASTSearchMetadataManagedProperty.md) - -[Remove-FASTSearchMetadataManagedProperty](Remove-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataRankProfile.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataRankProfile.md deleted file mode 100644 index 7d4dda80c7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataRankProfile.md +++ /dev/null @@ -1,360 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchmetadatarankprofile -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchMetadataRankProfile ---- - -# Set-FASTSearchMetadataRankProfile - -## SYNOPSIS -Reconfigures a rank profile. - -## SYNTAX - -### Name -``` -Set-FASTSearchMetadataRankProfile -Name <String> [-AuthorityWeight <Int32>] - [-FreshnessManagedPropertyReference <ManagedProperty>] [-FreshnessResolution <Int32>] - [-FreshnessWeight <Int32>] [-PositionStopWordThreshold <Int64>] [-QualityWeight <Int32>] - [-QueryAuthorityWeight <Int32>] [-RankModelName <String>] [-StopWordThreshold <Int64>] [<CommonParameters>] -``` - -### RankProfile -``` -Set-FASTSearchMetadataRankProfile -RankProfile <RankProfile> [-AuthorityWeight <Int32>] - [-FreshnessManagedPropertyReference <ManagedProperty>] [-FreshnessResolution <Int32>] - [-FreshnessWeight <Int32>] [-PositionStopWordThreshold <Int64>] [-QualityWeight <Int32>] - [-QueryAuthorityWeight <Int32>] [-RankModelName <String>] [-StopWordThreshold <Int64>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet adjusts the relevancy components of a rank profile to improve search result relevance. - -All weights are relative to each other. -If QualityWeight is 400, and AuthorityWeight is 100, this means that QualityWeight is 4 times more important than AuthorityWeight. - -After being multiplied by the weights determined in the rank profile, all relevance components are combined into a single rank score, which decides the sorting of the result set (as long as non-relevancy sorting is not specified). -All changes are effective immediately, and the content does not need to be re-fed for this to take effect. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchMetadataRankProfile -Name ExtraRankProfile -QualityWeight 100 -AuthorityWeight 200 -QueryAuthorityWeight 10 -FreshnessWeight 0 -``` - -This example changes the weights of the relevancy components on the rank profile named "ExtraRankProfile". -You can specify one or more weights to modify at a time. - -This example turns off the freshness relevancy component by setting the weight to 0, while adjusting the other components. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$processingtime = Get-FASTSearchMetadataManagedProperty -name Processingtime -Set-FASTSearchMetadataRankProfile -Name ExtraRankProfile -FreshnessManagedPropertyReference $processingtime -``` - -This example changes the "ExtraRankProfile" rank profile so that it no longer determines document freshness based on the "docdatetime" managed property. - -Instead, freshness is based on when the item was last processed (fed) into the FAST Search Server 2010 for SharePoint system. -The time the item was processed is stored in the "processingtime" managed property by default. - -### ---------------EXAMPLE 3----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchMetadataRankProfile -Name ExtraRankProfile -StopWordThreshold 100000 -``` - -This example sets the stop word threshold of the rank profile named "ExtraRankProfile" to 100000. -The stop word threshold determines if the query term is too common to be taken into account when calculating the relevancy of an item. - -Lowering the stop word threshold means that more terms may be ignored when calculating relevancy, which can have a positive impact on performance. - -### ---------------EXAMPLE 4----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$rankprofile = Get-FASTSearchMetadataRankProfile -Name default -$rankprofile.GetQualityComponents() -``` - -The quality rank metric is an importance score assigned to a document, independent of query terms. -This example lists the managed properties involved in calculating the quality rank by calling the GetQualityComponents() method call on the rank profile. - -### ---------------EXAMPLE 5----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$new_rank_component = New-FASTSearchMetadataManagedProperty -Name sitecredibility -$rankprofile = Get-FASTSearchMetadataRankProfile -Name default -$rankprofile.CreateQualityComponent($new_rank_component,100) -$rankprofile.GetQualityComponents() -``` - -The quality rank metric is an importance score assigned to a document, independent of query terms. -This example adds another managed property, named "sitecredibility", to the list of quality components which form the quality rank score. -The "sitecredibility" managed property is weighted the same as the other quality components (100). - -The next step would be to populate "sitecredibility" with a suitable crawled property. - -## PARAMETERS - -### -Name -The name of the rank profile to modify. - -```yaml -Type: String -Parameter Sets: Name -Aliases: RankProfileName, N -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -RankProfile -An object representing a rank profile. - -```yaml -Type: RankProfile -Parameter Sets: RankProfile -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AuthorityWeight -This integer parameter sets the authority weight component of the rank profile. - -Ranking on authority takes the connections between items into account when calculating a relevancy score. -Items that are central and frequently linked to receive a higher authority relevancy score than items that are hard to reach and less frequently linked to. - -The authority relevancy score is calculated regularly by the Webanalyzer component. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FreshnessManagedPropertyReference -This parameter specifies which managed properties to use when calculating freshness. - -The managed property must be represented with a ManagedPropertyImpl object (e.g., as returned from Get-FASTSearchMetadataManagedProperty). - -The managed property must be of the type "datetime" and have sorting enabled. - -The value of the managed property is used when calculating how fresh the document is. -Items with an older datetime value in the specified managed property get a lower freshness relevancy score. - -```yaml -Type: ManagedProperty -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FreshnessResolution -This integer parameter sets the size of the freshness boost tick. - -The tick is the smallest amount of time the freshness relevancy considers to be a different value. - -If set to an hour, all documents with a freshness managed property value within the same hour receive the same freshness relevancy score. - -If set to a day, documents with the same day value in the freshness managed property are considered equally fresh. - -Valid values are: - -0 (Second) - -1 (Minute) - -2 (Hour) - -3 (Day) - -4 (Year) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FreshnessWeight -This integer parameter sets the weight of the freshness relevancy component when calculating the relevance of a result. - -The freshness rank value goes down the older the document is. - -See the FreshnessManagedPropertyReference parameter to change the managed property used for calculating freshness. - -Set this value to 0 to ignore item freshness when calculating relevancy. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PositionStopWordThreshold -This integer parameter sets the position stop word threshold. - -If a query term occurs more often than position-stop-word-threshold (independent of the number of items it occurs in), then proximity relevancy calculations are not done for that term. - -If the query term count does not exceed the position stop word threshold, an extra rank score is added if query terms are positioned close to each other in the managed properties. - -If you do not want to use proximity as part of the relevancy model, set this parameter to 0 to disable proximity calculation. -This will decrease CPU use when searching. - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QualityWeight -This integer parameter sets the weight of the quality component of the relevancy model. - -Quality denotes the assigned importance of a document. -The quality metrics are assigned to individual documents without taking into account the query being evaluated. - -An excessively high quality weight makes item ranking less dependent on the user query terms, which can lead to a poor search experience, since items with a high quality relevancy score could outweigh items that are more relevant to the query terms. - -The quality relevancy score is calculated dynamically, based on one or more quality components. -The GetQualityComponents() method available on the RankProfileImpl object lists the managed properties used for this. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueryAuthorityWeight -This integer parameter sets the weight of the query authority relevancy component. - -The query authority increases for an item when a user clicks through to it from search results. -The more popular the item is for a given query, the higher the query authority relevancy score. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RankModelName -The name of a rank profile to modify. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StopWordThreshold -This integer parameter sets the stop word threshold of the rank profile. - -A stop word is a search term that is so common in the result set that it is not counted as part of the relevancy calculation. - -When a query term exceeds this threshold, FAST Search Server 2010 for SharePoint retries the query with a higher full text index importance level until it can find a level where the query term is not a stop word (see Set-FASTSearchMetadataFullTextIndexMapping for details about importance levels). - -If this is not possible, the query term is not included in the result set's relevancy. -A low StopWordThreshold value gives better search performance, but a lower result set relevancy (since there is a bigger chance that a query term does not influence which items are in the result set). - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchMetadataRankProfile](New-FASTSearchMetadataRankProfile.md) - -[Remove-FASTSearchMetadataRankProfile](Remove-FASTSearchMetadataRankProfile.md) - -[Get-FASTSearchMetadataRankProfile](Get-FASTSearchMetadataRankProfile.md) - -[Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityCCTKServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityCCTKServer.md deleted file mode 100644 index f42d680b47..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityCCTKServer.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecuritycctkserver -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityCCTKServer ---- - -# Set-FASTSearchSecurityCCTKServer - -## SYNOPSIS -Updates the CCTK server general setting. - -## SYNTAX - -``` -Set-FASTSearchSecurityCCTKServer [[-Port] <Int32>] [[-Enable] <Boolean>] - [[-GeneralSetting] <CCTKServerSetting>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the configuration information for the Content Connector Toolkit (CCTK) server general settings. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1---------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityCCTKServer -Port 13271 -Enable $true -``` - -This example updates the CCTK server port number and enables the CCTK server to accept requests. - -## PARAMETERS - -### -Port -The port number that the security manager listens to for handling CCTK requests. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -A Boolean flag to determine if the CCTK service will accept requests. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GeneralSetting -A CCTKServerSetting instance whose property values are used for the CCTKServerSetting being updated. - -```yaml -Type: CCTKServerSetting -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityCCTKServer](Get-FASTSearchSecurityCCTKServer.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityClaimsUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityClaimsUserStore.md deleted file mode 100644 index af42a5f655..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityClaimsUserStore.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecurityclaimsuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityClaimsUserStore ---- - -# Set-FASTSearchSecurityClaimsUserStore - -## SYNOPSIS -Updates a claims user store. - -## SYNTAX - -``` -Set-FASTSearchSecurityClaimsUserStore [-Identity] <String> [[-SecurityContent] <ClaimsUserStore>] - [[-Description] <String>] [[-Issuer] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the configuration settings for a claims user store. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityClaimsUserStore -Identity clm -Description "Sharepoint Users" -``` - -This example updates the description of the "clm" claims user store. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchSecurityClaimsUserStore -Identity cl2 | Set-FASTSearchSecurityClaimsUserStore -Issuer Windows -``` - -This example sets the issuer of the "cl2" claims user store to "Windows". -The Set-FASTSearchSecurityClaimsUserStore cmdlet updates the SecurityContent value piped from the Get-FASTSearchSecurityClaimsUserStore. - -## PARAMETERS - -### -Identity -The user store identity. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -SecurityContent -A claims user store object whose property values are used to update another claims user store. - -```yaml -Type: ClaimsUserStore -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Description -A brief explanation of the user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Issuer -The Microsoft SharePoint Server Security Token Service (STS) claims provider that issued the claims. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityClaimsUserStore](Get-FASTSearchSecurityClaimsUserStore.md) - -[New-FASTSearchSecurityClaimsUserStore](New-FASTSearchSecurityClaimsUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityDefaultUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityDefaultUserStore.md deleted file mode 100644 index 3c9299ce23..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityDefaultUserStore.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecuritydefaultuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityDefaultUserStore ---- - -# Set-FASTSearchSecurityDefaultUserStore - -## SYNOPSIS -Updates the default user store general setting. - -## SYNTAX - -### ProcessId -``` -Set-FASTSearchSecurityDefaultUserStore [[-DefaultUserStoreId] <String>] [<CommonParameters>] -``` - -### ProcessGeneralSetting -``` -Set-FASTSearchSecurityDefaultUserStore [[-GeneralSetting] <DefaultUserStoreSetting>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the identity of the user store that users and groups are looked up in, to determine the appropriate document access if the user store identity is not specified when looking up the user or group. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityDefaultUserStore -DefaultUserStoreId win -``` - -This example sets the default user store to "win". - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$defuserstore | Set-FASTSearchSecurityDefaultUserStore -``` - -This example updates the default user store using values from a pipeline GeneralSetting parameter. - -In this example, the $defuserstoreGeneralSetting was created with this command: $defuserstore = Get-FASTSearchSecurityDefaultUserStore. - -## PARAMETERS - -### -DefaultUserStoreId -The identity of the user store to set as the default user store. - -```yaml -Type: String -Parameter Sets: ProcessId -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GeneralSetting -A DefaultUserStoreSettinginstance whose property values are used for the DefaultUserStoreSetting being updated. - -```yaml -Type: DefaultUserStoreSetting -Parameter Sets: ProcessGeneralSetting -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityDefaultUserStore](Get-FASTSearchSecurityDefaultUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityLogLevel.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityLogLevel.md deleted file mode 100644 index 8d2db570dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityLogLevel.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecurityloglevel -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityLogLevel ---- - -# Set-FASTSearchSecurityLogLevel - -## SYNOPSIS -Updates the log level general setting. - -## SYNTAX - -``` -Set-FASTSearchSecurityLogLevel [[-GeneralSetting] <LogLevelSetting>] [-DebugNameSpaceLogLevel <String[]>] - [-DefaultLogLevel <String>] [-ErrorNameSpaceLogLevel <String[]>] [-IncludeExceptionStack <Boolean>] - [-InfoNameSpaceLogLevel <String[]>] [-WarningNameSpaceLogLevel <String[]>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the configuration information for the log level's general setting. -The log level controls the type of information that is logged by the security system. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityLogLevel -DefaultLogLevel debug -IncludeExceptionStack $True -``` - -This example sets the default log level to the "Debug" level and enables the setting to include the exception stack in the log. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityLogLevel -WarningNameSpaceLogLevel Microsoft -``` - -This example sets the log level setting for the "Microsoft" namespace to the "Warning" level. - -## PARAMETERS - -### -GeneralSetting -A LogLevelSetting whose property values are used for the LogLevelSetting being updated. - -```yaml -Type: LogLevelSetting -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DebugNameSpaceLogLevel -A list of C# namespaces. -Any class contained in that namespace logs all messages to the log. - -A class can occur in only one namespace. -If you specify the same class in more than one name space log level, the log level that generates the most messages will be set. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DefaultLogLevel -Specifies the type of log messages that each class writes to the log, unless the class is contained in a namespace explicitly specified in ErrorLogLevelNameSpaces, WarningLogLevelNameSpaces, InfoLogLevelNameSpaces, and DebugLogLevelNameSpaces. - -Valid values are: - --- Error --- Warning --- Info --- Debug - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ErrorNameSpaceLogLevel -A list of C# namespaces. -Any class included in the namespace only logs error messages. - -A class can occur in only one namespace. -If you specify the same class in more than one namespace log level, the log level that generates the most messages will be set. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IncludeExceptionStack -Whether or not to include the exception stack in the log. -Set to $True to include the exception stack. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -InfoNameSpaceLogLevel -A list of C# namespaces. -Any class contained in that namespace only logs error, warning, and info messages. - -A class can occur in only one namespace. -If you specify the same class in more than one namespace log level, the log level that generates the most messages will be set. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WarningNameSpaceLogLevel -A list of C# namespaces. -Any class included in the namespace only logs error and warning messages. - -A class can occur in only one namespace. -If you specify the same class in more one than namespace log level, the log level that generates the most messages will be set. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityLogLevel](Get-FASTSearchSecurityLogLevel.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityLotusNotesUserStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityLotusNotesUserStore.md deleted file mode 100644 index 7a4e0af921..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityLotusNotesUserStore.md +++ /dev/null @@ -1,280 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecuritylotusnotesuserstore -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityLotusNotesUserStore ---- - -# Set-FASTSearchSecurityLotusNotesUserStore - -## SYNOPSIS -Updates a Lotus Notes user store. - -## SYNTAX - -``` -Set-FASTSearchSecurityLotusNotesUserStore [-Identity] <String> [[-SecurityContent] <LotusNotesUserStore>] - [[-NonIndexableCharacterEncodingPrefix] <String>] [[-NonIndexableCharacterPattern] <String>] - [[-Description] <String>] [[-UseDenyOnDefault] <Boolean>] [[-UseDocumentSecurity] <Boolean>] - [[-UseWildcardSecurity] <Boolean>] [[-UseViewSecurity] <Boolean>] [[-AllowPrefix] <String>] - [[-DenyPrefix] <String>] [[-NonIndexableCharacterHandling] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the configuration settings for a Lotus Notes user store. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityLotusNotesUserStore -Identity ln4 -Description "My Lotus user store" -``` - -This example updates the description of the "ln4" Lotus Notes user store. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchSecurityLotusNotesUserStore -Identity ln3 | Set-FASTSearchSecurityLotusNotesUserStore -UseDocumentSecurity $false -``` - -This example sets the UseDocumentSecurity of the "ln3" Lotus Notes user store to false to skip item level security. - -In this case, only database level security is used. -The Set-FASTSearchSecurityLotusNotesUserStore command updates the SecurityContent object piped from the Get-FASTSearchSecurityLotusNotesUserStore. - -## PARAMETERS - -### -Identity -Identity of the Lotus Notes user store to update. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -SecurityContent -A Lotus Notes user store object whose property values are used for the Lotus Notes user store being updated. - -```yaml -Type: LotusNotesUserStore -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Description -A brief explanation of the user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDenyOnDefault -If true, support for default access with deny on users/groups is enabled on database level security. - -You must enable this filter for an inverse security model: first grant access to everyone, and then explicitly deny access to certain groups or users. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDocumentSecurity -If true, item security is enabled (i.e., the filter contains a item level security condition). - -If set to false, item level security is ignored; only database level security (and possibly view security) is used. - -If items always inherit the ACLs of the database, you can turn off this option. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseWildcardSecurity -If true, database access through wildcard group entry (starting with */) is enabled. - -If set to false, the wildcard check is ignored. -Only normal groups are checked against the database ACL. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseViewSecurity -If true, view security is enabled (i.e., the filter contains a view level security condition). - -If set to false, view level security is ignored; only database level security (and possibly item security) is used. - -If views always inherit the ACLs of the database, or if views are not indexed, you can turn off this option. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPrefix -A string value prepended to the document ACL to control which items the user is allowed access to and which items will be returned in the query. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 7 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DenyPrefix -A string value prepended to the ACL to control which items the user is denied access to and which items are not returned from the query. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 8 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NonIndexableCharacterHandling -Specifies what to do with ACL values that match the NonIndexableCharacterRegExPattern regular expression. - -Valid values: - --- encode - The ACL is encoded into a single searchable term. --- encodeWithPrefix - The value of NonIndexableEncodedPrefix is concatenated with the ACL to be encoded, producing a single searchable term. --- remove - The ACL is removed from both allowing and denying access. Specify "remove" if the ACL is never used to deny access. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NonIndexableCharacterEncodingPrefix -If NonIndexableCharacterHandling is set to encodeWithPrefix, this parameter specifies the prefix added to the encoded ACL. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 10 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NonIndexableCharacterPattern -Specifies a regular expression pattern used to detect non-indexable characters in an ACL. -Identities matching this regular expression pattern will be processed based on NonIndexableCharacterHandling. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 11 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityLotusNotesUserStore](Get-FASTSearchSecurityLotusNotesUserStore.md) - -[New-FASTSearchSecurityLotusNotesUserStore](New-FASTSearchSecurityLotusNotesUserStore.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityPublicFilter.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityPublicFilter.md deleted file mode 100644 index cee322ae24..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityPublicFilter.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecuritypublicfilter -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityPublicFilter ---- - -# Set-FASTSearchSecurityPublicFilter - -## SYNOPSIS -Updates the public filter general setting. - -## SYNTAX - -### ProcessFilter -``` -Set-FASTSearchSecurityPublicFilter [[-Filter] <String>] [<CommonParameters>] -``` - -### ProcessPipelineSetting -``` -Set-FASTSearchSecurityPublicFilter [[-GeneralSetting] <PublicFilterSetting>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the public filter general setting configuration. -The public filter is the search security filter that is used to find documents that all users have access to. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityPublicFilter -Filter docacl:unknown -``` - -This example updates the search security filter that is used to find documents that all users have access to. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -C:\PS>$pubfilter | Set-FASTSearchSecurityPublicFilter -``` - -This example updates the public filter setting using values from a pipeline GeneralSetting parameter. - -In this example, the $pubfilterGeneralSetting was created with this command: $pubfilter = Get-FASTSearchSecurityPublicFilter. - -## PARAMETERS - -### -Filter -The search security filter that is used to find documents that all users have access to. - -```yaml -Type: String -Parameter Sets: ProcessFilter -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GeneralSetting -A PublicFilterSetting whose property values are used for the PublicFilterSetting being updated. - -```yaml -Type: PublicFilterSetting -Parameter Sets: ProcessPipelineSetting -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: 9999 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-FASTSearchSecurityPublicFilter](Get-FASTSearchSecurityPublicFilter.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityRegexAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityRegexAliaser.md deleted file mode 100644 index 7ea95e9d52..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityRegexAliaser.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecurityregexaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityRegexAliaser ---- - -# Set-FASTSearchSecurityRegexAliaser - -## SYNOPSIS -Updates a regular expression aliaser. - -## SYNTAX - -``` -Set-FASTSearchSecurityRegexAliaser [-Identity] <String> [-CaseSensitive <Boolean>] [-InputUserStoreId <String>] - [-OutputUserStoreIds <String[]>] - [-Patterns <System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Security.Config.RegExAliasPatternMapConfig]>] - [-RegexAliaser <SecurityRegexAliaser>] [-UnicodeCaseSensitive <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the configuration settings for a regular expression aliaser to map users/groups from one user store to users/groups in other user stores, based on a regular expression pattern. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityRegexAliaser -Identity regex1 -OutputUserStoreIds ln2, ln3 -``` - -This example modifies the output user store ids for the "regex1" regular expression aliaser. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -New-FASTSearchSecurityRegexAliaserPattern -Regex .* -InputPropertyName mail -MapToUsername "\1" | Set-FASTSearchSecurityRegexAliaser -Identity regexalias1 -``` - -This example sets the regular expression pattern for the Regex Aliaser "regexalias1". -The regular expression pattern can be used to map the "mail" property of a Microsoft user store to identities in other user stores. - -## PARAMETERS - -### -Identity -The identity of the aliaser to update. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -CaseSensitive -Specifies whether the regular expressions patterns defined in the RegExAliasPatternMapConfig list are matched based on case sensitivity matching rules. -The default is true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InputUserStoreId -The identity of the mapped-from user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputUserStoreIds -A comma-separated list of mapped-to user store identities. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Patterns -List of RegExAliasPatternMapConfig instances containing the regular expression patterns using for the mapping. - -Use the New-RegExAliasPatternMapConfig cmdlet to create patterns. - -```yaml -Type: System.Collections.Generic.List`1[Microsoft.SharePoint.Search.Extended.Security.Config.RegExAliasPatternMapConfig] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RegexAliaser -A SecurityRegexAliaser object whose property values are used for the SecurityRegexAliaser aliaser being created. - -```yaml -Type: SecurityRegexAliaser -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -UnicodeCaseSensitive -Specifies whether the regular expressions patterns defined in the RegExAliasPatternMapConfig list are matched based on Unicode case sensitivity matching rules. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchSecurityRegexAliaser](New-FASTSearchSecurityRegexAliaser.md) - -[Get-FASTSearchSecurityRegexAliaser](Get-FASTSearchSecurityRegexAliaser.md) - -[New-FASTSearchSecurityRegexAliaserPattern](New-FASTSearchSecurityRegexAliaserPattern.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityXMLAliaser.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityXMLAliaser.md deleted file mode 100644 index 444df85849..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchSecurityXMLAliaser.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-fastsearchsecurityxmlaliaser -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Set-FASTSearchSecurityXMLAliaser ---- - -# Set-FASTSearchSecurityXMLAliaser - -## SYNOPSIS -Updates an XML aliaser. - -## SYNTAX - -``` -Set-FASTSearchSecurityXMLAliaser -Identity <String> [-InputPropertyName <String>] [-InputUserStoreId <String>] - [-OutputUserStoreIds <String[]>] [-PathToXMLFile <String>] [-XMLAliaser <SecurityXMLAliaser>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the configuration settings for an XML principal aliaser. - -An XML aliaser maps users/groups from one user store to users/groups in other user stores, based on an XML mapping file. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Set-FASTSearchSecurityXMLAliaser -Identity xmlalias1 -PathToXMLFile "C:\dev\temp\mapping1.xml" -``` - -This example uploads and updates the XML mapping for an XML aliaser. - -### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010) -``` -Get-FASTSearchSecurityAliaser myxmlalias | Set-FASTSearchSecurityXMLAliaser -OutputUserStoreIds ln2 -InputPropertyName '$PRINCIPAL_REFERENCE_ALIAS' -``` - -This example changes the OutputUserStoreIds and InputPropertyName for the XML aliaser piped from a Get-FASTSearchSecurityAliaser cmdlet. - -## PARAMETERS - -### -Identity -The identity of the XML aliaser to update. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -InputPropertyName -The user/group property name this regular expression pattern is matched again. - -The inputPropertyName is one of the following: - --- $PRINCIPAL_REFERENCE_ID - The identifier of the user or group. This is the default. - -Be sure to enclose in single quotes: '$PRINCIPAL_REFERENCE_ID' - --- $PRINCIPAL_REFERENCE_ALIAS - The alias of the user or group. - -Be sure to enclose in single quotes: '$PRINCIPAL_REFERENCE_NAME' - -Any other property of the user or group. -Refer to your specific user store for other properties that the user store exposes. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InputUserStoreId -The identity of the mapped-from user store. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputUserStoreIds -A comma-separated list of mapped-to user store identities. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PathToXMLFile -The absolute path to the XML mapping file to upload to the XML aliaser. - -The path must specify a file accessible to the security manager. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -XMLAliaser -A SecurityXMLAliaserobject whose property values are being updated. - -```yaml -Type: SecurityXMLAliaser -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-FASTSearchSecurityXMLAliaser](New-FASTSearchSecurityXMLAliaser.md) - -[Get-FASTSearchSecurityXMLAliaser](Get-FASTSearchSecurityXMLAliaser.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServiceApplication.md deleted file mode 100644 index 1075341cf1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServiceApplication.md +++ /dev/null @@ -1,455 +0,0 @@ ---- -external help file: microsoft.office.access.services.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spaccessserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAccessServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAccessServiceApplication - -## SYNOPSIS -Sets global properties of an existing Access Services application in SharePoint Server. - - -## SYNTAX - -``` -Set-SPAccessServiceApplication [-Identity] <SPAccessServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CacheTimeout <Int32>] [-ColumnsMax <Int32>] [-Confirm] - [-NonRemotableQueriesAllowed] [-OrderByMax <Int32>] [-OuterJoinsAllowed] [-OutputCalculatedColumnsMax <Int32>] - [-PrivateBytesMax <Int32>] [-RecordsInTableMax <Int32>] [-RequestDurationMax <Int32>] [-RowsMax <Int32>] - [-SessionMemoryMax <Int32>] [-SessionsPerAnonymousUserMax <Int32>] [-SessionsPerUserMax <Int32>] - [-SourcesMax <Int32>] [-TemplateSizeMax <Int32>] [-WhatIf] [-ApplicationLogSizeMax <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPAccessServiceApplication` cmdlet sets the global runtime properties of an existing Access Services application in SharePoint Server. -The changes made to the properties by using this cmdlet affect all machines in the farm on which this Access Services application runs. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------EXAMPLE 1------------------ -``` -Set-SPAccessServiceApplication -identity "MyAccessService" -RequestDurationMax 100 -``` - -This example sets the Access Services application named MyAccessService to let requests take up to 100 seconds before they time out. - - -### ------------EXAMPLE 2------------------ -``` -Get-SPAccessServiceApplication | Set-SPAccessServiceApplication -SessionsPerUserMax 5 -``` - -This example sets every Access Services application in the farm to allow up to five sessions per user on each back-end application server computer on which Access Services runs. - -First, every Access Services application is retrieved and then a new value is set by using the `Set-SPAccessServiceApplication` cmdlet. - - -### ------------EXAMPLE 3------------------ -``` -Get-SPAccessServiceApplication | where {$_.RowsMax -gt 50000 } | Set-SPAccessServiceApplication -RowsMax 50000 -``` - -This example sets every Access Services application in the farm that allows more than 50,000 rows to be returned from, or used in, a query and then sets the service application to allow up to 50,000 rows only. - -First, every Access Services application that has more than 50,000 rows is retrieved and then a new value is set by using the `Set-SPAccessServiceApplication` cmdlet. - - -## PARAMETERS - -### -Identity -Specifies the Access Services application to update. - -The type must be a valid name of an Access Services application; for example, AccessSrvApp1; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPAccessServiceApplication object. - -```yaml -Type: SPAccessServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheTimeout -Specifies the number of seconds that a data cache will remain active on Access services with no user activity. -Valid values include: -1, cache never times out; 1 to 2073600, cache remains active from 1 second to 24 days. - -The type must be the integers -1, or an integer in the range of 1 to 2073600 (24 days). -The default value is 300. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ColumnsMax -Specifies the maximum number of columns that a list involved in a query can contain, or that the output of the query can contain. -The default value is 30. - -The type must be an integer in the range of 1 to 255. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NonRemotableQueriesAllowed -Specifies that queries that cannot be sent remotely to the database tier can run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OrderByMax -Specifies the maximum number of Order By clauses in the query. -The default value is 4. - -The type must be an integer in the range of 1 to 8. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OuterJoinsAllowed -Specifies that left and right outer joins are supported. -Inner joins are always supported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutputCalculatedColumnsMax -Specifies the maximum number of calculated columns that can be included in the output as a part of the query. -Calculated columns in the underlying SharePoint list are not included. -The default value is 10. - -The type must be an integer in the range of 1 to 32. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateBytesMax -Specifies the maximum private bytes in megabytes that can be used by Access Services. -When set to -1 it defaults to 75 percent of physical memory on the machine. -Valid values: -1, no limit, from 1 to any positive integer.The default value is -1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecordsInTableMax -Specifies the maximum number of records allowed for a table in the Access Services application. -Valid values include: -1, no limit, and 1 to any positive integer. -The default value is 500000. - -The type must be the integer -1, or an integer in the range of 1 to MaxInt. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestDurationMax -Specifies the maximum number of seconds that a request to perform an operation can use before the request times out. -Valid values include: -1, no limit, 1 to 2073600, cache remains active 1 second to 24 days. -The default value is 30. - -The type must be the integer -1, or an integer in the range of 1 to 2073600 (24 days) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RowsMax -Specifies the maximum number of rows that a list involved in a query can have, or that the output of the query can have. -The default value is 50000. - -The type must be an integer in the range of 1 to 200000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionMemoryMax -Specifies the maximum allowable size, in megabytes, of an individual session. -Valid values include: 0, disable property, 1 to 4095. -The default value is 64. - -The type must be the integer 0, or an integer in the range of 1 to 4095. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerAnonymousUserMax -The maximum number of sessions allowed per user. -If this maximum is reached, the oldest session will be deleted when a new session is started. -Valid values include: -1, no limit, and 1 to any positive integer. -The default value is 10. - -The integer -1, or an integer in the range of 1 to MaxInt - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerUserMax -Specifies the maximum number of sessions allowed per user. -If this maximum is reached, the oldest session will be deleted when a new session is started. -Valid values include: -1, no limit, and 1 to any positive integer. -The default value is 10. - -The integer -1, or an integer in the range of 1 to MaxInt. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcesMax -Specifies the maximum number of lists that may be used as input to a query at one time. -The default value is 8. - -The type must be an integer in the range of 1 to 20. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TemplateSizeMax -The maximum allowable size in megabytes (MB) allowed for Access templates (.accdt files) uploaded into the solution gallery. -Valid values: -1, no limit, from 1 to any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationLogSizeMax -The maximum number of records for an Access Services Application Log list. Valid valies: -1 to maxint. A value of zero means none is allowed. The default value is 3000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesApplication.md deleted file mode 100644 index 9a3cacd13b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesApplication.md +++ /dev/null @@ -1,230 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spaccessservicesapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAccessServicesApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAccessServicesApplication - -## SYNOPSIS -Sets the properties of a Access Services service application. - - -## SYNTAX - -``` -Set-SPAccessServicesApplication [-Identity] <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CacheTimeout <Int32>] [-Confirm] [-PrivateBytesMax <Int32>] - [-RecoveryPointObjective <Int32>] [-RequestDurationMax <Int32>] [-SessionsPerAnonymousUserMax <Int32>] - [-SessionsPerUserMax <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAccessServicesApplication` cmdlet to set the properties of an Access Services service application. - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$sa = Get-SPAccessServicesApplication -Set-SPAccessServicesApplication -Identity $sa -SessionsPerUserMax 50 -``` - -Sets the maximum number of sessions per user to 50. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheTimeout -Sets the cache timeout value in seconds. The default is 300. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the Access Service service application to update. - -The type must be a valid GUID or the name of a valid managed metadata service application. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -PrivateBytesMax - -Sets the maximum private bytes that can be used by Access Services. The default value is -1 (no limit). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecoveryPointObjective - -Not used. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestDurationMax -Sets the timeout value for requests in seconds. Default is 30. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerAnonymousUserMax -Sets the number of sessions per anonymous user. The default is 25. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerUserMax -Sets the number of sessions per user. The default is 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesDatabaseServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesDatabaseServer.md deleted file mode 100644 index b103700b52..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesDatabaseServer.md +++ /dev/null @@ -1,410 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spaccessservicesdatabaseserver -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAccessServicesDatabaseServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAccessServicesDatabaseServer - -## SYNOPSIS -Sets parameters associated with a database server hosting Access Services databases. - - -## SYNTAX - -### SetAvailableForCreateParameterSet -``` -Set-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] -AvailableForCreate <Boolean> [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> [-Exclusive <Boolean>] [-WhatIf] - [<CommonParameters>] -``` - -### SetCredentialsParameterSet -``` -Set-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> [-DatabaseServerCredentials <PSCredential>] - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> [-DatabaseServerName <String>] [-WhatIf] - [<CommonParameters>] -``` - -### SetEncryptParameterSet -``` -Set-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> -Encrypt <Boolean> - -TrustServerCertificate <Boolean> [-WhatIf] [<CommonParameters>] -``` - -### SetFailoverParameterSet -``` -Set-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> -Failover <Boolean> [-WhatIf] - [<CommonParameters>] -``` - -### SetSecondaryDatabaseServerNameParameterSet -``` -Set-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> [-SecondaryDatabaseServerName <String>] - [-WhatIf] [<CommonParameters>] -``` - -### SetUserDomainParameterSet -``` -Set-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> -UserDomain <String> [-WhatIf] - [<CommonParameters>] -``` - -### SetServerStateParameterSet -``` -Set-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -DatabaseServer <AccessServicesDatabaseServerPipeBind> - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> -State <DatabaseServerStates> - -StateOwner <ServerStateOwner> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Sets parameters associated with a database server hosting Access Services databases allowing you to control database creation, credentials, and failover database servers. - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$site = (Get-SPWebApplication -IncludeCentralAdministration | ?{$_.IsAdministrationWebApplication -eq $true}).Sites[0] -$dbsvr = (Get-SPAccessServicesDatabaseServer -ServiceContext $site -DatabaseServerGroup DEFAULT)[0] -Set-SPAccessServicesDatabaseServer -ServiceContext $site -DatabaseServerGroup DEFAULT -DatabaseServer $dbsvr -Exclusive $true -AvailableForCreate $false -``` -Sets the first database in the database server group named DEFAULT to exclusive mode and disallowing creation of new Access Services database on the selected database server. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AvailableForCreate -Indicates whether new Access Services databases can be created on the specified SQL Server. - -```yaml -Type: Boolean -Parameter Sets: SetAvailableForCreateParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the SQL Server hosting Access Services databases. - -```yaml -Type: AccessServicesDatabaseServerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerCredentials -Specifies the Credential object for the database user. Use this parameter if you use SQL Server Authentication. If no database credentials are provided, Windows authentication is used. - -```yaml -Type: PSCredential -Parameter Sets: SetCredentialsParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerGroup -The name of the Access Services database server group containing the SQL Server object to set. - -```yaml -Type: AccessServicesDatabaseServerGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerName -Specifies the database server hosting Access Services databases. - -```yaml -Type: String -Parameter Sets: SetCredentialsParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Encrypt -Encrypts the database server connection. - -```yaml -Type: Boolean -Parameter Sets: SetEncryptParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Exclusive -Sets the database server to exclusive mode. No further Access Services databases are allowed to be created on the database server. - -```yaml -Type: Boolean -Parameter Sets: SetAvailableForCreateParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Failover -Enables or disables failover for the Access Services database server. - -```yaml -Type: Boolean -Parameter Sets: SetFailoverParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryDatabaseServerName -Specifies the failover database server name. - -```yaml -Type: String -Parameter Sets: SetSecondaryDatabaseServerNameParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object. An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -TrustServerCertificate -Sets a value that indicates whether the channel will be encrypted while bypassing walking the certificate chain to validate trust. - -```yaml -Type: Boolean -Parameter Sets: SetEncryptParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserDomain -Sets the user domain for the specified database server. - -```yaml -Type: String -Parameter Sets: SetUserDomainParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State -Sets the database server state. -Valid values: - - -- Active - -- Locked - -- Reserved - -```yaml -Type: DatabaseServerStates -Parameter Sets: SetServerStateParameterSet -Aliases: -Accepted values: Active, Locked, Reserved -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOwner -Sets the state owner. - -Valid values: - -- NoOwner - -- TenantMove - -```yaml -Type: ServerStateOwner -Parameter Sets: SetServerStateParameterSet -Aliases: -Accepted values: NoOwner, TenantMove -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesDatabaseServerGroupMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesDatabaseServerGroupMapping.md deleted file mode 100644 index 5ffb5c9075..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAccessServicesDatabaseServerGroupMapping.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -external help file: microsoft.office.access.server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spaccessservicesdatabaseservergroupmapping -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAccessServicesDatabaseServerGroupMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAccessServicesDatabaseServerGroupMapping - -## SYNOPSIS -Sets or creates the Access Services database server group mapping. - - -## SYNTAX - -### ClearDatabaseServerGroupMappingParameterSetName -``` -Set-SPAccessServicesDatabaseServerGroupMapping [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-ClearMapping] [-Confirm] [-CorporateCatalog] - [-DeveloperSite] [-ObjectModel] [-RemoteObjectModel] [-StoreFront] [-WhatIf] [<CommonParameters>] -``` - -### SetDatabaseServerGroupMappingParameter -``` -Set-SPAccessServicesDatabaseServerGroupMapping [-ServiceContext] <SPServiceContextPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-CorporateCatalog] - -DatabaseServerGroup <AccessServicesDatabaseServerGroupPipeBind> [-DeveloperSite] [-ObjectModel] - [-RemoteObjectModel] [-StoreFront] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet allows you to set the database server group to package source mapping. - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -$site = (Get-SPWebApplication -IncludeCentralAdministration | ?{$_.IsAdministrationWebApplication -eq $true}).Sites[0] -Set-SPAccessServicesDatabaseServerGroupMapping -ServiceContext $site -DatabaseServiceGroup GROUP2 -``` -Creates an Access Services database group named GROUP2. - -### --------------------EXAMPLE 1--------------------- -``` -$site = (Get-SPWebApplication -IncludeCentralAdministration | ?{$_.IsAdministrationWebApplication -eq $true}).Sites[0] -Set-SPAccessServicesDatabaseServerGroupMapping -ServiceContext $site -DatabaseServiceGroup GROUP2 -CorporateCatalog -``` - -Sets the database group named GROUP2 associating the group with packages from the corporate catalog. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClearMapping -Clears the database group mapping. - -```yaml -Type: SwitchParameter -Parameter Sets: ClearDatabaseServerGroupMappingParameterSetName -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CorporateCatalog -Associates the database server group with packages uploaded to the corporate catalog (SharePoint Add-ins). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServerGroup -The name of the database server group to set or create. - -```yaml -Type: AccessServicesDatabaseServerGroupPipeBind -Parameter Sets: SetDatabaseServerGroupMappingParameter -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeveloperSite -Associates the database server group with packages that came from the Developer Site. A Developer Site is one type of SharePoint template, intended as a site for developers to build, test and publish Office Add-ins. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ObjectModel -Associates the database server group with packages uploaded via the server-side object model. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteObjectModel -Associates the database server group with packages that are uploaded via the client-side object model. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object. An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -StoreFront -Associates the SharePoint Marketplace with the database server group. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceContextPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAlternateURL.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAlternateURL.md deleted file mode 100644 index 670bf90d76..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAlternateURL.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spalternateurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAlternateURL -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAlternateURL - -## SYNOPSIS -Configures the specified alternate URL. - - -## SYNTAX - -``` -Set-SPAlternateURL [-Identity] <SPAlternateUrlPipeBind> [-Url <String>] [-Zone <SPUrlZone>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPAlternateUrl` cmdlet changes the URL or zone of the alternate URL specified by the Identity parameter. -This cmdlet can be used to change only the zone of internal URLs and cannot be used to change the zone of public URLs. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Set-SPAlternateURL -Identity https://www.contoso.com -Zone "Internet" -``` - -This example changes the zone of the alternate URL https://www.contoso.com. - - -### ------------------EXAMPLE 2------------------ -``` -Set-SPAlternateURL -Identity https://www.contoso.com -Url https://sharepoint.contoso.com -Zone "Default" -``` - -This example changes the URL and zone of the alternate URL https://www.contoso.com. - - -### ------------------EXAMPLE 3------------------ -``` -Get-SPAlternateURL https://www.contoso.com | Set-SPAlternateURL -Zone "Internet" -``` - -This example changes the zone of the alternate URL https://www.contoso.com. - - -### ------------------EXAMPLE 4------------------ -``` -Get-SPWebApplication |%{ Get-SPAlternateURL -WebApplication $_ -Zone "Extranet" } | Set-SPAlternateURL -Zone "Intranet" -``` - -This example changes the zone of the alternate URL for the specified Web application from Extranet to Intranet. - - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the alternate URL to change. - -The type must be a valid URL, in the form https://server_name/WebApplication/site, or a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPAlternateUrlPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -Specifies the new alternate URL. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Zone -Sets the supplied alternate URL as one of the five zones. - -The type must be any one of the following values: Default, Intranet, Internet, Extranet, or Custom. - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppAcquisitionConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppAcquisitionConfiguration.md deleted file mode 100644 index f127c9cb49..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppAcquisitionConfiguration.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappacquisitionconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppAcquisitionConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppAcquisitionConfiguration - -## SYNOPSIS -Sets app acquisition settings. - -## SYNTAX - -### MarketplaceSettingsInSiteSubscription -``` -Set-SPAppAcquisitionConfiguration -Enable <Boolean> -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### MarketplaceSettingsInWebApplication -``` -Set-SPAppAcquisitionConfiguration -Enable <Boolean> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -WebApplication <SPWebApplicationPipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the Set-SPAppAcquisitionConfiguration cmdlet to set app acquisition settings from the SharePoint Store or App Catalog. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference (https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Set-SPAppAcquisitionConfiguration -WebApplication https://localhost -Enable:$false -``` - -This example disabled app purchases for the specified Web Application. - -### --------------------EXAMPLE 2--------------------- -``` -Set-SPAppAcquisitionConfiguration -SiteSubscription https://localhost/sites/SharePointOnlineAdmin1 -Enable:$false -``` - -This example disables app purchases for the specified tenant. - - -## PARAMETERS - -### -Enable -Specifies whether acquisition is enabled or disabled. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site collection for which to set app acquisition settings. - - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: MarketplaceSettingsInSiteSubscription -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the web application for which acquisitions settings are to be set. - - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: MarketplaceSettingsInWebApplication -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPWebApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPAppAcquisitionConfiguration](Get-SPAppAcquisitionConfiguration.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppAutoProvisionConnection.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppAutoProvisionConnection.md deleted file mode 100644 index bde873d7d0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppAutoProvisionConnection.md +++ /dev/null @@ -1,225 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappautoprovisionconnection -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppAutoProvisionConnection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppAutoProvisionConnection - -## SYNOPSIS -Sets provision connection settings for an app. - - -## SYNTAX - -### WebHostEndPoint -``` -Set-SPAppAutoProvisionConnection -ConnectionType <ConnectionTypes> -EndPoint <String> - [-AssignmentCollection <SPAssignmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [<CommonParameters>] -``` - -### WebHostSetup -``` -Set-SPAppAutoProvisionConnection -ConnectionType <ConnectionTypes> -EndPoint <String> -Password <String> - -Username <String> [-AssignmentCollection <SPAssignmentCollection>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -### WebHostCredential -``` -Set-SPAppAutoProvisionConnection -ConnectionType <ConnectionTypes> -Password <String> -Username <String> - [-AssignmentCollection <SPAssignmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [<CommonParameters>] -``` - -### Remove -``` -Set-SPAppAutoProvisionConnection [-Remove] [-AssignmentCollection <SPAssignmentCollection>] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Set-SPAppAutoProvisionConnection` cmdlet to set provision connection settings for a specified app. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Set-SpAppAutoProvisionConnection -ConnectionType RemoteWebHost -EndPoint https://SPremotewebhost -Password passname -Username <username> -``` - -This example configures remote web host to be used provision apps that use this functionality for the default site subscription server on https://SPremotewebhost. - - -### --------------------EXAMPLE 2--------------------- -``` -C:\PS>$subscription = Get-SPSiteSubscription https://Contoso.com - -Set-SPAppAutoProvisionConnection -ConnectionType RemoteWebHost -EndPoint https://SPremotewebhost -Password passname -Username <username> -SiteSubscription $subscription -``` - -This example configures remote web host to be used provision apps that use this functionality for the site subscription of Contoso.com site to server on https://SPremotewebhost. - - -### --------------------EXAMPLE 3--------------------- -``` -Set-SPAppAutoProvisionConnection -ConnectionType RemoteWebHost -EndPoint https://SPremotewebhost -``` - -This example updates the endpoint of the already configured remote web host server https://SPRemotewebhost for the default site subscription. - - -### --------------------EXAMPLE 4--------------------- -``` -Set-SPAppAutoProvisionConnection -ConnectionType RemoteWebHost -Remove -``` - -This example removes the remote web host configuration for the default site subscription. - - -## PARAMETERS - -### -ConnectionType -Specifies the connection type to provision. - -```yaml -Type: ConnectionTypes -Parameter Sets: WebHostEndPoint, WebHostSetup, WebHostCredential -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndPoint -Specifies the end point of the provision connection. - -```yaml -Type: String -Parameter Sets: WebHostEndPoint, WebHostSetup -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -Specifies the password for the provision connection. - -```yaml -Type: String -Parameter Sets: WebHostSetup, WebHostCredential -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Remove -Removes the auto provision connection of the app. - -```yaml -Type: SwitchParameter -Parameter Sets: Remove -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Username -Specifies the user name of the connection. - -```yaml -Type: String -Parameter Sets: WebHostSetup, WebHostCredential -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the site collection for which the provision connection is to be associated. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppAutoProvisionConnection](Get-SPAppAutoProvisionConnection.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppDisablingConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppDisablingConfiguration.md deleted file mode 100644 index 3076c65ae3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppDisablingConfiguration.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappdisablingconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppDisablingConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppDisablingConfiguration - -## SYNOPSIS -Sets the disable list sync state for an app. - - -## SYNTAX - -``` -Set-SPAppDisablingConfiguration -Enable <Boolean> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPAppDisablingConfiguration cmdlet to set the disabled sync list state for an app . - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference (https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPAppDisablingConfiguration -``` - -This example sets the disable sync state for apps. - - -## PARAMETERS - -### -Enable -Specifies whether to enable or disable an entry from the list. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPAppDisablingConfiguration](Get-SPAppDisablingConfiguration.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppDomain.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppDomain.md deleted file mode 100644 index 1b7fa25d13..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppDomain.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappdomain -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppDomain -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppDomain - -## SYNOPSIS -Sets the domain used to host apps. - - -## SYNTAX - -``` -Set-SPAppDomain [-AppDomain] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAppDomain` cmdlet to set the domain used to host apps in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPAppDomain -Domain apps.contoso.com -``` - -This example sets the app domain to apps.contoso.com. -All apps in the farm will be hosted in the apps.contoso.com domain. - - -## PARAMETERS - -### -AppDomain -Specifies the domain to be used for apps. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppDomain](Get-SPAppDomain.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppHostingQuotaConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppHostingQuotaConfiguration.md deleted file mode 100644 index cde366a2bc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppHostingQuotaConfiguration.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spapphostingquotaconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppHostingQuotaConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppHostingQuotaConfiguration - -## SYNOPSIS -Sets hosting quotas for an app. - - -## SYNTAX - -``` -Set-SPAppHostingQuotaConfiguration -AppHostingLicenseQuota <Double> -AppInstanceCountQuota <Double> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - -SiteSubscription <SPSiteSubscriptionPipeBind> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPAppHostingQuotaConfiguration cmdlet to set hosting quotas for a specified app by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference (https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### ----------------EXAMPLE 1---------- -``` -Set-SPAppHostingQuotaConfiguration -Identity 586d4a32-98c3-42ce-80be-3c76c10c250c -AppInstanceCountQuota 50 -AppHostingLicenseQuota 25 -``` - -This example sets hosting Quotas for the SiteSubscriptionId "586d4a32-98c3-42ce-80be-3c76c10c250c" with hosted appinstance limit as 50 and hosted apps licenses assigned as 25. - - -### ----------------EXAMPLE 2---------- -``` -Get-SPSiteSubscription | Set-SPAppHostingQuotaConfiguration -Identity $_ -AppInstanceCountQuota 50 -AppHostingLicenseQuota 25 -``` - -This example sets hosting Quotas for all SiteSubscriptions in the farm with hosted apps limit as 50 and hosted apps licenses assigned as 25. - - -## PARAMETERS - -### -AppHostingLicenseQuota -Specifies the app licensing quota. - - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AppInstanceCountQuota -Specifies the number instances of an app. - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the Site Subscription. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPAppHostingQuotaConfiguration](Get-SPAppHostingQuotaConfiguration.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppManagementDeploymentId.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppManagementDeploymentId.md deleted file mode 100644 index bc9c7025c4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppManagementDeploymentId.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappmanagementdeploymentid -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppManagementDeploymentId -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppManagementDeploymentId - -## SYNOPSIS -Sets the identifier of the farm or tenant used by the Office Marketplace to issue App licenses. - - -## SYNTAX - -``` -Set-SPAppManagementDeploymentId -AppManagementServiceApplication <AppManagementServiceApplication> - -DeploymentId <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Identity <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAppManagementDeploymentId` cmdlet to set the identifier of the farm or tenant used by the Office Marketplace to issue App Licenses. -To ensure you do not lose rights to the use of all Apps you have purchased on the Marketplace, do not change the deployment id unless directed by Microsoft documentation or support. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------EXAMPLE 1---------- -``` -$sa = Get-SPServiceApplication | where {$_.TypeName -eq "App Management Service Application"} -Set-SPAppManagementDeploymentId -DeploymentId 3102B7C3-1866-48EE-91CB-84E20AD24BF2 -AppManagementServiceApplication $sa -``` - -This example sets the deployment identifier of the current farm to 3102B7C3-1866-48EE-91CB-84E20AD24BF2. - - -### -----------EXAMPLE 2---------- -``` -$sa = Get-SPServiceApplication | where {$_.TypeName -eq "App Management Service Application"} -Get-SPSiteSubscription | where{$_.Id -eq "88f16a50-0530-4f3f-b749-24ef0b30d685"} | Set-SPAppManagementDeploymentId -DeploymentId 3102B7C3-1866-48EE-91CB-84E20AD24BF2 -AppManagementServiceApplication $sa -``` - -This example sets the deployment identifier of the tenant with the site subscription identifier 88f16a50-0530-4f3f-b749-24ef0b30d685 to 3102B7C3-1866-48EE-91CB-84E20AD24BF2. - - -## PARAMETERS - -### -AppManagementServiceApplication -Specifies the app management service application object that is running on the farm. - -```yaml -Type: AppManagementServiceApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeploymentId -Specifies the deployment identifier value for the tenant. -This parameter works in conjunction with the value that is defined with Identity parameter. -If Identity parameter is omitted, then it is assumed that this deployment identifier value belongs to the farm. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Identifies the site subscription object representing the tenant to which the DeploymentId parameter is to be assigned. -If the Identity parameter is omitted, it is assumed that the deployment identifier belongs to the farm. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: Subscription -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppPrincipalPermission.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppPrincipalPermission.md deleted file mode 100644 index b758ffc236..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppPrincipalPermission.md +++ /dev/null @@ -1,217 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappprincipalpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppPrincipalPermission -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppPrincipalPermission - -## SYNOPSIS -Sets the permissions on a given app principal. - - -## SYNTAX - -``` -Set-SPAppPrincipalPermission -AppPrincipal <SPAppPrincipal> -Right <SPCmdletAppPrincipalPermissionKind> - -Scope <SPCmdletAppPrincipalPermissionScope> -Site <SPWebPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [-EnableAppOnlyPolicy] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAppPrincipalPermission` cmdlet to set the permissions on a given app principal for a given scope (tenant, site collection, and web) and given levels (Read, Write, Manage, Full Control). - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------EXAMPLE------------- -``` -$clientID = "11111111-2222-3333-4444-555555555555" -$site = Get-SPSite https://siteUrl -$realm = Get-SPAuthenticationRealm -ServiceContext $site -$appIdentifier = $clientID + "@" + $realm -$appPrincipal = Get-SPAppPrincipal -NameIdentifier $appIdentifier -Web $site.RootWeb -Set-AppPrincipalPermission -AppPrincipal $appPrincipal -Site $site.RootWeb -Scope Site -Level Manage -``` - -This example sets the App Principal permission to Manage with a scope of Site. - -## PARAMETERS - -### -AppPrincipal -Specifies the AppPrincipal object. - -```yaml -Type: SPAppPrincipal -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Right -Specifies the permission level for the principal object. - -The value is any of the following levels: - ---Read - ---Write - ---Manage - ---Full Control - -```yaml -Type: SPCmdletAppPrincipalPermissionKind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Specifies the scope to which to apply the principal permission. - -The value is any of the following scopes: - ---Site - ---SiteCollection - ---SiteSubscription - -```yaml -Type: SPCmdletAppPrincipalPermissionScope -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Specifies the site (that is, SPWeb object) that the AppPrincipalPermission is being set.a - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableAppOnlyPolicy -Specifies if the app only policy is turned on for the app principal. - -The valid values are True and False. The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPAppPrincipalPermission](Remove-SPAppPrincipalPermission.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppScaleProfile.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppScaleProfile.md deleted file mode 100644 index b39ee7fa42..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppScaleProfile.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappscaleprofile -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppScaleProfile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppScaleProfile - -## SYNOPSIS -Sets settings for the app profile. - - -## SYNTAX - -``` -Set-SPAppScaleProfile [-AssignmentCollection <SPAssignmentCollection>] [-MaxDatabaseSize <String>] - [-RemoteWebSiteInstanceCount <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAppScaleProfile` cmdlet to set settings for an app profile. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE----------- -``` -Set-SPAppScaleProfile -MaxDatabaseSize "2 GB" -RemoteWebSiteInstanceCount 1 -``` - -This example sets the farm level app scale profile. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MaxDatabaseSize -Specifies the database size of the app profile. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteWebSiteInstanceCount -Specifies whether a remote site can access the profilefrom. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppScaleProfile](Get-SPAppScaleProfile.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppSiteDomain.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppSiteDomain.md deleted file mode 100644 index 9a82a5e8ad..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppSiteDomain.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappsitedomain -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppSiteDomain -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppSiteDomain - -## SYNOPSIS -Creates or changes the URL of any installed app. - - -## SYNTAX - -``` -Set-SPAppSiteDomain -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPAppSiteDomain cmdlet to create or change the URL of any installed app by using the Site parameter to reset the subscription name and app site domain identifier. - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPAppSiteDomain -Site https://www.contoso.com -``` - -This example sets the subscription name and app site domain identifier for the https://www.contoso.com site. - - -## PARAMETERS - -### -Site -Specifies the SPSite object or the GUID of the SPSite or the URL of the SPSite. - - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppSiteSubscriptionName.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppSiteSubscriptionName.md deleted file mode 100644 index 7c5b91b2e6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppSiteSubscriptionName.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappsitesubscriptionname -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppSiteSubscriptionName -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppSiteSubscriptionName - -## SYNOPSIS -Sets or changes the name for the specified site subscription. - - -## SYNTAX - -``` -Set-SPAppSiteSubscriptionName -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Force] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAppSiteSubscriptionName` cmdlet to set or change the name for a specified site subscription by using the Name parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------EXAMPLE 1---------- -``` -Set-SPAppSiteSubscriptionName -Name Contoso -``` - -This example sets the name of the default site subscription to "Contoso". - - -### -----------EXAMPLE 2---------- -``` -Set-SPAppSiteSubscriptionName -Name Contoso -SiteSubscription https://www.contoso.com -``` - -This example changes the name of the site subscription for SPSite from https://www.contoso.com to "Contoso". - - -## PARAMETERS - -### -Name -Specifies the name for the site subscription. - -Each site subscription must have a unique name. -The name is used in part to determine the domain that apps for SharePoint are installed in for each site subscription. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The site subscription name is recorded in other databases in the SharePoint farm. -In cases such as disaster recovery or restore of the SharePoint farm, the Force parameter can be specified to ensure that the site subscription name has been propagated appropriately throughout the SharePoint farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the SPSiteSubscription object or the SPSiteSubscription Id or the URL of an SPSite. -If this parameter is not specified, then the default site subscription is used. -All SharePoint SPSites are members of the default site subscription if they have not been specifically assigned a site subscription. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppSiteSubscriptionName](Get-SPAppSiteSubscriptionName.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStateUpdateInterval.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStateUpdateInterval.md deleted file mode 100644 index 84fc7e3985..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStateUpdateInterval.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappstateupdateinterval -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppStateUpdateInterval -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppStateUpdateInterval - -## SYNOPSIS -Sets the interval in hours between updates of the app state update job. - - -## SYNTAX - -``` -Set-SPAppStateUpdateInterval -AppStateSyncHours <Int32> -FastAppRevocationHours <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAppStateUpdateInterval` cmdlet to set the interval in hours between updates of the app state update job. -The app state update job updates the app states, including app updates, in SharePoint based on information in the SharePoint Store. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------EXAMPLE-------------- -``` -Set-SPAppStateUpdateInterval -AppStateSyncHours 24 -FastAppRevocationHours 6 -``` - -This example sets the app state update interval to 24 hours and the fast app revocation interval to 6 hours. - - -## PARAMETERS - -### -AppStateSyncHours -Specifies the interval in hours between updates of the app states. -Values are 1 to 24 inclusive. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FastAppRevocationHours -Specifies the interval in hours between checks of the list of revoked apps in the SharePoint Store. -If the list of revoked apps has changed from the last time, the app states are updated. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppStateUpdateInterval](Get-SPAppStateUpdateInterval.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStoreConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStoreConfiguration.md deleted file mode 100644 index 3ef6d2979c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStoreConfiguration.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappstoreconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppStoreConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppStoreConfiguration - -## SYNOPSIS -Sets SharePoint Store settings for an app. - - -## SYNTAX - -``` -Set-SPAppStoreConfiguration [-Url <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] -Enable <Boolean> [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPAppStoreConfiguration cmdlet to set SharePoint Store settings for a specified app. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715](https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Set-SPAppStoreConfiguration -Url https://office.microsoft.com -Enable $true -``` - -This example sets the URL to the Office.com server. - - -### --------------------EXAMPLE 2--------------------- -``` -Set-SPAppStoreConfiguration -Enable $false -``` - -This example turns off the SharePoint Store. - -### --------------------EXAMPLE 3--------------------- -``` -Set-SPAppStoreConfiguration -Enable $true -``` - -This example turns on the SharePoint Store. - -## PARAMETERS - -### -Url -Specifies the URL of the app for which to set SharePoint Store settings. - -The SharePoint store value should not be changed unless instructed by a Microsoft representative. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -Specifies whether the Office Store services lets third- party add-ins to be found or downloaded. - -This is intended for administrators to disable discovery and downloads of third-party add-ins on their SharePoint tenants and site collections. - -The valid values are True and False. - -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Get-SPAppStoreConfiguration](Get-SPAppStoreConfiguration.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStoreWebServiceConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStoreWebServiceConfiguration.md deleted file mode 100644 index 410c0bfa31..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAppStoreWebServiceConfiguration.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spappstorewebserviceconfiguration -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAppStoreWebServiceConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAppStoreWebServiceConfiguration - -## SYNOPSIS -Sets properties of a SharePoint Store app. - - -## SYNTAX - -``` -Set-SPAppStoreWebServiceConfiguration [-AssignmentCollection <SPAssignmentCollection>] -Client <String> - [-Confirm] [-ProxyVersion <Version>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPAppStoreWebServiceConfiguration cmdlet to set the product type (On-Premises or Online) and the version used to access the SharePoint Store when SharePoint is configured to access the . - -This cmdlet is not intended for the ITPro audience. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715](https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPAppStoreWebServiceConfiguration -Client=SP -ProxyVersion=16.1 -``` - -This example set the product type and version for a SharePoint Store app. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Client -Specifies the client value of the SharePoint Store app. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProxyVersion -Specifies the proxy version value of the SharePoint Store app. - -```yaml -Type: Version -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPApplicationCredentialKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPApplicationCredentialKey.md deleted file mode 100644 index 7316abc650..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPApplicationCredentialKey.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spapplicationcredentialkey -applicable: SharePoint Server 2019 -title: Set-SPApplicationCredentialKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPApplicationCredentialKey - -## SYNOPSIS -Sets the application credential key on the local server. - - -## SYNTAX - -``` -Set-SPApplicationCredentialKey [-Password] <SecureString> [-AssignmentCollection <SPAssignmentCollection>] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - - -## DESCRIPTION -Use the **Set-SPApplicationCredentialKey** cmdlet to set the application credential key on the local server, which is used by certain features to encrypt and decrypt passwords. - -The application credential key must be identical on each server in the farm where it is set. - -## EXAMPLES - -### EXAMPLE -```powershell - $key = ConvertTo-SecureString -String "New Password" -AsPlainText -Force -Set-SPApplicationCredentialKey -Password $key -``` - -This example sets the application credential key on the local server to "New Password". - -## PARAMETERS - -### -Password -Specifies the application credential key. -Avoid reusing the farm passphrase or service account passwords for the application credential key. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2019 -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## RELATED LINKS -[Remove-SPApplicationCredentialKey](Remove-SPApplicationCredentialKey.md) - - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAuthenticationRealm.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAuthenticationRealm.md deleted file mode 100644 index 6aa998a540..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPAuthenticationRealm.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spauthenticationrealm -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPAuthenticationRealm -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPAuthenticationRealm - -## SYNOPSIS -Sets the authentication realm. - - -## SYNTAX - -``` -Set-SPAuthenticationRealm [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Realm <String>] - [-ServiceContext <SPServiceContextPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPAuthenticationRealm` cmdlet to set the authentication realm at the farm or site collection level by using the Realm parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$c = Get-SPServiceContext -Site "https://<websiteurl>" -Set-SPAuthenticationRealm -ServiceContext $c -Realm "t686d436-9f16-42db-09b7-cb578e110ccd" -``` - -This example sets the authentication realm as specified by the realm parameter. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Realm -Specifies the realm to be set. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceContext -Specifies the service context for which the realm needs to be set. -For example, $root.web. - -```yaml -Type: SPServiceContextPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAuthenticationRealm](Get-SPAuthenticationRealm.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBingMapsBlock.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBingMapsBlock.md deleted file mode 100644 index 5cb37bc7da..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBingMapsBlock.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spbingmapsblock -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPBingMapsBlock -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPBingMapsBlock - -## SYNOPSIS -Sets Bing maps to blocked status. - - -## SYNTAX - -``` -Set-SPBingMapsBlock [-BlockBingMapsInAllLocales] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPBingMapsBlock` cmdlet to specify whether to block Bing Maps in all locales, or not to block them in all locales. -Bing Maps will be displayed only in non-restricted locales if this property is not set. -The default value is 0 (not blocked). -Use a value of 1 to block in all locales. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPBingMapsBlock 1 -``` - -This example displays how to block Bing Maps in all locales for the farm. - - -## PARAMETERS - -### -BlockBingMapsInAllLocales -Specifies whether Bing Maps are blocked in all locales. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPBingMapsBlock](Get-SPBingMapsBlock.md) - -[Get-SPBingMapsKey](Get-SPBingMapsKey.md) - -[Set-SPBingMapskey](Set-SPBingMapskey.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBingMapsKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBingMapsKey.md deleted file mode 100644 index d9b7f3ec63..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBingMapsKey.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spbingmapskey -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPBingMapsKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPBingMapsKey - -## SYNOPSIS -Sets the Bing Maps key. - - -## SYNTAX - -``` -Set-SPBingMapsKey [-BingKey] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPBingMapsKey` cmdlet to set the Bing Maps key. -This key lets you access Bing Maps. -For additional information about Bing Keys, see Bing Maps Account Center (https://www.bingmapsportal.com/) - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPBingMapsKey -BingKey <Bing Maps Key> -``` - -This example sets the key that is used by Bing Maps. - - -## PARAMETERS - -### -BingKey -Specifies the Bing Maps key to set. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPBingMapsKey](Get-SPBingMapsKey.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBrowserCustomerExperienceImprovementProgram.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBrowserCustomerExperienceImprovementProgram.md deleted file mode 100644 index 9ea6fd413b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBrowserCustomerExperienceImprovementProgram.md +++ /dev/null @@ -1,211 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spbrowsercustomerexperienceimprovementprogram -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPBrowserCustomerExperienceImprovementProgram -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPBrowserCustomerExperienceImprovementProgram - -## SYNOPSIS -Turns on or off the browser Customer Experience Improvement Program. - - -## SYNTAX - -### Farm -``` -Set-SPBrowserCustomerExperienceImprovementProgram [-Farm] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Enable] [-WhatIf] [<CommonParameters>] -``` - -### SiteSubscription -``` -Set-SPBrowserCustomerExperienceImprovementProgram -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Enable] [-WhatIf] [<CommonParameters>] -``` - -### WebApplication -``` -Set-SPBrowserCustomerExperienceImprovementProgram -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Enable] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPBrowserCustomerExperienceImprovementProgram` cmdlet turns on or off the browser Customer Experience Improvement Program for collecting software quality metrics. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Set-SPBrowserCustomerExperienceImprovementProgram -Farm -Enable -``` - -This example turns on the browser Customer Experience Improvement Program for the farm. - - -### ------------------EXAMPLE 2----------------------- -``` -Set-SPBrowserCustomerExperienceImprovementProgram -Farm -Enable:$False -``` - -This example turns off the browser Customer Experience Improvement Program for the farm. - - -### ------------------EXAMPLE 3----------------------- -``` -Set-SPWebApplication https://MyOfficeApp1 | Get- SPBrowserCustomerExperienceImprovementProgram -Enable -``` - -This example turns on the browser Customer Experience Improvement Program for the Web application, MyOfficeApp1. - - -## PARAMETERS - -### -Farm -{{Fill Farm Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: Farm -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Sets the Customer Experience Improvement Program opt-in state for the specified site subscription. - -The type must be a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscription1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Sets the Customer Experience Improvement Program opt-in state for the specified SharePoint Web application. - -The type must be a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -Turns on the browser Customer Experience Improvement Program. -The default value is True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogEntityNotificationWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogEntityNotificationWeb.md deleted file mode 100644 index f85a1c55d8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogEntityNotificationWeb.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spbusinessdatacatalogentitynotificationweb -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPBusinessDataCatalogEntityNotificationWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPBusinessDataCatalogEntityNotificationWeb - -## SYNOPSIS -Sets the entity notification site. - - -## SYNTAX - -``` -Set-SPBusinessDataCatalogEntityNotificationWeb -Web <SPWebPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPBusinessDataCatalogEntityNotificationWeb` cmdlet to sets the entity notification site for the specified service context by using the Web parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPBusinessDataCatalogEntityNotificationWeb -Web "https://contoso/" -``` - -This example sets https://contoso as the entity notification site for the service context of the site at https://contoso. - - -## PARAMETERS - -### -Web -Specifies the site to be set as the entity notification site for its own service context. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-SPBusinessDataCatalogEntityNotificationWeb](Clear-SPBusinessDataCatalogEntityNotificationWeb.md) - -[Get-SPBusinessDataCatalogEntityNotificationWeb](Get-SPBusinessDataCatalogEntityNotificationWeb.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogMetadataObject.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogMetadataObject.md deleted file mode 100644 index 2a3971207e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogMetadataObject.md +++ /dev/null @@ -1,229 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spbusinessdatacatalogmetadataobject -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPBusinessDataCatalogMetadataObject -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPBusinessDataCatalogMetadataObject - -## SYNOPSIS -Sets the value of a property or attribute of a Business Data Connectivity Metadata Store metadata object. - - -## SYNTAX - -### Display -``` -Set-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DisplayName <String>] [-Remove] - [-SettingId <String>] [-WhatIf] [<CommonParameters>] -``` - -### NameValue -``` -Set-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-PropertyName <String>] - [-PropertyValue <PSObject>] [-Remove] [-SettingId <String>] [-WhatIf] [<CommonParameters>] -``` - -### NameRemove -``` -Set-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-PropertyName <String>] [-Remove] - [-SettingId <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPBusinessDataCatalogMetadataObject` cmdlet sets the value of a property or attribute of a Business Data Connectivity Metadata Store metadata object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$obj = Get-SPBusinessDataCatalogMetadataObject -Namespace "ContosoDatabase" -Name "ContosoDatabase" -BdcObjectType "LobSystemInstance" -ServiceContext http://contoso -Set-SPBusinessDataCatalogMetadataObject -Identity $obj -PropertyName "ShowInSearchUI" -PropertyValue "True" -``` - -This example creates a property on the LobSystemInstance (External System Instance) of name ContosoDatabase. -The property has the name ShowInSearchUI and a value of True. - - -## PARAMETERS - -### -Identity -Specifies the Business Data Connectivity Metadata Store metadata object to update. - -```yaml -Type: MetadataObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -Specifies the display name of the Business Data Connectivity Metadata Store metadata object. - -```yaml -Type: String -Parameter Sets: Display -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertyName -Specifies the name of the property to update. - -```yaml -Type: String -Parameter Sets: NameValue, NameRemove -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertyValue -Sets the new value of the property specified in the PropertyName parameter. - -```yaml -Type: PSObject -Parameter Sets: NameValue -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Remove -Removes the property specified in the PropertyName parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SettingId -Specifies the custom environment settings model slice for which the property applies. - -The type must be a valid string that identifies a model slice; for example, ModelSlice1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogServiceApplication.md deleted file mode 100644 index 30934a0f42..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogServiceApplication.md +++ /dev/null @@ -1,281 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spbusinessdatacatalogserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPBusinessDataCatalogServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPBusinessDataCatalogServiceApplication - -## SYNOPSIS -Sets global properties for a Business Data Connectivity service application in the farm. - - -## SYNTAX - -``` -Set-SPBusinessDataCatalogServiceApplication [-ApplicationPool <SPIisWebServiceApplicationPool>] - [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabasePassword <SecureString>] - [-DatabaseServer <String>] [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] - -Identity <SPServiceApplicationPipeBind> [-Name <String>] [-Sharing] [-Confirm] [-WhatIf] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPBusinessDataCatalogServiceApplication` cmdlet sets global properties for a Business Data Connectivity service application in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Business Data Connectivity Service Application'} -Set-SPBusinessDataCatalogServiceApplication -Identity $sa -FailoverDatabaseServer "CONTOSO\Backup" -``` - -This example sets the failover database server to CONTOSO\Backup for the given service application. - - -## PARAMETERS - -### -ApplicationPool -Specifies the IIS application pool to use for the new Business Data Connectivity service application. - -```yaml -Type: SPIisWebServiceApplicationPool -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Server Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the Business Data Connectivity database. - -The type must be a valid name of a SQL Server database; for example, UsageLogDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user specified in DatabaseUserName. -Use this parameter only if SQL Server Authentication is used to access the Business Data Connectivity database. - -The type must be a valid password. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the Business Data Connectivity database. - -The type must be a valid name of a SQL Server database; for example, UsageLogDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user name to use for connecting to the catalog database. -Use this parameter only if SQL Server Authentication is used to access the Business Data Connectivity database. - -The type must be a valid user name; for example, UserName1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host server for the failover database server. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Identity -Specifies the Business Data Connectivity service application associated with the new proxy. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies a display name for the new Business Data Connectivity service application proxy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Sharing -Specifies that the Business Data Connectivity service application is published and shared across the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -{{Fill AssignmentCollection Description}} - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogThrottleConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogThrottleConfig.md deleted file mode 100644 index 2e264f7709..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPBusinessDataCatalogThrottleConfig.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spbusinessdatacatalogthrottleconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPBusinessDataCatalogThrottleConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPBusinessDataCatalogThrottleConfig - -## SYNOPSIS -Sets the throttling configuration for a Business Data Connectivity Service application. - - -## SYNTAX - -### MaxDefault -``` -Set-SPBusinessDataCatalogThrottleConfig -Default <Int32> -Identity <ThrottleConfig> -Maximum <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### Enforcement -``` -Set-SPBusinessDataCatalogThrottleConfig [-Enforced] -Identity <ThrottleConfig> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPBusinessDataCatalogThrottleConfig` cmdlet sets the throttling configuration for a Business Data Connectivity Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottleType Items -ServiceApplicationProxy $contosoServAppProxy | Set-SPBusinessDataCatalogThrottleConfig -Maximum 1000000000 -Default 500000 -``` - -This example sets the database item throttling to values of 1000000000 maximum and 500000 default for the given service application. - - -## PARAMETERS - -### -Default -Specifies the default setting of the throttle configuration. - -```yaml -Type: Int32 -Parameter Sets: MaxDefault -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enforced -Specifies that the throttle configuration setting cannot be overridden. - -```yaml -Type: SwitchParameter -Parameter Sets: Enforcement -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the throttle configuration to update. - -```yaml -Type: ThrottleConfig -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Maximum -Specifies the maximum value of the throttling configuration setting. - -```yaml -Type: Int32 -Parameter Sets: MaxDefault -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPCentralAdministration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPCentralAdministration.md deleted file mode 100644 index e5a563773b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPCentralAdministration.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spcentraladministration -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPCentralAdministration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPCentralAdministration - -## SYNOPSIS -Sets the port for the SharePoint Central Administration Web site. - - -## SYNTAX - -``` -Set-SPCentralAdministration -Port <Int32> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [-SecureSocketsLayer] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPCentralAdministration` cmdlet sets the port for the Central Administration site. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Set-SPCentralAdministration -Port 8282 -``` - -This example sets the port for the Central Administration web application on the local farm to 8282. - - -## PARAMETERS - -### -Port -Specifies the administration port for the Central Administration site. - -The type must be a valid port number; for example, 8080. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureSocketsLayer -Enables Secure Socket Layer (SSL) encryption for the specified port. If you choose to use SSL, you must assign a server certificate to the Central Administration IIS web site by using the IIS administration tools. The Central Administration web application won't be accessible until you do this. - -The default value is False. - -If this parameter is omitted or set to False the Central Administration site will use HTTP for the specified port. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPClaimProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPClaimProvider.md deleted file mode 100644 index 456d34cf01..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPClaimProvider.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spclaimprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPClaimProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPClaimProvider - -## SYNOPSIS -Updates registration of a claims provider. - - -## SYNTAX - -``` -Set-SPClaimProvider [-Identity] <SPClaimProviderPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Default] [-Enabled] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPClaimProvider` cmdlet updates registration of a claims provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Set-SPClaimProvider -Identity "12345678-90ab-cdef-1234-567890bcdefgh" -``` - -This example turns off the specified claim provider. - - -## PARAMETERS - -### -Identity -Specifies the claim provider to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a claim provider (for example, MyClaimProvider1); or an instance of a valid SPClaimProvider object. - -```yaml -Type: SPClaimProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Default -Specifies that the claim provider applies to all Web applications and zones. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -Turns on the claim provider. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDatabase.md deleted file mode 100644 index d140608374..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDatabase.md +++ /dev/null @@ -1,210 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPContentDatabase -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Set-SPContentDatabase - -## SYNOPSIS -Sets global properties of a SharePoint content database. - - -## SYNTAX - -``` -Set-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-MaxSiteCount <Int32>] [-Status <SPObjectStatus>] [-WarningSiteCount <Int32>] [-WhatIf] - [-DatabaseFailoverServer <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPContentDatabase` cmdlet sets global properties of a SharePoint content database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------EXAMPLE 1--------------- -``` -Get-SPContentDatabase https://contoso.com | Set-SPContentDatabase -MaxSiteCount 1 -``` - -This example sets the MaxSiteCount for the content database that contains contoso.com to 1. - - -### ---------------EXAMPLE 2--------------- -``` -Get-SPContentDatabase -WebApplication https://sitename | Set-SPContentDatabase -WarningSiteCount $null -``` - -This example clears the WarningSiteCount for all databases in the sitename Web application. - - -## PARAMETERS - -### -Identity -Specifies the content database to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint content database (for example, SPContentDB1); or an instance of a valid SPContentDatabase object. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSiteCount -Specifies the maximum number of site collections that this database can host. - -The type must be a positive integer. -Set to $null to clear this value. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Status -Specifies the status of the SQL Server database. -Set this parameter to Online to make the database available to host new sites. -Set this parameter to Disabled to make the database unavailable to host new sites. - -The type must be either of the following: Online or Disabled - -```yaml -Type: SPObjectStatus -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WarningSiteCount -Specifies the number of site collections that can be created before a warning event is generated and the owner of the site collection is notified. - -The type must be a positive integer. -Set to $null to clear this value. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseFailoverServer -Specifies the name of the mirror server for failover. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDeploymentJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDeploymentJob.md deleted file mode 100644 index f63363b487..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDeploymentJob.md +++ /dev/null @@ -1,321 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spcontentdeploymentjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPContentDeploymentJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPContentDeploymentJob - -## SYNOPSIS -Sets properties of a content deployment job. - - -## SYNTAX - -``` -Set-SPContentDeploymentJob [-Identity] <SPContentDeploymentJobPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] - [-EmailAddresses <String[]>] [-EmailNotifications <ContentDeploymentNotificationSettings>] - [-HostingSupportEnabled] [-IncrementalEnabled] [-Name <String>] [-Schedule <String>] [-ScheduleEnabled] - [-Scope <SPWebPipeBind[]>] [-SqlSnapshotSetting <ContentDeploymentSqlSnapshotSetting>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPContentDeploymentJob` cmdlet sets the properties of a content deployment job. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE------------------ -``` -Get-SPContentDeploymentJob "Job 1" | Set-SPContentDeploymentJob -Schedule "hourly between 0 and 59" -ScheduleEnabled:$true -``` - -This example sets the deployment job called Job 1 to run hourly. - - -## PARAMETERS - -### -Identity -Specifies the content deployment job to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment job (for example, DeployJob1); or an instance of a valid SPContentDeploymentJob object. - -```yaml -Type: SPContentDeploymentJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description for the content deployment job. -The name can be a maximum of 4096 alphanumeric characters. - -The type must be a valid string. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -EmailAddresses -Specifies the e-mail addresses of individuals who receive notification e-mails about this ContentDeploymentJob object. - -The type must be a list of valid e-mail addresses. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailNotifications -Specifies how e-mail notifications are sent about this ContentDeploymentJob object. - -The type must be one of the following: - --Never specifies that e-mail notifications will not be sent when a job succeeds or fails. - -- Success specifies that e-mail notifications will be sent if a content deployment job succeeds. -- Failure specifies that e-mail notifications will be sent if a content deployment job fails. -- Always specifies that e-mail notifications will be sent when a job succeeds or fails. - -```yaml -Type: ContentDeploymentNotificationSettings -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HostingSupportEnabled -Enables special hosting behavior. -The default value is False. - -Normally, a content deployment job is enabled or disabled by using the SharePoint Central Administration Web site. -However, in the case of hosting, the tenant administrator does not have permissions to access the Central Administration page to configure jobs. -Therefore, when the HostingSupportEnabled parameter is set to True, the hoster creates the job, so that tenants can enable or disable their deployment jobs from their tenant administration site. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncrementalEnabled -Specifies that only incremental changes are deployed to the destination site collection. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the new content deployment job. - -The type must be a valid name of a content deployment job; for example, DeployJob1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Schedule -Sets the schedule for the deployment job. - -The type must be a valid SPSchedule object. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScheduleEnabled -Enables the schedule for the deployment job. -If the schedule is not enabled, the job can be run manually only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Sets the scope of the deployment job. -SPSite objects that are passed in must exist in the current path of the source site collection. -The default scope is the entire site collection. -Valid values include a SPWeb object or an array of SPWeb objects. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint Foundation Web site (for example, MySPSite1); or an instance of a valid SPWeb object. - -```yaml -Type: SPWebPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SqlSnapshotSetting -Backs up the SharePoint Foundation content database by using SQL Server. - -The type must be one of the following values: None or CreateNew. - -```yaml -Type: ContentDeploymentSqlSnapshotSetting -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDeploymentPath.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDeploymentPath.md deleted file mode 100644 index cf142b8cda..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPContentDeploymentPath.md +++ /dev/null @@ -1,325 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spcontentdeploymentpath -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPContentDeploymentPath -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPContentDeploymentPath - -## SYNOPSIS -Sets properties of a content deployment path. - - -## SYNTAX - -``` -Set-SPContentDeploymentPath [-Identity] <SPContentDeploymentPathPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Authentication <PathAuthenticationOption>] - [-CompressionEnabled] [-DeploySecurityInformation <SPIncludeSecurity>] [-DeployUserNamesEnabled] - [-Description <String>] [-DestinationCentralAdministrationURL <Uri>] [-EventReceiversEnabled] - [-KeepTemporaryFilesOptions <TemporaryFilesOption>] [-Name <String>] [-PathAccount <PSCredential>] - [-PathEnabled] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPContentDeploymentPath` cmdlet sets the properties of a content deployment path for a content deployment job. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Get-SPContentDeploymentPath "Path 1" | Set-SPContentDeploymentPath -PathEnabled:$false -``` - -This example sets the deployment path Path 1 to be disabled. - - -## PARAMETERS - -### -Identity -Specifies the content deployment path to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment job (for example; DeployPath1); or an instance of a valid SPContentDeploymentPath object. - -```yaml -Type: SPContentDeploymentPathPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Authentication -Sets the Windows-based authentication type that the source front-end Web server uses to communicate with the destination Web application. - -The type must be one of the following values: WindowsAuth or BasicAuth. - -```yaml -Type: PathAuthenticationOption -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompressionEnabled -Turns on compression during the export. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeploySecurityInformation -Specifies the user and group information to include during the export operation for this content deployment path. -The default value is All. - -The type must be one of the following values: None, All, or WssOnly- Applies only SharePoint Foundation security settings. -Includes user memberships and role assignments such as default roles, for example, Web Designer or any custom roles that extend from the default roles. -The access control list (ACL) for each object is migrated. -No user information defined in the DAP or LDAP servers is included. - -```yaml -Type: SPIncludeSecurity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeployUserNamesEnabled -Specify to enable event receivers during import. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Sets the description for the content deployment path. -The description can contain a maximum of 4096 alphanumeric characters. - -The type must be a valid string. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DestinationCentralAdministrationURL -Specifies the SharePoint Central Administration URL for the destination farm. - -The type must be a valid URL, in the form http://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EventReceiversEnabled -Turns on event receivers during import. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepTemporaryFilesOptions -Specifies that temporary files are kept after content deployment is finished. - -The type must be one of the following values: Never, Always, or OnFailure. - -```yaml -Type: TemporaryFilesOption -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the content deployment path. - -The type must be a valid name of a content deployment path; for example, DeploymentPath1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -PathAccount -Specifies the user ID that is an administrator on the Central Administration page on the destination farm. - -The type must be a valid SharePoint user. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PathEnabled -Enables the content deployment path. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPCustomLayoutsPage.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPCustomLayoutsPage.md deleted file mode 100644 index 610d4b91b0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPCustomLayoutsPage.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spcustomlayoutspage -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPCustomLayoutsPage -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPCustomLayoutsPage - -## SYNOPSIS -Maps a new path for a custom layout page. - - -## SYNTAX - -### CustomPage -``` -Set-SPCustomLayoutsPage -Identity <SPCustomPage> -RelativePath <String> - -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [-CompatibilityLevel <Int32>] [<CommonParameters>] -``` - -### ResetCustomPage -``` -Set-SPCustomLayoutsPage -Identity <SPCustomPage> [-Reset] -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [-CompatibilityLevel <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPCustomLayoutsPage` cmdlet maps a new path for a custom layouts page in a Web application. -To remove the mapping for a custom layouts page, use the Reset parameter instead of the RelativePath parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Set-SPCustomLayoutsPage -Identity AccessDenied -RelativePath "/_layouts/custompages/myaccessdenied.aspx" -WebApplication "https://server_name/mywebapp" -``` - -This example maps the specified path for the AccessDenied layout page in the Web application "https://server_name/mywebapp". - - -## PARAMETERS - -### -Identity -Specifies the custom layout page to set. - -The type must be one of the following: None, AccessDenied, Confirmation, Error, Login, RequestAccess, Signout, or WebDeleted. - -```yaml -Type: SPCustomPage -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RelativePath -Specifies the path of the custom layout page. - -The type must be a valid path of a layout page, in the form _layouts/custompages/myaccessdenied.aspx. - -```yaml -Type: String -Parameter Sets: CustomPage -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Reset -Resets the mapping of a custom layouts page. - -```yaml -Type: SwitchParameter -Parameter Sets: ResetCustomPage -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the SharePoint Web application that contains the custom layout page. - -The type must be a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of templates to use when creating a new SPSite object. This value sets the initial CompatibilityLevel value for the site collection. When this parameter is not specified, the CompatibilityLevel will default to the highest possible version for the web application depending on the CompatibilityRange setting. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDataConnectionFile.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDataConnectionFile.md deleted file mode 100644 index a8172bcd8d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDataConnectionFile.md +++ /dev/null @@ -1,227 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spdataconnectionfile -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPDataConnectionFile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPDataConnectionFile - -## SYNOPSIS -Sets properties of a data connection file. - - -## SYNTAX - -``` -Set-SPDataConnectionFile [-Identity] <SPDataConnectionFilePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Category <String>] [-Confirm] [-Description <String>] - [-DisplayName <String>] [-WebAccessible <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPDataConnectionFile` cmdlet sets the properties of the data connection file specified in the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Set-SPDataConnectionFile -Identity "sample.udcx" -Category "Temp" -``` - -This example updates the Category of the specified .udcx file. - - -### --------------EXAMPLE 2----------------- -``` -Set-SPDataConnectionFile -Identity "sample.udcx" -DisplayName "NewDisplayName" -``` - -This example updates the DisplayName of the specified .udcx file. - - -### --------------EXAMPLE 3----------------- -``` -Sample.udcx" | Set-SPDataConnectionFile -Category "Temp" -``` - -This example updates the Category of the specified .udcx file. - - -### --------------EXAMPLE 4----------------- -``` -Get-SPDataConnectionFile | where {$_.Category -eq "Category1"} | Set-SPDataConnectionFile -Category "Category2" -``` - -This example updates the Category field for the collection of .udcx files that are returned from a query used by the `Get-SPDataConnectionFile` cmdlet. - - -## PARAMETERS - -### -Identity -Specifies the data connection file to update. - -The type must be a valid GUID, in form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a data connection file (for example, DataConnectionFileName1.udcx); or an instance of a valid SPDataConnectionFile object. - -```yaml -Type: SPDataConnectionFilePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Category -Sets an arbitrary category on the file which can be used to group the files. -The category name can have a maximum of 255 characters. - -The type must be a valid string value; for example, Category1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Sets the description for the data connection file. -The name can be a maximum of 4096 alphanumeric characters. - -The type must be a valid string; for example, Description of my universal data connection file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -Specifies the display name that describes the data connection file. -The name can have a maximum of 255 characters. - -The type must be a valid string; for example, InfoPathUDC1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebAccessible -Specifies that the universal data connection file can be accessed by using the Web service. -If false, only the forms server can retrieve the universal data connection files internally. -The default value is False. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDefaultProfileConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDefaultProfileConfig.md deleted file mode 100644 index 42a4eda706..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDefaultProfileConfig.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spdefaultprofileconfig -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPDefaultProfileConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPDefaultProfileConfig - -## SYNOPSIS -Changes the MySitesPublicEnabled property of the User Profile Application Proxy. - - -## SYNTAX - -``` -Set-SPDefaultProfileConfig [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -MySitesPublicEnabled <Boolean> -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPDefaultProfileConfig cmdlet to change the MySitesPublicEnabled property of a User Profile Application Proxy from whatever was set at the time of Proxy creation to whatever is defined by using this cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715)](https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Set-SPDefaultProfileConfig $proxy -MySitesPublicEnabled $true -``` - -This example changes the MySitesPublicEnabled property of the specified user profile service application. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MySitesPublicEnabled -Enables or disables public MySites. - -The valid values are $True or $False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the proxy of the User Profile Service application that contains the site subscription to delete.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application proxy (for example, UserProfileSvcProxy1); or an instance of a valid SPServiceApplicationProxy object. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationProxyPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDesignerSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDesignerSettings.md deleted file mode 100644 index 9b6e7e39fc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDesignerSettings.md +++ /dev/null @@ -1,281 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spdesignersettings -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPDesignerSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPDesignerSettings - -## SYNOPSIS -Sets SharePoint Designer features. - - -## SYNTAX - -``` -Set-SPDesignerSettings [-WebApplication] <SPWebApplicationPipeBind> [-AllowDesigner <Boolean>] - [-AllowMasterPageEditing <Boolean>] [-AllowRevertFromTemplate <Boolean>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-ShowURLStructure <Boolean>] [-WhatIf] - [-AllowCreateDeclarativeWorkflow <Boolean>] [-AllowSaveDeclarativeWorkflowAsTemplate <Boolean>] - [-AllowSavePublishDeclarativeWorkflow <Boolean>] [-DesignerDownloadUrl <String>] - [-RequiredDesignerVersion <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPDesignerSettings` cmdlet sets SharePoint Designer features on a specified Web application when the WebApplicaton is used. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE-------------------- -``` -Set-SPDesignerSettings -WebApplication https://contoso -AllowRevertFromTemplate $False -AllowMasterPageEditing $False -``` - -This example disables the ability to detach pages from existing site definitions and to edit master pages and page layouts. - - -## PARAMETERS - -### -WebApplication -Specifies the Web application in which the settings will apply. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AllowDesigner -Specifies whether to allow users to edit sites in a web application by using SharePoint Designer. -The default value is True - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMasterPageEditing -Specifies whether to allow site administrators to customize master pages and layout pages using SharePoint Designer. -The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowRevertFromTemplate -Specifies whether to allow site administrators to detach pages from the original site definition using SharePoint Designer. -The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowURLStructure -Specifies whether to allow site administrators to manage the URL structure of their Web sites by using SharePoint Designer. -The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCreateDeclarativeWorkflow -Allows the creation of declarative workflows. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowSaveDeclarativeWorkflowAsTemplate -Allows saving declarative workflows as a template. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowSavePublishDeclarativeWorkflow -Allows saving of published declarative workflows. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DesignerDownloadUrl -Sets the URL to the SharePoint Designer download. The default value is: - -https://go.microsoft.com/fwlink/?LinkId=328584 - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredDesignerVersion -Sets the required version of SharePoint Designer. The default value is - -15.0.0.0 - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDiagnosticConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDiagnosticConfig.md deleted file mode 100644 index 1998be818f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDiagnosticConfig.md +++ /dev/null @@ -1,514 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spdiagnosticconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPDiagnosticConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPDiagnosticConfig - -## SYNOPSIS -Sets diagnostic configuration settings on the farm. - - -## SYNTAX - -``` -Set-SPDiagnosticConfig [-AllowLegacyTraceProviders] [-AppAnalyticsAutomaticUploadEnabled] - [-AssignmentCollection <SPAssignmentCollection>] [-CustomerExperienceImprovementProgramEnabled] - [-DaysToKeepLogs <Int32>] [-DownloadErrorReportingUpdatesEnabled] [-ErrorReportingAutomaticUploadEnabled] - [-ErrorReportingEnabled] [-EventLogFloodProtectionEnabled] [-EventLogFloodProtectionNotifyInterval <Int32>] - [-EventLogFloodProtectionQuietPeriod <Int32>] [-EventLogFloodProtectionThreshold <Int32>] - [-EventLogFloodProtectionTriggerPeriod <Int32>] [-InputObject <PSObject>] [-LogCutInterval <Int32>] - [-LogDiskSpaceUsageGB <Int32>] [-LogLocation <String>] [-LogMaxDiskSpaceUsageEnabled] - [-ScriptErrorReportingDelay <Int32>] [-ScriptErrorReportingEnabled] [-ScriptErrorReportingRequireAuth] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPDiagnosticConfig` cmdlet to set diagnostic configuration settings on the entire farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Set-SPDiagnosticConfig -ErrorReportingEnabled -DownloadErrorReportingUpdatesEnabled:$false -DaysToKeepLog 60 -``` - -This example enables ErrorReporting, disables DownloadErrorReportingUpdatesEnable and sets DaysToKeepLog to 60. - - -### ------------------EXAMPLE 2----------------------- -``` -$config = Get-SPDiagnosticConfig -$config.CustomerExperienceImprovementProgramEnabled = $false -$config.LogCutInterval = 60 -$config | Set-SPDiagnosticConfig -``` - -This example disables CEIP and sets LogCutInterval to 60 minutes. - - -## PARAMETERS - -### -AllowLegacyTraceProviders -Specifies that trace providers built for previous versions of SharePoint Products and Technologies can write to the trace session for SharePoint Products. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AppAnalyticsAutomaticUploadEnabled -Specifies whether aggregated app usage data is automatically uploaded to Microsoft. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CustomerExperienceImprovementProgramEnabled -Specifies whether participation in the Customer Experience Improvement Program (CEIP) is enabled. - -The CEIP is designed to improve the quality, reliability, and performance of Microsoft products and technologies. -With your permission, anonymous information about your server is sent to Microsoft to help improve SharePoint Products. - -The type must be either of the following values: - -- $True -- $False - -The default value is $True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DaysToKeepLogs -Specifies the number of days to keep trace log files. -The type must be a valid number between 1 and 366. -The default value is 14 days. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -DownloadErrorReportingUpdatesEnabled -Specifies whether the error reporting remote control file is downloaded. - -The type must be either of the following values: - -- $True -- $False - -The default value is $True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ErrorReportingAutomaticUploadEnabled -Specifies whether error reports are uploaded to Microsoft automatically. - -Error reports include the following: information regarding the condition of the server when a problem occurs; the operating system version and computer hardware in use; and the digital product ID, which can be used to identify your license. -The IP address of your computer is also sent because you are connecting to an online service to send error reports; however, the IP address is used only to generate aggregate statistics. - -The type must be either of the following values: - -- $True -- $False - -The default value is $True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ErrorReportingEnabled -Specifies whether collection of error reports is enabled. - -Error reports are created when your system encounters hardware or software problems. -Microsoft and its partners actively use these reports to improve the reliability of the software. -Error reports include the following: information regarding the condition of the server when the problem occurs; the operating system version and computer hardware in use; and the digital product ID, which can be used to identify your license. -The IP address of your computer is also sent because you are connecting to an online service to send error reports; however, the IP address is used only to generate aggregate statistics. - -The type must be either of the following values: - -- $True -- $False - -The default value is $True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -EventLogFloodProtectionEnabled -Specifies whether the Event log flood protection feature is enabled. - -If multiple similar events are written to the event log, some duplicate messages are suppressed. -Then, after a period of time, a summary message is written that shows how many events were suppressed. - -The type must be either of the following values: - -- $True -- $False - -The default value is $True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -EventLogFloodProtectionNotifyInterval -Specifies in minutes how often to write a summary event indicating how many events were suppressed due to flood protection. - -The integer range is between 1 and 1440. -The default value is 5. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -EventLogFloodProtectionQuietPeriod -Specifies in minutes how much time must pass without an event firing to exit flood protection. - -The integer range is between 1 and 1440. -The default value is 2. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -EventLogFloodProtectionThreshold -Specifies the number of events allowed in a given timeframe before an event is considered to be flooding the event log. - -The integer range is between 1 and 100. -The default value is 5. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -EventLogFloodProtectionTriggerPeriod -Specifies in minutes the timeframe to watch for events that may be flooding. - -The integer range is between 1 and 1440. -The default value is 2. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -InputObject -Use the result from the `Get-SPDiagnosticConfig` cmdlet, make modifications and then pipeline the object into `Set-SPDiagnosticConfig` cmdlet to update the content database. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -LogCutInterval -Specifies the number of minutes between log file rollovers. - -The value must be a valid integer between 0 and 1440. - -The default value is 30. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -LogDiskSpaceUsageGB -Specifies the maximum amount of storage to use for trace log files, in gigabytes (GB). - -The default value is 1000 and only takes effect when the LogMaxDiskSpaceusageEnabled cmdlet is set to True. - -The type must be a valid number between 1 and 1000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -LogLocation -Specifies the path of where to log files will reside. - -The type must be a valid path, in the form C:\Logs. - -The default location is %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\14\Logs. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -LogMaxDiskSpaceUsageEnabled -Specifies whether to restrict the maximum space to use for trace log files. - -The type must be either of the following values: - -- $True -- $False - -The default value is $False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ScriptErrorReportingDelay -Specifies the time (in minutes) between script error reports. - -The type must be a valid integer between 0 and 1440. -The value is specified in minutes. - -The default value is 30. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ScriptErrorReportingEnabled -Specifies whether error reporting is enabled for client script errors. - -The type must be either of the following values: - -- $True -- $False - -The default value is $True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ScriptErrorReportingRequireAuth -Specifies whether script error reporting requires authentication. - -The type must be either of the following values: - -- $True -- $False - -The default value is $True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDiagnosticsProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDiagnosticsProvider.md deleted file mode 100644 index 491314e595..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDiagnosticsProvider.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spdiagnosticsprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPDiagnosticsProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPDiagnosticsProvider - -## SYNOPSIS -Enables a diagnostics provider and updates its retention policy. - - -## SYNTAX - -``` -Set-SPDiagnosticsProvider [-Identity] <SPDiagnosticsProviderPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DaysRetained <Int32>] [-Enable] [-WhatIf] - [-MaxTotalSizeInBytes <Int64>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPDiagnosticsProvider` cmdlet enables a diagnostics provider and updates its retention policy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Get-SPDiagnosticsProvider job-diagnostics-event-log-provider | Set-SPDiagnosticsProvider -Enable:$false -Get-SPDiagnosticsProvider job-diagnostics-event-log-provider -``` - -This example disables the event log diagnostics provider. - - -### ------------------EXAMPLE 2----------------------- -``` -Get-SPDiagnosticsProvider job-diagnostics-event-log-provider | Set-SPDiagnosticsProvider -Enable -DaysRetained 10 -Get-SPDiagnosticsProvider job-diagnostics-event-log-provider -``` - -This example enables the event log diagnostics provider and changes its retention policy to 10 days. - - -## PARAMETERS - -### -Identity -Specifies the diagnostics provider to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a diagnostic provider (for example, DiagnosticProv1); or an instance of a valid SPDiagnosticsProvider object. - -```yaml -Type: SPDiagnosticsProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DaysRetained -Specifies the number of days to retain the data collected by a diagnostics provider. - -The type must be a valid integer value in the range of 1 to 14. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -Turns on or off the specified diagnostics provider. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxTotalSizeInBytes -The maximum size of the partition within the Usage database. - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDistributedCacheClientSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDistributedCacheClientSetting.md deleted file mode 100644 index 85a294d9ea..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPDistributedCacheClientSetting.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spdistributedcacheclientsetting -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPDistributedCacheClientSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPDistributedCacheClientSetting - -## SYNOPSIS -Sets distributed cache settings. - - -## SYNTAX - -``` -Set-SPDistributedCacheClientSetting [-ContainerType] <SPDistributedCacheContainerType> - [-DistributedCacheClientSettings] <SPDistributedCacheClientSettings> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPDistributedCacheClientSettings` cmdlet to set the distributed cache service based on usage. -Usage can be any type of cache that the ContainerType parameter specifies. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$settings = Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache -$settings.MaxConnectionsToServer = 10 -Set-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache -DistributedCacheClientSettings $settings -``` - -This example updates the MaxConnectionsToServer to 10 for DistributedLogonTokenCache. - - -## PARAMETERS - -### -ContainerType -Specifies the container type to clear. - -The valid values are the following: - --DistributedDefaultCache - --DistributedAccessCache - --DistributedActivityFeedCache - --DistributedBouncerCache - --DistributedLogonTokenCache - --DistributedServerToAppServerAccessTokenCache - --DistributedSearchCache - --DistributedSecurityTrimmingCache - --DistributedActivityFeedLMTCache - --DistributedViewStateCache - - -```yaml -Type: SPDistributedCacheContainerType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DistributedCacheClientSettings -Updates the various cache client settings. -It is recommended to use the default settings. - -```yaml -Type: SPDistributedCacheClientSettings -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPDistributedCacheClientSetting](Get-SPDistributedCacheClientSetting.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEduServiceSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEduServiceSetting.md deleted file mode 100644 index 1e31f8ac84..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEduServiceSetting.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-speduservicesetting -applicable: SharePoint Server 2013 -title: Set-SPEduServiceSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEduServiceSetting - -## SYNOPSIS -Do not use - - -## SYNTAX - -``` -Set-SPEduServiceSetting [[-Enabled] <Boolean>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -Service <Services> -Site <SPSitePipeBind> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Do not use -``` - - - - -## PARAMETERS - -### -AssignmentCollection -Do not use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -Do not use - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Service -Do not use - -```yaml -Type: Services -Parameter Sets: (All) -Aliases: -Accepted values: Lync, Exchange, StudyGroup -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Do not use - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchAdministrationComponent.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchAdministrationComponent.md deleted file mode 100644 index f96358b5ff..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchAdministrationComponent.md +++ /dev/null @@ -1,206 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchadministrationcomponent -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchAdministrationComponent -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchAdministrationComponent - -## SYNOPSIS -Sets properties of an administration component for a search service application. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchAdministrationComponent [[-Identity] <AdminComponentPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] - [-SearchApplication <SearchServiceApplicationPipeBind>] - [-SearchServiceInstance <SearchServiceInstancePipeBind>] [-StoragePath <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The Set-SPEnterpriseSearchAdministrationComponent cmdlet updates properties of an AdministrationComponent object for a search service application. - -For permissions and the most current information about search cmdlets, see the online documentation, [https://go.microsoft.com/fwlink/?LinkId=163185](https://go.microsoft.com/fwlink/?LinkId=163185). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` - $ssa = Get-SPEnterpriseSearchServiceApplication "Search Service Application" - $admin = Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $ssa - $admin | Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance SP02 -Force -``` - -This example moves the administration component to a different server. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Specifies that the admin component must be moved to the new search service instance. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the administration component to update. - -The type must be a valid name (GUID), such as 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid AdminComponent object. - -```yaml -Type: AdminComponentPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the administration component. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchServiceInstance -Specifies the search service instance to host the administration component. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a search server (for example, MyQueryServer); or an instance of a valid SearchServiceInstance object. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StoragePath -Specifies the path for storing data for the administration component. The path must contain a valid file share and use valid registry characters. - -The type must be a valid path in either of the following forms: - -- C:\folder_name - -- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Server.Search.Cmdlet.AdminComponentPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchContentEnrichmentConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchContentEnrichmentConfiguration.md deleted file mode 100644 index 0f871b0cdb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchContentEnrichmentConfiguration.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchcontentenrichmentconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchContentEnrichmentConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchContentEnrichmentConfiguration - -## SYNOPSIS -Stores the specified content enrichment configuration to the search service application. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchContentEnrichmentConfiguration - -ContentEnrichmentConfiguration <ContentEnrichmentConfigurationPipeBind> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet validates the ContentEntrichmentConfiguration object and stores the provided configuration in the SearchServiceApplication. -Both a ContentEnrichmentConfiguration and a SearchServiceApplication object have to be provided. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1 ------------------ -``` -$config = New-SPEnterpriseSearchContentEnrichmentConfiguration -$config.Endpoint = "https://server/service" -$config.InputProperties = "Title", "Url" -$config.OutputProperties = "Title", "Url" -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SPEnterpriseSearchContentEnrichmentConfiguration -SearchApplication $ssa -ContentEnrichmentConfiguration $config -``` - -This example creates a new ContentEnrichmentConfiguration object. -The URL of the external web service is stored in the $config.Endpoint property. -The new ContentEnrichmentConfiguration is configured to use Title and URL, which are the managed properties that you want to send to the external web service. -It is also configured to expect the external web service to output the same managed properties. -The SearchServiceApplication object is retrieved and used for storing the newly created ContentEnrichmentConfiguration. - - -### ------------------EXAMPLE 2 ------------------ -``` -C:\PS>$config = New-SPEnterpriseSearchContentEnrichmentConfiguration -$config.Endpoint = "https://server/service" -$config.InputProperties = "Title" -$config.OutputProperties = "Title" -$config.Trigger = 'Contains(Title, "Example")' -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SPEnterpriseSearchContentEnrichmentConfiguration -SearchApplication $ssa -ContentEnrichmentConfiguration $config -``` - -This example creates a new ContentEnrichmentConfiguration object. -The URL of the external web service is stored in the $config.Endpoint property. -The new ContentEnrichmentConfiguration is configured to use Title, which is the managed property that you want to send to the external web service. -It is also configured to expect the external web service to output the same managed property. -The $config.Trigger is set to only send the managed property when the Boolean trigger expression is true, in this case when the managed property Title contains the string "Example". -The SearchServiceApplication object is retrieved, and used for storing the newly created ContentEnrichmentConfiguration. - - -## PARAMETERS - -### -ContentEnrichmentConfiguration -Specifies the ContentEnrichmentConfiguration that should be stored in the SearchServiceApplication. - -```yaml -Type: ContentEnrichmentConfigurationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the SearchServiceApplication that contains the ContentEnrichmentConfiguration. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchContentEnrichmentConfiguration](Get-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[New-SPEnterpriseSearchContentEnrichmentConfiguration](New-SPEnterpriseSearchContentEnrichmentConfiguration.md) - -[Remove-SPEnterpriseSearchContentEnrichmentConfiguration](Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlContentSource.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlContentSource.md deleted file mode 100644 index 84a74d0514..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlContentSource.md +++ /dev/null @@ -1,626 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchcrawlcontentsource -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchCrawlContentSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchCrawlContentSource - -## SYNOPSIS -Sets the properties of a crawl content source for a Search service application. - - -## SYNTAX - -### MonthlyDate -``` -Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] - [-BDCApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm] - [-CrawlPriority <CrawlPriority>] [-CrawlScheduleDaysOfMonth <Int32>] - [-CrawlScheduleMonthsOfYear <MonthsOfYear>] [-CrawlScheduleRepeatDuration <Int32>] - [-CrawlScheduleRepeatInterval <Int32>] [-CrawlScheduleStartDateTime <DateTime>] [-CustomProtocol <String>] - [-EnableContinuousCrawls <Boolean>] [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Int32>] - [-MaxSiteEnumerationDepth <Int32>] [-MonthlyCrawlSchedule] [-Name <String>] - [-ScheduleType <ContentSourceCrawlScheduleType>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [-StartAddresses <String>] [-Tag <String>] [-WhatIf] [<CommonParameters>] -``` - -### Weekly -``` -Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] - [-BDCApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm] - [-CrawlPriority <CrawlPriority>] [-CrawlScheduleDaysOfWeek <DaysOfWeek>] - [-CrawlScheduleRepeatDuration <Int32>] [-CrawlScheduleRepeatInterval <Int32>] - [-CrawlScheduleRunEveryInterval <Int32>] [-CrawlScheduleStartDateTime <DateTime>] [-CustomProtocol <String>] - [-EnableContinuousCrawls <Boolean>] [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Int32>] - [-MaxSiteEnumerationDepth <Int32>] [-Name <String>] [-ScheduleType <ContentSourceCrawlScheduleType>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-StartAddresses <String>] [-Tag <String>] - [-WeeklyCrawlSchedule] [-WhatIf] [<CommonParameters>] -``` - -### Daily -``` -Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] - [-BDCApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm] - [-CrawlPriority <CrawlPriority>] [-CrawlScheduleRepeatDuration <Int32>] [-CrawlScheduleRepeatInterval <Int32>] - [-CrawlScheduleRunEveryInterval <Int32>] [-CrawlScheduleStartDateTime <DateTime>] [-CustomProtocol <String>] - [-DailyCrawlSchedule] [-EnableContinuousCrawls <Boolean>] [-LOBSystemSet <String[]>] - [-MaxPageEnumerationDepth <Int32>] [-MaxSiteEnumerationDepth <Int32>] [-Name <String>] - -ScheduleType <ContentSourceCrawlScheduleType> [-SearchApplication <SearchServiceApplicationPipeBind>] - [-StartAddresses <String>] [-Tag <String>] [-WhatIf] [<CommonParameters>] -``` - -### RemoveSchedule -``` -Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] - [-BDCApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm] - [-CrawlPriority <CrawlPriority>] [-CustomProtocol <String>] [-EnableContinuousCrawls <Boolean>] - [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Int32>] [-MaxSiteEnumerationDepth <Int32>] - [-Name <String>] [-RemoveCrawlSchedule] [-ScheduleType <ContentSourceCrawlScheduleType>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-StartAddresses <String>] [-Tag <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPEnterpriseSearchCrawlContentSource` cmdlet updates the rules of a crawl content source when the search functionality is initially configured and after any new content source is added. -This cmdlet is called once to set the incremental crawl schedule for a content source and it is called again to set a full crawl schedule. - -The value of the optional EnableContinuousCrawls parameter can be True or False. -A value of True enables continuous crawls of items in this content source. -This causes the search system to automatically start incremental crawls to process the latest changes to items in the corresponding data repositories. -This helps to keep the index fresh for items in this content source. -Search service application administrators can still configure full crawls as needed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$cs = Get-SPEnterpriseSearchCrawlContentSource -Identity 'Local SharePoint Sites' -SearchApplication $ssa -$cs | Set-SPEnterpriseSearchCrawlContentSource -ScheduleType Full -DailyCrawlSchedule -CrawlScheduleRunEveryInterval 30 -$cs | Set-SPEnterpriseSearchCrawlContentSource -ScheduleType Incremental -DailyCrawlSchedule -CrawlScheduleRepeatInterval 60 -CrawlScheduleRepeatDuration 1440 -``` - -This example returns the "Local SharePoint Sites" content source and creates a schedule to run a full crawl every 30 days and an incremental crawl every hour every day. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BDCApplicationProxyGroup -Specifies the proxy to use for a business type content source. -This proxy group must contain a default Business Data Connectivity Metadata Store proxy. - - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlPriority -Specifies the priority of this content source. - -The type must be one of the following integers: 1= Normal, 2=High. - - -```yaml -Type: CrawlPriority -Parameter Sets: (All) -Aliases: p -Accepted values: Normal, High -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlScheduleDaysOfMonth -Specifies the days on which to crawl when the MonthlyCrawlSchedule parameter is set. - - -```yaml -Type: Int32 -Parameter Sets: MonthlyDate -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlScheduleDaysOfWeek -Specifies the days on which to crawl when the WeeklyCrawlSchedule parameter is set. - - -```yaml -Type: DaysOfWeek -Parameter Sets: Weekly -Aliases: -Accepted values: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Weekdays, Saturday, Weekends, Everyday -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlScheduleMonthsOfYear -Specifies the months on which to crawl when the MonthlyCrawlSchedule parameter is set. - - -```yaml -Type: MonthsOfYear -Parameter Sets: MonthlyDate -Aliases: month -Accepted values: January, February, March, April, May, June, July, August, September, October, November, December, AllMonths -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlScheduleRepeatDuration -Specifies the number of times to repeat the crawl schedule. - - -```yaml -Type: Int32 -Parameter Sets: MonthlyDate, Weekly, Daily -Aliases: duration -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlScheduleRepeatInterval -Specifies the number of minutes between each repeat interval for the crawl schedule - - -```yaml -Type: Int32 -Parameter Sets: MonthlyDate, Weekly, Daily -Aliases: interval -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlScheduleRunEveryInterval -Specifies the interval between crawls. - -When the DailyCrawlSchedule parameter is set, specifies the number of days between crawls. - -When the WeeklyCrawlSchedule parameter is set, specifies the number of weeks between crawls. - - -```yaml -Type: Int32 -Parameter Sets: Weekly, Daily -Aliases: every -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlScheduleStartDateTime -Specifies the initial date of the crawl. -The default value is midnight on the current day. - - -```yaml -Type: DateTime -Parameter Sets: MonthlyDate, Weekly, Daily -Aliases: start -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CustomProtocol -Specifies the custom protocol, handled by the custom connector, to use for this content source. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DailyCrawlSchedule -Base schedule on days between crawls. - - -```yaml -Type: SwitchParameter -Parameter Sets: Daily -Aliases: daily -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableContinuousCrawls -Specifies the value of the EnableContinuousCrawls parameter: True or False. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the crawl content source to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a ContentSource object (for example, ContentSource1); or an instance of a valid ContentSource object. - - -```yaml -Type: ContentSourcePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -LOBSystemSet -Specifies a comma-separated list of Business Data Connectivity Metadata Store system names and system instance names for a business type content source. - - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxPageEnumerationDepth -Specifies, for a web or custom type content source, the number of page hops that the crawler can make from the start address to a content item. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSiteEnumerationDepth -Specifies, for a web or custom type content source, the number of site hops that the crawler can take from the start address to a content item. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MonthlyCrawlSchedule -Base the schedule on months between crawls. - - -```yaml -Type: SwitchParameter -Parameter Sets: MonthlyDate -Aliases: monthly -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the new display name for the content source. - -The type must be a valid name of a content source; for example, ContentSource1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveCrawlSchedule -Deletes the specified crawl. - - -```yaml -Type: SwitchParameter -Parameter Sets: RemoveSchedule -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScheduleType -Specifies the type of crawl schedule. - -The type must be one of the following values: Full or Incremental. - - -```yaml -Type: ContentSourceCrawlScheduleType -Parameter Sets: MonthlyDate, Weekly, RemoveSchedule -Aliases: -Accepted values: Full, Incremental, Full, Incremental -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: ContentSourceCrawlScheduleType -Parameter Sets: Daily -Aliases: -Accepted values: Full, Incremental, Full, Incremental -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the content source. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartAddresses -Specifies the comma-separated list of URLs at which to start a crawl for this content source. - -The type must be a valid URL, in the form https://server_name. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: s -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tag -Specifies the URL for the page to modify the settings for a custom content source. -The string that specifies the URL can contain a maximum of 1,024 characters. - -The type must be a valid URL, in the form https://server_name. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: t -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WeeklyCrawlSchedule -Base the schedule on weeks between crawls. - - -```yaml -Type: SwitchParameter -Parameter Sets: Weekly -Aliases: weekly -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Server.Search.Cmdlet.ContentSourcePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlDatabase.md deleted file mode 100644 index e0361fb68a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlDatabase.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchcrawldatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchCrawlDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchCrawlDatabase - -## SYNOPSIS -Sets properties of a crawl database for a Search service application. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchCrawlDatabase [-Identity] <CrawlStorePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-FailoverDatabaseServer <String>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [-DatabaseName <String>] - [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPEnterpriseSearchCrawlDatabase` cmdlet sets properties of a specified crawl database for a Search service application. -A crawl database stores crawl history for a Search service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SPEnterpriseSearchCrawlDatabase -Identity SearchApp_CrawlStore -SearchApplication $ssa -FailoverDatabaseServer \\failoverServer -``` - -This example sets the failover database server for the crawl database, SearchApp_CrawlStore, to the \\\\failoverServer server. - - -## PARAMETERS - -### -Identity -Specifies the crawl database to modify. - -A valid crawl database name, in the form CrawlStore1; or a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid CrawlStore object. - -```yaml -Type: CrawlStorePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the server to be used for failover when SQL Server mirroring is used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the name of the search application to which the crawl database applies. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database to create for the crawl database. The type must be a valid name of a SQL Server database; for example, CrawlStoreDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the Microsoft SQL Server database server. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the account name on the Database Server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlLogReadPermission.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlLogReadPermission.md deleted file mode 100644 index 9b17533866..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlLogReadPermission.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchcrawllogreadpermission -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchCrawlLogReadPermission -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchCrawlLogReadPermission - -## SYNOPSIS -Grants users permission to view the crawl log information. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchCrawlLogReadPermission [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Identity <CrawlLogReadPermissionPipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [-Tenant <Guid>] [-UserNames <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Only the Search Service Application administrator can use this cmdlet. - -The administrator uses the `Set-SPEnterpriseSearchCrawlLogReadPermission` cmdlet to grant users permission to view crawl log information. -The administrator can choose to restrict the permission to crawl log information from a particular tenant. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$crawlLogPermission = Get-SPEnterpriseSearchCrawlLogReadPermission -SearchApplication $ssa -Tenant "00000000-0000-0000-0000-000000000001" -Set-SPEnterpriseSearchCrawlLogReadPermission -Identity $crawlLogPermission -SearchApplication $ssa -UserNames "user1;user2" -Tenant "00000000-0000-0000-0000-000000000001" -``` - -This example first defines $crawlLogPermission, which is the list of users who have permission to view the crawl log information from the tenant with id "00000000-0000-0000-0000-000000000001" on the search application referenced by $ssa. -Then the example uses the `Set-SPEnterpriseSearchCrawlLogReadPermission` cmdlet to add user1 and user2 to the list of users referenced by $crawlLogPermission. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the crawl log permissions list to which users should be added. - -```yaml -Type: CrawlLogReadPermissionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the crawl log. -The type must be a valid GUID, of the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the users shall be added to the crawl log permissions list within the scope of this tenant only. -The type must be a valid GUID of the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserNames -Specifies the user names that shall be granted permission to view the crawl log information Use "domain\username" or "username". -When adding several user names, separate names with semi-colons. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchCrawlLogReadPermission](Get-SPEnterpriseSearchCrawlLogReadPermission.md) - -[Remove-SPEnterpriseSearchCrawlLogReadPermission](Remove-SPEnterpriseSearchCrawlLogReadPermission.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlRule.md deleted file mode 100644 index ff76862255..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchCrawlRule.md +++ /dev/null @@ -1,352 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchcrawlrule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchCrawlRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchCrawlRule - -## SYNOPSIS -Sets properties for a crawl rule. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchCrawlRule [-AccountName <String>] [-AccountPassword <SecureString>] - [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationType <CrawlRuleAuthenticationType>] - [-Confirm] [-ContentClass <String>] [-CrawlAsHttp <Boolean>] [-FollowComplexUrls <Boolean>] - -Identity <CrawlRulePipeBind> [-IsAdvancedRegularExpression <Boolean>] [-PluggableSecurityTimmerId <Int32>] - [-Priority <Int32>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-SuppressIndexing <Boolean>] - [-Type <CrawlRuleType>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -A search administrator runs the `Set-SPEnterpriseSearchCrawlRule` cmdlet at initial search configuration or any other time, to set or update various attributes of a crawl rule. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$crawlRule = Get-SPEnterpriseSearchCrawlRule -Identity 'file://fileserver/root' -SearchApplication $ssa -Set-SPEnterpriseSearchCrawlRule -Identity $crawlRule -Type "ExclusionRule" -``` - -This example sets the type of the crawl rule pertaining to the URL, file://fileserver/root, to exclude this path from future crawls. - - -## PARAMETERS - -### -AccountName -Specifies the name of the account to be used to crawl content identified by the crawl rule. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AccountPassword -Specifies the password for AccountName. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationType -Specifies one of the following authentication types: - -- BasicAccountRuleAccess -Specifies basic authentication. - -- CertificateRuleAccess -Specifies the X.509 certificate name. - -- NTLMAccountRuleAccess -Specifies the account name for integrated authentication. - - -```yaml -Type: CrawlRuleAuthenticationType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentClass -Specifies a string that is sent to the protocol handler for any content that matches the crawl rule. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawlAsHttp -Specifies whether the crawler crawls content from a hierarchical content source as HTTP content. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FollowComplexUrls -Specifies whether the index engine crawls content from URLs that contain a question mark (?). - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the name of the crawl rule. - -The type must be a valid crawl rule URL, such as https://server_name, or an instance of a valid CrawlRule object. - - -```yaml -Type: CrawlRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsAdvancedRegularExpression -Specifies whether the rule has full regular expression syntax. - -The default value is False. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PluggableSecurityTimmerId -Specifies the ID of the custom pluggable security trimmer to use, if registered. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -Defines where in the list of crawl rules this crawl rule is to be applied. - -The priority value cannot be less than 0 or greater than or equal to the number of crawl rules for the search application. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -The name of the search application that is associated with the crawl rule to be modified. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SuppressIndexing -Specifies whether the crawler excludes the content of items, to which this rule applies, from the content index. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type of crawl rule. -A value of zero (0) includes the rule and a value of 1 excludes the rule. - - -```yaml -Type: CrawlRuleType -Parameter Sets: (All) -Aliases: t -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchFileFormatState.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchFileFormatState.md deleted file mode 100644 index 143f53f894..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchFileFormatState.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchfileformatstate -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchFileFormatState -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchFileFormatState - -## SYNOPSIS -Sets the activation state of a parser for a given file format. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchFileFormatState [-Identity] <DocumentParserFileFormatStatePipeBind> [-Enable] <Boolean> - -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [-UseIFilter <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPEnterpriseSearchFileFormatState` cmdlet sets the activation state of the parser that corresponds to the specified file format. -By default, the initial activation state of all file formats is $TRUE (enabled). -Use this cmdlet to temporarily disable a malfunctioning parser. -The system will only consider the change after a restart of the content processing components. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity PDF -Enable $false -``` - -This example uses the `Set-SPEnterpriseSearchFileFormatState` cmdlet to disable the parser for the file format "PDF". - - -## PARAMETERS - -### -Identity -Specifies the identification of the format to be disabled or enabled. - - -```yaml -Type: DocumentParserFileFormatStatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Enable -Specifies the activation state of the parser that corresponds to the specified file format. -The activation state can be $FALSE (disabled) or $TRUE (enabled). - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the name of the search application. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseIFilter -Specifies use of a third-party iFilter when parsing the file format. UseIFilter can be $false (built-in format handler is used) or $TRUE (third-party iFilter is used). $false is the default value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216 (https://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchFileFormat](New-SPEnterpriseSearchFileFormat.md) - -[Get-SPEnterpriseSearchFileFormat](Get-SPEnterpriseSearchFileFormat.md) - -[Remove-SPEnterpriseSearchFileFormat](Remove-SPEnterpriseSearchFileFormat.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchLinguisticComponentsStatus.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchLinguisticComponentsStatus.md deleted file mode 100644 index 193182666d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchLinguisticComponentsStatus.md +++ /dev/null @@ -1,210 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchlinguisticcomponentsstatus -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchLinguisticComponentsStatus -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchLinguisticComponentsStatus - -## SYNOPSIS -Sets the operation status of the linguistic query and document processing components. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchLinguisticComponentsStatus [-AllEnabled <Boolean>] - [-AssignmentCollection <SPAssignmentCollection>] [-EntityExtractionEnabled <Boolean>] - [-Identity <LinguisticComponentsStatusPipeBind>] [-QuerySpellingEnabled <Boolean>] - -SearchApplication <SearchServiceApplicationPipeBind> [-StemmingEnabled <Boolean>] - [-ThesaurusEnabled <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet sets the operational status of the linguistic query and document processing components. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SpEnterpriseSearchLinguisticComponentsStatus -SearchApplication $ssa -StemmingEnabled $false -``` - -This example shows how to disable stemming during query processing by setting the parameter StemmingEnabled to false. - - -### ------------------EXAMPLE 2----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SpEnterpriseSearchLinguisticComponentsStatus -SearchApplication $ssa -AllEnabled $false -``` - -This example shows how to disable all linguistic query and document processing functionalities. - - -## PARAMETERS - -### -AllEnabled -A Boolean value to enable or deactivate all linguistic functionalities. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -EntityExtractionEnabled -A Boolean value to enable or deactivate the company extractor and all custom extractors during document processing. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -An object that represents the current status of the linguistic components. - - -```yaml -Type: LinguisticComponentsStatusPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -QuerySpellingEnabled -A Boolean value to enable or deactivate query spelling correction. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the linguistic processing components. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StemmingEnabled -A Boolean value to enable or deactivate expansive stemming during query processing. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThesaurusEnabled -A Boolean value to enable or deactivate thesaurus lookup during query processing. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchLinguisticComponentsStatus](Get-SPEnterpriseSearchLinguisticComponentsStatus.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchLinksDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchLinksDatabase.md deleted file mode 100644 index d1e4e1497d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchLinksDatabase.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchlinksdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchLinksDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchLinksDatabase - -## SYNOPSIS -Sets properties of a links database for a search service application. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchLinksDatabase [-Identity] <LinksStorePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseName <String>] - [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] - [-FailoverDatabaseServer <String>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPEnterpriseSearchLinksDatabase` cmdlet sets properties of a specified links database for a search service application. -A links database stores query logging and analytics information. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp -Set-SPEnterpriseSearchLinksDatabase -Identity SearchApp_LinksStore -SearchApplication $ssa -FailoverDatabaseServer \\failoverServer -``` - -This example sets the failover database server to \\\\failoverServer for the links database SearchApp_LinksStore in the search service application mySearchServiceApp. - - -## PARAMETERS - -### -Identity -Specifies the links database to modify. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a LinksStore object, in the form LinksStore1; or an instance of a valid LinksStore object. - -```yaml -Type: LinksStorePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the links database name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password of the account to connect to the database. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the server to use for the host SQL database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the name of the account to connect to the database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the server to use for failover when using SQL Server mirroring. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the links database. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchLinksDatabase](New-SPEnterpriseSearchLinksDatabase.md) - -[Get-SPEnterpriseSearchLinksDatabase](Get-SPEnterpriseSearchLinksDatabase.md) - -[Remove-SPEnterpriseSearchLinksDatabase](Remove-SPEnterpriseSearchLinksDatabase.md) - -[Move-SPEnterpriseSearchLinksDatabases](Move-SPEnterpriseSearchLinksDatabases.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataCategory.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataCategory.md deleted file mode 100644 index 1ef9542456..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataCategory.md +++ /dev/null @@ -1,239 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchmetadatacategory -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchMetadataCategory -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchMetadataCategory - -## SYNOPSIS -Sets properties of a crawled property category. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchMetadataCategory [-AssignmentCollection <SPAssignmentCollection>] - [-AutoCreateNewManagedProperties <Boolean>] [-Confirm] [-DiscoverNewProperties <Boolean>] - -Identity <CategoryPipeBind> [-MapToContents <Boolean>] [-Name <String>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a crawled property category when the search functionality is configured for the first time and after a new crawled property category is discovered during a crawl. -SPEnterpriseSearchMetadataCategory represents a category in the enterprise search metadata property schema. - -Note that a category may represent multiple propsets. -Changes to the category will overwrite all propsets. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SPEnterpriseSearchMetadataCategory -Identity People -SearchApplication $ssa -DiscoverNewProperties $false -MapToContents $false -``` - -This example sets both DiscoverNewProperties and MapToContents properties to False for the People category for the default search service application. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AutoCreateNewManagedProperties -Specifies that when a new crawled property in this category is found, a corresponding managed property is created and mapped to this new crawled property. - -Note: -Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: auto -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiscoverNewProperties -Specifies that if there are unknown properties in this category, these new properties are discovered during a crawl. - -Note: -Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the metadata category to update. - -The type must be a valid name of a metadata category, for example, MetadataCategory1, or an instance of a valid Category object. - - -```yaml -Type: CategoryPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MapToContents -Specifies that all crawled properties of type string are mapped to corresponding managed properties of this category. - -Note: -Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: m -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the enterprise search metadata category. - -The type must be a valid name of a metadata category, for example MetadataCategory1. - -Note: -Null indicates that the value is unchanged. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the enterprise search metadata categories. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataCrawledProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataCrawledProperty.md deleted file mode 100644 index 2cb3d7f372..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataCrawledProperty.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchmetadatacrawledproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchMetadataCrawledProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchMetadataCrawledProperty - -## SYNOPSIS -Sets the properties of a metadata crawled property. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchMetadataCrawledProperty [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -Identity <CrawledPropertyPipeBind> -IsMappedToContents <Boolean> [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a crawled property when the search functionality is configured for the first time and after any new crawled property is added to create the rules for the crawled property. -SPEnterpriseSearchMetadataCrawledProperty represents a crawled property in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$crawlprop = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Name MyCrawlProp -Set-SPEnterpriseSearchMetadataCrawledProperty -Identity $crawlprop -IsMappedToContent $true -``` - -This example sets the IsMappedToContent parameter of the crawled property MyCrawlProp to false (see the example for the `New-SPEnterpriseSearchMetadataCrawledProperty` command) for the default search service application. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the crawled property to update. - -The type must be an instance of a valid CrawledProperty object. - - -```yaml -Type: CrawledPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsMappedToContents -Specifies that the crawled property is mapped to managed properties. -Specify true to map a crawled property to a managed property. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: im -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataManagedProperty.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataManagedProperty.md deleted file mode 100644 index 3084a98f13..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataManagedProperty.md +++ /dev/null @@ -1,486 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchmetadatamanagedproperty -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchMetadataManagedProperty -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchMetadataManagedProperty - -## SYNOPSIS -Sets the properties of a metadata managed property. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchMetadataManagedProperty [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DefaultForQueryIndependentRank <UInt32>] [-Description <String>] [-EnabledForQueryIndependentRank <Boolean>] - [-EnabledForScoping <Boolean>] [-FullTextQueriable <Boolean>] -Identity <ManagedPropertyPipeBind> - [-IncludeInAlertSignature <Boolean>] [-IncludeInMd5 <Boolean>] [-Name <String>] [-NameNormalized <Boolean>] - [-NoWordBreaker <Boolean>] [-RemoveDuplicates <Boolean>] [-RespectPriority <Boolean>] [-Retrievable <Boolean>] - [-SafeForAnonymous <Boolean>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-SiteCollection <Guid>] - [-Tenant <Guid>] [-UserFlags <Int16>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates the properties of a managed property. -It is typically used to change the name or description of a managed property. -SPEnterpriseSearchMetadataManagedProperty represents a managed property in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $ssa -Identity UserName -EnabledForScoping $true -``` - -This example sets the EnabledForScoping property to true for the managed property named UserName in the default search service application. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultForQueryIndependentRank -Specifies that the managed property is mandatory when it is used in query-independent rank (relevance). - -Note: -Null indicates that the value is unchanged. - - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: def -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Adds a description to the metadata managed property. - -The type must be a valid string. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnabledForQueryIndependentRank -Specifies that the managed property is mandatory when it is used in the custom ranking model for the query-independent work of ranking. - -The type must be one of the following query-independent ranking features in the custom model XML: - -- queryIndependentFeature -- categoryFeature -- languageFeature - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: qir -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnabledForScoping -Specifies that the managed property can be used in a scope definition. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: e -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FullTextQueriable -Specifies that the managed property can be used in enterprise search SQL queries. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: f -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the managed property to update. - -The type must be a valid name of a managed property, for example, ManagedProperty1, or an instance of a valid ManagedProperty object - - -```yaml -Type: ManagedPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IncludeInAlertSignature -Specifies whether this managed property should be included in alert signature. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: ia -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeInMd5 -Specifies that the managed property is included in the hash used by the crawler to determine whether a document has changed. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: im5 -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies a name for the managed property. - -The type must be a valid managed property name, for example ManagedProperty1. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NameNormalized -Specifies if the values of the managed property should be normalized, that is, enable to return results independent of letter casing and diacritics used in the query. -If value is set to true, the values are normalized. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: nn -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoWordBreaker -Specifies that the values for this managed property are processed by a word breaker. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: nw -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveDuplicates -Specifies that duplicate values for the managed property are removed. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: rd -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RespectPriority -Specifies that when a mapped crawled property contains multiple values and RespectPriority is set to true, only the first mapped crawled property is copied. -Otherwise, all mapped crawled properties that have a value are copied. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: rp -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Retrievable -Specifies whether the values for this managed property are retrievable or not. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: r -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SafeForAnonymous -Specifies whether it is acceptable to display the contents of the property in search results for anonymous searches. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: sfa -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the managed property collection. - -The type must be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the managed properties returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the managed properties returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserFlags -Reserved for future use. - -Note: Null indicates that the value is unchanged. - - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataMapping.md deleted file mode 100644 index f25072a1f2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchMetadataMapping.md +++ /dev/null @@ -1,234 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchmetadatamapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchMetadataMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchMetadataMapping - -## SYNOPSIS -Sets the properties of a managed property mapping for a search service application. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchMetadataMapping [-Identity] <MappingPipeBind> - [-SearchApplication <SearchServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-CrawledProperty <CrawledPropertyPipeBind>] [-ManagedProperty <ManagedPropertyPipeBind>] - [-SiteCollection <Guid>] [-Tenant <Guid>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a managed property mapping. -SPEnterpriseSearchMetadataMapping represents a mapping between a managed property and one or more crawled properties in the enterprise search metadata property schema. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -## get the crawl property to set to, in this case a new property is created -$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $ssa -Identity People -$cp = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Category $cat -Limit 1 -$ncp = New-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Name "MyNewCrawlProp" -PropSet $cp.PropSet -Category $cp.CategoryName -IsNameEnum $false -VariantType $cp.VariantType -IsMappedToContents $true -## get the mapping to replace -$mycp = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Name MyCrawlProp -$map = Get-SPEnterpriseSearchMetadataMapping -SearchApplication $ssa -ManagedProperty $mp -CrawledProperty $mycp -## set the new crawl property to map to for this mapping -Set-SPEnterpriseSearchMetadataMapping -Identity $map -SearchApplication $ssa -CrawledProperty $ncp -``` - -This example updates an existing mapping between the managed property UserName and the crawled property MyCrawlProp (see `New-SPEnterpriseSearchMetadataMapping`) for the default search service application. -The crawled property is replaced with a new crawled property named MyNewCrawlProp. - - -## PARAMETERS - -### -Identity -Specifies the metadata mapping to update. - -The type must be a valid URL, in the form https://server_name, or an instance of a valid Mapping object. - -```yaml -Type: MappingPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the metadata mapping. - -The type be a valid search application name, for example, SearchApp1, or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrawledProperty -Specifies the crawled property to map. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid URL in the form https://server_name, or an instance of a valid CrawledProperty object. - -Note: Null indicates that the value is unchanged. - -```yaml -Type: CrawledPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedProperty -Specifies the managed property to receive the crawled property mapping. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a managed property, for example, ManagedProperty1, or an instance of a valid ManagedProperty object. - -Note: Null indicates that the value is unchanged. - -```yaml -Type: ManagedPropertyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollection -Specifies that the metadata mappings returned are to be within the scope of a site collection (SPSite). - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies that the metadata mappings returned are to be within the scope of a tenant. - -The type must be a valid GUID that specifies the property set in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchPrimaryHostController.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchPrimaryHostController.md deleted file mode 100644 index f2e89eac1d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchPrimaryHostController.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchprimaryhostcontroller -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchPrimaryHostController -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchPrimaryHostController - -## SYNOPSIS -Sets the primary search host controller for the farm. - -## SYNTAX - -``` -Set-SPEnterpriseSearchPrimaryHostController [-SearchServiceInstance] <SearchServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet sets the primary SearchHostController for the farm to the defined SearchHostController. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$si = Get-SPEnterpriseSearchServiceInstance -Local -Set-SPEnterpriseSearchPrimaryHostController $si -``` - -This example sets the local SearchHostController instance as the new primary SearchHostController. -It is up to the user to select the HostController with latest version available. - -If you choose a SearchHostController that is not running the latest version of the repository, you will have to confirm before you continue. - - -### ------------------EXAMPLE 2------------------ -``` -$si = Get-SPEnterpriseSearchServiceInstance -Local -Set-SPEnterpriseSearchPrimaryHostController $si -Force -``` - -This example sets the local SearchHostController instance as the new primary SearchHostController. - -If you choose a SearchHostController that is not running the latest version of the repository, you will not get a confirmation message before you continue. - - -## PARAMETERS - -### -SearchServiceInstance -SearchServiceInstance of the server from where the SearchHostController object is returned. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Force the change of the primary SearcHostController. -No confirmation messages are asked, even if user tries to set primary to a SearchHostController not running the latest version of the repository. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryAuthority.md deleted file mode 100644 index 3021e3066f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryAuthority.md +++ /dev/null @@ -1,190 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchqueryauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchQueryAuthority -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchQueryAuthority - -## SYNOPSIS -Sets the properties of an authoritative page for a shared search application. - -## SYNTAX - -``` -Set-SPEnterpriseSearchQueryAuthority [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - -Identity <AuthorityPagePipeBind> [-Level <Single>] -Owner <SearchObjectOwner> - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPEnterpriseSearchQueryAuthority` cmdlet updates properties of an authoritative page and adjusts the query rank of an authoritative page. -SPEnterpriseSearchQueryAuthority represents authoritative sites that rank higher in relevance than demoted sites, which are de-emphasized in relevance. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Set-SPEnterpriseSearchQueryAuthority -Identity https://contoso.com -Level 0.5 -SearchApplication MySSA -``` - -This example adjusts the authoritative level of the URL https://contoso.com to 0.5 on the search service application named MySSA. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the query authority page to update. - -The type must be a valid URL, in the form https://server_name; or an instance of a valid AuthorityPage object. - - -```yaml -Type: AuthorityPagePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Level -Specifies the level of the new authoritative page. -Authoritative pages, designated by the service application administrator, are expert pages that link to the most relevant information. -Because a search service application can have several designated authoritative pages, you use the Level property to specify the value of a specific page. -This parameter sets the level for the most valuable authoritative pages to 0. - -The type must be one of the following floating-point numbers: 0, 1, or 2. - - -```yaml -Type: Single -Parameter Sets: (All) -Aliases: l -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding Query Authority is created. The owner must be one of the following valid levels:- Search Service Application- Site Subscription - - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the authority page collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryKeyword.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryKeyword.md deleted file mode 100644 index ee53eab791..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryKeyword.md +++ /dev/null @@ -1,273 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchquerykeyword -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchQueryKeyword -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchQueryKeyword - -## SYNOPSIS -Sets the properties of a keyword term for a shared search application. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchQueryKeyword [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Contact <String>] [-Definition <String>] [-EndDate <DateTime>] -Identity <KeywordPipeBind> - [-ReviewDate <DateTime>] -Site <SPSitePipeBind> [-StartDate <DateTime>] [-Term <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPEnterpriseSearchQueryKeyword` cmdlet updates properties and rules of a keyword term. -A query keyword is a query component of a query topology. -SPEnterpriseSearchQueryKeyword represents relevance setting through keywords. - -You can use this cmdlet for keywords in site collections that are in SharePoint Server mode. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchQueryKeyword -Identity Engineering -Site https://myserver/sites/engineering | Set-SPEnterpriseSearchQueryKeyword -StartDate "12/25/2009" -EndDate "12/24/2010" -Site https://myserver/sites/engineering -``` - -This example gets a reference to the keyword with the term Engineering from the site https://myserver/sites/engineering and sets the start dates and end dates for the keyword. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Contact -Specifies the user name associated with the new keyword. - -The type must be a valid user name; for example, KeywordUser1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: c -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Definition -Specifies the definition of the new keyword term. - -The type must be a valid string; for example, a keyword term definition. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndDate -Specifies the expiration date of the keyword term. -The default value is MaxDate. - -The type must be a valid DateTime type, in the form 2010,12,05. - - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: e -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the keyword term to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid string that contains a keyword term (for example, KeywordTerm1); or an instance of a valid Keyword object. - - -```yaml -Type: KeywordPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ReviewDate -Specifies the review date of the keyword term. -The default value is MaxDate. - -The type must be a valid DateTime type, in the form 2010,12,05. - - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: r -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Site -Associates the new keyword term to the specified results URL. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDate -Specifies the activation date for the keyword term. -The default value is the current date. - -The type must be a valid date, in the form 2010,12,05. - - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: s -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Term -Specifies the keyword term that triggers keyword results. - -The type must be a valid string; for example, a keyword term. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: t -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryScope.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryScope.md deleted file mode 100644 index 9bdf3bad18..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryScope.md +++ /dev/null @@ -1,274 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchqueryscope -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchQueryScope -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchQueryScope - -## SYNOPSIS -Sets the properties of a query results scope for a shared search application. - -## SYNTAX - -``` -Set-SPEnterpriseSearchQueryScope -AlternateResultsPage <String> - [-AssignmentCollection <SPAssignmentCollection>] [-CompilationType <Int32>] [-Confirm] [-Description <String>] - [-DisplayInAdminUI <Boolean>] -Identity <ScopePipeBind> [-Name <String>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-Url <Uri>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -After you upgrade a Search service application to SharePoint Server, you can view shared scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for shared scopes after upgrade. -However, you can convert shared scopes to result sources, which serve a similar purpose. -Similarly, after you upgrade to Sharepoint Server Site Collection to SharePoint Server mode, you can view local scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for local scopes after you upgrade a site collection. -However, you can convert local scopes to result sources, which serve a similar purpose. - -The `Set-SPEnterpriseSearchQueryScope` cmdlet updates properties of a shared scope. -SPEnterpriseSearchQueryScope represents a query results scope used by all shared search applications on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPenterpriseSearchServiceApplication -Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa | Set-SPEnterpriseSearchQueryScope -Description "Business critical sites to index" -CompilationType 1 -AlternateResultsPage https://altServer -``` - -This example obtains a reference to the scope named MustCrawl on the search service application named MySSA and changes the description, compilation type and alternate access URL. - - -## PARAMETERS - -### -AlternateResultsPage -Specifies the location to display results for the new query scope. - -The type must be a valid URL, in the form https://server_name. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompilationType -Specifies the compilation type of the new scope. -The value 0 specifies the conditionally compiled scope type, and the value 1 specifies the always compiled scope type. - -The type must be either of the following: 0 or 1. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: type -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Adds a description of the new query scope. - -The type must be a valid string; for example, a description of a query scope. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: d -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayInAdminUI -Specifies that the new scope is displayed in the administration application user interface (UI). -The default setting is to hide the new scope in the administration application UI. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: disp -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the identity of the scope to create. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope (for example, Scope1); or an instance of a valid Scope object. - - -```yaml -Type: ScopePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies a name for the query scope. - -The type must be a valid name of a query scope; for example, QueryScope1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Filters to delete scopes for the specified results URL. - -The type must be a valid URL, in the form https://server_name. - - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryScopeRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryScopeRule.md deleted file mode 100644 index 83fb4e2319..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQueryScopeRule.md +++ /dev/null @@ -1,280 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchqueryscoperule -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchQueryScopeRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchQueryScopeRule - -## SYNOPSIS -Sets the properties of a shared scope rule for a query scope. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchQueryScopeRule [-Identity] <ScopeRulePipeBind> -Url <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-FilterBehavior <String>] - [-ManagedPropertyName <String>] [-MatchingString <String>] [-PropertyValue <String>] [-Scope <ScopePipeBind>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-UrlScopeRuleType <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -After you upgrade a Search service application SharePoint Server, you can view shared scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for shared scopes after upgrade. -However, you can convert shared scopes to result sources, which serve a similar purpose. -Similarly, after you upgrade a SharePoint Server site collection to SharePoint Server mode, you can view local scopes, but you cannot create, update, or delete them. -Therefore, you cannot use this cmdlet for local scopes after you upgrade a site collection. -However, you can convert local scopes to result sources, which serve a similar purpose. - -The `Set-SPEnterpriseSearchQueryScopeRule` cmdlet updates the properties of a query scope. -SPEnterpriseSearchQueryScopeRule represents a query results scope rule that can be applied to a scope. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa -Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url https://criticalSite | Set-SPEnterpriseSearchQueryScopeRule -Url https://criticalSite -UrlScopeRuleType Url -``` - -This example gets a reference to a scope rule for the URL https://criticalSite and sets its rule type to Url. - - -## PARAMETERS - -### -Identity -Specifies the scope rule to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope rule (for example, ScopeRule1); or an instance a valid ScopeRule object. - -```yaml -Type: ScopeRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -Specifies the results URL that is associated with the query scope rule. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: u -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterBehavior -Specifies the type of scope rule to create for the query scope. - -The type must be one of the following values: Exclude, Include, or Require. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: f -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedPropertyName -Specifies the name of the managed property to use for the PropertyQuery scope rule. - -The type must be a valid name of a managed property; for example, ManagedProp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: mname -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MatchingString -Specifies the string to use when matching the URL rule type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: text -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertyValue -Specifies the property value to use when matching the PropertyQuery rule type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: value -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scope -Applies the query scope rule to the specified scope. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a scope (for example, Scope1); or an instance of a valid Scope object. - -```yaml -Type: ScopePipeBind -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the query scope rule collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UrlScopeRuleType -Specifies the value to use when matching the URL rule type. - -The type must be one of the following values: Folder, HostName, or Domain. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: ut -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQuerySpellingCorrection.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQuerySpellingCorrection.md deleted file mode 100644 index 5265a18827..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchQuerySpellingCorrection.md +++ /dev/null @@ -1,240 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchqueryspellingcorrection -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchQuerySpellingCorrection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchQuerySpellingCorrection - -## SYNOPSIS -Sets the operation status of the Query Spelling Corrections (QSC) component. - -## SYNTAX - -``` -Set-SPEnterpriseSearchQuerySpellingCorrection [-AssignmentCollection <SPAssignmentCollection>] - [-ContentAlignmentEnabled <Boolean>] [-DiacriticsInSuggestionsEnabled <Boolean>] - [-Identity <QuerySpellingCorrectionPipeBind>] [-MaxDictionarySize <Int32>] [-MaxProcessingTime <TimeSpan>] - -SearchApplication <SearchServiceApplicationPipeBind> [-SecurityTrimmingEnabled <Boolean>] - [-SpellingDictionary <SpellingDictionaryType>] [-TermFrequencyThreshold <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet provides access to the configuration options for the QSC component. -The two most prominent configuration options are the switch to enable the content-alignment process and the selection of dictionaries to be used for query spelling correction, that is the set of fixed dictionaries per language or the dynamic dictionary that is being produced by the content alignment process. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Set-SpEnterpriseSEarchQuerySpellingCorrection -SearchApplication $ssa -SpellingDictionary dynamic -``` - -This example sets the dictionary named dynamic to be used for query spelling correction for the default search service application. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ContentAlignmentEnabled -A Boolean value to enable or deactivate the content alignment process. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiacriticsInSuggestionsEnabled -A switch to enable or disable spelling suggestions that contain diacritics (for example, German umlaut umlaut). -The default setting is true. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies an object that represents the current status for the query spelling correction. - - -```yaml -Type: QuerySpellingCorrectionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MaxDictionarySize -Specifies the maximal number of terms in a content-aligned spelling dictionary. -In a multi-tenant environment, this number is valid per tenant. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxProcessingTime -Specifies the maximum runtime for compiling a content-aligned spelling dictionary. -The default value is 6 hours. - - -```yaml -Type: TimeSpan -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search service application that contains the QSC components. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecurityTrimmingEnabled -A Boolean value to enable or deactivate the security check for spelling suggestions. -If enabled, only spelling suggestions that deliver at least one document for the current user are shown. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SpellingDictionary -Specifies the dictionary to be used for query spelling correction. -The two available values are dynamic and static. -When value is set to dynamic, the query spelling correction uses the content-aligned dictionary. -When value is set to static, the query spelling correction uses the out of the box static spelling dictionaries. - - -```yaml -Type: SpellingDictionaryType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TermFrequencyThreshold -Specifies the minimum number of documents that must contain the most frequently used term in the document collection for the content-alignment process to be executed. -In a multi-tenant environment, this number is valid per tenant. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchRankingModel.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchRankingModel.md deleted file mode 100644 index 153ac6f879..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchRankingModel.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchrankingmodel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchRankingModel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchRankingModel - -## SYNOPSIS -Sets the properties of a ranking model for a shared search service application. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchRankingModel [-Identity] <RankingModelPipeBind> -Owner <SearchObjectOwner> - -RankingModelXML <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a ranking model for a search service application. -The name, description, and identifier (ID) for a ranking model are contained in the .xml file specified in RankingModelXML. -If the Identity parameter is not specified or the identity does not match any of the ranking models in the collection, an exception is thrown and the default ranking model is used. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$owner = Get-SPEnterpriseSearchOwner -Level ssa -$rankingModel = Get-SPEnterpriseSearchRankingModel -Identity 8f6fd0bc-06f9-43cf-bbab-08c377e083f4 -SearchApplication $ssa -Owner $owner -$newrankmodel = Get-Content .\newRankModel.xml -$newrankmodel = [String]$newrankmodel -Set-SPEnterpriseSearchRankingModel -Identity $rankingModel -SearchApplication $ssa -Owner $owner -RankingModelXML $newrankmodel -``` - -This example reconfigures the ranking model with the identity 8f6fd0bc-06f9-43cf-bbab-08c377e083f4 with the new ranking model specified in newRankModel.xml. - - -## PARAMETERS - -### -Identity -Specifies the ranking model to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid RankingModel object. - -```yaml -Type: RankingModelPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Owner -Specifies the scope where the ranking model is available. -The available scopes are: SSA, Tenant, Site Collection or Site. -A ranking model can be available in multiple scopes. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RankingModelXML -Specifies the name of the XML representation of the new ranking model. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application that contains the ranking model. - -The type must be a valid GUID in the 9bf36458-fc99-4f7b-b060-867e5a63adce, a valid search application name (for example, SearchApp1), or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchResultItemType.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchResultItemType.md deleted file mode 100644 index e928233843..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchResultItemType.md +++ /dev/null @@ -1,344 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchresultitemtype -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchResultItemType -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchResultItemType - -## SYNOPSIS -Sets properties of a result item type. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchResultItemType [-Identity] <ResultItemTypePipeBind> -Owner <SearchObjectOwner> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DisplayProperties <String>] - [-DisplayTemplateUrl <String>] [-Name <String>] [-OptimizeForFrequentUse <Boolean>] [-RulePriority <Int32>] - [-Rules <PropertyRuleCollection>] [-SearchApplication <SearchServiceApplicationPipeBind>] - [-SearchApplicationProxy <SearchServiceApplicationProxyPipeBind>] [-SourceID <Guid>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPEnterpriseSearchResultItemType` cmdlet sets properties of user-created result item types. -You cannot use this cmdlet to set or change properties of the built-in result item types that are included with SharePoint products. - -Result item types enable you to change the look of search results based on the type of result. -You start by defining a collection of rules, which will be evaluated against the properties of results. -Then you define the display template to use for rendering that type of result. -Once you have created the result item type, results matching the rules of the result item type will render using the specified display template. - -Example use cases: - -- Change the look of results for a particular file name extension, for example Word documents. -- Change the look of a particular content type in search results. -- Change the look of results from a particular author. -- Add a result action to results from a particular result source as part of a custom search application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$web = Get-SPWeb https://webUrl -$tenantOwner = Get-SPEnterpriseSearchOwner -Level SPSite -SPWeb $web -$ssa = Get-SPEnterpriseSearchServiceApplication -$resultType = Get-SPEnterpriseSearchResultItemType -Owner $tenantOwner -SearchApplication $ssa -$resultType.BuiltIn -$rule = Get-SPEnterpriseSearchPropertyRule -PropertyName "ContentTypeId" -Operator "StartsWith" -$rule.AddValue('0x010063C2F478ACC511DFB869B5BFDFD720851252') -$ruleCollection = Get-SPEnterpriseSearchPropertyRuleCollection -$ruleCollection.Add($rule) -$displayProperties = "WorkId,Rank,Title,Size,Path,Description,SiteName,HitHighlightedSummary,HitHighlightedProperties,ViewsLifeTime" -$displaytemplateUrl = "~sitecollection/_catalogs/masterpage/Display Templates/Search/Item_MyCustomDisplayTemplate.js" -Set-SPEnterpriseSearchResultItemType --Identity $resultType ` --SearchApplication $ssa ` --Name "CustomResultType" ` --Rules $ruleCollection ` --RulePriority 1 --DisplayProperties $displayProperties ` --DisplayTemplateUrl $displaytemplateUrl ` --Owner $tenantOwner -``` - -This example first defines variables for the URL of the site, the search owner and search application. -It retrieves the result item type and checks whether the result item type is a built-in result item type. -If $resultType.BuiltIn returns false then the result item type is not built-in and you can set its properties by using the `Set-SPEnterpriseSearchResultItemType`. - -Next, the example creates the rule that result item types shall be matched against and adds it to a property rule collection. - -Next, the example defines which properties of the result item type that shall be displayed and the display template to use. - -Finally, the example uses the `Set-SPEnterpriseSearchResultItemType` cmdlet to modify the result item type. - - -## PARAMETERS - -### -Identity -Specifies the result item type to update. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: ResultItemTypePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the result item type was created. - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayProperties -Specifies which result properties to display. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: dp -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayTemplateUrl -Specifies the URL of the display template that shall be used for rendering the results. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: url -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the result item type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: n -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OptimizeForFrequentUse -{{ Fill OptimizeForFrequentUse Description }} - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: opt -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RulePriority -Specifies which priority the collection of rules has compared to other rules. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: priority -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Rules -Specifies the collection of rules to evaluate the result properties against. - -```yaml -Type: PropertyRuleCollection -Parameter Sets: (All) -Aliases: rule -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the name of the search application. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplicationProxy -Specifies the proxy of the search application that contains the result item type. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application proxy name (for example, SearchAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SourceID -Identifies the search result source that the result item type applies to. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: sid -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchResultItemType](New-SPEnterpriseSearchResultItemType.md) - -[Get-SPEnterpriseSearchResultItemType](Get-SPEnterpriseSearchResultItemType.md) - -[Remove-SPEnterpriseSearchResultItemType](Remove-SPEnterpriseSearchResultItemType.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) - -[Get-SPEnterpriseSearchPropertyRule](Get-SPEnterpriseSearchPropertyRule.md) - -[Get-SPEnterpriseSearchPropertyRuleCollection](Get-SPEnterpriseSearchPropertyRuleCollection.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchResultSource.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchResultSource.md deleted file mode 100644 index 6506f1a767..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchResultSource.md +++ /dev/null @@ -1,457 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchresultsource -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchResultSource -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchResultSource - -## SYNOPSIS -Sets properties of a result source. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchResultSource [-AssignmentCollection <SPAssignmentCollection>] - [-AuthenticationType <FederationAuthType>] [-AutoDiscover <Boolean>] [-Confirm] [-Description <String>] - -Identity <ResultSourcePipeBind> [-MakeDefault <Boolean>] [-Name <String>] [-Owner <SearchObjectOwner>] - [-Password <String>] [-ProviderId <Guid>] [-QueryTemplate <String>] [-RemoteUrl <String>] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-SsoId <String>] [-UserName <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a user-created result source. -This cmdlet supports the same update operations as are supported through the "Manage Result Sources" page in Central Administration. -The result source cannot be a built-in source (a built-in source has the BuiltIn property set to true) for any update operation other than changing the default result source using the MakeDefault parameter. - For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$owner = Get-SPEnterpriseSearchOwner -Level SSA -$customResultSource = New-SPEnterpriseSearchResultSource -SearchApplication $ssa -Owner $owner -ProviderId fa947043-6046-4f97-9714-40d4c113963d -Name "Custom SharePoint Result Source" -Set-SPEnterpriseSearchResultSource -Identity $customResultSource -Name "Basic SharePoint Result Source" -``` - -This example updates the name of the result source and the identity of the result source is specified as a result source instance. -SearchApplication and Owner are not required for this update operation. - - -### --------------------EXAMPLE 2--------------------- -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$owner = Get-SPEnterpriseSearchOwner -Level SSA -$customResultSource = New-SPEnterpriseSearchResultSource -SearchApplication $ssa -Owner $owner -ProviderId fa947043-6046-4f97-9714-40d4c113963d -Name "Custom SharePoint Result Source" -Set-SPEnterpriseSearchResultSource -SearchApplication $ssa -Owner $owner -Identity "Custom SharePoint Result Source" -Description "A custom SharePoint Result Source for demonstration purposes" -``` - -This example updates the description of the result source and the identity of the result source is specified by name. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationType -Specifies an authentication type for the result source. If parameter is not specified, the value is unchanged. - -A specific set of authentication types are supported for each search provider type and if parameter is not specified, the authentication type will default based on search provider type. - -This cmdlet supports the following set of authentication mechanisms and corresponding types: Default SharePoint Authentication (FederationAuthType.LocalNTAuth), Basic Authentication (FederationAuthType.SingleAccountBasicAuth - specify UserName and Password), Default Remote SharePoint Authentication (FederationAuthType.PerUserBasicAuth), Single Sign On (FederationAuthType.SSO - requires SsoId to be specified), Anonymous (FederationAuthType.Anonymous), Digest Authentication (FederationAuthType.SingleAccountDigest - specify UserName and Password), NTLM Application Pool Identity (FederationAuthType.ApplicationPoolIdentity), NTLM User Name and Password (FederationAuthType.SingleAccountNTLM - specify UserName and Password). - -When using a Local SharePoint Search/Local SharePoint People Search provider, then FederationAuthType.LocalNTAuth (default) and FederationAuthType.SingleAccountBasicAuth are supported. - -When using a Remote SharePoint Search/Remote SharePoint People Search provider, then FederationAuthType.PerUserBasicAuth (default) and FederationAuthType.SSO are supported. - -When using OpenSearch 1.0/1.1 search provider, then the following authentication types are supported: FederationAuthType.Anonymous (default), FederationAuthType.SingleAccountBasicAuth, FederationAuthType.SingleAccountDigest, FederationAuthType.SingleAccountNTLM, and FederationAuthType.ApplicationPoolIdentity. - -All authentication types are listed in the enum FederationAuthType. - - -```yaml -Type: FederationAuthType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoDiscover -Specifies whether to use automatic discovery of the Exchange server endpoint for the result source. - -Setting value to true ($true) states that automatic discovery should be used. - -If parameter is not specified, the value is unchanged. - -Only applicable when using an Exchange search provider. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a description for the result source. - -If parameter is not specified, the value is unchanged. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the result source to update. - -The type must be a valid GUID string, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a result source (for example, "Custom SharePoint Result Source"); or an instance of a valid Source object. - - -```yaml -Type: ResultSourcePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MakeDefault -Specifies whether the result source should be set as default result source or not, for the scope specified by the Owner parameter. - -If parameter is not specified, the default result source will not change. - -Setting value to true ($true) states that the result source should be set as default. - -Setting value to false ($false) states that the result source should not be set as default and in this case, if the result source to update is currently the default, the original default result source ("Local SharePoint Results") will be set as default again. - -Tip: Use instance, not name or GUID string Id, as Identity when using Makedefault, to clearly specify that Owner is only to be used for specifying the level where the result source should be set as default (if value is true) or where the default should be reset to original (if value is false). - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies a name for the result source. - -If parameter is not specified, the value is unchanged. - -Names must be unique at each administrative level. - -For example, two result sources in a site cannot share a name, but one in a site and one provided by the site collection can. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Owner -Specifies the search object owner that defines the scope at which the corresponding result source is available. - - -```yaml -Type: SearchObjectOwner -Parameter Sets: (All) -Aliases: o -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -Specifies the password of the user credentials to use to connect to the result source. - -If parameter is not specified, the value is unchanged. - -Used when authentication type (AuthenticationType) is set to a type that consumes user credentials (FederationAuthType.SingleAccountBasicAuth, FederationAuthType.SingleAccountDigest or FederationAuthType.SingleAccountNTLM). - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProviderId -Specifies a search provider to be used by the result source. - -If parameter is not specified, the value is unchanged. - -Is specified as a Guid or GUID string, which must be one of the following: FA947043-6046-4F97-9714-40D4C113963D (Local SharePoint Search), E4BCC058-F133-4425-8FFC-1D70596FFD33 (Local SharePoint People Search), 1E0C8601-2E5D-4CCB-9561-53743B5DBDE7 (Remote SharePoint Search), E377CAAA-FCAF-4a1b-B7A1-E69A506A07AA (Remote SharePoint People Search), 3A17E140-1574-4093-BAD6-E19CDF1C0122 (Exchange Search), 3A17E140-1574-4093-BAD6-E19CDF1C0121 (OpenSearch 1.0/1.1). - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueryTemplate -Specifies the query transformation template of the result source. - -If parameter is not specified, the value is unchanged. - -Incoming queries are changed according to the template, to use this new query text instead. -Include the incoming query in the new text by using the query variable "{searchTerms}". -Use this to scope results. - -For example, to only return OneNote items, set the new text to "{searchTerms} fileextension=one". -Then, an incoming query "sharepoint" becomes "sharepoint fileextension=one". -Default value is {searchTerms}. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoteUrl -Specifies a connection URL template for the result source. - -If parameter is not specified, the value is unchanged. - -Must be set when using a search provider that consumes it: Remote SharePoint Search, Remote SharePoint People Search, OpenSearch 1.0/1.1, and Exchange (if AutoDiscover is not turned on). - -When using other search providers the parameter is ignored. - -For Remote SharePoint Search/Remote SharePoint People Search, specify the address of the root site collection of the remote SharePoint farm. - -For OpenSearch 1.0/1.1, specify the URL of the OpenSearch source. - -Include the query in the URL by using the query variable "{searchTerms}", which will be automatically replaced with the query. -For Exchange, specify the Exchange EWS URL from which to retrieve results. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SsoId -Specifies the reverse proxy certificate Secure Store Id to use to connect to the result source. - -If parameter is not specified, the value is unchanged. - -Must be specified if authentication type (AUthenticationType) is set to FederationAuthType.SSO (Single Sign On). - -If you are connecting to your intranet through a reverse proxy, enter the SSO Id of the Single Sign On entry which stores the certificate used to authenticate against the reverse proxy. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserName -Specifies the user name of the user credentials to use to connect to the result source. - -If parameter is not specified, the value is unchanged. - -Used when authentication type (AuthenticationType) is set to a type that consumes user credentials (FederationAuthType.SingleAccountBasicAuth, FederationAuthType.SingleAccountDigest or FederationAuthType.SingleAccountNTLM). - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPEnterpriseSearchResultSource](New-SPEnterpriseSearchResultSource.md) - -[Get-SPEnterpriseSearchResultSource](Get-SPEnterpriseSearchResultSource.md) - -[Remove-SPEnterpriseSearchResultSource](Remove-SPEnterpriseSearchResultSource.md) - -[Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchService.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchService.md deleted file mode 100644 index cbaddbec11..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchService.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchService - -## SYNOPSIS -Sets the properties of a search service for a farm. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchService [[-Identity] <SearchServicePipeBind>] [-AcknowledgementTimeout <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-ConnectionTimeout <String>] - [-ContactEmail <String>] [-IgnoreSSLWarnings <String>] [-InternetIdentity <String>] - [-PerformanceLevel <String>] [-ProxyType <String>] [-ServiceAccount <String>] - [-ServicePassword <SecureString>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a search service for a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$password = Read-Host -AsSecureString -Set-SPEnterpriseSearchService -IgnoreSSLWarnings $true -ServiceAccount 'contoso\adminAccount' -ServicePassword $password -``` - -This example configures the search service to ignore SSL warnings and changes the service account for the search service. - - -## PARAMETERS - -### -Identity -Specifies the search service to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchService1); or an instance of a valid SearchService object. - -```yaml -Type: SearchServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AcknowledgementTimeout -Specifies the time in seconds that the search server will wait for request acknowledgement while connecting to other services. - -The type must be string input that can be parsed to an integer value. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConnectionTimeout -Specifies the time in seconds that the search server waits while connecting to other services. - -The type must be string input that can be parsed to an integer value. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContactEmail -Specifies an e-mail address to which external site administrators can write if problems occur when the site is being crawled. - -The type must be a valid e-mail address, in the form MyAddress@mycompany.com. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreSSLWarnings -Specifies that the search service will ignore Secure Sockets Layer (SSL) certificate name warnings. -The default value is False. - -The type must be a string that can be cast to a Boolean value, for example, True or False. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InternetIdentity -Specifies the value that the crawler sends in the headers of its HTTP requests to sites when it fetches their pages. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PerformanceLevel -Specifies the relative number of threads for the crawl component performance. -The type must be one of the following values: Reduced, PartlyReduced, or Maximum. The default value is Maximum. - -* Reduced: Total number of threads = number of processors, Max Threads/host = number of processors. Threads are assigned Below Normal priority. - -* Partly Reduced: Total number of threads = 16 times the number of processors , Max Threads/host = 8 plus the number of processors. Threads are assigned Below Normal priority. - -* Maximum: Total number of threads = 32 times the number of processors, Max Threads/host = 8 plus the number of processors. Threads are assigned Normal priority. - - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProxyType -Specifies whether the search service uses a proxy server or connects directly when crawling content. -The default value is Direct, (No proxy server is used). - -The type must be one of the following values: Direct or Proxy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceAccount -Specifies the user account or service account to use for running the Office Server Search service. -When this parameter is used, the ServicePassword parameter must also be specified. - -The type must be a valid account name on the domain, in the form Domain\user name or user name. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServicePassword -Specifies the password for the service account specified in ServiceAccount. - -The type must contain the domain password to the account specified in the ServiceAccount parameter. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index 5f735f1647..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,362 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Sets the properties of a search service application for a farm. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchServiceApplication [-AdminApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] - [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] - [-DatabaseUsername <String>] [-DefaultContentAccessAccountName <String>] - [-DefaultContentAccessAccountPassword <SecureString>] [-DefaultSearchProvider <SearchProvider>] - [-DiacriticSensitive <String>] [-FailoverDatabaseServer <String>] -Identity <SearchServiceApplicationPipeBind> - [-VerboseQueryMonitoring <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a search service application. -SPEnterpriseSearchServiceApplication represents a self-contained aggregation of indexed content and properties available for search and provides an anchor class for setting global search properties. -A search application can include multiple search service applications. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Set-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" -VerboseQueryMonitoring True -``` - -This example turns on verbose query logging in the default search service application named Search Service Application. - - -## PARAMETERS - -### -AdminApplicationPool -Specifies the application pool for the administrative web service for the search service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AdminAppPool1); or an instance of a valid IISWebServiceApplicationPool object. - - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies an application pool for the search service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPool1); or an instance of a valid IISWebServiceApplicationPool object. - - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -This parameter is obsolete and has no function. -You should not use this parameter. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user ID that is used for accessing the web service administration database on SQL Server. - - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the web service administration database. - -The type must be a valid SQL Server host name, for example, SQLServerHost1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user ID to use for accessing the web service administration database. - -The type must be a valid user name, for example, WebAdminUserDB1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultContentAccessAccountName -Specifies the account ID to use for accessing content. - -The type must be a valid user name, for example, ContentAccessUser1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultContentAccessAccountPassword -Specifies the password for the content access account. - -The type must be a valid password. - - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultSearchProvider -Specifies the search application type to be used for this application. -This parameter has been deprecated for SharePoint Server. - - -```yaml -Type: SearchProvider -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DiacriticSensitive -Specifies that the search application respects diacritics (for example, ä). -The default value is false. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host SQL instance for the failover database server. - -The type must be a valid SQL Server instance name, for example, SQLServerHost1. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the search service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a search service application (for example, MySearchApp); or an instance of a valid SearchServiceApplication object. - - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -VerboseQueryMonitoring -Enables verbose query logging. -The default value is False. - -The type must be a string that can be cast to a Boolean value, for example, True or False. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceApplicationProxy.md deleted file mode 100644 index 278f174b10..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceApplicationProxy.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchServiceApplicationProxy - -## SYNOPSIS -Sets properties of a search service application proxy. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchServiceApplicationProxy [-Identity] <SearchServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of a site administration service application proxy for a search application. -SPEnterpriseSearchServiceApplicationProxy represents the proxy for search site administration functionality. -One search service application proxy exists for each search application on a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchServiceApplicationProxy -Identity SsaProxy | Set- SPEnterpriseSearchServiceApplicationProxy -Name ContosoSearchProxy -``` - -This example sets the display name of a search service application proxy. - - -## PARAMETERS - -### -Identity -Specified the search service application proxy to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a search service application proxy (for example, SearchServiceAppProxy1); or an instance of a valid SearchServiceApplicationProxy object. - -```yaml -Type: SearchServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name of the search application proxy to retrieve. - -The type must be a valid string, for example, SearchAppProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceInstance.md deleted file mode 100644 index 5036e32309..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchServiceInstance.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchServiceInstance - -## SYNOPSIS -Sets the properties of a search service instance. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchServiceInstance [-Identity] <SearchServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultIndexLocation <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet updates properties of the search service instance for a farm. - - For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference [https://go.microsoft.com/fwlink/p/?LinkId=671715](https://go.microsoft.com/fwlink/p/?LinkId=671715). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$si = Get-SPEnterpriseSearchServiceInstance -Local -Set-SPEnterpriseSearchServiceInstance -Identity $si -DefaultIndexLocation F:\SearchIndex -``` -Sets the default index location to F:\SearchIndex. - -## PARAMETERS - -### -Identity -Specifies the search service instance to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a query server (for example, MyQueryServer); or an instance of a valid SearchServiceInstance object. - - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultIndexLocation -> [!NOTE] -> On SharePoint Server 2013 and SharePoint Server 2016, SharePoint Server 2019 this parameter is obsolete and has no function. You should not use this parameter. - -Specifies the default path to use for creating an index of content. - -The type must be a valid path in either of the following forms: - -- C:\folder_name - -- \\\\server_name\folder_name - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Server.Search.Cmdlet.SearchServiceInstancePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchTopology.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchTopology.md deleted file mode 100644 index 7a9bebc1d5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPEnterpriseSearchTopology.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spenterprisesearchtopology -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPEnterpriseSearchTopology -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPEnterpriseSearchTopology - -## SYNOPSIS -Activates a given search topology. - - -## SYNTAX - -``` -Set-SPEnterpriseSearchTopology [-Identity] <SearchTopologyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet enables the search topology with the given identity, marking the currently active search topology as inactive. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Identity 10fa59cb-4b32-4fe6-8f8d-065388df201e -Set-SPEnterpriseSearchTopology -Identity $topology -SearchApplication $ssa -``` - -This example enables a search topology with the Identity 10fa59cb-4b32-4fe6-8f8d-065388df201e. - - -### ------------------EXAMPLE 2------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa | ?{$_.State -eq 'Inactive'} -Set-SPEnterpriseSearchTopology -Identity $topology -SearchApplication $ssa -``` - -This example retreives an inactive topology and sets it to the active topology. - -## PARAMETERS - -### -Identity -Specifies the search topology to enable. - -```yaml -Type: SearchTopologyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchApplication -Specifies the search application to which the search topology will belong. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPEnterpriseSearchTopology](Get-SPEnterpriseSearchTopology.md) - -[New-SPEnterpriseSearchTopology](New-SPEnterpriseSearchTopology.md) - -[Remove-SPEnterpriseSearchTopology](Remove-SPEnterpriseSearchTopology.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelBIServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelBIServer.md deleted file mode 100644 index c421c23b2e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelBIServer.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spexcelbiserver -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Set-SPExcelBIServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPExcelBIServer - -## SYNOPSIS - -Specifies a description for an existing BI server for Excel Services. - -## SYNTAX - -``` -Set-SPExcelBIServer [-Identity] <SPExcelBIServerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Description <String>] -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> - [-ServerId <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPExcelBIServer cmdlet to specify a description for an existing BI server for Excel Services. - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Excel Services Application Web Service Application'} -Set-SPExcelBIServer -Identity "ExcelServices" -ExcelServiceApplication $sa -``` - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the Analysis server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the ExcelServiceApplication identity. - -```yaml -Type: SPExcelBIServerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServerId -The name of the Analysis Services server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Excel.Server.Cmdlet.SPExcelBIServerPipeBind -Microsoft.Office.Excel.Server.Cmdlet.SPExcelServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelDataConnectionLibrary.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelDataConnectionLibrary.md deleted file mode 100644 index 70924e1ae8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelDataConnectionLibrary.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spexceldataconnectionlibrary -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Set-SPExcelDataConnectionLibrary -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPExcelDataConnectionLibrary - -## SYNOPSIS -Sets properties of a data connection library for Excel Services Application. - - -## SYNTAX - -``` -Set-SPExcelDataConnectionLibrary [-Identity] <SPExcelDCLPipeBind> - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-Address <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPExcelDataConnectionLibrary` cmdlet sets the properties of a library from which Excel Services Application loads data connection files. -Excel Services Application loads data connection files only if they are stored in a data connection library that is on the list of trusted data connection libraries. -Data connection libraries constitute a kind of list that contains data connection files. -These files contain everything that Excel Services Application and the Excel client require to connect to an external data source. -Data connection libraries enable you to reuse and share data connections. -Data connections can be loaded by using information from the workbook file. -However, using a data connection library to load data connections provides an additional layer for data connections so that they can be managed separately from workbooks. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelDataConnectionLibrary | where {$_.address -eq "https://portal/site/salesDCL" } | Set-SPExcelDataConnectionLibrary -Description "This is the DCL where all the connections to the sales data are stored -``` - -This example sets a display description for the entry https://portal/site/salesDCL in the list of trusted data connection libraries (DCLs) that is on the Excel Services Application Web service application named MyExcelService. - - -### --------------EXAMPLE 2-------------- -``` -Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelDataConnectionLibrary | where {$_.address -eq "https://portal/site/salesDCL" } | Set-SPExcelDataConnectionLibrary -Address "https://portal/site/salesDCL-%60%60%60--This%20example%20updates%20the%20address%20of%20the%20data%20connection%20library%20for%20the%20entry%20https://portal/test/site/salesDCL%20to%20https://portal/site/salesDCL%20in%20the%20list%20of%20trusted%20data%20connection%20libraries,%20which%20is%20on%20the%20Excel%20Services%20Application%20Web%20service%20application%20named%20MyExcelService.---##%20PARAMETERS--###%20-Identity-Specifies%20the%20DataConnectionLibrary%20object%20to%20update.--The%20type%20must%20be%20a%20valid%20GUID,%20in%20the%20form%2012345678-90ab-cdef-1234-567890bcdefgh;%20a%20valid%20name%20of%20a%20data%20connection%20library%20(for%20example,%20DataConnectionLib1);%20a%20valid%20URL,%20in%20the%20form%20https://server_name;%20or%20an%20instance%20of%20a%20valid%20SPExcelDCL%20object.--%60%60%60yaml-Type:%20SPExcelDCLPipeBind-Parameter%20Sets:%20(All)-Aliases:%20-Applicable:%20SharePoint%20Server%202010,%20SharePoint%20Server%202013--Required:%20True-Position:%201-Default%20value:%20None-Accept%20pipeline%20input:%20True%20(ByValue)-Accept%20wildcard%20characters:%20False-%60%60%60--###%20-ExcelServiceApplication-Specifies%20the%20Excel%20Services%20Application%20Web%20service%20application%20that%20contains%20SPExcelDataConnectionLibrary%20list%20object.--The%20type%20must%20be%20a%20valid%20GUID,%20in%20the%20form%2012345678-90ab-cdef-1234-567890bcdefgh;%20a%20valid%20name%20of%20an%20Excel%20Services%20Application%20Web%20service%20application%20in%20the%20farm%20(for%20example,%20MyExcelService1);%20or%20an%20instance%20of%20a%20valid%20SPExcelServiceApplication%20object.--%60%60%60yaml-Type:%20SPExcelServiceApplicationPipeBind-Parameter%20Sets:%20(All)-Aliases:%20-Applicable:%20SharePoint%20Server%202010,%20SharePoint%20Server%202013--Required:%20True-Position:%20Named-Default%20value:%20None-Accept%20pipeline%20input:%20True%20(ByPropertyName,%20ByValue)-Accept%20wildcard%20characters:%20False-%60%60%60--###%20-Address-Specifies%20the%20address%20of%20the%20data%20connection%20library.-The%20address%20must%20be%20unique%20in%20the%20list%20of%20trusted%20data%20connection%20libraries.--The%20type%20must%20be%20a%20valid%20URL,%20in%20the%20form%20https://server_name.--%60%60%60yaml-Type:%20String-Parameter%20Sets:%20(All)-Aliases:%20-Applicable:%20SharePoint%20Server%202010,%20SharePoint%20Server%202013--Required:%20False-Position:%20Named-Default%20value:%20None-Accept%20pipeline%20input:%20False-Accept%20wildcard%20characters:%20False-%60%60%60--###%20-AssignmentCollection-Manages%20objects%20for%20the%20purpose%20of%20proper%20disposal.-Use%20of%20objects,%20such%20as%20SPWeb%20or%20SPSite,%20can%20use%20large%20amounts%20of%20memory%20and%20use%20of%20these%20objects%20in%20Windows%20PowerShell%20scripts%20requires%20proper%20memory%20management.-Using%20the%20SPAssignment%20object,%20you%20can%20assign%20objects%20to%20a%20variable%20and%20dispose%20of%20the%20objects%20after%20they%20are%20needed%20to%20free%20up%20memory.-When%20SPWeb,%20SPSite,%20or%20SPSiteAdministration%20objects%20are%20used,%20the%20objects%20are%20automatically%20disposed%20of%20if%20an%20assignment%20collection%20or%20the%20Global%20parameter%20is%20not%20used.--When%20the%20Global%20parameter%20is%20used,%20all%20objects%20are%20contained%20in%20the%20global%20store.-If%20objects%20are%20not%20immediately%20used,%20or%20disposed%20of%20by%20using%20the%20%60Stop-SPAssignment%60%20command,%20an%20out-of-memory%20scenario%20can%20occur.--%60%60%60yaml-Type:%20SPAssignmentCollection-Parameter%20Sets:%20(All)-Aliases:%20-Applicable:%20SharePoint%20Server%202010,%20SharePoint%20Server%202013--Required:%20False-Position:%20Named-Default%20value:%20None-Accept%20pipeline%20input:%20True%20(ByValue)-Accept%20wildcard%20characters:%20False-%60%60%60--###%20-Confirm-Prompts%20you%20for%20confirmation%20before%20executing%20the%20command.-For%20more%20information,%20type%20the%20following%20command:%20%60get-help%20about_commonparameters%60--%60%60%60yaml-Type:%20SwitchParameter-Parameter%20Sets:%20(All)-Aliases:%20cf-Applicable:%20SharePoint%20Server%202010,%20SharePoint%20Server%202013--Required:%20False-Position:%20Named-Default%20value:%20None-Accept%20pipeline%20input:%20False-Accept%20wildcard%20characters:%20False-%60%60%60--###%20-Description-Specifies%20a%20friendly%20description%20for%20the%20data%20connection%20library.--The%20type%20must%20a%20valid%20a%20string;%20for%20example,"This is the data connection library where all the connections to the sales data are stored". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelDataProvider.md deleted file mode 100644 index 0a0adb8c8a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelDataProvider.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spexceldataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Set-SPExcelDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPExcelDataProvider - -## SYNOPSIS -Sets properties of a safe data provider for Excel Services Application. - - -## SYNTAX - -``` -Set-SPExcelDataProvider [-Identity] <SPExcelDataProviderPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-ProviderId <String>] - [-ProviderType <DataProviderType>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPExcelDataProvider` cmdlet sets the properties of a data provider that is stored in the list of safe data providers. -Excel Services Application refreshes external data connections only if the data provider for that connection is in the list of safe data providers. -Excel Services Application include a set of common data providers in this list. -Therefore, using cmdlets to modify safe data providers is typically an operation of custom data connection scenarios. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$provider = Get-SPExcelServiceApplication -Identity "MyExcelService" | Get-SPExcelDataProvider | where {$_.ProviderID -eq "SQLOLEDB" } -Set-SPExcelDataProvider $provider -Description "The SQLOLEDB provider description has changed." -$provider | format-table -``` - -This example retrieves the SQLOLEDB data provider from the list of safe data providers that is on the Excel Services Application Web service application named MyExcelService, as an object, adds a new display description and then displays the provider output in a Command Prompt window, formatted as a table. - - -## PARAMETERS - -### -Identity -Specifies the SPExcelDataProvider object to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid SPExcelDataProvider object. - -```yaml -Type: SPExcelDataProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a display description for the data provider. - -The type must a valid a string; for example, this is a custom OLEDB provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProviderId -Specifies the name of the data provider. -This ID should be present in the connection strings generated by this data provider and the ID must be unique for the data provider type. - -The type must a valid name of a provider; for example, CustomOLEDB. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProviderType -Specifies the supported type of the data provider to set. - -The type must be one of the following: OleDb, Odbc, or OdbcDsn. - -```yaml -Type: DataProviderType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelFileLocation.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelFileLocation.md deleted file mode 100644 index 9d3071b217..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelFileLocation.md +++ /dev/null @@ -1,618 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spexcelfilelocation -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Set-SPExcelFileLocation -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPExcelFileLocation - -## SYNOPSIS -Sets properties of a trusted file location for Excel Services Application. - - -## SYNTAX - -``` -Set-SPExcelFileLocation [-Identity] <SPExcelFileLocationPipeBind> - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-AbortOnRefreshOnOpenFail] [-Address <String>] - [-AssignmentCollection <SPAssignmentCollection>] [-AutomaticVolatileFunctionCacheLifetime <Int32>] - [-ChartAndImageSizeMax <Int32>] [-ConcurrentDataRequestsPerSessionMax <Int32>] [-Confirm] - [-DefaultWorkbookCalcMode <DefaultWorkbookCalcMode>] [-Description <String>] [-DisplayGranularExtDataErrors] - [-ExternalDataAllowed <AllowExternalData>] [-IncludeChildren] [-LocationType <LocationType>] - [-ManualExtDataCacheLifetime <Int32>] [-NewWorkbookSessionTimeout <Int32>] - [-PeriodicExtDataCacheLifetime <Int32>] [-RequestDurationMax <Int32>] [-RESTExternalDataAllowed] - [-SessionTimeout <Int32>] [-ShortSessionTimeout <Int32>] [-UdfsAllowed] [-WarnOnDataRefresh] [-WhatIf] - [-WorkbookSizeMax <Int32>] [-ChartRenderDurationMax <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPExcelFileLocation` cmdlet sets properties of a location from which Excel Services Application loads workbooks. -Excel Services Application loads only workbooks that are stored in a trusted file location. -Properties of trusted file locations control how workbooks can be used when they are loaded on Excel Services Application. -Excel Services Application always enforces the properties that are defined by the trusted file location from which a workbook was loaded. -The properties that are used by the trusted file location are determined by comparison of the file path for the workbook with the Address parameter of the trusted file location. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -Get-SPExcelFileLocation -ExcelServiceApplication "My Excel Service" | where { $_.externaldataallowed -eq "DclAndEmbedded"} | Set-SPExcelFileLocation -ExernalDataAllowed Dcl -``` - -This example gets every trusted file location for the Excel Services Application Web service application named My Excel Service that allows data connections to load from workbook files and specifies that the locations must use a data connection library to load data connections. - - -### --------------EXAMPLE 2-------------- -``` -Get-SPExcelServiceApplication | Get-SPExcelFileLocation | where {$_.Address -eq "https://"} | Set-SPExcelFileLocation -Description "This is the default trusted file location for Excel Services Application. It allows any file from anywhere in SharePoint to load." -``` - -This example changes the description of the default file location for every Excel Services Application Web service application in the farm. - - -## PARAMETERS - -### -Identity -Specifies the FileLocation object to update. -The name must be unique in the list of file locations. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid string identifying the file location, in the form https://myPortal/myTeam; a valid string identifying the path, in the form C:\folder_name; or an instance of a valid SPExcelFileLocation object. - -```yaml -Type: SPExcelFileLocationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelFileLocation list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AbortOnRefreshOnOpenFail -Specifies that the load of a Excel Services Application file automatically fails if an automatic data refresh operation fails when the file is opened. -The load is failed only if the following conditions are true: - --- User has read-only permissions to the Excel Services Application file. --- Workbook file has data connections that refresh automatically when the Excel file is opened. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Address -System.String - -Specifies a Web folder, or file directory from which Excel Services Application can load workbooks. - -The type must be a valid URL, in the form https://myPortal/myTeam; or a valid UNC path in form, \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AutomaticVolatileFunctionCacheLifetime -Specifies the maximum time, in seconds, that a computed value for a volatile function is cached for automatic recalculations. -Valid values include: - --1, calculate once when the workbook loads - -0, always calculate - -1 to 2073600, cache 1 second to 24 days - -The type must be the integers -1 or 0, or an integer value in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChartAndImageSizeMax -Specifies the maximum size, in megabytes, of a chart or image that can be opened. -The default value is 1. - -The type must be a valid integer greater than 0. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConcurrentDataRequestsPerSessionMax -Specifies the maximum number of concurrent external data requests allowed in each session. -If a session must issue more than this number of requests, additional requests must be queued. -The scope of this setting is the logical server. -The default value is 5. - -The type must be a positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultWorkbookCalcMode -Specifies the calculation mode of workbooks. -All of the settings except the File setting override the workbook settings. -If this parameter is changed, it is applied to all new sessions on Excel Services Application when the ConfigDB properties cache is refreshed. -The default setting is File. - -The type must be one of the following: File, Manual, Auto, or AutoDataTables. - -```yaml -Type: DefaultWorkbookCalcMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a friendly description for the new file location. - -The type must be a valid string; for example, this is the file location of the monthly sales reports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayGranularExtDataErrors -Displays granular error messages for external data failures for files in this location. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDataAllowed -Specifies the type of external data access allowed for workbooks: -None specifies that data refresh is disabled. -Dcl specifies that data is refreshed only when it uses a connection file in a trusted data connection library. -DclandEmbedded specifies that a data connection library can be used but is not required. -The scope of this setting is the trusted location. - -The default value is None. - -The type must be one of the following: None, Dcl, or DclAndEmbedded. - -```yaml -Type: AllowExternalData -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeChildren -Indicates that subordinate URLs, directories and libraries are trusted. -For example, if the trusted file location is https://portal, and IncludeChildren is true, then https://portal/subSite is also trusted, as is any subURL under the URL specified in Address. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationType -The type of location. -LocationType indicates how Excel Services Application retrieves files from that location specified in Address. -The default value is SharePoint. - -The type must be one of the following: SharePoint, UNC, or HTTP. - -```yaml -Type: LocationType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManualExtDataCacheLifetime -Specifies the time, in seconds, that Excel Services Application waits before re-issuing a manual, or user-initiated, external data request. -During this period, the results from the previous external data request may be returned from an external data cache. - -Valid values are: - --1 Never refresh after first query - -1 to 2073600 Caches 1 second to 24 days. - -The default value is 300. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewWorkbookSessionTimeout -Specifies the time, in seconds, that a session for a new, unsaved, workbook will remain active on Excel Services Application with no user activity. -The default value 1800. -Valid values include the following: - --1, session never expires - -0, session expires at the end of a single request - -1 to 2073600, remain active 1 second to 24 days. - -The type must be -1, 0, or an integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PeriodicExtDataCacheLifetime -Specifies the time, in seconds, that Excel Services Application waits before re-issuing an on-open or periodic (that is, automatic) external data request. -During this period, the results from the previous external data request may be returned from an external data cache. -A value -1 specifies to never refresh after the first query. - -The type must be -1, 0, or an integer in the range of 1 to 2073600. - -The default value is 300. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestDurationMax -Specifies the maximum duration, in seconds, for a single request in a session. -After this time elapses the request is timed out. - -The type must be -1 (no limit) or an integer in the range of 1 to 2073600. - -The default value is 300. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RESTExternalDataAllowed -Specifies whether requests from the Representational State Transfer (REST) Application Programming Interface (API) are permitted to refresh external data connections. - -The RESTExternalDataAllowed parameter has no effect if the External DataAllowed parameter is set to None. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionTimeout -Specifies the time, in seconds, that a session will remain active on Excel Services Application with no user activity. -The default is 300 seconds. -The default value is 300. -Valid values include: - --1, session never expires - -0, session expires at the end of a single request - -1 to 2073600, remain active 1 second to 24 days - -The type must be -1, 0, or an integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShortSessionTimeout -Specifies the time, in seconds, that a user has to make the initial interaction with a spreadsheet. -After this time has elapsed, if the user is not active, then the session is closed. -The value must always be less than SessionTimeout. -If the ShortSessionTimeout value is greater than or equal to SessionTimeout, an error is returned. -The default value is 75. - -The type must be -1 or an integer in the range of 1 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UdfsAllowed -Specifies that user-defined functions can be called by workbooks loaded from the trusted file location that is specified in Address. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarnOnDataRefresh -Specifies that a warning is displayed to the user on the first refresh of data for the workbook. -The default value is True. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookSizeMax -Specifies the maximum size, in megabytes, of a workbook that can be loaded. -The default value is 10. - -The type must be an integer value in the range of 1 to 2000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChartRenderDurationMax -The maximum time (in seconds) spent rendering any single chart. - -Valid values: -1 (no limit); from 1 through 2073600 (24 days). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelServiceApplication.md deleted file mode 100644 index a505851609..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelServiceApplication.md +++ /dev/null @@ -1,534 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spexcelserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Set-SPExcelServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPExcelServiceApplication - -## SYNOPSIS -Sets global properties for Excel Services Application. - - -## SYNTAX - -### ExistingTargetApplicationParameterSet -``` -Set-SPExcelServiceApplication [[-Identity] <SPExcelServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-CachingOfUnusedFilesEnable] [-Confirm] - [-CrossDomainAccessAllowed] [-EncryptedUserConnectionRequired <EncryptedConnectionMode>] - [-ExternalDataConnectionLifetime <Int32>] [-FileAccessMethod <FileAccessMethod>] - [-LoadBalancingScheme <LoadBalancingScheme>] [-MemoryCacheThreshold <Int32>] [-PrivateBytesMax <Int32>] - [-SessionsPerUserMax <Int32>] [-SiteCollectionAnonymousSessionsMax <Int32>] - [-TerminateProcessOnAccessViolation] [-ThrottleAccessViolationsPerSiteCollection <Int32>] - [-UnattendedAccountApplicationId <String>] [-UnusedObjectAgeMax <Int32>] [-WhatIf] [-WorkbookCache <String>] - [-WorkbookCacheSizeMax <Int32>] [-UseEffectiveUserName] [-WorkbookModelUsageTracker <String>] - [<CommonParameters>] -``` - -### NewTargetApplicationParameterSet -``` -Set-SPExcelServiceApplication [[-Identity] <SPExcelServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-CachingOfUnusedFilesEnable] [-Confirm] - [-CrossDomainAccessAllowed] [-EncryptedUserConnectionRequired <EncryptedConnectionMode>] - [-ExternalDataConnectionLifetime <Int32>] [-FileAccessMethod <FileAccessMethod>] - [-LoadBalancingScheme <LoadBalancingScheme>] [-MemoryCacheThreshold <Int32>] [-PrivateBytesMax <Int32>] - [-SessionsPerUserMax <Int32>] [-SiteCollectionAnonymousSessionsMax <Int32>] - [-TerminateProcessOnAccessViolation] [-ThrottleAccessViolationsPerSiteCollection <Int32>] - [-UnusedObjectAgeMax <Int32>] [-WhatIf] [-WorkbookCache <String>] [-WorkbookCacheSizeMax <Int32>] - [-UnattendedServiceAccount <PSCredential>] [-UseEffectiveUserName] [-WorkbookModelUsageTracker <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-ExcelServiceApplication` cmdlet changes global runtime properties for Excel Services Application. -Changes to properties that are made by using this cmdlet affect all machines in the farm that are running an instance of the specified Excel Services Application Web service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Excel Services Application Web Service Application'} -Set-SPExcelServiceApplication -Identity $sa -SessionsPerUserMax 10 -``` - -This example sets the Excel Services Application to enable each user to open no more than 10 sessions at one time on a back-end application server that runs Excel Services Application. - - -### --------------EXAMPLE 2-------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Excel Services Application Web Service Application'} -Set-SPExcelServiceApplication -Identity $sa -PrivateBytesMax -1 -``` -This example sets the maximum number of private bytes of memory on the computer to a value of -1, which indicates that Excel Services Application will consume 50 percent of the available memory resources. - - -## PARAMETERS - -### -Identity -Specifies the SPExcelServiceApplication object to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CachingOfUnusedFilesEnable -Specifies that files that are no longer used by Excel Services Application can remain in the cache for later use. -The default is true when the parameter is not specified on the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CrossDomainAccessAllowed -Specifies that trusted workbooks and data connection files can be requested and rendered by Web Parts or pages that reside in other HTTP domains. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EncryptedUserConnectionRequired -Requires that encryption is used between the end-user and the server running Excel Services Application. -The scope of this setting is the logical server. -The default value is None. - -The type must be one of the following: None or Connection. - -```yaml -Type: EncryptedConnectionMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalDataConnectionLifetime -Specifies the maximum number of seconds that an external data connection can remain open in the connection pool. - -Valid values are: - --1 Never recycle - -1 to 2073600 Remain active 1 second to 24 days. - -The default value is 1800. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileAccessMethod -Specifies the authentication method that Excel Services Application uses to retrieve files. -UseFileAccessAccount specifies that all workbooks always use the credentials of the service account running Excel Services Application. -UseImpersonation specifies that Excel Services Application retrieves the workbook files as the user who makes the request. -The default value is UseImpersonation. - -The type must be one of the following: UseImpersonation or UseFileAccessAccount. - -```yaml -Type: FileAccessMethod -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoadBalancingScheme -Specifies the load-balancing schema that is used by the Excel Services Application Web service application to send requests to different back-end Excel Services Application computers. -The default value is WorkbookURL. - -The type must be one of the following: RoundRobin, Local, or WorkbookURL. - -```yaml -Type: LoadBalancingScheme -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MemoryCacheThreshold -Specifies the percentage of the maximum private bytes that can be allocated to inactive objects. -When the memory cache threshold is exceeded, cached objects that are not currently in use are released. -Setting this value to 0 disables caching of inactive objects. -The default value is 90. - -The type must be an integer in the range of 0 to 95. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateBytesMax -Specifies the maximum private bytes, in megabytes, that are used by Excel Services Application. -When set to -1, the maximum private bytes defaults to 50 percent of physical memory on the computer. -Valid values include -1 for no limit, and any positive integer. -The default value is -1. - -The type must be -1 or any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionsPerUserMax -Specifies the maximum number of sessions allowed for a user. -If a user reaches this maximum the oldest session is deleted when a new session is started. -Valid values include -1 for no limit, and any positive integer. -The default value is 25. - -The type must be -1 or any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteCollectionAnonymousSessionsMax -Specifies the maximum number of anonymous sessions allowed per site collection. -A value of 0 specifies that no anonymous sessions are allowed. -Valid values include -1 for no limit, 0 to disable the setting, or any positive integer. -The default value is 25. - -The type must be -1, 0, or any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TerminateProcessOnAccessViolation -Terminates Excel Services Application when an access violation occurs in the process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThrottleAccessViolationsPerSiteCollection -Specifies that if a workbook causes an access violation error on Excel Services Application, all files originating from that workbook's site collection are blocked from loading for the specified period (in seconds). -Existing sessions for files on that site collection are unaffected. -Valid values include 0 to disable the setting, and the range of 1 to 2073600 seconds (24 days). -The default value is 0. - -The type must be an integer value in the range of 0 to 2073600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnattendedAccountApplicationId -Specifies that the application ID that is used to look up the unattended service account credentials from the secure storage service that is specified by the UnattendedAccountSecureServiceAppName parameter. -The secure storage service is contacted when this parameter is set and specific error cases occur. -Valid values are alphanumeric strings with a maximum of 256 characters. -The default value is an empty string. - -The type must be a valid string of alphanumeric characters; for example, UnattendedServiceAccountID. - -The unattended account is a single account that all workbooks can use to refresh data. -An unattended account is required when workbook connections specify None for authentication, or when any non-Windows credentials are used to refresh data. - -```yaml -Type: String -Parameter Sets: ExistingTargetApplicationParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnusedObjectAgeMax -Specifies the maximum amount of time, in minutes, that objects not currently used in a session are kept in the memory cache. -Valid values include -1 for no maximum setting, and a positive integer in the range of 1 to 34560 minutes (24 days). -The default value is -1. - -The type must be -1, or an integer in the range of 1 to 34560. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookCache -Specifies the local file system location of the cache that is used to store workbooks that are used by Excel Services Application. - -If no value is specified, the default value is a subdirectory in the system temporary directory. - -The type must be a valid path in either of the following forms: - --- C:\folder_name --- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookCacheSizeMax -Specifies the maximum allowable size, in megabytes, of an individual session. -The default value is 0. - -The type must be any positive integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnattendedServiceAccount -The Unattended Service Account is a single account that all workbooks can use to refresh data. This account is required to refresh data when workbook connections specify "Use the Unattended Service Account" without using Windows Credentials. - -```yaml -Type: PSCredential -Parameter Sets: NewTargetApplicationParameterSet -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseEffectiveUserName -The UseEffectiveUserName property is an alternative to Windows delegation for allowing users to securely access Analysis Services data. - -The setting will only impact external data connections based on Analysis Services workbook connections with an authentication setting of "Use the authenticated user's account". - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkbookModelUsageTracker -{{Fill WorkbookModelUsageTracker Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelUserDefinedFunction.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelUserDefinedFunction.md deleted file mode 100644 index 2dcefa2093..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelUserDefinedFunction.md +++ /dev/null @@ -1,232 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spexceluserdefinedfunction -applicable: SharePoint Server 2010, SharePoint Server 2013 -title: Set-SPExcelUserDefinedFunction -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPExcelUserDefinedFunction - -## SYNOPSIS -Sets properties of a user-defined function in Excel Services Application. - - -## SYNTAX - -``` -Set-SPExcelUserDefinedFunction [-Identity] <SPExcelUDFPipeBind> - -ExcelServiceApplication <SPExcelServiceApplicationPipeBind> [-Assembly <String>] - [-AssemblyLocation <AssemblyLocation>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Description <String>] [-Enable] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPExcelUserDefinedFunction` cmdlet sets properties of a user-defined function assembly. -Excel Services Application uses only user-defined functions that have an entry in the user-defined function list. -User-defined functions are managed code assemblies that can be called from an Excel Services Application workbook by using standard Excel Services Application formula syntax. -The assemblies can perform custom logic or other actions, such as refresh data. -Windows PowerShell cmdlets operate on the entries in the user-defined function list and do not operate on the assemblies. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1-------------- -``` -Set-SPExcelUserDefinedFunction -ExcelServiceApplication "My Excel Service" -Identity SampleCompany.SampleApplication.SampleUdf -Description "This is the new description for the sample UDF" -``` - -This example changes the description of the user-defined function (UDF) to the UDF SampleCompany.SampleApplication.SampleUdf file for the Excel Services Application Web service application named My Excel Service. - - -### --------------EXAMPLE 2-------------- -``` -Get-SPExcelServiceApplication "My Excel Service" | Set-SPExcelUserDefinedFunction -Identity SampleCompany.SampleApplication.SampleUdf -Enable: $false -``` - -This example disables the sample UDF SampleCompany.SampleApplication.SampleUdf file from the Excel Services Application named My Excel Service. - - -## PARAMETERS - -### -Identity -Specifies the SPExcelUserDefinedFunction object to update. - -The type must be a valid name of the code assembly; for example, SampleCompany.SampleApplication.SampleUdf; or an instance of a valid SPExcelUDF object. - -```yaml -Type: SPExcelUDFPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ExcelServiceApplication -Specifies the Excel Services Application Web service application that contains the SPExcelUserDefinedFunction list object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an Excel Services Application Web service application in the farm (for example, MyExcelService1); or an instance of a valid SPExcelServiceApplication object. - -```yaml -Type: SPExcelServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Assembly -Specifies the strongly-typed name of the assembly. -The name must be unique in the list of user-defined functions and cannot be more than 4096 alphanumeric characters long. - -The type must be a string of alphanumeric characters; for example, SampleCompany.SampleApplication.SampleUdf, C:\UDFs\SampleUdf.dll, or \\\\MyNetworkServer\UDFs\SampleUdf.dll. - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssemblyLocation -Specifies the location where the assembly is stored. - -The type must be one of the following: GAC or LocalFile. - -```yaml -Type: AssemblyLocation -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a display description for the user-defined function. -The name cannot be more than 4096 alphanumeric characters long. - -The type must be a string of alphanumeric characters; for example, this is the user-defined function for consolidation reports. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -Activates the user-defined function for use with Excel Services Application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPFarmConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPFarmConfig.md deleted file mode 100644 index 37fb504965..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPFarmConfig.md +++ /dev/null @@ -1,371 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spfarmconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPFarmConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPFarmConfig - -## SYNOPSIS -Sets a global property or a collection of global properties for the local farm. - - -## SYNTAX - -``` -Set-SPFarmConfig [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DataFormWebPartAutoRefreshEnabled <Boolean>] [-Force] [-InstalledProductsRefresh] - [-ServiceConnectionPointBindingInformation <String>] [-ServiceConnectionPointDelete] [-WhatIf] - [-WorkflowBatchSize <Int32>] [-WorkflowEventDeliveryTimeout <Int32>] [-WorkflowPostponeThreshold <Int32>] - [-ASPScriptOptimizationEnabled <Boolean>] [-UserAccountDirectoryPathIsImmutable] - [-DefaultActivateOnSiteMasterValue <Boolean>] [-MaxSiteSubscriptionSettingsValueLength <UInt32>] - [-MaxTenantStoreValueLength <UInt32>] [-SiteMasterMode <SPSiteMasterMode>] - [-SiteMasterValidationIntervalInHours <UInt32>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPFarmConfig` cmdlet updates a collection of global settings for the local farm that are not members of the SPFarm object. -Use the `Get-SPFarmConfig` cmdlet to read global settings for the local farm and to create a new PSCustomObject object from the collection of properties returned from the local farm and then add this object to the pipeline. -Modify the PSCustomObject object and pass it to the `Set-SPFarmConfig` cmdlet to change the parameter values. - -The properties collected in the PSCustomObject object must be farm-wide settings and must be configurable only once for the entire farm. -The parameter name added to the PSCustomObject object must match exactly the input parameter name for the `Set-SPFarmConfig` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------------EXAMPLE-------------------------- -``` -Set-SPFarmConfig -WorkflowBatchSize 50 -``` - -This example sets the WorkflowBatdhSize to 50. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataFormWebPartAutoRefreshEnabled -Specifies whether any DataFormWebPart on any page in this farm is allowed to periodically refresh its contents asynchronously (after the page has finished rendering). - -When set to false, all DataFormWebParts will ignore the automatic refresh interval provided in Web Part properties. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Force -Forces the deletion or updating of the service connection point. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InstalledProductsRefresh -Updates the current machine license state with the list of products that are installed in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ServiceConnectionPointBindingInformation -Adds or updates the service connection point for the current farm in Active Directory Domain Service (AD DS). - -The type must be an array of strings that are key value pairs that will be added to the service connection point. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceConnectionPointDelete -Delete the service connection point for the current farm in AD DS. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkflowBatchSize -Specifies the paging size for events delivered to a single workflow instance. - -For each request, the events are streamed out 100 at a time. - -Batch size is the number of events processed for a single workflow instance, which can have many events queued at the same time. -Throttle will override batch size; if the workflow instance cannot be started or restarted because there are too many instances running across all front-end Web servers, none of the events will be fetched, regardless of the batch size. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WorkflowEventDeliveryTimeout -Specifies the time as an integer in which a workflow job must run without the job timing out. - -If the workflow job does time out, it gets put back in the queue to be run again. - -For example, if the value is set to 5, the workflow job must run within 5 minutes are the workflow job will time out. -Any workflow job that does time out is placed back in the queue to run again.The default value is 5. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WorkflowPostponeThreshold -Specifies the number of workflows that can be running in IIS against a content database at a time before new workflow instances get postponed into a queue. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -ASPScriptOptimizationEnabled -Specifies if ASP Script optimization is enabled. The default value is false (off). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -UserAccountDirectoryPathIsImmutable -Specifies if the `UserAccountDirectoryPath` property on an `SPSite` object is immutable. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultActivateOnSiteMasterValue -Specifies whether to activate site master as default. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSiteSubscriptionSettingsValueLength -Sets the maximum size of a SiteSubscription property value. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxTenantStoreValueLength -Sets the maximum size of a Tenant Store property value. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteMasterMode -Specifies if site master mode is turned on or off. The default value is off. - -```yaml -Type: SPSiteMasterMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteMasterValidationIntervalInHours -Determines the length of time, in hours, to validate the Site Master. - -The default value is 24. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPIRMSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPIRMSettings.md deleted file mode 100644 index 70a75ece09..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPIRMSettings.md +++ /dev/null @@ -1,269 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spirmsettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPIRMSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPIRMSettings - -## SYNOPSIS -Sets the Information Rights Management (IRM) settings. - - -## SYNTAX - -### UseSpecifiedCertificateUrl -``` -Set-SPIRMSettings -CertificateServerUrl <Uri> [-IrmEnabled] [-AssignmentCollection <SPAssignmentCollection>] - [-CertificatePassword <SecureString>] [-Confirm] [-ServiceAuthenticationCertificate <X509Certificate2>] - [-SubscriptionScopeSettingsEnabled] [-WhatIf] [-UseOauth] [<CommonParameters>] -``` - -### UseServiceDiscovery -``` -Set-SPIRMSettings [-IrmEnabled] [-AssignmentCollection <SPAssignmentCollection>] - [-CertificatePassword <SecureString>] [-Confirm] [-ServiceAuthenticationCertificate <X509Certificate2>] - [-SubscriptionScopeSettingsEnabled] [-UseActiveDirectoryDiscovery] [-WhatIf] [-UseOauth] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Set-SPIRMSettings` cmdlet to set the Information Rights Management (IRM) settings for the tenant. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1------------ -``` -Set-SPIRMSettings -RmsEnabled -UseActiveDirectoryDiscovery -``` - -This example enables IRM for the farm and configures it to use the default RMS server configured in Active Directory. - -### --------------EXAMPLE 2------------ -``` -Set-SPIRMSettings -RmsEnabled -CertificateServerUrl https://myrmsserver -``` - -This example enables IRM for the farm and specifies the URL of the RMS server to use. - -### --------------EXAMPLE 3------------ -``` -site = Get-SPSite http://myspserver -$subscription = $site.SiteSubscription -Set-SPIRMSettings -SiteSubscription $subscription -RmsEnabled -CertificateServerUrl https://myrmsserver -``` - -This example enables IRM for the specified tenant and specifies the URL of the RMS server to use. - -### --------------EXAMPLE 4------------ -``` -Set-SPIRMSettings -RmsEnabled:$false -``` - -This example disables IRM for the farm. - - -## PARAMETERS - -### -CertificateServerUrl -Specifies the address of the RMS certificate server to use for the tenant. - -```yaml -Type: Uri -Parameter Sets: UseSpecifiedCertificateUrl -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IrmEnabled -Specifies whether or not IRM is enabled in the tenant. - -The default value is false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CertificatePassword -Specifies the password to access the Service Authentication Certificate. -This password is required in order to install the certificate in the machine certificate store. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceAuthenticationCertificate -Specifies the service authentication certificate. - -If the parameter is specified and not null, the authentication certificate is used when connecting from this farm to the RMS server. -If the parameter is not specified, the local farm connects to RMS server using integrated windows authentication. - -```yaml -Type: X509Certificate2 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriptionScopeSettingsEnabled -Specifies whether or not IRM can be configured at the site subscription scope. - -Site subscriptions can only configure custom IRM settings if IRM is enabled at the Farm scope. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseActiveDirectoryDiscovery -Specifies whether or not the RMS service should be used for discovery that will determine the address of the RMS server in the domain. - -```yaml -Type: SwitchParameter -Parameter Sets: UseServiceDiscovery -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseOauth -Specifies whether OAuth should be used. - -The valid values are True and False. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPIRMSettings](Get-SPIRMSettings.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathFormTemplate.md deleted file mode 100644 index b001f1ce9b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPInfoPathFormTemplate - -## SYNOPSIS -Sets properties of a InfoPath form template. - - -## SYNTAX - -``` -Set-SPInfoPathFormTemplate [-Identity] <SPFormTemplatePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Category <String>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPInfoPathFormsTemplate` cmdlet modifies the category of an InfoPath form template or to specify the browser streams for the form template. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Set-InfoPathFormTemplate -Identity "Sample.xsn" -Category "WorkFlowCategory" -``` - -This example modifies the category property of a form template for a specified name. - - -## PARAMETERS - -### -Identity -Specifies the InfoPath form template to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a form template (for example, InfoPathFormTemplate1); a valid name of a form template files (for example, FormTemplateFile1.xsn); or an instance of a valid SPFormTemplate object. - -```yaml -Type: SPFormTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Category -Specifies the category of the form template. -The category name can have a maximum of 255 characters. - -The type must be a valid name of a form template category; for example, FormTemplateCategory1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathFormsService.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathFormsService.md deleted file mode 100644 index 255e16fbba..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathFormsService.md +++ /dev/null @@ -1,473 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spinfopathformsservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPInfoPathFormsService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPInfoPathFormsService - -## SYNOPSIS -Sets parameters for InfoPath Forms Services in SharePoint Server. - - -## SYNTAX - -``` -Set-SPInfoPathFormsService [-ActiveSessionTimeout <Int32>] [-AllowEmbeddedSqlForDataConnections <String>] - [-AllowUdcAuthenticationForDataConnections <String>] [-AllowUserFormBrowserEnabling <String>] - [-AllowUserFormBrowserRendering <String>] [-AllowUserFormCrossDomainDataConnections <String>] - [-AllowViewState <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DefaultDataConnectionTimeout <Int32>] [-Identity <SPFormsServicePipeBind>] - [-MaxDataConnectionResponseSize <Int32>] [-MaxDataConnectionRoundTrip <Int32>] - [-MaxDataConnectionTimeout <Int32>] [-MaxFormLoadTime <Int32>] [-MaxPostbacksPerSession <Int32>] - [-MaxUserActionsPerPostback <Int32>] [-MemoryCacheSize <Int32>] [-RequireSslForDataConnections <String>] - [-ViewStateThreshold <Int32>] [-WhatIf] [-MaxSizeOfUserFormState <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPInfoPathFormsService` cmdlet modifies the settings for InfoPath Forms Services in SharePoint Server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE 1----------------- -``` -Set-SPInfoPathFormsService -AllowUserFormBrowserEnabling $true -AllowUserFormBrowserRendering $false -``` - -This example modifies the AllowUserFormBrowserEnabling and AllowUserFormBrowserRendering parameter values. - -### --------------EXAMPLE 2----------------- -``` -Set-SPInfoPathFormsService -AllowViewState $true -ViewStateThreshold 40961 -``` - -This example modifies the AllowViewState and ViewStateThreshold parameter values. - -## PARAMETERS - -### -ActiveSessionTimeout -Specifies the duration, in minutes, that a form's session state can remain active. -The default value is 1440. - -The type must be a non-negative integer value in the range from 0 through 999,999. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowEmbeddedSqlForDataConnections -Specifies a value that indicates whether embedded SQL authentication can be used by browser-enabled InfoPath form templates. - -The type must be one of the following values: True, False (default) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUdcAuthenticationForDataConnections -Specifies that authentication information in a universal data connection (.udcx file) can be used. - -The type must be one of the following values: True (default), False - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserFormBrowserEnabling -Specifies that users can browser enable form templates that do not contain form code, require full trust, enable rendering on a mobile device, or use a data connection managed by a server administrator. - -The type must be one of the following values: True (default), False - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserFormBrowserRendering -Specifies that browser-enabled form templates will be rendered by InfoPath Forms Services. - -The type must be one of the following values: True (default), False - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserFormCrossDomainDataConnections -Specifies that data connections to data sources located in a different domain can be queried. - -The type must be one of the following values: True, False (default) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowViewState -Defines the location to store form session state: View state when True, or Session State Service when False. - -The type must be one of the following values: True, False (default) - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultDataConnectionTimeout -Specifies the default data connection timeout in milliseconds. -The default value is 10000 (10 seconds). - -The type must be a non-negative integer and less than or equal to the value set for MaxDataConnectionTimeout. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the InfoPath Forms Services service to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an InfoPath Forms Services service (for example, FormsService1); or an instance of a valid SPFormsService object. - -```yaml -Type: SPFormsServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxDataConnectionResponseSize -Specifies the maximum size allowed for a data connection response. -The default value is 15000 kilobytes (KB). - -The type must be a non-negative integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxDataConnectionRoundTrip -Sets a threshold, in milliseconds, for the maximum time it takes from the start of a data request to the return of the data request on the server (the data connection round trip). -If the data connection round trip time exceeds this threshold, an event is logged in the Operational log. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxDataConnectionTimeout -Specifies the maximum data connection timeout in milliseconds. -The default value is 20000 (20 seconds). - -The type must be a non-negative integer and less than or equal to 999999. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxFormLoadTime -Sets a threshold, in milliseconds, for maximum form load time. -If form load time exceeds this threshold, an event is logged in the Operational log. - -The MaxFormLoadTime parameter measures the time it takes for a form to open, starting from when the request is accepted by the server until it leaves the server. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxPostbacksPerSession -Specifies the value of the maximum postbacks that an instance of a browser-enabled InfoPath form template can make to the InfoPath Forms Services service. -The default value is 20. - -The type must be a non-negative integer and less than or equal to 999999. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxUserActionsPerPostback -Specifies the maximum user actions per postback. -The default value is 200. - -The type must be a non-negative integer and less than or equal to 999999. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MemoryCacheSize -Sets the size, in megabytes (MB), of the cache for solutions in memory. - -The default value is 250 MB. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequireSslForDataConnections -Specifies the Secure Sockets Layer (SSL) requirement value. -If data connections in browser-enabled form templates require basic authentication or digest authentication, a password is sent over the network. -Set this value to True to require an SSL-encrypted connection for these authentication types. - -The type must be one of the following values: True (default), False. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ViewStateThreshold -Specifies the maximum size in kilobytes of the session state when stored in the form view. -The default value is 40. - -The type must be a non-negative integer and less than or equal to 99,999,999. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSizeOfUserFormState -Specifies the value of the maximum size in kilobytes of session state an instance of a browser-enabled InfoPath form template can use. The default value is 4096. - -The type must be a non-negative integer and less than or equal to 999999. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathWebServiceProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathWebServiceProxy.md deleted file mode 100644 index bd995e62e5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInfoPathWebServiceProxy.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spinfopathwebserviceproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPInfoPathWebServiceProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPInfoPathWebServiceProxy - -## SYNOPSIS -Sets parameters for an existing SharePoint Web service application. - - -## SYNTAX - -``` -Set-SPInfoPathWebServiceProxy [-Identity] <SPWebServiceProxyPipeBind> [-AllowForUserForms <String>] - [-AllowWebServiceProxy <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPInfoPathWebServiceProxy` cmdlet configures exposed parameters for an existing SharePoint Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Set-SPInfoPathWebServiceProxy -Identity "https://server_name/" -AllowWebServiceProxy $true -``` - -This example sets the Web service proxy for a Web application. - - -## PARAMETERS - -### -Identity -Specifies the SharePoint Web service application proxy to update. - -The type must be a valid URL, in the form https://server_name; a valid name of a Web application (for example, WebApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPWebServiceProxy object. - -```yaml -Type: SPWebServiceProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AllowForUserForms -Specifies that a form opened in the InfoPath client can use the InfoPath Forms Services Web service proxy to connect to a Web service. -This parameter can be set only when AllowWebServiceProxy is set to True. - -The type must be one of the following: True, False The default value is False. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowWebServiceProxy -Specifies that browser-enabled form templates can use the InfoPath Forms Services Web service proxy to connect to a Web service. - -The type must be one of the following: True, False The default value is False. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInternalAppStateUpdateInterval.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInternalAppStateUpdateInterval.md deleted file mode 100644 index 3c8716aea8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPInternalAppStateUpdateInterval.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spinternalappstateupdateinterval -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPInternalAppStateUpdateInterval -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPInternalAppStateUpdateInterval - -## SYNOPSIS -Sets the interval in hours between updates of the internal app state update job. - - -## SYNTAX - -``` -Set-SPInternalAppStateUpdateInterval -AppStateSyncHours <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPInternalAppStateUpdateInterval` cmdlet to set the interval in hours between updates of the internal app state update job. -The internal app state update job gets app upgrades from the internal app directory and sets them on app instances. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------EXAMPLE------------ -``` -Set-SPInternalAppStateUpdateInterval -AppStateSyncHours 24 -``` - -This example sets a 24-hour interval between updates of the internal app state update job. - - -## PARAMETERS - -### -AppStateSyncHours -Specifies the hour for which the internal app states are updated. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPInternalAppStateUpdateInterval](Get-SPInternalAppStateUpdateInterval.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPLogLevel.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPLogLevel.md deleted file mode 100644 index c594c252ff..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPLogLevel.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sploglevel -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPLogLevel -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPLogLevel - -## SYNOPSIS -Sets the trace and event level for a set of categories. - - -## SYNTAX - -``` -Set-SPLogLevel [-AssignmentCollection <SPAssignmentCollection>] [-EventSeverity <String>] - [-Identity <String[]>] [-InputObject <PSObject>] [-TraceSeverity <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPLogLevel` cmdlet sets the Windows event logging and trace logging levels for one or more diagnostic logging categories registered in the farm. -If an event or trace associated with a category occurs, but is less severe than that category's logging level, the event or trace is not written to the event log or the trace log. -If an event or trace associated with a category occurs and is equally severe or more severe than that category's logging level, the event or trace is written to the event log or the trace log. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -set-sploglevel -TraceSeverity Monitorable -``` - -This example sets the TraceSeverity values for all categories to Monitorable. - - -### ------------------EXAMPLE 2----------------------- -``` -Set-SPLogLevel -TraceSeverity High -EventSeverity Warning -Identity "Cat1" -``` - -This example sets the EventSeverity and TraceSeverity values for a single category. - - -### ------------------EXAMPLE 3----------------------- -``` -C:\PS>"Cat1", "Cat2", "Cat3" | Set-SPLogLevel -EventSeverity Error -``` - -This example sets the EventSeverity values for multiple categories. - - -### ------------------EXAMPLE 4----------------------- -``` -Set-SPLogLevel -EventSeverity Warning -Identity "AreaName:*" -``` - -This example sets the EventSeverity values for all categories in the same area. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -EventSeverity -Specifies the category level to be set. -The category level is any one of the following values: - -- None -- ErrorCritical -- Error -- Warning -- Information -- Verbose - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the name(s) of the category or set of categories to set the throttle for; for example, "Unified Logging Service". -If the Identity parameter is not specified, the event-throttling setting is applied to all categories in the farm. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InputObject -The InputObject is pipelined to the cmdlet and can be a string in a format identical to the Identity parameter, or can be an SPDiagnosticsCategory object. -The user can retrieve one or more categories from the `Get-SPLogLevel` cmdlet, modify the category values and then pipeline them into the `Set-SPLogLevel` cmdlet. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -TraceSeverity -Specifies trace throttle to set the specified categor(ies) to. -The trace log files are text files that are written to the trace log path that is defined on the Diagnostic Logging Settings page on the SharePoint Central Administration site. -The type must be any one of the following values: - -- None (no traces are written to the trace log) -- Unexpected -- Monitorable -- High -- Medium -- Verbose -- VerboseEx - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPManagedAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPManagedAccount.md deleted file mode 100644 index f7d43bfc6a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPManagedAccount.md +++ /dev/null @@ -1,345 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spmanagedaccount -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPManagedAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPManagedAccount - -## SYNOPSIS -Configures the managed account. - - -## SYNTAX - -### NewPassword -``` -Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -ConfirmPassword <SecureString> - -NewPassword <SecureString> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-EmailNotification <Int32>] [-PreExpireDays <Int32>] [-Schedule <String>] [-SetNewPassword] [-WhatIf] - [<CommonParameters>] -``` - -### ExistingPassword -``` -Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -ExistingPassword <SecureString> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-EmailNotification <Int32>] - [-PreExpireDays <Int32>] [-Schedule <String>] [-UseExistingPassword] [-WhatIf] [<CommonParameters>] -``` - -### NewPasswordAsParameter -``` -Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -Password <SecureString> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-EmailNotification <Int32>] - [-PreExpireDays <Int32>] [-Schedule <String>] [-WhatIf] [<CommonParameters>] -``` - -### AutoGeneratePassword -``` -Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-AutoGeneratePassword] [-Confirm] [-EmailNotification <Int32>] [-PreExpireDays <Int32>] [-Schedule <String>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPManagedAccount` cmdlet sets the properties on the given managed account. - -You can use this cmdlet to change the password expiration and notification settings for the managed account: Use the default parameter set. -Additionally, you can use this cmdlet to change the password for the managed account to automatically generated passwords on a set schedule: Use the parameter set that includes the AutoGeneratePassword parameter. -You can also use this cmdlet to change the password for the managed account to a new value, known to the administrator: Use the parameter set that includes the SetNewPassword parameter. -Finally, you can use this cmdlet to change the password for the managed account to an existing value that has been already been changed in Active Directory Domain Services (AD DS): Use the parameter set that includes the UseExistingPassword parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$m = Get-SPManagedAccount -Identity "DOMAINx\UserY" -Set-SPManagedAccount -Identity $m -AutoGeneratePassword true -``` - -This example displays an explicit managed account if it exists and then attempts to update it to use automatically generated passwords. - - -## PARAMETERS - -### -Identity -Specifies the full name or partial name of the managed accounts to retrieve. - -The type must be a valid account name, in the form Domain\User, or a GUID, in the form 1234-3456-09876. - -```yaml -Type: SPManagedAccountPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ConfirmPassword -Confirms the new password for this managed account. - -```yaml -Type: SecureString -Parameter Sets: NewPassword -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExistingPassword -Sets the password for this managed account to an existing value that has already been changed in Active Directory Domain Services (AD DS). - -```yaml -Type: SecureString -Parameter Sets: ExistingPassword -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewPassword -Sets a new password for the managed account - -```yaml -Type: SecureString -Parameter Sets: NewPassword -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Password -Sets a password for the managed account. - -```yaml -Type: SecureString -Parameter Sets: NewPasswordAsParameter -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AutoGeneratePassword -Automatically generates a new password. - -The type must be either of the following values: - -- True -- False - -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: AutoGeneratePassword -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailNotification -Specifies the number of days before password change to begin e-mail notifications. - -The default value is 5. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreExpireDays -Specifies the number of days before expiration to schedule password change. - -The default value is 2. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Schedule -Specifies the new schedule on which the password change job is to run. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SetNewPassword -Sets the password to the new value that is passed in, and changes the value in AD DS. - -The type must be either of the following values: - -- True -- False - -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: NewPassword -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseExistingPassword -Sets the password to a new value passed in where the value is already changed in AD DS. - -The type must be either of the following values: - -- True -- False - -The default value is False. - -```yaml -Type: SwitchParameter -Parameter Sets: ExistingPassword -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMetadataServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMetadataServiceApplication.md deleted file mode 100644 index 4a6ce8f8b6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMetadataServiceApplication.md +++ /dev/null @@ -1,535 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spmetadataserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPMetadataServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPMetadataServiceApplication - -## SYNOPSIS -Sets the properties of a managed metadata service application. - - -## SYNTAX - -### NoQuota -``` -Set-SPMetadataServiceApplication [-Identity] <SPMetadataServiceCmdletPipeBind> [-AdministratorAccount <String>] - [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-CacheTimeCheckInterval <Int32>] [-Confirm] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] - [-DatabaseServer <String>] [-DoNotUnpublishAllPackages] [-FailoverDatabaseServer <String>] - [-FullAccessAccount <String>] [-Name <String>] [-RestrictedAccount <String>] [-SyndicationErrorReportEnabled] - [-HubUri <String>] [-MaxChannelCache <Int32>] [-ReadAccessAccount <String>] [-WhatIf] [-DisablePartitionQuota] - [<CommonParameters>] -``` - -### Quota -``` -Set-SPMetadataServiceApplication [-Identity] <SPMetadataServiceCmdletPipeBind> [-AdministratorAccount <String>] - [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-CacheTimeCheckInterval <Int32>] [-Confirm] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] - [-DatabaseServer <String>] [-DoNotUnpublishAllPackages] [-FailoverDatabaseServer <String>] - [-FullAccessAccount <String>] [-Name <String>] [-RestrictedAccount <String>] [-SyndicationErrorReportEnabled] - [-HubUri <String>] [-MaxChannelCache <Int32>] [-ReadAccessAccount <String>] [-WhatIf] - -GroupsPerPartition <Int32> -LabelsPerPartition <Int32> -PropertiesPerPartition <Int32> - -TermSetsPerPartition <Int32> -TermsPerPartition <Int32> [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPMetadataServiceApplication` cmdlet to set the properties of a managed metadata service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -$sa = Get-SPMetadataServiceApplication -Identity 'Managed Metadata Service Application' -Set-SPMetadataServiceApplication -Identity $sa -HubUri 'https://sitename/' -SyndicationErrorReportEnabled -``` - -This example adds a content type hub to an existing managed metadata service application. -It also enables error reporting when content types are imported. - - -### --------------------EXAMPLE 2--------------------- -``` -$sa = Get-SPMetadataServiceApplication -Identity 'Managed Metadata Service Application' -Set-SPMetadataServiceApplication -Identity $sa -AdministratorAccount 'contoso\username1' -FullAccessAccount 'contoso\AppPoolAccount1,contoso\AppPoolAccount2' -RestrictedAccount 'contoso\AppPoolAccount3,contoso\AppPoolAccount4,contoso\AppPoolAccount5' -ReadAccessAccount 'contoso\AppPoolAccount6' -``` - -This example sets permissions on an existing managed metadata service application. - -If you use Windows PowerShell to set any of the account values, you should set all of them. -The `Set-SPMetadataServiceApplication` cmdlet first erases all accounts, then adds the accounts that you specified. - - -## PARAMETERS - -### -Identity -Specifies the managed metadata service application to update. - -The type must be a valid GUID or the name of a valid managed metadata service application. - -```yaml -Type: SPMetadataServiceCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AdministratorAccount -A comma-separated list of user accounts or service accounts in the format \<domain\>\\\<account\> that may create and run the service application. -The accounts must already exist. - -If a value is set by using this parameter, any existing values for the FullAccessAccount, ReadAccessAccount and RestrictedAccount parameters are removed. -Consider setting all four parameters at the same time. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies an existing IIS application pool in which to run the Web service for the managed metadata service application. - -The value must be a GUID that is the identity of an SPServiceApplicationPool object; the name of an existing application pool; or an instance of a valid SPServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheTimeCheckInterval -Specifies the interval, in seconds, that a front-end Web server should wait before asking the application server for changes. -This value is set per timer job, client application, or Web application. - -The mininum value is 1, and there is no maximum value. -The default value is 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL authentication. - -If SQL authentication is to be used, either the DatabaseCredentials parameter must be specified or both the DatabaseUserName and DatabasePassword parameters must be set. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database that contains the term store for the managed metadata service application. - -The type must be a valid name of a SQL Server database; for example MeatadataDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid name of a SQL Server database; for example SqlServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotUnpublishAllPackages -If this flag is set, the packages will not be unpublished. -If the HubUri parameter is changed, all content type packages will be unpublished by default. - -If the HubUri parameter is not changed, this flag has no effect. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host server for the failover database server. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FullAccessAccount -Specifies a comma-separated set of application pool accounts in the format \<domain\>\\\<account\> that will be given read/write permission to the managed metadata service's term store and content type gallery. -The accounts must already exist. - -If a value is set by using this parameter, any existing values for the AdministratorAccount, ReadAccessAccount and RestrictedAccount parameters are removed. -Consider setting all four parameters at the same time. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the new name of the service application. -The name can contain a maximum of 128 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RestrictedAccount -Specifies a comma-separated set of application pool accounts in the format \<domain\>\\\<account\> that will be given permission to read the managed metadata service's term store and content type gallery and permission to write to open term sets and local term sets and to create new enterprise keywords. -The accounts must already exist. - -If a value is set by using this parameter, any previous values for the FullAccessAccount, ReadAccessAccount and AdministratorAccount parameters are removed. -Consider setting all four parameters at the same time. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SyndicationErrorReportEnabled -Enables reporting of errors when content types are imported. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HubUri -Specifies the fully qualified URL of the site collection that contains the content type gallery that the service will provide access to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxChannelCache -Specifies the maximum number of Windows Communication Foundation (WCF) channels that a front-end Web server holds open to the application server. -This value is set per timer job, client application, or Web application. - -The minimum value is 0, and there is no maximum value. -The default value is 4. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadAccessAccount -Specifies a comma-separated set of application pool accounts in the format \<domain\>\\\<account\> that will be given read-only permission to the managed metadata service's term store and content type gallery. -The accounts must already exist. - -If a value is set by using this parameter, any previous values for the FullAccessAccount, RestrictedAccount and AdministratorAccount parameters are removed. -Consider setting all four parameters at the same time. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisablePartitionQuota -When in partitioned mode, disables the partition quota. - -```yaml -Type: SwitchParameter -Parameter Sets: NoQuota -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupsPerPartition -When in partitioned mode, sets the maximum number of groups per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LabelsPerPartition -When in partitioned mode, sets the maximum number of labels per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PropertiesPerPartition -When in partitioned mode, sets the maximum number of properties per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TermSetsPerPartition -When in partitioned mode, sets the maximum number of term sets per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TermsPerPartition -When in partitioned mode, sets the maximum number of terms per partition. - -```yaml -Type: Int32 -Parameter Sets: Quota -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMetadataServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMetadataServiceApplicationProxy.md deleted file mode 100644 index abbd7218dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMetadataServiceApplicationProxy.md +++ /dev/null @@ -1,246 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spmetadataserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPMetadataServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPMetadataServiceApplicationProxy - -## SYNOPSIS -Sets the properties of a connection to a managed metadata service application. - - -## SYNTAX - -``` -Set-SPMetadataServiceApplicationProxy [-Identity] <SPMetadataServiceProxyCmdletPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-ContentTypePushdownEnabled] - [-ContentTypeSyndicationEnabled] [-DefaultKeywordTaxonomy] [-DefaultSiteCollectionTaxonomy] [-Name <String>] - [-DefaultProxyGroup] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPMetadataServiceApplicationProxy` cmdlet to set the properties of a connection to a managed metadata service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE 1--------------------- -``` -Set-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1" -ContentTypeSyndicationEnabled -ContentTypePushdownEnabled -``` - -This example enables content type syndication and enables content type pushdown on an existing connection to a managed metadata service application. - - -### -----------------EXAMPLE 2--------------------- -``` -Set-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1" -ContentTypeSyndicationEnabled:$false -ContentTypePushdownEnabled:$false -``` - -This example disables content type syndication and disables content type pushdown on an existing connection to a managed metadata service application. - - -### -----------------EXAMPLE 3--------------------- -``` -Set-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1" -DefaultKeywordTaxonomy -DefaultSiteCollectionTaxonomy:$false -``` - -This example configures an existing connection to a managed metadata service application to be the default location for storing enterprise keywords and prevents it from being the default location for storing column-specific term sets. - - -## PARAMETERS - -### -Identity -Specifies the connection to update. - -The type must be a GUID that represents the identity of the connection to modify, the name of a valid connection to a managed metadata service, or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentTypePushdownEnabled -Specifies that existing instances of changed content types in subsites and libraries will be updated. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ContentTypeSyndicationEnabled -Specifies that this connection will provide access to the content types that are associated with the managed metadata service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultKeywordTaxonomy -Specifies that new enterprise keywords will be stored in the term store associated with the managed metadata service application. - -Do not make more than one connection the default keyword location. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultSiteCollectionTaxonomy -Specifies that the term set that is created when you create a new managed metadata column will be stored in the term store associated with the managed metadata service application. - -Do not make more than one connection the default location for site collection term sets. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the new display name of the connection. -The name can contain a maximum of 128 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the connection be added to the default proxy group of the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMicrofeedOptions.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMicrofeedOptions.md deleted file mode 100644 index 794aed14a8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMicrofeedOptions.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spmicrofeedoptions -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPMicrofeedOptions -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPMicrofeedOptions - -## SYNOPSIS -Sets the feed cache settings. - - -## SYNTAX - -``` -Set-SPMicrofeedOptions [-AssignmentCollection <SPAssignmentCollection>] [-AsyncRefs <Boolean>] - [-MaxCacheMs <Int32>] [-MaxMentions <Int32>] [-MaxPostLength <Int32>] [-MaxTags <Int32>] - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPMicrofeedOptions cmdlet to set the feed cache settings for the current user profile application. - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Set-SPMicrofeedOptions -ProfileServiceApplicationProxy $proxy -MaxTags 4 -``` - -This example sets the maximum tags per post and reply to 4 for the specified User Profile Service Application Proxy. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE:** When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AsyncRefs -Performs reference-posts via async threads. If the value is set to True, each @mention in a thread is handled in its own .NET threadpool async thread. - - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxCacheMs -Specifies the permissible range of cache loop up time. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxMentions -Specifies the maximum number @mentions per post and reply. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxPostLength -Sets the maximum number of characters in a Microfeed post. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxTags -Specifies the maximum number #tags per post and reply. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the unique identifier for the proxy. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationProxyPipeBind -Microsoft.SharePoint.PowerShell.SPSiteSubscriptionPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMobileMessagingAccount.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMobileMessagingAccount.md deleted file mode 100644 index f6d56fdcd6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPMobileMessagingAccount.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spmobilemessagingaccount -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPMobileMessagingAccount -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPMobileMessagingAccount - -## SYNOPSIS -Configures the specified mobile messaging account. - - -## SYNTAX - -``` -Set-SPMobileMessagingAccount [-Identity] <SPMobileMessagingAccountPipeBind> - -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Password <String>] [-ServiceName <String>] [-ServiceUrl <String>] [-UserId <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPMobileMessagingAccount` cmdlet configures the specified mobile messaging account. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Set-SPMobileMessagingAccount -WebApplication https://sitename -Identity SMS -ServiceName SMSLink -ServiceUrl https://www.adatum.com/Service/MessagingService.asmx-UserId someone@example.com -Password password1 -``` - -This example changes the SMS mobile account settings of the Web application, https://sitename, to the following values:service name: SMSLink; service URL: https://www.adatum.com/Service/MessagingService.asmx; user ID: someone@example.com; and password: password1. - - -## PARAMETERS - -### -Identity -Specifies whether to return either Short Message Service (SMS) or Multimedia Messaging Service (MMS) account information. -Valid values are SMS and MMS. -If you do not specify this parameter account, information is returned for both SMS and MMS. - -```yaml -Type: SPMobileMessagingAccountPipeBind -Parameter Sets: (All) -Aliases: ServiceType, AccountType -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the identity of the Web application that hosts the managed path to delete. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid Web application name (for example, WebApplication1212); or a valid name (for example, WebApp2423). - -You either must specify WebApplication or must use the HostHeader switch and specify the full URL in the Identity parameter. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Password -Specifies the password, if credentials are required for the account. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceName -Specifies the name of the SMS service. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceUrl -Specifies the URL of the SMS service. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserId -Specifies the user name, if credentials are required for the account. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPO365LinkSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPO365LinkSettings.md deleted file mode 100644 index dbf1c35f0c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPO365LinkSettings.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spo365linksettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPO365LinkSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPO365LinkSettings - -## SYNOPSIS -Set SharePoint O365 Link Settings for Hybrid Configuration. - -## SYNTAX - -``` -Set-SPO365LinkSettings -MySiteHostUrl <String> [-Audiences <String[]>] [-RedirectSites <Boolean>] - [-HybridAppLauncherEnabled <Boolean>] [-OnedriveDefaultToCloudEnabled <Boolean>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the **Set-SPO365LinkSettings** cmdlet to configure some of Hybrid features (Hybrid site redirection, OneDrive redirection, ODB default to Cloud) without running Hybrid Configuration Wizard. - -To run this cmdlet requires farm administrator permission and that the user account has full control access to the User Profile Application service. - -## EXAMPLES - -### EXAMPLE 1 -```powershell - Set-SPO365LinkSettings -MySiteHostUrl https://contoso-my.sharepoint.com/ -RedirectSites $true -``` - -This example sets the mysite host URL to contoso-my.sharepoint.com - -## PARAMETERS - -### -Audiences -Sets the user(s) for whom redirection is active. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -HybridAppLauncherEnabled -Sets a flag that indicates whether app launcher get data from SharePoint Online (SPO) is allowed - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -MySiteHostUrl -Sets the root URL for the redirected pages. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -OnedriveDefaultToCloudEnabled -Sets a flag that indicates whether Local Onedrive is redirected to SPO OneDrive. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - - -## RELATED LINKS - -[Get-SPO365LinkSettings](Get-SPO365LinkSettings.md) - -[Test-SPO365LinkSettings](Test-SPO365LinkSettings.md) - - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPOfficeStoreAppsDefaultActivation.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPOfficeStoreAppsDefaultActivation.md deleted file mode 100644 index 75be9ab285..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPOfficeStoreAppsDefaultActivation.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spofficestoreappsdefaultactivation -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Set-SPOfficeStoreAppsDefaultActivation -schema: 2.0.0 -author: trent-green -ms.author: trgreen -ms.reviewer: ---- - -# Set-SPOfficeStoreAppsDefaultActivation - -## SYNOPSIS -Sets the properties of apps for Office. - - -## SYNTAX - -### AppsForOfficeSettingsInSiteSubscription -``` -Set-SPOfficeStoreAppsDefaultActivation -Enable <Boolean> -SiteSubscription <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### AppsForOfficeSettingsInWebApplication -``` -Set-SPOfficeStoreAppsDefaultActivation -Enable <Boolean> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Set-SPOfficeStoreAppsDefaultActivation` cmdlet to set app settings for Office that are on the Office Store and would be started when the document that contains those apps in their browser is opened. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251831 (https://go.microsoft.com/fwlink/p/?LinkId=251831). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPOfficeStoreAppsDefaultActivation -SiteSubscription efca5b88-b3a3-448d-afbc-ef620f4744f1 -Enable $true -``` - -This example enables the apps for Office from the Office Store Office client that uses the subscription id, efca5b88-b3a3-448d-afbc-ef620f4744f1. - - -## PARAMETERS - -### -Enable -Specifies whether the apps for Office from the Office Store should be started. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the Site Group to which the settings apply. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: AppsForOfficeSettingsInSiteSubscription -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the URL, GUID, or name of the web application to which the setting applies. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: AppsForOfficeSettingsInWebApplication -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPOfficeStoreAppsDefaultActivation](Get-SPOfficeStoreAppsDefaultActivation.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPassPhrase.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPassPhrase.md deleted file mode 100644 index d774ad1245..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPassPhrase.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sppassphrase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPPassPhrase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPPassPhrase - -## SYNOPSIS -Sets the pass phrase to a new value. - - -## SYNTAX - -### LocalOnly -``` -Set-SPPassPhrase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-LocalServerOnly] [-WhatIf] - -PassPhrase <SecureString> [<CommonParameters>] -``` - -### AcrossFarm -``` -Set-SPPassPhrase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - -ConfirmPassPhrase <SecureString> -PassPhrase <SecureString> [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPPassPhrase` cmdlet sets the Passphrase to a new Passphrase value. -If the LocalServerOnly parameter is not used, the farm encryption key is re-encrypted with the new value and attempts to propagate this value to all other servers in the farm. -If the LocalServerOnly parameter is used, this is updated on the local machine only and the farm encryption key is not changed. -The Passphrase value must be the same on all servers in the farm if the farm is to function correctly. -So if the Passphrase fails to propagate to all servers, the LocalServerOnly parameter can be used to set the remaining servers to the new Passphrase value manually. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -$passphrase = ConvertTo-SecureString -asPlainText -Force -Set-SPPassPhrase -PassPhrase $passphrase -Confirm -``` - -This example queries for a string to use as a passphrase and sets the farm passphrase to a new value. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalServerOnly -Scopes the Passphrase change to the local server only. -If this parameter is not used, the Passphrase change is performed farm-wide. - -```yaml -Type: SwitchParameter -Parameter Sets: LocalOnly -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConfirmPassPhrase -Passphrase is typed a second time to confirm that it matches the first entry. - -```yaml -Type: SecureString -Parameter Sets: AcrossFarm -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassPhrase -Specifies the new Passphrase value. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPerformancePointSecureDataValues.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPerformancePointSecureDataValues.md deleted file mode 100644 index aca53ec125..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPerformancePointSecureDataValues.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spperformancepointsecuredatavalues -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPPerformancePointSecureDataValues -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPPerformancePointSecureDataValues - -## SYNOPSIS -Sets global settings for the unattended service account. - -## SYNTAX - -``` -Set-SPPerformancePointSecureDataValues - [-ServiceApplication] <SPPerformancePointMonitoringServiceApplicationPipeBind> - -DataSourceUnattendedServiceAccount <PSCredential> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPPerformancePointSecureDataValues` cmdlet sets global settings and properties for the unattended service account. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE 1-------------------- -``` -Set-SPPerformancePointSecureDataValues -ServiceApplication "PerformancePoint Service Application" -DataSourceUnattendedServiceAccount (get-credential) -``` - -This example shows how to set the unattended service account by prompting the user for the user name and password. - -### --------------------EXAMPLE 2-------------------- -``` -Set-SPPerformancePointSecureDataValues -ServiceApplication "PerformancePoint Service Application" -DataSourceUnattendedServiceAccount (New-Object System.Management.Automation.PSCredential "domain\user", (ConvertTo-SecureString "password" -AsPlainText -Force)) -``` - -This example shows how to pass the user name and password as parameters to the cmdlet. - -The DataSourceUnattendedServiceAccount parameter accepts a PSCredential object. -Therefore, to pass in this value as a parameter, a new PSCredential object must be created using the desired username and password values. -The PSCredential object requires that the password be given as a SecureString type. - -## PARAMETERS - -### -ServiceApplication -Specifies the PerformancePoint Service application that is to be configured. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -DataSourceUnattendedServiceAccount -Specifies the user credentials (user name and password) for the data source of the unattended service account. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPerformancePointServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPerformancePointServiceApplication.md deleted file mode 100644 index 1ad82523c0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPerformancePointServiceApplication.md +++ /dev/null @@ -1,745 +0,0 @@ ---- -external help file: Microsoft.PerformancePoint.Scorecards.BIMonitoringService.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spperformancepointserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPPerformancePointServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPPerformancePointServiceApplication - -## SYNOPSIS -Sets global runtime properties for a PerformancePoint Services application. - -## SYNTAX - -``` -Set-SPPerformancePointServiceApplication [-Identity] <SPPerformancePointMonitoringServiceApplicationPipeBind> - [-AnalyticQueryCellMax <Int32>] [-AnalyticQueryLoggingEnabled <Boolean>] [-ApplicationCacheEnabled <Boolean>] - [-ApplicationCacheMinimumHitCount <Int32>] [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] - [-ApplicationProxyCacheEnabled <Boolean>] [-AssignmentCollection <SPAssignmentCollection>] - [-CommentsDisabled <Boolean>] [-CommentsScorecardMax <Int32>] [-Confirm] [-DatabaseFailoverServer <String>] - [-DatabaseName <String>] [-DatabaseServer <String>] [-DatabaseSQLAuthenticationCredential <PSCredential>] - [-DataSourceQueryTimeoutSeconds <Int32>] [-DecompositionTreeMaximum <Int32>] [-ElementCacheSeconds <Int32>] - [-FilterRememberUserSelectionsDays <Int32>] [-FilterTreeMembersMax <Int32>] - [-IndicatorImageCacheSeconds <Int32>] [-MSMQEnabled <Boolean>] [-MSMQName <String>] - [-SelectMeasureMaximum <Int32>] [-SessionHistoryHours <Int32>] [-SettingsDatabase <String>] - [-ShowDetailsInitialRows <Int32>] [-ShowDetailsMaxRows <Int32>] [-ShowDetailsMaxRowsDisabled <Boolean>] - [-TrustedContentLocationsRestricted <Boolean>] [-TrustedDataSourceLocationsRestricted <Boolean>] [-WhatIf] - [-AnalyticResultCacheMinimumHitCount <Int32>] [-DatabaseUseWindowsAuthentication <Boolean>] - [-DataSourceUnattendedServiceAccountTargetApplication <String>] [-FilterSearchResultsMax <Int32>] - [-UseEffectiveUserName <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPPerformancePointServiceApplication` cmdlet updates global runtime properties for a PerformancePoint Service application. -The changes made to properties by using this cmdlet affect all servers in the farm that run the instance of the specified PerformancePoint Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE---------------------- -``` -$sa = Get-SPPerformancePointServiceApplication -Set-SPPerformancePointServiceApplication -Identity $sa -DataSourceQueryTimeoutSeconds 5000 -``` - -This example sets the Data Source Query Timeout setting to a value of 5000. -This cmdlet is equivalent to the PerformancePoint Service Settings page on the SharePoint Central Administration Web site. - -## PARAMETERS - -### -Identity -Specifies the PerformancePoint Service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointMonitoringServiceApplication object. - -```yaml -Type: SPPerformancePointMonitoringServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AnalyticQueryCellMax -Specifies the maximum number of returned cells in an analytic grid. - -A valid integer between 1-1,000,000,000. -The default value is 100,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnalyticQueryLoggingEnabled -Turns on verbose logging of query events. - -The type must be one of the following: True, False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationCacheEnabled -Specifies whether rendered output cache on the application server is on (True) or off (False). -The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationCacheMinimumHitCount -Specifies the minimum number of times rendered output must be requested before it is added to cache. -The default value is 2. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing IIS application pool to run the Web service in for the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ApplicationProxyCacheEnabled -Specifies rendered output cache on the web front end. -The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CommentsDisabled -Specifies that users can add comments to scorecard cells. - -The type must be one of the following: $True, $False. -The default value is $False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CommentsScorecardMax -Specifies the maximum number of comments that can be added to a scorecard. -The default value is 1000. - -The type must be an integer value in the range of 1 to 1,000,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseFailoverServer -Specifies the name of the database server that contains the PerformancePoint Services database that must be mirrored. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation 2010 with Service Pack 1 (SP1). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the PerformancePoint Services database that will be created when the service application is provisioned. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation 2010 with Service Pack 1 (SP1). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the database server where the PerformancePoint Services database will be created. -This should be the same server name that is used for the SharePoint content and configuration databases. - -The value may be written as SQL instance\server if it is not referring to the default instance. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseSQLAuthenticationCredential -Determines whether to use Windows authentication or SQL Server authentication when connecting to a PerformancePoint Services database. - -This parameter was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataSourceQueryTimeoutSeconds -Specifies the time, in seconds, before a data source query times out. -The default value is 300. - -The type must be an integer value in the range of 1 to 36,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DecompositionTreeMaximum -Specifies the maximum number of items (per level) returned to the decomposition tree visualization. - -A valid integer value between 1-1,000,000. -The default value is 25. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ElementCacheSeconds -Specifies the first class object cache expiration time. -The default value is 15. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterRememberUserSelectionsDays -Specifies the number of days that user filter selections are remembered. -The default value is 90. - -The type must be an integer value in the range of 1 to 10,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterTreeMembersMax -The maximum number of records to show in filter treeview control. -The default value is 500. - -An integer value in the range of 1 to 100,000 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IndicatorImageCacheSeconds -Specifies the time, in seconds, that key performance indicator (KPI) icons are cached. -The default value is 10. - -The type must be an integer value in the range of 1 to 3600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MSMQEnabled -Specifies that notifications are sent to Microsoft Message Queuing (MSMQ) on content change. - -The type must be one of the following: True, False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MSMQName -Specifies the name of the queue. -The queue name can contain a maximum of 380 characters and cannot contain the following characters: CR (ASCII 13), LF (ASCII 10), backslash (\\), plus sign (+), comma (,), or quotation marks (""). - -The type must be a valid MSMQ name; for example, MessageQueue1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SelectMeasureMaximum -Specifies the maximum number of measures to show in a dashboard Select Measure control. -The default value is 1000. - -The type must be an integer value in the range of 1 to 1,000,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionHistoryHours -Specifies the number of hours between clearing of expired user navigation history. -The default value is 2. - -The type must be an integer value in the range of 1 to 48. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SettingsDatabase -Specifies the name of the PerformancePoint Service database used for that service application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowDetailsInitialRows -Specifies the initial number of rows to retrieve for show details. -The default value is 1000. - -The type must be an integer value in the range of 1 to 100,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowDetailsMaxRows -Specifies the maximum number of rows to retrieve for show details. - -The type must be an integer value in the range of 1 to 1,000,000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowDetailsMaxRowsDisabled -Turns off the ShowDetailsInitialRows setting. -If set to true, Analysis Services controls limit. - -The type must be one of the following: True, False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedContentLocationsRestricted -Specifies that only specified locations are trusted. -The default setting is false (trust all content locations). - -The type must be one of the following: True, False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TrustedDataSourceLocationsRestricted -Specify to trust only specified data source locations. -The default is to trust all data source locations. - -The type must be one of the following: True, False. -The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AnalyticResultCacheMinimumHitCount -The minimum number of times an analytic report needs to be accessed before caching starts happening. The default value is 0. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUseWindowsAuthentication -When this value is set to true, Performance Point Services disables from using SQL authentication against all data sources. - -The type must be one of the following: $True, $False. The default value is $False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataSourceUnattendedServiceAccountTargetApplication -The name of the Secure Store Application that will be used by default to access data sources. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FilterSearchResultsMax -The maximum number of items to return on a Dashboard when viewing a filter. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseEffectiveUserName -Enables the use of the Analysis Services Effective User Name feature. - -The type must be one of the following: True, False. The default value is False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPowerPointConversionServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPowerPointConversionServiceApplication.md deleted file mode 100644 index b263df6d40..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPPowerPointConversionServiceApplication.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Powerpoint.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sppowerpointconversionserviceapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPPowerPointConversionServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPPowerPointConversionServiceApplication - -## SYNOPSIS -Configures settings for a PowerPoint Conversion Service application. - - -## SYNTAX - -``` -Set-SPPowerPointConversionServiceApplication [-Identity] <SPPowerPointConversionServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CacheExpirationPeriodInSeconds <UInt32>] - [-MaximumConversionsPerWorker <UInt32>] [-WorkerKeepAliveTimeoutInSeconds <UInt32>] - [-WorkerProcessCount <UInt32>] [-WorkerTimeoutInSeconds <UInt32>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPPowerPointConversionServiceApplication` cmdlet to set properties and settings for an instance of a PowerPoint Conversion Service application that is in a farm. - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Set-SPPowerPointConversionServiceApplication -Identity "MyWorkgroupPPTApp" -CacheExpirationPeriodInSeconds 1200 -``` - -This example establishes new operational defaults for the conversion cache expiration. - - -### --------------------EXAMPLE 2--------------------- -``` -Set-SPPowerPointConversionServiceApplication -Identity "MyWorkgroupPPTApp" -DisableBinaryScan:$false -``` - -This example disables binary scanning of documents. - - -## PARAMETERS - -### -Identity -Specifies the unique name of this PowerPoint Conversion Service application. - -```yaml -Type: SPPowerPointConversionServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CacheExpirationPeriodInSeconds -Specifies the maximum time, in seconds, that items remain in the back-end server cache. -The default value is 600 seconds (10 minutes). - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumConversionsPerWorker -Specifies the maximum number of presentations that a conversion worker process can convert before recycling. -The default value is 5. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkerKeepAliveTimeoutInSeconds -Specifies the maximum time, in seconds, that a conversion worker process can be unresponsive before being terminated. -The default value is 120 seconds. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkerProcessCount -Specifies the number of active instances of the conversion worker process on each back-end. -This value must be less than the Windows Communication Foundation (WCF) connection limit for this computer. -The default value is 3. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WorkerTimeoutInSeconds -Specifies the maximum time, in seconds, that a conversion worker process is given for any single conversion. -The default is 300 seconds (5 minutes). - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPPowerPointConversionServiceApplication](New-SPPowerPointConversionServiceApplication.md) - -[New-SPPowerPointConversionServiceApplicationProxy](New-SPPowerPointConversionServiceApplicationProxy.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplication.md deleted file mode 100644 index af9a7f55a7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplication.md +++ /dev/null @@ -1,423 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprofileserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPProfileServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProfileServiceApplication - -## SYNOPSIS -Sets properties of a User Profile Service application. - -## SYNTAX - -### Default -``` -Set-SPProfileServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-GetNonImportedObjects <Boolean>] [-MySiteHostLocation <SPSitePipeBind>] - [-ProfileDBCredentials <PSCredential>] [-ProfileSyncDBCredentials <PSCredential>] - [-ProfileSyncDBFailoverServer <String>] [-PurgeNonImportedObjects <Boolean>] - [-SocialDBCredentials <PSCredential>] [-SocialDBFailoverServer <String>] [-Name <String>] - [-UseOnlyPreferredDomainControllers <Boolean>] [-WhatIf] [-ProfileDBFailoverServer <String>] - [<CommonParameters>] -``` - -### MySiteSettings -``` -Set-SPProfileServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-GetNonImportedObjects <Boolean>] -MySiteHostLocation <SPSitePipeBind> - [-MySiteManagedPath <SPPrefixPipeBind>] [-ProfileDBCredentials <PSCredential>] - [-ProfileSyncDBCredentials <PSCredential>] [-ProfileSyncDBFailoverServer <String>] - [-PurgeNonImportedObjects <Boolean>] [-SiteNamingConflictResolution <String>] - [-SocialDBCredentials <PSCredential>] [-SocialDBFailoverServer <String>] [-Name <String>] - [-UseOnlyPreferredDomainControllers <Boolean>] [-WhatIf] [-ProfileDBFailoverServer <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The Set-SPProfileServiceApplication cmdlet sets properties of a User Profile Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------EXAMPLE--------------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'User Profile Service Application'} -Set-SPProfileServiceApplication -Identity $sa -PurgeNonImportedObjects:$true -``` - -This example purges objects from the Profile database which are not in scope of the User Profile import. - - -## PARAMETERS - -### -Identity -Specifies the User Profile Service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubscriptionSettingsApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing IIS application pool in which to run the Web service for the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GetNonImportedObjects -Specifies whether to inform the users that did not come from the import pipeline and will be marked for deletion. -The list of users marked for deletion is displayed to the console window. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MySiteHostLocation -Specifies the site collection where the My Site will be provisioned. - -The type must be a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscription1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -```yaml -Type: SPSitePipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MySiteManagedPath -Specifies the managed path location of personal sites. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: SPPrefixPipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ProfileDBCredentials -Specifies the set of security credentials, such as a user name and a password, that is used to connect to the User Profile database that this cmdlet creates. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileSyncDBCredentials -Specifies the set of security credentials, such as a user name and a password, that will be used to connect to the Profile Sync database that is specified in the ProfileSyncDBName parameter. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileSyncDBFailoverServer -Specifies the name of the failover SQL server for Profile database. -It is used to build the connection string for the Profile database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PurgeNonImportedObjects -Specifies whether to mark the non-imported users in the profile store for deletion and then inform the users that did not come from the import pipeline which will be marked for deletion. -The list of users marked for deletion is displayed on the console window - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteNamingConflictResolution -Specifies the format to use to name personal sites. - -Use one of the following integer values: - -1--Personal site collections are to be based on user names without any conflict resolution. -For example, https://portal_site/location/username/ - -2-- Personal site collections are to be based on user names with conflict resolution by using domain names. -For example, .../username/ or .../domain_username/ - -3 Personal site collections are to be named by using domain and user name always, to avoid any conflicts. -For example, https://portal_site/location/domain_username/ - -The default value is 1 (do not resolve conflicts). - -```yaml -Type: String -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialDBCredentials -The set of security credentials, including a user name and a password, that is used to connect to the Social database that this cmdlet creates. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SocialDBFailoverServer -Specifies the name of the failover SQL server for Social database. -It is used to build the connection string for the Social database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name for the new User Profile Service application. -The name that you use must be a unique name of a User Profile Service application in this farm. -The name can be a maximum of 128 characters. - -The type must be a valid name of a User Profile Service application; for example, UserProfileSvcApp1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseOnlyPreferredDomainControllers -Restricts profile synchronization communication to a specific domain controller. - -The valid values are $true or $false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileDBFailoverServer -Specifies the name of the failover SQL server for Profile database. It is used to build the connection string for the Profile database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplicationProxy.md deleted file mode 100644 index 930f28636a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplicationProxy.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprofileserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPProfileServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProfileServiceApplicationProxy - -## SYNOPSIS -Sets properties of a proxy for a User Profile Service application. - -## SYNTAX - -``` -Set-SPProfileServiceApplicationProxy [-Identity] <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] - [-MySiteHostLocation <SPSitePipeBind>] [-MySiteManagedPath <SPPrefixPipeBind>] [-Name <String>] - [-SiteNamingConflictResolution <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProfileServiceApplicationProxy` cmdlet sets properties of a proxy for a User Profile Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ----------------EXAMPLE--------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq 'User Profile Service Application Proxy'} -Set-SPProfileServiceApplicationProxy -Identity $proxy -SiteNamingConflictResolution 2 -``` - -This example sets the User Profile Service Application Proxy to use a site naming conflict resolution to use domain names prefixed to usernames. - - -## PARAMETERS - -### -Identity -Specifies the User Profile Service application proxy to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application proxy (for example, UserProfileSvcProxy1); or an instance of a valid SPServiceApplicationProxy object. - - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the User Profile Service application proxy is added to the default proxy group for the local farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MySiteHostLocation -Specifies the site collection where the My Site will be created. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MySiteManagedPath -Specifies the managed path location of personal sites. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: SPPrefixPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the display name for the User Profile Service application. -The name that you use must be a unique name of a User Profile Service application in this farm. -The name can be a maximum of 128 characters. - -The type must be a name of a valid service application proxy; for example, UserProfileSvcProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteNamingConflictResolution -Specifies the format to use to name personal sites. - -Use one of the following integer values: - -1 Personal site collections are to be based on user names without any conflict resolution. -For example, https://portal_site/location/username/ - -2 Personal site collections are to be based on user names with conflict resolution by using domain names. -For example, .../username/ or .../domain_username/ - -3 Personal site collections are to be named by using domain and user name always, to avoid any conflicts. -For example, https://portal_site/location/domain_username/ - -The default value is 1 (do not resolve conflicts). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplicationSecurity.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplicationSecurity.md deleted file mode 100644 index d45a7b58bf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProfileServiceApplicationSecurity.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprofileserviceapplicationsecurity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPProfileServiceApplicationSecurity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProfileServiceApplicationSecurity - -## SYNOPSIS -Sets permission and identity information. - -## SYNTAX - -``` -Set-SPProfileServiceApplicationSecurity -Identity <SPObjectSecurity> - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [-Type <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPProfileServiceApplictionSecurity` cmdlet to set permission and identity information for the following User Profile objects: - -- Read individual My Sites -- Use Personal Features -- Use Social Features -- Create Personal Site - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -$security = Get-SPProfileServiceApplicationSecurity -ProfileServiceApplicationProxy $proxy -$everyone = New-SPClaimsPrincipal -Identity 'c:0(.s|true' -IdentityType EncodedClaim -Revoke-SPObjectSecurity -Identity $security -Principal $everyone -Rights 'Create Personal Site' -Set-SPProfileServiceApplicationSecurity -Identity $security -ProfileServiceApplicationProxy $proxy -``` - -This example revokes the right 'Create Personal Site' from All Authenticated Users. - -### --------------------EXAMPLE 2--------------------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -$security = Get-SPProfileServiceApplicationSecurity -ProfileServiceApplicationProxy $proxy -$everyone = New-SPClaimsPrincipal -Identity 'c:0(.s|true' -IdentityType EncodedClaim -Grant-SPObjectSecurity -Identity $security -Principal $everyone -Rights 'All' -Set-SPProfileServiceApplicationSecurity -Identity $security -ProfileServiceApplicationProxy $proxy -``` - -This example grants the right 'All' to All Authenticated Users. - -## PARAMETERS - -### -Identity -Specifies the User Profile Service Application security object. - -```yaml -Type: SPObjectSecurity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the unique identifier for the proxy. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the account under which this service should run. -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Type -Specifies the type of object to display. - -The type is any one of the following values: - -- MySiteReaderACL -- UserACL - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectDatabaseQuota.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectDatabaseQuota.md deleted file mode 100644 index 8fdf634ed5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectDatabaseQuota.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectdatabasequota -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectDatabaseQuota -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectDatabaseQuota - -## SYNOPSIS -Microsoft internal use only. - -## SYNTAX - -### settings -``` -Set-SPProjectDatabaseQuota [-Settings] <ProjectDatabaseQuotaSettings> -Url <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### options -``` -Set-SPProjectDatabaseQuota [-Enabled] -MaxDbSize <Int32> -ReadOnlyLimit <Int32> - -ReadOnlyWarningThreshold <Int32> -Url <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Microsoft internal use only. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` - {{ Add example code here }} -``` - -{{ Add example description here }} - - -## PARAMETERS - -### -Settings -Microsoft internal use only. - -```yaml -Type: ProjectDatabaseQuotaSettings -Parameter Sets: settings -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: options -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxDbSize -Microsoft internal use only. - -```yaml -Type: Int32 -Parameter Sets: options -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadOnlyLimit -Microsoft internal use only. - -```yaml -Type: Int32 -Parameter Sets: options -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadOnlyWarningThreshold -Microsoft internal use only. - -```yaml -Type: Int32 -Parameter Sets: options -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Microsoft internal use only. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Microsoft internal use only. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectEventServiceSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectEventServiceSettings.md deleted file mode 100644 index 64ff69bade..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectEventServiceSettings.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojecteventservicesettings -applicable: Project Server 2016, Project Server 2019 -title: Set-SPProjectEventServiceSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectEventServiceSettings - -## SYNOPSIS -Allows you to change the Microsoft Project Server Events Service 2016 TCP port settings. If you change the TCP port, the Microsoft Project Server Events Service 2016 needs to be restarted for the changes to take effect. - -## SYNTAX - -``` -Set-SPProjectEventServiceSettings [-AssignmentCollection <SPAssignmentCollection>] [-NetTcpPort <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -Allows you to change the Microsoft Project Server Events Service 2016 TCP port settings. If you change the TCP port, the Microsoft Project Server Events Service 2016 needs to be restarted for the changes to take effect. - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPProjectEventServiceSettings -NetTcpPort 16100 -``` - -This example tells the service to listen on port 16100. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NetTcpPort -TCP port to listen on. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectOdataConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectOdataConfiguration.md deleted file mode 100644 index 8d424bb3f5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectOdataConfiguration.md +++ /dev/null @@ -1,235 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectodataconfiguration -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectOdataConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectOdataConfiguration - -## SYNOPSIS -Sets the properties for how the OData service is configured for an instance of Project Web App. - -## SYNTAX - -``` -Set-SPProjectOdataConfiguration [-AcceptCountRequests <Boolean>] [-AcceptProjectionRequests <Boolean>] - [-AssignmentCollection <SPAssignmentCollection>] [-ClearEntityPageSizeOverrides] [-DefaultMaxPageSize <Int32>] - [-EntitySetName <String>] [-MaxResultsPerCollection <Int32>] [-PageSizeOverride <Int32>] - [-UseVerboseErrors <Boolean>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProjectOdataConfiguration` cmdlet sets the settings for how the OData service is configured for an instance of Project Web App. -It allows the user to configure the settings for a list of parameters that specify paging, the enabling of various querying functionality, whether MaxResultsPerCollection has been enabled and whether verbose errors are enabled. -Paging can be specified per entity. -If no paging overrides exist for a given entity, the DefaultMaxPageSize parameter is used. -MaxResultsPerCollection cannot be used in conjunction with paging. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ----------------------EXAMPLE 1----------------------- -``` -Set-SPProjectOdataConfiguration -ClearEntityPageSizeOverrides -``` - -This example clears any page size overrides that have been set for any specific entities. - - -### ----------------------EXAMPLE 2----------------------- -``` -Set-SPProjectOdataConfiguration -AcceptProjectionRequests $true -``` - -This example sets AcceptProjectionRequests to true. - - -### ----------------------EXAMPLE 3----------------------- -``` -Set-SPProjectOdataConfiguration -DefaultMaxPageSize 50 -``` - -This example sets the default maximum page size to 50 rows. - - -### ----------------------EXAMPLE 4----------------------- -``` -Set-SPProjectOdataConfiguration -EntitySetName Assignments -PageSizeOverride 100 -``` - -This example sets the page size override for the Assignments entity. - - -## PARAMETERS - -### -AcceptCountRequests -Sets whether requests with the $count path segment or the $inlinecount query options are accepted. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AcceptProjectionRequests -Sets whether projection requests should be accepted. -Projection requests are made by using the $select query option. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClearEntityPageSizeOverrides -Clears all page-size overrides that had been set for any entities. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultMaxPageSize -Sets the default page size. -This is used for any entities that do not have an override set using the PageSizeOverride parameter. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EntitySetName -Specifies the entity name that is used to set a page size override with PageSizeOverride. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxResultsPerCollection -Sets the integer value that indicates the maximum number of results per entity. -This parameter cannot be used in conjunction with paging. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PageSizeOverride -Overrides the page size that is used for a specific entity. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseVerboseErrors -Sets the service to use more verbose error messages (for example, stack trace). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectPCSSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectPCSSettings.md deleted file mode 100644 index e1b6459d03..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectPCSSettings.md +++ /dev/null @@ -1,239 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectpcssettings -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectPCSSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectPCSSettings - -## SYNOPSIS -Sets the settings for the Project Calculation Engine on Project Server. - -## SYNTAX - -``` -Set-SPProjectPCSSettings [-ServiceApplication <PsiServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-CachePersistence <Int32>] [-EditingSessionTimeout <Int32>] - [-MaximumIdleWorkersCount <Int32>] [-MaximumProjectSize <Int32>] [-MaximumSessionsPerUser <Int32>] - [-MaximumWorkersCount <Int32>] [-MinimumMemoryRequired <Int32>] [-RequestTimeLimits <Int32>] - [-NetTcpPort <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProjectPCSSettings` cmdlet lets you configure the different settings that govern the operations of the Project Calculation Engine on Project Server. -The settings are per service application, which is identified by the Service Application parameter provided to this cmdlet. -The settings have maximum and minimum values that are enforced by Project Server. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Set-SPProjectPCSSettings -sa "Project Service Application" -MaximumSessionsPerUser 500 -``` - -This example sets 500 as the maximum allowed Project Calculation Engine sessions that a user can open on the "Project Service Application" service application. - - -## PARAMETERS - -### -ServiceApplication -The Project Server service application for which the settings are to be read. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CachePersistence -The maximum length of time before the Project Calculation Engine can begin to remove temporary cache files of projects opened on the Project Server service application. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EditingSessionTimeout -The maximum length of time that a user can be idle in a Project Calculation Engine session before a timeout occurs. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumIdleWorkersCount -The maximum number of idle Project Calculation Engine sessions available at a given time. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumProjectSize -The maximum size of a project that can be opened by the Project Calculation Engine. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumSessionsPerUser -The maximum number of sessions that a user is allowed to open. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumWorkersCount -The maximum number of Project Calculation Engine sessions that can be created. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MinimumMemoryRequired -The minimum memory required before launching a new Project Calculation Engine session. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestTimeLimits -The maximum allowable time for a request to the Project Calculation Engine to complete before the Project Calculation Engine session is terminated. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetTcpPort -The TCP port to use with the PCS service. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectPermissionMode.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectPermissionMode.md deleted file mode 100644 index 132183623a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectPermissionMode.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectpermissionmode -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectPermissionMode -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectPermissionMode - -## SYNOPSIS -Changes the permission mode for a Project Web App instance. -Running this cmdlet deletes all security settings and reverts to the default settings for the specified mode. - -## SYNTAX - -``` -Set-SPProjectPermissionMode [-Url] <Uri> [-Mode] <PermissionMode> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProjectPermissionMode` cmdlet changes the permission mode for the specified Project Web App instance. - -Switching security modes deletes all permissions configuration information for the specified Project Web App instance and reverts to the default settings for the specified mode. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------EXAMPLE 1------------------- -``` -Set-SPPRojectPermissionMode -Url https://AppServer/pwa -Mode ProjectServer -``` - -This example shows the syntax for transitioning a server into Project Server permission mode. - - -### --------------EXAMPLE 2------------------- -``` -Set-SPPRojectPermissionMode -Url https://AppServer/pwa -Mode SharePoint -``` - -This example shows the syntax for transitioning a server into SharePoint permission mode. - - -## PARAMETERS - -### -Url -Specifies the URL of the Project Web App instance for which the permission mode is to be changed. - -The type must be a valid URL, in the form https://\<ServerName\>/\<PWAName\>. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Mode -Specifies the mode into which the instance should be changed. - -The type must be a valid permission mode, in the form SharePoint or ProjectServer. - -```yaml -Type: PermissionMode -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPProjectPermissionMode](Get-SPProjectPermissionMode.md) - -[Invoke-SPProjectActiveDirectoryGroupSync](Invoke-SPProjectActiveDirectoryGroupSync.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectQueueSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectQueueSettings.md deleted file mode 100644 index 7f465abe6b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectQueueSettings.md +++ /dev/null @@ -1,328 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectqueuesettings -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectQueueSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectQueueSettings - -## SYNOPSIS -Sets the value of one or multiple Project Server Queue settings for a specific Project Server service application. - -## SYNTAX - -``` -Set-SPProjectQueueSettings [-ServiceApplication <PsiServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-CleanupNonSuccessAgeLimit <Int32>] - [-CleanupSuccessAgeLimit <Int32>] [-MaxConnections <Int32>] [-MaxDegreeOfConcurrency <Int32>] - [-MsgRetryInterval <Int32>] [-MsgRetryLimit <Int32>] [-PeriodicTasksInterval <Int32>] [-QueueTimeout <Int32>] - [-SqlCommandTimeout <Int32>] [-SqlRetryInterval <Int32>] [-SqlRetryLimit <Int32>] [-NetTcpPort <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -Sets the value of one or multiple Project Server Queue settings for a specific Project Server service application. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Set-SPProjectQueueSettings -ServiceApplication "Project Service Application" -MaxDegreeOfConcurrency 6 -``` - -This example sets a maximum of 6 for the number of jobs that can be processed at one time by the specified service application. - - -## PARAMETERS - -### -ServiceApplication -Specifies the Project Server service application to target. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Project Server service application (for example, ProjectServiceApp1); or an instance of a valid PsiServiceApplication object. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: sa -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CleanupNonSuccessAgeLimit -This setting determines the age threshold at which any job in a completed, non-successful state (example: Failed But Not Blocking Correlation) can be purged when the Queue Cleanup job runs. -The age of each job is determined by the completed date and time. -For example, if a job was cancelled at 2/1/2007 10:41 p.m. -and the Queue Cleanup job runs at 2/2/2007 11:55 p.m., then the job will not be purged (assuming the Cleanup Age Limit For Non-successful Jobs was 7 days). -Because the number of completed, non-successful jobs is usually not high, the Cleanup Age Limit For Non-successful Jobs setting is usually set to a high value of 168 (7 days). - -Minimum: 1;Maximum: 100000;Default: 168 (7 days) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CleanupSuccessAgeLimit -This setting determines the age threshold at which successful jobs can be purged when the Queue Cleanup job runs. -The age of each job is determined by the completed date and time. -For example, if a job succeeded at 2/1/2007 10:41 p.m. -and the Queue Cleanup job runs at 2/2/2007 11:55 p.m., then the job will be purged (assuming the Cleanup Age Limit For Successful Jobs was 1 day). -Since the number of successful jobs is usually high, the Cleanup Age Limit For Successful Jobs setting is usually set to a low value of 24 (1 day). - -Minimum: 1;Maximum: 100000;Default: 24 (1 day) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxConnections -Maximum number of Queue connections allowed to be pending dispatch on the server. - -Default: 10 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxDegreeOfConcurrency -The Queue is multi-threaded, which enables multiple jobs to be processed at the same time. -This setting limits the degree of concurrency of the queue. -Note that this setting is per Project Server service application. - -Minimum: 1;Maximum: 10;Default: 4 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MsgRetryInterval -If job processing fails due to transient issues (like a SQL Deadlock), instead of failing the job, the Queue will wait for the Retry Interval to elapse and retry the job. - -Minimum: 0 (immediately retry);Maximum: 300000 (5 minutes);Default: 1000 (1 second) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MsgRetryLimit -If job processing fails due to transient issues (like a SQL Deadlock), instead of failing the job, the Queue will retry the job. -The number of retries is bound by the Retry Limit. - -Minimum: 0 (no retries);Maximum: 100;Default: 5 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PeriodicTasksInterval -There are a number of bookkeeping tasks executed by the Queue System. -Some examples are awakening jobs in 'Sleeping' state, updating the heartbeat timestamp, checking whether Queue Cleanup needs to be executed and so on. -This setting controls the time interval at which these tasks run. - -Minimum: 500 (1/2 second);Maximum: 300000 (5 minutes);Default: 10000 (10 second) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueueTimeout -The Queue System has a failover recovery feature. -If the farm contains multiple servers running the Project Server Application Service and the Queue Service fails on one server, jobs are automatically redistributed to other servers on which the Queue Service is online. -A Queue Service is considered to have timed out if it cannot be accessed from the Queue health timer job for more than the 'Queue Timeout' interval. - -Minimum: 5 minutes;Maximum: 60 minutes;Default: 15 minutes - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SqlCommandTimeout -The Queue makes SQL calls for retrieving and executing jobs. -This setting controls the timeout value for all such calls. -If any job fails due to a SQL Timeout error, administrators can increase this setting and retry the job. - -Minimum: 30 seconds;Maximum: 86400 (1 day);Default: 1800 (30 minutes) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SqlRetryInterval -If the Queue fails to connect to a Project Web App database due to a transient SQL problem (like a SQL Deadlock), the Queue will wait for the SQL Retry Interval to elapse and retry the query. - -Minimum: 0 (immediately retry);Maximum: 60000 (1 minute);Default: 1000 (1 second) - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SqlRetryLimit -If the Queue fails to connect to a Project Web App database due to a transient SQL problem (like a SQL Deadlock), the Queue will retry the query after the SQL Retry Interval has elapsed. -The number of retries is bound by the SQL Retry Limit. - -Minimum: 0 (no retries)Maximum: 100Default: 5 - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetTcpPort -Sets the TCP port the Project Queue service uses. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectServiceApplication.md deleted file mode 100644 index c18957a7ce..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectServiceApplication.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectserviceapplication -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectServiceApplication - -## SYNOPSIS -Sets the properties of a Project Server Service application. - -## SYNTAX - -``` -Set-SPProjectServiceApplication [-Identity] <PsiServiceApplicationPipeBind> - [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProjectServiceApplication` cmdlet sets the properties of a Project Server Service application. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set- SPProjectServiceApplication -Identity PSIServiceApp -ApplicationPool newapppool RegisterTimerJob -``` - -This example updates the application pool and re-registers the timer job for a Project Server Service application. - - -## PARAMETERS - -### -Identity -Specifies the Project Server Service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Project Server service application (for example, ProjectWebApp1); or an instance of a valid PsiServiceApplication object. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing IIS application pool to run the web service in for the service application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSync.md deleted file mode 100644 index 76f1ae1270..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSync.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectusersync -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectUserSync -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectUserSync - -## SYNOPSIS -Controls the behavior of WSS user sync. - -## SYNTAX - -``` -Set-SPProjectUserSync [-Url] <Uri> [-Value] <UserSyncParameterValues[]> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -WSS User sync synchronizes Project Server permissions with SharePoint Server permissions. -When users are granted permissions to Project Server entities, permissions are granted to the Project Web App site and the connected SharePoint sites. -By using this cmdlet, administrators can control the behavior of WSS User sync. -They can choose to disable WSS User sync, enable it only for the Project Web App site, enable it only for connected SharePoint sites, or enable for both. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Set-SPProjectUserSync https://localhost/pwa EnablePWA -``` - -In this example, WSS User sync is enabled for the Project Web App site at https://localhost/pwa. - - -## PARAMETERS - -### -Url -Specifies the URL of the Project Web App instance to set the Project User Sync settings. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Value -Disabled completely disables WSS User Sync; EnablePWA enables WSS User sync for the Project Web App site; EnableEntProj enables WSS User sync for all SharePoint sites connected to Enterprise Projects; EnableSPProj enables WSS User sync for all SharePoint sites connected to SharePoint Projects; EnableAll enables WSS User sync for the Project Web App site and all connected SharePoint sites. - -```yaml -Type: UserSyncParameterValues[] -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPProjectUserSyncDisabledSyncThreshold](Set-SPProjectUserSyncDisabledSyncThreshold.md) - -[Set-SPProjectUserSyncFullSyncThreshold](Set-SPProjectUserSyncFullSyncThreshold.md) - -[Set-SPProjectUserSyncOffPeakSyncThreshold](Set-SPProjectUserSyncOffPeakSyncThreshold.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncDisabledSyncThreshold.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncDisabledSyncThreshold.md deleted file mode 100644 index 59ac770ad4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncDisabledSyncThreshold.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectusersyncdisabledsyncthreshold -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectUserSyncDisabledSyncThreshold -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectUserSyncDisabledSyncThreshold - -## SYNOPSIS -Defines the threshold over which a user sync job will not be executed but instead will be deleted. -This threshold is the product of the number of projects multiplied by the number of users. - -## SYNTAX - -``` -Set-SPProjectUserSyncDisabledSyncThreshold [-Url] <Uri> [-Threshold] <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProjectUserSyncDisabledSyncThreshold` cmdlet d the threshold over which a user sync job will not be executed but instead will be deleted. -This threshold is the product of the number of projects multiplied by the number of users. -The purpose of configuring this threshold is to prevent malicious user syncs of the whole server. -Set it to a negative value to reset to default value (not set). - -This cmdlet only works in Project Server Permission mode. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPProjectUserSyncDisabledSyncThreshold -URL http//contoso-AppSrv/PWA -Threshold 400 -``` - -This example sets the sync disable threshold for the Project Web App instance at http//contoso-AppSrv/PWA to 400. - - -## PARAMETERS - -### -Url -The URL of the Project Web App instance where you want to set the threshold. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -A whole number consisting of the number of projects multiplied by the number of users. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPProjectUserSync](Set-SPProjectUserSync.md) - -[Set-SPProjectUserSyncFullSyncThreshold](Set-SPProjectUserSyncFullSyncThreshold.md) - -[Set-SPProjectUserSyncOffPeakSyncThreshold](Set-SPProjectUserSyncOffPeakSyncThreshold.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncFullSyncThreshold.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncFullSyncThreshold.md deleted file mode 100644 index e4115300a4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncFullSyncThreshold.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectusersyncfullsyncthreshold -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectUserSyncFullSyncThreshold -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectUserSyncFullSyncThreshold - -## SYNOPSIS -Defines the threshold over which a delta user sync job will be executed as a complete user sync. -This threshold is the product of the number of projects multiplied by the number of users. - -## SYNTAX - -``` -Set-SPProjectUserSyncFullSyncThreshold [-Url] <Uri> [-Threshold] <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProjectUserSyncFullSyncThreshold` cmdlet defines the threshold over which a delta user sync job will be executed as a complete user sync. -This threshold is the product of the number of projects multiplied by the number of users. -The purpose of this threshold is to use the full sync method instead of the delta sync method when the amount of changes is large enough. -Set it to a negative value to reset to the default (not set). - -This cmdlet only works in Project Server Permission mode. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPProjectUserSyncFullSyncThreshold -URL https://contoso-AppSrv/ -Threshold 800 -``` - -This example sets the full user sync threshold for the Project Web App instance at https://contoso-AppSrv/PWA to 800. - - -## PARAMETERS - -### -Url -The URL of the Project Web App instance where you want to set the threshold. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -A whole number consisting of the number of projects multiplied by the number of users. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPProjectUserSync](Set-SPProjectUserSync.md) - -[Set-SPProjectUserSyncDisabledSyncThreshold](Set-SPProjectUserSyncDisabledSyncThreshold.md) - -[Set-SPProjectUserSyncOffPeakSyncThreshold](Set-SPProjectUserSyncOffPeakSyncThreshold.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncOffPeakSyncThreshold.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncOffPeakSyncThreshold.md deleted file mode 100644 index 75fa47379a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectUserSyncOffPeakSyncThreshold.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spprojectusersyncoffpeaksyncthreshold -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Set-SPProjectUserSyncOffPeakSyncThreshold -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPProjectUserSyncOffPeakSyncThreshold - -## SYNOPSIS -Defines the threshold over which a full user sync job will be executed during off peak hours instead of immediately. -This threshold is the product of the number of projects multiplied by the number of users. - -## SYNTAX - -``` -Set-SPProjectUserSyncOffPeakSyncThreshold [-Url] <Uri> [-Threshold] <Int32> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPProjectUserSyncOffPeakSyncThreshold` cmdlet defines the threshold over which a full user sync job will be executed during off-peak hours instead of immediately. -This threshold is the product of the number of projects multiplied by the number of users. -This threshold is used to preserve server performance. -Set it to a negative value to reset to the default of no threshold configured. - -This cmdlet only works in Project Server Permission mode. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPProjectUserSyncOffPeakSyncThreshold -URL https://contoso/PWA -Threshold 900000 -``` - -This example sets the sync off-peak threshold for the Project Web App instance at https://contoso-AppSrv/PWA to 900000. - - -## PARAMETERS - -### -Url -The URL of the Project Web App instance where you want to set the threshold. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -A whole number consisting of the number of projects multiplied by the number of users. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPProjectUserSync](Set-SPProjectUserSync.md) - -[Set-SPProjectUserSyncDisabledSyncThreshold](Set-SPProjectUserSyncDisabledSyncThreshold.md) - -[Set-SPProjectUserSyncFullSyncThreshold](Set-SPProjectUserSyncFullSyncThreshold.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRequestManagementSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRequestManagementSettings.md deleted file mode 100644 index 5f60431671..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRequestManagementSettings.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sprequestmanagementsettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPRequestManagementSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPRequestManagementSettings - -## SYNOPSIS -Sets Request Manager properties. - - -## SYNTAX - -``` -Set-SPRequestManagementSettings [-Identity] <SPRequestManagementSettingsPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-RoutingEnabled] [-RoutingScheme <SPRoutingScheme>] - [-ThrottlingEnabled] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPRequestManagementSettings` cmdlet to set properties for the Request Manager. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$wa = Get-SPWebApplication https://webAppUrl -$req = $wa | Get-SPRequestManagementSettings -Set-SPRequestManagementSettings -Identity $req -ThrottlingEnabled:$false -``` - -This example disables throttling on the specified Web Application. - -## PARAMETERS - -### -Identity -Specifies the Request Manager object for which settings will be applied. - -```yaml -Type: SPRequestManagementSettingsPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RoutingEnabled -Specifies whether routing is enabled or disabled for the Request Manager object. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoutingScheme -Specifies the routing scheme. - -The value is one of the following: - ---Default- Performs random selection. ---StaticMachineWeight- Uses Static weight of target. ---HealthBased- Considers health score of machine. - -```yaml -Type: SPRoutingScheme -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ThrottlingEnabled -Specifies whether throttling is enabled or disabled for the Request Manager object. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPRequestManagementSettings](Get-SPRequestManagementSettings.md) - -[New-SPRequestManagementRuleCriteria](New-SPRequestManagementRuleCriteria.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingMachineInfo.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingMachineInfo.md deleted file mode 100644 index 58761dd036..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingMachineInfo.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sproutingmachineinfo -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPRoutingMachineInfo -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPRoutingMachineInfo - -## SYNOPSIS -Sets routing target properties. - - -## SYNTAX - -``` -Set-SPRoutingMachineInfo [-Identity] <SPRoutingMachineInfoPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Availability <SPRoutingMachineAvailability>] - [-ClearOutgoingPort] [-OutgoingPort <Int32>] [-OutgoingScheme <SPRoutingOutgoingScheme>] - [-StaticWeight <Double>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPRoutingMachineInfo` cmdlet to set routing target properties by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$wa = Get-SPWebApplication -Identity https://webAppUrl -$rm = Get-SPRequestManagementSettings -Identity $wa -$m = Get-SPRoutingMachineInfo -RequestManagementSettings $rm -Name SP01 -Set-SPRoutingMachineInfo -Identity $m -Availability Unavailable -``` - -This example sets the "Availability" routing target property to Unavailable for a specified identity. - -## PARAMETERS - -### -Identity -Specifies the name of the request management settings object to set. - -```yaml -Type: SPRoutingMachineInfoPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Availability -Specifies whether or not the specified computer will be available for routing. - -The valid values are: - ---Available ---Unavailable - -```yaml -Type: SPRoutingMachineAvailability -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClearOutgoingPort -Clears the outgoing port if it is set. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutgoingPort -Specifies the port used by Request Manager to make an outgoing connection. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutgoingScheme -Determines the schema of outgoing connections. - -The valid values are: - ---SameAsIncoming ---Http ---Https - -```yaml -Type: SPRoutingOutgoingScheme -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StaticWeight -Specifies whether the static weight of a computer routing is used by Request Manager. -If the static weight is higher, more requests will be routed to the computer. - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingMachineInfo](Add-SPRoutingMachineInfo.md) - -[Get-SPRoutingMachineInfo](Get-SPRoutingMachineInfo.md) - -[Remove-SPRoutingMachineInfo](Remove-SPRoutingMachineInfo.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingMachinePool.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingMachinePool.md deleted file mode 100644 index 12dfacd444..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingMachinePool.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sproutingmachinepool -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPRoutingMachinePool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPRoutingMachinePool - -## SYNOPSIS -Sets properties of a machine pool. - - -## SYNTAX - -``` -Set-SPRoutingMachinePool [-Identity] <SPRoutingMachinePoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-MachineTargets <SPRoutingRuleTargetPipeBind[]>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPRoutingMachinePool` cmdlet to set properties of a machine pool by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$wa = Get-SPWebApplication -Identity https://webAppUrl -$rm = Get-SPRequestManagementSettings -Identity $wa -$pool = Get-SPRoutingMachinePool -RequestManagementSettings $rm -Name 'MachinePool' -$newMachine = Get-SPRoutingMachineInfo -RequestManagementSettings $rm -Name SP01 -Set-SPRoutingMachinePool -Identity $pool -MachineTargets ($pool.MachineTargets + $newMachine) -``` -This example sets the routing machine pool on the specified Web Application. Using the Request Management settings of the Web Application, it retrieves the existing routing machine pool named 'MachinePool'. It then gets the routing machine info for a new machine to add to the pool. Lastly, it sets the pool with the existing machine targets plus the new machine target. - -## PARAMETERS - -### -Identity -Specifies the name of the request management settings object to set. - -```yaml -Type: SPRoutingMachinePoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MachineTargets -Specifies the routing targets collection that the machine pool will contain. - -```yaml -Type: SPRoutingRuleTargetPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingMachinePool](Add-SPRoutingMachinePool.md) - -[Get-SPRoutingMachinePool](Get-SPRoutingMachinePool.md) - -[Remove-SPRoutingMachinePool](Remove-SPRoutingMachinePool.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingRule.md deleted file mode 100644 index 22ebc6d795..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPRoutingRule.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sproutingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPRoutingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPRoutingRule - -## SYNOPSIS -Changes properties of an existing routing rule. - - -## SYNTAX - -``` -Set-SPRoutingRule [-Identity] <SPRoutingRulePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Criteria <SPRequestManagementRuleCriteriaPipeBind[]>] [-ExecutionGroup <Int32>] [-Expiration <DateTime>] - [-MachinePool <SPRoutingMachinePoolPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPRoutingRule` cmdlet to change properties of an existing routing rule. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$wa = Get-SPWebApplication https://webAppUrl -$rm = Get-SPRequestManagementSettings -Identity $wa -Get-SPRoutingRule -RequestManagementSettings $rm -$machines = Get-SPRoutingMachineInfo -RequestManagementSettings $rm -$pool = Add-SPRoutingMachinePool -RequestManagementSettings $rm -Name <Name of Pool> -MachineTargets $machines -$criteria = New-SPRequestManagementRuleCriteria -Value http -Property url -MatchType startswith -CaseSensitive $false -$rule = Add-SPRoutingRule -RequestManagementSettings $rm -Name <Rule Name> -Criteria $c -MachinePool $pool -$criteriaNew = New-SPRequestManagementRuleCriteria -Property UserAgent -MatchType Equals -Value "Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 6.0 Robot)" -Set-SPRoutingRule -Identity $rule -Criteria $criteriaNew -``` - -This example sets a routing rule for the specified identity by using the $rule variable. - - -## PARAMETERS - -### -Identity -Specifies the name of the request management settings object to set. - -```yaml -Type: SPRoutingRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Criteria -Specifies the criteria for the rule to match. - -```yaml -Type: SPRequestManagementRuleCriteriaPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExecutionGroup -Specifies the group in which the rule will be placed. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expiration -Specifies the expiration date and time of the rule. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MachinePool -Specifies the pool of machines to which a request will be routed if the changed rule is matched. - -```yaml -Type: SPRoutingMachinePoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPRoutingRule](Add-SPRoutingRule.md) - -[Get-SPRoutingRule](Get-SPRoutingRule.md) - -[Remove-SPRoutingRule](Remove-SPRoutingRule.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPScaleOutDatabaseDataRange.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPScaleOutDatabaseDataRange.md deleted file mode 100644 index 493ccfc2a6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPScaleOutDatabaseDataRange.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spscaleoutdatabasedatarange -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPScaleOutDatabaseDataRange -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPScaleOutDatabaseDataRange - -## SYNOPSIS -Extends the range of a specified scale-out database. - - -## SYNTAX - -``` -Set-SPScaleOutDatabaseDataRange -Database <SPDatabasePipeBind> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-NewRangePoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPScaleOutDatabaseDataRange` cmdlet to extend the range of a specified scale-out database towards a specified direction. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -C:\PS>$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication - -C:\PS>$database = $databases[0] - -C:\PS>$state = Get-SPScaleOutDatabaseDataState -Database $database - -Set-SPScaleOutDatabaseDataRange -Database $database -Range $state.Range -NewRangePoint $null -IsUpperSubRange $true -``` - -This example extends the data range end point of the first database in the specified service application up to the maximum range point. - - -## PARAMETERS - -### -Database -Specifies the scale-out database to which to extend the data range. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsUpperSubRange -Specifies whether to set the start or the end point of the data range with the specified value in the NewRangePoint parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Range -Specifies the expected data range of the scale-out database. - -```yaml -Type: SPScaleOutDataRange -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewRangePoint -Specifies the new start or end point of the database. - -The maximum value is NULL. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-SPScaleOutDatabaseDataSubRange](Set-SPScaleOutDatabaseDataSubRange.md) - -[Get-SPScaleOutDatabase](Get-SPScaleOutDatabase.md) - -[Get-SPScaleOutDatabaseDataState](Get-SPScaleOutDatabaseDataState.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPScaleOutDatabaseDataSubRange.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPScaleOutDatabaseDataSubRange.md deleted file mode 100644 index b305ed2fbe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPScaleOutDatabaseDataSubRange.md +++ /dev/null @@ -1,269 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spscaleoutdatabasedatasubrange -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPScaleOutDatabaseDataSubRange -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPScaleOutDatabaseDataSubRange - -## SYNOPSIS -Creates a subrange for a specified scale-out database. - - -## SYNTAX - -### UnattachedDatabase -``` -Set-SPScaleOutDatabaseDataSubRange -ConnectionString <String> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> -SubRangeMode <SPScaleOutDatabaseSubRangeMode> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-IgnoreSubRangePointOnBoundary] - [-IsAzureDatabase] [-SubRangePoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -### AttachedDatabase -``` -Set-SPScaleOutDatabaseDataSubRange -Database <SPDatabasePipeBind> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> -SubRangeMode <SPScaleOutDatabaseSubRangeMode> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-IgnoreSubRangePointOnBoundary] - [-SubRangePoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPScaleOutDatabaseDataSubRange` cmdlet to create a subrange with the specified parameters for a specified scale-out database or a database which will be connected with a specified connection string. -A subrange is a subset of a range of data. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -C:\PS>$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication - -C:\PS>$database = $databases[0] - -C:\PS>$state = Get-SPScaleOutDatabaseDataState -Database $database - -Set-SPScaleOutDatabaseDataSubRange -Database $database -Range $state.Range -SubRangePoint $state.Range.RangeEnd -SubRangeMode ReadOnly -IsUpperSubRange $false -``` - -This example creates a read-only subrange that starts from the data range start point and ends at the data range end point on the first scale-out database of the specified service application. - - -## PARAMETERS - -### -ConnectionString -Specifies the connection string for the scale-out database to create the new data sub-range. - -```yaml -Type: String -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -Specifies the scale-out database to create the data subrange. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: AttachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsUpperSubRange -Specifies whether to create the data subrange on the upper or lower side of the data range. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Range -Specifies the expected current range of the scale-out database prior to this operation. - -```yaml -Type: SPScaleOutDataRange -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubRangeMode -Specifies the mode of the data subrange to be created. -The data subrange mode values are the following: - ---NULL- The data subrange on the specified side (lower or upper) of the data range will be removed. ---ReadOnly - The partitions which are inside the new data subrange can be read, but cannot be modified. ---Changing -The partitions which are inside the new data subrange cannot be read or modified ---Deleted- The partitions which are inside the new data subrange cannot be read or modified - -```yaml -Type: SPScaleOutDatabaseSubRangeMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreSubRangePointOnBoundary -Specifies whether to complete without any errors if the new subrange's start and end points are the same. -If this parameter is specified, no errors are displayed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsAzureDatabase -Specifies whether the database is hosted on SQL Azure. - -```yaml -Type: SwitchParameter -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubRangePoint -Specifies the start or end point of the data subrange to be created as defined by the following criteria: - ---The start point if the data sub-range is created on the upper side of the data range. ---The end point if the data sub-range is created on the lower side of the data range. - -The maximum value is NULL. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Clear-SPScaleOutDatabaseDeletedDataSubRange](Clear-SPScaleOutDatabaseDeletedDataSubRange.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreApplication.md deleted file mode 100644 index a875e3a3dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreApplication.md +++ /dev/null @@ -1,210 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsecurestoreapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSecureStoreApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSecureStoreApplication - -## SYNOPSIS -Sets properties of a Secure Store application. - - -## SYNTAX - -``` -Set-SPSecureStoreApplication -Identity <SPSecureStoreApplication> [-Administrator <SPClaim[]>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-CredentialsOwnerGroup <SPClaim[]>] - [-Fields <TargetApplicationField[]>] [-TargetApplication <TargetApplication>] [-TicketRedeemer <SPClaim[]>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPSecureStoreApplication` cmdlet sets properties of a Secure Store application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$targetApp.FriendlyName = "Updated Contoso Target App" - -Set-SPSecureStoreApplication -Identity $application -TargetApplication $targetApp -``` - -This example sets a new display name Updated Contoso Target App for the target application. - - -## PARAMETERS - -### -Identity -Specifies the Secure Store application to update. - -```yaml -Type: SPSecureStoreApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Administrator -Specifies the administrator of the Secure Store application. - -```yaml -Type: SPClaim[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CredentialsOwnerGroup -Specifies the claims object for the groups that own the group credentials. - -```yaml -Type: SPClaim[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Fields -Specifies the field information for the application. -The default fields are username and password. - -```yaml -Type: TargetApplicationField[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetApplication -Specifies the target application. - -```yaml -Type: TargetApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TicketRedeemer -Specifies the ticket redeemer claim value. - -```yaml -Type: SPClaim[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreDefaultProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreDefaultProvider.md deleted file mode 100644 index 8894f8ea7a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreDefaultProvider.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsecurestoredefaultprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSecureStoreDefaultProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSecureStoreDefaultProvider - -## SYNOPSIS -Updates the secure store provider. - - -## SYNTAX - -``` -Set-SPSecureStoreDefaultProvider -Type <Type> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPSecureStoreDefaultProvider` cmdlet sets or replaces the secure store provider. -To register a third-party secure store, implement the ISecureStoreProvider interface. -With the interface defined, place the DLL file in the global assembly cache, and then load the DLL and load the type, as shown in the example. -You can then set the secure store provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>[Reflection.Assembly]::LoadFrom("C:\ContosoFolder\contosoSecureStore.dll") - -C:\PS>$type = [Contoso.SecureStore.ContosoSecureStoreProvider] - -Set-SPSecureStoreDefaultProvider -Type $type -``` - -This example sets the custom implemented secure store provider. - - -## PARAMETERS - -### -Type -The type must be a secure store provider type enclosed in square brackets; for example, \[Reflection.Assembly\]. - -```yaml -Type: Type -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreServiceApplication.md deleted file mode 100644 index 6f9a23add1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecureStoreServiceApplication.md +++ /dev/null @@ -1,292 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsecurestoreserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSecureStoreServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSecureStoreServiceApplication - -## SYNOPSIS -Sets properties of a Secure Store Service application in the farm. - - -## SYNTAX - -``` -Set-SPSecureStoreServiceApplication -Identity <SPServiceApplicationPipeBind> - [-ApplicationPool <SPIisWebServiceApplicationPool>] [-AssignmentCollection <SPAssignmentCollection>] - [-AuditingEnabled] [-AuditlogMaxSize <Int32>] [-Confirm] [-DatabaseCredentials <PSCredential>] - [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] - [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] [-Sharing] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPSecureStoreServiceApplication` cmdlet sets properties of a Secure Store Service application in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Set-SPSecureStoreServiceApplication -Identity $contosoServApp -AuditlogMaxSize 40 -``` - -This example sets the maximum size of the audit log to 40 days for the given service application. - - -## PARAMETERS - -### -Identity -Specifies the service application to update. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing IIS application pool to run the Web service in for the new service application. - -```yaml -Type: SPIisWebServiceApplicationPool -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuditingEnabled -Turns on auditing for the Secure Store Service. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuditlogMaxSize -Specifies the number of days to retain the audit log. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL authentication. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the Secure Store service database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user specified in DatabaseUserName. -Use this parameter only if SQL authentication is used to access the metadata service application database. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user name to use for connecting to the database for the Secure Store service application. -Use this parameter only if SQL authentication is used to access the service application database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host server for the failover database server. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Sharing -Specifies that the Secure Store Service application is published and shared across the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecurityTokenServiceConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecurityTokenServiceConfig.md deleted file mode 100644 index 8e2b1c0a2e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSecurityTokenServiceConfig.md +++ /dev/null @@ -1,453 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsecuritytokenserviceconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSecurityTokenServiceConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSecurityTokenServiceConfig - -## SYNOPSIS -Updates the settings of the SharePoint security token service (STS) identity provider. - - -## SYNTAX - -### QueueSigningCertificateReference -``` -Set-SPSecurityTokenServiceConfig -QueueSigningCertificateThumbprint <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-FormsTokenLifetime <Int32>] - [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] - [-QueueSigningCertificateStoreName <String>] [-ServiceTokenCacheExpirationWindow <Int32>] - [-ServiceTokenLifetime <Int32>] [-WhatIf] [-WindowsTokenLifetime <Int32>] [<CommonParameters>] -``` - -### RevokeSigningCertificateReference -``` -Set-SPSecurityTokenServiceConfig -RevokeSigningCertificateThumbprint <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-FormsTokenLifetime <Int32>] - [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] - [-RevokeSigningCertificateStoreName <String>] [-ServiceTokenCacheExpirationWindow <Int32>] - [-ServiceTokenLifetime <Int32>] [-WhatIf] [-WindowsTokenLifetime <Int32>] [<CommonParameters>] -``` - -### SigningCertificateReference -``` -Set-SPSecurityTokenServiceConfig -SigningCertificateThumbprint <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-FormsTokenLifetime <Int32>] - [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] - [-ServiceTokenCacheExpirationWindow <Int32>] [-ServiceTokenLifetime <Int32>] - [-SigningCertificateStoreName <String>] [-WhatIf] [-WindowsTokenLifetime <Int32>] - [-QueueSigningCertificateThumbprint <String>] [-QueueSigningCertificateStoreName <String>] - [<CommonParameters>] -``` - -### SigningCertificateImport -``` -Set-SPSecurityTokenServiceConfig [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-FormsTokenLifetime <Int32>] [-ImportSigningCertificate <X509Certificate2>] - [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] - [-ServiceTokenCacheExpirationWindow <Int32>] [-ServiceTokenLifetime <Int32>] [-WhatIf] - [-WindowsTokenLifetime <Int32>] [<CommonParameters>] -``` - -### SigningCertificateQueue -``` -Set-SPSecurityTokenServiceConfig [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-FormsTokenLifetime <Int32>] [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] - [-QueueSigningCertificate <X509Certificate2>] [-ServiceTokenCacheExpirationWindow <Int32>] - [-ServiceTokenLifetime <Int32>] [-WhatIf] [-WindowsTokenLifetime <Int32>] [<CommonParameters>] -``` - -### SigningCertificateRevoke -``` -Set-SPSecurityTokenServiceConfig [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-FormsTokenLifetime <Int32>] [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] - [-RevokeSigningCertificate <X509Certificate2>] [-ServiceTokenCacheExpirationWindow <Int32>] - [-ServiceTokenLifetime <Int32>] [-WhatIf] [-WindowsTokenLifetime <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPSecurityTokenServiceConfig` cmdlet updates the settings of the SharePoint security token service (STS) identity provider. -If a certificate file is used, the certificate must be an X509 certificate with private keys, otherwise an exception is raised. - -This cmdlet operates only with certificates that can be exported. -To create a certificate which can be used in this cmdlet specify the X509KeyStorageFlags.Exportable bit in the keyStorageFlags parameter of the x509Certificate2 object constructor. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Set-SPSecurityTokenServiceConfig -SigningCertificateThumbprint "2796BAE63F1801E277261BA0D77770028F20EEE4" -``` - -This example updates the signing certificate of the SharePoint security token service (STS) identity provider with a certificate that has been deployed in the certificate store. - - -### --------------------EXAMPLE 2--------------------- -``` -$stsCert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 "c:\sts.pfx","a",20 -Set-SPSecurityTokenServiceConfig -ImportSigningCertificate $stsCert -``` - -This example imports the signing certificate for the SharePoint STS identity provider. - - -## PARAMETERS - -### -QueueSigningCertificateThumbprint -Sets the certificate with the provided thumbprint as the queued signing certificate. - -```yaml -Type: String -Parameter Sets: QueueSigningCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: SigningCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RevokeSigningCertificateThumbprint -Revoke the signing certificate with the provided thumbprint. - -```yaml -Type: String -Parameter Sets: RevokeSigningCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SigningCertificateThumbprint -Specifies the thumbrpint of the signing certificate. - -The type must be a valid identity of a signing certificate; for example 2796BAE63F1801E277261BA0D77770028F20EEE4. - -```yaml -Type: String -Parameter Sets: SigningCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FormsTokenLifetime -Specifies the expiration time, in minutes, for tokens issued to ASP.NET Membership Provider and Role providers. -The default value is 1380. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImportSigningCertificate -Specifies the X.509 certificate object from trusted authentication provider farm. - -The type must be a name of a valid X.509 certificate; for example, Certificate1. - -```yaml -Type: X509Certificate2 -Parameter Sets: SigningCertificateImport -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxLogonTokenCacheItems -Specifies the maximum number of entries for the in-memory logon token cache. -The default value is 250 entries. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxServiceTokenCacheItems -Specifies the maximum number of entries for the in-memory service token cache. -The default value is 250 entries. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueueSigningCertificate -Sets the provided certificate as the queued signing certificate. - -```yaml -Type: X509Certificate2 -Parameter Sets: SigningCertificateQueue -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueueSigningCertificateStoreName -The store to search in when looking up a certificate to be set as the queued signing certificate by its thumbprint. Required if QueueSigningCertificateThumbprint was specified. - -```yaml -Type: String -Parameter Sets: QueueSigningCertificateReference, SigningCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RevokeSigningCertificate -Revokes the signing certificate that matches the provided certificate. - -```yaml -Type: X509Certificate2 -Parameter Sets: SigningCertificateRevoke -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RevokeSigningCertificateStoreName -The store to search when looking up a certificate to be revoked by its thumbprint. Required if the QueueSigningCertificateThumbprint was specified. - -```yaml -Type: String -Parameter Sets: RevokeSigningCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceTokenCacheExpirationWindow -Specifies the interval, in minutes, for automatically renewing the token in the cache. -The default value is 2 minutes. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceTokenLifetime -Specifies the expiration time, in minutes, for the security token service cache. -The default value is 15 minutes. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SigningCertificateStoreName -Specifies the certificate store where the signing certificate resides. -The identity store for an identity provider can be a SQL database table, an Active Directory Domain Services (AD DS), or Active Directory Lightweight Directory Service (AD LDS). - -The type must be a valid identity of a signing certificate store; for example IdentityStore1. - -```yaml -Type: String -Parameter Sets: SigningCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WindowsTokenLifetime -Specifies the expiration time, in minutes, for tokens issued to Windows users. -The default value is 1380 minutes. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServer.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServer.md deleted file mode 100644 index a3d892a5dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServer.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spserver -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServer - -## SYNOPSIS -Changes the role of the server. - - -## SYNTAX - -``` -Set-SPServer [-Identity] <SPServerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Role <SPServerRole>] [-Status <SPObjectStatus>] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-SPServer cmdlet changes the role of the server in the farm by using the Role parameter. A new cmdlet in SharePoint Server 2016, SharePoint Server 2019 that is used in MinRole. - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPServer -Role SingleServerFarm -``` - -This example changes the server to SingleServerFarm role. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -Specifies the name of the server in the farm. - -```yaml -Type: SPServerPipeBind -Parameter Sets: (All) -Aliases: Address -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Role -Specifies the name of the server role you want to change. - -The valid values are: - -* WebFrontEnd -* Application -* SingleServerFarm -* Distributed Cache -* Search -* Custom -* ApplicationWithSearch -* WebFrontEndWithDistributedCache - - -```yaml -Type: SPServerRole -Parameter Sets: (All) -Aliases: -Accepted values: Application, ApplicationWithSearch, Custom, DistributedCache, Search, SingleServerFarm, WebFrontEnd, WebFrontEndWithDistributedCache -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Status -Sets the status of the server in the farm. - -```yaml -Type: SPObjectStatus -Parameter Sets: (All) -Aliases: -Accepted values: Online, Disabled, Offline, Unprovisioning, Provisioning, Upgrading, Patching -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServerPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServerScaleOutDatabaseDataRange.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServerScaleOutDatabaseDataRange.md deleted file mode 100644 index 45bc4ac4e0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServerScaleOutDatabaseDataRange.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spserverscaleoutdatabasedatarange -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServerScaleOutDatabaseDataRange -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServerScaleOutDatabaseDataRange - -## SYNOPSIS -Extends the range of a specified scale-out database. - - -## SYNTAX - -``` -Set-SPServerScaleOutDatabaseDataRange -Database <SPDatabasePipeBind> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-NewRangePoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPServerScaleOutDatabaseDataRange cmdlet to extend the range of a specified scale-out database in a specified direction. - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -$state = Get-SPServerScaleOutDatabaseDataState -Database $database -Set-SPServerScaleOutDatabaseDataRange -Database $database -Range $state.Range -NewRangePoint $null -IsUpperSubRange $true -``` - -This example extends the data range end point of the first database in the specified service application up to the maximum range point. - - -## PARAMETERS - -### -Database -Specifies the scale-out database to which to extend the data range. - - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsUpperSubRange -Specifies whether to set the start point or the end point of the data range with the specified value in the NewRangePoint parameter. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Range -Specifies the expected data range of the scale-out database. - - -```yaml -Type: SPScaleOutDataRange -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -Note: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewRangePoint -Specifies the new start point or end point of the database. -The maximum value is NULL. - -``yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-SPServerScaleOutDatabaseDataSubRange](Set-SPServerScaleOutDatabaseDataSubRange.md) - -[Clear-SPServerScaleOutDatabaseDeletedDataSubRange](Clear-SPServerScaleOutDatabaseDeletedDataSubRange.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServerScaleOutDatabaseDataSubRange.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServerScaleOutDatabaseDataSubRange.md deleted file mode 100644 index cb5b2bc3af..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServerScaleOutDatabaseDataSubRange.md +++ /dev/null @@ -1,268 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spserverscaleoutdatabasedatasubrange -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServerScaleOutDatabaseDataSubRange -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServerScaleOutDatabaseDataSubRange - -## SYNOPSIS -Creates a subrange for a specified scale-out database. - - -## SYNTAX - -### UnattachedDatabase -``` -Set-SPServerScaleOutDatabaseDataSubRange -ConnectionString <String> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> -SubRangeMode <SPScaleOutDatabaseSubRangeMode> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-IgnoreSubRangePointOnBoundary] - [-IsAzureDatabase] [-SubRangePoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -### AttachedDatabase -``` -Set-SPServerScaleOutDatabaseDataSubRange -Database <SPDatabasePipeBind> -IsUpperSubRange <Boolean> - -Range <SPScaleOutDataRange> -SubRangeMode <SPScaleOutDatabaseSubRangeMode> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-IgnoreSubRangePointOnBoundary] - [-SubRangePoint <Byte[]>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [Cmdlet Parameter Sets] (https://msdn.microsoft.com/library/dd878348(VS.85).aspx). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -$state = Get-SPServerScaleOutDatabaseDataState -Database $database -Set-SPServerScaleOutDatabaseDataSubRange -Database $database -Range $state.Range -SubRangePoint $state.Range.RangeEnd -SubRangeMode ReadOnly -IsUpperSubRange $false - -``` - -This example creates a read-only subrange that starts from the data range start point and ends at the data range end point on the first scale-out database of the specified service application. - - -## PARAMETERS - -### -ConnectionString -Specifies the connection string for the scale-out database to create the new data sub-range. - - -```yaml -Type: String -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Database -Specifies the scale-out database to create the data subrange. - - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: AttachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IsUpperSubRange -Specifies whether to create the data subrange on the upper or lower side of the data range. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Range -Specifies the expected current range of the scale-out database prior to this operation. - - -```yaml -Type: SPScaleOutDataRange -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubRangeMode - - - - -```yaml -Type: SPScaleOutDatabaseSubRangeMode -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -Note: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IgnoreSubRangePointOnBoundary -Specifies whether to complete without any errors if the new subrange's start and end points are the same. If this parameter is specified, no errors are displayed. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsAzureDatabase -Specifies whether the database is hosted on SQL Azure. - - -```yaml -Type: SwitchParameter -Parameter Sets: UnattachedDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubRangePoint -Specifies the start or end point of the data subrange to be created as defined by the following criteria: - ---The start point if the data sub-range is created on the upper side of the data range. ---The end point if the data sub-range is created on the lower side of the data range. - -The maximum value is NULL. - -```yaml -Type: Byte[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPDatabasePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Clear-SPServerScaleOutDatabaseDeletedDataSubRange](Clear-SPServerScaleOutDatabaseDeletedDataSubRange.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplication.md deleted file mode 100644 index e7004f126e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplication.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServiceApplication - -## SYNOPSIS -Sets properties of a service application. - - -## SYNTAX - -``` -Set-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-DefaultEndpoint <SPServiceEndpointPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-IisWebServiceApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] - [-ServiceApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPServiceApplication` cmdlet to set various properties of a service application such as the default endpoint and the application pool used by the service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------------EXAMPLE---------------- -``` -C:\PS>$serviceapp = Get-SPServiceApplication "My Service App" - -Set-SPServiceApplication $serviceapp -DefaultEndpoint https -``` - -This example sets the default endpoint of the service application to be https. - - -## PARAMETERS - -### -Identity -Specifies the service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubSettingsApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DefaultEndpoint -Specifies the address of the default endpoint of the service application. - -```yaml -Type: SPServiceEndpointPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IisWebServiceApplicationPool -Specifies the name or identity of the application pool used by the service application. - -The IisWebServiceApplicationPool parameter only applies to Web Service applications. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplicationProxyGroup -Specifies a custom service application proxy group for the Web application to use. -The Web application will use the proxies in this proxy group to connect to service applications. -If the ServiceApplicationProxyGroup parameter is not specified, the farm's default proxy group is used. - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationEndpoint.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationEndpoint.md deleted file mode 100644 index 22eb3a111e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationEndpoint.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spserviceapplicationendpoint -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServiceApplicationEndpoint -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServiceApplicationEndpoint - -## SYNOPSIS -Sets the host of an endpoint for a service application. - - -## SYNTAX - -### HostName -``` -Set-SPServiceApplicationEndpoint [-Identity] <SPServiceEndpointPipeBind> -HostName <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### ResetHostName -``` -Set-SPServiceApplicationEndpoint [-Identity] <SPServiceEndpointPipeBind> [-ResetHostName] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set- SPServiceApplicationEndpoint` cmdlet sets the host of a service endpoint. -Use the second parameter set to reset the host of the service endpoint to use the default endpoint. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE------------------- -``` -Set-SPServiceApplicationEndpoint -Identity "ServiceApp1" -HostName http://sitename -ResetHostName $true -``` - -This example associates the SPServiceEndpoint object with the specified identity and resets the hostname. - - -## PARAMETERS - -### -Identity -Specifies the service endpoint to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URI of an endpoint address, in the form http://sitename:8003/servicemodelsamples/service; or an instance of a valid SPServiceEndpoint object. - -```yaml -Type: SPServiceEndpointPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -HostName -Specifies the default host of the service endpoint. - -The type must be a valid full load balanced URL, in the form http://server_name. - -```yaml -Type: String -Parameter Sets: HostName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResetHostName -Removes the current host of the service endpoint and uses the default host. - -```yaml -Type: SwitchParameter -Parameter Sets: ResetHostName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationPool.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationPool.md deleted file mode 100644 index ee0f42ffc5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationPool.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spserviceapplicationpool -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServiceApplicationPool -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServiceApplicationPool - -## SYNOPSIS -Changes the account used for the Identity of the specified application pool. - - -## SYNTAX - -``` -Set-SPServiceApplicationPool [-Identity] <SPIisWebServiceApplicationPoolPipeBind> - [[-Account] <SPProcessAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPServiceApplicationPool` cmdlet changes the account used for the Identity of the specified application pool. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Set-SPServiceApplicationPool TestServiceWebApplicationPool -Account testdomain\testuser1 -``` - -This example changes the identity of the selected service application pool. - -For the Account parameter, the name of a managed account in the farm can be given. -Use the `Get-SPManagedAccount` cmdlet to view the existing managed account in the farm. -Also, a process account from the output of the `Get-SPProcessAccount` cmdlet can be used. - - -## PARAMETERS - -### -Identity -Specifies the identity of the Web service application pool to configure. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Account -Specifies the credentials that will be the new Identity of the application pool. - -```yaml -Type: SPProcessAccountPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationSecurity.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationSecurity.md deleted file mode 100644 index e07654e388..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceApplicationSecurity.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spserviceapplicationsecurity -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServiceApplicationSecurity -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServiceApplicationSecurity - -## SYNOPSIS -Updates the SPObjectSecurity object for a service application. - - -## SYNTAX - -``` -Set-SPServiceApplicationSecurity [-Identity] <SPServiceApplicationPipeBind> - [-ObjectSecurity] <SPObjectSecurity> [-Admin] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPServiceApplicationSecurity` cmdlet updates a security object for the specified service application. -Use this cmdlet with the `Grant-SPObjectSecurity` and `Get-SPServiceApplicationSecurity` cmdlets to manage security for a service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$sa = Get-SPServiceApplication -Identity <ID> -$security = Get-SPServiceApplicationSecurity $sa -Admin -$principal = New-SPClaimsPrincipal contoso\johndoe -IdentityType WindowsSamAccountName -Grant-SPObjectSecurity $security $principal "Full Control" -Set-SPServiceApplicationSecurity $sa -Admin $security -``` - -This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on a service application and adds a new user principal to that ACL. -The new user is an administrator for the service application $serviceApp. - - -## PARAMETERS - -### -Identity -Specifies the service application that contains the SPObjectSecurity object to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a service application (for example, ServiceApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ObjectSecurity -Specifies the SPObjectSecurity object to update. - -```yaml -Type: SPObjectSecurity -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Admin -Updates the access control list (ACL) that contains the administrators list of the service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceHostConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceHostConfig.md deleted file mode 100644 index d0e0db179b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPServiceHostConfig.md +++ /dev/null @@ -1,250 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spservicehostconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPServiceHostConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPServiceHostConfig - -## SYNOPSIS -Configures one or more common settings for all Web services. - - -## SYNTAX - -### SslCertificateReference -``` -Set-SPServiceHostConfig [-Identity] <SPIisWebServiceSettings> -SslCertificateThumbprint <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-HttpPort <Int32>] [-HttpsPort <Int32>] - [-NetTcpPort <Int32>] [-NoWait] [-SslCertificateStoreName <String>] [-WhatIf] [<CommonParameters>] -``` - -### SslCertificateImport -``` -Set-SPServiceHostConfig [-Identity] <SPIisWebServiceSettings> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-HttpPort <Int32>] [-HttpsPort <Int32>] [-ImportSslCertificate <X509Certificate2>] - [-NetTcpPort <Int32>] [-NoWait] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set- SPServiceHostConfig` cmdlet configures one or more common settings for all Web services. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Set-SPServiceHostConfig -Port 12345 -``` - -This example sets the HTTP port for the Web services. - - -## PARAMETERS - -### -Identity -Specifies the identity of the Web service application to configure. - -```yaml -Type: SPIisWebServiceSettings -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SslCertificateThumbprint -Specifies the thumbprint of the SSL certificate to retrieve for secure protocols. - -```yaml -Type: String -Parameter Sets: SslCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HttpPort -Specifies the new port for the Web service. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: Port -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HttpsPort -Specifies the new secure port for the Web service. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: SecurePort -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImportSslCertificate -Specifies the SSL Certificate to use for secure protocols. - -```yaml -Type: X509Certificate2 -Parameter Sets: SslCertificateImport -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetTcpPort -Sets the TCP port for the Web service. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoWait -For more information, see TechNet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SslCertificateStoreName -Specifies the thumbprint of the SSL certificate to retrieve for secure protocols. - -```yaml -Type: String -Parameter Sets: SslCertificateReference -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSessionStateService.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSessionStateService.md deleted file mode 100644 index a8e263de69..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSessionStateService.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsessionstateservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSessionStateService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSessionStateService - -## SYNOPSIS -Updates the credentials that are used to communicate with the state service database. - - -## SYNTAX - -``` -Set-SPSessionStateService [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DatabaseCredentials <PSCredential>] [-SessionTimeout <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPSessionStateService` cmdlet updates the credentials that are used to communicate with the state service database. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPSessionStateService -SessionTimeout 120 -``` - -This example changes the ASP.NET session state time-out to 2 hours. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the database credentials for SQL Authentication that are used to access the state service database. -If this parameter is not specified, Windows authentication is used. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionTimeout -Specifies the time, in minutes that an ASP.NET session will remain active with no user activity. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSite.md deleted file mode 100644 index d2d1ab6d8a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSite.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsite -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSite - -## SYNOPSIS -Configures the specified sites. - - -## SYNTAX - -### SiteSubscription -``` -Set-SPSite [-Identity] <SPSitePipeBind> [-AdministrationSiteType <SPAdministrationSiteType>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Force] - [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -### Default -``` -Set-SPSite [-Identity] <SPSitePipeBind> [-AdministrationSiteType <SPAdministrationSiteType>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-LockState <String>] [-MaxSize <Int64>] - [-OwnerAlias <SPUserPipeBind>] [-QuotaTemplate <SPQuotaTemplatePipeBind>] - [-SecondaryOwnerAlias <SPUserPipeBind>] [-SharingType <String>] [-Template <SPWebTemplatePipeBind>] - [-Url <String>] [-UserAccountDirectoryPath <String>] [-WarningSize <Int64>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPSite` cmdlet configures the site collection that is specified by the Identity parameter. -If a parameter is not used, the value is not changed. - -The QuotaTemplate parameter is mutually exclusive to the MaxSize parameter and WarningSize parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Get-SPSite https://sitename/sites/teams/* | Set-SPSite -SecondaryOwner "DOMAIN\Jdoe" -``` - -This example sets the secondary owner on a set of site collections to DOMAIN\Jdoe. - - -### --------------------EXAMPLE 2--------------------- -``` -Set-SPSite -identity "https://sitename/" -MaxSize 4000000 -WarningSize 2000000 -``` - -This example configures the Quota settings for the site collection https://sitename. - - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site collection to configure, or refers to an SPSite object that contains sites to configure. - -The type must be a valid URL, in the form https://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AdministrationSiteType -Specifies the site type. - -Valid values are None or TentantAdministration. - -```yaml -Type: SPAdministrationSiteType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses confirmation messages involved in setting the site subscription. -This parameter is used in conjunction with the SiteSubscription parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LockState -Sets the lock state of this site collection. -The valid lock states are - -Unlock Unlocks the site collection and makes it available to users - -NoAdditions Prevents users from adding new content to the site collection. -Updates and deletions are still allowed - -ReadOnly Prevents users from adding, updating, or deleting content. - -NoAccess Prevents access to content completely. -Users who attempt to access the site receive an access-denied message. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSize -Sets the maximum storage size for the site collection in bytes. - -The integer value must be larger than the WarningSize value. -You cannot use this parameter if the site collection is using a quota template. - -```yaml -Type: Int64 -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OwnerAlias -Specifies the alias name of the site collection administrator. - -The type must be a valid e-mail alias, in the form domain\username. - -```yaml -Type: SPUserPipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QuotaTemplate -Specifies the new quota template for this site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890abcdef or a string - -```yaml -Type: SPQuotaTemplatePipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryOwnerAlias -Sets the alias of the secondary site collection administrator. - -The type must be a valid e-mail alias, in the form domain\username. - -```yaml -Type: SPUserPipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharingType -Specifies whether external access a site collection should be disabled, limited to external users only, or enabled for external users and anonymous guests. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the Site Group to get site collections. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the template for this site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890abcdef. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Url -Specifies the URL of the new site. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserAccountDirectoryPath -Sets an organization unit to which to scope user accounts. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarningSize -Sets the storage warning level for the site collection in bytes. - -The integer value must be between 0 and the MaxSize value. -You cannot use this parameter if the site collection is using a quota template. - -```yaml -Type: Int64 -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteAdministration.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteAdministration.md deleted file mode 100644 index 3e60240213..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteAdministration.md +++ /dev/null @@ -1,312 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsiteadministration -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSiteAdministration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSiteAdministration - -## SYNOPSIS -Allows farm administrators to configure any site collection. - - -## SYNTAX - -### SiteSubscription -``` -Set-SPSiteAdministration [-Identity] <SPSiteAdministrationPipeBind> - [-AdministrationSiteType <SPAdministrationSiteType>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Force] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -### Default -``` -Set-SPSiteAdministration [-Identity] <SPSiteAdministrationPipeBind> - [-AdministrationSiteType <SPAdministrationSiteType>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-LockState <String>] [-MaxSize <Int64>] [-OwnerAlias <SPUserPipeBind>] - [-SecondaryOwnerAlias <SPUserPipeBind>] [-Template <SPWebTemplatePipeBind>] [-WarningSize <Int64>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPSiteAdministration` cmdlet allows a farm administrator to configure particular settings on a site collection even if the farm administrator is not granted explicit permissions. -Any parameter that is not provided is not changed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPSiteAdministration https://sitename -OwnerAlias "DOMAIN\NewOwner" -``` - -This example allows farm administrators to change the ownership of a site collection to which they do not have access. - - -## PARAMETERS - -### -Identity -Specifies the URL (full or partial) or GUID of the site collection. - -The type must be a valid URL, in the form https://server_name, or a GUID, in the form 1234-456-987fg. - -```yaml -Type: SPSiteAdministrationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AdministrationSiteType -Specifies the site type. - -Valid values are None or TentantAdministration. - -```yaml -Type: SPAdministrationSiteType -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses confirmation messages involved in setting the site subscription. -This parameter is used in conjunction with the SiteSubscription parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LockState -Specifies the lock state for the given site collection. - -The type must be any of the following values: - -- Unlock: Sets the site collection to unlock. -- Content: No new content can be added. Updates and deletions are allowed. -- Readonly: Sets the site collection to read-only. -- Noaccess: Sets the site collection to unavailable to all users. - -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxSize -Sets the maximum storage size of the site collection. - -The type must be a valid number greater than or equal to 0. - -Set to 0 for unlimited. - - -```yaml -Type: Int64 -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OwnerAlias -Sets the owner of this site collection. - -The type must be a valid user alias. - -```yaml -Type: SPUserPipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecondaryOwnerAlias -Sets the secondary owner of this site collection. - -The type must be a valid user alias. - -```yaml -Type: SPUserPipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteSubscription -Specifies the Site Group to get site collections. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: SiteSubscription -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the Web template for the top-level Web site of this site collection. -This can only be given if the template has not already been configured. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890abcdef, or an SPWebTemplate object. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarningSize -Specifies the site collection warning size limit. - -The type must be a valid number greater than or equal to 0. -Set to 0 for unlimited. - -```yaml -Type: Int64 -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionConfig.md deleted file mode 100644 index de7038cb5d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionConfig.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsitesubscriptionconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSiteSubscriptionConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSiteSubscriptionConfig - -## SYNOPSIS -Sets the configuration properties of a site subscription. - - -## SYNTAX - -``` -Set-SPSiteSubscriptionConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-PassThru] [-UserAccountDirectoryPath <String>] - [-WhatIf] [-FeaturePack <SPSiteSubscriptionFeaturePackPipeBind>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPSiteSubscriptionConfig` cmdlet sets the configuration properties of a site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPSiteSubscriptionConfig https://contoso.com -FeaturePack 12345678-90ab-cdef-1234-567890abcdef -``` - -This example sets the Feature set of the entire site subscription that contains https://contoso.com with a Feature pack GUID. - - -## PARAMETERS - -### -Identity -Specifies the site subscription configuration to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; an SPSite (object or URL) of a site collection that is a member of the site subscription; or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Specifies the output object can be passed through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserAccountDirectoryPath -Sets the site user account directory path to a specific organizational unit (OU) that is in the same domain as the site subscription. - -The type must be a name of a distinguished OU; for example, OU=Contoso1, DC=OSGCorp,DC=local. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FeaturePack -{{Fill FeaturePack Description}} - -```yaml -Type: SPSiteSubscriptionFeaturePackPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionEdiscoveryHub.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionEdiscoveryHub.md deleted file mode 100644 index c3b6c5d38d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionEdiscoveryHub.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsitesubscriptionediscoveryhub -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSiteSubscriptionEdiscoveryHub -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSiteSubscriptionEdiscoveryHub - -## SYNOPSIS -Sets properties for the eDiscovery hub of a site subscription. - - -## SYNTAX - -``` -Set-SPSiteSubscriptionEdiscoveryHub -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-SearchScope <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPSiteSubscriptionEdiscoveryHub` cmdlet sets global properties and settings for the Ediscovery hub. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE-------------------- -``` -Set-SPSiteSubscriptionEdiscoverySearchScope -Site https://contoso.com/sites/sitecollection1 -SearchScope 1 -``` - -This example enables the search scope for the entire site subscription. -A value of zero (0) disables the search scope across the entire site subscription. - - -## PARAMETERS - -### -Site -Specifies the site collection for the Ediscovery hub. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchScope -Specifies the name for the search scope. -The default value is All Sites. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionIRMConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionIRMConfig.md deleted file mode 100644 index e6b2093a59..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionIRMConfig.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsitesubscriptionirmconfig -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSiteSubscriptionIRMConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSiteSubscriptionIRMConfig - -## SYNOPSIS -Sets the Information Rights Management (IRM) settings. - - -## SYNTAX - -``` -Set-SPSiteSubscriptionIRMConfig [-Identity] <SPSiteSubscriptionPipeBind> [-IrmEnabled] - [-AssignmentCollection <SPAssignmentCollection>] [-CertificateServerUrl <Uri>] [-Confirm] [-PassThru] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Identity parameter of the `Set-SPSiteSubscriptionIRMConfig` cmdlet to set the IRM setting for a specified tenant. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -site = Get-SPSite HYPERLINK "https://<myspserver>" https:// <myspserver> - -C:\PS>$subscription = $site.SiteSubscription - -Set-SPSiteSubscriptionIRMConfig -Identity $subscription -IrmEnabled -CertificateServerUrl https:// <rmsserver> -``` - -This example enables IRM for the tenant and configures it to use the specified RMS server. - - -### --------------------EXAMPLE 2--------------------- -``` -site = Get-SPSite HYPERLINK "https://myspserver/" https:// <myspserver> - -C:\PS>$subscription = $site.SiteSubscription - -Set- SPSiteSubscriptionIRMConfig -Identity $subscription -IrmEnabled:$false -``` - -This example disables IRM for the tenant. - - -## PARAMETERS - -### -Identity -Specifies a site subscription for a particular tenant. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IrmEnabled -Specifies whether IRM is enabled in the tenant. - -The default value is false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CertificateServerUrl -Specifies the address of the RMS certificate server to use for the tenant. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Specifies that the output object can be passed through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPSiteSubscriptionIRMConfig](Get-SPSiteSubscriptionIRMConfig.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionMetadataConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionMetadataConfig.md deleted file mode 100644 index 19174a7f41..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionMetadataConfig.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsitesubscriptionmetadataconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSiteSubscriptionMetadataConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSiteSubscriptionMetadataConfig - -## SYNOPSIS -Sets the site subscription configuration settings for a specified Metadata Service application. - - -## SYNTAX - -``` -Set-SPSiteSubscriptionMetadataConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-ServiceProxy] <SPMetadataServiceProxyCmdletPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DoNotUnpublishAllPackages] [-HubUri <String>] [-SyndicationErrorReportEnabled] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPSiteSubscriptionMetadataConfig` cmdlet to set the site subscription-specific settings for a specified shared service application for the Metadata Service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPSiteSubscriptionMetadataConfig -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -HubUri "https://sitename/" -SyndicationErrorReportEnabled:$false -``` - -This example sets the content type syndication hub and disables syndication error reporting for a specific site subscription on an existing partitioned Metadata Service application. - - -## PARAMETERS - -### -Identity -Specifies the site subscription for which to set the Metadata Service application settings. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a site subscription (for example, SiteSubscriptionConfig1); or an instance of a valid SiteSubscription object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceProxy -Specifies the local metadata service proxy for the service application that contains the site subscription-specific settings. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of the service application proxy (for example, ServiceAppProxy1); or an instance of a valid SPMetadataServiceProxy object. - -```yaml -Type: SPMetadataServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DoNotUnpublishAllPackages -{{ Fill DoNotUnpublishAllPackages description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HubUri -Specifies the URI of the syndication hub. - -The type must be a valid URI, in the form file:\\\\server_name\sitedocs. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -SyndicationErrorReportEnabled -Enables error reporting for content type syndication. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionProfileConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionProfileConfig.md deleted file mode 100644 index 470f21c26c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionProfileConfig.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsitesubscriptionprofileconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSiteSubscriptionProfileConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSiteSubscriptionProfileConfig - -## SYNOPSIS -Sets the parameters of a site subscription. - - -## SYNTAX - -### Default -``` -Set-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> - [-MySiteHostLocation <SPSitePipeBind>] -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-SynchronizationOU <String>] [-WhatIf] - [<CommonParameters>] -``` - -### MySiteSettings -``` -Set-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> - -MySiteHostLocation <SPSitePipeBind> -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-MySiteManagedPath <SPPrefixPipeBind>] - [-SiteNamingConflictResolution <String>] [-SynchronizationOU <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPSiteSubscriptionProfileConfig` cmdlet sets the parameters of a site subscription. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -$sub = Get-SPSiteSubscription http://contoso/my -Set-SPSiteSubscriptionProfileConfig -Identity $sub -SiteNamingConflictResolution 3 -SynchronizationOU OrgUnit1 -``` - -This example sets the parameter of the site subscription SiteNamingConflictResolution to always avoid any conflicts and parameter SynchronizationOU to OrgUnit1. - - -## PARAMETERS - -### -Identity -Specifies the proxy of the User Profile Service application that contains the site subscription to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a User Profile Service application proxy (for example, UserProfileSvcProxy1); or an instance of a valid SPServiceApplicationProxy object. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MySiteHostLocation -Specifies the site collection where the My Site host for the site subscription is provisioned. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: Default -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -```yaml -Type: SPSitePipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy -Specifies the name of the proxy for the User Profile Service application. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MySiteManagedPath -Specifies the managed path where personal sites will be created. - -The type must be a valid URL, in the form https://server_name. - -```yaml -Type: SPPrefixPipeBind -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteNamingConflictResolution -Specifies the format to use to name personal sites. - -Use one of the following integer values: - -1-- Personal site collections to be named after user names without any conflict resolution. -For example, https://portal_site/location/username/ - -2-- Personal site collections to be named after user names with conflict resolution by using domain names. -For example, .../username/ or .../domain_username/ - -3-- Personal site collections to be named using domain and username always to avoid any conflicts. -For example, https://portal_site/location/domain_username/ - -The default value is 1 (do not resolve conflicts). - -```yaml -Type: String -Parameter Sets: MySiteSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SynchronizationOU -Specifies the organizational unit that serves the site subscription. - -The type must be a valid name of an organizational unit; for example, OrgUnit1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteURL.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteURL.md deleted file mode 100644 index 77c0a0b12c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteURL.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsiteurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSiteURL -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSiteURL - -## SYNOPSIS -Adds or changes an URL mapping for the site. - - -## SYNTAX - -``` -Set-SPSiteURL [-Identity] <SPSitePipeBind> -Url <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [-Zone <SPUrlZone>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPSiteUrl` cmdlet adds or changes an URL mapping for the site. - -The `Set-SPSiteUrl` cmdlet only applies to the root site collection for a host name that is, http://www.contoso.com. -This cmdlet cannot be directly run against a managed path site collection underneath the root that is, http://www.contoso.com/sites/test. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -C:\PS>$site = Get-SPSite 'http://www.contoso.com/' - -Set-SPSiteURL -Identity $site -Url http://contoso.sharepoint.com -Zone 0 -``` - -This example adds an additional URL, http://contoso.sharepoint.com, to the site collection. -The newly added URL is in the default zone. - - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site collection to set. -Must be the root site collection for a host-name. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Url -Specifies the URL. -This must be unique. -This must be an absolute URL including scheme (that is, https://www.contoso.com). -If URL exists, the current entry is updated. -Otherwise, the URL entry is added and cannot be in use by another site collection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Zone -Specifies one of the five zones with which the alternate URL is associated. -If the Zone parameter is not specified and is a new entry, the default value is set. -If an entry exists and is not specified, do not change. - - -```yaml -Type: SPUrlZone -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPSiteUrl](Get-SPSiteUrl.md) - -[Remove-SPSiteUrl](Remove-SPSiteUrl.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceApplication.md deleted file mode 100644 index a061931d86..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceApplication.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spstateserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPStateServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPStateServiceApplication - -## SYNOPSIS -Updates the name of a state service application. - - -## SYNTAX - -``` -Set-SPStateServiceApplication [-Identity] <SPStateServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPStateServiceApplication` cmdlet updates the name of a state service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPStateServiceApplication -Identity "State Service Application 1" -Name "New name for State Service Application 1" -``` - -This example changes the display name of a state service application. - - -## PARAMETERS - -### -Identity -Specifies the state service application to update. - -The type must be a valid name of a state service application (for example, StateServiceApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPStateServiceApplication object. - -```yaml -Type: SPStateServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name of the state service application. - -The type must be a valid name of a state service application; for example, StateSvc1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceApplicationProxy.md deleted file mode 100644 index a90b38baf3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceApplicationProxy.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spstateserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPStateServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPStateServiceApplicationProxy - -## SYNOPSIS -Updates the name of a state service application proxy. - -## SYNTAX - -``` -Set-SPStateServiceApplicationProxy [-Identity] <SPStateServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPStateServiceApplicationProxy` cmdlet updates the name of a state service application proxy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -Set-SPServiceApplicationProxy -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -Name "New Service Application Proxy Name" -``` - -This example changes the display name of a state service application proxy. - - -## PARAMETERS - -### -Identity -Specifies the state service application proxy to update. - -The type must be a valid name of a state service application proxy (for example, StateServiceProxy); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPStateServiceApplicationProxy object. - -```yaml -Type: SPStateServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -{{ Fill Confirm Description }} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name of the state service application proxy. - -The type must be a valid name of a state service application; for example, StateSvcProxy1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -{{ Fill WhatIf Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceDatabase.md deleted file mode 100644 index 6a1aea3162..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPStateServiceDatabase.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPStateServiceDatabase - -## SYNOPSIS -Updates properties of a state service database. - -## SYNTAX - -``` -Set-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> - [[-ServiceApplication] <SPStateServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DatabaseCredentials <PSCredential>] [-Weight <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPStateServiceDatabase` cmdlet manages the credentials that are used to communicate with the database, sets the weight of the database, or changes the state service application with which it is associated. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Set-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -Weight 10 -``` - -This example updates the database weight to the maximum (10). - - -### --------------------EXAMPLE 2--------------------- -``` -Set-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -ServiceApplication "StateSvcApp1" -``` - -This example updates the associated service application for a state service database. - - -### --------------------EXAMPLE 3--------------------- -``` -C:\PS>$cred = Get-Credential - -Set-SPStateServiceDatabase -Identity "StateSvcDB1" -DatabaseCredentials $cred -``` - -This example updates the SQL Authentication credentials that are used for a given database. - - -## PARAMETERS - -### -Identity -Specifies the state service database to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a state database (for example, StateSvcDB1); or an instance of a valid SPStateServiceDatabase object. - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplication -Specifies the state service application to which to add the state database. - -The type must be a valid name of a state service application (for example, StateServiceApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPStateServiceApplication object. - -```yaml -Type: SPStateServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: Application -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the database credentials for SQL Authentication used to access the state service database. -If this parameter is not specified, Windows authentication is used. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Weight -Specifies the weight for the state database. -The default value is 1. - -The type must be a valid integer in the range of 1 to 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSubscriptionSettingsServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSubscriptionSettingsServiceApplication.md deleted file mode 100644 index f51f507f13..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPSubscriptionSettingsServiceApplication.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spsubscriptionsettingsserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPSubscriptionSettingsServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPSubscriptionSettingsServiceApplication - -## SYNOPSIS -Sets properties of a subscription settings service application. - - -## SYNTAX - -``` -Set-SPSubscriptionSettingsServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseCredentials <PSCredential>] - [-DatabaseName <String>] [-DatabaseServer <String>] [-FailoverDatabaseServer <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPSubscriptionSettingsServiceApplication` cmdlet to set properties on a subscription settings service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ---------------------EXAMPLE-------------------------- -``` -C:\PS>$applicationPool = GetServiceApplicationPool SettingsApplicationPool - -Get-SPServiceApplication -Name SettingsServiceApp | Set-SPSubscriptionSettingsServiceApplication -ApplicationPool $applicationPool -``` - -This example changes the application pool of the subscription settings service application. -This command assumes that a subscription settings service application named SettingsServiceApp exists and that an application pool named SettingsApplicationPool exists - - -## PARAMETERS - -### -Identity -Specifies the settings service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubscriptionSettingsApp1); or an instance of a valid SPSubscriptionSettingsServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Server Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the subscription settings database. - -The type must be a valid name of a SQL Server database; for example, SubscriptionSettingsAppDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host SQL Server instance for the database specified in DatabaseName parameter. - -The type must be a valid SQL Server instance name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the name of the host SQL Server instance for the failover database server. - -The type must be a valid SQL Server instance name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPThrottlingRule.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPThrottlingRule.md deleted file mode 100644 index f177cf9a25..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPThrottlingRule.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spthrottlingrule -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPThrottlingRule -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPThrottlingRule - -## SYNOPSIS -Changes properties of an existing throttling rule. - - -## SYNTAX - -``` -Set-SPThrottlingRule [-Identity] <SPThrottlingRulePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Criteria <SPRequestManagementRuleCriteriaPipeBind[]>] [-Expiration <DateTime>] [-Threshold <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPThrottlingRule` cmdlet to change the properties of an existing throttling rule by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE--------------------- -``` -C:\PS>$web=Get-SPWebApplication -Identity <URL of web application> - -C:\PS>$rm=Get-SPRequestManagementSettings -Identity $web - -C:\PS>$c=New-SPRequestManagementRuleCriteria -Value http -Property url -MatchType startswith -CaseSensitive $false - -C:\PS>$throttlingrule=Add-SPThrottlingRule -RequestManagementSettings $rm -Name <Rule Name> -Criteria $c -Threshold 4 - -C:\PS>$criteriaNew = New-SPRequestManagementRuleCriteria -Property UserAgent -MatchType Equals -Value "Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 6.0 Robot)" - -Set-SPThrottlingRule -Identity $ throttlingrule -Criteria $criteriaNew -Threshold 8 -``` - -This example sets throttling rule property - - -## PARAMETERS - -### -Identity -Specifies the throttling rule object to set. - -```yaml -Type: SPThrottlingRulePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Criteria -Specifies the criteria for the rule to match. - -```yaml -Type: SPRequestManagementRuleCriteriaPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Expiration -Specifies the expiration date and time of the rule. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Threshold -Specifies a value between 0 and 10 which defines the maximum threshold for throttling. -The Request Manager will remove routing targets if the Health-Score becomes greater than this value. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPThrottlingRule](Add-SPThrottlingRule.md) - -[Get-SPThrottlingRule](Get-SPThrottlingRule.md) - -[Remove-SPThrottlingRule](Remove-SPThrottlingRule.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTimerJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTimerJob.md deleted file mode 100644 index de7c73762c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTimerJob.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptimerjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTimerJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTimerJob - -## SYNOPSIS -Sets the schedule for running a timer job. - - -## SYNTAX - -``` -Set-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Schedule <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPTimerJob` cmdlet sets the schedule for running a specified timer job. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE------------------------ -``` -Get-SPTimerJob job-recycle-bin-cleanup | Set-SPTimerJob -Schedule "weekly at sat 5:00" -``` - -This example sets the schedule to run the job-recylce-bin-cleanup timer job to weekly at sat 5:00. - -## PARAMETERS - -### -Identity -Specifies the timer job to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a timer job (for example, TimerJob1); or an instance of a valid SPTimerJob object. - -```yaml -Type: SPTimerJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Schedule -Specifies the schedule for running the timer job. - -The type must be a valid SharePoint Timer service (SPTimer) schedule in the form of any one of the following schedules: - -- Every 5 minutes between 0 and 59 -- Hourly between 0 and 59 -- Daily at 15:00:00 -- Weekly between Fri 22:00:00 and Sun 06:00:00 -- Monthly at 15 15:00:00 -- Yearly at Jan 1 15:00:00 - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTopologyServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTopologyServiceApplication.md deleted file mode 100644 index 7fa9844e5d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTopologyServiceApplication.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.SharePoint.TopologyService-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptopologyserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTopologyServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTopologyServiceApplication - -## SYNOPSIS -Sets the properties on the topology service application of the local farm. - - -## SYNTAX - -``` -Set-SPTopologyServiceApplication [-Identity] <SPTopologyWebServiceApplicationPipeBind> - -LoadBalancerUrl <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPTopologyServiceApplication` cmdlet sets the advanced properties of an application when the Identity parameter is used. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Set-SPTopologyServiceApplication 67877d63-bff4-4521-867a-ef4979ba07ce -LoadBalancedURL "https://testurl/" -``` - -This example sets the load-balanced URL for the topology service application. - -The topology service application GUID is unique to every farm. -You can run the `Get-SPTopologyServiceApplication` cmdlet to retrieve the GUID. - - -## PARAMETERS - -### -Identity -Specifies the GUID of the application to be set. - -The type must be a valid GUID, in the form 1234-456-854gh. - -```yaml -Type: SPTopologyWebServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -LoadBalancerUrl -Specifies an external physical load balancer. - -The type must be a valid URL, in the form http://search. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTopologyServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTopologyServiceApplicationProxy.md deleted file mode 100644 index 1fa9823953..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTopologyServiceApplicationProxy.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.SharePoint.TopologyService-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptopologyserviceapplicationproxy -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTopologyServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTopologyServiceApplicationProxy - -## SYNOPSIS -Sets the proxy properties of the topology service application. - - -## SYNTAX - -``` -Set-SPTopologyServiceApplicationProxy [-Identity] <SPTopologyWebServiceProxyPipeBind> -BadListPeriod <String> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPTopologyServiceApplicationProxy` cmdlet sets the properties of the local topology service application proxy and the default load balancer. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Set-SPTopologyServiceApplicationProxy 67877d63-bff4-4521-867a-ef4979ba07ce -BadListPeriod 1234 -``` - -This example sets the bad list period for the given topology service application proxy. - -The topology service application GUID is unique to every farm. -You can run the `Get-SPTopologyServiceApplication` cmdlet to retrieve the GUID. - - -## PARAMETERS - -### -Identity -Specifies the GUID of the application proxy. - -The type must be a valid GUID, in the form 1234-4567-098jhj. - -```yaml -Type: SPTopologyWebServiceProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -BadListPeriod -Specifies the time period that a node is kept in a bad list. - -The type must be a valid value between 1 and 480 (in minutes). - -The default value is 10. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationServiceApplication.md deleted file mode 100644 index 061e3b20a6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationServiceApplication.md +++ /dev/null @@ -1,653 +0,0 @@ ---- -external help file: Microsoft.Office.TranslationServices.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptranslationserviceapplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTranslationServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTranslationServiceApplication - -## SYNOPSIS -Sets property settings on a Machine Translation service application. - -## SYNTAX - -``` -Set-SPTranslationServiceApplication [-Identity] <TranslationServiceApplicationPipeBind> - [-AddEnabledFileExtensions <String[]>] [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-ClearEnabledFileExtensions] [-Confirm] - [-DatabaseCredential <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] - [-DisableBinaryFileScan <Boolean>] [-EnableAllFileExtensions] [-FailoverDatabaseServer <String>] - [-JobExpirationDays <Int32>] [-KeepAliveTimeout <Int32>] [-MachineTranslationAddress <String>] - [-MachineTranslationCategory <String>] [-MachineTranslationClientId <String>] [-MaximumBinaryFileSize <Int32>] - [-MaximumItemsPerDay <Int32>] [-MaximumItemsPerPartitionPerDay <Int32>] - [-MaximumSyncTranslationRequests <Int32>] [-MaximumTextFileSize <Int32>] [-MaximumTranslationAttempts <Int32>] - [-MaximumTranslationTime <Int32>] [-MaximumWordCharacterCount <Int32>] [-RecycleProcessThreshold <Int32>] - [-RemoveEnabledFileExtensions <String[]>] [-TimerJobFrequency <Int32>] [-TotalActiveProcesses <Int32>] - [-TranslationsPerInstance <Int32>] [-UseDefaultInternetSettings] [-WebProxyAddress <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPTranslationServiceApplication` cmdlet to set properties on a Machine Translation service application in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE--------------- -``` -Set-SPTranslationServiceApplication TranslationService -JobExpirationDays 14 -TotalActiveProcesses 3 -``` - -This example sets the job expiration to 14 days and the number of worker processes per server to 3 for the Machine Translation Service application named TranslationService. - - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the instance of the Machine Translation service to set. - -The type must be a valid URL in the form, https://server_name or a valid GUID (for example, 12345678-90ab-cdef-1234-567890bcdefgh). - -```yaml -Type: TranslationServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AddEnabledFileExtensions -Comma delimited list of file extensions that you want to add to the set of enabled file extensions for the Machine Translation Service application - -To return a list of supported file extensions, type \[Microsoft.Office.TranslationServices.TranslationService\]::EnumerateFileExtensions(). - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the managed application pool that the instance of Translation Service will run in. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClearEnabledFileExtensions -Disables all file extensions for the Machine Translation Service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredential -Specifies the SQL Server credentials used for this Translation Service instance. -This parameter to be used only used for SQL authentication; if not present, Windows authentication is used instead. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the database name which is to be used for this Translation Service instance. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the database server which is to be used for this Translation Service instance. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableBinaryFileScan -Determines whether Gatekeeper is run on binary files. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableAllFileExtensions -Enables all file extensions for the Machine Translation Service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -Specifies the SQL server instance that will be used as a backup to the primary SQL Server instance. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -JobExpirationDays -Specifies the amount of days after which completed jobs can be automatically removed from the Machine Translation Service queue database. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepAliveTimeout -Specifies the length of time (in seconds) that the worker can be inactive before it is automatically stopped. - -The valid values are 60 to 600. -The default value is 60. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MachineTranslationAddress -Specifies the service URL the service application will use to call the translation provider. -For example, https://api.microsofttranslator.com/v2/soap.svc - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MachineTranslationCategory -Specifies the category which will be used by the service when calling the translation provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MachineTranslationClientId -Specifies the AppId which will be used by the service when calling the translation provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumBinaryFileSize -Specifies the maximum file size in kilobytes (KB) which can be translated for file types which contain binary data. -The valid values are 100 to 524288. -The default value is 51200. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumItemsPerDay -Specifies the maximum number of items which can be added to the job queue in a 24-hour period. -A value of zero indicates no limit. - -The valid values are 1000 to 1000000. -A value of zero indicates no limit. -The default value is zero. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumItemsPerPartitionPerDay -Specifies the maximum number of items which can be added to the job queue in a 24-hour period per partition. -A value of zero indicates no limit. - -The valid values are 1000 to 1000000. -A value of zero indicates no limit. -The default value is zero. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumSyncTranslationRequests -Specifies the maximum number of items which can be added to the sync queue. -A valid of zero indicates no limit. - -The valid values are 0 to 300. -The default value is 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumTextFileSize -Specifies the maximum file size in kilobytes (KB) which can be translated for file types which contain mostly text data. -The valid values are 100 to 15360. -The default value is 5120. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumTranslationAttempts -Specifies the maximum number of attempts an unsuccessful job is tried before it is marked as Failed. - -The valid values are 1 to 10. -The default value is 2. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumTranslationTime -Specifies the maximum length of time (in minutes) that a translation can take. - -The valid values are 60 to 3600. -The default value is 600. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumWordCharacterCount -Specifies the maximum character count for a Microsoft Word document which can be translated. - -The valid Int values are 10000 to 10000000. -The default value is 500000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecycleProcessThreshold -Specifies the number of documents which are translated before a Translation Worker process is recycled. - -The valid values are 1 to 1,000. -The default value is 100. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveEnabledFileExtensions -Comma delimited list of file extensions that you want to remove from the set of enabled file extensions for the Machine Translation Service application. - -To return a list of supported file extensions, type \[Microsoft.Office.TranslationServices.TranslationService\]::EnumerateFileExtensions(). - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimerJobFrequency -Specifies the frequency (in minutes) with which the timer job for this service application runs. -The valid values are 1 to 59. -The default value is 15 minutes. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TotalActiveProcesses -Specifies the number of Translation Workers which are simultaneously running on a single machine. - -The valid values are 1 to 5. -The default value is 1. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TranslationsPerInstance -Specifies the number of translations dispatched to each service instance every time the timer job is run. - -Valid values are 1 to 1,000. -The default value is 200. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultInternetSettings -Determines whether the service application will use default Internet settings for the user service account to connect to the translation provider. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebProxyAddress -Specifies the web proxy address and port that the service application will use to connect to the translation provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPTranslationServiceApplication](New-SPTranslationServiceApplication.md) - -[New-SPTranslationServiceApplicationProxy](New-SPTranslationServiceApplicationProxy.md) - -[Set-SPTranslationServiceApplicationProxy](Set-SPTranslationServiceApplicationProxy.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationServiceApplicationProxy.md deleted file mode 100644 index 7a4945b07f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationServiceApplicationProxy.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.Office.TranslationServices.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptranslationserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTranslationServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTranslationServiceApplicationProxy - -## SYNOPSIS -Sets properties to the Machine Translation service application proxy. - -## SYNTAX - -``` -Set-SPTranslationServiceApplicationProxy [-Identity] <TranslationServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-MaximumGroupSize <Int32>] - [-MaximumItemCount <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPTranslationServiceApplicationProxy` cmdlet to set properties on a Machine Translation service application proxy in the farm. - -## EXAMPLES - -### -------------EXAMPLE--------- -``` -Set-SPTranslationServiceApplicationProxy TranslationServiceProxy -DefaultProxyGroup -``` - -This example adds the Machine Translation Service application proxy named TranslationServiceProxy to the default proxy group. - -## PARAMETERS - -### -Identity -Specifies the GUID of the service application proxy. - -The type must be a valid GUID in the form, 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: TranslationServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies that the Machine Translation Service application proxy be added to the default proxy group for the local farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumGroupSize -Maximum number of bytes the proxy will send to the service in a single request. -The valid values are 131072 to 10485760. -The default value is 2097152. - -We do not recommend use of this parameter. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumItemCount -Maximum number of documents to be translated that the proxy will send to the service in a single request. -The valid values are 1 to 40960. -The default value is 9000. - -We do not recommend use of this parameter. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPTranslationServiceApplication](New-SPTranslationServiceApplication.md) - -[New-SPTranslationServiceApplicationProxy](New-SPTranslationServiceApplicationProxy.md) - -[Set-SPTranslationServiceApplication](Set-SPTranslationServiceApplication.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationThrottlingSetting.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationThrottlingSetting.md deleted file mode 100644 index bb5d450fe3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTranslationThrottlingSetting.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Translation.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptranslationthrottlingsetting -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTranslationThrottlingSetting -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTranslationThrottlingSetting - -## SYNOPSIS -Sets the timer job duration. - -## SYNTAX - -``` -Set-SPTranslationThrottlingSetting [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-SiteQuota <Int32>] [-TenantQuota <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Set-SPTranslationThrottlingSetting cmdlet to set the timer job duration for each site collection. - -## EXAMPLES - -### -----------------EXAMPLE-------------------- -``` -Set-SPTranslationThrottlingSetting -SiteQuota 300 -TenantQuota 600 -``` - -This limits the Translation Timer job to spend no more than 300 seconds (5 minutes) per site collection, and no more than 600 seconds (10 minutes) per tenant. - -Note: TenantQuota must be greater than or equal to SiteQuota. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**NOTE:** When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteQuota - -The duration (in seconds) of timer job processing time that an individual SPSite is limited to - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantQuota -The duration (in seconds) of timer job processing time that an individual tenant is limited to. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedIdentityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedIdentityTokenIssuer.md deleted file mode 100644 index 45036ba25d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedIdentityTokenIssuer.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptrustedidentitytokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTrustedIdentityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTrustedIdentityTokenIssuer - -## SYNOPSIS -Sets the identity providers of a Web application. - - -## SYNTAX - -### ImportCertificateParameterSet -``` -Set-SPTrustedIdentityTokenIssuer [-Identity] <SPTrustedIdentityTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-ClaimProvider <SPClaimProviderPipeBind>] - [-ClaimsMappings <SPClaimMappingPipeBind[]>] [-Description <String>] - -ImportTrustCertificate <X509Certificate2> [-Realm <String>] [-SignInUrl <String>] [-UseWReply] [-Confirm] - [-RegisteredIssuerName <String>] [-WhatIf] [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -Set-SPTrustedIdentityTokenIssuer [-Identity] <SPTrustedIdentityTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-ClaimProvider <SPClaimProviderPipeBind>] - [-ClaimsMappings <SPClaimMappingPipeBind[]>] [-Description <String>] -MetadataEndPoint <Uri> [-Realm <String>] - [-SignInUrl <String>] [-UseWReply] [-Confirm] [-RegisteredIssuerName <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-SPTrustedIdentityTokenIssuer cmdlet sets the identity providers of a Web application or extended Web application. -For the ASP.NET Membership provider and Role provider, this cmdlet changes the identity provider only if the result is piped to a variable and passed to a Web application. -For security token service (STS) identity providers, this cmdlet changes the persisted identity provider object in the SPFarm object. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------------------EXAMPLE 1---------------------- -``` -Set-SPTrustedIdentityTokenIssuer "LiveIDSTS" -Certificate (Get-ChildItem"cert:Certificates (LocalComputer)\Personal\Certificates -Name "LiveID Cert") -``` - -This example sets the identity provider to LiveIDSTS. - - -### -------------------------EXAMPLE 2---------------------- -``` -C:\PS>$ip = @( (Get-SPTrustedIdentityTokenIssuer "LiveID STS"), (New-SPTrustedIdentityTokenIssuer -ASPNetMembershipProvider "myMembershipProvider" -ASPNetRoleProvider "myRoleProvider"), (Get-SPTrustedIdentityTokenIssuer "NTLM")) ) -New-SPWebApplication https://contoso.com -IdentityProvider $ip -``` - -This example sets the identity provider using the .ASPNetMembership and Role parameters. -When these parameters are used, a variable must be set; otherwise, the values do not take effect. - - -## PARAMETERS - -### -Identity -Specifies the identity provider to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of identity provider (for example, LiveID STS); or an instance of a valid SPIdentityProvider object. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClaimProvider -Specifies the IP STS that can resolve and search claims for claims people picker. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a claim provider (for example, MyIDprovider1); or an instance of a valid SPClaimProvider object. - -```yaml -Type: SPClaimProviderPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClaimsMappings -Specifies the mapping of the claims from the original token to the SharePoint token. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a claim mapping rule (for example, Email); or an instance of a valid SPClaimMapping object. - -```yaml -Type: SPClaimMappingPipeBind[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a description for the new identity provider. - -The type must be a valid string; for example, LiveID STS. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ImportTrustCertificate -Specifies the X.509 certificate object from trusted authentication provider farm. - -The type must be a name of a valid X.509 certificate; for example, Certificate1. - -```yaml -Type: X509Certificate2 -Parameter Sets: ImportCertificateParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Realm -Specifies the realm, or resource partition, associated with this trust. - -The type must be a name of a valid realm; for example, MD_REALM. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInUrl -Specifies the sign-in URLs for this trusted identity provider STS. - -The type must be a valid URL, in the form https://int.live.com/. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseWReply -Includes a WReply with the token request. -Wreply is a URL at the relying party to which the requestor is redirected once sign-out processing is complete. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegisteredIssuerName -{{Fill RegisteredIssuerName Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedRootAuthority.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedRootAuthority.md deleted file mode 100644 index 6a9c47ef10..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedRootAuthority.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptrustedrootauthority -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTrustedRootAuthority -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTrustedRootAuthority - -## SYNOPSIS -Creates a new trusted root authority. - - -## SYNTAX - -### ManualUpdateCertificateParameterSet -``` -Set-SPTrustedRootAuthority [-Identity] <SPTrustedRootAuthorityPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Certificate <X509Certificate2>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -Set-SPTrustedRootAuthority [-Identity] <SPTrustedRootAuthorityPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-MetadataEndPoint <Uri>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPTrustedRootAuthority` cmdlet creates a new trusted root authority. -If a certificate file is used, the certificate must be an X509 certificate without private keys, otherwise an exception is raised. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -C:\PS>$cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 -$cert.Import('C:\LiveIDSigningCert.pfx') -Get-SPTrustedRootAuthority -Name "WFEFarm1" | Set-SPTrustedRootAuthority -Certificate $cert -``` - -This example updates the certificate of the trusted root authority WFEFarm1. - - -## PARAMETERS - -### -Identity -Specifies the trusted root authority to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a trusted root authority (for example, WFEFarm1); or an instance of a valid SPTrustedRootAuthority object. - -```yaml -Type: SPTrustedRootAuthorityPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Certificate -Specifies the X.509 certificate of the trusted root authority. - -The type must be a name of a valid X.509 certificate; for example, Certificate1. - -```yaml -Type: X509Certificate2 -Parameter Sets: ManualUpdateCertificateParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -{{Fill MetadataEndPoint Description}} - -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedSecurityTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedSecurityTokenIssuer.md deleted file mode 100644 index 9332b93703..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedSecurityTokenIssuer.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptrustedsecuritytokenissuer -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTrustedSecurityTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTrustedSecurityTokenIssuer - -## SYNOPSIS -Sets the trusted token issuer. - - -## SYNTAX - -### ImportCertificateParameterSet -``` -Set-SPTrustedSecurityTokenIssuer [-Identity] <SPTrustedSecurityTokenServicePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Certificate <X509Certificate2>] [-Confirm] - [-Description <String>] [-IsTrustBroker] [-RegisteredIssuerName <String>] [-WhatIf] [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -Set-SPTrustedSecurityTokenIssuer [-Identity] <SPTrustedSecurityTokenServicePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Description <String>] [-IsTrustBroker] - [-MetadataEndPoint <Uri>] [-RegisteredIssuerName <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Set-SPTrustedSecurityTokenIssuer` cmdlet to set the trusted token issuer. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE-------------------- -``` -C:\PS>$a=Get-SPTrustedSecurityTokenIssuer - -Set-SPTrustedSecurityTokenIssuer -Identity $a -MetadataEndpoint https://<webappurl/>/_layouts/15/metadata/json/1/ -``` - -This example sets the metadata endpoint of the url for the self-issue. - - -## PARAMETERS - -### -Identity -Specifies the id of the SPTrustedSecurityTokenIssuer object to be set. - -```yaml -Type: SPTrustedSecurityTokenServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Certificate -Specifies the X509Certificate object that represents the public key of the signing certificate of the security token issuer. - -```yaml -Type: X509Certificate2 -Parameter Sets: ImportCertificateParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the issuer. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsTrustBroker -Specifies whether the trust is established with a self-issuer partner app (that is, Exchange Server or Lync). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -Specifies the URI for the metadata endpoint of the issuer. - -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegisteredIssuerName -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPTrustedSecurityTokenIssuer](Get-SPTrustedSecurityTokenIssuer.md) - -[New-SPTrustedSecurityTokenIssuer](New-SPTrustedSecurityTokenIssuer.md) - -[Remove-SPTrustedSecurityTokenIssuer](Remove-SPTrustedSecurityTokenIssuer.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedServiceTokenIssuer.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedServiceTokenIssuer.md deleted file mode 100644 index 3e9b9e3aa2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPTrustedServiceTokenIssuer.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-sptrustedservicetokenissuer -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPTrustedServiceTokenIssuer -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPTrustedServiceTokenIssuer - -## SYNOPSIS -Updates a trust with the farm. - - -## SYNTAX - -### ImportCertificateParameterSet -``` -Set-SPTrustedServiceTokenIssuer [-Identity] <SPTrustedServiceTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Certificate <X509Certificate2>] [-Description <String>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -### MetadataEndPointParameterSet -``` -Set-SPTrustedServiceTokenIssuer [-Identity] <SPTrustedServiceTokenIssuerPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Description <String>] [-Confirm] [-MetadataEndPoint <Uri>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPTrustedServiceTokenIssuer` cmdlet updates a trust with a SharePoint farm. -If a certificate file is used, it must have only one X509 certificate without private keys, otherwise an exception is raised. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -C:\PS>$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx -Set-SPTrustedServiceTokenIssuer "WFEFarm1" - Description "WFE Farm 1" - ImportTrustCertificate $cert -``` - -This example updates a SharePoint Farm trust using the trust certificate from a file. - - -### ------------------EXAMPLE 2------------------ -``` -Set-SPTrustedServiceTokenIssuer "WFEFarm1" - Description "WFE Farm 1" -FederationMetadataUrl "https://liveid.com/STS/2007/03/fedmetadata.xml" -``` - -This example updates a SharePoint farm trust using the trust certificate from the federation metadata endpoint URL. - - -## PARAMETERS - -### -Identity -Specifies the trusted service token issuer to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a trusted service token issuer (for example, WFEFarm1); or an instance of a valid SPTrustedRootAuthority object. - -```yaml -Type: SPTrustedServiceTokenIssuerPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Certificate -Specifies the X.509 certificate object from trusted authentication provider farm. - -The type must be a name of a valid X.509 certificate; for example, Certificate1. - -```yaml -Type: X509Certificate2 -Parameter Sets: ImportCertificateParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a description for the trust. - -The type must be a valid string; for example, WFE Farm Trust1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MetadataEndPoint -{{Fill MetadataEndPoint Description}} - -```yaml -Type: Uri -Parameter Sets: MetadataEndPointParameterSet -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageApplication.md deleted file mode 100644 index 4969074502..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageApplication.md +++ /dev/null @@ -1,253 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spusageapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPUsageApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPUsageApplication - -## SYNOPSIS -Sets properties of a usage application. - - -## SYNTAX - -``` -Set-SPUsageApplication [-Identity] <SPUsageApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseName <String>] - [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-EnableLogging] - [-FailoverDatabaseServer <String>] [-UsageService <SPUsageServicePipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPUsageApplication` cmdlet sets properties of a usage application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE---------------------- -``` -Set-SPUsageApplication -Identity "Usage and Health data collection" -DatabaseServer "Server Name" -DatabaseName "New Logging DB" -``` - -This example changes the database server and database name used by the usage logging service to store logging data. - - -## PARAMETERS - -### -Identity -Specifies the usage application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a usage application (for example; UsageApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPUsageApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the logging database. - -The type must be a valid name of a SQL Server database; for example, UsageLogDB1. - -If the logging database does not exist, a logging database will be automatically created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabasePassword -Specifies the password for the user specified in DatabaseUserName. -Use this parameter only if SQL Server Authentication is used to access the logging database. - -The type must be a valid password. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the database specified in DatabaseName. - -The type must be a valid SQL Server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseUsername -Specifies the user name to use for connecting to the logging database. -Use this parameter only if SQL Server Authentication is used to access the logging database. - -The type must be a valid user name; for example, UserName1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableLogging -Specifies that this usage application collects usage data. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverDatabaseServer -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsageService -Specifies the SPUsageService object that is the parent of the usage application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage service (for example, UsageService1); or an instance of a valid SPUsageService object. - -```yaml -Type: SPUsageServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageDefinition.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageDefinition.md deleted file mode 100644 index 529565a84e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageDefinition.md +++ /dev/null @@ -1,211 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spusagedefinition -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPUsageDefinition -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPUsageDefinition - -## SYNOPSIS -Sets the retention period for a usage provider. - - -## SYNTAX - -``` -Set-SPUsageDefinition [-Identity] <SPUsageDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DaysRetained <Int32>] [-DaysToKeepUsageFiles <Int32>] [-Enable] [-MaxTotalSizeInBytes <Int64>] - [-WhatIf] [-UsageDatabaseEnabled] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPUsageDefinition` cmdlet sets the retention period for a specified usage provider. -A usage definition object defines a specific type of usage provider. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE-------------------- -``` -Set-SPUsageDefinition -Identity "Page Requests" -DaysRetained 31 -``` - -This example sets the number of days that stores page requests usage data to 31. - - -## PARAMETERS - -### -Identity -Specifies the usage definition object to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage definition (for example, SiteSubscriptionConfig1); or an instance of a valid SPUsageDefinition object. - -```yaml -Type: SPUsageDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DaysRetained -Specifies the number of days that usage data for the usage provider is retained in the usage service database. -The default value is 14. - -The type must be an integer between 0 and 31. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DaysToKeepUsageFiles -Specifies the number of days to keep usage file retention. -The value must be less than or equal to value of the DaysRetained parameter. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enable -Turns on the specified usage provider. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxTotalSizeInBytes -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsageDatabaseEnabled -{{Fill UsageDatabaseEnabled Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageService.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageService.md deleted file mode 100644 index 90dae5d7f7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUsageService.md +++ /dev/null @@ -1,227 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spusageservice -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPUsageService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPUsageService - -## SYNOPSIS -Updates the properties of a usage service. - - -## SYNTAX - -``` -Set-SPUsageService [[-Identity] <SPUsageServicePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-LoggingEnabled <Boolean>] [-UsageLogCutTime <UInt32>] [-UsageLogLocation <String>] - [-UsageLogMaxFileSizeKB <UInt32>] [-UsageLogMaxSpaceGB <UInt32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPUsageService` cmdlet updates the properties of a usage service. -If the Identity parameter is not specified, the cmdlet applies the changes to the local usage service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------------EXAMPLE----------------- -``` -Set-SPUsageService -LoggingEnabled $false - -Set-SPUsageService -UsageLogLocation "D:\\testusagelogdir" - - -Set-SPUsageService -UsageLogCutTime 5 -``` - -The examples disables usage logging, changes the directory where usage files are stored and creates a new usage log file every 5 minutes. - - -## PARAMETERS - -### -Identity -Specifies the usage service to update. - -The type must be in one of the following forms: - ---A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh ---A valid name of a usage service (for example, UsageService1) ---An instance of a valid SPUsageService object. - -```yaml -Type: SPUsageServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LoggingEnabled -Specifies that usage data is logged to usage files. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UsageLogCutTime -Specifies the time, in minutes, of usage data that is collected per usage log file. -The default time is 5 minutes. - -The value must be an integer in the range of 1 to 1440. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -UsageLogLocation -Specifies the path on every computer in the farm where usage log files are created. - -The value must be a valid local path in the following form: - -- C:\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -UsageLogMaxFileSizeKB -Specifies the maximum size of a single usage file that is applied to all the usage providers. - -The minimum value is 512 kilobytes (KB) and the maximum value is 65536 KB. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -UsageLogMaxSpaceGB -The parameter is not used in SharePoint Server. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUser.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUser.md deleted file mode 100644 index c5b822a966..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPUser.md +++ /dev/null @@ -1,325 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spuser -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPUser -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPUser - -## SYNOPSIS -Configures properties of an existing user. - - -## SYNTAX - -``` -Set-SPUser [-Identity] <SPUserPipeBind> [-AddPermissionLevel <String[]>] - [-AssignmentCollection <SPAssignmentCollection>] [-ClearPermissions] [-Confirm] [-DisplayName <String>] - [-Email <String>] [-Group <SPGroupPipeBind>] [-IsSiteCollectionAdmin] [-PassThru] - [-RemovePermissionLevel <String[]>] [-SyncFromAD] [-Web <SPWebPipeBind>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPUser` cmdlet configures properties of an existing user. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Set-SPUser -Identity 'Contoso\jdoe' -Web https://intranet.contoso.com -AddPermissionLevel "Contributor" -``` - -This example sets a user (Contoso\jdoe) to be a contributor on https://intranet.contoso.com. - - -### ------------------EXAMPLE 2----------------------- -``` -Set-SPUser -Identity 'Contoso\jdoe' -Web https://intranet.contoso.com -SyncFromAD -``` - -This updates the User Information List for the user 'contoso\jdoe' with the current `displayName` and `mail` attribute values from the user's Active Directory account. - -## PARAMETERS - -### -Identity -Specifies the GUID, login name, or SPUser object of the user to be returned. - -The type must be a GUID of an existing user in the form, 1234-5678-9876-0987. - -```yaml -Type: SPUserPipeBind -Parameter Sets: (All) -Aliases: UserAlias -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AddPermissionLevel -Specifies the permission level to add to the user. - -The value must be one of the following options: - ---Contribute - -Can view, add, update and delete list items and documents. - ---Design - -Can view, add, update, delete, approve and customize documents. - ---Full Control - -Has full control for all documents. - ---Limited Access - -Can view specific lists, document libraries, list items, folders, or documents when permissions are granted. - ---Read - -Can view pages and list items and download documents. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClearPermissions -Deletes all assigned permissions from the user. -If Clear and Add values exist, permissions are first cleared and then new permissions are added. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -Specifies the new display name of the user. - -The type must be a valid name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Email -Specifies the new email address of the user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Group -Adds the user to an existing group in the given site. - -```yaml -Type: SPGroupPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsSiteCollectionAdmin -Specifies whether to set the user as a site collection administrator. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -If not provided, indicates that this cmdlet has no output. -If provided, this parameter indicates that the SPUser object for this user is to be returned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemovePermissionLevel -Removes the permission level from the user. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SyncFromAD -If provided, specifies that user information will be synchronized from the user directory store. This switch only retrieves the `displayName` and `mail` value from the directory store. It supports Active Directory (Classic or Windows authentication), Forms-based Authentication, and SAML. FBA and SAML providers must support resolving from their directory store for this switch to work. The switch only supports SharePoint User objects. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Web -Specifies the name of the URL or GUID to be used as a scope. -This parameter is not needed if the SPUser object is provided as the identity. - -The value must be an authentic URL, in the form https://server_name, or GUID, in the form 1234-5678-9807. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioExternalData.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioExternalData.md deleted file mode 100644 index a44646e40e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioExternalData.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spvisioexternaldata -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPVisioExternalData -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPVisioExternalData - -## SYNOPSIS -Configures settings related to external data connections for a Visio Services application. - -## SYNTAX - -``` -Set-SPVisioExternalData -UnattendedServiceAccountApplicationID <String> - -VisioServiceApplication <SPVisioServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPVisioExternalData` cmdlet sets and configures settings for external data connections for the Visio Services application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------------EXAMPLE----------------------- -``` -Set-SPVisioExternalData -VisioServiceApplication "VGS1" -UnattendedServiceAccountApplicationID "SSSApp1" -``` - -This example sets the unattended service account application ID to SSSApp1 for the Visio Services application named VGS1. - - -## PARAMETERS - -### -UnattendedServiceAccountApplicationID -Specifies the target application ID in the registered secure store service that is used to reference unattended service account credentials. -The unattended service account is a single account that all documents can use to refresh data. -It is required when connecting to external data sources. - -The type must be a valid value less than or equal to 256 characters. -The application ID must be registered in the secure store service application or an error message will be displayed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VisioServiceApplication -Specifies the Visio Services application that contains the SPVisioExternalData object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioPerformance.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioPerformance.md deleted file mode 100644 index 6dff70ade7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioPerformance.md +++ /dev/null @@ -1,203 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spvisioperformance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPVisioPerformance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPVisioPerformance - -## SYNOPSIS -Sets performance properties for a Visio Services application. - - -## SYNTAX - -``` -Set-SPVisioPerformance -MaxDiagramCacheAge <Int32> -MaxDiagramSize <Int64> -MaxRecalcDuration <Int32> - -MinDiagramCacheAge <Int32> -VisioServiceApplication <SPVisioServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] -MaxCacheSize <Int64> [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPVisioPerformance` cmdlet sets properties related to performance for a Visio Services application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE 1---------------------- -``` -Set-SPVisioPerformance -VisioServiceApplication "VGS2" -MaxDiagramSize 10 -MaxRecalcDuration 120 -MinDiagramCacheAge 1 -MaxDiagramCacheAge 4 -``` - -This example changes settings that are related to performance for a Visio Services application. - - -### -------------------EXAMPLE 2---------------------- -``` -Set-SPVisioPerformance -VisioServiceApplication "VGS2" -MaxDiagramSize 10 -``` - -This example changes settings that are related to performance for a Visio Services application. -Note that only one setting value is specified. -The cmdlet prompts you for the other parameter values. - - -## PARAMETERS - -### -MaxDiagramCacheAge -Specifies the time, in minutes, after which cached items are purged. -This value affects memory use on the server. -A large cache age slows the rate at which diagrams can be refreshed by users and reduces CPU and memory use of the server. -The default value is 60 minutes. - -The type must be an integer in the range of 0 to 34560 (24 days). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxDiagramSize -Specifies the maximum size, in megabytes, of a diagram that can be opened by the Visio Services application. -The default value is 5. - -The type must be an integer in the range of 1 to 50. - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxRecalcDuration -Specifies the maximum time, in seconds, that a diagram can only be recalculated by the Visio Services application. -Diagram recalculation operations that take longer than this number of seconds are canceled by the service. -A low value increases performance by allowing only simple diagrams to be processed by the server, which minimizes CPU and memory use. -A larger value allows the recalculation of more complex diagrams while using more CPU cycles and memory. - -The type must be a valid integer value in the range of 1 to 120 seconds (2 minutes). -The default value is 60 seconds. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MinDiagramCacheAge -Specifies the minimum time, in minutes, a diagram is cached in memory. -This value affects memory use on the server. -A small value allows users to refresh their diagrams more often, but will increase memory and CPU load of the server. -The default value is 5. - -The type must be an integer in the range of 0 to 34560 (24 days). - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VisioServiceApplication -Specifies the Visio Services application that contains the SPVisioPerformance object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MaxCacheSize -{{Fill MaxCacheSize Description}} - -```yaml -Type: Int64 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioSafeDataProvider.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioSafeDataProvider.md deleted file mode 100644 index ef43c46f20..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioSafeDataProvider.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spvisiosafedataprovider -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPVisioSafeDataProvider -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPVisioSafeDataProvider - -## SYNOPSIS -Specifies a description of a safe data provider for a Visio Services application. - -## SYNTAX - -``` -Set-SPVisioSafeDataProvider -DataProviderId <String> -DataProviderType <Int32> -Description <String> - -VisioServiceApplication <SPVisioServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPVisioSafeDataProvider` cmdlet sets the Description property of a safe data provider for a Visio Services application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------------EXAMPLE 1---------------------- -``` -Set-SPVisioSafeDataProvider -VisioServiceApplication "VGS1" -DataProviderID "SQLOLEDB" -DataProviderType 1 -Description "SQL OLEDB Driver!" -``` - -This example sets the description property of a safe data provider for a specific Visio Services application. - - -### -------------------EXAMPLE 2---------------------- -``` -Get-SPVisioServiceApplication -Identity "VGS1" | Set-SPVisioSafeDataProvider -DataProviderID "SQLOLEDB" -DataProviderType 1 -Description "SQL OLEDB Driver!" -``` - -This example sets the Description property of a safe data provider for a specific Visio Services application. -The result is piped from the `Set-SPVisioSafeDataProvider` cmdlet. - - -## PARAMETERS - -### -DataProviderId -Specifies the name of the data provider to update. -The combination of DataProviderID and DataProviderType uniquely identifies a data provider for a Visio Services application. -The string that identifies the data provider can be a maximum of 255 alphanumeric characters. -Custom data types are supported; for example, Excel Services. - -The type must be a valid string that identifies the data provider. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DataProviderType -Specifies the supported type of the data provider to get. -Custom data types are supported; for example, Excel services. - -The type must be a valid identity of a data provider type. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the description of the safe data provider to set. - -The type must be a string with a maximum of 4096 characters. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VisioServiceApplication -Specifies the Visio Services application that contains the SPVisioSafeDataProvider object. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioServiceApplication.md deleted file mode 100644 index 7727c53016..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPVisioServiceApplication.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.Office.Visio.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spvisioserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPVisioServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPVisioServiceApplication - -## SYNOPSIS -Sets the ServiceApplicationPool property for a Visio Services application. - -## SYNTAX - -``` -Set-SPVisioServiceApplication [-Identity] <SPVisioServiceApplicationPipeBind> - [-ServiceApplicationPool] <SPIisWebServiceApplicationPoolPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPVisioServiceApplication` cmdlet sets the ServiceApplicationPool property for a Visio Services application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------------EXAMPLE 1---------------------- -``` -Set-SPVisioServiceApplication -identity "VGS1" -ServiceApplicationPool "SharePoint Web Services System Default" -``` - -This example changes the application pool of the VGS1 service application. - - -### -----------------EXAMPLE 2---------------------- -``` -Get-SPServiceApplicationPool "SharePoint Web Services Default" | Set-SPVisioServiceApplication VGS1 -``` - -This example changes the application pool of the VGS1 service application. -The results are piped from the `Get-SPServiceApplicationPool` cmdlet. - - -## PARAMETERS - -### -Identity -Specifies the Visio Services application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication object. - -```yaml -Type: SPVisioServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServiceApplicationPool -Specifies the IIS application pool to change. -The Web service for the service application runs in the specified application pool. - -The type must be a valid name of a Visio Service application pool, such as MyVisioServiceAppPool1; or a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid SPIisWebServiceApplicationPoolPipeBind object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWOPIBinding.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWOPIBinding.md deleted file mode 100644 index 86dceff3dd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWOPIBinding.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spwopibinding -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPWOPIBinding -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWOPIBinding - -## SYNOPSIS -Updates the default click action for an application or file name extension binding. - - -## SYNTAX - -``` -Set-SPWOPIBinding [-Identity] <SPWopiBindingPipeBind> [-DefaultAction] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPWOPIBinding` cmdlet updates the default click action for an application or file name extension binding. -For example, you can set the default click action to view for a Word document in a SharePoint library. -To do this, you set the default action to true for the "view"-"Word" bindings. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` - Get-SPWOPIBinding -Action "view" -Application "Word"| Set-SPWOPIBinding -DefaultAction:$true -``` - -This example sets the default click action to view for a Word document in a SharePoint library. -You can verify that the default click action is set to view for Word by running the cmdlet `Get-SPWOPIBinding -Action "view" -Application "Word"`. -The IsDefaultAction value is set to "True." - - -## PARAMETERS - -### -Identity -Specifies the binding. - -```yaml -Type: SPWopiBindingPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DefaultAction -Specifies whether the binding should be set as the default click action for an application or file name extension in the binding. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters`. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters`. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[Get-SPWOPIBinding](Get-SPWOPIBinding.md) - -[Remove-SPWOPIBinding](Remove-SPWOPIBinding.md) - -[New-SPWOPIBinding](New-SPWOPIBinding.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWOPIZone.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWOPIZone.md deleted file mode 100644 index 9b31d283a2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWOPIZone.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spwopizone -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPWOPIZone -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWOPIZone - -## SYNOPSIS -Configures the zone that the current SharePoint farm will use to navigate the browser to the WOPI application. - - -## SYNTAX - -``` -Set-SPWOPIZone [[-Zone] <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPWOPIZone` cmdlet configures the zone that the current SharePoint farm will use to navigate the browser to the WOPI application (such as a server that runs Office Web Apps Server). -The SharePoint Server page in the browser creates a frame that contains a page on the WOPI application. -The zone for the URL of the WOPI application page is determined by this setting. - -If you do not set the zone, the default is "internal-HTTPS." If you select a zone that is not supported by the WOPI application, Office Web Apps will not work. -Only use HTTP when you are on a fully secure network that uses IPSEC (full encryption) or in a test environment that does not contain sensitive data. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Set-SPWOPIZone -Zone "external-https" -``` - -This example configures the current SharePoint farm to use external connections through HTTPS to the WOPI application (such as a server that runs Office Web Apps Server). - - -## PARAMETERS - -### -Zone -Specifies the zone. -For a list of zones that the WOPI application supports, run `Get-SPWOPIBinding`. - -If you have a SharePoint farm that's internal and external, specify external. -If you have a SharePoint farm that's internal only, specify internal. -Only use HTTP when you are on a fully secure network that uses IPSEC (full encryption) or in a test environment that does not contain sensitive data. -The options are as follows: - -- Internal-HTTP -- Internal-HTTPS -- External-HTTP -- External-HTTPS - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters`. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters`. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() - -[Get-SPWOPIZone](Get-SPWOPIZone.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWeb.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWeb.md deleted file mode 100644 index 2eb0e94193..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWeb.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spweb -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPWeb -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWeb - -## SYNOPSIS -Configures the specified subsite. - - -## SYNTAX - -``` -Set-SPWeb [-Identity] <SPWebPipeBind> [-Description <String>] [-RelativeUrl <String>] [-Theme <String>] - [-Template <SPWebTemplatePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPWeb` cmdlet configures the subsite specified by the Identity parameter. -Settings for any parameters that are not provided are not changed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Get-SPWeb https://sitename/subweb | Set-SPWeb -Description "My Site Description" -``` - -This example sets the description of an existing subsite. - - -## PARAMETERS - -### -Identity -The URL of the Web or SPWeb object that represents the Web. - -The type must be a valid URL, in the form https://server_name, or an SPWeb object. - -```yaml -Type: SPWebPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Description -Specifies the new description of the Web. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RelativeUrl -Specifies the new relative URL for the Web. -This is the URL path after the site collection URL. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Theme -Specifies the new theme to apply to the Web. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Template -Specifies the new template to apply to the Web. -This cannot be done if the template is already applied. - -```yaml -Type: SPWebTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplication.md deleted file mode 100644 index e36f736b80..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplication.md +++ /dev/null @@ -1,417 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spwebapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPWebApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWebApplication - -## SYNOPSIS -Configures the specified Web application. - - -## SYNTAX - -### UpdateMailSettings -``` -Set-SPWebApplication [-Identity] <SPWebApplicationPipeBind> [-OutgoingEmailAddress <String>] - [-ReplyToEmailAddress <String>] -SMTPServer <String> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Force] [-WhatIf] [-DisableSMTPEncryption] [-NotProvisionGlobally] [-SMTPServerPort <Int32>] - [<CommonParameters>] -``` - -### UpdateClaimSettings -``` -Set-SPWebApplication [-Identity] <SPWebApplicationPipeBind> -Zone <SPUrlZone> - [-AdditionalClaimProvider <SPClaimProviderPipeBind[]>] [-AssignmentCollection <SPAssignmentCollection>] - [-AuthenticationMethod <String>] [-AuthenticationProvider <SPAuthenticationProviderPipeBind[]>] [-Confirm] - [-Force] [-SignInRedirectProvider <SPTrustedIdentityTokenIssuerPipeBind>] [-SignInRedirectURL <String>] - [-WhatIf] [-NotProvisionGlobally] [<CommonParameters>] -``` - -### UpdateGeneralSettings -``` -Set-SPWebApplication [-Identity] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-DefaultQuotaTemplate <String>] [-DefaultTimeZone <Int32>] [-Force] - [-ServiceApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-WhatIf] [-NotProvisionGlobally] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Set-SPWebApplication` cmdlet configures the Web application specified by the Identity parameter. -For any settings that are zone-specific (for the Zone parameter set), the zone to configure must be provided. -The provided zone must already exist. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Get-SPWebApplication http://somesite | Set-SPWebApplication -Zone "Extranet" -HostHeader "http://www.contoso.com/" - AllowAnonymousAccess -``` - -This example sets the HostHeader URL for the Extranet zone of the given Web application as http://www.contoso.com and enables anonymous access. - - -## PARAMETERS - -### -Identity -Specifies the name or URL of the Web application. - -The type must be a valid name, in the form WebApplication-1212, or URL, in the form http://server_name/WebApplicaiton-1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -OutgoingEmailAddress -Specifies the new outgoing e-mail address for e-mail messages sent from this Web application. -The type must be a valid address; for example, someone@example.com. - -```yaml -Type: String -Parameter Sets: UpdateMailSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReplyToEmailAddress -Configures the reply e-mail address. - -The type must be a valid address; for example, someone@example.com. - -```yaml -Type: String -Parameter Sets: UpdateMailSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SMTPServer -Specifies the new outbound SMTP server that this Web application will use. - -```yaml -Type: String -Parameter Sets: UpdateMailSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Zone -When configuring zone-specific settings, the zone to configure must be specified. -This zone must already exist. - -The type must be any one of the following values: Default, Intranet, Internet, Extranet, or Custom. - -```yaml -Type: SPUrlZone -Parameter Sets: UpdateClaimSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AdditionalClaimProvider -Adds a specific claim provider to the defined Web application. - -```yaml -Type: SPClaimProviderPipeBind[] -Parameter Sets: UpdateClaimSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AuthenticationMethod -Use to set a Web application to classic Windows authentication. -The valid values are NTLM or Kerberos. - -```yaml -Type: String -Parameter Sets: UpdateClaimSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AuthenticationProvider -Defines the authentication provider(s) that applies to the Web application. - -```yaml -Type: SPAuthenticationProviderPipeBind[] -Parameter Sets: UpdateClaimSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultQuotaTemplate -Specifies the new default site quota template for this Web application. - -```yaml -Type: String -Parameter Sets: UpdateGeneralSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultTimeZone -Specifies the default time zone for new site collections in this Web application. - -```yaml -Type: Int32 -Parameter Sets: UpdateGeneralSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses confirmation messages involved in settings for a Web application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplicationProxyGroup -Specifies a custom service application proxy group for the Web application to use. -The Web application will use the proxies in this proxy group to connect to service applications. -If this parameter is not specified, the farm's default proxy group is used. - -```yaml -Type: SPServiceApplicationProxyGroupPipeBind -Parameter Sets: UpdateGeneralSettings -Aliases: ProxyGroup -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInRedirectProvider -Sets the sign-in redirect URL to point to the URL that is defined in the specified authentication provider. - -```yaml -Type: SPTrustedIdentityTokenIssuerPipeBind -Parameter Sets: UpdateClaimSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SignInRedirectURL -Specifies the sign-in redirect URL for the Web application. - -```yaml -Type: String -Parameter Sets: UpdateClaimSettings -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableSMTPEncryption -{{Fill DisableSMTPEncryption Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: UpdateMailSettings -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotProvisionGlobally -{{Fill NotProvisionGlobally Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SMTPServerPort -{{Fill SMTPServerPort Description}} - -```yaml -Type: Int32 -Parameter Sets: UpdateMailSettings -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplicationHttpThrottlingMonitor.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplicationHttpThrottlingMonitor.md deleted file mode 100644 index 259ea9bd65..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplicationHttpThrottlingMonitor.md +++ /dev/null @@ -1,263 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spwebapplicationhttpthrottlingmonitor -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPWebApplicationHttpThrottlingMonitor -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWebApplicationHttpThrottlingMonitor - -## SYNOPSIS -Sets the Health Score bucket values for an existing network throttling performance counter for a specified Web application. - - -## SYNTAX - -``` -Set-SPWebApplicationHttpThrottlingMonitor [-Identity] <SPWebApplicationPipeBind> [-Category] <String> - [-Counter] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-HealthScoreBuckets <Double[]>] [-Instance <String>] [-IsDESC] [-LowerLimit <Double>] [-UpperLimit <Double>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPWebApplicationHttpThrottlingMonitor` cmdlet sets the Health Score bucket values for an existing network throttling performance counter for a specified Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -C:\PS>$buckets=(2000,1000,500,300,200,100,50,30,20,10) -Set-SPWebApplicationHttpThrottlingMonitor https://sharepoint - -Category Memory -Counter 'Available Mbytes' -IsDesc -HealthScoreBuckets $buckets -``` - -This example sets the Health Score bucket values for the Memory\Available Mbytes counter to the array listed for the https://sharepoint Web application. - - -### ------------------EXAMPLE 2------------------ -``` -Set-SPWebApplicationHttpThrottlingMonitor https://sharepoint -0 -Category Memory -Counter 'Available Mbytes' -IsDesc -UpperLimit 3000 -``` - -This example sets the upper limit for the Memory\Available Mbytes counter, the highest value in the Health Score buckets, to 3000 for the https://sharepoint Web application. - - -## PARAMETERS - -### -Identity -Specifies the SharePoint Web application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Category -Specifies the name of the performance counter category. - -The type must be a valid performance counter category in the throttling monitor. -Use the `Get-SPWebApplicationHttpThrottlingMonitor` cmdlet to return a list of performance counter categories in the throttling monitor. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Counter -Specifies the name of the performance counter. - -The type must be a valid performance counter in the throttling monitor. -Use the `Get-SPWebApplicationHttpThrottlingMonitor` cmdlet to return a list of performance counters in the throttling monitor. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 3 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HealthScoreBuckets -Specifies bucket ranges to use in determining the calculation of the server Health Score for this counter. - -```yaml -Type: Double[] -Parameter Sets: (All) -Aliases: Buckets -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Instance -Specifies the instance of the performance counter. -The default value is empty. -If the specified value is invalid, this cmdlet will not run. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -IsDESC -Specifies that this counter is interpreted in descending order. - -If this parameter is set, Health Score bucket values are interpreted in descending order; for example, set this parameter by using the Memory category and Available Mbytes counter to monitor available memory. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -LowerLimit -Specifies the lower limit of the numerical threshold of the specified performance counter. -The lower limit is the lowest value in the Health Score bucket values. - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: Lower -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -UpperLimit -Specifies the upper limit of the numerical threshold of the specified performance counter. -The upper limit is the highest value in the Health Score bucket values. - -```yaml -Type: Double -Parameter Sets: (All) -Aliases: Upper -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWordConversionServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWordConversionServiceApplication.md deleted file mode 100644 index f5204c8c39..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWordConversionServiceApplication.md +++ /dev/null @@ -1,495 +0,0 @@ ---- -external help file: Microsoft.Office.Word.Server.dll-Help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spwordconversionserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPWordConversionServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWordConversionServiceApplication - -## SYNOPSIS -Sets properties of a Word Automation Services application. - -## SYNTAX - -``` -Set-SPWordConversionServiceApplication [-Identity] <WordServiceApplicationPipeBind> [-ActiveProcesses <Int32>] - [-AddSupportedFormats <String[]>] [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-ClearSupportedFormats] [-Confirm] - [-ConversionsPerInstance <Int32>] [-ConversionTimeout <Int32>] [-DatabaseCredential <PSCredential>] - [-DatabaseName <String>] [-DatabaseServer <String>] [-DisableBinaryFileScan] [-DisableEmbeddedFonts] - [-KeepAliveTimeout <Int32>] [-MaximumConversionAttempts <Int32>] [-MaximumConversionTime <Int32>] - [-MaximumMemoryUsage <Int32>] [-RecycleProcessThreshold <Int32>] [-RemoveSupportedFormats <String[]>] - [-TimerJobFrequency <Int32>] [-WhatIf] [-MaximumGroupSize <Int32>] [-MaximumSyncConversionRequests <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-SPWordConversionServiceApplication` cmdlet sets global properties of a Word Automation Services application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -----------EXAMPLE----------------- -``` -Get-SPServiceApplication -Name WordServices1 | Set-SPWordConversionServiceApplication -TimerJobFrequency 30 -``` - -This example sets the timer job frequency of the WordServices1 application to 30 minutes. - - -## PARAMETERS - -### -Identity -Specifies the Word Automation Services application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Word Automation Services application (for example, WordSvcApp1); or an instance of a valid SPServiceApplication object. - -```yaml -Type: WordServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -ActiveProcesses -Specifies the number of conversion processes on each machine on which the service application runs. -This value is equivalent to the number of simultaneous conversions. -The default value is 8. - -The type must be a valid integer in the range from 1 to 1000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AddSupportedFormats -Specifies a set of file formats to be enabled for use by the service application. - -The value must be a comma-delimited list of one or more of the following: docx, doc, mht, rtf, xml. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the existing IIS managed application pool in which this instance of Word Automation Services runs. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of an application pool (for example, AppPoolName1); or an instance of a valid IISWebServiceApplicationPool object. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ClearSupportedFormats -Specifies that all file formats should be disabled for use by the service application. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConversionsPerInstance -Specifies the number of items sent to each conversion process (see the ActiveProcesses parameter description earlier in this table) every time the timer job is run. -The default value is 12. - -The type must be a valid integer. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConversionTimeout -Specifies the time, in minutes, after which a conversion that is marked InProgress is confirmed to be still running each time the timer job runs and if necessary, the conversion is restarted. -The default value is 5. - -The type must be a valid integer in the range from 1 to 60. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseCredential -Specifies the credentials to use for connecting to the database for the Word Automation Services application. -Use this parameter only if SQL Authentication is used to access the service application database. - -When the DatabaseCredential parameter is specified, the DatabaseName and DatabaseServer parameters are required. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseName -Specifies the name of the database to use for this instance of the Word Automation Services application. - -The type must be a valid SQL database name; for example, MetadataDB1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseServer -Specifies the name of the host server for the Word Automation Services database. - -The type must be a valid SQL database server host name; for example, SQLServerHost1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableBinaryFileScan -Specifies whether additional checks are run when Word documents are processed. -Turn this setting off only if all documents processed by the service are trusted. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisableEmbeddedFonts -Specifies whether embedded fonts are ignored when present in input documents. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -KeepAliveTimeout -Specifies the length of time, in seconds, that a conversion can be non-responsive before it is terminated. -The default value is 30. - -The type must be a valid integer in the range from 10 to 60. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumConversionAttempts -The maximum number of conversion attempts before a conversion is marked with status "Failed". -The default value is 2. - -The type must be a valid integer in the range from 1 to 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumConversionTime -Specifies the maximum length of time, in seconds, that a conversion can run before it is terminated. -The default value is 300. - -The type must be a valid integer in the range from 60 to MaxInt. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumMemoryUsage -Specifies the maximum percentage of system memory which can be used by the service application. -The default value is 100. - -The type must be a valid integer in the range from 10 to 100. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RecycleProcessThreshold -Specifies the number of documents which are converted before a conversion process is recycled. -For additional information about the conversion process, see the ActiveProcess parameter description earlier in this table. - -The type must be a valid integer in the range from 1 to 1000. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveSupportedFormats -Specifies a set of file formats to be disabled for use by the service application. - -The value must be a comma delimited list of one or more of the following: docx, doc, mht, rtf, xml. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimerJobFrequency -Specifies the frequency, in minutes, with which the timer job for this service application runs. -The default value is 15. - -The type must be a valid integer in the range from 1 to 59. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumGroupSize -{{Fill MaximumGroupSize Description}} - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumSyncConversionRequests -{{Fill MaximumSyncConversionRequests Description}} - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkManagementServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkManagementServiceApplication.md deleted file mode 100644 index ae1de443ba..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkManagementServiceApplication.md +++ /dev/null @@ -1,269 +0,0 @@ ---- -external help file: Microsoft.Office.Server.WorkManagement.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spworkmanagementserviceapplication -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Set-SPWorkManagementServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWorkManagementServiceApplication - -## SYNOPSIS -Sets settings for the Work Management Service application. - -## SYNTAX - -``` -Set-SPWorkManagementServiceApplication [-Identity] <SPWorkManagementServiceCmdletPipeBind> - [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-MinimumTimeBetweenProviderRefreshes <TimeSpan>] [-MinimumTimeBetweenSearchQueries <TimeSpan>] - [-Name <String>] [-WhatIf] [-MinimumTimeBetweenEwsSyncSubscriptionSearches <TimeSpan>] - [-NumberOfSubscriptionSyncsPerEwsSyncRun <UInt32>] [-NumberOfUsersEwsSyncWillProcessAtOnce <UInt32>] - [-NumberOfUsersPerEwsSyncBatch <UInt32>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPWorkManagementServiceApplication` cmdlet to set settings (that is, minimum time between refreshes for aggregating tasks and load per machine for synchronization with Exchange) for the specified Work Management Service Application by using the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE--------------- -``` -C:\PS>$wmservice = Get-SPServiceApplication -Name "Work Management Service Application" - -C:\PS>$refreshTime = New-Timespan -Minutes 10 - -Set-SPWorkManagementServiceApplication -Identity $wmservice -MinimumTimeBetweenProviderRefreshes $refreshTime -``` - -This example sets the minimum time between provider refreshes to 10 minutes on the service application named "Work Management Service Application". - -## PARAMETERS - -### -Identity -Specifies the service application to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubSettingsApp1); or an instance of a valid SPWorkManagementServiceApplication object - -```yaml -Type: SPWorkManagementServiceCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ApplicationPool -Specifies the name of an application pool to use; for example, SharePoint - 1213. -If no value is specified, the default application pool is used. - -```yaml -Type: SPIisWebServiceApplicationPoolPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MinimumTimeBetweenProviderRefreshes -Specifies the minimum amount of time between cache update operations per user. -If this time has not passed since the last successful refresh request for a user, the service application does not execute new refresh requests. - -```yaml -Type: TimeSpan -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MinimumTimeBetweenSearchQueries -Specifies the minimum amount of time between calls to the Search Service application to discover new SharePoint task lists where a user has tasks. -If this time has not passed since the last successful call to Search for a user, the service application does not call Search during refresh operations. - -```yaml -Type: TimeSpan -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of the Work Management Service application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MinimumTimeBetweenEwsSyncSubscriptionSearches -This value specifies the minimum amount of time between calls into our routine that tries to find new tenants that want to sync EWS tasks. - -```yaml -Type: TimeSpan -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberOfSubscriptionSyncsPerEwsSyncRun -This value specifies the maximum number of tenants the service will try to sync via EWS per Timer job interval - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberOfUsersEwsSyncWillProcessAtOnce -This value specifies the maximum number of users a service instance machine will sync via EWS at one time across all tenants. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberOfUsersPerEwsSyncBatch -This value specifies the maximum number of users a service instance will try to sync on a given tenant via EWS per Timer job interval - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPWorkManagementServiceApplication](New-SPWorkManagementServiceApplication.md) - -[New-SPWorkManagementServiceApplicationProxy](New-SPWorkManagementServiceApplicationProxy.md) - -[Set-SPWorkManagementServiceApplicationProxy](Set-SPWorkManagementServiceApplicationProxy.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkManagementServiceApplicationProxy.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkManagementServiceApplicationProxy.md deleted file mode 100644 index d8fcaf66ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkManagementServiceApplicationProxy.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Office.Server.WorkManagement.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spworkmanagementserviceapplicationproxy -applicable: SharePoint Server 2013, SharePoint Server 2016 -title: Set-SPWorkManagementServiceApplicationProxy -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWorkManagementServiceApplicationProxy - -## SYNOPSIS -Sets the settings for the Work Management Service application proxy. - -## SYNTAX - -``` -Set-SPWorkManagementServiceApplicationProxy [-Identity] <SPWorkManagementServiceProxyCmdletPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DefaultProxyGroup] [-Name <String>] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Set-SPWorkManagementServiceApplicationProxy` cmdlet to set the settings for the Work Management service application proxy. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE-------- -``` -Set-SPWorkManagementServiceApplicationProxy -Identity "9187d901-e0e0-4509-b117-9eca20d3ead5" -DefaultProxyGroup -``` - -This example makes the Work Management service part of the default proxy group. - - -## PARAMETERS - -### -Identity -Specifies the service application proxy to update. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a subscription settings service application (for example, SubSettingsApp1); or an instance of a valid SPWorkManagementServiceApplicationProxy object - -```yaml -Type: SPWorkManagementServiceProxyCmdletPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultProxyGroup -Specifies whether the Work Management Service application proxy is to the default proxy group for the local farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the display name for the new Work Management Service application. -For example, WorkManService1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[New-SPWorkManagementServiceApplication](New-SPWorkManagementServiceApplication.md) - -[New-SPWorkManagementServiceApplicationProxy](New-SPWorkManagementServiceApplicationProxy.md) - -[Set-SPWorkManagementServiceApplication](Set-SPWorkManagementServiceApplication.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkflowConfig.md b/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkflowConfig.md deleted file mode 100644 index c323a1b64d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Set-SPWorkflowConfig.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/set-spworkflowconfig -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Set-SPWorkflowConfig -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Set-SPWorkflowConfig - -## SYNOPSIS -Configures the workflow settings for the specified Web application. - - -## SYNTAX - -### SiteCollection -``` -Set-SPWorkflowConfig [-SiteCollection] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-DeclarativeWorkflowsEnabled <Boolean>] [-EmailNoPermissionParticipantsEnabled <Boolean>] - [-SendDocumentToExternalParticipants <Boolean>] [-SingleWorkflowEpisodeTimeout <Int32>] [<CommonParameters>] -``` - -### WebApplication -``` -Set-SPWorkflowConfig [-WebApplication] <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-DeclarativeWorkflowsEnabled <Boolean>] - [-EmailNoPermissionParticipantsEnabled <Boolean>] [-SendDocumentToExternalParticipants <Boolean>] - [-SingleWorkflowEpisodeTimeout <Int32>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Set-SPWorkflowConfig` cmdlet to configure the workflow settings for the specified Web application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Set-SPWorkflowConfig -webapplication https://sitename DeclarativeWorkflowsEnabled $true -EmailNoPermissionParticipantsEnabled $true -SendDocumentToExternalParticipants $false -``` - -This example sets the workflow settings for the specified Web application to turn on declarative workflows, turn on e-mail to participants who do not have permissions to the site and turn off the functionality to send e-mail messages as attachments to external participants. - -No return values. -Use the `Get-SPWorkflowConfig` cmdlet to see values. -To set farm-level workflow settings for event-delivery time-out and to postpone threshold and batch size, use `Set-SPFarmConfig`. - - -## PARAMETERS - -### -SiteCollection -Specifies the name or URL of the site collection. - -The only other parameter that is used with the SiteCollection parameter is the DeclarativeWorkflowsEnabled parameter. -No other parameters are used. - -```yaml -Type: SPSitePipeBind -Parameter Sets: SiteCollection -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the name or URL of the Web application. - -The type must be a valid name or GUID, in the form WebApplication-1212, or a URL, in the form https://server_name/WebApplication-1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DeclarativeWorkflowsEnabled -Sets whether declarative workflows are allowed to run in the Web application. - -The type must be either 1 for True or 0 for False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailNoPermissionParticipantsEnabled -Sets whether workflows send task e-mail messages to users who do not have permissions to the site in which the workflows are running. - -The type must be either 1 for True or 0 for False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendDocumentToExternalParticipants -Sets whether workflows automatically send a copy of the document as an e-mail attachment to participants who do not have access to the site or who are not in any linked directory other than Active Directory Domain Services (AD DS). - -The type must be either 1 for True or 0 for False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SingleWorkflowEpisodeTimeout -{{Fill SingleWorkflowEpisodeTimeout Description}} - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Split-SPScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Split-SPScaleOutDatabase.md deleted file mode 100644 index 9cd00c4299..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Split-SPScaleOutDatabase.md +++ /dev/null @@ -1,294 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/split-spscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Split-SPScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Split-SPScaleOutDatabase - -## SYNOPSIS -Moves a specified percentage of partitions from one scale-out database to another. - - -## SYNTAX - -### NewDatabase -``` -Split-SPScaleOutDatabase -NewDatabaseName <String> -SourceDatabase <SPDatabasePipeBind> - -SourceServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-MoveLowerHalf] [-NewDatabaseCredentials <PSCredential>] [-NewDatabaseFailoverServer <String>] - [-NewDatabaseServer <String>] [-SourcePercentage <Int32>] [-WhatIf] [<CommonParameters>] -``` - -### ExistingDatabase -``` -Split-SPScaleOutDatabase -SourceDatabase <SPDatabasePipeBind> - -SourceServiceApplication <SPServiceApplicationPipeBind> -TargetDatabase <SPDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-MoveLowerHalf] [-SourcePercentage <Int32>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Split-SPScaleOutDatabase` cmdlet to move a specified percentage of partitions from a source database to an existing target database or to a new database that you create with the specified parameters. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE 1--------------- -``` -$databases = Get-SPScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -Split-SPScaleOutDatabase -NewDatabaseName Database2 -NewDatabaseServer MyDatabaseServer -SourceDatabase $database -SourceServiceApplication $serviceApplication -SourcePercentage 30 -``` - -This example creates a new scale-out database named Database2 on the MyDatabaseServer database server in the given service application. - -The example also moves 30% of the data from the upper side of the data range in the first scale-out database of the given service application. - -### ---------------EXAMPLE 2--------------- - -``` -$ssa = Get-SPEnterpriseSearchServiceApplication - -$newReportingDb = "Search_AnalyticsReporting2" -$reportingDb = Get-SPScaleOutDatabase -SearchApplication $ssa -Split-SPServerScaleOutDatabase -SourceServiceApplication $ssa -SourceDatabase $reportingDb -NewDatabaseName $newReportingDb -SourcePercentage 33 - -``` -This example scales out the Search Analytics database, moving 33% of data to the new databases. - -## PARAMETERS - -### -NewDatabaseName -Specifies the name of a new scale-out database that you are creating. - -```yaml -Type: String -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceDatabase -The source scale-out database to move data from. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceServiceApplication -The service application in which the data move operation will take place. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDatabase -The target scale-out database to move data to. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: ExistingDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveLowerHalf -Specifies whether to move the lower or the upper side of the data range from the source scale-out database. -If this parameter is not specified, the default behavior is to move the upper side of the source scale-out database data range. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewDatabaseCredentials -Specifies the credentials to use when creating the scale-out database. -These credentials will have owner rights on the newly created scale-out database. -If a value is not provided, the current user's credentials will be used by default. - -```yaml -Type: PSCredential -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewDatabaseFailoverServer -Specifies the failover server name of the new scale-out database to be created. -If a value is not provided, the new scale-out database does not have a failover server. - -```yaml -Type: String -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewDatabaseServer -Specifies the name of the server of the new scale-out database to be created. -If a value is not provided, the default database server is used. - -```yaml -Type: String -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcePercentage -Specifies the percentage of data in the source scale-out database to move. -If a value is not provided, the default value of 50 percent is used. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Add-SPScaleOutDatabase](Add-SPScaleOutDatabase.md) - -[Get-SPScaleOutDatabase](Get-SPScaleOutDatabase.md) - -[Remove-SPScaleOutDatabase](Remove-SPScaleOutDatabase.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Split-SPServerScaleOutDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Split-SPServerScaleOutDatabase.md deleted file mode 100644 index ddd8b0eba6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Split-SPServerScaleOutDatabase.md +++ /dev/null @@ -1,281 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/split-spserverscaleoutdatabase -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Split-SPServerScaleOutDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Split-SPServerScaleOutDatabase - -## SYNOPSIS -Moves a specified percentage of partitions from one scale-out database to another. - - -## SYNTAX - -### NewDatabase -``` -Split-SPServerScaleOutDatabase -NewDatabaseName <String> -SourceDatabase <SPDatabasePipeBind> - -SourceServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-MoveLowerHalf] [-NewDatabaseCredentials <PSCredential>] [-NewDatabaseFailoverServer <String>] - [-NewDatabaseServer <String>] [-SourcePercentage <Int32>] [-WhatIf] [<CommonParameters>] -``` - -### ExistingDatabase -``` -Split-SPServerScaleOutDatabase -SourceDatabase <SPDatabasePipeBind> - -SourceServiceApplication <SPServiceApplicationPipeBind> -TargetDatabase <SPDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-MoveLowerHalf] [-SourcePercentage <Int32>] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [Cmdlet Parameter Sets](https://msdn.microsoft.com/library/dd878348(VS.85).aspx). - -Use the Split-SPServerScaleOutDatabase cmdlet to move a specified percentage of partitions from a source database to an existing target database or to a new database that you create with the specified parameters. - - - -## EXAMPLES - -### ---------------EXAMPLE--------------- -``` -$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication -$database = $databases[0] -Split-SPServerScaleOutDatabase -NewDatabaseName Database2 -NewDatabaseServer MyDatabaseServer -SourceDatabase $database -SourceServiceApplication $serviceApplication -SourcePercentage 30 -``` - -This example creates a new scale-out database named Database2 on the MyDatabaseServer database server in the given service application. The example also moves 30 percent of the data from the upper side of the data range in the first scale-out database of the given service application. - -## PARAMETERS - -### -NewDatabaseName -Specifies the name of a new scale-out database that you are creating. - -```yaml -Type: String -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceDatabase -The source scale-out database to move data from. - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceServiceApplication -The service application in which the data move operation will take place. - - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetDatabase -The target scale-out database to move data to. - - -```yaml -Type: SPDatabasePipeBind -Parameter Sets: ExistingDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -Note: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MoveLowerHalf -Specifies whether to move the lower or the upper side of the data range from the source scale-out database. If this parameter is not specified, the default behavior is to move the upper side of the source scale-out database data range. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewDatabaseCredentials -Specifies the credentials to use when creating the scale-out database. These credentials will have owner permissions on the new scale-out database. If you do not provide a value, the credentials of the logged on user will be used. - - -```yaml -Type: PSCredential -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewDatabaseFailoverServer -Specifies the failover server name of the new scale-out database. If you do not provide a value, the new scale-out database does not have a failover server. - - -```yaml -Type: String -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewDatabaseServer -Specifies the name of the server of the new scale-out database. If you do not provide a value, the name of the default database server is used. - - -```yaml -Type: String -Parameter Sets: NewDatabase -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourcePercentage -Specifies the percentage of data in the source scale-out database to move. If you do not provide a value, the default value, 50 percent, is used. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Add-SPServerScaleOutDatabase](Add-SPServerScaleOutDatabase.md) - -[Get-SPServerScaleOutDatabase](Get-SPServerScaleOutDatabase.md) - -[Remove-SPServerScaleOutDatabase](Remove-SPServerScaleOutDatabase.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPAdminJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPAdminJob.md deleted file mode 100644 index a5dcc87e0a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPAdminJob.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spadminjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPAdminJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPAdminJob - -## SYNOPSIS -Immediately starts any waiting administrative job on the local computer. - - -## SYNTAX - -``` -Start-SPAdminJob [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Start-SPAdminJob` cmdlet to execute all administrative timer jobs immediately rather than waiting for the timer job to run. - -When the service account for the SharePoint Administration service (SPAdminV4)) is disabled (necessary in some installations for security reasons), the `Start-SPAdminJob` cmdlet must be run on all computers to perform administrative task like provisioning. - -When you run this cmdlet in person (not in script), use the Verbose parameter to see the individual administrative operations that are run. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Start-SPAdminJob -Verbose -``` - -This example runs all waiting administrative jobs and shows verbose output to the administrator. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPAssignment.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPAssignment.md deleted file mode 100644 index 1796d363ec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPAssignment.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spassignment -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPAssignment -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Start-SPAssignment - -## SYNOPSIS -Initiates a new assignment store. - - -## SYNTAX - -``` -Start-SPAssignment [-AssignmentCollection <SPAssignmentCollection>] [-Global] [<CommonParameters>] -``` - -## DESCRIPTION -The `Start-SPAssignment` cmdlet properly disposes of objects used with variable assignments. - -Large amounts of memory are often required when SPWeb, SPSite, or SPSiteAdminsitration objects are used. -So the use of these objects, or lists of these objects, in Windows PowerShell scripts requires proper memory management. -By default, all Get commands dispose of these objects immediately after the pipeline finishes, but by using SPAssignment, you can assign the list of objects to a variable and dispose of the objects after they are no longer needed. -You can also ensure that the objects remain as long as you need them, even throughout multiple iterations of commands. - -There are three levels of assignment: - --- No assignment -- The object is not assigned to a variable and is disposed of after each iteration of the command. - --- Simple assignment -- All objects are assigned to the global assignment store. This is done by using the Global parameter. When using this level, all objects are assigned to a global store and are disposed of when the Stop-SPAssignment cmdlet is called. - --- Advanced assignment -- Objects are assigned to named stores for disposal. You can dispose of objects by using the Identity parameter with the `Stop-SPAssignment` cmdlet. - -Regardless of the assignment level used, all objects are disposed of when the Windows PowerShell run space is closed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Start-SPAssignment -global -$w = Get-SPWeb https://MyWeb -$w | Set-SPWeb -title "Accounting" -Stop-SPAssignment -global -``` - -This example uses simple assignment. -Although it is easier to use simple assignment, it is not a good idea to run commands that iterate through multiple SPSite or SPWeb objects while simple assignment is enabled. -Ensure that you run `Stop-SPAssignment` before you attempt any iterations of multiple objects. - - -### ------------------EXAMPLE 2----------------------- -``` -$gc = Start-SPAssignment -$web = $gc | Get-SPWeb https://MyWeb -$web | Set-SPWeb -title "Accounting" -Stop-SPAssignment -SemiGlobal $gc -``` - -This example sets the title of the SPWeb object in multiple lines and controls the rate of disposal. -This is an advanced example. -Only developers are advised to use it. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Global -If you use this parameter, all objects are assigned to the lifetime of the script and are disposed of when the `Stop-SPAssignment` cmdlet is called. - -If you do not use this parameter, you must assign the output of this cmdlet to a variable and then dispose of objects by using the Identity parameter of the `Stop-SPAssignment` cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPContentDeploymentJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPContentDeploymentJob.md deleted file mode 100644 index c5f09e2562..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPContentDeploymentJob.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Publishing.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spcontentdeploymentjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPContentDeploymentJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPContentDeploymentJob - -## SYNOPSIS -Starts a content deployment job. - -## SYNTAX - -``` -Start-SPContentDeploymentJob [-Identity] <SPContentDeploymentJobPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DeploySinceTime <String>] [-TestEnabled] - [-WaitEnabled] [-WhatIf] [-UseSpecificSnapshot <String>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Start-SPContentDeploymentJob` cmdlet starts a content deployment job. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Get-SPContentDeploymentPath "Path 1" | New-SPContentDeploymentJob -Name "Job 1" -SPContentDeploymentPath $_ -IncrementalEnabled:$true -ScheduleEnabled:$false | Start-SPContentDeploymentJob -``` - -This example creates a content deployment job Job 1 and runs it immediately. - - -## PARAMETERS - -### -Identity -Specifies the content deployment job to run. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content deployment job (for example, DeployJob1); or an instance of a valid SPContentDeploymentJob object. - -```yaml -Type: SPContentDeploymentJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DeploySinceTime -Specifies the date to use to determine what changes to export incrementally. -This parameter is ignored if the deployment job type is full. - -The type must be a valid DateTime type, in the form 2010,12,05. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TestEnabled -Runs the content deployment job in test mode only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WaitEnabled -Specifies that the command is not returned until the operation is complete. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseSpecificSnapshot -Use a snapshot of the named Content Database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPDiagnosticsSession.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPDiagnosticsSession.md deleted file mode 100644 index 9c123a0d65..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPDiagnosticsSession.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spdiagnosticssession -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPDiagnosticsSession -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPDiagnosticsSession - -## SYNOPSIS -Starts a diagnostic session to report diagnostic information to the usage database. - - -## SYNTAX - -``` -Start-SPDiagnosticsSession [-AssignmentCollection <SPAssignmentCollection>] [-CorrelationId <Guid>] - [-Dashboard] [-TraceLevel <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Start-SPDiagnosticsSession` cmdlet to report diagnostic information to the usage database. -After a diagnostic session starts, all Windows PowerShell for SharePoint cmdlets in Windows PowerShell scripts will use the same correlation to report diagnostic information. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### -------------EXAMPLE------- -``` -$correlationId = [guid]::NewGuid() -Start-SPDiagnosticsSession -CorrelationId $correlationId -Dashboard:$true -TraceLevel Verbose -``` - -This example starts a diagnostic session for a specified correlation ID with the trace level of verbose. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CorrelationId -Specifies the correlation ID to be used for the diagnostic session. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Dashboard -Specifies that diagnostics behave as if the developer dashboard were enabled. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TraceLevel -Specifies the Unified Logging Service (ULS) trace level override. - ---High ---Medium ---Monitorable ---Unexpected ---Verbose ---VerboseEx ---None - - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Stop-SPDiagnosticsSession](Stop-SPDiagnosticsSession.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md deleted file mode 100644 index db6f218887..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spenterprisesearchqueryandsitesettingsserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance - -## SYNOPSIS -Starts an instance of a search manager service. - -## SYNTAX - -``` -Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance - [-Identity] <SearchQueryAndSiteSettingsServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance` cmdlet starts the query and site settings service instance on the server instance in the same farm as the search service application to host the query object model (OM), Windows Communication Foundation (WCF) endpoint and query processor for the search service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$qssInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local -Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity $qssInstance -``` - -This example starts the local query and site settings instance. - - -## PARAMETERS - -### -Identity -Specifies the search manager service instance to start. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid SPServer name, or the name of a search manager service instance (for example, SearchManagerServiceInstance1); or an instance of a valid SearchManagerServiceInstance object. - - -```yaml -Type: SearchQueryAndSiteSettingsServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPEnterpriseSearchServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPEnterpriseSearchServiceInstance.md deleted file mode 100644 index fc00634555..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPEnterpriseSearchServiceInstance.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spenterprisesearchserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPEnterpriseSearchServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPEnterpriseSearchServiceInstance - -## SYNOPSIS -Starts an instance of a search service. - -## SYNTAX - -``` -Start-SPEnterpriseSearchServiceInstance [-Identity] <SearchServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet starts an instance of a search service on a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -If you run this cmdlet on a running search service instance, the associated search components are also restarted. -This may lead to a short downtime for queries. - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchServiceInstance -Local | Start-SPEnterpriseSearchServiceInstance -``` - -This example starts the local search service instance. - - -## PARAMETERS - -### -Identity -Specifies the search service instance to start. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a query server (for example, MyQueryServer); or an instance of a valid SearchServiceInstance object. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPInfoPathFormTemplate.md deleted file mode 100644 index b98eb9b479..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPInfoPathFormTemplate - -## SYNOPSIS -Activates a previously quiesced InfoPath form template. - -## SYNTAX - -``` -Start-SPInfoPathFormTemplate [-Identity] <SPFormTemplatePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Start-SPInfoPathFormTemplate` cmdlet activates a previously quiesced InfoPath form template after the form is upgraded. -During update, a form is quiesced, which disables access to the form. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Start-SPInfoPathFormTemplate -Identity formName.xsn -``` - -This example activates a form with a specified name. - - -## PARAMETERS - -### -Identity -Specifies the InfoPath form template to start. - -The type must be a valid URL, in the form https://server_name; a valid name of a Web application (for example, WebApp1); a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or an instance of a valid SPWebServiceProxy object. - - -```yaml -Type: SPFormTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPProjectGenerateWsdl.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPProjectGenerateWsdl.md deleted file mode 100644 index c93c56a961..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPProjectGenerateWsdl.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spprojectgeneratewsdl -applicable: Project Server 2016, Project Server 2019 -title: Start-SPProjectGenerateWsdl -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPProjectGenerateWsdl - -## SYNOPSIS -Generates ASPX pages from WSDL files. - -## SYNTAX - -``` -Start-SPProjectGenerateWsdl [-AssignmentCollection <SPAssignmentCollection>] [-Path <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -Generates ASPX pages from WSDL files. - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Start-SPProjectGenerateWsdl -``` -Generates ASPX files in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\ISAPI\PSI from the pre-existing WSDL files. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Path -The path to the location containing the WSDL files. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPService.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPService.md deleted file mode 100644 index f8e60d2f62..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPService.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spservice -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPService - -## SYNOPSIS -Enables a service in the farm. - - -## SYNTAX - -``` -Start-SPService [-Identity] <SPServicePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-IncludeCustomServerRole] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Start-SPService cmdlet enables a service in the farm. Service instances for this service will be started on the appropriate servers in the farm. - -This cmdlet only controls service instances on servers that are managed by MinRole. The behavior for the Custom server role has changed with the November 2016 Public Update (PU). Please see the IncludeCustomServerRole parameter for additional information. - - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Start-SPService -Identity "Microsoft SharePoint Foundation Sandboxed Code Service" -``` - -This example enables the Microsoft SharePoint Foundation Sandboxed Code Service in the farm. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the name of the service to enable. - -```yaml -Type: SPServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IncludeCustomServerRole -Creates a timer job that also starts service instances on servers that are assigned to the custom server role. - -This is a one-time Timer job. MinRole will make no further attempts to manage the service instances on servers assigned to the Custom server role. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServicePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPServiceInstance.md deleted file mode 100644 index 00d417d643..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPServiceInstance.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-spserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPServiceInstance - -## SYNOPSIS -Starts the service instance for a service on a specific server or the farm. - - -## SYNTAX - -``` -Start-SPServiceInstance [-Identity] <SPServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Start-SPServiceInstance` cmdlet to start the service instance for a service on a specific server or on the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Start-SPServiceInstance 67877d63-bff4-4521-867a-ef4979ba07ce -``` - -This example starts the given service instance on the server. - -The service instance GUID is unique to every farm. -You can run the `Get-SPServiceInstance` cmdlet to see the GUID of the service instances and then use the result from the SPServiceInstance cmdlet for other cmdlets. - - -## PARAMETERS - -### -Identity -Specifies the GUID of the service instance to get. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPTimerJob.md b/sharepoint/sharepoint-ps/sharepoint-server/Start-SPTimerJob.md deleted file mode 100644 index 268829c2cc..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Start-SPTimerJob.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/start-sptimerjob -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Start-SPTimerJob -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Start-SPTimerJob - -## SYNOPSIS -Runs a timer job once. - - -## SYNTAX - -``` -Start-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Start-SPTimerJob` cmdlet runs a timer job once on each front-end Web server where the parent service is provisioned. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------------EXAMPLE---------------- -``` -Get-SPTimerJob job-recycle-bin-cleanup | Start-SPTimerJob -``` - -This example starts the timer job named, job-recycle-bin-cleanup. - -## PARAMETERS - -### -Identity -Specifies the timer job to run. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a timer job (for example, TimerJob1); or an instance of a valid SPTimerJob object. - -```yaml -Type: SPTimerJobPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPAssignment.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPAssignment.md deleted file mode 100644 index c5151b86c4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPAssignment.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spassignment -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPAssignment -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPAssignment - -## SYNOPSIS -Disposes of objects in the provided assignment collection. - - -## SYNTAX - -``` -Stop-SPAssignment [[-SemiGlobal] <SPAssignmentCollection>] [-AssignmentCollection <SPAssignmentCollection>] - [-Global] [<CommonParameters>] -``` - -## DESCRIPTION -The `Stop-SPAssignment` cmdlet disposes of objects in the provided assignment collection. -Use the Global parameter to dispose of all objects in the global assignment collector and to stop the global store from collecting additional objects. -Provide a SemiGlobal assignment collector to dispose of all contained objects. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Start-SPAssignment -global -$w = Get-SPWeb https://MyWeb -$w | Set-SPWeb -title "Accounting" -Stop-SPAssignment -global -``` - -This example uses simple assignment. -While easier to use simple assignment, running commands that iterate through multiple SPSite or SPWeb objects while simple assignment is enabled is not recommended. -Ensure that `Stop-SPAssignment` is run before attempting any iterations of multiple objects. - - -## PARAMETERS - -### -SemiGlobal -Provides the assignment collector from which to dispose of objects. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Global -Stops the global assignment collector from storing objects and disposes of any objects contained by the global assignment collector. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPContentTypeReplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPContentTypeReplication.md deleted file mode 100644 index f32c4ceea9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPContentTypeReplication.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spcontenttypereplication -applicable: SSharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPContentTypeReplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPContentTypeReplication - -## SYNOPSIS -Stops Content Type replication job from SharePoint Online. - -## SYNTAX - -``` -Stop-SPContentTypeReplication [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Stops Content Type replication job from SharePoint Online and deletes the replication timer job. - -## EXAMPLES - -### -----------------EXAMPLE---------------- -``` -Stop-SPContentTypeReplication -``` -Stops Content Type replication job from SharePoint Online. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDiagnosticsSession.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDiagnosticsSession.md deleted file mode 100644 index 3bd4c4cce4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDiagnosticsSession.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spdiagnosticssession -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPDiagnosticsSession -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPDiagnosticsSession - -## SYNOPSIS -Stops a diagnostic session. - - -## SYNTAX - -``` -Stop-SPDiagnosticsSession [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Stop-SPDiagnosticsSession` cmdlet to stop a diagnostic session. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE--------- -``` -Stop-SPDiagnosticsSession -``` - -This example stops a diagnostic session. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Start-SPDiagnosticsSession](Start-SPDiagnosticsSession.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDistributedCacheServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDistributedCacheServiceInstance.md deleted file mode 100644 index dd8fd0235b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDistributedCacheServiceInstance.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spdistributedcacheserviceinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPDistributedCacheServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPDistributedCacheServiceInstance - -## SYNOPSIS -Stops an instance of the Distributed Cache service on a local server. - - -## SYNTAX - -``` -Stop-SPDistributedCacheServiceInstance [-Graceful] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Stop-SPDistributedCacheServiceInstance cmdlet to stop an instance of the Distributed Cache service on a local server. While a -Graceful switch does exist, this cmdlet is not capable of properly transferring cached items to another Distributed Cache host within the farm. Follow the guidance available at [Manage the Distributed Cache service in SharePoint Server 2013](https://technet.microsoft.com/en-us/library/jj219613.aspx) to properly issue a graceful shutdown of the Distributed Cache service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [https://go.microsoft.com/fwlink/p/?LinkId=251831](https://go.microsoft.com/fwlink/p/?LinkId=251831). - -## EXAMPLES - -### ------------ Example 1 ---------- -``` - -``` -Please see referenced article instead of using this cmdlet directly. - -## PARAMETERS - -### -Graceful -Specifies whether to gracefully stop an instance of the Distributed Cache service. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPDistributedCacheServiceInstanceOnLocalServer](Remove-SPDistributedCacheServiceInstanceOnLocalServer.md) - -[Add-SPDistributedCacheServiceInstanceOnLocalServer](Add-SPDistributedCacheServiceInstanceOnLocalServer.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md deleted file mode 100644 index 2d017dd22e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spenterprisesearchqueryandsitesettingsserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance - -## SYNOPSIS -Stops an instance of a search manager service. - -## SYNTAX - -``` -Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance - [-Identity] <SearchQueryAndSiteSettingsServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance` cmdlet stops an instance of a search manager service. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$qssInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local -Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity $qssInstance -``` - -This example stops the local query and site settings service instance. - - -## PARAMETERS - -### -Identity -Specifies the search manager service instance to stop. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid SPServer name, or the name of a search manager service instance (for example, SearchManagerServiceInstance1); or an instance of a valid SearchManagerServiceInstance object. - -```yaml -Type: SearchQueryAndSiteSettingsServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPEnterpriseSearchServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPEnterpriseSearchServiceInstance.md deleted file mode 100644 index 2c47f028d9..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPEnterpriseSearchServiceInstance.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spenterprisesearchserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPEnterpriseSearchServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPEnterpriseSearchServiceInstance - -## SYNOPSIS -Stops an instance of a search service. - -## SYNTAX - -``` -Stop-SPEnterpriseSearchServiceInstance [-Identity] <SearchServiceInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet stops an instance of a search service. - -Before you can stop a search service instance, you must remove all search topology components on the associated server from the active topology. -This can be done in three ways: - -- Removing components from the search topology -- Moving components to another server. For more information, see . -- Removing the search service application. For more information, see `Remove-SPEnterpriseSearchServiceApplication` - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPEnterpriseSearchServiceInstance -Local | Stop-SPEnterpriseSearchServiceInstance -``` - -This example stops the local search service instance. - - -## PARAMETERS - -### -Identity -Specifies the shared search service instance to stop. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a query server (for example, MyQueryServer); or an instance of a valid SearchServiceInstance object. - -```yaml -Type: SearchServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPInfoPathFormTemplate.md deleted file mode 100644 index a94f64dd0a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPInfoPathFormTemplate - -## SYNOPSIS -Disables a InfoPath form template on a farm before an upgrade. - -## SYNTAX - -``` -Stop-SPInfoPathFormTemplate [-Identity] <SPFormTemplatePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-TimeLeft <Int32>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Stop-SPInfoPathFormTemplate` cmdlet quiesces, or disables, an InfoPath form template before it upgrades the form. -Before a form is updated it is quiesced, which disables access to the form. -Use `Start-SPIPFormTemplate` to unquiesce, or activate, a form template after the form is upgraded. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Stop-SPInfoPathFormTemplate -Identity formName.xsn -``` - -This example disables a form template for a specified name. - -## PARAMETERS - -### -Identity -Specifies the InfoPath form template to start. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a form template (for example, InfoPathFormTemplate1); a valid name of a form template files (for example, FormTemplateFile1.xsn); or an instance of a valid SPFormTemplate object. - -```yaml -Type: SPFormTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeLeft -Specifies the time duration, in minutes, before the form template will be quiesced. -The default value is 0. - -An integer value in the range from 0 to 1440. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPService.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPService.md deleted file mode 100644 index e7d9eb13af..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPService.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spservice -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPService -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPService - -## SYNOPSIS -Disables a service in the farm. - -## SYNTAX - -``` -Stop-SPService [-Identity] <SPServicePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-IncludeCustomServerRole] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The Stop-SPService cmdlet disables a service in the farm. Service instances for this service will be stopped on the appropriate servers in the farm. - -**Note**: This cmdlet only controls service instances on servers that are managed by MinRole. The behavior for the Custom server role has changed with the November 2016 Public Update (PU). Please see the **IncludeCustomServerRole** parameter for additional information. - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Stop-SPService -Identity "Microsoft SharePoint Foundation Sandboxed Code Service" -``` - -This example disables the Microsoft SharePoint Foundation Sandboxed Code Service in the farm. - - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -**Note**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the name of the service to disable. - -```yaml -Type: SPServicePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IncludeCustomServerRole -Creates a timer job that also stops service instances on servers that are assigned to the custom server role. -**Note**: This is a one-time Timer job. MinRole will make no further attempts to manage the service instances on servers assigned to the Custom server role. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServicePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPServiceInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPServiceInstance.md deleted file mode 100644 index a341064a7a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPServiceInstance.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-spserviceinstance -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPServiceInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPServiceInstance - -## SYNOPSIS -Stops the service instance for a service. - - -## SYNTAX - -``` -Stop-SPServiceInstance [-Identity] <SPServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Stops the service instance for a service on the specified server or for the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Stop-SPServiceInstance 67877d63-bff4-4521-867a-ef4979ba07ce -``` - -This example stops the service instance in the given server. - -The service instance GUID is unique to every farm. -You can run the `Get-SPServiceInstance` cmdlet to see the GUID of the service instances and then use the result from the SPServiceInstance cmdlet for other cmdlets. - -## PARAMETERS - -### -Identity -Specifies the GUID of the service instance to get. - -```yaml -Type: SPServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPTaxonomyReplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPTaxonomyReplication.md deleted file mode 100644 index dfc5459f41..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Stop-SPTaxonomyReplication.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.SharePoint.Taxonomy.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/stop-sptaxonomyreplication -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Stop-SPTaxonomyReplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Stop-SPTaxonomyReplication - -## SYNOPSIS -Terminates Hybrid SharePoint Taxonomy replication from SharePoint Online site to local SharePoint on-premises site. - -## SYNTAX - -``` -Stop-SPTaxonomyReplication [-AssignmentCollection <SPAssignmentCollection>] -Credential <PSCredential> - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Stop-SPTaxonomyReplication cmdlet to terminate Hybrid SharePoint Taxonomy replication from SharePoint Online site to local SharePoint on-premises site. The Taxonomy Groups Replication timer job will be killed and a full replication from SharePoint Online Taxonomy store to local SharePoint on-premises store will be performed. - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Stop-SPTaxonomyReplication -Credential (Get-Credential) -``` - -This example performs a full replication and deletes the Taxonomy Groups Replication timer job. If the full replication fails, you can run the cmdlet again. The credential is a SharePoint Online tenant administrator credential. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Credential -This is the Taxonomy Term Store administrator credential of remote SharePoint Online Term Store. - -Fetches full taxonomy data properties, so a Term Store Administrator's credential is needed to perform the operations. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSCredential -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Suspend-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Suspend-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index fdca8b8982..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Suspend-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/suspend-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Suspend-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Suspend-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Suspends a search service application, pausing all crawls and search operations, to perform a task such as system maintenance. - -## SYNTAX - -``` -Suspend-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet reads the SearchServiceApplication object and moves it from Paused for: External Request status to Suspend status. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA -$ssa | Suspend-SPEnterpriseSearchServiceApplication -``` - -This example obtains a reference to a search service application named MySSA and pauses it, stopping all crawls and other search components such as content processing components, analytics processing components and indexing components. - -## PARAMETERS - -### -Identity -Specifies the search service application to suspend. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Suspend-SPStateServiceDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Suspend-SPStateServiceDatabase.md deleted file mode 100644 index d67c61eb7d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Suspend-SPStateServiceDatabase.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.Office.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/suspend-spstateservicedatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Suspend-SPStateServiceDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Suspend-SPStateServiceDatabase - -## SYNOPSIS -Pauses a state database and thus prevents new rows of data from being added to a database. - -## SYNTAX - -``` -Suspend-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Suspend-SPStateServiceDatabase` cmdlet pauses a state database. -This cmdlet updates the state database object that is specified in the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -$db = Get-SPStateServiceDatabase -Suspend-SPStateServiceDatabase -Identity $db -``` - -This example suspends a specified state service database. - -## PARAMETERS - -### -Identity -Specifies the state database to pause. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a state database (for example, StateSvcDB1); or an instance of a valid SPStateServiceDatabase object. - -```yaml -Type: SPStateDatabasePipeBind -Parameter Sets: (All) -Aliases: Name -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Sync-SPProjectPermissions.md b/sharepoint/sharepoint-ps/sharepoint-server/Sync-SPProjectPermissions.md deleted file mode 100644 index 30afdeb23a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Sync-SPProjectPermissions.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/sync-spprojectpermissions -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Sync-SPProjectPermissions -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Sync-SPProjectPermissions - -## SYNOPSIS -Manually synchronizes permissions between a Project Web App instance and its associated project sites. - -## SYNTAX - -### PSMode -``` -Sync-SPProjectPermissions [-Url] <Uri> [-SyncPWASite] [-SyncProjectSites] [-Async] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -### SPMode -``` -Sync-SPProjectPermissions [-Url] <Uri> [[-Type] <SharePointPermissionModeSyncType>] - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Sync-SPProjectPermissions` cmdlet causes permissions to be synchronized to the project sites associated with projects in a Project Web App instance and the permissions set on those projects in Project Server. - -This cmdlet works with both SharePoint permission mode and Project Server permission mode. - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Sync-SPProjectPermissions -Url https://pwa_site -Type Full -``` - -Performs a full sync against the PWA site https://pwa_site. - -## PARAMETERS - -### -Url -Specifies the URL of the Project Web App instance for which you want to synch permissions. - -The type must be a valid URL, in the form https://pwa_site. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SyncPWASite -Triggers a synchronization of Project Server permissions to the PWA site. - -This parameter is used with Project Server permission mode. - -```yaml -Type: SwitchParameter -Parameter Sets: PSMode -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -Specifies the type of sync to perform: full or incremental. - -This parameter is used with SharePoint permission mode. - -Valid values are: - -Full, Incremental, AllGroups - -```yaml -Type: SharePointPermissionModeSyncType -Parameter Sets: SPMode -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SyncProjectSites -Triggers a synchronization of Project Server permissions to the project sites. - -This parameter is used with Project Server permission mode. - -```yaml -Type: SwitchParameter -Parameter Sets: PSMode -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Async -Specifies that the synchronization is placed in the Project Server queue. -Omitting this flag causes the synchronization to occur immediately within the Windows PowerShell console. - -This parameter is used with Project Server permission mode. - -```yaml -Type: SwitchParameter -Parameter Sets: PSMode -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Test-SPContentDatabase.md deleted file mode 100644 index 48c11b02f5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPContentDatabase.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/test-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Test-SPContentDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Test-SPContentDatabase - -## SYNOPSIS -Tests a content database. - - -## SYNTAX - -### ContentDatabaseById -``` -Test-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-DatabaseCredentials <PSCredential>] [-ExtendedCheck] [-ServerInstance <SPDatabaseServiceInstancePipeBind>] - [-ShowLocation] [-ShowRowCounts] [<CommonParameters>] -``` - -### ContentDatabaseByName -``` -Test-SPContentDatabase -Name <String> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseCredentials <PSCredential>] [-ExtendedCheck] - [-ServerInstance <SPDatabaseServiceInstancePipeBind>] [-ShowLocation] [-ShowRowCounts] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Test-SPContentDatabase` cmdlet to test a content database against a Web application to verify all customizations referenced within the content database are also installed in the web application. -This cmdlet can be issued against a content database currently attached to the farm, or a content database that is not connected to the farm. -It can be used to test content databases from SharePoint 2010 Products and from SharePoint Products and Technologies. - -The `Test-SPContentDatabase` cmdlet does not change any of the data or structure of the content database, but can cause load on the database while the checks are in progress, which could temporarily block use of the content database. -This cmdlet should only be used against a content database that is currently under low or no usage. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------------------EXAMPLE 1----------------------- -``` -Test-SPContentDatabase -name WSS_Content_DB -webapplication https://sitename -``` - -This example tests the WSS_Content_DB content database against the sitename Web application and returns a list of issues. - - -### ----------------------------EXAMPLE 2----------------------- -``` -$DB = Get-SPContentDatabase -site https://contoso.com -Test-SPContentDatabase $DB -showrowcounts -``` - -This example gets the content database that contains the site collection at https://contoso.com and then tests the database against the Web application that hosts it to determine issues. -Together with displaying the list of issues, by specifying the ShowRowCounts parameter, this also returns the table size metrics from the content database. - -## PARAMETERS - -### -Identity -Specifies an existing connected SharePoint content database to one of the two parameter sets in the form of a GUID or database name if it is unique. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: ContentDatabaseById -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Specifies the existing content database to test. - -The type must be a valid name of a SharePoint content database; for example, SPContentDB1. - -```yaml -Type: String -Parameter Sets: ContentDatabaseByName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the SharePoint Web application to use to test the content database. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: ContentDatabaseByName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -DatabaseCredentials -Specifies the PSCredential object that contains the user name and password to be used for database SQL Server Authentication. - -The type must be a valid PSCredential object. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExtendedCheck -Checks for inconsistent authentication modes during database-attach upgrade process. - -The selected mode, claims or classic, must be the same in both versions. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServerInstance -Specifies the instance of the database service to use to test the specified content database. - -The type must be a valid GUID, such as 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SQL Server instance (for example, DBSvrInstance1); or an instance of a valid SPDatabaseServiceInstance object. - -```yaml -Type: SPDatabaseServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowLocation -Specifies the locations where missing templates and features are being used within the database. -Typically, reported locations are scoped within the site collections that are within the specified content database. - -The use of the parameter significantly increases the time to complete the test procedure. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShowRowCounts -Returns database statistics which are row counts for tables in the content database. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Test-SPInfoPathFormTemplate.md deleted file mode 100644 index c4f58b3dc0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/test-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Test-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Test-SPInfoPathFormTemplate - -## SYNOPSIS -Validates that a InfoPath form template is browser-enabled. - -## SYNTAX - -``` -Test-SPInfoPathFormTemplate [-Path] <String> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Test-SPInfoPathFormTemplate` cmdlet validates that an InfoPath form template can be browser-enabled. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Test-SPInfoPathFormTemplate -Identity formName.xsn -``` - -This example validates an InfoPath form template for a specified name. - -## PARAMETERS - -### -Path -Specifies the path and name of the InfoPath form template to install. - -The type must be a valid path and file name of a form template, in the form: - -- C:\folder_name\formtemplate_name -- \\\\server_name\folder_name\formtemplate_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPO365LinkSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Test-SPO365LinkSettings.md deleted file mode 100644 index e51c7edc19..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPO365LinkSettings.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/test-spo365linksettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Test-SPO365LinkSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Test-SPO365LinkSettings - -## SYNOPSIS -Validates whether the configured Office 365 hybrid site uses a valid template. - -## SYNTAX - -``` -Test-SPO365LinkSettings [-AssignmentCollection <SPAssignmentCollection>] -MySiteHostUrl <Uri> - [<CommonParameters>] -``` - -## DESCRIPTION -Use the **Test-SPO365LinkSettings** cmdlet to validate a templated against a configured Office 365 hybrid site. - -## EXAMPLES - -### EXAMPLE 1 -```powershell -Test-SPO365LinkSettings -MySiteHostUrl https://contoso-my.sharepoint.com/ -``` - -This example test a template using the contoso-my.sharepoint site. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` -### -MySiteHostUrl -The root URL for the redirected pages - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## RELATED LINKS -[Get-SPO365LinkSettings](Get-SPO365LinkSettings.md) - -[Set-SPO365LinkSettings](Set-SPO365LinkSettings.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectServiceApplication.md deleted file mode 100644 index 450030364a..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectServiceApplication.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/test-spprojectserviceapplication -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Test-SPProjectServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Test-SPProjectServiceApplication - -## SYNOPSIS -This cmdlet runs a series of health checks against the Project Service Application. - -## SYNTAX - -``` -Test-SPProjectServiceApplication [-Identity] <PsiServiceApplicationPipeBind> - [[-Rule] <ProjectServiceApplicationHealthRuleName>] [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet runs a series of health checks against the Project Service Application. - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Project Application Services'} -Test-SPProjectServiceApplication -Identity $sa -``` - -This example runs all health checks again the service application named "Project Service Application." - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Identity -The name of the Project Service Application to test against. - -```yaml -Type: PsiServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Rule -Which rule to run against the service application. - -Valid rules are: - -All, CalcServiceWorkerState, QueueInFlightJobs, QueueServiceInternalState - -Project Server 2013 has this additional rule which is not available in Project Server 2016, Project Server 2019: - -QueueSiteCheck - -Project Server 2016, Project Server 2019 added this additional rule: - -DatabasePermissions - -```yaml -Type: ProjectServiceApplicationHealthRuleName -Parameter Sets: (All) -Aliases: -Accepted values: All, QueueServiceInternalState, QueueInFlightJobs, CalcServiceWorkerState, DatabasePermissions -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Office.Project.Server.Cmdlet.PsiServiceApplicationPipeBind -Microsoft.Office.Project.Server.HealthRules.ProjectServiceApplicationHealthRuleName -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectWebInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectWebInstance.md deleted file mode 100644 index 022d2af73d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectWebInstance.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: microsoft.office.project.server.stsadmcommandhandler.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/test-spprojectwebinstance -applicable: Project Server 2013, Project Server 2016, Project Server 2019 -title: Test-SPProjectWebInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Test-SPProjectWebInstance - -## SYNOPSIS -Runs a suite of tests on an existing Project Web Instance. - -## SYNTAX - -``` -Test-SPProjectWebInstance [-Identity] <ProjectInstancePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Rule <ProjectSiteHealthRuleName>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet runs a suite of tests on an existing Project Web Instance. -The tests are designed to verify the health status of the Project Web Instance. -The cmdlet returns the set of tests as a list of Microsoft.Office.Project.Server.HealthRules objects associated with a status of type SPSiteHealthStatusType (Passed, FailedWarning, FailedError). - -For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833). - -## EXAMPLES - -### ----------------------EXAMPLE----------------------- -``` -Get-SPProjectWebInstance | Test-SPProjectWebInstance -``` - -This example runs a suite of tests on all Project Web Instances in the SharePoint Server farm. - -## PARAMETERS - -### -Identity -Specifies a Project Web Instance. - -```yaml -Type: ProjectInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Rule -{{Fill Rule Description}} - -```yaml -Type: ProjectSiteHealthRuleName -Parameter Sets: (All) -Aliases: -Applicable: Project Server 2013, Project Server 2016, Project Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Mount-SPProjectWebInstance](Mount-SPProjectWebInstance.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Test-SPSite.md deleted file mode 100644 index 1940b96e99..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Test-SPSite.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/test-spsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Test-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Test-SPSite - -## SYNOPSIS -Activates the RunTests method against a referenced SPSite object. - - -## SYNTAX - -``` -Test-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-RuleId <Guid>] - [-RunAlways] [<CommonParameters>] -``` - -## DESCRIPTION -The `Test-SPSite` cmdlet runs one or all site collection health checks on the site collection and its contents. -This cmdlet reports the rules which were run and provides a summary of the results. - -To run tests in repair mode, use the `Repair-SPSite` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE 1------------ -``` -Test-SPSite https://<site name>/sites/testsite -``` - -This example runs all the site collection health checks on the https://\<site name\>/sites/testsite site collection. - -### --------------EXAMPLE 2------------ -``` -Test-SPSite https://<site name</sites/testsite -Rule "ee967197-ccbe-4c00-88e4-e6fab81145e1" -``` - -This example runs just the "Missing Galleries Check" on the https://\<site name\>/sites/testsite site collection. - -## PARAMETERS - -### -Identity -Specifies the URL or GUID of the site to run a test. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RuleId -Specifies one specific site health rule to run. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RunAlways -Forces a rule to run even if a health check was run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Repair-SPSite](Repair-SPSite.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-FASTSearchAdminDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-FASTSearchAdminDatabase.md deleted file mode 100644 index 5bfbc1a3cf..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-FASTSearchAdminDatabase.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-fastsearchadmindatabase -applicable: FAST Server for SharePoint 2010 -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: -title: Uninstall-FASTSearchAdminDatabase ---- - -# Uninstall-FASTSearchAdminDatabase - -## SYNOPSIS -Uninstalls the database used by the Microsoft FAST Search Server 2010 for SharePoint administration services. -This cmdlet is primarily called during uninstallation by the FAST Search Server 2010 for SharePoint installer. - -## SYNTAX - -``` -Uninstall-FASTSearchAdminDatabase [-DbConnection <String>] [-DbName <String>] [-DbServer <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet uninstalls the database used by the FAST Search Server 2010 for SharePoint administration services. -All data is deleted. -This cmdlet is primarily called during uninstallation, by the FAST Search Server 2010 for SharePoint installer. - -The administration database default name is "FASTSearchAdminDatabase" and is located in the Microsoft SQL Server instance specified by the DbServer or DbConnection parameters. - -For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227). - -## EXAMPLES - -### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010) -``` -Uninstall-FASTSearchAdminDatabase -DbServer=sqlserver.contoso.com -``` - -This example uninstalls the FAST Search Server 2010 for SharePoint administration database on the given SQL Server instance. -All data will be deleted. - -## PARAMETERS - -### -DbConnection -Specifies the database connection string for the FAST Search Server 2010 for SharePoint administration database, in the same format as the ConnectionString property of the System.Data.SqlClient.SqlConnection .NET Framework type. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DbName -Specifies the name of the FAST Search Server 2010 for SharePoint administration database. - -The name only takes effect when used in conjunction with the DbServer parameter, not the DbConnection parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DbServer -Specifies the database server instance that contains the FAST Search Server 2010 for SharePoint administration database - -Only one of the DbServer and DbConnection parameters must be specified. -Using DbServer with a value of sqlserver.contoso.com is equivalent to using DbConnection with the value "Data Source=sqlserver.contoso.com;Database=FASTSearchAdminDatabase;integrated Security=True"" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: FAST Server for SharePoint 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Install-FASTSearchAdminDatabase](Install-FASTSearchAdminDatabase.md) - diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPAppInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPAppInstance.md deleted file mode 100644 index b8b5aae5e0..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPAppInstance.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-spappinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPAppInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPAppInstance - -## SYNOPSIS -Uninstalls an instance of an app. - - -## SYNTAX - -``` -Uninstall-SPAppInstance -Identity <SPAppInstance> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Uninstall-SPAppInstance` cmdlet to uninstall an instance of an app. -This cmdlet is required to be run before a migration process. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE-------------- -``` -$spapp = Get-SPAppInstance -AppInstanceId $instance.Id -Uninstall-SPAppInstance -Identity $spapp -``` - -This example uninstalls an instance of an app. - - -## PARAMETERS - -### -Identity -Specifies the app instance for which to find metadata. - -```yaml -Type: SPAppInstance -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppInstance](Get-SPAppInstance.md) - -[Restart-SPAppInstanceJobs](Restart-SPAppInstanceJobs.md) - -[Uninstall-SPAppInstance](Uninstall-SPAppInstance.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPDataConnectionFile.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPDataConnectionFile.md deleted file mode 100644 index 189ec83a1b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPDataConnectionFile.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-spdataconnectionfile -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPDataConnectionFile -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPDataConnectionFile - -## SYNOPSIS -Removes a data connection file. - -## SYNTAX - -``` -Uninstall-SPDataConnectionFile [-Identity] <SPDataConnectionFilePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Uninstall-SPDataConnectionFile` cmdlet removes the data connection file specified in the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Uninstall-SPDataConnectionFile -Identity "Sample.udcx -"Sample1.udcx", "Sample2.udcx", "Sample3.udcx" | Uninstall-SPDataConnectionFile -``` - -This example uninstalls a specified data connection file in two different ways. - -## PARAMETERS - -### -Identity -Specifies the data connection file to remove. - -The type must be a valid GUID, in form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a data connection file (for example, DataConnectionFileName1.udcx); or an instance of a valid SPDataConnectionFile object. - -```yaml -Type: SPDataConnectionFilePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPFeature.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPFeature.md deleted file mode 100644 index 509558562d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPFeature.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-spfeature -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPFeature -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPFeature - -## SYNOPSIS -Uninstalls an installed feature definition. - - -## SYNTAX - -``` -Uninstall-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-CompatibilityLevel <Int32>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Uninstall-SPFeature` cmdlet removes the specified feature definition from the collection of feature definitions in the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1----------------------- -``` -Uninstall-SPFeature -Identity "MyCustomFeature" -``` - -This example uninstalls the feature at $env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES\MyCustomFeature/feature.xml. - -### ------------------EXAMPLE 2----------------------- -``` -Uninstall-SPFeature -Identity "MyCustomFeature" -CompatibilityLevel 14 -``` - -This example uninstalls the feature at $env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES\MyCustomFeature/feature.xml. - -## PARAMETERS - -### -Identity -Specifies the name of the feature or GUID to uninstall. - -The type must be the name of the feature folder located in the \<drive\>:\program files\common files\Microsoft Shared\Web server extensions\15\template\features folder, or must be a GUID, in the form 21d186e1-7036-4092-a825-0eb6709e9281. - -```yaml -Type: SPFeatureDefinitionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies the version of feature to uninstall. -When the version is not specified it will default to the web applications MaxVersion value. - - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces the uninstallation of a feature that is already installed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPHelpCollection.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPHelpCollection.md deleted file mode 100644 index 5c66f1c64e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPHelpCollection.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-sphelpcollection -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPHelpCollection -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPHelpCollection - -## SYNOPSIS -Removes Help collection files. - - -## SYNTAX - -``` -Uninstall-SPHelpCollection -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Uninstall-SPHelpCollection` cmdlet removes the specified Help collection files from the product Help library in the current farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Uninstall-SPHelpCollection -Name "OSSAdmin.1033" -``` - -This example uninstalls a Help collection. -The folder name of the Help collection to uninstall is OSSAdmin.1033. - -## PARAMETERS - -### -Name -Specifies the name of the Help collection files to uninstall. - -The type must be a valid name of a Help collection; for example, HelpDocs1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPInfoPathFormTemplate.md deleted file mode 100644 index 40abfb978d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPInfoPathFormTemplate - -## SYNOPSIS -Removes a InfoPath form template from a farm. - -## SYNTAX - -``` -Uninstall-SPInfoPathFormTemplate [-Identity] <SPFormTemplatePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Uninstall-SPInfoPathFormTemplate` cmdlet removes a specified InfoPath form template from a farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Uninstall-SPInfoPathFormTemplate -Identity formName.xsn -``` - -This example removes an InfoPath form template from a farm. - - -## PARAMETERS - -### -Identity -Specifies the InfoPath form template to uninstall. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a form template (for example, InfoPathFormTemplate1); a valid name of a form template files (for example, FormTemplateFile1.xsn); or an instance of a valid SPFormTemplate object. - -```yaml -Type: SPFormTemplatePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPSolution.md deleted file mode 100644 index 3490b0a126..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPSolution.md +++ /dev/null @@ -1,244 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-spsolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPSolution - -## SYNOPSIS -Retracts a deployed SharePoint solution. - - -## SYNTAX - -### AllWebApplication -``` -Uninstall-SPSolution [-Identity] <SPSolutionPipeBind> [-AllWebApplications] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-CompatibilityLevel <String>] - [-Language <UInt32>] [-Local] [-Time <String>] [-WhatIf] [<CommonParameters>] -``` - -### OneWebApplication -``` -Uninstall-SPSolution [-Identity] <SPSolutionPipeBind> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-CompatibilityLevel <String>] - [-Language <UInt32>] [-Local] [-Time <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Uninstall-SPSolution` cmdlet retracts a deployed SharePoint solution in preparation for removing it from the farm entirely. -This cmdlet removes files from the front-end Web server. -Use the `Remove-SPSolution` cmdlet to delete the solution package from the solution store of the farm; be sure to use the `Remove-SPSolution` cmdlet only after you have run `Uninstall-SPSolution`. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Uninstall-SPSolution -Identity contoso_solution.wsp -``` - -This example retracts the deployed SharePoint solution contoso_solution.wsp. - -## PARAMETERS - -### -Identity -Specifies the SharePoint solution to uninstall. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint solution (for example, SPSolution1); or an instance of a valid SPSolution object. - -```yaml -Type: SPSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AllWebApplications -Specifies that the new SharePoint solution will be uninstalled for all SharePoint Web applications in the farm. - -```yaml -Type: SwitchParameter -Parameter Sets: AllWebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Uninstalls the SharePoint solution for the specified SharePoint Web application. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; or a valid name of a SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: OneWebApplication -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel -Specifies whether to uninstall the solution, from a specific version directory based on CompatibilityLevel. The default behavior if this parameter is not specified is to uninstall the solution only from the version directory based on the version tracked in the manifest of the solution's cab file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Uninstalls the language pack for the specified language. - -The type must be a valid language identifier; for example, 1033. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Local -Uninstalls the solution from the active server computer. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Time -Specifies when the solution will be uninstalled. -The default value is immediate retraction. - -The type must be a valid DateTime value, in the form 2010,12,05. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPUserSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPUserSolution.md deleted file mode 100644 index 25ea9bed2c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPUserSolution.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-spusersolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPUserSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPUserSolution - -## SYNOPSIS -Deactivates a sandboxed solution in a site collection. - - -## SYNTAX - -``` -Uninstall-SPUserSolution [-Identity] <SPUserSolutionPipeBind> -Site <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Uninstall-SPUserSolution` cmdlet deactivates a sandboxed solution in a site collection so that you can delete it by using the `Remove-SPUserSolution` cmdlet. -A user solution is a sandboxed solution. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE--------------- -``` -Uninstall-SPUserSolution -Identity contoso_solution.wsp -Site https://sitename -``` - -This example deactivates the sandboxed solution contoso_solution.wsp on the site https://sitename. - -## PARAMETERS - -### -Identity -Specifies the sandboxed solution to deactivate. - -The type must be a valid name of a sandboxed solution (for example, UserSolution1); or an instance of a valid SPUserSolution object. - -```yaml -Type: SPUserSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Deactivates the sandboxed solution for the specified site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form http://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPWebPartPack.md b/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPWebPartPack.md deleted file mode 100644 index a53a5767d6..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPWebPartPack.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/uninstall-spwebpartpack -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Uninstall-SPWebPartPack -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Uninstall-SPWebPartPack - -## SYNOPSIS -Uninstalls the specified Web Part package. - - -## SYNTAX - -``` -Uninstall-SPWebPartPack [-Identity] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Language <UInt32>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf] [-CompatibilityLevel <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Uninstall-SPWebPartPack` cmdlet uninstalls the Web Part package specified by the Identity parameter. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE 1------------------ -``` -Uninstall-SPWebPartPack "mypart.wpp" -WebApplication https://portal -``` - -This example uninstalls mypart.wpp to from the Web application https://portal. - -### ------------------EXAMPLE 2------------------ -``` -Get-SPWebPartPack -WebApplication https://portal | Uninstall-SPWebPartPack -``` - -This example uninstalls all Web part packages from the Web application https://portal. - -## PARAMETERS - -### -Identity -Specifies the Web Part package in the farm's configuration database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Language -Specifies the language ID of the Web Part package to delete. -If no language is specified, the Web Part package is uninstalled for all languages. - -The type must be a valid language identifier, in the form 1033. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the Web application from which to uninstall the Web Part package. -If no Web application is specified, the Web Part package is uninstalled from all Web applications. - -The type must be a valid name, in the form WebApplication-1212, or a URL, in the form https://server_name/WebApplication-1212. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompatibilityLevel -{{Fill CompatibilityLevel Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Unpublish-SPServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Unpublish-SPServiceApplication.md deleted file mode 100644 index e850fbb3c5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Unpublish-SPServiceApplication.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/unpublish-spserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Unpublish-SPServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Unpublish-SPServiceApplication - -## SYNOPSIS -Stops sharing the specified service application outside the farm. - - -## SYNTAX - -``` -Unpublish-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Unpublish-SPServiceApplication` cmdlet to stop publishing the service application, specified by the Identity parameter, outside the farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -UnPublish-SPServiceApplication 053c34be-d251-488c-8e94-644eae94da26 -``` - -This example stops publishing of the specified service application outside the farm. - -The service application GUID is unique to every farm. -You can run the `Get-SPServiceApplication` cmdlet to see the GUID of the service applications and then use the result from the `Get-SPServiceApplication` cmdlet for other SPServiceApplication cmdlets; for example, `Publish-SPServiceApplication`. - -## PARAMETERS - -### -Identity -Specifies the GUID of the service application to stop sharing outside the farm. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppCatalogConfiguration.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppCatalogConfiguration.md deleted file mode 100644 index e420f7c1c1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppCatalogConfiguration.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spappcatalogconfiguration -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPAppCatalogConfiguration -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPAppCatalogConfiguration - -## SYNOPSIS -Sets a specific site collection as the App Catalog site collection. - -## SYNTAX - -``` -Update-SPAppCatalogConfiguration [-Site] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Force] [-SkipWebTemplateChecking] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Update-SPAppCatalogConfiguration cmdlet to set a specific site collection as the App Catalog site collection. The App Catalog site collection contains catalogs for Apps for SharePoint and Apps for Office. It is used to help ITPro administrators distribute SharePoint Apps and Office Apps to their end users. Each Web Application or Tenancy can have 1 App Catalog Site collection associated to it. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference (https://go.microsoft.com/fwlink/p/?LinkId=671715). - -## EXAMPLES - -### ---------------EXAMPLE----------- -``` -Update-SPAppCatalogConfiguration -Site https://contoso/sites/appcatalog_1 -Force:$true -SkipWebTemplateChecking:$true -``` -This example sets https://contoso/sites/appcatalog_1 as the app catalog site collection for the tenant it belongs to. - -## PARAMETERS - -### -Site -Specifies the URL or GUID of the site collection to be set as the app catalog site collection. - - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Specifies to force marking the site collection even if there are validation errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipWebTemplateChecking -Specifies whether to skip checking if the template of the site is APCATALOG#0. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPSitePipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppInstance.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppInstance.md deleted file mode 100644 index 9d78d8e2fd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppInstance.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spappinstance -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPAppInstance -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPAppInstance - -## SYNOPSIS -Updates the app instance. - - -## SYNTAX - -``` -Update-SPAppInstance -App <SPApp> -Identity <SPAppInstance> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Update-SPAppInstance` cmdlet to update the app instance. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - - -## EXAMPLES - -### --------EXAMPLE--------- -``` -$spapp = Import-SPAppPackage -Path .\feature-upgrade-v2.spapp -Site https://localhost -Source ([microsoft.sharepoint.administration.spappsource]::ObjectModel) -C:\S>$instance = Get-SPAppInstance -AppInstanceId $instance.Id -Update-SPAppInstance -Identity $instance -App $spapp -``` - -This example updates an instance of an app. - - -## PARAMETERS - -### -App -Specifies the app version to upgrade to. - -```yaml -Type: SPApp -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies The app instance to upgrade. - -```yaml -Type: SPAppInstance -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-SPAppInstance](Get-SPAppInstance.md) - -[Restart-SPAppInstanceJobs](Restart-SPAppInstanceJobs.md) - -[Uninstall-SPAppInstance](Uninstall-SPAppInstance.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPDistributedCacheSize.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPDistributedCacheSize.md deleted file mode 100644 index d451c1e7a4..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPDistributedCacheSize.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spdistributedcachesize -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPDistributedCacheSize -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPDistributedCacheSize - -## SYNOPSIS -Reconfigures the allocation of memory that is dedicated to the Distributed Cache service. - -## SYNTAX - -``` -Update-SPDistributedCacheSize [-CacheSizeInMB] <UInt32> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -Use the Update-SPDistributedCacheSize cmdlet to allocate memory to the Distributed cache service. - -## EXAMPLES - -### -------------EXAMPLE---------- -``` -Update-SPDistributedCacheSize -CacheSizeInMB 2048 -``` - -Updates the Distributed Cache size to 2048MB. - - -## PARAMETERS - -### -CacheSizeInMB -Specifies the memory size in megabytes (MB) that you want to allocate to the Distributed Cache service. The default value is 5 percent of total system random access memory (RAM). This value should not be more than 40 percent of total system RAM with a maximum limit of 16 gigabytes (GB). - - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -NOTE: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.UInt32 -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPFarmEncryptionKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPFarmEncryptionKey.md deleted file mode 100644 index a496d886cb..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPFarmEncryptionKey.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spfarmencryptionkey -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPFarmEncryptionKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPFarmEncryptionKey - -## SYNOPSIS -Changes the value of the farm encryption key and using the new key, re-encrypts all the data. - - -## SYNTAX - -``` -Update-SPFarmEncryptionKey [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Resume] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPFarmEncryptionKey` cmdlet changes the farm encryption key to a new randomly generated value. -When the new key is used, all the data is re-encrypted. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE----------------------- -``` -Update-SPFarmEncryptionKey -confirm -``` - -This example changes the farm encryption key to a new value and re-encrypts all the data. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Resume -Resumes re-encryption of data with the new farm encryption key if a previous attempt failed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPHelp.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPHelp.md deleted file mode 100644 index 1cb9842493..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPHelp.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-sphelp -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPHelp -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPHelp - -## SYNOPSIS -Updates SharePoint cmdlet help. - - -## SYNTAX - -``` -Update-SPHelp [-AssignmentCollection <SPAssignmentCollection>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The Update-SPHelp cmdlet checks the Windows Download Center for updates for the SharePoint Management Shell help files against the version of the help files on the local computer. If there updates available, the cmdlet will download and install these updates. By default, the cmdlet will allow checking for updates only once every 24 hours. To override this check, use the Force parameter. - -The computer that the cmdlet is being run on must have an internet connection. - -Note: This cmdlet currently does not update cmdlet help. - - -## EXAMPLES - -### --------------------EXAMPLE 1--------------------- -``` -Update-SPHelp -``` -Updates SharePoint cmdlet help. - -### --------------------EXAMPLE 2--------------------- -``` -Update-SPHelp -Force -``` - -This example over-rides the throttling logic and checks for updates to the help files even if a check was made in the last 24 hours. - -### --------------------EXAMPLE 3--------------------- -``` -Update-SPHelp -Verbose -``` - -This example checks for updates to the help files and provides detailed feedback for each step of the process. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -NOTE: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Force -Over-rides the throttling logic and checks for updates to the help files even if a check was made in the last 24 hours. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathAdminFileUrl.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathAdminFileUrl.md deleted file mode 100644 index a6607e3f4d..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathAdminFileUrl.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spinfopathadminfileurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPInfoPathAdminFileUrl -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPInfoPathAdminFileUrl - -## SYNOPSIS -Updates InfoPath form templates (.xsn files) and universal data connections (.udcx files), including all .xsn files and .udcx files that were deployed by an administrator. - -## SYNTAX - -``` -Update-SPInfoPathAdminFileUrl -Find <Uri> -Replace <Uri> [-AssignmentCollection <SPAssignmentCollection>] - [-Confirm] [-Scan] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPInfoPathAdminFileUrl` cmdlet updates data connections in administrator-approved InfoPath form templates (.xsn files) and universal data connections (.udcx files). -This allows for InfoPath data connections that reference the current farm to be updated when content is migrated to a different farm URL. -This cmdlet cannot update any references to URLs that exist in form template business logic (code). -Typically, this cmdlet is used with the `Import-SPInfoPathAdministratorFiles` cmdlet. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPWebApplication http://contoso2010 | Update-SPInfoPathAdminFileUrl --find "http://contoso2007/" --replace "http://contoso2010/" -``` - -This example updates data connections in administrator-approved InfoPath form templates and universal data connection files. -Data connections that reference http://contoso 2007 are updated to reference http://contoso2010. - -## PARAMETERS - -### -Find -Specifies the URL to find. - -The type must be a valid URL, in the form http://previous_server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Replace -Specifies the URL to find. - -The type must be a valid URL, in the form http://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scan -Run the tool and log the actions that can be taken. -No content is changed as a result of the scan. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathFormTemplate.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathFormTemplate.md deleted file mode 100644 index 6528a2434b..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathFormTemplate.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Office.InfoPath.Server.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spinfopathformtemplate -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPInfoPathFormTemplate -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPInfoPathFormTemplate - -## SYNOPSIS -Upgrades all InfoPath form templates on the farm. - -## SYNTAX - -``` -Update-SPInfoPathFormTemplate [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPInfoPathFormTemplate` cmdlet upgrades all the InfoPath form templates on a farm that were deployed by an administrator. -Use this cmdlet after the farm is upgraded to a new version. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ---------------EXAMPLE-------------- -``` -Update-SPInfoPathFormTemplate -``` - -This example updates InfoPath form templates on the entire farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathUserFileUrl.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathUserFileUrl.md deleted file mode 100644 index 5d6e7baee5..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathUserFileUrl.md +++ /dev/null @@ -1,234 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spinfopathuserfileurl -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPInfoPathUserFileUrl -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPInfoPathUserFileUrl - -## SYNOPSIS -Updates InfoPath form templates (.xsn files) and universal data connections (.udcx files). - - -## SYNTAX - -### ContentDB -``` -Update-SPInfoPathUserFileUrl [-ContentDatabase] <SPContentDatabasePipeBind> -Find <Uri> -Replace <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Scan] [-WhatIf] [<CommonParameters>] -``` - -### Site -``` -Update-SPInfoPathUserFileUrl [-Site] <SPSitePipeBind> -Find <Uri> -Replace <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Scan] [-WhatIf] [<CommonParameters>] -``` - -### WebApp -``` -Update-SPInfoPathUserFileUrl [-WebApplication] <SPWebApplicationPipeBind> -Find <Uri> -Replace <Uri> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-Scan] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see Cmdlet Parameter Sets (https://go.microsoft.com/fwlink/?LinkID=187810). - -The `Update-SPInfoPathAdminFileUrl` cmdlet updates data connections in InfoPath form templates (.xsn files) and universal data connections (.udcx files). -This allows for InfoPath data connections that reference the current farm to be updated when content is migrated to a different farm URL. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Get-SPWebApplication http://contoso2010 | Update-SPInfoPathUserFileUrl -Find "http://contoso2007/" -Replace "http://contoso2010/" -``` - -This example updates data connections in InfoPath form templates and universal data connection files, for all content under the Web application http://contoso2010. - -Data connections that reference http://contoso2007 are updated to reference http://contoso2010. - -## PARAMETERS - -### -ContentDatabase -Specifies the parent content database where the update will start. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a content database (for example, SPContent DB1); or an instance of a valid SPContentDatabase object. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: ContentDB -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Specifies the parent site collection where the update will start. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form http://sites/example; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: Site -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the parent SharePoint Web application where the update will start. - -The type must be a valid URL, in the form http://server_name; a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: WebApp -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Find -Specifies the URL to find. - -The type must be a valid URL, in the form http://previous_server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Replace -Specifies the URL to find. - -The type must be a valid URL, in the form http://server_name. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Scan -Run the tool and log the actions that can be taken. -No content is changed as a result of the scan. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfilePhotoStore.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfilePhotoStore.md deleted file mode 100644 index e12128b591..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfilePhotoStore.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spprofilephotostore -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPProfilePhotoStore -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPProfilePhotoStore - -## SYNOPSIS -Updates the profile photo store to be compatible with SharePoint Server. - -## SYNTAX - -``` -Update-SPProfilePhotoStore -MySiteHostLocation <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-CreateThumbnailsForImportedPhotos <Boolean>] - [-NewBaseUri <Uri>] [-NoDelete <Boolean>] [-OldBaseUri <Uri>] [<CommonParameters>] -``` - -## DESCRIPTION -After upgrading from Office SharePoint Server to SharePoint Server, run the `Update-SPProfilePhotoStore` cmdlet to ensure that the SharePoint profile photo store is compatible with SharePoint Server. -The `Update-SPProfilePhotoStore` cmdlet should be used only after an upgrade from Office SharePoint Server has completed. -When the `Update-SPProfilePhotoStore` cmdlet is used, three thumbnail versions with predictable sizes and names are created from the original photo, the new photos are placed into the My Site Host's User Photos library, and the property value in the profile database is updated. - -During the operation, the original image is left as-is. -If the operation fails for certain users for any reason, it continues on to the next user. - -During the migration of profile photos from one server URL to another, one can use the OldBaseUri and NewBaseUri parameters. -You just need to specify the starting portion of the URL that has changed from old to new and an attempt to rebase the profile picture URLs will occur. - -For example, OldBaseUri: https://server1/my/ProfilePhotos; NewBaseUri: https://server1/my/NewLocation/ProfilePhotos - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------- -``` -Update-SPProfilePhotoStore -MySiteHostLocation https://mysites -``` - -This example uploads photos to a specified My Site host location. - -## PARAMETERS - -### -MySiteHostLocation -Specifies the URL for the My Site host location where the photos are to be uploaded. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CreateThumbnailsForImportedPhotos -Creates thumbnails for all the imported user profile pictures. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NewBaseUri -Specifies the new URL for profile pictures. -For example, https://server2/. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoDelete -When the value is set to true, imported user profile picture files will be preserverd after creating thumbnails for them. -> [!NOTE] -> This will only work when CreateThumbnailsForImportedPhotos is set to `$true` - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OldBaseUri -Specifies the old URL for profile pictures. -For example, https://server1/. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfileSync.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfileSync.md deleted file mode 100644 index 2cceedf547..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfileSync.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spprofilesync -applicable: -title: Update-SPProfileSync -online version: -schema: 2.0.0 ---- - -# Update-SPProfileSync - -## SYNOPSIS -Updates the configuration of the User Profile Synchronization job based on the parameters specified. - -## SYNTAX - -``` -Update-SPProfileSync [[-ExcludeWebApplications] <String>] [[-SynchronizationTiming] <String>] - [[-SweepTiming] <String>] [[-IgnoreIsActive] <Boolean>] [-AssignmentCollection <SPAssignmentCollection>] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The Update-SPProfileSync cmdlet updates the configuration of the User Profile Synchronization job based on the parameters specified. - -## EXAMPLES - -### EXAMPLE 1 -``` -Update-SPProfileSync -IgnoreIsActive:$false -``` - -This example updates the User Profile Synchronization job marking it to sync all users irrespective of their activity, without prompting for user confirmation. - -### EXAMPLE 2 -``` -Update-SPProfileSync -SynchronizationTiming "every 15 minutes" -``` - -This example updates the User Profile Synchronization job marking it to run every 15 minutes, without prompting for user confirmation. - -## PARAMETERS - -### -ExcludeWebApplications -Comma-delimited list of Web application URLs to exclude from consideration in the synchronization process. - -The values specified delete any existing values set. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SynchronizationTiming -Sets the schedule for the main synchronization job. -You can mention the schedule using a text string of SPSchedule format (for example, "every 15 minutes" means the job is scheduled to run every 15 minutes, "daily at 09:00:00" means the job is scheduled to run at 9 AM every day). - -The default is once per hour. - -You can use the SPSchedule.FromString() string method to pass in the strings, "every 5 minutes" or "weekly xxxxxxx". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: 2 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SweepTiming -Performs the same tasks as the SynchronizationTiming parameter. -However, the SweepTiming parameter sets the schedule for the "sweep" job. -The sweep job is driven by the SharePoint Foundation change log and is used as a lightweight way to capture new users added. -For example, you might have a fully synchronized site, but then a user is added to the site. -The sweep job ensures that the incremental newly added user gets the User Profile properties replicated quickly. - -The default value is every 1 minute. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: 3 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -IgnoreIsActive -Specifies whether to sync only active profiles or all profiles. -User profiles of users who contribute to the site are considered as Active. - -The valid values are True or False. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: 4 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPRepopulateMicroblogFeedCache.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPRepopulateMicroblogFeedCache.md deleted file mode 100644 index 630d125c75..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPRepopulateMicroblogFeedCache.md +++ /dev/null @@ -1,283 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-sprepopulatemicroblogfeedcache -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPRepopulateMicroblogFeedCache -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPRepopulateMicroblogFeedCache - -## SYNOPSIS - -Refreshes the microblog feed cache. - -## SYNTAX - -### (Default) - -``` -Update-SPRepopulateMicroblogFeedCache [-AccountName <String>] - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [-SiteUrl <String>] [<CommonParameters>] -``` - -### Default - -``` -Update-SPRepopulateMicroblogFeedCache [-AccountName <String>] - -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] - [-SiteUrl <String>] [<CommonParameters>] -``` - -### FollowableList - -``` -Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] -SiteSubscription <SPSiteSubscriptionPipeBind> -ListId <Guid> - -ListRootFolderUrl <String> -SiteId <Guid> -WebId <Guid> [<CommonParameters>] -``` - -## DESCRIPTION - -Use the `Update-SPRepopulateMicroblogFeedCache` cmdlet to refresh the feeds of a given user. -It can be used in scenarios where the automatic refresh has failed or when reverting to an old version of a user's personal site. - -When you refresh the cache, the `Update-SPRepopulateMicroblogLMTCache` cmdlet should be run first and then the `Update-SPRepopulateMicroblogFeedCache` cmdlet second. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE 1------------ - -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy $proxy -AccountName contoso\userName -``` - -This example refreshes the feed for a specific user by using the AccountName parameter. - -### ------------EXAMPLE 2------------ - -```powershell -$site = (Get-SPWebApplication -IncludeCentralAdministration | ?{$_.IsAdministrationWebApplication -eq $true}).Sites[0] -$context = Get-SPServiceContext $site -$upm = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($context) -$profiles = $upm.GetEnumerator() -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -while($profiles.MoveNext()) { - $profile = $profiles.Current - Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy $proxy -AccountName $profile.AccountName } -``` - -This example refreshes the feeds for all users in the User Profile Service Application. - -### ------------EXAMPLE 3------------ - -```powershell -Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy $proxy -SiteUrl https://sharepoint.contoso.com -``` - -This example refreshes the feed on the site https://sharepoint.contoso.com. - -## PARAMETERS - -### -AccountName - -Specifies the user's account name for the User Profile Service application. - -```yaml -Type: String -Parameter Sets: (All), Default -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ProfileServiceApplicationProxy - -Specifies the User Profile Service application proxy to update. - -The type must be in one of the following forms: - ---A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh ---A valid name of a service application proxy (for example, UserProfileSvcProxy1) ---An instance of a valid SPServiceApplicationProxy object - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection - -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteSubscription - -Specifies the account under which this service should run. -This parameter is mandatory in a hosted-environment and optional in a non-hosted environment. - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: (All), Default -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -```yaml -Type: SPSiteSubscriptionPipeBind -Parameter Sets: FollowableList -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -SiteUrl - -Specifies the Site's URL to repopulate the site feeds. If you don't specify this parameter, you must specify the AccountName parameter. If neither parameter is specified, an error message is displayed. - -```yaml -Type: String -Parameter Sets: (All), Default -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ListId - -The ListId of the FollowableList. - -```yaml -Type: Guid -Parameter Sets: FollowableList -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ListRootFolderUrl - -The RootFolderUrl of the FollowableList. - -```yaml -Type: String -Parameter Sets: FollowableList -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteId - -The SiteId containing the FollowableList. - -```yaml -Type: Guid -Parameter Sets: FollowableList -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebId - -The WebId containing the FollowableList. - -```yaml -Type: Guid -Parameter Sets: FollowableList -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Update-SPRepopulateMicroblogLMTCache](Update-SPRepopulateMicroblogLMTCache.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPRepopulateMicroblogLMTCache.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPRepopulateMicroblogLMTCache.md deleted file mode 100644 index 41c40e4001..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPRepopulateMicroblogLMTCache.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-sprepopulatemicrobloglmtcache -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPRepopulateMicroblogLMTCache -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPRepopulateMicroblogLMTCache - -## SYNOPSIS -Refreshes the cache. - -## SYNTAX - -``` -Update-SPRepopulateMicroblogLMTCache -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Update-SPRepopulateMicroblogLMTCache` cmdlet to refresh when the Feed Cache Repopulation Job timer job fails to work. -The `Update-SPRepopulateMicroblogLMTCache` cmdlet forcefully refreshes the last modified times of all the known persisted entities to FeedCache. - -When you refresh the cache, the `Update-SPRepopulateMicroblogLMTCache` cmdlet should be run first and then the `Update-SPRepopulateMicroblogFeedCache` cmdlet second. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------EXAMPLE----------- -``` -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'} -Update-SPRepopulateMicroblogLMTCache -ProfileServiceApplicationProxy $proxy -``` - -This example refreshes the cache for the specified proxy. - -## PARAMETERS - -### -ProfileServiceApplicationProxy -Specifies the User Profile Service application proxy to update. - -The type must be in one of the following forms: - - ---A valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh - ---A valid name of a service application proxy (for example, UserProfileSvcProxy1) - ---An instance of a valid SPServiceApplicationProxy object - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Update-SPRepopulateMicroblogFeedCache](Update-SPRepopulateMicroblogFeedCache.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreApplicationServerKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreApplicationServerKey.md deleted file mode 100644 index 21984ed91f..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreApplicationServerKey.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spsecurestoreapplicationserverkey -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPSecureStoreApplicationServerKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPSecureStoreApplicationServerKey - -## SYNOPSIS -Synchronizes the key on a Microsoft SharePoint server with the Secure Store master key. - -## SYNTAX - -``` -Update-SPSecureStoreApplicationServerKey -Passphrase <String> - -ServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPSecureStoreApplicationServerKey` cmdlet synchronizes the key on a SharePoint server with the master key for the Secure Store service database. - -Updating a server key is required when: - ---A new SharePoint server that will run a Secure Store service instance is joined to the farm. ---The key stored in the server is not the key required for the current Secure Store service database (because of server or networking issues). ---The master key is updated but during propagation of the new key, this process fails on one or more of the servers. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$newPassPhrase = "abcDEF123!" -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'Secure Store Service Application Proxy'} -Update-SPSecureStoreApplicationServerKey -ServiceApplicationProxy $proxy -Passphrase $newPassPhrase -``` - -This example synchronizes the passphrase of the server key on a SharePoint server with the master key for the Secure Store service database. - -## PARAMETERS - -### -Passphrase -Specifies the passphrase that is used for the Secure Store service database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplicationProxy -Specifies the proxy of the service application that contains the server key to synchronize. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreCredentialMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreCredentialMapping.md deleted file mode 100644 index 32226d6360..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreCredentialMapping.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spsecurestorecredentialmapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPSecureStoreCredentialMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPSecureStoreCredentialMapping - -## SYNOPSIS -Sets a new credential mapping for a Secure Store Service application. - -## SYNTAX - -``` -Update-SPSecureStoreCredentialMapping -Identity <SPSecureStoreApplication> -Principal <SPClaim> - -Values <SecureString[]> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPSecureStoreCredentialMapping` cmdlet sets a new credential mapping for a Secure Store Service application. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApplication" -$firstCredential = ConvertTo-SecureString "LOBDATABASE\jdoe" -AsPlainText -Force -$secondCredential = ConvertTo-SecureString "abcDEF123$%^" -AsPlainText -Force -$credentialValues = $firstCredential,$secondCredential -$userClaim = New-SPClaimsPrincipal -Identity "CONTOSO\janedoe" -IdentityType WindowsSamAccountName -Update-SPSecureStoreCredentialMapping -Identity $ssApp -Values $credentialValues -Principal $userClaim -``` - -This example updates a credential mapping for the given site and the target application ContosoTargetApplication, for the user with the identity janedoe on domain CONTOSO. -This user is mapped to a pair of credential values on the External System with a username of identity jdoe on domain LOBDATABASE and password abcDEF123$%^. - -## PARAMETERS - -### -Identity -Specifies the Secure Store Service application (that contains the principal) from which to delete the credential mapping. - -```yaml -Type: SPSecureStoreApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Principal -Specifies the SPClaims object that contains the principal. - -```yaml -Type: SPClaim -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Values -Specifies the field values for the credential mapping. - -```yaml -Type: SecureString[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreGroupCredentialMapping.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreGroupCredentialMapping.md deleted file mode 100644 index 4bd9021acd..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreGroupCredentialMapping.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spsecurestoregroupcredentialmapping -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPSecureStoreGroupCredentialMapping -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPSecureStoreGroupCredentialMapping - -## SYNOPSIS -Sets a new group credential mapping for a Secure Store Service application. - -## SYNTAX - -``` -Update-SPSecureStoreGroupCredentialMapping -Identity <SPSecureStoreApplication> -Values <SecureString[]> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPSecureStoreGroupCredentialMapping` cmdlet sets a new group credential mapping for a Secure Store Service application. -Group credentials are a set of credentials that are associated with multiple identities. -Target applications will get credentials for a Secure Store application by using the current user. -If the current user meets the authorization rule defined in the Secure Store application for the group credentials, then the data is provided. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoGroupTargetApplication" -$firstCredential = ConvertTo-SecureString "LOBDATABASE\fulltimeemployees" -AsPlainText -Force -$secondCredential = ConvertTo-SecureString "abcDEF123$%^" -AsPlainText -Force -$credentialValues = $firstCredential,$secondCredential -Update-SPSecureStoreGroupCredentialMapping -Identity $ssApp -Values $credentialValues -``` - -This example adds a credential mapping for the target application ContosoGroupTargetApplication, for all users in this group target application. -These users are mapped to a pair of credential values on the External System with a username of identity fulltimeemployees on domain LOBDATABASE and with password abcDEF123$%^. - -## PARAMETERS - -### -Identity -Specifies the Secure Store application (that contains the principal) from which to delete the credential mapping. - -```yaml -Type: SPSecureStoreApplication -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Values -Specifies the field values for the credential mapping. - -```yaml -Type: SecureString[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreMasterKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreMasterKey.md deleted file mode 100644 index 887f7bc9f7..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSecureStoreMasterKey.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spsecurestoremasterkey -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPSecureStoreMasterKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPSecureStoreMasterKey - -## SYNOPSIS -Changes the master key of a Secure Store Service application. - -## SYNTAX - -``` -Update-SPSecureStoreMasterKey -Passphrase <String> -ServiceApplicationProxy <SPServiceApplicationProxyPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPSecureStoreApplicationServerKey` cmdlet changes the master key of a Secure Store Service application. - -Updating the master key is required when: - - ---A new instance of a service application is created and the database for the Secure Store service application is new or empty. - ---The master key or passphrase has been compromised. - ---Security guidelines require that the passphrase or key be replaced. - - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -$newPassPhrase = "abcDEF123!" -$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'Secure Store Service Application Proxy'} -Update-SPSecureStoreMasterKey -ServiceApplicationProxy $proxy -Passphrase $newPassPhrase -``` - -This example creates a new master key for the given service application. - -## PARAMETERS - -### -Passphrase -Specifies the passphrase that is used for the Secure Store database. -The passphrase that you enter is not stored. -Make sure that you write down the passphrase and store it in a secure location. -The passphrase will be required to add new Secure Store service servers. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceApplicationProxy -Specifies the proxy of the Secure Store service application that contains the master key to update. - -```yaml -Type: SPServiceApplicationProxyPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSolution.md deleted file mode 100644 index dc2087defe..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPSolution.md +++ /dev/null @@ -1,248 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spsolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPSolution - -## SYNOPSIS -Upgrades a deployed SharePoint solution. - - -## SYNTAX - -``` -Update-SPSolution [-Identity] <SPSolutionPipeBind> -LiteralPath <String> - [-AssignmentCollection <SPAssignmentCollection>] [-CASPolicies] [-Confirm] [-Force] [-GACDeployment] [-Local] - [-Time <String>] [-WhatIf] [-FullTrustBinDeployment] [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPSolution` cmdlet upgrades a deployed SharePoint solution in the farm. -Use this cmdlet only if a new solution contains the same set of files and features as the deployed solution. -If files and features are different, the solution must be retracted and redeployed by using the `Uninstall-SPSolution` and `Install-SPSolution` cmdlets, respectively. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Update-SPSolution -Identity contoso_solution.wsp -LiteralPath c:\contoso_solution_v2.wsp -GACDeployment -``` - -This example upgrades the deployed SharePoint solution contoso_solution.wsp to the solution c:\contoso_solution_v2.wsp. - -## PARAMETERS - -### -Identity -Specifies the SharePoint solution to deploy. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint solution (for example, SPSolution1); or an instance of a valid SPSolution object. - -```yaml -Type: SPSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -LiteralPath -Specifies the path to the solution package. - -The type must be a valid path in either of the following forms: - -- C:\folder_name -- \\\\server_name\folder_name - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -CASPolicies -Specifies that Code Access Security (CAS) policies can be deployed for the new SharePoint solution. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Forces the deployment of the new SharePoint solution. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GACDeployment -Specifies that the new SharePoint solution can be deployed to the global assembly cache (GAC). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Local -Deploys the solution on the local computer only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Time -Specifies when the solution will be deployed. -The default value is immediate deployment. - -The type must be a valid DateTime value, in the form 2010, 5, 1. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FullTrustBinDeployment -Specifies whether to deploy using fully trusted bin. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPUserSolution.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPUserSolution.md deleted file mode 100644 index f7b7e692ea..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPUserSolution.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spusersolution -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPUserSolution -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPUserSolution - -## SYNOPSIS -Upgrades an activated sandboxed solution in a farm. - - -## SYNTAX - -``` -Update-SPUserSolution [-Identity] <SPUserSolutionPipeBind> -Site <SPSitePipeBind> - -ToSolution <SPUserSolutionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPUserSolution` cmdlet upgrades a sandboxed solution that has already been activated in a specified site collection. -A user solution is a sandboxed solution. -Before you use this cmdlet to upgrade the activated solution, use the Add-SPUserSolution cmdlet to upload the upgraded solution to the solution gallery. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE--------------------- -``` -Update-SPUserSolution -Identity contoso_solution.wsp -Site https://sitename -ToSolution contoso_solution_v2.wsp -``` - -This example upgrades the sandboxed solution contoso_solution.wsp in the site https://sitename to the sandboxed solution contoso_solution_v2.wsp. - -## PARAMETERS - -### -Identity -Specifies the sandboxed solution to upgrade. - -The type must be a valid name of a sandboxed solution (for example, UserSolution1); or an instance of a valid SPUserSolution object. - -```yaml -Type: SPUserSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Site -Upgrade the sandboxed solution for the specified site collection. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form https://server_name; or an instance of a valid SPSite object. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ToSolution -Specifies the sandboxed solution you want to upgrade to. - -The type must be a valid name of a sandboxed solution (for example, UserSolution1); or an instance of a valid SPUserSolution object. - -```yaml -Type: SPUserSolutionPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPWOPIProofKey.md b/sharepoint/sharepoint-ps/sharepoint-server/Update-SPWOPIProofKey.md deleted file mode 100644 index 3ee007f3f1..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Update-SPWOPIProofKey.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/update-spwopiproofkey -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Update-SPWOPIProofKey -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Update-SPWOPIProofKey - -## SYNOPSIS -Updates the public key that is used to connect to the WOPI application on the current SharePoint farm where this cmdlet is run. - - -## SYNTAX - -``` -Update-SPWOPIProofKey [-AssignmentCollection <SPAssignmentCollection>] [-ServerName <String>] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Update-SPWOPIProofKey` cmdlet updates the public key that is used to connect to the WOPI application (which could be a server that runs Office Web Apps Server) on the current SharePoint farm where this cmdlet is run. -You may want to use this cmdlet if the keys become unsynchronized between the SharePoint farm and the WOPI application. -If the keys are unsynchronized, documents may not open in the browser and messages such as "Invalid Proof Signature for file..." or "Invalid Proof Signature for folder..." are found in the Unified Logging System (ULS) logs. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Update-SPWOPIProofKey -ServerName "Server.corp.Contoso.com" -``` - -This example obtains the current public key from the WOPI application (such as a server that runs Office Web Apps Server) and updates the key that is stored on the SharePoint farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ServerName -Specifies the WOPI application to obtain the key from. -This may be a server that runs Office Web Apps Server. -If this parameter is missing, public keys for all WOPI applications which are connected to the current SharePoint farm, are updated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Content roadmap for Office Web Apps]() - -[Use Office Web Apps with SharePoint 2013]() diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPAppManagementServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPAppManagementServiceApplication.md deleted file mode 100644 index e8404e5f25..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPAppManagementServiceApplication.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spappmanagementserviceapplication -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPAppManagementServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPAppManagementServiceApplication - -## SYNOPSIS -Do Not Use - -## SYNTAX - -### AppManagementSvcAppById -``` -Upgrade-SPAppManagementServiceApplication [[-Identity] <SPServiceApplicationPipeBind>] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-DatabaseIds <Guid[]>] [-WhatIf] - [<CommonParameters>] -``` - -### AppManagementSvcAppByName -``` -Upgrade-SPAppManagementServiceApplication [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-DatabaseIds <Guid[]>] [-Name <String>] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Do Not Use - -## EXAMPLES - -### --------------EXAMPLE----------------- -``` -Do Not Use -``` - - - -## PARAMETERS - -### -AssignmentCollection -Do Not Use - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseIds -Do Not Use - -```yaml -Type: Guid[] -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Do Not Use - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: AppManagementSvcAppById -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Name -Do Not Use - -```yaml -Type: String -Parameter Sets: AppManagementSvcAppByName -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPContentDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPContentDatabase.md deleted file mode 100644 index 51a35f55e8..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPContentDatabase.md +++ /dev/null @@ -1,319 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spcontentdatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPContentDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPContentDatabase - -## SYNOPSIS -Resumes a failed database upgrade or begins a build-to-build database upgrade. - - -## SYNTAX - -### ContentDatabaseById -``` -Upgrade-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [-ForceDeleteLock] - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-NoB2BSiteUpgrade] - [-ServerInstance <SPDatabaseServiceInstancePipeBind>] [-SkipIntegrityChecks] [-UseSnapshot] [-WhatIf] - [-AllowUnattached] [-SkipSiteUpgrade] [<CommonParameters>] -``` - -### ContentDatabaseByName -``` -Upgrade-SPContentDatabase [-ForceDeleteLock] -Name <String> -WebApplication <SPWebApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-NoB2BSiteUpgrade] - [-ServerInstance <SPDatabaseServiceInstancePipeBind>] [-SkipIntegrityChecks] [-UseSnapshot] [-WhatIf] - [-AllowUnattached] [-SkipSiteUpgrade] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet contains more than one parameter set. -You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. -For more information about how to use parameter sets, see [Cmdlet Parameter Sets](https://go.microsoft.com/fwlink/?LinkID=187810). - -Use the `Upgrade-SPContentDatabase` cmdlet to resume a failed database upgrade or begin a build-to-build database upgrade against a SharePoint content database. -The `Upgrade-SPContentDatabase` cmdlet initiates an upgrade of an existing content database that is attached to the current farm. -This cmdlet begins a new upgrade session, which can be used either to resume a failed version-to-version or build-to-build upgrade of a content database or to begin a build-to-build upgrade of a content database. - -If the database is hosted on a version of SQL Server that supports creation and use of snapshots of the database, this cmdlet can use a database snapshot for build-to-build upgrades. -During upgrade, users see a ready-only version of the database, which is the snapshot. -After upgrade users see upgraded content. - -The default behavior of this cmdlet causes an upgrade of the schema of the database and initiates build-to-build upgrades for all site collections within the specified content database if required. -To prevent build-to-build upgrades of site collections, use the NoB2BSiteUpgrade parameter. - -This cmdlet does not trigger version-to-version upgrade of any site collections. - - -## EXAMPLES - -### --------------------------EXAMPLE 1------------------------------ -``` -Upgrade-SPContentDatabase WSS_Content -``` - -This example upgrades the existing WSS_Content content database schema and then performs only build-to-build upgrade actions on existing site collections if required. -This operation does not changed the CompatibilityLevel for existing site collections in this database. - -### --------------------------EXAMPLE 2------------------------------ -``` -Upgrade-SPContentDatabase WSS_Content -NoB2BSiteUpgrade -``` - -This example upgrades the existing WSS_Content content database schema only. -No build-to-build upgrade actions are performed on any site collections. -This operation does not change The CompatibilityLevel for existing site collections in this database. - -### --------------------------EXAMPLE 3------------------------------ -``` -Upgrade-SPContentDatabase WSS_Content -NoB2BSiteUpgrade -UseSnapshot -``` - -This example upgrades the existing WSS_Content content database schema only while using a snapshot of the database to retain read-only access to the content during the upgrade. -No build-to-build upgrade actions are performed on any site collections. -This operation does not change the CompatibilityLevel for existing site collections in this database. - -## PARAMETERS - -### -Identity -Specifies the content database to upgrade. - -The value must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh or an instance of a valid SPContentDatabase object. - -```yaml -Type: SPContentDatabasePipeBind -Parameter Sets: ContentDatabaseById -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -ForceDeleteLock -Forces deletion of locks on the database before the upgrade starts. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Specifies the name of attached content database. - -```yaml -Type: String -Parameter Sets: ContentDatabaseByName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WebApplication -Specifies the web application that hosts the attached content database. - -```yaml -Type: SPWebApplicationPipeBind -Parameter Sets: ContentDatabaseByName -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NoB2BSiteUpgrade -Specifies to not upgrade all child objects when performing a build-to-build upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServerInstance -The SQL Server instance that hosts the attached content database. - -```yaml -Type: SPDatabaseServiceInstancePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipIntegrityChecks -Specifies the upgrade process not to run the internal integrity checks such as missing templates and orphan detection as part of the upgrade process. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseSnapshot -Specifies to use the snapshot method to perform unattached upgrade. -This will make a snapshot of the current database and then perform all upgrade operations that apply to the database and optionally to its contents. - -The existing connections to the content database will be set to use the snapshot for the duration of the upgrade and then switched back after successful completion of upgrade. -A failed upgrade reverts the database to its state when the snapshot was taken. - -This parameter only works for versions of SQL Server that support creation and use of snapshots, for example, SQL ServerEnterprise edition. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUnattached -Lets the upgrade process to proceed on a content database which is not currently attached to a SharePoint farm. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipSiteUpgrade -Specifies to not upgrade databases and their child objects when performing upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: NoB2BSiteUpgrade -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPEnterpriseSearchServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPEnterpriseSearchServiceApplication.md deleted file mode 100644 index 80adadefe3..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPEnterpriseSearchServiceApplication.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spenterprisesearchserviceapplication -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPEnterpriseSearchServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPEnterpriseSearchServiceApplication - -## SYNOPSIS -Upgrades a search service application. - -## SYNTAX - -``` -Upgrade-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet starts an upgrade process on a search service application. -This cmdlet runs the associated upgrade actions for the search service application. -Also, you can upgrade multiple search service applications in parallel by starting several instances of this cmdlet. -It is not necessary to run this cmdlet if you already have run the SharePoint Products Configuration Wizard. - -For the upgrade process to run successful, all of the computers in the farm must have the same version of binaries installed. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ----------------EXAMPLE 1----------------- -``` -Get-SPEnterpriseSearchServiceApplication | Upgrade-SPEnterpriseSearchServiceApplication -``` - -This example upgrades a search service application. - -### ----------------EXAMPLE 2----------------- -``` -Upgrade-SPEnterpriseSearchServiceApplication -Identity 846ceb0b-31d6-4c79-82c1-3a9deafe0b45 -``` - -This example upgrades a search service application. - -### ----------------EXAMPLE 3----------------- -``` -Upgrade-SPEnterpriseSearchServiceApplication "DefaultSearchApplication" -``` - -This example upgrades a search service application. - -## PARAMETERS - -### -Identity -Specifies the search service application to upgrade. - -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. - -```yaml -Type: SearchServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings.md deleted file mode 100644 index d11615c236..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.Office.Server.Search.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spenterprisesearchserviceapplicationsitesettings -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings - -## SYNOPSIS -Upgrades search settings for a particular site collection. - -## SYNTAX - -``` -Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings -Identity <SPSitePipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings` cmdlet to upgrade the search settings for specified site collection from 2010 to 2013 experience. -The upgrades include conversion of best bets to query rules. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### --------EXAMPLE-------- -``` -C:\PS>$site= Get-SPSite https://test - -Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings -Identity $site -``` - -This example upgrades the search settings for the site collection referenced by $site. - - -## PARAMETERS - -### -Identity -Specifies the site collection for which to upgrade search settings. -The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Remove-SPEnterpriseSearchServiceApplicationSiteSettings](Remove-SPEnterpriseSearchServiceApplicationSiteSettings.md) diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPFarm.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPFarm.md deleted file mode 100644 index b24ada9f5c..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPFarm.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spfarm -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPFarm -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPFarm - -## SYNOPSIS -Activates the Upgrade method for the local farm. - - -## SYNTAX - -``` -Upgrade-SPFarm [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [-ServerOnly] - [-SkipDatabaseUpgrade] [-SkipSiteUpgrade] [<CommonParameters>] -``` - -## DESCRIPTION -The `Upgrade-SPFarm` cmdlet starts the upgrade process on the local farm. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -----------EXAMPLE--------- -``` -Upgrade-SPFarm -``` - -This example starts the upgrade process on the local farm. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServerOnly -Specifies to only upgrade local server. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipDatabaseUpgrade -Specifies to not upgrade databases and their child objects when performing upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipSiteUpgrade -Specifies to not upgrade all site objects when performing upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: NoB2BSiteUpgrade -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPProfileServiceApplication.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPProfileServiceApplication.md deleted file mode 100644 index 96a10f1fec..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPProfileServiceApplication.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Office.Server.UserProfiles.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spprofileserviceapplication -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPProfileServiceApplication -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPProfileServiceApplication - -## SYNOPSIS -Upgrades User Profile Service and its related profile and social store. - -## SYNTAX - -``` -Upgrade-SPProfileServiceApplication [-Identity] <SPServiceApplicationPipeBind> - [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Upgrades User Profile Service and its related profile and social store. - -## EXAMPLES - -### -----------EXAMPLE--------- -``` -$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'User Profile Service Application'} -Upgrade-SPProfileServiceApplication $sa -``` - -This example upgrades the specified user profile service application. - -## PARAMETERS - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the User Profile Service application to update.The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a user profile service application (for example, UserProfileServiceApp); or an instance of a valid SPServiceApplication object. - -```yaml -Type: SPServiceApplicationPipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPServiceApplicationPipeBind -Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSingleSignOnDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSingleSignOnDatabase.md deleted file mode 100644 index 00057e0554..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSingleSignOnDatabase.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.SSOUpgrade-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spsinglesignondatabase -applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPSingleSignOnDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPSingleSignOnDatabase - -## SYNOPSIS -Migrates the application definitions from Single Sign-On (SSO) database to Secure Store database as target applications. - -## SYNTAX - -``` -Upgrade-SPSingleSignOnDatabase -SecureStoreConnectionString <String> -SecureStorePassphrase <SecureString> - -SSOConnectionString <String> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Upgrade-SPSingleSignOnDatabase` cmdlet migrates the application definitions from SSO database to Secure Store database as target applications. -Use the `Upgrade-SPSingleSignOn` cmdlet to convert an SSO database to a Secure Store database. -SSO is a SharePoint Server feature. -SSO functionality is performed by the Secure Store Service in SharePoint Server. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### ------------------EXAMPLE------------------ -``` -Upgrade-SPSingleSignOnDatabase -SSOConnectionString "Data Source=oldServer;Database=SSO;Trusted_Connection=yes;" -SecureStoreConnectionString "Data Source=CONTOSO\SQLDatabase;Database=ContosoSSDatabase;Trusted_Connection=yes;" -SecureStorePassphrase "abcDEF123!@#" -``` - -This example migrates the SSO database at the SSO connection to a Secure Store database at the Secure Store connection. - -## PARAMETERS - -### -SecureStoreConnectionString -Specifies the SQL Server connection string for the Secure Store database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SecureStorePassphrase -Specifies the passphrase used for the Secure Store database. - -```yaml -Type: SecureString -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SSOConnectionString -Specifies the SQL Server connection string for the SSO database. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSite.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSite.md deleted file mode 100644 index 8d24be1cb2..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSite.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -external help file: Microsoft.SharePoint.PowerShell.dll-help.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spsite -applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPSite -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPSite - -## SYNOPSIS -Starts the upgrade process on a site collection. - -## SYNTAX - -``` -Upgrade-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-Email] [-QueueOnly] [-Unthrottled] [-VersionUpgrade] [-WhatIf] [-Priority <Byte>] [<CommonParameters>] -``` - -## DESCRIPTION -The `Upgrade-SPSite` cmdlet starts the upgrade process on a site collection. - -The `Upgrade-SPSite` cmdlet activates the upgrade process for the specified SPSite object. -You can also use this cmdlet to resume failed upgrades. -When you use this cmdlet to initiate upgrade on an SPSite object, the object can be either a build-to-build or version-to-version upgrade. - -By default, the `Upgrade-SPSite` cmdlet operates as a build-to-build upgrade. -This prevents unexpected version upgrades of site collections if you use this cmdlet after a patching operation. -When in version-to-version upgrade mode, site collection health checks are run in repair mode to ensure that the site collection is healthy enough to upgrade successfully. -If successful, the remainder of the upgrade occurs. - -For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at [SharePoint Server Cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-server/sharepoint-server-cmdlets). - -## EXAMPLES - -### -------------EXAMPLE 1---------- -``` -Upgrade-SPSite https://<site name>/sites/testsite -``` - -This example upgrades the existing https://\<site name\>/sites/testsite site collection by using only build-to-build upgrade actions. -The SPSite.CompatibilityLevel will not be changed by this operation. - -### -------------EXAMPLE 2---------- -``` -Upgrade-SPSite https://<site name>/sites/testsite -VersionUpgrade -``` - -This example upgrades the existing https://\<site name\>/sites/testsite site collection by using only build-to-build upgrade actions. -The SPSite.CompatibilityLevel will not be changed by this operation. - -## PARAMETERS - -### -Identity -Specifies the SPSite object to run upgrade operations against. - -```yaml -Type: SPSitePipeBind -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -AssignmentCollection -Manages objects for the purpose of proper disposal. -Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. -Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. -When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. - -When the Global parameter is used, all objects are contained in the global store. -If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Email -Specifies whether to send mail on completion of the site collection upgrade. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -QueueOnly -Specifies to put the site into the queue for a delayed upgrade that is managed by a timer job. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Unthrottled -Specifies a farm administrator to bypass the throttle which permits a site collection to be upgraded even if there are "too many" site collections in the throttle to be upgraded. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VersionUpgrade -Specifies to perform a version-to-version upgrade on the SPSite object. -When this parameter is set, it internally triggers all available build-to-build actions that are associated with the current site collection operating mode. -Version-to-version actions follow to bring site collections to the next site collection operating mode inclusive of all new build-to-build actions that are associated with the new site collection operating mode. -When this parameter is not set, it triggers only available build-to-build upgrade actions that are associated with the current site collection operating mode. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Displays a message that describes the effect of the command instead of executing the command. -For more information, type the following command: `get-help about_commonparameters` - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -Specifies what priority to upgrade the site. - -The valid values are: - -* 128 - 255 (Low Priority) - -* 11 - 127 (Normal Priority) - -* 0 - 10 (High Priority) - -```yaml -Type: Byte -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSiteMapDatabase.md b/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSiteMapDatabase.md deleted file mode 100644 index 00728872ea..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/Upgrade-SPSiteMapDatabase.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: sharepointserver.xml -Module Name: Microsoft.Sharepoint.Powershell -online version: https://docs.microsoft.com/powershell/module/sharepoint-server/upgrade-spsitemapdatabase -applicable: SharePoint Server 2016, SharePoint Server 2019 -title: Upgrade-SPSiteMapDatabase -schema: 2.0.0 -author: techwriter40 -ms.author: kirks -ms.reviewer: ---- - -# Upgrade-SPSiteMapDatabase - -## SYNOPSIS -Do not use. - -## SYNTAX - -``` -Upgrade-SPSiteMapDatabase [-DatabaseId] <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm] - [-WhatIf] [<CommonParameters>] -``` - -## DESCRIPTION -Do not use. - -## EXAMPLES - -### -------------EXAMPLE 1---------- -``` -#Do not use -``` - -Do not use. - -## PARAMETERS - -### -AssignmentCollection -Do not use. - -```yaml -Type: SPAssignmentCollection -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DatabaseId -Do not use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: SharePoint Server 2016, SharePoint Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.SharePoint.PowerShell.SPAssignmentCollection - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md b/sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md deleted file mode 100644 index bba18c6a1e..0000000000 --- a/sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md +++ /dev/null @@ -1,3018 +0,0 @@ ---- -Module Name: SharePointServer -Module Guid: 01dfdcd9-c48d-46a9-b09a-587ca5c4829a -Help Version: 17.0.15229.2100 -Download Help Link: https://officedocs-cdn.azureedge.net/powershell/sharepoint/ -title: sharepoint-server -Additional Locale: de-DE,es-ES,fr-FR,it-IT,ja-JP,ko-KR,pt-BR,ru-RU,zh-CN,zh-TW -de-DE Version: 17.0.15229.2100 -es-ES Version: 17.0.15229.2100 -fr-FR Version: 17.0.15229.2100 -it-IT Version: 17.0.15229.2100 -ja-JP Version: 17.0.15229.2100 -ko-KR Version: 17.0.15229.2100 -pt-BR Version: 17.0.15229.2100 -ru-RU Version: 17.0.15229.2100 -zh-CN Version: 17.0.15229.2100 -zh-TW Version: 17.0.15229.2100 - ---- -# SharePoint Server - -## Description - -The following cmdlet references are for SharePoint Server. - -## sharepoint-server Cmdlets - -### Access Services (2010) - -#### [Get-SPAccessServiceApplication](Get-SPAccessServiceApplication.md) -Returns an Access Services application or a collection of Access Services applications. Platform: SharePoint 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPAccessServiceApplication](New-SPAccessServiceApplication.md) -Creates a new instance of an Access Services application in SharePoint Server. Platform: SharePoint 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAccessServiceApplication](Set-SPAccessServiceApplication.md) -Sets global properties of an existing Access Services application in SharePoint Server. Platform: SharePoint 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Access Services (2013) - -#### [Copy-SPAccessServicesDatabaseCredentials](Copy-SPAccessServicesDatabaseCredentials.md) -{{Enter description}}. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPAccessServicesDatabase](Export-SPAccessServicesDatabase.md) -Exports an Access Services Database to a DACPAC via the Data-Tier Framework. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAccessServicesApplication](Get-SPAccessServicesApplication.md) -Gets an Access Services Service Application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAccessServicesDatabase](Get-SPAccessServicesDatabase.md) -Returns an Access Services database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAccessServicesDatabaseServer](Get-SPAccessServicesDatabaseServer.md) -Returns SQL Server instances associated with Access Services. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAccessServicesDatabaseServerGroup](Get-SPAccessServicesDatabaseServerGroup.md) -Returns a database server group. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAccessServicesDatabaseServerGroupMapping](Get-SPAccessServicesDatabaseServerGroupMapping.md) -Returns the mapping of the database server group. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -##### [Import-SPAccessServicesDatabase](Import-SPAccessServicesDatabase.md) -Imports an Access Services Database to a DACPAC via the Data-Tier Framework. Platform: SharePoint Server 2016, SharePoint Server 2019. - -##### [New-SPAccessServicesApplication](New-SPAccessServicesApplication.md) -Creates an Access Services Service Application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPAccessServicesApplicationProxy](New-SPAccessServicesApplicationProxy.md) -Creates a Proxy for an Access Services Service Application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPAccessServicesDatabaseServer](New-SPAccessServicesDatabaseServer.md) -Adds a server to host Access Services databases. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPAccessServicesDatabaseServer](Remove-SPAccessServicesDatabaseServer.md) -Removes a database server for hosting Access Services databases. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Reset-SPAccessServicesDatabasePassword](Reset-SPAccessServicesDatabasePassword.md) -Resets the specified Access Services Database password with a randomly generated password. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAccessServicesApplication](Set-SPAccessServicesApplication.md) -Sets properties of an Access Services Service Application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAccessServicesDatabaseServer](Set-SPAccessServicesDatabaseServer.md) -SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAccessServicesDatabaseServerGroupMapping](Set-SPAccessServicesDatabaseServerGroupMapping.md) -SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -### SharePoint Addins - - -#### [Add-SPAppDeniedEndpoint](Add-SPAppDeniedEndpoint.md) -Adds a relative URL endpoint of a server to the list of app-denied endpoints. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPAppDeniedEndpointList](Clear-SPAppDeniedEndpointList.md) -Removes all app-denied endpoints in the farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPAppAutoProvision](Disable-SPAppAutoProvision.md) -Disables automatic provisioning of an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPAppAutoProvision](Enable-SPAppAutoProvision.md) -Enables automatic provisioning of an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPAppPackage](Export-SPAppPackage.md) -Exports an app package. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppAcquisitionConfiguration](Get-SPAppAcquisitionConfiguration.md) -Returns app acquisition settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppAutoProvisionConnection](Get-SPAppAutoProvisionConnection.md) -Returns provision connection settings for an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppDeniedEndpointList](Get-SPAppDeniedEndpointList.md) -Returns the app-denied endpoint list for the entire farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppDisablingConfiguration](Get-SPAppDisablingConfiguration.md) -Returns the disable sync list state for an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppDomain](Get-SPAppDomain.md) -Returns the domain used to host apps. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppHostingQuotaConfiguration](Get-SPAppHostingQuotaConfiguration.md) -Returns the hosting quotas for an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppInstance](Get-SPAppInstance.md) -Returns the metadata for an instance of an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppPrincipal](Get-SPAppPrincipal.md) -Displays a specific app principal object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppScaleProfile](Get-SPAppScaleProfile.md) -Returns settings for an app profile. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppSiteSubscriptionName](Get-SPAppSiteSubscriptionName.md) -Returns the name of the specified site subscription. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppStateSyncLastRunTime](Get-SPAppStateSyncLastRunTime.md) -Returns the latest time the app state update job was invoked. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppStateUpdateInterval](Get-SPAppStateUpdateInterval.md) -Returns the interval in hours between updates of the app state update job. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppStoreConfiguration](Get-SPAppStoreConfiguration.md) -Returns app SharePoint Store settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAppStoreWebServiceConfiguration](Get-SPAppStoreWebServiceConfiguration.md) -Returns properties of a SharePoint Store app. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPInternalAppStateSyncLastRunTime](Get-SPInternalAppStateSyncLastRunTime.md) -Returns the latest time the internal app state update job was invoked. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPInternalAppStateUpdateInterval](Get-SPInternalAppStateUpdateInterval.md) -Returns the interval in hours between updates of the internal app state update job. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPAppPackage](Import-SPAppPackage.md) -Imports an app package. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPApp](Install-SPApp.md) -Installs an instance of an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPMarketplaceWebServiceApplicationProxy](New-SPMarketplaceWebServiceApplicationProxy.md) -Creates a service application proxy for the app identity data web service. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Register-SPAppPrincipal](Register-SPAppPrincipal.md) -Lets an on-premises administrator register an app principal. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPAppDeniedEndpoint](Remove-SPAppDeniedEndpoint.md) -Removes a relative URL endpoint of a server from the list of app-denied endpoints. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPAppPrincipalPermission](Remove-SPAppPrincipalPermission.md) -Removes the permissions on a specified app principal. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Restart-SPAppInstanceJob](Restart-SPAppInstanceJob.md) -Restarts an app instance. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppAcquisitionConfiguration](Set-SPAppAcquisitionConfiguration.md) -Sets app acquisition settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppAutoProvisionConnection](Set-SPAppAutoProvisionConnection.md) -Sets provision connection settings for an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppDisablingConfiguration](Set-SPAppDisablingConfiguration.md) -Sets the disable list sync state for an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppDomain](Set-SPAppDomain.md) -Sets the domain used to host apps. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppHostingQuotaConfiguration](Set-SPAppHostingQuotaConfiguration.md) -Sets hosting quotas for an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppManagementDeploymentId](Set-SPAppManagementDeploymentId.md) -Sets the identifier of the farm or tenant used by the Office Marketplace to issue App licenses. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppPrincipalPermission](Set-SPAppPrincipalPermission.md) -Sets the permissions on a given app principal. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppScaleProfile](Set-SPAppScaleProfile.md) -Sets settings for the app profile. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppSiteDomain](Set-SPAppSiteDomain.md) -Creates or changes the URL of any installed app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppSiteSubscriptionName](Set-SPAppSiteSubscriptionName.md) -Sets or changes the name for the specified site subscription. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppStateUpdateInterval](Set-SPAppStateUpdateInterval.md) -Sets the interval in hours between updates of the app state update job. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppStoreConfiguration](Set-SPAppStoreConfiguration.md) -Sets SharePoint Store settings for an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAppStoreWebServiceConfiguration](Set-SPAppStoreWebServiceConfiguration.md) -Sets properties of a SharePoint Store app. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPInternalAppStateUpdateInterval](Set-SPInternalAppStateUpdateInterval.md) -Sets the interval in hours between updates of the internal app state update job. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPAppInstance](Uninstall-SPAppInstance.md) -Uninstalls an instance of an app. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPAppCatalogConfiguration](Update-SPAppCatalogConfiguration.md) -Sets a specific site collection as the App Catalog site collection. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPAppInstance](Update-SPAppInstance.md) -Updates the app instance. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### App Management Service - - -#### [New-SPAppManagementServiceApplication](New-SPAppManagementServiceApplication.md) -Creates an App Management Service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 -#### [New-SPAppManagementServiceApplicationProxy](New-SPAppManagementServiceApplicationProxy.md) -Creates an App Management Service application proxy. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 - -### Backup and Restore Operations -Backup and restore cmdlets. - -#### [Backup-SPConfigurationDatabase](Backup-SPConfigurationDatabase.md) -Performs a farm-level configuration-only backup. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Backup-SPFarm](Backup-SPFarm.md) -Creates a backup of an individual database, Web application, or the entire farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Backup-SPSite](Backup-SPSite.md) -Performs a backup of a site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPWeb](Export-SPWeb.md) -Exports a site, list, or library. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPBackupHistory](Get-SPBackupHistory.md) -Returns a history of backup and restore operations. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Restore-SPDeletedSite](Restore-SPDeletedSite.md) -Restores a deleted site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Restore-SPFarm](Restore-SPFarm.md) -Restores one or more items from a backup. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Restore-SPSite](Restore-SPSite.md) -Restores a site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Bing Maps - - -#### [Get-SPBingMapsBlock](Get-SPBingMapsBlock.md) -Returns Bing Maps blocked status. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPBingMapsKey](Get-SPBingMapsKey.md) -Returns the Bing Maps key. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPBingMapsBlock](Set-SPBingMapsBlock.md) -Sets Bing maps to blocked status. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPBingMapsKey](Set-SPBingMapsKey.md) -Sets the Bing Maps key. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Business Data Connectivity Services -Business Data Connectivity Services cmdlets. - -#### [Clear-SPBusinessDataCatalogEntityNotificationWeb](Clear-SPBusinessDataCatalogEntityNotificationWeb.md) -Clears the entity notification site. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Copy-SPBusinessDataCatalogAclToChildren](Copy-SPBusinessDataCatalogAclToChildren.md) -Copies a set of permissions of a Business Data Connectivity Metadata Store metadata object to its child objects. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPBusinessDataCatalogEntity](Disable-SPBusinessDataCatalogEntity.md) -Specifies content types for replicating from on-premises to SharePoint Online (SPO) environment. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPBusinessDataCatalogEntity](Enable-SPBusinessDataCatalogEntity.md) -Activates an External Content type in the Business Data Connectivity Metadata Store. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPBusinessDataCatalogModel](Export-SPBusinessDataCatalogModel.md) -Exports a Business Data Connectivity Model. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPBusinessDataCatalogEntityNotificationWeb](Get-SPBusinessDataCatalogEntityNotificationWeb.md) -Returns the entity notification site. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPBusinessDataCatalogMetadataObject](Get-SPBusinessDataCatalogMetadataObject.md) -Returns a Business Data Connectivity Metadata Store metadata object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPODataConnectionSetting](Get-SPODataConnectionSetting.md) -Returns Business Connectivity Services OData connection properties. PLatform: SharePoint Server 2013, SharePoint Server 2016. - -#### [Get-SPODataConnectionSettingMetadata](Get-SPODataConnectionSettingMetadata.md) -Returns a Business Data Connectivity service metadata object. Platform: SharePoint Server 2013, SharePoint Server 2016. - -#### [Get-SPBusinessDataCatalogThrottleConfig](Get-SPBusinessDataCatalogThrottleConfig.md) -Returns the throttling configuration for a Business Data Connectivity Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Grant-SPBusinessDataCatalogMetadataObject](Grant-SPBusinessDataCatalogMetadataObject.md) -rants a right to a principal for the specified Business Data Connectivity Metadata Store metadata object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPBusinessDataCatalogDotNetAssembly](Import-SPBusinessDataCatalogDotNetAssembly.md) -Imports a .NET Connectivity assembly. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPBusinessDataCatalogModel](Import-SPBusinessDataCatalogModel.md) -Imports a Business Data Connectivity Model. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPBusinessDataCatalogServiceApplication](New-SPBusinessDataCatalogServiceApplication.md) -Creates a new Business Data Connectivity service application in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPBusinessDataCatalogServiceApplicationProxy](New-SPBusinessDataCatalogServiceApplicationProxy.md) -Creates a new Business Data Connectivity service application proxy in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPBusinessDataCatalogModel](Remove-SPBusinessDataCatalogModel.md) -Deletes a Business Data Connectivity Model. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Revoke-SPBusinessDataCatalogMetadataObject](Revoke-SPBusinessDataCatalogMetadataObject.md) -Revokes a right to a principal in the specified Business Data Connectivity Metadata Store metadata object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPBusinessDataCatalogEntityNotificationWeb](Set-SPBusinessDataCatalogEntityNotificationWeb.md) -Sets the entity notification site. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPBusinessDataCatalogMetadataObject](Set-SPBusinessDataCatalogMetadataObject.md) -Sets the value of a property or attribute of a Business Data Connectivity Metadata Store metadata object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPBusinessDataCatalogServiceApplication](Set-SPBusinessDataCatalogServiceApplication.md) -Sets global properties for a Business Data Connectivity service application in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPBusinessDataCatalogThrottleConfig](Set-SPBusinessDataCatalogThrottleConfig.md) -Sets the throttling configuration for a Business Data Connectivity Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Database Operations - - -#### [Add-DatabaseToAvailabilityGroup](Add-DatabaseToAvailabilityGroup.md) -Adds one or more SharePoint databases to a SQL Server Availability Group. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPScaleOutDatabase](Add-SPScaleOutDatabase.md) -Adds an existing scale-out database to the specified service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPServerScaleOutDatabase](Add-SPServerScaleOutDatabase.md) -Adds an existing scale-out content database to the specified service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPScaleOutDatabaseDeletedDataSubRange](Clear-SPScaleOutDatabaseDeletedDataSubRange.md) -Clears all partitions inside the specified deleted subrange. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPScaleOutDatabaseLog](Clear-SPScaleOutDatabaseLog.md) -Clears all scale-out logs. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPScaleOutDatabaseTenantData](Clear-SPScaleOutDatabaseTenantData.md) -Removes all data related to the specified site subscription. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPServerScaleOutDatabaseDeletedDataSubRange](Clear-SPServerScaleOutDatabaseDeletedDataSubRange.md) -Clears all partitions inside the specified deleted subrange. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPServerScaleOutDatabaseLog](Clear-SPServerScaleOutDatabaseLog.md) -Clears all scale-out logs in the specified scale-out database unless there is a scale-out log entry newer than the specified time-out value.Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPServerScaleOutDatabaseTenantData](Clear-SPServerScaleOutDatabaseTenantData.md) -Removes all data related to the specified site subscription. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Dismount-SPContentDatabase](Dismount-SPContentDatabase.md) -Detaches a content database from its currently associated Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPScaleOutDatabaseTenantData](Export-SPScaleOutDatabaseTenantData.md) -Exports the data of the specified subscription. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPServerScaleOutDatabaseTenantData](Export-SPServerScaleOutDatabaseTenantData.md) -Exports the data of the specified subscription. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-AvailabilityGroupStatus](Get-AvailabilityGroupStatus.md) -Returns one or more objects representing the availability groups known to the SharePoint farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPContentDatabase](Get-SPContentDatabase.md) -Returns one or more content databases. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPContentDatabaseOrphanedData](Get-SPContentDatabaseOrphanedData -Gets orphaned data in content database. Platform: SharePoint Server 2019. - -#### [Get-SPDatabase](Get-SPDatabase.md). -Retrieves all properties of a database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPScaleOutDatabase](Get-SPScaleOutDatabase.md) -Returns all scale-out database objects. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPScaleOutDatabaseDataState](Get-SPScaleOutDatabaseDataState.md) -Returns the state information about the specified scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPScaleOutDatabaseInconsistency](Get-SPScaleOutDatabaseInconsistency.md) -Displays all inconsistencies related to scale-out databases' ranges. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPScaleOutDatabaseLogEntry](Get-SPScaleOutDatabaseLogEntry.md) -Queries a scale-out database for scale-out logs. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServerScaleOutDatabase](Get-SPServerScaleOutDatabase.md) -Returns all scale-out database objects. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServerScaleOutDatabaseDataState](Get-SPServerScaleOutDatabaseDataState.md) -Returns the state information about the specified scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServerScaleOutDatabaseInconsistency](Get-SPServerScaleOutDatabaseInconsistency.md) -Displays all inconsistencies related to scale-out databases' ranges. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServerScaleOutDatabaseLogEntry](Get-SPServerScaleOutDatabaseLogEntry.md) -Queries a scale-out database for scale-out logs. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPScaleOutDatabaseTenantData](Import-SPScaleOutDatabaseTenantData.md) -Imports data from the specified subscription id. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPServerScaleOutDatabaseTenantData](Import-SPServerScaleOutDatabaseTenantData.md) -Imports data from the specified subscription id. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Mount-SPContentDatabase](Mount-SPContentDatabase.md) -Attaches an existing content database to the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Move-SPBlobStorageLocation](Move-SPBlobStorageLocation.md) -Copies a content database to a new location by using Remote BLOB Storage (RBS). Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPContentDatabase](New-SPContentDatabase.md) -Creates a new content database and attaches it to the specified Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-DatabaseFromAvailabilityGroup](Remove-DatabaseFromAvailabilityGroup.md) -Removes one or more SharePoint databases from an availability group in SQL Server. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPContentDatabase](Remove-SPContentDatabase.md) -Deletes a content database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPScaleOutDatabase](Remove-SPScaleOutDatabase.md) -Removes a specific scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPServerScaleOutDatabase](Remove-SPServerScaleOutDatabase.md) -Removes a specific scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPContentDatabase](Set-SPContentDatabase.md) -Sets global properties of a SharePoint content database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPScaleOutDatabaseDataRange](Set-SPScaleOutDatabaseDataRange.md) -Extends the range of a specified scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPScaleOutDatabaseDataSubRange](Set-SPScaleOutDatabaseDataSubRange.md) -Creates a subrange for a specified scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServerScaleOutDatabaseDataRange](Set-SPServerScaleOutDatabaseDataRange.md) -Extends the range of a specified scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServerScaleOutDatabaseDataSubRange](Set-SPServerScaleOutDatabaseDataSubRange.md) -Creates a subrange for a specified scale-out database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Split-SPScaleOutDatabase](Split-SPScaleOutDatabase.md) -Moves a specified percentage of partitions from one scale-out database to another. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Split-SPServerScaleOutDatabase](Split-SPServerScaleOutDatabase.md) -Moves a specified percentage of partitions from one scale-out database to another. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Test-SPContentDatabase](Test-SPContentDatabase.md) -Tests a content database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPContentDatabase](Upgrade-SPContentDatabase.md) -Resumes a failed database upgrade or begins a build-to-build database upgrade. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Diagnostics Logs (ULS) - - -#### [Clear-SPLogLevel](Clear-SPLogLevel.md) -Resets the Windows event logging and trace logging to their default values. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPLogEvent](Get-SPLogEvent.md) -Returns results from a Unified Logging Service (ULS) trace log. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPLogLevel](Get-SPLogLevel.md) -Returns a list of objects or diagnostic levels. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Merge-SPLogFile](Merge-SPLogFile.md) -Combines trace log entries from all farm computers into a single log file on the local computer. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPLogFile](New-SPLogFile.md) -Creates a new log file. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPLogLevel](Set-SPLogLevel.md) -Sets the trace and event level for a set of categories. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Distributed Cache - - -#### [Add-SPDistributedCacheServiceInstance](Add-SPDistributedCacheServiceInstance.md) -Adds an instance of the distributed cache service to a local server. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPDistributedCacheItem](Clear-SPDistributedCacheItem.md) -Clears cached items from the distributed cache server. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDistributedCacheClientSetting](Get-SPDistributedCacheClientSetting.md) -Returns distributed cache settings from usage. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPDistributedCacheServiceInstance](Remove-SPDistributedCacheServiceInstance.md) -Removes an instance of the distributed cache service from a local server. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPDistributedCacheClientSetting](Set-SPDistributedCacheClientSetting.md) -Sets distributed cache settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPDistributedCacheServiceInstance](Stop-SPDistributedCacheServiceInstance.md) -Stops an instance of the Distributed Cache service on a local server. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPDistributedCacheSize](Update-SPDistributedCacheSize.md) -Reconfigures the allocation of memory that is dedicated to the Distributed Cache service. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Excel Calculation Services -Excel Calculation Services cmdlets. - -#### [Get-SPExcelBIServer](Get-SPExcelBIServer.md) -Returns the server ID of the instance of Analysis Services. Platform: SharePoint Server 2013. - -#### [Get-SPExcelBlockedFileType](Get-SPExcelBlockedFileType.md) -Returns a file type or list of file types that are prevented from loading. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Get-SPExcelDataConnectionLibrary](Get-SPExcelDataConnectionLibrary.md) -Returns a trusted data connection library or a list of trusted data connection libraries. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Get-SPExcelDataProvider](Get-SPExcelDataProvider.md) -Returns a safe data provider or a list of safe data providers. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Get-SPExcelFileLocation](Get-SPExcelFileLocation.md) -Returns a trusted file location or a list of trusted file locations. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Get-SPExcelServiceApplication](Get-SPExcelServiceApplication.md) -Returns an SPExcelServiceApplication object. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Get-SPExcelUserDefinedFunction](Get-SPExcelUserDefinedFunction.md) -Returns a user-defined function or a collection of user-defined functions. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [New-SPExcelBIServer](New-SPExcelBIServer.md) -Configures Analysis Services servers to work with Excel Services. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [New-SPExcelBlockedFileType](New-SPExcelBlockedFileType.md) -Adds a file type to the list of file types that Excel Services Application prevents from loading. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [New-SPExcelDataConnectionLibrary](New-SPExcelDataConnectionLibrary.md) -Adds a new data connection library to Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [New-SPExcelDataProvider](New-SPExcelDataProvider.md) -Adds a new safe data provider to Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [New-SPExcelFileLocation](New-SPExcelFileLocation.md) -Adds a new trusted location to Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [New-SPExcelServiceApplication](New-SPExcelServiceApplication.md) -Creates a new instance of Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [New-SPExcelUserDefinedFunction](New-SPExcelUserDefinedFunction.md) -Adds a new user-defined function to Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Remove-SPExcelBIServer](Remove-SPExcelBIServer.md) -Removes an instance of Analysis Services. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Remove-SPExcelBlockedFileType](Remove-SPExcelBlockedFileType.md) -Removes an entry from the list of file types that are prevented from loading on Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Remove-SPExcelDataConnectionLibrary](Remove-SPExcelDataConnectionLibrary.md) -Removes a data connection library from Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Remove-SPExcelDataProvider](Remove-SPExcelDataProvider.md) -Removes a data provider from Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Remove-SPExcelFileLocation](Remove-SPExcelFileLocation.md) -Removes a trusted file location from Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Remove-SPExcelUserDefinedFunction](Remove-SPExcelUserDefinedFunction.md) -Removes a user-defined function from Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Set-SPExcelBIServer](Set-SPExcelBIServer.md) -Specifies a description for an existing BI server for Excel Services. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Set-SPExcelDataConnectionLibrary](Set-SPExcelDataConnectionLibrary.md) -Sets properties of a data connection library for Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Set-SPExcelDataProvider](Set-SPExcelDataProvider.md) -Sets properties of a safe data provider for Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Set-SPExcelFileLocation](Set-SPExcelFileLocation.md) -Sets properties of a trusted file location for Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Set-SPExcelServiceApplication](Set-SPExcelServiceApplication.md) -Sets global properties for Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -#### [Set-SPExcelUserDefinedFunction](Set-SPExcelUserDefinedFunction.md) -Sets properties of a user-defined function in Excel Services Application. Platform: SharePoint Server 2010, SharePoint Server 2013. - -### Farm - - -#### [Disable-SPTimerJob](Disable-SPTimerJob.md) -Disables a timer job. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPTimerJob](Enable-SPTimerJob.md) -Enables a timer job. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPBrowserCustomerExperienceImprovementProgram](Get-SPBrowserCustomerExperienceImprovementProgram.md) -Returns the current opt-in state for the browser Customer Experience Improvement Program. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPFarm](Get-SPFarm.md) -Returns the local SharePoint farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPFarmConfig](Get-SPFarmConfig.md) -Returns a global property or a collection of global properties for the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPMobileMessagingAccount](Get-SPMobileMessagingAccount.md) -Retrieves mobile messaging accounts for the specified Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPProcessAccount](Get-SPProcessAccount.md) -Returns a system account or a managed account. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPProduct](Get-SPProduct.md) -Returns a list of the SharePoint-related products installed in the farm and the versions of all updates installed for each product. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServer](Get-SPServer.md) -Returns the server or servers in the farm that match the given identity. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPService](Get-SPService.md) -Gets a service in the farm. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceHostConfig](Get-SPServiceHostConfig.md) -Returns the common Web service settings. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceInstance](Get-SPServiceInstance.md) -Returns the services instance for a specific server or the entire farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPTimerJob](Get-SPTimerJob.md) -Returns timer jobs. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUserSettingsProvider](Get-SPUserSettingsProvider.md) -Returns a list of User Settings Providers installed on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUserSettingsProviderManager](Get-SPUserSettingsProviderManager.md) -Returns the User Settings Provider Manager. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWebPartPack](Get-SPWebPartPack.md) -Returns the Web Part packages that were installed for the specified scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPWebPartPack](Install-SPWebPartPack.md) -Installs the specified Web Part package to the specified location. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPUserSettingsProvider](New-SPUserSettingsProvider.md) -Adds a new User Settings Provider. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPApplicationCredentialKey](Remove-SPApplicationCredentialKey.md) -Removes the application credential key from the local server. Platform: SharePoint Server 2019. - -#### [Remove-SPUserSettingsProvider](Remove-SPUserSettingsProvider.md) -Removes a User Settings Provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Rename-SPServer](Rename-SPServer.md) -Renames a server that is currently connected to the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPApplicationCredentialKey](Set-SPApplicationCredentialKey -Sets the application credential key on the local server. Platform: SharePoint Server 2019. - -#### [Set-SPBrowserCustomerExperienceImprovementProgram](Set-SPBrowserCustomerExperienceImprovementProgram.md) -Turns on or off the browser Customer Experience Improvement Program. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPCustomLayoutsPage](Set-SPCustomLayoutsPage.md) -Maps a new path for a custom layout page. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPFarmConfig](Set-SPFarmConfig.md) -Sets a global property or a collection of global properties for the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPIRMSettings](Set-SPIRMSettings.md) -Sets the Information Rights Management (IRM) settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPMobileMessagingAccount](Set-SPMobileMessagingAccount.md) -Configures the specified mobile messaging account. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServiceHostConfig](Set-SPServiceHostConfig.md) -Configures one or more common settings for all Web services. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTimerJob](Set-SPTimerJob.md) -Sets the schedule for running a timer job. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPAdminJob](Start-SPAdminJob.md) -Immediately starts any waiting administrative job on the local computer. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPService](Start-SPService.md) -Enables a service in the farm. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPServiceInstance](Start-SPServiceInstance.md) -Starts the service instance for a service on a specific server or the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPTimerJob](Start-SPTimerJob.md) -Runs a timer job once. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPService](Stop-SPService.md) -Disables a service in the farm. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPServiceInstance](Stop-SPServiceInstance.md) -Stops the service instance for a service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPWebPartPack](Uninstall-SPWebPartPack.md) -Uninstalls the specified Web Part package. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Unpublish-SPServiceApplication](Unpublish-SPServiceApplication.md) -Stops sharing the specified service application outside the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Farm and Sandbox Solutions - - -#### [Add-SPSolution](Add-SPSolution.md) -Uploads a SharePoint solution package to the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPUserSolution](Add-SPUserSolution.md) -Uploads a new sandboxed solution to the solution gallery. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPUserSolutionAllowList](Disable-SPUserSolutionAllowList.md) -Disables the user managed solutions gallery capability on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPUserSolutionAllowList](Enable-SPUserSolutionAllowList.md) -Enables the user managed solutions gallery capability on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSolution](Get-SPSolution.md) -Returns a specified SharePoint solution. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUserSolution](Get-SPUserSolution.md) -Returns a specified sandboxed solution. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUserSolutionAllowList](Get-SPUserSolutionAllowList.md) -Gets the user managed solutions gallery configured on the specified web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPSolution](Install-SPSolution.md) -Deploys an installed SharePoint solution in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPUserSolution](Install-SPUserSolution.md) -Activates a sandboxed solution in a site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPUserSolutionAllowList](New-SPUserSolutionAllowList.md) -Creates a user managed solutions gallery. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSolution](Remove-SPSolution.md) -Removes a SharePoint solution from a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSolutionDeploymentLock](Remove-SPSolutionDeploymentLock.md) -Removes the solution deployment lock for a server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPUserSolution](Remove-SPUserSolution.md) -Removes a sandboxed solution from the solution gallery. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPSolution](Uninstall-SPSolution.md) -Retracts a deployed SharePoint solution. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPUserSolution](Uninstall-SPUserSolution.md) -Deactivates a sandboxed solution in a site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPSolution](Update-SPSolution.md) -Upgrades a deployed SharePoint solution. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPUserSolution](Update-SPUserSolution.md) -Upgrades an activated sandboxed solution in a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### FAST Search Service - -#### [Add-FASTSearchResource](Add-FASTSearchResource.md) -Uploads a resource to the resource store. Platform: FAST Server for SharePoint 2010. - -#### [Add-FASTSearchSpelltuning](Add-FASTSearchSpelltuning.md) -Enables the spell tuning processor, used to fine-tune a spell check dictionary. Platform: FAST Server for SharePoint 2010. - -#### [Clear-FASTSearchContentCollection](Clear-FASTSearchContentCollection.md) -Clears the content of a Microsoft FAST Search Server 2010 for SharePoint content collection. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchContentCollection](Get-FASTSearchContentCollection.md) -Retrieves Microsoft FAST Search Server 2010 for SharePoint content collections. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchDocumentProcessingPipeline](Get-FASTSearchDocumentProcessingPipeline.md) -Retrieves FAST Search Server 2010 for SharePoint document processing pipelines. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchMetadataCategory](Get-FASTSearchMetadataCategory.md) -Retrieves a crawled property category. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchMetadataCrawledProperty](Get-FASTSearchMetadataCrawledProperty.md) -Retrieves a crawled property from Microsoft FAST Search Server 2010 for SharePoint. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchMetadataCrawledPropertyMapping](Get-FASTSearchMetadataCrawledPropertyMapping.md) -Retrieves a list of crawled properties mapped to a managed property. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchMetadataFullTextIndex](Get-FASTSearchMetadataFullTextIndex.md) -Retrieves a full text index. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchMetadataFullTextIndexMapping](Get-FASTSearchMetadataFullTextIndexMapping.md) -Retrieves mappings between managed properties and the full text indexes. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchMetadataManagedProperty](Get-FASTSearchMetadataManagedProperty.md) -Retrieves a managed property with the specified name. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchMetadataRankProfile](Get-FASTSearchMetadataRankProfile.md) -Retrieves rank profiles from the Microsoft FAST Search Server 2010 for SharePoint system. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchResource](Get-FASTSearchResource.md) -Downloads a resource from the resource store. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSearchSettingGroup](Get-FASTSearchSearchSettingGroup.md) -Retrieves Microsoft FAST Search Server 2010 for SharePoint search setting groups. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityAliaser](Get-FASTSearchSecurityAliaser.md) -Gets a security principal aliaser. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityCCTKServer](Get-FASTSearchSecurityCCTKServer.md) -Gets the CCTK server general setting. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityClaimsUserStore](Get-FASTSearchSecurityClaimsUserStore.md) -Get the claims security user store. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityCompleteGroupExpansion](Get-FASTSearchSecurityCompleteGroupExpansion.md) -Gets complete group expansion information for a user. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityDecodedSid](Get-FASTSearchSecurityDecodedSid.md) -Gets the user identifier and SID from the encoded security identifier. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityDefaultUserStore](Get-FASTSearchSecurityDefaultUserStore.md) -Gets the default user store general setting. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityEncodedSid](Get-FASTSearchSecurityEncodedSid.md) -Gets the encoded extended security identifier. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityGeneralSettings](Get-FASTSearchSecurityGeneralSettings.md) -Gets the security general settings. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityLogLevel](Get-FASTSearchSecurityLogLevel.md) -Gets the log level general setting. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityLotusNotesUserStore](Get-FASTSearchSecurityLotusNotesUserStore.md) -Gets a Lotus Notes user store. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityPublicFilter](Get-FASTSearchSecurityPublicFilter.md) -Gets the public filter general setting. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityRegexAliaser](Get-FASTSearchSecurityRegexAliaser.md) -Gets a regular expression principal aliaser. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityUserFilter](Get-FASTSearchSecurityUserFilter.md) -Gets a user's search security filter. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityUserStore](Get-FASTSearchSecurityUserStore.md) -Gets a user store. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityUserStoreGroupExpansion](Get-FASTSearchSecurityUserStoreGroupExpansion.md) -Gets all groups in a user store that the specified user is a member of. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityWorkerNode](Get-FASTSearchSecurityWorkerNode.md) -Gets status information about a security worker or workers. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSecurityXMLAliaser](Get-FASTSearchSecurityXMLAliaser.md) -Gets a security principal aliaser. Platform: FAST Server for SharePoint 2010. - -#### [Get-FASTSearchSpelltuningStatus](Get-FASTSearchSpelltuningStatus.md) -Retrieves the status of spell tuning. Platform: FAST Server for SharePoint 2010. - -#### [Install-FASTSearchAdminDatabase](Install-FASTSearchAdminDatabase.md) -Installs the database used by the Microsoft FAST Search Server 2010 for SharePoint administration services. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchContentCollection](New-FASTSearchContentCollection.md) -Creates a new Microsoft FAST Search Server 2010 for SharePoint content collection. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchMetadataCategory](New-FASTSearchMetadataCategory.md) -Creates a new category for crawled properties. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchMetadataCrawledProperty](New-FASTSearchMetadataCrawledProperty.md) -Creates a new crawled property. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchMetadataCrawledPropertyMapping](New-FASTSearchMetadataCrawledPropertyMapping.md) -Creates a new mapping from a crawled property to a managed property. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchMetadataFullTextIndex](New-FASTSearchMetadataFullTextIndex.md) -Creates a new full text index. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchMetadataFullTextIndexMapping](New-FASTSearchMetadataFullTextIndexMapping.md) -Creates a new mapping from a managed property into the full text index. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchMetadataManagedProperty](New-FASTSearchMetadataManagedProperty.md) -Creates a new managed property. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchMetadataRankProfile](New-FASTSearchMetadataRankProfile.md) -Creates a new rank profile to calculate relevance in queries. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchSearchSettingGroup](New-FASTSearchSearchSettingGroup.md) -Creates a new Microsoft FAST Search Server 2010 for SharePoint search setting group. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchSecurityClaimsUserStore](New-FASTSearchSecurityClaimsUserStore.md) -Creates a FAST Search Server 2010 for SharePoint security user store to provide security for claims content. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchSecurityLotusNotesUserStore](New-FASTSearchSecurityLotusNotesUserStore.md) -Creates a FAST Search Server 2010 for SharePoint security user store to provide security for Lotus Notes content. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchSecurityRegexAliaser](New-FASTSearchSecurityRegexAliaser.md) -Creates a regular expression aliaser. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchSecurityRegexAliaserPattern](New-FASTSearchSecurityRegexAliaserPattern.md) -reates a new regular expression pattern for a regex principal aliaser. Platform: FAST Server for SharePoint 2010. - -#### [New-FASTSearchSecurityXMLAliaser](New-FASTSearchSecurityXMLAliaser.md) -Creates an XML principal aliaser. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchContentCollection](Remove-FASTSearchContentCollection.md) -Deletes a Microsoft FAST Search Server 2010 for SharePoint content collection. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchMetadataCategory](Remove-FASTSearchMetadataCategory.md) -Removes a crawled property category from the installation. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchMetadataCrawledPropertyMapping](Remove-FASTSearchMetadataCrawledPropertyMapping.md) -Removes a crawled-property-to-managed-property mapping. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchMetadataFullTextIndex](Remove-FASTSearchMetadataFullTextIndex.md) -Removes a full text index from the Microsoft FAST Search Server 2010 for SharePoint system. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchMetadataFullTextIndexMapping](Remove-FASTSearchMetadataFullTextIndexMapping.md) -Removes a managed-property-to-full-text-index mapping. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchMetadataManagedProperty](Remove-FASTSearchMetadataManagedProperty.md) -Removes a managed property from the Microsoft FAST Search Server 2010 for SharePoint system. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchMetadataRankProfile](Remove-FASTSearchMetadataRankProfile.md) -Removes a rank profile from the Microsoft FAST Search Server 2010 for SharePoint system. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchResource](Remove-FASTSearchResource.md) -Deletes a resource from the resource store. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchSearchSettingGroup](Remove-FASTSearchSearchSettingGroup.md) -tes a Microsoft FAST Search Server 2010 for SharePoint search setting group. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchSecurityAliaser](Remove-FASTSearchSecurityAliaser.md) -Removes a security aliaser. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchSecurityUserStore](Remove-FASTSearchSecurityUserStore.md) -Removes a user store. Platform: FAST Server for SharePoint 2010. - -#### [Remove-FASTSearchSpelltuning](Remove-FASTSearchSpelltuning.md) -Disables spell tuning. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchConfiguration](Set-FASTSearchConfiguration.md) -Configures the local instance of Microsoft FAST Search Server 2010 for SharePoint. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchIPSec](Set-FASTSearchIPSec.md) -Configures local Internet Protocol security (IPsec) for Microsoft FAST Search Server 2010 for SharePoint.Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchMetadataCategory](Set-FASTSearchMetadataCategory.md) -Updates the settings of a crawled property category. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchMetadataCrawledProperty](Set-FASTSearchMetadataCrawledProperty.md) -Updates the properties of a crawled property. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchMetadataCrawledPropertyMapping](Set-FASTSearchMetadataCrawledPropertyMapping.md) -Specifies which crawled properties map into specific managed properties. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchMetadataFullTextIndex](Set-FASTSearchMetadataFullTextIndex.md) -Updates the properties of a full text index. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchMetadataFullTextIndexMapping](Set-FASTSearchMetadataFullTextIndexMapping.md) -Updates the importance level of an existing full text index mapping. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchMetadataManagedProperty](Set-FASTSearchMetadataManagedProperty.md) -Updates the features of a managed property. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchMetadataRankProfile](Set-FASTSearchMetadataRankProfile.md) -Reconfigures a rank profile. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityCCTKServer](Set-FASTSearchSecurityCCTKServer.md) -Updates the CCTK server general setting. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityClaimsUserStore](Set-FASTSearchSecurityClaimsUserStore.md) -Updates a claims user store. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityDefaultUserStore](Set-FASTSearchSecurityDefaultUserStore.md) -Updates the default user store general setting. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityLogLevel](Set-FASTSearchSecurityLogLevel.md) -Updates the log level general setting. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityLotusNotesUserStore](Set-FASTSearchSecurityLotusNotesUserStore.md) -Updates a Lotus Notes user store. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityPublicFilter](Set-FASTSearchSecurityPublicFilter.md) -Updates the public filter general setting. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityRegexAliaser](Set-FASTSearchSecurityRegexAliaser.md) -Updates a regular expression aliaser. Platform: FAST Server for SharePoint 2010. - -#### [Set-FASTSearchSecurityXMLAliaser](Set-FASTSearchSecurityXMLAliaser.md) -Updates an XML aliaser. Platform: FAST Server for SharePoint 2010. - -#### [Uninstall-FASTSearchAdminDatabase](Uninstall-FASTSearchAdminDatabase.md) -Uninstalls the database used by the Microsoft FAST Search Server 2010 for SharePoint administration services.Platform: FAST Server for SharePoint 2010. - -### Feature - - -#### [Disable-SPFeature](Disable-SPFeature.md) -Disables an installed SharePoint Feature at a given scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPFeature](Enable-SPFeature.md) -Enables an installed SharePoint Feature at the given scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPFeature](Get-SPFeature.md) -Returns the SharePoint Features based on a given scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPFeature](Install-SPFeature.md) -Installs a SharePoint Feature by using the Feature.xml file. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPFeature](Uninstall-SPFeature.md) -Uninstalls an installed feature definition. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Hybrid and Migration - - -#### [Copy-SPContentTypes](Copy-SPContentTypes.md) -Specifies content types for replicating from on-premises to SharePoint Online (SPO) environment. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPInsightsConfig](Get-SPInsightsConfig.md) -Returns the uploader.xml and Microsoft.Office.BigData.DataLoader.exe.config files from the Configuration database. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPO365LinkSettings](Get-SPO365LinkSettings -Gets hybrid configurations. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPAzureAccessControlServiceApplicationProxy](New-SPAzureAccessControlServiceApplicationProxy.md) -Creates a new service application proxy group. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPO365LinkSettings](Set-SPO365LinkSettings -Set SharePoint O365 Link Settings for Hybrid Configuration. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPContentTypeReplication](Stop-SPContentTypeReplication.md) -Stops Content Type replication job to SharePoint Online. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Test-SPO365LinkSettings](Test-SPO365LinkSettings -Validates whether the configured Office 365 hybrid site uses a valid template. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Identity (General) - - -#### [Add-SPClaimTypeMapping](Add-SPClaimTypeMapping.md) -Adds a claim mapping to a trusted security token service (STS) identity provider. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPClaimProvider](Get-SPClaimProvider.md) -Returns a claim provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPClaimProviderManager](Get-SPClaimProviderManager.md) -Returns a claim provider manager. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPClaimTypeEncoding](Get-SPClaimTypeEncoding.md) -Returns a list of all the types of claims. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUser](Get-SPUser.md) -Returns the user account or accounts that match a given search criteria. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Move-SPUser](Move-SPUser.md) -Migrates a user account in SharePoint Products. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPClaimProvider](New-SPClaimProvider.md) -Registers a new claim provider in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPClaimsPrincipal](New-SPClaimsPrincipal.md) -Creates a claims principal. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPClaimTypeEncoding](New-SPClaimTypeEncoding.md) -Registers a new type of claim. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPClaimTypeMapping](New-SPClaimTypeMapping.md) -Creates a claim mapping rule for a security token service (STS) identity provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPManagedAccount](New-SPManagedAccount.md) -Registers a new managed account. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPUser](New-SPUser.md) -Adds an existing user to a SharePoint site with the designated permissions. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPClaimProvider](Remove-SPClaimProvider.md) -Unregisters a claim provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPClaimTypeMapping](Remove-SPClaimTypeMapping.md) -Deletes a claim type mapping rule for a security token service (STS) identity provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPManagedAccount](Remove-SPManagedAccount.md) -Removes a managed account registration from the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPUser](Remove-SPUser.md) -Removes a user from a Web site. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPClaimProvider](Set-SPClaimProvider.md) -Updates registration of a claims provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPUser](Set-SPUser.md) -Configures properties of an existing user. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### InfoPath Forms Service - - -#### [Add-SPInfoPathUserAgent](Add-SPInfoPathUserAgent.md) -Adds a user agent to a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPInfoPathFormTemplate](Disable-SPInfoPathFormTemplate.md) -Deactivates a InfoPath form template from the specified site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPInfoPathFormTemplate](Enable-SPInfoPathFormTemplate.md) -Activates a InfoPath form template in the specified site collection. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPInfoPathAdministrationFiles](Export-SPInfoPathAdministrationFiles.md) -Saves InfoPath form templates on the SharePoint Central Administration Web site and .udcx files to a .cab file. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDataConnectionFile](Get-SPDataConnectionFile.md) -Returns a data connection file or a collection of data connection files. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDataConnectionFileDependent](Get-SPDataConnectionFileDependent.md) -Returns deployed forms on the server dependent on a universal data connection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPInfoPathFormsService](Get-SPInfoPathFormsService.md) -Returns the InfoPath Forms Services in SharePoint Server settings that are in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPInfoPathFormTemplate](Get-SPInfoPathFormTemplate.md) -Returns a InfoPath form template. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPInfoPathUserAgent](Get-SPInfoPathUserAgent.md) -Returns a user agent or all the currently defined user agents for the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPInfoPathWebServiceProxy](Get-SPInfoPathWebServiceProxy.md) -Returns the Web proxy settings for the Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPInfoPathAdministrationFiles](Import-SPInfoPathAdministrationFiles.md) -Imports InfoPath form templates and .udcx files that are located on the SharePoint Central Administration Web site. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPDataConnectionFile](Install-SPDataConnectionFile.md) -Installs the provided data connection file. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPInfoPathFormTemplate](Install-SPInfoPathFormTemplate.md) -Installs an InfoPath form template on a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPInfoPathUserAgent](Remove-SPInfoPathUserAgent.md) -Removes a user agent. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPDataConnectionFile](Set-SPDataConnectionFile.md) -Sets properties of a data connection file. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPInfoPathFormsService](Set-SPInfoPathFormsService.md) -Sets parameters for InfoPath Forms Services in SharePoint Server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPInfoPathFormTemplate](Set-SPInfoPathFormTemplate.md) -Sets properties of a InfoPath form template. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPInfoPathWebServiceProxy](Set-SPInfoPathWebServiceProxy.md) -Sets parameters for an existing SharePoint Web service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPInfoPathFormTemplate](Start-SPInfoPathFormTemplate.md) -Activates a previously quiesced InfoPath form template. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPInfoPathFormTemplate](Stop-SPInfoPathFormTemplate.md) -Disables a InfoPath form template on a farm before an upgrade. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Test-SPInfoPathFormTemplate](Test-SPInfoPathFormTemplate.md) -Validates that a InfoPath form template is browser-enabled. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPDataConnectionFile](Uninstall-SPDataConnectionFile.md) -Removes a data connection file. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPInfoPathFormTemplate](Uninstall-SPInfoPathFormTemplate.md) -Removes a InfoPath form template from a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPInfoPathAdminFileUrl](Update-SPInfoPathAdminFileUrl.md) -Updates InfoPath form templates (.xsn files) and universal data connections (.udcx files). Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPInfoPathFormTemplate](Update-SPInfoPathFormTemplate.md) -Upgrades all InfoPath form templates on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPInfoPathUserFileUrl](Update-SPInfoPathUserFileUrl.md) -Updates InfoPath form templates (.xsn files) and universal data connections (.udcx files). Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Installation and Upgrade - - -#### [Connect-SPConfigurationDatabase](Connect-SPConfigurationDatabase.md) -Connects the local server computer to a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Copy-SPSideBySideFiles](Copy-SPSideBySideFiles.md) -Copy side by side files. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Disconnect-SPConfigurationDatabase](Disconnect-SPConfigurationDatabase.md) -Disconnects the local server computer from the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPPendingUpgradeActions](Get-SPPendingUpgradeActions.md) -Displays pending upgrade actions. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUpgradeActions](Get-SPUpgradeActions.md) -Returns all upgrade actions. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Initialize-SPResourceSecurity](Initialize-SPResourceSecurity.md) -Enforces resource security on the local server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPApplicationContent](Install-SPApplicationContent.md) -Copies shared application data to existing Web application folders. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPHelpCollection](Install-SPHelpCollection.md) -Installs the provided Help site collection files in the current farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPService](Install-SPService.md) -Installs and provisions services on a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPCentralAdministration](New-SPCentralAdministration.md) -Creates a new SharePoint Central Administration Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPConfigurationDatabase](New-SPConfigurationDatabase.md) -Creates a new configuration database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPCentralAdministration](Remove-SPCentralAdministration.md) -Removes the SharePoint Central Administration web site from the local server. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPConfigurationDatabase](Remove-SPConfigurationDatabase.md) -Permanently removes a configuration database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPCentralAdministration](Set-SPCentralAdministration.md) -Sets the port for the SharePoint Central Administration Web site. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPPassPhrase](Set-SPPassPhrase.md) -Sets the pass phrase to a new value. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServer](Set-SPServer.md) -Changes the role of the server. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Uninstall-SPHelpCollection](Uninstall-SPHelpCollection.md) -Removes Help collection files. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPFarmEncryptionKey](Update-SPFarmEncryptionKey.md) -Changes the value of the farm encryption key and using the new key, re-encrypts all the data. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPFarm](Upgrade-SPFarm.md) -Activates the Upgrade method for the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Machine Translation Services - - -#### [Get-SPTranslationThrottlingSetting](Get-SPTranslationThrottlingSetting.md) -Gets time duration settings. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPTranslationServiceApplication](New-SPTranslationServiceApplication.md) -Provisions a new instance of the Machine Translation service. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPTranslationServiceApplicationProxy](New-SPTranslationServiceApplicationProxy.md) -Creates a Machine Translation Service application proxy on the local farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPTranslationServiceJobHistory](Remove-SPTranslationServiceJobHistory.md) -Removes Machine Translation service jobs. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTranslationServiceApplication](Set-SPTranslationServiceApplication.md) -Sets property settings on a Machine Translation service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTranslationServiceApplicationProxy](Set-SPTranslationServiceApplicationProxy.md) -Sets properties to the Machine Translation service application proxy. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTranslationThrottlingSetting](Set-SPTranslationThrottlingSetting.md) -Sets the timer job duration. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Managed Account - - -#### [Get-SPManagedAccount](Get-SPManagedAccount.md) -Retrieves accounts registered in the configuration database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPManagedAccount](Set-SPManagedAccount.md) -Configures the managed account. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Repair-SPManagedAccountDeployment](Repair-SPManagedAccountDeployment.md) -Repairs the local managed account credential deployment. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Managed Metadata Service - - -#### [Export-SPMetadataWebServicePartitionData](Export-SPMetadataWebServicePartitionData.md) -Exports the data from a metadata Web service for a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Copy-SPTaxonomyGroups](Copy-SPTaxonomyGroups.md) -Copies Managed Metadata Taxonomy Groups from SharePoint on-premises to SharePoint Online. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPMetadataServiceApplication](Get-SPMetadataServiceApplication.md) -Returns a managed metadata service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPMetadataServiceApplicationProxy](Get-SPMetadataServiceApplicationProxy.md) -Returns an existing connection to a managed metadata service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPTaxonomySession](Get-SPTaxonomySession.md) -Returns a TaxonomySession object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPMetadataWebServicePartitionData](Import-SPMetadataWebServicePartitionData.md) -Restores the data for a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Move-SPProfileManagedMetadataProperty](Move-SPProfileManagedMetadataProperty.md) -Moves multiple-string values into a term set. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPMetadataServiceApplication](New-SPMetadataServiceApplication.md) -Creates a new managed metadata service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPMetadataServiceApplicationProxy](New-SPMetadataServiceApplicationProxy.md) -Creates a new connection to a managed metadata service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPMetadataServiceApplication](Set-SPMetadataServiceApplication.md) -Sets the properties of a managed metadata service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPMetadataServiceApplicationProxy](Set-SPMetadataServiceApplicationProxy.md) -Sets the properties of a connection to a managed metadata service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPTaxonomyReplication](Stop-SPTaxonomyReplication.md) -Terminates Hybrid SharePoint Taxonomy replication from SharePoint Online site to local SharePoint on-premises site. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Office Store Apps Default Activation - - -#### [Get-SPOfficeStoreAppsDefaultActivation](Get-SPOfficeStoreAppsDefaultActivation.md) -Returns the properties of apps for Office. - -#### [Set-SPOfficeStoreAppsDefaultActivation](Set-SPOfficeStoreAppsDefaultActivation.md) -Sets the properties of apps for Office. - -### Office Web Apps/Office Online Server - - -#### [Get-SPWOPIBinding](Get-SPWOPIBinding.md) -Returns a list of bindings that were created by using New-SPWOPIBinding on the current SharePoint farm where this cmdlet is run. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWOPISuppressionSetting](Get-SPWOPISuppressionSetting.md) -Returns the suppression settings on the current SharePoint farm where this cmdlet is run. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWOPIZone](Get-SPWOPIZone.md) -eturns the zone that is configured on the current SharePoint farm for the WOPI application to use. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPWOPIBinding](New-SPWOPIBinding.md) -Creates a new binding to associate file name extensions or applications with actions on the current SharePoint farm where this cmdlet is run. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPWOPISuppressionSetting](New-SPWOPISuppressionSetting.md) -Disables Office Web Apps for the action, file name extension, or programmatic identifier that you've specified on the current SharePoint farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPWOPIBinding](Remove-SPWOPIBinding.md) -Removes bindings for applications, file name extensions and their associated actions on the current SharePoint farm where this cmdlet is run. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPWOPISuppressionSetting](Remove-SPWOPISuppressionSetting.md) -Removes the suppression settings for a file name extension or programmatic ID and action on the current SharePoint farm where this cmdlet is run. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPWOPIBinding](Set-SPWOPIBinding.md) -Updates the default click action for an application or file name extension binding. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPWOPIZone](Set-SPWOPIZone.md) -Configures the zone that the current SharePoint farm will use to navigate the browser to the WOPI application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPWOPIProofKey](Update-SPWOPIProofKey.md) -Updates the public key that is used to connect to the WOPI application on the current SharePoint farm where this cmdlet is run. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### PerformancePoint Services - - -#### [Clear-SPPerformancePointServiceApplicationTrustedLocation](Clear-SPPerformancePointServiceApplicationTrustedLocation.md) -Clears all the trusted locations for a PerformancePoint Service application identity. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPPerformancePointContent](Export-SPPerformancePointContent.md) -Exports a Performance Point Server (PPS) dashboard. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPPerformancePointServiceApplication](Get-SPPerformancePointServiceApplication.md) -Returns a PerformancePoint Service application object and properties. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPPerformancePointServiceApplicationTrustedLocation](Get-SPPerformancePointServiceApplicationTrustedLocation.md) -Returns a trusted location object and properties for a PerformancePoint Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPPerformancePointContent](Import-SPPerformancePointContent.md) -Imports a Performance Point Server (PPS) dashboard. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPPerformancePointServiceApplication](New-SPPerformancePointServiceApplication.md) -Creates a new service application for the PerformancePoint Service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPPerformancePointServiceApplicationProxy](New-SPPerformancePointServiceApplicationProxy.md) -Creates a proxy for a PerformancePoint Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPPerformancePointServiceApplicationTrustedLocation](New-SPPerformancePointServiceApplicationTrustedLocation.md) -Creates a new trusted location for a PerformancePoint Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPPerformancePointServiceApplication](Remove-SPPerformancePointServiceApplication.md) -Deletes a PerformancePoint Service application from a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPPerformancePointServiceApplicationProxy](Remove-SPPerformancePointServiceApplicationProxy.md) -Deletes the proxy for a PerformancePoint Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPPerformancePointServiceApplicationTrustedLocation](Remove-SPPerformancePointServiceApplicationTrustedLocation.md) -Removes a single trusted location from a PerformancePoint Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPPerformancePointSecureDataValues](Set-SPPerformancePointSecureDataValues.md) -Sets global settings for the unattended service account. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPPerformancePointServiceApplication](Set-SPPerformancePointServiceApplication.md) -Sets global runtime properties for a PerformancePoint Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### PowerPoint Conversion Services - - -#### [New-SPPowerPointConversionServiceApplication](New-SPPowerPointConversionServiceApplication.md) -Creates a PowerPoint Conversion Service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPPowerPointConversionServiceApplicationProxy](New-SPPowerPointConversionServiceApplicationProxy.md) -Creates a PowerPoint Conversion Service application proxy. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPPowerPointConversionServiceApplication](Set-SPPowerPointConversionServiceApplication.md) -Configures settings for a PowerPoint Conversion Service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### PowerShell (General) - - -#### [Start-SPAssignment](Start-SPAssignment.md) -Initiates a new assignment store. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPAssignment](Stop-SPAssignment.md) -Disposes of objects in the provided assignment collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPHelp](Update-SPHelp.md) -Updates SharePoint cmdlet help. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Project Server - - -#### [Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync](Disable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md) -Disables Timer Job execution of the Active Directory Enterprise Resource Pool synchronization. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Disable-SPProjectEmailNotification](Disable-SPProjectEmailNotification.md) -Turns off the Project Web App site level setting for email notifications in Project Server. Platform: ProjectProject Server 2016. - -#### [Disable-SPProjectEnterpriseProjectTaskSync](Disable-SPProjectEnterpriseProjectTaskSync.md) -Disables task sync between Project Web App and the associated project site. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Disable-SPProjectQueueStatsMonitoring](Disable-SPProjectQueueStatsMonitoring.md) -Disables monitoring Project Server queue statistics. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Disable-ProjectServerLicense](Disable-ProjectServerLicense.md) -Disable the Project Server functionality across the farm. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-ProjectServerLicense](Enable-ProjectServerLicense.md) -Enables all Project Server functionality in the farm. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync](Enable-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md) -Enables Timer Job execution of the Active Directory Enterprise Resource Pool synchronization. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Enable-SPProjectEmailNotification](Enable-SPProjectEmailNotification.md) -Turns on the Project Web App site level setting for email notifications in Project Server. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Enable-SPProjectEnterpriseProjectTaskSync](Enable-SPProjectEnterpriseProjectTaskSync.md) -Enables task sync between Project Web App and the associated project site. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Enable-SPProjectQueueStatsMonitoring](Enable-SPProjectQueueStatsMonitoring.md) -Enables monitoring Project Server queue statistics. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-ProjectServerLicense](Get-ProjectServerLicense.md) -Retrieves the status of the license for Project Server. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPProjectDatabaseQuota](Get-SPProjectDatabaseQuota.md) -Microsoft internal use only. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectDatabaseUsage](Get-SPProjectDatabaseUsage.md) -Returns an approximate size, in megabytes (MB) of the Project Web App data used in the content database. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectEnterpriseProjectTaskSync](Get-SPProjectEnterpriseProjectTaskSync.md) -Returns whether the task list sync between Project Web App and project sites is enabled or disabled. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectEventServiceSettings](Get-SPProjectEventServiceSettings.md) -Returns the settings for the Microsoft Project Server Events Service. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectIsEmailNotificationEnabled](Get-SPProjectIsEmailNotificationEnabled.md) -Returns the Project Web App site level setting for email notifications. Platform: ProjectProject Server 2016. - -#### [Get-SPProjectOdataConfiguration](Get-SPProjectOdataConfiguration.md) -Returns the settings for how the OData service is configured for an instance of Project Web App. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectPCSSettings](Get-SPProjectPCSSettings.md) -Gets the settings for the Project Calculation Engine on the Project Server. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectPermissionMode](Get-SPProjectPermissionMode.md) -Returns the permission mode for a Project Web App (PWA) instance. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectQueueSettings](Get-SPProjectQueueSettings.md) -Returns a list of all Project Server Queue settings and their current values for the specified Project Server Service Application. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Get-SPProjectWebInstance](Get-SPProjectWebInstance.md) -Returns an instance of a Project Web App site. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync](Invoke-SPProjectActiveDirectoryEnterpriseResourcePoolSync.md) -Triggers Active Directory Enterprise Resource Pool synchronization on the specified instance of Project Web App. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Invoke-SPProjectActiveDirectoryGroupSync](Invoke-SPProjectActiveDirectoryGroupSync.md) -Manually starts the synchronization job to synchronize Project Server group membership with the specified Active Directory groups. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Migrate-SPProjectDatabase](Migrate-SPProjectDatabase.md) -Copies the data from the Project Server 2013 database into the corresponding SharePoint Server 2016, SharePoint Server 2019 content database containing the migrated site collection. Platform: ProjectProject Server 2016. - -#### [Migrate-SPProjectResourcePlans](Migrate-SPProjectResourcePlans.md) -Migrates the published resource plan assignment data to engagements. Platform: ProjectProject Server 2016. - -#### [New-SPProjectServiceApplication](New-SPProjectServiceApplication.md) -Creates a new Project Server Service application. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [New-SPProjectServiceApplicationProxy](New-SPProjectServiceApplicationProxy.md) -Creates a proxy for a Project Server Service application. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Pause-SPProjectWebInstance](Pause-SPProjectWebInstance.md) -Switches the specified instance of Project Web App to read-only. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Remove-SPProjectWebInstanceData](Remove-SPProjectWebInstanceData.md) -Disassociates a Site Collection with the Project Server instance. Platform: ProjectProject Server 2016. - -#### [Repair-SPProjectWebInstance](Repair-SPProjectWebInstance.md) -Re-queues specific Project Server queue items that may have fallen out of the queue. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Reset-SPProjectEventServiceSettings](Reset-SPProjectEventServiceSettings.md) -Resets the Microsoft Project Server Events Service 2016 settings to the default values. Platform: ProjectProject Server 2016. - -#### [Reset-SPProjectPCSSettings](Reset-SPProjectPCSSettings.md) -Resets the settings for the Project Calculation Engine on Project Server. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Reset-SPProjectQueueSettings](Reset-SPProjectQueueSettings.md) -Resets all Project Server Queue settings to their default values for a specific Project Server Service Application. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Resume-SPProjectWebInstance](Resume-SPProjectWebInstance.md) -Switches the specified instance of Project Web App to read-write mode, allowing users to change data again. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectDatabaseQuota](Set-SPProjectDatabaseQuota.md) -Microsoft internal use only. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectEventServiceSettings](Set-SPProjectEventServiceSettings.md) -Allows you to change the Microsoft Project Server Events Service 2016 TCP port settings. Platform: ProjectProject Server 2016. - -#### [Set-SPProjectOdataConfiguration](Set-SPProjectOdataConfiguration.md) -Sets the properties for how the OData service is configured for an instance of Project Web App. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectPCSSettings](Set-SPProjectPCSSettings.md) -Sets the settings for the Project Calculation Engine on Project Server. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectPermissionMode](Set-SPProjectPermissionMode.md) -Changes the permission mode for a Project Web App instance. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectQueueSettings](Set-SPProjectQueueSettings.md) -Sets the value of one or multiple Project Server Queue settings for a specific Project Server service application. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectServiceApplication](Set-SPProjectServiceApplication.md) -Sets the properties of a Project Server Service application. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectUserSync](Set-SPProjectUserSync.md) -Controls the behavior of WSS user sync. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectUserSyncDisabledSyncThreshold](Set-SPProjectUserSyncDisabledSyncThreshold.md) -Defines the threshold over which a user sync job will not be executed but instead will be deleted. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectUserSyncFullSyncThreshold](Set-SPProjectUserSyncFullSyncThreshold.md) -Defines the threshold over which a delta user sync job will be executed as a complete user sync. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Set-SPProjectUserSyncOffPeakSyncThreshold](Set-SPProjectUserSyncOffPeakSyncThreshold.md) -Defines the threshold over which a full user sync job will be executed during off peak hours instead of immediately. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Start-SPProjectGenerateWsdl](Start-SPProjectGenerateWsdl.md) -Generates ASPX pages from WSDL files. Platform: ProjectProject Server 2016. - -#### [Sync-SPProjectPermissions](Sync-SPProjectPermissions.md) -Manually synchronizes permissions between a Project Web App instance and its associated project sites. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Test-SPProjectServiceApplication](Test-SPProjectServiceApplication.md) -This cmdlet runs a series of health checks against the Project Service Application. Platform: ProjectProject Server 2013, Project Server 2016. - -#### [Test-SPProjectWebInstance](Test-SPProjectWebInstance.md) -Runs a suite of tests on an existing Project Web Instance. Platform: ProjectProject Server 2013, Project Server 2016. - -### Request Management - - -#### [Add-SPThrottlingRule](Add-SPThrottlingRule.md) -Adds a new throttling rule. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPRoutingMachineInfo](Add-SPRoutingMachineInfo.md) -Adds a new routing target to the farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPRoutingMachinePool](Add-SPRoutingMachinePool.md) -Adds a new machine pool. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPRoutingRule](Add-SPRoutingRule.md) -Adds a routing rule. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPRequestManagementSettings](Get-SPRequestManagementSettings.md) -Returns a Request Manager object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPRoutingMachineInfo](Get-SPRoutingMachineInfo.md) -Returns all the routing targets. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPRoutingMachinePool](Get-SPRoutingMachinePool.md) -Returns all available routing pools. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPRoutingRule](Get-SPRoutingRule.md) -Returns all routing rules. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPThrottlingRule](Get-SPThrottlingRule.md) -Returns all throttling rules. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPRequestManagementRuleCriteria](New-SPRequestManagementRuleCriteria.md) -Creates criteria for the rule to match. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPRoutingMachineInfo](Remove-SPRoutingMachineInfo.md) -Removes an external routing target. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPRoutingMachinePool](Remove-SPRoutingMachinePool.md) -Removes a routing pool from Request Manager. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPRoutingRule](Remove-SPRoutingRule.md) -Removes a routing rule. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPThrottlingRule](Remove-SPThrottlingRule.md) -Removes a throttling rule. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPRequestManagementSettings](Set-SPRequestManagementSettings.md) -Sets Request Manager properties. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPRoutingMachineInfo](Set-SPRoutingMachineInfo.md) -Sets routing target properties. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPRoutingMachinePool](Set-SPRoutingMachinePool.md) -Sets properties of a machine pool. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPRoutingRule](Set-SPRoutingRule.md) -Changes properties of an existing routing rule. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPThrottlingRule](Set-SPThrottlingRule.md) -Changes properties of an existing throttling rule. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Search Service Application - - -#### [Backup-SPEnterpriseSearchServiceApplicationIndex](Backup-SPEnterpriseSearchServiceApplicationIndex.md) -Takes a backup of the search index to a specified backup location. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPEnterpriseSearchTopology](Export-SPEnterpriseSearchTopology.md) -Saves an existing search topology. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchAdministrationComponent](Get-SPEnterpriseSearchAdministrationComponent.md) -Returns the administration component for a search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchComponent](Get-SPEnterpriseSearchComponent.md) -Retrieves one or all search components in a given search topology. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchContentEnrichmentConfiguration](Get-SPEnterpriseSearchContentEnrichmentConfiguration.md) -Returns the content enrichment configuration for the specified search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchCrawlContentSource](Get-SPEnterpriseSearchCrawlContentSource.md) -Returns a crawl content source. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchCrawlCustomConnector](Get-SPEnterpriseSearchCrawlCustomConnector.md) -Returns a CustomConnector object type. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchCrawlDatabase](Get-SPEnterpriseSearchCrawlDatabase.md) -Returns a crawl store. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchCrawlExtension](Get-SPEnterpriseSearchCrawlExtension.md) -Returns the file types to be included in the content index. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchCrawlLogReadPermission](Get-SPEnterpriseSearchCrawlLogReadPermission.md) -Retrieves the list of users with permission to access the crawl log information. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchCrawlMapping](Get-SPEnterpriseSearchCrawlMapping.md) -Returns a crawl mapping for the search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchCrawlRule](Get-SPEnterpriseSearchCrawlRule.md) -Accesses crawl rules. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchFileFormat](Get-SPEnterpriseSearchFileFormat.md) -Retrieves all parseable file formats. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchHostController](Get-SPEnterpriseSearchHostController.md) -Lists the specified or all search host controllers in the farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchLanguageResourcePhrase](Get-SPEnterpriseSearchLanguageResourcePhrase.md) -Returns a language resource phrase. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchLinguisticComponentsStatus](Get-SPEnterpriseSearchLinguisticComponentsStatus.md) -Returns the status of the linguistic query and document processing components. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchLinksDatabase](Get-SPEnterpriseSearchLinksDatabase.md) -Retrieves a reference to a links database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchMetadataCategory](Get-SPEnterpriseSearchMetadataCategory.md) -Returns a crawled property category. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchMetadataCrawledProperty](Get-SPEnterpriseSearchMetadataCrawledProperty.md) -Returns a crawled property. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchMetadataManagedProperty](Get-SPEnterpriseSearchMetadataManagedProperty.md) -Returns a managed property. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchMetadataMapping](Get-SPEnterpriseSearchMetadataMapping.md) -Returns the current status of a managed property mapping. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchOwner](Get-SPEnterpriseSearchOwner.md) -Retrieves the search object owner. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchPropertyRule](Get-SPEnterpriseSearchPropertyRule.md) -Returns a property rule instance, which can be used in result item types. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchPropertyRuleCollection](Get-SPEnterpriseSearchPropertyRuleCollection.md) -Returns the collection of rules that are applied to search results. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryAndSiteSettingsService](Get-SPEnterpriseSearchQueryAndSiteSettingsService.md) -Returns the search manager service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance](Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md) -Returns the service manager service instance. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy](Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy.md) -Returns the search manager service proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryAuthority](Get-SPEnterpriseSearchQueryAuthority.md) -Returns an authoritative page. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryDemoted](Get-SPEnterpriseSearchQueryDemoted.md) -Returns a demoted site rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryKeyword](Get-SPEnterpriseSearchQueryKeyword.md) -Returns a keyword term. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryScope](Get-SPEnterpriseSearchQueryScope.md) -Returns a query results scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQueryScopeRule](Get-SPEnterpriseSearchQueryScopeRule.md) -Returns a shared scope rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQuerySpellingCorrection](Get-SPEnterpriseSearchQuerySpellingCorrection.md) -Returns the object that exposes the Query Spelling Correction (QSC) configuration. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchQuerySuggestionCandidates](Get-SPEnterpriseSearchQuerySuggestionCandidates.md) -Returns a list of queries. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchRankingModel](Get-SPEnterpriseSearchRankingModel.md) -Returns a ranking model. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchResultItemType](Get-SPEnterpriseSearchResultItemType.md) -Retrieves result item types. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchResultSource](Get-SPEnterpriseSearchResultSource.md) -Retrieves a result source. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchSecurityTrimmer](Get-SPEnterpriseSearchSecurityTrimmer.md) -Returns a custom security trimmer. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchService](Get-SPEnterpriseSearchService.md) -Returns the search service for the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchServiceApplication](Get-SPEnterpriseSearchServiceApplication.md) -Returns the search service application for a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchServiceApplicationBackupStore](Get-SPEnterpriseSearchServiceApplicationBackupStore.md) -Retrieves information about the search service application backup files. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchServiceApplicationProxy](Get-SPEnterpriseSearchServiceApplicationProxy.md) -Returns the search service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchServiceInstance](Get-SPEnterpriseSearchServiceInstance.md) -Returns the search service instance for a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchSiteHitRule](Get-SPEnterpriseSearchSiteHitRule.md) -Returns the shared site hit rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchStatus](Get-SPEnterpriseSearchStatus.md) -Retrieves diagnostics information for the search components. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchTopology](Get-SPEnterpriseSearchTopology.md) -Retrieves one or all search topologies that belong to a given search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPEnterpriseSearchVssDataPath](Get-SPEnterpriseSearchVssDataPath.md) -Retrieves the index paths for all active search index components on the current server. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPEnterpriseSearchCustomExtractionDictionary](Import-SPEnterpriseSearchCustomExtractionDictionary.md) -Imports a custom extraction dictionary. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPEnterpriseSearchPopularQueries](Import-SPEnterpriseSearchPopularQueries.md) -Imports queries from a comma-separated list. The search box will suggest these queries as users type. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPEnterpriseSearchThesaurus](Import-SPEnterpriseSearchThesaurus.md) -Deploys the dictionary to the thesaurus component in the query processing flow. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPEnterpriseSearchTopology](Import-SPEnterpriseSearchTopology.md) -Imports and activates a topology from an XML file. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Move-SPEnterpriseSearchLinksDatabases](Move-SPEnterpriseSearchLinksDatabases.md) -Moves data across links databases. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchAdminComponent](New-SPEnterpriseSearchAdminComponent.md) -Creates a new admin component for the given topology and search service instance. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchAnalyticsProcessingComponent](New-SPEnterpriseSearchAnalyticsProcessingComponent.md) -Creates a new analytics processing component for the given topology and search service instance. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchContentEnrichmentConfiguration](New-SPEnterpriseSearchContentEnrichmentConfiguration.md) -Creates a new ContentEnrichmentConfiguration object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchContentProcessingComponent](New-SPEnterpriseSearchContentProcessingComponent.md) -Creates a new content processing component for the given topology and search service instance. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchCrawlComponent](New-SPEnterpriseSearchCrawlComponent.md) -Creates a new crawl component for the given topology and search service instance. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchCrawlContentSource](New-SPEnterpriseSearchCrawlContentSource.md) -Creates a content source for a Search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchCrawlCustomConnector](New-SPEnterpriseSearchCrawlCustomConnector.md) -Registers a protocol for custom crawling. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchCrawlDatabase](New-SPEnterpriseSearchCrawlDatabase.md) -Creates a crawl database which can be added to a search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchCrawlExtension](New-SPEnterpriseSearchCrawlExtension.md) -Adds an extension rule to a Search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchCrawlMapping](New-SPEnterpriseSearchCrawlMapping.md) -Creates a crawl mapping rule for a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchCrawlRule](New-SPEnterpriseSearchCrawlRule.md) -Creates a new crawl rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchFileFormat](New-SPEnterpriseSearchFileFormat.md) -Adds a new file format to the parsing system. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchIndexComponent](New-SPEnterpriseSearchIndexComponent.md) -Creates a new index component for the given topology and search service instance. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchLanguageResourcePhrase](New-SPEnterpriseSearchLanguageResourcePhrase.md) -Adds a language resource phrase to a shared search application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchLinksDatabase](New-SPEnterpriseSearchLinksDatabase.md) -Creates a new links database for a search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchMetadataCategory](New-SPEnterpriseSearchMetadataCategory.md) -Adds a crawled property category to a search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchMetadataCrawledProperty](New-SPEnterpriseSearchMetadataCrawledProperty.md) -Adds a crawled property. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchMetadataManagedProperty](New-SPEnterpriseSearchMetadataManagedProperty.md) -Adds a managed property to a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchMetadataMapping](New-SPEnterpriseSearchMetadataMapping.md) -Adds a managed property mapping. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchQueryAuthority](New-SPEnterpriseSearchQueryAuthority.md) -Adds an authoritative page to a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchQueryDemoted](New-SPEnterpriseSearchQueryDemoted.md) -Adds a demoted site rule to a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchQueryKeyword](New-SPEnterpriseSearchQueryKeyword.md) -Adds a keyword term to a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchQueryProcessingComponent](New-SPEnterpriseSearchQueryProcessingComponent.md) -Creates a new query processing component for the given topology and search service instance. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchQueryScope](New-SPEnterpriseSearchQueryScope.md) -Adds a query results scope to a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchQueryScopeRule](New-SPEnterpriseSearchQueryScopeRule.md) -Adds a shared scope rule to a query scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchRankingModel](New-SPEnterpriseSearchRankingModel.md) -Adds a ranking model to a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchResultItemType](New-SPEnterpriseSearchResultItemType.md) -Creates a new result item type. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchResultSource](New-SPEnterpriseSearchResultSource.md) -Creates a new result source. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchSecurityTrimmer](New-SPEnterpriseSearchSecurityTrimmer.md) -Adds a custom security trimmer to a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchServiceApplication](New-SPEnterpriseSearchServiceApplication.md) -Adds a search service application to a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchServiceApplicationProxy](New-SPEnterpriseSearchServiceApplicationProxy.md) -Adds a new search application proxy to a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchSiteHitRule](New-SPEnterpriseSearchSiteHitRule.md) -Adds a new site hit rule for a search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEnterpriseSearchTopology](New-SPEnterpriseSearchTopology.md) -Creates a new search topology in the given search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchComponent](Remove-SPEnterpriseSearchComponent.md) -Removes the specified search component from the given search topology. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchContentEnrichmentConfiguration](Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md) -Removes the current content enrichment configuration from the search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchCrawlContentSource](Remove-SPEnterpriseSearchCrawlContentSource.md) -Deletes a specified crawl content source from a search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchCrawlCustomConnector](Remove-SPEnterpriseSearchCrawlCustomConnector.md) -Removes a CustomConnector object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchCrawlDatabase](Remove-SPEnterpriseSearchCrawlDatabase.md) -Deletes a crawl database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchCrawlExtension](Remove-SPEnterpriseSearchCrawlExtension.md) -Removes a file name extension from the list of files that can be crawled. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchCrawlLogReadPermission](Remove-SPEnterpriseSearchCrawlLogReadPermission.md) -Removes permission to view crawl log information. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchCrawlMapping](Remove-SPEnterpriseSearchCrawlMapping.md) -Deletes a crawl mapping. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchCrawlRule](Remove-SPEnterpriseSearchCrawlRule.md) -Deletes a crawl rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchFileFormat](Remove-SPEnterpriseSearchFileFormat.md) -Removes support for parsing a file format. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchLanguageResourcePhrase](Remove-SPEnterpriseSearchLanguageResourcePhrase.md) -Deletes a language resource phrase from a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchLinksDatabase](Remove-SPEnterpriseSearchLinksDatabase.md) -Deletes a links database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchMetadataCategory](Remove-SPEnterpriseSearchMetadataCategory.md) -Deletes a crawled property category. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchMetadataManagedProperty](Remove-SPEnterpriseSearchMetadataManagedProperty.md) -Deletes a metadata managed property. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchMetadataMapping](Remove-SPEnterpriseSearchMetadataMapping.md) -Deletes a metadata mapping from a managed property. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchQueryAuthority](Remove-SPEnterpriseSearchQueryAuthority.md) -Deletes an authoritative page. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchQueryDemoted](Remove-SPEnterpriseSearchQueryDemoted.md) -Deletes a demoted site rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchQueryKeyword](Remove-SPEnterpriseSearchQueryKeyword.md) -Deletes a query keyword. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchQueryScope](Remove-SPEnterpriseSearchQueryScope.md) -Deletes a query scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchQueryScopeRule](Remove-SPEnterpriseSearchQueryScopeRule.md) -Deletes query results scope rules. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchRankingModel](Remove-SPEnterpriseSearchRankingModel.md) -Deletes a ranking model. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchResultItemType](Remove-SPEnterpriseSearchResultItemType.md) -Removes a result item type for a search object owner. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchResultSource](Remove-SPEnterpriseSearchResultSource.md) -Deletes a result source. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchSecurityTrimmer](Remove-SPEnterpriseSearchSecurityTrimmer.md) -Deletes a custom security trimmer. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchServiceApplication](Remove-SPEnterpriseSearchServiceApplication.md) -Deletes a search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchServiceApplicationProxy](Remove-SPEnterpriseSearchServiceApplicationProxy.md) -Deletes a search service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchServiceApplicationSiteSettings](Remove-SPEnterpriseSearchServiceApplicationSiteSettings.md) -Cleans up search settings for a particular site collection, subscription, or search application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchSiteHitRule](Remove-SPEnterpriseSearchSiteHitRule.md) -Deletes a site hit rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchTenantConfiguration](Remove-SPEnterpriseSearchTenantConfiguration.md) -Removes all tenant specific search settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchTenantSchema](Remove-SPEnterpriseSearchTenantSchema.md) -Removes a defined search schema. Platform: ProjectharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPEnterpriseSearchTopology](Remove-SPEnterpriseSearchTopology.md) -Removes an inactive search topology from a search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Restore-SPEnterpriseSearchServiceApplication](Restore-SPEnterpriseSearchServiceApplication.md) -Restores third-party backup of a search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Restore-SPEnterpriseSearchServiceApplicationIndex](Restore-SPEnterpriseSearchServiceApplicationIndex.md) -Restores the search index from the specified backup files. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Resume-SPEnterpriseSearchServiceApplication](Resume-SPEnterpriseSearchServiceApplication.md) -Resumes a search service application that was suspended. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchAdministrationComponent](Set-SPEnterpriseSearchAdministrationComponent.md) -Sets properties of an administration component for a search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchContentEnrichmentConfiguration](Set-SPEnterpriseSearchContentEnrichmentConfiguration.md) -Stores the specified content enrichment configuration to the search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchCrawlContentSource](Set-SPEnterpriseSearchCrawlContentSource.md) -Sets the properties of a crawl content source for a Search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchCrawlDatabase](Set-SPEnterpriseSearchCrawlDatabase.md) -Sets properties of a crawl database for a Search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchCrawlLogReadPermission](Set-SPEnterpriseSearchCrawlLogReadPermission.md) -Grants users permission to view the crawl log information. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchCrawlRule](Set-SPEnterpriseSearchCrawlRule.md) -Sets properties for a crawl rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchFileFormatState](Set-SPEnterpriseSearchFileFormatState.md) -Sets the activation state of a parser for a given file format. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchLinguisticComponentsStatus](Set-SPEnterpriseSearchLinguisticComponentsStatus.md) -Sets the operation status of the linguistic query and document processing components. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchLinksDatabase](Set-SPEnterpriseSearchLinksDatabase.md) -Sets properties of a links database for a search service application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchMetadataCategory](Set-SPEnterpriseSearchMetadataCategory.md) -Sets properties of a crawled property category. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchMetadataCrawledProperty](Set-SPEnterpriseSearchMetadataCrawledProperty.md) -Sets the properties of a metadata crawled property. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchMetadataManagedProperty](Set-SPEnterpriseSearchMetadataManagedProperty.md) -Sets the properties of a metadata managed property. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchMetadataMapping](Set-SPEnterpriseSearchMetadataMapping.md) -Sets the properties of a managed property mapping for a search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchPrimaryHostController](Set-SPEnterpriseSearchPrimaryHostController.md) -Sets the primary search host controller for the farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchQueryAuthority](Set-SPEnterpriseSearchQueryAuthority.md) -Sets the properties of an authoritative page for a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchQueryKeyword](Set-SPEnterpriseSearchQueryKeyword.md) -Sets the properties of a keyword term for a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchQueryScope](Set-SPEnterpriseSearchQueryScope.md) -Sets the properties of a query results scope for a shared search application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchQueryScopeRule](Set-SPEnterpriseSearchQueryScopeRule.md) -Sets the properties of a shared scope rule for a query scope. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchQuerySpellingCorrection](Set-SPEnterpriseSearchQuerySpellingCorrection.md) -Sets the operation status of the Query Spelling Corrections (QSC) component. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchRankingModel](Set-SPEnterpriseSearchRankingModel.md) -Sets the properties of a ranking model for a shared search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchResultItemType](Set-SPEnterpriseSearchResultItemType.md) -Sets properties of a result item type. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchResultSource](Set-SPEnterpriseSearchResultSource.md) -Sets properties of a result source. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchService](Set-SPEnterpriseSearchService.md) -Sets the properties of a search service for a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchServiceApplication](Set-SPEnterpriseSearchServiceApplication.md) -Sets the properties of a search service application for a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchServiceApplicationProxy](Set-SPEnterpriseSearchServiceApplicationProxy.md) -Sets properties of a search service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchServiceInstance](Set-SPEnterpriseSearchServiceInstance.md) -Sets the properties of a search service instance. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPEnterpriseSearchTopology](Set-SPEnterpriseSearchTopology.md) -Activates a given search topology. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance](Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md) -Starts an instance of a search manager service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPEnterpriseSearchServiceInstance](Start-SPEnterpriseSearchServiceInstance.md) -Starts an instance of a search service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance](Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md) -Stops an instance of a search manager service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPEnterpriseSearchServiceInstance](Stop-SPEnterpriseSearchServiceInstance.md) -Stops an instance of a search service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Suspend-SPEnterpriseSearchServiceApplication](Suspend-SPEnterpriseSearchServiceApplication.md) -Suspends a search service application, pausing all crawls and search operations, to perform a task such as system maintenance. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPEnterpriseSearchServiceApplication](Upgrade-SPEnterpriseSearchServiceApplication.md) -Upgrades a search service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings](Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings.md) -Upgrades search settings for a particular site collection. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Secure Store Service - - -#### [Add-SPSecureStoreSystemAccount](Add-SPSecureStoreSystemAccount.md) -Adds an account to a designated list. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPSecureStoreCredentialMapping](Clear-SPSecureStoreCredentialMapping.md) -Deletes a credential mapping from a Secure Store Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPSecureStoreDefaultProvider](Clear-SPSecureStoreDefaultProvider.md) -Clears the secure store provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPSingleSignOn](Disable-SPSingleSignOn.md) -Disables the single sign-on (SSO) Service on a farm server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSecureStoreApplication](Get-SPSecureStoreApplication.md) -Returns a Secure Store application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSecureStoreSystemAccount](Get-SPSecureStoreSystemAccount.md) -Returns a list of users from a designated list. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSecureStoreApplication](New-SPSecureStoreApplication.md) -Creates a new Secure Store application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSecureStoreApplicationField](New-SPSecureStoreApplicationField.md) -Creates a new Secure Store application fields object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSecureStoreServiceApplication](New-SPSecureStoreServiceApplication.md) -Creates a new Secure Store Service application in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSecureStoreServiceApplicationProxy](New-SPSecureStoreServiceApplicationProxy.md) -Creates a new Secure Store Service application proxy in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSecureStoreTargetApplication](New-SPSecureStoreTargetApplication.md) -Creates a new Secure Store target application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSecureStoreApplication](Remove-SPSecureStoreApplication.md) -Deletes a Secure Store application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSecureStoreSystemAccount](Remove-SPSecureStoreSystemAccount.md) -Removes a user account from a designated list. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSecureStoreApplication](Set-SPSecureStoreApplication.md) -Sets properties of a Secure Store application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSecureStoreDefaultProvider](Set-SPSecureStoreDefaultProvider.md) -Updates the secure store provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSecureStoreServiceApplication](Set-SPSecureStoreServiceApplication.md) -Sets properties of a Secure Store Service application in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPSecureStoreApplicationServerKey](Update-SPSecureStoreApplicationServerKey.md) -Synchronizes the key on a Microsoft SharePoint server with the Secure Store master key. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPSecureStoreCredentialMapping](Update-SPSecureStoreCredentialMapping.md) -Sets a new credential mapping for a Secure Store Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPSecureStoreGroupCredentialMapping](Update-SPSecureStoreGroupCredentialMapping.md) -Sets a new group credential mapping for a Secure Store Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPSecureStoreMasterKey](Update-SPSecureStoreMasterKey.md) -Changes the master key of a Secure Store Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPSingleSignOnDatabase](Upgrade-SPSingleSignOnDatabase.md) -Migrates the application definitions from Single Sign-On (SSO) database to Secure Store database as target applications. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Security (General) - - -#### [Add-SPShellAdmin](Add-SPShellAdmin.md) -Adds a user to the SharePoint_Shell_Access role for the specified database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAuthenticationProvider](Get-SPAuthenticationProvider.md) -Returns an authentication provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAuthenticationRealm](Get-SPAuthenticationRealm.md) -Returns the authentication realms. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPCertificateAuthority](Get-SPCertificateAuthority.md) -Returns the SharePoint certificate authority (CA). Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPIRMSettings](Get-SPIRMSettings.md) -Returns the Information Rights Management (IRM) settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSecurityTokenServiceConfig](Get-SPSecurityTokenServiceConfig.md) -Returns the security token service (STS) for the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPShellAdmin](Get-SPShellAdmin.md) -Returns the names of all users who have the SharePoint_Shell_Access role. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPTrustedIdentityTokenIssuer](Get-SPTrustedIdentityTokenIssuer.md) -Returns an identity provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPTrustedRootAuthority](Get-SPTrustedRootAuthority.md) -Returns a trusted root authority. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPTrustedSecurityTokenIssuer](Get-SPTrustedSecurityTokenIssuer.md) -Returns the trusted security token issuer object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPTrustedServiceTokenIssuer](Get-SPTrustedServiceTokenIssuer.md) -Returns the object that represents the farm trust. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Grant-SPObjectSecurity](Grant-SPObjectSecurity.md) -Adds a new security principal to an SPObjectSecurity object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPAuthenticationProvider](New-SPAuthenticationProvider.md) -Creates a new authentication provider in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPTrustedIdentityTokenIssuer](New-SPTrustedIdentityTokenIssuer.md) -Creates an identity provider in the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPTrustedRootAuthority](New-SPTrustedRootAuthority.md) -Creates a trusted root authority. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPTrustedSecurityTokenIssuer](New-SPTrustedSecurityTokenIssuer.md) -Creates a trust between a server to server principal. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPTrustedServiceTokenIssuer](New-SPTrustedServiceTokenIssuer.md) -Creates a trust with a SharePoint farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPShellAdmin](Remove-SPShellAdmin.md) -Removes a user from the SharePoint_Shell_Access role. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPTrustedIdentityTokenIssuer](Remove-SPTrustedIdentityTokenIssuer.md) -Deletes a Security Token Service (STS) identity provider from the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPTrustedRootAuthority](Remove-SPTrustedRootAuthority.md) -Deletes a trusted root authority. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPTrustedSecurityTokenIssuer](Remove-SPTrustedSecurityTokenIssuer.md) -Removes the trusted security token service object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPTrustedServiceTokenIssuer](Remove-SPTrustedServiceTokenIssuer.md) -Deletes the object that represents the farm trust. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### [Revoke-SPObjectSecurity](Revoke-SPObjectSecurity.md) -Removes a security principal from a SPObjectSecurity object. - -#### [Set-SPSecurityTokenServiceConfig](Set-SPSecurityTokenServiceConfig.md) -Updates the settings of the SharePoint security token service (STS) identity provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTrustedIdentityTokenIssuer](Set-SPTrustedIdentityTokenIssuer.md) -Sets the identity providers of a Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTrustedRootAuthority](Set-SPTrustedRootAuthority.md) -Creates a new trusted root authority. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTrustedSecurityTokenIssuer](Set-SPTrustedSecurityTokenIssuer.md) -Sets the trusted token issuer. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTrustedServiceTokenIssuer](Set-SPTrustedServiceTokenIssuer.md) -Updates a trust with the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAuthenticationRealm](Set-SPAuthenticationRealm.md) -Sets the authentication realm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Service Application - - -#### [Add-SPServiceApplicationProxyGroupMember](Add-SPServiceApplicationProxyGroupMember.md) -Adds a member to the service application proxy group. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPConnectedServiceApplicationInformation](Get-SPConnectedServiceApplicationInformation.md) -Returns the health of the service application proxy. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceApplication](Get-SPServiceApplication.md) -Returns the specified service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceApplicationEndpoint](Get-SPServiceApplicationEndpoint.md) -Returns the endpoint of a service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceApplicationPool](Get-SPServiceApplicationPool.md) -Returns the specified Internet Information Services (IIS) application pool. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceApplicationProxy](Get-SPServiceApplicationProxy.md) -Returns an instance of the specified service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceApplicationProxyGroup](Get-SPServiceApplicationProxyGroup.md) -Returns the proxy group for the specified service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceApplicationSecurity](Get-SPServiceApplicationSecurity.md) -Returns the SPObjectSecurity object for a service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPServiceApplicationPool](New-SPServiceApplicationPool.md) -Creates a new Web service application pool. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPServiceApplicationProxyGroup](New-SPServiceApplicationProxyGroup.md) -Creates a new service application proxy group. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Publish-SPServiceApplication](Publish-SPServiceApplication.md) -Shares the specified local service application outside the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Receive-SPServiceApplicationConnectionInfo](Receive-SPServiceApplicationConnectionInfo.md) -Configures this farm to receive service information from another farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPServiceApplication](Remove-SPServiceApplication.md) -Deletes the specified service application on the local server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPServiceApplicationPool](Remove-SPServiceApplicationPool.md) -Completely deletes the specified Web service application pool. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPServiceApplicationProxy](Remove-SPServiceApplicationProxy.md) -Deletes the specified service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPServiceApplicationProxyGroup](Remove-SPServiceApplicationProxyGroup.md) -Completely deletes the specified service application proxy group. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPServiceApplicationProxyGroupMember](Remove-SPServiceApplicationProxyGroupMember.md) -Removes one or more proxies from the specified service application proxy group. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServiceApplication](Set-SPServiceApplication.md) -Sets properties of a service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServiceApplicationEndpoint](Set-SPServiceApplicationEndpoint.md) -Sets the host of an endpoint for a service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServiceApplicationPool](Set-SPServiceApplicationPool.md) -Changes the account used for the Identity of the specified application pool. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPServiceApplicationSecurity](Set-SPServiceApplicationSecurity.md) -Updates the SPObjectSecurity object for a service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Session State Service - - -#### [Disable-SPSessionStateService](Disable-SPSessionStateService.md) -Turns off the session state service on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPSessionStateService](Enable-SPSessionStateService.md) -Creates a session state database and turns on the session state service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSessionStateService](Get-SPSessionStateService.md) -Returns the properties of the session state service, including time-out and database settings. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSessionStateService](Set-SPSessionStateService.md) -Updates the credentials that are used to communicate with the state service database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Site - - -#### [Copy-SPSite](Copy-SPSite.md) -Makes a copy of a site collection. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDeletedSite](Get-SPDeletedSite.md) -Gets a list of deleted site collections. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPServiceContext](Get-SPServiceContext.md) -Returns a service context. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSite](Get-SPSite.md) -Returns all site collections that match the specified criteria. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteAdministration](Get-SPSiteAdministration.md) -Returns a site administration object that allows farm administrators to view certain information about site collections to which they might not have access. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteMaster](Get-SPSiteMaster.md) -Returns site master information. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteUpgradeSessionInfo](Get-SPSiteUpgradeSessionInfo.md) -Manage or report site upgrade. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteURL](Get-SPSiteURL.md) -Displays all URL mappings for the site. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Move-SPDeletedSite](Move-SPDeletedSite.md) -Moves deleted site collections from one content database to another. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Move-SPSite](Move-SPSite.md) -Moves site collections from one content database to another. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSite](New-SPSite.md) -Creates a new site collection at the specified URL. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSiteMaster](New-SPSiteMaster.md) -Creates a site master. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPDeletedSite](Remove-SPDeletedSite.md) -Removes a deleted site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSite](Remove-SPSite.md) -Completely deletes an existing site collection and all subsites. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteMaster](Remove-SPSiteMaster.md) -Removes a site master. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteUpgradeSessionInfo](Remove-SPSiteUpgradeSessionInfo.md) -Removes an SPSite object from upgrade. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteURL](Remove-SPSiteURL.md) -Removes an URL mapping from the site. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Repair-SPSite](Repair-SPSite.md) -Activates the RunRepairs method against the referenced SPSite object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Request-SPUpgradeEvaluationSite](Request-SPUpgradeEvaluationSite.md) -Requests an upgrade evaluation site for a specified site. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Reset-SPSites](Reset-SPSites.md) -Synchronizes the content database with the configuration database of the farm. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSite](Set-SPSite.md) -Configures the specified sites. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSiteAdministration](Set-SPSiteAdministration.md) -Allows farm administrators to configure any site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSiteURL](Set-SPSiteURL.md) -Adds or changes an URL mapping for the site. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Test-SPSite](Test-SPSite.md) -Activates the RunTests method against a referenced SPSite object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPSite](Upgrade-SPSite.md) -Starts the upgrade process on a site collection. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Site Subscriptions - - -#### [Add-SPSiteSubscriptionFeaturePackMember](Add-SPSiteSubscriptionFeaturePackMember.md) -Adds a feature to a SharePoint Feature set. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPSiteSubscriptionProfileConfig](Add-SPSiteSubscriptionProfileConfig.md) -Adds a new site subscription to a User Profile Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPMetadataWebServicePartitionData](Clear-SPMetadataWebServicePartitionData.md) -Removes all data for a site subscription on a metadata Web service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPSiteSubscriptionBusinessDataCatalogConfig](Clear-SPSiteSubscriptionBusinessDataCatalogConfig.md) -Deletes all data from the Business Data Connectivity Metadata Store for a specified partition. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPSiteSubscriptionBusinessDataCatalogConfig](Export-SPSiteSubscriptionBusinessDataCatalogConfig.md) -Exports all data from the Business Data Connectivity Metadata Store associated with a partition. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Export-SPSiteSubscriptionSettings](Export-SPSiteSubscriptionSettings.md) -Creates a backup file of site subscription data. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteSubscription](Get-SPSiteSubscription.md) -Returns the site subscription for the given URL or all site subscriptions in the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteSubscriptionConfig](Get-SPSiteSubscriptionConfig.md) -Returns the configuration properties of a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteSubscriptionEdiscoveryHub](Get-SPSiteSubscriptionEdiscoveryHub.md) -Displays the eDiscovery hub for a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteSubscriptionEdiscoverySearchScope](Get-SPSiteSubscriptionEdiscoverySearchScope.md) -Displays the search scope for the eDiscovery hub of the specified site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteSubscriptionFeaturePack](Get-SPSiteSubscriptionFeaturePack.md) -Retrieves available SharePoint Feature sets or the Feature set assigned to a given site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteSubscriptionIRMConfig](Get-SPSiteSubscriptionIRMConfig.md) -Gets the Information Rights Management (IRM) settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPSiteSubscriptionMetadataConfig](Get-SPSiteSubscriptionMetadataConfig.md) -Returns the site subscription configuration settings for a Metadata Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPSiteSubscriptionBusinessDataCatalogConfig](Import-SPSiteSubscriptionBusinessDataCatalogConfig.md) -Imports data associated with an exported file that contains all data associated with the Business Data Connectivity Metadata Store for a given partition. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPSiteSubscriptionSettings](Import-SPSiteSubscriptionSettings.md) -Restores a backup of subscription site settings to the given subscription identifier. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSiteSubscription](New-SPSiteSubscription.md) -Creates a new site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSiteSubscriptionFeaturePack](New-SPSiteSubscriptionFeaturePack.md) -Creates a new SharePoint Feature set that can be used to limit the features available to a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteSubscription](Remove-SPSiteSubscription.md) -Removes data stored in a subscription settings service application for a set of site subscriptions. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteSubscriptionBusinessDataCatalogConfig](Remove-SPSiteSubscriptionBusinessDataCatalogConfig.md) -Removes the Business Data Connectivity Metadata Store for a partition. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteSubscriptionFeaturePack](Remove-SPSiteSubscriptionFeaturePack.md) -Removes a SharePoint Feature set from a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteSubscriptionFeaturePackMember](Remove-SPSiteSubscriptionFeaturePackMember.md) -Removes a feature definition from the provided SharePoint Feature set. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteSubscriptionMetadataConfig](Remove-SPSiteSubscriptionMetadataConfig.md) -Removes site subscription configuration settings. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteSubscriptionProfileConfig](Remove-SPSiteSubscriptionProfileConfig.md) -Deletes a site subscription from a User Profile Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSiteSubscriptionSettings](Remove-SPSiteSubscriptionSettings.md) -Removes the settings service data for a specified site subscription, or finds and removes orphaned data. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSiteSubscriptionConfig](Set-SPSiteSubscriptionConfig.md) -Sets the configuration properties of a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSiteSubscriptionEdiscoveryHub](Set-SPSiteSubscriptionEdiscoveryHub.md) -Sets properties for the eDiscovery hub of a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSiteSubscriptionIRMConfig](Set-SPSiteSubscriptionIRMConfig.md) -Sets the Information Rights Management (IRM) settings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSiteSubscriptionMetadataConfig](Set-SPSiteSubscriptionMetadataConfig.md) -Sets the site subscription configuration settings for a specified Metadata Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSiteSubscriptionProfileConfig](Set-SPSiteSubscriptionProfileConfig.md) -Sets the parameters of a site subscription. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### State Service - - -#### [Dismount-SPStateServiceDatabase](Dismount-SPStateServiceDatabase.md) -Removes the association to a state service database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPStateServiceApplication](Get-SPStateServiceApplication.md) -Returns state service applications on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPStateServiceApplicationProxy](Get-SPStateServiceApplicationProxy.md) -Returns state service application proxies on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPStateServiceDatabase](Get-SPStateServiceDatabase.md) -Returns a state service database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Initialize-SPStateServiceDatabase](Initialize-SPStateServiceDatabase.md) -Installs the state database schema into a state service database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Mount-SPStateServiceDatabase](Mount-SPStateServiceDatabase.md) -Attaches an existing state service database to the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPStateServiceApplication](New-SPStateServiceApplication.md) -Creates a new state service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPStateServiceApplicationProxy](New-SPStateServiceApplicationProxy.md) -Creates a proxy for a state service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPStateServiceDatabase](New-SPStateServiceDatabase.md) -Creates and provisions a new state service database and installs the state database schema into it. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPStateServiceDatabase](Remove-SPStateServiceDatabase.md) -Removes a state service database from a state service application and drops it from the SQL Server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Resume-SPStateServiceDatabase](Resume-SPStateServiceDatabase.md) -Resumes a paused state service database so that new rows of data are received. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPStateServiceApplication](Set-SPStateServiceApplication.md) -Updates the name of a state service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPStateServiceApplicationProxy](Set-SPStateServiceApplicationProxy.md) -Updates the name of a state service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPStateServiceDatabase](Set-SPStateServiceDatabase.md) -Updates properties of a state service database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Suspend-SPStateServiceDatabase](Suspend-SPStateServiceDatabase.md) -Pauses a state database and thus prevents new rows of data from being added to a database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Subscription Settings Service - - -#### [New-SPSubscriptionSettingsServiceApplication](New-SPSubscriptionSettingsServiceApplication.md) -Creates a new subscription settings service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPSubscriptionSettingsServiceApplicationProxy](New-SPSubscriptionSettingsServiceApplicationProxy.md) -Creates an application proxy to a subscription settings service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPSubscriptionSettingsServiceApplication](Set-SPSubscriptionSettingsServiceApplication.md) -Sets properties of a subscription settings service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Topology Service - - -#### [Get-SPTopologyServiceApplication](Get-SPTopologyServiceApplication.md) -Displays properties of the topology service application for the current farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPTopologyServiceApplicationProxy](Get-SPTopologyServiceApplicationProxy.md) -Retrieves the topology service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTopologyServiceApplication](Set-SPTopologyServiceApplication.md) -Sets the properties on the topology service application of the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPTopologyServiceApplicationProxy](Set-SPTopologyServiceApplicationProxy.md) -Sets the proxy properties of the topology service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Usage and Health Services - - -#### [Add-SPDiagnosticsPerformanceCounter](Add-SPDiagnosticsPerformanceCounter.md) -Adds a new instance of a performance counter to a Web front end computer or a database server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPHealthAnalysisRule](Disable-SPHealthAnalysisRule.md) -Disables health analyzer rules. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPHealthAnalysisRule](Enable-SPHealthAnalysisRule.md) -Enables a health analyzer rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDiagnosticConfig](Get-SPDiagnosticConfig.md) -Retrieves ULS diagnostic configuration values of the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDiagnosticsPerformanceCounter](Get-SPDiagnosticsPerformanceCounter.md) -Returns a collection of performance counters. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDiagnosticsProvider](Get-SPDiagnosticsProvider.md) -Returns a diagnostics provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPHealthAnalysisRule](Get-SPHealthAnalysisRule.md) -Gets a health analyzer rule. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPHelpCollection](Get-SPHelpCollection.md) -Returns Help collection files. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUsageApplication](Get-SPUsageApplication.md) -Returns a specified usage application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUsageDefinition](Get-SPUsageDefinition.md) -Returns a usage definition object. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUsageService](Get-SPUsageService.md) -Returns a usage service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Merge-SPUsageLog](Merge-SPUsageLog.md) -Returns records from usage log files. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPUsageApplication](New-SPUsageApplication.md) -Creates a new usage application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPUsageLogFile](New-SPUsageLogFile.md) -Starts a new usage log file on the current server computer. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPDiagnosticsPerformanceCounter](Remove-SPDiagnosticsPerformanceCounter.md) -Removes an instance of a performance counter. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPUsageApplication](Remove-SPUsageApplication.md) -Removes a usage application from the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPDiagnosticConfig](Set-SPDiagnosticConfig.md) -Sets diagnostic configuration settings on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPDiagnosticsProvider](Set-SPDiagnosticsProvider.md) -Enables a diagnostics provider and updates its retention policy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPUsageApplication](Set-SPUsageApplication.md) -Sets properties of a usage application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPUsageDefinition](Set-SPUsageDefinition.md) -Sets the retention period for a usage provider. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPUsageService](Set-SPUsageService.md) -Updates the properties of a usage service. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPDiagnosticsSession](Start-SPDiagnosticsSession.md) -Starts a diagnostic session to report diagnostic information to the usage database. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Stop-SPDiagnosticsSession](Stop-SPDiagnosticsSession.md) -Stops a diagnostic session. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### User Licensing - - -#### [Add-SPUserLicenseMapping](Add-SPUserLicenseMapping.md) -Maps a security group, forms-based role, or claim to a SharePoint user license. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPUserLicensing](Disable-SPUserLicensing.md) -Disables user license enforcement. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPUserLicensing](Enable-SPUserLicensing.md) -Enables user-license enforcement. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUserLicense](Get-SPUserLicense.md) -Returns the list of supported SharePoint user licenses. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUserLicenseMapping](Get-SPUserLicenseMapping.md) -Returns the claim-to-user license mappings. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPUserLicensing](Get-SPUserLicensing.md) -Returns the state of user-license enforcement. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPUserLicenseMapping](New-SPUserLicenseMapping.md) -Creates a license mapping object. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPUserLicenseMapping](Remove-SPUserLicenseMapping.md) -Removes a claim-to-SharePoint user license mapping. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### User Profile Service - - -#### [Add-SPPluggableSecurityTrimmer](Add-SPPluggableSecurityTrimmer.md) -Adds a pluggable security trimmer to a Profile service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPProfileLeader](Add-SPProfileLeader.md) -Adds a company leader. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Add-SPProfileSyncConnection](Add-SPProfileSyncConnection.md) -Adds a synchronization connection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Clear-SPContentDatabaseSyncData](Clear-SPContentDatabaseSyncData.md) -Clears synchronization information from the content databases that have not been synchronized since the mentioned number of days. Platform: SharePoint Server 2019. - -#### [Export-SPTagsAndNotesData](Export-SPTagsAndNotesData.md) -Exports the SharePoint Newsfeed tags and notes from the SharePoint database to a ZIP file. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPMicrofeedOptions](Get-SPMicrofeedOptions.md) -Returns the feed cache settings for the current user profile application. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPPluggableSecurityTrimmer](Get-SPPluggableSecurityTrimmer.md) -Gets pluggable security trimmers added to a profile service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPProfileLeader](Get-SPProfileLeader.md) -Returns the current company leaders. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPProfileServiceApplicationSecurity](Get-SPProfileServiceApplicationSecurity.md) -Returns permission and identity information. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Move-SPSocialComment](Move-SPSocialComment.md) -Moves social comments. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPProfileServiceApplication](New-SPProfileServiceApplication.md) -Adds a User Profile Service Application to a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPProfileServiceApplicationProxy](New-SPProfileServiceApplicationProxy.md) -Creates a User Profile Service application proxy on the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPActivityFeedItems](Remove-SPActivityFeedItems.md) -Removes activity events from the published and consolidated tables. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPPluggableSecurityTrimmer](Remove-SPPluggableSecurityTrimmer.md) -Removes a pluggable security trimmer from a profile service application proxy. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPProfileLeader](Remove-SPProfileLeader.md) -Remove a company leader. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPProfileSyncConnection](Remove-SPProfileSyncConnection.md) -Removes a synchronization connection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPSocialItemByDate](Remove-SPSocialItemByDate.md) -Deletes tags, notes, or ratings. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPDefaultProfileConfig](Set-SPDefaultProfileConfig.md) -Changes the MySitesPublicEnabled property of the User Profile Application Proxy. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPMicrofeedOptions](Set-SPMicrofeedOptions.md) -Sets the feed cache settings. Platform: SharePoint Server 2016, SharePoint Server 2019 -#### [Set-SPProfileServiceApplication](Set-SPProfileServiceApplication.md) -Sets properties of a User Profile Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPProfileServiceApplicationProxy](Set-SPProfileServiceApplicationProxy.md) -Sets properties of a proxy for a User Profile Service application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPProfileServiceApplicationSecurity](Set-SPProfileServiceApplicationSecurity.md) -Sets permission and identity information. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPProfilePhotoStore](Update-SPProfilePhotoStore.md) -Updates the profile photo store to be compatible with SharePoint Server. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPRepopulateMicroblogFeedCache](Update-SPRepopulateMicroblogFeedCache.md) -Refreshes the microblog feed cache. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Update-SPRepopulateMicroblogLMTCache](Update-SPRepopulateMicroblogLMTCache.md) -Refreshes the cache. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPProfileServiceApplication](Upgrade-SPProfileServiceApplication.md) -Upgrades User Profile Service and its related profile and social store. Platform: SharePoint Server 2016, SharePoint Server 2019. - -### Visio Services - - -#### [Get-SPVisioExternalData](Get-SPVisioExternalData.md) -Returns the settings for external data connections for a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPVisioPerformance](Get-SPVisioPerformance.md) -Returns the Visio Services settings for the performance of a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPVisioSafeDataProvider](Get-SPVisioSafeDataProvider.md) -Returns the settings of a safe data provider for a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPVisioServiceApplication](Get-SPVisioServiceApplication.md) -Returns properties of a Visio Services application or a collection of Visio Services applications. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPVisioServiceApplicationProxy](Get-SPVisioServiceApplicationProxy.md) -Returns properties of a Visio Services application proxy or a collection of Visio Services application proxies. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPVisioSafeDataProvider](New-SPVisioSafeDataProvider.md) -Adds a new data provider to a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPVisioServiceApplication](New-SPVisioServiceApplication.md) -Adds a new Visio Services application to a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPVisioServiceApplicationProxy](New-SPVisioServiceApplicationProxy.md) -Adds a new Visio Services application proxy to a farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPVisioSafeDataProvider](Remove-SPVisioSafeDataProvider.md) -Removes a data provider from a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPVisioExternalData](Set-SPVisioExternalData.md) -Configures settings related to external data connections for a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPVisioPerformance](Set-SPVisioPerformance.md) -Sets performance properties for a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPVisioSafeDataProvider](Set-SPVisioSafeDataProvider.md) -Specifies a description of a safe data provider for a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPVisioServiceApplication](Set-SPVisioServiceApplication.md) -Sets the ServiceApplicationPool property for a Visio Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Web - - -#### [Disable-SPWebTemplateForSiteMaster](Disable-SPWebTemplateForSiteMaster.md) -Disables the site master in the farm. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPWebTemplateForSiteMaster](Enable-SPWebTemplateForSiteMaster.md) -Creates a template for a site master. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWeb](Get-SPWeb.md) -Returns all subsites that match the given criteria. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWebTemplate](Get-SPWebTemplate.md) -Displays all globally installed site templates that match the given identity. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWebTemplatesEnabledForSiteMaster](Get-SPWebTemplatesEnabledForSiteMaster.md) -Returns a list of site master web templates. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Import-SPWeb](Import-SPWeb.md) -Imports a web, list, or library. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPWeb](New-SPWeb.md) -Creates a new site in an existing site collection. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPWeb](Remove-SPWeb.md) -Completely deletes the specified Web. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPWeb](Set-SPWeb.md) -Configures the specified subsite. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Web Application - - -#### [Convert-SPWebApplication](Convert-SPWebApplication.md) -Converts the authentication mode of a web application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Disable-SPWebApplicationHttpThrottling](Disable-SPWebApplicationHttpThrottling.md) -Turns off network throttling for a Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Enable-SPWebApplicationHttpThrottling](Enable-SPWebApplicationHttpThrottling.md) -Turns on network throttling for a Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPAlternateURL](Get-SPAlternateURL.md) -Returns all alternate URLs that match a given set of criteria. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPContentDeploymentJob](Get-SPContentDeploymentJob.md) -Returns a content deployment job or a collection of content deployment jobs. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPContentDeploymentPath](Get-SPContentDeploymentPath.md) -Returns a content deployment path or a collection of content deployment paths. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPCustomLayoutsPage](Get-SPCustomLayoutsPage.md) -Returns a mapping to a custom layout page. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPDesignerSettings](Get-SPDesignerSettings.md) -Displays SharePoint Designer features. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPManagedPath](Get-SPManagedPath.md) -Returns all managed paths that match the given criteria. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWebApplication](Get-SPWebApplication.md) -Returns all Web applications that match the given criteria. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWebApplicationAppDomain](Get-SPWebApplicationAppDomain.md) -Returns all app domains for a specific web application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWebApplicationHttpThrottlingMonitor](Get-SPWebApplicationHttpThrottlingMonitor.md) -Returns all counters and their associated Health Score bucket values for network throttling on a Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPAlternateURL](New-SPAlternateURL.md) -Creates a new public or internal URL for the specified Web application zone or resource. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPContentDeploymentJob](New-SPContentDeploymentJob.md) -Creates a content deployment job. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPContentDeploymentPath](New-SPContentDeploymentPath.md) -Creates a new content deployment path. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPManagedPath](New-SPManagedPath.md) -Creates a new managed path for the given Web application for all host header site collections. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPWebApplication](New-SPWebApplication.md) -Creates a new Web application within the local farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPWebApplicationAppDomain](New-SPWebApplicationAppDomain.md) -Creates an AppDomain entry. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPWebApplicationExtension](New-SPWebApplicationExtension.md) -Creates a new zone instance for the Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPAlternateURL](Remove-SPAlternateURL.md) -Completely deletes the specified alternate URL. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPContentDeploymentJob](Remove-SPContentDeploymentJob.md) -Removes a content deployment job. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPContentDeploymentPath](Remove-SPContentDeploymentPath.md) -Removes a content deployment path. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPManagedPath](Remove-SPManagedPath.md) -Deletes the specified managed path from the specified host header or Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPWebApplication](Remove-SPWebApplication.md) -Deletes the specified Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPWebApplicationAppDomain](Remove-SPWebApplicationAppDomain.md) -Deletes the AppDomain. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPAlternateURL](Set-SPAlternateURL.md) -Configures the specified alternate URL. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPContentDeploymentJob](Set-SPContentDeploymentJob.md) -Sets properties of a content deployment job. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPContentDeploymentPath](Set-SPContentDeploymentPath.md) -Sets properties of a content deployment path. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPDesignerSettings](Set-SPDesignerSettings.md) -Sets SharePoint Designer features. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPWebApplication](Set-SPWebApplication.md) -Configures the specified Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPWebApplicationHttpThrottlingMonitor](Set-SPWebApplicationHttpThrottlingMonitor.md) -Sets the Health Score bucket values for an existing network throttling performance counter for a specified Web application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Start-SPContentDeploymentJob](Start-SPContentDeploymentJob.md) -Starts a content deployment job. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Word Automation Services - - -#### [New-SPWordConversionServiceApplication](New-SPWordConversionServiceApplication.md) -Creates a new instance of a Word Automation Services application on the farm. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Remove-SPWordConversionServiceJobHistory](Remove-SPWordConversionServiceJobHistory.md) -Removes entries from the Word Automation Services job history database. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPWordConversionServiceApplication](Set-SPWordConversionServiceApplication.md) -Sets properties of a Word Automation Services application. Platform: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### Work Management Service - - -#### [New-SPWorkManagementServiceApplication](New-SPWorkManagementServiceApplication.md) -Creates a new Work Management Service application. Platform: SharePoint Server 2013. - -#### [New-SPWorkManagementServiceApplicationProxy](New-SPWorkManagementServiceApplicationProxy.md) -Creates a new Work Management Service application proxy. Platform: SharePoint Server 2013. - -#### [Set-SPWorkManagementServiceApplication](Set-SPWorkManagementServiceApplication.md) -Sets settings for the Work Management Service application. Platform: SharePoint Server 2013. - -#### [Set-SPWorkManagementServiceApplicationProxy](Set-SPWorkManagementServiceApplicationProxy.md) -Sets the settings for the Work Management Service application proxy. Platform: SharePoint Server 2013. - -### Workflow Service (SharePoint 2013 Workflows / Workflow Manager) - - -#### [Copy-SPActivitiesToWorkflowService](Copy-SPActivitiesToWorkflowService.md) -Copies the Workflow Activities from SharePoint to Workflow Manager. Activities are defined within Microsoft provided or custom coded assemblies. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWorkflowConfig](Get-SPWorkflowConfig.md) -Returns workflow settings for the specified Web application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Get-SPWorkflowServiceApplicationProxy](Get-SPWorkflowServiceApplicationProxy.md) -Returns the Workflow Service Application Proxy. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPWorkflowServiceApplicationProxy](New-SPWorkflowServiceApplicationProxy.md) -Creates a proxy to connect to Workflow Manager. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Register-SPWorkflowService](Register-SPWorkflowService.md) -Registers a Workflow Manager farm with the SharePoint farm. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [Set-SPWorkflowConfig](Set-SPWorkflowConfig.md) -Configures the workflow settings for the specified Web application. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -### DO NOT USE - - -#### [Add-SPEduClassMember](Add-SPEduClassMember.md) -DO NOT USE. Platform: SharePoint Server 2013. - -#### [Add-SPEduUser](Add-SPEduUser.md) -DO NOT USE. Platform: SharePoint Server 2013. - -#### [Dismount-SPSiteMapDatabase](Dismount-SPSiteMapDatabase.md) -DO NOT USE. Platform: SharePoint Server 2016. - -#### [Get-SPEduServiceSetting](Get-SPEduServiceSetting.md) -DO NOT USE. Platform: SharePoint Server 2013. - -#### [Get-SPSiteMapDatabase](Get-SPSiteMapDatabase.md) -DO NOT USE. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Install-SPEduSites](Install-SPEduSites.md) -DO NOT USE. Platform: SharePoint Server 2013. - -#### [Migrate-SPDatabase](Migrate-SPDatabase.md) -DO NOT USE. Platform: SharePoint Server 2016. - -#### [Move-SPAppManagementData](Move-SPAppManagementData.md) -DO NOT USE. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Mount-SPSiteMapDatabase](Mount-SPSiteMapDatabase.md) -DO NOT USE. Platform: SharePoint Server 2016. - -#### [New-SPBECWebServiceApplicationProxy](New-SPBECWebServiceApplicationProxy.md) -DO NOT USE. Platform: SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019. - -#### [New-SPEduClass](New-SPEduClass.md) -DO NOT USE. Platform: SharePoint Server 2013. - -#### [Remove-SPEduClassMember](Remove-SPEduClassMember.md) -DO NOT USE. Platform: SharePoint Server 2013. - -#### [Set-SPEduServiceSetting](Set-SPEduServiceSetting.md) -DO NOT USE. Platform: SharePoint Server 2013. - -#### [Upgrade-SPAppManagementServiceApplication](Upgrade-SPAppManagementServiceApplication.md) -DO NOT USE. Platform: SharePoint Server 2016, SharePoint Server 2019. - -#### [Upgrade-SPSiteMapDatabase](Upgrade-SPSiteMapDatabase.md) -DO NOT USE. Platform: SharePoint Server 2016, SharePoint Server 2019. diff --git a/skype/docfx.json b/skype/docfx.json index 533e2734d0..4b1f9f1bd1 100644 --- a/skype/docfx.json +++ b/skype/docfx.json @@ -2,7 +2,9 @@ "build": { "content": [ { - "files": ["**/*.md"], + "files": [ + "**/*.md" + ], "src": "docs-conceptual", "version": "skype-ps", "dest": "skype", @@ -12,26 +14,44 @@ "README.md", "LICENSE", "LICENSE-CODE", - "ThirdPartyNotices"] + "ThirdPartyNotices" + ] }, { - "files": ["toc.yml"], + "files": [ + "toc.yml" + ], "src": "docs-conceptual", "version": "skype-ps", "dest": "skype/skype-ps" }, { - "files": ["**/*.md"], - "src": "skype-ps", - "version": "skype-ps", - "dest": "module" - }, - { - "files": ["toc.yml"], - "src": "skype-ps", - "version": "skype-ps", - "dest": "module/skype-ps" - } + "files": [ + "**/*.yml" + ], + "exclude": [ + "toc.yml" + ], + "src": "skype-ps", + "version": "skype-ps", + "dest": "module" + }, + { + "files": [ + "toc.yml" + ], + "src": "skype-ps", + "version": "skype-ps", + "dest": "module/skype-ps" + }, + { + "files": [ + "**/*.md" + ], + "src": "virtual-folder", + "version": "skype-ps", + "dest": "module" + } ], "resource": [ { @@ -53,16 +73,21 @@ "overwrite": [], "externalReference": [], "globalMetadata": { - "author" : "kenwith", - "ms.author" : "kenwith", - "manager" : "serdars", - "ms.date" : "09/25/2017", - "ms.topic" : "reference", - "ms.service" : "skypeforbusiness-powershell", - "ms.devlang" : "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" + "uhfHeaderId": "MSDocsHeader-M365-IT", + "author": "serdarsoysal", + "ms.author": "serdars", + "manager": "serdars", + "ms.date": "04/04/2023", + "ms.topic": "reference", + "ms.service": "skypeforbusiness-powershell", + "products": [ + "https://authoring-docs-microsoft.poolparty.biz/devrel/74b1e9df-8124-4d0c-b310-50c3bf3ff02b", + "https://authoring-docs-microsoft.poolparty.biz/devrel/63959238-cb90-4871-a33d-4a5519097e47", + "https://authoring-docs-microsoft.poolparty.biz/devrel/8bce367e-2e90-4b56-9ed5-5e4e9f3a2dc3" + ], + "ms.devlang": "powershell", + "feedback_system": "Standard", + "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" }, "fileMetadata": {}, "template": [], diff --git a/skype/docs-conceptual/index.md b/skype/docs-conceptual/index.md index 7bff2d7098..d2fa109425 100644 --- a/skype/docs-conceptual/index.md +++ b/skype/docs-conceptual/index.md @@ -1,15 +1,16 @@ --- -localization_priority: Normal -title: Skype for Business cmdlet reference +ms.localizationpriority: medium +title: Skype for Business cmdlet help reference +description: "Learn about the Skype for Business PowerShell cmdlet help reference." --- -# Skype for Business cmdlet reference +# Skype for Business cmdlet help reference -Welcome to the Skype for Business PowerShell cmdlet help references. The Skype for Business cmdlets provide the command line interface for server and service administration and management. +Welcome to the Skype for Business PowerShell cmdlet **Help** reference. The Skype for Business cmdlets provide the command line interface for server and service administration and management. > [!IMPORTANT] -> As you migrate to Microsoft Teams you will find that some of the cmdlets in the Skype for Business Online module are also used for Microsoft Teams. To learn more about this, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview). +> As you migrate to Microsoft Teams, you will find that some of the cmdlets in the Skype for Business Online module are also used for Microsoft Teams. To learn more about this, see: [Teams PowerShell Overview](/MicrosoftTeams/teams-powershell-overview). -Here you will find all of the Skype for Business and relevant Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. +Here, you will find all of the Skype for Business and relevant Microsoft Teams PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README. -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. +The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page. diff --git a/skype/docs-conceptual/intro.md b/skype/docs-conceptual/intro.md index 7bff2d7098..309683be13 100644 --- a/skype/docs-conceptual/intro.md +++ b/skype/docs-conceptual/intro.md @@ -1,15 +1,16 @@ --- -localization_priority: Normal -title: Skype for Business cmdlet reference +ms.localizationpriority: medium +title: Skype for Business Server cmdlet reference +description: "Learn about Skype for Business Server cmdlets." --- -# Skype for Business cmdlet reference +# Skype for Business Server cmdlet reference -Welcome to the Skype for Business PowerShell cmdlet help references. The Skype for Business cmdlets provide the command line interface for server and service administration and management. +Welcome to the Skype for Business Server PowerShell cmdlet help references. The Skype for Business Server cmdlets provide the command line interface for server administration and management. > [!IMPORTANT] -> As you migrate to Microsoft Teams you will find that some of the cmdlets in the Skype for Business Online module are also used for Microsoft Teams. To learn more about this, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview). +> As you migrate to Microsoft Teams, to learn more, see: [Teams PowerShell Overview](/MicrosoftTeams/teams-powershell-overview). -Here you will find all of the Skype for Business and relevant Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. +Here you will find all of the Skype for Business Server. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. +The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page. diff --git a/skype/mapping/monikerMapping.json b/skype/mapping/MAML2Yaml/monikerMapping.json similarity index 100% rename from skype/mapping/monikerMapping.json rename to skype/mapping/MAML2Yaml/monikerMapping.json diff --git a/skype/skype-ps/skype/Add-CsSlaDelegates.md b/skype/skype-ps/skype/Add-CsSlaDelegates.md index 430c1da6eb..3700e12bc1 100644 --- a/skype/skype-ps/skype/Add-CsSlaDelegates.md +++ b/skype/skype-ps/skype/Add-CsSlaDelegates.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/add-cssladelegates -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/add-cssladelegates +applicable: Skype for Business Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Add-CsSlaDelegates schema: 2.0.0 manager: rogupta @@ -63,16 +63,12 @@ Accept wildcard characters: False ### -Identity Indicates the identity of the shared number to which the delegate will be added. User identities can be specified using one of five formats: -- SIP address - - Example: sip:kenmyer@litwareinc.com -- User principal name (UPN) - - Example: kenmyer@litwareinc.com -- Domain name and logon name in the form domain\logon - - Example: litwareinc\kenmyer -- Active Directory display name (this form typically requires quotes) - - Example: "Ken Myer" -- Active Directory distinguished name - - Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com + +- SIP address: Example. sip:kenmyer@litwareinc.com. +- User principal name (UPN). Example: kenmyer@litwareinc.com. +- Domain name and logon name in the form domain\logon. Example: litwareinc\kenmyer. +- Active Directory display name (this form typically requires quotes). Example: "Ken Myer". +- Active Directory distinguished name. Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com ```yaml Type: UserIdParameter @@ -147,4 +143,3 @@ The `Add-CsSlaDelegates` cmdlet returns a Microsoft.Rtc.Management.SlaConfigurat ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Approve-CsDeviceUpdateRule.md b/skype/skype-ps/skype/Approve-CsDeviceUpdateRule.md index 23c0247ac1..e35882d1bb 100644 --- a/skype/skype-ps/skype/Approve-CsDeviceUpdateRule.md +++ b/skype/skype-ps/skype/Approve-CsDeviceUpdateRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/approve-csdeviceupdaterule +online version: https://learn.microsoft.com/powershell/module/skype/approve-csdeviceupdaterule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Approve-CsDeviceUpdateRule schema: 2.0.0 @@ -191,4 +191,3 @@ Instead, the `Approve-CsDeviceUpdateRule` cmdlet approves instances of the Micro [Reset-CsDeviceUpdateRule](Reset-CsDeviceUpdateRule.md) [Restore-CsDeviceUpdateRule](Restore-CsDeviceUpdateRule.md) - diff --git a/skype/skype-ps/skype/Backup-CsPool.md b/skype/skype-ps/skype/Backup-CsPool.md index 02e07dd172..ebbf326a13 100644 --- a/skype/skype-ps/skype/Backup-CsPool.md +++ b/skype/skype-ps/skype/Backup-CsPool.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/backup-cspool +online version: https://learn.microsoft.com/powershell/module/skype/backup-cspool applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Backup-CsPool schema: 2.0.0 @@ -290,4 +290,3 @@ None. [Get-CsBackupServiceStatus](Get-CsBackupServiceStatus.md) [Get-CsPoolBackupRelationship](Get-CsPoolBackupRelationship.md) - diff --git a/skype/skype-ps/skype/Clear-CsDeviceUpdateFile.md b/skype/skype-ps/skype/Clear-CsDeviceUpdateFile.md index 0056784f78..4565de64c5 100644 --- a/skype/skype-ps/skype/Clear-CsDeviceUpdateFile.md +++ b/skype/skype-ps/skype/Clear-CsDeviceUpdateFile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/clear-csdeviceupdatefile +online version: https://learn.microsoft.com/powershell/module/skype/clear-csdeviceupdatefile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Clear-CsDeviceUpdateFile schema: 2.0.0 @@ -137,4 +137,3 @@ The `Clear-CsDeviceUpdateFile` cmdlet does not return any values. [Clear-CsDeviceUpdateLog](Clear-CsDeviceUpdateLog.md) [Get-CsDeviceUpdateConfiguration](Get-CsDeviceUpdateConfiguration.md) - diff --git a/skype/skype-ps/skype/Clear-CsDeviceUpdateLog.md b/skype/skype-ps/skype/Clear-CsDeviceUpdateLog.md index 9131d5f825..37114a8907 100644 --- a/skype/skype-ps/skype/Clear-CsDeviceUpdateLog.md +++ b/skype/skype-ps/skype/Clear-CsDeviceUpdateLog.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/clear-csdeviceupdatelog +online version: https://learn.microsoft.com/powershell/module/skype/clear-csdeviceupdatelog applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Clear-CsDeviceUpdateLog schema: 2.0.0 @@ -154,4 +154,3 @@ The `Clear-CsDeviceUpdateLog` cmdlet does not return any values. [Clear-CsDeviceUpdateFile](Clear-CsDeviceUpdateFile.md) [Get-CsDeviceUpdateConfiguration](Get-CsDeviceUpdateConfiguration.md) - diff --git a/skype/skype-ps/skype/Clear-CsOnlineTelephoneNumberReservation.md b/skype/skype-ps/skype/Clear-CsOnlineTelephoneNumberReservation.md deleted file mode 100644 index 982aced678..0000000000 --- a/skype/skype-ps/skype/Clear-CsOnlineTelephoneNumberReservation.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/clear-csonlinetelephonenumberreservation -applicable: Skype for Business Online -title: Clear-CsOnlineTelephoneNumberReservation -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Clear-CsOnlineTelephoneNumberReservation - -## SYNOPSIS -Use the `Clear-CsOnlineTelephoneNumberReservation` cmdlet to clear a reserved list of telephone numbers before they are acquired. -The telephone numbers will then be available for search and reservation again. - -## SYNTAX - -``` -Clear-CsOnlineTelephoneNumberReservation [-Tenant <Guid>] -ReservationId <String> - -InventoryType <String> [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet will fail if any of the numbers in the reservation have already been assigned. -An error message will identify the source of the failure. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Clear-CsOnlineTelephoneNumberReservation -ReservationId b1ae43f5-07ab-4b81-be32-4b8cc2d11f75 -InventoryType Service -``` - -This example clears a reservation with an inventory type of "Service". - - -## PARAMETERS - -### -InventoryType -Specifies the target telephone number type for the cmdlet. -Acceptable values are: - -- "Service" for numbers assigned to conferencing support. - -- "Subscriber" for numbers supporting public switched telephone network (PSTN) functions. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReservationId -Specifies the identification of the reservation you want to clear. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -None - -## OUTPUTS - -### -None - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Clear-CsPersistentChatRoom.md b/skype/skype-ps/skype/Clear-CsPersistentChatRoom.md index 6e70c34631..e6cc17f0f3 100644 --- a/skype/skype-ps/skype/Clear-CsPersistentChatRoom.md +++ b/skype/skype-ps/skype/Clear-CsPersistentChatRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/clear-cspersistentchatroom -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/clear-cspersistentchatroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Clear-CsPersistentChatRoom schema: 2.0.0 manager: rogupta @@ -180,4 +180,3 @@ None. Instead, `Clear-CsPersistentChatRoom` modifies existing instances of the M ## RELATED LINKS [Remove-CsPersistentChatMessage](Remove-CsPersistentChatMessage.md) - diff --git a/skype/skype-ps/skype/Complete-CsCceApplianceRegistration.md b/skype/skype-ps/skype/Complete-CsCceApplianceRegistration.md deleted file mode 100644 index d2a76140c6..0000000000 --- a/skype/skype-ps/skype/Complete-CsCceApplianceRegistration.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/complete-cscceapplianceregistration -applicable: Skype for Business Online -title: Complete-CsCceApplianceRegistration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Complete-CsCceApplianceRegistration - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -``` -Complete-CsCceApplianceRegistration [[-Identity] <Object>] [-BypassDualWrite <Object>] [-Confirm] [-Force] [-Instance <Object>] [-Tenant <Object>] [-WhatIf] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` - -``` - -Insert descriptive text for example 1. - -Insert example commands for example 1. - -## PARAMETERS - -### -Identity -PARAMVALUE: XdsGlobalRelativeIdentity - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassDualWrite -PARAMVALUE: $true | $false - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -PARAMVALUE: PSObject - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Complete-CsCceApplianceUnregistration.md b/skype/skype-ps/skype/Complete-CsCceApplianceUnregistration.md deleted file mode 100644 index 29963840f2..0000000000 --- a/skype/skype-ps/skype/Complete-CsCceApplianceUnregistration.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/complete-cscceapplianceunregistration -applicable: Skype for Business Online -title: Complete-CsCceApplianceUnregistration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Complete-CsCceApplianceUnregistration - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -``` -Complete-CsCceApplianceUnregistration [[-Identity] <Object>] [-BypassDualWrite <Object>] [-Confirm] [-Force] - [-Tenant <Object>] [-WhatIf] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -Identity -PARAMVALUE: XdsGlobalRelativeIdentity - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassDualWrite -PARAMVALUE: $true | $false - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Convert-CsUserData.md b/skype/skype-ps/skype/Convert-CsUserData.md index 88b9a2c207..36e5bfd5b6 100644 --- a/skype/skype-ps/skype/Convert-CsUserData.md +++ b/skype/skype-ps/skype/Convert-CsUserData.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/convert-csuserdata +online version: https://learn.microsoft.com/powershell/module/skype/convert-csuserdata applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Convert-CsUserData schema: 2.0.0 @@ -204,4 +204,3 @@ The `Convert-CsUserData` cmdlet creates either XML or ZIP files, depending on wh [Sync-CsUserData](Sync-CsUserData.md) [Update-CsUserData](Update-CsUserData.md) - diff --git a/skype/skype-ps/skype/ConvertTo-JsonForPSWS.md b/skype/skype-ps/skype/ConvertTo-JsonForPSWS.md index ba8b9ec208..a337781345 100644 --- a/skype/skype-ps/skype/ConvertTo-JsonForPSWS.md +++ b/skype/skype-ps/skype/ConvertTo-JsonForPSWS.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/convertto-jsonforpsws +online version: https://learn.microsoft.com/powershell/module/skype/convertto-jsonforpsws applicable: Skype for Business Online title: ConvertTo-JsonForPSWS schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # ConvertTo-JsonForPSWS @@ -176,5 +176,4 @@ You can pipe any object to ConvertTo-JsonForPSWS. ## RELATED LINKS -[ConvertTo-Json](https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/convertto-json?view=powershell-6) - +[ConvertTo-Json](https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/convertto-json?view=powershell-6) diff --git a/skype/skype-ps/skype/Copy-CsVoicePolicy.md b/skype/skype-ps/skype/Copy-CsVoicePolicy.md index 8996b31a5c..2b2f8404d0 100644 --- a/skype/skype-ps/skype/Copy-CsVoicePolicy.md +++ b/skype/skype-ps/skype/Copy-CsVoicePolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/copy-csvoicepolicy -applicable: Lync Server 2013, Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/skype/copy-csvoicepolicy +applicable: Lync Server 2013 title: Copy-CsVoicePolicy schema: 2.0.0 manager: bulenteg @@ -126,21 +126,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### CommonParameters ## INPUTS @@ -150,4 +135,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Debug-CsAddressBookReplication.md b/skype/skype-ps/skype/Debug-CsAddressBookReplication.md index 09f1f4b773..1afa8db7a1 100644 --- a/skype/skype-ps/skype/Debug-CsAddressBookReplication.md +++ b/skype/skype-ps/skype/Debug-CsAddressBookReplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/debug-csaddressbookreplication +online version: https://learn.microsoft.com/powershell/module/skype/debug-csaddressbookreplication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Debug-CsAddressBookReplication schema: 2.0.0 @@ -307,4 +307,3 @@ The Debug-CsAddressBookReplication cmdlet returns instances of the Microsoft.Rtc [Test-CsAddressBookService](Test-CsAddressBookService.md) [Test-CsAddressBookWebQuery](Test-CsAddressBookWebQuery.md) - diff --git a/skype/skype-ps/skype/Debug-CsDataConference.md b/skype/skype-ps/skype/Debug-CsDataConference.md index a4c57fe0b3..6db0f9115d 100644 --- a/skype/skype-ps/skype/Debug-CsDataConference.md +++ b/skype/skype-ps/skype/Debug-CsDataConference.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/debug-csdataconference +online version: https://learn.microsoft.com/powershell/module/skype/debug-csdataconference applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Debug-CsDataConference schema: 2.0.0 @@ -124,4 +124,3 @@ The Debug-CsDataConference cmdlet does not accept pipelined input. ## RELATED LINKS [Test-CsDataConference](Test-CsDataConference.md) - diff --git a/skype/skype-ps/skype/Debug-CsInterPoolReplication.md b/skype/skype-ps/skype/Debug-CsInterPoolReplication.md index 49e3ff72e9..ebc215436e 100644 --- a/skype/skype-ps/skype/Debug-CsInterPoolReplication.md +++ b/skype/skype-ps/skype/Debug-CsInterPoolReplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/debug-csinterpoolreplication +online version: https://learn.microsoft.com/powershell/module/skype/debug-csinterpoolreplication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Debug-CsInterPoolReplication schema: 2.0.0 @@ -215,4 +215,3 @@ Debug-CsInterPoolReplication does not accept pipelined data. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Debug-CsIntraPoolReplication.md b/skype/skype-ps/skype/Debug-CsIntraPoolReplication.md index c8625322bc..5f9eb262df 100644 --- a/skype/skype-ps/skype/Debug-CsIntraPoolReplication.md +++ b/skype/skype-ps/skype/Debug-CsIntraPoolReplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/debug-csintrapoolreplication +online version: https://learn.microsoft.com/powershell/module/skype/debug-csintrapoolreplication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Debug-CsIntraPoolReplication schema: 2.0.0 @@ -249,4 +249,3 @@ Debug-CsIntraPoolReplication returns instances of the Microsoft.Rtc.Management.U [Get-CsManagementStoreReplicationStatus](Get-CsManagementStoreReplicationStatus.md) [Test-CsReplica](Test-CsReplica.md) - diff --git a/skype/skype-ps/skype/Debug-CsLisConfiguration.md b/skype/skype-ps/skype/Debug-CsLisConfiguration.md index c50d5143f8..11d2b846e0 100644 --- a/skype/skype-ps/skype/Debug-CsLisConfiguration.md +++ b/skype/skype-ps/skype/Debug-CsLisConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/debug-cslisconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/debug-cslisconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Debug-CsLisConfiguration schema: 2.0.0 @@ -109,4 +109,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Export-CsLisConfiguration](Export-CsLisConfiguration.md) [Test-CsLisConfiguration](Test-CsLisConfiguration.md) - diff --git a/skype/skype-ps/skype/Debug-CsStorageServiceFailures.md b/skype/skype-ps/skype/Debug-CsStorageServiceFailures.md index 14a5e9b6e2..417dd26a22 100644 --- a/skype/skype-ps/skype/Debug-CsStorageServiceFailures.md +++ b/skype/skype-ps/skype/Debug-CsStorageServiceFailures.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/debug-csstorageservicefailures +online version: https://learn.microsoft.com/powershell/module/skype/debug-csstorageservicefailures applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Debug-CsStorageServiceFailures schema: 2.0.0 @@ -282,4 +282,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Debug-CsUnifiedContactStore.md b/skype/skype-ps/skype/Debug-CsUnifiedContactStore.md index a784f4a021..df94000299 100644 --- a/skype/skype-ps/skype/Debug-CsUnifiedContactStore.md +++ b/skype/skype-ps/skype/Debug-CsUnifiedContactStore.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/debug-csunifiedcontactstore -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/debug-csunifiedcontactstore +applicable: Skype for Business Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Debug-CsUnifiedContactStore schema: 2.0.0 manager: rogupta @@ -159,4 +159,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Test-CsUnifiedContactStore](Test-CsUnifiedContactStore.md) - diff --git a/skype/skype-ps/skype/Disable-CsAdDomain.md b/skype/skype-ps/skype/Disable-CsAdDomain.md index dd51ae43ac..38a11de6d4 100644 --- a/skype/skype-ps/skype/Disable-CsAdDomain.md +++ b/skype/skype-ps/skype/Disable-CsAdDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-csaddomain +online version: https://learn.microsoft.com/powershell/module/skype/disable-csaddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Disable-CsAdDomain schema: 2.0.0 @@ -220,4 +220,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Enable-CsAdDomain](Enable-CsAdDomain.md) [Get-CsAdDomain](Get-CsAdDomain.md) - diff --git a/skype/skype-ps/skype/Disable-CsAdForest.md b/skype/skype-ps/skype/Disable-CsAdForest.md index f55c633d5a..c417b7c00c 100644 --- a/skype/skype-ps/skype/Disable-CsAdForest.md +++ b/skype/skype-ps/skype/Disable-CsAdForest.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-csadforest +online version: https://learn.microsoft.com/powershell/module/skype/disable-csadforest applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Disable-CsAdForest schema: 2.0.0 @@ -229,4 +229,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Disable-CsComputer.md b/skype/skype-ps/skype/Disable-CsComputer.md index 640b7ccc31..d6b985bdfd 100644 --- a/skype/skype-ps/skype/Disable-CsComputer.md +++ b/skype/skype-ps/skype/Disable-CsComputer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-cscomputer +online version: https://learn.microsoft.com/powershell/module/skype/disable-cscomputer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Disable-CsComputer schema: 2.0.0 @@ -195,4 +195,3 @@ Instead, Disable-CsComputer disables instances of the Microsoft.Rtc.Management.D [Get-CsComputer](Get-CsComputer.md) [Test-CsComputer](Test-CsComputer.md) - diff --git a/skype/skype-ps/skype/Disable-CsHostingProvider.md b/skype/skype-ps/skype/Disable-CsHostingProvider.md index e5b23f7907..ed00fbdde6 100644 --- a/skype/skype-ps/skype/Disable-CsHostingProvider.md +++ b/skype/skype-ps/skype/Disable-CsHostingProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-cshostingprovider +online version: https://learn.microsoft.com/powershell/module/skype/disable-cshostingprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Disable-CsHostingProvider schema: 2.0.0 @@ -202,4 +202,3 @@ Instead, the cmdlet disables instances of the Microsoft.Rtc.Management.WritableC [Remove-CsHostingProvider](Remove-CsHostingProvider.md) [Set-CsHostingProvider](Set-CsHostingProvider.md) - diff --git a/skype/skype-ps/skype/Disable-CsMeetingRoom.md b/skype/skype-ps/skype/Disable-CsMeetingRoom.md index 52ad83cd93..15cd889743 100644 --- a/skype/skype-ps/skype/Disable-CsMeetingRoom.md +++ b/skype/skype-ps/skype/Disable-CsMeetingRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-csmeetingroom -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/disable-csmeetingroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Disable-CsMeetingRoom schema: 2.0.0 manager: bulenteg @@ -19,12 +19,14 @@ When you disable a meeting room object you remove all the Skype for Business Ser However, the Active Directory user account itself is not deleted. This cmdlet was introduced in Lync Server 2013. +**Note**: This cmdlet is not supported for managing Microsoft Teams Rooms. You must use the methods described in the [Microsoft Teams Rooms](/microsoftteams/rooms) documentation to manage Microsoft Teams Rooms. + ## SYNTAX ``` Disable-CsMeetingRoom [-Identity] <UserIdParameter> [-Confirm] [-DomainController <Fqdn>] [-PassThru] [-WhatIf] - [-AsJob] [<CommonParameters>] + [<CommonParameters>] ``` ## DESCRIPTION @@ -157,22 +159,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -199,4 +185,3 @@ Instead, Disable-CsMeetingRoom deletes instance of the Microsoft.Rtc.Management. [Move-CsMeetingRoom](Move-CsMeetingRoom.md) [Set-CsMeetingRoom](Set-CsMeetingRoom.md) - diff --git a/skype/skype-ps/skype/Disable-CsOnlineDialInConferencingUser.md b/skype/skype-ps/skype/Disable-CsOnlineDialInConferencingUser.md deleted file mode 100644 index bc6adc7017..0000000000 --- a/skype/skype-ps/skype/Disable-CsOnlineDialInConferencingUser.md +++ /dev/null @@ -1,270 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-csonlinedialinconferencinguser -applicable: Skype for Business Online -title: Disable-CsOnlineDialInConferencingUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Disable-CsOnlineDialInConferencingUser - -## SYNOPSIS -Use the `Disable-CsOnlineDialInConferencingUser` cmdlet to prevent a Skype for Business Online user from using dial-in or audio conferencing through Skype for Business Online. - -## SYNTAX - -``` -Disable-CsOnlineDialInConferencingUser [-WhatIf] [-SendEmailFromDisplayName <String>] [-TenantDomain <String>] - [-SendEmailToAddress <String>] [-SendEmailFromAddress <String>] [-Confirm] [-SendEmail] [[-Identity] <UserIdParameter>] - [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -The `Disable-CsOnlineDialInConferencingUser` cmdlet validates that the user is provisioned for audio conferencing using Microsoft as the audio conferencing provider and then disables audio conferencing which prevents the user from setting up audio conferences or meetings. - -When a user is disabled, the conference ID or passcode that was assigned to the user is released so it can be used by another user that is enabled for dial-in or audio conferencing even if they have a license assigned to them. - -When you disable the user for audio conferencing using this cmdlet, it will check that the user belongs to the specified tenant or domain and any audio conferencing information is removed. - -If the user is enabled for a third-party audio conferencing provider (ACP) and the Active Directory information is set, the cmdlet will fail and you must use the Remove-CsUserACP cmdlet. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Disable-CsOnlineDialInConferencingUser -Identity "Pilar Ackerman" -Confirm -``` - -This example disables user "Pilar Ackerman" from using audio conferencing and will prompt you to confirm the operation. - - -## PARAMETERS - -### -Identity -Specifies the identity of the user account that will be disabled for Skype for Business Online. -A user identity can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). -You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmail -Send an email to the user containing their Audio Conference information. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromAddress -You can specify the From Address to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmailFromDisplayName and -SendEmail. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromDisplayName -You can specify the Display Name to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmailFromAddress and -SendEmail. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailToAddress -You can specify the To Address to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmail. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -NOTE: This parameter is reserved for internal Microsoft use. - -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308". -You can find your tenant ID by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantDomain -NOTE: This parameter is reserved for internal Microsoft use. - -Specifies the domain name for the tenant or organization. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Enable-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/enable-csonlinedialinconferencinguser?view=skype-ps) - -[Get-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinguser?view=skype-ps) - -[Set-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencinguser?view=skype-ps) diff --git a/skype/skype-ps/skype/Disable-CsOnlineSipDomain.md b/skype/skype-ps/skype/Disable-CsOnlineSipDomain.md deleted file mode 100644 index 205eaddb06..0000000000 --- a/skype/skype-ps/skype/Disable-CsOnlineSipDomain.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-csonlinesipdomain -applicable: Skype for Business Online -title: Disable-CsOnlineSipDomain -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: rogupta ---- - -# Disable-CsOnlineSipDomain - -## SYNOPSIS -This cmdlet prevents provisioning of users in Skype for Business Online for the specified domain. This cmdlet allows organizations with multiple on-premises deployments of Skype For Business Server or Lync Server to safely synchronize users from multiple forests into a single Office 365 tenant. - -## SYNTAX - -``` -Disable-CsOnlineSipDomain -Domain <String> [-Force] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -> [!NOTE] -> Only one Skype for Business forest can be in hybrid mode at a given time. For full details on this scenario, including step-by-step instructions, see [Cloud consolidation for Teams and Skype for Business](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation). - -This cmdlet enables organizations with *multiple on-premises deployments of Skype for Business Server (or Lync Server)* to safely synchronize users from multiple forests into a single Office 365 tenant. When an online SIP domain is disabled in Skype for Business Online, provisioning is blocked for users in this SIP domain. This ensures routing for any on-premises users in this SIP domain continues to function properly. - -This cmdlet facilitates consolidation of multiple Skype for Business Server deployments into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, **provided the following key requirements are met**: - -- There must be at most 1 O365 tenant involved. Consolidation in scenarios with >1 O365 tenant is not supported. -- At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.) -- If 1 deployment is in hybrid mode, all sip domains from any other SfB forests must be disabled using this cmdlet before they can be synchronized into the tenant with Azure AD Connect. Users in all SfB forests other than the hybrid forest must remain on-premises. -- Organizations must fully migrate each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment. - - -This cmdlet may also be useful for organizations with on-premises deployments of Skype for Business Server that have not properly configured Azure AD Connect. If the organization does not sync msRTCSIP-DeploymentLocator for its users, then Skype for Business Online will attempt to provision online any users with an assigned Skype for Business license, despite there being users on-premises. While the correct fix is to update the configuration for Azure AD Connect to sync those attributes, using Disable-CsOnlineSipDomain can also mitigate the problem until that configuration change can be made. If this cmdlet is run, any users that were previously provisioned online in that domain will be de-provisioned in Skype for Business Online. - -**IMPORTANT** -This cmdlet should not be run for domains that contain users hosted in Skype for Business Online. Any users in a sip domain that are already provisioned *online* will cease to function if you disable the online sip domain: - -- Their SIP addresses will be removed. -- All contacts and meetings for these users hosted in Skype for Business Online will be deleted. -- These users will no longer be able to login to the Skype for Business Online environment. -- If these users use Teams, they will no longer be able to inter-operate with Skype for Business users, nor will they be able to federate with any users in other organizations. - -## EXAMPLES - -### Example 1 -```powershell -Disable-CsOnlineSipDomain -Domain Fabrikam.com -``` - -The cmdlet above disables the online sip domain Fabrikam.com. This would be useful in the case where a company, Contoso.com, that has Skype for Business acquires Fabrikam, which also has an on-premises deployment of Skype for Business Server. If Contoso is in hybrid mode with Skype for Business Online or if the intent is to configure it for hybrid, then if the organization wants to synchronize identities from Fabrikam.com into the same O365 tenant, the organization must first run this cmdlet. - -## PARAMETERS - -### -Domain -The SIP domain to be disabled for online provisioning in Skype for Business Online. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses all confirmation prompts that might occur when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### None - -## NOTES -This cmdlet is for advanced scenarios only. Organizations that are pure online or have only 1 on-premises deployment need not run this cmdlet. - -## RELATED LINKS - -[Enable-CsOnlineSipDomain](Enable-CsOnlineSipDomain.md) - -[Get-CsOnlineSipDomain](Get-CsOnlineSipDomain.md) - -[Cloud consolidation for Teams and Skype for Business](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation) diff --git a/skype/skype-ps/skype/Disable-CsPublicProvider.md b/skype/skype-ps/skype/Disable-CsPublicProvider.md index fc8779952e..7fe6d0507f 100644 --- a/skype/skype-ps/skype/Disable-CsPublicProvider.md +++ b/skype/skype-ps/skype/Disable-CsPublicProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-cspublicprovider +online version: https://learn.microsoft.com/powershell/module/skype/disable-cspublicprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Disable-CsPublicProvider schema: 2.0.0 @@ -192,4 +192,3 @@ Instead, the cmdlet disables instances of the Microsoft.Rtc.Management.WritableC [Remove-CsPublicProvider](Remove-CsPublicProvider.md) [Set-CsPublicProvider](Set-CsPublicProvider.md) - diff --git a/skype/skype-ps/skype/Disable-CsUser.md b/skype/skype-ps/skype/Disable-CsUser.md index 75974ece4f..df9affeaa4 100644 --- a/skype/skype-ps/skype/Disable-CsUser.md +++ b/skype/skype-ps/skype/Disable-CsUser.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/disable-csuser +online version: https://learn.microsoft.com/powershell/module/skype/disable-csuser applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Disable-CsUser schema: 2.0.0 @@ -189,4 +189,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.ADConne [Enable-CsUser](Enable-CsUser.md) [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Enable-CsAdDomain.md b/skype/skype-ps/skype/Enable-CsAdDomain.md index 965fcfb26c..c23a8ddc5c 100644 --- a/skype/skype-ps/skype/Enable-CsAdDomain.md +++ b/skype/skype-ps/skype/Enable-CsAdDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-csaddomain +online version: https://learn.microsoft.com/powershell/module/skype/enable-csaddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsAdDomain schema: 2.0.0 @@ -248,4 +248,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Disable-CsAdDomain](Disable-CsAdDomain.md) [Get-CsAdDomain](Get-CsAdDomain.md) - diff --git a/skype/skype-ps/skype/Enable-CsAdForest.md b/skype/skype-ps/skype/Enable-CsAdForest.md index 7d66e4eaf5..0ef2979fe9 100644 --- a/skype/skype-ps/skype/Enable-CsAdForest.md +++ b/skype/skype-ps/skype/Enable-CsAdForest.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-csadforest +online version: https://learn.microsoft.com/powershell/module/skype/enable-csadforest applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsAdForest schema: 2.0.0 @@ -245,4 +245,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Enable-CsComputer.md b/skype/skype-ps/skype/Enable-CsComputer.md index d8ae901f0c..7d94d1d9aa 100644 --- a/skype/skype-ps/skype/Enable-CsComputer.md +++ b/skype/skype-ps/skype/Enable-CsComputer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-cscomputer +online version: https://learn.microsoft.com/powershell/module/skype/enable-cscomputer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsComputer schema: 2.0.0 @@ -178,4 +178,3 @@ Instead, the Enable-CsComputer cmdlet enables instances of the Microsoft.Rtc.Man [Get-CsComputer](Get-CsComputer.md) [Test-CsComputer](Test-CsComputer.md) - diff --git a/skype/skype-ps/skype/Enable-CsHostingProvider.md b/skype/skype-ps/skype/Enable-CsHostingProvider.md index 89c216e599..13691b8524 100644 --- a/skype/skype-ps/skype/Enable-CsHostingProvider.md +++ b/skype/skype-ps/skype/Enable-CsHostingProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-cshostingprovider +online version: https://learn.microsoft.com/powershell/module/skype/enable-cshostingprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsHostingProvider schema: 2.0.0 @@ -200,4 +200,3 @@ Instead, the cmdlet enables instances of the Microsoft.Rtc.Management.WritableCo [Remove-CsHostingProvider](Remove-CsHostingProvider.md) [Set-CsHostingProvider](Set-CsHostingProvider.md) - diff --git a/skype/skype-ps/skype/Enable-CsMeetingRoom.md b/skype/skype-ps/skype/Enable-CsMeetingRoom.md index 7be2e2172f..c823fe60ad 100644 --- a/skype/skype-ps/skype/Enable-CsMeetingRoom.md +++ b/skype/skype-ps/skype/Enable-CsMeetingRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-csmeetingroom -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/enable-csmeetingroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsMeetingRoom schema: 2.0.0 manager: bulenteg @@ -19,7 +19,9 @@ To enable a meeting room you must first create an Active Directory user account Note that, although meeting room objects are based on user accounts, these objects will not show up when you run the Get-CsUser cmdlet. This cmdlet was introduced in Lync Server 2013. -The process for creating and updating meeting rooms differs depending on your deployment of Skype for Business Online and Skype for Business Server. Make sure you are following the guidance here to set up your meeting rooms properly: https://docs.microsoft.com/skypeforbusiness/deploy/deploy-clients/with-office-365 +The process for creating and updating meeting rooms differs depending on your deployment of Skype for Business Server. Make sure you are following the guidance here to set up your meeting rooms properly: [Manage conferencing in Skype for Business Server](https://learn.microsoft.com/skypeforbusiness/manage/conferencing/conferencing). + +**Note**: This cmdlet is not supported for managing Microsoft Teams Rooms. You must use the methods described in the [Microsoft Teams Rooms](/microsoftteams/rooms) documentation to manage Microsoft Teams Rooms. ## SYNTAX @@ -28,7 +30,7 @@ The process for creating and updating meeting rooms differs depending on your de Enable-CsMeetingRoom [-Identity] <UserIdParameter> [-Confirm] [-DomainController <Fqdn>] [-HostingProviderProxyFqdn <Fqdn>] [-OriginatorSid <SecurityIdentifier>] [-PassThru] [-ProxyPool <Fqdn>] [-RegistrarPool <Fqdn>] [-SipAddress <String>] [-SipAddressType <AddressType>] [-SipDomain <Fqdn>] [-WhatIf] - [-AsJob] [<CommonParameters>] + [<CommonParameters>] ``` ## DESCRIPTION @@ -45,7 +47,7 @@ Note that, for Skype for Business Server, there are no cmdlets for creating or r Instead, you use the Enable-CsMeetingRoom cmdlet to enable meeting rooms and the Disable-CsMeetingRoom cmdlet to disable meeting rooms. The resource account must already exist in order for you to enable the meeting room, and disabling a meeting room only removes that room from your collection of meeting rooms; it does not delete the resource mailbox account. -The process for creating and updating meeting rooms differs depending on your deployment of Skype for Business Online and Skype for Business Server. Make sure you are following the guidance here to set up your meeting rooms properly: https://docs.microsoft.com/skypeforbusiness/deploy/deploy-clients/with-office-365 +The process for creating and updating meeting rooms differs depending on your deployment of Skype for Business Server. Make sure you are following the guidance here to set up your meeting rooms properly: [Manage conferencing in Skype for Business Server](https://learn.microsoft.com/skypeforbusiness/manage/conferencing/conferencing). The functions carried out by the Enable-CsMeetingRoom cmdlet are not available in the Skype for Business Server Control Panel. @@ -306,22 +308,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -349,4 +335,3 @@ The cmdlet also accepts pipelined instances of the Active Directory user object. [Move-CsMeetingRoom](Move-CsMeetingRoom.md) [Set-CsMeetingRoom](Set-CsMeetingRoom.md) - diff --git a/skype/skype-ps/skype/Enable-CsOnlineDialInConferencingUser.md b/skype/skype-ps/skype/Enable-CsOnlineDialInConferencingUser.md deleted file mode 100644 index 629150418d..0000000000 --- a/skype/skype-ps/skype/Enable-CsOnlineDialInConferencingUser.md +++ /dev/null @@ -1,354 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-csonlinedialinconferencinguser -applicable: Skype for Business Online -title: Enable-CsOnlineDialInConferencingUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Enable-CsOnlineDialInConferencingUser - -## SYNOPSIS -Use the `Enable-CsOnlineDialInConferencingUser` cmdlet to enable a Skype for Business user to access audio conferencing through Skype for Business Online. - -## SYNTAX - -``` -Enable-CsOnlineDialInConferencingUser [-AllowPstnOnlyMeetings <Boolean>] [-ServiceNumber <String>] - [-SendEmailFromDisplayName <String>] [-ConferenceId <Int32>] [-TenantDomain <String>] - [-TollFreeServiceNumber <String>] [-SendEmailToAddress <String>] [-SendEmailFromAddress <String>] [-SendEmail] - [[-Identity] <UserIdParameter>] [-Tenant <Guid>] [-AllowTollFreeDialIn <Boolean>] [-DomainController <Fqdn>] - [-ReplaceProvider] [-Force] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -The `Enable-CsOnlineDialInConferencingUser` cmdlet allows a Skype for Business user to access audio conferencing through Skype for Business Online. -The cmdlet will validate if the user has the correct license assigned. -If the user already uses Microsoft as the audio conferencing provider, the cmdlet will run without any errors but no changes are made to the user. -The user can be moved from a third-party audio conferencing provider to Microsoft as the PSTN conferencing provider by using the ReplaceProvider parameter. - -If the bridge information (BridgeID or BridgeName) isn't provided and the tenant is just using one audio conferencing bridge, the user is assigned to the bridge. -If the bridge information isn't provided and the tenant uses multiple audio conferencing bridges, the user is then assigned to the default bridge. - -The audio conferencing provider name and domain information is automatically set for the user when they are enabled for audio conferencing. - -> [!NOTE] -> If your conferencing provider is Microsoft, your users' conference IDs are set to Dynamic Only. This cannot be changed. Conference IDs are automatically set only for Skype for Business users enabled for Audio Conferencing. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:> Enable-CsOnlineDialInConferencingUser -Identity "Ken Meyer" -AllowPstnOnlyMeetings $false -ConferenceId 3659305 -ReplaceProvider -ServiceNumber 14255551234 -``` - -This example enables a user named Ken Meyer to use audio conferencing and set up Skype for Business Online dial-in meetings. -When the cmdlet runs, it will replace Ken's existing audio conferencing provider information, set the default phone number to 14255551234 and the ConferenceId for meetings to 3659305. - - -## PARAMETERS - -### -Identity -A user identity can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). -You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPstnOnlyMeetings -If true, non-authenticated users can start meetings. -If false, non-authenticated callers wait in the lobby until an authenticated user joins, thereby starting the meeting. -An authenticated user is a user who joins the meeting using a Skype for Business client, or the organizer that joined the meeting via dial-in conferencing and was authenticated by a PIN number. -The default is false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConferenceId -Specifies the ConferenceId that will be used by the user for dial-in meetings. The cmdlet will fail if: - -The ConferenceId is already being used in the bridge where the user is assigned, or to which the user would be assigned. - -The ConferenceId doesn't meet the ConferenceId format requirements. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: Passcode -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReplaceProvider -If present, the ReplaceProvider switch causes the user's default conferencing provider information to be set to Microsoft. -If omitted, the Active Directory information will not be updated. - -If the ReplaceProvider parameter is not used and the user is enabled for a 3rd party conferencing provider, the cmdlet will fail. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmail -Send an email to the user that contains his Audio Conference information. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromAddress -This property has been deprecated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromDisplayName -This property has been deprecated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailToAddress -You can specify the To Address to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmail. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceNumber -Specifies the default phone number to be used by the user. -The default number is used in meeting invitations. -The service number parameter overwrites the default service number assigned to the bridge for the user. -The service number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308". -You can find your tenant ID by running this command: Get-CsTenant | Select-Object DisplayName, TenantID - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantDomain -Specifies the domain name for the tenant or organization. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TollFreeServiceNumber -Specifies a toll-free phone number to be used by the user. This number is then used in meeting invitations. -The toll-free number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowTollFreeDialIn -If true, specified toll-free number is used in meeting invitations. -If false, specified toll-free number is not allowed to be used in meeting invitations. -The default is true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Disable-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/disable-csonlinedialinconferencinguser?view=skype-ps) - -[Get-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinguser?view=skype-ps) - -[Set-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencinguser?view=skype-ps) diff --git a/skype/skype-ps/skype/Enable-CsOnlineSipDomain.md b/skype/skype-ps/skype/Enable-CsOnlineSipDomain.md deleted file mode 100644 index f95676e842..0000000000 --- a/skype/skype-ps/skype/Enable-CsOnlineSipDomain.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-csonlinesipdomain -applicable: Skype for Business Online -title: Enable-CsOnlineSipDomain -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: rogupta ---- - -# Enable-CsOnlineSipDomain - -## SYNOPSIS -This cmdlet enables provisioning of users in Skype for Business Online for the specified domain. This cmdlet is only necessary to run if you previously disabled a domain using Disable-CsOnlineSipDomain. Enable-CsOnlineSipDomain is used to facilitate consolidation of separate Skype for Business deployments into a single Office 365 tenant. - -## SYNTAX - -``` -Enable-CsOnlineSipDomain -Domain <String> [-Force] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet enables online provisioning of users in the specified SIP domain. In conjunction with Disable-CsOnlineSipDomain, this cmdlet allows organizations to consolidate *multiple on-premises deployments of Skype for Business Server (or Lync Server)* into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, provided the following key requirements are met: - -- There must be at most 1 O365 tenant involved. Consolidation for scenarios with > 1 O365 tenant is not supported. -- At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.) -- If 1 deployment is in hybrid mode, all online SIP domains from any other SfB forests must be disabled before they can be synchronized into the tenant with Azure AD Connect. Users in all SfB forests other than the hybrid forest must remain on-premises. -- Organizations must fully migrate (e.g move all users to the cloud) each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment. - -Before running this cmdlet for any SIP domain in a Skype for Business Server deployment, you must complete migration of any other existing hybrid SfB deployment that is in progress. All users in an existing hybrid deployment must be moved to the cloud, and that existing hybrid deployment must be detached from Office 365, as described in this article: [Disable hybrid to complete migration to the cloud](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid). - -**IMPORTANT** -If you have more than one on-premises deployment of Skype for Business Server, you *must* ensure SharedSipAddressSpace is disabled in all other Skype for Business Server deployments except the deployment containing the SIP domain that is being enabled. - -## EXAMPLES - -### Example 1 -```powershell -Enable-CsOnlineSipDomain -Domain contoso.com -``` - -Enables the domain contoso.com for online provisioning in Skype for Business Online. - -## PARAMETERS - -### -Domain -The SIP domain to be enabled for online provisioning in Skype for Business Online. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses all confirmation prompts that might occur when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### None - -## NOTES - -## RELATED LINKS - -[Disable-CsOnlineSipDomain](Disable-CsOnlineSipDomain.md) - -[Get-CsOnlineSipDomain](Get-CsOnlineSipDomain.md) diff --git a/skype/skype-ps/skype/Enable-CsPublicProvider.md b/skype/skype-ps/skype/Enable-CsPublicProvider.md index f35b92ce9c..e94296ea51 100644 --- a/skype/skype-ps/skype/Enable-CsPublicProvider.md +++ b/skype/skype-ps/skype/Enable-CsPublicProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-cspublicprovider +online version: https://learn.microsoft.com/powershell/module/skype/enable-cspublicprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsPublicProvider schema: 2.0.0 @@ -192,4 +192,3 @@ Instead, the cmdlet enables instances of the Microsoft.Rtc.Management.WritableCo [Remove-CsPublicProvider](Remove-CsPublicProvider.md) [Set-CsPublicProvider](Set-CsPublicProvider.md) - diff --git a/skype/skype-ps/skype/Enable-CsReplica.md b/skype/skype-ps/skype/Enable-CsReplica.md index 1615cea13f..9b9ffe4c9e 100644 --- a/skype/skype-ps/skype/Enable-CsReplica.md +++ b/skype/skype-ps/skype/Enable-CsReplica.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-csreplica +online version: https://learn.microsoft.com/powershell/module/skype/enable-csreplica applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsReplica schema: 2.0.0 @@ -163,4 +163,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Get-CsManagementStoreReplicationStatus](Get-CsManagementStoreReplicationStatus.md) - diff --git a/skype/skype-ps/skype/Enable-CsTopology.md b/skype/skype-ps/skype/Enable-CsTopology.md index 9f8ed1d733..6ea479e1df 100644 --- a/skype/skype-ps/skype/Enable-CsTopology.md +++ b/skype/skype-ps/skype/Enable-CsTopology.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-cstopology +online version: https://learn.microsoft.com/powershell/module/skype/enable-cstopology applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsTopology schema: 2.0.0 @@ -215,4 +215,3 @@ Instead, the Enable-CsTopology cmdlet enables instances of the Microsoft.Rtc.Man [Test-CsSetupPermission](Test-CsSetupPermission.md) [Test-CsTopology](Test-CsTopology.md) - diff --git a/skype/skype-ps/skype/Enable-CsUser.md b/skype/skype-ps/skype/Enable-CsUser.md index e14c11ebd9..edbb4b7306 100644 --- a/skype/skype-ps/skype/Enable-CsUser.md +++ b/skype/skype-ps/skype/Enable-CsUser.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/enable-csuser +online version: https://learn.microsoft.com/powershell/module/skype/enable-csuser applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Enable-CsUser schema: 2.0.0 @@ -83,6 +83,13 @@ To do this, the Get-CsAdUser cmdlet is invoked, along with the Filter parameter. The filter {Enabled -ne $True} returns a collection of all the users who have not been enabled for Skype for Business Server. That collection is then piped to the Enable-CsUser cmdlet, which enables each account, assigning the user to the Registrar pool atl-cs-001.litwareinc.com and auto-generating a SIP address for each user. +### -------------------------- Example 5 -------------------------- +``` +Enable-CsUser -Identity user@litwareinc.com -HostingProvider sipfed.online.lync.com -SipAddressType UserPrincipalName +``` + +Example 5 populates an existing Active Directory user in on-premises Skype for Business server who has been enabled for Skype for Business Online, or Microsoft Teams. The parameter -HostingProvider sipfed.online.lync.com specifies that the user is homed online, not on premises. + ## PARAMETERS @@ -319,4 +326,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.ADConne [Disable-CsUser](Disable-CsUser.md) [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Export-CsArchivingData.md b/skype/skype-ps/skype/Export-CsArchivingData.md index 04827640d4..cd7d61b79f 100644 --- a/skype/skype-ps/skype/Export-CsArchivingData.md +++ b/skype/skype-ps/skype/Export-CsArchivingData.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-csarchivingdata +online version: https://learn.microsoft.com/powershell/module/skype/export-csarchivingdata applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Export-CsArchivingData schema: 2.0.0 @@ -338,6 +338,4 @@ The Export-CsArchivingData cmdlet returns Archiving database records in EML form [Get-CsArchivingConfiguration](Get-CsArchivingConfiguration.md) -[Export archived data in Skype for Business Server](https://docs.microsoft.com/skypeforbusiness/manage/archiving/export-archived-data) - - +[Export archived data in Skype for Business Server](https://learn.microsoft.com/skypeforbusiness/manage/archiving/export-archived-data) diff --git a/skype/skype-ps/skype/Export-CsAutoAttendantHolidays.md b/skype/skype-ps/skype/Export-CsAutoAttendantHolidays.md deleted file mode 100644 index 5d968d458b..0000000000 --- a/skype/skype-ps/skype/Export-CsAutoAttendantHolidays.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-csautoattendantholidays -applicable: Skype for Business Online -title: Export-CsAutoAttendantHolidays -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Export-CsAutoAttendantHolidays - -## SYNOPSIS -Use Export-CsAutoAttendantHolidays cmdlet to export holiday schedules of an existing Auto Attendant (AA). The data is exported as a byte array from the cmdlet, which can be dumped to disk as a CSV file and can later be imported using the Import-CsAutoAttendantHolidays cmdlet. - -## SYNTAX - -``` -Export-CsAutoAttendantHolidays -Identity <String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-CsAutoAttendantHolidays cmdlet and the Import-CsAutoAttendantHolidays cmdlet enable you to export holiday schedules in your auto attendant and then later import that information. This can be extremely useful in a situation where you need to configure same holiday sets in multiple tenants. - -The Export-CsAutoAttendantHolidays cmdlet returns the holiday schedule information in serialized form (as a byte array). The caller can then write the bytes to the disk to obtain a CSV file. Similarly, the Import-CsAutoAttendantHolidays cmdlet accepts the holiday schedule information as a byte array, which can be read from the aforementioned CSV file. The first line of the CSV file is considered a header record and is always ignored. - -**NOTE** -- Each line in the CSV file used by Export-CsAutoAttendantHolidays and Import-CsAutoAttendantHolidays cmdlet should be of the following format: - - `HolidayName,StartDateTime1,EndDateTime1,StartDateTime2,EndDateTime2,...,StartDateTime10,EndDateTime10` - - where - - HolidayName is the name of the holiday to be imported. - - StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet. - - EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date. -- The first line of the CSV file is considered a header record and is always ignored by Import-CsAutoAttendantHolidays cmdlet. -- If the destination auto attendant for the import already contains a call flow or schedule by the same name as one of the holidays being imported, the corresponding CSV record is skipped. -- For holidays that are successfully imported, a default call flow is created which is configured without any greeting and simply disconnects the call on being executed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$bytes = Export-CsAutoAttendantHolidays -Identity 6abea1cd-904b-520b-be96-1092cc096432 -[System.IO.File]::WriteAllBytes("C:\Exports\Holidays.csv", $bytes) -``` - -In this example, the Export-CsAutoAttendantHolidays cmdlet is used to export holiday schedules of an auto attendant with Identity of 6abea1cd-904b-520b-be96-1092cc096432. The exported bytes are then written to a file with the path "C:\Exports\Holidays.csv". - -## PARAMETERS - -### -Identity -The identity for the AA whose holiday schedules are to be exported. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### System.String -The Export-CsAutoAttendantHolidays cmdlet accepts a string as the Identity parameter. - -## OUTPUTS - -### System.Byte[] - - -## NOTES - - -## RELATED LINKS - -[Import-CsAutoAttendantHolidays](Import-CsAutoAttendantHolidays.md) - -[Get-CsAutoAttendantHolidays](Get-CsAutoAttendantHolidays.md) - diff --git a/skype/skype-ps/skype/Export-CsConfiguration.md b/skype/skype-ps/skype/Export-CsConfiguration.md index 5f72adc319..07b09a1158 100644 --- a/skype/skype-ps/skype/Export-CsConfiguration.md +++ b/skype/skype-ps/skype/Export-CsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-csconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/export-csconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Export-CsConfiguration schema: 2.0.0 @@ -154,4 +154,3 @@ If called along with the AsBytes parameter, the Export-CsConfiguration cmdlet re ## RELATED LINKS [Import-CsConfiguration](Import-CsConfiguration.md) - diff --git a/skype/skype-ps/skype/Export-CsLisConfiguration.md b/skype/skype-ps/skype/Export-CsLisConfiguration.md index 2ff3b7ac9c..86b50a823e 100644 --- a/skype/skype-ps/skype/Export-CsLisConfiguration.md +++ b/skype/skype-ps/skype/Export-CsLisConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-cslisconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/export-cslisconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Export-CsLisConfiguration schema: 2.0.0 @@ -16,7 +16,6 @@ ms.reviewer: Exports an Enterprise Voice Enhanced 9-1-1 (E9-1-1) configuration to a file in compressed format for backup purposes. This cmdlet was introduced in Lync Server 2010. - ## SYNTAX ### FileName @@ -44,7 +43,6 @@ To return a list of all the role-based access control (RBAC) roles this cmdlet h `Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Export-CsLisConfiguration"}` - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -65,27 +63,20 @@ In this example, the LIS configuration is stored as an array of bytes in a varia ``` $lisconfig = Export-CsLisConfiguration -AsBytes -$lisconfig | Set-Content -Path C:\E911Config.bak -Encoding byte +[System.IO.File]::WriteAllBytes('C:\E911Config.bak', $lisconfig) -Get-Content -ReadCount 0 -Encoding byte -Path C:\E911Config.bak | Import-CsLisConfiguration +[System.IO.File]::ReadAllBytes('C:\E911Config.bak') | Import-CsLisConfiguration ``` Example 3 is a more complete version of Example 2. The first line is the same, we call the Export-CsLisConfiguration cmdlet with the AsBytes parameter to store the LIS configuration as an array of bytes in the variable $lisconfig. The rest of this example shows how to save that configuration to a file and then import it back into the location configuration database. -In line 2 we pipe the contents of $lisconfig, which is the byte array representing the LIS configuration, to the Windows PowerShell Set-Content cmdlet. -We assign values to two parameters of the Set-Content cmdlet: Path and Encoding. -We assign the full path and file name of the file to which we want to save the configuration to the Path parameter. -We use the Encoding parameter with a value of byte to ensure the configuration is stored as an array of bytes. +In line 2 we pipe the contents of $lisconfig, which is the byte array representing the LIS configuration, to the full path and file name of the file to which we want to save the configuration. Finally, in line 3 we import the configuration back into the location configuration database. -First we call the Get-Content cmdlet to retrieve the contents from the file. -We pass a value of 0 to the ReadCount property, which tells the Get-Content cmdlet to read all the contents of the file at once rather than one line at a time. -We again use the Encoding parameter with a value of byte to specify what type of data we're reading from the file. -Finally we pass the file name to the Path parameter. -The contents of the file that we read with the Get-Content cmdlet are piped to the Import-CsLisConfiguration cmdlet, which imports the saved configuration into the location database. - +First we retrieve the contents from the file. +The contents of the file are then piped to the Import-CsLisConfiguration cmdlet, which imports the saved configuration into the location database. ## PARAMETERS @@ -134,16 +125,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ### None - ## OUTPUTS ### Byte[] Returns a byte array when the AsBytes parameter is used. - ## NOTES - ## RELATED LINKS [Import-CsLisConfiguration](Import-CsLisConfiguration.md) @@ -155,4 +143,3 @@ Returns a byte array when the AsBytes parameter is used. [Unpublish-CsLisConfiguration](Unpublish-CsLisConfiguration.md) [Test-CsLisConfiguration](Test-CsLisConfiguration.md) - diff --git a/skype/skype-ps/skype/Export-CsOrganizationalAutoAttendantHolidays.md b/skype/skype-ps/skype/Export-CsOrganizationalAutoAttendantHolidays.md deleted file mode 100644 index bd6197a7db..0000000000 --- a/skype/skype-ps/skype/Export-CsOrganizationalAutoAttendantHolidays.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-csorganizationalautoattendantholidays -applicable: Skype for Business Online -title: Export-CsOrganizationalAutoAttendantHolidays -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Export-CsOrganizationalAutoAttendantHolidays - -## SYNOPSIS -Use Export-CsOrganizationalAutoAttendantHolidays cmdlet to export holiday schedules of an existing Auto Attendant (AA). The data is exported as a byte array from the cmdlet, which can be dumped to disk as a CSV file and can later be imported using the Import-CsOrganizationalAutoAttendantHolidays cmdlet. - -## SYNTAX - -``` -Export-CsOrganizationalAutoAttendantHolidays [-PrimaryUri] <Uri> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-CsOrganizationalAutoAttendantHolidays cmdlet and the Import-CsOrganizationalAutoAttendantHolidays cmdlet enable you to export holiday schedules in your auto attendant and then later import that information. This can be extremely useful in a situation where you need to configure same holiday sets in multiple auto attendants. - -The Export-CsOrganizationalAutoAttendantHolidays cmdlet returns the holiday schedule information in serialized form (as a byte array). The caller can then write the bytes to the disk to obtain a CSV file. Similarly, the Import-CsOrganizationalAutoAttendantHolidays cmdlet accepts the holiday schedule information as a byte array, which can be read from the aforementioned CSV file. The first line of the CSV file is considered a header record and is always ignored. - -**NOTE** -- Each line in the CSV file used by Export-CsOrganizationalAutoAttendantHolidays and Import-CsOrganizationalAutoAttendantHolidays cmdlet should be of the following format: - - `HolidayName,StartDateTime1,EndDateTime1,StartDateTime2,EndDateTime2,...,StartDateTime10,EndDateTime10` - - where - - HolidayName is the name of the holiday to be imported. - - StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet. - - EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date. -- The first line of the CSV file is considered a header record and is always ignored by Import-CsOrganizationalAutoAttendantHolidays cmdlet. -- If the destination auto attendant for the import already contains a call flow or schedule by the same name as one of the holidays being imported, the corresponding CSV record is skipped. -- For holidays that are successfully imported, a default call flow is created which is configured without any greeting and simply disconnects the call on being executed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$bytes = Export-CsOrganizationalAutoAttendantHolidays -PrimaryUri sip:mainoaa@contoso.com -[System.IO.File]::WriteAllBytes("C:\Exports\Holidays.csv", $bytes) -``` - -In this example, the Export-CsOrganizationalAutoAttendantHolidays cmdlet is used to export holiday schedules of an auto attendant with Primary URI of sip:mainoaa@contoso.com. The exported bytes are then written to a file with the path "C:\Exports\Holidays.csv". - -## PARAMETERS - -### -PrimaryUri -The Primary URI represents the SIP address of the auto attendant whose holiday schedules are to be exported. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### String -The String is used as the PrimaryUri input. - - -## OUTPUTS - -### System.Byte[] - - -## NOTES - - -## RELATED LINKS - -[Import-CsOrganizationalAutoAttendantHolidays](Import-CsOrganizationalAutoAttendantHolidays.md) - -[Get-CsOrganizationalAutoAttendantHolidays](Get-CsOrganizationalAutoAttendantHolidays.md) - diff --git a/skype/skype-ps/skype/Export-CsPersistentChatData.md b/skype/skype-ps/skype/Export-CsPersistentChatData.md index 7e745771f8..c748866515 100644 --- a/skype/skype-ps/skype/Export-CsPersistentChatData.md +++ b/skype/skype-ps/skype/Export-CsPersistentChatData.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-cspersistentchatdata -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/export-cspersistentchatdata +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Export-CsPersistentChatData schema: 2.0.0 manager: rogupta @@ -251,4 +251,3 @@ The Export-CsPersistentChatData cmdlet creates .ZIP files. ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Export-CsRgsConfiguration.md b/skype/skype-ps/skype/Export-CsRgsConfiguration.md index 82abdad209..eb820753a3 100644 --- a/skype/skype-ps/skype/Export-CsRgsConfiguration.md +++ b/skype/skype-ps/skype/Export-CsRgsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-csrgsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/export-csrgsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Export-CsRgsConfiguration schema: 2.0.0 @@ -163,4 +163,3 @@ The Export-CsRgsConfiguration cmdlet creates compressed files with the .ZIP file ## RELATED LINKS [Import-CsRgsConfiguration](Import-CsRgsConfiguration.md) - diff --git a/skype/skype-ps/skype/Export-CsUserData.md b/skype/skype-ps/skype/Export-CsUserData.md index 99ed482885..0a7cb7f3d3 100644 --- a/skype/skype-ps/skype/Export-CsUserData.md +++ b/skype/skype-ps/skype/Export-CsUserData.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/export-csuserdata +online version: https://learn.microsoft.com/powershell/module/skype/export-csuserdata applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Export-CsUserData schema: 2.0.0 diff --git a/skype/skype-ps/skype/Find-CsGroup.md b/skype/skype-ps/skype/Find-CsGroup.md deleted file mode 100644 index 50c21725c7..0000000000 --- a/skype/skype-ps/skype/Find-CsGroup.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/find-csgroup -applicable: Skype for Business Online -title: Find-CsGroup -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Find-CsGroup - -## SYNOPSIS -Use the Find-CsGroup cmdlet to search groups. - -## SYNTAX - -``` -Find-CsGroup [-Tenant <Guid>] -SearchQuery <String> [-MaxResults <UInt32>] [-ExactMatchOnly <Boolean>] -[-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The Find-CsGroup cmdlet lets you search groups in the Azure Address Book Service (AABS). - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Find-CsGroup -SearchQuery "Contoso Group" -MaxResults 5 -``` - -This example finds and displays up to five groups that match the "Contoso Group" search query. - -### -------------------------- Example 2 -------------------------- -``` -Find-CsGroup -SearchQuery "ed0d1180-169e-47c7-b718-bf9e60543914" -ExactMatchOnly $true -``` - -This example finds and displays only those groups that are an exact match to the search query. - -## PARAMETERS - -### -SearchQuery -The SearchQuery parameter defines a search query to search the display name or the sip address or the GUID of groups. This parameter accepts partial search query. The search is not case sensitive. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExactMatchOnly -The ExactMatchOnly parameter instructs the cmdlet to return exact matches only. The default value is false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxResults -The MaxResults parameter identifies the maximum number of results to return. If this parameter is not provided, the default is value is 10. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Group.Models.GroupModel -The Find-CsGroup cmdlet returns a list of Microsoft.Rtc.Management.Hosted.Group.Models.GroupModel. Microsoft.Rtc.Management.Hosted.Group.Models.GroupModel contains Id and DisplayName. - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Find-CsOnlineApplicationInstance.md b/skype/skype-ps/skype/Find-CsOnlineApplicationInstance.md deleted file mode 100644 index 60d2854232..0000000000 --- a/skype/skype-ps/skype/Find-CsOnlineApplicationInstance.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/find-csonlineapplicationinstance -applicable: Skype for Business Online -title: Find-CsOnlineApplicationInstance -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Find-CsOnlineApplicationInstance - -## SYNOPSIS -Use the Find-CsOnlineApplicationInstance cmdlet to find application instances that match your search criteria. - -## SYNTAX - -``` -Find-CsOnlineApplicationInstance -SearchQuery <String> [-MaxResults <UInt32?>] [-ExactMatchOnly] [-AssociatedOnly] [-UnAssociatedOnly] [-Tenant <Guid>] [-CommonParameters] -``` - -## DESCRIPTION -Use the Find-CsOnlineApplicationInstance cmdlet to find application instances that match your search criteria. - -If MaxResults is not specified, the number of returned applications instances is limited to 10 application instances. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Find-CsOnlineApplicationInstance -SearchQuery "Test" -``` - -This example returns up to 10 application instances whose name starts with "Test". - -### -------------------------- Example 2 -------------------------- -```powershell -Find-CsOnlineApplicationInstance -SearchQuery "Test" -MaxResults 5 -``` - -This example returns up to 5 application instances whose name starts with "Test". - -### -------------------------- Example 3 -------------------------- -```powershell -Find-CsOnlineApplicationInstance -SearchQuery "Test Auto Attendant" -ExactMatchOnly -``` - -This example returns up to 10 application instances whose name is "Test Auto Attendant". - -### -------------------------- Example 4 -------------------------- -```powershell -Find-CsOnlineApplicationInstance -SearchQuery "Test Auto Attendant" -AssociatedOnly -``` - -This example returns up to 10 application instances whose name is "Test Auto Attendant", and who are associated with an application configuration, like auto attendant or call queue. - -## PARAMETERS - -### -SearchQuery -The SearchQuery parameter defines a query for application instances by display name, telephone number, or GUID of the application instance. This parameter accepts partial queries for display names and telephone numbers. The search is not case sensitive. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExactMatchOnly -The ExactMatchOnly parameter instructs the cmdlet to return exact matches only. The default value is false. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssociatedOnly -The AssociatedOnly parameter instructs the cmdlet to return only application instances that are associated to a configuration. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnAssociatedOnly -The UnAssociatedOnly parameter instructs the cmdlet to return only application instances that are not associated to any configuration. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxResults -The MaxResults parameter identifies the maximum number of results to return. If this parameter is not provided, the default is value is 10. Max allowed value is 20. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.FindApplicationInstanceResult - - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsAVEdgeConfiguration.md b/skype/skype-ps/skype/Get-CsAVEdgeConfiguration.md index 1ecfd75aa2..25ec18533d 100644 --- a/skype/skype-ps/skype/Get-CsAVEdgeConfiguration.md +++ b/skype/skype-ps/skype/Get-CsAVEdgeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csavedgeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csavedgeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAVEdgeConfiguration schema: 2.0.0 @@ -176,4 +176,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsAVEdgeConfiguration](Remove-CsAVEdgeConfiguration.md) [Set-CsAVEdgeConfiguration](Set-CsAVEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsAccessEdgeConfiguration.md b/skype/skype-ps/skype/Get-CsAccessEdgeConfiguration.md index 54a4b65035..11284940f2 100644 --- a/skype/skype-ps/skype/Get-CsAccessEdgeConfiguration.md +++ b/skype/skype-ps/skype/Get-CsAccessEdgeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaccessedgeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csaccessedgeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAccessEdgeConfiguration schema: 2.0.0 @@ -152,4 +152,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsAdContact.md b/skype/skype-ps/skype/Get-CsAdContact.md index dcc3051e70..34b07fefb1 100644 --- a/skype/skype-ps/skype/Get-CsAdContact.md +++ b/skype/skype-ps/skype/Get-CsAdContact.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csadcontact +online version: https://learn.microsoft.com/powershell/module/skype/get-csadcontact applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdContact schema: 2.0.0 @@ -252,4 +252,3 @@ The Get-CsAdContact cmdlet accepts a pipelined string value representing the Ide [Get-CsAdUser](Get-CsAdUser.md) [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Get-CsAdDomain.md b/skype/skype-ps/skype/Get-CsAdDomain.md index e67b8fe876..5bccf6a4ec 100644 --- a/skype/skype-ps/skype/Get-CsAdDomain.md +++ b/skype/skype-ps/skype/Get-CsAdDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaddomain +online version: https://learn.microsoft.com/powershell/module/skype/get-csaddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdDomain schema: 2.0.0 @@ -184,4 +184,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Disable-CsAdDomain](Disable-CsAdDomain.md) [Enable-CsAdDomain](Enable-CsAdDomain.md) - diff --git a/skype/skype-ps/skype/Get-CsAdForest.md b/skype/skype-ps/skype/Get-CsAdForest.md index 87b73cfa70..7c4a94daab 100644 --- a/skype/skype-ps/skype/Get-CsAdForest.md +++ b/skype/skype-ps/skype/Get-CsAdForest.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csadforest +online version: https://learn.microsoft.com/powershell/module/skype/get-csadforest applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdForest schema: 2.0.0 @@ -169,4 +169,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsAdPrincipal.md b/skype/skype-ps/skype/Get-CsAdPrincipal.md index 962c5dbe46..408fcea9c1 100644 --- a/skype/skype-ps/skype/Get-CsAdPrincipal.md +++ b/skype/skype-ps/skype/Get-CsAdPrincipal.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csadprincipal +online version: https://learn.microsoft.com/powershell/module/skype/get-csadprincipal applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdPrincipal schema: 2.0.0 @@ -258,4 +258,3 @@ For example, this syntax returns Active Directory principal information for the [New-CsPersistentChatCategory](New-CsPersistentChatCategory.md) [Set-CsPersistentChatCategory](Set-CsPersistentChatCategory.md) - diff --git a/skype/skype-ps/skype/Get-CsAdServerSchema.md b/skype/skype-ps/skype/Get-CsAdServerSchema.md index 861c3f5e15..68b5c4a03e 100644 --- a/skype/skype-ps/skype/Get-CsAdServerSchema.md +++ b/skype/skype-ps/skype/Get-CsAdServerSchema.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csadserverschema +online version: https://learn.microsoft.com/powershell/module/skype/get-csadserverschema applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdServerSchema schema: 2.0.0 @@ -94,4 +94,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Install-CsAdServerSchema](Install-CsAdServerSchema.md) - diff --git a/skype/skype-ps/skype/Get-CsAdUser.md b/skype/skype-ps/skype/Get-CsAdUser.md index 7b8ed0cd56..64a6b36104 100644 --- a/skype/skype-ps/skype/Get-CsAdUser.md +++ b/skype/skype-ps/skype/Get-CsAdUser.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaduser +online version: https://learn.microsoft.com/powershell/module/skype/get-csaduser applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdUser schema: 2.0.0 @@ -279,4 +279,3 @@ The Get-CsAdUser cmdlet accepts a pipelined string value representing the Identi ## RELATED LINKS [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Get-CsAdditionalInternalDomain.md b/skype/skype-ps/skype/Get-CsAdditionalInternalDomain.md index fe7b6b307e..0e359015b0 100644 --- a/skype/skype-ps/skype/Get-CsAdditionalInternalDomain.md +++ b/skype/skype-ps/skype/Get-CsAdditionalInternalDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csadditionalinternaldomain +online version: https://learn.microsoft.com/powershell/module/skype/get-csadditionalinternaldomain applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdditionalInternalDomain schema: 2.0.0 @@ -105,4 +105,3 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsAddressBookConfiguration.md b/skype/skype-ps/skype/Get-CsAddressBookConfiguration.md index f7fcb06325..7515253dc6 100644 --- a/skype/skype-ps/skype/Get-CsAddressBookConfiguration.md +++ b/skype/skype-ps/skype/Get-CsAddressBookConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaddressbookconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csaddressbookconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAddressBookConfiguration schema: 2.0.0 @@ -167,4 +167,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsAddressBookConfiguration](Remove-CsAddressBookConfiguration.md) [Set-CsAddressBookConfiguration](Set-CsAddressBookConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsAddressBookNormalizationConfiguration.md b/skype/skype-ps/skype/Get-CsAddressBookNormalizationConfiguration.md index b46e7a945b..17e9105af0 100644 --- a/skype/skype-ps/skype/Get-CsAddressBookNormalizationConfiguration.md +++ b/skype/skype-ps/skype/Get-CsAddressBookNormalizationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaddressbooknormalizationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csaddressbooknormalizationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAddressBookNormalizationConfiguration schema: 2.0.0 @@ -151,4 +151,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsAddressBookNormalizationConfiguration](Set-CsAddressBookNormalizationConfiguration.md) [Import-CsCompanyPhoneNormalizationRules](Import-CsCompanyPhoneNormalizationRules.md) - diff --git a/skype/skype-ps/skype/Get-CsAddressBookNormalizationRule.md b/skype/skype-ps/skype/Get-CsAddressBookNormalizationRule.md index 395ed1a10c..d12fa7f30e 100644 --- a/skype/skype-ps/skype/Get-CsAddressBookNormalizationRule.md +++ b/skype/skype-ps/skype/Get-CsAddressBookNormalizationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaddressbooknormalizationrule +online version: https://learn.microsoft.com/powershell/module/skype/get-csaddressbooknormalizationrule applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAddressBookNormalizationRule schema: 2.0.0 @@ -153,4 +153,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsAddressBookNormalizationRule](Remove-CsAddressBookNormalizationRule.md) [Set-CsAddressBookNormalizationRule](Set-CsAddressBookNormalizationRule.md) - diff --git a/skype/skype-ps/skype/Get-CsAdminRole.md b/skype/skype-ps/skype/Get-CsAdminRole.md index bb2e6fcc5a..45ac191dd0 100644 --- a/skype/skype-ps/skype/Get-CsAdminRole.md +++ b/skype/skype-ps/skype/Get-CsAdminRole.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csadminrole +online version: https://learn.microsoft.com/powershell/module/skype/get-csadminrole applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdminRole schema: 2.0.0 @@ -239,4 +239,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsAdminRoleAssignment.md b/skype/skype-ps/skype/Get-CsAdminRoleAssignment.md index 8614d6ae1c..553b2ad153 100644 --- a/skype/skype-ps/skype/Get-CsAdminRoleAssignment.md +++ b/skype/skype-ps/skype/Get-CsAdminRoleAssignment.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csadminroleassignment +online version: https://learn.microsoft.com/powershell/module/skype/get-csadminroleassignment applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAdminRoleAssignment schema: 2.0.0 @@ -128,4 +128,3 @@ The Get-CsAdminRoleAssignment cmdlet returns string values representing the RBAC ## RELATED LINKS [Get-CsAdminRole](Get-CsAdminRole.md) - diff --git a/skype/skype-ps/skype/Get-CsAllowedDomain.md b/skype/skype-ps/skype/Get-CsAllowedDomain.md index e97737d1b9..d929aab5aa 100644 --- a/skype/skype-ps/skype/Get-CsAllowedDomain.md +++ b/skype/skype-ps/skype/Get-CsAllowedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csalloweddomain +online version: https://learn.microsoft.com/powershell/module/skype/get-csalloweddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAllowedDomain schema: 2.0.0 @@ -180,4 +180,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) [Set-CsAllowedDomain](Set-CsAllowedDomain.md) - diff --git a/skype/skype-ps/skype/Get-CsAnalogDevice.md b/skype/skype-ps/skype/Get-CsAnalogDevice.md index 7f93e05fb8..395151838c 100644 --- a/skype/skype-ps/skype/Get-CsAnalogDevice.md +++ b/skype/skype-ps/skype/Get-CsAnalogDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csanalogdevice +online version: https://learn.microsoft.com/powershell/module/skype/get-csanalogdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAnalogDevice schema: 2.0.0 @@ -295,4 +295,3 @@ The Get-CsAnalogDevice cmdlet accepts a pipelined string value that represents t [Remove-CsAnalogDevice](Remove-CsAnalogDevice.md) [Set-CsAnalogDevice](Set-CsAnalogDevice.md) - diff --git a/skype/skype-ps/skype/Get-CsAnnouncement.md b/skype/skype-ps/skype/Get-CsAnnouncement.md index 0e3066e228..a6d35b457e 100644 --- a/skype/skype-ps/skype/Get-CsAnnouncement.md +++ b/skype/skype-ps/skype/Get-CsAnnouncement.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csannouncement +online version: https://learn.microsoft.com/powershell/module/skype/get-csannouncement applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAnnouncement schema: 2.0.0 @@ -194,4 +194,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsAnnouncement](Set-CsAnnouncement.md) [Import-CsAnnouncementFile](Import-CsAnnouncementFile.md) - diff --git a/skype/skype-ps/skype/Get-CsApplicationEndpoint.md b/skype/skype-ps/skype/Get-CsApplicationEndpoint.md index 0f38044e06..abcb4005cc 100644 --- a/skype/skype-ps/skype/Get-CsApplicationEndpoint.md +++ b/skype/skype-ps/skype/Get-CsApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/get-csapplicationendpoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsApplicationEndpoint schema: 2.0.0 @@ -226,4 +226,3 @@ Accepts a pipelined string value representing the Identity of the application en ## RELATED LINKS [Move-CsApplicationEndpoint](Move-CsApplicationEndpoint.md) - diff --git a/skype/skype-ps/skype/Get-CsArchivingConfiguration.md b/skype/skype-ps/skype/Get-CsArchivingConfiguration.md index 7a13236ddc..55d5040275 100644 --- a/skype/skype-ps/skype/Get-CsArchivingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsArchivingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csarchivingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csarchivingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsArchivingConfiguration schema: 2.0.0 @@ -176,4 +176,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsArchivingConfiguration](Set-CsArchivingConfiguration.md) [Set-CsArchivingServer](Set-CsArchivingServer.md) - diff --git a/skype/skype-ps/skype/Get-CsArchivingPolicy.md b/skype/skype-ps/skype/Get-CsArchivingPolicy.md index f2ab3b19c5..f7195895dc 100644 --- a/skype/skype-ps/skype/Get-CsArchivingPolicy.md +++ b/skype/skype-ps/skype/Get-CsArchivingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csarchivingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csarchivingpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsArchivingPolicy schema: 2.0.0 @@ -208,4 +208,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsArchivingPolicy](Remove-CsArchivingPolicy.md) [Set-CsArchivingPolicy](Set-CsArchivingPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsAudioConferencingProvider.md b/skype/skype-ps/skype/Get-CsAudioConferencingProvider.md index 41954c0e7b..b3dc99ff07 100644 --- a/skype/skype-ps/skype/Get-CsAudioConferencingProvider.md +++ b/skype/skype-ps/skype/Get-CsAudioConferencingProvider.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaudioconferencingprovider +online version: https://learn.microsoft.com/powershell/module/skype/get-csaudioconferencingprovider applicable: Skype for Business Online title: Get-CsAudioConferencingProvider schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsAudioConferencingProvider @@ -139,4 +139,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsAudioTestServiceApplication.md b/skype/skype-ps/skype/Get-CsAudioTestServiceApplication.md index 182a0b8ae6..4829ab115f 100644 --- a/skype/skype-ps/skype/Get-CsAudioTestServiceApplication.md +++ b/skype/skype-ps/skype/Get-CsAudioTestServiceApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csaudiotestserviceapplication +online version: https://learn.microsoft.com/powershell/module/skype/get-csaudiotestserviceapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAudioTestServiceApplication schema: 2.0.0 @@ -205,4 +205,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsAudioTestServiceApplication](Set-CsAudioTestServiceApplication.md) - diff --git a/skype/skype-ps/skype/Get-CsAuthConfig.md b/skype/skype-ps/skype/Get-CsAuthConfig.md index eea936f104..56541b3cdc 100644 --- a/skype/skype-ps/skype/Get-CsAuthConfig.md +++ b/skype/skype-ps/skype/Get-CsAuthConfig.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csauthconfig -applicable: Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csauthconfig +applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAuthConfig schema: 2.0.0 manager: rogupta diff --git a/skype/skype-ps/skype/Get-CsAutoAttendant.md b/skype/skype-ps/skype/Get-CsAutoAttendant.md deleted file mode 100644 index 899ad0feb5..0000000000 --- a/skype/skype-ps/skype/Get-CsAutoAttendant.md +++ /dev/null @@ -1,248 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csautoattendant -applicable: Skype for Business Online -title: Get-CsAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsAutoAttendant - -## SYNOPSIS -Use the Get-CsAutoAttendant cmdlet to get information about your Auto Attendants (AA). - -## SYNTAX - -``` -Get-CsAutoAttendant [-Identity <String>] [-First <UInt32>] [-Skip <UInt32>] [-NameFilter <String>] [-SortBy <String>] [-Descending] [-IncludeStatus] [-ExcludeContent] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsAutoAttendant cmdlet returns information about the AAs in your organization. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Get-CsAutoAttendant -``` - -This example gets all AAs in the organization. - -### -------------------------- Example 2 -------------------------- -```powershell -Get-CsAutoAttendant -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" - -# Id : f7a821dc-2d69-5ae8-8525-bcb4a4556093 -# TenantId : 977c9d5b-2dae-5d82-aada-628bc1c14213 -# Name : Main Auto Attendant -# LanguageId : en-US -# VoiceId : Female -# DefaultCallFlow : Default Call Flow -# Operator : -# TimeZoneId : Pacific Standard Time -# VoiceResponseEnabled : False -# CallFlows : -# Schedules : -# CallHandlingAssociations : -# Status : -# DialByNameResourceId : -# DirectoryLookupScope : -# ApplicationInstances : {fa2f17ec-ebd5-43f8-81ac-959c245620fa, 56421bbe-5649-4208-a60c-24dbeded6f18, c7af9c3c-ae40-455d-a37c-aeec771e623d} -``` - -This example gets the AA that has the identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. - -### -------------------------- Example 3 -------------------------- -``` -Get-CsAutoAttendant -First 10 -``` - -This example gets the first ten auto attendants configured for use in the organization. - -### -------------------------- Example 4 -------------------------- -``` -Get-CsAutoAttendant -Skip 5 -First 10 -``` - -This example skips initial 5 auto attendants and gets the next 10 AAs configured in the organization. - - -## PARAMETERS - -### -Identity -The identity for the AA to be retrieved. If this parameter is not specified, then all created AAs in the organization are returned. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -First -The First parameter indicates the maximum number of auto attendants to retrieve as the result. It is intended to be used for pagination purposes. - -```yaml -Type: System.UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Skip -The Skip parameter indicates the number of initial auto attendants to skip in the result. It is intended to be used for pagination purposes. - -```yaml -Type: System.UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NameFilter -If specified, only auto attendants whose names match that value would be returned. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortBy -If specified, the retrieved auto attendants would be sorted by the specified property. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Descending -If specified, the retrieved auto attendants would be sorted in descending order. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeStatus -If specified, the status records for each auto attendant in the result set are also retrieved. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludeContent -If specified, only auto attendants' names, identities and associated application instances will be retrieved. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### System.String -The Get-CsAutoAttendant cmdlet accepts a string as the Identity parameter. - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.AutoAttendant - - -## NOTES - - -## RELATED LINKS - -[Get-CsAutoAttendantStatus](Get-CsAutoAttendantStatus.md) - -[New-CsAutoAttendant](New-CsAutoAttendant.md) - -[Remove-CsAutoAttendant](Remove-CsAutoAttendant.md) - -[Set-CsAutoAttendant](Set-CsAutoAttendant.md) - -[Update-CsAutoAttendant](Update-CsAutoAttendant.md) diff --git a/skype/skype-ps/skype/Get-CsAutoAttendantHolidays.md b/skype/skype-ps/skype/Get-CsAutoAttendantHolidays.md deleted file mode 100644 index 26e21eb323..0000000000 --- a/skype/skype-ps/skype/Get-CsAutoAttendantHolidays.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csautoattendantholidays -applicable: Skype for Business Online -title: Get-CsAutoAttendantHolidays -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsAutoAttendantHolidays - -## SYNOPSIS -Use Get-CsAutoAttendantHolidays cmdlet to get the holiday information for an existing Auto Attendant (AA). - -## SYNTAX - -``` -Get-CsAutoAttendantHolidays -Identity <String> [-Years <List>] [-Names <List>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsAutoAttendantHolidays provides a convenient way to visualize the information of all the holidays contained within an auto attendant. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -``` - -In this example, the Get-CsAutoAttendantHolidays cmdlet is used to get all holidays in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -Years @(2017) -``` - -In this example, the Get-CsAutoAttendantHolidays cmdlet is used to get all holidays in year 2017 in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. - -### -------------------------- Example 3 -------------------------- -``` -Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -Years @(2017) -Name @("Christmas") -``` - -In this example, the Get-CsAutoAttendantHolidays cmdlet is used to get holiday named Christmas in the year 2017 in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. - -### -------------------------- Example 4 -------------------------- -``` -Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" | Format-Table -Wrap -AutoSize -``` - -In this example, the Get-CsAutoAttendantHolidays cmdlet is used to retrieve all holidays in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093 and the result is formatted as a table. - - -## PARAMETERS - -### -Identity -Represents the identifier for the auto attendant whose holidays are to be retrieved. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Years -The Years parameter represents the years for the holidays to be retrieved. If this parameter is not specified, then holidays for all years in the AA are returned. - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Names -The Names parameter represents the names for the holidays to be retrieved. If this parameter is not specified, then all holidays in the AA are returned. - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### System.String -The Get-CsAutoAttendantHolidays cmdlet accepts a string as the Identity parameter. - - -## OUTPUTS - -### Microsoft.Rtc.Management.OAA.Models.HolidayVisRecord - - -## NOTES - - -## RELATED LINKS - -[Import-CsAutoAttendantHolidays](Import-CsAutoAttendantHolidays.md) - -[Export-CsAutoAttendantHolidays](Export-CsAutoAttendantHolidays.md) - diff --git a/skype/skype-ps/skype/Get-CsAutodiscoverConfiguration.md b/skype/skype-ps/skype/Get-CsAutodiscoverConfiguration.md index 9f311b4e3e..9b8fbb11b7 100644 --- a/skype/skype-ps/skype/Get-CsAutodiscoverConfiguration.md +++ b/skype/skype-ps/skype/Get-CsAutodiscoverConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csautodiscoverconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csautodiscoverconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsAutodiscoverConfiguration schema: 2.0.0 manager: rogupta @@ -169,4 +169,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsBackupServiceConfiguration.md b/skype/skype-ps/skype/Get-CsBackupServiceConfiguration.md index 095974a039..0807cde4a1 100644 --- a/skype/skype-ps/skype/Get-CsBackupServiceConfiguration.md +++ b/skype/skype-ps/skype/Get-CsBackupServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csbackupserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csbackupserviceconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsBackupServiceConfiguration schema: 2.0.0 @@ -133,4 +133,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsBackupServiceConfiguration](Remove-CsBackupServiceConfiguration.md) [Set-CsBackupServiceConfiguration](Set-CsBackupServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsBackupServiceStatus.md b/skype/skype-ps/skype/Get-CsBackupServiceStatus.md index 1e42fca825..6b305b2b3c 100644 --- a/skype/skype-ps/skype/Get-CsBackupServiceStatus.md +++ b/skype/skype-ps/skype/Get-CsBackupServiceStatus.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csbackupservicestatus +online version: https://learn.microsoft.com/powershell/module/skype/get-csbackupservicestatus applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsBackupServiceStatus schema: 2.0.0 @@ -122,4 +122,3 @@ Returns information about the backup service. ## RELATED LINKS [Get-CsBackupServiceConfiguration](Get-CsBackupServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsBandwidthPolicyServiceConfiguration.md b/skype/skype-ps/skype/Get-CsBandwidthPolicyServiceConfiguration.md index 48cd60363e..7b0c12b2c5 100644 --- a/skype/skype-ps/skype/Get-CsBandwidthPolicyServiceConfiguration.md +++ b/skype/skype-ps/skype/Get-CsBandwidthPolicyServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csbandwidthpolicyserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csbandwidthpolicyserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsBandwidthPolicyServiceConfiguration schema: 2.0.0 @@ -153,4 +153,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsBandwidthPolicyServiceConfiguration](Remove-CsBandwidthPolicyServiceConfiguration.md) [Set-CsBandwidthPolicyServiceConfiguration](Set-CsBandwidthPolicyServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsBlockedDomain.md b/skype/skype-ps/skype/Get-CsBlockedDomain.md index 780078da96..4db4188c4b 100644 --- a/skype/skype-ps/skype/Get-CsBlockedDomain.md +++ b/skype/skype-ps/skype/Get-CsBlockedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csblockeddomain +online version: https://learn.microsoft.com/powershell/module/skype/get-csblockeddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsBlockedDomain schema: 2.0.0 @@ -175,4 +175,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) [Set-CsBlockedDomain](Set-CsBlockedDomain.md) - diff --git a/skype/skype-ps/skype/Get-CsBroadcastMeetingConfiguration.md b/skype/skype-ps/skype/Get-CsBroadcastMeetingConfiguration.md index 6aebb3b81c..82470cd5a7 100644 --- a/skype/skype-ps/skype/Get-CsBroadcastMeetingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsBroadcastMeetingConfiguration.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csbroadcastmeetingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csbroadcastmeetingconfiguration applicable: Skype for Business Online title: Get-CsBroadcastMeetingConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsBroadcastMeetingConfiguration @@ -128,26 +128,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -166,4 +146,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsBroadcastMeetingPolicy.md b/skype/skype-ps/skype/Get-CsBroadcastMeetingPolicy.md index 088b337182..acdf4bbf3d 100644 --- a/skype/skype-ps/skype/Get-CsBroadcastMeetingPolicy.md +++ b/skype/skype-ps/skype/Get-CsBroadcastMeetingPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csbroadcastmeetingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csbroadcastmeetingpolicy applicable: Skype for Business Online title: Get-CsBroadcastMeetingPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsBroadcastMeetingPolicy @@ -240,26 +240,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -278,4 +258,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsBusyOptions.md b/skype/skype-ps/skype/Get-CsBusyOptions.md index ad2b099be5..717261c488 100644 --- a/skype/skype-ps/skype/Get-CsBusyOptions.md +++ b/skype/skype-ps/skype/Get-CsBusyOptions.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csbusyoptions +online version: https://learn.microsoft.com/powershell/module/skype/get-csbusyoptions applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsBusyOptions schema: 2.0.0 @@ -96,6 +96,6 @@ Microsoft.Rtc.Management.AD.UserIdParameter object. ## RELATED LINKS -[Remove-CsBusyOptions](https://docs.microsoft.com/powershell/module/skype/remove-csbusyoptions?view=skype-ps) +[Remove-CsBusyOptions](https://learn.microsoft.com/powershell/module/skype/remove-csbusyoptions?view=skype-ps) -[Set-CsBusyOptions](https://docs.microsoft.com/powershell/module/skype/set-csbusyoptions?view=skype-ps) +[Set-CsBusyOptions](https://learn.microsoft.com/powershell/module/skype/set-csbusyoptions?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsCallParkOrbit.md b/skype/skype-ps/skype/Get-CsCallParkOrbit.md index 8fc926c69e..d13afad9f1 100644 --- a/skype/skype-ps/skype/Get-CsCallParkOrbit.md +++ b/skype/skype-ps/skype/Get-CsCallParkOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscallparkorbit +online version: https://learn.microsoft.com/powershell/module/skype/get-cscallparkorbit applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsCallParkOrbit schema: 2.0.0 @@ -87,7 +87,7 @@ It does this by checking the StartsWith property of the NumberRangeStart object ### -------------------------- Example 6 -------------------------- ``` -Get-CsCallParkOrbit | Where-Object {\[Char\]::IsDigit($_.NumberRangeStart\[0\])} +Get-CsCallParkOrbit | Where-Object {[Char]::IsDigit($_.NumberRangeStart[0])} ``` The command in this example returns all call park orbit ranges where no prefix has been assigned to the numbers in the range. @@ -208,4 +208,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsCallParkOrbit](Remove-CsCallParkOrbit.md) [Set-CsCallParkOrbit](Set-CsCallParkOrbit.md) - diff --git a/skype/skype-ps/skype/Get-CsCallViaWorkPolicy.md b/skype/skype-ps/skype/Get-CsCallViaWorkPolicy.md index d1ed3a00e0..5bf6b230bd 100644 --- a/skype/skype-ps/skype/Get-CsCallViaWorkPolicy.md +++ b/skype/skype-ps/skype/Get-CsCallViaWorkPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscallviaworkpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-cscallviaworkpolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsCallViaWorkPolicy schema: 2.0.0 @@ -145,4 +145,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [New-CsCallViaWorkPolicy](New-CsCallViaWorkPolicy.md) [Grant-CsCallViaWorkPolicy](Grant-CsCallViaWorkPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsCallingLineIdentity.md b/skype/skype-ps/skype/Get-CsCallingLineIdentity.md deleted file mode 100644 index 4bdd17add7..0000000000 --- a/skype/skype-ps/skype/Get-CsCallingLineIdentity.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscallinglineidentity -applicable: Skype for Business Online -title: Get-CsCallingLineIdentity -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsCallingLineIdentity - -## SYNOPSIS -Use the `Get-CsCallingLineIdentity` cmdlet to display the Caller ID policies for your organization. - -## SYNTAX - -``` -Get-CsCallingLineIdentity [[-Identity] <XdsIdentity>] [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [-AsJob] -[<CommonParameters>] -``` - -## DESCRIPTION -By default, the Skype for Business Online user's phone number can be seen when that user makes a call to a PSTN phone, or when a call comes in. You can create Caller ID policies to change this behavior, and you can use the Get-CsCallingLineIdentity cmdlet to display the existing Caller ID policies for your organization. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Get-CsCallingLineIdentity -``` - -The example gets and displays the Caller ID policies for your organization. - -## PARAMETERS - -### -Filter -The Filter parameter lets you insert a string through which your search results are filtered. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter identifies the Caller ID policy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - - -## OUTPUTS - -### -Identity : Global - -Description : - -EnableUserOverride : False - -ServiceNumber : - -CallingIDSubstitute : LineUri - -BlockIncomingPstnCallerID : False - - -## NOTES - - -## RELATED LINKS -[Grant-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/grant-cscallinglineidentity?view=skype-ps) - -[New-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/new-cscallinglineidentity?view=skype-ps) - -[Remove-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/remove-cscallinglineidentity?view=skype-ps) - -[Set-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/set-cscallinglineidentity?view=skype-ps) - diff --git a/skype/skype-ps/skype/Get-CsCdrConfiguration.md b/skype/skype-ps/skype/Get-CsCdrConfiguration.md index 703ec90961..2b953208c4 100644 --- a/skype/skype-ps/skype/Get-CsCdrConfiguration.md +++ b/skype/skype-ps/skype/Get-CsCdrConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscdrconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cscdrconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsCdrConfiguration schema: 2.0.0 @@ -161,4 +161,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsCdrConfiguration](Remove-CsCdrConfiguration.md) [Set-CsCdrConfiguration](Set-CsCdrConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsCertificate.md b/skype/skype-ps/skype/Get-CsCertificate.md index 198dfbda65..99a8ec2704 100644 --- a/skype/skype-ps/skype/Get-CsCertificate.md +++ b/skype/skype-ps/skype/Get-CsCertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscertificate +online version: https://learn.microsoft.com/powershell/module/skype/get-cscertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsCertificate schema: 2.0.0 @@ -204,4 +204,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Request-CsCertificate](Request-CsCertificate.md) [Set-CsCertificate](Set-CsCertificate.md) - diff --git a/skype/skype-ps/skype/Get-CsClientAccessLicense.md b/skype/skype-ps/skype/Get-CsClientAccessLicense.md index 38fc20c0b8..ca9a1a2205 100644 --- a/skype/skype-ps/skype/Get-CsClientAccessLicense.md +++ b/skype/skype-ps/skype/Get-CsClientAccessLicense.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclientaccesslicense +online version: https://learn.microsoft.com/powershell/module/skype/get-csclientaccesslicense applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClientAccessLicense schema: 2.0.0 @@ -232,4 +232,3 @@ The Get-CsClientAccessLicense cmdlet returns licensing information. ## RELATED LINKS [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Get-CsClientCertificate.md b/skype/skype-ps/skype/Get-CsClientCertificate.md index 6775921162..396563d963 100644 --- a/skype/skype-ps/skype/Get-CsClientCertificate.md +++ b/skype/skype-ps/skype/Get-CsClientCertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclientcertificate +online version: https://learn.microsoft.com/powershell/module/skype/get-csclientcertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClientCertificate schema: 2.0.0 @@ -154,4 +154,3 @@ The cmdlet also accepts pipelined input of user objects. ## RELATED LINKS [Revoke-CsClientCertificate](Revoke-CsClientCertificate.md) - diff --git a/skype/skype-ps/skype/Get-CsClientPinInfo.md b/skype/skype-ps/skype/Get-CsClientPinInfo.md index d41082a872..58a1c53bdf 100644 --- a/skype/skype-ps/skype/Get-CsClientPinInfo.md +++ b/skype/skype-ps/skype/Get-CsClientPinInfo.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclientpininfo +online version: https://learn.microsoft.com/powershell/module/skype/get-csclientpininfo applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClientPinInfo schema: 2.0.0 @@ -157,4 +157,3 @@ The cmdlet also accepts pipelined input of user objects. [Set-CsClientPin](Set-CsClientPin.md) [Unlock-CsClientPin](Unlock-CsClientPin.md) - diff --git a/skype/skype-ps/skype/Get-CsClientPolicy.md b/skype/skype-ps/skype/Get-CsClientPolicy.md index 74bb736880..43174d771f 100644 --- a/skype/skype-ps/skype/Get-CsClientPolicy.md +++ b/skype/skype-ps/skype/Get-CsClientPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclientpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csclientpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClientPolicy schema: 2.0.0 manager: bulenteg @@ -176,26 +176,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### CommonParameters This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see (https://go.microsoft.com/fwlink/?LinkID=113216). @@ -221,4 +201,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsClientPolicy](Remove-CsClientPolicy.md) [Set-CsClientPolicy](Set-CsClientPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsClientVersionConfiguration.md b/skype/skype-ps/skype/Get-CsClientVersionConfiguration.md index 1eb7ce2e7a..62a9a4f591 100644 --- a/skype/skype-ps/skype/Get-CsClientVersionConfiguration.md +++ b/skype/skype-ps/skype/Get-CsClientVersionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclientversionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csclientversionconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClientVersionConfiguration schema: 2.0.0 @@ -173,4 +173,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsClientVersionConfiguration](Remove-CsClientVersionConfiguration.md) [Set-CsClientVersionConfiguration](Set-CsClientVersionConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsClientVersionPolicy.md b/skype/skype-ps/skype/Get-CsClientVersionPolicy.md index a696e4b6fa..79e4188c89 100644 --- a/skype/skype-ps/skype/Get-CsClientVersionPolicy.md +++ b/skype/skype-ps/skype/Get-CsClientVersionPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclientversionpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csclientversionpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClientVersionPolicy schema: 2.0.0 @@ -198,4 +198,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsClientVersionPolicy](Remove-CsClientVersionPolicy.md) [Set-CsClientVersionPolicy](Set-CsClientVersionPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsClientVersionPolicyRule.md b/skype/skype-ps/skype/Get-CsClientVersionPolicyRule.md index ed1192d11a..88381a0d58 100644 --- a/skype/skype-ps/skype/Get-CsClientVersionPolicyRule.md +++ b/skype/skype-ps/skype/Get-CsClientVersionPolicyRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclientversionpolicyrule +online version: https://learn.microsoft.com/powershell/module/skype/get-csclientversionpolicyrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClientVersionPolicyRule schema: 2.0.0 @@ -219,4 +219,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsClientVersionPolicyRule](Remove-CsClientVersionPolicyRule.md) [Set-CsClientVersionPolicyRule](Set-CsClientVersionPolicyRule.md) - diff --git a/skype/skype-ps/skype/Get-CsCloudCallDataConnector.md b/skype/skype-ps/skype/Get-CsCloudCallDataConnector.md index 832d81310b..9908ff7acb 100644 --- a/skype/skype-ps/skype/Get-CsCloudCallDataConnector.md +++ b/skype/skype-ps/skype/Get-CsCloudCallDataConnector.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscloudcalldataconnector +online version: https://learn.microsoft.com/powershell/module/skype/get-cscloudcalldataconnector applicable: Skype for Business Server 2019 title: Get-CsCloudCallDataConnector schema: 2.0.0 diff --git a/skype/skype-ps/skype/Get-CsCloudCallDataConnectorConfiguration.md b/skype/skype-ps/skype/Get-CsCloudCallDataConnectorConfiguration.md index f7e08b8d35..2e03619361 100644 --- a/skype/skype-ps/skype/Get-CsCloudCallDataConnectorConfiguration.md +++ b/skype/skype-ps/skype/Get-CsCloudCallDataConnectorConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscloudcalldataconnectorconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cscloudcalldataconnectorconfiguration applicable: Skype for Business Server 2019 title: Get-CsCloudCallDataConnectorConfiguration schema: 2.0.0 diff --git a/skype/skype-ps/skype/Get-CsCloudMeetingPolicy.md b/skype/skype-ps/skype/Get-CsCloudMeetingPolicy.md index 90807cfa2e..0cec065b8a 100644 --- a/skype/skype-ps/skype/Get-CsCloudMeetingPolicy.md +++ b/skype/skype-ps/skype/Get-CsCloudMeetingPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscloudmeetingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-cscloudmeetingpolicy applicable: Skype for Business Online title: Get-CsCloudMeetingPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsCloudMeetingPolicy @@ -128,26 +128,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). diff --git a/skype/skype-ps/skype/Get-CsClsAgentStatus.md b/skype/skype-ps/skype/Get-CsClsAgentStatus.md index aac759a754..cf595df96b 100644 --- a/skype/skype-ps/skype/Get-CsClsAgentStatus.md +++ b/skype/skype-ps/skype/Get-CsClsAgentStatus.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclsagentstatus +online version: https://learn.microsoft.com/powershell/module/skype/get-csclsagentstatus applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClsAgentStatus schema: 2.0.0 @@ -98,4 +98,3 @@ Or an XmlDocument object if the DefaultXml parameter is used. ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsClsConfiguration.md b/skype/skype-ps/skype/Get-CsClsConfiguration.md index 7281bbbab5..d64818736f 100644 --- a/skype/skype-ps/skype/Get-CsClsConfiguration.md +++ b/skype/skype-ps/skype/Get-CsClsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csclsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClsConfiguration schema: 2.0.0 @@ -182,4 +182,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsClsConfiguration](Remove-CsClsConfiguration.md) [Set-CsClsConfiguration](Set-CsClsConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsClsRegion.md b/skype/skype-ps/skype/Get-CsClsRegion.md index c409243968..2fbc717fd3 100644 --- a/skype/skype-ps/skype/Get-CsClsRegion.md +++ b/skype/skype-ps/skype/Get-CsClsRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclsregion +online version: https://learn.microsoft.com/powershell/module/skype/get-csclsregion applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClsRegion schema: 2.0.0 @@ -160,4 +160,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsClsRegion](Remove-CsClsRegion.md) [Set-CsClsRegion](Set-CsClsRegion.md) - diff --git a/skype/skype-ps/skype/Get-CsClsScenario.md b/skype/skype-ps/skype/Get-CsClsScenario.md index e5122159c4..b6d5b31459 100644 --- a/skype/skype-ps/skype/Get-CsClsScenario.md +++ b/skype/skype-ps/skype/Get-CsClsScenario.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclsscenario +online version: https://learn.microsoft.com/powershell/module/skype/get-csclsscenario applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClsScenario schema: 2.0.0 @@ -165,4 +165,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsClsSearchTerm.md b/skype/skype-ps/skype/Get-CsClsSearchTerm.md index 1b0891842a..df614416c4 100644 --- a/skype/skype-ps/skype/Get-CsClsSearchTerm.md +++ b/skype/skype-ps/skype/Get-CsClsSearchTerm.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclssearchterm +online version: https://learn.microsoft.com/powershell/module/skype/get-csclssearchterm applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClsSearchTerm schema: 2.0.0 @@ -168,4 +168,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsClsSearchTerm](Set-CsClsSearchTerm.md) - diff --git a/skype/skype-ps/skype/Get-CsClsSecurityGroup.md b/skype/skype-ps/skype/Get-CsClsSecurityGroup.md index a1b96e55a2..7c79d2ab0a 100644 --- a/skype/skype-ps/skype/Get-CsClsSecurityGroup.md +++ b/skype/skype-ps/skype/Get-CsClsSecurityGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csclssecuritygroup +online version: https://learn.microsoft.com/powershell/module/skype/get-csclssecuritygroup applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsClsSecurityGroup schema: 2.0.0 @@ -160,4 +160,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsClsSecurityGroup](Remove-CsClsSecurityGroup.md) [Set-CsClsSecurityGroup](Set-CsClsSecurityGroup.md) - diff --git a/skype/skype-ps/skype/Get-CsCommonAreaPhone.md b/skype/skype-ps/skype/Get-CsCommonAreaPhone.md index fe6b3b7ccb..97dc27f37a 100644 --- a/skype/skype-ps/skype/Get-CsCommonAreaPhone.md +++ b/skype/skype-ps/skype/Get-CsCommonAreaPhone.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscommonareaphone +online version: https://learn.microsoft.com/powershell/module/skype/get-cscommonareaphone applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsCommonAreaPhone schema: 2.0.0 @@ -269,4 +269,3 @@ Represents the Identity of the common area phone. [Remove-CsCommonAreaPhone](Remove-CsCommonAreaPhone.md) [Set-CsCommonAreaPhone](Set-CsCommonAreaPhone.md) - diff --git a/skype/skype-ps/skype/Get-CsComputer.md b/skype/skype-ps/skype/Get-CsComputer.md index d017fba976..295846eabe 100644 --- a/skype/skype-ps/skype/Get-CsComputer.md +++ b/skype/skype-ps/skype/Get-CsComputer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscomputer +online version: https://learn.microsoft.com/powershell/module/skype/get-cscomputer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsComputer schema: 2.0.0 @@ -164,4 +164,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Enable-CsComputer](Enable-CsComputer.md) [Test-CsComputer](Test-CsComputer.md) - diff --git a/skype/skype-ps/skype/Get-CsConferenceDirectory.md b/skype/skype-ps/skype/Get-CsConferenceDirectory.md index 25d83846c4..aaeb78a46a 100644 --- a/skype/skype-ps/skype/Get-CsConferenceDirectory.md +++ b/skype/skype-ps/skype/Get-CsConferenceDirectory.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csconferencedirectory +online version: https://learn.microsoft.com/powershell/module/skype/get-csconferencedirectory applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsConferenceDirectory schema: 2.0.0 @@ -144,4 +144,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [New-CsConferenceDirectory](New-CsConferenceDirectory.md) [Remove-CsConferenceDirectory](Remove-CsConferenceDirectory.md) - diff --git a/skype/skype-ps/skype/Get-CsConferenceDisclaimer.md b/skype/skype-ps/skype/Get-CsConferenceDisclaimer.md index dd4ec07886..6ce2b822e0 100644 --- a/skype/skype-ps/skype/Get-CsConferenceDisclaimer.md +++ b/skype/skype-ps/skype/Get-CsConferenceDisclaimer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csconferencedisclaimer +online version: https://learn.microsoft.com/powershell/module/skype/get-csconferencedisclaimer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsConferenceDisclaimer schema: 2.0.0 @@ -126,4 +126,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsConferenceDisclaimer](Remove-CsConferenceDisclaimer.md) [Set-CsConferenceDisclaimer](Set-CsConferenceDisclaimer.md) - diff --git a/skype/skype-ps/skype/Get-CsConferencingConfiguration.md b/skype/skype-ps/skype/Get-CsConferencingConfiguration.md index 9bbfc33fee..381a5744ae 100644 --- a/skype/skype-ps/skype/Get-CsConferencingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsConferencingConfiguration schema: 2.0.0 @@ -175,4 +175,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsConferencingConfiguration](Remove-CsConferencingConfiguration.md) [Set-CsConferencingConfiguration](Set-CsConferencingConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsConferencingPolicy.md b/skype/skype-ps/skype/Get-CsConferencingPolicy.md index 2bec59bc68..570ad8b1b5 100644 --- a/skype/skype-ps/skype/Get-CsConferencingPolicy.md +++ b/skype/skype-ps/skype/Get-CsConferencingPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csconferencingpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csconferencingpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsConferencingPolicy schema: 2.0.0 manager: bulenteg @@ -237,22 +237,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -280,4 +264,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsConferencingPolicy](Set-CsConferencingPolicy.md) [Get-CsConferencingPolicy](Get-CsConferencingPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsConfigurationStoreLocation.md b/skype/skype-ps/skype/Get-CsConfigurationStoreLocation.md index dd73e9a00f..fdc95a47a5 100644 --- a/skype/skype-ps/skype/Get-CsConfigurationStoreLocation.md +++ b/skype/skype-ps/skype/Get-CsConfigurationStoreLocation.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csconfigurationstorelocation +online version: https://learn.microsoft.com/powershell/module/skype/get-csconfigurationstorelocation applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsConfigurationStoreLocation schema: 2.0.0 @@ -111,4 +111,3 @@ The Get-CsConfigurationStoreLocation cmdlet reports back the location of the con [Remove-CsConfigurationStoreLocation](Remove-CsConfigurationStoreLocation.md) [Set-CsConfigurationStoreLocation](Set-CsConfigurationStoreLocation.md) - diff --git a/skype/skype-ps/skype/Get-CsConversationHistoryConfiguration.md b/skype/skype-ps/skype/Get-CsConversationHistoryConfiguration.md index 137fca243a..8c4b36089d 100644 --- a/skype/skype-ps/skype/Get-CsConversationHistoryConfiguration.md +++ b/skype/skype-ps/skype/Get-CsConversationHistoryConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csconversationhistoryconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csconversationhistoryconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsConversationHistoryConfiguration schema: 2.0.0 @@ -129,4 +129,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsConversationHistoryConfiguration](Remove-CsConversationHistoryConfiguration.md) [Set-CsConversationHistoryConfiguration](Set-CsConversationHistoryConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsCpsConfiguration.md b/skype/skype-ps/skype/Get-CsCpsConfiguration.md index 96de9c6a9e..2859c7b997 100644 --- a/skype/skype-ps/skype/Get-CsCpsConfiguration.md +++ b/skype/skype-ps/skype/Get-CsCpsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscpsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cscpsconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsCpsConfiguration schema: 2.0.0 @@ -159,4 +159,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsCpsConfiguration](Set-CsCpsConfiguration.md) [Set-CsCallParkServiceMusicOnHoldFile](Set-CsCallParkServiceMusicOnHoldFile.md) - diff --git a/skype/skype-ps/skype/Get-CsDatabaseMirrorState.md b/skype/skype-ps/skype/Get-CsDatabaseMirrorState.md index eb1626d850..ab7cc8b8ab 100644 --- a/skype/skype-ps/skype/Get-CsDatabaseMirrorState.md +++ b/skype/skype-ps/skype/Get-CsDatabaseMirrorState.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdatabasemirrorstate -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-csdatabasemirrorstate +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDatabaseMirrorState schema: 2.0.0 manager: rogupta @@ -173,4 +173,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Install-CsMirrorDatabase](Install-CsMirrorDatabase.md) [Uninstall-CsMirrorDatabase](Uninstall-CsMirrorDatabase.md) - diff --git a/skype/skype-ps/skype/Get-CsDeviceUpdateConfiguration.md b/skype/skype-ps/skype/Get-CsDeviceUpdateConfiguration.md index f69445587f..dcc4810931 100644 --- a/skype/skype-ps/skype/Get-CsDeviceUpdateConfiguration.md +++ b/skype/skype-ps/skype/Get-CsDeviceUpdateConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdeviceupdateconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csdeviceupdateconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDeviceUpdateConfiguration schema: 2.0.0 @@ -166,4 +166,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsDeviceUpdateConfiguration](Remove-CsDeviceUpdateConfiguration.md) [Set-CsDeviceUpdateConfiguration](Set-CsDeviceUpdateConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsDeviceUpdateRule.md b/skype/skype-ps/skype/Get-CsDeviceUpdateRule.md index fb4e0dae38..0e5442fdfb 100644 --- a/skype/skype-ps/skype/Get-CsDeviceUpdateRule.md +++ b/skype/skype-ps/skype/Get-CsDeviceUpdateRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdeviceupdaterule +online version: https://learn.microsoft.com/powershell/module/skype/get-csdeviceupdaterule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDeviceUpdateRule schema: 2.0.0 @@ -181,4 +181,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Reset-CsDeviceUpdateRule](Reset-CsDeviceUpdateRule.md) [Restore-CsDeviceUpdateRule](Restore-CsDeviceUpdateRule.md) - diff --git a/skype/skype-ps/skype/Get-CsDiagnosticConfiguration.md b/skype/skype-ps/skype/Get-CsDiagnosticConfiguration.md index 138e76de41..e828788cb7 100644 --- a/skype/skype-ps/skype/Get-CsDiagnosticConfiguration.md +++ b/skype/skype-ps/skype/Get-CsDiagnosticConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdiagnosticconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csdiagnosticconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDiagnosticConfiguration schema: 2.0.0 @@ -173,4 +173,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsDiagnosticConfiguration](Remove-CsDiagnosticConfiguration.md) [Set-CsDiagnosticConfiguration](Set-CsDiagnosticConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsDiagnosticHeaderConfiguration.md b/skype/skype-ps/skype/Get-CsDiagnosticHeaderConfiguration.md index f3e74f578e..70f111e8de 100644 --- a/skype/skype-ps/skype/Get-CsDiagnosticHeaderConfiguration.md +++ b/skype/skype-ps/skype/Get-CsDiagnosticHeaderConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdiagnosticheaderconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csdiagnosticheaderconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDiagnosticHeaderConfiguration schema: 2.0.0 @@ -181,4 +181,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsDiagnosticHeaderConfiguration](Remove-CsDiagnosticHeaderConfiguration.md) [Set-CsDiagnosticHeaderConfiguration](Set-CsDiagnosticHeaderConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsDialInConferencingAccessNumber.md b/skype/skype-ps/skype/Get-CsDialInConferencingAccessNumber.md index a002bff27d..fe50bf5290 100644 --- a/skype/skype-ps/skype/Get-CsDialInConferencingAccessNumber.md +++ b/skype/skype-ps/skype/Get-CsDialInConferencingAccessNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdialinconferencingaccessnumber +online version: https://learn.microsoft.com/powershell/module/skype/get-csdialinconferencingaccessnumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDialInConferencingAccessNumber schema: 2.0.0 @@ -329,4 +329,3 @@ The Get-CsDialInConferencingAccessNumber cmdlet accepts a string value represent [Remove-CsDialInConferencingAccessNumber](Remove-CsDialInConferencingAccessNumber.md) [Set-CsDialInConferencingAccessNumber](Set-CsDialInConferencingAccessNumber.md) - diff --git a/skype/skype-ps/skype/Get-CsDialInConferencingConfiguration.md b/skype/skype-ps/skype/Get-CsDialInConferencingConfiguration.md index 53a14f2cde..1a86bff077 100644 --- a/skype/skype-ps/skype/Get-CsDialInConferencingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsDialInConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdialinconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csdialinconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDialInConferencingConfiguration schema: 2.0.0 @@ -157,4 +157,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsDialInConferencingConfiguration](Remove-CsDialInConferencingConfiguration.md) [Set-CsDialInConferencingConfiguration](Set-CsDialInConferencingConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsDialInConferencingDtmfConfiguration.md b/skype/skype-ps/skype/Get-CsDialInConferencingDtmfConfiguration.md index efdcc93ec6..7656e7a355 100644 --- a/skype/skype-ps/skype/Get-CsDialInConferencingDtmfConfiguration.md +++ b/skype/skype-ps/skype/Get-CsDialInConferencingDtmfConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdialinconferencingdtmfconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csdialinconferencingdtmfconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDialInConferencingDtmfConfiguration schema: 2.0.0 @@ -162,4 +162,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsDialInConferencingDtmfConfiguration](Remove-CsDialInConferencingDtmfConfiguration.md) [Set-CsDialInConferencingDtmfConfiguration](Set-CsDialInConferencingDtmfConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsDialInConferencingLanguageList.md b/skype/skype-ps/skype/Get-CsDialInConferencingLanguageList.md index 6e055957ed..1f82e950cc 100644 --- a/skype/skype-ps/skype/Get-CsDialInConferencingLanguageList.md +++ b/skype/skype-ps/skype/Get-CsDialInConferencingLanguageList.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdialinconferencinglanguagelist +online version: https://learn.microsoft.com/powershell/module/skype/get-csdialinconferencinglanguagelist applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDialInConferencingLanguageList schema: 2.0.0 @@ -144,4 +144,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [New-CsDialInConferencingAccessNumber](New-CsDialInConferencingAccessNumber.md) [Set-CsDialInConferencingAccessNumber](Set-CsDialInConferencingAccessNumber.md) - diff --git a/skype/skype-ps/skype/Get-CsDialPlan.md b/skype/skype-ps/skype/Get-CsDialPlan.md index 58fb23bd97..bd10f2446f 100644 --- a/skype/skype-ps/skype/Get-CsDialPlan.md +++ b/skype/skype-ps/skype/Get-CsDialPlan.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csdialplan +online version: https://learn.microsoft.com/powershell/module/skype/get-csdialplan applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsDialPlan schema: 2.0.0 @@ -187,4 +187,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Test-CsDialPlan](Test-CsDialPlan.md) [Get-CsVoiceNormalizationRule](Get-CsVoiceNormalizationRule.md) - diff --git a/skype/skype-ps/skype/Get-CsEffectivePolicy.md b/skype/skype-ps/skype/Get-CsEffectivePolicy.md index 2b8582f3e8..117520586f 100644 --- a/skype/skype-ps/skype/Get-CsEffectivePolicy.md +++ b/skype/skype-ps/skype/Get-CsEffectivePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cseffectivepolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-cseffectivepolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsEffectivePolicy schema: 2.0.0 @@ -213,4 +213,3 @@ The cmdlet also accepts pipelined instances of the Active Directory user object. ## RELATED LINKS [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Get-CsEffectiveTenantDialPlan.md b/skype/skype-ps/skype/Get-CsEffectiveTenantDialPlan.md deleted file mode 100644 index 28553b500f..0000000000 --- a/skype/skype-ps/skype/Get-CsEffectiveTenantDialPlan.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cseffectivetenantdialplan -applicable: Skype for Business Online -title: Get-CsEffectiveTenantDialPlan -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsEffectiveTenantDialPlan - -## SYNOPSIS -Use the Get-CsEffectiveTenantDialPlan cmdlet to retrieve an effective tenant dial plan. - -## SYNTAX - -``` -Get-CsEffectiveTenantDialPlan [-Identity] <UserIdParameter> [-OU <OUIdParameter>] [-DomainController <Fqdn>] - [-Credential <PSCredential>] [-ResultSize <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsEffectiveTenantDialPlan cmdlet returns information about the effective tenant dial plan in an organization. -The returned effective Tenant Dial Plan contains the Identity and the Normalization rules that are effective for the user while using the EnterpriseVoice features. -The Identity is in the form TenantGUID_GlobalVoiceDialPlan_TenantDialPlan. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsEffectiveTenantDialPlan -Identity Vt1_User1 -``` - -This example gets the effective tenant dial plan for the Vt1_User1 organization. - - -## PARAMETERS - -### -Identity -The Identity parameter is the unique identifier of the tenant dial plan to retrieve. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -The Credential parameter specifies the user name 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. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Specifies the domain controller that's used by the cmdlet to read or write the specified data. -Valid inputs for this parameter are either the fully qualified domain name (FQDN) or the computer name. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OU -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. - -```yaml -Type: OUIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -Specifies the number of records returned by the cmdlet. -The result size can be set to any whole number between 0 and 2147483647, inclusive. -If set to 0, the command will run, but no data will be returned. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - - -## OUTPUTS - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsEnhancedEmergencyServiceDisclaimer.md b/skype/skype-ps/skype/Get-CsEnhancedEmergencyServiceDisclaimer.md index b680e2f691..36aa47f5ad 100644 --- a/skype/skype-ps/skype/Get-CsEnhancedEmergencyServiceDisclaimer.md +++ b/skype/skype-ps/skype/Get-CsEnhancedEmergencyServiceDisclaimer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csenhancedemergencyservicedisclaimer +online version: https://learn.microsoft.com/powershell/module/skype/get-csenhancedemergencyservicedisclaimer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsEnhancedEmergencyServiceDisclaimer schema: 2.0.0 @@ -122,4 +122,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsEnhancedEmergencyServiceDisclaimer](Set-CsEnhancedEmergencyServiceDisclaimer.md) [Get-CsLocationPolicy](Get-CsLocationPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsExUmContact.md b/skype/skype-ps/skype/Get-CsExUmContact.md index 06230805e7..e674e05256 100644 --- a/skype/skype-ps/skype/Get-CsExUmContact.md +++ b/skype/skype-ps/skype/Get-CsExUmContact.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csexumcontact +online version: https://learn.microsoft.com/powershell/module/skype/get-csexumcontact applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsExUmContact schema: 2.0.0 @@ -238,4 +238,3 @@ Accepts a pipelined string value representing the Identity of an Exchange UM con [Set-CsExUmContact](Set-CsExUmContact.md) [Move-CsExUmContact](Move-CsExUmContact.md) - diff --git a/skype/skype-ps/skype/Get-CsExternalAccessPolicy.md b/skype/skype-ps/skype/Get-CsExternalAccessPolicy.md index e5e61fe3bb..5fa4d707b7 100644 --- a/skype/skype-ps/skype/Get-CsExternalAccessPolicy.md +++ b/skype/skype-ps/skype/Get-CsExternalAccessPolicy.md @@ -1,10 +1,9 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csexternalaccesspolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csexternalaccesspolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsExternalAccessPolicy schema: 2.0.0 -manager: bulenteg author: tomkau ms.author: tomkau ms.reviewer: rogupta @@ -14,9 +13,9 @@ ms.reviewer: rogupta ## SYNOPSIS Returns information about the external access policies that have been configured for use in your organization. -External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Windows Live; and, 3) access Skype for Business Server over the Internet, without having to log on to your internal network. -This cmdlet was introduced in Lync Server 2010. +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; and, 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype. +This cmdlet was introduced in Lync Server 2010. ## SYNTAX @@ -44,12 +43,15 @@ External access policies can grant (or revoke) the ability of your users to do a 1. Communicate with people who have SIP accounts with a federated organization. Note that enabling federation alone will not provide users with this capability. Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. -2. Communicate with people who have SIP accounts with a public instant messaging service such as Windows Live. + +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration). + 3. Access Skype for Business Server over the Internet, without having to first log on to your internal network. This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. -The Get-CsExternalAccessPolicy cmdlet provides a way for you to return information about all of the external access policies that have been configured for use in your organization. +4. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. +The Get-CsExternalAccessPolicy cmdlet provides a way for you to return information about all of the external access policies that have been configured for use in your organization. ## EXAMPLES @@ -61,7 +63,6 @@ Get-CsExternalAccessPolicy Example 1 returns a collection of all the external access policies configured for use in your organization. Calling the Get-CsExternalAccessPolicy cmdlet without any additional parameters always returns the complete collection of external access policies. - ### -------------------------- EXAMPLE 2 -------------------------- (Skype for Business Online) ``` Get-CsExternalAccessPolicy -Identity "tag:RedmondExternalAccessPolicy" @@ -70,8 +71,6 @@ Get-CsExternalAccessPolicy -Identity "tag:RedmondExternalAccessPolicy" Example 2 uses the Identity parameter to return the external access policy that has the Identity tag:RedmondExternalAccessPolicy. Because access policy Identities must be unique, this command will never return more than one item. - - ### -------------------------- EXAMPLE 2 -------------------------- (Skype for Business Server 2015) ``` Get-CsExternalAccessPolicy -Identity site:Redmond @@ -118,7 +117,6 @@ NOTE: The ApplicableTo parameter can only be used with Skype for Business Online NOTE: This command requires the Office 365 UsageLocation property to be configured for the user's Active Directory user account. - ## PARAMETERS ### -Identity @@ -150,18 +148,16 @@ Accept wildcard characters: False **Below Content Applies To:** Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 Enables you to do a wildcard search for external access policies. -For example, to find all the policies configured at the site scope, use this Filter: +For example, to find all the policies configured at the site scope, use this Filter: `site:*` -To find the per-user policies Seattle, Seville, and Saskatoon (all of which start with the letter "S") use this Filter: +To find the per-user policies Seattle, Seville, and Saskatoon (all of which start with the letter "S") use this Filter: `"S*".` Note that the Filter parameter can only be applied to the policy Identity. - - **Below Content Applies To:** Skype for Business Online Enables you to do a wildcard search for external access policies. @@ -175,8 +171,6 @@ To find the per-user policies Seattle, Seville, and Saskatoon (all of which star Note that the Filter parameter can only be applied to the policy Identity. - - ```yaml Type: String Parameter Sets: Filter, (All) @@ -267,43 +261,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). - ## INPUTS ### None - ## OUTPUTS ### Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy - ## NOTES - ## RELATED LINKS [Grant-CsExternalAccessPolicy](Grant-CsExternalAccessPolicy.md) @@ -313,4 +283,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md) [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsExternalUserCommunicationPolicy.md b/skype/skype-ps/skype/Get-CsExternalUserCommunicationPolicy.md index 7671b605ce..f3dc30cd98 100644 --- a/skype/skype-ps/skype/Get-CsExternalUserCommunicationPolicy.md +++ b/skype/skype-ps/skype/Get-CsExternalUserCommunicationPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csexternalusercommunicationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csexternalusercommunicationpolicy applicable: Skype for Business Online title: Get-CsExternalUserCommunicationPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsExternalUserCommunicationPolicy @@ -19,7 +19,7 @@ Returns information about one or more external user communication policies confi ## SYNTAX ``` -Get-CsExternalUserCommunicationPolicy [[-Identity] <XdsIdentity>] [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [-AsJob] [<CommonParameters>] +Get-CsExternalUserCommunicationPolicy [[-Identity] <XdsIdentity>] [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [<CommonParameters>] ``` ## DESCRIPTION @@ -46,7 +46,7 @@ This example uses the Identity parameter to retrieve the external user communica PS C:\> Get-CsExternalUserCommunicationPolicy -Filter tag* ``` -This example uses the Filter parameter to retrieve all the external user communication policies along with the settings for each. All per-user external user communication policies have an Identity in the format tag:<ExternalUserCommunicationPolicy>. +This example uses the Filter parameter to retrieve all the external user communication policies along with the settings for each. All per-user external user communication policies have an Identity in the format `tag:<ExternalUserCommunicationPolicy>`. ### -------------------------- Example 4 ------------------------ ``` @@ -128,26 +128,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -162,10 +142,10 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[New-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/new-csexternalusercommunicationpolicy?view=skype-ps) +[New-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/new-csexternalusercommunicationpolicy?view=skype-ps) -[Set-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/set-csexternalusercommunicationpolicy?view=skype-ps) +[Set-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/set-csexternalusercommunicationpolicy?view=skype-ps) -[Remove-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csexternalusercommunicationpolicy?view=skype-ps) +[Remove-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/remove-csexternalusercommunicationpolicy?view=skype-ps) -[Grant-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csexternalusercommunicationpolicy?view=skype-ps) +[Grant-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/grant-csexternalusercommunicationpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsFIPSConfiguration.md b/skype/skype-ps/skype/Get-CsFIPSConfiguration.md index d675ebe1a3..4a4f0b69d7 100644 --- a/skype/skype-ps/skype/Get-CsFIPSConfiguration.md +++ b/skype/skype-ps/skype/Get-CsFIPSConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csfipsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csfipsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsFIPSConfiguration schema: 2.0.0 @@ -163,4 +163,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsFIPSConfiguration](Remove-CsFIPSConfiguration.md) [Set-CsFIPSConfiguration](Set-CsFIPSConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsFileTransferFilterConfiguration.md b/skype/skype-ps/skype/Get-CsFileTransferFilterConfiguration.md index 8967cc0a0f..388bc6c94d 100644 --- a/skype/skype-ps/skype/Get-CsFileTransferFilterConfiguration.md +++ b/skype/skype-ps/skype/Get-CsFileTransferFilterConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csfiletransferfilterconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csfiletransferfilterconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsFileTransferFilterConfiguration schema: 2.0.0 @@ -174,4 +174,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsFileTransferFilterConfiguration](Remove-CsFileTransferFilterConfiguration.md) [Set-CsFileTransferFilterConfiguration](Set-CsFileTransferFilterConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsGraphPolicy.md b/skype/skype-ps/skype/Get-CsGraphPolicy.md index 84914916fa..69cd22f5e8 100644 --- a/skype/skype-ps/skype/Get-CsGraphPolicy.md +++ b/skype/skype-ps/skype/Get-CsGraphPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csgraphpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csgraphpolicy applicable: Skype for Business Online title: Get-CsGraphPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsGraphPolicy @@ -17,7 +17,7 @@ Use the `Get-CsGraphPolicy` cmdlet to return information about one or more graph ## SYNTAX ``` -Get-CsGraphPolicy [[-Identity] <XdsIdentity>] [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [-AsJob] +Get-CsGraphPolicy [[-Identity] <XdsIdentity>] [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [<CommonParameters>] ``` @@ -112,26 +112,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -142,4 +122,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[Grant-CsGraphPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csgraphpolicy?view=skype-ps) +[Grant-CsGraphPolicy](https://learn.microsoft.com/powershell/module/skype/grant-csgraphpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsGroupPickupUserOrbit.md b/skype/skype-ps/skype/Get-CsGroupPickupUserOrbit.md index c2742d7cbc..199078925f 100644 --- a/skype/skype-ps/skype/Get-CsGroupPickupUserOrbit.md +++ b/skype/skype-ps/skype/Get-CsGroupPickupUserOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csgrouppickupuserorbit +online version: https://learn.microsoft.com/powershell/module/skype/get-csgrouppickupuserorbit applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsGroupPickupUserOrbit schema: 2.0.0 @@ -106,4 +106,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsHealthMonitoringConfiguration.md b/skype/skype-ps/skype/Get-CsHealthMonitoringConfiguration.md index 0aff88f824..ce017ff110 100644 --- a/skype/skype-ps/skype/Get-CsHealthMonitoringConfiguration.md +++ b/skype/skype-ps/skype/Get-CsHealthMonitoringConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshealthmonitoringconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cshealthmonitoringconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsHealthMonitoringConfiguration schema: 2.0.0 @@ -161,4 +161,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsHealthMonitoringConfiguration](Remove-CsHealthMonitoringConfiguration.md) [Set-CsHealthMonitoringConfiguration](Set-CsHealthMonitoringConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsHostedVoicemailPolicy.md b/skype/skype-ps/skype/Get-CsHostedVoicemailPolicy.md index e18f3c7d02..7910736a0e 100644 --- a/skype/skype-ps/skype/Get-CsHostedVoicemailPolicy.md +++ b/skype/skype-ps/skype/Get-CsHostedVoicemailPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshostedvoicemailpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-cshostedvoicemailpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsHostedVoicemailPolicy schema: 2.0.0 manager: bulenteg @@ -60,14 +60,6 @@ Get-CsHostedVoicemailPolicy -Filter tag:* This command returns the policy settings for all per-user hosted voice mail policies (policies beginning with the tag scope). -### -------------------------- Example 4 -------------------------- -``` -Get-CsHostedVoicemailPolicy -Tenant "73d355dd-ce5d-4ab9-bf49-7b822c18dd98" -``` - -This command returns the hosted voice mail policy for the Skype for Business Online tenant with the tenant ID 73d355dd-ce5d-4ab9-bf49-7b822c18dd98. - - ## PARAMETERS ### -Identity @@ -78,7 +70,7 @@ The Identity includes the scope (in the case of global), the scope and site (for Type: XdsIdentity Parameter Sets: Identity, (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 2 @@ -95,7 +87,7 @@ This will retrieve all instances of a hosted voice mail policy where the Identit Type: String Parameter Sets: Filter, (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -111,55 +103,7 @@ Retrieves the hosted voice mail policy from the local replica of the Central Man Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the Skype for Business Online tenant account whose voicemail policy is to be retrieved. - -For example: - -`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` - -You can return the tenant ID for each of your tenants by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -194,4 +138,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsHostedVoicemailPolicy](Set-CsHostedVoicemailPolicy.md) [Grant-CsHostedVoicemailPolicy](Grant-CsHostedVoicemailPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsHostingProvider.md b/skype/skype-ps/skype/Get-CsHostingProvider.md index edaf6152ae..3e5f2a3e66 100644 --- a/skype/skype-ps/skype/Get-CsHostingProvider.md +++ b/skype/skype-ps/skype/Get-CsHostingProvider.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshostingprovider -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-cshostingprovider +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsHostingProvider schema: 2.0.0 manager: bulenteg @@ -159,26 +159,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -207,4 +187,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsHostingProvider](Remove-CsHostingProvider.md) [Set-CsHostingProvider](Set-CsHostingProvider.md) - diff --git a/skype/skype-ps/skype/Get-CsHuntGroup.md b/skype/skype-ps/skype/Get-CsHuntGroup.md deleted file mode 100644 index 493bc3d1c9..0000000000 --- a/skype/skype-ps/skype/Get-CsHuntGroup.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshuntgroup -applicable: Skype for Business Online -title: Get-CsHuntGroup -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsHuntGroup - -## SYNOPSIS -The Get-CsHuntGroup cmdlet returns the identified Call Queues. - -## SYNTAX - -``` -Get-CsHuntGroup [-PrimaryUri <System.Uri>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsHuntGroup cmdlet lets you retrieve information about the Call Queues in your organization. Call Queue output contains statistical data on the number of active calls that are in the queue. - -If called without parameters, Get-CsHuntgroup returns a collection of all Call Queues configured to be used in your organization. - -The Get-CsHuntGroup cmdlet may suggest additional steps required to complete the Call Queue setup. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsHuntGroup -``` - -This example gets all Call Queues in the organization. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsHuntGroup -PrimaryUri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com" -``` - -This example gets the Call Queue with the primary uri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com". If no Call Queue exists with the primary uri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com", then this example generates an error. - - -## PARAMETERS - -### -PrimaryUri -The PrimaryUri parameter represents the SIP address for the Call Queue. It must start with "sip:". - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassDualWrite -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for Microsoft internal use only. - -PARAMVALUE: Fqdn - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.HuntGroup.Models.HuntGroup - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsHuntGroupTenantInformation.md b/skype/skype-ps/skype/Get-CsHuntGroupTenantInformation.md deleted file mode 100644 index 0274c8e1f5..0000000000 --- a/skype/skype-ps/skype/Get-CsHuntGroupTenantInformation.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshuntgrouptenantinformation -applicable: Skype for Business Online -title: Get-CsHuntGroupTenantInformation -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsHuntGroupTenantInformation - -## SYNOPSIS -The Get-CsHuntGroupTenantInformation cmdlet returns additional call queue information for the tenant. - -## SYNTAX - -``` -Get-CsHuntGroupTenantInformation [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsHuntGroupTenantInformation cmdlet returns additional call queue information for the tenant. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsHuntGroupTenantInformation -``` -This example returns additional call queue information for the tenant. - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Get-CsHybridApplicationEndpoint.md b/skype/skype-ps/skype/Get-CsHybridApplicationEndpoint.md index cf1ab93d84..4fe4251dd1 100644 --- a/skype/skype-ps/skype/Get-CsHybridApplicationEndpoint.md +++ b/skype/skype-ps/skype/Get-CsHybridApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsHybridApplicationEndpoint schema: 2.0.0 @@ -55,7 +55,7 @@ This example uses the Filter parameter to retrieve all the hybrid application en ### -Credential Enables you to run the Get-CsHybridApplicationEndpoint cmdlet under alternate credentials. This might be required if the account you used to log on to the Windows does not have the necessary privileges required to work with user objects. -To use the Credential parameter you must first create a PSCredential object by using the [Get-Credential](https://docs.microsoft.com/powershell/module/microsoft.powershell.security/get-credential?view=powershell-6) cmdlet. For details, see the Get-Credential cmdlet help topic. +To use the Credential parameter you must first create a PSCredential object by using the [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential?view=powershell-6) cmdlet. For details, see the Get-Credential cmdlet help topic. ```yaml Type: PSCredential @@ -194,8 +194,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[New-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint?view=skype-ps) +[New-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint?view=skype-ps) -[Set-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint?view=skype-ps) +[Set-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint?view=skype-ps) -[Remove-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint?view=skype-ps) +[Remove-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsHybridMediationServer.md b/skype/skype-ps/skype/Get-CsHybridMediationServer.md index 1090338d69..22a1a60c23 100644 --- a/skype/skype-ps/skype/Get-CsHybridMediationServer.md +++ b/skype/skype-ps/skype/Get-CsHybridMediationServer.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshybridmediationserver +online version: https://learn.microsoft.com/powershell/module/skype/get-cshybridmediationserver applicable: Skype for Business Online title: Get-CsHybridMediationServer schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsHybridMediationServer @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Gets the external FQDN of an Edge server access proxy that serves as a hosting provider to a user. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` @@ -111,26 +113,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). diff --git a/skype/skype-ps/skype/Get-CsHybridPSTNAppliance.md b/skype/skype-ps/skype/Get-CsHybridPSTNAppliance.md index 281fb0f9e1..35c6ae3de8 100644 --- a/skype/skype-ps/skype/Get-CsHybridPSTNAppliance.md +++ b/skype/skype-ps/skype/Get-CsHybridPSTNAppliance.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshybridpstnappliance +online version: https://learn.microsoft.com/powershell/module/skype/get-cshybridpstnappliance applicable: Skype for Business Online title: Get-CsHybridPSTNAppliance schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsHybridPSTNAppliance @@ -15,11 +15,13 @@ ms.reviewer: ## SYNOPSIS Use the `Get-CsHybridPSTNAppliance` cmdlet to retrieve information about your Skype for Business Cloud Connector Edition appliances. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` Get-CsHybridPSTNAppliance [-Name <String>] [-LocalStore] [[-Identity] <XdsGlobalRelativeIdentity>] -[-Tenant <Guid>] [-Filter <String>] [-SiteName <String>] [-AsJob] [<CommonParameters>] +[-Tenant <Guid>] [-Filter <String>] [-SiteName <String>] [<CommonParameters>] ``` ## DESCRIPTION @@ -169,26 +171,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -199,8 +181,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[Set-CsHybridPSTNAppliance](https://docs.microsoft.com/powershell/module/skype/set-cshybridpstnappliance?view=skype-ps) +[Set-CsHybridPSTNAppliance](https://learn.microsoft.com/powershell/module/skype/set-cshybridpstnappliance?view=skype-ps) -[Register-CsHybridPSTNAppliance](https://docs.microsoft.com/powershell/module/skype/register-cshybridpstnappliance?view=skype-ps) +[Register-CsHybridPSTNAppliance](https://learn.microsoft.com/powershell/module/skype/register-cshybridpstnappliance?view=skype-ps) -[Unregister-CsHybridPSTNAppliance](https://docs.microsoft.com/powershell/module/skype/unregister-cshybridpstnappliance?view=skype-ps) +[Unregister-CsHybridPSTNAppliance](https://learn.microsoft.com/powershell/module/skype/unregister-cshybridpstnappliance?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsHybridPSTNSite.md b/skype/skype-ps/skype/Get-CsHybridPSTNSite.md index 833ff31ddb..3bfc36476a 100644 --- a/skype/skype-ps/skype/Get-CsHybridPSTNSite.md +++ b/skype/skype-ps/skype/Get-CsHybridPSTNSite.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cshybridpstnsite +online version: https://learn.microsoft.com/powershell/module/skype/get-cshybridpstnsite applicable: Skype for Business Online title: Get-CsHybridPSTNSite schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsHybridPSTNSite @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the Get-CsHybridPSTNSite cmdlet to retrieve information about your hybrid public switched telephone network (PSTN) sites. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -128,26 +130,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -165,4 +147,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsIPPhonePolicy.md b/skype/skype-ps/skype/Get-CsIPPhonePolicy.md index 23b4f09d42..7ae4ac2e57 100644 --- a/skype/skype-ps/skype/Get-CsIPPhonePolicy.md +++ b/skype/skype-ps/skype/Get-CsIPPhonePolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csipphonepolicy -applicable: Skype for Business Online, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csipphonepolicy +applicable: Skype for Business Server 2019 title: Get-CsIPPhonePolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsIPPhonePolicy @@ -18,7 +18,7 @@ Use the Get-CsIPPhonePolicy cmdlet to get all the settings of the Skype for Busi ## SYNTAX ``` -Get-CsIPPhonePolicy [[-Identity] <XdsIdentity>] [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [-AsJob] [<CommonParameters>] +Get-CsIPPhonePolicy [[-Identity] <XdsIdentity>] [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [<CommonParameters>] ``` ## DESCRIPTION @@ -99,26 +99,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -136,6 +116,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Grant-CsIPPhonePolicy](https://docs.microsoft.com/powershell/module/skype/grant-csipphonepolicy?view=skype-ps) +[Grant-CsIPPhonePolicy](https://learn.microsoft.com/powershell/module/skype/grant-csipphonepolicy?view=skype-ps) -[Set-CsIPPhonePolicy](https://docs.microsoft.com/powershell/module/skype/set-csipphonepolicy?view=skype-ps) +[Set-CsIPPhonePolicy](https://learn.microsoft.com/powershell/module/skype/set-csipphonepolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsImConfiguration.md b/skype/skype-ps/skype/Get-CsImConfiguration.md index 652be83696..b174055e0f 100644 --- a/skype/skype-ps/skype/Get-CsImConfiguration.md +++ b/skype/skype-ps/skype/Get-CsImConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csimconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csimconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsImConfiguration schema: 2.0.0 @@ -122,8 +122,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[New-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/new-csimconfiguration?view=skype-ps) +[New-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/new-csimconfiguration?view=skype-ps) -[Set-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/set-csimconfiguration?view=skype-ps) +[Set-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/set-csimconfiguration?view=skype-ps) -[Remove-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/remove-csimconfiguration?view=skype-ps) +[Remove-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/remove-csimconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsImFilterConfiguration.md b/skype/skype-ps/skype/Get-CsImFilterConfiguration.md index 251885957e..fec8ca39e9 100644 --- a/skype/skype-ps/skype/Get-CsImFilterConfiguration.md +++ b/skype/skype-ps/skype/Get-CsImFilterConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csimfilterconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csimfilterconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsImFilterConfiguration schema: 2.0.0 manager: bulenteg @@ -145,26 +145,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -189,4 +169,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsImFilterConfiguration](Remove-CsImFilterConfiguration.md) [Set-CsImFilterConfiguration](Set-CsImFilterConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsImTranslationConfiguration.md b/skype/skype-ps/skype/Get-CsImTranslationConfiguration.md index 2a1467f531..4c07855098 100644 --- a/skype/skype-ps/skype/Get-CsImTranslationConfiguration.md +++ b/skype/skype-ps/skype/Get-CsImTranslationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csimtranslationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csimtranslationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsImTranslationConfiguration schema: 2.0.0 @@ -100,4 +100,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md b/skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md deleted file mode 100644 index de6a5155e8..0000000000 --- a/skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csinboundblockednumberpattern -applicable: Skype for Business Online -title: Get-CsInboundBlockedNumberPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# Get-CsInboundBlockedNumberPattern - -## SYNOPSIS -Returns a list of all blocked number patterns added to the tenant list. - -## SYNTAX - -### Identity (Default) -``` -Get-CsInboundBlockedNumberPattern [-Tenant <Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] - [-LocalStore] [-AsJob] [<CommonParameters>] -``` - -### Filter -``` -Get-CsInboundBlockedNumberPattern [-Tenant <Guid>] [-Filter <String>] [-LocalStore] -[-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet returns a list of all blocked number patterns added to the tenant list including Name, Description, Enabled (True/False), and Pattern for each. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Get-CsInboundBlockedNumberPattern -``` - -In the preceding example, the *Get-CsInboundBlockedNumberPattern* cmdlet is called without any parameters in order to return all the blocked number patterns. - -## PARAMETERS - -### -Filter -Enables you to limit the returned data by filtering on Skype for Business Online-specific attributes. The Filter parameter uses the same Windows PowerShell filtering syntax that is used by the Where-Object cmdlet. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the blocked number patterns to return. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the *AsJob* parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the *Receive-Job* cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS - -[New-CsInboundBlockedNumberPattern](New-CsInboundBlockedNumberPattern.md) - -[Set-CsInboundBlockedNumberPattern](Set-CsInboundBlockedNumberPattern.md) - -[Remove-CsInboundBlockedNumberPattern](Remove-CsInboundBlockedNumberPattern.md) diff --git a/skype/skype-ps/skype/Get-CsKerberosAccountAssignment.md b/skype/skype-ps/skype/Get-CsKerberosAccountAssignment.md index ad6478ba07..769b89632e 100644 --- a/skype/skype-ps/skype/Get-CsKerberosAccountAssignment.md +++ b/skype/skype-ps/skype/Get-CsKerberosAccountAssignment.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cskerberosaccountassignment +online version: https://learn.microsoft.com/powershell/module/skype/get-cskerberosaccountassignment applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsKerberosAccountAssignment schema: 2.0.0 @@ -160,4 +160,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsKerberosAccountAssignment](Remove-CsKerberosAccountAssignment.md) [Set-CsKerberosAccountAssignment](Set-CsKerberosAccountAssignment.md) - diff --git a/skype/skype-ps/skype/Get-CsLisCivicAddress.md b/skype/skype-ps/skype/Get-CsLisCivicAddress.md index d3edd240cf..c1fd4ffdb0 100644 --- a/skype/skype-ps/skype/Get-CsLisCivicAddress.md +++ b/skype/skype-ps/skype/Get-CsLisCivicAddress.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csliscivicaddress +online version: https://learn.microsoft.com/powershell/module/skype/get-csliscivicaddress applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLisCivicAddress schema: 2.0.0 @@ -87,4 +87,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Test-CsLisCivicAddress](Test-CsLisCivicAddress.md) [Get-CsLisLocation](Get-CsLisLocation.md) - diff --git a/skype/skype-ps/skype/Get-CsLisLocation.md b/skype/skype-ps/skype/Get-CsLisLocation.md index 118b8e57a7..7b91277e0f 100644 --- a/skype/skype-ps/skype/Get-CsLisLocation.md +++ b/skype/skype-ps/skype/Get-CsLisLocation.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cslislocation +online version: https://learn.microsoft.com/powershell/module/skype/get-cslislocation applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLisLocation schema: 2.0.0 @@ -104,4 +104,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsLisLocation](Set-CsLisLocation.md) [Get-CsLisCivicAddress](Get-CsLisCivicAddress.md) - diff --git a/skype/skype-ps/skype/Get-CsLisPort.md b/skype/skype-ps/skype/Get-CsLisPort.md index d179ac13e0..3eec392209 100644 --- a/skype/skype-ps/skype/Get-CsLisPort.md +++ b/skype/skype-ps/skype/Get-CsLisPort.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cslisport +online version: https://learn.microsoft.com/powershell/module/skype/get-cslisport applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLisPort schema: 2.0.0 @@ -80,4 +80,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsLisPort](Remove-CsLisPort.md) [Set-CsLisPort](Set-CsLisPort.md) - diff --git a/skype/skype-ps/skype/Get-CsLisServiceProvider.md b/skype/skype-ps/skype/Get-CsLisServiceProvider.md index e5656ec794..2efdc5c58d 100644 --- a/skype/skype-ps/skype/Get-CsLisServiceProvider.md +++ b/skype/skype-ps/skype/Get-CsLisServiceProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cslisserviceprovider +online version: https://learn.microsoft.com/powershell/module/skype/get-cslisserviceprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLisServiceProvider schema: 2.0.0 @@ -63,4 +63,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsLisServiceProvider](Remove-CsLisServiceProvider.md) [Set-CsLisServiceProvider](Set-CsLisServiceProvider.md) - diff --git a/skype/skype-ps/skype/Get-CsLisSubnet.md b/skype/skype-ps/skype/Get-CsLisSubnet.md index ccb98a2b90..070908d63a 100644 --- a/skype/skype-ps/skype/Get-CsLisSubnet.md +++ b/skype/skype-ps/skype/Get-CsLisSubnet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cslissubnet +online version: https://learn.microsoft.com/powershell/module/skype/get-cslissubnet applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLisSubnet schema: 2.0.0 @@ -80,4 +80,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsLisSubnet](Remove-CsLisSubnet.md) [Set-CsLisSubnet](Set-CsLisSubnet.md) - diff --git a/skype/skype-ps/skype/Get-CsLisSwitch.md b/skype/skype-ps/skype/Get-CsLisSwitch.md index 1a8ad2aad3..b4fbab5b8d 100644 --- a/skype/skype-ps/skype/Get-CsLisSwitch.md +++ b/skype/skype-ps/skype/Get-CsLisSwitch.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cslisswitch +online version: https://learn.microsoft.com/powershell/module/skype/get-cslisswitch applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLisSwitch schema: 2.0.0 @@ -91,4 +91,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsLisSwitch](Remove-CsLisSwitch.md) [Set-CsLisSwitch](Set-CsLisSwitch.md) - diff --git a/skype/skype-ps/skype/Get-CsLisWirelessAccessPoint.md b/skype/skype-ps/skype/Get-CsLisWirelessAccessPoint.md index d9c6a1f2ed..469f7a2244 100644 --- a/skype/skype-ps/skype/Get-CsLisWirelessAccessPoint.md +++ b/skype/skype-ps/skype/Get-CsLisWirelessAccessPoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csliswirelessaccesspoint +online version: https://learn.microsoft.com/powershell/module/skype/get-csliswirelessaccesspoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLisWirelessAccessPoint schema: 2.0.0 @@ -91,4 +91,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsLisWirelessAccessPoint](Remove-CsLisWirelessAccessPoint.md) [Set-CsLisWirelessAccessPoint](Set-CsLisWirelessAccessPoint.md) - diff --git a/skype/skype-ps/skype/Get-CsLocationPolicy.md b/skype/skype-ps/skype/Get-CsLocationPolicy.md index fa76512bfa..06e3d908b0 100644 --- a/skype/skype-ps/skype/Get-CsLocationPolicy.md +++ b/skype/skype-ps/skype/Get-CsLocationPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cslocationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-cslocationpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsLocationPolicy schema: 2.0.0 @@ -178,4 +178,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Grant-CsLocationPolicy](Grant-CsLocationPolicy.md) [Test-CsLocationPolicy](Test-CsLocationPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsManagementConnection.md b/skype/skype-ps/skype/Get-CsManagementConnection.md index cc4108667c..be0b6e4a2d 100644 --- a/skype/skype-ps/skype/Get-CsManagementConnection.md +++ b/skype/skype-ps/skype/Get-CsManagementConnection.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmanagementconnection +online version: https://learn.microsoft.com/powershell/module/skype/get-csmanagementconnection applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsManagementConnection schema: 2.0.0 @@ -82,4 +82,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsManagementConnection](Remove-CsManagementConnection.md) [Set-CsManagementConnection](Set-CsManagementConnection.md) - diff --git a/skype/skype-ps/skype/Get-CsManagementStoreReplicationStatus.md b/skype/skype-ps/skype/Get-CsManagementStoreReplicationStatus.md index dd365e6590..a9c3ebe4b8 100644 --- a/skype/skype-ps/skype/Get-CsManagementStoreReplicationStatus.md +++ b/skype/skype-ps/skype/Get-CsManagementStoreReplicationStatus.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmanagementstorereplicationstatus +online version: https://learn.microsoft.com/powershell/module/skype/get-csmanagementstorereplicationstatus applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsManagementStoreReplicationStatus schema: 2.0.0 @@ -146,4 +146,3 @@ If the CentralManagementStoreStatus parameter is used, then the cmdlet returns i ## RELATED LINKS [Invoke-CsManagementStoreReplication](Invoke-CsManagementStoreReplication.md) - diff --git a/skype/skype-ps/skype/Get-CsMcxConfiguration.md b/skype/skype-ps/skype/Get-CsMcxConfiguration.md index bbff6fa655..8a44cb988e 100644 --- a/skype/skype-ps/skype/Get-CsMcxConfiguration.md +++ b/skype/skype-ps/skype/Get-CsMcxConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmcxconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csmcxconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsMcxConfiguration schema: 2.0.0 manager: rogupta @@ -177,4 +177,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsMediaConfiguration.md b/skype/skype-ps/skype/Get-CsMediaConfiguration.md index 5faee1ec16..226f87551c 100644 --- a/skype/skype-ps/skype/Get-CsMediaConfiguration.md +++ b/skype/skype-ps/skype/Get-CsMediaConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmediaconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csmediaconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsMediaConfiguration schema: 2.0.0 @@ -151,4 +151,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsMediaConfiguration](Remove-CsMediaConfiguration.md) [Set-CsMediaConfiguration](Set-CsMediaConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsMeetingConfiguration.md b/skype/skype-ps/skype/Get-CsMeetingConfiguration.md index 5e93ca2ae5..431f2547ca 100644 --- a/skype/skype-ps/skype/Get-CsMeetingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsMeetingConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmeetingconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csmeetingconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsMeetingConfiguration schema: 2.0.0 author: tomkau @@ -10,7 +10,7 @@ ms.reviewer: rogupta manager: bulenteg audience: ITPro ms.topic: reference -localization_priority: Normal +ms.localizationpriority: medium --- # Get-CsMeetingConfiguration @@ -188,22 +188,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -228,4 +212,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsMeetingConfiguration](Remove-CsMeetingConfiguration.md) [Set-CsMeetingConfiguration](Set-CsMeetingConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsMeetingMigrationStatus.md b/skype/skype-ps/skype/Get-CsMeetingMigrationStatus.md deleted file mode 100644 index 6461dfe4c4..0000000000 --- a/skype/skype-ps/skype/Get-CsMeetingMigrationStatus.md +++ /dev/null @@ -1,222 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmeetingmigrationstatus -applicable: Skype for Business Online -title: Get-CsMeetingMigrationStatus -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsMeetingMigrationStatus - -## SYNOPSIS -You use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations. - -## SYNTAX -``` -Get-CsMeetingMigrationStatus [[-Identity] <UserIdParameter>] [-Confirm] [-EndTime <DateTime>] [-StartTime <DateTime>] - [-SummaryOnly] [-Tenant <Guid>] [-WhatIf] [-AsJob] [-State <StateType>] [<CommonParameters>] -``` - -## DESCRIPTION -Meeting Migration Service (MMS) is a Skype for Business service that runs in the background and automatically updates Skype for Business and Microsoft Teams meetings for users. MMS is designed to eliminate the need for users to run the Meeting Migration Tool to update their Skype for Business and Microsoft Teams meetings. - -You can use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsMeetingMigrationStatus -SummaryOnly -``` - -This example is used to get a summary status of all MMS migrations. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsMeetingMigrationStatus -Identity "ashaw@contoso.com" -``` - -This example gets the meeting migration status for user ashaw@contoso.com. - - -## PARAMETERS - -### -Identity -Specifies the Identity of the user account to be to be modified. A user identity can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartTime -Specifies the start date of the date range. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EndTime -Specifies the end date of the date range. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SummaryOnly -Specified that you want a summary status of MMS migrations returned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -State -With this parameter you can filter by migration state. Possible values are: -* Pending -* InProgress -* Failed -* Succeeded - -```yaml -Type: StateType -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Get-CsTenantMigrationConfiguration](https://docs.microsoft.com/powershell/module/skype/get-cstenantmigrationconfiguration?view=skype-ps) - -[Get-CsOnlineDialInConferencingTenantSettings](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingtenantsettings?view=skype-ps) - -[Start-CsExMeetingMigration](https://docs.microsoft.com/powershell/module/skype/start-csexmeetingmigration?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsMeetingRoom.md b/skype/skype-ps/skype/Get-CsMeetingRoom.md index 762c073cae..4401dd0254 100644 --- a/skype/skype-ps/skype/Get-CsMeetingRoom.md +++ b/skype/skype-ps/skype/Get-CsMeetingRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmeetingroom -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csmeetingroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsMeetingRoom schema: 2.0.0 manager: bulenteg @@ -18,12 +18,15 @@ A meeting room is a conferencing device designed to address video conferencing a This cmdlet was introduced in Lync Server 2013. +**Note**: This cmdlet is not supported for managing Microsoft Teams Rooms. You must use the methods described in the [Microsoft Teams Rooms](/microsoftteams/rooms) documentation to manage Microsoft Teams Rooms. + + ## SYNTAX ``` Get-CsMeetingRoom [[-Identity] <UserIdParameter>] [-Credential <PSCredential>] [-DomainController <Fqdn>] [-Filter <String>] [-LdapFilter <String>] [-OU <OUIdParameter>] - [-ResultSize <Microsoft.Rtc.Management.ADConnect.Core.Unlimited`1[System.UInt32]>] [-AsJob] + [-ResultSize <Microsoft.Rtc.Management.ADConnect.Core.Unlimited`1[System.UInt32]>] [<CommonParameters>] ``` @@ -221,22 +224,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -264,4 +251,3 @@ The Get-CsMeetingRoom cmdlet accepts a pipelined string value representing the I [Move-CsMeetingRoom](Move-CsMeetingRoom.md) [Set-CsMeetingRoom](Set-CsMeetingRoom.md) - diff --git a/skype/skype-ps/skype/Get-CsMobilityPolicy.md b/skype/skype-ps/skype/Get-CsMobilityPolicy.md index 65bc67e815..c59665485e 100644 --- a/skype/skype-ps/skype/Get-CsMobilityPolicy.md +++ b/skype/skype-ps/skype/Get-CsMobilityPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csmobilitypolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csmobilitypolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsMobilityPolicy schema: 2.0.0 manager: bulenteg @@ -204,22 +204,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -238,4 +222,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsNetworkBandwidthPolicyProfile.md b/skype/skype-ps/skype/Get-CsNetworkBandwidthPolicyProfile.md index e3bb67dcbb..de1572dc01 100644 --- a/skype/skype-ps/skype/Get-CsNetworkBandwidthPolicyProfile.md +++ b/skype/skype-ps/skype/Get-CsNetworkBandwidthPolicyProfile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworkbandwidthpolicyprofile +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworkbandwidthpolicyprofile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkBandwidthPolicyProfile schema: 2.0.0 @@ -137,4 +137,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsNetworkBandwidthPolicyProfile](Remove-CsNetworkBandwidthPolicyProfile.md) [Set-CsNetworkBandwidthPolicyProfile](Set-CsNetworkBandwidthPolicyProfile.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkConfiguration.md b/skype/skype-ps/skype/Get-CsNetworkConfiguration.md index 8055469241..5914281385 100644 --- a/skype/skype-ps/skype/Get-CsNetworkConfiguration.md +++ b/skype/skype-ps/skype/Get-CsNetworkConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworkconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworkconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkConfiguration schema: 2.0.0 manager: bulenteg @@ -122,22 +122,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -174,4 +158,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Get-CsNetworkSubnet](Get-CsNetworkSubnet.md) [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkInterRegionRoute.md b/skype/skype-ps/skype/Get-CsNetworkInterRegionRoute.md index 94ff58e532..c65e85e16f 100644 --- a/skype/skype-ps/skype/Get-CsNetworkInterRegionRoute.md +++ b/skype/skype-ps/skype/Get-CsNetworkInterRegionRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworkinterregionroute +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworkinterregionroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkInterRegionRoute schema: 2.0.0 @@ -151,4 +151,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsNetworkInterRegionRoute](Remove-CsNetworkInterRegionRoute.md) [Set-CsNetworkInterRegionRoute](Set-CsNetworkInterRegionRoute.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkInterSitePolicy.md b/skype/skype-ps/skype/Get-CsNetworkInterSitePolicy.md index ad00407757..447ed6ca95 100644 --- a/skype/skype-ps/skype/Get-CsNetworkInterSitePolicy.md +++ b/skype/skype-ps/skype/Get-CsNetworkInterSitePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworkintersitepolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworkintersitepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkInterSitePolicy schema: 2.0.0 @@ -153,4 +153,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsNetworkInterSitePolicy](Remove-CsNetworkInterSitePolicy.md) [Set-CsNetworkInterSitePolicy](Set-CsNetworkInterSitePolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkInterface.md b/skype/skype-ps/skype/Get-CsNetworkInterface.md index d196803f0d..cce4863773 100644 --- a/skype/skype-ps/skype/Get-CsNetworkInterface.md +++ b/skype/skype-ps/skype/Get-CsNetworkInterface.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworkinterface +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworkinterface applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkInterface schema: 2.0.0 @@ -181,4 +181,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Get-CsComputer](Get-CsComputer.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkRegion.md b/skype/skype-ps/skype/Get-CsNetworkRegion.md index d1e4f4c941..bac9faa045 100644 --- a/skype/skype-ps/skype/Get-CsNetworkRegion.md +++ b/skype/skype-ps/skype/Get-CsNetworkRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworkregion +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworkregion applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkRegion schema: 2.0.0 @@ -148,4 +148,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsNetworkRegion](Remove-CsNetworkRegion.md) [Set-CsNetworkRegion](Set-CsNetworkRegion.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkRegionLink.md b/skype/skype-ps/skype/Get-CsNetworkRegionLink.md index 152773167c..9c7f1775f6 100644 --- a/skype/skype-ps/skype/Get-CsNetworkRegionLink.md +++ b/skype/skype-ps/skype/Get-CsNetworkRegionLink.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworkregionlink +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworkregionlink applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkRegionLink schema: 2.0.0 @@ -149,4 +149,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsNetworkRegionLink](Remove-CsNetworkRegionLink.md) [Set-CsNetworkRegionLink](Set-CsNetworkRegionLink.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkSite.md b/skype/skype-ps/skype/Get-CsNetworkSite.md index 3c0216e8b2..63eaeaaf8c 100644 --- a/skype/skype-ps/skype/Get-CsNetworkSite.md +++ b/skype/skype-ps/skype/Get-CsNetworkSite.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworksite +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworksite applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkSite schema: 2.0.0 @@ -148,4 +148,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsNetworkSite](Remove-CsNetworkSite.md) [Set-CsNetworkSite](Set-CsNetworkSite.md) - diff --git a/skype/skype-ps/skype/Get-CsNetworkSubnet.md b/skype/skype-ps/skype/Get-CsNetworkSubnet.md index 1c91000ae2..aca38d63a4 100644 --- a/skype/skype-ps/skype/Get-CsNetworkSubnet.md +++ b/skype/skype-ps/skype/Get-CsNetworkSubnet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csnetworksubnet +online version: https://learn.microsoft.com/powershell/module/skype/get-csnetworksubnet applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsNetworkSubnet schema: 2.0.0 @@ -145,4 +145,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsNetworkSubnet](Remove-CsNetworkSubnet.md) [Set-CsNetworkSubnet](Set-CsNetworkSubnet.md) - diff --git a/skype/skype-ps/skype/Get-CsOAuthConfiguration.md b/skype/skype-ps/skype/Get-CsOAuthConfiguration.md index 31edf8192e..b2c5cfbfdd 100644 --- a/skype/skype-ps/skype/Get-CsOAuthConfiguration.md +++ b/skype/skype-ps/skype/Get-CsOAuthConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csoauthconfiguration -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csoauthconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsOAuthConfiguration schema: 2.0.0 manager: bulenteg @@ -22,12 +22,12 @@ This cmdlet was introduced in Lync Server 2013. ### Identity (Default) ``` -Get-CsOAuthConfiguration [[-Identity] <XdsIdentity>] [-LocalStore] [-Tenant <Guid>] [-AsJob] [<CommonParameters>] +Get-CsOAuthConfiguration [[-Identity] <XdsIdentity>] [-LocalStore] [-Tenant <Guid>] [<CommonParameters>] ``` ### Filter ``` -Get-CsOAuthConfiguration [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [-AsJob] [<CommonParameters>] +Get-CsOAuthConfiguration [-Filter <String>] [-LocalStore] [-Tenant <Guid>] [<CommonParameters>] ``` @@ -137,26 +137,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -176,4 +156,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsOAuthConfiguration](Set-CsOAuthConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsOAuthServer.md b/skype/skype-ps/skype/Get-CsOAuthServer.md index 26e05dc09b..d8186132f4 100644 --- a/skype/skype-ps/skype/Get-CsOAuthServer.md +++ b/skype/skype-ps/skype/Get-CsOAuthServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csoauthserver +online version: https://learn.microsoft.com/powershell/module/skype/get-csoauthserver applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsOAuthServer schema: 2.0.0 @@ -165,4 +165,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsOAuthServer](Remove-CsOAuthServer.md) [Set-CsOAuthServer](Set-CsOAuthServer.md) - diff --git a/skype/skype-ps/skype/Get-CsOnlineApplicationEndpoint.md b/skype/skype-ps/skype/Get-CsOnlineApplicationEndpoint.md deleted file mode 100644 index ad973f9eb8..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineApplicationEndpoint.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineapplicationendpoint -applicable: Skype for Business Online -title: Get-CsOnlineApplicationEndpoint -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineApplicationEndpoint - -## SYNOPSIS -It is used to fetch the application endpoints for a tenant. - -## SYNTAX - -``` -Get-CsOnlineApplicationEndpoint [-Uri] <String> [-PhoneNumber <String>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to fetch the application endpoints for a tenant. - -## EXAMPLES - -### Example 1 -``` -Get-CsOnlineApplicationEndpoint -Uri "sip:sample@domain.com" -``` - -This example retrieves information about the specified application endpoint. - -## PARAMETERS - -### -Uri -Sip Uri that identifies the tenant specific endpoint for the application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: SipUri - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneNumber -The service number assigned to the trusted application endpoint. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/set-csonlineapplicationendpoint) - -[New-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/new-csonlineapplicationendpoint) - -[Remove-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/remove-csonlineapplicationendpoint) - -[Set up a Trusted Application Endpoint](https://docs.microsoft.com/skype-sdk/trusted-application-api/docs/trustedapplicationendpoint) diff --git a/skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md b/skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md deleted file mode 100644 index d4238eebac..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineapplicationinstance -applicable: Skype for Business Online -title: Get-CsOnlineApplicationInstance -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineApplicationInstance - -## SYNOPSIS -Get application instance for the tenant from Azure Active Directory. - -## SYNTAX - -``` -Get-CsOnlineApplicationInstance [[-Identity] <string>] [[-ResultSize] <int>] [-Tenant <guid>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to get details of an application instance. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Get-CsOnlineApplicationInstance -Identity appinstance01@contoso.com -``` - -This example returns the application instance with identity "appinstance01@contoso.com". - -### -------------------------- Example 2 -------------------------- -```powershell -Get-CsOnlineApplicationInstance -ResultSize 10 -``` - -This example returns the first 10 application instances. - -### -------------------------- Example 3 -------------------------- -```powershell -Get-CsOnlineApplicationInstance -``` - -This example returns the details of all application instances. - -## PARAMETERS - -### -Identity -The URI or the object ID of the application instance to retrieve. If this parameter is not provided, it will retrieve all application instances in the tenant. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -The result size for bulk get. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -The Tenant ID. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsOnlineApplicationInstanceAssociation.md b/skype/skype-ps/skype/Get-CsOnlineApplicationInstanceAssociation.md deleted file mode 100644 index 40ba7d0249..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineApplicationInstanceAssociation.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineapplicationinstanceassociation -applicable: Skype for Business Online -title: Get-CsOnlineApplicationInstanceAssociation -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineApplicationInstanceAssociation - -## SYNOPSIS -Use the Get-CsOnlineApplicationInstanceAssociation cmdlet to get information about the associations setup in your organization. - -## SYNTAX - -``` -Get-CsOnlineApplicationInstanceAssociation -Identity <String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-CsOnlineApplicationInstanceAssociation cmdlet to get information about the associations setup between online application instances and the application configurations, like auto attendants and call queues. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Get-CsOnlineApplicationInstanceAssociation -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -``` - -This example gets the association object for the application instance that has the identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. - -## PARAMETERS - -### -Identity -The identity for the application instance whose association is to be retrieved. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### System.String -The Get-CsOnlineApplicationInstanceAssociation cmdlet accepts a string as the Identity parameter. - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.ApplicationInstanceAssociation - - -## NOTES - - -## RELATED LINKS - -[Get-CsOnlineApplicationInstanceAssociationStatus](Get-CsOnlineApplicationInstanceAssociationStatus.md) - -[New-CsOnlineApplicationInstanceAssociation](New-CsOnlineApplicationInstanceAssociation.md) - -[Remove-CsOnlineApplicationInstanceAssociation](Remove-CsOnlineApplicationInstanceAssociation.md) diff --git a/skype/skype-ps/skype/Get-CsOnlineApplicationInstanceAssociationStatus.md b/skype/skype-ps/skype/Get-CsOnlineApplicationInstanceAssociationStatus.md deleted file mode 100644 index 63fb79a975..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineApplicationInstanceAssociationStatus.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineapplicationinstanceassociationstatus -applicable: Skype for Business Online -title: Get-CsOnlineApplicationInstanceAssociationStatus -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineApplicationInstanceAssociationStatus - -## SYNOPSIS -Use the Get-CsOnlineApplicationInstanceAssociationStatus cmdlet to get the provisioning status for the associations you have setup in your organization. - -## SYNTAX - -``` -Get-CsOnlineApplicationInstanceAssociationStatus -Identity <String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Get-CsOnlineApplicationInstanceAssociationStatus cmdlet to get provisioning status for the associations you have setup between online application instances and the application configurations, like auto attendants and call queues. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Get-CsOnlineApplicationInstanceAssociationStatus -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -``` - -This example gets the provisioning status for the association object of the application instance that has the identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. - -## PARAMETERS - -### -Identity -The identity for the application instance whose association provisioning status is to be retrieved. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### System.String -The Get-CsOnlineApplicationInstanceAssociationStatus cmdlet accepts a string as the Identity parameter. - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.StatusRecord - - -## NOTES - - -## RELATED LINKS - -[Get-CsOnlineApplicationInstanceAssociation](Get-CsOnlineApplicationInstanceAssociation.md) - -[New-CsOnlineApplicationInstanceAssociation](New-CsOnlineApplicationInstanceAssociation.md) - -[Remove-CsOnlineApplicationInstanceAssociation](Remove-CsOnlineApplicationInstanceAssociation.md) diff --git a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingLanguagesSupported.md b/skype/skype-ps/skype/Get-CsOnlineDialInConferencingLanguagesSupported.md deleted file mode 100644 index acbb382545..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingLanguagesSupported.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinglanguagessupported -applicable: Skype for Business Online -title: Get-CsOnlineDialInConferencingLanguagesSupported -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialInConferencingLanguagesSupported - -## SYNOPSIS -Use the Get-CsOnlineDialInConferencingLanguagesSupported cmdlet to view the list of languages that are supported when an organization uses Microsoft as the dial-in audio conferencing provider. - -## SYNTAX - -``` -Get-CsOnlineDialInConferencingLanguagesSupported [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOnlineDialInConferencingLanguagesSupported cmdlet is used to view the primary and secondary languages that are set for a dial-in conferencing service number. -There is a primary language that is set along with secondary languages (up to 4) that can also be set. - -Primary and secondary languages are those languages that are used to play prompts when a caller calls into a dial-in service number. -When no languages are specified for a dial-in service number it will get the set of default languages. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Get-CsOnlineDialInConferencingLanguagesSupported | fl -``` - -This example allows returns the list of supported languages when you are using Microsoft as your dial-in audio conferencing provider and displays them in a formatted list. - - - -## PARAMETERS - -### -DomainController -Specifies the domain controller that's used by the cmdlet to read or write the specified data. -Valid inputs for this parameter include: - -Fully qualified domain name (FQDN): `-DomainController atl-cs-001.Contoso.com` - -Computer name: `-DomainController atl-cs-001` - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingTenantSettings.md b/skype/skype-ps/skype/Get-CsOnlineDialInConferencingTenantSettings.md deleted file mode 100644 index d7c40382d3..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingTenantSettings.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingtenantsettings -applicable: Skype for Business Online -title: Get-CsOnlineDialInConferencingTenantSettings -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialInConferencingTenantSettings - -## SYNOPSIS -Use the Get-CsOnlineDialInConferencingTenantSettings cmdlet to retrieve tenant level settings for dial-in conferencing. - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlineDialInConferencingTenantSettings [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlineDialInConferencingTenantSettings [-Tenant <Guid>] [-Filter <String>] [-LocalStore] - [<CommonParameters>] -``` - -## DESCRIPTION - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineDialInConferencingTenantSettings -``` - -This example returns the global setting for the tenant administrator's organization. - - -## PARAMETERS - -### -Filter -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -Retrieves the settings from the local replica of the Central Management store rather than from the Central Management store itself. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.WritableConfig.Settings.OnLineDialInConferencing.OnLineDialInConferencingTenantSettings - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUser.md b/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUser.md deleted file mode 100644 index 0a0f1ca9cf..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUser.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinguser -applicable: Skype for Business Online -title: Get-CsOnlineDialInConferencingUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialInConferencingUser - -## SYNOPSIS -Use the `Get-CsOnlineDialInConferencingUser` cmdlet to view the properties and settings of users that are enabled for dial-in conferencing and are using Microsoft as their PSTN conferencing provider. - -## SYNTAX - -``` -Get-CsOnlineDialInConferencingUser [-BridgeName <String>] [-ServiceNumber <String>] [-TenantDomain <String>] - [-LdapFilter <String>] [[-Identity] <UserIdParameter>] [-Tenant <Guid>] [-BridgeId <Guid>] [-ResultSize <Int32>] - [-DomainController <Fqdn>] [-Force] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet will only return users that have been enabled for audio conferencing using Microsoft as the audio conferencing provider. -Users that are enabled for audio conferencing using a third-party audio conferencing provider won't be returned. -If there are no users in the organization that have been enabled for audio conferencing, then the cmdlet will return no results. - -The see a list of users with conferencing providers other than Microsoft use the Get-CsUserAcp cmdlet. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Get-CsOnlineDialInConferencingUser -LdapFilter "Department=Finance" -``` - -This example uses the LdapFilter parameter to limit the returned data to users who work in the Finance department. - -### -------------------------- Example 2 -------------------------- -```powershell -Get-CsOnlineDialInConferencingUser -ServiceNumber +14255034412 | Format-Table -Property DisplayName, SipAddress -``` - -This example returns users who have been enabled for audio conferencing provided by Microsoft, and are assigned to the specified service number. - -By default, the Get-CsOnlineDialInConferencingUser cmdlet returns a large number of properties. -Therefore, in this example the retrieved data is piped to the Format-Table cmdlet. -The Format-Table cmdlet then uses the Property parameter to select the properties DisplayName and SipAddress. - - -## PARAMETERS - -### -BridgeId -Specifies the globally-unique identifier (GUID) for the audio conferencing bridge. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BridgeName -Specifies the name for the audio conferencing bridge. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the user to retrieve. -The user can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). -You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceNumber -Specifies a service number to serve as a filter for the returned user collection. -Only users who have been assigned the specified number will be returned. -The service number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LdapFilter -Enables you to limit the returned data by filtering on generic Active Directory attributes (that is, attributes that are not specific to Skype for Business Server 2015). -For example, you can limit returned data to users who work in a specific department, or users who have a specified manager or job title. -The LdapFilter parameter uses the LDAP query language when creating filters. -For example, a filter that returns only users who work in the city of Redmond would look like this: "l=Redmond", with "l" (a lowercase L) representing the Active Directory attribute (locality); "=" representing the comparison operator (equal to); and "Redmond" representing the filter value. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -Enables you to limit the number of records returned by the cmdlet. -For example, to return seven users (regardless of the number of users that are in your forest) include the ResultSize parameter and set the parameter value to 7. -Note that there is no way to guarantee which seven users will be returned. -The result size can be set to any whole number between 0 and 2147483647, inclusive. -If set to 0 the command will run, but no data will be returned. -If you set the ResultSize to 7 but you have only three users in your forest, the command will return those three users, and then complete without error. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -NOTE: This parameter is reserved for internal Microsoft use. - -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308". -You can find your tenant ID by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantDomain -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Enable-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/enable-csonlinedialinconferencinguser?view=skype-ps) - -[Disable-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/disable-csonlinedialinconferencinguser?view=skype-ps) - -[Set-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencinguser?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUserInfo.md b/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUserInfo.md deleted file mode 100644 index 0b8875c011..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUserInfo.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinguserinfo -applicable: Skype for Business Online -title: Get-CsOnlineDialInConferencingUserInfo -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialInConferencingUserInfo - -## SYNOPSIS -Use the `Get-CsOnlineDialInConferencingUserInfo` cmdlet to view the properties and settings of users that are enabled for dial-in conferencing and are using Microsoft or third-party provider as their PSTN conferencing provider. - -## SYNTAX - -### IdentityParams -``` -Get-CsOnlineDialInConferencingUserInfo [-Identity] <UserIdParameter> [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -### TenantIdParams -``` -Get-CsOnlineDialInConferencingUserInfo [-Tenant <Guid>] [-Skip <Int32>] [-First <Int32>] - [-SearchQuery <String>] [-Select <FilterSelection>] [-Filter <String>] [-SortDescending] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet will return users that have been enabled for audio conferencing using Microsoft or a third-party as the audio conferencing provider. If there are no users in the organization that have been enabled for audio conferencing, then the cmdlet will return no results. - -You can use [Get-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinguser?view=skype-ps) cmdlet to return only users that have been enabled for audio conferencing using Microsoft as the audio conferencing provider. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineDialInConferencingUserInfo -Filter {Provider -eq "InterCall"} -First 10 -``` - -This example returns users who have been enabled for audio conferencing provided by InterCall, but it will show only the first 10 users. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineDialInConferencingUserInfo -Select ConferencingProviderOther -``` - -This example returns users who have been enabled for audio conferencing provided by other than Microsoft. - -## PARAMETERS - -### -Identity -Specifies the user to retrieve. The user can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -Enables you to limit the returned data by filtering on Skype for Business specific attributes. For example, you can limit returned data to users who have been assigned a specific third-party provider. - -The Filter parameter uses the same filtering syntax that is used by the Where-Object cmdlet. For example, a filter that returns only users who have InterCall as Audio Conferencing Provider, with Provider representing the attribute, and -eq representing the comparison operator (equal to): - -{Provider -eq "InterCall"} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -First -When present, the cmdlet returns the first X number of users from the list of all the users enabled for dial-in conferencing. -If this parameter is not specified, the default behavior is to return the first 100 number of users. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchQuery -The SearchQuery parameter specifies a search string or a query formatted using Keyword Query Language (KQL). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Select -Use next values to filter the output: -* DialInConferencingOn: Display all the users who are enabled for dial-in conferencing. -* DialInConferencingOff: Display all the users who are not enabled for dial-in conferencing. -* ConferencingProviderMS: Display all the users who are CPC enabled. -* ConferencingProviderOther: Display all the users who have 3rd party ACP. -* ReadyForMigrationToCPC: Display all the users who have 3rd party ACP and have been assigned a CPC license. -* NoFilter: Display all the users. - -```yaml -Type: FilterSelection -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Skip -Skips (does not select) the specified number of items. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SortDescending -Indicates that the cmdlet sorts the objects in descending order. The default is ascending order. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Get-CsOnlineDialInConferencingUser](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinguser?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUserState.md b/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUserState.md deleted file mode 100644 index e6f794748c..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingUserState.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinguserstate -applicable: Skype for Business Online -title: Get-CsOnlineDialInConferencingUserState -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialInConferencingUserState - -## SYNOPSIS -Use the `Get-CsOnlineDialInConferencingUserState` cmdlet to view the current Dial In Conferencing state of users in your Tenant. - -## SYNTAX - -``` -Get-CsOnlineDialInConferencingUserState [[-Identity] <UserIdParameter>] [-Tenant <Guid>] - [-TenantDomain <String>] [-Provider <ProviderType>] [-LicenseState <String[]>] - [-ResultSize <Unlimited>] [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Use the `Get-CsOnlineDialInConferencingUserState` cmdlet to view the current Dial In Conferencing state of users in your Tenant. - -## EXAMPLES - -### Example 1 -``` -Get-CsOnlineDialInConferencingUserState -``` -Gets the Dial In Conferencing state of every user. - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the user to retrieve. The user can be specified by using the user's SIP address, the user's user principal name (UPN) or the user's display name (for example, Ken Myer). - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -LicenseState -License state of the user, possible values -- NoLicense -- Licensed - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Provider -Audio Conferencing Provider name, possible values -- AllProviders -- NoProviders -- Microsoft -- ThirdParty - -```yaml -Type: ProviderType -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -PARAMVALUE: Unlimited - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantDomain -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsOnlineDialOutPolicy.md b/skype/skype-ps/skype/Get-CsOnlineDialOutPolicy.md deleted file mode 100644 index f68633c185..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialOutPolicy.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialoutpolicy -applicable: Skype for Business Online -title: Get-CsOnlineDialOutPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialOutPolicy - -## SYNOPSIS -Use the `Get-CsOnlineDialOutPolicy` cmdlet to get all the available outbound calling restriction policies in your organization. - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlineDialOutPolicy [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlineDialOutPolicy [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -In Skype for Business Online, outbound calling restriction policies are used to restrict the type of audio conferencing and end user PSTN calls that can be made by users in your organization. -To get all the available policies in your organization run `Get-CSOnlineDialOutPolicy`. -To assign one of these policies to a user run `Grant-CsDialoutPolicy`. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-CSOnlineDialOutPolicy -``` - -In Example 1, `Get-CSOnlineDialOutPolicy` is called without any additional parameters; this returns a collection of all the outbound calling restriction policies configured for use in your organization. - -### Example 2 -```powershell -PS C:\> Get-CSOnlineDialOutPolicy -Identity DialoutCPCandPSTNDisabled -``` - -In Example 2, `Get-CSOnlineDialOutPolicy` is used to return the per-user outbound calling restriction policy that has an Identity DialoutCPCandPSTNDisabled. Because identities are unique, this command will never return more than one item. - -## PARAMETERS - -### -Filter -Enables you to use wildcard characters when indicating the policy (or policies) to be returned. To return a collection of all the per-user policies, use this syntax: -Filter "tag:\*". - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: True -``` - -### -Identity -Unique identifier of the outbound calling restriction policy to be returned. To refer to the global policy, use this syntax: "-Identity Global". To refer to a per-user policy, use syntax similar to this: -Identity DialoutCPCandPSTNDisabled. - -If this parameter is omitted, then all the outbound calling restriction policies configured for use in your tenant will be returned. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Grant-CsDialoutPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csdialoutpolicy) diff --git a/skype/skype-ps/skype/Get-CsOnlineDialinConferencingPolicy.md b/skype/skype-ps/skype/Get-CsOnlineDialinConferencingPolicy.md deleted file mode 100644 index b0d4e3329b..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialinConferencingPolicy.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingpolicy -applicable: Skype for Business Online -title: Get-CsOnlineDialinConferencingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialinConferencingPolicy - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlineDialinConferencingPolicy [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlineDialinConferencingPolicy [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -Filter -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -PARAMVALUE: XdsIdentity - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineDialinConferencingTenantConfiguration.md b/skype/skype-ps/skype/Get-CsOnlineDialinConferencingTenantConfiguration.md deleted file mode 100644 index 8d78715bf0..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDialinConferencingTenantConfiguration.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingtenantconfiguration -applicable: Skype for Business Online -title: Get-CsOnlineDialinConferencingTenantConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDialinConferencingTenantConfiguration - -## SYNOPSIS -Use the Get-CsOnlineDialinConferencingTenantConfiguration cmdlet to retrieve the tenant level configuration for dial-in conferencing. -The dial-in conferencing configuration specifies if dial-in conferencing is enabled for the tenant. - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlineDialinConferencingTenantConfiguration [-Tenant <Guid>] [[-Identity] <XdsIdentity>] - [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlineDialinConferencingTenantConfiguration [-Tenant <Guid>] [-Filter <String>] [-LocalStore] - [<CommonParameters>] -``` - -## DESCRIPTION -The dial-in conferencing configuration specifies only if dial-in conferencing is enabled for the tenant. -By contrast, the dial-in conferencing tenant settings specify what functions are available during a conference call. -For example, whether or not entries and exits from the call are announced. -The settings also manage some of the administrative functions, such as when users get notification of administrative actions, like a PIN change. -For more information on settings and their customization, see Set-CsOnlineDialInConferencingTenantSettings. - -This cmdlet currently displays only the enabled or disabled status of your tenant configuration. -There is one configuration per tenant. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineDialinConferencingTenantConfiguration -``` - -This example returns the configuration for the tenant administrator's organization. - - -## PARAMETERS - -### -Filter -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -Retrieves the configuration from the local replica of the Central Management store rather than from the Central Management store itself. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.WritableConfig.Settings.OnLineDialInConferencing.OnLineDialInConferencingTenantConfiguration - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineDirectoryTenant.md b/skype/skype-ps/skype/Get-CsOnlineDirectoryTenant.md deleted file mode 100644 index 21be47a5fa..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDirectoryTenant.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedirectorytenant -applicable: Skype for Business Online -title: Get-CsOnlineDirectoryTenant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDirectoryTenant - -## SYNOPSIS -Use the Get-CsOnlineDirectoryTenant cmdlet to retrieve a tenant and associated parameters from the Business Voice Directory. - -## SYNTAX -``` -Get-CsOnlineDirectoryTenant [[-Tenant] <Guid>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -The following is an example of the Get-CsOnlineDirectoryTenant cmdlet's console output: - -RunspaceId : 27655c26-8142-4f23-a7a7-0c18303b809f -Id : f71eaa50-9e75-4058-8c39-dba6fdd51b28 -AnnouncementsDisabled : False -NameRecordingDisabled : False -ServiceNumberCount : 0 -SubscriberNumberCount : 0 -DefaultPoolFqdn : -DefaultBridge : ae9ae5d8-c440-4ccd-8960-42792a9bcb0d -Bridges : {Id = [ae9ae5d8-c440-4ccd-8960-42792a9bcb0d], Name = [Conference Bridge], DefaultServiceNumber = [], IsDefaultBridge = [True], IsShared = [False], Region = [NOAM]} -Domains : {} -Pools : {sippoolsn44a06.infra.lync.com} -TnmAccountId : - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineDirectoryTenant -Tenant 7a205197-8e59-487d-b9fa-3fc1b108f1e5 -``` - -This example returns the tenant specified by GUID. - - -## PARAMETERS - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Specifies the domain controller that's used by the cmdlet to read or write the specified data. -Valid inputs for this parameter are either the fully qualified domain name (FQDN) or the computer name. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: - -`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` - -You can find your tenant ID by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - - -## OUTPUTS - -### Deserialized.Microsoft.Rtc.Management.Hosted.Bvd.Types.LacTenant - - -## NOTES - - -## RELATED LINKS - -[Get-CsOnlineTelephoneNumber](Get-CsOnlineTelephoneNumber.md) diff --git a/skype/skype-ps/skype/Get-CsOnlineDirectoryTenantNumberCities.md b/skype/skype-ps/skype/Get-CsOnlineDirectoryTenantNumberCities.md deleted file mode 100644 index 99f9d390b5..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineDirectoryTenantNumberCities.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedirectorytenantnumbercities -applicable: Skype for Business Online -title: Get-CsOnlineDirectoryTenantNumberCities -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineDirectoryTenantNumberCities - -## SYNOPSIS -Use the Get-CsOnlineDirectoryTenantNumberCities cmdlet to retrieve the cities for which telephone numbers have been acquired by your organization. - -## SYNTAX - -``` -Get-CsOnlineDirectoryTenantNumberCities [[-Tenant] <Guid>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet can be used to fetch all the cities for which your organization has already acquired telephone numbers. -It is mainly used to filter cities for which telephone numbers are acquired. - -The console output will be in the form: - -Get-CsOnlineDirectoryTenantNumberCities - -NOAM-US-CA-LA - -NOAM-US-IL-CH - -NOAM-US-NY-NY - -NOAM-US-TX-DA - -NOAM-US-MA-BO - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineDirectoryTenantNumberCities -``` - -This example returns all the cities for which telephone numbers have been acquired by your organization. - - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - - -## OUTPUTS - -### IList<string> containing the geocodes of the relevant cities. - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md b/skype/skype-ps/skype/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md deleted file mode 100644 index 54b3f42d44..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineenhancedemergencyservicedisclaimer -applicable: Skype for Business Online -title: Get-CsOnlineEnhancedEmergencyServiceDisclaimer -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineEnhancedEmergencyServiceDisclaimer - -## SYNOPSIS -Use the Get-CsOnlineEnhancedEmergencyServiceDisclaimer cmdlet to determine whether your organization has accepted the terms and conditions of enhanced emergency service. - -## SYNTAX - -``` -Get-CsOnlineEnhancedEmergencyServiceDisclaimer [-CountryOrRegion <CountryInfo>] [-DomainController <Fqdn>] [-Force] [-Tenant <Guid>] [-Version <String>] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -You can use this cmdlet to determine whether your organization has accepted the terms and conditions of enhanced emergency service. The United States is currently the only country supported. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineEnhancedEmergencyServiceDisclaimer -CountryOrRegion "US" -``` - -This example returns your organization's enhanced emergency service terms and conditions acceptance status. - - -## PARAMETERS - -### -CountryOrRegion -Specifies the region or country whose terms and conditions you wish to verify. -The United States is currently the only country supported, but it must be specified as "US". - -```yaml -Type: CountryInfo -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Version -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - - -## OUTPUTS - -### None - - -## NOTES - - -## RELATED LINKS -[Set-CsOnlineEnhancedEmergencyServiceDisclaimer](https://docs.microsoft.com/powershell/module/skype/set-csonlineenhancedemergencyservicedisclaimer?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineLisCivicAddress.md b/skype/skype-ps/skype/Get-CsOnlineLisCivicAddress.md deleted file mode 100644 index bbfd9fb8fe..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineLisCivicAddress.md +++ /dev/null @@ -1,301 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineliscivicaddress -applicable: Skype for Business Online -title: Get-CsOnlineLisCivicAddress -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# Get-CsOnlineLisCivicAddress - -## SYNOPSIS -Use the Get-CsOnlineLisCivicAddress cmdlet to retrieve information about existing emergency civic addresses defined in the Location Information Service (LIS.) - -## SYNTAX - -``` -Get-CsOnlineLisCivicAddress [-CivicAddressId <Guid>] [-LocationId <Guid>] - [-PopulateNumberOfVoiceUsers] [-PopulateNumberOfTelephoneNumbers] [-AssignmentStatus <String>] - [-City <String>] [-CountryOrRegion <String>] [-Description <String>] [-ValidationStatus <String>] - [-ResultSize <Int32>] [-NumberOfResultsToSkip <Int32>] [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -## DESCRIPTION - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineLisCivicAddress -CivicAddressId 235678321ee38d9a5-33dc-4a32-9fb8-f234cedb91ac -``` - -This example returns the civic address with the specified identification. - - - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineLisCivicAddress -City Seattle -``` - -This example returns all the civic addresses in the city of Seattle. - - -## PARAMETERS - -### -AssignmentStatus -Specifies whether the retrieved addresses have been assigned to users or not. -Valid inputs are "Assigned", or "Unassigned". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -Specifies the city of the target civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CivicAddressId -Specifies the identification number of the civic address to return. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the country or region of the target civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the administrator defined description of the target civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberOfResultsToSkip -Specifies the number of results to skip. -If there are a large number of civic addresses, you can limit the number of returns by using the ResultSize parameter. -If you limited the first cmdlet execution to 25 results, and want to look at the next 25 locations, then you leave ResultSize at 25 and set NumberOfResultsToSkip to 25 to omit the first 25 you've reviewed. -For example the command below will return civic addresses 26-50 for Seattle. - -\`Get-CsOnlineLisCivicAddress -City Seattle -ResultSize 25 -NumberOfResultsToSkip 25\` - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopulateNumberOfVoiceUsers -If present, the PopulateNumberOfVoiceUsers switch causes the cmdlet to provide the number of voice users at the returned addresses. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -Specifies the maximum number of results to return. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidationStatus -Specifies the validation status of the addresses to be returned. -Valid inputs are: Valid, Invalid, and Notvalidated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopulateNumberOfTelephoneNumbers -{{Fill PopulateNumberOfTelephoneNumbers Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### One or more instances of civic address objects. - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineLisLocation.md b/skype/skype-ps/skype/Get-CsOnlineLisLocation.md deleted file mode 100644 index 678b03e06e..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineLisLocation.md +++ /dev/null @@ -1,353 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinelislocation -applicable: Skype for Business Online -title: Get-CsOnlineLisLocation -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# Get-CsOnlineLisLocation - -## SYNOPSIS -Use the Get-CsOnlineLisLocation cmdlet to retrieve information on previously defined locations in the Location Information Service (LIS.) - -## SYNTAX - -### GetByLocationID (Default) -``` -Get-CsOnlineLisLocation [-PopulateNumberOfVoiceUsers] [-PopulateNumberOfTelephoneNumbers] - [-AssignmentStatus <String>] [-City <String>] [-CountryOrRegion <String>] [-Description <String>] - [-ValidationStatus <String>] [-ResultSize <Int32>] [-NumberOfResultsToSkip <Int32>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -### UseCivicAddressId -``` -Get-CsOnlineLisLocation -CivicAddressId <Guid> [-PopulateNumberOfVoiceUsers] - [-PopulateNumberOfTelephoneNumbers] [-AssignmentStatus <String>] [-City <String>] [-CountryOrRegion <String>] - [-Description <String>] [-ValidationStatus <String>] [-ResultSize <Int32>] [-NumberOfResultsToSkip <Int32>] - [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -### UseLocationId -``` -Get-CsOnlineLisLocation [-PopulateNumberOfVoiceUsers] [-PopulateNumberOfTelephoneNumbers] - [-LocationId <Guid>] [-AssignmentStatus <String>] [-City <String>] [-CountryOrRegion <String>] - [-Description <String>] [-ValidationStatus <String>] [-ResultSize <Int32>] [-NumberOfResultsToSkip <Int32>] - [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -### UseLocation -``` -Get-CsOnlineLisLocation [-PopulateNumberOfVoiceUsers] [-PopulateNumberOfTelephoneNumbers] -Location <String> - [-AssignmentStatus <String>] [-City <String>] [-CountryOrRegion <String>] [-Description <String>] - [-ValidationStatus <String>] [-ResultSize <Int32>] [-NumberOfResultsToSkip <Int32>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineLisLocation -City Seattle -ResultSize 25 -ValidationStatus Validated -``` - -This example returns a maximum of 25 validated locations in Seattle. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineLisLocation -CivicAddressId a363a9b8-1acd-41de-916a-296c7998a024 -``` - -This example returns the locations associated with a civic address specified by its unique identifier. - -### -------------------------- Example 3 -------------------------- -``` -Get-CsOnlineLisLocation -Location "3rd Floor Cafe" -``` - -This example returns the location described as the "3rd Floor Cafe". - -### -------------------------- Example 4 -------------------------- -``` -Get-CsOnlineLisLocation -LocationId 5aa884e8-d548-4b8e-a289-52bfd5265a6e -``` - -This example returns the information on one location specified by its unique identifier. - - -## PARAMETERS - -### -CivicAddressId -Specifies the identification number of the civic address that is associated with the target locations. - -```yaml -Type: Guid -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Location -Specifies an administrator defined description of the location to retrieve. -For example, "2nd Floor Cafe", "Main Lobby", or "Office 250". - -```yaml -Type: String -Parameter Sets: UseLocation -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AssignmentStatus -Specifies whether the retrieved locations have been assigned to users or not. -Valid inputs are "Assigned", or "Unassigned". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -Specifies the city of the target location. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the country or region of the target location. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the administrator defined description of the civic address that is associated with the target locations. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -Specifies the unique identifier of the target location. - -```yaml -Type: Guid -Parameter Sets: UseLocationId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberOfResultsToSkip -Specifies the number of results to skip. -If there are a large number of locations, you can limit the number of returns by using the ResultSize parameter. -If you limited the first cmdlet execution to 25 results, and want to look at the next 25 locations, then you leave ResultSize at 25 and set NumberOfResultsToSkip to 25 to omit the first 25 you've reviewed. -For example the command below will return locations 26-50 for Seattle. - -\`Get-CsOnlineLisLocation -City Seattle -ResultSize 25 -NumberOfResultsToSkip 25\` - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopulateNumberOfVoiceUsers -If present, the PopulateNumberOfVoiceUsers switch causes the cmdlet to provide the number of voice users at the returned locations. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -Specifies the maximum number of results to return. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidationStatus -Specifies the validation status of the addresses to be returned. -Valid inputs are: Valid, Invalid, and Notvalidated. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PopulateNumberOfTelephoneNumbers -{{Fill PopulateNumberOfTelephoneNumbers Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### Returns an instance, or instances of emergency location objects. - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineLisPort.md b/skype/skype-ps/skype/Get-CsOnlineLisPort.md deleted file mode 100644 index 413b2252ea..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineLisPort.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinelisport -applicable: Skype for Business Online -title: Get-CsOnlineLisPort -schema: 2.0.0 -author: junya -ms.author: junya -ms.reviewer: ---- - -# Get-CsOnlineLisPort - -## SYNOPSIS -Retrieves one or more ports from the location configuration database. Each port can be associated with a location, in which case this cmdlet will also retrieve the location information of the ports. This location association is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. - -## SYNTAX - -``` -Get-CsOnlineLisPort [[-TenantId] <Guid>] [[-ChassisID] <String>] [-PortID <String>] [-IsDebug <Boolean>] - [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet retrieves information on associations between physical locations and the port through which the client is connected. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineLisPort -``` - -Example 1 retrieves all Location Information Server (LIS) ports and any associated locations. - - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineLisPort -PortID 12174 -ChassisID 0B-23-CD-16-AA-CC -``` - -Example 2 retrieves the location information for port 12174 with ChassisID 0B-23-CD-16-AA-CC. - - -## PARAMETERS - -### -ChassisID -The Media Access Control (MAC) address of the port's switch. This value will be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDebug -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NCSApiUrl -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PortID -This parameter identifies the ID of the port. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - - -### System.Guid - - -### System.String - - -## OUTPUTS - - -### System.Object - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineLisSwitch.md b/skype/skype-ps/skype/Get-CsOnlineLisSwitch.md deleted file mode 100644 index eda25a6f77..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineLisSwitch.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinelisswitch -applicable: Skype for Business Online -title: Get-CsOnlineLisSwitch -schema: 2.0.0 -author: junya -ms.author: junya -ms.reviewer: ---- - -# Get-CsOnlineLisSwitch - -## SYNOPSIS -Retrieves one or more network switches from the location configuration database. Each switch can be associated with a location, in which case this cmdlet will also retrieve the location information of the switches. This location association is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. - -## SYNTAX - -``` -Get-CsOnlineLisSwitch [[-TenantId] <Guid>] [[-ChassisID] <String>] [-IsDebug <Boolean>] [-TargetStore <String>] - [-NCSApiUrl <String>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet retrieves information on associations between physical locations and the network switch through which the client is connected. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineLisSwitch -``` - -Example 1 retrieves all Location Information Server (LIS) switches and any associated locations. - - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineLisSwitch -ChassisID 0B-23-CD-16-BB-CC -``` - -Example 2 retrieves Location Information Server (LIS) switch "0B-23-CD-16-BB-CC" and associated location. - - -## PARAMETERS - -### -ChassisID -The Media Access Control (MAC) address of the port's switch. This value will be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDebug -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NCSApiUrl -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - - -### System.Guid - - -### System.String - - -## OUTPUTS - - -### System.Object - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineLisWirelessAccessPoint.md b/skype/skype-ps/skype/Get-CsOnlineLisWirelessAccessPoint.md deleted file mode 100644 index b31f05f0d7..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineLisWirelessAccessPoint.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineliswirelessaccesspoint -applicable: Skype for Business Online -title: Get-CsOnlineLisWirelessAccessPoint -schema: 2.0.0 -author: junya -ms.author: junya -ms.reviewer: ---- - -# Get-CsOnlineLisWirelessAccessPoint - -## SYNOPSIS -Retrieves one or more wireless access points (WAPs) from the location configuration database. Each WAP can be associated with a location, in which case this cmdlet will also retrieve the location information of the WAPs. This location association is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. - -## SYNTAX - -``` -Get-CsOnlineLisWirelessAccessPoint [[-TenantId] <Guid>] [[-BSSID] <String>] [-IsDebug <Boolean>] - [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet retrieves information on associations between physical locations and the WAP through which the client is connected. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineLisWirelessAccessPoint -``` - -Example 1 retrieves all Location Information Server (LIS) wireless access points and any associated locations. - - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineLisWirelessAccessPoint -BSSID 0B-23-CD-16-BB-CC -``` - -Example 2 retrieves Location Information Server (LIS) wireless access point "0B-23-CD-16-BB-CC" and associated location. - -## PARAMETERS - -### -BSSID -The Basic Service Set Identifier (BSSID) of the wireless access point. This value must be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. If an entry with the specified BSSID value does not exist, a new WAP location will be created. If an entry with the specified BSSID does exist, that entry will be replaced. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDebug -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NCSApiUrl -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - - -### System.Guid - - -### System.String - - -## OUTPUTS - - -### System.Object - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineNumberPortInOrder.md b/skype/skype-ps/skype/Get-CsOnlineNumberPortInOrder.md deleted file mode 100644 index 7cdab0730a..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineNumberPortInOrder.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinenumberportinorder -applicable: Skype for Business Online -title: Get-CsOnlineNumberPortInOrder -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineNumberPortInOrder - -## SYNOPSIS -This cmdlet is reserved for Microsoft internal use only. -New third party provider ports should be provisioned through the Skype for Business Online admin center. - -## SYNTAX - -``` -Get-CsOnlineNumberPortInOrder [-Tenant <Guid>] [-PortInOrderId <String>] [-DomainController <Fqdn>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` - -``` - -## PARAMETERS - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PortInOrderId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineNumberPortOutOrderPin.md b/skype/skype-ps/skype/Get-CsOnlineNumberPortOutOrderPin.md deleted file mode 100644 index 03e7019f0e..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineNumberPortOutOrderPin.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinenumberportoutorderpin -applicable: Skype for Business Online -title: Get-CsOnlineNumberPortOutOrderPin -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineNumberPortOutOrderPin - -## SYNOPSIS - - -## SYNTAX - -``` -Get-CsOnlineNumberPortOutOrderPin [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -{{Fill in the Description}} - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -{{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -{{Fill DomainController Description}} - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{Fill Force Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -{{Fill Tenant Description}} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlinePSTNGateway.md b/skype/skype-ps/skype/Get-CsOnlinePSTNGateway.md deleted file mode 100644 index adef6d94be..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlinePSTNGateway.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinepstngateway -applicable: Skype for Business Online -title: Get-CsOnlinePSTNGateway -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlinePSTNGateway - -## SYNOPSIS -Shows the configuration of the previously defined Session Border Controller(s) (SBC(s)) that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlinePSTNGateway [-Tenant <System.Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlinePSTNGateway [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to show the configuration of the previously created Session Border Controller(s) (SBC(s)) configuration. Each configuration contains specific settings for an SBC. These settings configure such entities as SIP signaling port, whether media bypass is enabled on this SBC, will the SBC send SIP options, specify the limit of maximum concurrent sessions, The cmdlet also let drain the SBC by setting parameter -Enabled to true or false state. When the Enabled parameter set to $false, the SBC will continue existing calls, bit all new calls routed to another SBC in a route (if exists). - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-CsOnlinePSTNGateway -``` - -This example shows all SBCs paired with the tenant. - -### Example 2 -```powershell -PS C:\> Get-CsOnlinePSTNGateway | ?{$_.Identity -like "*.contoso.com"} -``` - -This example selects all SBC with names matching the pattern *.contoso.com. For example: sbc1.contoso.com, sbc2.contoso.com etc - -## PARAMETERS - -### -Filter - -```yaml -Type: String -Parameter Sets: Filter -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The parameter is optional for the cmdlet. If not set all SBCs paired to the tenant are listed. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: -Applicable: Skype for Business Online -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-CsOnlinePSTNGateway](Set-CsOnlinePSTNGateway.md) - -[New-CsOnlinePSTNGateway](New-CsOnlinePSTNGateway.md) - -[Remove-CsOnlinePSTNGateway](Remove-CsOnlinePSTNGateway.md) diff --git a/skype/skype-ps/skype/Get-CsOnlinePstnUsage.md b/skype/skype-ps/skype/Get-CsOnlinePstnUsage.md deleted file mode 100644 index 7881884520..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlinePstnUsage.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinepstnusage -applicable: Skype for Business Online -title: Get-CsOnlinePstnUsage -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlinePstnUsage - -## SYNOPSIS -Returns information about online public switched telephone network (PSTN) usage records used in your tenant. - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlinePstnUsage [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlinePstnUsage [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -Online PSTN usages are string values that are used for call authorization. An online PSTN usage links an online voice policy to a route. The `Get-CsOnlinePstnUsage` cmdlet retrieves the list of all online PSTN usages available within a tenant. - -This cmdlet is used when configuring Microsoft Phone System Direct Routing. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Get-CSOnlinePSTNUsage -``` - -This command returns the list of global PSTN usages available within the tenant. - -## PARAMETERS - -### -Filter -The Filter parameter allows you to retrieve only those PSTN usages with an Identity matching a particular wildcard string. However, the only Identity available to PSTN usages is Global, so this parameter is not useful for this cmdlet. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The level at which these settings are applied. The only identity that can be applied to PSTN usages is Global. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Set-CsOnlinePstnUsage](https://docs.microsoft.com/powershell/module/skype/set-csonlinepstnusage?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineSchedule.md b/skype/skype-ps/skype/Get-CsOnlineSchedule.md deleted file mode 100644 index 6b54620c49..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineSchedule.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineschedule -applicable: Skype for Business Online -title: Get-CsOnlineSchedule -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineSchedule - -## SYNOPSIS -Use the Get-CsOnlineSchedule cmdlet to get information about schedules that belong to your organization. - -## SYNTAX - -``` -Get-CsOnlineSchedule -Id <String> [-Tenant <Guid>] [-CommonParameters] -``` - -## DESCRIPTION -The Get-CsOnlineSchedule cmdlet returns information about the schedules in your organization. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineSchedule -``` - -This example retrieves all schedules that belong to your organization. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineSchedule -Id "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -``` - -This example gets the schedules that has the Id of f7a821dc-2d69-5ae8-8525-bcb4a4556093. - -## PARAMETERS - -### -Id -The Id for the schedule to be retrieved. If this parameter is not specified, then all schedules in the organization are returned. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### System.String -The Get-CsOnlineSchedule cmdlet accepts a string as the Id parameter. - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.Schedule - - -## NOTES - -## RELATED LINKS - -[New-CsOnlineTimeRange](New-CsOnlineTimeRange.md) - -[New-CsOnlineDateTimeRange](New-CsOnlineDateTimeRange.md) - -[New-CsAutoAttendantCallFlow](New-CsAutoAttendantCallFlow.md) diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberAvailableCount.md b/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberAvailableCount.md deleted file mode 100644 index b09e8bef1a..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberAvailableCount.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumberavailablecount -applicable: Skype for Business Online -title: Get-CsOnlineTelephoneNumberAvailableCount -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineTelephoneNumberAvailableCount - -## SYNOPSIS -Use the Get-CsOnlineTelephoneNumberAvailableCount cmdlet to retrieve the total telephone numbers your organization is licensed to acquire. - -## SYNTAX -``` -Get-CsOnlineTelephoneNumberAvailableCount [[-Tenant] <Guid>] [-InventoryType <String>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The console output of this cmdlet will be in the form: - -Get-CsOnlineTelephoneNumberAvailableCount - -RunspaceId Count - -------------- ------ - -37c11bb0-3064-4e36-a0af-05efe9ee2bd3 11010 - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineTelephoneNumberAvailableCount -``` - -This example returns the total telephone numbers your organization is licensed to acquire. - - -## PARAMETERS - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InventoryType -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### LacAvailableNumberCount object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryAreas.md b/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryAreas.md deleted file mode 100644 index 4063e24828..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryAreas.md +++ /dev/null @@ -1,225 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumberinventoryareas -applicable: Skype for Business Online -title: Get-CsOnlineTelephoneNumberInventoryAreas -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineTelephoneNumberInventoryAreas - -## SYNOPSIS -Use the `Get-CsOnlineTelephoneNumberInventoryAreas` cmdlet to retrieve the geographical areas where specified inventory types are supported. - -## SYNTAX - -``` -Get-CsOnlineTelephoneNumberInventoryAreas [-Tenant <Guid>] -RegionalGroup <String> - -CountryOrRegion <String> [-Area <String>] -InventoryType <String> [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -## DESCRIPTION -Following is an example of the console output for the Get-CsOnlineTelephoneNumberInventoryAreas cmdlet. - -Get-CsOnlineTelephoneNumberInventoryAreas -InventoryType Subscriber -RegionalGroup NOAM -CountryOrRegion US - -RunspaceId : 8fa40044-7bcf-465b-b7c8-76e54f124c8d - -Id : IL - -DefaultName : Illinois - -Cities : {} - -RunspaceId : 8fa40044-7bcf-465b-b7c8-76e54f124c8d - -Id : MA - -DefaultName : Massachusetts - -Cities : {} - -RunspaceId : 8fa40044-7bcf-465b-b7c8-76e54f124c8d - -Id : NY - -DefaultName : New York - -Cities : {} - -RunspaceId : 8fa40044-7bcf-465b-b7c8-76e54f124c8d - -Id : OR - -DefaultName : Oregon - -Cities : {} - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineTelephoneNumberInventoryAreas -InventoryType Subscriber -RegionalGroup NOAM -CountryOrRegion US -``` - -This example returns the areas with Subscriber inventory in the specified region and country. - - -## PARAMETERS - -### -CountryOrRegion -Specifies the target country for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Country -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InventoryType -Specifies the target telephone number type for the cmdlet. -Acceptable values are: - -"Service" for numbers assigned to conferencing support. - -"Subscriber" for numbers supporting public switched telephone network (PSTN) functions. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionalGroup -Specifies the target geographical region for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Region -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Area -Specifies the target geographical area for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### Deserialized.Microsoft.Rtc.Management.Hosted.Bvd.Types.InventoryArea -Instance or array of the objects. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryCities.md b/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryCities.md deleted file mode 100644 index 379f8d1ad5..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryCities.md +++ /dev/null @@ -1,229 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumberinventorycities -applicable: Skype for Business Online -title: Get-CsOnlineTelephoneNumberInventoryCities -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineTelephoneNumberInventoryCities - -## SYNOPSIS -Use the `Get-CsOnlineTelephoneNumberInventoryCities` to retrieve the cities that support a given inventory type within a geographical area. - -## SYNTAX - -``` -Get-CsOnlineTelephoneNumberInventoryCities [-Tenant <Guid>] -RegionalGroup <String> - -CountryOrRegion <String> -Area <String> [-CapitalOrMajorCity <String>] -InventoryType <String> - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Following is an example of the `Get-CsOnlineTelephoneNumberInventoryCities` cmdlet's console output. - -Get-CsOnlineTelephoneNumberInventoryCities -InventoryType Service -RegionalGroup NOAM -CountryOrRegion US -Area NY - -RunspaceId : 1374aa93-75c4-4679-b765-6efc22f97563 - -Id : NY - -DefaultName : New York City - -GeoCode : NOAM-US-NY-NY - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineTelephoneNumberInventoryCities -InventoryType Service -RegionalGroup NOAM -CountryOrRegion US -Area NY -``` - -The following example retrieves the cities defined as supporting "Service" inventory types in New York state. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineTelephoneNumberInventoryCities -InventoryType Subscriber -RegionalGroup NOAM -CountryOrRegion US -Area NY -``` - -The following example retrieves the cities defined as supporting "Subscriber" inventory types in New York state. - - -## PARAMETERS - -### -Area -Specifies the target geographical area for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the target country for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Country -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InventoryType -Specifies the target telephone number type for the cmdlet. -Acceptable values are: - -"Service" for numbers assigned to conferencing support. - -"Subscriber" for numbers supporting public switched telephone network (PSTN) functions. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionalGroup -Specifies the target geographical region for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Region -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CapitalOrMajorCity -Specifies the target geographical city for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: City -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -None - -## OUTPUTS - -### Deserialized.Microsoft.Rtc.Management.Hosted.Bvd.Types.InventoryCity -Instance or array of the object. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryCountries.md b/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryCountries.md deleted file mode 100644 index a4a94de049..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryCountries.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumberinventorycountries -applicable: Skype for Business Online -title: Get-CsOnlineTelephoneNumberInventoryCountries -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineTelephoneNumberInventoryCountries - -## SYNOPSIS -Use the `Get-CsOnlineTelephoneNumberInventoryCountries` cmdlet to retrieve a list of countries with telephone number inventories by specified region and telephone number inventory types. - -## SYNTAX - -``` -Get-CsOnlineTelephoneNumberInventoryCountries [-Tenant <Guid>] -RegionalGroup <String> - [-CountryOrRegion <String>] -InventoryType <String> [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Following is an example of the `Get-CsOnlineTelephoneNumberInventoryCountries` cmdlet's console output. - -RunspaceId : af39ca40-06a7-473b-8963-668865d15e87 - -Id : US - -DefaultName : United States - -Areas : {} - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineTelephoneNumberInventoryCountries -InventoryType Service -RegionalGroup NOAM -``` - -This example returns the countries in the north American region that contain service type telephone numbers. - -## PARAMETERS - -### -InventoryType -Specifies the target telephone number type for the cmdlet. -Acceptable values are: - -"Service" for numbers assigned to conferencing support. - -"Subscriber" for numbers supporting public switched telephone network (PSTN) functions. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionalGroup -Specifies the target geographical region for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Region -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the target country for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Country -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### Deserialized.Microsoft.Skype.EnterpriseVoice.BVDClient.Country -Instance or array of the object. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryRegions.md b/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryRegions.md deleted file mode 100644 index cec735a84b..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryRegions.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumberinventoryregions -applicable: Skype for Business Online -title: Get-CsOnlineTelephoneNumberInventoryRegions -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineTelephoneNumberInventoryRegions - -## SYNOPSIS -Use the `Get-CsOnlineTelephoneNumberInventoryRegions` cmdlet to retrieve the regions where specified inventory types are supported. - -## SYNTAX - -``` -Get-CsOnlineTelephoneNumberInventoryRegions [-Tenant <Guid>] [-RegionalGroup <String>] - -InventoryType <String> [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Following is an example of the `Get-CsOnlineTelephoneNumberInventoryRegions` cmdlet's console output. - -RunspaceId : f90303a9-c6a8-483c-b3b3-a5b8cdbab19c - -Id : NOAM - -DefaultName : North America - -Countries : {} - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineTelephoneNumberInventoryRegions -InventoryType Service -``` - -This example returns the region where the inventory type of "Service" is supported. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineTelephoneNumberInventoryRegions -InventoryType Subscriber -``` - -This example returns the region where the inventory type of "Subscriber" is supported. - -## PARAMETERS - -### -InventoryType -Specifies the target telephone number type for the cmdlet. -Acceptable values are: - -"Service" for numbers assigned to conferencing support. - -"Subscriber" for numbers supporting public switched telephone network (PSTN) functions. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionalGroup -Specifies the target geographical region for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Region -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### Deserialized.Microsoft.Skype.EnterpriseVoice.BVDClient.Region -Instance or array of the object. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryTypes.md b/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryTypes.md deleted file mode 100644 index 4ed65e2595..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberInventoryTypes.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumberinventorytypes -applicable: Skype for Business Online -title: Get-CsOnlineTelephoneNumberInventoryTypes -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineTelephoneNumberInventoryTypes - -## SYNOPSIS -Use the Get-CsOnlineTelephoneNumberInventoryTypes cmdlet to retrieve the telephone number inventory types that are defined. - -## SYNTAX - -``` -Get-CsOnlineTelephoneNumberInventoryTypes [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -## DESCRIPTION -This is an example of Get-CsOnlineTelephoneNumberInventoryTypes cmdlet's console output. - -RunspaceId : af39ca40-06a7-473b-8963-668865d15e87 - -Id : Service - -Description : Inventory of service telephone numbers - -Regions : {} - -Reservations : {} - -RunspaceId : af39ca40-06a7-473b-8963-668865d15e87 - -Id : Subscriber - -Description : Inventory of subscriber telephone numbers - -Regions : {} - -Reservations : {} - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineTelephoneNumberInventoryTypes -``` - -This example retrieves all the telephone number types for your organization. - - -## PARAMETERS - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### Deserialized.Microsoft.Skype.EnterpriseVoice.BVDClient.Inventory -Instance or array of the object. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberReservationsInformation.md b/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberReservationsInformation.md deleted file mode 100644 index 7f92f1a1ca..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumberReservationsInformation.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumberreservationsinformation -applicable: Skype for Business Online -title: Get-CsOnlineTelephoneNumberReservationsInformation -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineTelephoneNumberReservationsInformation - -## SYNOPSIS -Use the Get-CsOnlineTelephoneNumberReservationsInformation to retrieve information about the total number of telephone numbers which can reserved per session, and the maximum active reservations per session. - -## SYNTAX - -``` -Get-CsOnlineTelephoneNumberReservationsInformation [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to see the number of active reservations, reserved telephone numbers, maximum reservations supported per session, and maximum telephone numbers that can be reserved per session. - -The console output of this cmdlet will be in the following form: - -Get-CsOnlineTelephoneNumberReservationsInformation - -RunspaceId : 37c11bb0-3064-4e36-a0af-05efe9ee2bd3 - -ActiveReservationsCount : 0 - -ActiveReservedNumbersCount : 0 - -MaximumActiveReservationsCount : 10 - -MaximumActiveReservedNumbersCount : 200 - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineTelephoneNumberReservationsInformation -``` - -This example returns the number of active reservations, reserved telephone numbers, maximum reservations supported per session, and maximum telephone numbers that can be reserved per session. - - -## PARAMETERS - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### LacReservationInformation object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOnlineUser.md b/skype/skype-ps/skype/Get-CsOnlineUser.md deleted file mode 100644 index 47a2fa1442..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineUser.md +++ /dev/null @@ -1,332 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlineuser -applicable: Skype for Business Online -title: Get-CsOnlineUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineUser - -## SYNOPSIS -Returns information about users who have accounts homed on Skype for Business Online. -This cmdlet can only be used with Skype for Business Online. - -## SYNTAX - -``` -Get-CsOnlineUser [-Filter <String>] [-LdapFilter <String>] [-OnOfficeCommunicationServer] [-OnModernServer] - [-UnassignedUser] [-SkipUserPolicies] [-OU <OUIdParameter>] [-DomainController <Fqdn>] - [-Credential <PSCredential>] [[-Identity] <UserIdParameter>] [-ResultSize <>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOnlineUser cmdlet returns information about users who have accounts homed on Skype for Business Online. -The returned information includes standard Active Directory account information (such as the department the user works in, his or her address and phone number, etc.) as well as Skype for Business Server 2015 specific information: the Get-CsOnlineUser cmdlet returns information about such things as whether or not the user has been enabled for Enterprise Voice and which per-user policies (if any) have been assigned to the user. - -Note that the Get-CsOnlineUser cmdlet does not have a TenantId parameter; that means you cannot use a command similar to this in order to limit the returned data to users who have accounts with a specific Skype for Business Online tenant: - -`Get-CsOnlineUser -TenantId "bf19b7db-6960-41e5-a139-2aa373474354"` - -However, if you have multiple you can return users from a specified tenant by using the Filter parameter and a command similar to this: - -`Get-CsOnlineUser -Filter {TenantId -eq "bf19b7db-6960-41e5-a139-2aa373474354"}` - -That command will limit the returned data to user accounts belong to the tenant with the TenantId "bf19b7db-6960-41e5-a139-2aa373474354". -If you do not know your tenant IDs you can return that information by using this command: - -`Get-CsTenant` - -If you have a hybrid or "split domain" deployment (that is, a deployment in which some users have accounts homed on Skype for Business Online while other users have accounts homed on an on-premises version of Skype for Business Server 2015) keep in mind that the Get-CsOnlineUser cmdlet only returns information for Skype for Business Online users. -However, the cmdlet will return information for both online users and on-premises users. -If you want to exclude Skype for Business Online users from the data returned by the Get-CsUser cmdlet, use the following command: - -`Get-CsUser -Filter {TenantId -eq "00000000-0000-0000-0000-000000000000"}` - -By definition, users homed on the on-premises version will always have a TenantId equal to 00000000-0000-0000-0000-000000000000. -Users homed on Skype for Business Online will a TenantId that is equal to some value other than 00000000-0000-0000-0000-000000000000. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineUser -``` - -The command shown in Example 1 returns information for all the users configured as online users. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineUser -Identity "sip:kenmyer@litwareinc.com" -``` - -In Example 2 information is returned for a single online user: the user with the SIP address "sip:kenmyer@litwareinc.com". - -### -------------------------- Example 3 -------------------------- -``` -Get-CsOnlineUser -Filter {ArchivingPolicy -eq "RedmondArchiving"} -``` - -Example 3 uses the Filter parameter to limit the returned data to online users who have been assigned the per-user archiving policy RedmondArchiving. -To do this, the filter value {ArchivingPolicy -eq "RedmondArchiving"} is employed; that syntax limits returned data to users where the ArchivingPolicy property is equal to (-eq) "RedmondArchiving". - -### -------------------------- Example 4 -------------------------- -``` -Get-CsOnlineUser -Filter {HideFromAddressLists -eq $True} -``` - -Example 4 returns information only for user accounts that have been configured so that the account does not appear in Microsoft Exchange address lists. -(That is, the Active Directory attribute msExchHideFromAddressLists is True.) To carry out this task, the Filter parameter is included along with the filter value {HideFromAddressLists -eq $True}. - -### -------------------------- Example 5 -------------------------- -``` -Get-CsOnlineUser -Filter {TenantId -eq "bf19b7db-6960-41e5-a139-2aa373474354"} -``` - -The command shown in Example 5 returns information for all the online users assigned to the tenant with the TenantID "bf19b7db-6960-41e5-a139-2aa373474354". -To accomplish the task, the command includes the Filter parameter along with the filter value {TenantId -eq "bf19b7db-6960-41e5-a139-2aa373474354"}. -This filter limits the returned data to online users assigned to the tenant "bf19b7db-6960-41e5-a139-2aa373474354". - - -## PARAMETERS - -### -Credential -This parameter is not used with Skype for Business Online. - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is not used with Skype for Business Online. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -Enables you to limit the returned data by filtering on Skype for Business specific attributes. -For example, you can limit returned data to users who have been assigned a specific voice policy, or users who have not been assigned a specific voice policy. - -The Filter parameter uses the same filtering syntax that is used by the Where-Object cmdlet. -For example, a filter that returns only users who have been enabled for Enterprise Voice would look like this, with EnterpriseVoiceEnabled representing the Active Directory attribute, -eq representing the comparison operator (equal to), and $True (a built-in Windows PowerShell variable) representing the filter value: - -`{EnterpriseVoiceEnabled -eq $True}` - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the user account to be retrieved. -User Identities can be specified using one of the following formats: 1) the user's SIP address; 2) the user's user principal name (UPN); or, 3) the user's Active Directory display name (for example, Ken Myer). - -You can use the asterisk ( * ) wildcard character when using the Display Name as the user Identity. -For example, the Identity "* Smith" returns all the users who have a display name that ends with the string value " Smith". - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LdapFilter -Enables you to limit the returned data by filtering on generic Active Directory attributes (that is, attributes that are not specific to Skype for Business). -For example, you can limit returned data to users who work in a specific department, or users who have a specified manager or job title. - -The LdapFilter parameter uses the LDAP query language when creating filters. -For example, a filter that returns only users who work in the city of Redmond would look like this: "l=Redmond", with "l" (a lowercase L) representing the Active Directory attribute (locality); "=" representing the comparison operator (equal to); and "Redmond" representing the filter value. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnModernServer -When present, the cmdlet returns a collection of users homed on Skype for Business. -Users with accounts on previous versions of the software will not be returned when you use this parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: OnLyncServer -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnOfficeCommunicationServer -This parameter is not used with Skype for Business Online. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OU -This parameter is not used with Skype for Business Online. - -```yaml -Type: OUIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -Enables you to limit the number of records returned by the cmdlet. -For example, to return seven users (regardless of the number of users that are in your forest) include the ResultSize parameter and set the parameter value to 7. -Note that there is no way to guarantee which seven users will be returned. - -The result size can be set to any whole number between 0 and 2147483647, inclusive. -If set to 0 the command will run, but no data will be returned. -If you set the ResultSize to 7 but you have only three users in your forest, the command will return those three users, and then complete without error. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SkipUserPolicies -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UnassignedUser -Enables you to return a collection of all the users who have been enabled for Skype for Business but are not currently assigned to a Registrar pool. -Users are not allowed to log on to unless they are assigned to a Registrar pool. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### Microsoft.Rtc.Management.ADConnect.Schema.OCSADUser or String -A String must represent a valid user account Identity (for example, "sip:kenmyer@litwareinc.com"). - - -## OUTPUTS - -### Microsoft.Rtc.Management.ADConnect.Schema.ADOCOnlineUser - - -## NOTES - - -## RELATED LINKS - -[Set-CsUser](Set-CsUser.md) - diff --git a/skype/skype-ps/skype/Get-CsOnlineVoiceRoute.md b/skype/skype-ps/skype/Get-CsOnlineVoiceRoute.md deleted file mode 100644 index 1a7c83c557..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineVoiceRoute.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroute -applicable: Skype for Business Online -title: Get-CsOnlineVoiceRoute -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineVoiceRoute - -## SYNOPSIS -Returns information about the online voice routes configured for use in your tenant. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlineVoiceRoute [-Tenant <Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlineVoiceRoute [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to retrieve one or more existing online voice routes in your tenant. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). - -This cmdlet can be used to retrieve voice route information such as which online PSTN gateways the route is associated with (if any), which online PSTN usages are associated with the route, the pattern (in the form of a regular expression) that identifies the phone numbers to which the route applies, and caller ID settings. The PSTN usage associates the voice route to a online voice policy. - -This cmdlet is used when configuring Microsoft Phone System Direct Routing. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoute -``` - -Retrieves the properties for all voice routes defined within the tenant. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoute -Identity Route1 -``` - -Retrieves the properties for the Route1 voice route. - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoute -Filter *test* -``` - -This command displays voice route settings where the Identity contains the string "test" anywhere within the value. To find the string test only at the end of the Identity, use the value \*test. Similarly, to find the string test only if it occurs at the beginning of the Identity, specify the value test\*. - -### -------------------------- Example 4 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoute | Where-Object {$_.OnlinePstnGatewayList.Count -eq 0} -``` - -This command retrieves all voice routes that have not had any PSTN gateways assigned. First all voice routes are retrieved using the Get-CsOnlineVoiceRoute cmdlet. These voice routes are then piped to the Where-Object cmdlet. The Where-Object cmdlet narrows down the results of the Get operation. In this case we look at each voice route (that's what the $_ represents) and check the Count property of the PstnGatewayList property. If the count of PSTN gateways is 0, the list is empty and no gateways have been defined for the route. - -## PARAMETERS - -### -Filter -This parameter filters the results of the Get operation based on the wildcard value passed to this parameter. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A string that uniquely identifies the voice route. If no identity is provided, all voice routes for the organization are returned. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[New-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroute?view=skype-ps) - -[Set-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroute?view=skype-ps) - -[Remove-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroute?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineVoiceRoutingPolicy.md b/skype/skype-ps/skype/Get-CsOnlineVoiceRoutingPolicy.md deleted file mode 100644 index 0bc462835b..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineVoiceRoutingPolicy.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroutingpolicy -applicable: Skype for Business Online -title: Get-CsOnlineVoiceRoutingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineVoiceRoutingPolicy - -## SYNOPSIS -Returns information about the online voice routing policies configured for use in your tenant. Online voice routing policies manage online PSTN usages for users of Phone System. - -## SYNTAX - -### Identity (Default) -``` -Get-CsOnlineVoiceRoutingPolicy [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsOnlineVoiceRoutingPolicy [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. - -Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoutingPolicy -``` - -The command shown in Example 1 returns information for all the online voice routing policies configured for use in the tenant. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -``` - -In Example 2, information is returned for a single online voice routing policy: the policy with the Identity RedmondOnlineVoiceRoutingPolicy. - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoutingPolicy -Filter "tag:*" -``` - -The command shown in Example 3 returns information about all the online voice routing policies configured at the per-user scope. To do this, the command uses the Filter parameter and the filter value "tag:\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "tag:". - -### -------------------------- Example 4 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -contains "Long Distance"} -``` - -In Example 4, information is returned only for those online voice routing policies that include the PSTN usage "Long Distance". To carry out this task, the command first calls `Get-CsVoiceRoutingPolicy` without any parameters; that returns a collection of all the voice routing policies configured for use in the organization. This collection is then piped to the Where-Object cmdlet, which picks out only those policies where the OnlinePstnUsages property includes (-contains) the usage "Long Distance". - -### -------------------------- Example 5 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -notcontains "Long Distance"} -``` - -Example 5 is a variation on the command shown in Example 4; in this case, however, information is returned only for those online voice routing policies that do not include the PSTN usage "Long Distance". In order to do that, the Where-Object cmdlet uses the -notcontains operator, which limits returned data to policies that do not include the usage "Long Distance". - -## PARAMETERS - -### -Filter -Enables you to use wildcards when retrieving one or more online voice routing policies. For example, to return all the policies configured at the per-user scope, use this syntax: - --Filter "tag:\*" - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier of the online voice routing policy to be retrieved. To return the global policy, use this syntax: - --Identity global - -To return a policy configured at the per-user scope, use syntax like this: - --Identity "RedmondOnlineVoiceRoutingPolicy" - -You cannot use wildcard characters when specifying the Identity. - -If neither the Identity nor the Filter parameters are specified, then `Get-CsOnlineVoiceRoutingPolicy` returns all the voice routing policies configured for use in the tenant. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policies are being queried. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[New-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroutingpolicy?view=skype-ps) - -[Set-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroutingpolicy?view=skype-ps) - -[Grant-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoiceroutingpolicy?view=skype-ps) - -[Remove-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroutingpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineVoiceUser.md b/skype/skype-ps/skype/Get-CsOnlineVoiceUser.md deleted file mode 100644 index 9c21794b52..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineVoiceUser.md +++ /dev/null @@ -1,356 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceuser -applicable: Skype for Business Online -title: Get-CsOnlineVoiceUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineVoiceUser - -## SYNOPSIS -Use the `Get-CsOnlineVoiceUser` cmdlet to retrieve a voice user's telephone number and location. - -## SYNTAX - -``` -Get-CsOnlineVoiceUser [-CivicAddressId <XdsCivicAddressId>] [-DomainController <Fqdn>] [-EnterpriseVoiceStatus <MultiValuedProperty>] [-ExpandLocation] [-First <Unlimited>] [-Force] [-GetFromAAD] [-GetPendingUsers] [-Identity <UserIdParameter>] [-LocationId <LocationID>] [-NumberAssigned] [-NumberNotAssigned] [-PSTNConnectivity <MultiValuedProperty>] [-SearchQuery <String>] [-Skip <Unlimited>] [-Tenant <Guid>] [-AsJob] - [<CommonParameters>] -``` - -## DESCRIPTION - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceUser -Identity Ken.Myer@contoso.com -``` - -This example uses the User Principal Name (UPN) to retrieve the location and phone number information. - - -## PARAMETERS - -### -CivicAddressId -Specifies the identity of the civic address that is assigned to the target users. - -```yaml -Type: XdsCivicAddressId -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnterpriseVoiceStatus -Possible values are: -* All -* Enabled -* Disabled - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExpandLocation -Displays the location parameter with its value. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -First -Specifies the number of users to return. -The default is 100. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GetFromAAD -Use this switch to get the users from Azure Active Directory. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GetPendingUsers -Use this switch to get only the users in pending state. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the identity of the target user. -Acceptable values include: - -Example: jphillips@contoso.com - -Example: sip:jphillips@contoso.com - -Example: 98403f08-577c-46dd-851a-f0460a13b03d - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -Specifies the location identity of the location whose users will be returned. -You can find location identifiers by using the `Get-CsOnlineLisLocation` cmdlet. - -```yaml -Type: LocationID -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberAssigned -If specified, the query will return users who have a phone number assigned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberNotAssigned -If specified, the query will return users who do not have a phone number assigned. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PSTNConnectivity -Possible values are: -* All -* Online -* OnPremises - -```yaml -Type: MultiValuedProperty -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SearchQuery -The SearchQuery parameter specifies a search string or a query formatted using Keyword Query Language (KQL). For more details about KQL, see Keyword Query Language syntax reference (https://go.microsoft.com/fwlink/p/?linkid=269603). - -If this parameter is empty, all users are returned. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Skip -Specifies the number of users to skip. -If you used the First parameter to return the first 50 users and wanted to get another 50, you could use -Skip 50 to avoid returning the first 50 you've already reviewed. -The default is 0. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the `Receive-Job` cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - - -## OUTPUTS - -### Deserialized.Microsoft.Rtc.Management.Hosted.Bvd.Types.LacUser - - -## NOTES - - -## RELATED LINKS -[Set-CsOnlineVoiceUser](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceuser?view=skype-ps) - -[Set-CsOnlineVoiceUserBulk](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceuserbulk?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineVoicemailPolicy.md b/skype/skype-ps/skype/Get-CsOnlineVoicemailPolicy.md deleted file mode 100644 index 2b56a596c2..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineVoicemailPolicy.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinevoicemailpolicy -applicable: Skype for Business Online -title: Get-CsOnlineVoicemailPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineVoicemailPolicy - -## SYNOPSIS -Use the `Get-CsOnlineVoicemailPolicy` cmdlet to get a list of all pre-configured policy instances for Voicemail service. - -## SYNTAX - -``` -Get-CsOnlineVoicemailPolicy [-LocalStore] [[-Identity] <XdsIdentity>] [-Tenant <Guid>] [-Filter <String>] [-AsJob] -[<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet retrieves information about all the voicemail policies that have been configured for use in your organization. Voicemail policies are used by the organization to manage Voicemail-related features such as transcription. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineVoicemailPolicy -``` - -In Example 1, the Get-CsOnlineVoicemailPolicy cmdlet is called without any additional parameters; this returns a collection of all the voicemail policies configured for use in your organization. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineVoicemailPolicy -Identity TranscriptionDisabled -``` - -In Example 2, the Get-CsOnlineVoicemailPolicy cmdlet is used to return the per-user voicemail policy that has an Identity TranscriptionDisabled. Because identities are unique, this command will never return more than one item. - -### -------------------------- Example 3 -------------------------- -``` -Get-CsOnlineVoicemailPolicy -Filter "tag:*" -``` - -Example 3 uses the Filter parameter to return all the voicemail policies that have been configured at the per-user scope. The filter value "tag:*" tells the Get-CsOnlineVoicemailPolicy cmdlet to return only those policies that have an Identity that begins with the string value "tag:". - - -## PARAMETERS - -### -Filter -This parameter accepts a wildcard string and returns all voicemail policies with identities matching that string. For example, a Filter value of Tag:* will return all preconfigured voicemail policy instances (excluding forest default "Global") available to use by the tenant admins. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier specifying the scope, and in some cases the name, of the policy. If this parameter is omitted, all voicemail policies available for use are returned. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the Skype for Business Online tenant account whose voicemail policy is to be retrieved. For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" You can return the tenant ID for each of your tenants by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.WritableConfig.Policy.OnlineVoicemail.OnlineVoicemailPolicy - - -## NOTES - - -## RELATED LINKS -[Set-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailpolicy?view=skype-ps) - -[New-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoicemailpolicy?view=skype-ps) - -[Remove-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoicemailpolicy?view=skype-ps) - -[Grant-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoicemailpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsOnlineVoicemailUserSettings.md b/skype/skype-ps/skype/Get-CsOnlineVoicemailUserSettings.md deleted file mode 100644 index ae2c07f5f0..0000000000 --- a/skype/skype-ps/skype/Get-CsOnlineVoicemailUserSettings.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinevoicemailusersettings -applicable: Skype for Business Online -title: Get-CsOnlineVoicemailUserSettings -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOnlineVoicemailUserSettings - -## SYNOPSIS -Use the Get-CsOnlineVoicemailUserSettings cmdlet to get information about online voicemail user settings of a specific user. - -## SYNTAX - -``` -Get-CsOnlineVoicemailUserSettings -Identity <String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOnlineVoicemailUserSettings cmdlet returns information about online voicemail user settings of a specific user in your organization. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOnlineVoicemailUserSettings -Identity sip:user@contoso.com -``` - -This example gets the online voicemail user settings of user with SIP URI sip:user@contoso.com. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineVoicemailUserSettings -Identity "00000000-0000-0000-0000-000000000000" -``` - -This example gets the online voicemail user settings of user with Object ID "00000000-0000-0000-0000-000000000000". - - -## PARAMETERS - -### -Identity -The Identity parameter represents the ID of the specific user in your organization; this can be either a SIP URI or an Object ID. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Voicemail.Models.VoicemailUserSettings - - -## NOTES - - -## RELATED LINKS - -[Set-CsOnlineVoicemailUserSettings](Set-CsOnlineVoicemailUserSettings.md) - diff --git a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendant.md b/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendant.md deleted file mode 100644 index 717f155653..0000000000 --- a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendant.md +++ /dev/null @@ -1,180 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csorganizationalautoattendant -applicable: Skype for Business Online -title: Get-CsOrganizationalAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOrganizationalAutoAttendant - -## SYNOPSIS -Use the Get-CsOrganizationalAutoAttendant cmdlet to get information about Auto Attendants (AAs). - -## SYNTAX - -``` -Get-CsOrganizationalAutoAttendant [-PrimaryUri] <Uri> [-First <UInt64>] [-Skip <UInt64>] [-IncludeStatus] [-ApplicationId <Guid>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOrganizationalAutoAttendant cmdlet returns information about the OAAs in your organization. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOrganizationalAutoAttendant -``` - -This example gets all OAAs in the organization. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOrganizationalAutoAttendant -PrimaryUri sip:mainoaa@contoso.com -``` - -This example gets the OAAs that has the Primary URI of sip:mainoaa@contoso.com. - -### -------------------------- Example 3 -------------------------- -``` -Get-CsOrganizationalAutoAttendant -First 10 -``` - -This example gets the first ten auto attendants configured for use in the organization. - -### -------------------------- Example 4 -------------------------- -``` -Get-CsOrganizationalAutoAttendant -Skip 5 -First 10 -``` - -This example skips initial 5 auto attendants and gets the next 10 OAAs configured for use in the organization. - - -## PARAMETERS - -### -PrimaryUri -The PrimaryUri parameter represents the SIP address for the OAA to be retrieved. If this parameter is not specified, then all created OAAs in the organization are returned. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -First -The First parameter indicates the maximum number of auto attendants to retrieve as the result. It is intended to be used for pagination purposes. - -```yaml -Type: System.UInt64 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Skip -The Skip parameter indicates the number of initial auto attendants to skip in the result. It is intended to be used for pagination purposes. - -```yaml -Type: System.UInt64 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeStatus -If specified, the status records for each auto attendant in the result set are also retrieved. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationId -Specifies a custom application ID to use for auto attendants. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### String -The String is used as the PrimaryUri input. - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.OrgAutoAttendant - - -## NOTES - - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendant](New-CsOrganizationalAutoAttendant.md) - -[Set-CsOrganizationalAutoAttendant](Set-CsOrganizationalAutoAttendant.md) - -[Remove-CsOrganizationalAutoAttendant](Remove-CsOrganizationalAutoAttendant.md) - diff --git a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantHolidays.md b/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantHolidays.md deleted file mode 100644 index 033870b787..0000000000 --- a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantHolidays.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csorganizationalautoattendantholidays -applicable: Skype for Business Online -title: Get-CsOrganizationalAutoAttendantHolidays -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOrganizationalAutoAttendantHolidays - -## SYNOPSIS -Use Get-CsOrganizationalAutoAttendantHolidays cmdlet to get the holiday information for an existing Auto Attendant (AA). - -## SYNTAX - -``` -Get-CsOrganizationalAutoAttendantHolidays [-PrimaryUri] <Uri> [-Years <List>] [-Names <List>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOrganizationalAutoAttendantHolidays provides a convenient way to visualize the information of all the holidays contained within an auto attendant. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOrganizationalAutoAttendantHolidays -PrimaryUri "sip:mainoaa@contoso.com" -``` - -In this example, the Get-CsOrganizationalAutoAttendantHolidays cmdlet is used to get all holidays in an auto attendant with Primary URI of sip:mainoaa@contoso.com. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOrganizationalAutoAttendantHolidays -PrimaryUri "sip:mainoaa@contoso.com" -Years @(2017) -``` - -In this example, the Get-CsOrganizationalAutoAttendantHolidays cmdlet is used to get all holidays in year 2017 in an auto attendant with Primary URI of sip:mainoaa@contoso.com. - -### -------------------------- Example 3 -------------------------- -``` -Get-CsOrganizationalAutoAttendantHolidays -PrimaryUri "sip:mainoaa@contoso.com" -Years @(2017) -Name @("Christmas") -``` - -In this example, the Get-CsOrganizationalAutoAttendantHolidays cmdlet is used to get holiday named Christmas in the year 2017 in an auto attendant with Primary URI of sip:mainoaa@contoso.com. - -### -------------------------- Example 4 -------------------------- -``` -Get-CsOrganizationalAutoAttendantHolidays -PrimaryUri "sip:mainoaa@contoso.com" | Format-Table -Wrap -AutoSize -``` - -In this example, the Get-CsOrganizationalAutoAttendantHolidays cmdlet is used to retrieve all holidays in an auto attendant with Primary URI of sip:mainoaa@contoso.com and the result is formatted as a table. - - -## PARAMETERS - -### -PrimaryUri -The PrimaryUri parameter represents the SIP address of the auto attendant whose holidays are to be retrieved. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Years -The Years parameter represents the years for the holidays to be retrieved. If this parameter is not specified, then holidays for all years in the OAA are returned. - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Names -The Names parameter represents the names for the holidays to be retrieved. If this parameter is not specified, then all holidays in the OAA are returned. - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### String -The String is used as the PrimaryUri input. - - -## OUTPUTS - -### Microsoft.Rtc.Management.OAA.Models.HolidayVisRecord - - -## NOTES - - -## RELATED LINKS - -[Import-CsOrganizationalAutoAttendantHolidays](Import-CsOrganizationalAutoAttendantHolidays.md) - -[Export-CsOrganizationalAutoAttendantHolidays](Export-CsOrganizationalAutoAttendantHolidays.md) - diff --git a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantStatus.md b/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantStatus.md deleted file mode 100644 index dee7b0677c..0000000000 --- a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantStatus.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csorganizationalautoattendantstatus -applicable: Skype for Business Online -title: Get-CsOrganizationalAutoAttendantStatus -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOrganizationalAutoAttendantStatus - -## SYNOPSIS -Use Get-CsOrganizationalAutoAttendantStatus cmdlet to get the status of an Auto Attendant (AA) provisioning. - - -## SYNTAX - -``` -Get-CsOrganizationalAutoAttendantStatus [-PrimaryUri] <Uri> [-IncludeResources <List>] [-ApplicationId <Guid>] [-Tenant <Guid>] [<CommonParameters>] -``` - - -## DESCRIPTION -This cmdlet provides a way to return the provisioning status of an auto attendant configured for use in your organization. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOrganizationalAutoAttendantStatus -PrimaryUri "sip:mainoaa@contoso.com" -``` - -In Example 1, the Get-CsOrganizationalAutoAttendantStatus cmdlet is used to get status records for all resources of an auto attendant with Primary URI of sip:mainoaa@contoso.com. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOrganizationalAutoAttendantStatus -PrimaryUri sip:mainoaa@contoso.com -IncludeResources @("AudioFile") -``` - -In Example 2, the Get-CsOrganizationalAutoAttendantStatus cmdlet is used to get status records pertaining to audio files only of an auto attendant with Primary URI of sip:mainoaa@contoso.com. - -## PARAMETERS - -### -PrimaryUri -The Primary URI represents the SIP address of the auto attendant whose provisioning status is to be retrieved. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeResources -The IncludeResources parameter identities the auto attendant resources whose status is to be retrieved. Available resources are: -- AudioFile: Indicates status for audio files used by OAA. -- DialByNameVoiceResponses: Indicates status for speech recognition when using dial-by-name (directory lookup) feature with OAA. -- SipProvisioning: Indicates status for calling OAA through its SIP (Primary) URI. - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Accepted values: AudioFile, DialByNameVoiceResponses, SipProvisioning -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationId -Specifies a custom application ID to use for auto attendants. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -The Get-CsOrganizationalAutoAttendantStatus cmdlet accepts a string as the PrimaryUri parameter. - -## OUTPUTS - -### Microsoft.Rtc.Management.OAA.Models.StatusRecord - -## NOTES - -## RELATED LINKS - -[Get-CsOrganizationalAutoAttendant](Get-CsOrganizationalAutoAttendant.md) - diff --git a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantSupportedLanguage.md b/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantSupportedLanguage.md deleted file mode 100644 index af0793eb5d..0000000000 --- a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantSupportedLanguage.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csorganizationalautoattendantsupportedlanguage -applicable: Skype for Business Online -title: Get-CsOrganizationalAutoAttendantSupportedLanguage -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOrganizationalAutoAttendantSupportedLanguage - -## SYNOPSIS -The Get-CsOrganizationalAutoAttendantSupportedLanguage cmdlet gets languages that are supported by the Auto Attendant (AA) service. - -## SYNTAX - -``` -Get-CsOrganizationalAutoAttendantSupportedLanguage [-Identity] <System.String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOrganizationalAutoAttendantSupportedLanguage cmdlet gets all languages (and their corresponding voices/speakers) that are supported by the OAA service. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOrganizationalAutoAttendantSupportedLanguage -``` - -This example gets all supported languages. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOrganizationalAutoAttendantSupportedLanguage -Identity "en-US" -``` - -This example gets the language that the Identity parameter specifies (en-US). - -## PARAMETERS - -### -Identity -The Identity parameter designates a specific language to be retrieved. If this parameter is not specified, then all supported languages are returned. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.Language - - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantSupportedTimeZone.md b/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantSupportedTimeZone.md deleted file mode 100644 index 442168e857..0000000000 --- a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantSupportedTimeZone.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csorganizationalautoattendantsupportedtimezone -applicable: Skype for Business Online -title: Get-CsOrganizationalAutoAttendantSupportedTimeZone -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOrganizationalAutoAttendantSupportedTimeZone - -## SYNOPSIS -The Get-CsOrganizationalAutoAttendantSupportedTimeZone cmdlet gets supported time zones for the Auto Attendant (AA) service. - -## SYNTAX - -``` -Get-CsOrganizationalAutoAttendantSupportedTimeZone [-Identity] <String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOrganizationalAutoAttendantSupportedTimeZone cmdlet gets all the time zones that the OAA service supports, or a specific time zone if its Identity is provided. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOrganizationalAutoAttendantSupportedTimeZone -``` - -This example gets all supported time zones. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOrganizationalAutoAttendantSupportedTimeZone -Identity "Pacific Standard Time" -``` - -This example gets the timezone that the Identity parameter specifies (Pacific Standard Time). - - -## PARAMETERS - -### -Identity -The Identity parameter specifies a time zone to be retrieved. If this parameter is not used, then all supported time zones are returned. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.TimeZone - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantTenantInformation.md b/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantTenantInformation.md deleted file mode 100644 index 56fdc9315c..0000000000 --- a/skype/skype-ps/skype/Get-CsOrganizationalAutoAttendantTenantInformation.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csorganizationalautoattendanttenantinformation -applicable: Skype for Business Online -title: Get-CsOrganizationalAutoAttendantTenantInformation -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsOrganizationalAutoAttendantTenantInformation - -## SYNOPSIS -Gets the default tenant information for Auto Attendant (AA) feature. - -## SYNTAX - -``` -Get-CsOrganizationalAutoAttendantTenantInformation [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsOrganizationalAutoAttendantTenantInformation cmdlet gets the default tenant information for Auto Attendant (AA) feature. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsOrganizationalAutoAttendantTenantInformation -``` - -Gets the default auto attendant information for the logged in tenant. - - -## PARAMETERS - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.TenantInformation - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsOutboundCallingNumberTranslationRule.md b/skype/skype-ps/skype/Get-CsOutboundCallingNumberTranslationRule.md index 290ef15bc9..5583f31ca1 100644 --- a/skype/skype-ps/skype/Get-CsOutboundCallingNumberTranslationRule.md +++ b/skype/skype-ps/skype/Get-CsOutboundCallingNumberTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csoutboundcallingnumbertranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/get-csoutboundcallingnumbertranslationrule applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsOutboundCallingNumberTranslationRule schema: 2.0.0 @@ -168,4 +168,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsOutboundCallingNumberTranslationRule](Remove-CsOutboundCallingNumberTranslationRule.md) [Set-CsOutboundCallingNumberTranslationRule](Set-CsOutboundCallingNumberTranslationRule.md) - diff --git a/skype/skype-ps/skype/Get-CsOutboundTranslationRule.md b/skype/skype-ps/skype/Get-CsOutboundTranslationRule.md index aa6c536ca6..8b9c66c91c 100644 --- a/skype/skype-ps/skype/Get-CsOutboundTranslationRule.md +++ b/skype/skype-ps/skype/Get-CsOutboundTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csoutboundtranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/get-csoutboundtranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsOutboundTranslationRule schema: 2.0.0 @@ -143,4 +143,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsOutboundTranslationRule](Remove-CsOutboundTranslationRule.md) [Set-CsOutboundTranslationRule](Set-CsOutboundTranslationRule.md) - diff --git a/skype/skype-ps/skype/Get-CsPartnerApplication.md b/skype/skype-ps/skype/Get-CsPartnerApplication.md index 9f955c1ce1..d88eef5d7f 100644 --- a/skype/skype-ps/skype/Get-CsPartnerApplication.md +++ b/skype/skype-ps/skype/Get-CsPartnerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspartnerapplication +online version: https://learn.microsoft.com/powershell/module/skype/get-cspartnerapplication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPartnerApplication schema: 2.0.0 @@ -186,4 +186,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPartnerApplication](Remove-CsPartnerApplication.md) [Set-CsPartnerApplication](Set-CsPartnerApplication.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatAddin.md b/skype/skype-ps/skype/Get-CsPersistentChatAddin.md index 508ca174d1..72d85cb632 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatAddin.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatAddin.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchataddin -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchataddin +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatAddin schema: 2.0.0 manager: rogupta @@ -137,4 +137,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPersistentChatAddin](Remove-CsPersistentChatAddin.md) [Set-CsPersistentChatAddin](Set-CsPersistentChatAddin.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatCategory.md b/skype/skype-ps/skype/Get-CsPersistentChatCategory.md index df640c38fa..e00444b74c 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatCategory.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatCategory.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchatcategory -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchatcategory +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatCategory schema: 2.0.0 manager: rogupta @@ -161,4 +161,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPersistentChatCategory](Remove-CsPersistentChatCategory.md) [Set-CsPersistentChatCategory](Set-CsPersistentChatCategory.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatComplianceConfiguration.md b/skype/skype-ps/skype/Get-CsPersistentChatComplianceConfiguration.md index 7b34e77a4c..cf19471a4f 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatComplianceConfiguration.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatComplianceConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchatcomplianceconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchatcomplianceconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatComplianceConfiguration schema: 2.0.0 manager: rogupta @@ -180,4 +180,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPersistentChatComplianceConfiguration](Remove-CsPersistentChatComplianceConfiguration.md) [Set-CsPersistentChatComplianceConfiguration](Set-CsPersistentChatComplianceConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatConfiguration.md b/skype/skype-ps/skype/Get-CsPersistentChatConfiguration.md index 828f205213..7fd56a3f4c 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatConfiguration.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchatconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchatconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatConfiguration schema: 2.0.0 manager: rogupta @@ -179,4 +179,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPersistentChatConfiguration](Remove-CsPersistentChatConfiguration.md) [Set-CsPersistentChatConfiguration](Set-CsPersistentChatConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatEligiblePrincipal.md b/skype/skype-ps/skype/Get-CsPersistentChatEligiblePrincipal.md index 8582982224..f4405e37b0 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatEligiblePrincipal.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatEligiblePrincipal.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchateligibleprincipal -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchateligibleprincipal +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatEligiblePrincipal schema: 2.0.0 manager: rogupta @@ -213,4 +213,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsPersistentChatCategory](Set-CsPersistentChatCategory.md) [New-CsPersistentChatRoom](New-CsPersistentChatRoom.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatEndpoint.md b/skype/skype-ps/skype/Get-CsPersistentChatEndpoint.md index 9b55800af6..04e98b3f03 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatEndpoint.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatEndpoint.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchatendpoint -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchatendpoint +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatEndpoint schema: 2.0.0 manager: rogupta @@ -248,4 +248,3 @@ String value representing the Identity or the SIP address of a Persistent Chat e [New-CsPersistentChatEndpoint](New-CsPersistentChatEndpoint.md) [Remove-CsPersistentChatEndpoint](Remove-CsPersistentChatEndpoint.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatPolicy.md b/skype/skype-ps/skype/Get-CsPersistentChatPolicy.md index 06e6d675b2..7c0e9ecc89 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatPolicy.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchatpolicy -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchatpolicy +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatPolicy schema: 2.0.0 manager: rogupta @@ -198,4 +198,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPersistentChatPolicy](Remove-CsPersistentChatPolicy.md) [Set-CsPersistentChatPolicy](Set-CsPersistentChatPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatRoom.md b/skype/skype-ps/skype/Get-CsPersistentChatRoom.md index 124a06ce57..b2f79623d0 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatRoom.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchatroom -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchatroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatRoom schema: 2.0.0 manager: rogupta @@ -390,4 +390,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPersistentChatRoom](Remove-CsPersistentChatRoom.md) [Set-CsPersistentChatRoom](Set-CsPersistentChatRoom.md) - diff --git a/skype/skype-ps/skype/Get-CsPersistentChatState.md b/skype/skype-ps/skype/Get-CsPersistentChatState.md index b673d18955..232ca51c32 100644 --- a/skype/skype-ps/skype/Get-CsPersistentChatState.md +++ b/skype/skype-ps/skype/Get-CsPersistentChatState.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspersistentchatstate -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspersistentchatstate +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPersistentChatState schema: 2.0.0 manager: rogupta @@ -152,4 +152,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsPersistentChatState](Set-CsPersistentChatState.md) - diff --git a/skype/skype-ps/skype/Get-CsPinPolicy.md b/skype/skype-ps/skype/Get-CsPinPolicy.md index b9d175534b..a72edbf43e 100644 --- a/skype/skype-ps/skype/Get-CsPinPolicy.md +++ b/skype/skype-ps/skype/Get-CsPinPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspinpolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-cspinpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPinPolicy schema: 2.0.0 @@ -202,4 +202,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPinPolicy](Remove-CsPinPolicy.md) [Set-CsPinPolicy](Set-CsPinPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsPlatformServiceSettings.md b/skype/skype-ps/skype/Get-CsPlatformServiceSettings.md index d3e89bb12a..556e9c6bbe 100644 --- a/skype/skype-ps/skype/Get-CsPlatformServiceSettings.md +++ b/skype/skype-ps/skype/Get-CsPlatformServiceSettings.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csplatformservicesettings -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csplatformservicesettings +applicable: Skype for Business Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPlatformServiceSettings schema: 2.0.0 manager: rogupta @@ -13,7 +13,7 @@ ms.reviewer: # Get-CsPlatformServiceSettings ## SYNOPSIS -Returns information about Skype for Business on Mac capabilites which have been enabled in your organization. This cmdlet was introduced in Skype for Business Server 2015 Cumulative Update 6 (December 2017). +Returns information about Skype for Business on Mac capabilities which have been enabled in your organization. This cmdlet was introduced in Skype for Business Server 2015 Cumulative Update 6 (December 2017). ## SYNTAX @@ -110,8 +110,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[New-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/new-csplatformservicesettings?view=skype-ps) +[New-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/new-csplatformservicesettings?view=skype-ps) -[Set-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/set-csplatformservicesettings?view=skype-ps) +[Set-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/set-csplatformservicesettings?view=skype-ps) -[Remove-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/remove-csplatformservicesettings?view=skype-ps) +[Remove-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/remove-csplatformservicesettings?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsPool.md b/skype/skype-ps/skype/Get-CsPool.md index 69840b66b2..8c56497961 100644 --- a/skype/skype-ps/skype/Get-CsPool.md +++ b/skype/skype-ps/skype/Get-CsPool.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspool +online version: https://learn.microsoft.com/powershell/module/skype/get-cspool applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPool schema: 2.0.0 @@ -175,4 +175,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Get-CsSite](Get-CsSite.md) [Get-CsTopology](Get-CsTopology.md) - diff --git a/skype/skype-ps/skype/Get-CsPoolBackupRelationship.md b/skype/skype-ps/skype/Get-CsPoolBackupRelationship.md index 35cc7ad0da..d29e9701e9 100644 --- a/skype/skype-ps/skype/Get-CsPoolBackupRelationship.md +++ b/skype/skype-ps/skype/Get-CsPoolBackupRelationship.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspoolbackuprelationship +online version: https://learn.microsoft.com/powershell/module/skype/get-cspoolbackuprelationship applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPoolBackupRelationship schema: 2.0.0 @@ -111,4 +111,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsPoolFabricState.md b/skype/skype-ps/skype/Get-CsPoolFabricState.md index 50fa7c9e40..2e915d6108 100644 --- a/skype/skype-ps/skype/Get-CsPoolFabricState.md +++ b/skype/skype-ps/skype/Get-CsPoolFabricState.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspoolfabricstate +online version: https://learn.microsoft.com/powershell/module/skype/get-cspoolfabricstate applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPoolFabricState schema: 2.0.0 @@ -324,5 +324,3 @@ String value representing the fabric state. ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Get-CsPoolUpgradeReadinessState.md b/skype/skype-ps/skype/Get-CsPoolUpgradeReadinessState.md index a9a72b1d58..db2ff87bbf 100644 --- a/skype/skype-ps/skype/Get-CsPoolUpgradeReadinessState.md +++ b/skype/skype-ps/skype/Get-CsPoolUpgradeReadinessState.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspoolupgradereadinessstate +online version: https://learn.microsoft.com/powershell/module/skype/get-cspoolupgradereadinessstate applicable: Lync Server 2013, Skype for Business Server 2015 title: Get-CsPoolUpgradeReadinessState schema: 2.0.0 @@ -132,4 +132,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsPresenceManagementState.md b/skype/skype-ps/skype/Get-CsPresenceManagementState.md index 2bf0fd2184..73930cdaf6 100644 --- a/skype/skype-ps/skype/Get-CsPresenceManagementState.md +++ b/skype/skype-ps/skype/Get-CsPresenceManagementState.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspresencemanagementstate +online version: https://learn.microsoft.com/powershell/module/skype/get-cspresencemanagementstate applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPresenceManagementState schema: 2.0.0 @@ -95,4 +95,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsPresenceManagementState](Set-CsPresenceManagementState.md) - diff --git a/skype/skype-ps/skype/Get-CsPresencePolicy.md b/skype/skype-ps/skype/Get-CsPresencePolicy.md index 97b963a70b..f4d0e7294a 100644 --- a/skype/skype-ps/skype/Get-CsPresencePolicy.md +++ b/skype/skype-ps/skype/Get-CsPresencePolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspresencepolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspresencepolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPresencePolicy schema: 2.0.0 manager: bulenteg @@ -155,26 +155,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Tenant Globally unique identifier (GUID) of the Skype for Business Online tenant account whose presence policies are being returned. For example: @@ -224,4 +204,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPresencePolicy](Remove-CsPresencePolicy.md) [Set-CsPresencePolicy](Set-CsPresencePolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsPresenceProvider.md b/skype/skype-ps/skype/Get-CsPresenceProvider.md index 02627be7bb..8051cd503e 100644 --- a/skype/skype-ps/skype/Get-CsPresenceProvider.md +++ b/skype/skype-ps/skype/Get-CsPresenceProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspresenceprovider +online version: https://learn.microsoft.com/powershell/module/skype/get-cspresenceprovider applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPresenceProvider schema: 2.0.0 @@ -166,4 +166,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPresenceProvider](Remove-CsPresenceProvider.md) [Set-CsPresenceProvider](Set-CsPresenceProvider.md) - diff --git a/skype/skype-ps/skype/Get-CsPrivacyConfiguration.md b/skype/skype-ps/skype/Get-CsPrivacyConfiguration.md index f5a453d20c..f008d70f24 100644 --- a/skype/skype-ps/skype/Get-CsPrivacyConfiguration.md +++ b/skype/skype-ps/skype/Get-CsPrivacyConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csprivacyconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csprivacyconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPrivacyConfiguration schema: 2.0.0 manager: bulenteg @@ -180,26 +180,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -224,4 +204,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPrivacyConfiguration](Remove-CsPrivacyConfiguration.md) [Set-CsPrivacyConfiguration](Set-CsPrivacyConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsProxyConfiguration.md b/skype/skype-ps/skype/Get-CsProxyConfiguration.md index 54335cd4b2..8ab2e40fe6 100644 --- a/skype/skype-ps/skype/Get-CsProxyConfiguration.md +++ b/skype/skype-ps/skype/Get-CsProxyConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csproxyconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csproxyconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsProxyConfiguration schema: 2.0.0 @@ -173,4 +173,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsProxyConfiguration](Remove-CsProxyConfiguration.md) [Set-CsProxyConfiguration](Set-CsProxyConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsPstnUsage.md b/skype/skype-ps/skype/Get-CsPstnUsage.md index 9b62db57ac..3905df1116 100644 --- a/skype/skype-ps/skype/Get-CsPstnUsage.md +++ b/skype/skype-ps/skype/Get-CsPstnUsage.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspstnusage +online version: https://learn.microsoft.com/powershell/module/skype/get-cspstnusage applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPstnUsage schema: 2.0.0 @@ -163,4 +163,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Get-CsVoicePolicy](Get-CsVoicePolicy.md) [Get-CsVoiceRoute](Get-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/Get-CsPublicProvider.md b/skype/skype-ps/skype/Get-CsPublicProvider.md index 4dc42352f8..e896dc4205 100644 --- a/skype/skype-ps/skype/Get-CsPublicProvider.md +++ b/skype/skype-ps/skype/Get-CsPublicProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspublicprovider +online version: https://learn.microsoft.com/powershell/module/skype/get-cspublicprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPublicProvider schema: 2.0.0 @@ -178,4 +178,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsPublicProvider](Remove-CsPublicProvider.md) [Set-CsPublicProvider](Set-CsPublicProvider.md) - diff --git a/skype/skype-ps/skype/Get-CsPushNotificationConfiguration.md b/skype/skype-ps/skype/Get-CsPushNotificationConfiguration.md index fff549646d..c691ad8fc7 100644 --- a/skype/skype-ps/skype/Get-CsPushNotificationConfiguration.md +++ b/skype/skype-ps/skype/Get-CsPushNotificationConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cspushnotificationconfiguration -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-cspushnotificationconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsPushNotificationConfiguration schema: 2.0.0 manager: bulenteg @@ -193,26 +193,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -231,8 +211,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Set-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration?view=skype-ps) +[Set-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration?view=skype-ps) -[New-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/new-cspushnotificationconfiguration?view=skype-ps) +[New-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/new-cspushnotificationconfiguration?view=skype-ps) -[Remove-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/remove-cspushnotificationconfiguration?view=skype-ps) +[Remove-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/remove-cspushnotificationconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsQoEConfiguration.md b/skype/skype-ps/skype/Get-CsQoEConfiguration.md index ee563ff861..df091a86aa 100644 --- a/skype/skype-ps/skype/Get-CsQoEConfiguration.md +++ b/skype/skype-ps/skype/Get-CsQoEConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csqoeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csqoeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsQoEConfiguration schema: 2.0.0 @@ -153,4 +153,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsQoEConfiguration](Remove-CsQoEConfiguration.md) [Set-CsQoEConfiguration](Set-CsQoEConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsRegistrarConfiguration.md b/skype/skype-ps/skype/Get-CsRegistrarConfiguration.md index ea1669f54b..e5b7e3c765 100644 --- a/skype/skype-ps/skype/Get-CsRegistrarConfiguration.md +++ b/skype/skype-ps/skype/Get-CsRegistrarConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csregistrarconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csregistrarconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRegistrarConfiguration schema: 2.0.0 @@ -177,4 +177,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsRegistrarConfiguration](Remove-CsRegistrarConfiguration.md) [Set-CsRegistrarConfiguration](Set-CsRegistrarConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsReportingConfiguration.md b/skype/skype-ps/skype/Get-CsReportingConfiguration.md index 30969717f8..6a67e67c54 100644 --- a/skype/skype-ps/skype/Get-CsReportingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsReportingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csreportingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csreportingconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsReportingConfiguration schema: 2.0.0 @@ -154,4 +154,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsReportingConfiguration](Remove-CsReportingConfiguration.md) [Set-CsReportingConfiguration](Set-CsReportingConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsRgsAgentGroup.md b/skype/skype-ps/skype/Get-CsRgsAgentGroup.md index b245c8d476..c55cfb40ac 100644 --- a/skype/skype-ps/skype/Get-CsRgsAgentGroup.md +++ b/skype/skype-ps/skype/Get-CsRgsAgentGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csrgsagentgroup +online version: https://learn.microsoft.com/powershell/module/skype/get-csrgsagentgroup applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRgsAgentGroup schema: 2.0.0 @@ -181,4 +181,3 @@ A string value representing the Identity of the Response Group agent group. [Remove-CsRgsAgentGroup](Remove-CsRgsAgentGroup.md) [Set-CsRgsAgentGroup](Set-CsRgsAgentGroup.md) - diff --git a/skype/skype-ps/skype/Get-CsRgsConfiguration.md b/skype/skype-ps/skype/Get-CsRgsConfiguration.md index 90a00d191b..efecbe98eb 100644 --- a/skype/skype-ps/skype/Get-CsRgsConfiguration.md +++ b/skype/skype-ps/skype/Get-CsRgsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csrgsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csrgsconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRgsConfiguration schema: 2.0.0 @@ -114,4 +114,3 @@ A string value representing the Identity of the Response Group configuration set [Move-CsRgsConfiguration](Move-CsRgsConfiguration.md) [Set-CsRgsConfiguration](Set-CsRgsConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsRgsHolidaySet.md b/skype/skype-ps/skype/Get-CsRgsHolidaySet.md index 0cbcf6b081..2b7b8d3bf5 100644 --- a/skype/skype-ps/skype/Get-CsRgsHolidaySet.md +++ b/skype/skype-ps/skype/Get-CsRgsHolidaySet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csrgsholidayset +online version: https://learn.microsoft.com/powershell/module/skype/get-csrgsholidayset applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRgsHolidaySet schema: 2.0.0 @@ -197,4 +197,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsRgsHolidaySet](Remove-CsRgsHolidaySet.md) [Set-CsRgsHolidaySet](Set-CsRgsHolidaySet.md) - diff --git a/skype/skype-ps/skype/Get-CsRgsHoursOfBusiness.md b/skype/skype-ps/skype/Get-CsRgsHoursOfBusiness.md index acce5ee5ab..8f06475469 100644 --- a/skype/skype-ps/skype/Get-CsRgsHoursOfBusiness.md +++ b/skype/skype-ps/skype/Get-CsRgsHoursOfBusiness.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csrgshoursofbusiness +online version: https://learn.microsoft.com/powershell/module/skype/get-csrgshoursofbusiness applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRgsHoursOfBusiness schema: 2.0.0 @@ -195,4 +195,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsRgsHoursOfBusiness](Remove-CsRgsHoursOfBusiness.md) [Set-CsRgsHoursOfBusiness](Set-CsRgsHoursOfBusiness.md) - diff --git a/skype/skype-ps/skype/Get-CsRgsQueue.md b/skype/skype-ps/skype/Get-CsRgsQueue.md index d2a3ecc805..80bee92147 100644 --- a/skype/skype-ps/skype/Get-CsRgsQueue.md +++ b/skype/skype-ps/skype/Get-CsRgsQueue.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csrgsqueue +online version: https://learn.microsoft.com/powershell/module/skype/get-csrgsqueue applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRgsQueue schema: 2.0.0 @@ -182,4 +182,3 @@ A string value representing the Identity of the Response Group queue. [Remove-CsRgsQueue](Remove-CsRgsQueue.md) [Set-CsRgsQueue](Set-CsRgsQueue.md) - diff --git a/skype/skype-ps/skype/Get-CsRgsWorkflow.md b/skype/skype-ps/skype/Get-CsRgsWorkflow.md index 4c159ce97b..2e3ca094e9 100644 --- a/skype/skype-ps/skype/Get-CsRgsWorkflow.md +++ b/skype/skype-ps/skype/Get-CsRgsWorkflow.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csrgsworkflow +online version: https://learn.microsoft.com/powershell/module/skype/get-csrgsworkflow applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRgsWorkflow schema: 2.0.0 @@ -193,4 +193,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsRgsWorkflow](Remove-CsRgsWorkflow.md) [Set-CsRgsWorkflow](Set-CsRgsWorkflow.md) - diff --git a/skype/skype-ps/skype/Get-CsRoutingConfiguration.md b/skype/skype-ps/skype/Get-CsRoutingConfiguration.md index 70e4e8a654..a17cb208b0 100644 --- a/skype/skype-ps/skype/Get-CsRoutingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsRoutingConfiguration schema: 2.0.0 @@ -123,4 +123,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsRoutingConfiguration](Set-CsRoutingConfiguration.md) [Get-CsVoiceRoute](Get-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/Get-CsServerApplication.md b/skype/skype-ps/skype/Get-CsServerApplication.md index eb7915293f..79fa934203 100644 --- a/skype/skype-ps/skype/Get-CsServerApplication.md +++ b/skype/skype-ps/skype/Get-CsServerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csserverapplication +online version: https://learn.microsoft.com/powershell/module/skype/get-csserverapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsServerApplication schema: 2.0.0 @@ -193,4 +193,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsServerApplication](Remove-CsServerApplication.md) [Set-CsServerApplication](Set-CsServerApplication.md) - diff --git a/skype/skype-ps/skype/Get-CsServerPatchVersion.md b/skype/skype-ps/skype/Get-CsServerPatchVersion.md index fb880b6921..707697cc6e 100644 --- a/skype/skype-ps/skype/Get-CsServerPatchVersion.md +++ b/skype/skype-ps/skype/Get-CsServerPatchVersion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csserverpatchversion +online version: https://learn.microsoft.com/powershell/module/skype/get-csserverpatchversion applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsServerPatchVersion schema: 2.0.0 @@ -67,4 +67,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsServerVersion.md b/skype/skype-ps/skype/Get-CsServerVersion.md index 9f40b8f89f..8335546002 100644 --- a/skype/skype-ps/skype/Get-CsServerVersion.md +++ b/skype/skype-ps/skype/Get-CsServerVersion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csserverversion +online version: https://learn.microsoft.com/powershell/module/skype/get-csserverversion applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsServerVersion schema: 2.0.0 @@ -74,4 +74,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsService.md b/skype/skype-ps/skype/Get-CsService.md index 7bd1ec9aea..c0a5253689 100644 --- a/skype/skype-ps/skype/Get-CsService.md +++ b/skype/skype-ps/skype/Get-CsService.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csservice +online version: https://learn.microsoft.com/powershell/module/skype/get-csservice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsService schema: 2.0.0 @@ -863,4 +863,3 @@ For example: [Set-CsUserServer](Set-CsUserServer.md) [Set-CsWebServer](Set-CsWebServer.md) - diff --git a/skype/skype-ps/skype/Get-CsSimpleUrlConfiguration.md b/skype/skype-ps/skype/Get-CsSimpleUrlConfiguration.md index a258d8bddb..aa3aa23c6e 100644 --- a/skype/skype-ps/skype/Get-CsSimpleUrlConfiguration.md +++ b/skype/skype-ps/skype/Get-CsSimpleUrlConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cssimpleurlconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cssimpleurlconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsSimpleUrlConfiguration schema: 2.0.0 @@ -33,12 +33,12 @@ Get-CsSimpleUrlConfiguration [-Filter <String>] [-Tenant <Guid>] [-LocalStore] [ ## DESCRIPTION In Microsoft Office Communications Server 2007 R2, meetings had URLs similar to this: -https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t +`https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t` However, such URLs are not especially intuitive, and not easy to convey to someone else. The simple URLs introduced in Lync Server 2010 helped overcome those problems by providing users with URLs that look more like this: -https://meet.litwareinc.com/kenmyer/071200 +`https://meet.litwareinc.com/kenmyer/071200` Simple URLs are an improvement over the URLs used in Office Communications Server. However, simple URLs are not automatically created for you; instead, you must configure the URLs yourself. @@ -221,4 +221,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsSimpleUrlConfiguration](Remove-CsSimpleUrlConfiguration.md) [Set-CsSimpleUrlConfiguration](Set-CsSimpleUrlConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsSipDomain.md b/skype/skype-ps/skype/Get-CsSipDomain.md index 1287309a6b..0b57d1b663 100644 --- a/skype/skype-ps/skype/Get-CsSipDomain.md +++ b/skype/skype-ps/skype/Get-CsSipDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cssipdomain +online version: https://learn.microsoft.com/powershell/module/skype/get-cssipdomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsSipDomain schema: 2.0.0 @@ -136,4 +136,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsSipDomain](Remove-CsSipDomain.md) [Set-CsSipDomain](Set-CsSipDomain.md) - diff --git a/skype/skype-ps/skype/Get-CsSipResponseCodeTranslationRule.md b/skype/skype-ps/skype/Get-CsSipResponseCodeTranslationRule.md index a0d72c6701..ffac7c3b58 100644 --- a/skype/skype-ps/skype/Get-CsSipResponseCodeTranslationRule.md +++ b/skype/skype-ps/skype/Get-CsSipResponseCodeTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cssipresponsecodetranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/get-cssipresponsecodetranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsSipResponseCodeTranslationRule schema: 2.0.0 @@ -175,4 +175,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsSipResponseCodeTranslationRule](Remove-CsSipResponseCodeTranslationRule.md) [Set-CsSipResponseCodeTranslationRule](Set-CsSipResponseCodeTranslationRule.md) - diff --git a/skype/skype-ps/skype/Get-CsSite.md b/skype/skype-ps/skype/Get-CsSite.md index 7e322d5bb7..fca553017d 100644 --- a/skype/skype-ps/skype/Get-CsSite.md +++ b/skype/skype-ps/skype/Get-CsSite.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cssite +online version: https://learn.microsoft.com/powershell/module/skype/get-cssite applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsSite schema: 2.0.0 @@ -141,4 +141,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsSite](Set-CsSite.md) - diff --git a/skype/skype-ps/skype/Get-CsSlaConfiguration.md b/skype/skype-ps/skype/Get-CsSlaConfiguration.md index 2f36309415..6e91991f77 100644 --- a/skype/skype-ps/skype/Get-CsSlaConfiguration.md +++ b/skype/skype-ps/skype/Get-CsSlaConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csslaconfiguration -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csslaconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsSlaConfiguration schema: 2.0.0 manager: rogupta @@ -133,4 +133,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsStaticRoutingConfiguration.md b/skype/skype-ps/skype/Get-CsStaticRoutingConfiguration.md index dd0c2eca5d..58237d6f2b 100644 --- a/skype/skype-ps/skype/Get-CsStaticRoutingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsStaticRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csstaticroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csstaticroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsStaticRoutingConfiguration schema: 2.0.0 @@ -180,4 +180,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsStaticRoutingConfiguration](Remove-CsStaticRoutingConfiguration.md) [Set-CsStaticRoutingConfiguration](Set-CsStaticRoutingConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsStorageServiceConfiguration.md b/skype/skype-ps/skype/Get-CsStorageServiceConfiguration.md index 45698ae828..c6356193a8 100644 --- a/skype/skype-ps/skype/Get-CsStorageServiceConfiguration.md +++ b/skype/skype-ps/skype/Get-CsStorageServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csstorageserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csstorageserviceconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsStorageServiceConfiguration schema: 2.0.0 @@ -165,4 +165,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsStorageServiceConfiguration](Remove-CsStorageServiceConfiguration.md) [Set-CsStorageServiceConfiguration](Set-CsStorageServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsTeamsAppPermissionPolicy.md b/skype/skype-ps/skype/Get-CsTeamsAppPermissionPolicy.md deleted file mode 100644 index cd249da58a..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsAppPermissionPolicy.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsapppermissionpolicy -applicable: Skype for Business Online -title: Get-CsTeamsAppPermissionPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Get-CsTeamsAppPermissionPolicy - -## SYNOPSIS - -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - - -## EXAMPLES - -### Example 1 -Intentionally omitted. - -## PARAMETERS - -### -Filter -Do not use - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Do not use. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -{{Fill Tenant Description}} - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsAppSetupPolicy.md b/skype/skype-ps/skype/Get-CsTeamsAppSetupPolicy.md deleted file mode 100644 index bd799eadef..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsAppSetupPolicy.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsappsetuppolicy -applicable: Skype for Business Online -title: Get-CsTeamsAppSetupPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Get-CsTeamsAppSetupPolicy - -## SYNOPSIS - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsAppSetupPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsAppSetupPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## EXAMPLES - -### Example 1 -Intentionally not provided - -## PARAMETERS - -### -Filter -Do not use. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Do not use. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Do not use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md b/skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md deleted file mode 100644 index fbebf13350..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamscallingpolicy -applicable: Skype for Business Online -title: Get-CsTeamsCallingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTeamsCallingPolicy - -## SYNOPSIS - -Returns information about the teams calling policies configured for use in your organization. -Teams calling policies help determine which users are able to use calling functionality within Microsoft Teams. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsCallingPolicy [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsCallingPolicy [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION - -Returns information about the teams calling policies configured for use in your organization. -Teams calling policies help determine which users are able to use calling functionality within Microsoft Teams and interoperability with Skype for Business. - -## EXAMPLES - -### Example 1 -```powershell -Get-CsTeamsCallingPolicy -Identity SalesCallingPolicy -``` - -Retrieves the calling policy with name "SalesCallingPolicy" - -## PARAMETERS - -### -Filter -Enables you to use wildcard characters when indicating the policy (or policies) to be returned. -To return a collection of all the per-user policies, use this syntax: -Filter "tag:*". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the TeamsCallingPolicy that you would like to retrieve. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -Microsoft internal use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Microsoft internal use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsChannelsPolicy.md b/skype/skype-ps/skype/Get-CsTeamsChannelsPolicy.md deleted file mode 100644 index c567132b6f..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsChannelsPolicy.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamschannelspolicy -applicable: Skype for Business Online -title: Get-CsTeamsChannelsPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTeamsChannelsPolicy - -## SYNOPSIS - -The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsChannelsPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsChannelsPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. The Get-CsTeamsChannelsPolicy returns policies that are available for use within your organization. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-CsTeamsCallParkPolicy -``` - -Retrieve all policies that are available in your organization. - - -## PARAMETERS - -### -Filter -Enables you to use wildcard characters when indicating the policy (or policies) to be returned. For example, to return a collection of all the per-user policies, use this syntax: -Filter "tag:". - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the unique name of a policy you would like to retrieve - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -Internal Microsoft use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsEmergencyCallRoutingPolicy.md b/skype/skype-ps/skype/Get-CsTeamsEmergencyCallRoutingPolicy.md deleted file mode 100644 index f89345fa2c..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsEmergencyCallRoutingPolicy.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsemergencycallroutingpolicy -applicable: Skype for Business Online -title: Get-CsTeamsEmergencyCallRoutingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Get-CsTeamsEmergencyCallRoutingPolicy - -## SYNOPSIS - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsEmergencyCallRoutingPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsEmergencyCallRoutingPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] - [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet returns one or more Emergency Call Routing policy. This Policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Get-CsTeamsEmergencyCallRoutingPolicy -``` - - Retrieves all emergency call routing policies that are available in your scope - -### Example 2 -```powershell -PS C:> Get-CsTeamsEmergencyCallRoutingPolicy -Identity TestECRP -``` - - Retrieves one emergency call routing policy specifying the identity - -## PARAMETERS - -### -Filter - The Filter parameter allows you to limit the number of results based on filters you specify. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - Specify the policy that you would like to retrieve. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore - Microsoft internal use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - Microsoft internal use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsEmergencyCallingPolicy.md b/skype/skype-ps/skype/Get-CsTeamsEmergencyCallingPolicy.md deleted file mode 100644 index 55e0a4c459..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsEmergencyCallingPolicy.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsemergencycallingpolicy -applicable: Skype for Business Online -title: Get-CsTeamsEmergencyCallingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Get-CsTeamsEmergencyCallingPolicy - -## SYNOPSIS - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsEmergencyCallingPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsEmergencyCallingPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet returns one or more emergency calling policies. Emergency calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Get-CsTeamsEmergencyCallingPolicy -``` - - Retrieves all emergency calling policies that are available in your scope - -### Example 2 -```powershell -PS C:> Get-CsTeamsEmergencyCallingPolicy -Identity TestECP -``` - - Retrieves emergency calling policy specifying the identity - -## PARAMETERS - -### -Filter - The Filter parameter allows you to limit the number of results based on filters you specify. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - Specify the policy that you would like to retrieve. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore - Microsoft internal use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsGuestMessagingConfiguration.md b/skype/skype-ps/skype/Get-CsTeamsGuestMessagingConfiguration.md deleted file mode 100644 index 98fa70e165..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsGuestMessagingConfiguration.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsguestmessagingconfiguration -applicable: Skype for Business Online -title: Get-CsTeamsGuestMessagingConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTeamsGuestMessagingConfiguration - -## SYNOPSIS -TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. This cmdlet returns your organization's current settings. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [-Filter <String>] [-LocalStore] - [<CommonParameters>] -``` - -## DESCRIPTION -TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. - -## EXAMPLES - -### Example 1 -``` -Get-CsTeamsGuestMessagingConfiguration -``` - -The command shown in Example 1 returns teams guest messaging configuration information for the current tenant - -## PARAMETERS - -### -Filter -Enables you to use wildcard characters in order to return a collection of tenant guest messaging configuration settings. -Because each tenant is limited to a single, global collection of guest messaging configuration settings there is no need to use the Filter parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the collection of tenant guest messaging configuration settings to be returned. -Because each tenant is limited to a single, global collection of guest messaging settings there is no need include this parameter when calling the cmdlet. -If you do choose to use the Identity parameter you must also include the Tenant parameter. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is not used with Skype for Business Online. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsTeamsTranslationRule.md b/skype/skype-ps/skype/Get-CsTeamsTranslationRule.md deleted file mode 100644 index 2bc3d4373d..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsTranslationRule.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamstranslationrule -applicable: Skype for Business Online -title: Get-CsTeamsTranslationRule -schema: 2.0.0 -manager: nmurav -author: filippse -ms.author: filippse -ms.reviewer: ---- - -# Get-CsTeamsTranslationRule - -## SYNOPSIS -Cmdlet to get an existing number manipulation rule (or list of rules). - -## SYNTAX - -``` -Get-CsTeamsTranslationRule [-LocalStore] [-Filter <Object>] [-Tenant <string>] [[-Identity] <string>] [-AsJob] -``` - -## DESCRIPTION -You can use this cmdlet to get an existing number manipulation rule (or list of rules). The rule can be used, for example, in the settings of your SBC (Set-CSOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-CsTeamsTranslationRule -``` - -This command will show all translation rules that exist in the tenant. Identity, Description, Pattern and Translation parameters listed for each rule. - -### Example 2 -```powershell -PS C:\> Get-CsTeamsTranslationRule -Identity AddPlus1 -``` - -This command will show Identity, Description, Pattern and Translation parameters for "AddPlus1" rule - - -## PARAMETERS - -### -Identity -Identifier of the rule. This parameter is required and later used to assign the rule to Inbound or Outbound Trunk Normalization policy. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose number manipulation rule is being evoked. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsUpgradeConfiguration.md b/skype/skype-ps/skype/Get-CsTeamsUpgradeConfiguration.md index 6611e9e6a7..4c98490cbe 100644 --- a/skype/skype-ps/skype/Get-CsTeamsUpgradeConfiguration.md +++ b/skype/skype-ps/skype/Get-CsTeamsUpgradeConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsupgradeconfiguration -applicable: Skype for Business Online, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csteamsupgradeconfiguration +applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTeamsUpgradeConfiguration schema: 2.0.0 manager: bulenteg @@ -124,4 +124,4 @@ These settings are only honored by newer versions of Skype for Business clients. [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) diff --git a/skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md b/skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md index 0553a215d5..69d65757c9 100644 --- a/skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md +++ b/skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsupgradepolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csteamsupgradepolicy applicable: Skype for Business Online, Skype for Business Server 2019, Skype for Business Server 2015 title: Get-CsTeamsUpgradePolicy schema: 2.0.0 @@ -15,6 +15,9 @@ ms.reviewer: rogupta ## SYNOPSIS TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. +> [!IMPORTANT] +> It can take up to 24 hours for a change to TeamsUpgradePolicy to take effect. Before then, user presence status may not be correct (may show as **Unknown**). + ## SYNTAX @@ -36,7 +39,7 @@ NOTES: - If you are using Skype for Business Server, there are no built-in instances and you'll need to create one. Also, only the NotifySfBUsers property is available. Mode is not present. - Using TeamsUpgradePolicy in an on-premises environmention requires Skype for Business Server 2015 with CU8 or later. -You can also find more guidance here: [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype). +You can also find more guidance here: [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype). ## EXAMPLES @@ -194,5 +197,4 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) - +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) diff --git a/skype/skype-ps/skype/Get-CsTeamsUpgradeStatus.md b/skype/skype-ps/skype/Get-CsTeamsUpgradeStatus.md deleted file mode 100644 index 382bb8823b..0000000000 --- a/skype/skype-ps/skype/Get-CsTeamsUpgradeStatus.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsupgradestatus -applicable: Skype for Business Online -title: Get-CsTeamsUpgradeStatus -schema: 2.0.0 -manager: -author: salarson -ms.author: salarson -ms.reviewer: ---- - -# Get-CsTeamsUpgradeStatus - -## SYNOPSIS -Returns information related to the Microsoft-driven automated upgrade status from Skype for Business Online to Teams. - - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsUpgradeStatus [-Tenant <Guid>] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsUpgradeStatus [-Tenant <Guid>] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -TeamsUpgradeStatus is used to check the status of customers eligible for Microsoft-driven automated upgrade of Skype for Business Online to Teams. - -You can also find more guidance here: [Getting started with your Microsoft Teams upgrade](https://docs.microsoft.com/MicrosoftTeams/upgrade-start-here). - -## EXAMPLES - -### Example 1: The below example shows an example of TeamsUpgradeStatus with the tenant being scheduled for Microsoft-driven automated upgrade. - -> [!NOTE] -> The PowerShell results get populated at the same time upgrade notification is sent and may be null if the tenant is not yet notified. - -``` -PS C:\> Get-CsTeamsUpgradeStatus - -TenantId : ca573b31-a0db-4185-951e-3af848668397 -State : ScheduledForUpgrade -OptInEligibleDate : 2018-04-12 18:06:36Z -UpgradeScheduledDate : 2018-06-15 00:00:00Z -UserNotificationDate : 2018-07-05 00:00:00Z -UpgradeDate : 2018-07-10 00:00:00Z -LastStateChangeDate : 2018-06-06 22:52:21Z - - -``` - -For more information on the results from the above example please reference the table below: - -* State: Tenant is scheduled to be upgraded via automated upgrade on the date returned. -* OptInEligbleDate: Tenant is OptInEligible since 2018-04-12 18:06:36Z. (tenant admin can upgrade users on own since 2018-04-12 18:06:36Z) -* UpgradeScheduledDate: Tenant's upgrade is/was scheduled to start at 2018-06-15 00:00:00Z. (When the tenant was first notified of the upgrade via the M365 Message Center) -* UserNotificationDate: Tenant's end users will be/were notified starting 2018-07-05 00:00:00Z via SfB Client. -* UpgradeDate: Tenant will be/was upgraded by Microsoft at 2018-07-10 00:00:00Z -* LastStateChangeDate: Tenant's state was last changed at 2018-06-06 22:52:21Z. - -For more information on the various upgrade "States" please reference the table below: - -* Null - Tenant isn't yet in the automated upgrade system. -* OptInEligible - Tenant will be invited to a Microsoft driven upgrade at some point in the future. -* ScheduledForUpgrade - Tenant is scheduled to be upgraded via automated upgrade on the date returned. This refers to the date that the tenant was first scheduled. Admins who click the Postpone button in the Teams Admin Portal will see the UpgradeDate move out 30 days but will not see a change in the Upgrade ScheduledDate field nor the OptInEligibleDate field. -* Upgraded - Date that Tenant will be or has been upgraded. -* Exempt - Tenant is exempt from Microsoft driven upgrade currently. - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### None -## NOTES - -## RELATED LINKS - -[Get-CsTeamsUpgradeConfiguration](Get-CsTeamsUpgradeConfiguration.md) - -[Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) - -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) - -[Skype for Business Online retirement on July 31, 2021](https://support.microsoft.com/en-us/help/4511540/retirement-of-skype-for-business-online) - -[Upgrade Basic guidance](https://docs.microsoft.com/en-us/MicrosoftTeams/upgrade-basic) - -[Transitioning from Skype for Business to Microsoft Teams via FastTrack](https://www.microsoft.com/en-us/fasttrack/skype-for-business-transition-to-teams?rtc=1) diff --git a/skype/skype-ps/skype/Get-CsTelemetryConfiguration.md b/skype/skype-ps/skype/Get-CsTelemetryConfiguration.md index 1a7ca78933..53ce0dee66 100644 --- a/skype/skype-ps/skype/Get-CsTelemetryConfiguration.md +++ b/skype/skype-ps/skype/Get-CsTelemetryConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstelemetryconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cstelemetryconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTelemetryConfiguration schema: 2.0.0 @@ -122,4 +122,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsTenant.md b/skype/skype-ps/skype/Get-CsTenant.md deleted file mode 100644 index 65160645bd..0000000000 --- a/skype/skype-ps/skype/Get-CsTenant.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenant -applicable: Skype for Business Online -title: Get-CsTenant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenant - -## SYNOPSIS -Returns information about the Skype for Business Online tenants that have been configured for use in your organization. -Tenants represent groups of online users. - -## SYNTAX - -``` -Get-CsTenant [-Filter <String>] [-DomainController <Fqdn>] [[-Identity] <OUIdParameter>] [-ResultSize <Int32>] - [<CommonParameters>] -``` - -## DESCRIPTION -In Skype for Business Online, tenants are groups of users who have accounts homed on the service. -Organizations will typically have a single tenant in which to house all their user accounts. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsTenant -``` - -The command shown in Example 1 returns information about your tenant. -Organizations will have only one tenant. - - -## PARAMETERS - -### -DomainController -This parameter is not used with Skype for Business Online. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Filter -Enables you to return data by using Active Directory attributes and without having to specify the full Active Directory distinguished name. -For example, to retrieve a tenant by using the tenant display name, use syntax similar to this: - -Get-CsTenant -Filter {DisplayName -eq "FabrikamTenant"} - -To return all tenants that use a Fabrikam domain use this syntax: - -Get-CsTenant -Filter {Domains -like "*fabrikam*"} - -The Filter parameter uses the same Windows PowerShell filtering syntax is used by the `Where-Object` cmdlet. - -You cannot use both the Identity parameter and the Filter parameter in the same command. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the tenant. -For example: - --Identity "bf19b7db-6960-41e5-a139-2aa373474354" - -If you do not include either the Identity or the Filter parameter then the `Get-CsTenant` cmdlet will return information about all your tenants. - -```yaml -Type: OUIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResultSize -Enables you to limit the number of records returned by the cmdlet. -For example, to return seven tenants (regardless of the number of tenants that are in your forest) include the ResultSize parameter and set the parameter value to 7. -Note that there is no way to guarantee which 7 users will be returned. - -The result size can be set to any whole number between 0 and 2147483647, inclusive. -If set to 0 the command will run, but no data will be returned. -If you set the tenants to 7 but you have only three contacts in your forest, the command will return those three tenants and then complete without error. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### Microsoft.Rtc.Management.ADConnect.Schema.TenantObject or String -The `Get-CsTenant` cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.ADConnect.Schema.TenantObject object as well as string values representing the Identity of the tenant (for example "bf19b7db-6960-41e5-a139-2aa373474354"). - -## OUTPUTS - -### Microsoft.Rtc.Management.ADConnect.Schema.TenantObject - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsTenantBlockedCallingNumbers.md b/skype/skype-ps/skype/Get-CsTenantBlockedCallingNumbers.md deleted file mode 100644 index 5f9ca0e882..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantBlockedCallingNumbers.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -applicable: Skype for Business Online -title: Get-CsTenantBlockedCallingNumbers -schema: 2.0.0 -manager: roykuntz -author: junya -ms.author: junya ---- - -# Get-CsTenantBlockedCallingNumbers - -## SYNOPSIS -Use the Get-CsTenantBlockedCallingNumbers cmdlet to retrieve tenant blocked calling numbers setting. - -## SYNTAX - -``` -Get-CsTenantBlockedCallingNumbers [[-Identity] <Object>] [-Tenant <Object>] [-Filter <Object>] [-LocalStore] - [-AsJob] -``` - -## DESCRIPTION -Skype for Business Online Calling Plans now supports blocking of inbound calls from the public switched telephone network (PSTN). This feature allows a tenant-global list of number patterns to be defined so that the caller ID of every incoming PSTN call to the tenant can be checked against the list for a match. If a match is made, an incoming call is rejected. - -The tenant blocked calling numbers includes a list of inbound blocked number patterns. Number patterns are managed through the CsInboundBlockedNumberPattern commands New, Get, Set, and Remove. You can manage a given pattern by using these cmdlets, including the ability to toggle the activation of a given pattern. - -The scope of tenant blocked calling numbers is global across the given tenant. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsTenantBlockedCallingNumbers -``` - -This example returns the tenant global settings for blocked calling numbers. It includes a list of inbound blocked number patterns. - -## PARAMETERS - -### -Filter -The Filter parameter allows you to limit the number of results based on filters you specify. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter is a unique identifier that designates the scope, and for per-user scope a name, which identifies the TenantBlockedCallingNumbers to retrieve. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308". -You can find your tenant ID by running this command: Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS -[Set-CsTenantBlockedCallingNumbers](Set-CsTenantBlockedCallingNumbers.md) \ No newline at end of file diff --git a/skype/skype-ps/skype/Get-CsTenantBlockedNumberExceptionPattern.md b/skype/skype-ps/skype/Get-CsTenantBlockedNumberExceptionPattern.md deleted file mode 100644 index f412e2e792..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantBlockedNumberExceptionPattern.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantblockednumberexceptionpattern -applicable: Skype for Business Online -title: Get-CsTenantBlockedNumberExceptionPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# Get-CsTenantBlockedNumberExceptionPattern - -## SYNOPSIS - -## SYNTAX - -### Identity (Default) -``` -Get-CsTenantBlockedNumberExceptionPattern [-Tenant <System.Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] - [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsTenantBlockedNumberExceptionPattern [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] - [<CommonParameters>] -``` - -## DESCRIPTION -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 -```powershell -PS C:> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -Filter -{{ Fill Filter Description }} - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -{{ Fill Identity Description }} - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -{{ Fill LocalStore Description }} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -{{ Fill Tenant Description }} - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTenantDialPlan.md b/skype/skype-ps/skype/Get-CsTenantDialPlan.md deleted file mode 100644 index 3980bcdb53..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantDialPlan.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantdialplan -applicable: Skype for Business Online -title: Get-CsTenantDialPlan -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenantDialPlan - -## SYNOPSIS -Use the Get-CsTenantDialPlan cmdlet to retrieve a tenant dial plan. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTenantDialPlan [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsTenantDialPlan [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsTenantDialPlan cmdlet returns information about one or more tenant dial plans (also known as a location profiles) in an organization. -Tenant dial plans provide required information to let Enterprise Voice users make telephone calls. -The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. -A tenant dial plan determines such things as which normalization rules are applied, and whether a prefix must be dialed for external calls. - -You can use the Get-CsTenantDialPlan cmdlet to retrieve specific information about the normalization rules of a tenant dial plan. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsTenantDialPlan -``` - -This example retrieves a tenant dial plan. - - - -### -------------------------- Example 2 -------------------------- -``` -Get-CsTenantDialPlan -Identity Vt1TenantDialPlan2 -``` - -This example retrieves the tenant dial plan that is within the scope of Vt1TenantDialplan2. - - -## PARAMETERS - -### -Filter -The Filter parameter allows you to limit the number of results based on filters you specify. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter is a unique identifier that designates the scope, and for per-user scope a name, which identifies the tenant dial plan to retrieve. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308". -You can find your tenant ID by running this command: Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsTenantHybridConfiguration.md b/skype/skype-ps/skype/Get-CsTenantHybridConfiguration.md index 6d9b663c13..af7842ce10 100644 --- a/skype/skype-ps/skype/Get-CsTenantHybridConfiguration.md +++ b/skype/skype-ps/skype/Get-CsTenantHybridConfiguration.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenanthybridconfiguration -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/skype/get-cstenanthybridconfiguration +applicable: Skype for Business Server 2019 title: Get-CsTenantHybridConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTenantHybridConfiguration @@ -16,6 +16,8 @@ ms.reviewer: Returns values for the hybrid configuration settings that enable users homed on Skype for Business Online to have access to Enterprise Voice features such as media bypass, Enhanced 9-1-1, and call parking. A hybrid scenario (also known as a split-domain scenario) is a Skype for Business Server deployment in which some users have accounts homed on-premises while other users have accounts homed on Skype for Business Online. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -152,22 +154,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -188,4 +174,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Set-CsTenantHybridConfiguration](Set-CsTenantHybridConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsTenantLicensingConfiguration.md b/skype/skype-ps/skype/Get-CsTenantLicensingConfiguration.md deleted file mode 100644 index c12690075d..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantLicensingConfiguration.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantlicensingconfiguration -applicable: Skype for Business Online -title: Get-CsTenantLicensingConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenantLicensingConfiguration - -## SYNOPSIS -Indicates whether licensing information for the specified tenant is available in the Lync admin center. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTenantHybridConfiguration [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTenantHybridConfiguration [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -The Get-CsTenantLicensingConfiguration cmdlet indicates whether licensing information for the specified tenant is available in the Lync admin center. -The cmdlet returns information similar to this: - -Identity : GlobalStatus : Enabled - -If the Status is equal to Enabled then licensing information is available in the admin center. -If not, then licensing information is not available in the admin center. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsTenantLicensingConfiguration -``` - -The command shown in Example 1 returns licensing configuration information for the current tenant: - - -## PARAMETERS - -### -Filter -Enables you to use wildcard characters in order to return a collection of tenant licensing configuration settings. -Because each tenant is limited to a single, global collection of licensing configuration settings there is no need to use the Filter parameter. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the collection of tenant licensing configuration settings to be returned. -Because each tenant is limited to a single, global collection of licensing settings there is no need include this parameter when calling the Get-CsTenantLicensingConfiguration cmdlet. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is not used with Skype for Business Online. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose licensing settings are being returned. -For example: - -`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` - -You can return your tenant ID by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### Deserialized.Microsoft.Rtc.Management.WritableConfig.Settings.TenantConfiguration.TenantLicensingConfiguration - - -## NOTES - - -## RELATED LINKS - -[Get-CsTenant](Get-CsTenant.md) - diff --git a/skype/skype-ps/skype/Get-CsTenantMigrationConfiguration.md b/skype/skype-ps/skype/Get-CsTenantMigrationConfiguration.md deleted file mode 100644 index ae1602a91d..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantMigrationConfiguration.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantmigrationconfiguration -applicable: Skype for Business Online -title: Get-CsTenantMigrationConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenantMigrationConfiguration - -## SYNOPSIS -Use the Get-CsTenantMigrationConfiguration cmdlet to check if Meeting Migration Service (MMS) is enabled in your organization. - -## SYNTAX - -``` -Get-CsTenantMigrationConfiguration [-LocalStore] [[-Identity] <XdsIdentity>] [-Tenant <Guid>] [-Filter <String>] - [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -Meeting Migration Service (MMS) is a Skype for Business service that runs in the background and automatically updates Skype for Business and Microsoft Teams meetings for users. MMS is designed to eliminate the need for users to run the Meeting Migration Tool to update their Skype for Business and Microsoft Teams meetings. This tool does not migrate Skype for Business meetings into Microsoft Teams meetings. - -The Get-CsTenantMigrationConfiguration cmdlet retrieves the Meeting Migration Service configuration in your organization. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Get-CsTenantMigrationConfiguration -``` - -This example shows the MMS configuration in your organization. - -## PARAMETERS - -### -Filter -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Set-CsTenantMigrationConfiguration](https://docs.microsoft.com/powershell/module/skype/set-cstenantmigrationconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Get-CsTenantNetworkRegion.md b/skype/skype-ps/skype/Get-CsTenantNetworkRegion.md deleted file mode 100644 index 0a45702fa8..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantNetworkRegion.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantnetworkregion -applicable: Skype for Business Online -title: Get-CsTenantNetworkRegion -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenantNetworkRegion - -## SYNOPSIS -Returns information about the network region setting in the tenant. Tenant network region is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTenantNetworkRegion [-Tenant <System.Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTenantNetworkRegion [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -A network region interconnects various parts of a network across multiple geographic areas. - -A network region contains a collection of network sites. For example, if your organization has many sites located in India, then you may choose to designate "India" as a network region. - -Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user's geographic location at the time of an incoming or outgoing PSTN call. - -Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Get-CsTenantNetworkRegion -``` - -The command shown in Example 1 returns the list of network regions for the current tenant. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> Get-CsTenantNetworkRegion -Identity RedmondRegion -``` - -The command shown in Example 2 returns the network region within the scope of RedmondRegion. - -## PARAMETERS - -### -Filter -The Filter parameter allows you to limit the number of results based on filters you specify. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network region to be returned. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network regions are being returned. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTenantNetworkSite.md b/skype/skype-ps/skype/Get-CsTenantNetworkSite.md deleted file mode 100644 index 1b27e623f7..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantNetworkSite.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantnetworksite -applicable: Skype for Business Online -title: Get-CsTenantNetworkSite -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenantNetworkSite - -## SYNOPSIS -Returns information about the network site setting in the tenant. Tenant network site is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTenantNetworkSite [-Tenant <System.Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTenantNetworkSite [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. - -A best practice for Location Bsed Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity. Each network site must be associated with a network region. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration. - -Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user's geographic location at the time of an incoming or outgoing PSTN call. - -Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Get-CsTenantNetworkSite -``` - -The command shown in Example 1 returns the list of network sites for the current tenant. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> Get-CsTenantNetworkSite -Identity siteA -``` - -The command shown in Example 2 returns the network site within the scope of siteA. - -## PARAMETERS - -### -Filter -The Filter parameter allows you to limit the number of results based on filters you specify. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network site to be returned. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network sites are being returned. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTenantNetworkSubnet.md b/skype/skype-ps/skype/Get-CsTenantNetworkSubnet.md deleted file mode 100644 index 5d1445e9a0..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantNetworkSubnet.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantnetworksubnet -applicable: Skype for Business Online -title: Get-CsTenantNetworkSubnet -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenantNetworkSubnet - -## SYNOPSIS -Returns information about the network subnet setting in the tenant. Tenant network subnet is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTenantNetworkSubnet [-Tenant <System.Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTenantNetworkSubnet [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. - -Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first. - -Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user's geographic location at the time of an incoming or outgoing PSTN call. - -Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Get-CsTenantNetworkSubnet -``` - -The command shown in Example 1 returns the list of network subnets for the current tenant. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> Get-CsTenantNetworkSubnet -Identity '2001:4898:e8:25:844e:926f:85ad:dd70' -``` - -The command shown in Example 2 returns the IPv6 format network subnet within the scope of '2001:4898:e8:25:844e:926f:85ad:dd70'. - -## PARAMETERS - -### -Filter -The Filter parameter allows you to limit the number of results based on filters you specify. - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network subnet to be returned. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network subnets are being returned. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTenantPublicProvider.md b/skype/skype-ps/skype/Get-CsTenantPublicProvider.md deleted file mode 100644 index 2aa676fce4..0000000000 --- a/skype/skype-ps/skype/Get-CsTenantPublicProvider.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantpublicprovider -applicable: Skype for Business Online -title: Get-CsTenantPublicProvider -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Get-CsTenantPublicProvider - -## SYNOPSIS -Returns information indicating whether Skype for Business Online users are allowed to communicate with people who have accounts on the third-party IM and presence providers Windows Live, AOL, and Yahoo. - -## SYNTAX - -``` -Get-CsTenantPublicProvider [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -Public providers are organizations that provide SIP communication services for the general public. -When you establish a federation relationship with a public provider, you effectively establish federation with any user who has an account hosted by that provider. -For example, if you federate with Windows Live, then your users will be able to exchange instant messages and presence information with anyone who has a Windows Live instant messaging account. - -Skype for Business Online gives administrators the option of configuring federation with one or more of the following public IM and presence providers: - -Windows Live - -AOL - -Yahoo! - -Administrators can use the Get-CsTenantPublicProvider cmdlet to determine which of those providers (if any) have been enabled for federation. -When you call the Get-CsTenantPublicProvider cmdlet you will get back information similar to this: - -PublicProviderSet DomainPicStatus - ------------------- ------------------------ - -True {Microsoft.Rtc.Management.Hosted.DomainPICStatus} - -The PublicProviderSet property indicates whether or not federation has been enabled for one or more public provider. -If PublicProviderSet is equal to True then that means federation has been enabled with at least one provider; if PublicProviderSet is equal to False then that means that federation is disabled for all three public providers (Windows Live, AOL, and Yahoo). -To determine the actual status of each provider use this command: - -Get-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" | Select-Object -ExpandProperty DomainPICStatus - -Note that simply enabling the status of a public provider does not mean that users can exchange instant messages and presence information with users who have accounts on that provider. -In addition to enabling federation with the provider itself, administrators must also set the AllowPublicUsers property of the federation configuration settings to True. -If this property is set to False then communication will not be allowed with any of the public providers, regardless of the public provider configuration settings. - -For more information, see the help topic for the Set-CsTenantFederationConfiguration cmdlet. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Get-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" | Select-Object -ExpandProperty DomainPICStatus -``` - -Example 1 returns detailed information about the status of all the public providers assigned to the tenant bf19b7db-6960-41e5-a139-2aa373474354. -To do this, the command first uses the Get-CsTenantPublicProvider cmdlet to return public provider information for the specified tenant. -That information is then piped to the Select-Object cmdlet, which uses the ExpandProperty parameter to "expand" the value of the DomainPICStatus property. -Expanding a property simply means displaying all the values stored in that property onscreen, and in an easy-to-read format. - -### -------------------------- Example 2 -------------------------- -``` -Get-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" | Select-Object -ExpandProperty DomainPICStatus | Where-Object {$_.Status -eq "Enabled"} -``` - -The command shown in Example 23 is a variation of the command shown in Example 1. -In Example 2, however, the public provider information returned by "expanding" the value of the DomainPICStatus property is, in turn, piped to the Where-Object cmdlet. -The Where-Object cmdlet then picks out only those providers where the Status property is set to Enabled. -The net effect is to display only those public providers that are enabled for use. - - -## PARAMETERS - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose public provider settings are being returned. -For example: - -`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` - -You can return your tenant ID by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.TenantPICStatus - - -## NOTES - - -## RELATED LINKS - -[Get-CsTenantFederationConfiguration](Get-CsTenantFederationConfiguration.md) - -[Set-CsTenantPublicProvider](Set-CsTenantPublicProvider.md) - diff --git a/skype/skype-ps/skype/Get-CsTenantUpdateTimeWindow.md b/skype/skype-ps/skype/Get-CsTenantUpdateTimeWindow.md index 1ab4688a61..375176efc1 100644 --- a/skype/skype-ps/skype/Get-CsTenantUpdateTimeWindow.md +++ b/skype/skype-ps/skype/Get-CsTenantUpdateTimeWindow.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantupdatetimewindow +online version: https://learn.microsoft.com/powershell/module/skype/get-cstenantupdatetimewindow applicable: Skype for Business Online title: Get-CsTenantUpdateTimeWindow schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTenantUpdateTimeWindow @@ -121,22 +121,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -147,4 +131,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsTestDevice.md b/skype/skype-ps/skype/Get-CsTestDevice.md index 4d0d6d508d..079667d0d1 100644 --- a/skype/skype-ps/skype/Get-CsTestDevice.md +++ b/skype/skype-ps/skype/Get-CsTestDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstestdevice +online version: https://learn.microsoft.com/powershell/module/skype/get-cstestdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTestDevice schema: 2.0.0 @@ -171,4 +171,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsTestDevice](Remove-CsTestDevice.md) [Set-CsTestDevice](Set-CsTestDevice.md) - diff --git a/skype/skype-ps/skype/Get-CsTestUserCredential.md b/skype/skype-ps/skype/Get-CsTestUserCredential.md index bb51a50675..328d03a5ff 100644 --- a/skype/skype-ps/skype/Get-CsTestUserCredential.md +++ b/skype/skype-ps/skype/Get-CsTestUserCredential.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstestusercredential +online version: https://learn.microsoft.com/powershell/module/skype/get-cstestusercredential applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTestUserCredential schema: 2.0.0 @@ -116,4 +116,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsTestUserCredential](Remove-CsTestUserCredential.md) [Set-CsTestUserCredential](Set-CsTestUserCredential.md) - diff --git a/skype/skype-ps/skype/Get-CsThirdPartyVideoSystem.md b/skype/skype-ps/skype/Get-CsThirdPartyVideoSystem.md index c770963e28..eec5a7e4a6 100644 --- a/skype/skype-ps/skype/Get-CsThirdPartyVideoSystem.md +++ b/skype/skype-ps/skype/Get-CsThirdPartyVideoSystem.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csthirdpartyvideosystem +online version: https://learn.microsoft.com/powershell/module/skype/get-csthirdpartyvideosystem applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsThirdPartyVideoSystem schema: 2.0.0 @@ -252,4 +252,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsThirdPartyVideoSystemPolicy.md b/skype/skype-ps/skype/Get-CsThirdPartyVideoSystemPolicy.md index e1f2c87c2d..372623ffd8 100644 --- a/skype/skype-ps/skype/Get-CsThirdPartyVideoSystemPolicy.md +++ b/skype/skype-ps/skype/Get-CsThirdPartyVideoSystemPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csthirdpartyvideosystempolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csthirdpartyvideosystempolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsThirdPartyVideoSystemPolicy schema: 2.0.0 @@ -199,4 +199,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsThirdPartyVideoSystem](Remove-CsThirdPartyVideoSystem.md) [Set-CsThirdPartyVideoSystemPolicy](Set-CsThirdPartyVideoSystemPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsTopology.md b/skype/skype-ps/skype/Get-CsTopology.md index b6398ae51d..4f487076f5 100644 --- a/skype/skype-ps/skype/Get-CsTopology.md +++ b/skype/skype-ps/skype/Get-CsTopology.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstopology +online version: https://learn.microsoft.com/powershell/module/skype/get-cstopology applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTopology schema: 2.0.0 @@ -122,4 +122,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Publish-CsTopology](Publish-CsTopology.md) [Test-CsTopology](Test-CsTopology.md) - diff --git a/skype/skype-ps/skype/Get-CsTrunk.md b/skype/skype-ps/skype/Get-CsTrunk.md index 7e48d07493..96dffbef9c 100644 --- a/skype/skype-ps/skype/Get-CsTrunk.md +++ b/skype/skype-ps/skype/Get-CsTrunk.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstrunk +online version: https://learn.microsoft.com/powershell/module/skype/get-cstrunk applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTrunk schema: 2.0.0 @@ -164,4 +164,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Get-CsTrunkConfiguration](Get-CsTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsTrunkConfiguration.md b/skype/skype-ps/skype/Get-CsTrunkConfiguration.md index a285e08f5d..c3be85f003 100644 --- a/skype/skype-ps/skype/Get-CsTrunkConfiguration.md +++ b/skype/skype-ps/skype/Get-CsTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cstrunkconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTrunkConfiguration schema: 2.0.0 @@ -140,4 +140,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Set-CsTrunkConfiguration](Set-CsTrunkConfiguration.md) [Test-CsTrunkConfiguration](Test-CsTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsTrustedApplication.md b/skype/skype-ps/skype/Get-CsTrustedApplication.md index 693516e384..b4d37f606f 100644 --- a/skype/skype-ps/skype/Get-CsTrustedApplication.md +++ b/skype/skype-ps/skype/Get-CsTrustedApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstrustedapplication +online version: https://learn.microsoft.com/powershell/module/skype/get-cstrustedapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTrustedApplication schema: 2.0.0 @@ -192,4 +192,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [Remove-CsTrustedApplication](Remove-CsTrustedApplication.md) [Set-CsTrustedApplication](Set-CsTrustedApplication.md) - diff --git a/skype/skype-ps/skype/Get-CsTrustedApplicationComputer.md b/skype/skype-ps/skype/Get-CsTrustedApplicationComputer.md index b93776351c..17ccc65a5d 100644 --- a/skype/skype-ps/skype/Get-CsTrustedApplicationComputer.md +++ b/skype/skype-ps/skype/Get-CsTrustedApplicationComputer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstrustedapplicationcomputer +online version: https://learn.microsoft.com/powershell/module/skype/get-cstrustedapplicationcomputer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTrustedApplicationComputer schema: 2.0.0 @@ -173,4 +173,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [New-CsTrustedApplicationComputer](New-CsTrustedApplicationComputer.md) [Remove-CsTrustedApplicationComputer](Remove-CsTrustedApplicationComputer.md) - diff --git a/skype/skype-ps/skype/Get-CsTrustedApplicationEndpoint.md b/skype/skype-ps/skype/Get-CsTrustedApplicationEndpoint.md index 2158976cb3..d41c6cd9e1 100644 --- a/skype/skype-ps/skype/Get-CsTrustedApplicationEndpoint.md +++ b/skype/skype-ps/skype/Get-CsTrustedApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstrustedapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/get-cstrustedapplicationendpoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTrustedApplicationEndpoint schema: 2.0.0 @@ -228,4 +228,3 @@ Accepts a pipelined string value representing the Identity of a user account. [Remove-CsTrustedApplicationEndpoint](Remove-CsTrustedApplicationEndpoint.md) [Set-CsTrustedApplicationEndpoint](Set-CsTrustedApplicationEndpoint.md) - diff --git a/skype/skype-ps/skype/Get-CsTrustedApplicationPool.md b/skype/skype-ps/skype/Get-CsTrustedApplicationPool.md index d6f477e119..c790d1b493 100644 --- a/skype/skype-ps/skype/Get-CsTrustedApplicationPool.md +++ b/skype/skype-ps/skype/Get-CsTrustedApplicationPool.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstrustedapplicationpool +online version: https://learn.microsoft.com/powershell/module/skype/get-cstrustedapplicationpool applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsTrustedApplicationPool schema: 2.0.0 diff --git a/skype/skype-ps/skype/Get-CsUCPhoneConfiguration.md b/skype/skype-ps/skype/Get-CsUCPhoneConfiguration.md index 0beff1c8a1..7441f11f69 100644 --- a/skype/skype-ps/skype/Get-CsUCPhoneConfiguration.md +++ b/skype/skype-ps/skype/Get-CsUCPhoneConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csucphoneconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csucphoneconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUCPhoneConfiguration schema: 2.0.0 manager: bulenteg @@ -196,26 +196,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -241,4 +221,3 @@ The Get-CsUCPhoneConfiguration cmdlet returns instances of the Microsoft.Rtc.Man [Remove-CsUCPhoneConfiguration](Remove-CsUCPhoneConfiguration.md) [Set-CsUCPhoneConfiguration](Set-CsUCPhoneConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsUICulture.md b/skype/skype-ps/skype/Get-CsUICulture.md index 4467ddae82..071c8309d1 100644 --- a/skype/skype-ps/skype/Get-CsUICulture.md +++ b/skype/skype-ps/skype/Get-CsUICulture.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuiculture +online version: https://learn.microsoft.com/powershell/module/skype/get-csuiculture applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUICulture schema: 2.0.0 @@ -84,4 +84,3 @@ The Get-CsUICulture cmdlet returns instances of the System.Globalization.Culture ## RELATED LINKS [Set-CsUICulture](Set-CsUICulture.md) - diff --git a/skype/skype-ps/skype/Get-CsUnassignedNumber.md b/skype/skype-ps/skype/Get-CsUnassignedNumber.md index 7c43ed9e3a..903f8ebaea 100644 --- a/skype/skype-ps/skype/Get-CsUnassignedNumber.md +++ b/skype/skype-ps/skype/Get-CsUnassignedNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csunassignednumber +online version: https://learn.microsoft.com/powershell/module/skype/get-csunassignednumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUnassignedNumber schema: 2.0.0 @@ -143,4 +143,3 @@ Returns an object of type Microsoft.Rtc.Management.Voice.Helpers.DisplayAnnounce [Remove-CsUnassignedNumber](Remove-CsUnassignedNumber.md) [Set-CsUnassignedNumber](Set-CsUnassignedNumber.md) - diff --git a/skype/skype-ps/skype/Get-CsUpgradeDomainInfo.md b/skype/skype-ps/skype/Get-CsUpgradeDomainInfo.md index a7eca11ea7..e8d813bd7c 100644 --- a/skype/skype-ps/skype/Get-CsUpgradeDomainInfo.md +++ b/skype/skype-ps/skype/Get-CsUpgradeDomainInfo.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csupgradedomaininfo +online version: https://learn.microsoft.com/powershell/module/skype/get-csupgradedomaininfo applicable: Skype for Business Server 2019 title: Get-CsUpgradeDomainInfo schema: 2.0.0 @@ -124,4 +124,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsUser.md b/skype/skype-ps/skype/Get-CsUser.md index 3ef6d380ea..c59d7c3028 100644 --- a/skype/skype-ps/skype/Get-CsUser.md +++ b/skype/skype-ps/skype/Get-CsUser.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuser +online version: https://learn.microsoft.com/powershell/module/skype/get-csuser applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUser schema: 2.0.0 @@ -49,7 +49,7 @@ For example, if you don't want to return all your Skype for Business Server user (These parameters are mutually exclusive: if you use Filter in a command you cannot use LdapFilter in that same command, and vice-versa.) The Filter parameter enables you to limit the returned data to users who meet the specified Skype for Business Server criteria; for example, you might decide to return only users with accounts on the specified Registrar pool, or only users who have been enabled for Enterprise Voice. The LdapFilter parameter enables you to limit the returned data to users who fit other Active Directory-based criteria; for example, users who work in a specified state or province, users who do or do not have a pager, or users with a designated job title. -**Note: the equivalent command for Skype for Business Online is [Get-CsOnlineUser](https://docs.microsoft.com/powershell/module/skype/get-csonlineuser?view=skype-ps)**. +**Note: the equivalent command for Skype for Business Online is [Get-CsOnlineUser](https://learn.microsoft.com/powershell/module/skype/get-csonlineuser?view=skype-ps)**. ## EXAMPLES @@ -415,4 +415,3 @@ The Get-CsUser cmdlet returns instances of the Microsoft.Rtc.Management.ADConnec [Move-CsUser](Move-CsUser.md) [Set-CsUser](Set-CsUser.md) - diff --git a/skype/skype-ps/skype/Get-CsUserAcp.md b/skype/skype-ps/skype/Get-CsUserAcp.md index f1851a82e7..430f4b037c 100644 --- a/skype/skype-ps/skype/Get-CsUserAcp.md +++ b/skype/skype-ps/skype/Get-CsUserAcp.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuseracp -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csuseracp +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUserAcp schema: 2.0.0 manager: bulenteg @@ -33,10 +33,12 @@ Get-CsUserAcp \[\[-Identity\] \<UserIdParameter\>\] \[-Filter \<string\>\] \[-Ld ``` Get-CsUserAcp [[-Identity] <UserIdParameter>] [-Credential <PSCredential>] [-Filter <String>] [-LdapFilter <String>] [-ResultSize <Microsoft.Rtc.Management.ADConnect.Core.Unlimited`1[System.UInt32]>] - [-AsJob] [<CommonParameters>] + [<CommonParameters>] ``` ## DESCRIPTION +Deprecation Notice: Integration of Skype for Business with third-party audio conferencing providers has been retired. More details are here - https://learn.microsoft.com/skypeforbusiness/legal-and-regulatory/end-of-integration-with-3rd-party-providers. As a result, cmdlet no longer works. + An audio conferencing provider is a third-party company that provides organizations with conferencing services. Among other things, audio conferencing providers provide a way for users located off site, and not connected to the corporate network or the Internet, to participate in the audio portion of a conference or meeting. Audio conferencing providers often provide high-end services such as live translation, transcription, and live per-conference operator assistance. @@ -220,22 +222,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -261,4 +247,3 @@ The Get-CsUserAcp cmdlet returns instances of the Microsoft.Rtc.Management.ADCon [Remove-CsUserAcp](Remove-CsUserAcp.md) [Set-CsUserAcp](Set-CsUserAcp.md) - diff --git a/skype/skype-ps/skype/Get-CsUserCallForwardingSettings.md b/skype/skype-ps/skype/Get-CsUserCallForwardingSettings.md index 35fdfcafca..3fa9eb9579 100644 --- a/skype/skype-ps/skype/Get-CsUserCallForwardingSettings.md +++ b/skype/skype-ps/skype/Get-CsUserCallForwardingSettings.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csusercallforwardingsettings +online version: https://learn.microsoft.com/powershell/module/skype/get-csusercallforwardingsettings applicable: Skype for Business Server 2019 title: Get-CsUserCallForwardingSettings schema: 2.0.0 @@ -23,11 +23,14 @@ Get-CsUserCallForwardingSettings [-User] <String> [-Force] [<CommonParameters>] ## DESCRIPTION The feature enables the use of SEFAUtil functionality in PowerShell. SEFAUtil (Secondary Extension Feature Activation) enables Skype server administrators and helpdesk agents to configure delegate-ringing, call-forwarding and Group Call Pickup settings on behalf of a Skype server user. This tool also allows administrators to query the call-routing settings that are published for a particular user. + The cmdlets introduced in this feature can only be run by members of the following groups for On-prem deployments, per the access level specified below: -• CsAdministrator - Get and Set for all cmdlets -• CsVoiceAdministrator - Get and Set for all cmdlets -• CsServerAdministrator - Get and Set for all cmdlets -• CsHelpDesk - Get for all cmdlets + +- CsAdministrator - Get and Set for all cmdlets +- CsVoiceAdministrator - Get and Set for all cmdlets +- CsServerAdministrator - Get and Set for all cmdlets +- CsHelpDesk - Get for all cmdlets + Server auto-discovery needs to be enabled. There are no additional licensing requirements for use of the cmdlets. ## EXAMPLES diff --git a/skype/skype-ps/skype/Get-CsUserDatabaseState.md b/skype/skype-ps/skype/Get-CsUserDatabaseState.md index b0db7c2cd4..e213d9e530 100644 --- a/skype/skype-ps/skype/Get-CsUserDatabaseState.md +++ b/skype/skype-ps/skype/Get-CsUserDatabaseState.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserdatabasestate +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserdatabasestate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUserDatabaseState schema: 2.0.0 @@ -144,6 +144,3 @@ The Get-CsUserDatabaseState cmdlet returns instances of the Microsoft.Rtc.Manage [Set-CsUserDatabaseState](Set-CsUserDatabaseState.md) [Update-CsUserDatabase](Update-CsUserDatabase.md) - - - diff --git a/skype/skype-ps/skype/Get-CsUserDelegates.md b/skype/skype-ps/skype/Get-CsUserDelegates.md index 88c60c48a4..414d0cf5f2 100644 --- a/skype/skype-ps/skype/Get-CsUserDelegates.md +++ b/skype/skype-ps/skype/Get-CsUserDelegates.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserdelegates +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserdelegates applicable: Skype for Business Server 2019 title: Get-CsUserDelegates schema: 2.0.0 @@ -23,13 +23,15 @@ Get-CsUserDelegates [-User] <String> [-Force] [<CommonParameters>] ## DESCRIPTION The feature enables the use of SEFAUtil functionality in PowerShell. SEFAUtil (Secondary Extension Feature Activation) enables Skype server administrators and helpdesk agents to configure delegate-ringing, call-forwarding and Group Call Pickup settings on behalf of a Skype server user. This tool also allows administrators to query the call-routing settings that are published for a particular user. + The cmdlets introduced in this feature can only be run by members of the following groups for On-prem deployments, per the access level specified below: -• CsAdministrator - Get and Set for all cmdlets -• CsVoiceAdministrator - Get and Set for all cmdlets -• CsServerAdministrator - Get and Set for all cmdlets -• CsHelpDesk - Get for all cmdlets -Server auto-discovery needs to be enabled. There are no additional licensing requirements for use of the cmdlets. +- CsAdministrator - Get and Set for all cmdlets +- CsVoiceAdministrator - Get and Set for all cmdlets +- CsServerAdministrator - Get and Set for all cmdlets +- CsHelpDesk - Get for all cmdlets + +Server auto-discovery needs to be enabled. There are no additional licensing requirements for use of the cmdlets. ## EXAMPLES diff --git a/skype/skype-ps/skype/Get-CsUserLocationStatus.md b/skype/skype-ps/skype/Get-CsUserLocationStatus.md index 8bc41011fb..88057a3b23 100644 --- a/skype/skype-ps/skype/Get-CsUserLocationStatus.md +++ b/skype/skype-ps/skype/Get-CsUserLocationStatus.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserlocationstatus +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserlocationstatus applicable: Skype for Business Online title: Get-CsUserLocationStatus schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsUserLocationStatus @@ -18,7 +18,7 @@ With `Get-CsUserLocationStatus` you can track the progress of the regionally hos ## SYNTAX ``` -Get-CsUserLocationStatus [[-Tenant] <Guid>] [[-Identity] <UserIdParameter>] [-Confirm] [-WhatIf] [-AsJob] +Get-CsUserLocationStatus [[-Tenant] <Guid>] [[-Identity] <UserIdParameter>] [-Confirm] [-WhatIf] [<CommonParameters>] ``` @@ -109,26 +109,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -143,4 +123,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsUserPoolInfo.md b/skype/skype-ps/skype/Get-CsUserPoolInfo.md index 71520bfa48..dc820faa56 100644 --- a/skype/skype-ps/skype/Get-CsUserPoolInfo.md +++ b/skype/skype-ps/skype/Get-CsUserPoolInfo.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserpoolinfo +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserpoolinfo applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUserPoolInfo schema: 2.0.0 @@ -169,5 +169,3 @@ The Get-CsUserPoolInfo cmdlet returns instances of the Microsoft.Rtc.Management. ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Get-CsUserPstnSettings.md b/skype/skype-ps/skype/Get-CsUserPstnSettings.md index 79b1e77810..0db2a2b553 100644 --- a/skype/skype-ps/skype/Get-CsUserPstnSettings.md +++ b/skype/skype-ps/skype/Get-CsUserPstnSettings.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserpstnsettings +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserpstnsettings applicable: Skype for Business Online title: Get-CsUserPstnSettings schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsUserPstnSettings @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the Get-CsUserPstnSettings cmdlet to retrieve a voice-enabled user's public switched telephone network (PSTN) settings. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` @@ -121,26 +123,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -157,5 +139,3 @@ The Get-CsUserPstnSettings cmdlet returns instances of the UserPstnSettings obje ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Get-CsUserReplicatorConfiguration.md b/skype/skype-ps/skype/Get-CsUserReplicatorConfiguration.md index 85459ee198..479833bdf5 100644 --- a/skype/skype-ps/skype/Get-CsUserReplicatorConfiguration.md +++ b/skype/skype-ps/skype/Get-CsUserReplicatorConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserreplicatorconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserreplicatorconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUserReplicatorConfiguration schema: 2.0.0 @@ -160,4 +160,3 @@ The Get-CsUserReplicatorConfiguration cmdlet returns instances of the Microsoft. [Remove-CsUserReplicatorConfiguration](Remove-CsUserReplicatorConfiguration.md) [Set-CsUserReplicatorConfiguration](Set-CsUserReplicatorConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsUserServicesConfiguration.md b/skype/skype-ps/skype/Get-CsUserServicesConfiguration.md index 6cc963193e..110e94585e 100644 --- a/skype/skype-ps/skype/Get-CsUserServicesConfiguration.md +++ b/skype/skype-ps/skype/Get-CsUserServicesConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserservicesconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserservicesconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUserServicesConfiguration schema: 2.0.0 @@ -194,4 +194,3 @@ The Get-CsUserServicesConfiguration cmdlet returns instances of the Microsoft.Rt [Remove-CsUserServicesConfiguration](Remove-CsUserServicesConfiguration.md) [Set-CsUserServicesConfiguration](Set-CsUserServicesConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsUserServicesPolicy.md b/skype/skype-ps/skype/Get-CsUserServicesPolicy.md index 7889dab238..2feb41556d 100644 --- a/skype/skype-ps/skype/Get-CsUserServicesPolicy.md +++ b/skype/skype-ps/skype/Get-CsUserServicesPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserservicespolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserservicespolicy +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUserServicesPolicy schema: 2.0.0 manager: bulenteg @@ -186,26 +186,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -235,4 +215,3 @@ The Get-CsUserServicesPolicy cmdlet returns instances of the Microsoft.Rtc.Manag [Remove-CsUserServicesPolicy](Remove-CsUserServicesPolicy.md) [Set-CsUserServicesPolicy](Set-CsUserServicesPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsUserSession.md b/skype/skype-ps/skype/Get-CsUserSession.md index 29e81f1aa1..8871e70049 100644 --- a/skype/skype-ps/skype/Get-CsUserSession.md +++ b/skype/skype-ps/skype/Get-CsUserSession.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csusersession +online version: https://learn.microsoft.com/powershell/module/skype/get-csusersession applicable: Skype for Business Online title: Get-CsUserSession schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsUserSession @@ -18,10 +18,12 @@ Use the Get-CsUserSession cmdlet to retrieve user session information within a s ## SYNTAX ``` -Get-CsUserSession -StartTime <DateTimeOffset> -User <String> [-EndTime <DateTimeOffset>] [-AsJob] [<CommonParameters>] +Get-CsUserSession -StartTime <DateTimeOffset> -User <String> [-EndTime <DateTimeOffset>] [<CommonParameters>] ``` ## DESCRIPTION +**Deprecation Notice**: We will be retiring this feature and cmdlet from Skype for Business Online beginning 5/30/2020. Instead, we recommend the utilization of MS Graph Call Records API, which is where we will continue to invest our development resources. For more information, see <https://learn.microsoft.com/graph/api/resources/callrecords-api-overview?view=graph-rest-beta>. + Use the Get-CsUserSession cmdlet to retrieve session information for users within a specified date range within the past 30 days. You have to be assigned Skype For Business admin role to run this cmdlet. @@ -87,26 +89,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -123,4 +105,3 @@ The Get-CsUserSession cmdlet returns an instance of the Microsoft.Rtc.Management ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsUserSettingsPageConfiguration.md b/skype/skype-ps/skype/Get-CsUserSettingsPageConfiguration.md index 33f72bd5ea..f92d47dd5f 100644 --- a/skype/skype-ps/skype/Get-CsUserSettingsPageConfiguration.md +++ b/skype/skype-ps/skype/Get-CsUserSettingsPageConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csusersettingspageconfiguration -applicable: Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csusersettingspageconfiguration +applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsUserSettingsPageConfiguration schema: 2.0.0 manager: bulenteg diff --git a/skype/skype-ps/skype/Get-CsUserTeamMembers.md b/skype/skype-ps/skype/Get-CsUserTeamMembers.md index bf7cdeb22d..a5584e71ca 100644 --- a/skype/skype-ps/skype/Get-CsUserTeamMembers.md +++ b/skype/skype-ps/skype/Get-CsUserTeamMembers.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csuserteammembers +online version: https://learn.microsoft.com/powershell/module/skype/get-csuserteammembers applicable: Skype for Business Server 2019 title: Get-CsUserTeamMembers schema: 2.0.0 @@ -23,11 +23,14 @@ Get-CsUserTeamMembers [-User] <String> [-Force] [<CommonParameters>] ## DESCRIPTION The feature enables the use of SEFAUtil functionality in PowerShell. SEFAUtil (Secondary Extension Feature Activation) enables Skype server administrators and helpdesk agents to configure delegate-ringing, call-forwarding and Group Call Pickup settings on behalf of a Skype server user. This tool also allows administrators to query the call-routing settings that are published for a particular user. + The cmdlets introduced in this feature can only be run by members of the following groups for On-prem deployments, per the access level specified below: -• CsAdministrator - Get and Set for all cmdlets -• CsVoiceAdministrator - Get and Set for all cmdlets -• CsServerAdministrator - Get and Set for all cmdlets -• CsHelpDesk - Get for all cmdlets + +- CsAdministrator - Get and Set for all cmdlets +- CsVoiceAdministrator - Get and Set for all cmdlets +- CsServerAdministrator - Get and Set for all cmdlets +- CsHelpDesk - Get for all cmdlets + Server auto-discovery needs to be enabled. There are no additional licensing requirements for use of the cmdlets. ## EXAMPLES diff --git a/skype/skype-ps/skype/Get-CsVideoInteropServerConfiguration.md b/skype/skype-ps/skype/Get-CsVideoInteropServerConfiguration.md index 9c764eff6f..66425ce2e9 100644 --- a/skype/skype-ps/skype/Get-CsVideoInteropServerConfiguration.md +++ b/skype/skype-ps/skype/Get-CsVideoInteropServerConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvideointeropserverconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csvideointeropserverconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVideoInteropServerConfiguration schema: 2.0.0 @@ -175,4 +175,3 @@ The Get-CsVideoInteropServerConfiguration cmdlet returns instances of the Micros [Remove-CsVideoInteropServerConfiguration](Remove-CsVideoInteropServerConfiguration.md) [Set-CsVideoInteropServerConfiguration](Set-CsVideoInteropServerConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsVideoInteropServerSyntheticTransactionConfiguration.md b/skype/skype-ps/skype/Get-CsVideoInteropServerSyntheticTransactionConfiguration.md index 4520e978ee..007084aa59 100644 --- a/skype/skype-ps/skype/Get-CsVideoInteropServerSyntheticTransactionConfiguration.md +++ b/skype/skype-ps/skype/Get-CsVideoInteropServerSyntheticTransactionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvideointeropserversynthetictransactionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csvideointeropserversynthetictransactionconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVideoInteropServerSyntheticTransactionConfiguration schema: 2.0.0 @@ -126,4 +126,3 @@ Returns an object array, or single instance (if used with the Identity parameter [Remove-CsVideoInteropServerSyntheticTransactionConfiguration](Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md) [Test-CsP2PVideoInteropServerSipTrunkAV](Test-CsP2PVideoInteropServerSipTrunkAV.md) - diff --git a/skype/skype-ps/skype/Get-CsVideoTrunk.md b/skype/skype-ps/skype/Get-CsVideoTrunk.md index 97122dba6a..b6024c0dac 100644 --- a/skype/skype-ps/skype/Get-CsVideoTrunk.md +++ b/skype/skype-ps/skype/Get-CsVideoTrunk.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvideotrunk +online version: https://learn.microsoft.com/powershell/module/skype/get-csvideotrunk applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVideoTrunk schema: 2.0.0 @@ -144,4 +144,3 @@ The Get-CsVideoTrunk cmdlet returns instances of the Microsoft.Rtc.Management.Xd ## RELATED LINKS [Set-CsVideoGateway](Set-CsVideoGateway.md) - diff --git a/skype/skype-ps/skype/Get-CsVideoTrunkConfiguration.md b/skype/skype-ps/skype/Get-CsVideoTrunkConfiguration.md index 5cb11382ff..fc9b683da3 100644 --- a/skype/skype-ps/skype/Get-CsVideoTrunkConfiguration.md +++ b/skype/skype-ps/skype/Get-CsVideoTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvideotrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csvideotrunkconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVideoTrunkConfiguration schema: 2.0.0 @@ -35,7 +35,7 @@ The Video Interop Server is a Skype service that runs on a standalone pool and c To enable the Video Interop Server, you must use Topology Builder to define at least one VIS instance. Each VIS instance will typically be associated with one or more Video Gateways. -Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from an third party PBX supporting 3rd party video teleconferencing systems (VTCs). +Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from a third party PBX supporting 3rd party video teleconferencing systems (VTCs). The Video Gateway and a Video Interop Server (VIS) use a Session Initiation Protocol (SIP) trunk to connect video calls between third party VTCs and internal endpoints. Video Trunks settings can be managed by using the CsVideoTrunkConfiguration cmdlets. @@ -171,4 +171,3 @@ The Get-CsVideoTrunkConfiguration cmdlet returns instances of the Microsoft.Rtc. [Set-CsVideoTrunkConfiguration](Set-CsVideoTrunkConfiguration.md) [Remove-CsVideoTrunkConfiguration](Remove-CsVideoTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsVoiceConfiguration.md b/skype/skype-ps/skype/Get-CsVoiceConfiguration.md index 6282bc47a1..862ecb0444 100644 --- a/skype/skype-ps/skype/Get-CsVoiceConfiguration.md +++ b/skype/skype-ps/skype/Get-CsVoiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvoiceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csvoiceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVoiceConfiguration schema: 2.0.0 @@ -120,4 +120,3 @@ This cmdlet returns an instance of the Microsoft.Rtc.Management.WritableConfig.P [Set-CsVoiceConfiguration](Set-CsVoiceConfiguration.md) [Get-CsVoiceTestConfiguration](Get-CsVoiceTestConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsVoiceNormalizationRule.md b/skype/skype-ps/skype/Get-CsVoiceNormalizationRule.md index 69a93c3de5..9747b6b836 100644 --- a/skype/skype-ps/skype/Get-CsVoiceNormalizationRule.md +++ b/skype/skype-ps/skype/Get-CsVoiceNormalizationRule.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvoicenormalizationrule -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csvoicenormalizationrule +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVoiceNormalizationRule schema: 2.0.0 manager: bulenteg @@ -17,17 +17,18 @@ Returns information about the voice normalization rules used in your organizatio Voice normalization rules convert telephone dialing requirements (for example, dialing 9 to access an outside line) to the E.164 phone number format used by Skype for Business Server. This cmdlet was introduced in Lync Server 2010. +**Note**: This cmdlet has been deprecated in Teams PowerShell Module 4.0.0. + ## SYNTAX ### Identity (Default) ``` -Get-CsVoiceNormalizationRule [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] +Get-CsVoiceNormalizationRule [[-Identity] <XdsIdentity>] [-Tenant <guid>] [-LocalStore] [<CommonParameters>] ``` ### Filter ``` -Get-CsVoiceNormalizationRule [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +Get-CsVoiceNormalizationRule [-Tenant <guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] ``` ## DESCRIPTION @@ -84,7 +85,7 @@ If a value is specified for this parameter, it must be in the format scope/name; Type: XdsIdentity Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 1 @@ -102,7 +103,7 @@ For example, the filter value *lob* will return all rules at the global scope (s Type: String Parameter Sets: Filter, (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -118,7 +119,7 @@ Retrieves the voice normalization rule from the local replica of the Central Man Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -128,29 +129,13 @@ Accept wildcard characters: False ``` ### -Tenant -{{Fill Tenant Description}} +For internal Microsoft usage. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -187,4 +172,3 @@ The Get-CsVoiceNormalizationRule cmdlet returns instances of the Microsoft.Rtc.M [Test-CsVoiceNormalizationRule](Test-CsVoiceNormalizationRule.md) [Get-CsDialPlan](Get-CsDialPlan.md) - diff --git a/skype/skype-ps/skype/Get-CsVoicePolicy.md b/skype/skype-ps/skype/Get-CsVoicePolicy.md index 9695d37e86..ee4a8eb0cb 100644 --- a/skype/skype-ps/skype/Get-CsVoicePolicy.md +++ b/skype/skype-ps/skype/Get-CsVoicePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvoicepolicy +online version: https://learn.microsoft.com/powershell/module/skype/get-csvoicepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVoicePolicy schema: 2.0.0 @@ -178,4 +178,3 @@ This cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Pol [Grant-CsVoicePolicy](Grant-CsVoicePolicy.md) [Test-CsVoicePolicy](Test-CsVoicePolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsVoiceRoute.md b/skype/skype-ps/skype/Get-CsVoiceRoute.md index e9b445cb8c..f66706f65e 100644 --- a/skype/skype-ps/skype/Get-CsVoiceRoute.md +++ b/skype/skype-ps/skype/Get-CsVoiceRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvoiceroute +online version: https://learn.microsoft.com/powershell/module/skype/get-csvoiceroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVoiceRoute schema: 2.0.0 @@ -155,4 +155,3 @@ This cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Pol [Set-CsVoiceRoute](Set-CsVoiceRoute.md) [Test-CsVoiceRoute](Test-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/Get-CsVoiceRoutingPolicy.md b/skype/skype-ps/skype/Get-CsVoiceRoutingPolicy.md index 49b0e89921..05f3448032 100644 --- a/skype/skype-ps/skype/Get-CsVoiceRoutingPolicy.md +++ b/skype/skype-ps/skype/Get-CsVoiceRoutingPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvoiceroutingpolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/get-csvoiceroutingpolicy +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVoiceRoutingPolicy schema: 2.0.0 manager: bulenteg @@ -144,26 +144,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -189,4 +169,3 @@ The Get-CsVoiceRoutingPolicy cmdlet returns instances of the Microsoft.Rtc.Manag [Remove-CsVoiceRoutingPolicy](Remove-CsVoiceRoutingPolicy.md) [Set-CsVoiceRoutingPolicy](Set-CsVoiceRoutingPolicy.md) - diff --git a/skype/skype-ps/skype/Get-CsVoiceTestConfiguration.md b/skype/skype-ps/skype/Get-CsVoiceTestConfiguration.md index 172c75dcf4..3ebb3b103b 100644 --- a/skype/skype-ps/skype/Get-CsVoiceTestConfiguration.md +++ b/skype/skype-ps/skype/Get-CsVoiceTestConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvoicetestconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csvoicetestconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVoiceTestConfiguration schema: 2.0.0 @@ -143,4 +143,3 @@ Returns one of more objects of type Microsoft.Rtc.Management.WritableConfig.Poli [Set-CsVoiceTestConfiguration](Set-CsVoiceTestConfiguration.md) [Test-CsVoiceTestConfiguration](Test-CsVoiceTestConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsVoicemailReroutingConfiguration.md b/skype/skype-ps/skype/Get-CsVoicemailReroutingConfiguration.md index a93f2ef755..18b12a31a4 100644 --- a/skype/skype-ps/skype/Get-CsVoicemailReroutingConfiguration.md +++ b/skype/skype-ps/skype/Get-CsVoicemailReroutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvoicemailreroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-csvoicemailreroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsVoicemailReroutingConfiguration schema: 2.0.0 @@ -152,4 +152,3 @@ Retrieves one or more objects of type Microsoft.Rtc.Management.WritableConfig.Se [Remove-CsVoicemailReroutingConfiguration](Remove-CsVoicemailReroutingConfiguration.md) [Set-CsVoicemailReroutingConfiguration](Set-CsVoicemailReroutingConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsWatcherNodeConfiguration.md b/skype/skype-ps/skype/Get-CsWatcherNodeConfiguration.md index 8f6c29067f..f8c31c4d96 100644 --- a/skype/skype-ps/skype/Get-CsWatcherNodeConfiguration.md +++ b/skype/skype-ps/skype/Get-CsWatcherNodeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cswatchernodeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cswatchernodeconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsWatcherNodeConfiguration schema: 2.0.0 @@ -171,4 +171,3 @@ The Get-CsWatcherNodeConfiguration cmdlet returns instances of the Microsoft.Rtc [Set-CsWatcherNodeConfiguration](Set-CsWatcherNodeConfiguration.md) [Test-CsWatcherNodeConfiguration](Test-CsWatcherNodeConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsWebServiceConfiguration.md b/skype/skype-ps/skype/Get-CsWebServiceConfiguration.md index eed1c672a7..0955ecea76 100644 --- a/skype/skype-ps/skype/Get-CsWebServiceConfiguration.md +++ b/skype/skype-ps/skype/Get-CsWebServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cswebserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/get-cswebserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsWebServiceConfiguration schema: 2.0.0 @@ -190,4 +190,3 @@ The Get-CsWebServiceConfiguration cmdlet returns instances of the Microsoft.Rtc. [Remove-CsWebServiceConfiguration](Remove-CsWebServiceConfiguration.md) [Set-CsWebServiceConfiguration](Set-CsWebServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Get-CsWindowsService.md b/skype/skype-ps/skype/Get-CsWindowsService.md index d0360a438d..1141e80426 100644 --- a/skype/skype-ps/skype/Get-CsWindowsService.md +++ b/skype/skype-ps/skype/Get-CsWindowsService.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cswindowsservice +online version: https://learn.microsoft.com/powershell/module/skype/get-cswindowsservice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsWindowsService schema: 2.0.0 @@ -241,4 +241,3 @@ The Get-CsWindowsService cmdlet returns instances of the Microsoft.Rtc.Managemen [Start-CsWindowsService](Start-CsWindowsService.md) [Stop-CsWindowsService](Stop-CsWindowsService.md) - diff --git a/skype/skype-ps/skype/Get-CsXmppAllowedPartner.md b/skype/skype-ps/skype/Get-CsXmppAllowedPartner.md index ec766e5b2c..d842572c39 100644 --- a/skype/skype-ps/skype/Get-CsXmppAllowedPartner.md +++ b/skype/skype-ps/skype/Get-CsXmppAllowedPartner.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csxmppallowedpartner -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-csxmppallowedpartner +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsXmppAllowedPartner schema: 2.0.0 manager: rogupta @@ -158,4 +158,3 @@ The Get-CsXmppAllowedPartner cmdlet returns instances of the Microsoft.Rtc.Manag [Remove-CsXmppAllowedPartner](Remove-CsXmppAllowedPartner.md) [Set-CsXmppAllowedPartner](Set-CsXmppAllowedPartner.md) - diff --git a/skype/skype-ps/skype/Get-CsXmppGatewayConfiguration.md b/skype/skype-ps/skype/Get-CsXmppGatewayConfiguration.md index 9c70733d8a..42d1978491 100644 --- a/skype/skype-ps/skype/Get-CsXmppGatewayConfiguration.md +++ b/skype/skype-ps/skype/Get-CsXmppGatewayConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csxmppgatewayconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/get-csxmppgatewayconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Get-CsXmppGatewayConfiguration schema: 2.0.0 manager: rogupta @@ -148,4 +148,3 @@ The Get-CsXmppGatewayConfiguration cmdlet returns instances of the Microsoft.Rtc ## RELATED LINKS [Set-CsXmppGatewayConfiguration](Set-CsXmppGatewayConfiguration.md) - diff --git a/skype/skype-ps/skype/Grant-CsArchivingPolicy.md b/skype/skype-ps/skype/Grant-CsArchivingPolicy.md index e6c54872c3..195e225d06 100644 --- a/skype/skype-ps/skype/Grant-CsArchivingPolicy.md +++ b/skype/skype-ps/skype/Grant-CsArchivingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csarchivingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-csarchivingpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsArchivingPolicy schema: 2.0.0 @@ -260,5 +260,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsArchivingPolicy](Remove-CsArchivingPolicy.md) [Set-CsArchivingPolicy](Set-CsArchivingPolicy.md) - - diff --git a/skype/skype-ps/skype/Grant-CsBroadcastMeetingPolicy.md b/skype/skype-ps/skype/Grant-CsBroadcastMeetingPolicy.md deleted file mode 100644 index 06036eace0..0000000000 --- a/skype/skype-ps/skype/Grant-CsBroadcastMeetingPolicy.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csbroadcastmeetingpolicy -applicable: Skype for Business Online -title: Grant-CsBroadcastMeetingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsBroadcastMeetingPolicy - -## SYNOPSIS -Use the Grant-CsBroadcastMeetingPolicy cmdlet to assign a broadcast meeting policy to a user. - -## SYNTAX -``` -Grant-CsBroadcastMeetingPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Administrators can manage Broadcast meeting functionality in Skype for Business Online using the following: -- Broadcast meeting configuration at the tenant level -- Broadcast meeting policy at the user level -- Conferencing policy at the user level. - -Broadcast meeting configuration and broadcast meeting policy govern broadcast-specific functionality. In addition, the settings of the conferencing policy assigned to the user producing the broadcast also general conferencing settings that are also relevant for broadcast meetings. - -This document describes how to specify which broadcast meeting policy is assigned to a user. Be sure to also review the following docs to manage conferencing policy:[Grant-CsConferencingPolicy](Grant-CsConferencingPolicy.md), [New-CsConferencingPolicy](New-CsConferencingPolicy.md), and [Set-CsConferencingPolicy](Set-CsConferencingPolicy.md). - -**NOTES** -- Broadcast meeting policies are predefined in Skype for Business. The defined settings for each policy can be displayed by using the Get-CsBroadcastMeetingPolicy cmdlet with no parameters. -- New broadcast meeting policy instance can't be created, and existing policies can't be modified. They can only be granted, or assigned to users. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` - -Grant-CsBroadcastMeetingPolicy -Identity jphillips@contoso.com -PolicyName BroadcastMeetingPolicyAllEnabled -``` - -This example grants the BroadcastMeetingPolicyAllEnabled policy to a user identified by their User Principal Name (UPN). - -### -------------------------- Example 2 -------------------------- -``` -Grant-CsBroadcastMeetingPolicy -Identity jphillips@contoso.com -PolicyName $Null -``` - -In Example 2, any per-user broadcast meeting policy previously assigned to the user jphillips is unassigned from that user; as a result, they will be managed by the global broadcast meeting policy. -To unassign a per-user policy, set the PolicyName to a null value ($Null). - - -## PARAMETERS - -### -Identity -Specifies the identity of the target user. -Acceptable values include: - -Example: jphillips@contoso.com - -Example: sip:jphillips@contoso.com - -Example: 98403f08-577c-46dd-851a-f0460a13b03d - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -Specifies the name of the policy to be assigned to a user. -A list of the policies for your organization can be retrieved using Get-CsBroadcastMeetingPolicy. -The PolicyName is the policy identity minus the policy scope (the "tag:" prefix). -For example, a policy with the identity "Tag:BroadcastMeetingPolicyDisabled" has a PolicyName equal to "BroadcastMeetingPolicyDisabled". -To unassign a previously assigned policy, set PolicyName to $Null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Enables you to pass a user object through the pipeline that represents the user account being assigned the policy. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### -None - -## OUTPUTS - -### -None - -## NOTES - -## RELATED LINKS - -[Get-CsBroadcastMeetingPolicy](Get-CsBroadcastMeetingPolicy.md) -[Grant-CsConferencingPolicy](Grant-CsConferencingPolicy.md) -[New-CsConferencingPolicy](New-CsConferencingPolicy.md) -[Set-CsConferencingPolicy](Set-CsConferencingPolicy.md) -[Set-CsBroadcastMeetingConfiguration](Set-CsBroadcastMeetingConfiguration.md) - diff --git a/skype/skype-ps/skype/Grant-CsCallViaWorkPolicy.md b/skype/skype-ps/skype/Grant-CsCallViaWorkPolicy.md index f10ae4336a..5b5a65c2cf 100644 --- a/skype/skype-ps/skype/Grant-CsCallViaWorkPolicy.md +++ b/skype/skype-ps/skype/Grant-CsCallViaWorkPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cscallviaworkpolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-cscallviaworkpolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsCallViaWorkPolicy schema: 2.0.0 @@ -179,5 +179,3 @@ None. [New-CsCallViaWorkPolicy](New-CsCallViaWorkPolicy.md) [Get-CsCallViaWorkPolicy](Get-CsCallViaWorkPolicy.md) - - diff --git a/skype/skype-ps/skype/Grant-CsCallingLineIdentity.md b/skype/skype-ps/skype/Grant-CsCallingLineIdentity.md deleted file mode 100644 index 7c7a57fc8a..0000000000 --- a/skype/skype-ps/skype/Grant-CsCallingLineIdentity.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cscallinglineidentity -applicable: Skype for Business Online -title: Grant-CsCallingLineIdentity -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsCallingLineIdentity - -## SYNOPSIS -Use the `Grant-CsCallingLineIdentity` cmdlet to apply a Caller ID policy to a user account. - -## SYNTAX - -``` -Grant-CsCallingLineIdentity [[-Identity] <UserIdParameter>] [[-PolicyName] <String>] [-Confirm] [-DomainController <Fqdn>] [-PassThru] [-Tenant <Guid>] [-WhatIf] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -You can either change or block the Caller ID (also called a Calling Line ID) for a user. By default, the Skype for Business Online user's phone number can be seen when that user makes a call to a PSTN phone, or when a call comes in. You can create a Caller ID policy to provide an alternate displayed number, or to block any number from being displayed; you can then apply the Caller ID policy to a specific user. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Grant-CsCallingLineIdentity -Identity "Ken Myer" -PolicyName CallerIDRedmond -``` - -This example assigns the Caller ID policy with the Identity CallerIDRedmond to the user with the display name Ken Myer. - -### -------------------------- Example 2 -------------------------- -``` -Grant-CsCallingLineIdentity -PolicyName Anonymous -Identity "amos.marble@contoso.com" -``` - -This example grants the Caller ID policy "Anonymous" to the user Amos Marble. - - -## PARAMETERS - -### -Identity -The Identity (unique identifier) of the user to whom the policy is being assigned. User Identities can be specified using one of the following formats: 1) the user's SIP address; 2) the user's user principal name (UPN); or, 3) the user's Active Directory display name (for example, Ken Myer). - -You can use the asterisk (\*) wildcard character when using the Display Name as the user Identity. For example, the Identity "\*Smith" returns all the users who have a display name that ends with the string value "Smith". - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The name (Identity) of the Caller ID policy to be assigned to the user. (Note that this includes only the name portion of the Identity. Per-user policy identities include a prefix of tag: that should not be included with the PolicyName). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Returns the results of the command. By default, this cmdlet does not generate any output. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Set-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/set-cscallinglineidentity?view=skype-ps) - -[Get-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/get-cscallinglineidentity?view=skype-ps) - -[Remove-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/remove-cscallinglineidentity?view=skype-ps) - -[New-CsCallingLineIdentity](https://docs.microsoft.com/powershell/module/skype/new-cscallinglineidentity?view=skype-ps) - diff --git a/skype/skype-ps/skype/Grant-CsClientPolicy.md b/skype/skype-ps/skype/Grant-CsClientPolicy.md index 03fdfb2677..5b614c56ca 100644 --- a/skype/skype-ps/skype/Grant-CsClientPolicy.md +++ b/skype/skype-ps/skype/Grant-CsClientPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csclientpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/grant-csclientpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsClientPolicy schema: 2.0.0 manager: bulenteg @@ -106,7 +106,7 @@ For example, the Identity "* Smith" returns all the users who have a display nam Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: True Position: 1 @@ -129,7 +129,7 @@ For example: Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 2 @@ -146,7 +146,7 @@ If this parameter is not included then the cmdlet will use the first available d Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -163,7 +163,7 @@ By default, the Grant-CsClientPolicy cmdlet does not pass objects through the pi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -179,7 +179,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -195,7 +195,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -222,27 +222,6 @@ The Tenant parameter is primarily for use in a hybrid deployment. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online Required: False Position: Named @@ -278,4 +257,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsClientPolicy](Remove-CsClientPolicy.md) [Set-CsClientPolicy](Set-CsClientPolicy.md) - diff --git a/skype/skype-ps/skype/Grant-CsClientVersionPolicy.md b/skype/skype-ps/skype/Grant-CsClientVersionPolicy.md index dcfd7ae57d..f3c7b5346a 100644 --- a/skype/skype-ps/skype/Grant-CsClientVersionPolicy.md +++ b/skype/skype-ps/skype/Grant-CsClientVersionPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csclientversionpolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-csclientversionpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsClientVersionPolicy schema: 2.0.0 @@ -248,4 +248,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsClientVersionPolicy](Remove-CsClientVersionPolicy.md) [Set-CsClientVersionPolicy](Set-CsClientVersionPolicy.md) - diff --git a/skype/skype-ps/skype/Grant-CsConferencingPolicy.md b/skype/skype-ps/skype/Grant-CsConferencingPolicy.md index 7ffa519110..079b1f8b84 100644 --- a/skype/skype-ps/skype/Grant-CsConferencingPolicy.md +++ b/skype/skype-ps/skype/Grant-CsConferencingPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csconferencingpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/grant-csconferencingpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsConferencingPolicy schema: 2.0.0 manager: bulenteg @@ -213,22 +213,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` @@ -269,5 +253,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsConferencingPolicy](Remove-CsConferencingPolicy.md) [Set-CsConferencingPolicy](Set-CsConferencingPolicy.md) - - diff --git a/skype/skype-ps/skype/Grant-CsDialPlan.md b/skype/skype-ps/skype/Grant-CsDialPlan.md index 79da65d273..17aa244dd3 100644 --- a/skype/skype-ps/skype/Grant-CsDialPlan.md +++ b/skype/skype-ps/skype/Grant-CsDialPlan.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csdialplan +online version: https://learn.microsoft.com/powershell/module/skype/grant-csdialplan applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsDialPlan schema: 2.0.0 @@ -24,7 +24,7 @@ This cmdlet was introduced in Lync Server 2010. ``` Grant-CsDialPlan [-Identity] <UserIdParameter> [[-PolicyName] <String>] [-DomainController <Fqdn>] [-PassThru] - [-WhatIf] [-Confirm] [-Tenant <Guid>] [-AsJob] [<CommonParameters>] + [-WhatIf] [-Confirm] [-Tenant <Guid>] [<CommonParameters>] ``` ## DESCRIPTION @@ -210,4 +210,3 @@ When used with the PassThru parameter, returns an object of type Microsoft.Rtc.M [Test-CsDialPlan](Test-CsDialPlan.md) [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Grant-CsDialoutPolicy.md b/skype/skype-ps/skype/Grant-CsDialoutPolicy.md deleted file mode 100644 index 245692186b..0000000000 --- a/skype/skype-ps/skype/Grant-CsDialoutPolicy.md +++ /dev/null @@ -1,210 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csdialoutpolicy -applicable: Skype for Business Online -title: Grant-CsDialoutPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsDialoutPolicy - -## SYNOPSIS -Use the `Grant-CsDialoutPolicy` cmdlet to assign a per-user outbound calling restriction policy to one or more users. - -## SYNTAX -``` -Grant-CsDialoutPolicy [[-Identity] <UserIdParameter>] [[-PolicyName] <string>] [-Confirm] [-DomainController <Fqdn>] - [-PassThru] [-Tenant <Guid>] [-WhatIf] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -In Skype for Business Online, outbound calling restriction policies are used to restrict the type of audio conferencing and end user PSTN calls that can be made by users in your organization. -To get all the available policies in your organization run `Get-CSOnlineDialOutPolicy`. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Grant-CsDialoutPolicy -Identity "ken.myer@contoso.com" -PolicyName "DialoutCPCandPSTNInternational" -``` - -This example assigns the per-user outbound calling restriction policy DialoutCPCandPSTNInternational to the user with the User Principal Name "ken.myer@contoso.com". - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Grant-CsDialoutPolicy -Identity "ken.myer@contoso.com" -PolicyName $Null -``` - -In this example, any per-user outbound calling restriction policy previously assigned to the user ken.myer@contoso.com is unassigned from that user; as a result, Ken Myer will be managed by the global outbound calling restriction policy. To unassign a per-user policy, set the PolicyName to a null value ($Null). - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> Get-CsOnlineUser | Grant-CsDialoutPolicy -PolicyName "DialoutCPCInternationalPSTNDisabled" -``` - -This example assigns the per-user outbound calling restriction policy DialoutCPCInternationalPSTNDisabled to all the users in your organization. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the Identity of the user account to be to be modified. A user identity can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Returns the results of the command. By default, this cmdlet does not generate any output. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -"Name" of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:Redmond has a PolicyName equal to Redmond; likewise, a policy with the Identity tag:RedmondPolicy has a PolicyName equal to RedmondPolicy. - -To unassign a per-user policy previously assigned to a user, set the PolicyName to a null value ($Null). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Get-CSOnlineDialOutPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialoutpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Grant-CsExternalAccessPolicy.md b/skype/skype-ps/skype/Grant-CsExternalAccessPolicy.md index ba1d38c7cc..cee8b30442 100644 --- a/skype/skype-ps/skype/Grant-CsExternalAccessPolicy.md +++ b/skype/skype-ps/skype/Grant-CsExternalAccessPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csexternalaccesspolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/grant-csexternalaccesspolicy +applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsExternalAccessPolicy schema: 2.0.0 manager: bulenteg @@ -15,37 +15,51 @@ ms.reviewer: rogupta ## SYNOPSIS Enables you to assign an external access policy to a user or a group of users. -External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as MSN; and, 3) access Skype for Business Server over the Internet, without having to log on to your internal network. -This cmdlet was introduced in Lync Server 2010. +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; and, 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype. +This cmdlet was introduced in Lync Server 2010. ## SYNTAX +### Identity (Default) +``` +Grant-CsExternalAccessPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsExternalAccessPolicy [-Identity] <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsExternalAccessPolicy [[-PolicyName] <String>] [-Group] <String> [-Rank] <Int32> [<CommonParameters>] +``` + +### GrantToTenant ``` -Grant-CsExternalAccessPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +Grant-CsExternalAccessPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] ``` ## DESCRIPTION -When you install Skype for Business Server your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with other people who have SIP accounts in your Active Directory Domain Services. +When you install Microsoft Teams or Skype for Business Server, your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with other people who have SIP accounts in your Active Directory Domain Services. In addition, users are not allowed to access Skype for Business Server over the Internet; instead, they must be logged on to your internal network before they will be able to log on to Skype for Business Server. That might be sufficient to meet your communication needs. If it doesn't meet your needs you can use external access policies to extend the ability of your users to communicate and collaborate. External access policies can grant (or revoke) the ability of your users to do any or all of the following: -1. -Communicate with people who have SIP accounts with a federated organization. +1. Communicate with people who have SIP accounts with a federated organization. Note that enabling federation will not automatically provide users with this capability. Instead, you must enable federation, and then assign users an external access policy that gives them the right to communicate with federated users. -2. -Communicate with people who have SIP accounts with a public instant messaging service such as MSN. +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration). + +3. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. -3. -Access Skype for Business Server over the Internet, without having to first log on to your internal network. +4. Access Skype for Business Server over the Internet, without having to first log on to your internal network. This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. When you install Skype for Business Server, a global external access policy is automatically created for you. @@ -61,7 +75,6 @@ For example, suppose you create a per-user policy that allows communication with As long as that policy is in force, Ken will be allowed to communicate with federated users even if this type of communication is not allowed by Ken's site policy or by the global policy. That's because the settings in the per-user policy take precedence. - ## EXAMPLES ### -------------------------- EXAMPLE 1 -------------------------- @@ -71,7 +84,6 @@ Grant-CsExternalAccessPolicy -Identity "Ken Myer" -PolicyName RedmondAccessPolic Example 1 assigns the external access policy RedmondAccessPolicy to the user with the Active Directory display name Ken Myer. - ### -------------------------- EXAMPLE 2 -------------------------- ``` Get-CsUser -LdapFilter "l=Redmond" | Grant-CsExternalAccessPolicy -PolicyName RedmondAccessPolicy @@ -81,7 +93,6 @@ The command shown in Example 2 assigns the external access policy RedmondAccessP To do this, the command first uses the Get-CsUser cmdlet and the LdapFilter parameter to return a collection of all the users who work in Redmond; the filter value "l=Redmond" limits returned data to those users who work in the city of Redmond (the l in the filter, a lowercase L, represents the locality). That collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy RedmondAccessPolicy to each user in the collection. - ### -------------------------- EXAMPLE 3 -------------------------- ``` Get-CsUser -LdapFilter "Title=Sales Representative" | Grant-CsExternalAccessPolicy -PolicyName SalesAccessPolicy @@ -91,7 +102,6 @@ In Example 3, all the users who have the job title "Sales Representative" are as To perform this task, the command first uses the Get-CsUser cmdlet and the LdapFilter parameter to return a collection of all the Sales Representatives; the filter value "Title=Sales Representative" restricts the returned collection to users who have the job title "Sales Representative". This filtered collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy SalesAccessPolicy to each user in the collection. - ### -------------------------- EXAMPLE 4 -------------------------- ``` Get-CsUser -Filter {ExternalAccessPolicy -eq $Null} | Grant-CsExternalAccessPolicy -PolicyName BasicAccessPolicy @@ -101,7 +111,6 @@ The command shown in Example 4 assigns the external access policy BasicAccessPol (That is, users currently being governed by a site policy or by the global policy.) To do this, the Get-CsUser cmdlet and the Filter parameter are used to return the appropriate set of users; the filter value {ExternalAccessPolicy -eq $Null} limits the returned data to user accounts where the ExternalAccessPolicy property is equal to (-eq) a null value ($Null). By definition, ExternalAccessPolicy will be null only if users have not been assigned a per-user policy. - ### -------------------------- EXAMPLE 5 -------------------------- ``` Get-CsUser -OU "ou=US,dc=litwareinc,dc=com" | Grant-CsExternalAccessPolicy -PolicyName USAccessPolicy @@ -111,7 +120,6 @@ Example 5 assigns the external access policy USAccessPolicy to all the users who The command starts off by calling the Get-CsUser cmdlet and the OU parameter; the parameter value "ou=US,dc=litwareinc,dc=com" limits the returned data to user accounts found in the US OU. The returned collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy USAccessPolicy to each user in the collection. - ### -------------------------- EXAMPLE 6 -------------------------- ``` Get-CsUser | Grant-CsExternalAccessPolicy -PolicyName $Null @@ -121,7 +129,6 @@ Example 6 unassigns any per-user external access policy previously assigned to a To do this, the command calls the Get-CsUser cmdlet (without any additional parameters) in order to return a collection of all the users enabled for Skype for Business Server. That collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which uses the syntax "`-PolicyName $Null`" to remove any per-user external access policy previously assigned to these users. - ## PARAMETERS ### -Identity @@ -134,9 +141,9 @@ For example, the Identity "* Smith" returns all the users with a display name th ```yaml Type: UserIdParameter -Parameter Sets: (All) +Parameter Sets: GrantToUser Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: True Position: 1 @@ -156,7 +163,7 @@ To unassign a per-user policy previously assigned to a user, set the PolicyName Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 2 @@ -173,7 +180,7 @@ If this parameter is not specified, then the Grant-CsExternalAccessPolicy cmdlet Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -190,7 +197,7 @@ By default, the Grant-CsExternalAccessPolicy cmdlet does not pass objects throug Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -206,7 +213,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -222,7 +229,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -247,21 +254,46 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". ```yaml Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Parameter Sets: GrantToTenant +Aliases: -Required: False -Position: Named +Required: True +Position: 0 Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -307,5 +339,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md) [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md) - - diff --git a/skype/skype-ps/skype/Grant-CsExternalUserCommunicationPolicy.md b/skype/skype-ps/skype/Grant-CsExternalUserCommunicationPolicy.md deleted file mode 100644 index ef57c993f7..0000000000 --- a/skype/skype-ps/skype/Grant-CsExternalUserCommunicationPolicy.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csexternalusercommunicationpolicy -applicable: Skype for Business Online -title: Grant-CsExternalUserCommunicationPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsExternalUserCommunicationPolicy - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -### Identity (Default) -``` -Grant-CsExternalUserCommunicationPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> - [-Tenant <Guid>] [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsExternalUserCommunicationPolicy [-PolicyName] <String> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -PolicyName -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -PARAMVALUE: Fqdn - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -PARAMVALUE: UserIdParameter - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Grant-CsGraphPolicy.md b/skype/skype-ps/skype/Grant-CsGraphPolicy.md index cb9c67110a..d1c384d7e3 100644 --- a/skype/skype-ps/skype/Grant-CsGraphPolicy.md +++ b/skype/skype-ps/skype/Grant-CsGraphPolicy.md @@ -1,20 +1,20 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csgraphpolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/skype/grant-csgraphpolicy +applicable: Lync Server 2010 title: Grant-CsGraphPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Grant-CsGraphPolicy ## SYNOPSIS Use the Grant-CsGraphPolicy cmdlet to assign a previously defined graph policy to a user or to your organization. -Graph policies determine whether users can pre-load content or files that are attached to an Outlook meeting invitation into a Skype for Business Online meeting, +Graph policies determine whether users can pre-load content or files that are attached to an Outlook meeting invitation into a Microsoft Teams or Skype for Business Online meeting, ## SYNTAX @@ -31,7 +31,7 @@ Grant-CsGraphPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController < ``` ## DESCRIPTION -Skype for Business Online supports a Global CsGraphPolicy that is set by default to enable Outlook content pre-load in Skype for Business Online meetings. +Microsoft Teams and Skype for Business Online support a Global CsGraphPolicy that is set by default to enable Outlook content pre-load in Microsoft Teams or Skype for Business Online meetings. The Global policy can't be changed by you. Use the Grant-CsGraphPolicy cmdlet to assign a predefined graph policy to users in your organization. @@ -55,17 +55,17 @@ This example grants the "GraphDisabled" policy to Ken Myer. Specifies the name of the graph policy to grant to the tenant or user. The two options are: -Graph Enabled: Granting this policy will enable the pre-loading content or files that are attached to an Outlook meeting invitation into a Skype for Business Online meeting. +Graph Enabled: Granting this policy will enable the pre-loading content or files that are attached to an Outlook meeting invitation into a Microsoft Teams or Skype for Business Online meeting. For example, `Grant-CsGraphPolicy -PolicyName "Graph Enabled"`. -Graph Disabled: Granting this policy will disable the pre-loading of content, files or attachments attached to an Outlook meeting invitation into a Skype for Business Online meeting. +Graph Disabled: Granting this policy will disable the pre-loading of content, files or attachments attached to an Outlook meeting invitation into a Microsoft Teams or Skype for Business Online meeting. For example, `Grant-CsGraphPolicy -PolicyName "Graph Disabled"`. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 2 @@ -81,7 +81,7 @@ The Confirm switch causes the command to pause processing, and requires confirma Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -98,7 +98,7 @@ Valid inputs for this parameter are either the fully qualified domain name (FQDN Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -114,7 +114,7 @@ Specifies the identity of the user who will be granted the graph policy. Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 1 @@ -130,7 +130,7 @@ Enables you to pass a user object through the pipeline that represents the user Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -146,7 +146,7 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -163,27 +163,7 @@ By using this switch, you can view what changes would occur without having to co Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -208,5 +188,3 @@ The Grant-CsGraphPolicy cmdlet returns an object of type Microsoft.Rtc.Managemen ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Grant-CsHostedVoicemailPolicy.md b/skype/skype-ps/skype/Grant-CsHostedVoicemailPolicy.md index 42ae73874d..9fe8d50ae6 100644 --- a/skype/skype-ps/skype/Grant-CsHostedVoicemailPolicy.md +++ b/skype/skype-ps/skype/Grant-CsHostedVoicemailPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cshostedvoicemailpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/grant-cshostedvoicemailpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsHostedVoicemailPolicy schema: 2.0.0 manager: bulenteg @@ -74,7 +74,7 @@ Full data type: Microsoft.Rtc.Management.AD.UserIdParameter Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: True Position: 1 @@ -92,7 +92,7 @@ Per-user hosted voice mail policy identities include a prefix of tag: that shoul Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 2 @@ -109,7 +109,7 @@ If no domain controller is specified, the first available will be used. Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -126,7 +126,7 @@ By default, this cmdlet does not generate any output. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -142,7 +142,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -158,39 +158,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -{{Fill Tenant Description}} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -230,4 +198,3 @@ When used with the PassThru parameter, returns an object of type Microsoft.Rtc.M [Get-CsHostedVoicemailPolicy](Get-CsHostedVoicemailPolicy.md) [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Grant-CsIPPhonePolicy.md b/skype/skype-ps/skype/Grant-CsIPPhonePolicy.md index 08567b59be..0bc1ea6d26 100644 --- a/skype/skype-ps/skype/Grant-CsIPPhonePolicy.md +++ b/skype/skype-ps/skype/Grant-CsIPPhonePolicy.md @@ -1,20 +1,20 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csipphonepolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/skype/grant-csipphonepolicy +applicable: Skype for Business Server 2019 title: Grant-CsIPPhonePolicy, Skype for Business Server 2019 schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Grant-CsIPPhonePolicy ## SYNOPSIS Use the Grant-CsIPPhonePolicy cmdlet to assign an Internet Protocol (IP) phone policy to a user or a group of users. -IP phone policies determine the features of Skype for Business Online and Skype for Business Server 2019 that are available to users. +IP phone policies determine the features of Microsoft Teams, Skype for Business Online, or Skype for Business Server 2019 that are available to users. For example, you might enable the Better Together Over Ethernet feature for some users while disabling it for others. ## SYNTAX @@ -32,7 +32,7 @@ Grant-CsIPPhonePolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController ``` ## DESCRIPTION -Skype for Business Online uses IP phone policies to determine the features and capabilities that are available to users. +Microsoft Teams or Skype for Business Online uses IP phone policies to determine the features and capabilities that are available to users. IP phone policies are applied each time a user accesses the system, regardless of where the user logs on from. ## EXAMPLES @@ -68,7 +68,7 @@ For example: `Grant-CsIPPhonePolicy -Identity "Ken Myer" -PolicyName $Null` Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online, Skype for Business Server 2019 +applicable: Microsoft Teams, Skype for Business Server 2019 Required: False Position: 2 @@ -84,7 +84,7 @@ The Confirm switch causes the command to pause processing, and requires confirma Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online, Skype for Business Server 2019 +applicable: Microsoft Teams, Skype for Business Server 2019 Required: False Position: Named @@ -100,7 +100,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online, Skype for Business Server 2019 +applicable: Microsoft Teams, Skype for Business Server 2019 Required: False Position: Named @@ -123,7 +123,7 @@ Example: 98403f08-577c-46dd-851a-f0460a13b03d Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online, Skype for Business Server 2019 +applicable: Microsoft Teams, Skype for Business Server 2019 Required: False Position: 1 @@ -140,7 +140,7 @@ By default, the Grant-CsIPPhonePolicy cmdlet does not pass objects through the p Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online, Skype for Business Server 2019 +applicable: Microsoft Teams, Skype for Business Server 2019 Required: False Position: Named @@ -156,7 +156,7 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online, Skype for Business Server 2019 +applicable: Microsoft Teams, Skype for Business Server 2019 Required: False Position: Named @@ -173,27 +173,7 @@ By using this switch, you can view what changes would occur without having to co Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online, Skype for Business Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams, Skype for Business Server 2019 Required: False Position: Named @@ -223,5 +203,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Get-CsIPPhonePolicy](Get-CsIPPhonePolicy.md) [Set-CsIPPhonePolicy](Set-CsIPPhonePolicy.md) - - diff --git a/skype/skype-ps/skype/Grant-CsLocationPolicy.md b/skype/skype-ps/skype/Grant-CsLocationPolicy.md index 718bab854e..6ea4f48cc5 100644 --- a/skype/skype-ps/skype/Grant-CsLocationPolicy.md +++ b/skype/skype-ps/skype/Grant-CsLocationPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cslocationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-cslocationpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsLocationPolicy schema: 2.0.0 @@ -216,4 +216,3 @@ When used with the PassThru parameter, returns an object of type Microsoft.Rtc.M [Test-CsLocationPolicy](Test-CsLocationPolicy.md) [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Grant-CsMobilityPolicy.md b/skype/skype-ps/skype/Grant-CsMobilityPolicy.md index 22b0e71b0d..a6b4002ac5 100644 --- a/skype/skype-ps/skype/Grant-CsMobilityPolicy.md +++ b/skype/skype-ps/skype/Grant-CsMobilityPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csmobilitypolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/grant-csmobilitypolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsMobilityPolicy schema: 2.0.0 manager: bulenteg @@ -15,7 +15,7 @@ ms.reviewer: rogupta ## SYNOPSIS Grants a per-user mobility policy to a user or group of users. -Mobility policies determine whether or not a user can use a mobile device (such as a cell phone) to connect to Skype for Business Server. +Mobility policies determine whether or not a user can use a mobile device (such as a cell phone) to connect to Microsoft Teams or Skype for Business Server. These policies also manage a user's ability to employ Call via Work, a feature that enables users to make and receive phone calls on their mobile phone by using their work phone number instead of their mobile phone number. Mobility policies can also be used to require Wi-Fi connections when making or receiving calls. This cmdlet was introduced in the cumulative update for Lync Server 2010: November 2011. @@ -30,19 +30,19 @@ Grant-CsMobilityPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainControlle ## DESCRIPTION -Skype for Business Mobile is a client application that enables users to run Skype for Business Server on their mobile phones. +Microsoft Teams Mobile or Skype for Business Mobile is a client application that enables users to run Microsoft Teams or Skype for Business Server on their mobile phones. Call via Work provides a way for users to make calls on their mobile phone and yet have it appear as though the call originated from their work phone number instead of their mobile phone number. Users who have been enabled for Call via Work can achieve this either by dialing directly from their mobile phone or by using the dial-out conferencing option. With dial-out conferencing, a user effectively asks the Mobility Service server to make a call for them. The server will set up the call, and then call the user back on their mobile phone. After the user has answered, the server will then dial the party being called. -Both of these capabilities can be managed by using mobility policies. +Both of these capabilities can be managed by using mobility policies. -With Skype for Business Server, mobile devices can make or receive phone calls by using either the standard cellular phone network. +With Microsoft Teams or Skype for Business Server, mobile devices can make or receive phone calls by using either the standard cellular phone network. or by using Wi-Fi connections. Mobility policies can be used to require Wi-Fi connections and to prevent calls over the cellular network. -When you install Skype for Business Server, you will have a single, global mobility policy that applies to all your users. +When you install Microsoft Teams or Skype for Business Server, you will have a single, global mobility policy that applies to all your users. However, administrators can use the New-CsMobilityPolicy cmdlet to create custom policies at either the site or the per-user scope. If you create a new policy at the site scope that policy will automatically be assigned to the appropriate site. @@ -119,7 +119,7 @@ For example, the Identity "* Smith" will assign the policy to all the users who Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: True Position: 1 @@ -135,7 +135,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -152,7 +152,7 @@ If this parameter is not specified then the Grant-CsMobilityPolicy cmdlet will c Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -169,7 +169,7 @@ By default, the Grant-CsMobilityPolicy cmdlet does not pass objects through the Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -194,7 +194,7 @@ To unassign a per-user policy previously assigned to a user, set the PolicyName Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 2 @@ -210,7 +210,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -226,23 +226,6 @@ Accept wildcard characters: False Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online Required: False Position: Named @@ -281,5 +264,3 @@ However, if you include the PassThru parameter, the cmdlet will be able to pipel ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Grant-CsOUPermission.md b/skype/skype-ps/skype/Grant-CsOUPermission.md index 8d1491e4a0..222046671f 100644 --- a/skype/skype-ps/skype/Grant-CsOUPermission.md +++ b/skype/skype-ps/skype/Grant-CsOUPermission.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csoupermission +online version: https://learn.microsoft.com/powershell/module/skype/grant-csoupermission applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsOUPermission schema: 2.0.0 @@ -286,5 +286,3 @@ The Grant-CsOUPermission cmdlet does not return any objects or values. [Revoke-CsOUPermission](Revoke-CsOUPermission.md) [Test-CsOUPermission](Test-CsOUPermission.md) - - diff --git a/skype/skype-ps/skype/Grant-CsOnlineVoiceRoutingPolicy.md b/skype/skype-ps/skype/Grant-CsOnlineVoiceRoutingPolicy.md deleted file mode 100644 index f53d3511e2..0000000000 --- a/skype/skype-ps/skype/Grant-CsOnlineVoiceRoutingPolicy.md +++ /dev/null @@ -1,222 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoiceroutingpolicy -applicable: Skype for Business Online -title: Grant-CsOnlineVoiceRoutingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsOnlineVoiceRoutingPolicy - -## SYNOPSIS -Assigns a per-user online voice routing policy to one or more users. Online voice routing policies manage online PSTN usages for Phone System users. - -## SYNTAX - -### Identity (Default) -``` -Grant-CsOnlineVoiceRoutingPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsOnlineVoiceRoutingPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. - -Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Grant-CsOnlineVoiceRoutingPolicy -Identity "Ken Myer" -PolicyName "RedmondOnlineVoiceRoutingPolicy" -``` - -The command shown in Example 1 assigns the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy to the user with the display name "Ken Myer". - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Grant-CsOnlineVoiceRoutingPolicy -Identity "Ken Myer" -PolicyName $Null -``` - -In Example 2, any per-user online voice routing policy previously assigned to the user Ken Myer is unassigned from that user; as a result, Ken Myer will be managed by the global online voice routing policy. To unassign a per-user policy, set the PolicyName to a null value ($Null). - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> Get-CsOnlineUser | Grant-CsOnlineVoiceRoutingPolicy -PolicyName "RedmondOnlineVoiceRoutingPolicy" -``` - -Example 3 assigns the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy to all the users in the tenant. To do this, the command first calls the `Get-CsOnlineUser` cmdlet to get all user accounts enabled for Skype for Business Online. Those user accounts are then piped to the `Grant-CsOnlineVoiceRoutingPolicy` cmdlet, which assigns each user the online voice routing policy RedmondOnlineVoiceRoutingPolicy. - -### -------------------------- Example 4 -------------------------- -``` -PS C:\> Grant-CsOnlineVoiceRoutingPolicy -PolicyName "RedmondOnlineVoiceRoutingPolicy" -Global -``` - -Example 4 assigns the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy to all the users in the tenant, except any that have an explicit policy assignment. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Global -When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant, except any that have an explicit policy assignment. To skip a warning when you do this operation, specify this parameter. - -```yaml -Type: SwitchParameter -Parameter Sets: GrantToTenant -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the user account to be assigned the per-user online voice routing policy. User Identities can be specified using one of the following formats: 1) the user's SIP address; 2) the user's user principal name (UPN); or, 3) the user's Active Directory display name (for example, Ken Myer). - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PassThru -Enables you to pass a user object through the pipeline that represents the user account being assigned the online voice routing policy. By default, the `Grant-CsOnlineVoiceRoutingPolicy` cmdlet does not pass objects through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -"Name" of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:Redmond has a PolicyName equal to Redmond; likewise, a policy with the Identity tag:RedmondOnlineVoiceRoutingPolicy has a PolicyName equal to RedmondOnlineVoiceRoutingPolicy. - -To unassign a per-user policy previously assigned to a user, set the PolicyName to a null value ($Null). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose online voice routing policy is being assigned. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[New-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroutingpolicy?view=skype-ps) - -[Get-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroutingpolicy?view=skype-ps) - -[Set-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroutingpolicy?view=skype-ps) - -[Remove-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroutingpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Grant-CsOnlineVoicemailPolicy.md b/skype/skype-ps/skype/Grant-CsOnlineVoicemailPolicy.md deleted file mode 100644 index 20bcf3a5d0..0000000000 --- a/skype/skype-ps/skype/Grant-CsOnlineVoicemailPolicy.md +++ /dev/null @@ -1,190 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoicemailpolicy -applicable: Skype for Business Online -title: Grant-CsOnlineVoicemailPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsOnlineVoicemailPolicy - -## SYNOPSIS -Assigns a online voice mail policy at the per-user scope. Online voicemail policies manage usages for Voicemail service. - -## SYNTAX - -``` -Grant-CsOnlineVoicemailPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet assigns an existing user-specific online voicemail policy to a user. Online voicemail policies are used by the organization to manage Voicemail-related features such as transcription. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Grant-CsOnlineVoicemailPolicy -Identity "sip:user@contoso.com" -PolicyName TranscriptionDisabled -``` - -The command shown in Example 1 assigns the per-user online voicemail policy TranscriptionDisabled to a single user with SIP URI sip:user@contoso.com. - - -## PARAMETERS - -### -Identity -The Identity parameter represents the ID of the specific user in your organization; this can be either a SIP URI or an Object ID. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -A unique identifier(name) of the policy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Enables you to specify the fully qualified domain name (FQDN) of a domain controller to be contacted when assigning the new policy. If this parameter is not specified then the Grant-CsMobilityPolicy cmdlet will contact the first available domain controller. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsOnlineVoicemailPolicy cmdlet does not pass objects through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the Skype for Business Online tenant account whose voicemail policy is to be retrieved. For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" You can return the tenant ID for each of your tenants by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoicemailpolicy?view=skype-ps) - -[Set-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailpolicy?view=skype-ps) - -[New-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoicemailpolicy?view=skype-ps) - -[Remove-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoicemailpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Grant-CsPersistentChatPolicy.md b/skype/skype-ps/skype/Grant-CsPersistentChatPolicy.md index cd502ce48f..2802ff6d76 100644 --- a/skype/skype-ps/skype/Grant-CsPersistentChatPolicy.md +++ b/skype/skype-ps/skype/Grant-CsPersistentChatPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cspersistentchatpolicy -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/grant-cspersistentchatpolicy +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsPersistentChatPolicy schema: 2.0.0 manager: rogupta @@ -227,4 +227,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsPersistentChatPolicy](Remove-CsPersistentChatPolicy.md) [Set-CsPersistentChatPolicy](Set-CsPersistentChatPolicy.md) - diff --git a/skype/skype-ps/skype/Grant-CsPinPolicy.md b/skype/skype-ps/skype/Grant-CsPinPolicy.md index e949da7632..7abc34da1c 100644 --- a/skype/skype-ps/skype/Grant-CsPinPolicy.md +++ b/skype/skype-ps/skype/Grant-CsPinPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cspinpolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-cspinpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsPinPolicy schema: 2.0.0 @@ -223,5 +223,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsPinPolicy](Remove-CsPinPolicy.md) [Set-CsPinPolicy](Set-CsPinPolicy.md) - - diff --git a/skype/skype-ps/skype/Grant-CsPresencePolicy.md b/skype/skype-ps/skype/Grant-CsPresencePolicy.md index 0860011f1f..0b4f666350 100644 --- a/skype/skype-ps/skype/Grant-CsPresencePolicy.md +++ b/skype/skype-ps/skype/Grant-CsPresencePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cspresencepolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-cspresencepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsPresencePolicy schema: 2.0.0 @@ -240,4 +240,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsPresencePolicy](Remove-CsPresencePolicy.md) [Set-CsPresencePolicy](Set-CsPresencePolicy.md) - diff --git a/skype/skype-ps/skype/Grant-CsSetupPermission.md b/skype/skype-ps/skype/Grant-CsSetupPermission.md index 07982ebbf4..7884f28095 100644 --- a/skype/skype-ps/skype/Grant-CsSetupPermission.md +++ b/skype/skype-ps/skype/Grant-CsSetupPermission.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cssetuppermission +online version: https://learn.microsoft.com/powershell/module/skype/grant-cssetuppermission applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsSetupPermission schema: 2.0.0 @@ -236,5 +236,3 @@ The Grant-CsSetupPermission cmdlet does not return any objects or values. [Revoke-CsSetupPermission](Revoke-CsSetupPermission.md) [Test-CsSetupPermission](Test-CsSetupPermission.md) - - diff --git a/skype/skype-ps/skype/Grant-CsTeamsAppPermissionPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsAppPermissionPolicy.md deleted file mode 100644 index ff525d8c13..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsAppPermissionPolicy.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsapppermissionpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsAppPermissionPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Grant-CsTeamsAppPermissionPolicy - -## SYNOPSIS - -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Permission Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -**We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -You can use this cmdlet to assign a specific custom policy to a user. - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsAppPermissionPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <System.Guid>] - [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsAppPermissionPolicy [-PolicyName] <String> [-Tenant <System.Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Permission Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -**We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -You can use this cmdlet to assign a specific custom policy to a user. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsAppPermissionPolicy -Identity "Ken Myer" -PolicyName StudentAppPermissionPolicy -``` - -In this example, a user with identity "Ken Myer" is being assigned the StudentAppPermissionPolicy - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Do not use. -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Global -Resets the values in the global policy to match those in the provided (PolicyName) policy. Note that this means all users with no explicit policy assigned will have these new policy settings. - -```yaml -Type: SwitchParameter -Parameter Sets: GrantToTenant -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The user to whom the policy should be assigned. - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PassThru - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Do not use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsAppSetupPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsAppSetupPolicy.md deleted file mode 100644 index 7035485538..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsAppSetupPolicy.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsappsetuppolicy -applicable: Skype for Business Online -title: Grant-CsTeamsAppSetupPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Grant-CsTeamsAppSetupPolicy - -## SYNOPSIS - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -**We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -You can use this cmdlet to assign a specific custom policy to a user. - - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsAppSetupPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <System.Guid>] - [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsAppSetupPolicy [-PolicyName] <String> [-Tenant <System.Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -**We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -You can use this cmdlet to assign a specific custom policy to a user. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsAppSetupPolicy -identity "Ken Myer" -PolicyName StudentAppSetupPolicy -``` - -In this example, a user with identity "Ken Myer" is being assigned the StudentAppSetupPolicy - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Do not use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Global -Resets the values in the global policy to match those in the provided (PolicyName) policy. Note that this means all users with no explicit policy assigned will have these new policy settings. - -```yaml -Type: SwitchParameter -Parameter Sets: GrantToTenant -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The user to whom the policy should be assigned. - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PassThru - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Do not use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsCallParkPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsCallParkPolicy.md deleted file mode 100644 index b4b93a9c07..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsCallParkPolicy.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamscallparkpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsCallParkPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsTeamsCallParkPolicy - -## SYNOPSIS - -The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone. The Grant-CsTeamsCallParkPolicy cmdlet lets you assign a custom policy to a specific user. - -NOTE: the call park feature currently only available in desktop, web clients and mobile clients. Call Park functionality is currently on the roadmap for Teams IP Phones. Supported with TeamsOnly mode for users with the Phone Sytem license - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsCallParkPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <System.Guid>] - [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsCallParkPolicy [-PolicyName] <String> [-Tenant <System.Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different phone. The Grant-CsTeamsCallParkPolicy cmdlet lets you assign a custom policy to a specific user. - - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsCallParkPolicy -PolicyName SalesPolicy -Identity "Ken Myer" -``` - -Assigns a custom policy "Sales Policy" to the user "Ken Myer" - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Internal Microsoft use only. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Global -Internal Microsoft use only. - -```yaml -Type: SwitchParameter -Parameter Sets: GrantToTenant -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The User Id of the user to whom the policy is being assigned. - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PassThru -If present, causes the cmdlet to pass the user object (or objects) through the Windows PowerShell pipeline. By default, the cmdlet does not pass objects through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -"Name" of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope ("tag:"). For example, a policy that has the Identity tag:Redmond has a PolicyName equal to Redmond; a policy with the Identity tag:RedmondConferencingPolicy has a PolicyName equal to RedmondConferencingPolicy. - -If you set PolicyName to a null value, then the command will unassign any per-user policy assigned to the user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md deleted file mode 100644 index 85c64ff835..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamscallingpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsCallingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsTeamsCallingPolicy - -## SYNOPSIS - -Cmdlet to assign a specific Teams Calling Policy to a user. - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsCallingPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsCallingPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The Teams Calling Policies designate which users are able to use calling functionality within teams and determine the interoperability state with Skype for Business. This cmdlet allows admins to grant user level policies to individual users. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsCallingPolicy -identity "Ken Myer" -PolicyName SalesCallingPolicy -``` - -Assigns the TeamsCallingPolicy called "SalesCallingPolicy" to the user "Ken Myer" - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Internal Microsoft use - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Global -Internal Microsoft use - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The user object to whom the policy is being assigned. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsCallingPolicy cmdlet does not pass objects through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The name of the policy being assigned. To remove an existing user level policy assignment, specify PolicyName as null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsComplianceRecordingPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsComplianceRecordingPolicy.md deleted file mode 100644 index 98e2c9c684..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsComplianceRecordingPolicy.md +++ /dev/null @@ -1,240 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsComplianceRecordingPolicy -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# Grant-CsTeamsComplianceRecordingPolicy - -## SYNOPSIS -Assigns a per-user Teams recording policy to one or more users. -This policy is used to govern automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsComplianceRecordingPolicy [-Identity <UserIdParameter>] [-PolicyName <String>] - [-Tenant <System.Guid>] [-DomainController <Fqdn>] - [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsComplianceRecordingPolicy [-Global] [-PolicyName <String>] - [-Tenant <System.Guid>] [-DomainController <Fqdn>] - [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Teams recording policies are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. - -Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. -Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. - -Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. -The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. -Existing calls and meetings are unaffected. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsComplianceRecordingPolicy -Identity 'Ken Myer' -PolicyName 'ContosoPartnerComplianceRecordingPolicy' -``` - -The command shown in Example 1 assigns the per-user Teams recording policy ContosoPartnerComplianceRecordingPolicy to the user with the display name "Ken Myer". - -### Example 2 -```powershell -PS C:\> Grant-CsTeamsComplianceRecordingPolicy -Identity 'Ken Myer' -PolicyName $null -``` - -In Example 2, any per-user Teams recording policy previously assigned to the user "Ken Myer" is revoked. -As a result, the user will be managed by the global Teams recording policy. - -## PARAMETERS - -### -Identity -Indicates the Identity of the user account to be assigned the per-user Teams recording policy. -User Identities can be specified using one of the following formats: -1) the user's SIP address; -2) the user's user principal name (UPN); -3) the user's Active Directory display name (for example, Ken Myer). - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Global -When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. -To skip a warning when you do this operation, specify "-Global". - -```yaml -Type: SwitchParameter -Parameter Sets: GrantToTenant -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -Name of the policy to be assigned. -The PolicyName is simply the policy Identity without the policy scope i.e. the "Tag:" prefix. -For example, a policy with the Identity Tag:ContosoPartnerComplianceRecordingPolicy has a PolicyName equal to ContosoPartnerComplianceRecordingPolicy. - -To revoke a per-user policy previously assigned to a user, set the PolicyName to a null value ($null). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru -Enables you to pass a user object through the pipeline that represents the user account being assigned the Teams recording policy. -By default, the Grant-CsTeamsComplianceRecordingPolicy cmdlet does not pass objects through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) diff --git a/skype/skype-ps/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md deleted file mode 100644 index 9746bf999d..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsemergencycallroutingpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsEmergencyCallRoutingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Grant-CsTeamsEmergencyCallRoutingPolicy - -## SYNOPSIS - -## SYNTAX - -``` -Grant-CsTeamsEmergencyCallRoutingPolicy [-PolicyName] <String> [-Tenant <System.Guid>] - [-DomainController <Fqdn>] [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet assigns a Teams Emergency Call Routing policy with one user. Teams Emergency Call Routing policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Grant-CsTeamsEmergencyCallRoutingPolicy -Identity user1 -PolicyName TestECRP -``` - -This example assigns a Teams Emergency Call Routing policy(TestECRP) to a user(user1) - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Allows you to specify a domain controller. If no domain controller is specified, the first available will be used. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the user account the policy should be assigned to. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PassThru -Including this parameter (which does not take a value) displays the user information when the cmdlet completes. Normally there is no output when this cmdlet is run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The Identity of the Teams Emergency Call Routing policy to apply to the user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Microsoft internal usage only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsEmergencyCallingPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsEmergencyCallingPolicy.md deleted file mode 100644 index e8ada5e0b4..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsEmergencyCallingPolicy.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsemergencycallingpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsEmergencyCallingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Grant-CsTeamsEmergencyCallingPolicy - -## SYNOPSIS - -## SYNTAX - -``` -Grant-CsTeamsEmergencyCallingPolicy [-PolicyName] <String> [-Tenant <System.Guid>] [-DomainController <Fqdn>] - [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet assigns a Teams Emergency Calling policy to a user. Emergency Calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Grant-CsTeamsEmergencyCallingPolicy -Identity user1 -PolicyName TestECP -``` - -This example assigns a Teams Emergency Calling policy to a user - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Allows you to specify a domain controller. If no domain controller is specified, the first available will be used. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the user account the policy should be assigned to. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PassThru -Including this parameter (which does not take a value) displays the user information when the cmdlet completes. Normally there is no output when this cmdlet is run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The Identity of the Teams Emergency Calling policy to apply to the user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Microsoft internal usage only - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsMeetingBroadcastPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsMeetingBroadcastPolicy.md deleted file mode 100644 index 02f553dc15..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsMeetingBroadcastPolicy.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsmeetingbroadcastpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsMeetingBroadcastPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - - -# Grant-CsTeamsMeetingBroadcastPolicy - -## SYNOPSIS -Grant-CsTeamsMeetingBroadcastPolicy \[\[-Identity\] \<UserIdParameter\>\] \[-PolicyName\] \<string\> \[-Tenant \<guid\>\] \[-DomainController \<Fqdn\>\] \[-PassThru\] \[-WhatIf\] \[-Confirm\] \[\<CommonParameters\>\] - -Grant-CsTeamsMeetingBroadcastPolicy \[-PolicyName\] \<string\> \[-Tenant \<guid\>\] \[-DomainController \<Fqdn\>\] \[-PassThru\] \[-Global\] \[-WhatIf\] \[-Confirm\] \[\<CommonParameters\>\] - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsMeetingBroadcastPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> - [-Tenant <Guid>] [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsMeetingBroadcastPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -User-level policy for tenant admin to configure meeting broadcast behavior for the broadcast event organizer. Use this cmdlet to assign a policy to a user. - -## EXAMPLES - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Not applicable to online service. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Global - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsMeetingPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsMeetingPolicy.md deleted file mode 100644 index c721addffb..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsMeetingPolicy.md +++ /dev/null @@ -1,180 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsmeetingpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsMeetingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsTeamsMeetingPolicy - -## SYNOPSIS -Assigns a teams meeting policy at the per-user scope. The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users - - -## SYNTAX - -``` -Grant-CsTeamsMeetingPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Assigns a teams meeting policy at the per-user scope. The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsMeetingPolicy -identity "Ken Myer" -PolicyName StudentMeetingPolicy -``` - -In this example, a user with identity "Ken Myer" is being assigned the StudentMeetingPolicy - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Grant-CsTeamsMessagingPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsMessagingPolicy.md deleted file mode 100644 index 011caf6077..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsMessagingPolicy.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsmessagingpolicy -applicable: Skype for Business Online -title: Grant-CsTeamsMessagingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsTeamsMessagingPolicy - -## SYNOPSIS -Assigns a teams messaging policy at the per-user scope. Teams messaging policies determine the features and capabilities that can be used in messaging within the teams client. - - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsMessagingPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsMessagingPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Granular control over which messaging features your users can or cannot use is an important feature for many organizations. This cmdlet lets you assign a teams messaging policy at the per-user scope. Teams messaging policies determine the features and capabilities that can be used in messaging within the teams client. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsMessagingPolicy -identity "Ken Myer" -PolicyName StudentMessagingPolicy -``` - -In this example, a user with identity "Ken Myer" is being assigned the StudentMessagingPolicy - -### Example 2 -```powershell -PS C:\> Get-CsOnlineUser -Filter {Department -eq 'Executive Management'} | Grant-CsTeamsMessagingPolicy -PolicyName "ExecutivesPolicy" -``` - -In this example, the ExecutivesPolicy is being assigned to a whole department by piping the result of Get-CsOnlineUser cmdlet - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Grant-CsTeamsMobilityPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsMobilityPolicy.md deleted file mode 100644 index 399c366d3e..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsMobilityPolicy.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsmobilitypolicy -applicable: Skype for Business Online -title: Grant-CsTeamsMobilityPolicy -schema: 2.0.0 -manager: ritikag -author: saragava -ms.author: saragava -ms.reviewer: ---- - - -# Grant-CsTeamsMobilityPolicy - -## SYNOPSIS -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsMobilityPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <System.Guid>] - [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsMobilityPolicy [-PolicyName] <String> [-Tenant <System.Guid>] [-DomainController <Fqdn>] - [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Assigns a teams mobility policy at the per-user scope. - -The Grant-CsTeamsMobilityPolicy cmdlet lets an Admin assign a custom teams mobility policy to a user. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsMobilityPolicy -PolicyName SalesPolicy -Identity "Ken Myer" -``` -Assigns a custom policy "Sales Policy" to the user "Ken Myer" - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The User Id of the user to whom the policy is being assigned. - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PolicyName -The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the Global policy, you can assign $Null. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md b/skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md index b86ecc6870..49be661490 100644 --- a/skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md +++ b/skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsupgradepolicy -applicable: Skype for Business Online, Skype for Business Server 2019, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/grant-csteamsupgradepolicy +applicable: Skype for Business Server 2019, Skype for Business Server 2015 title: Grant-CsTeamsUpgradePolicy schema: 2.0.0 manager: bulenteg @@ -17,16 +17,35 @@ TeamsUpgradePolicy allows administrators to manage the transition from Skype for ## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsUpgradePolicy [[-Identity] <String>] [-MigrateMeetingsToTeams <Boolean>] [-PassThru] + [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant ``` -Grant-CsTeamsUpgradePolicy [-Identity] <UserIdParameter>] [-PolicyName] <string> [-Tenant <guid>] [-Global] [-MigrateMeetingsToTeams] [-Confirm] [<CommonParameters>] +Grant-CsTeamsUpgradePolicy [-MigrateMeetingsToTeams <Boolean>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Force] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsUpgradePolicy [-MigrateMeetingsToTeams <Boolean>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] ``` ## DESCRIPTION -TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. As an organization with Skype for Business starts to adopt Teams, administrators can manage the user experience in their organization using the concept of coexistence "mode". Mode defines in which client incoming chats and calls land as well as in what service (Teams or Skype for Business) new meetings are scheduled in. Mode also governs what functionality is avaiable in the Teams client. Finally, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. + +TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. As an organization with Skype for Business starts to adopt Teams, administrators can manage the user experience in their organization using the concept of coexistence "mode". Mode defines in which client incoming chats and calls land as well as in what service (Teams or Skype for Business) new meetings are scheduled in. Mode also governs what functionality is available in the Teams client. Finally, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. This cmdlet enables admins to apply TeamsUpgradePolicy to either individual users or to set the default for the entire organization. -Office 365 provides all relevant instances of TeamsUpgradePolicy via built-in, read-only policies. The built-in instances are listed below. +**[NOTE]** Earlier versions of this cmdlet used to support -MigrateMeetingsToTeams option. This option is removed in later versions of the module. Tenants must run Start-CsExMeetingMigration. See [Start-CsExMeetingMigrationService](/powershell/module/skype/start-csexmeetingmigration). + +Microsoft Teams provides all relevant instances of TeamsUpgradePolicy via built-in, read-only policies. The built-in instances are as follows: |Identity|Mode|NotifySfbUsers|Comments| |---|---|---|---| @@ -41,18 +60,30 @@ Office 365 provides all relevant instances of TeamsUpgradePolicy via built-in, r |UpgradeToTeams|TeamsOnly|False|Use this mode to upgrade users to Teams and to prevent chat, calling, and meeting scheduling in Skype for Business.| |Global|Islands|False|| -**NOTES:** -- TeamsUpgradePolicy is available in both Office 365 and in on-premises versions of Skype for Business Server, but there are differences: - - In Office 365, admins can specify both coexistence mode and whether to trigger notifications of pending upgrade. - - In on-premises with Skype for Business Server, the only available option is to trigger notifications. Skype for Business Server 2015 with CU8 or Skype for Business Server 2019 are required. -- TeamsUpgradePolicy in Office 365 can be granted to users homed on-premises in hybrid deployments of Skype for Business as follows: - - Coexistence mode is honored by users homed on-premises, however on-premises users cannot be granted the UpgradeToTeams instance (mode=TeamsOnly) of TeamsUpgradePolicy. To be upgraded to TeamsOnly mode, users must be either homed in Skype for Business Online or have no Skype account anywhere. - - The NotifySfBUsers setting of Office 365 TeamsUpgradePolicy is not honored by users homed on-premises. Instead, the on-premises version of TeamsUpgradePolicy must be used. -- In Office 365, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet available. In contrast, Skype for Business Server does not contain built-in instances, so the New cmdlet is available on-premises. Only NotifySfBUsers property is available in on-premises. -- When granting a user a policy with mode=TeamsOnly or mode=SfBWithTeamsCollabAndMeetings, by default, meetings organized by that user will be migrated to Teams. For details, see [Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms). -**IMPORTANT** -When users are in any of the Skype for Business modes (SfBOnly, SfBWithTeamsCollab, SfBWithTeamsCollabAndMeetings), calling and chat functionality in the Teams app are disabled (but chat in the context of a Teams meeting is still allowed). Similarly, when users are in the SfBOnly or SfBWithTeamsCollab modes, meeting scheduling is disabled. For more details, see [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype). +>[!IMPORTANT] +>TeamsUpgradePolicy can be assigned to any Teams user, whether that user have an on-premises account in Skype for Business Server or not. However, **TeamsOnly mode can only be assigned to a user who is already homed in Skype for Business Online**. This is because interop with Skype for Business users and federation as well as Microsoft 365 Phone System functionality are only possible if the user is homed in Skype for Business Online. In addition, you cannot assign TeamsOnly mode as the tenant-wide default if you have any Skype for Business on-premises deployment (which is detected by presence of a lyncdiscover DNS record that points to a location other than Office 365. To make these users TeamsOnly you must first move these users individually to the cloud using `Move-CsUser`. Once all users have been moved to the cloud, you can [disable hybrid to complete migration to the cloud](https://learn.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid) and then apply TeamsOnly mode at the tenant level to ensure future users are TeamsOnly by default. + + +> [!NOTE] +> - TeamsUpgradePolicy is available in both Office 365 and in on-premises versions of Skype for Business Server, but there are differences: +> +> - In Office 365, admins can specify both coexistence mode and whether to trigger notifications of pending upgrade. +> +> - In on-premises with Skype for Business Server, the only available option is to trigger notifications. Skype for Business Server 2015 with CU8 or Skype for Business Server 2019 are required. +> +> - TeamsUpgradePolicy in Office 365 can be granted to users homed on-premises in hybrid deployments of Skype for Business as follows: +> +> - Coexistence mode is honored by users homed on-premises, however on-premises users cannot be granted the UpgradeToTeams instance (mode=TeamsOnly) of TeamsUpgradePolicy. To be upgraded to TeamsOnly mode, users must be either homed in Skype for Business Online or have no Skype account anywhere. +> +> - The NotifySfBUsers setting of Office 365 TeamsUpgradePolicy is not honored by users homed on-premises. Instead, the on-premises version of TeamsUpgradePolicy must be used. +> +> - In Office 365, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet available. In contrast, Skype for Business Server does not contain built-in instances, so the New cmdlet is available on-premises. Only NotifySfBUsers property is available in on-premises. +> +> - When granting a user a policy with mode=TeamsOnly or mode=SfBWithTeamsCollabAndMeetings, by default, meetings organized by that user will be migrated to Teams. For details, see [Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms). + + +When users are in any of the Skype for Business modes (SfBOnly, SfBWithTeamsCollab, SfBWithTeamsCollabAndMeetings), calling and chat functionality in the Teams app are disabled (but chat in the context of a Teams meeting is still allowed). Similarly, when users are in the SfBOnly or SfBWithTeamsCollab modes, meeting scheduling is disabled. For more details, see [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype). The `Grant-CsTeamsUpgradePolicy` cmdlet checks the configuration of the corresponding settings in TeamsMessagingPolicy, TeamsCallingPolicy, and TeamsMeetingPolicy to determine if those settings would be superceded by TeamsUpgradePolicy and if so, an informational message is provided in PowerShell. It is not necessary to set these other policy settings. This is for informational purposes only. Below is an example of what the PowerShell warning looks like: @@ -60,70 +91,87 @@ The `Grant-CsTeamsUpgradePolicy` cmdlet checks the configuration of the correspo `WARNING: The user 'user1@contoso.com' currently has enabled values for: AllowUserChat, AllowPrivateCalling, AllowPrivateMeetingScheduling, AllowChannelMeetingScheduling, however these values will be ignored. This is because you are granting this user TeamsUpgradePolicy with mode=SfBWithTeamsCollab, which causes the Teams client to behave as if they are disabled.` +> [!NOTE] +> These warning messages are not affected by the -WarningAction parameter. + ## EXAMPLES ### Example 1: Grant Policy to an individual user -``` + +```powershell PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity mike@contoso.com ``` The above cmdlet assigns the "UpgradeToTeams" policy to user Mike@contoso.com. This effectively upgrades the user to Teams only mode. This command will only succeed if the user does not have an on-premises Skype for Business account. ### Example 2: Remove Policy for an individual user -``` + +```powershell PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName $null -Identity mike@contoso.com ``` The above cmdlet removes any policy changes made to user Mike@contoso.com and effectively Inherits the global tenant setting for teams Upgrade. ### Example 3: Grant Policy to the entire tenant -``` + +```powershell PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly -Global ``` -To grant a policy to all users in the org (except any that have an explicit policy assigned), omit the identity parameter. If you do not specify the -Global paramter, you will be prompted to confirm the operation. +To grant a policy to all users in the org (except any that have an explicit policy assigned), omit the identity parameter. If you do not specify the -Global parameter, you will be prompted to confirm the operation. ### Example 4 Get a report on existing TeamsUpgradePolicy users (Screen Report) + You can get the output on the screen, on CSV or Html format. For Screen Report -``` + +```powershell Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* ``` ### Example 5 Get a report on existing TeamsUpgradePolicy users (CSV Report) -``` + +```powershell $objUsers = Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* $objusers | ConvertTo-Csv -NoTypeInformation | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.csv" ``` + This will create a CSV file on the Desktop of the current user with the name "TeamsUpgrade.csv" ### Example 6 Get a report on existing TeamsUpgradePolicy users (HTML Report) -``` + +```powershell $objUsers = Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* $objusers | ConvertTo-Html | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.html" ``` + After running these lines will create an HTML file on the Desktop of the current user with the name "TeamUpgrade.html" ### Example 7 Get a report on existing TeamsUpgradePolicy users (CSV Report - Oneliner version) -``` + +```powershell Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* | ConvertTo-Csv -NoTypeInformation | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.csv" ``` -This will create a CSV file on the Desktop of the current user with the name "TeasUpgrade.csv" + +This will create a CSV file on the Desktop of the current user with the name "TeamsUpgrade.csv" ### Example 8 Get a report on existing TeamsUpgradePolicy users (HTML Report - Oneliner Version) -``` + +```powershell Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* | ConvertTo-Html | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.html" ``` + After running these lines will create an HTML file on the Desktop of the current user with the name "TeamUpgrade.html" ## PARAMETERS ### -Identity + The user you want to grant policy to. This can be specified as SIP address, UserPrincipalName, or ObjectId. ```yaml Type: UserIdParameter -Parameter Sets: (All) +Parameter Sets: Identity Aliases: Applicable: Skype for Business Online, Skype for Business Server 2019, Skype for Business Server 2015 @@ -135,6 +183,7 @@ Accept wildcard characters: False ``` ### -PolicyName + The name of the policy instance. ```yaml @@ -151,6 +200,7 @@ Accept wildcard characters: False ``` ### -Global + Use this switch if you want to grant the specified policy to be the default policy for all users in the tenant. ```yaml @@ -166,16 +216,79 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MigrateMeetingsToTeams -Specifies whether to move existing Skype for Business meetings organized by the user to Teams. This parameter can only be true if the mode of the specified policy instance is either TeamsOnly or SfBWithTeamsCollabAndMeetings, and if the policy instance is being granted to a specific user. It is not possible to trigger meeting migration when granting TeamsUpgradePolicy to the entire tenant. For more details, see [Using the meeting migration service](https://docs.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms). +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Skype for Business Online, Skype for Business Server 2019, Skype for Business Server 2015 +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -Tenant + +Do not use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrateMeetingsToTeams +Not supported anymore, see the Description section. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online Required: False Position: Named @@ -184,14 +297,15 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Confirm -Prompts you for confirmation before running the cmdlet. +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the Teams call hold policy. + +By default, the cmdlet does not pass objects through the pipeline. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online, Skype for Business Server 2019, Skype for Business Server 2015 +Aliases: Required: False Position: Named @@ -200,14 +314,29 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Tenant -Do not use. +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. ```yaml -Type: Object +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: wi Required: False Position: Named @@ -216,6 +345,7 @@ Accept pipeline input: False Accept wildcard characters: False ``` + ## INPUTS ### Microsoft.Rtc.Management.AD.UserIdParameter @@ -227,11 +357,11 @@ Accept wildcard characters: False ## RELATED LINKS -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) -[Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms) +[Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms) -[Coexistence with Skype for Business](https://docs.microsoft.com/microsoftteams/coexistence-chat-calls-presence) +[Coexistence with Skype for Business](https://learn.microsoft.com/microsoftteams/coexistence-chat-calls-presence) [Get-CsTeamsUpgradeConfiguration](Get-CsTeamsUpgradeConfiguration.md) diff --git a/skype/skype-ps/skype/Grant-CsTeamsVideoInteropServicePolicy.md b/skype/skype-ps/skype/Grant-CsTeamsVideoInteropServicePolicy.md deleted file mode 100644 index 9a152f56d7..0000000000 --- a/skype/skype-ps/skype/Grant-CsTeamsVideoInteropServicePolicy.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamsvideointeropservicepolicy -applicable: Skype for Business Online -Module Name: Skype for Business Online -title: Grant-CsTeamsVideoInteropServicePolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsTeamsVideoInteropServicePolicy - -## SYNOPSIS - -Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. You can use the TeamsVideoInteropServicePolicy cmdlets to enable Cloud Video Interop for particular users or for your entire organization. - -## SYNTAX - -### Identity (Default) -``` -Grant-CsTeamsVideoInteropServicePolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> - [-Tenant <System.Guid>] [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### GrantToTenant -``` -Grant-CsTeamsVideoInteropServicePolicy [-PolicyName] <String> [-Tenant <System.Guid>] - [-DomainController <Fqdn>] [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. You can use the TeamsVideoInteropServicePolicy cmdlets to enable Cloud Video Interop for particular users or for your entire organization. Microsoft provides pre-constructed policies for each of our supported partners that allow you to designate which of the partners to use for cloud video interop. - -The Grant-CsTeamsVideoInteropServicePolicy cmdlet allows you to assign a pre-constructed policy across your whole organization or only to specific users. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Grant-CsTeamsVideoInteropServicePolicy -PolicyName ServiceProviderDisabled -``` - -In this example, Cloud Video Interop has been disabled for the entire tenant, except for those users that have an explicit policy assigned to them. - -### Example 2 -```powershell -PS C:\> Grant-CsTeamsVideoInteropServicePolicy -PolicyName ServiceProviderDisabled -Identity bob@contoso.com -``` - -In this example, Cloud Video Interop has been disabled only for one user - Bob - but the default tenant policy has been left on for all other users who do not have an explicit assignment. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Internal Microsoft use only. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Global -Use this flag to override the warning when assigning the global policy for your tenant. - -```yaml -Type: SwitchParameter -Parameter Sets: GrantToTenant -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -{{Fill Identity Description}} - -```yaml -Type: UserIdParameter -Parameter Sets: Identity -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -PassThru -Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsVideoInteropServicePolicy cmdlet does not pass objects through the pipeline. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -Specify the pre-constructed policy that you would like to assign to your tenant or a particular user. You can get the policies available for your organization using the cmdlet Get-CsTeamsVideoInteropServicePolicy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.AD.UserIdParameter - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Grant-CsTenantDialPlan.md b/skype/skype-ps/skype/Grant-CsTenantDialPlan.md deleted file mode 100644 index c4a6060e28..0000000000 --- a/skype/skype-ps/skype/Grant-CsTenantDialPlan.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cstenantdialplan -applicable: Skype for Business Online -title: Grant-CsTenantDialPlan -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Grant-CsTenantDialPlan - -## SYNOPSIS -Use the Grant-DsTenantDialPlan cmdlet to assign an existing tenant dial plan to a user. - -## SYNTAX - -``` -Grant-CsTenantDialPlan [-PolicyName] <String> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The Grant-CsTenantDialPlan cmdlet assigns an existing tenant dial plan to a user. -Tenant dial plans provide information that is required for Enterprise Voice users to make telephone calls. -Users who do not have a valid tenant dial plan cannot make calls by using Enterprise Voice. -A tenant dial plan determines such things as how normalization rules are applied, and whether a prefix must be dialed for external calls. - -You can check whether a user has been granted a per-user tenant dial plan by calling a command in this format: `Get-CsOnlineUser "<user name>" | Select-Object TenantDialPlan.` -## EXAMPLES - -### -------------------------- Example 1 -------------------------- - -(Skype for Business Online) -``` -Grant-CsTenantDialPlan -PolicyName Vt1tenantDialPlan9 -Identity (Get-CsOnlineUser Vt1_User1).SipAddress -``` - -This example grants the Vt1tenantDialPlan9 dial plan to Vt1_User1. - -### -------------------------- Example 2 -------------------------- -``` -Grant-CsTenantDialPlan -Identity "Ken Myer" -PolicyName $Null -``` - -In Example 2, any dial plan previously assigned to the user Ken Myer is unassigned from that user; as a result, Ken Myer will be managed by the global dial plan. -To unassign a custom tenant dial plan, set the PolicyName to a null value ($Null). - - - -## PARAMETERS - -### -Identity -The Identity parameter identifies the user to whom the policy should be assigned. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The PolicyName parameter is the name of the tenant dial plan to assign to the specified user. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Specifies the domain controller that's used by the cmdlet to read or write the specified data. -Valid inputs for this parameter are either the fully qualified domain name (FQDN) or the computer name. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PassThru - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308".` -You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Grant-CsThirdPartyVideoSystemPolicy.md b/skype/skype-ps/skype/Grant-CsThirdPartyVideoSystemPolicy.md index 8cef5a871f..c5066205d9 100644 --- a/skype/skype-ps/skype/Grant-CsThirdPartyVideoSystemPolicy.md +++ b/skype/skype-ps/skype/Grant-CsThirdPartyVideoSystemPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csthirdpartyvideosystempolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-csthirdpartyvideosystempolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsThirdPartyVideoSystemPolicy schema: 2.0.0 @@ -205,4 +205,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsThirdPartyVideoSystemPolicy](Remove-CsThirdPartyVideoSystemPolicy.md) [Set-CsThirdPartyVideoSystemPolicy](Set-CsThirdPartyVideoSystemPolicy.md) - diff --git a/skype/skype-ps/skype/Grant-CsUserServicesPolicy.md b/skype/skype-ps/skype/Grant-CsUserServicesPolicy.md index d132f0b07a..cbb4c917da 100644 --- a/skype/skype-ps/skype/Grant-CsUserServicesPolicy.md +++ b/skype/skype-ps/skype/Grant-CsUserServicesPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csuserservicespolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-csuserservicespolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsUserServicesPolicy schema: 2.0.0 @@ -216,4 +216,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsUserServicesPolicy](Remove-CsUserServicesPolicy.md) [Set-CsUserServicesPolicy](Set-CsUserServicesPolicy.md) - diff --git a/skype/skype-ps/skype/Grant-CsVoicePolicy.md b/skype/skype-ps/skype/Grant-CsVoicePolicy.md index d4095dde82..f553602f84 100644 --- a/skype/skype-ps/skype/Grant-CsVoicePolicy.md +++ b/skype/skype-ps/skype/Grant-CsVoicePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csvoicepolicy +online version: https://learn.microsoft.com/powershell/module/skype/grant-csvoicepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsVoicePolicy schema: 2.0.0 @@ -200,26 +200,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` @@ -249,6 +229,3 @@ When used with the PassThru parameter, returns an object of type Microsoft.Rtc.M [Test-CsVoicePolicy](Test-CsVoicePolicy.md) [Get-CsUser](Get-CsUser.md) - -[Get-CsOnlineUser](Get-CsOnlineUser.md) - diff --git a/skype/skype-ps/skype/Grant-CsVoiceRoutingPolicy.md b/skype/skype-ps/skype/Grant-CsVoiceRoutingPolicy.md index 656d7f8cb1..741af07a2c 100644 --- a/skype/skype-ps/skype/Grant-CsVoiceRoutingPolicy.md +++ b/skype/skype-ps/skype/Grant-CsVoiceRoutingPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csvoiceroutingpolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/grant-csvoiceroutingpolicy +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Grant-CsVoiceRoutingPolicy schema: 2.0.0 manager: bulenteg @@ -16,7 +16,7 @@ ms.reviewer: rogupta Assigns a per-user voice routing policy to one or more users. Voice routing policies manage PSTN usages for users of hybrid voice. -Hybrid voice enables users homed on Skype for Business Online to take advantage of the Enterprise Voice capabilities available in an on-premises installation of Skype for Business Server. +Hybrid voice enables users homed on Microsoft Teams or Skype for Business Online to take advantage of the Enterprise Voice capabilities available in an on-premises installation of Skype for Business Server. This cmdlet was introduced in Lync Server 2013. @@ -83,7 +83,7 @@ For example, the Identity "\* Smith" returns all the users who have a display na Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: True Position: 1 @@ -99,7 +99,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -116,7 +116,7 @@ To connect to a particular domain controller, include the DomainController param Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -133,7 +133,7 @@ By default, the Grant-CsVoiceRoutingPolicy cmdlet does not pass objects through Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -153,7 +153,7 @@ To unassign a per-user policy previously assigned to a user, set the PolicyName Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 2 @@ -169,7 +169,7 @@ The WhatIf switch causes the command to simulate its results. By using this swit Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Microsoft Teams, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -185,27 +185,6 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online Required: False Position: Named @@ -241,4 +220,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsVoiceRoutingPolicy](Remove-CsVoiceRoutingPolicy.md) [Set-CsVoiceRoutingPolicy](Set-CsVoiceRoutingPolicy.md) - diff --git a/skype/skype-ps/skype/Import-CSAnnouncementFile.md b/skype/skype-ps/skype/Import-CSAnnouncementFile.md index 9c14f30049..37882297f1 100644 --- a/skype/skype-ps/skype/Import-CSAnnouncementFile.md +++ b/skype/skype-ps/skype/Import-CSAnnouncementFile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csannouncementfile +online version: https://learn.microsoft.com/powershell/module/skype/import-csannouncementfile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CSAnnouncementFile schema: 2.0.0 @@ -17,8 +17,6 @@ ms.reviewer: Imports an announcement file to the Announcement service audio library. This cmdlet was introduced in Lync Server 2010. - - ## SYNTAX ``` @@ -37,24 +35,18 @@ At that point the New-CsUnassignedNumber or Set-CsUnassignedNumber cmdlet can be Imported files must be WAV or WMA files. - - ## EXAMPLES ### -------------------------- EXAMPLE 1 -------------------------- ``` -$a = Get-Content ".\GreetingFile.wav" -ReadCount 0 -Encoding Byte +$a = [System.IO.File]::ReadAllBytes('.\GreetingFile.wav') Import-CsAnnouncementFile -Parent ApplicationServer:redmond.litwareinc.com -FileName "WelcomeMessage.wav" -Content $a ``` These commands import an audio file into the Announcement service File Store. -Because audio files must be imported as byte arrays, we first need to call the Get-Content cmdlet to retrieve the audio file as an array of individual bytes. -Get-Content is a Windows PowerShell built-in cmdlet to which we pass the name (including path) of the file we want to use for our announcement. -Next we pass a value of 0 to the ReadCount parameter, meaning we want to read the whole file at once. -We then pass a value of Byte to the Encoding parameter, which tells Get-Content that we want the contents of the file as an array of bytes. -We assign that array to the variable $a. +Because audio files must be imported as byte arrays, we first need to retrieve the audio file as an array of individual bytes. We assign that array to the variable $a. In the second line we call the Import-CsAnnouncementFile cmdlet to actually import the file. We pass the service Identity ApplicationServer:redmond.litwareinc.com to the Parent parameter, then we pass a name to the FileName parameter (WelcomeMessage.wav). @@ -64,23 +56,21 @@ Finally, we pass the variable $a as the value to the Content parameter to read i ### -------------------------- EXAMPLE 2 -------------------------- ``` -Import-CsAnnouncementFile -Parent ApplicationServer:redmond.litwareinc.com -FileName "WelcomeMessage.wav" -Content (Get-Content ".\GreetingFile.wav" -ReadCount 0 -Encoding Byte) +Import-CsAnnouncementFile -Parent ApplicationServer:redmond.litwareinc.com -FileName "WelcomeMessage.wav" -Content ([System.IO.File]::ReadAllBytes('.\GreetingFile.wav')) ``` -Example 2 is identical to Example 1 except that we included the Get-Content command inside parentheses as a value to the Content parameter rather than calling that command on its own and assigning it to a variable. - +Example 2 is identical to Example 1 except that we included the command inside parentheses as a value to the Content parameter rather than calling that command on its own and assigning it to a variable. ### -------------------------- EXAMPLE 3 -------------------------- ``` -Get-Content ".\GreetingFile.wav" -ReadCount 0 -Encoding Byte | Import-CsAnnouncementFile -Parent ApplicationServer:redmond.litwareinc.com -FileName "WelcomeMessage.wav" +[System.IO.File]::ReadAllBytes('.\GreetingFile.wav') | Import-CsAnnouncementFile -Parent ApplicationServer:redmond.litwareinc.com -FileName "WelcomeMessage.wav" ``` Example 3 is yet another variation of Example 1. -The difference in this example is that rather than use the Content parameter, we first call the Get-Content cmdlet, then pipe the results to Import-CsAnnouncementFile. +The difference in this example is that rather than use the Content parameter, we first call the command to read the file, then pipe the results to Import-CsAnnouncementFile. This is the most reliable way of importing an announcement file from a remote session. - ## PARAMETERS ### -Parent @@ -119,6 +109,8 @@ Accept wildcard characters: False ### -Content The contents of the audio file as a byte array. +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). + ```yaml Type: Byte[] Parameter Sets: (All) @@ -199,4 +191,3 @@ This cmdlet does not return a value. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Import-CsCertificate.md b/skype/skype-ps/skype/Import-CsCertificate.md index 0555912132..ba39973617 100644 --- a/skype/skype-ps/skype/Import-CsCertificate.md +++ b/skype/skype-ps/skype/Import-CsCertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-cscertificate +online version: https://learn.microsoft.com/powershell/module/skype/import-cscertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsCertificate schema: 2.0.0 @@ -324,4 +324,3 @@ None. [Request-CsCertificate](Request-CsCertificate.md) [Set-CsCertificate](Set-CsCertificate.md) - diff --git a/skype/skype-ps/skype/Import-CsCompanyPhoneNormalizationRules.md b/skype/skype-ps/skype/Import-CsCompanyPhoneNormalizationRules.md index 950cf898f3..68beb13982 100644 --- a/skype/skype-ps/skype/Import-CsCompanyPhoneNormalizationRules.md +++ b/skype/skype-ps/skype/Import-CsCompanyPhoneNormalizationRules.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-cscompanyphonenormalizationrules +online version: https://learn.microsoft.com/powershell/module/skype/import-cscompanyphonenormalizationrules applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsCompanyPhoneNormalizationRules schema: 2.0.0 @@ -190,5 +190,3 @@ None [New-CsAddressBookNormalizationConfiguration](New-CsAddressBookNormalizationConfiguration.md) [Get-CsAddressBookNormalizationConfiguration](Get-CsAddressBookNormalizationConfiguration.md) - - diff --git a/skype/skype-ps/skype/Import-CsConfiguration.md b/skype/skype-ps/skype/Import-CsConfiguration.md index cc6f0a17c4..6f8f568b9c 100644 --- a/skype/skype-ps/skype/Import-CsConfiguration.md +++ b/skype/skype-ps/skype/Import-CsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/import-csconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsConfiguration schema: 2.0.0 @@ -185,5 +185,3 @@ The Import-CsConfiguration cmdlet does not return any values or objects. ## RELATED LINKS [Export-CsConfiguration](Export-CsConfiguration.md) - - diff --git a/skype/skype-ps/skype/Import-CsDeviceUpdate.md b/skype/skype-ps/skype/Import-CsDeviceUpdate.md index d0e459f353..a5c01e0bfd 100644 --- a/skype/skype-ps/skype/Import-CsDeviceUpdate.md +++ b/skype/skype-ps/skype/Import-CsDeviceUpdate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csdeviceupdate +online version: https://learn.microsoft.com/powershell/module/skype/import-csdeviceupdate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsDeviceUpdate schema: 2.0.0 @@ -189,5 +189,3 @@ The Import-CsDeviceUpdate cmdlet imports instances of the Microsoft.Rtc.Manageme ## RELATED LINKS [Get-CsDeviceUpdateRule](Get-CsDeviceUpdateRule.md) - - diff --git a/skype/skype-ps/skype/Import-CsLegacyConferenceDirectory.md b/skype/skype-ps/skype/Import-CsLegacyConferenceDirectory.md index 72e2c374c1..aa6269159b 100644 --- a/skype/skype-ps/skype/Import-CsLegacyConferenceDirectory.md +++ b/skype/skype-ps/skype/Import-CsLegacyConferenceDirectory.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-cslegacyconferencedirectory +online version: https://learn.microsoft.com/powershell/module/skype/import-cslegacyconferencedirectory applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsLegacyConferenceDirectory schema: 2.0.0 @@ -143,5 +143,3 @@ The Import-CsLegacyConferenceDirectory cmdlet does not return any objects or val [Merge-CsLegacyTopology](Merge-CsLegacyTopology.md) [Move-CsLegacyUser](Move-CsLegacyUser.md) - - diff --git a/skype/skype-ps/skype/Import-CsLegacyConfiguration.md b/skype/skype-ps/skype/Import-CsLegacyConfiguration.md index 7719c9bb6c..51ac1f67d2 100644 --- a/skype/skype-ps/skype/Import-CsLegacyConfiguration.md +++ b/skype/skype-ps/skype/Import-CsLegacyConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-cslegacyconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/import-cslegacyconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsLegacyConfiguration schema: 2.0.0 @@ -187,5 +187,3 @@ The Import-CsLegacyConfiguration cmdlet does not return any objects or values. [Merge-CsLegacyTopology](Merge-CsLegacyTopology.md) [Move-CsLegacyUser](Move-CsLegacyUser.md) - - diff --git a/skype/skype-ps/skype/Import-CsLisConfiguration.md b/skype/skype-ps/skype/Import-CsLisConfiguration.md index 0d44c5af60..20298f3573 100644 --- a/skype/skype-ps/skype/Import-CsLisConfiguration.md +++ b/skype/skype-ps/skype/Import-CsLisConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-cslisconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/import-cslisconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsLisConfiguration schema: 2.0.0 @@ -17,8 +17,6 @@ ms.reviewer: Imports an Enterprise Voice Enhanced 9-1-1 (E9-1-1) configuration from a backup file. This cmdlet was introduced in Lync Server 2010. - - ## SYNTAX ### ByteInput @@ -48,11 +46,8 @@ You call the Export-CsLisConfiguration cmdlet to back up your configuration. Later, you modify the Location property of that wireless access point to Building30/Rooms20-40. If you then call the Import-CsLisConfiguration cmdlet to restore the backed-up configuration, the location for that WAP will be Building30/Room10 (the location before the backup), but the location for Building30/Rooms20-40 will remain in the location configuration database. - - ## EXAMPLES - ### -------------------------- EXAMPLE 1 -------------------------- ``` @@ -61,7 +56,6 @@ Import-CsLisConfiguration -FileName C:\E911Config.bak This example imports the E9-1-1 configuration from the backup file named E911Config.back to the location configuration database. - ### -------------------------- EXAMPLE 2 -------------------------- ``` @@ -78,34 +72,25 @@ In line 2 the Import-CsLisConfiguration cmdlet is called. The ByteInput parameter receives a value of $lisconfig, which is the variable containing the byte array we exported. This will import that byte array back into the location configuration database. - - ### -------------------------- EXAMPLE 3 -------------------------- ``` $lisconfig = Export-CsLisConfiguration -AsBytes -$listconfig | Set-Content -Path C:\E911Config.bak -Encoding byte +[System.IO.File]::WriteAllBytes('C:\E911Config.bak', $lisconfig) -Get-Content -ReadCount 0 -Encoding byte -Path C:\E911Config.bak | Import-CsLisConfiguration +[System.IO.File]::ReadAllBytes('C:\E911Config.bak') | Import-CsLisConfiguration ``` Example 3 is a more complete version of Example 2. The first line is the same, we call the Export-CsLisConfiguration cmdlet with the AsBytes parameter to store the LIS configuration as an array of bytes in the variable $lisconfig. The rest of this example shows how to save that configuration to a file and then import it back into the location configuration database. -In line 2 we pipe the contents of $lisconfig, which is the byte array representing the LIS configuration, to the Windows PowerShell Set-Content cmdlet. -We assign values to two parameters of the Set-Content cmdlet: Path and Encoding. -We assign the full path and file name of the file to which we want to save the configuration to the Path parameter. -We use the Encoding parameter with a value of byte to ensure the configuration is stored as an array of bytes. +In line 2 we pipe the contents of $lisconfig, which is the byte array representing the LIS configuration, to the full path and file name of the file to which we want to save the configuration. Finally, in line 3 we import the configuration back into the location configuration database. -First we call the Get-Content cmdlet to retrieve the contents from the file. -We pass a value of 0 to the ReadCount property, which tells the Get-Content cmdlet to read all the contents of the file at once rather than one line at a time. -We again use the Encoding parameter with a value of byte to specify what type of data we're reading from the file. -Finally we pass the file name to the Path parameter. -The contents of the file that we read with the Get-Content cmdlet is piped to the Import-CsLisConfiguration cmdlet, which imports the saved configuration into the location configuration database. - +First we retrieve the contents from the file. +The contents of the file are then piped to the Import-CsLisConfiguration cmdlet, which imports the saved configuration into the location database. ## PARAMETERS @@ -172,4 +157,3 @@ This cmdlet does not return a value. [Debug-CsLisConfiguration](Debug-CsLisConfiguration.md) [Test-CsLisConfiguration](Test-CsLisConfiguration.md) - diff --git a/skype/skype-ps/skype/Import-CsOnlineAudioFile.md b/skype/skype-ps/skype/Import-CsOnlineAudioFile.md deleted file mode 100644 index 8ea01b4b4d..0000000000 --- a/skype/skype-ps/skype/Import-CsOnlineAudioFile.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csonlineaudiofile -applicable: Skype for Business Online -title: Import-CsOnlineAudioFile -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Import-CsOnlineAudioFile - -## SYNOPSIS -Use the Import-CsOnlineAudioFile cmdlet to upload a new audio file. - -## SYNTAX - -```powershell -Import-CsOnlineAudioFile -ApplicationId <OrgAutoAttendant | HuntGroup> -FileName <string> -Content <byte[]> -``` - -## DESCRIPTION -The Import-CsOnlineAudioFile cmdlet uploads a new audio file for use with the Auto Attendant (AA) or Call Queue (CQ) service. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -$content = Get-Content "C:\Media\Welcome.wav" -Encoding byte -ReadCount 0 -$audioFile = Import-CsOnlineAudioFile -ApplicationId "OrgAutoAttendant" -FileName "Hello.wav" -Content $content -``` - -This example creates a new audio file using the WAV content that has a filename of Hello.wav to be used with organizational auto attendants. - -## PARAMETERS - -### -ApplicationId -The ApplicationId parameter is the identifier for the application which will use this audio file. For example, if the audio file will be used with an organizational auto attendant, then it needs to be set to "OrgAutoAttendant". If the audio file will be used with a hunt group (call queue), then it needs to be set to "HuntGroup". - -Supported values: - -- OrgAutoAttendant -- HuntGroup - -```yaml -Type: System.string -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FileName -The FileName parameter is the name of the audio file. For example, the file name for the file C:\Media\Welcome.wav is Welcome.wav. - -```yaml -Type: System.string -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Content -The Content parameter represents the content of the audio file. Supported formats are WAV (uncompressed, linear PCM with 8/16/32-bit depth in mono or stereo), WMA (mono only), and MP3. The audio file content cannot be more 5MB. - -```yaml -Type: System.Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.AudioFile - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Import-CsOrganizationalAutoAttendantHolidays.md b/skype/skype-ps/skype/Import-CsOrganizationalAutoAttendantHolidays.md deleted file mode 100644 index 51635c5402..0000000000 --- a/skype/skype-ps/skype/Import-CsOrganizationalAutoAttendantHolidays.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csorganizationalautoattendantholidays -applicable: Skype for Business Online -title: Import-CsOrganizationalAutoAttendantHolidays -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Import-CsOrganizationalAutoAttendantHolidays - -## SYNOPSIS -Use Import-CsOrganizationalAutoAttendantHolidays cmdlet to import holiday schedules of an existing Auto Attendant (AA) that were previously exported using the Export-CsOrganizationalAutoAttendantHolidays cmdlet. - -## SYNTAX - -``` -Import-CsOrganizationalAutoAttendantHolidays [-PrimaryUri] <Uri> -Input <byte[]> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Export-CsOrganizationalAutoAttendantHolidays cmdlet and the Import-CsOrganizationalAutoAttendantHolidays cmdlet enable you to export holiday schedules in your auto attendant and then later import that information. This can be extremely useful in a situation where you need to configure same holiday sets in multiple auto attendants. - -The Export-CsOrganizationalAutoAttendantHolidays cmdlet returns the holiday schedule information in serialized form (as a byte array). The caller can then write the bytes to the disk to obtain a CSV file. Similarly, the Import-CsOrganizationalAutoAttendantHolidays cmdlet accepts the holiday schedule information as a byte array, which can be read from the aforementioned CSV file. The first line of the CSV file is considered a header record and is always ignored. - -**NOTE** -- Each line in the CSV file used by Export-CsOrganizationalAutoAttendantHolidays and Import-CsOrganizationalAutoAttendantHolidays cmdlet should be of the following format: - - `HolidayName,StartDateTime1,EndDateTime1,StartDateTime2,EndDateTime2,...,StartDateTime10,EndDateTime10` - - where - - HolidayName is the name of the holiday to be imported. - - StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet. - - EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date. -- The first line of the CSV file is considered a header record and is always ignored by Import-CsOrganizationalAutoAttendantHolidays cmdlet. -- If the destination auto attendant for the import already contains a call flow or schedule by the same name as one of the holidays being imported, the corresponding CSV record is skipped. -- For holidays that are successfully imported, a default call flow is created which is configured without any greeting and simply disconnects the call on being executed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$bytes = [System.IO.File]::ReadAllBytes("C:\Imports\Holidays.csv") -Import-CsOrganizationalAutoAttendantHolidays -PrimaryUri sip:mainoaa@contoso.com -Input $bytes -``` - -In this example, the Import-CsOrganizationalAutoAttendantHolidays cmdlet is used to import holiday schedule information from a file at path "C:\Imports\Holidays.csv" to an auto attendant with Primary URI of sip:mainoaa@contoso.com. - -### -------------------------- Example 2 -------------------------- -``` -$bytes = [System.IO.File]::ReadAllBytes("C:\Imports\Holidays.csv") -Import-CsOrganizationalAutoAttendantHolidays -PrimaryUri sip:mainoaa@contoso.com -Input $bytes | Format-Table -Wrap -AutoSize -``` - -In this example, the Import-CsOrganizationalAutoAttendantHolidays cmdlet is used to import holiday schedule information from a file at path "C:\Imports\Holidays.csv" to an auto attendant with Primary URI of sip:mainoaa@contoso.com. The result of the import process is formatted as a table. - -## PARAMETERS - -### -PrimaryUri -The Primary URI represents the SIP address of the auto attendant in where the holiday schedule information is to be imported. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Input -The Input parameter specifies the holiday schedule information that is to be imported. - -```yaml -Type: System.Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### String -The String is used as the PrimaryUri input. - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.HolidayImportResult - - -## NOTES - - -## RELATED LINKS - -[Export-CsOrganizationalAutoAttendantHolidays](Export-CsOrganizationalAutoAttendantHolidays.md) - -[Get-CsOrganizationalAutoAttendantHolidays](Get-CsOrganizationalAutoAttendantHolidays.md) - diff --git a/skype/skype-ps/skype/Import-CsPersistentChatData.md b/skype/skype-ps/skype/Import-CsPersistentChatData.md index 01437cb309..a6407326d2 100644 --- a/skype/skype-ps/skype/Import-CsPersistentChatData.md +++ b/skype/skype-ps/skype/Import-CsPersistentChatData.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-cspersistentchatdata -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/import-cspersistentchatdata +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsPersistentChatData schema: 2.0.0 manager: rogupta @@ -189,5 +189,3 @@ None. ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/Import-CsRgsAudioFile.md b/skype/skype-ps/skype/Import-CsRgsAudioFile.md index 1eed5d8f54..2e14bd423a 100644 --- a/skype/skype-ps/skype/Import-CsRgsAudioFile.md +++ b/skype/skype-ps/skype/Import-CsRgsAudioFile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csrgsaudiofile +online version: https://learn.microsoft.com/powershell/module/skype/import-csrgsaudiofile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsRgsAudioFile schema: 2.0.0 @@ -17,8 +17,6 @@ ms.reviewer: Imports a new audio file for use with the Response Group application. This cmdlet was introduced in Lync Server 2010. - - ## SYNTAX ``` @@ -37,14 +35,12 @@ Note that you must run Import-CsRgsAudioFile each time you want to use an audio For example, suppose Workflow A uses a given audio file as its custom music on hold file and you now want to use that same audio file as the custom music on hold for Workflow B. Even though the audio file is already used by the Response Group application you will still need to import the file in order to use it with Workflow B. - - ## EXAMPLES ### -------------------------- EXAMPLE 1 -------------------------- ``` -$x = Import-CsRgsAudioFile -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -FileName "WhileYouWait.wav" -Content (Get-Content C:\Media\WhileYouWait.wav -Encoding byte -ReadCount 0) +$x = Import-CsRgsAudioFile -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -FileName "WhileYouWait.wav" -Content ([System.IO.File]::ReadAllBytes('C:\Media\WhileYouWait.wav')) $y = Get-CsRgsWorkflow -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -Name "Help Desk Workflow" @@ -58,16 +54,14 @@ To perform this task, the first command uses Import-CsRgsAudioFile to import the In addition to the Identity parameter (which specifies the service location) the FileName parameter is used to specify the file name of the file being imported. At the same time, the Content parameter is used to import the audio file. -File importing is carried out by calling the Get-Content cmdlet followed by the path to the file being imported. -Get-Content also requires you to set the encoding type to byte and the ReadCount to 0. -(Setting the ReadCount to 0 ensures that the entire file is read in a single operation.) The imported file is then stored in a variable named $x. +File importing is carried out by calling the `[System.IO.File]::ReadAllBytes` command with the path to the file being imported. +The imported file is then stored in a variable named $x. In the second command, Get-CsRgsWorkflow is used to create an object reference ($y) to the workflow Help Desk Workflow. After this object reference has been created, command 3 sets the value of the CustomMusicOnHoldFile property to $x, the variable containing the imported audio file. Finally, the last command in the example uses Set-CsRgsWorkflow to write these changes to the actual workflow Help Desk Workflow. If you do not call Set-CsRgsWorkflow, your modifications will exist only in memory, and will disappear as soon as you close Windows PowerShell or delete the variables $x or $y. - ## PARAMETERS ### -Identity @@ -89,8 +83,8 @@ Accept wildcard characters: False ### -Content Actual content of the audio file being imported. -The Content property is populated by calling the Get-Content cmdlet. -When calling Get-Content, set the Encoding parameter to byte and the ReadCount parameter to 0 (for details, see the Examples section in this topic). + +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). ```yaml Type: Byte[] @@ -191,5 +185,3 @@ Creates new instances of the Microsoft.Rtc.Rgs.Management.WritableSettings.Audio [New-CsRgsWorkflow](New-CsRgsWorkflow.md) [Set-CsRgsWorkflow](Set-CsRgsWorkflow.md) - - diff --git a/skype/skype-ps/skype/Import-CsRgsConfiguration.md b/skype/skype-ps/skype/Import-CsRgsConfiguration.md index 505c269d29..a18372286a 100644 --- a/skype/skype-ps/skype/Import-CsRgsConfiguration.md +++ b/skype/skype-ps/skype/Import-CsRgsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csrgsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/import-csrgsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsRgsConfiguration schema: 2.0.0 @@ -181,4 +181,3 @@ None. ## RELATED LINKS [Export-CsRgsConfiguration](Export-CsRgsConfiguration.md) - diff --git a/skype/skype-ps/skype/Import-CsUserData.md b/skype/skype-ps/skype/Import-CsUserData.md index e88742f8d8..d282e09e95 100644 --- a/skype/skype-ps/skype/Import-CsUserData.md +++ b/skype/skype-ps/skype/Import-CsUserData.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csuserdata +online version: https://learn.microsoft.com/powershell/module/skype/import-csuserdata applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Import-CsUserData schema: 2.0.0 @@ -260,5 +260,3 @@ None. [Sync-CsUserData](Sync-CsUserData.md) [Update-CsUserData](Update-CsUserData.md) - - diff --git a/skype/skype-ps/skype/Install-CsAdServerSchema.md b/skype/skype-ps/skype/Install-CsAdServerSchema.md index d31f156e3b..9a20d7aaef 100644 --- a/skype/skype-ps/skype/Install-CsAdServerSchema.md +++ b/skype/skype-ps/skype/Install-CsAdServerSchema.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/install-csadserverschema +online version: https://learn.microsoft.com/powershell/module/skype/install-csadserverschema applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Install-CsAdServerSchema schema: 2.0.0 @@ -226,5 +226,3 @@ The Install-CsAdServerSchema cmdlet does not return any values or objects. ## RELATED LINKS [Get-CsAdServerSchema](Get-CsAdServerSchema.md) - - diff --git a/skype/skype-ps/skype/Install-CsDatabase.md b/skype/skype-ps/skype/Install-CsDatabase.md index 8aea82ff56..cfa2fa1de6 100644 --- a/skype/skype-ps/skype/Install-CsDatabase.md +++ b/skype/skype-ps/skype/Install-CsDatabase.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/install-csdatabase +online version: https://learn.microsoft.com/powershell/module/skype/install-csdatabase applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Install-CsDatabase schema: 2.0.0 @@ -637,5 +637,3 @@ The Install-CsDatabase cmdlet does not return any values or objects. ## RELATED LINKS [Uninstall-CsDatabase](Uninstall-CsDatabase.md) - - diff --git a/skype/skype-ps/skype/Install-CsMirrorDatabase.md b/skype/skype-ps/skype/Install-CsMirrorDatabase.md index 1b351cadf2..feb4acc5d3 100644 --- a/skype/skype-ps/skype/Install-CsMirrorDatabase.md +++ b/skype/skype-ps/skype/Install-CsMirrorDatabase.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/install-csmirrordatabase +online version: https://learn.microsoft.com/powershell/module/skype/install-csmirrordatabase applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Install-CsMirrorDatabase schema: 2.0.0 @@ -361,4 +361,3 @@ None. [Get-CsDatabaseMirrorState](Get-CsDatabaseMirrorState.md) [Uninstall-CsMirrorDatabase](Uninstall-CsMirrorDatabase.md) - diff --git a/skype/skype-ps/skype/Invoke-CsArchivingDatabasePurge.md b/skype/skype-ps/skype/Invoke-CsArchivingDatabasePurge.md index f432d14e74..dbb310849d 100644 --- a/skype/skype-ps/skype/Invoke-CsArchivingDatabasePurge.md +++ b/skype/skype-ps/skype/Invoke-CsArchivingDatabasePurge.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csarchivingdatabasepurge +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csarchivingdatabasepurge applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsArchivingDatabasePurge schema: 2.0.0 @@ -278,4 +278,3 @@ The Invoke-CsArchivingDatabasePurge cmdlet returns instances of the Microsoft.Rt [New-CsArchivingConfiguration](New-CsArchivingConfiguration.md) [Set-CsArchivingConfiguration](Set-CsArchivingConfiguration.md) - diff --git a/skype/skype-ps/skype/Invoke-CsBackupServiceSync.md b/skype/skype-ps/skype/Invoke-CsBackupServiceSync.md index e2a9c0c2dd..4c9944e54e 100644 --- a/skype/skype-ps/skype/Invoke-CsBackupServiceSync.md +++ b/skype/skype-ps/skype/Invoke-CsBackupServiceSync.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csbackupservicesync +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csbackupservicesync applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsBackupServiceSync schema: 2.0.0 @@ -130,4 +130,3 @@ None. ## RELATED LINKS [Backup-CsPool](Backup-CsPool.md) - diff --git a/skype/skype-ps/skype/Invoke-CsCdrDatabasePurge.md b/skype/skype-ps/skype/Invoke-CsCdrDatabasePurge.md index c9921e5925..1aff964a92 100644 --- a/skype/skype-ps/skype/Invoke-CsCdrDatabasePurge.md +++ b/skype/skype-ps/skype/Invoke-CsCdrDatabasePurge.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-cscdrdatabasepurge +online version: https://learn.microsoft.com/powershell/module/skype/invoke-cscdrdatabasepurge applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsCdrDatabasePurge schema: 2.0.0 @@ -269,4 +269,3 @@ The Invoke-CsCdrDatabasePurge cmdlet returns instances of the Microsoft.Rtc.Mana [New-CsCdrConfiguration](New-CsCdrConfiguration.md) [Set-CsCdrConfiguration](Set-CsCdrConfiguration.md) - diff --git a/skype/skype-ps/skype/Invoke-CsComputerFailBack.md b/skype/skype-ps/skype/Invoke-CsComputerFailBack.md index de46ceda78..2700d5b25c 100644 --- a/skype/skype-ps/skype/Invoke-CsComputerFailBack.md +++ b/skype/skype-ps/skype/Invoke-CsComputerFailBack.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-cscomputerfailback +online version: https://learn.microsoft.com/powershell/module/skype/invoke-cscomputerfailback applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsComputerFailBack schema: 2.0.0 @@ -184,4 +184,3 @@ None. ## RELATED LINKS [Invoke-CsComputerFailOver](Invoke-CsComputerFailOver.md) - diff --git a/skype/skype-ps/skype/Invoke-CsComputerFailOver.md b/skype/skype-ps/skype/Invoke-CsComputerFailOver.md index 340ea429fd..723b08653b 100644 --- a/skype/skype-ps/skype/Invoke-CsComputerFailOver.md +++ b/skype/skype-ps/skype/Invoke-CsComputerFailOver.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-cscomputerfailover +online version: https://learn.microsoft.com/powershell/module/skype/invoke-cscomputerfailover applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsComputerFailOver schema: 2.0.0 @@ -225,4 +225,3 @@ None. ## RELATED LINKS [Invoke-CsComputerFailBack](Invoke-CsComputerFailBack.md) - diff --git a/skype/skype-ps/skype/Invoke-CsDatabaseFailover.md b/skype/skype-ps/skype/Invoke-CsDatabaseFailover.md index a0780694b8..95e2fcf516 100644 --- a/skype/skype-ps/skype/Invoke-CsDatabaseFailover.md +++ b/skype/skype-ps/skype/Invoke-CsDatabaseFailover.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csdatabasefailover +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csdatabasefailover applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsDatabaseFailover schema: 2.0.0 @@ -276,4 +276,3 @@ None. [Get-CsDatabaseMirrorState](Get-CsDatabaseMirrorState.md) [Install-CsMirrorDatabase](Install-CsMirrorDatabase.md) - diff --git a/skype/skype-ps/skype/Invoke-CsManagementServerFailover.md b/skype/skype-ps/skype/Invoke-CsManagementServerFailover.md index 502f7d20ea..342f852532 100644 --- a/skype/skype-ps/skype/Invoke-CsManagementServerFailover.md +++ b/skype/skype-ps/skype/Invoke-CsManagementServerFailover.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csmanagementserverfailover +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csmanagementserverfailover applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsManagementServerFailover schema: 2.0.0 @@ -250,4 +250,3 @@ None. ## RELATED LINKS [Invoke-CsDatabaseFailover](Invoke-CsDatabaseFailover.md) - diff --git a/skype/skype-ps/skype/Invoke-CsManagementStoreReplication.md b/skype/skype-ps/skype/Invoke-CsManagementStoreReplication.md index 2c495d4bed..c002ae71c5 100644 --- a/skype/skype-ps/skype/Invoke-CsManagementStoreReplication.md +++ b/skype/skype-ps/skype/Invoke-CsManagementStoreReplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csmanagementstorereplication +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csmanagementstorereplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsManagementStoreReplication schema: 2.0.0 @@ -125,5 +125,3 @@ The Invoke-CsManagementStoreReplication cmdlet does not return any objects. ## RELATED LINKS [Get-CsManagementStoreReplicationStatus](Get-CsManagementStoreReplicationStatus.md) - - diff --git a/skype/skype-ps/skype/Invoke-CsPoolFailBack.md b/skype/skype-ps/skype/Invoke-CsPoolFailBack.md index e24c6571f0..99b453decd 100644 --- a/skype/skype-ps/skype/Invoke-CsPoolFailBack.md +++ b/skype/skype-ps/skype/Invoke-CsPoolFailBack.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-cspoolfailback +online version: https://learn.microsoft.com/powershell/module/skype/invoke-cspoolfailback applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsPoolFailBack schema: 2.0.0 @@ -222,4 +222,3 @@ None. ## RELATED LINKS [Invoke-CsPoolFailOver](Invoke-CsPoolFailOver.md) - diff --git a/skype/skype-ps/skype/Invoke-CsPoolFailOver.md b/skype/skype-ps/skype/Invoke-CsPoolFailOver.md index 24ea224644..45d8e8e11f 100644 --- a/skype/skype-ps/skype/Invoke-CsPoolFailOver.md +++ b/skype/skype-ps/skype/Invoke-CsPoolFailOver.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-cspoolfailover +online version: https://learn.microsoft.com/powershell/module/skype/invoke-cspoolfailover applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsPoolFailOver schema: 2.0.0 @@ -112,7 +112,7 @@ When present, indicates that failover is being performed in "disaster mode." If If this parameter is not present that means that the pool is still up and running and that failover occurred by administrator choice; for example, the pool might temporarily be failed over in order to do hardware or software upgrades on the server. -Note: The parameteris required for an Enterprise pool if the backend SQL services are down but the front end servers are still up. +Note: The parameters required for an Enterprise pool if the backend SQL services are down but the front end servers are still up. @@ -264,4 +264,3 @@ None. ## RELATED LINKS [Invoke-CsPoolFailBack](Invoke-CsPoolFailBack.md) - diff --git a/skype/skype-ps/skype/Invoke-CsQoEDatabasePurge.md b/skype/skype-ps/skype/Invoke-CsQoEDatabasePurge.md index 4e2bab4bb8..573235dd3b 100644 --- a/skype/skype-ps/skype/Invoke-CsQoEDatabasePurge.md +++ b/skype/skype-ps/skype/Invoke-CsQoEDatabasePurge.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csqoedatabasepurge +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csqoedatabasepurge applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsQoEDatabasePurge schema: 2.0.0 @@ -237,4 +237,3 @@ The Invoke-CsQoEDatabasePurge cmdlet returns instances of the Microsoft.Rtc.Mana [New-CsQoEConfiguration](New-CsQoEConfiguration.md) [Set-CsQoEConfiguration](Set-CsQoEConfiguration.md) - diff --git a/skype/skype-ps/skype/Invoke-CsRgsStoreReplicateData.md b/skype/skype-ps/skype/Invoke-CsRgsStoreReplicateData.md index d6725eafb0..a62fee6b1d 100644 --- a/skype/skype-ps/skype/Invoke-CsRgsStoreReplicateData.md +++ b/skype/skype-ps/skype/Invoke-CsRgsStoreReplicateData.md @@ -1,8 +1,8 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csrgsstorereplicatedata +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csrgsstorereplicatedata applicable: Skype for Business Server 2019 -title: Invoke-CsRgsStoreReplicateData +title: Invoke-CsRGSStoreReplicateData schema: 2.0.0 manager: rogupta author: hirenshah1 @@ -18,7 +18,7 @@ Replicate existing RGS data present on the specified pool to the backup tables s ## SYNTAX ``` -Invoke-CsRgsStoreReplicateData -PoolFqdn <Fqdn> [-Force] [<CommonParameters>] +Invoke-CsRGSStoreReplicateData -PoolFqdn <Fqdn> [-Force] [<CommonParameters>] ``` ## DESCRIPTION diff --git a/skype/skype-ps/skype/Invoke-CsStorageServiceFlush.md b/skype/skype-ps/skype/Invoke-CsStorageServiceFlush.md index f15d74d3cc..90e2298abf 100644 --- a/skype/skype-ps/skype/Invoke-CsStorageServiceFlush.md +++ b/skype/skype-ps/skype/Invoke-CsStorageServiceFlush.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csstorageserviceflush +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csstorageserviceflush applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsStorageServiceFlush schema: 2.0.0 @@ -198,4 +198,3 @@ String value. ## RELATED LINKS [Invoke-CsPoolFailOver](Invoke-CsPoolFailOver.md) - diff --git a/skype/skype-ps/skype/Invoke-CsUcsRollback.md b/skype/skype-ps/skype/Invoke-CsUcsRollback.md index c8c6457a67..b0d139bbd3 100644 --- a/skype/skype-ps/skype/Invoke-CsUcsRollback.md +++ b/skype/skype-ps/skype/Invoke-CsUcsRollback.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/invoke-csucsrollback -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/invoke-csucsrollback +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Invoke-CsUcsRollback schema: 2.0.0 manager: bulenteg @@ -24,7 +24,7 @@ This cmdlet was introduced in Lync Server 2013. ``` Invoke-CsUcsRollback [-Identity] <UserIdParameter> [-Confirm] [-DomainController <Fqdn>] [-Force] [-PassThru] - [-WhatIf] [-AsJob] [<CommonParameters>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION @@ -203,22 +203,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` @@ -252,4 +236,3 @@ None. [Set-CsUserServicesPolicy](Set-CsUserServicesPolicy.md) [Test-CsUnifiedContactStore](Test-CsUnifiedContactStore.md) - diff --git a/skype/skype-ps/skype/Lock-CsClientPin.md b/skype/skype-ps/skype/Lock-CsClientPin.md index 24e0c3bf33..4e7c015374 100644 --- a/skype/skype-ps/skype/Lock-CsClientPin.md +++ b/skype/skype-ps/skype/Lock-CsClientPin.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/lock-csclientpin +online version: https://learn.microsoft.com/powershell/module/skype/lock-csclientpin applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Lock-CsClientPin schema: 2.0.0 @@ -179,4 +179,3 @@ Instead, the cmdlet configures one or more instances of the Microsoft.Rtc.Manage [Set-CsClientPin](Set-CsClientPin.md) [Unlock-CsClientPin](Unlock-CsClientPin.md) - diff --git a/skype/skype-ps/skype/Merge-CsLegacyTopology.md b/skype/skype-ps/skype/Merge-CsLegacyTopology.md index 59622383f3..c472df4e40 100644 --- a/skype/skype-ps/skype/Merge-CsLegacyTopology.md +++ b/skype/skype-ps/skype/Merge-CsLegacyTopology.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/merge-cslegacytopology +online version: https://learn.microsoft.com/powershell/module/skype/merge-cslegacytopology applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Merge-CsLegacyTopology schema: 2.0.0 @@ -239,4 +239,3 @@ The Merge-CsLegacyTopology cmdlet does not return any objects or values. [Import-CsLegacyConferenceDirectory](Import-CsLegacyConferenceDirectory.md) [Move-CsLegacyUser](Move-CsLegacyUser.md) - diff --git a/skype/skype-ps/skype/Move-CsAnalogDevice.md b/skype/skype-ps/skype/Move-CsAnalogDevice.md index c488118641..70102968cd 100644 --- a/skype/skype-ps/skype/Move-CsAnalogDevice.md +++ b/skype/skype-ps/skype/Move-CsAnalogDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csanalogdevice +online version: https://learn.microsoft.com/powershell/module/skype/move-csanalogdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsAnalogDevice schema: 2.0.0 @@ -322,4 +322,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsAnalogDevice](Remove-CsAnalogDevice.md) [Set-CsAnalogDevice](Set-CsAnalogDevice.md) - diff --git a/skype/skype-ps/skype/Move-CsApplicationEndpoint.md b/skype/skype-ps/skype/Move-CsApplicationEndpoint.md index f14fa25328..1947fce031 100644 --- a/skype/skype-ps/skype/Move-CsApplicationEndpoint.md +++ b/skype/skype-ps/skype/Move-CsApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/move-csapplicationendpoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsApplicationEndpoint schema: 2.0.0 @@ -218,4 +218,3 @@ When used with the PassThru parameter, returns an object of type Microsoft.Rtc.M ## RELATED LINKS [Get-CsApplicationEndpoint](Get-CsApplicationEndpoint.md) - diff --git a/skype/skype-ps/skype/Move-CsCommonAreaPhone.md b/skype/skype-ps/skype/Move-CsCommonAreaPhone.md index 98d6d08545..55cd8f84f2 100644 --- a/skype/skype-ps/skype/Move-CsCommonAreaPhone.md +++ b/skype/skype-ps/skype/Move-CsCommonAreaPhone.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-cscommonareaphone +online version: https://learn.microsoft.com/powershell/module/skype/move-cscommonareaphone applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsCommonAreaPhone schema: 2.0.0 @@ -332,4 +332,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [Remove-CsCommonAreaPhone](Remove-CsCommonAreaPhone.md) [Set-CsCommonAreaPhone](Set-CsCommonAreaPhone.md) - diff --git a/skype/skype-ps/skype/Move-CsConferenceDirectory.md b/skype/skype-ps/skype/Move-CsConferenceDirectory.md index 229a453c5b..239a0646db 100644 --- a/skype/skype-ps/skype/Move-CsConferenceDirectory.md +++ b/skype/skype-ps/skype/Move-CsConferenceDirectory.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csconferencedirectory +online version: https://learn.microsoft.com/powershell/module/skype/move-csconferencedirectory applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsConferenceDirectory schema: 2.0.0 @@ -191,4 +191,3 @@ None. [New-CsConferenceDirectory](New-CsConferenceDirectory.md) [Remove-CsConferenceDirectory](Remove-CsConferenceDirectory.md) - diff --git a/skype/skype-ps/skype/Move-CsExUmContact.md b/skype/skype-ps/skype/Move-CsExUmContact.md index 2e92cea44b..fd94b648a5 100644 --- a/skype/skype-ps/skype/Move-CsExUmContact.md +++ b/skype/skype-ps/skype/Move-CsExUmContact.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csexumcontact +online version: https://learn.microsoft.com/powershell/module/skype/move-csexumcontact applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsExUmContact schema: 2.0.0 @@ -304,4 +304,3 @@ When called with the PassThru parameter, returns an object of type Microsoft.Rtc [Set-CsExUmContact](Set-CsExUmContact.md) [Get-CsExUmContact](Get-CsExUmContact.md) - diff --git a/skype/skype-ps/skype/Move-CsLegacyUser.md b/skype/skype-ps/skype/Move-CsLegacyUser.md index 7ea473df4a..9bc5c5ed52 100644 --- a/skype/skype-ps/skype/Move-CsLegacyUser.md +++ b/skype/skype-ps/skype/Move-CsLegacyUser.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-cslegacyuser +online version: https://learn.microsoft.com/powershell/module/skype/move-cslegacyuser applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsLegacyUser schema: 2.0.0 @@ -419,4 +419,3 @@ Instead, the cmdlet moves instances of the Microsoft.Rtc.Management.ADConnect.Sc [Move-CsUser](Move-CsUser.md) [Set-CsUser](Set-CsUser.md) - diff --git a/skype/skype-ps/skype/Move-CsManagementServer.md b/skype/skype-ps/skype/Move-CsManagementServer.md index 84cd157e8a..5e869c100f 100644 --- a/skype/skype-ps/skype/Move-CsManagementServer.md +++ b/skype/skype-ps/skype/Move-CsManagementServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csmanagementserver +online version: https://learn.microsoft.com/powershell/module/skype/move-csmanagementserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsManagementServer schema: 2.0.0 @@ -254,5 +254,3 @@ The Move-CsManagementServer cmdlet does not return any objects. ## RELATED LINKS [Set-CsManagementServer](Set-CsManagementServer.md) - - diff --git a/skype/skype-ps/skype/Move-CsMeetingRoom.md b/skype/skype-ps/skype/Move-CsMeetingRoom.md index b428dea652..25aefd9c8e 100644 --- a/skype/skype-ps/skype/Move-CsMeetingRoom.md +++ b/skype/skype-ps/skype/Move-CsMeetingRoom.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csmeetingroom +online version: https://learn.microsoft.com/powershell/module/skype/move-csmeetingroom applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsMeetingRoom schema: 2.0.0 @@ -42,7 +42,7 @@ In Skype for Business Server 2015, meeting rooms are self-contained computer app * Calendar integration to provide access to scheduled meetings * Content sharing and switching -In order to manage these new endpoint devices you must, among other things, create and enable a Exchange resource mailbox account for the device, then enable that resource account for Skype for Business Server 2015. +In order to manage these new endpoint devices you must, among other things, create and enable an Exchange resource mailbox account for the device, then enable that resource account for Skype for Business Server 2015. Note that, for Skype for Business Server 2015, there are no cmdlets for creating or removing meeting rooms. Instead, you use the Enable-CsMeetingRoom cmdlet to enable meeting rooms and the Disable-CsMeetingRoom cmdlet to disable meeting rooms. The resource account must already exist in order for you to enable the meeting room, and disabling a meeting room only removes that room from your collection of meeting rooms; it does not delete the resource mailbox account. @@ -320,5 +320,3 @@ None. [Get-CsMeetingRoom](Get-CsMeetingRoom.md) [Set-CsMeetingRoom](Set-CsMeetingRoom.md) - - diff --git a/skype/skype-ps/skype/Move-CsRgsConfiguration.md b/skype/skype-ps/skype/Move-CsRgsConfiguration.md index 04125b4526..c0b6514042 100644 --- a/skype/skype-ps/skype/Move-CsRgsConfiguration.md +++ b/skype/skype-ps/skype/Move-CsRgsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csrgsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/move-csrgsconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsRgsConfiguration schema: 2.0.0 @@ -28,7 +28,7 @@ When someone calls a designated phone number, that call can be automatically rou Alternatively, the call might be routed to an interactive voice response (IVR) queue. In that queue, the caller would be asked a series of questions (for example, "Are you calling about an existing order?") and then, based on the answers to those questions, be given the asked-for information or be routed to a Response Group agent. -If you are currently running the Response Group application on legacy server, the Move-CsRgsConfiguration cmdlet provides a way for you to migrate this service to newer vesion server. +If you are currently running the Response Group application on legacy server, the Move-CsRgsConfiguration cmdlet provides a way for you to migrate this service to newer version server. To migrate the service, you need to call the Move-CsRgsConfiguration cmdlet and specify: 1) the fully qualified domain name (FQDN) for the existing version of the Response Group application (the Source); and, 2) the FQDN for the new Skype for Business Server version of the service (the Destination). Move-CsRgsConfiguration will then move all the configuration settings, audio files, and contact objects from the existing version (for example, Office Communications Server 2007 R2 or Lync Server 2010) to newer version. After the service has been migrated, all calls to a Response Group phone number will be handled by the newer server. @@ -142,6 +142,3 @@ Move-CsRgsConfiguration moves instances of the Microsoft.Rtc.Management.Writable [Get-CsRgsConfiguration](Get-CsRgsConfiguration.md) [Move-CsRgsConfiguration](Move-CsRgsConfiguration.md) - - - diff --git a/skype/skype-ps/skype/Move-CsThirdPartyVideoSystem.md b/skype/skype-ps/skype/Move-CsThirdPartyVideoSystem.md index e3623e8b51..6ab001cf5a 100644 --- a/skype/skype-ps/skype/Move-CsThirdPartyVideoSystem.md +++ b/skype/skype-ps/skype/Move-CsThirdPartyVideoSystem.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csthirdpartyvideosystem +online version: https://learn.microsoft.com/powershell/module/skype/move-csthirdpartyvideosystem applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsThirdPartyVideoSystem schema: 2.0.0 @@ -290,4 +290,3 @@ However, if you include the PassThru parameter you can instances of the Microsof [Remove-CsThirdPartyVideoSystem](Remove-CsThirdPartyVideoSystem.md) [Set-CsThirdPartyVideoSystem](Set-CsThirdPartyVideoSystem.md) - diff --git a/skype/skype-ps/skype/Move-CsUser.md b/skype/skype-ps/skype/Move-CsUser.md index 343508b8dd..29973fc914 100644 --- a/skype/skype-ps/skype/Move-CsUser.md +++ b/skype/skype-ps/skype/Move-CsUser.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/move-csuser +online version: https://learn.microsoft.com/powershell/module/skype/move-csuser applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Move-CsUser schema: 2.0.0 @@ -14,65 +14,86 @@ ms.reviewer: ## SYNOPSIS -Moves one or more user accounts enabled for Skype for Business Server to a new Registrar pool, or to Office 365 (either to Teams or Skype for Business Online). +Moves one or more user accounts enabled for Skype for Business Server to TeamsOnly (or the reverse). This cmdlet also can be used to move on-premises users from one pool to another. + +**PRE-REQUISITES steps for running Move-CsUser** +- Install or update the Microsoft Teams PowerShell module to version 6.2.1 or later + +**PRE-REQUISITES steps for** [Office 365 operated by 21Vianet](/microsoft-365/admin/services-in-china/services-in-china?view=o365-21vianet) +- Install or update the Microsoft Teams PowerShell module to version 6.2.1 or later +- Run Set-TeamsEnvironmentConfig -TeamsEnvironmentName TeamsChina + +For more information, see [Set-TeamsEnvironmentConfig](/powershell/module/teams/set-teamsenvironmentconfig). ## SYNTAX ### (Default) ``` -Move-CsUser [-Identity] <UserIdParameter> [-Target] <Fqdn> [-Credential <PSCredential>] [-MoveToTeams] [-HostedMigrationOverrideUrl <String>] [-UseOAuth] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-ProxyPool <Fqdn>] [-MoveConferenceData] [-Confirm] [-Force] [-PassThru] [-WhatIf] [<CommonParameters>] +Move-CsUser [-Identity] <UserIdParameter> [-Target] <Fqdn> [-Credential <PSCredential>] [-UseOAuth] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-ProxyPool <Fqdn>] [-MoveConferenceData] [-Report <String>] [-DomainController <Fqdn>] [-Confirm] [-Force] [-PassThru] [-WhatIf] [<CommonParameters>] +``` + +### UserList + +``` +Move-CsUser -UserList <String> [-Target] <Fqdn> [-Credential <PSCredential>] [-UseOAuth] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-ProxyPool <Fqdn>] [-MoveConferenceData] [-Report <String>] [-DomainController <Fqdn>] [-Confirm] [-Force] [-PassThru] [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION The Move-CsUser cmdlet enables you to move a user account enabled for Skype for Business in the following scenarios: -- from an on-premises Skype for Business deployment to Teams-only in Office 365 (or the reverse) -- from an on-premises Skype for Business deployment to Skype for Business Online in Office 365 (or the reverse) +- from an on-premises Skype for Business deployment to Teams-only in Microsoft 365 (or the reverse) - from one registrar pool to another, in an on-premises Skype for Business Server deployment. The Move-CsUser cmdlet affects only the user's Skype for Business Server account location; it does not move the user's Active Directory account to a new organizational unit (OU) or other new location. -When moving a user to or from Office 365 (either Skype for Business Online or Teams): +When moving a user to the Microsoft 365 cloud to become TeamsOnly (or the reverse): -- Skype for Business hybrid must be configured. For more information, see [Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online](https://docs.microsoft.com/en-us/SkypeForBusiness/skype-for-business-hybrid-solutions/deploy-hybrid-connectivity/deploy-hybrid-connectivity). -- To move a user to Office 365, specify the ProxyFqdn of the hosting provider as the Target. In most cases, this is "sipfed.online.lync.com" but in specialized environments there will be variants of this address. For more details, see [Move users between on-premises and cloud](https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud). -- When migrating from on-premises to the cloud, meetings are migrated from Skype for Business Server to online. If the `MoveToTeams` switch is specified, the meetings will be migrated to Teams meetings. Otherwise, meetings are migrated to Skype for Business Online. Teams-only users can still join meetings hosted in Skype for Business. For details see [Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/en-us/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms). -- Moving a user to Teams is achieved by specifying the MoveToTeams switch. This performs the same operations as a move to Skype for Business Online (without the specifying -MoveToTeams) and also performs the following actions: +- Skype for Business hybrid must be configured. For more information, see [Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online](https://learn.microsoft.com/SkypeForBusiness/skype-for-business-hybrid-solutions/deploy-hybrid-connectivity/deploy-hybrid-connectivity). +- To move a user to Microsoft 365, specify the ProxyFqdn of the hosting provider as the Target. In most cases, this is "sipfed.online.lync.com" but in specialized environments, there will be variants of this address. For more details, see [Move users between on-premises and cloud](/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud). +- When migrating from on-premises to the cloud, users are automatically assigned Teams Only mode and their meetings from on-premises are automatically converted to Teams meetings. This conversion happens regardless of which on-premises version of Skype for Business Server or Lync Server was being used. You no longer need to specify the `-MoveToTeams` switch. In fact, specifying that switch no longer has any impact. Teams Only users can still *join* meetings hosted in Skype for Business (for example, they're invited to a meeting by a Skype For Business user). However, beginning in October 2022, users moved from on-premises to Teams Only will no longer be provisioned with the Skype for Business Online infrastructure. At this point, Teams Only users can join Skype for Business meetings, but only anonymously. For more information, see [Skype for Business Online retirement](/microsoftteams/skype-for-business-online-retirement). +- When migrating from on-premises to the cloud, contacts from Skype for Business Server are migrated to the cloud (unless you use the `-Force` switch in the Move-CsUser command) and become available in Teams after the move is complete and the user logs on to Teams. To ensure these contacts are migrated to Teams, the migrated user must sign in to Teams within 30 days of being moved from on-premises to Teams Only. For details, see [Guidance for Organizations with on-premises deployments of Skype for Business Server](/microsoftteams/skype-for-business-online-retirement#guidance-for-organizations-with-on-premises-deployments-of-skype-for-business-server). +- If you receive an error while running this cmdlet about multiple federated Edge pools, Skype for Business Federation can only be enabled for a single Edge pool. If you have multiple Edge pools, select one to use as the federating Edge pool. - - TeamsUpgradePolicy with Mode=TeamsOnly is assigned to the online user account. - - Meeting migration is triggered to move meetings to Teams instead of Skype for Business Online. This functionality is currently available to TAP customers only. For customers not in TAP, meetings are always migrated to Skype for Business Online. - -- Contacts are moved in all cases, unless -force is specified. +> [!NOTE] +> +> - Moving users from On-Premises to Teams requires TLS 1.2. TLS 1.0 and TLS 1.1 have been deprecated. Please visit [Disabling TLS 1.0 and 1.1 for Microsoft 365](/microsoft-365/compliance/tls-1.0-and-1.1-deprecation-for-office-365?view=o365-worldwide) and [Preparing for TLS 1.2 in Office 365 and Office 365 GCC](/microsoft-365/compliance/prepare-tls-1.2-in-office-365?view=o365-worldwide) for details. +> - To use Multi-Factor Authentication (MFA) with Move-CsUser requires either Skype for Business Server 2015 CU12 or any version of Skype for Business Server 2019. When using MFA do not specify the -Credential parameter. If you are using an earlier version of Skype for Business Server, you should either disable MFA and use the credential parameter, or obtain a newer version of the administrative tools for Skype for Business Server that supports MFA. > [!NOTE] -> <ul><li>The MoveToTeams switch is only available on Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. Organizations using other versions of Skype for Business Server must first move the user to Skype for Business Online, and then apply TeamsUpgradePolicy.</li><li>If you are using Skype for Business Server 2015 with CU8 or later, we recommend you pass the `-UseOAuth` switch, which ensures the on-premises code authenticates using OAuth, instead of Legacy LiveID authentication. In Skype for Business Server 2019 and later versions, OAuth is always used hence the switch is not relevant on those versions.</li></ul> +> As of November 10, 2023, moving users from Teams to On-Premises will no longer migrate their contacts. This is mainly due to our continuous efforts to tighten security and protect customers' data. After carefully analyzing the usage patterns and performing risk assessments with the legacy infrastructure, we decided to deprecate this feature. +**MINIMUM REQUIRED SERVER VERSIONS**: +As of July 31, 2022, moving users between an on-premises deployment and the cloud requires the following minimum version of either Skype for Business Server or Lync Server. In the future, moves between on-premises and the cloud will no longer be possible if you are using a version earlier than the ones listed below. If you are still using an earlier version of Skype for Business Server, you should upgrade to the specified minimum version (or later) before July 31, 2022. +</br> +</br> -## EXAMPLES +|On-premises product|Required minimum version|Required minimum build| +|---|---|---| +|Skype for Business Server 2019| CU6 |7.0.2046.385| +|Skype for Business Server 2015| CU12|6.0.9319.619| +|Lync Server 2013| CU10 with Hotfix 7|5.0.8308.1182| +|||| -### ------- EXAMPLE 1: Move a user to Teams----------------------- +</br> +</br> -```powershell -$cred=get-credential -Move-CsUser -Identity "PilarA@contoso.com" -Target "sipfed.online.lync.com" -MoveToTeams -Credential $cred -``` - -In Example 1, the Move-CsUser cmdlet is used to move the user account with sip address PilarA@contoso.com to Teams. This user will now be a Teams only user. If -Credential parameter is not specified, the admin will be prompted for credentials. +## EXAMPLES -### ------- EXAMPLE 2: Move a user to Skype for Business Online ---- +### EXAMPLE 1: Move a user to Teams ```powershell $cred=get-credential -Move-CsUser -Identity PilarA@contoso.com -Target "sipfed.online.lync.com" -Credential $cred +Move-CsUser -Identity "PilarA@contoso.com" -Target "sipfed.online.lync.com" -Credential $cred ``` -In Example 2, the Move-CsUser cmdlet is used to move the user account with sip address PilarA@contoso.com to Skype for Business Online. This is the same cmdlet usage as example 1, except the MoveToTeams switch is not specified. +In Example 1, the Move-CsUser cmdlet is used to move the user account with sip address PilarA@contoso.com to Teams. This user will now be a Teams only user. If -Credential parameter is not specified, the admin will be prompted for credentials. It no longer matters whether the `-MoveToTeams` switch is specified. -### -------- EXAMPLE 3: Move a user to another on-premises pool------- + +### EXAMPLE 2: Move a user to another on-premises pool ```powershell Move-CsUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com" @@ -80,15 +101,24 @@ Move-CsUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com" In Example 3, the Move-CsUser cmdlet is used to move the user account with the Identity Pilar Ackerman to the Registrar pool atl-cs-001.litwareinc.com. -### --------- EXAMPLE 4: Move multiple users --------------------------- +### EXAMPLE 3: Move multiple users ```powershell Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Move-CsUser -Target "atl-cs-001.litwareinc.com" ``` -In Example 4, all the user accounts in the Finance organizational unit (OU) are moved to the Registrar pool atl-cs-001.litwareinc.com. +In Example 4, all the user accounts in the Finance organizational unit (OU) are moved to the Registrar pool atl-cs-001.litwareinc.com in on-premises. To carry out this task, the command first uses the Get-CsUser cmdlet and the OU parameter to retrieve a collection of all the user accounts in the Finance OU. After the data has been retrieved, the information is piped to the Move-CsUser cmdlet, which moves each account in the collection to the Registrar pool atl-cs-001.litwareinc.com. +### EXAMPLE 4: Move multiple users listed in a file + +```powershell +Move-CsUser -UserList C:\Folder1\Folder2\file1.txt -Target "atl-cs-001.litwareinc.com" -Report C:\Folder1\Folder2\out.csv +``` + +In Example 5, all the users listed in file1.txt are moved to the Registrar pool atl-cs-001.litwareinc.com. +Also, a detailed report is created in the out.csv file. + ## PARAMETERS ### -Identity @@ -115,9 +145,9 @@ Accept wildcard characters: False ### -Target -If moving to an on-premises pool (either from another pool or from Office 365), this is the FQDN (for example, atl-cs-001.litwareinc.com) of the Registrar pool where the user account should be moved. +If moving to an on-premises pool (either from another pool or from Microsoft 365), this is the FQDN (for example, atl-cs-001.litwareinc.com) of the Registrar pool where the user account should be moved. -If moving to Office 365, this must be set to the ProxyFqdn value of the hosting provider. In most cases this is sipfed.online.lync.com. The value of the ProxyFqdn can be obtained using Get-CsHostingProvider +If moving to Microsoft 365, this must be set to the ProxyFqdn value of the hosting provider. In most cases this is sipfed.online.lync.com. The value of the ProxyFqdn can be obtained using Get-CsHostingProvider ```yaml Type: Fqdn @@ -132,22 +162,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MoveToTeams - -If specified, the user will be moved to Office 365 as a Teams-only user. This will ensure incoming chats and calls land in the user's Teams client. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Server 2015, Skype for Business Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Credential Enables you to run the Move-CsUser cmdlet under alternate credentials, which is typically required when moving to Office 365. To use the Credential parameter you must first create a PSCredential object using the Get-Credential cmdlet. For details, see the Get-Credential cmdlet help topic. @@ -165,26 +179,9 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -HostedMigrationOverrideUrl - -The hosted migration service is the service in Office 365 that performs user moves. By default, there is no need to specify a value for this parameter, as long as the hosting provider has its AutoDiscover URL properly configured and you are using an admin account the ends in .onmicrosoft.com. If you are using a user account from on-premises that synchronized to the cloud, you must specify this parameter. See [Required administrative credentials](https://docs.microsoft.com/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud#required-administrative-credentials). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -UseOAuth -If specified, authentication between on-premises and the host migration service is based on OAuth protocol. Otherwise, authentication is based on legacy LiveID authentication. This parameter is only available with Skype for Business Server 2015 with CU8 or later. In Skype for Business Server 2019 and later versions, OAuth is always used hence the switch is not relevant on those versions. +This switch is no longer relevant. Previously, this switch ensured authentication between on-premises and the cloud. This switch also ensured Skype for Business Server 2015 CU8 to CU11 used the OAuth protocol (supported in those versions, but not used by default). All currently supported versions for migration to Teams (see the list earlier in this article) automatically use OAuth, so this switch is no longer required. ```yaml Type: SwitchParameter @@ -200,7 +197,7 @@ Accept wildcard characters: False ### -BypassAudioConferencingCheck -By default, if the on-premise user is configured for dial in conferencing, moving the user to Office 365 will provision the user for Audio Conferencing, for an additional license is required. If you want to move such a user to Office 365 but do not want to configure them for Audio Conferencing, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. +This parameter has been deprecated and should not be used. ```yaml Type: SwitchParameter @@ -216,7 +213,7 @@ Accept wildcard characters: False ### -BypassEnterpriseVoiceCheck -By default, if the on-premise user is configured for Enterprise Voice, moving the user to Office 365 will provision the user for Microsoft Phone System, for an additional license is required. If you want to move such a user to Office 365 but do not want to configure them for Phone System, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. +This parameter has been deprecated and should not be used. ```yaml Type: SwitchParameter @@ -247,7 +244,7 @@ Accept wildcard characters: False ### -ProxyPool -This parameter has been deprecated and should not be used. +This is an optional parameter that can be used to specify the front-end pool for user migration. ```yaml Type: Fqdn @@ -298,7 +295,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` - ### -Confirm Enables you to bypass the confirmation prompt that would otherwise appear when you attempt to move a user. @@ -314,7 +310,7 @@ If you would prefer to have the confirmation prompt then use this syntax: Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -325,7 +321,7 @@ Accept wildcard characters: False ### -Report -PARAMVALUE: String +A CSV file to be created with detailed information about the move. You can supply the file name if you want to create the file in the current folder, or an absolute path. ```yaml Type: String @@ -340,6 +336,39 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -UserList + +A text file with a list of users to be moved, in the following format example: "sip:user1@contoso.com,sip:user2@contoso.com,sip:user3@contoso.com". You can supply the file name if it's located in the current folder, or the absolute path to the file. + +```yaml +Type: String +Parameter Sets: Users +Aliases: +Applicable: Skype for Business Server 2015, Skype for Business Server 2019 + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -PassThru Enables you to pass a user object through the pipeline that represents the user account being moved. @@ -400,10 +429,12 @@ Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.ADConnect ## RELATED LINKS -[Move users between on-premises and cloud](https://docs.microsoft.com/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud) +[Move users between on-premises and cloud](https://learn.microsoft.com/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud) + +[Configure Skype for Business hybrid](https://learn.microsoft.com/SkypeForBusiness/hybrid/configure-federation-with-skype-for-business-online) -[Skype for Business Hybrid Solutions](https://docs.microsoft.com/SkypeForBusiness/skype-for-business-hybrid-solutions/skype-for-business-hybrid-solutions) +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) +[Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms) -[Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms) +[Guidance for Organizations with on-premises deployments of Skype for Business Server](https://learn.microsoft.com/microsoftteams/skype-for-business-online-retirement#guidance-for-organizations-with-on-premises-deployments-of-skype-for-business-server) diff --git a/skype/skype-ps/skype/New-CsAVEdgeConfiguration.md b/skype/skype-ps/skype/New-CsAVEdgeConfiguration.md index 17852612cf..89161bbc99 100644 --- a/skype/skype-ps/skype/New-CsAVEdgeConfiguration.md +++ b/skype/skype-ps/skype/New-CsAVEdgeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csavedgeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csavedgeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAVEdgeConfiguration schema: 2.0.0 @@ -247,4 +247,3 @@ Creates instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.M [Remove-CsAVEdgeConfiguration](Remove-CsAVEdgeConfiguration.md) [Set-CsAVEdgeConfiguration](Set-CsAVEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsAdditionalInternalDomain.md b/skype/skype-ps/skype/New-CsAdditionalInternalDomain.md index c079e057ec..02cf488052 100644 --- a/skype/skype-ps/skype/New-CsAdditionalInternalDomain.md +++ b/skype/skype-ps/skype/New-CsAdditionalInternalDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csadditionalinternaldomain +online version: https://learn.microsoft.com/powershell/module/skype/new-csadditionalinternaldomain applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAdditionalInternalDomain schema: 2.0.0 @@ -158,7 +158,6 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[Remove-CsAdditionalInternalDomain](https://docs.microsoft.com/powershell/module/skype/remove-csadditionalinternaldomain?view=skype-ps) - -[Get-CsAdditionalInternalDomain](https://docs.microsoft.com/powershell/module/skype/get-csadditionalinternaldomain?view=skype-ps) +[Remove-CsAdditionalInternalDomain](https://learn.microsoft.com/powershell/module/skype/remove-csadditionalinternaldomain?view=skype-ps) +[Get-CsAdditionalInternalDomain](https://learn.microsoft.com/powershell/module/skype/get-csadditionalinternaldomain?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsAddressBookConfiguration.md b/skype/skype-ps/skype/New-CsAddressBookConfiguration.md index 8b840efd27..2e6b1c092e 100644 --- a/skype/skype-ps/skype/New-CsAddressBookConfiguration.md +++ b/skype/skype-ps/skype/New-CsAddressBookConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csaddressbookconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csaddressbookconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAddressBookConfiguration schema: 2.0.0 @@ -417,5 +417,3 @@ Creates instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Addres [Remove-CsAddressBookConfiguration](Remove-CsAddressBookConfiguration.md) [Set-CsAddressBookConfiguration](Set-CsAddressBookConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsAddressBookNormalizationConfiguration.md b/skype/skype-ps/skype/New-CsAddressBookNormalizationConfiguration.md index e419a2fce0..3291177ad9 100644 --- a/skype/skype-ps/skype/New-CsAddressBookNormalizationConfiguration.md +++ b/skype/skype-ps/skype/New-CsAddressBookNormalizationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csaddressbooknormalizationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csaddressbooknormalizationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAddressBookNormalizationConfiguration schema: 2.0.0 @@ -175,5 +175,3 @@ The New-CsAddressBookNormalizationConfiguration cmdlet creates new instances of [Set-CsAddressBookNormalizationConfiguration](Set-CsAddressBookNormalizationConfiguration.md) [Import-CsCompanyPhoneNormalizationRules](Import-CsCompanyPhoneNormalizationRules.md) - - diff --git a/skype/skype-ps/skype/New-CsAddressBookNormalizationRule.md b/skype/skype-ps/skype/New-CsAddressBookNormalizationRule.md index 494f56d48c..9aa677a96c 100644 --- a/skype/skype-ps/skype/New-CsAddressBookNormalizationRule.md +++ b/skype/skype-ps/skype/New-CsAddressBookNormalizationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csaddressbooknormalizationrule +online version: https://learn.microsoft.com/powershell/module/skype/new-csaddressbooknormalizationrule applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAddressBookNormalizationRule schema: 2.0.0 @@ -282,4 +282,3 @@ The New-CsAddressBookNormalizationRule cmdlet creates instances of the Microsoft [Remove-CsAddressBookNormalizationRule](Remove-CsAddressBookNormalizationRule.md) [Set-CsAddressBookNormalizationRule](Set-CsAddressBookNormalizationRule.md) - diff --git a/skype/skype-ps/skype/New-CsAdminRole.md b/skype/skype-ps/skype/New-CsAdminRole.md index 36e2214873..afa8e62603 100644 --- a/skype/skype-ps/skype/New-CsAdminRole.md +++ b/skype/skype-ps/skype/New-CsAdminRole.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csadminrole +online version: https://learn.microsoft.com/powershell/module/skype/new-csadminrole applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAdminRole schema: 2.0.0 @@ -366,4 +366,3 @@ The New-CsAdminRole cmdlet creates new instances of the Microsoft.Rtc.Management ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsAllowedDomain.md b/skype/skype-ps/skype/New-CsAllowedDomain.md index 3353e6c901..4bd2464f78 100644 --- a/skype/skype-ps/skype/New-CsAllowedDomain.md +++ b/skype/skype-ps/skype/New-CsAllowedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csalloweddomain +online version: https://learn.microsoft.com/powershell/module/skype/new-csalloweddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAllowedDomain schema: 2.0.0 @@ -325,5 +325,3 @@ Creates instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.A [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) [Set-CsAllowedDomain](Set-CsAllowedDomain.md) - - diff --git a/skype/skype-ps/skype/New-CsAnalogDevice.md b/skype/skype-ps/skype/New-CsAnalogDevice.md index e25e2a27c7..78fd82666f 100644 --- a/skype/skype-ps/skype/New-CsAnalogDevice.md +++ b/skype/skype-ps/skype/New-CsAnalogDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csanalogdevice +online version: https://learn.microsoft.com/powershell/module/skype/new-csanalogdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAnalogDevice schema: 2.0.0 @@ -306,4 +306,3 @@ The New-CsAnalogDevice cmdlet creates new instances of the Microsoft.Rtc.Managem [Remove-CsAnalogDevice](Remove-CsAnalogDevice.md) [Set-CsAnalogDevice](Set-CsAnalogDevice.md) - diff --git a/skype/skype-ps/skype/New-CsAnnouncement.md b/skype/skype-ps/skype/New-CsAnnouncement.md index a69ceb3e17..5d2ff20332 100644 --- a/skype/skype-ps/skype/New-CsAnnouncement.md +++ b/skype/skype-ps/skype/New-CsAnnouncement.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csannouncement +online version: https://learn.microsoft.com/powershell/module/skype/new-csannouncement applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAnnouncement schema: 2.0.0 @@ -360,4 +360,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Annou [New-CsUnassignedNumber](New-CsUnassignedNumber.md) [Set-CsUnassignedNumber](Set-CsUnassignedNumber.md) - diff --git a/skype/skype-ps/skype/New-CsArchivingConfiguration.md b/skype/skype-ps/skype/New-CsArchivingConfiguration.md index e0bfea4da0..16ef9e0722 100644 --- a/skype/skype-ps/skype/New-CsArchivingConfiguration.md +++ b/skype/skype-ps/skype/New-CsArchivingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csarchivingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csarchivingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsArchivingConfiguration schema: 2.0.0 @@ -384,4 +384,3 @@ The New-CsArchivingConfiguration cmdlet creates new instances of the Microsoft.R [Set-CsArchivingConfiguration](Set-CsArchivingConfiguration.md) [Set-CsArchivingServer](Set-CsArchivingServer.md) - diff --git a/skype/skype-ps/skype/New-CsArchivingPolicy.md b/skype/skype-ps/skype/New-CsArchivingPolicy.md index cefdc13ced..1abff2dd90 100644 --- a/skype/skype-ps/skype/New-CsArchivingPolicy.md +++ b/skype/skype-ps/skype/New-CsArchivingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csarchivingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csarchivingpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsArchivingPolicy schema: 2.0.0 @@ -279,5 +279,3 @@ The New-CsArchivingPolicy cmdlet creates instances of the Microsoft.Rtc.Manageme [Remove-CsArchivingPolicy](Remove-CsArchivingPolicy.md) [Set-CsArchivingPolicy](Set-CsArchivingPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsAutoAttendantCallFlow.md b/skype/skype-ps/skype/New-CsAutoAttendantCallFlow.md deleted file mode 100644 index 0fa48f36ff..0000000000 --- a/skype/skype-ps/skype/New-CsAutoAttendantCallFlow.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendantcallflow -applicable: Skype for Business Online -title: New-CsAutoAttendantCallFlow -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsAutoAttendantCallFlow - -## SYNOPSIS -Use the New-CsAutoAttendantCallFlow cmdlet to create a new call flow. - -## SYNTAX - -```powershell -New-CsAutoAttendantCallFlow -Name <String> -Menu <Object> [-Greetings <List>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsAutoAttendantCallFlow cmdlet creates a new call flow for use with the Auto Attendant (AA) service. The AA service uses the call flow to handle inbound calls by playing a greeting (if present), and provide callers with actions through a menu. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -$menuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$menu = New-CsAutoAttendantMenu -Name "Default Menu" -Prompts @($menuPrompt) -EnableDialByName -$callFlow = New-CsAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu -``` - -This example creates a new call flow that renders the "Default Menu" menu. - -### -------------------------- Example 2 -------------------------- -```powershell -$menuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$menu = New-CsAutoAttendantMenu -Name "Default Menu" -Prompts $menuPrompt -EnableDialByName -$greeting = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" -$callFlow = New-CsAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu -Greetings $greeting -``` - -This example creates a new call flow that plays a greeting before rendering the "Default Menu" menu. - -## PARAMETERS - -### -Name -The Name parameter represents a unique friendly name for the call flow. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Menu -The Menu parameter identifies the menu to render when the call flow is executed. - -You can create a new menu by using the [`New-CsAutoAttendantMenu`](New-CsAutoAttendantMenu.md) cmdlet. - - -```yaml -Type: System.Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Greetings -If present, the prompts specified by the Greetings parameter (either TTS or Audio) are played before the call flow's menu is rendered. - -You can create prompts by using the [`New-CsAutoAttendantPrompt`](New-CsAutoAttendantPrompt.md) cmdlet. - - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.CallFlow - - -## NOTES - -## RELATED LINKS - -[New-CsAutoAttendantMenu](New-CsAutoAttendantMenu.md) - -[New-CsAutoAttendantPrompt](New-CsAutoAttendantPrompt.md) diff --git a/skype/skype-ps/skype/New-CsAutoAttendantCallableEntity.md b/skype/skype-ps/skype/New-CsAutoAttendantCallableEntity.md deleted file mode 100644 index 90039a9a4c..0000000000 --- a/skype/skype-ps/skype/New-CsAutoAttendantCallableEntity.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendantcallableentity -applicable: Skype for Business Online -title: New-CsAutoAttendantCallableEntity -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsAutoAttendantCallableEntity - -## SYNOPSIS -The New-CsAutoAttendantCallableEntity cmdlet lets you create a callable entity. - -## SYNTAX - -```powershell -New-CsAutoAttendantCallableEntity -Identity <String> -Type <User | OrganizationalAutoAttendant | HuntGroup | ApplicationEndpoint | ExternalPstn | SharedVoicemail> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsAutoAttendantCallableEntity cmdlet lets you create a callable entity for use with call transfers from the Auto Attendant service. Callable entities can be created using either Object ID or TEL URIs and can refer to any of the following entities: - -- User -- OrganizationalAutoAttendant -- HuntGroup -- ApplicationEndpoint -- ExternalPstn -- SharedVoicemail - -**NOTE** - -In order to setup a shared voicemail, an Office 365 Group that can receive external emails is required. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -$callableEntity = New-CsAutoAttendantCallableEntity -Identity "9bad1a25-3203-5207-b34d-1bd933b867a5" -Type User -``` - -This example creates a user callable entity. - -### -------------------------- Example 2 -------------------------- -```powershell -$callableEntity = New-CsAutoAttendantCallableEntity -Identity "tel:+1234567890" -Type ApplicationEndpoint -``` - -This example creates an application endpoint callable entity. - -### -------------------------- Example 3 -------------------------- -```powershell -$operatorObjectId = (Get-CsOnlineUser operator@contoso.com).ObjectId -$callableEntity = New-CsAutoAttendantCallableEntity -Identity $operatorObjectId -Type User -``` - -This example gets a user object using Get-CsOnlineUser cmdlet. We then use the AAD ObjectId of that user object to create a user callable entity. - -### -------------------------- Example 4 -------------------------- -```powershell -$callableEntityId = (Find-CsOnlineApplicationInstance -SearchQuery "Main Auto Attendant") -MaxResults 1 | Select-Object -Property Id -$callableEntity = New-CsAutoAttendantCallableEntity -Identity $callableEntityId -Type ApplicationEndpoint -``` - -This example gets an application instance by name using Find-CsOnlineApplicationInstance cmdlet. We then use the AAD ObjectId of that application instance to create an application endpoint callable entity. - -### -------------------------- Example 5 -------------------------- -```powershell -$callableEntityGroup = Find-CsGroup -SearchQuery "Main Auto Attendant" -ExactMatchOnly $true -MailEnabledOnly $true -$callableEntity = New-CsAutoAttendantCallableEntity -Identity $callableEntityGroup -Type SharedVoicemail -EnableTranscription -``` - -This example gets an Office 365 group by name using Find-CsGroup cmdlet. Then the Guid of that group is used to create a shared voicemail callable entity that supports transcription. - -## PARAMETERS - -### -Identity -The Identity parameter represents the ID of the callable entity; this can be either a Object ID or a TEL URI. - -- Only the Object IDs of users that have Enterprise Voice enabled are supported. -- Only PSTN numbers that are acquired and assigned through Skype for Business Online are supported. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -The Type parameter represents the type of the callable entity, which can be any of the following: - -- User -- OrganizationalAutoAttendant -- HuntGroup -- ApplicationEndpoint -- ExternalPstn -- SharedVoicemail - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTranscription -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.CallableEntity - - -## NOTES - -## RELATED LINKS - -[Get-CsOnlineUser](Get-CsOnlineUser.md) - -[Find-CsOnlineApplicationInstance](Find-CsOnlineApplicationInstance.md) diff --git a/skype/skype-ps/skype/New-CsAutoAttendantDialScope.md b/skype/skype-ps/skype/New-CsAutoAttendantDialScope.md deleted file mode 100644 index f64b768d24..0000000000 --- a/skype/skype-ps/skype/New-CsAutoAttendantDialScope.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendantdialscope -applicable: Skype for Business Online -title: New-CsAutoAttendantDialScope -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsAutoAttendantDialScope - -## SYNOPSIS -Use New-CsAutoAttendantDialScope cmdlet to create dial-scopes for use with Auto Attendant (AA) service. - -## SYNTAX - -``` -New-CsAutoAttendantDialScope -GroupScope -GroupIds <List> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new dial-scope to be used with Auto Attendant (AA) service. AAs use dial-scopes to restrict the scope of call transfers that can be made through directory lookup feature. - -**NOTE** -- The returned dial-scope model composes a member for the underlying type/implementation, e.g. in case of the group-based dial scope, in order to modify its Group IDs, you can access them through `DialScope.GroupScope.GroupIds`. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$groupIds = @("00000000-0000-0000-0000-000000000000") -$dialScope = New-CsAutoAttendantDialScope -GroupScope -GroupIds $groupIds -``` - -In Example 1, the New-CsAutoAttendantDialScope cmdlet is used to create a dial-scope with a group whose id is 00000000-0000-0000-0000-000000000000. - -### -------------------------- Example 2 -------------------------- -``` -$groupIds = Find-CsGroup -SearchQuery "Contoso Sales" | % { $_.Id } -$dialScope = New-CsAutoAttendantDialScope -GroupScope -GroupIds $groupIds -``` - -In Example 2, we use the Find-CsGroup cmdlet to find groups with name "Contoso Sales", and then use the identities of those groups to create an auto attendant dial scope using the New-CsAutoAttendantDialScope cmdlet. - -## PARAMETERS - -### -GroupScope -Indicates that a dial-scope based on groups (distribution lists, security groups) is to be created. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupIds -Refers to the IDs of the groups that are to be included in the dial-scope. - -Group IDs can be obtained by using the Find-CsGroup cmdlet. - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.OAA.Models.DialScope - - -## NOTES - -## RELATED LINKS - -[Find-CsGroup](Find-CsGroup.md) diff --git a/skype/skype-ps/skype/New-CsAutoAttendantMenuOption.md b/skype/skype-ps/skype/New-CsAutoAttendantMenuOption.md deleted file mode 100644 index b95827ef0a..0000000000 --- a/skype/skype-ps/skype/New-CsAutoAttendantMenuOption.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendantmenuoption -applicable: Skype for Business Online -title: New-CsAutoAttendantMenuOption -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsAutoAttendantMenuOption - -## SYNOPSIS -Use the New-CsAutoAttendantMenuOption cmdlet to create a new menu option. - -## SYNTAX - -``` -New-CsAutoAttendantMenuOption -Action <DisconnectCall | TransferCallToOperator | TransferCallToTarget> -DtmfResponse <Tone0 | Tone1 | Tone2 | Tone3 | Tone4 | Tone5 | Tone6 | Tone7 | Tone8 | Tone9 | Automatic> [-VoiceResponses <List>] [-CallTarget <Object>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsAutoAttendantMenuOption cmdlet creates a new menu option for the Auto Attendant (AA) service. The AA service uses the menu options to respond to a caller with the appropriate action. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$menuOption = New-CsAutoAttendantMenuOption -Action TransferCallToOperator -DtmfResponse Tone0 -``` - -This example creates a menu option to call the operator when the 0 key is pressed. - -### -------------------------- Example 2 -------------------------- -``` -$troubleShootObjectId = (Get-CsOnlineUser troubleShoot@contoso.com).ObjectId -$troubleShootEntity = New-CsAutoAttendantCallableEntity -Identity $troubleShootObjectId -Type AApplicationEndpoint -$menuOption = New-CsAutoAttendantMenuOption -Action TransferCallToTarget -DtmfResponse Tone1 -VoiceResponses "Sales" -CallTarget $troubleShootEntity -``` - -This example creates a menu option to transfer the call to an application endpoint when the caller speaks the word "Sales" or presses the 1 key. - - -## PARAMETERS - -### -Action -The Action parameter represents the action to be taken when the menu option is activated. The Action must be set to one of the following values: - -- DisconnectCall - The call is disconnected. -- TransferCallToOperator - the call is transferred to the operator. -- TransferCallToTarget - The call is transferred to the menu option's call target. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DtmfResponse -The DtmfResponse parameter indicates the key on the telephone keypad to be pressed to activate the menu option. The DtmfResponse must be set to one of the following values: - -- Tone0 to Tone9 - Corresponds to DTMF tones from 0 to 9. -- Automatic - The action is executed without user response. - - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VoiceResponses -The VoiceResponses parameter represents the voice responses to select a menu option when Voice Responses are enabled for the auto attendant. - -Voice responses are currently limited to one voice response per menu option. - - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallTarget -The CallTarget parameter represents the target for call transfer after the menu option is selected. - -CallTarget is required if the action of the menu option is TransferCallToTarget. - -Use the New-CsAutoAttendantCallableEntity cmdlet to create new callable entities. - - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.MenuOption - - -## NOTES - -## RELATED LINKS - -[New-CsAutoAttendantCallableEntity](New-CsAutoAttendantCallableEntity.md) diff --git a/skype/skype-ps/skype/New-CsAutodiscoverConfiguration.md b/skype/skype-ps/skype/New-CsAutodiscoverConfiguration.md index 38c77c42ec..0e9d77cb0a 100644 --- a/skype/skype-ps/skype/New-CsAutodiscoverConfiguration.md +++ b/skype/skype-ps/skype/New-CsAutodiscoverConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautodiscoverconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csautodiscoverconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsAutodiscoverConfiguration schema: 2.0.0 manager: rogupta @@ -74,7 +74,7 @@ $Link2 = New-CsWebLink -Token "Fabrikam" -Href "https://LyncDiscoverInternal.fab New-CsAutoDiscoverConfiguration -Identity "site:Redmond" -WebLinks @{Add=$Link1,$Link2} ``` -The commands shown in Example 2 create a new collection of Autodiscover configuration settings for the Redmond site and assign those new settings a pair of Autodiscover URLs: https://LyncDiscover.fabrikam.com and https://LyncDiscoverInternal.fabrikam.com. +The commands shown in Example 2 create a new collection of Autodiscover configuration settings for the Redmond site and assign those new settings a pair of Autodiscover URLs: `https://LyncDiscover.fabrikam.com` and `https://LyncDiscoverInternal.fabrikam.com`. In order to carry out this task, the first two commands use the New-CsWebLink cmdlet to create the two Autodiscover URLs; the newly-created URLs are then stored in variables named $Link1 and $Link2. After the two URLs are created, the third command uses the New-CsAutoDiscoverConfiguration cmdlet to create the new Autodiscover configuration settings. In order to assign the two URLs to these settings, the WebLinks parameter is included along with the parameter value @{Add=$Link1,$Link2}. @@ -251,4 +251,3 @@ Creates new instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.A ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsBandwidthPolicyServiceConfiguration.md b/skype/skype-ps/skype/New-CsBandwidthPolicyServiceConfiguration.md index 249c7c1f36..3a2dc9990e 100644 --- a/skype/skype-ps/skype/New-CsBandwidthPolicyServiceConfiguration.md +++ b/skype/skype-ps/skype/New-CsBandwidthPolicyServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csbandwidthpolicyserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csbandwidthpolicyserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsBandwidthPolicyServiceConfiguration schema: 2.0.0 @@ -248,4 +248,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Bandw [Set-CsBandwidthPolicyServiceConfiguration](Set-CsBandwidthPolicyServiceConfiguration.md) [Get-CsBandwidthPolicyServiceConfiguration](Get-CsBandwidthPolicyServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsBlockedDomain.md b/skype/skype-ps/skype/New-CsBlockedDomain.md index 4fdce3e023..4b9231b7d5 100644 --- a/skype/skype-ps/skype/New-CsBlockedDomain.md +++ b/skype/skype-ps/skype/New-CsBlockedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csblockeddomain +online version: https://learn.microsoft.com/powershell/module/skype/new-csblockeddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsBlockedDomain schema: 2.0.0 @@ -242,5 +242,3 @@ Creates instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.B [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) [Set-CsBlockedDomain](Set-CsBlockedDomain.md) - - diff --git a/skype/skype-ps/skype/New-CsCallParkOrbit.md b/skype/skype-ps/skype/New-CsCallParkOrbit.md index f335a62a13..fb35a67100 100644 --- a/skype/skype-ps/skype/New-CsCallParkOrbit.md +++ b/skype/skype-ps/skype/New-CsCallParkOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscallparkorbit +online version: https://learn.microsoft.com/powershell/module/skype/new-cscallparkorbit applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsCallParkOrbit schema: 2.0.0 @@ -287,5 +287,3 @@ This cmdlet creates an object of type Microsoft.Rtc.Management.Voice.Helpers.Dis [Set-CsCallParkOrbit](Set-CsCallParkOrbit.md) [Get-CsCallParkOrbit](Get-CsCallParkOrbit.md) - - diff --git a/skype/skype-ps/skype/New-CsCallQueue.md b/skype/skype-ps/skype/New-CsCallQueue.md deleted file mode 100644 index 0da3630941..0000000000 --- a/skype/skype-ps/skype/New-CsCallQueue.md +++ /dev/null @@ -1,342 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscallqueue -applicable: Skype for Business Online -title: New-CsCallQueue -author: tomkau -ms.author: tomkau -manager: bulenteg -ms.reviewer: -schema: 2.0.0 ---- - -# New-CsCallQueue - -## SYNOPSIS -Creates new Call Queue in your Skype for Business Online organization. - -## SYNTAX - -``` -New-CsCallQueue -Name <String> [-AgentAlertTime <Int16>] [-AllowOptOut <Boolean>] [-DistributionLists <List>] -[-Tenant <Guid>] [-UseDefaultMusicOnHold <Boolean>] [-WelcomeMusicAudioFileId <Guid>] [-MusicOnHoldAudioFileId <Guid>] -[-OverflowAction <Object>] [-OverflowActionTarget <Guid>] [-OverflowThreshold <Int16>] -[-TimeoutAction <Object>] [-TimeoutActionTarget <Guid>] [-TimeoutThreshold <Int16>] -[-RoutingMethod <Object>] [-PresenceBasedRouting <Boolean>] [-Users <List>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsCallQueue cmdlet creates a new Call Queue. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsCallQueue -Name "Help Desk" -UseDefaultMusicOnHold $true -``` - -This example creates a Call Queue for the organization named "Help Desk" using default music on hold. - -### -------------------------- Example 2 -------------------------- -``` -New-CsCallQueue -Name "Help desk" -RoutingMethod Attendant -DistributionLists @("8521b0e3-51bd-4a4b-a8d6-b219a77a0a6a", "868dccd8-d723-4b4f-8d74-ab59e207c357") -AllowOptOut $false -AgentAlertTime 30 -OverflowThreshold 15 -OverflowAction Forward -OverflowActionTarget 7fd04db1-1c8e-4fdf-9af5-031514ba1358 -TimeoutThreshold 30 -TimeoutAction Disconnect -MusicOnHoldAudioFileId 1e81adaf-7c3e-4db1-9d61-5d135abb1bcc -WelcomeMusicAudioFileId 0b31bbe5-e2a0-4117-9b6f-956bca6023f8 - -``` - -This example creates a Call Queue for the organization named "Help Desk" with music on hold and welcome music audio files. - - -## PARAMETERS - -### -Name -The Name parameter specifies a unique name for the Call Queue. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AgentAlertTime -The AgentAlertTime parameter represents the time (in seconds) that a call can remain unanswered before it is automatically routed to the next agent. The AgentAlertTime can be set to any integer value between 30 and 180 seconds (3 minutes), inclusive. The default value is 30 seconds. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 30 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOptOut -The AllowOptOut parameter indicates whether or not agents can opt in or opt out from taking calls from a Call Queue. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionLists -The DistributionLists parameter lets you add all the members of the distribution lists to the Call Queue. This is a list of distribution list GUIDs. A service wide configurable maximum number of DLs per Call Queue are allowed. Only the first N (service wide configurable) agents from all distribution lists combined are considered for accepting the call. Nested DLs are supported. O365 Groups can also be used to add members to the Call Queue. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MusicOnHoldAudioFileId -The MusicOnHoldFileContent parameter represents music to play when callers are placed on hold. This is the unique identifier of the audio file. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowAction -The OverflowAction parameter designates the action to take if the overflow threshold is reached. The OverflowAction property must be set to one of the following three values: DisconnectWithBusy, Forward, and Voicemail. - -PARAMVALUE: DisconnectWithBusy | Forward | Voicemail - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: DisconnectWithBusy -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowActionTarget -The OverflowActionTarget parameter represents the target of the overflow action. If the OverFlowAction is set to Forward, this parameter must be set to a Guid. Otherwise, this parameter is optional. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowThreshold -The OverflowThreshold parameter defines the number of calls that can be in the queue at any one time before the overflow action is triggered. The OverflowThreshold can be any integer value between 0 and 200, inclusive. A value of 0 causes calls not to reach agents and the overflow action to be taken immediately - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 50 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoutingMethod -The RoutingMethod defines how agents will be called in a Call Queue. If the routing method is set to Serial, then agents will be called one at a time. If the routing method is set to Attendant, then agents will be called in parallel. - -PARAMVALUE: Attendant | Serial | RoundRobin - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Attendant -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutAction -The TimeoutAction parameter defines the action to take if the timeout threshold is reached. The TimeoutAction property must be set to one of the following three values: Disconnect, Forward, and Voicemail. The default value is Disconnect. - -PARAMVALUE: Disconnect | Forward | Voicemail - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Disconnect -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutActionTarget -The TimeoutActionTarget represents the target of the timeout action. If the TimeoutAction is set to Forward, this parameter must be set to a Guid. Otherwise, this field is optional. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutThreshold -The TimeoutThreshold parameter defines the time (in seconds) that a call can be in the queue before that call times out. At that point, the system will take the action specified by the TimeoutAction parameter. -The TimeoutThreshold can be any integer value between 0 and 2700 seconds (inclusive), and is rounded to the nearest 15th interval. For example, if set to 47 seconds, then it is rounded down to 45. If set to 0, welcome music is played, and then the timeout action will be taken. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 1200 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultMusicOnHold -The UseDefaultMusicOnHold parameter indicates that this Call Queue uses the default music on hold. This parameter cannot be specified together with MusicOnHoldAudioFileId. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WelcomeMusicAudioFileId -The WelcomeMusicAudioFileId parameter represents the audio file to play when callers are connected with the Call Queue. This is the unique identifier of the audio file. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PresenceBasedRouting -The PresenceBasedRouting parameter indicates whether or not presence based routing will be applied while call being routed to Call Queue agents. When set to False, calls will be routed to agents who have opted in to receive calls, regardless of their presence state. When set to True, opted-in agents will receive calls only when their presence state is Available. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Users -The Users parameter lets you add agents to the Call Queue. This parameter expects a list of user unique identifiers (GUID). - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue - -## NOTES - -## RELATED LINKS -[Create a Phone System Call Queue](https://support.office.com/en-us/article/Create-a-Phone-System-call-queue-67ccda94-1210-43fb-a25b-7b9785f8a061) diff --git a/skype/skype-ps/skype/New-CsCallViaWorkPolicy.md b/skype/skype-ps/skype/New-CsCallViaWorkPolicy.md index 43960ce027..cc14b7f786 100644 --- a/skype/skype-ps/skype/New-CsCallViaWorkPolicy.md +++ b/skype/skype-ps/skype/New-CsCallViaWorkPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscallviaworkpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-cscallviaworkpolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsCallViaWorkPolicy schema: 2.0.0 @@ -225,5 +225,3 @@ The New-CsCallViaWorkPolicy returns Microsoft.Rtc.Management.WritableConfig.Poli [Grant-CsCallViaWorkPolicy](Grant-CsCallViaWorkPolicy.md) [Get-CsCallViaWorkPolicy](Get-CsCallViaWorkPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsCallingLineIdentity.md b/skype/skype-ps/skype/New-CsCallingLineIdentity.md deleted file mode 100644 index b9207c2eb2..0000000000 --- a/skype/skype-ps/skype/New-CsCallingLineIdentity.md +++ /dev/null @@ -1,287 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscallinglineidentity -applicable: Skype for Business Online -title: New-CsCallingLineIdentity -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsCallingLineIdentity - -## SYNOPSIS -Use the New-CsCallingLineIdentity cmdlet to create a new Caller ID policy for your organization. - -## SYNTAX - -``` -New-CsCallingLineIdentity [-Tenant <Guid>] [-Description <String>] [-EnableUserOverride <Boolean>] - [-ServiceNumber <String>] [-CallingIDSubstitute <CallingIDSubstituteType>] - [-BlockIncomingPstnCallerID <Boolean>] [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -You can either change or block the Caller ID (also called a Calling Line ID) for a user. By default, the Skype for Business Online user's phone number can be seen when that user makes a call to a PSTN phone, or when a call comes in. You can create a Caller ID policy to provide an alternate displayed number, or to block any number from being displayed. - -Note: -- Identity must be unique. -- ServiceNumber must be a valid Service Number in the Skype for Business Online online telephone number inventory. -- If CallerIdSubstitute is given as "Service", then ServiceNumber cannot be empty. - - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsCallingLineIdentity -Identity Anonymous -Description "anonymous policy" -CallingIDSubstitute Anonymous -EnableUserOverride $false -``` - -This example creates a new Caller ID policy that sets the Caller ID to Anonymous. - -### -------------------------- Example 2 -------------------------- -``` -New-CsCallingLineIdentity -Identity "UKOrgAA" -CallingIdSubstitute "Service" -ServiceNumber "14258828080" -EnableUserOverride $false -Verbose -``` - -This example creates a new Caller ID policy that sets the Caller ID to a specified service number. - -### -------------------------- Example 3 -------------------------- -``` -New-CsCallingLineIdentity -Identity Anonymous -Description "anonymous policy" -CallingIDSubstitute Anonymous -EnableUserOverride $false -BlockIncomingPstnCallerID $true -``` - -This example creates a new Caller ID policy that blocks the incoming Caller ID. - -## PARAMETERS - -### -Identity -The Identity parameter identifies the Caller ID policy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockIncomingPstnCallerID -The BlockIncomingPstnCallerID switch determines whether to block the incoming Caller ID. The default value is false. - -The BlockIncomingPstnCallerID switch is specific to incoming calls from a PSTN caller to a user. If this is set to True and if this policy is assigned to a Lync user, then Caller ID for incoming calls is suppressed/anonymous. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallingIDSubstitute -PARAMVALUE: Anonymous | Service | LineUri - -The CallingIDSubstitute parameter lets you specify an alternate Caller ID. The default value is LineUri. - -```yaml -Type: CallingIDSubstituteType -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -The Description parameter briefly describes the Caller ID policy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableUserOverride -The EnableUserOverride switch lets the user override the Caller ID policy. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-<cmdlet>. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceNumber -The ServiceNumber parameter lets you add any valid service number for the CallingIdSubstitute. - -Note: Do not add '+' to the Service number. For example, if the Service number is +1425-xxx-xxxx then valid input is 1425xxxxxxx - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - -## OUTPUTS - -### None - -## NOTES - -## RELATED LINKS - -[Get-CsCallingLineIdentity](Get-CsCallingLineIdentity.md) - -[Grant-CsCallingLineIdentity](Grant-CsCallingLineIdentity.md) - -[Remove-CsCallingLineIdentity](Remove-CsCallingLineIdentity.md) - -[Set-CsCallingLineIdentity](Set-CsCallingLineIdentity.md) - diff --git a/skype/skype-ps/skype/New-CsCdrConfiguration.md b/skype/skype-ps/skype/New-CsCdrConfiguration.md index da1c62d592..68b89ad829 100644 --- a/skype/skype-ps/skype/New-CsCdrConfiguration.md +++ b/skype/skype-ps/skype/New-CsCdrConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscdrconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cscdrconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsCdrConfiguration schema: 2.0.0 @@ -291,5 +291,3 @@ Creates instances of the Microsoft.Rtc.Management.WritableConfig.Settings.CallDe [Remove-CsCdrConfiguration](Remove-CsCdrConfiguration.md) [Set-CsCdrConfiguration](Set-CsCdrConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsClientPolicy.md b/skype/skype-ps/skype/New-CsClientPolicy.md index 556ff21a69..38bddfb4fe 100644 --- a/skype/skype-ps/skype/New-CsClientPolicy.md +++ b/skype/skype-ps/skype/New-CsClientPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclientpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csclientpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsClientPolicy schema: 2.0.0 manager: bulenteg @@ -79,7 +79,7 @@ If you need to make changes to the global policy, use the Set-CsClientPolicy cmd Keep in mind that client policies differ from many other policies in that most of the policy settings do not have default values. -The following parameters are not applicable to Skype for Business Online: AddressBookAvailability, AsJob, AttendantSafeTransfer, AutoDiscoveryRetryInterval, BlockConversationFromFederatedContacts, CalendarStatePublicationInterval, ConferenceIMIdleTimeout, CustomizedHelpUrl, CustomLinkInErrorMessages, CustomStateUrl, Description, DGRefreshInterval, DisableContactCardOrganizationTab, DisableFederatedPromptDisplayName, DisableFeedsTab, DisableMeetingSubjectAndLocation, DisableOneNote12Integration, DisableOnlineContextualSearch, DisablePhonePresence, DisablePICPromptDisplayName, EnableEventLogging, EnableExchangeContactsFolder, EnableExchangeDelegateSync, EnableFullScreenVideo, EnableHighPerformanceConferencingAppSharing, EnableHighPerformanceP2PAppSharing, EnableMediaRedirection, EnableMeetingEngagement, EnableNotificationForNewSubscribers, EnableOnlineFeedback, EnableOnlineFeedbackScreenshots, EnableSQMData, EnableTracing, EnableViewBasedSubscriptionMode, EnableVOIPCallDefault, Force, HelpEnvironment, Identity, IMLatencyErrorThreshold, IMLatencySpinnerDelay, InMemory, MAPIPollInterval, MaximumDGsAllowedInContactList, MaximumNumberOfContacts, MaxPhotoSizeKB, P2PAppSharingEncryption, PipelineVariable, PolicyEntry, PublicationBatchDelay, RateMyCallAllowCustomUserFeedback, RequireContentPin, SearchPrefixFlags, SPSearchCenterExternalURL, SPSearchCenterInternalURL, SPSearchExternalURL, SPSearchInternalURL, SupportModernFilePicker, TabURL, TelemetryTier, Tenant, and WebServicePollInterval +The following parameters are not applicable to Skype for Business Online: AddressBookAvailability, AttendantSafeTransfer, AutoDiscoveryRetryInterval, BlockConversationFromFederatedContacts, CalendarStatePublicationInterval, ConferenceIMIdleTimeout, CustomizedHelpUrl, CustomLinkInErrorMessages, CustomStateUrl, Description, DGRefreshInterval, DisableContactCardOrganizationTab, DisableFederatedPromptDisplayName, DisableFeedsTab, DisableMeetingSubjectAndLocation, DisableOneNote12Integration, DisableOnlineContextualSearch, DisablePhonePresence, DisablePICPromptDisplayName, EnableEventLogging, EnableExchangeContactsFolder, EnableExchangeDelegateSync, EnableFullScreenVideo, EnableHighPerformanceConferencingAppSharing, EnableHighPerformanceP2PAppSharing, EnableMediaRedirection, EnableMeetingEngagement, EnableNotificationForNewSubscribers, EnableOnlineFeedback, EnableOnlineFeedbackScreenshots, EnableSQMData, EnableTracing, EnableViewBasedSubscriptionMode, EnableVOIPCallDefault, Force, HelpEnvironment, Identity, IMLatencyErrorThreshold, IMLatencySpinnerDelay, InMemory, MAPIPollInterval, MaximumDGsAllowedInContactList, MaximumNumberOfContacts, MaxPhotoSizeKB, P2PAppSharingEncryption, PipelineVariable, PolicyEntry, PublicationBatchDelay, RateMyCallAllowCustomUserFeedback, RequireContentPin, SearchPrefixFlags, SPSearchCenterExternalURL, SPSearchCenterInternalURL, SPSearchExternalURL, SPSearchInternalURL, SupportModernFilePicker, TabURL, TelemetryTier, Tenant, and WebServicePollInterval ## EXAMPLES @@ -1353,11 +1353,9 @@ To search only last name, first name, and display name you would construct this 1110000 After the binary value has been constructed, it must then be converted to a decimal value before being assigned to SearchPrefixFlags. -To convert a binary number to a decimal number, you can use the a Windows PowerShell command similar to this: - -`\[Convert\]::ToInt32("1110111", 2)` - +To convert a binary number to a decimal number, you can use a Windows PowerShell command similar to this: +`[Convert]::ToInt32("1110111", 2)` ```yaml Type: UInt16 @@ -2114,21 +2112,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` @@ -2160,5 +2143,3 @@ The New-CsClientPolicy cmdlet creates new instances of the Microsoft.Rtc.Managem [Remove-CsClientPolicy](Remove-CsClientPolicy.md) [Set-CsClientPolicy](Set-CsClientPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsClientPolicyEntry.md b/skype/skype-ps/skype/New-CsClientPolicyEntry.md index 3e27fd372b..4fb43fb573 100644 --- a/skype/skype-ps/skype/New-CsClientPolicyEntry.md +++ b/skype/skype-ps/skype/New-CsClientPolicyEntry.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclientpolicyentry +online version: https://learn.microsoft.com/powershell/module/skype/new-csclientpolicyentry applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsClientPolicyEntry schema: 2.0.0 @@ -174,4 +174,3 @@ The New-CsClientPolicyEntry cmdlet creates new instances of the Microsoft.Rtc.Ma [New-CsClientPolicy](New-CsClientPolicy.md) [Set-CsClientPolicy](Set-CsClientPolicy.md) - diff --git a/skype/skype-ps/skype/New-CsClientVersionConfiguration.md b/skype/skype-ps/skype/New-CsClientVersionConfiguration.md index c948acfd54..a361347d9f 100644 --- a/skype/skype-ps/skype/New-CsClientVersionConfiguration.md +++ b/skype/skype-ps/skype/New-CsClientVersionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclientversionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csclientversionconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsClientVersionConfiguration schema: 2.0.0 @@ -268,5 +268,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Policy.Clie [Remove-CsClientVersionConfiguration](Remove-CsClientVersionConfiguration.md) [Set-CsClientVersionConfiguration](Set-CsClientVersionConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsClientVersionPolicy.md b/skype/skype-ps/skype/New-CsClientVersionPolicy.md index f24b62fbf8..d8e270a440 100644 --- a/skype/skype-ps/skype/New-CsClientVersionPolicy.md +++ b/skype/skype-ps/skype/New-CsClientVersionPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclientversionpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csclientversionpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsClientVersionPolicy schema: 2.0.0 @@ -262,4 +262,3 @@ The New-CsClientVersionPolicy cmdlet creates new instances of the Microsoft.Rtc. [Remove-CsClientVersionPolicy](Remove-CsClientVersionPolicy.md) [Set-CsClientVersionPolicy](Set-CsClientVersionPolicy.md) - diff --git a/skype/skype-ps/skype/New-CsClientVersionPolicyRule.md b/skype/skype-ps/skype/New-CsClientVersionPolicyRule.md index 8a56e3445a..2cb0dc194e 100644 --- a/skype/skype-ps/skype/New-CsClientVersionPolicyRule.md +++ b/skype/skype-ps/skype/New-CsClientVersionPolicyRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclientversionpolicyrule +online version: https://learn.microsoft.com/powershell/module/skype/new-csclientversionpolicyrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsClientVersionPolicyRule schema: 2.0.0 @@ -90,7 +90,7 @@ Client version policies enforced in your organization do not override the client ### -------------------------- EXAMPLE 1 -------------------------- ``` -$x = \[guid\]::NewGuid() +$x = [guid]::NewGuid() New-CsClientVersionPolicyRule -Parent "site:Redmond" -RuleId $x -MajorVersion 4 -UserAgent InHouse ``` @@ -108,7 +108,7 @@ In this case, the UserAgent parameter represents an in-house client application. ### -------------------------- EXAMPLE 2 -------------------------- ``` -$x = \[guid\]::NewGuid() +$x = [guid]::NewGuid() $z = New-CsClientVersionPolicyRule -Parent "site:Redmond" -RuleId $x -InMemory @@ -407,7 +407,7 @@ Accept wildcard characters: False Globally unique identifier (GUID) for the rule. In Windows PowerShell, you can create a GUID by using the following command: -`$x = \[guid\]::NewGuid()` +`$x = [guid]::NewGuid()` ```yaml Type: String @@ -556,5 +556,3 @@ The New-CsClientVersionPolicyRule cmdlet creates new instances of Microsoft.Rtc. [Remove-CsClientVersionPolicyRule](Remove-CsClientVersionPolicyRule.md) [Set-CsClientVersionPolicyRule](Set-CsClientVersionPolicyRule.md) - - diff --git a/skype/skype-ps/skype/New-CsCloudCallDataConnectorConfiguration.md b/skype/skype-ps/skype/New-CsCloudCallDataConnectorConfiguration.md index 5ae5263461..9508f13493 100644 --- a/skype/skype-ps/skype/New-CsCloudCallDataConnectorConfiguration.md +++ b/skype/skype-ps/skype/New-CsCloudCallDataConnectorConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscloudcalldataconnectorconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cscloudcalldataconnectorconfiguration applicable: Skype for Business Server 2019 title: New-CsCloudCallDataConnectorConfiguration schema: 2.0.0 @@ -116,7 +116,7 @@ Accept wildcard characters: False ``` ### -InMemory -Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-<cmdlet>. +Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-\<cmdlet\>. ```yaml Type: SwitchParameter diff --git a/skype/skype-ps/skype/New-CsClsConfiguration.md b/skype/skype-ps/skype/New-CsClsConfiguration.md index 7a75aa82c8..123753063b 100644 --- a/skype/skype-ps/skype/New-CsClsConfiguration.md +++ b/skype/skype-ps/skype/New-CsClsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csclsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsClsConfiguration schema: 2.0.0 @@ -494,4 +494,3 @@ The New-CsClsConfiguration cmdlet creates new instances of the icrosoft.Rtc.Mana [Remove-CsClsConfiguration](Remove-CsClsConfiguration.md) [Set-CsClsConfiguration](Set-CsClsConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsClsProvider.md b/skype/skype-ps/skype/New-CsClsProvider.md index baa432885a..33da9f6a09 100644 --- a/skype/skype-ps/skype/New-CsClsProvider.md +++ b/skype/skype-ps/skype/New-CsClsProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclsprovider +online version: https://learn.microsoft.com/powershell/module/skype/new-csclsprovider applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -220,4 +220,3 @@ The New-CsClsProvider cmdlet creates new instances of the Microsoft.Rtc.Manageme [New-CsClsScenario](New-CsClsScenario.md) [Set-CsClsScenario](Set-CsClsScenario.md) - diff --git a/skype/skype-ps/skype/New-CsClsRegion.md b/skype/skype-ps/skype/New-CsClsRegion.md index 5852430fde..e25b134904 100644 --- a/skype/skype-ps/skype/New-CsClsRegion.md +++ b/skype/skype-ps/skype/New-CsClsRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclsregion +online version: https://learn.microsoft.com/powershell/module/skype/new-csclsregion applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -271,6 +271,3 @@ The New-CsClsRegion cmdlet creates new instances of the Microsoft.Rtc.Management [Remove-CsClsRegion](Remove-CsClsRegion.md) [Set-CsClsRegion](Set-CsClsRegion.md) - - - diff --git a/skype/skype-ps/skype/New-CsClsScenario.md b/skype/skype-ps/skype/New-CsClsScenario.md index 56ca60f412..c8ab273146 100644 --- a/skype/skype-ps/skype/New-CsClsScenario.md +++ b/skype/skype-ps/skype/New-CsClsScenario.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclsscenario +online version: https://learn.microsoft.com/powershell/module/skype/new-csclsscenario applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -256,6 +256,3 @@ The New-CsClsScenario cmdlet creates new instances of the Microsoft.Rtc.Manageme ## NOTES ## RELATED LINKS - - - diff --git a/skype/skype-ps/skype/New-CsClsSecurityGroup.md b/skype/skype-ps/skype/New-CsClsSecurityGroup.md index ab36d84ad4..6e4d1cada3 100644 --- a/skype/skype-ps/skype/New-CsClsSecurityGroup.md +++ b/skype/skype-ps/skype/New-CsClsSecurityGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csclssecuritygroup +online version: https://learn.microsoft.com/powershell/module/skype/new-csclssecuritygroup applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -241,4 +241,3 @@ The New-CsClsSecurityGroup cmdlet creates new instances of the Microsoft.Rtc.Man [Remove-CsClsSecurityGroup](Remove-CsClsSecurityGroup.md) [Set-CsClsSecurityGroup](Set-CsClsSecurityGroup.md) - diff --git a/skype/skype-ps/skype/New-CsCommonAreaPhone.md b/skype/skype-ps/skype/New-CsCommonAreaPhone.md index f2b574768d..948f235f55 100644 --- a/skype/skype-ps/skype/New-CsCommonAreaPhone.md +++ b/skype/skype-ps/skype/New-CsCommonAreaPhone.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscommonareaphone +online version: https://learn.microsoft.com/powershell/module/skype/new-cscommonareaphone applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -317,6 +317,3 @@ The New-CsCommonAreaPhone cmdlet creates new instances of the Microsoft.Rtc.Mana [Remove-CsCommonAreaPhone](Remove-CsCommonAreaPhone.md) [Set-CsCommonAreaPhone](Set-CsCommonAreaPhone.md) - - - diff --git a/skype/skype-ps/skype/New-CsConferenceDirectory.md b/skype/skype-ps/skype/New-CsConferenceDirectory.md index 7a4b7fc048..4a9c8747e0 100644 --- a/skype/skype-ps/skype/New-CsConferenceDirectory.md +++ b/skype/skype-ps/skype/New-CsConferenceDirectory.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csconferencedirectory +online version: https://learn.microsoft.com/powershell/module/skype/new-csconferencedirectory applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -158,6 +158,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Ps [Move-CsConferenceDirectory](Move-CsConferenceDirectory.md) [Remove-CsConferenceDirectory](Remove-CsConferenceDirectory.md) - - - diff --git a/skype/skype-ps/skype/New-CsConferencingConfiguration.md b/skype/skype-ps/skype/New-CsConferencingConfiguration.md index 4984c7cb0b..dd911eb816 100644 --- a/skype/skype-ps/skype/New-CsConferencingConfiguration.md +++ b/skype/skype-ps/skype/New-CsConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -642,6 +642,3 @@ The New-CsConferencingConfiguration cmdlet creates new instances of the Microsof [Remove-CsConferencingConfiguration](Remove-CsConferencingConfiguration.md) [Set-CsConferencingConfiguration](Set-CsConferencingConfiguration.md) - - - diff --git a/skype/skype-ps/skype/New-CsConferencingPolicy.md b/skype/skype-ps/skype/New-CsConferencingPolicy.md index 721f864ed6..08fab2b313 100644 --- a/skype/skype-ps/skype/New-CsConferencingPolicy.md +++ b/skype/skype-ps/skype/New-CsConferencingPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csconferencingpolicy -applicable: Skype for Business Online, Skype for Business Server 2019, Skype for Business Server 2015, Lync Server 2013, Lync Server 2010, +online version: https://learn.microsoft.com/powershell/module/skype/new-csconferencingpolicy +applicable: Skype for Business Server 2019, Skype for Business Server 2015, Lync Server 2013, Lync Server 2010, schema: 2.0.0 manager: bulenteg author: tomkau @@ -55,7 +55,7 @@ In Skype for Business Online and Skype for Business Server, conferences are mana - In Skype for Business Online, conferencing policy is managed on a per-user basis. Skype for Business Online provides several built-in conferencing policy instances, and if needed administrators, can create their own policy instances as well, using the New-CsConferencingPolicy cmdlet. - In Skype for Business Server, conferencing policies can be created at either the site or the per-user scope. If you need to modify property values of the global conferencing policy, use the Set-CsConferencingPolicy cmdlet. -The following parameters are not applicable to Skype for Business Online: ApplicationSharingMode, AsJob, AudioBitRateKb, Description, EnableMultiViewJoin, EnableOnlineMeetingPromptForLyncResources, EnableReliableConferenceDeletion, FileTransferBitRateKb, Force, Identity, InMemory, MaxMeetingSize, MaxVideoConferenceResolution, PipelineVariable, Tenant, and TotalReceiveVideoBitRateKb. +The following parameters are not applicable to Skype for Business Online: ApplicationSharingMode, AudioBitRateKb, Description, EnableMultiViewJoin, EnableOnlineMeetingPromptForLyncResources, EnableReliableConferenceDeletion, FileTransferBitRateKb, Force, Identity, InMemory, MaxMeetingSize, MaxVideoConferenceResolution, PipelineVariable, Tenant, and TotalReceiveVideoBitRateKb. @@ -1077,21 +1077,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -1121,6 +1106,3 @@ The New-CsConferencingPolicy cmdlet creates a new instance of the Microsoft.Rtc. [Remove-CsConferencingPolicy](Remove-CsConferencingPolicy.md) [Set-CsConferencingPolicy](Set-CsConferencingPolicy.md) - - - diff --git a/skype/skype-ps/skype/New-CsCpsConfiguration.md b/skype/skype-ps/skype/New-CsCpsConfiguration.md index a1a5b9bf03..dfaf405eee 100644 --- a/skype/skype-ps/skype/New-CsCpsConfiguration.md +++ b/skype/skype-ps/skype/New-CsCpsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cscpsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cscpsconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 schema: 2.0.0 manager: rogupta @@ -273,5 +273,3 @@ This cmdlet creates an object of type Microsoft.Rtc.Management.WritableConfig.Se [Get-CsCpsConfiguration](Get-CsCpsConfiguration.md) [Set-CsCallParkServiceMusicOnHoldFile](Set-CsCallParkServiceMusicOnHoldFile.md) - - diff --git a/skype/skype-ps/skype/New-CsDeviceUpdateConfiguration.md b/skype/skype-ps/skype/New-CsDeviceUpdateConfiguration.md index c00d5d84d6..e0f256355d 100644 --- a/skype/skype-ps/skype/New-CsDeviceUpdateConfiguration.md +++ b/skype/skype-ps/skype/New-CsDeviceUpdateConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdeviceupdateconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csdeviceupdateconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDeviceUpdateConfiguration schema: 2.0.0 diff --git a/skype/skype-ps/skype/New-CsDiagnosticConfiguration.md b/skype/skype-ps/skype/New-CsDiagnosticConfiguration.md index f4b3b34508..db23830811 100644 --- a/skype/skype-ps/skype/New-CsDiagnosticConfiguration.md +++ b/skype/skype-ps/skype/New-CsDiagnosticConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdiagnosticconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csdiagnosticconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDiagnosticConfiguration schema: 2.0.0 diff --git a/skype/skype-ps/skype/New-CsDiagnosticHeaderConfiguration.md b/skype/skype-ps/skype/New-CsDiagnosticHeaderConfiguration.md index 8c9593b067..7906c3c207 100644 --- a/skype/skype-ps/skype/New-CsDiagnosticHeaderConfiguration.md +++ b/skype/skype-ps/skype/New-CsDiagnosticHeaderConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdiagnosticheaderconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csdiagnosticheaderconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDiagnosticHeaderConfiguration schema: 2.0.0 @@ -259,5 +259,3 @@ The New-CsDiagnosticHeaderConfiguration cmdlet creates new instances of the Micr [Remove-CsDiagnosticHeaderConfiguration](Remove-CsDiagnosticHeaderConfiguration.md) [Set-CsDiagnosticHeaderConfiguration](Set-CsDiagnosticHeaderConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsDiagnosticsFilter.md b/skype/skype-ps/skype/New-CsDiagnosticsFilter.md index b1c80e4fe0..d2f329786f 100644 --- a/skype/skype-ps/skype/New-CsDiagnosticsFilter.md +++ b/skype/skype-ps/skype/New-CsDiagnosticsFilter.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdiagnosticsfilter +online version: https://learn.microsoft.com/powershell/module/skype/new-csdiagnosticsfilter applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDiagnosticsFilter schema: 2.0.0 @@ -26,6 +26,7 @@ This cmdlet was introduced in Lync Server 2010. New-CsDiagnosticsFilter [-Enabled <Boolean>] [-ExcludeConferenceMessages <Boolean>] [-ExcludePresenceNotifications <Boolean>] [-ExcludeRegisterMessages <Boolean>] [-Fqdn <PSListModifier>] [-Uri <PSListModifier>] [-ExcludeSubscribeMessages <Boolean>] [-ExcludeSuccessfulRequests <Boolean>] + [-ExcludeMidDialogRequests <Boolean>] [-ExcludeTypingNotifications <Boolean>] [<CommonParameters>] ``` @@ -53,7 +54,7 @@ After creating one of these virtual filters, you will then need to use either th ## EXAMPLES -### -------------------------- EXAMPLE 1 -------------------------- +### EXAMPLE 1 ``` $x = New-CsDiagnosticsFilter -Fqdn "fabrikam.com" -Enabled $False @@ -71,7 +72,7 @@ In this case, any existing values in the Filter property will be replaced by the -### -------------------------- EXAMPLE 2 -------------------------- +### EXAMPLE 2 ``` $x = New-CsDiagnosticsFilter -Fqdn "fabrikam.com","contoso.com" -Enabled $False @@ -235,6 +236,36 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ExcludeMidDialogRequests +If set to True, information about mid-dialog SIP requests will not be recorded in the log files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeTypingNotifications +If set to True, information about typing notifications SIP messages will not be recorded in the log files. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216).` @@ -257,5 +288,3 @@ The New-CsDiagnosticsFilter cmdlet creates new instances of the Microsoft.Rtc.Ma [New-CsDiagnosticConfiguration](New-CsDiagnosticConfiguration.md) [Set-CsDiagnosticConfiguration](Set-CsDiagnosticConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsDialInConferencingAccessNumber.md b/skype/skype-ps/skype/New-CsDialInConferencingAccessNumber.md index 770f6e4cd2..96f6b14689 100644 --- a/skype/skype-ps/skype/New-CsDialInConferencingAccessNumber.md +++ b/skype/skype-ps/skype/New-CsDialInConferencingAccessNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdialinconferencingaccessnumber +online version: https://learn.microsoft.com/powershell/module/skype/new-csdialinconferencingaccessnumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDialInConferencingAccessNumber schema: 2.0.0 @@ -391,5 +391,3 @@ The New-CsDialInConferencingAccessNumber cmdlet creates new instances of the Mic [Remove-CsDialInConferencingAccessNumber](Remove-CsDialInConferencingAccessNumber.md) [Set-CsDialInConferencingAccessNumber](Set-CsDialInConferencingAccessNumber.md) - - diff --git a/skype/skype-ps/skype/New-CsDialInConferencingConfiguration.md b/skype/skype-ps/skype/New-CsDialInConferencingConfiguration.md index f6006eb803..d05fb34422 100644 --- a/skype/skype-ps/skype/New-CsDialInConferencingConfiguration.md +++ b/skype/skype-ps/skype/New-CsDialInConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdialinconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csdialinconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDialInConferencingConfiguration schema: 2.0.0 @@ -280,5 +280,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Di [Remove-CsDialInConferencingConfiguration](Remove-CsDialInConferencingConfiguration.md) [Set-CsDialInConferencingConfiguration](Set-CsDialInConferencingConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsDialInConferencingDtmfConfiguration.md b/skype/skype-ps/skype/New-CsDialInConferencingDtmfConfiguration.md index 4179710641..80d7835196 100644 --- a/skype/skype-ps/skype/New-CsDialInConferencingDtmfConfiguration.md +++ b/skype/skype-ps/skype/New-CsDialInConferencingDtmfConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdialinconferencingdtmfconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csdialinconferencingdtmfconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDialInConferencingDtmfConfiguration schema: 2.0.0 @@ -376,5 +376,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Di [Remove-CsDialInConferencingDtmfConfiguration](Remove-CsDialInConferencingDtmfConfiguration.md) [Set-CsDialInConferencingDtmfConfiguration](Set-CsDialInConferencingDtmfConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsDialPlan.md b/skype/skype-ps/skype/New-CsDialPlan.md index 132bfaca65..aff1a6f077 100644 --- a/skype/skype-ps/skype/New-CsDialPlan.md +++ b/skype/skype-ps/skype/New-CsDialPlan.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csdialplan +online version: https://learn.microsoft.com/powershell/module/skype/new-csdialplan applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsDialPlan schema: 2.0.0 @@ -395,4 +395,3 @@ This cmdlet creates an object of type Microsoft.Rtc.Management.WritableConfig.Po [Remove-CsVoiceNormalizationRule](Remove-CsVoiceNormalizationRule.md) [Get-CsVoiceNormalizationRule](Get-CsVoiceNormalizationRule.md) - diff --git a/skype/skype-ps/skype/New-CsEdgeDomainPattern.md b/skype/skype-ps/skype/New-CsEdgeDomainPattern.md deleted file mode 100644 index 062a96c066..0000000000 --- a/skype/skype-ps/skype/New-CsEdgeDomainPattern.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csedgedomainpattern -applicable: Skype for Business Online -title: New-CsEdgeDomainPattern -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsEdgeDomainPattern - -## SYNOPSIS -Used to specify a domain that will be added or removed from the set of domains enabled for federation or the set of domains disabled for federation. -You must use the New-CsEdgeDomainPattern cmdlet when modifying the allowed or blocked domain lists. -String values (such as "fabrikam.com") cannot be directly passed to the cmdlets used to manage either of these lists. - -## SYNTAX - -``` -New-CsEdgeDomainPattern -Domain <String> [<CommonParameters>] -``` - -## DESCRIPTION -Federation is a service that enables users to exchange IM and presence information with users from other domains. -With Skype for Business Online, administrators can use the federation configuration settings to govern: - -Whether or not users can communicate with people from other domains and, if so, which domains they are allowed to communicate with. - -Whether or not users can communicate with people who have accounts on public IM and presence providers such as Windows Live, AOL, and Yahoo. - -Federation is managed, in part, by using allowed domain and blocked domain lists. -The allowed domain list specifies the domains that users are allowed to communicate with; the blocked domain list specifies the domains that users are not allowed to communicate with. -By default, users can communicate with any domain that does not appear on the blocked list. -However, administrators can modify this default setting and limit communication to domains that are on the allowed domains list. - -Skype for Business Online does not allow you to directly modify the allowed list or the blocked list; for example, you cannot use a command similar to this one, which passes a string value representing a domain name to the blocked domains list: - -`Set-CsTenantFederationConfiguration -BlockedDomains "fabrikam.com"` - -Instead, you must create a domain object by using the New-CsEdgeDomainPattern cmdlet, store that domain object in a variable (in this example, $x), then pass the variable name to the blocked domains list: - -`$x = New-CsEdgeDomainPattern -Domain "fabrikam.com"` - -`Set-CsTenantFederationConfiguration -BlockedDomains $x` - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" - -Set-CsTenantFederationConfiguration -BlockedDomains $x -``` - -Example 1 demonstrates how you can assign a single domain to the blocked domains list for a specified tenant. -To do this, the first command in the example creates a domain object for the domain fabrikam.com; this is done by calling the New-CsEdgeDomainPattern cmdlet and by saving the resulting domain object in a variable named $x. -The second command then uses the Set-CsTenantFederationConfiguration cmdlet and the BlockedDomains parameter to configure fabrikam.com as the only domain blocked by the current tenant. - - -## PARAMETERS - -### -Domain -Fully qualified domain name of the domain to be added to the allow list. -For example: - -`-Domain "fabrikam.com"` - -Note that you cannot use wildcards when specifying a domain name. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### -None. -The New-CsEdgeDomainPattern cmdlet does not accept pipelined input. - -## OUTPUTS - -### -The New-CsEdgeDomainPattern cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.DomainPattern object. - -## NOTES - -## RELATED LINKS - -[Set-CsTenantFederationConfiguration](Set-CsTenantFederationConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsEmergencyNumber.md b/skype/skype-ps/skype/New-CsEmergencyNumber.md index 37fd688295..f871386781 100644 --- a/skype/skype-ps/skype/New-CsEmergencyNumber.md +++ b/skype/skype-ps/skype/New-CsEmergencyNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csemergencynumber +online version: https://learn.microsoft.com/powershell/module/skype/new-csemergencynumber applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsEmergencyNumber schema: 2.0.0 @@ -98,6 +98,6 @@ This cmdlet supports the common parameters: `-Debug, -ErrorAction, -ErrorVariabl ## NOTES ## RELATED LINKS -[New-CsLocationPolicy](https://docs.microsoft.com/powershell/module/skype/new-cslocationpolicy?view=skype-ps) +[New-CsLocationPolicy](https://learn.microsoft.com/powershell/module/skype/new-cslocationpolicy?view=skype-ps) -[Set-CsLocationPolicy](https://docs.microsoft.com/powershell/module/skype/set-cslocationpolicy?view=skype-ps) +[Set-CsLocationPolicy](https://learn.microsoft.com/powershell/module/skype/set-cslocationpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsExUmContact.md b/skype/skype-ps/skype/New-CsExUmContact.md index b4483ba104..a9107cd958 100644 --- a/skype/skype-ps/skype/New-CsExUmContact.md +++ b/skype/skype-ps/skype/New-CsExUmContact.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csexumcontact +online version: https://learn.microsoft.com/powershell/module/skype/new-csexumcontact applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsExUmContact schema: 2.0.0 @@ -264,5 +264,3 @@ Creates an object of type Microsoft.Rtc.Management.ADConnect.Schema.OCSADExUmCon [Move-CsExUmContact](Move-CsExUmContact.md) [Get-CsHostedVoicemailPolicy](Get-CsHostedVoicemailPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsExtendedTest.md b/skype/skype-ps/skype/New-CsExtendedTest.md index 8701335fab..0b33391159 100644 --- a/skype/skype-ps/skype/New-CsExtendedTest.md +++ b/skype/skype-ps/skype/New-CsExtendedTest.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csextendedtest +online version: https://learn.microsoft.com/powershell/module/skype/new-csextendedtest applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsExtendedTest schema: 2.0.0 @@ -140,5 +140,3 @@ The New-CsExtendedTest cmdlet creates new instances of the Microsoft.Rtc.Managem [New-CsWatcherNodeConfiguration](New-CsWatcherNodeConfiguration.md) [Set-CsWatcherNodeConfiguration](Set-CsWatcherNodeConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsExternalAccessPolicy.md b/skype/skype-ps/skype/New-CsExternalAccessPolicy.md index 148ab0d3fe..0e86942e9c 100644 --- a/skype/skype-ps/skype/New-CsExternalAccessPolicy.md +++ b/skype/skype-ps/skype/New-CsExternalAccessPolicy.md @@ -1,10 +1,9 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csexternalaccesspolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csexternalaccesspolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsExternalAccessPolicy schema: 2.0.0 -manager: bulenteg author: tomkau ms.author: tomkau ms.reviewer: rogupta @@ -13,20 +12,24 @@ ms.reviewer: rogupta # New-CsExternalAccessPolicy ## SYNOPSIS +> [!NOTE] +> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter EnablePublicCloudAccess can no longer be used. Enables you to create a new external access policy. -External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as MSN; and, 3) access Skype for Business Server over the Internet, without having to log on to your internal network. -This cmdlet was introduced in Lync Server 2010. +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services](/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype; and, 5) communicate with people who are using Teams with an account that's not managed by an organization. + +This cmdlet was introduced in Lync Server 2010. +For information about external access in Microsoft Teams, see [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) and [Teams and Skype interoperability](/microsoftteams/teams-skype-interop) for specific details. ## SYNTAX -``` -New-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] - [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>] - [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableOutsideAccess <Boolean>] [-Identity] <XdsIdentity> +```powershell +New-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>] + [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableTeamsConsumerAccess <Boolean>] [-EnableTeamsConsumerInbound <Boolean>] [-EnableOutsideAccess <Boolean>] [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] + ``` ## DESCRIPTION @@ -38,18 +41,19 @@ That might be sufficient to meet your communication needs. If it doesn't meet your needs you can use external access policies to extend the ability of your users to communicate and collaborate. External access policies can grant (or revoke) the ability of your users to do any or all of the following: -1. -Communicate with people who have SIP accounts with a federated organization. +1. Communicate with people who have SIP accounts with a federated organization. Note that enabling federation alone will not provide users with this capability. Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. -2. -Communicate with people who have SIP accounts with a public instant messaging service such as MSN. +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration). -3. -Access Skype for Business Server over the Internet, without having to first log on to your internal network. +3. Access Skype for Business Server over the Internet, without having to first log on to your internal network. This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. +4. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. + +5. (Microsoft Teams Only) Communicate with people who are using Teams with an account that's not managed by an organization. This policy only applies if Teams Consumer Federation has been enabled at the tenant level using the cmdlet [Set-CsTenantFederationConfiguration](/powershell/module/skype/set-cstenantfederationconfiguration) or Teams Admin Center under the External Access setting. + When you install Skype for Business Server, a global external access policy is automatically created for you. In addition to the global policy, you can also create custom external access policies at either the site or the per-user scope. If you create an external access policy at the site scope, that policy will automatically be assigned to the site upon creation. @@ -60,11 +64,10 @@ New external access policies can be created by using the New-CsExternalAccessPol Note that these policies can only be created at the site or the per-user scope; you cannot create a new policy at the global scope. In addition, you can have only one external access policy per site: if the Redmond site already has been assigned an external access policy you cannot create a second policy for the site. -The following parameters are not applicable to Skype for Business Online: AsJob, Description, EnableXmppAccess, Force, Identity, InMemory, PipelineVariable, and Tenant +The following parameters are not applicable to Skype for Business Online/Microsoft Teams: Description, EnableXmppAccess, Force, Identity, InMemory, PipelineVariable, and Tenant ## EXAMPLES - ### -------------------------- EXAMPLE 1 -------------------------- ``` New-CsExternalAccessPolicy -Identity site:Redmond -EnableFederationAccess $True -EnableOutsideAccess $True @@ -73,26 +76,38 @@ New-CsExternalAccessPolicy -Identity site:Redmond -EnableFederationAccess $True The command shown in Example 1 creates a new external access policy that has the Identity site:Redmond; upon creation, this policy will automatically be assigned to the Redmond site. Note that this new policy sets both the EnableFederationAccess and the EnableOutsideAccess properties to True. +### -------------------------- Example 2 ------------------------ +``` +Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $true +New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed -EnableAcsFederationAccess $false +``` + +In this example, the Global policy is updated to allow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation disabled and which can then be assigned to selected users for which Team-ACS federation will not be allowed. + +### -------------------------- Example 3 ------------------------ +``` +New-CsExternalAccessPolicy -Identity site:Redmond -EnableTeamsConsumerAccess $True -EnableTeamsConsumerInbound $False +``` +The command shown in Example 3 creates a new external access policy that has the Identity site:Redmond; upon creation, this policy will automatically be assigned to the Redmond site. +Note that this new policy enables communication with people using Teams with an account that's not managed by an organization and limits this to only be initiated by people in your organization. This means that people using Teams with an account that's not managed by an organization will not be able to discover or start a conversation with people with this policy assigned. -### -------------------------- EXAMPLE 2 -------------------------- +### -------------------------- EXAMPLE 4 -------------------------- ``` $x = New-CsExternalAccessPolicy -Identity RedmondAccessPolicy -InMemory $x.EnableFederationAccess = $True -$x.EnablePublicCloudAccess = $True - $x.EnableOutsideAccess = $True Set-CsExternalAccessPolicy -Instance $x ``` -Example 2 demonstrates the use of the InMemory parameter; this parameter enables you to create an in-memory-only instance of an external access policy. +Example 4 demonstrates the use of the InMemory parameter; this parameter enables you to create an in-memory-only instance of an external access policy. After it has been created, you can modify the in-memory-only instance, then use the Set-CsExternalAccessPolicy cmdlet to transform the virtual policy into a real external access policy. To do this, the first command in the example uses the New-CsExternalAccessPolicy cmdlet and the InMemory parameter to create a virtual policy with the Identity RedmondAccessPolicy; this virtual policy is stored in a variable named $x. -The next three commands are used to modify three properties of the virtual policy: EnableFederationAccess, EnablePublicCloudAccess, and the EnableOutsideAccess. +The next three commands are used to modify two properties of the virtual policy: EnableFederationAccess and the EnableOutsideAccess. Finally, the last command uses the Set-CsExternalAccessPolicy cmdlet to create an actual per-user external access policy with the Identity RedmondAccessPolicy. If you do not call the Set-CsExternalAccessPolicy cmdlet, then the virtual policy will disappear as soon as you end your Windows PowerShell session or delete the variable $x. Should that happen, an external access policy with the Identity RedmondAccessPolicy will never be created. @@ -113,7 +128,7 @@ If you need to make changes to an existing policy, use the Set-CsExternalAccessP ```yaml Type: XdsIdentity Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: True @@ -130,7 +145,7 @@ For example, the Description might include information about the users the polic ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -142,47 +157,90 @@ Accept wildcard characters: False ### -EnableFederationAccess Indicates whether the user is allowed to communicate with people who have SIP accounts with a federated organization. -The default value is False. +Read [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` -### -EnableOutsideAccess -Indicates whether the user is allowed to connect to Skype for Business Server over the Internet, without logging on to the organization's internal network. -The default value is False. +### -EnableTeamsConsumerAccess +(Microsoft Teams Only) Indicates whether the user is allowed to communicate with people who have who are using Teams with an account that's not managed by an organization. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsConsumerInbound +(Microsoft Teams Only) Indicates whether the user is allowed to be discoverable by people who are using Teams with an account that's not managed by an organization. It also controls if people who are using Teams with an account that's not managed by an organization can start the communication with the user. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableAcsFederationAccess +Indicates whether Teams meetings organized by the user can be joined by users of customer applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration. Additionally, Azure Communication Services users would be able to call Microsoft 365 users that have assigned policies with enabled federation. + +To enable for all users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to True. It can be disabled for selected users by assigning them a policy with federation disabled. +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` -### -EnablePublicCloudAccess -Indicates whether the user is allowed to communicate with people who have SIP accounts with a public Internet connectivity provider such as MSN. +### -EnableOutsideAccess +Indicates whether the user is allowed to connect to Skype for Business Server over the Internet, without logging on to the organization's internal network. The default value is False. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -198,7 +256,7 @@ When set to False, audio and video options in Skype for Business Server will be ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -214,7 +272,7 @@ Suppresses the display of any non-fatal error message that might occur when runn ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -231,7 +289,7 @@ If you assign the output of this cmdlet called with this parameter to a variable ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -280,7 +338,7 @@ The default value is False. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -303,7 +361,7 @@ You can return the tenant ID for each of your Skype for Business Online tenants ```yaml Type: Guid Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -313,26 +371,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` @@ -360,5 +398,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Policy.Exte [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md) [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsExternalUserCommunicationPolicy.md b/skype/skype-ps/skype/New-CsExternalUserCommunicationPolicy.md index f307d20efe..728455d346 100644 --- a/skype/skype-ps/skype/New-CsExternalUserCommunicationPolicy.md +++ b/skype/skype-ps/skype/New-CsExternalUserCommunicationPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csexternalusercommunicationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csexternalusercommunicationpolicy applicable: Skype for Business Online title: New-CsExternalUserCommunicationPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsExternalUserCommunicationPolicy @@ -35,7 +35,7 @@ This cmdlet allows you to block P2P file transfer with Federated partners only. PS C:\> New-CsExternalUserCommunicationPolicy -Identity BlockExternalP2PFileTransfer -EnableP2PFileTransfer $False ``` -This example creates a new policy to block external file transfer. Then you can use `Grant-CsExternalUserCommunicationPolicy` to assign it to an user account. +This example creates a new policy to block external file transfer. Then you can use `Grant-CsExternalUserCommunicationPolicy` to assign it to a user account. ## PARAMETERS @@ -215,10 +215,10 @@ This cmdlet supports the common parameters: `-Debug, -ErrorAction, -ErrorVariabl ## NOTES ## RELATED LINKS -[Set-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/set-csexternalusercommunicationpolicy?view=skype-ps) +[Set-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/set-csexternalusercommunicationpolicy?view=skype-ps) -[Get-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/get-csexternalusercommunicationpolicy?view=skype-ps) +[Get-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/get-csexternalusercommunicationpolicy?view=skype-ps) -[Remove-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csexternalusercommunicationpolicy?view=skype-ps) +[Remove-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/remove-csexternalusercommunicationpolicy?view=skype-ps) -[Grant-CsExternalUserCommunicationPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csexternalusercommunicationpolicy?view=skype-ps) +[Grant-CsExternalUserCommunicationPolicy](https://learn.microsoft.com/powershell/module/skype/grant-csexternalusercommunicationpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsFIPSConfiguration.md b/skype/skype-ps/skype/New-CsFIPSConfiguration.md index 87cc75b7e6..64a8204ef3 100644 --- a/skype/skype-ps/skype/New-CsFIPSConfiguration.md +++ b/skype/skype-ps/skype/New-CsFIPSConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csfipsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csfipsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsFIPSConfiguration schema: 2.0.0 @@ -224,5 +224,3 @@ The New-CsFIPSConfiguration cmdlet creates new instances of the Microsoft.Rtc.Ma [Remove-CsFIPSConfiguration](Remove-CsFIPSConfiguration.md) [Set-CsFIPSConfiguration](Set-CsFIPSConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsFileTransferFilterConfiguration.md b/skype/skype-ps/skype/New-CsFileTransferFilterConfiguration.md index dbcfddc805..166f9d2ba7 100644 --- a/skype/skype-ps/skype/New-CsFileTransferFilterConfiguration.md +++ b/skype/skype-ps/skype/New-CsFileTransferFilterConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csfiletransferfilterconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csfiletransferfilterconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsFileTransferFilterConfiguration schema: 2.0.0 @@ -280,5 +280,3 @@ The New-CsFileTransferFilterConfiguration cmdlet creates new instances of the Mi [Set-CsFileTransferFilterConfiguration](Set-CsFileTransferFilterConfiguration.md) [Get-CsFileTransferFilterConfiguration](Get-CsFileTransferFilterConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsGroupPickupUserOrbit.md b/skype/skype-ps/skype/New-CsGroupPickupUserOrbit.md index 4026917bed..2b89c659fb 100644 --- a/skype/skype-ps/skype/New-CsGroupPickupUserOrbit.md +++ b/skype/skype-ps/skype/New-CsGroupPickupUserOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csgrouppickupuserorbit +online version: https://learn.microsoft.com/powershell/module/skype/new-csgrouppickupuserorbit applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsGroupPickupUserOrbit schema: 2.0.0 @@ -52,7 +52,7 @@ The first parameter after the cmdlet is assumed to be the User parameter value. ### -Orbit Specifies the group pickup orbit number to be assigned to the user. The number must be within an orbit pickup range that was created with a type of GroupPickup. -For more information on creating call park orbits, see New-CsCallParkOrbit (https://technet.microsoft.com/en-us/library/gg398936.aspx). +For more information on creating call park orbits, see [New-CsCallParkOrbit](https://learn.microsoft.com/powershell/module/skype/New-CsCallParkOrbit). Values for the Orbit parameter must match the regular expression (\[\*|#\]?\[1-9\]\d{0,7})|(\[1-9\]\d{0,8}). @@ -154,5 +154,3 @@ This cmdlet returns an instance of the Microsoft.Rtc.Management.Voice.Helpers.Gr ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsHealthMonitoringConfiguration.md b/skype/skype-ps/skype/New-CsHealthMonitoringConfiguration.md index 818b5b7684..836ccad607 100644 --- a/skype/skype-ps/skype/New-CsHealthMonitoringConfiguration.md +++ b/skype/skype-ps/skype/New-CsHealthMonitoringConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cshealthmonitoringconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cshealthmonitoringconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsHealthMonitoringConfiguration schema: 2.0.0 @@ -311,5 +311,3 @@ The New-CsHealthMonitoringConfiguration cmdlet creates new instances of the Micr [Remove-CsHealthMonitoringConfiguration](Remove-CsHealthMonitoringConfiguration.md) [Set-CsHealthMonitoringConfiguration](Set-CsHealthMonitoringConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsHostedVoicemailPolicy.md b/skype/skype-ps/skype/New-CsHostedVoicemailPolicy.md index bff9780a3b..31d525c270 100644 --- a/skype/skype-ps/skype/New-CsHostedVoicemailPolicy.md +++ b/skype/skype-ps/skype/New-CsHostedVoicemailPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cshostedvoicemailpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-cshostedvoicemailpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsHostedVoicemailPolicy schema: 2.0.0 @@ -38,6 +38,8 @@ You can call the Get-CsUser cmdlet and check the HostedVoiceMail property to det Policies created at the site scope will be automatically assigned to the users homed on those sites. Policies created at the per-user scope must be assigned to users or contact objects with the Grant-CsHostedVoicemailPolicy cmdlet. +> [!NOTE] +> Cloud Voicemail takes the place of Exchange Unified Messaging (UM) in providing voice messaging functionality for Skype for Business 2019 voice users who have mailboxes on Exchange Server 2019 or Exchange Online, and for Skype for Business Online voice users. For more information please check [Plan Cloud Voicemail service](https://learn.microsoft.com/skypeforbusiness/hybrid/plan-cloud-voicemail) and [Retiring Unified Messaging in Exchange Online](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Retiring-Unified-Messaging-in-Exchange-Online/ba-p/608991). ## EXAMPLES @@ -234,7 +236,7 @@ You can return the tenant ID for each of your tenants by running this command: Type: Guid Parameter Sets: (All) Aliases: -Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2013, Skype for Business Server 2015 Required: False Position: Named @@ -267,5 +269,3 @@ This cmdlet creates an object of type Microsoft.Rtc.Management.WritableConfig.Po [Get-CsHostedVoicemailPolicy](Get-CsHostedVoicemailPolicy.md) [Grant-CsHostedVoicemailPolicy](Grant-CsHostedVoicemailPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsHostingProvider.md b/skype/skype-ps/skype/New-CsHostingProvider.md index b82b285dfd..ef1f878ccf 100644 --- a/skype/skype-ps/skype/New-CsHostingProvider.md +++ b/skype/skype-ps/skype/New-CsHostingProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cshostingprovider +online version: https://learn.microsoft.com/powershell/module/skype/new-cshostingprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsHostingProvider schema: 2.0.0 @@ -373,5 +373,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Ed [Remove-CsHostingProvider](Remove-CsHostingProvider.md) [Set-CsHostingProvider](Set-CsHostingProvider.md) - - diff --git a/skype/skype-ps/skype/New-CsHuntGroup.md b/skype/skype-ps/skype/New-CsHuntGroup.md deleted file mode 100644 index 2afdf44439..0000000000 --- a/skype/skype-ps/skype/New-CsHuntGroup.md +++ /dev/null @@ -1,498 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cshuntgroup -applicable: Skype for Business Online -title: New-CsHuntGroup -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsHuntGroup - -## SYNOPSIS -Creates new Call Queue in your Skype for Business Online organization. Call Queues are part of Phone System in Office 365. - -## SYNTAX - -``` -New-CsHuntGroup -Domain <System.String> -Name <System.String> [-AgentAlertTime <Int16>] [-AllowOptOut <System.Boolean>] [-DistributionLists <System.Collections.Generic.List`1[System.Guid]>] - [-LineUri <System.Uri>] [-MusicOnHoldFileContent <System.Byte[]>] [-MusicOnHoldFileName <System.String>] [-OverflowAction <Microsoft.Rtc.Management.Hosted.HuntGroup.Models.OverflowAction>] - [-OverflowActionTarget <System.Uri>] [-OverflowThreshold <Int16>] [-RoutingMethod <Microsoft.Rtc.Management.Hosted.HuntGroup.Models.RoutingMethod>] [-TimeoutAction <Microsoft.Rtc.Management.Hosted.HuntGroup.Models.TimeoutAction>] [-TimeoutActionTarget <System.Uri>] [-TimeoutThreshold <Int16>] [-UseDefaultMusicOnHold <System.Boolean>] - [-WelcomeMusicFileContent <System.Byte[]>] [-WelcomeMusicFileName <System.String>] [<CommonParameters>] -``` - -## DESCRIPTION -Creates a new Call Queue in your Skype for Business Online organization. Call Queues are part of Phone System in Office 365. - -Note, you need to specify UseDefaultMusicOnHold $True (default is none), or provide MusicOnHoldFileName and MusicOnHoldFileContent. - -MusicOnHoldFileName and MusicOnHoldFileContent cannot be empty so you must specify a valid MusicOnHoldFileName and MusicOnHoldFileContent or set UseDefaultMusicOnHold to true. - -The New-CsHuntGroup cmdlet may suggest additional steps required to complete the Call Queue setup. - -The following parameters are not applicable to Skype for Business Online: AsJob, ClientAudience, DomainController, Force, HuntGroupServiceCallbackUri, PipelineVariable, and Ring. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsHuntGroup -Name "Help Desk" -Domain "litwareinc.com" -UseDefaultMusicOnHold $true -``` - -This example creates a Call Queue for the organization named "Help Desk" in the domain "litwareinc.com" using default music on hold. - -### -------------------------- Example 2 -------------------------- -``` -$musicOnHoldContent = Get-Content ".\MusicOnHold.wav" -ReadCount 0 -Encoding Byte -$welcomeMusicContent = Get-Content ".\WelcomeMusic.wav" -ReadCount 0 -Encoding Byte -New-CsHuntGroup -Name "Help desk" -Domain "litwareinc.com" -LineUri "tel:+19998881234" -RoutingMethod Attendant -DistributionLists @("8521b0e3-51bd-4a4b-a8d6-b219a77a0a6a", "868dccd8-d723-4b4f-8d74-ab59e207c357") -AllowOptOut $false -AgentAlertTime 30 -OverflowThreshold 15 -OverflowAction Forward -OverflowActionTarget "sip:backup_user@litwareinc.com" -TimeoutThreshold 30 -TimeoutAction Disconnect -MusicOnHoldFileName "MusicOnHold.wav" -MusicOnHoldFileContent $musicOnHoldContent -WelcomeMusicFileName "WelcomeMusic.wav" -``` - -This example saves the contents of music on hold and welcome music files in temporary variables. Then, it creates a Call Queue for the organization named "Help Desk" in the domain "litwareinc.com" using those contents and other configurable parameters. - - -## PARAMETERS - -### -Domain -The Domain parameter denotes the domain part of the primary uri for the Call Queue. This domain name is validated against the list of domains that the tenant owns. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies a unique name for the Call Queue. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AgentAlertTime -The AgentAlertTime parameter represents the time (in seconds) that a call can remain unanswered before it is automatically routed to the next agent. The AgentAlertTime can be set to any integer value between 30 and 180 seconds (3 minutes), inclusive. The default value is 30 seconds. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 30 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOptOut -The AllowOptOut parameter indicates whether or not agents can opt in or opt out from taking calls from a Call Queue. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionLists -The DistributionLists parameter lets you add all the members of the distribution lists to the Call Queue. This is a list of distribution list GUIDs. A service wide configurable maximum number of DLs per Call Queue are allowed. Only the first N (service wide configurable) agents from all distribution lists combined are considered for accepting the call. Nested DLs are supported. O365 Groups can also be used to add members to the Call Queue. - -```yaml -Type: System.Collections.Generic.List`1[System.Guid] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LineUri -The LineUri parameter is the phone number for the Call Queue. The line Uniform Resource Identifier (URI) must be specified by using the following format: the tel: prefix followed by a plus sign, followed by the country/region calling code, area code, and phone number (using only digits: no blank spaces, periods, or hyphens). For example: -LineUri "tel:+14255551219". - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MusicOnHoldFileContent -The MusicOnHoldFileContent parameter represents music to play when callers are placed on hold. This is the content of the audio file. Supported formats are: .wav, .mp3, and .wma. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. - -```yaml -Type: System.Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MusicOnHoldFileName -The MusicOnHoldFileName parameter represents music to play when callers are placed on hold. This is the name of the audio file. Supported formats are: .wav, .mp3, and .wma. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowAction -The OverflowAction parameter designates the action to take if the overflow threshold is reached. The OverflowAction property must be set to one of the following three values: DisconnectWithBusy, Forward, and Voicemail. - -PARAMVALUE: DisconnectWithBusy | Forward | Voicemail - -```yaml -Type: Microsoft.Rtc.Management.Hosted.HuntGroup.Models.OverflowAction -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: DisconnectWithBusy -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowActionTarget -The OverflowActionTarget parameter represents the target of the overflow action. If the OverFlowAction is set to Forward, this parameter must be set to a SIP address. Otherwise, this parameter is optional. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowThreshold -The OverflowThreshold parameter defines the number of calls that can be in the queue at any one time before the overflow action is triggered. The OverflowThreshold can be any integer value between 0 and 200, inclusive. A value of 0 causes calls not to reach agents and the overflow action to be taken immediately - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 50 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoutingMethod -The RoutingMethod defines how agents will be called in a Call Queue. If the routing method is set to Serial, then agents will be called one at a time. If the routing method is set to Attendant, then agents will be called in parallel. - -PARAMVALUE: Attendant | Serial - -```yaml -Type: Microsoft.Rtc.Management.Hosted.HuntGroup.Models.RoutingMethod -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Attendant -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutAction -The TimeoutAction parameter defines the action to take if the timeout threshold is reached. The TimeoutAction property must be set to one of the following three values: Disconnect, Forward, and Voicemail. The default value is Disconnect. - -PARAMVALUE: Disconnect | Forward | Voicemail - -```yaml -Type: Microsoft.Rtc.Management.Hosted.HuntGroup.Models.TimeoutAction -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Disconnect -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutActionTarget -The TimeoutActionTarget represents the target of the timeout action. If the TimeoutAction is set to Forward, this parameter must be set to a SIP address. Otherwise, this field is optional. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutThreshold -The TimeoutThreshold parameter defines the time (in seconds) that a call can be in the queue before that call times out. At that point, the system will take the action specified by the TimeoutAction parameter. -The TimeoutThreshold can be any integer value between 0 and 2700 seconds (inclusive), and is rounded to the nearest 15th interval. For example, if set to 47 seconds, then it is rounded down to 45. If set to 0, welcome music is played, and then the timeout action will be taken. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 1200 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultMusicOnHold -The UseDefaultMusicOnHold parameter indicates that this Call Queue uses the default music on hold. This parameter cannot be specified together with MusicOnHoldFileName and MusicOnHoldFileContent. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WelcomeMusicFileContent -The WelcomeMusicFileContent parameter represents the audio file to play when callers are connected with the Call Queue. This is the content of the audio file. Supported formats are: .wav, .mp3, .and wma. - -```yaml -Type: System.Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WelcomeMusicFileName -The WelcomeMusicFileName parameter represents audio file to play when callers are connected with the Call Queue. This is the name to the audio file. Supported formats are: .wav, .mp3, and .wma. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassDualWrite -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClientAudience -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for Microsoft internal use only. - -PARAMVALUE: Fqdn - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HuntGroupServiceCallbackUri -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Ring -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.HuntGroup.Models.HuntGroup - -## NOTES - -## RELATED LINKS -[Create a Phone System Call Queue](https://support.office.com/en-us/article/Create-a-Phone-System-call-queue-67ccda94-1210-43fb-a25b-7b9785f8a061) - diff --git a/skype/skype-ps/skype/New-CsHybridApplicationEndpoint.md b/skype/skype-ps/skype/New-CsHybridApplicationEndpoint.md index e2720d0cd5..55b09cfd15 100644 --- a/skype/skype-ps/skype/New-CsHybridApplicationEndpoint.md +++ b/skype/skype-ps/skype/New-CsHybridApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsHybridApplicationEndpoint schema: 2.0.0 @@ -111,7 +111,7 @@ Accept wildcard characters: False ``` ### -OU -Active Directory Organizational Unit (OU) for the disabled user to be created. Wait for the newly created user object to be directory synced to the Azure Active Directory or start a new directory sync cycle by running the [Start-ADSyncSyncCycle](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-feature-scheduler#start-the-scheduler) on the domain controller machine. +Active Directory Organizational Unit (OU) for the disabled user to be created. Wait for the newly created user object to be directory synced to the Microsoft Entra ID or start a new directory sync cycle by running the [Start-ADSyncSyncCycle](https://learn.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-feature-scheduler#start-the-scheduler) on the domain controller machine. ```yaml Type: OUIdParameter @@ -190,8 +190,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[Get-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint?view=skype-ps) +[Get-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint?view=skype-ps) -[Set-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint?view=skype-ps) +[Set-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint?view=skype-ps) -[Remove-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint?view=skype-ps) +[Remove-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsHybridPSTNSite.md b/skype/skype-ps/skype/New-CsHybridPSTNSite.md index 2627118764..7bd818bd11 100644 --- a/skype/skype-ps/skype/New-CsHybridPSTNSite.md +++ b/skype/skype-ps/skype/New-CsHybridPSTNSite.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cshybridpstnsite +online version: https://learn.microsoft.com/powershell/module/skype/new-cshybridpstnsite applicable: Skype for Business Online title: New-CsHybridPSTNSite schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsHybridPSTNSite @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the New-CsHybridPSTNSite cmdlet to create a new hybrid public switched telephone network (PSTN) site. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` @@ -219,22 +221,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` @@ -251,4 +237,3 @@ The New-CsHybridPSTNSite cmdlet returns instances of the HybridPstnSite object. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsImConfiguration.md b/skype/skype-ps/skype/New-CsImConfiguration.md index 36b1c7fb54..bff157c1c2 100644 --- a/skype/skype-ps/skype/New-CsImConfiguration.md +++ b/skype/skype-ps/skype/New-CsImConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csimconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csimconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsImConfiguration schema: 2.0.0 @@ -102,7 +102,7 @@ Accept wildcard characters: False ``` ### -InMemory -Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-<cmdlet>. +Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-\<cmdlet\>. ```yaml Type: SwitchParameter @@ -163,8 +163,8 @@ This cmdlet supports the common parameters: `-Debug, -ErrorAction, -ErrorVariabl ## NOTES ## RELATED LINKS -[Get-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/get-csimconfiguration?view=skype-ps) +[Get-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/get-csimconfiguration?view=skype-ps) -[Set-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/set-csimconfiguration?view=skype-ps) +[Set-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/set-csimconfiguration?view=skype-ps) -[Remove-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/remove-csimconfiguration?view=skype-ps) +[Remove-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/remove-csimconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsImFilterConfiguration.md b/skype/skype-ps/skype/New-CsImFilterConfiguration.md index 8cc901ea1f..07c90a6de3 100644 --- a/skype/skype-ps/skype/New-CsImFilterConfiguration.md +++ b/skype/skype-ps/skype/New-CsImFilterConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csimfilterconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csimfilterconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsImFilterConfiguration schema: 2.0.0 @@ -327,4 +327,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.ImFil [Set-CsImFilterConfiguration](Set-CsImFilterConfiguration.md) [Get-CsImFilterConfiguration](Get-CsImFilterConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsImTranslationConfiguration.md b/skype/skype-ps/skype/New-CsImTranslationConfiguration.md index d0a0c719f1..02129499f3 100644 --- a/skype/skype-ps/skype/New-CsImTranslationConfiguration.md +++ b/skype/skype-ps/skype/New-CsImTranslationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csimtranslationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csimtranslationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsImTranslationConfiguration schema: 2.0.0 @@ -225,5 +225,3 @@ This cmdlet supports the common parameters: `-Debug, -ErrorAction, -ErrorVariabl ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md b/skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md deleted file mode 100644 index 281b2afeaa..0000000000 --- a/skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csinboundblockednumberpattern -applicable: Skype for Business Online -title: New-CsInboundBlockedNumberPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# New-CsInboundBlockedNumberPattern - -## SYNOPSIS -Adds a blocked number pattern to the tenant list. - -## SYNTAX - -### Identity (Default) -``` -New-CsInboundBlockedNumberPattern [-Tenant <Guid>] [-Enabled <Boolean>] [-Description <String>] - -Pattern <String> [-Identity] <XdsGlobalRelativeIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [AsJob] [<CommonParameters>] -``` - -### ParentAndRelativeKey -``` -New-CsInboundBlockedNumberPattern [-Tenant <Guid>] -Name <String> [-Enabled <Boolean>] - [-Description <String>] -Pattern <String> [-InMemory] [-Force] [-WhatIf] [-Confirm] [AsJob] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet adds a blocked number pattern to the tenant list. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> New-CsInboundBlockedNumberPattern -Description "Avoid Unwanted Automatic Call" -Name "BlockAutomatic" -Pattern "^\+11234567890" -``` - -This example adds a blocked number pattern to block inbound calls from +11234567890 number. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A friendly description for the blocked number pattern to be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -If this parameter is set to True, the inbound calls matching the pattern will be blocked. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The *Force* switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the *Force* switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier specifying the blocked number pattern to be created. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -A displayable name describing the blocked number pattern to be created. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Pattern -A regular expression that the calling number must match in order to be blocked. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the *AsJob* parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the *Receive-Job* cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS - -[Get-CsInboundBlockedNumberPattern](Get-CsInboundBlockedNumberPattern.md) - -[Set-CsInboundBlockedNumberPattern](Set-CsInboundBlockedNumberPattern.md) - -[Remove-CsInboundBlockedNumberPattern](Remove-CsInboundBlockedNumberPattern.md) diff --git a/skype/skype-ps/skype/New-CsIssuedCertId.md b/skype/skype-ps/skype/New-CsIssuedCertId.md index 4f1ea9fca4..0303d409ac 100644 --- a/skype/skype-ps/skype/New-CsIssuedCertId.md +++ b/skype/skype-ps/skype/New-CsIssuedCertId.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csissuedcertid +online version: https://learn.microsoft.com/powershell/module/skype/new-csissuedcertid applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsIssuedCertId schema: 2.0.0 @@ -134,5 +134,3 @@ New-CsIssuedCertId creates instances of the Microsoft.Rtc.Management.WritableCon ## RELATED LINKS [New-CsSipProxyTLS](New-CsSipProxyTLS.md) - - diff --git a/skype/skype-ps/skype/New-CsKerberosAccount.md b/skype/skype-ps/skype/New-CsKerberosAccount.md index b5bf4b3018..85ed0abd14 100644 --- a/skype/skype-ps/skype/New-CsKerberosAccount.md +++ b/skype/skype-ps/skype/New-CsKerberosAccount.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cskerberosaccount +online version: https://learn.microsoft.com/powershell/module/skype/new-cskerberosaccount applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsKerberosAccount schema: 2.0.0 @@ -191,5 +191,3 @@ The New-CsKerberosAccount cmdlet creates new instances of the Microsoft.Rtc.Mana ## RELATED LINKS [New-CsKerberosAccountAssignment](New-CsKerberosAccountAssignment.md) - - diff --git a/skype/skype-ps/skype/New-CsKerberosAccountAssignment.md b/skype/skype-ps/skype/New-CsKerberosAccountAssignment.md index 99b0f02aeb..d02844a752 100644 --- a/skype/skype-ps/skype/New-CsKerberosAccountAssignment.md +++ b/skype/skype-ps/skype/New-CsKerberosAccountAssignment.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cskerberosaccountassignment +online version: https://learn.microsoft.com/powershell/module/skype/new-cskerberosaccountassignment applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsKerberosAccountAssignment schema: 2.0.0 @@ -193,4 +193,3 @@ The New-CsKerberosAccountAssignment cmdlet creates new instances of the Microsof [Remove-CsKerberosAccountAssignment](Remove-CsKerberosAccountAssignment.md) [Set-CsKerberosAccountAssignment](Set-CsKerberosAccountAssignment.md) - diff --git a/skype/skype-ps/skype/New-CsLocationPolicy.md b/skype/skype-ps/skype/New-CsLocationPolicy.md index 27309cbf95..bea3233f4e 100644 --- a/skype/skype-ps/skype/New-CsLocationPolicy.md +++ b/skype/skype-ps/skype/New-CsLocationPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cslocationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-cslocationpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsLocationPolicy schema: 2.0.0 @@ -504,5 +504,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Locatio [Get-CsPstnUsage](Get-CsPstnUsage.md) [Get-CsVoiceRoute](Get-CsVoiceRoute.md) - - diff --git a/skype/skype-ps/skype/New-CsMcxConfiguration.md b/skype/skype-ps/skype/New-CsMcxConfiguration.md index afa73fe140..58a5312e5f 100644 --- a/skype/skype-ps/skype/New-CsMcxConfiguration.md +++ b/skype/skype-ps/skype/New-CsMcxConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csmcxconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csmcxconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsMcxConfiguration schema: 2.0.0 manager: rogupta @@ -287,5 +287,3 @@ Creates new instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.M ## NOTES ## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsMediaConfiguration.md b/skype/skype-ps/skype/New-CsMediaConfiguration.md index 188e7380d0..b90eef34a2 100644 --- a/skype/skype-ps/skype/New-CsMediaConfiguration.md +++ b/skype/skype-ps/skype/New-CsMediaConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csmediaconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csmediaconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsMediaConfiguration schema: 2.0.0 @@ -346,7 +346,7 @@ Accept wildcard characters: False ``` ### -EnableVideoBasedSharing -Enables the use of Video Based Sharing, for more information, see [Video based Screen Sharing for Skype for Business Server](https://docs.microsoft.com/skypeforbusiness/manage/video-based-screen-sharing) +Enables the use of Video Based Sharing, for more information, see [Video based Screen Sharing for Skype for Business Server](https://learn.microsoft.com/skypeforbusiness/manage/video-based-screen-sharing) ```yaml Type: Boolean @@ -383,5 +383,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Media [Set-CsMediaConfiguration](Set-CsMediaConfiguration.md) [Get-CsMediaConfiguration](Get-CsMediaConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsMeetingConfiguration.md b/skype/skype-ps/skype/New-CsMeetingConfiguration.md index 0064e7784c..77faa8bbc2 100644 --- a/skype/skype-ps/skype/New-CsMeetingConfiguration.md +++ b/skype/skype-ps/skype/New-CsMeetingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csmeetingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csmeetingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsMeetingConfiguration schema: 2.0.0 @@ -414,5 +414,3 @@ The New-CsMeetingConfiguration cmdlet creates new instances of the Microsoft.Rtc [Remove-CsMeetingConfiguration](Remove-CsMeetingConfiguration.md) [Set-CsMeetingConfiguration](Set-CsMeetingConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsMobilityPolicy.md b/skype/skype-ps/skype/New-CsMobilityPolicy.md index 983461e8cf..5e9016c50f 100644 --- a/skype/skype-ps/skype/New-CsMobilityPolicy.md +++ b/skype/skype-ps/skype/New-CsMobilityPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csmobilitypolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csmobilitypolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsMobilityPolicy schema: 2.0.0 manager: bulenteg @@ -20,7 +20,7 @@ These policies also manage a user's ability to employ Call via Work, a feature t Mobility policies can also be used to require Wi-Fi connections when making or receiving IP video/screen share calls. This cmdlet was introduced in the cumulative update for Lync Server 2010: November 2011. -The following parameters are not applicable to Skype for Business Online: AllowAutomaticPstnFallback, AllowCustomerExperienceImprovementProgram, AllowExchangeConnectivity, AllowSaveCallLogs, AsJob, Description, EncryptAppData, Force, Identity, InMemory, PipelineVariable, RequireIntune, Tenant, and VoiceSettings +The following parameters are not applicable to Skype for Business Online: AllowAutomaticPstnFallback, AllowCustomerExperienceImprovementProgram, AllowExchangeConnectivity, AllowSaveCallLogs, Description, EncryptAppData, Force, Identity, InMemory, PipelineVariable, RequireIntune, Tenant, and VoiceSettings ## SYNTAX @@ -324,7 +324,7 @@ Accept wildcard characters: False When set to True (the default value) users will be allowed to sync device contacts on the mobile apps. -More information: [How to disable CallKit integration for Skype for Business iOS](https://docs.microsoft.com/SkypeForBusiness/troubleshoot/server-phone-system/disable-callkit-integration). +More information: [How to disable CallKit integration for Skype for Business iOS](https://learn.microsoft.com/SkypeForBusiness/troubleshoot/server-phone-system/disable-callkit-integration). ```yaml Type: Boolean @@ -529,27 +529,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob - -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` @@ -572,4 +551,3 @@ Creates new instances of the Microsoft.Rtc.Management.WriteableConfig.Policy.Mob ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsNetworkBWAlternatePath.md b/skype/skype-ps/skype/New-CsNetworkBWAlternatePath.md index e2a0fec3c8..cb3e77828a 100644 --- a/skype/skype-ps/skype/New-CsNetworkBWAlternatePath.md +++ b/skype/skype-ps/skype/New-CsNetworkBWAlternatePath.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkbwalternatepath +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkbwalternatepath applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkBWAlternatePath schema: 2.0.0 @@ -118,4 +118,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Netwo [New-CsNetworkRegion](New-CsNetworkRegion.md) [Set-CsNetworkRegion](Set-CsNetworkRegion.md) - diff --git a/skype/skype-ps/skype/New-CsNetworkBWPolicy.md b/skype/skype-ps/skype/New-CsNetworkBWPolicy.md index 3f9d1343d5..f6cd2973a3 100644 --- a/skype/skype-ps/skype/New-CsNetworkBWPolicy.md +++ b/skype/skype-ps/skype/New-CsNetworkBWPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkbwpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkbwpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkBWPolicy schema: 2.0.0 @@ -137,4 +137,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Netwo [New-CsNetworkBandwidthPolicyProfile](New-CsNetworkBandwidthPolicyProfile.md) [Set-CsNetworkBandwidthPolicyProfile](Set-CsNetworkBandwidthPolicyProfile.md) - diff --git a/skype/skype-ps/skype/New-CsNetworkBandwidthPolicyProfile.md b/skype/skype-ps/skype/New-CsNetworkBandwidthPolicyProfile.md index e003c360c0..0c27af1dff 100644 --- a/skype/skype-ps/skype/New-CsNetworkBandwidthPolicyProfile.md +++ b/skype/skype-ps/skype/New-CsNetworkBandwidthPolicyProfile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkbandwidthpolicyprofile +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkbandwidthpolicyprofile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkBandwidthPolicyProfile schema: 2.0.0 @@ -296,4 +296,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Netwo [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) [New-CsNetworkBWPolicy](New-CsNetworkBWPolicy.md) - diff --git a/skype/skype-ps/skype/New-CsNetworkInterRegionRoute.md b/skype/skype-ps/skype/New-CsNetworkInterRegionRoute.md index 4b63f69ed4..5a44fa962c 100644 --- a/skype/skype-ps/skype/New-CsNetworkInterRegionRoute.md +++ b/skype/skype-ps/skype/New-CsNetworkInterRegionRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkinterregionroute +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkinterregionroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkInterRegionRoute schema: 2.0.0 @@ -260,5 +260,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Netwo [Set-CsNetworkInterRegionRoute](Set-CsNetworkInterRegionRoute.md) [Get-CsNetworkInterRegionRoute](Get-CsNetworkInterRegionRoute.md) - - diff --git a/skype/skype-ps/skype/New-CsNetworkInterSitePolicy.md b/skype/skype-ps/skype/New-CsNetworkInterSitePolicy.md index 15825e839b..445ced2da8 100644 --- a/skype/skype-ps/skype/New-CsNetworkInterSitePolicy.md +++ b/skype/skype-ps/skype/New-CsNetworkInterSitePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkintersitepolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkintersitepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkInterSitePolicy schema: 2.0.0 @@ -233,5 +233,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Netwo [Set-CsNetworkInterSitePolicy](Set-CsNetworkInterSitePolicy.md) [Get-CsNetworkInterSitePolicy](Get-CsNetworkInterSitePolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsNetworkMediaBypassConfiguration.md b/skype/skype-ps/skype/New-CsNetworkMediaBypassConfiguration.md index 09674e52f5..37c19d474c 100644 --- a/skype/skype-ps/skype/New-CsNetworkMediaBypassConfiguration.md +++ b/skype/skype-ps/skype/New-CsNetworkMediaBypassConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkmediabypassconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkmediabypassconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkMediaBypassConfiguration schema: 2.0.0 manager: bulenteg @@ -17,9 +17,6 @@ ms.reviewer: rogupta Creates new global settings for media bypass. This cmdlet was introduced in Lync Server 2010. - - - ## SYNTAX ``` @@ -40,8 +37,6 @@ The object created by this cmdlet must be saved to a variable and then assigned The settings created with this cmdlet can be retrieved only by accessing the MediaBypassSettings property of the global network configuration. To retrieve these settings, run this command: (Get-CsNetworkConfiguration).MediaBypassSettings. - - ## EXAMPLES ### -------------------------- EXAMPLE 1 -------------------------- @@ -61,7 +56,7 @@ Setting Enabled to True enables media bypass, while setting AlwaysBypass to True The media bypass configuration is stored with the network configuration settings. Therefore, in line 2 of the example, we save the media bypass configuration changes to the network configuration by calling the Set-CsNetworkConfiguration cmdlet and passing the media bypass configuration object ($a) we created in line 1 to the MediaBypassSettings parameter. -The following parameters are not applicable to Skype for Business Online: AsJob, BypassID, EnableDefaultBypassID, EnabledForAudioVideoConferences, ExternalBypassMode, InternalBypassMode, PipelineVariable, and Tenant +The following parameters are not applicable to Skype for Business Online: BypassID, EnableDefaultBypassID, EnabledForAudioVideoConferences, ExternalBypassMode, InternalBypassMode, PipelineVariable, and Tenant ### -------------------------- EXAMPLE 2 -------------------------- @@ -86,7 +81,6 @@ We assign those settings to the variable $a. In line 2 we modify the settings stored in variable $a by assigning the value False ($false) to the AlwaysBypass property. Finally, in line 3 we call the Set-CsNetworkConfiguration cmdlet, passing the MediaBypassSettings parameter the variable $a, which saves the change we made to the AlwaysBypass property. - ## PARAMETERS ### -AlwaysBypass @@ -108,8 +102,6 @@ Setting AlwaysBypass and Enabled both to True will auto-generate a bypass ID tha Default: False - - ```yaml Type: Boolean Parameter Sets: (All) @@ -133,8 +125,6 @@ This ID must be in the format of a GUID (for example, 96f14dea-5170-429a-b92b-f1 However, you will typically not have to set or change this parameter. This value is automatically generated when Enabled is set to True and either: 1) AlwaysBypass is set to True, or 2) the EnableDefaultBypassID parameter is set to True. - - ```yaml Type: String Parameter Sets: (All) @@ -158,7 +148,6 @@ At that point bypass decisions will be based on the value of the AlwaysBypass se Default: False - ```yaml Type: Boolean Parameter Sets: (All) @@ -185,8 +174,6 @@ Any subnets associated with the core need not be defined and bypass will automat Default: False - - ```yaml Type: Boolean Parameter Sets: (All) @@ -207,8 +194,6 @@ External media bypass is not supported in Skype for Business Server. Default: Off - - ```yaml Type: BypassModeEnumType Parameter Sets: (All) @@ -230,9 +215,6 @@ Other values for this parameter are reserved for future use. Default: Off - - - ```yaml Type: BypassModeEnumType Parameter Sets: (All) @@ -251,9 +233,6 @@ Accept wildcard characters: False Indicates whether media bypass should be used for audio/video conferences. The default value is False ($False). - - - ```yaml Type: Boolean Parameter Sets: (All) @@ -305,4 +284,3 @@ Creates an object reference of type Microsoft.Rtc.Management.WritableConfig.Sett [Get-CsNetworkConfiguration](Get-CsNetworkConfiguration.md) [Set-CsNetworkConfiguration](Set-CsNetworkConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsNetworkRegion.md b/skype/skype-ps/skype/New-CsNetworkRegion.md index a5ddf68eb1..eee2fe72cc 100644 --- a/skype/skype-ps/skype/New-CsNetworkRegion.md +++ b/skype/skype-ps/skype/New-CsNetworkRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkregion +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkregion applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkRegion schema: 2.0.0 @@ -358,5 +358,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Netwo [Get-CsNetworkRegion](Get-CsNetworkRegion.md) [New-CsNetworkBWAlternatePath](New-CsNetworkBWAlternatePath.md) - - diff --git a/skype/skype-ps/skype/New-CsNetworkRegionLink.md b/skype/skype-ps/skype/New-CsNetworkRegionLink.md index c755d97873..20c21b9c30 100644 --- a/skype/skype-ps/skype/New-CsNetworkRegionLink.md +++ b/skype/skype-ps/skype/New-CsNetworkRegionLink.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworkregionlink +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworkregionlink applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkRegionLink schema: 2.0.0 @@ -240,5 +240,3 @@ This cmdlet creates an object of type Microsoft.Rtc.Management.WritableConfig.Se [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) [New-CsNetworkSite](New-CsNetworkSite.md) - - diff --git a/skype/skype-ps/skype/New-CsNetworkSite.md b/skype/skype-ps/skype/New-CsNetworkSite.md index 578ac84eb2..160f838625 100644 --- a/skype/skype-ps/skype/New-CsNetworkSite.md +++ b/skype/skype-ps/skype/New-CsNetworkSite.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworksite +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworksite applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkSite schema: 2.0.0 @@ -356,5 +356,3 @@ Create an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Networ [Get-CsLocationPolicy](Get-CsLocationPolicy.md) [Get-CsNetworkConfiguration](Get-CsNetworkConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsNetworkSubnet.md b/skype/skype-ps/skype/New-CsNetworkSubnet.md index 87a1e35e6f..38d0bfaf72 100644 --- a/skype/skype-ps/skype/New-CsNetworkSubnet.md +++ b/skype/skype-ps/skype/New-CsNetworkSubnet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csnetworksubnet +online version: https://learn.microsoft.com/powershell/module/skype/new-csnetworksubnet applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsNetworkSubnet schema: 2.0.0 @@ -275,4 +275,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Netwo [Get-CsNetworkSubnet](Get-CsNetworkSubnet.md) [Get-CsNetworkSite](Get-CsNetworkSite.md) - diff --git a/skype/skype-ps/skype/New-CsOAuthServer.md b/skype/skype-ps/skype/New-CsOAuthServer.md index fd9f42fc4d..683832a330 100644 --- a/skype/skype-ps/skype/New-CsOAuthServer.md +++ b/skype/skype-ps/skype/New-CsOAuthServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csoauthserver +online version: https://learn.microsoft.com/powershell/module/skype/new-csoauthserver applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsOAuthServer schema: 2.0.0 @@ -51,7 +51,7 @@ New-CsOAuthServer -Identity "Office 365" -MetadataUrl "https://sts.office365.mic ``` Example 1 creates a new OAuth Server named "Office 365". -The new server uses the metadata URL https://sts.office365.microsoft.com/metadata/json/1. +The new server uses the metadata URL `https://sts.office365.microsoft.com/metadata/json/1`. ## PARAMETERS @@ -277,5 +277,3 @@ The New-CsOAuthServer cmdlet creates new instances of the Microsoft.Rtc.Manageme [Remove-CsOAuthServer](Remove-CsOAuthServer.md) [Set-CsOAuthServer](Set-CsOAuthServer.md) - - diff --git a/skype/skype-ps/skype/New-CsOnlineApplicationEndpoint.md b/skype/skype-ps/skype/New-CsOnlineApplicationEndpoint.md deleted file mode 100644 index 13b1d2c9e0..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineApplicationEndpoint.md +++ /dev/null @@ -1,306 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlineapplicationendpoint -applicable: Skype for Business Online -title: New-CsOnlineApplicationEndpoint -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineApplicationEndpoint - -## SYNOPSIS -The `New-CsOnlineApplicationEndpoint` creates a Trusted Application Endpoint for a tenant. - -## SYNTAX -``` -New-CsOnlineApplicationEndpoint -ApplicationId <Guid> [-CallbackUri <String>] -Name <String> [-Region <String>] - [-Uri] <String> [-Audience <String>] [-Ring <String>] [-PhoneNumber <String>] [-IsInternalRun <Boolean>] - [-Tenant <Guid>] [-RunFullProvisioningFlow <Boolean>] [-DomainController <Fqdn>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a Trusted Application Endpoint. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsOnlineApplicationEndpoint -Uri "sip:sample@domain.com" -ApplicationId "44ff763b-5d1f-40ab-95bf-f31kc8757998" -Name "SampleApp" -PhoneNumber "19841110909" -``` - -This example creates a new application endpoint. - -## PARAMETERS - -### -ApplicationId -The Azure ApplicationID/ClientID from the Azure portal registration steps. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -A friendly name of your application within Skype for Business Online. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Uri -Sip Uri that identifies the tenant specific endpoint for the application. This must be a unique URI that does not conflict with an existing user in the tenant. Requests sent to this endpoint will trigger the Trusted Application API sending an event to the application, indicating that someone has sent a request. For example: helpdesk@contoso.com. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: SipUri -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Audience -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallbackUri -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsInternalRun -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneNumber -The service number assigned to the trusted application endpoint. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Region -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Ring -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RunFullProvisioningFlow -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/get-csonlineapplicationendpoint) - -[Set-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/set-csonlineapplicationendpoint) - -[Remove-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/remove-csonlineapplicationendpoint) - -[Set up a Trusted Application Endpoint](https://docs.microsoft.com/skype-sdk/trusted-application-api/docs/trustedapplicationendpoint) - diff --git a/skype/skype-ps/skype/New-CsOnlineApplicationInstance.md b/skype/skype-ps/skype/New-CsOnlineApplicationInstance.md deleted file mode 100644 index 705da10f7d..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineApplicationInstance.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlineapplicationinstance -applicable: Skype for Business Online -title: New-CsOnlineApplicationInstance -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineApplicationInstance - -## SYNOPSIS -Creates an application instance in Azure Active Directory. - -## SYNTAX - -``` -New-CsOnlineApplicationInstance [-UserPrincipalName] <string> [[-ApplicationId] <guid>] [[-DisplayName] <string>] - [-Tenant <guid>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to create an application instance in Azure Active Directory. This same cmdlet is also run when creating a new resource account using Teams Admin Center. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -New-CsOnlineApplicationInstance -UserPrincipalName appinstance01@contoso.com -ApplicationId ce933385-9390-45d1-9512-c8d228074e07 -DisplayName "AppInstance01" -``` - -This example creates a new application instance for an Auto Attendant with UserPrincipalName "appinstance01@contoso.com", ApplicationId "ce933385-9390-45d1-9512-c8d228074e07", DisplayName "AppInstance01" for the tenant. - -The application ID's that you need to use while creating the application instances are: - -Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07 -Call Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07 - -## PARAMETERS - -### -UserPrincipalName -The user principal name. It will be used as the SIP URI too. The user principal name should have an online domain. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationId -The application ID. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The display name. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsOnlineAudioFile.md b/skype/skype-ps/skype/New-CsOnlineAudioFile.md deleted file mode 100644 index b0c0b77e6a..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineAudioFile.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlineaudiofile -applicable: Skype for Business Online -title: New-CsOnlineAudioFile -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineAudioFile - -## SYNOPSIS -Use the New-CsOnlineAudioFile cmdlet to create a new audio file. - -## SYNTAX - -``` -New-CsOnlineAudioFile -FileName <String> -Content <Byte[]> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOnlineAudioFile cmdlet creates a new audio file for use with the Organizational Auto Attendant (OAA) service. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$content = Get-Content "C:\Media\Welcome.wav" -Encoding byte -ReadCount 0 -$audioFile = New-CsOnlineAudioFile -FileName "Hello.wav" -Content $content -``` - -This example creates a new audio file using the WAV content that has a filename of Hello.wav. - -## PARAMETERS - -### -FileName -The FileName parameter is the name of the audio file. For example, the file name for the file C:\Media\Welcome.wav is Welcome.wav. - -```yaml -Type: System.string -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Content -The Content parameter represents the content of the audio file. Supported formats are WAV (uncompressed, linear PCM with 8/16/32-bit depth in mono or stereo), WMA (mono only), and MP3. The audio file content cannot be more 5MB. - -```yaml -Type: System.Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.AudioFile - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsOnlineBulkAssignmentInput.md b/skype/skype-ps/skype/New-CsOnlineBulkAssignmentInput.md deleted file mode 100644 index c6ac7a59cb..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineBulkAssignmentInput.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinebulkassignmentinput -applicable: Skype for Business Online -title: New-CsOnlineBulkAssignmentInput -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineBulkAssignmentInput - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -``` -New-CsOnlineBulkAssignmentInput [-Identity] <UserIdParameter> [-TelephoneNumber <String>] - [-LocationID <Guid>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - - -## PARAMETERS - -### -Identity -PARAMVALUE: UserIdParameter - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -PARAMVALUE: Fqdn - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationID -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumber -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsOnlineDateTimeRange.md b/skype/skype-ps/skype/New-CsOnlineDateTimeRange.md deleted file mode 100644 index 92a306cff6..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineDateTimeRange.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinedatetimerange -applicable: Skype for Business Online -title: New-CsOnlineDateTimeRange -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineDateTimeRange - -## SYNOPSIS -Use the New-CsOnlineDateTimeRange cmdlet to create a new date-time range. - -## SYNTAX - -``` -New-CsOnlineDateTimeRange -Start <String> [-End <String>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOnlineDateTimeRange cmdlet creates a new date-time range to be used with the Organizational Auto Attendant (OAA) service. Date time ranges are used to form schedules. - -**NOTE** -- The start bound of the range must be less than its end bound. -- The time part of the range must be aligned with 30/60-minutes boundaries. -- A date time range bound can only be input in the following formats: - - "d/m/yyyy H:mm" - - "d/m/yyyy" (the time component of the date-time range is set to 00:00) - - -## EXAMPLES - -### Example 1 -``` -$dtr = New-CsOnlineDateTimeRange -Start "1/1/2017" -``` - -This example creates a date-time range for spanning from January 1, 2017 12AM to January 2, 2017 12AM. - -### Example 2 -``` -$dtr = New-CsOnlineDateTimeRange -Start "24/12/2017 09:00" -End "27/12/2017 00:00" -``` - -This example creates a date-time range spanning from December 24, 2017 9AM to December 27, 2017 12AM. - -## PARAMETERS - -### -Start -The Start parameter represents the start bound of the date-time range. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -End -The End parameter represents the end bound of the date-time range. - -If not present, the end bound of the date time range is set to 00:00 of the day after the start date. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.DateTimeRange - -## NOTES - -## RELATED LINKS - -[New-CsOnlineSchedule](New-CsOnlineSchedule.md) diff --git a/skype/skype-ps/skype/New-CsOnlineLisCivicAddress.md b/skype/skype-ps/skype/New-CsOnlineLisCivicAddress.md deleted file mode 100644 index abce369070..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineLisCivicAddress.md +++ /dev/null @@ -1,491 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlineliscivicaddress -applicable: Skype for Business Online -title: New-CsOnlineLisCivicAddress -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# New-CsOnlineLisCivicAddress - -## SYNOPSIS -Use the New-CsOnlineLisCivicAddress cmdlet to create a civic address in the Location Information Service (LIS.) - -## SYNTAX - -``` -New-CsOnlineLisCivicAddress [-HouseNumber <String>] [-HouseNumberSuffix <String>] [-StreetName <String>] - [-StreetSuffix <String>] [-PostDirectional <String>] [-PreDirectional <String>] [-City <String>] - [-CityAlias <String>] [-StateOrProvince <String>] -CountryOrRegion <String> [-PostalCode <String>] - [-Description <String>] -CompanyName <String> [-CompanyTaxId <String>] [-ValidationStatus <String>] - [-Latitude <String>] [-Longitude <String>] [-Confidence <String>] [-Elin <String>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Because each civic address needs at least one location to assign to users, creating a new civic address also creates a default location. -This is useful in cases where a civic address has no particular sub-locations. -In that scenario you can create the civic address using the New -CsOnlineLisCivicAddress cmdlet and use the default location identifier for assignment to users. -The example output from the Get-CsOnlineLisCivicAddress below shows the DefaultLocationId property. - -CivicAddressId : 51a8a6e3-dae4-4653-9a99-a6e71c4c24ac - -HouseNumber : - -HouseNumberSuffix : - -PreDirectional : - -StreetName : - -StreetSuffix : - -PostDirectional : - -City : - -PostalCode : - -StateOrProvince : - -CountryOrRegion : US - -Description : - -CompanyName : MSFT - -DefaultLocationId : 75301b5d-3609-458e-a379-da9a1ab33228 - -ValidationStatus : NotValidated - -NumberOfVoiceUsers : 0 - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsOnlineLisCivicAddress -HouseNumber 3910 -StreetName Smith -StreetSuffix Street -PostDirectional NE -City Redmond -StateorProvince Washington -Country US -PostalCode 98052 -Description "West Coast Headquarters" -CompanyName Contoso -``` - -This example creates a new civic address described as "West Coast Headquarters": 3910 Smith Street NE, Redmond WA, 98052. - - -### -------------------------- Example 2 -------------------------- -``` -New-CsOnlineLisCivicAddress -Latitude 12 -Longitude 34 -HouseNumber 567 -StreetName Main -StreetSuffix St -City Springfield -StateOrProvince WA -CountryOrRegion US -PostalCode 98052 -CompanyName Contoso -Elin MICROSOFT_ELIN -Description "R&D office" -``` - -This example creates a new civic address described as "R&D office", with latitude, longitude and ELIN. - - -## PARAMETERS - -### -CompanyName -Specifies the name of your organization. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the country or region of the new civic address. -Needs to be a valid country code as contained in the ISO 3166-1 alpha-2 specification. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -Specifies the city of the new civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CityAlias -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyTaxId -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies an administrator defined description of the new civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumber -Specifies the numeric portion of the new civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumberSuffix -Specifies the numeric suffix of the new civic address. -For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostalCode -Specifies the postal code of the new civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostDirectional -Specifies the directional attribute of the new civic address which follows the street name. -For example, "425 Smith Avenue NE". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreDirectional -Specifies the directional attribute of the new civic address which precedes the street name. -For example, "425 NE Smith Avenue ". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOrProvince -Specifies the state or province of the new civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetName -Specifies the street name of the new civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetSuffix -Specifies the street type of the new civic address. -The street suffix will typically be something like street, avenue, way, or boulevard. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidationStatus -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confidence -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Elin -Specifies the Emergency Location Identification Number. -This is used in Direct Routing EGW scenarios. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Latitude -Specifies the angular distance of a place north or south of the earth's equator. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Longitude -Specifies the angular distance of a place east or west of the meridian at Greenwich, England. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### None - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsOnlineLisLocation.md b/skype/skype-ps/skype/New-CsOnlineLisLocation.md deleted file mode 100644 index 0cec25293a..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineLisLocation.md +++ /dev/null @@ -1,495 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinelislocation -applicable: Skype for Business Online -title: New-CsOnlineLisLocation -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# New-CsOnlineLisLocation - -## SYNOPSIS -Use the New-CsOnlineLisLocation cmdlet to either to create a new emergency dispatch location within an existing civic address, or to create both a new civic address and a location assigned to that address. -There can be multiple locations in a civic address. -Typically the civic address designates the building, and locations are specific parts of that building such as a floor, office, or wing. - -## SYNTAX - -### ExistingCivicAddress (Default) -``` -New-CsOnlineLisLocation -CivicAddressId <Guid> -Location <String> [-CompanyName <String>] - [-CompanyTaxId <String>] [-HouseNumberSuffix <String>] [-CityAlias <String>] [-Latitude <String>] - [-Longitude <String>] [-Confidence <String>] [-Elin <String>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### CreateCivicAddress -``` -New-CsOnlineLisLocation [-Location <String>] [-CompanyName <String>] [-CompanyTaxId <String>] - [-HouseNumber <String>] [-HouseNumberSuffix <String>] [-StreetName <String>] [-StreetSuffix <String>] - [-PostDirectional <String>] [-PreDirectional <String>] [-City <String>] [-CityAlias <String>] - [-StateOrProvince <String>] -CountryOrRegion <String> [-PostalCode <String>] [-Description <String>] - [-Latitude <String>] [-Longitude <String>] [-Confidence <String>] [-Elin <String>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsOnlineLisLocation -CivicAddressId b39ff77d-db51-4ce5-8d50-9e9c778e1617 -Location "Office 101, 1st Floor" -``` - -This example creates a new location called "Office 101, 1st Floor" in the civic address specified by its identity. - - -### -------------------------- Example 2 -------------------------- -``` -New-CsOnlineLisLocation -Location "Office 202, 2nd Floor" -CompanyName "Contoso" -HouseNumber 3910 -StreetName 163rd -StreetSuffix St -City Bellevue -StateOrProvince WA -CountryOrRegion US -PostalCode 98004 -Description "New civic address location" -Elin TEST_ELIN -``` - -This example creates a new civic address and a location assigned to the address. Location is called "Office 202, 2st Floor" with Elin string "TEST_ELIN" - - -## PARAMETERS - -### -CivicAddressId -Specifies the unique identifier of the civic address that will contain the new location. -If specified, no other address description parameters are allowed. -Civic address identities can be discovered by using the Get-CsOnlineLisCivicAddress cmdlet. - -```yaml -Type: Guid -Parameter Sets: ExistingCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the country or region of the civic address. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: Country -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Location -Specifies an administrator defined description of the new location. -For example, "2nd Floor Cafe", "Main Lobby", or "Office 250". - -```yaml -Type: String -Parameter Sets: ExistingCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -Specifies the city of the civic address. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CityAlias -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyName -Specifies the name of your organization. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Name -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyTaxId -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies an administrator defined description of the civic address. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumber -Specifies the numeric portion of the civic address. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumberSuffix -Specifies the numeric suffix of the civic address. -For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostalCode -Specifies the postal code of the civic address. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostDirectional -Specifies the directional attribute of the civic address which follows the street name. -For example, "425 Smith Avenue NE". - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreDirectional -Specifies the directional attribute of the civic address which precedes the street name. -For example, "425 NE Smith Avenue ". - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOrProvince -Specifies the state or province of the civic address. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: State -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetName -Specifies the street name of the civic address. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetSuffix -Specifies the modifier of the street name. -The street suffix will typically be something like street, avenue, way, or boulevard. - -```yaml -Type: String -Parameter Sets: CreateCivicAddress -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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 - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confidence -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Elin -Specifies the Emergency Location Identification Number. -This is used in Direct Routing EGW scenarios. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Latitude -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Longitude -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsOnlineNumberPortInOrder.md b/skype/skype-ps/skype/New-CsOnlineNumberPortInOrder.md deleted file mode 100644 index c54f255041..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineNumberPortInOrder.md +++ /dev/null @@ -1,747 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinenumberportinorder -applicable: Skype for Business Online -title: New-CsOnlineNumberPortInOrder -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineNumberPortInOrder - -## SYNOPSIS -This cmdlet is reserved for Microsoft internal use only. -New third party provider ports should be provisioned through the Skype for Business Online admin center. - -## SYNTAX - -``` -New-CsOnlineNumberPortInOrder [-Tenant <Guid>] -InventoryType <String> [-TelephoneNumbers <String[]>] - [-LOABase64PayLoad <String>] [-LOAContentType <String>] [-LOAAuthorizingPerson <String>] - [-SubscriberArea <String>] [-SubscriberCity <String>] [-SubscriberCountry <String>] - [-SubscriberStreetName <String>] [-SubscriberBuildingNumber <String>] [-SubscriberZipCode <String>] - [-SubscriberBusinessName <String>] [-BillingTelephoneNumber <String>] [-SubscriberFirstName <String>] - [-SubscriberLastName <String>] [-EmailAddresses <String[]>] [-RequestedFocDate <DateTime>] - [-LosingTelcoPin <String>] [-LosingTelcoAccountId <String>] [-IsPartialPort] - [-SubscriberAddressLine1 <String>] [-SubscriberAddressLine2 <String>] [-SubscriberAddressLine3 <String>] - [-FriendlyName <String>] [-IsManual] [-RequestedFocDateBegin <DateTimeOffset>] - [-RequestedFocDateEnd <System.DateTimeOffset>] [-RangeHolder <String>] [-TelephoneNumberRanges <String[][]>] - [-SubscriberAdditionalInfo <String>] [-SubscriberBuildingNumberSuffix <String>] - [-SubscriberStreetSuffix <String>] [-SubscriberPreDirectional <String>] [-SubscriberPostDirectional <String>] - [-SubscriberDescription <String>] [-SubscriberCounty <String>] [-SubscriberCompanyName <String>] - [-SubscriberCityAlias <String>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` - -``` - -## PARAMETERS - -### -InventoryType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BillingTelephoneNumber -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FriendlyName -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsManual -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsPartialPort -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LOAAuthorizingPerson -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LOABase64PayLoad -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LOAContentType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LosingTelcoAccountId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LosingTelcoPin -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RangeHolder -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestedFocDate -This parameter is reserved for internal Microsoft use. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestedFocDateBegin -PARAMVALUE: DateTimeOffset - -```yaml -Type: DateTimeOffset -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestedFocDateEnd -PARAMVALUE: DateTimeOffset - -```yaml -Type: DateTimeOffset -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAdditionalInfo -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAddressLine1 -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAddressLine2 -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAddressLine3 -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberArea -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberBuildingNumber -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberBuildingNumberSuffix -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberBusinessName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberCity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberCityAlias -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberCompanyName -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberCountry -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberCounty -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberDescription -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberFirstName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberLastName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberPostDirectional -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberPreDirectional -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberStreetName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberStreetSuffix -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberZipCode -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumberRanges -PARAMVALUE: String\[\]\[\] - -```yaml -Type: String[][] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumbers -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsOnlinePSTNGateway.md b/skype/skype-ps/skype/New-CsOnlinePSTNGateway.md deleted file mode 100644 index c9fc10a5ca..0000000000 --- a/skype/skype-ps/skype/New-CsOnlinePSTNGateway.md +++ /dev/null @@ -1,472 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinepstngateway -applicable: Skype for Business Online -title: New-CsOnlinePSTNGateway -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlinePSTNGateway - -## SYNOPSIS -Creates a new Session Border Controller (SBC) Configuration that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. - -## SYNTAX - -``` -New-CsOnlinePSTNGateway [-Tenant <System.Guid>] [-Fqdn <String>] [-SipSignalingPort <Int32>] - [-CodecPriority <String>] [-ExcludedCodecs <String>] [-FailoverTimeSeconds <Int32>] - [-ForwardCallHistory <Boolean>] [-ForwardPai <Boolean>] [-SendSipOptions <Boolean>] - [-MaxConcurrentSessions <System.Int32>] [-Enabled <Boolean>] [-MediaBypass <Boolean>] - [-GatewaySiteId <String>] [-GatewaySiteLbrEnabled <Boolean>] [-BypassMode <String>] [-GenerateRingingWhileLocatingUser <Boolean>] - [-InboundTeamsNumberTranslationRules <String>] [-InboundPSTNNumberTranslationRules <String>] - [-OutboundTeamsNumberTranslationRules <String>] [-OutboundPSTNNumberTranslationRules <String>] [-PidfloSupported <Boolean>] - [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to create a new Session Border Controller (SBC) configuration. Each configuration contains specific settings for an SBC. These settings configure such entities as the SIP signaling port, whether media bypass is enabled on this SBC, will the SBC send SIP Options, and specify the limit of maximum concurrent sessions. The cmdlet also lets the administrator drain the SBC by setting parameter -Enabled to $true or $false state. When the Enabled parameter is set to $false, the SBC will continue existing calls, but all new calls will be routed to another SBC in a route (if one exists). - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsOnlinePSTNGateway -FQDN sbc.contoso.com -SIPSignalingPort 5061 -``` - -This example creates an SBC with FQDN sbc.contoso.com and signaling port 5061. All others parameters will stay default. Note the SBC will be in the disabled state. - -### Example 2 -```powershell -PS C:\> New-CsOnlinePSTNGateway -FQDN sbc.contoso.com -SIPSignalingPort 5061 -ForwardPAI $true -Enabled $true -``` - -This example creates an SBC with FQDN sbc.contoso.com and signaling port 5061. For each outbound to SBC session, the Direct Routing interface will report in P-Asserted-Identity fields the TEL URI and SIP address of the user who made a call. This is useful when a tenant administrator sets the identity of the caller as "Anonymous" or a general number of the company, but for billing purposes the real identity of the user is required. - -## PARAMETERS - -### -CodecPriority -Allows choice of codec priority when media is negotiated between Media Proxy and SBC. Default priority is ("SILKWB,SILKNB,PCMU,PCMA"). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: ("SILKWB,SILKNB,PCMU,PCMA") -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -Used to enable this SBC for outbound calls. Can be used to temporarily remove the SBC from service while it is being updated or during maintenance. Note if the parameter is not set the SBC will be created as disabled (default value -Enabled $false). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExcludedCodecs -Allows some codecs to be excluded when media is being negotiated between Media Proxy and SBC. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverTimeSeconds -When set to 10 (default value), outbound calls that are not answered by the gateway within 10 seconds are routed to the next available trunk; if there are no additional trunks, then the call is automatically dropped. In an organization with slow networks and slow gateway responses, that could potentially result in calls being dropped unnecessarily. The default value is 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: 10 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForwardCallHistory -Indicates whether call history information will be forwarded to the SBC. If enabled, the Office 365 PSTN Proxy sends two headers: History-info and Referred-By. The default value is False ($False). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForwardPai -Indicates whether the P-Asserted-Identity (PAI) header will be forwarded along with the call. The PAI header provides a way to verify the identity of the caller. The default value is False ($False). Setting this parameter to $true will render the from header anonymous, in accordance of RFC5379 and RFC3325. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Fqdn -Limited to 63 characters, the FQDN registered for the SBC. Copied automatically to Identity of the SBC field. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: -Applicable: Skype for Business Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -When creating a new SBC, the identity must be identical to the -FQDN parameter, described above. If the parameter is not defined the Identity will be copied from the -FQDN parameter. The Identity parameter is not mandatory. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: -Applicable: Skype for Business Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaxConcurrentSessions -Used by the alerting system. When any value is set, the alerting system will generate an alert to the tenant administrator when the number of concurrent sessions is 90% or higher than this value. If the parameter is not set, alerts are not generated. However, the monitoring system will report the number of concurrent sessions every 24 hours. - -```yaml -Type: System.Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MediaBypass -Parameter indicates if the SBC supports Media Bypass and the administrator wants to use it for this SBC. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverResponseCodes -If Direct Routing receives any 4xx or 6xx SIP error code in response to an outgoing Invite the call is considered completed by default. (Outgoing in this context is a call from a Teams client to the PSTN with traffic flow: Teams Client -> Direct Routing -> SBC -> Telephony network). Setting the SIP codes in this parameter forces Direct Routing on receiving the specified codes try another SBC (if another SBC exists in the voice routing policy of the user). Find more information in the "Reference" section of "Phone System Direct Routing" documentation. - -```yaml -Type: Int -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: 408, 503, 504 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GatewaySiteId -PSTN Gateway Site Id. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GatewaySiteLbrEnabled -Used to enable this SBC to report assigned site location. Site location is used for Location Based Routing. When this parameter is enabled ($True), the SBC will report the site name as defined by the tenant administrator. On an incoming call to a Teams user the value of the site assigned to the SBC is compared with the value of the site assigned to the user to make a routing decision. The parameter is mandatory for enabling Location Based Routing feature. The default value is False ($False). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendSipOptions -Defines if an SBC will or will not send SIP Options messages. If disabled, the SBC will be excluded from the Monitoring and Alerting system. We highly recommend that you enable SIP Options. The default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $true -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SipSignalingPort -Listening port used for communicating with Direct Routing services by using the Transport Layer Security (TLS) protocol. Must be value between 1 and 65535. -Please note: Spelling of this parameter changed recently from SipSignallingPort to SipSignalingPort. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassMode -Possible values are "None", "Always" and "OnlyForLocalUsers". By setting "Always" mode you indicate that your network is fully routable. If a user usually in site "Seattle", travels to site "Tallinn" and tries to use SBC located in Seattle we will try to deliver the traffic to Seattle assuming that there is connection between Tallinn and Seattle offices. With "OnlyForLocaUsers" you indicate that there is no direct connection between sites. In example above, the traffic will not be send directly from Tallinn to Seattle. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GenerateRingingWhileLocatingUser -This parameter is applicableis only for Direct Routing in non-media bypass mode. Sometimes inbound calls from the public switched telephone network (PSTN) to Teams clients can take longer than expected to be established. This can occur for various reasons. When this happens, the caller might not hear anything, the Teams client doesn't ring, and the call might be canceled by some telecommunications providers. This parameter helps to avoid unexpected silences that can occur in this scenario. When enabled for inbound calls from the PSTN to Teams clients, a distinctive audio signal is played to the caller to indicate that Teams is in the process of establishing the call. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundTeamsNumberTranslationRules -This parameter assigns an ordered list of Teams translation rules, that apply to Teams numbers on inbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundPSTNNumberTranslationRules -Creates an ordered list of Teams translation rules, that apply to PSTN number on inbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutbundTeamsNumberTranslationRulesList -Creates an ordered list of Teams translation rules, that apply to Teams Number on outbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutboundPSTNNumberTranslationRulesList -Assigns an ordered list of Teams translation rules, that apply to PSTN number on outbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PidfloSupported -Enables PIDF-LO support on the PSTN Gateway. If turned on the .xml body payload is sent to the SBC with the location details of the user. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-CsOnlinePSTNGateway](Set-CsOnlinePSTNGateway.md) - -[Get-CsOnlinePSTNGateway](Get-CsOnlinePSTNGateway.md) - -[Remove-CsOnlinePSTNGateway](Remove-CsOnlinePSTNGateway.md) diff --git a/skype/skype-ps/skype/New-CsOnlineSession.md b/skype/skype-ps/skype/New-CsOnlineSession.md deleted file mode 100644 index 2e6bca2205..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineSession.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -external help file: SkypeOnlineConnectorStartup-help.xml -applicable: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinesession -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineSession - -## SYNOPSIS -Creates a persistent connection to Microsoft Skype for Business Online DataCenter. - -## SYNTAX - -### UserName (Default) -``` -New-CsOnlineSession [[-UserName] <String>] [-OverrideAdminDomain <String>] [-OverrideDiscoveryUri <Uri>] - [-OverridePowerShellUri <Uri>] [-OverrideAccessTokenResourceUri <Uri>] [-SessionOption <PSSessionOption>] - [<CommonParameters>] -``` - -### Credential -``` -New-CsOnlineSession [[-Credential] <PSCredential>] [-OverrideAdminDomain <String>] - [-OverrideDiscoveryUri <Uri>] [-OverridePowerShellUri <Uri>] [-OverrideAccessTokenResourceUri <Uri>] - [-SessionOption <PSSessionOption>] [<CommonParameters>] -``` - -### OAuthAccessToken -``` -New-CsOnlineSession [-OAuthAccessToken <SecureString>] [-OverrideAdminDomain <String>] - [-OverrideDiscoveryUri <Uri>] [-OverridePowerShellUri <Uri>] [-OverrideAccessTokenResourceUri <Uri>] - [-SessionOption <PSSessionOption>] [<CommonParameters>] -``` - -## DESCRIPTION -Enables you to create a remote Windows PowerShell session that connects to Skype for Business Online. -In this session, Skype for Business Online administrator can run Skype for Business cmdlets to manage users, policies and configurations. - -## EXAMPLES - -### EXAMPLE 1 -``` -New-CsOnlineSession -Credential User@Domain.com -``` - -Establishes a Skype for Business Online Remote PowerShell Session, supplying the credentials of a Skype for Business Online administrator account. - -### EXAMPLE 2 -``` -New-CsOnlineSession -Credential User@Domain.com -OverrideAdminDomain contoso.onmicrosoft.com -``` - -Establishes a Skype for Business Online Remote PowerShell Session, with a Skype for Business Online administrator account that has permission to manage the tenant contoso.onmicrosoft.com. -Please change the OverrideAdminDomain to your default tenant domain. - -### EXAMPLE 3 -``` -$sfbSession = New-CsOnlineSession -Import-PSSession $sfbSession -``` - -Establishes a Skype for Business Online Remote PowerShell Session using multi-factor authentication, for more information, see [Connect using a Skype for Business Online administrator account with multi-factor authentication](https://docs.microsoft.com/office365/enterprise/powershell/manage-skype-for-business-online-with-office-365-powershell#connect-using-a-skype-for-business-online-administrator-account-with-multi-factor-authentication). - -## PARAMETERS - -### -UserName -Specifies the Skype for Business Online administrator account name to be used when prompting for credentials. - -```yaml -Type: String -Parameter Sets: UserName -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Credential -Specifies a Skype for Business Online administrator, or Syndicated Partner administrator account. - -Type a Skype for Business Online administrator account name, such as "User@Domain.com", or enter a PSCredential object, such as one returned by the Get-Credential cmdlet. - -When you type an account name, you will be prompted for a password. - -```yaml -Type: PSCredential -Parameter Sets: Credential -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OAuthAccessToken -Specifies access token acquired already by the Skype for Business Online administrator, or Syndicated Partner Administrator. - -```yaml -Type: SecureString -Parameter Sets: OAuthAccessToken -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverrideAdminDomain -Specifies a default domain to be managed. -Optional. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverrideDiscoveryUri -Specifies Skype for Business Auto Discovery URI. -Optional. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverridePowerShellUri -Specifies Skype for Business Remote Powershell URI. -Optional. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverrideAccessTokenResourceUri -Specifies Skype for Business Remote Powershell Authorization Token URI. -Optional. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SessionOption -Sets advanced options for the session. -Enter a SessionOption object, such as one that you create by using the New-PSSessionOption cmdlet, or a hash table in which the keys are session option names and the values are session option values. - -```yaml -Type: PSSessionOption -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsOnlineTimeRange.md b/skype/skype-ps/skype/New-CsOnlineTimeRange.md deleted file mode 100644 index 46afff47cd..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineTimeRange.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinetimerange -applicable: Skype for Business Online -title: New-CsOnlineTimeRange -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineTimeRange - -## SYNOPSIS -The New-CsOnlineTimeRange cmdlet creates a new time range. - -## SYNTAX - -``` -New-CsOnlineTimeRange -Start <TimeSpan> -End <TimeSpan> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOnlineTimeRange cmdlet creates a new time range to be used with the Organizational Auto Attendant (OAA) service. Time ranges are used to form schedules. - -**NOTE** -- The start bound of the range must be less than its end bound. -- A time range must be aligned with 30/60-minutes boundaries. -- A time range can span from one minute to 24 hours. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$workdayTimeRange = New-CsOnlineTimeRange -Start 09:00 -End 17:00 -``` - -This example creates a time range for a 9AM to 5PM work day. - -### -------------------------- Example 2 -------------------------- -``` -$allDayTimeRange = New-CsOnlineTimeRange -Start 00:00 -End 1.00:00 -``` - -This example creates a 24-hour time range. - - -## PARAMETERS - -### -Start -The Start parameter represents the start bound of the time range. - -```yaml -Type: System.TimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -End -The End parameter represents the end bound of the time range. - -```yaml -Type: System.TimeSpan -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.TimeRange - - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsOnlineVoiceRoute.md b/skype/skype-ps/skype/New-CsOnlineVoiceRoute.md deleted file mode 100644 index 2c9d90ea7c..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineVoiceRoute.md +++ /dev/null @@ -1,285 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroute -applicable: Skype for Business Online -title: New-CsOnlineVoiceRoute -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineVoiceRoute - -## SYNOPSIS -Creates a new online voice route. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). - -## SYNTAX - -### Identity (Default) -``` -New-CsOnlineVoiceRoute [-Tenant <Guid>] [-Description <String>] [-NumberPattern <String>] - [-OnlinePstnUsages <PSListModifier>] [-OnlinePstnGatewayList <PSListModifier>] [-Priority <Int32>] - [-Identity] <XdsGlobalRelativeIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### ParentAndRelativeKey -``` -New-CsOnlineVoiceRoute [-Tenant <Guid>] -Name <String> [-Description <String>] [-NumberPattern <String>] - [-OnlinePstnUsages <PSListModifier>] [-OnlinePstnGatewayList <PSListModifier>] [-Priority <Int32>] [-InMemory] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to create a new online voice route. All online voice routes are created at the Global scope. However, multiple global voice routes can be defined. This is accomplished through the Identity parameter, which requires a unique route name. - -Voice routes are associated with online voice policies through online PSTN usages. A voice route includes a regular expression that identifies which phone numbers will be routed through a given voice route: phone numbers matching the regular expression will be routed through this route. - -This cmdlet is used when configuring Microsoft Phone System Direct Routing. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> New-CsOnlineVoiceRoute -Identity Route1 -``` - -The command in this example creates a new online voice route with an Identity of Route1. All other properties will be set to the default values. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> New-CsOnlineVoiceRoute -Identity Route1 -OnlinePstnUsages @{add="Long Distance"} -OnlinePstnGatewayList @{add="sbc1.litwareinc.com"} -``` - -The command in this example creates a new online voice route with an Identity of Route1. It also adds the online PSTN usage Long Distance to the list of usages and the service ID PstnGateway sbc1.litwareinc.com to the list of online PSTN gateways. - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> $x = (Get-CsOnlinePstnUsage).Usage - -New-CsOnlineVoiceRoute -Identity Route1 -OnlinePstnUsages @{add=$x} -``` - -This example creates a new online voice route named Route1 and populates that route's list of PSTN usages with all the existing usages for the organization. The first command in this example retrieves the list of global online PSTN usages. Notice that the call to the `Get-CsOnlinePstnUsage` cmdlet is in parentheses; this means that we first retrieve an object containing PSTN usage information. (Because there is only one, global, online PSTN usage, only one object will be retrieved.) The command then retrieves the Usage property of this object. That property, which contains a list of usages, is assigned to the variable $x. In the second line of this example, the `New-CsOnlineVoiceRoute` cmdlet is called to create a new online voice route. This voice route will have an identity of Route1. Notice the value passed to the OnlinePstnUsages parameter: @{add=$x}. This value says to add the contents of $x, which contain the phone usages list retrieved in line 1, to the list of online PSTN usages for this route. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A description of what this online voice route is for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses any confirmation prompts that would otherwise be displayed before making changes. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A name that uniquely identifies the online voice route. Voice routes can be defined only at the global scope, so the identity is simply the name you want to give the route. (You can have spaces in the route name, for instance Test Route, but you must enclose the full string in double quotes in the call to the New-CsOnlineVoiceRoute cmdlet.) - -If Identity is specified, the Name must be left blank. The value of the Identity will be assigned to the Name. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-<cmdlet>. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The unique name of the voice route. If this parameter is set, the value will be automatically applied to the online voice route Identity. You cannot specify both an Identity and a Name. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberPattern -A regular expression that specifies the phone numbers to which this route applies. Numbers matching this pattern will be routed according to the rest of the routing settings. - -Default: [0-9]{10} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlinePstnGatewayList -This parameter contains a list of online gateways associated with this online voice route. Each member of this list must be the service Identity of the online PSTN gateway. The service Identity is the fully qualified domain name (FQDN) of the pool or the IP address of the server. For example, redmondpool.litwareinc.com. - -By default this list is empty. However, if you leave this parameter blank when creating a new voice route, you'll receive a warning message. - -```yaml -Type: PSListModifier -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlinePstnUsages -A list of online PSTN usages (such as Local, Long Distance, etc.) that can be applied to this online voice route. The PSTN usage must be an existing usage (PSTN usages can be retrieved by calling the Get-CsOnlinePstnUsage cmdlet). - -By default this list is empty. However, if you leave this parameter blank when creating a new online voice route, you'll receive a warning message. - -```yaml -Type: PSListModifier -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -A number could resolve to multiple online voice routes. The priority determines the order in which the routes will be applied if more than one route is possible. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroute?view=skype-ps) - -[Set-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroute?view=skype-ps) - -[Remove-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroute?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsOnlineVoiceRoutingPolicy.md b/skype/skype-ps/skype/New-CsOnlineVoiceRoutingPolicy.md deleted file mode 100644 index 981be247c1..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineVoiceRoutingPolicy.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroutingpolicy -applicable: Skype for Business Online -title: New-CsOnlineVoiceRoutingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineVoiceRoutingPolicy - -## SYNOPSIS -Creates a new online voice routing policy. Online voice routing policies manage online PSTN usages for Phone System users. - -## SYNTAX -### Identity -``` -New-CsOnlineVoiceRoutingPolicy [-Tenant <Guid>] [-OnlinePstnUsages <PSListModifier>] - [-Description <String>] [-RouteType <String>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. - -Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> New-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages "Long Distance" -``` - -The command shown in Example 1 creates a new online per-user voice routing policy with the Identity RedmondOnlineVoiceRoutingPolicy. This policy is assigned a single online PSTN usage: Long Distance. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> New-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages "Long Distance", "Local", "Internal" -``` - -Example 2 is a variation of the command shown in Example 1; in this case, however, the new policy is assigned three online PSTN usages: Long Distance; Local; Internal. Multiple usages can be assigned simply by separating each usage using a comma. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Enables administrators to provide explanatory text to accompany an online voice routing policy. For example, the Description might include information about the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier assigned to the policy when it was created. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlinePstnUsages -A list of online PSTN usages (such as Local or Long Distance) that can be applied to this online voice routing policy. The online PSTN usage must be an existing usage (PSTN usages can be retrieved by calling the `Get-CsOnlinePstnUsage` cmdlet). - -```yaml -Type: PSListModifier -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RouteType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose online voice routing policy is being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroutingpolicy?view=skype-ps) - -[Set-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroutingpolicy?view=skype-ps) - -[Grant-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoiceroutingpolicy?view=skype-ps) - -[Remove-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroutingpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsOnlineVoicemailPolicy.md b/skype/skype-ps/skype/New-CsOnlineVoicemailPolicy.md deleted file mode 100644 index 2edb83ef1e..0000000000 --- a/skype/skype-ps/skype/New-CsOnlineVoicemailPolicy.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlinevoicemailpolicy -applicable: Skype for Business Online -title: New-CsOnlineVoicemailPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOnlineVoicemailPolicy - -## SYNOPSIS -Creates a new Online Voicemail policy. Online Voicemail policies determine whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify voicemail maximum recording length for a user. - -## SYNTAX - -``` -New-CsOnlineVoicemailPolicy -Identity <XdsIdentity> [-Tenant <Guid>] [-EnableTranscription <Boolean>] [-ShareData <String>] - [-EnableTranscriptionProfanityMasking <Boolean>] [-EnableTranscriptionTranslation <Boolean>] [-EnableEditingCallAnswerRulesSetting <Boolean>] [-MaximumRecordingLength <Duration>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Online Voicemail service provides organizations with voicemail deposit capabilities for Phone System implementation. - -By default, users enabled for Phone System will be enabled for Online Voicemail, and Online Voicemail policy controls whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify voicemail maximum recording length for a user. Online Voicemail transcription is enabled by default, transcription profanity masking is disabled by default, transcription translation is enabled by default, editing call answer rule settings is enabled by default, and voicemail maximum recording length is set to 5 minutes by default. Tenant admin would be able to create customized online voicemail policy to match the organization's requirements. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsOnlineVoicemailPolicy -Identity "CustomOnlineVoicemailPolicy" -MaximumRecordingLength ([TimeSpan]::FromSeconds(60)) -``` - -The command shown in Example 1 creates a per-user online voicemail policy CustomOnlineVoicemailPolicy with MaximumRecordingLength set to 60 seconds and other fields set to tenant level global value. - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTranscription -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTranscriptionProfanityMasking -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTranscriptionTranslation -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableEditingCallAnswerRulesSetting -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumRecordingLength -A duration of voicemail maximum recording length. The length should be between 30 seconds to 10 minutes. - -```yaml -Type: Duration -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier specifying the scope, and in some cases the name, of the policy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the Skype for Business Online tenant account whose voicemail policy is to be retrieved. For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" You can return the tenant ID for each of your tenants by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoicemailpolicy?view=skype-ps) - -[Set-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailpolicy?view=skype-ps) - -[Remove-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoicemailpolicy?view=skype-ps) - -[Grant-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoicemailpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendant.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendant.md deleted file mode 100644 index e4be6d3edb..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendant.md +++ /dev/null @@ -1,502 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendant -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendant - -## SYNOPSIS -Use the New-CsOrganizationalAutoAttendant cmdlet to create a new Auto Attendant (AA). - -## SYNTAX - -``` -New-CsOrganizationalAutoAttendant -Name <String> [-Domain <String>] [-LineUris <>] -LanguageId <String> - [-VoiceId <String>] -DefaultCallFlow <CallFlow> [-Operator <CallableEntity>] [-EnableVoiceResponse] - [-ApplicationId <Guid>] [-CallbackUri <Uri>] [-Ring <String>] [-ClientAudience <Uri>] - -TimeZoneId <String> [-CallFlows <List>] [-Schedules <List>] [-CallHandlingAssociations <List>] - [-InclusionScope <DialScope>] [-ExclusionScope <DialScope>] [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Auto Attendants (AAs) are a key element in the Cloud PBX application. -Each OAA can be associated with a phone number that allows callers to reach specific people in the organization through a directory lookup. -Alternatively, it can route the calls to an operator, a user, another OAA, or a call queue. - -You can create new OAAs by using the New-CsOrganizationalAutoAttendant cmdlet; each newly created OAA gets assigned a random Primary (SIP) URI that serves as the identity of the OAA. - -**NOTE** -- PrimaryUri of OAAs is a SIP URI. -- The default call flow has the lowest precedence, and any custom call flow has a higher precedence and is executed if the schedule associated with it is in effect. -- Holiday call flows have higher priority than after-hours call flows. Thus, if a holiday schedule and an after-hours schedule are both in effect at a particular time, the call flow corresponding to the holiday call flow will be rendered. -- The default call flow can be used either as the 24/7 call flow if no other call flows are specified, or as the business hours call flow if an "after hours" call flow was specified together with the corresponding schedule and call handling association. -- If a user is present in both inclusion and exclusion scopes, then exclusion scope always takes priority, i.e., the user will not be able to be contacted through directory lookup feature. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$lineUri = [System.Uri] "tel:+11098765432" - -$operatorUri = "sip:operator@contoso.com" -$operatorEntity = New-CsOrganizationalAutoAttendantCallableEntity -Identity $operatorUri -Type User - -$greetingPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" -$menuOptionZero = New-CsOrganizationalAutoAttendantMenuOption -Action TransferCallToOperator -DtmfResponse Tone0 -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign or press 0 to reach the operator." -$defaultMenu = New-CsOrganizationalAutoAttendantMenu -Name "Default menu" -Prompts @($menuPrompt) -MenuOptions @($menuOptionZero) -EnableDialByName -$defaultCallFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Default call flow" -Greetings @($greetingPrompt) -Menu $defaultMenu - -$afterHoursGreetingPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso! Unfortunately, you have reached us outside of our business hours. We value your call please call us back Monday to Friday, between 9 A.M. to 12 P.M. and 1 P.M. to 5 P.M. Goodbye!" -$automaticMenuOption = New-CsOrganizationalAutoAttendantMenuOption -Action Disconnect -DtmfResponse Automatic -$afterHoursMenu=New-CsOrganizationalAutoAttendantMenu -Name "After Hours menu" -MenuOptions @($automaticMenuOption) -$afterHoursCallFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "After Hours call flow" -Greetings @($afterHoursGreetingPrompt) -Menu $afterHoursMenu - -$timerange1 = New-CsOnlineTimeRange -Start 09:00 -end 12:00 -$timerange2 = New-CsOnlineTimeRange -Start 13:00 -end 17:00 -$afterHoursSchedule = New-CsOnlineSchedule -Name "After Hours Schedule" -WeeklyRecurrentSchedule -MondayHours @($timerange1, $timerange2) -TuesdayHours @($timerange1, $timerange2) -WednesdayHours @($timerange1, $timerange2) -ThursdayHours @($timerange1, $timerange2) -FridayHours @($timerange1, $timerange2) -Complement - -$afterHoursCallHandlingAssociation = New-CsOrganizationalAutoAttendantCallHandlingAssociation -Type AfterHours -ScheduleId $afterHoursSchedule.Id -CallFlowId $afterHoursCallFlow.Id - -$inclusionScopeGroupIds = @("4c3053a6-20bf-43df-bf7a-156124168856") -$inclusionScope = New-CsOrganizationalAutoAttendantDialScope -GroupScope -GroupIds $inclusionScopeGroupIds - -$o=New-CsOrganizationalAutoAttendant -Name "Main auto attendant" -LineUris @($lineUri) -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -Schedules @($afterHoursSchedule) -CallFlows @($afterHoursCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation) -Language "en-US" -TimeZoneId "UTC" -Operator $operatorEntity -InclusionScope $inclusionScope -``` - -This example creates a new OAA named _Main auto attendant_ that has the following properties: - -- A phone number is assigned. -- It sets a default call flow. -- It sets an after-hours call flow. -- It enables voice response. -- The default language is en-US. -- The time zone is set to UTC. -- An inclusion scope is specified. - -### -------------------------- Example 2 -------------------------- -``` -$lineUri = [System.Uri] "tel:+11098765432" - -$operatorUri = "sip:operator@contoso.com" -$operatorEntity = New-CsOrganizationalAutoAttendantCallableEntity -Identity $operatorUri -Type User - -$dcfGreetingPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" -$dcfMenuOptionZero = New-CsOrganizationalAutoAttendantMenuOption -Action TransferCallToOperator -DtmfResponse Tone0 -$dcfMenuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign or press 0 to reach the operator." -$dcfMenu=New-CsOrganizationalAutoAttendantMenu -Name "Default menu" -Prompts @($dcfMenuPrompt) -MenuOptions @($dcfMenuOptionZero) -EnableDialByName -$defaultCallFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Default call flow" -Greetings @($dcfGreetingPrompt) -Menu $dcfMenu - -$afterHoursGreetingPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso! Unfortunately, you have reached us outside of our business hours. We value your call please call us back Monday to Friday, between 9 A.M. to 12 P.M. and 1 P.M. to 5 P.M. Goodbye!" -$afterHoursMenuOption = New-CsOrganizationalAutoAttendantMenuOption -Action DisconnectCall -DtmfResponse Automatic -$afterHoursMenu=New-CsOrganizationalAutoAttendantMenu -Name "After Hours menu" -MenuOptions @($afterHoursMenuOption) -$afterHoursCallFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "After Hours call flow" -Greetings @($afterHoursGreetingPrompt) -Menu $afterHoursMenu - -$timerange1 = New-CsOnlineTimeRange -Start 09:00 -end 12:00 -$timerange2 = New-CsOnlineTimeRange -Start 13:00 -end 17:00 -$afterHoursSchedule = New-CsOnlineSchedule -Name "After Hours Schedule" -WeeklyRecurrentSchedule -MondayHours @($timerange1, $timerange2) -TuesdayHours @($timerange1, $timerange2) -WednesdayHours @($timerange1, $timerange2) -ThursdayHours @($timerange1, $timerange2) -FridayHours @($timerange1, $timerange2) -Complement - -$afterHoursCallHandlingAssociation = New-CsOrganizationalAutoAttendantCallHandlingAssociation -Type AfterHours -ScheduleId $afterHoursSchedule.Id -CallFlowId $afterHoursCallFlow.Id - -$christmasGreetingPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Our offices are closed for Christmas from December 24 to December 26. Please call back later." -$christmasMenuOption = New-CsOrganizationalAutoAttendantMenuOption -Action DisconnectCall -DtmfResponse Automatic -$christmasMenu = New-CsOrganizationalAutoAttendantMenu -Name "Christmas Menu" -MenuOptions @($christmasMenuOption) -$christmasCallFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Christmas" -Greetings @($christmasGreetingPrompt) -Menu $christmasMenu - -$dtr = New-CsOnlineDateTimeRange -Start "24/12/2017" -End "26/12/2017" -$christmasSchedule = New-CsOnlineSchedule -Name "Christmas" -FixedSchedule -DateTimeRanges @($dtr) - -$christmasCallHandlingAssociation = New-CsOrganizationalAutoAttendantCallHandlingAssociation -Type Holiday -ScheduleId $christmasSchedule.Id -CallFlowId $christmasCallFlow.Id - -$o=New-CsOrganizationalAutoAttendant -Name "Main auto attendant" -LineUris @($lineUri) -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -Schedules @($afterHoursSchedule, $christmasSchedule) -CallFlows @($afterHoursCallFlow, $christmasCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation, $christmasCallHandlingAssociation) -Language "en-US" -TimeZoneId "UTC" -Operator $operatorEntity -``` - -This example creates a new OAA named _Main auto attendant_ that has the following properties: - -- A phone number is assigned. -- It sets a default call flow. -- It sets an after-hours call flow. -- It sets a call flow for Christmas holiday. -- It enables voice response. -- The default language is en-US. -- The time zone is set to UTC. - -## PARAMETERS - -### -Name -The Name parameter is a friendly name that is assigned to the OAA. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LanguageId -The LanguageId parameter is the language that is used to read text-to-speech (TTS) prompts. - -You can query the supported languages using the Get-CsOrganizationalAutoAttendantSupportedLanguage cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeZoneId -The TimeZoneId parameter represents the OAA time zone. All schedules are evaluated based on this time zone. - -You can query the supported timezones using the Get-CsOrganizationalAutoAttendantSupportedTimeZone cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultCallFlow -The DefaultCallFlow parameter is the flow to be executed when no other call flow is in effect (for example, during business hours). - -You can create the DefaultCallFlow by using the New-CsOrganizationalAutoAttendantCallFlow cmdlet. - -```yaml -Type: CallFlow -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallFlows -The CallFlows parameter represents call flows, which are required if they are referenced in the Associations parameter. - -You can create CallFlows by using the New-CsOrganizationalAutoAttendantCallFlow cmdlet. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Schedules -The Schedules parameter reflects schedules that are associated with the OAA. Schedules are required if they are referenced in the CallHandlingAssociations parameter. - -You can create schedules by using the New-CsOnlineSchedule cmdlet. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallHandlingAssociations -The CallHandlingAssociations parameter represents the call handling associations. -The OAA service uses call handling associations to determine which call flow to execute when a specific schedule is in effect. - -You can create CallHandlingAssociations by using the New-CsOrganizationalAutoAttendantCallHandlingAssociation cmdlet. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LineUris -The LineUris parameter represents PSTN numbers that are assigned to the OAA. -PSTN numbers must be your Service number or Toll-free number; User PSTN Numbers (normal numbers) cannot be added to Auto Attendant. -Each Uniform Resource Identifier (URI) must be specified by using the following format: the tel: prefix followed by a plus sign, followed by the country/region calling code, area code, and phone number (using only digits, no blank spaces, periods, or hyphens). -For example: `-LineUris [System.Uri]"tel:+4255551219"`. - -Note: Only PSTN numbers that are acquired through or migrated to Skype for Business Online are supported. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Operator -The Operator parameter represents the SIP address or PSTN number of the operator. - -You can create callable entities by using the New-CsOrganizationalAutoAttendantCallableEntity cmdlet. - -```yaml -Type: CallableEntity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Domain -The Domain parameter represents the domain part of the Primary (SIP) URI that is generated for the OAA. -The domain name is validated against the list of domains that are configured by the tenant. -If not provided, then a domain is randomly chosen for primary URI. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VoiceId -The VoiceId parameter represents the voice that is used to read text-to-speech (TTS) prompts. - -You can query the supported voices by using the Get-CsOrganizationalAutoAttendantSupportedLanguage cmdlet. You can determine the default voice for a language by issuing the following command: - -``` -$language = Get-CsOrganizationalAutoAttendantSupportedLanguage -Identity "en-US"` -$defaultVoice = $language.Voices[0].Gender -``` - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableVoiceResponse -The EnableVoiceResponse parameter indicates whether voice response for OAA is enabled. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InclusionScope -Specifies the users to which call transfers are allowed through directory lookup feature. -If not specified, all users in the organization can be reached through directory lookup. - -Dial scopes can be created by using the New-CsOrganizationalAutoAttendantDialScope cmdlet. - -```yaml -Type: DialScope -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExclusionScope -Specifies the users to which call transfers are not allowed through directory lookup feature. -If not specified, no user in the organization is excluded from directory lookup. - -Dial scopes can be created by using the New-CsOrganizationalAutoAttendantDialScope cmdlet. - - -```yaml -Type: DialScope -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationId -Specifies a custom application ID to use for OAAs. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallbackUri -Specifies a custom Callback URI for OAAs. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClientAudience -Specifies a custom client audience for OAAs. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Ring -Specifies a custom ring for OAAs. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.OAA.Models.OrgAutoAttendant - - -## NOTES - - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendantCallFlow](New-CsOrganizationalAutoAttendantCallFlow.md) - -[New-CsOrganizationalAutoAttendantCallHandlingAssociation](New-CsOrganizationalAutoAttendantCallHandlingAssociation.md) - -[New-CsOrganizationalAutoAttendantCallableEntity](New-CsOrganizationalAutoAttendantCallableEntity.md) - -[New-CsOnlineSchedule](New-CsOnlineSchedule.md) - -[Get-CsOrganizationalAutoAttendantSupportedLanguage](Get-CsOrganizationalAutoAttendantSupportedLanguage.md) - -[Get-CsOrganizationalAutoAttendantSupportedTimeZone](Get-CsOrganizationalAutoAttendantSupportedTimeZone.md) - diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallFlow.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallFlow.md deleted file mode 100644 index 2357890505..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallFlow.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendantcallflow -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendantCallFlow -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendantCallFlow - -## SYNOPSIS -Use the New-CsOrganizationalAutoAttendantCallFlow cmdlet to create a new call flow. - -## SYNTAX - -``` -New-CsOrganizationalAutoAttendantCallFlow -Name <String> [-Greetings <List>] -Menu <Menu> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOrganizationalAutoAttendantCallFlow cmdlet creates a new call flow for use with the Auto Attendant (AA) service. The OAA service uses the call flow to handle inbound calls by playing a greeting (if present), and provide callers with actions through a menu. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$menu = New-CsOrganizationalAutoAttendantMenu -Name "Default Menu" -Prompts @($menuPrompt) -EnableDialByName -$callFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu -``` - -This example creates a new call flow that renders the "Default Menu" menu. - -### -------------------------- Example 2 -------------------------- -``` -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$menu = New-CsOrganizationalAutoAttendantMenu -Name "Default Menu" -Prompts $menuPrompt -EnableDialByName -$greeting = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" -$callFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu -Greetings $greeting -``` - -This example creates a new call flow that plays a greeting before rendering the "Default Menu" menu. - -## PARAMETERS - -### -Name -The Name parameter represents a unique friendly name for the call flow. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Menu -The Menu parameter identifies the menu to render when the call flow is executed. - -You can create a new menu by using the New-CsOrganizationalAutoAttendantMenu cmdlet. - -```yaml -Type: Menu -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Greetings -If present, the prompts specified by the Greetings parameter (either TTS or Audio) are played before the call flow's menu is rendered. - -You can create prompts by using the New-CsOrganizationalAutoAttendantPrompt cmdlet. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.CallFlow - - -## NOTES - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendantMenu](New-CsOrganizationalAutoAttendantMenu.md) - -[New-CsOrganizationalAutoAttendantPrompt](New-CsOrganizationalAutoAttendantPrompt.md) diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallHandlingAssociation.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallHandlingAssociation.md deleted file mode 100644 index c55ed7102f..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallHandlingAssociation.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendantcallhandlingassociation -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendantCallHandlingAssociation -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendantCallHandlingAssociation - -## SYNOPSIS -Use the New-CsOrganizationalAutoAttendantCallHandlingAssociation cmdlet to create a new call handling association. - -## SYNTAX - -``` -New-CsOrganizationalAutoAttendantCallHandlingAssociation -CallFlowId <String> -ScheduleId <String> -Type <AfterHours | Holiday> [-Disable] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOrganizationalAutoAttendantCallHandlingAssociation cmdlet creates a new call handling association to be used with the Auto Attendant (AA) service. The OAA service uses call handling associations to determine which call flow to execute when a specific schedule is in effect. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$tr = New-CsOnlineTimeRange -Start 09:00 -End 17:00 -$schedule = New-CsOnlineSchedule -Name "Business Hours" -WeeklyRecurrentSchedule -MondayHours @($tr) -$scheduleId = $schedule.Id - -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$menu = New-CsOrganizationalAutoAttendantMenu -Name "Default Menu" -Prompts $menuPrompt -EnableDialByName -$callFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu -$callFlowId = $callFlow.Id - -$callHandlingAssociation = New-CsOrganizationalAutoAttendantCallHandlingAssociation -Type AfterHours -ScheduleId $scheduleId -CallFlowId $callFlowId -``` - -This example creates a new after-hours call handling association. - -### -------------------------- Example 2 -------------------------- -``` -$tr = New-CsOnlineTimeRange -Start 09:00 -End 17:00 -$schedule = New-CsOnlineSchedule -Name "Business Hours" -WeeklyRecurrentSchedule -MondayHours @($tr) -$scheduleId = $schedule.Id - -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$menu = New-CsOrganizationalAutoAttendantMenu -Name "Default Menu" -Prompts $menuPrompt -EnableDialByName -$callFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu -$callFlowId = $callFlow.Id - -$disabledCallHandlingAssociation = New-CsOrganizationalAutoAttendantCallHandlingAssociation -Type AfterHours -ScheduleId $scheduleId -CallFlowId $callFlowId -Disable -``` - -This example creates a disabled after-hours call handling association. - -### -------------------------- Example 3 -------------------------- -``` -$dtr = New-CsOnlineDateTimeRange -Start "24/12/2017" -$schedule = New-CsOnlineSchedule -Name "Christmas" -FixedSchedule -DateTimeRanges @($dtr) -$scheduleId = $schedule.Id - -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "We are closed for Christmas. Please call back later." -$menuOption = New-CsOrganizationalAutoAttendantMenuOption -DtmfResponse Automatic -Action DisconnectCall -$menu = New-CsOrganizationalAutoAttendantMenu -Name "Christmas Menu" -MenuOptions @($menuOption) -$callFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Christmas" -Greetings @($greeting) -Menu $menu -$callFlowId = $callFlow.Id - -$callHandlingAssociation = New-CsOrganizationalAutoAttendantCallHandlingAssociation -Type Holiday -ScheduleId $scheduleId -CallFlowId $callFlowId -``` - -This example creates a holiday call handling association. - -## PARAMETERS - -### -CallFlowId -The CallFlowId parameter represents the call flow to be associated with the schedule. - -You can create a call flow by using the New-CsOrganizationalAutoAttendantCallFlow cmdlet. - - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScheduleId -The ScheduleId parameter represents the schedule to be associated with the call flow. - -You can create a schedule by using the New-CsOnlineSchedule cmdlet - - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -The Type parameter represents the type of the call handling association. Currently, only AfterHours and Holiday are supported. - - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Disable -The Disable parameter, if set, establishes that the call handling association is created as disabled. This parameter can only be used when the Type parameter is set to AfterHours. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.OAA.Models.CallHandlingAssociation - - -## NOTES - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendantCallFlow](New-CsOrganizationalAutoAttendantCallFlow.md) - -[New-CsOnlineSchedule](New-CsOnlineSchedule.md) diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallableEntity.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallableEntity.md deleted file mode 100644 index 94c5274504..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantCallableEntity.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendantcallableentity -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendantCallableEntity -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendantCallableEntity - -## SYNOPSIS -The New-CsOrganizationalAutoAttendantCallableEntity cmdlet lets you create a callable entity. - -## SYNTAX - -``` -New-CsOrganizationalAutoAttendantCallableEntity -Identity <String> -Type <User | OrganizationalAutoAttendant | HuntGroup> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOrganizationalAutoAttendantCallableEntity cmdlet lets you create a callable entity for use with call transfers from the Auto Attendant service. Callable entities can be created using either SIP or TEL URIs and can refer to any of the following entities: - -- User -- OrganizationalAutoAttendant -- HuntGroup - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$callableEntity = New-CsOrganizationalAutoAttendantCallableEntity -Identity sip:operator@contoso.com -Type User -``` - -This example creates a user callable entity. - -### -------------------------- Example 2 -------------------------- -``` -$callableEntity = New-CsOrganizationalAutoAttendantCallableEntity -Identity "tel:+1234567890" -Type OrganizationalAutoAttendant -``` - -This example creates an auto attendant callable entity. - -## PARAMETERS - -### -Identity -The Identity parameter represents the ID of the callable entity; this can be either a SIP URI or a TEL URI. - -- Only the SIP URIs of users that have Enterprise Voice enabled are supported. -- Only PSTN numbers that are acquired and assigned through Skype for Business Online are supported. -- SIP URIs can be used for a user only. -- TEL URIs can be a user, an auto attendant, or a hunt group (call queue). - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Type -The Type parameter represents the type of the callable entity, which can be any of the following: - -- User -- OrganizationalAutoAttendant -- Huntgroup - - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.CallableEntity - - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantDialScope.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantDialScope.md deleted file mode 100644 index e042097e6c..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantDialScope.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendantdialscope -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendantDialScope -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendantDialScope - -## SYNOPSIS -Use New-CsOrganizationalAutoAttendantDialScope cmdlet to create dial-scopes for use with Auto Attendant (AA) service. - -## SYNTAX - -``` -New-CsOrganizationalAutoAttendantDialScope -GroupScope -GroupIds <List> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet creates a new dial-scope to be used with Auto Attendant (AA) service. OAAs use dial-scopes to restrict the scope of call transfers that can be made through directory lookup feature. - -**NOTE** -- The returned dial-scope model composes a member for the underlying type/implementation, e.g. in case of the group-based dial scope, in order to modify its Group IDs, you can access them through `DialScope.GroupScope.GroupIds`. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$groupIds = @("00000000-0000-0000-0000-000000000000") -$dialScope = New-CsOrganizationalAutoAttendantDialScope -GroupScope -GroupIds $groupIds -``` - -In Example 1, the New-CsOrganizationalAutoAttendantDialScope cmdlet is used to create a dial-scope with a group whose id is 00000000-0000-0000-0000-000000000000. - -## PARAMETERS - -### -GroupScope -Indicates that a dial-scope based on groups (distribution lists, security groups) is to be created. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GroupIds -Refers to the IDs of the groups that are to be included in the dial-scope. - -Group IDs can be obtained by using the Find-CsGroup cmdlet. - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.OAA.Models.DialScope - - -## NOTES - -## RELATED LINKS - - diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantMenu.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantMenu.md deleted file mode 100644 index b72a96d024..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantMenu.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendantmenu -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendantMenu -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendantMenu - -## SYNOPSIS -The New-CsOrganizationalAutoAttendantMenu cmdlet creates a new menu. - -## SYNTAX - -``` -New-CsOrganizationalAutoAttendantMenu -Name <String> -MenuOptions <List> [-Prompts <List>] [-EnableDialByName] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOrganizationalAutoAttendantMenu cmdlet creates a new menu for the Auto Attendant (AA) service. The OAA service uses menus to provide callers with choices, and then takes action based on the selection. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$menu = New-CsOrganizationalAutoAttendantMenu -Name "Default Menu" -Prompts @($menuPrompt) -EnableDialByName -``` - -This example creates a new menu that allows the caller to reach a target by name. - -### -------------------------- Example 2 -------------------------- -``` -$menuOptionZero = New-CsOrganizationalAutoAttendantMenuOption -Action TransferCallToOperator -DtmfResponse Tone0 -$menuPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign. For operator, press zero." -$menu = New-CsOrganizationalAutoAttendantMenu -Name "Default Menu" -Prompts @($menuPrompt) -MenuOptions @($menuOptionZero) -EnableDialByName -``` - -This example creates a new menu that allows the caller to reach a target by name or the operator by pressing the 0 key. - - -## PARAMETERS - -### -Name -The Name parameter represents a friendly name for the menu. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MenuOptions -The MenuOptions parameter is a list of menu options for this menu. These menu options specify what action to take when the user sends a particular input. - -You can create menu options by using the New-CsOrganizationalAutoAttendantMenuOption cmdlet. - - -```yaml -Type: System.Collections.Generic.List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Prompts -The Prompts parameter reflects the prompts to play when the menu is activated. - -You can create new prompts by using the New-CsOrganizationalAutoAttendantPrompt cmdlet. - - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableDialByName -The EnableDialByName parameter lets users do a directory search by recipient name and get transferred to the party. - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.Menu - - -## NOTES - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendantMenuOption](New-CsOrganizationalAutoAttendantMenuOption.md) -[New-CsOrganizationalAutoAttendantPrompt](New-CsOrganizationalAutoAttendantPrompt.md) - diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantMenuOption.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantMenuOption.md deleted file mode 100644 index 83fbcc1287..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantMenuOption.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendantmenuoption -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendantMenuOption -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendantMenuOption - -## SYNOPSIS -Use the New-CsOrganizationalAutoAttendantMenuOption cmdlet to create a new menu option. - -## SYNTAX - -``` -New-CsOrganizationalAutoAttendantMenuOption -Action <ActionType> -DtmfResponse <DtmfTone> [-VoiceResponses <List>] - [-CallTarget <CallableEntity>] [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOrganizationalAutoAttendantMenuOption cmdlet creates a new menu option for the Auto Attendant (AA) service. The OAA service uses the menu options to respond to a caller with the appropriate action. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$menuOption = New-CsOrganizationalAutoAttendantMenuOption -Action TransferCallToOperator -DtmfResponse Tone0 -``` - -This example creates a menu option to call the operator when the 0 key is pressed. - -### -------------------------- Example 2 -------------------------- -``` -$troubleShootUri = "sip:troubleShoot@contoso.com" -$troubleShootEntity = New-CsOrganizationalAutoAttendantCallableEntity -Identity $troubleShootUri -Type OrganizationalAutoAttendant -$menuOption = New-CsOrganizationalAutoAttendantMenuOption -Action TransferCallToTarget -DtmfResponse Tone1 -VoiceResponses "Sales" -CallTarget $troubleShootEntity -``` - -This example creates a menu option to transfer the call to an auto attendant when the caller speaks the word "Sales" or presses the 1 key. - - -## PARAMETERS - -### -Action -The Action parameter represents the action to be taken when the menu option is activated. The Action must be set to one of the following values: - -- DisconnectCall - The call is disconnected. -- TransferCallToOperator - the call is transferred to the operator. -- TransferCallToTarget - The call is transferred to the menu option's call target. - -```yaml -Type: ActionType -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DtmfResponse -The DtmfResponse parameter indicates the key on the telephone keypad to be pressed to activate the menu option. The DtmfResponse must be set to one of the following values: - -- Tone0 to Tone9 - Corresponds to DTMF tones from 0 to 9. -- Automatic - The action is executed without user response. - -```yaml -Type: DtmfTone -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VoiceResponses -The VoiceResponses parameter represents the voice responses to select a menu option when Voice Responses are enabled for the auto attendant. - -Voice responses are currently limited to one voice response per menu option. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallTarget -The CallTarget parameter represents the target for call transfer after the menu option is selected. - -CallTarget is required if the action of the menu option is TransferCallToTarget. - -Use the New-CsOrganizationalAutoAttendantCallableEntity cmdlet to create new callable entities. - -```yaml -Type: CallableEntity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.MenuOption - - -## NOTES - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendantCallableEntity](New-CsOrganizationalAutoAttendantCallableEntity.md) diff --git a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantPrompt.md b/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantPrompt.md deleted file mode 100644 index 9cd13bde52..0000000000 --- a/skype/skype-ps/skype/New-CsOrganizationalAutoAttendantPrompt.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csorganizationalautoattendantprompt -applicable: Skype for Business Online -title: New-CsOrganizationalAutoAttendantPrompt -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsOrganizationalAutoAttendantPrompt - -## SYNOPSIS -Use the New-CsOrganizationalAutoAttendantPrompt cmdlet to create a new prompt. - -## SYNTAX - -### AudioFileParamSet (Default) -``` -New-CsOrganizationalAutoAttendantPrompt -AudioFilePrompt <AudioFile> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -### DualParamSet -``` -New-CsOrganizationalAutoAttendantPrompt -ActiveType <PromptType> [-AudioFilePrompt <AudioFile>] - [-TextToSpeechPrompt <String>] [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -### TextToSpeechParamSet -``` -New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt <String> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -The New-CsOrganizationalAutoAttendantPrompt cmdlet creates a new prompt for the Auto Attendant (AA) service. A prompt is either an audio file that is played, or text that is read aloud to give callers additional information. A prompt can be disabled by setting the ActiveType to None. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$ttsPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" -``` - -This example creates a new prompt that reads the supplied text. - - - -### -------------------------- Example 2 -------------------------- -``` -$content = Get-Content "C:\Media\Welcome.wav" -Encoding byte -ReadCount 0 -$audioFile = New-CsOnlineAudioFile -FileName "hello.wav" -Content $content -$audioFilePrompt = New-CsOrganizationalAutoAttendantPrompt -AudioFilePrompt $audioFile -``` - -This example creates a new prompt that plays the selected audio file. - -### -------------------------- Example 3 -------------------------- -``` -$content = Get-Content "C:\Media\Welcome.wav" -Encoding byte -ReadCount 0 -$audioFile = New-CsOnlineAudioFile -FileName "hello.wav" -Content $content -$dualPrompt = New-CsOrganizationalAutoAttendantPrompt -ActiveType AudioFile -AudioFilePrompt $audioFile -TextToSpeechPrompt "Welcome to Contoso!" -``` - -This example creates a new prompt that has both audio file and text-to-speech data, but will play the audio file when the prompt is activated (rendered). - - -## PARAMETERS - -### -ActiveType -PARAMVALUE: None | TextToSpeech | AudioFile - -The ActiveType parameter identifies the active type (modality) of the OAA prompt. It can be set to None (the prompt is disabled), TextToSpeech (text-to-speech is played when the prompt is rendered) or AudioFile (audio file data is played when the prompt is rendered). - -This is explicitly required if both Audio File and TTS prompts are specified. Otherwise, it is inferred. - -```yaml -Type: PromptType -Parameter Sets: Dual -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AudioFilePrompt -The AudioFilePrompt parameter represents the audio to play when the prompt is activated (rendered). - -This parameter is required when audio file prompts are being created. You can create audio files by using the New-CsOnlineAudioFile cmdlet. - -```yaml -Type: AudioFile -Parameter Sets: AudioFile, Dual -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TextToSpeechPrompt -The TextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt that is to be read when the prompt is activated. - -This parameter is required when text to speech prompts are being created. - -```yaml -Type: String -Parameter Sets: TextToSpeech, Dual -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### None - - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.Prompt - - -## NOTES - -## RELATED LINKS - -[New-CsOnlineAudioFile](New-CsOnlineAudioFile.md) - diff --git a/skype/skype-ps/skype/New-CsOutboundCallingNumberTranslationRule.md b/skype/skype-ps/skype/New-CsOutboundCallingNumberTranslationRule.md index 8d31f123e6..db567dff75 100644 --- a/skype/skype-ps/skype/New-CsOutboundCallingNumberTranslationRule.md +++ b/skype/skype-ps/skype/New-CsOutboundCallingNumberTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csoutboundcallingnumbertranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/new-csoutboundcallingnumbertranslationrule applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsOutboundCallingNumberTranslationRule schema: 2.0.0 @@ -294,5 +294,3 @@ The New-CsOutboundCallingNumberTranslationRule cmdlet creates new instances of t [Remove-CsOutboundCallingNumberTranslationRule](Remove-CsOutboundCallingNumberTranslationRule.md) [Set-CsOutboundCallingNumberTranslationRule](Set-CsOutboundCallingNumberTranslationRule.md) - - diff --git a/skype/skype-ps/skype/New-CsOutboundTranslationRule.md b/skype/skype-ps/skype/New-CsOutboundTranslationRule.md index 08932e99fe..73e18b5b4f 100644 --- a/skype/skype-ps/skype/New-CsOutboundTranslationRule.md +++ b/skype/skype-ps/skype/New-CsOutboundTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csoutboundtranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/new-csoutboundtranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsOutboundTranslationRule schema: 2.0.0 @@ -297,5 +297,3 @@ This cmdlet creates an object of type Microsoft.Rtc.Management.WritableConfig.Se [Set-CsOutboundTranslationRule](Set-CsOutboundTranslationRule.md) [Get-CsOutboundTranslationRule](Get-CsOutboundTranslationRule.md) - - diff --git a/skype/skype-ps/skype/New-CsPartnerApplication.md b/skype/skype-ps/skype/New-CsPartnerApplication.md index e280e910b5..60a75d1f84 100644 --- a/skype/skype-ps/skype/New-CsPartnerApplication.md +++ b/skype/skype-ps/skype/New-CsPartnerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspartnerapplication +online version: https://learn.microsoft.com/powershell/module/skype/new-cspartnerapplication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPartnerApplication schema: 2.0.0 @@ -72,12 +72,12 @@ Skype for Business Server Control Panel: The functions carried out by the New-Cs ### -------------------------- Example 1 -------------------------- ``` -New-CsPartnerApplication -Identity "MicrosoftExchange" -ApplicationTrustLevel "Full" -MetadataUrl"https://autodiscover.litwareinc.com/metadata/json/1" +New-CsPartnerApplication -Identity "MicrosoftExchange" -ApplicationTrustLevel "Full" -MetadataUrl "https://autodiscover.litwareinc.com/metadata/json/1" ``` The command shown in Example 1 creates a new partner application with the Identity "MicrosoftExchange". -In this example, the new partner application uses the metadata URL https://autodiscover.litwareinc.com/metadata/json/1. +In this example, the new partner application uses the metadata URL `https://autodiscover.litwareinc.com/metadata/json/1`. ### -------------------------- Example 2 -------------------------- @@ -163,9 +163,9 @@ Accept wildcard characters: False Certificate (in Base64 encoded format) that can be assigned to the partner application. To read raw data from a certificate and then convert that data to the required format, use commands similar to these: -`$x = Get-Content "C:\Certificates\PartnerApplication.cer" -Encoding Byte` +`$x = [System.IO.File]::ReadAllBytes('C:\Certificates\PartnerApplication.cer')` -`$y = \[Convert\]::ToBase64String($x)` +`$y = [Convert]::ToBase64String($x)` You can then use this syntax to assign the certificate data stored in the variable $y: @@ -414,4 +414,3 @@ The New-CsPartnerApplication cmdlet creates new instances of the Microsoft.Rtc.M [Remove-CsPartnerApplication](Remove-CsPartnerApplication.md) [Set-CsPartnerApplication](Set-CsPartnerApplication.md) - diff --git a/skype/skype-ps/skype/New-CsPersistentChatAddin.md b/skype/skype-ps/skype/New-CsPersistentChatAddin.md index 7fef7cd2e4..6b554367cb 100644 --- a/skype/skype-ps/skype/New-CsPersistentChatAddin.md +++ b/skype/skype-ps/skype/New-CsPersistentChatAddin.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspersistentchataddin -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspersistentchataddin +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPersistentChatAddin schema: 2.0.0 manager: rogupta @@ -18,8 +18,6 @@ Enables you to configure a new Persistent Chat add-in. A Persistent Chat add-in is a customized web page that can be embedded within a Persistent Chat client. This cmdlet was introduced in Lync Server 2013. - - ## SYNTAX ``` @@ -40,8 +38,6 @@ Instead, the CsPersistentChatAddin cmdlets are used to associate (or disassociat Skype for Business Server Control Panel: To create a new Persistent Chat add-in using the Skype for Business Server Control Panel, click Persistent Chat, click Add-in, and then click New. - - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -51,7 +47,7 @@ New-CsPersistentChatAddin -Name "ITPersistentChatAddin" -PersistentChatPoolFqdn ``` The command shown in Example 1 creates a new Persistent Chat add-in (with the name ITPersistentChatAddin) for the pool atl-cs-001.litwareinc.com. -The URL parameter and the parameter value https://atl-cs-001.litwareinc.com/itchat specify the location of the add-in's webpage. +The URL parameter and the parameter value `https://atl-cs-001.litwareinc.com/itchat` specify the location of the add-in's webpage. ## PARAMETERS @@ -61,8 +57,6 @@ The URL parameter and the parameter value https://atl-cs-001.litwareinc.com/itch Friendly name to be given to the Persistent Chat add-in. Names must be unique per Persistent Chat Server pool. - - ```yaml Type: String Parameter Sets: (All) @@ -80,8 +74,6 @@ Accept wildcard characters: False URL of the webpage to be displayed by the Persistent Chat add-in. - - ```yaml Type: String Parameter Sets: (All) @@ -99,8 +91,6 @@ Accept wildcard characters: False Fully qualified domain name of the Persistent Chat Server pool. - - ```yaml Type: String Parameter Sets: (All) @@ -138,5 +128,3 @@ The New-CsPersistentChatAddin cmdlet creates new instances of the Microsoft.Rtc. [Remove-CsPersistentChatAddin](Remove-CsPersistentChatAddin.md) [Set-CsPersistentChatAddin](Set-CsPersistentChatAddin.md) - - diff --git a/skype/skype-ps/skype/New-CsPersistentChatCategory.md b/skype/skype-ps/skype/New-CsPersistentChatCategory.md index ddb8799d74..807ee1f92c 100644 --- a/skype/skype-ps/skype/New-CsPersistentChatCategory.md +++ b/skype/skype-ps/skype/New-CsPersistentChatCategory.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspersistentchatcategory -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspersistentchatcategory +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPersistentChatCategory schema: 2.0.0 manager: rogupta @@ -22,8 +22,6 @@ Instead, existing rooms must later be assigned to a category by using the Set-Cs However, new chat rooms can be assigned to the category at the same time the room is created. This cmdlet was introduced in Lync Server 2013. - - ## SYNTAX ``` @@ -46,8 +44,6 @@ That means that you must create at least one category before you can add any cha Skype for Business Server Control Panel: To create a new Persistent Chat category using the Skype for Business Server Control Panel, click Persistent Chat, click Category, and then click New. - - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -185,4 +181,3 @@ The New-CsPersistentChatCategory cmdlet creates new instances of the Microsoft.R [Remove-CsPersistentChatCategory](Remove-CsPersistentChatCategory.md) [Set-CsPersistentChatCategory](Set-CsPersistentChatCategory.md) - diff --git a/skype/skype-ps/skype/New-CsPersistentChatComplianceConfiguration.md b/skype/skype-ps/skype/New-CsPersistentChatComplianceConfiguration.md index d988fecdf6..98ea85b68d 100644 --- a/skype/skype-ps/skype/New-CsPersistentChatComplianceConfiguration.md +++ b/skype/skype-ps/skype/New-CsPersistentChatComplianceConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspersistentchatcomplianceconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspersistentchatcomplianceconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPersistentChatComplianceConfiguration schema: 2.0.0 manager: rogupta @@ -18,8 +18,6 @@ Creates a new collection of Persistent Chat compliance configuration settings at Persistent Chat compliance enables administrators to maintain an archive of Persistent Chat items and activities including: new messages; new events (for example, a user entering or existing a chat room); file uploads and downloads; and searches run against the chat history. This cmdlet was introduced in Lync Server 2013. - - ## SYNTAX ``` @@ -43,8 +41,6 @@ In addition, Persistent Chat compliance can only be managed using the Windows Po Skype for Business Server Control Panel: The functions carried out by the New-CsPersistentChatComplianceConfiguration cmdlet are not available in the Skype for Business Server Control Panel. - - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -134,8 +130,6 @@ This adapter is supplied by a third-party or can be set to the internal XML adap If you do not specify an adapter type Persistent Chat will not save compliance data. - - ```yaml Type: String Parameter Sets: (All) @@ -156,8 +150,6 @@ This has the potential to greatly increase the size of the compliance data. The default value is False. - - ```yaml Type: Boolean Parameter Sets: (All) @@ -178,8 +170,6 @@ This has the potential to greatly increase the size of the compliance data. The default value is False. - - ```yaml Type: Boolean Parameter Sets: (All) @@ -214,8 +204,6 @@ Accept wildcard characters: False When set to True, additional output files will be created to track file transfers within chat rooms. These files will have the file extension .ATTACH and are placed in the location specified by the AdapterOutputDirectory. - - ```yaml Type: Boolean Parameter Sets: (All) @@ -233,8 +221,6 @@ Accept wildcard characters: False XSLT transform script that enables Persistent Chat to save compliance data in a custom format of your design. - - ```yaml Type: String Parameter Sets: (All) @@ -360,5 +346,3 @@ The New-CsPersistentChatComplianceConfiguration cmdlet creates new instances of [Remove-CsPersistentChatComplianceConfiguration](Remove-CsPersistentChatComplianceConfiguration.md) [Set-CsPersistentChatComplianceConfiguration](Set-CsPersistentChatComplianceConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsPersistentChatConfiguration.md b/skype/skype-ps/skype/New-CsPersistentChatConfiguration.md index e65f625ed3..ede3df5de1 100644 --- a/skype/skype-ps/skype/New-CsPersistentChatConfiguration.md +++ b/skype/skype-ps/skype/New-CsPersistentChatConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspersistentchatconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspersistentchatconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPersistentChatConfiguration schema: 2.0.0 manager: rogupta @@ -19,8 +19,6 @@ Persistent Chat configuration settings are used to manage the Persistent Chat se For example, these settings allow you to specify the maximum number of users who can participate in a chat room. This cmdlet was introduced in Lync Server 2013. - - ## SYNTAX ``` @@ -40,8 +38,6 @@ These settings can be configured at the global or the site scope, or at the serv Skype for Business Server Control Panel: To create a new collection of Persistent Chat configuration settings using the Skype for Business Server Control Panel, click Persistent Chat, click Persistent Chat Configuration, click New, and then click either Site configuration or Pool configuration. - - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -53,7 +49,6 @@ New-CsPersistentChatConfiguration -Identity "site:Redmond" -ParticipantUpdateLim The command shown in Example 1 creates a new set of Persistent Chat configuration settings applied to the Redmond site. In this example, the ParticipantUpdateLimit property is set to 100. - ## PARAMETERS ### -Identity @@ -238,5 +233,3 @@ The New-CsPersistentChatConfiguration cmdlet creates new instances of the Micros [Remove-CsPersistentChatConfiguration](Remove-CsPersistentChatConfiguration.md) [Set-CsPersistentChatConfiguration](Set-CsPersistentChatConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsPersistentChatEndpoint.md b/skype/skype-ps/skype/New-CsPersistentChatEndpoint.md index 8064bc314a..ea7227eca8 100644 --- a/skype/skype-ps/skype/New-CsPersistentChatEndpoint.md +++ b/skype/skype-ps/skype/New-CsPersistentChatEndpoint.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspersistentchatendpoint -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspersistentchatendpoint +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPersistentChatEndpoint schema: 2.0.0 manager: rogupta @@ -181,4 +181,3 @@ The New-CsPersistentChatEndpoint cmdlet creates new instances of the Microsoft.R [Get-CsPersistentChatEndpoint](Get-CsPersistentChatEndpoint.md) [Remove-CsPersistentChatEndpoint](Remove-CsPersistentChatEndpoint.md) - diff --git a/skype/skype-ps/skype/New-CsPersistentChatPolicy.md b/skype/skype-ps/skype/New-CsPersistentChatPolicy.md index 69d1f3b1e8..24a866881d 100644 --- a/skype/skype-ps/skype/New-CsPersistentChatPolicy.md +++ b/skype/skype-ps/skype/New-CsPersistentChatPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspersistentchatpolicy -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspersistentchatpolicy +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPersistentChatPolicy schema: 2.0.0 manager: rogupta @@ -245,5 +245,3 @@ The New-CsPersistentChatPolicy cmdlet creates new instances of the Microsoft.Rtc [Remove-CsPersistentChatPolicy](Remove-CsPersistentChatPolicy.md) [Set-CsPersistentChatPolicy](Set-CsPersistentChatPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsPersistentChatRoom.md b/skype/skype-ps/skype/New-CsPersistentChatRoom.md index 4ed0fccfbd..b387851687 100644 --- a/skype/skype-ps/skype/New-CsPersistentChatRoom.md +++ b/skype/skype-ps/skype/New-CsPersistentChatRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspersistentchatroom -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspersistentchatroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPersistentChatRoom schema: 2.0.0 manager: rogupta @@ -251,5 +251,3 @@ The New-CsPersistentChatRoom cmdlet creates new instances of the Microsoft.Rtc.M [Remove-CsPersistentChatRoom](Remove-CsPersistentChatRoom.md) [Set-CsPersistentChatRoom](Set-CsPersistentChatRoom.md) - - diff --git a/skype/skype-ps/skype/New-CsPinPolicy.md b/skype/skype-ps/skype/New-CsPinPolicy.md index 6972a69438..36afdd1b3c 100644 --- a/skype/skype-ps/skype/New-CsPinPolicy.md +++ b/skype/skype-ps/skype/New-CsPinPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspinpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-cspinpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPinPolicy schema: 2.0.0 @@ -388,5 +388,3 @@ Creates a new instance of the Microsoft.Rtc.Management.WritableConfig.Policy.Use [Remove-CsPinPolicy](Remove-CsPinPolicy.md) [Set-CsPinPolicy](Set-CsPinPolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsPlatformServiceSettings.md b/skype/skype-ps/skype/New-CsPlatformServiceSettings.md index 4bfb39a8e4..a469445901 100644 --- a/skype/skype-ps/skype/New-CsPlatformServiceSettings.md +++ b/skype/skype-ps/skype/New-CsPlatformServiceSettings.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csplatformservicesettings -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csplatformservicesettings +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPlatformServiceSettings schema: 2.0.0 manager: rogupta @@ -297,8 +297,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[Set-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/set-csplatformservicesettings?view=skype-ps) +[Set-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/set-csplatformservicesettings?view=skype-ps) -[Get-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/get-csplatformservicesettings?view=skype-ps) +[Get-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/get-csplatformservicesettings?view=skype-ps) -[Remove-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/remove-csplatformservicesettings?view=skype-ps) +[Remove-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/remove-csplatformservicesettings?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsPresencePolicy.md b/skype/skype-ps/skype/New-CsPresencePolicy.md index 879afba5d1..3fbe18e8f8 100644 --- a/skype/skype-ps/skype/New-CsPresencePolicy.md +++ b/skype/skype-ps/skype/New-CsPresencePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspresencepolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-cspresencepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPresencePolicy schema: 2.0.0 @@ -293,5 +293,3 @@ The New-CsPresencePolicy cmdlet creates new instances of the Microsoft.Rtc.Manag [Remove-CsPresencePolicy](Remove-CsPresencePolicy.md) [Set-CsPresencePolicy](Set-CsPresencePolicy.md) - - diff --git a/skype/skype-ps/skype/New-CsPresenceProvider.md b/skype/skype-ps/skype/New-CsPresenceProvider.md index 5d5b0fb5c2..a7723a9ad6 100644 --- a/skype/skype-ps/skype/New-CsPresenceProvider.md +++ b/skype/skype-ps/skype/New-CsPresenceProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspresenceprovider +online version: https://learn.microsoft.com/powershell/module/skype/new-cspresenceprovider applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPresenceProvider schema: 2.0.0 @@ -242,4 +242,3 @@ The New-CsPresenceProvider cmdlet creates new instances of the Microsoft.Rtc.Man [Remove-CsPresenceProvider](Remove-CsPresenceProvider.md) [Set-CsPresenceProvider](Set-CsPresenceProvider.md) - diff --git a/skype/skype-ps/skype/New-CsPrivacyConfiguration.md b/skype/skype-ps/skype/New-CsPrivacyConfiguration.md index 844c6fdad2..73c2badb7b 100644 --- a/skype/skype-ps/skype/New-CsPrivacyConfiguration.md +++ b/skype/skype-ps/skype/New-CsPrivacyConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csprivacyconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csprivacyconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPrivacyConfiguration schema: 2.0.0 @@ -312,5 +312,3 @@ The New-CsPrivacyConfiguration cmdlet creates new instances of the Microsoft.Rtc [Remove-CsPrivacyConfiguration](Remove-CsPrivacyConfiguration.md) [Set-CsPrivacyConfiguration](Set-CsPrivacyConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsProxyConfiguration.md b/skype/skype-ps/skype/New-CsProxyConfiguration.md index 7a54a3f66d..2d9e20f244 100644 --- a/skype/skype-ps/skype/New-CsProxyConfiguration.md +++ b/skype/skype-ps/skype/New-CsProxyConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csproxyconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csproxyconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsProxyConfiguration schema: 2.0.0 @@ -615,5 +615,3 @@ The New-CsProxyConfiguration cmdlet creates new instances of the Microsoft.Rtc.M [Remove-CsProxyConfiguration](Remove-CsProxyConfiguration.md) [Set-CsProxyConfiguration](Set-CsProxyConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsPublicProvider.md b/skype/skype-ps/skype/New-CsPublicProvider.md index e4c2f13dc1..3350062fcf 100644 --- a/skype/skype-ps/skype/New-CsPublicProvider.md +++ b/skype/skype-ps/skype/New-CsPublicProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspublicprovider +online version: https://learn.microsoft.com/powershell/module/skype/new-cspublicprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPublicProvider schema: 2.0.0 @@ -377,5 +377,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Ed [Remove-CsPublicProvider](Remove-CsPublicProvider.md) [Set-CsPublicProvider](Set-CsPublicProvider.md) - - diff --git a/skype/skype-ps/skype/New-CsPushNotificationConfiguration.md b/skype/skype-ps/skype/New-CsPushNotificationConfiguration.md index a3583defaf..614ff79df4 100644 --- a/skype/skype-ps/skype/New-CsPushNotificationConfiguration.md +++ b/skype/skype-ps/skype/New-CsPushNotificationConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cspushnotificationconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-cspushnotificationconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsPushNotificationConfiguration schema: 2.0.0 manager: rogupta @@ -260,9 +260,8 @@ The New-CsPushNotificationConfiguration cmdlet creates new instances of the Micr ## NOTES ## RELATED LINKS -[Set-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration?view=skype-ps) +[Set-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration?view=skype-ps) -[Get-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/get-cspushnotificationconfiguration?view=skype-ps) - -[Remove-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/remove-cspushnotificationconfiguration?view=skype-ps) +[Get-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/get-cspushnotificationconfiguration?view=skype-ps) +[Remove-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/remove-cspushnotificationconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsQoEConfiguration.md b/skype/skype-ps/skype/New-CsQoEConfiguration.md index d021a867a3..936e584b5d 100644 --- a/skype/skype-ps/skype/New-CsQoEConfiguration.md +++ b/skype/skype-ps/skype/New-CsQoEConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csqoeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csqoeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsQoEConfiguration schema: 2.0.0 @@ -322,5 +322,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.QoE.Q [Set-CsQoEConfiguration](Set-CsQoEConfiguration.md) [Get-CsQoEConfiguration](Get-CsQoEConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsRegistrarConfiguration.md b/skype/skype-ps/skype/New-CsRegistrarConfiguration.md index 043834e5bb..cb6eea8e9f 100644 --- a/skype/skype-ps/skype/New-CsRegistrarConfiguration.md +++ b/skype/skype-ps/skype/New-CsRegistrarConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csregistrarconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csregistrarconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRegistrarConfiguration schema: 2.0.0 @@ -432,5 +432,3 @@ The New-CsRegistrarConfiguration cmdlet creates new instances of the Microsoft.R [Remove-CsRegistrarConfiguration](Remove-CsRegistrarConfiguration.md) [Set-CsRegistrarConfiguration](Set-CsRegistrarConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsReportingConfiguration.md b/skype/skype-ps/skype/New-CsReportingConfiguration.md index 5b8cf483ce..5b76d057c5 100644 --- a/skype/skype-ps/skype/New-CsReportingConfiguration.md +++ b/skype/skype-ps/skype/New-CsReportingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csreportingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csreportingconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsReportingConfiguration schema: 2.0.0 @@ -58,7 +58,7 @@ New-CsReportingConfiguration -Identity "service:MonitoringDatabase:atl-sql-001.l ``` The command shown in Example 1 creates a new collection of reporting configuration settings assigned to the monitoring database with the identity service:MonitoringDatabase:atl-sql-001.litwareinc.com. -In this example, the value of the ReportingUrl property is set to "https://atl-sql-001.litwareinc.com/lync_reports". +In this example, the value of the ReportingUrl property is set to `https://atl-sql-001.litwareinc.com/lync_reports`. ## PARAMETERS @@ -189,5 +189,3 @@ The New-CsReportingConfiguration cmdlet creates new instances of the Microsoft.R [Remove-CsReportingConfiguration](Remove-CsReportingConfiguration.md) [Set-CsReportingConfiguration](Set-CsReportingConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsRgsAgentGroup.md b/skype/skype-ps/skype/New-CsRgsAgentGroup.md index 1dbf72e3ab..ce81c7775c 100644 --- a/skype/skype-ps/skype/New-CsRgsAgentGroup.md +++ b/skype/skype-ps/skype/New-CsRgsAgentGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsagentgroup +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsagentgroup applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsAgentGroup schema: 2.0.0 @@ -342,4 +342,3 @@ New-CsRgsAgentGroup creates new instances of the Microsoft.Rtc.Rgs.Management.Wr [Remove-CsRgsAgentGroup](Remove-CsRgsAgentGroup.md) [Set-CsRgsAgentGroup](Set-CsRgsAgentGroup.md) - diff --git a/skype/skype-ps/skype/New-CsRgsAnswer.md b/skype/skype-ps/skype/New-CsRgsAnswer.md index 6a7fac41d0..446e74549c 100644 --- a/skype/skype-ps/skype/New-CsRgsAnswer.md +++ b/skype/skype-ps/skype/New-CsRgsAnswer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsanswer +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsanswer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsAnswer schema: 2.0.0 @@ -172,5 +172,3 @@ Creates new instances of the Microsoft.Rtc.Rgs.Management.WritableSettings.Answe ## RELATED LINKS [New-CsRgsQuestion](New-CsRgsQuestion.md) - - diff --git a/skype/skype-ps/skype/New-CsRgsCallAction.md b/skype/skype-ps/skype/New-CsRgsCallAction.md index 12940a18a0..5e38c17538 100644 --- a/skype/skype-ps/skype/New-CsRgsCallAction.md +++ b/skype/skype-ps/skype/New-CsRgsCallAction.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgscallaction +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgscallaction applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsCallAction schema: 2.0.0 @@ -229,4 +229,3 @@ New-CsRgsCallAction creates new instances of the Microsoft.Rtc.Rgs.Management.Wr [New-CsRgsQueue](New-CsRgsQueue.md) [Set-CsRgsQueue](Set-CsRgsQueue.md) - diff --git a/skype/skype-ps/skype/New-CsRgsHoliday.md b/skype/skype-ps/skype/New-CsRgsHoliday.md index b1f4b898a0..18b0630657 100644 --- a/skype/skype-ps/skype/New-CsRgsHoliday.md +++ b/skype/skype-ps/skype/New-CsRgsHoliday.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsholiday +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsholiday applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsHoliday schema: 2.0.0 @@ -164,4 +164,3 @@ New-CsRgsHoliday creates new instances of the Microsoft.Rtc.Rgs.Management.Writa [New-CsRgsHolidaySet](New-CsRgsHolidaySet.md) [Set-CsRgsHolidaySet](Set-CsRgsHolidaySet.md) - diff --git a/skype/skype-ps/skype/New-CsRgsHolidaySet.md b/skype/skype-ps/skype/New-CsRgsHolidaySet.md index 12f3d09699..d86a40c358 100644 --- a/skype/skype-ps/skype/New-CsRgsHolidaySet.md +++ b/skype/skype-ps/skype/New-CsRgsHolidaySet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsholidayset +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsholidayset applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsHolidaySet schema: 2.0.0 @@ -247,5 +247,3 @@ New-CsRgsHolidaySet creates new instances of the Microsoft.Rtc.Rgs.Management.Wr [Remove-CsRgsHolidaySet](Remove-CsRgsHolidaySet.md) [Set-CsRgsHolidaySet](Set-CsRgsHolidaySet.md) - - diff --git a/skype/skype-ps/skype/New-CsRgsHoursOfBusiness.md b/skype/skype-ps/skype/New-CsRgsHoursOfBusiness.md index f598d11f95..137037c180 100644 --- a/skype/skype-ps/skype/New-CsRgsHoursOfBusiness.md +++ b/skype/skype-ps/skype/New-CsRgsHoursOfBusiness.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgshoursofbusiness +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgshoursofbusiness applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsHoursOfBusiness schema: 2.0.0 @@ -563,4 +563,3 @@ Creates new instances of the Microsoft.Rtc.Rgs.Management.WritableSettings.Busin [Remove-CsRgsHoursOfBusiness](Remove-CsRgsHoursOfBusiness.md) [Set-CsRgsHoursOfBusiness](Set-CsRgsHoursOfBusiness.md) - diff --git a/skype/skype-ps/skype/New-CsRgsPrompt.md b/skype/skype-ps/skype/New-CsRgsPrompt.md index 08fcfdab62..663c604f09 100644 --- a/skype/skype-ps/skype/New-CsRgsPrompt.md +++ b/skype/skype-ps/skype/New-CsRgsPrompt.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsprompt +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsprompt applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsPrompt schema: 2.0.0 @@ -18,8 +18,6 @@ Creates a new workflow prompt for the Response Group application. A workflow prompt is either an audio file that is played or text that is read aloud in order to supply callers with additional information. This cmdlet was introduced in Lync Server 2010. - - ## SYNTAX ``` @@ -49,8 +47,6 @@ Each time you need to use a prompt it must be created from scratch; there is no If you provide both a text-to-speech and an audio file prompt, the Response Group application will use the audio file by default, and will rely on the text-to-speech prompt only if the audio file is unavailable. After new prompts are created in memory, the corresponding object reference is then typically added to a Response Group call action. - - ## EXAMPLES ### -------------------------- EXAMPLE 1 -------------------------- @@ -73,16 +69,14 @@ The final command in the example uses New-CsRgsCallAction to create a new Respon When creating the call action, the object reference $prompt (which contains the newly-created workflow prompt) is used as the value for the Prompt parameter; the object reference $queue is likewise used in conjunction with the QueueID parameter. After running this command, the new call action and its new workflow prompt are ready to be added to a Response Group workflow. - ### -------------------------- EXAMPLE 2 -------------------------- ``` $queue = Get-CsRgsQueue -Identity service:ApplicationServer:atl-cs-001.litwareinc.com -Name "Help Desk Queue" -$audioFile = Import-CsRgsAudioFile -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -FileName "welcome.wav" -Content (Get-Content C:\Media\Welcome.wav -Encoding byte -ReadCount 0) +$audioFile = Import-CsRgsAudioFile -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -FileName "welcome.wav" -Content ([System.IO.File]::ReadAllBytes('C:\Media\Welcome.wav')) -$prompt = New-CsRgsPrompt -AudioFilePrompt $audioFile -TextToSpeechPrompt "Welcome to the help desk. -Please hold." +$prompt = New-CsRgsPrompt -AudioFilePrompt $audioFile -TextToSpeechPrompt "Welcome to the help desk. Please hold." $z = New-CsRgsCallAction -Prompt $prompt -Action TransferToQueue -QueueID $queue.Identity ``` @@ -96,7 +90,6 @@ After the audio file has been imported, both it and a text-to-speech prompt are To do this, the AudioFilePrompt parameter is set to $audioFile, and the TextToSpeechPrompt parameter is set to the text value "Welcome to the help desk. Please hold." - ## PARAMETERS ### -TextToSpeechPrompt @@ -154,5 +147,3 @@ New-CsRgsPrompt creates instances of the Microsoft.Rtc.Management.WritableSettin [Import-CsRgsAudioFile](Import-CsRgsAudioFile.md) [New-CsRgsCallAction](New-CsRgsCallAction.md) - - diff --git a/skype/skype-ps/skype/New-CsRgsQuestion.md b/skype/skype-ps/skype/New-CsRgsQuestion.md index 6cd1c717c6..9a30312ad9 100644 --- a/skype/skype-ps/skype/New-CsRgsQuestion.md +++ b/skype/skype-ps/skype/New-CsRgsQuestion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsquestion +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsquestion applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsQuestion schema: 2.0.0 @@ -193,5 +193,3 @@ New-CsRgsQuestion creates instances of the Microsoft.Rtc.Management.WriteableSet ## RELATED LINKS [New-CsRgsAnswer](New-CsRgsAnswer.md) - - diff --git a/skype/skype-ps/skype/New-CsRgsQueue.md b/skype/skype-ps/skype/New-CsRgsQueue.md index fc4efda298..119cd58947 100644 --- a/skype/skype-ps/skype/New-CsRgsQueue.md +++ b/skype/skype-ps/skype/New-CsRgsQueue.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsqueue +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsqueue applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsQueue schema: 2.0.0 @@ -322,5 +322,3 @@ New-CsRgsQueue creates new instances of the Microsoft.Rtc.Rgs.Management.Writabl [Remove-CsRgsQueue](Remove-CsRgsQueue.md) [Set-CsRgsQueue](Set-CsRgsQueue.md) - - diff --git a/skype/skype-ps/skype/New-CsRgsTimeRange.md b/skype/skype-ps/skype/New-CsRgsTimeRange.md index 39b58bb1c7..7d567a2ff5 100644 --- a/skype/skype-ps/skype/New-CsRgsTimeRange.md +++ b/skype/skype-ps/skype/New-CsRgsTimeRange.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgstimerange +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgstimerange applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsTimeRange schema: 2.0.0 @@ -175,4 +175,3 @@ New-CsRgsTimeRange creates new instances of the Microsoft.Rtc.Rgs.Management.Wri [New-CsRgsHoursOfBusiness](New-CsRgsHoursOfBusiness.md) [Set-CsRgsHoursOfBusiness](Set-CsRgsHoursOfBusiness.md) - diff --git a/skype/skype-ps/skype/New-CsRgsWorkflow.md b/skype/skype-ps/skype/New-CsRgsWorkflow.md index 8f66464abf..dd48bcbd80 100644 --- a/skype/skype-ps/skype/New-CsRgsWorkflow.md +++ b/skype/skype-ps/skype/New-CsRgsWorkflow.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csrgsworkflow +online version: https://learn.microsoft.com/powershell/module/skype/new-csrgsworkflow applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRgsWorkflow schema: 2.0.0 @@ -322,7 +322,7 @@ However, that language can be used in a workflow only if it is a language suppor The language must be specified using one of the following language codes: -ca-ES - Catalan (Spain) +ca-ES - Catalan da-DK - Danish (Denmark) @@ -597,4 +597,3 @@ The New-CsRgsWorkflow cmdlet creates new instances of the Microsoft.Rtc.Rgs.Mana [Remove-CsRgsWorkflow](Remove-CsRgsWorkflow.md) [Set-CsRgsWorkflow](Set-CsRgsWorkflow.md) - diff --git a/skype/skype-ps/skype/New-CsRoutingConfiguration.md b/skype/skype-ps/skype/New-CsRoutingConfiguration.md index 7f27b048bb..b71bf8d54b 100644 --- a/skype/skype-ps/skype/New-CsRoutingConfiguration.md +++ b/skype/skype-ps/skype/New-CsRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsRoutingConfiguration schema: 2.0.0 @@ -226,5 +226,3 @@ Can create an in-memory object of type Microsoft.Rtc.Management.WritableConfig.P [New-CsVoiceRoute](New-CsVoiceRoute.md) [Get-CsVoiceRoute](Get-CsVoiceRoute.md) - - diff --git a/skype/skype-ps/skype/New-CsServerApplication.md b/skype/skype-ps/skype/New-CsServerApplication.md index 5470c049e7..00a0588174 100644 --- a/skype/skype-ps/skype/New-CsServerApplication.md +++ b/skype/skype-ps/skype/New-CsServerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csserverapplication +online version: https://learn.microsoft.com/powershell/module/skype/new-csserverapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsServerApplication schema: 2.0.0 @@ -141,7 +141,7 @@ Accept wildcard characters: False ### -Uri Unique Uniform Resource Identifier (URI) for the application. -For example, the QoEAgent application has the URI http://www.microsoft.com/LCS/QoEAgent. +For example, the QoEAgent application has the URI `http://www.microsoft.com/LCS/QoEAgent`. ```yaml Type: String @@ -352,5 +352,3 @@ The New-CsServerApplication cmdlet creates new instances of the Microsoft.Rtc.Ma [Remove-CsServerApplication](Remove-CsServerApplication.md) [Set-CsServerApplication](Set-CsServerApplication.md) - - diff --git a/skype/skype-ps/skype/New-CsSimpleUrl.md b/skype/skype-ps/skype/New-CsSimpleUrl.md index 4bb48e1e3e..93d388cd74 100644 --- a/skype/skype-ps/skype/New-CsSimpleUrl.md +++ b/skype/skype-ps/skype/New-CsSimpleUrl.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssimpleurl +online version: https://learn.microsoft.com/powershell/module/skype/new-cssimpleurl applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSimpleUrl schema: 2.0.0 @@ -28,12 +28,12 @@ New-CsSimpleUrl -Component <String> -Domain <String> [-SimpleUrlEntry <PSListMod In Microsoft Office Communications Server 2007 R2, meetings had URLs similar to this: -https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t +`https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t` However, such URLs are not especially intuitive, and not easy to convey to someone else. The simple URLs introduced in Lync Server 2010 help overcome those problems by providing users with URLs that look more like this: -https://meet.litwareinc.com/kenmyer/071200 +`https://meet.litwareinc.com/kenmyer/071200` Simple URLs are an improvement over the URLs used in Office Communications Server. However, simple URLs are not automatically created for you; instead, you must configure the URLs yourself. @@ -53,7 +53,7 @@ When you install Skype for Business Server, a global collection is created for y This gives you the ability to use different simple URLs at each of your sites. To add an actual URL to a simple URL collection, you must first create the URL by using the New-CsSimpleUrl cmdlet and the New-CsSimpleUrlEntry cmdlet. -The New-CsSimpleUrlEntry cmdlet creates a URL entry: a URL (such as https://meet.litwareinc.com) that can be used as a simple URL (for meeting, administration, or dial-in conferencing purposes). +The New-CsSimpleUrlEntry cmdlet creates a URL entry: a URL (such as `https://meet.litwareinc.com`) that can be used as a simple URL (for meeting, administration, or dial-in conferencing purposes). The object created by the New-CsSimpleUrlEntry cmdlet is added to the SimpleUrlEntry property of a new simple URL. You must use a separate cmdlet to create the object because the SimpleUrlEntry property can hold multiple URLs. (However, only one such URL can be designated as the active URL. @@ -75,10 +75,10 @@ Set-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Add=$simpleUr ``` Example 1 shows how a new URL can be added to an existing collection of simple URLs. -To begin with, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to https://meet.fabrikam.com; this URL entry is stored in a variable named $urlEntry. +To begin with, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to `https://meet.fabrikam.com`; this URL entry is stored in a variable named $urlEntry. In the second command, the New-CsSimpleUrl cmdlet is used to create an in-memory-only instance of a simple URL. -In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to https://meet.fabrikam.com; and the SimpleUrl property is set to $urlEntry, with $urlEntry being the URL entry created in the first command. +In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to `https://meet.fabrikam.com`; and the SimpleUrl property is set to $urlEntry, with $urlEntry being the URL entry created in the first command. After the URL has been created (and stored in the object reference $simpleUrl) the final command in the example adds the new URL to the simple URL collection for the Redmond site. This is done by using the Set-CsSimpleUrlConfiguration cmdlet, the SimpleUrl parameter, and the parameter value @{Add=$simpleUrl}. @@ -139,7 +139,7 @@ Accept wildcard characters: False ### -SimpleUrlEntry Collection of URLs for the specified component. -For example, both https://meet.litwareinc.com and https://litwareinc.com/meet might be configured as URL entries for the Meet component. +For example, both `https://meet.litwareinc.com` and `https://litwareinc.com/meet` might be configured as URL entries for the Meet component. However, only one of those URLs can be (and must be) configured as the active URL. Simple URL entries must be created by using the New-CsSimpleUrlEntry cmdlet. @@ -166,7 +166,7 @@ An error will occur if you try to set the ActiveUrl to a value not found in the To assign an active URL, simply use the URL itself as the parameter value. For example: -`-ActiveUrl https://meet.litwareinc.com"` +`-ActiveUrl "https://meet.litwareinc.com/"` @@ -204,4 +204,3 @@ The New-CsSimpleUrl cmdlet creates new instances of the Microsoft.Rtc.Management [New-CsSimpleUrlConfiguration](New-CsSimpleUrlConfiguration.md) [New-CsSimpleUrlEntry](New-CsSimpleUrlEntry.md) - diff --git a/skype/skype-ps/skype/New-CsSimpleUrlConfiguration.md b/skype/skype-ps/skype/New-CsSimpleUrlConfiguration.md index afe6e1b74f..4bcbbf4b6a 100644 --- a/skype/skype-ps/skype/New-CsSimpleUrlConfiguration.md +++ b/skype/skype-ps/skype/New-CsSimpleUrlConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssimpleurlconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cssimpleurlconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSimpleUrlConfiguration schema: 2.0.0 @@ -32,12 +32,12 @@ New-CsSimpleUrlConfiguration [-Identity] <XdsIdentity> [-SimpleUrl <PSListModifi In Microsoft Office Communications Server 2007 R2, meetings had URLs similar to this: -https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t +`https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t` However, such URLs are not especially intuitive, and not easy to convey to someone else. The simple URLs introduced in Lync Server 2010 help overcome those problems by providing users with URLs that look more like this: -https://meet.litwareinc.com/kenmyer/071200 +`https://meet.litwareinc.com/kenmyer/071200` Simple URLs are an improvement over the URLs used in Office Communications Server. However, simple URLs are not automatically created for you; instead, you must configure the URLs yourself. @@ -89,11 +89,11 @@ New-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Add=$simpleUr ``` Example 2 shows how you can create a new collection of simple URLs that includes two simple URLs (one for meeting management and one for dial-in conferencing). -To do this, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to https://dialin.litwareinc.com; this URL entry is stored in a variable named $urlEntry. -The second command then creates another URL entry, this one pointing to https://meet.fabrikam.com. +To do this, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to `https://dialin.litwareinc.com`; this URL entry is stored in a variable named $urlEntry. +The second command then creates another URL entry, this one pointing to `https://meet.fabrikam.com`. Next, the New-CsSimpleUrl cmdlet is used to create an in-memory-only instance of a simple URL. -In this example, the URL Component is set to dialin; the domain is set to an asterisk (*); the ActiveUrl is set to https://dialin.fabrikam.com; and the SimpleUrl property is set to $urlEntry. +In this example, the URL Component is set to dialin; the domain is set to an asterisk (*); the ActiveUrl is set to `https://dialin.fabrikam.com`; and the SimpleUrl property is set to $urlEntry. (The variable $urlEntry represents the URL entry created in the first command.) A similar command is then used to create a simple URL for meet.fabrikam.com. After the URLs have been created (and stored in the object references $simpleUrl and $simpleUrl2) the final command in the example creates a new simple URL collection for the Redmond site, adding the two new in-memory-only URLs to that collection. @@ -267,5 +267,3 @@ The New-CsSimpleUrlConfiguration cmdlet creates new instances of the Microsoft.R [Remove-CsSimpleUrlConfiguration](Remove-CsSimpleUrlConfiguration.md) [Set-CsSimpleUrlConfiguration](Set-CsSimpleUrlConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsSimpleUrlEntry.md b/skype/skype-ps/skype/New-CsSimpleUrlEntry.md index 83d51db3ae..f748308d5a 100644 --- a/skype/skype-ps/skype/New-CsSimpleUrlEntry.md +++ b/skype/skype-ps/skype/New-CsSimpleUrlEntry.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssimpleurlentry +online version: https://learn.microsoft.com/powershell/module/skype/new-cssimpleurlentry applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSimpleUrlEntry schema: 2.0.0 @@ -30,12 +30,12 @@ New-CsSimpleUrlEntry -Url <String> [<CommonParameters>] In Microsoft Office Communications Server 2007 R2, meetings had URLs similar to this: -https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t +`https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t` However, such URLs are not especially intuitive, and not easy to convey to someone else. The simple URLs introduced in Lync Server 2010 help overcome those problems by providing users with URLs that look more like this: -https://meet.litwareinc.com/kenmyer/071200 +`https://meet.litwareinc.com/kenmyer/071200` Simple URLs are obviously an improvement over the URLs used in Office Communications Server. However, simple URLs are not automatically created for you; instead, you must configure the URLs yourself. @@ -55,7 +55,7 @@ When you install Skype for Business Server, a global collection is created for y This gives you the ability to use different simple URLs at each of your sites. To add an actual URL to a simple URL collection, you must first create the URL by using the New-CsSimpleUrl cmdlet and the New-CsSimpleUrlEntry cmdlet. -The New-CsSimpleUrlEntry cmdlet creates a URL entry; this is nothing more than a URL (such as https://meet.litwareinc.com) that can be used as a simple URL (for meeting, administration, or dial-in conferencing purposes). +The New-CsSimpleUrlEntry cmdlet creates a URL entry; this is nothing more than a URL (such as `https://meet.litwareinc.com`) that can be used as a simple URL (for meeting, administration, or dial-in conferencing purposes). The object created by the New-CsSimpleUrlEntry cmdlet is then added to the SimpleUrlEntry property of a new simple URL. You must use a separate cmdlet to create the object; that's because the SimpleUrlEntry property can hold multiple URLs. (However, only one such URL can be designated as the active URL. @@ -80,10 +80,10 @@ Set-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Add=$simpleUr ``` Example 1 shows how a new URL can be added to an existing collection of simple URLs. -To begin with, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to https://meet.fabrikam.com; this URL entry is stored in a variable named $urlEntry. +To begin with, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to `https://meet.fabrikam.com`; this URL entry is stored in a variable named $urlEntry. In the second command, the New-CsSimpleUrl cmdlet is used to create an in-memory-only instance of a simple URL. -In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to https://meet.fabrikam.com; and the SimpleUrl property is set to $urlEntry, with $urlEntry being the URL entry created in the first command. +In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to `https://meet.fabrikam.com`; and the SimpleUrl property is set to $urlEntry, with $urlEntry being the URL entry created in the first command. After the URL has been created (and stored in the object reference $simpleUrl) the final command in the example adds the new URL to the simple URL collection for the Redmond site. This is done by using the Set-CsSimpleUrlConfiguration cmdlet, the SimpleUrl parameter and the parameter value @{Add=$simpleUrl}. @@ -105,12 +105,12 @@ Set-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Add=$simpleUr ``` In Example 2, a pair of URL entries is added to an existing collection of simple URLs. -To do this, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to https://meet.fabrikam.com; this URL entry is stored in a variable named $urlEntry. +To do this, the first command in the example uses the New-CsSimpleUrlEntry cmdlet to create a URL entry that points to `https://meet.fabrikam.com`; this URL entry is stored in a variable named $urlEntry. The second command then creates a second URL entry, this one stored in the variable $urlEntry2 and pointing to the URL https:// dialin.fabrikam.com. After the two URL entries have been created, the New-CsSimpleUrl cmdlet is used to create two in-memory-only instances of a simple URL. -In the first instance, the URL Component is set to Meet; the domain is set to fabrikam.com; and the ActiveUrl is set to https://meet.fabrikam.com. -In the second instance, the component is set to Dialin; the domain to an asterisk (*); and the ActiveURL property is set to https://dialin.fabrikam.com. +In the first instance, the URL Component is set to Meet; the domain is set to fabrikam.com; and the ActiveUrl is set to `https://meet.fabrikam.com`. +In the second instance, the component is set to Dialin; the domain to an asterisk (*); and the ActiveURL property is set to `https://dialin.fabrikam.com`. After the URLs have been created (and stored in the object references $simpleUrl and $simpleUrl2), the final command in the example adds the new URL to the simple URL collection for the Redmond site. This is done by using the Set-CsSimpleUrlConfiguration cmdlet, the SimpleUrl parameter, and the parameter value @{Add=$simpleUrl, $simpleUrl2}. @@ -163,5 +163,3 @@ The New-CsSimpleUrlEntry cmdlet creates new instances of the Microsoft.Rtc.Manag [New-CsSimpleUrl](New-CsSimpleUrl.md) [New-CsSimpleUrlConfiguration](New-CsSimpleUrlConfiguration.md) - - diff --git a/skype/skype-ps/skype/New-CsSipDomain.md b/skype/skype-ps/skype/New-CsSipDomain.md index 2225e7e23d..e3f6128773 100644 --- a/skype/skype-ps/skype/New-CsSipDomain.md +++ b/skype/skype-ps/skype/New-CsSipDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipdomain +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipdomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipDomain schema: 2.0.0 @@ -180,5 +180,3 @@ The New-CsSipDomain cmdlet creates new instances of the Microsoft.Rtc.Management [Remove-CsSipDomain](Remove-CsSipDomain.md) [Set-CsSipDomain](Set-CsSipDomain.md) - - diff --git a/skype/skype-ps/skype/New-CsSipProxyCustom.md b/skype/skype-ps/skype/New-CsSipProxyCustom.md index e7adf2a7e5..1e9b87ddfd 100644 --- a/skype/skype-ps/skype/New-CsSipProxyCustom.md +++ b/skype/skype-ps/skype/New-CsSipProxyCustom.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipproxycustom +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipproxycustom applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipProxyCustom schema: 2.0.0 @@ -85,5 +85,3 @@ The New-CsSipProxyCustom cmdlet creates new instances of the Microsoft.Rtc.Manag [New-CsSipProxyRealm](New-CsSipProxyRealm.md) [New-CsSipProxyUseDefault](New-CsSipProxyUseDefault.md) - - diff --git a/skype/skype-ps/skype/New-CsSipProxyRealm.md b/skype/skype-ps/skype/New-CsSipProxyRealm.md index 96aa699307..28a9713563 100644 --- a/skype/skype-ps/skype/New-CsSipProxyRealm.md +++ b/skype/skype-ps/skype/New-CsSipProxyRealm.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipproxyrealm +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipproxyrealm applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipProxyRealm schema: 2.0.0 @@ -107,5 +107,3 @@ The New-CsSipProxyRealm cmdlet creates new instances of the Microsoft.Rtc.Manage [New-CsSipProxyCustom](New-CsSipProxyCustom.md) [New-CsSipProxyUseDefault](New-CsSipProxyUseDefault.md) - - diff --git a/skype/skype-ps/skype/New-CsSipProxyTCP.md b/skype/skype-ps/skype/New-CsSipProxyTCP.md index 6d027f75dd..60a6fa4a29 100644 --- a/skype/skype-ps/skype/New-CsSipProxyTCP.md +++ b/skype/skype-ps/skype/New-CsSipProxyTCP.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipproxytcp +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipproxytcp applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipProxyTCP schema: 2.0.0 @@ -103,5 +103,3 @@ The New-CsSipProxyTCP cmdlet creates new instances of the Microsoft.Rtc.Manageme [New-CsSipProxyTLS](New-CsSipProxyTLS.md) [New-CsSipProxyTransport](New-CsSipProxyTransport.md) - - diff --git a/skype/skype-ps/skype/New-CsSipProxyTLS.md b/skype/skype-ps/skype/New-CsSipProxyTLS.md index 47bb0d1f72..8083398419 100644 --- a/skype/skype-ps/skype/New-CsSipProxyTLS.md +++ b/skype/skype-ps/skype/New-CsSipProxyTLS.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipproxytls +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipproxytls applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipProxyTLS schema: 2.0.0 @@ -132,5 +132,3 @@ The New-CsSipProxyTLS cmdlet creates new instances of the Microsoft.Rtc.Manageme [New-CsSipProxyTransport](New-CsSipProxyTransport.md) [New-CsSipProxyUseDefaultCert](New-CsSipProxyUseDefaultCert.md) - - diff --git a/skype/skype-ps/skype/New-CsSipProxyTransport.md b/skype/skype-ps/skype/New-CsSipProxyTransport.md index 060f63fdb8..3986103a26 100644 --- a/skype/skype-ps/skype/New-CsSipProxyTransport.md +++ b/skype/skype-ps/skype/New-CsSipProxyTransport.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipproxytransport +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipproxytransport applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipProxyTransport schema: 2.0.0 @@ -134,4 +134,3 @@ The `New-CsSipProxyTransport` cmdlet creates new instances of the Microsoft.Rtc. [New-CsSipProxyTCP](New-CsSipProxyTCP.md) [New-CsSipProxyTLS](New-CsSipProxyTLS.md) - diff --git a/skype/skype-ps/skype/New-CsSipProxyUseDefault.md b/skype/skype-ps/skype/New-CsSipProxyUseDefault.md index eefe9a81ac..c4b0c49aba 100644 --- a/skype/skype-ps/skype/New-CsSipProxyUseDefault.md +++ b/skype/skype-ps/skype/New-CsSipProxyUseDefault.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipproxyusedefault +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipproxyusedefault applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipProxyUseDefault schema: 2.0.0 @@ -80,4 +80,3 @@ The `New-CsSipProxyUseDefault` cmdlet creates new instances of the Microsoft.Rtc [New-CsSipProxyCustom](New-CsSipProxyCustom.md) [New-CsSipProxyRealm](New-CsSipProxyRealm.md) - diff --git a/skype/skype-ps/skype/New-CsSipProxyUseDefaultCert.md b/skype/skype-ps/skype/New-CsSipProxyUseDefaultCert.md index 2fab300eea..c3e2de765f 100644 --- a/skype/skype-ps/skype/New-CsSipProxyUseDefaultCert.md +++ b/skype/skype-ps/skype/New-CsSipProxyUseDefaultCert.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipproxyusedefaultcert +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipproxyusedefaultcert applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipProxyUseDefaultCert schema: 2.0.0 @@ -97,4 +97,3 @@ The `New-CsSipProxyUseDefaultCert` cmdlet creates new instances of the Microsoft ## RELATED LINKS [New-CsSipProxyTLS](New-CsSipProxyTLS.md) - diff --git a/skype/skype-ps/skype/New-CsSipResponseCodeTranslationRule.md b/skype/skype-ps/skype/New-CsSipResponseCodeTranslationRule.md index c532a631d6..79e5457a51 100644 --- a/skype/skype-ps/skype/New-CsSipResponseCodeTranslationRule.md +++ b/skype/skype-ps/skype/New-CsSipResponseCodeTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cssipresponsecodetranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/new-cssipresponsecodetranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsSipResponseCodeTranslationRule schema: 2.0.0 @@ -311,4 +311,3 @@ The `New-CsSipResponseCodeTranslationRule` cmdlet creates new instances of the M [Remove-CsSipResponseCodeTranslationRule](Remove-CsSipResponseCodeTranslationRule.md) [Set-CsSipResponseCodeTranslationRule](Set-CsSipResponseCodeTranslationRule.md) - diff --git a/skype/skype-ps/skype/New-CsStaticRoute.md b/skype/skype-ps/skype/New-CsStaticRoute.md index 80d607749c..f7208b4025 100644 --- a/skype/skype-ps/skype/New-CsStaticRoute.md +++ b/skype/skype-ps/skype/New-CsStaticRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csstaticroute +online version: https://learn.microsoft.com/powershell/module/skype/new-csstaticroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsStaticRoute schema: 2.0.0 @@ -326,4 +326,3 @@ The `New-CsStaticRoute` cmdlet creates new instances of the Microsoft.Rtc.Manage [New-CsStaticRoutingConfiguration](New-CsStaticRoutingConfiguration.md) [Set-CsStaticRoutingConfiguration](Set-CsStaticRoutingConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsStaticRoutingConfiguration.md b/skype/skype-ps/skype/New-CsStaticRoutingConfiguration.md index 263673ffb9..f59880c6ef 100644 --- a/skype/skype-ps/skype/New-CsStaticRoutingConfiguration.md +++ b/skype/skype-ps/skype/New-CsStaticRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csstaticroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csstaticroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsStaticRoutingConfiguration schema: 2.0.0 @@ -194,4 +194,3 @@ The `New-CsStaticRoutingConfiguration` cmdlet creates new instances of the Micro [Remove-CsStaticRoutingConfiguration](Remove-CsStaticRoutingConfiguration.md) [Set-CsStaticRoutingConfiguration](Set-CsStaticRoutingConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsStorageServiceConfiguration.md b/skype/skype-ps/skype/New-CsStorageServiceConfiguration.md index 348dc7e626..b9fb8758da 100644 --- a/skype/skype-ps/skype/New-CsStorageServiceConfiguration.md +++ b/skype/skype-ps/skype/New-CsStorageServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csstorageserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csstorageserviceconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsStorageServiceConfiguration schema: 2.0.0 @@ -226,4 +226,3 @@ The `New-CsStorageServiceConfiguration` cmdlet creates new instances of the Micr [Remove-CsStorageServiceConfiguration](Remove-CsStorageServiceConfiguration.md) [Set-CsStorageServiceConfiguration](Set-CsStorageServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsTeamsAppPermissionPolicy.md b/skype/skype-ps/skype/New-CsTeamsAppPermissionPolicy.md deleted file mode 100644 index d093fbfa84..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsAppPermissionPolicy.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsapppermissionpolicy -applicable: Skype for Business Online -title: New-CsTeamsAppPermissionPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# New-CsTeamsAppPermissionPolicy - -## SYNOPSIS - -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## SYNTAX - -## DESCRIPTION -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## EXAMPLES - -### Example 1 -Intentionally omitted. - -## 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsAppSetupPolicy.md b/skype/skype-ps/skype/New-CsTeamsAppSetupPolicy.md deleted file mode 100644 index 647179d0ae..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsAppSetupPolicy.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsappsetuppolicy -applicable: Skype for Business Online -title: New-CsTeamsAppSetupPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# New-CsTeamsAppSetupPolicy - -## SYNOPSIS - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## SYNTAX - -## DESCRIPTION - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## EXAMPLES - -### Example 1 -Intentionally not provided - -## 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsCallParkPolicy.md b/skype/skype-ps/skype/New-CsTeamsCallParkPolicy.md deleted file mode 100644 index e8bcaf795b..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsCallParkPolicy.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamscallparkpolicy -applicable: Skype for Business Online -title: New-CsTeamsCallParkPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - - -# New-CsTeamsCallParkPolicy - -## SYNOPSIS - -The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone. The New-CsTeamsCallParkPolicy cmdlet lets you create a new custom policy that can then be assigned to one or more specific users. - -NOTE: The call park feature currently available in desktop. mobile and web clients. Supported with TeamsOnly mode. - -## SYNTAX - -### Identity (Default) -``` -New-CsTeamsCallParkPolicy [-Tenant <System.Guid>] [-AllowCallPark <Boolean>] [[-Identity] <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different phone. The New-CsTeamsCallParkPolicy cmdlet lets you create a new custom policy that can then be assigned to one or more specific users. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsCallParkPolicy -Identity "SalesPolicy" -AllowCallPark $false -``` - -Create a new custom policy that has call park enabled. This policy can then be assigned to individual users. - -## PARAMETERS - -### -AllowCallPark -If set to true, customers will be able to leverage the call park feature to place calls on hold and then decide how the call should be handled - transferred to another department, retrieved using the same phone, or retrieved using a different phone. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppress all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier for the policy - this will be used to retrieve the policy later on to assign it to specific users. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsChannelsPolicy.md b/skype/skype-ps/skype/New-CsTeamsChannelsPolicy.md deleted file mode 100644 index a59c5d05be..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsChannelsPolicy.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamschannelspolicy -applicable: Skype for Business Online -title: New-CsTeamsChannelsPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsTeamsChannelsPolicy - -## SYNOPSIS - -The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. - -## SYNTAX -``` -New-CsTeamsChannelsPolicy [-Tenant <Guid>] [-AllowOrgWideTeamCreation <Boolean>] - [-AllowPrivateTeamDiscovery <Boolean>] [-AllowPrivateChannelCreation <Boolean>] [-Identity] <XdsIdentity> - [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. - -This cmdlet allows you to create new policies of this type, which can later be assigned to specific users. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsChannelsPolicy -Identity StudentPolicy -AllowPrivateTeamDiscovery $false -``` - -This example shows creating a new policy with name "StudentPolicy" where Private Team Discovery is disabled. - -## PARAMETERS - -### -AllowPrivateTeamDiscovery -Determines whether a user is allowed to discover private teams in suggestions and search results. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Bypasses all non-fatal errors. -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the name of the policy that you are creating. - -```yaml -Type: String -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOrgWideTeamCreation -Determines whether a user is allowed to create an org-wide team. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPrivateChannelCreation -Determines whether a user is allowed to create a private channel. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamschannelspolicy) - -[Remove-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamschannelspolicy) - -[Grant-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamschannelspolicy) - -[Get-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamschannelspolicy) diff --git a/skype/skype-ps/skype/New-CsTeamsComplianceRecordingPairedApplication.md b/skype/skype-ps/skype/New-CsTeamsComplianceRecordingPairedApplication.md deleted file mode 100644 index 31fd178e11..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsComplianceRecordingPairedApplication.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication -applicable: Skype for Business Online -title: New-CsTeamsComplianceRecordingPairedApplication -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# New-CsTeamsComplianceRecordingPairedApplication - -## SYNOPSIS -Creates a new association between multiple application instances of policy-based recording applications to achieve application resiliency in automatic policy-based recording scenarios. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -``` -New-CsTeamsComplianceRecordingPairedApplication -Id <String> - [<CommonParameters>] -``` - -## DESCRIPTION -Policy-based recording applications are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. - -Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. - -In situations where application resiliency is a necessity, invites can be sent to separate paired applications for the same call or meeting. -If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. - -If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. - -If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. - -If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. - -If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application, to determine if application resiliency is needed for your workflows, and how best to achieve application resiliency. -Please also refer to the documentation of CsTeamsComplianceRecordingApplication cmdlets for further information. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsComplianceRecordingPairedApplication -Id '39dc3ede-c80e-4f19-9153-417a65a1f144' -``` - -The command shown in Example 1 creates an in-memory instance of an application instance of a policy-based recording application that can be associated with other such application instances to achieve application resiliency. - -Note that this cmdlet is only used in conjunction with New-CsTeamsComplianceRecordingApplication and Set-CsTeamsComplianceRecordingApplication to create associations between multiple application instances of policy-based recording applications. -Please refer to the documentation of CsTeamsComplianceRecordingApplication cmdlets for examples and further information. - -## PARAMETERS - -### -Id -The ObjectId of the application instance of a policy-based recording application as exposed by the Get-CsOnlineApplicationInstance cmdlet. -For example, the Id of an application instance can be \"39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance has ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsTeamsComplianceRecordingPolicy.md b/skype/skype-ps/skype/New-CsTeamsComplianceRecordingPolicy.md deleted file mode 100644 index d68bcc5d79..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsComplianceRecordingPolicy.md +++ /dev/null @@ -1,268 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy -applicable: Skype for Business Online -title: New-CsTeamsComplianceRecordingPolicy -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# New-CsTeamsComplianceRecordingPolicy - -## SYNOPSIS -Creates a new Teams recording policy for governing automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -``` -New-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-Enabled <Boolean>] [-WarnUserOnRemoval <Boolean>] [-Description <String>] - [-ComplianceRecordingApplications <ComplianceRecordingApplication[]>] - [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Teams recording policies are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. - -Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. -Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. - -Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. -The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. -Existing calls and meetings are unaffected. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $true -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899') -``` - -The command shown in Example 1 creates a new per-user Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. -This policy is assigned a single application instance of a policy-based recording application: d93fefc7-93cc-4d44-9a5d-344b0fff2899, which is the ObjectId of the application instance as obtained from the Get-CsOnlineApplicationInstance cmdlet. - -Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by that application instance. Existing calls and meetings are unaffected. - -### Example 2 -```powershell -PS C:\> New-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $true -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899'), @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') -``` - -Example 2 is a variation of Example 1. -In this case, the Teams recording policy is assigned two application instances of policy-based recording applications. - -Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by both those application instances. Existing calls and meetings are unaffected. - -## PARAMETERS - -### -Identity -Unique identifier to be assigned to the new Teams recording policy. - -Use the "Global" Identity if you wish to assign this policy to the entire tenant. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -Controls whether this Teams recording policy is active or not. - -Setting this to True and having the right set of ComplianceRecordingApplications will initiate automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. - -Setting this to False will stop automatic policy-based recording for any new calls or meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarnUserOnRemoval -This parameter is reserved for future use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Enables administrators to provide explanatory text to accompany a Teams recording policy. For example, the Description might include information about the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ComplianceRecordingApplications -A list of application instances of policy-based recording applications to assign to this policy. -The Id of each of these application instances must be the ObjectId of the application instance as obtained by the Get-CsOnlineApplicationInstance cmdlet. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. - -```yaml -Type: ComplianceRecordingApplication[] -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -Creates an object reference without actually committing the object as a permanent change. -If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set- cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) diff --git a/skype/skype-ps/skype/New-CsTeamsEmergencyCallRoutingPolicy.md b/skype/skype-ps/skype/New-CsTeamsEmergencyCallRoutingPolicy.md deleted file mode 100644 index 29694568d8..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsEmergencyCallRoutingPolicy.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsemergencycallroutingpolicy -applicable: Skype for Business Online -title: New-CsTeamsEmergencyCallRoutingPolicy -author: danny-levin -ms.author: dannyle -manger: roykuntz -ms.reviewer: chenc, vaddank, pthota -schema: 2.0.0 ---- - -# New-CsTeamsEmergencyCallRoutingPolicy - -## SYNOPSIS - -## SYNTAX - -``` -New-CsTeamsEmergencyCallRoutingPolicy [-Tenant <System.Guid>] [-EmergencyNumbers <>] - [-AllowEnhancedEmergencyServices <Boolean>] [-Description <String>] [-Identity] <XdsIdentity> [-InMemory] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet creates a new Teams Emergency Call Routing policy with one or more emergency number. Teams Emergency Call Routing policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> $en1 = New-CsTeamsEmergencyNumber -EmergencyDialString "112" -EmergencyDialMask "117;897" -OnlinePSTNUsage "Local" -CarrierProfile "Local" -New-CsTeamsEmergencyCallRoutingPolicy -Identity "testecrp" -Tenant $tenant -EmergencyNumbers @{add=$en1} -AllowEnhancedEmergencyServices:$true -Description "test" -``` - - This example first creates a new Teams emergency number object and then creates a Teams Emergency Call Routing policy with this emergency number object. - Note that the OnlinePSTNUsage specified in the first command must previously exist. Note that the resulting object from the New-CsTeamsEmergencyNumber only exists in memory, so you must apply it to a policy to be used. - -## PARAMETERS - -### -AllowEnhancedEmergencyServices - Flag to enable Enhanced Emergency Services - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - The Description parameter describes the Teams Emergency Call Routing policy - what it's for, what type of user it applies to and any other information that helps to identify the purpose of this policy. Maximum characters: 512. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmergencyNumbers - One or more emergency number objects obtained from [New-CsTeamsEmergencyNumber](https://docs.microsoft.com/powershell/module/skype/new-csteamsemergencynumber?view=skype-ps) cmdlet - -```yaml -Type: -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - The Identity parameter is a unique identifier that designates the name of the policy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory - The InMemory parameter creates an object reference without actually committing the object as a permanent change. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - Specify the tenant id - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsEmergencyCallingPolicy.md b/skype/skype-ps/skype/New-CsTeamsEmergencyCallingPolicy.md deleted file mode 100644 index 27ef1f7a7a..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsEmergencyCallingPolicy.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsemergencycallingpolicy -applicable: Skype for Business Online -title: New-CsTeamsEmergencyCallingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# New-CsTeamsEmergencyCallingPolicy - -## SYNOPSIS - -## SYNTAX - -``` -New-CsTeamsEmergencyCallingPolicy [-Tenant <System.Guid>] [-NotificationGroup <String>] - [-NotificationDialOutNumber <String>] [-ExternalLocationLookupMode <ExternalLocationLookupMode>] - [-NotificationMode <Microsoft.Rtc.Management.WritableConfig.Policy.Teams.NotificationMode>] - [-Description <String>] [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet creates a new Teams Emergency Calling policy. Emergency calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> New-CsTeamsEmergencyCallingPolicy -Identity testECRP -Description "Test ECRP" -NotificationGroup "alert@contoso.com" -NotificationDialOutNumber "4253214567" -NotificationMode NotificationOnly -ExternalLocationLookupMode $true -``` - - This example creates a Teams Emergency Calling policy that has a identity of testECRP, where a notification group and number is being defined and also the type of notification. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - The Description parameter describes the Teams Emergency Calling policy - what it is for, what type of user it applies to and any other information that helps to identify the purpose of this policy. Maximum characters: 512. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalLocationLookupMode - Enable ExternalLocationLookupMode. This parameter is currently not supported. - -```yaml -Type: ExternalLocationLookupMode -Parameter Sets: (All) -Aliases: -Accepted values: Disabled, Enabled - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - The Identity parameter is a unique identifier that designates the name of the policy - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory - The InMemory parameter creates an object reference without actually committing the object as a permanent change. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationDialOutNumber - This parameter represents PSTN number which can be dialed out if NotificationMode is set to either of the two Conference values - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationGroup - NotificationGroup is a email list of users and groups to be notified of an emergency call - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationMode - The type of conference experience for security desk notification - -```yaml -Type: Microsoft.Rtc.Management.WritableConfig.Policy.Teams.NotificationMode -Parameter Sets: (All) -Aliases: -Accepted values: NotificationOnly, ConferenceMuted, ConferenceUnMuted - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - Specify the tenant id - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsEmergencyNumber.md b/skype/skype-ps/skype/New-CsTeamsEmergencyNumber.md deleted file mode 100644 index b6fd7e204c..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsEmergencyNumber.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsemergencynumber -applicable: Skype for Business Online -title: New-CsTeamsEmergencyNumber -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# New-CsTeamsEmergencyNumber - -## SYNOPSIS - -## SYNTAX - -``` -New-CsTeamsEmergencyNumber -EmergencyDialString <String> [-EmergencyDialMask <String>] - [-OnlinePSTNUsage <String>] [-CarrierProfile <String>] [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet supports to create multiple Teams emergency numbers. The Maximum limitation is 10 - -## EXAMPLES - -### Example 1 -```powershell -PS C:> New-CsTeamsEmergencyNumber -EmergencyDialString 711 -EmergencyDialMask 321 -OnlinePSTNUsage "US911" -``` - - Create a new Teams emergency number - -## PARAMETERS - -### -CarrierProfile - Microsoft internal usage only - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmergencyDialMask - For each Teams emergency number, you can specify zero or more emergency dial masks. A dial mask is a number that you want to translate into the value of the emergency dial number value when it is dialed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmergencyDialString - Specifies the emergency phone number - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlinePSTNUsage - Specify the online public switched telephone network (PSTN) usage - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsFeedbackPolicy.md b/skype/skype-ps/skype/New-CsTeamsFeedbackPolicy.md deleted file mode 100644 index b9309eba4d..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsFeedbackPolicy.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsfeedbackpolicy -applicable: Skype for Business Online -title: New-CsTeamsFeedbackPolicy -schema: 2.0.0 -manager: bulenteg -ms.author: tomkau -author: tomkau -ms.reviewer: ---- - -# New-CsTeamsFeedbackPolicy - -## SYNOPSIS -Use this cmdlet to control whether users in your organization can send feedback about Teams to Microsoft through Give feedback and whether they receive the survey. - -## SYNTAX - -``` -New-CsTeamsFeedbackPolicy [-WhatIf] [-Confirm] [[-Identity] <Object>] [-Tenant <Object>] [-InMemory] - [-UserInitiatedMode <Object>] [-ReceiveSurveysMode <Object>] [-Force] [-AsJob] -``` - -## DESCRIPTION -Use this cmdlet to control whether users in your organization can send feedback about Teams to Microsoft through Give feedback and whether they receive the survey. By default, all users in your organization are automatically assigned the global (Org-wide default) policy and the Give feedback feature and survey are enabled in the policy. The exception is Teams for Education, where the features are enabled for teachers and disabled for students. For more information, visit [Manage feedback policies in Microsoft Teams](https://docs.microsoft.com/microsoftteams/manage-feedback-policies-in-teams). - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsFeedbackPolicy -identity "New Hire Feedback Policy" -userInitiatedMode disabled -receiveSurveysMode disabled -``` - -In this example, we create a feedback policy called New Hire Feedback Policy and we turn off the ability to give feedback through Give feedback and the survey. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppress all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -The InMemory parameter creates an object reference without actually committing the object as a permanent change. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReceiveSurveysMode -Set the receiveSurveysMode parameter to enabled to allow users who are assigned the policy to receive the survey. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UserInitiatedMode - Set the userInitiatedMode parameter to enabled to allow users who are assigned the policy to give feedback. - Setting the parameter to disabled turns off the feature and users who are assigned the policy don't have the option to give feedback. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md b/skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md deleted file mode 100644 index f0fd455bc4..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md +++ /dev/null @@ -1,448 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsmeetingpolicy -applicable: Skype for Business Online -title: New-CsTeamsMeetingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsTeamsMeetingPolicy - -## SYNOPSIS - The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users -## SYNTAX - -``` -New-CsTeamsMeetingPolicy [-Tenant <Guid>] [-Description <String>] - [-AllowChannelMeetingScheduling <Boolean>] [-AllowMeetNow <Boolean>] [-AllowIPVideo <Boolean>] - [-AllowAnonymousUsersToDialOut <Boolean>] [-AllowAnonymousUsersToStartMeeting <Boolean>] - [-AllowPrivateMeetingScheduling <Boolean>] [-AutoAdmittedUsers <String>] [-AllowCloudRecording <Boolean>] - [-AllowOutlookAddIn <Boolean>] [-AllowPowerPointSharing <Boolean>] - [-AllowParticipantGiveRequestControl <Boolean>] [-AllowExternalParticipantGiveRequestControl <Boolean>] - [-AllowSharedNotes <Boolean>] [-AllowWhiteboard <Boolean>] [-AllowTranscription <Boolean>] - [-MediaBitRateKb <UInt32>] [-ScreenSharingMode <String>] [-PreferredMeetingProviderForIslandsMode <string>] - [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users - -The New-CsTeamsMeetingPolicy cmdlet allows administrators to define new meeting policies that can be assigned to particular users to control Teams features related to meetings. -## EXAMPLES - -### -------------------------- EXAMPLE 1 -------------------------- -``` -New-CsTeamsMeetingPolicy -Identity SalesMeetingPolicy -AllowTranscription $True -``` - -The command shown in Example 1 uses the New-CsTeamsMeetingPolicy cmdlet to create a new meeting policy with the Identity SalesMeetingPolicy. -This policy will use all the default values for a meeting policy except one: AllowTranscription; in this example, meetings for users with this policy can include real time or post meeting captions and transcriptions. - - -### -------------------------- EXAMPLE 2 -------------------------- -``` -New-CsTeamsMeetingPolicy -Identity HrMeetingPolicy -AutoAdmittedUsers "Everyone" -AllowMeetNow $False -``` - -In Example 2, the New-CsTeamsMeetingPolicy cmdlet is used to create a meeting policy with the Identity HrMeetingPolicy. -In this example two different property values are configured: AutoAdmittedUsers is set to Everyone and AllowMeetNow is set to False. -All other policy properties will use the default values. - - -## PARAMETERS - -### -AllowAnonymousUsersToDialOut -Determines whether anonymous users are allowed to dial out to a PSTN number. Set this to TRUE to allow anonymous users to dial out. Set this to FALSE to prohibit anonymous users from dialing out. - -> [!NOTE] -> This parameter is temporarily disabled. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowAnonymousUsersToStartMeeting -Determines whether anonymous users can initiate a meeting. Set this to TRUE to allow anonymous users to initiate a meeting. Set this to FALSE to prohibit them from initiating a meeting - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowChannelMeetingScheduling -Determines whether a user can schedule channel meetings. Set this to TRUE to allow a user to schedule channel meetings. Set this to FALSE to prohibit the user from scheduling channel meetings. Note this only restricts from scheduling and not from joining a meeting scheduled by another user. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCloudRecording -Determines whether cloud recording is allowed in a user's meetings. Set this to TRUE to allow the user to be able to record meetings. Set this to FALSE to prohibit the user from recording meetings - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowExternalParticipantGiveRequestControl -Determines whether external participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit an external user from giving or requesting control in a meeting - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowIPVideo -Determines whether video is enabled in a user's meetings or calls. Set this to TRUE to allow the user to share their video. Set this to FALSE to prohibit the user from sharing their video - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMeetNow -Determines whether a user can start ad-hoc meetings. Set this to TRUE to allow a user to start ad-hoc meetings. Set this to FALSE to prohibit the user from starting ad-hoc meetings. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOutlookAddIn -Determines whether a user can schedule Teams Meetings in Outlook desktop client. Set this to TRUE to allow the user to be able to schedule Teams meetings in Outlook client. Set this to FALSE to prohibit a user from scheduling Teams meeting in Outlook client - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowParticipantGiveRequestControl -Determines whether participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit the user from giving, requesting control in a meeting - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPowerPointSharing -Determines whether Powerpoint sharing is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPrivateMeetingScheduling -Determines whether a user can schedule private meetings. Set this to TRUE to allow a user to schedule private meetings. Set this to FALSE to prohibit the user from scheduling private meetings. Note this only restricts from scheduling and not from joining a meeting scheduled by another user - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowSharedNotes -Determines whether users are allowed to take shared notes. Set this to TRUE to allow. Set this to FALSE to prohibit - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowTranscription -Determines whether real-time and/or post-meeting captions and transcriptions are allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowWhiteboard -Determines whether whiteboard is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutoAdmittedUsers -Determines what types of participants will automatically be added to meetings organized by this user. Set this to EveryoneInCompany if you would like meetings to place every external user in the lobby but allow all users in the company to join the meeting immediately. Set this to Everyone if you'd like to admit anonymous users by default. Set this to EveryoneInSameAndFederatedCompany if you would like meetings to allow federated users to join like your company's users, but place all other external users in a lobby. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -Enables administrators to provide explanatory text about the meeting policy. -For example, the Description might indicate the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the name of the policy being created. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MediaBitRateKb -Determines the media bit rate for audio/video/app sharing transmissions in meetings - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScreenSharingMode -Determines the mode in which a user can share a screen in calls or meetings. Set this to SingleApplication to allow the user to share an application at a given point in time. Set this to EntireScreen to allow the user to share anything on their screens. Set this to Disabled to prohibit the user from sharing their screens. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMeetingProviderForIslandsMode -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: TeamsAndSfb -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsTeamsMessagingPolicy.md b/skype/skype-ps/skype/New-CsTeamsMessagingPolicy.md deleted file mode 100644 index c8cf7de53d..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsMessagingPolicy.md +++ /dev/null @@ -1,400 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsmessagingpolicy -applicable: Skype for Business Online -title: New-CsTeamsMessagingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsTeamsMessagingPolicy - -## SYNOPSIS -The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. - -## SYNTAX - -``` -New-CsTeamsMessagingPolicy [-AllowOwnerDeleteMessage <Boolean>] [-Description <String>] - [-AllowUserChat <Boolean>] [[-Identity] <XdsIdentity>] [-InMemory] [-AllowUserDeleteMessage <Boolean>] - [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>] [-Force] [-AllowStickers <Boolean>] [-AllowUrlPreviews <Boolean>] - [-Tenant <Guid>] [-AllowImmersiveReader <Boolean>] [-AllowUserTranslation <Boolean>] - [-AllowUserEditMessage <Boolean>] [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>] [-AllowRemoveUser <Boolean>] - [-ReadReceiptsEnabledType <String>] [-AllowMemes <Boolean>] [-Confirm] [-AllowPriorityMessages <Boolean>] - [-WhatIf] [-GiphyRatingType <String>] [-AllowGiphy <Boolean>] [-AsJob] - ``` - -## DESCRIPTION - The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. This cmdlet creates a new Teams messaging policy. Custom policies can then be assigned to users using the Grant-CsTeamsMessagingPolicy cmdlet. - -## EXAMPLES - -### Example 1 -``` -powershell -PS C:\> New-CsTeamsMessagingPolicy -Identity StudentMessagingPolicy -AllowGiphy $false -AllowMemes $false -``` - -In this example two different property values are configured: AllowGiphy is set to false and AllowMemes is set to False. -All other policy properties will use the default values. - - -## PARAMETERS - -### -AllowGiphy -Determines whether a user is allowed to access and post Giphys. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMemes -Determines whether a user is allowed to access and post memes. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOwnerDeleteMessage -Determines whether owners are allowed to delete all the messages in their team. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowStickers -Determines whether a user is allowed to access and post stickers. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserChat -Determines whether a user is allowed to chat. Set this to TRUE to allow a user to chat across private chat, group chat and in meetings. Set this to FALSE to prohibit all chat. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserDeleteMessage -Determines whether a user is allowed to delete their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserEditMessage -Determines whether a user is allowed to edit their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserTranslation -Determines whether a user is allowed to translate messages to their client languages. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of your policy to identify purpose of creating it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GiphyRatingType -Determines the Giphy content restrictions applicable to a user. Set this to STRICT, MODERATE or NORESTRICTION. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the teams messaging policy to be created. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChannelsInChatListEnabledType -Possible values are: DisabledUserOverride,EnabledUserOverride. - -```yaml -Type: ChannelsInChatListEnabledTypeEnum -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowImmersiveReader -Determines whether a user is allowed to use Immersive Reader for reading conversation messages. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AudioMessageEnabledType -Determines whether a user is allowed to send audio messages. Possible values are: ChatsAndChannels,ChatsOnly,Disabled. - -```yaml -Type: AudioMessageEnabledTypeEnum -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowRemoveUser -Determines whether a user is allowed to remove a user from a conversation. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPriorityMessages -Determines whether a user is allowed to send priorities messages. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsTeamsMobilityPolicy.md b/skype/skype-ps/skype/New-CsTeamsMobilityPolicy.md deleted file mode 100644 index 4fa821d082..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsMobilityPolicy.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsmobilitypolicy -applicable: Skype for Business Online -title: New-CsTeamsMobilityPolicy -schema: 2.0.0 -manager: ritikag -author: saragava -ms.author: saragava -ms.reviewer: ---- - - -# New-CsTeamsMobilityPolicy - -## SYNOPSIS -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -## SYNTAX - -``` -New-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Description <String>] [-IPVideoMobileMode <String>] - [-IPAudioMobileMode <String>] [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -The New-CsTeamsMobilityPolicy cmdlet lets an Admin create a custom teams mobility policy to assign to particular sets of users. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsMobilityPolicy -Identity SalesMobilityPolicy -IPAudioMobileMode "WifiOnly" -``` - -The command shown in Example 1 uses the New-CsTeamsMobilityPolicy cmdlet to create a new Teams Mobility Policy with the Identity SalesMobilityPolicy and IPAudioMobileMode equal to WifiOnly. - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppress all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPAudioMobileMode -When set to WifiOnly, prohibits the user from making, receiving calls or joining meetings using VoIP calls on the mobile device while on cellular data connection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPVideoMobileMode -When set to WifiOnly, prohibits the user from making, receiving video calls or enabling video in meetings using VoIP calls on the mobile device while on cellular data connection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the name of the policy that you are creating. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsTranslationRule.md b/skype/skype-ps/skype/New-CsTeamsTranslationRule.md deleted file mode 100644 index f87ebb8156..0000000000 --- a/skype/skype-ps/skype/New-CsTeamsTranslationRule.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamstranslationrule -applicable: Skype for Business Online -title: New-CsTeamsTranslationRule -schema: 2.0.0 -manager: nmurav -author: filippse -ms.author: filippse -ms.reviewer: ---- - -# New-CsTeamsTranslationRule - -## SYNOPSIS -Cmdlet to create a new telephone number manipulation rule. - -## SYNTAX - -``` -New-CsTeamsTranslationRule [-Identity <string>] [-Tenant <guid>] [-Description <string>] [-Pattern <string>] [-Translation <string>] [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -You can use this cmdlet to create a new number manipulation rule. The rule can be used, for example, in the settings of your SBC (Set-CSOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsTranslationRule -Identity 'AddPlus1' -Pattern '^(\d{10})$' -Translation '+$1' -``` - -This example creates a rule that adds +1 to any ten digits number. For example, 2065555555 will be translated to +1206555555 - -### Example 2 -```powershell -PS C:\> New-CsTeamsTranslationRule -Identity 'StripPlus1' -Pattern '^\+1(\d{10})$' -Translation '$1' -``` - -This example creates a rule that strips +1 from any E.164 eleven digits number. For example, +12065555555 will be translated to 206555555 - -### Example 3 -```powershell -PS C:\> New-CsTeamsTranslationRule -Identity 'AddE164SeattleAreaCode' -Pattern '^(\d{4})$' -Translation '+120655$1' -``` - -This example creates a rule that adds +1206555 to any four digits number (converts it to E.164number). For example, 5555 will be translated to +1206555555 - -### Example 4 -```powershell -PS C:\> New-CsTeamsTranslationRule -Identity 'AddSeattleAreaCode' -Pattern '^(\d{4})$' -Translation '425555$1' -``` - -This example creates a rule that adds 425555 to any four digits number (converts to non-E.164 ten digits number). For example, 5555 will be translated to 4255555555 - -### Example 5 -```powershell -PS C:\> New-CsTeamsTranslationRule -Identity 'StripE164SeattleAreaCode' -Pattern '^\+1206555(\d{4})$' -Translation '$1' -``` - -This example creates a rule that strips +1206555 from any E.164 ten digits number. For example, +12065555555 will be translated to 5555 - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A friendly description of the normalization rule. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Identifier of the rule. This parameter is required and later used to assign the rule to Inbound or Outbound Trunk Normalization policy. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-<cmdlet>. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Pattern -A regular expression that caller or callee number must match in order for this rule to be applied. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose number manipulation rule is being created. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Translation -The regular expression pattern that will be applied to the number to convert it. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsUpgradePolicy.md b/skype/skype-ps/skype/New-CsTeamsUpgradePolicy.md index 1e36dd9290..e0076883f9 100644 --- a/skype/skype-ps/skype/New-CsTeamsUpgradePolicy.md +++ b/skype/skype-ps/skype/New-CsTeamsUpgradePolicy.md @@ -1,8 +1,8 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml Module Name: SkypeForBusiness -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsupgradepolicy -applicable: Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csteamsupgradepolicy +applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTeamsUpgradePolicy schema: 2.0.0 manager: rogupta @@ -38,7 +38,7 @@ Notes: ### Example 1: Create a site-level policy ```powershell -PS C:\> new-CsTeamsUpgradePolicy -identity site:Redmond1 -NotifySfBUsers $true +PS C:\> new-CsTeamsUpgradePolicy -identity site:Redmond1 -NotifySfBUsers $true ``` This creates a policy for users in the site Redmond1. @@ -46,7 +46,7 @@ This creates a policy for users in the site Redmond1. ### Example 2: Create a policy not specific to a site. ```powershell -PS C:\> new-CsTeamsUpgradePolicy -identity EnableNotifications -NotifySfBUsers $true +PS C:\> new-CsTeamsUpgradePolicy -identity EnableNotifications -NotifySfBUsers $true ``` This creates a policy for users that can be granted as desired to individual users @@ -118,7 +118,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) diff --git a/skype/skype-ps/skype/New-CsTelemetryConfiguration.md b/skype/skype-ps/skype/New-CsTelemetryConfiguration.md index e8511e1acb..8cff3d883a 100644 --- a/skype/skype-ps/skype/New-CsTelemetryConfiguration.md +++ b/skype/skype-ps/skype/New-CsTelemetryConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstelemetryconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cstelemetryconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTelemetryConfiguration schema: 2.0.0 @@ -164,4 +164,3 @@ None. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsTenantBlockedNumberExceptionPattern.md b/skype/skype-ps/skype/New-CsTenantBlockedNumberExceptionPattern.md deleted file mode 100644 index ff2a4a03ee..0000000000 --- a/skype/skype-ps/skype/New-CsTenantBlockedNumberExceptionPattern.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstenantblockednumberexceptionpattern -applicable: Skype for Business Online -title: New-CsTenantBlockedNumberExceptionPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# New-CsTenantBlockedNumberExceptionPattern - -## SYNOPSIS - -## SYNTAX - -### Identity (Default) -``` -New-CsTenantBlockedNumberExceptionPattern [-Tenant <System.Guid>] [-Enabled <Boolean>] [-Description <String>] - -Pattern <String> [-Identity] <XdsGlobalRelativeIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### ParentAndRelativeKey -``` -New-CsTenantBlockedNumberExceptionPattern [-Tenant <System.Guid>] -Name <String> [-Enabled <Boolean>] - [-Description <String>] -Pattern <String> [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 -```powershell -PS C:> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -{{ Fill Description Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -{{ Fill Enabled Description }} - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{ Fill Force Description }} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -{{ Fill Identity Description }} - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -{{ Fill InMemory Description }} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -{{ Fill Name Description }} - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Pattern -{{ Fill Pattern Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -{{ Fill Tenant Description }} - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTenantDialPlan.md b/skype/skype-ps/skype/New-CsTenantDialPlan.md deleted file mode 100644 index 43812c5d1c..0000000000 --- a/skype/skype-ps/skype/New-CsTenantDialPlan.md +++ /dev/null @@ -1,275 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstenantdialplan -applicable: Skype for Business Online -title: New-CsTenantDialPlan -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsTenantDialPlan - -## SYNOPSIS -Use the `New-CsTenantDialPlan` cmdlet to create a new tenant dial plan. - -## SYNTAX - -``` -New-CsTenantDialPlan [-Tenant <Guid>] [-Description <String>] [-NormalizationRules <List>] - [-ExternalAccessPrefix <String>] [-SimpleName <String>] [-OptimizeDeviceDialing <Boolean>] - [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -You can use this cmdlet to create a new tenant dial plan. -Tenant dial plans provide required information to let Enterprise Voice users make telephone calls. -The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. -A tenant dial plan determines such things as which normalization rules are applied and whether a prefix must be dialed for external calls. - -You can add new normalization rules to a tenant dial plan by calling the `New-CsVoiceNormalizationRule` (https://technet.microsoft.com/en-us/library/gg398240.aspx) cmdlet. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -New-CsTenantDialPlan -Identity vt1tenantDialPlan9 -``` - -This example creates a tenant dial plan that has an Identity of vt1tenantDialPlan9. - - -### -------------------------- Example 2 -------------------------- -``` -$nr2 = New-CsVoiceNormalizationRule -Identity Global/NR2 -Description "TestNR1" -Pattern '^(d{11})$' -Translation '+1' -InMemory - -New-CsTenantDialPlan -Identity vt1tenantDialPlan91 -NormalizationRules @{Add=$nr2} -``` - -This example creates a new normalization rule and then applies that rule to a new tenant dial plan. - - -## PARAMETERS - -### -Identity -The Identity parameter is a unique identifier that designates the name of the tenant dial plan. -Identity is an alphanumeric string that cannot exceed 49 characters. -Valid characters are alphabetic or numeric characters, hyphen (-) and dot (.). -The value should not begin with a (.) - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -The Description parameter describes the tenant dial plan - what it's for, what type of user it applies to and any other information that helps to identify the purpose of the tenant dial plan. -Maximum characters: 512. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalAccessPrefix -The ExternalAccessPrefix parameter is a number (or set of numbers) that designates the call as external to the organization. -(For example, to tenant-dial an outside line, first press 9.) This prefix is ignored by the normalization rules, although these rules are applied to the remainder of the number. - -The OptimizeDeviceDialing parameter must be set to True for this value to take effect. -This parameter must match the regular expression \[0-9\]{1,4}: that is, it must be a value 0 through 9 and one to four digits in length. -The default value is 9. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -The InMemory parameter creates an object reference without actually committing the object as a permanent change. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NormalizationRules -The NormalizationRules parameter is a list of normalization rules that are applied to this dial plan. -Although this list and these rules can be created directly by using this cmdlet, we recommend that you create the normalization rules by the `New-CsVoiceNormalizationRule` (https://technet.microsoft.com/en-us/library/gg398240.aspx) cmdlet, which creates the rule and assigns it to the specified tenant dial plan. - -Each time a new tenant dial plan is created, a new voice normalization rule with default settings is also created for that site, service, or per-user tenant dial plan. -By default, the Identity of the new voice normalization rule is the tenant dial plan Identity followed by a slash and then followed by the name Prefix All. -(For example, TAG:Redmond/Prefix All.) The number of normalization rules cannot exceed 50 per TenantDialPlan. - -You can create a new normalization rule by calling the `New-CsVoiceNormalizationRule` (https://technet.microsoft.com/en-us/library/gg398240.aspx) cmdlet. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OptimizeDeviceDialing -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SimpleName -The SimpleName parameter is a display name for the tenant dial plan. -This name must be unique among all tenant dial plans within the Skype for Business Server deployment. - -This string can be up to 49 characters long. -Valid characters are alphabetic or numeric characters, hyphen (-), dot (.) and parentheses (()). - -This parameter must contain a value. -However, if you don't provide a value, a default value will be supplied. -The default value for a Global tenant dial plan is Prefix All. -The default value for a site-level tenant dial plan is the name of the site. -The default value for a service is the name of the service (Registrar or PSTN gateway) followed by an underscore, followed by the service fully qualified domain name (FQDN). -For example: Registrar_pool0.litwareinc.com. -The default value for a per-user tenant dial plan is the Identity of the tenant dial plan. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"`. -You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsTenantNetworkRegion.md b/skype/skype-ps/skype/New-CsTenantNetworkRegion.md deleted file mode 100644 index 8cb7086a24..0000000000 --- a/skype/skype-ps/skype/New-CsTenantNetworkRegion.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstenantnetworkregion -applicable: Skype for Business Online -title: New-CsTenantNetworkRegion -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsTenantNetworkRegion - -## SYNOPSIS -As an Admin, you can use the Windows PowerShell command, New-CsTenantNetworkRegion to define network regions. A network region interconnects various parts of a network across multiple geographic areas. The RegionID parameter is a logical name that represents the geography of the region, and has no dependencies or restrictions. Tenant network region is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -New-CsTenantNetworkRegion [-Tenant <System.Guid>] [-Description <String>] [-BypassID <String>] - [-CentralSite <String>] [-Identity] <XdsGlobalRelativeIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### ParentAndRelativeKey -``` -New-CsTenantNetworkRegion -NetworkRegionID <String> [-Tenant <System.Guid>] [-Description <String>] - [-BypassID <String>] [-CentralSite <String>] [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. A network region contains a collection of network sites. For example, if your organization has many sites located in Redmond, then you may choose to designate "Redmond" as a network region. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> New-CsTenantNetworkRegion -NetworkRegionID "RegionA" -``` - -The command shown in Example 1 created the network region 'RegionA' with no description. Identity and CentralSite will both be set identical with NetworkRegionID. - -Previously in Skype for Business there was an additional required parameter `-CentralSite <site ID>`, however it is now optional. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> New-CsTenantNetworkRegion -NetworkRegionID "RegionRedmond" -Description "Redmond region" -CentralSite "Central site 1" -``` - -The command shown in Example 2 created the network region 'RegionRedmond' with description 'Redmond region'. CentralSite is set to "Central site 1". - -## PARAMETERS - -### -BypassID -Bypass ID was not required and not used in current commands. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CentralSite -This parameter is optional. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of the network region to identify purpose of creating it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network region to be created. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetworkRegionID -The name of the network region. This must be a string that is unique. You cannot specify an NetworkRegionID and an Identity at the same time. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network regions are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTenantNetworkSite.md b/skype/skype-ps/skype/New-CsTenantNetworkSite.md deleted file mode 100644 index 4d5f41bd9f..0000000000 --- a/skype/skype-ps/skype/New-CsTenantNetworkSite.md +++ /dev/null @@ -1,280 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstenantnetworksite -applicable: Skype for Business Online -title: New-CsTenantNetworkSite -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsTenantNetworkSite - -## SYNOPSIS -As an Admin, you can use the Windows PowerShell command, New-CsTenantNetworkSite to define network sites. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. Tenant network site is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -New-CsTenantNetworkSite [-Tenant <System.Guid>] [-Description <String>] [-NetworkRegionID <String>] - [-LocationPolicy <String>] [-EnableLocationBasedRouting <Boolean>] [-OnlineVoiceRoutingPolicy <String>] - [-SiteAddress <String>] [-Identity] <XdsGlobalRelativeIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### ParentAndRelativeKey -``` -New-CsTenantNetworkSite [-Tenant <System.Guid>] -NetworkSiteID <String> [-Description <String>] - [-NetworkRegionID <String>] [-LocationPolicy <String>] [-EnableLocationBasedRouting <Boolean>] - [-OnlineVoiceRoutingPolicy <String>] [-SiteAddress <String>] [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. - -A best practice for Location Based Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> New-CsTenantNetworkSite -NetworkSiteID "MicrosoftSite1" -NetworkRegionID "RegionRedmond" -``` - -The command shown in Example 1 created the network site 'MicrosoftSite1' with no description. Identity will be set identical with NetworkSiteID. - -The network region 'RegionRedmond' is created beforehand and 'MicrosoftSite1' will be associated with 'RegionRedmond'. - -NetworkSites can exist without all parameters excepts NetworkSiteID. NetworkRegionID can be left blank. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> New-CsTenantNetworkSite -NetworkSiteID "site2" -Description "site 2" -NetworkRegionID "RedmondRegion" -LocationPolicy "TestLocationPolicy" -EnableLocationBasedRouting $true -SiteAddress "One Microsoft way" -OnlineVoiceRoutingPolicy "OVRP1" -``` - -The command shown in Example 2 created the network site 'site2' with description 'site 2'. This site is enabled for LBR, and associates with network region 'RedmondRegion', with location policy 'TestLocationPolicy', and with OnlineVoiceRoutingPolicy "OVRP1" - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of the network site to identify purpose of creating it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableLocationBasedRouting -This parameter determines whether the current site is enabled for location based routing. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network site to be created. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationPolicy -LocationPolicy is the identifier for the location policy which the current network site is associating to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetworkRegionID -NetworkRegionID is the identifier for the network region which the current network site is associating to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetworkSiteID -The name of the network site. This must be a string that is unique. You cannot specify an NetworkSiteID and an Identity at the same time. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlineVoiceRoutingPolicy -This parameter determines the unique name of existing OnlineVoiceRoutingPolicy that the current network site associates to. - -OnlineVoiceRoutingPolicy is used to associate a user with the appropriate PSTN usages. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SiteAddress -The address of current network site. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network sites are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTenantNetworkSubnet.md b/skype/skype-ps/skype/New-CsTenantNetworkSubnet.md deleted file mode 100644 index 2c04ae6a0b..0000000000 --- a/skype/skype-ps/skype/New-CsTenantNetworkSubnet.md +++ /dev/null @@ -1,232 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstenantnetworksubnet -applicable: Skype for Business Online -title: New-CsTenantNetworkSubnet -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# New-CsTenantNetworkSubnet - -## SYNOPSIS -As an Admin, you can use the Windows PowerShell command, New-CsTenantNetworkSubnet to define network subnets and assign them to network sites. Each internal subnet may only be associated with one site. Tenant network subnet is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -New-CsTenantNetworkSubnet [-Tenant <System.Guid>] [-Description <String>] [-NetworkSiteID <String>] - -MaskBits <Int32> [-Identity] <XdsGlobalRelativeIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### ParentAndRelativeKey -``` -New-CsTenantNetworkSubnet [-Tenant <System.Guid>] -SubnetID <String> [-Description <String>] - [-NetworkSiteID <String>] -MaskBits <Int32> [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first. - -When the client is sending the network subnet, please make sure we have already whitelisted the IP address by running this command-let, otherwise the request will be rejected. If you are only adding the IPv4 address by running this command-let, but your client are only sending and IPv6 address, it will be rejected. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> New-CsTenantNetworkSubnet -SubnetID "192.168.0.1" -MaskBits "24" -NetworkSiteID "site1" -``` - -The command shown in Example 1 created the network subnet '192.168.0.1' with no description. The subnet is IPv4 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 24. - -IPv4 format subnet accepts maskbits from 0 to 32 inclusive. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> New-CsTenantNetworkSubnet -SubnetID "2001:4898:e8:25:844e:926f:85ad:dd8e" -MaskBits "120" -NetworkSiteID "site1" -``` - -The command shown in Example 2 created the network subnet '2001:4898:e8:25:844e:926f:85ad:dd8e' with no description. The subnet is IPv6 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 120. - -IPv6 format subnet accepts maskbits from 0 to 128 inclusive. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of the network subnet to identify purpose of creating it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network subnet to be created. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaskBits -This parameter determines the length of bits to mask to the subnet. - -IPv4 format subnet accepts maskbits from 0 to 32 inclusive. IPv6 format subnet accepts maskbits from 0 to 128 inclusive. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetworkSiteID -NetworkSiteID is the identifier for the network site which the current network subnet is associating to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubnetID -The name of the network subnet. This must be a unique and valid IPv4 or IPv6 address. You cannot specify an NetworkSubnetID and an Identity at the same time. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network subnets are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTenantUpdateTimeWindow.md b/skype/skype-ps/skype/New-CsTenantUpdateTimeWindow.md index 5fd198b0fe..11a5b21e8e 100644 --- a/skype/skype-ps/skype/New-CsTenantUpdateTimeWindow.md +++ b/skype/skype-ps/skype/New-CsTenantUpdateTimeWindow.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstenantupdatetimewindow +online version: https://learn.microsoft.com/powershell/module/skype/new-cstenantupdatetimewindow applicable: Skype for Business Online title: New-CsTenantUpdateTimeWindow schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsTenantUpdateTimeWindow @@ -337,4 +337,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsTestDevice.md b/skype/skype-ps/skype/New-CsTestDevice.md index 946c6c0809..74d4439948 100644 --- a/skype/skype-ps/skype/New-CsTestDevice.md +++ b/skype/skype-ps/skype/New-CsTestDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstestdevice +online version: https://learn.microsoft.com/powershell/module/skype/new-cstestdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTestDevice schema: 2.0.0 @@ -267,4 +267,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.De [Remove-CsTestDevice](Remove-CsTestDevice.md) [Set-CsTestDevice](Set-CsTestDevice.md) - diff --git a/skype/skype-ps/skype/New-CsThirdPartyVideoSystem.md b/skype/skype-ps/skype/New-CsThirdPartyVideoSystem.md index 72e23d2651..b99a3a2d81 100644 --- a/skype/skype-ps/skype/New-CsThirdPartyVideoSystem.md +++ b/skype/skype-ps/skype/New-CsThirdPartyVideoSystem.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csthirdpartyvideosystem +online version: https://learn.microsoft.com/powershell/module/skype/new-csthirdpartyvideosystem applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsThirdPartyVideoSystem schema: 2.0.0 @@ -256,4 +256,3 @@ The `New-CsThirdPartyVideoSystem` cmdlet creates new instances of the Microsoft. [Remove-CsThirdPartyVideoSystem](Remove-CsThirdPartyVideoSystem.md) [Set-CsThirdPartyVideoSystem](Set-CsThirdPartyVideoSystem.md) - diff --git a/skype/skype-ps/skype/New-CsThirdPartyVideoSystemPolicy.md b/skype/skype-ps/skype/New-CsThirdPartyVideoSystemPolicy.md index 67bafce935..4043433c11 100644 --- a/skype/skype-ps/skype/New-CsThirdPartyVideoSystemPolicy.md +++ b/skype/skype-ps/skype/New-CsThirdPartyVideoSystemPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csthirdpartyvideosystempolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csthirdpartyvideosystempolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsThirdPartyVideoSystemPolicy schema: 2.0.0 @@ -196,4 +196,3 @@ The `New-CsThirdPartyVideoSystemPolicy` cmdlet creates new instances of the Micr [Remove-CsThirdPartyVideoSystemPolicy](Remove-CsThirdPartyVideoSystemPolicy.md) [Set-CsThirdPartyVideoSystemPolicy](Set-CsThirdPartyVideoSystemPolicy.md) - diff --git a/skype/skype-ps/skype/New-CsTrunkConfiguration.md b/skype/skype-ps/skype/New-CsTrunkConfiguration.md index 802c676bea..f7e31d7df2 100644 --- a/skype/skype-ps/skype/New-CsTrunkConfiguration.md +++ b/skype/skype-ps/skype/New-CsTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cstrunkconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTrunkConfiguration schema: 2.0.0 @@ -27,7 +27,7 @@ New-CsTrunkConfiguration [-Identity] <XdsIdentity> [-ConcentratedTopology <Boole [-RTCPActiveCalls <Boolean>] [-RTCPCallsOnHold <Boolean>] [-SipResponseCodeTranslationRulesList <PSListModifier>] [-SRTPMode <SRTPMode>] [-Force] [-InMemory] [-WhatIf] [-Confirm] [-Enable3pccRefer <Boolean>] [-EnableFastFailoverTimer <Boolean>] [-EnableOnlineVoice <Boolean>] - [-EnableRTPLatching <Boolean>] [-ForwardCallHistory <Boolean>] [-ForwardPAI <Boolean>] + [-EnableRTPLatching <Boolean>] [-ForwardCallHistory <Boolean>] [-ForwardPAI <Boolean>] [-ForwardAnonymousCallGatewayPAI <Boolean>] [-OutboundCallingNumberTranslationRulesList <PSListModifier>] [-PstnUsages <PSListModifier>] [-EnableLocationRestriction <Boolean>] [-NetworkSiteID <String>] [<CommonParameters>] ``` @@ -598,6 +598,26 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ForwardAnonymousCallGatewayPAI +If an anonymous call is forwarded to an outgoing PSTN call, this parameter indicates whether the incoming P-Asserted-Identity (PAI) header at the Gateway call will be preserved in the PSTN call. The default value is **False** ($False). + +**Notes:** +- `EnablePAIPAssthrough` is deprecated in favor of `ForwardAnonymousCallGatewayPAI`. This change is made by installing KB5016483. +- When `ForwardAnonymousCallGatewayPAI` is used, `ForwardPAI` must be set to **True**. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -OutboundCallingNumberTranslationRulesList Collection of outbound calling number translation rules assigned to the trunk. You can retrieve information about the available rules by running this command: @@ -704,4 +724,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Trunk [Test-CsTrunkConfiguration](Test-CsTrunkConfiguration.md) [New-CsOutboundTranslationRule](New-CsOutboundTranslationRule.md) - diff --git a/skype/skype-ps/skype/New-CsTrustedApplication.md b/skype/skype-ps/skype/New-CsTrustedApplication.md index 18dc245ff7..a46ee864c0 100644 --- a/skype/skype-ps/skype/New-CsTrustedApplication.md +++ b/skype/skype-ps/skype/New-CsTrustedApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstrustedapplication +online version: https://learn.microsoft.com/powershell/module/skype/new-cstrustedapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTrustedApplication schema: 2.0.0 @@ -263,4 +263,3 @@ Creates an object of type Microsoft.Rtc.Management.Xds.DisplayTrustedApplication [Set-CsTrustedApplication](Set-CsTrustedApplication.md) [Get-CsTrustedApplication](Get-CsTrustedApplication.md) - diff --git a/skype/skype-ps/skype/New-CsTrustedApplicationComputer.md b/skype/skype-ps/skype/New-CsTrustedApplicationComputer.md index b4650c484b..1f2dd613a9 100644 --- a/skype/skype-ps/skype/New-CsTrustedApplicationComputer.md +++ b/skype/skype-ps/skype/New-CsTrustedApplicationComputer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstrustedapplicationcomputer +online version: https://learn.microsoft.com/powershell/module/skype/new-cstrustedapplicationcomputer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTrustedApplicationComputer schema: 2.0.0 @@ -156,4 +156,3 @@ Creates an object of type Microsoft.Rtc.Management.Xds.DisplayComputer. [New-CsTrustedApplicationPool](New-CsTrustedApplicationPool.md) [Get-CsTrustedApplicationPool](Get-CsTrustedApplicationPool.md) - diff --git a/skype/skype-ps/skype/New-CsTrustedApplicationEndpoint.md b/skype/skype-ps/skype/New-CsTrustedApplicationEndpoint.md index 2ef6736315..9013c9e9a4 100644 --- a/skype/skype-ps/skype/New-CsTrustedApplicationEndpoint.md +++ b/skype/skype-ps/skype/New-CsTrustedApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstrustedapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/new-cstrustedapplicationendpoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTrustedApplicationEndpoint schema: 2.0.0 @@ -292,4 +292,3 @@ Creates an object of type Microsoft.Rtc.Management.ADConnect.Schema.OCSADApplica [Set-CsTrustedApplicationEndpoint](Set-CsTrustedApplicationEndpoint.md) [Get-CsTrustedApplicationEndpoint](Get-CsTrustedApplicationEndpoint.md) - diff --git a/skype/skype-ps/skype/New-CsTrustedApplicationPool.md b/skype/skype-ps/skype/New-CsTrustedApplicationPool.md index 76d4eb2de9..cd945137d5 100644 --- a/skype/skype-ps/skype/New-CsTrustedApplicationPool.md +++ b/skype/skype-ps/skype/New-CsTrustedApplicationPool.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cstrustedapplicationpool +online version: https://learn.microsoft.com/powershell/module/skype/new-cstrustedapplicationpool applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsTrustedApplicationPool schema: 2.0.0 @@ -412,4 +412,3 @@ Creates an object of type Microsoft.Rtc.Management.Xds.DisplayExternalServer. [New-CsTrustedApplicationComputer](New-CsTrustedApplicationComputer.md) [Get-CsSite](Get-CsSite.md) - diff --git a/skype/skype-ps/skype/New-CsUCPhoneConfiguration.md b/skype/skype-ps/skype/New-CsUCPhoneConfiguration.md index 022c8e3579..30a0ec713e 100644 --- a/skype/skype-ps/skype/New-CsUCPhoneConfiguration.md +++ b/skype/skype-ps/skype/New-CsUCPhoneConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csucphoneconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csucphoneconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsUCPhoneConfiguration schema: 2.0.0 @@ -354,4 +354,3 @@ Creates instances of the Microsoft.Rtc.Management.WritableConfig.Policy.Voice.Uc [Remove-CsUCPhoneConfiguration](Remove-CsUCPhoneConfiguration.md) [Set-CsUCPhoneConfiguration](Set-CsUCPhoneConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsUnassignedNumber.md b/skype/skype-ps/skype/New-CsUnassignedNumber.md index 32317e3c0a..963f52646a 100644 --- a/skype/skype-ps/skype/New-CsUnassignedNumber.md +++ b/skype/skype-ps/skype/New-CsUnassignedNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csunassignednumber +online version: https://learn.microsoft.com/powershell/module/skype/new-csunassignednumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsUnassignedNumber schema: 2.0.0 @@ -308,4 +308,3 @@ Creates an object of type Microsoft.Rtc.Management.Voice.Helpers.DisplayAnnounce [Get-CsAnnouncement](Get-CsAnnouncement.md) [Get-CsExUmContact](Get-CsExUmContact.md) - diff --git a/skype/skype-ps/skype/New-CsUserReplicatorConfiguration.md b/skype/skype-ps/skype/New-CsUserReplicatorConfiguration.md index 84ad592acb..285f45e328 100644 --- a/skype/skype-ps/skype/New-CsUserReplicatorConfiguration.md +++ b/skype/skype-ps/skype/New-CsUserReplicatorConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csuserreplicatorconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csuserreplicatorconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsUserReplicatorConfiguration schema: 2.0.0 @@ -249,4 +249,3 @@ The `New-CsUserReplicatorConfiguration` cmdlet creates new instances of the Micr [Remove-CsUserReplicatorConfiguration](Remove-CsUserReplicatorConfiguration.md) [Set-CsUserReplicatorConfiguration](Set-CsUserReplicatorConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsUserServicesConfiguration.md b/skype/skype-ps/skype/New-CsUserServicesConfiguration.md index e0468d4c56..6a6f17e252 100644 --- a/skype/skype-ps/skype/New-CsUserServicesConfiguration.md +++ b/skype/skype-ps/skype/New-CsUserServicesConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csuserservicesconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csuserservicesconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsUserServicesConfiguration schema: 2.0.0 @@ -445,4 +445,3 @@ The `New-CsUserServicesConfiguration` cmdlet creates new instances of the Micros [Remove-CsUserServicesConfiguration](Remove-CsUserServicesConfiguration.md) [Set-CsUserServicesConfiguration](Set-CsUserServicesConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsUserServicesPolicy.md b/skype/skype-ps/skype/New-CsUserServicesPolicy.md index 8695591188..d9608afa86 100644 --- a/skype/skype-ps/skype/New-CsUserServicesPolicy.md +++ b/skype/skype-ps/skype/New-CsUserServicesPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csuserservicespolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csuserservicespolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsUserServicesPolicy schema: 2.0.0 @@ -254,4 +254,3 @@ The `New-CsUserServicesPolicy` cmdlet creates new instances of the Microsoft.Rtc [Remove-CsUserServicesPolicy](Remove-CsUserServicesPolicy.md) [Set-CsUserServicesPolicy](Set-CsUserServicesPolicy.md) - diff --git a/skype/skype-ps/skype/New-CsVideoInteropServerConfiguration.md b/skype/skype-ps/skype/New-CsVideoInteropServerConfiguration.md index 191733e3b2..3c55431495 100644 --- a/skype/skype-ps/skype/New-CsVideoInteropServerConfiguration.md +++ b/skype/skype-ps/skype/New-CsVideoInteropServerConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvideointeropserverconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csvideointeropserverconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVideoInteropServerConfiguration schema: 2.0.0 @@ -185,4 +185,3 @@ The `New-CsVideoInteropServerConfiguration` cmdlet creates new instances of the [Remove-CsVideoInteropServerConfiguration](Remove-CsVideoInteropServerConfiguration.md) [Set-CsVideoInteropServerConfiguration](Set-CsVideoInteropServerConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsVideoInteropServerSyntheticTransactionConfiguration.md b/skype/skype-ps/skype/New-CsVideoInteropServerSyntheticTransactionConfiguration.md index c32be64dce..090e344050 100644 --- a/skype/skype-ps/skype/New-CsVideoInteropServerSyntheticTransactionConfiguration.md +++ b/skype/skype-ps/skype/New-CsVideoInteropServerSyntheticTransactionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvideointeropserversynthetictransactionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csvideointeropserversynthetictransactionconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVideoInteropServerSyntheticTransactionConfiguration schema: 2.0.0 @@ -179,4 +179,3 @@ Returns a VideoInteropServerSyntheticTransactionConfiguration object. [Remove-CsVideoInteropServerSyntheticTransactionConfiguration](Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md) [Test-CsP2PVideoInteropServerSipTrunkAV](Test-CsP2PVideoInteropServerSipTrunkAV.md) - diff --git a/skype/skype-ps/skype/New-CsVideoTrunkConfiguration.md b/skype/skype-ps/skype/New-CsVideoTrunkConfiguration.md index bc8bfc3371..554d14112c 100644 --- a/skype/skype-ps/skype/New-CsVideoTrunkConfiguration.md +++ b/skype/skype-ps/skype/New-CsVideoTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvideotrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csvideotrunkconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVideoTrunkConfiguration schema: 2.0.0 @@ -32,7 +32,7 @@ The Video Interop Server is a Skype service that runs on a standalone pool and c To enable the Video Interop Server, you must use Topology Builder to define at least one VIS instance. Each VIS instance will typically be associated with one or more Video Gateways. -Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from an third party PBX supporting 3rd party video teleconferencing systems (VTCs). +Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from a third party PBX supporting 3rd party video teleconferencing systems (VTCs). The Video Gateway and a Video Interop Server (VIS) use a Session Initiation Protocol (SIP) trunk to connect video calls between third party VTCs and internal endpoints. Video Trunks settings can be managed by using the CsVideoTrunkConfiguration cmdlets. @@ -264,4 +264,3 @@ The `New-CsVideoTrunkConfiguration` cmdlet creates new instances of the Microsof [Set-CsVideoTrunkConfiguration](Set-CsVideoTrunkConfiguration.md) [Remove-CsVideoTrunkConfiguration](Remove-CsVideoTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsVoiceNormalizationRule.md b/skype/skype-ps/skype/New-CsVoiceNormalizationRule.md index 13f5901988..9404a4f7ca 100644 --- a/skype/skype-ps/skype/New-CsVoiceNormalizationRule.md +++ b/skype/skype-ps/skype/New-CsVoiceNormalizationRule.md @@ -1,20 +1,22 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvoicenormalizationrule -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csvoicenormalizationrule +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVoiceNormalizationRule schema: 2.0.0 manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: rogupta +author: jenstrier +ms.author: serdars --- # New-CsVoiceNormalizationRule ## SYNOPSIS Creates a new voice normalization rule. -Voice normalization rules are used to convert a telephone dialing requirement (for example, dialing 9 to access an outside line) to the E.164 phone number format used by Skype for Business Server. + +Voice normalization rules are used to convert a telephone dialing requirement (for example, dialing 9 to access an outside line) to the E.164 phone number format used by +Skype for Business Server or Microsoft Teams. + This cmdlet was introduced in Lync Server 2010. @@ -37,13 +39,17 @@ New-CsVoiceNormalizationRule [-Tenant <Guid>] -Parent <String> -Name <String> [- ## DESCRIPTION This cmdlet creates a named voice normalization rule. These rules are a required part of phone authorization and call routing. -They define the requirements for converting (or translating) numbers from an internal Skype for Business Server format to a standard (E.164) format. +They define the requirements for converting (or translating) numbers from an internal format to a standard (E.164) format. An understanding of regular expressions is helpful in order to define number patterns that will be translated. -Rules that are created by using this cmdlet are part of the dial plan and in addition to being accessible through the `Get-CsVoiceNormalizationRule` cmdlet, can also be accessed through the NormalizationRules property returned by a call to the `Get-CsDialPlan` cmdlet. +For Lync or Skype for Business Server, rules that are created by using this cmdlet are part of the dial plan and in addition to being accessible through the +The `Get-CsVoiceNormalizationRule` cmdlet can also be accessed through the NormalizationRules property returned by a call to the `Get-CsDialPlan` cmdlet. You cannot create a normalization rule unless a dial plan with an Identity matching the scope specified in the normalization rule Identity already exists. For example, you can't create a normalization rule with the Identity site:Redmond/RedmondNormalizationRule unless a dial plan for site:Redmond already exists. +For Microsoft Teams, rules that are created by using this cmdlet can only be created with the InMemory switch and should be added to a tenant dial plan using +the `New-CsTenantDialPlan` or `Set-CsTenantDialPlan` cmdlets. + ## EXAMPLES @@ -78,6 +84,13 @@ Single quotes are required for these values; double quotes (or no quotes) will n As in Example 1, a dial plan with the given scope must exist. In this case, that means a dial plan with the Identity SeattleUser must already exist. +### -------------------------- Example 3 -------------------------- +``` +$nr1=New-CsVoiceNormalizationRule -Identity dp1/nr1 -Description "Dialing with internal four-digit extension" -Pattern '^(\d{4})$' -Translation '+1206555$1' -InMemory +New-CsTenantDialPlan -Identity DP1 -NormalizationRules @{Add=$nr1} +``` + +This example creates a new in-memory voice normalization rule and then adds it to a new tenant dial plan DP1 to be used for Microsoft Teams users. ## PARAMETERS @@ -87,10 +100,12 @@ The Identity specified must include the scope followed by a slash and then the n The name portion will automatically be stored in the Name property. You cannot specify values for Identity and Name in the same command. -Voice normalization rules can be created at the following scopes: global, site, service (Registrar and PSTNGateway only) and per user. +For Lync and Skype for Business Server, voice normalization rules can be created at the following scopes: global, site, service (Registrar and PSTNGateway only) and per user. A dial plan with an Identity matching the scope of the normalization rule must already exist before a new rule can be created. (To retrieve a list of dial plans, call the `Get-CsDialPlan` cmdlet.) +For Microsoft Teams, voice normalization rules can be created at the following scopes: global and tag. + The Identity parameter is required unless the Parent parameter is specified. You cannot include the Identity parameter and the Parent parameter in the same command. @@ -99,7 +114,7 @@ You cannot include the Identity parameter and the Parent parameter in the same c Type: XdsIdentity Parameter Sets: Identity Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: True Position: 2 @@ -119,7 +134,7 @@ The Name parameter and the Identity parameter cannot be used in the same command Type: String Parameter Sets: ParentAndRelativeKey Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: True Position: Named @@ -130,7 +145,8 @@ Accept wildcard characters: False ### -Parent The scope at which the new normalization rule will be created. -This value must be global; site:\<sitename\>, where \<sitename\> is the name of the Skype for Business Server site; PSTN gateway or Registrar service, such as PSTNGateway:redmond.litwareinc.com; or a string designating a per user rule. +This value must be global; site:\<sitename\>, where \<sitename\> is the name of the Skype for Business Server site; PSTN gateway or Registrar service, such as +PSTNGateway:redmond.litwareinc.com; or a string designating a per user rule. A dial plan with the specified scope must already exist or the command will fail. The Parent parameter is required unless the Identity parameter is specified. @@ -141,7 +157,7 @@ If you include the Parent parameter, the Name parameter is also required. Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -159,7 +175,7 @@ Maximum string length: 512 characters. Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -171,7 +187,7 @@ Accept wildcard characters: False ### -IsInternalExtension If True, the result of applying this rule will be a number internal to the organization. If False, applying the rule results in an external number. -This value is ignored if the value of the OptimizeDeviceDialing property of the associated dial plan is set to False. +This value is ignored if the value of the OptimizeDeviceDialing property of the associated dial plan/tenant dial plan is set to False. Default: False @@ -179,7 +195,7 @@ Default: False Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -197,7 +213,7 @@ Default: ^(\d{11})$ (The default represents any set of numbers up to 11 digits.) Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -215,7 +231,7 @@ This parameter sets the order in which the rules are tested against the number. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -233,7 +249,7 @@ Default: +$1 (The default prefixes the number with a plus sign \[+\].) Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -249,7 +265,7 @@ Suppresses any confirmation prompts that would otherwise be displayed before mak Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -260,13 +276,15 @@ Accept wildcard characters: False ### -InMemory Creates an object reference without actually committing the object as a permanent change. -If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-\<cmdlet\>. + +For Lync or Skype for Business Server, if you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the +object reference and then commit those changes by calling this cmdlet's matching Set-\<cmdlet\>. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -275,6 +293,19 @@ Accept pipeline input: False Accept wildcard characters: False ``` +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf Describes what would happen if you executed the command without actually executing the command. @@ -282,7 +313,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -298,7 +329,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -308,13 +339,13 @@ Accept wildcard characters: False ``` ### -Tenant -{{Fill Tenant Description}} +For internal Microsoft usage. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named diff --git a/skype/skype-ps/skype/New-CsVoicePolicy.md b/skype/skype-ps/skype/New-CsVoicePolicy.md index 7a0347ea73..1f0e3f4982 100644 --- a/skype/skype-ps/skype/New-CsVoicePolicy.md +++ b/skype/skype-ps/skype/New-CsVoicePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvoicepolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csvoicepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVoicePolicy schema: 2.0.0 @@ -601,4 +601,3 @@ This cmdlet creates an instance of the Microsoft.Rtc.Management.WritableConfig.V [Test-CsVoicePolicy](Test-CsVoicePolicy.md) [Get-CsPstnUsage](Get-CsPstnUsage.md) - diff --git a/skype/skype-ps/skype/New-CsVoiceRegex.md b/skype/skype-ps/skype/New-CsVoiceRegex.md index def2b44ee6..dfa493a3db 100644 --- a/skype/skype-ps/skype/New-CsVoiceRegex.md +++ b/skype/skype-ps/skype/New-CsVoiceRegex.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvoiceregex -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csvoiceregex +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVoiceRegex schema: 2.0.0 manager: bulenteg @@ -193,4 +193,3 @@ Creates on object of type Microsoft.Rtc.Management.Voice.OcsVoiceRegex. [New-CsOutboundTranslationRule](New-CsOutboundTranslationRule.md) [New-CsVoiceRoute](New-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/New-CsVoiceRoute.md b/skype/skype-ps/skype/New-CsVoiceRoute.md index deebe0fda1..f6633618bd 100644 --- a/skype/skype-ps/skype/New-CsVoiceRoute.md +++ b/skype/skype-ps/skype/New-CsVoiceRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvoiceroute +online version: https://learn.microsoft.com/powershell/module/skype/new-csvoiceroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVoiceRoute schema: 2.0.0 @@ -362,4 +362,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Voice.R [Get-CsPstnUsage](Get-CsPstnUsage.md) [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/New-CsVoiceRoutingPolicy.md b/skype/skype-ps/skype/New-CsVoiceRoutingPolicy.md index fa21fd1d59..f6a0bd7f8b 100644 --- a/skype/skype-ps/skype/New-CsVoiceRoutingPolicy.md +++ b/skype/skype-ps/skype/New-CsVoiceRoutingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvoiceroutingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/new-csvoiceroutingpolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVoiceRoutingPolicy schema: 2.0.0 @@ -219,4 +219,3 @@ The `New-CsVoiceRoutingPolicy` cmdlet creates new instances of Microsoft.Rtc.Man [Remove-CsVoiceRoutingPolicy](Remove-CsVoiceRoutingPolicy.md) [Set-CsVoiceRoutingPolicy](Set-CsVoiceRoutingPolicy.md) - diff --git a/skype/skype-ps/skype/New-CsVoiceTestConfiguration.md b/skype/skype-ps/skype/New-CsVoiceTestConfiguration.md index 4ee948ada8..bff35169f4 100644 --- a/skype/skype-ps/skype/New-CsVoiceTestConfiguration.md +++ b/skype/skype-ps/skype/New-CsVoiceTestConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvoicetestconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csvoicetestconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVoiceTestConfiguration schema: 2.0.0 @@ -344,4 +344,3 @@ This cmdlet creates an object of type Microsoft.Rtc.Management.WritableConfig.Po [Get-CsDialPlan](Get-CsDialPlan.md) [Get-CsVoicePolicy](Get-CsVoicePolicy.md) - diff --git a/skype/skype-ps/skype/New-CsVoicemailReroutingConfiguration.md b/skype/skype-ps/skype/New-CsVoicemailReroutingConfiguration.md index 081e466dcc..58bcb680ea 100644 --- a/skype/skype-ps/skype/New-CsVoicemailReroutingConfiguration.md +++ b/skype/skype-ps/skype/New-CsVoicemailReroutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvoicemailreroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-csvoicemailreroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsVoicemailReroutingConfiguration schema: 2.0.0 @@ -224,4 +224,3 @@ Creates an object of type Microsoft.Rtc.Management.WritableConfig.Settings.ExumR [Set-CsVoicemailReroutingConfiguration](Set-CsVoicemailReroutingConfiguration.md) [Get-CsVoicemailReroutingConfiguration](Get-CsVoicemailReroutingConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsWatcherNodeConfiguration.md b/skype/skype-ps/skype/New-CsWatcherNodeConfiguration.md index 14f1d564ca..7127cbf0ec 100644 --- a/skype/skype-ps/skype/New-CsWatcherNodeConfiguration.md +++ b/skype/skype-ps/skype/New-CsWatcherNodeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cswatchernodeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cswatchernodeconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsWatcherNodeConfiguration schema: 2.0.0 @@ -361,4 +361,3 @@ The `New-CsWatcherNodeConfiguration` cmdlet creates new instances of the Microso ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsWebLink.md b/skype/skype-ps/skype/New-CsWebLink.md index 9db20e8d25..56cf68d55b 100644 --- a/skype/skype-ps/skype/New-CsWebLink.md +++ b/skype/skype-ps/skype/New-CsWebLink.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csweblink -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csweblink +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsWebLink schema: 2.0.0 manager: rogupta @@ -47,7 +47,7 @@ When you install Skype for Business Server a global collection of settings will Managing Autodiscover configuration settings typically means adding Autodiscover URLs. These URLs must be created using the `New-CsWebLink` cmdlet, with the resulting URL stored in a variable and then added to a collection of Autodiscover configuration settings. -Autodiscover URLs are based on the SIP domains used in your organization; administrators will typically create one URL for use by users outside the organization's firewall (for example, https://LyncDiscover.litwareinc.com) and a second URL (for example, https://LyncDiscoverInternal.litwareinc.com) for use by users inside the firewall. +Autodiscover URLs are based on the SIP domains used in your organization; administrators will typically create one URL for use by users outside the organization's firewall (for example, `https://LyncDiscover.litwareinc.com`) and a second URL (for example, `https://LyncDiscoverInternal.litwareinc.com``) for use by users inside the firewall. ## EXAMPLES @@ -59,7 +59,7 @@ $Link1 = New-CsWebLink -Token "Fabrikam" -Href "https://LyncDiscover.fabrikam.co Set-CsAutoDiscoverConfiguration -Identity "site:Redmond" -WebLinks @{Add=$Link1} ``` -The commands shown in Example 1 add a new Autodiscover URL (https://LyncDiscover.fabrikam.com) to the Autodiscover configuration settings assigned to the Redmond site. +The commands shown in Example 1 add a new Autodiscover URL (`https://LyncDiscover.fabrikam.com`) to the Autodiscover configuration settings assigned to the Redmond site. To do this, the first command in the example uses the `New-CsWebLink` cmdlet to create a new Autodiscover URL; that URL is stored in a variable named $Link1. After that, the `Set-CsAutoDiscoverConfiguration` cmdlet is used to add the new URL to any URLs already assigned to these settings. This is done by using the WebLinks parameter and the parameter value @{Add=$Link1}. @@ -74,7 +74,7 @@ $Link2 = New-CsWebLink -Token "Fabrikam" -Href "https://LyncDiscoverInternal.fab Set-CsAutoDiscoverConfiguration -Identity "site:Redmond" -WebLinks @{Add=$Link1,$Link2} ``` -The commands in Example 2 assign a pair of Autodiscover URLs (https://LyncDiscover.fabrikam.com and https://LyncDiscoverInternal.fabrikam.com) to the Autodiscover configuration settings assigned to the Redmond site.. +The commands in Example 2 assign a pair of Autodiscover URLs (`https://LyncDiscover.fabrikam.com` and `https://LyncDiscoverInternal.fabrikam.com`) to the Autodiscover configuration settings assigned to the Redmond site.. In order to carry out this task, the first two commands use the `New-CsWebLink` cmdlet to create the two Autodiscover URLs; the newly-created URLs are then stored in variables named $Link1 and $Link2. After the two URLs are created, the third command uses the `Set-CsAutoDiscoverConfiguration` cmdlet to assign the two URLs to the Redmond site. To do this, the WebLinks parameter is included along with the parameter value @{Add=$Link1,$Link2}. @@ -137,4 +137,3 @@ Creates new instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.W ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/New-CsWebOrigin.md b/skype/skype-ps/skype/New-CsWebOrigin.md index 9ba77fedc5..f4c97376ec 100644 --- a/skype/skype-ps/skype/New-CsWebOrigin.md +++ b/skype/skype-ps/skype/New-CsWebOrigin.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csweborigin -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/new-csweborigin +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsWebOrigin schema: 2.0.0 manager: rogupta @@ -107,4 +107,3 @@ The `New-CsWebOrigin` cmdlet creates new instances of the Microsoft.Rtc.Manageme [New-CsWebServiceConfiguration](New-CsWebServiceConfiguration.md) [Set-CsWebServiceConfiguration](Set-CsWebServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsWebServiceConfiguration.md b/skype/skype-ps/skype/New-CsWebServiceConfiguration.md index b08e888d2d..8b4f16252e 100644 --- a/skype/skype-ps/skype/New-CsWebServiceConfiguration.md +++ b/skype/skype-ps/skype/New-CsWebServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cswebserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/new-cswebserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsWebServiceConfiguration schema: 2.0.0 @@ -32,6 +32,7 @@ New-CsWebServiceConfiguration [-Identity] <XdsIdentity> [-AllowAnonymousAccessTo [-ShowAlternateJoinOptionsExpanded <Boolean>] [-UseWsFedPassiveAuth <Boolean>] [-WsFedPassiveMetadataUri <String>] [-CrossDomainAuthorizationList <PSListModifier>] [-EnableMediaBasicAuth <Boolean>] [-EnableStatisticsInResponse <Boolean>] [-HstsMaxAgeInSeconds <Int64>] + [-PendingGetWaitTimeOutInMinutes <Int64>] [-PendingGetWaitSupportingApps <String>] [-MobilePreferredAuthType <MobilePreferredAuthType>] [-UseDomainAuthInLWA <Boolean>] [-UseWebClientLegacyUI <Boolean>] [<CommonParameters>] ``` @@ -52,7 +53,7 @@ Likewise, your command will fail if you try to create a new collection at, for i ## EXAMPLES -### -------------------------- Example 1 ------------------------ +### Example 1 ``` New-CsWebServiceConfiguration -Identity site:Redmond -EnableGroupExpansion $False -UseCertificateAuth $True ``` @@ -65,7 +66,7 @@ Note that this command will fail if a collection of Web Services configuration s That's because sites are limited to a single collection of Web Services configuration settings. -### -------------------------- Example 2 ------------------------ +### Example 2 ``` $x = New-CsWebServiceConfiguration -Identity site:Redmond -InMemory @@ -87,7 +88,7 @@ If you do not call the `Set-CsWebServiceConfiguration` cmdlet, no new settings w Instead, your virtual Web Services configuration settings will disappear as soon as you end your Windows PowerShell session or delete the variable $x. -### -------------------------- Example 3 -------------------------- +### Example 3 ``` $x = New-CsWebOrigin -Url "http://fabrikam.com/" @@ -102,7 +103,7 @@ The second command in the example uses the `New-CsWebServiceConfiguration` cmdle The syntax `- CrossDomainAuthorizationList $x` adds http://fabrikam.com to the collection of domains authorized for cross-domain scripting. -### -------------------------- Example 4 -------------------------- +### Example 4 ``` $x = New-CsWebOrigin -Url "http://fabrikam.com/" @@ -733,6 +734,46 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PendingGetWaitTimeOutInMinutes +Specifies the time in minutes to send an event at a particular interval to Keep Alive EventChannel. +The value can be specified in between 5 to 15 minutes (both inclusive). +The default value is 15 minutes. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PendingGetWaitSupportingApps +Specifies a semicolon-separated list of applications for which PendingGetWaitTimeOutInMinutes need to be set. +Supported applications are Android, iPhone, iPad, Macintosh, Windows. +To support all applications you can give All as input. +For example: +- To support Android and Macintosh - Android;Macintosh; +- To support all devices - All; +The default value is None. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MobilePreferredAuthType Specifies the preferred authentication type to be used by mobile applications. If an unsupported method is specified, the web ticket service will not start and an event will be logged by the Skype for Business Server. @@ -828,4 +869,3 @@ The `New-CsWebServiceConfiguration` cmdlet creates new instances of the Microsof [Remove-CsWebServiceConfiguration](Remove-CsWebServiceConfiguration.md) [Set-CsWebServiceConfiguration](Set-CsWebServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsWebTrustedCACertificate.md b/skype/skype-ps/skype/New-CsWebTrustedCACertificate.md index 5dead0cb26..1ae3b83bb3 100644 --- a/skype/skype-ps/skype/New-CsWebTrustedCACertificate.md +++ b/skype/skype-ps/skype/New-CsWebTrustedCACertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-cswebtrustedcacertificate +online version: https://learn.microsoft.com/powershell/module/skype/new-cswebtrustedcacertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsWebTrustedCACertificate schema: 2.0.0 @@ -119,4 +119,3 @@ The `New-CsWebTrustedCACertificate` cmdlet creates new instances of the Microsof [New-CsWebServiceConfiguration](New-CsWebServiceConfiguration.md) [Set-CsWebServiceConfiguration](Set-CsWebServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/New-CsXmppAllowedPartner.md b/skype/skype-ps/skype/New-CsXmppAllowedPartner.md index 8d1eff00a8..3143cc1192 100644 --- a/skype/skype-ps/skype/New-CsXmppAllowedPartner.md +++ b/skype/skype-ps/skype/New-CsXmppAllowedPartner.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csxmppallowedpartner -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/new-csxmppallowedpartner +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: New-CsXmppAllowedPartner schema: 2.0.0 manager: rogupta @@ -392,4 +392,3 @@ The `New-CsXmppAllowedPartner` cmdlet creates new instances of the Microsoft.Rtc [Remove-CsXmppAllowedPartner](Remove-CsXmppAllowedPartner.md) [Set-CsXmppAllowedPartner](Set-CsXmppAllowedPartner.md) - diff --git a/skype/skype-ps/skype/Publish-CsLisConfiguration.md b/skype/skype-ps/skype/Publish-CsLisConfiguration.md index 56718586f7..a3a95573fd 100644 --- a/skype/skype-ps/skype/Publish-CsLisConfiguration.md +++ b/skype/skype-ps/skype/Publish-CsLisConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/publish-cslisconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/publish-cslisconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Publish-CsLisConfiguration schema: 2.0.0 @@ -117,4 +117,3 @@ This cmdlet does not return a value. [Export-CsLisConfiguration](Export-CsLisConfiguration.md) [Test-CsLisConfiguration](Test-CsLisConfiguration.md) - diff --git a/skype/skype-ps/skype/Publish-CsTopology.md b/skype/skype-ps/skype/Publish-CsTopology.md index 1aa7b9aee1..a947773c93 100644 --- a/skype/skype-ps/skype/Publish-CsTopology.md +++ b/skype/skype-ps/skype/Publish-CsTopology.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/publish-cstopology +online version: https://learn.microsoft.com/powershell/module/skype/publish-cstopology applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Publish-CsTopology schema: 2.0.0 @@ -268,4 +268,3 @@ Instead, the `Publish-CsTopology` cmdlet publishes instances of the Microsoft.Rt [New-CsSimpleUrlConfiguration](New-CsSimpleUrlConfiguration.md) [Test-CsTopology](Test-CsTopology.md) - diff --git a/skype/skype-ps/skype/Register-CsHybridPSTNAppliance.md b/skype/skype-ps/skype/Register-CsHybridPSTNAppliance.md index 2cd8ef7d82..9dcace377f 100644 --- a/skype/skype-ps/skype/Register-CsHybridPSTNAppliance.md +++ b/skype/skype-ps/skype/Register-CsHybridPSTNAppliance.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/register-cshybridpstnappliance +online version: https://learn.microsoft.com/powershell/module/skype/register-cshybridpstnappliance applicable: Skype for Business Online title: Register-CsHybridPSTNAppliance schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Register-CsHybridPSTNAppliance @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the `Register-CsHybridPSTNAppliance` cmdlet to create a new Skype for Business Cloud Connector Edition appliance. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` @@ -201,4 +203,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Register-CsOnlineDialInConferencingServiceNumber.md b/skype/skype-ps/skype/Register-CsOnlineDialInConferencingServiceNumber.md deleted file mode 100644 index 33c486abb5..0000000000 --- a/skype/skype-ps/skype/Register-CsOnlineDialInConferencingServiceNumber.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/register-csonlinedialinconferencingservicenumber -applicable: Skype for Business Online -title: Register-CsOnlineDialInConferencingServiceNumber -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Register-CsOnlineDialInConferencingServiceNumber - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -### UniqueNumberParams -``` -Register-CsOnlineDialInConferencingServiceNumber [-Identity] <String> [-BridgeId <Guid>] - [-BridgeName <String>] [-Tenant <Guid>] [-TenantDomain <String>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -### InstanceParams -``` -Register-CsOnlineDialInConferencingServiceNumber [-Instance] <ConferencingServiceNumber> - [-BridgeId <Guid>] [-BridgeName <String>] [-Tenant <Guid>] [-TenantDomain <String>] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -Identity -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -PARAMVALUE: ConferencingServiceNumber - -```yaml -Type: ConferencingServiceNumber -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BridgeId -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BridgeName -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -PARAMVALUE: Fqdn - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantDomain -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsAVEdgeConfiguration.md b/skype/skype-ps/skype/Remove-CsAVEdgeConfiguration.md index bf9f54b89d..37d8b834d3 100644 --- a/skype/skype-ps/skype/Remove-CsAVEdgeConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsAVEdgeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csavedgeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csavedgeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAVEdgeConfiguration schema: 2.0.0 @@ -165,4 +165,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsAVEdgeConfiguration](New-CsAVEdgeConfiguration.md) [Set-CsAVEdgeConfiguration](Set-CsAVEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsAdditionalInternalDomain.md b/skype/skype-ps/skype/Remove-CsAdditionalInternalDomain.md index 6207f4e8de..9840f5844b 100644 --- a/skype/skype-ps/skype/Remove-CsAdditionalInternalDomain.md +++ b/skype/skype-ps/skype/Remove-CsAdditionalInternalDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csadditionalinternaldomain +online version: https://learn.microsoft.com/powershell/module/skype/remove-csadditionalinternaldomain applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAdditionalInternalDomain schema: 2.0.0 @@ -120,6 +120,6 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[New-CsAdditionalInternalDomain](https://docs.microsoft.com/powershell/module/skype/new-csadditionalinternaldomain?view=skype-ps) +[New-CsAdditionalInternalDomain](https://learn.microsoft.com/powershell/module/skype/new-csadditionalinternaldomain?view=skype-ps) -[Get-CsAdditionalInternalDomain](https://docs.microsoft.com/powershell/module/skype/get-csadditionalinternaldomain?view=skype-ps) +[Get-CsAdditionalInternalDomain](https://learn.microsoft.com/powershell/module/skype/get-csadditionalinternaldomain?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsAddressBookConfiguration.md b/skype/skype-ps/skype/Remove-CsAddressBookConfiguration.md index 5853a00ea6..6462ca6564 100644 --- a/skype/skype-ps/skype/Remove-CsAddressBookConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsAddressBookConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csaddressbookconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csaddressbookconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAddressBookConfiguration schema: 2.0.0 @@ -167,4 +167,3 @@ Instead, the cmdlet removes instances of the Microsoft.Rtc.Management.WritableCo [New-CsAddressBookConfiguration](New-CsAddressBookConfiguration.md) [Set-CsAddressBookConfiguration](Set-CsAddressBookConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsAddressBookNormalizationConfiguration.md b/skype/skype-ps/skype/Remove-CsAddressBookNormalizationConfiguration.md index d9e4638be9..5aa40f5cda 100644 --- a/skype/skype-ps/skype/Remove-CsAddressBookNormalizationConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsAddressBookNormalizationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csaddressbooknormalizationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csaddressbooknormalizationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAddressBookNormalizationConfiguration schema: 2.0.0 @@ -152,4 +152,3 @@ Instead, the `Remove-CsAddressBookNormalizationConfiguration` cmdlet deletes exi [Set-CsAddressBookNormalizationConfiguration](Set-CsAddressBookNormalizationConfiguration.md) [Import-CsCompanyPhoneNormalizationRules](Import-CsCompanyPhoneNormalizationRules.md) - diff --git a/skype/skype-ps/skype/Remove-CsAddressBookNormalizationRule.md b/skype/skype-ps/skype/Remove-CsAddressBookNormalizationRule.md index 0a24c7f6de..b1f7133ca9 100644 --- a/skype/skype-ps/skype/Remove-CsAddressBookNormalizationRule.md +++ b/skype/skype-ps/skype/Remove-CsAddressBookNormalizationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csaddressbooknormalizationrule +online version: https://learn.microsoft.com/powershell/module/skype/remove-csaddressbooknormalizationrule applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAddressBookNormalizationRule schema: 2.0.0 @@ -152,4 +152,3 @@ Instead, the `Remove-CsAddressBookNormalizationRule` cmdlet deletes existing ins [New-CsAddressBookNormalizationRule](New-CsAddressBookNormalizationRule.md) [Set-CsAddressBookNormalizationRule](Set-CsAddressBookNormalizationRule.md) - diff --git a/skype/skype-ps/skype/Remove-CsAdminRole.md b/skype/skype-ps/skype/Remove-CsAdminRole.md index 14f44ad7c8..0902573360 100644 --- a/skype/skype-ps/skype/Remove-CsAdminRole.md +++ b/skype/skype-ps/skype/Remove-CsAdminRole.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csadminrole +online version: https://learn.microsoft.com/powershell/module/skype/remove-csadminrole applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAdminRole schema: 2.0.0 @@ -255,4 +255,3 @@ The `Remove-CsAdminRole` cmdlet deletes existing instances of the Microsoft.Rtc. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsAllowedDomain.md b/skype/skype-ps/skype/Remove-CsAllowedDomain.md index 36a0d15e75..369b896c1d 100644 --- a/skype/skype-ps/skype/Remove-CsAllowedDomain.md +++ b/skype/skype-ps/skype/Remove-CsAllowedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csalloweddomain +online version: https://learn.microsoft.com/powershell/module/skype/remove-csalloweddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAllowedDomain schema: 2.0.0 @@ -176,4 +176,3 @@ Deletes instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.A [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) [Set-CsAllowedDomain](Set-CsAllowedDomain.md) - diff --git a/skype/skype-ps/skype/Remove-CsAnalogDevice.md b/skype/skype-ps/skype/Remove-CsAnalogDevice.md index a6a43e23ba..2934cae81d 100644 --- a/skype/skype-ps/skype/Remove-CsAnalogDevice.md +++ b/skype/skype-ps/skype/Remove-CsAnalogDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csanalogdevice +online version: https://learn.microsoft.com/powershell/module/skype/remove-csanalogdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAnalogDevice schema: 2.0.0 @@ -159,4 +159,3 @@ The `Remove-CsAnalogDevice` cmdlet deletes existing instances of the Microsoft.R [New-CsAnalogDevice](New-CsAnalogDevice.md) [Set-CsAnalogDevice](Set-CsAnalogDevice.md) - diff --git a/skype/skype-ps/skype/Remove-CsAnnouncement.md b/skype/skype-ps/skype/Remove-CsAnnouncement.md index df574aad85..b51ed922b3 100644 --- a/skype/skype-ps/skype/Remove-CsAnnouncement.md +++ b/skype/skype-ps/skype/Remove-CsAnnouncement.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csannouncement +online version: https://learn.microsoft.com/powershell/module/skype/remove-csannouncement applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAnnouncement schema: 2.0.0 @@ -149,4 +149,3 @@ Deletes existing instances of the Microsoft.Rtc.Management.WritableConfig.Settin [Set-CsAnnouncement](Set-CsAnnouncement.md) [Get-CsAnnouncement](Get-CsAnnouncement.md) - diff --git a/skype/skype-ps/skype/Remove-CsArchivingConfiguration.md b/skype/skype-ps/skype/Remove-CsArchivingConfiguration.md index c5ea7d6357..cd4dcbd64d 100644 --- a/skype/skype-ps/skype/Remove-CsArchivingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsArchivingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csarchivingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csarchivingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsArchivingConfiguration schema: 2.0.0 @@ -182,4 +182,3 @@ Instead, the cmdlet removes instances of the Microsoft.Rtc.Management.WritableCo [Set-CsArchivingConfiguration](Set-CsArchivingConfiguration.md) [Set-CsArchivingServer](Set-CsArchivingServer.md) - diff --git a/skype/skype-ps/skype/Remove-CsArchivingPolicy.md b/skype/skype-ps/skype/Remove-CsArchivingPolicy.md index 43c7d0f5f5..aad1e6bdd9 100644 --- a/skype/skype-ps/skype/Remove-CsArchivingPolicy.md +++ b/skype/skype-ps/skype/Remove-CsArchivingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csarchivingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csarchivingpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsArchivingPolicy schema: 2.0.0 @@ -214,4 +214,3 @@ Instead, the cmdlet removes instances of the Microsoft.Rtc.Management.WritableCo [New-CsArchivingPolicy](New-CsArchivingPolicy.md) [Set-CsArchivingPolicy](Set-CsArchivingPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsAutoAttendant.md b/skype/skype-ps/skype/Remove-CsAutoAttendant.md deleted file mode 100644 index 03e065ae0b..0000000000 --- a/skype/skype-ps/skype/Remove-CsAutoAttendant.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csautoattendant -applicable: Skype for Business Online -title: Remove-CsAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsAutoAttendant - -## SYNOPSIS -Use the Remove-CsAutoAttendant cmdlet to delete an Auto Attendant (AA). - -## SYNTAX - -``` -Remove-CsAutoAttendant -Identity <String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Remove-CsAutoAttendant cmdlet deletes an AA that is specified by the Identity parameter. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Remove-CsAutoAttendant -Identity "fa9081d6-b4f3-5c96-baec-0b00077709e5" -``` - -This example deletes the AA that has a identity of fa9081d6-b4f3-5c96-baec-0b00077709e5. - - -## PARAMETERS - -### -Identity -The identity for the AA to be removed. - - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### String -The Remove-CsAutoAttendant cmdlet accepts a string as the Identity parameter. - - -## OUTPUTS - -### None - - -## NOTES - -## RELATED LINKS - -[New-CsAutoAttendant](New-CsAutoAttendant.md) - -[Get-CsAutoAttendant](Get-CsAutoAttendant.md) - -[Set-CsAutoAttendant](Set-CsAutoAttendant.md) diff --git a/skype/skype-ps/skype/Remove-CsAutodiscoverConfiguration.md b/skype/skype-ps/skype/Remove-CsAutodiscoverConfiguration.md index 579e937cab..28d818613b 100644 --- a/skype/skype-ps/skype/Remove-CsAutodiscoverConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsAutodiscoverConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csautodiscoverconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csautodiscoverconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsAutodiscoverConfiguration schema: 2.0.0 manager: rogupta @@ -161,4 +161,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WriteableC ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsBackupServiceConfiguration.md b/skype/skype-ps/skype/Remove-CsBackupServiceConfiguration.md index 3789a1234c..c6a0bc6cfc 100644 --- a/skype/skype-ps/skype/Remove-CsBackupServiceConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsBackupServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csbackupserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csbackupserviceconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsBackupServiceConfiguration schema: 2.0.0 @@ -135,4 +135,3 @@ Instead, the `Remove-CsBackupServiceConfiguration` cmdlet deletes instances of t [Get-CsBackupServiceConfiguration](Get-CsBackupServiceConfiguration.md) [Set-CsBackupServiceConfiguration](Set-CsBackupServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsBandwidthPolicyServiceConfiguration.md b/skype/skype-ps/skype/Remove-CsBandwidthPolicyServiceConfiguration.md index fba0244e50..41f3e9cac6 100644 --- a/skype/skype-ps/skype/Remove-CsBandwidthPolicyServiceConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsBandwidthPolicyServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csbandwidthpolicyserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csbandwidthpolicyserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsBandwidthPolicyServiceConfiguration schema: 2.0.0 @@ -146,4 +146,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ba [Set-CsBandwidthPolicyServiceConfiguration](Set-CsBandwidthPolicyServiceConfiguration.md) [Get-CsBandwidthPolicyServiceConfiguration](Get-CsBandwidthPolicyServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsBlockedDomain.md b/skype/skype-ps/skype/Remove-CsBlockedDomain.md index ca81a96432..29b6a48035 100644 --- a/skype/skype-ps/skype/Remove-CsBlockedDomain.md +++ b/skype/skype-ps/skype/Remove-CsBlockedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csblockeddomain +online version: https://learn.microsoft.com/powershell/module/skype/remove-csblockeddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsBlockedDomain schema: 2.0.0 @@ -167,4 +167,3 @@ Deletes instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.B [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) [Set-CsBlockedDomain](Set-CsBlockedDomain.md) - diff --git a/skype/skype-ps/skype/Remove-CsBusyOptions.md b/skype/skype-ps/skype/Remove-CsBusyOptions.md index 01aa55a8fb..3a462337d7 100644 --- a/skype/skype-ps/skype/Remove-CsBusyOptions.md +++ b/skype/skype-ps/skype/Remove-CsBusyOptions.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csbusyoptions +online version: https://learn.microsoft.com/powershell/module/skype/remove-csbusyoptions applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsBusyOptions schema: 2.0.0 @@ -118,6 +118,6 @@ This cmdlet does not return any objects. ## NOTES ## RELATED LINKS -[Get-CsBusyOptions](https://docs.microsoft.com/powershell/module/skype/get-csbusyoptions?view=skype-ps) +[Get-CsBusyOptions](https://learn.microsoft.com/powershell/module/skype/get-csbusyoptions?view=skype-ps) -[Set-CsBusyOptions](https://docs.microsoft.com/powershell/module/skype/set-csbusyoptions?view=skype-ps) +[Set-CsBusyOptions](https://learn.microsoft.com/powershell/module/skype/set-csbusyoptions?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsCallParkOrbit.md b/skype/skype-ps/skype/Remove-CsCallParkOrbit.md index d674478bb5..c2fc47f998 100644 --- a/skype/skype-ps/skype/Remove-CsCallParkOrbit.md +++ b/skype/skype-ps/skype/Remove-CsCallParkOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscallparkorbit +online version: https://learn.microsoft.com/powershell/module/skype/remove-cscallparkorbit applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsCallParkOrbit schema: 2.0.0 @@ -152,4 +152,3 @@ It removes an object of type Microsoft.Rtc.Management.Voice.Helpers.DisplayCallP [Set-CsCallParkOrbit](Set-CsCallParkOrbit.md) [Get-CsCallParkOrbit](Get-CsCallParkOrbit.md) - diff --git a/skype/skype-ps/skype/Remove-CsCallViaWorkPolicy.md b/skype/skype-ps/skype/Remove-CsCallViaWorkPolicy.md index 9de3cc0cfa..80f2007953 100644 --- a/skype/skype-ps/skype/Remove-CsCallViaWorkPolicy.md +++ b/skype/skype-ps/skype/Remove-CsCallViaWorkPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscallviaworkpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-cscallviaworkpolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsCallViaWorkPolicy schema: 2.0.0 @@ -149,4 +149,3 @@ None. [Grant-CsCallViaWorkPolicy](Grant-CsCallViaWorkPolicy.md) [Get-CsCallViaWorkPolicy](Get-CsCallViaWorkPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsCallingLineIdentity.md b/skype/skype-ps/skype/Remove-CsCallingLineIdentity.md deleted file mode 100644 index 365429522b..0000000000 --- a/skype/skype-ps/skype/Remove-CsCallingLineIdentity.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscallinglineidentity -applicable: Skype for Business Online -title: Remove-CsCallingLineIdentity -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsCallingLineIdentity - -## SYNOPSIS -Use the `Remove-CsCallingLineIdentity` cmdlet to remove a Caller ID policy from your organization. - -## SYNTAX - -``` -Remove-CsCallingLineIdentity [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -You can either change or block the Caller ID (also called a Calling Line ID) for a user. By default, the Skype for Business Online user's phone number can be seen when that user makes a call to a PSTN phone, or when a call comes in. You can modify a Caller ID policy to provide an alternate displayed number, or to block any number from being displayed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Remove-CsCallingLineIdentity -Identity Anonymous -``` - -This example removes a Caller ID policy. - - -## PARAMETERS - -### -Identity -The Identity parameter identifies the Caller ID policy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsCdrConfiguration.md b/skype/skype-ps/skype/Remove-CsCdrConfiguration.md index dc5548065d..fd052dd951 100644 --- a/skype/skype-ps/skype/Remove-CsCdrConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsCdrConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscdrconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cscdrconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsCdrConfiguration schema: 2.0.0 @@ -170,4 +170,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsCdrConfiguration](New-CsCdrConfiguration.md) [Set-CsCdrConfiguration](Set-CsCdrConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsCertificate.md b/skype/skype-ps/skype/Remove-CsCertificate.md index 94317013b4..f66a9b06f6 100644 --- a/skype/skype-ps/skype/Remove-CsCertificate.md +++ b/skype/skype-ps/skype/Remove-CsCertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscertificate +online version: https://learn.microsoft.com/powershell/module/skype/remove-cscertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsCertificate schema: 2.0.0 diff --git a/skype/skype-ps/skype/Remove-CsClientPolicy.md b/skype/skype-ps/skype/Remove-CsClientPolicy.md index 42c70999a6..dad1f49490 100644 --- a/skype/skype-ps/skype/Remove-CsClientPolicy.md +++ b/skype/skype-ps/skype/Remove-CsClientPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclientpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclientpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClientPolicy schema: 2.0.0 manager: bulenteg @@ -194,4 +194,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsClientPolicy](New-CsClientPolicy.md) [Set-CsClientPolicy](Set-CsClientPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsClientVersionConfiguration.md b/skype/skype-ps/skype/Remove-CsClientVersionConfiguration.md index 2e35e6db34..fee4af8bf2 100644 --- a/skype/skype-ps/skype/Remove-CsClientVersionConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsClientVersionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclientversionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclientversionconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClientVersionConfiguration schema: 2.0.0 @@ -167,4 +167,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsClientVersionConfiguration](New-CsClientVersionConfiguration.md) [Set-CsClientVersionConfiguration](Set-CsClientVersionConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsClientVersionPolicy.md b/skype/skype-ps/skype/Remove-CsClientVersionPolicy.md index 160ae4b397..73274296e7 100644 --- a/skype/skype-ps/skype/Remove-CsClientVersionPolicy.md +++ b/skype/skype-ps/skype/Remove-CsClientVersionPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclientversionpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclientversionpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClientVersionPolicy schema: 2.0.0 @@ -196,4 +196,3 @@ The `Remove-CsClientVersionPolicy` cmdlet deletes existing instances of the Micr [New-CsClientVersionPolicy](New-CsClientVersionPolicy.md) [Set-CsClientVersionPolicy](Set-CsClientVersionPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsClientVersionPolicyRule.md b/skype/skype-ps/skype/Remove-CsClientVersionPolicyRule.md index 9e3dc51636..9ab5db8977 100644 --- a/skype/skype-ps/skype/Remove-CsClientVersionPolicyRule.md +++ b/skype/skype-ps/skype/Remove-CsClientVersionPolicyRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclientversionpolicyrule +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclientversionpolicyrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClientVersionPolicyRule schema: 2.0.0 @@ -214,4 +214,3 @@ Instead, the `Remove-CsClientVersionPolicyRule` cmdlet deletes instances of the [New-CsClientVersionPolicyRule](New-CsClientVersionPolicyRule.md) [Set-CsClientVersionPolicyRule](Set-CsClientVersionPolicyRule.md) - diff --git a/skype/skype-ps/skype/Remove-CsClsConfiguration.md b/skype/skype-ps/skype/Remove-CsClsConfiguration.md index 9311fa7837..2e6f11933a 100644 --- a/skype/skype-ps/skype/Remove-CsClsConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsClsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClsConfiguration schema: 2.0.0 @@ -177,4 +177,3 @@ Instead, the `Remove-CsClsConfiguration` cmdlet deletes existing instances of th [New-CsClsConfiguration](New-CsClsConfiguration.md) [Set-CsClsConfiguration](Set-CsClsConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsClsRegion.md b/skype/skype-ps/skype/Remove-CsClsRegion.md index 6fea4cc0ff..d453a56054 100644 --- a/skype/skype-ps/skype/Remove-CsClsRegion.md +++ b/skype/skype-ps/skype/Remove-CsClsRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclsregion +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclsregion applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClsRegion schema: 2.0.0 @@ -161,4 +161,3 @@ Instead, the `Remove-CsClsRegion` cmdlet deletes existing instances of the Micro [New-CsClsRegion](New-CsClsRegion.md) [Set-CsClsRegion](Set-CsClsRegion.md) - diff --git a/skype/skype-ps/skype/Remove-CsClsScenario.md b/skype/skype-ps/skype/Remove-CsClsScenario.md index d35c83f045..c1cf3ade17 100644 --- a/skype/skype-ps/skype/Remove-CsClsScenario.md +++ b/skype/skype-ps/skype/Remove-CsClsScenario.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclsscenario +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclsscenario applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClsScenario schema: 2.0.0 @@ -152,4 +152,3 @@ Instead, the `Remove-CsClsScenario` cmdlet deletes existing instances of the Mic ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsClsSecurityGroup.md b/skype/skype-ps/skype/Remove-CsClsSecurityGroup.md index 1c93177b0a..823296de5b 100644 --- a/skype/skype-ps/skype/Remove-CsClsSecurityGroup.md +++ b/skype/skype-ps/skype/Remove-CsClsSecurityGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csclssecuritygroup +online version: https://learn.microsoft.com/powershell/module/skype/remove-csclssecuritygroup applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsClsSecurityGroup schema: 2.0.0 @@ -161,4 +161,3 @@ Instead, the `Remove-CsClsSecurityGroup` cmdlet deletes existing instances of th [New-CsClsSecurityGroup](New-CsClsSecurityGroup.md) [Set-CsClsSecurityGroup](Set-CsClsSecurityGroup.md) - diff --git a/skype/skype-ps/skype/Remove-CsCommonAreaPhone.md b/skype/skype-ps/skype/Remove-CsCommonAreaPhone.md index 29800c17dc..2a890219dc 100644 --- a/skype/skype-ps/skype/Remove-CsCommonAreaPhone.md +++ b/skype/skype-ps/skype/Remove-CsCommonAreaPhone.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscommonareaphone +online version: https://learn.microsoft.com/powershell/module/skype/remove-cscommonareaphone applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsCommonAreaPhone schema: 2.0.0 @@ -156,4 +156,3 @@ The `Remove-CsCommonAreaPhone` cmdlet deletes existing instances of the Microsof [New-CsCommonAreaPhone](New-CsCommonAreaPhone.md) [Set-CsCommonAreaPhone](Set-CsCommonAreaPhone.md) - diff --git a/skype/skype-ps/skype/Remove-CsConferenceDirectory.md b/skype/skype-ps/skype/Remove-CsConferenceDirectory.md index 1a75ffa405..407a22cf8c 100644 --- a/skype/skype-ps/skype/Remove-CsConferenceDirectory.md +++ b/skype/skype-ps/skype/Remove-CsConferenceDirectory.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csconferencedirectory +online version: https://learn.microsoft.com/powershell/module/skype/remove-csconferencedirectory applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsConferenceDirectory schema: 2.0.0 @@ -151,4 +151,3 @@ Instead, the `Removes-CsConferenceDirectory` cmdlet deletes instances of the Mic [Move-CsConferenceDirectory](Move-CsConferenceDirectory.md) [New-CsConferenceDirectory](New-CsConferenceDirectory.md) - diff --git a/skype/skype-ps/skype/Remove-CsConferenceDisclaimer.md b/skype/skype-ps/skype/Remove-CsConferenceDisclaimer.md index c6fcab1403..efd4048142 100644 --- a/skype/skype-ps/skype/Remove-CsConferenceDisclaimer.md +++ b/skype/skype-ps/skype/Remove-CsConferenceDisclaimer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csconferencedisclaimer +online version: https://learn.microsoft.com/powershell/module/skype/remove-csconferencedisclaimer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsConferenceDisclaimer schema: 2.0.0 @@ -135,4 +135,3 @@ Instead, the `Remove-CsConferenceDisclaimer` cmdlet resets existing instances of [Get-CsConferenceDisclaimer](Get-CsConferenceDisclaimer.md) [Set-CsConferenceDisclaimer](Set-CsConferenceDisclaimer.md) - diff --git a/skype/skype-ps/skype/Remove-CsConferencingConfiguration.md b/skype/skype-ps/skype/Remove-CsConferencingConfiguration.md index 92afeb9850..4164a16021 100644 --- a/skype/skype-ps/skype/Remove-CsConferencingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsConferencingConfiguration schema: 2.0.0 @@ -177,4 +177,3 @@ Instead, the `Remove-CsConferencingConfiguration` cmdlet deletes existing instan [New-CsConferencingConfiguration](New-CsConferencingConfiguration.md) [Set-CsConferencingConfiguration](Set-CsConferencingConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsConferencingPolicy.md b/skype/skype-ps/skype/Remove-CsConferencingPolicy.md index b30958e001..cbc2051711 100644 --- a/skype/skype-ps/skype/Remove-CsConferencingPolicy.md +++ b/skype/skype-ps/skype/Remove-CsConferencingPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csconferencingpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csconferencingpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsConferencingPolicy schema: 2.0.0 manager: bulenteg @@ -205,4 +205,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsConferencingPolicy](New-CsConferencingPolicy.md) [Set-CsConferencingPolicy](Set-CsConferencingPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsConfigurationStoreLocation.md b/skype/skype-ps/skype/Remove-CsConfigurationStoreLocation.md index 2ed3f24c91..654ff393a0 100644 --- a/skype/skype-ps/skype/Remove-CsConfigurationStoreLocation.md +++ b/skype/skype-ps/skype/Remove-CsConfigurationStoreLocation.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csconfigurationstorelocation +online version: https://learn.microsoft.com/powershell/module/skype/remove-csconfigurationstorelocation applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsConfigurationStoreLocation schema: 2.0.0 @@ -165,4 +165,3 @@ The `Remove-CsConfigurationStoreLocation` cmdlet does not return any objects or [Get-CsConfigurationStoreLocation](Get-CsConfigurationStoreLocation.md) [Set-CsConfigurationStoreLocation](Set-CsConfigurationStoreLocation.md) - diff --git a/skype/skype-ps/skype/Remove-CsConversationHistoryConfiguration.md b/skype/skype-ps/skype/Remove-CsConversationHistoryConfiguration.md index 783c46e4f8..1d6e47fc07 100644 --- a/skype/skype-ps/skype/Remove-CsConversationHistoryConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsConversationHistoryConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csconversationhistoryconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csconversationhistoryconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsConversationHistoryConfiguration schema: 2.0.0 @@ -137,4 +137,3 @@ Instead, `Remove-CsConversationHistoryConfiguration` resets instances of the Mic [Get-CsConversationHistoryConfiguration](Get-CsConversationHistoryConfiguration.md) [Set-CsConversationHistoryConfiguration](Set-CsConversationHistoryConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsCpsConfiguration.md b/skype/skype-ps/skype/Remove-CsCpsConfiguration.md index b2da6a421b..31f01a2608 100644 --- a/skype/skype-ps/skype/Remove-CsCpsConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsCpsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscpsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cscpsconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsCpsConfiguration schema: 2.0.0 @@ -151,4 +151,3 @@ Removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.CallP [Get-CsCpsConfiguration](Get-CsCpsConfiguration.md) [Set-CsCallParkServiceMusicOnHoldFile](Set-CsCallParkServiceMusicOnHoldFile.md) - diff --git a/skype/skype-ps/skype/Remove-CsDeviceUpdateConfiguration.md b/skype/skype-ps/skype/Remove-CsDeviceUpdateConfiguration.md index 2891fd0ac7..3ba03e403a 100644 --- a/skype/skype-ps/skype/Remove-CsDeviceUpdateConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsDeviceUpdateConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdeviceupdateconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdeviceupdateconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDeviceUpdateConfiguration schema: 2.0.0 @@ -178,4 +178,3 @@ Instead, the `Remove-CsDeviceUpdateConfiguration` cmdlet deletes instances of th [New-CsDeviceUpdateConfiguration](New-CsDeviceUpdateConfiguration.md) [Set-CsDeviceUpdateConfiguration](Set-CsDeviceUpdateConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsDeviceUpdateRule.md b/skype/skype-ps/skype/Remove-CsDeviceUpdateRule.md index ead2aa7c26..f13625d1e3 100644 --- a/skype/skype-ps/skype/Remove-CsDeviceUpdateRule.md +++ b/skype/skype-ps/skype/Remove-CsDeviceUpdateRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdeviceupdaterule +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdeviceupdaterule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDeviceUpdateRule schema: 2.0.0 @@ -174,4 +174,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [Reset-CsDeviceUpdateRule](Reset-CsDeviceUpdateRule.md) [Restore-CsDeviceUpdateRule](Restore-CsDeviceUpdateRule.md) - diff --git a/skype/skype-ps/skype/Remove-CsDiagnosticConfiguration.md b/skype/skype-ps/skype/Remove-CsDiagnosticConfiguration.md index 46315b185e..863e71f71f 100644 --- a/skype/skype-ps/skype/Remove-CsDiagnosticConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsDiagnosticConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdiagnosticconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdiagnosticconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDiagnosticConfiguration schema: 2.0.0 @@ -167,4 +167,3 @@ Instead, the `Remove-CsDiagnosticConfiguration` cmdlet deletes existing instance [New-CsDiagnosticConfiguration](New-CsDiagnosticConfiguration.md) [Set-CsDiagnosticConfiguration](Set-CsDiagnosticConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsDiagnosticHeaderConfiguration.md b/skype/skype-ps/skype/Remove-CsDiagnosticHeaderConfiguration.md index 703701dabb..5b42883a96 100644 --- a/skype/skype-ps/skype/Remove-CsDiagnosticHeaderConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsDiagnosticHeaderConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdiagnosticheaderconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdiagnosticheaderconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDiagnosticHeaderConfiguration schema: 2.0.0 @@ -172,4 +172,3 @@ Instead, the `Remove-CsDiagnosticHeaderConfiguration` cmdlet deletes existing in [New-CsDiagnosticHeaderConfiguration](New-CsDiagnosticHeaderConfiguration.md) [Set-CsDiagnosticHeaderConfiguration](Set-CsDiagnosticHeaderConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsDialInConferencingAccessNumber.md b/skype/skype-ps/skype/Remove-CsDialInConferencingAccessNumber.md index 9d4e4184dd..7f4137e2f9 100644 --- a/skype/skype-ps/skype/Remove-CsDialInConferencingAccessNumber.md +++ b/skype/skype-ps/skype/Remove-CsDialInConferencingAccessNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdialinconferencingaccessnumber +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdialinconferencingaccessnumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDialInConferencingAccessNumber schema: 2.0.0 @@ -172,4 +172,3 @@ The `Remove-CsDialInConferencingAccessNumber` cmdlet deletes instances of the Mi [New-CsDialInConferencingAccessNumber](New-CsDialInConferencingAccessNumber.md) [Set-CsDialInConferencingAccessNumber](Set-CsDialInConferencingAccessNumber.md) - diff --git a/skype/skype-ps/skype/Remove-CsDialInConferencingConfiguration.md b/skype/skype-ps/skype/Remove-CsDialInConferencingConfiguration.md index 87d15b22a4..e0c94267aa 100644 --- a/skype/skype-ps/skype/Remove-CsDialInConferencingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsDialInConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdialinconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdialinconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDialInConferencingConfiguration schema: 2.0.0 @@ -166,4 +166,3 @@ Instead, the `Remove-CSDialInConferencingConfiguration` cmdlet deletes instances [New-CsDialInConferencingConfiguration](New-CsDialInConferencingConfiguration.md) [Set-CsDialInConferencingConfiguration](Set-CsDialInConferencingConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsDialInConferencingDtmfConfiguration.md b/skype/skype-ps/skype/Remove-CsDialInConferencingDtmfConfiguration.md index a05dbf0b6e..8eaaf5a8d7 100644 --- a/skype/skype-ps/skype/Remove-CsDialInConferencingDtmfConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsDialInConferencingDtmfConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdialinconferencingdtmfconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdialinconferencingdtmfconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDialInConferencingDtmfConfiguration schema: 2.0.0 @@ -171,4 +171,3 @@ Instead, the `Remove-CSDialInConferencingDtmfConfiguration` cmdlet deletes insta [New-CsDialInConferencingDtmfConfiguration](New-CsDialInConferencingDtmfConfiguration.md) [Set-CsDialInConferencingDtmfConfiguration](Set-CsDialInConferencingDtmfConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsDialPlan.md b/skype/skype-ps/skype/Remove-CsDialPlan.md index 162b10d712..e42285747c 100644 --- a/skype/skype-ps/skype/Remove-CsDialPlan.md +++ b/skype/skype-ps/skype/Remove-CsDialPlan.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csdialplan +online version: https://learn.microsoft.com/powershell/module/skype/remove-csdialplan applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsDialPlan schema: 2.0.0 @@ -155,4 +155,3 @@ This cmdlet removes instances of the Microsoft.Rtc.Management.WritableConfig.Pol [Remove-CsVoiceNormalizationRule](Remove-CsVoiceNormalizationRule.md) [Get-CsVoiceNormalizationRule](Get-CsVoiceNormalizationRule.md) - diff --git a/skype/skype-ps/skype/Remove-CsEnhancedEmergencyServiceDisclaimer.md b/skype/skype-ps/skype/Remove-CsEnhancedEmergencyServiceDisclaimer.md index 06c5d57e43..12953178d6 100644 --- a/skype/skype-ps/skype/Remove-CsEnhancedEmergencyServiceDisclaimer.md +++ b/skype/skype-ps/skype/Remove-CsEnhancedEmergencyServiceDisclaimer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csenhancedemergencyservicedisclaimer +online version: https://learn.microsoft.com/powershell/module/skype/remove-csenhancedemergencyservicedisclaimer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsEnhancedEmergencyServiceDisclaimer schema: 2.0.0 @@ -134,4 +134,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Loc [Get-CsEnhancedEmergencyServiceDisclaimer](Get-CsEnhancedEmergencyServiceDisclaimer.md) [Get-CsLocationPolicy](Get-CsLocationPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsExUmContact.md b/skype/skype-ps/skype/Remove-CsExUmContact.md index dc2dd8f351..264bd46774 100644 --- a/skype/skype-ps/skype/Remove-CsExUmContact.md +++ b/skype/skype-ps/skype/Remove-CsExUmContact.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csexumcontact +online version: https://learn.microsoft.com/powershell/module/skype/remove-csexumcontact applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsExUmContact schema: 2.0.0 @@ -131,4 +131,3 @@ It removes an object of type Microsoft.Rtc.Management.ADConnect.Schema.OCSADExUm [Get-CsExUmContact](Get-CsExUmContact.md) [Move-CsExUmContact](Move-CsExUmContact.md) - diff --git a/skype/skype-ps/skype/Remove-CsExternalAccessPolicy.md b/skype/skype-ps/skype/Remove-CsExternalAccessPolicy.md index 8a09be45ec..d10506b89c 100644 --- a/skype/skype-ps/skype/Remove-CsExternalAccessPolicy.md +++ b/skype/skype-ps/skype/Remove-CsExternalAccessPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csexternalaccesspolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csexternalaccesspolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsExternalAccessPolicy schema: 2.0.0 manager: bulenteg @@ -14,10 +14,9 @@ ms.reviewer: rogupta ## SYNOPSIS Enables you to remove an existing external access policy. -External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Windows Live and 3) access Skype for Business Server over the Internet, without having to log on to your internal network. +External access policies determine whether or not your users can: 1) Communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) Communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Windows Live; 3) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop) and 4) Access Skype for Business Server over the Internet, without having to log on to your internal network. This cmdlet was introduced in Lync Server 2010. - ## SYNTAX ``` @@ -29,18 +28,17 @@ Remove-CsExternalAccessPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force When you install Skype for Business Server your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with other people who have SIP accounts in your Active Directory Domain Services. In addition, users are not allowed to access Skype for Business Server over the Internet; instead, they must be logged on to your internal network before they will be able to log on to Skype for Business Server. -1. -That might be sufficient to meet your communication needs. +1. That might be sufficient to meet your communication needs. If it doesn't meet your needs you can use external access policies to extend the ability of your users to communicate and collaborate. External access policies can grant (or revoke) the ability of your users to do any or all of the following: -2. -Communicate with people who have SIP accounts with a federated organization. +2. Communicate with people who have SIP accounts with a federated organization. Note that enabling federation alone will not provide users with this capability. Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. -3. -Communicate with people who have SIP accounts with a public instant messaging service such as Windows Live. +3. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration). + +4. Communicate with people who have SIP accounts with a public instant messaging service such as Windows Live. Access Skype for Business Server over the Internet, without having to first log on to your internal network. This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. @@ -53,7 +51,6 @@ You can also run the `Remove-CsExternalAccessPolicy` cmdlet against the global e In that case, however, the global policies will not be deleted; by design, global policies cannot be deleted. Instead, the properties of the global policy will simply be reset to their default values. - ## EXAMPLES ### -------------------------- Example 1 ------------------------ @@ -64,7 +61,6 @@ Remove-CsExternalAccessPolicy -Identity site:Redmond In Example 1, the external access policy with the Identity site:Redmond is deleted. After the policy is removed, users in the Redmond site will have their external access permissions governed by the global policy. - ### -------------------------- Example 2 ------------------------ ``` Get-CsExternalAccessPolicy -Filter site:* | Remove-CsExternalAccessPolicy @@ -74,7 +70,6 @@ Example 2 deletes all the external access policies that have been configured at To carry out this task, the command first uses the `Get-CsExternalAccessPolicy` cmdlet and the Filter parameter to return a collection of policies configured at the site scope; the filter value "site:*" limits the returned data to external access policies that have an Identity that begins with the string value "site:". The filtered collection is then piped to the `Remove-CsExternalAccessPolicy` cmdlet, which deletes each policy in the collection. - ### -------------------------- Example 3 ------------------------ ``` Get-CsExternalAccessPolicy | Where-Object {$_.EnableFederationAccess -eq $True} | Remove-CsExternalAccessPolicy @@ -85,7 +80,6 @@ To do this, the command first calls the `Get-CsExternalAccessPolicy` cmdlet to r This collection is then piped to the `Where-Object` cmdlet, which picks out only those policies where the EnableFederationAccess property is equal to True. This filtered collection is then piped to the `Remove-CsExternalAccessPolicy` cmdlet, which deletes each policy in the collection. - ### -------------------------- Example 4 ------------------------ ``` Get-CsExternalAccessPolicy | Where-Object {$_.EnableFederationAccess -eq $True -or $_.EnablePublicCloudAccess -eq $True} | Remove-CsExternalAccessPolicy @@ -100,7 +94,6 @@ To delete all the policies where both EnableFederationAccess and EnablePublicClo `Where-Object {$_.EnableFederationAccess -eq $True -and $_.EnablePublicCloudAccess -eq $True}` - ## PARAMETERS ### -Identity @@ -113,11 +106,10 @@ To remove a per-user policy, use syntax similar to this: `-Identity SalesAccessP Note that wildcards are not allowed when specifying an Identity. - ```yaml Type: XdsIdentity Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: True @@ -130,11 +122,10 @@ Accept wildcard characters: False ### -Force Suppresses the display of any non-fatal error message that might occur when running the command. - ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -147,7 +138,6 @@ Accept wildcard characters: False ### -WhatIf Describes what would happen if you executed the command without actually executing the command. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -164,7 +154,6 @@ Accept wildcard characters: False ### -Confirm Prompts you for confirmation before executing the command. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -188,11 +177,10 @@ You can return the tenant ID for each of your Skype for Business Online tenants `Get-CsTenant | Select-Object DisplayName, TenantID` - ```yaml Type: Guid Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -229,4 +217,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsExternalAccessPolicy](New-CsExternalAccessPolicy.md) [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsExternalUserCommunicationPolicy.md b/skype/skype-ps/skype/Remove-CsExternalUserCommunicationPolicy.md index 54d5a33e6e..a7a6576fd6 100644 --- a/skype/skype-ps/skype/Remove-CsExternalUserCommunicationPolicy.md +++ b/skype/skype-ps/skype/Remove-CsExternalUserCommunicationPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csexternalusercommunicationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csexternalusercommunicationpolicy applicable: Skype for Business Online title: Remove-CsExternalUserCommunicationPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsExternalUserCommunicationPolicy @@ -131,4 +131,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsFIPSConfiguration.md b/skype/skype-ps/skype/Remove-CsFIPSConfiguration.md index 02e27ad528..21351e05ab 100644 --- a/skype/skype-ps/skype/Remove-CsFIPSConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsFIPSConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csfipsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csfipsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsFIPSConfiguration schema: 2.0.0 @@ -169,4 +169,3 @@ Instead, the `Remove-CsFIPSConfiguration` cmdlet deletes existing instances of t [New-CsFIPSConfiguration](New-CsFIPSConfiguration.md) [Set-CsFIPSConfiguration](Set-CsFIPSConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsFileTransferFilterConfiguration.md b/skype/skype-ps/skype/Remove-CsFileTransferFilterConfiguration.md index 162e27f702..bcffa2634d 100644 --- a/skype/skype-ps/skype/Remove-CsFileTransferFilterConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsFileTransferFilterConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csfiletransferfilterconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csfiletransferfilterconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsFileTransferFilterConfiguration schema: 2.0.0 @@ -160,4 +160,3 @@ Instead, it removes instances of the Microsoft.Rtc.Management.WritableConfig.Set [Set-CsFileTransferFilterConfiguration](Set-CsFileTransferFilterConfiguration.md) [Get-CsFileTransferFilterConfiguration](Get-CsFileTransferFilterConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsGroupPickupUserOrbit.md b/skype/skype-ps/skype/Remove-CsGroupPickupUserOrbit.md index 0a97ba8877..f6a9d6484e 100644 --- a/skype/skype-ps/skype/Remove-CsGroupPickupUserOrbit.md +++ b/skype/skype-ps/skype/Remove-CsGroupPickupUserOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csgrouppickupuserorbit +online version: https://learn.microsoft.com/powershell/module/skype/remove-csgrouppickupuserorbit applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsGroupPickupUserOrbit schema: 2.0.0 @@ -124,4 +124,3 @@ None. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsHealthMonitoringConfiguration.md b/skype/skype-ps/skype/Remove-CsHealthMonitoringConfiguration.md index 97e5a7ea90..d7ea78fe80 100644 --- a/skype/skype-ps/skype/Remove-CsHealthMonitoringConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsHealthMonitoringConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cshealthmonitoringconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cshealthmonitoringconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsHealthMonitoringConfiguration schema: 2.0.0 @@ -175,4 +175,3 @@ Instead, the `Remove-CsHealthMonitoringConfiguration` cmdlet deletes existing in [New-CsHealthMonitoringConfiguration](New-CsHealthMonitoringConfiguration.md) [Set-CsHealthMonitoringConfiguration](Set-CsHealthMonitoringConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsHostedVoicemailPolicy.md b/skype/skype-ps/skype/Remove-CsHostedVoicemailPolicy.md index bbd7a131c7..ce701e607c 100644 --- a/skype/skype-ps/skype/Remove-CsHostedVoicemailPolicy.md +++ b/skype/skype-ps/skype/Remove-CsHostedVoicemailPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cshostedvoicemailpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-cshostedvoicemailpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsHostedVoicemailPolicy schema: 2.0.0 @@ -165,4 +165,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Voic [Get-CsHostedVoicemailPolicy](Get-CsHostedVoicemailPolicy.md) [Grant-CsHostedVoicemailPolicy](Grant-CsHostedVoicemailPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsHostingProvider.md b/skype/skype-ps/skype/Remove-CsHostingProvider.md index 307afddd32..8dd1e03560 100644 --- a/skype/skype-ps/skype/Remove-CsHostingProvider.md +++ b/skype/skype-ps/skype/Remove-CsHostingProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cshostingprovider +online version: https://learn.microsoft.com/powershell/module/skype/remove-cshostingprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsHostingProvider schema: 2.0.0 @@ -199,4 +199,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsHostingProvider](New-CsHostingProvider.md) [Set-CsHostingProvider](Set-CsHostingProvider.md) - diff --git a/skype/skype-ps/skype/Remove-CsHuntGroup.md b/skype/skype-ps/skype/Remove-CsHuntGroup.md deleted file mode 100644 index 456fc095ae..0000000000 --- a/skype/skype-ps/skype/Remove-CsHuntGroup.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cshuntgroup -applicable: Skype for Business Online -title: Remove-CsHuntGroup -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsHuntGroup - -## SYNOPSIS -The Remove-CsHuntGroup cmdlet deletes an existing Call Queue. - -## SYNTAX - -``` -Remove-CsHuntGroup -PrimaryUri <System.Uri> [<CommonParameters>] -``` - -## DESCRIPTION -The Remove-CsHuntGroup cmdlet deletes an existing Call Queue specified by the PrimaryUri parameter. - -The Remove-CsHuntGroup cmdlet may suggest additional steps required to complete the Call Queue setup. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsHuntGroup -PrimaryUri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com" -``` - -This example deletes the Call Queue with the primary uri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com". - - - - -## PARAMETERS - -### -PrimaryUri -The PrimaryUri parameter represents the SIP address for the Call Queue. It must start with "sip:". - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassDualWrite -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for Microsoft internal use only. - -PARAMVALUE: Fqdn - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Uri - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.HuntGroup.Models.HuntGroup - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsHybridApplicationEndpoint.md b/skype/skype-ps/skype/Remove-CsHybridApplicationEndpoint.md index 5f1d0f13d4..947839dc20 100644 --- a/skype/skype-ps/skype/Remove-CsHybridApplicationEndpoint.md +++ b/skype/skype-ps/skype/Remove-CsHybridApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsHybridApplicationEndpoint schema: 2.0.0 @@ -101,8 +101,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[New-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint?view=skype-ps) +[New-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint?view=skype-ps) -[Get-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint?view=skype-ps) +[Get-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint?view=skype-ps) -[Set-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint?view=skype-ps) +[Set-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsHybridPSTNSite.md b/skype/skype-ps/skype/Remove-CsHybridPSTNSite.md index a88440ba32..57891ebc8e 100644 --- a/skype/skype-ps/skype/Remove-CsHybridPSTNSite.md +++ b/skype/skype-ps/skype/Remove-CsHybridPSTNSite.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cshybridpstnsite +online version: https://learn.microsoft.com/powershell/module/skype/remove-cshybridpstnsite applicable: Skype for Business Online title: Remove-CsHybridPSTNSite schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsHybridPSTNSite @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the `Remove-CsHybridPSTNSite` cmdlet to remove a previously specified hybrid public switched telephone network (PSTN) site. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` @@ -154,4 +156,3 @@ None. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsImConfiguration.md b/skype/skype-ps/skype/Remove-CsImConfiguration.md index a0dc98074b..9b6ba26e08 100644 --- a/skype/skype-ps/skype/Remove-CsImConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsImConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csimconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csimconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsImConfiguration schema: 2.0.0 @@ -130,8 +130,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[Get-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/get-csimconfiguration?view=skype-ps) +[Get-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/get-csimconfiguration?view=skype-ps) -[New-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/new-csimconfiguration?view=skype-ps) +[New-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/new-csimconfiguration?view=skype-ps) -[Set-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/set-csimconfiguration?view=skype-ps) +[Set-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/set-csimconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsImFilterConfiguration.md b/skype/skype-ps/skype/Remove-CsImFilterConfiguration.md index 067d6023b5..25c342bb06 100644 --- a/skype/skype-ps/skype/Remove-CsImFilterConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsImFilterConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csimfilterconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csimfilterconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsImFilterConfiguration schema: 2.0.0 @@ -145,4 +145,3 @@ Removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.ImFil [Set-CsImFilterConfiguration](Set-CsImFilterConfiguration.md) [Get-CsImFilterConfiguration](Get-CsImFilterConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsImTranslationConfiguration.md b/skype/skype-ps/skype/Remove-CsImTranslationConfiguration.md index 197a41b16f..f3d59ef6ed 100644 --- a/skype/skype-ps/skype/Remove-CsImTranslationConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsImTranslationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csimtranslationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csimtranslationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsImTranslationConfiguration schema: 2.0.0 @@ -111,4 +111,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md b/skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md deleted file mode 100644 index ab941661ab..0000000000 --- a/skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csinboundblockednumberpattern -applicable: Skype for Business Online -title: Remove-CsInboundBlockedNumberPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# Remove-CsInboundBlockedNumberPattern - -## SYNOPSIS -Removes a blocked number pattern from the tenant list. - -## SYNTAX - -``` -Remove-CsInboundBlockedNumberPattern [-Tenant <System.Guid>] [-Identity] <XdsGlobalRelativeIdentity> [-Force] - [-WhatIf] [-Confirm] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet removes a blocked number pattern from the tenant list. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Remove-CsInboundBlockedNumberPattern -Identity "BlockAutomatic" -``` - -This example removes a blocked number pattern identified as "BlockAutomatic". - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The *Force* switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the *Force* switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier specifying the blocked number pattern to be removed. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the *AsJob* parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the *Receive-Job* cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS - -[New-CsInboundBlockedNumberPattern](New-CsInboundBlockedNumberPattern.md) - -[Set-CsInboundBlockedNumberPattern](Set-CsInboundBlockedNumberPattern.md) - -[Get-CsInboundBlockedNumberPattern](Get-CsInboundBlockedNumberPattern.md) diff --git a/skype/skype-ps/skype/Remove-CsKerberosAccountAssignment.md b/skype/skype-ps/skype/Remove-CsKerberosAccountAssignment.md index b289a22865..acd10f5224 100644 --- a/skype/skype-ps/skype/Remove-CsKerberosAccountAssignment.md +++ b/skype/skype-ps/skype/Remove-CsKerberosAccountAssignment.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cskerberosaccountassignment +online version: https://learn.microsoft.com/powershell/module/skype/remove-cskerberosaccountassignment applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsKerberosAccountAssignment schema: 2.0.0 @@ -159,4 +159,3 @@ Instead, the cmdlet deletes existing instances of the Microsoft.Rtc.Management.W [New-CsKerberosAccountAssignment](New-CsKerberosAccountAssignment.md) [Set-CsKerberosAccountAssignment](Set-CsKerberosAccountAssignment.md) - diff --git a/skype/skype-ps/skype/Remove-CsLisLocation.md b/skype/skype-ps/skype/Remove-CsLisLocation.md index 043fae055b..ccca42e1b3 100644 --- a/skype/skype-ps/skype/Remove-CsLisLocation.md +++ b/skype/skype-ps/skype/Remove-CsLisLocation.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cslislocation +online version: https://learn.microsoft.com/powershell/module/skype/remove-cslislocation applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsLisLocation schema: 2.0.0 @@ -493,4 +493,3 @@ It removes an object of type System.Management.Automation.PSCustomObject. [Remove-CsLisWirelessAccessPoint](Remove-CsLisWirelessAccessPoint.md) [Get-CsLisCivicAddress](Get-CsLisCivicAddress.md) - diff --git a/skype/skype-ps/skype/Remove-CsLisPort.md b/skype/skype-ps/skype/Remove-CsLisPort.md index 766576e96e..6a06ce9cb4 100644 --- a/skype/skype-ps/skype/Remove-CsLisPort.md +++ b/skype/skype-ps/skype/Remove-CsLisPort.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cslisport +online version: https://learn.microsoft.com/powershell/module/skype/remove-cslisport applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsLisPort schema: 2.0.0 @@ -183,4 +183,3 @@ It removes an object of type System.Management.Automation.PSCustomObject. [Remove-CsLisLocation](Remove-CsLisLocation.md) [Remove-CsLisSwitch](Remove-CsLisSwitch.md) - diff --git a/skype/skype-ps/skype/Remove-CsLisServiceProvider.md b/skype/skype-ps/skype/Remove-CsLisServiceProvider.md index 4809dd6244..e7c73e5c72 100644 --- a/skype/skype-ps/skype/Remove-CsLisServiceProvider.md +++ b/skype/skype-ps/skype/Remove-CsLisServiceProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cslisserviceprovider +online version: https://learn.microsoft.com/powershell/module/skype/remove-cslisserviceprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsLisServiceProvider schema: 2.0.0 @@ -95,4 +95,3 @@ It removes an object of type System.Management.Automation.PSCustomObject. [Set-CsLisServiceProvider](Set-CsLisServiceProvider.md) [Get-CsLisServiceProvider](Get-CsLisServiceProvider.md) - diff --git a/skype/skype-ps/skype/Remove-CsLisSubnet.md b/skype/skype-ps/skype/Remove-CsLisSubnet.md index 6ad3321a5b..3ce56e33d1 100644 --- a/skype/skype-ps/skype/Remove-CsLisSubnet.md +++ b/skype/skype-ps/skype/Remove-CsLisSubnet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cslissubnet +online version: https://learn.microsoft.com/powershell/module/skype/remove-cslissubnet applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsLisSubnet schema: 2.0.0 @@ -136,4 +136,3 @@ This cmdlet removes an object of type System.Management.Automation.PSCustomObjec [Get-CsLisSubnet](Get-CsLisSubnet.md) [Remove-CsLisLocation](Remove-CsLisLocation.md) - diff --git a/skype/skype-ps/skype/Remove-CsLisSwitch.md b/skype/skype-ps/skype/Remove-CsLisSwitch.md index 76f3f6ebda..5ef8122f1d 100644 --- a/skype/skype-ps/skype/Remove-CsLisSwitch.md +++ b/skype/skype-ps/skype/Remove-CsLisSwitch.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cslisswitch +online version: https://learn.microsoft.com/powershell/module/skype/remove-cslisswitch applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsLisSwitch schema: 2.0.0 @@ -141,4 +141,3 @@ It removes an object of type System.Management.Automation.PSCustomObject. [Remove-CsLisLocation](Remove-CsLisLocation.md) [Get-CsLisPort](Get-CsLisPort.md) - diff --git a/skype/skype-ps/skype/Remove-CsLisWirelessAccessPoint.md b/skype/skype-ps/skype/Remove-CsLisWirelessAccessPoint.md index e987410b6b..044104f835 100644 --- a/skype/skype-ps/skype/Remove-CsLisWirelessAccessPoint.md +++ b/skype/skype-ps/skype/Remove-CsLisWirelessAccessPoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csliswirelessaccesspoint +online version: https://learn.microsoft.com/powershell/module/skype/remove-csliswirelessaccesspoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsLisWirelessAccessPoint schema: 2.0.0 @@ -132,4 +132,3 @@ This cmdlet removes an object of type System.Management.Automation.PSCustomObjec [Get-CsLisWirelessAccessPoint](Get-CsLisWirelessAccessPoint.md) [Remove-CsLisLocation](Remove-CsLisLocation.md) - diff --git a/skype/skype-ps/skype/Remove-CsLocationPolicy.md b/skype/skype-ps/skype/Remove-CsLocationPolicy.md index 1f30767b50..b6aa1cf457 100644 --- a/skype/skype-ps/skype/Remove-CsLocationPolicy.md +++ b/skype/skype-ps/skype/Remove-CsLocationPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cslocationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-cslocationpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsLocationPolicy schema: 2.0.0 @@ -181,4 +181,3 @@ Instead, the cmdlet removes instances of the Microsoft.Rtc.Management.WritableCo [Grant-CsLocationPolicy](Grant-CsLocationPolicy.md) [Test-CsLocationPolicy](Test-CsLocationPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsManagementConnection.md b/skype/skype-ps/skype/Remove-CsManagementConnection.md index 3fa999ecd5..6df3c26265 100644 --- a/skype/skype-ps/skype/Remove-CsManagementConnection.md +++ b/skype/skype-ps/skype/Remove-CsManagementConnection.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csmanagementconnection +online version: https://learn.microsoft.com/powershell/module/skype/remove-csmanagementconnection applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsManagementConnection schema: 2.0.0 @@ -107,4 +107,3 @@ Instead, the `Remove-CsManagementConnection` cmdlet deletes instances of the Mic [Remove-CsConfigurationStoreLocation](Remove-CsConfigurationStoreLocation.md) [Set-CsManagementConnection](Set-CsManagementConnection.md) - diff --git a/skype/skype-ps/skype/Remove-CsMcxConfiguration.md b/skype/skype-ps/skype/Remove-CsMcxConfiguration.md index 15f251a2cc..87060d1bca 100644 --- a/skype/skype-ps/skype/Remove-CsMcxConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsMcxConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csmcxconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csmcxconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsMcxConfiguration schema: 2.0.0 manager: rogupta @@ -185,4 +185,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WriteableC ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsMediaConfiguration.md b/skype/skype-ps/skype/Remove-CsMediaConfiguration.md index c80ffb002d..afa18b9584 100644 --- a/skype/skype-ps/skype/Remove-CsMediaConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsMediaConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csmediaconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csmediaconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsMediaConfiguration schema: 2.0.0 @@ -154,4 +154,3 @@ Removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Media [Set-CsMediaConfiguration](Set-CsMediaConfiguration.md) [Get-CsMediaConfiguration](Get-CsMediaConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsMeetingConfiguration.md b/skype/skype-ps/skype/Remove-CsMeetingConfiguration.md index 6475e2152a..29096e1294 100644 --- a/skype/skype-ps/skype/Remove-CsMeetingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsMeetingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csmeetingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csmeetingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsMeetingConfiguration schema: 2.0.0 @@ -190,4 +190,3 @@ Instead, the `Remove-CsMeetingConfiguration` cmdlet deletes existing instances o [New-CsMeetingConfiguration](New-CsMeetingConfiguration.md) [Set-CsMeetingConfiguration](Set-CsMeetingConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsMobilityPolicy.md b/skype/skype-ps/skype/Remove-CsMobilityPolicy.md index 1b202e5672..bf1e210f0e 100644 --- a/skype/skype-ps/skype/Remove-CsMobilityPolicy.md +++ b/skype/skype-ps/skype/Remove-CsMobilityPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csmobilitypolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csmobilitypolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsMobilityPolicy schema: 2.0.0 manager: bulenteg @@ -216,4 +216,3 @@ Instead, the `Remove-CsMobilityPolicy` cmdlet deletes instances of the Microsoft ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsNetworkBandwidthPolicyProfile.md b/skype/skype-ps/skype/Remove-CsNetworkBandwidthPolicyProfile.md index f5dbe3debe..134bd4667f 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkBandwidthPolicyProfile.md +++ b/skype/skype-ps/skype/Remove-CsNetworkBandwidthPolicyProfile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworkbandwidthpolicyprofile +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworkbandwidthpolicyprofile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkBandwidthPolicyProfile schema: 2.0.0 @@ -153,4 +153,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Set-CsNetworkBandwidthPolicyProfile](Set-CsNetworkBandwidthPolicyProfile.md) [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) - diff --git a/skype/skype-ps/skype/Remove-CsNetworkConfiguration.md b/skype/skype-ps/skype/Remove-CsNetworkConfiguration.md index 616d874b90..ae7068d77e 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsNetworkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworkconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkConfiguration schema: 2.0.0 @@ -142,4 +142,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Get-CsNetworkSubnet](Get-CsNetworkSubnet.md) [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) - diff --git a/skype/skype-ps/skype/Remove-CsNetworkInterRegionRoute.md b/skype/skype-ps/skype/Remove-CsNetworkInterRegionRoute.md index c630fe8b40..3df20e1a1b 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkInterRegionRoute.md +++ b/skype/skype-ps/skype/Remove-CsNetworkInterRegionRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworkinterregionroute +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworkinterregionroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkInterRegionRoute schema: 2.0.0 @@ -146,4 +146,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Set-CsNetworkInterRegionRoute](Set-CsNetworkInterRegionRoute.md) [Get-CsNetworkInterRegionRoute](Get-CsNetworkInterRegionRoute.md) - diff --git a/skype/skype-ps/skype/Remove-CsNetworkInterSitePolicy.md b/skype/skype-ps/skype/Remove-CsNetworkInterSitePolicy.md index 72a1969f6f..8dc5aaec89 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkInterSitePolicy.md +++ b/skype/skype-ps/skype/Remove-CsNetworkInterSitePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworkintersitepolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworkintersitepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkInterSitePolicy schema: 2.0.0 @@ -141,4 +141,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Set-CsNetworkInterSitePolicy](Set-CsNetworkInterSitePolicy.md) [Get-CsNetworkInterSitePolicy](Get-CsNetworkInterSitePolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsNetworkRegion.md b/skype/skype-ps/skype/Remove-CsNetworkRegion.md index 3fbc38039e..3f35e18280 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkRegion.md +++ b/skype/skype-ps/skype/Remove-CsNetworkRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworkregion +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworkregion applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkRegion schema: 2.0.0 @@ -173,4 +173,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Set-CsNetworkRegion](Set-CsNetworkRegion.md) [Get-CsNetworkRegion](Get-CsNetworkRegion.md) - diff --git a/skype/skype-ps/skype/Remove-CsNetworkRegionLink.md b/skype/skype-ps/skype/Remove-CsNetworkRegionLink.md index 5e6c326dec..57fec11fcc 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkRegionLink.md +++ b/skype/skype-ps/skype/Remove-CsNetworkRegionLink.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworkregionlink +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworkregionlink applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkRegionLink schema: 2.0.0 @@ -143,4 +143,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Set-CsNetworkRegionLink](Set-CsNetworkRegionLink.md) [Get-CsNetworkRegionLink](Get-CsNetworkRegionLink.md) - diff --git a/skype/skype-ps/skype/Remove-CsNetworkSite.md b/skype/skype-ps/skype/Remove-CsNetworkSite.md index cd132e027e..385a4f9411 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkSite.md +++ b/skype/skype-ps/skype/Remove-CsNetworkSite.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworksite +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworksite applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkSite schema: 2.0.0 @@ -141,4 +141,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Set-CsNetworkSite](Set-CsNetworkSite.md) [Get-CsNetworkSite](Get-CsNetworkSite.md) - diff --git a/skype/skype-ps/skype/Remove-CsNetworkSubnet.md b/skype/skype-ps/skype/Remove-CsNetworkSubnet.md index b7caa97b9b..60a89146b9 100644 --- a/skype/skype-ps/skype/Remove-CsNetworkSubnet.md +++ b/skype/skype-ps/skype/Remove-CsNetworkSubnet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csnetworksubnet +online version: https://learn.microsoft.com/powershell/module/skype/remove-csnetworksubnet applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsNetworkSubnet schema: 2.0.0 @@ -143,4 +143,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Ne [Set-CsNetworkSubnet](Set-CsNetworkSubnet.md) [Get-CsNetworkSubnet](Get-CsNetworkSubnet.md) - diff --git a/skype/skype-ps/skype/Remove-CsOAuthServer.md b/skype/skype-ps/skype/Remove-CsOAuthServer.md index 184efd5e08..8841ad2fa5 100644 --- a/skype/skype-ps/skype/Remove-CsOAuthServer.md +++ b/skype/skype-ps/skype/Remove-CsOAuthServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csoauthserver +online version: https://learn.microsoft.com/powershell/module/skype/remove-csoauthserver applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsOAuthServer schema: 2.0.0 @@ -174,4 +174,3 @@ Instead, the `Remove-CsOAuthServer` cmdlet deletes existing instances of the Mic [New-CsOAuthServer](New-CsOAuthServer.md) [Set-CsOAuthServer](Set-CsOAuthServer.md) - diff --git a/skype/skype-ps/skype/Remove-CsOnlineApplicationEndpoint.md b/skype/skype-ps/skype/Remove-CsOnlineApplicationEndpoint.md deleted file mode 100644 index 141151c631..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineApplicationEndpoint.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlineapplicationendpoint -applicable: Skype for Business Online -title: Remove-CsOnlineApplicationEndpoint -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineApplicationEndpoint - -## SYNOPSIS -The `Remove-CsOnlineApplicationEndpoint` is used to remove a Trusted Application Endpoint for a tenant. - -## SYNTAX - -``` -Remove-CsOnlineApplicationEndpoint [-Uri] <String> [-Audience <String>] [-Ring <String>] - [-PhoneNumber <String>] [-IsInternalRun <Boolean>] [-Tenant <Guid>] - [-RunFullProvisioningFlow <Boolean>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to remove a Trusted Application Endpoint for a tenant. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOnlineApplicationEndpoint -Uri "sip:sample@domain.com" -``` - -This exampes removes the "sample@domain.com" application endpoint. - -## PARAMETERS - -### -Uri -Sip Uri that identifies the tenant specific endpoint for the application. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: SipUri -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Audience -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneNumber -The service number assigned to the trusted application endpoint. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsInternalRun -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Ring -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RunFullProvisioningFlow -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Set-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/set-csonlineapplicationendpoint) - -[New-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/new-csonlineapplicationendpoint) - -[Get-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/get-csonlineapplicationendpoint) - -[Set up a Trusted Application Endpoint](https://docs.microsoft.com/skype-sdk/trusted-application-api/docs/trustedapplicationendpoint) diff --git a/skype/skype-ps/skype/Remove-CsOnlineApplicationInstanceAssociation.md b/skype/skype-ps/skype/Remove-CsOnlineApplicationInstanceAssociation.md deleted file mode 100644 index 938e1ecd5d..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineApplicationInstanceAssociation.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlineapplicationinstanceassociation -applicable: Skype for Business Online -title: Remove-CsOnlineApplicationInstanceAssociation -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineApplicationInstanceAssociation - -## SYNOPSIS -Use the Remove-CsOnlineApplicationInstanceAssociation cmdlet to remove the association between an application instance and the associated application configuration. - -## SYNTAX - -``` -Remove-CsOnlineApplicationInstanceAssociation -Identities <String[]> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Remove-CsOnlineApplicationInstanceAssociation cmdlet to remove the association between an application instance and the associated application configuration. - -This is useful when you want to associate this application instance with another application configuration for handling incoming calls. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Remove-CsOnlineApplicationInstanceAssociation -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -``` - -This example removes the configuration association for the application instance that has the identity of "f7a821dc-2d69-5ae8-8525-bcb4a4556093". - -## PARAMETERS - -### -Identities -The identities for the application instances whose configuration associations are to be removed. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### System.String[] -The Remove-CsOnlineApplicationInstanceAssociation cmdlet accepts a string array as the Identities parameter. - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Online.Models.AssociationOperationOutput - -## NOTES - -## RELATED LINKS - -[Get-CsOnlineApplicationInstanceAssociation](Get-CsOnlineApplicationInstanceAssociation.md) - -[Get-CsOnlineApplicationInstanceAssociationStatus](Get-CsOnlineApplicationInstanceAssociationStatus.md) - -[New-CsOnlineApplicationInstanceAssociation](New-CsOnlineApplicationInstanceAssociation.md) diff --git a/skype/skype-ps/skype/Remove-CsOnlineLisCivicAddress.md b/skype/skype-ps/skype/Remove-CsOnlineLisCivicAddress.md deleted file mode 100644 index 499434b66c..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineLisCivicAddress.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlineliscivicaddress -applicable: Skype for Business Online -title: Remove-CsOnlineLisCivicAddress -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# Remove-CsOnlineLisCivicAddress - -## SYNOPSIS -Use the \`Remove-CsOnlineLisCivicAddress\` cmdlet to delete an existing civic address from the Location Information Server (LIS.) You can't remove a civic address if any of its associated locations are assigned to users. - -## SYNTAX - -``` -Remove-CsOnlineLisCivicAddress -CivicAddressId <Guid> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOnlineLisCivicAddress -CivicAddressId ee38d9a5-33dc-4a32-9fb8-f234cedb91ac -``` - -This example removes the emergency civic address with the specified identification. - - -### -------------------------- Example 2 -------------------------- -``` -Get-CsOnlineLisCivicAddress -City Redmond | Remove-CsOnlineLisCivicAddress -``` - -This example removes all the emergency civic addresses in the city of Redmond. - - -## PARAMETERS - -### -CivicAddressId -Specifies the unique identifier of the civic address to be deleted. -You can find civic address identifiers by using the \`Get-CsOnlineLisCivicAddress\` cmdlet. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### This cmdlet accepts pipelined input from the \`Get-CsOnlineLisCivicAddress\` cmdlet. - -## OUTPUTS - -### None - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsOnlineLisLocation.md b/skype/skype-ps/skype/Remove-CsOnlineLisLocation.md deleted file mode 100644 index ccfd2a47ae..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineLisLocation.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinelislocation -applicable: Skype for Business Online -title: Remove-CsOnlineLisLocation -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# Remove-CsOnlineLisLocation - -## SYNOPSIS -Use the \`Remove-CsOnlineLisLocation\` cmdlet to remove an existing emergency location from the Location Information Service (LIS.) You can only remove locations that have no assigned users. - -## SYNTAX -``` -Remove-CsOnlineLisLocation -LocationId <Guid> [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -If the location specified for removal is assigned to users, the cmdlet will fail until the users assignments are removed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOnlineLisLocation -LocationId 788dd820-c136-4255-9f61-24b880ad0763 -``` - -This example removes the location specified by its identity. - - -## PARAMETERS - -### -LocationId -Specifies the unique identifier of the location to be deleted. -Location identities can be discovered by using the \`Get-CsOnlineLisLocation\` cmdlet. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### This cmdlet supports pipelined input from the \`Get-CsOnlineLisLocation\` cmdlet. - -## OUTPUTS - -### None - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsOnlineLisWirelessAccessPoint.md b/skype/skype-ps/skype/Remove-CsOnlineLisWirelessAccessPoint.md deleted file mode 100644 index 304343d297..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineLisWirelessAccessPoint.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlineliswirelessaccesspoint -applicable: Skype for Business Online -title: Remove-CsOnlineLisWirelessAccessPoint -schema: 2.0.0 -author: junya -ms.author: junya -ms.reviewer: ---- - -# Remove-CsOnlineLisWirelessAccessPoint - -## SYNOPSIS -Removes a Location Information Server (LIS) wireless access point (WAP). - -## SYNTAX - -``` -Remove-CsOnlineLisWirelessAccessPoint [[-TenantId] <Guid>] [-BSSID] <String> [-IsDebug <Boolean>] - [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet removes a WAP from the location configuration database. Removing the WAP will not remove the location associated with that WAP. Use the \`Remove-CsLisOnlineLocation\` cmdlet to remove a location. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOnlineLisWirelessAccessPoint -BSSID 0B-23-CD-16-AA-CC -``` - -Example 1 removes the Location Information Server (LIS) wireless access point with BSS ID "0B-23-CD-16-AA-CC". - - -## PARAMETERS - -### -BSSID -The Basic Service Set Identifier (BSSID) of the wireless access point. This value must be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. If an entry with the specified BSSID value does not exist, a new WAP location will be created. If an entry with the specified BSSID does exist, that entry will be replaced. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDebug -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NCSApiUrl -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - - -### System.Guid - - -### System.String - - -## OUTPUTS - - -### System.Object - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsOnlineNumberPortInOrder.md b/skype/skype-ps/skype/Remove-CsOnlineNumberPortInOrder.md deleted file mode 100644 index 411805ca4e..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineNumberPortInOrder.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinenumberportinorder -applicable: Skype for Business Online -title: Remove-CsOnlineNumberPortInOrder -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineNumberPortInOrder - -## SYNOPSIS -This cmdlet is reserved for Microsoft internal use only. -New third party provider ports should be provisioned through the Skype for Business Online admin center. - -## SYNTAX - -``` -Remove-CsOnlineNumberPortInOrder [-Tenant <Guid>] -PortInOrderId <String> [-DomainController <Fqdn>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -PortInOrderId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsOnlinePSTNGateway.md b/skype/skype-ps/skype/Remove-CsOnlinePSTNGateway.md deleted file mode 100644 index 91ba51a16b..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlinePSTNGateway.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinepstngateway -applicable: Skype for Business Online -title: Remove-CsOnlinePSTNGateway -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlinePSTNGateway - -## SYNOPSIS -Removes the configuration of the previously defined Session Border Controller(s) (SBC(s)) that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. - -## SYNTAX -``` -Remove-CsOnlinePSTNGateway -Identity <SBCFQDN> -``` - -## DESCRIPTION -Use this cmdlet to remove the configuration of the previously created Session Border Controller(s) (SBC(s)) configuration. Note the SBC must be removed from all voice routes before executing this cmdlet. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsOnlinePSTNGateway -Identity sbc.contoso.com -``` - -This example removes SBC with Identity (and FQDN) sbc.contoso.com. - -### Example 2 -```powershell -PS C:\> Remove-CsOnlinePSTNGateway | ?{$_.Identity -like "*.contoso.com"} -``` - -This example removes the SBCs with identities (and FQDNs) matching the pattern *.contoso.com. For example: sbc1.contoso.com, sbc2.contoso.com etc. - -## PARAMETERS - -### -Identity -The parameter is mandatory for the cmdlet. The Identity is the same as the SBC FQDN. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: -Applicable: Skype for Business Online -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[Set-CsOnlinePSTNGateway](Set-CsOnlinePSTNGateway.md) - -[New-CsOnlinePSTNGateway](New-CsOnlinePSTNGateway.md) - -[Get-CsOnlinePSTNGateway](Get-CsOnlinePSTNGateway.md) diff --git a/skype/skype-ps/skype/Remove-CsOnlineSchedule.md b/skype/skype-ps/skype/Remove-CsOnlineSchedule.md deleted file mode 100644 index 7067de8a56..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineSchedule.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlineschedule -applicable: Skype for Business Online -title: Remove-CsOnlineSchedule -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineSchedule - -## SYNOPSIS -Use the Remove-CsOnlineSchedule cmdlet to remove a schedule. - -## SYNTAX -``` -Remove-CsOnlineSchedule -Id <String> [-Tenant <Guid>] [-CommonParameters] -``` - -## DESCRIPTION -The Remove-CsOnlineSchedule cmdlet deletes a schedule that is specified by using the Id parameter. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOnlineSchedule -Id "fa9081d6-b4f3-5c96-baec-0b00077709e5" -``` - -This example deletes the schedule that has a Id of fa9081d6-b4f3-5c96-baec-0b00077709e5. - - -## PARAMETERS - -### -Id -The Id for the schedule to be removed. - - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216).` - -## INPUTS - -### System.String -The Remove-CsOnlineSchedule cmdlet accepts a string as the Id parameter. - - -## OUTPUTS - -### System.Void - - -## NOTES - -## RELATED LINKS - -[New-CsOnlineSchedule](New-CsOnlineSchedule.md) - -[Set-CsOnlineSchedule](Set-CsOnlineSchedule.md) diff --git a/skype/skype-ps/skype/Remove-CsOnlineTelephoneNumber.md b/skype/skype-ps/skype/Remove-CsOnlineTelephoneNumber.md deleted file mode 100644 index 1605004b9a..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineTelephoneNumber.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinetelephonenumber -applicable: Skype for Business Online -title: Remove-CsOnlineTelephoneNumber -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineTelephoneNumber - -## SYNOPSIS -Use the `Remove-CsOnlineTelephoneNumber` cmdlet to remove a telephone number from the Business Voice Directory. - -## SYNTAX - -``` -Remove-CsOnlineTelephoneNumber -TelephoneNumber <String[]> [-Tenant <Guid>] [-DomainController <Fqdn>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOnlineTelephoneNumber -TelephoneNumber +14258884567 -``` - -This example removes the specified telephone number from the Business Voice Directory. - - -## PARAMETERS - -### -TelephoneNumber -Specifies the target telephone number. -For example: -TelephoneNumber tel:+18005551234, or -TelephoneNumber +14251234567 - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -None - -## OUTPUTS - -### -None - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsOnlineVoiceRoute.md b/skype/skype-ps/skype/Remove-CsOnlineVoiceRoute.md deleted file mode 100644 index b62a1e6ca1..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineVoiceRoute.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroute -applicable: Skype for Business Online -title: Get-CsOnlineUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineVoiceRoute - -## SYNOPSIS -Removes an online voice route. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). - -## SYNTAX -``` -Remove-CsOnlineVoiceRoute [-Tenant <Guid>] [[-Identity] <XdsGlobalRelativeIdentity>] [-Force] [-WhatIf] [-Confirm] -``` - -## DESCRIPTION -Use this cmdlet to remove an existing online voice route. Online voice routes are associated with online voice policies through online PSTN usages, so removing an online voice route does not change any values relating to an online voice policy, it simply changes the routing for the numbers that had matched the pattern for the deleted online voice route. - -This cmdlet is used when configuring Microsoft Phone System Direct Routing. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Remove-CsOnlineVoiceRoute -Identity Route1 -``` - -Removes the settings for the online voice route with the identity Route1. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\ Get-CsOnlineVoiceRoute | Remove-CsOnlineVoiceRoute -``` - -This command removes all online voice routes from the organization. First all online voice routes are retrieved by the `Get-CsOnlineVoiceRoute` cmdlet. These online voice routes are then piped to the `Remove-CsOnlineVoiceRoute` cmdlet, which removes each one. - -### -------------------------- Example 3 -------------------------- -``` -PS C:\ Get-CsOnlineVoiceRoute -Filter *Redmond* | Remove-CsOnlineVoiceRoute -``` - -This command removes all online voice routes with an identity that includes the string "Redmond". First the `Get-CsOnlineVoiceRoute` cmdlet is called with the Filter parameter. The value of the Filter parameter is the string Redmond surrounded by wildcard characters (\*), which specifies that the string can be anywhere within the Identity. After all of the online voice routes with identities that include the string Redmond are retrieved, these online voice routes are piped to the `Remove-CsOnlineVoiceRoute` cmdlet, which removes each one. - -## PARAMETERS -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses any confirmation prompts that would otherwise be displayed before making changes. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The unique identity of the online voice route. (If the route name contains a space, such as Test Route, you must enclose the full string in parentheses.) - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroute?view=skype-ps) - -[New-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroute?view=skype-ps) - -[Set-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroute?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsOnlineVoiceRoutingPolicy.md b/skype/skype-ps/skype/Remove-CsOnlineVoiceRoutingPolicy.md deleted file mode 100644 index be01d2e8a8..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineVoiceRoutingPolicy.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroutingpolicy -applicable: Skype for Business Online -title: Get-CsOnlineUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineVoiceRoutingPolicy - -## SYNOPSIS -Deletes an existing online voice routing policy. Online voice routing policies manage online PSTN usages for Phone System users. - -## SYNTAX - -### Identity -``` -Remove-CsOnlineVoiceRoutingPolicy [[-Identity] <XdsIdentity>] [-Tenant <Guid>] [-Force] [-WhatIf] -[-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. - -Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Remove-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -``` - -The command shown in Example 1 deletes the online voice routing policy RedmondOnlineVoiceRoutingPolicy. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoutingPolicy -Filter "tag:*" | Remove-CsOnlineVoiceRoutingPolicy -``` - -In Example 2, all the online voice routing policies configured at the per-user scope are removed. To do this, the command first calls the `Get-CsOnlineVoiceRoutingPolicy` cmdlet along with the Filter parameter; the filter value "tag:\*" limits the returned data to online voice routing policies configured at the per-user scope. Those per-user policies are then piped to and removed by, the `Remove-CsOnlineVoiceRoutingPolicy` cmdlet. - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> Get-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -contains "Long Distance"} | Remove-CsOnlineVoiceRoutingPolicy -``` - -In Example 3, all the online voice routing polices that include the online PSTN usage "Long Distance" are removed. To carry out this task, the `Get-CsOnlineVoiceRoutingPolicy` cmdlet is first called without any parameters in order to return a collection of all the available online voice routing policies. That collection is then piped to the Where-Object cmdlet, which picks out only those policies where the OnlinePstnUsages property includes (-contains) the usage "Long Distance". Policies that meet that criterion are then piped to the `Remove-CsOnlineVoiceRoutingPolicy`, which removes each online voice routing policy that includes the online PSTN usage "Long Distance". - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier assigned to the policy when it was created. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose online voice routing policy is being removed. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[New-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroutingpolicy?view=skype-ps) - -[Get-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroutingpolicy?view=skype-ps) - -[Set-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroutingpolicy?view=skype-ps) - -[Grant-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoiceroutingpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsOnlineVoicemailPolicy.md b/skype/skype-ps/skype/Remove-CsOnlineVoicemailPolicy.md deleted file mode 100644 index 4c143125bd..0000000000 --- a/skype/skype-ps/skype/Remove-CsOnlineVoicemailPolicy.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoicemailpolicy -applicable: Skype for Business Online -title: Remove-CsOnlineVoicemailPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOnlineVoicemailPolicy - -## SYNOPSIS -Deletes an existing Online Voicemail policy. Online Voicemail policies determine whether or not voicemail transcription, profanity masking for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify voicemail maximum recording length for a user. - -## SYNTAX - -``` -Remove-CsOnlineVoicemailPolicy -Identity <XdsIdentity> [-Tenant <Guid>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Online Voicemail service provides organizations with voicemail deposit capabilities for Phone System implementation. - -By default, users enabled for Phone System will be enabled for Online Voicemail, and Online Voicemail policy controls whether or not voicemail transcription, profanity masking for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify voicemail maximum recording length for a user. Online Voicemail transcription is enabled by default, transcription profanity masking is disabled by default, editing call answer rule settings is enabled by default, and voicemail maximum recording length is set to 5 minutes by default. Tenant admin would be able to create customized online voicemail policy to match the organization's requirements. If a online voicemail policy instance is no longer needed, tenant admin could delete it by calling Remove-CsOnlineVoicemailPolicy. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOnlineVoicemailPolicy -Identity "CustomOnlineVoicemailPolicy" -``` - -The command shown in Example 1 deletes a per-user online voicemail policy CustomOnlineVoicemailPolicy. - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier specifying the scope, and in some cases the name, of the policy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the Skype for Business Online tenant account whose voicemail policy is to be retrieved. For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" You can return the tenant ID for each of your tenants by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoicemailpolicy?view=skype-ps) - -[Set-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailpolicy?view=skype-ps) - -[New-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoicemailpolicy?view=skype-ps) - -[Grant-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoicemailpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsOrganizationalAutoAttendant.md b/skype/skype-ps/skype/Remove-CsOrganizationalAutoAttendant.md deleted file mode 100644 index 5067199f33..0000000000 --- a/skype/skype-ps/skype/Remove-CsOrganizationalAutoAttendant.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csorganizationalautoattendant -applicable: Skype for Business Online -title: Remove-CsOrganizationalAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsOrganizationalAutoAttendant - -## SYNOPSIS -Use the Remove-CsOrganizationalAutoAttendant cmdlet to delete an Auto Attendant (AA). - -## SYNTAX - -``` -Remove-CsOrganizationalAutoAttendant [-PrimaryUri] <Uri> [-ApplicationId <Guid>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Remove-CsOrganizationalAutoAttendant cmdlet deletes an OAA that is specified by using the PrimaryUri parameter. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsOrganizationalAutoAttendant -PrimaryUri "sip:mainoaa@contoso.com" -``` - -This example deletes the OAA that has a Primary URI of sip:mainoaa@contoso.com. - - -## PARAMETERS - -### -PrimaryUri -The PrimaryUri parameter represents the SIP address for the OAA to be removed. - - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationId -Specifies a custom application ID to use for OAAs. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### String -The Remove-CsOrganizationalAutoAttendant cmdlet accepts a string as the PrimaryUri parameter. - - -## OUTPUTS - -### None - - -## NOTES - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendant](New-CsOrganizationalAutoAttendant.md) - -[Get-CsOrganizationalAutoAttendant](Get-CsOrganizationalAutoAttendant.md) - -[Set-CsOrganizationalAutoAttendant](Set-CsOrganizationalAutoAttendant.md) diff --git a/skype/skype-ps/skype/Remove-CsOutboundCallingNumberTranslationRule.md b/skype/skype-ps/skype/Remove-CsOutboundCallingNumberTranslationRule.md index fceb1df1d5..340683cf93 100644 --- a/skype/skype-ps/skype/Remove-CsOutboundCallingNumberTranslationRule.md +++ b/skype/skype-ps/skype/Remove-CsOutboundCallingNumberTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csoutboundcallingnumbertranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/remove-csoutboundcallingnumbertranslationrule applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsOutboundCallingNumberTranslationRule schema: 2.0.0 @@ -162,4 +162,3 @@ Instead, the `Remove-CsOutboundCallingNumberTranslationRule` cmdlet deletes exis [New-CsOutboundCallingNumberTranslationRule](New-CsOutboundCallingNumberTranslationRule.md) [Set-CsOutboundCallingNumberTranslationRule](Set-CsOutboundCallingNumberTranslationRule.md) - diff --git a/skype/skype-ps/skype/Remove-CsOutboundTranslationRule.md b/skype/skype-ps/skype/Remove-CsOutboundTranslationRule.md index 34c2aeb2c9..4ead086ae1 100644 --- a/skype/skype-ps/skype/Remove-CsOutboundTranslationRule.md +++ b/skype/skype-ps/skype/Remove-CsOutboundTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csoutboundtranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/remove-csoutboundtranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsOutboundTranslationRule schema: 2.0.0 @@ -147,4 +147,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Tr [Set-CsOutboundTranslationRule](Set-CsOutboundTranslationRule.md) [Get-CsOutboundTranslationRule](Get-CsOutboundTranslationRule.md) - diff --git a/skype/skype-ps/skype/Remove-CsPartnerApplication.md b/skype/skype-ps/skype/Remove-CsPartnerApplication.md index 270f406696..1095f08f13 100644 --- a/skype/skype-ps/skype/Remove-CsPartnerApplication.md +++ b/skype/skype-ps/skype/Remove-CsPartnerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspartnerapplication +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspartnerapplication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPartnerApplication schema: 2.0.0 @@ -186,4 +186,3 @@ Instead, the `Remove-CsPartnerApplication` cmdlet deletes existing instances of [New-CsPartnerApplication](New-CsPartnerApplication.md) [Set-CsPartnerApplication](Set-CsPartnerApplication.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatAddin.md b/skype/skype-ps/skype/Remove-CsPersistentChatAddin.md index 6522701a5a..40d9000d06 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatAddin.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatAddin.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchataddin -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchataddin +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPersistentChatAddin schema: 2.0.0 manager: rogupta @@ -175,4 +175,3 @@ Instead, the `Remove-CsPersistentChatAddin` cmdlet deletes existing instances of [New-CsPersistentChatAddin](New-CsPersistentChatAddin.md) [Set-CsPersistentChatAddin](Set-CsPersistentChatAddin.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatCategory.md b/skype/skype-ps/skype/Remove-CsPersistentChatCategory.md index aca860ec19..658c5fe6a8 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatCategory.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatCategory.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchatcategory -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchatcategory +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPersistentChatCategory schema: 2.0.0 manager: rogupta @@ -164,4 +164,3 @@ Instead, the `Remove-CsPersistentChatCategory` cmdlet deletes existing instances [New-CsPersistentChatCategory](New-CsPersistentChatCategory.md) [Set-CsPersistentChatCategory](Set-CsPersistentChatCategory.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatComplianceConfiguration.md b/skype/skype-ps/skype/Remove-CsPersistentChatComplianceConfiguration.md index fec07c8a29..cfca03a5d7 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatComplianceConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatComplianceConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchatcomplianceconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchatcomplianceconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2015 title: Remove-CsPersistentChatComplianceConfiguration schema: 2.0.0 manager: rogupta @@ -172,4 +172,3 @@ Instead, the `Remove-CsPersistentChatComplianceConfiguration` cmdlet deletes exi [New-CsPersistentChatComplianceConfiguration](New-CsPersistentChatComplianceConfiguration.md) [Set-CsPersistentChatComplianceConfiguration](Set-CsPersistentChatComplianceConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatConfiguration.md b/skype/skype-ps/skype/Remove-CsPersistentChatConfiguration.md index e8824c6b2f..9ad34a8583 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchatconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchatconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPersistentChatConfiguration schema: 2.0.0 manager: rogupta @@ -172,4 +172,3 @@ Instead, the `Remove-CsPersistentChatConfiguration` cmdlet deletes existing inst [New-CsPersistentChatConfiguration](New-CsPersistentChatConfiguration.md) [Set-CsPersistentChatConfiguration](Set-CsPersistentChatConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatEndpoint.md b/skype/skype-ps/skype/Remove-CsPersistentChatEndpoint.md index 18f661deb8..7443eaddef 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatEndpoint.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchatendpoint +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchatendpoint applicable: Lync Server 2013, Skype for Business Server 2015 title: Remove-CsPersistentChatEndpoint schema: 2.0.0 @@ -162,4 +162,3 @@ The `Remove-CsPersistentChatEndpoint` cmdlet does not return objects or data. [Get-CsPersistentChatEndpoint](Get-CsPersistentChatEndpoint.md) [New-CsPersistentChatEndpoint](New-CsPersistentChatEndpoint.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatMessage.md b/skype/skype-ps/skype/Remove-CsPersistentChatMessage.md index 95b702a137..dd1b9a62b1 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatMessage.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatMessage.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchatmessage -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchatmessage +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPersistentChatMessage schema: 2.0.0 manager: rogupta @@ -290,4 +290,3 @@ None. ## RELATED LINKS [Clear-CsPersistentChatRoom](Clear-CsPersistentChatRoom.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatPolicy.md b/skype/skype-ps/skype/Remove-CsPersistentChatPolicy.md index 062d09557f..75517edccd 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatPolicy.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchatpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchatpolicy applicable: Lync Server 2013, Skype for Business Server 2015 title: Remove-CsPersistentChatPolicy schema: 2.0.0 @@ -198,4 +198,3 @@ Instead, the `Remove-CsPersistentChatPolicy` cmdlet deletes existing instances o [New-CsPersistentChatPolicy](New-CsPersistentChatPolicy.md) [Set-CsPersistentChatPolicy](Set-CsPersistentChatPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsPersistentChatRoom.md b/skype/skype-ps/skype/Remove-CsPersistentChatRoom.md index 65af4207b1..d789e263f1 100644 --- a/skype/skype-ps/skype/Remove-CsPersistentChatRoom.md +++ b/skype/skype-ps/skype/Remove-CsPersistentChatRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspersistentchatroom -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspersistentchatroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPersistentChatRoom schema: 2.0.0 manager: rogupta @@ -184,4 +184,3 @@ Instead, the `Remove-CsPersistentChatRoom` cmdlet deletes existing instances of [New-CsPersistentChatRoom](New-CsPersistentChatRoom.md) [Set-CsPersistentChatRoom](Set-CsPersistentChatRoom.md) - diff --git a/skype/skype-ps/skype/Remove-CsPinPolicy.md b/skype/skype-ps/skype/Remove-CsPinPolicy.md index 073b588aac..b50a7851b2 100644 --- a/skype/skype-ps/skype/Remove-CsPinPolicy.md +++ b/skype/skype-ps/skype/Remove-CsPinPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspinpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspinpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPinPolicy schema: 2.0.0 @@ -215,4 +215,3 @@ Instead, the cmdlet removes one or more instances of the Microsoft.Rtc.Managemen [New-CsPinPolicy](New-CsPinPolicy.md) [Set-CsPinPolicy](Set-CsPinPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsPlatformServiceSettings.md b/skype/skype-ps/skype/Remove-CsPlatformServiceSettings.md index 21b2ff06e5..a4f1d6ea41 100644 --- a/skype/skype-ps/skype/Remove-CsPlatformServiceSettings.md +++ b/skype/skype-ps/skype/Remove-CsPlatformServiceSettings.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csplatformservicesettings -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csplatformservicesettings +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPlatformServiceSettings schema: 2.0.0 manager: rogupta @@ -118,8 +118,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[New-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/new-csplatformservicesettings?view=skype-ps) +[New-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/new-csplatformservicesettings?view=skype-ps) -[Get-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/get-csplatformservicesettings?view=skype-ps) +[Get-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/get-csplatformservicesettings?view=skype-ps) -[Set-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/set-csplatformservicesettings?view=skype-ps) +[Set-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/set-csplatformservicesettings?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsPresencePolicy.md b/skype/skype-ps/skype/Remove-CsPresencePolicy.md index 6d886c1bde..7257c10c6d 100644 --- a/skype/skype-ps/skype/Remove-CsPresencePolicy.md +++ b/skype/skype-ps/skype/Remove-CsPresencePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspresencepolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspresencepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPresencePolicy schema: 2.0.0 @@ -204,4 +204,3 @@ Instead, the `Remove-CsPresencePolicy` cmdlet deletes instances of the Microsoft [New-CsPresencePolicy](New-CsPresencePolicy.md) [Set-CsPresencePolicy](Set-CsPresencePolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsPresenceProvider.md b/skype/skype-ps/skype/Remove-CsPresenceProvider.md index fb31290fec..66ad10e6b7 100644 --- a/skype/skype-ps/skype/Remove-CsPresenceProvider.md +++ b/skype/skype-ps/skype/Remove-CsPresenceProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspresenceprovider +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspresenceprovider applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPresenceProvider schema: 2.0.0 @@ -164,4 +164,3 @@ Instead, the `Remove-CsPresenceProvider` cmdlet deletes instances of the Microso [New-CsPresenceProvider](New-CsPresenceProvider.md) [Set-CsPresenceProvider](Set-CsPresenceProvider.md) - diff --git a/skype/skype-ps/skype/Remove-CsPrivacyConfiguration.md b/skype/skype-ps/skype/Remove-CsPrivacyConfiguration.md index 30c2a9d2ea..f0a1d07838 100644 --- a/skype/skype-ps/skype/Remove-CsPrivacyConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsPrivacyConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csprivacyconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csprivacyconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPrivacyConfiguration schema: 2.0.0 @@ -203,4 +203,3 @@ Instead, the `Remove-CsPrivacyConfiguration` cmdlet deletes existing instances o [New-CsPrivacyConfiguration](New-CsPrivacyConfiguration.md) [Set-CsPrivacyConfiguration](Set-CsPrivacyConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsProxyConfiguration.md b/skype/skype-ps/skype/Remove-CsProxyConfiguration.md index 5b406de0a9..fdf06b7833 100644 --- a/skype/skype-ps/skype/Remove-CsProxyConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsProxyConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csproxyconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csproxyconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsProxyConfiguration schema: 2.0.0 @@ -168,4 +168,3 @@ Instead, the `Remove-CsProxyConfiguration` cmdlet deletes existing instances of [New-CsProxyConfiguration](New-CsProxyConfiguration.md) [Set-CsProxyConfiguration](Set-CsProxyConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsPublicProvider.md b/skype/skype-ps/skype/Remove-CsPublicProvider.md index 441097419b..85a18e6544 100644 --- a/skype/skype-ps/skype/Remove-CsPublicProvider.md +++ b/skype/skype-ps/skype/Remove-CsPublicProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspublicprovider +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspublicprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPublicProvider schema: 2.0.0 @@ -170,4 +170,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsPublicProvider](New-CsPublicProvider.md) [Set-CsPublicProvider](Set-CsPublicProvider.md) - diff --git a/skype/skype-ps/skype/Remove-CsPushNotificationConfiguration.md b/skype/skype-ps/skype/Remove-CsPushNotificationConfiguration.md index a22ef311d6..75b54cd946 100644 --- a/skype/skype-ps/skype/Remove-CsPushNotificationConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsPushNotificationConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cspushnotificationconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cspushnotificationconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsPushNotificationConfiguration schema: 2.0.0 manager: rogupta @@ -197,8 +197,8 @@ Instead, the `Remove-CsPushNotificationConfiguration` cmdlet deletes instances o ## NOTES ## RELATED LINKS -[Set-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration?view=skype-ps) +[Set-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration?view=skype-ps) -[New-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/new-cspushnotificationconfiguration?view=skype-ps) +[New-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/new-cspushnotificationconfiguration?view=skype-ps) -[Get-CsPushNotificationConfiguration](https://docs.microsoft.com/powershell/module/skype/get-cspushnotificationconfiguration?view=skype-ps) +[Get-CsPushNotificationConfiguration](https://learn.microsoft.com/powershell/module/skype/get-cspushnotificationconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsQoEConfiguration.md b/skype/skype-ps/skype/Remove-CsQoEConfiguration.md index 0016b3be63..02136f6354 100644 --- a/skype/skype-ps/skype/Remove-CsQoEConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsQoEConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csqoeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csqoeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsQoEConfiguration schema: 2.0.0 @@ -154,4 +154,3 @@ Instead, it removes instances of the Microsoft.Rtc.Management.WritableConfig.Set [Set-CsQoEConfiguration](Set-CsQoEConfiguration.md) [Get-CsQoEConfiguration](Get-CsQoEConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsRegistrarConfiguration.md b/skype/skype-ps/skype/Remove-CsRegistrarConfiguration.md index c79b398607..698ba81e59 100644 --- a/skype/skype-ps/skype/Remove-CsRegistrarConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsRegistrarConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csregistrarconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csregistrarconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsRegistrarConfiguration schema: 2.0.0 @@ -175,4 +175,3 @@ Instead, the `Remove-CsRegistrarConfiguration` cmdlet deletes existing instances [New-CsRegistrarConfiguration](New-CsRegistrarConfiguration.md) [Set-CsRegistrarConfiguration](Set-CsRegistrarConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsReportingConfiguration.md b/skype/skype-ps/skype/Remove-CsReportingConfiguration.md index 60ef8bb506..f39a678c24 100644 --- a/skype/skype-ps/skype/Remove-CsReportingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsReportingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csreportingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csreportingconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsReportingConfiguration schema: 2.0.0 @@ -55,9 +55,12 @@ This collection is then piped to the `Remove-CsReportingConfiguration` cmdlet, w Get-CsReportingConfiguration | Where-Object {$_.ReportingUrl -eq "https://atl-sql-002.litwareinc.com/lync_reports" | Remove-CsReportingConfiguration ``` -The command shown in Example 3 deletes any reporting configuration settings where the reporting URL is set to https://atl-sql-002.litwareinc.com/lync_reports. +The command shown in Example 3 deletes any reporting configuration settings where the reporting URL is set to `https://atl-sql-002.litwareinc.com/lync_reports`. + To carry out this task, the command first uses the `Get-CsReportingConfiguration` cmdlet to return all the reporting configuration settings currently in use. -This collection is then piped to the `Where-Object` cmdlet, which selects only those settings where the ReportingURL property is equal to https://atl-sql-002.litwareinc.com/lync_reports. + +This collection is then piped to the `Where-Object` cmdlet, which selects only those settings where the ReportingURL property is equal to `https://atl-sql-002.litwareinc.com/lync_reports`. + That filtered collection is then piped to the `Remove-CsReportingConfiguration` cmdlet, which removes each item in the collection. @@ -153,4 +156,3 @@ Instead, the `Remove-CsReportingConfiguration` cmdlet deletes existing instances [New-CsReportingConfiguration](New-CsReportingConfiguration.md) [Set-CsReportingConfiguration](Set-CsReportingConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsRgsAgentGroup.md b/skype/skype-ps/skype/Remove-CsRgsAgentGroup.md index 22be51ab23..7062f37fd4 100644 --- a/skype/skype-ps/skype/Remove-CsRgsAgentGroup.md +++ b/skype/skype-ps/skype/Remove-CsRgsAgentGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csrgsagentgroup +online version: https://learn.microsoft.com/powershell/module/skype/remove-csrgsagentgroup applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsRgsAgentGroup schema: 2.0.0 @@ -173,4 +173,3 @@ Microsoft.Rtc.Rgs.Management.WritableSettings.AgentGroup object. [New-CsRgsAgentGroup](New-CsRgsAgentGroup.md) [Set-CsRgsAgentGroup](Set-CsRgsAgentGroup.md) - diff --git a/skype/skype-ps/skype/Remove-CsRgsHolidaySet.md b/skype/skype-ps/skype/Remove-CsRgsHolidaySet.md index b0dd17a42e..65b20debef 100644 --- a/skype/skype-ps/skype/Remove-CsRgsHolidaySet.md +++ b/skype/skype-ps/skype/Remove-CsRgsHolidaySet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csrgsholidayset +online version: https://learn.microsoft.com/powershell/module/skype/remove-csrgsholidayset applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsRgsHolidaySet schema: 2.0.0 @@ -194,4 +194,3 @@ Microsoft.Rtc.Rgs.Management.WritableSettings.HolidaySet object. [New-CsRgsHolidaySet](New-CsRgsHolidaySet.md) [Set-CsRgsHolidaySet](Set-CsRgsHolidaySet.md) - diff --git a/skype/skype-ps/skype/Remove-CsRgsHoursOfBusiness.md b/skype/skype-ps/skype/Remove-CsRgsHoursOfBusiness.md index fe45d3ac03..d9620b6ae4 100644 --- a/skype/skype-ps/skype/Remove-CsRgsHoursOfBusiness.md +++ b/skype/skype-ps/skype/Remove-CsRgsHoursOfBusiness.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csrgshoursofbusiness +online version: https://learn.microsoft.com/powershell/module/skype/remove-csrgshoursofbusiness applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsRgsHoursOfBusiness schema: 2.0.0 @@ -191,4 +191,3 @@ Deletes existing instances of the Microsoft.Rtc.Rgs.Management.WritableSettings. [New-CsRgsHoursOfBusiness](New-CsRgsHoursOfBusiness.md) [Set-CsRgsHoursOfBusiness](Set-CsRgsHoursOfBusiness.md) - diff --git a/skype/skype-ps/skype/Remove-CsRgsQueue.md b/skype/skype-ps/skype/Remove-CsRgsQueue.md index 72552f0ac2..a930605625 100644 --- a/skype/skype-ps/skype/Remove-CsRgsQueue.md +++ b/skype/skype-ps/skype/Remove-CsRgsQueue.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csrgsqueue +online version: https://learn.microsoft.com/powershell/module/skype/remove-csrgsqueue applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsRgsQueue schema: 2.0.0 @@ -177,4 +177,3 @@ Microsoft.Rtc.Rgs.Management.WritableSettings.Queue object. [New-CsRgsQueue](New-CsRgsQueue.md) [Set-CsRgsQueue](Set-CsRgsQueue.md) - diff --git a/skype/skype-ps/skype/Remove-CsRgsWorkflow.md b/skype/skype-ps/skype/Remove-CsRgsWorkflow.md index b885613184..e12c40c092 100644 --- a/skype/skype-ps/skype/Remove-CsRgsWorkflow.md +++ b/skype/skype-ps/skype/Remove-CsRgsWorkflow.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csrgsworkflow +online version: https://learn.microsoft.com/powershell/module/skype/remove-csrgsworkflow applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsRgsWorkflow schema: 2.0.0 @@ -189,4 +189,3 @@ Microsoft.Rtc.Rgs.Management.WritableSettings.Workflow object. [New-CsRgsWorkflow](New-CsRgsWorkflow.md) [Set-CsRgsWorkflow](Set-CsRgsWorkflow.md) - diff --git a/skype/skype-ps/skype/Remove-CsRoutingConfiguration.md b/skype/skype-ps/skype/Remove-CsRoutingConfiguration.md index ac8f69f043..ad76c4dab3 100644 --- a/skype/skype-ps/skype/Remove-CsRoutingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsRoutingConfiguration schema: 2.0.0 @@ -137,4 +137,3 @@ This cmdlet removes (resets) an object of type Microsoft.Rtc.Management.Policy.V [Remove-CsVoiceRoute](Remove-CsVoiceRoute.md) [Get-CsVoiceRoute](Get-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/Remove-CsServerApplication.md b/skype/skype-ps/skype/Remove-CsServerApplication.md index 32b0b43703..a83b20565e 100644 --- a/skype/skype-ps/skype/Remove-CsServerApplication.md +++ b/skype/skype-ps/skype/Remove-CsServerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csserverapplication +online version: https://learn.microsoft.com/powershell/module/skype/remove-csserverapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsServerApplication schema: 2.0.0 @@ -155,4 +155,3 @@ The `Remove-CsServerApplication` cmdlet deletes existing instances of the Micros [New-CsServerApplication](New-CsServerApplication.md) [Set-CsServerApplication](Set-CsServerApplication.md) - diff --git a/skype/skype-ps/skype/Remove-CsSimpleUrlConfiguration.md b/skype/skype-ps/skype/Remove-CsSimpleUrlConfiguration.md index a8d24d0a58..4d7b1655df 100644 --- a/skype/skype-ps/skype/Remove-CsSimpleUrlConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsSimpleUrlConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cssimpleurlconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cssimpleurlconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsSimpleUrlConfiguration schema: 2.0.0 @@ -28,12 +28,12 @@ Remove-CsSimpleUrlConfiguration [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-C ## DESCRIPTION In Microsoft Office Communications Server 2007 R2, meetings had URLs similar to this: -https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t +`https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t` However, such URLs are not especially intuitive, and not easy to convey to someone else. The simple URLs introduced in Lync Server 2010 help overcome those problems by providing users with URLs that look more like this: -https://meet.litwareinc.com/kenmyer/071200 +`https://meet.litwareinc.com/kenmyer/071200` Simple URLs are an improvement over the URLs used in Office Communications Server. However, simple URLs are not automatically created for you; instead, you must configure the URLs yourself. @@ -203,4 +203,3 @@ None. [New-CsSimpleUrlConfiguration](New-CsSimpleUrlConfiguration.md) [Set-CsSimpleUrlConfiguration](Set-CsSimpleUrlConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsSipDomain.md b/skype/skype-ps/skype/Remove-CsSipDomain.md index 01181219cf..d59dc449bb 100644 --- a/skype/skype-ps/skype/Remove-CsSipDomain.md +++ b/skype/skype-ps/skype/Remove-CsSipDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cssipdomain +online version: https://learn.microsoft.com/powershell/module/skype/remove-cssipdomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsSipDomain schema: 2.0.0 @@ -157,4 +157,3 @@ Instead, the `Remove-CsSipDomain` cmdlet deletes existing instance of the Micros [New-CsSipDomain](New-CsSipDomain.md) [Set-CsSipDomain](Set-CsSipDomain.md) - diff --git a/skype/skype-ps/skype/Remove-CsSipResponseCodeTranslationRule.md b/skype/skype-ps/skype/Remove-CsSipResponseCodeTranslationRule.md index 9cf05c6684..6dcccff10c 100644 --- a/skype/skype-ps/skype/Remove-CsSipResponseCodeTranslationRule.md +++ b/skype/skype-ps/skype/Remove-CsSipResponseCodeTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cssipresponsecodetranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/remove-cssipresponsecodetranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsSipResponseCodeTranslationRule schema: 2.0.0 @@ -170,4 +170,3 @@ Instead, the cmdlet deletes modifies instances of the Microsoft.Rtc.Management.W [New-CsSipResponseCodeTranslationRule](New-CsSipResponseCodeTranslationRule.md) [Set-CsSipResponseCodeTranslationRule](Set-CsSipResponseCodeTranslationRule.md) - diff --git a/skype/skype-ps/skype/Remove-CsSlaConfiguration.md b/skype/skype-ps/skype/Remove-CsSlaConfiguration.md index 5c8a7161c1..9cf8fa98a8 100644 --- a/skype/skype-ps/skype/Remove-CsSlaConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsSlaConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csslaconfiguration -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csslaconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsSlaConfiguration schema: 2.0.0 manager: rogupta @@ -118,6 +118,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[Get-CsSlaConfiguration](https://docs.microsoft.com/powershell/module/skype/get-csslaconfiguration?view=skype-ps) +[Get-CsSlaConfiguration](https://learn.microsoft.com/powershell/module/skype/get-csslaconfiguration?view=skype-ps) -[Set-CsSlaConfiguration](https://docs.microsoft.com/powershell/module/skype/set-csslaconfiguration?view=skype-ps) +[Set-CsSlaConfiguration](https://learn.microsoft.com/powershell/module/skype/set-csslaconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsSlaDelegates.md b/skype/skype-ps/skype/Remove-CsSlaDelegates.md index 087f54e6db..66462078dc 100644 --- a/skype/skype-ps/skype/Remove-CsSlaDelegates.md +++ b/skype/skype-ps/skype/Remove-CsSlaDelegates.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cssladelegates -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-cssladelegates +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsSlaDelegates schema: 2.0.0 manager: rogupta @@ -63,16 +63,12 @@ Accept wildcard characters: False ### -Identity Indicates the identity of the shared number to which the delegate will be removed. User identities can be specified using one of five formats: -- SIP address - - Example: sip:kenmyer@litwareinc.com -- User principal name (UPN) - - Example: kenmyer@litwareinc.com -- Domain name and logon name in the form domain\logon - - Example: litwareinc\kenmyer -- Active Directory display name (this form typically requires quotes) - - Example: "Ken Myer" -- Active Directory distinguished name - - Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com + +- SIP address. Example: sip:kenmyer@litwareinc.com. +- User principal name (UPN). Example: kenmyer@litwareinc.com. +- Domain name and logon name in the form domain\logon. Example: litwareinc\kenmyer. +- Active Directory display name (this form typically requires quotes). Example: "Ken Myer". +- Active Directory distinguished name. Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com. ```yaml Type: UserIdParameter @@ -145,4 +141,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[Add-CsSlaDelegates](https://docs.microsoft.com/powershell/module/skype/add-cssladelegates?view=skype-ps) +[Add-CsSlaDelegates](https://learn.microsoft.com/powershell/module/skype/add-cssladelegates?view=skype-ps) diff --git a/skype/skype-ps/skype/Remove-CsStaticRoutingConfiguration.md b/skype/skype-ps/skype/Remove-CsStaticRoutingConfiguration.md index 00f32cb3b0..7c0a317d02 100644 --- a/skype/skype-ps/skype/Remove-CsStaticRoutingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsStaticRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csstaticroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csstaticroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsStaticRoutingConfiguration schema: 2.0.0 @@ -176,4 +176,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsStaticRoutingConfiguration](New-CsStaticRoutingConfiguration.md) [Set-CsStaticRoutingConfiguration](Set-CsStaticRoutingConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsStorageServiceConfiguration.md b/skype/skype-ps/skype/Remove-CsStorageServiceConfiguration.md index 368378bbc1..47b61a9369 100644 --- a/skype/skype-ps/skype/Remove-CsStorageServiceConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsStorageServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csstorageserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csstorageserviceconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsStorageServiceConfiguration schema: 2.0.0 @@ -159,4 +159,3 @@ The `Remove-CsStorageServiceConfiguration` cmdlet does not return any objects or [New-CsStorageServiceConfiguration](New-CsStorageServiceConfiguration.md) [Set-CsStorageServiceConfiguration](Set-CsStorageServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsTeamsAppPermissionPolicy.md b/skype/skype-ps/skype/Remove-CsTeamsAppPermissionPolicy.md deleted file mode 100644 index 78736eb41d..0000000000 --- a/skype/skype-ps/skype/Remove-CsTeamsAppPermissionPolicy.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsapppermissionpolicy -applicable: Skype for Business Online -title: Remove-CsTeamsAppPermissionPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Remove-CsTeamsAppPermissionPolicy - -## SYNOPSIS - -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Permission Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -**We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -This cmdlet allows you to remove app permission policies that have been created within your organization. If you run Remove-CsTeamsAppPermissionPolicy on the Global policy, it will be reset to the defaults provided for new organizations. - -## SYNTAX - -``` -Remove-CsTeamsAppSetupPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Permission Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -**We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -This cmdlet allows you to remove app permission policies that have been created within your organization. If you run Remove-CsTeamsAppPermissionPolicy on the Global policy, it will be reset to the defaults provided for new organizations. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsTeamsAppPermissionPolicy -Identity SalesPolicy -``` - -Deletes a custom policy that has already been created in the organization. - -## PARAMETERS - -### -Identity -Unique identifier for the policy to be removed. -To "remove" the global policy, use the following syntax: `-Identity global`. -(Note that the global policy cannot actually be removed. Instead, all the properties in that policy will be reset to their default values.) To remove a per-user policy, use syntax similar to this: `-Identity "SalesDepartmentPolicy"`. -You cannot use wildcards when specifying a policy Identity. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Force -Suppresses all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsAppSetupPolicy.md b/skype/skype-ps/skype/Remove-CsTeamsAppSetupPolicy.md deleted file mode 100644 index 880db411b5..0000000000 --- a/skype/skype-ps/skype/Remove-CsTeamsAppSetupPolicy.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsappsetuppolicy -applicable: Skype for Business Online -title: Remove-CsTeamsAppSetupPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsTeamsAppSetupPolicy - -## SYNOPSIS - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -**We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## SYNTAX - -``` -Remove-CsTeamsAppSetupPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -**We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -If you run Remove-CsTeamsAppSetupPolicy on the Global policy, it will be reset to the defaults provided for new organizations. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsTeamsAppSetupPolicy -Identity SalesPolicy -``` - -Deletes a custom policy that has already been created in the organization. - -## PARAMETERS - -### -Identity -Unique identifier for the policy to be removed. -To "remove" the global policy, use the following syntax: `-Identity global`. -(Note that the global policy cannot actually be removed. Instead, all the properties in that policy will be reset to their default values.) To remove a per-user policy, use syntax similar to this: `-Identity "SalesDepartmentPolicy"`. -You cannot use wildcards when specifying a policy Identity. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Force -Suppresses all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsChannelsPolicy.md b/skype/skype-ps/skype/Remove-CsTeamsChannelsPolicy.md deleted file mode 100644 index b578abd736..0000000000 --- a/skype/skype-ps/skype/Remove-CsTeamsChannelsPolicy.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamschannelspolicy -applicable: Skype for Business Online -title: Remove-CsTeamsChannelsPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsTeamsChannelsPolicy - -## SYNOPSIS - -The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. - - -## SYNTAX - -``` -Remove-CsTeamsChannelsPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - - -## DESCRIPTION -The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. The Remove-CsTeamsChannelsPolicy cmdlet lets you delete a custom policy that has been configured in your organization. - -If you run Remove-CsTeamsChannelsPolicy on the Global policy, it will be reset to the defaults provided for new organizations. - - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsTeamsChannelsPolicy -Identity SalesPolicy -``` - -Deletes a custom policy that has already been created in the organization. - -## PARAMETERS - - -### -Identity -Unique identifier for the policy to be removed. -To "remove" the global policy, use the following syntax: `-Identity global`. -(Note that the global policy cannot actually be removed. Instead, all the properties in that policy will be reset to their default values.) To remove a per-user policy, use syntax similar to this: `-Identity "StudentPolicy"`. -You cannot use wildcards when specifying a policy Identity. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 2 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Force -Suppresses all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsEmergencyCallRoutingPolicy.md b/skype/skype-ps/skype/Remove-CsTeamsEmergencyCallRoutingPolicy.md deleted file mode 100644 index 6f7e78a8a1..0000000000 --- a/skype/skype-ps/skype/Remove-CsTeamsEmergencyCallRoutingPolicy.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsemergencycallroutingpolicy -applicable: Skype for Business Online -title: Remove-CsTeamsEmergencyCallRoutingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Remove-CsTeamsEmergencyCallRoutingPolicy - -## SYNOPSIS - -## SYNTAX - -``` -Remove-CsTeamsEmergencyCallRoutingPolicy [-Tenant <System.Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet removes an existing Teams Emergency Call Routing policy - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Remove-CsTeamsEmergencyCallRoutingPolicy -Identity TestECRP -``` - - This example removes Teams Emergency Call Routing policy with identity TestECRP - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - The Force parameter suppresses any confirmation prompts that are otherwise displayed before the changes are made. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - The Identity parameter is the unique identifier of the Teams Emergency Call Routing policy to remove. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant - Specifies the tenant id. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsEmergencyCallingPolicy.md b/skype/skype-ps/skype/Remove-CsTeamsEmergencyCallingPolicy.md deleted file mode 100644 index e02248c5ba..0000000000 --- a/skype/skype-ps/skype/Remove-CsTeamsEmergencyCallingPolicy.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsemergencycallingpolicy -applicable: Skype for Business Online -title: Remove-CsTeamsEmergencyCallingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Remove-CsTeamsEmergencyCallingPolicy - -## SYNOPSIS - -## SYNTAX - -``` -Remove-CsTeamsEmergencyCallingPolicy [-Tenant <System.Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet removes an existing Teams Emergency Calling policy. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Remove-CsTeamsEmergencyCallingPolicy -Identity testECP -``` - - This example removes an existing Teams Emergency Calling policy with identity testECRP - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - The Force parameter suppresses any confirmation prompts that are otherwise displayed before the changes are made. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - The Identity parameter is the unique identifier of the Teams Emergency Calling policy to remove. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant - Specifies the tenant id. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsPinnedApp.md b/skype/skype-ps/skype/Remove-CsTeamsPinnedApp.md deleted file mode 100644 index f6211fe064..0000000000 --- a/skype/skype-ps/skype/Remove-CsTeamsPinnedApp.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamspinnedapp -applicable: Skype for Business Online -title: Remove-CsTeamsAppSetupPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsTeamsPinnedApp - -## SYNOPSIS - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - - -## SYNTAX - -## DESCRIPTION - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## EXAMPLES - -### Example 1 -Intentionally not provided - -## 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsTranslationRule.md b/skype/skype-ps/skype/Remove-CsTeamsTranslationRule.md deleted file mode 100644 index 83eecf84d4..0000000000 --- a/skype/skype-ps/skype/Remove-CsTeamsTranslationRule.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamstranslationrule -applicable: Skype for Business Online -title: Remove-CsTeamsTranslationRule -schema: 2.0.0 -manager: nmurav -author: filippse -ms.author: filippse -ms.reviewer: ---- - -# Remove-CsTeamsTranslationRule - -## SYNOPSIS -Cmdlet to remove an existing number manipulation rule (or list of rules). - -## SYNTAX - -``` -Remove-CsTeamsTranslationRule [-Confirm] [-WhatIf] [-Identity <string>] [-Tenant <string>] [-Force] [-AsJob] -``` - -## DESCRIPTION -You can use this cmdlet to remove an existing number manipulation rule (or list of rules). The rule can be used, for example, in the settings of your SBC (Set-CSOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsTeamsTranslationRule -Identity AddPlus1 -``` - -This example removes the "AddPlus1" translation rule. As the rule can be used in some places, integrity check is preformed to ensure that the rule is not in use. If the rule is in use an error thrown with specifying which SBC use this rule. - - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Identifier of the rule. This parameter is required. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose number manipulation rule is being edited. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsUpgradePolicy.md b/skype/skype-ps/skype/Remove-CsTeamsUpgradePolicy.md index 519a6c5f48..f8d9052ec0 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsUpgradePolicy.md +++ b/skype/skype-ps/skype/Remove-CsTeamsUpgradePolicy.md @@ -1,8 +1,8 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml Module Name: SkypeForBusiness -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsupgradepolicy -applicable: Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csteamsupgradepolicy +applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTeamsUpgradePolicy schema: 2.0.0 manager: rogupta @@ -69,7 +69,7 @@ Accept wildcard characters: False ## RELATED LINKS -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) diff --git a/skype/skype-ps/skype/Remove-CsTelemetryConfiguration.md b/skype/skype-ps/skype/Remove-CsTelemetryConfiguration.md index dbb68757a7..ce9b3db03d 100644 --- a/skype/skype-ps/skype/Remove-CsTelemetryConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsTelemetryConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstelemetryconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstelemetryconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTelemetryConfiguration schema: 2.0.0 @@ -141,4 +141,3 @@ None. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsTenantBlockedNumberExceptionPattern.md b/skype/skype-ps/skype/Remove-CsTenantBlockedNumberExceptionPattern.md deleted file mode 100644 index 1601b4f132..0000000000 --- a/skype/skype-ps/skype/Remove-CsTenantBlockedNumberExceptionPattern.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstenantblockednumberexceptionpattern -applicable: Skype for Business Online -title: Remove-CsTenantBlockedNumberExceptionPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# Remove-CsTenantBlockedNumberExceptionPattern - -## SYNOPSIS - -## SYNTAX - -``` -Remove-CsTenantBlockedNumberExceptionPattern [-Tenant <System.Guid>] [-Identity] <XdsGlobalRelativeIdentity> - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 -```powershell -PS C:> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{ Fill Force Description }} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -{{ Fill Identity Description }} - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant -{{ Fill Tenant Description }} - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTenantDialPlan.md b/skype/skype-ps/skype/Remove-CsTenantDialPlan.md deleted file mode 100644 index a89a4940b1..0000000000 --- a/skype/skype-ps/skype/Remove-CsTenantDialPlan.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstenantdialplan -applicable: Skype for Business Online -title: Remove-CsTenantDialPlan -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsTenantDialPlan - -## SYNOPSIS -Use the `Remove-CsTenantDialPlan` cmdlet to remove a tenant dial plan. - -## SYNTAX - -``` -Remove-CsTenantDialPlan [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-CsTenantDialPlan` cmdlet removes an existing tenant dial plan (also known as a location profile). -Tenant dial plans provide required information to allow Enterprise Voice users to make telephone calls. -The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. -A tenant dial plan determines such things as which normalization rules are applied and whether a prefix must be dialed for external calls. - -Removing a tenant dial plan also removes any associated normalization rules. -If no tenant dial plan is assigned to an organization, the Global dial plan is used. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Remove-CsTenantDialPlan -Identity Vt1TenantDialPlan2 -``` - -This example removes the Vt1TenantDialPlan2. - - -## PARAMETERS - -### -Identity -The Identity parameter is the unique identifier of the tenant dial plan to remove. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm parameter prompts you for confirmation before the command is executed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force parameter suppresses any confirmation prompts that are otherwise displayed before the changes are made. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"`. -You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf parameter describes what would happen if you executed the command, without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsTenantNetworkRegion.md b/skype/skype-ps/skype/Remove-CsTenantNetworkRegion.md deleted file mode 100644 index dae8620ba1..0000000000 --- a/skype/skype-ps/skype/Remove-CsTenantNetworkRegion.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstenantnetworkregion -applicable: Skype for Business Online -title: Remove-CsTenantNetworkRegion -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsTenantNetworkRegion - -## SYNOPSIS -Use the `Remove-CsTenantNetworkRegion` cmdlet to remove a tenant network region. - - -## SYNTAX - -``` -Remove-CsTenantNetworkRegion [-Tenant <System.Guid>] [-Identity] <XdsGlobalRelativeIdentity> [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-CsTenantNetworkRegion` cmdlet removes an existing tenant network region. - -A network region contains a collection of network sites. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Remove-CsTenantNetworkRegion -Identity "RedmondRegion" -``` - -The command shown in Example 1 removes 'RedmondRegion'. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network region to be removed. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network regions are being removed. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTenantNetworkSite.md b/skype/skype-ps/skype/Remove-CsTenantNetworkSite.md deleted file mode 100644 index 6a754c2f2e..0000000000 --- a/skype/skype-ps/skype/Remove-CsTenantNetworkSite.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstenantnetworksite -applicable: Skype for Business Online -title: Remove-CsTenantNetworkSite -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsTenantNetworkSite - -## SYNOPSIS -Use the `Remove-CsTenantNetworkSite` cmdlet to remove a tenant network site. - -## SYNTAX - -``` -Remove-CsTenantNetworkSite [-Tenant <System.Guid>] [-Identity] <XdsGlobalRelativeIdentity> [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-CsTenantNetworkSite` cmdlet removes an existing tenant network site. - -A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Remove-CsTenantNetworkSite -Identity "site1" -``` - -The command shown in Example 1 removes 'site1'. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network site to be removed. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network sites are being removed. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTenantNetworkSubnet.md b/skype/skype-ps/skype/Remove-CsTenantNetworkSubnet.md deleted file mode 100644 index a68320a66e..0000000000 --- a/skype/skype-ps/skype/Remove-CsTenantNetworkSubnet.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstenantnetworksubnet -applicable: Skype for Business Online -title: Remove-CsTenantNetworkSubnet -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Remove-CsTenantNetworkSubnet - -## SYNOPSIS -Use the `Remove-CsTenantNetworkSubnet` cmdlet to remove a tenant network subnet. - -## SYNTAX - -``` -Remove-CsTenantNetworkSubnet [-Tenant <System.Guid>] [-Identity] <XdsGlobalRelativeIdentity> [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The `Remove-CsTenantNetworkSubnet` cmdlet removes an existing tenant network subnet. - -IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Remove-CsTenantNetworkSubnet -Identity "192.168.0.1" -``` - -The command shown in Example 1 removes '192.168.0.1'. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network subnet to be removed. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network subnets are being removed. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTenantUpdateTimeWindow.md b/skype/skype-ps/skype/Remove-CsTenantUpdateTimeWindow.md index 6948145cf8..0927a0240a 100644 --- a/skype/skype-ps/skype/Remove-CsTenantUpdateTimeWindow.md +++ b/skype/skype-ps/skype/Remove-CsTenantUpdateTimeWindow.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstenantupdatetimewindow +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstenantupdatetimewindow applicable: Skype for Business Online title: Remove-CsTenantUpdateTimeWindow schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsTenantUpdateTimeWindow @@ -136,4 +136,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsTestDevice.md b/skype/skype-ps/skype/Remove-CsTestDevice.md index ab03c9f688..0cf245979f 100644 --- a/skype/skype-ps/skype/Remove-CsTestDevice.md +++ b/skype/skype-ps/skype/Remove-CsTestDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstestdevice +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstestdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTestDevice schema: 2.0.0 @@ -187,4 +187,3 @@ Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableCo [New-CsTestDevice](New-CsTestDevice.md) [Set-CsTestDevice](Set-CsTestDevice.md) - diff --git a/skype/skype-ps/skype/Remove-CsTestUserCredential.md b/skype/skype-ps/skype/Remove-CsTestUserCredential.md index d693a37093..2d8afa8192 100644 --- a/skype/skype-ps/skype/Remove-CsTestUserCredential.md +++ b/skype/skype-ps/skype/Remove-CsTestUserCredential.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstestusercredential +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstestusercredential applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTestUserCredential schema: 2.0.0 @@ -160,4 +160,3 @@ Instead, the `Remove-CsTestUserCredential` cmdlet deletes existing instances of [Get-CsTestUserCredential](Get-CsTestUserCredential.md) [Set-CsTestUserCredential](Set-CsTestUserCredential.md) - diff --git a/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystem.md b/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystem.md index 3eb14024f2..a55a5ee89b 100644 --- a/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystem.md +++ b/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystem.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csthirdpartyvideosystem +online version: https://learn.microsoft.com/powershell/module/skype/remove-csthirdpartyvideosystem applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsThirdPartyVideoSystem schema: 2.0.0 @@ -137,4 +137,3 @@ The `Remove-CsThirdPartyVideoSystem` cmdlet does not return any objects or data. [New-CsThirdPartyVideoSystem](New-CsThirdPartyVideoSystem.md) [Set-CsThirdPartyVideoSystem](Set-CsThirdPartyVideoSystem.md) - diff --git a/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystemPolicy.md b/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystemPolicy.md index c2f8e8eefd..e2e7dcdc56 100644 --- a/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystemPolicy.md +++ b/skype/skype-ps/skype/Remove-CsThirdPartyVideoSystemPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csthirdpartyvideosystempolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csthirdpartyvideosystempolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsThirdPartyVideoSystemPolicy schema: 2.0.0 @@ -205,4 +205,3 @@ Instead, the `Remove-CsThirdPartyVideoSystemPolicy` cmdlet deletes instances of [New-CsThirdPartyVideoSystemPolicy](New-CsThirdPartyVideoSystemPolicy.md) [Set-CsThirdPartyVideoSystemPolicy](Set-CsThirdPartyVideoSystemPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsTrunkConfiguration.md b/skype/skype-ps/skype/Remove-CsTrunkConfiguration.md index 1016d4eea7..4c863ae2fc 100644 --- a/skype/skype-ps/skype/Remove-CsTrunkConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstrunkconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTrunkConfiguration schema: 2.0.0 @@ -144,4 +144,3 @@ It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Tr [Get-CsTrunkConfiguration](Get-CsTrunkConfiguration.md) [Test-CsTrunkConfiguration](Test-CsTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsTrustedApplication.md b/skype/skype-ps/skype/Remove-CsTrustedApplication.md index 1bcb770b4b..f740667361 100644 --- a/skype/skype-ps/skype/Remove-CsTrustedApplication.md +++ b/skype/skype-ps/skype/Remove-CsTrustedApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstrustedapplication +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstrustedapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTrustedApplication schema: 2.0.0 @@ -150,4 +150,3 @@ It removes an object of type Microsoft.Rtc.Management.Xds.DisplayTrustedApplicat [Set-CsTrustedApplication](Set-CsTrustedApplication.md) [Get-CsTrustedApplication](Get-CsTrustedApplication.md) - diff --git a/skype/skype-ps/skype/Remove-CsTrustedApplicationComputer.md b/skype/skype-ps/skype/Remove-CsTrustedApplicationComputer.md index 1c1c17f968..b98867daaa 100644 --- a/skype/skype-ps/skype/Remove-CsTrustedApplicationComputer.md +++ b/skype/skype-ps/skype/Remove-CsTrustedApplicationComputer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstrustedapplicationcomputer +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstrustedapplicationcomputer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTrustedApplicationComputer schema: 2.0.0 @@ -149,4 +149,3 @@ It removes an object of type Microsoft.Rtc.Management.Xds.DisplayComputer. [Remove-CsTrustedApplicationPool](Remove-CsTrustedApplicationPool.md) [Get-CsTrustedApplicationPool](Get-CsTrustedApplicationPool.md) - diff --git a/skype/skype-ps/skype/Remove-CsTrustedApplicationEndpoint.md b/skype/skype-ps/skype/Remove-CsTrustedApplicationEndpoint.md index 689e989bfc..e90e6d3555 100644 --- a/skype/skype-ps/skype/Remove-CsTrustedApplicationEndpoint.md +++ b/skype/skype-ps/skype/Remove-CsTrustedApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstrustedapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstrustedapplicationendpoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTrustedApplicationEndpoint schema: 2.0.0 @@ -125,4 +125,3 @@ It removes an object of type Microsoft.Rtc.Management.ADConnect.Schema.OCSADAppl [Set-CsTrustedApplicationEndpoint](Set-CsTrustedApplicationEndpoint.md) [Get-CsTrustedApplicationEndpoint](Get-CsTrustedApplicationEndpoint.md) - diff --git a/skype/skype-ps/skype/Remove-CsTrustedApplicationPool.md b/skype/skype-ps/skype/Remove-CsTrustedApplicationPool.md index 19ca3967d8..1d488c17fc 100644 --- a/skype/skype-ps/skype/Remove-CsTrustedApplicationPool.md +++ b/skype/skype-ps/skype/Remove-CsTrustedApplicationPool.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstrustedapplicationpool +online version: https://learn.microsoft.com/powershell/module/skype/remove-cstrustedapplicationpool applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsTrustedApplicationPool schema: 2.0.0 @@ -149,4 +149,3 @@ It removes an object of type Microsoft.Rtc.Management.Xds.DisplayExternalServer. [Set-CsTrustedApplicationPool](Set-CsTrustedApplicationPool.md) [Get-CsTrustedApplicationPool](Get-CsTrustedApplicationPool.md) - diff --git a/skype/skype-ps/skype/Remove-CsUCPhoneConfiguration.md b/skype/skype-ps/skype/Remove-CsUCPhoneConfiguration.md index 39442d4fb6..f45cd01e67 100644 --- a/skype/skype-ps/skype/Remove-CsUCPhoneConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsUCPhoneConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csucphoneconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csucphoneconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsUCPhoneConfiguration schema: 2.0.0 @@ -188,4 +188,3 @@ Instead, the cmdlet removes instances of the Microsoft.Rtc.Management.WritableCo [New-CsUCPhoneConfiguration](New-CsUCPhoneConfiguration.md) [Set-CsUCPhoneConfiguration](Set-CsUCPhoneConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsUnassignedNumber.md b/skype/skype-ps/skype/Remove-CsUnassignedNumber.md index e06fba8054..76c0291f9f 100644 --- a/skype/skype-ps/skype/Remove-CsUnassignedNumber.md +++ b/skype/skype-ps/skype/Remove-CsUnassignedNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csunassignednumber +online version: https://learn.microsoft.com/powershell/module/skype/remove-csunassignednumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsUnassignedNumber schema: 2.0.0 @@ -145,4 +145,3 @@ It removes an object of type Microsoft.Rtc.Management.Voice.Helpers.DisplayAnnou [Get-CsAnnouncement](Get-CsAnnouncement.md) [Get-CsExUmContact](Get-CsExUmContact.md) - diff --git a/skype/skype-ps/skype/Remove-CsUserAcp.md b/skype/skype-ps/skype/Remove-CsUserAcp.md index f022b473b0..dc022a2e7e 100644 --- a/skype/skype-ps/skype/Remove-CsUserAcp.md +++ b/skype/skype-ps/skype/Remove-CsUserAcp.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csuseracp -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csuseracp +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsUserAcp schema: 2.0.0 manager: bulenteg @@ -21,10 +21,12 @@ This cmdlet was introduced in Lync Server 2010. ``` Remove-CsUserAcp [-Identity] <UserIdParameter> [-Name <String>] [-TollNumber <String>] [-PassThru] [-WhatIf] - [-Confirm] [-ParticipantPasscode <String>] [-AsJob] [<CommonParameters>] + [-Confirm] [-ParticipantPasscode <String>] [<CommonParameters>] ``` ## DESCRIPTION +Deprecation Notice: Integration of Skype for Business with third-party audio conferencing providers has been retired. More details are here - https://learn.microsoft.com/skypeforbusiness/legal-and-regulatory/end-of-integration-with-3rd-party-providers. As a result, cmdlet no longer works. + An audio conferencing provider is a third-party company that provides organizations with conferencing services. Among other things, audio conferencing providers provide a way for users located off site and not connected to the corporate network or the Internet, to participate in the audio portion of a conference or meeting. Audio conferencing providers often provide high-end services such as live translation, transcription, and live per-conference operator assistance. @@ -221,22 +223,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -259,4 +245,3 @@ None. [Get-CsUserAcp](Get-CsUserAcp.md) [Set-CsUserAcp](Set-CsUserAcp.md) - diff --git a/skype/skype-ps/skype/Remove-CsUserReplicatorConfiguration.md b/skype/skype-ps/skype/Remove-CsUserReplicatorConfiguration.md index e7b6480691..1c2fa5fc3f 100644 --- a/skype/skype-ps/skype/Remove-CsUserReplicatorConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsUserReplicatorConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csuserreplicatorconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csuserreplicatorconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsUserReplicatorConfiguration schema: 2.0.0 @@ -162,4 +162,3 @@ Instead, the `Remove-CsUserReplicatorConfiguration` cmdlet deletes instances of [New-CsUserReplicatorConfiguration](New-CsUserReplicatorConfiguration.md) [Set-CsUserReplicatorConfiguration](Set-CsUserReplicatorConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsUserServicesConfiguration.md b/skype/skype-ps/skype/Remove-CsUserServicesConfiguration.md index a7d0a44344..373e6cace5 100644 --- a/skype/skype-ps/skype/Remove-CsUserServicesConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsUserServicesConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csuserservicesconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csuserservicesconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsUserServicesConfiguration schema: 2.0.0 @@ -170,4 +170,3 @@ Instead, the `Remove-CsUserServicesConfiguration` cmdlet deletes existing instan [New-CsUserServicesConfiguration](New-CsUserServicesConfiguration.md) [Set-CsUserServicesConfiguration](Set-CsUserServicesConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsUserServicesPolicy.md b/skype/skype-ps/skype/Remove-CsUserServicesPolicy.md index 6600ffcb40..b5402b89cb 100644 --- a/skype/skype-ps/skype/Remove-CsUserServicesPolicy.md +++ b/skype/skype-ps/skype/Remove-CsUserServicesPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csuserservicespolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csuserservicespolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsUserServicesPolicy schema: 2.0.0 @@ -199,4 +199,3 @@ Instead, the `Remove-CsUserServicesPolicy` cmdlet deletes existing instances of [New-CsUserServicesPolicy](New-CsUserServicesPolicy.md) [Set-CsUserServicesPolicy](Set-CsUserServicesPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsUserStoreBackupData.md b/skype/skype-ps/skype/Remove-CsUserStoreBackupData.md index fb8676737c..a03b9546bf 100644 --- a/skype/skype-ps/skype/Remove-CsUserStoreBackupData.md +++ b/skype/skype-ps/skype/Remove-CsUserStoreBackupData.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csuserstorebackupdata +online version: https://learn.microsoft.com/powershell/module/skype/remove-csuserstorebackupdata applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsUserStoreBackupData schema: 2.0.0 @@ -135,4 +135,3 @@ None. ## RELATED LINKS [Get-CsBackupServiceStatus](Get-CsBackupServiceStatus.md) - diff --git a/skype/skype-ps/skype/Remove-CsVideoInteropServerConfiguration.md b/skype/skype-ps/skype/Remove-CsVideoInteropServerConfiguration.md index e651be10a3..3aebb35e96 100644 --- a/skype/skype-ps/skype/Remove-CsVideoInteropServerConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsVideoInteropServerConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvideointeropserverconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvideointeropserverconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVideoInteropServerConfiguration schema: 2.0.0 @@ -170,4 +170,3 @@ The `Remove-CsVideoInteropServerConfiguration` cmdlet deletes instances of the M [New-CsVideoInteropServerConfiguration](New-CsVideoInteropServerConfiguration.md) [Set-CsVideoInteropServerConfiguration](Set-CsVideoInteropServerConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md b/skype/skype-ps/skype/Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md index fcd996af0e..c5fe430c83 100644 --- a/skype/skype-ps/skype/Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvideointeropserversynthetictransactionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvideointeropserversynthetictransactionconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVideoInteropServerSyntheticTransactionConfiguration schema: 2.0.0 @@ -135,4 +135,3 @@ None [New-CsVideoInteropServerSyntheticTransactionConfiguration](New-CsVideoInteropServerSyntheticTransactionConfiguration.md) [Test-CsP2PVideoInteropServerSipTrunkAV](Test-CsP2PVideoInteropServerSipTrunkAV.md) - diff --git a/skype/skype-ps/skype/Remove-CsVideoTrunkConfiguration.md b/skype/skype-ps/skype/Remove-CsVideoTrunkConfiguration.md index 10a7e54ad7..820a5f657f 100644 --- a/skype/skype-ps/skype/Remove-CsVideoTrunkConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsVideoTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvideotrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvideotrunkconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVideoTrunkConfiguration schema: 2.0.0 @@ -28,7 +28,7 @@ The VIS is a service that runs on a standalone pool and cannot be co-located on To enable the Video Interop Server, you must use Topology Builder to define at least one VIS instance. Each VIS instance will typically be associated with one or more Video Gateways. -Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from an third party PBX supporting 3rd party video teleconferencing systems (VTCs). +Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from a third party PBX supporting 3rd party video teleconferencing systems (VTCs). The Video Gateway and a Video Interop Server (VIS) use a Session Initiation Protocol (SIP) trunk to connect video calls between third party VTCs and internal endpoints. Video Trunks settings can be managed by using the CsVideoTrunkConfiguration cmdlets. @@ -162,4 +162,3 @@ The `Remove-CsVideoTrunkConfiguration` cmdlet removes specified Microsoft.Rtc.Ma [New-CsVideoTrunkConfiguration](New-CsVideoTrunkConfiguration.md) [Set-CsVideoTrunkConfiguration](Set-CsVideoTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsVoiceConfiguration.md b/skype/skype-ps/skype/Remove-CsVoiceConfiguration.md index 23ce50a0b4..ce31f612a4 100644 --- a/skype/skype-ps/skype/Remove-CsVoiceConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsVoiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvoiceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvoiceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVoiceConfiguration schema: 2.0.0 @@ -136,4 +136,3 @@ This cmdlet removes (resets) an object of type Microsoft.Rtc.Management.Writable [Remove-CsVoiceTestConfiguration](Remove-CsVoiceTestConfiguration.md) [Get-CsVoiceTestConfiguration](Get-CsVoiceTestConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsVoiceNormalizationRule.md b/skype/skype-ps/skype/Remove-CsVoiceNormalizationRule.md index dc189bbcae..4513a469fb 100644 --- a/skype/skype-ps/skype/Remove-CsVoiceNormalizationRule.md +++ b/skype/skype-ps/skype/Remove-CsVoiceNormalizationRule.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvoicenormalizationrule -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvoicenormalizationrule +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVoiceNormalizationRule schema: 2.0.0 manager: bulenteg @@ -17,12 +17,12 @@ Removes a voice normalization rule. Voice normalization rules are used to convert telephone dialing requirements (for example, dialing 9 to access an outside line) to the E.164 phone number format used by Skype for Business Server. This cmdlet was introduced in Lync Server 2010. +**Note**: This cmdlet has been deprecated in Teams PowerShell Module 4.0.0. ## SYNTAX ``` -Remove-CsVoiceNormalizationRule [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] +Remove-CsVoiceNormalizationRule [-Identity] <XdsIdentity> [-Tenant <guid>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION @@ -65,7 +65,7 @@ If the value passed to the Identity contains only the scope (site:Redmond), all Type: XdsIdentity Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: True Position: 2 @@ -82,7 +82,7 @@ Suppresses any confirmation prompts that would otherwise be displayed before mak Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -99,7 +99,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -116,7 +116,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -126,13 +126,13 @@ Accept wildcard characters: False ``` ### -Tenant -This parameter is reserved for internal Microsoft use. +For internal Microsoft usage. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -170,4 +170,3 @@ This cmdlet deletes an object of type Microsoft.Rtc.Management.WritableConfig.Po [Remove-CsDialPlan](Remove-CsDialPlan.md) [Get-CsDialPlan](Get-CsDialPlan.md) - diff --git a/skype/skype-ps/skype/Remove-CsVoicePolicy.md b/skype/skype-ps/skype/Remove-CsVoicePolicy.md index 8bdfbebceb..137f719863 100644 --- a/skype/skype-ps/skype/Remove-CsVoicePolicy.md +++ b/skype/skype-ps/skype/Remove-CsVoicePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvoicepolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvoicepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVoicePolicy schema: 2.0.0 @@ -169,4 +169,3 @@ It removes an instance of a Microsoft.Rtc.Management.WritableConfig.Policy.Voice [Grant-CsVoicePolicy](Grant-CsVoicePolicy.md) [Test-CsVoicePolicy](Test-CsVoicePolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsVoiceRoute.md b/skype/skype-ps/skype/Remove-CsVoiceRoute.md index ebb7f6cbb6..97f01579c4 100644 --- a/skype/skype-ps/skype/Remove-CsVoiceRoute.md +++ b/skype/skype-ps/skype/Remove-CsVoiceRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvoiceroute +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvoiceroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVoiceRoute schema: 2.0.0 @@ -151,4 +151,3 @@ Removes an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Voice.R [Get-CsVoiceRoute](Get-CsVoiceRoute.md) [Test-CsVoiceRoute](Test-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/Remove-CsVoiceRoutingPolicy.md b/skype/skype-ps/skype/Remove-CsVoiceRoutingPolicy.md index 92ea588fbf..2d439ee40e 100644 --- a/skype/skype-ps/skype/Remove-CsVoiceRoutingPolicy.md +++ b/skype/skype-ps/skype/Remove-CsVoiceRoutingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvoiceroutingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvoiceroutingpolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVoiceRoutingPolicy schema: 2.0.0 @@ -173,4 +173,3 @@ Instead, the `Remove-CsVoiceRoutingPolicy` cmdlet deletes existing instances of [New-CsVoiceRoutingPolicy](New-CsVoiceRoutingPolicy.md) [Set-CsVoiceRoutingPolicy](Set-CsVoiceRoutingPolicy.md) - diff --git a/skype/skype-ps/skype/Remove-CsVoiceTestConfiguration.md b/skype/skype-ps/skype/Remove-CsVoiceTestConfiguration.md index 6d4193d3a4..0a7f3baca9 100644 --- a/skype/skype-ps/skype/Remove-CsVoiceTestConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsVoiceTestConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvoicetestconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvoicetestconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVoiceTestConfiguration schema: 2.0.0 @@ -140,4 +140,3 @@ Removes an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Voice.T [Get-CsVoiceTestConfiguration](Get-CsVoiceTestConfiguration.md) [Test-CsVoiceTestConfiguration](Test-CsVoiceTestConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsVoicemailReroutingConfiguration.md b/skype/skype-ps/skype/Remove-CsVoicemailReroutingConfiguration.md index f5dafcf04c..9a5d3a1dfd 100644 --- a/skype/skype-ps/skype/Remove-CsVoicemailReroutingConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsVoicemailReroutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvoicemailreroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-csvoicemailreroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsVoicemailReroutingConfiguration schema: 2.0.0 @@ -145,4 +145,3 @@ Removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.ExumR [Set-CsVoicemailReroutingConfiguration](Set-CsVoicemailReroutingConfiguration.md) [Get-CsVoicemailReroutingConfiguration](Get-CsVoicemailReroutingConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsWatcherNodeConfiguration.md b/skype/skype-ps/skype/Remove-CsWatcherNodeConfiguration.md index a6fdab30ef..e6ad98fce0 100644 --- a/skype/skype-ps/skype/Remove-CsWatcherNodeConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsWatcherNodeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cswatchernodeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cswatchernodeconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsWatcherNodeConfiguration schema: 2.0.0 @@ -163,4 +163,3 @@ Instead, the `Remove-CsWatcherNodeConfiguration` cmdlet deletes existing instanc [Set-CsWatcherNodeConfiguration](Set-CsWatcherNodeConfiguration.md) [Test-CsWatcherNodeConfiguration](Test-CsWatcherNodeConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsWebServiceConfiguration.md b/skype/skype-ps/skype/Remove-CsWebServiceConfiguration.md index 65271bfc91..11ae5b1038 100644 --- a/skype/skype-ps/skype/Remove-CsWebServiceConfiguration.md +++ b/skype/skype-ps/skype/Remove-CsWebServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cswebserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/remove-cswebserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsWebServiceConfiguration schema: 2.0.0 @@ -175,4 +175,3 @@ Instead, the `Remove-CsWebServiceConfiguration` cmdlet deletes existing instance [New-CsWebServiceConfiguration](New-CsWebServiceConfiguration.md) [Set-CsWebServiceConfiguration](Set-CsWebServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Remove-CsXmppAllowedPartner.md b/skype/skype-ps/skype/Remove-CsXmppAllowedPartner.md index c7a0e1c191..fabbb2d393 100644 --- a/skype/skype-ps/skype/Remove-CsXmppAllowedPartner.md +++ b/skype/skype-ps/skype/Remove-CsXmppAllowedPartner.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csxmppallowedpartner -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/remove-csxmppallowedpartner +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Remove-CsXmppAllowedPartner schema: 2.0.0 manager: rogupta @@ -161,4 +161,3 @@ Instead, the `Remove-CsXmppAllowedPartner` cmdlet deletes existing instances of [New-CsXmppAllowedPartner](New-CsXmppAllowedPartner.md) [Set-CsXmppAllowedPartner](Set-CsXmppAllowedPartner.md) - diff --git a/skype/skype-ps/skype/Request-CsCertificate.md b/skype/skype-ps/skype/Request-CsCertificate.md index ce03acc87d..56a2d03fd8 100644 --- a/skype/skype-ps/skype/Request-CsCertificate.md +++ b/skype/skype-ps/skype/Request-CsCertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/request-cscertificate +online version: https://learn.microsoft.com/powershell/module/skype/request-cscertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Request-CsCertificate schema: 2.0.0 @@ -98,7 +98,7 @@ Example 3 uses the Output parameter to create an offline certificate request. ### -------------------------- Example 4 ----------------------- ``` -Request-CsCertificate -New -Type Default,WebServicesInternal,WebServicesExternal -ComputerFqdn "atl-cs-001.litwareinc.com" -CA "atl-ca-001.litwareinc.com\myca" -FriendlyName "Standard Edition Certficate" -Template jcila -PrivateKeyExportable $True -DomainName "atl-cs-001.litwareinc.com,atl-ext.litwareinc.com" +Request-CsCertificate -New -Type Default,WebServicesInternal,WebServicesExternal -ComputerFqdn "atl-cs-001.litwareinc.com" -CA "atl-ca-001.litwareinc.com\myca" -FriendlyName "Standard Edition Certificate" -Template jcila -PrivateKeyExportable $True -DomainName "atl-cs-001.litwareinc.com,atl-ext.litwareinc.com" ``` Example 4 is a more detailed (and more realistic) example of how to use the `Request-CsCertificate` cmdlet. @@ -725,4 +725,3 @@ Instead, the `Request-CsCertificate` cmdlet helps manage instances of the Micros [Remove-CsCertificate](Remove-CsCertificate.md) [Set-CsCertificate](Set-CsCertificate.md) - diff --git a/skype/skype-ps/skype/Reset-CsDeviceUpdateRule.md b/skype/skype-ps/skype/Reset-CsDeviceUpdateRule.md index 73507493ba..70da9753fa 100644 --- a/skype/skype-ps/skype/Reset-CsDeviceUpdateRule.md +++ b/skype/skype-ps/skype/Reset-CsDeviceUpdateRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/reset-csdeviceupdaterule +online version: https://learn.microsoft.com/powershell/module/skype/reset-csdeviceupdaterule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Reset-CsDeviceUpdateRule schema: 2.0.0 @@ -193,4 +193,3 @@ Instead, the `Reset-CsDeviceUpdateRule` cmdlet resets instances of the Microsoft [Remove-CsDeviceUpdateRule](Remove-CsDeviceUpdateRule.md) [Restore-CsDeviceUpdateRule](Restore-CsDeviceUpdateRule.md) - diff --git a/skype/skype-ps/skype/Reset-CsNotificationQueues.md b/skype/skype-ps/skype/Reset-CsNotificationQueues.md index 56d79db5ff..dff712feba 100644 --- a/skype/skype-ps/skype/Reset-CsNotificationQueues.md +++ b/skype/skype-ps/skype/Reset-CsNotificationQueues.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/reset-csnotificationqueues +online version: https://learn.microsoft.com/powershell/module/skype/reset-csnotificationqueues applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Reset-CsNotificationQueues schema: 2.0.0 @@ -113,4 +113,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Reset-CsPoolRegistrarState.md b/skype/skype-ps/skype/Reset-CsPoolRegistrarState.md index 9ca7cb1ab3..db9733ae64 100644 --- a/skype/skype-ps/skype/Reset-CsPoolRegistrarState.md +++ b/skype/skype-ps/skype/Reset-CsPoolRegistrarState.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/reset-cspoolregistrarstate +online version: https://learn.microsoft.com/powershell/module/skype/reset-cspoolregistrarstate applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Reset-CsPoolRegistrarState schema: 2.0.0 @@ -289,4 +289,3 @@ The `Reset-CsPoolRegistrarState` cmdlet does not return objects. ## RELATED LINKS [Get-CsPoolFabricState](Get-CsPoolFabricState.md) - diff --git a/skype/skype-ps/skype/Reset-CsRoutingGroup.md b/skype/skype-ps/skype/Reset-CsRoutingGroup.md index 093d69ff9d..af1ce598f9 100644 --- a/skype/skype-ps/skype/Reset-CsRoutingGroup.md +++ b/skype/skype-ps/skype/Reset-CsRoutingGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/reset-csroutinggroup +online version: https://learn.microsoft.com/powershell/module/skype/reset-csroutinggroup applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Reset-CsRoutingGroup schema: 2.0.0 @@ -211,4 +211,3 @@ The `Reset-CsRoutingGroup` cmdlet does return objects or data. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Restore-CsDeviceUpdateRule.md b/skype/skype-ps/skype/Restore-CsDeviceUpdateRule.md index f8427615d2..2bff596090 100644 --- a/skype/skype-ps/skype/Restore-CsDeviceUpdateRule.md +++ b/skype/skype-ps/skype/Restore-CsDeviceUpdateRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/restore-csdeviceupdaterule +online version: https://learn.microsoft.com/powershell/module/skype/restore-csdeviceupdaterule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Restore-CsDeviceUpdateRule schema: 2.0.0 @@ -196,4 +196,3 @@ Instead, the `Restore-CsDeviceUpdateRule` cmdlet restores instances of the Micro [Remove-CsDeviceUpdateRule](Remove-CsDeviceUpdateRule.md) [Reset-CsDeviceUpdateRule](Reset-CsDeviceUpdateRule.md) - diff --git a/skype/skype-ps/skype/Revoke-CsClientCertificate.md b/skype/skype-ps/skype/Revoke-CsClientCertificate.md index 3f187ee6d3..5b2828745f 100644 --- a/skype/skype-ps/skype/Revoke-CsClientCertificate.md +++ b/skype/skype-ps/skype/Revoke-CsClientCertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/revoke-csclientcertificate +online version: https://learn.microsoft.com/powershell/module/skype/revoke-csclientcertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Revoke-CsClientCertificate schema: 2.0.0 @@ -150,4 +150,3 @@ Instead, the `Revoke-CsClientCertificate` cmdlet revokes instances of the Micros ## RELATED LINKS [Get-CsClientCertificate](Get-CsClientCertificate.md) - diff --git a/skype/skype-ps/skype/Revoke-CsOUPermission.md b/skype/skype-ps/skype/Revoke-CsOUPermission.md index 62b4bdafb8..e78386a8cd 100644 --- a/skype/skype-ps/skype/Revoke-CsOUPermission.md +++ b/skype/skype-ps/skype/Revoke-CsOUPermission.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/revoke-csoupermission +online version: https://learn.microsoft.com/powershell/module/skype/revoke-csoupermission applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Revoke-CsOUPermission schema: 2.0.0 @@ -250,4 +250,3 @@ The `Revoke-CsOUPermission` cmdlet does not return any objects or values. [Grant-CsOUPermission](Grant-CsOUPermission.md) [Test-CsOUPermission](Test-CsOUPermission.md) - diff --git a/skype/skype-ps/skype/Revoke-CsSetupPermission.md b/skype/skype-ps/skype/Revoke-CsSetupPermission.md index f06ed2ba38..2749dcce16 100644 --- a/skype/skype-ps/skype/Revoke-CsSetupPermission.md +++ b/skype/skype-ps/skype/Revoke-CsSetupPermission.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/revoke-cssetuppermission +online version: https://learn.microsoft.com/powershell/module/skype/revoke-cssetuppermission applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Revoke-CsSetupPermission schema: 2.0.0 @@ -223,4 +223,3 @@ None. [Grant-CsSetupPermission](Grant-CsSetupPermission.md) [Test-CsSetupPermission](Test-CsSetupPermission.md) - diff --git a/skype/skype-ps/skype/Search-CsClsLogging.md b/skype/skype-ps/skype/Search-CsClsLogging.md index 46180400bb..012dcf1d84 100644 --- a/skype/skype-ps/skype/Search-CsClsLogging.md +++ b/skype/skype-ps/skype/Search-CsClsLogging.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/search-csclslogging +online version: https://learn.microsoft.com/powershell/module/skype/search-csclslogging applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Search-CsClsLogging schema: 2.0.0 @@ -430,4 +430,3 @@ String values or XML. [Sync-CsClsLogging](Sync-CsClsLogging.md) [Update-CsClsLogging](Update-CsClsLogging.md) - diff --git a/skype/skype-ps/skype/Search-CsOnlineTelephoneNumberInventory.md b/skype/skype-ps/skype/Search-CsOnlineTelephoneNumberInventory.md deleted file mode 100644 index 61452c7baf..0000000000 --- a/skype/skype-ps/skype/Search-CsOnlineTelephoneNumberInventory.md +++ /dev/null @@ -1,247 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/search-csonlinetelephonenumberinventory -applicable: Skype for Business Online -title: Search-CsOnlineTelephoneNumberInventory -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Search-CsOnlineTelephoneNumberInventory - -## SYNOPSIS -Use the `Search-CsOnlineTelephoneNumberInventory` cmdlet to reserve a telephone numbers that are in inventory and available to be acquired. - -## SYNTAX - -``` -Search-CsOnlineTelephoneNumberInventory [-Tenant <Guid>] -RegionalGroup <String> - -CountryOrRegion <String> -Area <String> -CapitalOrMajorCity <String> -Quantity <Int32> - [-TelephoneNumber <String>] [-AreaCode <String>] -InventoryType <String> [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -## DESCRIPTION -Acquiring tenant telephone numbers is a two step process. - -+12127539059 +1 (212) 753 9059 - -`Select-CsOnlineTelephoneNumberInventory -ReservationId 76ce711f-9da4-46d9-b81d-471172450443 -TelephoneNumbers 12127539058,12127539059 -Region NOAM -Country US -Area NY -City NY` - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Search-CsOnlineTelephoneNumberInventory -InventoryType Service -Region NOAM -Country US -Area NY -City NY -Quantity 10 -``` - -This example reserves 10 Service type telephone numbers in New York, New York. - - -## PARAMETERS - -### -Area -Specifies the target geographical area for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CapitalOrMajorCity -Specifies the target geographical city for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: City -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the target country for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Country -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InventoryType -Specifies the target telephone number type for the cmdlet. -Acceptable values are: - -"Service" for numbers assigned to conferencing support. - -"Subscriber" for numbers supporting public switched telephone network (PSTN) functions. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Quantity -Specifies the quantity of telephone numbers to reserve. -The maximum value is 500. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionalGroup -Specifies the target geographical region for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Region -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AreaCode -Specifies the area code to search for telephone numbers. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumber -Specifies either an individual telephone number to reserve, or multiple telephone numbers can be entered separated by a comma. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies your tenant identifier. -To find your tenant id use the command: `Get-CsTenant | fl objectid`. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -None - -## OUTPUTS - -### -This cmdlets returns an Microsoft.Rtc.Management.Hosted.Bvd.Types.NumberReservationResponse object. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Select-CsOnlineTelephoneNumberInventory.md b/skype/skype-ps/skype/Select-CsOnlineTelephoneNumberInventory.md deleted file mode 100644 index d51261995e..0000000000 --- a/skype/skype-ps/skype/Select-CsOnlineTelephoneNumberInventory.md +++ /dev/null @@ -1,233 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/select-csonlinetelephonenumberinventory -applicable: Skype for Business Online -title: Select-CsOnlineTelephoneNumberInventory -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Select-CsOnlineTelephoneNumberInventory - -## SYNOPSIS -Use the `Select-CsOnlineTelephoneNumberInventory` cmdlet to acquire a list of inventoried telephone numbers and associate them with a Business Voice Directory tenant. -The input must be from a telephone number search operation generated by the `Search-CsOnlineTelephoneNumberInventory` cmdlet. - -## SYNTAX - -``` -Select-CsOnlineTelephoneNumberInventory [-Tenant <Guid>] -RegionalGroup <String> - -CountryOrRegion <String> -Area <String> -CapitalOrMajorCity <String> -ReservationId <String> - -TelephoneNumbers <String[]> [-LocationId <Guid>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -## DESCRIPTION -Acquiring tenant telephone numbers is a two step process. - -+12127539059 +1 (212) 753 9059 - -`Select-CsOnlineTelephoneNumberInventory -ReservationId 76ce711f-9da4-46d9-b81d-471172450443 -TelephoneNumbers 12127539058,12127539059 -RegionalGroup NOAM -CountryOrRegion US -Area NY -CapitalOrMajorCity NY` - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Select-CsOnlineTelephoneNumberInventory -ReservationId 76ce711f-9da4-46d9-b81d-471172450443 -TelephoneNumbers 12127539058,12127539059 -RegionalGroup NOAM -CountryOrRegion US -Area NY -CapitalOrMajorCity NY -``` - -This example assigns two telephone numbers to New York City. - -## PARAMETERS - -### -Area -Specifies the target geographical area for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CapitalOrMajorCity -Specifies the target geographical city for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: City -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the target country for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Country -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RegionalGroup -Specifies the target geographical region for the cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: Region -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReservationId -Specifies the telephone number reservation to access. -The reservation itself is created by the `Search-CsOnlineTelephoneNumberInventory` cmdlet. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumbers -Specifies the telephone numbers you wish to assign, separated by commas. -The numbers must be in E.164 format. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Specifies the domain controller that's used by the cmdlet to read or write the specified data. -Valid inputs for this parameter are either the fully qualified domain name (FQDN) or the computer name. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"`. -You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -None - -## OUTPUTS - -### -This cmdlets returns an Microsoft.Rtc.Management.Hosted.Bvd.Types.NumberReservationResponse object. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsAVEdgeConfiguration.md b/skype/skype-ps/skype/Set-CsAVEdgeConfiguration.md index 1305c1f2c2..32085367bd 100644 --- a/skype/skype-ps/skype/Set-CsAVEdgeConfiguration.md +++ b/skype/skype-ps/skype/Set-CsAVEdgeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csavedgeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csavedgeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAVEdgeConfiguration schema: 2.0.0 @@ -222,4 +222,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsAVEdgeConfiguration](New-CsAVEdgeConfiguration.md) [Remove-CsAVEdgeConfiguration](Remove-CsAVEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsAccessEdgeConfiguration.md b/skype/skype-ps/skype/Set-CsAccessEdgeConfiguration.md index 9ac552a311..a8885119cb 100644 --- a/skype/skype-ps/skype/Set-CsAccessEdgeConfiguration.md +++ b/skype/skype-ps/skype/Set-CsAccessEdgeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csaccessedgeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csaccessedgeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAccessEdgeConfiguration schema: 2.0.0 @@ -659,4 +659,3 @@ The `Set-CsAccessEdgeConfiguration` cmdlet does not return any objects or values ## RELATED LINKS [Get-CsAccessEdgeConfiguration](Get-CsAccessEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsAddressBookConfiguration.md b/skype/skype-ps/skype/Set-CsAddressBookConfiguration.md index c227ee9055..deb444e50b 100644 --- a/skype/skype-ps/skype/Set-CsAddressBookConfiguration.md +++ b/skype/skype-ps/skype/Set-CsAddressBookConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csaddressbookconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csaddressbookconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAddressBookConfiguration schema: 2.0.0 @@ -403,4 +403,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsAddressBookConfiguration](New-CsAddressBookConfiguration.md) [Remove-CsAddressBookConfiguration](Remove-CsAddressBookConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsAddressBookNormalizationConfiguration.md b/skype/skype-ps/skype/Set-CsAddressBookNormalizationConfiguration.md index 500c1b04bc..eb9e97ae29 100644 --- a/skype/skype-ps/skype/Set-CsAddressBookNormalizationConfiguration.md +++ b/skype/skype-ps/skype/Set-CsAddressBookNormalizationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csaddressbooknormalizationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csaddressbooknormalizationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAddressBookNormalizationConfiguration schema: 2.0.0 @@ -220,4 +220,3 @@ Instead, the `Set-CsAddressBookNormalizationConfiguration` cmdlet modifies exist [Remove-CsAddressBookNormalizationConfiguration](Remove-CsAddressBookNormalizationConfiguration.md) [Import-CsCompanyPhoneNormalizationRules](Import-CsCompanyPhoneNormalizationRules.md) - diff --git a/skype/skype-ps/skype/Set-CsAddressBookNormalizationRule.md b/skype/skype-ps/skype/Set-CsAddressBookNormalizationRule.md index 66b673c768..c68c1560bb 100644 --- a/skype/skype-ps/skype/Set-CsAddressBookNormalizationRule.md +++ b/skype/skype-ps/skype/Set-CsAddressBookNormalizationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csaddressbooknormalizationrule +online version: https://learn.microsoft.com/powershell/module/skype/set-csaddressbooknormalizationrule applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAddressBookNormalizationRule schema: 2.0.0 @@ -239,4 +239,3 @@ Instead, the `Set-CsAddressBookNormalizationRule` cmdlet modifies existing insta [New-CsAddressBookNormalizationRule](New-CsAddressBookNormalizationRule.md) [Remove-CsAddressBookNormalizationRule](Remove-CsAddressBookNormalizationRule.md) - diff --git a/skype/skype-ps/skype/Set-CsAdminRole.md b/skype/skype-ps/skype/Set-CsAdminRole.md index dcd7aeca02..844768e6e6 100644 --- a/skype/skype-ps/skype/Set-CsAdminRole.md +++ b/skype/skype-ps/skype/Set-CsAdminRole.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csadminrole +online version: https://learn.microsoft.com/powershell/module/skype/set-csadminrole applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAdminRole schema: 2.0.0 @@ -335,4 +335,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsAllowedDomain.md b/skype/skype-ps/skype/Set-CsAllowedDomain.md index 9931f1c783..09d21b4f92 100644 --- a/skype/skype-ps/skype/Set-CsAllowedDomain.md +++ b/skype/skype-ps/skype/Set-CsAllowedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csalloweddomain +online version: https://learn.microsoft.com/powershell/module/skype/set-csalloweddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAllowedDomain schema: 2.0.0 @@ -294,4 +294,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsAllowedDomain](Remove-CsAllowedDomain.md) [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsAnalogDevice.md b/skype/skype-ps/skype/Set-CsAnalogDevice.md index 10fe2f56c8..5c9cadbf2c 100644 --- a/skype/skype-ps/skype/Set-CsAnalogDevice.md +++ b/skype/skype-ps/skype/Set-CsAnalogDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csanalogdevice +online version: https://learn.microsoft.com/powershell/module/skype/set-csanalogdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAnalogDevice schema: 2.0.0 @@ -338,4 +338,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [New-CsAnalogDevice](New-CsAnalogDevice.md) [Remove-CsAnalogDevice](Remove-CsAnalogDevice.md) - diff --git a/skype/skype-ps/skype/Set-CsAnnouncement.md b/skype/skype-ps/skype/Set-CsAnnouncement.md index 0f84ce0f8e..7ed8e2878a 100644 --- a/skype/skype-ps/skype/Set-CsAnnouncement.md +++ b/skype/skype-ps/skype/Set-CsAnnouncement.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csannouncement +online version: https://learn.microsoft.com/powershell/module/skype/set-csannouncement applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAnnouncement schema: 2.0.0 @@ -289,4 +289,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [Get-CsAnnouncement](Get-CsAnnouncement.md) [Import-CsAnnouncementFile](Import-CsAnnouncementFile.md) - diff --git a/skype/skype-ps/skype/Set-CsApplicationServer.md b/skype/skype-ps/skype/Set-CsApplicationServer.md index 1de977f970..0d12488539 100644 --- a/skype/skype-ps/skype/Set-CsApplicationServer.md +++ b/skype/skype-ps/skype/Set-CsApplicationServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csapplicationserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csapplicationserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsApplicationServer schema: 2.0.0 @@ -427,4 +427,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## RELATED LINKS [Get-CsServerApplication](Get-CsServerApplication.md) - diff --git a/skype/skype-ps/skype/Set-CsArchivingConfiguration.md b/skype/skype-ps/skype/Set-CsArchivingConfiguration.md index 4c4793d251..f3a3c69100 100644 --- a/skype/skype-ps/skype/Set-CsArchivingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsArchivingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csarchivingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csarchivingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsArchivingConfiguration schema: 2.0.0 @@ -386,4 +386,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsArchivingConfiguration](Remove-CsArchivingConfiguration.md) [Set-CsArchivingServer](Set-CsArchivingServer.md) - diff --git a/skype/skype-ps/skype/Set-CsArchivingPolicy.md b/skype/skype-ps/skype/Set-CsArchivingPolicy.md index b9ff16153c..f4e73c3195 100644 --- a/skype/skype-ps/skype/Set-CsArchivingPolicy.md +++ b/skype/skype-ps/skype/Set-CsArchivingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csarchivingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csarchivingpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsArchivingPolicy schema: 2.0.0 @@ -265,4 +265,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsArchivingPolicy](New-CsArchivingPolicy.md) [Remove-CsArchivingPolicy](Remove-CsArchivingPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsArchivingServer.md b/skype/skype-ps/skype/Set-CsArchivingServer.md index c921084fca..8d31fba3a6 100644 --- a/skype/skype-ps/skype/Set-CsArchivingServer.md +++ b/skype/skype-ps/skype/Set-CsArchivingServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csarchivingserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csarchivingserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsArchivingServer schema: 2.0.0 @@ -156,4 +156,3 @@ Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.Xds.Displ ## RELATED LINKS [Get-CsArchivingConfiguration](Get-CsArchivingConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsAudioTestServiceApplication.md b/skype/skype-ps/skype/Set-CsAudioTestServiceApplication.md index dba2489097..bb891a7b26 100644 --- a/skype/skype-ps/skype/Set-CsAudioTestServiceApplication.md +++ b/skype/skype-ps/skype/Set-CsAudioTestServiceApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csaudiotestserviceapplication +online version: https://learn.microsoft.com/powershell/module/skype/set-csaudiotestserviceapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAudioTestServiceApplication schema: 2.0.0 @@ -356,4 +356,3 @@ The `Set-CsAudioTestServiceApplication` cmdlet does not return any objects or va ## RELATED LINKS [Get-CsAudioTestServiceApplication](Get-CsAudioTestServiceApplication.md) - diff --git a/skype/skype-ps/skype/Set-CsAuthConfig.md b/skype/skype-ps/skype/Set-CsAuthConfig.md index f4561db533..3e47cfbe63 100644 --- a/skype/skype-ps/skype/Set-CsAuthConfig.md +++ b/skype/skype-ps/skype/Set-CsAuthConfig.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csauthconfig +online version: https://learn.microsoft.com/powershell/module/skype/set-csauthconfig applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAuthConfig schema: 2.0.0 @@ -138,6 +138,6 @@ For more information, see [about_CommonParameters](https://go.microsoft.com/fwli ## NOTES -After changing CsAuthConfig, you must run [Enable-CsComputer](https://docs.microsoft.com/powershell/module/skype/enable-cscomputer?view=skype-ps) on each Skype for Business Server machine before your changes take effect. +After changing CsAuthConfig, you must run [Enable-CsComputer](https://learn.microsoft.com/powershell/module/skype/enable-cscomputer?view=skype-ps) on each Skype for Business Server machine before your changes take effect. ## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsAutodiscoverConfiguration.md b/skype/skype-ps/skype/Set-CsAutodiscoverConfiguration.md index a9e60b5b55..19027a504c 100644 --- a/skype/skype-ps/skype/Set-CsAutodiscoverConfiguration.md +++ b/skype/skype-ps/skype/Set-CsAutodiscoverConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csautodiscoverconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csautodiscoverconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsAutodiscoverConfiguration schema: 2.0.0 manager: rogupta @@ -24,14 +24,14 @@ This cmdlet was introduced in the cumulative update for Lync Server 2010: Novemb ``` Set-CsAutodiscoverConfiguration [[-Identity] <XdsIdentity>] [-Confirm] [-ExternalSipClientAccessFqdn <String>] [-ExternalSipClientAccessPort <UInt32>] [-Force] [-WebLinks <PSListModifier>] [-WhatIf] - [-EnableCertificateProvisioningServiceUrl <Boolean>] [<CommonParameters>] + [-EnableCertificateProvisioningServiceUrl <Boolean>] [-EnableCORS <Boolean>] [<CommonParameters>] ``` ### Instance ``` Set-CsAutodiscoverConfiguration [-Confirm] [-ExternalSipClientAccessFqdn <String>] [-ExternalSipClientAccessPort <UInt32>] [-Force] [-Instance <PSObject>] [-WebLinks <PSListModifier>] [-WhatIf] - [-EnableCertificateProvisioningServiceUrl <Boolean>] [<CommonParameters>] + [-EnableCertificateProvisioningServiceUrl <Boolean>] [-EnableCORS <Boolean>] [<CommonParameters>] ``` ## DESCRIPTION @@ -67,7 +67,7 @@ $Link1 = New-CsWebLink -Token "Fabrikam" -Href "https://LyncDiscover.fabrikam.co Set-CsAutoDiscoverConfiguration -Identity "site:Redmond" -WebLinks @{Add=$Link1} ``` -The commands shown in Example 1 add a new Autodiscover URL (https://LyncDiscover.fabrikam.com) to the Autodiscover configuration settings assigned to the Redmond site. +The commands shown in Example 1 add a new Autodiscover URL (`https://LyncDiscover.fabrikam.com`) to the Autodiscover configuration settings assigned to the Redmond site. To do this, the first command in the example uses the `New-CsWebLink` cmdlet to create a new Autodiscover URL; that URL is stored in a variable named $Link1. In the second command, the `Set-CsAutoDiscoverConfiguration` cmdlet is used to add the new URL to any URLs already assigned to these settings. This is done by using the WebLinks parameter and the parameter value @{Add=$Link1}. @@ -99,8 +99,8 @@ Set-CsAutoDiscoverConfiguration -Identity "site:Redmond" -WebLinks @{Replace=$Li ``` Example 3 shows how you can replace an existing collection of Autodiscover URLs with, in this case, a single URL. -To carry out this task, the first command in the example uses the `New-CsWebLink` cmdlet to create a new Autodiscover URL for https://LyncDiscover.contoso.com; the resulting URL is stored in a variable named $Link2. -The second command then uses the `Set-CsAutoDiscoverConfiguration` cmdlet and the WebLinks parameter to remove any URLs previously assigned to the Redmond site and replace them with the URL for https://LyncDiscover.contoso.com. +To carry out this task, the first command in the example uses the `New-CsWebLink` cmdlet to create a new Autodiscover URL for `https://LyncDiscover.contoso.com`; the resulting URL is stored in a variable named $Link2. +The second command then uses the `Set-CsAutoDiscoverConfiguration` cmdlet and the WebLinks parameter to remove any URLs previously assigned to the Redmond site and replace them with the URL for `https://LyncDiscover.contoso.com`. To do this, the command uses the Replace method instead of the Add or Remove method. @@ -132,6 +132,23 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnableCORS + +If set to True, Cross-Origin Resource Sharing is enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ExternalSipClientAccessFqdn Fully qualified domain name (FQDN) of the server that is used for external client access. @@ -272,6 +289,23 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnableCORS + +If set to True, Cross-Origin Resource Sharing is enabled. + +```yaml +Type: Boolean +Position: Named +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). @@ -289,4 +323,3 @@ The `Set-CsAutoDiscoverConfiguration` cmdlet modifies instances of the Microsoft ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsBackupServiceConfiguration.md b/skype/skype-ps/skype/Set-CsBackupServiceConfiguration.md index 0172972f03..dec80abb43 100644 --- a/skype/skype-ps/skype/Set-CsBackupServiceConfiguration.md +++ b/skype/skype-ps/skype/Set-CsBackupServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csbackupserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csbackupserviceconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsBackupServiceConfiguration schema: 2.0.0 @@ -332,4 +332,3 @@ Instead, the `Set-CsBackupServiceConfiguration` cmdlet modifies existing instanc [Get-CsBackupServiceConfiguration](Get-CsBackupServiceConfiguration.md) [Remove-CsBackupServiceConfiguration](Remove-CsBackupServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsBandwidthPolicyServiceConfiguration.md b/skype/skype-ps/skype/Set-CsBandwidthPolicyServiceConfiguration.md index 343498ee5f..cc5fd68c6b 100644 --- a/skype/skype-ps/skype/Set-CsBandwidthPolicyServiceConfiguration.md +++ b/skype/skype-ps/skype/Set-CsBandwidthPolicyServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csbandwidthpolicyserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csbandwidthpolicyserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsBandwidthPolicyServiceConfiguration schema: 2.0.0 @@ -237,4 +237,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.B [Remove-CsBandwidthPolicyServiceConfiguration](Remove-CsBandwidthPolicyServiceConfiguration.md) [Get-CsBandwidthPolicyServiceConfiguration](Get-CsBandwidthPolicyServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsBlockedDomain.md b/skype/skype-ps/skype/Set-CsBlockedDomain.md index e440e9efdc..15662712d0 100644 --- a/skype/skype-ps/skype/Set-CsBlockedDomain.md +++ b/skype/skype-ps/skype/Set-CsBlockedDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csblockeddomain +online version: https://learn.microsoft.com/powershell/module/skype/set-csblockeddomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsBlockedDomain schema: 2.0.0 @@ -207,4 +207,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsBlockedDomain](Remove-CsBlockedDomain.md) [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsBroadcastMeetingConfiguration.md b/skype/skype-ps/skype/Set-CsBroadcastMeetingConfiguration.md index d191cf65a0..62a74c0304 100644 --- a/skype/skype-ps/skype/Set-CsBroadcastMeetingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsBroadcastMeetingConfiguration.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csbroadcastmeetingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csbroadcastmeetingconfiguration applicable: Skype for Business Online title: Set-CsBroadcastMeetingConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsBroadcastMeetingConfiguration @@ -447,4 +447,3 @@ None ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsBusyOptions.md b/skype/skype-ps/skype/Set-CsBusyOptions.md index 7ab1f02455..5743b4b153 100644 --- a/skype/skype-ps/skype/Set-CsBusyOptions.md +++ b/skype/skype-ps/skype/Set-CsBusyOptions.md @@ -36,7 +36,7 @@ After configuration, the Busy Options setting is in effect for all the user's Sk Users will see missed-call notifications on their Skype for Business clients and devices, and they will be notified by email as well. Callers whose call was rejected due to Busy on Busy will see a notification in their Skype for Business client stating that the user they attempted to reach is busy on another call. -For more information about how to enable Busy Options in your organization, see (https://docs.microsoft.com/skypeforbusiness/deploy/deploy-enterprise-voice/install-and-configure-busy-options). +For more information about how to enable Busy Options in your organization, see (https://learn.microsoft.com/skypeforbusiness/deploy/deploy-enterprise-voice/install-and-configure-busy-options). ## EXAMPLES @@ -162,6 +162,6 @@ Microsoft.Rtc.Management.AD.UserIdParameter object. ## NOTES ## RELATED LINKS -[Get-CsBusyOptions](https://docs.microsoft.com/powershell/module/skype/get-csbusyoptions?view=skype-ps) +[Get-CsBusyOptions](https://learn.microsoft.com/powershell/module/skype/get-csbusyoptions?view=skype-ps) -[Remove-CsBusyOptions](https://docs.microsoft.com/powershell/module/skype/remove-csbusyoptions?view=skype-ps) +[Remove-CsBusyOptions](https://learn.microsoft.com/powershell/module/skype/remove-csbusyoptions?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsCallParkOrbit.md b/skype/skype-ps/skype/Set-CsCallParkOrbit.md index 03aae13268..1962bcc635 100644 --- a/skype/skype-ps/skype/Set-CsCallParkOrbit.md +++ b/skype/skype-ps/skype/Set-CsCallParkOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscallparkorbit +online version: https://learn.microsoft.com/powershell/module/skype/set-cscallparkorbit applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsCallParkOrbit schema: 2.0.0 @@ -269,4 +269,3 @@ This cmdlet modifies an object of type Microsoft.Rtc.Management.Voice.Helpers.Di [Remove-CsCallParkOrbit](Remove-CsCallParkOrbit.md) [Get-CsCallParkOrbit](Get-CsCallParkOrbit.md) - diff --git a/skype/skype-ps/skype/Set-CsCallParkServiceMusicOnHoldFile.md b/skype/skype-ps/skype/Set-CsCallParkServiceMusicOnHoldFile.md index 8a1c8aa1fc..81af567605 100644 --- a/skype/skype-ps/skype/Set-CsCallParkServiceMusicOnHoldFile.md +++ b/skype/skype-ps/skype/Set-CsCallParkServiceMusicOnHoldFile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscallparkservicemusiconholdfile +online version: https://learn.microsoft.com/powershell/module/skype/set-cscallparkservicemusiconholdfile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsCallParkServiceMusicOnHoldFile schema: 2.0.0 @@ -45,17 +45,13 @@ Audio files must be in the following format: Windows Media Audio 9, 44 kHz, 16 b ### -------------------------- Example 1 -------------------------- ``` -$a = Get-Content -ReadCount 0 -Encoding byte "C:\MoHFiles\soothingmusic.wma" +$a = [System.IO.File]::ReadAllBytes('C:\MoHFiles\soothingmusic.wma') Set-CsCallParkServiceMusicOnHoldFile -Service ApplicationServer:pool0.litwareinc.com -Content $a ``` This example sets the file SoothingMusic.wma to be the audio file that is played to callers whose calls are parked. -The first line of this example is a call to the `Get-Content` cmdlet. -This cmdlet simply reads the contents of a file and assigns them, in this case, to the variable $a. -We pass a value of 0 to the ReadCount parameter so the `Get-Content` cmdlet will read the entire file at once (rather than try to read it line by line, which doesn't apply to an audio file). -We set the Encoding parameter to byte. -This tells the `Get-Content` cmdlet that the content we want to read into variable $a is a byte array rather than the audio file in .wma format. +The first line of this example uses the `[System.IO.File]::ReadAllBytes` command to read the contents of a file in byte format and assign them, in this case, to the variable $a. Line 2 in this example is where we actually assign the audio file. We call the `Set-CsCallParkServiceMusicOnHoldFile` cmdlet and specify the service ID where the Call Park service is running. @@ -84,8 +80,7 @@ Accept wildcard characters: False ### -Content The contents of the audio file in byte format. -Use the `Get-Content` cmdlet to retrieve the contents of the audio file in byte format. -(For details, see the Examples section in this topic.) +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('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`). ```yaml Type: Byte[] @@ -173,4 +168,3 @@ This cmdlet does not return a value. [Set-CsCpsConfiguration](Set-CsCpsConfiguration.md) [Get-CsCpsConfiguration](Get-CsCpsConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsCallQueue.md b/skype/skype-ps/skype/Set-CsCallQueue.md deleted file mode 100644 index 882c869f7d..0000000000 --- a/skype/skype-ps/skype/Set-CsCallQueue.md +++ /dev/null @@ -1,354 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscallqueue -applicable: Skype for Business Online -title: Set-CsCallQueue -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Set-CsCallQueue - -## SYNOPSIS -Updates a Call Queue in your Skype for Business Online organization. - -## SYNTAX - -``` -Set-CsCallQueue -Identity <Guid> [-AgentAlertTime <Int16>] [-AllowOptOut <Boolean>] [-DistributionLists <List>] [-MusicOnHoldAudioFileId <Guid>] [-Name <String>] [-OverflowAction <Object>] [-OverflowActionTarget <Guid>] [-OverflowThreshold <Int16>] [-RoutingMethod <Object>] [-TimeoutAction <Object>] [-Tenant <Guid>] [-TimeoutActionTarget <Guid>] [-TimeoutThreshold <Int16>] [-UseDefaultMusicOnHold <Boolean>] [-WelcomeMusicAudioFileId <Guid>] [-PresenceBasedRouting <Boolean>] [-Users <List>] [<CommonParameters>] -``` - -## DESCRIPTION - -Set-CsCallQueue cmdlet provides a way for you to modify the properties of an existing Call Queue; for example, you can change the name for the Call Queue, the distribution lists associated with the Call Queue, or the welcome audio file. - -The Set-CsCallQueue cmdlet may suggest additional steps required to complete the Call Queue setup. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsCallQueue -Identity e7e00636-47da-449c-a36b-1b3d6ee04440 -UseDefaultMusicOnHold $true -``` - -This example updates the Call Queue with identity e7e00636-47da-449c-a36b-1b3d6ee04440 by making it use the default music on hold. - -### -------------------------- Example 2 -------------------------- -``` -Set-CsCallQueue -Identity e7e00636-47da-449c-a36b-1b3d6ee04440 -DistributionLists @("8521b0e3-51bd-4a4b-a8d6-b219a77a0a6a", "868dccd8-d723-4b4f-8d74-ab59e207c357") -MusicOnHoldAudioFileId 4d7361c1-5b46-4f69-b125-cf35a098a341 -``` - -This example updates the Call Queue with new distribution lists and references a new music on hold audio file. - -## PARAMETERS - -### -Identity -PARAMVALUE: Guid - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AgentAlertTime -The AgentAlertTime parameter represents the time (in seconds) that a call can remain unanswered before it is automatically routed to the next agent. The AgentAlertTime can be set to any integer value between 15 and 180 seconds (3 minutes), inclusive. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 30 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOptOut -The AllowOptOut parameter indicates whether or not agents can opt in or opt out from taking calls from a Call Queue. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionLists -The DistributionLists parameter lets you add all the members of the distribution lists to the Call Queue. This is a list of distribution list GUIDs. A service wide configurable maximum number of DLs per Call Queue are allowed. Only the first N (service wide configurable) agents from all distribution lists combined are considered for accepting the call. Nested DLs are supported. O365 Groups can also be used to add members to the Call Queue. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MusicOnHoldAudioFileId -The MusicOnHoldFileContent parameter represents music to play when callers are placed on hold. This is the unique identifier of the audio file. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies a unique name for the Call Queue. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowAction -The OverflowAction parameter designates the action to take if the overflow threshold is reached. The OverflowAction property must be set to one of the following three values: DisconnectWithBusy, Forward, and Voicemail. - -PARAMVALUE: DisconnectWithBusy | Forward | Voicemail - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: DisconnectWithBusy -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowActionTarget -The OverflowActionTarget parameter represents the target of the overflow action. If the OverFlowAction is set to Forward, this parameter must be set to a Guid. Otherwise, this parameter is optional. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowThreshold -The OverflowThreshold parameter defines the number of calls that can be in the queue at any one time before the overflow action is triggered. The OverflowThreshold can be any integer value between 0 and 200, inclusive. A value of 0 causes calls not to reach agents and the overflow action to be taken immediately. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 50 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoutingMethod -The RoutingMethod defines how agents will be called in a Call Queue. If the routing method is set to Serial, then agents will be called one at a time. If the routing method is set to Attendant, then agents will be called in parallel. - -PARAMVALUE: Attendant | Serial | RoundRobin - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Attendant -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutAction -The TimeoutAction parameter defines the action to take if the timeout threshold is reached. The TimeoutAction property must be set to one of the following three values: Disconnect, Forward, and Voicemail. The default value is Disconnect. - -PARAMVALUE: Disconnect | Forward | Voicemail - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Disconnect -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutActionTarget -The TimeoutActionTarget represents the target of the timeout action. If the TimeoutAction is set to Forward, this parameter must be set to a Guid. Otherwise, this field is optional. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutThreshold -The TimeoutThreshold parameter defines the time (in seconds) that a call can be in the queue before that call times out. At that point, the system will take the action specified by the TimeoutAction parameter. -The TimeoutThreshold can be any integer value between 0 and 2700 seconds (inclusive), and is rounded to the nearest 15th interval. For example, if set to 47 seconds, then it is rounded down to 45. If set to 0, welcome music is played, and then the timeout action will be taken. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 1200 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultMusicOnHold -The UseDefaultMusicOnHold parameter indicates that this Call Queue uses the default music on hold. This parameter cannot be specified together with MusicOnHoldAudioFileId. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WelcomeMusicAudioFileId -The WelcomeMusicAudioFileId parameter represents the audio file to play when callers are connected with the Call Queue. This is the unique identifier of the audio file. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PresenceBasedRouting -The PresenceBasedRouting parameter indicates whether or not presence based routing will be applied while call being routed to Call Queue agents. When set to False, calls will be routed to agents who have opted in to receive calls, regardless of their presence state. When set to True, opted-in agents will receive calls only when their presence state is Available. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Users -The Users parameter lets you add agents to the Call Queue. This parameter expects a list of user unique identifiers (GUID). - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsCallViaWorkPolicy.md b/skype/skype-ps/skype/Set-CsCallViaWorkPolicy.md index af6fc58a40..5177db6710 100644 --- a/skype/skype-ps/skype/Set-CsCallViaWorkPolicy.md +++ b/skype/skype-ps/skype/Set-CsCallViaWorkPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscallviaworkpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-cscallviaworkpolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsCallViaWorkPolicy schema: 2.0.0 @@ -229,4 +229,3 @@ None. [Grant-CsCallViaWorkPolicy](Grant-CsCallViaWorkPolicy.md) [Get-CsCallViaWorkPolicy](Get-CsCallViaWorkPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsCallingLineIdentity.md b/skype/skype-ps/skype/Set-CsCallingLineIdentity.md deleted file mode 100644 index 0b06c57276..0000000000 --- a/skype/skype-ps/skype/Set-CsCallingLineIdentity.md +++ /dev/null @@ -1,308 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscallinglineidentity -applicable: Skype for Business Online -title: Set-CsCallingLineIdentity -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsCallingLineIdentity - -## SYNOPSIS -Use the `Set-CsCallingLineIdentity` cmdlet to modify a Caller ID policy in your organization. - -## SYNTAX - -### Identity (Default) -``` -Set-CsCallingLineIdentity [-Tenant <Guid>] [-Description <String>] [-EnableUserOverride <Boolean>] - [-ServiceNumber <String>] [-CallingIDSubstitute <CallingIDSubstituteType>] - [-BlockIncomingPstnCallerID <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] - [AsJob] [<CommonParameters>] -``` - -### Instance -``` -Set-CsCallingLineIdentity [-Tenant <Guid>] [-Description <String>] [-EnableUserOverride <Boolean>] - [-ServiceNumber <String>] [-CallingIDSubstitute <CallingIDSubstituteType>] - [-BlockIncomingPstnCallerID <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] - [AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -You can either change or block the Caller ID (also called a Calling Line ID) for a user. -By default, the Skype for Business Online user's phone number can be seen when that user makes a call to a PSTN phone, or when a call comes in. -You can modify a Caller ID policy to provide an alternate displayed number, or to block any number from being displayed. - -Note: -Identity must be unique. - -ServiceNumber must be a valid Service Number in the Skype for Business Online Telephone Number Inventory. - -If CallerIdSubstitute is given as "Service", then ServiceNumber cannot be empty. - -## EXAMPLES - -### Example 1 -``` -PS C:\> Set-CsCallingLineIdentity -Identity "MyBlockingPolicy" -BlockIncomingPstnCallerID $true -``` - -This example blocks the incoming caller ID. -The user can override this setting. - -### Example 2 -``` -PS C:\> Set-CsCallingLineIdentity -Identity "UKOrgAA" -CallingIdSubstitute "Service" -ServiceNumber "14258828080" -``` - -This example modifies the UKOrgAA Caller ID policy to sets the Caller ID to a specified service number. - -### Example 3 -``` -PS C:\> Set-CsCallingLineIdentity -Identity Anonymous -Description "anonymous policy" -CallingIDSubstitute Anonymous -EnableUserOverride $false -BlockIncomingPstnCallerID $true -``` - -This example modifies the new Anonymous Caller ID policy that blocks the incoming Caller ID. - -## PARAMETERS - -### -BlockIncomingPstnCallerID -The BlockIncomingPstnCallerID switch determines whether to block the incoming Caller ID. -The default value is false. - -The BlockIncomingPstnCallerID switch is specific to incoming calls from a PSTN caller to a user. -If this is set to True and if this policy is assigned to a Lync user, then Caller ID for incoming calls is suppressed/anonymous. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallingIDSubstitute -The CallingIDSubstitute parameter lets you specify an alternate Caller ID. -The possible values are Anonymous, Service and LineUri. - -```yaml -Type: CallingIDSubstituteType -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -The Description parameter briefly describes the Caller ID policy. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableUserOverride -The EnableUserOverride switch lets the user override the Caller ID policy. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter identifies the Caller ID policy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceNumber -The ServiceNumber parameter lets you add any valid service number for the CallingIdSubstitute. - -Note: Do not add '+' to the Service number. -For example, if the Service number is +1425-xxx-xxxx then valid input is 1425xxxxxxx. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Get-CsCallingLineIdentity](Get-CsCallingLineIdentity.md) - -[Grant-CsCallingLineIdentity](Grant-CsCallingLineIdentity.md) - -[New-CsCallingLineIdentity](New-CsCallingLineIdentity.md) - -[Remove-CsCallingLineIdentity](Remove-CsCallingLineIdentity.md) diff --git a/skype/skype-ps/skype/Set-CsCceApplianceConfigurationReplicationStatus.md b/skype/skype-ps/skype/Set-CsCceApplianceConfigurationReplicationStatus.md index 54704140d2..4d556a212d 100644 --- a/skype/skype-ps/skype/Set-CsCceApplianceConfigurationReplicationStatus.md +++ b/skype/skype-ps/skype/Set-CsCceApplianceConfigurationReplicationStatus.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscceapplianceconfigurationreplicationstatus +online version: https://learn.microsoft.com/powershell/module/skype/set-cscceapplianceconfigurationreplicationstatus applicable: Skype for Business Online title: Set-CsCceApplianceConfigurationReplicationStatus schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsCceApplianceConfigurationReplicationStatus @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS {{Fill in the Synopsis}} +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -154,4 +156,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsCceApplianceDeploymentStatus.md b/skype/skype-ps/skype/Set-CsCceApplianceDeploymentStatus.md index 84f178ea97..1ca389b8ab 100644 --- a/skype/skype-ps/skype/Set-CsCceApplianceDeploymentStatus.md +++ b/skype/skype-ps/skype/Set-CsCceApplianceDeploymentStatus.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscceappliancedeploymentstatus +online version: https://learn.microsoft.com/powershell/module/skype/set-cscceappliancedeploymentstatus applicable: Skype for Business Online title: Set-CsCceApplianceDeploymentStatus schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsCceApplianceDeploymentStatus @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Provide the topic introduction here. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -218,4 +220,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsCceApplianceStatus.md b/skype/skype-ps/skype/Set-CsCceApplianceStatus.md index bba7b6d3f0..634a66015e 100644 --- a/skype/skype-ps/skype/Set-CsCceApplianceStatus.md +++ b/skype/skype-ps/skype/Set-CsCceApplianceStatus.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscceappliancestatus +online version: https://learn.microsoft.com/powershell/module/skype/set-cscceappliancestatus applicable: Skype for Business Online title: Set-CsCceApplianceStatus schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsCceApplianceStatus @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Provide the topic introduction here. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -200,4 +202,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsCdrConfiguration.md b/skype/skype-ps/skype/Set-CsCdrConfiguration.md index 1741e90be4..adac626963 100644 --- a/skype/skype-ps/skype/Set-CsCdrConfiguration.md +++ b/skype/skype-ps/skype/Set-CsCdrConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscdrconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cscdrconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsCdrConfiguration schema: 2.0.0 @@ -310,4 +310,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsCdrConfiguration](New-CsCdrConfiguration.md) [Remove-CsCdrConfiguration](Remove-CsCdrConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsCertificate.md b/skype/skype-ps/skype/Set-CsCertificate.md index ec3efc3634..a88a78863d 100644 --- a/skype/skype-ps/skype/Set-CsCertificate.md +++ b/skype/skype-ps/skype/Set-CsCertificate.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscertificate +online version: https://learn.microsoft.com/powershell/module/skype/set-cscertificate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsCertificate schema: 2.0.0 @@ -376,4 +376,3 @@ The `Set-CsCertificate` cmdlet does not return any values or objects. [Remove-CsCertificate](Remove-CsCertificate.md) [Request-CsCertificate](Request-CsCertificate.md) - diff --git a/skype/skype-ps/skype/Set-CsClientPin.md b/skype/skype-ps/skype/Set-CsClientPin.md index 0aae41324c..186c380a81 100644 --- a/skype/skype-ps/skype/Set-CsClientPin.md +++ b/skype/skype-ps/skype/Set-CsClientPin.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclientpin +online version: https://learn.microsoft.com/powershell/module/skype/set-csclientpin applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClientPin schema: 2.0.0 @@ -207,4 +207,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.UserPin [Lock-CsClientPin](Lock-CsClientPin.md) [Unlock-CsClientPin](Unlock-CsClientPin.md) - diff --git a/skype/skype-ps/skype/Set-CsClientPolicy.md b/skype/skype-ps/skype/Set-CsClientPolicy.md index 6a5fbf79b6..6af1ef3225 100644 --- a/skype/skype-ps/skype/Set-CsClientPolicy.md +++ b/skype/skype-ps/skype/Set-CsClientPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclientpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csclientpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClientPolicy schema: 2.0.0 manager: bulenteg @@ -120,7 +120,7 @@ The `Set-CsClientPolicy` cmdlet enables you to modify any (or all) of the client Keep in mind that client policies differ from many other policies in that most of the policy settings do not have default values. When setting is null/none just means that server in band provisioning does not override default client value. Basically, default values are set by client for these cases. -The following parameters are not applicable to Skype for Business Online: AddressBookAvailability, AsJob, AttendantSafeTransfer, AutoDiscoveryRetryInterval, BlockConversationFromFederatedContacts, CalendarStatePublicationInterval, ConferenceIMIdleTimeout, CustomizedHelpUrl, CustomLinkInErrorMessages, CustomStateUrl, Description, DGRefreshInterval, DisableContactCardOrganizationTab, DisableFederatedPromptDisplayName, DisableFeedsTab, DisableMeetingSubjectAndLocation, DisableOneNote12Integration, DisableOnlineContextualSearch, DisablePhonePresence, DisablePICPromptDisplayName, EnableEventLogging, EnableExchangeContactsFolder, EnableExchangeDelegateSync, EnableFullScreenVideo, EnableHighPerformanceConferencingAppSharing, EnableHighPerformanceP2PAppSharing, EnableMediaRedirection, EnableMeetingEngagement, EnableNotificationForNewSubscribers, EnableOnlineFeedback, EnableOnlineFeedbackScreenshots, EnableSQMData, EnableTracing, EnableViewBasedSubscriptionMode, EnableVOIPCallDefault, Force, HelpEnvironment, Identity, IMLatencyErrorThreshold, IMLatencySpinnerDelay, Instance, MAPIPollInterval, MaximumDGsAllowedInContactList, MaximumNumberOfContacts, MaxPhotoSizeKB, P2PAppSharingEncryption, PipelineVariable, PolicyEntry, PublicationBatchDelay, RateMyCallAllowCustomUserFeedback, RequireContentPin, SearchPrefixFlags, SPSearchCenterExternalURL, SPSearchCenterInternalURL, SPSearchExternalURL, SPSearchInternalURL, SupportModernFilePicker, TabURL, TelemetryTier, Tenant, and WebServicePollInterval +The following parameters are not applicable to Skype for Business Online: AddressBookAvailability, AttendantSafeTransfer, AutoDiscoveryRetryInterval, BlockConversationFromFederatedContacts, CalendarStatePublicationInterval, ConferenceIMIdleTimeout, CustomizedHelpUrl, CustomLinkInErrorMessages, CustomStateUrl, Description, DGRefreshInterval, DisableContactCardOrganizationTab, DisableFederatedPromptDisplayName, DisableFeedsTab, DisableMeetingSubjectAndLocation, DisableOneNote12Integration, DisableOnlineContextualSearch, DisablePhonePresence, DisablePICPromptDisplayName, EnableEventLogging, EnableExchangeContactsFolder, EnableExchangeDelegateSync, EnableFullScreenVideo, EnableHighPerformanceConferencingAppSharing, EnableHighPerformanceP2PAppSharing, EnableMediaRedirection, EnableMeetingEngagement, EnableNotificationForNewSubscribers, EnableOnlineFeedback, EnableOnlineFeedbackScreenshots, EnableSQMData, EnableTracing, EnableViewBasedSubscriptionMode, EnableVOIPCallDefault, Force, HelpEnvironment, Identity, IMLatencyErrorThreshold, IMLatencySpinnerDelay, Instance, MAPIPollInterval, MaximumDGsAllowedInContactList, MaximumNumberOfContacts, MaxPhotoSizeKB, P2PAppSharingEncryption, PipelineVariable, PolicyEntry, PublicationBatchDelay, RateMyCallAllowCustomUserFeedback, RequireContentPin, SearchPrefixFlags, SPSearchCenterExternalURL, SPSearchCenterInternalURL, SPSearchExternalURL, SPSearchInternalURL, SupportModernFilePicker, TabURL, TelemetryTier, Tenant, and WebServicePollInterval ## EXAMPLES @@ -1372,8 +1372,7 @@ To search only display name, first name, and last name you would construct this After the binary value has been constructed it must then be converted to a decimal value before being assigned to SearchPrefixFlags. To convert a binary number to a decimal number you can use the following Windows PowerShell command: -`\[Convert\]::ToInt32("1110111", 2)` - +`[Convert]::ToInt32("1110111", 2)` ```yaml Type: UInt16 @@ -2119,4 +2118,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsClientPolicy](New-CsClientPolicy.md) [Remove-CsClientPolicy](Remove-CsClientPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsClientVersionConfiguration.md b/skype/skype-ps/skype/Set-CsClientVersionConfiguration.md index 729650a4e5..c7a71cdaca 100644 --- a/skype/skype-ps/skype/Set-CsClientVersionConfiguration.md +++ b/skype/skype-ps/skype/Set-CsClientVersionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclientversionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csclientversionconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClientVersionConfiguration schema: 2.0.0 @@ -266,4 +266,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsClientVersionConfiguration](New-CsClientVersionConfiguration.md) [Remove-CsClientVersionConfiguration](Remove-CsClientVersionConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsClientVersionPolicy.md b/skype/skype-ps/skype/Set-CsClientVersionPolicy.md index 0a43f47feb..dfff66f31a 100644 --- a/skype/skype-ps/skype/Set-CsClientVersionPolicy.md +++ b/skype/skype-ps/skype/Set-CsClientVersionPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclientversionpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csclientversionpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClientVersionPolicy schema: 2.0.0 @@ -252,4 +252,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsClientVersionPolicy](Remove-CsClientVersionPolicy.md) [Set-CsClientVersionPolicy](Set-CsClientVersionPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsClientVersionPolicyRule.md b/skype/skype-ps/skype/Set-CsClientVersionPolicyRule.md index 493fac5211..b9933740d1 100644 --- a/skype/skype-ps/skype/Set-CsClientVersionPolicyRule.md +++ b/skype/skype-ps/skype/Set-CsClientVersionPolicyRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclientversionpolicyrule +online version: https://learn.microsoft.com/powershell/module/skype/set-csclientversionpolicyrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClientVersionPolicyRule schema: 2.0.0 @@ -485,4 +485,3 @@ Instead, the `Set-CsClientVersionPolicyRule` cmdlet modifies instances of the Mi [New-CsClientVersionPolicyRule](New-CsClientVersionPolicyRule.md) [Set-CsClientVersionPolicyRule](Set-CsClientVersionPolicyRule.md) - diff --git a/skype/skype-ps/skype/Set-CsCloudCallDataConnector.md b/skype/skype-ps/skype/Set-CsCloudCallDataConnector.md index 5a2eab330f..d15bbdcaf8 100644 --- a/skype/skype-ps/skype/Set-CsCloudCallDataConnector.md +++ b/skype/skype-ps/skype/Set-CsCloudCallDataConnector.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscloudcalldataconnector +online version: https://learn.microsoft.com/powershell/module/skype/set-cscloudcalldataconnector applicable: Skype for Business Server 2019 title: Set-CsCloudCallDataConnector schema: 2.0.0 @@ -35,9 +35,12 @@ The Set-CsCloudCallDataConnector cmdlet provides a way for you to store an on-pr PS C:\> New-CsCloudCallDataConnection | Set-CsCloudCallDataConnector -TenantId <tenant_id> ``` -If you're logged in to Skype for Business Online Powershell within the Skype for Business Server Management Shell 2019, this command in example 1 takes the output of the New-CsCloudCallDataConnection online cmdlet and passes it to the Set-CsCloudCallDataConnector cmdlet via pipeline so that the Token can be stored on premises. Along with the Token, the TenantId of your O365 tenant will get stored on premises as well. +If you're logged in to Microsoft Teams PowerShell Module within the Skype for Business Server Management Shell 2019, this command in example 1 takes the output of the New-CsCloudCallDataConnection online cmdlet and passes it to the Set-CsCloudCallDataConnector cmdlet via pipeline so that the Token can be stored on premises. Along with the Token, the TenantId of your O365 tenant will get stored on premises as well. ### Example 2 +```PowerShell +Set-CsCloudCallDataConnector -Identity Global -TenantId <tenant_id> -Token <token-copied-from-online> +``` Example showing the scenario when we aren't piping the output from online cmdlet. ## PARAMETERS diff --git a/skype/skype-ps/skype/Set-CsCloudCallDataConnectorConfiguration.md b/skype/skype-ps/skype/Set-CsCloudCallDataConnectorConfiguration.md index cbec2d0092..021a5cf3e8 100644 --- a/skype/skype-ps/skype/Set-CsCloudCallDataConnectorConfiguration.md +++ b/skype/skype-ps/skype/Set-CsCloudCallDataConnectorConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscloudcalldataconnectorconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cscloudcalldataconnectorconfiguration applicable: Skype for Business Server 2019 title: Set-CsCloudCallDataConnectorConfiguration schema: 2.0.0 @@ -20,13 +20,13 @@ Modifies an existing collection of Cloud Call Data Connector configuration setti ### Identity (Default) ``` Set-CsCloudCallDataConnectorConfiguration [-EnableCallDataConnector <Boolean>] [[-Identity] <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] + [-Force] [-WhatIf] [<CommonParameters>] ``` ### Instance ``` Set-CsCloudCallDataConnectorConfiguration [-EnableCallDataConnector <Boolean>] [-Instance <PSObject>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] + [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION @@ -68,21 +68,6 @@ The filtered collection is then piped to the `Set-CsCloudCallDataConnectorConfig ## PARAMETERS -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Server 2019 -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -EnableCallDataConnector Enables upload of call data. diff --git a/skype/skype-ps/skype/Set-CsClsConfiguration.md b/skype/skype-ps/skype/Set-CsClsConfiguration.md index 6b4d56c5b7..ac2b5e0018 100644 --- a/skype/skype-ps/skype/Set-CsClsConfiguration.md +++ b/skype/skype-ps/skype/Set-CsClsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csclsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClsConfiguration schema: 2.0.0 @@ -29,6 +29,7 @@ Set-CsClsConfiguration [[-Identity] <XdsIdentity>] [-CacheFileLocalFolders <Stri [-Force] [-MinimumClsAgentServiceVersion <UInt32>] [-Regions <PSListModifier>] [-Scenarios <PSListModifier>] [-SearchTerms <PSListModifier>] [-SecurityGroups <PSListModifier>] [-TmfFileSearchPath <String>] [-WhatIf] [-NetworkUsagePacketSize <UInt32>] [-NetworkUsageThreshold <UInt32>] [-Version <String>] [<CommonParameters>] + [-ETLMinFreeSpaceInDiskInBytes<Int64>] [-ETLEnoughFreeSpaceInDiskInBytes<Int64>] [-ETLMinQuotaInBytes <Int64>] [-ETLMaxQuotaInBytes <Int64>] [-ETLEnoughQuotaInBytes <Int64>] [EtlMaxRetentionInDays <UInt32>] ``` ### Instance @@ -40,6 +41,7 @@ Set-CsClsConfiguration [-CacheFileLocalFolders <String>] [-CacheFileLocalMaxDisk [-MinimumClsAgentServiceVersion <UInt32>] [-Regions <PSListModifier>] [-Scenarios <PSListModifier>] [-SearchTerms <PSListModifier>] [-SecurityGroups <PSListModifier>] [-TmfFileSearchPath <String>] [-WhatIf] [-NetworkUsagePacketSize <UInt32>] [-NetworkUsageThreshold <UInt32>] [-Version <String>] [<CommonParameters>] + [-ETLMinFreeSpaceInDiskInBytes<Int64>] [-ETLEnoughFreeSpaceInDiskInBytes<Int64>] [-ETLMinQuotaInBytes <Int64>] [-ETLMaxQuotaInBytes <Int64>] [-ETLEnoughQuotaInBytes <Int64>] [EtlMaxRetentionInDays <UInt32>] ``` ## DESCRIPTION @@ -496,6 +498,105 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ETLMinFreeSpaceInDiskInBytes +Minimum allowed free disk space to have on the ETL folder drive. +If disk reaches this size and ETL Folder size is more than ETLMinQuotaInBytes, Purge executes. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2019 + +Required: False +Position: Named +Default value: 2000000000 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ETLEnoughFreeSpaceInDiskInBytes +Enough free disk space to make purge stop due low free disk space. +If disk size reaches this size, purge stops. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2019 + +Required: False +Position: Named +Default value: 4000000000 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ETLMinQuotaInBytes +Min quota allowed for ETL files, even if disk size is less than ETLMinFreeSpaceInDiskInBytes. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2019 + +Required: False +Position: Named +Default value: 3221225472 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ETLMaxQuotaInBytes +Max allowed quota used by ETL files before purge starts + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2019 + +Required: False +Position: Named +Default value: 400000000000 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ETLEnoughQuotaInBytes +Enough ETL usage quota to make purge stop due max quota condition reached + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2019 + +Required: False +Position: Named +Default value: 250000000000 +Accept pipeline input: False +Accept wildcard characters: False +``` + + +### -ETLMaxRetentionInDays +Maximum retention time in days for ETL files + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2019 + +Required: False +Position: Named +Default value: 14 +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). @@ -519,4 +620,3 @@ Instead, the `Set-CsClsConfiguration` cmdlet modifies existing instances of the [New-CsClsConfiguration](New-CsClsConfiguration.md) [Remove-CsClsConfiguration](Remove-CsClsConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsClsRegion.md b/skype/skype-ps/skype/Set-CsClsRegion.md index 1efa94ab40..89a4dee70b 100644 --- a/skype/skype-ps/skype/Set-CsClsRegion.md +++ b/skype/skype-ps/skype/Set-CsClsRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclsregion +online version: https://learn.microsoft.com/powershell/module/skype/set-csclsregion applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClsRegion schema: 2.0.0 @@ -213,4 +213,3 @@ Instead, the `Set-CsClsRegion` cmdlet modifies existing instances of the Microso [New-CsClsRegion](New-CsClsRegion.md) [Remove-CsClsRegion](Remove-CsClsRegion.md) - diff --git a/skype/skype-ps/skype/Set-CsClsScenario.md b/skype/skype-ps/skype/Set-CsClsScenario.md index 23c5b108a5..156d2a64db 100644 --- a/skype/skype-ps/skype/Set-CsClsScenario.md +++ b/skype/skype-ps/skype/Set-CsClsScenario.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclsscenario +online version: https://learn.microsoft.com/powershell/module/skype/set-csclsscenario applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClsScenario schema: 2.0.0 @@ -197,4 +197,3 @@ Instead, the `Set-CsClsScenario` cmdlet modifies existing instances of the Micro ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsClsSearchTerm.md b/skype/skype-ps/skype/Set-CsClsSearchTerm.md index 0fafe4702d..f3cb33712c 100644 --- a/skype/skype-ps/skype/Set-CsClsSearchTerm.md +++ b/skype/skype-ps/skype/Set-CsClsSearchTerm.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclssearchterm +online version: https://learn.microsoft.com/powershell/module/skype/set-csclssearchterm applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClsSearchTerm schema: 2.0.0 @@ -187,4 +187,3 @@ Instead, the `Set-CsClsSearchTerm` cmdlet modifies existing instances of the Mic ## RELATED LINKS [Get-CsClsSearchTerm](Get-CsClsSearchTerm.md) - diff --git a/skype/skype-ps/skype/Set-CsClsSecurityGroup.md b/skype/skype-ps/skype/Set-CsClsSecurityGroup.md index 6312375835..a0d8f37e29 100644 --- a/skype/skype-ps/skype/Set-CsClsSecurityGroup.md +++ b/skype/skype-ps/skype/Set-CsClsSecurityGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csclssecuritygroup +online version: https://learn.microsoft.com/powershell/module/skype/set-csclssecuritygroup applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsClsSecurityGroup schema: 2.0.0 @@ -210,4 +210,3 @@ Instead, the `Set-CsClsSecurityGroup` cmdlet modifies existing instances of the [New-CsClsSecurityGroup](New-CsClsSecurityGroup.md) [Remove-CsClsSecurityGroup](Remove-CsClsSecurityGroup.md) - diff --git a/skype/skype-ps/skype/Set-CsCommonAreaPhone.md b/skype/skype-ps/skype/Set-CsCommonAreaPhone.md index eabbc81868..0339c1c04d 100644 --- a/skype/skype-ps/skype/Set-CsCommonAreaPhone.md +++ b/skype/skype-ps/skype/Set-CsCommonAreaPhone.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscommonareaphone +online version: https://learn.microsoft.com/powershell/module/skype/set-cscommonareaphone applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsCommonAreaPhone schema: 2.0.0 @@ -349,4 +349,3 @@ However, if you include the PassThru parameter, the cmdlet will return instances [New-CsCommonAreaPhone](New-CsCommonAreaPhone.md) [Remove-CsCommonAreaPhone](Remove-CsCommonAreaPhone.md) - diff --git a/skype/skype-ps/skype/Set-CsConferenceDisclaimer.md b/skype/skype-ps/skype/Set-CsConferenceDisclaimer.md index 1bdcc9992a..161abd1d7d 100644 --- a/skype/skype-ps/skype/Set-CsConferenceDisclaimer.md +++ b/skype/skype-ps/skype/Set-CsConferenceDisclaimer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csconferencedisclaimer +online version: https://learn.microsoft.com/powershell/module/skype/set-csconferencedisclaimer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsConferenceDisclaimer schema: 2.0.0 @@ -192,4 +192,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [Get-CsConferenceDisclaimer](Get-CsConferenceDisclaimer.md) [Remove-CsConferenceDisclaimer](Remove-CsConferenceDisclaimer.md) - diff --git a/skype/skype-ps/skype/Set-CsConferenceServer.md b/skype/skype-ps/skype/Set-CsConferenceServer.md index 4754748cbb..b10649feaa 100644 --- a/skype/skype-ps/skype/Set-CsConferenceServer.md +++ b/skype/skype-ps/skype/Set-CsConferenceServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csconferenceserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csconferenceserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsConferenceServer schema: 2.0.0 @@ -31,7 +31,7 @@ Set-CsConferenceServer [[-Identity] <XdsGlobalRelativeIdentity>] [-AppSharingSip ## DESCRIPTION Conference Servers (also known as A/V Conferencing Servers) are used to provide audio and video capabilities to conferences. In turn, the `Set-CsConferenceServer` cmdlet can be used to modify the properties of these servers; in particular, you can specify which ports are used for such things as audio traffic, video traffic and application sharing. -You can also use the `Set-CsConferenceServer` cmdlet to associate a given server with a Edge Server or Archiving Server. +You can also use the `Set-CsConferenceServer` cmdlet to associate a given server with an Edge Server or Archiving Server. ## EXAMPLES @@ -368,4 +368,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [Get-CsConferencingConfiguration](Get-CsConferencingConfiguration.md) [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsConferencingConfiguration.md b/skype/skype-ps/skype/Set-CsConferencingConfiguration.md index 950896c439..6af69082b4 100644 --- a/skype/skype-ps/skype/Set-CsConferencingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsConferencingConfiguration schema: 2.0.0 @@ -31,7 +31,7 @@ Set-CsConferencingConfiguration [[-Identity] <XdsIdentity>] [-ClientAppSharingPo [-HelpdeskExternalUrl <String>] [-HelpdeskInternalUrl <String>] [-MaxBandwidthPerAppSharingServiceMb <UInt64>] [-MaxContentStorageMb <UInt16>] [-Organization <String>] [-Force] [-WhatIf] [-Confirm] [-MaxUploadFileSizeMb <UInt16>] [-CloudPollServicePrimaryUrl <String>] - [-CloudPollServiceSecondaryUrl <String>] [<CommonParameters>] + [-CloudPollServiceSecondaryUrl <String>] [-EncryptArchivedData <Boolean>] [<CommonParameters>] ``` ### Instance @@ -45,7 +45,7 @@ Set-CsConferencingConfiguration [-Instance <PSObject>] [-ClientAppSharingPort <U [-HelpdeskExternalUrl <String>] [-HelpdeskInternalUrl <String>] [-MaxBandwidthPerAppSharingServiceMb <UInt64>] [-MaxContentStorageMb <UInt16>] [-Organization <String>] [-Force] [-WhatIf] [-Confirm] [-MaxUploadFileSizeMb <UInt16>] [-CloudPollServicePrimaryUrl <String>] - [-CloudPollServiceSecondaryUrl <String>] [<CommonParameters>] + [-CloudPollServiceSecondaryUrl <String>] [-EncryptArchivedData <Boolean>] [<CommonParameters>] ``` ## DESCRIPTION @@ -645,6 +645,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EncryptArchivedData +Boolean flag to turn on/off encryption for a conference's archived attachments. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2019 + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). @@ -669,4 +685,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsConferencingConfiguration](New-CsConferencingConfiguration.md) [Remove-CsConferencingConfiguration](Remove-CsConferencingConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsConferencingPolicy.md b/skype/skype-ps/skype/Set-CsConferencingPolicy.md index 26ad11c09f..96b5bc05d9 100644 --- a/skype/skype-ps/skype/Set-CsConferencingPolicy.md +++ b/skype/skype-ps/skype/Set-CsConferencingPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csconferencingpolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csconferencingpolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsConferencingPolicy schema: 2.0.0 manager: bulenteg @@ -83,7 +83,7 @@ This provides administrators with enormous flexibility when it comes to deciding Policy property values can be configured at the time a policy is created. In addition to that, you can, at any time, use the `Set-CsConferencingPolicy` cmdlet to modify the property values of an existing policy. -The following parameters are not applicable to Skype for Business Online: ApplicationSharingMode, AsJob, AudioBitRateKb, Description, EnableMultiViewJoin, EnableOnlineMeetingPromptForLyncResources, EnableReliableConferenceDeletion, FileTransferBitRateKb, Force, Identity, Instance, MaxMeetingSize, MaxVideoConferenceResolution, PipelineVariable, Tenant, and TotalReceiveVideoBitRateKb +The following parameters are not applicable to Skype for Business Online: ApplicationSharingMode, AudioBitRateKb, Description, EnableMultiViewJoin, EnableOnlineMeetingPromptForLyncResources, EnableReliableConferenceDeletion, FileTransferBitRateKb, Force, Identity, Instance, MaxMeetingSize, MaxVideoConferenceResolution, PipelineVariable, Tenant, and TotalReceiveVideoBitRateKb ## EXAMPLES @@ -1075,4 +1075,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsConferencingPolicy](New-CsConferencingPolicy.md) [Remove-CsConferencingPolicy](Remove-CsConferencingPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsConfigurationStoreLocation.md b/skype/skype-ps/skype/Set-CsConfigurationStoreLocation.md index e87084224e..e52a31a523 100644 --- a/skype/skype-ps/skype/Set-CsConfigurationStoreLocation.md +++ b/skype/skype-ps/skype/Set-CsConfigurationStoreLocation.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csconfigurationstorelocation +online version: https://learn.microsoft.com/powershell/module/skype/set-csconfigurationstorelocation applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsConfigurationStoreLocation schema: 2.0.0 @@ -255,4 +255,3 @@ The `Set-CsConfigurationStoreLocation` cmdlet does not return any objects or val [Get-CsConfigurationStoreLocation](Get-CsConfigurationStoreLocation.md) [Remove-CsConfigurationStoreLocation](Remove-CsConfigurationStoreLocation.md) - diff --git a/skype/skype-ps/skype/Set-CsConversationHistoryConfiguration.md b/skype/skype-ps/skype/Set-CsConversationHistoryConfiguration.md index 9bf230e8f6..4852521547 100644 --- a/skype/skype-ps/skype/Set-CsConversationHistoryConfiguration.md +++ b/skype/skype-ps/skype/Set-CsConversationHistoryConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csconversationhistoryconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csconversationhistoryconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsConversationHistoryConfiguration schema: 2.0.0 @@ -220,4 +220,3 @@ Instead, `Set-CsConversationHistoryConfiguration` modifies instances of the Micr [Get-CsConversationHistoryConfiguration](Get-CsConversationHistoryConfiguration.md) [Remove-CsConversationHistoryConfiguration](Remove-CsConversationHistoryConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsCpsConfiguration.md b/skype/skype-ps/skype/Set-CsCpsConfiguration.md index dc8e5d6f03..ae868b8cba 100644 --- a/skype/skype-ps/skype/Set-CsCpsConfiguration.md +++ b/skype/skype-ps/skype/Set-CsCpsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cscpsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cscpsconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsCpsConfiguration schema: 2.0.0 @@ -264,4 +264,3 @@ Modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.Call [Get-CsCpsConfiguration](Get-CsCpsConfiguration.md) [Set-CsCallParkServiceMusicOnHoldFile](Set-CsCallParkServiceMusicOnHoldFile.md) - diff --git a/skype/skype-ps/skype/Set-CsDeviceUpdateConfiguration.md b/skype/skype-ps/skype/Set-CsDeviceUpdateConfiguration.md index 5dd5a7f393..8f111fabab 100644 --- a/skype/skype-ps/skype/Set-CsDeviceUpdateConfiguration.md +++ b/skype/skype-ps/skype/Set-CsDeviceUpdateConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdeviceupdateconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csdeviceupdateconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDeviceUpdateConfiguration schema: 2.0.0 @@ -375,4 +375,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsDeviceUpdateConfiguration](New-CsDeviceUpdateConfiguration.md) [Remove-CsDeviceUpdateConfiguration](Remove-CsDeviceUpdateConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsDiagnosticConfiguration.md b/skype/skype-ps/skype/Set-CsDiagnosticConfiguration.md index 1a481cfdee..505b7d16bb 100644 --- a/skype/skype-ps/skype/Set-CsDiagnosticConfiguration.md +++ b/skype/skype-ps/skype/Set-CsDiagnosticConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdiagnosticconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csdiagnosticconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDiagnosticConfiguration schema: 2.0.0 @@ -283,4 +283,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsDiagnosticsFilter](New-CsDiagnosticsFilter.md) [Remove-CsDiagnosticConfiguration](Remove-CsDiagnosticConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsDiagnosticHeaderConfiguration.md b/skype/skype-ps/skype/Set-CsDiagnosticHeaderConfiguration.md index 848b23262a..4d2cb97630 100644 --- a/skype/skype-ps/skype/Set-CsDiagnosticHeaderConfiguration.md +++ b/skype/skype-ps/skype/Set-CsDiagnosticHeaderConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdiagnosticheaderconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csdiagnosticheaderconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDiagnosticHeaderConfiguration schema: 2.0.0 @@ -250,4 +250,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [New-CsDiagnosticHeaderConfiguration](New-CsDiagnosticHeaderConfiguration.md) [Remove-CsDiagnosticHeaderConfiguration](Remove-CsDiagnosticHeaderConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsDialInConferencingAccessNumber.md b/skype/skype-ps/skype/Set-CsDialInConferencingAccessNumber.md index 9ebe876b01..01205b59cd 100644 --- a/skype/skype-ps/skype/Set-CsDialInConferencingAccessNumber.md +++ b/skype/skype-ps/skype/Set-CsDialInConferencingAccessNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdialinconferencingaccessnumber +online version: https://learn.microsoft.com/powershell/module/skype/set-csdialinconferencingaccessnumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDialInConferencingAccessNumber schema: 2.0.0 @@ -422,4 +422,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Xds.Acc [New-CsDialInConferencingAccessNumber](New-CsDialInConferencingAccessNumber.md) [Remove-CsDialInConferencingAccessNumber](Remove-CsDialInConferencingAccessNumber.md) - diff --git a/skype/skype-ps/skype/Set-CsDialInConferencingConfiguration.md b/skype/skype-ps/skype/Set-CsDialInConferencingConfiguration.md index 48cf48e60d..05992d1033 100644 --- a/skype/skype-ps/skype/Set-CsDialInConferencingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsDialInConferencingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdialinconferencingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csdialinconferencingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDialInConferencingConfiguration schema: 2.0.0 @@ -288,4 +288,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [New-CsDialInConferencingConfiguration](New-CsDialInConferencingConfiguration.md) [Remove-CsDialInConferencingConfiguration](Remove-CsDialInConferencingConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsDialInConferencingDtmfConfiguration.md b/skype/skype-ps/skype/Set-CsDialInConferencingDtmfConfiguration.md index 3a75ba8707..f9a7d636a3 100644 --- a/skype/skype-ps/skype/Set-CsDialInConferencingDtmfConfiguration.md +++ b/skype/skype-ps/skype/Set-CsDialInConferencingDtmfConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdialinconferencingdtmfconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csdialinconferencingdtmfconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDialInConferencingDtmfConfiguration schema: 2.0.0 @@ -370,4 +370,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsDialInConferencingDtmfConfiguration](New-CsDialInConferencingDtmfConfiguration.md) [Remove-CsDialInConferencingDtmfConfiguration](Remove-CsDialInConferencingDtmfConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsDialPlan.md b/skype/skype-ps/skype/Set-CsDialPlan.md index ab43fd0171..f8e44ed1dd 100644 --- a/skype/skype-ps/skype/Set-CsDialPlan.md +++ b/skype/skype-ps/skype/Set-CsDialPlan.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdialplan +online version: https://learn.microsoft.com/powershell/module/skype/set-csdialplan applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDialPlan schema: 2.0.0 @@ -353,4 +353,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsVoiceNormalizationRule](Remove-CsVoiceNormalizationRule.md) [Get-CsVoiceNormalizationRule](Get-CsVoiceNormalizationRule.md) - diff --git a/skype/skype-ps/skype/Set-CsDirector.md b/skype/skype-ps/skype/Set-CsDirector.md index 412bbfe37c..49d7fa107e 100644 --- a/skype/skype-ps/skype/Set-CsDirector.md +++ b/skype/skype-ps/skype/Set-CsDirector.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csdirector +online version: https://learn.microsoft.com/powershell/module/skype/set-csdirector applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsDirector schema: 2.0.0 @@ -318,4 +318,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsEdgeServer.md b/skype/skype-ps/skype/Set-CsEdgeServer.md index 6e3a53e9e5..5f2b5044cf 100644 --- a/skype/skype-ps/skype/Set-CsEdgeServer.md +++ b/skype/skype-ps/skype/Set-CsEdgeServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csedgeserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csedgeserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsEdgeServer schema: 2.0.0 @@ -432,4 +432,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md b/skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md index 72416d2df0..25d66021cd 100644 --- a/skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md +++ b/skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csenhancedemergencyservicedisclaimer +online version: https://learn.microsoft.com/powershell/module/skype/set-csenhancedemergencyservicedisclaimer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsEnhancedEmergencyServiceDisclaimer schema: 2.0.0 @@ -35,7 +35,7 @@ Set-CsEnhancedEmergencyServiceDisclaimer [-Instance <PSObject>] [-Body <String>] ## DESCRIPTION In order for an Enterprise Voice implementation to provide E9-1-1 service, locations must be mapped to ports, subnets, switches and wireless access points to identify the caller's location. -When the caller is connecting from outside one of these mapped points, he must enter his location manually for it to be received by emergency services. +When the caller is connecting from outside one of these mapped points, they must enter their location manually for it to be received by emergency services. This cmdlet sets a text string that will be displayed to users who decide not to enter their location information. This message will be displayed only if the LocationRequired property of the user's location policy is set to Disclaimer. (You can retrieve location policy settings by calling the `Get-CsLocationPolicy` cmdlet.) @@ -175,4 +175,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Loc [Get-CsEnhancedEmergencyServiceDisclaimer](Get-CsEnhancedEmergencyServiceDisclaimer.md) [Get-CsLocationPolicy](Get-CsLocationPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsExUmContact.md b/skype/skype-ps/skype/Set-CsExUmContact.md index 58171eca36..aaee007975 100644 --- a/skype/skype-ps/skype/Set-CsExUmContact.md +++ b/skype/skype-ps/skype/Set-CsExUmContact.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csexumcontact +online version: https://learn.microsoft.com/powershell/module/skype/set-csexumcontact applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsExUmContact schema: 2.0.0 @@ -315,4 +315,3 @@ When the PassThru parameter is used, it also returns an object of this type. [Get-CsExUmContact](Get-CsExUmContact.md) [Move-CsExUmContact](Move-CsExUmContact.md) - diff --git a/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md b/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md index d9a7bf1ce7..7261e645e0 100644 --- a/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md +++ b/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md @@ -1,10 +1,9 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csexternalaccesspolicy -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csexternalaccesspolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsExternalAccessPolicy schema: 2.0.0 -manager: bulenteg author: tomkau ms.author: tomkau ms.reviewer: rogupta @@ -13,26 +12,28 @@ ms.reviewer: rogupta # Set-CsExternalAccessPolicy ## SYNOPSIS +> [!NOTE] +> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter EnablePublicCloudAccess can no longer be used. + Enables you to modify the properties of an existing external access policy. -External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as MSN and 3) access Skype for Business Server over the Internet, without having to log on to your internal network. -This cmdlet was introduced in Lync Server 2010. +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services](/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype; and, 5) communicate with people who are using Teams with an account that's not managed by an organization. +This cmdlet was introduced in Lync Server 2010. ## SYNTAX ### Identity (Default) ``` -Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] - [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>] - [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableOutsideAccess <Boolean>] [[-Identity] <XdsIdentity>] +Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>] + [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableTeamsConsumerAccess <Boolean>] [-EnableTeamsConsumerInbound <Boolean>] [-EnableOutsideAccess <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ### Instance ``` -Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] - [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>] - [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableOutsideAccess <Boolean>] [-Instance <PSObject>] +Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>] + [-EnableXmppAccess <Boolean>] + [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableTeamsConsumerAccess <Boolean>] [-EnableTeamsConsumerInbound <Boolean>] [-EnableOutsideAccess <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` @@ -44,24 +45,25 @@ That might be sufficient to meet your communication needs. If it doesn't meet your needs, you can use external access policies to extend the ability of your users to communicate and collaborate. External access policies can grant (or revoke) the ability of your users to do any or all of the following: -1. -Communicate with people who have SIP accounts with a federated organization. +1. Communicate with people who have SIP accounts with a federated organization. Note that enabling federation alone will not provide users with this capability. Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. -2. -Communicate with people who have SIP accounts with a public instant messaging service such as MSN. +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration). -3. -Access Skype for Business Server over the Internet, without having to first log on to your internal network. +3. Access Skype for Business Server over the Internet, without having to first log on to your internal network. This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. +4. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. + + The following parameters are not applicable to Skype for Business Online/Microsoft Teams: Description, EnableXmppAccess, Force, Identity, Instance, PipelineVariable, and Tenant + +5. (Microsoft Teams Only) Communicate with people who are using Teams with an account that's not managed by an organization. This policy only applies if Teams Consumer Federation has been enabled at the tenant level using the cmdlet [Set-CsTenantFederationConfiguration](/powershell/module/skype/set-cstenantfederationconfiguration) or Teams admin center under the External Access setting. + After an external access policy has been created, you can use the `Set-CsExternalAccessPolicy` cmdlet to change the property values of that policy. For example, by default the global policy does not allow users to communicate with people who have accounts with a federated organization. If you would like to grant this capability to all of your users you can call the `Set-CsExternalAccessPolicy` cmdlet and set the value of the global policy's EnableFederationAccess property to True. -The following parameters are not applicable to Skype for Business Online: AsJob, Description, EnableXmppAccess, Force, Identity, Instance, PipelineVariable, and Tenant - ## EXAMPLES ### -------------------------- Example 1 ------------------------ @@ -72,7 +74,6 @@ Set-CsExternalAccessPolicy -Identity RedmondExternalAccessPolicy -EnableFederati The command shown in Example 1 modifies the per-user external access policy that has the Identity RedmondExternalAccessPolicy. In this example, the command changes the value of the EnableFederationAccess property to True. - ### -------------------------- Example 2 ------------------------ ``` Get-CsExternalAccessPolicy | Set-CsExternalAccessPolicy -EnableFederationAccess $True @@ -82,29 +83,31 @@ In Example 2, federation access is enabled for all the external access policies To do this, the command first calls the `Get-CsExternalAccessPolicy` cmdlet without any parameters; this returns a collection of all the external policies currently configured for use. That collection is then piped to the `Set-CsExternalAccessPolicy` cmdlet, which changes the value of the EnableFederationAccess property for each policy in the collection. - ### -------------------------- Example 3 ------------------------ ``` Get-CsExternalAccessPolicy -Filter tag:* | Set-CsExternalAccessPolicy -EnableFederationAccess $True ``` Example 3 enables federation access for all the external access policies that have been configured at the per-user scope. -To carry out this task, the first thing the command does is use the `Get-CsExternalAcessPolicy` cmdlet and the Filter parameter to return a collection of all the policies that have been configured at the per-user scope. +To carry out this task, the first thing the command does is use the `Get-CsExternalAccessPolicy` cmdlet and the Filter parameter to return a collection of all the policies that have been configured at the per-user scope. (The filter value "tag:*" limits returned data to policies that have an Identity that begins with the string value "tag:". Any policy with an Identity that begins with "tag:" has been configured at the per-user scope.) The filtered collection is then piped to the `Set-CsExternalAccessPolicy` cmdlet, which modifies the EnableFederationAccess property for each policy in the collection. - ### -------------------------- Example 4 ------------------------ ``` -Get-CsExternalAccessPolicy | Where-Object {$_.EnablePublicCloudAccess -eq $True} | Set-CsExternalAccessPolicy -EnableFederationAccess $True +Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $false +New-CsExternalAccessPolicy -Identity AcsFederationAllowed -EnableAcsFederationAccess $true ``` -In Example 4, federation access is enabled for all the external access policies that allow public cloud access. -To do this, the command first uses the `Get-CsExternalAccessPolicy` cmdlet to return a collection of all the external access policies currently configured for use in the organization. -This collection is piped to the `Where-Object` cmdlet, which picks out only those policies where the EnablePublicCloudAccess property is equal to True. -The filtered collection is then piped to the `Set-CsExternalAccessPolicy` cmdlet, which takes each policy and sets the EnableFederationAccess property to True. -The net result: all external access policies that allow public cloud access will also allow federation access. +In this example, the Global policy is updated to disallow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation enabled and which can be assigned to selected users for which Team-ACS federation will be allowed. + +### -------------------------- Example 5 ------------------------ +``` +Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $true +New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed -EnableAcsFederationAccess $false +``` +In this example, the Global policy is updated to allow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation disabled and which can then be assigned to selected users for which Team-ACS federation will not be allowed. ## PARAMETERS @@ -121,7 +124,7 @@ Note that wildcards are not allowed when specifying an Identity. ```yaml Type: XdsIdentity Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -137,7 +140,7 @@ Allows you to pass a reference to an object to the cmdlet rather than set indivi ```yaml Type: PSObject Parameter Sets: Instance -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -151,11 +154,10 @@ Accept wildcard characters: False Enables administrators to provide additional text to accompany the policy. For example, the Description might include information about the users the policy should be assigned to. - ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -167,13 +169,13 @@ Accept wildcard characters: False ### -EnableFederationAccess Indicates whether the user is allowed to communicate with people who have SIP accounts with a federated organization. -The default value is False. - +Read [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -183,20 +185,23 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -EnablePublicCloudAccess -Indicates whether the user is allowed to communicate with people who have SIP accounts with a public Internet connectivity provider such as MSN. -The default value is False. +### -EnableAcsFederationAccess +Indicates whether Teams meeting organized by the user can be joined by users of customer applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration. + +Additionally, Azure Communication Services users would be able to call Microsoft 365 users that have assigned policies with enabled federation. +To enable for all users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to True. It can be disabled for selected users by assigning them a policy with federation disabled. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 - +Aliases: +Applicable: Microsoft Teams Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -206,11 +211,10 @@ Indicates whether the user is allowed to conduct audio/video conversations with When set to False, audio and video options in Skype for Business will be disabled any time a user is communicating with a public Internet connectivity contact. The default value is False. - ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -220,14 +224,55 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnableTeamsConsumerAccess +(Microsoft Teams Only) Indicates whether the user is allowed to communicate with people who have who are using Teams with an account that's not managed by an organization. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsConsumerInbound +(Microsoft Teams Only) Indicates whether the user is allowed to be discoverable by people who are using Teams with an account that's not managed by an organization. It also controls if people who have who are using Teams with an account that's not managed by an organization can start the communication with the user. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Force Suppresses the display of any non-fatal error message that might occur when running the command. - ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -240,7 +285,6 @@ Accept wildcard characters: False ### -WhatIf Describes what would happen if you executed the command without actually executing the command. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -257,7 +301,6 @@ Accept wildcard characters: False ### -Confirm Prompts you for confirmation before executing the command. - ```yaml Type: SwitchParameter Parameter Sets: (All) @@ -275,11 +318,10 @@ Accept wildcard characters: False Indicates whether the user is allowed to connect to Skype for Business Server over the Internet, without logging on to the organization's internal network. The default value is False. - ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -293,11 +335,10 @@ Accept wildcard characters: False Indicates whether the user is allowed to communicate with users who have SIP accounts with a federated XMPP (Extensible Messaging and Presence Protocol) partner. The default value is False. - ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -317,7 +358,6 @@ You can return the tenant ID for each of your Skype for Business Online tenants `Get-CsTenant | Select-Object DisplayName, TenantID` - ```yaml Type: Guid Parameter Sets: (All) @@ -357,4 +397,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsExternalAccessPolicy](New-CsExternalAccessPolicy.md) [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsExternalUserCommunicationPolicy.md b/skype/skype-ps/skype/Set-CsExternalUserCommunicationPolicy.md index 8a045b241f..58dfe5fefc 100644 --- a/skype/skype-ps/skype/Set-CsExternalUserCommunicationPolicy.md +++ b/skype/skype-ps/skype/Set-CsExternalUserCommunicationPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csexternalusercommunicationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csexternalusercommunicationpolicy applicable: Skype for Business Online title: Set-CsExternalUserCommunicationPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsExternalUserCommunicationPolicy @@ -35,7 +35,7 @@ Set-CsExternalUserCommunicationPolicy [-Tenant <Guid>] [-EnableFileTransfer <Boo ## DESCRIPTION -The following parameters are not applicable to Skype for Business Online: AllowPresenceVisibility, AllowTitleVisibility, AsJob, EnableFileTransfer, Force, Identity, Instance, PipelineVariable, and Tenant +The following parameters are not applicable to Skype for Business Online: AllowPresenceVisibility, AllowTitleVisibility, EnableFileTransfer, Force, Identity, Instance, PipelineVariable, and Tenant ## EXAMPLES @@ -225,4 +225,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsFIPSConfiguration.md b/skype/skype-ps/skype/Set-CsFIPSConfiguration.md index d5d7da6393..609a96b73c 100644 --- a/skype/skype-ps/skype/Set-CsFIPSConfiguration.md +++ b/skype/skype-ps/skype/Set-CsFIPSConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csfipsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csfipsconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsFIPSConfiguration schema: 2.0.0 @@ -215,4 +215,3 @@ Instead, the `Set-CsFIPSConfiguration` cmdlet modifies existing instances of the [New-CsFIPSConfiguration](New-CsFIPSConfiguration.md) [Remove-CsFIPSConfiguration](Remove-CsFIPSConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsFileTransferFilterConfiguration.md b/skype/skype-ps/skype/Set-CsFileTransferFilterConfiguration.md index 0a52ccb3ec..711fda67d7 100644 --- a/skype/skype-ps/skype/Set-CsFileTransferFilterConfiguration.md +++ b/skype/skype-ps/skype/Set-CsFileTransferFilterConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csfiletransferfilterconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csfiletransferfilterconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsFileTransferFilterConfiguration schema: 2.0.0 @@ -277,4 +277,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsFileTransferFilterConfiguration](Remove-CsFileTransferFilterConfiguration.md) [Get-CsFileTransferFilterConfiguration](Get-CsFileTransferFilterConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsGroupPickupUserOrbit.md b/skype/skype-ps/skype/Set-CsGroupPickupUserOrbit.md index 84e714359a..5b56d01e9e 100644 --- a/skype/skype-ps/skype/Set-CsGroupPickupUserOrbit.md +++ b/skype/skype-ps/skype/Set-CsGroupPickupUserOrbit.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csgrouppickupuserorbit +online version: https://learn.microsoft.com/powershell/module/skype/set-csgrouppickupuserorbit applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsGroupPickupUserOrbit schema: 2.0.0 @@ -43,7 +43,7 @@ In this case, the display name "Ken Myer". ### -Orbit Specifies the new group pickup orbit number to be assigned to the user. The number must be within an orbit pickup range that was created with a type of GroupPickup. -For more information on creating call park orbits, see `New-CsCallParkOrbit` (https://technet.microsoft.com/en-us/library/gg398936.aspx). +For more information on creating call park orbits, see [New-CsCallParkOrbit](https://learn.microsoft.com/powershell/module/skype/New-CsCallParkOrbit). Values for the Orbit parameter must match the regular expression (\[\*|#\]?\[1-9\]\d{0,7})|(\[1-9\]\d{0,8}). @@ -145,4 +145,3 @@ This cmdlet returns an instance of the Microsoft.Rtc.Management.Voice.Helpers.Gr ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsHealthMonitoringConfiguration.md b/skype/skype-ps/skype/Set-CsHealthMonitoringConfiguration.md index 573ff350dc..6ad6748d7f 100644 --- a/skype/skype-ps/skype/Set-CsHealthMonitoringConfiguration.md +++ b/skype/skype-ps/skype/Set-CsHealthMonitoringConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshealthmonitoringconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cshealthmonitoringconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsHealthMonitoringConfiguration schema: 2.0.0 @@ -267,4 +267,3 @@ Instead, the `Set-CsHealthMonitoringConfiguration` cmdlet modifies existing inst [New-CsHealthMonitoringConfiguration](New-CsHealthMonitoringConfiguration.md) [Remove-CsHealthMonitoringConfiguration](Remove-CsHealthMonitoringConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsHostedVoicemailPolicy.md b/skype/skype-ps/skype/Set-CsHostedVoicemailPolicy.md index cd95c06931..812ec3758b 100644 --- a/skype/skype-ps/skype/Set-CsHostedVoicemailPolicy.md +++ b/skype/skype-ps/skype/Set-CsHostedVoicemailPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshostedvoicemailpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-cshostedvoicemailpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsHostedVoicemailPolicy schema: 2.0.0 @@ -268,4 +268,3 @@ This cmdlet modifies an object of type Microsoft.Rtc.Management.WritableConfig.P [Get-CsHostedVoicemailPolicy](Get-CsHostedVoicemailPolicy.md) [Grant-CsHostedVoicemailPolicy](Grant-CsHostedVoicemailPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsHostingProvider.md b/skype/skype-ps/skype/Set-CsHostingProvider.md index 7ca401955a..0e74e387f7 100644 --- a/skype/skype-ps/skype/Set-CsHostingProvider.md +++ b/skype/skype-ps/skype/Set-CsHostingProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshostingprovider +online version: https://learn.microsoft.com/powershell/module/skype/set-cshostingprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsHostingProvider schema: 2.0.0 @@ -343,4 +343,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsHostingProvider](New-CsHostingProvider.md) [Remove-CsHostingProvider](Remove-CsHostingProvider.md) - diff --git a/skype/skype-ps/skype/Set-CsHuntGroup.md b/skype/skype-ps/skype/Set-CsHuntGroup.md deleted file mode 100644 index d77458db93..0000000000 --- a/skype/skype-ps/skype/Set-CsHuntGroup.md +++ /dev/null @@ -1,510 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshuntgroup -applicable: Skype for Business Online -title: Set-CsHuntGroup -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsHuntGroup - -## SYNOPSIS -Updates a Call Queue in your Skype for Business Online organization. - -## SYNTAX - -``` -Set-CsHuntGroup -PrimaryUri <System.Uri> [-AgentAlertTime <Int16>] [-AllowOptOut <System.Boolean>] [-DistributionLists <System.Collections.Generic.List`1[System.Guid]>] [-LineUri <System.Uri>] - [-MusicOnHoldFileContent <System.Byte[]>] [-MusicOnHoldFileName <System.String>] [-Name <System.String>] - [-OverflowAction <Microsoft.Rtc.Management.Hosted.HuntGroup.Models.OverflowAction>] [-OverflowActionTarget <System.Uri>] [-OverflowThreshold <Int16>] - [-RoutingMethod <Microsoft.Rtc.Management.Hosted.HuntGroup.Models.RoutingMethod>] [-TimeoutAction <Microsoft.Rtc.Management.Hosted.HuntGroup.Models.TimeoutAction>] - [-TimeoutActionTarget <System.Uri>] [-TimeoutThreshold <Int16>] [-UseDefaultMusicOnHold <System.Boolean>] [-WelcomeMusicFileContent <System.Byte[]>] - [-WelcomeMusicFileName <System.String>] [<CommonParameters>] -``` - -## DESCRIPTION - -Set-CsHuntGroup cmdlet provides a way for you to modify the properties of an existing Call Queue; for example, you can change the phone number for the Call Queue, the distribution lists associated with the Call Queue, or the welcome audio file. - -The Set-CsHuntGroup cmdlet may suggest additional steps required to complete the Call Queue setup. - -The following parameters are not applicable to Skype for Business Online: AsJob, ClientAudience, DomainController, Force, HuntGroupServiceCallbackUri, and PipelineVariable - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsHuntGroup -PrimaryUri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com" -UseDefaultMusicOnHold $true -``` - -This example updates the Call Queue with primary uri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com" by making it use the default music on hold. - -### -------------------------- Example 2 -------------------------- -``` -$musicOnHoldContent = Get-Content ".\MusicOnHold.wav" -ReadCount 0 -Encoding Byte -Set-CsHuntGroup -PrimaryUri "sip:hg_a82e2406b9b5474a9878e9659f32dbc3@litwareinc.com" -LineUri "tel:+19998881234" -DistributionLists @("8521b0e3-51bd-4a4b-a8d6-b219a77a0a6a", "868dccd8-d723-4b4f-8d74-ab59e207c357") -MusicOnHoldFileName "MusicOnHold.wav" -MusicOnHoldFileContent $musicOnHoldContent -``` - -This example saves the contents of music on hold to a temporary variable. Then, it updates the Call Queue with new phone number, distribution lists, and the name and content of the music on hold file. - - -## PARAMETERS - -### -PrimaryUri -The PrimaryUri parameter represents the SIP address for the Call Queue. It must start with "sip:". - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AgentAlertTime -The AgentAlertTime parameter represents the time (in seconds) that a call can remain unanswered before it is automatically routed to the next agent. The AgentAlertTime can be set to any integer value between 30 and 180 seconds (3 minutes), inclusive. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 30 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOptOut -The AllowOptOut parameter indicates whether or not agents can opt in or opt out from taking calls from a Call Queue. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DistributionLists -The DistributionLists parameter lets you add all the members of the distribution lists to the Call Queue. This is a list of distribution list GUIDs. A service wide configurable maximum number of DLs per Call Queue are allowed. Only the first N (service wide configurable) agents from all distribution lists combined are considered for accepting the call. Nested DLs are supported. O365 Groups can also be used to add members to the Call Queue. - -```yaml -Type: System.Collections.Generic.List`1[System.Guid] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LineUri -The LineUri parameter is the phone number for the Call Queue. The line Uniform Resource Identifier (URI) must be specified by using the following format: the tel: prefix followed by a plus sign, followed by the country/region calling code, area code, and phone number (using only digits: no blank spaces, periods, or hyphens). For example: -LineUri "tel:+14255551219". - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MusicOnHoldFileContent -The MusicOnHoldFileContent parameter represents music to play when callers are placed on hold. This is the content of the audio file. Supported formats are: .wav, .mp3, and .wma. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. - -```yaml -Type: System.Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MusicOnHoldFileName -The MusicOnHoldFileName parameter represents music to play when callers are placed on hold. This is the name of the audio file. Supported formats are: .wav, .mp3, and .wma. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -The Name parameter specifies a unique name for the Call Queue. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowAction -The OverflowAction parameter designates the action to take if the overflow threshold is reached. The OverflowAction property must be set to one of the following three values: DisconnectWithBusy, Forward, and Voicemail. - -PARAMVALUE: DisconnectWithBusy | Forward | Voicemail - -```yaml -Type: Microsoft.Rtc.Management.Hosted.HuntGroup.Models.OverflowAction -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: DisconnectWithBusy -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowActionTarget -The OverflowActionTarget parameter represents the target of the overflow action. If the OverFlowAction is set to Forward, this parameter must be set to a SIP address. Otherwise, this parameter is optional. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OverflowThreshold -The OverflowThreshold parameter defines the number of calls that can be in the queue at any one time before the overflow action is triggered. The OverflowThreshold can be any integer value between 0 and 200, inclusive. A value of 0 causes calls not to reach agents and the overflow action to be taken immediately. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 50 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RoutingMethod -The RoutingMethod defines how agents will be called in a Call Queue. If the routing method is set to Serial, then agents will be called one at a time. If the routing method is set to Attendant, then agents will be called in parallel. - -PARAMVALUE: Attendant | Serial - -```yaml -Type: Microsoft.Rtc.Management.Hosted.HuntGroup.Models.RoutingMethod -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Attendant -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutAction -The TimeoutAction parameter defines the action to take if the timeout threshold is reached. The TimeoutAction property must be set to one of the following three values: Disconnect, Forward, and Voicemail. The default value is Disconnect. - -PARAMVALUE: Disconnect | Forward | Voicemail - -```yaml -Type: Microsoft.Rtc.Management.Hosted.HuntGroup.Models.TimeoutAction -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Disconnect -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutActionTarget -The TimeoutActionTarget represents the target of the timeout action. If the TimeoutAction is set to Forward, this parameter must be set to a SIP address. Otherwise, this field is optional. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeoutThreshold -The TimeoutThreshold parameter defines the time (in seconds) that a call can be in the queue before that call times out. At that point, the system will take the action specified by the TimeoutAction parameter. -The TimeoutThreshold can be any integer value between 0 and 2700 seconds (inclusive), and is rounded to the nearest 15th interval. For example, if set to 47 seconds, then it is rounded down to 45. If set to 0, welcome music is played, and then the timeout action will be taken. - -```yaml -Type: Int16 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: 1200 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseDefaultMusicOnHold -The UseDefaultMusicOnHold parameter indicates that this Call Queue uses the default music on hold. This parameter cannot be specified together with MusicOnHoldFileName and MusicOnHoldFileContent. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WelcomeMusicFileContent -The WelcomeMusicFileContent parameter represents the audio file to play when callers are connected with the Call Queue. This is the content of the audio file. Supported formats are: .wav, .mp3, .and wma. - -```yaml -Type: System.Byte[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WelcomeMusicFileName -The WelcomeMusicFileName parameter represents audio file to play when callers are connected with the Call Queue. This is the name to the audio file. Supported formats are: .wav, .mp3, and .wma. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassDualWrite -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ClientAudience -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing, and requires confirmation to proceed. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for Microsoft internal use only. - -PARAMVALUE: Fqdn - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HuntGroupServiceCallbackUri -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.HuntGroup.Models.HuntGroup - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsHybridApplicationEndpoint.md b/skype/skype-ps/skype/Set-CsHybridApplicationEndpoint.md index d241d61daf..33c98d57dc 100644 --- a/skype/skype-ps/skype/Set-CsHybridApplicationEndpoint.md +++ b/skype/skype-ps/skype/Set-CsHybridApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/set-cshybridapplicationendpoint applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsHybridApplicationEndpoint schema: 2.0.0 @@ -23,7 +23,7 @@ Set-CsHybridApplicationEndpoint [-Identity] <HybridApplicationEndpointIdParamete ``` ## DESCRIPTION -The `Set-CsHybridApplicationEndpoint` cmdlet enables you to modify the Skype for Business Server related hybrid application endpoint attributes that are stored in Active Directory Domain Services. For example, you can modify an enpoint's line URI number; or modify an enpoint's display name. +The `Set-CsHybridApplicationEndpoint` cmdlet enables you to modify the Skype for Business Server related hybrid application endpoint attributes that are stored in Active Directory Domain Services. For example, you can modify an endpoint's line URI number; or modify an endpoint's display name. ## EXAMPLES @@ -164,8 +164,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[New-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint?view=skype-ps) +[New-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/new-cshybridapplicationendpoint?view=skype-ps) -[Get-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint?view=skype-ps) +[Get-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/get-cshybridapplicationendpoint?view=skype-ps) -[Remove-CsHybridApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint?view=skype-ps) +[Remove-CsHybridApplicationEndpoint](https://learn.microsoft.com/powershell/module/skype/remove-cshybridapplicationendpoint?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsHybridMediationServer.md b/skype/skype-ps/skype/Set-CsHybridMediationServer.md index c19c96a56f..22cc44dca7 100644 --- a/skype/skype-ps/skype/Set-CsHybridMediationServer.md +++ b/skype/skype-ps/skype/Set-CsHybridMediationServer.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshybridmediationserver +online version: https://learn.microsoft.com/powershell/module/skype/set-cshybridmediationserver applicable: Skype for Business Online title: Set-CsHybridMediationServer schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsHybridMediationServer @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Sets the external FQDN of an Edge server access proxy as the hosting provider for a user. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` @@ -158,4 +160,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS [Get-CsHybridMediationServer](Get-CsHybridMediationServer.md) - diff --git a/skype/skype-ps/skype/Set-CsHybridPSTNAppliance.md b/skype/skype-ps/skype/Set-CsHybridPSTNAppliance.md index 097f011c70..b3f6d8058f 100644 --- a/skype/skype-ps/skype/Set-CsHybridPSTNAppliance.md +++ b/skype/skype-ps/skype/Set-CsHybridPSTNAppliance.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshybridpstnappliance +online version: https://learn.microsoft.com/powershell/module/skype/set-cshybridpstnappliance applicable: Skype for Business Online title: Set-CsHybridPSTNAppliance schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsHybridPSTNAppliance @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the `Set-CsHybridPSTNAppliance` cmdlet to modify an existing Skype for Business Cloud Connector Edition appliance's attributes. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -194,4 +196,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsHybridPSTNSite.md b/skype/skype-ps/skype/Set-CsHybridPSTNSite.md index d33abb947c..9cc149848a 100644 --- a/skype/skype-ps/skype/Set-CsHybridPSTNSite.md +++ b/skype/skype-ps/skype/Set-CsHybridPSTNSite.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cshybridpstnsite +online version: https://learn.microsoft.com/powershell/module/skype/set-cshybridpstnsite applicable: Skype for Business Online title: Set-CsHybridPSTNSite schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsHybridPSTNSite @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the `Set-CsHybridPSTNSite` cmdlet to modify an existing hybrid public switched telephone network (PSTN) site's attributes. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -241,4 +243,3 @@ None. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsIPPhonePolicy.md b/skype/skype-ps/skype/Set-CsIPPhonePolicy.md index 48aa0844a4..944e00aac7 100644 --- a/skype/skype-ps/skype/Set-CsIPPhonePolicy.md +++ b/skype/skype-ps/skype/Set-CsIPPhonePolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csipphonepolicy -applicable: Skype for Business Online, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csipphonepolicy +applicable: Skype for Business Server 2019 title: Set-CsIPPhonePolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsIPPhonePolicy @@ -439,4 +439,3 @@ The `Set-CsIPPhonePolicy` cmdlet does not return a value or object. However, if ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsImConfiguration.md b/skype/skype-ps/skype/Set-CsImConfiguration.md index c3bb7b2c96..d086c199eb 100644 --- a/skype/skype-ps/skype/Set-CsImConfiguration.md +++ b/skype/skype-ps/skype/Set-CsImConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csimconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csimconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsImConfiguration schema: 2.0.0 @@ -169,8 +169,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[Get-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/get-csimconfiguration?view=skype-ps) +[Get-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/get-csimconfiguration?view=skype-ps) -[New-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/new-csimconfiguration?view=skype-ps) +[New-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/new-csimconfiguration?view=skype-ps) -[Remove-CsImConfiguration](https://docs.microsoft.com/powershell/module/skype/remove-csimconfiguration?view=skype-ps) +[Remove-CsImConfiguration](https://learn.microsoft.com/powershell/module/skype/remove-csimconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsImFilterConfiguration.md b/skype/skype-ps/skype/Set-CsImFilterConfiguration.md index 9d87be16a9..cbe1b6db70 100644 --- a/skype/skype-ps/skype/Set-CsImFilterConfiguration.md +++ b/skype/skype-ps/skype/Set-CsImFilterConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csimfilterconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csimfilterconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsImFilterConfiguration schema: 2.0.0 @@ -334,4 +334,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsImFilterConfiguration](Remove-CsImFilterConfiguration.md) [Get-CsImFilterConfiguration](Get-CsImFilterConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsImTranslationConfiguration.md b/skype/skype-ps/skype/Set-CsImTranslationConfiguration.md index af9e0b701f..4b9375f9fb 100644 --- a/skype/skype-ps/skype/Set-CsImTranslationConfiguration.md +++ b/skype/skype-ps/skype/Set-CsImTranslationConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csimtranslationconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csimtranslationconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsImTranslationConfiguration schema: 2.0.0 @@ -232,4 +232,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md b/skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md deleted file mode 100644 index 3cdf4469f4..0000000000 --- a/skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csinboundblockednumberpattern -applicable: Skype for Business Online -title: Set-CsInboundBlockedNumberPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# Set-CsInboundBlockedNumberPattern - -## SYNOPSIS -Modifies one or more parameters of a blocked number pattern in the tenant list. - -## SYNTAX - -### Identity (Default) -``` -Set-CsInboundBlockedNumberPattern [-Tenant <Guid>] [-Enabled <Boolean>] [-Description <String>] - [-Pattern <String>] [[-Identity] <XdsGlobalRelativeIdentity>] [-Force] [-WhatIf] [-Confirm] - [-AsJob] [<CommonParameters>] -``` - -### Instance -``` -Set-CsInboundBlockedNumberPattern [-Tenant <Guid>] [-Enabled <Boolean>] [-Description <String>] - [-Pattern <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [-AsJob] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet modifies one or more parameters of a blocked number pattern in the tenant list. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Set-CsInboundBlockedNumberPattern -Identity "BlockAutomatic" -Pattern "^\+11234567890" -``` - -This example modifies a blocked number pattern to block inbound calls from +11234567890 number. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A friendly description for the blocked number pattern to be modified. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -If this parameter is set to True, the inbound calls matching the pattern will be blocked. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The *Force* switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the *Force* switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier specifying the blocked number pattern to be modified. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Pattern -A regular expression that the calling number must match in order to be blocked. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the *AsJob* parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the *Receive-Job* cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS - -[New-CsInboundBlockedNumberPattern](New-CsInboundBlockedNumberPattern.md) - -[Get-CsInboundBlockedNumberPattern](Get-CsInboundBlockedNumberPattern.md) - -[Remove-CsInboundBlockedNumberPattern](Remove-CsInboundBlockedNumberPattern.md) diff --git a/skype/skype-ps/skype/Set-CsKerberosAccountAssignment.md b/skype/skype-ps/skype/Set-CsKerberosAccountAssignment.md index da6e4db915..2805bab96e 100644 --- a/skype/skype-ps/skype/Set-CsKerberosAccountAssignment.md +++ b/skype/skype-ps/skype/Set-CsKerberosAccountAssignment.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cskerberosaccountassignment +online version: https://learn.microsoft.com/powershell/module/skype/set-cskerberosaccountassignment applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsKerberosAccountAssignment schema: 2.0.0 @@ -191,4 +191,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [New-CsKerberosAccountAssignment](New-CsKerberosAccountAssignment.md) [Remove-CsKerberosAccountAssignment](Remove-CsKerberosAccountAssignment.md) - diff --git a/skype/skype-ps/skype/Set-CsKerberosAccountPassword.md b/skype/skype-ps/skype/Set-CsKerberosAccountPassword.md index e32370cab2..53c7a9e3e7 100644 --- a/skype/skype-ps/skype/Set-CsKerberosAccountPassword.md +++ b/skype/skype-ps/skype/Set-CsKerberosAccountPassword.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cskerberosaccountpassword +online version: https://learn.microsoft.com/powershell/module/skype/set-cskerberosaccountpassword applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsKerberosAccountPassword schema: 2.0.0 @@ -203,4 +203,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsLisLocation.md b/skype/skype-ps/skype/Set-CsLisLocation.md index a73c29a9be..61ea6408ff 100644 --- a/skype/skype-ps/skype/Set-CsLisLocation.md +++ b/skype/skype-ps/skype/Set-CsLisLocation.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cslislocation +online version: https://learn.microsoft.com/powershell/module/skype/set-cslislocation applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsLisLocation schema: 2.0.0 @@ -588,4 +588,3 @@ It creates or modifies an object of type System.Management.Automation.PSCustomOb [Set-CsLisWirelessAccessPoint](Set-CsLisWirelessAccessPoint.md) [Get-CsLisCivicAddress](Get-CsLisCivicAddress.md) - diff --git a/skype/skype-ps/skype/Set-CsLisPort.md b/skype/skype-ps/skype/Set-CsLisPort.md index 99d327ea44..62814d4f3e 100644 --- a/skype/skype-ps/skype/Set-CsLisPort.md +++ b/skype/skype-ps/skype/Set-CsLisPort.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cslisport +online version: https://learn.microsoft.com/powershell/module/skype/set-cslisport applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsLisPort schema: 2.0.0 @@ -629,4 +629,3 @@ This cmdlet creates or modifies an object of type System.Management.Automation.P [Get-CsLisLocation](Get-CsLisLocation.md) [Get-CsLisSwitch](Get-CsLisSwitch.md) - diff --git a/skype/skype-ps/skype/Set-CsLisServiceProvider.md b/skype/skype-ps/skype/Set-CsLisServiceProvider.md index 17c5f6c908..135b7b925b 100644 --- a/skype/skype-ps/skype/Set-CsLisServiceProvider.md +++ b/skype/skype-ps/skype/Set-CsLisServiceProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cslisserviceprovider +online version: https://learn.microsoft.com/powershell/module/skype/set-cslisserviceprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsLisServiceProvider schema: 2.0.0 @@ -181,4 +181,3 @@ This cmdlet creates or modifies an object of type System.Management.Automation.P [Remove-CsLisServiceProvider](Remove-CsLisServiceProvider.md) [Get-CsLisServiceProvider](Get-CsLisServiceProvider.md) - diff --git a/skype/skype-ps/skype/Set-CsLisSubnet.md b/skype/skype-ps/skype/Set-CsLisSubnet.md index 505001be17..d8f243e8d0 100644 --- a/skype/skype-ps/skype/Set-CsLisSubnet.md +++ b/skype/skype-ps/skype/Set-CsLisSubnet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cslissubnet +online version: https://learn.microsoft.com/powershell/module/skype/set-cslissubnet applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsLisSubnet schema: 2.0.0 @@ -548,4 +548,3 @@ This cmdlet creates or modifies an object of type System.Management.Automation.P [Get-CsLisSubnet](Get-CsLisSubnet.md) [Get-CsLisLocation](Get-CsLisLocation.md) - diff --git a/skype/skype-ps/skype/Set-CsLisSwitch.md b/skype/skype-ps/skype/Set-CsLisSwitch.md index 5990cbdfc8..13f563aa57 100644 --- a/skype/skype-ps/skype/Set-CsLisSwitch.md +++ b/skype/skype-ps/skype/Set-CsLisSwitch.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cslisswitch +online version: https://learn.microsoft.com/powershell/module/skype/set-cslisswitch applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsLisSwitch schema: 2.0.0 @@ -569,4 +569,3 @@ This cmdlet creates or modifies an object of type System.Management.Automation.P [Set-CsLisPort](Set-CsLisPort.md) [Get-CsLisPort](Get-CsLisPort.md) - diff --git a/skype/skype-ps/skype/Set-CsLisWirelessAccessPoint.md b/skype/skype-ps/skype/Set-CsLisWirelessAccessPoint.md index 94c1f86f07..31b0d854db 100644 --- a/skype/skype-ps/skype/Set-CsLisWirelessAccessPoint.md +++ b/skype/skype-ps/skype/Set-CsLisWirelessAccessPoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csliswirelessaccesspoint +online version: https://learn.microsoft.com/powershell/module/skype/set-csliswirelessaccesspoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsLisWirelessAccessPoint schema: 2.0.0 @@ -560,4 +560,3 @@ This cmdlet creates or modifies an object of type System.Management.Automation.P [Get-CsLisWirelessAccessPoint](Get-CsLisWirelessAccessPoint.md) [Get-CsLisLocation](Get-CsLisLocation.md) - diff --git a/skype/skype-ps/skype/Set-CsLocationPolicy.md b/skype/skype-ps/skype/Set-CsLocationPolicy.md index 02022fb7fe..6586f63b11 100644 --- a/skype/skype-ps/skype/Set-CsLocationPolicy.md +++ b/skype/skype-ps/skype/Set-CsLocationPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cslocationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-cslocationpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsLocationPolicy schema: 2.0.0 @@ -482,4 +482,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Get-CsPstnUsage](Get-CsPstnUsage.md) [Get-CsVoiceRoute](Get-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/Set-CsManagementConnection.md b/skype/skype-ps/skype/Set-CsManagementConnection.md index 2395aaeb62..66a2a17e21 100644 --- a/skype/skype-ps/skype/Set-CsManagementConnection.md +++ b/skype/skype-ps/skype/Set-CsManagementConnection.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmanagementconnection +online version: https://learn.microsoft.com/powershell/module/skype/set-csmanagementconnection applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsManagementConnection schema: 2.0.0 @@ -188,4 +188,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Store.S [Remove-CsManagementConnection](Remove-CsManagementConnection.md) [Set-CsConfigurationStoreLocation](Set-CsConfigurationStoreLocation.md) - diff --git a/skype/skype-ps/skype/Set-CsManagementServer.md b/skype/skype-ps/skype/Set-CsManagementServer.md index 1e80e57f44..0d77658545 100644 --- a/skype/skype-ps/skype/Set-CsManagementServer.md +++ b/skype/skype-ps/skype/Set-CsManagementServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmanagementserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csmanagementserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsManagementServer schema: 2.0.0 @@ -149,4 +149,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [Get-CsService](Get-CsService.md) [Move-CsManagementServer](Move-CsManagementServer.md) - diff --git a/skype/skype-ps/skype/Set-CsMcxConfiguration.md b/skype/skype-ps/skype/Set-CsMcxConfiguration.md index b9acb6f8ca..664b12f04d 100644 --- a/skype/skype-ps/skype/Set-CsMcxConfiguration.md +++ b/skype/skype-ps/skype/Set-CsMcxConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmcxconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csmcxconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsMcxConfiguration schema: 2.0.0 manager: rogupta @@ -280,4 +280,3 @@ Instead, the `Set-CsMcxConfiguration` cmdlet modifies existing instances of the ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsMediaConfiguration.md b/skype/skype-ps/skype/Set-CsMediaConfiguration.md index 8919ef31b4..17f1f8b8b8 100644 --- a/skype/skype-ps/skype/Set-CsMediaConfiguration.md +++ b/skype/skype-ps/skype/Set-CsMediaConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmediaconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csmediaconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsMediaConfiguration schema: 2.0.0 @@ -25,7 +25,8 @@ Set-CsMediaConfiguration [[-Identity] <XdsIdentity>] [-EnableQoS <Boolean>] [-En [-EncryptionLevel <EncryptionLevel>] [-MaxVideoRateAllowed <MaxVideoRateAllowed>] [-Force] [-WhatIf] [-Confirm] [-EnableAdaptiveBandWidthEstimation <Boolean>] [-EnableG722StereoCodec <Boolean>] [-EnableH264Codec <Boolean>] [-EnableInCallQoS <Boolean>] [-EnableRtpRtcpMultiplexing <Boolean>] - [-InCallQoSIntervalSeconds <UInt16>] [-EnableVideoBasedSharing <Boolean>] [-EnableDtls <Boolean>] [-EnableSilkForAudioVideoConferences <Boolean>] -[EnableServerFecForVideoInterop] [-WaitIceCompletedToAddDialOutUser] [<CommonParameters>] + [-InCallQoSIntervalSeconds <UInt16>] [-EnableVideoBasedSharing <Boolean>] [-EnableDtls <Boolean>] [-EnableSilkForAudioVideoConferences <Boolean>] -[EnableServerFecForVideoInterop] [-WaitIceCompletedToAddDialOutUser] [-EnableRtx <Boolean>] [-EnableAVBundling <Boolean>] [-EnableReceiveAgc <Boolean>] + [<CommonParameters>] ``` ### Instance @@ -34,7 +35,8 @@ Set-CsMediaConfiguration [-Instance <PSObject>] [-EnableQoS <Boolean>] [-EnableS [-EncryptionLevel <EncryptionLevel>] [-MaxVideoRateAllowed <MaxVideoRateAllowed>] [-Force] [-WhatIf] [-Confirm] [-EnableAdaptiveBandWidthEstimation <Boolean>] [-EnableG722StereoCodec <Boolean>] [-EnableH264Codec <Boolean>] [-EnableInCallQoS <Boolean>] [-EnableRtpRtcpMultiplexing <Boolean>] - [-InCallQoSIntervalSeconds <UInt16>] [-EnableVideoBasedSharing <Boolean>] [-EnableDtls <Boolean>] [-EnableSilkForAudioVideoConferences <Boolean>] -[EnableServerFecForVideoInterop] [-WaitIceCompletedToAddDialOutUser] [<CommonParameters>] + [-InCallQoSIntervalSeconds <UInt16>] [-EnableVideoBasedSharing <Boolean>] [-EnableDtls <Boolean>] [-EnableSilkForAudioVideoConferences <Boolean>] -[EnableServerFecForVideoInterop] [-WaitIceCompletedToAddDialOutUser] [-EnableRtx <Boolean>] [-EnableAVBundling <Boolean>] [-EnableReceiveAgc <Boolean>] + [<CommonParameters>] ``` ## DESCRIPTION @@ -44,7 +46,8 @@ These actions relate to audio and video calls between client endpoints. ## EXAMPLES -### -------------------------- Example 1 -------------------------- +### Example 1 + ``` Set-CsMediaConfiguration -Identity site:Redmond1 -MaxVideoRateAllowed hd720p15m ``` @@ -54,7 +57,8 @@ Note that the value passed to the MaxVideoRateAllowed parameter must be one of t Also note that the values are not case sensitive; the value entered here as hd720p15m will be automatically converted to the appropriate casing (in this instance, to Hd720p15M). -### -------------------------- Example 2 -------------------------- +### Example 2 + ``` Set-CsMediaConfiguration site:Redmond1 -EncryptionLevel donotsupportencryption ``` @@ -342,7 +346,7 @@ Accept wildcard characters: False ``` ### -EnableVideoBasedSharing -Enables the use of Video Based Sharing, for more information, see [Video based Screen Sharing for Skype for Business Server](https://docs.microsoft.com/skypeforbusiness/manage/video-based-screen-sharing) +Enables the use of Video Based Sharing, for more information, see [Video based Screen Sharing for Skype for Business Server](https://learn.microsoft.com/skypeforbusiness/manage/video-based-screen-sharing) ```yaml Type: Boolean @@ -421,6 +425,51 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EnableRtx +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableAVBundling +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableReceiveAgc +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). @@ -445,4 +494,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsMediaConfiguration](Remove-CsMediaConfiguration.md) [Get-CsMediaConfiguration](Get-CsMediaConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsMediationServer.md b/skype/skype-ps/skype/Set-CsMediationServer.md index bf0c7f7d3f..35d51973bb 100644 --- a/skype/skype-ps/skype/Set-CsMediationServer.md +++ b/skype/skype-ps/skype/Set-CsMediationServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmediationserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csmediationserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsMediationServer schema: 2.0.0 @@ -280,4 +280,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsMeetingConfiguration.md b/skype/skype-ps/skype/Set-CsMeetingConfiguration.md index 9c8e9f82fa..3e3103f124 100644 --- a/skype/skype-ps/skype/Set-CsMeetingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsMeetingConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmeetingconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csmeetingconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsMeetingConfiguration schema: 2.0.0 manager: bulenteg @@ -125,11 +125,7 @@ Accept wildcard characters: False ``` ### -AdmitAnonymousUsersByDefault -Determines whether meetings will, by default, allow attendance by anonymous users (that is, by unauthenticated users) or by federated users (authenticated users from other tenants). -Set this value to True if you would like new meetings to allow for attendance by anonymous users or federated users by default. -Set this value to False if you would prefer that, by default, new meetings do not allow for attendance by anonymous users or federated users. When set to False, anonymous and federated users will be placed in the lobby of a meeting when trying to join it. After being placed in the lobby, they can be admitted by any presenter in the meeting. -When this value is changed, the change will only apply to new meetings and it will not applied to meetings already scheduled. -The default value is True. +Determines whether meetings will, by default, allow attendance by anonymous users (that is, unauthenticated users). Set this value to True if you would like new meetings to allow for attendance by anonymous users by default. Set this value to False if you would prefer that, by default, new meetings do not allow for attendance by anonymous users. The default value is True. ```yaml Type: Boolean diff --git a/skype/skype-ps/skype/Set-CsMeetingRoom.md b/skype/skype-ps/skype/Set-CsMeetingRoom.md index b0621c7154..c7bc7a6973 100644 --- a/skype/skype-ps/skype/Set-CsMeetingRoom.md +++ b/skype/skype-ps/skype/Set-CsMeetingRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmeetingroom -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csmeetingroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsMeetingRoom schema: 2.0.0 manager: bulenteg @@ -17,6 +17,8 @@ Modifies the property values of an existing Skype for Business Server meeting ro A meeting room is a conferencing device designed to address video conferencing and collaboration scenarios in small conference rooms. This cmdlet was introduced in Lync Server 2013. +**Note**: This cmdlet is not supported for managing Microsoft Teams Rooms. You must use the methods described in the [Microsoft Teams Rooms](/microsoftteams/rooms) documentation to manage Microsoft Teams Rooms. + ## SYNTAX @@ -26,7 +28,7 @@ Set-CsMeetingRoom [-Identity] <UserIdParameter> [-AudioVideoDisabled <Boolean>] [-Confirm] [-DomainController <Fqdn>] [-Enabled <Boolean>] [-EnterpriseVoiceEnabled <Boolean>] [-ExchangeArchivingPolicy <ExchangeArchivingPolicyOptionsEnum>] [-HostedVoiceMail <Boolean>] [-LineServerURI <String>] [-LineURI <String>] [-PassThru] [-PrivateLine <String>] - [-RemoteCallControlTelephonyEnabled <Boolean>] [-SipAddress <String>] [-WhatIf] [-AsJob] [<CommonParameters>] + [-RemoteCallControlTelephonyEnabled <Boolean>] [-SipAddress <String>] [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION @@ -424,22 +426,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -465,4 +451,3 @@ Instead, the `Set-CsMeetingRoom` cmdlet modifies existing instances of the Micro [Get-CsMeetingRoom](Get-CsMeetingRoom.md) [Move-CsMeetingRoom](Move-CsMeetingRoom.md) - diff --git a/skype/skype-ps/skype/Set-CsMobilityPolicy.md b/skype/skype-ps/skype/Set-CsMobilityPolicy.md index e650ef6f1a..b159325592 100644 --- a/skype/skype-ps/skype/Set-CsMobilityPolicy.md +++ b/skype/skype-ps/skype/Set-CsMobilityPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmobilitypolicy -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csmobilitypolicy +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsMobilityPolicy schema: 2.0.0 manager: bulenteg @@ -68,7 +68,7 @@ In turn, that means that the user will not be able to use Call via Work, regardl To use Call via Work, users must be managed by a voice policy that allows simultaneous ringing. -The following parameters are not applicable to Skype for Business Online: AllowAutomaticPstnFallback, AllowCustomerExperienceImprovementProgram, AllowExchangeConnectivity, AllowSaveCallLogs, AsJob, Description, EncryptAppData, Force, Identity, Instance, PipelineVariable, RequireIntune, Tenant, VoiceSettings +The following parameters are not applicable to Skype for Business Online: AllowAutomaticPstnFallback, AllowCustomerExperienceImprovementProgram, AllowExchangeConnectivity, AllowSaveCallLogs, Description, EncryptAppData, Force, Identity, Instance, PipelineVariable, RequireIntune, Tenant, VoiceSettings ## EXAMPLES @@ -355,7 +355,7 @@ Accept wildcard characters: False ### -AllowDeviceContactsSync When set to True users will be allowed to sync device contacts on the mobile apps. -More information: [How to disable CallKit integration for Skype for Business iOS](https://docs.microsoft.com/SkypeForBusiness/troubleshoot/server-phone-system/disable-callkit-integration). +More information: [How to disable CallKit integration for Skype for Business iOS](https://learn.microsoft.com/SkypeForBusiness/troubleshoot/server-phone-system/disable-callkit-integration). ```yaml Type: Boolean @@ -410,7 +410,7 @@ Accept wildcard characters: False When set to True (the default value) users will be allowed to save credentials information (such as passwords) on their mobile device. This information can then be applied to auto-logon scenarios. -Note: If a user has AllowSaveCredentials set to False in the CsMobility policy, the Skype for Business App for iOS may sign out automatically when bringing it from the background to the foreground. This is due to the password not being saved anywhere but in the iOS process memory. Once the process is killed by the iOS system, the password will no longer be available, so the user will need to enter it again. However, there is no impact if modern authenticaion is implemented. +Note: If a user has AllowSaveCredentials set to False in the CsMobility policy, the Skype for Business App for iOS may sign out automatically when bringing it from the background to the foreground. This is due to the password not being saved anywhere but in the iOS process memory. Once the process is killed by the iOS system, the password will no longer be available, so the user will need to enter it again. However, there is no impact if modern authentication is implemented. @@ -577,4 +577,3 @@ Instead, the `Set-CsMobilityPolicy` cmdlet modifies existing instances of the Mi ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsMonitoringServer.md b/skype/skype-ps/skype/Set-CsMonitoringServer.md index 0347d71dbf..4906331044 100644 --- a/skype/skype-ps/skype/Set-CsMonitoringServer.md +++ b/skype/skype-ps/skype/Set-CsMonitoringServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csmonitoringserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csmonitoringserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsMonitoringServer schema: 2.0.0 @@ -176,4 +176,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsNetworkBandwidthPolicyProfile.md b/skype/skype-ps/skype/Set-CsNetworkBandwidthPolicyProfile.md index cf1bdc7f81..dffaff9982 100644 --- a/skype/skype-ps/skype/Set-CsNetworkBandwidthPolicyProfile.md +++ b/skype/skype-ps/skype/Set-CsNetworkBandwidthPolicyProfile.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworkbandwidthpolicyprofile +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworkbandwidthpolicyprofile applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkBandwidthPolicyProfile schema: 2.0.0 @@ -370,4 +370,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.N [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) [New-CsNetworkBWPolicy](New-CsNetworkBWPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsNetworkConfiguration.md b/skype/skype-ps/skype/Set-CsNetworkConfiguration.md index 2cd9ca3db5..c57f41a6da 100644 --- a/skype/skype-ps/skype/Set-CsNetworkConfiguration.md +++ b/skype/skype-ps/skype/Set-CsNetworkConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworkconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworkconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkConfiguration schema: 2.0.0 manager: bulenteg @@ -56,7 +56,7 @@ If at any point in the validation you choose to stop validation (by typing N at If EnableBandwidthPolicyCheck is already set to True, you can call the `Set-CsNetworkConfiguration` cmdlet and pass a value of True to the parameter EnableBandwidthPolicyCheck to run the validation without modifying any settings. In addition, when EnableBandwidthPolicyCheck is True, any changes you attempt to make by calling the `Set-CsNetworkConfiguration` cmdlet will again cause the validation check to run. -The following parameters are not applicable to Skype for Business Online: AsJob, BWPolicyProfiles, EnableBandwidthPolicyCheck, Force, Identity, Instance, InterNetworkRegionRoutes, InterNetworkSitePolicies, NetworkRegionLinks, NetworkRegions, NetworkSites, PipelineVariable, Subnets, and Tenant +The following parameters are not applicable to Skype for Business Online: BWPolicyProfiles, EnableBandwidthPolicyCheck, Force, Identity, Instance, InterNetworkRegionRoutes, InterNetworkSitePolicies, NetworkRegionLinks, NetworkRegions, NetworkSites, PipelineVariable, Subnets, and Tenant ## EXAMPLES @@ -384,4 +384,3 @@ Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.WritableC [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) [New-CsNetworkMediaBypassConfiguration](New-CsNetworkMediaBypassConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsNetworkInterRegionRoute.md b/skype/skype-ps/skype/Set-CsNetworkInterRegionRoute.md index 0f80563668..2c6e2a913f 100644 --- a/skype/skype-ps/skype/Set-CsNetworkInterRegionRoute.md +++ b/skype/skype-ps/skype/Set-CsNetworkInterRegionRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworkinterregionroute +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworkinterregionroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkInterRegionRoute schema: 2.0.0 @@ -253,4 +253,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.N [Remove-CsNetworkInterRegionRoute](Remove-CsNetworkInterRegionRoute.md) [Get-CsNetworkInterRegionRoute](Get-CsNetworkInterRegionRoute.md) - diff --git a/skype/skype-ps/skype/Set-CsNetworkInterSitePolicy.md b/skype/skype-ps/skype/Set-CsNetworkInterSitePolicy.md index 328bb4509e..549ddcf054 100644 --- a/skype/skype-ps/skype/Set-CsNetworkInterSitePolicy.md +++ b/skype/skype-ps/skype/Set-CsNetworkInterSitePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworkintersitepolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworkintersitepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkInterSitePolicy schema: 2.0.0 @@ -209,4 +209,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.N [Remove-CsNetworkInterSitePolicy](Remove-CsNetworkInterSitePolicy.md) [Get-CsNetworkInterSitePolicy](Get-CsNetworkInterSitePolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsNetworkRegion.md b/skype/skype-ps/skype/Set-CsNetworkRegion.md index c9340f4558..5262233618 100644 --- a/skype/skype-ps/skype/Set-CsNetworkRegion.md +++ b/skype/skype-ps/skype/Set-CsNetworkRegion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworkregion +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworkregion applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkRegion schema: 2.0.0 @@ -321,4 +321,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.N [Get-CsNetworkRegion](Get-CsNetworkRegion.md) [New-CsNetworkBWAlternatePath](New-CsNetworkBWAlternatePath.md) - diff --git a/skype/skype-ps/skype/Set-CsNetworkRegionLink.md b/skype/skype-ps/skype/Set-CsNetworkRegionLink.md index 609f5b030b..c56b65a75a 100644 --- a/skype/skype-ps/skype/Set-CsNetworkRegionLink.md +++ b/skype/skype-ps/skype/Set-CsNetworkRegionLink.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworkregionlink +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworkregionlink applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkRegionLink schema: 2.0.0 @@ -210,5 +210,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.N [Get-CsNetworkRegionLink](Get-CsNetworkRegionLink.md) [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) - - diff --git a/skype/skype-ps/skype/Set-CsNetworkSite.md b/skype/skype-ps/skype/Set-CsNetworkSite.md index c82980b1e4..92a478becd 100644 --- a/skype/skype-ps/skype/Set-CsNetworkSite.md +++ b/skype/skype-ps/skype/Set-CsNetworkSite.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworksite +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworksite applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkSite schema: 2.0.0 @@ -322,4 +322,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.N [Get-CsLocationPolicy](Get-CsLocationPolicy.md) [Get-CsNetworkConfiguration](Get-CsNetworkConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsNetworkSubnet.md b/skype/skype-ps/skype/Set-CsNetworkSubnet.md index 44349a524c..c12c29f142 100644 --- a/skype/skype-ps/skype/Set-CsNetworkSubnet.md +++ b/skype/skype-ps/skype/Set-CsNetworkSubnet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csnetworksubnet +online version: https://learn.microsoft.com/powershell/module/skype/set-csnetworksubnet applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsNetworkSubnet schema: 2.0.0 @@ -220,4 +220,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.N [Remove-CsNetworkSubnet](Remove-CsNetworkSubnet.md) [Get-CsNetworkSubnet](Get-CsNetworkSubnet.md) - diff --git a/skype/skype-ps/skype/Set-CsOAuthConfiguration.md b/skype/skype-ps/skype/Set-CsOAuthConfiguration.md index 66ed81a3f1..ad81bf71a0 100644 --- a/skype/skype-ps/skype/Set-CsOAuthConfiguration.md +++ b/skype/skype-ps/skype/Set-CsOAuthConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csoauthconfiguration -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csoauthconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsOAuthConfiguration schema: 2.0.0 manager: bulenteg @@ -46,7 +46,7 @@ Each Skype for Business Online tenant is also limited to a single collection of Skype for Business Server Control Panel: The functions carried out by the `Set-CsOAuthConfiguration` cmdlet are not available in the Skype for Business Server Control Panel. -The following parameters are not applicable to Skype for Business Online: AdditionalAudienceUrls, AlternateAudienceUrl, AsJob, ClientAuthorizationOAuthServerIdentity, ExchangeAutodiscoverAllowedDomains, ExchangeAutodiscoverUrl, Force, Identity, Instance, PipelineVariable, Realm, ServiceName, and Tenant +The following parameters are not applicable to Skype for Business Online: AdditionalAudienceUrls, AlternateAudienceUrl, ClientAuthorizationOAuthServerIdentity, ExchangeAutodiscoverAllowedDomains, ExchangeAutodiscoverUrl, Force, Identity, Instance, PipelineVariable, Realm, ServiceName, and Tenant ## EXAMPLES @@ -285,7 +285,7 @@ Allowed, Enables OAuth for the tenant Disallowed, Disables OAuth for the tenant -For more information, see [Hybrid Modern Authentication overview and prerequisites for using it with on-premises Skype for Business and Exchange servers](https://docs.microsoft.com/office365/enterprise/hybrid-modern-auth-overview) +For more information, see [Hybrid Modern Authentication overview and prerequisites for using it with on-premises Skype for Business and Exchange servers](https://learn.microsoft.com/office365/enterprise/hybrid-modern-auth-overview) ```yaml Type: ClientAdalAuthOverride @@ -337,4 +337,3 @@ Instead, the `Set-CsOAuthConfiguration` cmdlet modifies existing instances of th ## RELATED LINKS [Get-CsOAuthConfiguration](Get-CsOAuthConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsOAuthServer.md b/skype/skype-ps/skype/Set-CsOAuthServer.md index dd940dd66f..0749b9d100 100644 --- a/skype/skype-ps/skype/Set-CsOAuthServer.md +++ b/skype/skype-ps/skype/Set-CsOAuthServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csoauthserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csoauthserver applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsOAuthServer schema: 2.0.0 @@ -247,4 +247,3 @@ Instead, the `Set-CsOAuthServer` cmdlet modifies existing instances of the Micro [New-CsOAuthServer](New-CsOAuthServer.md) [Remove-CsOAuthServer](Remove-CsOAuthServer.md) - diff --git a/skype/skype-ps/skype/Set-CsOnlineApplicationEndpoint.md b/skype/skype-ps/skype/Set-CsOnlineApplicationEndpoint.md deleted file mode 100644 index 91a80845eb..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineApplicationEndpoint.md +++ /dev/null @@ -1,273 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlineapplicationendpoint -applicable: Skype for Business Online -title: Set-CsOnlineApplicationEndpoint -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineApplicationEndpoint - -## SYNOPSIS -The `Set-CsOnlineApplicationEndpoint` is used to update a Trusted Application Endpoint for a tenant. - -## SYNTAX -``` -Set-CsOnlineApplicationEndpoint [-CallbackUri <String>] [-Name <String>] [-Uri] <String> [-Audience <String>] - [-Ring <String>] [-PhoneNumber <String>] [-IsInternalRun <Boolean>] [-Tenant <Guid>] - [-RunFullProvisioningFlow <Boolean>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to update a Trusted Application Endpoint for a tenant. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineApplicationEndpoint -Uri "sip:sample@domain.com" -PhoneNumber "19841110909" -``` - -This example assigns the service number "19841110909" to the trusted application with the sip uri "sample@domain.com". - -## PARAMETERS - -### -Uri -Sip Uri that identifies the tenant specific endpoint for the application. This must be a unique URI that does not conflict with an existing user in the tenant. Requests sent to this endpoint will trigger the Trusted Application API sending an event to the application, indicating that someone has sent a request. For example: helpdesk@contoso.com. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: SipUri -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Audience -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallbackUri -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -A friendly name of your application within Skype for Business Online. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneNumber -The service number assigned to the trusted application endpoint. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsInternalRun -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Ring -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RunFullProvisioningFlow -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - -[Get-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/get-csonlineapplicationendpoint) - -[New-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/new-csonlineapplicationendpoint) - -[Remove-CsOnlineApplicationEndpoint](https://docs.microsoft.com/powershell/module/skype/remove-csonlineapplicationendpoint) - -[Set up a Trusted Application Endpoint](https://docs.microsoft.com/skype-sdk/trusted-application-api/docs/trustedapplicationendpoint) diff --git a/skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md b/skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md deleted file mode 100644 index dcedaa44ff..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlineapplicationinstance -applicable: Skype for Business Online -title: Set-CsOnlineApplicationInstance -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineApplicationInstance - -## SYNOPSIS -Updates an application instance in Azure Active Directory. - -## SYNTAX - -``` -Set-CsOnlineApplicationInstance [-Identity] <string> [[-OnpremPhoneNumber] <string>] [[-ApplicationId] <guid>] - [[-DisplayName] <string>] [-Tenant <guid>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet is used to update an application instance in Azure Active Directory. This same cmdlet is also run when creating a new resource account using Teams Admin Center. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Set-CsOnlineApplicationInstance -Identity appinstance01@contoso.com -OnpremPhoneNumber +14250000000 -ApplicationId ce933385-9390-45d1-9512-c8d228074e07 -DisplayName "AppInstance01" -``` - -This example shows updating OnpremPhoneNumber, ApplicationId, DisplayName information for an existing Auto Attendant application instance with Identity "appinstance01@contoso.com". - -The following are the application ID's for each type of application instance types: - -Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07 -Call Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07 - -## PARAMETERS - -### -Identity -The URI or ID of the application instance to update. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnpremPhoneNumber -Assigns a hybrid (on-premise) telephone number to the application instance. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationId -The application ID. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DisplayName -The display name. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingTenantSettings.md b/skype/skype-ps/skype/Set-CsOnlineDialInConferencingTenantSettings.md deleted file mode 100644 index 0ebd78fbd1..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingTenantSettings.md +++ /dev/null @@ -1,465 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencingtenantsettings -applicable: Skype for Business Online -title: Set-CsOnlineDialInConferencingTenantSettings -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineDialInConferencingTenantSettings - -## SYNOPSIS -Use the `Set-CsOnlineDialInConferencingTenantSettings` to modify the tenant level settings of dial-in conferencing. -Dial-in conferencing tenant settings control the conference experience of users and manage some conferencing administrative functions. - -## SYNTAX - -### Identity (Default) -``` -Set-CsOnlineDialInConferencingTenantSettings [-Tenant <Guid>] [-EnableEntryExitNotifications <Boolean>] - [-EntryExitAnnouncementsType <EntryExitAnnouncementsType>] [-EnableNameRecording <Boolean>] - [-IncludeTollFreeNumberInMeetingInvites <Boolean>] [-PinLength <UInt32>] - [-AllowPSTNOnlyMeetingsByDefault <Boolean>] [-AutomaticallySendEmailsToUsers <Boolean>] - [-SendEmailFromOverride <Boolean>] [-SendEmailFromAddress <String>] [-SendEmailFromDisplayName <String>] - [-AutomaticallyReplaceAcpProvider <Boolean>] [-UseUniqueConferenceIds <Boolean>] - [-AutomaticallyMigrateUserMeetings <Boolean>] [-MigrateServiceNumbersOnCrossForestMove <Boolean>] - [-EnableDialOutJoinConfirmation <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### Instance -``` -Set-CsOnlineDialInConferencingTenantSettings [-Tenant <Guid>] [-EnableEntryExitNotifications <Boolean>] - [-EntryExitAnnouncementsType <EntryExitAnnouncementsType>] [-EnableNameRecording <Boolean>] - [-IncludeTollFreeNumberInMeetingInvites <Boolean>] [-PinLength <UInt32>] - [-AllowPSTNOnlyMeetingsByDefault <Boolean>] [-AutomaticallySendEmailsToUsers <Boolean>] - [-SendEmailFromOverride <Boolean>] [-SendEmailFromAddress <String>] [-SendEmailFromDisplayName <String>] - [-AutomaticallyReplaceAcpProvider <Boolean>] [-UseUniqueConferenceIds <Boolean>] - [-AutomaticallyMigrateUserMeetings <Boolean>] [-MigrateServiceNumbersOnCrossForestMove <Boolean>] - [-EnableDialOutJoinConfirmation <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Dial-in conferencing tenant settings control what functions are available during a conference call. -For example, whether or not entries and exits from the call are announced. -The settings also manage some of the administrative functions, such as when users get notification of administrative actions, like a PIN change. -By contrast, the higher level dial-in conferencing configuration only maintains a flag for whether dial-in conferencing is enabled for your organization. -For more information, see `Get-CsOnlineDialinConferencingTenantConfiguration`. - -There is always a single instance of the dial-in conferencing settings per tenant. -You can modify the settings using `Set-CsOnlineDialInConferencingTenantSettings` and revert those settings to their defaults by using `Remove-CsOnlineDialInConferencingTenantSettings`. - -The following parameters are not applicable to Skype for Business Online: AsJob, EnableDialOutJoinConfirmation, IncludeTollFreeNumberInMeetingInvites, MigrateServiceNumbersOnCrossForestMove, and UseUniqueConferenceIds - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineDialInConferencingTenantSettings -EnableEntryExitNotifications $True -EnableNameRecording $True -PinLength 7 -``` - -This example sets the tenant's conferencing settings to enable entry and exit notifications supported by name recording. -The PIN length is set to 7. - - -### -------------------------- Example 2 -------------------------- -``` -Set-CsOnlineDialInConferencingTenantSettings -SendEmailFromOverride $true -SendEmailFromAddress admin@contoso.com -SendEmailFromDisplayName "Conferencing Administrator" -``` - -This example defines the contact information to be used in dial-in conferencing email notifications and enables the default address to be overridden. - - -## PARAMETERS - -### -AllowPSTNOnlyMeetingsByDefault -Specifies the default value that gets assigned to the "AllowPSTNOnlyMeetings" setting of users when they are enabled for dial-in conferencing, or when a user's dial-in conferencing provider is set to Microsoft. -If set to $true, the "AllowPSTNOnlyMeetings" setting of the user will also be set to true. -If $false, the user setting will be false. -The default value for AllowPSTNOnlyMeetingsByDefault is $false. - -When AllowPSTNOnlyMeetingsByDefault is changed, the value of the "AllowPSTNOnlyMeetings" setting of currently enabled users doesn't change. -The new default value will only be applied to users that are subsequently enabled for dial-in conferencing, or whose provider is changed to Microsoft. - -The "AllowPSTNOnlyMeetings" setting of a user defines if unauthenticated callers can start a meeting if they are the first person to join. -An unauthenticated caller is defined as a participant who joins a meeting over the phone and doesn't provide the organizer PIN when joining the meeting. - -For more information on the "AllowPSTNOnlyMeetings" user setting, see `Set-CsOnlineDialInConferencingUser`. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutomaticallyMigrateUserMeetings -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutomaticallyReplaceAcpProvider -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AutomaticallySendEmailsToUsers -Specifies whether advisory emails will be sent to users when the events listed below occur. -Setting the parameter to $true enables the emails to be sent, $false disables the emails. -The default is $true. - -User is enabled or disabled for dial-in conferencing. - -The dial-in conferencing provider is changed either to Microsoft, or from Microsoft to another provider, or none. - -The dial-in conferencing PIN is reset by the tenant administrator. - -Changes to either the user's conference ID, or the user's default dial-in conference number. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableEntryExitNotifications -Specifies if, by default, announcements are made as users enter and exit a conference call. -Set to $true to enable notifications, $false to disable notifications. -The default is $true. - -This setting can be overridden on a meeting by meeting basis when a user joins a meeting via a Skype for Business client and modifies the Announce when people enter or leave setting on the Skype Meeting Options menu of a meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableNameRecording -Specifies whether the name of a user is recorded on entry to the conference. -This recording is used during entry and exit notifications. -Set to $true to enable name recording, set to $false to bypass name recording. -The default is $true. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EntryExitAnnouncementsType -PARAMVALUE: UseNames | ToneOnly - -```yaml -Type: EntryExitAnnouncementsType -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IncludeTollFreeNumberInMeetingInvites -This parameter is obsolete and not functional. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MigrateServiceNumbersOnCrossForestMove -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PinLength -Specifies the number of digits in the automatically generated PINs. -Organizers can enter their PIN to start a meeting they scheduled if they join via phone and are the first person to join. -The minimum value is 4, the maximum is 12, and the default is 5. - -A user's PIN will only authenticate them as leaders for a meeting they scheduled. -The PIN of a user that did not schedule the meeting will not enable that user to lead the meeting. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromAddress -Specifies the email address to use in the "From" contact information on emails that are sent to users to notify them of their dial-in conferencing settings, or when their settings change. -The email address needs to be in the form \<UserAlias\>@\<Domain\>. -For example, "KenMyer@Contoso.com" or "Admin@Contoso.com". - -The SendEmailFromAddress value is used only if the SendEmailFromDisplayName setting is specified, and the SendEmailFromOverride setting is $true. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromDisplayName -Specifies the display name to use in the "From" contact information on emails that are sent to users to notify them of their dial-in conferencing settings, or when their settings change. - -The SendEmailFromDisplayName value is used only if the SendEmailFromDisplayName setting is specified, and the SendEmailFromOverride setting is $true. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromOverride -Specifies if the contact information on dial-in conferencing notifications will be the default generated by Office 365, or administrator defined values. -Setting SendEmailFromOverride to $true enables the system to use the SendEmailFromAddress and SendEmailFromDisplayName parameter inputs as the "From" contact information. -Setting this parameter to $false will cause email notifications to be sent with the system generated default. -The default is $false. - -SendEmailFromOverride can't be $true if SendEmailFromAddress and SendEmailFromDisplayName aren't specified. - -If you want to change the email address information, you need to make sure that your inbound email policies allow for emails that come from the address specified by the SendEmailFromAddress parameter. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -UseUniqueConferenceIds -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -None - -## OUTPUTS - -### -None. - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingUser.md b/skype/skype-ps/skype/Set-CsOnlineDialInConferencingUser.md deleted file mode 100644 index 60d0f8c1d3..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingUser.md +++ /dev/null @@ -1,434 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencinguser -applicable: Skype for Business Online -title: Set-CsOnlineDialInConferencingUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineDialInConferencingUser - -## SYNOPSIS -Use the `Set-CsOnlineDialInConferencingUser` cmdlet to modify the properties of a user that has been enabled for Microsoft's audio conferencing service. - -## SYNTAX - -### TenantIdParams (Default) -``` -Set-CsOnlineDialInConferencingUser [-Identity] <UserIdParameter> [-BridgeId <Guid>] - [-BridgeName <String>] [-Tenant <Guid>] [-ConferenceId <System.Int32>] [-ResetConferenceId] - [-ServiceNumber <String>] [-TollFreeServiceNumber <String>] [-AllowPSTNOnlyMeetings <Boolean>] [-Force] - [-ResetLeaderPin] [-AllowTollFreeDialIn <Boolean>] [-SendEmailToAddress <String>] - [-SendEmailFromAddress <String>] [-SendEmailFromDisplayName <String>] [-SendEmail] [-DomainController <Fqdn>] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### TenantDomainParams -``` -Set-CsOnlineDialInConferencingUser [-Identity] <UserIdParameter> [-BridgeId <Guid>] - [-BridgeName <String>] -TenantDomain <String> [-ConferenceId <Int32>] [-ResetConferenceId] - [-ServiceNumber <String>] [-TollFreeServiceNumber <String>] [-AllowPSTNOnlyMeetings <Boolean>] [-Force] - [-ResetLeaderPin] [-AllowTollFreeDialIn <Boolean>] [-SendEmailToAddress <String>] - [-SendEmailFromAddress <String>] [-SendEmailFromDisplayName <String>] [-SendEmail] [-DomainController <Fqdn>] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-CsOnlineDialInConferencingUser` cmdlet is used to modify properties for a Microsoft audio conferencing user. -This cmdlet will not work for users with third-party conferencing providers. -The cmdlet will verify that the correct license is assigned to the user. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineDialInConferencingUser -Identity "Ken Meyers" -ConferenceId 3542699 -ResetLeaderPin -ServiceNumber 14255037265 -``` - -This example shows how to set a ConferenceId for a user, reset the meeting leader's PIN and set the audio conferencing provider default meeting phone number. - - -### -------------------------- Example 2 -------------------------- -``` -Set-CsOnlineDialInConferencingUser -Identity "Ken Meyers" -BridgeName "Conference Bridge" -ConferenceId 3542699 -``` - -This example sets a user's ConferenceId and conference bridge assignment. - - -## PARAMETERS - -### -Identity -Specifies the Identity of the user account to be to be modified. -A user identity can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). -You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantDomain -Specifies the domain name for the tenant or organization. - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPSTNOnlyMeetings -If true, non-authenticated users can start meetings. -If false, non-authenticated callers wait in the lobby until an authenticated user joins, thereby starting the meeting. -An authenticated user is a user who joins the meeting using a Skype for Business client, or the organizer that joined the meeting via dial-in conferencing and was authenticated by a PIN number. -The default is false. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BridgeId -Specifies the globally-unique identifier (GUID) for the audio conferencing bridge. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BridgeName -Specifies the name of the audio conferencing bridge. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConferenceId -Specifies the ConferenceId that will be used by the user for dial-in meetings. -The cmdlet will fail if: - -The ConferenceId is already being used in the bridge where the user is assigned, or to which the user would be assigned. - -The ConferenceId doesn't meet the ConferenceId format requirements. - -ConferenceId and ResetConferenceId are mutually exclusive. -When ConferenceId is specified the new ConferenceId will be assigned to the user. -When ResetConferenceId is specified, the user will get an auto-generated ConferenceId. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: Passcode -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Specifies the domain controller that's used by the cmdlet to read or write the specified data. -Valid inputs for this parameter include: - -Fully qualified domain name (FQDN): `-DomainController atl-cs-001.Contoso.com` - -Computer name: `-DomainController atl-cs-001` - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResetConferenceId -Specifies whether to reset the ConferenceId for meetings that the user is organizing. -If specified, the meetings using the old ConferenceId will fail. -The user will have to reschedule his existing meetings, or run the meeting migration tool. - -ConferenceId and ResetConferenceId are mutually exclusive. -When ConferenceId is specified the new ConferenceId will be assigned to the user. -When ResetConferenceId is specified, the user will get an auto-generated ConferenceId. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: ResetPasscode -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ResetLeaderPin -Specifies whether to reset the meeting organizer or leaders PIN for meetings. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmail -Send an email to the user containing their Audio Conference information. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromAddress -You can specify the From Address to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmailFromDisplayName and -SendEmail. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailFromDisplayName -You can specify the Display Name to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmailFromAddress and -SendEmail. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendEmailToAddress -You can specify the To Address to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmail. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ServiceNumber -Specifies the default service number for the user. -The default number is used in meeting invitations. -The cmdlet will verify that the service number is assigned to the user's current conference bridge, or the one the user is being assigned to. - -The service number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"`. -You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` - -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TollFreeServiceNumber -Specifies a toll-free phone number to be used by the user. This number is then used in meeting invitations. The toll-free number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf parameter is not implemented for this cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowTollFreeDialIn -If toll-free numbers are available in your Microsoft Audio Conferencing bridge, this parameter controls if they can be used to join the meetings of a given user. Please note that making modifications to this value could trigger rescheduling all existing meetings organized by the given users, and all meeting invites will be resent to all participants. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineDirectoryUser.md b/skype/skype-ps/skype/Set-CsOnlineDirectoryUser.md deleted file mode 100644 index 932ed2ccd3..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineDirectoryUser.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinedirectoryuser -applicable: Skype for Business Online -title: Set-CsOnlineDirectoryUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineDirectoryUser - -## SYNOPSIS -Use the `Set-CsOnlineDirectoryUser` cmdlet to create or modify a PSTN enabled user in Business Voice Directory. -This should be done via provisioning or operations in special cases. - -## SYNTAX - -``` -Set-CsOnlineDirectoryUser [-Identity] <UserIdParameter> [-Tenant <Guid>] [-Ring <String>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -Identity -Specifies the identity of the target user. -Acceptable values include: - -Example: jphillips@contoso.com - -Example: sip:jphillips@contoso.com - -Example: 98403f08-577c-46dd-851a-f0460a13b03d - -You can use the `Get-CsOnlineUser` cmdlet to identify the users you want to modify. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -Specifies the domain controller that's used by the cmdlet to read or write the specified data. -Valid inputs for this parameter are either the fully qualified domain name (FQDN) or the computer name. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Ring -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"`. -You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md b/skype/skype-ps/skype/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md deleted file mode 100644 index 97715e8e33..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlineenhancedemergencyservicedisclaimer -applicable: Skype for Business Online -title: Set-CsOnlineEnhancedEmergencyServiceDisclaimer -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineEnhancedEmergencyServiceDisclaimer - -## SYNOPSIS -Use the `Set-CsOnlineEnhancedEmergencyServiceDisclaimer` cmdlet to record your organization's acceptance of the enhanced emergency service terms and conditions. -Any tenant administrator can accept the terms and conditions. - -## SYNTAX - -``` -Set-CsOnlineEnhancedEmergencyServiceDisclaimer -CountryOrRegion <String> [-Version <String>] [-ForceAccept] - [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - - -## DESCRIPTION -You must run this cmdlet prior to assigning phone numbers and locations to voice enabled users in the United States. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineEnhancedEmergencyServiceDisclaimer -CountryOrRegion US -``` - -This example accepts the U.S. -version of the enhanced emergency service terms and conditions. - - -## PARAMETERS - -### -CountryOrRegion -Specifies the region or country whose terms and conditions you wish to accept. -The United States is currently the only country supported, but it must be specified as "US". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForceAccept -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Version -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -None - -## OUTPUTS - -### -None - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineLisCivicAddress.md b/skype/skype-ps/skype/Set-CsOnlineLisCivicAddress.md deleted file mode 100644 index 9adef15d31..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineLisCivicAddress.md +++ /dev/null @@ -1,473 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlineliscivicaddress -applicable: Skype for Business Online -title: Set-CsOnlineLisCivicAddress -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# Set-CsOnlineLisCivicAddress - -## SYNOPSIS -Use the \`Set-CsOnlineLisCivicAddress\` cmdlet to modify an existing civic address which has not been validated. -Validated civic addresses cannot be modified. - -## SYNTAX - -``` -Set-CsOnlineLisCivicAddress -CivicAddressId <Guid> [-CompanyName <String>] [-CompanyTaxId <String>] - [-HouseNumber <String>] [-HouseNumberSuffix <String>] [-StreetName <String>] [-StreetSuffix <String>] - [-PreDirectional <String>] [-PostDirectional <String>] [-City <String>] [-CityAlias <String>] - [-StateOrProvince <String>] [-CountryOrRegion <String>] [-PostalCode <String>] [-Description <String>] - [-ValidationStatus <String>] [-Latitude <String>] [-Longitude <String>] [-Confidence <String>] - [-Elin <String>] [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -{{Fill in the Description}} - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineLisCivicAddress -CivicAddressid a363a9b8-1acd-41de-916a-296c7998a024 -Description "City Center" -CompanyName Contoso -``` - -This example modifies the description and company name of the civic address with the identity a363a9b8-1acd-41de-916a-296c7998a024. - - -### -------------------------- Example 2 -------------------------- -``` -Set-CsOnlineLisCivicAddress -CivicAddressid a363a9b8-1acd-41de-916a-296c7998a024 -Longitude 12 -Latitude 34 -ELIN MICROSOFT_ELIN -``` - -This example modifies the latitude, longitude and ELIN name of the civic address with the identity a363a9b8-1acd-41de-916a-296c7998a024. - - -## PARAMETERS - -### -CivicAddressId -Specifies the unique identifier of the civic address to be modified. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -Specifies a new city for the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CityAlias -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyName -Specifies a new company name for the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyTaxId -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies a new country or region for the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies a new description for the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumber -Specifies the new numeric portion of the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumberSuffix -Specifies the new numeric suffix of the new civic address. -For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostalCode -Specifies the new postal code of the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostDirectional -Specifies the new directional attribute of the civic address which follows the street name. -For example, "425 Smith Avenue NE". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreDirectional -Specifies the new directional attribute of the civic address which precedes the street name. -For example, "425 NE Smith Avenue ". - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOrProvince -Specifies the new state or province of the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetName -Specifies the new street name of the civic address. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetSuffix -Specifies the new modifier of the street name of the new civic address. -The street suffix will typically be something like street, avenue, way, or boulevard. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ValidationStatus -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confidence -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Elin -Specifies the Emergency Location Identification Number. -This is used in Direct Routing EGW scenarios. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Latitude -Specifies the angular distance of a place north or south of the earth's equator. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Longitude -Specifies the angular distance of a place east or west of the meridian at Greenwich, England. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### None - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineLisLocation.md b/skype/skype-ps/skype/Set-CsOnlineLisLocation.md deleted file mode 100644 index 55b4413bed..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineLisLocation.md +++ /dev/null @@ -1,500 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinelislocation -applicable: Skype for Business Online -title: Set-CsOnlineLisLocation -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# Set-CsOnlineLisLocation - -## SYNOPSIS -Use the \`Set-CsOnlineLisLocation\` cmdlet to modify an existing emergency dispatch location. -There can be multiple locations in a civic address. -Typically the civic address designates the building, and locations are specific parts of that building such as a floor, office, or wing. - -## SYNTAX - -### UseCivicAddressId -``` -Set-CsOnlineLisLocation -CivicAddressId <Guid> [-CompanyName <String>] [-CompanyTaxId <String>] - [-HouseNumber <String>] [-HouseNumberSuffix <String>] [-StreetName <String>] [-StreetSuffix <String>] - [-PreDirectional <String>] [-PostDirectional <String>] [-City <String>] [-CityAlias <String>] - [-StateOrProvince <String>] [-CountryOrRegion <String>] [-PostalCode <String>] [-Description <String>] - [-Latitude <String>] [-Longitude <String>] [-Confidence <String>] [-Elin <String>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### UseLocationId -``` -Set-CsOnlineLisLocation -LocationId <Guid> [-Location <String>] [-CityAlias <String>] [-Latitude <String>] - [-Longitude <String>] [-Confidence <String>] [-Elin <String>] [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineLisLocation -LocationId 5aa884e8-d548-4b8e-a289-52bfd5265a6e -Location "B5 2nd Floor" -``` - -This example changes the location description of the location specified by its location identity. - - -### -------------------------- Example 2 -------------------------- -``` -Set-CsOnlineLisLocation -CivicAddressId 5687eb59-9039-4e99-bb89-71771d723b7a -Location "B5 2nd Floor" -Elin "TEST_ELIN" -``` - -This example changes the Elin of the location specified by its location identity. - - -## PARAMETERS - -### -CivicAddressId -Specifies the unique identifier of the civic address that contains the location to be modified. -Civic address identities can be discovered by using the \`Get-CsOnlineLisCivicAddress\` cmdlet. - -```yaml -Type: Guid -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -Specifies the unique identifier of the location to be modified. -If specified, no other address parameters are allowed. -Location identities can be discovered by using the \`Get-CsOnlineLisLocation\` cmdlet. - -```yaml -Type: Guid -Parameter Sets: UseLocationId -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -Specifies the city of the civic address. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CityAlias -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyName -Specifies the name of your organization. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyTaxId -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the country or region of the civic address. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies an administrator defined description of the civic address. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumber -Specifies the numeric portion of the civic address. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumberSuffix -Specifies the numeric suffix of the civic address. -For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Location -Specifies an administrator defined description of the new location. -For example, "2nd Floor Cafe", "Main Lobby", or "Office 250". - -```yaml -Type: String -Parameter Sets: UseLocationId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostalCode -Specifies the postal code of the civic address. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostDirectional -Specifies the directional attribute of the civic address which follows the street name. -For example, "425 Smith Avenue NE". - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreDirectional -Specifies the directional attribute of the civic address which precedes the street name. -For example, "425 NE Smith Avenue ". - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOrProvince -Specifies the state or province of the civic address. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetName -Specifies the street name of the civic address. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetSuffix -Specifies a modifier of the street name of the civic address. -The street suffix will typically be something like street, avenue, way, or boulevard. - -```yaml -Type: String -Parameter Sets: UseCivicAddressId -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confidence -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Elin -Specifies the Emergency Location Identification Number. -This is used in Direct Routing EGW scenarios. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Latitude -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Longitude -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineLisPort.md b/skype/skype-ps/skype/Set-CsOnlineLisPort.md deleted file mode 100644 index 3439bb08ea..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineLisPort.md +++ /dev/null @@ -1,243 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinelisport -applicable: Skype for Business Online -title: Set-CsOnlineLisPort -schema: 2.0.0 -author: junya -ms.author: junya -ms.reviewer: ---- - -# Set-CsOnlineLisPort - -## SYNOPSIS -Creates a Location Information Server (LIS) port, creates an association between a port and a location (creating a new location if that location doesn't exist), or modifies an existing port and its associated location. The association between a port and location is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. - - -## SYNTAX - -``` -Set-CsOnlineLisPort [[-TenantId] <Guid>] [-ChassisID] <String> -PortID <String> -LocationId <Guid> - [-Description <String>] [-IsDebug <Boolean>] [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet allows the administrator to map physical locations to the port through which the client is connected. - -If a location with an address exactly matching the address parameters entered here (including null values) does not exist in the location database, a new address will be created based on the parameters entered with this cmdlet. (You can retrieve a list of locations by calling the \`Get-CsOnlineLisLocation\` cmdlet.) The \`Set-CsOnlineLisPort\` cmdlet does require or prompt for location parameters. A valid location consists of, at minimum, the Location, HouseNumber, StreetName, City, State and Country. If you do not supply all of these parameters, calls that are received by the referenced port may not contain the information required by the emergency operator (depending on whether valid settings are available for a switch, subnet, or wireless access point that can be used in place of port settings). It is recommended that you be as specific as possible with the location parameters and fill in as many as possible. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineLisPort -PortID 12174 -ChassisID 0B-23-CD-16-AA-CC -Description "LisPort 12174" -LocationId efd7273e-3092-4a56-8541-f5c896bb6fee -``` - -Example 1 creayes the association between port "12174" and LocationId "efd7273e-3092-4a56-8541-f5c896bb6fee". - -## PARAMETERS - -### -ChassisID -The Media Access Control (MAC) address of the port's switch. This value will be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the administrator defined description of the port. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDebug -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -Specifies the unique identifier of the location to be modified. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NCSApiUrl -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PortID -This parameter identifies the ID of the port. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - - -### System.Guid - - -### System.String - - -## OUTPUTS - - -### System.Object - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineLisSwitch.md b/skype/skype-ps/skype/Set-CsOnlineLisSwitch.md deleted file mode 100644 index 947db462f9..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineLisSwitch.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinelisswitch -applicable: Skype for Business Online -title: Set-CsOnlineLisSwitch -schema: 2.0.0 -author: junya -ms.author: junya -ms.reviewer: ---- - -# Set-CsOnlineLisSwitch - -## SYNOPSIS -Creates a Location Information Server (LIS) switch, creates an association between a switch and a location (creating a new location if that location doesn't exist), or modifies an existing switch and its associated location. The association between a switch and location is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. - -## SYNTAX - -``` -Set-CsOnlineLisSwitch [[-TenantId] <Guid>] [-ChassisID] <String> -LocationId <Guid> [-Description <String>] - [-IsDebug <Boolean>] [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet allows the administrator to map physical locations to the network switch through which the client is connected. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineLisSwitch -ChassisID 0B-23-CD-16-AA-CC -Description "LIS switch with chassis ID 0B-23-CD-16-AA-CC" -LocationId d26a4935-5997-4bcf-b0db-6ae5a88805fd -``` - -Example 1 creates the Location Information Server (LIS) switch with Chassis ID "0B-23-CD-16-AA-CC", associated with location ID d26a4935-5997-4bcf-b0db-6ae5a88805fd. - - -## PARAMETERS - -### -ChassisID -The Media Access Control (MAC) address of the port's switch. This value will be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the administrator defined description of the switch. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDebug -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -The name for this location. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NCSApiUrl -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - - -### System.Guid - - -### System.String - - -## OUTPUTS - - -### System.Object - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineLisWirelessAccessPoint.md b/skype/skype-ps/skype/Set-CsOnlineLisWirelessAccessPoint.md deleted file mode 100644 index 0246563da9..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineLisWirelessAccessPoint.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlineliswirelessaccesspoint -applicable: Skype for Business Online -title: Set-CsOnlineLisWirelessAccessPoint -schema: 2.0.0 -author: junya -ms.author: junya -ms.reviewer: ---- - -# Set-CsOnlineLisWirelessAccessPoint - -## SYNOPSIS -Creates a Location Information Server (LIS) wireless access point (WAP), creates an association between a WAP and a location (creating a new location if that location doesn't exist), or modifies an existing WAP and its associated location. The association between a WAP and location is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. - -## SYNTAX - -``` -Set-CsOnlineLisWirelessAccessPoint [[-TenantId] <Guid>] [-BSSID] <String> -LocationId <Guid> - [-Description <String>] [-IsDebug <Boolean>] [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet allows the administrator to map physical locations to the WAP through which calls will be routed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineLisWirelessAccessPoint -BSSID 0B-23-CD-16-AA-CC -Description "LIS WAP with BSS ID 0B-23-CD-16-AA-CC" -LocationId d26a4935-5997-4bcf-b0db-6ae5a88805fd -``` - -Example 1 creates the Location Information Server (LIS) wireless access point with Chassis ID "0B-23-CD-16-AA-CC", associated with location ID d26a4935-5997-4bcf-b0db-6ae5a88805fd. - - -## PARAMETERS - -### -BSSID -The Basic Service Set Identifier (BSSID) of the wireless access point. This value must be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. If an entry with the specified BSSID value does not exist, a new WAP location will be created. If an entry with the specified BSSID does exist, that entry will be replaced. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies the administrator defined description of the WAP. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsDebug -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocationId -The name for this location. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NCSApiUrl -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - - -### System.Guid - - -### System.String - - -## OUTPUTS - - -### System.Object - - -## NOTES - - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineNumberPortInOrder.md b/skype/skype-ps/skype/Set-CsOnlineNumberPortInOrder.md deleted file mode 100644 index 0f7e188c72..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineNumberPortInOrder.md +++ /dev/null @@ -1,507 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinenumberportinorder -applicable: Skype for Business Online -title: Set-CsOnlineNumberPortInOrder -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineNumberPortInOrder - -## SYNOPSIS -This cmdlet is reserved for Microsoft internal use only. -New third party provider ports should be provisioned through the Skype for Business Online admin center. - -## SYNTAX - -``` -Set-CsOnlineNumberPortInOrder [-Tenant <Guid>] -PortInOrderId <String> [-LOABase64PayLoad <String>] - [-LOAContentType <String>] [-LOAAuthorizingPerson <String>] [-SubscriberArea <String>] - [-SubscriberCity <String>] [-SubscriberCountry <String>] [-SubscriberStreetName <String>] - [-SubscriberBuildingNumber <String>] [-SubscriberZipCode <String>] [-SubscriberBusinessName <String>] - [-BillingTelephoneNumber <String>] [-SubscriberFirstName <String>] [-SubscriberLastName <String>] - [-EmailAddresses <String[]>] [-RequestedFocDate <DateTime>] [-LosingTelcoPin <String>] - [-LosingTelcoAccountId <String>] [-SubscriberAddressLine1 <String>] [-SubscriberAddressLine2 <String>] - [-IsPartialPort <Boolean>] [-SubscriberAddressLine3 <String>] [-FriendlyName <String>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -{{Fill in the Description}} - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> {{ Add example code here }} -``` - -{{ Add example description here }} - - -## PARAMETERS - -### -PortInOrderId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BillingTelephoneNumber -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmailAddresses -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FriendlyName -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsPartialPort -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LOAAuthorizingPerson -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LOABase64PayLoad -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LOAContentType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LosingTelcoAccountId -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LosingTelcoPin -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequestedFocDate -This parameter is reserved for internal Microsoft use. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAddressLine1 -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAddressLine2 -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberAddressLine3 -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberArea -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberBuildingNumber -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberBusinessName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberCity -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberCountry -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberFirstName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberLastName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberStreetName -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SubscriberZipCode -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineNumberPortOutOrderPin.md b/skype/skype-ps/skype/Set-CsOnlineNumberPortOutOrderPin.md deleted file mode 100644 index 4150e7b0f8..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineNumberPortOutOrderPin.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinenumberportoutorderpin -applicable: Skype for Business Online -title: Set-CsOnlineNumberPortOutOrderPin -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineNumberPortOutOrderPin - -## SYNOPSIS -{{Fill in the Synopsis}} - - -## SYNTAX - -``` -Set-CsOnlineNumberPortOutOrderPin [-Tenant <Guid>] [-PortOrderPin <String>] [-DomainController <Fqdn>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -{{Fill in the Description}} - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -{{Fill DomainController Description}} - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{Fill Force Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PortOrderPin -{{Fill PortOrderPin Description}} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -{{Fill Tenant Description}} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlinePSTNGateway.md b/skype/skype-ps/skype/Set-CsOnlinePSTNGateway.md deleted file mode 100644 index 3855d7b45d..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlinePSTNGateway.md +++ /dev/null @@ -1,441 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinepstngateway -applicable: Skype for Business Online -title: Set-CsOnlinePSTNGateway -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlinePSTNGateway - -## SYNOPSIS -Modifies the previously defined Session Border Controller (SBC) Configuration that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. - -## SYNTAX - -``` -Set-CsOnlinePSTNGateway [-Tenant <System.Guid>] [-SipSignalingPort <Int32>] [-FailoverTimeSeconds <Int32>] -[-ForwardCallHistory <Boolean>] [-ForwardPai <Boolean>] [-SendSipOptions <Boolean>] -[-MaxConcurrentSessions <System.Int32>] [-Enabled <Boolean>] [-MediaBypass <Boolean>] [-GatewaySiteId <String>] -[-GatewaySiteLbrEnabled <Boolean>] [-MediaRelayRoutingLocationOverride] [-Identity <XdsGlobalRelativeIdentity>] -[-BypassMode <String>] [-GenerateRingingWhileLocatingUser <Boolean>] -[-InboundTeamsNumberTranslationRules <String>] [-InboundPSTNNumberTranslationRules <String>] -[-OutboundTeamsNumberTranslationRules <String>] [-PidfloSupported <Boolean>] [-OutboundPSTNNumberTranslationRules <String>] -[-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to modify the configuration of the previously created Session Border Controller (SBC) configuration. Each configuration contains specific settings for an SBC. These settings configure such entities as SIP signaling port, whether media bypass is enabled on this SBC, will the SBC send SIP options, specify the limit of maximum concurrent sessions, The cmdlet also let drain the SBC by setting parameter -Enabled to true or false state. When the Enabled parameter set to $false, the SBC will continue existing calls, but all new calls routed to another SBC in a route (if exists). - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsOnlinePSTNGateway -Identity sbc.contoso.com -Enabled $true -``` - -This example enables previously created SBC with Identity (and FQDN) sbc.contoso.com. All others parameters will stay default. - -### Example 2 -```powershell -PS C:\> Set-CsOnlinePSTNGateway -Identity sbc.contoso.com -SIPSignalingPort 5064 -ForwardPAI $true -Enabled $true -``` - -This example modifies the configuration of an SBC with identity (and FQDN) sbc.contoso.com. It changes the SIPSignalingPort to 5064 and enabled P-Asserted-Identity field on outbound connections (outbound from Direct Routing to SBC). For each outbound to SBC session, the Direct Routing interface will report in P-Asserted-Identity fields the TEL URI and SIP address of the user who made a call. This is useful when a tenant administrator set identity of the caller as "Anonymous" or a general number of the company, but for the billing purposes the real identity of the user should be reported. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -Used to enable this SBC for outbound calls. Can be used to temporarily remove the SBC from service while it is being updated or during maintenance. Note if the parameter is not set the SBC will be created as disabled (default value -Enabled $false). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverTimeSeconds -When set to 10 (default value), outbound calls that are not answered by the gateway within 10 seconds are routed to the next available trunk; if there are no additional trunks, then the call is automatically dropped. In an organization with slow networks and slow gateway responses, that could potentially result in calls being dropped unnecessarily. The default value is 10. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: 10 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForwardCallHistory -Indicates whether call history information will be forwarded through the trunk. If enabled, the Office 365 PSTN Proxy sends two headers: History-info and Referred-By. The default value is False ($False). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ForwardPai -Indicates whether the P-Asserted-Identity (PAI) header will be forwarded along with the call. The PAI header provides a way to verify the identity of the caller. The default value is False ($False). Setting this parameter to $true will render the from header anonymous, in accordance of RFC5379 and RFC3325. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The parameter is mandatory when modifying an existing SBC. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: -Applicable: Skype for Business Online -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MaxConcurrentSessions -Used by the alerting system. When any value is set, the alerting system will generate an alert to the tenant administrator when the number of concurrent session is 90% or higher than this value. If this parameter is not set, the alerts are not generated. However, the monitoring system will report the number of concurrent sessions every 24 hours. - -```yaml -Type: System.Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MediaBypass -Parameter indicated of the SBC supports Media Bypass and the administrator wants to use it for this SBC. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MediaRelayRoutingLocationOverride -Allows selecting path for media manually. Direct Routing assigns a datacenter for media path based on the public IP of the SBC. We always select closest to the SBC datacenter. However, in some cases a public IP from for example a US range can be assigned to an SBC located in Europe. In this case we will be using not optimal media path. This parameter allows manually set the preferred region for media traffic. We only recommend setting this parameter if the call logs clearly indicate that automatic assignment of the datacenter for media path does not assign the closest to the SBC datacenter - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Microsoft Teams -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FailoverResponseCodes -If Direct Routing receives any 4xx or 6xx SIP error code in response on outgoing Invite (outgoing means call from a Teams client to PSTN with traffic flow :Teams Client -> Direct Routing -> SBC -> Telephony network) the call is considered completed by default. -Setting the SIP codes in this parameter forces Direct Routing on receiving the specified codes try another SBC (if another SBC exists in the voice routing policy of the user). Please find more in "Reference" section of "Phone System Direct Routing" documentation - -```yaml -Type: Int -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: 408, 503, 504 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GatewaySiteId -PSTN Gateway Site Id. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GatewaySiteLbrEnabled -Used to enable this SBC to report assigned site location. Site location is used for Location Based Routing. When this parameter is turned on, the SBC will report the site name as defined by tenant administrator. On incoming call to a Teams user the value of the site assigned to the SBC is compared with the value of the site assigned to the user to make a routing decision. The parameter is mandatory for enabling Location Based Routing feature. The default value is False ($False). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SendSipOptions -Defines if an SBC will or will not send the SIP options. If disabled, the SBC will be excluded from Monitoring and Alerting system. We highly recommend that you enable SIP options. Default value is True. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $true -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SipSignalingPort -Listening port used for communicating with Direct Routing services by using the Transport Layer Security (TLS) protocol. The value must be between 1 and 65535. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BypassMode -Possible values are "None", "Always" and "OnlyForLocalUsers". By setting "Always" mode you indicate that your network is fully routable. If a user usually in site "Seattle", travels to site "Tallinn" and tries to use SBC located in Seattle we will try to deliver the traffic to Seattle assuming that there is connection between Tallinn and Seattle offices. With "OnlyForLocaUsers" you indicate that there is no direct connection between sites. In example above, the traffic will not be send directly from Tallinn to Seattle. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### -GenerateRingingWhileLocatingUser -This parameter is applicableis only for Direct Routing in non-media bypass mode. Sometimes inbound calls from the public switched telephone network (PSTN) to Teams clients can take longer than expected to be established. This can occur for various reasons. When this happens, the caller might not hear anything, the Teams client doesn't ring, and the call might be canceled by some telecommunications providers. This parameter helps to avoid unexpected silences that can occur in this scenario. When enabled for inbound calls from the PSTN to Teams clients, a distinctive audio signal is played to the caller to indicate that Teams is in the process of establishing the call. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundTeamsNumberTranslationRules -This parameter assigns an ordered list of Teams translation rules, that apply to Teams numbers on inbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundPSTNNumberTranslationRules -Creates an ordered list of Teams translation rules, that apply to PSTN number on inbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutbundTeamsNumberTranslationRulesList -Creates an ordered list of Teams translation rules, that apply to Teams Number on outbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OutboundPSTNNumberTranslationRulesList -Assigns an ordered list of Teams translation rules, that apply to PSTN number on outbound direction. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PidfloSupported -Enables PIDF-LO support on the PSTN Gateway. If turned on the .xml body payload is sent to the SBC with the location details of the user. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: $false -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[New-CsOnlinePSTNGateway](New-CsOnlinePSTNGateway.md) - -[Get-CsOnlinePSTNGateway](Get-CsOnlinePSTNGateway.md) - -[Remove-CsOnlinePSTNGateway](Remove-CsOnlinePSTNGateway.md) diff --git a/skype/skype-ps/skype/Set-CsOnlinePstnUsage.md b/skype/skype-ps/skype/Set-CsOnlinePstnUsage.md deleted file mode 100644 index a6e926d27a..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlinePstnUsage.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinepstnusage -applicable: Skype for Business Online -title: Get-CsOnlineUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlinePstnUsage - -## SYNOPSIS -Modifies a set of strings that identify the allowed online public switched telephone network (PSTN) usages. This cmdlet can be used to add usages to the list of online PSTN usages or remove usages from the list. - -## SYNTAX - -### Identity (Default) -``` -Set-CsOnlinePstnUsage [-Tenant <Guid>] [-Usage <PSListModifier>] [[-Identity] <XdsIdentity>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsOnlinePstnUsage [-Tenant <Guid>] [-Usage <PSListModifier>] [-Instance <PSObject>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Online PSTN usages are string values that are used for call authorization. An online PSTN usage links an online voice policy to a route. The `Set-CsOnlinePstnUsage` cmdlet is used to add or remove phone usages to or from the usage list. This list is global so it can be used by policies and routes throughout the tenant. - -This cmdlet is used when configuring Microsoft Phone System Direct Routing. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Set-CsOnlinePstnUsage -Identity global -Usage @{add="International"} -``` - -This command adds the string "International" to the current list of available PSTN usages. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Set-CsOnlinePstnUsage -Identity global -Usage @{remove="Local"} -``` - -This command removes the string "Local" from the list of available PSTN usages. - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> Set-CsOnlinePstnUsage -Usage @{remove="Local"} -``` - -The command in this example performs the exact same action as the command in Example 2: it removes the "Local" PSTN usage. This example shows the command without the Identity parameter specified. The only Identity available to the Set-CsOnlinePstnUsage cmdlet is the Global identity; omitting the Identity parameter defaults to Global. - -### -------------------------- Example 4 -------------------------- -``` -PS C:\> Set-CsOnlinePstnUsage -Usage @{replace="International","Restricted"} -``` - -This command replaces everything in the usage list with the values International and Restricted. All previously existing usages are removed. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses any confirmation prompts that would otherwise be displayed before making changes. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The scope at which these settings are applied. The Identity for this cmdlet is always Global. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -A reference to a PSTN usage object. This object must be of type PstnUsages and can be retrieved by calling the Get-CsOnlinePstnUsage cmdlet. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Usage -Contains a list of allowable usage strings. These entries can be any string value. - -```yaml -Type: PSListModifier -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Get-CsOnlinePstnUsage](https://docs.microsoft.com/powershell/module/skype/get-csonlinepstnusage?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsOnlineVoiceApplicationInstance.md b/skype/skype-ps/skype/Set-CsOnlineVoiceApplicationInstance.md deleted file mode 100644 index c3d67f91f3..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineVoiceApplicationInstance.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceapplicationinstance -applicable: Skype for Business Online -title: Set-CsOnlineVoiceApplicationInstance -author: -ms.author:Danny Levin -ms.reviewer: -schema: 2.0.0 -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Set-CsOnlineVoiceApplicationInstance - -## SYNOPSIS -The `Set-CsOnlineVoiceApplicationInstance` modifies an application instance in Azure Active Directory. - -## SYNTAX -``` -Set-CsOnlineVoiceApplicationInstance [-WhatIf] [-Confirm] [-TelephoneNumber <String>] [[-Identity] <String>] - [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [-AsJob] -``` - -## DESCRIPTION -This cmdlet is used to modify an application instance in Azure Active Directory. - -## EXAMPLES - -### Example 1 -```powershell -Set-CsOnlineVoiceApplicationInstance -Identity testra1@contoso.com -TelephoneNumber +14255550100 -``` - -This example sets a phone number to the resource account testra1@contoso.com. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: DC - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The user principal name (UPN) of the resource account in Azure Active Directory. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumber -The phone number to be assigned to the resource account. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS - -[New-CsOnlineApplicationInstance](https://docs.microsoft.com/powershell/module/skype/new-csonlineapplicationinstance) diff --git a/skype/skype-ps/skype/Set-CsOnlineVoiceRoute.md b/skype/skype-ps/skype/Set-CsOnlineVoiceRoute.md deleted file mode 100644 index fe1220efd8..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineVoiceRoute.md +++ /dev/null @@ -1,288 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroute -applicable: Skype for Business Online -title: Get-CsOnlineUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineVoiceRoute - -## SYNOPSIS -Modifies an online voice route. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). - -## SYNTAX - -### Identity (Default) -``` -Set-CsOnlineVoiceRoute [-Tenant <Guid>] [-Description <String>] [-NumberPattern <String>] - [-OnlinePstnUsages <PSListModifier>] [-OnlinePstnGatewayList <PSListModifier>] [-Priority <Int32>] - [[-Identity] <XdsGlobalRelativeIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsOnlineVoiceRoute [-Tenant <Guid>] [-Description <String>] [-NumberPattern <String>] - [-OnlinePstnUsages <PSListModifier>] [-OnlinePstnGatewayList <PSListModifier>] [-Priority <Int32>] - [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Use this cmdlet to modify an existing online voice route. Online voice routes are associated with online voice policies through online public switched telephone network (PSTN) usages. A online voice route includes a regular expression that identifies which phone numbers will be routed through a given voice route: phone numbers matching the regular expression will be routed through this route. - -This cmdlet is used when configuring Microsoft Phone System Direct Routing. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Set-CsOnlineVoiceRoute -Identity Route1 -Description "Test Route" -``` - -This command sets the Description of the Route1 online voice route to "Test Route." - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Set-CsOnlineVoiceRoute -Identity Route1 -PstnUsages @{add="Long Distance"} -``` - -The command in this example modifies the online voice route with the identity Route1 to add the online PSTN usage Long Distance to the list of usages for this voice route. Long Distance must be in the list of global online PSTN usages (which can be retrieved with a call to the `Get-CsOnlinePstnUsage` cmdlet). - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> $x = (Get-CsOnlinePstnUsage).Usage - -PS C:\> Set-CsOnlineVoiceRoute -Identity Route1 -OnlinePstnUsages @{replace=$x} -``` - -This example modifies the online voice route named Route1 to populate that route's list of online PSTN usages with all the existing usages for the organization. The first command in this example retrieves the list of global online PSTN usages. Notice that the call to the `Get-CsOnlinePstnUsage` cmdlet is in parentheses; this means that we first retrieve an object containing PSTN usage information. (Because there is only one--global--PSTN usage, only one object will be retrieved.) The command then retrieves the Usage property of this object. That property, which contains a list of online PSTN usages, is assigned to the variable $x. In the second line of this example, the Set-CsOnlineVoiceRoute cmdlet is called to modify the online voice route with the identity Route1. Notice the value passed to the OnlinePstnUsages parameter: @{replace=$x}. This value says to replace everything in the OnlinePstnUsages list for this route with the contents of $x, which contain the online PSTN usages list retrieved in line 1. - -### -------------------------- Example 4 -------------------------- -``` -PS C:\> $x = Get-CsOnlineVoiceRoute -Identity Route1 - -PS C:\> $x.Name = "RouteA" - -PS C:\> Set-CsOnlineVoiceRoute -Instance $x -``` - -This set of commands changes the Name property of the online voice route with the identity Route1 to RouteA. Changing the Name property automatically changes the Identity property, in this case to RouteA. - -In the first line, the `Get-CsOnlineVoiceRoute` cmdlet is called to retrieve the online voice route with the identity Route1. The returned object is stored in the variable $x. Next, the Name property of that object is assigned the string value "RouteA". Finally, the object (contained in the variable $x) is passed to the Instance parameter of the `Set-CsOnlineVoiceRoute` cmdlet to make the change. - -### -------------------------- Example 5 -------------------------- -``` -PS C:\> $y = Get-CsOnlineVoiceRoute -Identity Route1 - -PS C:\> $y.OnlinePstnGatewayList.Add("192.168.0.100") - -PS C:\> Set-CsOnlineVoiceRoute -Instance $y -``` - -This example modifies the online voice route named Route1 and populates that route's list of online PSTN gateways (OnlinePstnGatewayList) with the server role of the gateway with the identity PstnGateway:192.168.0.100. In the first line of this example, the `Get-CsOnlineVoiceRoute` cmdlet is called to retrieve the online voice route we want to modify, in this case Route1. Next we call the Add method on the OnlinePstnGatewayList property of Route1. We pass the Add method the Identity of the service we want to add. Finally, we call the `Set-CsOnlineVoiceRoute` cmdlet, passing the Instance parameter the variable $y, which will update Route1 (stored in $y) with the newly-added online PSTN gateway. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A description of what this phone route is for. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses any confirmation prompts that would otherwise be displayed before making changes. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The unique identity of the online voice route. (If the route name contains a space, such as Test Route, you must enclose the full string in parentheses.) - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. This object can be retrieved by calling the `Get-CsOnlineVoiceRoute` cmdlet. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NumberPattern -A regular expression that specifies the phone numbers to which this route applies. Numbers matching this pattern will be routed according to the rest of the routing settings. For example, the default number pattern, [0-9]{10}, specifies a 10-digit number containing any digits 0 through 9. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlinePstnGatewayList -This parameter contains a list of online gateways associated with this online voice route. Each member of this list must be the service Identity of the online PSTN gateway. The service Identity is the fully qualified domain name (FQDN) of the pool or the IP address of the server. For example, redmondpool.litwareinc.com. - -By default this list is empty. However, if you leave this parameter blank when creating a new voice route, you'll receive a warning message. - -```yaml -Type: PSListModifier -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlinePstnUsages -A list of online PSTN usages (such as Local, Long Distance, etc.) that can be applied to this online voice route. The PSTN usage must be an existing usage (PSTN usages can be retrieved by calling the Get-CsOnlinePstnUsage cmdlet). - -By default this list is empty. However, if you leave this parameter blank when creating a new online voice route, you'll receive a warning message. - -```yaml -Type: PSListModifier -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -A number could resolve to multiple online voice routes. The priority determines the order in which the routes will be applied if more than one route is possible. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroute?view=skype-ps) - -[New-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroute?view=skype-ps) - -[Remove-CsOnlineVoiceRoute](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroute?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsOnlineVoiceRoutingPolicy.md b/skype/skype-ps/skype/Set-CsOnlineVoiceRoutingPolicy.md deleted file mode 100644 index 345e89e3a7..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineVoiceRoutingPolicy.md +++ /dev/null @@ -1,238 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceroutingpolicy -applicable: Skype for Business Online -title: Get-CsOnlineUser -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineVoiceRoutingPolicy - -## SYNOPSIS -Modifies an existing online voice routing policy. Online voice routing policies manage online PSTN usages for Phone System users. - -## SYNTAX - -### Identity (Default) -``` -Set-CsOnlineVoiceRoutingPolicy [-Tenant <Guid>] [-OnlinePstnUsages <PSListModifier>] - [-Description <String>] [-RouteType <String>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### Instance -``` -Set-CsOnlineVoiceRoutingPolicy [-Tenant <Guid>] [-OnlinePstnUsages <PSListModifier>] - [-Description <String>] [-RouteType <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. - -Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Set-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages @{Add="Long Distance"} -``` - -The command shown in Example 1 adds the online PSTN usage "Long Distance" to the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Set-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages @{Remove="Local"} -``` - -In Example 2, the online PSTN usage "Local" is removed from the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy. - -### -------------------------- Example 3 -------------------------- -``` -PS C:\> Set-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -contains "Local"} | Set-CsOnlineVoiceRoutingPolicy -OnlinePstnUsages @{Remove="Local"} -``` - -Example 3 removes the online PSTN usage "Local" from all the online voice routing policies that include that usage. In order to do this, the command first calls the `Get-CsOnlineVoiceRoutingPolicy` cmdlet without any parameters in order to return a collection of all the available online voice routing policies. That collection is then piped to the Where-Object cmdlet, which picks out only those policies where the OnlinePstnUsages property includes (-contains) the "Local" usage. Those policies are then piped to the `Set-CsOnlineVoiceRoutingPolicy` cmdlet, which deletes the Local usage from each policy. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Enables administrators to provide explanatory text to accompany an online voice routing policy. For example, the Description might include information about the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier assigned to the policy when it was created. Online voice routing policies can be assigned at the global scope or the per-user scope. To refer to the global instance, use this syntax: - --Identity global - -To refer to a per-user policy, use syntax similar to this: - --Identity "RedmondOnlineVoiceRoutingPolicy" - -If you do not specify an Identity, then the `Set-CsOnlineVoiceRoutingPolicy` cmdlet will modify the global policy. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -OnlinePstnUsages -A list of online PSTN usages (such as Local or Long Distance) that can be applied to this online voice routing policy. The online PSTN usage must be an existing usage. (PSTN usages can be retrieved by calling the `Get-CsOnlinePstnUsage` cmdlet.) - -```yaml -Type: PSListModifier -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RouteType -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose online voice routing policies are being changed. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS -[New-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroutingpolicy?view=skype-ps) - -[Get-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoiceroutingpolicy?view=skype-ps) - -[Grant-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoiceroutingpolicy?view=skype-ps) - -[Remove-CsOnlineVoiceRoutingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoiceroutingpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsOnlineVoiceUserBulk.md b/skype/skype-ps/skype/Set-CsOnlineVoiceUserBulk.md deleted file mode 100644 index 4807d69b5b..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineVoiceUserBulk.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceuserbulk -applicable: Skype for Business Online -title: Set-CsOnlineVoiceUserBulk -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineVoiceUserBulk - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -``` -Set-CsOnlineVoiceUserBulk [-Tenant <Guid>] [-NumberAssignmentDetails <>] [-DomainController <Fqdn>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -Confirm -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -PARAMVALUE: Fqdn - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NumberAssignmentDetails -PARAMVALUE: List - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineVoicemailPolicy.md b/skype/skype-ps/skype/Set-CsOnlineVoicemailPolicy.md deleted file mode 100644 index fcc8e1477f..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineVoicemailPolicy.md +++ /dev/null @@ -1,252 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailpolicy -applicable: Skype for Business Online -title: Set-CsOnlineVoicemailPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineVoicemailPolicy - -## SYNOPSIS -Modifies an existing Online Voicemail policy. Online Voicemail policies determine whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify voicemail maximum recording length for a user. - -## SYNTAX - -### Identity (Default) -``` -Set-CsOnlineVoicemailPolicy [-Tenant <Guid>] [-EnableTranscription <Boolean>] [-ShareData <String>] - [-EnableTranscriptionProfanityMasking <Boolean>] [-EnableTranscriptionTranslation <Boolean>] [-EnableEditingCallAnswerRulesSetting <Boolean>] [-MaximumRecordingLength <Duration>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### Instance -``` -Set-CsOnlineVoicemailPolicy [-Tenant <Guid>] [-EnableTranscription <Boolean>] [-ShareData <String>] - [-EnableTranscriptionProfanityMasking <Boolean>] [-EnableTranscriptionTranslation <Boolean>] [-EnableEditingCallAnswerRulesSetting <Boolean>] [-MaximumRecordingLength <Duration>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Online Voicemail service provides organizations with voicemail deposit capabilities for Phone System implementation. - -By default, users enabled for Phone System will be enabled for Online Voicemail, and Online Voicemail policy controls whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify voicemail maximum recording length for a user. Online Voicemail transcription is enabled by default, transcription profanity masking is disabled by default, editing call answer rule settings is enabled by default, and voicemail maximum recording length is set to 5 minutes by default. Tenant admin would be able to modify existing policies to match the organization's requirements. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineVoicemailPolicy -Identity "CustomOnlineVoicemailPolicy" -MaximumRecordingLength ([TimeSpan]::FromSeconds(60)) -``` - -The command shown in Example 1 changes the MaximumRecordingLength to 60 seconds for the per-user online voicemail policy CustomOnlineVoicemailPolicy. - -### -------------------------- Example 2 -------------------------- -``` -Set-CsOnlineVoicemailPolicy -EnableTranscriptionProfanityMasking $false -``` - -The command shown in Example 2 changes the EnableTranscriptionProfanityMasking to false for tenant level global online voicemail policy when calling without Identity parameter. - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTranscription -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTranscriptionProfanityMasking -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableTranscriptionTranslation -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableEditingCallAnswerRulesSetting -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MaximumRecordingLength -A duration of voicemail maximum recording length. The length should be between 30 seconds to 10 minutes. - -```yaml -Type: Duration -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -A unique identifier specifying the scope, and in some cases the name, of the policy. If this parameter is omitted, Set-CsOnlineVoicemailPolicy would update tenant level Global policy value. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the Skype for Business Online tenant account whose voicemail policy is to be retrieved. For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" You can return the tenant ID for each of your tenants by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Get-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoicemailpolicy?view=skype-ps) - -[New-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoicemailpolicy?view=skype-ps) - -[Remove-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoicemailpolicy?view=skype-ps) - -[Grant-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoicemailpolicy?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsOnlineVoicemailUserSettings.md b/skype/skype-ps/skype/Set-CsOnlineVoicemailUserSettings.md deleted file mode 100644 index 15f4941e1d..0000000000 --- a/skype/skype-ps/skype/Set-CsOnlineVoicemailUserSettings.md +++ /dev/null @@ -1,315 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailusersettings -applicable: Skype for Business Online -title: Set-CsOnlineVoicemailUserSettings -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOnlineVoicemailUserSettings - -## SYNOPSIS -Use the Set-CsOnlineVoicemailUserSettings cmdlet to modify the online voicemail user settings of a specific user. -New online voicemail user settings of the user would be returned after executing. - -## SYNTAX - -``` -Set-CsOnlineVoicemailUserSettings -Identity <String> [-VoicemailEnabled <Boolean>] [-PromptLanguage <String>] [-OofGreetingEnabled <Boolean>] [-OofGreetingFollowAutomaticRepliesEnabled <Boolean>] [-OofGreetingFollowCalendarEnabled <Boolean>] [-CallAnswerRule <DeclineCall | PromptOnly | PromptOnlyWithTransfer | RegularVoicemail | VoicemailWithTransferOption>] [-TransferTarget <String>] [-DefaultGreetingPromptOverwrite <String>] [-DefaultOofGreetingPromptOverwrite <String>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-CsOnlineVoicemailUserSettings cmdlet lets tenant admin modify the online voicemail user settings of a specific user in the organization. New online voicemail user settings of the user would be returned after executing. -For example, tenant admin could enable/disable voicemail, change voicemail prompt language, modify out-of-office voicemail greeting settings, or setup simple call answer rules. Only those properties that tenant admin have actually provided with be modified. If an online voicemail user setting was not set by tenant admin, it would remain the old value after this cmdlet has been executed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsOnlineVoicemailUserSettings -Identity sip:user@contoso.com -VoicemailEnabled $true -``` - -This example changes VoicemailEnabled setting to true for the user with SIP URI sip:user@contoso.com. - -### -------------------------- Example 2 -------------------------- -``` -Set-CsOnlineVoicemailUserSettings -Identity "00000000-0000-0000-0000-000000000000" -PromptLanguage "en-US" -OofGreetingFollowCalendarEnabled $false -``` - -This example changes PromptLanguage setting to "en-US" and OofGreetingFollowCalendarEnabled setting to false for the user with Object ID "00000000-0000-0000-0000-000000000000". - -### -------------------------- Example 3 -------------------------- -``` -Set-CsOnlineVoicemailUserSettings -Identity "00000000-0000-0000-0000-000000000000" -CallAnswerRule PromptOnlyWithTransfer -TransferTarget sip:user2@contoso.com -``` - -This example changes CallAnswerRule setting to PromptOnlyWithTransfer and set TransferTarget to "sip:user2@contoso.com" for the user with Object ID "00000000-0000-0000-0000-000000000000". - -### -------------------------- Example 4 -------------------------- -``` -Set-CsOnlineVoicemailUserSettings -Identity "00000000-0000-0000-0000-000000000000" -CallAnswerRule VoicemailWithTransferOption -TransferTarget "+12345678900" -``` - -This example changes CallAnswerRule setting to VoicemailWithTransferOption and set TransferTarget to "+12345678900" for the user with Object ID "00000000-0000-0000-0000-000000000000". - -### -------------------------- Example 5 -------------------------- -``` -Set-CsOnlineVoicemailUserSettings -Identity "00000000-0000-0000-0000-000000000000" -DefaultGreetingPromptOverwrite "Hi, I am currently not available." -``` - -This example changes DefaultGreetingPromptOverwrite setting to "Hi, I am currently not available." for the user with Object ID "00000000-0000-0000-0000-000000000000". - - -## PARAMETERS - -### -Identity -The Identity parameter represents the ID of the specific user in your organization; this can be either a SIP URI or an Object ID. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -VoicemailEnabled -The VoicemailEnabled parameter represents whether to enable voicemail service. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PromptLanguage -The PromptLanguage parameter represents the language that is used to play voicemail prompts. - -Now the following languages are supported: - -- "ar-EG" (Arabic - Egypt) -- "ca-ES" (Catalan - Catalan) -- "da-DK" (Danish - Denmark) -- "de-DE" (German - Germany) -- "en-AU" (English - Australia) -- "en-CA" (English - Canada) -- "en-GB" (English - United Kingdom) -- "en-IN" (English - India) -- "en-US" (English - United States) -- "es-ES" (Spanish - Spain) -- "es-MX" (Spanish - Mexico) -- "fi-FI" (Finnish - Finland) -- "fr-CA" (French - Canada) -- "fr-FR" (French - France) -- "it-IT" (Italian - Italy) -- "ja-JP" (Japanese - Japan) -- "ko-KR" (Korean - Korea) -- "nl-NL" (Dutch - Netherlands) -- "nb-NO" (Norwegian, Bokmål - Norway) -- "pl-PL" (Polish - Poland) -- "pt-BR" (Portuguese - Brazil) -- "pt-PT" (Portuguese - Portugal) -- "ru-RU" (Russian - Russia) -- "sv-SE" (Swedish - Sweden) -- "tr-TR" (Turkish - Turkey) -- "zh-CN" (Chinese - Simplified, PRC) -- "zh-TW" (Chinese - Traditional, Taiwan) -- "zh-HK" (Chinese - Traditional, Hong Kong S.A.R.) -- "cs-CZ" (Czech - Czech Republic) -- "th-TH" (Thai - Thailand) -- "el-GR" (Greek - Greece) -- "hu-HU" (Hungarian - Hungary) -- "sk-SK" (Slovak - Slovakia) -- "hr-HR" (Croatian - Croatia) -- "sl-SI" (Slovenian - Slovenia) -- "id-ID" (Indonesian - Indonesia) -- "ro-RO" (Romanian - Romania) -- "vi-VN" (Vietnamese - Viet Nam) - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OofGreetingEnabled -The OofGreetingEnabled parameter represents whether to play out-of-office greeting in voicemail deposit scenario. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OofGreetingFollowAutomaticRepliesEnabled -The OofGreetingFollowAutomaticRepliesEnabled parameter represents whether to play out-of-office greeting in voicemail deposit scenario when user set automatic replies in Outlook. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OofGreetingFollowCalendarEnabled -The OofGreetingFollowCalendarEnabled parameter represents whether to play out-of-office greeting in voicemail deposit scenario when user set out-of-office in calendar. - -```yaml -Type: System.Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CallAnswerRule -The CallAnswerRule parameter represents the value of the call answer rule, which can be any of the following: - -- DeclineCall -- PromptOnly -- PromptOnlyWithTransfer -- RegularVoicemail -- VoicemailWithTransferOption - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TransferTarget -The TransferTarget parameter represents the target to transfer the call when call answer rule set to PromptOnlyWithTransfer or VoicemailWithTransferOption. -Value of this parameter should be a SIP URI of another user, an auto attendant, or a hunt group (call queue) in your organization. -For user with Enterprise Voice enabled, a valid telephone number could also be accepted as TransferTarget. - - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultGreetingPromptOverwrite -The DefaultGreetingPromptOverwrite parameter represents the contents that overwrite the default normal greeting prompt. -If user normal custom greeting is not set and DefaultGreetingPromptOverwrite is not empty, voicemail service will play this overwrite greeting instead of default normal greeting in voicemail deposit scenario. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultOofGreetingPromptOverwrite -The DefaultOofGreetingPromptOverwrite parameter represents the contents that overwrite the default out-of-office greeting prompt. -If user out-of-office custom greeting is not set and DefaultOofGreetingPromptOverwrite is not empty, voicemail service will play this overwrite greeting instead of default out-of-office greeting in voicemail deposit scenario. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - - -## INPUTS - -### None - -## OUTPUTS - -### Microsoft.Rtc.Management.Hosted.Voicemail.Models.VoicemailUserSettings - - -## NOTES - - -## RELATED LINKS - -[Get-CsOnlineVoicemailUserSettings](Get-CsOnlineVoicemailUserSettings.md) - diff --git a/skype/skype-ps/skype/Set-CsOrganizationalAutoAttendant.md b/skype/skype-ps/skype/Set-CsOrganizationalAutoAttendant.md deleted file mode 100644 index 61e1313917..0000000000 --- a/skype/skype-ps/skype/Set-CsOrganizationalAutoAttendant.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csorganizationalautoattendant -applicable: Skype for Business Online -title: Set-CsOrganizationalAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsOrganizationalAutoAttendant - -## SYNOPSIS -Use the Set-CsOrganizationalAutoAttendant cmdlet to modify the properties of an existing Auto Attendant (AA). - -## SYNTAX - -``` -Set-CsOrganizationalAutoAttendant [-Instance] <OrgAutoAttendant> [-Tenant <Guid>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The Set-CsOrganizationalAutoAttendant cmdlet lets you modify the properties of an auto attendant. For example, you can change the phone number, the operator, the greeting, or the menu prompts. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -$oaa = Get-CsOrganizationalAutoAttendant -PrimaryUri "sip:mainoaa@contoso.com" -$oaa.LineUris = @([System.Uri] "tel:+11098765432") -Set-CsOrganizationalAutoAttendant -Instance $oaa -``` - -This example changes the telephone number for the OAA that has a Primary URI of sip:mainoaa@contoso.com. - -### -------------------------- Example 2 -------------------------- -``` -$oaa = Get-CsOrganizationalAutoAttendant -PrimaryUri "sip:mainoaa@contoso.com" - -$christmasGreetingPrompt = New-CsOrganizationalAutoAttendantPrompt -TextToSpeechPrompt "Our offices are closed for Christmas from December 24 to December 26. Please call back later." -$christmasMenuOption = New-CsOrganizationalAutoAttendantMenuOption -Action DisconnectCall -DtmfResponse Automatic -$christmasMenu = New-CsOrganizationalAutoAttendantMenu -Name "Christmas Menu" -MenuOptions @($christmasMenuOption) -$christmasCallFlow = New-CsOrganizationalAutoAttendantCallFlow -Name "Christmas" -Greetings @($christmasGreetingPrompt) -Menu $christmasMenu - -$dtr = New-CsOnlineDateTimeRange -Start "24/12/2017" -End "26/12/2017" -$christmasSchedule = New-CsOnlineSchedule -Name "Christmas" -FixedSchedule -DateTimeRanges @($dtr) - -$christmasCallHandlingAssociation = New-CsOrganizationalAutoAttendantCallHandlingAssociation -Type Holiday -ScheduleId $christmasSchedule.Id -CallFlowId $christmasCallFlow.Id - -$oaa.CallFlows = $oaa.CallFlows + @($christmasCallFlow) -$oaa.Schedules = $oaa.Schedules + @($christmasSchedule) -$oaa.CallHandlingAssociations = $oaa.CallHandlingAssociations + @($christmasCallHandlingAssociation) - -Set-CsOrganizationalAutoAttendant -Instance $oaa -``` - -This example adds a Christmas holiday to an OAA that a Primary URI of sip:mainoaa@contoso.com. - -## PARAMETERS - -### -Instance -The Instance parameter is the object reference to the OAA to be modified. - -You can retrieve an object reference to an existing OAA by using the Get-CsOrganizationalAutoAttendant cmdlet and assigning the returned value to a variable. - -```yaml -Type: OrgAutoAttendant -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -{{Fill DomainController Description}} - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{Fill Force Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Hosted.OAA.Models.OrgAutoAttendant -The Set-CsOrganizationalAutoAttendant cmdlet accepts a Microsoft.Rtc.Management.Hosted.OAA.Models.OrgAutoAttendant object as the Instance parameter. - - -## OUTPUTS - -### None -The Set-CsOrganizationalAutoAttendant cmdlet does not return any objects or values. Instead, the cmdlet modifies the instance of the Microsoft.Rtc.Management.Hosted.OAA.Models.OrgAutoAttendant object that is passed in as the Instance parameter. - - -## NOTES - -## RELATED LINKS - -[New-CsOrganizationalAutoAttendant](New-CsOrganizationalAutoAttendant.md) - -[Get-CsOrganizationalAutoAttendant](Get-CsOrganizationalAutoAttendant.md) - diff --git a/skype/skype-ps/skype/Set-CsOutboundCallingNumberTranslationRule.md b/skype/skype-ps/skype/Set-CsOutboundCallingNumberTranslationRule.md index 35c8cac16c..02b03a405f 100644 --- a/skype/skype-ps/skype/Set-CsOutboundCallingNumberTranslationRule.md +++ b/skype/skype-ps/skype/Set-CsOutboundCallingNumberTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csoutboundcallingnumbertranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/set-csoutboundcallingnumbertranslationrule applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsOutboundCallingNumberTranslationRule schema: 2.0.0 @@ -232,4 +232,3 @@ Instead, the `Set-CsOutboundCallingNumberTranslationRule` cmdlet modifies existi [New-CsOutboundCallingNumberTranslationRule](New-CsOutboundCallingNumberTranslationRule.md) [Remove-CsOutboundCallingNumberTranslationRule](Remove-CsOutboundCallingNumberTranslationRule.md) - diff --git a/skype/skype-ps/skype/Set-CsOutboundTranslationRule.md b/skype/skype-ps/skype/Set-CsOutboundTranslationRule.md index f2b6106f9c..8840737092 100644 --- a/skype/skype-ps/skype/Set-CsOutboundTranslationRule.md +++ b/skype/skype-ps/skype/Set-CsOutboundTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csoutboundtranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/set-csoutboundtranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsOutboundTranslationRule schema: 2.0.0 @@ -256,4 +256,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.T [Remove-CsOutboundTranslationRule](Remove-CsOutboundTranslationRule.md) [Get-CsOutboundTranslationRule](Get-CsOutboundTranslationRule.md) - diff --git a/skype/skype-ps/skype/Set-CsPartnerApplication.md b/skype/skype-ps/skype/Set-CsPartnerApplication.md index 82e484dadb..b1273b0d76 100644 --- a/skype/skype-ps/skype/Set-CsPartnerApplication.md +++ b/skype/skype-ps/skype/Set-CsPartnerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspartnerapplication +online version: https://learn.microsoft.com/powershell/module/skype/set-cspartnerapplication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPartnerApplication schema: 2.0.0 @@ -131,9 +131,9 @@ Accept wildcard characters: False Certificate (in Base64 encoded format) that can be assigned to the partner application. To read raw data from a certificate and then convert that data to the required format, use commands similar to these: -`$x = Get-Content "C:\Certificates\PartnerApplication.cer" -Encoding Byte` +`$x = [System.IO.File]::ReadAllBytes('C:\Certificates\PartnerApplication.cer')` -`$y = \[Convert\]::ToBase64String($x)` +`$y = [Convert]::ToBase64String($x)` You can then use this syntax to assign the certificate data stored in the variable $y: @@ -375,4 +375,3 @@ Instead, the `Set-CsPartnerApplication` cmdlet modifies existing instances of th [New-CsPartnerApplication](New-CsPartnerApplication.md) [Remove-CsPartnerApplication](Remove-CsPartnerApplication.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatActiveServer.md b/skype/skype-ps/skype/Set-CsPersistentChatActiveServer.md index e45ad2dd4b..6bb38b73c1 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatActiveServer.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatActiveServer.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchatactiveserver -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchatactiveserver +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPersistentChatActiveServer schema: 2.0.0 manager: rogupta @@ -203,4 +203,3 @@ None. ## RELATED LINKS [Set-CsPersistentChatState](Set-CsPersistentChatState.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatAddin.md b/skype/skype-ps/skype/Set-CsPersistentChatAddin.md index 49dd1c47e1..57d307c906 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatAddin.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatAddin.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchataddin -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchataddin +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPersistentChatAddin schema: 2.0.0 manager: rogupta @@ -54,7 +54,7 @@ Set-CsPersistentChatAddin -Identity "atl-cs-001.litwareinc.com\ITPersistentChatA ``` Example 1 modifies the URL assigned to the Persistent Chat add-in ITPersistentChatAddin. -In this case, the URL is changed to https://atl-cs-001.litwareinc.com/itchat2. +In this case, the URL is changed to `https://atl-cs-001.litwareinc.com/itchat2`. ## PARAMETERS @@ -183,4 +183,3 @@ Instead, the `Set-CsPersistentChatAddin` cmdlet modifies existing instances of t [New-CsPersistentChatAddin](New-CsPersistentChatAddin.md) [Remove-CsPersistentChatAddin](Remove-CsPersistentChatAddin.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatCategory.md b/skype/skype-ps/skype/Set-CsPersistentChatCategory.md index 7929d32d6d..5398bb8787 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatCategory.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatCategory.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchatcategory -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchatcategory +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPersistentChatCategory schema: 2.0.0 manager: rogupta @@ -387,4 +387,3 @@ Instead, the `Set-CsPersistentChatCategory` cmdlet modifies existing instances o [New-CsPersistentChatCategory](New-CsPersistentChatCategory.md) [Remove-CsPersistentChatCategory](Remove-CsPersistentChatCategory.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatComplianceConfiguration.md b/skype/skype-ps/skype/Set-CsPersistentChatComplianceConfiguration.md index b9804216d3..9dabe65046 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatComplianceConfiguration.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatComplianceConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchatcomplianceconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchatcomplianceconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPersistentChatComplianceConfiguration schema: 2.0.0 manager: rogupta @@ -357,4 +357,3 @@ Instead, the `Set-CsPersistentChatComplianceConfiguration` cmdlet modifies exist [New-CsPersistentChatComplianceConfiguration](New-CsPersistentChatComplianceConfiguration.md) [Remove-CsPersistentChatComplianceConfiguration](Remove-CsPersistentChatComplianceConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatConfiguration.md b/skype/skype-ps/skype/Set-CsPersistentChatConfiguration.md index f30dd63660..f174447fa0 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatConfiguration.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchatconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchatconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2015 title: Set-CsPersistentChatConfiguration schema: 2.0.0 manager: rogupta @@ -276,4 +276,3 @@ Instead, the `Set-CsPersistentChatConfiguration` cmdlet modifies existing instan [New-CsPersistentChatConfiguration](New-CsPersistentChatConfiguration.md) [Remove-CsPersistentChatConfiguration](Remove-CsPersistentChatConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatPolicy.md b/skype/skype-ps/skype/Set-CsPersistentChatPolicy.md index a0d6ac8542..0be410776e 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatPolicy.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatPolicy.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchatpolicy -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchatpolicy +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPersistentChatPolicy schema: 2.0.0 manager: rogupta @@ -235,4 +235,3 @@ Instead, the `Set-CsPersistentChatPolicy` cmdlet modifies existing instances of [New-CsPersistentChatPolicy](New-CsPersistentChatPolicy.md) [Remove-CsPersistentChatPolicy](Remove-CsPersistentChatPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatRoom.md b/skype/skype-ps/skype/Set-CsPersistentChatRoom.md index 8be9df3859..0a6014d89c 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatRoom.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatRoom.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchatroom -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchatroom +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPersistentChatRoom schema: 2.0.0 manager: rogupta @@ -485,4 +485,3 @@ Instead, the `Set-CsPersistentChatRoom` cmdlet modifies existing instances of th [New-CsPersistentChatRoom](New-CsPersistentChatRoom.md) [Remove-CsPersistentChatRoom](Remove-CsPersistentChatRoom.md) - diff --git a/skype/skype-ps/skype/Set-CsPersistentChatState.md b/skype/skype-ps/skype/Set-CsPersistentChatState.md index 70f4e797c4..b0d38cefb9 100644 --- a/skype/skype-ps/skype/Set-CsPersistentChatState.md +++ b/skype/skype-ps/skype/Set-CsPersistentChatState.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspersistentchatstate -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspersistentchatstate +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPersistentChatState schema: 2.0.0 manager: rogupta @@ -179,4 +179,3 @@ Instead, the `Set-CsPersistentChatState` cmdlet modifies existing instances of t [Get-CsPersistentChatState](Get-CsPersistentChatState.md) [Set-CsPersistentChatActiveServer](Set-CsPersistentChatActiveServer.md) - diff --git a/skype/skype-ps/skype/Set-CsPinPolicy.md b/skype/skype-ps/skype/Set-CsPinPolicy.md index 792867a008..8432fb8fd2 100644 --- a/skype/skype-ps/skype/Set-CsPinPolicy.md +++ b/skype/skype-ps/skype/Set-CsPinPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspinpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-cspinpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPinPolicy schema: 2.0.0 @@ -362,4 +362,3 @@ Instead, the cmdlet configures one or more instances of the Microsoft.Rtc.Manage [New-CsPinPolicy](New-CsPinPolicy.md) [Remove-CsPinPolicy](Remove-CsPinPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsPlatformServiceSettings.md b/skype/skype-ps/skype/Set-CsPlatformServiceSettings.md index f2b97a72c3..9bf4ba1881 100644 --- a/skype/skype-ps/skype/Set-CsPlatformServiceSettings.md +++ b/skype/skype-ps/skype/Set-CsPlatformServiceSettings.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csplatformservicesettings -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csplatformservicesettings +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPlatformServiceSettings schema: 2.0.0 manager: rogupta @@ -13,7 +13,7 @@ ms.reviewer: # Set-CsPlatformServiceSettings ## SYNOPSIS -Modifies the Skype for Business on Mac capabilites in your organization. This cmdlet was introduced in Skype for Business Server 2015 Cumulative Update 6 (December 2017). +Modifies the Skype for Business on Mac capabilities in your organization. This cmdlet was introduced in Skype for Business Server 2015 Cumulative Update 6 (December 2017). ## SYNTAX @@ -293,8 +293,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## NOTES ## RELATED LINKS -[New-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/new-csplatformservicesettings?view=skype-ps) +[New-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/new-csplatformservicesettings?view=skype-ps) -[Get-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/get-csplatformservicesettings?view=skype-ps) +[Get-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/get-csplatformservicesettings?view=skype-ps) -[Remove-CsPlatformServiceSettings](https://docs.microsoft.com/powershell/module/skype/remove-csplatformservicesettings?view=skype-ps) +[Remove-CsPlatformServiceSettings](https://learn.microsoft.com/powershell/module/skype/remove-csplatformservicesettings?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsPresenceManagementState.md b/skype/skype-ps/skype/Set-CsPresenceManagementState.md index b1a7671e1e..863e995fa9 100644 --- a/skype/skype-ps/skype/Set-CsPresenceManagementState.md +++ b/skype/skype-ps/skype/Set-CsPresenceManagementState.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspresencemanagementstate +online version: https://learn.microsoft.com/powershell/module/skype/set-cspresencemanagementstate applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPresenceManagementState schema: 2.0.0 @@ -261,4 +261,3 @@ None. ## RELATED LINKS [Get-CsPresenceManagementState](Get-CsPresenceManagementState.md) - diff --git a/skype/skype-ps/skype/Set-CsPresencePolicy.md b/skype/skype-ps/skype/Set-CsPresencePolicy.md index 3ddc2bcca6..b700f28738 100644 --- a/skype/skype-ps/skype/Set-CsPresencePolicy.md +++ b/skype/skype-ps/skype/Set-CsPresencePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspresencepolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-cspresencepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPresencePolicy schema: 2.0.0 @@ -290,4 +290,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [New-CsPresencePolicy](New-CsPresencePolicy.md) [Remove-CsPresencePolicy](Remove-CsPresencePolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsPresenceProvider.md b/skype/skype-ps/skype/Set-CsPresenceProvider.md index 6af5f68403..253ee70774 100644 --- a/skype/skype-ps/skype/Set-CsPresenceProvider.md +++ b/skype/skype-ps/skype/Set-CsPresenceProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspresenceprovider +online version: https://learn.microsoft.com/powershell/module/skype/set-cspresenceprovider applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPresenceProvider schema: 2.0.0 @@ -170,4 +170,3 @@ Instead, the `Set-CsPresenceProvider` cmdlet modifies existing instances of the [New-CsPresenceProvider](New-CsPresenceProvider.md) [Remove-CsPresenceProvider](Remove-CsPresenceProvider.md) - diff --git a/skype/skype-ps/skype/Set-CsPrivacyConfiguration.md b/skype/skype-ps/skype/Set-CsPrivacyConfiguration.md index 4094af9e7a..2cca0f6368 100644 --- a/skype/skype-ps/skype/Set-CsPrivacyConfiguration.md +++ b/skype/skype-ps/skype/Set-CsPrivacyConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csprivacyconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csprivacyconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPrivacyConfiguration schema: 2.0.0 manager: bulenteg @@ -17,12 +17,11 @@ Modifies an existing set of privacy configuration settings. Privacy configuration settings help determine how much information users make available to other users. This cmdlet was introduced in Lync Server 2010. - ## SYNTAX ### Identity (Default) ``` -Set-CsPrivacyConfiguration [-Tenant <Guid>] [-EnablePrivacyMode <Boolean>] +Set-CsPrivacyConfiguration [-EnablePrivacyMode <Boolean>] [-AutoInitiateContacts <Boolean>] [-PublishLocationDataDefault <Boolean>] [-DisplayPublishedPhotoDefault <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] @@ -30,7 +29,7 @@ Set-CsPrivacyConfiguration [-Tenant <Guid>] [-EnablePrivacyMode <Boolean>] ### Instance ``` -Set-CsPrivacyConfiguration [-Tenant <Guid>] [-EnablePrivacyMode <Boolean>] +Set-CsPrivacyConfiguration [-EnablePrivacyMode <Boolean>] [-AutoInitiateContacts <Boolean>] [-PublishLocationDataDefault <Boolean>] [-DisplayPublishedPhotoDefault <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] @@ -179,6 +178,7 @@ In advanced privacy mode, only people on your Contacts list will be allowed to v If False, your presence information will be available to anyone in your organization. The default value is False. +For information about privacy mode in Microsoft Teams, see [User presence in Teams](/microsoftteams/presence-admins). ```yaml Type: Boolean @@ -229,34 +229,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -Tenant -Globally unique identifier (GUID) of the Skype for Business Online tenant account for the privacy configuration settings being modified. -For example: - -`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` - -You can return the tenant ID for each of your tenants by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -WhatIf Describes what would happen if you executed the command without actually executing the command. @@ -315,4 +287,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. [New-CsPrivacyConfiguration](New-CsPrivacyConfiguration.md) [Remove-CsPrivacyConfiguration](Remove-CsPrivacyConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsProxyConfiguration.md b/skype/skype-ps/skype/Set-CsProxyConfiguration.md index daa1e485d5..9d347a53bc 100644 --- a/skype/skype-ps/skype/Set-CsProxyConfiguration.md +++ b/skype/skype-ps/skype/Set-CsProxyConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csproxyconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csproxyconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsProxyConfiguration schema: 2.0.0 @@ -620,4 +620,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsProxyConfiguration](New-CsProxyConfiguration.md) [Remove-CsProxyConfiguration](Remove-CsProxyConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsPstnGateway.md b/skype/skype-ps/skype/Set-CsPstnGateway.md index 0234c94697..652c120b20 100644 --- a/skype/skype-ps/skype/Set-CsPstnGateway.md +++ b/skype/skype-ps/skype/Set-CsPstnGateway.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspstngateway +online version: https://learn.microsoft.com/powershell/module/skype/set-cspstngateway applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPstnGateway schema: 2.0.0 @@ -285,4 +285,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsPstnUsage.md b/skype/skype-ps/skype/Set-CsPstnUsage.md index b9f32dd13c..d588c47094 100644 --- a/skype/skype-ps/skype/Set-CsPstnUsage.md +++ b/skype/skype-ps/skype/Set-CsPstnUsage.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspstnusage +online version: https://learn.microsoft.com/powershell/module/skype/set-cspstnusage applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPstnUsage schema: 2.0.0 @@ -198,4 +198,3 @@ Instead, it configures instances of the Microsoft.Rtc.Management.WritableConfig. ## RELATED LINKS [Get-CsPstnUsage](Get-CsPstnUsage.md) - diff --git a/skype/skype-ps/skype/Set-CsPublicProvider.md b/skype/skype-ps/skype/Set-CsPublicProvider.md index a9c47472ff..4895b36792 100644 --- a/skype/skype-ps/skype/Set-CsPublicProvider.md +++ b/skype/skype-ps/skype/Set-CsPublicProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspublicprovider +online version: https://learn.microsoft.com/powershell/module/skype/set-cspublicprovider applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPublicProvider schema: 2.0.0 @@ -244,4 +244,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsPublicProvider](New-CsPublicProvider.md) [Remove-CsPublicProvider](Remove-CsPublicProvider.md) - diff --git a/skype/skype-ps/skype/Set-CsPushNotificationConfiguration.md b/skype/skype-ps/skype/Set-CsPushNotificationConfiguration.md index 14ff6b60c9..7a86381463 100644 --- a/skype/skype-ps/skype/Set-CsPushNotificationConfiguration.md +++ b/skype/skype-ps/skype/Set-CsPushNotificationConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration -applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-cspushnotificationconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsPushNotificationConfiguration schema: 2.0.0 manager: bulenteg @@ -266,4 +266,3 @@ Instead, the `Set-CsPushNotificationConfiguration` cmdlet modifies existing inst ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsQoEConfiguration.md b/skype/skype-ps/skype/Set-CsQoEConfiguration.md index db861c69b1..257965025e 100644 --- a/skype/skype-ps/skype/Set-CsQoEConfiguration.md +++ b/skype/skype-ps/skype/Set-CsQoEConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csqoeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csqoeconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsQoEConfiguration schema: 2.0.0 @@ -312,4 +312,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Remove-CsQoEConfiguration](Remove-CsQoEConfiguration.md) [Get-CsQoEConfiguration](Get-CsQoEConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsRegistrar.md b/skype/skype-ps/skype/Set-CsRegistrar.md index d371114dd1..b304b0a075 100644 --- a/skype/skype-ps/skype/Set-CsRegistrar.md +++ b/skype/skype-ps/skype/Set-CsRegistrar.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csregistrar +online version: https://learn.microsoft.com/powershell/module/skype/set-csregistrar applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRegistrar schema: 2.0.0 @@ -639,4 +639,3 @@ Instead, the command modifies existing instances of the Microsoft.Rtc.Management ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsRegistrarConfiguration.md b/skype/skype-ps/skype/Set-CsRegistrarConfiguration.md index b8839bcf7c..42491be2c9 100644 --- a/skype/skype-ps/skype/Set-CsRegistrarConfiguration.md +++ b/skype/skype-ps/skype/Set-CsRegistrarConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csregistrarconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csregistrarconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRegistrarConfiguration schema: 2.0.0 @@ -416,4 +416,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsRegistrarConfiguration](New-CsRegistrarConfiguration.md) [Remove-CsRegistrarConfiguration](Remove-CsRegistrarConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsReportingConfiguration.md b/skype/skype-ps/skype/Set-CsReportingConfiguration.md index f3170e78d8..9e96050de2 100644 --- a/skype/skype-ps/skype/Set-CsReportingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsReportingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csreportingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csreportingconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsReportingConfiguration schema: 2.0.0 @@ -59,7 +59,7 @@ Set-CsReportingConfiguration -Identity "service:MonitoringDatabase:atl-sql-002.l ``` The command shown in Example 1 modifies the reporting URL for the reporting configuration settings with the Identity service:MonitoringDatabase:atl-sql-002.litwareinc.com. -In this example, the reporting URL is changed to "https://atl-sql-002.litwareinc.com/lync_reports". +In this example, the reporting URL is changed to `https://atl-sql-002.litwareinc.com/lync_reports`. ## PARAMETERS @@ -187,4 +187,3 @@ Instead, the `Set-CsReportingConfiguration` cmdlet modifies existing instances o [New-CsReportingConfiguration](New-CsReportingConfiguration.md) [Remove-CsReportingConfiguration](Remove-CsReportingConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsRgsAgentGroup.md b/skype/skype-ps/skype/Set-CsRgsAgentGroup.md index 9165465dff..287057404c 100644 --- a/skype/skype-ps/skype/Set-CsRgsAgentGroup.md +++ b/skype/skype-ps/skype/Set-CsRgsAgentGroup.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csrgsagentgroup +online version: https://learn.microsoft.com/powershell/module/skype/set-csrgsagentgroup applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRgsAgentGroup schema: 2.0.0 @@ -207,4 +207,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Rgs.Managem [New-CsRgsAgentGroup](New-CsRgsAgentGroup.md) [Remove-CsRgsAgentGroup](Remove-CsRgsAgentGroup.md) - diff --git a/skype/skype-ps/skype/Set-CsRgsConfiguration.md b/skype/skype-ps/skype/Set-CsRgsConfiguration.md index a2d1882a8e..6114842831 100644 --- a/skype/skype-ps/skype/Set-CsRgsConfiguration.md +++ b/skype/skype-ps/skype/Set-CsRgsConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csrgsconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csrgsconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRgsConfiguration schema: 2.0.0 @@ -66,7 +66,7 @@ In turn, those computers are piped to the `ForEach-Object` cmdlet. ### -------------------------- Example 3 ------------------------ ``` -$x = Import-CsRgsAudioFile -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -FileName "WhileYouWait.wav" -Content (Get-Content C:\Media\WhileYouWait.wav -Encoding byte -ReadCount 0) +$x = Import-CsRgsAudioFile -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -FileName "WhileYouWait.wav" -Content ([System.IO.File]::ReadAllBytes('C:\Media\WhileYouWait.wav')) Set-CsRgsConfiguration -Identity "service:ApplicationServer:atl-cs-001.litwareinc.com" -DefaultMusicOnHoldFile $x ``` @@ -76,13 +76,11 @@ To perform this task, the first command uses `Import-CsRgsAudioFile` to import t In addition to the Identity parameter (which specifies the service location), the FileName parameter is used to specify the file name of the file being imported. Equally important, the Content parameter is used to import the audio file. -File importing is carried out by calling the `Get-Content` cmdlet followed by the path to the file being imported. -`Get-Content` also requires you to set the encoding type to byte and the ReadCount to 0. -(Setting the ReadCount to 0 ensures that the entire file is read in a single operation). The imported file is then stored in a variable named $x. +File importing is carried out by using the `[System.IO.File]::ReadAllBytes` command with the path to the file being imported. +The imported file is then stored in a variable named $x. After the file has been imported, `Set-CsRgsConfiguration` is called in order to set the DefaultMusicOnHoldFile property to the audio file stored in $x. - ## PARAMETERS ### -Identity @@ -251,4 +249,3 @@ Instead, the cmdlet configures existing instances of the Microsoft.Rtc.Rgs.Manag [Get-CsRgsConfiguration](Get-CsRgsConfiguration.md) [Move-CsRgsConfiguration](Move-CsRgsConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsRgsHolidaySet.md b/skype/skype-ps/skype/Set-CsRgsHolidaySet.md index 59c317889e..479d34c95d 100644 --- a/skype/skype-ps/skype/Set-CsRgsHolidaySet.md +++ b/skype/skype-ps/skype/Set-CsRgsHolidaySet.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csrgsholidayset +online version: https://learn.microsoft.com/powershell/module/skype/set-csrgsholidayset applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRgsHolidaySet schema: 2.0.0 @@ -209,4 +209,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Rgs.Managem [New-CsRgsHolidaySet](New-CsRgsHolidaySet.md) [Remove-CsRgsHolidaySet](Remove-CsRgsHolidaySet.md) - diff --git a/skype/skype-ps/skype/Set-CsRgsHoursOfBusiness.md b/skype/skype-ps/skype/Set-CsRgsHoursOfBusiness.md index 3867e2ed5d..2357b448fd 100644 --- a/skype/skype-ps/skype/Set-CsRgsHoursOfBusiness.md +++ b/skype/skype-ps/skype/Set-CsRgsHoursOfBusiness.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csrgshoursofbusiness +online version: https://learn.microsoft.com/powershell/module/skype/set-csrgshoursofbusiness applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRgsHoursOfBusiness schema: 2.0.0 @@ -202,4 +202,3 @@ Modifies existing instances of the Microsoft.Rtc.Rgs.Management.WriteableSetting [New-CsRgsTimeRange](New-CsRgsTimeRange.md) [Remove-CsRgsHoursOfBusiness](Remove-CsRgsHoursOfBusiness.md) - diff --git a/skype/skype-ps/skype/Set-CsRgsQueue.md b/skype/skype-ps/skype/Set-CsRgsQueue.md index 009c7935ec..4fbf3f12e4 100644 --- a/skype/skype-ps/skype/Set-CsRgsQueue.md +++ b/skype/skype-ps/skype/Set-CsRgsQueue.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csrgsqueue +online version: https://learn.microsoft.com/powershell/module/skype/set-csrgsqueue applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRgsQueue schema: 2.0.0 @@ -184,4 +184,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Rgs.Managem [New-CsRgsQueue](New-CsRgsQueue.md) [Remove-CsRgsQueue](Remove-CsRgsQueue.md) - diff --git a/skype/skype-ps/skype/Set-CsRgsWorkflow.md b/skype/skype-ps/skype/Set-CsRgsWorkflow.md index c3e77a6e0c..2a4c7f6b0e 100644 --- a/skype/skype-ps/skype/Set-CsRgsWorkflow.md +++ b/skype/skype-ps/skype/Set-CsRgsWorkflow.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Rgs.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csrgsworkflow +online version: https://learn.microsoft.com/powershell/module/skype/set-csrgsworkflow applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRgsWorkflow schema: 2.0.0 @@ -83,7 +83,9 @@ After the description has been changed, command 3 uses the `Set-CsRgsWorkflow` t ### -------------------------- Example 3 ------------------------ ``` -$musicFile = Get-Content -ReadCount 0 -Encoding Byte C:\MediaFiles\Hold.wav | Import-CsRgsAudioFile -Identity Service:ApplicationServer:atl-cs-001.litwareinc.com -FileName "HelpDeskHoldMusic.wav" +$musicFile = [System.IO.File]::ReadAllBytes('C:\MediaFiles\Hold.wav') | Import-CsRgsAudioFile -Identity Service:ApplicationServer:atl-cs-001.litwareinc.com -FileName "HelpDeskHoldMusic.wav" + + $y = Get-CsRgsWorkflow -Identity Service:ApplicationServer:atl-cs-001.litwareinc.com -Name "Help Desk" @@ -94,7 +96,7 @@ Set-CsRgsWorkflow -Instance $y The commands shown in Example 3 import a new Response Group audio file, then assign this audio file to an existing workflow. To do this, the first command in the example imports the new audio file. -This is done by calling the `Get-Content` cmdlet in order to read in the audio file (C:\MediaFiles\Hold.wav) byte-by-byte; to ensure that the audio file is read in correctly, you must include the ReadCount parameter (set to 0) and the Encoding parameter (set to Byte). +This is done by using the `[System.IO.File]::ReadAllBytes` command in order to read in the audio file (C:\MediaFiles\Hold.wav) byte-by-byte. After the audio file has been read in, the data is piped to `New-CsRgsAudioFile`, which creates a new file on ApplicationServer:atl-cs-001.litwareinc.com. An object reference to this file (which has the name HelpDeskHoldMusic.wav), is stored in a variable named $musicFile. @@ -204,4 +206,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Rgs.Managem [New-CsRgsWorkflow](New-CsRgsWorkflow.md) [Remove-CsRgsWorkflow](Remove-CsRgsWorkflow.md) - diff --git a/skype/skype-ps/skype/Set-CsRoutingConfiguration.md b/skype/skype-ps/skype/Set-CsRoutingConfiguration.md index ada20f85fe..5a2141d994 100644 --- a/skype/skype-ps/skype/Set-CsRoutingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsRoutingConfiguration schema: 2.0.0 @@ -244,4 +244,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Get-CsVoiceRoute](Get-CsVoiceRoute.md) [New-CsCallViaWorkPolicy](New-CsCallViaWorkPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsServerApplication.md b/skype/skype-ps/skype/Set-CsServerApplication.md index 6d208d29bb..96b56c6e53 100644 --- a/skype/skype-ps/skype/Set-CsServerApplication.md +++ b/skype/skype-ps/skype/Set-CsServerApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csserverapplication +online version: https://learn.microsoft.com/powershell/module/skype/set-csserverapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsServerApplication schema: 2.0.0 @@ -174,7 +174,7 @@ Accept wildcard characters: False ### -Uri Unique Uniform Resource Identifier (URI) for the application. -For example, the QoEAgent application has the URI http://www.microsoft.com/LCS/QoEAgent. +For example, the QoEAgent application has the URI `http://www.microsoft.com/LCS/QoEAgent`. ```yaml Type: String @@ -286,4 +286,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsServerApplication](New-CsServerApplication.md) [Remove-CsServerApplication](Remove-CsServerApplication.md) - diff --git a/skype/skype-ps/skype/Set-CsSimpleUrlConfiguration.md b/skype/skype-ps/skype/Set-CsSimpleUrlConfiguration.md index 6c3bdad99f..c34fbf16bf 100644 --- a/skype/skype-ps/skype/Set-CsSimpleUrlConfiguration.md +++ b/skype/skype-ps/skype/Set-CsSimpleUrlConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cssimpleurlconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cssimpleurlconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsSimpleUrlConfiguration schema: 2.0.0 @@ -35,12 +35,12 @@ Set-CsSimpleUrlConfiguration [-Instance <PSObject>] [-SimpleUrl <PSListModifier> ## DESCRIPTION In Microsoft Office Communications Server 2007 R2, meetings had URLs similar to this: -https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t +`https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t` However, such URLs are not especially intuitive, and not easy to convey to someone else. The simple URLs introduced in Microsoft Lync Server 2010 help overcome those problems by providing users with URLs that look more like this: -https://meet.litwareinc.com/kenmyer/071200 +`https://meet.litwareinc.com/kenmyer/071200` Simple URLs are an improvement over the URLs used in Office Communications Server. However, simple URLs are not automatically created for you; instead, you must configure the URLs yourself. @@ -94,10 +94,10 @@ Set-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Add=$simpleUr ``` Example 2 shows how a new URL can be added to an existing collection of simple URLs. -To begin with, the first command in the example uses the `New-CsSimpleUrlEntry` cmdlet to create a URL entry that points to https://meet.fabrikam.com; this URL entry is stored in a variable named $urlEntry. +To begin with, the first command in the example uses the `New-CsSimpleUrlEntry` cmdlet to create a URL entry that points to `https://meet.fabrikam.com`; this URL entry is stored in a variable named $urlEntry. In the second command, the `New-CsSimpleUrl` cmdlet is used to create an in-memory-only instance of a simple URL. -In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to https://meet.fabrikam.com and the SimpleUrl property is set to $urlEntry, with $urlEntry being the URL entry created in the first command. +In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to `https://meet.fabrikam.com` and the SimpleUrl property is set to $urlEntry, with $urlEntry being the URL entry created in the first command. After the URL has been created (and stored in the object reference $simpleUrl) the final command in the example adds the new URL to the simple URL collection for the Redmond site. This is done by using the `Set-CsSimpleUrlConfiguration` cmdlet, the SimpleUrl parameter and the parameter value @{Add=$simpleUrl}. @@ -115,10 +115,10 @@ Set-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Remove=$simpl The commands shown in Example 3 demonstrate how you can delete a single URL from a simple URL collection. Because the `Set-CsSimpleUrlConfiguration` cmdlet needs to work with URL objects, the example starts by creating a new object that contains the exact same property values as the URL to be deleted. -To do that, the first command uses the `New-CsSimpleUrlEntry` cmdlet to create a URL entry that points to https://meet.fabrikam.com; this URL entry is stored in a variable named $urlEntry. +To do that, the first command uses the `New-CsSimpleUrlEntry` cmdlet to create a URL entry that points to `https://meet.fabrikam.com`; this URL entry is stored in a variable named $urlEntry. After the URL entry has been created, the second command uses the `New-CsSimpleUrl` cmdlet to create an in-memory instance of a simple URL. -In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to https://meet.fabrikam.com; and the SimpleUrl property is set to $urlEntry, $urlEntry being the URL entry created in the first command. +In this example, the URL Component is set to Meet; the domain is set to fabrikam.com; the ActiveUrl is set to `https://meet.fabrikam.com`; and the SimpleUrl property is set to $urlEntry, $urlEntry being the URL entry created in the first command. This creates an in-memory URL ($simpleUrl) that has the same property values as the URL to be deleted. The final command in the example then deletes the URL from the simple URL collection for the Redmond site. @@ -287,4 +287,3 @@ None. [New-CsSimpleUrlEntry](New-CsSimpleUrlEntry.md) [Remove-CsSimpleUrlConfiguration](Remove-CsSimpleUrlConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsSipDomain.md b/skype/skype-ps/skype/Set-CsSipDomain.md index 1eace93f61..dc43ae35bf 100644 --- a/skype/skype-ps/skype/Set-CsSipDomain.md +++ b/skype/skype-ps/skype/Set-CsSipDomain.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cssipdomain +online version: https://learn.microsoft.com/powershell/module/skype/set-cssipdomain applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsSipDomain schema: 2.0.0 @@ -162,4 +162,3 @@ Instead, the cmdlet is used to modify existing instances of the Microsoft.Rtc.Ma [New-CsSipDomain](New-CsSipDomain.md) [Remove-CsSipDomain](Remove-CsSipDomain.md) - diff --git a/skype/skype-ps/skype/Set-CsSipResponseCodeTranslationRule.md b/skype/skype-ps/skype/Set-CsSipResponseCodeTranslationRule.md index 666fbdc620..8709e8d4e9 100644 --- a/skype/skype-ps/skype/Set-CsSipResponseCodeTranslationRule.md +++ b/skype/skype-ps/skype/Set-CsSipResponseCodeTranslationRule.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cssipresponsecodetranslationrule +online version: https://learn.microsoft.com/powershell/module/skype/set-cssipresponsecodetranslationrule applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsSipResponseCodeTranslationRule schema: 2.0.0 @@ -265,4 +265,3 @@ Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.WritableC [New-CsSipResponseCodeTranslationRule](New-CsSipResponseCodeTranslationRule.md) [Remove-CsSipResponseCodeTranslationRule](Remove-CsSipResponseCodeTranslationRule.md) - diff --git a/skype/skype-ps/skype/Set-CsSite.md b/skype/skype-ps/skype/Set-CsSite.md index 7fbd7449fc..b5779296c3 100644 --- a/skype/skype-ps/skype/Set-CsSite.md +++ b/skype/skype-ps/skype/Set-CsSite.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cssite +online version: https://learn.microsoft.com/powershell/module/skype/set-cssite applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsSite schema: 2.0.0 @@ -251,4 +251,3 @@ Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.Deploy.In ## RELATED LINKS [Get-CsSite](Get-CsSite.md) - diff --git a/skype/skype-ps/skype/Set-CsSlaConfiguration.md b/skype/skype-ps/skype/Set-CsSlaConfiguration.md index 077ff7c2f4..17fb0a02a8 100644 --- a/skype/skype-ps/skype/Set-CsSlaConfiguration.md +++ b/skype/skype-ps/skype/Set-CsSlaConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csslaconfiguration -applicable: Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csslaconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsSlaConfiguration schema: 2.0.0 manager: rogupta @@ -127,7 +127,7 @@ Accept wildcard characters: False ``` ### -MissedCallForwardTarget -Specifies the sip address of a user account or a telephone number to forward the call when you select `Forward` in the `MissedCallOption` parameter. The target could be a user in your organization or a phone number following next sintax: +Specifies the sip address of a user account or a telephone number to forward the call when you select `Forward` in the `MissedCallOption` parameter. The target could be a user in your organization or a phone number following next syntax: * tel:\<PhoneNumber\> * sip:\<NameofDelegate@domain\> @@ -181,7 +181,7 @@ Accept wildcard characters: False ``` ### -Target -Specifies the sip address of a user account or a telephone number to forward the call when you select `Forward` in the `BusyOption` parameter. The target could be a user in your organization or a phone number following next sintax: +Specifies the sip address of a user account or a telephone number to forward the call when you select `Forward` in the `BusyOption` parameter. The target could be a user in your organization or a phone number following next syntax: * tel:\<PhoneNumber\> * sip:\<NameofDelegate@domain\> @@ -224,7 +224,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS -[Get-CsSlaConfiguration](https://docs.microsoft.com/powershell/module/skype/get-csslaconfiguration?view=skype-ps) - -[Remove-CsSlaConfiguration](https://docs.microsoft.com/powershell/module/skype/remove-csslaconfiguration?view=skype-ps) +[Get-CsSlaConfiguration](https://learn.microsoft.com/powershell/module/skype/get-csslaconfiguration?view=skype-ps) +[Remove-CsSlaConfiguration](https://learn.microsoft.com/powershell/module/skype/remove-csslaconfiguration?view=skype-ps) diff --git a/skype/skype-ps/skype/Set-CsStaticRoutingConfiguration.md b/skype/skype-ps/skype/Set-CsStaticRoutingConfiguration.md index bfcd075c59..e573931e83 100644 --- a/skype/skype-ps/skype/Set-CsStaticRoutingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsStaticRoutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csstaticroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csstaticroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsStaticRoutingConfiguration schema: 2.0.0 @@ -233,4 +233,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsStaticRoutingConfiguration](New-CsStaticRoutingConfiguration.md) [Remove-CsStaticRoutingConfiguration](Remove-CsStaticRoutingConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsStorageServiceConfiguration.md b/skype/skype-ps/skype/Set-CsStorageServiceConfiguration.md index 23945d870f..e8dde2d1fe 100644 --- a/skype/skype-ps/skype/Set-CsStorageServiceConfiguration.md +++ b/skype/skype-ps/skype/Set-CsStorageServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csstorageserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csstorageserviceconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsStorageServiceConfiguration schema: 2.0.0 @@ -234,4 +234,3 @@ The `Set-CsStorageServiceConfiguration` cmdlet does not return any data or objec [New-CsStorageServiceConfiguration](New-CsStorageServiceConfiguration.md) [Remove-CsStorageServiceConfiguration](Remove-CsStorageServiceConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsTeamsAppPermissionPolicy.md b/skype/skype-ps/skype/Set-CsTeamsAppPermissionPolicy.md deleted file mode 100644 index cf2fee8795..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsAppPermissionPolicy.md +++ /dev/null @@ -1,263 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsapppermissionpolicy -applicable: Skype for Business Online -title: Set-CsTeamsAppPermissionPolicy -schema: 2.0.0 -ms.reviewer: -manager: bulenteg -ms.author: tomkau -author: tomkau ---- - -# Set-CsTeamsAppPermissionPolicy - -## SYNOPSIS - -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [-DefaultCatalogApps <>] [-GlobalCatalogApps <>] - [-PrivateCatalogApps <>] [-Description <String>] [-DefaultCatalogAppsType <String>] - [-GlobalCatalogAppsType <String>] [-PrivateCatalogAppsType <String>] [[-Identity] <XdsIdentity>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [-DefaultCatalogApps <>] [-GlobalCatalogApps <>] - [-PrivateCatalogApps <>] [-Description <String>] [-DefaultCatalogAppsType <String>] - [-GlobalCatalogAppsType <String>] [-PrivateCatalogAppsType <String>] [-Instance <PSObject>] [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - -As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## EXAMPLES - -### Example 1 -Intentionally omitted. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultCatalogApps -Do not use. - -```yaml -Type: -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DefaultCatalogAppsType -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GlobalCatalogApps -Do not use. - -```yaml -Type: -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GlobalCatalogAppsType -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Do not use. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Do not use. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -PrivateCatalogApps -Do not use. - -```yaml -Type: -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PrivateCatalogAppsType -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Do not use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsAppSetupPolicy.md b/skype/skype-ps/skype/Set-CsTeamsAppSetupPolicy.md deleted file mode 100644 index 9aa599c269..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsAppSetupPolicy.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsappsetuppolicy -applicable: Skype for Business Online -title: Set-CsTeamsAppSetupPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsAppSetupPolicy - -## SYNOPSIS - -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsAppSetupPolicy [-Tenant <System.Guid>] [-PinnedAppBarApps <>] [-Description <String>] - [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsAppSetupPolicy [-Tenant <System.Guid>] [-PinnedAppBarApps <>] [-Description <String>] - [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** - -## EXAMPLES - -### Example 1 - -Intentionally not provided. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Do not use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Do not use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Do not use. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Do not use. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -PinnedAppBarApps -Do not use. - -```yaml -Type: -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Do not use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsCallParkPolicy.md b/skype/skype-ps/skype/Set-CsTeamsCallParkPolicy.md deleted file mode 100644 index be5c409f94..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsCallParkPolicy.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamscallparkpolicy -applicable: Skype for Business Online -title: Set-CsTeamsCallParkPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsCallParkPolicy - -## SYNOPSIS - -The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone. The Set-CsTeamsCallParkPolicy cmdlet lets you update a policy that has already been created for your organization. - -NOTE: The call park feature currently available in desktop, mobile, and web clients. Supported with TeamsOnly mode. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsCallParkPolicy [-Tenant <System.Guid>] [-AllowCallPark <Boolean>] [[-Identity] <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsCallParkPolicy [-Tenant <System.Guid>] [-AllowCallPark <Boolean>] [-Instance <PSObject>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different phone. The Set-CsTeamsCallParkPolicy cmdlet lets you update a policy that has already been created for your organization. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsTeamsCallParkPolicy -Identity SalesPolicy -AllowCallPark $true -``` - -Update the existing policy "SalesPolicy" to enable the call park feature. - -## PARAMETERS - -### -AllowCallPark -If set to true, customers will be able to leverage the call park feature to place calls on hold and then decide how the call should be handled - transferred to another department, retrieved using the same phone, or retrieved using a different phone. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppress all non-fatal errors - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The unique identifier of the policy being updated. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -This parameter is used when piping a specific policy retrieved from Get-CsTeamsCallParkPolicy that you then want to update. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md b/skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md deleted file mode 100644 index 6faacbc357..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md +++ /dev/null @@ -1,308 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamscallingpolicy -applicable: Skype for Business Online -title: Set-CsTeamsCallingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsCallingPolicy - -## SYNOPSIS -Use this cmdlet to update values in existing Teams Calling Policies. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsCallingPolicy [-Tenant <System.Guid>] [-AllowCalling <Boolean>] [-AllowPrivateCalling <Boolean>] - [-AllowVoicemail <String>] [-AllowCallGroups <Boolean>] [-AllowDelegation <Boolean>] - [-AllowCallForwardingToUser <Boolean>] [-AllowCallForwardingToPhone <Boolean>] - [-PreventTollBypass <Boolean>] [-BusyOnBusyEnabledType <String>] [-MusicOnHoldEnabledType <Enum>][[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsCallingPolicy [-Tenant <System.Guid>] [-AllowCalling <Boolean>] [-AllowPrivateCalling <Boolean>] - [-AllowVoicemail <String>] [-AllowCallGroups <Boolean>] [-AllowDelegation <Boolean>] - [-AllowCallForwardingToUser <Boolean>] [-AllowCallForwardingToPhone <Boolean>] - [-PreventTollBypass <Boolean>] [-BusyOnBusyEnabledType <String>] [-MusicOnHoldEnabledType <Enum>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The Teams Calling Policies designate which users are able to use calling functionality within teams and determine the interopability state with Skype for Business. -This cmdlet allows admins to set values in a given calling policy. - -## EXAMPLES - -### Example 1 -``` -PS C:\> Set-CsTeamsCallingPolicy -Identity Global -AllowPrivateCalling $true -``` - -Sets the value of the parameter AllowPrivateCalling, which controls whether or not users can leverage calling functionality in Microsoft Teams, in the global (default) tenant CallingPolicy. - -## PARAMETERS - -### -AllowCalling -Controls interop calling capabilities. -Turning this on will allow Skype for Business users to have one-on-one calls with Teams users and vice-versa. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPrivateCalling -Controls all calling capabilities in Teams. -Turning this off will turn off all calling functionality in Teams. -If you use Skype for Business for calling, this policy will not affect calling functionality in Skype for Business. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Name of the policy being modified. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Use this to pipe a specific calling policy to be set. You can only modify the global policy, so can only pass the global instance of the Calling Policy. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCallForwardingToPhone -Enables call forwarding or simultaneous ringing of inbound calls to any phone number. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCallForwardingToUser -Enables call forwarding or simultaneous ringing of inbound calls to other users in your tenant. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCallGroups -Enables inbound calls to be routed to call groups. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowDelegation -Enables inbound calls to be routed to delegates; allows delegates to make outbound calls on behalf of the users for whom they have delegated permissions. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowVoicemail -Enables inbound calls to be routed to voice mail. Valid options are: AlwaysEnabled, AlwaysDisabled, UserOverride. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreventTollBypass -Setting this parameter to True will send calls through PSTN and incur charges rather than going through the network and bypassing the tolls. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BusyOnBusyEnabledType -Setting this parameter lets you configure how incoming calls are handled when a user is already in a call or conference or has a call placed on hold. New or incoming calls will be rejected with a busy signal. Valid options are: Enabled, Disabled. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### -MusicOnHoldEnabledType -Settings this parameter allows you to turn on or turn off music on hold when a PSTN caller is placed on hold. It is turned on by default. Valid options are: Enabled, Disabled, UserOverride. For now setting the value to UserOverride is the same as Enabled. This setting does not apply to call park and SLA boss delegate features. - -```yaml -Type: Enum -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: Enabled -Accept pipeline input: False -Accept wildcard characters: False -``` -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsChannelsPolicy.md b/skype/skype-ps/skype/Set-CsTeamsChannelsPolicy.md deleted file mode 100644 index a5e53db82c..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsChannelsPolicy.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamschannelspolicy -applicable: Skype for Business Online -title: Set-CsTeamsChannelsPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsChannelsPolicy - -## SYNOPSIS - -The CsTeamsChannelsPolicy allows you to manage features related to the Teams and Channels experience within the Teams application. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsChannelsPolicy [-Tenant <Guid>] [-AllowOrgWideTeamCreation <Boolean>] - [-AllowPrivateTeamDiscovery <Boolean>] [-AllowPrivateChannelCreation <Boolean>] [[-Identity] <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsChannelsPolicy [-Tenant <Guid>] [-AllowOrgWideTeamCreation <Boolean>] - [-AllowPrivateTeamDiscovery <Boolean>] [-AllowPrivateChannelCreation <Boolean>] [-Instance <PSObject>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. - -This cmdlet allows you to update existing policies of this type. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsTeamsChannelsPolicy -Identity StudentPolicy -AllowPrivateTeamDiscovery $true -``` - -This example shows updating an existing policy with name "StudentPolicy" and enabling Private Team Discovery. - -## PARAMETERS - -### -AllowPrivateTeamDiscovery -Determines whether a user is allowed to discover private teams in suggestions and search results. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Bypass all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Use this parameter to specify the name of the policy being updated. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Use this parameter to pass the policy object output of Get-CsTeamsChannelsPolicy to update that policy. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOrgWideTeamCreation -Determines whether a user is allowed to create an org-wide team. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPrivateChannelCreation -Determines whether a user is allowed to create a private channel. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - -[New-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamschannelspolicy) - -[Remove-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamschannelspolicy) - -[Grant-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamschannelspolicy) - -[Get-CsTeamsChannelsPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamschannelspolicy) diff --git a/skype/skype-ps/skype/Set-CsTeamsEmergencyCallRoutingPolicy.md b/skype/skype-ps/skype/Set-CsTeamsEmergencyCallRoutingPolicy.md deleted file mode 100644 index a1442833a4..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsEmergencyCallRoutingPolicy.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsemergencycallroutingpolicy -applicable: Skype for Business Online -title: Set-CsTeamsEmergencyCallRoutingPolicy -author: danny-levin -ms.author: dannyle -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Set-CsTeamsEmergencyCallRoutingPolicy - -## SYNOPSIS - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsEmergencyCallRoutingPolicy [-Tenant <System.Guid>] [-EmergencyNumbers <>] - [-AllowEnhancedEmergencyServices <Boolean>] [-Description <String>] [[-Identity] <XdsIdentity>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsEmergencyCallRoutingPolicy [-Tenant <System.Guid>] [-EmergencyNumbers <>] - [-AllowEnhancedEmergencyServices <Boolean>] [-Description <String>] [-Instance <PSObject>] [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet modifies an existing Teams Emergency Call Routing Policy. Teams Emergency Call Routing policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Set-CsTeamsEmergencyCallRoutingPolicy -Identity "testecrp" -Tenant $tenant -AllowEnhancedEmergencyServices:$false -Description "test" -``` - - This example modifies an existing Teams Emergency Call Routing Policy. - -## PARAMETERS - -### -AllowEnhancedEmergencyServices - Flag to enable Enhanced Emergency Services - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - Provide a description of the Teams Emergency Call Routing policy to identify purpose of setting it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EmergencyNumbers - One or more emergency number objects obtained from [New-CsTeamsEmergencyNumber](https://docs.microsoft.com/powershell/module/skype/new-csteamsemergencynumber?view=skype-ps) cmdlet - -```yaml -Type: -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - The Identity parameter is a unique identifier that designates the name of the policy. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance - The Instance parameter allows you to pass a reference to an object to the cmdlet, rather than set individual parameter values. You can retrieve this object reference by calling the Get-CsTeamsEmergencyCallRoutingPolicy cmdlet. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Tenant - Specify the tenant id - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsEmergencyCallingPolicy.md b/skype/skype-ps/skype/Set-CsTeamsEmergencyCallingPolicy.md deleted file mode 100644 index 81e6b99aa3..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsEmergencyCallingPolicy.md +++ /dev/null @@ -1,229 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsemergencycallingpolicy -applicable: Skype for Business Online -title: Set-CsTeamsEmergencyCallingPolicy -author: danny-levin -ms.author: dannyle -manager: roykuntz -ms.reviewer: chenc, pthota -schema: 2.0.0 ---- - -# Set-CsTeamsEmergencyCallingPolicy - -## SYNOPSIS - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsEmergencyCallingPolicy [-Tenant <System.Guid>] [-NotificationGroup <String>] - [-NotificationDialOutNumber <String>] [-ExternalLocationLookupMode <ExternalLocationLookupMode>] - [-NotificationMode <Microsoft.Rtc.Management.WritableConfig.Policy.Teams.NotificationMode>] - [-Description <String>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsEmergencyCallingPolicy [-Tenant <System.Guid>] [-NotificationGroup <String>] - [-NotificationDialOutNumber <String>] [-ExternalLocationLookupMode <ExternalLocationLookupMode>] - [-NotificationMode <Microsoft.Rtc.Management.WritableConfig.Policy.Teams.NotificationMode>] - [-Description <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - This cmdlet modifies an existing Teams Emergency Calling policy. Emergency calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. - -## EXAMPLES - -### Example 1 -```powershell -PS C:> Set-CsTeamsEmergencyCallingPolicy -Identity "testECP" -NotificationGroup "123@gh.com;567@test.com" -``` - - This example modifies a existing cmdlet with identity testECP. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - Provide a description of the Teams Emergency Calling policy to identify purpose of setting it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalLocationLookupMode - Enable ExternalLocationLookupMode. This parameter is currently not supported. - -```yaml -Type: ExternalLocationLookupMode -Parameter Sets: (All) -Aliases: -Accepted values: Disabled, Enabled - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - The Identity parameter is a unique identifier that designates the name of the policy - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance - The Instance parameter allows you to pass a reference to an object to the cmdlet, rather than set individual parameter values. You can retrieve this object reference by calling the Get-CsTeamsEmergencyCallingPolicy cmdlet. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NotificationDialOutNumber - This parameter represents PSTN number which can be dialed out if NotificationMode is set to either of the two Conference values - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationGroup - NotificationGroup is a email list of users and groups to be notified of an emergency call - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NotificationMode - The type of conference experience for security desk notification - -```yaml -Type: Microsoft.Rtc.Management.WritableConfig.Policy.Teams.NotificationMode -Parameter Sets: (All) -Aliases: -Accepted values: NotificationOnly, ConferenceMuted, ConferenceUnMuted - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - Specify the tenant id - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsGuestMeetingConfiguration.md b/skype/skype-ps/skype/Set-CsTeamsGuestMeetingConfiguration.md deleted file mode 100644 index e50437b60b..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsGuestMeetingConfiguration.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsguestmeetingconfiguration -applicable: Skype for Business Online -title: Set-CsTeamsGuestMeetingConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsGuestMeetingConfiguration - -## SYNOPSIS - -Designates what meeting features guests using Microsoft Teams will have available. Use this cmdlet to set the configuration. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsGuestMeetingConfiguration [-Tenant <Guid>] [-AllowIPVideo <Boolean>] - [-ScreenSharingMode <String>] [-AllowMeetNow <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsGuestMeetingConfiguration [-Tenant <Guid>] [-AllowIPVideo <Boolean>] - [-ScreenSharingMode <String>] [-AllowMeetNow <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION - -The TeamsGuestMeetingConfiguration designates which meeting features guests leveraging Microsoft Teams will have available. This configuration will apply to all guests utilizing Microsoft Teams. Use the Set-CsTeamsGuestMeetingConfiguration cmdlet to designate what values are set for your organization. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsTeamsGuestMeetingConfiguration -Identity Global -AllowMeetNow $false -AllowIPVideo $false -``` - -Disables Guests' usage of MeetNow and Video calling in the organization; all other values of the configuration are left as is. - -## PARAMETERS - -### -AllowIPVideo -Determines whether video is enabled in a user's meetings or calls. Set this to TRUE to allow guests to share their video. Set this to FALSE to prohibit guests from sharing their video - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMeetNow -Determines whether guests can start ad-hoc meetings. Set this to TRUE to allow guests to start ad-hoc meetings. Set this to FALSE to prohibit guests from starting ad-hoc meetings. - - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses all non fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The only input allowed is "Global" - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Pipe the existing configuration from a Get- call. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScreenSharingMode -Determines the mode in which guests can share a screen in calls or meetings. Set this to SingleApplication to allow the user to share an application at a given point in time. Set this to EntireScreen to allow the user to share anything on their screens. Set this to Disabled to prohibit the user from sharing their screens - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Internal Microsoft use - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsGuestMessagingConfiguration.md b/skype/skype-ps/skype/Set-CsTeamsGuestMessagingConfiguration.md deleted file mode 100644 index cfd9da473e..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsGuestMessagingConfiguration.md +++ /dev/null @@ -1,254 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsguestmessagingconfiguration -applicable: Skype for Business Online -title: Set-CsTeamsGuestMessagingConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsGuestMessagingConfiguration - -## SYNOPSIS -TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [-AllowUserEditMessage <Boolean>] - [-AllowUserDeleteMessage <Boolean>] [-AllowUserChat <Boolean>] [-AllowGiphy <Boolean>] - [-GiphyRatingType <String>] [-AllowMemes <Boolean>] [-AllowStickers <Boolean>] [[-Identity] <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [-AllowUserEditMessage <Boolean>] - [-AllowUserDeleteMessage <Boolean>] [-AllowUserChat <Boolean>] [-AllowGiphy <Boolean>] - [-GiphyRatingType <String>] [-AllowMemes <Boolean>] [-AllowStickers <Boolean>] [-Instance <PSObject>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. This cmdlet lets you update the guest messaging options you'd like to enable in your organization. - -## EXAMPLES - -### Example 1 -``` -Set-CsTeamsGuestMessagingConfiguration -AllowMemes $False -``` - -The command shown in Example 1 disables memes usage by guests within Teams. - -## PARAMETERS - -### -AllowGiphy -Determines if Giphy images are available. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMemes -Determines if memes are available for use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowStickers -Determines if stickers are available for use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserChat -Determines if a user is allowed to chat. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserDeleteMessage -Determines if a user is allowed to delete their own messages. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserEditMessage -Determines if a user is allowed to edit their own messages. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GiphyRatingType -Determines Giphy content restrictions. Default value is "Moderate", other options are "NoRestriction" and "Strict" - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsTeamsMeetingPolicy.md b/skype/skype-ps/skype/Set-CsTeamsMeetingPolicy.md deleted file mode 100644 index 2478113e96..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsMeetingPolicy.md +++ /dev/null @@ -1,535 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsmeetingpolicy -applicable: Skype for Business Online -title: Set-CsTeamsMeetingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsMeetingPolicy - -## SYNOPSIS -The `CsTeamsMeetingPolicy` cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsMeetingPolicy [-Tenant <Guid>] [-Description <String>] - [-AllowChannelMeetingScheduling <Boolean>] [-AllowMeetNow <Boolean>] [-AllowPrivateMeetNow <Boolean>] - [-MeetingChatEnabledType <String>] [-LiveCaptionsEnabledType <String>] [-AllowIPVideo <Boolean>] - [-AllowAnonymousUsersToDialOut <Boolean>] [-AllowAnonymousUsersToStartMeeting <Boolean>] - [-AllowPrivateMeetingScheduling <Boolean>] [-AutoAdmittedUsers <String>] [-AllowCloudRecording <Boolean>] - [-AllowOutlookAddIn <Boolean>] [-AllowPowerPointSharing <Boolean>] - [-AllowParticipantGiveRequestControl <Boolean>] [-AllowExternalParticipantGiveRequestControl <Boolean>] - [-AllowSharedNotes <Boolean>] [-AllowWhiteboard <Boolean>] [-AllowTranscription <Boolean>] - [-MediaBitRateKb <UInt32>] [-ScreenSharingMode <String>] [-AllowPSTNUsersToBypassLobby <Boolean>] - [-PreferredMeetingProviderForIslandsMode <string>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsMeetingPolicy [-Tenant <Guid>] [-Description <String>] - [-AllowChannelMeetingScheduling <Boolean>] [-AllowMeetNow <Boolean>] [-AllowPrivateMeetNow <Boolean>] - [-MeetingChatEnabledType <String>] [-LiveCaptionsEnabledType <String>] [-AllowIPVideo <Boolean>] - [-AllowAnonymousUsersToDialOut <Boolean>] [-AllowAnonymousUsersToStartMeeting <Boolean>] - [-AllowPrivateMeetingScheduling <Boolean>] [-AutoAdmittedUsers <String>] [-AllowCloudRecording <Boolean>] - [-AllowOutlookAddIn <Boolean>] [-AllowPowerPointSharing <Boolean>] - [-AllowParticipantGiveRequestControl <Boolean>] [-AllowExternalParticipantGiveRequestControl <Boolean>] - [-AllowSharedNotes <Boolean>] [-AllowWhiteboard <Boolean>] [-AllowTranscription <Boolean>] - [-MediaBitRateKb <UInt32>] [-ScreenSharingMode <String>] [-AllowPSTNUsersToBypassLobby <Boolean>] - [-PreferredMeetingProviderForIslandsMode <string>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -The `CsTeamsMeetingPolicy` cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users. - -The Set-CsTeamsMeetingPolicy cmdlet allows administrators to update existing meeting policies that can be assigned to particular users to control Teams features related to meetings. - -## EXAMPLES - -### -------------------------- EXAMPLE 1 -------------------------- -``` -Set-CsTeamsMeetingPolicy -Identity SalesMeetingPolicy -AllowTranscription $True -``` - -The command shown in Example 1 uses the Set-CsTeamsMeetingPolicy cmdlet to update an existing meeting policy with the Identity SalesMeetingPolicy. -This policy will use all the existing values except one: AllowTranscription; in this example, meetings for users with this policy can include real time or post meeting captions and transcriptions. - - -### -------------------------- EXAMPLE 2 -------------------------- -``` -Set-CsTeamsMeetingPolicy -Identity HrMeetingPolicy -AutoAdmittedUsers "Everyone" -AllowMeetNow $False -``` - -In Example 2, the Set-CsTeamsMeetingPolicy cmdlet is used to update a meeting policy with the Identity HrMeetingPolicy. -In this example two different property values are configured: AutoAdmittedUsers is set to Everyone and AllowMeetNow is set to False. -All other policy properties will use the existing values. - -## PARAMETERS - -### -AllowAnonymousUsersToStartMeeting -Determines whether anonymous users can initiate a meeting. Set this to TRUE to allow anonymous users to initiate a meeting. Set this to FALSE to prohibit them from initiating a meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowChannelMeetingScheduling -Determines whether a user can schedule channel meetings. Set this to TRUE to allow a user to schedule channel meetings. Set this to FALSE to prohibit the user from scheduling channel meetings. Note this only restricts from scheduling and not from joining a meeting scheduled by another user. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowCloudRecording -Determines whether cloud recording is allowed in a user's meetings. Set this to TRUE to allow the user to be able to record meetings. Set this to FALSE to prohibit the user from recording meetings. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowExternalParticipantGiveRequestControl -Determines whether external participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit an external user from giving or requesting control in a meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowIPVideo -Determines whether video is enabled in a user's meetings or calls. Set this to TRUE to allow the user to share their video. Set this to FALSE to prohibit the user from sharing their video. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMeetNow -Determines whether a user can start ad-hoc meetings. Set this to TRUE to allow a user to start ad-hoc meetings. Set this to FALSE to prohibit the user from starting ad-hoc meetings. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOutlookAddIn -Determines whether a user can schedule Teams Meetings in Outlook desktop client. Set this to TRUE to allow the user to be able to schedule Teams meetings in Outlook client. Set this to FALSE to prohibit a user from scheduling Teams meeting in Outlook client. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowParticipantGiveRequestControl -Determines whether participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit the user from giving, requesting control in a meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPowerPointSharing -Determines whether Powerpoint sharing is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPrivateMeetingScheduling -Determines whether a user can schedule private meetings. Set this to TRUE to allow a user to schedule private meetings. Set this to FALSE to prohibit the user from scheduling private meetings. Note this only restricts from scheduling and not from joining a meeting scheduled by another user. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowSharedNotes -Determines whether users are allowed to take shared notes. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowTranscription -Determines whether post-meeting captions and transcriptions are allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowWhiteboard -Determines whether whiteboard is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - - -### -AutoAdmittedUsers -Determines what types of participants will automatically be added to meetings organized by this user. Set this to EveryoneInCompany if you would like meetings to place every external user in the lobby but allow all users in the company to join the meeting immediately. Set this to Everyone if you'd like to admit anonymous users by default. Set this to EveryoneInSameAndFederatedCompany if you would like meetings to allow federated users to join like your company's users, but place all other external users in a lobby. This setting also applies to participants joining via a PSTN device (i.e. a traditional phone). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description - -Enables administrators to provide explanatory text about the meeting policy. -For example, the Description might indicate the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the name of the policy being created. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Specify the name of the policy being modified. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MediaBitRateKb -Determines the media bit rate for audio/video/app sharing transmissions in meetings. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ScreenSharingMode -Determines the mode in which a user can share a screen in calls or meetings. Set this to SingleApplication to allow the user to share an application at a given point in time. Set this to EntireScreen to allow the user to share anything on their screens. Set this to Disabled to prohibit the user from sharing their screens. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPSTNUsersToBypassLobby -Determines whether a PSTN user joining the meeting is allowed or not to bypass the lobby. If you set this parameter to **True**, PSTN users are allowed to bypass the lobby as long as an authenticated user is joined to the meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MeetingChatEnabledType -Specify if users will be able to chat in meetings. Possible values are: Disabled,Enabled. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPrivateMeetNow -This setting controls whether a user can start an ad hoc private meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowAnonymousUsersToDialOut -Determines whether anonymous users are allowed to dial out to a PSTN number. Set this to TRUE to allow anonymous users to dial out. Set this to FALSE to prohibit anonymous users from dialing out. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreferredMeetingProviderForIslandsMode -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: TeamsAndSfb -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LiveCaptionsEnabledType -Determines whether real-time captions are available for the user in Teams meetings. Set this to DisabledUserOverride to allow user to turn on live captions. Set this to Disabled to prohibit. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: DisabledUserOverride -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsTeamsMessagingPolicy.md b/skype/skype-ps/skype/Set-CsTeamsMessagingPolicy.md deleted file mode 100644 index b9022d79a9..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsMessagingPolicy.md +++ /dev/null @@ -1,437 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsmessagingpolicy -applicable: Skype for Business Online -title: Set-CsTeamsMessagingPolicy -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTeamsMessagingPolicy - -## SYNOPSIS -The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsMessagingPolicy [-Tenant <Guid>] [-Description <String>] [-AllowUrlPreviews <Boolean>] - [-AllowOwnerDeleteMessage <Boolean>] [-AllowUserEditMessage <Boolean>] [-AllowUserDeleteMessage <Boolean>] - [-AllowUserChat <Boolean>] [-AllowGiphy <Boolean>] [-GiphyRatingType <String>] [-AllowMemes <Boolean>] - [-AllowStickers <Boolean>] [-AllowUserTranslation <Boolean>] [-AllowImmersiveReader <Boolean>] - [-AllowRemoveUser <Boolean>] [-AllowPriorityMessages <Boolean>] [-ReadReceiptsEnabledType <String>] - [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>] [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>] - [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsMessagingPolicy [-Tenant <Guid>] [-Description <String>] [-AllowUrlPreviews <Boolean>] - [-AllowOwnerDeleteMessage <Boolean>] [-AllowUserEditMessage <Boolean>] [-AllowUserDeleteMessage <Boolean>] - [-AllowUserChat <Boolean>] [-AllowGiphy <Boolean>] [-GiphyRatingType <String>] [-AllowMemes <Boolean>] - [-AllowStickers <Boolean>] [-AllowUserTranslation <Boolean>] [-AllowImmersiveReader <Boolean>] - [-AllowRemoveUser <Boolean>] [-AllowPriorityMessages <Boolean>] [-ReadReceiptsEnabledType <String>] - [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>] [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>] - [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION - The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. This cmdlet updates a Teams messaging policy. Custom policies can then be assigned to users using the Grant-CsTeamsMessagingPolicy cmdlet. - - -## EXAMPLES - -### Example 1 - -```powershell -PS C:\> Set-CsTeamsMessagingPolicy -Identity StudentMessagingPolicy -AllowGiphy $false -AllowMemes $false -``` - -In this example two different property values are configured: AllowGiphy is set to false and AllowMemes is set to False. -All other policy properties will be left as previously assigned. - -### Example 2 - -```powershell -PS C:\> Get-CsTeamsMessagingPolicy -Identity StudentMessagingPolicy | Set-CsTeamsMessagingPolicy -AllowGiphy $false -AllowMemes $false -``` - -In this example two different property values are configured for all teams messaging policies in the organization: AllowGiphy is set to false and AllowMemes is set to False. -All other policy properties will be left as previously assigned. - - -## PARAMETERS - -### -AllowGiphy -Determines whether a user is allowed to access and post Giphys. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowImmersiveReader -Determines whether a user is allowed to use Immersive Reader for reading conversation messages. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowMemes -Determines whether a user is allowed to access and post memes. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowOwnerDeleteMessage -Determines whether owners are allowed to delete all the messages in their team. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPriorityMessages -Determines whether a user is allowed to send priorities messages. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowRemoveUser -Determines whether a user is allowed to remove a user from a conversation. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowStickers -Determines whether a user is allowed to access and post stickers. Set this to TRUE to allow. Set this FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserChat -Determines whether a user is allowed to chat. Set this to TRUE to allow a user to chat across private chat, group chat and in meetings. Set this to FALSE to prohibit all chat. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserDeleteMessage -Determines whether a user is allowed to delete their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserEditMessage -Determines whether a user is allowed to edit their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUserTranslation -Determines whether a user is allowed to translate messages to their client languages. Set this to TRUE to allow. Set this to FALSE to prohibit. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowUrlPreviews -Use this setting to turn automatic URL previewing on or off in messages. Set this to TRUE to turn on. Set this to FALSE to turn off. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AudioMessageEnabledType -Determines whether a user is allowed to send audio messages. Possible values are: ChatsAndChannels, ChatsOnly, Disabled. - -```yaml -Type: AudioMessageEnabledTypeEnum -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ChannelsInChatListEnabledType -Possible values are: DisabledUserOverride, EnabledUserOverride. - -```yaml -Type: ChannelsInChatListEnabledTypeEnum -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of your policy to identify purpose of creating it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -GiphyRatingType -Determines the Giphy content restrictions applicable to a user. Set this to STRICT, MODERATE or NORESTRICTION. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Identity for the teams messaging policy you're modifying. To modify the global policy, use this syntax: -Identity global. To modify a per-user policy, use syntax similar to this: -Identity TeamsMessagingPolicy. - -If you do not specify an Identity the Set-CsTeamsMessagingPolicy cmdlet will automatically modify the global policy. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ReadReceiptsEnabledType -Use this setting to specify whether read receipts are user controlled, enabled for everyone, or disabled. Set this to UserPreference, Everyone or None. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### System.Management.Automation.PSObject - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsTeamsTranslationRule.md b/skype/skype-ps/skype/Set-CsTeamsTranslationRule.md deleted file mode 100644 index 49987148b8..0000000000 --- a/skype/skype-ps/skype/Set-CsTeamsTranslationRule.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamstranslationrule -applicable: Skype for Business Online -title: Set-CsTeamsTranslationRule -schema: 2.0.0 -manager: nmurav -author: filippse -ms.author: filippse -ms.reviewer: ---- - -# Set-CsTeamsTranslationRule - -## SYNOPSIS -Cmdlet to modify an existing normalization rule. - -## SYNTAX - -``` -Set-CsTeamsTranslationRule [-Description <string>] [-Pattern <string>] [-WhatIf] [-Translation <string>] - [-Identity <string>] [-Tenant <string>] [-Confirm] [-Force] [-Instance <Object>] [-AsJob] -``` - -## DESCRIPTION -You can use this cmdlet to modify an existing number manipulation rule. The rule can be used, for example, in the settings of your SBC (Set-CSOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsTeamsTranslationRule -Identity StripE164SeattleAreaCode -Pattern ^+12065555(\d{3})$ -Translation $1 -``` - -This example modifies the rule that initially configured to strip +1206555 from any E.164 ten digits number. For example, +12065555555 translated to 5555 to a new pattern. Modified rule now only applies to three digit number (initially to four digits number) and adds one more number in prefix (+120655555 instead of +1206555) - - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -A friendly description of the normalization rule. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Identifier of the rule. This parameter is required and later used to assign the rule to Inbound or Outbound Trunk Normalization policy. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Pattern -A regular expression that caller or callee number must match in order for this rule to be applied. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose number manipulation rule is being edited. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Translation -The regular expression pattern that will be applied to the number to convert it. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsUpgradeConfiguration.md b/skype/skype-ps/skype/Set-CsTeamsUpgradeConfiguration.md index f3ce016ac1..c8556d260f 100644 --- a/skype/skype-ps/skype/Set-CsTeamsUpgradeConfiguration.md +++ b/skype/skype-ps/skype/Set-CsTeamsUpgradeConfiguration.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsupgradeconfiguration -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/skype/set-csteamsupgradeconfiguration +applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTeamsUpgradeConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTeamsUpgradeConfiguration @@ -180,4 +180,4 @@ These settings are only honored by newer versions of Skype for Business clients. [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) diff --git a/skype/skype-ps/skype/Set-CsTeamsUpgradePolicy.md b/skype/skype-ps/skype/Set-CsTeamsUpgradePolicy.md index 573730d368..86e0f3e376 100644 --- a/skype/skype-ps/skype/Set-CsTeamsUpgradePolicy.md +++ b/skype/skype-ps/skype/Set-CsTeamsUpgradePolicy.md @@ -1,8 +1,8 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml Module Name: SkypeForBusiness -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsupgradepolicy -applicable: Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csteamsupgradepolicy +applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTeamsUpgradePolicy schema: 2.0.0 manager: rogupta @@ -34,26 +34,26 @@ Set-CsTeamsUpgradePolicy [-Tenant <Guid>] [-Description <String>] [-NotifySfbUse ``` ## DESCRIPTION - -**This cmdlet is only relevant for Skype for Business Server 2019. It does not apply for Skype for Business Online.** +**NOTE**: This cmdlet is only relevant for Skype for Business Server 2019. It does not apply for Skype for Business Online. In on-premises deployments of Skype for Business Server, TeamsUpgradePolicy enables administrators to control whether users see a notification of a pending upgrade to Teams in their Skype for Business client. The Set-CsTeamsUpgradePolicy lets the administrator modify an existing instance of TeamsUpgradePolicy for users homed in Skype for Business on-premises. Notifications are enabled by the boolean parameter NotifySfBUsers. For users with Win32 versions of Skype for Business, if DownloadTeams=true in TeamsUpgradeConfiguration, users who are assigned an instance of TeamsUpgradePolicy with NotifySfBUsers=true will have Teams automatically downloaded in the background. Notes: -* Instances of TeamsUpgradePolicy created in on-premises will not apply to any users that are already homed online. -* Office 365 already provides built-in instances of TeamsUpgradePolicy, so there is no Set-CsTeamsUpgradePolicy cmdlet for the online environment by design. + +- Instances of TeamsUpgradePolicy created in on-premises will not apply to any users that are already homed online. +- Office 365 already provides built-in instances of TeamsUpgradePolicy, so there is no Set-CsTeamsUpgradePolicy cmdlet for the online environment by design. ## EXAMPLES ### Example 1 ```powershell -PS C:\> Set-CsTeamsUpgradePolicy -Identity Site:Redmond1 -NotifySfbUsers $false +Set-CsTeamsUpgradePolicy -Identity Site:Redmond1 -NotifySfbUsers $false ``` -This disables notifications for users in the Redmond1 site. +This disables notifications for users in the Redmond1 site. ## PARAMETERS @@ -138,7 +138,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) diff --git a/skype/skype-ps/skype/Set-CsTelemetryConfiguration.md b/skype/skype-ps/skype/Set-CsTelemetryConfiguration.md index 293d9624df..8a7a2ec48f 100644 --- a/skype/skype-ps/skype/Set-CsTelemetryConfiguration.md +++ b/skype/skype-ps/skype/Set-CsTelemetryConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstelemetryconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cstelemetryconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTelemetryConfiguration schema: 2.0.0 @@ -170,4 +170,3 @@ None ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsTenantBlockedCallingNumbers.md b/skype/skype-ps/skype/Set-CsTenantBlockedCallingNumbers.md deleted file mode 100644 index 46f8e0153a..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantBlockedCallingNumbers.md +++ /dev/null @@ -1,247 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -applicable: Skype for Business Online -title: Set-CsTenantBlockedCallingNumbers -schema: 2.0.0 -manager: roykuntz -author: junya -ms.author: junya ---- - -# Set-CsTenantBlockedCallingNumbers - -## SYNOPSIS -Use the Set-CsTenantBlockedCallingNumbers cmdlet to set tenant blocked calling numbers setting. - -## SYNTAX - -``` -Set-CsTenantBlockedCallingNumbers [-Force] [-Name <Object>] [-WhatIf] [-Confirm] [[-Identity] <Object>] - [-InboundExemptNumberPatterns <Object>] [-Tenant <Object>] [-InboundBlockedNumberPatterns <Object>] - [-Enabled <Object>] [-Instance <Object>] [-AsJob] -``` - -## DESCRIPTION -Skype for Business Online Calling Plans now supports blocking of inbound calls from the public switched telephone network (PSTN). This feature allows a tenant-global list of number patterns to be defined so that the caller ID of every incoming PSTN call to the tenant can be checked against the list for a match. If a match is made, an incoming call is rejected. - -The tenant blocked calling numbers includes a list of inbound blocked number patterns. Number patterns are managed through the CsInboundBlockedNumberPattern commands New, Get, Set, and Remove. You can manage a given pattern by using these cmdlets, including the ability to toggle the activation of a given pattern. - -The scope of tenant blocked calling numbers is global across the given tenant. This command-let can also turn on/off the blocked calling numbers setting in tenant level. - -To get the current tenant blocked calling numbers setting, use Get-CsTenantBlockedCallingNumbers - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsTenantBlockedCallingNumbers -Enabled $false -``` - -This example turns off the tenant blocked calling numbers setting. No inbound number will be blocked from this feature. - -### -------------------------- Example 2 -------------------------- -``` -Set-CsTenantBlockedCallingNumbers -Enabled $true -``` - -This example turns on the tenant blocked calling numbers setting. Inbound calls will be blocked based on the list of blocked number patterns. - -### -------------------------- Example 3 -------------------------- -``` -Set-CsTenantBlockedCallingNumbers -Name "MyCustomBlockedCallingNumbersName" -``` - -This example renames the current blocked calling numbers with "MyCustomBlockedCallingNumbersName". No change is made besides the Name field change. - -### -------------------------- Example 4 -------------------------- -``` -Set-CsTenantBlockedCallingNumbers -InboundBlockedNumberPatterns @((New-CsInboundBlockedNumberPattern -Name "AnonymousBlockedPattern" -Enabled $true -Pattern "^(?!)Anonymous")) -``` - -This example sets the tenant blocked calling numbers with a new list of inbound blocked number patterns. There is a new InboundBlockedNumberPattern being created. The pattern name is "AnonymousBlockedPattern". The pattern is turned on. The pattern is a normalization rule which contains "Anonymous". - -Note that if the current InboundBlockedNumberPatterns already contains a list of patterns while a new pattern needs to be created, this example will wipe out the existing patterns and only add the new one. Please save the current InboundBlockedNumberPatterns list before adding new patterns. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -The switch to turn on or turn off the blocked calling numbers setting. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch overrides the confirmation prompt displayed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter is a unique identifier that designates the scope, and for per-user scope a name, which identifies the TenantBlockedCallingNumbers to set. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundBlockedNumberPatterns -The InboundBlockedNumberPatterns parameter contains the list of InboundBlockedNumberPatterns. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InboundExemptNumberPatterns -The InboundExemptNumberPatterns parameter contains the list of InboundExemptNumberPatterns. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -This parameter allows you to provide a name to the TenantBlockedCallingNumbers setting. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308". -You can find your tenant ID by running this command: Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS -[Get-CsTenantBlockedCallingNumbers](Get-CsTenantBlockedCallingNumbers.md) diff --git a/skype/skype-ps/skype/Set-CsTenantBlockedNumberExceptionPattern.md b/skype/skype-ps/skype/Set-CsTenantBlockedNumberExceptionPattern.md deleted file mode 100644 index 368b6a8a9b..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantBlockedNumberExceptionPattern.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantblockednumberexceptionpattern -applicable: Skype for Business Online -title: Set-CsTenantBlockedNumberExceptionPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# Set-CsTenantBlockedNumberExceptionPattern - -## SYNOPSIS - -## SYNTAX - -### Identity (Default) -``` -Set-CsTenantBlockedNumberExceptionPattern [-Tenant <System.Guid>] [-Enabled <Boolean>] [-Description <String>] - [-Pattern <String>] [[-Identity] <XdsGlobalRelativeIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### Instance -``` -Set-CsTenantBlockedNumberExceptionPattern [-Tenant <System.Guid>] [-Enabled <Boolean>] [-Description <String>] - [-Pattern <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 -```powershell -PS C:> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -{{ Fill Description Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Enabled -{{ Fill Enabled Description }} - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -{{ Fill Force Description }} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -{{ Fill Identity Description }} - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -{{ Fill Instance Description }} - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Pattern -{{ Fill Pattern Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -{{ Fill Tenant Description }} - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTenantDialPlan.md b/skype/skype-ps/skype/Set-CsTenantDialPlan.md deleted file mode 100644 index 83ea23f60d..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantDialPlan.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantdialplan -applicable: Skype for Business Online -title: Set-CsTenantDialPlan -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTenantDialPlan - -## SYNOPSIS -Use the `Set-CsTenantDialPlan` cmdlet to modify an existing tenant dial plan. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTenantDialPlan [-Tenant <Guid>] [-Description <String>] [-NormalizationRules <List>] - [-ExternalAccessPrefix <String>] [-SimpleName <String>] [-OptimizeDeviceDialing <Boolean>] - [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTenantDialPlan [-Tenant <Guid>] [-Description <String>] [-NormalizationRules <List>] - [-ExternalAccessPrefix <String>] [-SimpleName <String>] [-OptimizeDeviceDialing <Boolean>] - [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The `Set-CsTenantDialPlan` cmdlet modifies an existing tenant dial plan. -Tenant dial plans provide required information to let Enterprise Voice users make telephone calls. -The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. -A tenant dial plan determines such things as which normalization rules are applied and whether a prefix must be dialed for external calls. - -Although normalization rules of a tenant dial plan can be added by using this cmdlet, it is recommended that you use the `New-CsVoiceNormalizationRule` (https://technet.microsoft.com/en-us/library/gg398240.aspx) cmdlet instead. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsTenantDialPlan -ExternalAccessPrefix "123" -Identity vt1tenantDialPlan9 -``` - -This example updates the vt1tenantDialPlan9 tenant dial plan to use an external access prefix of 123. - - -### -------------------------- Example 2 -------------------------- -``` -$nr2 = Get-CsVoiceNormalizationRule -Identity Global/NR2 - -Set-CsTenantDialPlan -ExternalAccessPrefix "123" -Identity vt1tenantDialPlan9 -NormalizationRules @{Add=$nr2} -``` - -This example updates the vt1tenantDialPlan9 tenant dial plan to have an external access prefix of 123 and use the Global/NR2 normalization rules. - - -## PARAMETERS - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -The Description parameter describes the tenant dial plan - what it's for, what type of user it applies to or any other information that helps to identify the purpose of the tenant dial plan. -Maximum characters is 512. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ExternalAccessPrefix -The ExternalAccessPrefix parameter is a number (or set of numbers) that designates the call as external to the organization. -(For example, to tenant-dial an outside line, first dial 9). This prefix is ignored by the normalization rules, although these rules will be applied to the rest of the number. -The OptimizeDeviceDialing parameter must be set to True for this value to take effect. - -The value of this parameter must match the regular expression \[0-9\]{1,4}. -This means it must be a value one to four digits in length, with each digit being a number 0 through 9. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -The Identity parameter is a unique identifier that designates the scope, or for per-user plans a name, to identify the tenant dial plan to modify. -For example, a site Identity is in the format site:\<sitename\>, where sitename is the name of the site. -A tenant dial plan at the service scope is a Registrar or PSTN gateway service, where the Identity value is formatted in this way: Registrar:Redmond.litwareinc.com. -A per-user Identity is a unique string value. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -The Instance parameter allows you to pass a reference to an object to the cmdlet, rather than set individual parameter values. -You can retrieve this object reference by calling the `Get-CsTenantDialPlan` cmdlet. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NormalizationRules -The NormalizationRules parameter is a list of normalization rules that are applied to this dial plan. -Although this list and these rules can be created directly by using this cmdlet, we recommend that you create the normalization rules by the `New-CsVoiceNormalizationRule` (https://technet.microsoft.com/en-us/library/gg398240.aspx) cmdlet, which creates the rule and assigns it to the specified tenant dial plan. - -The number of normalization rules cannot exceed 50 per TenantDialPlan. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OptimizeDeviceDialing -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SimpleName -The SimpleName parameter is a display name for the tenant dial plan. -This name must be unique among all tenant dial plans within the Skype for Business Server deployment. - -This string can be up to 256 characters long. -Valid characters are alphabetic or numeric characters, hyphen (-), dot (.) and parentheses (()). - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. -For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"`. -You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -The WhatIf parameter describes what would happen if you executed the command, without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsTenantFederationConfiguration.md b/skype/skype-ps/skype/Set-CsTenantFederationConfiguration.md deleted file mode 100644 index b5526904b6..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantFederationConfiguration.md +++ /dev/null @@ -1,381 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantfederationconfiguration -applicable: Skype for Business Online -title: Set-CsTenantFederationConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTenantFederationConfiguration - -## SYNOPSIS -Manages federation configuration settings for your Skype for Business Online tenants. -These settings are used to determine which domains (if any) your users are allowed to communicate with. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTenantFederationConfiguration [-Tenant <Guid>] [-AllowedDomains <IAllowedDomainsChoice>] - [-BlockedDomains <List>] [-AllowFederatedUsers <Boolean>] [-AllowPublicUsers <Boolean>] - [-TreatDiscoveredPartnersAsUnverified <Boolean>] [-SharedSipAddressSpace <Boolean>] - [-AllowedDomainsAsAList <List>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTenantFederationConfiguration [-Tenant <Guid>] [-AllowedDomains <IAllowedDomainsChoice>] - [-BlockedDomains <List>] [-AllowFederatedUsers <Boolean>] [-AllowPublicUsers <Boolean>] - [-TreatDiscoveredPartnersAsUnverified <Boolean>] [-SharedSipAddressSpace <Boolean>] - [-AllowedDomainsAsAList <List>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Federation is a service that enables users to exchange IM and presence information with users from other domains. -With Skype for Business Online, administrators can use the federation configuration settings to govern: - -Whether or not users can communicate with people from other domains and if so, which domains they are allowed to communicate with. - -Whether or not users can communicate with people who have accounts on public IM and presence providers such as Windows Live, AOL and Yahoo. - -Administrators can use the `Set-CsTenantFederationConfiguration` cmdlet to enable and disable federation with other domains and federation with public providers. -In addition, this cmdlet can be used to expressly indicate the domains that users can communicate with and/or the domains that users are not allowed to communicate with. -However, administrators must use the `Set-CsTenantPublicProvider` cmdlet in order to indicate the public IM and presence providers that users can and cannot communicate with. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsTenantFederationConfiguration -AllowPublicUsers $False -``` - -The command shown in Example 1 disables communication with public providers for the current tenant. - - -### -------------------------- Example 2 -------------------------- -``` -$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" - -Set-CsTenantFederationConfiguration -BlockedDomains @{Replace=$x} -``` - -In Example 2, the domain fabrikam.com is assigned as the only domain on the blocked domains list for current tenant. -To do this, the first command in the example uses the `New-CsEdgeDomainPattern` cmdlet to create a new domain object for fabrikam.com. -This domain object is stored in a variable named $x. - -The second command in the example then uses the `Set-CsTenantFederationConfiguration` cmdlet to update the blocked domains list. -Using the Replace method ensures that the existing blocked domains list will be replaced by the new list: a list that contains only the domain fabrikam.com. - - -### -------------------------- Example 3 -------------------------- -``` -$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" - -Set-CsTenantFederationConfiguration -BlockedDomains @{Remove=$x} -``` - -The commands shown in Example 3 remove fabrikam.com from the list of domains blocked by the current tenant. -To do this, the first command in the example uses the `New-CsEdgeDomainPattern` cmdlet to create a domain object for fabrikam.com. -The resulting domain object is then stored in a variable named $x. - -The second command in the example then uses the `Set-CsTenantFederationConfiguration` cmdlet and the Remove method to remove fabrikam.com from the blocked domains list for the specified tenant. - - -### -------------------------- Example 4 -------------------------- -``` -$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" - -Set-CsTenantFederationConfiguration -BlockedDomains @{Add=$x} -``` - -The commands shown in Example 4 add the domain fabrikam.com to the list of domains blocked by the current tenant. -To add a new blocked domain, the first command in the example uses the `New-CsEdgeDomainPattern` cmdlet to create a domain object for fabrikam.com. -This object is stored in a variable named $x. - -After the domain object has been created, the second command then uses the `Set-CsTenantFederationConfiguration` cmdlet and the Add method to add fabrikam.com to any domains already on the blocked domains list. - - -### -------------------------- Example 5 -------------------------- -``` -Set-CsTenantFederationConfiguration -BlockedDomains $Null -``` - -Example 5 shows how you can remove all the domains assigned to the blocked domains list for the current tenant. -To do this, simply include the BlockedDomains parameter and set the parameter value to null ($Null). -When this command completes, the blocked domain list will be cleared. - -### -------------------------- Example 6 -------------------------- -``` -$list = New-Object Collections.Generic.List[String] -$list.add("contoso.com") -$list.add("fabrikam.com") -Set-CsTenantFederationConfiguration -AllowedDomainsAsAList $list -``` - -Example 6 shows how you can add domains to the Allowed Domains using a List collection object. -First, a List collection is created and domains are added to it, then, simply include the AllowedDomainsAsAList parameter and set the parameter value to the List object. -When this command completes, the allowed domain list will be filled with those domains. - -## PARAMETERS - -### -AllowedDomains -Domain objects (created by using the `New-CsEdgeAllowList` cmdlet or the `New-CsEdgeAllowAllKnownDomains` cmdlet) that represent the domains that users are allowed to communicate with. -If the `New-CsEdgeAllowAllKnownDomains` cmdlet is used then users can communicate with any domain that does not appear on the blocked domains list. -If the `New-CsEdgeAllowList` cmdlet is used then users can only communicate with domains that have been added to the allowed domains list. - -Note that string values cannot be passed directly to the AllowedDomains parameter. -Instead, you must create an object reference using the `New-CsEdgeAllowList` cmdlet or the `New-CsEdgeAllowAllKnownDomains` cmdlet and then use the object reference variable as the parameter value. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowFederatedUsers -When set to True (the default value) users will be potentially allowed to communicate with users from other domains. -If this property is set to False then users cannot communicate with users from other domains regardless of the values assigned to the AllowedDomains and BlockedDomains properties. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowPublicUsers -When set to True (the default value) users will be potentially allowed to communicate with users who have accounts on public IM and presence providers such as Windows Live, Yahoo, and AOL. -The collection of public providers that users can actually communicate with is managed by using the `Set-CsTenantPublicProvider` cmdlet. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BlockedDomains -If the AllowedDomains property has been set to AllowAllKnownDomains, then users will be allowed to communicate with users from any domain except domains that appear in the blocked domains list. -If the AllowedDomains property has not been set to AllowAllKnownDomains, then the blocked list is ignored, and users can only communicate with domains that have been expressly added to the allowed domains list. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specifies the collection of tenant federation configuration settings to be modified. -Because each tenant is limited to a single, global collection of federation settings there is no need include this parameter when calling the `Set-CsTenantFederationConfiguration` cmdlet. -If you do choose to use the Identity parameter you must also include the Tenant parameter. -For example: - -`Set-CsTenantFederationConfiguration -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Identity "global"` - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SharedSipAddressSpace -When set to True, indicates that the users homed on Skype for Business Online use the same SIP domain as users homed on the on-premises version of Skype for Business Server. -The default value is False, meaning that the two sets of users have different SIP domains. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose federation settings are being modified. -For example: - -`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` - -You can return your tenant ID by running this command: - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TreatDiscoveredPartnersAsUnverified -When set to True, messages sent from discovered partners are considered unverified. -That means that those messages will be delivered only if they were sent from a person who is on the recipient's Contacts list. -The default value is False ($False). - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AllowedDomainsAsAList -You can specify allowed domains using a List object that contains the domains that users are allowed to communicate with. See Examples section. - -```yaml -Type: List -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -The `Set-CsTenantFederationConfiguration` cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.TenantFederationSettings object. - -## OUTPUTS - -### -None. -Instead, the `Set-CsTenantFederationConfiguration` cmdlet modifies existing instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.TenantFederationSettings object. - -## NOTES - -## RELATED LINKS - -[Get-CsTenantFederationConfiguration](Get-CsTenantFederationConfiguration.md) - -[Get-CsTenantPublicProvider](Get-CsTenantPublicProvider.md) - diff --git a/skype/skype-ps/skype/Set-CsTenantHybridConfiguration.md b/skype/skype-ps/skype/Set-CsTenantHybridConfiguration.md index 2161c17779..ca249562b2 100644 --- a/skype/skype-ps/skype/Set-CsTenantHybridConfiguration.md +++ b/skype/skype-ps/skype/Set-CsTenantHybridConfiguration.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenanthybridconfiguration -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/skype/set-cstenanthybridconfiguration +applicable: Skype for Business Server 2019 title: Set-CsTenantHybridConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTenantHybridConfiguration @@ -16,6 +16,8 @@ ms.reviewer: Used in a hybrid scenario to give users homed on Skype for Business Online access to on-premises Enterprise Voice features such as media bypass, Enhanced 9-1-1, and call parking. A hybrid scenario (also known as a split-domain scenario) is a deployment in which some users have accounts homed on-premises while other users have accounts homed on Skype for Business Online. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ### Identity (Default) @@ -259,4 +261,3 @@ None. ## RELATED LINKS [Get-CsTenantHybridConfiguration](Get-CsTenantHybridConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsTenantMigrationConfiguration.md b/skype/skype-ps/skype/Set-CsTenantMigrationConfiguration.md deleted file mode 100644 index 0440446302..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantMigrationConfiguration.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantmigrationconfiguration -applicable: Skype for Business Online -title: Set-CsTenantMigrationConfiguration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTenantMigrationConfiguration - -## SYNOPSIS -Provide the topic introduction here. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTenantMigrationConfiguration [-Tenant <Guid>] [-MeetingMigrationEnabled <Boolean>] - [-ACPMeetingMigrationTriggerEnabled <Boolean>] - [-MeetingMigrationSourceMeetingTypes <MeetingMigrationSourceMeetingTypes>] - [-MeetingMigrationTargetMeetingTypes <MeetingMigrationTargetMeetingTypes>] [[-Identity] <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTenantMigrationConfiguration [-Tenant <Guid>] [-MeetingMigrationEnabled <Boolean>] - [-ACPMeetingMigrationTriggerEnabled <Boolean>] - [-MeetingMigrationSourceMeetingTypes <MeetingMigrationSourceMeetingTypes>] - [-MeetingMigrationTargetMeetingTypes <MeetingMigrationTargetMeetingTypes>] [-Instance <PSObject>] [-Force] - [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Provide the detailed description here. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Insert example commands for example 1. -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -Confirm -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -PARAMVALUE: XdsIdentity - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -PARAMVALUE: PSObject - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MeetingMigrationEnabled -PARAMVALUE: $true | $false - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ACPMeetingMigrationTriggerEnabled -{{Fill ACPMeetingMigrationTriggerEnabled Description}} - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsTenantNetworkRegion.md b/skype/skype-ps/skype/Set-CsTenantNetworkRegion.md deleted file mode 100644 index 10e74271af..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantNetworkRegion.md +++ /dev/null @@ -1,212 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantnetworkregion -applicable: Skype for Business Online -title: Set-CsTenantNetworkRegion -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTenantNetworkRegion - -## SYNOPSIS -As an Admin, you can use the Windows PowerShell command, Set-CsTenantNetworkRegion to define network regions. A network region interconnects various parts of a network across multiple geographic areas. The RegionID parameter is a logical name that represents the geography of the region, and has no dependencies or restrictions. Tenant network region is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTenantNetworkRegion [-Tenant <System.Guid>] [-Description <String>] [-NetworkRegionID <String>] - [-CentralSite <String>] [[-Identity] <XdsGlobalRelativeIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### Instance -``` -Set-CsTenantNetworkRegion [-Tenant <System.Guid>] [-Description <String>] [-NetworkRegionID <String>] - [-CentralSite <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. A network region contains a collection of network sites. For example, if your organization has many sites located in Redmond, then you may choose to designate "Redmond" as a network region. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Set-CsTenantNetworkRegion -Identity "RegionA" -Description "Region A" -``` - -The command shown in Example 1 set the network region 'RegionA' with description 'Region A'. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> Set-CsTenantNetworkRegion -Identity "RegionRedmond" -Description "Redmond region" -CentralSite "Central site 1" -``` - -The command shown in Example 2 set the network region 'RegionRedmond' with description 'Redmond region'. CentralSite is set to "Central site 1". - -Previously in Skype for Business there was an additional required parameter `-CentralSite <site ID>`, however it is now optional. - -## PARAMETERS - -### -CentralSite -This parameter is optional. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of the network region to identify purpose of setting it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network region to be set. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -The Instance parameter allows you to pass a reference to an object to the cmdlet, rather than set individual parameter values. -You can retrieve this object reference by calling the `Get-CsTenantNetworkRegion` cmdlet. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -NetworkRegionID -The name of the network region. Not required in this PowerShell command. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network regions are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTenantNetworkSite.md b/skype/skype-ps/skype/Set-CsTenantNetworkSite.md deleted file mode 100644 index 97cc21a6af..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantNetworkSite.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantnetworksite -applicable: Skype for Business Online -title: Set-CsTenantNetworkSite -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTenantNetworkSite - -## SYNOPSIS -As an Admin, you can use the Windows PowerShell command, Set-CsTenantNetworkSite to define network sites. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. Tenant network site is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTenantNetworkSite [-Tenant <System.Guid>] [-Description <String>] [-NetworkRegionID <String>] - [-LocationPolicy <String>] [-EnableLocationBasedRouting <Boolean>] [-OnlineVoiceRoutingPolicy <String>] - [[-Identity] <XdsGlobalRelativeIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTenantNetworkSite [-Tenant <System.Guid>] [-Description <String>] [-NetworkRegionID <String>] - [-LocationPolicy <String>] [-EnableLocationBasedRouting <Boolean>] [-OnlineVoiceRoutingPolicy <String>] - [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. - -A best practice for Location Based Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Set-CsTenantNetworkSite -Identity "MicrosoftSite1" -NetworkRegionID "RegionRedmond" -Description "Microsoft site 1" -``` - -The command shown in Example 1 set the network site 'MicrosoftSite1' with description 'Microsoft site 1'. - -The network region 'RegionRedmond' is created beforehand and 'MicrosoftSite1' will be associated with 'RegionRedmond'. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> Set-CsTenantNetworkSite -Identity "site2" -Description "site 2" -NetworkRegionID "RedmondRegion" -LocationPolicy "TestLocationPolicy" -EnableLocationBasedRouting $true -SiteAddress "One Microsoft way" -``` - -The command shown in Example 2 sets the network site 'site2' with description 'site 2'. This site is enabled for LBR. The example associates the site with network region 'RedmondRegion' and with location policy 'TestLocationPolicy'. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of the network site to identify purpose of setting it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -EnableLocationBasedRouting -This parameter determines whether the current site is enabled for location based routing. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network site to be set. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -The Instance parameter allows you to pass a reference to an object to the cmdlet, rather than set individual parameter values. -You can retrieve this object reference by calling the `Get-CsTenantNetworkSite` cmdlet. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -LocationPolicy -LocationPolicy is the identifier for the location policy which the current network site is associating to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetworkRegionID -NetworkRegionID is the identifier for the network region which the current network site is associating to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -OnlineVoiceRoutingPolicy -This parameter is deprecated and should not be used. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network sites are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTenantNetworkSubnet.md b/skype/skype-ps/skype/Set-CsTenantNetworkSubnet.md deleted file mode 100644 index ea7ff8bf64..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantNetworkSubnet.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantnetworksubnet -applicable: Skype for Business Online -title: Set-CsTenantNetworkSubnet -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTenantNetworkSubnet - -## SYNOPSIS -As an Admin, you can use the Windows PowerShell command, Set-CsTenantNetworkSubnet to define network subnets and assign them to network sites. Each internal subnet may only be associated with one site. Tenant network subnet is used for Location Based Routing. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTenantNetworkSubnet [-Tenant <System.Guid>] [-Description <String>] [-NetworkSiteID <String>] - [-MaskBits <Int32>] [[-Identity] <XdsGlobalRelativeIdentity>] [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -### Instance -``` -Set-CsTenantNetworkSubnet [-Tenant <System.Guid>] [-Description <String>] [-NetworkSiteID <String>] - [-MaskBits <Int32>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first. - -## EXAMPLES - -###-------------------------- Example 1 -------------------------- -```powershell -PS C:\> Set-CsTenantNetworkSubnet -Identity "192.168.0.1" -MaskBits "24" -NetworkSiteID "site1" -``` - -The command shown in Example 1 set the network subnet '192.168.0.1'. The subnet is in IPv4 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 24. - -IPv4 format subnet accepts maskbits from 0 to 32 inclusive. - -###-------------------------- Example 2 -------------------------- -```powershell -PS C:\> Set-CsTenantNetworkSubnet -Identity "2001:4898:e8:25:844e:926f:85ad:dd8e" -MaskBits "120" -NetworkSiteID "site1" -Description "Subnet 2001:4898:e8:25:844e:926f:85ad:dd8e" -``` - -The command shown in Example 2 set the network subnet '2001:4898:e8:25:844e:926f:85ad:dd8e' with description 'Subnet 2001:4898:e8:25:844e:926f:85ad:dd8e'. The subnet is in IPv6 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 120. - -IPv6 format subnet accepts maskbits from 0 to 128 inclusive. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Provide a description of the network subnet to identify purpose of setting it. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the network subnet to be set. - -```yaml -Type: XdsGlobalRelativeIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -The Instance parameter allows you to pass a reference to an object to the cmdlet, rather than set individual parameter values. -You can retrieve this object reference by calling the `Get-CsTenantNetworkSubnet` cmdlet. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -MaskBits -This parameter determines the length of bits to mask to the subnet. - -IPv4 format subnet accepts maskbits from 0 to 32 inclusive. IPv6 format subnet accepts maskbits from 0 to 128 inclusive. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -NetworkSiteID -NetworkSiteID is the identifier for the network site which the current network subnet is associating to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose network subnets are being created. For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTenantPublicProvider.md b/skype/skype-ps/skype/Set-CsTenantPublicProvider.md deleted file mode 100644 index 49ace4e21a..0000000000 --- a/skype/skype-ps/skype/Set-CsTenantPublicProvider.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantpublicprovider -applicable: Skype for Business Online -title: Set-CsTenantPublicProvider -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Set-CsTenantPublicProvider - -## SYNOPSIS -Enables and disables communication with the third-party IM and presence providers Windows Live, AOL, and Yahoo. -When enabled, Skype for Business Online users will be able to exchange IM and presence information with users who have accounts on the specified public provider. - -## SYNTAX - -``` -Set-CsTenantPublicProvider [-Provider <String[]>] [-Tenant <Guid>] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -Public providers are organizations that provide SIP communication services for the general public. -When you establish a federation relationship with a public provider, you effectively establish federation with any user who has an account hosted by that provider. -For example, if you federate with Windows Live, then your users will be able to exchange instant messages and presence information with anyone who has a Windows Live instant messaging account. - -Skype for Business Online gives administrators the option of configuring federation with one or more of the following public IM and presence providers: - -Windows Live - -AOL - -Yahoo! - -The `Set-CsTenantPublicProvider` cmdlet can be used to enable or disable federation with any of these public providers. -When using this cmdlet, keep in mind that each time you run the `Set-CsTenantPublicProvider` cmdlet you must specify all of the providers that should be enabled. -For example, suppose all three providers are disabled and you run this command: - -`Set-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Provider "WindowsLive"` - -As you might expect, that will enable Windows Live, and will leave AOL and Yahoo disabled. - -Now, suppose you next run this command: - -`Set-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Provider "AOL"` - -That command will enable AOL. -However, it will also disable Windows Live: that's because Windows Live was not specified as part of the parameter value supplied to the Provider parameter. -If you want to enable AOL and keep Windows Live enabled as well, then you must specify both AOL and Windows Live when calling Set-CsTenantPublicProvider: - -`Set-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Provider "AOL","WindowsLive"` - -To disable federation for all three providers, set the Provider property to an empty string (""): - -`Set-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Provider ""` - -Note that simply enabling the status of a public provider does not mean that users can exchange instant messages and presence information with users who have accounts on that provider. -In addition to enabling federation with the provider itself, administrators must also set the AllowPublicUsers property of the federation configuration settings to True. -If this property is set to False then communication will not be allowed with any of the public providers, regardless of the public provider configuration settings. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Set-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Provider "WindowsLive" -``` - -The command shown in Example 1 enables federation with Windows Live for the tenant with the tenant ID bf19b7db-6960-41e5-a139-2aa373474354. -Because Windows Live is the only provider specified, both the AOL and Yahoo providers will be disabled after the command executes. - - -### -------------------------- Example 2 -------------------------- -``` -Set-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Provider "WindowsLive","AOL" -``` - -In Example 2, two public providers are enabled: Windows Live and AOL. -That means that only the Yahoo public provider will be disabled for the specified tenant. - - -### -------------------------- Example 3 -------------------------- -``` -Set-CsTenantPublicProvider -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Provider "" -``` - -Example 3 shows how you can disable all the public providers for a given tenant. -This is done by setting the Provider property to an empty string (""). - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Provider -Indicates the public provider (or providers) that users will be allowed to communicate with. -Valid values are: - -* AOL -* WindowsLive -* Yahoo - -Note that, when configuring public providers, any provider included in the Provider parameter value will be enabled for use, while any provider not included in the parameter value will be disabled. -For example, this syntax enables only Yahoo, while disabling Windows Live and AOL: - -`-Provider "Yahoo"` - -You can enable multiple providers by separating the provider names by using commas: - -`-Provider "AOL","WindowsLive"` - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose public provider settings are being modified. -For example: - -`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` - -You can return your tenant ID by running this command - -`Get-CsTenant | Select-Object DisplayName, TenantID` - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Describes what would happen if you executed the command without actually executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### -The `Set-CsTenantPublicProvider` cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.Hosted.TenantPICStatus object. - -## OUTPUTS - -### -None. -Instead, the `Set-CsTenantPublicProvider` cmdlet modifies existing instances of the Microsoft.Rtc.Management.Hosted.TenantPICStatus object. - -## NOTES - -## RELATED LINKS - -[Get-CsTenantFederationConfiguration](Get-CsTenantFederationConfiguration.md) - -[Get-CsTenantPublicProvider](Get-CsTenantPublicProvider.md) - diff --git a/skype/skype-ps/skype/Set-CsTenantUpdateTimeWindow.md b/skype/skype-ps/skype/Set-CsTenantUpdateTimeWindow.md index 401f8381b9..16213f56b6 100644 --- a/skype/skype-ps/skype/Set-CsTenantUpdateTimeWindow.md +++ b/skype/skype-ps/skype/Set-CsTenantUpdateTimeWindow.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenantupdatetimewindow +online version: https://learn.microsoft.com/powershell/module/skype/set-cstenantupdatetimewindow applicable: Skype for Business Online title: Set-CsTenantUpdateTimeWindow schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTenantUpdateTimeWindow @@ -344,4 +344,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsTestDevice.md b/skype/skype-ps/skype/Set-CsTestDevice.md index d5cac0e6b3..47708627fc 100644 --- a/skype/skype-ps/skype/Set-CsTestDevice.md +++ b/skype/skype-ps/skype/Set-CsTestDevice.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstestdevice +online version: https://learn.microsoft.com/powershell/module/skype/set-cstestdevice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTestDevice schema: 2.0.0 @@ -224,4 +224,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsTestDevice](New-CsTestDevice.md) [Remove-CsTestDevice](Remove-CsTestDevice.md) - diff --git a/skype/skype-ps/skype/Set-CsTestUserCredential.md b/skype/skype-ps/skype/Set-CsTestUserCredential.md index c48ce93af0..35ebd6a75a 100644 --- a/skype/skype-ps/skype/Set-CsTestUserCredential.md +++ b/skype/skype-ps/skype/Set-CsTestUserCredential.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstestusercredential +online version: https://learn.microsoft.com/powershell/module/skype/set-cstestusercredential applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTestUserCredential schema: 2.0.0 @@ -230,4 +230,3 @@ Instead, the `Set-CsTestUserCredential` cmdlet modifies existing instances of th [Get-CsTestUserCredential](Get-CsTestUserCredential.md) [Remove-CsTestUserCredential](Remove-CsTestUserCredential.md) - diff --git a/skype/skype-ps/skype/Set-CsThirdPartyVideoSystem.md b/skype/skype-ps/skype/Set-CsThirdPartyVideoSystem.md index f36891e93d..8ceafe90ca 100644 --- a/skype/skype-ps/skype/Set-CsThirdPartyVideoSystem.md +++ b/skype/skype-ps/skype/Set-CsThirdPartyVideoSystem.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csthirdpartyvideosystem +online version: https://learn.microsoft.com/powershell/module/skype/set-csthirdpartyvideosystem applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsThirdPartyVideoSystem schema: 2.0.0 @@ -247,4 +247,3 @@ However, if you include the PassThru parameter the cmdlet will pass instances of [Remove-CsThirdPartyVideoSystem](Remove-CsThirdPartyVideoSystem.md) [Set-CsThirdPartyVideoSystem](Set-CsThirdPartyVideoSystem.md) - diff --git a/skype/skype-ps/skype/Set-CsThirdPartyVideoSystemPolicy.md b/skype/skype-ps/skype/Set-CsThirdPartyVideoSystemPolicy.md index a8d6723831..c59e5e1f93 100644 --- a/skype/skype-ps/skype/Set-CsThirdPartyVideoSystemPolicy.md +++ b/skype/skype-ps/skype/Set-CsThirdPartyVideoSystemPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csthirdpartyvideosystempolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csthirdpartyvideosystempolicy applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsThirdPartyVideoSystemPolicy schema: 2.0.0 @@ -225,4 +225,3 @@ Instead, the `Set-CsThirdPartyVideoSystemPolicy` cmdlet modifies existing instan [New-CsThirdPartyVideoSystemPolicy](New-CsThirdPartyVideoSystemPolicy.md) [Remove-CsThirdPartyVideoSystemPolicy](Remove-CsThirdPartyVideoSystemPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsTrunkConfiguration.md b/skype/skype-ps/skype/Set-CsTrunkConfiguration.md index 64688edfea..d679673e79 100644 --- a/skype/skype-ps/skype/Set-CsTrunkConfiguration.md +++ b/skype/skype-ps/skype/Set-CsTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cstrunkconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTrunkConfiguration schema: 2.0.0 @@ -28,7 +28,7 @@ Set-CsTrunkConfiguration [[-Identity] <XdsIdentity>] [-ConcentratedTopology <Boo [-RTCPActiveCalls <Boolean>] [-RTCPCallsOnHold <Boolean>] [-SipResponseCodeTranslationRulesList <PSListModifier>] [-SRTPMode <SRTPMode>] [-Force] [-WhatIf] [-Confirm] [-Enable3pccRefer <Boolean>] [-EnableFastFailoverTimer <Boolean>] [-EnableOnlineVoice <Boolean>] - [-EnableRTPLatching <Boolean>] [-ForwardCallHistory <Boolean>] [-ForwardPAI <Boolean>] + [-EnableRTPLatching <Boolean>] [-ForwardCallHistory <Boolean>] [-ForwardPAI <Boolean>] [-ForwardAnonymousCallGatewayPAI <Boolean>] [-OutboundCallingNumberTranslationRulesList <PSListModifier>] [-PstnUsages <PSListModifier>] [-EnableLocationRestriction <Boolean>] [-NetworkSiteID <String>] [AcceptGatewayPAIForOutboundCalls] [<CommonParameters>] ``` @@ -42,7 +42,7 @@ Set-CsTrunkConfiguration [-Instance <PSObject>] [-ConcentratedTopology <Boolean> [-RTCPActiveCalls <Boolean>] [-RTCPCallsOnHold <Boolean>] [-SipResponseCodeTranslationRulesList <PSListModifier>] [-SRTPMode <SRTPMode>] [-Force] [-WhatIf] [-Confirm] [-Enable3pccRefer <Boolean>] [-EnableFastFailoverTimer <Boolean>] [-EnableOnlineVoice <Boolean>] - [-EnableRTPLatching <Boolean>] [-ForwardCallHistory <Boolean>] [-ForwardPAI <Boolean>] + [-EnableRTPLatching <Boolean>] [-ForwardCallHistory <Boolean>] [-ForwardPAI <Boolean>] [-ForwardAnonymousCallGatewayPAI <Boolean>] [-OutboundCallingNumberTranslationRulesList <PSListModifier>] [-PstnUsages <PSListModifier>] [-EnableLocationRestriction <Boolean>] [-NetworkSiteID <String>] [AcceptGatewayPAIForOutboundCalls] [<CommonParameters>] ``` @@ -622,6 +622,26 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ForwardAnonymousCallGatewayPAI +If an anonymous call is forwarded to an outgoing PSTN call, this parameter indicates whether the incoming P-Asserted-Identity (PAI) header at the Gateway call will be preserved in the PSTN call. The default value is **False** ($False). + +**Notes:** +- `EnablePAIPAssthrough` is deprecated in favor of `ForwardAnonymousCallGatewayPAI`. This change is made by installing KB5016483. +- When `ForwardAnonymousCallGatewayPAI` is used, `ForwardPAI` must be set to **True**. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -OutboundCallingNumberTranslationRulesList Collection of outbound calling number translation rules assigned to the trunk. You can retrieve information about the available rules by running this command: @@ -745,4 +765,3 @@ This cmdlet does not return a value; it modifies an object of type Microsoft.Rtc [New-CsOutboundTranslationRule](New-CsOutboundTranslationRule.md) [Set-CsOutboundTranslationRule](Set-CsOutboundTranslationRule.md) - diff --git a/skype/skype-ps/skype/Set-CsTrustedApplication.md b/skype/skype-ps/skype/Set-CsTrustedApplication.md index 3d905b3c39..5decd88312 100644 --- a/skype/skype-ps/skype/Set-CsTrustedApplication.md +++ b/skype/skype-ps/skype/Set-CsTrustedApplication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstrustedapplication +online version: https://learn.microsoft.com/powershell/module/skype/set-cstrustedapplication applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTrustedApplication schema: 2.0.0 @@ -156,4 +156,3 @@ It modifies an object of type Microsoft.Rtc.Management.Xds.DisplayTrustedApplica [Remove-CsTrustedApplication](Remove-CsTrustedApplication.md) [Get-CsTrustedApplication](Get-CsTrustedApplication.md) - diff --git a/skype/skype-ps/skype/Set-CsTrustedApplicationEndpoint.md b/skype/skype-ps/skype/Set-CsTrustedApplicationEndpoint.md index 0c587c5c33..505d5b29a7 100644 --- a/skype/skype-ps/skype/Set-CsTrustedApplicationEndpoint.md +++ b/skype/skype-ps/skype/Set-CsTrustedApplicationEndpoint.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstrustedapplicationendpoint +online version: https://learn.microsoft.com/powershell/module/skype/set-cstrustedapplicationendpoint applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTrustedApplicationEndpoint schema: 2.0.0 @@ -341,4 +341,3 @@ It modifies an object of type Microsoft.Rtc.Management.ADConnect.Schema.OCSADApp [Remove-CsTrustedApplicationEndpoint](Remove-CsTrustedApplicationEndpoint.md) [Get-CsTrustedApplicationEndpoint](Get-CsTrustedApplicationEndpoint.md) - diff --git a/skype/skype-ps/skype/Set-CsTrustedApplicationPool.md b/skype/skype-ps/skype/Set-CsTrustedApplicationPool.md index 4309a1f09e..aa6bd0be59 100644 --- a/skype/skype-ps/skype/Set-CsTrustedApplicationPool.md +++ b/skype/skype-ps/skype/Set-CsTrustedApplicationPool.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstrustedapplicationpool +online version: https://learn.microsoft.com/powershell/module/skype/set-cstrustedapplicationpool applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsTrustedApplicationPool schema: 2.0.0 @@ -325,4 +325,3 @@ It modifies an object of type Microsoft.Rtc.Management.Xds.DisplayExternalServer [Get-CsTrustedApplicationPool](Get-CsTrustedApplicationPool.md) [New-CsTrustedApplicationComputer](New-CsTrustedApplicationComputer.md) - diff --git a/skype/skype-ps/skype/Set-CsUCPhoneConfiguration.md b/skype/skype-ps/skype/Set-CsUCPhoneConfiguration.md index 39d98eb572..5a7d9ecb84 100644 --- a/skype/skype-ps/skype/Set-CsUCPhoneConfiguration.md +++ b/skype/skype-ps/skype/Set-CsUCPhoneConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csucphoneconfiguration -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csucphoneconfiguration +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUCPhoneConfiguration schema: 2.0.0 manager: bulenteg @@ -54,7 +54,7 @@ In addition to creating new collections of UC phone settings, you can use the `S For example, by default logging is disabled for UC phones. To enable logging at the global level, you can use the `Set-CsUCPhoneConfiguration` cmdlet to change the value of the global collection's LoggingLevel property to True. -The following parameters are not applicable to Skype for Business Online: AsJob, CalendarPollInterval, Force, Identity, Instance, PipelineVariable, SIPSecurityMode, Tenant, Voice8021p, and VoiceDiffServTag +The following parameters are not applicable to Skype for Business Online: CalendarPollInterval, Force, Identity, Instance, PipelineVariable, SIPSecurityMode, Tenant, Voice8021p, and VoiceDiffServTag ## EXAMPLES @@ -413,4 +413,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsUCPhoneConfiguration](New-CsUCPhoneConfiguration.md) [Remove-CsUCPhoneConfiguration](Remove-CsUCPhoneConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsUICulture.md b/skype/skype-ps/skype/Set-CsUICulture.md index 8caeaae3b9..e596429fed 100644 --- a/skype/skype-ps/skype/Set-CsUICulture.md +++ b/skype/skype-ps/skype/Set-CsUICulture.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuiculture +online version: https://learn.microsoft.com/powershell/module/skype/set-csuiculture applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUICulture schema: 2.0.0 @@ -136,4 +136,3 @@ Instead, the cmdlet modifies existing instances of the System.Globalization.Cult ## RELATED LINKS [Get-CsUICulture](Get-CsUICulture.md) - diff --git a/skype/skype-ps/skype/Set-CsUnassignedNumber.md b/skype/skype-ps/skype/Set-CsUnassignedNumber.md index 8111a9ccf5..404dd230e4 100644 --- a/skype/skype-ps/skype/Set-CsUnassignedNumber.md +++ b/skype/skype-ps/skype/Set-CsUnassignedNumber.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csunassignednumber +online version: https://learn.microsoft.com/powershell/module/skype/set-csunassignednumber applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUnassignedNumber schema: 2.0.0 @@ -311,4 +311,3 @@ It modifies an object of type Microsoft.Rtc.Management.Voice.Helpers.DisplayAnno [Get-CsAnnouncement](Get-CsAnnouncement.md) [Get-CsExUmContact](Get-CsExUmContact.md) - diff --git a/skype/skype-ps/skype/Set-CsUser.md b/skype/skype-ps/skype/Set-CsUser.md index 850fe92ef0..6578b30a14 100644 --- a/skype/skype-ps/skype/Set-CsUser.md +++ b/skype/skype-ps/skype/Set-CsUser.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuser -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csuser +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUser schema: 2.0.0 manager: bulenteg @@ -17,6 +17,7 @@ Modifies Skype for Business properties for an existing user account. Properties can be modified only for accounts that have been enabled for use with Skype for Business. This cmdlet was introduced in Lync Server 2010. +**Note**: Using this cmdlet for Microsoft Teams users in commercial and GCC cloud instances has been deprecated. Use the new [Set-CsPhoneNumberAssignment](/powershell/module/teams/set-csphonenumberassignment) and [Remove-CsPhoneNumberAssignment](/powershell/module/teams/remove-csphonenumberassignment) cmdlets instead. ## SYNTAX @@ -30,8 +31,8 @@ Set-CsUser [-DomainController <Fqdn>] [-Identity] <UserIdParameter> [-PassThru] ``` ## DESCRIPTION -The `Set-CsUser` cmdlet enables you to modify the Skype for Business related user account attributes that are stored in Active Directory Domain Services or modify a subset of Skype for Business online user attributes that are stored in Azure Active Directory. -For example, you can disable or re-enable a user for Skype for Business Server; enable or disable a user for audio/video (A/V) communications; or modify a user's private line and line URI numbers. For Skype for Business online enable or disable a user for enterprise voice, hosted voicemail, or modify the user's on premise line uri. +The `Set-CsUser` cmdlet enables you to modify the Skype for Business related user account attributes that are stored in Active Directory Domain Services or modify a subset of Skype for Business online user attributes that are stored in Microsoft Entra ID. +For example, you can disable or re-enable a user for Skype for Business Server; enable or disable a user for audio/video (A/V) communications; or modify a user's private line and line URI numbers. For Skype for Business online enable or disable a user for enterprise voice, hosted voicemail, or modify the user's on premise line uri. The `Set-CsUser` cmdlet can be used only for users who have been enabled for Skype for Business. The only attributes you can modify using the `Set-CsUser` cmdlet are attributes related to Skype for Business. @@ -39,11 +40,10 @@ Other user account attributes, such as the user's job title or department, canno Keep in mind, however, that the Skype for Business attributes should only be modified by using the `Set-CsUser` cmdlet or the Skype for Business Server Control Panel. You should not attempt to manually configure these attributes. - ## EXAMPLES ### -------------------------- Example 1 -------------------------- -``` +```powershell Set-CsUser -Identity "Pilar Ackerman" -EnterpriseVoiceEnabled $True ``` @@ -53,7 +53,7 @@ This task is carried out by adding the EnterpriseVoiceEnabled parameter, and the ### -------------------------- Example 2 -------------------------- -``` +```powershell Get-CsUser -LdapFilter "Department=Finance" | Set-CsUser -EnterpriseVoiceEnabled $True ``` @@ -62,7 +62,7 @@ In this command, the `Get-CsUser` cmdlet and the LdapFilter parameter are first That information is then piped to the `Set-CsUser` cmdlet, which enables Enterprise Voice for each account in the collection. ### -------------------------- Example 3 -------------------------- -``` +```powershell Set-CsUser -Identity "Pilar Ackerman" -LineUri "tel:+123456789" ``` @@ -79,11 +79,10 @@ User Identities can also be referenced by using the user's Active Directory dist You can use the asterisk (*) wildcard character when using the display name as the user Identity. For example, the Identity "Smith" returns all the users who have a display name that ends with the string value " Smith". - ```yaml Type: UserIdParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: True @@ -99,11 +98,12 @@ If set to True, the user will largely be restricted to sending and receiving ins You cannot disable A/V communications if a user is currently enabled for remote call control, Enterprise Voice, and/or Internet Protocol private branch exchange (IP-PBX) soft phone routing. +**Note**: This parameter is not available for Teams Only tenants from version 3.0.0 onwards. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -122,7 +122,6 @@ If you later re-enable the account by using the Enabled parameter, the associate This differs from using the `Disable-CsUser` cmdlet to disable a user account. When you run the `Disable-CsUser` cmdlet, all the Skype for Business Server data associated with that account is deleted. - ```yaml Type: Boolean Parameter Sets: (All) @@ -140,11 +139,10 @@ Accept wildcard characters: False Enables you to specify a domain controller to connect to when modifying a user account. If this parameter is not included then the cmdlet will use the first available domain controller. - ```yaml Type: Fqdn Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -158,11 +156,12 @@ Accept wildcard characters: False Indicates whether the user has been enabled for Enterprise Voice, which is the Microsoft implementation of Voice over Internet Protocol (VoIP). With Enterprise Voice, users can make telephone calls using the Internet rather than using the standard telephone network. +**Note**: Using this parameter for Microsoft Teams users in commercial and GCC cloud instances has been deprecated. Use the new [Set-CsPhoneNumberAssignment](/powershell/module/teams/set-csphonenumberassignment) cmdlet instead. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -176,11 +175,12 @@ Accept wildcard characters: False When set to True, enables a user's voice mail calls to be routed to a hosted version of Microsoft Exchange Server. In addition, setting this option to True enables Skype for Business users to directly place a call to another user's voice mail. +**Note**: It is not required to set this parameter for Microsoft Teams users. Using this parameter has been deprecated for Microsoft Teams users in commercial and GCC cloud instances. ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -191,25 +191,26 @@ Accept wildcard characters: False ``` ### -LineURI -Phone number assigned to the user. -The line Uniform Resource Identifier (URI) must be specified using the E.164 format and use the "TEL:" prefix. -For example: TEL:+14255551297. -Any extension number should be added to the end of the line URI, for example: TEL:+14255551297;ext=51297. - -It is important to note that Skype for Business Server treats TEL:+14255551297 and TEL:+14255551297;ext=51297 as two different numbers. -If you assign Ken Myer the line URI TEL:+14255551297 and later try to assign Pilar Ackerman the line URI TEL:+14255551297;ext=51297, that assignment will succeed; the number assigned to Pilar will not be flagged as a duplicate number. -This is due to the fact that, depending on your setup, those two numbers could actually be different. -For example, in some organizations dialing 1-425-555-1297 routes your call to an Exchange Auto Attendant. -Conversely, dialing just the extension (51297) or using Skype for Business to dial the number 1-425-555-1297 extension 51297 will route your call directly to the user. +Phone number to be assigned to the user in Skype for Business Server or Direct Routing phone number to be assigned to a Microsoft Teams user in GCC High and DoD cloud instances only. + +The line Uniform Resource Identifier (URI) must be specified using the E.164 format and the "tel:" prefix, for example: tel:+14255551297. +Any extension number should be added to the end of the line URI, for example: tel:+14255551297;ext=51297. + +It is important to note that Skype for Business Server treats tel:+14255551297 and tel:+14255551297;ext=51297 as two different numbers. +If you assign Ken Myer the line URI tel:+14255551297 and later try to assign Pilar Ackerman the line URI tel:+14255551297;ext=51297, that assignment will succeed; the number assigned to Pilar will not +be flagged as a duplicate number. This is due to the fact that, depending on your setup, those two numbers could actually be different. For example, in some organizations dialing 1-425-555-1297 +routes your call to an Exchange Auto Attendant. Conversely, dialing just the extension (51297) or using Skype for Business to dial the number 1-425-555-1297 extension 51297 will route your call +directly to the user. -Note: Extension should be part of the E164 Number. For example if you have 5 digit Extensions then the last 5 digits of the E164 Number should always match the 5 digit extension TEL:+14255551297;ext=51297 +For Direct Routing phone numbers in GCC High and DoD cloud instances, assigning a base phone number to a user or resource account is not supported if you already have other users or resource accounts assigned phone numbers with the same base phone number and extensions or vice versa. For instance, if you have a user with the assigned phone number +14255551200;ext=123 you can't assign the phone number +14255551200 to another user or resource account or if you have a user or resource account with the assigned phone number +14255551200 you can't assign the phone number +14255551200;ext=123 to another user or resource account. Assigning phone numbers with the same base number but different extensions to users and resource accounts is supported. For instance, you can have a user with +14255551200;ext=123 and another user with +14255551200;ext=124. +Note: Extension should be part of the E164 Number. For example if you have 5 digit Extensions then the last 5 digits of the E164 Number should always match the 5 digit extension tel:+14255551297;ext=51297 ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: False Position: Named @@ -223,11 +224,10 @@ The URI of the remote call control telephone gateway assigned to the user. The LineServerUri is the gateway URI, prefaced by "sip:". For example: sip:rccgateway@litwareinc.com - ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -243,14 +243,13 @@ A private line is a phone number that is not published in Active Directory Domai In addition, this private line bypasses most in-bound call routing rules; for example, a call to a private line will not be forwarded to a person's delegates. Private lines are often used for personal phone calls or for business calls that should be kept separate from other team members. -The private line value should be specified using the E.164 format, and be prefixed by the "TEL:" prefix. -For example: TEL:+14255551297. - +The private line value should be specified using the E.164 format, and be prefixed by the "tel:" prefix. +For example: tel:+14255551297. ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -270,11 +269,10 @@ For details, see the parameter EnterpriseVoiceEnabled. To be enabled for remote call control, a user must have both a LineUri and a LineServerUri. - ```yaml Type: Boolean Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -288,11 +286,10 @@ Accept wildcard characters: False Unique identifier (similar to an email address) that allows the user to communicate using SIP devices such as Skype for Business. The SIP address must use the sip: prefix as well as a valid SIP domain; for example: `-SipAddress sip:kenmyer@litwareinc.com`. - ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -306,10 +303,12 @@ Accept wildcard characters: False Enables you to pass a user object through the pipeline that represents the user whose account is being modified. By default, the `Set-CsUser` cmdlet does not pass objects through the pipeline. +**Note**: This parameter is not available for Teams Only tenants from version 3.0.0 onwards. + ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -355,11 +354,10 @@ Accept wildcard characters: False Enables you to assign one or more third-party audio conferencing providers to a user. However, it is recommended that you use the `Set-CsUserAcp` cmdlet to assign Audio conferencing providers. - ```yaml Type: AcpInfo Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -381,11 +379,10 @@ ArchivingToExchange NoArchiving - ```yaml Type: ExchangeArchivingPolicyOptionsEnum Parameter Sets: (All) -Aliases: +Aliases: Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False @@ -397,20 +394,24 @@ Accept wildcard characters: False ### -OnPremLineURI Specifies the phone number assigned to the user if no number is assigned to that user in the Skype for Business hybrid environment. -The line Uniform Resource Identifier (URI) must be specified using the E.164 format and use the "TEL:" prefix. -For example: TEL:+14255551297. -Any extension number should be added to the end of the line URI, for example: TEL:+14255551297;ext=51297. +The line Uniform Resource Identifier (URI) must be specified using the E.164 format and use the "tel:" prefix. +For example: tel:+14255551297. +Any extension number should be added to the end of the line URI, for example: tel:+14255551297;ext=51297. -Note that Skype for Business treats TEL:+14255551297 and TEL:+14255551297;ext=51297 as two different numbers. -If you assign Ken Myer the line URI TEL:+14255551297 and later try to assign Pilar Ackerman the line URI TEL:+14255551297;ext=51297, that assignment will succeed. +Note that Skype for Business treats tel:+14255551297 and tel:+14255551297;ext=51297 as two different numbers. +If you assign Ken Myer the line URI tel:+14255551297 and later try to assign Pilar Ackerman the line URI tel:+14255551297;ext=51297, that assignment will succeed. Depending on your setup, those two numbers could actually be different. For example, in some organizations dialing 1-425-555-1297 routes your call to an Exchange Auto Attendant. Conversely, dialing just the extension (51297) or using Skype for Business to dial the number 1-425-555-1297 extension 51297 will route your call directly to the user. +**Note**: Using this parameter for Microsoft Teams users in commercial and GCC cloud instances has been deprecated. Use the new [Set-CsPhoneNumberAssignment](/powershell/module/teams/set-csphonenumberassignment) cmdlet instead. + +**Note**: Using this parameter for Microsoft Teams users in GCC High and DoD cloud instances has been deprecated. Use the -LineURI parameter instead. + ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -447,5 +448,3 @@ The `Set-CsUser` cmdlet does not return any objects. [Move-CsUser](Move-CsUser.md) -[Get-CsOnlineUser](Get-CsOnlineUser.md) - diff --git a/skype/skype-ps/skype/Set-CsUserAcp.md b/skype/skype-ps/skype/Set-CsUserAcp.md index 6b493798ee..e79059fc9a 100644 --- a/skype/skype-ps/skype/Set-CsUserAcp.md +++ b/skype/skype-ps/skype/Set-CsUserAcp.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuseracp -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csuseracp +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUserAcp schema: 2.0.0 manager: bulenteg @@ -22,10 +22,12 @@ This cmdlet was introduced in Lync Server 2010. ``` Set-CsUserAcp [-Identity] <UserIdParameter> -Domain <String> -Name <String> -ParticipantPasscode <String> -TollNumber <String> [-IsDefault <Boolean>] [-TollFreeNumbers <String[]>] [-Url <String>] [-PassThru] - [-WhatIf] [-Confirm] [-AsJob] [<CommonParameters>] + [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION +Deprecation Notice: Integration of Skype for Business with third-party audio conferencing providers has been retired. More details are here - https://learn.microsoft.com/skypeforbusiness/legal-and-regulatory/end-of-integration-with-3rd-party-providers. As a result, cmdlet no longer works. + An audio conferencing provider is a third-party company that provides organizations with conferencing services. Among other things, audio conferencing providers offer a way for users located off site and not connected to the corporate network or the Internet, to participate in the audio portion of a conference or meeting. Audio conferencing providers often include high-end services such as live translation, transcription and live per-conference operator assistance. @@ -300,22 +302,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -338,4 +324,3 @@ None. [Get-CsUserAcp](Get-CsUserAcp.md) [Remove-CsUserAcp](Remove-CsUserAcp.md) - diff --git a/skype/skype-ps/skype/Set-CsUserCallForwardingSettings.md b/skype/skype-ps/skype/Set-CsUserCallForwardingSettings.md index 9232b34e37..1c371c4113 100644 --- a/skype/skype-ps/skype/Set-CsUserCallForwardingSettings.md +++ b/skype/skype-ps/skype/Set-CsUserCallForwardingSettings.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csusercallforwardingsettings +online version: https://learn.microsoft.com/powershell/module/skype/set-csusercallforwardingsettings applicable: Skype for Business Server 2019 title: Set-CsUserCallForwardingSettings schema: 2.0.0 @@ -42,21 +42,45 @@ Set-CsUserCallForwardingSettings -EnableSimulRing <String> [-SettingsActiveWorkH ## DESCRIPTION The feature enables the use of SEFAUtil functionality in PowerShell. SEFAUtil (Secondary Extension Feature Activation) enables Skype server administrators and helpdesk agents to configure delegate-ringing, call-forwarding and Group Call Pickup settings on behalf of a Skype server user. This tool also allows administrators to query the call-routing settings that are published for a particular user. + The cmdlets introduced in this feature can only be run by members of the following groups for On-prem deployments, per the access level specified below: -• CsAdministrator - Get and Set for all cmdlets -• CsVoiceAdministrator - Get and Set for all cmdlets -• CsServerAdministrator - Get and Set for all cmdlets -• CsHelpDesk - Get for all cmdlets + +- CsAdministrator - Get and Set for all cmdlets +- CsVoiceAdministrator - Get and Set for all cmdlets +- CsServerAdministrator - Get and Set for all cmdlets +- CsHelpDesk - Get for all cmdlets + Server auto-discovery needs to be enabled. There are no additional licensing requirements for use of the cmdlets. ## EXAMPLES ### Example 1 ```powershell -PS C:\> {{ Add example code here }} +PS C:\> Set-CsUserCallForwardingSettings -User user@contoso.com -DisableForwarding +``` + +This example disables the user's call forwarding settings. + +### Example 2 +```powershell +PS C:\> Set-CsUserCallForwardingSettings -User user@contoso.com -EnableForwarding +4721956666 +``` + +This example modifies the user's call forwarding settings, activating call forwarding to a specific phone number. + +### Example 3 +```powershell +PS C:\> Set-CsUserCallForwardingSettings -User user1@contoso.com -EnableSimulRing Team -Team user2@contoso.com,user2@contoso.com -TeamDelegateRingWaitTime 5 +``` + +This example modifies the SimulRing settings, activating simultaneous ring for the users listed in the Team parameter. + +### Example 4 +```powershell +PS C:\> Set-CsUserCallForwardingSettings -User user@contoso.com -DisableForwarding -UnansweredToVoicemail -UnansweredWaitTime 30 ``` -{{ Add example description here }} +This example sends unanswered calls to voicemail after 30 seconds. ## PARAMETERS @@ -77,8 +101,7 @@ Accept wildcard characters: False ``` ### -DelegateRingWaitTime -Specifies the time, in seconds, to wait before ringing delegates. -Acceptable inputs: 0, 5, 10 +Specifies the time, in seconds, to wait before ringing delegates. Acceptable inputs: 0, 5, 10, 15. The parameter DelegateWaitRingTime needs to be explicitly set to a positive value to allow call forwarding to delegates. ```yaml @@ -95,7 +118,7 @@ Accept wildcard characters: False ``` ### -Delegates -Specifies list of delegates that calls will be forwarded to. This parameter can only be used with EnableForwarding and EnableSimulRing parameters. +Specifies the list of delegates that calls will be forwarded to. This parameter can only be used with EnableForwarding and EnableSimulRing parameters. ```yaml Type: System.Management.Automation.PSListModifier`1[System.String] @@ -143,9 +166,7 @@ Accept wildcard characters: False ``` ### -EnableSimulRing -This is a switch parameter that enables forwarding to the specified destination. Cannot be used along with the DisableForwarding and EnableForwarding parameters. -oSimulRingDestination can be a phone number, delegates, or team call group. - Acceptable input formats: "<phone number>", Team, Delegates +This is a switch parameter that enables forwarding to the specified destination. Cannot be used along with the DisableForwarding and EnableForwarding parameters. SimulRingDestination can be a phone number, delegates, or team call group. Acceptable input formats: "\<phone number\>", Team, Delegates. ```yaml @@ -178,9 +199,7 @@ Accept wildcard characters: False ``` ### -Team -Specifies list of team members that calls will be forwarded to. The add and remove switches will add and remove specified users from the Team Members list. The replace parameter will set the list to the specified list, wiping out the previous list. Add and remove can be used together, but neither of them can be used along with replace. -o Acceptable input formats for add/remove/replace list: The inputs can be a single user address (in one of the below formats), or a comma separated list of user addresses, in the 4 standard formats that Identity parameter accepts. - +Specifies list of team members that calls will be forwarded to. The add and remove switches will add and remove specified users from the Team Members list. The replace parameter will set the list to the specified list, wiping out the previous list. Add and remove can be used together, but neither of them can be used along with replace. Acceptable input formats for add/remove/replace list: The inputs can be a single user address (in one of the below formats), or a comma separated list of user addresses, in the 4 standard formats that Identity parameter accepts. ```yaml Type: System.Management.Automation.PSListModifier`1[System.String] @@ -196,7 +215,7 @@ Accept wildcard characters: False ``` ### -TeamDelegateRingWaitTime -{{ Fill TeamDelegateRingWaitTime Description }} +Specifies the time, in seconds, to wait before ringing team members. ```yaml Type: Int32 @@ -212,7 +231,7 @@ Accept wildcard characters: False ``` ### -UnansweredToOther -{{ Fill UnansweredToOther Description }} +Specifies that unanswered calls will be send to other user or phone number. ```yaml Type: String @@ -228,7 +247,7 @@ Accept wildcard characters: False ``` ### -UnansweredToVoicemail -{{ Fill UnansweredToVoicemail Description }} +Specifies that unanswered calls will be send to voicemail. ```yaml Type: SwitchParameter @@ -244,7 +263,7 @@ Accept wildcard characters: False ``` ### -UnansweredWaitTime -{{ Fill UnansweredWaitTime Description }} +Specifies the time, in seconds, to wait before send unanswered calls to voicemail. ```yaml Type: Int32 @@ -260,7 +279,7 @@ Accept wildcard characters: False ``` ### -User -{{ Fill User Description }} +Specifies the SIP address of the user whose call forwarding settings will be modified. ```yaml Type: String diff --git a/skype/skype-ps/skype/Set-CsUserDatabaseState.md b/skype/skype-ps/skype/Set-CsUserDatabaseState.md index ed0e505571..457fd92a5b 100644 --- a/skype/skype-ps/skype/Set-CsUserDatabaseState.md +++ b/skype/skype-ps/skype/Set-CsUserDatabaseState.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserdatabasestate +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserdatabasestate applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUserDatabaseState schema: 2.0.0 @@ -207,4 +207,3 @@ Instead, the `Set-CsUserDatabaseState` cmdlet modifies existing instances of the [Get-CsUserDatabaseState](Get-CsUserDatabaseState.md) [Update-CsUserDatabase](Update-CsUserDatabase.md) - diff --git a/skype/skype-ps/skype/Set-CsUserDelegates.md b/skype/skype-ps/skype/Set-CsUserDelegates.md index a64d13a21c..51ab7a0a53 100644 --- a/skype/skype-ps/skype/Set-CsUserDelegates.md +++ b/skype/skype-ps/skype/Set-CsUserDelegates.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserdelegates +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserdelegates applicable: Skype for Business Server 2019 title: Set-CsUserDelegates schema: 2.0.0 @@ -13,26 +13,26 @@ ms.reviewer: # Set-CsUserDelegates ## SYNOPSIS -{{ Fill in the Synopsis }} +Used to modify a user's delegates list. ## SYNTAX ``` -Set-CsUserDelegates -Delegates <System.Management.Automation.PSListModifier`1[System.String]> [-User] <String> +Set-CsUserDelegates -Delegates <PSListModifier> [-User] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION -{{ Fill in the Description }} +The feature enables the use of SEFAUtil functionality in PowerShell. SEFAUtil (Secondary Extension Feature Activation) enables Skype server administrators and helpdesk agents to configure delegate-ringing, call-forwarding and Group Call Pickup settings on behalf of a Skype server user. This tool also allows administrators to query the call-routing settings that are published for a particular user. The cmdlets introduced in this feature can only be run by members of the following groups for On-prem deployments, per the access level specified below: CsAdministrator - Get and Set for all cmdlets, CsVoiceAdministrator - Get and Set for all cmdlets, CsServerAdministrator - Get and Set for all cmdlets, CsHelpDesk - Get for all cmdlets Server auto-discovery needs to be enabled. There are no additional licensing requirements for use of the cmdlets. For more information see [Using SEFAUtil functionality via PowerShell in Skype for Business Server 2019](https://learn.microsoft.com/skypeforbusiness/sefautil-functionality). ## EXAMPLES ### Example 1 ```powershell -PS C:\> {{ Add example code here }} +PS C:\> Set-CsUserDelegates -Delegates @{add='ChewDavid@contoso.com','dmx@contoso.com'} -User "Ken.Myer@contoso.com" ``` -{{ Add example description here }} +This cmdlet modifies the specified user's delegation settings, returns an object of delegates list and displays the list of delegates, in case of success. In case of failure, an appropriate error message will be shown. ## PARAMETERS @@ -52,7 +52,7 @@ Accept wildcard characters: False ``` ### -Delegates -{{ Fill Delegates Description }} +Specifies list of delegates. The add and remove switches will add and remove specified users from the delegates list. The replace parameter will set the list to the specified list, wiping out the previous list. Add and remove can be used together, but neither of them can be used along with replace. Acceptable input formats for add/remove/replace list: The inputs can be a single user address (in one of the below formats), or a comma separated list of user addresses, in the 4 standard formats that Identity parameter accepts. ```yaml Type: System.Management.Automation.PSListModifier`1[System.String] @@ -67,7 +67,7 @@ Accept wildcard characters: False ``` ### -Force -{{ Fill Force Description }} +Suppresses the display of any non-fatal error message that might occur when running the command. ```yaml Type: SwitchParameter @@ -82,7 +82,7 @@ Accept wildcard characters: False ``` ### -User -{{ Fill User Description }} +Indicates the Identity of the user account to be modified. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. ```yaml Type: String diff --git a/skype/skype-ps/skype/Set-CsUserPstnSettings.md b/skype/skype-ps/skype/Set-CsUserPstnSettings.md index 918e6fc68f..92e36241ea 100644 --- a/skype/skype-ps/skype/Set-CsUserPstnSettings.md +++ b/skype/skype-ps/skype/Set-CsUserPstnSettings.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserpstnsettings +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserpstnsettings applicable: Skype for Business Online title: Set-CsUserPstnSettings schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsUserPstnSettings @@ -15,6 +15,8 @@ ms.reviewer: ## SYNOPSIS Use the `Set-CsUserPstnSettings` cmdlet to modify an existing voice-enabled user's public switched telephone network (PSTN) settings. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` @@ -172,4 +174,3 @@ The `Set-CsUserPstnSettings` cmdlet returns instances of the UserPstnSettings ob ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsUserReplicatorConfiguration.md b/skype/skype-ps/skype/Set-CsUserReplicatorConfiguration.md index f46a0315aa..55e92367ce 100644 --- a/skype/skype-ps/skype/Set-CsUserReplicatorConfiguration.md +++ b/skype/skype-ps/skype/Set-CsUserReplicatorConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserreplicatorconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserreplicatorconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUserReplicatorConfiguration schema: 2.0.0 @@ -290,4 +290,3 @@ Instead, the cmdlet modifies the global instance (the only such instance) of the [New-CsUserReplicatorConfiguration](New-CsUserReplicatorConfiguration.md) [Remove-CsUserReplicatorConfiguration](Remove-CsUserReplicatorConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsUserServer.md b/skype/skype-ps/skype/Set-CsUserServer.md index e98058b0ab..5e4b1ca974 100644 --- a/skype/skype-ps/skype/Set-CsUserServer.md +++ b/skype/skype-ps/skype/Set-CsUserServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUserServer schema: 2.0.0 @@ -250,4 +250,3 @@ Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management. ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsUserServicesConfiguration.md b/skype/skype-ps/skype/Set-CsUserServicesConfiguration.md index 3e98288aa5..e84ea92d4a 100644 --- a/skype/skype-ps/skype/Set-CsUserServicesConfiguration.md +++ b/skype/skype-ps/skype/Set-CsUserServicesConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserservicesconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserservicesconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUserServicesConfiguration schema: 2.0.0 @@ -459,4 +459,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [New-CsUserServicesConfiguration](New-CsUserServicesConfiguration.md) [Remove-CsUserServicesConfiguration](Remove-CsUserServicesConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsUserServicesPolicy.md b/skype/skype-ps/skype/Set-CsUserServicesPolicy.md index 79f6fd34bc..b616c7d545 100644 --- a/skype/skype-ps/skype/Set-CsUserServicesPolicy.md +++ b/skype/skype-ps/skype/Set-CsUserServicesPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserservicespolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserservicespolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsUserServicesPolicy schema: 2.0.0 @@ -52,7 +52,7 @@ After that, you must then use the `Invoke-CsUcsRollback` cmdlet to "manually" mi Skype for Business Server Control Panel: The functions carried out by the `Set-CsUserServicesPolicy` cmdlet are not available in the Skype for Business Server Control Panel. -The following parameters are not applicable to Skype for Business Online: AsJob, Force, Identity, Instance, MigrationDelayInDays, PipelineVariable, and Tenant +The following parameters are not applicable to Skype for Business Online: Force, Identity, Instance, MigrationDelayInDays, PipelineVariable, and Tenant ## EXAMPLES @@ -281,4 +281,3 @@ Instead, the `Set-CsUserServicesPolicy` cmdlet modifies existing instances of th [New-CsUserServicesPolicy](New-CsUserServicesPolicy.md) [Remove-CsUserServicesPolicy](Remove-CsUserServicesPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsUserTeamMembers.md b/skype/skype-ps/skype/Set-CsUserTeamMembers.md index c93355657d..ec4147db30 100644 --- a/skype/skype-ps/skype/Set-CsUserTeamMembers.md +++ b/skype/skype-ps/skype/Set-CsUserTeamMembers.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csuserteammembers +online version: https://learn.microsoft.com/powershell/module/skype/set-csuserteammembers applicable: Skype for Business Server 2019 title: Set-CsUserTeamMembers schema: 2.0.0 @@ -13,26 +13,26 @@ ms.reviewer: # Set-CsUserTeamMembers ## SYNOPSIS -{{ Fill in the Synopsis }} +Used to modify a user's team members list. ## SYNTAX ``` -Set-CsUserTeamMembers -Team <System.Management.Automation.PSListModifier`1[System.String]> [-User] <String> +Set-CsUserTeamMembers -Team <PSListModifier> [-User] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION -{{ Fill in the Description }} +The feature enables the use of SEFAUtil (Secondary Extension Feature Activation) functionality in PowerShell. SEFAUtil enables Skype server administrators and helpdesk agents to configure delegate-ringing, call-forwarding and Group Call Pickup settings on behalf of a Skype server user. This tool also allows administrators to query the call-routing settings that are published for a particular user. The cmdlets introduced in this feature can only be run by members of the following groups for On-prem deployments, per the access level specified below: CsAdministrator - Get and Set for all cmdlets, CsVoiceAdministrator - Get and Set for all cmdlets, CsServerAdministrator - Get and Set for all cmdlets, CsHelpDesk - Get for all cmdlets Server auto-discovery needs to be enabled. There are no additional licensing requirements for use of the cmdlets. For more information see [Using SEFAUtil functionality via PowerShell in Skype for Business Server 2019](https://learn.microsoft.com/skypeforbusiness/sefautil-functionality). ## EXAMPLES ### Example 1 ```powershell -PS C:\> {{ Add example code here }} +PS C:\> Set-CsUserTeamMembers -User "Ken.Myer@contoso.com" -Team @{add='ChewDavid@contoso.com','dmx@contoso.com'} ``` -{{ Add example description here }} +This cmdlet adds two other users to the specified user's team members list, returns an object that contains the team member list and displays the object on the screen, in case of success. In case of failure, an appropriate error message will be shown. ## PARAMETERS @@ -52,7 +52,7 @@ Accept wildcard characters: False ``` ### -Force -{{ Fill Force Description }} +Suppresses the display of any non-fatal error message that might occur when running the command. ```yaml Type: SwitchParameter @@ -67,10 +67,10 @@ Accept wildcard characters: False ``` ### -Team -{{ Fill Team Description }} +Specifies list of team members. The add and remove switches will add and remove specified users from the Team Members list. The replace parameter will set the list to the specified list, wiping out the previous list. Add and remove can be used together, but neither of them can be used along with replace. Acceptable input formats for add/remove/replace list: The inputs can be a single user address (in one of the below formats), or a comma separated list of user addresses, in the 4 standard formats that Identity parameter accepts. ```yaml -Type: System.Management.Automation.PSListModifier`1[System.String] +Type: PSListModifier Parameter Sets: (All) Aliases: @@ -82,7 +82,7 @@ Accept wildcard characters: False ``` ### -User -{{ Fill User Description }} +Indicates the Identity of the user account to be modified. User Identities can be specified using one of four formats: 1) the SIP address; 2) the user principal name (UPN); 3) the domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. ```yaml Type: String diff --git a/skype/skype-ps/skype/Set-CsVideoGateway.md b/skype/skype-ps/skype/Set-CsVideoGateway.md index ed9b6768a1..166e402503 100644 --- a/skype/skype-ps/skype/Set-CsVideoGateway.md +++ b/skype/skype-ps/skype/Set-CsVideoGateway.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvideogateway +online version: https://learn.microsoft.com/powershell/module/skype/set-csvideogateway applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVideoGateway schema: 2.0.0 @@ -191,4 +191,3 @@ The `Set-CsVideoGateway` cmdlet does not return any objects or values. ## RELATED LINKS [Get-CsVideoTrunk](Get-CsVideoTrunk.md) - diff --git a/skype/skype-ps/skype/Set-CsVideoInteropServer.md b/skype/skype-ps/skype/Set-CsVideoInteropServer.md index 2a9250a899..206a48e916 100644 --- a/skype/skype-ps/skype/Set-CsVideoInteropServer.md +++ b/skype/skype-ps/skype/Set-CsVideoInteropServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvideointeropserver +online version: https://learn.microsoft.com/powershell/module/skype/set-csvideointeropserver applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVideoInteropServer schema: 2.0.0 @@ -301,4 +301,3 @@ The `Set-CsVideoInteropServer` cmdlet does not return any objects or values. [Set-CsVideoGateway](Set-CsVideoGateway.md) [Get-CsVideoTrunk](Get-CsVideoTrunk.md) - diff --git a/skype/skype-ps/skype/Set-CsVideoInteropServerConfiguration.md b/skype/skype-ps/skype/Set-CsVideoInteropServerConfiguration.md index f0b550fb86..80989a190d 100644 --- a/skype/skype-ps/skype/Set-CsVideoInteropServerConfiguration.md +++ b/skype/skype-ps/skype/Set-CsVideoInteropServerConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvideointeropserverconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csvideointeropserverconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVideoInteropServerConfiguration schema: 2.0.0 @@ -205,4 +205,3 @@ The `Set-CsVideoInteropServerConfiguration` cmdlet modifies existing instances o [New-CsVideoInteropServerConfiguration](New-CsVideoInteropServerConfiguration.md) [Remove-CsVideoInteropServerConfiguration](Remove-CsVideoInteropServerConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsVideoInteropServerSyntheticTransactionConfiguration.md b/skype/skype-ps/skype/Set-CsVideoInteropServerSyntheticTransactionConfiguration.md index 0788048bdd..05da2f52c4 100644 --- a/skype/skype-ps/skype/Set-CsVideoInteropServerSyntheticTransactionConfiguration.md +++ b/skype/skype-ps/skype/Set-CsVideoInteropServerSyntheticTransactionConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvideointeropserversynthetictransactionconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csvideointeropserversynthetictransactionconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVideoInteropServerSyntheticTransactionConfiguration schema: 2.0.0 @@ -182,4 +182,3 @@ None. [Remove-CsVideoInteropServerSyntheticTransactionConfiguration](Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md) [Test-CsP2PVideoInteropServerSipTrunkAV](Test-CsP2PVideoInteropServerSipTrunkAV.md) - diff --git a/skype/skype-ps/skype/Set-CsVideoTrunkConfiguration.md b/skype/skype-ps/skype/Set-CsVideoTrunkConfiguration.md index 7e3c9b5afb..32c668c947 100644 --- a/skype/skype-ps/skype/Set-CsVideoTrunkConfiguration.md +++ b/skype/skype-ps/skype/Set-CsVideoTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvideotrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csvideotrunkconfiguration applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVideoTrunkConfiguration schema: 2.0.0 @@ -39,7 +39,7 @@ The Video Interop Server is a Skype service that runs on a standalone pool and c To enable the Video Interop Server, you must use Topology Builder to define at least one VIS instance. Each VIS instance will typically be associated with one or more Video Gateways. -Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from an third party PBX supporting 3rd party video teleconferencing systems (VTCs). +Video Gateways route traffic between internal and third party video devices such as an internal Skype endpoint receiving video from a third party PBX supporting 3rd party video teleconferencing systems (VTCs). The Video Gateway and a Video Interop Server (VIS) use a Session Initiation Protocol (SIP) trunk to connect video calls between third party VTCs and internal endpoints. Video Trunks settings can be managed by using the CsVideoTrunkConfiguration cmdlets. @@ -280,4 +280,3 @@ The `Set-CsVideoTrunkConfiguration` cmdlet modifies existing instances of the Mi [New-CsVideoTrunkConfiguration](New-CsVideoTrunkConfiguration.md) [Remove-CsVideoTrunkConfiguration](Remove-CsVideoTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsVoiceConfiguration.md b/skype/skype-ps/skype/Set-CsVoiceConfiguration.md index 7410f4ce3f..55b566c49c 100644 --- a/skype/skype-ps/skype/Set-CsVoiceConfiguration.md +++ b/skype/skype-ps/skype/Set-CsVoiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvoiceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csvoiceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVoiceConfiguration schema: 2.0.0 @@ -214,4 +214,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Set-CsVoiceTestConfiguration](Set-CsVoiceTestConfiguration.md) [Get-CsVoiceTestConfiguration](Get-CsVoiceTestConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsVoiceNormalizationRule.md b/skype/skype-ps/skype/Set-CsVoiceNormalizationRule.md index b4c71d9a6f..75e02f9f89 100644 --- a/skype/skype-ps/skype/Set-CsVoiceNormalizationRule.md +++ b/skype/skype-ps/skype/Set-CsVoiceNormalizationRule.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvoicenormalizationrule -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/set-csvoicenormalizationrule +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVoiceNormalizationRule schema: 2.0.0 manager: bulenteg @@ -17,19 +17,20 @@ Modifies a voice normalization rule. Voice normalization rules are used to convert a telephone dialing requirement (for example, dialing 9 to access an outside line) to the E.164 phone number format used by Skype for Business Server. This cmdlet was introduced in Lync Server 2010. +**Note**: This cmdlet has been deprecated in Teams PowerShell Module 4.0.0. ## SYNTAX ### Identity (Default) ``` -Set-CsVoiceNormalizationRule [-Tenant <Guid>] [-Description <String>] [-Pattern <String>] - [-Translation <String>] [-IsInternalExtension <Boolean>] [-Priority <Int32>] [[-Identity] <XdsIdentity>] +Set-CsVoiceNormalizationRule [-Description <String>] [-Pattern <String>] + [-Translation <String>] [-IsInternalExtension <Boolean>] [-Priority <Int32>] [[-Identity] <XdsIdentity>] [-Tenant <guid>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ### Instance ``` -Set-CsVoiceNormalizationRule [-Tenant <Guid>] [-Description <String>] [-Pattern <String>] +Set-CsVoiceNormalizationRule [-Tenant <guid>] [-Description <String>] [-Pattern <String>] [-Translation <String>] [-IsInternalExtension <Boolean>] [-Priority <Int32>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` @@ -67,13 +68,11 @@ For example, if the existing pattern matched any four-digit number and the numbe ### -------------------------- Example 3 -------------------------- ``` $a = Get-CsVoiceNormalizationRule -Identity global/RedmondFourDigit - $a.name = "RedmondRule" - Set-CsVoiceNormalizationRule -Instance $a ``` -Example 3 changes the name of the normalization rule. +Example 3 applies to Skype For Business Server only and changes the name of the normalization rule. Keep in mind that changing the name also changes the name portion of the Identity. The `Set-CsVoiceNormalizationRule` cmdlet doesn't have a Name parameter, so in order to change the name we first call the `Get-CsVoiceNormalizationRule` cmdlet to retrieve the rule with the Identity global/RedmondFourDigit and assign the returned object to the variable $a. We then assign the string RedmondRule to the Name property of the object. @@ -90,7 +89,7 @@ The Identity specified must include the scope followed by a slash followed by th Type: XdsIdentity Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: 1 @@ -108,7 +107,7 @@ This object must be of type NormalizationRule and can be retrieved by calling th Type: PSObject Parameter Sets: Instance Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -127,7 +126,7 @@ Maximum string length: 512 characters. Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -146,7 +145,7 @@ This value is ignored if the value of the OptimizeDeviceDialing property of the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -165,7 +164,7 @@ This parameter sets the order in which the rules are tested against the number. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -182,7 +181,7 @@ A regular expression that the dialed number must match in order for this rule to Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -199,7 +198,7 @@ The regular expression pattern that will be applied to the number to convert it Type: String Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -216,7 +215,7 @@ Suppresses any confirmation prompts that would otherwise be displayed before mak Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -233,7 +232,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -250,7 +249,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -260,13 +259,13 @@ Accept wildcard characters: False ``` ### -Tenant -{{Fill Tenant Description}} +For internal Microsoft usage. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 Required: False Position: Named @@ -305,4 +304,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Set-CsDialPlan](Set-CsDialPlan.md) [Get-CsDialPlan](Get-CsDialPlan.md) - diff --git a/skype/skype-ps/skype/Set-CsVoicePolicy.md b/skype/skype-ps/skype/Set-CsVoicePolicy.md index 9a35761710..bd2491217f 100644 --- a/skype/skype-ps/skype/Set-CsVoicePolicy.md +++ b/skype/skype-ps/skype/Set-CsVoicePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvoicepolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csvoicepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVoicePolicy schema: 2.0.0 @@ -574,4 +574,3 @@ Instead, it configures instances of the Microsoft.Rtc.Management.WritableConfig. [Test-CsVoicePolicy](Test-CsVoicePolicy.md) [Get-CsPstnUsage](Get-CsPstnUsage.md) - diff --git a/skype/skype-ps/skype/Set-CsVoiceRoute.md b/skype/skype-ps/skype/Set-CsVoiceRoute.md index f1379ed7ec..7a66daa439 100644 --- a/skype/skype-ps/skype/Set-CsVoiceRoute.md +++ b/skype/skype-ps/skype/Set-CsVoiceRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvoiceroute +online version: https://learn.microsoft.com/powershell/module/skype/set-csvoiceroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVoiceRoute schema: 2.0.0 @@ -366,4 +366,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl [Get-CsPstnUsage](Get-CsPstnUsage.md) [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsVoiceRoutingPolicy.md b/skype/skype-ps/skype/Set-CsVoiceRoutingPolicy.md index 05cd14173b..1c2aeaffd5 100644 --- a/skype/skype-ps/skype/Set-CsVoiceRoutingPolicy.md +++ b/skype/skype-ps/skype/Set-CsVoiceRoutingPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvoiceroutingpolicy +online version: https://learn.microsoft.com/powershell/module/skype/set-csvoiceroutingpolicy applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVoiceRoutingPolicy schema: 2.0.0 @@ -241,4 +241,3 @@ Instead, the `Set-CsVoiceRoutingPolicy` cmdlet modifies existing instances of th [New-CsVoiceRoutingPolicy](New-CsVoiceRoutingPolicy.md) [Remove-CsVoiceRoutingPolicy](Remove-CsVoiceRoutingPolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsVoiceTestConfiguration.md b/skype/skype-ps/skype/Set-CsVoiceTestConfiguration.md index 0c3fe41f46..56905fbe1a 100644 --- a/skype/skype-ps/skype/Set-CsVoiceTestConfiguration.md +++ b/skype/skype-ps/skype/Set-CsVoiceTestConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvoicetestconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csvoicetestconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVoiceTestConfiguration schema: 2.0.0 @@ -302,4 +302,3 @@ This cmdlet returns an object of type Microsoft.Rtc.Management.WritableConfig.Po [Get-CsDialPlan](Get-CsDialPlan.md) [Get-CsVoicePolicy](Get-CsVoicePolicy.md) - diff --git a/skype/skype-ps/skype/Set-CsVoicemailReroutingConfiguration.md b/skype/skype-ps/skype/Set-CsVoicemailReroutingConfiguration.md index 4a8f40da33..b20a8c0c9d 100644 --- a/skype/skype-ps/skype/Set-CsVoicemailReroutingConfiguration.md +++ b/skype/skype-ps/skype/Set-CsVoicemailReroutingConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvoicemailreroutingconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-csvoicemailreroutingconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsVoicemailReroutingConfiguration schema: 2.0.0 @@ -226,4 +226,3 @@ It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.E [Remove-CsVoicemailReroutingConfiguration](Remove-CsVoicemailReroutingConfiguration.md) [Get-CsVoicemailReroutingConfiguration](Get-CsVoicemailReroutingConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsWatcherNodeConfiguration.md b/skype/skype-ps/skype/Set-CsWatcherNodeConfiguration.md index 7647c21d99..8f943ec290 100644 --- a/skype/skype-ps/skype/Set-CsWatcherNodeConfiguration.md +++ b/skype/skype-ps/skype/Set-CsWatcherNodeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cswatchernodeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cswatchernodeconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsWatcherNodeConfiguration schema: 2.0.0 @@ -388,4 +388,3 @@ Instead, the `Set-CsWatcherNodeConfiguration` cmdlet modifies existing instances [Remove-CsWatcherNodeConfiguration](Remove-CsWatcherNodeConfiguration.md) [Test-CsWatcherNodeConfiguration](Test-CsWatcherNodeConfiguration.md) - diff --git a/skype/skype-ps/skype/Set-CsWebServer.md b/skype/skype-ps/skype/Set-CsWebServer.md index 37bf8e9c68..5bf3b8c7cc 100644 --- a/skype/skype-ps/skype/Set-CsWebServer.md +++ b/skype/skype-ps/skype/Set-CsWebServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cswebserver +online version: https://learn.microsoft.com/powershell/module/skype/set-cswebserver applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsWebServer schema: 2.0.0 @@ -631,4 +631,3 @@ Instead, the `Set-CsWebServer` cmdlet modifies instances of the Microsoft.Rtc.Ma ## RELATED LINKS [Get-CsService](Get-CsService.md) - diff --git a/skype/skype-ps/skype/Set-CsWebServiceConfiguration.md b/skype/skype-ps/skype/Set-CsWebServiceConfiguration.md index 7f97711dae..7a41b51175 100644 --- a/skype/skype-ps/skype/Set-CsWebServiceConfiguration.md +++ b/skype/skype-ps/skype/Set-CsWebServiceConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cswebserviceconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/set-cswebserviceconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsWebServiceConfiguration schema: 2.0.0 @@ -23,7 +23,7 @@ This cmdlet was introduced in Lync Server 2010. ``` Set-CsWebServiceConfiguration [[-Identity] <XdsIdentity>] [-AllowAnonymousAccessToLWAConference <Boolean>] - [-CASigningKeyLength <UInt64>] [-DefaultValidityPeriodHours <UInt64>] [-EnableCertChainDownload <Boolean>] + [-CASigningKeyLength <UInt64>] [-DefaultValidityPeriodHours <UInt64>] [-EnableCertChainDownload <Boolean>] [-EnableCORS <Boolean>] [-EnableGroupExpansion <Boolean>] [-InferCertChainFromSSL <Boolean>] [-MACResolverUrl <String>] [-MaxCSRKeySize <UInt64>] [-MaxGroupSizeToExpand <UInt32>] [-MaxValidityPeriodHours <UInt64>] [-MinCSRKeySize <UInt64>] [-MinValidityPeriodHours <UInt64>] [-SecondaryLocationSourceUrl <String>] @@ -34,6 +34,7 @@ Set-CsWebServiceConfiguration [[-Identity] <XdsIdentity>] [-AllowAnonymousAccess [-UseWsFedPassiveAuth <Boolean>] [-WsFedPassiveMetadataUri <String>] [-CrossDomainAuthorizationList <PSListModifier>] [-EnableMediaBasicAuth <Boolean>] [-EnableStatisticsInResponse <Boolean>] [-HstsMaxAgeInSeconds <Int64>] + [-PendingGetWaitTimeOutInMinutes <Int64>] [-PendingGetWaitSupportingApps <String>] [-MobilePreferredAuthType <MobilePreferredAuthType>] [-UseDomainAuthInLWA <Boolean>] [-OverrideAuthTypeForInternalClients <String>] [-OverrideAuthTypeForExternalClients <String>] [-UseWebClientLegacyUI <Boolean>] [<CommonParameters>] @@ -54,6 +55,7 @@ Set-CsWebServiceConfiguration [-Instance <PSObject>] [-AllowAnonymousAccessToLWA [-UseWsFedPassiveAuth <Boolean>] [-WsFedPassiveMetadataUri <String>] [-CrossDomainAuthorizationList <PSListModifier>] [-EnableMediaBasicAuth <Boolean>] [-EnableStatisticsInResponse <Boolean>] [-HstsMaxAgeInSeconds <Int64>] + [-PendingGetWaitTimeOutInMinutes <Int64>] [-PendingGetWaitSupportingApps <String>] [-MobilePreferredAuthType <MobilePreferredAuthType>] [-UseDomainAuthInLWA <Boolean>] [-OverrideAuthTypeForInternalClients <String>] [-OverrideAuthTypeForExternalClients <String>] [-UseWebClientLegacyUI <Boolean>] [<CommonParameters>] @@ -77,7 +79,7 @@ Alternatively, you can modify the property values for an existing collection by ## EXAMPLES -### -------------------------- Example 1 ------------------------ +### Example 1 ```powershell Set-CsWebServiceConfiguration -Identity site:Redmond -EnableGroupExpansion $True @@ -86,7 +88,7 @@ Set-CsWebServiceConfiguration -Identity site:Redmond -EnableGroupExpansion $True Example 1 enables group expansion for the Web Services configuration settings applied to the Redmond site (-Identity site:Redmond). This is done by including the EnableGroupExpansion property and setting the parameter value to True. -### -------------------------- Example 2 ------------------------ +### Example 2 ```powershell Get-CsWebServiceConfiguration -Filter "site:*" | Set-CsWebServiceConfiguration -MaxValidityPeriodHours 16 @@ -96,7 +98,7 @@ In Example 2, the maximum validity period for all the Web Services configuration To carry out this task, the `Get-CsWebServiceConfiguration` cmdlet is called along with the Filter parameter; the filter value "site:*" limits the returned data to settings where the Identity begins with the characters "site:". This collection is then piped to the `Set-CsWebServiceConfiguration` cmdlet, which takes each item in the collection and changes the MaxValidityPeriodHours property to 16. -### -------------------------- Example 3 ------------------------ +### Example 3 ```powershell Get-CsWebServiceConfiguration | Where-Object {$_.EnableGroupExpansion -eq $True} | Set-CsWebServiceConfiguration -MaxGroupSizeToExpand 400 @@ -107,7 +109,7 @@ To do this, the `Get-CsWebServiceConfiguration` cmdlet is called without any par This collection is then piped to the `Where-Object` cmdlet, which selects only those settings where the EnableGroupExpansion property is equal to True. In turn, this filtered collection is piped to the `Set-CsWebServiceConfiguration` cmdlet, which takes each item in the collection and sets the value of the MaxGroupSizeToExpand property to 400. -### -------------------------- Example 4 ------------------------ +### Example 4 ```powershell Set-CsWebServiceConfiguration -Identity global -ShowDownloadCommunicatorAttendeeLink $True @@ -116,7 +118,7 @@ Set-CsWebServiceConfiguration -Identity global -ShowDownloadCommunicatorAttendee The command shown in Example 4 shows how the global Web Services settings can be configured so that any person joining a meeting using a client application other than Skype for Business Server will first be shown a link to a site where he or she can download Skype for Business Web App. This is done by including the ShowDownloadCommunicatorAttendeeLink parameter and setting the parameter value to $True. -### -------------------------- Example 5 -------------------------- +### Example 5 ```powershell $x = New-CsWebOrigin -Url "https://fabrikam.com/" @@ -132,7 +134,7 @@ The second command in the example uses the `Set-CsWebServiceConfiguration` cmdle The syntax @{Add=$x} adds the domain to any domains already in the collection of domains authorized for cross-domain scripting. To replace the existing collection with just https://fabrikam.com use the syntax @{Replace=$x}. -### -------------------------- Example 6 -------------------------- +### Example 6 ```powershell $x = Get-CsWebServiceConfiguration -Identity "site:Redmond" @@ -155,7 +157,7 @@ To remove the second domain (index number 1) from the CrossDomainAuthorizationLi Note that command 2 removes the domain from the copy of the Redmond site stored in the variable $x and not from the site itself. To actually remove the domain from the Redmond site, the third command in the example uses the `Set-CsWebServiceConfiguration` cmdlet and the Instance parameter to overwrite settings for the Redmond site with the settings stored in $x. -### -------------------------- Example 7 -------------------------- +### Example 7 ```powershell Set-CsWebServiceConfiguration -Identity "site:Redmond" - CrossDomainAuthorizationList $Null @@ -287,6 +289,23 @@ Default value: None Accept pipeline input: False Accept wildcard characters: False ``` +### -EnableCORS + +If set to True, Cross-Origin Resource Sharing is enabled. + +```yaml +Type: Boolean +Position: Named +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` ### -EnableGroupExpansion @@ -805,6 +824,46 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PendingGetWaitTimeOutInMinutes +Specifies the time in minutes to send an event at a particular interval to Keep Alive EventChannel. +The value can be specified in between 5 to 15 minutes (both inclusive). +The default value is 15 minutes. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PendingGetWaitSupportingApps +Specifies a semicolon-separated list of applications for which PendingGetWaitTimeOutInMinutes need to be set. +Supported applications are Android, iPhone, iPad, Macintosh, Windows. +To support all applications you can give All as input. +For example: +- To support Android and Macintosh - Android;Macintosh; +- To support all devices - All; +The default value is None. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MobilePreferredAuthType Specifies the default authentication method used for mobile client connectivity. @@ -862,8 +921,7 @@ Accept wildcard characters: False ### -OverrideAuthTypeForExternalClients -The proper way to access the functionality that this parameter provide is to use the Get/Set-CsAuthConfig cmdlet. For more information, please go to -https://docs.microsoft.com/en-us/powershell/module/skype/set-csauthconfig?view=skype-ps. +The proper way to access the functionality that this parameter provide is to use the Get/Set-CsAuthConfig cmdlet. For more information, see [Set-CsAuthConfig](https://learn.microsoft.com/powershell/module/skype/set-csauthconfig). ```yaml Type: String @@ -879,8 +937,7 @@ Accept wildcard characters: False ### -OverrideAuthTypeForInternalClients -The proper way to access the functionality that this parameter provide is to use the Get/Set-CsAuthConfig cmdlet. For more information, please go to -https://docs.microsoft.com/en-us/powershell/module/skype/set-csauthconfig?view=skype-ps. +The proper way to access the functionality that this parameter provide is to use the Get/Set-CsAuthConfig cmdlet. For more information, see [Set-CsAuthConfig](https://learn.microsoft.com/powershell/module/skype/set-csauthconfig). ```yaml Type: String diff --git a/skype/skype-ps/skype/Set-CsXmppAllowedPartner.md b/skype/skype-ps/skype/Set-CsXmppAllowedPartner.md index a33dbc6dee..cb19f7f293 100644 --- a/skype/skype-ps/skype/Set-CsXmppAllowedPartner.md +++ b/skype/skype-ps/skype/Set-CsXmppAllowedPartner.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csxmppallowedpartner -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-csxmppallowedpartner +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsXmppAllowedPartner schema: 2.0.0 manager: rogupta @@ -381,4 +381,3 @@ Instead, the `Set-CsXmppAllowedPartner` cmdlet modifies existing instances of th [New-CsXmppAllowedPartner](New-CsXmppAllowedPartner.md) [Remove-CsXmppAllowedPartner](Remove-CsXmppAllowedPartner.md) - diff --git a/skype/skype-ps/skype/Set-CsXmppGatewayConfiguration.md b/skype/skype-ps/skype/Set-CsXmppGatewayConfiguration.md index 8e0c92b071..4a97a22ae7 100644 --- a/skype/skype-ps/skype/Set-CsXmppGatewayConfiguration.md +++ b/skype/skype-ps/skype/Set-CsXmppGatewayConfiguration.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csxmppgatewayconfiguration -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/set-csxmppgatewayconfiguration +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Set-CsXmppGatewayConfiguration schema: 2.0.0 manager: rogupta @@ -314,4 +314,3 @@ Instead, the `Set-CsXmppGatewayConfiguration` cmdlet modifies existing instances ## RELATED LINKS [Get-CsXmppGatewayConfiguration](Get-CsXmppGatewayConfiguration.md) - diff --git a/skype/skype-ps/skype/Show-CsClsLogging.md b/skype/skype-ps/skype/Show-CsClsLogging.md index ea88ab9b23..034eb323fd 100644 --- a/skype/skype-ps/skype/Show-CsClsLogging.md +++ b/skype/skype-ps/skype/Show-CsClsLogging.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/show-csclslogging +online version: https://learn.microsoft.com/powershell/module/skype/show-csclslogging applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Show-CsClsLogging schema: 2.0.0 @@ -153,4 +153,3 @@ The `Show-CsClsLogging` cmdlet does not return objects. [Sync-CsClsLogging](Sync-CsClsLogging.md) [Update-CsClsLogging](Update-CsClsLogging.md) - diff --git a/skype/skype-ps/skype/Start-CsClsLogging.md b/skype/skype-ps/skype/Start-CsClsLogging.md index e1eb0f1629..52f1ac216a 100644 --- a/skype/skype-ps/skype/Start-CsClsLogging.md +++ b/skype/skype-ps/skype/Start-CsClsLogging.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/start-csclslogging +online version: https://learn.microsoft.com/powershell/module/skype/start-csclslogging applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Start-CsClsLogging schema: 2.0.0 @@ -208,4 +208,3 @@ The `Start-CsClsLogging` cmdlet does not return objects. [Sync-CsClsLogging](Sync-CsClsLogging.md) [Update-CsClsLogging](Update-CsClsLogging.md) - diff --git a/skype/skype-ps/skype/Start-CsExMeetingMigration.md b/skype/skype-ps/skype/Start-CsExMeetingMigration.md deleted file mode 100644 index 5d5d1a98a9..0000000000 --- a/skype/skype-ps/skype/Start-CsExMeetingMigration.md +++ /dev/null @@ -1,190 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/start-csexmeetingmigration -applicable: Skype for Business Online -title: Start-CsExMeetingMigration -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Start-CsExMeetingMigration - -## SYNOPSIS -This cmdlet manually trigger a meeting migration request for the specified user. - -## SYNTAX - -``` -Start-CsExMeetingMigration [-SourceMeetingType <MmsSourceMeetingTypes>] [-TargetMeetingType <MmsTargetMeetingTypes>] - [-Tenant <Guid>] [-Identity] <UserIdParameter> [-WhatIf] [-Confirm] [-AsJob] [<CommonParameters>] -``` - -## DESCRIPTION -Meeting Migration Service (MMS) is a Skype for Business service that runs in the background and automatically updates Skype for Business and Microsoft Teams meetings for users. -MMS is designed to eliminate the need for users to run the Meeting Migration Tool to update their Skype for Business and Microsoft Teams meetings. - -Also, with `Start-CsExMeetingMigration` cmdlet, you can start a meeting migration manually. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Start-CsExMeetingMigration -Identity ashaw@contoso.com -TargetMeetingType Teams -``` - -This example below shows how to initiate meeting migration for user ashaw@contoso.com so that all meetings are migrated to Teams. - - -## PARAMETERS - -### -Identity -Specifies the Identity of the user account to be modified. A user identity can be specified by using one of four formats: -1. The user's SIP address -2. The user's user principal name (UPN) -3. The user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) -4. The user's Active Directory display name (for example, Ken Myer). You can also reference a user account by using the user's Active Directory distinguished name. - -```yaml -Type: UserIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -The Confirm switch causes the command to pause processing and requires confirmation to proceed. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -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: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -SourceMeetingType -The possible values are: -* **All:** indicates that both Skype for Business meetings and Teams meetings should be updated. This is the **default value**. -* **SfB:** indicates that only Skype for Business meetings (whether on-premises or online) should be updated. -* **Teams:** indicates that only Teams meetings should be updated. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: All -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TargetMeetingType -The possible values are: -* **Current:** specifies that Skype for Business meetings remain Skype for Business meetings and Teams meetings remain Teams meetings. However audio conferencing coordinates might be changed, and any on-premises Skype for Business meetings would be migrated to Skype for Business Online. This is the **default value**. -* **Teams:** specifies that any existing meeting must be migrated to Teams, regardless of whether the meeting is hosted in Skype for Business online or on-premises, and regardless of whether any audio conferencing updates are required. - -```yaml -Type: Object -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: Current -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. -You can continue to work in the session while the job finishes. -The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. -To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS -[Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/SkypeForBusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms) - -[Get-CsMeetingMigrationStatus](https://docs.microsoft.com/powershell/module/skype/get-csmeetingmigrationstatus) - -[Set-CsTenantMigrationConfiguration](https://docs.microsoft.com/powershell/module/skype/set-cstenantmigrationconfiguration) - -[Get-CsTenantMigrationConfiguration](https://docs.microsoft.com/powershell/module/skype/get-cstenantmigrationconfiguration) - - - diff --git a/skype/skype-ps/skype/Start-CsPool.md b/skype/skype-ps/skype/Start-CsPool.md index e5d44b4e87..61b0bbeaf5 100644 --- a/skype/skype-ps/skype/Start-CsPool.md +++ b/skype/skype-ps/skype/Start-CsPool.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/start-cspool +online version: https://learn.microsoft.com/powershell/module/skype/start-cspool applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Start-CsPool schema: 2.0.0 @@ -186,4 +186,3 @@ None [Backup-CsPool](Backup-CsPool.md) [Get-CsPool](Get-CsPool.md) - diff --git a/skype/skype-ps/skype/Start-CsWindowsService.md b/skype/skype-ps/skype/Start-CsWindowsService.md index 87534935ab..ab1c0c8008 100644 --- a/skype/skype-ps/skype/Start-CsWindowsService.md +++ b/skype/skype-ps/skype/Start-CsWindowsService.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/start-cswindowsservice +online version: https://learn.microsoft.com/powershell/module/skype/start-cswindowsservice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Start-CsWindowsService schema: 2.0.0 @@ -258,4 +258,3 @@ Instead, the `Start-CsWindowsService` cmdlet starts instances of the Microsoft.R [Get-CsWindowsService](Get-CsWindowsService.md) [Stop-CsWindowsService](Stop-CsWindowsService.md) - diff --git a/skype/skype-ps/skype/Stop-CsClsLogging.md b/skype/skype-ps/skype/Stop-CsClsLogging.md index b29b1f8b21..46d2784689 100644 --- a/skype/skype-ps/skype/Stop-CsClsLogging.md +++ b/skype/skype-ps/skype/Stop-CsClsLogging.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/stop-csclslogging +online version: https://learn.microsoft.com/powershell/module/skype/stop-csclslogging applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Stop-CsClsLogging schema: 2.0.0 @@ -174,4 +174,3 @@ The `Stop-CsClsLogging` cmdlet does not return objects. [Sync-CsClsLogging](Sync-CsClsLogging.md) [Update-CsClsLogging](Update-CsClsLogging.md) - diff --git a/skype/skype-ps/skype/Stop-CsWindowsService.md b/skype/skype-ps/skype/Stop-CsWindowsService.md index 3a03b4ae5d..fa3302b7ad 100644 --- a/skype/skype-ps/skype/Stop-CsWindowsService.md +++ b/skype/skype-ps/skype/Stop-CsWindowsService.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/stop-cswindowsservice +online version: https://learn.microsoft.com/powershell/module/skype/stop-cswindowsservice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Stop-CsWindowsService schema: 2.0.0 diff --git a/skype/skype-ps/skype/Sync-CsClsLogging.md b/skype/skype-ps/skype/Sync-CsClsLogging.md index a4a262d95c..f1e1fb7909 100644 --- a/skype/skype-ps/skype/Sync-CsClsLogging.md +++ b/skype/skype-ps/skype/Sync-CsClsLogging.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/sync-csclslogging +online version: https://learn.microsoft.com/powershell/module/skype/sync-csclslogging applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Sync-CsClsLogging schema: 2.0.0 @@ -155,4 +155,3 @@ The `Sync-CsClsLogging` cmdlet does not return objects. [Stop-CsClsLogging](Stop-CsClsLogging.md) [Update-CsClsLogging](Update-CsClsLogging.md) - diff --git a/skype/skype-ps/skype/Sync-CsOnlineApplicationInstance.md b/skype/skype-ps/skype/Sync-CsOnlineApplicationInstance.md deleted file mode 100644 index 4d8a04bef1..0000000000 --- a/skype/skype-ps/skype/Sync-CsOnlineApplicationInstance.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/sync-csonlineapplicationinstance -applicable: Skype for Business Online -title: Sync-CsOnlineApplicationInstance -schema: 2.0.0 -author: xixian73 -ms.author: xixian -manager:naveenv -ms.reviewer: ---- - -# Sync-CsOnlineApplicationInstance - -## SYNOPSIS -Use the Sync-CsOnlineApplicationInstance cmdlet to sync the application instance from Azure Active Directory into Agent Provisioning Service. - -## SYNTAX - -``` -Sync-CsOnlineApplicationInstance [-ObjectId <guid>] [-Tenant <Guid>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Use the Sync-CsOnlineApplicationInstance cmdlet to sync application instances from Azure Active Directory into Agent Provisioning Service. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Sync-CsOnlineApplicationInstance -ObjectId 00000000-0000-0000-0000-000000000000 -``` - -This example sync application instance with object id "00000000-0000-0000-0000-000000000000" into Agent Provisioning Service. - -## PARAMETERS - -### -ObjectId -The application instance ID. - -```yaml -Type: System.Guid -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -Applicable: Skype for Business Online -``` - -### -Tenant -The Tenant ID. - -```yaml -Type: System.Guid -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -Applicable: Skype for Business Online -``` - -### 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/?LinkID=113216). diff --git a/skype/skype-ps/skype/Sync-CsUserData.md b/skype/skype-ps/skype/Sync-CsUserData.md index a35b68d334..24515c4190 100644 --- a/skype/skype-ps/skype/Sync-CsUserData.md +++ b/skype/skype-ps/skype/Sync-CsUserData.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/sync-csuserdata +online version: https://learn.microsoft.com/powershell/module/skype/sync-csuserdata applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Sync-CsUserData schema: 2.0.0 @@ -136,4 +136,3 @@ None. [Import-CsUserData](Import-CsUserData.md) [Update-CsUserData](Update-CsUserData.md) - diff --git a/skype/skype-ps/skype/Test-CsASConference.md b/skype/skype-ps/skype/Test-CsASConference.md index ad96df9f2a..099b932352 100644 --- a/skype/skype-ps/skype/Test-CsASConference.md +++ b/skype/skype-ps/skype/Test-CsASConference.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csasconference +online version: https://learn.microsoft.com/powershell/module/skype/test-csasconference applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsASConference schema: 2.0.0 @@ -373,4 +373,3 @@ The `Test-CsASConference` cmdlet returns an instance of the Microsoft.Rtc.Synthe [Get-CsConferencingPolicy](Get-CsConferencingPolicy.md) [Test-CsDataConference](Test-CsDataConference.md) - diff --git a/skype/skype-ps/skype/Test-CsAVConference.md b/skype/skype-ps/skype/Test-CsAVConference.md index 24652064a2..10358b7db6 100644 --- a/skype/skype-ps/skype/Test-CsAVConference.md +++ b/skype/skype-ps/skype/Test-CsAVConference.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csavconference +online version: https://learn.microsoft.com/powershell/module/skype/test-csavconference applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsAVConference schema: 2.0.0 @@ -397,4 +397,3 @@ The `Test-CsAVConference` cmdlet returns an instance of the Microsoft.Rtc.Synthe [Get-CsAVEdgeConfiguration](Get-CsAVEdgeConfiguration.md) [Test-CsDialInConferencing](Test-CsDialInConferencing.md) - diff --git a/skype/skype-ps/skype/Test-CsAVEdgeConnectivity.md b/skype/skype-ps/skype/Test-CsAVEdgeConnectivity.md index 057e0ee16f..4a02865927 100644 --- a/skype/skype-ps/skype/Test-CsAVEdgeConnectivity.md +++ b/skype/skype-ps/skype/Test-CsAVEdgeConnectivity.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csavedgeconnectivity +online version: https://learn.microsoft.com/powershell/module/skype/test-csavedgeconnectivity applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsAVEdgeConnectivity schema: 2.0.0 @@ -326,4 +326,3 @@ The `Test-CsAVEdgeConnectivity` cmdlet returns instances of the Microsoft.Rtc.Sy ## RELATED LINKS [Get-CsAVEdgeConfiguration](Get-CsAVEdgeConfiguration.md) - diff --git a/skype/skype-ps/skype/Test-CsAddressBookService.md b/skype/skype-ps/skype/Test-CsAddressBookService.md index bc8c537f3c..cd35b1f681 100644 --- a/skype/skype-ps/skype/Test-CsAddressBookService.md +++ b/skype/skype-ps/skype/Test-CsAddressBookService.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csaddressbookservice +online version: https://learn.microsoft.com/powershell/module/skype/test-csaddressbookservice applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsAddressBookService schema: 2.0.0 @@ -381,4 +381,3 @@ The `Test-CsAddressBookService` cmdlet returns an instance of the Microsoft.Rtc. [Test-CsAddressBookWebQuery](Test-CsAddressBookWebQuery.md) [Update-CsAddressBook](Update-CsAddressBook.md) - diff --git a/skype/skype-ps/skype/Test-CsAddressBookWebQuery.md b/skype/skype-ps/skype/Test-CsAddressBookWebQuery.md index 97e17acf23..6347a249c5 100644 --- a/skype/skype-ps/skype/Test-CsAddressBookWebQuery.md +++ b/skype/skype-ps/skype/Test-CsAddressBookWebQuery.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csaddressbookwebquery +online version: https://learn.microsoft.com/powershell/module/skype/test-csaddressbookwebquery applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsAddressBookWebQuery schema: 2.0.0 @@ -425,4 +425,3 @@ The `Test-CsAddressBookWebQuery` cmdlet returns an instance of the Microsoft.Rtc [Test-CsAddressBookService](Test-CsAddressBookService.md) [Update-CsAddressBook](Update-CsAddressBook.md) - diff --git a/skype/skype-ps/skype/Test-CsAudioConferencingProvider.md b/skype/skype-ps/skype/Test-CsAudioConferencingProvider.md index 630ed37db2..5c7f75a011 100644 --- a/skype/skype-ps/skype/Test-CsAudioConferencingProvider.md +++ b/skype/skype-ps/skype/Test-CsAudioConferencingProvider.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csaudioconferencingprovider +online version: https://learn.microsoft.com/powershell/module/skype/test-csaudioconferencingprovider applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsAudioConferencingProvider schema: 2.0.0 @@ -352,4 +352,3 @@ The `Test-CsAudioConferencingProvider` cmdlet returns an instance of the Microso ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsCertificateConfiguration.md b/skype/skype-ps/skype/Test-CsCertificateConfiguration.md index 34f6cb9e57..a47d84c519 100644 --- a/skype/skype-ps/skype/Test-CsCertificateConfiguration.md +++ b/skype/skype-ps/skype/Test-CsCertificateConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cscertificateconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/test-cscertificateconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsCertificateConfiguration schema: 2.0.0 @@ -106,4 +106,3 @@ The `Test-CsCertificateConfiguration` cmdlet returns instances of the Microsoft. ## RELATED LINKS [Get-CsCertificate](Get-CsCertificate.md) - diff --git a/skype/skype-ps/skype/Test-CsClientAuth.md b/skype/skype-ps/skype/Test-CsClientAuth.md index e9752e286f..6bd285963b 100644 --- a/skype/skype-ps/skype/Test-CsClientAuth.md +++ b/skype/skype-ps/skype/Test-CsClientAuth.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csclientauth +online version: https://learn.microsoft.com/powershell/module/skype/test-csclientauth applicable: Lync Server 2010 title: Test-CsClientAuth schema: 2.0.0 @@ -208,4 +208,3 @@ None. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsClientAuthentication.md b/skype/skype-ps/skype/Test-CsClientAuthentication.md index 9ab7439895..b8dd9c675a 100644 --- a/skype/skype-ps/skype/Test-CsClientAuthentication.md +++ b/skype/skype-ps/skype/Test-CsClientAuthentication.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csclientauthentication +online version: https://learn.microsoft.com/powershell/module/skype/test-csclientauthentication applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsClientAuthentication schema: 2.0.0 @@ -247,4 +247,3 @@ The `Test-CsClientAuthentication` cmdlet returns an instance of the Microsoft.Rt [Get-CsWebServiceConfiguration](Get-CsWebServiceConfiguration.md) [Test-CsRegistration](Test-CsRegistration.md) - diff --git a/skype/skype-ps/skype/Test-CsComputer.md b/skype/skype-ps/skype/Test-CsComputer.md index 228ead7f72..24f055387a 100644 --- a/skype/skype-ps/skype/Test-CsComputer.md +++ b/skype/skype-ps/skype/Test-CsComputer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cscomputer +online version: https://learn.microsoft.com/powershell/module/skype/test-cscomputer applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsComputer schema: 2.0.0 @@ -113,4 +113,3 @@ The `Test-CsComputer` cmdlet returns an instance of the Microsoft.Rtc.SyntheticT [Enable-CsComputer](Enable-CsComputer.md) [Get-CsComputer](Get-CsComputer.md) - diff --git a/skype/skype-ps/skype/Test-CsDataConference.md b/skype/skype-ps/skype/Test-CsDataConference.md index 743e8477ca..261a1b7fce 100644 --- a/skype/skype-ps/skype/Test-CsDataConference.md +++ b/skype/skype-ps/skype/Test-CsDataConference.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csdataconference +online version: https://learn.microsoft.com/powershell/module/skype/test-csdataconference applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsDataConference schema: 2.0.0 @@ -67,7 +67,7 @@ $credential2 = Get-Credential "litwareinc\kenmyer" Test-CsDataConference -TargetFqdn "atl-cs-001.litwareinc.com" -SenderSipAddress "sip:pilar@litwareinc.com" -SenderCredential $credential1 -ReceiverSipAddress "sip:kenmyer@litwareinc.com" -ReceiverCredential $credential2 ``` -The commands shown in Example 2 test the ability of a pair of users (litwareinc\pilar and litwareinc\kenmyer) to log on to Skype for Business Server and then conduct an data conference. +The commands shown in Example 2 test the ability of a pair of users (litwareinc\pilar and litwareinc\kenmyer) to log on to Skype for Business Server and then conduct a data conference. To do this, the first command in the example uses the `Get-Credential` cmdlet to create a Windows PowerShell command-line interface credential object containing the name and password of the user Pilar Ackerman. (Because the logon name, litwareinc\pilar, has been included as a parameter, the Windows PowerShell Credential Request dialog box only requires the administrator to enter the password for the Pilar Ackerman account.) The resulting credential object is then stored in a variable named $cred1. The second command does the same thing, this time returning a credential object for the Ken Myer account. @@ -395,4 +395,3 @@ The `Test-CsDataConference` cmdlet returns instances of the Microsoft.Rtc.Synthe ## RELATED LINKS [Test-CsASConference](Test-CsASConference.md) - diff --git a/skype/skype-ps/skype/Test-CsDatabase.md b/skype/skype-ps/skype/Test-CsDatabase.md index 6e143b1ce6..8d7c71703f 100644 --- a/skype/skype-ps/skype/Test-CsDatabase.md +++ b/skype/skype-ps/skype/Test-CsDatabase.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csdatabase +online version: https://learn.microsoft.com/powershell/module/skype/test-csdatabase applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsDatabase schema: 2.0.0 @@ -309,4 +309,3 @@ The `Test-CsDatabase` cmdlet returns an instance of the Microsoft.Rtc.SyntheticT [Get-CsService](Get-CsService.md) [Get-CsUserDatabaseState](Get-CsUserDatabaseState.md) - diff --git a/skype/skype-ps/skype/Test-CsDialInConferencing.md b/skype/skype-ps/skype/Test-CsDialInConferencing.md index ff1e1a8dd0..b081788241 100644 --- a/skype/skype-ps/skype/Test-CsDialInConferencing.md +++ b/skype/skype-ps/skype/Test-CsDialInConferencing.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csdialinconferencing +online version: https://learn.microsoft.com/powershell/module/skype/test-csdialinconferencing applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsDialInConferencing schema: 2.0.0 @@ -357,4 +357,3 @@ The `Test-CsDialInConferencing` cmdlet returns an instance of the Microsoft.Rtc. ## RELATED LINKS [Test-CsAVConference](Test-CsAVConference.md) - diff --git a/skype/skype-ps/skype/Test-CsDialPlan.md b/skype/skype-ps/skype/Test-CsDialPlan.md index 0f834eec29..77e180d416 100644 --- a/skype/skype-ps/skype/Test-CsDialPlan.md +++ b/skype/skype-ps/skype/Test-CsDialPlan.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csdialplan +online version: https://learn.microsoft.com/powershell/module/skype/test-csdialplan applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsDialPlan schema: 2.0.0 @@ -145,4 +145,3 @@ Returns an object of type Microsoft.Rtc.Management.Voice.LocationProfileTestResu [Get-CsDialPlan](Get-CsDialPlan.md) [Grant-CsDialPlan](Grant-CsDialPlan.md) - diff --git a/skype/skype-ps/skype/Test-CsExStorageConnectivity.md b/skype/skype-ps/skype/Test-CsExStorageConnectivity.md index acff8e4575..c2e02985e3 100644 --- a/skype/skype-ps/skype/Test-CsExStorageConnectivity.md +++ b/skype/skype-ps/skype/Test-CsExStorageConnectivity.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csexstorageconnectivity +online version: https://learn.microsoft.com/powershell/module/skype/test-csexstorageconnectivity applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsExStorageConnectivity schema: 2.0.0 @@ -209,4 +209,3 @@ The `Test-CsExStorageConnectivity` cmdlet returns instances of the Microsoft.Rtc ## RELATED LINKS [Test-CsExStorageNotification](Test-CsExStorageNotification.md) - diff --git a/skype/skype-ps/skype/Test-CsExStorageNotification.md b/skype/skype-ps/skype/Test-CsExStorageNotification.md index 4f95aa6033..0a1a1928e8 100644 --- a/skype/skype-ps/skype/Test-CsExStorageNotification.md +++ b/skype/skype-ps/skype/Test-CsExStorageNotification.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csexstoragenotification +online version: https://learn.microsoft.com/powershell/module/skype/test-csexstoragenotification applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsExStorageNotification schema: 2.0.0 @@ -151,4 +151,3 @@ The `Test-CsExStorageNotification` cmdlet returns instances of the Microsoft.Rtc ## RELATED LINKS [Test-CsExStorageConnectivity](Test-CsExStorageConnectivity.md) - diff --git a/skype/skype-ps/skype/Test-CsExUMConnectivity.md b/skype/skype-ps/skype/Test-CsExUMConnectivity.md index faf807cc92..89de2a0acc 100644 --- a/skype/skype-ps/skype/Test-CsExUMConnectivity.md +++ b/skype/skype-ps/skype/Test-CsExUMConnectivity.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csexumconnectivity +online version: https://learn.microsoft.com/powershell/module/skype/test-csexumconnectivity applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsExUMConnectivity schema: 2.0.0 @@ -302,4 +302,3 @@ The `Test-CsExUMConnectivity` cmdlet returns an instance of the Microsoft.Rtc.Sy ## RELATED LINKS [Test-CsExUMVoiceMail](Test-CsExUMVoiceMail.md) - diff --git a/skype/skype-ps/skype/Test-CsExUMVoiceMail.md b/skype/skype-ps/skype/Test-CsExUMVoiceMail.md index 01e53f398d..54fb97e64e 100644 --- a/skype/skype-ps/skype/Test-CsExUMVoiceMail.md +++ b/skype/skype-ps/skype/Test-CsExUMVoiceMail.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csexumvoicemail +online version: https://learn.microsoft.com/powershell/module/skype/test-csexumvoicemail applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsExUMVoiceMail schema: 2.0.0 @@ -190,11 +190,11 @@ Note: Do not use prepend a $ character when specifying the variable name. To save the information stored in the logger variable to an HTML file, use a command similar to this: -`$TestOutput.ToHTML() \> C:\Logs\TestOutput.html` +`$TestOutput.ToHTML() > C:\Logs\TestOutput.html` To save the information stored in the logger variable to an XML file, use a command similar to this: -`$TestOutput.ToXML() \> C:\Logs\TestOutput.xml` +`$TestOutput.ToXML() > C:\Logs\TestOutput.xml` ```yaml Type: String @@ -355,4 +355,3 @@ The `Test-CsExUMVoiceMail` cmdlet returns an instance of the Microsoft.Rtc.Synth ## RELATED LINKS [Test-CsExUMConnectivity](Test-CsExUMConnectivity.md) - diff --git a/skype/skype-ps/skype/Test-CsFederatedPartner.md b/skype/skype-ps/skype/Test-CsFederatedPartner.md index 970daaae78..91379de7a9 100644 --- a/skype/skype-ps/skype/Test-CsFederatedPartner.md +++ b/skype/skype-ps/skype/Test-CsFederatedPartner.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csfederatedpartner +online version: https://learn.microsoft.com/powershell/module/skype/test-csfederatedpartner applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsFederatedPartner schema: 2.0.0 @@ -234,4 +234,3 @@ None. ## RELATED LINKS [Get-CsAllowedDomain](Get-CsAllowedDomain.md) - diff --git a/skype/skype-ps/skype/Test-CsGroupExpansion.md b/skype/skype-ps/skype/Test-CsGroupExpansion.md index fc2db61665..857d5182b8 100644 --- a/skype/skype-ps/skype/Test-CsGroupExpansion.md +++ b/skype/skype-ps/skype/Test-CsGroupExpansion.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csgroupexpansion +online version: https://learn.microsoft.com/powershell/module/skype/test-csgroupexpansion applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsGroupExpansion schema: 2.0.0 @@ -396,4 +396,3 @@ The `Test-CsGroupExpansion` cmdlet returns an instance of the Microsoft.Rtc.Synt [Test-CsAddressBookService](Test-CsAddressBookService.md) [Test-CsAddressBookWebQuery](Test-CsAddressBookWebQuery.md) - diff --git a/skype/skype-ps/skype/Test-CsGroupIM.md b/skype/skype-ps/skype/Test-CsGroupIM.md index 7474e28833..02b1dae31c 100644 --- a/skype/skype-ps/skype/Test-CsGroupIM.md +++ b/skype/skype-ps/skype/Test-CsGroupIM.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csgroupim +online version: https://learn.microsoft.com/powershell/module/skype/test-csgroupim applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsGroupIM schema: 2.0.0 @@ -410,4 +410,3 @@ The `Test-CsGroupIM` cmdlet returns an instance of the Microsoft.Rtc.SyntheticTr ## RELATED LINKS [Test-CsIM](Test-CsIM.md) - diff --git a/skype/skype-ps/skype/Test-CsIM.md b/skype/skype-ps/skype/Test-CsIM.md index f587a41127..76029053a9 100644 --- a/skype/skype-ps/skype/Test-CsIM.md +++ b/skype/skype-ps/skype/Test-CsIM.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csim +online version: https://learn.microsoft.com/powershell/module/skype/test-csim applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsIM schema: 2.0.0 @@ -495,4 +495,3 @@ The `Test-CsIM` cmdlet returns an instance of the Microsoft.Rtc.SyntheticTransac ## RELATED LINKS [Test-CsGroupIM](Test-CsGroupIM.md) - diff --git a/skype/skype-ps/skype/Test-CsInboundBlockedNumberPattern.md b/skype/skype-ps/skype/Test-CsInboundBlockedNumberPattern.md deleted file mode 100644 index 787c15e371..0000000000 --- a/skype/skype-ps/skype/Test-CsInboundBlockedNumberPattern.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csinboundblockednumberpattern -applicable: Skype for Business Online -title: Test-CsInboundBlockedNumberPattern -author: tomkau -ms.author: tomkau -ms.reviewer: -manager: bulenteg -schema: 2.0.0 ---- - -# Test-CsInboundBlockedNumberPattern - -## SYNOPSIS - -## SYNTAX - -``` -Test-CsInboundBlockedNumberPattern -PhoneNumber <String> [-TenantId <Guid>] [-FQDN <String>] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -{{ Fill in the Description }} - -## EXAMPLES - -### Example 1 -```powershell -PS C:> {{ Add example code here }} -``` - -{{ Add example description here }} - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FQDN -{{ Fill FQDN Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneNumber -{{ Fill PhoneNumber Description }} - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -TenantId -{{ Fill TenantId Description }} - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String - -### System.Guid - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS diff --git a/skype/skype-ps/skype/Test-CsInterTrunkRouting.md b/skype/skype-ps/skype/Test-CsInterTrunkRouting.md index 6be112cae7..c0afe78bea 100644 --- a/skype/skype-ps/skype/Test-CsInterTrunkRouting.md +++ b/skype/skype-ps/skype/Test-CsInterTrunkRouting.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csintertrunkrouting +online version: https://learn.microsoft.com/powershell/module/skype/test-csintertrunkrouting applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsInterTrunkRouting schema: 2.0.0 @@ -143,4 +143,3 @@ None. [Get-CsTrunk](Get-CsTrunk.md) [Get-CsTrunkConfiguration](Get-CsTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Test-CsKerberosAccountAssignment.md b/skype/skype-ps/skype/Test-CsKerberosAccountAssignment.md index 3c4c804f96..f5ecfa9315 100644 --- a/skype/skype-ps/skype/Test-CsKerberosAccountAssignment.md +++ b/skype/skype-ps/skype/Test-CsKerberosAccountAssignment.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cskerberosaccountassignment +online version: https://learn.microsoft.com/powershell/module/skype/test-cskerberosaccountassignment applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsKerberosAccountAssignment schema: 2.0.0 @@ -120,4 +120,3 @@ The `Test-CsKerberosAccountAssignment` cmdlet does not return any objects or val [Remove-CsKerberosAccountAssignment](Remove-CsKerberosAccountAssignment.md) [Set-CsKerberosAccountAssignment](Set-CsKerberosAccountAssignment.md) - diff --git a/skype/skype-ps/skype/Test-CsLisCivicAddress.md b/skype/skype-ps/skype/Test-CsLisCivicAddress.md index cc3dc95f08..2ff376a8bc 100644 --- a/skype/skype-ps/skype/Test-CsLisCivicAddress.md +++ b/skype/skype-ps/skype/Test-CsLisCivicAddress.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csliscivicaddress +online version: https://learn.microsoft.com/powershell/module/skype/test-csliscivicaddress applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsLisCivicAddress schema: 2.0.0 @@ -311,4 +311,3 @@ This cmdlet does not return a value. ## RELATED LINKS [Get-CsLisCivicAddress](Get-CsLisCivicAddress.md) - diff --git a/skype/skype-ps/skype/Test-CsLisConfiguration.md b/skype/skype-ps/skype/Test-CsLisConfiguration.md index 3dd8ec3b69..40c2654be8 100644 --- a/skype/skype-ps/skype/Test-CsLisConfiguration.md +++ b/skype/skype-ps/skype/Test-CsLisConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cslisconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/test-cslisconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsLisConfiguration schema: 2.0.0 @@ -100,7 +100,7 @@ Test-CsLisConfiguration -TargetUri https://atl-cs-001.litwareinc.com/locationinf The first line of this example calls the `Get-Credential` cmdlet, which prompts the user for a user ID and password. This information is stored in an encrypted fashion in the variable $cred. -Line 2 tests the LIS configuration by making a call to the web service URI (https://atl-cs-001.litwareinc.com/locationinformation/lisservice.svc) based on the SIP address of the remote user (sip:kmyer@litwareinc.com), and using the credentials we obtained in line 1 by passing them to the WebCredential parameter. +Line 2 tests the LIS configuration by making a call to the web service URI (`https://atl-cs-001.litwareinc.com/locationinformation/lisservice.svc`) based on the SIP address of the remote user (sip:kmyer@litwareinc.com), and using the credentials we obtained in line 1 by passing them to the WebCredential parameter. The test will be successful if a connection can be made with the given user credentials to the LIS web service at that URI. If a location can be found that maps to the subnet IP address 192.168.0.0, the MAC address 0A-23-00-00-00-AA or the Port ID 4500 and ChassisId 0A-23-00-00-00-AA, that location address will be returned. @@ -504,4 +504,3 @@ The `Test-CsLisConfiguration` cmdlet returns an instance of the Microsoft.Rtc.Sy [Import-CsLisConfiguration](Import-CsLisConfiguration.md) [Export-CsLisConfiguration](Export-CsLisConfiguration.md) - diff --git a/skype/skype-ps/skype/Test-CsLocationPolicy.md b/skype/skype-ps/skype/Test-CsLocationPolicy.md index c09d1d445e..a4881b7d5b 100644 --- a/skype/skype-ps/skype/Test-CsLocationPolicy.md +++ b/skype/skype-ps/skype/Test-CsLocationPolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cslocationpolicy +online version: https://learn.microsoft.com/powershell/module/skype/test-cslocationpolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsLocationPolicy schema: 2.0.0 @@ -347,4 +347,3 @@ The `Test-CsLocationPolicy` cmdlet returns an instance of the Microsoft.Rtc.Synt [Set-CsHealthMonitoringConfiguration](Set-CsHealthMonitoringConfiguration.md) [Set-CsNetworkSite](Set-CsNetworkSite.md) - diff --git a/skype/skype-ps/skype/Test-CsManagementServer.md b/skype/skype-ps/skype/Test-CsManagementServer.md index 248d4db513..3f9787e03b 100644 --- a/skype/skype-ps/skype/Test-CsManagementServer.md +++ b/skype/skype-ps/skype/Test-CsManagementServer.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csmanagementserver +online version: https://learn.microsoft.com/powershell/module/skype/test-csmanagementserver applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsManagementServer schema: 2.0.0 @@ -81,4 +81,3 @@ The `Test-CsManagementServer` cmdlet returns an instance of the Microsoft.Rtc.Sy ## RELATED LINKS [Set-CsManagementServer](Set-CsManagementServer.md) - diff --git a/skype/skype-ps/skype/Test-CsMcxConference.md b/skype/skype-ps/skype/Test-CsMcxConference.md index c79b9c202e..ead7987bb7 100644 --- a/skype/skype-ps/skype/Test-CsMcxConference.md +++ b/skype/skype-ps/skype/Test-CsMcxConference.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csmcxconference -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/test-csmcxconference +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 title: Test-CsMcxConference schema: 2.0.0 manager: rogupta @@ -325,4 +325,3 @@ The `Test-CsMcxConference` cmdlet returns an instance of the Microsoft.Rtc.Synth ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsMcxP2PIM.md b/skype/skype-ps/skype/Test-CsMcxP2PIM.md index fefa5099f4..b56a148b8b 100644 --- a/skype/skype-ps/skype/Test-CsMcxP2PIM.md +++ b/skype/skype-ps/skype/Test-CsMcxP2PIM.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csmcxp2pim -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/test-csmcxp2pim +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 title: Test-CsMcxP2PIM schema: 2.0.0 manager: rogupta @@ -278,4 +278,3 @@ The `Test-CsMcxP2PIM` cmdlet returns an instance of the Microsoft.Rtc.SyntheticT ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsMcxPushNotification.md b/skype/skype-ps/skype/Test-CsMcxPushNotification.md index 5bdab7b30f..cc044294c2 100644 --- a/skype/skype-ps/skype/Test-CsMcxPushNotification.md +++ b/skype/skype-ps/skype/Test-CsMcxPushNotification.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csmcxpushnotification -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/test-csmcxpushnotification +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 title: Test-CsMcxPushNotification schema: 2.0.0 manager: rogupta @@ -170,4 +170,3 @@ The `Test-CsMcxPushNotification` cmdlet returns an instance of the Microsoft.Rtc ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsOUPermission.md b/skype/skype-ps/skype/Test-CsOUPermission.md index e75aac65b5..1dfd1ab566 100644 --- a/skype/skype-ps/skype/Test-CsOUPermission.md +++ b/skype/skype-ps/skype/Test-CsOUPermission.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csoupermission +online version: https://learn.microsoft.com/powershell/module/skype/test-csoupermission applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsOUPermission schema: 2.0.0 @@ -213,4 +213,3 @@ The `Test-CsOUPermission` cmdlet returns an instance of the Microsoft.Rtc.Synthe [Grant-CsOUPermission](Grant-CsOUPermission.md) [Revoke-CsOUPermission](Revoke-CsOUPermission.md) - diff --git a/skype/skype-ps/skype/Test-CsOnlineCarrierPortabilityIn.md b/skype/skype-ps/skype/Test-CsOnlineCarrierPortabilityIn.md deleted file mode 100644 index 74e7b80c01..0000000000 --- a/skype/skype-ps/skype/Test-CsOnlineCarrierPortabilityIn.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csonlinecarrierportabilityin -applicable: Skype for Business Online -title: Test-CsOnlineCarrierPortabilityIn -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Test-CsOnlineCarrierPortabilityIn - -## SYNOPSIS -This cmdlet is reserved for Microsoft internal use only. - - -## SYNTAX - -``` -Test-CsOnlineCarrierPortabilityIn -TelephoneNumbers <String[]> [-DomainController <Fqdn>] [-Force] [-WhatIf] - [-Confirm] [<CommonParameters>] -``` - - -## DESCRIPTION - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` - -``` - - -## PARAMETERS - -### -TelephoneNumbers -This parameter is reserved for internal Microsoft use. - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsOnlineLisCivicAddress.md b/skype/skype-ps/skype/Test-CsOnlineLisCivicAddress.md deleted file mode 100644 index 6549e9cd61..0000000000 --- a/skype/skype-ps/skype/Test-CsOnlineLisCivicAddress.md +++ /dev/null @@ -1,369 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csonlineliscivicaddress -applicable: Skype for Business Online -title: Test-CsOnlineLisCivicAddress -schema: 2.0.0 -manager: bulenteg -author: junya -ms.author: junya -ms.reviewer: ---- - -# Test-CsOnlineLisCivicAddress - - -## SYNOPSIS -Use the \`Test-CsOnlineLisCivicAddress\` cmdlet to verify that a civic address exists in the master street address guide (MSAG), and is suitable for emergency dispatch. - - -## SYNTAX - -### TestWithExistingAddr (Default) -``` -Test-CsOnlineLisCivicAddress -CivicAddressId <Guid> [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - -### TestWithNewAddr -``` -Test-CsOnlineLisCivicAddress -CompanyName <String> [-CompanyTaxId <String>] [-HouseNumber <String>] - [-HouseNumberSuffix <String>] [-StreetName <String>] [-StreetSuffix <String>] [-PostDirectional <String>] - [-PreDirectional <String>] [-City <String>] [-StateOrProvince <String>] -CountryOrRegion <String> - [-PostalCode <String>] [-Description <String>] [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] - [<CommonParameters>] -``` - - -## DESCRIPTION -The \`Test-CsOnlineLisCivicAddress\` cmdlet operates in two modes. - -Validate and report: When called along with a list of address parameters, the cmdlet will test the address and report the result. -Neither the address, nor the validation status is saved in the Location Information Service (LIS.) Use this mode to verify the address before creating it using the \`New-CsOnlineLisCivicAddress\` cmdlet. - -Validate and save: When called with only the CivicAddressId parameter specified, the cmdlet will test the address and, if validated, save the validation status in the Location Information Service (LIS.) - -The \`Test-CsOnlineLisCivicAddress\` produces three results: - -Accepted as is: The address entered (validate and report mode), or specified (validate and save mode) is valid. - -Accepted with changes: The address entered or specified would be valid with changes. -The changes required are specified in the output. - -Rejected: The address entered or specified cannot be found, and no suggested changes can be defined. -The output will contain the reason the validation failed. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Test-CsOnlineLisCivicAddress -CivicAddressId a363a9b8-1acd-41de-916a-296c7998a024 -``` - -This example tests emergency dispatch suitability for the civic address with the specified identification. - - -### -------------------------- Example 2 -------------------------- -``` -Test-CsOnlineLisCivicAddress -HouseNumber 3910 -StreetName Smith -StreetSuffix Street -PostDirectional NE -City Redmond -StateorProvince Washington -CountryOrRegion US -PostalCode 98052 -Description "Puget Sound" -CompanyName Contoso -``` - -This examples tests the emergency dispatch suitability for the civic address specified by address definition parameters. - - -## PARAMETERS - -### -CivicAddressId -Specifies the identification number of the civic address to test. -If specified, no other address definition parameters are allowed. -Civic address identities can be discovered by using the \`Get-CsOnlineLisCivicAddress\` cmdlet. - -```yaml -Type: Guid -Parameter Sets: TestWithExistingAddr -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyName -Specifies the name of your organization. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CountryOrRegion -Specifies the country or region of the civic address. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -City -Specifies the city of the civic address. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CompanyTaxId -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Specifies an administrator defined description of the civic address. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -The Force switch specifies whether to suppress warning and confirmation messages. -It can be useful in scripting to suppress interactive prompts. -If the Force switch isn't provided in the command, you're prompted for administrative input if required. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumber -Specifies the numeric portion of the civic address. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -HouseNumberSuffix -Specifies the numeric suffix of the civic address. -For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostalCode -Specifies the postal code of the civic address. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PostDirectional -Specifies the directional attribute of the civic address which follows the street name. -For example, "425 Smith Avenue NE". - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PreDirectional -Specifies the directional attribute of the civic address which precedes the street name. -For example, "425 NE Smith Avenue ". - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StateOrProvince -Specifies the state or province of the new civic address. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetName -Specifies the street name of the civic address. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StreetSuffix -Specifies a modifier of the street name of the civic address. -The street suffix will typically be something like street, avenue, way, or boulevard. - -```yaml -Type: String -Parameter Sets: TestWithNewAddr -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### The address accepts pipelined input from the \`Get-CsOnlineLisCivicAddress\` cmdlet. - -## OUTPUTS - -### None - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsOnlinePortabilityIn.md b/skype/skype-ps/skype/Test-CsOnlinePortabilityIn.md deleted file mode 100644 index 466f082f6d..0000000000 --- a/skype/skype-ps/skype/Test-CsOnlinePortabilityIn.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csonlineportabilityin -applicable: Skype for Business Online -title: Test-CsOnlinePortabilityIn -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Test-CsOnlinePortabilityIn - -## SYNOPSIS -Tests the ability to use ported phone numbers from your current service provider to Skype for Business. - -## SYNTAX - -``` -Test-CsOnlinePortabilityIn [-TelephoneNumbers <String[]>] [-TelephoneNumberRanges <String[][]>] - [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Tests the ability to use ported phone numbers from your current service provider to Skype for Business. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> -``` - -Insert descriptive text for example 1. - - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before executing the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -This parameter is reserved for Microsoft internal use only. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumberRanges -Defines a telephone number range to test. For example, let's say you want to test all of your 25 phone numbers (+1 425-555-1235 through 1259). You should enter: "+14255551234-+14255551259". - -```yaml -Type: String[][] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TelephoneNumbers -Defines a list of telephone numbers to test. For example, let's say you want to test +1 425-555-1235, +1 425-555-1245 and +1 425-555-1259. You should enter: "+14255551235,+14255551245,+14255551259". - -```yaml -Type: String[] -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsP2PAV.md b/skype/skype-ps/skype/Test-CsP2PAV.md index c1499381e0..8c3e9d9900 100644 --- a/skype/skype-ps/skype/Test-CsP2PAV.md +++ b/skype/skype-ps/skype/Test-CsP2PAV.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csp2pav +online version: https://learn.microsoft.com/powershell/module/skype/test-csp2pav applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsP2PAV schema: 2.0.0 @@ -388,4 +388,3 @@ The `Test-CsP2PAV` cmdlet returns an instance of the Microsoft.Rtc.SyntheticTran ## RELATED LINKS [Test-CsAVConference](Test-CsAVConference.md) - diff --git a/skype/skype-ps/skype/Test-CsP2PVideoInteropServerSipTrunkAV.md b/skype/skype-ps/skype/Test-CsP2PVideoInteropServerSipTrunkAV.md index 27eeb9d043..73035ead45 100644 --- a/skype/skype-ps/skype/Test-CsP2PVideoInteropServerSipTrunkAV.md +++ b/skype/skype-ps/skype/Test-CsP2PVideoInteropServerSipTrunkAV.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csp2pvideointeropserversiptrunkav +online version: https://learn.microsoft.com/powershell/module/skype/test-csp2pvideointeropserversiptrunkav applicable: Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsP2PVideoInteropServerSipTrunkAV schema: 2.0.0 @@ -298,4 +298,3 @@ None [New-CsVideoInteropServerSyntheticTransactionConfiguration](New-CsVideoInteropServerSyntheticTransactionConfiguration.md) [Remove-CsVideoInteropServerSyntheticTransactionConfiguration](Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md) - diff --git a/skype/skype-ps/skype/Test-CsPersistentChatMessage.md b/skype/skype-ps/skype/Test-CsPersistentChatMessage.md index 8d8ecba333..d670ad8f25 100644 --- a/skype/skype-ps/skype/Test-CsPersistentChatMessage.md +++ b/skype/skype-ps/skype/Test-CsPersistentChatMessage.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cspersistentchatmessage -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/test-cspersistentchatmessage +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsPersistentChatMessage schema: 2.0.0 manager: rogupta @@ -423,4 +423,3 @@ The `Test-CsPersistentChatMessage` cmdlet returns instances of the Microsoft.Rtc [New-CsPersistentChatPolicy](New-CsPersistentChatPolicy.md) [Set-CsPersistentChatPolicy](Set-CsPersistentChatPolicy.md) - diff --git a/skype/skype-ps/skype/Test-CsPhoneBootstrap.md b/skype/skype-ps/skype/Test-CsPhoneBootstrap.md index 7fa01b9e0d..d6cb06ded2 100644 --- a/skype/skype-ps/skype/Test-CsPhoneBootstrap.md +++ b/skype/skype-ps/skype/Test-CsPhoneBootstrap.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csphonebootstrap +online version: https://learn.microsoft.com/powershell/module/skype/test-csphonebootstrap applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsPhoneBootstrap schema: 2.0.0 @@ -283,4 +283,3 @@ The `Test-CsPhoneBootstrap` cmdlet returns an instance of the Microsoft.Rtc.Synt ## RELATED LINKS [Test-CsRegistration](Test-CsRegistration.md) - diff --git a/skype/skype-ps/skype/Test-CsPresence.md b/skype/skype-ps/skype/Test-CsPresence.md index f7753fd098..8a2d1f60ca 100644 --- a/skype/skype-ps/skype/Test-CsPresence.md +++ b/skype/skype-ps/skype/Test-CsPresence.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cspresence +online version: https://learn.microsoft.com/powershell/module/skype/test-cspresence applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsPresence schema: 2.0.0 @@ -406,4 +406,3 @@ The `Test-CsPresence` cmdlet returns an instance of the Microsoft.Rtc.SyntheticT ## RELATED LINKS [Test-CsRegistration](Test-CsRegistration.md) - diff --git a/skype/skype-ps/skype/Test-CsPstnOutboundCall.md b/skype/skype-ps/skype/Test-CsPstnOutboundCall.md index 7f4f305a30..dad3350baa 100644 --- a/skype/skype-ps/skype/Test-CsPstnOutboundCall.md +++ b/skype/skype-ps/skype/Test-CsPstnOutboundCall.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cspstnoutboundcall +online version: https://learn.microsoft.com/powershell/module/skype/test-cspstnoutboundcall applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsPstnOutboundCall schema: 2.0.0 @@ -358,4 +358,3 @@ The `Test-CsPstnOutboundCall` cmdlet returns an instance of the Microsoft.Rtc.Sy ## RELATED LINKS [Test-CsPstnPeerToPeerCall](Test-CsPstnPeerToPeerCall.md) - diff --git a/skype/skype-ps/skype/Test-CsPstnPeerToPeerCall.md b/skype/skype-ps/skype/Test-CsPstnPeerToPeerCall.md index 21e93d6e70..58c8bf1766 100644 --- a/skype/skype-ps/skype/Test-CsPstnPeerToPeerCall.md +++ b/skype/skype-ps/skype/Test-CsPstnPeerToPeerCall.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cspstnpeertopeercall +online version: https://learn.microsoft.com/powershell/module/skype/test-cspstnpeertopeercall applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsPstnPeerToPeerCall schema: 2.0.0 @@ -401,4 +401,3 @@ The `Test-CsPstnPeerToPeerCall` cmdlet returns an instance of the Microsoft.Rtc. ## RELATED LINKS [Test-CsPstnOutboundCall](Test-CsPstnOutboundCall.md) - diff --git a/skype/skype-ps/skype/Test-CsRegistration.md b/skype/skype-ps/skype/Test-CsRegistration.md index 2e6ef3d99f..6310aa0ec1 100644 --- a/skype/skype-ps/skype/Test-CsRegistration.md +++ b/skype/skype-ps/skype/Test-CsRegistration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csregistration +online version: https://learn.microsoft.com/powershell/module/skype/test-csregistration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsRegistration schema: 2.0.0 @@ -329,4 +329,3 @@ The `Test-CsRegistration` cmdlet returns an instance of the Microsoft.Rtc.Synthe ## RELATED LINKS [Test-CsClientAuth](Test-CsClientAuth.md) - diff --git a/skype/skype-ps/skype/Test-CsReplica.md b/skype/skype-ps/skype/Test-CsReplica.md index d5ec18f110..fa960e4ed6 100644 --- a/skype/skype-ps/skype/Test-CsReplica.md +++ b/skype/skype-ps/skype/Test-CsReplica.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csreplica +online version: https://learn.microsoft.com/powershell/module/skype/test-csreplica applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsReplica schema: 2.0.0 @@ -132,4 +132,3 @@ The `Test-CsReplica` cmdlet returns an instance of the Microsoft.Rtc.SyntheticTr ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsSetupPermission.md b/skype/skype-ps/skype/Test-CsSetupPermission.md index 2f2c7072f4..d3a68325b5 100644 --- a/skype/skype-ps/skype/Test-CsSetupPermission.md +++ b/skype/skype-ps/skype/Test-CsSetupPermission.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cssetuppermission +online version: https://learn.microsoft.com/powershell/module/skype/test-cssetuppermission applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsSetupPermission schema: 2.0.0 @@ -172,4 +172,3 @@ The `Test-CsSetupPermission` cmdlet returns an instance of the Microsoft.Rtc.Syn [Grant-CsSetupPermission](Grant-CsSetupPermission.md) [Revoke-CsSetupPermission](Revoke-CsSetupPermission.md) - diff --git a/skype/skype-ps/skype/Test-CsTopology.md b/skype/skype-ps/skype/Test-CsTopology.md index 1bc1b46019..09df3bc984 100644 --- a/skype/skype-ps/skype/Test-CsTopology.md +++ b/skype/skype-ps/skype/Test-CsTopology.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cstopology +online version: https://learn.microsoft.com/powershell/module/skype/test-cstopology applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsTopology schema: 2.0.0 @@ -178,4 +178,3 @@ The `Test-CsTopology` cmdlet returns an instance of the Microsoft.Rtc.SyntheticT [Get-CsTopology](Get-CsTopology.md) [Publish-CsTopology](Publish-CsTopology.md) - diff --git a/skype/skype-ps/skype/Test-CsTrunkConfiguration.md b/skype/skype-ps/skype/Test-CsTrunkConfiguration.md index eb6bc07484..7cbb042b1c 100644 --- a/skype/skype-ps/skype/Test-CsTrunkConfiguration.md +++ b/skype/skype-ps/skype/Test-CsTrunkConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cstrunkconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/test-cstrunkconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsTrunkConfiguration schema: 2.0.0 @@ -125,4 +125,3 @@ Returns a value of type Microsoft.Rtc.Management.Voice.TrunkConfigurationTestRes [Set-CsTrunkConfiguration](Set-CsTrunkConfiguration.md) [Get-CsTrunkConfiguration](Get-CsTrunkConfiguration.md) - diff --git a/skype/skype-ps/skype/Test-CsUcwaConference.md b/skype/skype-ps/skype/Test-CsUcwaConference.md index 0ef2f8a2bf..c94960225f 100644 --- a/skype/skype-ps/skype/Test-CsUcwaConference.md +++ b/skype/skype-ps/skype/Test-CsUcwaConference.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csucwaconference +online version: https://learn.microsoft.com/powershell/module/skype/test-csucwaconference applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsUcwaConference schema: 2.0.0 @@ -364,4 +364,3 @@ The `Test-CsUcwaConference` cmdlet returns instances of the Microsoft.Rtc.Synthe [Test-CsDataConference](Test-CsDataConference.md) [Test-CsAVConference](Test-CsAVConference.md) - diff --git a/skype/skype-ps/skype/Test-CsUnifiedContactStore.md b/skype/skype-ps/skype/Test-CsUnifiedContactStore.md index 594dadcca0..e4e5ffea71 100644 --- a/skype/skype-ps/skype/Test-CsUnifiedContactStore.md +++ b/skype/skype-ps/skype/Test-CsUnifiedContactStore.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csunifiedcontactstore +online version: https://learn.microsoft.com/powershell/module/skype/test-csunifiedcontactstore applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsUnifiedContactStore schema: 2.0.0 @@ -317,4 +317,3 @@ The `Test-CsUnifiedContactStore` cmdlet returns instances of the Microsoft.Rtc.S [New-CsUserServicesPolicy](New-CsUserServicesPolicy.md) [Set-CsUserServicesPolicy](Set-CsUserServicesPolicy.md) - diff --git a/skype/skype-ps/skype/Test-CsVoiceNormalizationRule.md b/skype/skype-ps/skype/Test-CsVoiceNormalizationRule.md index 45f5c36ef3..7506be3ac9 100644 --- a/skype/skype-ps/skype/Test-CsVoiceNormalizationRule.md +++ b/skype/skype-ps/skype/Test-CsVoiceNormalizationRule.md @@ -1,27 +1,27 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csvoicenormalizationrule -applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/test-csvoicenormalizationrule +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsVoiceNormalizationRule schema: 2.0.0 manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: rogupta +author: jenstrier +ms.author: serdars --- # Test-CsVoiceNormalizationRule ## SYNOPSIS Tests a telephone number against a voice normalization rule and returns the number after the normalization rule has been applied. -Voice normalization rules are used to convert a telephone dialing requirement (for example, you must dial 9 to access an outside line) to the E.164 phone number format used by Skype for Business Server. +Voice normalization rules are typically used to convert a telephone dialing requirement (for example, you must dial 9 to access an outside line) to the E.164 phone +number format. This cmdlet was introduced in Lync Server 2010. ## SYNTAX ``` -Test-CsVoiceNormalizationRule -DialedNumber <PhoneNumber> -NormalizationRule <NormalizationRule> [-AsJob] +Test-CsVoiceNormalizationRule -DialedNumber <PhoneNumber> -NormalizationRule <NormalizationRule> [<CommonParameters>] ``` @@ -39,7 +39,7 @@ Use this cmdlet to troubleshoot dialing issues or to verify that rules will work Get-CsVoiceNormalizationRule -Identity "global/11 digit number rule" | Test-CsVoiceNormalizationRule -DialedNumber 14255559999 ``` -This example runs a voice normalization test against the voice normalization rule with the Identity "global/11 digit number rule". +For Lync or Skype for Business Server, this example runs a voice normalization test against the voice normalization rule with the Identity "global/11 digit number rule". First the `Get-CsVoiceNormalizationRule` cmdlet is run to retrieve the rule with the Identity "global/11 digit number rule". That rule object is then piped to the `Test-CsVoiceNormalizationRule` cmdlet, where the rule is tested against the telephone number 14255559999. The output will be the DialedNumber after the voice normalization rule "global/11 digit number rule" has been applied. @@ -49,11 +49,12 @@ If this rule does not apply to the DialedNumber value (for example, if the norma ### -------------------------- Example 2 -------------------------- ``` $a = Get-CsVoiceNormalizationRule -Identity "global/11 digit number rule" - Test-CsVoiceNormalizationRule -DialedNumber 5551212 -NormalizationRule $a ``` -Example 2 is identical to Example 1 except that instead of piping the results of the Get operation directly to the Test cmdlet, the object is first stored in the variable $a and then is passed as the value to the parameter NormalizationRule to be used as the voice normalization rule against which the test will run. +For Lync or Skype for Business Server, example 2 is identical to Example 1 except that instead of piping the results of the Get operation directly to the Test cmdlet, the +object is first stored in the variable $a and then is passed as the value to the parameter NormalizationRule to be used as the voice normalization rule against which the +test will run. ### -------------------------- Example 3 -------------------------- @@ -61,11 +62,36 @@ Example 2 is identical to Example 1 except that instead of piping the results of Get-CsVoiceNormalizationRule | Test-CsVoiceNormalizationRule -DialedNumber 2065559999 ``` -This example runs a voice normalization test against all voice normalization rules defined within the Skype for Business Server deployment. -First the `Get-CsVoiceNormalizationRule` cmdlet is run (with no parameters) to retrieve all the voice normalization rules. -The collection of rules that is returned is then piped to the `Test-CsVoiceNormalizationRule` cmdlet, where each rule in the collection is tested against the telephone number 2065559999. -The output will be a list of translated numbers, one for each rule tested. -If a rule does not apply to the DialedNumber value (for example, if the normalization rule matches the pattern for an 11-digit number and you supply a 7-digit number) there will be a blank line in the list for that rule. +For Lync or Skype for Business Server, this example runs a voice normalization test against all voice normalization rules defined within the Skype for Business +Server deployment. First the `Get-CsVoiceNormalizationRule` cmdlet is run (with no parameters) to retrieve all the voice normalization rules. +The collection of rules that is returned is then piped to the `Test-CsVoiceNormalizationRule` cmdlet, where each rule in the collection is tested against the telephone +number 2065559999. The output will be a list of translated numbers, one for each rule tested. +If a rule does not apply to the DialedNumber value (for example, if the normalization rule matches the pattern for an 11-digit number and you supply a 7-digit number) there +will be a blank line in the list for that rule. + +### -------------------------- Example 4 -------------------------- +```powershell +$nr=(Get-CsTenantDialPlan -Identity dp1).NormalizationRules +$nr[0] +``` +```output +Description : +Pattern : ^(\d{4})$ +Translation : +1206555$1 +Name : nr1 +IsInternalExtension : False +``` +```powershell +Test-CsVoiceNormalizationRule -DialedNumber 1234 -NormalizationRule $nr[0] +``` +```output +TranslatedNumber +---------------- ++12065551234 +``` + +For Microsoft Teams, this example gets all the normalization rules in the tenant dial plan DP1, shows the first of these rules, and then test that rule on the +dialed number 1234. The output shows that the rule normalize the dialed number to +12065551234. ## PARAMETERS @@ -80,7 +106,7 @@ Full Data Type: Microsoft.Rtc.Management.Voice.PhoneNumber Type: PhoneNumber Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: True Position: Named @@ -92,14 +118,14 @@ Accept wildcard characters: False ### -NormalizationRule An object containing a reference to the normalization rule against which you want to test the number specified in the DialedNumber parameter. -You can retrieve voice normalization rules by calling the `Get-CsVoiceNormalizationRule` cmdlet. - +For Lync and Skype for Business Server, you can retrieve voice normalization rules by calling the `Get-CsVoiceNormalizationRule` cmdlet. +For Microsoft Teams, you can retrieve voice normalization rules by calling the `Get-CsTenantDialPlan` cmdlet. ```yaml Type: NormalizationRule Parameter Sets: (All) Aliases: -Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams Required: True Position: Named @@ -108,22 +134,6 @@ Accept pipeline input: True (ByPropertyName, ByValue) Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). diff --git a/skype/skype-ps/skype/Test-CsVoicePolicy.md b/skype/skype-ps/skype/Test-CsVoicePolicy.md index b6550b3b5a..9e26043f76 100644 --- a/skype/skype-ps/skype/Test-CsVoicePolicy.md +++ b/skype/skype-ps/skype/Test-CsVoicePolicy.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csvoicepolicy +online version: https://learn.microsoft.com/powershell/module/skype/test-csvoicepolicy applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsVoicePolicy schema: 2.0.0 @@ -165,4 +165,3 @@ Returns an object of type Microsoft.Rtc.Management.Voice.VoicePolicyTestResult. [Get-CsVoicePolicy](Get-CsVoicePolicy.md) [Grant-CsVoicePolicy](Grant-CsVoicePolicy.md) - diff --git a/skype/skype-ps/skype/Test-CsVoiceRoute.md b/skype/skype-ps/skype/Test-CsVoiceRoute.md index 318642e570..4291233efd 100644 --- a/skype/skype-ps/skype/Test-CsVoiceRoute.md +++ b/skype/skype-ps/skype/Test-CsVoiceRoute.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csvoiceroute +online version: https://learn.microsoft.com/powershell/module/skype/test-csvoiceroute applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsVoiceRoute schema: 2.0.0 @@ -169,4 +169,3 @@ Returns an object of type Microsoft.Rtc.Management.Voice.VoiceRouteTestResult. [Set-CsVoiceRoute](Set-CsVoiceRoute.md) [Get-CsVoiceRoute](Get-CsVoiceRoute.md) - diff --git a/skype/skype-ps/skype/Test-CsVoiceTestConfiguration.md b/skype/skype-ps/skype/Test-CsVoiceTestConfiguration.md index f98e41cb87..ff6c869062 100644 --- a/skype/skype-ps/skype/Test-CsVoiceTestConfiguration.md +++ b/skype/skype-ps/skype/Test-CsVoiceTestConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csvoicetestconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/test-csvoicetestconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsVoiceTestConfiguration schema: 2.0.0 @@ -265,4 +265,3 @@ This cmdlet returns an object of type Microsoft.Rtc.Management.Voice.OcsVoiceTes [Get-CsVoicePolicy](Get-CsVoicePolicy.md) [Get-CsRoutingConfiguration](Get-CsRoutingConfiguration.md) - diff --git a/skype/skype-ps/skype/Test-CsVoiceUser.md b/skype/skype-ps/skype/Test-CsVoiceUser.md index abf94a7ec7..d31c01af75 100644 --- a/skype/skype-ps/skype/Test-CsVoiceUser.md +++ b/skype/skype-ps/skype/Test-CsVoiceUser.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csvoiceuser +online version: https://learn.microsoft.com/powershell/module/skype/test-csvoiceuser applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsVoiceUser schema: 2.0.0 @@ -137,4 +137,3 @@ Returns an object of type Microsoft.Rtc.Management.Voice.OcsVoiceUserTestResult. ## RELATED LINKS [Get-CsUser](Get-CsUser.md) - diff --git a/skype/skype-ps/skype/Test-CsWatcherNodeConfiguration.md b/skype/skype-ps/skype/Test-CsWatcherNodeConfiguration.md index 52b3ddc0cd..ab6e773b6e 100644 --- a/skype/skype-ps/skype/Test-CsWatcherNodeConfiguration.md +++ b/skype/skype-ps/skype/Test-CsWatcherNodeConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cswatchernodeconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/test-cswatchernodeconfiguration applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsWatcherNodeConfiguration schema: 2.0.0 @@ -111,4 +111,3 @@ The `Test-CsWatcherNodeConfiguration` cmdlet returns an instance of the Microsof [Remove-CsWatcherNodeConfiguration](Remove-CsWatcherNodeConfiguration.md) [Set-CsWatcherNodeConfiguration](Set-CsWatcherNodeConfiguration.md) - diff --git a/skype/skype-ps/skype/Test-CsWebApp.md b/skype/skype-ps/skype/Test-CsWebApp.md index 35fff83307..fc6945a42c 100644 --- a/skype/skype-ps/skype/Test-CsWebApp.md +++ b/skype/skype-ps/skype/Test-CsWebApp.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cswebapp +online version: https://learn.microsoft.com/powershell/module/skype/test-cswebapp applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsWebApp schema: 2.0.0 @@ -415,4 +415,3 @@ The Test-CsWebApp cmdlet returns an instance of the Microsoft.Rtc.SyntheticTrans ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsWebAppAnonymous.md b/skype/skype-ps/skype/Test-CsWebAppAnonymous.md index 915b872dfc..56fef6875f 100644 --- a/skype/skype-ps/skype/Test-CsWebAppAnonymous.md +++ b/skype/skype-ps/skype/Test-CsWebAppAnonymous.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cswebappanonymous +online version: https://learn.microsoft.com/powershell/module/skype/test-cswebappanonymous applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsWebAppAnonymous schema: 2.0.0 @@ -365,4 +365,3 @@ The `Test-CsWebAppAnonymous` cmdlet returns an instance of the Microsoft.Rtc.Syn ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Test-CsWebScheduler.md b/skype/skype-ps/skype/Test-CsWebScheduler.md index c555e8cdae..8339aaae79 100644 --- a/skype/skype-ps/skype/Test-CsWebScheduler.md +++ b/skype/skype-ps/skype/Test-CsWebScheduler.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cswebscheduler +online version: https://learn.microsoft.com/powershell/module/skype/test-cswebscheduler applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsWebScheduler schema: 2.0.0 @@ -358,4 +358,3 @@ The `Test-CsWebScheduler` cmdlet returns instances of the Microsoft.Rtc.Syntheti ## RELATED LINKS [Set-CsWebServer](Set-CsWebServer.md) - diff --git a/skype/skype-ps/skype/Test-CsXmppIM.md b/skype/skype-ps/skype/Test-CsXmppIM.md index 3ea326f491..2f3d174cf0 100644 --- a/skype/skype-ps/skype/Test-CsXmppIM.md +++ b/skype/skype-ps/skype/Test-CsXmppIM.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-csxmppim -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/test-csxmppim +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Test-CsXmppIM schema: 2.0.0 manager: rogupta @@ -303,4 +303,3 @@ The `Test-CsXmppIM` cmdlet returns instances of the Microsoft.Rtc.SyntheticTrans ## RELATED LINKS [Set-CsXmppGatewayConfiguration](Set-CsXmppGatewayConfiguration.md) - diff --git a/skype/skype-ps/skype/Uninstall-CsDatabase.md b/skype/skype-ps/skype/Uninstall-CsDatabase.md index 8c77cb286c..5963d866fb 100644 --- a/skype/skype-ps/skype/Uninstall-CsDatabase.md +++ b/skype/skype-ps/skype/Uninstall-CsDatabase.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/uninstall-csdatabase +online version: https://learn.microsoft.com/powershell/module/skype/uninstall-csdatabase applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Uninstall-CsDatabase schema: 2.0.0 @@ -260,4 +260,3 @@ The `Uninstall-CsDatabase` cmdlet does not return any values or objects. ## RELATED LINKS [Install-CsDatabase](Install-CsDatabase.md) - diff --git a/skype/skype-ps/skype/Uninstall-CsMirrorDatabase.md b/skype/skype-ps/skype/Uninstall-CsMirrorDatabase.md index 78af735007..882ce126eb 100644 --- a/skype/skype-ps/skype/Uninstall-CsMirrorDatabase.md +++ b/skype/skype-ps/skype/Uninstall-CsMirrorDatabase.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/uninstall-csmirrordatabase -applicable: Lync Server 2013, Skype for Business Server 2015 +online version: https://learn.microsoft.com/powershell/module/skype/uninstall-csmirrordatabase +applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Uninstall-CsMirrorDatabase schema: 2.0.0 manager: rogupta @@ -222,4 +222,3 @@ None. [Get-CsDatabaseMirrorState](Get-CsDatabaseMirrorState.md) [Install-CsMirrorDatabase](Install-CsMirrorDatabase.md) - diff --git a/skype/skype-ps/skype/Unlock-CsClientPin.md b/skype/skype-ps/skype/Unlock-CsClientPin.md index c2107c758d..9e0e115c1e 100644 --- a/skype/skype-ps/skype/Unlock-CsClientPin.md +++ b/skype/skype-ps/skype/Unlock-CsClientPin.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/unlock-csclientpin +online version: https://learn.microsoft.com/powershell/module/skype/unlock-csclientpin applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Unlock-CsClientPin schema: 2.0.0 @@ -157,4 +157,3 @@ Instead, the cmdlet configures one or more instances of the Microsoft.Rtc.Manage [Lock-CsClientPin](Lock-CsClientPin.md) [Set-CsClientPin](Set-CsClientPin.md) - diff --git a/skype/skype-ps/skype/Unpublish-CsLisConfiguration.md b/skype/skype-ps/skype/Unpublish-CsLisConfiguration.md index ff347dba21..6b754867cf 100644 --- a/skype/skype-ps/skype/Unpublish-CsLisConfiguration.md +++ b/skype/skype-ps/skype/Unpublish-CsLisConfiguration.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/unpublish-cslisconfiguration +online version: https://learn.microsoft.com/powershell/module/skype/unpublish-cslisconfiguration applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Unpublish-CsLisConfiguration schema: 2.0.0 @@ -117,4 +117,3 @@ This cmdlet does not return a value. [Export-CsLisConfiguration](Export-CsLisConfiguration.md) [Test-CsLisConfiguration](Test-CsLisConfiguration.md) - diff --git a/skype/skype-ps/skype/Unregister-CsHybridPSTNAppliance.md b/skype/skype-ps/skype/Unregister-CsHybridPSTNAppliance.md index 2bac6082fc..458d44b4aa 100644 --- a/skype/skype-ps/skype/Unregister-CsHybridPSTNAppliance.md +++ b/skype/skype-ps/skype/Unregister-CsHybridPSTNAppliance.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/unregister-cshybridpstnappliance +online version: https://learn.microsoft.com/powershell/module/skype/unregister-cshybridpstnappliance applicable: Skype for Business Online title: Unregister-CsHybridPSTNAppliance schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Unregister-CsHybridPSTNAppliance @@ -15,11 +15,13 @@ ms.reviewer: ## SYNOPSIS Use the `Unregister-CsHybridPSTNAppliance` cmdlet to unregister a previously specified Skype for Business Cloud Connector Edition appliance. +**Note**: This cmdlet will be deprecated from Teams PowerShell Module. + ## SYNTAX ``` Unregister-CsHybridPSTNAppliance [[-Identity] <Object>] [-BypassDualWrite <Object>] [-Confirm] [-Force] - [-Instance <Object>] [-Tenant <Object>] [-WhatIf] [-AsJob] [<CommonParameters>] + [-Instance <Object>] [-Tenant <Object>] [-WhatIf] [<CommonParameters>] ``` ## DESCRIPTION @@ -159,22 +161,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). @@ -185,4 +171,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Unregister-CsOnlineDialInConferencingServiceNumber.md b/skype/skype-ps/skype/Unregister-CsOnlineDialInConferencingServiceNumber.md deleted file mode 100644 index 2d1086ee79..0000000000 --- a/skype/skype-ps/skype/Unregister-CsOnlineDialInConferencingServiceNumber.md +++ /dev/null @@ -1,211 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/unregister-csonlinedialinconferencingservicenumber -applicable: Skype for Business Online -title: Unregister-CsOnlineDialInConferencingServiceNumber -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Unregister-CsOnlineDialInConferencingServiceNumber - -## SYNOPSIS -Unassigns the previously assigned service number as default Conference Bridge number. - -## SYNTAX - -``` -Unregister-CsOnlineDialInConferencingServiceNumber [-Identity] <String> [-BridgeId <Guid>] - [-BridgeName <String>] [-Tenant <Guid>] [-TenantDomain <String>] [-RemoveDefaultServiceNumber] - [-DomainController <Fqdn>] [-Force] [<CommonParameters>] -``` - -## DESCRIPTION -Unassigns the previously assigned service number as default Conference Bridge number. - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Unregister-CsOnlineDialInConferencingServiceNumber -BridgeName "Conference Bridge" -RemoveDefaultServiceNumber 1234 -``` - -Unassigns the 1234 Service Number to the given Conference Bridge. - - -## PARAMETERS - -### -Identity -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -PARAMVALUE: ConferencingServiceNumber - -```yaml -Type: ConferencingServiceNumber -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BridgeId -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -BridgeName -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -PARAMVALUE: Fqdn - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: DC -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RemoveDefaultServiceNumber -PARAMVALUE: SwitchParameter - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -PARAMVALUE: Guid - -```yaml -Type: Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TenantDomain -PARAMVALUE: String - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS - diff --git a/skype/skype-ps/skype/Update-CsAddressBook.md b/skype/skype-ps/skype/Update-CsAddressBook.md index 850bcf9a93..3db49c7148 100644 --- a/skype/skype-ps/skype/Update-CsAddressBook.md +++ b/skype/skype-ps/skype/Update-CsAddressBook.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-csaddressbook +online version: https://learn.microsoft.com/powershell/module/skype/update-csaddressbook applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Update-CsAddressBook schema: 2.0.0 @@ -115,4 +115,3 @@ Instead, the Update-CsAddressBook cmdlet updates existing instances of the Micro [Test-CsAddressBookService](Test-CsAddressBookService.md) [Test-CsAddressBookWebQuery](Test-CsAddressBookWebQuery.md) - diff --git a/skype/skype-ps/skype/Update-CsAdminRole.md b/skype/skype-ps/skype/Update-CsAdminRole.md index 3cd90a0c2b..6b1a812753 100644 --- a/skype/skype-ps/skype/Update-CsAdminRole.md +++ b/skype/skype-ps/skype/Update-CsAdminRole.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-csadminrole -applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +online version: https://learn.microsoft.com/powershell/module/skype/update-csadminrole +applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Update-CsAdminRole schema: 2.0.0 manager: rogupta @@ -108,4 +108,3 @@ The Update-CsAdminRole cmdlet does not return any data or objects. ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Update-CsAutoAttendant.md b/skype/skype-ps/skype/Update-CsAutoAttendant.md deleted file mode 100644 index 81661a85a4..0000000000 --- a/skype/skype-ps/skype/Update-CsAutoAttendant.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-csautoattendant -applicable: Skype for Business Online -title: Update-CsAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Update-CsAutoAttendant - -## SYNOPSIS -Use Update-CsAutoAttendant cmdlet to force an update of resources associated with an Auto Attendant (AA) provisioning. - -## SYNTAX - -```powershell -Update-CsAutoAttendant -Identity <String> [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet provides a way to update the resources associated with an auto attendant configured for use in your organization. Currently, it repairs the Dial-by-Name recognition status of an auto attendant. - -Note: This cmdlet only triggers the refresh of auto attendant resources. It does not wait until all the resources have been refreshed. The last completed status of auto attendant can be retrieved using [`Get-CsAutoAttendantStatus`](Get-CsAutoAttendantStatus.md) cmdlet. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -```powershell -Update-CsAutoAttendant -Identity "6abea1cd-904b-520b-be96-1092cc096432" -``` - -In Example 1, the Update-CsAutoAttendant cmdlet is used to update all resources of an auto attendant with Identity of 6abea1cd-904b-520b-be96-1092cc096432. - -## PARAMETERS - -### -Identity -The identity for the AA whose resources are to be updated. - -```yaml -Type: System.String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### System.String -The Update-CsAutoAttendant cmdlet accepts a string as the Identity parameter. - - -## OUTPUTS - -### None - - -## NOTES - -## RELATED LINKS - -[Get-CsAutoAttendant](Get-CsAutoAttendant.md) - -[Get-CsAutoAttendantStatus](Get-CsAutoAttendantStatus.md) - -[Set-CsAutoAttendant](Set-CsAutoAttendant.md) - -[Remove-CsAutoAttendant](Remove-CsAutoAttendant.md) diff --git a/skype/skype-ps/skype/Update-CsClsLogging.md b/skype/skype-ps/skype/Update-CsClsLogging.md index 6626ed1040..1478045d95 100644 --- a/skype/skype-ps/skype/Update-CsClsLogging.md +++ b/skype/skype-ps/skype/Update-CsClsLogging.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-csclslogging +online version: https://learn.microsoft.com/powershell/module/skype/update-csclslogging applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Update-CsClsLogging schema: 2.0.0 @@ -186,4 +186,3 @@ String value. [Stop-CsClsLogging](Stop-CsClsLogging.md) [Sync-CsClsLogging](Sync-CsClsLogging.md) - diff --git a/skype/skype-ps/skype/Update-CsOrganizationalAutoAttendant.md b/skype/skype-ps/skype/Update-CsOrganizationalAutoAttendant.md deleted file mode 100644 index 090654d22f..0000000000 --- a/skype/skype-ps/skype/Update-CsOrganizationalAutoAttendant.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-csorganizationalautoattendant -applicable: Skype for Business Online -title: Update-CsOrganizationalAutoAttendant -schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: ---- - -# Update-CsOrganizationalAutoAttendant - -## SYNOPSIS -Use Update-CsOrganizationalAutoAttendant cmdlet to force an update of resources associated with an Auto Attendant (AA) provisioning. - -## SYNTAX - -``` -Update-CsOrganizationalAutoAttendant [-PrimaryUri] <Uri> [-ApplicationId <Guid>] [-Tenant <Guid>] [<CommonParameters>] -``` - -## DESCRIPTION -This cmdlet provides a way to update the resources associated with an auto attendant configured for use in your organization. Currently, it repairs the Dial-by-Name recognition status and the SIP provisioning status of an auto attendant. - -Note: This cmdlet only triggers the refresh of auto attendant resources. It does not wait until all the resources have been refreshed. The last completed status of auto attendant can be retrieved using Get-CsOrganizationalAutoAttendantStatus cmdlet. - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -Update-CsOrganizationalAutoAttendant -PrimaryUri "sip:mainoaa@contoso.com" -``` - -In Example 1, the Update-CsOrganizationalAutoAttendant cmdlet is used to update all resources of an auto attendant with Primary URI of sip:mainoaa@contoso.com. - -## PARAMETERS - -### -PrimaryUri -The Primary URI represents the SIP address of the auto attendant whose resources are to be updated. - -```yaml -Type: System.Uri -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ApplicationId -Specifies a custom application ID to use for OAAs. This parameter is reserved for Microsoft internal use only. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### String -The Update-CsOrganizationalAutoAttendant cmdlet accepts a string as the PrimaryUri parameter. - - -## OUTPUTS - -### None - - -## NOTES - -## RELATED LINKS - -[Get-CsOrganizationalAutoAttendantStatus](Get-CsOrganizationalAutoAttendantStatus.md) - diff --git a/skype/skype-ps/skype/Update-CsTenantMeetingUrl.md b/skype/skype-ps/skype/Update-CsTenantMeetingUrl.md index 272c3e9fef..03dc67a577 100644 --- a/skype/skype-ps/skype/Update-CsTenantMeetingUrl.md +++ b/skype/skype-ps/skype/Update-CsTenantMeetingUrl.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-cstenantmeetingurl +online version: https://learn.microsoft.com/powershell/module/skype/update-cstenantmeetingurl applicable: Skype for Business Online title: Update-CsTenantMeetingUrl schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Update-CsTenantMeetingUrl @@ -19,7 +19,7 @@ The updated URL uses a simpler, more standardized format that makes it easier fo ## SYNTAX ``` -Update-CsTenantMeetingUrl [-Confirm] [-Force] [-Tenant <Guid>] [-WhatIf] [-AsJob] +Update-CsTenantMeetingUrl [-Confirm] [-Force] [-Tenant <Guid>] [-WhatIf] [<CommonParameters>] ``` @@ -28,18 +28,18 @@ The `Update-CsTenantMeetingUrl` updates the Skype for Business Online meeting UR For example, suppose an organization sets up an Office 365 domain with the name contoso.onmicrosoft.com. When they do that, meetings will have URLs similar to this: -https://meet.lync.com/onmicrosoft/contoso/user1/45GZFH99 +`https://meet.lync.com/onmicrosoft/contoso/user1/45GZFH99` Now, suppose the organization undergoes some changes and decides to use the "vanity" URL litwareinc.com instead of the onmicrosoft.com URL. The organization modifies their user email addresses to use the litwareinc.com domain. However, meeting URLs will still use the old domain name: -https://meet.lync.com/contoso/user1/45GZFH99 +`https://meet.lync.com/contoso/user1/45GZFH99` To fix this problem, administrators should run the `Update-CsTenantMeetingUrl` cmdlet. That will replace the old meeting URL with a new one that features the vanity URL instead: -https://meet.lync.com/litwareinc.com/user1/37JYLP71 +`https://meet.lync.com/litwareinc.com/user1/37JYLP71` Running the `Update-CsTenantMeetingUrl` cmdlet is the only way to make this change. @@ -166,27 +166,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216). diff --git a/skype/skype-ps/skype/Update-CsUserData.md b/skype/skype-ps/skype/Update-CsUserData.md index c2ae02be50..1002d5a2b2 100644 --- a/skype/skype-ps/skype/Update-CsUserData.md +++ b/skype/skype-ps/skype/Update-CsUserData.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-csuserdata +online version: https://learn.microsoft.com/powershell/module/skype/update-csuserdata applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Update-CsUserData schema: 2.0.0 @@ -266,4 +266,3 @@ The Update-CsUserData cmdlet updates Skype for Business Server 2015 user informa [Import-CsUserData](Import-CsUserData.md) [Sync-CsUserData](Sync-CsUserData.md) - diff --git a/skype/skype-ps/skype/Update-CsUserDatabase.md b/skype/skype-ps/skype/Update-CsUserDatabase.md index eb8555e408..e4b3514b60 100644 --- a/skype/skype-ps/skype/Update-CsUserDatabase.md +++ b/skype/skype-ps/skype/Update-CsUserDatabase.md @@ -1,6 +1,6 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/update-csuserdatabase +online version: https://learn.microsoft.com/powershell/module/skype/update-csuserdatabase applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 title: Update-CsUserDatabase schema: 2.0.0 @@ -110,4 +110,3 @@ Instead, the `Update-CsUserDatabase` cmdlet updates instances of the Microsoft.R [Get-CsUserDatabaseState](Get-CsUserDatabaseState.md) [Set-CsUserDatabaseState](Set-CsUserDatabaseState.md) - diff --git a/skype/skype-ps/skype/skype.md b/skype/skype-ps/skype/skype.md index 13b91bdaae..54e242ca7d 100644 --- a/skype/skype-ps/skype/skype.md +++ b/skype/skype-ps/skype/skype.md @@ -2,7 +2,6 @@ Module Name: SkypeForBusiness Module Guid: 01dfdcd9-c48d-46a9-b09a-587ca5c4829a Help Version: 17.0.15229.2100 -Download Help Link: https://officedocs-cdn.azureedge.net/powershell/skype/ title: skype Additional Locale: de-DE,es-ES,fr-FR,it-IT,ja-JP,ko-KR,pt-BR,ru-RU,zh-CN,zh-TW de-DE Version: 17.0.15229.2100 @@ -17,3293 +16,893 @@ zh-CN Version: 17.0.15229.2100 zh-TW Version: 17.0.15229.2100 --- -# Skype for Business PowerShell +# Skype for Business Server PowerShell ## Description -The following cmdlet references are for Skype for Business and Microsoft Teams. You can find information on installing the module for Skype for Business Online here: https://docs.microsoft.com/office365/enterprise/powershell/manage-skype-for-business-online-with-office-365-powershell. If you are using Skype for Business Server then the cmdlets are available in the Skype for Business Server Management Shell and you can find information about it here: https://docs.microsoft.com/skypeforbusiness/manage/management-shell. +The following cmdlet references are for Skype for Business Server Management Shell and you can find information about it here: https://learn.microsoft.com/skypeforbusiness/manage/management-shell. -## Skype for Business Cmdlets +## Skype for Business Server Cmdlets ### [Add-CsSlaDelegates](Add-CsSlaDelegates.md) -{{Manually Enter Add-CsSlaDelegates Description Here}} - ### [Approve-CsDeviceUpdateRule](Approve-CsDeviceUpdateRule.md) -{{Manually Enter Approve-CsDeviceUpdateRule Description Here}} - ### [Backup-CsPool](Backup-CsPool.md) -{{Manually Enter Backup-CsPool Description Here}} - ### [Clear-CsDeviceUpdateFile](Clear-CsDeviceUpdateFile.md) -{{Manually Enter Clear-CsDeviceUpdateFile Description Here}} - ### [Clear-CsDeviceUpdateLog](Clear-CsDeviceUpdateLog.md) -{{Manually Enter Clear-CsDeviceUpdateLog Description Here}} - -### [Clear-CsOnlineTelephoneNumberReservation](Clear-CsOnlineTelephoneNumberReservation.md) -{{Manually Enter Clear-CsOnlineTelephoneNumberReservation Description Here}} - ### [Clear-CsPersistentChatRoom](Clear-CsPersistentChatRoom.md) -{{Manually Enter Clear-CsPersistentChatRoom Description Here}} - -### [Complete-CsCceApplianceRegistration](Complete-CsCceApplianceRegistration.md) -{{Manually Enter Complete-CsCceApplianceRegistration Description Here}} - -### [Complete-CsCceApplianceUnregistration](Complete-CsCceApplianceUnregistration.md) -{{Manually Enter Complete-CsCceApplianceUnregistration Description Here}} - ### [Convert-CsUserData](Convert-CsUserData.md) -{{Manually Enter Convert-CsUserData Description Here}} - -### [ConvertTo-JsonForPSWS](ConvertTo-JsonForPSWS.md) -{{Manually Enter ConvertTo-JsonForPSWS Description Here}} - ### [Copy-CsVoicePolicy](Copy-CsVoicePolicy.md) -{{Manually Enter Copy-CsVoicePolicy Description Here}} - ### [Debug-CsAddressBookReplication](Debug-CsAddressBookReplication.md) -{{Manually Enter Debug-CsAddressBookReplication Description Here}} - ### [Debug-CsDataConference](Debug-CsDataConference.md) -{{Manually Enter Debug-CsDataConference Description Here}} - ### [Debug-CsInterPoolReplication](Debug-CsInterPoolReplication.md) -{{Manually Enter Debug-CsInterPoolReplication Description Here}} - ### [Debug-CsIntraPoolReplication](Debug-CsIntraPoolReplication.md) -{{Manually Enter Debug-CsIntraPoolReplication Description Here}} - ### [Debug-CsLisConfiguration](Debug-CsLisConfiguration.md) -{{Manually Enter Debug-CsLisConfiguration Description Here}} - ### [Debug-CsStorageServiceFailures](Debug-CsStorageServiceFailures.md) -{{Manually Enter Debug-CsStorageServiceFailures Description Here}} - ### [Debug-CsUnifiedContactStore](Debug-CsUnifiedContactStore.md) -{{Manually Enter Debug-CsUnifiedContactStore Description Here}} - ### [Disable-CsAdDomain](Disable-CsAdDomain.md) -{{Manually Enter Disable-CsAdDomain Description Here}} - ### [Disable-CsAdForest](Disable-CsAdForest.md) -{{Manually Enter Disable-CsAdForest Description Here}} - ### [Disable-CsComputer](Disable-CsComputer.md) -{{Manually Enter Disable-CsComputer Description Here}} - ### [Disable-CsHostingProvider](Disable-CsHostingProvider.md) -{{Manually Enter Disable-CsHostingProvider Description Here}} - ### [Disable-CsMeetingRoom](Disable-CsMeetingRoom.md) -{{Manually Enter Disable-CsMeetingRoom Description Here}} - ### [Disable-CsOnlineDialInConferencingUser](Disable-CsOnlineDialInConferencingUser.md) -{{Manually Enter Disable-CsOnlineDialInConferencingUser Description Here}} - ### [Disable-CsPublicProvider](Disable-CsPublicProvider.md) -{{Manually Enter Disable-CsPublicProvider Description Here}} - ### [Disable-CsUser](Disable-CsUser.md) -{{Manually Enter Disable-CsUser Description Here}} - ### [Enable-CsAdDomain](Enable-CsAdDomain.md) -{{Manually Enter Enable-CsAdDomain Description Here}} - ### [Enable-CsAdForest](Enable-CsAdForest.md) -{{Manually Enter Enable-CsAdForest Description Here}} - ### [Enable-CsComputer](Enable-CsComputer.md) -{{Manually Enter Enable-CsComputer Description Here}} - ### [Enable-CsHostingProvider](Enable-CsHostingProvider.md) -{{Manually Enter Enable-CsHostingProvider Description Here}} - ### [Enable-CsMeetingRoom](Enable-CsMeetingRoom.md) -{{Manually Enter Enable-CsMeetingRoom Description Here}} - -### [Enable-CsOnlineDialInConferencingUser](Enable-CsOnlineDialInConferencingUser.md) -{{Manually Enter Enable-CsOnlineDialInConferencingUser Description Here}} - ### [Enable-CsPublicProvider](Enable-CsPublicProvider.md) -{{Manually Enter Enable-CsPublicProvider Description Here}} - ### [Enable-CsReplica](Enable-CsReplica.md) -{{Manually Enter Enable-CsReplica Description Here}} - ### [Enable-CsTopology](Enable-CsTopology.md) -{{Manually Enter Enable-CsTopology Description Here}} - ### [Enable-CsUser](Enable-CsUser.md) -{{Manually Enter Enable-CsUser Description Here}} - ### [Export-CsArchivingData](Export-CsArchivingData.md) -{{Manually Enter Export-CsArchivingData Description Here}} - ### [Export-CsConfiguration](Export-CsConfiguration.md) -{{Manually Enter Export-CsConfiguration Description Here}} - ### [Export-CsLisConfiguration](Export-CsLisConfiguration.md) -{{Manually Enter Export-CsLisConfiguration Description Here}} - ### [Export-CsPersistentChatData](Export-CsPersistentChatData.md) -{{Manually Enter Export-CsPersistentChatData Description Here}} - ### [Export-CsRgsConfiguration](Export-CsRgsConfiguration.md) -{{Manually Enter Export-CsRgsConfiguration Description Here}} - ### [Export-CsUserData](Export-CsUserData.md) -{{Manually Enter Export-CsUserData Description Here}} - -### [Find-CsGroup](Find-CsGroup.md) -{{Manually Enter Find-CsGroup Description Here}} - ### [Get-CsAccessEdgeConfiguration](Get-CsAccessEdgeConfiguration.md) -{{Manually Enter Get-CsAccessEdgeConfiguration Description Here}} - ### [Get-CsAdContact](Get-CsAdContact.md) -{{Manually Enter Get-CsAdContact Description Here}} - +### [Get-CsAdditionalInternalDomain](Get-CsAdditionalInternalDomain.md) ### [Get-CsAdDomain](Get-CsAdDomain.md) -{{Manually Enter Get-CsAdDomain Description Here}} - ### [Get-CsAddressBookConfiguration](Get-CsAddressBookConfiguration.md) -{{Manually Enter Get-CsAddressBookConfiguration Description Here}} - ### [Get-CsAddressBookNormalizationConfiguration](Get-CsAddressBookNormalizationConfiguration.md) -{{Manually Enter Get-CsAddressBookNormalizationConfiguration Description Here}} - ### [Get-CsAddressBookNormalizationRule](Get-CsAddressBookNormalizationRule.md) -{{Manually Enter Get-CsAddressBookNormalizationRule Description Here}} - ### [Get-CsAdForest](Get-CsAdForest.md) -{{Manually Enter Get-CsAdForest Description Here}} - ### [Get-CsAdminRole](Get-CsAdminRole.md) -{{Manually Enter Get-CsAdminRole Description Here}} - ### [Get-CsAdminRoleAssignment](Get-CsAdminRoleAssignment.md) -{{Manually Enter Get-CsAdminRoleAssignment Description Here}} - ### [Get-CsAdPrincipal](Get-CsAdPrincipal.md) -{{Manually Enter Get-CsAdPrincipal Description Here}} - ### [Get-CsAdServerSchema](Get-CsAdServerSchema.md) -{{Manually Enter Get-CsAdServerSchema Description Here}} - ### [Get-CsAdUser](Get-CsAdUser.md) -{{Manually Enter Get-CsAdUser Description Here}} - ### [Get-CsAllowedDomain](Get-CsAllowedDomain.md) -{{Manually Enter Get-CsAllowedDomain Description Here}} - ### [Get-CsAnalogDevice](Get-CsAnalogDevice.md) -{{Manually Enter Get-CsAnalogDevice Description Here}} - ### [Get-CsAnnouncement](Get-CsAnnouncement.md) -{{Manually Enter Get-CsAnnouncement Description Here}} - ### [Get-CsApplicationEndpoint](Get-CsApplicationEndpoint.md) -{{Manually Enter Get-CsApplicationEndpoint Description Here}} - ### [Get-CsArchivingConfiguration](Get-CsArchivingConfiguration.md) -{{Manually Enter Get-CsArchivingConfiguration Description Here}} - ### [Get-CsArchivingPolicy](Get-CsArchivingPolicy.md) -{{Manually Enter Get-CsArchivingPolicy Description Here}} - -### [Get-CsAudioConferencingProvider](Get-CsAudioConferencingProvider.md) -{{Manually Enter Get-CsAudioConferencingProvider Description Here}} - ### [Get-CsAudioTestServiceApplication](Get-CsAudioTestServiceApplication.md) -{{Manually Enter Get-CsAudioTestServiceApplication Description Here}} - +### [Get-CsAuthConfig](Get-CsAuthConfig.md) ### [Get-CsAutodiscoverConfiguration](Get-CsAutodiscoverConfiguration.md) -{{Manually Enter Get-CsAutodiscoverConfiguration Description Here}} - ### [Get-CsAVEdgeConfiguration](Get-CsAVEdgeConfiguration.md) -{{Manually Enter Get-CsAVEdgeConfiguration Description Here}} - ### [Get-CsBackupServiceConfiguration](Get-CsBackupServiceConfiguration.md) -{{Manually Enter Get-CsBackupServiceConfiguration Description Here}} - ### [Get-CsBackupServiceStatus](Get-CsBackupServiceStatus.md) -{{Manually Enter Get-CsBackupServiceStatus Description Here}} - ### [Get-CsBandwidthPolicyServiceConfiguration](Get-CsBandwidthPolicyServiceConfiguration.md) -{{Manually Enter Get-CsBandwidthPolicyServiceConfiguration Description Here}} - ### [Get-CsBlockedDomain](Get-CsBlockedDomain.md) -{{Manually Enter Get-CsBlockedDomain Description Here}} - -### [Get-CsBroadcastMeetingConfiguration](Get-CsBroadcastMeetingConfiguration.md) -{{Manually Enter Get-CsBroadcastMeetingConfiguration Description Here}} - -### [Get-CsBroadcastMeetingPolicy](Get-CsBroadcastMeetingPolicy.md) -{{Manually Enter Get-CsBroadcastMeetingPolicy Description Here}} - ### [Get-CsBusyOptions](Get-CsBusyOptions.md) -{{Manually Enter Get-CsBusyOptions Description Here}} - -### [Get-CsCallingLineIdentity](Get-CsCallingLineIdentity.md) -{{Manually Enter Get-CsCallingLineIdentity Description Here}} - ### [Get-CsCallParkOrbit](Get-CsCallParkOrbit.md) -{{Manually Enter Get-CsCallParkOrbit Description Here}} - ### [Get-CsCallViaWorkPolicy](Get-CsCallViaWorkPolicy.md) -{{Manually Enter Get-CsCallViaWorkPolicy Description Here}} - ### [Get-CsCdrConfiguration](Get-CsCdrConfiguration.md) -{{Manually Enter Get-CsCdrConfiguration Description Here}} - ### [Get-CsCertificate](Get-CsCertificate.md) -{{Manually Enter Get-CsCertificate Description Here}} - ### [Get-CsClientAccessLicense](Get-CsClientAccessLicense.md) -{{Manually Enter Get-CsClientAccessLicense Description Here}} - ### [Get-CsClientCertificate](Get-CsClientCertificate.md) -{{Manually Enter Get-CsClientCertificate Description Here}} - ### [Get-CsClientPinInfo](Get-CsClientPinInfo.md) -{{Manually Enter Get-CsClientPinInfo Description Here}} - ### [Get-CsClientPolicy](Get-CsClientPolicy.md) -{{Manually Enter Get-CsClientPolicy Description Here}} - ### [Get-CsClientVersionConfiguration](Get-CsClientVersionConfiguration.md) -{{Manually Enter Get-CsClientVersionConfiguration Description Here}} - ### [Get-CsClientVersionPolicy](Get-CsClientVersionPolicy.md) -{{Manually Enter Get-CsClientVersionPolicy Description Here}} - ### [Get-CsClientVersionPolicyRule](Get-CsClientVersionPolicyRule.md) -{{Manually Enter Get-CsClientVersionPolicyRule Description Here}} - -### [Get-CsCloudMeetingPolicy](Get-CsCloudMeetingPolicy.md) -{{Manually Enter Get-CsCloudMeetingPolicy Description Here}} - +### [Get-CsCloudCallDataConnector](Get-CsCloudCallDataConnector.md) +### [Get-CsCloudCallDataConnectorConfiguration](Get-CsCloudCallDataConnectorConfiguration.md) ### [Get-CsClsAgentStatus](Get-CsClsAgentStatus.md) -{{Manually Enter Get-CsClsAgentStatus Description Here}} - ### [Get-CsClsConfiguration](Get-CsClsConfiguration.md) -{{Manually Enter Get-CsClsConfiguration Description Here}} - ### [Get-CsClsRegion](Get-CsClsRegion.md) -{{Manually Enter Get-CsClsRegion Description Here}} - ### [Get-CsClsScenario](Get-CsClsScenario.md) -{{Manually Enter Get-CsClsScenario Description Here}} - ### [Get-CsClsSearchTerm](Get-CsClsSearchTerm.md) -{{Manually Enter Get-CsClsSearchTerm Description Here}} - ### [Get-CsClsSecurityGroup](Get-CsClsSecurityGroup.md) -{{Manually Enter Get-CsClsSecurityGroup Description Here}} - ### [Get-CsCommonAreaPhone](Get-CsCommonAreaPhone.md) -{{Manually Enter Get-CsCommonAreaPhone Description Here}} - ### [Get-CsComputer](Get-CsComputer.md) -{{Manually Enter Get-CsComputer Description Here}} - ### [Get-CsConferenceDirectory](Get-CsConferenceDirectory.md) -{{Manually Enter Get-CsConferenceDirectory Description Here}} - ### [Get-CsConferenceDisclaimer](Get-CsConferenceDisclaimer.md) -{{Manually Enter Get-CsConferenceDisclaimer Description Here}} - ### [Get-CsConferencingConfiguration](Get-CsConferencingConfiguration.md) -{{Manually Enter Get-CsConferencingConfiguration Description Here}} - ### [Get-CsConferencingPolicy](Get-CsConferencingPolicy.md) -{{Manually Enter Get-CsConferencingPolicy Description Here}} - ### [Get-CsConfigurationStoreLocation](Get-CsConfigurationStoreLocation.md) -{{Manually Enter Get-CsConfigurationStoreLocation Description Here}} - ### [Get-CsConversationHistoryConfiguration](Get-CsConversationHistoryConfiguration.md) -{{Manually Enter Get-CsConversationHistoryConfiguration Description Here}} - ### [Get-CsCpsConfiguration](Get-CsCpsConfiguration.md) -{{Manually Enter Get-CsCpsConfiguration Description Here}} - ### [Get-CsDatabaseMirrorState](Get-CsDatabaseMirrorState.md) -{{Manually Enter Get-CsDatabaseMirrorState Description Here}} - ### [Get-CsDeviceUpdateConfiguration](Get-CsDeviceUpdateConfiguration.md) -{{Manually Enter Get-CsDeviceUpdateConfiguration Description Here}} - ### [Get-CsDeviceUpdateRule](Get-CsDeviceUpdateRule.md) -{{Manually Enter Get-CsDeviceUpdateRule Description Here}} - ### [Get-CsDiagnosticConfiguration](Get-CsDiagnosticConfiguration.md) -{{Manually Enter Get-CsDiagnosticConfiguration Description Here}} - ### [Get-CsDiagnosticHeaderConfiguration](Get-CsDiagnosticHeaderConfiguration.md) -{{Manually Enter Get-CsDiagnosticHeaderConfiguration Description Here}} - ### [Get-CsDialInConferencingAccessNumber](Get-CsDialInConferencingAccessNumber.md) -{{Manually Enter Get-CsDialInConferencingAccessNumber Description Here}} - ### [Get-CsDialInConferencingConfiguration](Get-CsDialInConferencingConfiguration.md) -{{Manually Enter Get-CsDialInConferencingConfiguration Description Here}} - ### [Get-CsDialInConferencingDtmfConfiguration](Get-CsDialInConferencingDtmfConfiguration.md) -{{Manually Enter Get-CsDialInConferencingDtmfConfiguration Description Here}} - ### [Get-CsDialInConferencingLanguageList](Get-CsDialInConferencingLanguageList.md) -{{Manually Enter Get-CsDialInConferencingLanguageList Description Here}} - ### [Get-CsDialPlan](Get-CsDialPlan.md) -{{Manually Enter Get-CsDialPlan Description Here}} - ### [Get-CsEffectivePolicy](Get-CsEffectivePolicy.md) -{{Manually Enter Get-CsEffectivePolicy Description Here}} - -### [Get-CsEffectiveTenantDialPlan](Get-CsEffectiveTenantDialPlan.md) -{{Manually Enter Get-CsEffectiveTenantDialPlan Description Here}} - ### [Get-CsEnhancedEmergencyServiceDisclaimer](Get-CsEnhancedEmergencyServiceDisclaimer.md) -{{Manually Enter Get-CsEnhancedEmergencyServiceDisclaimer Description Here}} - ### [Get-CsExternalAccessPolicy](Get-CsExternalAccessPolicy.md) -{{Manually Enter Get-CsExternalAccessPolicy Description Here}} - -### [Get-CsExternalUserCommunicationPolicy](Get-CsExternalUserCommunicationPolicy.md) -{{Manually Enter Get-CsExternalUserCommunicationPolicy Description Here}} - ### [Get-CsExUmContact](Get-CsExUmContact.md) -{{Manually Enter Get-CsExUmContact Description Here}} - ### [Get-CsFileTransferFilterConfiguration](Get-CsFileTransferFilterConfiguration.md) -{{Manually Enter Get-CsFileTransferFilterConfiguration Description Here}} - ### [Get-CsFIPSConfiguration](Get-CsFIPSConfiguration.md) -{{Manually Enter Get-CsFIPSConfiguration Description Here}} - -### [Get-CsGraphPolicy](Get-CsGraphPolicy.md) -{{Manually Enter Get-CsGraphPolicy Description Here}} - ### [Get-CsGroupPickupUserOrbit](Get-CsGroupPickupUserOrbit.md) -{{Manually Enter Get-CsGroupPickupUserOrbit Description Here}} - ### [Get-CsHealthMonitoringConfiguration](Get-CsHealthMonitoringConfiguration.md) -{{Manually Enter Get-CsHealthMonitoringConfiguration Description Here}} - ### [Get-CsHostedVoicemailPolicy](Get-CsHostedVoicemailPolicy.md) -{{Manually Enter Get-CsHostedVoicemailPolicy Description Here}} - ### [Get-CsHostingProvider](Get-CsHostingProvider.md) -{{Manually Enter Get-CsHostingProvider Description Here}} - -### [Get-CsHuntGroup](Get-CsHuntGroup.md) -{{Manually Enter Get-CsHuntGroup Description Here}} - -### [Get-CsHuntGroupTenantInformation](Get-CsHuntGroupTenantInformation.md) -{{Manually Enter Get-CsHuntGroupTenantInformation Description Here}} - -### [Get-CsHybridMediationServer](Get-CsHybridMediationServer.md) -{{Manually Enter Get-CsHybridMediationServer Description Here}} - -### [Get-CsHybridPSTNAppliance](Get-CsHybridPSTNAppliance.md) -{{Manually Enter Get-CsHybridPSTNAppliance Description Here}} - -### [Get-CsHybridPSTNSite](Get-CsHybridPSTNSite.md) -{{Manually Enter Get-CsHybridPSTNSite Description Here}} - +### [Get-CsHybridApplicationEndpoint](Get-CsHybridApplicationEndpoint.md) ### [Get-CsImConfiguration](Get-CsImConfiguration.md) -{{Manually Enter Get-CsImConfiguration Description Here}} - ### [Get-CsImFilterConfiguration](Get-CsImFilterConfiguration.md) -{{Manually Enter Get-CsImFilterConfiguration Description Here}} - ### [Get-CsImTranslationConfiguration](Get-CsImTranslationConfiguration.md) -{{Manually Enter Get-CsImTranslationConfiguration Description Here}} - ### [Get-CsIPPhonePolicy](Get-CsIPPhonePolicy.md) -{{Manually Enter Get-CsIPPhonePolicy Description Here}} - ### [Get-CsKerberosAccountAssignment](Get-CsKerberosAccountAssignment.md) -{{Manually Enter Get-CsKerberosAccountAssignment Description Here}} - ### [Get-CsLisCivicAddress](Get-CsLisCivicAddress.md) -{{Manually Enter Get-CsLisCivicAddress Description Here}} - ### [Get-CsLisLocation](Get-CsLisLocation.md) -{{Manually Enter Get-CsLisLocation Description Here}} - ### [Get-CsLisPort](Get-CsLisPort.md) -{{Manually Enter Get-CsLisPort Description Here}} - ### [Get-CsLisServiceProvider](Get-CsLisServiceProvider.md) -{{Manually Enter Get-CsLisServiceProvider Description Here}} - ### [Get-CsLisSubnet](Get-CsLisSubnet.md) -{{Manually Enter Get-CsLisSubnet Description Here}} - ### [Get-CsLisSwitch](Get-CsLisSwitch.md) -{{Manually Enter Get-CsLisSwitch Description Here}} - ### [Get-CsLisWirelessAccessPoint](Get-CsLisWirelessAccessPoint.md) -{{Manually Enter Get-CsLisWirelessAccessPoint Description Here}} - ### [Get-CsLocationPolicy](Get-CsLocationPolicy.md) -{{Manually Enter Get-CsLocationPolicy Description Here}} - ### [Get-CsManagementConnection](Get-CsManagementConnection.md) -{{Manually Enter Get-CsManagementConnection Description Here}} - ### [Get-CsManagementStoreReplicationStatus](Get-CsManagementStoreReplicationStatus.md) -{{Manually Enter Get-CsManagementStoreReplicationStatus Description Here}} - ### [Get-CsMcxConfiguration](Get-CsMcxConfiguration.md) -{{Manually Enter Get-CsMcxConfiguration Description Here}} - ### [Get-CsMediaConfiguration](Get-CsMediaConfiguration.md) -{{Manually Enter Get-CsMediaConfiguration Description Here}} - ### [Get-CsMeetingConfiguration](Get-CsMeetingConfiguration.md) -{{Manually Enter Get-CsMeetingConfiguration Description Here}} - -### [Get-CsMeetingMigrationStatus](Get-CsMeetingMigrationStatus.md) -{{Manually Enter Get-CsMeetingMigrationStatus Description Here}} - ### [Get-CsMeetingRoom](Get-CsMeetingRoom.md) -{{Manually Enter Get-CsMeetingRoom Description Here}} - ### [Get-CsMobilityPolicy](Get-CsMobilityPolicy.md) -{{Manually Enter Get-CsMobilityPolicy Description Here}} - ### [Get-CsNetworkBandwidthPolicyProfile](Get-CsNetworkBandwidthPolicyProfile.md) -{{Manually Enter Get-CsNetworkBandwidthPolicyProfile Description Here}} - ### [Get-CsNetworkConfiguration](Get-CsNetworkConfiguration.md) -{{Manually Enter Get-CsNetworkConfiguration Description Here}} - ### [Get-CsNetworkInterface](Get-CsNetworkInterface.md) -{{Manually Enter Get-CsNetworkInterface Description Here}} - ### [Get-CsNetworkInterRegionRoute](Get-CsNetworkInterRegionRoute.md) -{{Manually Enter Get-CsNetworkInterRegionRoute Description Here}} - ### [Get-CsNetworkInterSitePolicy](Get-CsNetworkInterSitePolicy.md) -{{Manually Enter Get-CsNetworkInterSitePolicy Description Here}} - ### [Get-CsNetworkRegion](Get-CsNetworkRegion.md) -{{Manually Enter Get-CsNetworkRegion Description Here}} - ### [Get-CsNetworkRegionLink](Get-CsNetworkRegionLink.md) -{{Manually Enter Get-CsNetworkRegionLink Description Here}} - ### [Get-CsNetworkSite](Get-CsNetworkSite.md) -{{Manually Enter Get-CsNetworkSite Description Here}} - ### [Get-CsNetworkSubnet](Get-CsNetworkSubnet.md) -{{Manually Enter Get-CsNetworkSubnet Description Here}} - ### [Get-CsOAuthConfiguration](Get-CsOAuthConfiguration.md) -{{Manually Enter Get-CsOAuthConfiguration Description Here}} - ### [Get-CsOAuthServer](Get-CsOAuthServer.md) -{{Manually Enter Get-CsOAuthServer Description Here}} - -### [Get-CsOnlineApplicationEndpoint](Get-CsOnlineApplicationEndpoint.md) -{{Manually Enter Get-CsOnlineApplicationEndpoint Description Here}} - ### [Get-CsOnlineDialInConferencingBridge](Get-CsOnlineDialInConferencingBridge.md) -{{Manually Enter Get-CsOnlineDialInConferencingBridge Description Here}} - ### [Get-CsOnlineDialInConferencingLanguagesSupported](Get-CsOnlineDialInConferencingLanguagesSupported.md) -{{Manually Enter Get-CsOnlineDialInConferencingLanguagesSupported Description Here}} - -### [Get-CsOnlineDialinConferencingPolicy](Get-CsOnlineDialinConferencingPolicy.md) -{{Manually Enter Get-CsOnlineDialinConferencingPolicy Description Here}} - -### [Get-CsOnlineDialInConferencingServiceNumber](Get-CsOnlineDialInConferencingServiceNumber.md) -{{Manually Enter Get-CsOnlineDialInConferencingServiceNumber Description Here}} - -### [Get-CsOnlineDialinConferencingTenantConfiguration](Get-CsOnlineDialinConferencingTenantConfiguration.md) -{{Manually Enter Get-CsOnlineDialinConferencingTenantConfiguration Description Here}} - -### [Get-CsOnlineDialInConferencingTenantSettings](Get-CsOnlineDialInConferencingTenantSettings.md) -{{Manually Enter Get-CsOnlineDialInConferencingTenantSettings Description Here}} - -### [Get-CsOnlineDialInConferencingUser](Get-CsOnlineDialInConferencingUser.md) -{{Manually Enter Get-CsOnlineDialInConferencingUser Description Here}} - ### [Get-CsOnlineDialInConferencingUserInfo](Get-CsOnlineDialInConferencingUserInfo.md) -{{Manually Enter Get-CsOnlineDialInConferencingUserInfo Description Here}} - ### [Get-CsOnlineDialInConferencingUserState](Get-CsOnlineDialInConferencingUserState.md) -{{Manually Enter Get-CsOnlineDialInConferencingUserState Description Here}} - -### [Get-CsOnlineDialOutPolicy](Get-CsOnlineDialOutPolicy.md) -{{Manually Enter Get-CsOnlineDialOutPolicy Description Here}} - -### [Get-CsOnlineDirectoryTenant](Get-CsOnlineDirectoryTenant.md) -{{Manually Enter Get-CsOnlineDirectoryTenant Description Here}} - -### [Get-CsOnlineDirectoryTenantNumberCities](Get-CsOnlineDirectoryTenantNumberCities.md) -{{Manually Enter Get-CsOnlineDirectoryTenantNumberCities Description Here}} - -### [Get-CsOnlineEnhancedEmergencyServiceDisclaimer](Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md) -{{Manually Enter Get-CsOnlineEnhancedEmergencyServiceDisclaimer Description Here}} - -### [Get-CsOnlineLisCivicAddress](Get-CsOnlineLisCivicAddress.md) -{{Manually Enter Get-CsOnlineLisCivicAddress Description Here}} - -### [Get-CsOnlineLisLocation](Get-CsOnlineLisLocation.md) -{{Manually Enter Get-CsOnlineLisLocation Description Here}} - ### [Get-CsOnlineNumberPortInOrder](Get-CsOnlineNumberPortInOrder.md) -{{Manually Enter Get-CsOnlineNumberPortInOrder Description Here}} - ### [Get-CsOnlineNumberPortOutOrderPin](Get-CsOnlineNumberPortOutOrderPin.md) -{{Manually Enter Get-CsOnlineNumberPortOutOrderPin Description Here}} - -### [Get-CsOnlinePSTNGateway](Get-CsOnlinePSTNGateway.md) -{{Manually Enter Get-CsOnlinePSTNGateway Description Here}} - -### [Get-CsOnlineTelephoneNumber](Get-CsOnlineTelephoneNumber.md) -{{Manually Enter Get-CsOnlineTelephoneNumber Description Here}} - -### [Get-CsOnlineTelephoneNumberAvailableCount](Get-CsOnlineTelephoneNumberAvailableCount.md) -{{Manually Enter Get-CsOnlineTelephoneNumberAvailableCount Description Here}} - -### [Get-CsOnlineTelephoneNumberInventoryAreas](Get-CsOnlineTelephoneNumberInventoryAreas.md) -{{Manually Enter Get-CsOnlineTelephoneNumberInventoryAreas Description Here}} - -### [Get-CsOnlineTelephoneNumberInventoryCities](Get-CsOnlineTelephoneNumberInventoryCities.md) -{{Manually Enter Get-CsOnlineTelephoneNumberInventoryCities Description Here}} - -### [Get-CsOnlineTelephoneNumberInventoryCountries](Get-CsOnlineTelephoneNumberInventoryCountries.md) -{{Manually Enter Get-CsOnlineTelephoneNumberInventoryCountries Description Here}} - -### [Get-CsOnlineTelephoneNumberInventoryRegions](Get-CsOnlineTelephoneNumberInventoryRegions.md) -{{Manually Enter Get-CsOnlineTelephoneNumberInventoryRegions Description Here}} - -### [Get-CsOnlineTelephoneNumberInventoryTypes](Get-CsOnlineTelephoneNumberInventoryTypes.md) -{{Manually Enter Get-CsOnlineTelephoneNumberInventoryTypes Description Here}} - -### [Get-CsOnlineTelephoneNumberReservationsInformation](Get-CsOnlineTelephoneNumberReservationsInformation.md) -{{Manually Enter Get-CsOnlineTelephoneNumberReservationsInformation Description Here}} - -### [Get-CsOnlineUser](Get-CsOnlineUser.md) -{{Manually Enter Get-CsOnlineUser Description Here}} - -### [Get-CsOnlineVoicemailPolicy](Get-CsOnlineVoicemailPolicy.md) -{{Manually Enter Get-CsOnlineVoicemailPolicy Description Here}} - -### [Get-CsOnlineVoiceUser](Get-CsOnlineVoiceUser.md) -{{Manually Enter Get-CsOnlineVoiceUser Description Here}} - -### [Get-CsOrganizationalAutoAttendant](Get-CsOrganizationalAutoAttendant.md) -{{Manually Enter Get-CsOrganizationalAutoAttendant Description Here}} - -### [Get-CsOrganizationalAutoAttendantStatus](Get-CsOrganizationalAutoAttendantStatus.md) -{{Manually Enter Get-CsOrganizationalAutoAttendantStatus Description Here}} - -### [Get-CsOrganizationalAutoAttendantSupportedLanguage](Get-CsOrganizationalAutoAttendantSupportedLanguage.md) -{{Manually Enter Get-CsOrganizationalAutoAttendantSupportedLanguage Description Here}} - -### [Get-CsOrganizationalAutoAttendantSupportedTimeZone](Get-CsOrganizationalAutoAttendantSupportedTimeZone.md) -{{Manually Enter Get-CsOrganizationalAutoAttendantSupportedTimeZone Description Here}} - -### [Get-CsOrganizationalAutoAttendantTenantInformation](Get-CsOrganizationalAutoAttendantTenantInformation.md) -{{Manually Enter Get-CsOrganizationalAutoAttendantTenantInformation Description Here}} - ### [Get-CsOutboundCallingNumberTranslationRule](Get-CsOutboundCallingNumberTranslationRule.md) -{{Manually Enter Get-CsOutboundCallingNumberTranslationRule Description Here}} - ### [Get-CsOutboundTranslationRule](Get-CsOutboundTranslationRule.md) -{{Manually Enter Get-CsOutboundTranslationRule Description Here}} - ### [Get-CsPartnerApplication](Get-CsPartnerApplication.md) -{{Manually Enter Get-CsPartnerApplication Description Here}} - ### [Get-CsPersistentChatAddin](Get-CsPersistentChatAddin.md) -{{Manually Enter Get-CsPersistentChatAddin Description Here}} - ### [Get-CsPersistentChatCategory](Get-CsPersistentChatCategory.md) -{{Manually Enter Get-CsPersistentChatCategory Description Here}} - ### [Get-CsPersistentChatComplianceConfiguration](Get-CsPersistentChatComplianceConfiguration.md) -{{Manually Enter Get-CsPersistentChatComplianceConfiguration Description Here}} - ### [Get-CsPersistentChatConfiguration](Get-CsPersistentChatConfiguration.md) -{{Manually Enter Get-CsPersistentChatConfiguration Description Here}} - ### [Get-CsPersistentChatEligiblePrincipal](Get-CsPersistentChatEligiblePrincipal.md) -{{Manually Enter Get-CsPersistentChatEligiblePrincipal Description Here}} - ### [Get-CsPersistentChatEndpoint](Get-CsPersistentChatEndpoint.md) -{{Manually Enter Get-CsPersistentChatEndpoint Description Here}} - ### [Get-CsPersistentChatPolicy](Get-CsPersistentChatPolicy.md) -{{Manually Enter Get-CsPersistentChatPolicy Description Here}} - ### [Get-CsPersistentChatRoom](Get-CsPersistentChatRoom.md) -{{Manually Enter Get-CsPersistentChatRoom Description Here}} - ### [Get-CsPersistentChatState](Get-CsPersistentChatState.md) -{{Manually Enter Get-CsPersistentChatState Description Here}} - ### [Get-CsPinPolicy](Get-CsPinPolicy.md) -{{Manually Enter Get-CsPinPolicy Description Here}} - +### [Get-CsPlatformServiceSettings](Get-CsPlatformServiceSettings.md) ### [Get-CsPool](Get-CsPool.md) -{{Manually Enter Get-CsPool Description Here}} - ### [Get-CsPoolBackupRelationship](Get-CsPoolBackupRelationship.md) -{{Manually Enter Get-CsPoolBackupRelationship Description Here}} - ### [Get-CsPoolFabricState](Get-CsPoolFabricState.md) -{{Manually Enter Get-CsPoolFabricState Description Here}} - ### [Get-CsPoolUpgradeReadinessState](Get-CsPoolUpgradeReadinessState.md) -{{Manually Enter Get-CsPoolUpgradeReadinessState Description Here}} - ### [Get-CsPresenceManagementState](Get-CsPresenceManagementState.md) -{{Manually Enter Get-CsPresenceManagementState Description Here}} - ### [Get-CsPresencePolicy](Get-CsPresencePolicy.md) -{{Manually Enter Get-CsPresencePolicy Description Here}} - ### [Get-CsPresenceProvider](Get-CsPresenceProvider.md) -{{Manually Enter Get-CsPresenceProvider Description Here}} - ### [Get-CsPrivacyConfiguration](Get-CsPrivacyConfiguration.md) -{{Manually Enter Get-CsPrivacyConfiguration Description Here}} - ### [Get-CsProxyConfiguration](Get-CsProxyConfiguration.md) -{{Manually Enter Get-CsProxyConfiguration Description Here}} - ### [Get-CsPstnUsage](Get-CsPstnUsage.md) -{{Manually Enter Get-CsPstnUsage Description Here}} - ### [Get-CsPublicProvider](Get-CsPublicProvider.md) -{{Manually Enter Get-CsPublicProvider Description Here}} - ### [Get-CsPushNotificationConfiguration](Get-CsPushNotificationConfiguration.md) -{{Manually Enter Get-CsPushNotificationConfiguration Description Here}} - ### [Get-CsQoEConfiguration](Get-CsQoEConfiguration.md) -{{Manually Enter Get-CsQoEConfiguration Description Here}} - ### [Get-CsRegistrarConfiguration](Get-CsRegistrarConfiguration.md) -{{Manually Enter Get-CsRegistrarConfiguration Description Here}} - ### [Get-CsReportingConfiguration](Get-CsReportingConfiguration.md) -{{Manually Enter Get-CsReportingConfiguration Description Here}} - ### [Get-CsRgsAgentGroup](Get-CsRgsAgentGroup.md) -{{Manually Enter Get-CsRgsAgentGroup Description Here}} - ### [Get-CsRgsConfiguration](Get-CsRgsConfiguration.md) -{{Manually Enter Get-CsRgsConfiguration Description Here}} - ### [Get-CsRgsHolidaySet](Get-CsRgsHolidaySet.md) -{{Manually Enter Get-CsRgsHolidaySet Description Here}} - ### [Get-CsRgsHoursOfBusiness](Get-CsRgsHoursOfBusiness.md) -{{Manually Enter Get-CsRgsHoursOfBusiness Description Here}} - ### [Get-CsRgsQueue](Get-CsRgsQueue.md) -{{Manually Enter Get-CsRgsQueue Description Here}} - ### [Get-CsRgsWorkflow](Get-CsRgsWorkflow.md) -{{Manually Enter Get-CsRgsWorkflow Description Here}} - ### [Get-CsRoutingConfiguration](Get-CsRoutingConfiguration.md) -{{Manually Enter Get-CsRoutingConfiguration Description Here}} - ### [Get-CsServerApplication](Get-CsServerApplication.md) -{{Manually Enter Get-CsServerApplication Description Here}} - ### [Get-CsServerPatchVersion](Get-CsServerPatchVersion.md) -{{Manually Enter Get-CsServerPatchVersion Description Here}} - ### [Get-CsServerVersion](Get-CsServerVersion.md) -{{Manually Enter Get-CsServerVersion Description Here}} - ### [Get-CsService](Get-CsService.md) -{{Manually Enter Get-CsService Description Here}} - ### [Get-CsSimpleUrlConfiguration](Get-CsSimpleUrlConfiguration.md) -{{Manually Enter Get-CsSimpleUrlConfiguration Description Here}} - ### [Get-CsSipDomain](Get-CsSipDomain.md) -{{Manually Enter Get-CsSipDomain Description Here}} - ### [Get-CsSipResponseCodeTranslationRule](Get-CsSipResponseCodeTranslationRule.md) -{{Manually Enter Get-CsSipResponseCodeTranslationRule Description Here}} - ### [Get-CsSite](Get-CsSite.md) -{{Manually Enter Get-CsSite Description Here}} - ### [Get-CsSlaConfiguration](Get-CsSlaConfiguration.md) -{{Manually Enter Get-CsSlaConfiguration Description Here}} - ### [Get-CsStaticRoutingConfiguration](Get-CsStaticRoutingConfiguration.md) -{{Manually Enter Get-CsStaticRoutingConfiguration Description Here}} - ### [Get-CsStorageServiceConfiguration](Get-CsStorageServiceConfiguration.md) -{{Manually Enter Get-CsStorageServiceConfiguration Description Here}} - -### [Get-CsTeamsCallingPolicy](Get-CsTeamsCallingPolicy.md) -{{Manually Enter Get-CsTeamsCallingPolicy Description Here}} - -### [Get-CsTeamsMobilityPolicy](Get-CsTeamsMobilityPolicy.md) -{{Manually Enter Get-CsTeamsMobilityPolicy Description Here}} - -### [Get-CsTeamsMeetingPolicy](Get-CsTeamsMeetingPolicy.md) -{{Manually Enter Get-CsTeamsMeetingPolicy Description Here}} - +### [Get-CsTeamsUpgradeConfiguration](Get-CsTeamsUpgradeConfiguration.md) +### [Get-CsTeamsUpgradePolicy](Get-CsTeamsUpgradePolicy.md) ### [Get-CsTelemetryConfiguration](Get-CsTelemetryConfiguration.md) -{{Manually Enter Get-CsTelemetryConfiguration Description Here}} - -### [Get-CsTenant](Get-CsTenant.md) -{{Manually Enter Get-CsTenant Description Here}} - -### [Get-CsTenantDialPlan](Get-CsTenantDialPlan.md) -{{Manually Enter Get-CsTenantDialPlan Description Here}} - -### [Get-CsTenantFederationConfiguration](Get-CsTenantFederationConfiguration.md) -{{Manually Enter Get-CsTenantFederationConfiguration Description Here}} - ### [Get-CsTenantHybridConfiguration](Get-CsTenantHybridConfiguration.md) -{{Manually Enter Get-CsTenantHybridConfiguration Description Here}} - -### [Get-CsTenantLicensingConfiguration](Get-CsTenantLicensingConfiguration.md) -{{Manually Enter Get-CsTenantLicensingConfiguration Description Here}} - -### [Get-CsTenantMigrationConfiguration](Get-CsTenantMigrationConfiguration.md) -{{Manually Enter Get-CsTenantMigrationConfiguration Description Here}} - -### [Get-CsTenantNetworkRegion](Get-CsTenantNetworkRegion.md) -{{Manually Enter Get-CsTenantNetworkRegion Description Here}} - -### [Get-CsTenantNetworkSite](Get-CsTenantNetworkSite.md) -{{Manually Enter Get-CsTenantNetworkSite Description Here}} - -### [Get-CsTenantNetworkSubnet](Get-CsTenantNetworkSubnet.md) -{{Manually Enter Get-CsTenantNetworkSubnet Description Here}} - -### [Get-CsTenantPublicProvider](Get-CsTenantPublicProvider.md) -{{Manually Enter Get-CsTenantPublicProvider Description Here}} - -### [Get-CsTenantTrustedIPAddress](Get-CsTenantTrustedIPAddress.md) -{{Manually Enter Get-CsTenantTrustedIPAddress Description Here}} - -### [Get-CsTenantUpdateTimeWindow](Get-CsTenantUpdateTimeWindow.md) -{{Manually Enter Get-CsTenantUpdateTimeWindow Description Here}} - ### [Get-CsTestDevice](Get-CsTestDevice.md) -{{Manually Enter Get-CsTestDevice Description Here}} - ### [Get-CsTestUserCredential](Get-CsTestUserCredential.md) -{{Manually Enter Get-CsTestUserCredential Description Here}} - ### [Get-CsThirdPartyVideoSystem](Get-CsThirdPartyVideoSystem.md) -{{Manually Enter Get-CsThirdPartyVideoSystem Description Here}} - ### [Get-CsThirdPartyVideoSystemPolicy](Get-CsThirdPartyVideoSystemPolicy.md) -{{Manually Enter Get-CsThirdPartyVideoSystemPolicy Description Here}} - ### [Get-CsTopology](Get-CsTopology.md) -{{Manually Enter Get-CsTopology Description Here}} - ### [Get-CsTrunk](Get-CsTrunk.md) -{{Manually Enter Get-CsTrunk Description Here}} - ### [Get-CsTrunkConfiguration](Get-CsTrunkConfiguration.md) -{{Manually Enter Get-CsTrunkConfiguration Description Here}} - ### [Get-CsTrustedApplication](Get-CsTrustedApplication.md) -{{Manually Enter Get-CsTrustedApplication Description Here}} - ### [Get-CsTrustedApplicationComputer](Get-CsTrustedApplicationComputer.md) -{{Manually Enter Get-CsTrustedApplicationComputer Description Here}} - ### [Get-CsTrustedApplicationEndpoint](Get-CsTrustedApplicationEndpoint.md) -{{Manually Enter Get-CsTrustedApplicationEndpoint Description Here}} - ### [Get-CsTrustedApplicationPool](Get-CsTrustedApplicationPool.md) -{{Manually Enter Get-CsTrustedApplicationPool Description Here}} - ### [Get-CsUCPhoneConfiguration](Get-CsUCPhoneConfiguration.md) -{{Manually Enter Get-CsUCPhoneConfiguration Description Here}} - ### [Get-CsUICulture](Get-CsUICulture.md) -{{Manually Enter Get-CsUICulture Description Here}} - ### [Get-CsUnassignedNumber](Get-CsUnassignedNumber.md) -{{Manually Enter Get-CsUnassignedNumber Description Here}} - +### [Get-CsUpgradeDomainInfo](Get-CsUpgradeDomainInfo.md) ### [Get-CsUser](Get-CsUser.md) -{{Manually Enter Get-CsUser Description Here}} - ### [Get-CsUserAcp](Get-CsUserAcp.md) -{{Manually Enter Get-CsUserAcp Description Here}} - ### [Get-CsUserCallForwardingSettings](Get-CsUserCallForwardingSettings.md) -{{Manually Enter Get-CsUserCallForwardingSettings Description Here}} - ### [Get-CsUserDatabaseState](Get-CsUserDatabaseState.md) -{{Manually Enter Get-CsUserDatabaseState Description Here}} - ### [Get-CsUserDelegates](Get-CsUserDelegates.md) -{{Manually Enter Get-CsUserDelegates Description Here}} - -### [Get-CsUserLocationStatus](Get-CsUserLocationStatus.md) -{{Manually Enter Get-CsUserLocationStatus Description Here}} - ### [Get-CsUserPoolInfo](Get-CsUserPoolInfo.md) -{{Manually Enter Get-CsUserPoolInfo Description Here}} - -### [Get-CsUserPstnSettings](Get-CsUserPstnSettings.md) -{{Manually Enter Get-CsUserPstnSettings Description Here}} - ### [Get-CsUserReplicatorConfiguration](Get-CsUserReplicatorConfiguration.md) -{{Manually Enter Get-CsUserReplicatorConfiguration Description Here}} - ### [Get-CsUserServicesConfiguration](Get-CsUserServicesConfiguration.md) -{{Manually Enter Get-CsUserServicesConfiguration Description Here}} - ### [Get-CsUserServicesPolicy](Get-CsUserServicesPolicy.md) -{{Manually Enter Get-CsUserServicesPolicy Description Here}} - -### [Get-CsUserSession](Get-CsUserSession.md) -{{Manually Enter Get-CsUserSession Description Here}} - +### [Get-CsUserSettingsPageConfiguration](Get-CsUserSettingsPageConfiguration.md) ### [Get-CsUserTeamMembers](Get-CsUserTeamMembers.md) -{{Manually Enter Get-CsUserTeamMembers Description Here}} - ### [Get-CsVideoInteropServerConfiguration](Get-CsVideoInteropServerConfiguration.md) -{{Manually Enter Get-CsVideoInteropServerConfiguration Description Here}} - ### [Get-CsVideoInteropServerSyntheticTransactionConfiguration](Get-CsVideoInteropServerSyntheticTransactionConfiguration.md) -{{Manually Enter Get-CsVideoInteropServerSyntheticTransactionConfiguration Description Here}} - ### [Get-CsVideoTrunk](Get-CsVideoTrunk.md) -{{Manually Enter Get-CsVideoTrunk Description Here}} - ### [Get-CsVideoTrunkConfiguration](Get-CsVideoTrunkConfiguration.md) -{{Manually Enter Get-CsVideoTrunkConfiguration Description Here}} - ### [Get-CsVoiceConfiguration](Get-CsVoiceConfiguration.md) -{{Manually Enter Get-CsVoiceConfiguration Description Here}} - ### [Get-CsVoicemailReroutingConfiguration](Get-CsVoicemailReroutingConfiguration.md) -{{Manually Enter Get-CsVoicemailReroutingConfiguration Description Here}} - ### [Get-CsVoiceNormalizationRule](Get-CsVoiceNormalizationRule.md) -{{Manually Enter Get-CsVoiceNormalizationRule Description Here}} - ### [Get-CsVoicePolicy](Get-CsVoicePolicy.md) -{{Manually Enter Get-CsVoicePolicy Description Here}} - ### [Get-CsVoiceRoute](Get-CsVoiceRoute.md) -{{Manually Enter Get-CsVoiceRoute Description Here}} - ### [Get-CsVoiceRoutingPolicy](Get-CsVoiceRoutingPolicy.md) -{{Manually Enter Get-CsVoiceRoutingPolicy Description Here}} - ### [Get-CsVoiceTestConfiguration](Get-CsVoiceTestConfiguration.md) -{{Manually Enter Get-CsVoiceTestConfiguration Description Here}} - ### [Get-CsWatcherNodeConfiguration](Get-CsWatcherNodeConfiguration.md) -{{Manually Enter Get-CsWatcherNodeConfiguration Description Here}} - ### [Get-CsWebServiceConfiguration](Get-CsWebServiceConfiguration.md) -{{Manually Enter Get-CsWebServiceConfiguration Description Here}} - ### [Get-CsWindowsService](Get-CsWindowsService.md) -{{Manually Enter Get-CsWindowsService Description Here}} - ### [Get-CsXmppAllowedPartner](Get-CsXmppAllowedPartner.md) -{{Manually Enter Get-CsXmppAllowedPartner Description Here}} - ### [Get-CsXmppGatewayConfiguration](Get-CsXmppGatewayConfiguration.md) -{{Manually Enter Get-CsXmppGatewayConfiguration Description Here}} - ### [Grant-CsArchivingPolicy](Grant-CsArchivingPolicy.md) -{{Manually Enter Grant-CsArchivingPolicy Description Here}} - -### [Grant-CsBroadcastMeetingPolicy](Grant-CsBroadcastMeetingPolicy.md) -{{Manually Enter Grant-CsBroadcastMeetingPolicy Description Here}} - -### [Grant-CsCallingLineIdentity](Grant-CsCallingLineIdentity.md) -{{Manually Enter Grant-CsCallingLineIdentity Description Here}} - ### [Grant-CsCallViaWorkPolicy](Grant-CsCallViaWorkPolicy.md) -{{Manually Enter Grant-CsCallViaWorkPolicy Description Here}} - ### [Grant-CsClientPolicy](Grant-CsClientPolicy.md) -{{Manually Enter Grant-CsClientPolicy Description Here}} - ### [Grant-CsClientVersionPolicy](Grant-CsClientVersionPolicy.md) -{{Manually Enter Grant-CsClientVersionPolicy Description Here}} - -### [Grant-CsCloudMeetingPolicy](Grant-CsCloudMeetingPolicy.md) -{{Manually Enter Grant-CsCloudMeetingPolicy Description Here}} - ### [Grant-CsConferencingPolicy](Grant-CsConferencingPolicy.md) -{{Manually Enter Grant-CsConferencingPolicy Description Here}} - -### [Grant-CsDialoutPolicy](Grant-CsDialoutPolicy.md) -{{Manually Enter Grant-CsDialoutPolicy Description Here}} - ### [Grant-CsDialPlan](Grant-CsDialPlan.md) -{{Manually Enter Grant-CsDialPlan Description Here}} - ### [Grant-CsExternalAccessPolicy](Grant-CsExternalAccessPolicy.md) -{{Manually Enter Grant-CsExternalAccessPolicy Description Here}} - -### [Grant-CsExternalUserCommunicationPolicy](Grant-CsExternalUserCommunicationPolicy.md) -{{Manually Enter Grant-CsExternalUserCommunicationPolicy Description Here}} - -### [Grant-CsGraphPolicy](Grant-CsGraphPolicy.md) -{{Manually Enter Grant-CsGraphPolicy Description Here}} - ### [Grant-CsHostedVoicemailPolicy](Grant-CsHostedVoicemailPolicy.md) -{{Manually Enter Grant-CsHostedVoicemailPolicy Description Here}} - ### [Grant-CsIPPhonePolicy](Grant-CsIPPhonePolicy.md) -{{Manually Enter Grant-CsIPPhonePolicy Description Here}} - ### [Grant-CsLocationPolicy](Grant-CsLocationPolicy.md) -{{Manually Enter Grant-CsLocationPolicy Description Here}} - ### [Grant-CsMobilityPolicy](Grant-CsMobilityPolicy.md) -{{Manually Enter Grant-CsMobilityPolicy Description Here}} - -### [Grant-CsOnlineVoicemailPolicy](Grant-CsOnlineVoicemailPolicy.md) -{{Manually Enter Grant-CsOnlineVoicemailPolicy Description Here}} - ### [Grant-CsOUPermission](Grant-CsOUPermission.md) -{{Manually Enter Grant-CsOUPermission Description Here}} - ### [Grant-CsPersistentChatPolicy](Grant-CsPersistentChatPolicy.md) -{{Manually Enter Grant-CsPersistentChatPolicy Description Here}} - ### [Grant-CsPinPolicy](Grant-CsPinPolicy.md) -{{Manually Enter Grant-CsPinPolicy Description Here}} - ### [Grant-CsPresencePolicy](Grant-CsPresencePolicy.md) -{{Manually Enter Grant-CsPresencePolicy Description Here}} - ### [Grant-CsSetupPermission](Grant-CsSetupPermission.md) -{{Manually Enter Grant-CsSetupPermission Description Here}} - -### [Grant-CsTeamsCallingPolicy](Grant-CsTeamsCallingPolicy.md) -{{Manually Enter Grant-CsTeamsCallingPolicy Description Here}} - -### [Grant-CsTeamsMobilityPolicy](Grant-CsTeamsMobilityPolicy.md) -{{Manually Enter Grant-CsTeamsMobilityPolicy Description Here}} - -### [Grant-CsTeamsEmergencyCallingPolicy](Grant-CsTeamsEmergencyCallingPolicy.md) -{{Manually Enter Grant-CsTeamsEmergencyCallingPolicy Description Here}} - -### [Grant-CsTeamsEmergencyCallRoutingPolicy](Grant-CsTeamsEmergencyCallRoutingPolicy.md) -{{Manually Enter Grant-CsTeamsEmergencyCallRoutingPolicy Description Here}} - -### [Grant-CsTeamsMeetingPolicy](Grant-CsTeamsMeetingPolicy.md) -{{Manually Enter Grant-CsTeamsMeetingPolicy Description Here}} - -### [Grant-CsTenantDialPlan](Grant-CsTenantDialPlan.md) -{{Manually Enter Grant-CsTenantDialPlan Description Here}} - +### [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) ### [Grant-CsThirdPartyVideoSystemPolicy](Grant-CsThirdPartyVideoSystemPolicy.md) -{{Manually Enter Grant-CsThirdPartyVideoSystemPolicy Description Here}} - ### [Grant-CsUserServicesPolicy](Grant-CsUserServicesPolicy.md) -{{Manually Enter Grant-CsUserServicesPolicy Description Here}} - ### [Grant-CsVoicePolicy](Grant-CsVoicePolicy.md) -{{Manually Enter Grant-CsVoicePolicy Description Here}} - ### [Grant-CsVoiceRoutingPolicy](Grant-CsVoiceRoutingPolicy.md) -{{Manually Enter Grant-CsVoiceRoutingPolicy Description Here}} - ### [Import-CSAnnouncementFile](Import-CSAnnouncementFile.md) -{{Manually Enter Import-CSAnnouncementFile Description Here}} - ### [Import-CsCertificate](Import-CsCertificate.md) -{{Manually Enter Import-CsCertificate Description Here}} - ### [Import-CsCompanyPhoneNormalizationRules](Import-CsCompanyPhoneNormalizationRules.md) -{{Manually Enter Import-CsCompanyPhoneNormalizationRules Description Here}} - ### [Import-CsConfiguration](Import-CsConfiguration.md) -{{Manually Enter Import-CsConfiguration Description Here}} - ### [Import-CsDeviceUpdate](Import-CsDeviceUpdate.md) -{{Manually Enter Import-CsDeviceUpdate Description Here}} - ### [Import-CsLegacyConferenceDirectory](Import-CsLegacyConferenceDirectory.md) -{{Manually Enter Import-CsLegacyConferenceDirectory Description Here}} - ### [Import-CsLegacyConfiguration](Import-CsLegacyConfiguration.md) -{{Manually Enter Import-CsLegacyConfiguration Description Here}} - ### [Import-CsLisConfiguration](Import-CsLisConfiguration.md) -{{Manually Enter Import-CsLisConfiguration Description Here}} - ### [Import-CsPersistentChatData](Import-CsPersistentChatData.md) -{{Manually Enter Import-CsPersistentChatData Description Here}} - ### [Import-CsRgsAudioFile](Import-CsRgsAudioFile.md) -{{Manually Enter Import-CsRgsAudioFile Description Here}} - ### [Import-CsRgsConfiguration](Import-CsRgsConfiguration.md) -{{Manually Enter Import-CsRgsConfiguration Description Here}} - ### [Import-CsUserData](Import-CsUserData.md) -{{Manually Enter Import-CsUserData Description Here}} - ### [Install-CsAdServerSchema](Install-CsAdServerSchema.md) -{{Manually Enter Install-CsAdServerSchema Description Here}} - ### [Install-CsDatabase](Install-CsDatabase.md) -{{Manually Enter Install-CsDatabase Description Here}} - ### [Install-CsMirrorDatabase](Install-CsMirrorDatabase.md) -{{Manually Enter Install-CsMirrorDatabase Description Here}} - ### [Invoke-CsArchivingDatabasePurge](Invoke-CsArchivingDatabasePurge.md) -{{Manually Enter Invoke-CsArchivingDatabasePurge Description Here}} - ### [Invoke-CsBackupServiceSync](Invoke-CsBackupServiceSync.md) -{{Manually Enter Invoke-CsBackupServiceSync Description Here}} - ### [Invoke-CsCdrDatabasePurge](Invoke-CsCdrDatabasePurge.md) -{{Manually Enter Invoke-CsCdrDatabasePurge Description Here}} - ### [Invoke-CsComputerFailBack](Invoke-CsComputerFailBack.md) -{{Manually Enter Invoke-CsComputerFailBack Description Here}} - ### [Invoke-CsComputerFailOver](Invoke-CsComputerFailOver.md) -{{Manually Enter Invoke-CsComputerFailOver Description Here}} - ### [Invoke-CsDatabaseFailover](Invoke-CsDatabaseFailover.md) -{{Manually Enter Invoke-CsDatabaseFailover Description Here}} - ### [Invoke-CsManagementServerFailover](Invoke-CsManagementServerFailover.md) -{{Manually Enter Invoke-CsManagementServerFailover Description Here}} - ### [Invoke-CsManagementStoreReplication](Invoke-CsManagementStoreReplication.md) -{{Manually Enter Invoke-CsManagementStoreReplication Description Here}} - ### [Invoke-CsPoolFailBack](Invoke-CsPoolFailBack.md) -{{Manually Enter Invoke-CsPoolFailBack Description Here}} - ### [Invoke-CsPoolFailOver](Invoke-CsPoolFailOver.md) -{{Manually Enter Invoke-CsPoolFailOver Description Here}} - ### [Invoke-CsQoEDatabasePurge](Invoke-CsQoEDatabasePurge.md) -{{Manually Enter Invoke-CsQoEDatabasePurge Description Here}} - ### [Invoke-CsRgsStoreReplicateData](Invoke-CsRgsStoreReplicateData.md) -{{Manually Enter Invoke-CsRgsStoreReplicateData Description Here}} - ### [Invoke-CsStorageServiceFlush](Invoke-CsStorageServiceFlush.md) -{{Manually Enter Invoke-CsStorageServiceFlush Description Here}} - ### [Invoke-CsUcsRollback](Invoke-CsUcsRollback.md) -{{Manually Enter Invoke-CsUcsRollback Description Here}} - ### [Lock-CsClientPin](Lock-CsClientPin.md) -{{Manually Enter Lock-CsClientPin Description Here}} - ### [Merge-CsLegacyTopology](Merge-CsLegacyTopology.md) -{{Manually Enter Merge-CsLegacyTopology Description Here}} - ### [Move-CsAnalogDevice](Move-CsAnalogDevice.md) -{{Manually Enter Move-CsAnalogDevice Description Here}} - ### [Move-CsApplicationEndpoint](Move-CsApplicationEndpoint.md) -{{Manually Enter Move-CsApplicationEndpoint Description Here}} - ### [Move-CsCommonAreaPhone](Move-CsCommonAreaPhone.md) -{{Manually Enter Move-CsCommonAreaPhone Description Here}} - ### [Move-CsConferenceDirectory](Move-CsConferenceDirectory.md) -{{Manually Enter Move-CsConferenceDirectory Description Here}} - ### [Move-CsExUmContact](Move-CsExUmContact.md) -{{Manually Enter Move-CsExUmContact Description Here}} - ### [Move-CsLegacyUser](Move-CsLegacyUser.md) -{{Manually Enter Move-CsLegacyUser Description Here}} - ### [Move-CsManagementServer](Move-CsManagementServer.md) -{{Manually Enter Move-CsManagementServer Description Here}} - ### [Move-CsMeetingRoom](Move-CsMeetingRoom.md) -{{Manually Enter Move-CsMeetingRoom Description Here}} - ### [Move-CsRgsConfiguration](Move-CsRgsConfiguration.md) -{{Manually Enter Move-CsRgsConfiguration Description Here}} - ### [Move-CsThirdPartyVideoSystem](Move-CsThirdPartyVideoSystem.md) -{{Manually Enter Move-CsThirdPartyVideoSystem Description Here}} - ### [Move-CsUser](Move-CsUser.md) -{{Manually Enter Move-CsUser Description Here}} - +### [New-CsAdditionalInternalDomain](New-CsAdditionalInternalDomain.md) ### [New-CsAddressBookConfiguration](New-CsAddressBookConfiguration.md) -{{Manually Enter New-CsAddressBookConfiguration Description Here}} - ### [New-CsAddressBookNormalizationConfiguration](New-CsAddressBookNormalizationConfiguration.md) -{{Manually Enter New-CsAddressBookNormalizationConfiguration Description Here}} - ### [New-CsAddressBookNormalizationRule](New-CsAddressBookNormalizationRule.md) -{{Manually Enter New-CsAddressBookNormalizationRule Description Here}} - ### [New-CsAdminRole](New-CsAdminRole.md) -{{Manually Enter New-CsAdminRole Description Here}} - ### [New-CsAllowedDomain](New-CsAllowedDomain.md) -{{Manually Enter New-CsAllowedDomain Description Here}} - ### [New-CsAnalogDevice](New-CsAnalogDevice.md) -{{Manually Enter New-CsAnalogDevice Description Here}} - ### [New-CsAnnouncement](New-CsAnnouncement.md) -{{Manually Enter New-CsAnnouncement Description Here}} - ### [New-CsArchivingConfiguration](New-CsArchivingConfiguration.md) -{{Manually Enter New-CsArchivingConfiguration Description Here}} - ### [New-CsArchivingPolicy](New-CsArchivingPolicy.md) -{{Manually Enter New-CsArchivingPolicy Description Here}} - ### [New-CsAutodiscoverConfiguration](New-CsAutodiscoverConfiguration.md) -{{Manually Enter New-CsAutodiscoverConfiguration Description Here}} - ### [New-CsAVEdgeConfiguration](New-CsAVEdgeConfiguration.md) -{{Manually Enter New-CsAVEdgeConfiguration Description Here}} - ### [New-CsBandwidthPolicyServiceConfiguration](New-CsBandwidthPolicyServiceConfiguration.md) -{{Manually Enter New-CsBandwidthPolicyServiceConfiguration Description Here}} - ### [New-CsBlockedDomain](New-CsBlockedDomain.md) -{{Manually Enter New-CsBlockedDomain Description Here}} - -### [New-CsCallingLineIdentity](New-CsCallingLineIdentity.md) -{{Manually Enter New-CsCallingLineIdentity Description Here}} - ### [New-CsCallParkOrbit](New-CsCallParkOrbit.md) -{{Manually Enter New-CsCallParkOrbit Description Here}} - ### [New-CsCallViaWorkPolicy](New-CsCallViaWorkPolicy.md) -{{Manually Enter New-CsCallViaWorkPolicy Description Here}} - ### [New-CsCdrConfiguration](New-CsCdrConfiguration.md) -{{Manually Enter New-CsCdrConfiguration Description Here}} - ### [New-CsClientPolicy](New-CsClientPolicy.md) -{{Manually Enter New-CsClientPolicy Description Here}} - ### [New-CsClientPolicyEntry](New-CsClientPolicyEntry.md) -{{Manually Enter New-CsClientPolicyEntry Description Here}} - ### [New-CsClientVersionConfiguration](New-CsClientVersionConfiguration.md) -{{Manually Enter New-CsClientVersionConfiguration Description Here}} - ### [New-CsClientVersionPolicy](New-CsClientVersionPolicy.md) -{{Manually Enter New-CsClientVersionPolicy Description Here}} - ### [New-CsClientVersionPolicyRule](New-CsClientVersionPolicyRule.md) -{{Manually Enter New-CsClientVersionPolicyRule Description Here}} - +### [New-CsCloudCallDataConnectorConfiguration](New-CsCloudCallDataConnectorConfiguration.md) ### [New-CsClsConfiguration](New-CsClsConfiguration.md) -{{Manually Enter New-CsClsConfiguration Description Here}} - ### [New-CsClsProvider](New-CsClsProvider.md) -{{Manually Enter New-CsClsProvider Description Here}} - ### [New-CsClsRegion](New-CsClsRegion.md) -{{Manually Enter New-CsClsRegion Description Here}} - ### [New-CsClsScenario](New-CsClsScenario.md) -{{Manually Enter New-CsClsScenario Description Here}} - ### [New-CsClsSecurityGroup](New-CsClsSecurityGroup.md) -{{Manually Enter New-CsClsSecurityGroup Description Here}} - ### [New-CsCommonAreaPhone](New-CsCommonAreaPhone.md) -{{Manually Enter New-CsCommonAreaPhone Description Here}} - ### [New-CsConferenceDirectory](New-CsConferenceDirectory.md) -{{Manually Enter New-CsConferenceDirectory Description Here}} - ### [New-CsConferencingConfiguration](New-CsConferencingConfiguration.md) -{{Manually Enter New-CsConferencingConfiguration Description Here}} - ### [New-CsConferencingPolicy](New-CsConferencingPolicy.md) -{{Manually Enter New-CsConferencingPolicy Description Here}} - ### [New-CsCpsConfiguration](New-CsCpsConfiguration.md) -{{Manually Enter New-CsCpsConfiguration Description Here}} - ### [New-CsDeviceUpdateConfiguration](New-CsDeviceUpdateConfiguration.md) -{{Manually Enter New-CsDeviceUpdateConfiguration Description Here}} - ### [New-CsDiagnosticConfiguration](New-CsDiagnosticConfiguration.md) -{{Manually Enter New-CsDiagnosticConfiguration Description Here}} - ### [New-CsDiagnosticHeaderConfiguration](New-CsDiagnosticHeaderConfiguration.md) -{{Manually Enter New-CsDiagnosticHeaderConfiguration Description Here}} - ### [New-CsDiagnosticsFilter](New-CsDiagnosticsFilter.md) -{{Manually Enter New-CsDiagnosticsFilter Description Here}} - ### [New-CsDialInConferencingAccessNumber](New-CsDialInConferencingAccessNumber.md) -{{Manually Enter New-CsDialInConferencingAccessNumber Description Here}} - ### [New-CsDialInConferencingConfiguration](New-CsDialInConferencingConfiguration.md) -{{Manually Enter New-CsDialInConferencingConfiguration Description Here}} - ### [New-CsDialInConferencingDtmfConfiguration](New-CsDialInConferencingDtmfConfiguration.md) -{{Manually Enter New-CsDialInConferencingDtmfConfiguration Description Here}} - ### [New-CsDialPlan](New-CsDialPlan.md) -{{Manually Enter New-CsDialPlan Description Here}} - -### [New-CsEdgeAllowAllKnownDomains](New-CsEdgeAllowAllKnownDomains.md) -{{Manually Enter New-CsEdgeAllowAllKnownDomains Description Here}} - -### [New-CsEdgeAllowList](New-CsEdgeAllowList.md) -{{Manually Enter New-CsEdgeAllowList Description Here}} - -### [New-CsEdgeDomainPattern](New-CsEdgeDomainPattern.md) -{{Manually Enter New-CsEdgeDomainPattern Description Here}} - ### [New-CsEmergencyNumber](New-CsEmergencyNumber.md) -{{Manually Enter New-CsEmergencyNumber Description Here}} - ### [New-CsExtendedTest](New-CsExtendedTest.md) -{{Manually Enter New-CsExtendedTest Description Here}} - ### [New-CsExternalAccessPolicy](New-CsExternalAccessPolicy.md) -{{Manually Enter New-CsExternalAccessPolicy Description Here}} - -### [New-CsExternalUserCommunicationPolicy](New-CsExternalUserCommunicationPolicy.md) -{{Manually Enter New-CsExternalUserCommunicationPolicy Description Here}} - ### [New-CsExUmContact](New-CsExUmContact.md) -{{Manually Enter New-CsExUmContact Description Here}} - ### [New-CsFileTransferFilterConfiguration](New-CsFileTransferFilterConfiguration.md) -{{Manually Enter New-CsFileTransferFilterConfiguration Description Here}} - ### [New-CsFIPSConfiguration](New-CsFIPSConfiguration.md) -{{Manually Enter New-CsFIPSConfiguration Description Here}} - ### [New-CsGroupPickupUserOrbit](New-CsGroupPickupUserOrbit.md) -{{Manually Enter New-CsGroupPickupUserOrbit Description Here}} - ### [New-CsHealthMonitoringConfiguration](New-CsHealthMonitoringConfiguration.md) -{{Manually Enter New-CsHealthMonitoringConfiguration Description Here}} - ### [New-CsHostedVoicemailPolicy](New-CsHostedVoicemailPolicy.md) -{{Manually Enter New-CsHostedVoicemailPolicy Description Here}} - ### [New-CsHostingProvider](New-CsHostingProvider.md) -{{Manually Enter New-CsHostingProvider Description Here}} - -### [New-CsHuntGroup](New-CsHuntGroup.md) -{{Manually Enter New-CsHuntGroup Description Here}} - -### [New-CsHybridPSTNSite](New-CsHybridPSTNSite.md) -{{Manually Enter New-CsHybridPSTNSite Description Here}} - +### [New-CsHybridApplicationEndpoint](New-CsHybridApplicationEndpoint.md) ### [New-CsImConfiguration](New-CsImConfiguration.md) -{{Manually Enter New-CsImConfiguration Description Here}} - ### [New-CsImFilterConfiguration](New-CsImFilterConfiguration.md) -{{Manually Enter New-CsImFilterConfiguration Description Here}} - ### [New-CsImTranslationConfiguration](New-CsImTranslationConfiguration.md) -{{Manually Enter New-CsImTranslationConfiguration Description Here}} - ### [New-CsIssuedCertId](New-CsIssuedCertId.md) -{{Manually Enter New-CsIssuedCertId Description Here}} - ### [New-CsKerberosAccount](New-CsKerberosAccount.md) -{{Manually Enter New-CsKerberosAccount Description Here}} - ### [New-CsKerberosAccountAssignment](New-CsKerberosAccountAssignment.md) -{{Manually Enter New-CsKerberosAccountAssignment Description Here}} - ### [New-CsLocationPolicy](New-CsLocationPolicy.md) -{{Manually Enter New-CsLocationPolicy Description Here}} - ### [New-CsMcxConfiguration](New-CsMcxConfiguration.md) -{{Manually Enter New-CsMcxConfiguration Description Here}} - ### [New-CsMediaConfiguration](New-CsMediaConfiguration.md) -{{Manually Enter New-CsMediaConfiguration Description Here}} - ### [New-CsMeetingConfiguration](New-CsMeetingConfiguration.md) -{{Manually Enter New-CsMeetingConfiguration Description Here}} - ### [New-CsMobilityPolicy](New-CsMobilityPolicy.md) -{{Manually Enter New-CsMobilityPolicy Description Here}} - ### [New-CsNetworkBandwidthPolicyProfile](New-CsNetworkBandwidthPolicyProfile.md) -{{Manually Enter New-CsNetworkBandwidthPolicyProfile Description Here}} - ### [New-CsNetworkBWAlternatePath](New-CsNetworkBWAlternatePath.md) -{{Manually Enter New-CsNetworkBWAlternatePath Description Here}} - ### [New-CsNetworkBWPolicy](New-CsNetworkBWPolicy.md) -{{Manually Enter New-CsNetworkBWPolicy Description Here}} - ### [New-CsNetworkInterRegionRoute](New-CsNetworkInterRegionRoute.md) -{{Manually Enter New-CsNetworkInterRegionRoute Description Here}} - ### [New-CsNetworkInterSitePolicy](New-CsNetworkInterSitePolicy.md) -{{Manually Enter New-CsNetworkInterSitePolicy Description Here}} - ### [New-CsNetworkMediaBypassConfiguration](New-CsNetworkMediaBypassConfiguration.md) -{{Manually Enter New-CsNetworkMediaBypassConfiguration Description Here}} - ### [New-CsNetworkRegion](New-CsNetworkRegion.md) -{{Manually Enter New-CsNetworkRegion Description Here}} - ### [New-CsNetworkRegionLink](New-CsNetworkRegionLink.md) -{{Manually Enter New-CsNetworkRegionLink Description Here}} - ### [New-CsNetworkSite](New-CsNetworkSite.md) -{{Manually Enter New-CsNetworkSite Description Here}} - ### [New-CsNetworkSubnet](New-CsNetworkSubnet.md) -{{Manually Enter New-CsNetworkSubnet Description Here}} - ### [New-CsOAuthServer](New-CsOAuthServer.md) -{{Manually Enter New-CsOAuthServer Description Here}} - -### [New-CsOnlineApplicationEndpoint](New-CsOnlineApplicationEndpoint.md) -{{Manually Enter New-CsOnlineApplicationEndpoint Description Here}} - -### [New-CsOnlineAudioFile](New-CsOnlineAudioFile.md) -{{Manually Enter New-CsOnlineAudioFile Description Here}} - ### [New-CsOnlineBulkAssignmentInput](New-CsOnlineBulkAssignmentInput.md) -{{Manually Enter New-CsOnlineBulkAssignmentInput Description Here}} - -### [New-CsOnlineDateTimeRange](New-CsOnlineDateTimeRange.md) -{{Manually Enter New-CsOnlineDateTimeRange Description Here}} - -### [New-CsOnlineLisCivicAddress](New-CsOnlineLisCivicAddress.md) -{{Manually Enter New-CsOnlineLisCivicAddress Description Here}} - -### [New-CsOnlineLisLocation](New-CsOnlineLisLocation.md) -{{Manually Enter New-CsOnlineLisLocation Description Here}} - ### [New-CsOnlineNumberPortInOrder](New-CsOnlineNumberPortInOrder.md) -{{Manually Enter New-CsOnlineNumberPortInOrder Description Here}} - -### [New-CsOnlinePSTNGateway](New-CsOnlinePSTNGateway.md) -{{Manually Enter New-CsOnlinePSTNGateway Description Here}} - -### [New-CsOnlineSchedule](New-CsOnlineSchedule.md) -{{Manually Enter New-CsOnlineSchedule Description Here}} - -### [New-CsOnlineTimeRange](New-CsOnlineTimeRange.md) -{{Manually Enter New-CsOnlineTimeRange Description Here}} - -### [New-CsOrganizationalAutoAttendant](New-CsOrganizationalAutoAttendant.md) -{{Manually Enter New-CsOrganizationalAutoAttendant Description Here}} - -### [New-CsOrganizationalAutoAttendantCallableEntity](New-CsOrganizationalAutoAttendantCallableEntity.md) -{{Manually Enter New-CsOrganizationalAutoAttendantCallableEntity Description Here}} - -### [New-CsOrganizationalAutoAttendantCallFlow](New-CsOrganizationalAutoAttendantCallFlow.md) -{{Manually Enter New-CsOrganizationalAutoAttendantCallFlow Description Here}} - -### [New-CsOrganizationalAutoAttendantCallHandlingAssociation](New-CsOrganizationalAutoAttendantCallHandlingAssociation.md) -{{Manually Enter New-CsOrganizationalAutoAttendantCallHandlingAssociation Description Here}} - -### [New-CsOrganizationalAutoAttendantDialScope](New-CsOrganizationalAutoAttendantDialScope.md) -{{Manually Enter New-CsOrganizationalAutoAttendantDialScope Description Here}} - -### [New-CsOrganizationalAutoAttendantMenu](New-CsOrganizationalAutoAttendantMenu.md) -{{Manually Enter New-CsOrganizationalAutoAttendantMenu Description Here}} - -### [New-CsOrganizationalAutoAttendantMenuOption](New-CsOrganizationalAutoAttendantMenuOption.md) -{{Manually Enter New-CsOrganizationalAutoAttendantMenuOption Description Here}} - -### [New-CsOrganizationalAutoAttendantPrompt](New-CsOrganizationalAutoAttendantPrompt.md) -{{Manually Enter New-CsOrganizationalAutoAttendantPrompt Description Here}} - +### [New-CsOnlineSession](New-CsOnlineSession.md) ### [New-CsOutboundCallingNumberTranslationRule](New-CsOutboundCallingNumberTranslationRule.md) -{{Manually Enter New-CsOutboundCallingNumberTranslationRule Description Here}} - ### [New-CsOutboundTranslationRule](New-CsOutboundTranslationRule.md) -{{Manually Enter New-CsOutboundTranslationRule Description Here}} - ### [New-CsPartnerApplication](New-CsPartnerApplication.md) -{{Manually Enter New-CsPartnerApplication Description Here}} - ### [New-CsPersistentChatAddin](New-CsPersistentChatAddin.md) -{{Manually Enter New-CsPersistentChatAddin Description Here}} - ### [New-CsPersistentChatCategory](New-CsPersistentChatCategory.md) -{{Manually Enter New-CsPersistentChatCategory Description Here}} - ### [New-CsPersistentChatComplianceConfiguration](New-CsPersistentChatComplianceConfiguration.md) -{{Manually Enter New-CsPersistentChatComplianceConfiguration Description Here}} - ### [New-CsPersistentChatConfiguration](New-CsPersistentChatConfiguration.md) -{{Manually Enter New-CsPersistentChatConfiguration Description Here}} - ### [New-CsPersistentChatEndpoint](New-CsPersistentChatEndpoint.md) -{{Manually Enter New-CsPersistentChatEndpoint Description Here}} - ### [New-CsPersistentChatPolicy](New-CsPersistentChatPolicy.md) -{{Manually Enter New-CsPersistentChatPolicy Description Here}} - ### [New-CsPersistentChatRoom](New-CsPersistentChatRoom.md) -{{Manually Enter New-CsPersistentChatRoom Description Here}} - ### [New-CsPinPolicy](New-CsPinPolicy.md) -{{Manually Enter New-CsPinPolicy Description Here}} - +### [New-CsPlatformServiceSettings](New-CsPlatformServiceSettings.md) ### [New-CsPresencePolicy](New-CsPresencePolicy.md) -{{Manually Enter New-CsPresencePolicy Description Here}} - ### [New-CsPresenceProvider](New-CsPresenceProvider.md) -{{Manually Enter New-CsPresenceProvider Description Here}} - ### [New-CsPrivacyConfiguration](New-CsPrivacyConfiguration.md) -{{Manually Enter New-CsPrivacyConfiguration Description Here}} - ### [New-CsProxyConfiguration](New-CsProxyConfiguration.md) -{{Manually Enter New-CsProxyConfiguration Description Here}} - ### [New-CsPublicProvider](New-CsPublicProvider.md) -{{Manually Enter New-CsPublicProvider Description Here}} - ### [New-CsPushNotificationConfiguration](New-CsPushNotificationConfiguration.md) -{{Manually Enter New-CsPushNotificationConfiguration Description Here}} - ### [New-CsQoEConfiguration](New-CsQoEConfiguration.md) -{{Manually Enter New-CsQoEConfiguration Description Here}} - ### [New-CsRegistrarConfiguration](New-CsRegistrarConfiguration.md) -{{Manually Enter New-CsRegistrarConfiguration Description Here}} - ### [New-CsReportingConfiguration](New-CsReportingConfiguration.md) -{{Manually Enter New-CsReportingConfiguration Description Here}} - ### [New-CsRgsAgentGroup](New-CsRgsAgentGroup.md) -{{Manually Enter New-CsRgsAgentGroup Description Here}} - ### [New-CsRgsAnswer](New-CsRgsAnswer.md) -{{Manually Enter New-CsRgsAnswer Description Here}} - ### [New-CsRgsCallAction](New-CsRgsCallAction.md) -{{Manually Enter New-CsRgsCallAction Description Here}} - ### [New-CsRgsHoliday](New-CsRgsHoliday.md) -{{Manually Enter New-CsRgsHoliday Description Here}} - ### [New-CsRgsHolidaySet](New-CsRgsHolidaySet.md) -{{Manually Enter New-CsRgsHolidaySet Description Here}} - ### [New-CsRgsHoursOfBusiness](New-CsRgsHoursOfBusiness.md) -{{Manually Enter New-CsRgsHoursOfBusiness Description Here}} - ### [New-CsRgsPrompt](New-CsRgsPrompt.md) -{{Manually Enter New-CsRgsPrompt Description Here}} - ### [New-CsRgsQuestion](New-CsRgsQuestion.md) -{{Manually Enter New-CsRgsQuestion Description Here}} - ### [New-CsRgsQueue](New-CsRgsQueue.md) -{{Manually Enter New-CsRgsQueue Description Here}} - ### [New-CsRgsTimeRange](New-CsRgsTimeRange.md) -{{Manually Enter New-CsRgsTimeRange Description Here}} - ### [New-CsRgsWorkflow](New-CsRgsWorkflow.md) -{{Manually Enter New-CsRgsWorkflow Description Here}} - ### [New-CsRoutingConfiguration](New-CsRoutingConfiguration.md) -{{Manually Enter New-CsRoutingConfiguration Description Here}} - ### [New-CsServerApplication](New-CsServerApplication.md) -{{Manually Enter New-CsServerApplication Description Here}} - ### [New-CsSimpleUrl](New-CsSimpleUrl.md) -{{Manually Enter New-CsSimpleUrl Description Here}} - ### [New-CsSimpleUrlConfiguration](New-CsSimpleUrlConfiguration.md) -{{Manually Enter New-CsSimpleUrlConfiguration Description Here}} - ### [New-CsSimpleUrlEntry](New-CsSimpleUrlEntry.md) -{{Manually Enter New-CsSimpleUrlEntry Description Here}} - ### [New-CsSipDomain](New-CsSipDomain.md) -{{Manually Enter New-CsSipDomain Description Here}} - ### [New-CsSipProxyCustom](New-CsSipProxyCustom.md) -{{Manually Enter New-CsSipProxyCustom Description Here}} - ### [New-CsSipProxyRealm](New-CsSipProxyRealm.md) -{{Manually Enter New-CsSipProxyRealm Description Here}} - ### [New-CsSipProxyTCP](New-CsSipProxyTCP.md) -{{Manually Enter New-CsSipProxyTCP Description Here}} - ### [New-CsSipProxyTLS](New-CsSipProxyTLS.md) -{{Manually Enter New-CsSipProxyTLS Description Here}} - ### [New-CsSipProxyTransport](New-CsSipProxyTransport.md) -{{Manually Enter New-CsSipProxyTransport Description Here}} - ### [New-CsSipProxyUseDefault](New-CsSipProxyUseDefault.md) -{{Manually Enter New-CsSipProxyUseDefault Description Here}} - ### [New-CsSipProxyUseDefaultCert](New-CsSipProxyUseDefaultCert.md) -{{Manually Enter New-CsSipProxyUseDefaultCert Description Here}} - ### [New-CsSipResponseCodeTranslationRule](New-CsSipResponseCodeTranslationRule.md) -{{Manually Enter New-CsSipResponseCodeTranslationRule Description Here}} - ### [New-CsStaticRoute](New-CsStaticRoute.md) -{{Manually Enter New-CsStaticRoute Description Here}} - ### [New-CsStaticRoutingConfiguration](New-CsStaticRoutingConfiguration.md) -{{Manually Enter New-CsStaticRoutingConfiguration Description Here}} - ### [New-CsStorageServiceConfiguration](New-CsStorageServiceConfiguration.md) -{{Manually Enter New-CsStorageServiceConfiguration Description Here}} - -### [New-CsTeamsMeetingPolicy](New-CsTeamsMeetingPolicy.md) -{{Manually Enter New-CsTeamsMeetingPolicy Description Here}} - +### [New-CsTeamsUpgradePolicy](New-CsTeamsUpgradePolicy.md) ### [New-CsTelemetryConfiguration](New-CsTelemetryConfiguration.md) -{{Manually Enter New-CsTelemetryConfiguration Description Here}} - -### [New-CsTenantDialPlan](New-CsTenantDialPlan.md) -{{Manually Enter New-CsTenantDialPlan Description Here}} - -### [New-CsTenantNetworkRegion](New-CsTenantNetworkRegion.md) -{{Manually Enter New-CsTenantNetworkRegion Description Here}} - -### [New-CsTenantNetworkSite](New-CsTenantNetworkSite.md) -{{Manually Enter New-CsTenantNetworkSite Description Here}} - -### [New-CsTenantNetworkSubnet](New-CsTenantNetworkSubnet.md) -{{Manually Enter New-CsTenantNetworkSubnet Description Here}} - -### [New-CsTenantTrustedIPAddress](New-CsTenantTrustedIPAddress.md) -{{Manually Enter New-CsTenantTrustedIPAddress Description Here}} - -### [New-CsTenantUpdateTimeWindow](New-CsTenantUpdateTimeWindow.md) -{{Manually Enter New-CsTenantUpdateTimeWindow Description Here}} - ### [New-CsTestDevice](New-CsTestDevice.md) -{{Manually Enter New-CsTestDevice Description Here}} - ### [New-CsThirdPartyVideoSystem](New-CsThirdPartyVideoSystem.md) -{{Manually Enter New-CsThirdPartyVideoSystem Description Here}} - ### [New-CsThirdPartyVideoSystemPolicy](New-CsThirdPartyVideoSystemPolicy.md) -{{Manually Enter New-CsThirdPartyVideoSystemPolicy Description Here}} - ### [New-CsTrunkConfiguration](New-CsTrunkConfiguration.md) -{{Manually Enter New-CsTrunkConfiguration Description Here}} - ### [New-CsTrustedApplication](New-CsTrustedApplication.md) -{{Manually Enter New-CsTrustedApplication Description Here}} - ### [New-CsTrustedApplicationComputer](New-CsTrustedApplicationComputer.md) -{{Manually Enter New-CsTrustedApplicationComputer Description Here}} - ### [New-CsTrustedApplicationEndpoint](New-CsTrustedApplicationEndpoint.md) -{{Manually Enter New-CsTrustedApplicationEndpoint Description Here}} - ### [New-CsTrustedApplicationPool](New-CsTrustedApplicationPool.md) -{{Manually Enter New-CsTrustedApplicationPool Description Here}} - ### [New-CsUCPhoneConfiguration](New-CsUCPhoneConfiguration.md) -{{Manually Enter New-CsUCPhoneConfiguration Description Here}} - ### [New-CsUnassignedNumber](New-CsUnassignedNumber.md) -{{Manually Enter New-CsUnassignedNumber Description Here}} - ### [New-CsUserReplicatorConfiguration](New-CsUserReplicatorConfiguration.md) -{{Manually Enter New-CsUserReplicatorConfiguration Description Here}} - ### [New-CsUserServicesConfiguration](New-CsUserServicesConfiguration.md) -{{Manually Enter New-CsUserServicesConfiguration Description Here}} - ### [New-CsUserServicesPolicy](New-CsUserServicesPolicy.md) -{{Manually Enter New-CsUserServicesPolicy Description Here}} - ### [New-CsVideoInteropServerConfiguration](New-CsVideoInteropServerConfiguration.md) -{{Manually Enter New-CsVideoInteropServerConfiguration Description Here}} - ### [New-CsVideoInteropServerSyntheticTransactionConfiguration](New-CsVideoInteropServerSyntheticTransactionConfiguration.md) -{{Manually Enter New-CsVideoInteropServerSyntheticTransactionConfiguration Description Here}} - ### [New-CsVideoTrunkConfiguration](New-CsVideoTrunkConfiguration.md) -{{Manually Enter New-CsVideoTrunkConfiguration Description Here}} - ### [New-CsVoicemailReroutingConfiguration](New-CsVoicemailReroutingConfiguration.md) -{{Manually Enter New-CsVoicemailReroutingConfiguration Description Here}} - ### [New-CsVoiceNormalizationRule](New-CsVoiceNormalizationRule.md) -{{Manually Enter New-CsVoiceNormalizationRule Description Here}} - ### [New-CsVoicePolicy](New-CsVoicePolicy.md) -{{Manually Enter New-CsVoicePolicy Description Here}} - ### [New-CsVoiceRegex](New-CsVoiceRegex.md) -{{Manually Enter New-CsVoiceRegex Description Here}} - ### [New-CsVoiceRoute](New-CsVoiceRoute.md) -{{Manually Enter New-CsVoiceRoute Description Here}} - ### [New-CsVoiceRoutingPolicy](New-CsVoiceRoutingPolicy.md) -{{Manually Enter New-CsVoiceRoutingPolicy Description Here}} - ### [New-CsVoiceTestConfiguration](New-CsVoiceTestConfiguration.md) -{{Manually Enter New-CsVoiceTestConfiguration Description Here}} - ### [New-CsWatcherNodeConfiguration](New-CsWatcherNodeConfiguration.md) -{{Manually Enter New-CsWatcherNodeConfiguration Description Here}} - ### [New-CsWebLink](New-CsWebLink.md) -{{Manually Enter New-CsWebLink Description Here}} - ### [New-CsWebOrigin](New-CsWebOrigin.md) -{{Manually Enter New-CsWebOrigin Description Here}} - ### [New-CsWebServiceConfiguration](New-CsWebServiceConfiguration.md) -{{Manually Enter New-CsWebServiceConfiguration Description Here}} - ### [New-CsWebTrustedCACertificate](New-CsWebTrustedCACertificate.md) -{{Manually Enter New-CsWebTrustedCACertificate Description Here}} - ### [New-CsXmppAllowedPartner](New-CsXmppAllowedPartner.md) -{{Manually Enter New-CsXmppAllowedPartner Description Here}} - ### [Publish-CsLisConfiguration](Publish-CsLisConfiguration.md) -{{Manually Enter Publish-CsLisConfiguration Description Here}} - ### [Publish-CsTopology](Publish-CsTopology.md) -{{Manually Enter Publish-CsTopology Description Here}} - -### [Register-CsHybridPSTNAppliance](Register-CsHybridPSTNAppliance.md) -{{Manually Enter Register-CsHybridPSTNAppliance Description Here}} - -### [Register-CsOnlineDialInConferencingServiceNumber](Register-CsOnlineDialInConferencingServiceNumber.md) -{{Manually Enter Register-CsOnlineDialInConferencingServiceNumber Description Here}} - +### [Remove-CsAdditionalInternalDomain](Remove-CsAdditionalInternalDomain.md) ### [Remove-CsAddressBookConfiguration](Remove-CsAddressBookConfiguration.md) -{{Manually Enter Remove-CsAddressBookConfiguration Description Here}} - ### [Remove-CsAddressBookNormalizationConfiguration](Remove-CsAddressBookNormalizationConfiguration.md) -{{Manually Enter Remove-CsAddressBookNormalizationConfiguration Description Here}} - ### [Remove-CsAddressBookNormalizationRule](Remove-CsAddressBookNormalizationRule.md) -{{Manually Enter Remove-CsAddressBookNormalizationRule Description Here}} - ### [Remove-CsAdminRole](Remove-CsAdminRole.md) -{{Manually Enter Remove-CsAdminRole Description Here}} - ### [Remove-CsAllowedDomain](Remove-CsAllowedDomain.md) -{{Manually Enter Remove-CsAllowedDomain Description Here}} - ### [Remove-CsAnalogDevice](Remove-CsAnalogDevice.md) -{{Manually Enter Remove-CsAnalogDevice Description Here}} - ### [Remove-CsAnnouncement](Remove-CsAnnouncement.md) -{{Manually Enter Remove-CsAnnouncement Description Here}} - ### [Remove-CsArchivingConfiguration](Remove-CsArchivingConfiguration.md) -{{Manually Enter Remove-CsArchivingConfiguration Description Here}} - ### [Remove-CsArchivingPolicy](Remove-CsArchivingPolicy.md) -{{Manually Enter Remove-CsArchivingPolicy Description Here}} - ### [Remove-CsAutodiscoverConfiguration](Remove-CsAutodiscoverConfiguration.md) -{{Manually Enter Remove-CsAutodiscoverConfiguration Description Here}} - ### [Remove-CsAVEdgeConfiguration](Remove-CsAVEdgeConfiguration.md) -{{Manually Enter Remove-CsAVEdgeConfiguration Description Here}} - ### [Remove-CsBackupServiceConfiguration](Remove-CsBackupServiceConfiguration.md) -{{Manually Enter Remove-CsBackupServiceConfiguration Description Here}} - ### [Remove-CsBandwidthPolicyServiceConfiguration](Remove-CsBandwidthPolicyServiceConfiguration.md) -{{Manually Enter Remove-CsBandwidthPolicyServiceConfiguration Description Here}} - ### [Remove-CsBlockedDomain](Remove-CsBlockedDomain.md) -{{Manually Enter Remove-CsBlockedDomain Description Here}} - ### [Remove-CsBusyOptions](Remove-CsBusyOptions.md) -{{Manually Enter Remove-CsBusyOptions Description Here}} - -### [Remove-CsCallingLineIdentity](Remove-CsCallingLineIdentity.md) -{{Manually Enter Remove-CsCallingLineIdentity Description Here}} - ### [Remove-CsCallParkOrbit](Remove-CsCallParkOrbit.md) -{{Manually Enter Remove-CsCallParkOrbit Description Here}} - ### [Remove-CsCallViaWorkPolicy](Remove-CsCallViaWorkPolicy.md) -{{Manually Enter Remove-CsCallViaWorkPolicy Description Here}} - ### [Remove-CsCdrConfiguration](Remove-CsCdrConfiguration.md) -{{Manually Enter Remove-CsCdrConfiguration Description Here}} - ### [Remove-CsCertificate](Remove-CsCertificate.md) -{{Manually Enter Remove-CsCertificate Description Here}} - ### [Remove-CsClientPolicy](Remove-CsClientPolicy.md) -{{Manually Enter Remove-CsClientPolicy Description Here}} - ### [Remove-CsClientVersionConfiguration](Remove-CsClientVersionConfiguration.md) -{{Manually Enter Remove-CsClientVersionConfiguration Description Here}} - ### [Remove-CsClientVersionPolicy](Remove-CsClientVersionPolicy.md) -{{Manually Enter Remove-CsClientVersionPolicy Description Here}} - ### [Remove-CsClientVersionPolicyRule](Remove-CsClientVersionPolicyRule.md) -{{Manually Enter Remove-CsClientVersionPolicyRule Description Here}} - ### [Remove-CsClsConfiguration](Remove-CsClsConfiguration.md) -{{Manually Enter Remove-CsClsConfiguration Description Here}} - ### [Remove-CsClsRegion](Remove-CsClsRegion.md) -{{Manually Enter Remove-CsClsRegion Description Here}} - ### [Remove-CsClsScenario](Remove-CsClsScenario.md) -{{Manually Enter Remove-CsClsScenario Description Here}} - ### [Remove-CsClsSecurityGroup](Remove-CsClsSecurityGroup.md) -{{Manually Enter Remove-CsClsSecurityGroup Description Here}} - ### [Remove-CsCommonAreaPhone](Remove-CsCommonAreaPhone.md) -{{Manually Enter Remove-CsCommonAreaPhone Description Here}} - ### [Remove-CsConferenceDirectory](Remove-CsConferenceDirectory.md) -{{Manually Enter Remove-CsConferenceDirectory Description Here}} - ### [Remove-CsConferenceDisclaimer](Remove-CsConferenceDisclaimer.md) -{{Manually Enter Remove-CsConferenceDisclaimer Description Here}} - ### [Remove-CsConferencingConfiguration](Remove-CsConferencingConfiguration.md) -{{Manually Enter Remove-CsConferencingConfiguration Description Here}} - ### [Remove-CsConferencingPolicy](Remove-CsConferencingPolicy.md) -{{Manually Enter Remove-CsConferencingPolicy Description Here}} - ### [Remove-CsConfigurationStoreLocation](Remove-CsConfigurationStoreLocation.md) -{{Manually Enter Remove-CsConfigurationStoreLocation Description Here}} - ### [Remove-CsConversationHistoryConfiguration](Remove-CsConversationHistoryConfiguration.md) -{{Manually Enter Remove-CsConversationHistoryConfiguration Description Here}} - ### [Remove-CsCpsConfiguration](Remove-CsCpsConfiguration.md) -{{Manually Enter Remove-CsCpsConfiguration Description Here}} - ### [Remove-CsDeviceUpdateConfiguration](Remove-CsDeviceUpdateConfiguration.md) -{{Manually Enter Remove-CsDeviceUpdateConfiguration Description Here}} - ### [Remove-CsDeviceUpdateRule](Remove-CsDeviceUpdateRule.md) -{{Manually Enter Remove-CsDeviceUpdateRule Description Here}} - ### [Remove-CsDiagnosticConfiguration](Remove-CsDiagnosticConfiguration.md) -{{Manually Enter Remove-CsDiagnosticConfiguration Description Here}} - ### [Remove-CsDiagnosticHeaderConfiguration](Remove-CsDiagnosticHeaderConfiguration.md) -{{Manually Enter Remove-CsDiagnosticHeaderConfiguration Description Here}} - ### [Remove-CsDialInConferencingAccessNumber](Remove-CsDialInConferencingAccessNumber.md) -{{Manually Enter Remove-CsDialInConferencingAccessNumber Description Here}} - ### [Remove-CsDialInConferencingConfiguration](Remove-CsDialInConferencingConfiguration.md) -{{Manually Enter Remove-CsDialInConferencingConfiguration Description Here}} - ### [Remove-CsDialInConferencingDtmfConfiguration](Remove-CsDialInConferencingDtmfConfiguration.md) -{{Manually Enter Remove-CsDialInConferencingDtmfConfiguration Description Here}} - ### [Remove-CsDialPlan](Remove-CsDialPlan.md) -{{Manually Enter Remove-CsDialPlan Description Here}} - ### [Remove-CsEnhancedEmergencyServiceDisclaimer](Remove-CsEnhancedEmergencyServiceDisclaimer.md) -{{Manually Enter Remove-CsEnhancedEmergencyServiceDisclaimer Description Here}} - ### [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md) -{{Manually Enter Remove-CsExternalAccessPolicy Description Here}} - -### [Remove-CsExternalUserCommunicationPolicy](Remove-CsExternalUserCommunicationPolicy.md) -{{Manually Enter Remove-CsExternalUserCommunicationPolicy Description Here}} - ### [Remove-CsExUmContact](Remove-CsExUmContact.md) -{{Manually Enter Remove-CsExUmContact Description Here}} - ### [Remove-CsFileTransferFilterConfiguration](Remove-CsFileTransferFilterConfiguration.md) -{{Manually Enter Remove-CsFileTransferFilterConfiguration Description Here}} - ### [Remove-CsFIPSConfiguration](Remove-CsFIPSConfiguration.md) -{{Manually Enter Remove-CsFIPSConfiguration Description Here}} - ### [Remove-CsGroupPickupUserOrbit](Remove-CsGroupPickupUserOrbit.md) -{{Manually Enter Remove-CsGroupPickupUserOrbit Description Here}} - ### [Remove-CsHealthMonitoringConfiguration](Remove-CsHealthMonitoringConfiguration.md) -{{Manually Enter Remove-CsHealthMonitoringConfiguration Description Here}} - ### [Remove-CsHostedVoicemailPolicy](Remove-CsHostedVoicemailPolicy.md) -{{Manually Enter Remove-CsHostedVoicemailPolicy Description Here}} - ### [Remove-CsHostingProvider](Remove-CsHostingProvider.md) -{{Manually Enter Remove-CsHostingProvider Description Here}} - -### [Remove-CsHuntGroup](Remove-CsHuntGroup.md) -{{Manually Enter Remove-CsHuntGroup Description Here}} - -### [Remove-CsHybridPSTNSite](Remove-CsHybridPSTNSite.md) -{{Manually Enter Remove-CsHybridPSTNSite Description Here}} - +### [Remove-CsHybridApplicationEndpoint](Remove-CsHybridApplicationEndpoint.md) ### [Remove-CsImConfiguration](Remove-CsImConfiguration.md) -{{Manually Enter Remove-CsImConfiguration Description Here}} - ### [Remove-CsImFilterConfiguration](Remove-CsImFilterConfiguration.md) -{{Manually Enter Remove-CsImFilterConfiguration Description Here}} - ### [Remove-CsImTranslationConfiguration](Remove-CsImTranslationConfiguration.md) -{{Manually Enter Remove-CsImTranslationConfiguration Description Here}} - ### [Remove-CsKerberosAccountAssignment](Remove-CsKerberosAccountAssignment.md) -{{Manually Enter Remove-CsKerberosAccountAssignment Description Here}} - ### [Remove-CsLisLocation](Remove-CsLisLocation.md) -{{Manually Enter Remove-CsLisLocation Description Here}} - ### [Remove-CsLisPort](Remove-CsLisPort.md) -{{Manually Enter Remove-CsLisPort Description Here}} - ### [Remove-CsLisServiceProvider](Remove-CsLisServiceProvider.md) -{{Manually Enter Remove-CsLisServiceProvider Description Here}} - ### [Remove-CsLisSubnet](Remove-CsLisSubnet.md) -{{Manually Enter Remove-CsLisSubnet Description Here}} - ### [Remove-CsLisSwitch](Remove-CsLisSwitch.md) -{{Manually Enter Remove-CsLisSwitch Description Here}} - ### [Remove-CsLisWirelessAccessPoint](Remove-CsLisWirelessAccessPoint.md) -{{Manually Enter Remove-CsLisWirelessAccessPoint Description Here}} - ### [Remove-CsLocationPolicy](Remove-CsLocationPolicy.md) -{{Manually Enter Remove-CsLocationPolicy Description Here}} - ### [Remove-CsManagementConnection](Remove-CsManagementConnection.md) -{{Manually Enter Remove-CsManagementConnection Description Here}} - ### [Remove-CsMcxConfiguration](Remove-CsMcxConfiguration.md) -{{Manually Enter Remove-CsMcxConfiguration Description Here}} - ### [Remove-CsMediaConfiguration](Remove-CsMediaConfiguration.md) -{{Manually Enter Remove-CsMediaConfiguration Description Here}} - ### [Remove-CsMeetingConfiguration](Remove-CsMeetingConfiguration.md) -{{Manually Enter Remove-CsMeetingConfiguration Description Here}} - ### [Remove-CsMobilityPolicy](Remove-CsMobilityPolicy.md) -{{Manually Enter Remove-CsMobilityPolicy Description Here}} - ### [Remove-CsNetworkBandwidthPolicyProfile](Remove-CsNetworkBandwidthPolicyProfile.md) -{{Manually Enter Remove-CsNetworkBandwidthPolicyProfile Description Here}} - ### [Remove-CsNetworkConfiguration](Remove-CsNetworkConfiguration.md) -{{Manually Enter Remove-CsNetworkConfiguration Description Here}} - ### [Remove-CsNetworkInterRegionRoute](Remove-CsNetworkInterRegionRoute.md) -{{Manually Enter Remove-CsNetworkInterRegionRoute Description Here}} - ### [Remove-CsNetworkInterSitePolicy](Remove-CsNetworkInterSitePolicy.md) -{{Manually Enter Remove-CsNetworkInterSitePolicy Description Here}} - ### [Remove-CsNetworkRegion](Remove-CsNetworkRegion.md) -{{Manually Enter Remove-CsNetworkRegion Description Here}} - ### [Remove-CsNetworkRegionLink](Remove-CsNetworkRegionLink.md) -{{Manually Enter Remove-CsNetworkRegionLink Description Here}} - ### [Remove-CsNetworkSite](Remove-CsNetworkSite.md) -{{Manually Enter Remove-CsNetworkSite Description Here}} - ### [Remove-CsNetworkSubnet](Remove-CsNetworkSubnet.md) -{{Manually Enter Remove-CsNetworkSubnet Description Here}} - ### [Remove-CsOAuthServer](Remove-CsOAuthServer.md) -{{Manually Enter Remove-CsOAuthServer Description Here}} - -### [Remove-CsOnlineApplicationEndpoint](Remove-CsOnlineApplicationEndpoint.md) -{{Manually Enter Remove-CsOnlineApplicationEndpoint Description Here}} - -### [Remove-CsOnlineDialInConferencingTenantSettings](Remove-CsOnlineDialInConferencingTenantSettings.md) -{{Manually Enter Remove-CsOnlineDialInConferencingTenantSettings Description Here}} - -### [Remove-CsOnlineLisCivicAddress](Remove-CsOnlineLisCivicAddress.md) -{{Manually Enter Remove-CsOnlineLisCivicAddress Description Here}} - -### [Remove-CsOnlineLisLocation](Remove-CsOnlineLisLocation.md) -{{Manually Enter Remove-CsOnlineLisLocation Description Here}} - ### [Remove-CsOnlineNumberPortInOrder](Remove-CsOnlineNumberPortInOrder.md) -{{Manually Enter Remove-CsOnlineNumberPortInOrder Description Here}} - -### [Remove-CsOnlinePSTNGateway](Remove-CsOnlinePSTNGateway.md) -{{Manually Enter Remove-CsOnlinePSTNGateway Description Here}} - -### [Remove-CsOnlineTelephoneNumber](Remove-CsOnlineTelephoneNumber.md) -{{Manually Enter Remove-CsOnlineTelephoneNumber Description Here}} - -### [Remove-CsOrganizationalAutoAttendant](Remove-CsOrganizationalAutoAttendant.md) -{{Manually Enter Remove-CsOrganizationalAutoAttendant Description Here}} - ### [Remove-CsOutboundCallingNumberTranslationRule](Remove-CsOutboundCallingNumberTranslationRule.md) -{{Manually Enter Remove-CsOutboundCallingNumberTranslationRule Description Here}} - ### [Remove-CsOutboundTranslationRule](Remove-CsOutboundTranslationRule.md) -{{Manually Enter Remove-CsOutboundTranslationRule Description Here}} - ### [Remove-CsPartnerApplication](Remove-CsPartnerApplication.md) -{{Manually Enter Remove-CsPartnerApplication Description Here}} - ### [Remove-CsPersistentChatAddin](Remove-CsPersistentChatAddin.md) -{{Manually Enter Remove-CsPersistentChatAddin Description Here}} - ### [Remove-CsPersistentChatCategory](Remove-CsPersistentChatCategory.md) -{{Manually Enter Remove-CsPersistentChatCategory Description Here}} - ### [Remove-CsPersistentChatComplianceConfiguration](Remove-CsPersistentChatComplianceConfiguration.md) -{{Manually Enter Remove-CsPersistentChatComplianceConfiguration Description Here}} - ### [Remove-CsPersistentChatConfiguration](Remove-CsPersistentChatConfiguration.md) -{{Manually Enter Remove-CsPersistentChatConfiguration Description Here}} - ### [Remove-CsPersistentChatEndpoint](Remove-CsPersistentChatEndpoint.md) -{{Manually Enter Remove-CsPersistentChatEndpoint Description Here}} - ### [Remove-CsPersistentChatMessage](Remove-CsPersistentChatMessage.md) -{{Manually Enter Remove-CsPersistentChatMessage Description Here}} - ### [Remove-CsPersistentChatPolicy](Remove-CsPersistentChatPolicy.md) -{{Manually Enter Remove-CsPersistentChatPolicy Description Here}} - ### [Remove-CsPersistentChatRoom](Remove-CsPersistentChatRoom.md) -{{Manually Enter Remove-CsPersistentChatRoom Description Here}} - ### [Remove-CsPinPolicy](Remove-CsPinPolicy.md) -{{Manually Enter Remove-CsPinPolicy Description Here}} - +### [Remove-CsPlatformServiceSettings](Remove-CsPlatformServiceSettings.md) ### [Remove-CsPresencePolicy](Remove-CsPresencePolicy.md) -{{Manually Enter Remove-CsPresencePolicy Description Here}} - ### [Remove-CsPresenceProvider](Remove-CsPresenceProvider.md) -{{Manually Enter Remove-CsPresenceProvider Description Here}} - ### [Remove-CsPrivacyConfiguration](Remove-CsPrivacyConfiguration.md) -{{Manually Enter Remove-CsPrivacyConfiguration Description Here}} - ### [Remove-CsProxyConfiguration](Remove-CsProxyConfiguration.md) -{{Manually Enter Remove-CsProxyConfiguration Description Here}} - ### [Remove-CsPublicProvider](Remove-CsPublicProvider.md) -{{Manually Enter Remove-CsPublicProvider Description Here}} - ### [Remove-CsPushNotificationConfiguration](Remove-CsPushNotificationConfiguration.md) -{{Manually Enter Remove-CsPushNotificationConfiguration Description Here}} - ### [Remove-CsQoEConfiguration](Remove-CsQoEConfiguration.md) -{{Manually Enter Remove-CsQoEConfiguration Description Here}} - ### [Remove-CsRegistrarConfiguration](Remove-CsRegistrarConfiguration.md) -{{Manually Enter Remove-CsRegistrarConfiguration Description Here}} - ### [Remove-CsReportingConfiguration](Remove-CsReportingConfiguration.md) -{{Manually Enter Remove-CsReportingConfiguration Description Here}} - ### [Remove-CsRgsAgentGroup](Remove-CsRgsAgentGroup.md) -{{Manually Enter Remove-CsRgsAgentGroup Description Here}} - ### [Remove-CsRgsHolidaySet](Remove-CsRgsHolidaySet.md) -{{Manually Enter Remove-CsRgsHolidaySet Description Here}} - ### [Remove-CsRgsHoursOfBusiness](Remove-CsRgsHoursOfBusiness.md) -{{Manually Enter Remove-CsRgsHoursOfBusiness Description Here}} - ### [Remove-CsRgsQueue](Remove-CsRgsQueue.md) -{{Manually Enter Remove-CsRgsQueue Description Here}} - ### [Remove-CsRgsWorkflow](Remove-CsRgsWorkflow.md) -{{Manually Enter Remove-CsRgsWorkflow Description Here}} - ### [Remove-CsRoutingConfiguration](Remove-CsRoutingConfiguration.md) -{{Manually Enter Remove-CsRoutingConfiguration Description Here}} - ### [Remove-CsServerApplication](Remove-CsServerApplication.md) -{{Manually Enter Remove-CsServerApplication Description Here}} - ### [Remove-CsSimpleUrlConfiguration](Remove-CsSimpleUrlConfiguration.md) -{{Manually Enter Remove-CsSimpleUrlConfiguration Description Here}} - ### [Remove-CsSipDomain](Remove-CsSipDomain.md) -{{Manually Enter Remove-CsSipDomain Description Here}} - ### [Remove-CsSipResponseCodeTranslationRule](Remove-CsSipResponseCodeTranslationRule.md) -{{Manually Enter Remove-CsSipResponseCodeTranslationRule Description Here}} - ### [Remove-CsSlaConfiguration](Remove-CsSlaConfiguration.md) -{{Manually Enter Remove-CsSlaConfiguration Description Here}} - ### [Remove-CsSlaDelegates](Remove-CsSlaDelegates.md) -{{Manually Enter Remove-CsSlaDelegates Description Here}} - ### [Remove-CsStaticRoutingConfiguration](Remove-CsStaticRoutingConfiguration.md) -{{Manually Enter Remove-CsStaticRoutingConfiguration Description Here}} - ### [Remove-CsStorageServiceConfiguration](Remove-CsStorageServiceConfiguration.md) -{{Manually Enter Remove-CsStorageServiceConfiguration Description Here}} - -### [Remove-CsTeamsMeetingPolicy](Remove-CsTeamsMeetingPolicy.md) -{{Manually Enter Remove-CsTeamsMeetingPolicy Description Here}} - +### [Remove-CsTeamsUpgradePolicy](Remove-CsTeamsUpgradePolicy.md) ### [Remove-CsTelemetryConfiguration](Remove-CsTelemetryConfiguration.md) -{{Manually Enter Remove-CsTelemetryConfiguration Description Here}} - -### [Remove-CsTenantDialPlan](Remove-CsTenantDialPlan.md) -{{Manually Enter Remove-CsTenantDialPlan Description Here}} - -### [Remove-CsTenantNetworkRegion](Remove-CsTenantNetworkRegion.md) -{{Manually Enter Remove-CsTenantNetworkRegion Description Here}} - -### [Remove-CsTenantNetworkSite](Remove-CsTenantNetworkSite.md) -{{Manually Enter Remove-CsTenantNetworkSite Description Here}} - -### [Remove-CsTenantNetworkSubnet](Remove-CsTenantNetworkSubnet.md) -{{Manually Enter Remove-CsTenantNetworkSubnet Description Here}} - -### [Remove-CsTenantTrustedIPAddress](Remove-CsTenantTrustedIPAddress.md) -{{Manually Enter Remove-CsTenantTrustedIPAddress Description Here}} - -### [Remove-CsTenantUpdateTimeWindow](Remove-CsTenantUpdateTimeWindow.md) -{{Manually Enter Remove-CsTenantUpdateTimeWindow Description Here}} - ### [Remove-CsTestDevice](Remove-CsTestDevice.md) -{{Manually Enter Remove-CsTestDevice Description Here}} - ### [Remove-CsTestUserCredential](Remove-CsTestUserCredential.md) -{{Manually Enter Remove-CsTestUserCredential Description Here}} - ### [Remove-CsThirdPartyVideoSystem](Remove-CsThirdPartyVideoSystem.md) -{{Manually Enter Remove-CsThirdPartyVideoSystem Description Here}} - ### [Remove-CsThirdPartyVideoSystemPolicy](Remove-CsThirdPartyVideoSystemPolicy.md) -{{Manually Enter Remove-CsThirdPartyVideoSystemPolicy Description Here}} - ### [Remove-CsTrunkConfiguration](Remove-CsTrunkConfiguration.md) -{{Manually Enter Remove-CsTrunkConfiguration Description Here}} - ### [Remove-CsTrustedApplication](Remove-CsTrustedApplication.md) -{{Manually Enter Remove-CsTrustedApplication Description Here}} - ### [Remove-CsTrustedApplicationComputer](Remove-CsTrustedApplicationComputer.md) -{{Manually Enter Remove-CsTrustedApplicationComputer Description Here}} - ### [Remove-CsTrustedApplicationEndpoint](Remove-CsTrustedApplicationEndpoint.md) -{{Manually Enter Remove-CsTrustedApplicationEndpoint Description Here}} - ### [Remove-CsTrustedApplicationPool](Remove-CsTrustedApplicationPool.md) -{{Manually Enter Remove-CsTrustedApplicationPool Description Here}} - ### [Remove-CsUCPhoneConfiguration](Remove-CsUCPhoneConfiguration.md) -{{Manually Enter Remove-CsUCPhoneConfiguration Description Here}} - ### [Remove-CsUnassignedNumber](Remove-CsUnassignedNumber.md) -{{Manually Enter Remove-CsUnassignedNumber Description Here}} - ### [Remove-CsUserAcp](Remove-CsUserAcp.md) -{{Manually Enter Remove-CsUserAcp Description Here}} - ### [Remove-CsUserReplicatorConfiguration](Remove-CsUserReplicatorConfiguration.md) -{{Manually Enter Remove-CsUserReplicatorConfiguration Description Here}} - ### [Remove-CsUserServicesConfiguration](Remove-CsUserServicesConfiguration.md) -{{Manually Enter Remove-CsUserServicesConfiguration Description Here}} - ### [Remove-CsUserServicesPolicy](Remove-CsUserServicesPolicy.md) -{{Manually Enter Remove-CsUserServicesPolicy Description Here}} - ### [Remove-CsUserStoreBackupData](Remove-CsUserStoreBackupData.md) -{{Manually Enter Remove-CsUserStoreBackupData Description Here}} - ### [Remove-CsVideoInteropServerConfiguration](Remove-CsVideoInteropServerConfiguration.md) -{{Manually Enter Remove-CsVideoInteropServerConfiguration Description Here}} - ### [Remove-CsVideoInteropServerSyntheticTransactionConfiguration](Remove-CsVideoInteropServerSyntheticTransactionConfiguration.md) -{{Manually Enter Remove-CsVideoInteropServerSyntheticTransactionConfiguration Description Here}} - ### [Remove-CsVideoTrunkConfiguration](Remove-CsVideoTrunkConfiguration.md) -{{Manually Enter Remove-CsVideoTrunkConfiguration Description Here}} - ### [Remove-CsVoiceConfiguration](Remove-CsVoiceConfiguration.md) -{{Manually Enter Remove-CsVoiceConfiguration Description Here}} - ### [Remove-CsVoicemailReroutingConfiguration](Remove-CsVoicemailReroutingConfiguration.md) -{{Manually Enter Remove-CsVoicemailReroutingConfiguration Description Here}} - ### [Remove-CsVoiceNormalizationRule](Remove-CsVoiceNormalizationRule.md) -{{Manually Enter Remove-CsVoiceNormalizationRule Description Here}} - ### [Remove-CsVoicePolicy](Remove-CsVoicePolicy.md) -{{Manually Enter Remove-CsVoicePolicy Description Here}} - ### [Remove-CsVoiceRoute](Remove-CsVoiceRoute.md) -{{Manually Enter Remove-CsVoiceRoute Description Here}} - ### [Remove-CsVoiceRoutingPolicy](Remove-CsVoiceRoutingPolicy.md) -{{Manually Enter Remove-CsVoiceRoutingPolicy Description Here}} - ### [Remove-CsVoiceTestConfiguration](Remove-CsVoiceTestConfiguration.md) -{{Manually Enter Remove-CsVoiceTestConfiguration Description Here}} - ### [Remove-CsWatcherNodeConfiguration](Remove-CsWatcherNodeConfiguration.md) -{{Manually Enter Remove-CsWatcherNodeConfiguration Description Here}} - ### [Remove-CsWebServiceConfiguration](Remove-CsWebServiceConfiguration.md) -{{Manually Enter Remove-CsWebServiceConfiguration Description Here}} - ### [Remove-CsXmppAllowedPartner](Remove-CsXmppAllowedPartner.md) -{{Manually Enter Remove-CsXmppAllowedPartner Description Here}} - ### [Request-CsCertificate](Request-CsCertificate.md) -{{Manually Enter Request-CsCertificate Description Here}} - ### [Reset-CsDeviceUpdateRule](Reset-CsDeviceUpdateRule.md) -{{Manually Enter Reset-CsDeviceUpdateRule Description Here}} - ### [Reset-CsNotificationQueues](Reset-CsNotificationQueues.md) -{{Manually Enter Reset-CsNotificationQueues Description Here}} - ### [Reset-CsPoolRegistrarState](Reset-CsPoolRegistrarState.md) -{{Manually Enter Reset-CsPoolRegistrarState Description Here}} - ### [Reset-CsRoutingGroup](Reset-CsRoutingGroup.md) -{{Manually Enter Reset-CsRoutingGroup Description Here}} - ### [Restore-CsDeviceUpdateRule](Restore-CsDeviceUpdateRule.md) -{{Manually Enter Restore-CsDeviceUpdateRule Description Here}} - ### [Revoke-CsClientCertificate](Revoke-CsClientCertificate.md) -{{Manually Enter Revoke-CsClientCertificate Description Here}} - ### [Revoke-CsOUPermission](Revoke-CsOUPermission.md) -{{Manually Enter Revoke-CsOUPermission Description Here}} - ### [Revoke-CsSetupPermission](Revoke-CsSetupPermission.md) -{{Manually Enter Revoke-CsSetupPermission Description Here}} - ### [Search-CsClsLogging](Search-CsClsLogging.md) -{{Manually Enter Search-CsClsLogging Description Here}} - -### [Search-CsOnlineTelephoneNumberInventory](Search-CsOnlineTelephoneNumberInventory.md) -{{Manually Enter Search-CsOnlineTelephoneNumberInventory Description Here}} - -### [Select-CsOnlineTelephoneNumberInventory](Select-CsOnlineTelephoneNumberInventory.md) -{{Manually Enter Select-CsOnlineTelephoneNumberInventory Description Here}} - ### [Set-CsAccessEdgeConfiguration](Set-CsAccessEdgeConfiguration.md) -{{Manually Enter Set-CsAccessEdgeConfiguration Description Here}} - ### [Set-CsAddressBookConfiguration](Set-CsAddressBookConfiguration.md) -{{Manually Enter Set-CsAddressBookConfiguration Description Here}} - ### [Set-CsAddressBookNormalizationConfiguration](Set-CsAddressBookNormalizationConfiguration.md) -{{Manually Enter Set-CsAddressBookNormalizationConfiguration Description Here}} - ### [Set-CsAddressBookNormalizationRule](Set-CsAddressBookNormalizationRule.md) -{{Manually Enter Set-CsAddressBookNormalizationRule Description Here}} - ### [Set-CsAdminRole](Set-CsAdminRole.md) -{{Manually Enter Set-CsAdminRole Description Here}} - ### [Set-CsAllowedDomain](Set-CsAllowedDomain.md) -{{Manually Enter Set-CsAllowedDomain Description Here}} - ### [Set-CsAnalogDevice](Set-CsAnalogDevice.md) -{{Manually Enter Set-CsAnalogDevice Description Here}} - ### [Set-CsAnnouncement](Set-CsAnnouncement.md) -{{Manually Enter Set-CsAnnouncement Description Here}} - ### [Set-CsApplicationServer](Set-CsApplicationServer.md) -{{Manually Enter Set-CsApplicationServer Description Here}} - ### [Set-CsArchivingConfiguration](Set-CsArchivingConfiguration.md) -{{Manually Enter Set-CsArchivingConfiguration Description Here}} - ### [Set-CsArchivingPolicy](Set-CsArchivingPolicy.md) -{{Manually Enter Set-CsArchivingPolicy Description Here}} - ### [Set-CsArchivingServer](Set-CsArchivingServer.md) -{{Manually Enter Set-CsArchivingServer Description Here}} - ### [Set-CsAudioTestServiceApplication](Set-CsAudioTestServiceApplication.md) -{{Manually Enter Set-CsAudioTestServiceApplication Description Here}} - +### [Set-CsAuthConfig](Set-CsAuthConfig.md) ### [Set-CsAutodiscoverConfiguration](Set-CsAutodiscoverConfiguration.md) -{{Manually Enter Set-CsAutodiscoverConfiguration Description Here}} - ### [Set-CsAVEdgeConfiguration](Set-CsAVEdgeConfiguration.md) -{{Manually Enter Set-CsAVEdgeConfiguration Description Here}} - ### [Set-CsBackupServiceConfiguration](Set-CsBackupServiceConfiguration.md) -{{Manually Enter Set-CsBackupServiceConfiguration Description Here}} - ### [Set-CsBandwidthPolicyServiceConfiguration](Set-CsBandwidthPolicyServiceConfiguration.md) -{{Manually Enter Set-CsBandwidthPolicyServiceConfiguration Description Here}} - ### [Set-CsBlockedDomain](Set-CsBlockedDomain.md) -{{Manually Enter Set-CsBlockedDomain Description Here}} - -### [Set-CsBroadcastMeetingConfiguration](Set-CsBroadcastMeetingConfiguration.md) -{{Manually Enter Set-CsBroadcastMeetingConfiguration Description Here}} - ### [Set-CsBusyOptions](Set-CsBusyOptions.md) -{{Manually Enter Set-CsBusyOptions Description Here}} - -### [Set-CsCallingLineIdentity](Set-CsCallingLineIdentity.md) -{{Manually Enter Set-CsCallingLineIdentity Description Here}} - ### [Set-CsCallParkOrbit](Set-CsCallParkOrbit.md) -{{Manually Enter Set-CsCallParkOrbit Description Here}} - ### [Set-CsCallParkServiceMusicOnHoldFile](Set-CsCallParkServiceMusicOnHoldFile.md) -{{Manually Enter Set-CsCallParkServiceMusicOnHoldFile Description Here}} - ### [Set-CsCallViaWorkPolicy](Set-CsCallViaWorkPolicy.md) -{{Manually Enter Set-CsCallViaWorkPolicy Description Here}} - -### [Set-CsCceApplianceConfigurationReplicationStatus](Set-CsCceApplianceConfigurationReplicationStatus.md) -{{Manually Enter Set-CsCceApplianceConfigurationReplicationStatus Description Here}} - -### [Set-CsCceApplianceDeploymentStatus](Set-CsCceApplianceDeploymentStatus.md) -{{Manually Enter Set-CsCceApplianceDeploymentStatus Description Here}} - -### [Set-CsCceApplianceStatus](Set-CsCceApplianceStatus.md) -{{Manually Enter Set-CsCceApplianceStatus Description Here}} - ### [Set-CsCdrConfiguration](Set-CsCdrConfiguration.md) -{{Manually Enter Set-CsCdrConfiguration Description Here}} - ### [Set-CsCertificate](Set-CsCertificate.md) -{{Manually Enter Set-CsCertificate Description Here}} - ### [Set-CsClientPin](Set-CsClientPin.md) -{{Manually Enter Set-CsClientPin Description Here}} - ### [Set-CsClientPolicy](Set-CsClientPolicy.md) -{{Manually Enter Set-CsClientPolicy Description Here}} - ### [Set-CsClientVersionConfiguration](Set-CsClientVersionConfiguration.md) -{{Manually Enter Set-CsClientVersionConfiguration Description Here}} - ### [Set-CsClientVersionPolicy](Set-CsClientVersionPolicy.md) -{{Manually Enter Set-CsClientVersionPolicy Description Here}} - ### [Set-CsClientVersionPolicyRule](Set-CsClientVersionPolicyRule.md) -{{Manually Enter Set-CsClientVersionPolicyRule Description Here}} - +### [Set-CsCloudCallDataConnector](Set-CsCloudCallDataConnector.md) +### [Set-CsCloudCallDataConnectorConfiguration](Set-CsCloudCallDataConnectorConfiguration.md) ### [Set-CsClsConfiguration](Set-CsClsConfiguration.md) -{{Manually Enter Set-CsClsConfiguration Description Here}} - ### [Set-CsClsRegion](Set-CsClsRegion.md) -{{Manually Enter Set-CsClsRegion Description Here}} - ### [Set-CsClsScenario](Set-CsClsScenario.md) -{{Manually Enter Set-CsClsScenario Description Here}} - ### [Set-CsClsSearchTerm](Set-CsClsSearchTerm.md) -{{Manually Enter Set-CsClsSearchTerm Description Here}} - ### [Set-CsClsSecurityGroup](Set-CsClsSecurityGroup.md) -{{Manually Enter Set-CsClsSecurityGroup Description Here}} - ### [Set-CsCommonAreaPhone](Set-CsCommonAreaPhone.md) -{{Manually Enter Set-CsCommonAreaPhone Description Here}} - ### [Set-CsConferenceDisclaimer](Set-CsConferenceDisclaimer.md) -{{Manually Enter Set-CsConferenceDisclaimer Description Here}} - ### [Set-CsConferenceServer](Set-CsConferenceServer.md) -{{Manually Enter Set-CsConferenceServer Description Here}} - ### [Set-CsConferencingConfiguration](Set-CsConferencingConfiguration.md) -{{Manually Enter Set-CsConferencingConfiguration Description Here}} - ### [Set-CsConferencingPolicy](Set-CsConferencingPolicy.md) -{{Manually Enter Set-CsConferencingPolicy Description Here}} - ### [Set-CsConfigurationStoreLocation](Set-CsConfigurationStoreLocation.md) -{{Manually Enter Set-CsConfigurationStoreLocation Description Here}} - ### [Set-CsConversationHistoryConfiguration](Set-CsConversationHistoryConfiguration.md) -{{Manually Enter Set-CsConversationHistoryConfiguration Description Here}} - ### [Set-CsCpsConfiguration](Set-CsCpsConfiguration.md) -{{Manually Enter Set-CsCpsConfiguration Description Here}} - ### [Set-CsDeviceUpdateConfiguration](Set-CsDeviceUpdateConfiguration.md) -{{Manually Enter Set-CsDeviceUpdateConfiguration Description Here}} - ### [Set-CsDiagnosticConfiguration](Set-CsDiagnosticConfiguration.md) -{{Manually Enter Set-CsDiagnosticConfiguration Description Here}} - ### [Set-CsDiagnosticHeaderConfiguration](Set-CsDiagnosticHeaderConfiguration.md) -{{Manually Enter Set-CsDiagnosticHeaderConfiguration Description Here}} - ### [Set-CsDialInConferencingAccessNumber](Set-CsDialInConferencingAccessNumber.md) -{{Manually Enter Set-CsDialInConferencingAccessNumber Description Here}} - ### [Set-CsDialInConferencingConfiguration](Set-CsDialInConferencingConfiguration.md) -{{Manually Enter Set-CsDialInConferencingConfiguration Description Here}} - ### [Set-CsDialInConferencingDtmfConfiguration](Set-CsDialInConferencingDtmfConfiguration.md) -{{Manually Enter Set-CsDialInConferencingDtmfConfiguration Description Here}} - ### [Set-CsDialPlan](Set-CsDialPlan.md) -{{Manually Enter Set-CsDialPlan Description Here}} - ### [Set-CsDirector](Set-CsDirector.md) -{{Manually Enter Set-CsDirector Description Here}} - ### [Set-CsEdgeServer](Set-CsEdgeServer.md) -{{Manually Enter Set-CsEdgeServer Description Here}} - ### [Set-CsEnhancedEmergencyServiceDisclaimer](Set-CsEnhancedEmergencyServiceDisclaimer.md) -{{Manually Enter Set-CsEnhancedEmergencyServiceDisclaimer Description Here}} - ### [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md) -{{Manually Enter Set-CsExternalAccessPolicy Description Here}} - -### [Set-CsExternalUserCommunicationPolicy](Set-CsExternalUserCommunicationPolicy.md) -{{Manually Enter Set-CsExternalUserCommunicationPolicy Description Here}} - ### [Set-CsExUmContact](Set-CsExUmContact.md) -{{Manually Enter Set-CsExUmContact Description Here}} - ### [Set-CsFileTransferFilterConfiguration](Set-CsFileTransferFilterConfiguration.md) -{{Manually Enter Set-CsFileTransferFilterConfiguration Description Here}} - ### [Set-CsFIPSConfiguration](Set-CsFIPSConfiguration.md) -{{Manually Enter Set-CsFIPSConfiguration Description Here}} - ### [Set-CsGroupPickupUserOrbit](Set-CsGroupPickupUserOrbit.md) -{{Manually Enter Set-CsGroupPickupUserOrbit Description Here}} - ### [Set-CsHealthMonitoringConfiguration](Set-CsHealthMonitoringConfiguration.md) -{{Manually Enter Set-CsHealthMonitoringConfiguration Description Here}} - ### [Set-CsHostedVoicemailPolicy](Set-CsHostedVoicemailPolicy.md) -{{Manually Enter Set-CsHostedVoicemailPolicy Description Here}} - ### [Set-CsHostingProvider](Set-CsHostingProvider.md) -{{Manually Enter Set-CsHostingProvider Description Here}} - -### [Set-CsHuntGroup](Set-CsHuntGroup.md) -{{Manually Enter Set-CsHuntGroup Description Here}} - -### [Set-CsHybridMediationServer](Set-CsHybridMediationServer.md) -{{Manually Enter Set-CsHybridMediationServer Description Here}} - -### [Set-CsHybridPSTNAppliance](Set-CsHybridPSTNAppliance.md) -{{Manually Enter Set-CsHybridPSTNAppliance Description Here}} - -### [Set-CsHybridPSTNSite](Set-CsHybridPSTNSite.md) -{{Manually Enter Set-CsHybridPSTNSite Description Here}} - +### [Set-CsHybridApplicationEndpoint](Set-CsHybridApplicationEndpoint.md) ### [Set-CsImConfiguration](Set-CsImConfiguration.md) -{{Manually Enter Set-CsImConfiguration Description Here}} - ### [Set-CsImFilterConfiguration](Set-CsImFilterConfiguration.md) -{{Manually Enter Set-CsImFilterConfiguration Description Here}} - ### [Set-CsImTranslationConfiguration](Set-CsImTranslationConfiguration.md) -{{Manually Enter Set-CsImTranslationConfiguration Description Here}} - ### [Set-CsIPPhonePolicy](Set-CsIPPhonePolicy.md) -{{Manually Enter Set-CsIPPhonePolicy Description Here}} - ### [Set-CsKerberosAccountAssignment](Set-CsKerberosAccountAssignment.md) -{{Manually Enter Set-CsKerberosAccountAssignment Description Here}} - ### [Set-CsKerberosAccountPassword](Set-CsKerberosAccountPassword.md) -{{Manually Enter Set-CsKerberosAccountPassword Description Here}} - ### [Set-CsLisLocation](Set-CsLisLocation.md) -{{Manually Enter Set-CsLisLocation Description Here}} - ### [Set-CsLisPort](Set-CsLisPort.md) -{{Manually Enter Set-CsLisPort Description Here}} - ### [Set-CsLisServiceProvider](Set-CsLisServiceProvider.md) -{{Manually Enter Set-CsLisServiceProvider Description Here}} - ### [Set-CsLisSubnet](Set-CsLisSubnet.md) -{{Manually Enter Set-CsLisSubnet Description Here}} - ### [Set-CsLisSwitch](Set-CsLisSwitch.md) -{{Manually Enter Set-CsLisSwitch Description Here}} - ### [Set-CsLisWirelessAccessPoint](Set-CsLisWirelessAccessPoint.md) -{{Manually Enter Set-CsLisWirelessAccessPoint Description Here}} - ### [Set-CsLocationPolicy](Set-CsLocationPolicy.md) -{{Manually Enter Set-CsLocationPolicy Description Here}} - ### [Set-CsManagementConnection](Set-CsManagementConnection.md) -{{Manually Enter Set-CsManagementConnection Description Here}} - ### [Set-CsManagementServer](Set-CsManagementServer.md) -{{Manually Enter Set-CsManagementServer Description Here}} - ### [Set-CsMcxConfiguration](Set-CsMcxConfiguration.md) -{{Manually Enter Set-CsMcxConfiguration Description Here}} - ### [Set-CsMediaConfiguration](Set-CsMediaConfiguration.md) -{{Manually Enter Set-CsMediaConfiguration Description Here}} - ### [Set-CsMediationServer](Set-CsMediationServer.md) -{{Manually Enter Set-CsMediationServer Description Here}} - ### [Set-CsMeetingConfiguration](Set-CsMeetingConfiguration.md) -{{Manually Enter Set-CsMeetingConfiguration Description Here}} - ### [Set-CsMeetingRoom](Set-CsMeetingRoom.md) -{{Manually Enter Set-CsMeetingRoom Description Here}} - ### [Set-CsMobilityPolicy](Set-CsMobilityPolicy.md) -{{Manually Enter Set-CsMobilityPolicy Description Here}} - ### [Set-CsMonitoringServer](Set-CsMonitoringServer.md) -{{Manually Enter Set-CsMonitoringServer Description Here}} - ### [Set-CsNetworkBandwidthPolicyProfile](Set-CsNetworkBandwidthPolicyProfile.md) -{{Manually Enter Set-CsNetworkBandwidthPolicyProfile Description Here}} - ### [Set-CsNetworkConfiguration](Set-CsNetworkConfiguration.md) -{{Manually Enter Set-CsNetworkConfiguration Description Here}} - ### [Set-CsNetworkInterRegionRoute](Set-CsNetworkInterRegionRoute.md) -{{Manually Enter Set-CsNetworkInterRegionRoute Description Here}} - ### [Set-CsNetworkInterSitePolicy](Set-CsNetworkInterSitePolicy.md) -{{Manually Enter Set-CsNetworkInterSitePolicy Description Here}} - ### [Set-CsNetworkRegion](Set-CsNetworkRegion.md) -{{Manually Enter Set-CsNetworkRegion Description Here}} - ### [Set-CsNetworkRegionLink](Set-CsNetworkRegionLink.md) -{{Manually Enter Set-CsNetworkRegionLink Description Here}} - ### [Set-CsNetworkSite](Set-CsNetworkSite.md) -{{Manually Enter Set-CsNetworkSite Description Here}} - ### [Set-CsNetworkSubnet](Set-CsNetworkSubnet.md) -{{Manually Enter Set-CsNetworkSubnet Description Here}} - ### [Set-CsOAuthConfiguration](Set-CsOAuthConfiguration.md) -{{Manually Enter Set-CsOAuthConfiguration Description Here}} - ### [Set-CsOAuthServer](Set-CsOAuthServer.md) -{{Manually Enter Set-CsOAuthServer Description Here}} - -### [Set-CsOnlineApplicationEndpoint](Set-CsOnlineApplicationEndpoint.md) -{{Manually Enter Set-CsOnlineApplicationEndpoint Description Here}} - -### [Set-CsOnlineDialInConferencingBridge](Set-CsOnlineDialInConferencingBridge.md) -{{Manually Enter Set-CsOnlineDialInConferencingBridge Description Here}} - -### [Set-CsOnlineDialInConferencingServiceNumber](Set-CsOnlineDialInConferencingServiceNumber.md) -{{Manually Enter Set-CsOnlineDialInConferencingServiceNumber Description Here}} - -### [Set-CsOnlineDialInConferencingTenantSettings](Set-CsOnlineDialInConferencingTenantSettings.md) -{{Manually Enter Set-CsOnlineDialInConferencingTenantSettings Description Here}} - -### [Set-CsOnlineDialInConferencingUser](Set-CsOnlineDialInConferencingUser.md) -{{Manually Enter Set-CsOnlineDialInConferencingUser Description Here}} - ### [Set-CsOnlineDialInConferencingUserDefaultNumber](Set-CsOnlineDialInConferencingUserDefaultNumber.md) -{{Manually Enter Set-CsOnlineDialInConferencingUserDefaultNumber Description Here}} - ### [Set-CsOnlineDirectoryUser](Set-CsOnlineDirectoryUser.md) -{{Manually Enter Set-CsOnlineDirectoryUser Description Here}} - -### [Set-CsOnlineEnhancedEmergencyServiceDisclaimer](Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md) -{{Manually Enter Set-CsOnlineEnhancedEmergencyServiceDisclaimer Description Here}} - -### [Set-CsOnlineLisCivicAddress](Set-CsOnlineLisCivicAddress.md) -{{Manually Enter Set-CsOnlineLisCivicAddress Description Here}} - -### [Set-CsOnlineLisLocation](Set-CsOnlineLisLocation.md) -{{Manually Enter Set-CsOnlineLisLocation Description Here}} - ### [Set-CsOnlineNumberPortInOrder](Set-CsOnlineNumberPortInOrder.md) -{{Manually Enter Set-CsOnlineNumberPortInOrder Description Here}} - ### [Set-CsOnlineNumberPortOutOrderPin](Set-CsOnlineNumberPortOutOrderPin.md) -{{Manually Enter Set-CsOnlineNumberPortOutOrderPin Description Here}} - -### [Set-CsOnlinePSTNGateway](Set-CsOnlinePSTNGateway.md) -{{Manually Enter Set-CsOnlinePSTNGateway Description Here}} - -### [Set-CsOnlineVoicemailPolicy](Set-CsOnlineVoicemailPolicy.md) -{{Manually Enter Set-CsOnlineVoicemailPolicy Description Here}} - -### [Set-CsOnlineVoiceUser](Set-CsOnlineVoiceUser.md) -{{Manually Enter Set-CsOnlineVoiceUser Description Here}} - ### [Set-CsOnlineVoiceUserBulk](Set-CsOnlineVoiceUserBulk.md) -{{Manually Enter Set-CsOnlineVoiceUserBulk Description Here}} - -### [Set-CsOrganizationalAutoAttendant](Set-CsOrganizationalAutoAttendant.md) -{{Manually Enter Set-CsOrganizationalAutoAttendant Description Here}} - ### [Set-CsOutboundCallingNumberTranslationRule](Set-CsOutboundCallingNumberTranslationRule.md) -{{Manually Enter Set-CsOutboundCallingNumberTranslationRule Description Here}} - ### [Set-CsOutboundTranslationRule](Set-CsOutboundTranslationRule.md) -{{Manually Enter Set-CsOutboundTranslationRule Description Here}} - ### [Set-CsPartnerApplication](Set-CsPartnerApplication.md) -{{Manually Enter Set-CsPartnerApplication Description Here}} - ### [Set-CsPersistentChatActiveServer](Set-CsPersistentChatActiveServer.md) -{{Manually Enter Set-CsPersistentChatActiveServer Description Here}} - ### [Set-CsPersistentChatAddin](Set-CsPersistentChatAddin.md) -{{Manually Enter Set-CsPersistentChatAddin Description Here}} - ### [Set-CsPersistentChatCategory](Set-CsPersistentChatCategory.md) -{{Manually Enter Set-CsPersistentChatCategory Description Here}} - ### [Set-CsPersistentChatComplianceConfiguration](Set-CsPersistentChatComplianceConfiguration.md) -{{Manually Enter Set-CsPersistentChatComplianceConfiguration Description Here}} - ### [Set-CsPersistentChatConfiguration](Set-CsPersistentChatConfiguration.md) -{{Manually Enter Set-CsPersistentChatConfiguration Description Here}} - ### [Set-CsPersistentChatPolicy](Set-CsPersistentChatPolicy.md) -{{Manually Enter Set-CsPersistentChatPolicy Description Here}} - ### [Set-CsPersistentChatRoom](Set-CsPersistentChatRoom.md) -{{Manually Enter Set-CsPersistentChatRoom Description Here}} - ### [Set-CsPersistentChatState](Set-CsPersistentChatState.md) -{{Manually Enter Set-CsPersistentChatState Description Here}} - ### [Set-CsPinPolicy](Set-CsPinPolicy.md) -{{Manually Enter Set-CsPinPolicy Description Here}} - +### [Set-CsPlatformServiceSettings](Set-CsPlatformServiceSettings.md) ### [Set-CsPresenceManagementState](Set-CsPresenceManagementState.md) -{{Manually Enter Set-CsPresenceManagementState Description Here}} - ### [Set-CsPresencePolicy](Set-CsPresencePolicy.md) -{{Manually Enter Set-CsPresencePolicy Description Here}} - ### [Set-CsPresenceProvider](Set-CsPresenceProvider.md) -{{Manually Enter Set-CsPresenceProvider Description Here}} - ### [Set-CsPrivacyConfiguration](Set-CsPrivacyConfiguration.md) -{{Manually Enter Set-CsPrivacyConfiguration Description Here}} - ### [Set-CsProxyConfiguration](Set-CsProxyConfiguration.md) -{{Manually Enter Set-CsProxyConfiguration Description Here}} - ### [Set-CsPstnGateway](Set-CsPstnGateway.md) -{{Manually Enter Set-CsPstnGateway Description Here}} - ### [Set-CsPstnUsage](Set-CsPstnUsage.md) -{{Manually Enter Set-CsPstnUsage Description Here}} - ### [Set-CsPublicProvider](Set-CsPublicProvider.md) -{{Manually Enter Set-CsPublicProvider Description Here}} - ### [Set-CsPushNotificationConfiguration](Set-CsPushNotificationConfiguration.md) -{{Manually Enter Set-CsPushNotificationConfiguration Description Here}} - ### [Set-CsQoEConfiguration](Set-CsQoEConfiguration.md) -{{Manually Enter Set-CsQoEConfiguration Description Here}} - ### [Set-CsRegistrar](Set-CsRegistrar.md) -{{Manually Enter Set-CsRegistrar Description Here}} - ### [Set-CsRegistrarConfiguration](Set-CsRegistrarConfiguration.md) -{{Manually Enter Set-CsRegistrarConfiguration Description Here}} - ### [Set-CsReportingConfiguration](Set-CsReportingConfiguration.md) -{{Manually Enter Set-CsReportingConfiguration Description Here}} - ### [Set-CsRgsAgentGroup](Set-CsRgsAgentGroup.md) -{{Manually Enter Set-CsRgsAgentGroup Description Here}} - ### [Set-CsRgsConfiguration](Set-CsRgsConfiguration.md) -{{Manually Enter Set-CsRgsConfiguration Description Here}} - ### [Set-CsRgsHolidaySet](Set-CsRgsHolidaySet.md) -{{Manually Enter Set-CsRgsHolidaySet Description Here}} - ### [Set-CsRgsHoursOfBusiness](Set-CsRgsHoursOfBusiness.md) -{{Manually Enter Set-CsRgsHoursOfBusiness Description Here}} - ### [Set-CsRgsQueue](Set-CsRgsQueue.md) -{{Manually Enter Set-CsRgsQueue Description Here}} - ### [Set-CsRgsWorkflow](Set-CsRgsWorkflow.md) -{{Manually Enter Set-CsRgsWorkflow Description Here}} - ### [Set-CsRoutingConfiguration](Set-CsRoutingConfiguration.md) -{{Manually Enter Set-CsRoutingConfiguration Description Here}} - ### [Set-CsServerApplication](Set-CsServerApplication.md) -{{Manually Enter Set-CsServerApplication Description Here}} - ### [Set-CsSimpleUrlConfiguration](Set-CsSimpleUrlConfiguration.md) -{{Manually Enter Set-CsSimpleUrlConfiguration Description Here}} - ### [Set-CsSipDomain](Set-CsSipDomain.md) -{{Manually Enter Set-CsSipDomain Description Here}} - ### [Set-CsSipResponseCodeTranslationRule](Set-CsSipResponseCodeTranslationRule.md) -{{Manually Enter Set-CsSipResponseCodeTranslationRule Description Here}} - ### [Set-CsSite](Set-CsSite.md) -{{Manually Enter Set-CsSite Description Here}} - ### [Set-CsSlaConfiguration](Set-CsSlaConfiguration.md) -{{Manually Enter Set-CsSlaConfiguration Description Here}} - ### [Set-CsStaticRoutingConfiguration](Set-CsStaticRoutingConfiguration.md) -{{Manually Enter Set-CsStaticRoutingConfiguration Description Here}} - ### [Set-CsStorageServiceConfiguration](Set-CsStorageServiceConfiguration.md) -{{Manually Enter Set-CsStorageServiceConfiguration Description Here}} - -### [Set-CsTeamsCallingPolicy](Set-CsTeamsCallingPolicy.md) -{{Manually Enter Set-CsTeamsCallingPolicy Description Here}} - -### [Set-CsTeamsMobilityPolicy](Set-CsTeamsMobilityPolicy.md) -{{Manually Enter Set-CsTeamsMobilityPolicy Description Here}} - -### [Set-CsTeamsMeetingPolicy](Set-CsTeamsMeetingPolicy.md) -{{Manually Enter Set-CsTeamsMeetingPolicy Description Here}} - +### [Set-CsTeamsUpgradeConfiguration](Set-CsTeamsUpgradeConfiguration.md) +### [Set-CsTeamsUpgradePolicy](Set-CsTeamsUpgradePolicy.md) ### [Set-CsTelemetryConfiguration](Set-CsTelemetryConfiguration.md) -{{Manually Enter Set-CsTelemetryConfiguration Description Here}} - -### [Set-CsTenantDialPlan](Set-CsTenantDialPlan.md) -{{Manually Enter Set-CsTenantDialPlan Description Here}} - -### [Set-CsTenantNetworkRegion](Set-CsTenantNetworkRegion.md) -{{Manually Enter Set-CsTenantNetworkRegion Description Here}} - -### [Set-CsTenantNetworkSite](Set-CsTenantNetworkSite.md) -{{Manually Enter Set-CsTenantNetworkSite Description Here}} - -### [Set-CsTenantNetworkSubnet](Set-CsTenantNetworkSubnet.md) -{{Manually Enter Set-CsTenantNetworkSubnet Description Here}} - -### [Set-CsTenantTrustedIPAddress](Set-CsTenantTrustedIPAddress.md) -{{Manually Enter Set-CsTenantTrustedIPAddress Description Here}} - -### [Set-CsTenantFederationConfiguration](Set-CsTenantFederationConfiguration.md) -{{Manually Enter Set-CsTenantFederationConfiguration Description Here}} - ### [Set-CsTenantHybridConfiguration](Set-CsTenantHybridConfiguration.md) -{{Manually Enter Set-CsTenantHybridConfiguration Description Here}} - -### [Set-CsTenantMigrationConfiguration](Set-CsTenantMigrationConfiguration.md) -{{Manually Enter Set-CsTenantMigrationConfiguration Description Here}} - -### [Set-CsTenantPublicProvider](Set-CsTenantPublicProvider.md) -{{Manually Enter Set-CsTenantPublicProvider Description Here}} - -### [Set-CsTenantUpdateTimeWindow](Set-CsTenantUpdateTimeWindow.md) -{{Manually Enter Set-CsTenantUpdateTimeWindow Description Here}} - ### [Set-CsTestDevice](Set-CsTestDevice.md) -{{Manually Enter Set-CsTestDevice Description Here}} - ### [Set-CsTestUserCredential](Set-CsTestUserCredential.md) -{{Manually Enter Set-CsTestUserCredential Description Here}} - ### [Set-CsThirdPartyVideoSystem](Set-CsThirdPartyVideoSystem.md) -{{Manually Enter Set-CsThirdPartyVideoSystem Description Here}} - ### [Set-CsThirdPartyVideoSystemPolicy](Set-CsThirdPartyVideoSystemPolicy.md) -{{Manually Enter Set-CsThirdPartyVideoSystemPolicy Description Here}} - ### [Set-CsTrunkConfiguration](Set-CsTrunkConfiguration.md) -{{Manually Enter Set-CsTrunkConfiguration Description Here}} - ### [Set-CsTrustedApplication](Set-CsTrustedApplication.md) -{{Manually Enter Set-CsTrustedApplication Description Here}} - ### [Set-CsTrustedApplicationEndpoint](Set-CsTrustedApplicationEndpoint.md) -{{Manually Enter Set-CsTrustedApplicationEndpoint Description Here}} - ### [Set-CsTrustedApplicationPool](Set-CsTrustedApplicationPool.md) -{{Manually Enter Set-CsTrustedApplicationPool Description Here}} - ### [Set-CsUCPhoneConfiguration](Set-CsUCPhoneConfiguration.md) -{{Manually Enter Set-CsUCPhoneConfiguration Description Here}} - ### [Set-CsUICulture](Set-CsUICulture.md) -{{Manually Enter Set-CsUICulture Description Here}} - ### [Set-CsUnassignedNumber](Set-CsUnassignedNumber.md) -{{Manually Enter Set-CsUnassignedNumber Description Here}} - ### [Set-CsUser](Set-CsUser.md) -{{Manually Enter Set-CsUser Description Here}} - ### [Set-CsUserAcp](Set-CsUserAcp.md) -{{Manually Enter Set-CsUserAcp Description Here}} - ### [Set-CsUserCallForwardingSettings](Set-CsUserCallForwardingSettings.md) -{{Manually Enter Set-CsUserCallForwardingSettings Description Here}} - ### [Set-CsUserDatabaseState](Set-CsUserDatabaseState.md) -{{Manually Enter Set-CsUserDatabaseState Description Here}} - ### [Set-CsUserDelegates](Set-CsUserDelegates.md) -{{Manually Enter Set-CsUserDelegates Description Here}} - -### [Set-CsUserPstnSettings](Set-CsUserPstnSettings.md) -{{Manually Enter Set-CsUserPstnSettings Description Here}} - ### [Set-CsUserReplicatorConfiguration](Set-CsUserReplicatorConfiguration.md) -{{Manually Enter Set-CsUserReplicatorConfiguration Description Here}} - ### [Set-CsUserServer](Set-CsUserServer.md) -{{Manually Enter Set-CsUserServer Description Here}} - ### [Set-CsUserServicesConfiguration](Set-CsUserServicesConfiguration.md) -{{Manually Enter Set-CsUserServicesConfiguration Description Here}} - ### [Set-CsUserServicesPolicy](Set-CsUserServicesPolicy.md) -{{Manually Enter Set-CsUserServicesPolicy Description Here}} - ### [Set-CsUserTeamMembers](Set-CsUserTeamMembers.md) -{{Manually Enter Set-CsUserTeamMembers Description Here}} - ### [Set-CsVideoGateway](Set-CsVideoGateway.md) -{{Manually Enter Set-CsVideoGateway Description Here}} - ### [Set-CsVideoInteropServer](Set-CsVideoInteropServer.md) -{{Manually Enter Set-CsVideoInteropServer Description Here}} - ### [Set-CsVideoInteropServerConfiguration](Set-CsVideoInteropServerConfiguration.md) -{{Manually Enter Set-CsVideoInteropServerConfiguration Description Here}} - ### [Set-CsVideoInteropServerSyntheticTransactionConfiguration](Set-CsVideoInteropServerSyntheticTransactionConfiguration.md) -{{Manually Enter Set-CsVideoInteropServerSyntheticTransactionConfiguration Description Here}} - ### [Set-CsVideoTrunkConfiguration](Set-CsVideoTrunkConfiguration.md) -{{Manually Enter Set-CsVideoTrunkConfiguration Description Here}} - ### [Set-CsVoiceConfiguration](Set-CsVoiceConfiguration.md) -{{Manually Enter Set-CsVoiceConfiguration Description Here}} - ### [Set-CsVoicemailReroutingConfiguration](Set-CsVoicemailReroutingConfiguration.md) -{{Manually Enter Set-CsVoicemailReroutingConfiguration Description Here}} - ### [Set-CsVoiceNormalizationRule](Set-CsVoiceNormalizationRule.md) -{{Manually Enter Set-CsVoiceNormalizationRule Description Here}} - ### [Set-CsVoicePolicy](Set-CsVoicePolicy.md) -{{Manually Enter Set-CsVoicePolicy Description Here}} - ### [Set-CsVoiceRoute](Set-CsVoiceRoute.md) -{{Manually Enter Set-CsVoiceRoute Description Here}} - ### [Set-CsVoiceRoutingPolicy](Set-CsVoiceRoutingPolicy.md) -{{Manually Enter Set-CsVoiceRoutingPolicy Description Here}} - ### [Set-CsVoiceTestConfiguration](Set-CsVoiceTestConfiguration.md) -{{Manually Enter Set-CsVoiceTestConfiguration Description Here}} - ### [Set-CsWatcherNodeConfiguration](Set-CsWatcherNodeConfiguration.md) -{{Manually Enter Set-CsWatcherNodeConfiguration Description Here}} - ### [Set-CsWebServer](Set-CsWebServer.md) -{{Manually Enter Set-CsWebServer Description Here}} - ### [Set-CsWebServiceConfiguration](Set-CsWebServiceConfiguration.md) -{{Manually Enter Set-CsWebServiceConfiguration Description Here}} - ### [Set-CsXmppAllowedPartner](Set-CsXmppAllowedPartner.md) -{{Manually Enter Set-CsXmppAllowedPartner Description Here}} - ### [Set-CsXmppGatewayConfiguration](Set-CsXmppGatewayConfiguration.md) -{{Manually Enter Set-CsXmppGatewayConfiguration Description Here}} - ### [Show-CsClsLogging](Show-CsClsLogging.md) -{{Manually Enter Show-CsClsLogging Description Here}} - +### [skype](skype.md) ### [Start-CsClsLogging](Start-CsClsLogging.md) -{{Manually Enter Start-CsClsLogging Description Here}} - -### [Start-CsExMeetingMigration](Start-CsExMeetingMigration.md) -{{Manually Enter Start-CsExMeetingMigration Description Here}} - ### [Start-CsPool](Start-CsPool.md) -{{Manually Enter Start-CsPool Description Here}} - ### [Start-CsWindowsService](Start-CsWindowsService.md) -{{Manually Enter Start-CsWindowsService Description Here}} - ### [Stop-CsClsLogging](Stop-CsClsLogging.md) -{{Manually Enter Stop-CsClsLogging Description Here}} - ### [Stop-CsWindowsService](Stop-CsWindowsService.md) -{{Manually Enter Stop-CsWindowsService Description Here}} - ### [Sync-CsClsLogging](Sync-CsClsLogging.md) -{{Manually Enter Sync-CsClsLogging Description Here}} - ### [Sync-CsUserData](Sync-CsUserData.md) -{{Manually Enter Sync-CsUserData Description Here}} - ### [Test-CsAddressBookService](Test-CsAddressBookService.md) -{{Manually Enter Test-CsAddressBookService Description Here}} - ### [Test-CsAddressBookWebQuery](Test-CsAddressBookWebQuery.md) -{{Manually Enter Test-CsAddressBookWebQuery Description Here}} - ### [Test-CsASConference](Test-CsASConference.md) -{{Manually Enter Test-CsASConference Description Here}} - ### [Test-CsAudioConferencingProvider](Test-CsAudioConferencingProvider.md) -{{Manually Enter Test-CsAudioConferencingProvider Description Here}} - ### [Test-CsAVConference](Test-CsAVConference.md) -{{Manually Enter Test-CsAVConference Description Here}} - ### [Test-CsAVEdgeConnectivity](Test-CsAVEdgeConnectivity.md) -{{Manually Enter Test-CsAVEdgeConnectivity Description Here}} - ### [Test-CsCertificateConfiguration](Test-CsCertificateConfiguration.md) -{{Manually Enter Test-CsCertificateConfiguration Description Here}} - ### [Test-CsClientAuth](Test-CsClientAuth.md) -{{Manually Enter Test-CsClientAuth Description Here}} - ### [Test-CsClientAuthentication](Test-CsClientAuthentication.md) -{{Manually Enter Test-CsClientAuthentication Description Here}} - ### [Test-CsComputer](Test-CsComputer.md) -{{Manually Enter Test-CsComputer Description Here}} - ### [Test-CsDatabase](Test-CsDatabase.md) -{{Manually Enter Test-CsDatabase Description Here}} - ### [Test-CsDataConference](Test-CsDataConference.md) -{{Manually Enter Test-CsDataConference Description Here}} - ### [Test-CsDialInConferencing](Test-CsDialInConferencing.md) -{{Manually Enter Test-CsDialInConferencing Description Here}} - ### [Test-CsDialPlan](Test-CsDialPlan.md) -{{Manually Enter Test-CsDialPlan Description Here}} - -### [Test-CsEffectiveTenantDialPlan](Test-CsEffectiveTenantDialPlan.md) -{{Manually Enter Test-CsEffectiveTenantDialPlan Description Here}} - ### [Test-CsExStorageConnectivity](Test-CsExStorageConnectivity.md) -{{Manually Enter Test-CsExStorageConnectivity Description Here}} - ### [Test-CsExStorageNotification](Test-CsExStorageNotification.md) -{{Manually Enter Test-CsExStorageNotification Description Here}} - ### [Test-CsExUMConnectivity](Test-CsExUMConnectivity.md) -{{Manually Enter Test-CsExUMConnectivity Description Here}} - ### [Test-CsExUMVoiceMail](Test-CsExUMVoiceMail.md) -{{Manually Enter Test-CsExUMVoiceMail Description Here}} - ### [Test-CsFederatedPartner](Test-CsFederatedPartner.md) -{{Manually Enter Test-CsFederatedPartner Description Here}} - ### [Test-CsGroupExpansion](Test-CsGroupExpansion.md) -{{Manually Enter Test-CsGroupExpansion Description Here}} - ### [Test-CsGroupIM](Test-CsGroupIM.md) -{{Manually Enter Test-CsGroupIM Description Here}} - ### [Test-CsIM](Test-CsIM.md) -{{Manually Enter Test-CsIM Description Here}} - ### [Test-CsInterTrunkRouting](Test-CsInterTrunkRouting.md) -{{Manually Enter Test-CsInterTrunkRouting Description Here}} - ### [Test-CsKerberosAccountAssignment](Test-CsKerberosAccountAssignment.md) -{{Manually Enter Test-CsKerberosAccountAssignment Description Here}} - ### [Test-CsLisCivicAddress](Test-CsLisCivicAddress.md) -{{Manually Enter Test-CsLisCivicAddress Description Here}} - ### [Test-CsLisConfiguration](Test-CsLisConfiguration.md) -{{Manually Enter Test-CsLisConfiguration Description Here}} - ### [Test-CsLocationPolicy](Test-CsLocationPolicy.md) -{{Manually Enter Test-CsLocationPolicy Description Here}} - ### [Test-CsManagementServer](Test-CsManagementServer.md) -{{Manually Enter Test-CsManagementServer Description Here}} - ### [Test-CsMcxConference](Test-CsMcxConference.md) -{{Manually Enter Test-CsMcxConference Description Here}} - ### [Test-CsMcxP2PIM](Test-CsMcxP2PIM.md) -{{Manually Enter Test-CsMcxP2PIM Description Here}} - ### [Test-CsMcxPushNotification](Test-CsMcxPushNotification.md) -{{Manually Enter Test-CsMcxPushNotification Description Here}} - ### [Test-CsOnlineCarrierPortabilityIn](Test-CsOnlineCarrierPortabilityIn.md) -{{Manually Enter Test-CsOnlineCarrierPortabilityIn Description Here}} - ### [Test-CsOnlineLisCivicAddress](Test-CsOnlineLisCivicAddress.md) -{{Manually Enter Test-CsOnlineLisCivicAddress Description Here}} - ### [Test-CsOnlinePortabilityIn](Test-CsOnlinePortabilityIn.md) -{{Manually Enter Test-CsOnlinePortabilityIn Description Here}} - ### [Test-CsOUPermission](Test-CsOUPermission.md) -{{Manually Enter Test-CsOUPermission Description Here}} - ### [Test-CsP2PAV](Test-CsP2PAV.md) -{{Manually Enter Test-CsP2PAV Description Here}} - ### [Test-CsP2PVideoInteropServerSipTrunkAV](Test-CsP2PVideoInteropServerSipTrunkAV.md) -{{Manually Enter Test-CsP2PVideoInteropServerSipTrunkAV Description Here}} - ### [Test-CsPersistentChatMessage](Test-CsPersistentChatMessage.md) -{{Manually Enter Test-CsPersistentChatMessage Description Here}} - ### [Test-CsPhoneBootstrap](Test-CsPhoneBootstrap.md) -{{Manually Enter Test-CsPhoneBootstrap Description Here}} - ### [Test-CsPresence](Test-CsPresence.md) -{{Manually Enter Test-CsPresence Description Here}} - ### [Test-CsPstnOutboundCall](Test-CsPstnOutboundCall.md) -{{Manually Enter Test-CsPstnOutboundCall Description Here}} - ### [Test-CsPstnPeerToPeerCall](Test-CsPstnPeerToPeerCall.md) -{{Manually Enter Test-CsPstnPeerToPeerCall Description Here}} - ### [Test-CsRegistration](Test-CsRegistration.md) -{{Manually Enter Test-CsRegistration Description Here}} - ### [Test-CsReplica](Test-CsReplica.md) -{{Manually Enter Test-CsReplica Description Here}} - ### [Test-CsSetupPermission](Test-CsSetupPermission.md) -{{Manually Enter Test-CsSetupPermission Description Here}} - ### [Test-CsTopology](Test-CsTopology.md) -{{Manually Enter Test-CsTopology Description Here}} - ### [Test-CsTrunkConfiguration](Test-CsTrunkConfiguration.md) -{{Manually Enter Test-CsTrunkConfiguration Description Here}} - ### [Test-CsUcwaConference](Test-CsUcwaConference.md) -{{Manually Enter Test-CsUcwaConference Description Here}} - ### [Test-CsUnifiedContactStore](Test-CsUnifiedContactStore.md) -{{Manually Enter Test-CsUnifiedContactStore Description Here}} - ### [Test-CsVoiceNormalizationRule](Test-CsVoiceNormalizationRule.md) -{{Manually Enter Test-CsVoiceNormalizationRule Description Here}} - ### [Test-CsVoicePolicy](Test-CsVoicePolicy.md) -{{Manually Enter Test-CsVoicePolicy Description Here}} - ### [Test-CsVoiceRoute](Test-CsVoiceRoute.md) -{{Manually Enter Test-CsVoiceRoute Description Here}} - ### [Test-CsVoiceTestConfiguration](Test-CsVoiceTestConfiguration.md) -{{Manually Enter Test-CsVoiceTestConfiguration Description Here}} - ### [Test-CsVoiceUser](Test-CsVoiceUser.md) -{{Manually Enter Test-CsVoiceUser Description Here}} - ### [Test-CsWatcherNodeConfiguration](Test-CsWatcherNodeConfiguration.md) -{{Manually Enter Test-CsWatcherNodeConfiguration Description Here}} - ### [Test-CsWebApp](Test-CsWebApp.md) -{{Manually Enter Test-CsWebApp Description Here}} - ### [Test-CsWebAppAnonymous](Test-CsWebAppAnonymous.md) -{{Manually Enter Test-CsWebAppAnonymous Description Here}} - ### [Test-CsWebScheduler](Test-CsWebScheduler.md) -{{Manually Enter Test-CsWebScheduler Description Here}} - ### [Test-CsXmppIM](Test-CsXmppIM.md) -{{Manually Enter Test-CsXmppIM Description Here}} - ### [Uninstall-CsDatabase](Uninstall-CsDatabase.md) -{{Manually Enter Uninstall-CsDatabase Description Here}} - ### [Uninstall-CsMirrorDatabase](Uninstall-CsMirrorDatabase.md) -{{Manually Enter Uninstall-CsMirrorDatabase Description Here}} - ### [Unlock-CsClientPin](Unlock-CsClientPin.md) -{{Manually Enter Unlock-CsClientPin Description Here}} - ### [Unpublish-CsLisConfiguration](Unpublish-CsLisConfiguration.md) -{{Manually Enter Unpublish-CsLisConfiguration Description Here}} - -### [Unregister-CsHybridPSTNAppliance](Unregister-CsHybridPSTNAppliance.md) -{{Manually Enter Unregister-CsHybridPSTNAppliance Description Here}} - -### [Unregister-CsOnlineDialInConferencingServiceNumber](Unregister-CsOnlineDialInConferencingServiceNumber.md) -{{Manually Enter Unregister-CsOnlineDialInConferencingServiceNumber Description Here}} - ### [Update-CsAddressBook](Update-CsAddressBook.md) -{{Manually Enter Update-CsAddressBook Description Here}} - ### [Update-CsAdminRole](Update-CsAdminRole.md) -{{Manually Enter Update-CsAdminRole Description Here}} - ### [Update-CsClsLogging](Update-CsClsLogging.md) -{{Manually Enter Update-CsClsLogging Description Here}} - -### [Update-CsOrganizationalAutoAttendant](Update-CsOrganizationalAutoAttendant.md) -{{Manually Enter Update-CsOrganizationalAutoAttendant Description Here}} - -### [Update-CsTenantMeetingUrl](Update-CsTenantMeetingUrl.md) -{{Manually Enter Update-CsTenantMeetingUrl Description Here}} - ### [Update-CsUserData](Update-CsUserData.md) -{{Manually Enter Update-CsUserData Description Here}} - ### [Update-CsUserDatabase](Update-CsUserDatabase.md) -{{Manually Enter Update-CsUserDatabase Description Here}} - -### [Get-CsTeamsInteropPolicy](Get-CsTeamsInteropPolicy.md) -{{Manually Enter Get-CsTeamsInteropPolicy Description Here}} - -### [Grant-CsTeamsInteropPolicy](Grant-CsTeamsInteropPolicy.md) -{{Manually Enter Grant-CsTeamsInteropPolicy Description Here}} - -### [Remove-CsTeamsInteropPolicy](Remove-CsTeamsInteropPolicy.md) -{{Manually Enter Remove-CsTeamsInteropPolicy Description Here}} - -### [Set-CsPlatformServiceSettings](Set-CsPlatformServiceSettings.md) -{{Manually Enter Set-CsPlatformServiceSettings Description Here}} - -### [Get-CsPlatformServiceSettings](Get-CsPlatformServiceSettings.md) -{{Manually Enter Get-CsPlatformServiceSettings Description Here}} - -### [New-CsPlatformServiceSettings](New-CsPlatformServiceSettings.md) -{{Manually Enter New-CsPlatformServiceSettings Description Here}} - -### [Remove-CsPlatformServiceSettings](Remove-CsPlatformServiceSettings.md) -{{Manually Enter Remove-CsPlatformServiceSettings Description Here}} - -### [Get-CsAdditionalInternalDomain](Get-CsAdditionalInternalDomain.md) -{{Manually Enter Get-CsAdditionalInternalDomain Description Here}} - -### [New-CsAdditionalInternalDomain](New-CsAdditionalInternalDomain.md) -{{Manually Enter New-CsAdditionalInternalDomain Description Here}} - -### [Remove-CsAdditionalInternalDomain](Remove-CsAdditionalInternalDomain.md) -{{Manually Enter Remove-CsAdditionalInternalDomain Description Here}} - -### [Get-CsHybridApplicationEndpoint](Get-CsHybridApplicationEndpoint.md) -{{Manually Enter Get-CsHybridApplicationEndpoint Description Here}} - -### [New-CsHybridApplicationEndpoint](New-CsHybridApplicationEndpoint.md) -{{Manually Enter New-CsHybridApplicationEndpoint Description Here}} - -### [Set-CsHybridApplicationEndpoint](Set-CsHybridApplicationEndpoint.md) -{{Manually Enter Set-CsHybridApplicationEndpoint Description Here}} - -### [Remove-CsHybridApplicationEndpoint](Remove-CsHybridApplicationEndpoint.md) -{{Manually Enter Remove-CsHybridApplicationEndpoint Description Here}} - -### [Get-CsTeamsUpgradeConfiguration](Get-CsTeamsUpgradeConfiguration.md) - -### [Set-CsTeamsUpgradeConfiguration](Set-CsTeamsUpgradeConfiguration.md) - -### [Get-CsTeamsUpgradePolicy](Get-CsTeamsUpgradePolicy.md) - -### [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) - -### [New-CsTeamsUpgradePolicy](New-CsTeamsUpgradePolicy.md) - -### [Remove-CsTeamsUpgradePolicy](Remove-CsTeamsUpgradePolicy.md) - -### [Set-CsTeamsUpgradePolicy](Set-CsTeamsUpgradePolicy.md) - -### [Get-CsCloudCallDataConnector](Get-CsCloudCallDataConnector.md) - -### [Get-CsCloudCallDataConnectorConfiguration](Get-CsCloudCallDataConnectorConfiguration.md) - -### [New-CsCloudCallDataConnectorConfiguration](New-CsCloudCallDataConnectorConfiguration.md) - -### [Set-CsCloudCallDataConnector](Set-CsCloudCallDataConnector.md) - -### [Set-CsCloudCallDataConnectorConfiguration](Set-CsCloudCallDataConnectorConfiguration.md) - -### [Get-CsTeamsCallingPolicy](Get-CsTeamsCallingPolicy.md) - -### [Set-CsTeamsCallingPolicy](Set-CsTeamsCallingPolicy.md) - -### [Grant-CsTeamsCallingPolicy](Grant-CsTeamsCallingPolicy.md) - -### [Get-CsTeamsMobilityPolicy](Get-CsTeamsMobilityPolicy.md) - -### [Set-CsTeamsMobilityPolicy](Set-CsTeamsMobilityPolicy.md) - -### [Grant-CsTeamsMobilityPolicy](Grant-CsTeamsMobilityPolicy.md) - -### [Set-CsTeamsMeetingBroadcastConfiguration](Set-CsTeamsMeetingBroadcastConfiguration.md) - -### [Get-CsTeamsMeetingBroadcastConfiguration](Get-CsTeamsMeetingBroadcastConfiguration.md) - -### [Get-CsTeamsMeetingPolicy](Get-CsTeamsMeetingPolicy.md) - -### [Set-CsTeamsMeetingPolicy](Set-CsTeamsMeetingPolicy.md) - -### [New-CsTeamsMeetingPolicy](New-CsTeamsMeetingPolicy.md) - -### [Grant-CsTeamsMeetingPolicy](Grant-CsTeamsMeetingPolicy.md) - -### [Remove-CsTeamsMeetingPolicy](Remove-CsTeamsMeetingPolicy.md) - -### [Set-CsAuthConfig](Set-CsAuthConfig.md) - -### [Get-CsAuthConfig](Get-CsAuthConfig.md) - -### [Get-CsOnlineSipDomain](Get-CsOnlineSipDomain.md) - -### [Enable-CsOnlineSipDomain](Enable-CsOnlineSipDomain.md) - -### [Disable-CsOnlineSipDomain](Disable-CsOnlineSipDomain.md) - -### [Get-CsTeamsMobilityPolicy](Get-CsTeamsMobilityPolicy.md) - -### [Get-CsTeamsCallParkPolicy](Get-CsTeamsCallParkPolicy.md) - -### [Set-CsTeamsCallParkPolicy](Set-CsTeamsCallParkPolicy.md) - -### [New-CsTeamsCallParkPolicy](New-CsTeamsCallParkPolicy.md) - -### [Grant-CsTeamsCallParkPolicy](Grant-CsTeamsCallParkPolicy.md) - -### [Remove-CsTeamsCallParkPolicy](Remove-CsTeamsCallParkPolicy.md) - -### [Get-CsTeamsComplianceRecordingPolicy](Get-CsTeamsComplianceRecordingPolicy.md) - -### [Set-CsTeamsComplianceRecordingPolicy](Set-CsTeamsComplianceRecordingPolicy.md) - -### [New-CsTeamsComplianceRecordingPolicy](New-CsTeamsComplianceRecordingPolicy.md) - -### [Remove-CsTeamsComplianceRecordingPolicy](Remove-CsTeamsComplianceRecordingPolicy.md) - -### [Grant-CsTeamsComplianceRecordingPolicy](Grant-CsTeamsComplianceRecordingPolicy.md) - -### [Get-CsTeamsComplianceRecordingApplication](Get-CsTeamsComplianceRecordingApplication.md) - -### [Set-CsTeamsComplianceRecordingApplication](Set-CsTeamsComplianceRecordingApplication.md) - -### [New-CsTeamsComplianceRecordingApplication](New-CsTeamsComplianceRecordingApplication.md) - -### [Remove-CsTeamsComplianceRecordingApplication](Remove-CsTeamsComplianceRecordingApplication.md) - -### [Set-CsOnlineApplicationInstance](Set-CsOnlineApplicationInstance.md) - -### [New-CsOnlineApplicationInstance](New-CsOnlineApplicationInstance.md) - -### [Get-CsOnlineApplicationInstance](Get-CsOnlineApplicationInstance.md) - -### [Get-CsTeamsChannelsPolicy](Get-CsTeamsChannelsPolicy.md) - -### [Set-CsTeamsChannelsPolicy](Set-CsTeamsChannelsPolicy.md) - -### [New-CsTeamsChannelsPolicy](New-CsTeamsChannelsPolicy.md) - -### [Grant-CsTeamsChannelsPolicy](Grant-CsTeamsChannelsPolicy.md) - -### [Remove-CsTeamsChannelsPolicy](Remove-CsTeamsChannelsPolicy.md) - -### [Get-CsTeamsAppPermissionPolicy](Get-CsTeamsAppPermissionPolicy.md) - -### [Set-CsTeamsAppPermissionPolicy](Set-CsTeamsAppPermissionPolicy.md) - -### [New-CsTeamsAppPermissionPolicy](New-CsTeamsAppPermissionPolicy.md) - -### [Grant-CsTeamsAppPermissionPolicy](Grant-CsTeamsAppPermissionPolicy.md) - -### [Remove-CsTeamsAppPermissionPolicy](Remove-CsTeamsAppPermissionPolicy.md) - -### [Get-CsTeamsEmergencyCallRoutingPolicy](Get-CsTeamsEmergencyCallRoutingPolicy.md) - -### [Get-CsTeamsEmergencyCallingPolicy](Get-CsTeamsEmergencyCallingPolicy.md) - -### [New-CsTeamsEmergencyCallRoutingPolicy](New-CsTeamsEmergencyCallRoutingPolicy.md) - -### [New-CsTeamsEmergencyCallingPolicy](New-CsTeamsEmergencyCallingPolicy.md) - -### [New-CsTeamsEmergencyNumber](New-CsTeamsEmergencyNumber.md) - -### [Remove-CsTeamsEmergencyCallRoutingPolicy](Remove-CsTeamsEmergencyCallRoutingPolicy.md) - -### [Remove-CsTeamsEmergencyCallingPolicy](Remove-CsTeamsEmergencyCallingPolicy.md) - -### [Set-CsTeamsEmergencyCallRoutingPolicy](Set-CsTeamsEmergencyCallRoutingPolicy.md) - -### [Set-CsTeamsEmergencyCallingPolicy](Set-CsTeamsEmergencyCallingPolicy.md) - -### [Get-CsTeamsUpgradeStatus](Get-CsTeamsUpgradeStatus.md) -{{Manually Enter Get-CsTeamsUpgradeStatus Description Here}} - -### [New-CsTeamsTranslationRule](New-CsTeamsTranslationRuley.md) - -### [Set-CsTeamsTranslationRule](Set-CsTeamsTranslationRuley.md) - -### [Get-CsTeamsTranslationRule](Get-CsTeamsTranslationRuley.md) - -### [Remove-CsTeamsTranslationRule](Remove-CsTeamsTranslationRuley.md) - -### [Get-CsInboundBlockedNumberPattern](Get-CsInboundBlockedNumberPattern.md) - -### [New-CsInboundBlockedNumberPattern](New-CsInboundBlockedNumberPattern.md) - -### [Remove-CsInboundBlockedNumberPattern](Remove-CsInboundBlockedNumberPattern.md) - -### [Set-CsInboundBlockedNumberPattern](Set-CsInboundBlockedNumberPattern.md) - -### [Test-CsInboundBlockedNumberPattern](Test-CsInboundBlockedNumberPattern.md) - -### [Get-CsTenantBlockedCallingNumbers](Get-CsTenantBlockedCallingNumbers.md) - -### [Set-CsTenantBlockedCallingNumbers](Set-CsTenantBlockedCallingNumbers) - diff --git a/spmt/docfx.json b/spmt/docfx.json index e81deb8333..44cc42e8b1 100644 --- a/spmt/docfx.json +++ b/spmt/docfx.json @@ -2,7 +2,9 @@ "build": { "content": [ { - "files": ["**/*.md"], + "files": [ + "**/*.md" + ], "src": "docs-conceptual", "version": "spmt-ps", "dest": "spmt", @@ -12,26 +14,37 @@ "README.md", "LICENSE", "LICENSE-CODE", - "ThirdPartyNotices"] + "ThirdPartyNotices" + ] }, { - "files": ["toc.yml"], + "files": [ + "toc.yml" + ], "src": "docs-conceptual", "version": "spmt-ps", "dest": "spmt/spmt-ps" }, { - "files": ["**/*.md"], - "src": "spmt-ps", - "version": "spmt-ps", - "dest": "module" - }, - { - "files": ["toc.yml"], - "src": "spmt-ps", - "version": "spmt-ps", - "dest": "module/spmt-ps" - } + "files": [ + "**/*.yml", + "**/spmt.md" + ], + "exclude": [ + "toc.yml" + ], + "src": "spmt-ps", + "version": "spmt-ps", + "dest": "module" + }, + { + "files": [ + "toc.yml" + ], + "src": "spmt-ps", + "version": "spmt-ps", + "dest": "module/spmt-ps" + } ], "resource": [ { @@ -53,18 +66,22 @@ "overwrite": [], "externalReference": [], "globalMetadata": { - "author" : "kenwith", - "ms.author" : "kenwith", - "manager" : "serdars", - "ms.topic" : "reference", - "ms.service" : "spmt-powershell", - "ms.devlang" : "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" + "uhfHeaderId": "MSDocsHeader-M365-IT", + "author": "serdarsoysal", + "ms.author": "serdars", + "manager": "serdars", + "ms.topic": "reference", + "ms.service": "spmt-powershell", + "products": [ + "https://authoring-docs-microsoft.poolparty.biz/devrel/9d7be3ef-f27c-4c7f-9eba-67c3cd429995", + "https://authoring-docs-microsoft.poolparty.biz/devrel/8bce367e-2e90-4b56-9ed5-5e4e9f3a2dc3" + ], + "ms.devlang": "powershell", + "feedback_system": "Standard", + "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" }, "fileMetadata": {}, "template": [], "dest": "spmt-ps" } -} \ No newline at end of file +} diff --git a/spmt/docs-conceptual/index.md b/spmt/docs-conceptual/index.md index d670842917..520cbb77ca 100644 --- a/spmt/docs-conceptual/index.md +++ b/spmt/docs-conceptual/index.md @@ -1,12 +1,14 @@ --- -localization_priority: Normal -title: Microsoft SharePoint Migration Tool cmdlet reference +ms.localizationpriority: medium +title: Microsoft SharePoint Migration Tool cmdlet help reference +ms.date: 01/01/2020 +description: "Learn about the Microsoft SharePoint Migration Tool PowerShell cmdlet help reference." --- -# Microsoft SharePoint Migration Tool cmdlet reference +# Microsoft SharePoint Migration Tool cmdlet help reference -Welcome to the Microsoft SharePoint Migration Tool PowerShell cmdlet help references. The Microsoft SharePoint Migration Tool cmdlets provide the command line interface for service administration and management. +Welcome to the Microsoft SharePoint Migration Tool PowerShell cmdlet **Help** reference. The Microsoft SharePoint Migration Tool cmdlets provide the command line interface for service administration and management. -Here you will find all of the Microsoft SharePoint Migration Tool PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. +Here, you will find all of the Microsoft SharePoint Migration Tool PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README. -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. \ No newline at end of file +The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page. diff --git a/spmt/docs-conceptual/intro.md b/spmt/docs-conceptual/intro.md index 80c18ef12a..7d2f08a7ba 100644 --- a/spmt/docs-conceptual/intro.md +++ b/spmt/docs-conceptual/intro.md @@ -1,14 +1,16 @@ --- -localization_priority: Normal +ms.localizationpriority: medium title: Microsoft SharePoint Migration Tool cmdlet reference +ms.date: 01/01/2020 +description: "Learn about Microsoft SharePoint Migration Tool cmdlets." --- # Microsoft SharePoint Migration Tool cmdlet reference Welcome to the Microsoft SharePoint Migration Tool PowerShell cmdlet help references. The Microsoft SharePoint Migration Tool cmdlets provide the command line interface for service administration and management. -Here you will find all of the Microsoft SharePoint Migration Tool PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. +Here you will find all of the Microsoft SharePoint Migration Tool PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. +The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page. -To find other modules you can use the PowerShell Module Browser located at: https://docs.microsoft.com/powershell/module. For example, to see the SharePoint modules you could use this query: https://docs.microsoft.com/powershell/module/?term=sharepoint. +To find other modules you can use the PowerShell Module Browser located at: `https://learn.microsoft.com/powershell/module`. For example, to see the SharePoint modules you could use this query: `https://learn.microsoft.com/powershell/module/?term=sharepoint`. diff --git a/spmt/docs-conceptual/overview.md b/spmt/docs-conceptual/overview.md index c6ba9ea695..d9f557df03 100644 --- a/spmt/docs-conceptual/overview.md +++ b/spmt/docs-conceptual/overview.md @@ -1,5 +1,7 @@ --- title: My overview +ms.date: 01/01/2020 +description: "Microsoft SharePoint Migration Tool cmdlet reference." --- # My overview diff --git a/spmt/mapping/monikerMapping.json b/spmt/mapping/MAML2Yaml/monikerMapping.json similarity index 100% rename from spmt/mapping/monikerMapping.json rename to spmt/mapping/MAML2Yaml/monikerMapping.json diff --git a/spmt/spmt-ps/spmt/Add-SPMTTask.md b/spmt/spmt-ps/spmt/Add-SPMTTask.md index 5e90414ee9..eb66f4701b 100644 --- a/spmt/spmt-ps/spmt/Add-SPMTTask.md +++ b/spmt/spmt-ps/spmt/Add-SPMTTask.md @@ -1,12 +1,12 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/add-spmttask +online version: https://learn.microsoft.com/powershell/module/spmt/add-spmttask applicable: SharePoint Migration Tool title: Add-SPMTTask schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -414,7 +414,7 @@ Accept wildcard characters: False ``` ### 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/spmt/spmt-ps/spmt/Get-SPMTMigration.md b/spmt/spmt-ps/spmt/Get-SPMTMigration.md index 3cd55ea15d..1e4b20d6a6 100644 --- a/spmt/spmt-ps/spmt/Get-SPMTMigration.md +++ b/spmt/spmt-ps/spmt/Get-SPMTMigration.md @@ -1,12 +1,12 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/get-spmtmigration +online version: https://learn.microsoft.com/powershell/module/spmt/get-spmtmigration applicable: SharePoint Migration Tool title: Get-SPMTMigration schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -75,7 +75,7 @@ This example starts a migration first, and then run "Get-SPMTMigration" to get t ## 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -83,4 +83,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES -## RELATED LINKS \ No newline at end of file +## RELATED LINKS diff --git a/spmt/spmt-ps/spmt/Register-SPMTMigration.md b/spmt/spmt-ps/spmt/Register-SPMTMigration.md index 4408af5b51..f092abf2ef 100644 --- a/spmt/spmt-ps/spmt/Register-SPMTMigration.md +++ b/spmt/spmt-ps/spmt/Register-SPMTMigration.md @@ -1,12 +1,12 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/register-spmtmigration +online version: https://learn.microsoft.com/powershell/module/spmt/register-spmtmigration applicable: SharePoint Migration Tool title: Register-SPMTMigration schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -19,7 +19,7 @@ After a session is registered, the user can add a migration task to the migratio ## SYNTAX ```powershell -Register-SPMTMigration [-SPOCredentials<PSCredential>] [-EnableMultiRound <bool>] [-ScanOnly <bool>] [-MigrateFilesAndFoldersWithInvalidChars <bool>] [-AzureActiveDirectoryLookup <bool>] [-CustomAzureAccessKey <string>] [-CustomAzureStorageAccount <bool>] [-DeleteTempFilesWhenMigrationDone <bool>] [-EnableEncryption <bool>] [-KeepAllVersions <bool>] [-MigrateFileVersionHistory <bool>] [-MigrateOneNoteFolderAsOneNoteNoteBook <bool>] [-MigrateFilesCreatedAfter <DateTime>] [-MigrateFilesModifiedAfter <DateTime>] [-SkipFilesWithExtension <string>] [-MigrateHiddenFiles <bool>] [-NumberOfVersionToMigrate <int>] [-PreserveUserPermissionsForFileShare <bool>] [-PreserveUserPermissionsForSharePointSource <bool>] [-SkipListWithAudienceTargetingEnabled <bool>] [-StartMigrationAutomaticallyWhenNoScanIssue <bool>] [-UseCustomAzureStorage <bool>] [-UserMappingFile <string>] [-MigrateAllSiteFieldsAndContentTypes<bool>] [-WorkingFolder <string>] [-SkipSitesWithName <string>] [-SkipListsWithName <string>] [-SkipContentTypesWithName <string>] [-DuplicatePageBehavior <string>] [-MigrateNavigation <string>] [-MigrateTermGroups <string>] -Force +Register-SPMTMigration [-SPOCredentials<PSCredential>] [-EnableMultiRound <bool>] [-ScanOnly <bool>] [-AzureActiveDirectoryLookup <bool>] [-CustomAzureAccessKey <string>] [-CustomAzureStorageAccount <bool>] [-DeleteTempFilesWhenMigrationDone <bool>] [-EnableEncryption <bool>] [-IgnoreUpdate <SwitchParameter>] [-KeepAllVersions <bool>] [-MigrateFileVersionHistory <bool>] [-MigrateOneNoteFolderAsOneNoteNoteBook <bool>] [-MigrateFilesCreatedAfter <DateTime>] [-MigrateFilesModifiedAfter <DateTime>] [-SkipFilesWithExtension <string>] [-IncludeHiddenFiles <bool>] [-NumberOfVersionToMigrate <int>] [-PreserveUserPermissionsForFileShare <bool>] [-PreserveUserPermissionsForSharePointSource <bool>] [-SkipListWithAudienceTargetingEnabled <bool>] [-StartMigrationAutomaticallyWhenNoScanIssue <bool>] [-UseCustomAzureStorage <bool>] [-UserMappingFile <string>] [-MigrateAllSiteFieldsAndContentTypes<bool>] [-WorkingFolder <string>] [-SkipSitesWithName <string>] [-SkipListsWithName <string>] [-SkipContentTypesWithName <string>] [-DuplicatePageBehavior <string>] [-MigrateNavigation <string>] [-MigrateTermGroups <string>] [-MigrateWithoutRootFolder] -Force ``` ## DESCRIPTION @@ -49,7 +49,7 @@ This example registers a migration session. ### -AzureActiveDirectoryLookup By default, this is set to On. -If no user mapping file is provided by the user, then Azure Active Directory is used as the default for user mapping. +If no user mapping file is provided by the user, then Microsoft Entra ID is used as the default for user mapping. ```yaml Type: Boolean @@ -219,23 +219,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MigrateFilesAndFoldersWithInvalidChars -The default is On. -Files and folders with invalid characters (for example:\<, \>, :, ", |, ?, *, /, \,\u007f) in the names will be migrated by default. -If set to Off, files and folders with invalid characters in names will not be migrated. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -MigrateFilesCreatedAfter If you choose to limit which files are to be migrated based on creation dates, set your values in this section. This may be to limit the number of files migrated or to adhere to overall company governance policy regarding to file retention. @@ -270,9 +253,9 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MigrateHiddenFiles -If set to On, hidden system files will be migrated. -By default, it is set to On. +### -IncludeHiddenFiles +If set to true, hidden system files will be migrated. +By default, it is set to true. ```yaml Type: Boolean @@ -449,8 +432,8 @@ Accept wildcard characters: False ``` ### -UserMappingFile -By default, Azure AD lookup is used to map users when submitting migration jobs. -If you choose to use a custom user mapping file and you want to preserve user permissions, turn off Azure Active Directory lookup.By doing so, if a user isn't found in the mapping file, the tool won't look it up in AAD. +By default, Microsoft Entra lookup is used to map users when submitting migration jobs. +If you choose to use a custom user mapping file and you want to preserve user permissions, turn off Microsoft Entra lookup.By doing so, if a user isn't found in the mapping file, the tool won't look it up in Microsoft Entra ID. ```yaml Type: String @@ -601,8 +584,23 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MigrateWithoutRootFolder +In file share migrations, use this parameter to migrate only the root folder's contents to the target. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/spmt/spmt-ps/spmt/Remove-SPMTTask.md b/spmt/spmt-ps/spmt/Remove-SPMTTask.md index 662f733216..a8c0c3f424 100644 --- a/spmt/spmt-ps/spmt/Remove-SPMTTask.md +++ b/spmt/spmt-ps/spmt/Remove-SPMTTask.md @@ -1,12 +1,12 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/remove-spmttask +online version: https://learn.microsoft.com/powershell/module/spmt/remove-spmttask applicable: SharePoint Migration Tool title: Remove-SPMTTask schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -101,7 +101,7 @@ Accept wildcard characters: False ### 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/spmt/spmt-ps/spmt/SharePointMigrationTool.md b/spmt/spmt-ps/spmt/SharePointMigrationTool.md new file mode 100644 index 0000000000..0faff30e0e --- /dev/null +++ b/spmt/spmt-ps/spmt/SharePointMigrationTool.md @@ -0,0 +1,35 @@ +--- +Module Name: SharePoint Migration Tool +Module Guid: joece26c-1775-4100-85c0-20c4d71eaa21 +title: SharePoint Migration Tool +--- + +# Microsoft SharePoint Migration Tool +## Description +The following migration cmdlets are based on the SharePoint Migration Tool (SPMT) migration engine. It will move files from File Share, SharePoint 2013 document libraries, or items of SharePoint 2013 lists to Office 365. + +[Install SPMT and Get PowerShell module](https://spmtreleasescus.blob.core.windows.net/install/default.htm "Install SPMT and Get PowerShell module") + +Notes: + +PowerShell 5.0 and .NET Framework 4.6.2 or higher are required to support the migration of file paths of up to 400 characters. + +After installing SPMT, the PowerShell dlls are copied to %userprofile%\Documents\WindowsPowerShell\Modules. + +## Microsoft Teams Cmdlets + +### [Add-SPMTTask](Add-SPMTTask.md) + +### [Get-SPMTMigration](Get-SPMTMigration.md) + +### [Register-SPMTMigration](Register-SPMTMigration.md) + +### [Remove-SPMTTask](Remove-SPMTTask.md) + +### [Show-SPMTMigration](Show-SPMTMigration.md) + +### [Start-SPMTMigration](Start-SPMTMigration.md) + +### [Stop-SPMTMigration](Stop-SPMTMigration.md) + +### [Unregister-SPMTMigration](Unregister-SPMTMigration.md) diff --git a/spmt/spmt-ps/spmt/Show-SPMTMigration.md b/spmt/spmt-ps/spmt/Show-SPMTMigration.md index 47cbe8560b..5d9ded7974 100644 --- a/spmt/spmt-ps/spmt/Show-SPMTMigration.md +++ b/spmt/spmt-ps/spmt/Show-SPMTMigration.md @@ -1,19 +1,19 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/show-spmtmigration +online version: https://learn.microsoft.com/powershell/module/spmt/show-spmtmigration applicable: SharePoint Migration Tool title: Show-SPMTMigration schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- # Show-SPMTMigration ## SYNOPSIS -If the user starts the migration with -NoShow parameter, running the ‘Show-SPMTMigration’ cmdlet will display the task ID, data source location, target location and migration status in the console. Pressing Ctrl+C will return to NoShow mode. +If the user starts the migration with -NoShow parameter, running the 'Show-SPMTMigration' cmdlet will display the task ID, data source location, target location and migration status in the console. Pressing Ctrl+C will return to NoShow mode. ## SYNTAX @@ -22,7 +22,7 @@ Show-SPMTMigration [<CommonParameters>] ``` ## DESCRIPTION -If the user starts the migration with -NoShow parameter, running the ‘Show-SPMTMigration’ cmdlet will display the task ID, data source location, target location and migration status in the console. Pressing Ctrl+C will return to NoShow mode. +If the user starts the migration with -NoShow parameter, running the 'Show-SPMTMigration' cmdlet will display the task ID, data source location, target location and migration status in the console. Pressing Ctrl+C will return to NoShow mode. ## EXAMPLES @@ -62,12 +62,12 @@ Start-SPMTMigration -NoShow Show-SPMTMigration ``` -This example, first, starts a migration with -NoShow parameter, then run ‘Show-SPMTMigration’, the migration task ID, data source location, target location and migration status will show up in the console. +This example, first, starts a migration with -NoShow parameter, then run 'Show-SPMTMigration', the migration task ID, data source location, target location and migration status will show up in the console. ## 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/spmt/spmt-ps/spmt/Start-SPMTMigration.md b/spmt/spmt-ps/spmt/Start-SPMTMigration.md index f4e6b75071..285f7f17c9 100644 --- a/spmt/spmt-ps/spmt/Start-SPMTMigration.md +++ b/spmt/spmt-ps/spmt/Start-SPMTMigration.md @@ -1,12 +1,12 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/start-spmtmigration +online version: https://learn.microsoft.com/powershell/module/spmt/start-spmtmigration applicable: SharePoint Migration Tool title: Start-SPMTMigration schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -99,7 +99,7 @@ Accept wildcard characters: False ``` ### 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/spmt/spmt-ps/spmt/Stop-SPMTMigration.md b/spmt/spmt-ps/spmt/Stop-SPMTMigration.md index c8686c609a..211d84a4ec 100644 --- a/spmt/spmt-ps/spmt/Stop-SPMTMigration.md +++ b/spmt/spmt-ps/spmt/Stop-SPMTMigration.md @@ -1,12 +1,12 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/stop-spmtmigration +online version: https://learn.microsoft.com/powershell/module/spmt/stop-spmtmigration applicable: SharePoint Migration Tool title: Stop-SPMTMigration schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -69,7 +69,7 @@ This example starts a migration first, then run "Stop-SPMTMigration" to cancel t ## 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/spmt/spmt-ps/spmt/Unregister-SPMTMigration.md b/spmt/spmt-ps/spmt/Unregister-SPMTMigration.md index 19b66959b1..173a2fee3e 100644 --- a/spmt/spmt-ps/spmt/Unregister-SPMTMigration.md +++ b/spmt/spmt-ps/spmt/Unregister-SPMTMigration.md @@ -1,12 +1,12 @@ --- -External help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml +external help file: Microsoft.SharePoint.MigrationTool.PowerShell.dll-Help.xml Module Name: Microsoft.SharePoint.MigrationTool.PowerShell -online version: https://docs.microsoft.com/powershell/module/spmt/unregister-spmtmigration +online version: https://learn.microsoft.com/powershell/module/spmt/unregister-spmtmigration applicable: SharePoint Migration Tool title: Unregister-SPMTMigration schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -69,7 +69,7 @@ This example cancels the started migration and unregister the migration session. ## 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](http://go.microsoft.com/fwlink/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/spmt/spmt-ps/spmt/spmt.md b/spmt/spmt-ps/spmt/spmt.md deleted file mode 100644 index d0b443701e..0000000000 --- a/spmt/spmt-ps/spmt/spmt.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -Module Name: SharePoint Migration Tool -Module Guid: joece26c-1775-4100-85c0-20c4d71eaa21 -Title: SharePoint Migration Tool -content_git_url: https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/spmt/spmt-ps/spmt/spmt.md ---- - -# Microsoft SharePoint Migration Tool -## Description -The following migration cmdlets are based on the SharePoint Migration Tool (SPMT) migration engine. It will move files from File Share, SharePoint 2013 document libraries, or items of SharePoint 2013 lists to Office 365. - -[Install SPMT and Get PowerShell module](https://spmtreleasescus.blob.core.windows.net/install/default.htm "Install SPMT and Get PowerShell module") - -Notes: - -PowerShell 5.0 and .NET Framework 4.6.2 or higher are required to support the migration of file paths of up to 400 characters. - -After installing SPMT, the PowerShell dlls are copied to %userprofile%\Documents\WindowsPowerShell\Modules. - -## Microsoft Teams Cmdlets - -### [Add-SPMTTask](Add-SPMTTask.md) - -### [Get-SPMTMigration](Get-SPMTMigration.md) - -### [Register-SPMTMigration](Register-SPMTMigration.md) - -### [Remove-SPMTTask](Remove-SPMTTask.md) - -### [Show-SPMTMigration](Show-SPMTMigration.md) - -### [Start-SPMTMigration](Start-SPMTMigration.md) - -### [Stop-SPMTMigration](Stop-SPMTMigration.md) - -### [Unregister-SPMTMigration](Unregister-SPMTMigration.md) diff --git a/staffhub/docfx.json b/staffhub/docfx.json deleted file mode 100644 index 8c85e45c60..0000000000 --- a/staffhub/docfx.json +++ /dev/null @@ -1,71 +0,0 @@ -{ - "build": { - "content": [ - { - "files": ["**/*.md"], - "src": "docs-conceptual", - "version": "staffhub-ps", - "dest": "staffhub", - "exclude": [ - "**/obj/**", - "**/includes/**", - "README.md", - "LICENSE", - "LICENSE-CODE", - "ThirdPartyNotices"] - }, - { - "files": ["toc.yml"], - "src": "docs-conceptual", - "version": "staffhub-ps", - "dest": "staffhub/staffhub-ps" - }, - { - "files": ["**/*.md"], - "src": "staffhub-ps", - "version": "staffhub-ps", - "dest": "module" - }, - { - "files": ["toc.yml"], - "src": "staffhub-ps", - "version": "staffhub-ps", - "dest": "module/staffhub-ps" - } - ], - "resource": [ - { - "files": [ - "**/*.png", - "**/*.jpg" - ], - "exclude": [ - "**/obj/**", - "**/includes/**" - ] - } - ], - "versions": { - "staffhub-ps": { - "dest": "staffhub-ps" - } - }, - "overwrite": [], - "externalReference": [], - "globalMetadata": { - "author" : "kenwith", - "ms.author" : "kenwith", - "manager" : "serdars", - "ms.date" : "09/25/2017", - "ms.topic" : "reference", - "ms.service" : "staffhub-powershell", - "ms.devlang" : "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" - }, - "fileMetadata": {}, - "template": [], - "dest": "staffhub-ps" - } -} \ No newline at end of file diff --git a/staffhub/docs-conceptual/LICENSE.txt b/staffhub/docs-conceptual/LICENSE.txt deleted file mode 100644 index 26d50e3e0f..0000000000 --- a/staffhub/docs-conceptual/LICENSE.txt +++ /dev/null @@ -1,190 +0,0 @@ -------------------------------------------- START OF LICENSE ----------------------------------------- - -Microsoft StaffHub PowerShell Cmdlets - -Copyright (c) Microsoft Corporation. All rights reserved. - -MIT License - -Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation -the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: -The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT -LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF -CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. - ------------------------------------------------ END OF LICENSE ------------------------------------------ - -THIRD PARTY SOFTWARE NOTICES -Do Not Translate or Localize - -This file is based on or incorporates material from the projects listed below (Third Party IP). The original copyright notice and the license under which Microsoft received such Third Party IP, are set forth below. Such licenses and notices are provided for informational purposes only. Microsoft licenses the Third Party IP to you under the licensing terms for the Microsoft product. Microsoft reserves all other rights not expressly granted under this agreement, whether by implication, estoppel or otherwise. -1. azure-sdk-for-net (Microsoft.Rest.ClientRuntime) #f5b4bee10d8a0264e5cd810e7ec1829209cda6b8 -2. azure-sdk-for-net (Microsoft.Rest.ClientRuntime.Azure) #f5b4bee10d8a0264e5cd810e7ec1829209cda6b8 -3. Json.NET v10.0.3 -4. azure-activedirectory-library-for-dotnet v3.17.0 - -START OF NOTICES AND INFORMATION for azure-sdk-for-net (Microsoft.Rest.ClientRuntime) #f5b4bee10d8a0264e5cd810e7ec1829209cda6b8 -========================================= -Copyright (c) 2015 Microsoft -https://github.com/Azure/azure-sdk-for-net/#readme --------------------------------------START OF LICENSE ------------------------------------------------------------ -MIT License -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ - -/azure-sdk-for-net-f5b4bee10d8a0264e5cd810e7ec1829209cda6b8/tools/AzCopy/Newtonsoft.Json.dll -Copyright (c) 2007 James Newton-King -https://github.com/JamesNK/Newtonsoft.Json --------------------------------------START OF LICENSE ------------------------------------------------------------ -The MIT License (MIT) -Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: -The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ -========================================= -END OF NOTICES AND INFORMATION for azure-sdk-for-net (Microsoft.Rest.ClientRuntime) #f5b4bee10d8a0264e5cd810e7ec1829209cda6b8 - -START OF NOTICES AND INFORMATION for azure-sdk-for-net (Microsoft.Rest.ClientRuntime.Azure) #f5b4bee10d8a0264e5cd810e7ec1829209cda6b8 -========================================= -Copyright (c) 2015 Microsoft -https://github.com/Azure/azure-sdk-for-net/#readme --------------------------------------START OF LICENSE ------------------------------------------------------------ -MIT License - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ - -/azure-sdk-for-net-f5b4bee10d8a0264e5cd810e7ec1829209cda6b8/tools/AzCopy/Newtonsoft.Json.dll -Copyright (c) 2007 James Newton-King -https://github.com/JamesNK/Newtonsoft.Json -------------------------------------START OF LICENSE ------------------------------------------------------------ -The MIT License (MIT) -Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: -The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ -========================================= -END OF NOTICES AND INFORMATION for azure-sdk-for-net (Microsoft.Rest.ClientRuntime.Azure) #f5b4bee10d8a0264e5cd810e7ec1829209cda6b8 - - -START OF NOTICES AND INFORMATION for Json.NET v10.0.3 -========================================= -Copyright (c) 2007 James Newton-King -https://github.com/JamesNK/Newtonsoft.Json --------------------------------------START OF LICENSE ------------------------------------------------------------ -MIT License - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ - -/Newtonsoft.Json-10.0.3/Src/Newtonsoft.Json/Utilities/LinqBridge.cs -LINQBridge Copyright (c) 2007-2009, Atif Aziz, Joseph Albahari -All rights reserved. --------------------------------------START OF LICENSE ------------------------------------------------------------ -BSD – 3 License -Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: -- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. -- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. -- Neither the name of the original authors nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. -THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ - -/Newtonsoft.Json-10.0.3/Src/Newtonsoft.Json/Utilities/ConvertUtils.cs -Copyright (c) .NET Foundation and Contributors -All rights reserved. -https://github.com/dotnet/coreclr/blob/master/src/classlibnative/bcltype/number.cpp#L451 --------------------------------------START OF LICENSE ------------------------------------------------------------ -The MIT License (MIT) -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ -========================================= -END OF NOTICES AND INFORMATION for Json.NET v10.0.3 - -START OF NOTICES AND INFORMATION for azure-activedirectory-library-for-dotnet v3.17.0 -========================================= -Copyright (c) Microsoft -https://github.com/AzureAD/azure-activedirectory-library-for-dotnet#readme --------------------------------------START OF LICENSE ------------------------------------------------------------ -MIT License -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. -----------------------------------------END OF LICENSE ------------------------------------------------------------ -========================================= -END OF NOTICES AND INFORMATION for azure-activedirectory-library-for-dotnet v3.17.0 diff --git a/staffhub/docs-conceptual/index.md b/staffhub/docs-conceptual/index.md deleted file mode 100644 index 5f8e698ed3..0000000000 --- a/staffhub/docs-conceptual/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Microsoft StaffHub cmdlet reference ---- - -# Microsoft StaffHub cmdlet reference - -Welcome to the Microsoft StaffHub cmdlet help references. The Microsoft StaffHub cmdlets provide the command line interface for service administration and management. - -Here you will find all of the Microsoft StaffHub PowerShell help topics. The reference documentation can be found here: https://docs.microsoft.com/powershell/module/staffhub/?view=staffhub-ps - -Instructions on installing the StaffHub cmdlet module can be found here: https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha - -These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. - -The repo is located here: https://github.com/MicrosoftDocs/office-docs-powershell and you can find the README displayed at the bottom of the page. diff --git a/staffhub/docs-conceptual/intro.md b/staffhub/docs-conceptual/intro.md deleted file mode 100644 index 5f8e698ed3..0000000000 --- a/staffhub/docs-conceptual/intro.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Microsoft StaffHub cmdlet reference ---- - -# Microsoft StaffHub cmdlet reference - -Welcome to the Microsoft StaffHub cmdlet help references. The Microsoft StaffHub cmdlets provide the command line interface for service administration and management. - -Here you will find all of the Microsoft StaffHub PowerShell help topics. The reference documentation can be found here: https://docs.microsoft.com/powershell/module/staffhub/?view=staffhub-ps - -Instructions on installing the StaffHub cmdlet module can be found here: https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha - -These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. - -The repo is located here: https://github.com/MicrosoftDocs/office-docs-powershell and you can find the README displayed at the bottom of the page. diff --git a/staffhub/docs-conceptual/overview.md b/staffhub/docs-conceptual/overview.md deleted file mode 100644 index c6ba9ea695..0000000000 --- a/staffhub/docs-conceptual/overview.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: My overview ---- - -# My overview - -This is an overview page \ No newline at end of file diff --git a/staffhub/docs-conceptual/toc.yml b/staffhub/docs-conceptual/toc.yml deleted file mode 100644 index 2f726b4da1..0000000000 --- a/staffhub/docs-conceptual/toc.yml +++ /dev/null @@ -1,5 +0,0 @@ -- name: Overview - href: index.md - items: - - name: Introduction - href: intro.md diff --git a/staffhub/mapping/monikerMapping.json b/staffhub/mapping/monikerMapping.json deleted file mode 100644 index 2439d024bf..0000000000 --- a/staffhub/mapping/monikerMapping.json +++ /dev/null @@ -1,11 +0,0 @@ -{ - "staffhub-ps": { - "conceptualToc": "docs-conceptual/toc.yml", - "conceptualTocUrl": "/powershell/staffhub/staffhub-ps/toc.json", - "referenceTocUrl": "/powershell/module/staffhub-ps/toc.json", - "packageRoot": "staffhub-ps", - "modules": { - "staffhub": {} - } - } -} \ No newline at end of file diff --git a/staffhub/staffhub-ps/staffhub/Add-StaffHubMember.md b/staffhub/staffhub-ps/staffhub/Add-StaffHubMember.md deleted file mode 100644 index a984f7ae36..0000000000 --- a/staffhub/staffhub-ps/staffhub/Add-StaffHubMember.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/add-staffhubmember -applicable: Microsoft StaffHub -title: Add-StaffHubMember -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Add-StaffHubMember - -## SYNOPSIS -Adds a member or manager to the specified team - -Note: This cmdlet currently is in Beta. - -## SYNTAX - -``` -Add-StaffHubMember [-TeamId] <String> [-FirstName] <String> [-LastName] <String> [[-Email] <String>] - [[-PhoneNumber] <String>] [-IsManager] <Boolean> -``` - -## DESCRIPTION -Adds a member or manager to the specified team. - -## EXAMPLES - -### Example 1 -```powershell -Add-StaffHubMember -TeamId "TEAM_1234" -FirstName "Abc" -LastName "123" -Email "abc@contoso.com" -IsManager $false -``` - -Adds the member with specified email/PhoneNumber to the team. Either PhoneNumber/Email is mandatory. - -## PARAMETERS - -### -Email -Office 365 email of the member to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -FirstName -First name of the member to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IsManager -Should the person be added as a manager. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LastName -Last name of the member to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PhoneNumber -Phone number of the member to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: False -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamId -ID of the team to which the member is to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet currently is in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Add-StaffHubShift.md b/staffhub/staffhub-ps/staffhub/Add-StaffHubShift.md deleted file mode 100644 index b2460e9ace..0000000000 --- a/staffhub/staffhub-ps/staffhub/Add-StaffHubShift.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/add-staffhubshift -applicable: Microsoft StaffHub -title: Add-StaffHubShift -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Add-StaffHubShift - -## SYNOPSIS -Adds a shift to the specified member in a team. - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Add-StaffHubShift [-Title] <String> [[-Notes] <String>] [-StartDateTime] <DateTime> [-EndDateTime] <DateTime> - [-ShiftType] <String> [-MemberId] <String> [-TeamId] <String> -``` - -## DESCRIPTION -Adds a shift to the specified member in a team. - -## EXAMPLES - -### Example 1 -```powershell -$startTime = Get-Date -Date "2018-01-01T00:10:00" -$endTime = Get-Date -Date "2018-01-01T04:10:00" -Add-StaffHubShift -Title "Title" -StartDateTime $startTime -EndDateTime $endTime -ShiftType Working -MemberId "MBER_1234" -TeamId "TEAM_1234" -``` - -Creates a shift for member MBER_1234 under the team TEAM_1234. - -## PARAMETERS - -### -EndDateTime -End time of the shift. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MemberId -Member to which the shift is to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Notes -Additional notes for the shift. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ShiftType -ShiftType - Working/Absence. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Accepted values: Working, Absence -Required: True -Position: 6 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDateTime -Start time of the shift. - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 4 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamId -ID of the team to which the shift is to be added. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Title -Title of the shift. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Add-StaffHubTeam.md b/staffhub/staffhub-ps/staffhub/Add-StaffHubTeam.md deleted file mode 100644 index 794f83b357..0000000000 --- a/staffhub/staffhub-ps/staffhub/Add-StaffHubTeam.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/add-staffhubteam -applicable: Microsoft StaffHub -title: Add-StaffHubTeam -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Add-StaffHubTeam - -## SYNOPSIS -Creates a team. - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Add-StaffHubTeam [-Name] <String> [-TimeZone] <String> [[-ManagerEmail] <String>] -``` - -## DESCRIPTION -Creates a team. - -## EXAMPLES - -### Example 1 -```powershell -Add-StaffHubTeam -Name "TeamFromCmdletTest" -TimeZone "Asia/Calcutta" -ManagerEmail "abc@contoso.com" -``` - -Creates a team with abc@contoso.com as manager. - -### Example 2 -```powershell -Add-StaffHubTeam -Name "TeamFromCmdletTest" -TimeZone "Asia/Calcutta" -``` - -Creates a team with the logged in user as manager. - -## PARAMETERS - -### -ManagerEmail -Organizational email of the member who should be the manager of the team. If not specified, the logged in user is assigned as the manager. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Name -Name of the team to be created. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TimeZone -TimeZone of the team. Format - tz database. -Reference: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Connect-StaffHub.md b/staffhub/staffhub-ps/staffhub/Connect-StaffHub.md deleted file mode 100644 index d60cb4704e..0000000000 --- a/staffhub/staffhub-ps/staffhub/Connect-StaffHub.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/connect-staffhub -applicable: Microsoft StaffHub -title: Connect-StaffHub -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Connect-StaffHub - -## SYNOPSIS -The `Connect-StaffHub` cmdlet connects an authenticated account to use for Microsoft StaffHub cmdlet requests. -You can use this authenticated account only with Microsoft StaffHub cmdlets. - -Note: The cmdlet is currently in Beta. - -## SYNTAX - -``` -Connect-StaffHub [[-Credentials] <PSCredential>] [[-LogLocation] <String>] [[-LogHistoryInDays] <Int32>] [[-CultureInfo] <String>] -``` - -## DESCRIPTION -The `Connect-StaffHub` cmdlet connects an authenticated account. This cmdlet authenticates a user for Staff Hub. -You can use this authenticated account only with Microsoft StaffHub cmdlets. - -## EXAMPLES - -### Example 1 -```powershell -Connect-StaffHub -Credentials $mycreds -``` - -LogIn the session with the specified credential. - -### Example 2 -```powershell -Connect-StaffHub -``` - -Prompts to enter credentials and then Log in. - -## PARAMETERS - -### -Credentials -PSCredential object of the credential. -Eg: $secpasswd = ConvertTo-SecureString "password" -AsPlainText -Force -$mycreds = New-Object System.Management.Automation.PSCredential ("username", $secpasswd) - -```yaml -Type: PSCredential -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -CultureInfo -CultureInfo in which the message is to be displayed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 3 -Default value: en-US -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogHistoryInDays -Number of days the logs are to be persisted. -Default value is 10 days. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 2 -Default value: 10 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LogLocation -Location where the logs are to be persisted in user's box. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -The cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Get-StaffHubMember.md b/staffhub/staffhub-ps/staffhub/Get-StaffHubMember.md deleted file mode 100644 index 3bd368b26d..0000000000 --- a/staffhub/staffhub-ps/staffhub/Get-StaffHubMember.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/get-staffhubmember -applicable: Microsoft StaffHub -title: Get-StaffHubMember -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Get-StaffHubMember - -## SYNOPSIS -Get details for all team members or for a specified team member. - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Get-StaffHubMember [-TeamId] <String> [[-MemberId] <String>] -``` - -## DESCRIPTION -Get details of team members. - -## EXAMPLES - -### Example 1 -```powershell -Get-StaffHubMember -TeamId "TEAM_1234" -MemberId MBER_1234 -``` - -Get the details of MBER_1234 in team TEAM_1234. - -### Example 2 -```powershell -Get-StaffHubMember -TeamId "TEAM_1234" -``` - -Get the details of all the members in team TEAM_1234. - -## PARAMETERS - -### -MemberId -MemberId for the specified member in the team. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamId -TeamId for which all the members are to be fetched. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Get-StaffHubShifts.md b/staffhub/staffhub-ps/staffhub/Get-StaffHubShifts.md deleted file mode 100644 index 15782a49a4..0000000000 --- a/staffhub/staffhub-ps/staffhub/Get-StaffHubShifts.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/get-staffhubshifts -applicable: Microsoft StaffHub -title: Get-StaffHubShifts -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Get-StaffHubShifts - -## SYNOPSIS -Note: This cmdlet is currently in Beta. -Get details of shifts for all team members or for a specified team member for the given time window. - -## SYNTAX - -``` -Get-StaffHubShifts [-TeamId] <String> [-StartDateTime] <DateTime> [-EndDateTime] <DateTime> - [[-MemberId] <String>] [<CommonParameters>] -``` - -## DESCRIPTION -Get details of the shifts for all team members or for a specified team member - -## EXAMPLES - -### Example 1 -```powershell -$startTime = Get-Date -Date "2018-01-01T00:10:00" -$endTime = Get-Date -Date "2018-01-01T04:10:00" -Get-StaffHubShifts -TeamId "TEAM_1234" -StartDateTime $startTime -EndDateTime $endTime -MemberId MBER_1234 -``` -Get the details of the shifts for MBER_1234 in the team TEAM_1234 between start time and end time - -### Example 2 -```powershell -$startTime = Get-Date -Date "2018-01-01T00:10:00" -$endTime = Get-Date -Date "2018-01-01T04:10:00" -Get-StaffHubShifts -TeamId "TEAM_1234" -StartDateTime $startTime -EndDateTime $endTime -``` - -Get the details of the shifts for all the members in team TEAM_1234 between start time and end time - -## PARAMETERS - -### -EndDateTime -EndDateTime for the time window between which shifts are to be fetched - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MemberId -MemberId of the member for which the shifts are to be fetched - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -StartDateTime -StartDateTime for the time window between which shifts are to be fetched - -```yaml -Type: DateTime -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamId -TeamId of the team for which the shifts are to be fetched - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/staffhub/staffhub-ps/staffhub/Get-StaffHubTeamsForTenant.md b/staffhub/staffhub-ps/staffhub/Get-StaffHubTeamsForTenant.md deleted file mode 100644 index 6227f34972..0000000000 --- a/staffhub/staffhub-ps/staffhub/Get-StaffHubTeamsForTenant.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/get-staffhubteamsfortenant -applicable: Microsoft StaffHub -title: Get-StaffHubTeamsForTenant -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Get-StaffHubTeamsForTenant - -## SYNOPSIS -Get all the teams in the tenant of the logged in user. - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Get-StaffHubTeamsForTenant [[-ContinuationToken] <String>] [[-Top] <Int32>] [[-ManagedBy] <StaffHub|Teams>] -``` - -## DESCRIPTION -Get all the teams in the tenant of the logged in user. -ContinuationToken from the call is stored in $nextToken Variable. -So the next call can be made like Get-StaffHubTeamsForTenant -Top 10 -ContinuationToken $nextToken. - -## EXAMPLES - -### Example 1 -```powershell -Get-StaffHubTeamsForTenant -Top 10 -``` - -Get first 10 teams in the tenant by ascending creation time order. -If 'Top' parameter is not specified, then it defaults it to 1000. -This returns a continuation token stored in $nextToken variable which can be used by the following call. -Eg: Get-StaffHubTeamsForTenant -Top 10 -ContinuationToken $nextToken. - -### Example 2 -```powershell -Get-StaffHubTeamsForTenant -``` - -Get all teams in the tenant with page size restricted to 1000 by default. - -### Example 3 -```powershell -Get-StaffHubTeamsForTenant -ManagedBy Teams -``` - -Return Teams that have not been created using StaffHub. - -## PARAMETERS - -### -ContinuationToken -Continuation Token returned by the previous call. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Top -Top 'n' items to be fetched sorted by ascending creation time order. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ManagedBy -Get Teams of a specific type. Valid values are: -- StaffHub -- Teams - -```yaml -Type: StaffHub | Teams -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 3 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Get-StaffHubUsersForTenant.md b/staffhub/staffhub-ps/staffhub/Get-StaffHubUsersForTenant.md deleted file mode 100644 index 1a927f8b52..0000000000 --- a/staffhub/staffhub-ps/staffhub/Get-StaffHubUsersForTenant.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/get-staffhubusersfortenant -applicable: Microsoft StaffHub -title: Get-StaffHubUsersForTenant -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Get-StaffHubUsersForTenant - -## SYNOPSIS -Note: This cmdlet is currently in Beta. -Get all the StaffHub users in the tenant of the logged in user. - -## SYNTAX - -``` -Get-StaffHubUsersForTenant [[-ContinuationToken] <String>] [[-Top] <Int32>] -``` - -## DESCRIPTION -Get all the StaffHub users in the tenant of the logged in user. -ContinuationToken from the call is stored in $nextToken variable. -Here is an example of the next call that can be made: Get-StaffHubUsersForTenant -Top 10 -ContinuationToken $nextToken - -## EXAMPLES - -### Example 1 -```powershell -Get-StaffHubUsersForTenant -Top 10 -``` - -Get first 10 StaffHub users in the tenant by ascending creation time order. -If 'Top' parameter is not specified, then it defaults to 1000. -This returns a continuation token stored in $nextToken variable which can be used by the following call. -Eg: Get-StaffHubUsersForTenant -Top 10 -ContinuationToken $nextToken - -### Example 2 -```powershell -Get-StaffHubUsersForTenant -``` - -Get all StaffHub users in the tenant with page size restricted to 1000 by default. - -## PARAMETERS - -### -ContinuationToken -Continuation Token returned by the previous call - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Top -Top 'n' items to be fetched sorted by ascending creation time order. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: False -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/staffhub/staffhub-ps/staffhub/Import-StaffHubMember.md b/staffhub/staffhub-ps/staffhub/Import-StaffHubMember.md deleted file mode 100644 index d57d697cef..0000000000 --- a/staffhub/staffhub-ps/staffhub/Import-StaffHubMember.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/import-staffhubmember -applicable: Microsoft StaffHub -title: Import-StaffHubMember -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Import-StaffHubMember - -## SYNOPSIS -Import a list of members and adds them to teams. - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Import-StaffHubMember [-Path] <String> [[-Encoding] <String>] -``` - -## DESCRIPTION - -Import a list of members and add them to teams. -Format of the file context - TeamId,FirstName,LastName,Email,PhoneNumber,IsManager. Either Email or PhoneNumber is required. -Eg: TEAM_1234,Staff,five,abc@contoso.com,True -Failure in adding one member does not stop the other members from getting added. - -## EXAMPLES - -### Example 1 -```powershell -Import-StaffHubMember -Path "C:\member.txt" -``` - -Imports the list of members from the file in the specified path. - -## PARAMETERS - -### -Encoding -Encoding type of the file. -https://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx - Encoding parameter value list - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Location of the file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Import-StaffHubShift.md b/staffhub/staffhub-ps/staffhub/Import-StaffHubShift.md deleted file mode 100644 index 4916756fb3..0000000000 --- a/staffhub/staffhub-ps/staffhub/Import-StaffHubShift.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/import-staffhubshift -applicable: Microsoft StaffHub -title: Import-StaffHubShift -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Import-StaffHubShift - -## SYNOPSIS -Imports a list of shifts and adds them to members in the specified teams. - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Import-StaffHubShift [-Path] <String> [[-Encoding] <String>] -``` - -## DESCRIPTION - -Imports a list of shifts and adds them to members in the specified teams. -Format of the file content - Title,Notes,StartDateTime,EndDateTime,ShiftType,MemberId,TeamId -Eg: Title,Notes,2018-11-28T00:00:00Z,2018-11-28T02:00:00Z,Working,MBER_1234,TEAM_1234 -Failure in adding one shift does not stop the other shifts from getting added. - -## EXAMPLES - -### Example 1 -```powershell -Import-StaffHubShift -Path "C:\shift.txt" -``` - -Imports the list of shifts from the file in the specified path. - -## PARAMETERS - -### -Encoding -Encoding type of the file -https://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx - Encoding parameter value list - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Location of the file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Import-StaffHubTeam.md b/staffhub/staffhub-ps/staffhub/Import-StaffHubTeam.md deleted file mode 100644 index d486c3a726..0000000000 --- a/staffhub/staffhub-ps/staffhub/Import-StaffHubTeam.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/import-staffhubteam -applicable: Microsoft StaffHub -title: Import-StaffHubTeam -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Import-StaffHubTeam - -## SYNOPSIS -Imports a set of teams from a specified file - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Import-StaffHubTeam [-Path] <String> [[-Encoding] <String>] -``` - -## DESCRIPTION - -Imports a set of teams from a specified file. -Format of the File content - Name,TimeZone,ManagerEmail -Eg: CmdletTestTeam,Asia/Calcutta,abc@contoso.com -Failure in adding one team does not stop the other teams from getting added. - -## EXAMPLES - -### Example 1 -```powershell -Import-StaffHubTeam -Path "C:\team.txt" -``` - -Imports a list of teams from the file in the specified path. - -## PARAMETERS - -### -Encoding -Encoding type of the file -https://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx - Encoding parameter value list - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Path -Location of the file. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Remove-StaffHubMember.md b/staffhub/staffhub-ps/staffhub/Remove-StaffHubMember.md deleted file mode 100644 index 31b987224a..0000000000 --- a/staffhub/staffhub-ps/staffhub/Remove-StaffHubMember.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/remove-staffhubmember -applicable: Microsoft StaffHub -title: Remove-StaffHubMember -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Remove-StaffHubMember - -## SYNOPSIS -Removes the specified member from the team. - -Note: This cmdlet is currently in Beta. - -## SYNTAX - -``` -Remove-StaffHubMember [-TeamId] <String> [[-MemberId] <String>] [[-MemberObject] <PSObject>] -``` - -## DESCRIPTION -Removes the specified member from the team. - -## EXAMPLES - -### Example 1 -```powershell -Remove-StaffHubMember -TeamId "TEAM_1234" -MemberId "MBER_1234" -``` - -This removes member MBER_1234 from TEAM_1234. - -## PARAMETERS - -### -MemberId -MemberId of the member to be removed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -MemberObject -Entire member object returned from `Get-StaffHubMember`. - -```yaml -Type: PSObject -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: False -Position: 2 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -TeamId -TeamId from which the specified member is to be removed. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## NOTES - -This cmdlet is currently in Beta. - -## RELATED LINKS - -[MicrosoftStaffHub Module in Gallery](https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha) diff --git a/staffhub/staffhub-ps/staffhub/Remove-StaffHubUser.md b/staffhub/staffhub-ps/staffhub/Remove-StaffHubUser.md deleted file mode 100644 index 7be8301000..0000000000 --- a/staffhub/staffhub-ps/staffhub/Remove-StaffHubUser.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -external help file: Microsoft.OutlookApps.StaffHub.PowershellCmdlets.dll-Help.xml -Module Name: Microsoft.OutlookApps.StaffHub.PowershellCmdlets -online version: https://docs.microsoft.com/powershell/module/staffhub/remove-staffhubuser -applicable: Microsoft StaffHub -title: Remote-StaffHubUser -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Remove-StaffHubUser - -## SYNOPSIS -Note: This cmdlet is currently in Beta. -Removes the specified user from StaffHub (Only for users deleted in AAD already) - -## SYNTAX - -``` -Remove-StaffHubUser [-UserId] <String> -``` - -## DESCRIPTION -Removes the specified user from StaffHub. -Pre-requisite is to delete the user from AAD. - -## EXAMPLES - -### Example 1 -```powershell -Remove-StaffHubUser -UserId "USER_1234" -``` - -This removes the user "USER_1234" from StaffHub, if the user has been deleted in AAD already. - -## PARAMETERS - -### -UserId -UserId of the user to be removed from StaffHub - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Microsoft StaffHub - -Required: True -Position: 0 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -## INPUTS - -### None - - -## OUTPUTS - -### System.Object - -## NOTES - -## RELATED LINKS diff --git a/staffhub/staffhub-ps/staffhub/staffhub.md b/staffhub/staffhub-ps/staffhub/staffhub.md deleted file mode 100644 index 2bf9da8d78..0000000000 --- a/staffhub/staffhub-ps/staffhub/staffhub.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -Module Name: Microsoft StaffHub PowerShell -Module Guid: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -title: staffhub ---- - -# Microsoft StaffHub PowerShell - -## Description - -The following cmdlet references are for Microsoft StaffHub. - -## StaffHub Cmdlets - -### [Add-StaffHubMember](Add-StaffHubMember.md) -{{Manually Enter Add-StaffHubMember Description Here}} - -### [Add-StaffHubShift](Add-StaffHubShift.md) -{{Manually Enter Add-StaffHubShift Description Here}} - -### [Add-StaffHubTeam](Add-StaffHubTeam.md) -{{Manually Enter Add-StaffHubTeam Description Here}} - -### [Connect-StaffHub](Connect-StaffHub.md) -{{Manually Enter Connect-StaffHub Description Here}} - -### [Get-StaffHubMember](Get-StaffHubMember.md) -{{Manually Enter Get-StaffHubMember Description Here}} - -### [Get-StaffHubShifts](Get-StaffHubShifts.md) -{{Manually Enter Get-StaffHubShifts Description Here}} - -### [Get-StaffHubTeamsForTenant](Get-StaffHubTeamsForTenant.md) -{{Manually Enter Get-StaffHubTeamsForTenant Description Here}} - -### [Get-StaffHubUsersForTenant](Get-StaffHubUsersForTenant.md) -{{Manually Enter Get-StaffHubUsersForTenant Description Here}} - -### [Import-StaffHubMember](Import-StaffHubMember.md) -{{Manually Enter Import-StaffHubMember Description Here}} - -### [Import-StaffHubShift](Import-StaffHubShift.md) -{{Manually Enter Import-StaffHubShift Description Here}} - -### [Import-StaffHubTeam](Import-StaffHubTeam.md) -{{Manually Enter Import-StaffHubTeam Description Here}} - -### [Remove-StaffHubMember](Remove-StaffHubMember.md) -{{Manually Enter Remove-StaffHubMember Description Here}} - -### [Remove-StaffHubUser](Remove-StaffHubUser.md) -{{Manually Enter Remove-StaffHubUser Description Here}} diff --git a/teams/LICENSE.txt b/teams/LICENSE.txt new file mode 100644 index 0000000000..51f5ba2f39 --- /dev/null +++ b/teams/LICENSE.txt @@ -0,0 +1,76 @@ +Your use of the Microsoft Teams PowerShell is subject to the terms and conditions of the agreement you agreed to when you signed up for the Microsoft Teams subscription and by which you acquired a license for the software. For instance, if you are: + +• a volume license customer, use of this software is subject to your volume license agreement. +• a Microsoft Online Subscription customer, use of this software is subject to the Microsoft Online Subscription agreement. + +You may not use the service or software if you have not validly acquired a license from Microsoft or its licensed distributors. + +----------------START OF THIRD PARTY NOTICE-------------------------------- +The software includes the Polly library ("Polly"). The New BSD License set out below is provided for informational purposes only. It is not the license that governs any part of the software. + +Copyright (c) 2015-2020, App vNext +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are met: + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + * Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + * Neither the name of App vNext nor the + names of its contributors may be used to endorse or promote products + derived from this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND +ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY +DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND +ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +---END OF LICENSE--------- + +The software includes the Polly.Contrib.WaitAndRetry library ("Polly-Contrib"). The New BSD License set out below is provided for informational purposes only. It is not the license that governs any part of the software. + +Copyright (c) 2015-2020, App vNext and contributors +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are met: + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + * Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + * Neither the name of App vNext nor the + names of its contributors may be used to endorse or promote products + derived from this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND +ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY +DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND +ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +---END OF LICENSE--------- + +The software includes Newtonsoft.Json. The MIT License set out below is provided for informational purposes only. It is not the license that governs any part of the software. + +Newtonsoft.Json + +The MIT License (MIT) +Copyright (c) 2007 James Newton-King +Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: +The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +---END OF LICENSE--------- + +-------------END OF THIRD PARTY NOTICE---------------------------------------- diff --git a/teams/docfx.json b/teams/docfx.json index d2d135bfc9..401d0beb8b 100644 --- a/teams/docfx.json +++ b/teams/docfx.json @@ -21,7 +21,8 @@ "dest": "teams/teams-ps" }, { - "files": ["**/*.md"], + "files": ["**/*.yml"], + "exclude": ["toc.yml"], "src": "teams-ps", "version": "teams-ps", "dest": "module" @@ -53,19 +54,22 @@ "overwrite": [], "externalReference": [], "globalMetadata": { - "author" : "kenwith", - "ms.author" : "kenwith", + "uhfHeaderId": "MSDocsHeader-MicrosoftTeams", + "author" : "serdarsoysal", + "ms.author" : "serdars", "manager" : "serdars", - "ms.date" : "09/25/2017", "ms.topic" : "reference", "ms.service" : "teams-powershell", + "products" : [ + "https://authoring-docs-microsoft.poolparty.biz/devrel/63959238-cb90-4871-a33d-4a5519097e47", + "https://authoring-docs-microsoft.poolparty.biz/devrel/8bce367e-2e90-4b56-9ed5-5e4e9f3a2dc3" + ], "ms.devlang" : "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" + "feedback_system": "Standard", + "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" }, "fileMetadata": {}, "template": [], "dest": "teams-ps" } -} \ No newline at end of file +} diff --git a/teams/docs-conceptual/index.md b/teams/docs-conceptual/index.md index 7e37d40427..83c900e736 100644 --- a/teams/docs-conceptual/index.md +++ b/teams/docs-conceptual/index.md @@ -1,14 +1,16 @@ --- -localization_priority: Normal -title: Microsoft Teams cmdlet reference +ms.localizationpriority: medium +title: Microsoft Teams cmdlet help reference +ms.date: 01/01/2020 +description: "Learn about the Microsoft Teams PowerShell cmdlet help reference." --- -# Microsoft Teams cmdlet reference +# Microsoft Teams cmdlet help reference -Welcome to the Microsoft Teams PowerShell cmdlet help references. Cmdlets for managing Microsoft Teams service are split between two powershell modules: the Skype for Business Online module and the Microsoft Teams module. +Welcome to the Microsoft Teams PowerShell cmdlet **Help** reference. -This powershell module is used for provisioning and management of teams and their backing groups themselves. The module can be installed here: https://www.powershellgallery.com/packages/MicrosoftTeams/ . To manage the policies and configurations that apply to the Microsoft Teams service, please see the reference docs for the Skype for Business module: https://docs.microsoft.com/powershell/module/skype/?view=skype-ps +This PowerShell module is used for provisioning and management of teams and their backing groups themselves. The module can be installed here: <https://www.powershellgallery.com/packages/MicrosoftTeams/>. -Here you will find all of the Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. +Here, you will find all of the Microsoft Teams PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README. -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. +The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page. diff --git a/teams/docs-conceptual/intro.md b/teams/docs-conceptual/intro.md deleted file mode 100644 index 7e37d40427..0000000000 --- a/teams/docs-conceptual/intro.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -localization_priority: Normal -title: Microsoft Teams cmdlet reference ---- - -# Microsoft Teams cmdlet reference - -Welcome to the Microsoft Teams PowerShell cmdlet help references. Cmdlets for managing Microsoft Teams service are split between two powershell modules: the Skype for Business Online module and the Microsoft Teams module. - -This powershell module is used for provisioning and management of teams and their backing groups themselves. The module can be installed here: https://www.powershellgallery.com/packages/MicrosoftTeams/ . To manage the policies and configurations that apply to the Microsoft Teams service, please see the reference docs for the Skype for Business module: https://docs.microsoft.com/powershell/module/skype/?view=skype-ps - -Here you will find all of the Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. - -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. diff --git a/teams/docs-conceptual/overview.md b/teams/docs-conceptual/overview.md index c6ba9ea695..e4b420d32e 100644 --- a/teams/docs-conceptual/overview.md +++ b/teams/docs-conceptual/overview.md @@ -1,5 +1,7 @@ --- title: My overview +ms.date: 01/01/2020 +description: "Microsoft Teams cmdlet help reference." --- # My overview diff --git a/teams/docs-conceptual/toc.yml b/teams/docs-conceptual/toc.yml index 2f726b4da1..1ba183cc0b 100644 --- a/teams/docs-conceptual/toc.yml +++ b/teams/docs-conceptual/toc.yml @@ -1,5 +1,2 @@ - name: Overview href: index.md - items: - - name: Introduction - href: intro.md diff --git a/teams/mapping/monikerMapping.json b/teams/mapping/MAML2Yaml/monikerMapping.json similarity index 100% rename from teams/mapping/monikerMapping.json rename to teams/mapping/MAML2Yaml/monikerMapping.json diff --git a/teams/teams-ps/teams/Add-TeamChannelUser.md b/teams/teams-ps/teams/Add-TeamChannelUser.md index 6df27a1141..dcc55539d1 100644 --- a/teams/teams-ps/teams/Add-TeamChannelUser.md +++ b/teams/teams-ps/teams/Add-TeamChannelUser.md @@ -1,7 +1,8 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/add-teamchanneluser +online version: https://learn.microsoft.com/powershell/module/teams/add-teamchanneluser +title: Add-TeamChannelUser schema: 2.0.0 --- @@ -10,21 +11,19 @@ schema: 2.0.0 ## SYNOPSIS Adds an owner or member to the private channel. -Note: the command will return immediately, but the Teams application will not reflect the update immediately, please refresh the members page to see the update. +The command will return immediately, but the Teams application will not reflect the update immediately. To see the update you should refresh the members page. -To turn an existing Member into an Owner, first Add-TeamChannelUser -User foo to add them to the members list, then Add-TeamChannelUser -User foo -Role Owner to add them to owner list. +Note: Technical limitations of private channels apply. To add a user as a member to a channel, they need to first be a member of the team. To make a user an owner of a channel, they need to first be a member of the channel. ## SYNTAX ``` -Add-TeamChannelUser -GroupId <String> -DisplayName <String> -User <String> [-Role <String>] - [<CommonParameters>] +Add-TeamChannelUser -GroupId <String> -DisplayName <String> -User <String> [-Role <String>] [-TenantId <String>] [<CommonParameters>] ``` ## DESCRIPTION -> [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. +Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see [Install Teams PowerShell public preview](https://learn.microsoft.com/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview) and also see [Microsoft Teams PowerShell Release Notes](https://learn.microsoft.com/microsoftteams/teams-powershell-release-notes). ## EXAMPLES @@ -42,6 +41,13 @@ Add-TeamChannelUser -GroupId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df -DisplayName " Promote user dmx@example.com to an owner of private channel with name "Engineering" under the given group. +### Example 3 +``` +Add-TeamChannelUser -GroupId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df -DisplayName "Engineering" -User 0e4249a7-6cfd-8c93-a510-91cda44c8c73 -TenantId dcd143cb-c4ae-4364-9faf-e1c3242bf4ff +``` + +Adds external user 0e4249a7-6cfd-8c93-a510-91cda44c8c73 to a shared channel. + ## PARAMETERS ### -GroupId @@ -105,12 +111,28 @@ Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` +### -TenantId +TenantId of the external user + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). ## INPUTS -### GroupId, DisplayName, User, Role +### GroupId, DisplayName, User, Role, TenantId + ## OUTPUTS ## NOTES diff --git a/teams/teams-ps/teams/Add-TeamUser.md b/teams/teams-ps/teams/Add-TeamUser.md index 5eb0a41bd4..91f29ce8bb 100644 --- a/teams/teams-ps/teams/Add-TeamUser.md +++ b/teams/teams-ps/teams/Add-TeamUser.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/add-teamuser +online version: https://learn.microsoft.com/powershell/module/teams/add-teamuser +title: Add-TeamUser schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -22,7 +23,7 @@ Add-TeamUser -GroupId <String> -User <String> [-Role <String>] [<CommonParameter This cmdlet adds an owner or member to the team, and to the unified group which backs the team. > [!Note] -> The command will return immediately, but the Teams application will not reflect the update immediately. The change can take between 24 and 48 hours to appear within the Teams client. +> The command will return immediately, but the Teams application will not reflect the update immediately. The change can take between 24 and 48 hours to appear within the Teams client. ## EXAMPLES @@ -66,7 +67,7 @@ Accept wildcard characters: False ``` ### -Role -Member or Owner. If Owner is specified then the user is also added as a member to the Team backed by unified group. +Member or Owner. If Owner is specified then the user is also added as a member to the Team backed by unified group. ```yaml Type: String @@ -81,8 +82,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Add-TeamsAppInstallation.md b/teams/teams-ps/teams/Add-TeamsAppInstallation.md index 9185033f78..031a1aa094 100644 --- a/teams/teams-ps/teams/Add-TeamsAppInstallation.md +++ b/teams/teams-ps/teams/Add-TeamsAppInstallation.md @@ -1,11 +1,9 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/add-teamsappinstallation +online version: https://learn.microsoft.com/powershell/module/teams/add-teamsappinstallation +title: Add-TeamsAppInstallation schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: --- # Add-TeamsAppInstallation @@ -28,6 +26,8 @@ Add-TeamsAppInstallation -AppId <String> -UserId <String> [-Permissions <String> ## DESCRIPTION Add a Teams App to Microsoft Teams. +Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see [Install Teams PowerShell public preview](https://learn.microsoft.com/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview) and also see [Microsoft Teams PowerShell Release Notes](https://learn.microsoft.com/microsoftteams/teams-powershell-release-notes). + ## EXAMPLES ### Example 1 @@ -37,6 +37,13 @@ PS C:\> Add-TeamsAppInstallation -AppId b9cc7986-dd56-4b57-ab7d-9c4e5288b775 -Te This example adds a Teams App to Microsoft Teams. +### Example 2 +```powershell +PS C:\> Add-TeamsAppInstallation -AppId b9cc7986-dd56-4b57-ab7d-9c4e5288b775 -TeamId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df -Permissions "TeamSettings.Read.Group ChannelMessage.Read.Group" +``` + +This example adds a Teams App to Microsoft Teams with RSC Permissions. + ## PARAMETERS ### -AppId @@ -109,6 +116,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Clear-CsOnlineTelephoneNumberOrder.md b/teams/teams-ps/teams/Clear-CsOnlineTelephoneNumberOrder.md new file mode 100644 index 0000000000..36eee8cbf2 --- /dev/null +++ b/teams/teams-ps/teams/Clear-CsOnlineTelephoneNumberOrder.md @@ -0,0 +1,102 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/clear-csonlinetelephonenumberorder +Module Name: MicrosoftTeams +title: Clear-CsOnlineTelephoneNumberOrder +schema: 2.0.0 +manager: mreddy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: julienp +--- + +# Clear-CsOnlineTelephoneNumberOrder + +## SYNOPSIS + +Use the `Clear-CsOnlineTelephoneNumberOrder` cmdlet to cancel a specific telephone number search order and release the telephone numbers. The telephone numbers can then be available for search and acquire. + +## SYNTAX + +``` +Clear-CsOnlineTelephoneNumberOrder [-OrderId] <OrderId> [<CommonParameters>] +``` + +## DESCRIPTION + +Use the `Clear-CsOnlineTelephoneNumberOrder` cmdlet to cancel a specific telephone number search order and release the telephone numbers. The telephone numbers can then be available for search and acquire. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Clear-CsOnlineTelephoneNumberOrder -OrderId 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 +PS C:\> Get-CsOnlineTelephoneNumberOrder -OrderId 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 + +AreaCode : +CivicAddressId : +CountryCode : US +CreatedAt : 8/23/2021 5:43:44 PM +Description : test +ErrorCode : NoError +Id : 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 +InventoryType : Subscriber +IsManual : False +Name : test +NumberPrefix : 1718 +NumberType : UserSubscriber +Quantity : 1 +ReservationExpiryDate : 8/23/2021 5:59:45 PM +SearchType : Prefix +SendToServiceDesk : False +Status : Cancelled +TelephoneNumber : {Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.TelephoneNumberSearchResult} + +PS C:\> $order.TelephoneNumber + +Location TelephoneNumber +-------- --------------- +New York City +17182000004 +``` + +This example cancels the purchase of the telephone number order containing the phone number +17182000004. + +## PARAMETERS + +### OrderId +Specifies the telephone number search order to look up. Use `New-CsOnlineTelephoneNumberOrder` to create a search order to obtain a search order Id. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineTelephoneNumberCountry](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry) + +[Get-CsOnlineTelephoneNumberType](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbertype) + +[New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) + +[Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) + +[Complete-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/complete-csonlinetelephonenumberorder) + +[Clear-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/clear-csonlinetelephonenumberorder) diff --git a/teams/teams-ps/teams/Clear-TeamsEnvironmentConfig.md b/teams/teams-ps/teams/Clear-TeamsEnvironmentConfig.md new file mode 100644 index 0000000000..62e51c733c --- /dev/null +++ b/teams/teams-ps/teams/Clear-TeamsEnvironmentConfig.md @@ -0,0 +1,53 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Connect.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/clear-teamsenvironmentconfig +title: Clear-TeamsEnvironmentConfig +schema: 2.0.0 +author: VikneshMSFT +ms.author: vimohan +ms.reviewer: pbafna +manager: vinelap +--- + +# Clear-TeamsEnvironmentConfig + +## SYNOPSIS +Clears environment-specific configurations from the local machine set by running Set-TeamsEnvironmentConfig. + +## SYNTAX + +``` +Clear-TeamsEnvironmentConfig [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet clears environment-specific configurations from the local machine set by running Set-TeamsEnvironmentConfig. This helps in clearing and rectifying any wrong information set in Set-TeamsEnvironmentConfig. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Clear-TeamsEnvironmentConfig +``` + +Clears environment-specific configurations from the local machine set by running Set-TeamsEnvironmentConfig. + +## 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +We do not recommend using Clear-TeamsEnvironmentConfig in Commercial, GCC, GCC High, or DoD environments. This cmdlet is available in Microsoft Teams PowerShell module from version 5.2.0-GA. + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Complete-CsOnlineTelephoneNumberOrder.md b/teams/teams-ps/teams/Complete-CsOnlineTelephoneNumberOrder.md new file mode 100644 index 0000000000..8e367470c6 --- /dev/null +++ b/teams/teams-ps/teams/Complete-CsOnlineTelephoneNumberOrder.md @@ -0,0 +1,102 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/complete-csonlinetelephonenumberorder +Module Name: MicrosoftTeams +title: Complete-CsOnlineTelephoneNumberOrder +schema: 2.0.0 +manager: mreddy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: julienp +--- + +# Complete-CsOnlineTelephoneNumberOrder + +## SYNOPSIS + +Use the `Complete-CsOnlineTelephoneNumberOrder` cmdlet to complete a specific telephone number search order and confirm the purchase of the new telephone numbers. The telephone numbers can then be used to set up calling features for users and services in your organization. + +## SYNTAX + +``` +Complete-CsOnlineTelephoneNumberOrder [-OrderId] <OrderId> [<CommonParameters>] +``` + +## DESCRIPTION + +Use the `Complete-CsOnlineTelephoneNumberOrder` cmdlet to complete a specific telephone number search order and confirm the purchase of the new telephone numbers. The telephone numbers can then be used to set up calling features for users and services in your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Complete-CsOnlineTelephoneNumberOrder -OrderId 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 +PS C:\> Get-CsOnlineTelephoneNumberOrder -OrderId 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 | fl + +AreaCode : +CivicAddressId : +CountryCode : US +CreatedAt : 8/23/2021 5:43:44 PM +Description : test +ErrorCode : NoError +Id : 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 +InventoryType : Subscriber +IsManual : False +Name : test +NumberPrefix : 1718 +NumberType : UserSubscriber +Quantity : 1 +ReservationExpiryDate : 8/23/2021 5:59:45 PM +SearchType : Prefix +SendToServiceDesk : False +Status : Completed +TelephoneNumber : {Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.TelephoneNumberSearchResult} + +PS C:\> (Get-CsOnlineTelephoneNumberOrder -OrderId 1efd85ca-dd46-41b3-80a0-2e4c5f87c912).TelephoneNumber + +Location TelephoneNumber +-------- --------------- +New York City +17182000004 +``` + +This example completes the purchase of the telephone number order containing the phone number +17182000004. + +## PARAMETERS + +### OrderId +Specifies the telephone number search order to look up. Use `New-CsOnlineTelephoneNumberOrder` to create a search order to obtain a search order Id. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineTelephoneNumberCountry](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry) + +[Get-CsOnlineTelephoneNumberType](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbertype) + +[New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) + +[Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) + +[Complete-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/complete-csonlinetelephonenumberorder) + +[Clear-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/clear-csonlinetelephonenumberorder) diff --git a/teams/teams-ps/teams/Connect-MicrosoftTeams.md b/teams/teams-ps/teams/Connect-MicrosoftTeams.md index c97a1c0c99..c713e2275a 100644 --- a/teams/teams-ps/teams/Connect-MicrosoftTeams.md +++ b/teams/teams-ps/teams/Connect-MicrosoftTeams.md @@ -1,55 +1,236 @@ --- external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/connect-microsoftteams +online version: https://learn.microsoft.com/powershell/module/teams/connect-microsoftteams +title: Connect-MicrosoftTeams schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- # Connect-MicrosoftTeams ## SYNOPSIS -The Connect-MicrosoftTeams cmdlet connects an authenticated account to use for Microsoft Teams cmdlet requests. -You can use this authenticated account only with Microsoft Teams cmdlets. +The Connect-MicrosoftTeams cmdlet connects an authenticated account for use with cmdlets from the MicrosoftTeams module. ## SYNTAX ### UserCredential (Default) ``` -Connect-MicrosoftTeams [-TenantId <String>] [-Credential <PSCredential>] [-AccountId <String>] - [-LogLevel <LogLevel>] [-LogFilePath <String>] [-TeamsEnvironmentName <String>] [-WhatIf] [-Confirm] - [<CommonParameters>] +Connect-MicrosoftTeams +[-TenantId <String>] +[-Credential <PSCredential>] +[-AccountId <String>] +[-LogLevel <LogLevel>] +[-LogFilePath <String>] +[-TeamsEnvironmentName <String>] +[-UseDeviceAuthentication] +[-WhatIf] +[-Confirm] +[<CommonParameters>] ``` ### ServicePrincipalCertificate ``` -Connect-MicrosoftTeams -TenantId <String> -CertificateThumbprint <String> -ApplicationId <String> - [-LogLevel <LogLevel>] [-LogFilePath <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +Connect-MicrosoftTeams +-TenantId <String> +-Certificate <X509Certificate2> +-ApplicationId <String> +[-LogLevel <LogLevel>] +[-LogFilePath <String>] +[-WhatIf] +[-Confirm] +[<CommonParameters>] ``` -### AccessToken +### ServicePrincipalCertificateThumbprint ``` -Connect-MicrosoftTeams [-TenantId <String>] -AadAccessToken <String> [-MsAccessToken <String>] - -AccountId <String> [-LogLevel <LogLevel>] [-LogFilePath <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +Connect-MicrosoftTeams +-TenantId <String> +-CertificateThumbprint <String> +-ApplicationId <String> +[-LogLevel <LogLevel>] +[-LogFilePath <String>] +[-WhatIf] +[-Confirm] +[<CommonParameters>] +``` + +### AccessTokens +``` +Connect-MicrosoftTeams +[-TenantId <String>] +-AccessTokens <String[]> +[-LogLevel <LogLevel>] +[-LogFilePath <String>] +[-WhatIf] +[-Confirm] +[<CommonParameters>] ``` ## DESCRIPTION +The Connect-MicrosoftTeams cmdlet connects to Microsoft Teams with an authenticated account for use with cmdlets from the MicrosoftTeams PowerShell module. After executing this cmdlet, you can disconnect from MicrosoftTeams account using Disconnect-MicrosoftTeams. + +**Note**: With versions 4.x.x or later, enablement of basic authentication is not needed anymore in commercial, GCC, GCC High, and DoD environments. ## EXAMPLES -### Example 1 +### Example 1: Connect to MicrosoftTeams +This example connects to an Azure account. You must provide a Microsoft account or organizational ID credentials. If multi-factor authentication is enabled for your credentials, you must log in using the interactive option. + +```powershell +Connect-MicrosoftTeams +Account Environment Tenant TenantId +------- ----------- ------------------------------------ ------------------------------------ +user@contoso.com AzureCloud xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx +``` + +### Example 2: Connect to MicrosoftTeams +The first command prompts for user credentials and stores them in the $Credential variable. The second command connects to an Azure account using the credentials stored in $credential. This account authenticates with Azure using organizational ID credentials. + +```powershell +$credential = Get-Credential +Connect-MicrosoftTeams -Credential $credential +Account Environment Tenant TenantId +------- ----------- ------------------------------------ ------------------------------------ +user@contoso.com AzureCloud xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx +``` + +### Example 3: Connect to MicrosoftTeams in a specific environment +This example connects to an Azure account in a specific environment. You must provide a Microsoft account or organizational ID credentials. If multi-factor authentication is enabled for your credentials, you must log in using the interactive option. + +```powershell +Connect-MicrosoftTeams -TeamsEnvironmentName TeamsGCCH +Account Environment Tenant TenantId +------- ----------- ------------------------------------ ------------------------------------ +user@contoso.com TeamsGCCH xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx +``` + +### Example 4: Connect to MicrosoftTeams using a certificate thumbprint +This example demonstrates how to authenticate using a certificate thumbprint. Application-based authentication has been reintroduced with version 4.7.1-preview. For details and supported cmdlets, please see [Application-based authentication in Teams PowerShell Module](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication). + +```powershell +Connect-MicrosoftTeams -CertificateThumbprint "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" -ApplicationId "00000000-0000-0000-0000-000000000000" -TenantId "YYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYY" +``` + +### Example 5: Connect to MicrosoftTeams using a certificate object +This example demonstrates how to authenticate using a certificate object. The Certificate parameter is available from Teams PowerShell Module version 4.9.2-preview or later. For details about application-based authentication and supported cmdlets, see [Application-based authentication in Teams PowerShell Module](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication). + +```powershell +$cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("C:\exampleCert.pfx",$password) +Connect-MicrosoftTeams -Certificate $cert -ApplicationId "00000000-0000-0000-0000-000000000000" -TenantId "YYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYY" +``` + +### Example 6: Connect to MicrosoftTeams using Application-based Access Tokens +This example demonstrates how to authenticate with an application using Access Tokens. Access Tokens can be retrieved via the login.microsoftonline.com endpoint. It requires two Access Tokens: "MS Graph" and "Skype and Teams Tenant Admin API" resources. + +Application-based authentication has been reintroduced with version 4.7.1-preview. For details and supported cmdlets, see [Application-based authentication in Teams PowerShell Module](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication). + ```powershell -PS C:\> Connect-MicrosoftTeams -TeamsEnvironmentName TeamsGCCH +$ClientSecret = "..." +$ApplicationID = "00000000-0000-0000-0000-000000000000" +$TenantID = "YYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYY" + +$graphtokenBody = @{ + Grant_Type = "client_credentials" + Scope = "https://graph.microsoft.com/.default" + Client_Id = $ApplicationID + Client_Secret = $ClientSecret +} + +$graphToken = Invoke-RestMethod -Uri "https://login.microsoftonline.com/$TenantID/oauth2/v2.0/token" -Method POST -Body $graphtokenBody | Select-Object -ExpandProperty Access_Token + +$teamstokenBody = @{ + Grant_Type = "client_credentials" + Scope = "48ac35b8-9aa8-4d74-927d-1f4a14a0b239/.default" + Client_Id = $ApplicationID + Client_Secret = $ClientSecret +} + +$teamsToken = Invoke-RestMethod -Uri "https://login.microsoftonline.com/$TenantID/oauth2/v2.0/token" -Method POST -Body $teamstokenBody | Select-Object -ExpandProperty Access_Token + +Connect-MicrosoftTeams -AccessTokens @("$graphToken", "$teamsToken") ``` -Specifies that the organization being managed is in the Teams GCC High environment, so connect to that environment. +### Example 7: Connect to MicrosoftTeams using Access Tokens in the delegated flow +This example demonstrates how to sign in using Access Tokens. Admin can retrieve Access Tokens via the login.microsoftonline.com endpoint. It requires two tokens, MS Graph Access Token and Teams Resource token. + +A delegated flow, such as Resource Owner Password Credentials (ROPC) or device code, must be used, with the following delegated app permissions required. + +| API | Grant type | Permission | +|-|-|-| +| Microsoft Graph | Delegated | User.Read.All | +| Microsoft Graph | Delegated | Group.ReadWrite.All | +| Microsoft Graph | Delegated | AppCatalog.ReadWrite.All | +| Microsoft Graph | Delegated | TeamSettings.ReadWrite.All | +| Microsoft Graph | Delegated | Channel.Delete.All | +| Microsoft Graph | Delegated | ChannelSettings.ReadWrite.All | +| Microsoft Graph | Delegated | ChannelMember.ReadWrite.All | +| Skype and Teams Tenant Admin API | Delegated | user_impersonation | + +```powershell +$ClientID = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" +$ClientSecret = "..." +$ClientSecret = [Net.WebUtility]::URLEncode($ClientSecret) +$TenantID = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" +$Username = "user@contoso.onmicrosoft.com" +$Password = "..." +$Password = [Net.WebUtility]::URLEncode($Password) + +$URI = "https://login.microsoftonline.com/$TenantID/oauth2/v2.0/token" +$Body = "client_id=$ClientID&client_secret=$ClientSecret&grant_type=password&username=$Username&password=$Password" +$RequestParameters = @{ + URI = $URI + Method = "POST" + ContentType = "application/x-www-form-urlencoded" +} +$GraphToken = (Invoke-RestMethod @RequestParameters -Body "$Body&scope=https://graph.microsoft.com/.default").access_token +$TeamsToken = (Invoke-RestMethod @RequestParameters -Body "$Body&scope=48ac35b8-9aa8-4d74-927d-1f4a14a0b239/.default").access_token +Connect-MicrosoftTeams -AccessTokens @($GraphToken, $TeamsToken) + +Account Environment Tenant TenantId +------- ----------- ------------------------------------ ------------------------------------ +user@contoso.com AzureCloud xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx +``` ## PARAMETERS -### -AadAccessToken -Specifies a Azure Active Directory Graph access token. +### AccessTokens +Specifies access tokens for "MS Graph" and "Skype and Teams Tenant Admin API" resources. Both the tokens used should be of the same type. + +- Application-based authentication has been reintroduced with version 4.7.1-preview. For details and supported cmdlets, see [Application-based authentication in Teams PowerShell Module](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication). + +- Delegated flow - The following steps must be performed by Tenant Admin in the Azure portal when using your own application. + + Steps to configure the Microsoft Entra application. + 1. Go to Azure portal and go to App Registrations. + 2. Create or select the existing application. + 3. Add the following permission to this Application. + 4. Click API permissions. + 5. Click Add a permission. + 6. Click on the Microsoft Graph, and then select Delegated permissions. + 7. Add the following permissions: "AppCatalog.ReadWrite.All", "Group.ReadWrite.All", "User.Read.All", "TeamSettings.ReadWrite.All", "Channel.Delete.All", "ChannelSettings.ReadWrite.All", "ChannelMember.ReadWrite.All". + 8. Next, we need to add "Skype and Teams Tenant Admin API" resource permission. Click Add a permission. + 9. Navigate to "APIs my organization uses" + 10. Search for "Skype and Teams Tenant Admin API", and then select Delegated permissions. + 11. Add all the listed permissions. + 12. Grant admin consent to both Microsoft Graph and "Skype and Teams Tenant Admin API" name. + +```yaml +Type: String[] +Parameter Sets: AccessTokens +Aliases: +Required: True +Position: Named +Default value: None +Accept wildcard characters: False +``` + +### -AadAccessToken (Removed from version 2.3.2-preview) +Specifies an Azure Active Directory Graph access token. +> [!WARNING] +>This parameter has been removed from version 2.3.2-preview. ```yaml Type: String @@ -65,13 +246,11 @@ Accept wildcard characters: False ### -AccountId Specifies the ID of an account. -You must specify the UPN of the user when authenticating with a user access token. ```yaml Type: String Parameter Sets: UserCredential Aliases: - Required: False Position: Named Default value: None @@ -79,11 +258,15 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ApplicationId +Specifies the application ID of the service principal that is used in application-based authentication. + +This parameter has been reintroduced with version 4.7.1-preview. For more information about Application-based authentication and supported cmdlets, see [Application-based authentication in Teams PowerShell Module](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication). + ```yaml Type: String -Parameter Sets: AccessToken +Parameter Sets: ServicePrincipalCertificate Aliases: - Required: True Position: Named Default value: None @@ -91,13 +274,15 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ApplicationId -Specifies the application ID of the service principal. +### -Certificate +Specifies the certificate that is used for application-based authentication. A valid value is the X509Certificate2 object value of the certificate. + +This parameter has been introduced with version 4.9.2-preview. For more information about application-based authentication and supported cmdlets, see [Application-based authentication in Teams PowerShell Module](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication). ```yaml -Type: String +Type: X509Certificate2 Parameter Sets: ServicePrincipalCertificate -Aliases: +Aliases: CertificateThumbprint Required: True Position: Named @@ -107,13 +292,14 @@ Accept wildcard characters: False ``` ### -CertificateThumbprint -Specifies the certificate thumbprint of a digital public key X.509 certificate of a user account that has permission to perform this action. +Specifies the certificate thumbprint of a digital public key X.509 certificate of an application that has permission to perform this action. + +This parameter has been reintroduced with version 4.7.1-preview. For more information about Application-based authentication and supported cmdlets, see [Application-based authentication in Teams PowerShell Module](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication). ```yaml Type: String Parameter Sets: ServicePrincipalCertificate Aliases: - Required: True Position: Named Default value: None @@ -128,7 +314,6 @@ Prompts you for confirmation before running the cmdlet. Type: SwitchParameter Parameter Sets: (All) Aliases: cf - Required: False Position: Named Default value: False @@ -146,7 +331,6 @@ The PSCredential object provides the user ID and password for organizational ID Type: PSCredential Parameter Sets: UserCredential Aliases: - Required: False Position: Named Default value: None @@ -162,7 +346,6 @@ Provide a value here if you need to deviate from the default PowerShell log file Type: String Parameter Sets: (All) Aliases: - Required: False Position: Named Default value: None @@ -171,7 +354,7 @@ Accept wildcard characters: False ``` ### -LogLevel -Specifies the log level. +Specifies the log level. The acceptable values for this parameter are: - Info @@ -185,7 +368,6 @@ The default value is Info. Type: LogLevel Parameter Sets: (All) Aliases: - Required: False Position: Named Default value: None @@ -193,14 +375,15 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -MsAccessToken +### -MsAccessToken (Removed from version 2.3.2-preview) Specifies a Microsoft Graph access token. +> [!WARNING] +>This parameter has been removed from version 2.3.2-preview. ```yaml Type: String Parameter Sets: AccessToken Aliases: - Required: False Position: Named Default value: None @@ -219,7 +402,6 @@ You must specify the TenantId parameter to authenticate as a service principal o Type: String Parameter Sets: UserCredential, AccessToken Aliases: Domain, TenantDomain - Required: False Position: Named Default value: None @@ -231,7 +413,6 @@ Accept wildcard characters: False Type: String Parameter Sets: ServicePrincipalCertificate Aliases: Domain, TenantDomain - Required: True Position: Named Default value: None @@ -247,7 +428,6 @@ The cmdlet is not run. Type: SwitchParameter Parameter Sets: (All) Aliases: wi - Required: False Position: Named Default value: False @@ -256,14 +436,90 @@ Accept wildcard characters: False ``` ### -TeamsEnvironmentName -Use this setting if your organization is in one of the Teams Government Cloud environments. +Specifies the Teams environment. The following environments are supported: -Specify "TeamsGCCH" if your organization is in the GCC High Environment. Specify "TeamsDOD" if your organization is in the DoD Environment. + - Commercial or GCC environments: Don't use this parameter, this is the default. + - GCC High environment: TeamsGCCH + - DoD environment: TeamsDOD + - Microsoft Teams operated by 21Vianet: TeamsChina ```yaml Type: String Parameter Sets: UserCredential Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Login using managed service identity in the current environment. For *-Cs cmdlets, this is supported from version 5.8.1-preview onwards. + +> [!Note] +> This is currently only supported in commercial environments. A few [cmdlets](https://learn.microsoft.com/microsoftteams/teams-powershell-application-authentication#cmdlets-supported) that don't support application-based authentication are not supported either. + +```yaml +Type: SwitchParameter +Parameter Sets: ManagedServiceLogin +Aliases: MSI, ManagedService +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedServiceHostName +Host name for managed service login. + +```yaml +Type: String +Parameter Sets: ManagedServiceLogin +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedServicePort +Port number for managed service login. + +```yaml +Type: Int32 +Parameter Sets: ManagedServiceLogin +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManagedServiceSecret +Secret, used for some kinds of managed service login. + +```yaml +Type: SecureString +Parameter Sets: ManagedServiceLogin +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseDeviceAuthentication +Use device code authentication instead of a browser control. + +```yaml +Type: SwitchParameter +Parameter Sets: UserCredential +Aliases: Required: False Position: Named @@ -273,24 +529,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ## OUTPUTS ## NOTES -Tips for troubleshooting: - -**1. Confirm SAML 2.0 is being used.**\ -IDP is outputting invalid SAML information. -Needs to have SAML 2.0 vs. -SAML 1.0 for the module to connect. -You might experience an error if the Identity Provider (IDP) only allows the use of SAML 1.0 when trying to auth via basic authentication. -Which in turn, isn't expected to work because the cmdlet expects either OAUTH2 (which is used when doing just connect-microsofteams), or SAML 2.0. - -**2. Confirm you have the latest version of the cmdlet.**\ -You can find the version by running: \`get-module -listavailable\` and then looking for the MicrosoftTeams name and the version to the left of it. For more information and how to download the module, see [Teams PowerShell Overview](https://docs.microsoft.com/microsoftteams/teams-powershell-overview) ## RELATED LINKS diff --git a/teams/teams-ps/teams/Disable-CsOnlineSipDomain.md b/teams/teams-ps/teams/Disable-CsOnlineSipDomain.md new file mode 100644 index 0000000000..932a55f2fe --- /dev/null +++ b/teams/teams-ps/teams/Disable-CsOnlineSipDomain.md @@ -0,0 +1,132 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/disable-csonlinesipdomain +applicable: Microsoft Teams +title: Disable-CsOnlineSipDomain +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Disable-CsOnlineSipDomain + +## SYNOPSIS + +This cmdlet prevents provisioning of users in Skype for Business Online for the specified domain. This cmdlet allows organizations with multiple on-premises deployments of Skype For Business Server or Lync Server to safely synchronize users from multiple forests into a single Office 365 tenant. + +## SYNTAX + +```powershell +Disable-CsOnlineSipDomain -Domain <String> [-Force] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Note: Only one Skype for Business forest can be in hybrid mode at a given time. For full details on this scenario, including step-by-step instructions, see [Cloud consolidation for Teams and Skype for Business](https://learn.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation). + +This cmdlet enables organizations with *multiple on-premises deployments of Skype for Business Server (or Lync Server)* to safely synchronize users from multiple forests into a single Office 365 tenant. When an online SIP domain is disabled in Skype for Business Online, provisioning is blocked for users in this SIP domain. This ensures routing for any on-premises users in this SIP domain continues to function properly. + +This cmdlet facilitates consolidation of multiple Skype for Business Server deployments into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, **provided the following key requirements are met**: + +- There must be at most 1 O365 tenant involved. Consolidation in scenarios with >1 O365 tenant is not supported. + +- At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.) + +- If 1 deployment is in hybrid mode, all sip domains from any other SfB forests must be disabled using this cmdlet before they can be synchronized into the tenant with Microsoft Entra Connect. Users in all SfB forests other than the hybrid forest must remain on-premises. + +- Organizations must fully migrate each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment. + +This cmdlet may also be useful for organizations with on-premises deployments of Skype for Business Server that have not properly configured Microsoft Entra Connect. If the organization does not sync msRTCSIP-DeploymentLocator for its users, then Skype for Business Online will attempt to provision online any users with an assigned Skype for Business license, despite there being users on-premises. While the correct fix is to update the configuration for Microsoft Entra Connect to sync those attributes, using Disable-CsOnlineSipDomain can also mitigate the problem until that configuration change can be made. If this cmdlet is run, any users that were previously provisioned online in that domain will be de-provisioned in Skype for Business Online. + +Important: This cmdlet should not be run for domains that contain users hosted in Skype for Business Online. Any users in a sip domain that are already provisioned *online* will cease to function if you disable the online sip domain: +- Their SIP addresses will be removed. +- All contacts and meetings for these users hosted in Skype for Business Online will be deleted. +- These users will no longer be able to login to the Skype for Business Online environment. +- If these users use Teams, they will no longer be able to inter-operate with Skype for Business users, nor will they be able to federate with any users in other organizations. + +Note: If the Tenant is enabled for Regionally Hosted Meetings in Skype for Business Online, Online SIP Domains must be disabled in all regions. You must execute this cmdlet in each region that is added in Allowed Data Location. + +## EXAMPLES + +### Example 1 + +```powershell +Disable-CsOnlineSipDomain -Domain Fabrikam.com +``` + +The cmdlet above disables the online sip domain Fabrikam.com. This would be useful in the case where a company, Contoso.com, that has Skype for Business acquires Fabrikam, which also has an on-premises deployment of Skype for Business Server. If Contoso is in hybrid mode with Skype for Business Online or if the intent is to configure it for hybrid, then if the organization wants to synchronize identities from Fabrikam.com into the same O365 tenant, the organization must first run this cmdlet. + +## PARAMETERS + +### -Domain + +The SIP domain to be disabled for online provisioning in Skype for Business Online. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +Suppresses all confirmation prompts that might occur when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES + +This cmdlet is for advanced scenarios only. Organizations that are pure online or have only 1 on-premises deployment need not run this cmdlet. + +## RELATED LINKS + +[Enable-CsOnlineSipDomain](https://learn.microsoft.com/powershell/module/teams/enable-csonlinesipdomain) + +[Get-CsOnlineSipDomain](https://learn.microsoft.com/powershell/module/teams/get-csonlinesipdomain) + +[Cloud consolidation for Teams and Skype for Business](https://learn.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation) diff --git a/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md b/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md new file mode 100644 index 0000000000..84d184eb9d --- /dev/null +++ b/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md @@ -0,0 +1,68 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Disable-CsTeamsShiftsConnectionErrorReport +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/disable-csteamsshiftsconnectionerrorreport +schema: 2.0.0 +--- + +# Disable-CsTeamsShiftsConnectionErrorReport + +## SYNOPSIS + +**Note:** This cmdlet is currently in public preview. + +This cmdlet disables an error report. + +## SYNTAX + +``` +Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId <String> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet disables an error report. All available instances can be found by running [Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId 18b3e490-e6ed-4c2e-9925-47e36609dff3 +``` + +Disables the error report with ID `18b3e490-e6ed-4c2e-9925-47e36609dff3`. + +## PARAMETERS + +### -ErrorReportId + +The ID of the error report that you want to disable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport) diff --git a/teams/teams-ps/teams/Disconnect-MicrosoftTeams.md b/teams/teams-ps/teams/Disconnect-MicrosoftTeams.md index e6b5c155ca..b840da266f 100644 --- a/teams/teams-ps/teams/Disconnect-MicrosoftTeams.md +++ b/teams/teams-ps/teams/Disconnect-MicrosoftTeams.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/disconnect-microsoftteams +online version: https://learn.microsoft.com/powershell/module/teams/disconnect-microsoftteams +title: Disconnect-MicrosoftTeams schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -62,8 +63,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Enable-CsOnlineSipDomain.md b/teams/teams-ps/teams/Enable-CsOnlineSipDomain.md new file mode 100644 index 0000000000..7356c8e473 --- /dev/null +++ b/teams/teams-ps/teams/Enable-CsOnlineSipDomain.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/enable-csonlinesipdomain +applicable: Microsoft Teams +title: Enable-CsOnlineSipDomain +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Enable-CsOnlineSipDomain + +## SYNOPSIS + +This cmdlet enables provisioning of users in Skype for Business Online for the specified domain. This cmdlet is only necessary to run if you previously disabled a domain using Disable-CsOnlineSipDomain. Enable-CsOnlineSipDomain is used to facilitate consolidation of separate Skype for Business deployments into a single Office 365 tenant. + +## SYNTAX + +```powershell +Enable-CsOnlineSipDomain -Domain <String> [-Force] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet enables online provisioning of users in the specified SIP domain. In conjunction with Disable-CsOnlineSipDomain, this cmdlet allows organizations to consolidate *multiple on-premises deployments of Skype for Business Server (or Lync Server)* into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, provided the following key requirements are met: + +- There must be at most 1 O365 tenant involved. Consolidation for scenarios with > 1 O365 tenant is not supported. + +- At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.) + +- If 1 deployment is in hybrid mode, all online SIP domains from any other SfB forests must be disabled before they can be synchronized into the tenant with Microsoft Entra Connect. Users in all SfB forests other than the hybrid forest must remain on-premises. + +- Organizations must fully migrate (e.g move all users to the cloud) each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment. + +Before running this cmdlet for any SIP domain in a Skype for Business Server deployment, you must complete migration of any other existing hybrid SfB deployment that is in progress. All users in an existing hybrid deployment must be moved to the cloud, and that existing hybrid deployment must be detached from Office 365, as described in this article: [Disable hybrid to complete migration to the cloud](https://learn.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid). + +Important: If you have more than one on-premises deployment of Skype for Business Server, you *must* ensure SharedSipAddressSpace is disabled in all other Skype for Business Server deployments except the deployment containing the SIP domain that is being enabled. + +Note: If the Tenant is enabled for Regionally Hosted Meetings in Skype for Business Online, Online SIP Domains must be Enabled in all regions. You must execute this cmdlet in each region that is added in Allowed Data Location for Skype for Business. + +## EXAMPLES + +### Example 1 + +```powershell +Enable-CsOnlineSipDomain -Domain contoso.com +``` + +Enables the domain contoso.com for online provisioning in Skype for Business Online. + +## PARAMETERS + +### -Domain + +The SIP domain to be enabled for online provisioning in Skype for Business Online. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +Suppresses all confirmation prompts that might occur when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES + +## RELATED LINKS + +[Disable-CsOnlineSipDomain](https://learn.microsoft.com/powershell/module/teams/disable-csonlinesipdomain) + +[Get-CsOnlineSipDomain](https://learn.microsoft.com/powershell/module/teams/get-csonlinesipdomain) diff --git a/teams/teams-ps/teams/Export-CsAcquiredPhoneNumber.md b/teams/teams-ps/teams/Export-CsAcquiredPhoneNumber.md new file mode 100644 index 0000000000..2af9e62f5d --- /dev/null +++ b/teams/teams-ps/teams/Export-CsAcquiredPhoneNumber.md @@ -0,0 +1,127 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/export-csacquiredphonenumber +applicable: Microsoft Teams +title: Export-CsAcquiredPhoneNumber +author: pavellatif +ms.author: pavellatif +ms.reviewer: +manager: roykuntz +schema: 2.0.0 +--- + +# Export-CsAcquiredPhoneNumber + +## SYNOPSIS +This cmdlet exports the list of phone numbers acquired by Teams Phone tenant. + +## SYNTAX + +``` +Export-CsAcquiredPhoneNumber [-Property <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet exports all the acquired phone numbers by the tenant to a file. The cmdlet is an asynchronus operation and will return an OrderId. [Get-CsExportAcquiredPhoneNumberStatus](https://learn.microsoft.com/powershell/module/teams/get-csexportacquiredphonenumberstatus) cmdlet can be used to check the status of the OrderId including the download link to exported file. + +By default, this cmdlet returns all the phone numbers acquired by the tenant with all corresponding properties in the results. The tenant admin may indicate specific properties as an input to get a list with only selected properties in the file. + +**Available properties to use are**: + +- TelephoneNumber +- OperatorId +- NumberType +- LocationId +- CivicAddressId +- NetworkSiteId +- AvailableCapabilities +- AcquiredCapabilities +- AssignmentStatus +- PlaceName +- ActivationState +- PartnerName +- IsoCountryCode +- PortInOrderStatus +- CapabilityUpdateSupported +- AcquisitionDate +- TargetId +- TargetType +- AssignmentCategory +- CallingProfileId +- IsoSubdivisionCode +- NumberSource +- SupportedCustomerActions +- ReverseNumberLookup +- RoutingOptions + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Export-CsAcquiredPhoneNumber +``` +```output +0e923e2c-ab0e-4b7a-be5a-906be8c +``` +This example displays the output of the export acquired phone numbers operation. The OrderId shown as the output string and can be used to get the download link for the file. + +### Example 2 +```powershell +PS C:\> Export-CsAcquiredPhoneNumber -Property "TelephoneNumber, NumberType, AssignmentStatus" +``` +```output +0e923e2c-ab0e-6h8c-be5a-906be8c +``` +This example displays the output of the export acquired phone numbers operation with filtered properties. This file will only contain the properties indicated. + +### Example 3 +```powershell +PS C:\> $orderId = Export-CsAcquiredPhoneNumber +``` +This example displays the use of variable "orderId" for the export acquired phone numbers operation. The OrderId string will be stored in the variable named "orderId" and no output will be shown for the cmdlet. + +### Example 4 +```powershell +PS C:\> Export-CsAcquiredPhoneNumber -Property "TelephoneNumber, NumberType, AssignmentStatus" +``` +```output +OrderId : 0e923e2c-ab0e-6h8c-be5a-906be8c +``` +This example displays the use of variable "orderId" for the export acquired phone numbers operation with filtered properties. The OrderId string will be stored in the variable named "orderId" and no output will be shown for the cmdlet. + +## PARAMETERS + +### -Property +{{ Fill Property Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.String + +## NOTES +The cmdlet is available in Teams PowerShell module 6.1.0 or later. + +The cmdlet is only available in commercial and GCC cloud instances. + +## RELATED LINKS +[Get-CsExportAcquiredPhoneNumberStatus](https://learn.microsoft.com/powershell/module/teams/get-csexportacquiredphonenumberstatus) diff --git a/teams/teams-ps/teams/Export-CsAutoAttendantHolidays.md b/teams/teams-ps/teams/Export-CsAutoAttendantHolidays.md new file mode 100644 index 0000000000..610335e471 --- /dev/null +++ b/teams/teams-ps/teams/Export-CsAutoAttendantHolidays.md @@ -0,0 +1,104 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/export-csautoattendantholidays +applicable: Microsoft Teams +title: Export-CsAutoAttendantHolidays +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Export-CsAutoAttendantHolidays + +## SYNOPSIS +Use Export-CsAutoAttendantHolidays cmdlet to export holiday schedules of an existing Auto Attendant (AA). The data is exported as a byte array from the cmdlet, which can be dumped to disk as a CSV file and can later be imported using the Import-CsAutoAttendantHolidays cmdlet. + +## SYNTAX + +``` +Export-CsAutoAttendantHolidays -Identity <String> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The Export-CsAutoAttendantHolidays cmdlet and the Import-CsAutoAttendantHolidays cmdlet enable you to export holiday schedules in your auto attendant and then later import that information. This can be extremely useful in a situation where you need to configure same holiday sets in multiple tenants. + +The Export-CsAutoAttendantHolidays cmdlet returns the holiday schedule information in serialized form (as a byte array). The caller can then write the bytes to the disk to obtain a CSV file. Similarly, the Import-CsAutoAttendantHolidays cmdlet accepts the holiday schedule information as a byte array, which can be read from the aforementioned CSV file. The first line of the CSV file is considered a header record and is always ignored. + +**NOTE**: Each line in the CSV file used by Export-CsAutoAttendantHolidays and Import-CsAutoAttendantHolidays cmdlet should be of the following format: + +`HolidayName,StartDateTime1,EndDateTime1,StartDateTime2,EndDateTime2,...,StartDateTime10,EndDateTime10` + +where + +- HolidayName is the name of the holiday to be imported. +- StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet. +- EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date. + +- The first line of the CSV file is considered a header record and is always ignored by Import-CsAutoAttendantHolidays cmdlet. +- If the destination auto attendant for the import already contains a call flow or schedule by the same name as one of the holidays being imported, the corresponding CSV record is skipped. +- For holidays that are successfully imported, a default call flow is created which is configured without any greeting and simply disconnects the call on being executed. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$bytes = Export-CsAutoAttendantHolidays -Identity 6abea1cd-904b-520b-be96-1092cc096432 +[System.IO.File]::WriteAllBytes("C:\Exports\Holidays.csv", $bytes) +``` + +In this example, the Export-CsAutoAttendantHolidays cmdlet is used to export holiday schedules of an auto attendant with Identity of 6abea1cd-904b-520b-be96-1092cc096432. The exported bytes are then written to a file with the path "C:\Exports\Holidays.csv". + +## PARAMETERS + +### -Identity +The identity for the AA whose holiday schedules are to be exported. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Export-CsAutoAttendantHolidays cmdlet accepts a string as the Identity parameter. + +## OUTPUTS + +### System.Byte[] + +## NOTES + +## RELATED LINKS + +[Import-CsAutoAttendantHolidays](https://learn.microsoft.com/powershell/module/teams/import-csautoattendantholidays) + +[Get-CsAutoAttendantHolidays](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantholidays) diff --git a/teams/teams-ps/teams/Find-CsGroup.md b/teams/teams-ps/teams/Find-CsGroup.md new file mode 100644 index 0000000000..18c265455b --- /dev/null +++ b/teams/teams-ps/teams/Find-CsGroup.md @@ -0,0 +1,151 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/find-csgroup +applicable: Microsoft Teams +title: Find-CsGroup +schema: 2.0.0 +--- + +# Find-CsGroup + +## SYNOPSIS +Use the Find-CsGroup cmdlet to search groups. + +## SYNTAX + +``` +Find-CsGroup [-Tenant <Guid>] -SearchQuery <String> [-MaxResults <UInt32>] [-ExactMatchOnly <Boolean>] [-MailEnabledOnly <Boolean>] +[-Force] [<CommonParameters>] +``` + +## DESCRIPTION +The Find-CsGroup cmdlet lets you search groups in the Azure Address Book Service (AABS). + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Find-CsGroup -SearchQuery "Contoso Group" -MaxResults 5 +``` + +This example finds and displays up to five groups that match the "Contoso Group" search query. + +### -------------------------- Example 2 -------------------------- +``` +Find-CsGroup -SearchQuery "ed0d1180-169e-47c7-b718-bf9e60543914" -ExactMatchOnly $true +``` + +This example finds and displays only those groups that are an exact match to the search query. + +## PARAMETERS + +### -SearchQuery +The SearchQuery parameter defines a search query to search the display name or the sip address or the GUID of groups. This parameter accepts partial search query. The search is not case sensitive. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExactMatchOnly +The ExactMatchOnly parameter instructs the cmdlet to return exact matches only. The default value is false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxResults +The MaxResults parameter identifies the maximum number of results to return. If this parameter is not provided, the default is value is 10. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MailEnabledOnly +Instructs the cmdlet to return mail enabled only groups. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Group.Models.GroupModel +The Find-CsGroup cmdlet returns a list of Microsoft.Rtc.Management.Hosted.Group.Models.GroupModel. Microsoft.Rtc.Management.Hosted.Group.Models.GroupModel contains Id and DisplayName. + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Find-CsOnlineApplicationInstance.md b/teams/teams-ps/teams/Find-CsOnlineApplicationInstance.md new file mode 100644 index 0000000000..2744bd46e0 --- /dev/null +++ b/teams/teams-ps/teams/Find-CsOnlineApplicationInstance.md @@ -0,0 +1,178 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/find-csonlineapplicationinstance +applicable: Microsoft Teams +title: Find-CsOnlineApplicationInstance +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Find-CsOnlineApplicationInstance + +## SYNOPSIS +Use the Find-CsOnlineApplicationInstance cmdlet to find application instances that match your search criteria. + +## SYNTAX + +``` +Find-CsOnlineApplicationInstance [-SearchQuery] <string> [[-MaxResults] <uint>] [-ExactMatchOnly] [-AssociatedOnly] [-UnAssociatedOnly] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +Use the Find-CsOnlineApplicationInstance cmdlet to find application instances that match your search criteria. + +If MaxResults is not specified, the number of returned applications instances is limited to 10 application instances. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Find-CsOnlineApplicationInstance -SearchQuery "Test" +``` + +This example returns up to 10 application instances whose name starts with "Test". + +### -------------------------- Example 2 -------------------------- +```powershell +Find-CsOnlineApplicationInstance -SearchQuery "Test" -MaxResults 5 +``` + +This example returns up to 5 application instances whose name starts with "Test". + +### -------------------------- Example 3 -------------------------- +```powershell +Find-CsOnlineApplicationInstance -SearchQuery "Test Auto Attendant" -ExactMatchOnly +``` + +This example returns up to 10 application instances whose name is "Test Auto Attendant". + +### -------------------------- Example 4 -------------------------- +```powershell +Find-CsOnlineApplicationInstance -SearchQuery "Test Auto Attendant" -AssociatedOnly +``` + +This example returns up to 10 application instances whose name is "Test Auto Attendant", and who are associated with an application configuration, like auto attendant or call queue. + +## PARAMETERS + +### -SearchQuery +The SearchQuery parameter defines a query for application instances by display name, telephone number, or GUID of the application instance. This parameter accepts partial queries for display names and telephone numbers. The search is not case sensitive. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExactMatchOnly +The ExactMatchOnly parameter instructs the cmdlet to return exact matches only. The default value is false. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssociatedOnly +The AssociatedOnly parameter instructs the cmdlet to return only application instances that are associated to a configuration. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnAssociatedOnly +The UnAssociatedOnly parameter instructs the cmdlet to return only application instances that are not associated to any configuration. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxResults +The MaxResults parameter identifies the maximum number of results to return. If this parameter is not provided, the default is value is 10. Max allowed value is 20. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +This switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If it isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.FindApplicationInstanceResult + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstance) + +[New-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstance) + +[Find-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/find-csonlineapplicationinstance) + +[Set-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/set-csonlineapplicationinstance) diff --git a/teams/teams-ps/teams/Get-ALLM365TeamsApps.md b/teams/teams-ps/teams/Get-ALLM365TeamsApps.md new file mode 100644 index 0000000000..b3dd4967bb --- /dev/null +++ b/teams/teams-ps/teams/Get-ALLM365TeamsApps.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.Teams.PowerShell.TeamsCmdlets.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://docs.microsoft.com/powershell/module/teams/Get-ALLM365TeamsApps +applicable: Microsoft Teams +title: Get-ALLM365TeamsApps +author: lkueter +ms.author: sribagchi +manager: rahulrgupta +ms.date: 04/24/2024 +schema: 2.0.0 +--- + +# Get-AllM365TeamsApps + +## SYNOPSIS + +This cmdlet returns all Microsoft Teams apps in the app catalog, including Microsoft, custom, and non-Microsoft apps. + +## SYNTAX + +```powershell +Get-AllM365TeamsApps [<CommonParameters>] +``` + +## DESCRIPTION + +Get-AllM365TeamsApps retrieves a complete list of all Teams apps in an organization, their statuses, and their availability information. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-AllM365TeamsApps +``` + +Returns a complete list of all Teams apps in an organization, their statuses, and their availability information. + +### Example 2 + +```powershell +PS C:\> Get-AllM365TeamsApps | Select-Object -Property Id, IsBlocked, AvailableTo -ExpandProperty AvailableTo +``` + +Returns a complete list of all Teams apps in an organization, their statuses, and their availability information in expanded format. + +### Example 3 + +```powershell +PS C:\> Get-AllM365TeamsApps | Select-Object -Property Id, IsBlocked, AvailableTo, InstalledFor -ExpandProperty InstalledFor +``` + +Returns a complete list of all Teams apps in an organization, their statuses, their availability and their installation information in expanded format. + +## 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +**Id** +Application ID of the Teams app. + +**IsBlocked** +The state of the app in the tenant. +Values: + +- Blocked +- Unblocked + +**AvailableTo** +Provides available to properties for the app. +Properties: + +- AssignmentType: App availability type. + Values: + - Everyone + - UsersandGroups + - Noone +- LastUpdatedTimestamp: Time and date when the app AvailableTo value was last updated. +- AssignedBy: UserID of the last user who updated the app available to value. + +**InstalledFor** +Provides installation status for the app. +Properties: + +- AppInstallType: App availability type. + Values: + - Everyone + - UsersandGroups + - Noone +- LastUpdatedTimestamp: Time and date when the app AvailableTo value was last updated. +- InstalledBy: UserID of the last user who installed the app available to value. +- InstalledSource: Source of Installation +- Version: Version of the app installed + +## NOTES + +## RELATED LINKS + +[Get-M365TeamsApp](https://learn.microsoft.com/powershell/module/teams/get-m365teamsapp) +[Update-M365TeamsApp](https://learn.microsoft.com/powershell/module/teams/get-m365teamsapp) diff --git a/teams/teams-ps/teams/Get-AssociatedTeam.md b/teams/teams-ps/teams/Get-AssociatedTeam.md new file mode 100644 index 0000000000..2bc7566964 --- /dev/null +++ b/teams/teams-ps/teams/Get-AssociatedTeam.md @@ -0,0 +1,81 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-associatedteam +title: Get-AssociatedTeam +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: dedaniel, robharad +--- + +# Get-AssociatedTeam + +## SYNOPSIS +This cmdlet supports retrieving all teams associated with a user, including teams which host shared channels. + +## SYNTAX +```PowerShell +Get-AssociatedTeam [-User <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet supports retrieving all associated teams of a user, including teams which host shared channels. + +## EXAMPLES + +### Example 1 +```PowerShell +Get-AssociatedTeam +``` + +Returns associated teams of the current user. + +### Example 2 +```PowerShell +Get-AssociatedTeam -user example@example.com +``` + +Returns associated teams of a given user email. + +### Example 3 +```PowerShell +Get-AssociatedTeam -user 0e4249a7-6cfd-8c93-a510-91cda44c8c73 +``` + +Returns associated teams of a given user ID. + +## PARAMETERS + +### -User +User's UPN (user principal name, for example +johndoe@example.com) or user ID (for example 0e4249a7-6cfd-8c93-a510-91cda44c8c73). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### User + +## OUTPUTS + +### Team + +## NOTES + +## RELATED LINKS +[Get-Team](https://learn.microsoft.com/powershell/module/teams/get-team) +[Get-SharedWithTeam](https://learn.microsoft.com/powershell/module/teams/get-team) diff --git a/teams/teams-ps/teams/Get-CsApplicationAccessPolicy.md b/teams/teams-ps/teams/Get-CsApplicationAccessPolicy.md new file mode 100644 index 0000000000..a3cd76b4a4 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsApplicationAccessPolicy.md @@ -0,0 +1,124 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csapplicationaccesspolicy +applicable: Microsoft Teams +title: Get-CsApplicationAccessPolicy +schema: 2.0.0 +manager: zhengni +author: frankpeng7 +ms.author: frpeng +ms.reviewer: +--- + +# Get-CsApplicationAccessPolicy + +## SYNOPSIS + +Retrieves information about the application access policy configured for use in the tenant. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsApplicationAccessPolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsApplicationAccessPolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet retrieves information about the application access policy configured for use in the tenant. + +## EXAMPLES + +### Retrieve all application access policies + +```powershell +PS C:\> Get-CsApplicationAccessPolicy +``` + +The command shown above returns information of all application access policies that have been configured for use in the tenant. + +### Retrieve specific application access policy + +```powershell +PS C:\> Get-CsApplicationAccessPolicy -Identity "ASimplePolicy" +``` + +In the command shown above, information is returned for a single application access policy: the policy with the Identity ASimplePolicy. + +## PARAMETERS + +### -Identity + +Unique identifier assigned to the policy when it was created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter + +A filter that is not expressed in the standard wildcard language. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) + +[Grant-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csapplicationaccesspolicy) + +[Set-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/set-csapplicationaccesspolicy) + +[Remove-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csapplicationaccesspolicy) diff --git a/teams/teams-ps/teams/Get-CsApplicationMeetingConfiguration.md b/teams/teams-ps/teams/Get-CsApplicationMeetingConfiguration.md new file mode 100644 index 0000000000..0980ee7a04 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsApplicationMeetingConfiguration.md @@ -0,0 +1,110 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-CsApplicationMeetingConfiguration +applicable: Teams +title: Get-CsApplicationMeetingConfiguration +schema: 2.0.0 +manager: zhengni +author: jackry6350 +ms.author: yoren +ms.reviewer: +--- + +# Get-CsApplicationMeetingConfiguration + +## SYNOPSIS + +Retrieves information about the application meeting configuration settings configured for the tenant. + +## SYNTAX + +### Identity + +``` +Get-CsApplicationMeetingConfiguration [-Identity <XdsIdentity>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet retrieves information about the application meeting configuration settings configured for the tenant. + +## EXAMPLES + +### Retrieve application meeting configuration settings for the tenant. + +``` +PS C:\> Get-CsApplicationMeetingConfiguration +``` + +The command shown above returns application meeting configuration settings that have been configured for the tenant. + +## PARAMETERS + +### -Identity + +Unique identifier of the application meeting configuration settings to be returned. +Because you can only have a single, global instance of these settings, you do not have to include the Identity when calling the Get-CsApplicationMeetingConfiguration cmdlet. +However, you can use the following syntax to retrieve the global settings: -Identity global. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcards when specifying the application meeting configuration settings to be returned. +Because you can only have a single, global instance of these settings there is little reason to use the Filter parameter. +However, if you prefer, you can use syntax similar to this to retrieve the global settings: -Identity "g*". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: +Applicable: Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Retrieves the application meeting configuration data from the local replica of the Central Management store rather than from the Central Management store itself. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.WritableConfig.Settings.PlatformApplications.ApplicationMeetingConfiguration + +## NOTES + +## RELATED LINKS + +[Set-CsApplicationMeetingConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csapplicationmeetingconfiguration) diff --git a/teams/teams-ps/teams/Get-CsAutoAttendant.md b/teams/teams-ps/teams/Get-CsAutoAttendant.md new file mode 100644 index 0000000000..7fc22623fe --- /dev/null +++ b/teams/teams-ps/teams/Get-CsAutoAttendant.md @@ -0,0 +1,246 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csautoattendant +applicable: Microsoft Teams +title: Get-CsAutoAttendant +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsAutoAttendant + +## SYNOPSIS +Use the Get-CsAutoAttendant cmdlet to get information about your Auto Attendants (AA). + +## SYNTAX + +``` +Get-CsAutoAttendant [-Identity <String>] [-First <UInt32>] [-Skip <UInt32>] [-NameFilter <String>] [-SortBy <String>] [-Descending] [-IncludeStatus] [-ExcludeContent] [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsAutoAttendant cmdlet returns information about the AAs in your organization. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsAutoAttendant +``` + +This example gets the first 100 auto attendants in the organization. + +### Example 2 +```powershell +Get-CsAutoAttendant -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" + +# Id : f7a821dc-2d69-5ae8-8525-bcb4a4556093 +# TenantId : 977c9d5b-2dae-5d82-aada-628bc1c14213 +# Name : Main Auto Attendant +# LanguageId : en-US +# VoiceId : Female +# DefaultCallFlow : Default Call Flow +# Operator : +# TimeZoneId : Pacific Standard Time +# VoiceResponseEnabled : False +# CallFlows : +# Schedules : +# CallHandlingAssociations : +# Status : +# DialByNameResourceId : +# DirectoryLookupScope : +# ApplicationInstances : {fa2f17ec-ebd5-43f8-81ac-959c245620fa, 56421bbe-5649-4208-a60c-24dbeded6f18, c7af9c3c-ae40-455d-a37c-aeec771e623d} +``` + +This example gets the AA that has the identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +### Example 3 +``` +Get-CsAutoAttendant -First 10 +``` + +This example gets the first ten auto attendants configured for use in the organization. + +### Example 4 +``` +Get-CsAutoAttendant -Skip 5 -First 10 +``` + +This example skips initial 5 auto attendants and gets the next 10 AAs configured in the organization. + +## PARAMETERS + +### -Identity +The identity for the AA to be retrieved. If this parameter is not specified, then all created AAs in the organization are returned. +If you specify this parameter, you can't specify the other parameters. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -First +The First parameter gets the first N auto attendants, up to a maximum of 100 at a time. +When not specified, the default behavior is to return the first 100 auto attendants. It is intended to be used in conjunction with the `-Skip` parameter for pagination purposes. +If a number greater than 100 is supplied, the request will fail. + +```yaml +Type: System.UInt32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Skip +The Skip parameter skips the first N auto attendants. It is intended to be used in conjunction with the `-First` parameter for pagination purposes. + +```yaml +Type: System.UInt32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NameFilter +If specified, only auto attendants whose names match that value would be returned. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SortBy +If specified, the retrieved auto attendants would be sorted by the specified property. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Descending +If specified, the retrieved auto attendants would be sorted in descending order. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeStatus +If specified, the status records for each auto attendant in the result set are also retrieved. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeContent +If specified, only auto attendants' names, identities and associated application instances will be retrieved. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Get-CsAutoAttendant cmdlet accepts a string as the Identity parameter. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[Get-CsAutoAttendantStatus](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantstatus) + +[New-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/new-csautoattendant) + +[Remove-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/remove-csautoattendant) + +[Set-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/set-csautoattendant) + +[Update-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/update-csautoattendant) diff --git a/teams/teams-ps/teams/Get-CsAutoAttendantHolidays.md b/teams/teams-ps/teams/Get-CsAutoAttendantHolidays.md new file mode 100644 index 0000000000..92114b548b --- /dev/null +++ b/teams/teams-ps/teams/Get-CsAutoAttendantHolidays.md @@ -0,0 +1,141 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csautoattendantholidays +applicable: Microsoft Teams +title: Get-CsAutoAttendantHolidays +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsAutoAttendantHolidays + +## SYNOPSIS +Use Get-CsAutoAttendantHolidays cmdlet to get the holiday information for an existing Auto Attendant (AA). + +## SYNTAX + +``` +Get-CsAutoAttendantHolidays [-Identity] <string> [-Force] [-Names <List[string]>] [-Years <List[int]>] [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsAutoAttendantHolidays provides a convenient way to visualize the information of all the holidays contained within an auto attendant. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" +``` + +In this example, the Get-CsAutoAttendantHolidays cmdlet is used to get all holidays in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -Years @(2017) +``` + +In this example, the Get-CsAutoAttendantHolidays cmdlet is used to get all holidays in year 2017 in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +### -------------------------- Example 3 -------------------------- +``` +Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -Years @(2017) -Names @("Christmas") +``` + +In this example, the Get-CsAutoAttendantHolidays cmdlet is used to get holiday named Christmas in the year 2017 in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +### -------------------------- Example 4 -------------------------- +``` +(Get-CsAutoAttendantHolidays -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" -Years @(2017) -Names @("Christmas")).DateTimeRanges +``` + +In this example, the Get-CsAutoAttendantHolidays cmdlet is used to retrieve the DateTimeRanges for the holiday named Christmas in the year 2017 in an auto attendant with Identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +## PARAMETERS + +### -Identity +Represents the identifier for the auto attendant whose holidays are to be retrieved. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Years +The Years parameter represents the years for the holidays to be retrieved. If this parameter is not specified, then holidays for all years in the AA are returned. + +```yaml +Type: System.Collections.Generic.List[System.String] +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Names +The Names parameter represents the names for the holidays to be retrieved. If this parameter is not specified, then all holidays in the AA are returned. + +```yaml +Type: System.Collections.Generic.List[System.Int32] +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Get-CsAutoAttendantHolidays cmdlet accepts a string as the Identity parameter. + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.HolidayVisRecord + +## NOTES +The DateTimeRanges parameter in the output needs to be explicitly referenced to show the value. See Example 4 for one way of doing it. + +## RELATED LINKS + +[Import-CsAutoAttendantHolidays](https://learn.microsoft.com/powershell/module/teams/import-csautoattendantholidays) + +[Export-CsAutoAttendantHolidays](https://learn.microsoft.com/powershell/module/teams/export-csautoattendantholidays) diff --git a/skype/skype-ps/skype/Get-CsAutoAttendantStatus.md b/teams/teams-ps/teams/Get-CsAutoAttendantStatus.md similarity index 86% rename from skype/skype-ps/skype/Get-CsAutoAttendantStatus.md rename to teams/teams-ps/teams/Get-CsAutoAttendantStatus.md index 914a882129..69b5630115 100644 --- a/skype/skype-ps/skype/Get-CsAutoAttendantStatus.md +++ b/teams/teams-ps/teams/Get-CsAutoAttendantStatus.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csautoattendantstatus -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csautoattendantstatus +applicable: Microsoft Teams title: Get-CsAutoAttendantStatus schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsAutoAttendantStatus @@ -15,18 +15,15 @@ ms.reviewer: ## SYNOPSIS Use Get-CsAutoAttendantStatus cmdlet to get the status of an Auto Attendant (AA) provisioning. - ## SYNTAX ``` Get-CsAutoAttendantStatus -Identity <String> [-IncludeResources <List>] [-Tenant <Guid>] [<CommonParameters>] ``` - ## DESCRIPTION This cmdlet provides a way to return the provisioning status of an auto attendant configured for use in your organization. - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -52,7 +49,7 @@ Represents the identifier for the auto attendant whose provisioning status is to Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: 0 @@ -72,7 +69,7 @@ Type: System.Collections.Generic.List Parameter Sets: (All) Aliases: Accepted values: AudioFile, DialByNameVoiceResponses, SipProvisioning -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -87,7 +84,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -97,7 +94,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -112,5 +109,4 @@ The Get-CsAutoAttendantStatus cmdlet accepts a string as the Identity parameter. ## RELATED LINKS -[Get-CsAutoAttendant](Get-CsAutoAttendant.md) - +[Get-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/get-csautoattendant) diff --git a/skype/skype-ps/skype/Get-CsAutoAttendantSupportedLanguage.md b/teams/teams-ps/teams/Get-CsAutoAttendantSupportedLanguage.md similarity index 85% rename from skype/skype-ps/skype/Get-CsAutoAttendantSupportedLanguage.md rename to teams/teams-ps/teams/Get-CsAutoAttendantSupportedLanguage.md index d8b9c694b9..c6cb4253af 100644 --- a/skype/skype-ps/skype/Get-CsAutoAttendantSupportedLanguage.md +++ b/teams/teams-ps/teams/Get-CsAutoAttendantSupportedLanguage.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csautoattendantsupportedlanguage -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csautoattendantsupportedlanguage +applicable: Microsoft Teams title: Get-CsAutoAttendantSupportedLanguage schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsAutoAttendantSupportedLanguage @@ -49,7 +49,7 @@ The Identity parameter designates a specific language to be retrieved. If this p Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 0 @@ -64,7 +64,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -74,7 +74,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -85,8 +85,6 @@ The Get-CsAutoAttendantSupportedLanguage cmdlet accepts a string as the Identity ### Microsoft.Rtc.Management.Hosted.OAA.Models.Language - ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsAutoAttendantSupportedTimeZone.md b/teams/teams-ps/teams/Get-CsAutoAttendantSupportedTimeZone.md similarity index 84% rename from skype/skype-ps/skype/Get-CsAutoAttendantSupportedTimeZone.md rename to teams/teams-ps/teams/Get-CsAutoAttendantSupportedTimeZone.md index 89b540ffb4..1e0491d7e4 100644 --- a/skype/skype-ps/skype/Get-CsAutoAttendantSupportedTimeZone.md +++ b/teams/teams-ps/teams/Get-CsAutoAttendantSupportedTimeZone.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csautoattendantsupportedtimezone -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csautoattendantsupportedtimezone +applicable: Microsoft Teams title: Get-CsAutoAttendantSupportedTimeZone schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsAutoAttendantSupportedTimeZone @@ -40,7 +40,6 @@ Get-CsAutoAttendantSupportedTimeZone -Identity "Pacific Standard Time" This example gets the timezone that the Identity parameter specifies (Pacific Standard Time). - ## PARAMETERS ### -Identity @@ -50,7 +49,7 @@ The Identity parameter specifies a time zone to be retrieved. If this parameter Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 0 @@ -65,7 +64,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -75,7 +74,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -88,9 +87,6 @@ The Get-CsAutoAttendantSupportedTimeZone cmdlet accepts a string as the Identity ### Microsoft.Rtc.Management.Hosted.OAA.Models.TimeZone - ## NOTES - ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsAutoAttendantTenantInformation.md b/teams/teams-ps/teams/Get-CsAutoAttendantTenantInformation.md similarity index 80% rename from skype/skype-ps/skype/Get-CsAutoAttendantTenantInformation.md rename to teams/teams-ps/teams/Get-CsAutoAttendantTenantInformation.md index e761af416e..92a3a9bbc1 100644 --- a/skype/skype-ps/skype/Get-CsAutoAttendantTenantInformation.md +++ b/teams/teams-ps/teams/Get-CsAutoAttendantTenantInformation.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csautoattendanttenantinformation -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csautoattendanttenantinformation +applicable: Microsoft Teams title: Get-CsAutoAttendantTenantInformation schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsAutoAttendantTenantInformation @@ -33,7 +33,6 @@ Get-CsAutoAttendantTenantInformation Gets the default auto attendant information for the logged in tenant. - ## PARAMETERS ### -Tenant @@ -42,7 +41,7 @@ Gets the default auto attendant information for the logged in tenant. Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -52,7 +51,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -65,4 +64,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md b/teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md index 6982e39e14..b9a3895727 100644 --- a/teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md +++ b/teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md @@ -1,25 +1,34 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-csbatchpolicyassignmentoperation +online version: https://learn.microsoft.com/powershell/module/teams/get-csbatchpolicyassignmentoperation +title: Get-CsBatchPolicyAssignmentOperation schema: 2.0.0 author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsBatchPolicyAssignmentOperation ## SYNOPSIS -**Note:** This cmdlet is currently in public preview. - -This cmdlet is used to assign retrieve the status of batch policy assignment operations. +This cmdlet is used to retrieve the status of batch policy assignment operations. ## SYNTAX +### Get (Default) +``` +Get-CsBatchPolicyAssignmentOperation [-Status <String>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### Get1 ``` -Get-CsBatchPolicyAssignmentOperation [-OperationId <UniqueIdentifier>] +Get-CsBatchPolicyAssignmentOperation -Identity <String> [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [<CommonParameters>] ``` ## DESCRIPTION @@ -27,12 +36,12 @@ This cmdlets returns the status of all batch policy assignment operations for th ## EXAMPLES -### Example 1 -In this example, the status of all batch assignment operations is returned. - -``` +### EXAMPLE 1 +```powershell Get-CsBatchPolicyAssignmentOperation +``` +```output OperationId OperationName OverallStatus CreatedTime CreatedBy ----------- ------------- ------------- ----------- --------- e640a5c9-c74f-4df7-b62e-4b01ae878bdc Assigning Kiosk mtg Completed 1/30/2020 3:21:07 PM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 @@ -40,12 +49,14 @@ e640a5c9-c74f-4df7-b62e-4b01ae878bdc Assigning Kiosk mtg Completed 1/30/ 47bbc636-365d-4441-af34-9e0eceb05ef1 Completed 1/30/2020 4:14:22 PM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 ``` -### Example 2 -In this example, the details of a specific operation are returned. +In this example, the status of all batch assignment operations is returned. -``` +### EXAMPLE 2 +```powershell Get-CsBatchPolicyAssignmentOperation -OperationId 01b9b2b7-5dbb-487c-b4ea-887c7c66559c | fl +``` +```output OperationId : 01b9b2b7-5dbb-487c-b4ea-887c7c66559c OperationName : Assigning allow calling OverallStatus : Completed @@ -60,12 +71,14 @@ UserState : {f0d9c148-27c1-46f5-9685-544d20170ea1, cc05e18d-5fc0-4096-8461 bcff5b7e-8d3c-4721-b34a-63552a6a53f9} ``` -### Example 3 -In this example, the UserState property is expanded to see the status of each user in the batch. In this example, one of the users was not found. +In this example, the details of a specific operation are returned. -``` +### EXAMPLE 3 +```powershell Get-CsBatchPolicyAssignmentOperation -OperationId 001141c3-1daa-4da1-88e9-66cc01c511e1 | Select -ExpandProperty UserState +``` +```output Id Result State -- ------ ----- f0d9c148-27c1-46f5-9685-544d20170ea1 Success Completed @@ -73,14 +86,31 @@ cc05e18d-5fc0-4096-8461-ded64d7356e0 Success Completed bcff5b7e-8d3c-4721-b34a-63552a6a53f9 User not found Completed ``` +In this example, the UserState property is expanded to see the status of each user in the batch. In this example, one of the users was not found. + ## PARAMETERS -### -OperationId +### -Identity The ID of a batch policy assignment operation. ```yaml Type: String -Parameter Sets: +Parameter Sets: Get1 +Aliases: OperationId + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Status +Option filter + +```yaml +Type: String +Parameter Sets: Get Aliases: Required: False @@ -89,9 +119,99 @@ Default value: None Accept pipeline input: False Accept wildcard characters: False ``` + +### -Break +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -132,7 +252,13 @@ Contains the status for each user in the batch. **Id:** The ID of the user as specified when the batch was submitted. Either the user object ID (guid) or UPN/SIP/email. -**result:** The result of the assignment operation for the user: Success or an error. +**result:** The result of the assignment operation for the user: Success or an error. Some common errors include: +- User not found. Check the ID or SIP address of the user to confirm it is correct. If the UPN or email address was used, but it does not match the SIP address, then the user will not be found. +- Multiple users found with a given SIP address. This is typically a result of on-prem to cloud sync. Check your directory and update the affected users. +- User invalid. If you are syncing users from on-prem to the cloud, some users might not have been synced properly and are in an invalid state. Check the sync status for the user. +- User ineligible for the policy or missing a necessary license. Check the documentation for the specific policy type being assigned to understand the requirements and update the user accordingly. +- The policy settings are incorrect. Check the documentation for the specific policy type being assigned to understand the requirements and update the policy accordingly. +- Unknown errors. In rare cases, there can be transient system errors that failed on all initial retry attempts during batch process. Resubmit these users in a separate batch. **state:** The status for the user: NotStarted, InProgress, Completed @@ -140,4 +266,4 @@ Contains the status for each user in the batch. ## RELATED LINKS -[New-CsBatchPolicyAssignmentOperation]() +[New-CsBatchPolicyAssignmentOperation](https://learn.microsoft.com/powershell/module/teams/new-csbatchpolicyassignmentoperation) diff --git a/teams/teams-ps/teams/Get-CsBatchTeamsDeploymentStatus.md b/teams/teams-ps/teams/Get-CsBatchTeamsDeploymentStatus.md new file mode 100644 index 0000000000..2fdd9166f2 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsBatchTeamsDeploymentStatus.md @@ -0,0 +1,85 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsBatchTeamsDeploymentStatus +title: Get-CsBatchTeamsDeploymentStatus +schema: 2.0.0 +--- + +# Get-CsBatchTeamsDeploymentStatus + +## SYNOPSIS + +This cmdlet is used to get the status of the batch deployment orchestration. + +## SYNTAX + +```powershell +Get-CsBatchTeamsDeploymentStatus -OrchestrationId <String> + -InputObject <IConfigApiBasedCmdletsIdentity> + [<CommonParameters>] +``` + +## DESCRIPTION +After deploying teams using New-CsBatchTeamsDeployment, an admin can check the status of the job/orchestration using Get-CsBatchTeamsDeploymentStatus. + +To learn more, see [Deploy Teams at scale for frontline workers](https://learn.microsoft.com/microsoft-365/frontline/deploy-teams-at-scale). + +## EXAMPLES + +### EXAMPLE 1 +```powershell +Get-CsBatchTeamsDeploymentStatus -OrchestrationId "My-Orchestration-Id" +``` + +This command provides the status of the specified batch deployment orchestrationId. + +## PARAMETERS + +### OrchestrationId +This ID is generated when a batch deployment is submitted with the New-CsBatchTeamsDeployment cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +The Identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Status of the orchestrationId + +Running: The orchestration is running. +Completed: The orchestration is completed, either succeeded, partially succeeded, or failed. + +## NOTES + +## RELATED LINKS + +[New-CsBatchTeamsDeployment](https://learn.microsoft.com/powershell/module/teams/new-csbatchteamsdeployment) diff --git a/skype/skype-ps/skype/Get-CsCallQueue.md b/teams/teams-ps/teams/Get-CsCallQueue.md similarity index 75% rename from skype/skype-ps/skype/Get-CsCallQueue.md rename to teams/teams-ps/teams/Get-CsCallQueue.md index ffaf7e00e6..9ea06bec8e 100644 --- a/skype/skype-ps/skype/Get-CsCallQueue.md +++ b/teams/teams-ps/teams/Get-CsCallQueue.md @@ -1,13 +1,14 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cscallqueue -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-cscallqueue +applicable: Microsoft Teams title: Get-CsCallQueue schema: 2.0.0 ms.reviewer: manager: bulenteg -ms.author: tomkau author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney --- # Get-CsCallQueue @@ -18,7 +19,7 @@ The Get-CsCallQueue cmdlet returns the identified Call Queues. ## SYNTAX ``` -Get-CsCallQueue [-Identity <Guid>] [-Tenant <Guid>] [-First <Int32>] [-Skip <Int32>] [-ExcludeContent <Switch>] [-Sort <String>] [-Descending <Switch>] [-NameFilter <String>] [<CommonParameters>] +Get-CsCallQueue [-Identity <Guid>] [-Tenant <Guid>] [-First <Int32>] [-Skip <Int32>] [-ExcludeContent <Switch>] [-Sort <String>] [-Descending <Switch>] [-NameFilter <String>] [<CommonParameters>] ``` ## DESCRIPTION @@ -31,7 +32,7 @@ The Get-CsCallQueue cmdlet lets you retrieve information about the Call Queues i Get-CsCallQueue ``` -This example gets all Call Queues in the organization. +This example gets the first 100 call queues in the organization. ### -------------------------- Example 2 -------------------------- ``` @@ -40,7 +41,6 @@ Get-CsCallQueue -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 This example gets the Call Queue with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no Call Queue exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. - ## PARAMETERS ### -Identity @@ -49,8 +49,8 @@ PARAMVALUE: Guid ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -65,8 +65,8 @@ PARAMVALUE: Guid ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -76,13 +76,15 @@ Accept wildcard characters: False ``` ### -First -The First parameter gets the first N Call Queues. The default behavior is to return the first 100 number of queues. It is intended to be used for pagination purposes. +The First parameter gets the first N Call Queues, up to a maximum of 100 at a time. +When not specified, the default behavior is to return the first 100 call queues. It is intended to be used in conjunction with the `-Skip` parameter for pagination purposes. +If a number greater than 100 is supplied, the request will fail. ```yaml Type: Int32 Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -92,13 +94,13 @@ Accept wildcard characters: False ``` ### -Skip -The Skip parameter skips the first N Call Queues. It is intended to be used for pagination purposes. +The Skip parameter skips the first N call queues. It is intended to be used in conjunction with the `-First` parameter for pagination purposes. ```yaml Type: Int32 Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -113,8 +115,8 @@ The ExcludeContent parameter only displays the Name and Id of the Call Queues ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -129,8 +131,8 @@ The Sort parameter specifies the property used to sort. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: True Position: Named @@ -145,8 +147,8 @@ The Descending parameter sorts Call Queues in descending order ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -161,8 +163,8 @@ The NameFilter parameter returns Call Queues where name contains specified strin ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: True Position: Named @@ -172,19 +174,17 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### Identity Represents the unique identifier of a Call Queue. - ## OUTPUTS ### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue ## NOTES - ## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsCallingLineIdentity.md b/teams/teams-ps/teams/Get-CsCallingLineIdentity.md new file mode 100644 index 0000000000..bbd56f2336 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsCallingLineIdentity.md @@ -0,0 +1,102 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cscallinglineidentity +applicable: Microsoft Teams +title: Get-CsCallingLineIdentity +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsCallingLineIdentity + +## SYNOPSIS +Use the `Get-CsCallingLineIdentity` cmdlet to display the Caller ID policies for your organization. + +## SYNTAX + +### Identity (Default) +``` +Get-CsCallingLineIdentity [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsCallingLineIdentity [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Use the `Get-CsCallingLineIdentity` cmdlet to display the Caller ID policies for your organization. + +## EXAMPLES + +### Example 1 +``` +PS C:\> Get-CsCallingLineIdentity +``` + +The example gets and displays the Caller ID policies for your organization. + +### Example 2 +``` +PS C:\> Get-CsCallingLineIdentity -Filter "tag:Sales*" +``` + +The example gets and displays the Caller ID policies with Identity starting with Sales. + +## PARAMETERS + +### -Identity +The Identity parameter identifies the Caller ID policy. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +The Filter parameter lets you insert a string through which your search results are filtered. + +```yaml +Type: String +Parameter Sets: (Filter) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Grant-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/grant-cscallinglineidentity) + +[Set-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/set-cscallinglineidentity) + +[New-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/new-cscallinglineidentity) + +[Remove-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/remove-cscallinglineidentity) diff --git a/teams/teams-ps/teams/Get-CsCloudCallDataConnection.md b/teams/teams-ps/teams/Get-CsCloudCallDataConnection.md new file mode 100644 index 0000000000..f2b7e131f9 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsCloudCallDataConnection.md @@ -0,0 +1,62 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Get-CsCloudCallDataConnection +online version: https://learn.microsoft.com/powershell/module/teams/get-cscloudcalldataconnection +schema: 2.0.0 +author: 2012ucp1544 +ms.author: uditagrawal +ms.reviewer: pbafna +manager: subadjat + +--- + +# Get-CsCloudCallDataConnection + +## SYNOPSIS +This cmdlet retrieves an already existing online call data connection. + +## SYNTAX + +```powershell +Get-CsCloudCallDataConnection [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet retrieves an already existing online call data connection. Output of this cmdlet contains a token value, which is needed when configuring your on-premises environment with Set-CsCloudCallDataConnector. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsCloudCallDataConnection + +Token +----- +00000000-0000-0000-0000-000000000000 +``` + +Returns a token value, which is needed when configuring your on-premises environment with Set-CsCloudCallDataConnector. + +## 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +The Get-CsCloudCallDataConnection cmdlet is only supported in commercial environments from Teams PowerShell Module versions 4.6.0 or later. + +## RELATED LINKS + +[Configure Call Data Connector](https://learn.microsoft.com/skypeforbusiness/hybrid/configure-call-data-connector) +[New-CsCloudCallDataConnection](https://learn.microsoft.com/powershell/module/teams/new-cscloudcalldataconnection) diff --git a/teams/teams-ps/teams/Get-CsComplianceRecordingForCallQueueTemplate.md b/teams/teams-ps/teams/Get-CsComplianceRecordingForCallQueueTemplate.md new file mode 100644 index 0000000000..9d668b7749 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsComplianceRecordingForCallQueueTemplate.md @@ -0,0 +1,89 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsComplianceRecordingForCallQueueTemplate +applicable: Microsoft Teams +title: Get-CsComplianceRecordingForCallQueueTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsComplianceRecordingForCallQueueTemplate + +## SYNTAX + +```powershell +Get-CsComplianceRecordingForCallQueueTemplate [-Id <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Use the Get-CsComplianceRecordingForCallQueueTemplate cmdlet to retrieve a Compliance Recording for Call Queues template. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsComplianceRecordingForCallQueueTemplate +``` + +This example gets all Compliance Recording for Call Queue Templates in the organization. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsComplianceRecordingForCallQueueTemplate -Id 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +``` + +This example gets the Compliance Recording for Call Queue template with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no Compliance Recording for Call Queue template exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. + +## PARAMETERS + +### -Id +The Id parameter is the unique identifier assigned to the Compliance Recording for Call Queue template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[New-CsComplianceRecordingForCallQueueTemplate](./New-CsComplianceRecordingForCallQueueTemplate.md) + +[Set-CsComplianceRecordingForCallQueueTemplate](./Set-CsComplianceRecordingForCallQueueTemplate.md) + +[Remove-CsComplianceRecordingForCallQueueTemplate](./Remove-CsComplianceRecordingForCallQueueTemplate.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + diff --git a/teams/teams-ps/teams/Get-CsDialPlan.md b/teams/teams-ps/teams/Get-CsDialPlan.md new file mode 100644 index 0000000000..f7d347abb0 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsDialPlan.md @@ -0,0 +1,169 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csdialplan +applicable: Microsoft Teams +title: Get-CsDialPlan +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Get-CsDialPlan + +## SYNOPSIS +Returns information about the dial plans used in your organization. +This cmdlet was introduced in Lync Server 2010. + +## SYNTAX + +### Identity (Default) +``` +Get-CsDialPlan [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsDialPlan [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet returns information about one or more dial plans (also known as a location profiles) in an organization. +Dial plans provide information required to enable Enterprise Voice users to make telephone calls. +Dial plans are also used by the Conferencing Attendant application for dial-in conferencing. +A dial plan determines such things as which normalization rules are applied and whether a prefix must be dialed for external calls. + +Note: You can use the Get-CsDialPlan cmdlet to retrieve specific information about the normalization rules of a dial plan, but if that's the only dial plan information you need, you can also use the Get-CsVoiceNormalizationRule cmdlet. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsDialPlan +``` + +Example 1 returns a collection of all the dial plans configured for use in your organization; this is done by calling the Get-CsDialPlan cmdlet without any additional parameters. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsDialPlan -Identity RedmondDialPlan +``` + +In Example 2, the Identity parameter is used to limit the retrieved data to dial plans that have a per-user dial plan with the Identity RedmondDialPlan. +Because identities must be unique, this command will return only the specified dial plan. + +### -------------------------- Example 3 -------------------------- +``` +Get-CsDialPlan -Identity site:Redmond +``` + +Example 3 is identical to Example 2 except that instead of retrieving a per-user dial plan, we're retrieving a dial plan assigned to a site. +We do that by specifying the value site: followed by the site name (in this case Redmond) of the site we want to retrieve. + +### -------------------------- Example 4 -------------------------- +``` +Get-CsDialPlan -Filter tag:* +``` + +This example uses the Filter parameter to return a collection of all the dial plans that have been configured at the per-user scope. +(Settings configured at the per-user, or tag, scope can be directly assigned to users and groups.) The wildcard string tag:* instructs the cmdlet to return only those dial plans that have an identity beginning with the string value tag:, which identifies a dial plan as a per-user dial plan. + +### -------------------------- Example 5 -------------------------- +``` +Get-CsDialPlan | Select-Object -ExpandProperty NormalizationRules +``` + +This example displays the normalization rules used by the dial plans configured for use in your organization. +Because the NormalizationRules property consists of an array of objects, the complete set of normalization rules is typically not displayed on screen. +To see all of these rules, this sample command first uses the Get-CsDialPlan cmdlet to retrieve a collection of all the dial plans. +That collection is then piped to the Select-Object cmdlet; in turn, the ExpandProperty parameter of the Select-Object cmdlet is used to "expand" the values found in the NormalizationRules property. +Expanding the values simply means that all the normalization rules will be listed out individually on the screen, the same output that would be seen if the Get-CsVoiceNormalizationRule cmdlet had been called. + +### -------------------------- Example 6 -------------------------- +``` +Get-CsDialPlan | Where-Object {$_.Description -match "Redmond"} +``` + +In Example 6, the Get-CsDialPlan cmdlet and the Where-Object cmdlet are used to retrieve a collection of all the dial plans that include the word Redmond in their description. +To do this, the command first uses the Get-CsDialPlan cmdlet to retrieve all the dial plans. +That collection is then piped to the Where-Object cmdlet, which applies a filter that limits the returned data to profiles that have the word Redmond somewhere in their Description. + +## PARAMETERS + +### -Identity +The unique identifier designating the scope, and for per-user scope a name, to identify the dial plan you want to retrieve. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Performs a wildcard search that allows you to narrow down your results to only dial plans with identities that match the given wildcard string. + +```yaml +Type: String +Parameter Sets: Filter, (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Retrieves the dial plan information from the local replica of the Central Management store, rather than the Central Management store itself. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +{{Fill Tenant Description}} + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.WritableConfig.Policy.Voice.LocationProfile + +## NOTES + +## RELATED LINKS + +[Get-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/get-cstenantdialplan) diff --git a/teams/teams-ps/teams/Get-CsEffectiveTenantDialPlan.md b/teams/teams-ps/teams/Get-CsEffectiveTenantDialPlan.md new file mode 100644 index 0000000000..e7be699f75 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsEffectiveTenantDialPlan.md @@ -0,0 +1,137 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cseffectivetenantdialplan +applicable: Microsoft Teams +title: Get-CsEffectiveTenantDialPlan +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsEffectiveTenantDialPlan + +## SYNOPSIS +Use the Get-CsEffectiveTenantDialPlan cmdlet to retrieve an effective tenant dial plan. + +## SYNTAX + +``` +Get-CsEffectiveTenantDialPlan [-Identity] <UserIdParameter> [-OU <OUIdParameter>] [-ResultSize <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsEffectiveTenantDialPlan cmdlet returns information about the effective tenant dial plan in an organization. +The returned effective Tenant Dial Plan contains the EffectiveTenantDialPlanName and the Normalization rules that are effective for the user while using +the EnterpriseVoice features. The EffectiveTenantDialPlanName is in the form TenantGUID_GlobalVoiceDialPlan_TenantDialPlan. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsEffectiveTenantDialPlan -Identity Vt1_User1 +``` + +This example gets the effective tenant dial plan for the Vt1_User1. + +## PARAMETERS + +### -Identity +The Identity parameter is the unique identifier of the user for whom to retrieve the effective tenant dial plan. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing, and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OU +**Note:** This parameter is not supported in Teams PowerShell Module version 3.0.0 or later. + +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. + +```yaml +Type: OUIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +**Note:** This parameter is not supported in Teams PowerShell Module version 3.0.0 or later. + +Specifies the number of records returned by the cmdlet. +The result size can be set to any whole number between 0 and 2147483647, inclusive. +If set to 0, the command will run, but no data will be returned. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsExportAcquiredPhoneNumberStatus.md b/teams/teams-ps/teams/Get-CsExportAcquiredPhoneNumberStatus.md new file mode 100644 index 0000000000..1571bfb68b --- /dev/null +++ b/teams/teams-ps/teams/Get-CsExportAcquiredPhoneNumberStatus.md @@ -0,0 +1,107 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/get-csexportacquiredphonenumberstatus +applicable: Microsoft Teams +title: Get-CsExportAcquiredPhoneNumberStatus +author: pavellatif +ms.author: pavellatif +ms.reviewer: +manager: roykuntz +schema: 2.0.0 +--- + +# Get-CsExportAcquiredPhoneNumberStatus + +## SYNOPSIS +This cmdlet shows the status of the [Export-CsAcquiredPhoneNumber](https://learn.microsoft.com/powershell/module/teams/export-csacquiredphonenumber) cmdlet. + +## SYNTAX + +### Get-CsExportAcquiredPhoneNumberStatus (Default) +``` +Get-CsExportAcquiredPhoneNumberStatus -OrderId <String> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet returns OrderId status from the respective [Export-CsAcquiredPhoneNumber](https://learn.microsoft.com/powershell/module/teams/export-csacquiredphonenumber) operation. The response will include the download link to the file if operation has been completed. + +By default, the download link will remain active for 1 hour. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsExportAcquiredPhoneNumberStatus -OrderId 0e923e2c-ab0e-4b7a-be5a-906be8c +``` +```output +Id : 0e923e2c-ab0e-4b7a-be5a-906be8c +CreatedAt : 2024-08-29 21:50:54Z +status : Success +DownloadLinkExpiry : 2024-08-29 22:51:17Z +DownloadLink : <link> +``` +This example displays the status of the export acquired phone numbers operation. The OrderId is the output from [Export-CsAcquiredPhoneNumber](https://learn.microsoft.com/powershell/module/teams/export-csacquiredphonenumber) cmdlet. The status contains the download link for the file along with expiry date. + +### Example 2 +```powershell +PS C:\> Get-CsExportAcquiredPhoneNumberStatus -OrderId $orderId +``` +```output +Id : 0e923e2c-ab0e-4b7a-be5a-906be8c +CreatedAt : 2024-08-29 21:50:54Z +status : Success +DownloadLinkExpiry : 2024-08-29 22:51:17Z +DownloadLink : <link> +``` +This example displays the status of the export acquired phone numbers operation with the use of a variable named "orderId". + +### Example 3 +```powershell +PS C:\> $order = Get-CsExportAcquiredPhoneNumberStatus -OrderId $orderId +PS C:\> $order +``` +```output +Id : 0e923e2c-ab0e-4b7a-be5a-906be8c +CreatedAt : 2024-08-29 21:50:54Z +status : Success +DownloadLinkExpiry : 2024-08-29 22:51:17Z +DownloadLink : <link> +``` +This example stores the [Get-CsExportAcquiredPhoneNumberStatus](https://learn.microsoft.com/powershell/module/teams/get-csexportacquiredphonenumberstatus) cmdlet status for the "orderId" in the variable "order". This will allow a quick view of the order status without typing the cmdlet again. + +## PARAMETERS + +### -OrderId +The orderId of the ExportAcquiredNumberStatus cmdlet. + +```yaml +Type: String +Parameter Sets: Get +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ISkypeTelephoneNumberMgmtGetExportAcquiredTelephoneNumbersResponse + +## NOTES +The cmdlet is available in Teams PowerShell module 6.1.0 or later. + +The cmdlet is only available in commercial and GCC cloud instances. + +## RELATED LINKS +[Get-CsExportAcquiredPhoneNumberStatus](https://learn.microsoft.com/powershell/module/teams/get-csexportacquiredphonenumberstatus) diff --git a/teams/teams-ps/teams/Get-CsExternalAccessPolicy.md b/teams/teams-ps/teams/Get-CsExternalAccessPolicy.md new file mode 100644 index 0000000000..6b5e5dfbaa --- /dev/null +++ b/teams/teams-ps/teams/Get-CsExternalAccessPolicy.md @@ -0,0 +1,282 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csexternalaccesspolicy +applicable: Microsoft Teams +title: Get-CsExternalAccessPolicy +schema: 2.0.0 +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Get-CsExternalAccessPolicy + +## SYNOPSIS +Returns information about the external access policies that have been configured for use in your organization. +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; and, 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype. + +This cmdlet was introduced in Lync Server 2010. + +## SYNTAX + +### Identity (Default) +``` +Get-CsExternalAccessPolicy [-Tenant <Guid>] [-Include <PolicyFilter>] [-ApplicableTo <UserIdParameter>] + [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsExternalAccessPolicy [-Tenant <Guid>] [-Include <PolicyFilter>] [-ApplicableTo <UserIdParameter>] + [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +When you first configure Skype for Business Online your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with other people who have SIP accounts in your Online organization or in your Active Directory Domain Services for on-premises deployments. + +For on-premises deployments, users are not allowed to access Skype for Business Server over the Internet; instead, they must be logged on to your internal network before they will be able to log on to Skype for Business Server. + +That might be sufficient to meet your communication needs. +If it doesn't meet your needs, you can use external access policies to extend the ability of your users to communicate and collaborate. +External access policies can grant (or revoke) the ability of your users to do any or all of the following: + +1. Communicate with people who have SIP accounts with a federated organization. +Note that enabling federation alone will not provide users with this capability. +Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. + +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration). + +3. Access Skype for Business Server over the Internet, without having to first log on to your internal network. +This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. + +4. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. + +The Get-CsExternalAccessPolicy cmdlet provides a way for you to return information about all of the external access policies that have been configured for use in your organization. + +## EXAMPLES + +### -------------------------- EXAMPLE 1 -------------------------- +``` +Get-CsExternalAccessPolicy +``` + +Example 1 returns a collection of all the external access policies configured for use in your organization. +Calling the Get-CsExternalAccessPolicy cmdlet without any additional parameters always returns the complete collection of external access policies. + +### -------------------------- EXAMPLE 2 -------------------------- (Skype for Business Online) +``` +Get-CsExternalAccessPolicy -Identity "tag:RedmondExternalAccessPolicy" +``` + +Example 2 uses the Identity parameter to return the external access policy that has the Identity tag:RedmondExternalAccessPolicy. +Because access policy Identities must be unique, this command will never return more than one item. + +### -------------------------- EXAMPLE 2 -------------------------- (Skype for Business Server 2015) +``` +Get-CsExternalAccessPolicy -Identity site:Redmond +``` + +Example 2 uses the Identity parameter to return the external access policy that has the Identity site:Redmond. +Because access policy Identities must be unique, this command will never return more than one item. + +### -------------------------- Example 3 -------------------------- +``` +Get-CsExternalAccessPolicy -Filter tag:* +``` + +The command shown in Example 3 uses the Filter parameter to return all of the external access policies that have been configured at the per-user scope; the parameter value "tag:*" limits returned data to those policies that have an Identity that begins with the string value "tag:". +By definition, any policy that has an Identity beginning with "tag:" is a policy that has been configured at the per-user scope. + +### -------------------------- Example 4 -------------------------- +``` +Get-CsExternalAccessPolicy | Where-Object {$_.EnableFederationAccess -eq $True} +``` + +In Example 4, the Get-CsExternalAccessPolicy cmdlet and the Where-Object cmdlet are used to return all the external access policies that grant users federation access. +To do this, the Get-CsExternalAccessPolicy cmdlet is first used to return a collection of all the external access policies currently in use in the organization. +This collection is then piped to the Where-Object cmdlet, which selects only those policies where the EnableFederationAccess property is equal to True. + +### -------------------------- Example 5 -------------------------- +``` +Get-CsExternalAccessPolicy | Where-Object {$_.EnableFederationAccess -eq $True -and $_.EnablePublicCloudAccess -eq $True} +``` + +The command shown in Example 5 returns the external access policies that meet two criteria: both federation access and public cloud access are allowed. +In order to perform this task, the command first uses the Get-CsExternalAccessPolicy cmdlet to return a collection of all the access policies in use in the organization. +That collection is then piped to the Where-Object cmdlet, which picks out only those policies that meet two criteria: the EnableFederationAccess property must be equal to True and the EnablePublicCloudAccess property must also be equal to True. +Only policies in which both EnableFederationAccess and EnablePublicCloudAccess are True will be returned and displayed on the screen. + +### -------------------------- EXAMPLE 6 -------------------------- +``` +Get-CsExternalAccessPolicy -ApplicableTo "kenmyer@litwareinc.com" +``` + +In Example 6, the ApplicableTo parameter is used to return only the policies that can be assigned to the user "kenmyer@litwareinc.com". + +NOTE: The ApplicableTo parameter can only be used with Skype for Business Online; that's because, with Skype for Business Online, there might be policies that cannot be assigned to certain users due to licensing and/or country/region restrictions. + +NOTE: This command requires the Office 365 UsageLocation property to be configured for the user's Active Directory user account. + +## PARAMETERS + +### -Identity +Unique Identity assigned to the policy when it was created. +External access policies can be assigned at the global, site, or per-user scope. +To refer to the global instance use this syntax: -Identity global. +To refer to a policy at the site scope, use this syntax: -Identity site:Redmond. +To refer to a policy at the per-user scope, use syntax similar to this: -Identity RedmondPolicy. + +Note that wildcard characters such as the asterisk (*) cannot be used with the Identity parameter. +To do a wildcard search for policies, use the Filter parameter instead. + +If neither the Identity nor Filter parameters are specified, then the Get-CsExternalAccessPolicy cmdlet will bring back a collection of all the external access policies configured for use in the organization. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity, (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +**Below Content Applies To:** Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 + +Enables you to do a wildcard search for external access policies. +For example, to find all the policies configured at the site scope, use this Filter: + +`site:*` + +To find the per-user policies Seattle, Seville, and Saskatoon (all of which start with the letter "S") use this Filter: + +`"S*".` + +Note that the Filter parameter can only be applied to the policy Identity. + +**Below Content Applies To:** Skype for Business Online + +Enables you to do a wildcard search for external access policies. +For example, to find all the policies configured at the per-user scope, use this Filter: + +`"tag:*"` + +To find the per-user policies Seattle, Seville, and Saskatoon (all of which start with the letter "S") use this Filter: + +`"tag:S*"` + +Note that the Filter parameter can only be applied to the policy Identity. + +```yaml +Type: String +Parameter Sets: Filter, (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Retrieves the external access policy data from the local replica of the Central Management store rather than from the Central Management store itself. + +NOTE: This parameter is not used with Skype for Business Online. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplicableTo +Returns a list of the external access policies that can be assigned to the specified user. +For example, to return a collection of policies that can be assigned to the user kenmyer@litwareinc.com, use this command: + +`Get-CsExternalAccessPolicy -ApplicableTo "kenmyer@litwareinc.com"` + +The ApplicableTo parameter is useful because it's possible that only some of the available per-user external access policies can be assigned to a given user. +This is due to the fact that different licensing agreements and different country/region restrictions might limit the policies that can be assigned to a user. +For example, if Ken Myer works in China, country/region restrictions might limit his access to policies A, B, D, and E, Meanwhile, similar restrictions might limit Pilar Ackerman, who works in the United States, to policies A, B, C, and F. +If you call Get-CsExternalAccessPolicy without using the ApplicableTo parameter you will get back a collection of all the available policies, including any policies that can't actually be assigned to a specific user. + +The ApplicableTo parameter applies only to Skype for Business Online. +This parameter is not intended for use with the on-premises version of Skype for Business Server 2015. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Include +PARAMVALUE: Automatic | All | SubscriptionDefaults | TenantDefinedOnly + +```yaml +Type: PolicyFilter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy + +## NOTES + +## RELATED LINKS + +[Grant-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csexternalaccesspolicy) + +[New-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csexternalaccesspolicy) + +[Remove-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csexternalaccesspolicy) + +[Set-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/set-csexternalaccesspolicy) diff --git a/teams/teams-ps/teams/Get-CsGroupPolicyAssignment.md b/teams/teams-ps/teams/Get-CsGroupPolicyAssignment.md index 0374e6ed9a..015cc6cfd9 100644 --- a/teams/teams-ps/teams/Get-CsGroupPolicyAssignment.md +++ b/teams/teams-ps/teams/Get-CsGroupPolicyAssignment.md @@ -1,25 +1,21 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-csgrouppolicyassignment +online version: https://learn.microsoft.com/powershell/module/teams/get-csgrouppolicyassignment +title: Get-CsGroupPolicyAssignment schema: 2.0.0 -author: tomkau -ms.author: tomkau -ms.reviewer: --- # Get-CsGroupPolicyAssignment ## SYNOPSIS -**Note:** This cmdlet is currently only available in private preview in the pre-release Teams PowerShell module. - This cmdlet is used to return group policy assignments. ## SYNTAX -``` -Get-CsGroupPolicyAssignment [-GroupId <String>] [-PolicyType <String>] +```powershell +Get-CsGroupPolicyAssignment [-GroupId <String>] [-PolicyType <String>] [<CommonParameters>] ``` ## DESCRIPTION @@ -30,8 +26,8 @@ This cmdlets returns group policy assignments. Optional parameters allow the re ### Example 1 In this example, all group policy assignments are returned. -``` -Get-CsGroupPolicyAssignment +```powershell +Get-CsGroupPolicyAssignment GroupId PolicyType PolicyName Rank CreatedTime CreatedBy ------- ---------- ---------- ---- ----------- --------- @@ -47,7 +43,7 @@ e2a3ed24-97be-494d-8d3c-dbc04cbb878a TeamsCallingPolicy AllowCalling ### Example 2 In this example, only the policies assigned to a specific group are returned. -``` +```powershell Get-CsGroupPolicyAssignment -GroupId e050ce51-54bc-45b7-b3e6-c00343d31274 GroupId PolicyType PolicyName Rank CreatedTime CreatedBy @@ -62,7 +58,7 @@ In this example, only the policies of a specific type are returned. Get-CsGroupPolicyAssignment -PolicyType TeamsCallingPolicy -``` +```powershell GroupId PolicyType PolicyName Rank CreatedTime CreatedBy ------- ---------- ---------- ---- ----------- --------- e2a3ed24-97be-494d-8d3c-dbc04cbb878a TeamsCallingPolicy AllowCalling 1 11/4/2019 12:54:27 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 @@ -77,7 +73,7 @@ The ID of a group whose policy assignments will be returned. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: False @@ -89,10 +85,48 @@ Accept wildcard characters: False ### -PolicyType The policy type for which group policy assignments will be returned. +Possible values: + +ApplicationAccessPolicy +CallingLineIdentity +ExternalAccessPolicy +OnlineAudioConferencingRoutingPolicy +OnlineVoicemailPolicy +OnlineVoiceRoutingPolicy +TeamsAppSetupPolicy +TeamsAudioConferencingPolicy +TeamsCallHoldPolicy +TeamsCallingPolicy +TeamsCallParkPolicy +TeamsChannelsPolicy +TeamsComplianceRecordingPolicy +TeamsCortanaPolicy +TeamsEmergencyCallingPolicy +TeamsEmergencyCallRoutingPolicy +TeamsEnhancedEncryptionPolicy +TeamsEventsPolicy +TeamsFeedbackPolicy +TeamsFilesPolicy +TeamsIPPhonePolicy +TeamsMediaLoggingPolicy +TeamsMeetingBrandingPolicy +TeamsMeetingBroadcastPolicy +TeamsMeetingPolicy +TeamsMeetingTemplatePermissionPolicy +TeamsMessagingPolicy +TeamsMobilityPolicy +TeamsRoomVideoTeleConferencingPolicy +TeamsSharedCallingRoutingPolicy +TeamsShiftsPolicy +TeamsUpdateManagementPolicy +TeamsVdiPolicy +TeamsVideoInteropServicePolicy +TeamsVirtualAppointmentsPolicy +TenantDialPlan ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: False @@ -103,8 +137,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -114,8 +147,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[New-CsGroupPolicyAssignment]() +[New-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment) -[Set-CsGroupPolicyAssignment]() +[Set-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/set-csgrouppolicyassignment) -[Remove-CsGroupPolicyAssignment]() +[Remove-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csgrouppolicyassignment) diff --git a/teams/teams-ps/teams/Get-CsHybridTelephoneNumber.md b/teams/teams-ps/teams/Get-CsHybridTelephoneNumber.md new file mode 100644 index 0000000000..15b1d9e69b --- /dev/null +++ b/teams/teams-ps/teams/Get-CsHybridTelephoneNumber.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-cshybridtelephonenumber +applicable: Microsoft Teams +title: Get-CsHybridTelephoneNumber +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: + +--- + +# Get-CsHybridTelephoneNumber + +## SYNOPSIS +This cmdlet displays information about one or more hybrid telephone numbers. + +> [!IMPORTANT] +> This cmdlet is being deprecated. Use the **Get-CsPhoneNumberAssignment** cmdlet to display information about one or more phone numbers. Detailed instructions on how to use the new cmdlet can be found at [Get-CsPhoneNumberAssignment](/powershell/module/teams/get-csphonenumberassignment?view=teams-ps) + +## SYNTAX + +### Assignment (Default) +```powershell +Get-CsHybridTelephoneNumber [-TelephoneNumber <string>] -InputObject <IConfigApiBasedCmdletsIdentity> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet displays information about one or more hybrid telephone numbers used for Audio Conferencing with Direct Routing for GCC High and DoD clouds. + +Returned results are sorted by telephone number in ascending order. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsHybridTelephoneNumber -TelephoneNumber 14025551234 +``` +```output +Id O365Region SourceType TargetType TelephoneNumber UserId +-- ---------- ---------- ---------- --------------- ------ +14025551234 NOAM Hybrid 14025551234 00000000-0000-0000-0000-000000000000 +``` +This example displays information about the phone number +1 (402) 555-1234. + +### Example 2 +```powershell +Get-CsHybridTelephoneNumber +``` +```output +Id O365Region SourceType TargetType TelephoneNumber UserId +-- ---------- ---------- ---------- --------------- ------ +14025551234 Hybrid 14025551234 +14025551235 Hybrid 14025551235 +``` +This example displays information about all hybrid telephone numbers in the tenant. Note that O365Region, TargetType, and UserId will not be populated. + +## PARAMETERS + +### -TelephoneNumber +Filters the returned results to a specific phone number. The number should be specified without a prefixed "+". The phone number can't have "tel:" prefixed. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +The identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES +The cmdlet is available in Teams PowerShell module 4.5.0 or later. + +The cmdlet is only available in GCC High and DoD cloud instances. + +## RELATED LINKS +[New-CsHybridTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/new-cshybridtelephonenumber) + +[Remove-CsHybridTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/remove-cshybridtelephonenumber) diff --git a/teams/teams-ps/teams/Get-CsInboundBlockedNumberPattern.md b/teams/teams-ps/teams/Get-CsInboundBlockedNumberPattern.md new file mode 100644 index 0000000000..bf831c5aa7 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsInboundBlockedNumberPattern.md @@ -0,0 +1,96 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csinboundblockednumberpattern +applicable: Microsoft Teams +title: Get-CsInboundBlockedNumberPattern +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: bulenteg +schema: 2.0.0 +--- + +# Get-CsInboundBlockedNumberPattern + +## SYNOPSIS +Returns a list of all blocked number patterns added to the tenant list. + +## SYNTAX + +### Identity (Default) +``` +Get-CsInboundBlockedNumberPattern [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsInboundBlockedNumberPattern [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet returns a list of all blocked number patterns added to the tenant list including Name, Description, Enabled (True/False), and Pattern for each. + +## EXAMPLES + +### Example 1 +```powershell +PS> Get-CsInboundBlockedNumberPattern +``` + +In this example, the *Get-CsInboundBlockedNumberPattern* cmdlet is called without any parameters in order to return all the blocked number patterns. + +### Example 2 +```powershell +PS> Get-CsInboundBlockedNumberPattern -Filter Block* +``` + +In this example, the *Get-CsInboundBlockedNumberPattern* cmdlet will return all the blocked number patterns which identity starts with Block. + +## PARAMETERS + +### -Filter +Enables you to limit the returned data by filtering on the Identity. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the blocked number patterns to return. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/new-csinboundblockednumberpattern) + +[Set-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/set-csinboundblockednumberpattern) + +[Remove-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/remove-csinboundblockednumberpattern) diff --git a/teams/teams-ps/teams/Get-CsInboundExemptNumberPattern.md b/teams/teams-ps/teams/Get-CsInboundExemptNumberPattern.md new file mode 100644 index 0000000000..9f59ffa49a --- /dev/null +++ b/teams/teams-ps/teams/Get-CsInboundExemptNumberPattern.md @@ -0,0 +1,107 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csinboundexemptnumberpattern +applicable: Microsoft Teams +title: Get-CsInboundExemptNumberPattern +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Get-CsInboundExemptNumberPattern + +## SYNOPSIS +Returns a specific or the full list of all number patterns exempt from call blocking. + +## SYNTAX + +### Identity (Default) +``` +Get-CsInboundBlockedNumberPattern [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsInboundBlockedNumberPattern [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet returns a specific or all exempt number patterns added to the tenant list for call blocking including Name, Description, Enabled (True/False), and Pattern for each. + +## EXAMPLES + +### Example 1 +```powershell +PS>Get-CsInboundExemptNumberPattern +``` +This returns all exempt number patterns. + +### Example 2 +```powershell +PS>Get-CsInboundExemptNumberPattern -Identity "Exempt1" +``` + +This returns the exempt number patterns with Identity Exempt1. + +### Example 3 +```powershell +PS>Get-CsInboundExemptNumberPattern -Filter "Exempt*" +``` + +This example returns the exempt number patterns with Identity starting with Exempt. + +## PARAMETERS + +### -Filter +Enables you to limit the returned data by filtering on Identity. + +```yaml +Type: String +Parameter Sets: (Filter) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the exempt number pattern to be listed. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +You can use Test-CsInboundBlockedNumberPattern to test your call block and exempt phone number ranges. + +## RELATED LINKS +[New-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/new-csinboundexemptnumberpattern) + +[Set-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/set-csinboundexemptnumberpattern) + +[Remove-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/remove-csinboundexemptnumberpattern) + +[Test-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/test-csinboundblockednumberpattern) + +[Get-CsTenantBlockedCallingNumbers](https://learn.microsoft.com/powershell/module/teams/get-cstenantblockedcallingnumbers) diff --git a/teams/teams-ps/teams/Get-CsMeetingMigrationStatus.md b/teams/teams-ps/teams/Get-CsMeetingMigrationStatus.md new file mode 100644 index 0000000000..36129dc3a8 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsMeetingMigrationStatus.md @@ -0,0 +1,165 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csmeetingmigrationstatus +applicable: Microsoft Teams +title: Get-CsMeetingMigrationStatus +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsMeetingMigrationStatus + +## SYNOPSIS +You use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations. + +## SYNTAX +``` +Get-CsMeetingMigrationStatus [[-Identity] <UserIdParameter>] [-EndTime <DateTime>] [-StartTime <DateTime>] [-SummaryOnly] [-State <StateType>] [<CommonParameters>] +``` + +## DESCRIPTION +Meeting Migration Service (MMS) is a Skype for Business service that runs in the background and automatically updates Skype for Business and Microsoft Teams meetings for users. MMS is designed to eliminate the need for users to run the Meeting Migration Tool to update their Skype for Business and Microsoft Teams meetings. + +You can use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsMeetingMigrationStatus -SummaryOnly +``` + +This example is used to get a summary status of all MMS migrations. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsMeetingMigrationStatus -Identity "ashaw@contoso.com" +``` + +This example gets the meeting migration status for user ashaw@contoso.com. + +## PARAMETERS + +### -Identity +Specifies the Identity of the user account to be to be modified. A user identity can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). You can also reference a user account by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartTime +Specifies the start date of the date range. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndTime +Specifies the end date of the date range. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SummaryOnly +Specified that you want a summary status of MMS migrations returned. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +With this parameter you can filter by migration state. Possible values are: + +- Pending +- InProgress +- Failed +- Succeeded + +```yaml +Type: StateType +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +CorrelationId : 849d3e3b-3e1d-465f-8dde-785aa9e3f856 +CreateDate : 2024-04-27T00:24:00.1442688Z +FailedMeeting : 0 +InvitesUpdate : 0 +LastMessage : +MigrationType : AllToTeams +ModifiedDate : 2024-04-27T00:24:00.1442688Z +RetryCount : 0 +State : Pending +SucceededMeeting : 0 +TotalMeeting : 0 +UserId : 27c6ee67-c71d-4386-bf84-ebfdc7c3a171 +UserPrincipalName : syntest1-prod@TESTTESTMMSSYNTHETICUSWESTT.onmicrosoft.com + +where **MigrationType** can have the following values: + +- **SfbToTeams** (Skype for Business On-prem to Teams) +- **TeamsToTeams** (Teams to Teams) +- **ToSameType** (Same source and target meeting types) +- **AllToTeams** (All types to Teams) + +## RELATED LINKS +[Get-CsTenantMigrationConfiguration](https://learn.microsoft.com/powershell/module/teams/get-cstenantmigrationconfiguration) + +[Get-CsOnlineDialInConferencingTenantSettings](https://learn.microsoft.com/powershell/module/teams/get-csonlinedialinconferencingtenantsettings) + +[Start-CsExMeetingMigration](https://learn.microsoft.com/powershell/module/teams/start-csexmeetingmigration) diff --git a/teams/teams-ps/teams/Get-CsOnlineApplicationInstance.md b/teams/teams-ps/teams/Get-CsOnlineApplicationInstance.md new file mode 100644 index 0000000000..c153103192 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineApplicationInstance.md @@ -0,0 +1,188 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstance +applicable: Microsoft Teams +title: Get-CsOnlineApplicationInstance +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineApplicationInstance + +## SYNOPSIS +Get application instance for the tenant from Microsoft Entra ID. + +## SYNTAX + +``` +Get-CsOnlineApplicationInstance [[-Identity] <string>] [[-Identities] <string>] [[-ResultSize] <int>] [[-Skip] <int>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet is used to get details of an application instance. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Get-CsOnlineApplicationInstance -Identity appinstance01@contoso.com +``` + +This example returns the application instance with identity "appinstance01@contoso.com". +### -------------------------- Example 2 -------------------------- +```powershell +Get-CsOnlineApplicationInstance -Identities appinstance01@contoso.com,appinstance02@contoso.com +``` + +This example returns the application instance with identities "appinstance01@contoso.com" and "appinstance02@contoso.com". Query with multiple comma separated Identity. + +### -------------------------- Example 3 -------------------------- +```powershell +Get-CsOnlineApplicationInstance -ResultSize 10 +``` + +This example returns the first 10 application instances. + +### -------------------------- Example 4 -------------------------- +```powershell +Get-CsOnlineApplicationInstance +``` + +This example returns the details of all application instances. + +## PARAMETERS + +### -Identity +The UPN or the object ID of the application instance to retrieve. If this parameter nor parameter Identities are not provided, it will retrieve all application instances in the tenant. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identities +The UPNs or the object IDs of the application instances to retrieve, separated with comma. If this parameter nor parameter Identity are not provided, it will retrieve all application instances in the tenant. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +The result size for bulk get. This parameter is currently not working. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Skip +Skips the first specified number of returned results. The default value is 0. This parameter is currently not working. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +This switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If it isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/set-csonlineapplicationinstance) + +[New-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstance) + +[Find-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/find-csonlineapplicationinstance) + +[Sync-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/sync-csonlineapplicationinstance) diff --git a/teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociation.md b/teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociation.md new file mode 100644 index 0000000000..f837f328ee --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociation.md @@ -0,0 +1,89 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociation +applicable: Microsoft Teams +title: Get-CsOnlineApplicationInstanceAssociation +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineApplicationInstanceAssociation + +## SYNOPSIS +Use the Get-CsOnlineApplicationInstanceAssociation cmdlet to get information about the associations setup in your organization. + +## SYNTAX + +``` +Get-CsOnlineApplicationInstanceAssociation -Identity <String> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +Use the Get-CsOnlineApplicationInstanceAssociation cmdlet to get information about the associations setup between online application instances and the application configurations, like auto attendants and call queues. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Get-CsOnlineApplicationInstanceAssociation -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" +``` + +This example gets the association object for the application instance that has the identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +## PARAMETERS + +### -Identity +The identity for the application instance whose association is to be retrieved. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Get-CsOnlineApplicationInstanceAssociation cmdlet accepts a string as the Identity parameter. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.ApplicationInstanceAssociation + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineApplicationInstanceAssociationStatus](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociationstatus) + +[New-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstanceassociation) + +[Remove-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/remove-csonlineapplicationinstanceassociation) diff --git a/teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociationStatus.md b/teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociationStatus.md new file mode 100644 index 0000000000..bf4db93e15 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociationStatus.md @@ -0,0 +1,89 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociationstatus +applicable: Microsoft Teams +title: Get-CsOnlineApplicationInstanceAssociationStatus +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineApplicationInstanceAssociationStatus + +## SYNOPSIS +Use the Get-CsOnlineApplicationInstanceAssociationStatus cmdlet to get the provisioning status for the associations you have setup in your organization. + +## SYNTAX + +``` +Get-CsOnlineApplicationInstanceAssociationStatus -Identity <String> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +Use the Get-CsOnlineApplicationInstanceAssociationStatus cmdlet to get provisioning status for the associations you have setup between online application instances and the application configurations, like auto attendants and call queues. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Get-CsOnlineApplicationInstanceAssociationStatus -Identity "f7a821dc-2d69-5ae8-8525-bcb4a4556093" +``` + +This example gets the provisioning status for the association object of the application instance that has the identity of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +## PARAMETERS + +### -Identity +The identity for the application instance whose association provisioning status is to be retrieved. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Get-CsOnlineApplicationInstanceAssociationStatus cmdlet accepts a string as the Identity parameter. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.StatusRecord + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociation) + +[New-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstanceassociation) + +[Remove-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/remove-csonlineapplicationinstanceassociation) diff --git a/teams/teams-ps/teams/Get-CsOnlineAudioConferencingRoutingPolicy.md b/teams/teams-ps/teams/Get-CsOnlineAudioConferencingRoutingPolicy.md new file mode 100644 index 0000000000..e2a5e510e0 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineAudioConferencingRoutingPolicy.md @@ -0,0 +1,120 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineaudioconferencingroutingpolicy +title: Get-CsOnlineAudioConferencingRoutingPolicy +schema: 2.0.0 +--- + +# Get-CsOnlineAudioConferencingRoutingPolicy + +## SYNOPSIS + +This cmdlet retrieves all online audio conferencing routing policies for the tenant. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsOnlineAudioConferencingRoutingPolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsOnlineAudioConferencingRoutingPolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION + +Teams meeting dial-out calls are initiated from within a meeting in your organization to PSTN numbers, including call-me-at calls and calls to bring new participants to a meeting. + +To enable Teams meeting dial-out routing through Direct Routing to on-network users, you need to create and assign an Audio Conferencing routing policy called "OnlineAudioConferencingRoutingPolicy." + +The OnlineAudioConferencingRoutingPolicy policy is equivalent to the CsOnlineVoiceRoutingPolicy for 1:1 PSTN calls via Direct Routing. + +Audio Conferencing voice routing policies determine the available routes for calls from meeting dial-out based on the destination number. Audio Conferencing voice routing policies link to PSTN usages, determining routes for meeting dial-out calls by associated organizers. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-CsOnlineAudioConferencingRoutingPolicy +``` + +Retrieves all Online Audio Conferencing Routing Policy instances + +## PARAMETERS + +### -Filter + +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. To return a collection of all the per-user policies, use this syntax: -Filter "tag:*". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the Online Audio Conferencing Routing Policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsOnlineAudioConferencingRoutingPolicy](New-CsOnlineAudioConferencingRoutingPolicy.md) +[Remove-CsOnlineAudioConferencingRoutingPolicy](Remove-CsOnlineAudioConferencingRoutingPolicy.md) +[Grant-CsOnlineAudioConferencingRoutingPolicy](Grant-CsOnlineAudioConferencingRoutingPolicy.md) +[Set-CsOnlineAudioConferencingRoutingPolicy](Set-CsOnlineAudioConferencingRoutingPolicy.md) diff --git a/teams/teams-ps/teams/Get-CsOnlineAudioFile.md b/teams/teams-ps/teams/Get-CsOnlineAudioFile.md new file mode 100644 index 0000000000..65d7fc94b4 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineAudioFile.md @@ -0,0 +1,132 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineaudiofile +applicable: Microsoft Teams +title: Get-CsOnlineAudioFile +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: + +--- + +# Get-CsOnlineAudioFile + +## SYNOPSIS +Returns information about a specific or all uploaded audio files of a given application type. + +## SYNTAX + +```powershell +Get-CsOnlineAudioFile [[-Identity] <string>] [-ApplicationId <OrgAutoAttendant | HuntGroup | TenantGlobal>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet returns information on a specific or all uploaded audio files of a given application type. If you are not specifying any parameters you will get information of all uploaded audio files with ApplicationId = TenantGlobal. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsOnlineAudioFile + +``` +```Output +Id : 85364afb59a143fc9466979e0f34f749 +FileName : CustomMoH.mp3 +ApplicationId : TenantGlobal +MarkedForDeletion : False +``` +This returns information about all uploaded audio files with ApplicationId = TenantGlobal. + +### Example 2 +```powershell +Get-CsOnlineAudioFile -ApplicationId HuntGroup -Identity dcfcc31daa9246f29d94d0a715ef877e + +``` +```Output +Id : dcfcc31daa9246f29d94d0a715ef877e +FileName : SupportCQ.mp3 +ApplicationId : HuntGroup +MarkedForDeletion : False +``` +This cmdlet returns information about the audio file with Id dcfcc31daa9246f29d94d0a715ef877e and with ApplicationId = HuntGroup. + +### Example 3 +```powershell +Get-CsOnlineAudioFile -ApplicationId OrgAutoAttendant + +``` +```Output +Id : 58083ae8bc9e4a66a6b2810b2e1f4e4e +FileName : MainAAAnnouncement.mp3 +ApplicationId : OrgAutoAttendant +MarkedForDeletion : False +``` +This cmdlet returns information about all uploaded audio files with ApplicationId = OrgAutoAttendant. + +## PARAMETERS + +### -ApplicationId +The ApplicationId parameter specifies the identifier for the application that was specified when audio file was uploaded. For example, if the audio file is used with an auto attendant, then it should specified as "OrgAutoAttendant". +If the audio file is used with a hunt group (call queue), then it needs to be specified as "HuntGroup". If the audio file is used for music on hold, the it needs to specified as "TenantGlobal". + +If you are not specifying an ApplicationId it is assumed to be TenantGlobal. + +Supported values: + +- OrgAutoAttendant +- HuntGroup +- TenantGlobal + +```yaml +Type: System.string +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TenantGlobal +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Id of the specific audio file that you would like to see information about. If you are only specifying -Identity, the -ApplicationId it is assumed to be TenantGlobal. + +If you need to see the information of a specific audio file with ApplicationId of OrgAutoAttendant or HuntGroup, you need to specify -ApplicationId with the corresponding value and -Identity with the Id of the audio file. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PS module 2.4.0-preview or later. + +If you call the cmdlet without having uploaded any audio files, with a non-existing Identity or with an illegal ApplicationId, you will receive a generic error message. In addition, the ApplicationId is case sensitive. + +## RELATED LINKS +[Export-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/export-csonlineaudiofile) + +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) + +[Remove-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/remove-csonlineaudiofile) diff --git a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingBridge.md b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingBridge.md similarity index 77% rename from skype/skype-ps/skype/Get-CsOnlineDialInConferencingBridge.md rename to teams/teams-ps/teams/Get-CsOnlineDialInConferencingBridge.md index f70a7d7925..8668124a9a 100644 --- a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingBridge.md +++ b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingBridge.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingbridge -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingbridge +applicable: Microsoft Teams title: Get-CsOnlineDialInConferencingBridge schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsOnlineDialInConferencingBridge @@ -55,7 +55,6 @@ Get-CsOnlineDialInConferencingBridge -Tenant 26efe125-c070-46f9-8ed0-fc02165a167 This example shows how to return all of the audio conferencing bridges for the given tenant. - ## PARAMETERS ### -Identity @@ -64,7 +63,7 @@ Specifies the globally-unique identifier (GUID) for the audio conferencing bridg ```yaml Type: Guid Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -80,7 +79,7 @@ Specifies the name of the audio conferencing bridge. ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -94,11 +93,11 @@ Accept wildcard characters: False Specifies the domain controller that's used by the cmdlet to read or write the specified data. Valid inputs for this parameter include: -Fully qualified domain name (FQDN): +Fully qualified domain name (FQDN): `-DomainController atl-cs-001.Contoso.com` -Computer name: +Computer name: `-DomainController atl-cs-001` @@ -125,7 +124,7 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -141,7 +140,7 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -157,28 +156,7 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs]( https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -191,19 +169,14 @@ Accept wildcard characters: False ### 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/?LinkID=113216). - ## INPUTS ### None - ## OUTPUTS ### None - ## NOTES - ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-CsOnlineDialInConferencingLanguagesSupported.md b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingLanguagesSupported.md new file mode 100644 index 0000000000..b8c773dd60 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingLanguagesSupported.md @@ -0,0 +1,90 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/skype/get-csonlinedialinconferencinglanguagessupported +applicable: Microsoft Teams +title: Get-CsOnlineDialInConferencingLanguagesSupported +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineDialInConferencingLanguagesSupported + +## SYNOPSIS +Use the Get-CsOnlineDialInConferencingLanguagesSupported cmdlet to view the list of languages that are supported when an organization uses Microsoft as the dial-in audio conferencing provider. + +## SYNTAX + +``` +Get-CsOnlineDialInConferencingLanguagesSupported [-DomainController <Fqdn>] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsOnlineDialInConferencingLanguagesSupported cmdlet is used to view the primary and secondary languages that are set for a dial-in conferencing service number. +There is a primary language that is set along with secondary languages (up to 4) that can also be set. + +Primary and secondary languages are those languages that are used to play prompts when a caller calls into a dial-in service number. +When no languages are specified for a dial-in service number it will get the set of default languages. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Get-CsOnlineDialInConferencingLanguagesSupported | fl +``` + +This example allows returns the list of supported languages when you are using Microsoft as your dial-in audio conferencing provider and displays them in a formatted list. + +## PARAMETERS + +### -DomainController +Specifies the domain controller that's used by the cmdlet to read or write the specified data. +Valid inputs for this parameter include: + +Fully qualified domain name (FQDN): `-DomainController atl-cs-001.Contoso.com` + +Computer name: `-DomainController atl-cs-001` + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +Applicable: Skype for Business Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingServiceNumber.md b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingServiceNumber.md similarity index 78% rename from skype/skype-ps/skype/Get-CsOnlineDialInConferencingServiceNumber.md rename to teams/teams-ps/teams/Get-CsOnlineDialInConferencingServiceNumber.md index 192dee0c5a..daa9adb621 100644 --- a/skype/skype-ps/skype/Get-CsOnlineDialInConferencingServiceNumber.md +++ b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingServiceNumber.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingservicenumber -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinedialinconferencingservicenumber +applicable: Microsoft Teams title: Get-CsOnlineDialInConferencingServiceNumber schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsOnlineDialInConferencingServiceNumber @@ -75,7 +75,6 @@ Get-CsOnlineDialInConferencingBridge -Name "Conference Bridge" This example returns all of the default service numbers for the audio conferencing bridge named "Conference Bridge". - ## PARAMETERS ### -BridgeId @@ -85,8 +84,8 @@ When it's used it returns all of the service numbers that are configured on the ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -101,8 +100,8 @@ Specifies the default dial-in service number string. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 1 @@ -117,8 +116,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -133,8 +132,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -150,8 +149,8 @@ When it is used it returns all of the service numbers that are configured on the ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -167,8 +166,8 @@ When used it lists all of the service numbers for a specific city geocode. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -189,7 +188,7 @@ Computer name: `-DomainController atl-cs-001` Type: Fqdn Parameter Sets: (All) Aliases: DC -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -206,8 +205,8 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -228,28 +227,8 @@ If you set the ResultSize to 7 but you have only three users in your forest, the ```yaml Type: Int32 Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -259,7 +238,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -268,4 +247,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-CsOnlineDialInConferencingTenantSettings.md b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingTenantSettings.md new file mode 100644 index 0000000000..5f1ea406de --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingTenantSettings.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinedialinconferencingtenantsettings +applicable: Microsoft Teams +title: Get-CsOnlineDialInConferencingTenantSettings +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineDialInConferencingTenantSettings + +## SYNOPSIS +Use the Get-CsOnlineDialInConferencingTenantSettings cmdlet to retrieve tenant level settings for dial-in conferencing. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlineDialInConferencingTenantSettings [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlineDialInConferencingTenantSettings [-Tenant <Guid>] [-Filter <String>] [-LocalStore] + [<CommonParameters>] +``` + +## DESCRIPTION + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineDialInConferencingTenantSettings +``` + +This example returns the global setting for the tenant administrator's organization. + +## PARAMETERS + +### -Filter +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter is reserved for internal Microsoft use. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Retrieves the settings from the local replica of the Central Management store rather than from the Central Management store itself. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.WritableConfig.Settings.OnLineDialInConferencing.OnLineDialInConferencingTenantSettings + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsOnlineDialInConferencingUser.md b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingUser.md new file mode 100644 index 0000000000..7c7a3686cb --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineDialInConferencingUser.md @@ -0,0 +1,271 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinedialinconferencinguser +applicable: Microsoft Teams +title: Get-CsOnlineDialInConferencingUser +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineDialInConferencingUser + +## SYNOPSIS +Use the `Get-CsOnlineDialInConferencingUser` cmdlet to view the properties and settings of users that are enabled for dial-in conferencing and are using Microsoft as their PSTN conferencing provider. + +## SYNTAX + +``` +Get-CsOnlineDialInConferencingUser [-BridgeName <String>] [-ServiceNumber <String>] [-TenantDomain <String>] + [-LdapFilter <String>] [[-Identity] <UserIdParameter>] [-Tenant <Guid>] [-BridgeId <Guid>] [-ResultSize <Int32>] + [-DomainController <Fqdn>] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet will only return users that have been enabled for audio conferencing using Microsoft as the audio conferencing provider. +Users that are enabled for audio conferencing using a third-party audio conferencing provider won't be returned. +If there are no users in the organization that have been enabled for audio conferencing, then the cmdlet will return no results. + +The see a list of users with conferencing providers other than Microsoft use the Get-CsUserAcp cmdlet. + +**NOTE**: In the Teams PowerShell Module version 3.0 or later, the following input parameters have been deprecated for TeamsOnly customers (removed or very low usage): + +- BridgeId +- BridgeName +- DomainController +- Force +- LdapFilter +- ServiceNumber +- TenantDomain +- Common Parameters + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsOnlineDialInConferencingUser -Identity Ken.Myer@contoso.com +``` + +This example uses the User Principal Name (UPN) to retrieve the BridgeID and ServiceNumber information. + +## PARAMETERS + +### -BridgeId + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +Specifies the globally-unique identifier (GUID) for the audio conferencing bridge. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BridgeName + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +Specifies the name for the audio conferencing bridge. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the user to retrieve. +The user can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). +You can also reference a user account by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceNumber + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +Specifies a service number to serve as a filter for the returned user collection. +Only users who have been assigned the specified number will be returned. +The service number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LdapFilter + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +Enables you to limit the returned data by filtering on generic Active Directory attributes (that is, attributes that are not specific to Skype for Business Server 2015). +For example, you can limit returned data to users who work in a specific department, or users who have a specified manager or job title. +The LdapFilter parameter uses the LDAP query language when creating filters. +For example, a filter that returns only users who work in the city of Redmond would look like this: "l=Redmond", with "l" (a lowercase L) representing the Active Directory attribute (locality); "=" representing the comparison operator (equal to); and "Redmond" representing the filter value. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +Enables you to limit the number of records returned by the cmdlet. +For example, to return seven users (regardless of the number of users that are in your forest) include the ResultSize parameter and set the parameter value to 7. +Note that there is no way to guarantee which seven users will be returned. +The result size can be set to any whole number between 0 and 2147483647, inclusive. +If set to 0 the command will run, but no data will be returned. +If you set the ResultSize to 7 but you have only three users in your forest, the command will return those three users, and then complete without error. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +NOTE: This parameter is reserved for internal Microsoft use. + +Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. +For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308". +You can find your tenant ID by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantDomain + +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineDialInConferencingUser](https://learn.microsoft.com/powershell/module/teams/set-csonlinedialinconferencinguser) diff --git a/teams/teams-ps/teams/Get-CsOnlineDialOutPolicy.md b/teams/teams-ps/teams/Get-CsOnlineDialOutPolicy.md new file mode 100644 index 0000000000..050f8fa643 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineDialOutPolicy.md @@ -0,0 +1,100 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinedialoutpolicy +applicable: Microsoft Teams +title: Get-CsOnlineDialOutPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineDialOutPolicy + +## SYNOPSIS +Use the `Get-CsOnlineDialOutPolicy` cmdlet to get all the available outbound calling restriction policies in your organization. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlineDialOutPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlineDialOutPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +In Microsoft Teams, outbound calling restriction policies are used to restrict the type of audio conferencing and end user PSTN calls that can be made by users in your organization. The policies apply to all the different PSTN connectivity options for Microsoft Teams; Calling Plan, Direct Routing, and Operator Connect. + +To get all the available policies in your organization run `Get-CsOnlineDialOutPolicy`. +To assign one of these policies to a user run `Grant-CsDialoutPolicy`. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsOnlineDialOutPolicy +``` + +In Example 1, `Get-CsOnlineDialOutPolicy` is called without any additional parameters; this returns a collection of all the outbound calling restriction policies configured for use in your organization. + +### Example 2 +```powershell +Get-CsOnlineDialOutPolicy -Identity DialoutCPCandPSTNDisabled +``` + +In Example 2, `Get-CsOnlineDialOutPolicy` is used to return the per-user outbound calling restriction policy that has an Identity DialoutCPCandPSTNDisabled. Because identities are unique, this command will never return more than one item. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. To return a collection of all the per-user policies, use this syntax: -Filter "tag:*". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -Identity +Unique identifier of the outbound calling restriction policy to be returned. To refer to the global policy, use this syntax: "-Identity Global". To refer to a per-user policy, use syntax similar to this: -Identity DialoutCPCandPSTNDisabled. + +If this parameter is omitted, then all the outbound calling restriction policies configured for use in your tenant will be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Grant-CsDialoutPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csdialoutpolicy) diff --git a/teams/teams-ps/teams/Get-CsOnlineDialinConferencingPolicy.md b/teams/teams-ps/teams/Get-CsOnlineDialinConferencingPolicy.md new file mode 100644 index 0000000000..44a0e83fd6 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineDialinConferencingPolicy.md @@ -0,0 +1,101 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinedialinconferencingpolicy +applicable: Microsoft Teams +title: Get-CsOnlineDialinConferencingPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineDialinConferencingPolicy + +## SYNOPSIS +Retrieves the available Dial-in Conferencing policies in the tenant. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlineDialinConferencingPolicy [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlineDialinConferencingPolicy [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +Retrieves the available Dial-in Conferencing policies in the tenant. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineDialinConferencingPolicy +``` + +This example retrieves all the available Dial in Conferencing policies in the tenant. + +## PARAMETERS + +### -Filter +This parameter accepts a wildcard string and returns all policies with identities matching that string. For example, a Filter value of tag:* will return all policies defined at the per-user level. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A unique identifier specifying the scope and, in some cases the name, of the policy. If this parameter is omitted, all policies for the organization are returned. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Reserved for Microsoft Internal use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsOnlineDialinConferencingTenantConfiguration.md b/teams/teams-ps/teams/Get-CsOnlineDialinConferencingTenantConfiguration.md new file mode 100644 index 0000000000..7c1dbe713c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineDialinConferencingTenantConfiguration.md @@ -0,0 +1,131 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinedialinconferencingtenantconfiguration +applicable: Microsoft Teams +title: Get-CsOnlineDialinConferencingTenantConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineDialinConferencingTenantConfiguration + +## SYNOPSIS +Use the Get-CsOnlineDialinConferencingTenantConfiguration cmdlet to retrieve the tenant level configuration for dial-in conferencing. +The dial-in conferencing configuration specifies if dial-in conferencing is enabled for the tenant. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlineDialinConferencingTenantConfiguration [-Tenant <Guid>] [[-Identity] <XdsIdentity>] + [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlineDialinConferencingTenantConfiguration [-Tenant <Guid>] [-Filter <String>] [-LocalStore] + [<CommonParameters>] +``` + +## DESCRIPTION +The dial-in conferencing configuration specifies only if dial-in conferencing is enabled for the tenant. +By contrast, the dial-in conferencing tenant settings specify what functions are available during a conference call. +For example, whether or not entries and exits from the call are announced. +The settings also manage some of the administrative functions, such as when users get notification of administrative actions, like a PIN change. +For more information on settings and their customization, see Set-CsOnlineDialInConferencingTenantSettings. + +This cmdlet currently displays only the enabled or disabled status of your tenant configuration. +There is one configuration per tenant. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineDialinConferencingTenantConfiguration +``` + +This example returns the configuration for the tenant administrator's organization. + +## PARAMETERS + +### -Filter +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter is reserved for internal Microsoft use. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Retrieves the configuration from the local replica of the Central Management store rather than from the Central Management store itself. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.WritableConfig.Settings.OnLineDialInConferencing.OnLineDialInConferencingTenantConfiguration + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsOnlineDirectoryTenant.md b/teams/teams-ps/teams/Get-CsOnlineDirectoryTenant.md new file mode 100644 index 0000000000..35a0ee1afb --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineDirectoryTenant.md @@ -0,0 +1,146 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinedirectorytenant +applicable: Microsoft Teams +title: Get-CsOnlineDirectoryTenant +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineDirectoryTenant + +## SYNOPSIS +Use the Get-CsOnlineDirectoryTenant cmdlet to retrieve a tenant and associated parameters from the Business Voice Directory. + +## SYNTAX +``` +Get-CsOnlineDirectoryTenant [[-Tenant] <Guid>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +**Note**: Starting with Teams PowerShell Module 4.0, this cmdlet will be deprecated. Use the Get-CsTenant or Get-CsOnlineDialInConferencingBridge cmdlet to view information previously present in Get-CsOnlineDirectoryTenant. + +Use the Get-CsOnlineDirectoryTenant cmdlet to retrieve tenant parameters like AnnouncementsDisabled, NameRecordingDisabled and Bridges from the Business Voice Directory. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineDirectoryTenant -Tenant 7a205197-8e59-487d-b9fa-3fc1b108f1e5 +``` + +This example returns the tenant specified by GUID. + +## PARAMETERS + +### -Confirm +The Confirm switch causes the command to pause processing, and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Specifies the domain controller that's used by the cmdlet to read or write the specified data. +Valid inputs for this parameter are either the fully qualified domain name (FQDN) or the computer name. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. +For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can find your tenant ID by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Deserialized.Microsoft.Rtc.Management.Hosted.Bvd.Types.LacTenant + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumber) diff --git a/teams/teams-ps/teams/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md b/teams/teams-ps/teams/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md new file mode 100644 index 0000000000..4c7b04e076 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md @@ -0,0 +1,135 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineenhancedemergencyservicedisclaimer +applicable: Microsoft Teams +title: Get-CsOnlineEnhancedEmergencyServiceDisclaimer +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineEnhancedEmergencyServiceDisclaimer + +## SYNOPSIS +Use the Get-CsOnlineEnhancedEmergencyServiceDisclaimer cmdlet to determine whether your organization has accepted the terms and conditions of enhanced emergency service. + +## SYNTAX + +``` +Get-CsOnlineEnhancedEmergencyServiceDisclaimer [-CountryOrRegion <CountryInfo>] [-DomainController <Fqdn>] [-Force] [-Tenant <Guid>] [-Version <String>] [<CommonParameters>] +``` + +## DESCRIPTION +You can use this cmdlet to determine whether your organization has accepted the terms and conditions of enhanced emergency service. The United States is currently the only country supported. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineEnhancedEmergencyServiceDisclaimer -CountryOrRegion "US" +``` + +This example returns your organization's enhanced emergency service terms and conditions acceptance status. + +## PARAMETERS + +### -CountryOrRegion +Specifies the region or country whose terms and conditions you wish to verify. +The United States is currently the only country supported, but it must be specified as "US". + +```yaml +Type: CountryInfo +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Version +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES + +## RELATED LINKS +[Set-CsOnlineEnhancedEmergencyServiceDisclaimer](https://learn.microsoft.com/powershell/module/teams/set-csonlineenhancedemergencyservicedisclaimer) diff --git a/teams/teams-ps/teams/Get-CsOnlineLisCivicAddress.md b/teams/teams-ps/teams/Get-CsOnlineLisCivicAddress.md new file mode 100644 index 0000000000..3a889df518 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineLisCivicAddress.md @@ -0,0 +1,265 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineliscivicaddress +applicable: Microsoft Teams +title: Get-CsOnlineLisCivicAddress +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineLisCivicAddress + +## SYNOPSIS +Use the Get-CsOnlineLisCivicAddress cmdlet to retrieve information about existing emergency civic addresses defined in the Location Information Service (LIS). + +## SYNTAX + +``` +Get-CsOnlineLisCivicAddress [-AssignmentStatus <string>] [-City <string>] [-CivicAddressId <guid>] [-CountryOrRegion <string>] +[-Description <string>] [-Force] [-LocationId <guid>] [-NumberOfResultsToSkip <int>] [-PopulateNumberOfTelephoneNumbers] [-PopulateNumberOfVoiceUsers] +[-ResultSize <long>] [-ValidationStatus <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Returns one or more emergency civic addresses. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsOnlineLisCivicAddress -CivicAddressId 235678321ee38d9a5-33dc-4a32-9fb8-f234cedb91ac +``` + +This example returns the civic address with the specified identification. + +### Example 2 +```powershell +Get-CsOnlineLisCivicAddress -City Seattle +``` + +This example returns all the civic addresses in the city of Seattle. + +## PARAMETERS + +### -AssignmentStatus + +**Note:** This parameter has been deprecated from the Teams PowerShell Module version 3.0.0 or later. + +Specifies whether the retrieved addresses have been assigned to users or not. +Valid inputs are "Assigned", or "Unassigned". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -City +Specifies the city of the target civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CivicAddressId +Specifies the identity of the civic address to return. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CountryOrRegion +Specifies the country or region of the target civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies the administrator defined description of the target civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberOfResultsToSkip +Specifies the number of results to skip. +If there are a large number of civic addresses, you can limit the number of results by using the ResultSize parameter. +If you limited the first cmdlet execution to 25 results, and want to look at the next 25 locations, then you leave ResultSize at 25 and set NumberOfResultsToSkip to 25 to omit the first 25 you've reviewed. +For example the command below will return civic addresses 26-50 for Seattle. + +\`Get-CsOnlineLisCivicAddress -City Seattle -ResultSize 25 -NumberOfResultsToSkip 25\` + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopulateNumberOfTelephoneNumbers +If present, the PopulateNumberOfTelephoneNumbers switch causes the cmdlet to provide the number of phone numbers at the returned addresses. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopulateNumberOfVoiceUsers +If present, the PopulateNumberOfVoiceUsers switch causes the cmdlet to provide the number of voice users at the returned addresses. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize +Specifies the maximum number of results to return. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidationStatus +Specifies the validation status of the addresses to be returned. +Valid inputs are: Valid, Invalid, and Notvalidated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Set-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/set-csonlineliscivicaddress) + +[New-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/new-csonlineliscivicaddress) + +[Remove-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/remove-csonlineliscivicaddress) diff --git a/teams/teams-ps/teams/Get-CsOnlineLisLocation.md b/teams/teams-ps/teams/Get-CsOnlineLisLocation.md new file mode 100644 index 0000000000..2fb1346e9a --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineLisLocation.md @@ -0,0 +1,322 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinelislocation +applicable: Microsoft Teams +title: Get-CsOnlineLisLocation +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineLisLocation + +## SYNOPSIS +Use the Get-CsOnlineLisLocation cmdlet to retrieve information on previously defined locations in the Location Information Service (LIS.) + +## SYNTAX + +### GetByLocationID (Default) +``` +Get-CsOnlineLisLocation [-AssignmentStatus <string>] [-City <string>] [-CountryOrRegion <string>] [-Description <string>] [-Force] + [-NumberOfResultsToSkip <int>] [-PopulateNumberOfTelephoneNumbers] [-PopulateNumberOfVoiceUsers] [-ResultSize <long>] [-ValidationStatus <string>] + [<CommonParameters>] +``` + +### UseCivicAddressId +``` +Get-CsOnlineLisLocation -CivicAddressId <guid> [-AssignmentStatus <string>] [-City <string>] [-CountryOrRegion <string>] [-Description <string>] + [-Force] [-NumberOfResultsToSkip <int>] [-PopulateNumberOfTelephoneNumbers] [-PopulateNumberOfVoiceUsers] [-ResultSize <long>] + [-ValidationStatus <string>] [<CommonParameters>] +``` + +### UseLocation +``` +Get-CsOnlineLisLocation -Location <string> [-AssignmentStatus <string>] [-City <string>] [-CountryOrRegion <string>] [-Description <string>] + [-Force] [-NumberOfResultsToSkip <int>] [-PopulateNumberOfTelephoneNumbers] [-PopulateNumberOfVoiceUsers] [-ResultSize <long>] + [-ValidationStatus <string>] [<CommonParameters>] +``` + +### UseLocationId +``` +Get-CsOnlineLisLocation [-AssignmentStatus <string>] [-City <string>] [-CountryOrRegion <string>] [-Description <string>] [-Force] + [-NumberOfResultsToSkip <int>] [-PopulateNumberOfTelephoneNumbers] [-PopulateNumberOfVoiceUsers] [-ResultSize <long>] [-ValidationStatus <string>] + [-LocationId <guid>] [<CommonParameters>] +``` + +## DESCRIPTION + +## EXAMPLES + +### Example 1 +``` +Get-CsOnlineLisLocation -City Seattle -ResultSize 25 -ValidationStatus Validated +``` + +This example returns a maximum of 25 validated locations in Seattle. + +### Example 2 +``` +Get-CsOnlineLisLocation -CivicAddressId a363a9b8-1acd-41de-916a-296c7998a024 +``` + +This example returns the locations associated with a civic address specified by its unique identifier. + +### Example 3 +``` +Get-CsOnlineLisLocation -Location "3rd Floor Cafe" +``` + +This example returns the location described as the "3rd Floor Cafe". + +### Example 4 +``` +Get-CsOnlineLisLocation -LocationId 5aa884e8-d548-4b8e-a289-52bfd5265a6e +``` + +This example returns the information on one location specified by its unique identifier. + +## PARAMETERS + +### -CivicAddressId +Specifies the identification number of the civic address that is associated with the target locations. + +```yaml +Type: Guid +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Location +Specifies an administrator defined description of the location to retrieve. +For example, "2nd Floor Cafe", "Main Lobby", or "Office 250". + +```yaml +Type: String +Parameter Sets: UseLocation +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssignmentStatus + +**Note:** This parameter has been deprecated from the Teams PowerShell Module version 3.0.0 or later. + +Specifies whether the retrieved locations have been assigned to users or not. +Valid inputs are "Assigned", or "Unassigned". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -City +Specifies the city of the target location. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CountryOrRegion +Specifies the country or region of the target location. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Description +Specifies the administrator defined description of the civic address that is associated with the target locations. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationId +Specifies the unique identifier of the target location. + +```yaml +Type: Guid +Parameter Sets: UseLocationId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -NumberOfResultsToSkip +Specifies the number of results to skip. +If there are a large number of locations, you can limit the number of results by using the ResultSize parameter. +If you limited the first cmdlet execution to 25 results, and want to look at the next 25 locations, then you leave ResultSize at 25 and set NumberOfResultsToSkip to 25 to omit the first 25 you've reviewed. +For example the command below will return locations 26-50 for Seattle. + +\`Get-CsOnlineLisLocation -City Seattle -ResultSize 25 -NumberOfResultsToSkip 25\` + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopulateNumberOfTelephoneNumbers +If present, the PopulateNumberOfTelephoneNumbers switch causes the cmdlet to provide the number of telephone numbers at the returned locations. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopulateNumberOfVoiceUsers +If present, the PopulateNumberOfVoiceUsers switch causes the cmdlet to provide the number of voice users at the returned locations. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -ResultSize +Specifies the maximum number of results to return. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidationStatus +Specifies the validation status of the addresses to be returned. +Valid inputs are: Validated, Invalid, and Notvalidated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Returns an instance, or instances of emergency location objects. + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/set-csonlinelislocation) + +[New-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/new-csonlinelislocation) + +[Remove-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/remove-csonlinelislocation) diff --git a/teams/teams-ps/teams/Get-CsOnlineLisPort.md b/teams/teams-ps/teams/Get-CsOnlineLisPort.md new file mode 100644 index 0000000000..190850463c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineLisPort.md @@ -0,0 +1,172 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinelisport +applicable: Microsoft Teams +title: Get-CsOnlineLisPort +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineLisPort + +## SYNOPSIS +Retrieves one or more ports from the location configuration database. Each port can be associated with a location, in which case this cmdlet will also retrieve the location information of the ports. This location association is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. + +## SYNTAX + +``` +Get-CsOnlineLisPort [[-ChassisID] <string>] [-Force] [-IsDebug <bool>] [-NCSApiUrl <string>] [-PortID <string>] [-TargetStore <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet retrieves information on associations between physical locations and the port through which the client is connected. + +## EXAMPLES + +### Example 1 +``` +Get-CsOnlineLisPort +``` +```output +PortID ChassisID LocationId Description +------ --------- ---------- ----------- +G1/0/30 B8-BE-BF-4A-A3-00 9905bca0-6fb0-11ec-84a4-25019013784a +S2/0/25 F6-26-79-B5-3D-49 d7714269-ee52-4635-97b0-d7c228801d24 +``` + +Example 1 retrieves all Location Information Server (LIS) ports and any associated locations. + +### Example 2 +``` +Get-CsOnlineLisPort -ChassisID 'B8-BE-BF-4A-A3-00' -PortID 'G1/0/30' +``` +```output +PortID ChassisID LocationId Description +------ --------- ---------- ----------- +G1/0/30 B8-BE-BF-4A-A3-00 9905bca0-6fb0-11ec-84a4-25019013784a +``` + +Example 2 retrieves the location information for port G1/0/30 with ChassisID B8-BE-BF-4A-A3-00. + +## PARAMETERS + +### -ChassisID +The Media Access Control (MAC) address of the port's switch. This value will be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDebug +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NCSApiUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PortID +This parameter identifies the ID of the port. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Guid + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisPort](https://learn.microsoft.com/powershell/module/teams/set-csonlinelisport) + +[Remove-CsOnlineLisPort](https://learn.microsoft.com/powershell/module/teams/remove-csonlinelisport) diff --git a/skype/skype-ps/skype/Get-CsOnlineLisSubnet.md b/teams/teams-ps/teams/Get-CsOnlineLisSubnet.md similarity index 91% rename from skype/skype-ps/skype/Get-CsOnlineLisSubnet.md rename to teams/teams-ps/teams/Get-CsOnlineLisSubnet.md index 67127c6ac8..7aff6725b1 100644 --- a/skype/skype-ps/skype/Get-CsOnlineLisSubnet.md +++ b/teams/teams-ps/teams/Get-CsOnlineLisSubnet.md @@ -1,11 +1,11 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinelissubnet -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinelissubnet +applicable: Microsoft Teams title: Get-CsOnlineLisSubnet schema: 2.0.0 -author: kaishuipinggai -ms.author: junya +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -35,7 +35,6 @@ Get-CsOnlineLisSubnet Example 1 retrieves all Location Information Server (LIS) subnets. - ### -------------------------- Example 2 -------------------------- ``` Get-CsOnlineLisSubnet -Subnet 10.106.89.12 @@ -43,7 +42,6 @@ Get-CsOnlineLisSubnet -Subnet 10.106.89.12 Example 2 retrieves the Location Information Server (LIS) subnet for Subnet ID "10.106.89.12". - ### -------------------------- Example 3 -------------------------- ``` Get-CsOnlineLisSubnet -Subnet 2001:4898:e8:6c:90d2:28d4:76a4:ec5e @@ -51,7 +49,6 @@ Get-CsOnlineLisSubnet -Subnet 2001:4898:e8:6c:90d2:28d4:76a4:ec5e Example 2 retrieves the Location Information Server (LIS) subnet for Subnet ID "2001:4898:e8:6c:90d2:28d4:76a4:ec5e". - ## PARAMETERS ### -Force @@ -63,7 +60,7 @@ If the Force switch isn't provided in the command, you're prompted for administr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -79,7 +76,7 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -95,7 +92,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -111,7 +108,7 @@ The IP address of the subnet. This value can be either IPv4 or IPv6 format. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 1 @@ -127,7 +124,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -143,7 +140,7 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 0 @@ -155,24 +152,16 @@ Accept wildcard characters: False ### 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/?LinkID=113216). - ## INPUTS - ### System.Guid - ### System.String - ## OUTPUTS - ### System.Object - ## NOTES - ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-CsOnlineLisSwitch.md b/teams/teams-ps/teams/Get-CsOnlineLisSwitch.md new file mode 100644 index 0000000000..c5be65a3ec --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineLisSwitch.md @@ -0,0 +1,156 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinelisswitch +applicable: Microsoft Teams +title: Get-CsOnlineLisSwitch +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineLisSwitch + +## SYNOPSIS +Retrieves one or more network switches from the location configuration database. Each switch can be associated with a location, in which case this cmdlet will also retrieve the location information of the switches. This location association is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. + +## SYNTAX + +``` +Get-CsOnlineLisSwitch [[-ChassisID] <string>] [-Force] [-IsDebug <bool>] [-NCSApiUrl <string>] [-TargetStore <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet retrieves information on associations between physical locations and the network switch through which the client is connected. + +## EXAMPLES + +### Example 1 +``` +Get-CsOnlineLisSwitch +``` +```output +ChassisID LocationId Description +--------- ---------- ----------- +B8-BE-BF-4A-A3-00 9905bca0-6fb0-11ec-84a4-25019013784a DKSwitch1 +F6-26-79-B5-3D-49 d7714269-ee52-4635-97b0-d7c228801d24 USSwitch1 +``` + +Example 1 retrieves all Location Information Server (LIS) switches and any associated locations. + +### Example 2 +``` +Get-CsOnlineLisSwitch -ChassisID B8-BE-BF-4A-A3-00 +``` +```output +ChassisID LocationId Description +--------- ---------- ----------- +B8-BE-BF-4A-A3-00 9905bca0-6fb0-11ec-84a4-25019013784a DKSwitch1 +``` + +Example 2 retrieves Location Information Server (LIS) switch "B8-BE-BF-4A-A3-00" and associated location. + +## PARAMETERS + +### -ChassisID +The Media Access Control (MAC) address of the port's switch. This value will be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDebug +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NCSApiUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisSwitch](https://learn.microsoft.com/powershell/module/teams/set-csonlinelisswitch) + +[Remove-CsOnlineLisSwitch](https://learn.microsoft.com/powershell/module/teams/remove-csonlinelisswitch) diff --git a/teams/teams-ps/teams/Get-CsOnlineLisWirelessAccessPoint.md b/teams/teams-ps/teams/Get-CsOnlineLisWirelessAccessPoint.md new file mode 100644 index 0000000000..a8526f7ab2 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineLisWirelessAccessPoint.md @@ -0,0 +1,183 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineliswirelessaccesspoint +applicable: Microsoft Teams +title: Get-CsOnlineLisWirelessAccessPoint +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineLisWirelessAccessPoint + +## SYNOPSIS +Retrieves one or more wireless access points (WAPs) from the location configuration database. Each WAP can be associated with a location, in which case this cmdlet will also retrieve the location information of the WAPs. This location association is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. + +## SYNTAX + +``` +Get-CsOnlineLisWirelessAccessPoint [[-BSSID] <string>] [-Force] [-IsDebug <bool>] [-NCSApiUrl <string>] [-TargetStore <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet retrieves information on associations between physical locations and the WAP through which the client is connected. + +The BSSID (Basic Service Set Identifiers) is used to describe sections of a wireless local area network. It is the MAC of the 802.11 side of the access point. The BSSID parameter in this command also supports the wildcard format to cover all BSSIDs in the range which are sharing the same description and Location ID. The wildcard '*' can be on either the last one or two character(s). + +If a BSSID with a wildcard format is already exists, a location request with a WAP which is within this wildcard range will return the access point that is configured with the wildcard format. + +## EXAMPLES + +### Example 1 +``` +Get-CsOnlineLisWirelessAccessPoint +``` +```output +BSSID LocationId Description +----- ---------- ----------- +F0-6E-0B-C2-03-23 d7714269-ee52-4635-97b0-d7c228801d24 USWAP1 +34-E3-80-D5-AB-60 9905bca0-6fb0-11ec-84a4-25019013784a DKWAP1 +F0-6E-0B-C2-03-* b2804a1a-e4cf-47df-8964-3eaf6fe1ae3a SEWAPs +``` + +Example 1 retrieves all Location Information Server (LIS) wireless access points and any associated locations. + +### Example 2 +``` +Get-CsOnlineLisWirelessAccessPoint -BSSID F0-6E-0B-C2-03-23 +``` +```output +BSSID LocationId Description +----- ---------- ----------- +F0-6E-0B-C2-03-23 d7714269-ee52-4635-97b0-d7c228801d24 USWAP1 +``` + +Example 2 retrieves Location Information Server (LIS) wireless access point "F0-6E-0B-C2-03-23" and associated location. + +### Example 3 +``` +Get-CsOnlineLisWirelessAccessPoint -BSSID F0-6E-0B-C2-03-* +``` +```output +BSSID LocationId Description +----- ---------- ----------- +F0-6E-0B-C2-03-* b2804a1a-e4cf-47df-8964-3eaf6fe1ae3a SEWAPs +``` + +Example 3 retrieves Location Information Server (LIS) wireless access point "F0-6E-0B-C2-03-*" and associated location. + +### Example 4 +``` +Get-CsOnlineLisWirelessAccessPoint -BSSID F0-6E-0B-C2-03-12 +``` +```output +BSSID LocationId Description +----- ---------- ----------- +F0-6E-0B-C2-03-* b2804a1a-e4cf-47df-8964-3eaf6fe1ae3a SEWAPs +``` + +Example 4 retrieves Location Information Server (LIS) wireless access point "F0-6E-0B-C2-03-12" and associated location. + +## PARAMETERS + +### -BSSID +The Basic Service Set Identifier (BSSID) of the wireless access point. This value must be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. It can be presented in wildcard format. The wildcard '*' can be on either the last one or two character(s). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDebug +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NCSApiUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisWirelessAccessPoint](https://learn.microsoft.com/powershell/module/teams/set-csonlineliswirelessaccesspoint) + +[Remove-CsOnlineLisWirelessAccessPoint](https://learn.microsoft.com/powershell/module/teams/remove-csonlineliswirelessaccesspoint) diff --git a/teams/teams-ps/teams/Get-CsOnlinePSTNGateway.md b/teams/teams-ps/teams/Get-CsOnlinePSTNGateway.md new file mode 100644 index 0000000000..c7574f56ce --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlinePSTNGateway.md @@ -0,0 +1,99 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinepstngateway +applicable: Microsoft Teams +title: Get-CsOnlinePSTNGateway +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlinePSTNGateway + +## SYNOPSIS +Shows the configuration of the previously defined Session Border Controller(s) (SBC(s)) that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlinePSTNGateway [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlinePSTNGateway [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to show the configuration of the previously created Session Border Controller(s) (SBC(s)) configuration. Each configuration contains specific settings for an SBC. These settings configure such entities as SIP signaling port, whether media bypass is enabled on this SBC, will the SBC send SIP options, specify the limit of maximum concurrent sessions, The cmdlet also let drain the SBC by setting parameter -Enabled to true or false state. When the Enabled parameter set to $false, the SBC will continue existing calls, bit all new calls routed to another SBC in a route (if exists). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsOnlinePSTNGateway +``` + +This example shows all SBCs paired with the tenant. + +### Example 2 +```powershell +PS C:\> Get-CsOnlinePSTNGateway -Filter "*.contoso.com" +``` + +This example selects all SBCs with identities matching the pattern *.contoso.com, such as sbc1.contoso.com and sbc2.contoso.com. + +## PARAMETERS + +### -Filter + +```yaml +Type: String +Parameter Sets: Filter +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The parameter is optional for the cmdlet. If not set all SBCs paired to the tenant are listed. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/set-csonlinepstngateway) + +[New-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/new-csonlinepstngateway) + +[Remove-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/remove-csonlinepstngateway) diff --git a/teams/teams-ps/teams/Get-CsOnlinePstnUsage.md b/teams/teams-ps/teams/Get-CsOnlinePstnUsage.md new file mode 100644 index 0000000000..c70a50caf0 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlinePstnUsage.md @@ -0,0 +1,90 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinepstnusage +applicable: Microsoft Teams +title: Get-CsOnlinePstnUsage +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlinePstnUsage + +## SYNOPSIS +Returns information about online public switched telephone network (PSTN) usage records used in your tenant. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlinePstnUsage [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlinePstnUsage [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Online PSTN usages are string values that are used for call authorization. An online PSTN usage links an online voice policy to a route. The `Get-CsOnlinePstnUsage` cmdlet retrieves the list of all online PSTN usages available within a tenant. + +This cmdlet is used when configuring Microsoft Phone System Direct Routing. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CSOnlinePSTNUsage +``` + +This command returns the list of global PSTN usages available within the tenant. + +## PARAMETERS + +### -Filter +The Filter parameter allows you to retrieve only those PSTN usages with an Identity matching a particular wildcard string. However, the only Identity available to PSTN usages is Global, so this parameter is not useful for this cmdlet. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The level at which these settings are applied. The only identity that can be applied to PSTN usages is Global. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Set-CsOnlinePstnUsage](https://learn.microsoft.com/powershell/module/teams/set-csonlinepstnusage) diff --git a/teams/teams-ps/teams/Get-CsOnlineSchedule.md b/teams/teams-ps/teams/Get-CsOnlineSchedule.md new file mode 100644 index 0000000000..9b0227da05 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineSchedule.md @@ -0,0 +1,81 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineschedule +applicable: Microsoft Teams +title: Get-CsOnlineSchedule +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsOnlineSchedule + +## SYNOPSIS +Use the Get-CsOnlineSchedule cmdlet to get information about schedules that belong to your organization. + +## SYNTAX + +``` +Get-CsOnlineSchedule -Id <String> [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsOnlineSchedule cmdlet returns information about the schedules in your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineSchedule +``` + +This example retrieves all schedules that belong to your organization. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsOnlineSchedule -Id "f7a821dc-2d69-5ae8-8525-bcb4a4556093" +``` + +This example gets the schedules that has the Id of f7a821dc-2d69-5ae8-8525-bcb4a4556093. + +## PARAMETERS + +### -Id +The Id for the schedule to be retrieved. If this parameter is not specified, then all schedules in the organization are returned. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Get-CsOnlineSchedule cmdlet accepts a string as the Id parameter. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.Schedule + +## NOTES + +## RELATED LINKS + +[New-CsOnlineTimeRange](https://learn.microsoft.com/powershell/module/teams/new-csonlinetimerange) + +[New-CsOnlineDateTimeRange](https://learn.microsoft.com/powershell/module/teams/new-csonlinedatetimerange) + +[New-CsAutoAttendantCallFlow](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow) diff --git a/skype/skype-ps/skype/Get-CsOnlineSipDomain.md b/teams/teams-ps/teams/Get-CsOnlineSipDomain.md similarity index 76% rename from skype/skype-ps/skype/Get-CsOnlineSipDomain.md rename to teams/teams-ps/teams/Get-CsOnlineSipDomain.md index c480acf9c3..0627f86a2a 100644 --- a/skype/skype-ps/skype/Get-CsOnlineSipDomain.md +++ b/teams/teams-ps/teams/Get-CsOnlineSipDomain.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinesipdomain -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinesipdomain +applicable: Microsoft Teams title: Get-CsOnlineSipDomain schema: 2.0.0 manager: bulenteg @@ -13,7 +13,7 @@ ms.reviewer: rogupta # Get-CsOnlineSipDomain ## SYNOPSIS -This cmdlet lists online sip domains and their enabled/disabled status. In a disabled domain, provisioning of users is blocked. Once a domain is re-enabled, provisioning of users in that domain will happen. +This cmdlet lists online sip domains and their enabled/disabled status. In a disabled domain, provisioning of users is blocked. Once a domain is re-enabled, provisioning of users in that domain will happen. ## SYNTAX @@ -22,7 +22,7 @@ Get-CsOnlineSipDomain [-Domain <String>] [-DomainStatus <DomainStatus>] [<Common ``` ## DESCRIPTION -This cmdlet is useful for organizations consolidating multiple on-premises deployments of Skype for Business Server into a single Office 365 tenant. During consolidation, sip domains for all forests hosting Skype for Business Server - other than the forest currently in hybrid mode - must be disabled. Once a hybrid deployment is fully migrated to the cloud and detached from Office 365, the next forest can start migration to the cloud. This cmdlet allows administrators to view the status of sip domains in their Office 365 tenant. For full details on cloud consolidation scenarios, see [Cloud consolidation for Teams and Skype for Business](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation). +This cmdlet is useful for organizations consolidating multiple on-premises deployments of Skype for Business Server into a single Office 365 tenant. During consolidation, sip domains for all forests hosting Skype for Business Server - other than the forest currently in hybrid mode - must be disabled. Once a hybrid deployment is fully migrated to the cloud and detached from Office 365, the next forest can start migration to the cloud. This cmdlet allows administrators to view the status of sip domains in their Office 365 tenant. For full details on cloud consolidation scenarios, see [Cloud consolidation for Teams and Skype for Business](https://learn.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation). ## EXAMPLES @@ -49,7 +49,7 @@ A specific domain to get the status of. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named Default value: None @@ -65,7 +65,7 @@ Type: DomainStatus Parameter Sets: (All) Aliases: Accepted values: All, Enabled, Disabled -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named Default value: None @@ -74,8 +74,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -89,8 +88,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[Disable-CsOnlineSipDomain](Disable-CsOnlineSipDomain.md) +[Disable-CsOnlineSipDomain](https://learn.microsoft.com/powershell/module/teams/disable-csonlinesipdomain) -[Enable-CsOnlineSipDomain](Enable-CsOnlineSipDomain.md) +[Enable-CsOnlineSipDomain](https://learn.microsoft.com/powershell/module/teams/enable-csonlinesipdomain) -[Cloud consolidation for Teams and Skype for Business](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation) +[Cloud consolidation for Teams and Skype for Business](https://learn.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation) diff --git a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumber.md b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumber.md similarity index 75% rename from skype/skype-ps/skype/Get-CsOnlineTelephoneNumber.md rename to teams/teams-ps/teams/Get-CsOnlineTelephoneNumber.md index 830530b918..0fced81daf 100644 --- a/skype/skype-ps/skype/Get-CsOnlineTelephoneNumber.md +++ b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumber.md @@ -1,12 +1,12 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csonlinetelephonenumber -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumber +applicable: Microsoft Teams title: Get-CsOnlineTelephoneNumber schema: 2.0.0 manager: bulenteg -author: tomkau -ms.author: tomkau +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -15,15 +15,33 @@ ms.reviewer: ## SYNOPSIS Use the `Get-CsOnlineTelephoneNumber` to retrieve telephone numbers from the Business Voice Directory. +**Note**: This cmdlet has been deprecated. Use the new [Get-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/get-csphonenumberassignment) cmdlet instead. For Microsoft 365 GCC High and DoD cloud instances use the new [Get-CshybridTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/get-cshybridtelephonenumber) cmdlet instead. + ## SYNTAX ``` -Get-CsOnlineTelephoneNumber [-ActivationState <String>] [-Assigned <MultiValuedProperty>] [-CapitalOrMajorCity <String>] [-DomainController <Fqdn>] [-ExpandLocation] [-Force] [-InventoryType <MultiValuedProperty>] [-IsNotAssigned] [-ResultSize <UInt32>] [-TelephoneNumber <String>] [-TelephoneNumberGreaterThan <String>] [-TelephoneNumberLessThan <String>] [-TelephoneNumberStartsWith <String>] [-Tenant <Guid>] [-AsJob] [<CommonParameters>] +Get-CsOnlineTelephoneNumber [-ActivationState <String>] [-Assigned <MultiValuedProperty>] [-CapitalOrMajorCity <String>] [-DomainController <Fqdn>] [-ExpandLocation] [-Force] [-InventoryType <MultiValuedProperty>] [-IsNotAssigned] [-ResultSize <UInt32>] [-TelephoneNumber <String>] [-TelephoneNumberGreaterThan <String>] [-TelephoneNumberLessThan <String>] [-TelephoneNumberStartsWith <String>] [-Tenant <Guid>] [<CommonParameters>] ``` ## DESCRIPTION -Here is an example of the output of the `Get-CsOnlineTelephoneNumber` cmdlet. +Use the `Get-CsOnlineTelephoneNumber` to retrieve telephone numbers from the Business Voice Directory. +Note: By default the result size is limited to 500 items, specify a higher result size using ResultSize parameter. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsOnlineTelephoneNumber -TelephoneNumber 19294450177 +``` +This example gets the attributes of a specific phone number. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Get-CsOnlineTelephoneNumber -CapitalOrMajorCity NOAM-US-NY-NY +``` + +```output RunspaceId : f90303a9-c6a8-483c-b3b3-a5b8cdbab19c ActivationState : Activated @@ -57,20 +75,6 @@ UserId : IsManagedByServiceDesk : True PortInOrderStatus : - - -## EXAMPLES - -### -------------------------- Example 1 -------------------------- -``` -PS C:\> Get-CsOnlineTelephoneNumber -TelephoneNumber 19294450177 -``` - -This example gets the attributes of a specific phone number. - -### -------------------------- Example 2 -------------------------- -``` -PS C:\> Get-CsOnlineTelephoneNumber -CapitalOrMajorCity NOAM-US-NY-NY ``` This example gets the phone numbers with the city code designating New York, New York. @@ -83,8 +87,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -106,8 +110,8 @@ The values for the Assigned parameter are case-sensitive. ```yaml Type: MultiValuedProperty Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -126,7 +130,7 @@ The values for the CapitalOrMajorCity parameter are case-sensitive. Type: String Parameter Sets: (All) Aliases: CityCode -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -142,7 +146,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: DC -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -157,8 +161,8 @@ Displays the location parameter with its value. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -175,8 +179,8 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -189,15 +193,17 @@ Accept wildcard characters: False Specifies the target telephone number type for the cmdlet. Acceptable values are: -* "Service" for numbers assigned to conferencing support. +* "Service" for numbers assigned to conferencing support, call queue or auto attendant. * "Subscriber" for numbers supporting public switched telephone network (PSTN) functions. +The values for the InventoryType parameter are case-sensitive. + ```yaml Type: MultiValuedProperty Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -212,8 +218,8 @@ Specifying this switch parameter will return only telephone numbers which are no ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -230,8 +236,8 @@ If set to 0, the command will run, but no data will be returned. ```yaml Type: UInt32 Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -242,15 +248,15 @@ Accept wildcard characters: False ### -TelephoneNumber Specifies the target telephone number. -For example: +For example: `-TelephoneNumber tel:+18005551234, or -TelephoneNumber +14251234567` ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -267,8 +273,8 @@ The telephone number should be in E.164 format. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -285,8 +291,8 @@ The telephone number should be in E.164 format. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -304,8 +310,8 @@ You can use up to nine digits. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -320,28 +326,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -351,7 +337,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -365,4 +351,4 @@ An instance or array of the objects. ## NOTES ## RELATED LINKS -[Remove-CsOnlineTelephoneNumber](https://docs.microsoft.com/powershell/module/skype/remove-csonlinetelephonenumber?view=skype-ps) +[Remove-CsOnlineTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/remove-csonlinetelephonenumber) diff --git a/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberCountry.md b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberCountry.md new file mode 100644 index 0000000000..e2731e0eed --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberCountry.md @@ -0,0 +1,69 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry +Module Name: MicrosoftTeams +title: Get-CsOnlineTelephoneNumberCountry +schema: 2.0.0 +manager: mreddy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: julienp +--- + +# Get-CsOnlineTelephoneNumberCountry + +## SYNOPSIS +Use the `Get-CsOnlineTelephoneNumberCountry` cmdlet to get the list of supported countries or regions to search and acquire new telephone numbers. The telephone numbers can then be used to set up calling features for users and services in your organization. + +## SYNTAX + +``` +PS C:\> Get-CsOnlineTelephoneNumberCountry [<CommonParameters>] +``` +## DESCRIPTION + +Use the `Get-CsOnlineTelephoneNumberCountry` cmdlet to get the list of supported countries or regions to search and acquire new telephone numbers. The telephone numbers can then be used to set up calling features for users and services in your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineTelephoneNumberCountry +``` + +```output +Name Value +---- ----- +Antigua and Barbuda AG +Argentina AR +Australia AU +Austria AT +... +United Kingdom GB +United States US +Uruguay UY +Venezuela VE +Vietnam VN +``` + +This example returns the list of supported countries or regions for the cmdlet search and acquire of new telephone numbers. + +## 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsOnlineTelephoneNumberCountry](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry) +[Get-CsOnlineTelephoneNumberType](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry) + +[New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) +[Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) +[Complete-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) +[Clear-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) diff --git a/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberOrder.md b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberOrder.md new file mode 100644 index 0000000000..5725171ad6 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberOrder.md @@ -0,0 +1,215 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder +Module Name: MicrosoftTeams +title: Get-CsOnlineTelephoneNumberOrder +schema: 2.0.0 +manager: mreddy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: julienp +--- + +# Get-CsOnlineTelephoneNumberOrder + +## SYNOPSIS +Use the `Get-CsOnlineTelephoneNumberOrder` cmdlet to get the order report of a specific telephone number order. + +## SYNTAX + +``` +Get-CsOnlineTelephoneNumberOrder -OrderId <String> [-OrderType <String>] + [<CommonParameters>] +``` + +## DESCRIPTION + +This `Get-CsOnlineTelephoneNumberOrder` cmdlet can be used to get the status of specific telephone number orders. Currently supported orders for retrievals are: Search [New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder), Direct Routing Number Upload [New-CsOnlineDirectRoutingTelephoneNumberUploadOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinedirectroutingtelephonenumberuploadorder), and Direct Routing Number Release [New-CsOnlineTelephoneNumberReleaseOrder](https://learn.microsoft.com/powershell/module/teams/New-csonlinetelephonenumberreleaseorder). When the OrderType is not indicated, the cmdlet will default to a Search order. + +## EXAMPLES + +### Example 1 +``` +PS C:\> $order = Get-CsOnlineTelephoneNumberOrder -OrderType Search -OrderId 1fd52b3b-b804-4ac4-a84d-4d70b51dd4be + +Key Value +--- ----- +Id 1fd52b3b-b804-4ac4-a84d-4d70b51dd4be +Name Postal Code Search Test +CreatedAt 2024-11-30T00:34:00.0825627+00:00 +CreatedBy ContosoAdmin +Description Postal Code Search Test +NumberType UserSubscriber +SearchType PostalCode +AreaCode 778 +PostalOrZipCode V7Y 1G5 +Quantity 2 +Status Reserved +IsManual False +TelephoneNumbers {System.Collections.Generic.Dictionary`2[System.String,System.Object], System.Collections.Generic.Dictionary`2[System.String,System.Object]} +ReservationExpiryDate 2024-11-30T00:50:01.1794152+00:00 +ErrorCode NoError +InventoryType Subscriber +SendToServiceDesk False +CountryCode CA + +PS C:\> $order.TelephoneNumbers + +Key Value +--- ----- +Location Vancouver +TelephoneNumber +16046606034 +Location Vancouver +TelephoneNumber +16046606030 +``` + +This example returns a successful telephone number search and the telephone numbers are reserved for purchase. + +### Example 2 +``` +PS C:\> $order = Get-CsOnlineTelephoneNumberOrder -OrderType Search -OrderId 8d23e073-bc98-4f73-8e05-7517655d7042 + +Key Value +--- ----- +Id 8d23e073-bc98-4f73-8e05-7517655d7042 +Name Postal Code Search Test +CreatedAt 2024-11-30T00:34:00.0825627+00:00 +CreatedBy ContosoAdmin +Description Prefix Search Test +NumberType UserSubscriber +SearchType Prefix +AreaCode +PostalOrZipCode +Quantity 1 +Status Error +IsManual False +TelephoneNumbers {} +ReservationExpiryDate +ErrorCode OutOfStock +InventoryType Subscriber +SendToServiceDesk False +CountryCode +``` + +This example returns a failed telephone number search and the `ErrorCode` is showing that telephone numbers with `NumberPrefix: 1425` is `OutOfStock`. + +### Example 3 +```powershell +PS C:\> Get-CsOnlineTelephoneNumberOrder -OrderId 1fd52b3b-b804-4ac4-a84d-4d70b51dd4be + +Key Value +--- ----- +Id 1fd52b3b-b804-4ac4-a84d-4d70b51dd4be +Name Postal Code Search Test +CreatedAt 2024-11-30T00:34:00.0825627+00:00 +CreatedBy TNM +Description Postal Code Search Test from Postman +NumberType UserSubscriber +SearchType PostalCode +AreaCode 778 +PostalOrZipCode V7Y 1G5 +Quantity 2 +Status Expired +IsManual False +TelephoneNumbers {System.Collections.Generic.Dictionary`2[System.String,System.Object], System.Collections.Generic.Dictionary`2[System.String,System.Object]} +ReservationExpiryDate 2024-11-30T00:50:01.1794152+00:00 +ErrorCode NoError +InventoryType Subscriber +SendToServiceDesk False +CountryCode CA +``` + +When the OrderType is not indicated, the cmdlet will default to a Search order. This example returns a successful telephone number search and the telephone numbers are reserved for purchase. + +### Example 4 +```powershell +PS C:\> Get-CsOnlineTelephoneNumberOrder -OrderType Release -OrderId 6aa4f786-8628-4923-9df1-896f3d84016c + +Key Value +--- ----- +OrderId 6aa4f786-8628-4923-9df1-896f3d84016c +CreatedAt 2024-11-27T06:44:26.1975766+00:00 +Status Complete +TotalCount 3 +SuccessCount 3 +FailureCount 0 +SuccessPhoneNumbers {+12063866355, +12063868075, +12063861642} +FailedPhoneNumbers {} +``` + +This example returns the status of a successful release order for Direct Routing telephone numbers. + +### Example 5 +```powershell +PS C:\> Get-CsOnlineTelephoneNumberOrder -OrderType DirectRoutingNumberCreation -OrderId faef09f7-5bd5-4740-9e76-9a5762380f34 + +Key Value +--- ----- +OrderId faef09f7-5bd5-4740-9e76-9a5762380f34 +CreatedAt 2024-11-30T00:22:59.4989508+00:00 +Status Success +TotalCount 1 +SuccessCount 1 +FailureCount 0 +WarningCount 0 +FailedPhoneNumbers {} +WarningPhoneNumbers {} +SuccessPhoneNumbers {+99999980} +``` + +This example returns the status of a successful upload order for a Direct Routing phone number. + +## PARAMETERS + +### -OrderId +Use the OrderId received as output of your order creation cmdlets. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OrderType +Specifies the type of telephone number order to look up. Currently supported values are **Search**, **Release**, and **DirectRoutingNumberCreation**. If this value is unspecified, then it will default to a **Search** order. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +Updates in Teams PowerShell Module version 6.7.1 and later: +- A new optional parameter `OrderType` is introduced. If no OrderType is provided, it will default to a Search order. +- [BREAKING CHANGE] When a Search order is queried, the property name `TelephoneNumber` in the output will be changed to `TelephoneNumbers`. The structure of the `TelephoneNumbers` output will remain unchanged. + - Impact: Scripts and processes that reference the `TelephoneNumber` property will need to be updated to use `TelephoneNumbers`. + +## RELATED LINKS +[Get-CsOnlineTelephoneNumberCountry](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry) +[Get-CsOnlineTelephoneNumberType](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbertype) +[New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) +[Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) +[Complete-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/complete-csonlinetelephonenumberorder) +[Clear-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/clear-csonlinetelephonenumberorder) +[New-CsOnlineDirectRoutingTelephoneNumberUploadOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinedirectroutingtelephonenumberuploadorder) +[New-CsOnlineTelephoneNumberReleaseOrder](https://learn.microsoft.com/powershell/module/teams/New-csonlinetelephonenumberreleaseorder) diff --git a/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberType.md b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberType.md new file mode 100644 index 0000000000..47c397e14b --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineTelephoneNumberType.md @@ -0,0 +1,110 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbertype +Module Name: MicrosoftTeams +title: Get-CsOnlineTelephoneNumberType +schema: 2.0.0 +manager: mreddy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: julienp +--- + +# Get-CsOnlineTelephoneNumberType + +## SYNOPSIS +Use the `Get-CsOnlineTelephoneNumberType` cmdlet to get the list of supported telephone number offerings in a given country or region. The telephone numbers can then be used to set up calling features for users and services in your organization. + +## SYNTAX + +``` +Get-CsOnlineTelephoneNumberType [-Country] <CountryCode> [<CommonParameters>] +``` + +## DESCRIPTION + +Use the `Get-CsOnlineTelephoneNumberType` cmdlet to get the list of supported telephone number offerings in a given country or region. The `NumberType` field in the response is used to indicate the capabilities of a given offering. The telephone numbers can then be used to set up calling features for users and services in your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsOnlineTelephoneNumberType -Country US +``` + +```output +AllowedSearchType : {CivicAddress, Prefix} +AreaCode : +AvailabilityInfo : Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.AvailabilityInfo +Id : 470316bd-815e-459d-80e7-d7332f00fcb9 +NumberType : UserSubscriber +OfferModel : DirectStock +PrefixSearchOption : Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.PrefixSearchOptions +RequiresCivicAddress : True + +AllowedSearchType : {CivicAddress, Prefix} +AreaCode : +AvailabilityInfo : Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.AvailabilityInfo +Id : 25444938-a335-4a85-b64d-d445b45f04e3 +NumberType : UserSubscriberVoiceAndSms +OfferModel : DirectStock +PrefixSearchOption : Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.PrefixSearchOptions +RequiresCivicAddress : True +``` + +This example returns the list of supported number offerings in United States. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Get-CsOnlineTelephoneNumberType -Country CA | ft NumberType +``` + +```output +NumberType +---------- +UserSubscriber +UserSubscriberVoiceAndSms +ConferenceToll +ConferenceTollFree +CallQueueToll +CallQueueTollFree +AutoAttendantToll +AutoAttendantTollFree +``` +This example returns the list of supported NumberTypes in Canada. + +## PARAMETERS + +### Country +Specifies the country or region that the number offerings belong. The country code uses ISO 3166 standard and the list of supported countries or regions can be found by calling `Get-CsOnlineTelephoneNumberCountry`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineTelephoneNumberCountry](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry) +[Get-CsOnlineTelephoneNumberType](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbertype) + +[New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) +[Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) +[Complete-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/complete-csonlinetelephonenumberorder) +[Clear-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/clear-csonlinetelephonenumberorder) diff --git a/teams/teams-ps/teams/Get-CsOnlineUser.md b/teams/teams-ps/teams/Get-CsOnlineUser.md new file mode 100644 index 0000000000..73ccb9f1c7 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineUser.md @@ -0,0 +1,591 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlineuser +applicable: Microsoft Teams +title: Get-CsOnlineUser +schema: 2.0.0 +manager: sshastri +author: praspatil +ms.author: praspatil +ms.reviewer: +--- + +# Get-CsOnlineUser + +## SYNOPSIS +Returns information about users who have accounts homed on Microsoft Teams or Skype for Business Online. + +## SYNTAX + +``` +Get-CsOnlineUser [[-Identity] <UserIdParameter>] + [-AccountType <String>] + [-Filter <String>] + [-Properties <String>] + [-ResultSize <Unlimited>] + [-SkipUserPolicies] + [-SoftDeletedUser] + [-Sort] + [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsOnlineUser cmdlet returns information about users who have accounts homed on Microsoft Teams +The returned information includes standard Active Directory account information (such as the department the user works in, his or her address and phone number, etc.): the Get-CsOnlineUser cmdlet returns information about such things as whether or not the user has been enabled for Enterprise Voice and which per-user policies (if any) have been assigned to the user. + +Note that the Get-CsOnlineUser cmdlet does not have a TenantId parameter; that means you cannot use a command similar to this in order to limit the returned data to users who have accounts with a specific Microsoft Teams or Skype for Business Online tenant: + +`Get-CsOnlineUser -TenantId "bf19b7db-6960-41e5-a139-2aa373474354"` + +However, if you have multiple tenants you can return users from a specified tenant by using the Filter parameter and a command similar to this: + +`Get-CsOnlineUser -Filter "TenantId -eq 'bf19b7db-6960-41e5-a139-2aa373474354'"` + +That command will limit the returned data to user accounts belong to the tenant with the TenantId "bf19b7db-6960-41e5-a139-2aa373474354". +If you do not know your tenant IDs you can return that information by using this command: + +`Get-CsTenant` + +If you have a hybrid or "split domain" deployment (that is, a deployment in which some users have accounts homed on Skype for Business Online while other users have accounts homed on an on-premises version of Skype for Business Server 2015) keep in mind that the Get-CsOnlineUser cmdlet only returns information for Skype for Business Online users. +However, the cmdlet will return information for both online users and on-premises users. +If you want to exclude Skype for Business Online users from the data returned by the Get-CsUser cmdlet, use the following command: + +`Get-CsUser -Filter "TenantId -eq '00000000-0000-0000-0000-000000000000'"` + +By definition, users homed on the on-premises version will always have a TenantId equal to 00000000-0000-0000-0000-000000000000. +Users homed on Skype for Business Online will a TenantId that is equal to some value other than 00000000-0000-0000-0000-000000000000. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineUser +``` + +The command shown in Example 1 returns information for all the users configured as online users. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsOnlineUser -Identity "sip:kenmyer@litwareinc.com" +``` + +In Example 2 information is returned for a single online user: the user with the SIP address "sip:kenmyer@litwareinc.com". + +### -------------------------- Example 3 -------------------------- +``` +Get-CsOnlineUser -Filter "ArchivingPolicy -eq 'RedmondArchiving'" +``` + +Example 3 uses the Filter parameter to limit the returned data to online users who have been assigned the per-user archiving policy RedmondArchiving. + +To do this, the filter value {ArchivingPolicy -eq "RedmondArchiving"} is employed; that syntax limits returned data to users where the ArchivingPolicy property is equal to (-eq) "RedmondArchiving". + +### -------------------------- Example 4 -------------------------- +``` +Get-CsOnlineUser -Filter {HideFromAddressLists -eq $True} +``` + +Example 4 returns information only for user accounts that have been configured so that the account does not appear in Microsoft Exchange address lists. + +(That is, the Active Directory attribute msExchHideFromAddressLists is True.) To carry out this task, the Filter parameter is included along with the filter value {HideFromAddressLists -eq $True}. + +### -------------------------- Example 5 -------------------------- +``` +Get-CsOnlineUser -Filter {LineURI -eq "tel:+1234"} +Get-CsOnlineUser -Filter {LineURI -eq "tel:+1234,ext:"} +Get-CsOnlineUser -Filter {LineURI -eq "1234"} +``` + +Example 5 returns information for user accounts that have been assigned a designated phone number. + +### -------------------------- Example 6 -------------------------- +``` +Get-CsOnlineUser -AccountType ResourceAccount +``` + +Example 6 returns information for user accounts that are categorized as resource accounts. + +### -------------------------- Example 7 -------------------------- +``` +Get-CsOnlineUser -Filter "FeatureTypes -Contains 'PhoneSystem'" +``` + +Example 7 returns information for user's assigned plans. + +## PARAMETERS + +### -AccountType +This parameter is added to Get-CsOnlineUser starting from TPM 4.5.1 to indicate the user type. The possible values for the AccountType parameter are: + +- `User` - to query for user accounts. +- `ResourceAccount` - to query for app endpoints or resource accounts. +- `Guest` - to query for guest accounts. +- `SfBOnPremUser` - to query for users that are hosted on-premises +- `IneligibleUser` - to query for a user that does not have valid Teams license (except Guest, ResourceAccount and SfbOnPremUser). + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account to be retrieved. + +For TeamsOnly customers using the Teams PowerShell Module version 3.0.0 or later, you use the following values to identify the account: + +- GUID +- SIP address +- UPN +- Alias + +Using the Teams PowerShell Module version 2.6 or earlier only, you can use the following values to identify the account: + +- GUID +- SIP address +- UPN +- Alias +- Display name. Supports the asterisk ( \* ) wildcard character. For example, `-Identity "* Smith"` returns all the users whose display names end with Smith. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to limit the returned data by filtering on specific attributes. For example, you can limit returned data to users who have been assigned a specific voice policy, or users who have not been assigned a specific voice policy. + +The Filter parameter uses the same filtering syntax as the Where-Object cmdlet. For example, the following filter returns only users who have been enabled for Enterprise Voice: `-Filter 'EnterpriseVoiceEnabled -eq $True'` or ``-Filter "EnterpriseVoiceEnabled -eq `$True"``. + +Examples: +- Get-CsOnlineUser -Filter {AssignedPlan -like "*MCO*"} +- Get-CsOnlineUser -Filter {UserPrincipalName -like "test*" -and (AssignedPlans -eq "MCOEV" -or AssignedPlans -like "MCOPSTN*")} +- Get-CsOnlineUser -Filter {OnPremHostingProvider -ne $null} +- Get-CsOnlineUser -Filter {WhenChanged -gt "1/25/2022 11:59:59 PM"} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Properties + +Allows you to specify the properties you want to include in the output. Provide the properties as a comma-separated list. Identity, UserPrincipalName, Alias, AccountEnabled and DisplayName attributes will always be present in the output. Please note that only attributes available in the output of the Get-CsOnlineUser cmdlet can be selected. For a complete list of available attributes, refer to the response of the Get-CsOnlineUser cmdlet. + +Examples: +- Get-CsOnlineUser -Properties DisplayName, UserPrincipalName, FeatureTypes +- Get-CsOnlineUser -Properties DisplayName, Alias, LineURI + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize + +**Note**: Starting with Teams PowerShell Modules version 4.0 and later, "-ResultSize" type has been changed to uint32. + +Enables you to limit the number of records returned by the cmdlet. For example, to return seven users (regardless of the number of users that are in your forest) include the ResultSize parameter and set the parameter value to 7. Note that there is no way to guarantee which seven users will be returned. + +The result size can be set to any whole number between 0 and 2147483647, inclusive. The value 0 returns no data. If you set the ResultSize to 7 but you have only three users in your forest, the command will return those three users, and then complete without error. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SkipUserPolicies +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SoftDeletedUser + +This parameter enables you to return a collection of all the users who are deleted and can be restored within 30 days from their deletion time + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Sort + +Sorting is now enabled in Teams PowerShell Module by using the "-Sort" or "-OrderBy" parameters. For example: + +- Get-CsOnlineUser -Filter {LineURI -like *123*} -OrderBy "DisplayName asc" +- Get-CsOnlineUser -Filter {DisplayName -like '*abc'} -OrderBy {DisplayName desc} + +**Note**: Sorting on few attributes like LineURI can be case-sensitive. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: OrderBy +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +A recent fix has addressed an issue where some Guest users were being omitted from the output of the Get-CsOnlineUser cmdlet, resulting in an increase in the reported user count. + +**Commonly used FeatureTypes and their descriptions:** + +- Teams: Enables Users to access Teams +- AudioConferencing': Enables users to call-in to Teams meetings from their phones +- PhoneSystem: Enables users to place, receive, transfer, mute, unmute calls in Teams with mobile device, PC, or IP Phones +- CallingPlan: Enables an All-in-the-cloud voice solution for Teams users that connects Teams Phone System to the PSTN to enable external calling. With this option, Microsoft acts as the PSTN carrier. +- TeamsMultiGeo: Enables Teams chat data to be stored at rest in a specified geo location +- VoiceApp: Enables to set up resource accounts to support voice applications like Auto Attendants and Call Queues +- M365CopilotTeams: Enables Copilot in Teams +- TeamsProMgmt: Enables enhanced meeting recap features like AI generated notes and tasks from meetings, view when a screen was shared etc +- TeamsProProtection: Enables additional ways to safeguard and monitor users' Teams experiences with features like Sensitivity labels, Watermarking, end-to-end encryption etc. +- TeamsProWebinar: Enables advances webinar features like engagement reports, RTMP-In, Webinar Wait List, in Teams. +- TeamsProCust: Enables meeting customization features like branded meetings, together mode, in Teams. +- TeamsProVirtualAppt: Enables advances virtual appointment features like SMS notifications, custom waiting room, in Teams. +- TeamsRoomPro: Enables premium in-room meeting experience like intelligent audio, large galleries in Teams. +- TeamsRoomBasic: Enables core meeting experience with Teams Rooms Systems. +- TeamsAdvComms: Enables advances communication management like custom communication policies in Teams. +- TeamsMobileExperience: Enables users to use a single phone number in Teams across both sim-enabled mobile phone and desk lines. +- Conferencing_RequiresCommunicationCredits: Allows pay-per minute Audio Conferencing without monthly licenses. +- CommunicationCredits: Enables users to pay Teams calling and conferencing through the credits. + +**Updates in Teams PowerShell Module verion 7.1.1 Preview and later**: + +- EffectivePolicyAssignments: The EffectivePolicyAssignments attribute has been added to the Get-CsOnlineUser cmdlet in commercial environments. This new attribute provides information about a user's effective policy assignments. Each assignment includes the following details: + - PolicyType - which specifies the type of policy assigned (for example, TeamsMeetingPolicy, TeamsCallingPolicy, and so on.) + - PolicyAssignment - which includes the display name of the assigned policy (displayName), the assignment type (assignmentType) indicating whether it is direct or group-based, the unique identifier of the policy (policyId), and the group identifier (groupId) if applicable. + **Note**: The policyId property isn't currently supported. + +**Updates in Teams PowerShell Module**: + +- DialPlan: DialPlan attribute will be deprecated and no longer populated in the output of Get-CsOnlineUser in all clouds. + +**Updates in Teams PowerShell Module version 7.0.0 and later**: + +- OptionFlags: OptionFlags attribute will no longer be populated with value in the output of Get-CsOnlineUser in all clouds. It's important to note that other details besides EnterpriseVoiceEnabled, previously found in OptionFlags, are no longer relevant for Teams. Administrators can still utilize the EnterpriseVoiceEnabled attribute in the output of the Get-CsOnlineUser cmdlet to get this information. This change will be rolled out to all Teams Powershell Module versions. + +**Updates in Teams PowerShell Module version 6.9.0 and later**: + +Adds new attribute in the output of Get-CsOnlineUser cmdlet in commercial environments. + - TelephoneNumbers: A new list of complex object that includes telephone number and its corresponding assignment category. The assignment category can include values such as 'Primary', 'Private', and 'Alternate'. + +Adds new parameter to the Get-CsOnlineUser cmdlet in all clouds: + - Properties: Allows you to specify the properties you want to include in the output. Provide the properties as a comma-separated list. Note that the following properties will always be present in the output: Identity, UserPrincipalName, Alias, AccountEnabled, DisplayName. + +**Updates in Teams PowerShell Module version 6.8.0 and later**: + +New policies - TeamsBYODAndDesksPolicy, TeamsAIPolicy, TeamsWorkLocationDetectionPolicy, TeamsMediaConnectivityPolicy, TeamsMeetingTemplatePermissionPolicy, TeamsVirtualAppointmentsPolicy and TeamsWorkLoadPolicy will be visible in the Get-CsOnlineUser cmdlet output. + +The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 6.8.0 or later for Microsoft Teams operated by 21Vianet. These updates will be rolled out gradually to older Microsoft Teams PowerShell versions. + +The following attributes are populated with correct values in the output of Get-CsOnlineUser when not using the "-identity" parameter: + +- CountryAbbreviation +- UserValidationErrors +- WhenCreated + +The following updates are applicable to the output in scenarios where "-identity" parameter is not used: + +- Only valid OnPrem users would be available in the output: These are users that are DirSyncEnabled and have a valid OnPremSipAddress or SIP address in ShadowProxyAddresses. +- Guest are available in the output +- Unlicensed Users: Unlicensed users would show up in the output of Get-CsOnlineUser (note Unlicensed users in commercial clouds would show up in the output for only 30 days post-license removal.) +- Soft deleted users: These users will be displayed in the output of Get-CsOnlineUser and the TAC Manage Users page by default with SoftDeletionTimestamp set to a value. +- AccountType as Unknown will be renamed to AccountType as IneligibleUser in GCC High and DoD environments. IneligibleUser will include users who do not have any valid Teams licenses (except Guest, SfbOnPremUser, ResourceAccount). + +If any information is required for a user that is not available in the output (when not using "-identity" parameter) then it can be obtained using the "-identity" parameter. Information for all users would be available using the "-identity" parameter until they are hard deleted. + +If Guest, Soft Deleted Users, IneligibleUser are not required in the output then they can be filtered out by using filter on AccountType and SoftDeletionTimestamp. For example: + +- Get-CsOnlineUser -Filter {AccountType -ne 'Guest'} +- Get-CsOnlineUser -Filter {SoftDeletionTimestamp -eq $null} +- Get-CsOnlineUser -Filter {AccountType -ne 'IneligibleUser'} + +**Updates in Teams PowerShell Module version 6.1.1 Preview and later**: + +The following updates are applicable for organizations that use Microsoft Teams PowerShell version 6.1.1 (Targeted Release: April 15th, 2024) or later. These changes will be gradually rolled out for all tenants starting from April 26th, 2024. + +When using the Get-CsOnlineUser cmdlet in Teams PowerShell Module without the -identity parameter, we are introducing these updates: + +- Before the rollout, unlicensed users who did not have a valid Teams license were displayed in the output of the Get-CsOnlineUser cmdlet for 30 days after license removal. After the rollout, Get-CsOnlineUser will show unlicensed users after the initial 30 days and also include unlicensed users who never had a valid Teams license. +- The AccountType value Unknown is being renamed to IneligibleUser, and will include users who do not have a valid Teams license (exceptions: Guest, SfbOnPremUser, and ResourceAccount). +- You can exclude users with the AccountType as IneligibleUser from the output with the AccountType filter. For example, Get-CsOnlineUser -Filter {AccountType -ne 'IneligibleUser'} + +When Get-CsOnlineUser is used with the -identity parameter, you can also use UPN, Alias, and SIP Address with the -identity parameter to obtain the information for a specific unlicensed user. + +**Updates in Teams PowerShell Module version 6.1.0 and later**: + +The following updates are applicable for organizations that use Microsoft Teams PowerShell version 6.1.0 or later. + +- LocationPolicy: LocationPolicy attribute is being deprecated from the output of Get-CsOnlineUser in all clouds. Get-CsPhoneNumberAssignment -IsoCountryCode can be used to get the LocationPolicy information. (Note: LocationPolicy attribute will no longer be populated with value in the older Teams Powershell Module versions (<6.1.0) starting from 20th March 2024.) + +**Updates in Teams PowerShell Module version 6.0.0 and later**: + +The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 6.0.0 or later. + +- GracePeriodExpiryDate: GracePeriodExpiryDate attribute is being introduced within the AssignedPlan JSON array. It specifies the date when the grace period of a previously deleted license expires, and the license will be permanently deleted. The attribute remains empty/null for active licenses. (Note: The attribute is currently in private preview and will display valid values only for private preview) + +- IsInGracePeriod: IsInGracePeriod attribute is a boolean flag that indicates that the associated plan is in grace period after deletion. (Note: The attribute is currently in private preview and will display valid values only for private preview) + +**Updates in Teams PowerShell Module version 5.9.0 and later**: + +The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 5.9.0 or later in GCC High and DoD environments (note that these changes are already rolled out in commercial environments). These updates will be applicable to older Teams PowerShell versions from 15th March 2024 in GCC High and DoD environments: + +The following attributes are populated with correct values in the output of Get-CsOnlineUser when not using the "-identity" parameter: + +- CountryAbbreviation +- UserValidationErrors +- WhenCreated + +The following updates are applicable to the output in scenarios where "-identity" parameter is not used: + +- Only valid OnPrem users would be available in the output: These are users that are DirSyncEnabled and have a valid OnPremSipAddress or SIP address in ShadowProxyAddresses. +- Guest are available in the output +- Unlicensed Users: Unlicensed users would show up in the output of Get-CsOnlineUser (note Unlicensed users in commercial clouds would show up in the output for only 30 days post-license removal.) +- Soft deleted users: These users will be displayed in the output of Get-CsOnlineUser and the TAC Manage Users page by default with SoftDeletionTimestamp set to a value. +- AccountType as Unknown will be renamed to AccountType as IneligibleUser in GCC High and DoD environments. IneligibleUser will include users who do not have any valid Teams licenses (except Guest, SfbOnPremUser, ResourceAccount). + +If any information is required for a user that is not available in the output (when not using "-identity" parameter) then it can be obtained using the "-identity" parameter. Information for all users would be available using the "-identity" parameter until they are hard deleted. + +If Guest, Soft Deleted Users, IneligibleUser are not required in the output then they can be filtered out by using filter on AccountType and SoftDeletionTimestamp. For example: + +- Get-CsOnlineUser -Filter {AccountType -ne 'Guest'} +- Get-CsOnlineUser -Filter {SoftDeletionTimestamp -eq $null} +- Get-CsOnlineUser -Filter {AccountType -ne 'IneligibleUser'} + +**Updates in Teams PowerShell Module version 3.0.0 and above**: + +The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 3.0.0 and later, excluding updates mentioned previously for Teams PowerShell Module version 5.0.0: + +_New user attributes_: + +FeatureTypes: Array of unique strings specifying what features are enabled for a user. This attribute is an alternative to several attributes that have been dropped as outlined in the next section. + +Some of the commonly used FeatureTypes include: + +- Teams +- AudioConferencing +- PhoneSystem +- CallingPlan + +**Note**: This attribute is now filterable in Teams PowerShell Module versions 4.0.0 and later using the "-Contains" operator as shown in Example 7. + +AccountEnabled: Indicates whether a user is enabled for login in Microsoft Entra ID. + +_Dropped attributes_: + +The following attributes are no longer relevant to Teams and have been dropped from the output: + +- AcpInfo +- AdminDescription +- ArchivingPolicy +- AudioVideoDisabled +- BaseSimpleUrl +- BroadcastMeetingPolicy +- CallViaWorkPolicy +- ClientPolicy +- ClientUpdateOverridePolicy +- ClientVersionPolicy +- CloudMeetingOpsPolicy +- CloudMeetingPolicy +- CloudVideoInteropPolicy +- ContactOptionFlags +- CountryOrRegionDisplayName +- Description +- DistinguishedName +- EnabledForRichPresence +- ExchangeArchivingPolicy +- ExchUserHoldPolicies +- ExperiencePolicy +- ExternalUserCommunicationPolicy +- ExUmEnabled +- Guid +- HomeServer +- HostedVoicemailPolicy +- IPPBXSoftPhoneRoutingEnabled +- IPPhone +- IPPhonePolicy +- IsByPassValidation +- IsValid +- LegalInterceptPolicy +- LicenseRemovalTimestamp +- LineServerURI +- Manager +- MNCReady +- Name +- NonPrimaryResource +- ObjectCategory +- ObjectClass +- ObjectState +- OnPremHideFromAddressLists +- OriginalPreferredDataLocation +- OriginatingServer +- OriginatorSid +- OverridePreferredDataLocation +- PendingDeletion +- PrivateLine +- ProvisioningCounter +- ProvisioningStamp +- PublishingCounter +- PublishingStamp +- Puid +- RemoteCallControlTelephonyEnabled +- RemoteMachine +- SamAccountName +- ServiceInfo +- StsRefreshTokensValidFrom +- SubProvisioningCounter +- SubProvisioningStamp +- SubProvisionLineType +- SyncingCounter +- TargetRegistrarPool +- TargetServerIfMoving +- TeamsInteropPolicy +- ThumbnailPhoto +- UpgradeRetryCounter +- UserAccountControl +- UserProvisionType +- UserRoutingGroupId +- VoicePolicy - Alternative is the CallingPlan and PhoneSystem string in FeatureTypes +- XForestMovePolicy +- AddressBookPolicy +- GraphPolicy +- PinPolicy +- PreferredDataLocationOverwritePolicy +- PresencePolicy +- SmsServicePolicy +- TeamsVoiceRoute +- ThirdPartyVideoSystemPolicy +- UserServicesPolicy +- ConferencingPolicy +- Id +- MobilityPolicy +- OnlineDialinConferencingPolicy - Alternative is the AudioConferencing string in FeatureTypes +- Sid +- TeamsWorkLoadPolicy +- VoiceRoutingPolicy +- ClientUpdatePolicy +- HomePhone +- HostedVoiceMail +- MobilePhone +- OtherTelephone +- StreetAddress +- WebPage +- AssignedLicenses +- OnPremisesUserPrincipalName +- HostedVoiceMail +- LicenseAssignmentStates +- OnPremDomainName +- OnPremSecurityIdentifier +- OnPremSamAccountName +- CallerIdPolicy +- Fax +- LastName (available in Teams PowerShell Module 4.2.1 and later) +- Office +- Phone +- WindowsEmailAddress +- SoftDeletedUsers (available in Teams PowerShell Module 4.4.3 and later) + +The following attributes are temporarily unavailable in the output when using the "-Filter" or when used without the "-Identity" parameter: + +- WhenChanged +- CountryAbbreviation + +**Note**: These attributes will be available in the near future. + +_Attributes renamed_: + +- ObjectId renamed to Identity +- FirstName renamed to GivenName +- DirSyncEnabled renamed to UserDirSyncEnabled +- MCOValidationErrors renamed to UserValidationErrors +- Enabled renamed to IsSipEnabled +- TeamsBranchSurvivabilityPolicy renamed to TeamsSurvivableBranchAppliancePolicy +- CountryOrRegionDisplayName introduced as Country (in versions 4.2.0 and later) +- InterpretedUserType: "AADConnectEnabledOnline" prefix for the InterpretedUserType output value has now been renamed DirSyncEnabledOnline, for example, AADConnectEnabledOnlineTeamsOnlyUser is now DirSyncEnabledOnlineTeamsOnlyUser. + +_Attributes that have changed in meaning/format_: + +**OnPremLineURI**: This attribute previously used to refer to both: + +1. LineURI set via OnPrem AD. +2. Direct Routing numbers assigned to users via Set-CsUser. + +In Teams PowerShell Modules 3.0.0 and above OnPremLineURI will only refer to the LineURI set via OnPrem AD. Direct Routing numbers will be available from the LineURI field. Direct Routing Numbers can be distinguished from Calling Plan Numbers by looking at the FeatureTypes attribute. + +- **The output format of AssignedPlan and ProvisionedPlan have now changed from XML to JSON array.** +- **The output format of Policies has now changed from String to JSON type UserPolicyDefinition.** + +## RELATED LINKS + +[Set-CsUser](https://learn.microsoft.com/powershell/module/teams/set-csuser) diff --git a/teams/teams-ps/teams/Get-CsOnlineVoiceRoute.md b/teams/teams-ps/teams/Get-CsOnlineVoiceRoute.md new file mode 100644 index 0000000000..530da92267 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineVoiceRoute.md @@ -0,0 +1,117 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroute +applicable: Microsoft Teams +title: Get-CsOnlineVoiceRoute +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineVoiceRoute + +## SYNOPSIS +Returns information about the online voice routes configured for use in your tenant. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlineVoiceRoute [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlineVoiceRoute [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to retrieve one or more existing online voice routes in your tenant. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). + +This cmdlet can be used to retrieve voice route information such as which online PSTN gateways the route is associated with (if any), which online PSTN usages are associated with the route, the pattern (in the form of a regular expression) that identifies the phone numbers to which the route applies, and caller ID settings. The PSTN usage associates the voice route to an online voice policy. + +This cmdlet is used when configuring Microsoft Phone System Direct Routing. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoute +``` + +Retrieves the properties for all voice routes defined within the tenant. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoute -Identity Route1 +``` + +Retrieves the properties for the Route1 voice route. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoute -Filter *test* +``` + +This command displays voice route settings where the Identity contains the string "test" anywhere within the value. To find the string test only at the end of the Identity, use the value \*test. Similarly, to find the string test only if it occurs at the beginning of the Identity, specify the value test\*. + +### -------------------------- Example 4 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoute | Where-Object {$_.OnlinePstnGatewayList.Count -eq 0} +``` + +This command retrieves all voice routes that have not had any PSTN gateways assigned. First all voice routes are retrieved using the Get-CsOnlineVoiceRoute cmdlet. These voice routes are then piped to the Where-Object cmdlet. The Where-Object cmdlet narrows down the results of the Get operation. In this case we look at each voice route (that's what the $_ represents) and check the Count property of the PstnGatewayList property. If the count of PSTN gateways is 0, the list is empty and no gateways have been defined for the route. + +## PARAMETERS + +### -Filter +This parameter filters the results of the Get operation based on the wildcard value passed to this parameter. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A string that uniquely identifies the voice route. If no identity is provided, all voice routes for the organization are returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroute) + +[Set-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroute) + +[Remove-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroute) diff --git a/teams/teams-ps/teams/Get-CsOnlineVoiceRoutingPolicy.md b/teams/teams-ps/teams/Get-CsOnlineVoiceRoutingPolicy.md new file mode 100644 index 0000000000..1aec9c2d0a --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineVoiceRoutingPolicy.md @@ -0,0 +1,136 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroutingpolicy +applicable: Microsoft Teams +title: Get-CsOnlineVoiceRoutingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineVoiceRoutingPolicy + +## SYNOPSIS +Returns information about the online voice routing policies configured for use in your tenant. Online voice routing policies manage online PSTN usages for users of Phone System. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlineVoiceRoutingPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlineVoiceRoutingPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. + +Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoutingPolicy +``` + +The command shown in Example 1 returns information for all the online voice routing policies configured for use in the tenant. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" +``` + +In Example 2, information is returned for a single online voice routing policy: the policy with the Identity RedmondOnlineVoiceRoutingPolicy. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoutingPolicy -Filter "tag:*" +``` + +The command shown in Example 3 returns information about all the online voice routing policies configured at the per-user scope. To do this, the command uses the Filter parameter and the filter value "tag:\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "tag:". + +### -------------------------- Example 4 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -contains "Long Distance"} +``` + +In Example 4, information is returned only for those online voice routing policies that include the PSTN usage "Long Distance". To carry out this task, the command first calls `Get-CsVoiceRoutingPolicy` without any parameters; that returns a collection of all the voice routing policies configured for use in the organization. This collection is then piped to the Where-Object cmdlet, which picks out only those policies where the OnlinePstnUsages property includes (-contains) the usage "Long Distance". + +### -------------------------- Example 5 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -notcontains "Long Distance"} +``` + +Example 5 is a variation on the command shown in Example 4; in this case, however, information is returned only for those online voice routing policies that do not include the PSTN usage "Long Distance". In order to do that, the Where-Object cmdlet uses the -notcontains operator, which limits returned data to policies that do not include the usage "Long Distance". + +## PARAMETERS + +### -Filter +Enables you to use wildcards when retrieving one or more online voice routing policies. For example, to return all the policies configured at the per-user scope, use this syntax: + +-Filter "tag:\*" + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier of the online voice routing policy to be retrieved. To return the global policy, use this syntax: + +-Identity global + +To return a policy configured at the per-user scope, use syntax like this: + +-Identity "RedmondOnlineVoiceRoutingPolicy" + +You cannot use wildcard characters when specifying the Identity. + +If neither the Identity nor the Filter parameters are specified, then `Get-CsOnlineVoiceRoutingPolicy` returns all the voice routing policies configured for use in the tenant. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroutingpolicy) + +[Set-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroutingpolicy) + +[Grant-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoiceroutingpolicy) + +[Remove-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroutingpolicy) diff --git a/teams/teams-ps/teams/Get-CsOnlineVoiceUser.md b/teams/teams-ps/teams/Get-CsOnlineVoiceUser.md new file mode 100644 index 0000000000..71f7ff2efb --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineVoiceUser.md @@ -0,0 +1,396 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceuser +applicable: Microsoft Teams +title: Get-CsOnlineVoiceUser +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineVoiceUser + +## SYNOPSIS +Use the `Get-CsOnlineVoiceUser` cmdlet to retrieve a voice user's telephone number and location. + +## SYNTAX + +``` +Get-CsOnlineVoiceUser [-CivicAddressId <XdsCivicAddressId>] [-DomainController <Fqdn>] [-EnterpriseVoiceStatus <MultiValuedProperty>] [-ExpandLocation] [-First <Unlimited>] [-Force] [-GetFromAAD] [-GetPendingUsers] [-Identity <UserIdParameter>] [-LocationId <LocationID>] [-NumberAssigned] [-NumberNotAssigned] [-PSTNConnectivity <MultiValuedProperty>] [-SearchQuery <String>] [-Skip <Unlimited>] [-Tenant <Guid>] + [<CommonParameters>] +``` + +## DESCRIPTION + +**Note**: This cmdlet **is no longer supported** on the public and GCC cloud instances. You should use the replacement cmdlets described here. + +The following table lists the parameters to `Get-CsOnlineVoiceUser` and the alternative method of getting the same data using a combination of `Get-CsOnlineUser`, `Get-CsPhoneNumberAssignment`, `Get-CsOnlineLisLocation`, and `Get-CsOnlineLisCivicAddress`. + +| Parameter | Description | Alternative | +| :------------| :------- | :------- | +| No parameters | Get information for all users | `Get-CsOnlineUser -Filter {(FeatureTypes -contains 'PhoneSystem') -and (AccountEnabled -eq $True)} -AccountType User` | +| CivicAddressId | Find phone number information where the assigned phone number is associated with the CivicAddressId | `Get-CsPhoneNumberAssignment -CivicAddressId <CivicAddressId>` | +| EnterpriseVoiceStatus | Find enabled users based on EnterpriseVoiceEnabled | `Get-CsOnlineUser -Filter {(EnterpriseVoiceEnabled -eq $True) -and (FeatureTypes -contains 'PhoneSystem') -and (AccountEnabled -eq $True)} -AccountType User` or `Get-CsOnlineUser -Filter {(EnterpriseVoiceEnabled -eq $False) -and (FeatureTypes -contains 'PhoneSystem') -and (AccountEnabled -eq $True)} -AccountType User` | +| ExpandLocation | Show information about the LocationId | `Get-CsOnlineLisLocation -LocationId <LocationId>` | +| Identity | Get information for a user | `Get-CsOnlineUser -Identity <Identity>` | +| LocationId | Find phone number information where the assigned phone number is associated with the LocationId | `Get-CsPhoneNumberAssignment -LocationId <LocationId>` | +| NumberAssigned | Find enabled users with a phone number assigned | `Get-CsOnlineUser -Filter {(LineUri -ne $Null) -and (FeatureTypes -contains 'PhoneSystem') -and (AccountEnabled -eq $True)} -AccountType User` | +| NumberNotAssigned | Find users without a phone number assigned | `Get-CsOnlineUser -Filter {(LineUri -eq $Null) -and (FeatureTypes -contains 'PhoneSystem') -and (AccountEnabled -eq $True)} -AccountType User` | +| PSTNConnectivity | Find enabled users with PhoneSystem (OnPremises) or CallingPlan (Online) | Online: `Get-CsOnlineUser -Filter {(FeatureTypes -contains 'CallingPlan') -and (AccountEnabled -eq $True)} -AccountType User` OnPremises: `Get-CsOnlineUser -Filter {-not (FeatureTypes -contains 'CallingPlan') -and (FeatureTypes -contains 'PhoneSystem') -and (AccountEnabled -eq $True)} -AccountType User` | + +The following table lists the output fields from `Get-CsOnlineVoiceUser` and the alternative method of getting the same information using a combination of `Get-CsOnlineUser`, `Get-CsPhoneNumberAssignment`, and `Get-CsOnlineLisLocation`. + +| Output field | Alternative | +| :---------------------------------| :--------------------------------- | +| Name | DisplayName in the output from `Get-CsOnlineUser` | +| Id | Identity in the output from `Get-CsOnlineUser`| +| SipDomain | Extract SipDomain from the SipAddress in the output from `Get-CsOnlineUser` | +| DataCenter | Extract DataCenter from RegistrarPool in the output from `Get-CsOnlineUser`| +| TenantId | TenantId in the output from `Get-CsOnlineUser`| +| PstnConnectivity | FeatureTypes in the output from `Get-CsOnlineUser`. If FeatureTypes contains `CallingPlan`, PstnConnectivity is `Online`. If FeatureTypes contains `PhoneSystem` and does not contain `CallingPlan`, PstnConnectivity is `OnPremises` | +| UsageLocation | UsageLocation in the output from `Get-CsOnlineUser` | +| EnterpriseVoiceEnabled | EnterpriseVoiceEnabled in the output from `Get-CsOnlineUser` | +| Number | LineUri in the output from `Get-CsOnlineUser`. You can get same phone number format by doing LineUri.Replace('tel:+','') | +| Location | Use LocationId in the output from `Get-CsPhoneNumberAssignment -AssignedPstnTargetId <Identity>` as the input to `Get-CsOnlineLisLocation -LocationId` | + +In Teams PowerShell Module version 3.0 and later in commercial cloud (and Teams PowerShell Module versions 5.0.1 and later in GCCH and DOD), the following improvements have been introduced for organizations using Teams: +- This cmdlet now accurately returns users who are voice-enabled (the older cmdlet in version 2.6.0 and earlier returned users without MCOEV* plans assigned). +- The result size is not limited to 100 users anymore (the older cmdlet in version 2.6.0 and earlier limited the result size to 100). + +In Teams PowerShell Module version 2.6.2 and later in commercial cloud (and Teams PowerShell Module versions 5.0.1 and later in GCCH and DOD), the following attributes are deprecated for organizations with Teams users using the ExpandLocation parameter: + +- Force +- NumberOfResultsToSkip +- CorrelationId +- Verb +- ResultSize +- LicenceState + +In Teams PowerShell Module version 2.6.2 and later in commercial cloud (and Teams PowerShell Module versions 5.0.1 and later in GCCH and DOD), the following input parameters are deprecated for organizations with Teams users due to low or zero usage: + +- DomainController +- Force +- GetFromAAD +- GetPendingUsers +- SearchQuery +- Skip +- Tenant +- Common Parameters + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceUser -Identity Ken.Myer@contoso.com +``` + +This example uses the User Principal Name (UPN) to retrieve the location and phone number information. + +## PARAMETERS + +### -CivicAddressId +Specifies the identity of the civic address that is assigned to the target users. + +```yaml +Type: XdsCivicAddressId +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnterpriseVoiceStatus +Possible values are: +* All +* Enabled +* Disabled + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExpandLocation +Displays the location parameter with its value. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -First +Specifies the number of users to return. +The default is 100. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GetFromAAD +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +Use this switch to get the users from Microsoft Entra ID. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GetPendingUsers +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +Use this switch to get only the users in pending state. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the identity of the target user. +Acceptable values include: + +Example: jphillips@contoso.com + +Example: sip:jphillips@contoso.com + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationId +Specifies the location identity of the location whose users will be returned. +You can find location identifiers by using the `Get-CsOnlineLisLocation` cmdlet. + +```yaml +Type: LocationID +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberAssigned +If specified, the query will return users who have a phone number assigned. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberNotAssigned +If specified, the query will return users who do not have a phone number assigned. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PSTNConnectivity + +Possible values are: +* All +* Online +* OnPremises + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SearchQuery +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +The SearchQuery parameter specifies a search string or a query formatted using Keyword Query Language (KQL). For more details about KQL, see Keyword Query Language syntax reference (https://go.microsoft.com/fwlink/p/?linkid=269603). + +If this parameter is empty, all users are returned. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Skip +Specifies the number of users to skip. +If you used the First parameter to return the first 50 users and wanted to get another 50, you could use -Skip 50 to avoid returning the first 50 you've already reviewed. +The default is 0. + +```yaml +Type: Unlimited +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +*This parameter has been deprecated from Teams PowerShell Modules 3.0 and above due to limited usage*. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Deserialized.Microsoft.Rtc.Management.Hosted.Bvd.Types.LacUser + +## NOTES + +## RELATED LINKS +[Set-CsOnlineVoiceUser](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceuser) diff --git a/teams/teams-ps/teams/Get-CsOnlineVoicemailPolicy.md b/teams/teams-ps/teams/Get-CsOnlineVoicemailPolicy.md new file mode 100644 index 0000000000..844b74b828 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineVoicemailPolicy.md @@ -0,0 +1,109 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinevoicemailpolicy +applicable: Microsoft Teams +title: Get-CsOnlineVoicemailPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineVoicemailPolicy + +## SYNOPSIS +Use the `Get-CsOnlineVoicemailPolicy` cmdlet to get a list of all pre-configured policy instances related to Cloud Voicemail service. + +## SYNTAX + +### Identity (Default) +``` +Get-CsOnlineVoicemailPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsOnlineVoicemailPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet retrieves information about one or more voicemail policies that have been configured for use in your organization. Voicemail policies are used by the organization to manage Voicemail-related features such as transcription. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineVoicemailPolicy +``` + +In Example 1, the Get-CsOnlineVoicemailPolicy cmdlet is called without any additional parameters; this returns a collection of all the voicemail policies configured for use in your organization. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsOnlineVoicemailPolicy -Identity TranscriptionDisabled +``` + +In Example 2, the Get-CsOnlineVoicemailPolicy cmdlet is used to return the per-user voicemail policy that has an Identity TranscriptionDisabled. Because identities are unique, this command will never return more than one item. + +### -------------------------- Example 3 -------------------------- +``` +Get-CsOnlineVoicemailPolicy -Filter "tag:*" +``` + +Example 3 uses the Filter parameter to return all the voicemail policies that have been configured at the per-user scope. The filter value "tag:*" tells the Get-CsOnlineVoicemailPolicy cmdlet to return only those policies that have an Identity that begins with the string value "tag:". + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. If this parameter is omitted, all voicemail policies available for use are returned. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -Filter +This parameter accepts a wildcard string and returns all voicemail policies with identities matching that string. For example, a Filter value of Tag:* will return all preconfigured voicemail policy instances (excluding forest default "Global") available to use by the tenant admins. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.WritableConfig.Policy.OnlineVoicemail.OnlineVoicemailPolicy + +## NOTES + +## RELATED LINKS +[Set-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailpolicy) + +[New-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoicemailpolicy) + +[Remove-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoicemailpolicy) + +[Grant-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoicemailpolicy) diff --git a/teams/teams-ps/teams/Get-CsOnlineVoicemailUserSettings.md b/teams/teams-ps/teams/Get-CsOnlineVoicemailUserSettings.md new file mode 100644 index 0000000000..b4437f7b08 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsOnlineVoicemailUserSettings.md @@ -0,0 +1,84 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csonlinevoicemailusersettings +applicable: Microsoft Teams +title: Get-CsOnlineVoicemailUserSettings +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsOnlineVoicemailUserSettings + +## SYNOPSIS +Use the Get-CsOnlineVoicemailUserSettings cmdlet to get information about online voicemail user settings of a specific user. + +## SYNTAX + +``` +Get-CsOnlineVoicemailUserSettings [-Identity] <string> [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsOnlineVoicemailUserSettings cmdlet returns information about online voicemail user settings of a specific user in your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsOnlineVoicemailUserSettings -Identity sip:user@contoso.com +``` + +This example gets the online voicemail user settings of user with SIP URI sip:user@contoso.com. + +## PARAMETERS + +### -Identity +The Identity parameter represents the ID of the specific user in your organization; this can be either a SIP URI or an Object ID. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Voicemail.Models.VoicemailUserSettings + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineVoicemailUserSettings](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailusersettings) diff --git a/teams/teams-ps/teams/Get-CsPhoneNumberAssignment.md b/teams/teams-ps/teams/Get-CsPhoneNumberAssignment.md new file mode 100644 index 0000000000..9b68146e1f --- /dev/null +++ b/teams/teams-ps/teams/Get-CsPhoneNumberAssignment.md @@ -0,0 +1,602 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csphonenumberassignment +applicable: Microsoft Teams +title: Get-CsPhoneNumberAssignment +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Get-CsPhoneNumberAssignment + +## SYNOPSIS +This cmdlet displays information about one or more phone numbers. + +## SYNTAX + +### Assignment (Default) +```powershell +Get-CsPhoneNumberAssignment [-ActivationState <string>] [-AssignedPstnTargetId <string>] [-AssignmentCategory <string>] + [-CapabilitiesContain <string>] [-CivicAddressId <string>] [-Filter <String>] [-IsoCountryCode <string>] + [-LocationId <string>] [-NetworkSiteId <string>] [-NumberType <string>] [-PstnAssignmentStatus <string>] [-Skip <int>] [-TelephoneNumber <string>] + [-TelephoneNumberContain <string>] [-TelephoneNumberGreaterThan <string>] [-TelephoneNumberLessThan <string>] + [-TelephoneNumberStartsWith <string>] [-Top <int>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet displays information about one or more phone numbers. You can filter the phone numbers to return by using different parameters. Returned results are sorted by TelephoneNumber in ascending order. Supported list of attributes for Filter are: +- TelephoneNumber +- OperatorId +- PstnAssignmentStatus (also supported AssignmentStatus) +- ActivationState +- IsoCountryCode +- Capability (also supported AcquiredCapabilities) +- IsOperatorConnect +- PstnPartnerName (also supported PartnerName) +- LocationId +- CivicAddressId +- NetworkSiteId +- NumberType +- AssignedPstnTargetId (also supported TargetId) +- TargetType +- AssignmentCategory +- ResourceAccountSharedCallingPolicySupported +- SupportedCustomerActions +- ReverseNumberLookup +- RoutingOptions +- SmsActivationState +- Tags + +If you are using both -Skip X and -Top Y for filtering, the returned results will first be skipped by X, and then the top Y results will be returned. + +By default, this cmdlet returns a maximum of 500 results. A maximum of 1000 results can be returned using -Top filter. If you need to get more than 1000 results, a combination of -Skip and -Top filtering can be used to list incremental returns of 1000 numbers. If a full list of telephone numbers acquired by the tenant is required, you can use [Export-CsAcquiredPhoneNumber](./export-csacquiredphonenumber.md) cmdlet to download a list of all acquired telephone numbers. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsPhoneNumberAssignment -TelephoneNumber +14025551234 +``` +```output +TelephoneNumber : +14025551234 +OperatorId : 2b24d246-a9ee-428b-96bc-fb9d9a053c8d +NumberType : CallingPlan +ActivationState : Activated +AssignedPstnTargetId : dc13d97b-7897-494e-bc28-6b469bf7a70e +AssignmentCategory : Primary +Capability : {UserAssignment} +City : Omaha +CivicAddressId : 703b30e5-dbdd-4132-9809-4c6160a6acc7 +IsoCountryCode : US +IsoSubdivision : Nebraska +LocationId : 407c17ae-8c41-431e-894a-38787c682f68 +LocationUpdateSupported : True +NetworkSiteId : +PortInOrderStatus : +PstnAssignmentStatus : UserAssigned +PstnPartnerId : 7fc2f2eb-89aa-41d7-93de-73d015d22ff0 +PstnPartnerName : Microsoft +NumberSource : Online +ReverseNumberLookup : {} +``` +This example displays information about the Microsoft Calling Plan subscriber phone number +1 (402) 555-1234. You can see that it is assigned to a user. + +### Example 2 +```powershell +Get-CsPhoneNumberAssignment -TelephoneNumber "+12065551000;ext=524" +``` +```output +TelephoneNumber : +12065551000;ext=524 +OperatorId : 83d289bc-a4d3-41e6-8a3f-cff260a3f091 +NumberType : DirectRouting +ActivationState : Activated +AssignedPstnTargetId : 2713551e-ed63-415d-9175-fc4ff825a0be +AssignmentCategory : Primary +Capability : {ConferenceAssignment, VoiceApplicationAssignment, UserAssignment} +City : +CivicAddressId : 00000000-0000-0000-0000-000000000000 +IsoCountryCode : +IsoSubdivision : +LocationId : 00000000-0000-0000-0000-000000000000 +LocationUpdateSupported : True +NetworkSiteId : +PortInOrderStatus : +PstnAssignmentStatus : UserAssigned +PstnPartnerId : +PstnPartnerName : +NumberSource : OnPremises +ReverseNumberLookup : {} +``` +This example displays information about the Direct Routing phone number +1 (206) 555-1000;ext=524. You can see that it is assigned to a user. + +### Example 3 +```powershell +Get-CsPhoneNumberAssignment -CapabilitiesContain "VoiceApplicationAssignment,ConferenceAssignment" +``` +This example returns all phone numbers that have both the capability VoiceApplicationAssignment and the capability ConferenceAssignment assigned, but phone numbers that have only one of these capabilities assigned won't be returned. + +### Example 4 +```powershell +Get-CsPhoneNumberAssignment -AssignedPstnTargetId user1@contoso.com +``` +This example returns information about the phone number assigned to user1@contoso.com. + +### Example 5 +```powershell +Get-CsPhoneNumberAssignment -AssignedPstnTargetId aa1@contoso.com +``` +This example returns information about the phone number assigned to resource account aa1@contoso.com. + +### Example 6 +```powershell +Get-CsPhoneNumberAssignment -ActivationState Activated -CapabilitiesContain VoiceApplicationAssignment -PstnAssignmentStatus Unassigned +``` +This example returns information about all activated phone numbers with the capability VoiceApplicationAssignment that are not assigned. + +### Example 7 +```powershell +Get-CsPhoneNumberAssignment -TelephoneNumberContain "524" +``` +This example returns information about all phone numbers that contain the digits 524, including the phone number with extension 524 used in example 2. + +### Example 8 +```powershell +Get-CsPhoneNumberAssignment -Skip 1000 -Top 1000 +``` +This example returns all phone numbers sequenced between 1001 to 2000 in the record of phone numbers. + +### Example 9 +```powershell +Get-CsPhoneNumberAssignment -AssignedPstnTargetId 'TeamsSharedCallingRoutingPolicy|Tag:SC1' +``` +This example returns all phone numbers assigned as emergency numbers in the Teams shared calling routing policy instance SC1. + +### Example 10 +```powershell +Get-CsPhoneNumberAssignment -TelephoneNumber "+12065551000;ext=524" +``` +```output +TelephoneNumber : +12065551000;ext=524 +OperatorId : 83d289bc-a4d3-41e6-8a3f-cff260a3f091 +NumberType : DirectRouting +ActivationState : Activated +AssignedPstnTargetId : 2713551e-ed63-415d-9175-fc4ff825a0be +AssignmentCategory : Primary +Capability : {ConferenceAssignment, VoiceApplicationAssignment, UserAssignment} +City : +CivicAddressId : 00000000-0000-0000-0000-000000000000 +IsoCountryCode : +IsoSubdivision : +LocationId : 00000000-0000-0000-0000-000000000000 +LocationUpdateSupported : True +NetworkSiteId : +PortInOrderStatus : +PstnAssignmentStatus : UserAssigned +PstnPartnerId : +PstnPartnerName : +NumberSource : OnPremises +ReverseNumberLookup : {SkipInternalVoip} +``` +This example displays when SkipInternalVoip option is turned on for a number. + +### Example 11 +```powershell +Get-CsPhoneNumberAssignment -Filter "TelephoneNumber -eq '+12065551000'" +``` +```output +TelephoneNumber : +12065551000 +OperatorId : 83d289bc-a4d3-41e6-8a3f-cff260a3f091 +NumberType : DirectRouting +ActivationState : Activated +AssignedPstnTargetId : 2713551e-ed63-415d-9175-fc4ff825a0be +AssignmentCategory : Primary +Capability : {ConferenceAssignment, VoiceApplicationAssignment, UserAssignment} +City : +CivicAddressId : 00000000-0000-0000-0000-000000000000 +IsoCountryCode : +IsoSubdivision : +LocationId : 00000000-0000-0000-0000-000000000000 +LocationUpdateSupported : True +NetworkSiteId : +PortInOrderStatus : +PstnAssignmentStatus : UserAssigned +PstnPartnerId : +PstnPartnerName : +NumberSource : OnPremises +ReverseNumberLookup : {} +``` +This example shows a way to use -Filter parameter to display information of a specific number. + +### Example 12 +```powershell +Get-CsPhoneNumberAssignment -Filter "TelephoneNumber -like '+12065551000' -and NumberType -eq 'DirectRouting'" +``` +```output +TelephoneNumber : +12065551000 +OperatorId : 83d289bc-a4d3-41e6-8a3f-cff260a3f091 +NumberType : DirectRouting +ActivationState : Activated +AssignedPstnTargetId : 2713551e-ed63-415d-9175-fc4ff825a0be +AssignmentCategory : Primary +Capability : {ConferenceAssignment, VoiceApplicationAssignment, UserAssignment} +City : +CivicAddressId : 00000000-0000-0000-0000-000000000000 +IsoCountryCode : +IsoSubdivision : +LocationId : 00000000-0000-0000-0000-000000000000 +LocationUpdateSupported : True +NetworkSiteId : +PortInOrderStatus : +PstnAssignmentStatus : UserAssigned +PstnPartnerId : +PstnPartnerName : +NumberSource : OnPremises +ReverseNumberLookup : {} +``` +This example shows a way to get filtered results using multiple Filter parameters. + + +## PARAMETERS + +### -ActivationState +Filters the returned results based on the number type. Supported values are Activated, AssignmentPending, AssignmentFailed, UpdatePending, and UpdateFailed. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssignedPstnTargetId +Filters the returned results based on the user or resource account ID the phone number is assigned to. Supported values are UserPrincipalName, SIP address, ObjectId, and the Teams shared calling routing policy instance name. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AssignmentCategory +This parameter is used to differentiate between Primary and Private line assignment for a user. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CapabilitiesContain +Filters the returned results based on the capabilities assigned to the phone number. You can specify one or more capabilities delimited by a comma. Supported capabilities are ConferenceAssignment, VoiceApplicationAssignment, UserAssignment, and TeamsPhoneMobile. + +If you specify only one capability, you will get all phone numbers returned that have that capability assigned. If you specify a comma separated list for instance like +ConferenceAssignment, VoiceApplicationAssignment you will get all phone numbers that have both capabilities assigned, but you won't get phone numbers that have only +VoiceApplicationAssignment or ConferenceAssignment assigned as capability. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CivicAddressId +Filters the returned results based on the CivicAddressId assigned to the phone number. You can get the CivicAddressId by using [Get-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/get-csonlineliscivicaddress). + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +This can be used to filter on one or more parameters within the search results. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsoCountryCode +Filters the returned results based on the ISO 3166-1 Alpha-2 country code assigned to the phone number. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationId +Filters the returned results based on the LocationId assigned to the phone number. You can get the LocationId by using [Get-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/get-csonlinelislocation). + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkSiteId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberType +Filters the returned results based on the number type. Supported values are DirectRouting, CallingPlan, and OperatorConnect. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PstnAssignmentStatus +Filters the returned results based on the assignment status. Support values are Unassigned, UserAssigned, ConferenceAssigned, VoiceApplicationAssigned, ThirdPartyAppAssigned, and PolicyAssigned. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Skip +Skips the first X returned results and the default value is 0. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TelephoneNumber +Filters the returned results to a specific phone number. It is optional to specify a prefixed "+". The phone number can't have "tel:" prefixed. +We support Direct Routing numbers with extensions using the formats +1206555000;ext=1234 or 1206555000;ext=1234. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TelephoneNumberContain + +Filters the returned results based on substring match for the specified string on TelephoneNumber. To search for a number with an extension, you need to specify +the digits of the extension. For supported formats see TelephoneNumber. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TelephoneNumberGreaterThan +Filters the returned results based on greater than match for the specified string on TelephoneNumber. Can be used together with TelephoneNumberLessThan to specify a +range of phone numbers to return results for. For supported formats see TelephoneNumber. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TelephoneNumberLessThan +Filters the returned results based on less than match for the specified string on TelephoneNumber. Can be used together with TelephoneNumberGreaterThan to specify a +range of phone numbers to return results for. For supported formats see TelephoneNumber. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TelephoneNumberStartsWith +Filters the returned results based on starts with string match for the specified string on TelephoneNumber. For supported formats see TelephoneNumber. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Top +Returns the first X returned results and the default value is 500. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### ActivationState +The activation state of the telephone number. + +### AssignedPstnTargetId +The ID of the object the phone number is assigned to, either the ObjectId of a user or resource account or the policy instance ID of a Teams shared calling routing policy instance. + +### AssignmentCategory +This parameter is reserved for internal Microsoft use. + +### Capability +The list of capabilities assigned to the phone number. + +### City +The city where the phone number is located. + +### CivicAddressId +The ID of the CivicAddress assigned to the phone number. + +### IsoCountryCode +The ISO country code assigned to the phone number. + +### IsoSubDivision +The subdivision within the country/region assigned to the phone number, for example, the state for US phone numbers. + +### LocationId +The ID of the Location assigned to the phone number. + +### LocationUpdateSupported +Boolean stating if updating of the location assigned to the phone number is allowed. + +### NetworkSiteId +This parameter is reserved for internal Microsoft use. + +### NumberSource +The source of the phone number. Online for phone numbers assigned in Microsoft 365 and OnPremises for phone numbers assigned in AD on-premises and synchronized into Microsoft 365. + +### NumberType +The type of the phone number. + +### OperatorId +The ID of the operator. + +### PortInOrderStatus +The status of any port in order covering the phone number. + +### PstnAssignmentStatus +The assignment status of the phone number. + +### PstnPartnerId +The ID of the PSTN partner providing the phone number. + +### PstnPartnerName +The name of the PSTN partner. + +### TelephoneNumber +The phone number. The number is always displayed with prefixed "+", even if it was not assigned using prefixed "+". + +The object returned is of type SkypeTelephoneNumberMgmtCmdletAcquiredTelephoneNumber. + +### ReverseNumberLookup +Status of Reverse Number Lookup (RNL). When it is set to SkipInternalVoip, the calls are handled through external PSTN connection instead of internal VoIP lookup. + +## NOTES +The cmdlet is available in Teams PowerShell module 4.0.0 or later. The parameter AssignmentCategory was introduced in Teams PowerShell module 5.3.1-preview. The parameter NetworkSiteId was introduced in Teams PowerShell module 5.5.0. The output parameter NumberSource was introduced in Teams PowerShell module 5.7.0. + +The cmdlet is only available in commercial and GCC cloud instances. + +## RELATED LINKS +[Remove-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment) + +[Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) diff --git a/teams/teams-ps/teams/Get-CsPhoneNumberTag.md b/teams/teams-ps/teams/Get-CsPhoneNumberTag.md new file mode 100644 index 0000000000..beba5186cd --- /dev/null +++ b/teams/teams-ps/teams/Get-CsPhoneNumberTag.md @@ -0,0 +1,58 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/get-csphonenumbertag +applicable: Microsoft Teams +title: Get-CsPhoneNumberTag +author: pavellatif +ms.author: pavellatif +ms.reviewer: pavellatif +manager: roykuntz +schema: 2.0.0 +--- + +# Get-CsPhoneNumberTag + +## SYNOPSIS +This cmdlet allows the admin to get a list of existing tags for telephone numbers. + +## SYNTAX + +``` +Get-CsPhoneNumberTag [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet will get a list of all existing tags that are assigned to phone numbers in the tenant. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsPhoneNumberTag +``` +```output +TagValue +HR +Redmond HQ +Executives +``` + +This example shows how to get a list of existing tags for telephone numbers + +## 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ISkypeTelephoneNumberMgmtCmdletTenantTagRecord + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsPolicyPackage.md b/teams/teams-ps/teams/Get-CsPolicyPackage.md index 52766ec557..0e3330e1af 100644 --- a/teams/teams-ps/teams/Get-CsPolicyPackage.md +++ b/teams/teams-ps/teams/Get-CsPolicyPackage.md @@ -1,13 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -applicable: Microsoft Teams title: Get-CsPolicyPackage -author: etgottli -ms.author: etgottli -ms.reviewer: icchan +author: serdarsoysal +ms.author: serdars manager: amitar -online version: https://docs.microsoft.com/powershell/module/teams/get-cspolicypackage +online version: https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage schema: 2.0.0 --- @@ -19,14 +17,14 @@ This cmdlet supports retrieving all the policy packages available on a tenant. ## SYNTAX -``` -Get-CsPolicyPackage [[-Identity] <String>] [<CommonParameters>] +```powershell +Get-CsPolicyPackage [[-Identity] <String>] -InputObject <IConfigApiBasedCmdletsIdentity> [<CommonParameters>] ``` ## DESCRIPTION This cmdlet supports retrieving all the policy packages available on a tenant. Provide the identity of a specific policy package to retrieve its definition, including details on the policies applied with the package. -For more information on policy packages, please review https://docs.microsoft.com/en-us/MicrosoftTeams/manage-policy-packages +For more information on policy packages, please review https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages. ## EXAMPLES @@ -42,7 +40,27 @@ Returns all policy packages available on the tenant. PS C:\> Get-CsPolicyPackage -Identity Education_PrimaryStudent ``` -Returns the definition of the Education_PrimaryStudent policy package, including the policies applied with the package. +Returns only the Education_PrimaryStudent policy package. + +### Example 3 +```powershell +PS C:\> $a = Get-CsPolicyPackage -Identity Education_PrimaryStudent +PS C:\> $a.Policies + +# In module versions 1.1.9+ +PS C:\> $a = Get-CsPolicyPackage -Identity Education_PrimaryStudent +PS C:\> $a.Policies.AdditionalProperties + +Key Value +--- ----- +TeamsMessagingPolicy {[Identity, Education_PrimaryStudent], [Description, This is an Education_PrimarySt... +TeamsMeetingPolicy {[Identity, Education_PrimaryStudent], [Description, This is an Education_PrimarySt... +TeamsAppSetupPolicy {[Identity, Education_PrimaryStudent], [Description, This is an Education_PrimarySt... +TeamsCallingPolicy {[Identity, Education_PrimaryStudent], [Description, This is an Education_PrimarySt... +TeamsMeetingBroadcastPolicy {[Identity, Education_PrimaryStudent], [Description, This is an Education_PrimarySt... +``` + +Returns the set of policies in the Education_PrimaryStudent policy package. ## PARAMETERS @@ -62,6 +80,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -InputObject + +The identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). @@ -73,8 +107,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Get-CsUserPolicyPackageRecommendation](Get-CsUserPolicyPackageRecommendation.md) +[Get-CsUserPolicyPackageRecommendation](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackagerecommendation) -[Get-CsUserPolicyPackage](Get-CsUserPolicyPackage.md) +[Get-CsUserPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackage) -[Grant-CsUserPolicyPackage](Grant-CsUserPolicyPackage.md) +[Grant-CsUserPolicyPackage](https://learn.microsoft.com/powershell/module/teams/grant-csuserpolicypackage) diff --git a/teams/teams-ps/teams/Get-CsSdgBulkSignInRequestStatus.md b/teams/teams-ps/teams/Get-CsSdgBulkSignInRequestStatus.md new file mode 100644 index 0000000000..7152c35e07 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsSdgBulkSignInRequestStatus.md @@ -0,0 +1,66 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +online version: +title: Get-CsSdgBulkSignInRequestStatus +schema: 2.0.0 +--- + +# Get-CsSdgBulkSignInRequestStatus + +## SYNOPSIS +Get the status of an active bulk sign in request. + +## SYNTAX + +``` +Get-CsSdgBulkSignInRequestStatus -Batchid <String> [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to get granular device level details of a bulk sign in request. Status is shown for every username and hardware ID pair included in the device details CSV used as input to the bulk sign in request. + +## EXAMPLES + +### Example 1 +```powershell +$newBatchResponse = New-CsSdgBulkSignInRequest -DeviceDetailsFilePath .\Example.csv -Region APAC +$newBatchResponse.BatchId +$getBatchStatusResponse = Get-CsSdgBulkSignInRequestStatus -Batchid $newBatchResponse.BatchId +$getBatchStatusResponse | ft +$getBatchStatusResponse.BatchItem +``` + +This example shows how to read the batch status response into a new variable and print the status for every batch item. + +## PARAMETERS + +### -Batchid +Batch ID is the response returned by the `New-CsSdgBulkSignInRequest` cmdlet. It is used as input for querying the status of the batch through `Get-CsSdgBulkSignInRequestStatus` cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ISdgBulkSignInRequestStatusResult + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsSdgBulkSignInRequestsSummary.md b/teams/teams-ps/teams/Get-CsSdgBulkSignInRequestsSummary.md new file mode 100644 index 0000000000..b1f9e93472 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsSdgBulkSignInRequestsSummary.md @@ -0,0 +1,48 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +online version: +title: Get-CsSdgBulkSignInRequestsSummary +schema: 2.0.0 +--- + +# Get-CsSdgBulkSignInRequestsSummary + +## SYNOPSIS +Get the tenant level summary of all bulk sign in requests executed in the past 30 days. + +## SYNTAX + +``` +Get-CsSdgBulkSignInRequestsSummary [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet gives the overall tenant level summary of all bulk sign in requests executed for a particular tenant within the last 30 days. Status is shown at batch level as succeeded / failed. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsSdgBulkSignInRequestsSummary +``` + +This example shows how to run the cmdlet to get a tenant level summary. + +## 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ISdgBulkSignInRequestsSummaryResponseItem + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsSharedCallQueueHistoryTemplate.md b/teams/teams-ps/teams/Get-CsSharedCallQueueHistoryTemplate.md new file mode 100644 index 0000000000..eed80beb3f --- /dev/null +++ b/teams/teams-ps/teams/Get-CsSharedCallQueueHistoryTemplate.md @@ -0,0 +1,91 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsSharedCallQueueHistoryTemplate +applicable: Microsoft Teams +title: Get-CsSharedCallQueueHistoryTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsSharedCallQueueHistoryTemplate + +## SYNTAX + +```powershell +Get-CsSharedCallQueueHistoryTemplate -Id <string> [<CommonParameters>] +``` + +## DESCRIPTION +Use the Get-CsSharedCallQueueHistory cmdlet to list the Shared Call Queue History templates + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsSharedCallQueueHistoryTemplate -Id 3a4b3d9b-91d8-4fbf-bcff-6907f325842c +``` + +This example retrieves the Shared Call Queue History Template with the Id `3a4b3d9b-91d8-4fbf-bcff-6907f325842c` + +### -------------------------- Example 2 -------------------------- +``` +Get-CsSharedCallQueueHistoryTemplate +``` + +This example retrieves all the Shared Call Queue History Templates + +## PARAMETERS + +### -Id +The Id of the shared call queue history template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: false +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[New-CsSharedCallQueueHistoryTemplate](./New-CsSharedCallQueueHistoryTemplate.md) + +[Set-CsSharedCallQueueHistoryTemplate](./Set-CsSharedCallQueueHistoryTemplate.md) + +[Remove-CsSharedCallQueueHistoryTemplate](./Remove-CsSharedCallQueueHistoryTemplate.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + + + diff --git a/teams/teams-ps/teams/Get-CsTeamTemplate.md b/teams/teams-ps/teams/Get-CsTeamTemplate.md new file mode 100644 index 0000000000..de8f75a2f2 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamTemplate.md @@ -0,0 +1,244 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamtemplate +title: Get-CsTeamTemplate +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: farahf +schema: 2.0.0 +--- + +# Get-CsTeamTemplate + +## SYNOPSIS + +This cmdlet supports retrieving details of a team template available to your tenant given the team template uri. + +NOTE: The returned template definition is a PowerShell object formatted as a JSON for readability. Please refer to the examples for suggested interaction flows for template management. + +## SYNTAX + +### Get (Default) + +```powershell +Get-CsTeamTemplate -OdataId <String> [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity + +```powershell +Get-CsTeamTemplate -InputObject <IConfigApiBasedCmdletsIdentity> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet supports retrieving details of a team template available to your tenant given the team template uri. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\> (Get-CsTeamTemplateList -PublicTemplateLocale en-US) | where Name -like 'test' | ForEach-Object {Get-CsTeamTemplate -OdataId $_.OdataId} +``` + +Within the universe of templates the admin's tenant has access to, returns a template definition object (displayed as a JSON by default) for every custom and every Microsoft en-US template which names include 'test'. + +### EXAMPLE 2 + +```powershell +PS C:\> Get-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/cefcf333-91a9-43d0-919f-bbca5b7d2b24/Tenant/en-US' > 'config.json' +``` + +Saves the template with specified template ID as a JSON file. + +## PARAMETERS + +### -OdataId + +A composite URI of a template. + +```yaml +Type: String +Parameter Sets: Get +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +Identity Parameter +To construct, see NOTES section for INPUTOBJECT properties and create a hash table. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break + +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend + +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend + +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy + +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential + +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials + +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamTemplate + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorObject + +## NOTES + +COMPLEX PARAMETER PROPERTIES + +To create the parameters described below, construct a hash table containing the appropriate properties. For information on hash tables, run Get-Help about_Hash_Tables. + +INPUTOBJECT \<IConfigApiBasedCmdletsIdentity\>: Identity Parameter + - `[Bssid <String>]`: + - `[ChassisId <String>]`: + - `[CivicAddressId <String>]`: Civic address id. + - `[Country <String>]`: + - `[GroupId <String>]`: The ID of a group whose policy assignments will be returned. + - `[Id <String>]`: + - `[Identity <String>]`: + - `[Locale <String>]`: + - `[LocationId <String>]`: Location id. + - `[OdataId <String>]`: A composite URI of a template. + - `[OperationId <String>]`: The ID of a batch policy assignment operation. + - `[OrderId <String>]`: + - `[PackageName <String>]`: The name of a specific policy package + - `[PolicyType <String>]`: The policy type for which group policy assignments will be returned. + - `[Port <String>]`: + - `[PortInOrderId <String>]`: + - `[PublicTemplateLocale <String>]`: Language and country code for localization of publicly available templates. + - `[SubnetId <String>]`: + - `[TenantId <String>]`: + - `[UserId <String>]`: UserId. Supports Guid. Eventually UPN and SIP. + +## RELATED LINKS + +[Get-CsTeamTemplateList](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) + +[Get-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplate) + +[New-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamtemplate) + +[Update-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/update-csteamtemplate) + +[Remove-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/remove-csteamtemplate) diff --git a/teams/teams-ps/teams/Get-CsTeamTemplateList.md b/teams/teams-ps/teams/Get-CsTeamTemplateList.md new file mode 100644 index 0000000000..c9928c4038 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamTemplateList.md @@ -0,0 +1,147 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist +title: Get-CsTeamTemplateList +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: farahf +schema: 2.0.0 +--- + +# Get-CsTeamTemplateList + +## SYNOPSIS + +This cmdlet supports retrieving information of all team templates available to your tenant, including both first party Microsoft team templates as well as custom templates. The templates information retrieved includes OData Id, template name, short description, count of channels and count of applications. +Note: All custom templates will be retrieved, regardless of the locale specification. If you have hidden templates in the admin center, you will still be able to see the hidden templates here. + +## SYNTAX + +### Get (Default) + +```powershell +Get-CsTeamTemplateList [[-PublicTemplateLocale] <String>] [<CommonParameters>] +``` + +### GetViaIdentity + +```powershell +Get-CsTeamTemplateList -InputObject <IConfigApiBasedCmdletsIdentity> [<CommonParameters>] +``` + +## DESCRIPTION + +Get a list of available team templates + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\> Get-CsTeamTemplateList +``` + +Returns all en-US templates within the universe of templates the admin's tenant has access to. + +Note: All 1P Microsoft templates will always be returned in the specified locale. If the locale is not specified, en-US will be used. + +### EXAMPLE 2 + +```powershell +PS C:\> (Get-CsTeamTemplateList -PublicTemplateLocale en-US) | where ChannelCount -GT 3 +``` + +Returns all en-US templates that have 3 channels within the universe of templates the admin's tenant has access to. + +## PARAMETERS + +### -PublicTemplateLocale + +The language and country code of templates localization for Microsoft team templates. This will not be applied to your tenant custom team templates. Defaults to en-US. + +```yaml +Type: String +Parameter Sets: Get +Aliases: + +Required: False +Position: 1 +Default value: 'en-US' +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +Identity Parameter +To construct, see NOTES section for INPUTOBJECT properties and create a hash table. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorObject + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamTemplateSummary + +## NOTES + +COMPLEX PARAMETER PROPERTIES + +To create the parameters described below, construct a hash table containing the appropriate properties.\ +For information on hash tables, run Get-Help about_Hash_Tables.\ +\ +INPUTOBJECT \<IConfigApiBasedCmdletsIdentity\>: Identity Parameter\ +\[Bssid \<String\>\]:\ +\[ChassisId \<String\>\]:\ +\[CivicAddressId \<String\>\]: Civic address id.\ +\[Country \<String\>\]:\ +\[GroupId \<String\>\]: The ID of a group whose policy assignments will be returned.\ +\[Id \<String\>\]:\ +\[Identity \<String\>\]:\ +\[Locale \<String\>\]: The language and country code of templates localization.\ +\[LocationId \<String\>\]: Location id.\ +\[OdataId \<String\>\]: A composite URI of a template.\ +\[OperationId \<String\>\]: The ID of a batch policy assignment operation.\ +\[OrderId \<String\>\]:\ +\[PackageName \<String\>\]: The name of a specific policy package\ +\[PolicyType \<String\>\]: The policy type for which group policy assignments will be returned.\ +\[Port \<String\>\]:\ +\[PortInOrderId \<String\>\]:\ +\[SubnetId \<String\>\]:\ +\[TenantId \<String\>\]:\ +\[UserId \<String\>\]: UserId.\ +Supports Guid.\ +Eventually UPN and SIP. + +## RELATED LINKS + +[Get-CsTeamTemplateList](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) + +[Get-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplate) + +[New-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamtemplate) + +[Update-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/update-csteamtemplate) + +[Remove-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/remove-csteamtemplate) diff --git a/teams/teams-ps/teams/Get-CsTeamsAIPolicy.md b/teams/teams-ps/teams/Get-CsTeamsAIPolicy.md new file mode 100644 index 0000000000..77a631f12f --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsAIPolicy.md @@ -0,0 +1,89 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Get-CsTeamsAIPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsTeamsAIPolicy +schema: 2.0.0 +author: Andy447 +ms.author: andywang +--- + +# Get-CsTeamsAIPolicy + +## SYNOPSIS + +This cmdlet retrieves all Teams AI policies for the tenant. + +## SYNTAX + +```powershell +Get-CsTeamsAIPolicy [[-Identity] <String>] [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +The new csTeamsAIPolicy will replace the existing enrollment settings in csTeamsMeetingPolicy, providing enhanced flexibility and control for Teams meeting administrators. Unlike the current single setting, EnrollUserOverride, which applies to both face and voice enrollment, the new policy introduces two distinct settings: EnrollFace and EnrollVoice. These can be individually set to Enabled or Disabled, offering more granular control over biometric enrollments. A new setting, SpeakerAttributionBYOD, is also being added to csTeamsAIPolicy. This allows IT admins to turn off speaker attribution in BYOD scenarios, giving them greater control over how voice data is managed in such environments. This setting can be set to Enabled or Disabled, and will be Enabled by default. In addition to improving the management of face and voice data, the csTeamsAIPolicy is designed to support future AI-related settings in Teams, making it a scalable solution for evolving needs. + +This cmdlet retrieves all Teams AI policies for the tenant. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsAIPolicy +``` + +Retrieves Teams AI policies and shows "EnrollFace", "EnrollVoice" and "SpeakerAttributionBYOD" values. + +## PARAMETERS + +### -Identity +Identity of the Teams AI policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. +To return a collection of all the per-user policies, use this syntax: -Filter "tag:*". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsaipolicy) + +[Remove-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsaipolicy) + +[Set-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy) + +[Grant-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaipolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsAcsFederationConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsAcsFederationConfiguration.md new file mode 100644 index 0000000000..6ba81b228a --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsAcsFederationConfiguration.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsAcsFederationConfiguration +author: tomkau +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsacsfederationconfiguration +schema: 2.0.0 +--- + +# Get-CsTeamsAcsFederationConfiguration + +## SYNOPSIS + +This cmdlet is used to retrieve the federation configuration between Teams and Azure Communication Services. For more information, refer to [Azure Communication Services and Teams Interoperability](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). + +## SYNTAX + +```powershell +Get-CsTeamsAcsFederationConfiguration + [-Identity <String[]>] + [-Filter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION + +Federation between Teams and Azure Communication Services (ACS) allows users of custom solutions built with ACS to connect and communicate with Teams users over voice, video, Teams users over voice, video and screen sharing, and more. For more information, see [Teams interoperability](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). + +This cmdlet is used retrieve the Teams and ACS federation configuration for a Teams tenant. + +You must be a Teams service admin or a Teams communication admin for your organization to run the cmdlet. + +## Examples + +### Example 1 +```powershell +PS C:\> Get-CsTeamsAcsFederationConfiguration + +Identity : Global +AllowedAcsResources : {'faced04c-2ced-433d-90db-063e424b87b1'} +EnableAcsUsers : True +``` + +In this example, federation has been enabled for just one ACS resource. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsAcsFederationConfiguration + +Identity : Global +AllowedAcsResources : {} +EnableAcsUsers : False +``` + +In this example, federation is disabled for all ACS resources. + +## PARAMETERS + +### -Filter +Enables you to use wildcards when specifying the Teams and ACS federation configuration settings to be returned. +Because you can only have a single, global instance of these settings there is little reason to use the Filter parameter. +However, if you prefer, you can use syntax similar to this to retrieve the global settings: -Identity "g*". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the collection of tenant federation configuration settings to be modified. Because each tenant is limited to a single, global collection of federation settings there is no need include this parameter when calling the Set-CsTenantFederationConfiguration cmdlet. If you do choose to use the Identity parameter you must also include the Tenant parameter. For example: + +`Set-CsTenantFederationConfiguration -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Identity "global"` + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration) + +[New-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csexternalaccesspolicy) + +[Set-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/set-csexternalaccesspolicy) + +[Grant-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csexternalaccesspolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsAppPermissionPolicy.md b/teams/teams-ps/teams/Get-CsTeamsAppPermissionPolicy.md new file mode 100644 index 0000000000..cc36983ff2 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsAppPermissionPolicy.md @@ -0,0 +1,162 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsapppermissionpolicy +applicable: Microsoft Teams +title: Get-CsTeamsAppPermissionPolicy +schema: 2.0.0 +ms.reviewer: mhayrapetyan +manager: prkosh +ms.author: prkosh +author: ashishguptaiitb +--- + +# Get-CsTeamsAppPermissionPolicy + +## SYNOPSIS +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. This cmdlet is not supported for tenants that migrated to app centric management feature as it replaced permission policies. While the cmdlet may succeed, the changes aren't applied to the tenant. + +As an admin, you can use app permission policies to allow or block apps for your users. Learn more about the app permission policies at <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies> and about app centric management at <https://learn.microsoft.com/microsoftteams/app-centric-management>. + +**This is only applicable for tenants who have not been migrated to ACM or UAM.** + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies>. + +## EXAMPLES + +### Example 1 + +```powershell +Get-CsTeamsAppPermissionPolicy -Identity Global +``` + +```Output +Identity : Global +DefaultCatalogApps : {Id=26bc2873-6023-480c-a11b-76b66605ce8c, Id=0d820ecd-def2-4297-adad-78056cde7c78, Id=com.microsoft.teamspace.tab.planner} +GlobalCatalogApps : {} +PrivateCatalogApps : {} +Description : +DefaultCatalogAppsType : AllowedAppList +GlobalCatalogAppsType : AllowedAppList +PrivateCatalogAppsType : AllowedAppList +``` +Get the global Teams app permission policy. + +### Example 2 + +```powershell +Get-CsTeamsAppPermissionPolicy +``` + +```Output +Identity : Global +DefaultCatalogApps : {Id=26bc2873-6023-480c-a11b-76b66605ce8c, Id=0d820ecd-def2-4297-adad-78056cde7c78, Id=com.microsoft.teamspace.tab.planner} +GlobalCatalogApps : {} +PrivateCatalogApps : {} +Description : +DefaultCatalogAppsType : AllowedAppList +GlobalCatalogAppsType : AllowedAppList +PrivateCatalogAppsType : AllowedAppList + +Identity : Tag:test +DefaultCatalogApps : {Id=26bc2873-6023-480c-a11b-76b66605ce8c, Id=0d820ecd-def2-4297-adad-78056cde7c78, Id=com.microsoft.teamspace.tab.planner} +GlobalCatalogApps : {} +PrivateCatalogApps : {} +Description : +DefaultCatalogAppsType : AllowedAppList +GlobalCatalogAppsType : AllowedAppList +PrivateCatalogAppsType : AllowedAppList +``` +Get all the Teams app permission policies. + +## PARAMETERS + +### -Filter +Do not use + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the app setup permission policy. If empty, all identities will be used by default. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Do not use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +{{Fill Tenant Description}} + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsAppSetupPolicy.md b/teams/teams-ps/teams/Get-CsTeamsAppSetupPolicy.md new file mode 100644 index 0000000000..47de4b4b99 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsAppSetupPolicy.md @@ -0,0 +1,165 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsappsetuppolicy +applicable: Microsoft Teams +title: Get-CsTeamsAppSetupPolicy +schema: 2.0.0 +ms.reviewer: +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsTeamsAppSetupPolicy + +## SYNOPSIS +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsAppSetupPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsAppSetupPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## EXAMPLES + +### Example 1 + +```powershell +Get-CsTeamsAppSetupPolicy -Identity Global +``` + +```Output +Identity : Global +AppPresetList : {Id=d2c6f111-ffad-42a0-b65e-ee00425598aa} +PinnedAppBarApps : {Id=14d6962d-6eeb-4f48-8890-de55454bb136;Order=1, Id=86fcd49b-61a2-4701-b771-54728cd291fb;Order=2, Id=2a84919f-59d8-4441-a975-2a8c2643b741;Order=3, Id=ef56c0de-36fc-4ef8-b417-3d82ba9d073c;Order=4...} +PinnedMessageBarApps : {} +AppPresetMeetingList : {} +Description : +AllowSideLoading : True +AllowUserPinning : True +``` +Get all the Teams App Setup Policies. + +### Example 2 + +```powershell +Get-CsTeamsAppSetupPolicy +``` + +```Output +Identity : Global +AppPresetList : {Id=d2c6f111-ffad-42a0-b65e-ee00425598aa} +PinnedAppBarApps : {Id=14d6962d-6eeb-4f48-8890-de55454bb136;Order=1, Id=86fcd49b-61a2-4701-b771-54728cd291fb;Order=2, Id=2a84919f-59d8-4441-a975-2a8c2643b741;Order=3, Id=ef56c0de-36fc-4ef8-b417-3d82ba9d073c;Order=4...} +PinnedMessageBarApps : {} +AppPresetMeetingList : {} +Description : +AllowSideLoading : True +AllowUserPinning : True + +Identity : Tag:Set-test +AppPresetList : {Id=d2c6f111-ffad-42a0-b65e-ee00425598aa} +PinnedAppBarApps : {Id=14d6962d-6eeb-4f48-8890-de55454bb136;Order=1, Id=86fcd49b-61a2-4701-b771-54728cd291fb;Order=2, Id=2a84919f-59d8-4441-a975-2a8c2643b741;Order=3, Id=ef56c0de-36fc-4ef8-b417-3d82ba9d073c;Order=4...} +PinnedMessageBarApps : {} +AppPresetMeetingList : {} +Description : +AllowSideLoading : True +AllowUserPinning : True +``` +Get all the Teams App Setup Policies. + +## PARAMETERS + +### -Filter +Do not use. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of App setup policy. If empty, all Identities will be used by default. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Do not use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Do not use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsAudioConferencingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsAudioConferencingPolicy.md new file mode 100644 index 0000000000..77cad0be0c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsAudioConferencingPolicy.md @@ -0,0 +1,110 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsaudioconferencingpolicy +title: Get-CsTeamsAudioConferencingPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsAudioConferencingPolicy + +## SYNOPSIS + +Audio conferencing policies can be used to manage audio conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsAudioConferencingPolicy [[-Identity] <String>] [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsAudioConferencingPolicy [-LocalStore] [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsTeamsAudioConferencingPolicy cmdlet enables administrators to control audio conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. The Get-CsTeamsAudioConferencingPolicy cmdlet enables you to return information about all the audio-conferencing policies that have been configured for use in your organization. + +## EXAMPLES + +### EXAMPLE 1 +``` +PS C:\> Get-CsTeamsAudioConferencingPolicy +``` + +The command shown in Example 1, Get-CsTeamsAudioConferencingPolicy is called without any additional parameters; this returns a collection of all the teams audio conferencing policies configured for use in your organization. + +### EXAMPLE 2 +``` +PS C:\> Get-CsTeamsAudioConferencingPolicy -Identity "EMEA Users" +``` + +The command shown in Example 2, Get-CsTeamsAudioConferencingPolicy is used to return the per-user audio conferencing policy that has an Identity "EMEA Users". Because identities are unique, this command will never return more than one item. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the policy to be retrieved. To retrieve the global policy, use this syntax: -Identity global. To retrieve a per-user policy use syntax similar to this: -Identity "EMEA Users". +If this parameter is not included, the Get-CsTeamsAudioConferencingPolicy cmdlet will return a collection of all the teams audio conferencing policies configured for use in your organization. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Internal Microsoft use only. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Object +## NOTES + +## RELATED LINKS + +[Set-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaudioconferencingpolicy) + +[New-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsaudioconferencingpolicy) + +[Grant-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaudioconferencingpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsCallHoldPolicy.md b/teams/teams-ps/teams/Get-CsTeamsCallHoldPolicy.md new file mode 100644 index 0000000000..479035c0ea --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsCallHoldPolicy.md @@ -0,0 +1,127 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscallholdpolicy +applicable: Microsoft Teams +title: Get-CsTeamsCallHoldPolicy +schema: 2.0.0 +ms.reviewer: +manager: abnair +ms.author: serdars +author: serdarsoysal +--- + +# Get-CsTeamsCallHoldPolicy + +## SYNOPSIS + +Returns information about the policies configured to customize the call hold experience for Teams clients. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsCallHoldPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsCallHoldPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Teams call hold policies are used to customize the call hold experience for teams clients. +When Microsoft Teams users participate in calls, they have the ability to hold a call and have the other entity in the call listen to an audio file during the duration of the hold. + +Assigning a Teams call hold policy to a user sets an audio file to be played during the duration of the hold. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsCallHoldPolicy +``` + +The command shown in Example 1 returns information for all the Teams call hold policies configured for use in the tenant. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsCallHoldPolicy -Identity 'ContosoPartnerCallHoldPolicy' +``` + +In Example 2, information is returned for a single Teams call hold policy: the policy with the Identity ContosoPartnerCallHoldPolicy. + +### Example 3 +```powershell +PS C:\> Get-CsTeamsCallHoldPolicy -Filter 'Tag:*' +``` + +The command shown in Example 3 returns information about all the Teams call hold policies configured at the per-user scope. +To do this, the command uses the Filter parameter and the filter value "Tag:\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "Tag:". + +## PARAMETERS + +### -Filter +Enables you to use wildcards when retrieving one or more Teams call hold policies. +For example, to return all the policies configured at the per-user scope, use this syntax: + +-Filter "Tag:\*" + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier of the Teams call hold policy to be retrieved. + +To return the global policy, use this syntax: + +`-Identity "Global"` + +To return a policy configured at the per-user scope, use syntax like this: + +`-Identity "ContosoPartnerCallHoldPolicy"` + +You cannot use wildcard characters when specifying the Identity. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallholdpolicy) + +[Set-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallholdpolicy) + +[Grant-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallholdpolicy) + +[Remove-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallholdpolicy) diff --git a/skype/skype-ps/skype/Get-CsTeamsCallParkPolicy.md b/teams/teams-ps/teams/Get-CsTeamsCallParkPolicy.md similarity index 91% rename from skype/skype-ps/skype/Get-CsTeamsCallParkPolicy.md rename to teams/teams-ps/teams/Get-CsTeamsCallParkPolicy.md index c73ad3880a..e9b195959d 100644 --- a/skype/skype-ps/skype/Get-CsTeamsCallParkPolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsCallParkPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamscallparkpolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscallparkpolicy +applicable: Microsoft Teams title: Get-CsTeamsCallParkPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsCallParkPolicy @@ -106,14 +106,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Get-CsTeamsCallingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsCallingPolicy.md new file mode 100644 index 0000000000..44a936109d --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsCallingPolicy.md @@ -0,0 +1,108 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscallingpolicy +applicable: Microsoft Teams +title: Get-CsTeamsCallingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsTeamsCallingPolicy + +## SYNOPSIS + +Returns information about the teams calling policies configured for use in your organization. +Teams calling policies help determine which users are able to use calling functionality within Microsoft Teams. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsCallingPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsCallingPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION + +Returns information about the teams calling policies configured for use in your organization. +Teams calling policies help determine which users are able to use calling functionality within Microsoft Teams and interoperability with Skype for Business. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsTeamsCallingPolicy -Identity SalesCallingPolicy +``` + +Retrieves the calling policy with the Identity "SalesCallingPolicy". + +### Example 2 +```powershell +Get-CsTeamsCallingPolicy -Filter "tag:Sales*" +``` + +Retrieves the calling policies with Identity starting with Sales. + +## PARAMETERS + +### -Identity +Specify the TeamsCallingPolicy that you would like to retrieve. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. +To return a collection of all the per-user policies, use this syntax: -Filter "tag:*". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallingpolicy) + +[Remove-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallingpolicy) + +[Grant-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallingpolicy) + +[New-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallingpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsChannelsPolicy.md b/teams/teams-ps/teams/Get-CsTeamsChannelsPolicy.md new file mode 100644 index 0000000000..444867452e --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsChannelsPolicy.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamschannelspolicy +applicable: Microsoft Teams +title: Get-CsTeamsChannelsPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsTeamsChannelsPolicy + +## SYNOPSIS + +The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsChannelsPolicy [[-Identity] <XdsIdentity>] [-LocalStore] [-Tenant <System.Guid>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsChannelsPolicy [-Filter <String>] [-LocalStore] [-Tenant <System.Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. The Get-CsTeamsChannelsPolicy returns policies that are available for use within your organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsChannelsPolicy +``` + +Retrieves all policies related to Teams & Channels that are available in your organization. + +## PARAMETERS + +### -Identity +Specify the unique name of a policy you would like to retrieve. Use one of the following values: + +- `Global` +- The name of a custom policy you've created. If the value contains spaces, enclose the value in quotation marks ("). Note that the Identity value shows as `Tag:<Name>`, but the `<Name>` value also works. +- `Default`: This is a template that's used to populate the default property values when you create a new policy or to reset the property values in the global policy in case you delete it. Note that the Identity value shows as `Tag:Default`, but the `Default` value also works. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. For example, to return a collection of all the per-user policies, use this syntax: -Filter "tag:". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Internal Microsoft use only. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsClientConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsClientConfiguration.md similarity index 90% rename from skype/skype-ps/skype/Get-CsTeamsClientConfiguration.md rename to teams/teams-ps/teams/Get-CsTeamsClientConfiguration.md index 0c36fa8cfe..8ade0c1ba8 100644 --- a/skype/skype-ps/skype/Get-CsTeamsClientConfiguration.md +++ b/teams/teams-ps/teams/Get-CsTeamsClientConfiguration.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsclientconfiguration -applicable: Skype for Business Online -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsclientconfiguration +applicable: Microsoft Teams +Module Name: MicrosoftTeams title: Get-CsTeamsClientConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsClientConfiguration @@ -106,14 +106,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/skype/skype-ps/skype/Get-CsTeamsComplianceRecordingApplication.md b/teams/teams-ps/teams/Get-CsTeamsComplianceRecordingApplication.md similarity index 81% rename from skype/skype-ps/skype/Get-CsTeamsComplianceRecordingApplication.md rename to teams/teams-ps/teams/Get-CsTeamsComplianceRecordingApplication.md index e49526406c..a480bcadfc 100644 --- a/skype/skype-ps/skype/Get-CsTeamsComplianceRecordingApplication.md +++ b/teams/teams-ps/teams/Get-CsTeamsComplianceRecordingApplication.md @@ -1,192 +1,194 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication -applicable: Skype for Business Online -title: Get-CsTeamsComplianceRecordingApplication -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# Get-CsTeamsComplianceRecordingApplication - -## SYNOPSIS -Returns information about the application instances of policy-based recording applications that have been configured for administering automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Filter <String>] - [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -Policy-based recording applications are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. - -Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. - -Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -Note that if neither the Identity nor the Filter parameters are specified, then Get-CsTeamsComplianceRecordingApplication returns all application instances of policy-based recording applications that are associated with a Teams recording policy. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. -Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingApplication -``` - -The command shown in Example 1 returns information for all the application instances of policy-based recording applications associated with Teams recording policies. - -### Example 2 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144' -``` - -In Example 2, information is returned for a single application instance of a policy-based recording application with the Identity Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144. - -### Example 3 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingApplication -Filter 'Tag:*' -``` - -The command shown in Example 3 returns all the application instances associated with Teams recording policies at the per-user scope. -To do this, the command uses the Filter parameter and the filter value "Tag:\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "Tag:". - -### Example 4 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingApplication -Filter 'Tag:ContosoPartnerComplianceRecordingPolicy*' -``` - -The command shown in Example 4 returns all the application instances associated with Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. -To do this, the command uses the Filter parameter and the filter value "Tag:ContosoPartnerComplianceRecordingPolicy\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "Tag:ContosoPartnerComplianceRecordingPolicy". - -## PARAMETERS - -### -Filter -Enables you to use wildcards when retrieving one or more application instances of policy-based recording applications. -For example, to return all the application instances associated with Teams recording policies at the per-user scope, use this syntax: - --Filter "Tag:\*" - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: True -``` - -### -Identity -Unique identifier of the application instance of a policy-based recording application to be retrieved. - -You cannot use wildcard characters when specifying the Identity. - -Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication +applicable: Microsoft Teams +title: Get-CsTeamsComplianceRecordingApplication +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# Get-CsTeamsComplianceRecordingApplication + +## SYNOPSIS +Returns information about the application instances of policy-based recording applications that have been configured for administering automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Filter <String>] + [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +Policy-based recording applications are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. + +Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. + +Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +Note that if neither the Identity nor the Filter parameters are specified, then Get-CsTeamsComplianceRecordingApplication returns all application instances of policy-based recording applications that are associated with a Teams recording policy. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. +Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingApplication +``` + +The command shown in Example 1 returns information for all the application instances of policy-based recording applications associated with Teams recording policies. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144' +``` + +In Example 2, information is returned for a single application instance of a policy-based recording application with the Identity Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144. + +### Example 3 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingApplication -Filter 'Tag:*' +``` + +The command shown in Example 3 returns all the application instances associated with Teams recording policies at the per-user scope. +To do this, the command uses the Filter parameter and the filter value "Tag:\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "Tag:". + +### Example 4 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingApplication -Filter 'Tag:ContosoPartnerComplianceRecordingPolicy*' +``` + +The command shown in Example 4 returns all the application instances associated with Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. +To do this, the command uses the Filter parameter and the filter value "Tag:ContosoPartnerComplianceRecordingPolicy\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "Tag:ContosoPartnerComplianceRecordingPolicy". + +## PARAMETERS + +### -Filter +Enables you to use wildcards when retrieving one or more application instances of policy-based recording applications. +For example, to return all the application instances associated with Teams recording policies at the per-user scope, use this syntax: + +-Filter "Tag:\*" + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -Identity +Unique identifier of the application instance of a policy-based recording application to be retrieved. + +You cannot use wildcard characters when specifying the Identity. + +Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/skype/skype-ps/skype/Get-CsTeamsComplianceRecordingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsComplianceRecordingPolicy.md similarity index 77% rename from skype/skype-ps/skype/Get-CsTeamsComplianceRecordingPolicy.md rename to teams/teams-ps/teams/Get-CsTeamsComplianceRecordingPolicy.md index 519132a8eb..a406247e81 100644 --- a/skype/skype-ps/skype/Get-CsTeamsComplianceRecordingPolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsComplianceRecordingPolicy.md @@ -1,187 +1,189 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy -applicable: Skype for Business Online -title: Get-CsTeamsComplianceRecordingPolicy -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# Get-CsTeamsComplianceRecordingPolicy - -## SYNOPSIS -Returns information about the policies configured for governing automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-LocalStore] [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Filter <String>] - [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -Teams recording policies are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. - -Note that if neither the Identity nor the Filter parameters are specified, then Get-CsTeamsComplianceRecordingPolicy returns all the Teams recording policies configured for use in the tenant. - -Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. -Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. - -Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. -The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. -Existing calls and meetings are unaffected. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingPolicy -``` - -The command shown in Example 1 returns information for all the Teams recording policies configured for use in the tenant. - -### Example 2 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -``` - -In Example 2, information is returned for a single Teams recording policy: the policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -### Example 3 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingPolicy -Filter 'Tag:*' -``` - -The command shown in Example 3 returns information about all the Teams recording policies configured at the per-user scope. -To do this, the command uses the Filter parameter and the filter value "Tag:\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "Tag:". - -## PARAMETERS - -### -Filter -Enables you to use wildcards when retrieving one or more Teams recording policies. -For example, to return all the policies configured at the per-user scope, use this syntax: - --Filter "Tag:\*" - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: True -``` - -### -Identity -Unique identifier of the Teams recording policy to be retrieved. -To return the global policy, use this syntax: - --Identity "Global" - -To return a policy configured at the per-user scope, use syntax like this: - --Identity "ContosoPartnerComplianceRecordingPolicy" - -You cannot use wildcard characters when specifying the Identity. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -LocalStore -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy +applicable: Microsoft Teams +title: Get-CsTeamsComplianceRecordingPolicy +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# Get-CsTeamsComplianceRecordingPolicy + +## SYNOPSIS +Returns information about the policies configured for governing automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Filter <String>] + [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +Teams recording policies are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. + +Note that if neither the Identity nor the Filter parameters are specified, then Get-CsTeamsComplianceRecordingPolicy returns all the Teams recording policies configured for use in the tenant. + +Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. +Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. + +Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. +The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. +Existing calls and meetings are unaffected. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingPolicy +``` + +The command shown in Example 1 returns information for all the Teams recording policies configured for use in the tenant. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' +``` + +In Example 2, information is returned for a single Teams recording policy: the policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +### Example 3 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingPolicy -Filter 'Tag:*' +``` + +The command shown in Example 3 returns information about all the Teams recording policies configured at the per-user scope. +To do this, the command uses the Filter parameter and the filter value "Tag:\*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "Tag:". + +## PARAMETERS + +### -Filter +Enables you to use wildcards when retrieving one or more Teams recording policies. +For example, to return all the policies configured at the per-user scope, use this syntax: + +-Filter "Tag:\*" + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -Identity +Unique identifier of the Teams recording policy to be retrieved. +To return the global policy, use this syntax: + +-Identity "Global" + +To return a policy configured at the per-user scope, use syntax like this: + +-Identity "ContosoPartnerComplianceRecordingPolicy" + +You cannot use wildcard characters when specifying the Identity. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/teams/teams-ps/teams/Get-CsTeamsCortanaPolicy.md b/teams/teams-ps/teams/Get-CsTeamsCortanaPolicy.md new file mode 100644 index 0000000000..e56310edf7 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsCortanaPolicy.md @@ -0,0 +1,129 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscortanapolicy +applicable: Microsoft Teams +title: Get-CsTeamsCortanaPolicy +schema: 2.0.0 +manager: amehta +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsTeamsCortanaPolicy + +## SYNOPSIS +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsCortanaPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsCortanaPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION + +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. Specifically, if a user can use Cortana voice assistant in Microsoft Teams and determines Cortana invocation behavior via CortanaVoiceInvocationMode parameter - + +* Disabled - Cortana voice assistant is disabled +* PushToTalkUserOverride - Cortana voice assistant is enabled but without wake-word ("Hey Cortana") invocation +* WakeWordPushToTalkUserOverride - Cortana voice assistant is enabled with wake-word ("Hey Cortana") invocation on devices where wake-word is supported + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsCortanaPolicy +``` +In the first example, the Get-CsTeamsCortanaPolicy cmdlet is called without specifying any additional parameters. This causes the Get-CsTeamsCortanaPolicy cmdlet to return a collection of all the Cortana voice assistant policies configured for use in your organization. + +## PARAMETERS + +### -Filter + +Enables you to use wildcards when specifying the policy (or policies) to be retrieved. For example, this syntax returns all the policies that have been configured at the site scope: -Filter "site:". This syntax returns all the policies that have been configured at the per-user scope: -Filter "tag:". +You cannot use both the Filter and the Identity parameters in the same command. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier for the policy to be returned. To return the global policy, use this syntax: -Identity global. To return a policy configured at the site scope, use syntax similar to this: -Identity "site:Redmond". To return a policy configured at the service scope, use syntax similar to this: -Identity "Registrar:atl-cs-001.litwareinc.com". + +Policies can also be configured at the per-user scope. To return one of these policies, use syntax similar to this: -Identity "SalesDepartmentPolicy". +If this parameter is not included then all of Cortana voice assistant policies configured for use in your organization will be returned. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore + +Retrieves the Cortana voice assistant policy data from the local replica of the Central Management store rather than from the Central Management store itself. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +Globally unique identifier (GUID) of the Skype for Business Online tenant account whose Cortana voice assistant policies are being returned. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsCustomBannerText.md b/teams/teams-ps/teams/Get-CsTeamsCustomBannerText.md new file mode 100644 index 0000000000..963877780a --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsCustomBannerText.md @@ -0,0 +1,79 @@ +--- +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscustombannertext +title: Get-CsTeamsCustomBannerText +schema: 2.0.0 +author: saleens7 +ms.author: wblocker +--- + +# Get-CsTeamsCustomBannerText + +## SYNOPSIS + +Enables administrators to configure a custom text on the banner displayed when compliance recording bots start recording the call. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsCustomBannerText [[-Identity] <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +Returns all or a single instance of custom banner text. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsCustomBannerText +``` + +This example gets the properties of all instances of the TeamsCustomBannerText. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsCustomBannerText -Identity CustomText +``` + +This example gets the properties of the CustomText instance of TeamsCustomBannerText. + +## PARAMETERS + +### -Identity +Policy instance name (optional). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/set-csteamscustombannertext) + +[New-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext) + +[Remove-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/remove-csteamscustombannertext) diff --git a/skype/skype-ps/skype/Get-CsTeamsEducationAssignmentsAppPolicy.md b/teams/teams-ps/teams/Get-CsTeamsEducationAssignmentsAppPolicy.md similarity index 89% rename from skype/skype-ps/skype/Get-CsTeamsEducationAssignmentsAppPolicy.md rename to teams/teams-ps/teams/Get-CsTeamsEducationAssignmentsAppPolicy.md index 314eaaf5cc..9a3a36317e 100644 --- a/skype/skype-ps/skype/Get-CsTeamsEducationAssignmentsAppPolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsEducationAssignmentsAppPolicy.md @@ -1,16 +1,16 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamseducationassignmentsapppolicy -applicable: Skype for Business Online -title: Set-CsTeamsEducationAssignmentsAppPolicy +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamseducationassignmentsapppolicy +applicable: Microsoft Teams +title: Get-CsTeamsEducationAssignmentsAppPolicy schema: 2.0.0 ms.reviewer: manager: bulenteg -ms.author: tomkau author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney --- - # Get-CsTeamsEducationAssignmentsAppPolicy ## SYNOPSIS @@ -106,14 +106,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Get-CsTeamsEducationConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsEducationConfiguration.md new file mode 100644 index 0000000000..09801a74c1 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsEducationConfiguration.md @@ -0,0 +1,94 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsEducationConfiguration +author: SaritaBehera +ms.author: saritabehera +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamseducationconfiguration +schema: 2.0.0 +--- + +# Get-CsTeamsEducationConfiguration + +## SYNOPSIS + +This cmdlet is used to retrieve the organization-wide education configuration for Teams. + +## SYNTAX + +### Identity (Default) +```powershell +Get-CsTeamsEducationConfiguration [-Identity <String>] [<CommonParameters>] +``` + +### Filter +```powershell +Get-CsTeamsEducationConfiguration [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet is used to retrieve the organization-wide education configuration for Teams which contains settings that are applicable to education organizations. + +You must be a Teams Service Administrator for your organization to run the cmdlet. + +## Examples + +### Example 1 +```powershell +PS C:\> Get-CsTeamsEducationConfiguration + +Identity : Global +ParentGuardianPreferredContactMethod : Email +UpdateParentInformation : Enabled +``` + +In this example, the organization has set the defaults as follows: + +- Email is set as the preferred contact method for the parent communication invites. +- Capability to edit parent contact information by educators is enabled. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters in order to return a collection of team education configuration settings. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The unique identifier of the configuration. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsEducationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamseducationconfiguration) diff --git a/teams/teams-ps/teams/Get-CsTeamsEmergencyCallRoutingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsEmergencyCallRoutingPolicy.md new file mode 100644 index 0000000000..82cff25140 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsEmergencyCallRoutingPolicy.md @@ -0,0 +1,107 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallroutingpolicy +applicable: Microsoft Teams +title: Get-CsTeamsEmergencyCallRoutingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc +schema: 2.0.0 +--- + +# Get-CsTeamsEmergencyCallRoutingPolicy + +## SYNOPSIS +This cmdlet returns one or more Emergency Call Routing policies. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsEmergencyCallRoutingPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsEmergencyCallRoutingPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet returns one or more Emergency Call Routing policies. This policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsTeamsEmergencyCallRoutingPolicy +``` + +Retrieves all emergency call routing policies that are available in your scope. + +### Example 2 +```powershell +Get-CsTeamsEmergencyCallRoutingPolicy -Identity TestECRP +``` + +Retrieves one emergency call routing policy specifying the identity. + +### Example 3 +```powershell +Get-CsTeamsEmergencyCallRoutingPolicy -Filter 'Test*' +``` + +Retrieves all emergency call routing policies with identity starting with Test. + +## PARAMETERS + +### -Identity +Specify the policy that you would like to retrieve. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter + Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallroutingpolicy) + +[Set-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallroutingpolicy) + +[Grant-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallroutingpolicy) + +[Remove-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallroutingpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsEmergencyCallingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsEmergencyCallingPolicy.md new file mode 100644 index 0000000000..2bae2ad08c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsEmergencyCallingPolicy.md @@ -0,0 +1,126 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallingpolicy +applicable: Microsoft Teams +title: Get-CsTeamsEmergencyCallingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc +schema: 2.0.0 +--- + +# Get-CsTeamsEmergencyCallingPolicy + +## SYNOPSIS + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsEmergencyCallingPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsEmergencyCallingPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet returns one or more emergency calling policies. Emergency calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsTeamsEmergencyCallingPolicy +``` + +Retrieves all emergency calling policies that are available in your scope. + +### Example 2 +```powershell +Get-CsTeamsEmergencyCallingPolicy -Identity TestECP +``` + +Retrieves an emergency calling policy with the identity TestECP + +### Example 3 +```powershell +Get-CsTeamsEmergencyCallingPolicy -Filter Test* +``` + +Retrieves all emergency calling policies with Identity starting with Test. + +### Example 4 +```powershell +(Get-CsTeamsEmergencyCallingPolicy -Identity TestECP).ExtendedNotifications +``` +```output +EmergencyDialString : 112 +NotificationGroup : alert2@contoso.com +NotificationDialOutNumber : +NotificationMode : ConferenceUnMuted + +EmergencyDialString : 911 +NotificationGroup : alert3@contoso.com +NotificationDialOutNumber : +14255551234 +NotificationMode : NotificationOnly +``` + +This example displays extended notifications set on emergency calling policy with the identity TestECP. + +## PARAMETERS + +### -Identity +Specify the policy that you would like to retrieve. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +The Filter parameter allows you to limit the number of results based on filters on Identity you specify. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingpolicy) + +[Grant-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallingpolicy) + +[Remove-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallingpolicy) + +[Set-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallingpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsEnhancedEncryptionPolicy.md b/teams/teams-ps/teams/Get-CsTeamsEnhancedEncryptionPolicy.md new file mode 100644 index 0000000000..d1c2fd903d --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsEnhancedEncryptionPolicy.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsenhancedencryptionpolicy +title: Get-CsTeamsEnhancedEncryptionPolicy +author: serdarsoysal +ms.author: serdars +manager: mdress +schema: 2.0.0 +--- + +# Get-CsTeamsEnhancedEncryptionPolicy + +## SYNOPSIS +Returns information about the teams enhanced encryption policies configured for use in your organization. +## SYNTAX + +``` +Get-CsTeamsEnhancedEncryptionPolicy [-LocalStore] [[-Identity] <Object>] [-Filter <Object>] + [<CommonParameters>] +``` + +## DESCRIPTION +Returns information about the Teams enhanced encryption policies configured for use in your organization. +The TeamsEnhancedEncryptionPolicy enables administrators to determine which users in your organization can use the enhanced encryption settings in Teams, setting for End-to-end encryption in ad-hoc 1-to-1 VOIP calls is the parameter supported by this policy currently. + +## EXAMPLES + +### EXAMPLE 1 +```PowerShell +PS C:\> Get-CsTeamsEnhancedEncryptionPolicy +``` + +The command shown in Example 1 returns information for all the teams enhanced encryption policies configured for use in the tenant. + +### EXAMPLE 2 +```PowerShell +PS C:\> Get-CsTeamsEnhancedEncryptionPolicy -Identity 'ContosoPartnerEnhancedEncryptionPolicy' +``` + +In Example 2, information is returned for a single teams enhanced encryption policy: the policy with the Identity ContosoPartnerEnhancedEncryptionPolicy. + +## PARAMETERS + +### -LocalStore +Internal Microsoft use only. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the Teams enhanced encryption policy. + +Use the "Global" Identity if you wish to retrieve the policy set for the entire tenant. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +If you don't know what policies have been pre-constructed, you can use filter to identify all policies available. This is a regex string against the name (Identity) of the pre-constructed policies. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsenhancedencryptionpolicy) + +[Set-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsenhancedencryptionpolicy) + +[Remove-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsenhancedencryptionpolicy) + +[Grant-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsenhancedencryptionpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsEventsPolicy.md b/teams/teams-ps/teams/Get-CsTeamsEventsPolicy.md new file mode 100644 index 0000000000..db497af1ae --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsEventsPolicy.md @@ -0,0 +1,90 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamseventspolicy +title: Get-CsTeamsEventsPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsEventsPolicy + +## SYNOPSIS +Returns information about the Teams Events policy. Note that this policy is currently still in preview. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsEventsPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsEventsPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Returns information about the Teams Events policy. TeamsEventsPolicy is used to configure options for customizing Teams Events experiences. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsEventsPolicy +``` + +Returns information for all Teams Events policies available for use in the tenant. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsEventsPolicy -Identity Global +``` + +Returns information for Teams Events policy with identity "Global". + +## PARAMETERS + +### -Filter +Enables using wildcards when specifying the policy (or policies) to be retrieved. Note that you cannot use both the Filter and the Identity parameters in the same command. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the Teams Events policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsExternalAccessConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsExternalAccessConfiguration.md new file mode 100644 index 0000000000..ca976fe3ca --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsExternalAccessConfiguration.md @@ -0,0 +1,83 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsexternalaccessconfiguration +title: Get-CsTeamsExternalAccessConfiguration +schema: 2.0.0 +--- + +# Get-CsTeamsExternalAccessConfiguration + +## SYNOPSIS +The TeamsExternalAccessConfiguration contains all configurations that can be used to enhance the security of the entire organization, such as managing blocked users. This cmdlet returns the current settings of your organization. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsExternalAccessConfiguration [[-Identity] <XdsIdentity>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsExternalAccessConfiguration [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Retrieves the current Teams External Access Configuration in the organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsExternalAccessConfiguration +``` + +In this example, we retrieve the Teams External Access Configuration in the organization. + +## PARAMETERS + +### -Filter +Internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The only value accepted is Global + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsExternalAccessConfiguration.Cmdlets.TeamsExternalAccessConfiguration + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsFeedbackPolicy.md b/teams/teams-ps/teams/Get-CsTeamsFeedbackPolicy.md new file mode 100644 index 0000000000..5000645a03 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsFeedbackPolicy.md @@ -0,0 +1,88 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsfeedbackpolicy +applicable: Microsoft Teams +title: Get-CsTeamsFeedbackPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: +--- + +# Get-CsTeamsFeedbackPolicy + +## SYNOPSIS + +Use this cmdlet to retrieve the current Teams Feedback policies (the ability to send feedback about Teams to Microsoft and whether they receive the survey) in the organization. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsFeedbackPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsFeedbackPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Retrieves the current Teams Feedback policies (the ability to send feedback about Teams to Microsoft and whether they receive the survey) in the organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsFeedbackPolicy +``` + +In this example, we retrieve all the existing Teams feedback policies in the organization. + +## PARAMETERS + +### -Identity +The unique identifier of the policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Internal Microsoft use + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsFilesPolicy.md b/teams/teams-ps/teams/Get-CsTeamsFilesPolicy.md new file mode 100644 index 0000000000..0340a280a1 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsFilesPolicy.md @@ -0,0 +1,110 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsfilespolicy +title: Get-CsTeamsFilesPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsFilesPolicy + +## SYNOPSIS +Use the \`Get-CsTeamsFilesPolicy\` cmdlet to get a list of all pre-configured policy instances related to teams files. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsFilesPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsFilesPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet retrieves information about one or more teams files policies that have been configured for use in your organization. +teams files policies are used by the organization to manage files-related features such as third party storage provider for files from teams. + +## EXAMPLES + +### Example 1 +``` +Get-CsTeamsFilesPolicy +``` + +In Example 1, the Get-CsTeamsFilesPolicy cmdlet is called without any additional parameters; this returns a collection of all the teams files policies configured for use in your organization. + +### Example 2 +``` +Get-CsTeamsFilesPolicy -Identity TranscriptionDisabled +``` + +In Example 2, the Get-CsTeamsFilesPolicy cmdlet is used to return the per-user teams files policy that has an Identity TranscriptionDisabled. +Because identities are unique, this command will never return more than one item. + +### Example 3 +``` +Get-CsTeamsFilesPolicy -Filter "tag:*" +``` + +Example 3 uses the Filter parameter to return all the teams files policies that have been configured at the per-user scope. +The filter value "tag:*" tells the Get-CsTeamsFilesPolicy cmdlet to return only those policies that have an Identity that begins with the string value "tag:". + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. +If this parameter is omitted, all teams files policies available for use are returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +This parameter accepts a wildcard string and returns all teams files policies with identities matching that string. +For example, a Filter value of Tag:* will return all preconfigured teams files policy instances (excluding forest default "Global") available to use by the tenant admins. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsfilespolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsFirstPartyMeetingTemplateConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsFirstPartyMeetingTemplateConfiguration.md new file mode 100644 index 0000000000..274a3a8171 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsFirstPartyMeetingTemplateConfiguration.md @@ -0,0 +1,84 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsTeamsFirstPartyMeetingTemplateConfiguration +title: Get-CsTeamsFirstPartyMeetingTemplateConfiguration +schema: 2.0.0 +author: boboPD +ms.author: pradas +--- + +# Get-CsTeamsFirstPartyMeetingTemplateConfiguration + +## SYNOPSIS +This cmdlet fetches the first-party meeting templates stored on the tenant. + +## SYNTAX + +```powershell +Get-CsTeamsFirstPartyMeetingTemplateConfiguration [[-Identity] <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Fetches the list of first-party templates on the tenant. Each template object contains its list of meeting options, the name of the template, and its ID. + +This is a read-only configuration. + +## EXAMPLES + +### Example 1 - Fetching all first party meeting templates on the tenant + +```powershell +PS C:\> Get-CsTeamsFirstPartyMeetingTemplateConfiguration + +Identity : Global +TeamsMeetingTemplates : {default, firstparty_30d773c0-1b4e-4bf6-970b-73f544c054bb, + firstparty_399f69a3-c482-41bf-9cf7-fcdefe269ce6, + firstparty_64c92390-c8a2-471e-96d9-4ee8f6080155...} +Description : The `TeamsMeetingTemplates` property contains the meeting template details: + +TeamsMeetingOptions : {SelectedSensitivityLabel, AutoAdmittedUsers, AllowPstnUsersToBypassLobby, + EntryExitAnnouncementsEnabled...} +Description : Townhall +Name : firstparty_21f91ef7-6265-4064-b78b-41ab66889d90 +Category : + +TeamsMeetingOptions : {AutoRecordingEnabled, AllowMeetingChat, PresenterOption} +Description : Virtual appointment +Name : firstparty_e514e598-fba6-4e1f-b8b3-138dd3bca748 +Category : +``` + +Fetches all the first-party templates on the tenant. + +## PARAMETERS + +### -Identity + +This parameter can be used to fetch a specific instance of the configuration. + +Note: This configuration is read only and will only have the Global instance. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsTeamsMeetingTemplateConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingtemplateconfiguration) diff --git a/skype/skype-ps/skype/Get-CsTeamsGuestCallingConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsGuestCallingConfiguration.md similarity index 88% rename from skype/skype-ps/skype/Get-CsTeamsGuestCallingConfiguration.md rename to teams/teams-ps/teams/Get-CsTeamsGuestCallingConfiguration.md index 5f0314b9f8..c14d3fbeec 100644 --- a/skype/skype-ps/skype/Get-CsTeamsGuestCallingConfiguration.md +++ b/teams/teams-ps/teams/Get-CsTeamsGuestCallingConfiguration.md @@ -1,12 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsguestcallingconfiguration +Module Name: MicrosoftTeams title: Get-CsTeamsGuestCallingConfiguration schema: 2.0.0 -manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +manager: bulenteg +ms.reviewer: --- # Get-CsTeamsGuestCallingConfiguration @@ -39,7 +40,7 @@ Returns information about the GuestCallingConfiguration, which specifies what op Get-CsTeamsGuestCallingConfiguration ``` -Returns the results +Returns the results ## PARAMETERS @@ -104,15 +105,16 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None + ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsGuestMeetingConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsGuestMeetingConfiguration.md similarity index 85% rename from skype/skype-ps/skype/Get-CsTeamsGuestMeetingConfiguration.md rename to teams/teams-ps/teams/Get-CsTeamsGuestMeetingConfiguration.md index 7003688293..fb9aee778f 100644 --- a/skype/skype-ps/skype/Get-CsTeamsGuestMeetingConfiguration.md +++ b/teams/teams-ps/teams/Get-CsTeamsGuestMeetingConfiguration.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsguestmeetingconfiguration -applicable: Skype for Business Online -title: Get-CsTeamsGuestCallingConfiguration +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsguestmeetingconfiguration +applicable: Microsoft Teams +title: Get-CsTeamsGuestMeetingConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsGuestMeetingConfiguration @@ -107,15 +107,16 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None + ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsGuestMessagingConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsGuestMessagingConfiguration.md new file mode 100644 index 0000000000..c5dbf828bd --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsGuestMessagingConfiguration.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsguestmessagingconfiguration +applicable: Microsoft Teams +title: Get-CsTeamsGuestMessagingConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsTeamsGuestMessagingConfiguration + +## SYNOPSIS +TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. This cmdlet returns your organization's current settings. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [-Filter <String>] [-LocalStore] + [<CommonParameters>] +``` + +## DESCRIPTION +TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. + +## EXAMPLES + +### Example 1 +``` +Get-CsTeamsGuestMessagingConfiguration +``` + +The command shown in Example 1 returns teams guest messaging configuration information for the current tenant + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters in order to return a collection of tenant guest messaging configuration settings. +Because each tenant is limited to a single, global collection of guest messaging configuration settings there is no need to use the Filter parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the collection of tenant guest messaging configuration settings to be returned. +Because each tenant is limited to a single, global collection of guest messaging settings there is no need include this parameter when calling the cmdlet. +If you do choose to use the Identity parameter you must also include the Tenant parameter. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +This parameter is not used with Skype for Business Online. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsIPPhonePolicy.md b/teams/teams-ps/teams/Get-CsTeamsIPPhonePolicy.md new file mode 100644 index 0000000000..4df635ab40 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsIPPhonePolicy.md @@ -0,0 +1,109 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsipphonepolicy +applicable: Microsoft Teams +title: Get-CsTeamsIPPhonePolicy +author: tonywoodruff +ms.author: anwoodru +ms.reviewer: kponnus +manager: sandrao +schema: 2.0.0 +--- + +# Get-CsTeamsIPPhonePolicy + +## SYNOPSIS + +Get-CsTeamsIPPhonePolicy allows IT Admins to view policies for IP Phone experiences in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsIPPhonePolicy [[-Identity] <String>] + [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsIPPhonePolicy [-Filter <String>] + [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +## DESCRIPTION + +Returns information about the Teams IP Phone Policies configured for use in your organization. Teams IP phone policies enable you to configure the different sign-in experiences based upon the function the device is performing; example: common area phone. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsIPPhonePolicy -identity CommonAreaPhone +``` + +Retrieves the IP Phone Policy with name "CommonAreaPhone". + +## PARAMETERS + +### -Identity +Specify the unique name of the TeamsIPPhonePolicy that you would like to retrieve. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. To return a collection of all the policies, use this syntax: -Filter "tag:*". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +Internal Microsoft use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsMediaConnectivityPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMediaConnectivityPolicy.md new file mode 100644 index 0000000000..8c4debe867 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsMediaConnectivityPolicy.md @@ -0,0 +1,100 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Get-CsTeamsMediaConnectivityPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsTeamsMediaConnectivityPolicy +schema: 2.0.0 +author: lirunping-MSFT +ms.author: runli +--- + +# Get-CsTeamsMediaConnectivityPolicy + +## SYNOPSIS + +This cmdlet retrieves all Teams media connectivity policies for the current tenant. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsMediaConnectivityPolicy [-Identity <String>] [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsMediaConnectivityPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet retrieves all Teams media connectivity policies for the current tenant. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsMediaConnectivityPolicy + +Identity DirectConnection +-------- ---------------- +Tag:Test Enabled +``` + +This example retrieves the Teams media connectivity policies and shows the result as identity tag and "DirectConnection" value. + +## PARAMETERS + +### -Filter + +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the Teams Media Connectivity Policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmediaconnectivitypolicy) + +[Remove-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmediaconnectivitypolicy) + +[Set-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmediaconnectivitypolicy) + +[Grant-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmediaconnectivitypolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsMediaLoggingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMediaLoggingPolicy.md new file mode 100644 index 0000000000..85ecd6cb9c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsMediaLoggingPolicy.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmedialoggingpolicy +applicable: Microsoft Teams +title: Get-CsTeamsMediaLoggingPolicy +author: LeoKuhorev +ms.author: leokukharau +manager: shalages +schema: 2.0.0 +--- + +# Get-CsTeamsMediaLoggingPolicy + +## SYNOPSIS + +Returns information about the Teams Media Logging policy. + +## SYNTAX + +### Identity (Default) + +``` +Get-CsTeamsMediaLoggingPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter + +``` +Get-CsTeamsMediaLoggingPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +Returns information about the Teams Media Logging policy. +TeamsMediaLoggingPolicy allows administrators to enable media logging for users. When assigned, it will enable media logging for the user overriding other settings. After removing the policy, media logging setting will revert to the previous value. + +NOTES: +TeamsMediaLoggingPolicy has only one instance that is built into the system, so there is no corresponding New cmdlet. + +## EXAMPLES + +### EXAMPLE 1 + +```PowerShell +PS C:\> Get-CsTeamsMediaLoggingPolicy +``` + +Return information for all Teams Media Logging policies available for use in the tenant. + +### EXAMPLE 2 + +```PowerShell +PS C:\> Get-CsTeamsMediaLoggingPolicy -Identity Global +``` + +Return Teams Media Logging policy that is set for the entire tenant. + +## PARAMETERS + +### -Identity + +Unique identifier assigned to the Teams Media Logging policy. Note that Teams Media Logging policy has only one instance that has Identity "Enabled". + +Use the "Global" Identity if you wish to retrieve the policy set for the entire tenant. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -Filter + +Enables using wildcards when specifying the policy (or policies) to be retrieved. +Note that you cannot use both the Filter and the Identity parameters in the same command. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Grant-CsTeamsMediaLoggingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmedialoggingpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsMeetingBrandingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMeetingBrandingPolicy.md new file mode 100644 index 0000000000..d7a61ce63f --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsMeetingBrandingPolicy.md @@ -0,0 +1,104 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbrandingpolicy +schema: 2.0.0 +title: Get-CsTeamsMeetingBrandingPolicy +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: stanlythomas +--- + +# Get-CsTeamsMeetingBrandingPolicy + +## SYNOPSIS +The **CsTeamsMeetingBrandingPolicy** cmdlet enables administrators to control the appearance in meetings by defining custom backgrounds, logos, and colors. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsMeetingBrandingPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsMeetingBrandingPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +The `Get-CsTeamsMeetingBrandingPolicy` cmdlet enables you to return information about all the meeting branding policies that have been configured for use in your organization. + +## EXAMPLES + +### Return all branding policies +```powershell +PS C:\> Get-CsTeamsMeetingBrandingPolicy +``` + +In this example, the command returns a collection of all the teams meeting branding policies configured for use in your organization. + +### Return specified policy +```powershell +PS C:\> CsTeamsMeetingBrandingPolicy -Identity "policy test2" +``` + +In this example, the command returns the meeting branding policy that has an **Identity** `policy test 2`. Because identities are unique, this command will never return more than one item. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier of the policy to be returned. To refer to the global policy, use this syntax: `-Identity global`. If this parameter is omitted, then all the meeting branding policies configured for use in your organization will be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### TeamsMeetingBrandingPolicy.Cmdlets.TeamsMeetingBrandingPolicy + +## NOTES + +Available in Teams PowerShell Module 4.9.3 and later. + +## RELATED LINKS + +[Get-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbrandingpolicy) + +[Grant-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingbrandingpolicy) + +[New-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingbrandingpolicy) + +[Remove-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingbrandingpolicy) + +[Set-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbrandingpolicy) diff --git a/skype/skype-ps/skype/Get-CsTeamsMeetingBroadcastConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastConfiguration.md similarity index 88% rename from skype/skype-ps/skype/Get-CsTeamsMeetingBroadcastConfiguration.md rename to teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastConfiguration.md index b798852881..973021d356 100644 --- a/skype/skype-ps/skype/Get-CsTeamsMeetingBroadcastConfiguration.md +++ b/teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastConfiguration.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsmeetingbroadcastconfiguration -applicable: Skype for Business Online +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbroadcastconfiguration +applicable: Microsoft Teams title: Get-CsTeamsMeetingBroadcastConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsMeetingBroadcastConfiguration @@ -115,15 +115,16 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None + ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsMeetingBroadcastPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastPolicy.md similarity index 75% rename from skype/skype-ps/skype/Get-CsTeamsMeetingBroadcastPolicy.md rename to teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastPolicy.md index 1dd23b7000..0b2ca7c3cd 100644 --- a/skype/skype-ps/skype/Get-CsTeamsMeetingBroadcastPolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastPolicy.md @@ -1,22 +1,19 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsmeetingbroadcastpolicy -applicable: Skype for Business Online -title: Set-CsTeamsMeetingBroadcastPolicy +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbroadcastpolicy +applicable: Microsoft Teams +title: Get-CsTeamsMeetingBroadcastPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- - # Get-CsTeamsMeetingBroadcastPolicy ## SYNOPSIS -Get-CsTeamsMeetingBroadcastPolicy \[\[-Identity\] \<XdsIdentity\>\] \[-Tenant \<guid\>\] \[-LocalStore\] \[\<CommonParameters\>\] - -Get-CsTeamsMeetingBroadcastPolicy \[-Tenant \<guid\>\] \[-Filter \<string\>\] \[-LocalStore\] \[\<CommonParameters\>\] +User-level policy for tenant admin to configure meeting broadcast behavior for the broadcast event organizer. ## SYNTAX @@ -36,11 +33,23 @@ User-level policy for tenant admin to configure meeting broadcast behavior for t ## EXAMPLES +### Example 1 +``` +Get-CsTeamsMeetingBroadcastPolicy +``` +Returns all the Teams Meeting Broadcast policies. + +### Example 2 +``` +Get-CsTeamsMeetingBroadcastPolicy -Filter "Education_Teacher" +``` + +In this example, the -Filter parameter is used to return all the policies that match "Education_Teacher". ## PARAMETERS ### -Filter -Enables you to use wildcard characters when specifying the policy (or policies) to be returned. For example, this syntax returns all the policies configured at the per-user scope +Enables you to use wildcard characters when specifying the policy (or policies) to be returned. ```yaml Type: String @@ -104,15 +113,16 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None + ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsMeetingConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsMeetingConfiguration.md similarity index 88% rename from skype/skype-ps/skype/Get-CsTeamsMeetingConfiguration.md rename to teams/teams-ps/teams/Get-CsTeamsMeetingConfiguration.md index 22b226a019..3cd9448904 100644 --- a/skype/skype-ps/skype/Get-CsTeamsMeetingConfiguration.md +++ b/teams/teams-ps/teams/Get-CsTeamsMeetingConfiguration.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsmeetingconfiguration -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingconfiguration +applicable: Microsoft Teams title: Get-CsTeamsMeetingConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsMeetingConfiguration @@ -112,8 +112,7 @@ Accept wildcard characters: False ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/skype/skype-ps/skype/Get-CsTeamsMeetingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMeetingPolicy.md similarity index 78% rename from skype/skype-ps/skype/Get-CsTeamsMeetingPolicy.md rename to teams/teams-ps/teams/Get-CsTeamsMeetingPolicy.md index 542b8a678a..3679deb1f5 100644 --- a/skype/skype-ps/skype/Get-CsTeamsMeetingPolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsMeetingPolicy.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsmeetingpolicy -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingpolicy +applicable: Microsoft Teams title: Get-CsTeamsMeetingPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsMeetingPolicy @@ -37,15 +37,14 @@ The Get-CsTeamsMeetingPolicy cmdlet enables you to return information about all ## EXAMPLES ### -------------------------- Example 1 -------------------------- -``` +```powershell Get-CsTeamsMeetingPolicy ``` In Example 1, Get-CsTeamsMeetingPolicy is called without any additional parameters; this returns a collection of all the teams meeting policies configured for use in your organization. - ### -------------------------- Example 2 -------------------------- -``` +```powershell Get-CsTeamsMeetingPolicy -Identity SalesPolicy ``` @@ -53,7 +52,7 @@ In Example 2, Get-CsTeamsMeetingPolicy is used to return the per-user meeting po Because identities are unique, this command will never return more than one item. ### -------------------------- Example 3 -------------------------- -``` +```powershell Get-CsTeamsMeetingPolicy | Where-Object {$_.AllowMeetNow -eq $True} ``` @@ -61,6 +60,18 @@ The preceding command returns a collection of all the meeting policies where the To do this, Get-CsTeamsMeetingPolicy is first called without any parameters in order to return a collection of all the policies configured for use in the organization. This collection is then piped to the Where-Object cmdlet, which selects only those policies where the AllowMeetNow property is equal to True. +### -------------------------- Example 4 -------------------------- +```powershell +Get-CsTeamsMeetingPolicy -Identity Global | fl NewMeetingRecordingExpirationDays +``` + +```Output +NewMeetingRecordingExpirationDays : 60 +``` + +The above command returns expiration date setting currently applied on TMR. For more details, see: +[Auto-expiration of Teams meeting recordings](https://learn.microsoft.com/microsoftteams/cloud-recording#auto-expiration-of-teams-meeting-recordings). + ## PARAMETERS ### -Filter @@ -122,25 +133,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +### 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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object @@ -148,4 +147,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-CsTeamsMeetingTemplateConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsMeetingTemplateConfiguration.md new file mode 100644 index 0000000000..f5121f5202 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsMeetingTemplateConfiguration.md @@ -0,0 +1,82 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsMeetingTemplateConfiguration +author: boboPD +ms.author: pradas +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsTeamsMeetingTemplateConfiguration +schema: 2.0.0 +--- + +# Get-CsTeamsMeetingTemplateConfiguration + +## SYNOPSIS +This cmdlet fetches the custom meeting templates stored on the tenant. + +## SYNTAX + +```powershell +Get-CsTeamsMeetingTemplateConfiguration [[-Identity] <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Fetches the list of custom templates on the tenant. Each template object contains its list of meeting options, the name of the template, and its ID. + +## EXAMPLES + +### Example 1 - Fetching all custom meeting templates on the tenant + +```powershell +PS C:\> Get-CsTeamsMeetingTemplateConfiguration + +Identity : Global +TeamsMeetingTemplates : {default, customtemplate_1cb7073a-8b19-4b5d-a3a6-14737d006969, + customtemplate_21ecf22c-eb1a-4f05-93e0-555b994ebeb5, + customtemplate_0b9c1f57-01ec-4b8a-b4c2-08bd1c01e6ba...} +Description : The `TeamsMeetingTemplates` property contains the meeting template details: + +TeamsMeetingOptions : {SelectedSensitivityLabel, AutoAdmittedUsers, AllowPstnUsersToBypassLobby, + EntryExitAnnouncementsEnabled...} +Description : Custom Template 1 +Name : customtemplate_1cb7073a-8b19-4b5d-a3a6-14737d006969 +Category : + +TeamsMeetingOptions : {AutoRecordingEnabled, AllowMeetingChat, PresenterOption} +Description : Custom Template 2 +Name : customtemplate_21ecf22c-eb1a-4f05-93e0-555b994ebeb5 +Category : +``` + +Fetches all the custom templates on the tenant. + +## PARAMETERS + +### -Identity + +This parameter can be used to fetch a specific instance of the configuration. + +Note: This configuration is read only and will only have the Global instance. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsTeamsFirstPartyMeetingTemplateConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsfirstpartymeetingtemplateconfiguration) diff --git a/teams/teams-ps/teams/Get-CsTeamsMeetingTemplatePermissionPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMeetingTemplatePermissionPolicy.md new file mode 100644 index 0000000000..22af122659 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsMeetingTemplatePermissionPolicy.md @@ -0,0 +1,133 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsMeetingTemplatePermissionPolicy +author: boboPD +ms.author: pradas +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsTeamsMeetingTemplatePermissionPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsMeetingTemplatePermissionPolicy + +## SYNOPSIS +Fetches the TeamsMeetingTemplatePermissionPolicy. This policy can be used to hide meeting templates from users and groups. + +## SYNTAX + +### Identity +```powershell +Get-CsTeamsMeetingTemplatePermissionPolicy [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +```powershell +Get-CsTeamsMeetingTemplatePermissionPolicy [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Fetches the instances of the policy. Each policy object contains a property called `HiddenMeetingTemplates`.This array contains the list of meeting template IDs that will be hidden by that instance of the policy. + +## EXAMPLES + +### Example 1 - Fetching all policies + +```powershell +PS C:\> Get-CsTeamsMeetingTemplatePermissionPolicy + +Identity : Global +HiddenMeetingTemplates : {} +Description : + +Identity : Tag:Foobar +HiddenMeetingTemplates : {customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056} +Description : + +Identity : Tag:dashbrd test +HiddenMeetingTemplates : {customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056} +Description : test + +Identity : Tag:Default +HiddenMeetingTemplates : {} +Description : +``` + +Fetches all the policy instances currently available. + +### Example 2 - Fetching a specific policy using its identity + +```powershell +PS C:\> Get-CsTeamsMeetingTemplatePermissionPolicy -Identity Foobar + +Identity : Tag:Foobar +HiddenMeetingTemplates : {customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056} +Description : +``` + +Fetches an instance of a policy with known identity. + +### Example 3 - Fetching policies using regex + +```powershell +PS C:\> Get-CsTeamsMeetingTemplatePermissionPolicy -Filter *Foo* + +Identity : Tag:Foobar +HiddenMeetingTemplates : {customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056} +Description : +``` + +The `Filter` parameter can be used to fetch policy instances based on partial matches on Identity. + +Note: _The "Tag:" prefix can be ignored when specifying the identity._ + +## PARAMETERS + +### -Identity + +This parameter can be used to fetch a specific instance of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter + +This parameter can be used to fetch policy instances based on partial matches on the `Identity` field. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Set-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingtemplatepermissionpolicy) + +[New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy) + +[Remove-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingtemplatepermissionpolicy) + +[Grant-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingtemplatepermissionpolicy) diff --git a/skype/skype-ps/skype/Get-CsTeamsMessagingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMessagingPolicy.md similarity index 80% rename from skype/skype-ps/skype/Get-CsTeamsMessagingPolicy.md rename to teams/teams-ps/teams/Get-CsTeamsMessagingPolicy.md index ac8dde21b9..8f998b1d2f 100644 --- a/skype/skype-ps/skype/Get-CsTeamsMessagingPolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsMessagingPolicy.md @@ -1,21 +1,19 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsmessagingpolicy -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmessagingpolicy +applicable: Microsoft Teams title: Get-CsTeamsMessagingPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsMessagingPolicy ## SYNOPSIS -Get-CsTeamsMessagingPolicy \[\[-Identity\] \<XdsIdentity\>\] \[-Tenant \<guid\>\] \[-LocalStore\] \[\<CommonParameters\>\] - -Get-CsTeamsMessagingPolicy \[-Tenant \<guid\>\] \[-Filter \<string\>\] \[-LocalStore\] \[\<CommonParameters\>\] +The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. ## SYNTAX @@ -107,25 +105,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -AsJob - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +### 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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object @@ -133,4 +119,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Get-CsTeamsMobilityPolicy.md b/teams/teams-ps/teams/Get-CsTeamsMobilityPolicy.md similarity index 87% rename from skype/skype-ps/skype/Get-CsTeamsMobilityPolicy.md rename to teams/teams-ps/teams/Get-CsTeamsMobilityPolicy.md index 41cb916cf8..3a147f9743 100644 --- a/skype/skype-ps/skype/Get-CsTeamsMobilityPolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsMobilityPolicy.md @@ -1,92 +1,89 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsmobilitypolicy -applicable: Skype for Business Online -title: Get-CsTeamsMobilityPolicy -schema: 2.0.0 -manager: ritikag -author: saragava -ms.author: saragava -ms.reviewer: ---- - - -# Get-CsTeamsMobilityPolicy - -## SYNOPSIS -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -## SYNTAX - -### Identity (Default) -``` -Get-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] - [<CommonParameters>] -``` - -### Filter -``` -Get-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] -``` - -## DESCRIPTION -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -The Get-CsTeamsMobilityPolicy cmdlet allows administrators to get all teams mobility policies. - -NOTE: Please note that this cmdlet was deprecated and then removed from this PowerShell module. This reference will continue to be listed here for legacy purposes. - - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-CsTeamsMobilityPolicy -``` -Retrieve all teams mobility policies that are available in your organization - -## PARAMETERS - -### -Filter -Enables you to use wildcard characters when indicating the policy (or policies) to be returned. For example, to return a collection of all the per-user policies, use this syntax: -Filter "tag:". - -```yaml -Type: String -Parameter Sets: Filter -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the unique name of a policy you would like to retrieve - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmobilitypolicy +applicable: Microsoft Teams +title: Get-CsTeamsMobilityPolicy +schema: 2.0.0 +manager: ritikag +ms.reviewer: ritikag +--- + +# Get-CsTeamsMobilityPolicy + +## SYNOPSIS +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +The Get-CsTeamsMobilityPolicy cmdlet allows administrators to get all teams mobility policies. + +NOTE: Please note that this cmdlet was deprecated and then removed from this PowerShell module. This reference will continue to be listed here for legacy purposes. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsMobilityPolicy +``` +Retrieve all teams mobility policies that are available in your organization + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. For example, to return a collection of all the per-user policies, use this syntax: -Filter "tag:". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the unique name of a policy you would like to retrieve + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsMultiTenantOrganizationConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsMultiTenantOrganizationConfiguration.md new file mode 100644 index 0000000000..73ca7780ac --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsMultiTenantOrganizationConfiguration.md @@ -0,0 +1,50 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Get-CsTeamsMultiTenantOrganizationConfiguration +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsmultitenantorganizationconfiguration +schema: 2.0.0 +author: samlyu +ms.author: samlyu +--- + +# Get-CsTeamsMultiTenantOrganizationConfiguration + +## SYNOPSIS + +This cmdlet retrieves all tenant settings for Multi-tenant Organizations + +## SYNTAX + +``` +Get-CsTeamsMultiTenantOrganizationConfiguration [<CommonParameters>] +``` + +## DESCRIPTION + +The Get-CsTeamsMultiTenantOrganizationConfiguration cmdlet enables Teams meeting administrators to retrieve the Multi-Tenant Organization settings for their tenant. This includes the *CopilotFromHomeTenant* field, which specifies whether users in a Multi-Tenant Organization are allowed to utilize their Copilot license from their home tenant during cross-tenant meetings. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsMultiTenantOrganizationConfiguration +``` + +Retrieves tenant's Multi-tenant Organization Configuration, including CopilotFromHomeTenant. + +## 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsMultiTenantOrganizationConfiguration](Set-CsTeamsMultiTenantOrganizationConfiguration.md) diff --git a/teams/teams-ps/teams/Get-CsTeamsNetworkRoamingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsNetworkRoamingPolicy.md new file mode 100644 index 0000000000..f098d86971 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsNetworkRoamingPolicy.md @@ -0,0 +1,123 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsnetworkroamingpolicy +applicable: Microsoft Teams +title: Get-CsTeamsNetworkRoamingPolicy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: +manager: mreddy +schema: 2.0.0 +--- + +# Get-CsTeamsNetworkRoamingPolicy + +## SYNOPSIS + +Get-CsTeamsNetworkRoamingPolicy allows IT Admins to view policies for the Network Roaming and Bandwidth Control experiences in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsNetworkRoamingPolicy [-Identity <String>] + [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsNetworkRoamingPolicy [-Filter <String>] + [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +Returns information about the Teams Network Roaming Policies configured for use in your organization. + +The TeamsNetworkRoamingPolicy cmdlets enable administrators to provide specific settings from the TeamsMeetingPolicy to be rendered dynamically based upon the location of the Teams client. The TeamsNetworkRoamingPolicy cannot be granted to a user but instead can be assigned to a network site. The settings from the TeamsMeetingPolicy included are AllowIPVideo and MediaBitRateKb. When a Teams client is connected to a network site where a CsTeamRoamingPolicy is assigned, these two settings from the TeamsRoamingPolicy will be used instead of the settings from the TeamsMeetingPolicy. + +More on the impact of bit rate setting on bandwidth can be found [here](https://learn.microsoft.com/microsoftteams/prepare-network). + +To enable the network roaming policy for users who are not Enterprise Voice enabled, you must also enable the AllowNetworkConfigurationSettingsLookup setting in TeamsMeetingPolicy. This setting is off by default. See Set-TeamsMeetingPolicy for more information on how to enable AllowNetworkConfigurationSettingsLookup for users who are not Enterprise Voice enabled. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsTeamsNetworkRoamingPolicy +``` + +In Example 1, Get-CsTeamsNetworkRoamingPolicy is called without any additional parameters; this returns a collection of all the teams network roaming policies configured for use in your organization. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Get-CsTeamsNetworkRoamingPolicy -Identity OfficePolicy +``` + +In Example 2, Get-CsTeamsNetworkRoamingPolicy is used to return the network roaming policy that has an Identity OfficePolicy. +Because identities are unique, this command will never return more than one item. + +## PARAMETERS + +### -Identity +Unique identifier of the policy to be returned. +If this parameter is omitted, then all the Teams Network Roaming Policies configured for use in your organization will be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +Internal Microsoft use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsNotificationAndFeedsPolicy.md b/teams/teams-ps/teams/Get-CsTeamsNotificationAndFeedsPolicy.md new file mode 100644 index 0000000000..95ac82e696 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsNotificationAndFeedsPolicy.md @@ -0,0 +1,100 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsnotificationandfeedspolicy +title: Get-CsTeamsNotificationAndFeedsPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsNotificationAndFeedsPolicy + +## SYNOPSIS +Retrieves information about the Teams Notification and Feeds policy configured for use in the tenant. + +## SYNTAX + +### Identity (Default) +```powershell +Get-CsTeamsNotificationAndFeedsPolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter +```powershell +Get-CsTeamsNotificationAndFeedsPolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +The Microsoft Teams notifications and feeds policy allows administrators to manage how notifications and activity feeds are handled within Teams. This policy includes settings that control the types of notifications users receive, how they are delivered, and which activities are highlighted in their feeds. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsNotificationAndFeedsPolicy +``` + +The command shown above returns information of all Teams NotificationAndFeedsPolicy that have been configured for use in the tenant. + +## PARAMETERS + +### -Filter +A filter that is not expressed in the standard wildcard language. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsRecordingRollOutPolicy.md b/teams/teams-ps/teams/Get-CsTeamsRecordingRollOutPolicy.md new file mode 100644 index 0000000000..f4c168932c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsRecordingRollOutPolicy.md @@ -0,0 +1,94 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsrecordingrolloutpolicy +schema: 2.0.0 +applicable: Microsoft Teams +title: Get-CsTeamsRecordingRollOutPolicy +manager: yujin1 +author: ronwa +ms.author: ronwa +--- + +# Get-CsTeamsRecordingRollOutPolicy + +## SYNOPSIS + +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsRecordingRollOutPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsRecordingRollOutPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. This policy would be deprecated over time as this is only to allow IT admins to phase the roll out of this breaking change. + +The Get-CsTeamsRecordingRollOutPolicy cmdlet enables you to return information about all the CsTeamsRecordingRollOutPolicy that have been configured for use in your organization. + +This command is available from Teams powershell module 6.1.1-preview and above. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsRecordingRollOutPolicy +``` + +In Example 1, Get-CsTeamsRecordingRollOutPolicy is called without any additional parameters; this returns a collection of all the CsTeamsRecordingRollOutPolicy configured for use in your organization. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier of the policy to be returned. To refer to the global policy, use this syntax: -Identity global. To refer to a per-user policy, use syntax similar to this: -Identity SalesDepartmentPolicy. +If this parameter is omitted, then all the meeting policies configured for use in your organization will be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsRecordingRollOutPolicy.Cmdlets.TeamsRecordingRollOutPolicy + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsRoomVideoTeleConferencingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsRoomVideoTeleConferencingPolicy.md new file mode 100644 index 0000000000..d0da8be66e --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsRoomVideoTeleConferencingPolicy.md @@ -0,0 +1,99 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsroomvideoteleconferencingpolicy +title: Get-CsTeamsRoomVideoTeleConferencingPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsRoomVideoTeleConferencingPolicy + +## SYNOPSIS + +Use this cmdlet to retrieve the current Teams Room Video TeleConferencing policies. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsRoomVideoTeleConferencingPolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsRoomVideoTeleConferencingPolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Room Video Teleconferencing Policy enables administrators to configure and manage video teleconferencing behavior for Microsoft Teams Rooms (meeting room devices). + +## PARAMETERS + +### -Filter + +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The name the tenant admin gave to the Policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsSettingsCustomApp.md b/teams/teams-ps/teams/Get-CsTeamsSettingsCustomApp.md new file mode 100644 index 0000000000..74dc4c20ca --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsSettingsCustomApp.md @@ -0,0 +1,83 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamssettingscustomapp +title: Get-CsTeamsSettingsCustomApp +schema: 2.0.0 +--- + +# Get-CsTeamsSettingsCustomApp + +## SYNOPSIS +Get the Custom Apps Setting's value of Teams Admin Center. + +## SYNTAX + +``` +Get-CsTeamsSettingsCustomApp [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +There is a switch for managing Custom Apps in the Org-wide app settings page of Teams Admin Center. The command can get the current value of this switch. If the switch is enabled, the custom apps can be uploaded as app packages and available in the organization's app store, vice versa. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsSettingsCustomApp + +IsSideloadedAppsInteractionEnabled +---------------------------------- + False +``` + +Get the value of Custom Apps Setting. The value in the example is False, so custom apps are unavailable in the organization's app store. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Set-CsTeamsSettingsCustomApp](https://learn.microsoft.com/powershell/module/teams/set-csteamssettingscustomapp) diff --git a/teams/teams-ps/teams/Get-CsTeamsSharedCallingRoutingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsSharedCallingRoutingPolicy.md new file mode 100644 index 0000000000..817189ce6e --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsSharedCallingRoutingPolicy.md @@ -0,0 +1,114 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamssharedcallingroutingpolicy +applicable: Microsoft Teams +title: Get-CsTeamsSharedCallingRoutingPolicy +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Get-CsTeamsSharedCallingRoutingPolicy + +## SYNOPSIS +Use the Get-CsTeamsSharedCallingRoutingPolicy cmdlet to get Teams shared calling routing policy information. +Teams shared calling routing policy is used to configure shared calling. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsSharedCallingRoutingPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsSharedCallingRoutingPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +TeamsSharedCallingRoutingPolicy is used to configure shared calling. + +## EXAMPLES + +### Example 1 +``` +Get-CsTeamsSharedCallingRoutingPolicy +``` +The command shown in Example 1 returns information for all the Teams shared calling routing policies configured for use in the organization. + +### Example 2 +``` +Get-CsTeamsSharedCallingRoutingPolicy -Identity "Seattle" +``` +In Example 2, information is returned for a single Teams shared calling routing policy; the policy with Identity Seattle. + +### Example 3 +``` +Get-CsTeamsSharedCallingRoutingPolicy -Filter "tag:*" +``` +The command shown in Example 3 returns information about all the Teams shared calling routing policies configured at the per-user scope. + +### Example 4 +``` +Get-CsTeamsSharedCallingRoutingPolicy -Identity Global +``` +The command shown in Example 4 returns information about the Global policy instance. + +## PARAMETERS + +### -Identity +Unique identifier of the Teams shared calling routing policy to be retrieved. + +You cannot use wildcard characters when specifying the Identity. If neither the Identity nor the Filter parameters are specified, then Get-CsTeamsSharedCallingRoutingPolicy +returns all the Teams shared calling routing policies configured for use in the organization. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. +To return a collection of all the per-user policies, use this syntax: -Filter "tag:*". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Set-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamssharedcallingroutingpolicy) + +[Grant-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamssharedcallingroutingpolicy) + +[Remove-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamssharedcallingroutingpolicy) + +[New-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamssharedcallingroutingpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsAppPolicy.md b/teams/teams-ps/teams/Get-CsTeamsShiftsAppPolicy.md new file mode 100644 index 0000000000..e669a7e816 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsAppPolicy.md @@ -0,0 +1,107 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsapppolicy +title: Get-CsTeamsShiftsAppPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsAppPolicy + +## SYNOPSIS + +Returns information about the Teams Shifts App policies that have been configured for use in your organization. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsShiftsAppPolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsShiftsAppPolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Shifts app is designed to help frontline workers and their managers manage schedules and communicate effectively. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-CsTeamsShiftsAppPolicy +``` + +Lists any available Teams Shifts Apps Policies. + +## PARAMETERS + +### -Filter + +This parameter accepts a wildcard string and returns all policies with identities matching that string. For example, a Filter value of tag:* will return all policies defined at the per-user level. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique Identity assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +{{ Fill MsftInternalProcessingMode Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnection.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnection.md new file mode 100644 index 0000000000..5bfed6ecbd --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnection.md @@ -0,0 +1,268 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnection +author: serdarsoysal +ms.author: serdars +manager: valk +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnection + +## SYNOPSIS +This cmdlet returns the list of existing workforce management (WFM) connections. It can also return the configuration details for a given WFM connection. + +## SYNTAX + +### Get (Default) +```powershell +Get-CsTeamsShiftsConnection [-Authorization <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### Get1 +```powershell +Get-CsTeamsShiftsConnection -ConnectionId <string> [-Authorization <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity +```powershell +Get-CsTeamsShiftsConnection -InputObject <IConfigApiBasedCmdletsIdentity> [-Authorization <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet returns the list of existing connections. It can also return the configuration details for a given connection. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnection | Format-List +``` +```output +ConnectorId : 6A51B888-FF44-4FEA-82E1-839401E00000 +ConnectorSpecificSettingAdminApiUrl : https://www.contoso.com/retail/data/wfmadmin/api/v1-beta3 +ConnectorSpecificSettingApiUrl : +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : +ConnectorSpecificSettingCookieAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingEssApiUrl : https://www.contoso.com/retail/data/wfmess/api/v1-beta2 +ConnectorSpecificSettingFederatedAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingRetailWebApiUrl : https://www.contoso.com/retail/data/retailwebapi/api/v1 +ConnectorSpecificSettingSiteManagerUrl : https://www.contoso.com/retail/data/wfmsm/api/v1-beta4 +ConnectorSpecificSettingSsoUrl : +CreatedDateTime : 24/03/2023 04:58:23 +Etag : "5b00dd1b-0000-0400-0000-641d2df00000" +Id : 4dae9db0-0841-412c-8d6b-f5684bfebdd7 +LastModifiedDateTime : 24/03/2023 04:58:23 +Name : My connection 1 +State : Active +TenantId : dfd24b34-ccb0-47e1-bdb7-000000000000 + +ConnectorId : 95BF2848-2DDA-4425-B0EE-D62AEED4C0A0 +ConnectorSpecificSettingAdminApiUrl : +ConnectorSpecificSettingApiUrl : https://www.contoso.com/api +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W +ConnectorSpecificSettingCookieAuthUrl : +ConnectorSpecificSettingEssApiUrl : +ConnectorSpecificSettingFederatedAuthUrl : +ConnectorSpecificSettingRetailWebApiUrl : +ConnectorSpecificSettingSiteManagerUrl : +ConnectorSpecificSettingSsoUrl : https://www.contoso.com/sso +CreatedDateTime : 06/04/2023 11:05:39 +Etag : "3100fd6e-0000-0400-0000-642ea7840000" +Id : a2d1b091-5140-4dd2-987a-98a8b5338744 +LastModifiedDateTime : 06/04/2023 11:05:39 +Name : My connection 2 +State : Active +TenantId : dfd24b34-ccb0-47e1-bdb7-000000000000 +``` + +Returns the list of connections. + +### Example 2 +```powershell +PS C:\> $connection = Get-CsTeamsShiftsConnection -ConnectionId a2d1b091-5140-4dd2-987a-98a8b5338744 +PS C:\> $connection.ToJsonString() +``` +```output +{ + "connectorSpecificSettings": { + "apiUrl": "https://www.contoso.com/api", + "ssoUrl": "https://www.contoso.com/sso", + "clientId": "Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W" + }, + "id": "a2d1b091-5140-4dd2-987a-98a8b5338744", + "tenantId": "dfd24b34-ccb0-47e1-bdb7-000000000000", + "connectorId": "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0", + "name": "My connection 2", + "etag": "\"3100fd6e-0000-0400-0000-642ea7840000\"", + "createdDateTime": "2023-04-06T11:05:39.8790000Z", + "lastModifiedDateTime": "2023-04-06T11:05:39.8790000Z", + "state": "Active" +} +``` +Returns the connection with the specified -ConnectionId. + +## PARAMETERS + +### -Break +Wait for .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId +The connection ID. + +```yaml +Type: String +Parameter Sets: Get1 +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Authorization +Used to provide the necessary credentials for authenticating and authorizing the connection to the workforce management (WFM) system. This parameter ensures that the connection has the appropriate permissions to access and manage the data within the WFM system. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IWfmConnectionResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[New-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnection) + +[Set-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnection) + +[Update-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/update-csteamsshiftsconnection) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md new file mode 100644 index 0000000000..b236e9c29c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md @@ -0,0 +1,69 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionConnector +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionconnector +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionConnector + +## SYNOPSIS + +This cmdlet supports retrieving the available Shifts Connectors. + +## SYNTAX + +``` +Get-CsTeamsShiftsConnectionConnector [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet shows the available list of Shifts Connectors that can be used to synchronize a third-party workforce management system with Teams and the types of data that can be synchronized. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionConnector | Format-List +``` +``` +Id : 6A51B888-FF44-4FEA-82E1-839401E9CD74 +Name : Contoso V1 +SupportedSyncScenarioOfferShiftRequest : {Disabled, FromWfmToShifts, TwoWay} +SupportedSyncScenarioOpenShift : {Disabled, FromWfmToShifts} +SupportedSyncScenarioOpenShiftRequest : {Disabled, FromWfmToShifts, TwoWay} +SupportedSyncScenarioShift : {Disabled, FromWfmToShifts} +SupportedSyncScenarioSwapRequest : {Disabled, FromWfmToShifts, TwoWay} +SupportedSyncScenarioTimeCard : {Disabled, FromWfmToShifts, TwoWay} +SupportedSyncScenarioTimeOff : {Disabled, FromWfmToShifts} +SupportedSyncScenarioTimeOffRequest : {Disabled, FromWfmToShifts, TwoWay} +SupportedSyncScenarioUserShiftPreference : {Disabled, FromWfmToShifts, TwoWay} +Version : 2020.3 - 2021.1 +``` +Get the list of Shifts Connectors available on the tenant. + +## 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnection) + +[New-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectioninstance) + +[Set-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnectioninstance) + +[Test-CsTeamsShiftsConnectionValidate](https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md new file mode 100644 index 0000000000..adf41720e0 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md @@ -0,0 +1,437 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionErrorReport +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionErrorReport + +## SYNOPSIS + +This cmdlet returns the list of all the team mapping error reports. It can also return the configuration details of one mapping error report with its ID provided or other filter parameters. + +## SYNTAX + +### Get (Default) +```powershell +Get-CsTeamsShiftsConnectionErrorReport [-Activeness <String>] [-After <String>] [-Before <String>] + [-Code <String>] [-ConnectionId <String>] [-ConnectorInstanceId <String>] [-Operation <String>] + [-Procedure <String>] [-TeamId <String>] [-Authorization <String>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### Get1 +```powershell +Get-CsTeamsShiftsConnectionErrorReport -ErrorReportId <String> [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity +```powershell +Get-CsTeamsShiftsConnectionErrorReport -InputObject <IConfigApiBasedCmdletsIdentity> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet returns the list of existing team mapping error reports. It can also return the configuration details for mapping result with given ID or other filters. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionErrorReport +``` +```output +Code ConnectionId CreatedAt Culture ErrorNotificationSent ErrorType Id IntermediateIncident Message +---- ------------ --------- ------- --------------------- --------- -- -------------------- ------- +WFMAuthError 30/09/2022 14:14:08 en-US False WFMAuthErrorMessageType 74091f69-29b7-4884-aab9-ee5d705f36e3 1042 The workforce management system account credentials you've ... +WFMAuthError 17/10/2022 19:42:15 en-US False WFMAuthErrorMessageType b0d04444-d80b-490a-a573-ae3bb7f871bc 40 The workforce management system account credentials you've ... +WFMAuthError 17/10/2022 20:27:31 en-US False WFMAuthErrorMessageType 91ca35d9-1abc-4ded-bcda-dbf58a155930 94 The workforce management system account credentials you've ... +GraphUserAuthError 18/10/2022 04:46:57 en-US False GraphUserAuthErrorMessageType 4d26df1c-7133-4477-9266-5d7ffb70aa88 0 Authentication failed. Ensure that you've entered valid cre... +UserMappingError 18/10/2022 04:47:15 en-US False UserMappingErrorMessageType 6a90b796-9cda-4cc9-a74c-499de91073f9 0 Mapping failed for some users: 3 succeeded, 0 failed AAD us... +BatchTeamMappingError 06/04/2023 15:24:22 en-US False BatchTeamMappingErrorMessageType bf1bc3ea-1e40-483b-b6cc-669f22f24c48 1 This designated actor profile doesn't have team ownership p... +``` + +Returns the list of all the error reports. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionErrorReport -ErrorReportId 74091f69-29b7-4884-aab9-ee5d705f36e3 | Format-List +``` +```output +Code : WFMAuthError +ConnectionId : +CreatedAt : 30/09/2022 14:14:08 +Culture : en-US +ErrorNotificationSent : False +ErrorType : WFMAuthErrorMessageType +Id : 74091f69-29b7-4884-aab9-ee5d705f36e3 +IntermediateIncident : 1042 +Message : The workforce management system account credentials you've provided are invalid or this account doesn't have the required permissions. +Operation : SyncSwapShiftRequestCommand +Parameter : +Procedure : ExecuteAsync +ReferenceLink : +ResolvedAt : +ResolvedNotificationSentOn : +RevisitIntervalInMinute : 1440 +RevisitedAt : +ScheduleSequenceNumber : 310673843 +Severity : Critical +TeamId : +TenantId : dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a +TotalIncident : 1042 +Ttl : 2505600 +WfmConnectorInstanceId : WCI-6f8eb424-c347-46b4-a50b-118af8d3d546 +``` + +Returns the error report with ID `18b3e490-e6ed-4c2e-9925-47e36609dff3`. + +### Example 3 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionErrorReport -Code UserMappingError +``` +```output +Code ConnectionId CreatedAt Culture ErrorNotificationSent ErrorType Id IntermediateIncident Message +---- ------------ --------- ------- --------------------- --------- -- -------------------- ------- +UserMappingError 18/10/2022 04:47:15 en-US False UserMappingErrorMessageType 6a90b796-9cda-4cc9-a74c-499de91073f9 0 Mapping failed for some users: 3 succeeded, 0 failed AAD user(s) and ... +UserMappingError 18/10/2022 04:47:28 en-US False UserMappingErrorMessageType 005c4a9d-552e-4ea1-9d6a-c0316d272bc9 0 Mapping failed for some users: 3 succeeded, 0 failed AAD user(s) and ... +UserMappingError 18/10/2022 04:48:25 en-US False UserMappingErrorMessageType 841e00b5-c4e5-4e24-89d2-703d79250516 0 Mapping failed for some users: 4 succeeded, 0 failed AAD user(s) and ... +UserMappingError 18/10/2022 04:54:05 en-US False UserMappingErrorMessageType 0e10d036-c071-4db2-9cac-22e520f929d9 0 Mapping failed for some users: 5 succeeded, 0 failed AAD user(s) and ... +``` + +Returns the error report with error code `UserMappingError`. + +### Example 4 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionErrorReport -Operation UserMappingHandler +``` +```output +Code ConnectionId CreatedAt Culture ErrorNotificationSent ErrorType Id IntermediateIncident Message +---- ------------ --------- ------- --------------------- --------- -- -------------------- ------- +UserMappingError 18/10/2022 04:47:15 en-US False UserMappingErrorMessageType 6a90b796-9cda-4cc9-a74c-499de91073f9 0 Mapping failed for some users: 3 succeeded, 0 failed AAD user(s) and ... +UserMappingError 18/10/2022 04:47:28 en-US False UserMappingErrorMessageType 005c4a9d-552e-4ea1-9d6a-c0316d272bc9 0 Mapping failed for some users: 3 succeeded, 0 failed AAD user(s) and ... +UserMappingError 18/10/2022 04:48:25 en-US False UserMappingErrorMessageType 841e00b5-c4e5-4e24-89d2-703d79250516 0 Mapping failed for some users: 4 succeeded, 0 failed AAD user(s) and ... +UserMappingError 18/10/2022 04:54:05 en-US False UserMappingErrorMessageType 0e10d036-c071-4db2-9cac-22e520f929d9 0 Mapping failed for some users: 5 succeeded, 0 failed AAD user(s) and ... +``` + +Returns the error report with operation `UserMappingHandler`. + +### Example 5 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionErrorReport -After 2022-12-12T19:11:39.073Z +``` +```output +Code ConnectionId CreatedAt Culture ErrorNotificationSent ErrorType Id IntermediateIncident Message +---- ------------ --------- ------- --------------------- --------- -- -------------------- ------- +UserMappingError 26/01/2023 14:42:27 en-US True UserMappingErrorMessageType d7ab9ab4-b60c-44d3-8c12-d8ee64a67ce8 172 Mapping failed for some users: 1 succeeded, 2 failed AAD us... +WFMAuthError 26/01/2023 16:08:31 en-US False WFMAuthErrorMessageType 7adc3e4e-124e-4613-855c-9ac1b338400a 1 The workforce management system account credentials you've ... +``` + +Returns the error report created after `2022-12-12T19:11:39.073Z`. + +## PARAMETERS + +### -ErrorReportId + +The ID of the error report. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Activeness + +The flag indicating results should have which activeness. +Set this to `ActiveOnly` to get Error reports that are not resolved. +Set this to `InactiveOnly` to get Error reports that are resolved. +Set this to `Both` to get both active and inactive Error reports. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId + +The UUID of a WFM connection. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorInstanceId + +The UUID of a connector instance. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamId + +The UUID of a team in Graph. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Operation + +The name of the action of the controller or the name of the command. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Procedure + +The name of the executing function or procedure. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Code + +The enum value of error code, human readable string defined in codebase. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Before + +The timestamp indicating results should be before which date and time. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -After + +The timestamp indicating results should be after which date and time. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Authorization +Used to provide the necessary credentials for authenticating and authorizing the connection to the workforce management (WFM) system. This parameter ensures that the connection has the appropriate permissions to access and manage the data within the WFM system. + +```yaml +Type: String +Parameter Sets: Get +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Break +Wait for the .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Disable-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/disable-csteamsshiftsconnectionerrorreport) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md new file mode 100644 index 0000000000..9cae80f516 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md @@ -0,0 +1,279 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionInstance +author: leonardospina +ms.author: lespina +manager: valk +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionInstance + +## SYNOPSIS +This cmdlet returns the list of existing connection instances. It can also return the configuration details for a given connection instance. + +## SYNTAX + +### Get (Default) +``` +Get-CsTeamsShiftsConnectionInstance [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### Get1 +``` +Get-CsTeamsShiftsConnectionInstance -ConnectorInstanceId <String> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity +``` +Get-CsTeamsShiftsConnectionInstance -InputObject <IConfigApiBasedCmdletsIdentity> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet returns the list of existing connections. It can also return the configuration details for a given connection instance. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionInstance | Format-List +``` +```output + +ConnectionId : a2d1b091-5140-4dd2-987a-98a8b5338744 +ConnectorAdminEmail : {testAdmin@contoso.com} +ConnectorId : 95BF2848-2DDA-4425-B0EE-D62AEED4C0A0 +CreatedDateTime : 07/04/2023 10:53:59 +DesignatedActorId : ec1a4edb-1a5f-4b2d-b2a4-37aaf3acd231 +Etag : "4f00c221-0000-0400-0000-642ff6480000" +Id : WCI-b58d7a98-ab2c-473f-99a5-e0627d54c062 +LastModifiedDateTime : 07/04/2023 10:53:59 +Name : My connection instance 1 +State : Active +SyncFrequencyInMin : 10 +SyncScenarioOfferShiftRequest : FromWfmToShifts +SyncScenarioOpenShift : FromWfmToShifts +SyncScenarioOpenShiftRequest : FromWfmToShifts +SyncScenarioShift : FromWfmToShifts +SyncScenarioSwapRequest : FromWfmToShifts +SyncScenarioTimeCard : FromWfmToShifts +SyncScenarioTimeOff : FromWfmToShifts +SyncScenarioTimeOffRequest : FromWfmToShifts +SyncScenarioUserShiftPreference : FromWfmToShifts +TenantId : dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a +WorkforceIntegrationId : WFI_2ab21992-b9b1-464a-b9cd-e0de1fac95b1 + +ConnectionId : a2d1b091-5140-4dd2-987a-98a8b5338744 +ConnectorAdminEmail : {} +ConnectorId : 95BF2848-2DDA-4425-B0EE-D62AEED4C0A0 +CreatedDateTime : 07/04/2023 10:54:01 +DesignatedActorId : ec1a4edb-1a5f-4b2d-b2a4-37aab6ebd231 +Etag : "4f005d22-0000-0400-0000-642ff64a0000" +Id : WCI-eba2865f-6cac-46f9-8733-e0631a4536e1 +LastModifiedDateTime : 07/04/2023 10:54:01 +Name : My connection instance 2 +State : Active +SyncFrequencyInMin : 30 +SyncScenarioOfferShiftRequest : FromWfmToShifts +SyncScenarioOpenShift : FromWfmToShifts +SyncScenarioOpenShiftRequest : FromWfmToShifts +SyncScenarioShift : FromWfmToShifts +SyncScenarioSwapRequest : Disabled +SyncScenarioTimeCard : Disabled +SyncScenarioTimeOff : FromWfmToShifts +SyncScenarioTimeOffRequest : FromWfmToShifts +SyncScenarioUserShiftPreference : Disabled +TenantId : dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a +WorkforceIntegrationId : WFI_6b225907-b476-4d40-9773-08b86db7b11b +``` + +Returns the list of connection instances. + +### Example 2 +```powershell +PS C:\> $ci = Get-CsTeamsShiftsConnectionInstance -ConnectorInstanceId WCI-78F5116E-9098-45F5-B595-1153DF9D6F70 +PS C:\> $ci.ToJsonString() +``` +```output +{ + "syncScenarios": { + "offerShiftRequest": "FromWfmToShifts", + "openShift": "FromWfmToShifts", + "openShiftRequest": "FromWfmToShifts", + "shift": "FromWfmToShifts", + "swapRequest": "Disabled", + "timeCard": "Disabled", + "timeOff": "FromWfmToShifts", + "timeOffRequest": "FromWfmToShifts", + "userShiftPreferences": "Disabled" + }, + "id": "WCI-78F5116E-9098-45F5-B595-1153DF9D6F70", + "tenantId": "dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a", + "connectionId": "a2d1b091-5140-4dd2-987a-98a8b5338744", + "connectorAdminEmails": [ ], + "connectorId": "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0", + "designatedActorId": "ec1a4edb-1a5f-4b2d-b2a4-37aab6ebd231", + "name": "My connection instance 2", + "syncFrequencyInMin": 30, + "workforceIntegrationId": "WFI_6b225907-b476-4d40-9773-08b86db7b11b", + "etag": "\"4f005d22-0000-0400-0000-642ff64a0000\"", + "createdDateTime": "2023-04-07T10:54:01.8170000Z", + "lastModifiedDateTime": "2023-04-07T10:54:01.8170000Z", + "state": "Active" +} +``` +Returns the connection instance with the specified -ConnectorInstanceId. + +## PARAMETERS + +### -Break +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorInstanceId +The connector instance id + +```yaml +Type: String +Parameter Sets: Get1 +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConnectorInstanceResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[New-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectioninstance) + +[Set-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnectioninstance) + +[Remove-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectioninstance) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md new file mode 100644 index 0000000000..e1910f5da5 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md @@ -0,0 +1,185 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionOperation +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionoperation +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionOperation + +## SYNOPSIS + +This cmdlet gets the requested batch mapping operation. The batch mapping operation can be submitted by running [New-CsTeamsShiftsConnectionBatchTeamMap](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectionbatchteammap). + +## SYNTAX + +### Get (Default) +```powershell +Get-CsTeamsShiftsConnectionOperation -OperationId <String> [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity +```powershell +Get-CsTeamsShiftsConnectionOperation -InputObject <IConfigApiBasedCmdletsIdentity> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet returns the details of a specific batch team mapping operation. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionOperation -OperationId c79131b7-9ecb-484b-a8df-2959c7c1e5f2 +``` +```output +CreatedDateTime LastActionDateTime Id Status TenantId Type WfmConnectorInstanceId +--------------- ------------------ ----------- ------ -------- ---- ---------------------- +12/6/2021 7:28:51 PM 12/6/2021 7:28:51 PM c79131b7-9ecb-484b-a8df-2959c7c1e5f2 NotStarted dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a TeamsMappingOperation WCI-2afeb8ec-a0f6-4580-8f1e-85fd4a113e01 +``` + +Returns the details of batch mapping operation with ID `c79131b7-9ecb-484b-a8df-2959c7c1e5f2`. + +## PARAMETERS + +### -Break +Wait for the .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -OperationId +The ID of the batch mapping operation. + +```yaml +Type: String +Parameter Sets: Get +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsShiftsConnectionBatchTeamMap](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectionbatchteammap) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md new file mode 100644 index 0000000000..d893f5cf7e --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md @@ -0,0 +1,106 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionSyncResult +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionsyncresult +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionSyncResult + +## SYNOPSIS + +This cmdlet supports retrieving the list of user details in the mapped teams of last sync. + +## SYNTAX + +``` +Get-CsTeamsShiftsConnectionSyncResult -ConnectorInstanceId <string> -TeamId <string> -InputObject <IConfigApiBasedCmdletsIdentity> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet supports retrieving the list of successful and failed users in the mapped teams of last sync. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionSyncResult -ConnectorInstanceId "WCI-d1addd70-2684-4723-b8f2-7fa2230648c9" -TeamId "12345d29-7ee1-4259-8999-946953feb79e" +``` +```output +FailedAadUser FailedWfmUser SuccessfulUser +------------- ------------- -------------- +{LABRO} {FRPET, WAROS, JOREE} {user3@contoso.com, user2@contoso.comm, user@contoso.com} +``` + +Returns the successful and failed users in the team mapping of Teams `12345d29-7ee1-4259-8999-946953feb79e` in the instance with ID `WCI-d1addd70-2684-4723-b8f2-7fa2230648c9`. +`LABRO` in FailedAadUser column shows the list of users who failed to sync from Teams to Wfm. +`FRPET, WAROS, JOREE` in FailedWfmUser column shows the list of users who failed to sync from Wfm to Teams. +`user3@contoso.com, user2@contoso.comm, user@contoso.com` in SuccessfulUser column shows the list of users who synced in both Wfm and Teams. + +## PARAMETERS + +### -ConnectorInstanceId + +The ID of the connection instance. It can be retrieved by running [Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamId + +The Teams team ID. It can be retrieved by visiting [AzureAAD](https://portal.azure.com/#blade/Microsoft_AAD_IAM/GroupsManagementMenuBlade/AllGroups). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +The Identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md new file mode 100644 index 0000000000..7bdc708135 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md @@ -0,0 +1,95 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionTeamMap +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionteammap +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionTeamMap + +## SYNOPSIS + +This cmdlet supports retrieving the list of team mappings. + +## SYNTAX + +``` +Get-CsTeamsShiftsConnectionTeamMap -ConnectorInstanceId <String> -InputObject <IConfigApiBasedCmdletsIdentity> [<CommonParameters>] +``` + +## DESCRIPTION + +Workforce management (WFM) systems have locations / sites that are mapped to a Microsoft Teams team for synchronization of shifts data. This cmdlet shows the list of mapped teams inside the connection instance. Instance IDs can be found by running [Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionTeamMap -ConnectorInstanceId "WCI-d1addd70-2684-4723-b8f2-7fa2230648c9" +``` +```output +TeamId TeamName TimeZone WfmTeamId WfmTeamName +------ -------- -------- --------- ----------- +12344689-758c-4598-9206-3e23416da8c2 America/Los_Angeles 1000107 +``` + +Returns the list of team mappings in the instance with ID `WCI-d1addd70-2684-4723-b8f2-7fa2230648c9`. + +In case of error, we can capture the error response as following: + +* Hold the cmdlet output in a variable: `$result=<CMDLET>` + +* To get the entire error message in Json: `$result.ToJsonString()` + +* To get the error object and object details: `$result, $result.Detail` + +## PARAMETERS + +### -ConnectorInstanceId + +The ID of the connection instance. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -InputObject +The Identity parameter + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Remove-CsTeamsShiftsConnectionTeamMap](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectionteammap) + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md new file mode 100644 index 0000000000..f65e7c3eed --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md @@ -0,0 +1,277 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionWfmTeam +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionwfmteam +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionWfmTeam + +## SYNOPSIS + +This cmdlet supports retrieving the list of available Workforce management (WFM) teams in the connection instance. + +## SYNTAX + +### Get (Default) +```powershell +Get-CsTeamsShiftsConnectionWfmTeam -ConnectorInstanceId <String> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### Get1 +```powershell +Get-CsTeamsShiftsConnectionWfmTeam -ConnectionId <String> [-Authorization <String>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity1 +```powershell +Get-CsTeamsShiftsConnectionWfmTeam -InputObject <IConfigApiBasedCmdletsIdentity> [-Authorization <String>] + [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity +```powershell +Get-CsTeamsShiftsConnectionWfmTeam -InputObject <IConfigApiBasedCmdletsIdentity> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet shows the WFM teams that are not currently mapped to a Microsoft Teams team, and thus can be mapped to a Microsoft Teams team in the connection instance. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionWfmTeam -ConnectorInstanceId "WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b" +``` +```output +Id Name +-- ---- +1000105 0002 - Bucktown +1000106 0003 - West Town +1000107 0005 - Old Town +1000108 0004 - River North +1000109 0001 - Wicker Park +1000111 2055 +1000112 2056 +1000114 1004 +1000115 1003 +1000116 1002 +1000122 0010 +1000124 0300 +1000125 1000 +1000126 4500 +1000128 0006 - WFM Team 1 +1000129 Test +``` + +Returns the WFM teams for the connection instance with ID `WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b`. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionWfmTeam -ConnectionId "a2d1b091-5140-4dd2-987a-98a8b5338744" +``` +```output +Id Name +-- ---- +1000105 0002 - Bucktown +1000106 0003 - West Town +1000107 0005 - Old Town +1000108 0004 - River North +1000109 0001 - Wicker Park +1000111 2055 +1000112 2056 +1000114 1004 +1000115 1003 +1000116 1002 +1000122 0010 +1000124 0300 +1000125 1000 +1000126 4500 +1000128 0006 - WFM Team 1 +1000129 Test +``` + +Returns the WFM teams for the WFM connection with ID `a2d1b091-5140-4dd2-987a-98a8b5338744`. + +## PARAMETERS + +### -ConnectorInstanceId + +The ID of the connection instance. You can retrieve it by running [Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId + +The ID of the connection. You can retrieve it by running [Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Authorization +Used to provide the necessary credentials for authenticating and authorizing the connection to the workforce management (WFM) system. This parameter ensures that the connection has the appropriate permissions to access and manage the data within the WFM system. + +```yaml +Type: String +Parameter Sets: Get1, GetViaIdentity1 +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Break +Wait for the .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity1, GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection) + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) + +[Get-CsTeamsShiftsConnectionWfmUser](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionwfmuser) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md new file mode 100644 index 0000000000..f32eda9d1a --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsShiftsConnectionWfmUser +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionwfmuser +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsConnectionWfmUser + +## SYNOPSIS + +This cmdlet shows the list of Workforce management (WFM) users in a specified WFM team. + +## SYNTAX + +```powershell +Get-CsTeamsShiftsConnectionWfmUser -ConnectorInstanceId <string> -WfmTeamId <string> -InputObject <IConfigApiBasedCmdletsIdentity> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet shows the list of Workforce management (WFM) users in a specified WFM team. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsConnectionWfmUser -ConnectorInstanceId "WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b" -WfmTeamId "1000107" +``` +```output +Id Name +-- ---- +1000111 FRPET +1000121 WAROS +1000123 LABRO +1000125 JOREE +1006068 ABC +1006069 XYZ +1006095 DEF +``` + +Returns the users in the WFM team with ID `1000107` in the connection instances with ID `WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b`. + +## PARAMETERS + +### -ConnectorInstanceId + +The ID of the connection instance. It can be retrieved by running [Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WfmTeamId + +The Teams team ID. It can be retrieved by running [Get-CsTeamsShiftsConnectionWfmTeam](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionwfmteam). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +The identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) + +[Get-CsTeamsShiftsConnectionWfmTeam](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionwfmteam) diff --git a/teams/teams-ps/teams/Get-CsTeamsShiftsPolicy.md b/teams/teams-ps/teams/Get-CsTeamsShiftsPolicy.md new file mode 100644 index 0000000000..05e0a5d12c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsShiftsPolicy.md @@ -0,0 +1,99 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-teamsshiftspolicy +title: Get-CsTeamsShiftsPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsShiftsPolicy + +## SYNOPSIS + +This cmdlet allows you to get properties of a TeamsShiftPolicy instance, including user's Teams off shift warning message-specific settings. + +## SYNTAX + +### Identity (Default) +```powershell +Get-CsTeamsShiftsPolicy [[-Identity] <XdsIdentity>] [<CommonParameters>] +``` + +### Filter +```powershell +Get-CsTeamsShiftsPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet allows you to get properties of a TeamsShiftPolicy instance. Use this to get the policy name and Teams off shift warning message-specific settings (ShiftNoticeMessageType, ShiftNoticeMessageCustom, ShiftNoticeFrequency, AccessGracePeriodMinutes). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsShiftsPolicy +``` + +Gets the properties of all instances of the TeamsShiftPolicy. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsShiftsPolicy -Identity OffShiftAccessMessage1Always +``` + +Gets the properties of the OffShiftAccessMessage1Always instance of the TeamsShiftPolicy. + +## PARAMETERS + +### -Identity +Policy instance name. Optional. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. To return a collection of all the policies, use this syntax: -Filter "tag:*". + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftspolicy) + +[New-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftspolicy) + +[Remove-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftspolicy) + +[Grant-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsshiftspolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsSipDevicesConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsSipDevicesConfiguration.md new file mode 100644 index 0000000000..bae35132f4 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsSipDevicesConfiguration.md @@ -0,0 +1,53 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-CsTeamsSipDevicesConfiguration +author: anmandav +ms.author: anmandav +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamssipdevicesconfiguration +schema: 2.0.0 +--- + +# Get-CsTeamsSipDevicesConfiguration + +## SYNOPSIS + +This cmdlet is used to retrieve the organization-wide Teams SIP devices configuration. + +## SYNTAX + +```powershell +Get-CsTeamsSipDevicesConfiguration [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet is used to retrieve the organization-wide Teams SIP devices configuration which contains settings that are applicable to SIP devices connected to Teams using Teams Sip Gateway. + +To execute the cmdlet, you need to hold a role within your organization such as Global Reader, Teams Administrator, or Teams Communication Administrator. + +## Examples + +### Example 1 + +```powershell +PS C:\> Get-CsTeamsSipDevicesConfiguration + +Identity : Global +BulkSignIn : Enabled +``` + +In this example, the organization has Bulk SignIn enabled for their SIP devices. + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsSipDevicesConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamssipdevicesconfiguration) diff --git a/teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliance.md b/teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliance.md new file mode 100644 index 0000000000..e62879f6a5 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliance.md @@ -0,0 +1,95 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamssurvivablebranchappliance +title: Get-CsTeamsSurvivableBranchAppliance +schema: 2.0.0 +--- + +# Get-CsTeamsSurvivableBranchAppliance + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsSurvivableBranchAppliance [[-Identity] <String>] [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsSurvivableBranchAppliance [-MsftInternalProcessingMode <String>] [-Filter <String>] + [<CommonParameters>] +``` + +## PARAMETERS + +### -Filter + +This parameter can be used to fetch instances based on partial matches on the Identity field. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the SBA. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliancePolicy.md b/teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliancePolicy.md new file mode 100644 index 0000000000..c978c4c0a6 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliancePolicy.md @@ -0,0 +1,95 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamssurvivablebranchappliancepolicy +title: Get-CsTeamsSurvivableBranchAppliancePolicy +schema: 2.0.0 +--- + +# Get-CsTeamsSurvivableBranchAppliancePolicy + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) Policy cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsSurvivableBranchAppliancePolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsSurvivableBranchAppliancePolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] + [<CommonParameters>] +``` + +## PARAMETERS + +### -Filter + +This parameter can be used to fetch policy instances based on partial matches on the Identity field. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +This parameter can be used to fetch a specific instance of the policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsTargetingPolicy.md b/teams/teams-ps/teams/Get-CsTeamsTargetingPolicy.md new file mode 100644 index 0000000000..8b48de854b --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsTargetingPolicy.md @@ -0,0 +1,111 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamstargetingpolicy +title: Get-CsTeamsTargetingPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsTargetingPolicy + +## SYNOPSIS + +The Teams Targeting Policy cmdlets enable administrators to control the type of Tenant tag setting that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsTargetingPolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsTargetingPolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +The CsTeamsTargetingPolicy cmdlets enable administrators to control the type of tags that users can create or the features that they can access in Teams. It also helps determine how tags deal with Teams members or guest users. + +The Get-CsTeamsTargetingPolicy cmdlet enables you to return information about all the Tenant tag setting policies that have been configured for use in your organization. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-CsTeamsTargetingPolicy -Identity SalesPolicy +``` + +In this example Get-CsTeamsTargetingPolicy is used to return the per-tenant tag policy that has an Identity SalesPolicy. Because identities are unique, this command will never return more than one item. + +## PARAMETERS + +### -Filter + +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier of the policy to be returned. To refer to the global policy, use this syntax: -Identity global. To refer to a per-tenant policy, use syntax similar to this: -Identity SalesDepartmentPolicy. If this parameter is omitted, then all the tenant tag setting policies configured for use in your organization will be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Set-CsTargetingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstargetingpolicy) +[Remove-CsTargetingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamstargetingpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsTemplatePermissionPolicy.md b/teams/teams-ps/teams/Get-CsTeamsTemplatePermissionPolicy.md new file mode 100644 index 0000000000..783c5f16c2 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsTemplatePermissionPolicy.md @@ -0,0 +1,126 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamstemplatepermissionpolicy +title: Get-CsTeamsTemplatePermissionPolicy +author: yishuaihuang4 +ms.author: yishuaihuang +ms.reviewer: +manager: weiliu2 +schema: 2.0.0 +--- + +# Get-CsTeamsTemplatePermissionPolicy + +## SYNOPSIS +Fetches the TeamsTemplatePermissionPolicy. This policy can be used to hide Teams templates from users and groups. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsTemplatePermissionPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsTemplatePermissionPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Fetches the instances of the policy. Each policy object contains a property called `HiddenTemplates`.This array contains the list of Teams template IDs that will be hidden by that instance of the policy. + +## EXAMPLES + +### Example 1 +```powershell +PS >Get-CsTeamsTemplatePermissionPolicy +``` +```output +Identity HiddenTemplates Description +-------- --------------- ----------- +Global {com.microsoft.teams.template.CoordinateIncidentResponse} +Tag:Foobar {com.microsoft.teams.template.ManageAProject, com.microsoft.teams.template.ManageAnEvent} +``` + +Fetches all the policy instances currently available. + +### Example 2 + +```powershell +PS >Get-CsTeamsTemplatePermissionPolicy -Identity Foobar +``` +```output +Identity HiddenTemplates Description +-------- --------------- ----------- +Tag:Foobar {com.microsoft.teams.template.ManageAProject, com.microsoft.teams.template.ManageAnEvent} +``` + +Fetches an instance of a policy with known identity. + +### Example 3 + +```powershell +PS >Get-CsTeamsTemplatePermissionPolicy -Filter *Foo* +``` +```output +Identity HiddenTemplates Description +-------- --------------- ----------- +Tag:Foobar {com.microsoft.teams.template.ManageAProject, com.microsoft.teams.template.ManageAnEvent} +``` + +The `Filter` parameter can be used to fetch policy instances based on partial matches on Identity. + +Note: _The "Tag:" prefix can be ignored when specifying the identity._ + +## PARAMETERS + +### -Filter +This parameter can be used to fetch policy instances based on partial matches on the `Identity` field. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter can be used to fetch a specific instance of the policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsTemplatePermissionPolicy.Cmdlets.TeamsTemplatePermissionPolicy + +## NOTES + +## RELATED LINKS +[New-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy) + +[Remove-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamstemplatepermissionpolicy) + +[Set-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsTranslationRule.md b/teams/teams-ps/teams/Get-CsTeamsTranslationRule.md new file mode 100644 index 0000000000..402b525db2 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsTranslationRule.md @@ -0,0 +1,105 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamstranslationrule +applicable: Microsoft Teams +title: Get-CsTeamsTranslationRule +schema: 2.0.0 +manager: nmurav +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsTeamsTranslationRule + +## SYNOPSIS +Cmdlet to get an existing number manipulation rule (or list of rules). + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsTranslationRule [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsTranslationRule [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +You can use this cmdlet to get an existing number manipulation rule (or list of rules). The rule can be used, for example, in the settings of your SBC (Set-CSOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsTeamsTranslationRule +``` + +This command will show all translation rules that exist in the tenant. Identity, Name, Description, Pattern, and Translation parameters are listed for each rule. + +### Example 2 +```powershell +Get-CsTeamsTranslationRule -Identity AddPlus1 +``` + +This command will show Identity, Name, Description, Pattern, and Translation parameters for the "AddPlus1" rule. + +### Example 3 +```powershell +Get-CsTeamsTranslationRule -Filter 'Add*' +``` + +This command will show Identity, Name, Description, Pattern, and Translation parameters for all rules with Identity starting with Add. + +## PARAMETERS + +### -Identity +Identifier of the specific translation rule to display. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +The filter to use against the Identity of translation rules. + +```yaml +Type: String +Parameter Sets: (Filter) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[New-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/new-csteamstranslationrule) + +[Test-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/test-csteamstranslationrule) + +[Set-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/set-csteamstranslationrule) + +[Remove-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/remove-csteamstranslationrule) diff --git a/teams/teams-ps/teams/Get-CsTeamsUnassignedNumberTreatment.md b/teams/teams-ps/teams/Get-CsTeamsUnassignedNumberTreatment.md new file mode 100644 index 0000000000..cd8a81e96e --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsUnassignedNumberTreatment.md @@ -0,0 +1,105 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsunassignednumbertreatment +applicable: Microsoft Teams +title: Get-CsTeamsUnassignedNumberTreatment +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Get-CsTeamsUnassignedNumberTreatment + +## SYNOPSIS +Displays a specific or all treatments for how calls to an unassigned number range should be routed. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsUnassignedNumberTreatment [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsUnassignedNumberTreatment [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet displays a specific or all treatments for how calls to an unassigned number range should be routed. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsTeamsUnassignedNumberTreatment -Identity MainAA +``` +This example displays the treatment MainAA. + +### Example 2 +```powershell +Get-CsTeamsUnassignedNumberTreatment +``` +This example displays all configured treatments. + +### Example 3 +```powershell +Get-CsTeamsUnassignedNumberTreatment -Filter Ann* +``` +This example displays all configured treatments with an Identity starting with Ann. + +## PARAMETERS + +### -Filter +Enables you to limit the returned data by filtering on the Identity attribute. + +```yaml +Type: String +Parameter Sets: (Filter) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Id of the specific treatment to show. + +```yaml +Type: System.String +Parameter Sets: (Identity) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PS module 2.5.1 or later. + +## RELATED LINKS +[Remove-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/remove-csteamsunassignednumbertreatment) + +[New-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/new-csteamsunassignednumbertreatment) + +[Set-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/set-csteamsunassignednumbertreatment) diff --git a/teams/teams-ps/teams/Get-CsTeamsUpdateManagementPolicy.md b/teams/teams-ps/teams/Get-CsTeamsUpdateManagementPolicy.md new file mode 100644 index 0000000000..3bcd814b61 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsUpdateManagementPolicy.md @@ -0,0 +1,89 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsupdatemanagementpolicy +applicable: Microsoft Teams +title: Get-CsTeamsUpdateManagementPolicy +schema: 2.0.0 +author: vargasj-ms +ms.author: vargasj +manager: gnamun +--- + +# Get-CsTeamsUpdateManagementPolicy + +## SYNOPSIS +Use this cmdlet to retrieve the current Teams Update Management policies in the organization. + +## SYNTAX + +### Identity (Default) +```powershell +Get-CsTeamsUpdateManagementPolicy [[-Identity] <String>] [-ProgressAction <ActionPreference>] + [<CommonParameters>] +``` + +### Filter +```powershell +Get-CsTeamsUpdateManagementPolicy [-Filter <String>] [-ProgressAction <ActionPreference>] [<CommonParameters>] +``` + +## DESCRIPTION +The Teams Update Management Policy allows admins to specify if a given user is enabled to preview features in Teams. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsUpdateManagementPolicy +``` + +In this example, we retrieve all the existing Teams Update Management policies in the organization. + +## PARAMETERS + +### -Identity +The unique identifier of the policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter + +This parameter accepts a wildcard string and returns all policies with identities matching that string. For example, a Filter value of tag:* will return all policies defined at the per-user level. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsUpdateManagementPolicy.Cmdlets.TeamsUpdateManagementPolicy + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTeamsUpgradeConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsUpgradeConfiguration.md new file mode 100644 index 0000000000..7443bce227 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsUpgradeConfiguration.md @@ -0,0 +1,123 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/skype/get-csteamsupgradeconfiguration +applicable: Microsoft Teams +title: Get-CsTeamsUpgradeConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Get-CsTeamsUpgradeConfiguration + +## SYNOPSIS +Returns information related to managing the upgrade to Teams from Skype for Business. TeamsUpgradeConfiguration should be used in conjunction with TeamsUpgradePolicy. The settings in TeamsUpgradeConfiguration allow administrators to configure whether users subject to upgrade and who are running on Windows clients should automatically download Teams. For Office 365 users, it allows administrators to determine which application end users should use to join Skype for Business meetings. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsUpgradeConfiguration [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsUpgradeConfiguration [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +TeamsUpgradeConfiguration is used in conjunction with TeamsUpgradePolicy. The settings in TeamsUpgradeConfiguration allow administrators to configure whether users subject to upgrade and who are running on Windows clients should automatically download the Teams app. It also allows administrators to determine which application Office 365 users should use to join Skype for Business meetings. + +Separate instances of TeamsUpgradeConfiguration exist in Office 365 and Skype for Business Server. + - TeamsUpgradeConfiguration in Office 365 applies to any user who does not have an on-premises Skype for Business account. + - TeamsUpgradeConfiguration in Skype for Business Server can used to manage on-premises users in a hybrid environment. In on-premises, only the DownloadTeams property is available. + +The DownloadTeams property allows admins to control whether the Skype for Business client should automatically download the Teams app in the background. This setting is only honored for users on Windows clients, and only if TeamsUpgradePolicy for the user meets either of these conditions: + - NotifySfbUser=true, or + - Mode=TeamsOnly + Otherwise, this setting is ignored. + +The SfBMeetingJoinUx property allows admins to specify which app is used to join Skype for Business meetings, even after the user has been upgraded to Teams. Allowed values are: SkypeMeetingsApp and NativeLimitedClient. "NativeLimitedClient" means the existing Skype for Business rich client will be used, but since the user is upgraded, only meeting functionality is available. Calling and Messaging are done via Teams. "SkypeMeetingsApp" means use the web-downloadable app. This setting can be useful for organizations that have upgraded to Teams and no longer want to install Skype for Business on their users' computers. This property is only available when configuring TeamsUpgradeConfiguration in Office 365. It is not honored for users homed on-premises in Skype for Business Server. + +## EXAMPLES + +### Example 1 +``` +PS C:\> Get-CsTeamsUpgradeConfiguration +``` + +The above cmdlet lists the properties of TeamsUpgradeConfiguration. + +## PARAMETERS + +### -Identity +{{Fill Identity Description}} + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +Do not use + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +{{Fill Tenant Description}} + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +These settings are only honored by newer versions of Skype for Business clients. + +## RELATED LINKS + +[Set-CsTeamsUpgradeConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsupgradeconfiguration) + +[Get-CsTeamsUpgradePolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsupgradepolicy) + +[Grant-CsTeamsUpgradePolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsupgradepolicy) + +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) diff --git a/teams/teams-ps/teams/Get-CsTeamsUpgradePolicy.md b/teams/teams-ps/teams/Get-CsTeamsUpgradePolicy.md new file mode 100644 index 0000000000..1da715da85 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsUpgradePolicy.md @@ -0,0 +1,198 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/skype/get-csteamsupgradepolicy +applicable: Microsoft Teams +title: Get-CsTeamsUpgradePolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Get-CsTeamsUpgradePolicy + +## SYNOPSIS +TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. + +> [!IMPORTANT] +> It can take up to 24 hours for a change to TeamsUpgradePolicy to take effect. Before then, user presence status may not be correct (may show as **Unknown**). + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsUpgradePolicy [-Tenant <Guid>] [[-Identity] <XdsIdentity>] [-LocalStore] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsUpgradePolicy [-Tenant <Guid>] [-Filter <String>] [-LocalStore] [<CommonParameters>] +``` + +## DESCRIPTION +TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. This cmdlet returns the set of instances of this policy. As an organization with Skype for Business starts to adopt Teams, administrators can manage the user experience in their organization using the concept of coexistence "mode". Mode defines in which client incoming chats and calls land as well as in what service (Teams or Skype for Business) new meetings are scheduled in. Mode also governs whether chat, calling, and meeting scheduling functionality are available in the Teams client. Finally, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. + +NOTES: + - Except for on-premise versions of Skype for Business Server, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet. + - If you are using Skype for Business Server, there are no built-in instances and you'll need to create one. Also, only the NotifySfBUsers property is available. Mode is not present. + - Using TeamsUpgradePolicy in an on-premises environmention requires Skype for Business Server 2015 with CU8 or later. + +You can also find more guidance here: [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype). + +## EXAMPLES + +### Example 1: List all instances of TeamsUpgradePolicy (Skype for Business Online) +``` +PS C:\> Get-CsTeamsUpgradePolicy + +Identity : Global +Description : Users can use either Skype for Business client or Teams client +Mode : Islands +NotifySfbUsers : False + +Identity : Tag:UpgradeToTeams +Description : Use Teams Only +Mode : TeamsOnly +NotifySfbUsers : False + +Identity : Tag:Islands +Description : Use either Skype for Business client or Teams client +Mode : Islands +NotifySfbUsers : False +Action : None + +Identity : Tag:IslandsWithNotify +Description : Use either Skype for Business client or Teams client +Mode : Islands +NotifySfbUsers : True + +Identity : Tag:SfBOnly +Description : Use only Skype for Business +Mode : SfBOnly +NotifySfbUsers : False + +Identity : Tag:SfBOnlyWithNotify +Description : Use only Skype for Business +Mode : SfBOnly +NotifySfbUsers : True + +Identity : Tag:SfBWithTeamsCollab +Description : Use Skype for Business and use Teams only for group collaboration +Mode : SfBWithTeamsCollab +NotifySfbUsers : False + +Identity : Tag:SfBWithTeamsCollabWithNotify +Description : Use Skype for Business and use Teams only for group collaboration +Mode : SfBWithTeamsCollab +NotifySfbUsers : True + +Identity : Tag:SfBWithTeamsCollabAndMeetings +Description : Use Skype for Business and use Teams only for group collaboration +Mode : SfBWithTeamsCollabAndMeetings +NotifySfbUsers : False + +Identity : Tag:SfBWithTeamsCollabAndMeetingsWithNotify +Description : Use Skype for Business and use Teams only for group collaboration +Mode : SfBWithTeamsCollabAndMeetings +NotifySfbUsers : True +``` + +List all instances of TeamsUpgradePolicy + +### Example 2: List the global instance of TeamsUpgradePolicy (which applies to all users in a tenant unless they are explicitly assigned an instance of this policy) +``` +PS C:\> Get-CsTeamsUpgradePolicy -Identity Global + +Identity : Global +Description : Users can use either Skype for Business client or Teams client +Mode : Islands +NotifySfbUsers : False + +``` + +List the global instance of TeamsUpgradePolicy + +### Example 3: List all instances of TeamsUpgradePolicy in an on-premises environment +``` +PS C:\> Get-CsTeamsUpgradePolicy -Identity Global + +Identity : Global +Description : Notifications are disabled +NotifySfbUsers : False + +``` + +List all on-premises instances (if any) of TeamsUpgradePolicy. + +## PARAMETERS + +### -Identity +If identity parameter is passed, this will return a specific instance. If no identity parameter is specified, the cmdlet returns all instances. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -Filter +{{Fill Filter Description}} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +{{Fill Tenant Description}} + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsUpgradeConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsupgradeconfiguration) + +[Set-CsTeamsUpgradeConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsupgradeconfiguration) + +[Grant-CsTeamsUpgradePolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsupgradepolicy) + +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) diff --git a/teams/teams-ps/teams/Get-CsTeamsVdiPolicy.md b/teams/teams-ps/teams/Get-CsTeamsVdiPolicy.md new file mode 100644 index 0000000000..41be427ab3 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsVdiPolicy.md @@ -0,0 +1,99 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsvdipolicy +title: Get-CsTeamsVdiPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsVdiPolicy + +## SYNOPSIS +The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +## SYNTAX + +### Identity (Default) +```powershell +Get-CsTeamsVdiPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +```powershell +Get-CsTeamsVdiPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +Teams Vdi policies can be configured at the global and per-user scopes. The Get-CsTeamsVdiPolicy cmdlet enables you to return infomration about all the Vdi policies that have been configured for use in your organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsVdiPolicy +``` + +In Example 1, Get-CsTeamsVdiPolicy is called without any additional parameters; this returns a collection of all the teams meeting policies configured for use in your organization. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsVdiPolicy -Identity SalesPolicy +``` + +In Example 2, Get-CsTeamsVdiPolicy is used to return the per-user meeting policy that has an Identity SalesPolicy. Because identites are unique, this command will never return more than one item. + +### Example 3 +```powershell +PS C:\> Get-CsTeamsVdiPolicy | where-Object {$_.VDI2Optimization -eq "Enabled"} +``` + +The preceding command returns a collection of all the meeting policies where the VDI2Optimization property is Enabled. To do this, Get-CsTeamsVdiPolicy is first called without any parameters in order to return a collection of all the policies configured for use in the organization. This collection is then piped to the Where-Object cmdlet, which selects only those policies where the VDI2Optimization property is equal to Enabled. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier of the policy to be returned. To refer to the global policy, use this syntax: -Identity global. To refer to a per-user policy, use syntax similar to this: -Identity SalesDepartmentPolicy. If this parameter is omitted, then all the meeting policies configured for use in your organization will be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsVdiPolicy.Cmdlets.TeamsVdiPolicy + +## NOTES + +## RELATED LINKS diff --git a/skype/skype-ps/skype/Get-CsTeamsVideoInteropServicePolicy.md b/teams/teams-ps/teams/Get-CsTeamsVideoInteropServicePolicy.md similarity index 90% rename from skype/skype-ps/skype/Get-CsTeamsVideoInteropServicePolicy.md rename to teams/teams-ps/teams/Get-CsTeamsVideoInteropServicePolicy.md index 415a953bb6..be0b2b593d 100644 --- a/skype/skype-ps/skype/Get-CsTeamsVideoInteropServicePolicy.md +++ b/teams/teams-ps/teams/Get-CsTeamsVideoInteropServicePolicy.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csteamsvideointeropservicepolicy -applicable: Skype for Business Online -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsvideointeropservicepolicy +applicable: Microsoft Teams +Module Name: MicrosoftTeams title: Get-CsTeamsVideoInteropServicePolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTeamsVideoInteropServicePolicy @@ -32,7 +32,7 @@ Get-CsTeamsVideoInteropServicePolicy [-Tenant <System.Guid>] [-Filter <String>] ``` ## DESCRIPTION -Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. You can use the TeamsVideoInteropServicePolicy cmdlets to enable Cloud Video Interop for particular users or for your entire organization. Microsoft provides pre-constructed policies for each of our supported partners that allow you to designate which partner(s) to use for cloud video interop. +Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. You can use the TeamsVideoInteropServicePolicy cmdlets to enable Cloud Video Interop for particular users or for your entire organization. Microsoft provides pre-constructed policies for each of our supported partners that allow you to designate which partner(s) to use for cloud video interop. The Get-CsTeamsVideoInteropServicePolicy cmdlet allows you to identify the pre-constructed policies that you can use in your organization. You can assign this policy to one or more of your users leveraging the Grant-CsTeamsVideoInteropServicePolicy cmdlet. @@ -108,14 +108,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Get-CsTeamsVirtualAppointmentsPolicy.md b/teams/teams-ps/teams/Get-CsTeamsVirtualAppointmentsPolicy.md new file mode 100644 index 0000000000..5d698766b8 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsVirtualAppointmentsPolicy.md @@ -0,0 +1,124 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsvirtualappointmentspolicy +title: Get-CsTeamsVirtualAppointmentsPolicy +schema: 2.0.0 +ms.author: erocha +manager: sonaggarwal +author: emmanuelrocha001 +--- + +# Get-CsTeamsVirtualAppointmentsPolicy + +## SYNOPSIS +This cmdlet is used to fetch policy instances of TeamsVirtualAppointmentsPolicy. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsVirtualAppointmentsPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsVirtualAppointmentsPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Fetches instances of TeamsVirtualAppointmentsPolicy. Each policy object contains a property called `EnableSmsNotifications`. This property specifies whether your users can choose to send SMS text notifications to external guests in meetings that they schedule using a virtual appointment meeting template. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsVirtualAppointmentsPolicy +``` +```output +Identity EnableSmsNotifications +-------- ---------------------- +Global True +Tag:sms-enabled True +Tag:sms-disabled False +``` +Fetches all the policy instances currently available. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsVirtualAppointmentsPolicy -Identity sms-enabled +``` +```output +Identity EnableSmsNotifications +-------- ---------------------- +Tag:sms-enabled True +``` +Fetches an instance of a policy with a known identity. + +### Example 3 +```powershell +PS C:\> Get-CsTeamsVirtualAppointmentsPolicy -Filter *sms* +``` +```output +Identity EnableSmsNotifications +-------- ---------------------- +Tag:sms-enabled True +Tag:sms-disabled False +``` +The `Filter` parameter can be used to fetch policy instances based on partial matches on Identity. + +Note: _The "Tag:" prefix can be ignored when specifying the identity._ + +## PARAMETERS + +### -Filter +This parameter can be used to fetch policy instances based on partial matches on the Identity field. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter can be used to fetch a specific instance of the policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### TeamsVirtualAppointmentsPolicy.Cmdlets.TeamsVirtualAppointmentsPolicy + +## NOTES + +## RELATED LINKS +[New-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvirtualappointmentspolicy) + +[Remove-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvirtualappointmentspolicy) + +[Set-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvirtualappointmentspolicy) + +[Grant-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvirtualappointmentspolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsVoiceApplicationsPolicy.md b/teams/teams-ps/teams/Get-CsTeamsVoiceApplicationsPolicy.md new file mode 100644 index 0000000000..0a73f7a287 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsVoiceApplicationsPolicy.md @@ -0,0 +1,115 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsvoiceapplicationspolicy +title: Get-CsTeamsVoiceApplicationsPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsVoiceApplicationsPolicy + +## SYNOPSIS +Use the Get-CsTeamsVoiceApplicationsPolicy cmdlet to get Teams voice applications policy information. TeamsVoiceApplications policy governs what permissions the supervisors/users have over auto attendants and call queues. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsVoiceApplicationsPolicy [[-Identity] <String>] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsVoiceApplicationsPolicy [-Filter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION + +TeamsVoiceApplicationsPolicy is used for Supervisor Delegated Administration which allows tenant admins to permit certain users to make changes to auto attendant and call queue configurations. + +## EXAMPLES + +### EXAMPLE 1 +``` +Get-CsTeamsVoiceApplicationsPolicy +``` +The command shown in Example 1 returns information for all the Teams voice applications policies configured for use in the tenant. + +### EXAMPLE 2 +``` +Get-CsTeamsVoiceApplicationsPolicy -Identity "SDA-Allow-All" +``` +In Example 2, information is returned for a single Teams voice applications policy; the policy with the Identity SDA-Allow-All. + +### EXAMPLE 3 +``` +Get-CsTeamsVoiceApplicationsPolicy -Filter "tag:*" +``` +The command shown in Example 3 returns information about all the Teams voice applications policies configured at the per-user scope. To do this, the command uses the Filter parameter and the filter value "tag:*"; that filter value limits the returned data to policies that have an Identity that begins with the string value "tag:". + +## PARAMETERS + +### -Identity +Unique identifier of the Teams voice applications policy to be retrieved. To return the global policy, use this syntax: + +-Identity global + +To return a policy configured at the per-user scope, use syntax like this: + +-Identity "SDA-Allow-All" + +You cannot use wildcard characters when specifying the Identity. + +If neither the Identity nor the Filter parameters are specified, then Get-CsTeamsVoiceApplicationsPolicy returns all the Teams voice applications policies configured for use in the tenant. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +Enables you to use wildcards when retrieving one or more Teams voice applications policies. For example, to return all the policies configured at the per-user scope, use this syntax: + +-Filter "tag:*" + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvoiceapplicationspolicy) + +[Grant-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvoiceapplicationspolicy) + +[Remove-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvoiceapplicationspolicy) + +[New-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvoiceapplicationspolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsWorkLoadPolicy.md b/teams/teams-ps/teams/Get-CsTeamsWorkLoadPolicy.md new file mode 100644 index 0000000000..894f122d6b --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsWorkLoadPolicy.md @@ -0,0 +1,115 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsworkloadpolicy +title: Get-CsTeamsWorkLoadPolicy +schema: 2.0.0 +--- + +# Get-CsTeamsWorkLoadPolicy + +## SYNOPSIS + +This cmdlet applies an instance of the Teams Workload policy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsWorkLoadPolicy [[-Identity] <String>] [-MsftInternalProcessingMode <String>] [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsWorkLoadPolicy [-MsftInternalProcessingMode <String>] [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +The TeamsWorkLoadPolicy determines the workloads like meeting, messaging, calling that are enabled and/or pinned for the user. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-CsTeamsWorkLoadPolicy +``` + +Retrieves the Teams Workload Policy instances and shows assigned values. + +## PARAMETERS + +### -Filter + +Enables you to use wildcard characters when indicating the policy (or policies) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Identity of the Teams Workload Policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Microsoft internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Remove-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworkloadpolicy) + +[New-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworkloadpolicy) + +[Set-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworkloadpolicy) + +[Grant-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworkloadpolicy) diff --git a/teams/teams-ps/teams/Get-CsTeamsWorkLocationDetectionPolicy.md b/teams/teams-ps/teams/Get-CsTeamsWorkLocationDetectionPolicy.md new file mode 100644 index 0000000000..2dd5152b3d --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTeamsWorkLocationDetectionPolicy.md @@ -0,0 +1,125 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamsworklocationdetectionpolicy +title: Get-CsTeamsWorkLocationDetectionPolicy +schema: 2.0.0 +ms.author: arkozlov +manager: prashibadkur +author: artemiykozlov +--- + +# Get-CsTeamsWorkLocationDetectionPolicy + +## SYNOPSIS +This cmdlet is used to fetch policy instances of TeamsWorkLocationDetectionPolicy. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTeamsWorkLocationDetectionPolicy [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTeamsWorkLocationDetectionPolicy [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Fetches instances of TeamsWorkLocationDetectionPolicy. Each policy object contains a property called `EnableWorkLocationDetection`. This setting allows your organization to collect the work location of users when they connect, interact, or are detected near your organization's networks and devices. It also captures the geographic location information users share from personal and mobile devices. +This gives users the ability to consent to the use of this location data to set their current work location.Microsoft collects this information to provide users with a consistent location-based experience and to improve the hybrid work experience in Microsoft 365 according to the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsWorkLocationDetectionPolicy +``` +```output +Identity EnableWorkLocationDetection +-------- ---------------------- +Global False +Tag:wld-policy1 True +Tag:wld-policy2 False +``` +Fetches all the policy instances currently available. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsWorkLocationDetectionPolicy -Identity wld-policy1 +``` +```output +Identity EnableWorkLocationDetection +-------- ---------------------- +Tag:wld-policy1 True +``` +Fetches an instance of a policy with a known identity. + +### Example 3 +```powershell +PS C:\> Get-CsTeamsWorkLocationDetectionPolicy -Filter *wld* +``` +```output +Identity EnableWorkLocationDetection +-------- ---------------------- +Tag:wld-policy1 True +Tag:wld-policy2 False +``` +The `Filter` parameter can be used to fetch policy instances based on partial matches on Identity. + +Note: _The "Tag:" prefix can be ignored when specifying the identity._ + +## PARAMETERS + +### -Filter +This parameter can be used to fetch policy instances based on partial matches on the Identity field. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter can be used to fetch a specific instance of the policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### TeamsWorkLocationDetectionPolicy.Cmdlets.TeamsWorkLocationDetectionPolicy + +## NOTES + +## RELATED LINKS +[New-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworklocationdetectionpolicy) + +[Remove-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworklocationdetectionpolicy) + +[Set-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworklocationdetectionpolicy) + +[Grant-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworklocationdetectionpolicy) diff --git a/teams/teams-ps/teams/Get-CsTenant.md b/teams/teams-ps/teams/Get-CsTenant.md new file mode 100644 index 0000000000..2558268bcf --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenant.md @@ -0,0 +1,215 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenant +applicable: Microsoft Teams +title: Get-CsTenant +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsTenant + +## SYNOPSIS +Returns information about the Microsoft Teams or Skype for Business Online tenants that have been configured for use in your organization. +Tenants represent groups of online users. + +## SYNTAX + +``` +Get-CsTenant [-Filter <String>] [-DomainController <Fqdn>] [[-Identity] <OUIdParameter>] [-ResultSize <Int32>] + [<CommonParameters>] +``` + +## DESCRIPTION +In Microsoft Teams or Skype for Business Online, tenants are groups of users who have accounts homed on the service. Organizations will typically have a single tenant in which to house all their user accounts. + +In the Teams PowerShell Module version 3.0.0 or later, the following attributes have been deprecated for organizations with Teams users: + +- AdminDescription +- AllowedDataLocation +- AssignedLicenses +- DefaultDataLocation +- DefaultPoolFqdn +- Description +- DisableExoPlanProvisioning +- DistinguishedName +- DomainUrlMap +- ExperiencePolicy +- Guid +- HostedVoiceMail +- HostedVoiceMailNotProvisioned +- Id +- Identity +- IsByPassValidation +- IsMNC +- IsO365MNC +- IsReadinessUploaded +- IsUpgradeReady +- IsValid +- LastSubProvisionTimeStamp +- MNCEnableTimeStamp +- Name +- NonPrimarySource +- ObjectCategory +- ObjectClass +- ObjectId +- ObjectState +- OcoDomainTracked +- OnPremisesImmutableId +- OnPremisesUserPrincipalName +- OnPremSamAccountName +- OnPremSecurityIdentifier +- OriginalRegistrarPool +- OriginatingServer +- PendingDeletion +- Phone +- ProvisioningCounter +- ProvisioningStamp +- ProvisionType +- PublicProvider +- PublishingCounter +- PublishingStamp +- RegistrarPool +- RemoteMachine +- SubProvisioningCounter +- SubProvisioningStamp +- SyncingCounter +- TeamsUpgradeEligible +- TelehealthEnabled +- TenantNotified +- TenantPoolExtension +- UpgradeRetryCounter +- UserRoutingGroupIds +- XForestMovePolicy + +In the Teams PowerShell Module version 3.0.0 or later, the following attributes have been renamed for TeamsOnly customers: + +- CountryAbbreviation is now CountryLetterCode +- CountryOrRegionDisplayName is now Country +- StateOrProvince is now State + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsTenant +``` + +The command shown in Example 1 returns information about your tenant. +Organizations will have only one tenant. + +## PARAMETERS + +### -DomainController +This parameter is not used with Skype for Business Online and will be deprecated in the near future. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter + +**Note:** This parameter has been deprecated from the Teams PowerShell Module version 3.0.0 or later. + +Enables you to return data by using Active Directory attributes and without having to specify the full Active Directory distinguished name. +For example, to retrieve a tenant by using the tenant display name, use syntax similar to this: + +Get-CsTenant -Filter {DisplayName -eq "FabrikamTenant"} + +To return all tenants that use a Fabrikam domain use this syntax: + +Get-CsTenant -Filter {Domains -like "*fabrikam*"} + +The Filter parameter uses the same Windows PowerShell filtering syntax is used by the `Where-Object` cmdlet. + +You cannot use both the Identity parameter and the Filter parameter in the same command. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +**Note:** This parameter has been deprecated from the Teams PowerShell Module version 3.0.0 or later. + +Unique identifier for the tenant. +For example: + +-Identity "bf19b7db-6960-41e5-a139-2aa373474354" + +If you do not include either the Identity or the Filter parameter then the `Get-CsTenant` cmdlet will return information about all your tenants. + +```yaml +Type: OUIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResultSize + +**Note:** This parameter has been deprecated from the Teams PowerShell Module version 3.0.0 or later. + +Enables you to limit the number of records returned by the cmdlet. +For example, to return seven tenants (regardless of the number of tenants that are in your forest) include the ResultSize parameter and set the parameter value to 7. +Note that there is no way to guarantee which 7 users will be returned. + +The result size can be set to any whole number between 0 and 2147483647, inclusive. +If set to 0 the command will run, but no data will be returned. +If you set the tenants to 7 but you have only three contacts in your forest, the command will return those three tenants and then complete without error. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.ADConnect.Schema.TenantObject or String +The `Get-CsTenant` cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.ADConnect.Schema.TenantObject object as well as string values representing the Identity of the tenant (for example "bf19b7db-6960-41e5-a139-2aa373474354"). + +## OUTPUTS + +### Microsoft.Rtc.Management.ADConnect.Schema.TenantObject + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsTenantBlockedCallingNumbers.md b/teams/teams-ps/teams/Get-CsTenantBlockedCallingNumbers.md new file mode 100644 index 0000000000..8f125d7c02 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantBlockedCallingNumbers.md @@ -0,0 +1,116 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantblockedcallingnumbers +title: Get-CsTenantBlockedCallingNumbers +applicable: Microsoft Teams +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +manager: roykuntz +--- + +# Get-CsTenantBlockedCallingNumbers + +## SYNOPSIS +Use the Get-CsTenantBlockedCallingNumbers cmdlet to retrieve tenant blocked calling numbers setting. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTenantBlockedCallingNumbers [[-Identity] <String>] + [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTenantBlockedCallingNumbers [-Filter <String>] + [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +Microsoft Direct Routing, Operator Connect and Calling Plans supports blocking of inbound calls from the public switched telephone network (PSTN). This feature allows a tenant-global list of number patterns to be defined so that the caller ID of every incoming PSTN call to the tenant can be checked against the list for a match. If a match is made, an incoming call is rejected. + +The tenant blocked calling numbers includes a list of inbound blocked number patterns. Number patterns are managed through the CsInboundBlockedNumberPattern commands New, Get, Set, and Remove. You can manage a given pattern by using these cmdlets, including the ability to toggle the activation of a given pattern. + +You can also configure a list of number patterns to be exempt from call blocking. Exempt number patterns are managed through the CsInboundExemptNumberPattern commands New, Get, Set, and Remove. + +You can test your call blocking by using the command Test-CsInboundBlockedNumberPattern. + +The scope of tenant blocked calling numbers is global across the given tenant. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsTenantBlockedCallingNumbers +``` + +This example returns the tenant global settings for blocked calling numbers. It includes a list of inbound blocked number patterns and exempt number patterns. + +## PARAMETERS + +### -Identity +The Identity parameter is a unique identifier that designates the scope, and for per-user scope a name, which identifies the TenantBlockedCallingNumbers to retrieve. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +The Filter parameter allows you to limit the number of results based on filters you specify. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +Internal Microsoft use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Set-CsTenantBlockedCallingNumbers](https://learn.microsoft.com/powershell/module/teams/set-cstenantblockedcallingnumbers) + +[Test-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/test-csinboundblockednumberpattern) diff --git a/teams/teams-ps/teams/Get-CsTenantDialPlan.md b/teams/teams-ps/teams/Get-CsTenantDialPlan.md new file mode 100644 index 0000000000..6981f68fc3 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantDialPlan.md @@ -0,0 +1,107 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantdialplan +applicable: Microsoft Teams +title: Get-CsTenantDialPlan +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsTenantDialPlan + +## SYNOPSIS +Use the Get-CsTenantDialPlan cmdlet to retrieve a tenant dial plan. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTenantDialPlan [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTenantDialPlan [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsTenantDialPlan cmdlet returns information about one or more tenant dial plans (also known as a location profiles) in an organization. +Tenant dial plans provide required information to let Enterprise Voice users make telephone calls. +The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. +A tenant dial plan determines such things as which normalization rules are applied. + +You can use the Get-CsTenantDialPlan cmdlet to retrieve specific information about the normalization rules of a tenant dial plan. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsTenantDialPlan +``` + +This example retrieves all existing tenant dial plans. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsTenantDialPlan -Identity Vt1TenantDialPlan2 +``` + +This example retrieves the tenant dial plan that has an identity of Vt1TenantDialplan2. + +## PARAMETERS + +### -Filter +The Filter parameter allows you to limit the number of results based on filters you specify. + +```yaml +Type: String +Parameter Sets: (Filter) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter is a unique identifier that designates the name of the tenant dial plan to retrieve. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +The ExternalAccessPrefix and OptimizeDeviceDialing parameters have been removed from New-CsTenantDialPlan and Set-CsTenantDialPlan cmdlet since they are no longer used. External access dialing is now handled implicitly using normalization rules of the dial plans. +The Get-CsTenantDialPlan will still show the external access prefix in the form of a normalization rule of the dial plan. + +## RELATED LINKS + +[Grant-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/grant-cstenantdialplan) + +[New-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/new-cstenantdialplan) + +[Set-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/set-cstenantdialplan) + +[Remove-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/remove-cstenantdialplan) diff --git a/skype/skype-ps/skype/Get-CsTenantFederationConfiguration.md b/teams/teams-ps/teams/Get-CsTenantFederationConfiguration.md similarity index 76% rename from skype/skype-ps/skype/Get-CsTenantFederationConfiguration.md rename to teams/teams-ps/teams/Get-CsTenantFederationConfiguration.md index cd962353d1..8a7b9f790c 100644 --- a/skype/skype-ps/skype/Get-CsTenantFederationConfiguration.md +++ b/teams/teams-ps/teams/Get-CsTenantFederationConfiguration.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenantfederationconfiguration -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantfederationconfiguration +applicable: Microsoft Teams title: Get-CsTenantFederationConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTenantFederationConfiguration @@ -42,7 +42,6 @@ The Get-CsTenantFederationConfiguration cmdlet provides a way for administrators This cmdlet can also be used to review the allowed and blocked lists, lists which are used to specify domains that users can and cannot communicate with. However, administrators must use the Get-CsTenantPublicProvider cmdlet in order to see which public IM and presence providers users are allowed to communicate with. - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -54,14 +53,10 @@ The command shown in Exercise 1 returns federation configuration information for ### -------------------------- Example 2 -------------------------- ``` -Get-CsTenantFederationConfiguration | Select-Object -ExpandProperty AllowedList +Get-CsTenantFederationConfiguration | Select-Object -ExpandProperty AllowedDomains ``` -In Example 2, information is returned for all the domains found on the federation allowed list for the current tenant. -(The allowed list represents all the domains that the tenant is allowed to federate with.) To do this, the command first calls the Get-CsTenantFederationConfiguration cmdlet to return federation information for the specified tenant. -That information is then piped to the Select-Object cmdlet, which uses the ExpandProperty to "expand" the property AllowedList. -Expanding a property simply means displaying all the information stored in that property onscreen, and in an easy-to-read format. - +In Example 2, information is returned for all the allowed domains found on the federation configuration for the current tenant (This list represents all the domains that the tenant is allowed to federate with). To do this, the command first calls the Get-CsTenantFederationConfiguration cmdlet to return federation information for the specified tenant. That information is then piped to the Select-Object cmdlet, which uses the ExpandProperty to "expand" the property AllowedDomains. Expanding a property simply means displaying all the information stored in that property onscreen, and in an easy-to-read format. ## PARAMETERS @@ -75,8 +70,8 @@ However, this is valid syntax for the Get-CsTenantFederationConfiguration cmdlet ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -96,8 +91,8 @@ For example: ```yaml Type: XdsIdentity Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 2 @@ -112,8 +107,8 @@ This parameter is not used with Skype for Business Online. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -139,24 +134,8 @@ The Tenant parameter is primarily for use in a hybrid deployment. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -166,24 +145,18 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### Microsoft.Rtc.Management.WritableConfig.Settings.Edge.TenantFederationSettings - ## NOTES - ## RELATED LINKS -[Get-CsTenantPublicProvider](Get-CsTenantPublicProvider.md) - -[Set-CsTenantFederationConfiguration](Set-CsTenantFederationConfiguration.md) - +[Set-CsTenantFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-cstenantfederationconfiguration) diff --git a/teams/teams-ps/teams/Get-CsTenantLicensingConfiguration.md b/teams/teams-ps/teams/Get-CsTenantLicensingConfiguration.md new file mode 100644 index 0000000000..5eab013035 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantLicensingConfiguration.md @@ -0,0 +1,116 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantlicensingconfiguration +applicable: Microsoft Teams +title: Get-CsTenantLicensingConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsTenantLicensingConfiguration + +## SYNOPSIS +Indicates whether licensing information for the specified tenant is available in the Teams admin center. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTenantLicensingConfiguration [[-Identity] <String>] [-MsftInternalProcessingMode <String>] + [<CommonParameters>] +``` + +### Filter +``` +Get-CsTenantLicensingConfiguration [-MsftInternalProcessingMode <String>] [-Filter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +The Get-CsTenantLicensingConfiguration cmdlet indicates whether licensing information for the specified tenant is available in the Teams admin center. +The cmdlet returns information similar to this: + +Identity : GlobalStatus : Enabled + +If the Status is equal to Enabled then licensing information is available in the admin center. +If not, then licensing information is not available in the admin center. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsTenantLicensingConfiguration +``` + +The command shown in Example 1 returns licensing configuration information for the current tenant: + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters in order to return a collection of tenant licensing configuration settings. +Because each tenant is limited to a single, global collection of licensing configuration settings there is no need to use the Filter parameter. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the collection of tenant licensing configuration settings to be returned. +Because each tenant is limited to a single, global collection of licensing settings there is no need include this parameter when calling the Get-CsTenantLicensingConfiguration cmdlet. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Deserialized.Microsoft.Rtc.Management.WritableConfig.Settings.TenantConfiguration.TenantLicensingConfiguration + +## NOTES + +## RELATED LINKS + +[Get-CsTenant](https://learn.microsoft.com/powershell/module/teams/get-cstenant) diff --git a/teams/teams-ps/teams/Get-CsTenantMigrationConfiguration.md b/teams/teams-ps/teams/Get-CsTenantMigrationConfiguration.md new file mode 100644 index 0000000000..23ce62dd9e --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantMigrationConfiguration.md @@ -0,0 +1,115 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantmigrationconfiguration +applicable: Microsoft Teams +title: Get-CsTenantMigrationConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Get-CsTenantMigrationConfiguration + +## SYNOPSIS +Use the Get-CsTenantMigrationConfiguration cmdlet to check if Meeting Migration Service (MMS) is enabled in your organization. + +## SYNTAX + +``` +Get-CsTenantMigrationConfiguration [-LocalStore] [[-Identity] <XdsIdentity>] [-Tenant <Guid>] [-Filter <String>] + [<CommonParameters>] +``` + +## DESCRIPTION +Meeting Migration Service (MMS) is a Skype for Business service that runs in the background and automatically updates Skype for Business and Microsoft Teams meetings for users. MMS is designed to eliminate the need for users to run the Meeting Migration Tool to update their Skype for Business and Microsoft Teams meetings. This tool does not migrate Skype for Business meetings into Microsoft Teams meetings. + +The Get-CsTenantMigrationConfiguration cmdlet retrieves the Meeting Migration Service configuration in your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Get-CsTenantMigrationConfiguration +``` + +This example shows the MMS configuration in your organization. + +## PARAMETERS + +### -Filter +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter is reserved for internal Microsoft use. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocalStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Set-CsTenantMigrationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-cstenantmigrationconfiguration) diff --git a/teams/teams-ps/teams/Get-CsTenantNetworkConfiguration.md b/teams/teams-ps/teams/Get-CsTenantNetworkConfiguration.md new file mode 100644 index 0000000000..110a8e54cc --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantNetworkConfiguration.md @@ -0,0 +1,127 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworkconfiguration +applicable: Microsoft Teams +title: Get-CsTenantNetworkConfiguration +schema: 2.0.0 +ms.reviewer: +--- + +# Get-CsTenantNetworkConfiguration + +## SYNOPSIS +Returns information about the network regions, sites and subnets in the tenant network configuration. Tenant network configuration is used for Location Based Routing. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTenantNetworkConfiguration [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTenantNetworkConfiguration [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +Tenant Network Configuration contains the list of network sites, subnets and regions configured. + +A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. + +A best practice for Location Based Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity. Each network site must be associated with a network region. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration. + +IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. + +Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first. + +A network region interconnects various parts of a network across multiple geographic areas. + +A network region contains a collection of network sites. For example, if your organization has many sites located in India, then you may choose to designate "India" as a network region. + +Location-Based Routing is a feature that allows PSTN toll bypass to be restricted for users based on policy and the user's geographic location at the time of an incoming or outgoing PSTN call. + +Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in Microsoft 365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTenantNetworkConfiguration +``` +The command shown in Example 1 returns the list of network configuration for the current tenant. + +### Example 2 +```powershell +PS C:\> Get-CsTenantNetworkConfiguration -Identity Global +``` +The command shown in Example 2 returns the network configuration within the scope of Global. + +### Example 3 +```powershell +PS C:\> Get-CsTenantNetworkConfiguration -Filter "global" +``` +The command shown in Example 3 returns the network site that matches the specified filter. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the network configuration (or network configurations) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter is a unique identifier for the network configuration. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Identity +The Identity of the network configuration. + +### NetworkRegions +The list of network regions of the network configuration. + +### NetworkSites +The list of network sites of the network configuration. + +### Subnets +The list of network subnets of the network configuration. + +### PostalCodes +This parameter is reserved for internal Microsoft use. + +## NOTES + +## RELATED LINKS +[Get-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksite) +[Get-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksite) +[Get-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksite) + diff --git a/teams/teams-ps/teams/Get-CsTenantNetworkRegion.md b/teams/teams-ps/teams/Get-CsTenantNetworkRegion.md new file mode 100644 index 0000000000..4e5bac9aa2 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantNetworkRegion.md @@ -0,0 +1,105 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworkregion +applicable: Microsoft Teams +title: Get-CsTenantNetworkRegion +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsTenantNetworkRegion + +## SYNOPSIS +Returns information about the network region setting in the tenant. Tenant network region is used for Location Based Routing. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTenantNetworkRegion [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTenantNetworkRegion [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +A network region interconnects various parts of a network across multiple geographic areas. + +A network region contains a collection of network sites. For example, if your organization has many sites located in India, then you may choose to designate "India" as a network region. + +Location-Based Routing is a feature that allows PSTN toll bypass to be restricted for users based on policy and the user's geographic location at the time of an incoming or outgoing PSTN call. + +Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in Microsoft 365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTenantNetworkRegion +``` + +The command shown in Example 1 returns the list of network regions for the current tenant. + +### Example 2 +```powershell +PS C:\> Get-CsTenantNetworkRegion -Identity RedmondRegion +``` + +The command shown in Example 2 returns the network region within the scope of RedmondRegion. + +## PARAMETERS + +### -Filter +The Filter parameter allows you to limit the number of results based on filters you specify. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network region to be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworkregion) + +[Remove-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworkregion) + +[Set-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworkregion) diff --git a/teams/teams-ps/teams/Get-CsTenantNetworkSite.md b/teams/teams-ps/teams/Get-CsTenantNetworkSite.md new file mode 100644 index 0000000000..140fb2c326 --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantNetworkSite.md @@ -0,0 +1,172 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksite +applicable: Microsoft Teams +title: Get-CsTenantNetworkSite +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsTenantNetworkSite + +## SYNOPSIS +Returns information about the network site setting in the tenant. Tenant network site is used for Location Based Routing. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTenantNetworkSite [[-Identity] <string>] [-IncludePhoneNumbers <bool>] [<CommonParameters>] +``` + +### QueryParameter +``` +Get-CsTenantNetworkSite [-IncludePhoneNumbers <bool>] [-Filter <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTenantNetworkSite [-IncludePhoneNumbers <bool>] [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. + +A best practice for Location Bsed Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity. Each network site must be associated with a network region. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration. + +Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user's geographic location at the time of an incoming or outgoing PSTN call. + +Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTenantNetworkSite +``` +The command shown in Example 1 returns the list of network sites for the current tenant. + +### Example 2 +```powershell +PS C:\> Get-CsTenantNetworkSite -Identity siteA +``` +The command shown in Example 2 returns the network site within the scope of siteA. + +### Example 3 +```powershell +PS C:\> Get-CsTenantNetworkSite -Filter "Los Angeles" +``` +The command shown in Example 3 returns the network site that matches the specified filter. + +## PARAMETERS + +### -Filter +Enables you to use wildcard characters when indicating the site (or sites) to be returned. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter is a unique identifier for the site. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludePhoneNumbers +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: All +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Identity +The Identity of the site. + +### Description +The description of the site. + +### NetworkRegionID +The network region ID of the site. + +### LocationPolicyID +The ID of the location policy assigned to the site. + +### SiteAddress +This parameter is reserved for internal Microsoft use. + +### NetworkSiteID +The ID of the network site. + +### OnlineVoiceRoutingPolicyTagID +The ID of the online voice routing policy assigned to the site. + +### EnableLocationBasedRouting +Boolean stating whether Location-Based Routing is enabled on the site. + +### EmergencyCallRoutingPolicyTagID +The ID of the Teams emergency call routing policy assigned to the site. + +### EmergencyCallingPolicyTagID +The ID of the Teams emergency calling policy assigned to the site. + +### NetworkRoamingPolicyTagID +The ID of the Teams network roaming policy assigned to the site. + +### EmergencyCallRoutingPolicyName +The name of the Teams emergency call routing policy assigned to the site. + +### EmergencyCallingPolicyName +The name of the Teams emergency calling policy assigned to the site. + +### NetworkRoamingPolicyName +The name of the Teams network roaming policy assigned to the site. + +### PhoneNumbers +This parameter is reserved for internal Microsoft use. + +## NOTES +The parameter IncludePhoneNumbers was introduced in Teams PowerShell Module 5.5.0. + +## RELATED LINKS +[New-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksite) + +[Remove-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksite) + +[Set-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksite) diff --git a/teams/teams-ps/teams/Get-CsTenantNetworkSubnet.md b/teams/teams-ps/teams/Get-CsTenantNetworkSubnet.md new file mode 100644 index 0000000000..451655976b --- /dev/null +++ b/teams/teams-ps/teams/Get-CsTenantNetworkSubnet.md @@ -0,0 +1,104 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksubnet +applicable: Microsoft Teams +title: Get-CsTenantNetworkSubnet +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Get-CsTenantNetworkSubnet + +## SYNOPSIS +Returns information about the network subnet setting in the tenant. Tenant network subnet is used for Location Based Routing. + +## SYNTAX + +### Identity (Default) +``` +Get-CsTenantNetworkSubnet [[-Identity] <string>] [<CommonParameters>] +``` + +### Filter +``` +Get-CsTenantNetworkSubnet [-Filter <string>] [<CommonParameters>] +``` + +## DESCRIPTION +IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. + +Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first. + +Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user's geographic location at the time of an incoming or outgoing PSTN call. + +Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTenantNetworkSubnet +``` + +The command shown in Example 1 returns the list of network subnets for the current tenant. + +### Example 2 +```powershell +PS C:\> Get-CsTenantNetworkSubnet -Identity '2001:4898:e8:25:844e:926f:85ad:dd70' +``` + +The command shown in Example 2 returns the IPv6 format network subnet within the scope of '2001:4898:e8:25:844e:926f:85ad:dd70'. + +## PARAMETERS + +### -Identity +The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network subnets to be returned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Filter +The Filter parameter allows you to limit the number of results based on filters you specify. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksubnet) + +[Remove-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksubnet) + +[Set-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksubnet) diff --git a/skype/skype-ps/skype/Get-CsTenantTrustedIPAddress.md b/teams/teams-ps/teams/Get-CsTenantTrustedIPAddress.md similarity index 93% rename from skype/skype-ps/skype/Get-CsTenantTrustedIPAddress.md rename to teams/teams-ps/teams/Get-CsTenantTrustedIPAddress.md index d861b51cb5..178e4bd1fa 100644 --- a/skype/skype-ps/skype/Get-CsTenantTrustedIPAddress.md +++ b/teams/teams-ps/teams/Get-CsTenantTrustedIPAddress.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-cstenanttrustedipaddress -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-cstenanttrustedipaddress +applicable: Microsoft Teams title: Get-CsTenantTrustedIPAddress schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsTenantTrustedIPAddress @@ -33,7 +33,7 @@ External trusted IPs are the Internet external IPs of the enterprise network and If the user's external IP matches one defined in the trusted list, then Location-Based Routing will check to determine which internal subnet the user's endpoint is located. If the user's external IP doesn't match one defined in the trusted list, the endpoint will be classified as being at an unknown and any PSTN calls to/from an LBR enabled user are blocked. -Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user's geographic location at the time of an incoming or outgoing PSTN call. +Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user's geographic location at the time of an incoming or outgoing PSTN call. Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user's location is determined by the IP subnet which the user's Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client's routing separately depending on the location of its endpoint. @@ -116,8 +116,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -126,6 +125,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-CsUserCallingSettings.md b/teams/teams-ps/teams/Get-CsUserCallingSettings.md new file mode 100644 index 0000000000..43b422011c --- /dev/null +++ b/teams/teams-ps/teams/Get-CsUserCallingSettings.md @@ -0,0 +1,249 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-csusercallingsettings +applicable: Microsoft Teams +title: Get-CsUserCallingSettings +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Get-CsUserCallingSettings + +## SYNOPSIS +This cmdlet will show the call forwarding, simultaneous ringing, call group and delegation settings for a user. + +## SYNTAX + +```powershell +Get-CsUserCallingSettings -Identity <String> [<CommonParameters>] + +``` + +## DESCRIPTION +This cmdlet shows the call forwarding, simultaneous ringing, call group and delegation settings for a user. It will also show any call groups the user is a member of and +if someone else has added the user as a delegate. + +## EXAMPLES + +### Example 1 +```powershell +Get-CsUserCallingSettings -Identity user1@contoso.com +``` +```output +SipUri : sip:user1@contoso.com +IsForwardingEnabled : True +ForwardingType : Immediate +ForwardingTarget : +ForwardingTargetType : Voicemail +IsUnansweredEnabled : False +UnansweredTarget : +UnansweredTargetType : Voicemail +UnansweredDelay : 00:00:20 +Delegates : +Delegators : +CallGroupOrder : InOrder +CallGroupTargets : {} +GroupMembershipDetails : +GroupNotificationOverride : +``` + +This example shows that user1@contoso.com has immediate call forwarding set (IsForwardingEnabled and ForwardingType) to route all incoming calls to voicemail (ForwardingTargetType). + +### Example 2 +```powershell +Get-CsUserCallingSettings -Identity user2@contoso.com +``` +```output +SipUri : sip:user2@contoso.com +IsForwardingEnabled : True +ForwardingType : Simultaneous +ForwardingTarget : sip:user3@contoso.com +ForwardingTargetType : SingleTarget +IsUnansweredEnabled : True +UnansweredTarget : +UnansweredTargetType : Voicemail +UnansweredDelay : 00:00:20 +Delegates : +Delegators : +CallGroupOrder : InOrder +CallGroupTargets : {} +GroupMembershipDetails : +GroupNotificationOverride : +``` + +This example shows that user2@contoso.com has simultaneous ringing set (IsForwardingEnabled and ForwardingType) to user3@contoso.com +(ForwardingTarget and ForwardingTargetType) and if the call has not been answered (IsUnansweredEnabled) within 20 seconds (UnansweredDelay) the call is routed +to voicemail (UnansweredTargetType). + +### Example 3 +```powershell +Get-CsUserCallingSettings -Identity user4@contoso.com +``` +```output +SipUri : sip:user4@contoso.com +IsForwardingEnabled : True +ForwardingType : Simultaneous +ForwardingTarget : +ForwardingTargetType : Group +IsUnansweredEnabled : True +UnansweredTarget : +UnansweredTargetType : Voicemail +UnansweredDelay : 00:00:20 +Delegates : +Delegators : +CallGroupOrder : InOrder +CallGroupTargets : {sip:user5@contoso.com} +GroupMembershipDetails : CallGroupOwnerId:sip:user6@contoso.com +GroupNotificationOverride : Mute +``` +```powershell +(Get-CsUserCallingSettings -Identity user4@contoso.com).GroupMembershipDetails +``` +```output +CallGroupOwnerId NotificationSetting +---------------- ------------------- +sip:user6@contoso.com Ring +``` + +This example shows that user4@contoso.com has simultaneous ringing set to his/her call group (ForwardingTargetType) and that the call group contains user5@contoso.com +(CallGroupTargets). The call group is defined to ring members in the order listed in the call group (CallGroupOrder). + +You can also see that user4@contoso.com is a member of user6@contoso.com's call group (GroupMembershipDetails), that user6@contoso.com defined the call group with Ring +notification for user4@contoso.com (NotificationSetting) and that user4@contoso.com has decided to turn off call notification for call group calls (GroupNotificationOverride). + +### Example 4 +```powershell +Get-CsUserCallingSettings -Identity user7@contoso.com +``` +```output +SipUri : sip:opr7@contoso.com +IsForwardingEnabled : True +ForwardingType : Simultaneous +ForwardingTarget : +ForwardingTargetType : MyDelegates +IsUnansweredEnabled : True +UnansweredTarget : +UnansweredTargetType : Voicemail +UnansweredDelay : 00:00:20 +Delegates : Id:sip:user8@contoso.com +Delegators : +CallGroupOrder : InOrder +CallGroupTargets : {} +GroupMembershipDetails : +GroupNotificationOverride : Ring +``` +```powershell +(Get-CsUserCallingSettings -Identity user7@contoso.com).Delegates +``` +```output +Id : sip:user8@contoso.com +MakeCalls : True +ManageSettings : True +ReceiveCalls : True +``` + +This example shows that user7@contoso.com has simultaneous ringing set to his/her delegates (ForwardingTargetType). User8@contoso.com is the only delegate +(Delegates) and that user has all the permissions you can have as a delegate (Delegates). + +### Example 5 +```powershell +Get-CsUserCallingSettings -Identity user9@contoso.com +``` +```output +SipUri : sip:user9@contoso.com +IsForwardingEnabled : False +ForwardingType : Immediate +ForwardingTarget : +ForwardingTargetType : Voicemail +IsUnansweredEnabled : True +UnansweredTarget : +UnansweredTargetType : Voicemail +UnansweredDelay : 00:00:20 +Delegates : +Delegators : Id:sip:user10@contoso.com +CallGroupOrder : InOrder +CallGroupTargets : {} +GroupMembershipDetails : +GroupNotificationOverride : Ring +``` +```powershell +(Get-CsUserCallingSettings -Identity user9@contoso.com).Delegators +``` +```output +Id : sip:user10@contoso.com +MakeCalls : True +ManageSettings : True +ReceiveCalls : True +``` + +This example shows that user9@contoso.com is a delegate of user10@contoso.com (Delegators) and that user10@contoso.com has given user9@contoso.com all the +permissions you can have as a delegate (Delegators). + +### Example 6 +```powershell +Get-CsUserCallingSettings -Identity user11@contoso.com +``` +```output +SipUri : sip:user11@contoso.com +IsForwardingEnabled : +ForwardingType : +ForwardingTarget : +ForwardingTargetType : +IsUnansweredEnabled : +UnansweredTarget : +UnansweredTargetType : +UnansweredDelay : 00:00:20 +Delegates : +Delegators : +CallGroupOrder : Simultaneous +CallGroupTargets : {} +GroupMembershipDetails : +GroupNotificationOverride : +``` + +This example shows the default settings for a user that has never changed the call forward settings via Microsoft Teams. Note that for users with settings as shown here, +unanswered calls will by default be forwarded to voicemail after 30 seconds. + +## PARAMETERS + +### -Identity +The Identity of the user to show call forwarding, simultaneous ringing, call group and delegation settings for. Can be specified using the ObjectId or the SIP address. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PowerShell module 4.0.0 or later. + +## RELATED LINKS + +[Set-CsUserCallingSettings](https://learn.microsoft.com/powershell/module/teams/set-csusercallingsettings) + +[New-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/new-csusercallingdelegate) + +[Set-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/set-csusercallingdelegate) + +[Remove-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/remove-csusercallingdelegate) diff --git a/teams/teams-ps/teams/Get-CsUserPolicyAssignment.md b/teams/teams-ps/teams/Get-CsUserPolicyAssignment.md index 1575676cf4..692be05e33 100644 --- a/teams/teams-ps/teams/Get-CsUserPolicyAssignment.md +++ b/teams/teams-ps/teams/Get-CsUserPolicyAssignment.md @@ -1,25 +1,34 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-csuserpolicyassignment +online version: https://learn.microsoft.com/powershell/module/teams/get-csuserpolicyassignment +title: Get-CsUserPolicyAssignment schema: 2.0.0 author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsUserPolicyAssignment ## SYNOPSIS -**Note:** This cmdlet is currently in public preview. - This cmdlet is used to return the policy assignments for a user, both directly assigned and inherited from a group. ## SYNTAX +### Get (Default) +``` +Get-CsUserPolicyAssignment -Identity <String> [-PolicyType <String>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] +``` + +### GetViaIdentity ``` -Get-CsUserPolicyAssignment -Identity <String> [-PolicyType <String>] +Get-CsUserPolicyAssignment -InputObject <IIc3AdminConfigRpPolicyIdentity> [-PolicyType <String>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [<CommonParameters>] ``` ## DESCRIPTION @@ -69,7 +78,6 @@ AssignmentType PolicyName Reference Group AllOn d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 Group Kiosk 566b8d39-5c5c-4aaa-bc07-4f36278a1b38 - Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy GroupId PolicyType PolicyName Rank CreatedTime CreatedBy @@ -83,9 +91,11 @@ d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 TeamsMeetingPolicy AllOn 1 10/29/20 ### -Identity The identify of the user whose policy assignments will be returned. +The -Identity parameter can be in the form of the users ObjectID (taken from Microsoft Entra ID) or in the form of the UPN (a.smith@example.com) + ```yaml Type: String -Parameter Sets: +Parameter Sets: Get Aliases: Required: True @@ -95,12 +105,73 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -InputObject +Identity Parameter +To construct, see NOTES section for INPUTOBJECT properties and create a hash table. + +```yaml +Type: IIc3AdminConfigRpPolicyIdentity +Parameter Sets: GetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + ### -PolicyType Use to filter to a specific policy type. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Break +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) Aliases: Required: False @@ -110,20 +181,76 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Proxy +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS +### Microsoft.Teams.Config.Cmdlets.Models.IIc3AdminConfigRpPolicyIdentity ## OUTPUTS +### Microsoft.Teams.Config.Cmdlets.Models.IEffectivePolicy ## NOTES +COMPLEX PARAMETER PROPERTIES + +To create the parameters described below, construct a hash table containing the appropriate properties. +For information on hash tables, run Get-Help about_Hash_Tables. + +INPUTOBJECT \<IIc3AdminConfigRpPolicyIdentity\>: Identity Parameter + \[GroupId \<String\>\]: The ID of a group whose policy assignments will be returned. + \[Identity \<String\>\]: + \[OperationId \<String\>\]: The ID of a batch policy assignment operation. + \[PolicyType \<String\>\]: The policy type for which group policy assignments will be returned. ## RELATED LINKS -[New-CsGroupPolicyAssignment]() +[New-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment) -[Set-CsGroupPolicyAssignment]() +[Set-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/set-csgrouppolicyassignment) -[Remove-CsGroupPolicyAssignment]() +[Remove-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csgrouppolicyassignment) diff --git a/teams/teams-ps/teams/Get-CsUserPolicyPackage.md b/teams/teams-ps/teams/Get-CsUserPolicyPackage.md index 17bb57361f..c0edaf3689 100644 --- a/teams/teams-ps/teams/Get-CsUserPolicyPackage.md +++ b/teams/teams-ps/teams/Get-CsUserPolicyPackage.md @@ -1,13 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -applicable: Microsoft Teams title: Get-CsUserPolicyPackage -author: icchan -ms.author: icchan -ms.reviewer: etgottli +author: serdarsoysal +ms.author: serdars manager: amitar -online version: https://docs.microsoft.com/powershell/module/teams/get-csuserpolicypackage +online version: https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackage schema: 2.0.0 --- @@ -26,7 +24,7 @@ Get-CsUserPolicyPackage [-Identity] <String> [<CommonParameters>] ## DESCRIPTION This cmdlet supports retrieving the policy package that's assigned to a user. Provide the identity of a user to retrieve the definition of their assigned policy package. -For more information on policy packages, please review https://docs.microsoft.com/en-us/MicrosoftTeams/manage-policy-packages +For more information on policy packages, please review https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages. ## EXAMPLES @@ -66,8 +64,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Get-CsPolicyPackage](Get-CsPolicyPackage.md) +[Get-CsPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage) -[Get-CsUserPolicyPackageRecommendation](Get-CsUserPolicyPackageRecommendation.md) +[Get-CsUserPolicyPackageRecommendation](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackagerecommendation) -[Grant-CsUserPolicyPackage](Grant-CsUserPolicyPackage.md) +[Grant-CsUserPolicyPackage](https://learn.microsoft.com/powershell/module/teams/grant-csuserpolicypackage) diff --git a/teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md b/teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md index f07cc0073d..ca19b2c0d9 100644 --- a/teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md +++ b/teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md @@ -1,13 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -applicable: Microsoft Teams title: Get-CsUserPolicyPackageRecommendation -author: etgottli -ms.author: etgottli -ms.reviewer: icchan +author: serdarsoysal +ms.author: serdars manager: amitar -online version: https://docs.microsoft.com/powershell/module/teams/get-csuserpolicypackagerecommendation +online version: https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackagerecommendation schema: 2.0.0 --- @@ -26,7 +24,7 @@ Get-CsUserPolicyPackageRecommendation [-Identity] <String> [<CommonParameters>] ## DESCRIPTION This cmdlet supports retrieving recommendations for which policy packages are best suited for a given user. This recommendation is based on tenant and user information such as license types. -For more information on policy packages, please review https://docs.microsoft.com/en-us/MicrosoftTeams/manage-policy-packages +For more information on policy packages, please review https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages. ## EXAMPLES @@ -66,8 +64,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Get-CsPolicyPackage](Get-CsPolicyPackage.md) +[Get-CsPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage) -[Get-CsUserPolicyPackage](Get-CsUserPolicyPackage.md) +[Get-CsUserPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackage) -[Grant-CsUserPolicyPackage](Grant-CsUserPolicyPackage.md) +[Grant-CsUserPolicyPackage](https://learn.microsoft.com/powershell/module/teams/grant-csuserpolicypackage) diff --git a/skype/skype-ps/skype/Get-CsVideoInteropServiceProvider.md b/teams/teams-ps/teams/Get-CsVideoInteropServiceProvider.md similarity index 89% rename from skype/skype-ps/skype/Get-CsVideoInteropServiceProvider.md rename to teams/teams-ps/teams/Get-CsVideoInteropServiceProvider.md index f5cce46755..2210e9d40f 100644 --- a/skype/skype-ps/skype/Get-CsVideoInteropServiceProvider.md +++ b/teams/teams-ps/teams/Get-CsVideoInteropServiceProvider.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/get-csvideointeropserviceprovider -applicable: Skype for Business Online -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/get-csvideointeropserviceprovider +applicable: Microsoft Teams +Module Name: MicrosoftTeams title: Get-CsVideoInteropServiceProvider schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Get-CsVideoInteropServiceProvider @@ -16,7 +16,6 @@ ms.reviewer: ## SYNOPSIS Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. The CsVideoInteropServiceProvider cmdlets allow you to designate provider/tenant specific information about the connection to the provider. - ## SYNTAX ### Identity (Default) @@ -105,14 +104,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Get-LicenseReportForChangeNotificationSubscription.md b/teams/teams-ps/teams/Get-LicenseReportForChangeNotificationSubscription.md new file mode 100644 index 0000000000..445cec3c6a --- /dev/null +++ b/teams/teams-ps/teams/Get-LicenseReportForChangeNotificationSubscription.md @@ -0,0 +1,53 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Get-LicenseReportForChangeNotificationSubscription +author: serdarsoysal +ms.author: serdars +manager: alagra +online version: https://learn.microsoft.com/powershell/module/teams/get-licensereportforchangenotificationsubscription +schema: 2.0.0 +--- + +# Get-LicenseReportForChangeNotificationSubscription + +## SYNOPSIS + +This cmdlet tells whether a user has the required license to export their messages via [change notification subscription](https://learn.microsoft.com/graph/teams-licenses). + +## SYNTAX + +``` +Get-LicenseReportForChangeNotificationSubscription [-Period] <Number> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet supports retrieving the total number of messages sent by a user in chat/channel and whether a user has the required license(s) to send change notification events when subscribed for chat or channel messages. For more details, please review [Licenses for subscribing to chat messages](https://learn.microsoft.com/graph/teams-licenses). +This cmdlet is currently supported in preview version only. + +## EXAMPLES + +### Example +```powershell +PS C:\> Get-LicenseReportForChangeNotificationSubscription -Period 7 +``` + +Returns license info and total messages sent by users in the last 7 days. + +## PARAMETERS + +### -Period + +Number of days prior to today. Acceptable values are 7, 30, 90 and 180. + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-M365TeamsApp.md b/teams/teams-ps/teams/Get-M365TeamsApp.md new file mode 100644 index 0000000000..2d665c2c79 --- /dev/null +++ b/teams/teams-ps/teams/Get-M365TeamsApp.md @@ -0,0 +1,128 @@ +--- +external help file: Microsoft.Teams.PowerShell.TeamsCmdlets.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://docs.microsoft.com/powershell/module/teams/Get-M365TeamsApp +applicable: Microsoft Teams +title: Get-M365TeamsApp +author: lkueter +ms.author: sribagchi +manager: rahulrgupta +schema: 2.0.0 +--- + +# Get-M365TeamsApp + +## SYNOPSIS + +This cmdlet returns app availability and state for the Microsoft Teams app. + +## SYNTAX + +```powershell +Get-M365TeamsApp -Id <String> [<CommonParameters>] +``` + +## DESCRIPTION + +Get-M365TeamsApps retrieves information about the Teams app. This includes app state, app availability, user who updated app availability, and the associated timestamp. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-M365TeamsApp -Id b782e2e8-9682-4898-b211-a304714f4f6b +``` + +Provides information about b782e2e8-9682-4898-b211-a304714f4f6b app, which includes app state, app availability, user who updated app availability, and the associated timestamp. + +## PARAMETERS + +### -Id + +Application ID of the Teams app. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +**ID** +Application ID of the Teams app. + +**IsBlocked** +The state of the app in the tenant. +Values: + +- Blocked +- Unblocked + +**AvailableTo** +Provides available to properties for the app. +Properties: + +- AssignmentType: App availability type. + Values: + - Everyone + - UsersandGroups + - Noone +- Users: List of all the users for whom the app is enabled. + Values: + - Id: GUID of UserIDs. + - AssignedBy: UserID of last user who updated the app AvailableTo value. + - LastUpdatedTimeStamp: Time and date when the app AvailableTo value was last updated. +- Groups: List of all the groups for whom the app is enabled. + Values: + - Id: GUID of GroupIDs. + - AssignedBy: UserID of last user who updated the app AvailableTo value. + - LastUpdatedTimeStamp: Time and date when the app AvailableTo value was last updated. + +**InstalledFor** +Provides installed for properties for the app. +Properties: + +- AppInstallType: App install type. + Values: + - Everyone + - UsersandGroups + - Noone +- LastUpdatedTimestamp: Last Updated date +- InstalledBy: The user performing the installation +- InstalledSource: Source of installation +- Version: Version of the app installed +- InstallForUsers: List of all the users for whom the app is enabled. + Values: + - Id: GUID of UserIDs. + - AssignedBy: UserID of last user who updated the app AvailableTo value. + - LastUpdatedTimeStamp: Time and date when the app AvailableTo value was last updated. +- InstallForGroups: List of all the groups for whom the app is enabled. + Values: + - Id: GUID of GroupIDs. + - AssignedBy: UserID of last user who updated the app AvailableTo value. + - LastUpdatedTimeStamp: Time and date when the app AvailableTo value was last updated. + +## NOTES + +## RELATED LINKS + +[Get-AllM365TeamsApps](https://learn.microsoft.com/powershell/module/teams/get-allm365teamsapps) +[Update-M365TeamsApp](https://learn.microsoft.com/powershell/module/teams/get-allm365teamsapps) diff --git a/teams/teams-ps/teams/Get-M365UnifiedCustomPendingApps.md b/teams/teams-ps/teams/Get-M365UnifiedCustomPendingApps.md new file mode 100644 index 0000000000..0e4deaa2f7 --- /dev/null +++ b/teams/teams-ps/teams/Get-M365UnifiedCustomPendingApps.md @@ -0,0 +1,77 @@ +--- +external help file: Microsoft.Teams.PowerShell.TeamsCmdlets.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://docs.microsoft.com/powershell/module/teams/Get-M365UnifiedCustomPendingApps +applicable: Microsoft Teams +title: Get-M365UnifiedCustomPendingApps +author: michelle-paradis +ms.author: mparadis +manager: swmerchant +ms.date: 01/14/2025 +schema: 2.0.0 +--- + +# Get-M365UnifiedCustomPendingApps + +## SYNOPSIS + +This cmdlet returns all custom Microsoft Teams apps that are pending review from an IT Admin. + +## SYNTAX + +```powershell +Get-M365UnifiedCustomPendingApps [<CommonParameters>] +``` + +## DESCRIPTION + +Get-M365UnifiedCustomPendingApps retrieves a complete list of all custom Microsoft Teams apps that are pending review, and their review statuses. + +## EXAMPLES + +### Example + +```powershell +PS C:\> Get-M365UnifiedCustomPendingApps +``` + +Returns a complete list of all custom Microsoft Teams apps that are pending review, and their review statuses. + +## 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +**Id**: +Application ID of the Teams app. + +**ExternalId**: +External ID of the Teams app. + +**Iteration**: +The Staged App Definition Etag of the app. This is a unique tag created everytime the staged app is updated, to help track changes. + +**CreatedBy**: +The User ID of the user that created the app. + +**LastUpdateDateTime**: +The date and time the app was last updated. + +**ReviewStatus**: +The review status of the app. +Values: + +- PendingPublishing: A new custom app was requested that hasn't been published before. +- PendingUpdate: An existing custom app that was previously published and now has an update. + +**Metadata**: +The metadata of the app. diff --git a/teams/teams-ps/teams/Get-M365UnifiedTenantSettings.md b/teams/teams-ps/teams/Get-M365UnifiedTenantSettings.md new file mode 100644 index 0000000000..c67594e6ff --- /dev/null +++ b/teams/teams-ps/teams/Get-M365UnifiedTenantSettings.md @@ -0,0 +1,104 @@ +--- +external help file: Microsoft.Teams.PowerShell.TeamsCmdlets.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://docs.microsoft.com/powershell/module/teams/Get-M365UnifiedTenantSettings +applicable: Microsoft Teams +title: Get-M365UnifiedTenantSettings +author: lkueter +ms.author: sribagchi +manager: rahulrgupta +ms.date: 10/22/2024 +schema: 2.0.0 +--- + +# Get-M365UnifiedTenantSettings + +## SYNOPSIS + +This cmdlet returns the current tenant settings for a particular tenant + +## SYNTAX + +```powershell +Get-M365UnifiedTenantSettings -SettingNames <String[]> [<CommonParameters>] +``` + +## DESCRIPTION + +Get-M365UnifiedTenantSettings retrieves the current tenant settings for a particular tenant. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-M365UnifiedTenantSettings +``` + +Returns all the current tenant settings for this tenant. + +### Example 2 + +```powershell +PS C:\> Get-M365UnifiedTenantSettings -SettingNames DefaultApp +``` + +Returns the current tenant setting for DefaultApp for this tenant. + +### Example 3 + +```powershell +PS C:\> Get-M365UnifiedTenantSettings -SettingNames DefaultApp,EnableCopilotExtensibility +``` + +Returns the current tenant setting for DefaultApp and EnableCopilotExtensibility for this tenant. + +## PARAMETERS + +### -SettingNames + +Setting names requested. Possible values - DefaultApp,GlobalApp,PrivateApp,EnableCopilotExtensibility + +```yaml +Type: String +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +**SettingName** +Setting Name returned. + +**SettingValue** +The status of this setting in the tenant. +Values: + +- All +- None +- Some (only applicable for EnableCopilotExtensibility) + +**Users** +The list of users this setting is applicable to (only applicable for EnableCopilotExtensibility). + +**Groups** +The list of groups this setting is applicable to (only applicable for EnableCopilotExtensibility). + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-SharedWithTeam.md b/teams/teams-ps/teams/Get-SharedWithTeam.md new file mode 100644 index 0000000000..4728ffa1b4 --- /dev/null +++ b/teams/teams-ps/teams/Get-SharedWithTeam.md @@ -0,0 +1,104 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-sharedwithteam +title: Get-SharedWithTeam +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: dedaniel, robharad +--- + +# Get-SharedWithTeam + +## SYNOPSIS +This cmdlet supports retrieving teams with which a specified channel is shared. + +## SYNTAX +```PowerShell +Get-SharedWithTeam -HostTeamId <String> -ChannelId <String> [-SharedWithTeamId <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet supports retrieving teams with which a specified channel is shared. + +## EXAMPLES + +### Example 1 +```PowerShell +Get-AssociatedTeam -HostTeamId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 -ChannelId 19:cUfyYYw3h_t-1KG8-WkvVa7KLEsIx-JHmyeG43VJojg1@thread.tacv2 +``` + +Returns teams with which a specified channel is shared. + +### Example 2 +```PowerShell +Get-AssociatedTeam -HostTeamId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 -ChannelId 19:cUfyYYw3h_t-1KG8-WkvVa7KLEsIx-JHmyeG43VJojg1@thread.tacv2 +-SharedWithTeam d2aad370-c6ca-438b-b4d7-05f0aa911a7b +``` + +Returns detail of a team with which a specified channel is shared. + +## PARAMETERS + +### -HostTeamId +Team ID of the host team (Group ID). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ChannelId +Thread ID of the shared channel. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -SharedWithTeamId +Team ID of the shared with team. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### HostTeamId, ChannelId, SharedWithTeamId + +## OUTPUTS + +### Team + +## NOTES + +## RELATED LINKS +[Get-Team](https://learn.microsoft.com/powershell/module/teams/get-team) +[Get-AssociatedTeam](https://learn.microsoft.com/powershell/module/teams/get-team) diff --git a/teams/teams-ps/teams/Get-SharedWithTeamUser.md b/teams/teams-ps/teams/Get-SharedWithTeamUser.md new file mode 100644 index 0000000000..4a3f016867 --- /dev/null +++ b/teams/teams-ps/teams/Get-SharedWithTeamUser.md @@ -0,0 +1,119 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-sharedwithteamuser +title: Get-SharedWithTeamUser +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: dedaniel, robharad +--- + +# Get-SharedWithTeamUser + +## SYNOPSIS +This cmdlet supports retrieving users of a shared with team. + +## SYNTAX +```PowerShell +Get-SharedWithTeamUser -HostTeamId <String> -ChannelId <String> -SharedWithTeamId <String> [-Role <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet supports retrieving users of a shared with team. + +## EXAMPLES + +### Example 1 +```PowerShell +Get-SharedWithTeamUser -HostTeamId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 -ChannelId 19:cUfyYYw3h_t-1KG8-WkvVa7KLEsIx-JHmyeG43VJojg1@thread.tacv2 +-SharedWithTeam d2aad370-c6ca-438b-b4d7-05f0aa911a7b +``` + +Returns users of a team with which a specified channel is shared. + +### Example 2 +```PowerShell +Get-AssociatedTeam -HostTeamId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 -ChannelId 19:cUfyYYw3h_t-1KG8-WkvVa7KLEsIx-JHmyeG43VJojg1@thread.tacv2 +-SharedWithTeam d2aad370-c6ca-438b-b4d7-05f0aa911a7b -Role owner +``` + +Returns owners of a team with which a specified channel is shared. + +## PARAMETERS + +### -HostTeamId +Team ID of the host team (Group ID). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ChannelId +Thread ID of the shared channel. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -SharedWithTeamId +Team ID of the shared with team. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Role +Filters the results to only users with the given role of "Owner" or "Member". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### HostTeamId, ChannelId, SharedWithTeamId + +## OUTPUTS + +### User + +## NOTES + +## RELATED LINKS +[Get-TeamUser](https://learn.microsoft.com/powershell/module/teams/get-teamuser) diff --git a/teams/teams-ps/teams/Get-Team.md b/teams/teams-ps/teams/Get-Team.md index 0c3e10ea68..b2edb13e51 100644 --- a/teams/teams-ps/teams/Get-Team.md +++ b/teams/teams-ps/teams/Get-Team.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-team +online version: https://learn.microsoft.com/powershell/module/teams/get-team +title: Get-Team schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -19,20 +20,20 @@ This cmdlet supports retrieving teams with particular properties/information, in ### Identity ``` Get-Team -GroupId <String> [-User <String>] [-Archived <Boolean>] [-Visibility <String>] - [-DisplayName <String>] [-MailNickName <String>] [<CommonParameters>] + [-DisplayName <String>] [-MailNickName <String>] [<CommonParameters>] [-NumberOfThreads <Int32>] ``` ### Filters ``` Get-Team [-User <String>] [-Archived <Boolean>] [-Visibility <String>] [-DisplayName <String>] - [-MailNickName <String>] [<CommonParameters>] + [-MailNickName <String>] [<CommonParameters>] [-NumberOfThreads <Int32>] ``` ## DESCRIPTION This cmdlet supports retrieving teams with particular properties/information, including all teams that a specific user belongs to, all teams that have been archived, all teams with a specific display name, or all teams in the organization. ->[!NOTE] ->Depending on the number of teams and O365 Groups in your organization and which filters you are using, this cmdlet can take upwards of ten minutes to run. Some of the input parameters are guaranteed unique (e.g. GroupId), and others serve as filters (e.g. -Archived). +> [!NOTE] +> Get-Team may return multiple results matching the input and not just the exact match for attributes like DisplayName/MailNickName. This is known behavior. ## EXAMPLES @@ -53,13 +54,20 @@ Returns all teams that are private and have been archived. ``` PS> Get-Team -MailNickName "BusinessDevelopment" ``` -Returns the team that matches the specified MailNickName +Returns the team with the specified MailNickName. (This acts as a filter rather than an exact match.) ### Example 4 ``` PS> Get-Team -DisplayName "Sales and Marketing" ``` -Returns the team that matches the specified DisplayName +Returns the team that includes the specified text in its DisplayName. (This acts as a filter rather than an exact match). + +### Example 5 +``` +PS> $team=[uri]::EscapeDataString('AB&C') +PS> Get-Team -DisplayName $team +``` +Returns the team that includes the specified escaped representation of its DisplayName, useful when the DisplayName has special characters. (This acts as a filter rather than an exact match.) ## PARAMETERS @@ -119,7 +127,7 @@ Accept wildcard characters: False ``` ### -DisplayName -Filters to return teams with a full match to the provided displayname. As displayname is not unique, this acts as a filter rather than an exact match. Note that this filter value is case-sensitive. +Specify this parameter to return teams with the provided display name as a filter. As the display name is not unique, multiple values can be returned. Note that this filter value is case-sensitive. ```yaml Type: String @@ -161,7 +169,7 @@ Accept wildcard characters: False ``` ### -MailNickName -Specify the mailnickname of the team that is being returned. This is a unique identifier and returns exact match. +Specify the mailnickname of the team that is being returned. This acts as a filter instead of being an exact match. ```yaml Type: String @@ -214,9 +222,23 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -NumberOfThreads +Specifies the number of threads to use. If you have sufficient network bandwidth and want to decrease the time required to retrieve the list of teams, use the -NumberOfThreads parameter, which supports a value from 1 through 20. + +```yaml +Type: Int32 +Parameter Sets: All +Aliases: + +Required: False +Position: Named +Default value: 20 +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -230,7 +252,6 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[New-Team](new-team.md) - -[Set-Team](set-team.md) +[New-Team](https://learn.microsoft.com/powershell/module/teams/new-team) +[Set-Team](https://learn.microsoft.com/powershell/module/teams/set-team) diff --git a/teams/teams-ps/teams/Get-TeamAllChannel.md b/teams/teams-ps/teams/Get-TeamAllChannel.md new file mode 100644 index 0000000000..eae8aeb08e --- /dev/null +++ b/teams/teams-ps/teams/Get-TeamAllChannel.md @@ -0,0 +1,88 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-teamallchannel +title: Get-TeamAllChannel +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: dedaniel, robharad +--- + +# Get-TeamAllChannel + +## SYNOPSIS +This cmdlet supports retrieving all channels of a team, including incoming channels and channels hosted by the team. + +## SYNTAX +```PowerShell +Get-TeamAllChannel -GroupId <String> [-MembershipType <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet supports retrieving all channels of a team, including incoming channels and channels hosted by the team. + +## EXAMPLES + +### Example 1 +```PowerShell +Get-TeamAllChannel -GroupId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 +``` + +Returns all channels of a team. + +### Example 2 +```PowerShell +Get-TeamAllChannel -GroupId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 -MembershipType Shared +``` + +Returns all shared channels of a team. + +## PARAMETERS + +### -GroupId +Returns the Group ID of the team. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MembershipType +Membership type of the channel to display; Standard, Private, or Shared + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### GroupId, MembershipType + +## OUTPUTS + +### Channel + +## NOTES + +## RELATED LINKS +[Get-TeamChannel](https://learn.microsoft.com/powershell/module/teams/get-teamchannel) +[Get-TeamIncomingChannel](https://learn.microsoft.com/powershell/module/teams/get-teamchannel) diff --git a/teams/teams-ps/teams/Get-TeamChannel.md b/teams/teams-ps/teams/Get-TeamChannel.md index b185482f9a..9eae890d9e 100644 --- a/teams/teams-ps/teams/Get-TeamChannel.md +++ b/teams/teams-ps/teams/Get-TeamChannel.md @@ -1,26 +1,23 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-teamchannel +online version: https://learn.microsoft.com/powershell/module/teams/get-teamchannel +title: Get-TeamChannel schema: 2.0.0 --- -# Get-TeamChannel +# Get-TeamChannel ## SYNOPSIS - -Get all the channels for a team. +This cmdlet supports retrieving channels hosted by a team. ## SYNTAX - ``` Get-TeamChannel -GroupId <String> [-MembershipType <String>] [<CommonParameters>] ``` ## DESCRIPTION - -> [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. +This cmdlet supports retrieving channels hosted by a team. ## EXAMPLES diff --git a/teams/teams-ps/teams/Get-TeamChannelUser.md b/teams/teams-ps/teams/Get-TeamChannelUser.md index 024449639e..a245c41c40 100644 --- a/teams/teams-ps/teams/Get-TeamChannelUser.md +++ b/teams/teams-ps/teams/Get-TeamChannelUser.md @@ -1,11 +1,12 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-teamchanneluser +online version: https://learn.microsoft.com/powershell/module/teams/get-teamchanneluser +title: Get-TeamChannelUser schema: 2.0.0 --- -# Get-TeamChannelUser +# Get-TeamChannelUser ## SYNOPSIS Returns users of a channel. @@ -18,8 +19,7 @@ Get-TeamChannelUser -GroupId <String> -DisplayName <String> [-Role <String>] [<C ## DESCRIPTION -> [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. +Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see [Install Teams PowerShell public preview](https://learn.microsoft.com/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview) and also see [Microsoft Teams PowerShell Release Notes](https://learn.microsoft.com/microsoftteams/teams-powershell-release-notes). ## EXAMPLES diff --git a/teams/teams-ps/teams/Get-TeamFunSettings.md b/teams/teams-ps/teams/Get-TeamFunSettings.md index 266dd4bd14..00fb19db53 100644 --- a/teams/teams-ps/teams/Get-TeamFunSettings.md +++ b/teams/teams-ps/teams/Get-TeamFunSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Get-TeamFunSettings -online version: https://docs.microsoft.com/powershell/module/teams/get-teamfunsettings +online version: https://learn.microsoft.com/powershell/module/teams/get-teamfunsettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -57,4 +57,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-TeamGuestSettings.md b/teams/teams-ps/teams/Get-TeamGuestSettings.md index 3f9f6db3bd..91b260b35c 100644 --- a/teams/teams-ps/teams/Get-TeamGuestSettings.md +++ b/teams/teams-ps/teams/Get-TeamGuestSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Get-TeamGuestSettings -online version: https://docs.microsoft.com/powershell/module/teams/get-teamguestsettings +online version: https://learn.microsoft.com/powershell/module/teams/get-teamguestsettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -57,4 +57,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-TeamHelp.md b/teams/teams-ps/teams/Get-TeamHelp.md deleted file mode 100644 index f8705c51ad..0000000000 --- a/teams/teams-ps/teams/Get-TeamHelp.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml -Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-teamhelp -schema: 2.0.0 -author: kenwith -ms.author: kenwith -ms.reviewer: ---- - -# Get-TeamHelp - -## SYNOPSIS - -Gets a list of commands for Microsoft Teams. - -## SYNTAX - -``` -Get-TeamHelp -``` - -## DESCRIPTION - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Get-TeamHelp -``` - -Gets a list of commands available for Microsoft Teams. - -## 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/teams/teams-ps/teams/Get-TeamIncomingChannel.md b/teams/teams-ps/teams/Get-TeamIncomingChannel.md new file mode 100644 index 0000000000..b1ad0429ef --- /dev/null +++ b/teams/teams-ps/teams/Get-TeamIncomingChannel.md @@ -0,0 +1,66 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-teamincomingchannel +title: Get-TeamIncomingChannel +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: dedaniel, robharad +--- + +# Get-TeamIncomingChannel + +## SYNOPSIS +This cmdlet supports retrieving incoming channels of a team. + +## SYNTAX +```PowerShell +Get-TeamIncomingChannel -GroupId <String> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet supports retrieving incoming channels of a team. + +## EXAMPLES + +### Example 1 +```PowerShell +Get-TeamIncomingChannel -GroupId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 +``` + +Returns incoming channels of a team. + +## PARAMETERS + +### -GroupId +Group ID of the team + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### GroupId + +## OUTPUTS + +### Channel + +## NOTES + +## RELATED LINKS +[Get-TeamChannel](https://learn.microsoft.com/powershell/module/teams/get-teamchannel) +[Get-TeamAllChannel](https://learn.microsoft.com/powershell/module/teams/get-teamchannel) diff --git a/teams/teams-ps/teams/Get-TeamMemberSettings.md b/teams/teams-ps/teams/Get-TeamMemberSettings.md index 73e46c5316..f2b4df4491 100644 --- a/teams/teams-ps/teams/Get-TeamMemberSettings.md +++ b/teams/teams-ps/teams/Get-TeamMemberSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Get-TeamMemberSettings -online version: https://docs.microsoft.com/powershell/module/teams/get-teammembersettings +online version: https://learn.microsoft.com/powershell/module/teams/get-teammembersettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -57,4 +57,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-TeamMessagingSettings.md b/teams/teams-ps/teams/Get-TeamMessagingSettings.md index cafbffed5a..75cbd47356 100644 --- a/teams/teams-ps/teams/Get-TeamMessagingSettings.md +++ b/teams/teams-ps/teams/Get-TeamMessagingSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Get-TeamMessagingSettings -online version: https://docs.microsoft.com/powershell/module/teams/get-teammessagingsettings +online version: https://learn.microsoft.com/powershell/module/teams/get-teammessagingsettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -57,4 +57,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Get-TeamTargetingHierarchyStatus.md b/teams/teams-ps/teams/Get-TeamTargetingHierarchyStatus.md new file mode 100644 index 0000000000..2480953c1b --- /dev/null +++ b/teams/teams-ps/teams/Get-TeamTargetingHierarchyStatus.md @@ -0,0 +1,113 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/get-teamtargetinghierarchystatus +title: Get-TeamTargetingHierarchyStatus +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- +# Get-TeamTargetingHierarchyStatus + +## SYNOPSIS + +Get the status of a hierarchy upload (see [Set-TeamTargetingHierarchy](https://learn.microsoft.com/powershell/module/teams/set-teamtargetinghierarchy)) + +## SYNTAX + +### Get (Default) +``` +Get-TeamTargetingHierarchyStatus [-RequestId <String>] [-ApiVersion <String>] [<CommonParameters>] +``` + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-TeamTargetingHierarchy -FilePath d:\hier.csv + +Key Value +--- ----- +requestId c67e86109d88479e9708c3b7e8ff7217 + +PS C:\> Get-TeamTargetingHierarchyStatus -RequestId c67e86109d88479e9708c3b7e8ff7217 + +# When an error occurs, you will see the details in the ErrorMessage field. + +Id : c67e86109d88479e9708c3b7e8ff7217 +Status : Failed +LastKnownStatus : Validating +ErrorMessage : 1 error(s) were found. + Error: InvalidTeamId + Descriptions: + TeamID in row 2 doesn't match a valid Group ID. Please view our documentation to learn how to get the proper Group ID for each team. + TeamID in row 3 doesn't match a valid Group ID. Please view our documentation to learn how to get the proper Group ID for each team. + TeamID in row 4 doesn't match a valid Group ID. Please view our documentation to learn how to get the proper Group ID for each team. + TeamID in row 5 doesn't match a valid Group ID. Please view our documentation to learn how to get the proper Group ID for each team. + TeamID in row 6 doesn't match a valid Group ID. Please view our documentation to learn how to get the proper Group ID for each team. + TeamID in row 7 doesn't match a valid Group ID. Please view our documentation to learn how to get the proper Group ID for each team. + +LastUpdatedAt : 2021-02-17T22:28:08.7832795+00:00 +LastModifiedBy : a145d7eb-b70d-4591-9455-6c87382a22b7 +FileName : hier1.csv + +# When the hierarchy uploads and parses successfully, you will see this status. + +Id : c67e86109d88479e9708c3b7e8ff7217 +Status : Successful +LastKnownStatus : +ErrorMessage : +LastUpdatedAt : 2021-02-17T22:48:41.6664097+00:00 +LastModifiedBy : a145d7eb-b70d-4591-9455-6c87382a22b7 +FileName : hier.csv +``` + +Prompts for user credentials to connect and manage a Microsoft Teams environment. + +## PARAMETERS + +### -RequestId +Specifies the ID returned by the Set-TeamTargetingHierarchy cmdlet. This parameter is optional and the status of the most recent upload will be retrieved. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiVersion +The version of the Hierarchy APIs to use. Valid values are: 1 or 2. + +Currently only available in preview from version 6.6.1-preview. Specifying "-ApiVersion 2" will direct cmdlet requests to the newer version of the Hierarchy APIs. This integration is currently in preview/beta mode so customers should not try it on their production workloads but are welcome to try it on test workloads. This is an optional parameter and not specifying it will be interpreted as specifying "-ApiVersion 1", which will continue to direct cmdlet requests to the original version of the Hierarchy APIs until we upgrade production to v2, at which time we will set the default to 2. We do not expect this to have any impact on your cmdlet usage or existing scripts. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 1 +Accept pipeline input: false +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-TeamTargetingHierarchy](https://learn.microsoft.com/powershell/module/teams/set-teamtargetinghierarchy) diff --git a/teams/teams-ps/teams/Get-TeamUser.md b/teams/teams-ps/teams/Get-TeamUser.md index 00c04ead8b..a7b4fd3d69 100644 --- a/teams/teams-ps/teams/Get-TeamUser.md +++ b/teams/teams-ps/teams/Get-TeamUser.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-teamuser +online version: https://learn.microsoft.com/powershell/module/teams/get-teamuser +title: Get-TeamUser schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -20,6 +21,7 @@ Get-TeamUser -GroupId <String> [-Role <String>] [<CommonParameters>] ``` ## DESCRIPTION +Returns an array containing the UPN, UserId, Name and Role of users belonging to an specific GroupId. ## EXAMPLES @@ -27,6 +29,7 @@ Get-TeamUser -GroupId <String> [-Role <String>] [<CommonParameters>] ``` Get-TeamUser -GroupId 2f162b0e-36d2-4e15-8ba3-ba229cecdccf -Role Owner ``` +This example returns the UPN, UserId, Name, and Role of the owners of the specified GroupId. ## PARAMETERS @@ -61,8 +64,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Get-TeamsApp.md b/teams/teams-ps/teams/Get-TeamsApp.md index 0b5d754c10..e393faf0f5 100644 --- a/teams/teams-ps/teams/Get-TeamsApp.md +++ b/teams/teams-ps/teams/Get-TeamsApp.md @@ -6,7 +6,7 @@ author: joeyglocke ms.author: joglocke ms.reviewer: ken.withee manager: islubin -online version: https://docs.microsoft.com/powershell/module/teams/get-teamsapp +online version: https://learn.microsoft.com/powershell/module/teams/get-teamsapp schema: 2.0.0 --- @@ -75,7 +75,7 @@ Accept wildcard characters: False ``` ### -ExternalId -The external ID of the app, provided by the app developer and used by Azure Active Directory +The external ID of the app, provided by the app developer and used by Microsoft Entra ID ```yaml Type: String @@ -105,14 +105,12 @@ Accept wildcard characters: False ``` ### 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 (http://go.microsoft.com/fwlink/?LinkID=113216). +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Get-TeamsAppInstallation.md b/teams/teams-ps/teams/Get-TeamsAppInstallation.md index 4ac8e3ece2..39ef59a41c 100644 --- a/teams/teams-ps/teams/Get-TeamsAppInstallation.md +++ b/teams/teams-ps/teams/Get-TeamsAppInstallation.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/get-teamsappinstallation +online version: https://learn.microsoft.com/powershell/module/teams/get-teamsappinstallation +title: Get-TeamsAppInstallation schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -28,6 +29,8 @@ Get-TeamsAppInstallation -UserId <String> [-AppInstallationId <String>] [-AppId ## DESCRIPTION Get a Teams App installed in Microsoft Teams. +Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see [Install Teams PowerShell public preview](https://learn.microsoft.com/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview) and also see [Microsoft Teams PowerShell Release Notes](https://learn.microsoft.com/microsoftteams/teams-powershell-release-notes). + ## EXAMPLES ### Example 1 @@ -109,6 +112,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsApplicationAccessPolicy.md b/teams/teams-ps/teams/Grant-CsApplicationAccessPolicy.md new file mode 100644 index 0000000000..b321e2118c --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsApplicationAccessPolicy.md @@ -0,0 +1,234 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csapplicationaccesspolicy +applicable: Microsoft Teams +title: Grant-CsApplicationAccessPolicy +schema: 2.0.0 +manager: zhengni +author: frankpeng7 +ms.author: frpeng +ms.reviewer: +--- + +# Grant-CsApplicationAccessPolicy + +## SYNOPSIS + +Assigns a per-user application access policy to one or more users. After assigning an application access policy to a user, the applications configured in the policy will be authorized to access online meetings on behalf of that user. + +## SYNTAX + +### Identity + +``` +Grant-CsApplicationAccessPolicy [-Identity <UserIdParameter>] [-PolicyName <String>] [-Global] +``` + +### GrantToTenant (Default) +``` +Grant-CsApplicationAccessPolicy [-Global] [-PassThru] [-PolicyName <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsApplicationAccessPolicy [-PassThru] [-PolicyName <String>] [-MsftInternalProcessingMode <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet assigns a per-user application access policy to one or more users. After assigning an application access policy to a user, the applications configured in the policy will be authorized to access online meetings on behalf of that user.**Note:** You can assign only 1 application access policy at a time to a particular user. Assigning a new application access policy to a user will override the existing application access policy if any. + +## EXAMPLES + +### Assign an application access policy to a user + +``` +PS C:\> Grant-CsApplicationAccessPolicy -Identity "dc17674c-81d9-4adb-bfb2-8f6a442e4624" -PolicyName "ASimplePolicy" +``` + +The command shown above assigns the per-user application access policy "ASimplePolicy" to the user with object ID "dc17674c-81d9-4adb-bfb2-8f6a442e4624". + +### Unassign an application access policy from a user + +``` +PS C:\> Grant-CsApplicationAccessPolicy -Identity "dc17674c-81d9-4adb-bfb2-8f6a442e4624" -PolicyName $Null +``` + +In the command shown above, any per-user application access policy previously assigned to the user with user (object) ID "dc17674c-81d9-4adb-bfb2-8f6a442e4624" is unassigned from that user; as a result, applications configured in the policy can no longer access online meetings on behalf of that user. To unassign a per-user policy, set the PolicyName to a null value ($Null). + +### Assign an application access policy to all users in the tenant + +``` +PS C:\> Get-CsOnlineUser | Grant-CsApplicationAccessPolicy -PolicyName "ASimplePolicy" +``` + +The command shown above assigns the per-user application access policy ASimplePolicy to all the users in the tenant. To do this, the command first calls the `Get-CsOnlineUser` cmdlet to get all user accounts enabled for Microsoft Teams or Skype for Business Online. Those user accounts are then piped to the `Grant-CsApplicationAccessPolicy` cmdlet, which assigns each user the application access policy "ASimplePolicy". + +### Assign an application access policy to users who have not been assigned one + +``` +PS C:\> Grant-CsApplicationAccessPolicy -PolicyName "ASimplePolicy" -Global +``` + +The command shown above assigns the per-user application access policy "ASimplePolicy" to all the users in the tenant, except any that have an explicit policy assignment. + +## PARAMETERS + +### -Identity + +Indicates the user (object) ID of the user account to be assigned the per-user application access policy. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName + +Name of the policy to be assigned. The PolicyName is simply the policy Identity without the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:ASimplePolicy has a PolicyName equal to ASimplePolicy. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant, except any that have an explicit policy assignment. For example, if the user already have application access policy "A" assigned, and tenant admin assigns "B" globally, then application access policy "A" will take effect for the user. + +```yaml +Type: SwitchParameter +Parameter Sets:(All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +Allows the user to indicate whether the cmdlet passes an output object through the pipeline, in this case, after a process is stopped. Be aware that this parameter is tied to the cmdlet itself instead of to a property of the input object. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Get-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Set-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Remove-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) diff --git a/teams/teams-ps/teams/Grant-CsCallingLineIdentity.md b/teams/teams-ps/teams/Grant-CsCallingLineIdentity.md new file mode 100644 index 0000000000..bac8b79e4c --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsCallingLineIdentity.md @@ -0,0 +1,209 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-cscallinglineidentity +applicable: Microsoft Teams +title: Grant-CsCallingLineIdentity +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsCallingLineIdentity + +## SYNOPSIS +Use the `Grant-CsCallingLineIdentity` cmdlet to apply a Caller ID policy to a user account, to a group of users, or to set the tenant Global instance. + +## SYNTAX + +### GrantToTenant (Default) +``` +Grant-CsCallingLineIdentity [[-PolicyName] <string>] [-Global] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsCallingLineIdentity [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Identity +``` +Grant-CsCallingLineIdentity [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You can either assign a Caller ID policy to a specific user, to a group of users, or you can set the Global policy instance. + +## EXAMPLES + +### Example 1 +``` +PS C:\> Grant-CsCallingLineIdentity -Identity Ken.Myer@contoso.com -PolicyName CallerIDRedmond +``` + +This example assigns the Caller ID policy with the Identity CallerIDRedmond to the user Ken.Myer@contoso.com + +### Example 2 +``` +Grant-CsCallingLineIdentity -PolicyName CallerIDSeattle -Global +``` + +This example copies the Caller ID policy CallerIDSeattle to the Global policy instance. + +### Example 3 +``` +Grant-CsCallingLineIdentity -Group sales@contoso.com -PolicyName CallerIDSeattle -Rank 10 +``` + +This example assigns the Caller ID policy with the Identity CallerIDSeattle to the members of the group sales@contoso.com. + +## PARAMETERS + +### -Global +Sets the parameters of the Global policy instance to the values in the specified policy instance. + +```yaml +Type: SwitchParameter +Parameter Sets: (GrantToTenant) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsCallingLineIdentity cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name (Identity) of the Caller ID policy to be assigned. To remove an existing user level policy assignment, specify PolicyName as $null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -Identity +The Identity of the user to whom the policy is being assigned. User Identities can be specified using the user's SIP address, the user's user principal name (UPN), or +the user's ObjectId/Identity. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module 4.5.1-preview or later. + +## RELATED LINKS +[Set-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/set-cscallinglineidentity) + +[Get-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/get-cscallinglineidentity) + +[Remove-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/remove-cscallinglineidentity) + +[New-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/new-cscallinglineidentity) diff --git a/skype/skype-ps/skype/Grant-CsCloudMeetingPolicy.md b/teams/teams-ps/teams/Grant-CsCloudMeetingPolicy.md similarity index 77% rename from skype/skype-ps/skype/Grant-CsCloudMeetingPolicy.md rename to teams/teams-ps/teams/Grant-CsCloudMeetingPolicy.md index bfee02c26d..e85a10218d 100644 --- a/skype/skype-ps/skype/Grant-CsCloudMeetingPolicy.md +++ b/teams/teams-ps/teams/Grant-CsCloudMeetingPolicy.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-cscloudmeetingpolicy -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-cscloudmeetingpolicy +applicable: Microsoft Teams title: Grant-CsCloudMeetingPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Grant-CsCloudMeetingPolicy @@ -24,7 +24,7 @@ Grant-CsCloudMeetingPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainContr ## DESCRIPTION The Grant-CsCloudMeetingPolicy cmdlet enables or disables automatic scheduling of Skype Meetings features for a specified user. -The default is disbaled. +The default is disabled. To enable automatic scheduling for all users in a tenant, use the Set-CsCloudMeetingPolicy cmdlet. @@ -32,7 +32,7 @@ Note that the policies to use this cmdlet are not available unless the Set-CsClo ## EXAMPLES -### -------------------------- Example 1 -------------------------- (Skype for Business Online) +### -------------------------- Example 1 -------------------------- ``` Grant-CsCloudMeetingPolicy -PolicyName AutoScheduleEnabled -Identity "JaneC" @@ -40,7 +40,6 @@ Grant-CsCloudMeetingPolicy -PolicyName AutoScheduleEnabled -Identity "JaneC" This example enables Skype Meetings automatic scheduling for a user. - ## PARAMETERS ### -Identity @@ -50,8 +49,8 @@ For example: `-Identity "SeattlePSTN".` ```yaml Type: UserIdParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 1 @@ -67,8 +66,8 @@ Can be either AutoScheduleEnabled or AutoScheduleDisabled. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 2 @@ -84,7 +83,7 @@ The Confirm switch causes the command to pause processing, and requires confirma Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -100,8 +99,8 @@ Valid inputs for this parameter are either the fully qualified domain name (FQDN ```yaml Type: Fqdn Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -116,8 +115,8 @@ Accept wildcard characters: False ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -138,8 +137,8 @@ The Tenant parameter is primarily for use in a hybrid deployment. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -156,23 +155,7 @@ By using this switch, you can view what changes would occur without having to co Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -182,7 +165,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS @@ -191,5 +174,3 @@ This cmdlet supports the common parameters: `-Debug, -ErrorAction, -ErrorVariabl ## NOTES ## RELATED LINKS - - diff --git a/teams/teams-ps/teams/Grant-CsDialoutPolicy.md b/teams/teams-ps/teams/Grant-CsDialoutPolicy.md new file mode 100644 index 0000000000..73c1d5c787 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsDialoutPolicy.md @@ -0,0 +1,226 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csdialoutpolicy +applicable: Microsoft Teams +title: Grant-CsDialoutPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsDialoutPolicy + +## SYNOPSIS +Use the `Grant-CsDialoutPolicy` cmdlet to assign the tenant global, a group of users, or a per-user outbound calling restriction policy to one or more users. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsDialoutPolicy [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsDialoutPolicy [[-PolicyName] <string>] [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsDialoutPolicy [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +In Microsoft Teams, outbound calling restriction policies are used to restrict the type of audio conferencing and end user PSTN calls that can be made by users in your organization. The policies apply to all the different PSTN connectivity options for Microsoft Teams; Calling Plan, Direct Routing, and Operator Connect. + +To get all the available policies in your organization run `Get-CsOnlineDialOutPolicy`. + +## EXAMPLES + +### Example 1 +``` +Grant-CsDialoutPolicy -Identity "ken.myer@contoso.com" -PolicyName "DialoutCPCandPSTNInternational" +``` + +This example assigns the per-user outbound calling restriction policy DialoutCPCandPSTNInternational to the user with the User Principal Name "ken.myer@contoso.com". + +### Example 2 +``` +Grant-CsDialoutPolicy -Identity "ken.myer@contoso.com" -PolicyName $Null +``` + +In this example, any per-user outbound calling restriction policy previously assigned to the user ken.myer@contoso.com is unassigned from that user; as a result, Ken Myer will be managed by the global outbound calling restriction policy. To unassign a per-user policy, set the PolicyName to a null value ($Null). + +### Example 3 +``` +Get-CsOnlineUser | Grant-CsDialoutPolicy -PolicyName "DialoutCPCInternationalPSTNDisabled" +``` + +This example assigns the per-user outbound calling restriction policy DialoutCPCInternationalPSTNDisabled to all the users in your organization. + +### Example 4 +``` +Grant-CsDialoutPolicy -Global -PolicyName "DialoutCPCandPSTNInternational" +``` + +This example sets the tenant global policy instance to DialoutCPCandPSTNInternational. + +### Example 5 +``` +Grant-CsDialoutPolicy -Group support@contoso.com -Rank 10 -PolicyName "DialoutCPCandPSTNInternational" +``` + +This example assigns the policy instance "DialoutCPCandPSTNInternational" to the members of the group support@contoso.com. + +## PARAMETERS + +### -Global +This parameter sets the tenant global policy instance. This is the policy that all users in the tenant will get unless they have a specific policy instance assigned. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the Identity of the user account to be to be modified. A user identity can be specified by using one of three formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's ObjectId/Identity. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PassThru +Returns the results of the command. By default, this cmdlet does not generate any output. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +"Name" of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:DialoutCPCZoneAPSTNDomestic has a PolicyName equal to DialoutCPCZoneAPSTNDomestic. + +To unassign a per-user policy previously assigned to a user, set the PolicyName to a null value ($Null). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module 4.5.1-preview or later. + +The cmdlet is not supported for Teams resource accounts. + +## RELATED LINKS +[Get-CsOnlineDialOutPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinedialoutpolicy) diff --git a/teams/teams-ps/teams/Grant-CsExternalAccessPolicy.md b/teams/teams-ps/teams/Grant-CsExternalAccessPolicy.md new file mode 100644 index 0000000000..ffce2c43e2 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsExternalAccessPolicy.md @@ -0,0 +1,297 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csexternalaccesspolicy +applicable: Microsoft Teams +title: Grant-CsExternalAccessPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Grant-CsExternalAccessPolicy + +## SYNOPSIS + +Enables you to assign an external access policy to a user or a group of users. +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; and, 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype. + +This cmdlet was introduced in Lync Server 2010. + +## SYNTAX + +### Identity (Default) +```powershell +Grant-CsExternalAccessPolicy [<CommonParameters>] +``` + +### GrantToUser +```powershell +Grant-CsExternalAccessPolicy [-Identity] <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsExternalAccessPolicy [[-PolicyName] <String>] [-Group] <String> [-Rank] <Int32> [<CommonParameters>] +``` + +### GrantToTenant +```powershell +Grant-CsExternalAccessPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION + +When you install Microsoft Teams or Skype for Business Server, your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with other people who have SIP accounts in your Active Directory Domain Services. +In addition, users are not allowed to access Skype for Business Server over the Internet; instead, they must be logged on to your internal network before they will be able to log on to Skype for Business Server. + +That might be sufficient to meet your communication needs. +If it doesn't meet your needs you can use external access policies to extend the ability of your users to communicate and collaborate. +External access policies can grant (or revoke) the ability of your users to do any or all of the following: + +1. Communicate with people who have SIP accounts with a federated organization. +Note that enabling federation will not automatically provide users with this capability. +Instead, you must enable federation, and then assign users an external access policy that gives them the right to communicate with federated users. + +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration). + +3. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. + +4. Access Skype for Business Server over the Internet, without having to first log on to your internal network. +This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. + +When you install Skype for Business Server, a global external access policy is automatically created for you. +In addition to this global policy, you can use the New-CsExternalAccessPolicy cmdlet to create additional external access policies configured at either the site or the per-user scope. + +When a policy is created at the site scope, it is automatically assigned to the site in question; for example, an external access policy with the Identity site:Redmond will automatically be assigned to the Redmond site. +By contrast, policies created at the per-user scope are not automatically assigned to anyone. +Instead, these policies must be explicitly assigned to a user or a group of users. +Assigning per-user policies is the job of the Grant-CsExternalAccessPolicy cmdlet. + +Note that per-user policies always take precedent over site policies and the global policy. +For example, suppose you create a per-user policy that allows communication with federated users, and you assign that policy to Ken Myer. +As long as that policy is in force, Ken will be allowed to communicate with federated users even if this type of communication is not allowed by Ken's site policy or by the global policy. +That's because the settings in the per-user policy take precedence. + +## EXAMPLES + +### -------------------------- EXAMPLE 1 -------------------------- +```powershell +Grant-CsExternalAccessPolicy -Identity "Ken Myer" -PolicyName RedmondAccessPolicy +``` + +Example 1 assigns the external access policy RedmondAccessPolicy to the user with the Active Directory display name Ken Myer. + +### -------------------------- EXAMPLE 2 -------------------------- +```powershell +Get-CsUser -LdapFilter "l=Redmond" | Grant-CsExternalAccessPolicy -PolicyName RedmondAccessPolicy +``` + +The command shown in Example 2 assigns the external access policy RedmondAccessPolicy to all the users who work in the city of Redmond. +To do this, the command first uses the Get-CsUser cmdlet and the LdapFilter parameter to return a collection of all the users who work in Redmond; the filter value "l=Redmond" limits returned data to those users who work in the city of Redmond (the l in the filter, a lowercase L, represents the locality). +That collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy RedmondAccessPolicy to each user in the collection. + +### -------------------------- EXAMPLE 3 -------------------------- +```powershell +Get-CsUser -LdapFilter "Title=Sales Representative" | Grant-CsExternalAccessPolicy -PolicyName SalesAccessPolicy +``` + +In Example 3, all the users who have the job title "Sales Representative" are assigned the external access policy SalesAccessPolicy. +To perform this task, the command first uses the Get-CsUser cmdlet and the LdapFilter parameter to return a collection of all the Sales Representatives; the filter value "Title=Sales Representative" restricts the returned collection to users who have the job title "Sales Representative". +This filtered collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy SalesAccessPolicy to each user in the collection. + +### -------------------------- EXAMPLE 4 -------------------------- +```powershell +Get-CsUser -Filter {ExternalAccessPolicy -eq $Null} | Grant-CsExternalAccessPolicy -PolicyName BasicAccessPolicy +``` + +The command shown in Example 4 assigns the external access policy BasicAccessPolicy to all the users who have not been explicitly assigned a per-user policy. +(That is, users currently being governed by a site policy or by the global policy.) To do this, the Get-CsUser cmdlet and the Filter parameter are used to return the appropriate set of users; the filter value {ExternalAccessPolicy -eq $Null} limits the returned data to user accounts where the ExternalAccessPolicy property is equal to (-eq) a null value ($Null). +By definition, ExternalAccessPolicy will be null only if users have not been assigned a per-user policy. + +### -------------------------- EXAMPLE 5 -------------------------- +```powershell +Get-CsUser -OU "ou=US,dc=litwareinc,dc=com" | Grant-CsExternalAccessPolicy -PolicyName USAccessPolicy +``` + +Example 5 assigns the external access policy USAccessPolicy to all the users who have accounts in the US organizational unit (OU). +The command starts off by calling the Get-CsUser cmdlet and the OU parameter; the parameter value "ou=US,dc=litwareinc,dc=com" limits the returned data to user accounts found in the US OU. +The returned collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy USAccessPolicy to each user in the collection. + +### -------------------------- EXAMPLE 6 -------------------------- +```powershell +Get-CsUser | Grant-CsExternalAccessPolicy -PolicyName $Null +``` + +Example 6 unassigns any per-user external access policy previously assigned to any of the users enabled for Skype for Business Server. +To do this, the command calls the Get-CsUser cmdlet (without any additional parameters) in order to return a collection of all the users enabled for Skype for Business Server. +That collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which uses the syntax "`-PolicyName $Null`" to remove any per-user external access policy previously assigned to these users. + +## PARAMETERS + +### -Identity +Identity of the user account the policy should be assigned to. +User Identities can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). +User Identities can also be referenced by using the user's Active Directory distinguished name. + +In addition, you can use the asterisk (*) wildcard character when specifying the user Identity. +For example, the Identity "* Smith" returns all the users with a display name that ends with the string value " Smith." + +```yaml +Type: UserIdParameter +Parameter Sets: GrantToUser +Aliases: +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PolicyName +"Name" of the policy to be assigned. +The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). +For example, a policy with the Identity tag:Redmond has a PolicyName equal to Redmond; a policy with the Identity tag:RedmondAccessPolicy has a PolicyName equal to RedmondAccessPolicy. + +To unassign a per-user policy previously assigned to a user, set the PolicyName parameter to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Enables you to specify the fully qualified domain name (FQDN) of a domain controller to be contacted when assigning the new policy. +If this parameter is not specified, then the Grant-CsExternalAccessPolicy cmdlet will contact the first available domain controller. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. +By default, the Grant-CsExternalAccessPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter +String value or Microsoft.Rtc.Management.ADConnect.Schema.ADUser object. + +Grant-CsExternalAccessPolicy accepts pipelined input of string values representing the Identity of a user account. +The cmdlet also accepts pipelined input of user objects. + +## OUTPUTS + +### Output types +By default, Grant-CsExternalAccessPolicy does not return a value or object. + +However, if you include the PassThru parameter, the cmdlet will return instances of the Microsoft.Rtc.Management.ADConnect.Schema.OCSUserOrAppContact object. + +## NOTES + +## RELATED LINKS + +[Get-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/get-csexternalaccesspolicy) + +[New-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csexternalaccesspolicy) + +[Remove-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csexternalaccesspolicy) + +[Set-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/set-csexternalaccesspolicy) diff --git a/teams/teams-ps/teams/Grant-CsExternalUserCommunicationPolicy.md b/teams/teams-ps/teams/Grant-CsExternalUserCommunicationPolicy.md new file mode 100644 index 0000000000..d587ae4503 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsExternalUserCommunicationPolicy.md @@ -0,0 +1,167 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csexternalusercommunicationpolicy +applicable: Microsoft Teams +title: Grant-CsExternalUserCommunicationPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Grant-CsExternalUserCommunicationPolicy + +## SYNOPSIS +Provide the topic introduction here. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsExternalUserCommunicationPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> + [-Tenant <Guid>] [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsExternalUserCommunicationPolicy [-PolicyName] <String> [-Tenant <Guid>] + [-DomainController <Fqdn>] [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Provide the detailed description here. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Insert example commands for example 1. +``` + +Insert descriptive text for example 1. + +## PARAMETERS + +### -PolicyName +PARAMVALUE: String + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +PARAMVALUE: Fqdn + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +PARAMVALUE: UserIdParameter + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md b/teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md new file mode 100644 index 0000000000..a3f18f52c8 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md @@ -0,0 +1,145 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Grant-CsGroupPolicyPackageAssignment +author: serdarsoysal +ms.author: serdars +manager: dasosby +online version: https://learn.microsoft.com/powershell/module/teams/grant-csgrouppolicypackageassignment +schema: 2.0.0 +--- + +# Grant-CsGroupPolicyPackageAssignment + +## SYNOPSIS + +This cmdlet assigns a policy package to a group in a tenant. + +## SYNTAX + +``` +Grant-CsGroupPolicyPackageAssignment -GroupId <String> -PackageName <String> [-PolicyRankings <String[]>] [<CommonParameters>] [-Confirm] [-WhatIf] +``` + +## DESCRIPTION + +This cmdlet assigns a policy package to a group in a tenant. The available policy packages and their definitions can be found by running Get-CsPolicyPackage. For more information on policy packages, please review [Manage policy packages in Microsoft Teams](https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages). + +Policy rankings can be optionally specified for each policy type in the package to determine which policies will be assigned to the user in case they belong to two or more groups. If policy rankings for a policy type is not specified, one of two things can happen: + +- If the policy type was previously assigned to the group, the ranking for the policy type will not change. +- If the policy type was not previously assigned to the group, the ranking for the policy type will be ranked last. + +Finally, if a user was directly assigned a package, direct assignment takes precedence over group assignment. For more information on policy rankings and group policy assignments, please review [the description section under New-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment#description). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsGroupPolicyPackageAssignment -GroupId 1bc0b35f-095a-4a37-a24c-c4b6049816ab -PackageName Education_PrimaryStudent +``` + +Assigns the Education_PrimaryStudent policy package to the group. The group will receive the lowest policy ranking for each policy type in the Education_PrimaryStudent package if the policy type is newly assigned to the group. If a policy type was already assigned to the group, the group will receive the same policy ranking as before. + +### Example 2 +```powershell +PS C:\> Grant-CsGroupPolicyPackageAssignment -GroupId 1bc0b35f-095a-4a37-a24c-c4b6049816ab -PackageName Education_Teacher -PolicyRankings "TeamsMessagingPolicy, 1", "TeamsMeetingPolicy, 1", "TeamsCallingPolicy, 2" +``` + +Assigns the Education_Teacher policy package to the group. The group will receive a policy ranking of 1 for TeamsMessagingPolicy policy type, a policy ranking of 1 for TeamsMeetingPolicy policy type and a policy ranking of 2 for TeamsCallingPolicy policy type. For each unspecified policy type in the package, the group will receive the lowest policy ranking if it is newly assigned to the group. If a policy type was already assigned to the group, the group will receive the same policy ranking as before. + +## PARAMETERS + +### -GroupId + +A group id in the tenant. It can either be a group's object id or a group's email address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PackageName + +The name of a policy package. All policy package names can be found by running Get-CsPolicyPackage. To reset the currently assigned package value for the group, use $null or an empty string "". This will not remove any existing policy assignments to the group. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyRankings + +The policy rankings for each of the policy types in the package. To specify the policy rankings, follow this format: "\<PolicyType\>, \<PolicyRank\>". Delimiters of ' ', '.', ':', '\t' are also acceptable. Supported policy types are listed [here](https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages#what-is-a-policy-package). Policy rank must be a number greater than or equal to 1. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage) + +[New-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment) diff --git a/teams/teams-ps/teams/Grant-CsOnlineAudioConferencingRoutingPolicy.md b/teams/teams-ps/teams/Grant-CsOnlineAudioConferencingRoutingPolicy.md new file mode 100644 index 0000000000..d9f1d28be6 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsOnlineAudioConferencingRoutingPolicy.md @@ -0,0 +1,247 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csonlineaudioconferencingroutingpolicy +title: Grant-CsOnlineAudioConferencingRoutingPolicy +schema: 2.0.0 +--- + +# Grant-CsOnlineAudioConferencingRoutingPolicy + +## SYNOPSIS + +This cmdlet applies an instance of the Online Audio Conferencing Routing policy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) + +```powershell +Grant-CsOnlineAudioConferencingRoutingPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant + +```powershell +Grant-CsOnlineAudioConferencingRoutingPolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup + +```powershell +Grant-CsOnlineAudioConferencingRoutingPolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Group] <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +Teams meeting dial-out calls are initiated from within a meeting in your organization to PSTN numbers, including call-me-at calls and calls to bring new participants to a meeting. + +To enable Teams meeting dial-out routing through Direct Routing to on-network users, you need to create and assign an Audio Conferencing routing policy called "OnlineAudioConferencingRoutingPolicy." + +The OnlineAudioConferencingRoutingPolicy policy is equivalent to the CsOnlineVoiceRoutingPolicy for 1:1 PSTN calls via Direct Routing. + +Audio Conferencing voice routing policies determine the available routes for calls from meeting dial-out based on the destination number. Audio Conferencing voice routing policies link to PSTN usages, determining routes for meeting dial-out calls by associated organizers. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Grant-CsOnlineAudioConferencingRoutingPolicy -PolicyName Test -Identity testuser@test.onmicrosoft.com +``` + +Applies the policy "test" to the user "<testuser@test.onmicrosoft.com>". + +### Example 2 + +```powershell +PS C:\> Grant-CsOnlineAudioConferencingRoutingPolicy -PolicyName Test -Identity Global +``` + +Applies the policy "test" to the entire tenant. + +### Example 3 + +```powershell +PS C:\> Grant-CsOnlineAudioConferencingRoutingPolicy -Group f13d6c9d-ce76-422c-af78-b6018b4d9c80 -PolicyName Test +``` + +Applies the policy "test" to the specified group. + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +This can be used to apply the policy to the entire tenant. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group + +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Specifies the identity of the target user. + +Example: <testuser@test.onmicrosoft.com> + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName + +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), for example, a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank + +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsOnlineAudioConferencingRoutingPolicy](New-CsOnlineAudioConferencingRoutingPolicy.md) +[Remove-CsOnlineAudioConferencingRoutingPolicy](Remove-CsOnlineAudioConferencingRoutingPolicy.md) +[Set-CsOnlineAudioConferencingRoutingPolicy](Set-CsOnlineAudioConferencingRoutingPolicy.md) +[Get-CsOnlineAudioConferencingRoutingPolicy](Get-CsOnlineAudioConferencingRoutingPolicy.md) diff --git a/teams/teams-ps/teams/Grant-CsOnlineVoiceRoutingPolicy.md b/teams/teams-ps/teams/Grant-CsOnlineVoiceRoutingPolicy.md new file mode 100644 index 0000000000..4f5598bbb8 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsOnlineVoiceRoutingPolicy.md @@ -0,0 +1,191 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoiceroutingpolicy +applicable: Microsoft Teams +title: Grant-CsOnlineVoiceRoutingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsOnlineVoiceRoutingPolicy + +## SYNOPSIS +Assigns a per-user online voice routing policy to one user, a group of users, or sets the Global policy instance. Online voice routing policies manage online PSTN usages for Phone System users. + +## SYNTAX + +### Identity (Default) +```powershell +Grant-CsOnlineVoiceRoutingPolicy [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [<CommonParameters>] +``` + +### GrantToTenant +```powershell +Grant-CsOnlineVoiceRoutingPolicy [[-PolicyName] <string>] [-PassThru] [-Global] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsOnlineVoiceRoutingPolicy [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [<CommonParameters>] +``` + +## DESCRIPTION +Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. + +Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. + +## EXAMPLES + +### Example 1 +```powershell +Grant-CsOnlineVoiceRoutingPolicy -Identity Ken.Myer@contoso.com -PolicyName "RedmondOnlineVoiceRoutingPolicy" +``` + +The command shown in Example 1 assigns the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy to the user ken.myer@contoso.com. + +### Example 2 +```powershell +Grant-CsOnlineVoiceRoutingPolicy -Identity Ken.Myer@contoso.com -PolicyName $Null +``` + +In Example 2, any per-user online voice routing policy previously assigned to the user Ken Myer is unassigned from that user; as a result, Ken Myer will be managed by the global online voice routing policy. To unassign a per-user policy, set the PolicyName to a null value ($null). + +### Example 3 +```powershell +Get-CsOnlineUser | Grant-CsOnlineVoiceRoutingPolicy -PolicyName "RedmondOnlineVoiceRoutingPolicy" +``` + +Example 3 assigns the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy to all the users in the tenant. To do this, the command first calls the `Get-CsOnlineUser` cmdlet to get all user accounts enabled for Microsoft Teams or Skype for Business Online. Those user accounts are then piped to the `Grant-CsOnlineVoiceRoutingPolicy` cmdlet, which assigns each user the online voice routing policy RedmondOnlineVoiceRoutingPolicy. + +### Example 4 +```powershell +Grant-CsOnlineVoiceRoutingPolicy -PolicyName "RedmondOnlineVoiceRoutingPolicy" -Global +``` + +Example 4 assigns the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy as the global online voice routing policy. This affects all the users in the tenant, except any that have an explicit policy assignment. + +### Example 5 +```powershell +Grant-CsOnlineVoiceRoutingPolicy -Group sales@contoso.com -Rank 10 -PolicyName "RedmondOnlineVoiceRoutingPolicy" +``` + +Example 5 assigns the online voice routing policy RedmondOnlineVoiceRoutingPolicy to all members of the group sales@contoso.com. + +## PARAMETERS + +### -Identity +Indicates the Identity of the user account to be assigned the per-user online voice routing policy. User Identities can be specified using one of the following formats: the user's SIP address, the user's user principal name (UPN), or the user's Active Directory display name (for example, Ken Myer). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the online voice routing policy. By default, the `Grant-CsOnlineVoiceRoutingPolicy` cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Name of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:Redmond has a PolicyName equal to Redmond; likewise, a policy with the Identity tag:RedmondOnlineVoiceRoutingPolicy has a PolicyName equal to RedmondOnlineVoiceRoutingPolicy. + +To unassign a per-user policy previously assigned to a user, set the PolicyName to a null value ($Null). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant, except any that have an explicit policy assignment. To skip a warning when you do this operation, specify this parameter. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module 4.5.1-preview or later. + +## RELATED LINKS +[New-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroutingpolicy) + +[Get-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroutingpolicy) + +[Set-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroutingpolicy) + +[Remove-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroutingpolicy) diff --git a/teams/teams-ps/teams/Grant-CsOnlineVoicemailPolicy.md b/teams/teams-ps/teams/Grant-CsOnlineVoicemailPolicy.md new file mode 100644 index 0000000000..fada417049 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsOnlineVoicemailPolicy.md @@ -0,0 +1,201 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoicemailpolicy +applicable: Microsoft Teams +title: Grant-CsOnlineVoicemailPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsOnlineVoicemailPolicy + +## SYNOPSIS +Assigns an online voicemail policy to a user account, to a group of users, or set the tenant Global instance. Online voicemail policies manage usages for Voicemail service. + +## SYNTAX + +### GrantToTenant (Default) +``` +Grant-CsOnlineVoicemailPolicy [[-PolicyName] <string>] [-Global] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` +### GrantToGroup +``` +Grant-CsOnlineVoicemailPolicy [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Identity +``` +Grant-CsOnlineVoicemailPolicy [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet assigns an existing user-specific online voicemail policy to a user, a group of users, or the Global policy instance. + +## EXAMPLES + +### Example 1 +``` +Grant-CsOnlineVoicemailPolicy -Identity "user@contoso.com" -PolicyName TranscriptionDisabled +``` + +The command shown in Example 1 assigns the per-user online voicemail policy TranscriptionDisabled to a single user user@contoso.com. + +### Example 2 +``` +Grant-CsOnlineVoicemailPolicy -Group sales@contoso.com -Rank 10 -PolicyName TranscriptionDisabled +``` + +The command shown in Example 2 assigns the online voicemail policy TranscriptionDisabled to the members of the group sales@contoso.com. + +## PARAMETERS + +### -Global +Sets the parameters of the Global policy instance to the values in the specified policy instance. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsOnlineVoicemailPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +A unique identifier(name) of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter represents the ID of the specific user in your organization; this can be either a SIP address or an Object ID. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module 4.5.1-preview or later. + +## RELATED LINKS +[Get-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoicemailpolicy) + +[Set-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailpolicy) + +[New-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoicemailpolicy) + +[Remove-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoicemailpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsAIPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsAIPolicy.md new file mode 100644 index 0000000000..4b3575f42c --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsAIPolicy.md @@ -0,0 +1,193 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Grant-CsTeamsAIPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Grant-CsTeamsAIPolicy +schema: 2.0.0 +author: Andy447 +ms.author: andywang +--- + +# Grant-CsTeamsAIPolicy + +## SYNOPSIS +This cmdlet applies an instance of the Teams AI policy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsAIPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsAIPolicy -Identity <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsAIPolicy [[-PolicyName] <String>] [-Group] <String> -Rank <Int32> + [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsAIPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION + +The new csTeamsAIPolicy will replace the existing enrollment settings in csTeamsMeetingPolicy, providing enhanced flexibility and control for Teams meeting administrators. Unlike the current single setting, EnrollUserOverride, which applies to both face and voice enrollment, the new policy introduces two distinct settings: EnrollFace and EnrollVoice. These can be individually set to Enabled or Disabled, offering more granular control over biometric enrollments. A new setting, SpeakerAttributionBYOD, is also being added to csTeamsAIPolicy. This allows IT admins to turn off speaker attribution in BYOD scenarios, giving them greater control over how voice data is managed in such environments. This setting can be set to Enabled or Disabled, and will be Enabled by default. In addition to improving the management of face and voice data, the csTeamsAIPolicy is designed to support future AI-related settings in Teams, making it a scalable solution for evolving needs. + +This cmdlet applies an instance of the Teams AI policy to users or groups in a tenant. + +Passes in the `Identity` of the policy instance in the `PolicyName` parameter and the user identifier in the `Identity` parameter or the group name in the `Group` parameter. One of either `Identity` or `Group` needs to be passed. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsAIPolicy -PolicyName Test -Identity testuser@test.onmicrosoft.com +``` + +Assigns a given policy to a user. + +### Example 2 +```powershell +PS C:\> Grant-CsTeamsAIPolicy -Group f13d6c9d-ce76-422c-af78-b6018b4d9c80 -PolicyName Test +``` + +Assigns a given policy to a group. + +### Example 3 +```powershell +PS C:\> Grant-CsTeamsAIPolicy -Global -PolicyName Test +``` + +Assigns a given policy to the tenant. + +### Example 4 +```powershell +PS C:\> Grant-CsTeamsAIPolicy -Global -PolicyName Test +``` + +Note: _Using $null in place of a policy name can be used to unassigned a policy instance._ + +## PARAMETERS + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +This is the equivalent to `-Identity Global`. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the identity of the target user. + +Example: testuser@test.onmicrosoft.com + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: GrantToUser +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), for example, a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +```yaml +Type: String +Parameter Sets: GrantToUser, GrantToGroup, GrantToTenant +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsaipolicy) + +[Remove-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsaipolicy) + +[Get-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaipolicy) + +[Set-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy) \ No newline at end of file diff --git a/teams/teams-ps/teams/Grant-CsTeamsAppPermissionPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsAppPermissionPolicy.md new file mode 100644 index 0000000000..76d9afbba6 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsAppPermissionPolicy.md @@ -0,0 +1,224 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsapppermissionpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsAppPermissionPolicy +schema: 2.0.0 +ms.reviewer: mhayrapetyan +manager: prkosh +ms.author: prkosh +author: ashishguptaiitb +--- + +# Grant-CsTeamsAppPermissionPolicy + +## SYNOPSIS +**NOTE**: You can use this cmdlet to assign a specific custom policy to a user. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. This cmdlet is not supported for tenants that migrated to app centric management feature as it replaced permission policies. While the cmdlet may succeed, the changes aren't applied to the tenant. + +As an admin, you can use app permission policies to allow or block apps for your users. Learn more about the app permission policies at <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies> and about app centric management at <https://learn.microsoft.com/microsoftteams/app-centric-management>. + +This is only applicable for tenants who have not been migrated to ACM or UAM. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsAppPermissionPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsAppPermissionPolicy [-Identity] <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsAppPermissionPolicy [[-PolicyName] <String>] [-Group] <String> [-Rank] <Int32> + [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsAppPermissionPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: You can use this cmdlet to assign a specific custom policy to a user. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Permission Policies: <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies>. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsAppPermissionPolicy -Identity "Ken Myer" -PolicyName StudentAppPermissionPolicy +``` + +In this example, a user with identity "Ken Myer" is being assigned the StudentAppPermissionPolicy + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Do not use. +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Resets the values in the global policy to match those in the provided (PolicyName) policy. Note that this means all users with no explicit policy assigned will have these new policy settings. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The user to whom the policy should be assigned. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Do not use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named + +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsAppSetupPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsAppSetupPolicy.md new file mode 100644 index 0000000000..3568887beb --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsAppSetupPolicy.md @@ -0,0 +1,226 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsappsetuppolicy +applicable: Microsoft Teams +title: Grant-CsTeamsAppSetupPolicy +schema: 2.0.0 +ms.reviewer: +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Grant-CsTeamsAppSetupPolicy + +## SYNOPSIS +**NOTE**: You can use this cmdlet to assign a specific custom policy to a user. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsAppSetupPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsAppSetupPolicy [-Identity] <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsAppSetupPolicy [[-PolicyName] <String>] [-Group] <String> [-Rank] <Int32> [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsAppSetupPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: You can use this cmdlet to assign a specific custom policy to a user. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsAppSetupPolicy -identity "Ken Myer" -PolicyName StudentAppSetupPolicy +``` + +In this example, a user with identity "Ken Myer" is being assigned the StudentAppSetupPolicy + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Do not use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Resets the values in the global policy to match those in the provided (PolicyName) policy. Note that this means all users with no explicit policy assigned will have these new policy settings. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The user to whom the policy should be assigned. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Do not use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsAudioConferencingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsAudioConferencingPolicy.md new file mode 100644 index 0000000000..10b0d7085d --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsAudioConferencingPolicy.md @@ -0,0 +1,191 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsaudioconferencingpolicy +title: Grant-CsTeamsAudioConferencingPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsAudioConferencingPolicy + +## SYNOPSIS + +Assigns a Teams audio-conferencing policy at the per-user scope. Audio conferencing policies are used to manage audio conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. + +## SYNTAX + +### GrantToTenant (Default) +``` +Grant-CsTeamsAudioConferencingPolicy [-Global] [-PassThru] [[-PolicyName] <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsAudioConferencingPolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +### Identity +``` +Grant-CsTeamsAudioConferencingPolicy [-PassThru] [[-PolicyName] <String>] [[-Identity] <String>] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Granular control over which audio conferencing features your users can or cannot use is an important feature for many organizations. This cmdlet lets you assign a teams audio conferencing policy at the per-user scope. Audio conferencing policies determine the audio-conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. + +## EXAMPLES + +### EXAMPLE 1 +``` +PS C:\> Grant-CsTeamsAudioCOnferencingPolicy -identity "Ken Myer" -PolicyName "Emea Users" +``` + +In this example, a user with identity "Ken Myer" is being assigned the "Emea Users" policy. + +## PARAMETERS + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant, except any that have an explicit policy assignment. To skip a warning when you do this operation, specify this parameter. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account to be assigned the per-user online voice routing policy. User Identities can be specified using one of the following formats: 1) the user's SIP address; 2) the user's user principal name (UPN); or, 3) the user's Active Directory display name (for example, Ken Myer). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the online voice routing policy. +Enables you to pass a user object through the pipeline that represents the user account being assigned the online voice routing policy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### String + +## OUTPUTS + +### Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaudioconferencingpolicy) + +[Set-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaudioconferencingpolicy) + +[Remove-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsaudioconferencingpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsCallHoldPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsCallHoldPolicy.md new file mode 100644 index 0000000000..6d1b8028b7 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsCallHoldPolicy.md @@ -0,0 +1,235 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamscallholdpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsCallHoldPolicy +schema: 2.0.0 +ms.reviewer: +manager: abnair +ms.author: serdars +author: serdarsoysal +--- + +# Grant-CsTeamsCallHoldPolicy + +## SYNOPSIS + +Assigns a per-user Teams call hold policy to one or more users. The Teams call hold policy is used to customize the call hold experience for Teams clients. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsCallHoldPolicy [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsCallHoldPolicy [[-PolicyName] <string>] [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsCallHoldPolicy [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Teams call hold policies are used to customize the call hold experience for teams clients. +When Microsoft Teams users participate in calls, they have the ability to hold a call and have the other entity in the call listen to an audio file during the duration of the hold. + +Assigning a teams call hold policy to a user sets an audio file to be played during the duration of the hold. + +## EXAMPLES + +### Example 1 +```powershell +Grant-CsTeamsCallHoldPolicy -Identity 'KenMyer@contoso.com' -PolicyName 'ContosoPartnerTeamsCallHoldPolicy' +``` + +The command shown in Example 1 assigns the per-user Teams call hold policy, ContosoPartnerTeamsCallHoldPolicy, to the user with the user principal name (UPN) "KenMyer@contoso.com". + +### Example 2 +```powershell +Grant-CsTeamsCallHoldPolicy -Identity 'Ken Myer' -PolicyName 'ContosoPartnerTeamsCallHoldPolicy' +``` + +The command shown in Example 2 assigns the per-user Teams call hold policy, ContosoPartnerTeamsCallHoldPolicy, to the user with the display name "Ken Myer". + +### Example 3 +```powershell +Grant-CsTeamsCallHoldPolicy -Identity 'Ken Myer' -PolicyName $null +``` + +In Example 3, any per-user Teams call hold policy previously assigned to the user "Ken Myer" is revoked. +As a result, the user will be managed by the global Teams call hold policy. + +### Example 4 +```powershell +Grant-CsTeamsCallHoldPolicy -Global -PolicyName 'ContosoPartnerTeamsCallHoldPolicy' +``` + +The command shown in Example 4 sets the Teams call hold policy, ContosoPartnerTeamsCallHoldPolicy, as the Global policy which will apply to all users in your tenant. + +### Example 5 +```powershell +Grant-CsTeamsCallHoldPolicy -Group sales@contoso.com -Rank 10 -PolicyName 'ContosoPartnerTeamsCallHoldPolicy' +``` + +The command shown in Example 5 sets the Teams call hold policy, ContosoPartnerTeamsCallHoldPolicy, to the members of the group sales@contoso.com. + +## PARAMETERS + +### -Identity +Indicates the Identity of the user account to be assigned the per-user Teams call hold policy. +User Identities can be specified using one of the following formats: + +- The user's SIP address; +- The user's user principal name (UPN); +- The user's Active Directory display name (for example, Ken Myer). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the Teams call hold policy. + +By default, the Grant-CsTeamsCallHoldPoly cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Name of the policy to be assigned. The PolicyName is simply the policy Identity without the policy scope, i.e. the "Tag:" prefix. + +For example, a policy with the Identity Tag:ContosoPartnerCallHoldPolicy has a PolicyName equal to ContosoPartnerCallHoldPolicy. + +To revoke a per-user policy previously assigned to a user, set the PolicyName to a null value ($null). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module 4.5.1-preview or later. + +## RELATED LINKS + +[New-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallholdpolicy) + +[Get-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallholdpolicy) + +[Set-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallholdpolicy) + +[Remove-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallholdpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsCallParkPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsCallParkPolicy.md new file mode 100644 index 0000000000..65c8d7ab00 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsCallParkPolicy.md @@ -0,0 +1,202 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamscallparkpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsCallParkPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsTeamsCallParkPolicy + +## SYNOPSIS + +The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone. The Grant-CsTeamsCallParkPolicy cmdlet lets you assign a custom policy to a specific user. + +NOTE: the call park feature currently only available in desktop, web clients and mobile clients. Call Park functionality is currently on the roadmap for Teams IP Phones. Supported with TeamsOnly mode for users with the Phone System license + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsCallParkPolicy [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsCallParkPolicy [[-PolicyName] <string>] [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsCallParkPolicy [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different phone. The Grant-CsTeamsCallParkPolicy cmdlet lets you assign a custom policy to a specific user. + +## EXAMPLES + +### Example 1 +```powershell +Grant-CsTeamsCallParkPolicy -PolicyName SalesPolicy -Identity Ken.Myer@contoso.com +``` + +Assigns a custom policy "Sales Policy" to the user Ken Myer. + +### Example 2 +```powershell +Grant-CsTeamsCallParkPolicy -Group sales@contoso.com -Rank 10 -PolicyName SalesPolicy +``` + +Assigns a custom policy "Sales Policy" to the members of the group sales@contoso.com. + +## PARAMETERS + +### -Identity +The User ID of the user to whom the policy is being assigned. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +If present, causes the cmdlet to pass the user object (or objects) through the Windows PowerShell pipeline. By default, the cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Name of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope ("tag:"). For example, a policy that has the Identity tag:Redmond has a PolicyName equal to Redmond; a policy with the Identity tag:RedmondConferencingPolicy has a PolicyName equal to RedmondConferencingPolicy. + +If you set PolicyName to a null value, the command will unassign any per-user policy assigned to the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Sets the parameters of the Global policy instance to the values in the specified policy instance. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module 4.5.1-preview or later. + +## RELATED LINKS +[Set-CsTeamsCallParkPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallparkpolicy) + +[Get-CsTeamsCallParkPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallparkpolicy) + +[New-CsTeamsCallParkPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallparkpolicy) + +[Remove-CsTeamsCallParkPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallparkpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsCallingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsCallingPolicy.md new file mode 100644 index 0000000000..c843a89e58 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsCallingPolicy.md @@ -0,0 +1,177 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamscallingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsCallingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsTeamsCallingPolicy + +## SYNOPSIS + +Assigns a specific Teams Calling Policy to a user, a group of users, or sets the Global policy instance. + +## SYNTAX + +### Identity (Default) +```powershell +Grant-CsTeamsCallingPolicy [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [<CommonParameters>] +``` + +### GrantToTenant +```powershell +Grant-CsTeamsCallingPolicy [[-PolicyName] <string>] [-PassThru] [-Global] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsTeamsCallingPolicy [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [<CommonParameters>] +``` + +## DESCRIPTION +The Teams Calling Policies designate how users are able to use calling functionality within Microsoft Teams. This cmdlet allows admins to grant user level policies to individual users, to members of a group, or to set the Global policy instance. + +## EXAMPLES + +### Example 1 +```powershell +Grant-CsTeamsCallingPolicy -identity user1@contoso.com -PolicyName SalesCallingPolicy +``` + +Assigns the TeamsCallingPolicy called "SalesCallingPolicy" to user1@contoso.com + +### Example 2 +```powershell +Grant-CsTeamsCallingPolicy -Global -PolicyName SalesCallingPolicy +``` + +Assigns the TeamsCallingPolicy called "SalesCallingPolicy" to the Global policy instance. This sets the parameters in the Global policy instance to the values found +in the SalesCallingPolicy instance. + +### Example 3 +```powershell +Grant-CsTeamsCallingPolicy -Group sales@contoso.com -Rank 10 -PolicyName SalesCallingPolicy +``` + +Assigns the TeamsCallingPolicy called "SalesCallingPolicy" to the members of the group sales@contoso.com. + +## PARAMETERS + +### -Identity +The user object to whom the policy is being assigned. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsCallingPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the policy being assigned. To remove an existing user level policy assignment, specify PolicyName as $null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Sets the parameters of the Global policy instance to the values in the specified policy instance. + +```yaml +Type: SwitchParameter +Parameter Sets: (GrantToTenant) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: (GrantToGroup) +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: (GrantToGroup) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module 4.5.1-preview or later. + +## RELATED LINKS + +[Set-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallingpolicy) + +[Remove-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallingpolicy) + +[Get-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallingpolicy) + +[New-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallingpolicy) diff --git a/skype/skype-ps/skype/Grant-CsTeamsChannelsPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsChannelsPolicy.md similarity index 77% rename from skype/skype-ps/skype/Grant-CsTeamsChannelsPolicy.md rename to teams/teams-ps/teams/Grant-CsTeamsChannelsPolicy.md index d3970dafed..abfbdfe908 100644 --- a/skype/skype-ps/skype/Grant-CsTeamsChannelsPolicy.md +++ b/teams/teams-ps/teams/Grant-CsTeamsChannelsPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/grant-csteamschannelspolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamschannelspolicy +applicable: Microsoft Teams title: Grant-CsTeamsChannelsPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Grant-CsTeamsChannelsPolicy @@ -30,6 +30,12 @@ Grant-CsTeamsChannelsPolicy [-PolicyName] <String> [-Tenant <System.Guid>] [-Dom [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] ``` +### GrantToGroup +``` +Grant-CsTeamsChannelsPolicy [-PassThru] [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + ## DESCRIPTION The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. The Grant-CsTeamsChannelsPolicy allows you to assign specific policies to users that have been created in your tenant. @@ -164,15 +170,43 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### Microsoft.Rtc.Management.AD.UserIdParameter - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Grant-CsTeamsComplianceRecordingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsComplianceRecordingPolicy.md new file mode 100644 index 0000000000..caa013a167 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsComplianceRecordingPolicy.md @@ -0,0 +1,280 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsComplianceRecordingPolicy +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# Grant-CsTeamsComplianceRecordingPolicy + +## SYNOPSIS +Assigns a per-user Teams recording policy to one or more users. +This policy is used to govern automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsComplianceRecordingPolicy [-Identity <UserIdParameter>] [-PolicyName <String>] + [-Tenant <System.Guid>] [-DomainController <Fqdn>] + [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsComplianceRecordingPolicy [-Global] [-PolicyName <String>] + [-Tenant <System.Guid>] [-DomainController <Fqdn>] + [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsComplianceRecordingPolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Teams recording policies are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. + +Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. +Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. + +Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. +The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. +Existing calls and meetings are unaffected. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsComplianceRecordingPolicy -Identity 'Ken Myer' -PolicyName 'ContosoPartnerComplianceRecordingPolicy' +``` + +The command shown in Example 1 assigns the per-user Teams recording policy ContosoPartnerComplianceRecordingPolicy to the user with the display name "Ken Myer". + +### Example 2 +```powershell +PS C:\> Grant-CsTeamsComplianceRecordingPolicy -Identity 'Ken Myer' -PolicyName $null +``` + +In Example 2, any per-user Teams recording policy previously assigned to the user "Ken Myer" is revoked. +As a result, the user will be managed by the global Teams recording policy. + +## PARAMETERS + +### -Identity +Indicates the Identity of the user account to be assigned the per-user Teams recording policy. +User Identities can be specified using one of the following formats: + +- The user's SIP address; +- The user's user principal name (UPN); +- The user's Active Directory display name (for example, Ken Myer). + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. +To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Name of the policy to be assigned. +The PolicyName is simply the policy Identity without the policy scope i.e. the "Tag:" prefix. +For example, a policy with the Identity Tag:ContosoPartnerComplianceRecordingPolicy has a PolicyName equal to ContosoPartnerComplianceRecordingPolicy. + +To revoke a per-user policy previously assigned to a user, set the PolicyName to a null value ($null). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Microsoft Teams or Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the Teams recording policy. +By default, the Grant-CsTeamsComplianceRecordingPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/teams/teams-ps/teams/Grant-CsTeamsCortanaPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsCortanaPolicy.md new file mode 100644 index 0000000000..ef2205b07d --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsCortanaPolicy.md @@ -0,0 +1,222 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscortanapolicy +applicable: Microsoft Teams +title: Grant-CsTeamsCortanaPolicy +schema: 2.0.0 +manager: amehta +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsTeamsCortanaPolicy + +## SYNOPSIS +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsCortanaPolicy [[-Identity] <UserIdParameter>] [-PolicyName] <String> [-Tenant <System.Guid>] + [-DomainController <Fqdn>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsCortanaPolicy [-PolicyName] <String> [-Tenant <System.Guid>] [-DomainController <Fqdn>] + [-PassThru] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsCortanaPolicy [-PassThru] [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. Specifically, these specify if a user can use Cortana voice assistant in Microsoft Teams and Cortana invocation behavior via CortanaVoiceInvocationMode parameter - +* Disabled - Cortana voice assistant is disabled +* PushToTalkUserOverride - Cortana voice assistant is enabled but without wake-word ("Hey Cortana") invocation +* WakeWordPushToTalkUserOverride - Cortana voice assistant is enabled with wake-word ("Hey Cortana") invocation on devices where wake-word is supported + +This cmdlet lets you assign a Teams Cortana policy at the per-user scope. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsCortanaPolicy -identity "Ken Myer" -PolicyName MyCortanaPolicy +``` + +In this example, a user with identity "Ken Myer" is being assigned the MyCortanaPolicy + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the identity of the user account the policy should be assigned to. User identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" +You can return your tenant ID by running this command: +Get-CsTenant | Select-Object DisplayName, TenantID + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsEmergencyCallRoutingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsEmergencyCallRoutingPolicy.md new file mode 100644 index 0000000000..c86a84aa89 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsEmergencyCallRoutingPolicy.md @@ -0,0 +1,199 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallroutingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsEmergencyCallRoutingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc +schema: 2.0.0 +--- + +# Grant-CsTeamsEmergencyCallRoutingPolicy + +## SYNOPSIS +This cmdlet assigns a Teams Emergency Call Routing policy. + +## SYNTAX + +### GrantToTenant (Default) +``` +Grant-CsTeamsEmergencyCallRoutingPolicy [[-PolicyName] <string>] [-Global] + [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsEmergencyCallRoutingPolicy [-Group] <string> [[-PolicyName] <string>] + [-PassThru] [-Rank <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Identity +``` +Grant-CsTeamsEmergencyCallRoutingPolicy [[-Identity] <string>] [[-PolicyName] <string>] + [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet assigns a Teams Emergency Call Routing policy to a user, a group of users, or to the Global policy instance. Teams Emergency Call Routing policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration. + +## EXAMPLES + +### Example 1 +```powershell +Grant-CsTeamsEmergencyCallRoutingPolicy -Identity user1 -PolicyName Test +``` + +This example assigns a Teams Emergency Call Routing policy (Test) to a user (user1). + +### Example 2 +```powershell +Grant-CsTeamsEmergencyCallRoutingPolicy -Group sales@contoso.com -Rank 10 -PolicyName Test +``` + +This example assigns the Teams Emergency Call Routing policy (Test) to the members of the group sales@contoso.com. + +## PARAMETERS + +### -Global +Sets the parameters of the Global policy instance to the values in the specified policy instance. + +```yaml +Type: SwitchParameter +Parameter Sets: (GrantToTenant) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Including this parameter (which does not take a value) displays the user information when the cmdlet completes. Normally there is no output when this cmdlet is run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The Identity of the Teams Emergency Call Routing policy to apply. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module version 4.5.1-preview or later. + +## RELATED LINKS + +[New-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallroutingpolicy) + +[Set-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallroutingpolicy) + +[Get-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallroutingpolicy) + +[Remove-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallroutingpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsEmergencyCallingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsEmergencyCallingPolicy.md new file mode 100644 index 0000000000..6a5ce3b2a9 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsEmergencyCallingPolicy.md @@ -0,0 +1,198 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsEmergencyCallingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc, pthota +schema: 2.0.0 +--- + +# Grant-CsTeamsEmergencyCallingPolicy + +## SYNOPSIS +This cmdlet assigns a Teams Emergency Calling policy. + +## SYNTAX + +### GrantToTenant (Default) +``` +Grant-CsTeamsEmergencyCallingPolicy [[-PolicyName] <string>] [-Global] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Identity +``` +Grant-CsTeamsCallingPolicy [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsEmergencyCallingPolicy [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet assigns a Teams Emergency Calling policy to a user, a group of users, or to the Global policy instance. Emergency Calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. + +## EXAMPLES + +### Example 1 +```powershell +Grant-CsTeamsEmergencyCallingPolicy -Identity user1 -PolicyName TestTECP +``` + +This example assigns the Teams Emergency Calling policy TestTECP to a user + +### Example 2 +```powershell +Grant-CsTeamsEmergencyCallingPolicy -Global -PolicyName SalesTECP +``` + +Assigns the Teams Emergency Calling policy called "SalesTECP" to the Global policy instance. This sets the parameters in the Global policy instance to the values found in the SalesTECP instance. + +## PARAMETERS + +### -Global +Sets the parameters of the Global policy instance to the values in the specified policy instance. + +```yaml +Type: SwitchParameter +Parameter Sets: (GrantToTenant) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Including this parameter (which does not take a value) displays the user information when the cmdlet completes. Normally there is no output when this cmdlet is run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The Identity of the Teams Emergency Calling policy to apply to the user. To remove an existing user level policy assignment, specify PolicyName as $null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +The GrantToGroup syntax is supported in Teams PowerShell Module version 4.5.1-preview or later. + +## RELATED LINKS + +[New-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingpolicy) + +[Get-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallingpolicy) + +[Remove-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallingpolicy) + +[Set-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallingpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsEnhancedEncryptionPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsEnhancedEncryptionPolicy.md new file mode 100644 index 0000000000..58b0be1886 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsEnhancedEncryptionPolicy.md @@ -0,0 +1,201 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsenhancedencryptionpolicy +title: Grant-CsTeamsEnhancedEncryptionPolicy +author: serdarsoysal +ms.author: serdars +manager: mdress +schema: 2.0.0 +--- + +# Grant-CsTeamsEnhancedEncryptionPolicy + +## SYNOPSIS +Cmdlet to assign a specific Teams enhanced encryption Policy to a user. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsEnhancedEncryptionPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>][-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsEnhancedEncryptionPolicy [-PassThru] [[-PolicyName] <String>] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsEnhancedEncryptionPolicy [-PassThru] [[-PolicyName] <String>] -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Cmdlet to assign a specific Teams enhanced encryption Policy to a user. + +The TeamsEnhancedEncryptionPolicy enables administrators to determine which users in your organization can use the enhanced encryption settings in Teams, setting for End-to-end encryption in ad-hoc 1-to-1 VOIP calls is the parameter supported by this policy currently. + +## EXAMPLES + +### EXAMPLE 1 +```PowerShell +PS C:\> Grant-CsTeamsEnhancedEncryptionPolicy -Identity 'KenMyer@contoso.com' -PolicyName 'ContosoPartnerTeamsEnhancedEncryptionPolicy' +``` + +The command shown in Example 1 assigns the per-user Teams enhanced encryption policy, ContosoPartnerTeamsEnhancedEncryptionPolicy, to the user with the user principal name (UPN) "KenMyer@contoso.com". + +### EXAMPLE 2 +```PowerShell +PS C:\> Grant-CsTeamsEnhancedEncryptionPolicy -Identity 'Ken Myer' -PolicyName $null +``` + +In Example 2, any per-user Teams enhanced encryption policy previously assigned to the user "Ken Myer" is revoked. + +As a result, the user will be managed by the global Teams enhanced encryption policy. + +## PARAMETERS + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsEnhancedEncryptionPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"). A policy that has an identity of "Tag:ContosoPartnerTeamsEnhancedEncryptionPolicy" has a PolicyName of "ContosoPartnerTeamsEnhancedEncryptionPolicy". If you set PolicyName to a null value, then the command will unassign any individual policy assigned to the user. For example: Grant-CsTeamsEnhancedEncryptionPolicy -Identity "Ken Myer" -PolicyName $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the Teams enhanced encryption policy. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -Global +Use this switch if you want to grant the specified policy to be the default policy for all users in the tenant. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Object +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsenhancedencryptionpolicy) + +[New-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsenhancedencryptionpolicy) + +[Set-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsenhancedencryptionpolicy) + +[Remove-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsenhancedencryptionpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsEventsPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsEventsPolicy.md new file mode 100644 index 0000000000..ad83d722d4 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsEventsPolicy.md @@ -0,0 +1,207 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamseventspolicy +title: Grant-CsTeamsEventsPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsEventsPolicy + +## SYNOPSIS +Assigns Teams Events policy to a user, group of users, or the entire tenant. Note that this policy is currently still in preview. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsEventsPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsEventsPolicy [-PassThru] [[-PolicyName] <String>] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsEventsPolicy [-PassThru] [[-PolicyName] <String>] + [-Group] <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Assigns Teams Events policy to a user, group of users, or the entire tenant. + +TeamsEventsPolicy is used to configure options for customizing Teams Events experiences. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsEventsPolicy -Identity "user1@contoso.com" -Policy DisablePublicWebinars +``` + +The command shown in Example 1 assigns the per-user Teams Events policy, DisablePublicWebinars, to the user with the user principal name (UPN) "user1@contoso.com". + +### Example 2 +```powershell +PS C:\> Grant-CsTeamsEventsPolicy -Identity "user1@contoso.com" -Policy $null +``` + +The command shown in Example 2 revokes the per-user Teams Events policy for the user with the user principal name (UPN) "user1@contoso.com". As a result, the user will be managed by the global Teams Events policy. + +### Example 3 +```powershell +PS C:\> Grant-CsTeamsEventsPolicy -Group "sales@contoso.com" -Rank 10 -Policy DisablePublicWebinars +``` + +The command shown in Example 3 assigns the Teams Events policy, DisablePublicWebinars, to the members of the group "sales@contoso.com". + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Use this switch if you want to grant the specified policy to be the default policy for all users in the tenant. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the identity of the target user. Acceptable values include: + +Example: jphillips@contoso.com + +Example: sip:jphillips@contoso.com + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Enables passing a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsEventsPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +"Name" of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:DisablePublicWebinars has a PolicyName equal to DisablePublicWebinars. + +To unassign a per-user policy previously assigned to a user, set the PolicyName to a null value ($Null). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsFeedbackPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsFeedbackPolicy.md new file mode 100644 index 0000000000..cacbfb5a0b --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsFeedbackPolicy.md @@ -0,0 +1,217 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsfeedbackpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsFeedbackPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: +--- + +# Grant-CsTeamsFeedbackPolicy + +## SYNOPSIS + +Use this cmdlet to grant a specific Teams Feedback policy to a user (the ability to send feedback about Teams to Microsoft and whether they receive the survey). + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsFeedbackPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsFeedbackPolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsFeedbackPolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Grants a specific Teams Feedback policy to a user (the ability to send feedback about Teams to Microsoft and whether they receive the survey) or to set a specific Teams feedback policy the new effective global policy. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsFeedbackPolicy -PolicyName "New Hire Feedback Policy" -Identity kenmyer@litwareinc.com +``` + +In this example, the policy "New Hire Feedback Policy" is granted to the user kenmyer@litwareinc.com. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Use this parameter to make the specified policy in -PolicyName the new effective global policy. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the identity of the user account the policy should be assigned to. + +```yaml +Type: Object +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Including this parameter (which does not take a value) displays the user information when the cmdlet completes. Normally there is no output when this cmdlet is run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The identity of the policy to be granted. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsFilesPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsFilesPolicy.md new file mode 100644 index 0000000000..3f44d72269 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsFilesPolicy.md @@ -0,0 +1,207 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsfilespolicy +title: Grant-CsTeamsFilesPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsFilesPolicy + +## SYNOPSIS + +This cmdlet applies an instance of the Teams AI policy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) + +```powershell +Grant-CsTeamsFilesPolicy [<CommonParameters>] +``` + +### GrantToUser + +```powershell +Grant-CsTeamsFilesPolicy -Identity <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup + +```powershell +Grant-CsTeamsFilesPolicy [[-PolicyName] <String>] [-Group] <String> -Rank <Int32> [<CommonParameters>] +``` + +### GrantToTenant + +```powershell +Grant-CsTeamsFilesPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Files Policy is used to modify files related settings in Microsoft teams. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Grant-CsTeamsFilesPolicy -PolicyName Test -Identity testuser@test.onmicrosoft.com +``` + +Assigns a given policy to a user. + +### Example 2 + +```powershell +PS C:\> Grant-CsTeamsFilesPolicy -Group f13d6c9d-ce76-422c-af78-b6018b4d9c80 -PolicyName Test +``` + +Assigns a given policy to a group. + +### Example 3 + +```powershell +PS C:\> Grant-CsTeamsFilesPolicy -Global -PolicyName Test +``` + +Assigns a given policy to the tenant. + +### Example 4 + +```powershell +PS C:\> Grant-CsTeamsFilesPolicy -Global -PolicyName Test +``` + +Note: _Using $null in place of a policy name can be used to unassigned a policy instance._ + +## PARAMETERS + +### -Force + +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +This is the equivalent to `-Identity Global`. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group + +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Specifies the identity of the target user. + +Example: <testuser@test.onmicrosoft.com> + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: GrantToUser +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PolicyName + +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), for example, a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +```yaml +Type: String +Parameter Sets: GrantToUser, GrantToGroup, GrantToTenant +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank + +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Grant-CsTeamsFilesPolicy](Grant-CsTeamsFilesPolicy.md) + +[Remove-CsTeamsFilesPolicy](Remove-CsTeamsFilesPolicy.md) + +[Get-CsTeamsFilesPolicy](Get-CsTeamsFilesPolicy.md) + +[Set-CsTeamsFilesPolicy](Set-CsTeamsFilesPolicy.md) + +[New-CsTeamsFilesPolicy](New-CsTeamsFilesPolicy.md) diff --git a/teams/teams-ps/teams/Grant-CsTeamsIPPhonePolicy.md b/teams/teams-ps/teams/Grant-CsTeamsIPPhonePolicy.md new file mode 100644 index 0000000000..4e0833c5a5 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsIPPhonePolicy.md @@ -0,0 +1,220 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsipphonepolicy +applicable: Microsoft Teams +title: Grant-CsTeamsIPPhonePolicy +author: tonywoodruff +ms.author: anwoodru +ms.reviewer: kponnus +manager: sandrao +schema: 2.0.0 +--- + +# Grant-CsTeamsIPPhonePolicy + +## SYNOPSIS + +Use the Grant-CsTeamsIPPhonePolicy cmdlet to assign a set of Teams phone policies to a user account or group of user accounts. Teams phone policies determine the features that are available to users of Teams phones. For example, you might enable the hot desking feature for some users while disabling it for others. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsIPPhonePolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsIPPhonePolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsIPPhonePolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use the Grant-CsTeamsIPPhonePolicy cmdlet to assign a set of Teams phone policies to a phone signed in with an account that may be used by end users, common area phones, or meeting room accounts. + +Note: Assigning a per user policy will override any global policy taking effect against the respective user account. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsIPPhonePolicy -Identity Foyer1@contoso.com -PolicyName CommonAreaPhone +``` + +This example shows assignment of the CommonAreaPhone policy to user account Foyer1@contoso.com. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Microsoft Internal Use Only. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Use this parameter to make the specified policy in -PolicyName the new effective global policy. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the identity of the user account the policy should be assigned to. + +```yaml +Type: Object +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Including this parameter (which does not take a value) displays the user information when the cmdlet completes. Normally there is no output when this cmdlet is run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The Identity of the Teams phone policy to apply to the user. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Microsoft internal usage only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsMediaConnectivityPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMediaConnectivityPolicy.md new file mode 100644 index 0000000000..126e7adfd2 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMediaConnectivityPolicy.md @@ -0,0 +1,191 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Grant-CsTeamsMediaConnectivityPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Grant-CsTeamsMediaConnectivityPolicy +schema: 2.0.0 +author: lirunping-MSFT +ms.author: runli +--- + +# Grant-CsTeamsMediaConnectivityPolicy + +## SYNOPSIS +This cmdlet applies an instance of the Teams media connectivity policy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsMediaConnectivityPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsMediaConnectivityPolicy -Identity <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsMediaConnectivityPolicy [[-PolicyName] <String>] [-Group] <String> -Rank <Int32> + [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsMediaConnectivityPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet applies an instance of the Teams media connectivity policy to users or groups in a tenant. + +Passes in the `Identity` of the policy instance in the `PolicyName` parameter and the user identifier in the `Identity` parameter or the group name in the `Group` parameter. One of either `Identity` or `Group` needs to be passed. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsMediaConnectivityPolicy -PolicyName Test -Identity testuser@test.onmicrosoft.com +``` + +Assigns a given policy to a user. + +### Example 2 +```powershell +PS C:\> Grant-CsTeamsMediaConnectivityPolicy -Group f13d6c9d-ce76-422c-af78-b6018b4d9c80 -PolicyName Test +``` + +Assigns a given policy to a group. + +### Example 3 +```powershell +PS C:\> Grant-CsTeamsMediaConnectivityPolicy -Global -PolicyName Test +``` + +Assigns a given policy to the tenant. + +### Example 4 +```powershell +PS C:\> Grant-CsTeamsMediaConnectivityPolicy -Global -PolicyName Test +``` + +Note: _Using $null in place of a policy name can be used to unassigned a policy instance._ + +## PARAMETERS + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +This is the equivalent to `-Identity Global`. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the identity of the target user. + +Example: testuser@test.onmicrosoft.com + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: GrantToUser +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), for example, a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +```yaml +Type: String +Parameter Sets: GrantToUser, GrantToGroup, GrantToTenant +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmediaconnectivitypolicy) + +[Remove-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmediaconnectivitypolicy) + +[Get-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmediaconnectivitypolicy) + +[Set-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmediaconnectivitypolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsMediaLoggingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMediaLoggingPolicy.md new file mode 100644 index 0000000000..960fd62910 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMediaLoggingPolicy.md @@ -0,0 +1,242 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsmedialoggingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsMediaLoggingPolicy +author: LeoKuhorev +ms.author: leokukharau +manager: shalages +schema: 2.0.0 +--- + +# Grant-CsTeamsMediaLoggingPolicy + +## SYNOPSIS + +Assigns Teams Media Logging policy to a user or entire tenant. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsMediaLoggingPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsMediaLoggingPolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsMediaLoggingPolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +Assigns Teams Media Logging policy to a user or entire tenant. +TeamsMediaLoggingPolicy allows administrators to enable media logging for users. When assigned, it will enable media logging for the user overriding other settings. After unassigning the policy, media logging setting will revert to the previous value. + +## EXAMPLES + +### EXAMPLE 1 + +```PowerShell +PS C:\> Grant-CsTeamsMediaLoggingPolicy -Identity 'KenMyer@contoso.com' -PolicyName Enabled +``` + +Assign Teams Media Logging policy to a single user with the user principal name (UPN) "KenMyer@contoso.com". This will enable media logging for the user. + +### EXAMPLE 2 + +```PowerShell +PS C:\> Grant-CsTeamsMediaLoggingPolicy -Identity 'KenMyer@contoso.com' -PolicyName $null +``` + +Unassign Teams Media Logging policy from a single user with the user principal name (UPN) "KenMyer@contoso.com". This will revert media logging setting to the previous value. + +### EXAMPLE 3 + +```PowerShell +PS C:\> Grant-CsTeamsMediaLoggingPolicy -Global -PolicyName Enabled +``` + +Assign Teams Media Logging policy to the entire tenant. Note that this will enable logging for every single user in the tenant without a possibility to disable it for individual users. + +### EXAMPLE 4 + +```PowerShell +PS C:\> Grant-CsTeamsMediaLoggingPolicy -Global -PolicyName $null +``` + +Unassign Teams Media Logging policy from the entire tenant. + +## PARAMETERS + +### -Identity + +Specifies the identity of the target user. +Acceptable values include: + +Example: jphillips@contoso.com + +Example: sip:jphillips@contoso.com + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru + +Enables passing a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsMediaLoggingPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName + +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), e.g. a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +Note that Teams Media Logging policy has only one instance that has PolicyName "Enabled". + +If you set PolicyName to a null value, the command will unassign any individual policy assigned to the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +When this cmdlet is used with `-Global` identity, the policy applies to all users in the tenant, except any that have an explicit policy assignment. For example, if the user already has Media Logging policy set to "Enabled", and tenant admin assigns "$null" globally, the user will still have Media Logging policy "Enabled". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsMediaLoggingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmedialoggingpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsMeetingBrandingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMeetingBrandingPolicy.md new file mode 100644 index 0000000000..cd29d655c1 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMeetingBrandingPolicy.md @@ -0,0 +1,168 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingbrandingpolicy +schema: 2.0.0 +title: Grant-CsTeamsMeetingBrandingPolicy +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: stanlythomas +--- + +# Grant-CsTeamsMeetingBrandingPolicy + +## SYNOPSIS +Assigns a teams meeting branding policy at the per-user scope. The **CsTeamsMeetingBrandingPolicy** cmdlet enables administrators to control the appearance in meetings by defining custom backgrounds, logos, and colors. + +## SYNTAX + +### GrantToUser +``` +Grant-CsTeamsMeetingBrandingPolicy -Identity <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsMeetingBrandingPolicy [[-PolicyName] <String>] [-Group] <String> -Rank <Int32> + [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsMeetingBrandingPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +Assigns a teams meeting branding policy at the per-user scope. The **CsTeamsMeetingBrandingPolicy** cmdlet enables administrators to control the appearance in meetings by defining custom backgrounds, logos, and colors. + +## EXAMPLES + +### Assign TeamsMeetingBrandingPolicy to a user +```powershell +PS C:\> Grant-CsTeamsMeetingBrandingPolicy -identity "alice@contoso.com" -PolicyName "Policy Test" +``` + +In this example, the command assigns TeamsMeetingBrandingPolicy with the name `Policy Test` to user `alice@contoso.com`. + +### Assign TeamsMeetingBrandingPolicy to a group +```powershell +PS C:\> Grant-CsTeamsMeetingBrandingPolicy -Group group@contoso.com -PolicyName "Policy Test" -Rank 1 +``` + +In this example, the command will assign TeamsMeetingBrandingPolicy with the name `Policy Test` to group `group@contoso.com`. + +## PARAMETERS + +### -Global +Use this switch if you want to grant the specified policy to be the default policy for all users in the tenant. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The user you want to grant policy to. This can be specified as an SIP address, UserPrincipalName, or ObjectId. + +```yaml +Type: String +Parameter Sets: GrantToUser +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign it to `$Null`. + +```yaml +Type: String +Parameter Sets: GrantToUser, GrantToGroup, GrantToTenant +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +Available in Teams PowerShell Module 4.9.3 and later. + +## RELATED LINKS + +[Get-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbrandingpolicy) + +[Grant-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingbrandingpolicy) + +[New-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingbrandingpolicy) + +[Remove-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingbrandingpolicy) + +[Set-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbrandingpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsMeetingBroadcastPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMeetingBroadcastPolicy.md new file mode 100644 index 0000000000..1fac390b29 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMeetingBroadcastPolicy.md @@ -0,0 +1,207 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingbroadcastpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsMeetingBroadcastPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Grant-CsTeamsMeetingBroadcastPolicy + +## SYNOPSIS +Grant-CsTeamsMeetingBroadcastPolicy \[\[-Identity\] \<UserIdParameter\>\] \[-PolicyName\] \<string\> \[-Tenant \<guid\>\] \[-DomainController \<Fqdn\>\] \[-PassThru\] \[-WhatIf\] \[-Confirm\] \[\<CommonParameters\>\] + +Grant-CsTeamsMeetingBroadcastPolicy \[-PolicyName\] \<string\> \[-Tenant \<guid\>\] \[-DomainController \<Fqdn\>\] \[-PassThru\] \[-Global\] \[-WhatIf\] \[-Confirm\] \[\<CommonParameters\>\] + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsMeetingBroadcastPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsMeetingBroadcastPolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsMeetingBroadcastPolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +User-level policy for tenant admin to configure meeting broadcast behavior for the broadcast event organizer. Use this cmdlet to assign a policy to a user. + +## EXAMPLES + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Not applicable to online service. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsMeetingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMeetingPolicy.md new file mode 100644 index 0000000000..555e7a9518 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMeetingPolicy.md @@ -0,0 +1,186 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsMeetingPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Grant-CsTeamsMeetingPolicy + +## SYNOPSIS +Assigns a teams meeting policy at the per-user scope. The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users + +## SYNTAX + +### GrantToTenant (Default) +```powershell +Grant-CsTeamsMeetingPolicy [-Global] [-PassThru] [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsTeamsMeetingPolicy [-PassThru] [[-PolicyName] <String>] + [[-Group] <String>] [-Rank <Int32>] [<CommonParameters>] +``` + +### Identity +```powershell +Grant-CsTeamsMeetingPolicy [-PassThru] [[-PolicyName] <String>] + [[-Identity] <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Assigns a teams meeting policy at the per-user scope. The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsMeetingPolicy -identity "Ken Myer" -PolicyName StudentMeetingPolicy +``` + +In this example, a user with identity "Ken Myer" is being assigned the StudentMeetingPolicy + +## PARAMETERS + +### -DomainController + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsMeetingTemplatePermissionPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMeetingTemplatePermissionPolicy.md new file mode 100644 index 0000000000..591125a048 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMeetingTemplatePermissionPolicy.md @@ -0,0 +1,168 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +title: Grant-CsTeamsMeetingTemplatePermissionPolicy +author: boboPD +ms.author: pradas +online version: https://learn.microsoft.com/powershell/module/teams/Grant-CsTeamsMeetingTemplatePermissionPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsMeetingTemplatePermissionPolicy + +## SYNOPSIS +This cmdlet applies an instance of the TeamsMeetingTemplatePermissionPolicy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsMeetingTemplatePermissionPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsMeetingTemplatePermissionPolicy [-Identity] <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsMeetingTemplatePermissionPolicy [[-PolicyName] <String>] [-Group] <String> [-Rank] <Int32> + [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsMeetingTemplatePermissionPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet applies an instance of the TeamsMeetingTemplatePermissionPolicy to users or groups in a tenant. + +Pass in the `Identity` of the policy instance in the `PolicyName` parameter and the user identifier in the `Identity` parameter or the group name in the `Group` parameter. One of either `Identity` or `Group` needs to be passed. + +## EXAMPLES + +### Example 1 - Assign a policy to a user + +```powershell +PS> Grant-CsTeamsMeetingTemplatePermissionPolicy -PolicyName Foobar -Identity testuser@test.onmicrosoft.com +``` + +Assigns a given policy to a user. + +## PARAMETERS + +### -PolicyName + +Specifies the Identity of the policy to assign to the user or group. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +This is the identifier of the user that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group + +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +This is the equivalent to `-Identity Global`. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +Forces the policy assignment. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingtemplatepermissionpolicy) + +[New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy) + +[Set-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingtemplatepermissionpolicy) + +[Remove-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingtemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsMessagingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMessagingPolicy.md new file mode 100644 index 0000000000..cbe96c09cb --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMessagingPolicy.md @@ -0,0 +1,220 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsmessagingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsMessagingPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Grant-CsTeamsMessagingPolicy + +## SYNOPSIS +Assigns a teams messaging policy at the per-user scope. Teams messaging policies determine the features and capabilities that can be used in messaging within the teams client. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsMessagingPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsMessagingPolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsMessagingPolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Granular control over which messaging features your users can or cannot use is an important feature for many organizations. This cmdlet lets you assign a teams messaging policy at the per-user scope. Teams messaging policies determine the features and capabilities that can be used in messaging within the teams client. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsMessagingPolicy -identity "Ken Myer" -PolicyName StudentMessagingPolicy +``` + +In this example, a user with identity "Ken Myer" is being assigned the StudentMessagingPolicy + +### Example 2 +```powershell +PS C:\> Get-CsOnlineUser -Filter {Department -eq 'Executive Management'} | Grant-CsTeamsMessagingPolicy -PolicyName "ExecutivesPolicy" +``` + +In this example, the ExecutivesPolicy is being assigned to a whole department by piping the result of Get-CsOnlineUser cmdlet + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsMobilityPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsMobilityPolicy.md new file mode 100644 index 0000000000..9ca488f23b --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsMobilityPolicy.md @@ -0,0 +1,187 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsmobilitypolicy +applicable: Microsoft Teams +title: Grant-CsTeamsMobilityPolicy +schema: 2.0.0 +manager: ritikag +ms.reviewer: ritikag +--- + +# Grant-CsTeamsMobilityPolicy + +## SYNOPSIS +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsMobilityPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsMobilityPolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsMobilityPolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Assigns a teams mobility policy at the per-user scope. + +The Grant-CsTeamsMobilityPolicy cmdlet lets an Admin assign a custom teams mobility policy to a user. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsMobilityPolicy -PolicyName SalesPolicy -Identity "Ken Myer" +``` +Assigns a custom policy "Sales Policy" to the user "Ken Myer" + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The User Id of the user to whom the policy is being assigned. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the Global policy, you can assign $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the Teams call hold policy. + +By default, the cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsRecordingRollOutPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsRecordingRollOutPolicy.md new file mode 100644 index 0000000000..de38261c46 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsRecordingRollOutPolicy.md @@ -0,0 +1,85 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsrecordingrolloutpolicy +schema: 2.0.0 +applicable: Microsoft Teams +title: Grant-CsTeamsRecordingRollOutPolicy +manager: yujin1 +author: ronwa +ms.author: ronwa +--- + +# Grant-CsTeamsRecordingRollOutPolicy + +## SYNOPSIS +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. + +## SYNTAX + +``` +Grant-CsTeamsRecordingRollOutPolicy -Identity <String> -PolicyName <String> [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. This policy would be deprecated over time as this is only to allow IT admins to phase the roll out of this breaking change. + +The Grant-CsTeamsRecordingRollOutPolicy cmdlet allows administrators to assign a CsTeamsRecordingRollOutPolicy at the per-user scope. + +This command is available from Teams powershell module 6.1.1-preview and above. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsMeetingPolicy -identity "Ken Myer" -PolicyName OrganizerPolicy +``` + +In this example, a user with identity "Ken Myer" is being assigned the OrganizerPolicy + +## PARAMETERS + +### -Identity +Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsRoomVideoTeleConferencingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsRoomVideoTeleConferencingPolicy.md new file mode 100644 index 0000000000..e9460ea3d0 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsRoomVideoTeleConferencingPolicy.md @@ -0,0 +1,204 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsroomvideoteleconferencingpolicy +title: Grant-CsTeamsRoomVideoTeleConferencingPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsRoomVideoTeleConferencingPolicy + +## SYNOPSIS + +Assigns a TeamsRoomVideoTeleConferencingPolicy to a Teams Room Alias on a per-room or per-Group basis. + +## SYNTAX + +### Identity (Default) + +```powershell +Grant-CsTeamsRoomVideoTeleConferencingPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant + +```powershell +Grant-CsTeamsRoomVideoTeleConferencingPolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup + +```powershell +Grant-CsTeamsRoomVideoTeleConferencingPolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Group] <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Room Video Teleconferencing Policy enables administrators to configure and manage video teleconferencing behavior for Microsoft Teams Rooms (meeting room devices). + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +When you use this cmdlet without specifying a identity, the policy applies to all rooms in your tenant, except any that have an explicit policy assignment. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group + +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The alias of the Teams room that the IT admin is granting this PolicyName to. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +Allows the user to indicate whether the cmdlet passes an output object through the pipeline, in this case, after a process is stopped. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName + +Corresponds to the name of the policy under -Identity from the cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank + +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsSharedCallingRoutingPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsSharedCallingRoutingPolicy.md new file mode 100644 index 0000000000..4eb7f30ac5 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsSharedCallingRoutingPolicy.md @@ -0,0 +1,168 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamssharedcallingroutingpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsSharedCallingRoutingPolicy +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Grant-CsTeamsSharedCallingRoutingPolicy + +## SYNOPSIS + +Assigns a specific Teams shared calling routing policy to a user, a group of users, or sets the Global policy instance. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsSharedCallingRoutingPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsSharedCallingRoutingPolicy [[-PolicyName] <string>] -Identity <string> [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsSharedCallingRoutingPolicy -Global [[-PolicyName] <string>] [-Force] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsSharedCallingRoutingPolicy [-Group] <string> [[-PolicyName] <string>] -Rank <int> [<CommonParameters>] +``` + +## EXAMPLES + +### EXAMPLE 1 +``` +Grant-CsTeamsSharedCallingRoutingPolicy -Identity "user@contoso.com" -PolicyName "Seattle" +``` +The command shown in Example 1 assigns the per-user Teams shared calling routing policy instance Seattle to the user user@contoso.com. + +### EXAMPLE 2 +``` +Grant-CsTeamsSharedCallingRoutingPolicy -PolicyName "Seattle" -Global +``` +Example 2 assigns the per-user Teams shared calling routing policy instance Seattle to all the users in the organization, except any that have an explicit Teams shared calling routing policy assignment. + +## PARAMETERS + +### -Identity +Indicates the Identity of the user account to be assigned the per-user Teams shared calling routing policy. User identities can be specified using one of the following formats: the user's SIP address, the user's user principal name (UPN), or the user's ObjectId or Identity. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PolicyName +Name of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:Seattle has a PolicyName equal to Seattle. + +To unassign a per-user policy previously assigned to a user, set the PolicyName to a null value ($Null). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your organization, except any that have an explicit policy assignment. To prevent a warning when you carry out this operation, specify this parameter. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: (GrantToGroup) +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: (GrantToGroup) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +This cmdlet was introduced in Teams PowerShell Module 5.5.0. + +## RELATED LINKS +[Get-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamssharedcallingroutingpolicy) + +[Set-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamssharedcallingroutingpolicy) + +[Remove-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamssharedcallingroutingpolicy) + +[New-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamssharedcallingroutingpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsShiftsPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsShiftsPolicy.md new file mode 100644 index 0000000000..43875faa32 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsShiftsPolicy.md @@ -0,0 +1,162 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-teamsshiftspolicy +title: Grant-CsTeamsShiftsPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsShiftsPolicy + +## SYNOPSIS + +This cmdlet supports applying the TeamsShiftsPolicy to users in a tenant. + +## SYNTAX + +### Identity (Default) +```powershell +Grant-CsTeamsShiftsPolicy [<CommonParameters>] +``` + +### GrantToUser +```powershell +Grant-CsTeamsShiftsPolicy [-Identity] <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsTeamsShiftsPolicy [[-PolicyName] <String>] [-Group] <String> [-Rank] <Int32> [<CommonParameters>] +``` + +### GrantToTenant +```powershell +Grant-CsTeamsShiftsPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet enables admins to grant Shifts specific policy settings to users in their tenant. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsShiftsPolicy -Identity IsaiahL@mwtdemo.onmicrosoft.com -PolicyName OffShiftAccessMessage1Always +``` +Applies the OffShiftAccessMessage1Always instance of TeamsShiftsPolicy to one user in the tenant. + +## PARAMETERS + +### -Identity +UserId to whom the policy is granted. Email id is acceptable. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PolicyName +The name of the TeamsShiftsPolicy instance that is being applied to the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named + +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftspolicy) + +[New-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftspolicy) + +[Set-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftspolicy) + +[Remove-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftspolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsSurvivableBranchAppliancePolicy.md b/teams/teams-ps/teams/Grant-CsTeamsSurvivableBranchAppliancePolicy.md new file mode 100644 index 0000000000..bbe885264d --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsSurvivableBranchAppliancePolicy.md @@ -0,0 +1,199 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamssurvivablebranchappliancepolicy +title: Grant-CsTeamsSurvivableBranchAppliancePolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsSurvivableBranchAppliancePolicy + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) Policy cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +### Identity (Default) + +```powershell +Grant-CsTeamsSurvivableBranchAppliancePolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant + +```powershell +Grant-CsTeamsSurvivableBranchAppliancePolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup + +```powershell +Grant-CsTeamsSurvivableBranchAppliancePolicy [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Group] <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group + +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the user. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +Enables you to pass a user object through the pipeline that represents the user account being assigned the policy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName + +Name of the policy to be assigned. The PolicyName is simply the policy Identity without the policy scope, i.e. the "Tag:" prefix. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank + +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsUpdateManagementPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsUpdateManagementPolicy.md new file mode 100644 index 0000000000..d17f961f44 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsUpdateManagementPolicy.md @@ -0,0 +1,157 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsupdatemanagementpolicy +applicable: Microsoft Teams +title: Grant-CsTeamsUpdateManagementPolicy +schema: 2.0.0 +author: vargasj-ms +ms.author: vargasj +manager: gnamun +--- + +# Grant-CsTeamsUpdateManagementPolicy + +## SYNOPSIS +Use this cmdlet to grant a specific Teams Update Management policy to a user. + +## SYNTAX + +### Identity (Default) +```powershell +Grant-CsTeamsUpdateManagementPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-ProgressAction <ActionPreference>] + [<CommonParameters>] +``` + +### GrantToTenant +```powershell +Grant-CsTeamsUpdateManagementPolicy [-PassThru] [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] + [-Global] [-ProgressAction <ActionPreference>] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsTeamsUpdateManagementPolicy [-PassThru] [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] + [-Group] <String> [-Rank <Int32>] [-ProgressAction <ActionPreference>] + [<CommonParameters>] +``` + +## DESCRIPTION +Grants a specific Teams Update Management policy to a user or sets a specific Teams Update Management policy as the new effective global policy. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsUpdateManagementPolicy -PolicyName "Campaign Policy" -Identity kenmyer@litwareinc.com +``` + +In this example, the policy "Campaign Policy" is granted to the user kenmyer@litwareinc.com. + +## PARAMETERS + +### -Global +Use this parameter to make the specified policy in -PolicyName the new effective global policy. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the identity of the user account the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Including this parameter (which does not take a value) displays the user information when the cmdlet completes. Normally there is no output when this cmdlet is run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The identity of the policy to be granted. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsUpgradePolicy.md b/teams/teams-ps/teams/Grant-CsTeamsUpgradePolicy.md new file mode 100644 index 0000000000..54251476e5 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsUpgradePolicy.md @@ -0,0 +1,325 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/skype/grant-csteamsupgradepolicy +applicable: Microsoft Teams +title: Grant-CsTeamsUpgradePolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Grant-CsTeamsUpgradePolicy + +## SYNOPSIS +TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. + +## SYNTAX + +### Identity (Default) +```powershell +Grant-CsTeamsUpgradePolicy [[-Identity] <String>] [-MigrateMeetingsToTeams <Boolean>] [-PassThru] + [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] [<CommonParameters>] +``` + +### GrantToTenant +```powershell +Grant-CsTeamsUpgradePolicy [-MigrateMeetingsToTeams <Boolean>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-Force] [-Global] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsTeamsUpgradePolicy [-MigrateMeetingsToTeams <Boolean>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] -Group <String> [-Rank <Int32>] + [<CommonParameters>] +``` + +## DESCRIPTION + +TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. As an organization with Skype for Business starts to adopt Teams, administrators can manage the user experience in their organization using the concept of coexistence "mode". Mode defines in which client incoming chats and calls land as well as in what service (Teams or Skype for Business) new meetings are scheduled in. Mode also governs what functionality is available in the Teams client. Finally, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. + +This cmdlet enables admins to apply TeamsUpgradePolicy to either individual users or to set the default for the entire organization. + +**NOTE**: Earlier versions of this cmdlet used to support -MigrateMeetingsToTeams option. This option is removed in later versions of the module. Tenants must run Start-CsExMeetingMigration. See [Start-CsExMeetingMigrationService](https://learn.microsoft.com/powershell/module/skype/start-csexmeetingmigration). + +Microsoft Teams provides all relevant instances of TeamsUpgradePolicy via built-in, read-only policies. The built-in instances are as follows: + +|Identity|Mode|NotifySfbUsers|Comments| +|---|---|---|---| +|Islands|Islands|False|Default configuration. Allows a single user to evaluate both clients side by side. Chats and calls can land in either client, so users must always run both clients.| +|IslandsWithNotify|Islands|True|Same as Islands and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.| +|SfBOnly|SfBOnly|False|Calling, chat functionality and meeting scheduling in the Teams app are disabled.| +|SfBOnlyWithNotify|SfBOnly|True|Same as SfBOnly and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.| +|SfBWithTeamsCollab|SfBWithTeamsCollab|False|Calling, chat functionality and meeting scheduling in the Teams app are disabled.| +|SfBWithTeamsCollabWithNotify|SfBWithTeamsCollab|True|Same as SfBWithTeamsCollab and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.| +|SfBWithTeamsCollabAndMeetings|SfBWithTeamsCollabAndMeetings|False|Calling and chat functionality in the Teams app are disabled.| +|SfBWithTeamsCollabAndMeetingsWithNotify|SfBWithTeamsCollabAndMeetings|True|Same as SfBWithTeamsCollabAndMeetings and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.| +|UpgradeToTeams|TeamsOnly|False|Use this mode to upgrade users to Teams and to prevent chat, calling, and meeting scheduling in Skype for Business.| +|Global|Islands|False|| + +> [!IMPORTANT] +> TeamsUpgradePolicy can be assigned to any Teams user, whether that user have an on-premises account in Skype for Business Server or not. However, **TeamsOnly mode can only be assigned to a user who is already homed in Skype for Business Online**. This is because interop with Skype for Business users and federation as well as Microsoft 365 Phone System functionality are only possible if the user is homed in Skype for Business Online. In addition, you cannot assign TeamsOnly mode as the tenant-wide default if you have any Skype for Business on-premises deployment (which is detected by presence of a lyncdiscover DNS record that points to a location other than Office 365. To make these users TeamsOnly you must first move these users individually to the cloud using `Move-CsUser`. Once all users have been moved to the cloud, you can [disable hybrid to complete migration to the cloud](https://learn.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid) and then apply TeamsOnly mode at the tenant level to ensure future users are TeamsOnly by default. + +> [!NOTE] +> +> - TeamsUpgradePolicy is available in both Office 365 and in on-premises versions of Skype for Business Server, but there are differences: +> - In Office 365, admins can specify both coexistence mode and whether to trigger notifications of pending upgrade. +> - In on-premises with Skype for Business Server, the only available option is to trigger notifications. Skype for Business Server 2015 with CU8 or Skype for Business Server 2019 are required. +> - TeamsUpgradePolicy in Office 365 can be granted to users homed on-premises in hybrid deployments of Skype for Business as follows: +> - Coexistence mode is honored by users homed on-premises, however on-premises users cannot be granted the UpgradeToTeams instance (mode=TeamsOnly) of TeamsUpgradePolicy. To be upgraded to TeamsOnly mode, users must be either homed in Skype for Business Online or have no Skype account anywhere. +> - The NotifySfBUsers setting of Office 365 TeamsUpgradePolicy is not honored by users homed on-premises. Instead, the on-premises version of TeamsUpgradePolicy must be used. +> - In Office 365, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet available. In contrast, Skype for Business Server does not contain built-in instances, so the New cmdlet is available on-premises. Only NotifySfBUsers property is available in on-premises. +> - When granting a user a policy with mode=TeamsOnly or mode=SfBWithTeamsCollabAndMeetings, by default, meetings organized by that user will be migrated to Teams. For details, see [Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms). + +When users are in any of the Skype for Business modes (SfBOnly, SfBWithTeamsCollab, SfBWithTeamsCollabAndMeetings), calling and chat functionality in the Teams app are disabled (but chat in the context of a Teams meeting is still allowed). Similarly, when users are in the SfBOnly or SfBWithTeamsCollab modes, meeting scheduling is disabled. For more details, see [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype). + +The `Grant-CsTeamsUpgradePolicy` cmdlet checks the configuration of the corresponding settings in TeamsMessagingPolicy, TeamsCallingPolicy, and TeamsMeetingPolicy to determine if those settings would be superceded by TeamsUpgradePolicy and if so, an informational message is provided in PowerShell. It is not necessary to set these other policy settings. This is for informational purposes only. Below is an example of what the PowerShell warning looks like: + +`Grant-CsTeamsUpgradePolicy -Identity user1@contoso.com -PolicyName SfBWithTeamsCollab` + +**WARNING**: The user `user1@contoso.com` currently has enabled values for: AllowUserChat, AllowPrivateCalling, AllowPrivateMeetingScheduling, AllowChannelMeetingScheduling, however these values will be ignored. This is because you are granting this user TeamsUpgradePolicy with mode=SfBWithTeamsCollab, which causes the Teams client to behave as if they are disabled. + +> [!NOTE] +> These warning messages are not affected by the -WarningAction parameter. + +## EXAMPLES + +### Example 1: Grant Policy to an individual user + +```powershell +PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity mike@contoso.com +``` + +The above cmdlet assigns the "UpgradeToTeams" policy to user Mike@contoso.com. This effectively upgrades the user to Teams only mode. This command will only succeed if the user does not have an on-premises Skype for Business account. + +### Example 2: Remove Policy for an individual user + +```powershell +PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName $null -Identity mike@contoso.com +``` + +The above cmdlet removes any policy changes made to user Mike@contoso.com and effectively Inherits the global tenant setting for teams Upgrade. + +### Example 3: Grant Policy to the entire tenant + +```powershell +PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly -Global +``` + +To grant a policy to all users in the org (except any that have an explicit policy assigned), omit the identity parameter. If you do not specify the -Global parameter, you will be prompted to confirm the operation. + +### Example 4 Get a report on existing TeamsUpgradePolicy users (Screen Report) + +```powershell +Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* +``` + +You can get the output on the screen, on CSV or Html format. For Screen Report. + +### Example 5 Get a report on existing TeamsUpgradePolicy users (CSV Report) + +```powershell +$objUsers = Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* +$objusers | ConvertTo-Csv -NoTypeInformation | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.csv" +``` + +This will create a CSV file on the Desktop of the current user with the name "TeamsUpgrade.csv" + +### Example 6 Get a report on existing TeamsUpgradePolicy users (HTML Report) + +```powershell +$objUsers = Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* +$objusers | ConvertTo-Html | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.html" +``` + +After running these lines will create an HTML file on the Desktop of the current user with the name "TeamUpgrade.html" + +### Example 7 Get a report on existing TeamsUpgradePolicy users (CSV Report - Oneliner version) + +```powershell +Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* | ConvertTo-Csv -NoTypeInformation | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.csv" +``` + +This will create a CSV file on the Desktop of the current user with the name "TeamsUpgrade.csv" + +### Example 8 Get a report on existing TeamsUpgradePolicy users (HTML Report - Oneliner Version) + +```powershell +Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* | ConvertTo-Html | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.html" +``` + +After running these lines will create an HTML file on the Desktop of the current user with the name "TeamUpgrade.html" + +## PARAMETERS + +### -Identity + +The user you want to grant policy to. This can be specified as SIP address, UserPrincipalName, or ObjectId. + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PolicyName + +The name of the policy instance. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +Use this switch if you want to grant the specified policy to be the default policy for all users in the tenant. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +Do not use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrateMeetingsToTeams +Not supported anymore, see the Description section. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the Teams call hold policy. + +By default, the cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) + +[Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms) + +[Coexistence with Skype for Business](https://learn.microsoft.com/microsoftteams/coexistence-chat-calls-presence) + +[Get-CsTeamsUpgradeConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsupgradeconfiguration) + +[Set-CsTeamsUpgradeConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsupgradeconfiguration) + +[Get-CsTeamsUpgradePolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsupgradepolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsVdiPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsVdiPolicy.md new file mode 100644 index 0000000000..6d3a365fa0 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsVdiPolicy.md @@ -0,0 +1,153 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsvdipolicy +title: Grant-CsTeamsVdiPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsVdiPolicy + +## SYNOPSIS +Assigns a teams Vdi policy at the per-user scope. The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +## SYNTAX + +### Identity (Default) +```powershell +Grant-CsTeamsVdiPolicy [<CommonParameters>] +``` + +### GrantToUser +```powershell +Grant-CsTeamsVdiPolicy -Identity <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +```powershell +Grant-CsTeamsVdiPolicy [[-PolicyName] <String>] [-Group] <String> -Rank <Int32> [<CommonParameters>] +``` + +### GrantToTenant +```powershell +Grant-CsTeamsVdiPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +Assigns a teams Vdi policy at the per-user scope. The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsVdiPolicy -identity "Ken Myer" -PolicyName RestrictedUserPolicy +``` + +In this example, a user with identity "Ken Myer" is being assigned the RestrictedUserPolicy + +## PARAMETERS + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant. To skip a warning when you do this operation, specify "-Global". + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name. + +```yaml +Type: String +Parameter Sets: GrantToUser +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -PolicyName +The name of the custom policy that is being assigned to the user. To remove a specific assignment and fall back to the default tenant policy, you can assign to $Null. + +```yaml +Type: String +Parameter Sets: GrantToUser, GrantToGroup, GrantToTenant +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsVideoInteropServicePolicy.md b/teams/teams-ps/teams/Grant-CsTeamsVideoInteropServicePolicy.md new file mode 100644 index 0000000000..a6a5f02703 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsVideoInteropServicePolicy.md @@ -0,0 +1,266 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsvideointeropservicepolicy +applicable: Microsoft Teams +Module Name: MicrosoftTeams +title: Grant-CsTeamsVideoInteropServicePolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Grant-CsTeamsVideoInteropServicePolicy + +## SYNOPSIS + +Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. You can use the TeamsVideoInteropServicePolicy cmdlets to enable Cloud Video Interop for particular users or for your entire organization. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsVideoInteropServicePolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsVideoInteropServicePolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsVideoInteropServicePolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. You can use the TeamsVideoInteropServicePolicy cmdlets to enable Cloud Video Interop for particular users or for your entire organization. Microsoft provides pre-constructed policies for each of our supported partners that allow you to designate which of the partners to use for cloud video interop. + +The Grant-CsTeamsVideoInteropServicePolicy cmdlet allows you to assign a pre-constructed policy across your whole organization or only to specific users. + +User needs to be assigned one policy from admin to create a CVI meeting. There could be multiple provides in a tenant, but user can only be assigned only one policy(provide). + +**FAQ**: + +Q: After running `Grant-CsTeamsVideoInteropServicePolicy -PolicyName <Identity of the Policy>` to assign a policy to the whole tenant, the result of `Get-CsOnlineUser -Identity {User Identity} | Format-List TeamsVideoInteropServicePolicy` that checks if the User Policy is empty. + +A: Global/Tenant level Policy Assignment can be checked by running `Get-CsTeamsVideoInteropServicePolicy Global`. + +Q: I assigned CVI policy to a user, but I can't create a VTC meeting with that policy or I made changes to policy assignment, but it didn't reflect on new meetings I created. + +A: The policy is cached for 6 hours. Changes to the policy are updated after the cache expires. Check for your changes after 6 hours. + +**Frequently used commands that can help identify the policy assignment**: + +- Command to get full list of user along with their CVI policy: `Get-CsOnlineUser | Format-List UserPrincipalName,TeamsVideoInteropServicePolicy` + +- Command to get the policy assigned to the whole tenant: `Get-CsTeamsVideoInteropServicePolicy Global` + +## EXAMPLES + +### Example 1: The whole tenant has the same provider + +```powershell +Grant-CsTeamsVideoInteropServicePolicy -PolicyName <Identity of the Policy | $null> -Global +``` + +Specify the provider for the whole tenant or use the value $null to remove the tenant-level provider and let the whole tenant fall back to the Global policy. + +### Example 2: The tenant has two (or three) interop service providers + +```powershell +Grant-CsTeamsVideoInteropServicePolicy -PolicyName <Identity of the Policy | $null> -Identity <UserId> +``` + +Specify each user with the Identity parameter, and use Provider-1 or Provider-2 for the value of the PolicyName parameter. Use the value $null to remove the provider and let the user's provider fallback to Global policy. + +### Example 3: The tenant has a default interop service provider, but specific users (say IT folks) want to pilot another interop provider. + +```powershell +Grant-CsTeamsVideoInteropServicePolicy -PolicyName <Identity of the Policy | ServiceProviderDisabled> [-Identity <UserId>] +``` + +- To assign Provider-1 as the default interop service provider, don't use the Identity parameter and use the value Provider-1 for the PolicyName parameter. + +- For specific users to try Provider-2, specify each user with the Identity parameter, and use the value Provider-2 for the PolicyName parameter. + +- For specific users who need to disable CVI, specify each user with the Identity parameter and use the value ServiceProviderDisabled for the PolicyName parameter. + +### Example 4: Cloud Video Interop has been disabled for the entire tenant, except for those users that have an explicit policy assigned to them. + +```powershell +Grant-CsTeamsVideoInteropServicePolicy -PolicyName ServiceProviderDisabled +``` + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Internal Microsoft use only. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +Use this flag to override the warning when assigning the global policy for your tenant. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +{{Fill Identity Description}} + +```yaml +Type: UserIdParameter +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsVideoInteropServicePolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Specify the pre-constructed policy that you would like to assign to your tenant or a particular user. You can get the policies available for your organization using the cmdlet Get-CsTeamsVideoInteropServicePolicy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.AD.UserIdParameter + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Grant-CsTeamsVirtualAppointmentsPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsVirtualAppointmentsPolicy.md new file mode 100644 index 0000000000..1203279e74 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsVirtualAppointmentsPolicy.md @@ -0,0 +1,195 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsvirtualappointmentspolicy +title: Grant-CsTeamsVirtualAppointmentsPolicy +schema: 2.0.0 +ms.author: erocha +manager: sonaggarwal +author: emmanuelrocha001 +--- + +# Grant-CsTeamsVirtualAppointmentsPolicy + +## SYNOPSIS +This cmdlet applies an instance of the TeamsVirtualAppointmentsPolicy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsVirtualAppointmentsPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsVirtualAppointmentsPolicy -Identity <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsVirtualAppointmentsPolicy [[-PolicyName] <String>] [-Group] <String> -Rank <Int32> + [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsVirtualAppointmentsPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet applies an instance of the TeamsVirtualAppointmentsPolicy to users or groups in a tenant. + +Passes in the `Identity` of the policy instance in the `PolicyName` parameter and the user identifier in the `Identity` parameter or the group name in the `Group` parameter. One of either `Identity` or `Group` needs to be passed. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsVirtualAppointmentsPolicy -PolicyName sms-enabled -Identity testuser@test.onmicrosoft.com +``` + +Assigns a given policy to a user. + +### Example 2 +```powershell +PS C:\> Grant-CsTeamsVirtualAppointmentsPolicy -Group f13d6c9d-ce76-422c-af78-b6018b4d9c80 -PolicyName sms-enabled +``` + +Assigns a given policy to a group. + +### Example 3 +```powershell +PS C:\> Grant-CsTeamsVirtualAppointmentsPolicy -Global -PolicyName sms-enabled +``` + +Assigns a given policy to the tenant. + +### Example 3 +```powershell +PS C:\> Grant-CsTeamsVirtualAppointmentsPolicy -Global -PolicyName sms-enabled +``` + +Note: _Using $null in place of a policy name can be used to unassigned a policy instance._ + +## PARAMETERS + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +This is the equivalent to `-Identity Global`. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the identity of the target user. + +Example: testuser@test.onmicrosoft.com + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: GrantToUser +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), for example, a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +```yaml +Type: String +Parameter Sets: GrantToUser, GrantToGroup, GrantToTenant +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvirtualappointmentspolicy) + +[New-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvirtualappointmentspolicy) + +[Set-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvirtualappointmentspolicy) + +[Remove-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvirtualappointmentspolicy) + diff --git a/teams/teams-ps/teams/Grant-CsTeamsVoiceApplicationsPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsVoiceApplicationsPolicy.md new file mode 100644 index 0000000000..e97f8b3ab1 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsVoiceApplicationsPolicy.md @@ -0,0 +1,196 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsvoiceapplicationspolicy +title: Grant-CsTeamsVoiceApplicationsPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsVoiceApplicationsPolicy + +## SYNOPSIS +Assigns a per-user Teams voice applications policy to one or more users. TeamsVoiceApplications policy governs what permissions the supervisors/users have over auto attendants and call queues. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsVoiceApplicationsPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsVoiceApplicationsPolicy [-PassThru] [[-PolicyName] <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsVoiceApplicationsPolicy [-PassThru] [[-PolicyName] <String>] + -Group <String> [-Rank <Int32>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +TeamsVoiceApplicationsPolicy is used for Supervisor Delegated Administration which allows tenant admins to permit certain users to make changes to auto attendant and call queue configurations. + +## EXAMPLES + +### EXAMPLE 1 +``` +Grant-CsTeamsVoiceApplicationsPolicy -Identity "Ken Myer" -PolicyName "SDA-Allow-All" +``` +The command shown in Example 1 assigns the per-user Teams voice applications policy SDA-Allow-All to the user with the display name "Ken Myer". + +### EXAMPLE 2 +``` +Grant-CsTeamsVoiceApplicationsPolicy -PolicyName "SDA-Allow-All" -Global +``` +Example 2 assigns the per-user online voice routing policy "SDA-Allow-All to all the users in the tenant, except any that have an explicit policy assignment. + +## PARAMETERS + +### -Identity +Indicates the Identity of the user account to be assigned the per-user Teams voice applications policy. User Identities can be specified using one of the following formats: the user's SIP address, the user's user principal name (UPN), or the user's Active Directory display name (for example, Ken Myer). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user account being assigned the Teams voice applications policy. By default, the Grant-CsTeamsVoiceApplicationsPolicy cmdlet does not pass objects through the pipeline. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +"Name" of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the "tag:" prefix). For example, a policy with the Identity tag:Redmond has a PolicyName equal to Redmond; likewise, a policy with the Identity tag:SDAAllowAllTeamsVoiceApplicationsPolicy has a PolicyName equal to SDAAllowAllTeamsVoiceApplicationsPolicy. + +To unassign a per-user policy previously assigned to a user, set the PolicyName to a null value ($Null). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +When you use this cmdlet without specifying a user identity, the policy applies to all users in your tenant, except any that have an explicit policy assignment. To skip a warning when you do this operation, specify this parameter. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvoiceapplicationspolicy) + +[Set-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvoiceapplicationspolicy) + +[Remove-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvoiceapplicationspolicy) + +[New-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvoiceapplicationspolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsWorkLoadPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsWorkLoadPolicy.md new file mode 100644 index 0000000000..b6dcf697af --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsWorkLoadPolicy.md @@ -0,0 +1,253 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsworkloadpolicy +title: Grant-CsTeamsWorkLoadPolicy +schema: 2.0.0 +--- + +# Grant-CsTeamsWorkLoadPolicy + +## SYNOPSIS + +This cmdlet applies an instance of the Teams Workload policy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) + +```powershell +Grant-CsTeamsWorkLoadPolicy [[-Identity] <String>] [-PassThru] [[-PolicyName] <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToTenant + +```powershell +Grant-CsTeamsWorkLoadPolicy [-PassThru] [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] + [-Global] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### GrantToGroup + +```powershell +Grant-CsTeamsWorkLoadPolicy [-PassThru] [[-PolicyName] <String>] [-MsftInternalProcessingMode <String>] + [-Group] <String> [-Rank <Int32>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The TeamsWorkLoadPolicy determines the workloads like meeting, messaging, calling that are enabled and/or pinned for the user. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Grant-CsTeamsWorkLoadPolicy -PolicyName Test -Identity testuser@test.onmicrosoft.com +``` + +Assigns a given policy to a user. + +### Example 2 + +```powershell +PS C:\> Grant-CsTeamsWorkLoadPolicy -Group f13d6c9d-ce76-422c-af78-b6018b4d9c80 -PolicyName Test +``` + +Assigns a given policy to a group. + +### Example 3 + +```powershell +PS C:\> Grant-CsTeamsWorkLoadPolicy -Global -PolicyName Test +``` + +Assigns a given policy to the tenant. + +### Example 4 + +```powershell +PS C:\> Grant-CsTeamsWorkLoadPolicy -Global -PolicyName Test +``` + +> [!NOTE] +> _Using `$null` in place of a policy name can be used to unassigned a policy instance._ + + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global + +This is the equivalent to `-Identity Global`. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group + +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Specifies the identity of the target user. + +Example: <testuser@test.onmicrosoft.com> + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Microsoft internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName + +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), for example, a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank + +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Remove-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworkloadpolicy) + +[Get-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworkloadpolicy) + +[Set-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworkloadpolicy) + +[New-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworkloadpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTeamsWorkLocationDetectionPolicy.md b/teams/teams-ps/teams/Grant-CsTeamsWorkLocationDetectionPolicy.md new file mode 100644 index 0000000000..35c5297361 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTeamsWorkLocationDetectionPolicy.md @@ -0,0 +1,194 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/grant-csteamsworklocationdetectionpolicy +title: Grant-CsTeamsWorkLocationDetectionPolicy +schema: 2.0.0 +ms.author: arkozlov +manager: prashibadkur +author: artemiykozlov +--- + +# Grant-CsTeamsWorkLocationDetectionPolicy + +## SYNOPSIS +This cmdlet applies an instance of the TeamsWorkLocationDetectionPolicy to users or groups in a tenant. + +## SYNTAX + +### Identity (Default) +``` +Grant-CsTeamsWorkLocationDetectionPolicy [<CommonParameters>] +``` + +### GrantToUser +``` +Grant-CsTeamsWorkLocationDetectionPolicy -Identity <String> [[-PolicyName] <String>] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTeamsWorkLocationDetectionPolicy [[-PolicyName] <String>] [-Group] <String> -Rank <Int32> + [<CommonParameters>] +``` + +### GrantToTenant +``` +Grant-CsTeamsWorkLocationDetectionPolicy [[-PolicyName] <String>] [-Global] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet applies an instance of the TeamsWorkLocationDetectionPolicy to users or groups in a tenant. + +Passes in the `Identity` of the policy instance in the `PolicyName` parameter and the user identifier in the `Identity` parameter or the group name in the `Group` parameter. One of either `Identity` or `Group` needs to be passed. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Grant-CsTeamsWorkLocationDetectionPolicy -PolicyName sms-policy -Identity testuser@test.onmicrosoft.com +``` + +Assigns a given policy to a user. + +### Example 2 +```powershell +PS C:\> Grant-CsTeamsWorkLocationDetectionPolicy -Group f13d6c9d-ce76-422c-af78-b6018b4d9c80 -PolicyName wld-policy +``` + +Assigns a given policy to a group. + +### Example 3 +```powershell +PS C:\> Grant-CsTeamsWorkLocationDetectionPolicy -Global -PolicyName wld-policy +``` + +Assigns a given policy to the tenant. + +### Example 3 +```powershell +PS C:\> Grant-CsTeamsWorkLocationDetectionPolicy -Global -PolicyName wld-policy +``` + +Note: _Using $null in place of a policy name can be used to unassigned a policy instance._ + +## PARAMETERS + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Global +This is the equivalent to `-Identity Global`. + +```yaml +Type: SwitchParameter +Parameter Sets: GrantToTenant +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +This is the identifier of the group that the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the identity of the target user. + +Example: testuser@test.onmicrosoft.com + +Example: 98403f08-577c-46dd-851a-f0460a13b03d + +Use the "Global" Identity if you wish to set the policy for the entire tenant. + +```yaml +Type: String +Parameter Sets: GrantToUser +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +Specifies the name of the policy to be assigned. The PolicyName is the policy identity minus the policy scope ("tag:"), for example, a policy that has an identity of "Tag:Enabled" has a PolicyName of "Enabled". + +```yaml +Type: String +Parameter Sets: GrantToUser, GrantToGroup, GrantToTenant +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: GrantToGroup +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworklocationdetectionpolicy) + +[New-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworklocationdetectionpolicy) + +[Set-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworklocationdetectionpolicy) + +[Remove-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworklocationdetectionpolicy) diff --git a/teams/teams-ps/teams/Grant-CsTenantDialPlan.md b/teams/teams-ps/teams/Grant-CsTenantDialPlan.md new file mode 100644 index 0000000000..9f4245e9a8 --- /dev/null +++ b/teams/teams-ps/teams/Grant-CsTenantDialPlan.md @@ -0,0 +1,185 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/grant-cstenantdialplan +applicable: Microsoft Teams +title: Grant-CsTenantDialPlan +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Grant-CsTenantDialPlan + +## SYNOPSIS +Use the Grant-CsTenantDialPlan cmdlet to assign an existing tenant dial plan to a user, to a group of users, or to set the Global policy instance. + +## SYNTAX + +### GrantToTenant (Default) +``` +Grant-CsTenantDialPlan [[-PolicyName] <string>] [-Global] [-PassThru] [<CommonParameters>] +``` + +### GrantToGroup +``` +Grant-CsTenantDialPlan [-Group] <string> [[-PolicyName] <string>] [-PassThru] [-Rank <int>] [<CommonParameters>] +``` + +### Identity +``` +Grant-CsTenantDialPlan [[-Identity] <string>] [[-PolicyName] <string>] [-PassThru] [<CommonParameters>] +``` + +## DESCRIPTION +The Grant-CsTenantDialPlan cmdlet assigns an existing tenant dial plan to a user, a group of users, or sets the Global policy instance. +Tenant dial plans provide information that is required for Enterprise Voice users to make telephone calls. +Users who do not have a valid tenant dial plan cannot make calls by using Enterprise Voice. +A tenant dial plan determines such things as how normalization rules are applied. + +You can check whether a user has been granted a per-user tenant dial plan by calling a command in this format: `Get-CsUserPolicyAssignment -Identity "<user name>" -PolicyType TenantDialPlan.` + +## EXAMPLES + +### Example 1 + +```powershell +Grant-CsTenantDialPlan -PolicyName Vt1tenantDialPlan9 -Identity Ken.Myer@contoso.com +``` + +This example grants the Vt1tenantDialPlan9 dial plan to Ken.Meyer@contoso.com. + +### Example 2 +```powershell +Grant-CsTenantDialPlan -Identity Ken.Myer@contoso.com -PolicyName $Null +``` + +In Example 2, any dial plan previously assigned to the user Ken Myer is unassigned from that user; as a result, Ken Myer will be managed by the global dial plan. +To unassign a custom tenant dial plan, set the PolicyName to a null value ($Null). + +### Example 3 + +```powershell +Grant-CsTenantDialPlan -Group sales@contoso.com -Rank 10 -PolicyName Vt1tenantDialPlan9 +``` + +This example grants the Vt1tenantDialPlan9 dial plan to members of the group sales@contoso.com. + +## PARAMETERS + +### -Global +Sets the parameters of the Global policy instance to the values in the specified policy instance. + +```yaml +Type: SwitchParameter +Parameter Sets: (GrantToTenant) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyName +The PolicyName parameter is the name of the tenant dial plan to be assigned. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Group +Specifies the group used for the group policy assignment. + +```yaml +Type: String +Parameter Sets: (GrantToGroup) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Rank +The rank of the policy assignment, relative to other group policy assignments for the same policy type. + +```yaml +Type: Int32 +Parameter Sets: (GrantToGroup) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter identifies the user to whom the policy should be assigned. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +The ExternalAccessPrefix and OptimizeDeviceDialing parameters have been removed from New-CsTenantDialPlan and Set-CsTenantDialPlan cmdlet since they are no longer used. External access dialing is now handled implicitly using normalization rules of the dial plans. +The Get-CsTenantDialPlan will still show the external access prefix in the form of a normalization rule of the dial plan. + +## RELATED LINKS + +[Set-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/set-cstenantdialplan) + +[New-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/new-cstenantdialplan) + +[Remove-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/remove-cstenantdialplan) + +[Get-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/get-cstenantdialplan) diff --git a/teams/teams-ps/teams/Grant-CsUserPolicyPackage.md b/teams/teams-ps/teams/Grant-CsUserPolicyPackage.md index b4221756a0..6d4fc120b3 100644 --- a/teams/teams-ps/teams/Grant-CsUserPolicyPackage.md +++ b/teams/teams-ps/teams/Grant-CsUserPolicyPackage.md @@ -1,13 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -applicable: Microsoft Teams title: Grant-CsUserPolicyPackage -author: etgottli -ms.author: etgottli -ms.reviewer: icchan +author: serdarsoysal +ms.author: serdars manager: amitar -online version: https://docs.microsoft.com/powershell/module/teams/grant-csuserpolicypackage +online version: https://learn.microsoft.com/powershell/module/teams/grant-csuserpolicypackage schema: 2.0.0 --- @@ -15,18 +13,18 @@ schema: 2.0.0 ## SYNOPSIS -This cmdlet supports applying a policy package to users in a tenant. Note that there is a limit of 20 users you can apply the package to at a time. +This cmdlet supports applying a policy package to users in a tenant. Note that there is a limit of 20 users you can apply the package to at a time. To apply a policy package to a larger number of users, consider using New-CsBatchPolicyPackageAssignmentOperation. ## SYNTAX ``` -Grant-CsUserPolicyPackage [-Identity] <String[]> [-PackageName] <String> [<CommonParameters>] +Grant-CsUserPolicyPackage [-Identity] <String[]> [-PackageName] <String> [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION This cmdlet supports applying a policy package to users in a tenant. Provide one or more user identities to assign the package with all the associated policies. The available policy packages and their definitions can be found by running Get-CsPolicyPackage. The recommended policy package for each user can be found by running Get-CsUserPolicyPackageRecommendation. -For more information on policy packages, please review https://docs.microsoft.com/en-us/MicrosoftTeams/manage-policy-packages +For more information on policy packages, please review https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages. ## EXAMPLES @@ -71,6 +69,37 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). @@ -82,8 +111,10 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Get-CsPolicyPackage](Get-CsPolicyPackage.md) +[Get-CsPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage) + +[Get-CsUserPolicyPackageRecommendation](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackagerecommendation) -[Get-CsUserPolicyPackageRecommendation](Get-CsUserPolicyPackageRecommendation.md) +[Get-CsUserPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackage) -[Get-CsUserPolicyPackage](Get-CsUserPolicyPackage.md) +[New-CsBatchPolicyPackageAssignmentOperation](https://learn.microsoft.com/powershell/module/teams/new-csbatchpolicypackageassignmentoperation) diff --git a/skype/skype-ps/skype/Import-CsAutoAttendantHolidays.md b/teams/teams-ps/teams/Import-CsAutoAttendantHolidays.md similarity index 77% rename from skype/skype-ps/skype/Import-CsAutoAttendantHolidays.md rename to teams/teams-ps/teams/Import-CsAutoAttendantHolidays.md index d672106650..aee3150e6e 100644 --- a/skype/skype-ps/skype/Import-CsAutoAttendantHolidays.md +++ b/teams/teams-ps/teams/Import-CsAutoAttendantHolidays.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/import-csautoattendantholidays -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/import-csautoattendantholidays +applicable: Microsoft Teams title: Import-CsAutoAttendantHolidays schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Import-CsAutoAttendantHolidays @@ -26,15 +26,18 @@ The Export-CsAutoAttendantHolidays cmdlet and the Import-CsAutoAttendantHolidays The Export-CsAutoAttendantHolidays cmdlet returns the holiday schedule information in serialized form (as a byte array). The caller can then write the bytes to the disk to obtain a CSV file. Similarly, the Import-CsAutoAttendantHolidays cmdlet accepts the holiday schedule information as a byte array, which can be read from the aforementioned CSV file. The first line of the CSV file is considered a header record and is always ignored. -**NOTE** -- Each line in the CSV file used by Export-CsAutoAttendantHolidays and Import-CsAutoAttendantHolidays cmdlet should be of the following format: +**NOTES**: + +Each line in the CSV file used by Export-CsAutoAttendantHolidays and Import-CsAutoAttendantHolidays cmdlet should be of the following format: `HolidayName,StartDateTime1,EndDateTime1,StartDateTime2,EndDateTime2,...,StartDateTime10,EndDateTime10` - where - - HolidayName is the name of the holiday to be imported. - - StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet. - - EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date. +where + +- HolidayName is the name of the holiday to be imported. +- StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet. +- EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date. + - The first line of the CSV file is considered a header record and is always ignored by Import-CsAutoAttendantHolidays cmdlet. - If the destination auto attendant for the import already contains a call flow or schedule by the same name as one of the holidays being imported, the corresponding CSV record is skipped. - For holidays that are successfully imported, a default call flow is created which is configured without any greeting and simply disconnects the call on being executed. @@ -66,7 +69,7 @@ The identity for the AA whose holiday schedules are to be imported. Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: 0 @@ -82,7 +85,7 @@ The Input parameter specifies the holiday schedule information that is to be imp Type: System.Byte[] Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -97,7 +100,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -107,26 +110,21 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). - +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/?LinkID=113216). ## INPUTS ### System.String The Import-CsAutoAttendantHolidays cmdlet accepts a string as the Identity parameter. - ## OUTPUTS ### Microsoft.Rtc.Management.Hosted.OAA.Models.HolidayImportResult - ## NOTES - ## RELATED LINKS -[Export-CsAutoAttendantHolidays](Export-CsAutoAttendantHolidays.md) - -[Get-CsAutoAttendantHolidays](Get-CsAutoAttendantHolidays.md) +[Export-CsAutoAttendantHolidays](https://learn.microsoft.com/powershell/module/teams/export-csautoattendantholidays) +[Get-CsAutoAttendantHolidays](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantholidays) diff --git a/teams/teams-ps/teams/Import-CsOnlineAudioFile.md b/teams/teams-ps/teams/Import-CsOnlineAudioFile.md new file mode 100644 index 0000000000..08de362834 --- /dev/null +++ b/teams/teams-ps/teams/Import-CsOnlineAudioFile.md @@ -0,0 +1,133 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile +applicable: Microsoft Teams +title: Import-CsOnlineAudioFile +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Import-CsOnlineAudioFile + +## SYNOPSIS +Use the Import-CsOnlineAudioFile cmdlet to upload a new audio file. + +## SYNTAX + +```powershell +Import-CsOnlineAudioFile -ApplicationId <String> -FileName <string> -Content <Byte[]> [<CommonParameters>] +``` + +## DESCRIPTION +The Import-CsOnlineAudioFile cmdlet uploads a new audio file for use with the Auto Attendant (AA), Call Queue (CQ) service or Music on Hold for Microsoft Teams. + +## EXAMPLES + +### Example 1 +```powershell +$content = [System.IO.File]::ReadAllBytes('C:\Media\Hello.wav') +$audioFile = Import-CsOnlineAudioFile -ApplicationId "OrgAutoAttendant" -FileName "Hello.wav" -Content $content +``` + +This example creates a new audio file using the WAV content that has a filename of Hello.wav to be used with organizational auto attendants. The stored variable, $audioFile, will be used when running other cmdlets to update the audio file for Auto Attendant, for example [New-CsAutoAttendantPrompt](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantprompt). + +### Example 2 +```powershell +$content = [System.IO.File]::ReadAllBytes('C:\Media\MOH.wav') +$audioFile = Import-CsOnlineAudioFile -ApplicationId "HuntGroup" -FileName "MOH.wav" -Content $content +``` + +This example creates a new audio file using the WAV content that has a filename of MOH.wav to be used as a Music On Hold file with a Call Queue. The stored variable, $audioFile, will be used with [Set-CsCallQueue](https://learn.microsoft.com/powershell/module/teams/set-cscallqueue) to provide the audio file id. + +### Example 3 +```powershell +$content = [System.IO.File]::ReadAllBytes('C:\Media\MOH.wav') +$audioFile = Import-CsOnlineAudioFile -ApplicationId TenantGlobal -FileName "MOH.wav" -Content $content +``` + +This example creates a new audio file using the WAV content that has a filename of MOH.wav to be used as Music On Hold for Microsoft Teams. The stored variable, $audioFile, will be used with [New-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallholdpolicy) to provide the audio file id. + +## PARAMETERS + +### -ApplicationId +The ApplicationId parameter is the identifier for the application which will use this audio file. For example, if the audio file will be used with an Auto Attendant, then it needs to be set to "OrgAutoAttendant". If the audio file will be used with a Call Queue, then it needs to be set to "HuntGroup". If the audio file will be used with Microsoft Teams, then it needs to be set to "TenantGlobal". + +Supported values: + +- OrgAutoAttendant +- HuntGroup +- TenantGlobal + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileName +The FileName parameter is the name of the audio file. For example, the file name for the file C:\Media\Welcome.wav is Welcome.wav. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Content +The Content parameter represents the content of the audio file. Supported formats are WAV (uncompressed, linear PCM with 8/16/32-bit depth in mono or stereo), WMA (mono only), and MP3. The audio file content cannot be more 5MB. + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.AudioFile + +## NOTES + +When you import an audio file to be used for Auto Attendant or Call Queue, the audio file will automatically be marked for deletion (as seen by running +Get-CsOnlineAudioFile) and it will be deleted after 48 to 72 hours from the time of import, unless the audio file is associated to an +Auto Attendant and Call Queue before 48 hours after it was imported. + +You are responsible for independently clearing and securing all necessary rights and permissions to use any music or audio file with your Microsoft Teams service, which may include intellectual property and other rights in any music, sound effects, audio, brands, names, and other content in the audio file from all relevant rights holders, which may include artists, actors, performers, musicians, songwriters, composers, record labels, music publishers, unions, guilds, rights societies, collective management organizations and any other parties who own, control or license the music copyrights, sound effects, audio and other intellectual property rights. + +## RELATED LINKS +[Export-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/export-csonlineaudiofile) + +[Get-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/get-csonlineaudiofile) + +[Remove-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/remove-csonlineaudiofile) diff --git a/teams/teams-ps/teams/New-CsApplicationAccessPolicy.md b/teams/teams-ps/teams/New-CsApplicationAccessPolicy.md new file mode 100644 index 0000000000..1f6d71a39b --- /dev/null +++ b/teams/teams-ps/teams/New-CsApplicationAccessPolicy.md @@ -0,0 +1,114 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy +applicable: Microsoft Teams +title: New-CsApplicationAccessPolicy +schema: 2.0.0 +manager: zhengni +author: frankpeng7 +ms.author: frpeng +ms.reviewer: +--- + +# New-CsApplicationAccessPolicy + +## SYNOPSIS + +Creates a new application access policy. Application access policy contains a list of application (client) IDs. When granted to a user, those applications will be authorized to access online meetings on behalf of that user. + +## SYNTAX + +### Identity + +``` +New-CsApplicationAccessPolicy [-Identity <XdsIdentity>] [-AppIds <PSListModifier>] [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet creates a new application access policy. Application access policy contains a list of application (client) IDs. When granted to a user, those applications will be authorized to access online meetings on behalf of that user. + +## EXAMPLES + +### Create a new application access policy with one app ID + +``` +PS C:\> New-CsApplicationAccessPolicy -Identity "ASimplePolicy" -AppIds "d39597bf-8407-40ca-92ef-1ec26b885b7b" -Description "Some description" +``` + +The command shown above shows how to create a new policy with one app IDs configured. + +### Create a new application access policy with multiple app IDs + +``` +PS C:\> New-CsApplicationAccessPolicy -Identity "ASimplePolicy" -AppIds "d39597bf-8407-40ca-92ef-1ec26b885b71", "57caaef9-5ed0-48d5-8862-e5abfa71b3e1", "dc17674c-81d9-4adb-bfb2-8f6a442e4620" -Description "Some description" +``` + +The command shown above shows how to create a new policy with a list of (three) app IDs configured. + +## PARAMETERS + +### -Identity + +Unique identifier assigned to the policy when it was created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppIds + +A list of application (client) IDs. For details of application (client) ID, refer to: [Get tenant and app ID values for signing in](https://learn.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#get-tenant-and-app-id-values-for-signing-in). + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Specifies the description of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Grant-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csapplicationaccesspolicy) +[Get-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csapplicationaccesspolicy) +[Set-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csapplicationaccesspolicy) +[Remove-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csapplicationaccesspolicy) diff --git a/skype/skype-ps/skype/New-CsAutoAttendant.md b/teams/teams-ps/teams/New-CsAutoAttendant.md similarity index 77% rename from skype/skype-ps/skype/New-CsAutoAttendant.md rename to teams/teams-ps/teams/New-CsAutoAttendant.md index ceb36363b7..98e32e7234 100644 --- a/skype/skype-ps/skype/New-CsAutoAttendant.md +++ b/teams/teams-ps/teams/New-CsAutoAttendant.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendant -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendant +applicable: Microsoft Teams title: New-CsAutoAttendant schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsAutoAttendant @@ -18,7 +18,7 @@ Use the New-CsAutoAttendant cmdlet to create a new Auto Attendant (AA). ## SYNTAX ```powershell -New-CsAutoAttendant -Name <String> -LanguageId <String> -TimeZoneId <String> -DefaultCallFlow <Object> [-CallFlows <Object>] [-CallHandlingAssociations <Object>] [-Operator <Object>] [-VoiceId <String>] [-EnableVoiceResponse] [-InclusionScope <Object>] [-ExclusionScope <Object>] [-Tenant <Guid>] [<CommonParameters>] +New-CsAutoAttendant -Name <String> -LanguageId <String> -TimeZoneId <String> -DefaultCallFlow <Object> [-CallFlows <Object>] [-CallHandlingAssociations <Object>] [-Operator <Object>] [-VoiceId <String>] [-EnableVoiceResponse] [-InclusionScope <Object>] [-ExclusionScope <Object>] [-AuthorizedUsers <List>] [-HideAuthorizedUsers <List>] [-UserNameExtension <String>] [-Tenant <Guid>] [<CommonParameters>] ``` ## DESCRIPTION @@ -27,7 +27,14 @@ Each AA can be associated with phone numbers that allow callers to reach specifi You can create new AAs by using the New-CsAutoAttendant cmdlet; each newly created AA gets assigned a random string that serves as the identity of the AA. -**NOTE** +> [!CAUTION] +> The following configuration parameters are currently only available in PowerShell and do not appear in Teams admin center. Saving a call queue configuration through Teams admin center will _remove_ any of these configured items: +> +> - -HideAuthorizedUsers +> - -UserNameExtension + +**NOTES**: + - To setup your AA for calling, you need to create an application instance first using `New-CsOnlineApplicationInstance` cmdlet , then associate it with your AA configuration using `New-CsOnlineApplicationInstanceAssociation` cmdlet. - The default call flow has the lowest precedence, and any custom call flow has a higher precedence and is executed if the schedule associated with it is in effect. - Holiday call flows have higher priority than after-hours call flows. Thus, if a holiday schedule and an after-hours schedule are both in effect at a particular time, the call flow corresponding to the holiday call flow will be rendered. @@ -38,7 +45,7 @@ You can create new AAs by using the New-CsAutoAttendant cmdlet; each newly creat ### -------------------------- Example 1 -------------------------- ```powershell -$operatorObjectId = (Get-CsOnlineUser operator@contoso.com).ObjectId +$operatorObjectId = (Get-CsOnlineUser operator@contoso.com).Identity $operatorEntity = New-CsAutoAttendantCallableEntity -Identity $operatorObjectId -Type User $greetingPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" @@ -61,7 +68,7 @@ $afterHoursCallHandlingAssociation = New-CsAutoAttendantCallHandlingAssociation $inclusionScopeGroupIds = @("4c3053a6-20bf-43df-bf7a-156124168856") $inclusionScope = New-CsAutoAttendantDialScope -GroupScope -GroupIds $inclusionScopeGroupIds -$aa = New-CsAutoAttendant -Name "Main auto attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation) -Language "en-US" -TimeZoneId "UTC" -Operator $operatorEntity -InclusionScope $inclusionScope +$aa = New-CsAutoAttendant -Name "Main auto attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation) -LanguageId "en-US" -TimeZoneId "UTC" -Operator $operatorEntity -InclusionScope $inclusionScope ``` This example creates a new AA named _Main auto attendant_ that has the following properties: @@ -75,7 +82,7 @@ This example creates a new AA named _Main auto attendant_ that has the following ### -------------------------- Example 2 -------------------------- ```powershell -$operatorObjectId = (Get-CsOnlineUser operator@contoso.com).ObjectId +$operatorObjectId = (Get-CsOnlineUser operator@contoso.com).Identity $operatorEntity = New-CsAutoAttendantCallableEntity -Identity $operatorObjectId -Type User $dcfGreetingPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" @@ -105,7 +112,7 @@ $christmasSchedule = New-CsOnlineSchedule -Name "Christmas" -FixedSchedule -Date $christmasCallHandlingAssociation = New-CsAutoAttendantCallHandlingAssociation -Type Holiday -ScheduleId $christmasSchedule.Id -CallFlowId $christmasCallFlow.Id -$aa = New-CsAutoAttendant -Name "Main auto attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow, $christmasCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation, $christmasCallHandlingAssociation) -Language "en-US" -TimeZoneId "UTC" -Operator $operatorEntity +$aa = New-CsAutoAttendant -Name "Main auto attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow, $christmasCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation, $christmasCallHandlingAssociation) -LanguageId "en-US" -TimeZoneId "UTC" -Operator $operatorEntity ``` This example creates a new AA named _Main auto attendant_ that has the following properties: @@ -126,7 +133,7 @@ $christmasSchedule = New-CsOnlineSchedule -Name "Christmas" -FixedSchedule -Date # Create First Auto Attendant $dcfGreetingPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso Customer Support!" $dcfMenuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$dcfMenu=New-CsAutoAttendantMenu -Name "Default menu" -Prompts @($dcfMenuPrompt) -EnableDialByName +$dcfMenu = New-CsAutoAttendantMenu -Name "Default menu" -Prompts @($dcfMenuPrompt) -EnableDialByName -DirectorySearchMethod ByName $defaultCallFlow = New-CsAutoAttendantCallFlow -Name "Default call flow" -Greetings @($dcfGreetingPrompt) -Menu $dcfMenu $christmasGreetingPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Our offices are closed for Christmas from December 24 to December 26. Please call back later." @@ -136,7 +143,7 @@ $christmasCallFlow = New-CsAutoAttendantCallFlow -Name "Christmas" -Greetings @( $christmasCallHandlingAssociation = New-CsAutoAttendantCallHandlingAssociation -Type Holiday -ScheduleId $christmasSchedule.Id -CallFlowId $christmasCallFlow.Id -New-CsAutoAttendant -Name "Customer Support Auto Attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow, $christmasCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation, $christmasCallHandlingAssociation) -Language "en-US" -TimeZoneId "UTC" +New-CsAutoAttendant -Name "Customer Support Auto Attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow, $christmasCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation, $christmasCallHandlingAssociation) -LanguageId "en-US" -TimeZoneId "UTC" # Id : a65b3434-05a1-48ed-883d-e3ca35a60af8 # TenantId : f6b89083-a2f8-55cc-9f62-33b73af44164 @@ -158,7 +165,7 @@ New-CsAutoAttendant -Name "Customer Support Auto Attendant" -DefaultCallFlow $de # Create Second Auto Attendant $dcfGreetingPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso Store!" $dcfMenuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." -$dcfMenu=New-CsAutoAttendantMenu -Name "Default menu" -Prompts @($dcfMenuPrompt) -EnableDialByName +$dcfMenu = New-CsAutoAttendantMenu -Name "Default menu" -Prompts @($dcfMenuPrompt) -EnableDialByName -DirectorySearchMethod ByName $defaultCallFlow = New-CsAutoAttendantCallFlow -Name "Default call flow" -Greetings @($dcfGreetingPrompt) -Menu $dcfMenu $christmasGreetingPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Our offices are closed for Christmas from December 24 to December 26. Please call back later." @@ -168,7 +175,7 @@ $christmasCallFlow = New-CsAutoAttendantCallFlow -Name "Christmas" -Greetings @( $christmasCallHandlingAssociation = New-CsAutoAttendantCallHandlingAssociation -Type Holiday -ScheduleId $christmasSchedule.Id -CallFlowId $christmasCallFlow.Id -New-CsAutoAttendant -Name "Main auto attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow, $christmasCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation, $christmasCallHandlingAssociation) -Language "en-US" -TimeZoneId "UTC" +New-CsAutoAttendant -Name "Main auto attendant" -DefaultCallFlow $defaultCallFlow -EnableVoiceResponse -CallFlows @($afterHoursCallFlow, $christmasCallFlow) -CallHandlingAssociations @($afterHoursCallHandlingAssociation, $christmasCallHandlingAssociation) -LanguageId "en-US" -TimeZoneId "UTC" # Id : 236450c4-9f1e-4c19-80eb-d68819d36a15 # TenantId : f6b89083-a2f8-55cc-9f62-33b73af44164 @@ -187,7 +194,6 @@ New-CsAutoAttendant -Name "Main auto attendant" -DefaultCallFlow $defaultCallFlo # DirectoryLookupScope : # ApplicationInstances : - # Show the auto attendants associated with this holiday schedule: Get-CsOnlineSchedule $christmasSchedule.Id @@ -203,7 +209,7 @@ This example creates two new AAs named _Main auto attendant_ and _Customer Suppo We can see when we ran the Get-CsOnlineSchedule cmdlet at the end, to get the _Christmas Holiday_ schedule information, that the configuration IDs for the newly created AAs have been added to the `AssociatedConfigurationIds` properties of that schedule. This means any updates made to this schedule would reflect in both associated AAs. -Removing an association between an AA and a schedule is as simple as deleting the CallHandlingAssociation of that schedule in the AA you want to modify. Please refer to [Set-CsAutoAttendant](Set-CsAutoAttendant.md) cmdlet documentation for examples on how to do that. +Removing an association between an AA and a schedule is as simple as deleting the CallHandlingAssociation of that schedule in the AA you want to modify. Please refer to [Set-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/set-csautoattendant) cmdlet documentation for examples on how to do that. ### -------------------------- Example 4 -------------------------- ```powershell @@ -213,9 +219,9 @@ $greetingText = "Welcome to Contoso" $mainMenuText = "To reach your party by name, say it now. To talk to Sales, please press 1. To talk to User2 press 2. Please press 0 for operator" $afterHoursText = "Sorry Contoso is closed. Please call back during week days from 7AM to 8PM. Goodbye!" $tz = "Romance Standard Time" -$operatorId = (Get-CsOnlineUser -Identity "sip:user1@contoso.com").ObjectId -$user1Id = (Get-CsOnlineUser -Identity "sip:user2@contoso.com").ObjectId -$salesCQappinstance = (Get-CsOnlineUser -Identity "sales@contoso.com").ObjectId # one of the application instances associated to the Call Queue +$operatorId = (Get-CsOnlineUser -Identity "sip:user1@contoso.com").Identity +$user1Id = (Get-CsOnlineUser -Identity "sip:user2@contoso.com").Identity +$salesCQappinstance = (Get-CsOnlineUser -Identity "sales@contoso.com").Identity # one of the application instances associated to the Call Queue $tr1 = New-CsOnlineTimeRange -Start 07:00 -End 20:00 # After hours @@ -241,7 +247,7 @@ $menu = New-CsAutoAttendantMenu -Name "AA menu2" -Prompts @($menuPrompt) -Enable $callFlow = New-CsAutoAttendantCallFlow -Name "Default" -Menu $menu -Greetings $greetingPrompt # Auto attendant -New-CsAutoAttendant -Name $aaName -Language $language -CallFlows @($afterHoursCallFlow) -TimeZoneId $tz -Operator $operator -DefaultCallFlow $callFlow -CallHandlingAssociations @($afterHoursCallHandlingAssociation) -EnableVoiceResponse +New-CsAutoAttendant -Name $aaName -LanguageId $language -CallFlows @($afterHoursCallFlow) -TimeZoneId $tz -Operator $operator -DefaultCallFlow $callFlow -CallHandlingAssociations @($afterHoursCallHandlingAssociation) -EnableVoiceResponse ``` This example creates a new AA named _Main auto attendant_ that has the following properties: @@ -265,7 +271,7 @@ The Name parameter is a friendly name that is assigned to the AA. Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -277,13 +283,13 @@ Accept wildcard characters: False ### -LanguageId The LanguageId parameter is the language that is used to read text-to-speech (TTS) prompts. -You can query the supported languages using the [`Get-CsAutoAttendantSupportedLanguage`](Get-CsAutoAttendantSupportedLanguage.md) cmdlet. +You can query the supported languages using the [`Get-CsAutoAttendantSupportedLanguage`](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantsupportedlanguage) cmdlet. ```yaml Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -295,13 +301,13 @@ Accept wildcard characters: False ### -TimeZoneId The TimeZoneId parameter represents the AA time zone. All schedules are evaluated based on this time zone. -You can query the supported timezones using the [`Get-CsAutoAttendantSupportedTimeZone`](Get-CsAutoAttendantSupportedTimeZone.md) cmdlet. +You can query the supported timezones using the [`Get-CsAutoAttendantSupportedTimeZone`](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantsupportedtimezone) cmdlet. ```yaml Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -313,14 +319,13 @@ Accept wildcard characters: False ### -DefaultCallFlow The DefaultCallFlow parameter is the flow to be executed when no other call flow is in effect (for example, during business hours). -You can create the DefaultCallFlow by using the [`New-CsAutoAttendantCallFlow`](New-CsAutoAttendantCallFlow.md) cmdlet. - +You can create the DefaultCallFlow by using the [`New-CsAutoAttendantCallFlow`](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow) cmdlet. ```yaml Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -332,14 +337,13 @@ Accept wildcard characters: False ### -CallFlows The CallFlows parameter represents call flows, which are required if they are referenced in the CallHandlingAssociations parameter. -You can create CallFlows by using the [`New-CsAutoAttendantCallFlow`](New-CsAutoAttendantCallFlow.md) cmdlet. - +You can create CallFlows by using the [`New-CsAutoAttendantCallFlow`](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow) cmdlet. ```yaml Type: System.Collections.Generic.List Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -358,7 +362,7 @@ You can create CallHandlingAssociations by using the `New-CsAutoAttendantCallHan Type: System.Collections.Generic.List Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -372,12 +376,11 @@ The Operator parameter represents the SIP address or PSTN number of the operator You can create callable entities by using the `New-CsAutoAttendantCallableEntity` cmdlet. - ```yaml Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -392,15 +395,15 @@ The VoiceId parameter represents the voice that is used to read text-to-speech ( You can query the supported voices by using the `Get-CsAutoAttendantSupportedLanguage` cmdlet. You can determine the default voice for a language by issuing the following command: ``` -$language = Get-CsAutoAttendantSupportedLanguage -Identity "en-US"` -$defaultVoice = $language.Voices[0].Gender +$language = Get-CsAutoAttendantSupportedLanguage -Identity "en-US" +$defaultVoice = $language.Voices[0].Id ``` ```yaml Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -416,7 +419,7 @@ The EnableVoiceResponse parameter indicates whether voice response for AA is ena Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -429,14 +432,13 @@ Accept wildcard characters: False Specifies the users to which call transfers are allowed through directory lookup feature. If not specified, all users in the organization can be reached through directory lookup. -Dial scopes can be created by using the [`New-CsAutoAttendantDialScope`](New-CsAutoAttendantDialScope.md) cmdlet. - +Dial scopes can be created by using the [`New-CsAutoAttendantDialScope`](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantdialscope) cmdlet. ```yaml Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -449,14 +451,13 @@ Accept wildcard characters: False Specifies the users to which call transfers are not allowed through directory lookup feature. If not specified, no user in the organization is excluded from directory lookup. -Dial scopes can be created by using the [`New-CsAutoAttendantDialScope`](New-CsAutoAttendantDialScope.md) cmdlet. - +Dial scopes can be created by using the [`New-CsAutoAttendantDialScope`](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantdialscope) cmdlet. ```yaml Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -465,13 +466,69 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AuthorizedUsers +This is a list of GUIDs for users who are authorized to make changes to this call queue. The users must also have a TeamsVoiceApplications policy assigned. The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HideAuthorizedUsers +_Saving an auto attendant configuration through Teams admin center will *remove* this setting._ + +The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserNameExtension +_Saving an auto attendant configuration through Teams admin center will *remove* this setting._ + +The UserNameExtension parameter is a string that specifies how to extend usernames in dial search by appending additional information after the name. +This parameter is used in dial search when multiple search results are found, as it helps to distinguish users with similar names. Possible values are: + +- None: Default value, which means the username is pronounced as is. +- Office: Adds office information from the user profile. +- Department: Adds department information from the user profile. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: false +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Tenant ```yaml Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -481,43 +538,40 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### Microsoft.Rtc.Management.OAA.Models.AutoAttendant - ## NOTES - ## RELATED LINKS -[New-CsOnlineApplicationInstanceAssociation](New-CsOnlineApplicationInstanceAssociation.md) +[New-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstanceassociation) -[Get-CsAutoAttendant](Get-CsAutoAttendant.md) +[Get-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/get-csautoattendant) -[Get-CsAutoAttendantStatus](Get-CsAutoAttendantStatus.md) +[Get-CsAutoAttendantStatus](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantstatus) -[Get-CsAutoAttendantSupportedLanguage](Get-CsAutoAttendantSupportedLanguage.md) +[Get-CsAutoAttendantSupportedLanguage](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantsupportedlanguage) -[Get-CsAutoAttendantSupportedTimeZone](Get-CsAutoAttendantSupportedTimeZone.md) +[Get-CsAutoAttendantSupportedTimeZone](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantsupportedtimezone) -[New-CsAutoAttendantCallableEntity](New-CsAutoAttendantCallableEntity.md) +[New-CsAutoAttendantCallableEntity](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallableentity) -[New-CsAutoAttendantCallFlow](New-CsAutoAttendantCallFlow.md) +[New-CsAutoAttendantCallFlow](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow) -[New-CsAutoAttendantCallHandlingAssociation](New-CsAutoAttendantCallHandlingAssociation.md) +[New-CsAutoAttendantCallHandlingAssociation](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallhandlingassociation) -[New-CsOnlineSchedule](New-CsOnlineSchedule.md) +[New-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/new-csonlineschedule) -[Remove-CsAutoAttendant](Remove-CsAutoAttendant.md) +[Remove-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/remove-csautoattendant) -[Set-CsAutoAttendant](Set-CsAutoAttendant.md) +[Set-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/set-csautoattendant) -[Update-CsAutoAttendant](Update-CsAutoAttendant.md) +[Update-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/update-csautoattendant) diff --git a/teams/teams-ps/teams/New-CsAutoAttendantCallFlow.md b/teams/teams-ps/teams/New-CsAutoAttendantCallFlow.md new file mode 100644 index 0000000000..e5d964c2c4 --- /dev/null +++ b/teams/teams-ps/teams/New-CsAutoAttendantCallFlow.md @@ -0,0 +1,151 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow +applicable: Microsoft Teams +title: New-CsAutoAttendantCallFlow +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsAutoAttendantCallFlow + +## SYNOPSIS +Use the New-CsAutoAttendantCallFlow cmdlet to create a new call flow. + +## SYNTAX + +```powershell +New-CsAutoAttendantCallFlow -Name <String> -Menu <Object> [-Greetings <List>] [-Tenant <Guid>] [-ForceListenMenuEnabled] [<CommonParameters>] +``` + +## DESCRIPTION +The New-CsAutoAttendantCallFlow cmdlet creates a new call flow for use with the Auto Attendant (AA) service. The AA service uses the call flow to handle inbound calls by playing a greeting (if present), and provide callers with actions through a menu. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +$menuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." +$menu = New-CsAutoAttendantMenu -Name "Default Menu" -Prompts @($menuPrompt) -EnableDialByName +$callFlow = New-CsAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu +``` + +This example creates a new call flow that renders the "Default Menu" menu. + +### -------------------------- Example 2 -------------------------- +```powershell +$menuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." +$menu = New-CsAutoAttendantMenu -Name "Default Menu" -Prompts $menuPrompt -EnableDialByName +$greeting = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" +$callFlow = New-CsAutoAttendantCallFlow -Name "Default Call Flow" -Menu $menu -Greetings $greeting -ForceListenMenuEnabled +``` + +This example creates a new call flow that plays a greeting before rendering the "Default Menu" menu with Force listen menu enabled. + +## PARAMETERS + +### -Name +The Name parameter represents a unique friendly name for the call flow. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Menu +The Menu parameter identifies the menu to render when the call flow is executed. + +You can create a new menu by using the [`New-CsAutoAttendantMenu`](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantmenu) cmdlet. + +```yaml +Type: System.Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Greetings +If present, the prompts specified by the Greetings parameter (either TTS or Audio) are played before the call flow's menu is rendered. + +You can create prompts by using the [`New-CsAutoAttendantPrompt`](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantprompt) cmdlet. + +```yaml +Type: System.Collections.Generic.List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceListenMenuEnabled + +If specified, DTMF and speech inputs will not be processed while the greeting or menu prompt is playing. It will enforce callers to listen to all menu options before making a selection. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.OAA.Models.CallFlow + +## NOTES + +## RELATED LINKS + +[New-CsAutoAttendantMenu](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantmenu) + +[New-CsAutoAttendantPrompt](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantprompt) diff --git a/skype/skype-ps/skype/New-CsAutoAttendantCallHandlingAssociation.md b/teams/teams-ps/teams/New-CsAutoAttendantCallHandlingAssociation.md similarity index 79% rename from skype/skype-ps/skype/New-CsAutoAttendantCallHandlingAssociation.md rename to teams/teams-ps/teams/New-CsAutoAttendantCallHandlingAssociation.md index 6b370c4174..0dd8a74ae2 100644 --- a/skype/skype-ps/skype/New-CsAutoAttendantCallHandlingAssociation.md +++ b/teams/teams-ps/teams/New-CsAutoAttendantCallHandlingAssociation.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendantcallhandlingassociation -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallhandlingassociation +applicable: Microsoft Teams title: New-CsAutoAttendantCallHandlingAssociation schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsAutoAttendantCallHandlingAssociation @@ -29,7 +29,7 @@ The `New-CsAutoAttendantCallHandlingAssociation` cmdlet creates a new call handl ### -------------------------- Example 1 -------------------------- ```powershell $tr = New-CsOnlineTimeRange -Start 09:00 -End 17:00 -$schedule = New-CsOnlineSchedule -Name "Business Hours" -WeeklyRecurrentSchedule -MondayHours @($tr) -TuesdayHours @($tr) -WednesdayHours @($tr) -ThursdayHours @($tr) -FridayHours @($tr) +$schedule = New-CsOnlineSchedule -Name "Business Hours" -WeeklyRecurrentSchedule -MondayHours @($tr) -TuesdayHours @($tr) -WednesdayHours @($tr) -ThursdayHours @($tr) -FridayHours @($tr) -Complement $scheduleId = $schedule.Id $menuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." @@ -49,7 +49,7 @@ This example creates the following: ### -------------------------- Example 2 -------------------------- ```powershell $tr = New-CsOnlineTimeRange -Start 09:00 -End 17:00 -$schedule = New-CsOnlineSchedule -Name "Business Hours" -WeeklyRecurrentSchedule -MondayHours @($tr) -TuesdayHours @($tr) -WednesdayHours @($tr) -ThursdayHours @($tr) -FridayHours @($tr) +$schedule = New-CsOnlineSchedule -Name "Business Hours" -WeeklyRecurrentSchedule -MondayHours @($tr) -TuesdayHours @($tr) -WednesdayHours @($tr) -ThursdayHours @($tr) -FridayHours @($tr) -Complement $scheduleId = $schedule.Id $menuPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "To reach your party by name, enter it now, followed by the pound sign." @@ -92,14 +92,13 @@ This example creates the following: ### -CallFlowId The CallFlowId parameter represents the call flow to be associated with the schedule. -You can create a call flow by using the [`New-CsAutoAttendantCallFlow`](New-CsAutoAttendantCallFlow.md) cmdlet. - +You can create a call flow by using the [`New-CsAutoAttendantCallFlow`](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow) cmdlet. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -111,14 +110,13 @@ Accept wildcard characters: False ### -ScheduleId The ScheduleId parameter represents the schedule to be associated with the call flow. -You can create a schedule by using the [`New-CsOnlineSchedule`](New-CsOnlineSchedule.md) cmdlet. Additionally, you can use [`Get-CsOnlineSchedule`](Get-CsOnlineSchedule.md) cmdlet to get the schedules configured for your organization. - +You can create a schedule by using the [New-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/new-csonlineschedule) cmdlet. additionally, you can use [Get-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/get-csonlineschedule) cmdlet to get the schedules configured for your organization. ```yaml Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -133,12 +131,11 @@ The Type parameter represents the type of the call handling association. Current - `AfterHours` - `Holiday` - ```yaml Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -154,7 +151,7 @@ The Disable parameter, if set, establishes that the call handling association is Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -178,7 +175,7 @@ If you are using a remote session of Windows PowerShell and are connected only t Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -188,24 +185,22 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### Microsoft.Rtc.Management.OAA.Models.CallHandlingAssociation - ## NOTES ## RELATED LINKS -[New-CsAutoAttendantCallFlow](New-CsAutoAttendantCallFlow.md) +[New-CsAutoAttendantCallFlow](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow) -[New-CsOnlineSchedule](New-CsOnlineSchedule.md) +[New-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/new-csonlineschedule) -[`Get-CsOnlineSchedule`](Get-CsOnlineSchedule.md) +[Get-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/get-csonlineschedule) diff --git a/teams/teams-ps/teams/New-CsAutoAttendantCallableEntity.md b/teams/teams-ps/teams/New-CsAutoAttendantCallableEntity.md new file mode 100644 index 0000000000..b496fcaaad --- /dev/null +++ b/teams/teams-ps/teams/New-CsAutoAttendantCallableEntity.md @@ -0,0 +1,214 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallableentity +applicable: Microsoft Teams +title: New-CsAutoAttendantCallableEntity +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsAutoAttendantCallableEntity + +## SYNOPSIS +The New-CsAutoAttendantCallableEntity cmdlet lets you create a callable entity. + +## SYNTAX + +```powershell +New-CsAutoAttendantCallableEntity -Identity <String> -Type <User | ApplicationEndpoint | ConfigurationEndpoint | ExternalPstn | SharedVoicemail> [-Tenant <Guid>] [-EnableTranscription] [-EnableSharedVoicemailSystemPromptSuppression] [-CallPriority <Int16>] [<CommonParameters>] +``` + +## DESCRIPTION +The New-CsAutoAttendantCallableEntity cmdlet lets you create a callable entity for use with call transfers from the Auto Attendant service. Callable entities can be created using either Object ID or TEL URIs and can refer to any of the following entities: + +- User +- ApplicationEndpoint +- ConfigurationEndpoint +- ExternalPstn +- SharedVoicemail + +**NOTE**: In order to setup a shared voicemail, an Office 365 Group that can receive external emails is required. + +## EXAMPLES + +### Example 1 +```powershell +$callableEntity = New-CsAutoAttendantCallableEntity -Identity "9bad1a25-3203-5207-b34d-1bd933b867a5" -Type User +``` + +This example creates a user callable entity. + +### Example 2 +```powershell +$callableEntity = New-CsAutoAttendantCallableEntity -Identity "tel:+1234567890" -Type ExternalPSTN +``` + +This example creates an ExternalPSTN callable entity. + +### Example 3 +```powershell +$operatorObjectId = (Get-CsOnlineUser operator@contoso.com).ObjectId +$callableEntity = New-CsAutoAttendantCallableEntity -Identity $operatorObjectId -Type User +``` + +This example gets a user object using Get-CsOnlineUser cmdlet. We then use the Microsoft Entra ObjectId of that user object to create a user callable entity. + +### Example 4 +```powershell +$callableEntityId = Find-CsOnlineApplicationInstance -SearchQuery "Main Auto Attendant" -MaxResults 1 | Select-Object -Property Id +$callableEntity = New-CsAutoAttendantCallableEntity -Identity $callableEntityId.Id -Type ApplicationEndpoint +``` + +This example gets an application instance by name using Find-CsOnlineApplicationInstance cmdlet. We then use the Microsoft Entra ObjectId of that application instance to create an application endpoint callable entity. + +### Example 5 +```powershell +$callableEntityGroup = Find-CsGroup -SearchQuery "Main Auto Attendant" -ExactMatchOnly $true -MailEnabledOnly $true +$callableEntity = New-CsAutoAttendantCallableEntity -Identity $callableEntityGroup -Type SharedVoicemail -EnableTranscription +``` + +This example gets an Office 365 group by name using Find-CsGroup cmdlet. Then the Guid of that group is used to create a shared voicemail callable entity that supports transcription. + +## PARAMETERS + +### -Identity +The Identity parameter represents the ID of the callable entity; this can be either a Object ID or a TEL URI. + +- Only the Object IDs of users that have Enterprise Voice enabled are supported. +- Only PSTN numbers that are acquired and assigned through Skype for Business Online are supported. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Type +The Type parameter represents the type of the callable entity, which can be any of the following: + +- User +- ApplicationEndpoint (when transferring to a Resource Account) +- ConfigurationEndpoint (when transferring directly to a nested Auto Attendant or Call Queue) +- ExternalPstn +- SharedVoicemail + +> [!IMPORTANT] +> Nesting Auto attendants and Call queues via ***ConfigurationEndpoint*** isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. If you nest an Auto attendant or Call queue without a resource account, authorized users can't edit the auto attendant or call queue. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTranscription +Enables the email transcription of voicemail, this is only supported with shared voicemail callable entities. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSharedVoicemailSystemPromptSuppression +Suppresses the "Please leave a message after the tone" system prompt when transferring to shared voicemail. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallPriority +_Saving an auto attendant configuration through Teams admin center will reset the priority to 3 - Normal / Default._ + +The Call Priority of the MenuOption, only applies when the `Type` is `ApplicationEndpoint` or `ConfigurationEndpoint`. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 + +1 = Very High +2 = High +3 = Normal / Default +4 = Low +5 = Very Low + +> [!IMPORTANT] +> Call priorities isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. Authorized users will not be able to edit call flows with priorities. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 3 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.OAA.Models.CallableEntity + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineUser](https://learn.microsoft.com/powershell/module/teams/get-csonlineuser) + +[Find-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/find-csonlineapplicationinstance) diff --git a/teams/teams-ps/teams/New-CsAutoAttendantDialScope.md b/teams/teams-ps/teams/New-CsAutoAttendantDialScope.md new file mode 100644 index 0000000000..acea07c42e --- /dev/null +++ b/teams/teams-ps/teams/New-CsAutoAttendantDialScope.md @@ -0,0 +1,113 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendantdialscope +applicable: Microsoft Teams +title: New-CsAutoAttendantDialScope +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsAutoAttendantDialScope + +## SYNOPSIS +Use New-CsAutoAttendantDialScope cmdlet to create dial-scopes for use with Auto Attendant (AA) service. + +## SYNTAX + +``` +New-CsAutoAttendantDialScope -GroupScope -GroupIds <List> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a new dial-scope to be used with Auto Attendant (AA) service. AAs use dial-scopes to restrict the scope of call transfers that can be made through directory lookup feature. + +**NOTE**: The returned dial-scope model composes a member for the underlying type/implementation, e.g. in case of the group-based dial scope, in order to modify its Group IDs, you can access them through `DialScope.GroupScope.GroupIds`. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$groupIds = @("00000000-0000-0000-0000-000000000000") +$dialScope = New-CsAutoAttendantDialScope -GroupScope -GroupIds $groupIds +``` + +In Example 1, the New-CsAutoAttendantDialScope cmdlet is used to create a dial-scope with a group whose id is 00000000-0000-0000-0000-000000000000. + +### -------------------------- Example 2 -------------------------- +``` +$groupIds = Find-CsGroup -SearchQuery "Contoso Sales" | % { $_.Id } +$dialScope = New-CsAutoAttendantDialScope -GroupScope -GroupIds $groupIds +``` + +In Example 2, we use the Find-CsGroup cmdlet to find groups with name "Contoso Sales", and then use the identities of those groups to create an auto attendant dial scope using the New-CsAutoAttendantDialScope cmdlet. + +## PARAMETERS + +### -GroupScope +Indicates that a dial-scope based on groups (distribution lists, security groups) is to be created. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupIds +Refers to the IDs of the groups that are to be included in the dial-scope. + +Group IDs can be obtained by using the Find-CsGroup cmdlet. + +```yaml +Type: System.Collections.Generic.List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.DialScope + +## NOTES + +## RELATED LINKS + +[Find-CsGroup](https://learn.microsoft.com/powershell/module/teams/find-csgroup) diff --git a/skype/skype-ps/skype/New-CsAutoAttendantMenu.md b/teams/teams-ps/teams/New-CsAutoAttendantMenu.md similarity index 79% rename from skype/skype-ps/skype/New-CsAutoAttendantMenu.md rename to teams/teams-ps/teams/New-CsAutoAttendantMenu.md index cf9ea0093d..762182a023 100644 --- a/skype/skype-ps/skype/New-CsAutoAttendantMenu.md +++ b/teams/teams-ps/teams/New-CsAutoAttendantMenu.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendantmenu -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendantmenu +applicable: Microsoft Teams title: New-CsAutoAttendantMenu schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsAutoAttendantMenu @@ -24,7 +24,6 @@ New-CsAutoAttendantMenu -Name <String> [-MenuOptions <List>] [-Prompts <List>] [ ## DESCRIPTION The New-CsAutoAttendantMenu cmdlet creates a new menu for the Auto Attendant (AA) service. The OAA service uses menus to provide callers with choices, and then takes action based on the selection. - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -44,7 +43,6 @@ $menu = New-CsAutoAttendantMenu -Name "Default Menu" -Prompts @($menuPrompt) -Me This example creates a new menu that allows the caller to reach a target by name or the operator by pressing the 0 key, and also defines the Directory Search Method to Dial By Name. - ## PARAMETERS ### -Name @@ -54,7 +52,7 @@ The Name parameter represents a friendly name for the menu. Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -68,12 +66,11 @@ The MenuOptions parameter is a list of menu options for this menu. These menu op You can create menu options by using the New-CsAutoAttendantMenuOption cmdlet. - ```yaml Type: System.Collections.Generic.List Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -87,12 +84,11 @@ The Prompts parameter reflects the prompts to play when the menu is activated. You can create new prompts by using the New-CsAutoAttendantPrompt cmdlet. - ```yaml Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -104,12 +100,11 @@ Accept wildcard characters: False ### -EnableDialByName The EnableDialByName parameter lets users do a directory search by recipient name and get transferred to the party. - ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -119,7 +114,7 @@ Accept wildcard characters: False ``` ### -DirectorySearchMethod -The DirectorySearchMethod parameter lets you define the type of Directory Search Method for the Auto Attendant menu, for more information, see [Set up a Cloud auto attendant](https://docs.microsoft.com/MicrosoftTeams/create-a-phone-system-auto-attendant?WT.mc_id=TeamsAdminCenterCSH) +The DirectorySearchMethod parameter lets you define the type of Directory Search Method for the Auto Attendant menu, for more information, see [Set up a Cloud auto attendant](https://learn.microsoft.com/MicrosoftTeams/create-a-phone-system-auto-attendant?WT.mc_id=TeamsAdminCenterCSH) Possible values are @@ -131,7 +126,7 @@ Possible values are Type: Microsoft.Rtc.Management.Hosted.OAA.Models.DirectorySearchMethod Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -146,7 +141,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -156,22 +151,19 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### Microsoft.Rtc.Management.Hosted.OAA.Models.Menu - ## NOTES ## RELATED LINKS -[New-CsAutoAttendantMenuOption](New-CsAutoAttendantMenuOption.md) -[New-CsAutoAttendantPrompt](New-CsAutoAttendantPrompt.md) - +[New-CsAutoAttendantMenuOption](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantmenuoption) +[New-CsAutoAttendantPrompt](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantmenuoption) diff --git a/teams/teams-ps/teams/New-CsAutoAttendantMenuOption.md b/teams/teams-ps/teams/New-CsAutoAttendantMenuOption.md new file mode 100644 index 0000000000..075d0dccbd --- /dev/null +++ b/teams/teams-ps/teams/New-CsAutoAttendantMenuOption.md @@ -0,0 +1,185 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendantmenuoption +applicable: Microsoft Teams +title: New-CsAutoAttendantMenuOption +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsAutoAttendantMenuOption + +## SYNOPSIS +Use the New-CsAutoAttendantMenuOption cmdlet to create a new menu option. + +## SYNTAX + +``` +New-CsAutoAttendantMenuOption -Action <DisconnectCall | TransferCallToOperator | TransferCallToTarget> -DtmfResponse <Tone0 | Tone1 | Tone2 | Tone3 | Tone4 | Tone5 | Tone6 | Tone7 | Tone8 | Tone9 | Automatic> [-VoiceResponses <List>] [-CallTarget <Object>] [-Prompt <Object>] [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The New-CsAutoAttendantMenuOption cmdlet creates a new menu option for the Auto Attendant (AA) service. The AA service uses the menu options to respond to a caller with the appropriate action. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$menuOption = New-CsAutoAttendantMenuOption -Action TransferCallToOperator -DtmfResponse Tone0 +``` + +This example creates a menu option to call the operator when the 0 key is pressed. + +### -------------------------- Example 2 -------------------------- +``` +$troubleShootObjectId = (Get-CsOnlineUser troubleShoot@contoso.com).ObjectId +$troubleShootEntity = New-CsAutoAttendantCallableEntity -Identity $troubleShootObjectId -Type ApplicationEndpoint +$menuOption = New-CsAutoAttendantMenuOption -Action TransferCallToTarget -DtmfResponse Tone1 -VoiceResponses "Sales" -CallTarget $troubleShootEntity +``` + +This example creates a menu option to transfer the call to an application endpoint when the caller speaks the word "Sales" or presses the 1 key. + +### -------------------------- Example 3 -------------------------- +``` +$Prompt = New-CsAutoAttendantPrompt -ActiveType TextToSpeech -TextToSpeechPrompt "Our Office is open from Monday to Friday from 9 AM to 5 PM" +$menuOption = New-CsAutoAttendantMenuOption -Action Announcement -DtmfResponse Tone2 -VoiceResponses "Hours" -Prompt $Prompt +``` + +This example creates a menu option to play an announcement for the defined prompt. After playing the announcement, the **Menu Prompt** is repeated. + +## PARAMETERS + +### -Action +The Action parameter represents the action to be taken when the menu option is activated. The Action must be set to one of the following values: + +- Announcement - plays a defined prompt then returns to the menu +- DisconnectCall - The call is disconnected. +- TransferCallToOperator - the call is transferred to the operator. +- TransferCallToTarget - The call is transferred to the menu option's call target. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DtmfResponse +The DtmfResponse parameter indicates the key on the telephone keypad to be pressed to activate the menu option. The DtmfResponse must be set to one of the following values: + +- Tone0 to Tone9 - Corresponds to DTMF tones from 0 to 9. +- ToneStar - Corresponds to DTMF tone *. +- TonePound - Corresponds to DTMF tone #. +- Automatic - The action is executed without user response. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceResponses +The VoiceResponses parameter represents the voice responses to select a menu option when Voice Responses are enabled for the auto attendant. + +Voice responses are currently limited to one voice response per menu option. + +```yaml +Type: System.Collections.Generic.List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallTarget +The CallTarget parameter represents the target for call transfer after the menu option is selected. + +CallTarget is required if the action of the menu option is TransferCallToTarget. + +Use the New-CsAutoAttendantCallableEntity cmdlet to create new callable entities. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Prompt +The **Prompt** parameter reflects the prompts to play when the menu option is activated. + +You can create new prompts by using the **New-CsAutoAttendantPrompt** cmdlet. + +This parameter is required if the **Action** is set to **Announcement**. + +```yaml +Type: Microsoft.Rtc.Management.Hosted.OAA.Models.Prompt +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.OAA.Models.MenuOption + +## NOTES + +## RELATED LINKS + +[New-CsAutoAttendantCallableEntity](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallableentity) diff --git a/skype/skype-ps/skype/New-CsAutoAttendantPrompt.md b/teams/teams-ps/teams/New-CsAutoAttendantPrompt.md similarity index 82% rename from skype/skype-ps/skype/New-CsAutoAttendantPrompt.md rename to teams/teams-ps/teams/New-CsAutoAttendantPrompt.md index b9b00d1b13..9a601bd5d8 100644 --- a/skype/skype-ps/skype/New-CsAutoAttendantPrompt.md +++ b/teams/teams-ps/teams/New-CsAutoAttendantPrompt.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csautoattendantprompt -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csautoattendantprompt +applicable: Microsoft Teams title: New-CsAutoAttendantPrompt schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsAutoAttendantPrompt @@ -35,7 +35,6 @@ New-CsAutoAttendantPrompt -ActiveType <None | TextToSpeech | AudioFile> -AudioFi ## DESCRIPTION The New-CsAutoAttendantPrompt cmdlet creates a new prompt for the Auto Attendant (AA) service. A prompt is either an audio file that is played, or text that is read aloud to give callers additional information. A prompt can be disabled by setting the ActiveType to None. - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -45,10 +44,9 @@ $ttsPrompt = New-CsAutoAttendantPrompt -TextToSpeechPrompt "Welcome to Contoso!" This example creates a new prompt that reads the supplied text. - ### -------------------------- Example 2 -------------------------- ```powershell -$content = Get-Content "C:\Media\Welcome.wav" -Encoding byte -ReadCount 0 +$content = [System.IO.File]::ReadAllBytes('C:\Media\hello.wav') $audioFile = Import-CsOnlineAudioFile -ApplicationId "OrgAutoAttendant" -FileName "hello.wav" -Content $content $audioFilePrompt = New-CsAutoAttendantPrompt -AudioFilePrompt $audioFile ``` @@ -57,14 +55,13 @@ This example creates a new prompt that plays the selected audio file. ### -------------------------- Example 3 -------------------------- ```powershell -$content = Get-Content "C:\Media\Welcome.wav" -Encoding byte -ReadCount 0 +$content = [System.IO.File]::ReadAllBytes('C:\Media\hello.wav') $audioFile = Import-CsOnlineAudioFile -ApplicationId "OrgAutoAttendant" -FileName "hello.wav" -Content $content $dualPrompt = New-CsAutoAttendantPrompt -ActiveType AudioFile -AudioFilePrompt $audioFile -TextToSpeechPrompt "Welcome to Contoso!" ``` This example creates a new prompt that has both audio file and text-to-speech data, but will play the audio file when the prompt is activated (rendered). - ## PARAMETERS ### -ActiveType @@ -74,12 +71,11 @@ The ActiveType parameter identifies the active type (modality) of the AA prompt. This is explicitly required if both Audio File and TTS prompts are specified. Otherwise, it is inferred. - ```yaml Type: Object Parameter Sets: Dual Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -93,12 +89,11 @@ The AudioFilePrompt parameter represents the audio to play when the prompt is ac This parameter is required when audio file prompts are being created. You can create audio files by using the `Import-CsOnlineAudioFile` cmdlet. - ```yaml Type: Object Parameter Sets: AudioFile, Dual Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -112,12 +107,11 @@ The TextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt that This parameter is required when text to speech prompts are being created. - ```yaml Type: System.String Parameter Sets: TextToSpeech, Dual Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -132,7 +126,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -142,21 +136,18 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### Microsoft.Rtc.Management.Hosted.OAA.Models.Prompt - ## NOTES ## RELATED LINKS -[Import-CsOnlineAudioFile](Import-CsOnlineAudioFile.md) - +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) diff --git a/teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md b/teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md index aaa731cd68..e710dfbc0a 100644 --- a/teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md +++ b/teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md @@ -1,72 +1,84 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/new-csbatchpolicyassignmentoperation +online version: https://learn.microsoft.com/powershell/module/teams/new-csbatchpolicyassignmentoperation +title: New-CsBatchPolicyAssignmentOperation schema: 2.0.0 author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsBatchPolicyAssignmentOperation ## SYNOPSIS -**Note:** This cmdlet is currently in public preview. - -This cmdlet is used to assign a policy to a batch of users. +This cmdlet is used to assign or unassign a policy to a batch of users. ## SYNTAX ``` -New-CsBatchPolicyAssignmentOperation -PolicyType <String> -PolicyName <String> -Identity <Array> [-OperationName <String>] +New-CsBatchPolicyAssignmentOperation [-OperationName <String>] -Identity <String[]> -PolicyType <String> + [-AdditionalParameters <Hashtable>] [-PolicyName <String>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION When a policy is assigned to a batch of users, the assignments are performed as an asynchronous operation. The cmdlet returns the operation ID which can be used to track the progress and status of the assignments. -Users can be specified by their object ID (guid) or by their UPN/SIP/email (user@contoso.com). +Users can be specified by their object ID (guid) or by their SIP address (user@contoso.com). Note that a user's SIP address often has the same value as the User Principal Name (UPN), but this is not required. If a user is specified using their UPN, but it has a different value than their SIP address, then the policy assignment will fail for the user. + +A batch may contain up to 5,000 users. If a batch includes duplicate users, the duplicates will be removed from the batch before processing and status will only be provided for the unique users remaining in the batch. For best results, do not submit more than a few batches at a time. Allow batches to complete processing before submitting more batches. -A batch may contain up to 20,000 users. +You must be a Teams service admin or a Teams communication admin to run the cmdlet. Batch policy assignment is currently limited to the following policy types: -CallingLineIdentity, OnlineVoiceRoutingPolicy, TeamsAppSetupPolicy, TeamsAppPermissionPolicy, TeamsCallingPolicy, TeamsCallParkPolicy, TeamsChannelsPolicy, TeamsEducationAssignmentsAppPolicy, TeamsEmergencyCallingPolicy, TeamsMeetingBroadcastPolicy, TeamsEmergencyCallRoutingPolicy, TeamsMeetingPolicy, TeamsMessagingPolicy, TeamsUpdateManagementPolicy, TeamsUpgradePolicy, TeamsVerticalPackagePolicy, TeamsVideoInteropServicePolicy, TenantDialPlan +CallingLineIdentity, ExternalAccessPolicy, OnlineVoiceRoutingPolicy, TeamsAppSetupPolicy, TeamsAppPermissionPolicy, TeamsCallingPolicy, TeamsCallParkPolicy, TeamsChannelsPolicy, TeamsEducationAssignmentsAppPolicy, TeamsEmergencyCallingPolicy, TeamsMeetingBroadcastPolicy, TeamsEmergencyCallRoutingPolicy, TeamsMeetingPolicy, TeamsMessagingPolicy, TeamsTemplatePermissionPolicy, TeamsUpdateManagementPolicy, TeamsUpgradePolicy, TeamsVerticalPackagePolicy, TeamsVideoInteropServicePolicy, TenantDialPlan ## EXAMPLES -### Example 1 -In this example, the batch of users is specified as an array of user email addresses. - +### EXAMPLE 1 ``` $users_ids = @("psmith@contoso.com","tsanchez@contoso.com","bharvest@contoso.com") New-CsBatchPolicyAssignmentOperation -PolicyType TeamsMeetingPolicy -PolicyName Kiosk -Identity $users_ids -OperationName "Batch assign Kiosk" ``` -### Example 2 -In this example, the batch of users is read from a text file containing user object IDs (guids). +In this example, the batch of users is specified as an array of user SIP addresses. +### EXAMPLE 2 +``` +$users_ids = @("2bdb15a9-2cf1-4b27-b2d5-fcc1d13eebc9", "d928e0fc-c957-4685-991b-c9e55a3534c7", "967cc9e4-4139-4057-9b84-1af80f4856fc") +New-CsBatchPolicyAssignmentOperation -PolicyType TeamsMeetingPolicy -PolicyName $null -Identity $users_ids -OperationName "Batch unassign meeting policy" ``` -$user_ids = Get-Content .\users_ids.txt + +In this example, a policy is removed from a batch of users by passing $null as the policy name. + +### EXAMPLE 3 +``` +$users_ids = Get-Content .\users_ids.txt New-CsBatchPolicyAssignmentOperation -PolicyType TeamsMeetingPolicy -PolicyName Kiosk -Identity $users_ids -OperationName "Batch assign Kiosk" ``` -### Example 3 -In this example, the batch of users is obtained by connecting to Azure AD and retrieving a collection of users and then referencing their user principal names. +In this example, the batch of users is read from a text file containing user object IDs (guids). +### EXAMPLE 4 ``` Connect-AzureAD $users = Get-AzureADUser -New-CsBatchPolicyAssignmentOperation -PolicyType TeamsMeetingPolicy -PolicyName Kiosk -Identity $users.UserPrincipalName -OperationName "batch assign kiosk" +New-CsBatchPolicyAssignmentOperation -PolicyType TeamsMeetingPolicy -PolicyName Kiosk -Identity $users.SipProxyAddress -OperationName "batch assign kiosk" ``` +In this example, the batch of users is obtained by connecting to Microsoft Entra ID and retrieving a collection of users and then referencing the SipProxyAddress property. + ## PARAMETERS ### -Identity -An array of users, specified either as object IDs (guid) or as UPN/SIP/email. There is a maximum of 20,000 users per batch. +An array of users, specified either using object IDs (guid) or SIP addresses. There is a maximum of 5,000 users per batch. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -77,11 +89,11 @@ Accept wildcard characters: False ``` ### -PolicyName -The name of the policy to be assigned to the users. +The name of the policy to be assigned to the users. To remove the currently assigned policy, use $null or an empty string "". ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -92,11 +104,11 @@ Accept wildcard characters: False ``` ### -PolicyType -The name of the policy to be assigned to the users. +The type of the policy to be assigned to the users. For the list of current policy types accepted by this parameter, see the Description section at the beginning of this article. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -111,7 +123,22 @@ An optional name for the batch assignment operation. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdditionalParameters +. + +```yaml +Type: Hashtable +Parameter Sets: (All) Aliases: Required: False @@ -121,9 +148,98 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Break +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -136,4 +252,4 @@ The ID of the operation that can be used with the Get-CsBatchPolicyAssignmentOpe ## RELATED LINKS -[Get-CsBatchPolicyAssignmentOperation]() +[Get-CsBatchPolicyAssignmentOperation](https://learn.microsoft.com/powershell/module/teams/get-csbatchpolicyassignmentoperation) diff --git a/teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md b/teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md index 7ca9483795..7ff16c4092 100644 --- a/teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md +++ b/teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md @@ -2,10 +2,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams title: New-CsBatchPolicyPackageAssignmentOperation -author: ruguan -ms.author: ruguan +author: serdarsoysal +ms.author: serdars manager: amitar -online version: https://docs.microsoft.com/powershell/module/teams/new-csbatchpolicypackageassignmentoperation +online version: https://learn.microsoft.com/powershell/module/teams/new-csbatchpolicypackageassignmentoperation schema: 2.0.0 --- @@ -22,7 +22,7 @@ New-CsBatchPolicyPackageAssignmentOperation -Identity <String[]> -PackageName <S ## DESCRIPTION -This cmdlet submits an operation that applies a policy package to a batch of users in a tenant. Provide one or more user identities to assign the package with all the associated policies. The available policy packages and their definitions can be found by running Get-CsPolicyPackage. The recommended policy package for each user can be found by running Get-CsUserPolicyPackageRecommendation. For more information on policy packages, please review https://docs.microsoft.com/en-us/MicrosoftTeams/manage-policy-packages +This cmdlet submits an operation that applies a policy package to a batch of users in a tenant. Provide one or more user identities to assign the package with all the associated policies. The available policy packages and their definitions can be found by running Get-CsPolicyPackage. The recommended policy package for each user can be found by running Get-CsUserPolicyPackageRecommendation. For more information on policy packages, please review https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages. ## EXAMPLES @@ -53,7 +53,7 @@ Accept wildcard characters: False ### -PackageName -The name of a specific policy package to apply. All policy package names can be found by running Get-CsPolicyPackage. +The name of a specific policy package to apply. All policy package names can be found by running Get-CsPolicyPackage. To remove the currently assigned package, use $null or an empty string "". This will not remove any policy assignments, just the package assigned value. ```yaml Type: String @@ -78,6 +78,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Get-CsPolicyPackage](Get-CsPolicyPackage.md) +[Get-CsPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage) -[Get-CsUserPolicyPackageRecommendation](Get-CsUserPolicyPackageRecommendation.md) \ No newline at end of file +[Get-CsUserPolicyPackageRecommendation](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackagerecommendation) + +[Get-CsUserPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicypackage) diff --git a/teams/teams-ps/teams/New-CsBatchTeamsDeployment.md b/teams/teams-ps/teams/New-CsBatchTeamsDeployment.md new file mode 100644 index 0000000000..90392de568 --- /dev/null +++ b/teams/teams-ps/teams/New-CsBatchTeamsDeployment.md @@ -0,0 +1,98 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csbatchteamsdeployment +title: New-CsBatchTeamsDeployment +schema: 2.0.0 +--- + +# New-CsBatchTeamsDeployment + +## SYNOPSIS + +This cmdlet is used to run a batch deployment orchestration. + +## SYNTAX + +``` +New-CsBatchTeamsDeployment -TeamsFilePath <String> -UsersFilePath <String> + -UsersToNotify <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deploying Teams at scale enables admins to deploy up to 500 teams and add 25 users per team using one Teams PowerShell command and two CSV files. This allows admins to meet your organization's scale needs and significantly reduce deployment time. Admins can also use this solution to add and remove members from existing teams at scale. You can use this cmdlet to: +- Create teams using pre-built templates or your own custom templates. +- Add users to teams as owners or members. +- Manage teams at scale by adding or removing users from existing teams. +- Stay notified through email, including completion, status, and errors (if any). You can choose to notify up to five people about the status of each batch of teams you deploy. Team owners and members are automatically notified when they're added to a team. + +## EXAMPLES + +### EXAMPLE 1 +``` +New-CsBatchTeamsDeployment -TeamsFilePath "C:\dscale\Teams.csv" -UsersFilePath "C:\dscale\Users.csv" -UsersToNotify "adminteams@contoso.com,adelev@contoso.com" +``` +This command runs a batch deployment with the provided parameters in the CSV files and emails the status and errors (if any) to adminteams@contoso.com and adelev@contoso.com. + +## PARAMETERS + +### -TeamsFilePath +The path to the CSV file that defines the teams you're creating. For information about the CSV file format, see [Deploy Teams at scale for frontline workers](https://learn.microsoft.com/microsoft-365/frontline/deploy-teams-at-scale). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsersFilePath +The path to the CSV file that maps the users you're adding to each team. For information about the CSV file format, see [Deploy Teams at scale for frontline workers](https://learn.microsoft.com/microsoft-365/frontline/deploy-teams-at-scale). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsersToNotify +The email addresses of up to five recipients to notify about this deployment. The recipients will receive email notifications about deployment status. The email contains the orchestration ID for the batch you submitted and any errors that may have occurred. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### OrchestrationId +The ID of the operation that can be used with the Get-CsBatchTeamsDeploymentStatus cmdlet to get the status of the operation. + +## NOTES + +## RELATED LINKS + +[Get-CsBatchTeamsDeploymentStatus](https://learn.microsoft.com/powershell/module/teams/get-csbatchteamsdeploymentstatus) diff --git a/teams/teams-ps/teams/New-CsCallQueue.md b/teams/teams-ps/teams/New-CsCallQueue.md new file mode 100644 index 0000000000..003cdb37c1 --- /dev/null +++ b/teams/teams-ps/teams/New-CsCallQueue.md @@ -0,0 +1,1706 @@ +--- +external help file: Microsoft.Rtc.Management.dll-Help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-cscallqueue +applicable: Microsoft Teams +title: New-CsCallQueue +author: tomkau +ms.author: tomkau +manager: bulenteg +ms.reviewer: +schema: 2.0.0 +--- + +# New-CsCallQueue + +## SYNOPSIS +Creates new Call Queue in your Skype for Business Online organization. + +## SYNTAX + +``` +New-CsCallQueue -Name <String> [-AgentAlertTime <Int16>] [-AllowOptOut <Boolean>] [-DistributionLists <List>] [-Tenant <Guid>] [-UseDefaultMusicOnHold <Boolean>] [-WelcomeMusicAudioFileId <Guid>] [-MusicOnHoldAudioFileId <Guid>] [-OverflowAction <Object>] [-OverflowActionTarget <Guid>] [-OverflowActionCallPriority <Int16>] [-OverflowThreshold <Int16>] [-TimeoutAction <Object>] [-TimeoutActionTarget <Guid>] [-TimeoutActionCallPriority <Int16>] [-TimeoutThreshold <Int16>] [-NoAgentAction <Object>] [-NoAgentActionTarget <Guid>] [-NoAgentActionCallPriority <Int16>] [-RoutingMethod <Object>] [-PresenceBasedRouting <Boolean>] [-ConferenceMode <Boolean>] [-User <List>] [-LanguageId <String>] [-LineUri <String>] [-OboResourceAccountIds <List>] [-OverflowDisconnectTextToSpeechPrompt <String>][-OverflowDisconnectAudioFilePrompt <Guid>] [-OverflowRedirectPersonTextToSpeechPrompt <String>][-OverflowRedirectPersonAudioFilePrompt <Guid>] [-OverflowRedirectVoiceAppTextToSpeechPrompt <String>] [-OverflowRedirectVoiceAppAudioFilePrompt <Guid>] [-OverflowRedirectPhoneNumberTextToSpeechPrompt <String>] [-OverflowRedirectPhoneNumberAudioFilePrompt <Guid>] [-OverflowRedirectVoicemailTextToSpeechPrompt <String>] [-OverflowRedirectVoicemailAudioFilePrompt <Guid>] [-OverflowSharedVoicemailTextToSpeechPrompt <String>] [-OverflowSharedVoicemailAudioFilePrompt <Guid>] [-EnableOverflowSharedVoicemailTranscription <Boolean>] [-EnableOverflowSharedVoicemailSystemPromptSuppression <Boolean>] [-TimeoutDisconnectTextToSpeechPrompt <String>][-TimeoutDisconnectAudioFilePrompt <Guid>] [-TimeoutRedirectPersonTextToSpeechPrompt <String>] [-TimeoutRedirectPersonAudioFilePrompt <Guid>] [-TimeoutRedirectVoiceAppTextToSpeechPrompt <String>] [-TimeoutRedirectVoiceAppAudioFilePrompt <Guid>] [-TimeoutRedirectPhoneNumberTextToSpeechPrompt <String>] [-TimeoutRedirectPhoneNumberAudioFilePrompt <Guid>] [-TimeoutRedirectVoicemailTextToSpeechPrompt <String>] [-TimeoutRedirectVoicemailAudioFilePrompt <Guid>] [-TimeoutSharedVoicemailTextToSpeechPrompt <String>] [-TimeoutSharedVoicemailAudioFilePrompt <Guid>] [-EnableTimeoutSharedVoicemailTranscription <Boolean>] [-EnableTimeoutSharedVoicemailSystemPromptSuppression <Boolean>] [-NoAgentApplyTo <String>] [-NoAgentDisconnectTextToSpeechPrompt <String>][-NoAgentDisconnectAudioFilePrompt <Guid>] [-NoAgentRedirectPersonTextToSpeechPrompt <String>] [-NoAgentRedirectPersonAudioFilePrompt <Guid>] [-NoAgentRedirectVoiceAppTextToSpeechPrompt <String>] [-NoAgentRedirectVoiceAppAudioFilePrompt <Guid>] [-NoAgentRedirectPhoneNumberTextToSpeechPrompt <String>] [-NoAgentRedirectPhoneNumberAudioFilePrompt <Guid>] [-NoAgentRedirectVoicemailTextToSpeechPrompt <String>] [-NoAgentRedirectVoicemailAudioFilePrompt <Guid>] [-NoAgentSharedVoicemailTextToSpeechPrompt <String>] [-NoAgentSharedVoicemailAudioFilePrompt <Guid>] [-EnableNoAgentSharedVoicemailTranscription <Boolean>] [-EnableNoAgentSharedVoicemailSystemPromptSuppression <Boolean>] [-ChannelId <String>] [-ChannelUserObjectId <Guid>] [-ShiftsTeamId <String>] [-ShiftsSchedulingGroupId <String>] [-AuthorizedUsers <List>] [-HideAuthorizedUsers <List>] [-WelcomeTextToSpeechPrompt <String>] [-IsCallbackEnabled <Boolean>] [-CallbackRequestDtmf <String>] [-WaitTimeBeforeOfferingCallbackInSecond <Int16>] [-NumberOfCallsInQueueBeforeOfferingCallback <Int16>] [-CallToAgentRatioThresholdBeforeOfferingCallback <Int16>] [-CallbackOfferAudioFilePromptResourceId <Guid>] [-CallbackOfferTextToSpeechPrompt <String>] [-CallbackEmailNotificationTarget <Guid>] [-ServiceLevelThresholdResponseTimeInSecond <Int16> ] [-ComplianceRecordingForCallQueueTemplateId <List>] [-TextAnnouncementForCR <String>] [-CustomAudioFileAnnouncementForCR <Guid>] [-TextAnnouncementForCRFailure <String>] [-CustomAudioFileAnnouncementForCRFailure <Guid>] [-ShouldOverwriteCallableChannelProperty <Boolean>] [-SharedCallQueueHistoryTemplateId <String>] [<CommonParameters>] +``` + +## DESCRIPTION +The New-CsCallQueue cmdlet creates a new Call Queue. + +> [!CAUTION] +> The following configuration parameters are currently only available in PowerShell and do not appear in Teams admin center. Saving a call queue configuration through Teams admin center will _remove_ any of these configured items: +> +> - -HideAuthorizedUsers +> - -OverflowActionCallPriority +> - -OverflowRedirectPersonTextToSpeechPrompt +> - -OverflowRedirectPersonAudioFilePrompt +> - -OverflowRedirectVoicemailTextToSpeechPrompt +> - -OverflowRedirectVoicemailAudioFilePrompt +> - -TimeoutActionCallPriority +> - -TimeoutRedirectPersonTextToSpeechPrompt +> - -TimeoutRedirectPersonAudioFilePrompt +> - -TimeoutRedirectVoicemailTextToSpeechPrompt +> - -TimeoutRedirectVoicemailAudioFilePrompt +> - -NoAgentActionCallPriority +> - -NoAgentRedirectPersonTextToSpeechPrompt +> - -NoAgentRedirectPersonAudioFilePrompt +> - -NoAgentRedirectVoicemailTextToSpeechPrompt +> - -NoAgentRedirectVoicemailAudioFilePrompt +> +> The following configuration parameters will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time. +> +> - -ShiftsTeamId +> - -ShiftsSchedulingGroupId +> - -ComplianceRecordingForCallQueueTemplateId +> - -TextAnnouncementForCR +> - -CustomAudioFileAnnouncementForCR +> - -TextAnnouncementForCRFailure +> - -CustomAudioFileAnnouncementForCRFailure +> - -SharedCallQueueHistoryTemplateId +> +> [Nesting Auto attendants and Call queues](/microsoftteams/plan-auto-attendant-call-queue#nested-auto-attendants-and-call-queues) without a resource account isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. If you nest an Auto attendant or Call queue without a resource account, authorized users can't edit the auto attendant or call queue. +> +> Authorized users can't edit call flows with call priorities at this time. + +## EXAMPLES + +### Example 1 +``` +New-CsCallQueue -Name "Help Desk" -UseDefaultMusicOnHold $true +``` + +This example creates a Call Queue for the organization named "Help Desk" using default music on hold. + +### Example 2 +``` +New-CsCallQueue -Name "Help desk" -RoutingMethod Attendant -DistributionLists @("8521b0e3-51bd-4a4b-a8d6-b219a77a0a6a", "868dccd8-d723-4b4f-8d74-ab59e207c357") -AllowOptOut $false -AgentAlertTime 30 -OverflowThreshold 15 -OverflowAction Forward -OverflowActionTarget 7fd04db1-1c8e-4fdf-9af5-031514ba1358 -TimeoutThreshold 30 -TimeoutAction Disconnect -MusicOnHoldAudioFileId 1e81adaf-7c3e-4db1-9d61-5d135abb1bcc -WelcomeMusicAudioFileId 0b31bbe5-e2a0-4117-9b6f-956bca6023f8 + +``` + +This example creates a Call Queue for the organization named "Help Desk" with music on hold and welcome music audio files. + +## PARAMETERS + +### -Name +The Name parameter specifies a unique name for the Call Queue. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AgentAlertTime +The AgentAlertTime parameter represents the time (in seconds) that a call can remain unanswered before it is automatically routed to the next agent. The AgentAlertTime can be set to any integer value between 15 and 180 seconds (3 minutes), inclusive. The default value is 30 seconds. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 30 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOptOut +The AllowOptOut parameter indicates whether or not agents can opt in or opt out from taking calls from a Call Queue. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DistributionLists +The DistributionLists parameter lets you add all the members of the distribution lists to the Call Queue. This is a list of distribution list GUIDs. A service wide configurable maximum number of DLs per Call Queue are allowed. Only the first N (service wide configurable) agents from all distribution lists combined are considered for accepting the call. Nested DLs are supported. O365 Groups can also be used to add members to the Call Queue. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for Microsoft internal use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseDefaultMusicOnHold +The UseDefaultMusicOnHold parameter indicates that this Call Queue uses the default music on hold. This parameter cannot be specified together with MusicOnHoldAudioFileId. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WelcomeMusicAudioFileId +The WelcomeMusicAudioFileId parameter represents the audio file to play when callers are connected with the Call Queue. This is the unique identifier of the audio file. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MusicOnHoldAudioFileId +The MusicOnHoldAudioFileId parameter represents music to play when callers are placed on hold. This is the unique identifier of the audio file. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowAction +The OverflowAction parameter designates the action to take if the overflow threshold is reached. The OverflowAction property must be set to one of the following values: DisconnectWithBusy, Forward, Voicemail, and SharedVoicemail. The default value is DisconnectWithBusy. + +PARAMVALUE: DisconnectWithBusy | Forward | Voicemail | SharedVoicemail + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: DisconnectWithBusy +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowActionTarget +The OverflowActionTarget parameter represents the target of the overflow action. If the OverFlowAction is set to Forward, this parameter must be set to a Guid or a telephone number with a mandatory 'tel:' prefix. If the OverflowAction is set to SharedVoicemail, this parameter must be set to a group ID (Microsoft 365, Distribution list, or Mail-enabled security). Otherwise, this parameter is optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowActionCallPriority +_Saving a call queue configuration through Teams admin center will reset the priority to 3 - Normal / Default._ + +If the OverFlowAction is set to Forward, and the OverflowActionTarget is set to an Auto attendant or Call queue resource account Guid, this parameter must be set to indicate the priority that will be assigned to the call. Otherwise, this parameter is not applicable. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 +- 1 = Very High +- 2 = High +- 3 = Normal / Default +- 4 = Low +- 5 = Very Low + +> [!IMPORTANT] +> Call priorities isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. Authorized users will not be able to edit call flows with priorities. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowThreshold +The OverflowThreshold parameter defines the number of calls that can be in the queue at any one time before the overflow action is triggered. The OverflowThreshold can be any integer value between 0 and 200, inclusive. A value of 0 causes calls not to reach agents and the overflow action to be taken immediately. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 50 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutAction +The TimeoutAction parameter defines the action to take if the timeout threshold is reached. The TimeoutAction property must be set to one of the following values: Disconnect, Forward, Voicemail, and SharedVoicemail. The default value is Disconnect. + +PARAMVALUE: Disconnect | Forward | Voicemail | SharedVoicemail + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disconnect +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutActionTarget +The TimeoutActionTarget represents the target of the timeout action. If the TimeoutAction is set to Forward, this parameter must be set to a Guid or a telephone number with a mandatory 'tel:' prefix. If the TimeoutAction is set to SharedVoicemail, this parameter must be set to an Office 365 Group ID. Otherwise, this field is optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutActionCallPriority +_Saving a call queue configuration through Teams admin center will reset the priority to 3 - Normal / Default._ + +If the TimeoutAction is set to Forward, and the TimeoutActionTarget is set to an Auto attendant or Call queue resource account Guid, this parameter must be set to indicate the priority that will be assigned to the call. Otherwise, this parameter is not applicable. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 +- 1 = Very High +- 2 = High +- 3 = Normal / Default +- 4 = Low +- 5 = Very Low + +> [!IMPORTANT] +> Call priorities isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. Authorized users will not be able to edit call flows with priorities. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutThreshold +The TimeoutThreshold parameter defines the time (in seconds) that a call can be in the queue before that call times out. At that point, the system will take the action specified by the TimeoutAction parameter. +The TimeoutThreshold can be any integer value between 0 and 2700 seconds (inclusive), and is rounded to the nearest 15th interval. For example, if set to 47 seconds, then it is rounded down to 45. If set to 0, welcome music is played, and then the timeout action will be taken. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 1200 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentApplyTo +The NoAgentApplyTo parameter defines if the NoAgentAction applies to calls already in queue and new calls arriving to the queue, or only new calls that arrive once the No Agents condition occurs. The default value is AllCalls. + +PARAMVALUE: AllCalls | NewCalls + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disconnect +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentAction +The NoAgentAction parameter defines the action to take if the no agents condition is reached. The NoAgentAction property must be set to one of the following values: Queue, Disconnect, Forward, Voicemail, and SharedVoicemail. The default value is Queue. + +PARAMVALUE: Queue | Disconnect | Forward | Voicemail | SharedVoicemail + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disconnect +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentActionTarget +The NoAgentActionTarget represents the target of the no agent action. If the NoAgentAction is set to Forward, this parameter must be set to a GUID or a telephone number with a mandatory 'tel:' prefix. If the NoAgentAction is set to SharedVoicemail, this parameter must be set to a Microsoft 365 Group ID. Otherwise, this field is optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentActionCallPriority +_Saving a call queue configuration through Teams admin center will reset the priority to 3 - Normal / Default._ + +If the NoAgentAction is set to Forward, and the NoAgentActionTarget is set to an Auto attendant or Call queue resource account Guid, this parameter must be set to indicate the priority that will be assigned to the call. Otherwise, this parameter is not applicable. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 +- 1 = Very High +- 2 = High +- 3 = Normal / Default +- 4 = Low +- 5 = Very Low + +> [!IMPORTANT] +> Call priorities isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. Authorized users will not be able to edit call flows with priorities. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoutingMethod +The RoutingMethod parameter defines how agents will be called in a Call Queue. If the routing method is set to Serial, then agents will be called one at a time. If the routing method is set to Attendant, then agents will be called in parallel. If the routing method is set to RoundRobin, the agents will be called using the Round Robin strategy so that all agents share the call load equally. If the routing method is set to LongestIdle, the agents will be called based on their idle time, that is, the agent that has been idle for the longest period will be called. + +PARAMVALUE: Attendant | Serial | RoundRobin | LongestIdle + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Attendant +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PresenceBasedRouting +The PresenceBasedRouting parameter indicates whether or not presence based routing will be applied while call being routed to Call Queue agents. When set to False, calls will be routed to agents who have opted in to receive calls, regardless of their presence state. When set to True, opted-in agents will receive calls only when their presence state is Available. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConferenceMode +The ConferenceMode parameter indicates whether or not Conference mode will be applied on calls for this Call queue. Conference mode significantly reduces the amount of time it takes for a caller to be connected to an agent, after the agent accepts the call. The following bullet points detail the difference between both modes: + +- Conference Mode Disabled: CQ call is presented to agent. Agent answers and media streams are setup. Based on geographic location of the CQ call and agent, there may be a slight delay in setting up the media streams which may result in some dead air and the first part of the conversation being cut off. + +- Conference Mode Enabled: CQ call is put into conference. Agent answers and is brought into conference. Media streams are already setup when agent is brought into conference thus no dead air, and first bit of conversation will not be cut off. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Users +The Users parameter lets you add agents to the Call Queue. This parameter expects a list of user unique identifiers (GUID). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LanguageId +The LanguageId parameter indicates the language that is used to play shared voicemail prompts. This parameter becomes a required parameter if either OverflowAction or TimeoutAction is set to SharedVoicemail. + +You can query the supported languages using the Get-CsAutoAttendantSupportedLanguage cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LineUri +This parameter is reserved for Microsoft internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OboResourceAccountIds +The OboResourceAccountIds parameter lets you add resource account with phone number to the Call Queue. The agents in the Call Queue will be able to make outbound calls using the phone number on the resource accounts. This is a list of resource account GUIDs. + +Only Call Queue managed by a Teams Channel will be able to use this feature. For more information, refer to [Manage your support Call Queue in Teams](https://support.microsoft.com/office/manage-your-support-call-queue-in-teams-9f07dabe-91c6-4a9b-a545-8ffdddd2504e). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowDisconnectTextToSpeechPrompt +The OverflowDisconnectTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being disconnected due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowDisconnectAudioFilePrompt +The OverflowDisconnectAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being disconnected due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPersonTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectPersonTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person in the organization due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPersonAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectPersonAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person in the organization due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoiceAppTextToSpeechPrompt +The OverflowRedirectVoiceAppsTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a voice application due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoiceAppAudioFilePrompt +The OverflowRedirectVoiceAppAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a voice application due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPhoneNumberTextToSpeechPrompt +The OverflowRedirectPhoneNumberTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to an external PSTN phone number due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPhoneNumberAudioFilePrompt +The OverflowRedirectPhoneNumberAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to an external PSTN phone number due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoicemailTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person's voicemail due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoicemailAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectVoiceMailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person's voicemail due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowSharedVoicemailTextToSpeechPrompt +The OverflowSharedVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is to be played as a greeting to the caller when transferred to shared voicemail on overflow. This parameter becomes a required parameter when OverflowAction is SharedVoicemail and OverflowSharedVoicemailAudioFilePrompt is null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowSharedVoicemailAudioFilePrompt +The OverflowSharedVoicemailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is to be played as a greeting to the caller when transferred to shared voicemail on overflow. This parameter becomes a required parameter when OverflowAction is SharedVoicemail and OverflowSharedVoicemailTextToSpeechPrompt is null. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOverflowSharedVoicemailTranscription +The EnableOverflowSharedVoicemailTranscription parameter is used to turn on transcription for voicemails left by a caller on overflow. This parameter is only applicable when OverflowAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOverflowSharedVoicemailSystemPromptSuppression +The EnableOverflowSharedVoicemailSystemPromptSuppress parameter is used to turn off the default voicemail system prompts. This parameter is only applicable when OverflowAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutDisconnectTextToSpeechPrompt +The TimeoutDisconnectTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being disconnected due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutDisconnectAudioFilePrompt +The TimeoutDisconnectAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being disconnected due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPersonTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectPersonTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person in the organization due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPersonAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectPersonAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person in the organization due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoiceAppTextToSpeechPrompt +The TimeoutRedirectVoiceAppsTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a voice application due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoiceAppAudioFilePrompt +The TimeoutRedirectVoiceAppAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a voice application due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPhoneNumberTextToSpeechPrompt +The TimeoutRedirectPhoneNumberTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to an external PSTN phone number due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPhoneNumberAudioFilePrompt +The TimeoutRedirectPhoneNumberAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to an external PSTN phone number due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoicemailTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person's voicemail due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoicemailAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectVoiceMailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person's voicemail due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutSharedVoicemailTextToSpeechPrompt +The TimeoutSharedVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is to be played as a greeting to the caller when transferred to shared voicemail on timeout. This parameter becomes a required parameter when TimeoutAction is SharedVoicemail and TimeoutSharedVoicemailAudioFilePrompt is null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutSharedVoicemailAudioFilePrompt +The TimeoutSharedVoicemailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is to be played as a greeting to the caller when transferred to shared voicemail on timeout. This parameter becomes a required parameter when TimeoutAction is SharedVoicemail and TimeoutSharedVoicemailTextToSpeechPrompt is null. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTimeoutSharedVoicemailTranscription +The EnableTimeoutSharedVoicemailTranscription parameter is used to turn on transcription for voicemails left by a caller on timeout. This parameter is only applicable when TimeoutAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTimeoutSharedVoicemailSystemPromptSuppression +The EnableTimeoutSharedVoicemailSystemPromptSuppress parameter is used to turn off the default voicemail system prompts. This parameter is only applicable when OverflowAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentDisconnectTextToSpeechPrompt +The NoAgentDisconnectTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being disconnected due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentDisconnectAudioFilePrompt +The NoAgentDisconnectAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being disconnected due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPersonTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectPersonTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person in the organization due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPersonAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectPersonAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person in the organization due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoiceAppTextToSpeechPrompt +The NoAgentRedirectVoiceAppsTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a voice application due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoiceAppAudioFilePrompt +The NoAgentRedirectVoiceAppAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a voice application due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPhoneNumberTextToSpeechPrompt +The NoAgentRedirectPhoneNumberTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to an external PSTN phone number due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPhoneNumberAudioFilePrompt +The NoAgentRedirectPhoneNumberAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to an external PSTN phone number due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoicemailTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person's voicemail due to no agent. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoicemailAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectVoiceMailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person's voicemail due to no agent. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentSharedVoicemailTextToSpeechPrompt +The NoAgentSharedVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is to be played as a greeting to the caller when transferred to shared voicemail on no agents. This parameter becomes a required parameter when NoAgentAction is SharedVoicemail and NoAgentSharedVoicemailAudioFilePrompt is null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentSharedVoicemailAudioFilePrompt +The NoAgentSharedVoicemailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is to be played as a greeting to the caller when transferred to shared voicemail on no agents. This parameter becomes a required parameter when NoAgentAction is SharedVoicemail and NoAgentSharedVoicemailTextToSpeechPrompt is null. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableNoAgentSharedVoicemailTranscription +The EnableNoAgentSharedVoicemailTranscription parameter is used to turn on transcription for voicemails left by a caller on no agents. This parameter is only applicable when NoAgentAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableNoAgentSharedVoicemailSystemPromptSuppression +The EnableNoAgentSharedVoicemailSystemPromptSuppress parameter is used to turn off the default voicemail system prompts. This parameter is only applicable when NoAgentAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelId +Id of the channel to connect a call queue to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelUserObjectId +Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). This is the GUID of one of the owners of the team the channels belongs to. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftsTeamId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +Id of the Team containing the Scheduling Group to connect a call queue to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftsSchedulingGroupId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +Id of the Scheduling Group to connect a call queue to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuthorizedUsers +This is a list of GUIDs for users who are authorized to make changes to this call queue. The users must also have a TeamsVoiceApplications policy assigned. The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HideAuthorizedUsers +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +This is a list of GUIDs of authorized users who should not appear on the list of supervisors for the agents who are members of this queue. The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WelcomeTextToSpeechPrompt +This parameter indicates which Text-to-Speech (TTS) prompt is played when callers are connected to the Call Queue. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsCallbackEnabled + +The IsCallbackEnabled parameter is used to turn on/off callback. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackRequestDtmf + +The DTMF touch-tone key the caller will be told to press to select callback. The CallbackRequestDtmf must be set to one of the following values: + +- Tone0 to Tone9 - Corresponds to DTMF tones from 0 to 9. +- ToneStar - Corresponds to DTMF tone *. +- TonePound - Corresponds to DTMF tone #. + +This parameter becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WaitTimeBeforeOfferingCallbackInSecond + +The number of seconds a call must wait before becoming eligible for callback. This condition applies to calls at the front of the call queue. Set to null ($null) to disable this condition. + +At least one of `-WaitTimeBeforeOfferingCallbackInSecond`, `-NumberOfCallsInQueueBeforeOfferingCallback`, or `-CallToAgentRatioThresholdBeforeOfferingCallback` must be set to a value other than null when `-IsCallbackEnabled` is `True`. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberOfCallsInQueueBeforeOfferingCallback + +The number of calls in queue before a call becomes eligible for callback. This condition applies to calls arriving at the call queue. Set to null ($null) to disable this condition. + +At least one of `-WaitTimeBeforeOfferingCallbackInSecond`, `-NumberOfCallsInQueueBeforeOfferingCallback`, or `-CallToAgentRatioThresholdBeforeOfferingCallback` must be set to a value other than null when `-IsCallbackEnabled` is `True`. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallToAgentRatioThresholdBeforeOfferingCallback + +The ratio of calls to agents that must be in queue before a call becomes eligible for callback. This condition applies to calls arriving at the call queue. Minimum value of 1. Set to null ($null) to disable this condition. + +At least one of `-WaitTimeBeforeOfferingCallbackInSecond`, `-NumberOfCallsInQueueBeforeOfferingCallback`, or `-CallToAgentRatioThresholdBeforeOfferingCallback` must be set to a value other than null when `-IsCallbackEnabled` is `True`. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackOfferAudioFilePromptResourceId + +The CallbackOfferAudioFilePromptResourceId parameter indicates the unique identifier for the Audio file prompt which is played to calls that are eligible for callback. This message should tell callers which DTMF touch-tone key (CallbackRequestDtmf) to press to select callback. This parameter, or `-CallbackOfferTextToSpeechPrompt`, becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackOfferTextToSpeechPrompt + +The CallbackOfferTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to calls that are eligible for callback. This message should tell callers which DTMF touch-tone key (CallbackRequestDtmf) to press to select callback. This parameter, or `-CallbackOfferAudioFilePromptResourceId`, becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackEmailNotificationTarget + +The CallbackEmailNotificationTarget parameter must be set to a group ID (Microsoft 365, Distribution list, or Mail-enabled security) that will receive notification if a callback times out of the call queue or can't be completed for some other reason. This parameter becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceLevelThresholdResponseTimeInSecond + +The target number of seconds calls should be answered in. This number is used to calculate the call queue service level percentage. + +A value of `$null` indicates that a service level percentage will not be calculated for this call queue. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceRecordingForCallQueueTemplateId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The ComplianceRecordingForCallQueueTemplateId parameter indicates a list of up to 2 Compliance Recording for Call Queue templates to apply to the call queue. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TextAnnouncementForCR +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TextAnnouncementForCR parameter indicates the custom Text-to-Speech (TTS) prompt which is played to callers when compliance recording for call queues is enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAudioFileAnnouncementForCR +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The CustomAudioFileAnnouncementForCR parameter indicates the unique identifier for the Audio file prompt which is played to callers when compliance recording for call queues is enabled. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TextAnnouncementForCRFailure +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TextAnnouncementForCRFailure parameter indicates the custom Text-to-Speech (TTS) prompt which is played to callers if the compliance recording for call queue bot is unable to join or drops from the call. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAudioFileAnnouncementForCRFailure +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The CustomAudioFileAnnouncementForCRFailure parameter indicates the unique identifier for the Audio file prompt which is played to callers if the compliance recording for call queue bot is unable to join or drops from the call. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharedCallQueueHistoryTemplateId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The SharedCallQueueHistoryTemplateId parameter indicates the Shared Call Queue History template to apply to the call queue. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShouldOverwriteCallableChannelProperty + +A Teams Channel can only be linked to one Call Queue at a time. To force reassignment of the Teams Channel to a new Call Queue, set this to $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS +[Create a Phone System Call Queue](https://support.office.com/article/Create-a-Phone-System-call-queue-67ccda94-1210-43fb-a25b-7b9785f8a061) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + +[New-CsComplianceRecordingForCallQueueTemplate](./New-CsComplianceRecordingForCallQueueTemplate.md) + +[Get-CsComplianceRecordingForCallQueueTemplate](./Get-CsComplianceRecordingForCallQueueTemplate.md) + +[Set-CsComplianceRecordingForCallQueueTemplate](./Set-CsComplianceRecordingForCallQueueTemplate.md) + +[Remove-CsComplianceRecordingForCallQueueTemplate](./Remove-CsComplianceRecordingForCallQueueTemplate.md) diff --git a/teams/teams-ps/teams/New-CsCallingLineIdentity.md b/teams/teams-ps/teams/New-CsCallingLineIdentity.md new file mode 100644 index 0000000000..93e83c74a1 --- /dev/null +++ b/teams/teams-ps/teams/New-CsCallingLineIdentity.md @@ -0,0 +1,237 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-cscallinglineidentity +applicable: Microsoft Teams +title: New-CsCallingLineIdentity +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsCallingLineIdentity + +## SYNOPSIS +Use the New-CsCallingLineIdentity cmdlet to create a new Caller ID policy for your organization. + +## SYNTAX + +``` +New-CsCallingLineIdentity [-Identity] <string> [-BlockIncomingPstnCallerID <bool>] [-CallingIDSubstitute <string>] [-CompanyName <string>] +[-Description <string>] [-EnableUserOverride <bool>] [-ResourceAccount <string>] +[-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You can either change or block the Caller ID (also called a Calling Line ID) for a user. By default, the Teams or Skype for Business Online user's phone number can be seen when that user makes a call to a PSTN phone, or when a call comes in. You can create a Caller ID policy to provide an alternate displayed number, or to block any number from being displayed. + +Note: +- Identity must be unique. +- If CallerIdSubstitute is given as "Resource", then ResourceAccount cannot be empty. + +## EXAMPLES + +### Example 1 +``` +New-CsCallingLineIdentity -Identity Anonymous -Description "anonymous policy" -CallingIDSubstitute Anonymous -EnableUserOverride $false +``` + +This example creates a new Caller ID policy that sets the Caller ID to Anonymous. + +### Example 2 +``` +New-CsCallingLineIdentity -Identity BlockIncomingCLID -BlockIncomingPstnCallerID $true +``` + +This example creates a new Caller ID policy that blocks the incoming Caller ID. + +### Example 3 +``` +$ObjId = (Get-CsOnlineApplicationInstance -Identity dkcq@contoso.com).ObjectId +New-CsCallingLineIdentity -Identity DKCQ -CallingIDSubstitute Resource -EnableUserOverride $false -ResourceAccount $ObjId -CompanyName "Contoso" +``` + +This example creates a new Caller ID policy that sets the Caller ID to the phone number of the specified resource account and sets the Calling party name to Contoso + +### Example 4 +``` +New-CsCallingLineIdentity -Identity AllowAnonymousForUsers -EnableUserOverride $true +``` + +This example creates a new Caller ID policy that allows Teams users to make anonymous calls. + +## PARAMETERS + +### -Identity +The Identity parameter identifies the Caller ID policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockIncomingPstnCallerID +The BlockIncomingPstnCallerID switch determines whether to block the incoming Caller ID. The default value is false. + +The BlockIncomingPstnCallerID switch is specific to incoming calls from a PSTN caller to a user. If this is set to True and if this policy is assigned to a user, then Caller ID for incoming calls is suppressed/anonymous. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallingIDSubstitute +The CallingIDSubstitute parameter lets you specify an alternate Caller ID. The default value is LineUri. Supported values are Anonymous, LineUri, and Resource. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompanyName +This parameter sets the Calling party name (typically referred to as CNAM) on the outgoing PSTN call. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter briefly describes the Caller ID policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUserOverride +The EnableUserOverride parameter gives Microsoft Teams users the option under Settings and Calls to hide their phone number when making outgoing calls. The CallerID will be Anonymous. + +If CallingIDSubstitute is set to Anonymous, the EnableUserOverride parameter has no effect, and the caller ID is always set to Anonymous. + +EnableUserOverride has precedence over other settings in the policy unless substitution is set to Anonymous. For example, assume the policy instance has substitution using a resource account and EnableUserOverride is set and enabled by the user. In this case, the outbound caller ID will be blocked and Anonymous will be used. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResourceAccount +This parameter specifies the ObjectId of a resource account/online application instance used for Teams Auto Attendant or Call Queue. The outgoing PSTN call will use the phone number defined on the resource account as caller id. For more information about resource accounts please see https://learn.microsoft.com/microsoftteams/manage-resource-accounts + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES + +## RELATED LINKS + +[Get-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/get-cscallinglineidentity) + +[Grant-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/grant-cscallinglineidentity) + +[Remove-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/remove-cscallinglineidentity) + +[Set-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/set-cscallinglineidentity) diff --git a/teams/teams-ps/teams/New-CsCloudCallDataConnection.md b/teams/teams-ps/teams/New-CsCloudCallDataConnection.md new file mode 100644 index 0000000000..772f8f1d49 --- /dev/null +++ b/teams/teams-ps/teams/New-CsCloudCallDataConnection.md @@ -0,0 +1,62 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: New-CsCloudCallDataConnection +online version: https://learn.microsoft.com/powershell/module/teams/new-cscloudcalldataconnection +schema: 2.0.0 +author: 2012ucp1544 +ms.author: uditagrawal +ms.reviewer: pbafna +manager: subadjat + +--- + +# New-CsCloudCallDataConnection + +## SYNOPSIS +This cmdlet creates an online call data connection. + +## SYNTAX + +```powershell +New-CsCloudCallDataConnection [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates an online call data connection. If you get an error that the connection already exists, it means that the call data connection already exists for your tenant. In this case, run Get-CsCloudCallDataConnection. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsCloudCallDataConnection + +Token +----- +00000000-0000-0000-0000-000000000000 +``` + +Returns a token value, which is needed when configuring your on-premises environment with Set-CsCloudCallDataConnector. + +## 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +The New-CsCloudCallDataConnection cmdlet is only supported in commercial environments from Teams PowerShell Module versions 4.6.0 or later. + +## RELATED LINKS + +[Configure Call Data Connector](https://learn.microsoft.com/skypeforbusiness/hybrid/configure-call-data-connector) +[Get-CsCloudCallDataConnection](https://learn.microsoft.com/powershell/module/teams/get-cscloudcalldataconnection) diff --git a/teams/teams-ps/teams/New-CsComplianceRecordingForCallQueueTemplate.md b/teams/teams-ps/teams/New-CsComplianceRecordingForCallQueueTemplate.md new file mode 100644 index 0000000000..f98067448d --- /dev/null +++ b/teams/teams-ps/teams/New-CsComplianceRecordingForCallQueueTemplate.md @@ -0,0 +1,182 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/New-CsComplianceRecordingForCallQueueTemplate +applicable: Microsoft Teams +title: New-CsComplianceRecordingForCallQueueTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsComplianceRecordingForCallQueueTemplate + +## SYNTAX + +```powershell +New-CsComplianceRecordingForCallQueueTemplate -Name <String> -Description <String> -BotId <String> [-RequiredDuringCall <Boolean>] [-RequiredBeforeCall <Boolean>] [-CurrentInvitationCount <Int32>] [-PairedApplication <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Use the New-CsComplianceRecordingForCallQueueTemplate cmdlet to create a Compliance Recording for Call Queues template. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +New-CsComplianceRecordingForCallQueueTemplate -Name "Customer Service" -Description "Required before/during call" -BotId 14732826-8206-42e3-b51e-6693e2abb698 -RequiredDuringCall $true -RequiredBeforeCall $true +``` + +This example creates a new Compliance Recording for Call Queue template. + +## PARAMETERS + +### -Name +The name of the compliance recording for call queue template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +A description for the compliance recording for call queues template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BotId +The Id of the compliance recording for call queue bot to invite. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredDuringCall +Indicates if the compliance recording for call queues bot must remain part of the call. +*Strict recording* - if the bot leaves the call, the call will end. + +```yaml +Type: System.Booleen +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredBeforeCall +Indicates if the compliance recording for call queues bot must be able to join the call. +*Strict recording* - if the bot can't join the call, the call will end. + +```yaml +Type: System.Booleen +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConcurrentInvitationCount +The number of concurrent invitations to send to the compliance recording for call queue bot. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 1 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PairedApplication +The PairedApplication parameter specifies the paired application for the call queue. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[Get-CsComplianceRecordingForCallQueueTemplate](./Get-CsComplianceRecordingForCallQueueTemplate.md) + +[Set-CsComplianceRecordingForCallQueueTemplate](./Set-CsComplianceRecordingForCallQueueTemplate.md) + +[Remove-CsComplianceRecordingForCallQueueTemplate](./Remove-CsComplianceRecordingForCallQueueTemplate.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + + + diff --git a/teams/teams-ps/teams/New-CsCustomPolicyPackage.md b/teams/teams-ps/teams/New-CsCustomPolicyPackage.md new file mode 100644 index 0000000000..bf6a5dfc6b --- /dev/null +++ b/teams/teams-ps/teams/New-CsCustomPolicyPackage.md @@ -0,0 +1,108 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: New-CsCustomPolicyPackage +author: sunguchuan +ms.author: gucsun +manager: dasosby +online version: https://learn.microsoft.com/powershell/module/teams/new-cscustompolicypackage +schema: 2.0.0 +--- + +# New-CsCustomPolicyPackage + +## SYNOPSIS + +**Note:** This cmdlet is currently in private preview. + +This cmdlet creates a custom policy package. + +## SYNTAX + +``` +New-CsCustomPolicyPackage -Identity <String> -PolicyList <String[]> [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet creates a custom policy package. It allows the admin to create their own policy packages for the tenant. For more information on policy packages and the policy types available, see [Managing policy packages in Teams](https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsCustomPolicyPackage -Identity "MyPackage" -PolicyList "TeamsMessagingPolicy, MyMessagingPolicy" +``` + +Creates a custom package named "MyPackage" with one policy in the package: a messaging policy of name "MyMessagingPolicy". +### Example 2 +```powershell +PS C:\> New-CsCustomPolicyPackage -Identity "MyPackage" -PolicyList "TeamsMessagingPolicy, MyMessagingPolicy", "TeamsMeetingPolicy, MyMeetingPolicy" -Description "My package" +``` + +Creates a custom package named "MyPackage" with description "My package" and two policies in the package: a messaging policy of name "MyMessagingPolicy" and a meeting policy of name "MyMeetingPolicy". + +## PARAMETERS + +### -Identity + +The name of the custom package. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyList + +A list of one or more policies to be added in the package. To specify the policy list, follow this format: "\<PolicyType\>, \<PolicyName\>". Delimiters of ' ', '.', ':', '\t' are also acceptable. Supported policy types are listed [here](https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages#what-is-a-policy-package). To get the list of available policy names on your tenant, use the skypeforbusiness module and refer to cmdlets such as [Get-CsTeamsMeetingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingpolicy) and [Get-CsTeamsMessagingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmessagingpolicy). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +The description of the custom package. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Update-CsCustomPolicyPackage](https://learn.microsoft.com/powershell/module/teams/update-cscustompolicypackage) + +[Remove-CsCustomPolicyPackage](https://learn.microsoft.com/powershell/module/teams/remove-cscustompolicypackage) diff --git a/skype/skype-ps/skype/New-CsEdgeAllowAllKnownDomains.md b/teams/teams-ps/teams/New-CsEdgeAllowAllKnownDomains.md similarity index 80% rename from skype/skype-ps/skype/New-CsEdgeAllowAllKnownDomains.md rename to teams/teams-ps/teams/New-CsEdgeAllowAllKnownDomains.md index f4b27786b1..2aef1fe8ea 100644 --- a/skype/skype-ps/skype/New-CsEdgeAllowAllKnownDomains.md +++ b/teams/teams-ps/teams/New-CsEdgeAllowAllKnownDomains.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csedgeallowallknowndomains -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csedgeallowallknowndomains +applicable: Microsoft Teams title: New-CsEdgeAllowAllKnownDomains schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsEdgeAllowAllKnownDomains @@ -18,7 +18,7 @@ Enables Skype for Business Online federation with all domains except for those d ## SYNTAX ``` -New-CsEdgeAllowAllKnownDomains [-AsJob] [<CommonParameters>] +New-CsEdgeAllowAllKnownDomains [<CommonParameters>] ``` ## DESCRIPTION @@ -51,7 +51,7 @@ To configure federation with all known domains, use a set of commands similar to ## EXAMPLES -### -------------------------- Example 1 -------------------------- +### -------------------------- Example 1 -------------------------- ``` $x = New-CsEdgeAllowAllKnownDomains @@ -62,44 +62,24 @@ The two commands shown in Example 1 configure the federation settings for the cu To do this, the first command in the example uses the New-CsEdgeAllowAllKnownDomains cmdlet to create an instance of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.AllowAllKnownDomains object; this instance is stored in a variable named $x. In the second command, the Set-CsTenantFederationConfiguration cmdlet is called along with the AllowedDomains parameter; using $x as the parameter value configures the federation settings to allow all known domains. - - ## PARAMETERS -### -AsJob -{{Fill AsJob Description}} - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS -### +### Input types None. The New-CsEdgeAllowAllKnownDomains cmdlet does not accept pipelined input. ## OUTPUTS -### +### Output types The New-CsEdgeAllowAllKnownDomains cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.AllowAllKnownDomains object. ## NOTES ## RELATED LINKS -[Set-CsTenantFederationConfiguration](Set-CsTenantFederationConfiguration.md) - - +[Set-CsTenantFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-cstenantfederationconfiguration) diff --git a/skype/skype-ps/skype/New-CsEdgeAllowList.md b/teams/teams-ps/teams/New-CsEdgeAllowList.md similarity index 78% rename from skype/skype-ps/skype/New-CsEdgeAllowList.md rename to teams/teams-ps/teams/New-CsEdgeAllowList.md index bc3aaf9d7b..051c806683 100644 --- a/skype/skype-ps/skype/New-CsEdgeAllowList.md +++ b/teams/teams-ps/teams/New-CsEdgeAllowList.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csedgeallowlist -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csedgeallowlist +applicable: Microsoft Teams title: New-CsEdgeAllowList schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsEdgeAllowList @@ -56,7 +56,7 @@ When this command finishes executing, users will only be allowed to communicate ## EXAMPLES -### -------------------------- Example 1 -------------------------- +### -------------------------- Example 1 -------------------------- ``` $x = New-CsEdgeDomainPattern -Domain "fabrikam.com" @@ -72,8 +72,7 @@ After the domain object has been created, the `New-CsEdgeAllowList` cmdlet is us With the allowed domain list created, the final command in the example can then use the `Set-CsTenantFederationConfiguration` cmdlet to configure fabrikam.com as the only domain on the allowed domain list for the current tenant. - -### -------------------------- Example 2 -------------------------- +### -------------------------- Example 2 -------------------------- ``` $x = New-CsEdgeDomainPattern -Domain "contoso.com" @@ -88,7 +87,7 @@ Example 2 shows how you can add multiple domains to an allowed domains list. This is done by calling the `New-CsEdgeDomainPattern` cmdlet multiple times (one for each domain to be added to the list), and storing the resulting domain objects in separate variables. Each of those variables can then be added to the allow list created by the `New-CsEdgeAllowList` cmdlet simply by using the AllowedDomain parameter and separating the variables name by using commas. -### -------------------------- Example 3 -------------------------- +### -------------------------- Example 3 -------------------------- ``` $newAllowList = New-CsEdgeAllowList -AllowedDomain $Null @@ -112,28 +111,8 @@ For example: ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -AsJob -Indicates that this cmdlet runs as a background job. - -When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. - -For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6). - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -143,23 +122,23 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS -### +### Input types None. The `New-CsEdgeAllowList` cmdlet does not accept pipelined input. ## OUTPUTS -### +### Output types The `New-CsEdgeAllowList` cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.AllowList object. ## NOTES ## RELATED LINKS -[New-CsEdgeDomainPattern](New-CsEdgeDomainPattern.md) +[New-CsEdgeDomainPattern](https://learn.microsoft.com/powershell/module/teams/new-csedgedomainpattern) -[Set-CsTenantFederationConfiguration](Set-CsTenantFederationConfiguration.md) +[Set-CsTenantFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-cstenantfederationconfiguration) diff --git a/teams/teams-ps/teams/New-CsEdgeDomainPattern.md b/teams/teams-ps/teams/New-CsEdgeDomainPattern.md new file mode 100644 index 0000000000..5bc669bc16 --- /dev/null +++ b/teams/teams-ps/teams/New-CsEdgeDomainPattern.md @@ -0,0 +1,103 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csedgedomainpattern +applicable: Microsoft Teams +title: New-CsEdgeDomainPattern +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsEdgeDomainPattern + +## SYNOPSIS +Used to specify a domain that will be added or removed from the set of domains enabled for federation or the set of domains disabled for federation. +You must use the New-CsEdgeDomainPattern cmdlet when modifying the allowed or blocked domain lists. +String values (such as "fabrikam.com") cannot be directly passed to the cmdlets used to manage either of these lists. + +## SYNTAX + +``` +New-CsEdgeDomainPattern -Domain <String> [<CommonParameters>] +``` + +## DESCRIPTION +Federation is a service that enables users to exchange IM and presence information with users from other domains. +With Skype for Business Online, administrators can use the federation configuration settings to govern: + +Whether or not users can communicate with people from other domains and, if so, which domains they are allowed to communicate with. + +Whether or not users can communicate with people who have accounts on public IM and presence providers such as Windows Live, AOL, and Yahoo. + +Federation is managed, in part, by using allowed domain and blocked domain lists. +The allowed domain list specifies the domains that users are allowed to communicate with; the blocked domain list specifies the domains that users are not allowed to communicate with. +By default, users can communicate with any domain that does not appear on the blocked list. +However, administrators can modify this default setting and limit communication to domains that are on the allowed domains list. + +Skype for Business Online does not allow you to directly modify the allowed list or the blocked list; for example, you cannot use a command similar to this one, which passes a string value representing a domain name to the blocked domains list: + +`Set-CsTenantFederationConfiguration -BlockedDomains "fabrikam.com"` + +Instead, you must create a domain object by using the New-CsEdgeDomainPattern cmdlet, store that domain object in a variable (in this example, $x), then pass the variable name to the blocked domains list: + +`$x = New-CsEdgeDomainPattern -Domain "fabrikam.com"` + +`Set-CsTenantFederationConfiguration -BlockedDomains $x` + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" + +Set-CsTenantFederationConfiguration -BlockedDomains $x +``` + +Example 1 demonstrates how you can assign a single domain to the blocked domains list for a specified tenant. +To do this, the first command in the example creates a domain object for the domain fabrikam.com; this is done by calling the New-CsEdgeDomainPattern cmdlet and by saving the resulting domain object in a variable named $x. +The second command then uses the Set-CsTenantFederationConfiguration cmdlet and the BlockedDomains parameter to configure fabrikam.com as the only domain blocked by the current tenant. + +## PARAMETERS + +### -Domain +Fully qualified domain name of the domain to be added to the allow list. +For example: + +`-Domain "fabrikam.com"` + +Note that you cannot use wildcards when specifying a domain name. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +None. +The New-CsEdgeDomainPattern cmdlet does not accept pipelined input. + +## OUTPUTS + +### Output types +The New-CsEdgeDomainPattern cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.DomainPattern object. + +## NOTES + +## RELATED LINKS + +[Set-CsTenantFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-cstenantfederationconfiguration) diff --git a/teams/teams-ps/teams/New-CsExternalAccessPolicy.md b/teams/teams-ps/teams/New-CsExternalAccessPolicy.md new file mode 100644 index 0000000000..5534e03ef3 --- /dev/null +++ b/teams/teams-ps/teams/New-CsExternalAccessPolicy.md @@ -0,0 +1,533 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csexternalaccesspolicy +applicable: Microsoft Teams +title: New-CsExternalAccessPolicy +schema: 2.0.0 +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# New-CsExternalAccessPolicy + +## SYNOPSIS + +Enables you to create a new external access policy. + +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype; and, 5) communicate with people who are using Teams with an account that's not managed by an organization. + +This cmdlet was introduced in Lync Server 2010. + +For information about external access in Microsoft Teams, see [Manage external access in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-external-access) and [Teams and Skype interoperability](https://learn.microsoft.com/microsoftteams/teams-skype-interop) for specific details. + +## SYNTAX + +```powershell +New-CsExternalAccessPolicy [-Identity] <XdsIdentity> + [-AllowedExternalDomains <List>] + [-BlockedExternalDomains <List>] + [-CommunicationWithExternalOrgs <String>] + [-Confirm] + [-Description <String>] + [-EnableAcsFederationAccess <Boolean>] + [-EnableFederationAccess <Boolean>] + [-EnableOutsideAccess <Boolean>] + [-EnablePublicCloudAudioVideoAccess <Boolean>] + [-EnableTeamsConsumerAccess <Boolean>] + [-EnableTeamsConsumerInbound <Boolean>] + [-EnableTeamsSmsAccess <Boolean>] + [-EnableXmppAccess <Boolean>] + [-FederatedBilateralChats <Boolean>] + [-Force] + [-InMemory] + [-RestrictTeamsConsumerAccessToExternalUserProfiles <Boolean>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION + +When you install Skype for Business Server your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with other people who have SIP accounts in your Active Directory Domain Services. +In addition, users are not allowed to access Skype for Business Server over the Internet; instead, they must be logged on to your internal network before they will be able to log on to Skype for Business Server. + +That might be sufficient to meet your communication needs. +If it doesn't meet your needs you can use external access policies to extend the ability of your users to communicate and collaborate. +External access policies can grant (or revoke) the ability of your users to do any or all of the following: + +1. Communicate with people who have SIP accounts with a federated organization. +Note that enabling federation alone will not provide users with this capability. +Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. + +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). this policy setting only applies if acs federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration). + +3. Access Skype for Business Server over the Internet, without having to first log on to your internal network. +This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. + +4. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. + +5. (Microsoft Teams Only) Communicate with people who are using Teams with an account that's not managed by an organization. This policy only applies if Teams Consumer Federation has been enabled at the tenant level using the cmdlet [Set-CsTenantFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-cstenantfederationconfiguration) or Teams Admin Center under the External Access setting. + +When you install Skype for Business Server, a global external access policy is automatically created for you. +In addition to the global policy, you can also create custom external access policies at either the site or the per-user scope. +If you create an external access policy at the site scope, that policy will automatically be assigned to the site upon creation. +If you create an external access policy at the per-user scope, that policy will be created but will not be assigned to any users. +To assign the policy to a user or group of users, use the Grant-CsExternalAccessPolicy cmdlet. + +New external access policies can be created by using the New-CsExternalAccessPolicy cmdlet. +Note that these policies can only be created at the site or the per-user scope; you cannot create a new policy at the global scope. +In addition, you can have only one external access policy per site: if the Redmond site already has been assigned an external access policy you cannot create a second policy for the site. + +The following parameters are not applicable to Skype for Business Online/Microsoft Teams: Description, EnableXmppAccess, Force, Identity, InMemory, PipelineVariable, and Tenant + +## EXAMPLES + +### -------------------------- EXAMPLE 1 -------------------------- +``` +New-CsExternalAccessPolicy -Identity site:Redmond -EnableFederationAccess $True -EnableOutsideAccess $True +``` + +The command shown in Example 1 creates a new external access policy that has the Identity site:Redmond; upon creation, this policy will automatically be assigned to the Redmond site. +Note that this new policy sets both the EnableFederationAccess and the EnableOutsideAccess properties to True. + +### -------------------------- Example 2 ------------------------ +``` +Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $true +New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed -EnableAcsFederationAccess $false +``` + +In this example, the Global policy is updated to allow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation disabled and which can then be assigned to selected users for which Team-ACS federation will not be allowed. + +### -------------------------- Example 3 ------------------------ +``` +New-CsExternalAccessPolicy -Identity site:Redmond -EnableTeamsConsumerAccess $True -EnableTeamsConsumerInbound $False +``` + +The command shown in Example 3 creates a new external access policy that has the Identity site:Redmond; upon creation, this policy will automatically be assigned to the Redmond site. +Note that this new policy enables communication with people using Teams with an account that's not managed by an organization and limits this to only be initiated by people in your organization. This means that people using Teams with an account that's not managed by an organization will not be able to discover or start a conversation with people with this policy assigned. + +### -------------------------- EXAMPLE 4 -------------------------- +``` +$x = New-CsExternalAccessPolicy -Identity RedmondAccessPolicy -InMemory + +$x.EnableFederationAccess = $True + +$x.EnableOutsideAccess = $True + +Set-CsExternalAccessPolicy -Instance $x +``` + +Example 4 demonstrates the use of the InMemory parameter; this parameter enables you to create an in-memory-only instance of an external access policy. +After it has been created, you can modify the in-memory-only instance, then use the Set-CsExternalAccessPolicy cmdlet to transform the virtual policy into a real external access policy. + +To do this, the first command in the example uses the New-CsExternalAccessPolicy cmdlet and the InMemory parameter to create a virtual policy with the Identity RedmondAccessPolicy; this virtual policy is stored in a variable named $x. +The next three commands are used to modify two properties of the virtual policy: EnableFederationAccess and the EnableOutsideAccess. +Finally, the last command uses the Set-CsExternalAccessPolicy cmdlet to create an actual per-user external access policy with the Identity RedmondAccessPolicy. +If you do not call the Set-CsExternalAccessPolicy cmdlet, then the virtual policy will disappear as soon as you end your Windows PowerShell session or delete the variable $x. +Should that happen, an external access policy with the Identity RedmondAccessPolicy will never be created. + +### -------------------------- Example 5 ------------------------ +``` +New-CsExternalAccessPolicy -Identity GranularFederationExample -CommunicationWithExternalOrgs "AllowSpecificExternalDomains" -AllowedExternalDomains @("example1.com", "example2.com") +Set-CsTenantFederationConfiguration -CustomizeFederation $true +``` + +In this example, we create an ExternalAccessPolicy named "GranularFederationExample" that allows communication with specific external domains, namely `example1.com` and `example2.com`. The federation policy is set to restrict communication to only these allowed domains. + +## PARAMETERS + +### -Identity +Unique Identity to be assigned to the policy. New external access policies can be created at the site or per-user scope. + +To create a new site policy, use the prefix "site:" and the name of the site as your Identity. + +For example, use this syntax to create a new policy for the Redmond site: `-Identity site:Redmond.` + +To create a new per-user policy, use an Identity similar to this: `-Identity SalesAccessPolicy.` + +Note that you cannot create a new global policy; if you want to make changes to the global policy, use the Set-CsExternalAccessPolicy cmdlet instead. + +Likewise, you cannot create a new site or per-user policy if a policy with that Identity already exists. If you need to make changes to an existing policy, use the Set-CsExternalAccessPolicy cmdlet. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedExternalDomains +> [!NOTE] +> Please note that this parameter is in Private Preview. + +Specifies the external domains allowed to communicate with users assigned to this policy. This setting is applicable only when `CommunicationWithExternalOrgs` is configured to `AllowSpecificExternalDomains`. This setting can be modified only in custom policy. In Global (default) policy `CommunicationWithExternalOrgs` can only be set to `OrganizationDefault` and cannot be changed. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedExternalDomains +> [!NOTE] +> Please note that this parameter is in Private Preview. + +Specifies the external domains blocked from communicating with users assigned to this policy. This setting is applicable only when `CommunicationWithExternalOrgs` is configured to `BlockSpecificExternalDomains`. This setting can be modified only in custom policy. In Global (default) policy `CommunicationWithExternalOrgs` can only be set to `OrganizationDefault` and cannot be changed. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CommunicationWithExternalOrgs +> [!NOTE] +> Please note that this parameter is in Private Preview. + +Indicates how users assigned to the policy can communicate with external organizations (domains). This setting has 5 possible values: + +- OrganizationDefault: users follow the federation settings specified in `TenantFederationConfiguration`. This is the default value. +- AllowAllExternalDomains: users are allowed to communicate with all domains. +- AllowSpecificExternalDomains: users can communicate with external domains listed in `AllowedExternalDomains`. +- BlockSpecificExternalDomains: users are blocked from communicating with domains listed in `BlockedExternalDomains`. +- BlockAllExternalDomains: users cannot communicate with any external domains. + +The setting is only applicable when `EnableFederationAccess` is set to true. This setting can only be modified in custom policies. In the Global (default) policy, it is fixed to `OrganizationDefault` and cannot be changed. +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 +Required: False +Position: Named +Default value: OrganizationDefault +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany the policy. +For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableAcsFederationAccess +Indicates whether Teams meetings organized by the user can be joined by users of customer applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration. Additionally, Azure Communication Services users would be able to call Microsoft 365 users that have assigned policies with enabled federation. + +To enable for all users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to True. It can be disabled for selected users by assigning them a policy with federation disabled. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableFederationAccess +Indicates whether the user is allowed to communicate with people who have SIP accounts with a federated organization. +Read [Manage external access in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOutsideAccess +Indicates whether the user is allowed to connect to Skype for Business Server over the Internet, without logging on to the organization's internal network. +The default value is False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnablePublicCloudAudioVideoAccess +Indicates whether the user is allowed to conduct audio/video conversations with people who have SIP accounts with a public Internet connectivity provider such as MSN. +When set to False, audio and video options in Skype for Business Server will be disabled any time a user is communicating with a public Internet connectivity contact. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsConsumerAccess +(Microsoft Teams Only) Indicates whether the user is allowed to communicate with people who have who are using Teams with an account that's not managed by an organization. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsConsumerInbound +(Microsoft Teams Only) Indicates whether the user is allowed to be discoverable by people who are using Teams with an account that's not managed by an organization. It also controls if people who have who are using Teams with an account that's not managed by an organization can start the communication with the user. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsSmsAccess +Allows you to control whether users can have SMS text messaging capabilities within Teams. + +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableXmppAccess +Indicates whether the user is allowed to communicate with users who have SIP accounts with a federated XMPP (Extensible Messaging and Presence Protocol) partner. +The default value is False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FederatedBilateralChats +> [!NOTE] +> Please note that this parameter is in Private Preview. + +This setting enables bi-lateral chats for the users included in the messaging policy. + +Some organizations may want to restrict who users are able to message in Teams. While organizations have always been able to limit users' chats to only other internal users, organizations can now limit users' chat ability to only chat with other internal users and users in one other organization via the bilateral chat policy. + +Once external access and bilateral policy is set up, users with the policy can be in external group chats only with a maximum of two organizations. When they try to create a new external chat with users from more than two tenants or add a user from a third tenant to an existing external chat, a system message will be shown preventing this action. + +Users with bilateral policy applied are also removed from existing external group chats with more than two organizations. + +This policy doesn't apply to meetings, meeting chats, or channels. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might occur when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. +If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-\<cmdlet\>. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictTeamsConsumerAccessToExternalUserProfiles +Defines if a user is restricted to collaboration with Teams Consumer (TFL) user only in Extended Directory + +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the Skype for Business Online tenant account for whom the new external access policy is being created. +For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can return the tenant ID for each of your Skype for Business Online tenants by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +None. +The New-CsExternalAccessPolicy cmdlet does not accept pipelined input. + +## OUTPUTS + +### Output types +Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy object. + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/get-csexternalaccesspolicy) + +[Grant-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csexternalaccesspolicy) + +[Remove-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csexternalaccesspolicy) + +[Set-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/set-csexternalaccesspolicy) diff --git a/teams/teams-ps/teams/New-CsGroupPolicyAssignment.md b/teams/teams-ps/teams/New-CsGroupPolicyAssignment.md index 4fd03c6846..efbf01984f 100644 --- a/teams/teams-ps/teams/New-CsGroupPolicyAssignment.md +++ b/teams/teams-ps/teams/New-CsGroupPolicyAssignment.md @@ -1,41 +1,55 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment +online version: https://learn.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment +title: New-CsGroupPolicyAssignment schema: 2.0.0 author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsGroupPolicyAssignment ## SYNOPSIS -**Note:** This cmdlet is currently only available in private preview in the pre-release Teams PowerShell module. - -This cmdlet is used to assign a policy to a group. +This cmdlet is used to assign a policy to a security group or distribution list. ## SYNTAX ``` -New-CsGroupPolicyAssignment -GroupId <String> -PolicyType <String> -PolicyName <String> [-Rank <Int>] +New-CsGroupPolicyAssignment -GroupId <String> -PolicyType <String> -PolicyName <String> [-Rank <Int32>] + [-PassThru] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION -This cmdlet will assign a policy to a group. The policy assignment will then be propagated to the members of the group in accordance with the rules for group policy inheritance. If a user is directly assigned a policy of a specific type, then they will not inherit a policy of the same type from a group. If a user is a member of two or more groups that each have a policy of the same type assigned, then the user will inherit the policy based on the group policy assignment with the highest rank. +> [!NOTE] +> As of May 2023, group policy assignment functionality in Teams PowerShell Module has been extended to support all policy types used in Teams except for the following: +> - Teams App Permission Policy +> - Teams Network Roaming Policy +> - Teams Emergency Call Routing Policy +> - Teams Voice Applications Policy +> - Teams Upgrade Policy +> +> This cmdlet will be deprecated in the future. Going forward, group policy assignment can be performed by using the corresponding Grant-Cs[PolicyType] cmdlet with the '-Group' parameter. + +This cmdlet is used to assign a policy to a Microsoft 365 group, a security group, or a distribution list. When creating a group policy assignment, you must specify a rank, which indicates the precedence of that assignment relative to any other group assignments for the same policy type that may exist. The assignment will be applied to users in the group for any user that does not have a direct policy assignment, provided the user does not have any higher-ranking assignments from other groups for the same policy type. -The group policy assignment rank is set at the time a policy is being assigned to a group and is relative to other group policy assignments of the same policy type. For example, if there are two groups, each assigned a Teams Meeting policy, then one of the group assignments will be rank 1 while the other will be rank 2. +The group policy assignment rank is set at the time a policy is assigned to a group and it is relative to other group policy assignments of the same policy type. For example, if there are two groups, each assigned a Teams Meeting policy, then one of the group assignments will be rank 1 while the other will be rank 2. It's helpful to think of rank as determining the position of each policy assignment in an ordered list, from highest rank to lowest rank. In fact, rank can be specified as any number, but these are converted into sequential values 1, 2, 3, etc. with 1 being the highest rank. When assigning a policy to a group, set the rank to be the position in the list where you want the new group policy assignment to be. If a rank is not specified, the policy assignment will be given the lowest rank, corresponding to the end of the list. Assignments applied directly to a user will be treated like rank 0, having precedence over all assignments applied via groups. -It’s helpful to think of rank as determining the position of each policy assignment in an ordered list, from highest rank to lowest rank. In fact, rank can be specified as any number, but these are converted into sequential values 1, 2, 3, etc. with 1 being the highest rank. When assigning a policy to a group, set the rank to be the position in the list where you want the new group policy assignment to be. If a rank is not specified, the policy assignment will be given the lowest rank, corresponding to the end of the list. +Once a group policy assignment is created, the policy assignment will be propagated to the members of the group, including users that are added to the group after the assignment was created. Propagation time of the policy assignments to members of the group varies based on the number of users in the group. Propagation time for subsequent group membership changes also varies based on the number of users being added or removed from the group. For large groups, propagation to all members may take 24 hours or more. When using group policy assignment, the recommended maximum group membership size is 50,000 users per group. -Group policy assignment is currently limited to the following policy types: -TeamsCallingPolicy, TeamsCallParkPolicy, TeamsChannelPolicy, TeamsEducationAssignmentsAppPolicy, TeamsMeetingBroadcastPolicy, TeamsMeetingPolicy, TeamsMessagingPolicy +> [!NOTE] +> - A given policy type can be assigned to at most 64 groups, across policy instances for that type. +> - Policy assignments are only propagated to users that are direct members of the group; the assignments are not propagated to members of nested groups. +> - Direct user assignments of policy take precedence over any group policy assignments for a given policy type. Group PolicyPolicy assignments only take effect to a user if that user does not have a direct policy assignment. +> - Get-CsOnlineUser only shows *direct* assignments of policy. It does not show the effect of group policy assignments. To view a specific user's effective policy, use `Get-CsUserPolicyAssignment`. This cmdlet shows whether the effective policy is from a direct assignment or from a group, as well as the ranked order of each group policy assignment in the case where a user is a member of more than 1 group with a group policy assignment of the same policy type. For example, to view all TeamsMeetingPolicy assignments for a given user, $user, run the following powershell cmdlet: `Get-CsUserPolicyAssignment -Identity $user -PolicyType TeamsMeetingPolicy|select -ExpandProperty PolicySource`. For details, see [Get-CsUserPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicyassignment). +> - Group policy assignment is currently not available in the Microsoft 365 DoD deployment. ## EXAMPLES ### Example 1 -In this example, a policy is assigned to a group specified by object id. +In this example, a policy is assigned to a group specified by its object id. ``` New-CsGroupPolicyAssignment -GroupId d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 -PolicyType TeamsMeetingPolicy -PolicyName AllOn -Rank 1 @@ -62,7 +76,7 @@ d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 TeamsMeetingPolicy AllOn 1 10/29/20 ``` ### Example 3 -In this example, the policy assignment rank is set to 2. The current rank 2 policy assignment of the same type will be updated to rank 3. +In this example, the policy assignment rank is set to 2. The current rank 2 policy assignment of the same type will be updated to rank 3. ``` Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy @@ -90,7 +104,7 @@ The ID of a batch policy assignment operation. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -101,11 +115,11 @@ Accept wildcard characters: False ``` ### -PolicyType -The type of the policy to be assigned. +The type of policy to be assigned. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -120,7 +134,7 @@ The name of the policy to be assigned. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -135,7 +149,7 @@ The rank of the policy assignment, relative to other group policy assignments fo ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: False @@ -145,9 +159,54 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PassThru +Returns true when the command succeeds + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -157,9 +216,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[Get-CsGroupPolicyAssignment]() - -[Set-CsGroupPolicyAssignment]() +[Get-CsUserPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/get-csuserpolicyassignment) -[Remove-CsGroupPolicyAssignment]() +[Get-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/get-csgrouppolicyassignment) +[Remove-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csgrouppolicyassignment) diff --git a/teams/teams-ps/teams/New-CsHybridTelephoneNumber.md b/teams/teams-ps/teams/New-CsHybridTelephoneNumber.md new file mode 100644 index 0000000000..80fbe8f586 --- /dev/null +++ b/teams/teams-ps/teams/New-CsHybridTelephoneNumber.md @@ -0,0 +1,105 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-cshybridtelephonenumber +applicable: Microsoft Teams +title: New-CsHybridTelephoneNumber +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# New-CsHybridTelephoneNumber + +## SYNOPSIS +This cmdlet adds a hybrid telephone number to the tenant. + +> [!IMPORTANT] +> This cmdlet is being deprecated. Use the **New-CsOnlineDirectRoutingTelephoneNumberUploadOrder** cmdlet to add a telephone number for Audio Conferencing with Direct Routing in Microsoft 365 GCC High and DoD clouds. Detailed instructions on how to use the new cmdlet can be found at [New-CsOnlineDirectRoutingTelephoneNumberUploadOrder](/powershell/module/teams/new-csonlinedirectroutingtelephonenumberuploadorder?view=teams-ps) + +## SYNTAX + +### Identity (Default) +```powershell +New-CsHybridTelephoneNumber -TelephoneNumber <string> [-Force] -InputObject <IConfigApiBasedCmdletsIdentity> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet adds a hybrid telephone number to the tenant that can be used for Audio Conferencing with Direct Routing for GCC High and DoD clouds. + +## EXAMPLES + +### Example 1 +```powershell +New-CsHybridTelephoneNumber -TelephoneNumber +14025551234 +``` +This example adds the hybrid phone number +1 (402) 555-1234. + +## PARAMETERS + +### -TelephoneNumber +The telephone number to add. The number should be specified with a prefixed "+". The phone number can't have "tel:" prefixed. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +The identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: NewViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES + +The cmdlet is only available in GCC High and DoD cloud instances. + +## RELATED LINKS +[Remove-CsHybridTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/remove-cshybridtelephonenumber) + +[Get-CsHybridTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/get-cshybridtelephonenumber) diff --git a/teams/teams-ps/teams/New-CsInboundBlockedNumberPattern.md b/teams/teams-ps/teams/New-CsInboundBlockedNumberPattern.md new file mode 100644 index 0000000000..ba2c63af2f --- /dev/null +++ b/teams/teams-ps/teams/New-CsInboundBlockedNumberPattern.md @@ -0,0 +1,171 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csinboundblockednumberpattern +applicable: Microsoft Teams +title: New-CsInboundBlockedNumberPattern +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: bulenteg +schema: 2.0.0 +--- + +# New-CsInboundBlockedNumberPattern + +## SYNOPSIS +Adds a blocked number pattern to the tenant list. + +## SYNTAX + +### Identity (Default) +``` +New-CsInboundBlockedNumberPattern [-Identity] <string> -Pattern <string> [-Description <string>] [-Enabled <boolean>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsInboundBlockedNumberPattern -Pattern <string> -Name <string> [-Description <string>] [-Enabled <boolean>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet adds a blocked number pattern to the tenant list. An inbound PSTN call from a number that matches the blocked number pattern will be blocked. + +## EXAMPLES + +### Example 1 +```powershell +PS> New-CsInboundBlockedNumberPattern -Description "Avoid Unwanted Automatic Call" -Name "BlockAutomatic" -Pattern "^\+11234567890" +``` + +This example adds a blocked number pattern to block inbound calls from +11234567890 number. + +## PARAMETERS + +### -Description +A friendly description for the blocked number pattern to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +If this parameter is set to True, the inbound calls matching the pattern will be blocked. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A unique identifier specifying the blocked number pattern to be created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +A displayable name describing the blocked number pattern to be created. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern +A regular expression that the calling number must match in order to be blocked. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/get-csinboundblockednumberpattern) + +[Set-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/set-csinboundblockednumberpattern) + +[Remove-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/remove-csinboundblockednumberpattern) diff --git a/teams/teams-ps/teams/New-CsInboundExemptNumberPattern.md b/teams/teams-ps/teams/New-CsInboundExemptNumberPattern.md new file mode 100644 index 0000000000..63ed383946 --- /dev/null +++ b/teams/teams-ps/teams/New-CsInboundExemptNumberPattern.md @@ -0,0 +1,177 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csinboundexemptnumberpattern +applicable: Microsoft Teams +title: New-CsInboundExemptNumberPattern +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# New-CsInboundExemptNumberPattern + +## SYNOPSIS + +This cmdlet lets you configure a new number pattern that is exempt from tenant call blocking. + +## SYNTAX + +### Identity (Default) + +```powershell +New-CsInboundExemptNumberPattern -Identity <String> -Pattern <String> [-Description <String>] [-Enabled <Boolean>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsInboundExemptNumberPattern -Pattern <string> -Name <string> [-Description <string>] [-Enabled <boolean>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS> New-CsInboundExemptNumberPattern -Identity "AllowContoso1" -Pattern "^\+?1312555888[2|3]$" -Description "Allow Contoso helpdesk" -Enabled $True +``` + +Creates a new inbound exempt number pattern for the numbers 1 (312) 555-88882 and 1 (312) 555-88883 and enables it + +## PARAMETERS + +### -Description + +Sets the description of the number pattern. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +This parameter determines whether the number pattern is enabled for exemption or not. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the exempt number pattern to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +A displayable name describing the exempt number pattern to be created. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern + +A regular expression that the calling number must match in order to be exempt from blocking. It is best practice to start the regular expression with the hat character and end it with the dollar character. You can use various regular expression test sites on the Internet to validate the expression. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +You can use Test-CsInboundBlockedNumberPattern to test your block and exempt phone number ranges. + +## RELATED LINKS + +[Get-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/get-csinboundexemptnumberpattern) + +[Set-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/set-csinboundexemptnumberpattern) + +[Remove-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/remove-csinboundexemptnumberpattern) + +[Test-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/test-csinboundblockednumberpattern) + +[Get-CsTenantBlockedCallingNumbers](https://learn.microsoft.com/powershell/module/teams/get-cstenantblockedcallingnumbers) diff --git a/teams/teams-ps/teams/New-CsOnlineApplicationInstance.md b/teams/teams-ps/teams/New-CsOnlineApplicationInstance.md new file mode 100644 index 0000000000..0254f15626 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineApplicationInstance.md @@ -0,0 +1,152 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstance +applicable: Microsoft Teams +title: New-CsOnlineApplicationInstance +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsOnlineApplicationInstance + +## SYNOPSIS +Creates an application instance in Microsoft Entra ID. + +## SYNTAX + +``` +New-CsOnlineApplicationInstance [-UserPrincipalName] <string> [[-ApplicationId] <guid>] [[-DisplayName] <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet is used to create an application instance in Microsoft Entra ID. This same cmdlet is also run when creating a new resource account using Teams Admin Center. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +New-CsOnlineApplicationInstance -UserPrincipalName appinstance01@contoso.com -ApplicationId ce933385-9390-45d1-9512-c8d228074e07 -DisplayName "AppInstance01" +``` + +This example creates a new application instance for an Auto Attendant with UserPrincipalName "appinstance01@contoso.com", ApplicationId "ce933385-9390-45d1-9512-c8d228074e07", DisplayName "AppInstance01" for the tenant. + +## PARAMETERS + +### -UserPrincipalName +The user principal name. It will be used as the SIP URI too. The user principal name should have an online domain. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplicationId +The application ID. The Microsoft application Auto Attendant has the ApplicationId ce933385-9390-45d1-9512-c8d228074e07 and the Microsoft application Call Queue has the ApplicationId 11cd3e2e-fccb-42ad-ad00-878b93575e07. Third-party applications available in a tenant will use other ApplicationId's. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +The display name. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +This switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If it isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstance) + +[Set-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/set-csonlineapplicationinstance) + +[Find-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/find-csonlineapplicationinstance) + +[Sync-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/sync-csonlineapplicationinstance) diff --git a/skype/skype-ps/skype/New-CsOnlineApplicationInstanceAssociation.md b/teams/teams-ps/teams/New-CsOnlineApplicationInstanceAssociation.md similarity index 83% rename from skype/skype-ps/skype/New-CsOnlineApplicationInstanceAssociation.md rename to teams/teams-ps/teams/New-CsOnlineApplicationInstanceAssociation.md index 4fbb4b8856..9cc704f634 100644 --- a/skype/skype-ps/skype/New-CsOnlineApplicationInstanceAssociation.md +++ b/teams/teams-ps/teams/New-CsOnlineApplicationInstanceAssociation.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlineapplicationinstanceassociation -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstanceassociation +applicable: Microsoft Teams title: New-CsOnlineApplicationInstanceAssociation schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsOnlineApplicationInstanceAssociation @@ -18,7 +18,7 @@ Use the New-CsOnlineApplicationInstanceAssociation cmdlet to associate either a ## SYNTAX ``` -New-CsOnlineApplicationInstanceAssociation -Identities <String[]> -ConfigurationId <String> -ConfigurationType <Object> [-Tenant <Guid>] [<CommonParameters>] +New-CsOnlineApplicationInstanceAssociation -Identities <String[]> -ConfigurationId <String> -ConfigurationType <Object> [-CallPriority <Int16>] [-Tenant <Guid>] [<CommonParameters>] ``` ## DESCRIPTION @@ -119,7 +119,7 @@ The Identities parameter is the identities of application instances to be associ Type: System.String[] Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -129,13 +129,13 @@ Accept wildcard characters: False ``` ### -ConfigurationId -The ConfigurationId parameter is the identity of the configuration that would be associatied with the provided application instances. +The ConfigurationId parameter is the identity of the configuration that would be associated with the provided application instances. ```yaml Type: System.string Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -156,7 +156,7 @@ It can be one of two values: Type: System.string Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -165,13 +165,37 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -CallPriority +The call priority assigned to calls arriving on this application instance if a priority has not already been assigned. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 + +1 = Very High +2 = High +3 = Normal / Default +4 = Low +5 = Very Low + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 3 +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Tenant ```yaml Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -181,7 +205,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -195,9 +219,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## RELATED LINKS -[Get-CsOnlineApplicationInstanceAssociation](Get-CsOnlineApplicationInstanceAssociation.md) - -[Get-CsOnlineApplicationInstanceAssociationStatus](Get-CsOnlineApplicationInstanceAssociationStatus.md) +[Get-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociation) -[Remove-CsOnlineApplicationInstanceAssociation](Remove-CsOnlineApplicationInstanceAssociation.md) +[Get-CsOnlineApplicationInstanceAssociationStatus](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociationstatus) +[Remove-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/remove-csonlineapplicationinstanceassociation) diff --git a/teams/teams-ps/teams/New-CsOnlineAudioConferencingRoutingPolicy.md b/teams/teams-ps/teams/New-CsOnlineAudioConferencingRoutingPolicy.md new file mode 100644 index 0000000000..f38c088398 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineAudioConferencingRoutingPolicy.md @@ -0,0 +1,177 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlineaudioconferencingroutingpolicy +title: New-CsOnlineAudioConferencingRoutingPolicy +schema: 2.0.0 +--- + +# New-CsOnlineAudioConferencingRoutingPolicy + +## SYNOPSIS + +This cmdlet creates a Online Audio Conferencing Routing Policy. + +## SYNTAX + +```powershell +New-CsOnlineAudioConferencingRoutingPolicy [-Identity] <String> [-Description <String>] + [-OnlinePstnUsages <Object>] [-RouteType <String>] [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +Teams meeting dial-out calls are initiated from within a meeting in your organization to PSTN numbers, including call-me-at calls and calls to bring new participants to a meeting. + +To enable Teams meeting dial-out routing through Direct Routing to on-network users, you need to create and assign an Audio Conferencing routing policy called "OnlineAudioConferencingRoutingPolicy." + +The OnlineAudioConferencingRoutingPolicy policy is equivalent to the CsOnlineVoiceRoutingPolicy for 1:1 PSTN calls via Direct Routing. + +Audio Conferencing voice routing policies determine the available routes for calls from meeting dial-out based on the destination number. Audio Conferencing voice routing policies link to PSTN usages, determining routes for meeting dial-out calls by associated organizers. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> New-CsOnlineAudioConferencingRoutingPolicy -Identity Test +``` + +Creates a new Online Audio Conferencing Routing Policy policy with an identity called "Test". + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide explanatory text about the Online Audio Conferencing Routing policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Identity of the Online Audio Conferencing Routing Policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnUsages + +A list of online PSTN usages (such as Local or Long Distance) that can be applied to this online audio routing policy. The online PSTN usages must be existing usages (PSTN usages can be retrieved by calling the Get-CsOnlinePstnUsage cmdlet). + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RouteType + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Remove-CsOnlineAudioConferencingRoutingPolicy](Remove-CsOnlineAudioConferencingRoutingPolicy.md) +[Grant-CsOnlineAudioConferencingRoutingPolicy](Grant-CsOnlineAudioConferencingRoutingPolicy.md) +[Set-CsOnlineAudioConferencingRoutingPolicy](Set-CsOnlineAudioConferencingRoutingPolicy.md) +[Get-CsOnlineAudioConferencingRoutingPolicy](Get-CsOnlineAudioConferencingRoutingPolicy.md) diff --git a/teams/teams-ps/teams/New-CsOnlineDateTimeRange.md b/teams/teams-ps/teams/New-CsOnlineDateTimeRange.md new file mode 100644 index 0000000000..ad73e8f554 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineDateTimeRange.md @@ -0,0 +1,117 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinedatetimerange +applicable: Microsoft Teams +title: New-CsOnlineDateTimeRange +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsOnlineDateTimeRange + +## SYNOPSIS +Use the New-CsOnlineDateTimeRange cmdlet to create a new date-time range. + +## SYNTAX + +``` +New-CsOnlineDateTimeRange -Start <String> [-End <String>] [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The New-CsOnlineDateTimeRange cmdlet creates a new date-time range to be used with the Organizational Auto Attendant (OAA) service. Date time ranges are used to form schedules. + +**NOTE**: + +- The start bound of the range must be less than its end bound. +- The time part of the range must be aligned with 30/60-minutes boundaries. +- A date time range bound can only be input in the following formats: + - "d/m/yyyy H:mm" + - "d/m/yyyy" (the time component of the date-time range is set to 00:00) + +## EXAMPLES + +### Example 1 +``` +$dtr = New-CsOnlineDateTimeRange -Start "1/1/2017" +``` + +This example creates a date-time range for spanning from January 1, 2017 12AM to January 2, 2017 12AM. + +### Example 2 +``` +$dtr = New-CsOnlineDateTimeRange -Start "24/12/2017 09:00" -End "27/12/2017 00:00" +``` + +This example creates a date-time range spanning from December 24, 2017 9AM to December 27, 2017 12AM. + +## PARAMETERS + +### -Start +The Start parameter represents the start bound of the date-time range. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -End +The End parameter represents the end bound of the date-time range. + +If not present, the end bound of the date time range is set to 00:00 of the day after the start date. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.DateTimeRange + +## NOTES + +## RELATED LINKS + +[New-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/new-csonlineschedule) diff --git a/teams/teams-ps/teams/New-CsOnlineDirectRoutingTelephoneNumberUploadOrder.md b/teams/teams-ps/teams/New-CsOnlineDirectRoutingTelephoneNumberUploadOrder.md new file mode 100644 index 0000000000..b7d52913b8 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineDirectRoutingTelephoneNumberUploadOrder.md @@ -0,0 +1,145 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinedirectroutingtelephonenumberuploadorder +applicable: Microsoft Teams +title: New-CsOnlineDirectRoutingTelephoneNumberUploadOrder +author: pavellatif +ms.author: pavellatif +ms.reviewer: pavellatif +manager: roykuntz +schema: 2.0.0 +--- + +# New-CsOnlineDirectRoutingTelephoneNumberUploadOrder + +## SYNOPSIS +This cmdlet creates a request to upload Direct Routing telephone numbers to Microsoft Teams telephone number management inventory. The output of the cmdlet is the "orderId" of the asynchronous Direct Routing Number creation operation. A maximum of 10,000 phone numbers can be uploaded at a time. If more than 10,000 numbers need to be uploaded, the requests should be divided into multiple increments of up to 10,000 numbers. + +## SYNTAX + +``` +New-CsOnlineDirectRoutingTelephoneNumberUploadOrder [-TelephoneNumber <String>] [-StartingNumber <String>] [-EndingNumber <String>] [-FileContent <Byte[]>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet uploads Direct Routing telephone numbers to Microsoft Teams telephone number management inventory. Once uploaded the phone numbers will be visible in Teams PowerShell as acquired Direct Routing phone numbers. + +The cmdlet is an asynchronous operation and will return an OrderId as output. You can use the [Get-CsOnlineTelephoneNumberOrder](./get-csonlinetelephonenumberorder.md) cmdlet to check the status of the OrderId, including any error or warning messages that might result from the operation: `Get-CsOnlineTelephoneNumberOrder -OrderType DirectRoutingNumberCreation -OrderId "orderId"`. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsOnlineDirectRoutingTelephoneNumberUploadOrder -TelephoneNumber "+123456789" +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c13 +``` + +In this example, a new Direct Routing telephone number "+123456789" is being uploaded to Microsoft Teams telephone number management inventory. The output of the cmdlet is the OrderId that can be used with the [Get-CsOnlineTelephoneNumberOrder](./get-csonlinetelephonenumberorder.md) cmdlet to retrieve the status of the order: `Get-CsOnlineTelephoneNumberOrder -OrderType DirectRoutingNumberCreation -OrderId "orderId"`. + +### Example 2 +```powershell +PS C:\> New-CsOnlineDirectRoutingTelephoneNumberUploadOrder -TelephoneNumber "+123456789,+134567890,+145678901" +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c14 +``` + +In this example, a list of telephone numbers is being uploaded to Microsoft Teams telephone number management inventory. The output of the cmdlet is the OrderId that can be used with the [Get-CsOnlineTelephoneNumberOrder](./get-csonlinetelephonenumberorder.md) cmdlet to retrieve the status of the order: `Get-CsOnlineTelephoneNumberOrder -OrderType DirectRoutingNumberCreation -OrderId "orderId"`. + +### Example 3 +```powershell +PS C:\> New-CsOnlineDirectRoutingTelephoneNumberUploadOrder -StartingNumber "+12000000" -EndingNumber "+12000009" +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c13 +``` + +In this example, a range of Direct Routing telephone numbers from "+12000000" to "+12000009" are being uploaded to Microsoft Teams telephone number management inventory. The output of the cmdlet is the OrderId that can be used with the [Get-CsOnlineTelephoneNumberOrder](./get-csonlinetelephonenumberorder.md) cmdlet to retrieve the status of the order: `Get-CsOnlineTelephoneNumberOrder -OrderType DirectRoutingNumberCreation -OrderId "orderId"`. + +### Example 4 +```powershell +PS C:\> $drlist = [System.IO.File]::ReadAllBytes("C:\Users\testuser\DrNumber.csv") +PS C:\> New-CsOnlineDirectRoutingTelephoneNumberUploadOrder -FileContent $drlist +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c19 +``` + +In this example, the content of a file with a list of Direct Routing telephone numbers are being uploaded via file upload. The file should be in Comma Separated Values (CSV) file format and only containing the list of DR numbers. Only the content of the file can be passed to the New-CsOnlineDirectRoutingTelephoneNumberUploadOrder cmdlet. Additional fields will be supported via file upload in future releases. The output of the cmdlet is the OrderId that can be used with the [Get-CsOnlineTelephoneNumberOrder](./get-csonlinetelephonenumberorder.md) cmdlet to retrieve the status of the order: `Get-CsOnlineTelephoneNumberOrder -OrderType DirectRoutingNumberCreation -OrderId "orderId"`. + +## PARAMETERS + +### -TelephoneNumber +This is the Direct Routing telephone numbers you wish to upload to Microsoft Teams telephone number management inventory. It is comma delimited list of one or more Direct Routing telephone numbers. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartingNumber +This is the starting number of a range of Direct Routing telephone number you wish to upload to Microsoft Teams telephone number management inventory. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndingNumber +This is the ending number of a range of Direct Routing telephone number you wish to upload to Microsoft Teams telephone number management inventory. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileContent +This is the content of a .csv file that includes the Direct Routing telephone numbers to be uploaded to the Microsoft Teams telephone number management inventory. This parameter can be used to upload up to 10,000 numbers at a time. + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.String + +## NOTES +The cmdlet is available in Teams PowerShell module 6.7.1 or later. + +The cmdlet is only available in commercial and GCC cloud instances. + +## RELATED LINKS +[Get-CsOnlineTelephoneNumberOrder](./get-csonlinetelephonenumberorder.md) +[New-CsOnlineTelephoneNumberReleaseOrder](./new-csonlinetelephonenumberreleaseorder.md) \ No newline at end of file diff --git a/teams/teams-ps/teams/New-CsOnlineLisCivicAddress.md b/teams/teams-ps/teams/New-CsOnlineLisCivicAddress.md new file mode 100644 index 0000000000..18fa5f7f05 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineLisCivicAddress.md @@ -0,0 +1,467 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlineliscivicaddress +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: New-CsOnlineLisCivicAddress +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsOnlineLisCivicAddress + +## SYNOPSIS +Use the New-CsOnlineLisCivicAddress cmdlet to create a civic address in the Location Information Service (LIS). + +## SYNTAX + +``` +New-CsOnlineLisCivicAddress -CompanyName <string> -CountryOrRegion <string> [-City <string>] [-CityAlias <string>] [-CompanyTaxId <string>] +[-Description <string>] [-Elin <string>] [-Force] [-HouseNumber <string>] [-HouseNumberSuffix <string>] +[-Latitude <string>] [-Longitude <string>] [-PostalCode <string>] [-PostDirectional <string>] [-PreDirectional <string>] +[-StateOrProvince <string>] [-StreetName <string>] [-StreetSuffix <string>] [-Confidence <String>] [-IsAzureMapValidationRequired <String>] [-ValidationStatus <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Because each civic address needs at least one location to assign to users, creating a new civic address also creates a default location. +This is useful in cases where a civic address has no particular sub-locations. +In that scenario you can create the civic address using the New -CsOnlineLisCivicAddress cmdlet and use the default location identifier for assignment to users. +The example output from the Get-CsOnlineLisCivicAddress below shows the DefaultLocationId property. + +CivicAddressId : 51a8a6e3-dae4-4653-9a99-a6e71c4c24ac + +HouseNumber : + +HouseNumberSuffix : + +PreDirectional : + +StreetName : + +StreetSuffix : + +PostDirectional : + +City : + +PostalCode : + +StateOrProvince : + +CountryOrRegion : US + +Description : + +CompanyName : MSFT + +DefaultLocationId : 75301b5d-3609-458e-a379-da9a1ab33228 + +ValidationStatus : NotValidated + +NumberOfVoiceUsers : 0 + +## EXAMPLES + +### Example 1 +```powershell +New-CsOnlineLisCivicAddress -HouseNumber 1 -StreetName 'Microsoft Way' -City Redmond -StateorProvince Washington -CountryOrRegion US -PostalCode 98052 -Description "West Coast Headquarters" -CompanyName Contoso -Latitude 47.63952 -Longitude -122.12781 -Elin MICROSOFT_ELIN +``` + +This example creates a new civic address described as "West Coast Headquarters": 1 Microsoft Way, Redmond WA, 98052 and sets the geo-coordinates. + +## PARAMETERS + +### -CompanyName +Specifies the name of your organization. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CountryOrRegion +Specifies the country or region of the new civic address. +Needs to be a valid country code as contained in the ISO 3166-1 alpha-2 specification. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -City +Specifies the city of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CityAlias +Specifies the city alias of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompanyTaxId +Specifies the company tax identifier of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies an administrator defined description of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Elin +Specifies the Emergency Location Identification Number. +This is used in Direct Routing EGW scenarios. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HouseNumber +Specifies the numeric portion of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HouseNumberSuffix +Specifies the numeric suffix of the new civic address. +For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Latitude +Specifies the angular distance of a place north or south of the earth's equator using the decimal degrees format. Required for all countries except Australia and Japan where it's optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Longitude +Specifies the angular distance of a place east or west of the meridian at Greenwich, England, using the decimal degrees format. Required for all countries except Australia and Japan where it's optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostalCode +Specifies the postal code of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostDirectional +Specifies the directional attribute of the new civic address which follows the street name. +For example, "425 Smith Avenue NE". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreDirectional +Specifies the directional attribute of the new civic address which precedes the street name. +For example, "425 NE Smith Avenue". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StateOrProvince +Specifies the state or province of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreetName +Specifies the street name of the new civic address. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreetSuffix +Specifies the street type of the new civic address. +The street suffix will typically be something like street, avenue, way, or boulevard. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confidence +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsAzureMapValidationRequired +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidationStatus +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing, and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/set-csonlineliscivicaddress) + +[Remove-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/remove-csonlineliscivicaddress) + +[Get-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/get-csonlineliscivicaddress) diff --git a/teams/teams-ps/teams/New-CsOnlineLisLocation.md b/teams/teams-ps/teams/New-CsOnlineLisLocation.md new file mode 100644 index 0000000000..418b3f5aa2 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineLisLocation.md @@ -0,0 +1,454 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinelislocation +applicable: Microsoft Teams +title: New-CsOnlineLisLocation +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsOnlineLisLocation + +## SYNOPSIS +Use the New-CsOnlineLisLocation cmdlet to create a new emergency dispatch location within an existing civic address. Typically the civic address designates the building, and locations are specific parts of that building such as a floor, office, or wing. + +## SYNTAX + +``` +New-CsOnlineLisLocation -Location <string> -CivicAddressId <guid> [-Elin <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +## EXAMPLES + +### Example 1 +```powershell +New-CsOnlineLisLocation -CivicAddressId b39ff77d-db51-4ce5-8d50-9e9c778e1617 -Location "Office 101, 1st Floor" +``` + +This example creates a new location called "Office 101, 1st Floor" in the civic address specified by its identity. + +## PARAMETERS + +### -CivicAddressId +Specifies the unique identifier of the civic address that will contain the new location. Civic address identities can be discovered by using the Get-CsOnlineLisCivicAddress cmdlet. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Location +Specifies an administrator-defined description of the new location. For example, "2nd Floor Cafe", "Main Lobby", or "Office 250". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CountryOrRegion +Specifies the country or region of the civic address. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: Country +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -City +Specifies the city of the civic address. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CityAlias +Specifies the city alias. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CompanyName +Specifies the name of your organization. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: Name +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompanyTaxId +The company tax ID. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confidence +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies an administrator defined description of the civic address. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Elin +Specifies the Emergency Location Identification Number. This is used in Direct Routing EGW scenarios. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HouseNumber +Specifies the numeric portion of the civic address. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -HouseNumberSuffix +Specifies the numeric suffix of the civic address. +For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Latitude +Specifies the angular distance of a place north or south of the earth's equator using the decimal degrees format. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Longitude +Specifies the angular distance of a place east or west of the meridian at Greenwich, England, using the decimal degrees format. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostalCode +Specifies the postal code of the civic address. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PostDirectional +Specifies the directional attribute of the civic address which follows the street name. For example, "425 Smith Avenue NE". + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PreDirectional +Specifies the directional attribute of the civic address which precedes the street name. For example, "425 NE Smith Avenue". + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StateOrProvince +Specifies the state or province of the civic address. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: State +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StreetName +Specifies the street name of the civic address. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StreetSuffix +Specifies the modifier of the street name. The street suffix will typically be something like street, avenue, way, or boulevard. + +**Note:** This parameter is not supported and is deprecated. + +```yaml +Type: String +Parameter Sets: CreateCivicAddress +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing, and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/set-csonlinelislocation) + +[Get-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/get-csonlinelislocation) + +[Remove-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/remove-csonlinelislocation) diff --git a/teams/teams-ps/teams/New-CsOnlinePSTNGateway.md b/teams/teams-ps/teams/New-CsOnlinePSTNGateway.md new file mode 100644 index 0000000000..3da8fd129c --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlinePSTNGateway.md @@ -0,0 +1,459 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinepstngateway +applicable: Microsoft Teams +title: New-CsOnlinePSTNGateway +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsOnlinePSTNGateway + +## SYNOPSIS +Creates a new Session Border Controller (SBC) Configuration that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. + +## SYNTAX + +### Identity (Default) +``` +New-CsOnlinePSTNGateway [-Identity] <string> -SipSignalingPort <int> [-BypassMode <string>] [-Description <string>] [-Enabled <boolean>] + [-FailoverResponseCodes <string>] [-FailoverTimeSeconds <int>] [-ForwardCallHistory <boolean>] [-ForwardPai <boolean>] [-GatewayLbrEnabledUserOverride <boolean>] + [-GatewaySiteId <string>] [-GatewaySiteLbrEnabled <boolean>] [-InboundPstnNumberTranslationRules <Object>] [-InboundTeamsNumberTranslationRules <Object>] + [-MaxConcurrentSessions <int>] [-MediaBypass <boolean>] [-MediaRelayRoutingLocationOverride <string>] [-OutboundPstnNumberTranslationRules <Object>] + [-OutboundTeamsNumberTranslationRules <Object>] [-PidfLoSupported <boolean>] [-ProxySbc <string>] [-SendSipOptions <boolean>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsOnlinePSTNGateway -SipSignalingPort <int> -Fqdn <string> [-BypassMode <string>] [-Description <string>] [-Enabled <boolean>] + [-FailoverResponseCodes <string>] [-FailoverTimeSeconds <int>] [-ForwardCallHistory <boolean>] [-ForwardPai <boolean>] [-GatewayLbrEnabledUserOverride <boolean>] + [-GatewaySiteId <string>] [-GatewaySiteLbrEnabled <boolean>] [-InboundPstnNumberTranslationRules <Object>] [-InboundTeamsNumberTranslationRules <Object>] + [-MaxConcurrentSessions <int>] [-MediaBypass <boolean>] [-MediaRelayRoutingLocationOverride <string>] [-OutboundPstnNumberTranslationRules <Object>] + [-OutboundTeamsNumberTranslationRules <Object>] [-PidfLoSupported <boolean>] [-ProxySbc <string>] [-SendSipOptions <boolean>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to create a new Session Border Controller (SBC) configuration. Each configuration contains specific settings for an SBC. These settings configure such entities as the SIP signaling port, whether media bypass is enabled on this SBC, will the SBC send SIP Options, and specify the limit of maximum concurrent sessions. The cmdlet also lets the administrator drain the SBC by setting parameter -Enabled to $true or $false state. When the Enabled parameter is set to $false, the SBC will continue existing calls, but all new calls will be routed to another SBC in a route (if one exists). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsOnlinePSTNGateway -FQDN sbc.contoso.com -SIPSignalingPort 5061 +``` + +This example creates an SBC with FQDN sbc.contoso.com and signaling port 5061. All others parameters will stay default. Note the SBC will be in the disabled state. + +### Example 2 +```powershell +PS C:\> New-CsOnlinePSTNGateway -FQDN sbc.contoso.com -SIPSignalingPort 5061 -ForwardPAI $true -Enabled $true +``` + +This example creates an SBC with FQDN sbc.contoso.com and signaling port 5061. For each outbound to SBC session, the Direct Routing interface will report in P-Asserted-Identity fields the TEL URI and SIP address of the user who made a call. This is useful when a tenant administrator sets the identity of the caller as "Anonymous" or a general number of the company, but for billing purposes the real identity of the user is required. + +## PARAMETERS + +### -Description +Free-format string to describe the gateway. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +Used to enable this SBC for outbound calls. Can be used to temporarily remove the SBC from service while it is being updated or during maintenance. Note if the parameter is not set the SBC will be created as disabled (default value -Enabled $false). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FailoverResponseCodes +If Direct Routing receives any 4xx or 6xx SIP error code in response to an outgoing Invite the call is considered completed by default. (Outgoing in this context is a call +from a Teams client to the PSTN with traffic flow: Teams Client -> Direct Routing -> SBC -> Telephony network). Setting the SIP codes in this parameter forces Direct Routing +on receiving the specified codes try another SBC (if another SBC exists in the voice routing policy of the user). Find more information in the "Reference" section of "Phone +System Direct Routing" documentation. + +Setting this parameter overwrites the default values, so if you want to include the default values, please add them to string. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: 408, 503, 504 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FailoverTimeSeconds +When set to 10 (default value), outbound calls that are not answered by the gateway within 10 seconds are routed to the next available trunk; if there are no additional trunks, then the call is automatically dropped. In an organization with slow networks and slow gateway responses, that could potentially result in calls being dropped unnecessarily. The default value is 10. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: 10 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardCallHistory +Indicates whether call history information will be forwarded to the SBC. If enabled, the Office 365 PSTN Proxy sends two headers: History-info and Referred-By. The default value is False ($False). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardPai +Indicates whether the P-Asserted-Identity (PAI) header will be forwarded along with the call. The PAI header provides a way to verify the identity of the caller. The default value is False ($False). Setting this parameter to $true will render the from header anonymous, in accordance of RFC5379 and RFC3325. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Fqdn +Limited to 63 characters, the FQDN registered for the SBC. Copied automatically to Identity of the SBC field. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GatewaySiteId +PSTN Gateway Site Id. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GatewaySiteLbrEnabled +Used to enable this SBC to report assigned site location. Site location is used for Location Based Routing. When this parameter is enabled ($True), the SBC will report the site +name as defined by the tenant administrator. On an incoming call to a Teams user the value of the site assigned to the SBC is compared with the value of the site assigned to +the user to make a routing decision. The parameter is mandatory for enabling Location Based Routing feature. The default value is False ($False). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GatewayLbrEnabledUserOverride +Allows an LBR enabled user working from a network site outside the corporate network or a network site on the corporate network not configured using a tenant network site to make outbound PSTN calls or receive inbound PSTN calls via an LBR enabled gateway. The default value is False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +When creating a new SBC, the identity must be identical to the -FQDN parameter, described above. If the parameter is not defined the Identity will be copied from the -FQDN parameter. The Identity parameter is not mandatory. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxConcurrentSessions +Used by the alerting system. When any value is set, the alerting system will generate an alert to the tenant administrator when the number of concurrent sessions is 90% or higher than this value. If the parameter is not set, alerts are not generated. However, the monitoring system will report the number of concurrent sessions every 24 hours. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaBypass +Parameter indicates if the SBC supports Media Bypass and the administrator wants to use it for this SBC. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaRelayRoutingLocationOverride +Allows selecting path for media manually. Direct Routing assigns a datacenter for media path based on the public IP of the SBC. We always select closest to the SBC datacenter. However, in some cases a public IP from for example a US range can be assigned to an SBC located in Europe. In this case we will be using not optimal media path. We only recommend setting this parameter if the call logs clearly indicate that automatic assignment of the datacenter for media path does not assign the closest to the SBC datacenter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendSipOptions +Defines if an SBC will or will not send SIP Options messages. If disabled, the SBC will be excluded from the Monitoring and Alerting system. We highly recommend that you enable SIP Options. The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $true +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SipSignalingPort +Listening port used for communicating with Direct Routing services by using the Transport Layer Security (TLS) protocol. Must be value between 1 and 65535. +Please note: Spelling of this parameter changed recently from SipSignallingPort to SipSignalingPort. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassMode +Possible values are "None", "Always" and "OnlyForLocalUsers". By setting "Always" mode you indicate that your network is fully routable. If a user usually in site "Seattle", travels to site "Tallinn" and tries to use SBC located in Seattle we will try to deliver the traffic to Seattle assuming that there is connection between Tallinn and Seattle offices. With "OnlyForLocaUsers" you indicate that there is no direct connection between sites. In example above, the traffic will not be send directly from Tallinn to Seattle. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundTeamsNumberTranslationRules +This parameter assigns an ordered list of Teams translation rules, that apply to Teams numbers on inbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundPSTNNumberTranslationRules +Creates an ordered list of Teams translation rules, that apply to PSTN number on inbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutbundTeamsNumberTranslationRules +Creates an ordered list of Teams translation rules, that apply to Teams Number on outbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutboundPSTNNumberTranslationRules +Assigns an ordered list of Teams translation rules, that apply to PSTN number on outbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PidfloSupported +Enables PIDF-LO support on the PSTN Gateway. If turned on the .xml body payload is sent to the SBC with the location details of the user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxySbc +The FQDN of the proxy SBC. Used in Local Media Optimization configurations. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/set-csonlinepstngateway) + +[Get-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/get-csonlinepstngateway) + +[Remove-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/remove-csonlinepstngateway) diff --git a/skype/skype-ps/skype/New-CsOnlineSchedule.md b/teams/teams-ps/teams/New-CsOnlineSchedule.md similarity index 80% rename from skype/skype-ps/skype/New-CsOnlineSchedule.md rename to teams/teams-ps/teams/New-CsOnlineSchedule.md index 8f06ae71ca..321a1e96c4 100644 --- a/skype/skype-ps/skype/New-CsOnlineSchedule.md +++ b/teams/teams-ps/teams/New-CsOnlineSchedule.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csonlineschedule -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlineschedule +applicable: Microsoft Teams title: New-CsOnlineSchedule schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsOnlineSchedule @@ -19,18 +19,19 @@ Use the New-CsOnlineSchedule cmdlet to create a new schedule. ### WeeklyRecurrentSchedule ```powershell -New-CsOnlineSchedule -Name <String> -WeeklyRecurrentSchedule [-MondayHours <List>] [-TuesdayHours <List>] [-WednesdayHours <List>] [-ThursdayHours <List>] [-FridayHours <List>] [-SaturdayHours <List>] [-SundayHours <List>] [-Complement] [-Tenant <Guid>] [-CommonParameters] +New-CsOnlineSchedule -Name <String> -WeeklyRecurrentSchedule [-MondayHours <List>] [-TuesdayHours <List>] [-WednesdayHours <List>] [-ThursdayHours <List>] [-FridayHours <List>] [-SaturdayHours <List>] [-SundayHours <List>] [-Complement] [-Tenant <Guid>] [<CommonParameters>] ``` ### FixedSchedule ```powershell -New-CsOnlineSchedule -Name <String> -FixedSchedule [-DateTimeRanges <List>] [-Tenant <Guid>] [-CommonParameters] +New-CsOnlineSchedule -Name <String> -FixedSchedule [-DateTimeRanges <List>] [-Tenant <Guid>] [<CommonParameters>] ``` ## DESCRIPTION -The New-CsOnlineSchedule cmdlet creates a new schedule for the Organizational Auto Attendant (OAA) service. The OAA service uses schedules to conditionally execute call flows when a specific schedule is in effect. +The New-CsOnlineSchedule cmdlet creates a new schedule for the Auto Attendant (AA) service. The AA service uses schedules to conditionally execute call flows when a specific schedule is in effect. + +**NOTES**: -**NOTE** - The type of the schedule cannot be altered after the schedule is created. - Currently, only two types of schedules can be created: WeeklyRecurrentSchedule or FixedSchedule. - The schedule types are mutually exclusive. So a weekly recurrent schedule cannot be a fixed schedule and vice versa. @@ -40,6 +41,7 @@ The New-CsOnlineSchedule cmdlet creates a new schedule for the Organizational Au - For a fixed schedule, at most 10 date-time ranges can be specified. - You can create a new date-time range for a fixed schedule by using the New-CsOnlineDateTimeRange cmdlet. - The return type of this cmdlet composes a member for the underlying type/implementation. For example, in case of the weekly recurrent schedule, you can modify Monday's time ranges through the Schedule.WeeklyRecurrentSchedule.MondayHours property. Similarly, date-time ranges of a fixed schedule can be modified by using the Schedule.FixedSchedule.DateTimeRanges property. +- Schedules can then be used by [New-CsAutoAttendantCallHandlingAssociation](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallhandlingassociation). ## EXAMPLES @@ -80,8 +82,6 @@ This example creates a fixed schedule that is active from December 24, 2017 to D ### -------------------------- Example 5 -------------------------- ```powershell -$dtr1 = New-CsOnlineDateTimeRange -Start "24/12/2017" -End "26/12/2017" -$dtr2 = New-CsOnlineDateTimeRange -Start "24/12/2018" -End "26/12/2018" $notInEffectSchedule = New-CsOnlineSchedule -Name "NotInEffect" -FixedSchedule ``` @@ -96,7 +96,7 @@ The Name parameter represents a unique friendly name for the schedule. Type: System.String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -112,7 +112,7 @@ The WeeklyRecurrentSchedule parameter indicates that a weekly recurrent schedule Type: SwitchParameter Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -128,7 +128,7 @@ List of time ranges for that day. Type: System.Collections.Generic.List Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -144,7 +144,7 @@ List of time ranges for that day. Type: System.Collections.Generic.List Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -160,7 +160,7 @@ List of time ranges for that day. Type: System.Collections.Generic.List Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -176,7 +176,7 @@ List of time ranges for that day. Type: System.Collections.Generic.List Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -192,7 +192,7 @@ List of time ranges for that day. Type: System.Collections.Generic.List Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -208,7 +208,7 @@ List of time ranges for that day. Type: System.Collections.Generic.List Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -224,7 +224,7 @@ List of time ranges for that day. Type: System.Collections.Generic.List Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -242,7 +242,7 @@ For example, if Complement is enabled and the schedule only contains time ranges Type: SwitchParameter Parameter Sets: WeeklyRecurrentSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -258,7 +258,7 @@ The FixedSchedule parameter indicates that a fixed schedule is to be created. Type: SwitchParameter Parameter Sets: FixedSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -274,7 +274,7 @@ List of date-time ranges for a fixed schedule. At most, 10 date-time ranges can Type: System.Collections.Generic.List Parameter Sets: FixedSchedule Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -289,7 +289,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -299,26 +299,26 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216).` +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### Microsoft.Rtc.Management.Hosted.Online.Models.Schedule - ## NOTES ## RELATED LINKS -[New-CsOnlineTimeRange](New-CsOnlineTimeRange.md) +[New-CsOnlineTimeRange](https://learn.microsoft.com/powershell/module/teams/new-csonlinetimerange) + +[New-CsOnlineDateTimeRange](https://learn.microsoft.com/powershell/module/teams/new-csonlinedatetimerange) -[New-CsOnlineDateTimeRange](New-CsOnlineDateTimeRange.md) +[New-CsAutoAttendantCallFlow](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallflow) -[New-CsOrganizationalAutoAttendantCallFlow](New-CsOrganizationalAutoAttendantCallFlow.md) +[New-CsAutoAttendantCallHandlingAssociation](https://learn.microsoft.com/powershell/module/teams/new-csautoattendantcallhandlingassociation) -[New-CsOrganizationalAutoAttendantCallHandlingAssociation](New-CsOrganizationalAutoAttendantCallHandlingAssociation.md) +[New-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/new-csautoattendant) diff --git a/teams/teams-ps/teams/New-CsOnlineTelephoneNumberOrder.md b/teams/teams-ps/teams/New-CsOnlineTelephoneNumberOrder.md new file mode 100644 index 0000000000..e60b5f483c --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineTelephoneNumberOrder.md @@ -0,0 +1,276 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder +Module Name: MicrosoftTeams +title: New-CsOnlineTelephoneNumberOrder +schema: 2.0.0 +manager: mreddy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: julienp +--- + +# New-CsOnlineTelephoneNumberOrder + +## SYNOPSIS +Use the `New-CsOnlineTelephoneNumberOrder` cmdlet to create a telephone number search order. The telephone numbers can then be used to set up calling features for users and services in your organization. + +## SYNTAX + +``` +New-CsOnlineTelephoneNumberOrder [-Name] <orderName> [-Description] <orderDescription> [-Country] <countryCode> [-NumberType] <numberType> [-Quantity] <quantity> [-CivicAddressId] <civicAddressId> [-NumberPrefix] <numberPrefix> [-AreaCode] <areaCode> [<CommonParameters>] +``` + +## DESCRIPTION + +Use the `New-CsOnlineTelephoneNumberOrder` cmdlet to create a telephone number search order. The telephone numbers can then be used to set up calling features for users and services in your organization. Use the `Get-CsOnlineTelephoneNumberType` cmdlet to find out the supported types of searches for each NumberType and construct the search request demonstrated below: + +Telephone numbers can be created with 3 ways: + +- **Civic Address Search**: A telephone number search order can be created base on a given civic address ID. The service will look up the address and fulfill the search order using available telephone numbers local to the given address. For civic address based search, the parameter `CivicAddressId` is required. + +- **Number Prefix Search**: A telephone number search order can be created base on a given number prefix. The number prefix search allow the tenant to acquire telephone numbers with a fixed number prefix. For number prefix based search, the parameter `NumberPrefix` is required. + +- **Area Code Selection Search**: A telephone number search order can be created base on a give area code. Certain service numbers are only offered with a dedicated set of area codes. With area code selection search, the tenant can acquire the desired telephone numbers by area code. For area code selection based search, the parameter `AreaCode` is required. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> $orderId = New-CsOnlineTelephoneNumberOrder -Name "Example 1" -Description "Civic address search example" -Country "US" -NumberType "UserSubscriber" -Quantity 1 -CivicAddressId 3b175352-4131-431e-970c-273226b8fb46 +PS C:\> $order = Get-CsOnlineTelephoneNumberOrder -OrderId $orderId + +AreaCode : +CivicAddressId : 3b175352-4131-431e-970c-273226b8fb46 +CountryCode : US +CreatedAt : 8/23/2021 5:43:44 PM +Description : Civic address search example +ErrorCode : NoError +Id : 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 +InventoryType : Subscriber +IsManual : False +Name : Example 1 +NumberPrefix : +NumberType : UserSubscriber +Quantity : 1 +ReservationExpiryDate : 8/23/2021 5:59:45 PM +SearchType : CivicAddress +SendToServiceDesk : False +Status : Reserved +TelephoneNumber : {Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.TelephoneNumberSearchResult} + +PS C:\> $order.TelephoneNumber + +Location TelephoneNumber +-------- --------------- +New York City +17182000004 +``` + +This example demonstrates a civic address based telephone number search. Telephone number +17182000004 is found to belong to the given address and is reserved for purchase. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> $orderId = New-CsOnlineTelephoneNumberOrder -Name "Example 2" -Description "Number prefix search example" -Country "US" -NumberType "UserSubscriber" -Quantity 1 -NumberPrefix 1425 +PS C:\> $order = Get-CsOnlineTelephoneNumberOrder -OrderId $orderId + +AreaCode : +CivicAddressId : +CountryCode : US +CreatedAt : 8/23/2021 5:43:44 PM +Description : Number prefix search example +ErrorCode : NoError +Id : 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 +InventoryType : Subscriber +IsManual : False +Name : Example 2 +NumberPrefix : +NumberType : UserSubscriber +Quantity : 1 +ReservationExpiryDate : 8/23/2021 5:59:45 PM +SearchType : Prefix +SendToServiceDesk : False +Status : Reserved +TelephoneNumber : {Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.TelephoneNumberSearchResult} + +PS C:\> $order.TelephoneNumber + +Location TelephoneNumber +-------- --------------- +Bellevue +14252000004 +``` + +This example demonstrates a number prefix based telephone number search. Telephone number +14252000004 is found to have the desired number prefix and is reserved for purchase. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> $orderId = New-CsOnlineTelephoneNumberOrder -Name "Example 3" -Description "Area code selection search example" -Country "US" -NumberType "ConferenceTollFree" -Quantity 1 -AreaCode 800 +PS C:\> $order = Get-CsOnlineTelephoneNumberOrder -OrderId $orderId + +AreaCode : +CivicAddressId : +CountryCode : US +CreatedAt : 8/23/2021 5:43:44 PM +Description : Area code selection search example +ErrorCode : NoError +Id : 1efd85ca-dd46-41b3-80a0-2e4c5f87c912 +InventoryType : Service +IsManual : False +Name : Example 3 +NumberPrefix : +NumberType : ConferenceTollFree +Quantity : 1 +ReservationExpiryDate : 8/23/2021 5:59:45 PM +SearchType : AreaCodeSelection +SendToServiceDesk : False +Status : Reserved +TelephoneNumber : {Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.TelephoneNumberSearchResult} + +PS C:\> $order.TelephoneNumber + +Location TelephoneNumber +-------- --------------- +Toll Free +18002000004 +``` + +This example demonstrates an area code selection based telephone number search. Telephone number +18002000004 is found to have the desired area code and is reserved for purchase. + +## PARAMETERS + +### Name +Specifies the telephone number search order name. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### Description +Specifies the telephone number search order description. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### Country +Specifies the telephone number search order country/region. Use `Get-CsOnlineTelephoneNumberCountry` to find the supported countries/regions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### NumberType +Specifies the telephone number search order number type. Use `Get-CsOnlineTelephoneNumberType` to find the supported number types. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### Quantity +Specifies the telephone number search order quantity. The number of allowed quantity is based on the tenant licenses. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CivicAddressId +Specifies the telephone number search order civic address. CivicAddressId is required for civic address based search and when RequiresCivicAddress is true for a given NumberType. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### NumberPrefix +Specifies the telephone number search order number prefix. NumberPrefix is required for number prefix based search. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### AreaCode +Specifies the telephone number search order number area code. AreaCode is required for area code selection based search. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineTelephoneNumberCountry](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbercountry) +[Get-CsOnlineTelephoneNumberType](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumbertype) + +[New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinetelephonenumberorder) +[Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) +[Complete-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/complete-csonlinetelephonenumberorder) +[Clear-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/clear-csonlinetelephonenumberorder) diff --git a/teams/teams-ps/teams/New-CsOnlineTelephoneNumberReleaseOrder.md b/teams/teams-ps/teams/New-CsOnlineTelephoneNumberReleaseOrder.md new file mode 100644 index 0000000000..b9ccb97cab --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineTelephoneNumberReleaseOrder.md @@ -0,0 +1,144 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version:online version: https://learn.microsoft.com/powershell/module/teams/New-csonlinetelephonenumberreleaseorder +applicable: Microsoft Teams +title: New-CsOnlineTelephoneNumberReleaseOrder +author: pavellatif +ms.author: pavellatif +ms.reviewer: pavellatif +manager: roykuntz +schema: 2.0.0 +--- + +# New-CsOnlineTelephoneNumberReleaseOrder + +## SYNOPSIS +This cmdlet creates a request to release Direct Routing telephone numbers from Microsoft Teams telephone number management inventory. + +## SYNTAX + +``` +New-CsOnlineTelephoneNumberReleaseOrder [-TelephoneNumber <String>] [-StartingNumber <String>] [-EndingNumber <String>] [-FileContent <Byte[]>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet releases existing Direct Routing telephone numbers from Microsoft Teams telephone number management inventory. Once released the phone numbers will not be visible in Teams PowerShell as acquired Direct Routing phone numbers. A maximum of 1,000 phone numbers can be released at a time. If more than 1,000 numbers need to be released, the requests should be divided into multiple increments of up to 1,000 numbers. + +The cmdlet is an asynchronous operation and will return an OrderId as output. You can use the [Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) cmdlet to check the status of the OrderId, including any error or warning messages that might result from the operation: `Get-CsOnlineTelephoneNumberOrder -OrderType Release -OrderId "orderId"`. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsOnlineTelephoneNumberReleaseOrder -TelephoneNumber "+123456789" +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c13 +``` + +In this example, a new Direct Routing telephone number "+123456789" is being released from Microsoft Teams telephone number management inventory. The output of the cmdlet is the OrderId that can be used with the [Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) cmdlet to retrieve the status of the order: `Get-CsOnlineTelephoneNumberOrder -OrderType Release -OrderId "orderId"`. + +### Example 2 +```powershell +PS C:\> New-CsOnlineTelephoneNumberReleaseOrder -TelephoneNumber "+123456789,+134567890,+145678901" +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c13 +``` + +In this example, a list of Direct Routing telephone numbers are being released from Microsoft Teams telephone number management. The output of the cmdlet is the OrderId that can be used with the [Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) cmdlet to retrieve the status of the order: `Get-CsOnlineTelephoneNumberOrder -OrderType Release -OrderId "orderId"`. + +### Example 3 +```powershell +PS C:\> New-CsOnlineTelephoneNumberReleaseOrder -StartingNumber "+12000000" -EndingNumber "+12000009" +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c13 +``` + +In this example, a range of Direct Routing telephone numbers from "+12000000" to "+12000009" are being released from Microsoft Teams telephone number management. The output of the cmdlet is the OrderId that can be used with the [Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) cmdlet to retrieve the status of the order: `Get-CsOnlineTelephoneNumberOrder -OrderType Release -OrderId "orderId"`. + +### Example 4 +```powershell +PS C:\> $drlist = [System.IO.File]::ReadAllBytes("C:\Users\testuser\DrNumber.csv") +PS C:\> New-CsOnlineTelephoneNumberReleaseOrder -FileContent $drlist +cdf3073a-6fbb-4ade-a8af-e8fa1f3b9c13 +``` + +In this example, the content of a file with a list of Direct Routing telephone numbers are being released via file upload. The file should be in Comma Separated Values (CSV) file format and should only contain the list of DR numbers to be released. The New-CsOnlineTelephoneNumberReleaseOrder cmdlet is only used to pass the content. To read the output of this cmdlet and retrieve the status of your order, you can use OrderId with the [Get-CsOnlineTelephoneNumberOrder](./get-csonlinetelephonenumberorder.md) cmdlet : `Get-CsOnlineTelephoneNumberOrder -OrderType Release -OrderId "orderId"`. + +## PARAMETERS + +### -TelephoneNumber +This is the Direct Routing telephone number you wish to release from Microsoft Teams telephone number management inventory. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StartingNumber +This is the starting number of a range of Direct Routing telephone number you wish to release from Microsoft Teams telephone number management inventory. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndingNumber +This is the ending number of a range of Direct Routing telephone number you wish to release from Microsoft Teams telephone number management inventory. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileContent +This is the content of a .csv file that includes the Direct Routing telephone numbers to be released from the Microsoft Teams telephone number management inventory. This parameter can be used to release up to 1,000 numbers at a time. + +```yaml +Type: Byte[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.String + +## NOTES +The cmdlet is available in Teams PowerShell module 6.7.1 or later. + +The cmdlet is only available in commercial and GCC cloud instances. + +## RELATED LINKS +[Get-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumberorder) +[New-CsOnlineDirectRoutingTelephoneNumberUploadOrder](https://learn.microsoft.com/powershell/module/teams/new-csonlinedirectroutingtelephonenumberuploadorder) \ No newline at end of file diff --git a/teams/teams-ps/teams/New-CsOnlineTimeRange.md b/teams/teams-ps/teams/New-CsOnlineTimeRange.md new file mode 100644 index 0000000000..e331b4ffe5 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineTimeRange.md @@ -0,0 +1,110 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinetimerange +applicable: Microsoft Teams +title: New-CsOnlineTimeRange +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsOnlineTimeRange + +## SYNOPSIS +The New-CsOnlineTimeRange cmdlet creates a new time range. + +## SYNTAX + +``` +New-CsOnlineTimeRange -Start <TimeSpan> -End <TimeSpan> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The New-CsOnlineTimeRange cmdlet creates a new time range to be used with the Auto Attendant (AA) service. Time ranges are used to form schedules. + +**NOTES**: + +- The start bound of the range must be less than its end bound. +- Time ranges within a weekly recurrent schedule must align with 15-minute boundaries. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$workdayTimeRange = New-CsOnlineTimeRange -Start 09:00 -End 17:00 +``` + +This example creates a time range for a 9AM to 5PM work day. + +### -------------------------- Example 2 -------------------------- +``` +$allDayTimeRange = New-CsOnlineTimeRange -Start 00:00 -End 1.00:00 +``` + +This example creates a 24-hour time range. + +## PARAMETERS + +### -Start +The Start parameter represents the start bound of the time range. + +```yaml +Type: System.TimeSpan +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -End +The End parameter represents the end bound of the time range. + +```yaml +Type: System.TimeSpan +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.TimeRange + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsOnlineVoiceRoute.md b/teams/teams-ps/teams/New-CsOnlineVoiceRoute.md new file mode 100644 index 0000000000..270d9deed1 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineVoiceRoute.md @@ -0,0 +1,249 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroute +applicable: Microsoft Teams +title: New-CsOnlineVoiceRoute +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsOnlineVoiceRoute + +## SYNOPSIS +Creates a new online voice route. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). + +## SYNTAX + +### Identity (Default) +``` +New-CsOnlineVoiceRoute [-Identity] <String> [-BridgeSourcePhoneNumber <String>] [-Description <String>] + [-NumberPattern <String>] [-OnlinePstnGatewayList <Object>] [-OnlinePstnUsages <Object>] [-Priority <Int32>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsOnlineVoiceRoute [-BridgeSourcePhoneNumber <String>] [-Description <String>] [-NumberPattern <String>] + [-OnlinePstnGatewayList <Object>] [-OnlinePstnUsages <Object>] [-Priority <Int32>] + -Name <String> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to create a new online voice route. All online voice routes are created at the Global scope. However, multiple global voice routes can be defined. This is accomplished through the Identity parameter, which requires a unique route name. + +Voice routes are associated with online voice policies through online PSTN usages. A voice route includes a regular expression that identifies which phone numbers will be routed through a given voice route: phone numbers matching the regular expression will be routed through this route. + +This cmdlet is used when configuring Microsoft Phone System Direct Routing. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> New-CsOnlineVoiceRoute -Identity Route1 +``` + +The command in this example creates a new online voice route with an Identity of Route1. All other properties will be set to the default values. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> New-CsOnlineVoiceRoute -Identity Route1 -OnlinePstnUsages @{add="Long Distance"} -OnlinePstnGatewayList @{add="sbc1.litwareinc.com"} +``` + +The command in this example creates a new online voice route with an Identity of Route1. It also adds the online PSTN usage Long Distance to the list of usages and the service ID PstnGateway sbc1.litwareinc.com to the list of online PSTN gateways. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> $x = (Get-CsOnlinePstnUsage).Usage + +New-CsOnlineVoiceRoute -Identity Route1 -OnlinePstnUsages @{add=$x} +``` + +This example creates a new online voice route named Route1 and populates that route's list of PSTN usages with all the existing usages for the organization. The first command in this example retrieves the list of global online PSTN usages. Notice that the call to the `Get-CsOnlinePstnUsage` cmdlet is in parentheses; this means that we first retrieve an object containing PSTN usage information. (Because there is only one, global, online PSTN usage, only one object will be retrieved.) The command then retrieves the Usage property of this object. That property, which contains a list of usages, is assigned to the variable $x. In the second line of this example, the `New-CsOnlineVoiceRoute` cmdlet is called to create a new online voice route. This voice route will have an identity of Route1. Notice the value passed to the OnlinePstnUsages parameter: @{add=$x}. This value says to add the contents of $x, which contain the phone usages list retrieved in line 1, to the list of online PSTN usages for this route. + +## PARAMETERS + +### -BridgeSourcePhoneNumber +BridgeSourcePhoneNumber is an E.164 formatted Operator Connect Conferencing phone number assigned to your Audio Conferencing Bridge. Using BridgeSourcePhoneNumber in an online voice route is mutually exclusive with using OnlinePstnGatewayList in the same online voice route. + +When using BridgeSourcePhoneNumber in an online voice route, the OnlinePstnUsages used in the online voice route should only be used in a corresponding OnlineAudioConferencingRoutingPolicy. The same OnlinePstnUsages should not be used in online voice routes that are not using BridgeSourcePhoneNumber. + +For more information about Operator Connect Conferencing, please see [Configure Operator Connect Conferencing](https://learn.microsoft.com/microsoftteams/operator-connect-conferencing-configure). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +A description of what this online voice route is for. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A name that uniquely identifies the online voice route. Voice routes can be defined only at the global scope, so the identity is simply the name you want to give the route. (You can have spaces in the route name, for instance Test Route, but you must enclose the full string in double quotes in the call to the New-CsOnlineVoiceRoute cmdlet.) + +If Identity is specified, the Name must be left blank. The value of the Identity will be assigned to the Name. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The unique name of the voice route. If this parameter is set, the value will be automatically applied to the online voice route Identity. You cannot specify both an Identity and a Name. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberPattern +A regular expression that specifies the phone numbers to which this route applies. Numbers matching this pattern will be routed according to the rest of the routing settings. + +Default: [0-9]{10} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnGatewayList +This parameter contains a list of online gateways associated with this online voice route. Each member of this list must be the service Identity of the online PSTN gateway. The service Identity is the fully qualified domain name (FQDN) of the pool or the IP address of the server. For example, redmondpool.litwareinc.com. + +By default this list is empty. However, if you leave this parameter blank when creating a new voice route, you'll receive a warning message. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnUsages +A list of online PSTN usages (such as Local, Long Distance, etc.) that can be applied to this online voice route. The PSTN usage must be an existing usage (PSTN usages can be retrieved by calling the Get-CsOnlinePstnUsage cmdlet). + +By default this list is empty. However, if you leave this parameter blank when creating a new online voice route, you'll receive a warning message. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +A number could resolve to multiple online voice routes. The priority determines the order in which the routes will be applied if more than one route is possible. The lowest priority will be applied first and then in ascendant order. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroute) + +[Set-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroute) + +[Remove-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroute) diff --git a/teams/teams-ps/teams/New-CsOnlineVoiceRoutingPolicy.md b/teams/teams-ps/teams/New-CsOnlineVoiceRoutingPolicy.md new file mode 100644 index 0000000000..a4646da2fa --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineVoiceRoutingPolicy.md @@ -0,0 +1,160 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroutingpolicy +applicable: Microsoft Teams +title: New-CsOnlineVoiceRoutingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsOnlineVoiceRoutingPolicy + +## SYNOPSIS +Creates a new online voice routing policy. Online voice routing policies manage online PSTN usages for Phone System users. + +## SYNTAX + +### Identity +``` +New-CsOnlineVoiceRoutingPolicy [-Identity] <string> [-Description <string>] [-OnlinePstnUsages <Object>] [-RouteType <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. + +Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> New-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages "Long Distance" +``` + +The command shown in Example 1 creates a new online per-user voice routing policy with the Identity RedmondOnlineVoiceRoutingPolicy. This policy is assigned a single online PSTN usage: Long Distance. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> New-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages "Long Distance", "Local", "Internal" +``` + +Example 2 is a variation of the command shown in Example 1; in this case, however, the new policy is assigned three online PSTN usages: Long Distance; Local; Internal. Multiple usages can be assigned simply by separating each usage using a comma. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany an online voice routing policy. For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnUsages +A list of online PSTN usages (such as Local or Long Distance) that can be applied to this online voice routing policy. The online PSTN usage must be an existing usage (PSTN usages can be retrieved by calling the `Get-CsOnlinePstnUsage` cmdlet). + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RouteType +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroutingpolicy) + +[Set-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroutingpolicy) + +[Grant-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoiceroutingpolicy) + +[Remove-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroutingpolicy) diff --git a/teams/teams-ps/teams/New-CsOnlineVoicemailPolicy.md b/teams/teams-ps/teams/New-CsOnlineVoicemailPolicy.md new file mode 100644 index 0000000000..04a4f92099 --- /dev/null +++ b/teams/teams-ps/teams/New-CsOnlineVoicemailPolicy.md @@ -0,0 +1,308 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csonlinevoicemailpolicy +applicable: Microsoft Teams +title: New-CsOnlineVoicemailPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsOnlineVoicemailPolicy + +## SYNOPSIS +Creates a new Online Voicemail policy. Online Voicemail policies determine whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify voicemail maximum recording length for a user and the primary and secondary voicemail system prompt languages. + +## SYNTAX + +### Identity (Default) + +```powershell +New-CsOnlineVoicemailPolicy [-Identity] <string> [-EnableEditingCallAnswerRulesSetting <boolean>] [-EnableTranscription <boolean>] +[-EnableTranscriptionProfanityMasking <boolean>] [-EnableTranscriptionTranslation <boolean>] [-MaximumRecordingLength <timespan>] +[-PostAmbleAudioFile <string>] [-PreambleAudioFile <string>] [-PreamblePostambleMandatory <boolean>] +[-PrimarySystemPromptLanguage <string>] [-SecondarySystemPromptLanguage <string>] [-ShareData <string>] [-WhatIf] [-Confirm] [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Cloud Voicemail service provides organizations with voicemail deposit capabilities for Phone System implementation. + +By default, users enabled for Phone System will be enabled for Cloud Voicemail. The Online Voicemail policy controls whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify the voicemail maximum recording length for a user and the primary and secondary voicemail system prompt languages. + +- Voicemail transcription is enabled by default +- Transcription profanity masking is disabled by default +- Transcription translation is enabled by default +- Editing call answer rule settings is enabled by default +- Voicemail maximum recording length is set to 5 minutes by default +- Primary and secondary system prompt languages are set to null by default and the user's voicemail language setting is used + +Tenant admin would be able to create a customized online voicemail policy to match the organization's requirements. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +New-CsOnlineVoicemailPolicy -Identity "CustomOnlineVoicemailPolicy" -MaximumRecordingLength ([TimeSpan]::FromSeconds(60)) +``` + +The command shown in Example 1 creates a per-user online voicemail policy CustomOnlineVoicemailPolicy with MaximumRecordingLength set to 60 seconds and other fields set to tenant level global value. + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -EnableEditingCallAnswerRulesSetting +Controls if editing call answer rule settings are enabled or disabled for a user. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTranscription +Allows you to disable or enable voicemail transcription. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTranscriptionProfanityMasking +Allows you to disable or enable profanity masking for the voicemail transcriptions. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTranscriptionTranslation +Allows you to disable or enable translation for the voicemail transcriptions. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaximumRecordingLength +A duration of voicemail maximum recording length. The length should be between 30 seconds to 10 minutes. + +```yaml +Type: Duration +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostambleAudioFile +The audio file to play to the caller after the user's voicemail greeting has played and before the caller is allowed to leave a voicemail message. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -PreambleAudioFile +The audio file to play to the caller before the user's voicemail greeting is played. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreamblePostambleMandatory +Is playing the Pre- or Post-amble mandatory before the caller can leave a message. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySystemPromptLanguage +The primary (or first) language that voicemail system prompts will be presented in. Must also set SecondarySystemPromptLanguage. When set, this overrides the user language choice. Please see [Set-CsOnlineVoicemailUserSettings](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailusersettings) -PromptLanguage for supported languages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SecondarySystemPromptLanguage +The secondary language that voicemail system prompts will be presented in. Must also set PrimarySystemPromptLanguage and may not be the same value as PrimarySystemPromptanguage. When set, this overrides the user language choice. Please see [Set-CsOnlineVoicemailUserSettings](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailusersettings) -PromptLanguage for supported languages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShareData +Specifies whether voicemail and transcription data are shared with the service for training and improving accuracy. Possible values are Defer and Deny. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoicemailpolicy) + +[Set-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailpolicy) + +[Remove-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoicemailpolicy) + +[Grant-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoicemailpolicy) diff --git a/teams/teams-ps/teams/New-CsSdgBulkSignInRequest.md b/teams/teams-ps/teams/New-CsSdgBulkSignInRequest.md new file mode 100644 index 0000000000..3c44267712 --- /dev/null +++ b/teams/teams-ps/teams/New-CsSdgBulkSignInRequest.md @@ -0,0 +1,92 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +online version: +title: New-CsSdgBulkSignInRequest +schema: 2.0.0 +--- + +# New-CsSdgBulkSignInRequest + +## SYNOPSIS +Use the New-CsSdgBulkSignInRequest cmdlet to sign in a batch of up to 100 devices. + +## SYNTAX + +``` +New-CsSdgBulkSignInRequest -DeviceDetailsFilePath <String> -Region <String> [<CommonParameters>] +``` + +## DESCRIPTION +Bulk Sign In for Teams SIP Gateway enables you to sign in a batch of devices in one go. This feature is intended for admins and works for shared devices. +The password for the shared device account is reset at runtime to an unknown value and the cmdlet uses the new credential for fetching token from Entra ID. Admins can sign in shared account remotely and in bulk using this feature. + +## EXAMPLES + +### Example 1 +```powershell +Import-Module MicrosoftTeams +$credential = Get-Credential // Enter your admin's email and password +Connect-MicrosoftTeams -Credential $credential +$newBatchResponse = New-CsSdgBulkSignInRequest -DeviceDetailsFilePath .\Example.csv -Region APAC +``` + +This example shows how to connect to Microsoft Teams PowerShell module, and read the output of the New-SdgBulkSignInRequest cmdlet into a variable newBatchResponse. The cmdlet uses Example.csv as the device details file, and SIP Gateway region as APAC. + +### Example 2 +```powershell +$newBatchResponse = New-CsSdgBulkSignInRequest -DeviceDetailsFilePath .\Example.csv -Region APAC +$newBatchResponse.BatchId +$getBatchStatusResponse = Get-CsSdgBulkSignInRequestStatus -Batchid $newBatchResponse.BatchId +$getBatchStatusResponse | ft +$getBatchStatusResponse.BatchItem +``` +This example shows how to view the status of a bulk sign in batch. + +## PARAMETERS + +### -DeviceDetailsFilePath +This is the path of the device details CSV file. The CSV file contains two columns - username and hardware ID, where username is of the format FirstFloorLobbyPhone1@contoso.com and hardware ID is the device MAC address in the format 1A-2B-3C-4D-5E-6F + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Region +This is the SIP Gateway region. Possible values include NOAM, EMEA, APAC. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsSharedCallQueueHistoryTemplate.md b/teams/teams-ps/teams/New-CsSharedCallQueueHistoryTemplate.md new file mode 100644 index 0000000000..f71b11582d --- /dev/null +++ b/teams/teams-ps/teams/New-CsSharedCallQueueHistoryTemplate.md @@ -0,0 +1,136 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/New-CsSharedCallQueueHistoryTemplate +applicable: Microsoft Teams +title: New-CsSharedCallQueueHistoryTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsSharedCallQueueHistoryTemplate + +## SYNTAX + +```powershell +New-CsSharedCallQueueHistoryTemplate -Name <String> -Description <String> [-IncomingMissedCalls <Object>] [-AnsweredAndOutboundCalls <Object>] [<CommonParameters>] +``` + +## DESCRIPTION +Use the New-CsSharedCallQueueHistory cmdlet to create a Shared Call Queue History template. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +New-CsSharedCallQueueHistoryTemplate -Name "Customer Service" -Description "Missed:All Answered:Auth" -IncomingMissedCall XXXXXX -AnsweredAndOutboundCalls XXXXX +``` + +This example creates a new Shared CallQueue History template where incoming missed calls are shown to authorized users and agents and, answered and outbound calls are shown to authorized users only. + +## PARAMETERS + +### -Name +The name of the shared call queue history template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +A description for the shared call queue history template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncomingMissedCalls +A description for the shared call queue history template. + +PARAMVALUE: Off | AuthorizedUsersOnly | AuthorizedUsersAndAgents + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Off +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnsweredAndOutboundCalls +A description for the shared call queue history template. + +PARAMVALUE: Off | AuthorizedUsersOnly | AuthorizedUsersAndAgents + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Off +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[Get-CsSharedCallQueueHistoryTemplate](./Get-CsSharedCallQueueHistoryTemplate.md) + +[Set-CsSharedCallQueueHistoryTemplate](./Set-CsSharedCallQueueHistoryTemplate.md) + +[Remove-CsSharedCallQueueHistoryTemplate](./Remove-CsSharedCallQueueHistoryTemplate.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + + + diff --git a/teams/teams-ps/teams/New-CsTeamTemplate.md b/teams/teams-ps/teams/New-CsTeamTemplate.md new file mode 100644 index 0000000000..4230e09bf3 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamTemplate.md @@ -0,0 +1,810 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamtemplate +title: New-CsTeamTemplate +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +schema: 2.0.0 +--- + +# New-CsTeamTemplate + +## SYNOPSIS + +This cmdlet lets you provision a new team template for use in Microsoft Teams. To learn more about team templates, see [Get started with Teams templates in the admin center](https://learn.microsoft.com/microsoftteams/get-started-with-teams-templates-in-the-admin-console). + +NOTE: The response is a PowerShell object formatted as a JSON for readability. Please refer to the examples for suggested interaction flows for template management. + +## SYNTAX + +### NewExpanded (Default) + +```powershell +New-CsTeamTemplate -Locale <String> -DisplayName <String> -ShortDescription <String> + [-App <ITeamsAppTemplate[]>] [-Category <String[]>] [-Channel <IChannelTemplate[]>] + [-Classification <String>] [-Description <String>] [-DiscoverySetting <ITeamDiscoverySettings>] + [-FunSetting <ITeamFunSettings>] [-GuestSetting <ITeamGuestSettings>] [-Icon <String>] + [-IsMembershipLimitedToOwner] [-MemberSetting <ITeamMemberSettings>] + [-MessagingSetting <ITeamMessagingSettings>] [-OwnerUserObjectId <String>] [-PublishedBy <String>] + [-Specialization <String>] [-TemplateId <String>] [-Uri <String>] [-Visibility <String>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### New + +```powershell +New-CsTeamTemplate -Locale <String> -Body <ITeamTemplate> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### NewViaIdentity + +```powershell +New-CsTeamTemplate -InputObject <IConfigApiBasedCmdletsIdentity> -Body <ITeamTemplate> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### NewViaIdentityExpanded + +```powershell +New-CsTeamTemplate -InputObject <IConfigApiBasedCmdletsIdentity> -DisplayName <String> + -ShortDescription <String> [-App <ITeamsAppTemplate[]>] [-Category <String[]>] + [-Channel <IChannelTemplate[]>] [-Classification <String>] [-Description <String>] + [-DiscoverySetting <ITeamDiscoverySettings>] [-FunSetting <ITeamFunSettings>] + [-GuestSetting <ITeamGuestSettings>] [-Icon <String>] [-IsMembershipLimitedToOwner] + [-MemberSetting <ITeamMemberSettings>] [-MessagingSetting <ITeamMessagingSettings>] + [-OwnerUserObjectId <String>] [-PublishedBy <String>] [-Specialization <String>] [-TemplateId <String>] + [-Uri <String>] [-Visibility <String>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\> (Get-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/com.microsoft.teams.template.AdoptOffice365/Public/en-US') > input.json +# open json in your favorite editor, make changes + +PS C:\> New-CsTeamTemplate -Locale en-US -Body (Get-Content '.input.json' | Out-String) +``` + +Step 1: Create new template from copy of existing template. Gets the template JSON file of Template with specified OData ID, creates a JSON file user can make edits in. +Step 2: Create a new template from the JSON file named "input". + +### EXAMPLE 2 + +```powershell +PS C:\> $template = Get-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/com.microsoft.teams.template.AdoptOffice365/Public/en-US' +PS C:\> $template | Format-List # show the output object as it would be accessed + +PS C:\> $template.Category = $null # unset category to copy from public template +PS C:\> $template.DisplayName = 'New Template from object' +PS C:\> $template.Channel[1].DisplayName += ' modified' +## add a new channel to the channel list +PS C:\> $template.Channel += ` +@{ ` + displayName="test"; ` + id="b82b7d0a-6bc9-4fd8-bf09-d432e4ea0475"; ` + isFavoriteByDefault=$false; ` +} + +PS C:\> New-CsTeamTemplate -Locale en-US -Body $template +``` + +Create a template using a complex object syntax. + +### EXAMPLE 3 + +```powershell +PS C:\> $template = New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.TeamTemplate -Property @{` +DisplayName='New Template';` +ShortDescription='Short Definition';` +Description='New Description';` +App=@{id='feda49f8-b9f2-4985-90f0-dd88a8f80ee1'}, @{id='1d71218a-92ad-4254-be15-c5ab7a3e4423'};` +Channel=@{` + displayName = "General";` + id= "General";` + isFavoriteByDefault= $true` + },` + @{` + displayName= "test";` + id= "b82b7d0a-6bc9-4fd8-bf09-d432e4ea0475";` + isFavoriteByDefault= $false` + }` +} + +PS C:\> New-CsTeamTemplate -Locale en-US -Body $template +``` + +Create template from scratch + +> [!Note] +> It can take up to 24 hours for Teams users to see a custom template change in the gallery. + +## PARAMETERS + +### -App + +Gets or sets the set of applications that should be installed in teams created based on the template.The app catalog is the main directory for information about each app; this set is intended only as a reference. +To construct, see NOTES section for APP properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamsAppTemplate[] +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Body + +The client input for a request to create a template. +Only admins from Config Api can perform this request. +To construct, see NOTES section for BODY properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamTemplate +Parameter Sets: New, NewViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Category + +Gets or sets list of categories. + +```yaml +Type: System.String[] +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Channel + +Gets or sets the set of channel templates included in the team template. +To construct, see NOTES section for CHANNEL properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IChannelTemplate[] +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Classification + +Gets or sets the team's classification.Tenant admins configure Microsoft Entra ID with the set of possible values. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Gets or sets the team's Description. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DiscoverySetting + +Governs discoverability of a team. +To construct, see NOTES section for DISCOVERYSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamDiscoverySettings +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName + +Gets or sets the team's DisplayName. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FunSetting + +Governs use of fun media like giphy and stickers in the team. +To construct, see NOTES section for FUNSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamFunSettings +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GuestSetting + +Guest role settings for the team. +To construct, see NOTES section for GUESTSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamGuestSettings +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Icon + +Gets or sets template icon. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +Identity Parameter +To construct, see NOTES section for INPUTOBJECT properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity +Parameter Sets: NewViaIdentity, NewViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -IsMembershipLimitedToOwner + +Gets or sets whether to limit the membership of the team to owners in the Microsoft Entra group until an owner "activates" the team. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Locale + +```yaml +Type: System.String +Parameter Sets: New, NewExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MemberSetting + +Member role settings for the team. +To construct, see NOTES section for MEMBERSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamMemberSettings +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessagingSetting + +Governs use of messaging features within the teamThese are settings the team owner should be able to modify from UI after team creation. +To construct, see NOTES section for MESSAGINGSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamMessagingSettings +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OwnerUserObjectId + +Gets or sets the Microsoft Entra user object id of the user who should be set as the owner of the new team.Only to be used when an application or administrative user is making the request on behalf of the specified user. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublishedBy + +Gets or sets published name. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShortDescription + +Gets or sets template short description. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Specialization + +The specialization or use case describing the team.Used for telemetry/BI, part of the team context exposed to app developers, and for legacy implementations of differentiated features for education. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TemplateId + +Gets or sets the id of the base template for the team.Either a Microsoft base template or a custom template. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Uri + +Gets or sets uri to be used for GetTemplate api call. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Visibility + +Used to control the scope of users who can view a group/team and its members, and ability to join. + +```yaml +Type: System.String +Parameter Sets: NewExpanded, NewViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Break + +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend + +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend + +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy + +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential + +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials + +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamTemplate + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ICreateTemplateResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamTemplateErrorResponse + +## NOTES + +ALIASES + +COMPLEX PARAMETER PROPERTIES + +To create the parameters described below, construct a hash table containing the appropriate properties. For information on hash tables, run Get-Help about_Hash_Tables. + +APP <ITeamsAppTemplate[]>: Gets or sets the set of applications that should be installed in teams created based on the template.The app catalog is the main directory for information about each app; this set is intended only as a reference. + +- `[Id <String>]`: Gets or sets the app's ID in the global apps catalog. + +BODY \<ITeamTemplate\>: The client input for a request to create a template. Only admins from Config Api can perform this request. + +- `DisplayName <String>`: Gets or sets the team's DisplayName. +- `ShortDescription <String>`: Gets or sets template short description. +- `[App <ITeamsAppTemplate[]>]`: Gets or sets the set of applications that should be installed in teams created based on the template. The app catalog is the main directory for information about each app; this set is intended only as a reference. + - `[Id <String>]`: Gets or sets the app's ID in the global apps catalog. +- `[Category <String[]>]`: Gets or sets list of categories. +- `[Channel <IChannelTemplate[]>]`: Gets or sets the set of channel templates included in the team template. + - `[Description <String>]`: Gets or sets channel description as displayed to users. + - `[DisplayName <String>]`: Gets or sets channel name as displayed to users. + - `[Id <String>]`: Gets or sets identifier for the channel template. + - `[IsFavoriteByDefault <Boolean?>]`: Gets or sets a value indicating whether new members of the team should automatically favorite the channel, pinning it for visibility in the UI and using resources to make switching to the channel faster. + - `[Tab <IChannelTabTemplate[]>]`: Gets or sets collection of tabs that should be added to the channel. + - `[Configuration <ITeamsTabConfiguration>]`: Represents the configuration of a tab. + - `[ContentUrl <String>]`: Gets or sets the Url used for rendering tab contents in Teams. + - `[EntityId <String>]`: Gets or sets the identifier for the entity hosted by the tab provider. + - `[RemoveUrl <String>]`: Gets or sets the Url that is invoked when the user tries to remove a tab from the FE client. + - `[WebsiteUrl <String>]`: Gets or sets the Url for showing tab contents outside of Teams. + - `[Id <String>]`: Gets or sets identifier for the channel tab template. + - `[Key <String>]`: Gets a unique identifier. + - `[MessageId <String>]`: Gets or sets id used to identify the chat message associated with the tab. + - `[Name <String>]`: Gets or sets the tab name displayed to users. + - `[SortOrderIndex <String>]`: Gets or sets index of the order used for sorting tabs. + - `[TeamsAppId <String>]`: Gets or sets the app's id in the global apps catalog. + - `[WebUrl <String>]`: Gets or sets the deep link url of the tab instance. +- `[Classification <String>]`: Gets or sets the team's classification. Tenant admins configure Microsoft Entra ID with the set of possible values. +- `[Description <String>]`: Gets or sets the team's Description. +- `[DiscoverySetting <ITeamDiscoverySettings>]`: Governs discoverability of a team. + - `ShowInTeamsSearchAndSuggestion <Boolean>`: Gets or sets value indicating if team is visible within search and suggestions in Teams clients. +- `[FunSetting <ITeamFunSettings>]`: Governs use of fun media like giphy and stickers in the team. + - `AllowCustomMeme <Boolean>`: Gets or sets a value indicating whether users are allowed to create and post custom meme images in team conversations. + - `AllowGiphy <Boolean>`: Gets or sets a value indicating whether users can post giphy content in team conversations. + - `AllowStickersAndMeme <Boolean>`: Gets or sets a value indicating whether users can post stickers and memes in team conversations. + - `GiphyContentRating <String>`: Gets or sets the rating filter on giphy content. +- `[GuestSetting <ITeamGuestSettings>]`: Guest role settings for the team. + - `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether guests can create or edit channels in the team. + - `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether guests can delete team channels. +- `[Icon <String>]`: Gets or sets template icon. +- `[IsMembershipLimitedToOwner <Boolean?>]`: Gets or sets whether to limit the membership of the team to owners in the Microsoft Entra group until an owner "activates" the team. +- `[MemberSetting <ITeamMemberSettings>]`: Member role settings for the team. + - `AllowAddRemoveApp <Boolean>`: Gets or sets a value indicating whether members can add or remove apps in the team. + - `AllowCreatePrivateChannel <Boolean>`: Gets or Sets a value indicating whether members can create Private channels. + - `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether members can create or edit channels in the team. + - `AllowCreateUpdateRemoveConnector <Boolean>`: Gets or sets a value indicating whether members can add, edit, or remove connectors in the team. + - `AllowCreateUpdateRemoveTab <Boolean>`: Gets or sets a value indicating whether members can add, edit or remove pinned tabs in the team. + - `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether members can delete team channels. + - `UploadCustomApp <Boolean>`: Gets or sets a value indicating is allowed to upload custom apps. +- `[MessagingSetting <ITeamMessagingSettings>]`: Governs use of messaging features within the team These are settings the team owner should be able to modify from UI after team creation. + - `AllowChannelMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention entire channels in team conversations. + - `AllowOwnerDeleteMessage <Boolean>`: Gets or sets a value indicating whether team owners can delete anyone's messages in team conversations. + - `AllowTeamMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention the entire team in team conversations. + - `AllowUserDeleteMessage <Boolean>`: Gets or sets a value indicating whether team members can delete their own messages in team conversations. + - `AllowUserEditMessage <Boolean>`: Gets or sets a value indicating whether team members can edit their own messages in team conversations. +- `[OwnerUserObjectId <String>]`: Gets or sets the Microsoft Entra user object id of the user who should be set as the owner of the new team. Only to be used when an application or administrative user is making the request on behalf of the specified user. +- `[PublishedBy <String>]`: Gets or sets published name. +- `[Specialization <String>]`: The specialization or use case describing the team. Used for telemetry/BI, part of the team context exposed to app developers, and for legacy implementations of differentiated features for education. +- `[TemplateId <String>]`: Gets or sets the id of the base template for the team. Either a Microsoft base template or a custom template. +- `[Uri <String>]`: Gets or sets uri to be used for GetTemplate api call. +- `[Visibility <String>]`: Used to control the scope of users who can view a group/team and its members, and ability to join. + +CHANNEL <IChannelTemplate[]>: Gets or sets the set of channel templates included in the team template. + +- `[Description <String>]`: Gets or sets channel description as displayed to users. +- `[DisplayName <String>]`: Gets or sets channel name as displayed to users. +- `[Id <String>]`: Gets or sets identifier for the channel template. +- `[IsFavoriteByDefault <Boolean?>]`: Gets or sets a value indicating whether new members of the team should automatically favorite the channel, pinning it for visibility in the UI and using resources to make switching to the channel faster. +- `[Tab <IChannelTabTemplate[]>]`: Gets or sets collection of tabs that should be added to the channel. + - `[Configuration <ITeamsTabConfiguration>]`: Represents the configuration of a tab. + - `[ContentUrl <String>]`: Gets or sets the Url used for rendering tab contents in Teams. + - `[EntityId <String>]`: Gets or sets the identifier for the entity hosted by the tab provider. + - `[RemoveUrl <String>]`: Gets or sets the Url that is invoked when the user tries to remove a tab from the FE client. + - `[WebsiteUrl <String>]`: Gets or sets the Url for showing tab contents outside of Teams. + - `[Id <String>]`: Gets or sets identifier for the channel tab template. + - `[Key <String>]`: Gets a unique identifier. + - `[MessageId <String>]`: Gets or sets id used to identify the chat message associated with the tab. + - `[Name <String>]`: Gets or sets the tab name displayed to users. + - `[SortOrderIndex <String>]`: Gets or sets index of the order used for sorting tabs. + - `[TeamsAppId <String>]`: Gets or sets the app's id in the global apps catalog. + - `[WebUrl <String>]`: Gets or sets the deep link url of the tab instance. + +DISCOVERYSETTING \<ITeamDiscoverySettings\>: Governs discoverability of a team. + +- `ShowInTeamsSearchAndSuggestion <Boolean>`: Gets or sets value indicating if team is visible within search and suggestions in Teams clients. + +FUNSETTING \<ITeamFunSettings\>: Governs use of fun media like giphy and stickers in the team. + +- `AllowCustomMeme <Boolean>`: Gets or sets a value indicating whether users are allowed to create and post custom meme images in team conversations. +- `AllowGiphy <Boolean>`: Gets or sets a value indicating whether users can post giphy content in team conversations. +- `AllowStickersAndMeme <Boolean>`: Gets or sets a value indicating whether users can post stickers and memes in team conversations. +- `GiphyContentRating <String>`: Gets or sets the rating filter on giphy content. + +GUESTSETTING \<ITeamGuestSettings\>: Guest role settings for the team. + +- `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether guests can create or edit channels in the team. +- `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether guests can delete team channels. + +INPUTOBJECT \<IConfigApiBasedCmdletsIdentity\>: Identity Parameter + +- `[Bssid <String>]`: +- `[ChassisId <String>]`: +- `[CivicAddressId <String>]`: Civic address id. +- `[Country <String>]`: +- `[GroupId <String>]`: The ID of a group whose policy assignments will be returned. +- `[Id <String>]`: +- `[Identity <String>]`: +- `[Locale <String>]`: +- `[LocationId <String>]`: Location id. +- `[OdataId <String>]`: A composite URI of a template. +- `[OperationId <String>]`: The ID of a batch policy assignment operation. +- `[OrderId <String>]`: +- `[PackageName <String>]`: The name of a specific policy package +- `[PolicyType <String>]`: The policy type for which group policy assignments will be returned. +- `[Port <String>]`: +- `[PortInOrderId <String>]`: +- `[PublicTemplateLocale <String>]`: Language and country code for localization of publicly available templates. +- `[SubnetId <String>]`: +- `[TenantId <String>]`: +- `[UserId <String>]`: UserId. Supports Guid. Eventually UPN and SIP. + +MEMBERSETTING \<ITeamMemberSettings\>: Member role settings for the team. + +- `AllowAddRemoveApp <Boolean>`: Gets or sets a value indicating whether members can add or remove apps in the team. +- `AllowCreatePrivateChannel <Boolean>`: Gets or Sets a value indicating whether members can create Private channels. +- `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether members can create or edit channels in the team. +- `AllowCreateUpdateRemoveConnector <Boolean>`: Gets or sets a value indicating whether members can add, edit, or remove connectors in the team. +- `AllowCreateUpdateRemoveTab <Boolean>`: Gets or sets a value indicating whether members can add, edit or remove pinned tabs in the team. +- `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether members can delete team channels. +- `UploadCustomApp <Boolean>`: Gets or sets a value indicating is allowed to upload custom apps. + +MESSAGINGSETTING \<ITeamMessagingSettings\>: Governs use of messaging features within the teamThese are settings the team owner should be able to modify from UI after team creation. + +- `AllowChannelMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention entire channels in team conversations. +- `AllowOwnerDeleteMessage <Boolean>`: Gets or sets a value indicating whether team owners can delete anyone's messages in team conversations. +- `AllowTeamMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention the entire team in team conversations. +- `AllowUserDeleteMessage <Boolean>`: Gets or sets a value indicating whether team members can delete their own messages in team conversations. +- `AllowUserEditMessage <Boolean>`: Gets or sets a value indicating whether team members can edit their own messages in team conversations. + +## RELATED LINKS + +- [Get-CsTeamTemplateList](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [Get-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [New-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [Update-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [Remove-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) diff --git a/teams/teams-ps/teams/New-CsTeamsAIPolicy.md b/teams/teams-ps/teams/New-CsTeamsAIPolicy.md new file mode 100644 index 0000000000..4a7ff4af67 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsAIPolicy.md @@ -0,0 +1,136 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: New-CsTeamsAIPolicy +online version: https://learn.microsoft.com/powershell/module/teams/New-CsTeamsAIPolicy +schema: 2.0.0 +author: Andy447 +ms.author: andywang +--- + +# New-CsTeamsAIPolicy + +## SYNOPSIS +This cmdlet creates a Teams AI policy. + +## SYNTAX + +```powershell +New-CsTeamsAIPolicy -Identity <String> + [-EnrollFace <string>] + [-EnrollVoice <string>] + [-SpeakerAttributionBYOD <string>] + [-Description <string>] + [<CommonParameters>] +``` + +## DESCRIPTION + +The new csTeamsAIPolicy will replace the existing enrollment settings in csTeamsMeetingPolicy, providing enhanced flexibility and control for Teams meeting administrators. Unlike the current single setting, EnrollUserOverride, which applies to both face and voice enrollment, the new policy introduces two distinct settings: EnrollFace and EnrollVoice. These can be individually set to Enabled or Disabled, offering more granular control over biometric enrollments. A new setting, SpeakerAttributionBYOD, is also being added to csTeamsAIPolicy. This allows IT admins to turn off speaker attribution in BYOD scenarios, giving them greater control over how voice data is managed in such environments. This setting can be set to Enabled or Disabled, and will be Enabled by default. In addition to improving the management of face and voice data, the csTeamsAIPolicy is designed to support future AI-related settings in Teams, making it a scalable solution for evolving needs. + +This cmdlet creates a Teams AI policy. If you get an error that the policy already exists, it means that the policy already exists for your tenant. In this case, run Get-CsTeamsAIPolicy. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsAIPolicy -Identity Test +``` +Creates a new Teams AI policy with the specified identity. +The newly created policy with value will be printed on success. + +## PARAMETERS + +### -Identity +Identity of the Teams AI policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnrollFace +Policy value of the Teams AI EnrollFace policy. EnrollFace controls user access to user face enrollment in the Teams app settings. + +```yaml +Type: String +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnrollVoice +Policy value of the Teams AI EnrollVoice policy. EnrollVoice controls user access to user voice enrollment in the Teams app settings. + +```yaml +Type: String +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpeakerAttributionBYOD +Policy value of the Teams AI SpeakerAttributionBYOD policy. Setting to "Enabled" turns on speaker attribution in BYOD scenarios while "Disabled" will turn off the function. + +```yaml +Type: String +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the Teams AI policy. +For example, the Description might indicate the users the policy should be assigned to. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Remove-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsaipolicy) + +[Get-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaipolicy) + +[Set-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy) + +[Grant-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaipolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsAppPermissionPolicy.md b/teams/teams-ps/teams/New-CsTeamsAppPermissionPolicy.md new file mode 100644 index 0000000000..ff4308f76f --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsAppPermissionPolicy.md @@ -0,0 +1,67 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsapppermissionpolicy +applicable: Microsoft Teams +title: New-CsTeamsAppPermissionPolicy +schema: 2.0.0 +ms.reviewer: mhayrapetyan +manager: prkosh +ms.author: prkosh +author: ashishguptaiitb +--- + +# New-CsTeamsAppPermissionPolicy + +## SYNOPSIS + +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. This cmdlet is not supported for tenants that migrated to app centric management feature as it replaced permission policies. While the cmdlet may succeed, the changes aren't applied to the tenant. + +As an admin, you can use app permission policies to allow or block apps for your users. Learn more about the app permission policies at <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies> and about app centric management at <https://learn.microsoft.com/microsoftteams/app-centric-management>. + +**This is only applicable for tenants who have not been migrated to ACM or UAM.** + +## SYNTAX + +``` +New-CsTeamsAppPermissionPolicy [[-Identity] <String>] + [-Confirm] + [-DefaultCatalogApps <DefaultCatalogApp[]>] + [-DefaultCatalogAppsType <String>] + [-Description <String>] + [-Force] + [-GlobalCatalogApps <GlobalCatalogApp[]>] + [-GlobalCatalogAppsType <String>] + [-InMemory] + [-PrivateCatalogApps <PrivateCatalogApp[]>] + [-PrivateCatalogAppsType <String>] + [-Tenant <Object>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies>. + +## EXAMPLES + +### Example 1 +Intentionally omitted. + +## 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsAppSetupPolicy.md b/teams/teams-ps/teams/New-CsTeamsAppSetupPolicy.md new file mode 100644 index 0000000000..ff00d0c8a6 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsAppSetupPolicy.md @@ -0,0 +1,314 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsappsetuppolicy +applicable: Microsoft Teams +title: New-CsTeamsAppSetupPolicy +schema: 2.0.0 +--- + +# New-CsTeamsAppSetupPolicy + +## SYNOPSIS +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## SYNTAX + +``` +New-CsTeamsAppSetupPolicy [-Identity] <String> + [-AllowSideLoading <Boolean>] + [-AllowUserPinning <Boolean>] + [-AppPresetList <Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset[]>] + [-Confirm] + [-Description <String>] + [-Force] + [-PinnedAppBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp[]>] + [-PinnedCallingBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedCallingBarApp[]>] + [-PinnedMessageBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp[]>] + [-AppPresetMeetingList <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPresetMeeting]>] + [-AdditionalCustomizationApps <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AdditionalCustomizationApp]>] + [-Tenant <System.Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## EXAMPLES + +### Example 1 + +```powershell +New-CsTeamsAppSetupPolicy -Identity (Get-Date -Format FileDateTimeUniversal) +``` +Create a new TeamsAppSetupPolicy, if no parameters are specified, the Global Policy configuration is used by default. + +### Example 2 + +```powershell +New-CsTeamsAppSetupPolicy -Identity (Get-Date -Format FileDateTimeUniversal) -AllowSideLoading $true -AllowUserPinning $true +``` +Create a new TeamsAppSetupPolicy. Users can upload a custom app package in the Teams app because AllowSideLoading is set as True, and existing app pins can be added to the list of pinned apps because AllowUserPinning is set as True. + +### Example 3 + +```powershell +# Set ActivityApp, ChatApp, TeamsApp as PinnedAppBarApps +$ActivityApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp -Property @{Id="14d6962d-6eeb-4f48-8890-de55454bb136"} +$ChatApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp -Property @{Id="86fcd49b-61a2-4701-b771-54728cd291fb"} +$TeamsApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp -Property @{Id="2a84919f-59d8-4441-a975-2a8c2643b741"} +$PinnedAppBarApps = @($ActivityApp,$ChatApp,$TeamsApp) + +# Settings to pin these apps to the app bar in Teams client. +New-CsTeamsAppSetupPolicy -Identity (Get-Date -Format FileDateTimeUniversal) -AllowUserPinning $true -PinnedAppBarApps $PinnedAppBarApps +``` + +Create a new TeamsAppSetupPolicy and pin ActivityApp, ChatApp, TeamsApp apps to the app bar in Teams client by setting these apps as PinnedAppBarApps. + +### Example 4 + +```powershell +# Set VivaConnectionsApp as PinnedMessageBarApps +$VivaConnectionsApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp -Property @{Id="d2c6f111-ffad-42a0-b65e-ee00425598aa"} +$PinnedMessageBarApps = @($VivaConnectionsApp) +# Settings to pin these apps to the messaging extension in Teams client. +Set-CsTeamsAppSetupPolicy -Identity (Get-Date -Format FileDateTimeUniversal) -AllowUserPinning $true -PinnedMessageBarApps $PinnedMessageBarApps +``` + +Create a new TeamsAppSetupPolicy and pin VivaConnections app to the messaging extension in Teams client by setting these apps as PinnedMessageBarApps. + +### Example 5 + +```powershell +# Set VivaConnectionsApp as AppPresetList +$VivaConnectionsApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset -Property @{Id="d2c6f111-ffad-42a0-b65e-ee00425598aa"} +$AppPresetList = @($VivaConnectionsApp) +# Settings to install these apps in your users' personal Teams environment +Set-CsTeamsAppSetupPolicy -Identity (Get-Date -Format FileDateTimeUniversal) -AllowSideLoading $true -AppPresetList $AppPresetList +``` + +Create a new TeamsAppSetupPolicy and install VivaConnections App in users' personal Teams environment by setting these apps as AppPresetList. + +## PARAMETERS + +### -Identity +Name of App setup policy. If empty, all Identities will be used by default. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSideLoading +This is also known as side loading. This setting determines if a user can upload a custom app package in the Teams app. Turning it on lets you create or develop a custom app to be used personally or across your organization without having to submit it to the Teams app store. Uploading a custom app also lets you test an app before you distribute it more widely by only assigning it to a single user or group of users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserPinning +If you turn this on, the user's existing app pins will be added to the list of pinned apps set in this policy. Users can rearrange, add, and remove pins as they choose. If you turn this off, the user's existing app pins will be removed and replaced with the apps defined in this policy. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppPresetList +Choose which apps and messaging extensions you want to be installed in your users' personal Teams environment and in meetings they create. Users can install other available apps from the Teams app store. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Description of the app setup policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinnedAppBarApps +Pinning an app displays the app in the app bar in Teams client. Admins can pin apps and they can allow users to pin apps. Pinning is used to highlight apps that are needed the most by users and promote ease of access. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinnedCallingBarApps +Determines the list of apps that are pre pinned for a participant in Calls. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedCallingBarApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinnedMessageBarApps +Apps are pinned in messaging extensions and into the ellipsis menu. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdditionalCustomizationApps +This parameter allows IT admins to create multiple customized versions of their apps and assign these customized versions to users and groups via setup policies. It enables customization of app icons and names for supportive first-party (1P) and third-party (3P) apps, enhancing corporate connections to employees through brand expression and stimulating app awareness and usage. + +```yaml +Type: System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AdditionalCustomizationApp] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppPresetMeetingList +This parameter is used to manage the list of preset apps that are available during meetings. It allows admins to control which apps are pinned and set the order in which they appear, ensuring that users have quick access to the relevant apps during meetings. + +```yaml +Type: System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPresetMeeting] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Do not use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset + +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp + +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsAudioConferencingPolicy.md b/teams/teams-ps/teams/New-CsTeamsAudioConferencingPolicy.md new file mode 100644 index 0000000000..e95b230bdc --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsAudioConferencingPolicy.md @@ -0,0 +1,163 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsaudioconferencingpolicy +title: New-CsTeamsAudioConferencingPolicy +schema: 2.0.0 +--- + +# New-CsTeamsAudioConferencingPolicy + +## SYNOPSIS + +## SYNTAX + +``` +New-CsTeamsAudioConferencingPolicy [-Identity] <String> [-AllowTollFreeDialin <Boolean>] [-Force] [-InMemory] + [-MeetingInvitePhoneNumbers <Object>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The New-CsTeamsAudioConferencingPolicy cmdlet enables administrators to control audio conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. This cmdlet creates a new Teams audio conferencing policy. Custom policies can then be assigned to users using the Grant-CsTeamsAudioConferencingPolicy cmdlet. + +## EXAMPLES + +### EXAMPLE 1 +``` +PS C:\> New-CsTeamsAudioConferencingPolicy -Identity "EMEA Users" -AllowTollFreeDialin $False +``` + +The command shown in Example 1 uses the New-CsTeamsAudioConferencingPolicy cmdlet to create a new audio-conferencing policy with the Identity "EMEA users". This policy will use all the default values for a meeting policy except one: AllowTollFreeDialin; in this example, meetings created by users with this policy cannot include Toll Free phone numbers. + +### EXAMPLE 2 +``` +PS C:\> New-CsTeamsAudioConferencingPolicy -Identity "EMEA Users" -AllowTollFreeDialin $True -MeetingInvitePhoneNumbers "+49695095XXXXX","+353156YYYYY","+1800856ZZZZZ" +``` + +The command shown in Example 2 uses the New-CsTeamsAudioConferencingPolicy cmdlet to create a new audio-conferencing policy with the Identity "EMEA users". This policy will use all the default values for a meeting policy except one: MeetingInvitePhoneNumbers; in this example, meetings created by users with this policy will include the following toll and toll free phone numbers "+49695095XXXXX","+353156YYYYY","+1800856ZZZZZ". + +## PARAMETERS + +### -AllowTollFreeDialin +Determines whether users of the Policy can have Toll free numbers + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy that you are creating + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set- cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingInvitePhoneNumbers +Determines the list of audio-conferencing Toll- and Toll-free telephone numbers that will be included in meetings invites created by users of this policy. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Object +## NOTES + +## RELATED LINKS + +[Get-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaudioconferencingpolicy) + +[Set-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaudioconferencingpolicy) + +[Grant-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaudioconferencingpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsCallHoldPolicy.md b/teams/teams-ps/teams/New-CsTeamsCallHoldPolicy.md new file mode 100644 index 0000000000..92744364e9 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsCallHoldPolicy.md @@ -0,0 +1,191 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamscallholdpolicy +applicable: Microsoft Teams +title: New-CsTeamsCallHoldPolicy +schema: 2.0.0 +ms.reviewer: +manager: abnair +ms.author: serdars +author: serdarsoysal +--- + +# New-CsTeamsCallHoldPolicy + +## SYNOPSIS + +Creates a new Teams call hold policy in your tenant. The Teams call hold policy is used to customize the call hold experience for Teams clients. + +## SYNTAX + +``` +New-CsTeamsCallHoldPolicy [-Identity] <string> [-Description <string>] [-AudioFileId <string>] [-StreamingSourceUrl <string>] [-StreamingSourceAuthType <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Teams call hold policies are used to customize the call hold experience for teams clients. +When Microsoft Teams users participate in calls, they have the ability to hold a call and have the other entity in the call listen to an audio file during the duration of the hold. + +Assigning a Teams call hold policy to a user sets an audio file to be played during the duration of the hold. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsCallHoldPolicy -Identity "ContosoPartnerTeamsCallHoldPolicy" -Description "country music" -AudioFileID "c65233-ac2a27-98701b-123ccc" +``` + +The command shown in Example 1 creates a new, per-user Teams call hold policy with the Identity ContosoPartnerTeamsCallHoldPolicy. +This policy is assigned the audio file ID: c65233-ac2a27-98701b-123ccc, which is the ID referencing an audio file that was uploaded using the Import-CsOnlineAudioFile cmdlet. + +Any Microsoft Teams users who are assigned this policy will have their call holds customized such that the user being held will hear the audio file specified by AudioFileId. + +## PARAMETERS + +### -Identity +Unique identifier to be assigned to the new Teams call hold policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams call hold policy. + +For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AudioFileId +A string representing the ID referencing an audio file uploaded via the Import-CsOnlineAudioFile cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreamingSourceUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreamingSourceAuthType +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallholdpolicy) + +[Set-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallholdpolicy) + +[Grant-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallholdpolicy) + +[Remove-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallholdpolicy) + +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) diff --git a/teams/teams-ps/teams/New-CsTeamsCallParkPolicy.md b/teams/teams-ps/teams/New-CsTeamsCallParkPolicy.md new file mode 100644 index 0000000000..ba4ca721a7 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsCallParkPolicy.md @@ -0,0 +1,225 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamscallparkpolicy +applicable: Microsoft Teams +title: New-CsTeamsCallParkPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# New-CsTeamsCallParkPolicy + +## SYNOPSIS + +The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone. The New-CsTeamsCallParkPolicy cmdlet lets you create a new custom policy that can then be assigned to one or more specific users. + +NOTE: The call park feature currently available in desktop. mobile and web clients. Supported with TeamsOnly mode. + +## SYNTAX + +### Identity (Default) +```powershell +New-CsTeamsCallParkPolicy [-Tenant <System.Guid>] [-AllowCallPark <Boolean>] [[-Identity] <XdsIdentity>] [-PickupRangeStart <Integer>] [-PickupRangeEnd <Integer>] [-ParkTimeoutSeconds <Integer>] [-Force] [-WhatIf] [-Confirm] [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different phone. The New-CsTeamsCallParkPolicy cmdlet lets you create a new custom policy that can then be assigned to one or more specific users. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsCallParkPolicy -Identity "SalesPolicy" -AllowCallPark $true +``` + +Create a new custom policy that has call park enabled. This policy can then be assigned to individual users. + +### Example 2 +```powershell +PS C:\> New-CsTeamsCallParkPolicy -Identity "SalesPolicy" -AllowCallPark $true -PickupRangeStart 500 -PickupRangeEnd 1500 +``` + +Create a new custom policy that has call park enabled. This policy will generate pickup numbers starting from 500 and up until 1500. + +### Example 3 +```powershell +PS C:\> New-CsTeamsCallParkPolicy -Identity "SalesPolicy" -AllowCallPark $true -ParkTimeoutSeconds 600 +``` + +Create a new custom call park policy which will ring back the parker after 600 seconds if the parked call is unanswered + +## PARAMETERS + +### -AllowCallPark +If set to true, customers will be able to leverage the call park feature to place calls on hold and then decide how the call should be handled - transferred to another department, retrieved using the same phone, or retrieved using a different phone. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppress all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A unique identifier for the policy - this will be used to retrieve the policy later on to assign it to specific users. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PickupRangeEnd +Specify the maximum value that a rendered pickup code can take. Value can be from 10 to 9999. + +Note: PickupRangeStart must be smaller than PickupRangeEnd. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 99 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParkTimeoutSeconds +Specify the number of seconds to wait before ringing the parker when the parked call hasn't been picked up. Value can be from 120 to 1800 (seconds). + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 300 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PickupRangeStart +Specify the minimum value that a rendered pickup code can take. Value can be from 10 to 9999. + +Note: PickupRangeStart must be smaller than PickupRangeEnd. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 10 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsCallingPolicy.md b/teams/teams-ps/teams/New-CsTeamsCallingPolicy.md new file mode 100644 index 0000000000..638a131b09 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsCallingPolicy.md @@ -0,0 +1,732 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamscallingpolicy +applicable: Microsoft Teams +title: New-CsTeamsCallingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: alejandramu +--- + +# New-CsTeamsCallingPolicy + +## SYNOPSIS +Use this cmdlet to create a new instance of a Teams Calling Policy. + +## SYNTAX + +### Identity (Default) +``` +New-CsTeamsCallingPolicy [-Identity] <string> + [-AIInterpreter <string>] + [-AllowCallForwardingToPhone <boolean>] + [-AllowCallForwardingToUser <boolean>] + [-AllowCallGroups <boolean>] + [-AllowCallRedirect <string>] + [-AllowCloudRecordingForCalls <boolean>] + [-AllowDelegation <boolean>] + [-AllowPrivateCalling <boolean>] + [-AllowSIPDevicesCalling <boolean>] + [-AllowTranscriptionForCalling <boolean>] + [-AllowVoicemail <string>] + [-AllowWebPSTNCalling <boolean>] + [-AutoAnswerEnabledType <string>] + [-BusyOnBusyEnabledType <string>] + [-CallingSpendUserLimit <long>] + [-CallRecordingExpirationDays <long>] + [-Confirm] + [-Copilot <string>] + [-Description <string>] + [-EnableSpendLimits <boolean>] + [-EnableWebPstnMediaBypass <Boolean>] + [-Force] + [-InboundFederatedCallRoutingTreatment <string>] + [-InboundPstnCallRoutingTreatment <string>] + [-LiveCaptionsEnabledTypeForCalling <string>] + [-MusicOnHoldEnabledType <string>] + [-PopoutAppPathForIncomingPstnCalls <string>] + [-PopoutForIncomingPstnCalls <string>] + [-PreventTollBypass <boolean>] + [-SpamFilteringEnabledType <string>] + [-VoiceSimulationInInterpreter <string>] + [-RealTimeText <string>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The Teams Calling Policy controls which calling and call forwarding features are available to users in Microsoft Teams. This cmdlet allows admins to create new policy instances. + +## EXAMPLES + +### Example 1 +``` +PS C:\> New-CsTeamsCallingPolicy -Identity Sales -AllowPrivateCalling $false +``` + +The cmdlet create the policy instance Sales and sets the value of the parameter AllowPrivateCalling to False. The rest of the parameters are set to the corresponding +values in the Global policy instance. + +## PARAMETERS + +### -Identity +Name of the policy instance being created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AIInterpreter +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the AI Interpreter related features + +Possible values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallForwardingToPhone +Enables the user to configure in the Microsoft Teams client call forwarding or simultaneous ringing of inbound calls to any phone number. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallForwardingToUser +Enables the user to configure in the Microsoft Teams client call forwarding or simultaneous ringing of inbound calls to other users in your tenant. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallGroups +Enables the user to configure call groups in the Microsoft Teams client and that inbound calls should be routed to call groups. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallRedirect +Setting this parameter enables local call redirection for SIP devices connecting via the Microsoft Teams SIP gateway. + +Valid options are: +- Enabled: Enables the user to redirect an incoming call. +- Disabled: The user is not enabled to redirect an incoming call. + +- UserOverride: This option is not available for use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCloudRecordingForCalls +Determines whether cloud recording is allowed in a user's 1:1 Teams or PSTN calls. Set this to True to allow the user to be able to record 1:1 calls. Set this to False to prohibit the user from recording 1:1 calls. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowDelegation +Enables the user to configure delegation in the Microsoft Teams client and that inbound calls to be routed to delegates; allows delegates to make outbound calls on behalf of the users for whom they have delegated permissions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateCalling +Controls all calling capabilities in Teams. Turning this off will turn off all calling functionality in Teams. +If you use Skype for Business for calling, this policy will not affect calling functionality in Skype for Business. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSIPDevicesCalling +Determines whether the user is allowed to use a SIP device for calling on behalf of a Teams client. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTranscriptionForCalling +Determines whether post-call transcriptions are allowed. Set this to True to allow. Set this to False to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowVoicemail +Enables inbound calls to be routed to voicemail. + +Valid options are: + +- AlwaysEnabled: Calls are always forwarded to voicemail on unanswered after ringing for thirty seconds, regardless of the unanswered call forward setting for the user. +- AlwaysDisabled: Calls are never routed to voicemail, regardless of the call forward or unanswered settings for the user. Voicemail isn't available as a call forwarding or unanswered setting in Teams. +- UserOverride: Calls are forwarded to voicemail based on the call forwarding and/or unanswered settings for the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWebPSTNCalling +Allows PSTN calling from the Team web client. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoAnswerEnabledType +Setting this parameter allows you to enable or disable auto-answer for incoming meeting invites on Teams Phones. This setting applies only to incoming meeting invites and does not include support for other call types. + +Valid options are: + +- Enabled: Auto-answer is enabled. +- Disabled: Auto-answer is disabled. This is the default setting. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BusyOnBusyEnabledType +Setting this parameter lets you configure how incoming calls are handled when a user is already in a call or conference or has a call placed on hold. + +Valid options are: + +- Enabled: New or incoming calls will be rejected with a busy signal. +- Unanswered: The user's unanswered settings will take effect, such as routing to voicemail or forwarding to another user. +- Disabled: New or incoming calls will be presented to the user. +- UserOverride: Users can set their busy options directly from call settings in Teams app. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallingSpendUserLimit +The maximum amount a user can spend on outgoing PSTN calls, including all calls made through Pay-as-you-go Calling Plans and any overages on plans with bundled minutes. + +Possible values: any positive integer + +```yaml +Type: Long +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallRecordingExpirationDays +Sets the expiration of the recorded 1:1 calls. Default is 60 days. + +```yaml +Type: Long +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Copilot +Setting this parameter lets you control how Copilot is used during calls and if transcription is needed to be turned on and saved after the call. + +Valid options are: +- Enabled: Copilot can work with or without transcription during calls. This is the default value. +- EnabledWithTranscript: Copilot will only work when transcription is enabled during calls. +- Disabled: Copilot is disabled for calls. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the calling policy. For example, the Description might indicate the users to whom the policy should be assigned. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSpendLimits +This setting allows an admin to enable or disable spend limits on PSTN calls for their user base. + +Possible values: + +- True +- False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableWebPstnMediaBypass +Determines if MediaBypass is enabled for PSTN calls on specified Web platforms. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundFederatedCallRoutingTreatment +Setting this parameter lets you control how inbound federated calls should be routed. + +Valid options are: + +- RegularIncoming: No changes are made to default inbound routing. This is the default setting. +- Unanswered: The inbound federated call will be routed according to the called user's unanswered call settings and the call will not be presented to the called user. The called user will see a missed call notification. If the called user has not enabled unanswered call settings the call will be disconnected. + +- Voicemail: The inbound federated call will be routed directly to the called user's voicemail and the call will not be presented to the user. If the called user does not have voicemail enabled the call will be disconnected. + +Setting this parameter to Unanswered or Voicemail will have precedence over other call forwarding settings like call forward/simultaneous ringing to delegate, call groups, or call forwarding. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: RegularIncoming +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundPstnCallRoutingTreatment +Setting this parameter lets you control how inbound PSTN calls should be routed. + +Valid options are: + +- RegularIncoming: No changes are made to default inbound routing. This is the default setting. +- Unanswered: The inbound PSTN call will be routed according to the called user's unanswered call settings and the call will not be presented to the called user. The called user will see a missed call notification. If the called user has not enabled unanswered call settings the call will be disconnected. +- Voicemail: The inbound PSTN call will be routed directly to the called user's voicemail and the call will not be presented to the user. If the called user does not have voicemail enabled the call will be disconnected. +- UserOverride: For now, setting the value to UserOverride is the same as RegularIncoming. + +Setting this parameter to Unanswered or Voicemail will have precedence over other call forwarding settings like call forward/simultaneous ringing to delegate, call groups, or call forwarding. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: RegularIncoming +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveCaptionsEnabledTypeForCalling +Determines whether real-time captions are available for the user in Teams calls. + +Valid options are: + +- DisabledUserOverride: Allows the user to turn on live captions. +- Disabled: Prohibits the user from turning on live captions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MusicOnHoldEnabledType +Setting this parameter allows you to turn on or turn off the music on hold when a caller is placed on hold. + +Valid options are: + +- Enabled: Music on hold is enabled. This is the default. +- Disabled: Music on hold is disabled. +- UserOverride: For now, setting the value to UserOverride is the same as Enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopoutAppPathForIncomingPstnCalls +Setting this parameter allows you to set the PopoutForIncomingPstnCalls setting's URL path of the website to launch upon receiving incoming PSTN calls. This parameter accepts an HTTPS URL with less than 1024 characters. The URL can contain a `{phone}` placeholder that is replaced with the caller's PSTN number in E.164 format when launched. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: "" +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopoutForIncomingPstnCalls +Setting this parameter allows you to control the tenant users' ability to launch an external website URL automatically in the browser window upon incoming PSTN calls for specific users or user groups. Valid options are Enabled and Disabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreventTollBypass +Setting this parameter to True will send calls through PSTN and incur charges rather than going through the network and bypassing the tolls. + +> [!NOTE] +> Do not set this parameter to True for Calling Plan or Operator Connect users as it will prevent successful call routing. This setting only works with Direct Routing which is configured to handle location-based routing restrictions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamFilteringEnabledType +Determines Spam filtering mode. + +Possible values: + +- Enabled: Spam Filtering is fully enabled. Both Basic and Captcha Interactive Voice Response (IVR) checks are performed. In case the call is considered spam, the user will get a "Spam Likely" notification in Teams. +- Disabled: Spam Filtering is completely disabled. No checks are performed. A "Spam Likely" notification will not appear. +- EnabledWithoutIVR: Spam Filtering is partially enabled. Captcha IVR checks are disabled. A "Spam Likely" notification will appear. A call might get dropped if it gets a high score from Basic checks. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceSimulationInInterpreter + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the voice simulation feature while being AI interpreted. + +Possible Values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeText +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Allows users to use real time text during a call, allowing them to communicate by typing their messages in real time. + +Possible Values: +- Enabled: User is allowed to turn on real time text. +- Disabled: User is not allowed to turn on real time text. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallingpolicy) + +[Remove-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallingpolicy) + +[Grant-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallingpolicy) + +[Set-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallingpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsChannelsPolicy.md b/teams/teams-ps/teams/New-CsTeamsChannelsPolicy.md new file mode 100644 index 0000000000..fd19f2ca12 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsChannelsPolicy.md @@ -0,0 +1,258 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamschannelspolicy +applicable: Microsoft Teams +title: New-CsTeamsChannelsPolicy +schema: 2.0.0 +--- + +# New-CsTeamsChannelsPolicy + +## SYNOPSIS + +The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. + +## SYNTAX +``` +New-CsTeamsChannelsPolicy [-Tenant <Guid>] [-AllowOrgWideTeamCreation <Boolean>] + [-EnablePrivateTeamDiscovery <Boolean>] [-AllowPrivateChannelCreation <Boolean>] + [-AllowUserToParticipateInExternalSharedChannel <Boolean>] [-AllowChannelSharingToExternalUser <Boolean>] [-AllowSharedChannelCreation <Boolean>] [-ThreadedChannelCreation <String>] + [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] [-Confirm] [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. + +This cmdlet allows you to create new policies of this type, which can later be assigned to specific users. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsChannelsPolicy -Identity StudentPolicy -EnablePrivateTeamDiscovery $false +``` + +This example shows creating a new policy with name "StudentPolicy" where Private Team Discovery is disabled. + +## PARAMETERS + +### -EnablePrivateTeamDiscovery +Determines whether a user is allowed to discover private teams in suggestions and search results. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Bypasses all non-fatal errors. +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy that you are creating. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOrgWideTeamCreation +Determines whether a user is allowed to create an org-wide team. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateChannelCreation +Determines whether a user is allowed to create a private channel. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowChannelSharingToExternalUser +Owners of a shared channel can invite external users to join the channel if Microsoft Entra external sharing policies are configured. If the channel has been shared with an external member or team, they will continue to have access to the channel even if this parameter is set to FALSE. For more information, see [Manage channel policies in Microsoft Teams](https://learn.microsoft.com/microsoftteams/teams-policies). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSharedChannelCreation +Team owners can create shared channels for people within and outside the organization. Only people added to the shared channel can read and write messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserToParticipateInExternalSharedChannel +Users and teams can be invited to external shared channels if Microsoft Entra external sharing policies are configured. If a team in your organization is part of an external shared channel, new team members will have access to the channel even if this parameter is set to FALSE. For more information, see [Manage channel policies in Microsoft Teams](https://learn.microsoft.com/microsoftteams/teams-policies). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThreadedChannelCreation +This setting enables/disables Threaded Channel creation and editing. + +Possible Values: +- Enabled: Users are allowed to create and edit Threaded Channels. +- Disabled: Users are not allowed to create and edit Threaded Channels. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies the description of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamschannelspolicy) + +[Remove-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamschannelspolicy) + +[Grant-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamschannelspolicy) + +[Get-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamschannelspolicy) diff --git a/skype/skype-ps/skype/New-CsTeamsComplianceRecordingApplication.md b/teams/teams-ps/teams/New-CsTeamsComplianceRecordingApplication.md similarity index 90% rename from skype/skype-ps/skype/New-CsTeamsComplianceRecordingApplication.md rename to teams/teams-ps/teams/New-CsTeamsComplianceRecordingApplication.md index 836ca7385d..a08b36dfb9 100644 --- a/skype/skype-ps/skype/New-CsTeamsComplianceRecordingApplication.md +++ b/teams/teams-ps/teams/New-CsTeamsComplianceRecordingApplication.md @@ -1,441 +1,443 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication -applicable: Skype for Business Online -title: New-CsTeamsComplianceRecordingApplication -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# New-CsTeamsComplianceRecordingApplication - -## SYNOPSIS -Creates a new association between an application instance of a policy-based recording application and a Teams recording policy for administering automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -### Identity (Default) -``` -New-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] - [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] - [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] - [-Priority <Int32>] [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### ParentAndRelativeKey -``` -New-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] -Parent <String> -Id <String> - [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] - [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] - [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] - [-Priority <Int32>] [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Policy-based recording applications are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. - -Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. - -Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. -Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> New-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -``` - -The command shown in Example 1 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -### Example 2 -```powershell -PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -``` - -The command shown in Example 2 is a variation of Example 1. -It also creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy, but it does this by using the Parent and Id parameters instead of the Identity parameter. - -### Example 3 -```powershell -PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeMeetingJoin $false -RequiredDuringMeeting $false -``` - -The command shown in Example 3 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is deemed optional for meetings but mandatory for calls. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredDuringMeeting parameters for more information. - -### Example 4 -```powershell -PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeCallEstablishment $false -RequiredDuringCall $false -``` - -The command shown in Example 4 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is deemed optional for calls but mandatory for meetings. -Please refer to the documentation of the RequiredBeforeCallEstablishment and RequiredDuringCall parameters for more information. - -### Example 5 -```powershell -PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -ConcurrentInvitationCount 2 -``` - -The command shown in Example 5 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is made resilient by specifying that two invites must be sent to the same application for the same call or meeting. -Please refer to the documentation of the ConcurrentInvitationCount parameter for more information. - -### Example 6 -```powershell -PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -ComplianceRecordingPairedApplications @(New-CsTeamsComplianceRecordingPairedApplication -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') -``` - -The command shown in Example 6 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is made resilient by pairing it with another application instance of a policy-based recording application with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. -Separate invites are sent to the paired applications for the same call or meeting. -Please refer to the documentation of the ComplianceRecordingPairedApplications parameter for more information. - -## PARAMETERS - -### -Identity -A name that uniquely identifies the application instance of the policy-based recording application. - -Application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -To do this association correctly, the Identity of these application instances must be \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Parent -The Identity of the Teams recording policy that this application instance of a policy-based recording application is associated with. -For example, the Parent of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy\", which indicates that the application instance is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Id -The ObjectId of the application instance of a policy-based recording application as exposed by the Get-CsOnlineApplicationInstance cmdlet. -For example, the Id of an application instance can be \"39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance has ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. - -```yaml -Type: String -Parameter Sets: ParentAndRelativeKey -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredBeforeMeetingJoin -Indicates whether the policy-based recording application must be in the meeting before the user is allowed to join the meeting. - -If this is set to True, the user will not be allowed to join the meeting if the policy-based recording application fails to join the meeting. -The meeting will still continue for users who are in the meeting. - -If this is set to False, the user will be allowed to join the meeting even if the policy-based recording application fails to join the meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredDuringMeeting -Indicates whether the policy-based recording application must be in the meeting while the user is in the meeting. - -If this is set to True, the user will be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. -The meeting will still continue for users who are in the meeting. - -If this is set to False, the user will not be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredBeforeCallEstablishment -Indicates whether the policy-based recording application must be in the call before the call is allowed to establish. - -If this is set to True, the call will be cancelled if the policy-based recording application fails to join the call. - -If this is set to False, call establishment will proceed normally if the policy-based recording application fails to join the call. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredDuringCall -Indicates whether the policy-based recording application must be in the call while the call is active. - -If this is set to True, the call will be cancelled if the policy-based recording application leaves the call or is dropped from the call. - -If this is set to False, call establishment will proceed normally if the policy-based recording application leaves the call or is dropped from the call. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConcurrentInvitationCount -Determines the number of invites to send out to the application instance of the policy-based recording application. - -In situations where application resiliency is a necessity, multiple invites can be sent to the same application for the same call or meeting. -If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. - -If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. - -If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. - -If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. - -If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. - -Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. -However, you cannot do both. -Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: 1 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ComplianceRecordingPairedApplications -Determines the other policy-based recording applications to pair with this application to achieve application resiliency. - -In situations where application resiliency is a necessity, invites can be sent to separate paired applications for the same call or meeting. -If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. - -If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. - -If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. - -If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. - -If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. - -Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. -However, you cannot do both. -Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. - -```yaml -Type: ComplianceRecordingPairedApplication[] -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -This priority determines the order in which the policy-based recording applications are displayed in the output of the Get-CsTeamsComplianceRecordingPolicy cmdlet. - -All policy-based recording applications are invited in parallel to ensure low call setup and meeting join latencies. -So this parameter does not affect the order of invitations to the applications, or any other routing. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -InMemory -Creates an object reference without actually committing the object as a permanent change. -If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set- cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### None - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication +applicable: Microsoft Teams +title: New-CsTeamsComplianceRecordingApplication +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# New-CsTeamsComplianceRecordingApplication + +## SYNOPSIS +Creates a new association between an application instance of a policy-based recording application and a Teams recording policy for administering automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +### Identity (Default) +``` +New-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] + [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] + [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] + [-Priority <Int32>] [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] -Parent <String> -Id <String> + [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] + [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] + [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] + [-Priority <Int32>] [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Policy-based recording applications are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. + +Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. + +Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. +Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' +``` + +The command shown in Example 1 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +### Example 2 +```powershell +PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' +``` + +The command shown in Example 2 is a variation of Example 1. +It also creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy, but it does this by using the Parent and Id parameters instead of the Identity parameter. + +### Example 3 +```powershell +PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeMeetingJoin $false -RequiredDuringMeeting $false +``` + +The command shown in Example 3 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is deemed optional for meetings but mandatory for calls. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredDuringMeeting parameters for more information. + +### Example 4 +```powershell +PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeCallEstablishment $false -RequiredDuringCall $false +``` + +The command shown in Example 4 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is deemed optional for calls but mandatory for meetings. +Please refer to the documentation of the RequiredBeforeCallEstablishment and RequiredDuringCall parameters for more information. + +### Example 5 +```powershell +PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -ConcurrentInvitationCount 2 +``` + +The command shown in Example 5 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is made resilient by specifying that two invites must be sent to the same application for the same call or meeting. +Please refer to the documentation of the ConcurrentInvitationCount parameter for more information. + +### Example 6 +```powershell +PS C:\> New-CsTeamsComplianceRecordingApplication -Parent 'Tag:ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899' -ComplianceRecordingPairedApplications @(New-CsTeamsComplianceRecordingPairedApplication -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') +``` + +The command shown in Example 6 creates a new association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is made resilient by pairing it with another application instance of a policy-based recording application with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. +Separate invites are sent to the paired applications for the same call or meeting. +Please refer to the documentation of the ComplianceRecordingPairedApplications parameter for more information. + +## PARAMETERS + +### -Identity +A name that uniquely identifies the application instance of the policy-based recording application. + +Application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +To do this association correctly, the Identity of these application instances must be \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Parent +The Identity of the Teams recording policy that this application instance of a policy-based recording application is associated with. +For example, the Parent of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy\", which indicates that the application instance is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Id +The ObjectId of the application instance of a policy-based recording application as exposed by the Get-CsOnlineApplicationInstance cmdlet. +For example, the Id of an application instance can be \"39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance has ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredBeforeMeetingJoin +Indicates whether the policy-based recording application must be in the meeting before the user is allowed to join the meeting. + +If this is set to True, the user will not be allowed to join the meeting if the policy-based recording application fails to join the meeting. +The meeting will still continue for users who are in the meeting. + +If this is set to False, the user will be allowed to join the meeting even if the policy-based recording application fails to join the meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredDuringMeeting +Indicates whether the policy-based recording application must be in the meeting while the user is in the meeting. + +If this is set to True, the user will be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. +The meeting will still continue for users who are in the meeting. + +If this is set to False, the user will not be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredBeforeCallEstablishment +Indicates whether the policy-based recording application must be in the call before the call is allowed to establish. + +If this is set to True, the call will be cancelled if the policy-based recording application fails to join the call. + +If this is set to False, call establishment will proceed normally if the policy-based recording application fails to join the call. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredDuringCall +Indicates whether the policy-based recording application must be in the call while the call is active. + +If this is set to True, the call will be cancelled if the policy-based recording application leaves the call or is dropped from the call. + +If this is set to False, call establishment will proceed normally if the policy-based recording application leaves the call or is dropped from the call. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConcurrentInvitationCount +Determines the number of invites to send out to the application instance of the policy-based recording application. Can be set to 1 or 2 only. + +In situations where application resiliency is a necessity, multiple invites can be sent to the same application for the same call or meeting. +If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. + +If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. + +If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. + +If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. + +If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. + +Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. +However, you cannot do both. +Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 1 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceRecordingPairedApplications +Determines the other policy-based recording applications to pair with this application to achieve application resiliency. Can only have one paired application. + +In situations where application resiliency is a necessity, invites can be sent to separate paired applications for the same call or meeting. +If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. + +If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. + +If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. + +If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. + +If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. + +Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. +However, you cannot do both. +Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. + +```yaml +Type: ComplianceRecordingPairedApplication[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +This priority determines the order in which the policy-based recording applications are displayed in the output of the Get-CsTeamsComplianceRecordingPolicy cmdlet. + +All policy-based recording applications are invited in parallel to ensure low call setup and meeting join latencies. +So this parameter does not affect the order of invitations to the applications, or any other routing. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. +If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set- cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/teams/teams-ps/teams/New-CsTeamsComplianceRecordingPairedApplication.md b/teams/teams-ps/teams/New-CsTeamsComplianceRecordingPairedApplication.md new file mode 100644 index 0000000000..d444f6ae79 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsComplianceRecordingPairedApplication.md @@ -0,0 +1,109 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication +applicable: Microsoft Teams +title: New-CsTeamsComplianceRecordingPairedApplication +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# New-CsTeamsComplianceRecordingPairedApplication + +## SYNOPSIS +Creates a new association between multiple application instances of policy-based recording applications to achieve application resiliency in automatic policy-based recording scenarios. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +``` +New-CsTeamsComplianceRecordingPairedApplication -Id <String> + [<CommonParameters>] +``` + +## DESCRIPTION +Policy-based recording applications are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. + +Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. + +In situations where application resiliency is a necessity, invites can be sent to separate paired applications for the same call or meeting. +If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. + +If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. + +If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. + +If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. + +If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application, to determine if application resiliency is needed for your workflows, and how best to achieve application resiliency. +Please also refer to the documentation of CsTeamsComplianceRecordingApplication cmdlets for further information. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsComplianceRecordingPairedApplication -Id '39dc3ede-c80e-4f19-9153-417a65a1f144' +``` + +The command shown in Example 1 creates an in-memory instance of an application instance of a policy-based recording application that can be associated with other such application instances to achieve application resiliency. + +Note that this cmdlet is only used in conjunction with New-CsTeamsComplianceRecordingApplication and Set-CsTeamsComplianceRecordingApplication to create associations between multiple application instances of policy-based recording applications. +Please refer to the documentation of CsTeamsComplianceRecordingApplication cmdlets for examples and further information. + +## PARAMETERS + +### -Id +The ObjectId of the application instance of a policy-based recording application as exposed by the Get-CsOnlineApplicationInstance cmdlet. +For example, the Id of an application instance can be \"39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance has ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) diff --git a/teams/teams-ps/teams/New-CsTeamsComplianceRecordingPolicy.md b/teams/teams-ps/teams/New-CsTeamsComplianceRecordingPolicy.md new file mode 100644 index 0000000000..e1caae78f9 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsComplianceRecordingPolicy.md @@ -0,0 +1,346 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy +applicable: Microsoft Teams +title: New-CsTeamsComplianceRecordingPolicy +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +--- + +# New-CsTeamsComplianceRecordingPolicy + +## SYNOPSIS +Creates a new Teams recording policy for governing automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +```powershell +New-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-Enabled <Boolean>] [-WarnUserOnRemoval <Boolean>] [-DisableComplianceRecordingAudioNotificationForCalls <Boolean>] + [-RecordReroutedCalls <Boolean>] [-Description <String>] + [-ComplianceRecordingApplications <ComplianceRecordingApplication[]>] [-CustomBanner <Guid>] + [-CustomPromptsEnabled <Boolean>] [-CustomPromptsPackageId <String>] + [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Teams recording policies are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. + +Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. +Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. + +Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. +The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. +Existing calls and meetings are unaffected. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $true -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899') +``` + +The command shown in Example 1 creates a new per-user Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. +This policy is assigned a single application instance of a policy-based recording application: d93fefc7-93cc-4d44-9a5d-344b0fff2899, which is the ObjectId of the application instance as obtained from the Get-CsOnlineApplicationInstance cmdlet. + +Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by that application instance. Existing calls and meetings are unaffected. + +### Example 2 +```powershell +PS C:\> New-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $true -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899'), @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') +``` + +Example 2 is a variation of Example 1. +In this case, the Teams recording policy is assigned two application instances of policy-based recording applications. + +Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by both those application instances. Existing calls and meetings are unaffected. + +## PARAMETERS + +### -Identity +Unique identifier to be assigned to the new Teams recording policy. + +Use the "Global" Identity if you wish to assign this policy to the entire tenant. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +Controls whether this Teams recording policy is active or not. + +Setting this to True and having the right set of ComplianceRecordingApplications will initiate automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. + +Setting this to False will stop automatic policy-based recording for any new calls or meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomBanner +References the Custom Banner text in the storage. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WarnUserOnRemoval +This parameter is reserved for future use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams recording policy. For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceRecordingApplications +A list of application instances of policy-based recording applications to assign to this policy. +The Id of each of these application instances must be the ObjectId of the application instance as obtained by the Get-CsOnlineApplicationInstance cmdlet. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. + +```yaml +Type: ComplianceRecordingApplication[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableComplianceRecordingAudioNotificationForCalls +Setting this attribute to true disables recording audio notifications for 1:1 calls that are under compliance recording. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordReroutedCalls +Setting this attribute to true enables compliance recording for calls that have been re-routed from a compliance recording-enabled user. Supported call scenarios include forward, transfer, delegation, call groups, and simultaneous ring. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. +If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set- cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomPromptsEnabled +Indicates whether compliance recording custom prompts feature is enabled for this tenant / user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomPromptsPackageId +Reference to custom prompts package. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/teams/teams-ps/teams/New-CsTeamsCortanaPolicy.md b/teams/teams-ps/teams/New-CsTeamsCortanaPolicy.md new file mode 100644 index 0000000000..247ea3b3a6 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsCortanaPolicy.md @@ -0,0 +1,234 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscortanapolicy +applicable: Microsoft Teams +title: New-CsTeamsCortanaPolicy +schema: 2.0.0 +manager: amehta +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsTeamsCortanaPolicy + +## SYNOPSIS +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. + +## SYNTAX + +``` +New-CsTeamsCortanaPolicy [-Tenant <System.Guid>] [-Description <String>] [-CortanaVoiceInvocationMode <String>] + [-AllowCortanaVoiceInvocation <Boolean>] [-AllowCortanaAmbientListening <Boolean>] + [-AllowCortanaInContextSuggestions <Boolean>] [-Identity] <XdsIdentity> [-InMemory] [-Force] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. Specifically, these specify if a user can use Cortana voice assistant in Microsoft Teams and Cortana invocation behavior via CortanaVoiceInvocationMode parameter - +* Disabled - Cortana voice assistant is disabled +* PushToTalkUserOverride - Cortana voice assistant is enabled but without wake-word ("Hey Cortana") invocation +* WakeWordPushToTalkUserOverride - Cortana voice assistant is enabled with wake-word ("Hey Cortana") invocation on devices where wake-word is supported + +This cmdlet creates a new Teams Cortana policy. Custom policies can then be assigned to users using the Grant-CsTeamsCortanaPolicy cmdlet. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsCortanaPolicy -Identity MyCortanaPolicy -CortanaVoiceInvocationMode PushToTalkUserOverride +``` + +In this example, a new Teams Cortana Policy is created. Cortana voice invocation mode is set to 'push to talk' i.e. Cortana in Teams can be invoked by tapping on the Cortana mic button only. Wake word ("Hey Cortana") invocation is not allowed. + +## PARAMETERS + +### -AllowCortanaAmbientListening +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCortanaInContextSuggestions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCortanaVoiceInvocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CortanaVoiceInvocationMode +The value of this field indicates if Cortana is enabled and mode of invocation. +* Disabled - Cortana voice assistant is turned off and cannot be used. +* PushToTalkUserOverride - Cortana voice assistant is enabled but without wake-word ("Hey Cortana") invocation +* WakeWordPushToTalkUserOverride - Cortana voice assistant is enabled with wake-word ("Hey Cortana") invocation on devices where wake-word is supported + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of your policy to identify purpose of creating it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for Teams cortana policy you're creating. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsCustomBannerText b/teams/teams-ps/teams/New-CsTeamsCustomBannerText new file mode 100644 index 0000000000..af23fbf760 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsCustomBannerText @@ -0,0 +1,95 @@ +--- +Module Name: MicrosoftTeams +title: New-CsTeamsCustomBannerText +author: saleens7 +ms.author: wblocker +online version: https://learn.microsoft.com/powershell/module/teams/New-CsTeamsCustomBannerText +schema: 2.0.0 +--- + +# New-CsTeamsCustomBannerText + +## SYNOPSIS + +Enables administrators to configure a custom text on the banner displayed when compliance recording bots start recording the call. + +## SYNTAX + +### Identity (Default) +``` +New-CsTeamsCustomBannerText [[-Id] <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION + +Creates a single instance of a custom banner text. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> New-CsTeamsCustomBannerText -Identity CustomText +``` + +Creates an instance of TeamsCustomBannerText with the name CustomText. + +## PARAMETERS + +### -Id +The Identity of the CustomBannerText. You do not need to provide an ID as the backend will generate it for you. However, if you wish to provide your own ID, you can provide your own GUID. Note that you have to provide a unique ID for every CsTeamsCustomBannerText you create. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Text +The text that the tenant admin would like to set in the policy. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description that the tenant admin would like to set to identify what this text represents. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/set-csteamscustombannertext) + +[New-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext) + +[Remove-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/remove-csteamscustombannertext) diff --git a/teams/teams-ps/teams/New-CsTeamsCustomBannerText.md b/teams/teams-ps/teams/New-CsTeamsCustomBannerText.md new file mode 100644 index 0000000000..4ed97c99b6 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsCustomBannerText.md @@ -0,0 +1,95 @@ +--- +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext +title: New-CsTeamsCustomBannerText +schema: 2.0.0 +author: saleens7 +ms.author: wblocker +--- + +# New-CsTeamsCustomBannerText + +## SYNOPSIS + +Enables administrators to configure a custom text on the banner displayed when compliance recording bots start recording the call. + +## SYNTAX + +### Identity (Default) +``` +New-CsTeamsCustomBannerText [[-Id] <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION + +Creates a single instance of a custom banner text. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> New-CsTeamsCustomBannerText -Id 123e4567-e89b-12d3-a456-426614174000 -Description "Custom Banner Text Example" -Text "Custom Text" +``` + +This example creates an instance of TeamsCustomBannerText with the name CustomText. + +## PARAMETERS + +### -Id +The Identity of the CustomBannerText. You do not need to provide an ID as the backend will generate it for you. However, if you wish to provide your own ID, you can provide your own GUID. Note that you have to provide a unique ID for every CsTeamsCustomBannerText you create. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Text +The text that the global admin would like to set in the policy. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description that the global admin would like to set to identify what this text represents. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/set-csteamscustombannertext) + +[New-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext) + +[Remove-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/remove-csteamscustombannertext) diff --git a/teams/teams-ps/teams/New-CsTeamsEmergencyCallRoutingPolicy.md b/teams/teams-ps/teams/New-CsTeamsEmergencyCallRoutingPolicy.md new file mode 100644 index 0000000000..0cc06eb366 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsEmergencyCallRoutingPolicy.md @@ -0,0 +1,163 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallroutingpolicy +applicable: Microsoft Teams +title: New-CsTeamsEmergencyCallRoutingPolicy +author: serdarsoysal +ms.author: serdars +manger: roykuntz +ms.reviewer: chenc, vaddank +schema: 2.0.0 +--- + +# New-CsTeamsEmergencyCallRoutingPolicy + +## SYNOPSIS +This cmdlet creates a new Teams Emergency Call Routing policy with one or more emergency number. + +## SYNTAX + +``` +New-CsTeamsEmergencyCallRoutingPolicy [-Identity] <string> [-AllowEnhancedEmergencyServices <bool>] + [-Description <string>] [-EmergencyNumbers <Object>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a new Teams Emergency Call Routing policy with one or more emergency numbers. Teams Emergency Call Routing policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration. + +## EXAMPLES + +### Example 1 +```powershell +$en1 = New-CsTeamsEmergencyNumber -EmergencyDialString "911" -EmergencyDialMask "933" -OnlinePSTNUsage "USE911" +New-CsTeamsEmergencyCallRoutingPolicy -Identity "Test" -EmergencyNumbers @{add=$en1} -AllowEnhancedEmergencyServices:$true -Description "test" +``` + +This example first creates a new Teams emergency number object and then creates a Teams Emergency Call Routing policy with this emergency number object. +Note that the OnlinePSTNUsage specified in the first command must previously exist. Note that the resulting object from the New-CsTeamsEmergencyNumber only exists in memory, so you must apply it to a policy to be used. +Note that {@add=....} will try to append a new emergency number to the values taken from the global instance. + +### Example 2 +```powershell +$en1 = New-CsTeamsEmergencyNumber -EmergencyDialString "911" -EmergencyDialMask "933" -OnlinePSTNUsage "USE911" +New-CsTeamsEmergencyCallRoutingPolicy -Identity "testecrp" -EmergencyNumbers $en1 -AllowEnhancedEmergencyServices:$true -Description "test" +``` +This example overrides the global emergency numbers from the global instance. + +## PARAMETERS + +### -Identity +The Identity parameter is a unique identifier that designates the name of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEnhancedEmergencyServices +Flag to enable Enhanced Emergency Services. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter describes the Teams Emergency Call Routing policy - what it's for, what type of user it applies to and any other information that helps to identify the purpose of this policy. Maximum characters: 512. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyNumbers +One or more emergency number objects obtained from the [New-CsTeamsEmergencyNumber](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencynumber) cmdlet. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallroutingpolicy) + +[Grant-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallroutingpolicy) + +[Remove-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallroutingpolicy) + +[Get-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallroutingpolicy) + +[New-CsTeamsEmergencyNumber](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencynumber) diff --git a/teams/teams-ps/teams/New-CsTeamsEmergencyCallingExtendedNotification.md b/teams/teams-ps/teams/New-CsTeamsEmergencyCallingExtendedNotification.md new file mode 100644 index 0000000000..693ea5b9cd --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsEmergencyCallingExtendedNotification.md @@ -0,0 +1,116 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingextendednotification +applicable: Microsoft Teams +title: New-CsTeamsEmergencyCallingExtendedNotification +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: +schema: 2.0.0 +--- + +# New-CsTeamsEmergencyCallingExtendedNotification + +## SYNOPSIS + +## SYNTAX + +``` +New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString <string> [-NotificationGroup <string>] + [-NotificationDialOutNumber <string>] [-NotificationMode <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet supports creating specific emergency calling notification settings per emergency phone number. It is used with TeamsEmergencyCallingPolicy. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> $en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "alert2@contoso.com" -NotificationMode ConferenceUnMuted +``` + +Creates an extended emergency calling notification for the emergency phone number 911 and stores it in the variable $en1. The variable should be added afterward to a TeamsEmergencyCallingPolicy instance. + +## PARAMETERS + +### -EmergencyDialString +Specifies the emergency phone number. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationGroup +NotificationGroup is an email list of users and groups to be notified of an emergency call. Individual users or groups are separated by ";", for instance, "group1@contoso.com;group2@contoso.com". A maximum of 10 entries consisting of users and/or groups can be added to the NotificationGroup. The total number of users notified cannot exceed 50. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationDialOutNumber +This parameter represents the PSTN number which can be dialed out if NotificationMode is set to either of the two Conference values. The PSTN phone cannot be unmuted even when the NotificationMode is set to ConferenceUnMuted. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationMode +The type of conference experience for security desk notification. + +```yaml +Type: Microsoft.Rtc.Management.WritableConfig.Policy.Teams.NotificationMode +Parameter Sets: (All) +Aliases: +Accepted values: NotificationOnly, ConferenceMuted, ConferenceUnMuted + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallingpolicy) + +[New-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsEmergencyCallingPolicy.md b/teams/teams-ps/teams/New-CsTeamsEmergencyCallingPolicy.md new file mode 100644 index 0000000000..60f9db0fb7 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsEmergencyCallingPolicy.md @@ -0,0 +1,243 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingpolicy +applicable: Microsoft Teams +title: New-CsTeamsEmergencyCallingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc +schema: 2.0.0 +--- + +# New-CsTeamsEmergencyCallingPolicy + +## SYNOPSIS + +## SYNTAX + +``` +New-CsTeamsEmergencyCallingPolicy [-Identity] <string> [-ExtendedNotifications <PSListModifier[TeamsEmergencyCallingExtendedNotification]>] + [-NotificationGroup <string>] [-NotificationDialOutNumber <string>] [-ExternalLocationLookupMode <ExternalLocationLookupMode>] + [-NotificationMode <NotificationMode>] [-EnhancedEmergencyServiceDisclaimer <string>] [-Description <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] + ``` + +## DESCRIPTION +This cmdlet creates a new Teams Emergency Calling policy. Emergency calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. + +## EXAMPLES + +### Emergency calling policy Example 1 +In the following example, ECP1, an emergency calling policy with identify ECP1 is configured with full security desk configuration. Extended notifications for the test emergency number, 933, are set to null. +**ECP1** +<ul> + <li>Notification group: alert@contoso.com</li> + <li>Notification Dial Out Number - 14255551234</li> + <li>Notification Mode - Conferenced in and are unmuted</li> + <li>External Lookup Mode - On</li> +</ul> + +```powershell +$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "933" +New-CsTeamsEmergencyCallingPolicy -Identity ECP1 -Description "Test ECP1" -NotificationGroup "alert@contoso.com" -NotificationDialOutNumber "+14255551234" -NotificationMode ConferenceUnMuted -ExternalLocationLookupMode Enabled -ExtendedNotifications @{add=$en1} +``` + +### Emergency calling policy Example 2 +In the following example, ECP2, an emergency calling policy with identify ECP2 is configured with both 911 and 933 in the extended notification settings. Extended notifications for the test emergency number 911 are set to notify two groups separated by ";" and for 933 are set to null. +**ECP2** +<ul> + <li>Notification group: null</li> + <li>Notification Dial Out Number - null</li> + <li>Notification Mode - null</li> + <li>External Lookup Mode - On</li> +</ul> + +```powershell +$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "alert@contoso.com;567@contoso.com" -NotificationDialOutNumber "+14255551234" -NotificationMode ConferenceUnMuted +$en2 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "933" +New-CsTeamsEmergencyCallingPolicy -Identity ECP2 -Description "Test ECP2" -ExternalLocationLookupMode Enabled -ExtendedNotifications @{add=$en1,$en2} +``` + +## PARAMETERS + +### -Identity + The Identity parameter is a unique identifier that designates the name of the policy + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter describes the Teams Emergency Calling policy - what it is for, what type of user it applies to and any other information that helps to identify the purpose of this policy. Maximum characters: 512. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnhancedEmergencyServiceDisclaimer +Allows the tenant administrator to configure a text string, which is shown at the top of the Calls app. The user can acknowledge the string by selecting OK. The string will be shown on client restart. The disclaimer can be up to 350 characters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedNotifications + +A list of one or more instances of TeamsEmergencyCallingExtendedNotification. Each TeamsEmergencyCallingExtendedNotification should use a unique EmergencyDialString. + +If an extended notification is found for an emergency phone number based on the EmergencyDialString parameter the extended notification will be controlling the notification. If no extended notification is found the notification settings on the policy instance itself will be used. + +```yaml +Type: System.Management.Automation.PSListModifier[Microsoft.Teams.Policy.Administration.Cmdlets.Core.TeamsEmergencyCallingExtendedNotification] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalLocationLookupMode +Enable ExternalLocationLookupMode. This mode allow users to set Emergency addresses for remote locations. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.ExternalLocationLookupMode +Parameter Sets: (All) +Aliases: +Accepted values: Disabled, Enabled + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationDialOutNumber +This parameter represents the PSTN number which can be dialed out if NotificationMode is set to either of the two Conference values. The PSTN phone cannot be unmuted even when the NotificationMode is set to ConferenceUnMuted. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationGroup +NotificationGroup is an email list of users and groups to be notified of an emergency call via Teams chat. Individual users or groups are separated by ";", for instance, "group1@contoso.com;group2@contoso.com". A maximum of 10 e-mail addresses can be specified and a maximum of 50 users in total can be notified. Both UPN and SMTP address are accepted when adding users directly. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationMode +The type of conference experience for security desk notification. +Possible values are NotificationOnly, ConferenceMuted, and ConferenceUnMuted. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.NotificationMode +Parameter Sets: (All) +Aliases: +Accepted values: NotificationOnly, ConferenceMuted, ConferenceUnMuted + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallingpolicy) + +[Grant-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallingpolicy) + +[Remove-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallingpolicy) + +[Set-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallingpolicy) + +[New-CsTeamsEmergencyCallingExtendedNotification](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingextendednotification) diff --git a/teams/teams-ps/teams/New-CsTeamsEmergencyNumber.md b/teams/teams-ps/teams/New-CsTeamsEmergencyNumber.md new file mode 100644 index 0000000000..9d89a4ced3 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsEmergencyNumber.md @@ -0,0 +1,107 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencynumber +applicable: Microsoft Teams +title: New-CsTeamsEmergencyNumber +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc, pthota +schema: 2.0.0 +--- + +# New-CsTeamsEmergencyNumber + +## SYNOPSIS + +## SYNTAX + +``` +New-CsTeamsEmergencyNumber [-EmergencyDialString <String>] [-EmergencyDialMask <String>] + [-OnlinePSTNUsage <String>] [<CommonParameters>] +``` + +## DESCRIPTION + This cmdlet supports creating multiple Teams emergency numbers. Used with TeamsEmergencyCallRoutingPolicy and only relevant for Direct Routing. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsEmergencyNumber -EmergencyDialString 911 -EmergencyDialMask 933 -OnlinePSTNUsage "US911" +``` + + Create a new Teams emergency number + +### Example 2 +```powershell +PS C:\> New-CsTeamsEmergencyNumber -EmergencyDialString "112" -EmergencyDialMask "117;897" -OnlinePSTNUsage "EU112" +``` + +Create a new Teams emergency number with multiple emergency dial masks. + +## PARAMETERS + +### -EmergencyDialMask + For each Teams emergency number, you can specify zero or more emergency dial masks. A dial mask is a number that you want to translate into the value of the emergency dial number value when it is dialed. Dial mask must be list of numbers separated by semicolon. Each number string must be made of the digits 0 through 9 and can be from 1 to 10 digits in length. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyDialString + Specifies the emergency phone number + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePSTNUsage + Specify the online public switched telephone network (PSTN) usage + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallroutingpolicy) + +[New-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallroutingpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsEnhancedEncryptionPolicy.md b/teams/teams-ps/teams/New-CsTeamsEnhancedEncryptionPolicy.md new file mode 100644 index 0000000000..94d8089d7a --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsEnhancedEncryptionPolicy.md @@ -0,0 +1,189 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsenhancedencryptionpolicy +title: New-CsTeamsEnhancedEncryptionPolicy +author: serdarsoysal +ms.author: serdars +manager: mdress +schema: 2.0.0 +--- + +# New-CsTeamsEnhancedEncryptionPolicy + +## SYNOPSIS +Use this cmdlet to create a new Teams enhanced encryption policy. + +## SYNTAX + +``` +New-CsTeamsEnhancedEncryptionPolicy [-Description <Object>] [-CallingEndtoEndEncryptionEnabledType <Object>] [-MeetingEndToEndEncryption <Object>] + [[-Identity] <Object>] [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to create a new Teams enhanced encryption policy. + +The TeamsEnhancedEncryptionPolicy enables administrators to determine which users in your organization can use the enhanced encryption settings in Teams, setting for end-to-end encryption in ad-hoc 1-to-1 VOIP calls is the parameter supported by this policy currently. + +## EXAMPLES + +### EXAMPLE 1 +```PowerShell +PS C:\> New-CsTeamsEnhancedEncryptionPolicy -Identity ContosoPartnerTeamsEnhancedEncryptionPolicy +``` + +Creates a new instance of TeamsEnhancedEncryptionPolicy called ContosoPartnerTeamsEnhancedEncryptionPolicy and applies the default values to its settings. + +### EXAMPLE 2 +```PowerShell +PS C:\> New-CsTeamsEnhancedEncryptionPolicy -Identity ContosoPartnerTeamsEnhancedEncryptionPolicy -CallingEndtoEndEncryptionEnabledType DisabledUserOverride -MeetingEndToEndEncryption DisabledUserOverride +``` + +Creates a new instance of TeamsEnhancedEncryptionPolicy called ContosoPartnerTeamsEnhancedEncryptionPolicy and applies the provided values to its settings. + +## PARAMETERS + +### -Description +Enables administrators to provide explanatory text to accompany a Teams enhanced encryption policy. + +For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallingEndtoEndEncryptionEnabledType +Determines whether end-to-end encrypted calling is available for the user in Teams. Set this to DisabledUserOverride to allow user to turn on end-to-end encrypted calls. Set this to Disabled to prohibit. + +```yaml +Type: Enum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingEndToEndEncryption +Determines whether end-to-end encrypted meetings are available in Teams ([requires a Teams Premium license](https://www.microsoft.com/en-us/microsoft-teams/premium)). Set this to DisabledUserOverride to allow users to schedule end-to-end encrypted meetings. Set this to Disabled to prohibit. + +```yaml +Type: Enum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the Teams enhanced encryption policy. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling Set-CsTeamsEnhancedEncryptionPolicy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsenhancedencryptionpolicy) + +[Set-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsenhancedencryptionpolicy) + +[Remove-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsenhancedencryptionpolicy) + +[Grant-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsenhancedencryptionpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsEventsPolicy.md b/teams/teams-ps/teams/New-CsTeamsEventsPolicy.md new file mode 100644 index 0000000000..778df29878 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsEventsPolicy.md @@ -0,0 +1,391 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamseventspolicy +title: New-CsTeamsEventsPolicy +schema: 2.0.0 +ms.date: 04/23/2025 +--- + +# New-CsTeamsEventsPolicy + +## SYNOPSIS +This cmdlet allows you to create a new TeamsEventsPolicy instance and set its properties. Note that this policy is currently still in preview. + +## SYNTAX + +```powershell +New-CsTeamsEventsPolicy [-Identity] <String> [-AllowWebinars <String>] [-AllowTownhalls <String>] [-AllowEmailEditing <String>] [-Description <String>] +[-TownhallEventAttendeeAccess <String>] [-RecordingForTownhall <String>] [-RecordingForWebinar <String>] +[-TranscriptionForTownhall <String>] [-TranscriptionForWebinar <String>] [-AllowEventIntegrations <Boolean>] [-TownhallChatExperience <String>] +[-UseMicrosoftECDN <String>] [-EventAccessType <String>] [-BroadcastPremiumApps <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +TeamsEventsPolicy is used to configure options for customizing Teams Events experiences. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsEventsPolicy -Identity DisablePublicWebinars -AllowWebinars Enabled -EventAccessType EveryoneInCompanyExcludingGuests +``` + +The command shown in Example 1 creates a new per-user Teams Events policy with the Identity DisablePublicWebinars. This policy disables a user from creating public webinars. + +### Example 2 +```powershell +PS C:\> New-CsTeamsEventsPolicy -Identity DisableWebinars -AllowWebinars Disabled +``` + +The command shown in Example 2 creates a new per-user Teams Events policy with the Identity DisableWebinars. This policy disables a user from creating webinars. + +## PARAMETERS + +### -AllowWebinars +This setting governs if a user can create webinars using Teams Events. +Possible values are: + - **Enabled**: Enables creating webinars. + - **Disabled**: Disables creating webinars. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseMicrosoftECDN +This setting governs whether the admin disables this property and prevents the organizers from creating town halls that use Microsoft eCDN even though they have been assigned a Teams Premium license. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTownhalls +This setting governs if a user can create town halls using Teams Events. +Possible values are: + - **Enabled**: Enables creating town halls. + - **Disabled**: Disables creating town hall. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TownhallEventAttendeeAccess +This setting governs what identity types may attend a Town hall that is scheduled by a particular person or group that is assigned this policy. +Possible values are: + - **Everyone**: Anyone with the join link may enter the event. + - **EveryoneInOrganizationAndGuests**: Only those who are Guests to the tenant, MTO users, and internal AAD users may enter the event. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Everyone +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEmailEditing +This setting governs if a user is allowed to edit the communication emails in Teams Town Hall or Teams Webinar events. +Possible values are: + - **Enabled**: Enables editing of communication emails. + - **Disabled**: Disables editing of communication emails. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventAccessType +This setting governs which users can access the Town hall event and access the event registration page or the event site to register for a Webinar. It also governs which user type is allowed to join the session or sessions in the event for both event types. + +Possible values are: + - **Everyone**: Enables creating events to allow in-tenant, guests, federated, and anonymous (external to the tenant) users to register and join the event. + + - **EveryoneInCompanyExcludingGuests**: For Webinar - enables creating events to allow only in-tenant users to register and join the event. For Town hall - enables creating events to allow only in-tenant users to join the event (Note: for Town hall, in-tenant users include guests; this parameter will disable public Town halls). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Everyone +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedQuestionTypesInRegistrationForm +This setting governs which users in a tenant can add which registration form questions to an event registration page for attendees to answer when registering for the event. + +Possible values are: DefaultOnly, DefaultAndPredefinedOnly, AllQuestions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedTownhallTypesForRecordingPublish +This setting governs which types of town halls can have their recordings published. + +Possible values are: None, InviteOnly, EveryoneInCompanyIncludingGuests, Everyone. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedWebinarTypesForRecordingPublish +This setting governs which types of webinars can have their recordings published. + +Possible values are: None, InviteOnly, EveryoneInCompanyIncludingGuests, Everyone. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordingForTownhall +Determines whether recording is allowed in a user's townhall. +Possible values are: + - **Enabled**: Allow recording in user's townhalls. + - **Disabled**: Prohibit recording in user's townhalls. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` +### -RecordingForWebinar +Determines whether recording is allowed in a user's webinar. +Possible values are: + - **Enabled**: Allow recording in user's webinars. + - **Disabled**: Prohibit recording in user's webinars. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` +### -TranscriptionForTownhall +Determines whether transcriptions are allowed in a user's townhall. +Possible values are: + - **Enabled**: Allow transcriptions in user's townhalls. + - **Disabled**: Prohibit transcriptions in user's townhalls. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` +### -TranscriptionForWebinar +Determines whether transcriptions are allowed in a user's webinar. +Possible values are: + - **Enabled**: Allow transcriptions in user's webinars. + - **Disabled**: Prohibit transcriptions in user's webinars. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEventIntegrations +This setting governs the access to the integrations tab in the event creation workflow. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TownhallChatExperience +This setting governs if the user can enable the Comment Stream chat experience for Townhalls. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BroadcastPremiumApps +This setting will enable Tenant Admins to specify if an organizer of a Teams Premium town hall may add an app that is accessible by everyone, including attendees, in a broadcast style Event including a Town hall. This does not include control over apps (such as AI Producer and Custom Streaming Apps) that are only accessible by the Event group. + +Possible values are: +- **Enabled**: An organizer of a Premium town hall can add a Premium App such as Polls to the Town hall +- **Disabled**: An organizer of a Premium town hall CANNOT add a Premium App such as Polls to the Town hall + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch does not work with this cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams Events policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the Teams Events policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch does not work with this cmdlet. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsFeedbackPolicy.md b/teams/teams-ps/teams/New-CsTeamsFeedbackPolicy.md new file mode 100644 index 0000000000..97eb4b84ce --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsFeedbackPolicy.md @@ -0,0 +1,237 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsfeedbackpolicy +applicable: Microsoft Teams +title: New-CsTeamsFeedbackPolicy +schema: 2.0.0 +--- + +# New-CsTeamsFeedbackPolicy + +## SYNOPSIS +Use this cmdlet to control whether users in your organization can send feedback about Teams to Microsoft through Give feedback and whether they receive the survey. + +## SYNTAX + +```powershell +New-CsTeamsFeedbackPolicy [-WhatIf] [-Confirm] [[-Identity] <Object>] [-Tenant <Object>] [-InMemory] +[-AllowEmailCollection <Boolean>] [-AllowLogCollection <Boolean>] [-AllowScreenshotCollection <Boolean>] [-EnableFeatureSuggestions <Boolean>] + [-UserInitiatedMode <String>] [-ReceiveSurveysMode <String>] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to control whether users in your organization can send feedback about Teams to Microsoft through Give feedback and whether they receive the survey. By default, all users in your organization are automatically assigned the global (Org-wide default) policy and the Give feedback feature and survey are enabled in the policy. The exception is Teams for Education, where the features are enabled for teachers and disabled for students. For more information, visit [Manage feedback policies in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-feedback-policies-in-teams). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsFeedbackPolicy -identity "New Hire Feedback Policy" -userInitiatedMode disabled -receiveSurveysMode disabled +``` + +In this example, we create a feedback policy called New Hire Feedback Policy and we turn off the ability to give feedback through Give feedback and the survey. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppress all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A unique identifier. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +The InMemory parameter creates an object reference without actually committing the object as a permanent change. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveSurveysMode +Set the receiveSurveysMode parameter to enabled to allow users who are assigned the policy to receive the survey. + +Possible values: + - Enabled + - Disabled + - EnabledUserOverride + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserInitiatedMode + Set the userInitiatedMode parameter to enabled to allow users who are assigned the policy to give feedback. + Setting the parameter to disabled turns off the feature and users who are assigned the policy don't have the option to give feedback. + + Possible values: + - Enabled + - Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEmailCollection +Set this to TRUE to enable Email collection. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLogCollection +Set this to TRUE to enable log collection. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowScreenshotCollection +Set this to TRUE to enable Screenshot collection. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableFeatureSuggestions + This setting will enable Tenant Admins to hide or show the Teams menu item “Help | Suggest a Feature”. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsFilesPolicy.md b/teams/teams-ps/teams/New-CsTeamsFilesPolicy.md new file mode 100644 index 0000000000..dca829ac76 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsFilesPolicy.md @@ -0,0 +1,168 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsfilespolicy +title: New-CsTeamsFilesPolicy +schema: 2.0.0 +--- + +# New-CsTeamsFilesPolicy + +## SYNOPSIS +Creates a new teams files policy. +teams files policies determine whether or not files entry points to sharepoint enabled for a user. +The policies also specify third party app id to allow file storage(eg. Box). + +## SYNTAX + +```powershell +New-CsTeamsFilesPolicy [-NativeFileEntryPoints <String>] [-SPChannelFilesTab <String>] + [-DefaultFileUploadAppId <String>] [-FileSharingInChatswithExternalUsers <String>] [-Identity] <String> + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +If your organization chooses a third-party for content storage, you can turn off the NativeFileEntryPoints parameter in the Teams Files policy. This parameter is enabled by default, which shows option to attach OneDrive / SharePoint content from Teams chats or channels. When this parameter is disabled, users won't see access points for OneDrive and SharePoint in Teams. Please note that OneDrive app in the left navigation pane in Teams isn't affected by this policy. +Teams administrators would be able to create a customized teams files policy to match the organization's requirements. + +## EXAMPLES + +### Example 1 +```powershell +New-CsTeamsFilesPolicy -Identity "CustomTeamsFilesPolicy" -NativeFileEntryPoints Disabled/Enabled +``` + +The command shown in Example 1 creates a per-user teams files policy CustomTeamsFilesPolicy with NativeFileEntryPoints set to Disabled/Enabled and other fields set to tenant level global value. + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NativeFileEntryPoints +This parameter is enabled by default, which shows the option to upload content from ODSP to Teams chats or channels. . +Possible values are Enabled or Disabled. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False + +``` + +### -DefaultFileUploadAppId +This can be used by the 3p apps to configure their app, so when the files will be dragged and dropped in compose, it will get uploaded in that 3P app. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileSharingInChatswithExternalUsers + +Indicates if file sharing in chats with external users is enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SPChannelFilesTab + +Indicates whether Iframe channel files tab is enabled, if not, integrated channel files tab will be enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsfilespolicy) + diff --git a/teams/teams-ps/teams/New-CsTeamsHiddenMeetingTemplate.md b/teams/teams-ps/teams/New-CsTeamsHiddenMeetingTemplate.md new file mode 100644 index 0000000000..afae69de7e --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsHiddenMeetingTemplate.md @@ -0,0 +1,72 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +title: New-CsTeamsHiddenMeetingTemplate +author: boboPD +ms.author: pradas +online version: https://learn.microsoft.com/powershell/module/teams/New-CsTeamsHiddenMeetingTemplate +schema: 2.0.0 +--- + +# New-CsTeamsHiddenMeetingTemplate + +## SYNOPSIS +This cmdlet is used to create a `HiddenMeetingTemplate` object for use with the [New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy) and [Set-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingtemplatepermissionpolicy) cmdlets. + +## SYNTAX + +```powershell +New-CsTeamsHiddenMeetingTemplate -Id <string> [<CommonParameters>] +``` + +## DESCRIPTION + +Creates an object that can be supplied as `HiddenMeetingTemplate` to the [New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy) and [Set-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingtemplatepermissionpolicy) cmdlets. + +## EXAMPLES + +### Example 1 - Creating a new hidden meeting template + +Creates a new hidden meeting template object: + +```powershell +PS> $hiddentemplate_1 = New-CsTeamsHiddenMeetingTemplate -Id customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056 +``` + +Creates a new HiddenMeetingTemplate object with the given template ID. + +For more examples of how this can be used, see the examples for [New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy). + +## PARAMETERS + +### -Id + +ID of the meeting template to hide. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingtemplatepermissionpolicy) + +[New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy) + +[Set-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingtemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsHiddenTemplate.md b/teams/teams-ps/teams/New-CsTeamsHiddenTemplate.md new file mode 100644 index 0000000000..5df0f7b450 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsHiddenTemplate.md @@ -0,0 +1,69 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamshiddentemplate +title: New-CsTeamsHiddenTemplate +author: yishuaihuang4 +ms.author: yishuaihuang +ms.reviewer: +manager: weiliu2 +schema: 2.0.0 +--- + +# New-CsTeamsHiddenTemplate + +## SYNOPSIS +This cmdlet is used to create a `HiddenTemplate` object for use with the [New-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy) and [Set-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstemplatepermissionpolicy) cmdlets. + +## SYNTAX + +``` +New-CsTeamsHiddenTemplate -Id <String> [<CommonParameters>] +``` + +## DESCRIPTION +Creates an object that can be supplied as `HiddenTemplate` to the [New-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy) and [Set-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstemplatepermissionpolicy) cmdlets. + +## EXAMPLES + +### Example 1 +```powershell +PS >$manageProjectTemplate = New-CsTeamsHiddenTemplate -Id com.microsoft.teams.template.ManageAProject +``` + +Creates a new hidden Teams template object. For more examples of how this can be used, see the examples for [New-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy). + +## PARAMETERS + +### -Id +ID of the Teams template to hide. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### HiddenTemplate.Cmdlets.HiddenTemplate + +## NOTES + +## RELATED LINKS +[New-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy) + +[Set-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsIPPhonePolicy.md b/teams/teams-ps/teams/New-CsTeamsIPPhonePolicy.md new file mode 100644 index 0000000000..93cdfa7a78 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsIPPhonePolicy.md @@ -0,0 +1,261 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsipphonepolicy +applicable: Microsoft Teams +title: New-CsTeamsIPPhonePolicy +author: tonywoodruff +ms.author: anwoodru +ms.reviewer: kponnus +manager: sandrao +schema: 2.0.0 +--- + +# New-CsTeamsIPPhonePolicy + +## SYNOPSIS + +New-CsTeamsIPPhonePolicy allows you to create a policy to manage features related to Teams phone experiences. Teams phone policies determine the features that are available to users. + +## SYNTAX + +``` +New-CsTeamsIPPhonePolicy [[-Identity] <XdsIdentity>] + [-AllowBetterTogether <String>] + [-AllowHomeScreen <String>] + [-AllowHotDesking <Boolean>] + [-Confirm] + [-Description <String>] + [-Force] + [-HotDeskingIdleTimeoutInMinutes <Int>] + [-InMemory] + [-SearchOnCommonAreaPhoneMode <Object>] + [-SignInMode <String>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION + +The New-CsTeamsIPPhonePolicy cmdlet allows you to create a policy to manage features related to Teams phone experiences assigned to a user account used to sign into a Teams phone. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsIPPhonePolicy -Identity CommonAreaPhone -SignInMode CommonAreaPhoneSignin +``` +This example shows a new policy being created called "CommonAreaPhone" setting the SignInMode as "CommonAreaPhoneSignIn". + +## PARAMETERS + +### -Identity +The identity of the policy that you want to create. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBetterTogether +Determines whether Better Together mode is enabled, phones can lock and unlock in an integrated fashion when connected to their Windows PC running a 64-bit Teams desktop client. +Possible values this parameter can take: + +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowHomeScreen +Determines whether the Home Screen feature of the Teams IP Phones is enabled. +Possible values this parameter can take: + +- Enabled +- EnabledUserOverride +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: EnabledUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowHotDesking +Determines whether hot desking mode is enabled. Set this to TRUE to enable. Set this to FALSE to disable hot desking mode. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Free form text that can be used by administrators as desired. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HotDeskingIdleTimeoutInMinutes +Determines the idle timeout value in minutes for the signed in user account. When the timeout is reached, the account is logged out. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SearchOnCommonAreaPhoneMode +Determines whether a user can search the Global Address List in Common Area Phone Mode. Set this to ENABLED to enable the feature. Set this to DISABLED to disable the feature. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignInMode +Determines the sign in mode for the device when signing in to Teams. +Possible Values: +- 'UserSignIn: Enables the individual user's Teams experience on the phone' +- 'CommonAreaPhoneSignIn: Enables a Common Area Phone experience on the phone' +- 'MeetingSignIn: Enables the meeting/conference room experience on the phone' + +```yaml +Type: String + +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsMediaConnectivityPolicy.md b/teams/teams-ps/teams/New-CsTeamsMediaConnectivityPolicy.md new file mode 100644 index 0000000000..3f141907b4 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsMediaConnectivityPolicy.md @@ -0,0 +1,87 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: New-CsTeamsMediaConnectivityPolicy +online version: https://learn.microsoft.com/powershell/module/teams/New-CsTeamsMediaConnectivityPolicy +schema: 2.0.0 +author: lirunping-MSFT +ms.author: runli +--- + +# New-CsTeamsMediaConnectivityPolicy + +## SYNOPSIS +This cmdlet creates a Teams media connectivity policy. + +## SYNTAX + +```powershell +New-CsTeamsMediaConnectivityPolicy -Identity <String> [-DirectConnection <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a Teams media connectivity policy. If you get an error that the policy already exists, it means that the policy already exists for your tenant. In this case, run Get-CsTeamsMediaConnectivityPolicy. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsMediaConnectivityPolicy -Identity Test + +Identity DirectConnection +------------------------- +Tag:Test Enabled +``` +Creates a new Teams media connectivity policy with the specified identity. +The newly created policy with value will be printed on success. + +## PARAMETERS + +### -Identity +Identity of the Teams media connectivity policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DirectConnection +This setting will enable Tenant Admins to control the Teams media connectivity behavior in Teams for both Meetings and 1:1 calls. If this setting is set to true, a direct media connection between the current user and a remote user is allowed which may improve the meeting quality and reduce the egress bandwidth usage for the customer. If this setting is set to disabled, no direct media connection will be allowed for the current user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Remove-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmediaconnectivitypolicy) + +[Get-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmediaconnectivitypolicy) + +[Set-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmediaconnectivitypolicy) + +[Grant-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmediaconnectivitypolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsMeetingBrandingPolicy.md b/teams/teams-ps/teams/New-CsTeamsMeetingBrandingPolicy.md new file mode 100644 index 0000000000..6a2c7ee7cd --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsMeetingBrandingPolicy.md @@ -0,0 +1,252 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingbrandingpolicy +schema: 2.0.0 +title: New-CsTeamsMeetingBrandingPolicy +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: stanlythomas +--- + +# New-CsTeamsMeetingBrandingPolicy + +## SYNOPSIS +The **CsTeamsMeetingBrandingPolicy** cmdlet enables administrators to control the appearance in meetings by defining custom backgrounds, logos, and colors. + +## SYNTAX + +```powershell +New-CsTeamsMeetingBrandingPolicy + [-MeetingBackgroundImages <PSListModifier>] + [-MeetingBrandingThemes <PSListModifier>] + [-DefaultTheme <String>] [-EnableMeetingOptionsThemeOverride <Boolean>] + [-EnableNdiAssuranceSlate <Boolean>] [-NdiAssuranceSlateImages <PSListModifier>] [-RequireBackgroundEffect <Boolean>] + [-EnableMeetingBackgroundImages <Boolean>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a new **TeamsMeetingBrandingPolicy**. +You can only create an empty meeting branding policy with this cmdlet, image upload is not supported. +If you want to upload the images, you should use Teams Admin Center. + +## EXAMPLES + +### Create empty meeting branding policy +```powershell +PS C:\> New-CsTeamsMeetingBrandingPolicy -Identity "test policy" +``` + +In this example, the command will create an empty meeting branding policy with the identity `test policy`. + +## PARAMETERS + +### -DefaultTheme +*This parameter is reserved for Microsoft internal use only.* +Identity of default meeting theme. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMeetingBackgroundImages +Enable custom meeting backgrounds. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMeetingOptionsThemeOverride +Allow organizer to control meeting theme. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Identity of meeting branding policy that will be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingBackgroundImages +*This parameter is reserved for Microsoft internal use only.* +List of meeting background images. +Image upload is not possible via cmdlets. You should upload background images via Teams Admin Center. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingBrandingThemes +*This parameter is reserved for Microsoft internal use only.* +List of meeting branding themes. +Image upload is not possible via cmdlets. You should create meeting themes via Teams Admin Center. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableNdiAssuranceSlate +This enables meeting Network Device Interface Assurance Slate branding. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NdiAssuranceSlateImages +Used to specify images that can be used as assurance slates during NDI (Network Device Interface) streaming in Teams meetings. This parameter allows administrators to define a set of images that can be displayed to participants to ensure that the NDI stream is functioning correctly. + +```yaml +Type: System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.NdiAssuranceSlate] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequireBackgroundEffect +This mandates a meeting background for participants. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +Available in Teams PowerShell Module 4.9.3 and later. + +## RELATED LINKS + +[Get-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbrandingpolicy) + +[Grant-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingbrandingpolicy) + +[New-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingbrandingpolicy) + +[Remove-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingbrandingpolicy) + +[Set-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbrandingpolicy) diff --git a/skype/skype-ps/skype/New-CsTeamsMeetingBroadcastPolicy.md b/teams/teams-ps/teams/New-CsTeamsMeetingBroadcastPolicy.md similarity index 87% rename from skype/skype-ps/skype/New-CsTeamsMeetingBroadcastPolicy.md rename to teams/teams-ps/teams/New-CsTeamsMeetingBroadcastPolicy.md index 2f13e8a9ef..898cfcd848 100644 --- a/skype/skype-ps/skype/New-CsTeamsMeetingBroadcastPolicy.md +++ b/teams/teams-ps/teams/New-CsTeamsMeetingBroadcastPolicy.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csteamsmeetingbroadcastpolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingbroadcastpolicy +applicable: Microsoft Teams title: New-CsTeamsMeetingBroadcastPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsTeamsMeetingBroadcastPolicy @@ -33,16 +33,15 @@ User-level policy for tenant admin to configure meeting broadcast behavior for t ### Example 1 ```powershell -PS C:\> New-CsTeamsMeetingBroadcastPolicy -Identity Students -AllowBroadcastScheduling $false +PS C:\> New-CsTeamsMeetingBroadcastPolicy -Identity Students -AllowBroadcastScheduling $false ``` Creates a new MeetingBroadcastPolicy with broadcast scheduling disabled, which can then be assigned to individual users using the corresponding grant- command. - ## PARAMETERS ### -AllowBroadcastScheduling -Specifies whether this user can create broadcast events in Teams. This settng impacts broadcasts that use both self-service and external encoder production methods. +Specifies whether this user can create broadcast events in Teams. This setting impacts broadcasts that use both self-service and external encoder production methods. ```yaml Type: Boolean @@ -72,7 +71,7 @@ Accept wildcard characters: False ``` ### -BroadcastAttendeeVisibilityMode -Specifies the attendee visibility mode of the broadcast events created by this user.  This setting controls who can watch the broadcast event - e.g. anyone can watch this event including anonymous users or only authenticated users in my company can watch the event.  Note: this setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. +Specifies the attendee visibility mode of the broadcast events created by this user. This setting controls who can watch the broadcast event - e.g. anyone can watch this event including anonymous users or only authenticated users in my company can watch the event. Note: this setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. ```yaml Type: String @@ -216,8 +215,7 @@ Accept wildcard characters: False ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/New-CsTeamsMeetingPolicy.md b/teams/teams-ps/teams/New-CsTeamsMeetingPolicy.md new file mode 100644 index 0000000000..8c7b734046 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsMeetingPolicy.md @@ -0,0 +1,1964 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingpolicy +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: New-CsTeamsMeetingPolicy +schema: 2.0.0 +manager: bulenteg +ms.reviewer: alejandramu +ms.date: 2/26/2025 +--- + +# New-CsTeamsMeetingPolicy + +## SYNOPSIS + The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users. + +## SYNTAX + +```powershell +New-CsTeamsMeetingPolicy [-Identity] <XdsIdentity> + [-AIInterpreter <string>] + [-AllowAnonymousUsersToDialOut <Boolean>] + [-AllowAnonymousUsersToJoinMeeting <Boolean>] + [-AllowAnonymousUsersToStartMeeting <Boolean>] + [-AllowAnnotations <Boolean>] + [-AllowAvatarsInGallery <Boolean>] + [-AllowBreakoutRooms <String>] + [-AllowCarbonSummary <Boolean>] + [-AllowCartCaptionsScheduling <string>] + [-AllowChannelMeetingScheduling <Boolean>] + [-AllowCloudRecording <Boolean>] + [-AllowDocumentCollaboration <String>] + [-AllowedUsersForMeetingContext <String>] + [-AllowEngagementReport <String>] + [-AllowExternalNonTrustedMeetingChat <Boolean>] + [-AllowExternalParticipantGiveRequestControl <Boolean>] + [-AllowImmersiveView <Boolean>] + [-AllowIPAudio <Boolean>] + [-AllowIPVideo <Boolean>] + [-AllowLocalRecording] + [-AllowMeetingCoach <Boolean>] + [-AllowMeetNow <Boolean>] + [-AllowMeetingReactions <Boolean>] + [-AllowMeetingRegistration <Boolean>] + [-AllowNDIStreaming <Boolean>] + [-AllowNetworkConfigurationSettingsLookup <Boolean>] + [-AllowOrganizersToOverrideLobbySettings <Boolean>] + [-AllowOutlookAddIn <Boolean>] + [-AllowPSTNUsersToBypassLobby <Boolean>] + [-AllowParticipantGiveRequestControl <Boolean>] + [-AllowPowerPointSharing <Boolean>] + [-AllowPrivateMeetNow <Boolean>] + [-AllowPrivateMeetingScheduling <Boolean>] + [-AllowRecordingStorageOutsideRegion <Boolean>] + [-AllowScreenContentDigitization <Boolean>] + [-AllowSharedNotes <Boolean>] + [-AllowTasksFromTranscript <String>] + [-AllowTrackingInReport <Boolean>] + [-AllowTranscription <Boolean>] + [-AllowUserToJoinExternalMeeting <String>] + [-AllowWatermarkCustomizationForCameraVideo <Boolean>] + [-AllowWatermarkCustomizationForScreenSharing <Boolean>] + [-AllowWatermarkForCameraVideo <Boolean>] + [-AllowWatermarkForScreenSharing <Boolean>] + [-AllowWhiteboard <Boolean>] + [-AllowedStreamingMediaInput <String>] + [-AnonymousUserAuthenticationMethod <String>] + [-AttendeeIdentityMasking <String>] + [-AudibleRecordingNotification <String>] + [-AutoAdmittedUsers <String>] + [-AutomaticallyStartCopilot <String>] + [-BlockedAnonymousJoinClientTypes <List>] + [-CaptchaVerificationForMeetingJoin <String>] + [-ChannelRecordingDownload <String>] + [-ConnectToMeetingControls <String>] + [-Confirm] + [-ContentSharingInExternalMeetings <String>] + [-Copilot <String>] + [-CopyRestriction <Boolean>] + [-Description <String>] + [-DesignatedPresenterRoleMode <String>] + [-DetectSensitiveContentDuringScreenSharing <Boolean>] + [-EnrollUserOverride <String>] + [-ExplicitRecordingConsent <String>] + [-ExternalMeetingJoin <String>] + [-Force] + [-IPAudioMode <String>] + [-IPVideoMode <String>] + [-InfoShownInReportMode <String>] + [-InMemory] + [-LiveCaptionsEnabledType <String>] + [-LiveInterpretationEnabledType <String>] + [-LiveStreamingMode <String>] + [-LobbyChat <string>] + [-MediaBitRateKb <UInt32>] + [-MeetingChatEnabledType <String>] + [-MeetingInviteLanguages <String>] + [-NewMeetingRecordingExpirationDays <Int32>] + [-NoiseSuppressionForDialInParticipants <String>] + [-ParticipantNameChange <String>] + [-PreferredMeetingProviderForIslandsMode <String>] + [-QnAEngagementMode <String>] + [-RecordingStorageMode <String>] + [-RoomAttributeUserOverride <String>] + [-RoomPeopleNameUserOverride <String>] + [-ScreenSharingMode <String>] + [-SmsNotifications <String>] + [-SpeakerAttributionMode <String>] + [-StreamingAttendeeMode <String>] + [-TeamsCameraFarEndPTZMode <String>] + [-Tenant <Guid>] + [-UsersCanAdmitFromLobby <String>] + [-VideoFiltersMode <String>] + [-VoiceIsolation <String>] + [-VoiceSimulationInInterpreter <string>] + [-WatermarkForAnonymousUsers <String>] + [-WatermarkForCameraVideoOpacity <Int64>] + [-WatermarkForCameraVideoPattern <String>] + [-WatermarkForScreenSharingOpacity <Int64>] + [-WatermarkForScreenSharingPattern <String>] + [-AllowedUsersForMeetingDetails <String>] + [-RealTimeText <String>] + [-WhatIf] + [-WhoCanRegister <Object>] + [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users. + +The New-CsTeamsMeetingPolicy cmdlet allows administrators to define new meeting policies that can be assigned to particular users to control Teams features related to meetings. +## EXAMPLES + +### -------------------------- EXAMPLE 1 -------------------------- +``` +New-CsTeamsMeetingPolicy -Identity SalesMeetingPolicy -AllowTranscription $True +``` + +The command shown in Example 1 uses the New-CsTeamsMeetingPolicy cmdlet to create a new meeting policy with the Identity SalesMeetingPolicy. +This policy will use all the default values for a meeting policy except one: AllowTranscription; in this example, meetings for users with this policy can include real time or post meeting captions and transcriptions. + +### -------------------------- EXAMPLE 2 -------------------------- +``` +New-CsTeamsMeetingPolicy -Identity HrMeetingPolicy -AutoAdmittedUsers "Everyone" -AllowMeetNow $False +``` + +In Example 2, the New-CsTeamsMeetingPolicy cmdlet is used to create a meeting policy with the Identity HrMeetingPolicy. +In this example two different property values are configured: AutoAdmittedUsers is set to Everyone and AllowMeetNow is set to False. +All other policy properties will use the default values. + +## PARAMETERS + +### -Identity +Specify the name of the policy being created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AIInterpreter +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the AI Interpreter related features + +Possible values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnonymousUsersToDialOut +Determines whether anonymous users are allowed to dial out to a PSTN number. Set this to TRUE to allow anonymous users to dial out. Set this to FALSE to #prohibit anonymous users from dialing out. + +> [!NOTE] +> This parameter is temporarily disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnonymousUsersToJoinMeeting + +> [!NOTE] +> The experience for users is dependent on both the value of -DisableAnonymousJoin (the old tenant-wide setting) and -AllowAnonymousUsersToJoinMeeting (the new per-organizer policy). Please check <https://learn.microsoft.com/microsoftteams/meeting-settings-in-teams> for details. + +Determines whether anonymous users can join the meetings that impacted users organize. Set this to TRUE to allow anonymous users to join a meeting. Set this to FALSE to prohibit them from joining a meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnonymousUsersToStartMeeting +Determines whether anonymous users can initiate a meeting. Set this to TRUE to allow anonymous users to initiate a meeting. Set this to FALSE to prohibit them from initiating a meeting + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnnotations +This setting will allow admins to choose which users will be able to use the Annotation feature. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAvatarsInGallery +If admins disable avatars in 2D meetings, then users cannot represent themselves as avatars in the Gallery view. This does not disable avatars in Immersive view. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBreakoutRooms +Set to true to enable Breakout Rooms, set to false to disable the Breakout Rooms functionality. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCarbonSummary + +This setting will enable Tenant Admins to enable/disable the sharing of location data necessary to provide the end of meeting carbon summary screen for either the entire tenant or for a particular user. If set to True the meeting organizer will share their location to the client of the participant to enable the calculation of distance and the resulting carbon. + +>[!NOTE] +>Location data will not be visible to the organizer or participants in this case and only carbon avoided will be shown. If set to False then organizer location data will not be shown and no carbon summary screen will be displayed to the participants. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCartCaptionsScheduling +Determines whether a user can add a URL for captions from a Communications Access Real-Time Translation (CART) captioner for providing real-time captions in meetings. + +Possible values are: + +- **EnabledUserOverride**: CART captions are available by default but you can disable them. +- **DisabledUserOverride**: If you would like users to be able to use CART captions in meetings but they are disabled by default. +- **Disabled**: If you do not want to allow CART captions in meetings. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: DisabledUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowChannelMeetingScheduling +Determines whether a user can schedule channel meetings. Set this to TRUE to allow a user to schedule channel meetings. Set this to FALSE to prohibit the user from scheduling channel meetings. Note this only restricts from scheduling and not from joining a meeting scheduled by another user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCloudRecording +Determines whether cloud recording is allowed in a user's meetings. Set this to TRUE to allow the user to be able to record meetings. Set this to FALSE to prohibit the user from recording meetings + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowDocumentCollaboration +This setting will allow admins to choose which users will be able to use the Document Collaboration feature. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedUsersForMeetingContext + +This policy controls which users should have the ability to see the meeting info details on the join screen. 'None' option should disable the feature completely. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEngagementReport +Determines whether users are allowed to download the attendee engagement report. Set this to Enabled to allow the user to download the report. Set this to Disabled to prohibit the user to download it. ForceEnabled will enable attendee report generation and prohibit meeting organizer from disabling it. + +Possible values: + +- Enabled +- Disabled +- ForceEnabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowExternalNonTrustedMeetingChat + +This field controls whether a user is allowed to chat in external meetings with users from non trusted organizations. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowExternalParticipantGiveRequestControl +Determines whether external participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit an external user from giving or requesting control in a meeting + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowImmersiveView +If admins have disabled avatars, this does not disable using avatars in Immersive view on Teams desktop or web. Additionally, it does not prevent users from joining the Teams meeting on VR headsets. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowIPAudio +Determines whether audio is enabled in a user's meetings or calls. Set this to TRUE to allow the user to share their audio. Set this to FALSE to prohibit the user from sharing their audio. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowIPVideo +Determines whether video is enabled in a user's meetings or calls. Set this to TRUE to allow the user to share their video. Set this to FALSE to prohibit the user from sharing their video + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLocalRecording +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetNow +Determines whether a user can start ad-hoc meetings in a channel. Set this to TRUE to allow a user to start ad-hoc meetings in a channel. Set this to FALSE to prohibit the user from starting ad-hoc meetings in a channel. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TRUE +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingCoach +This setting will allow admins to allow users the option of turning on Meeting Coach during meetings, which provides users with private personalized feedback on their communication and inclusivity. If set to True, then users will see and be able to click the option for turning on Meeting Coach during calls. If set to False, then users will not have the option to turn on Meeting Coach during calls. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingReactions +Set to false to disable Meeting Reactions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingRegistration +Controls if a user can create a webinar meeting. The default value is True. + +Possible values: + +- true +- false + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowNDIStreaming +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowNetworkConfigurationSettingsLookup +Determines whether network configuration setting lookups can be made by users who are not Enterprise Voice enabled. It is used to enable Network Roaming policies. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOrganizersToOverrideLobbySettings +Set this parameter to true to enable Organizers to override lobby settings. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOutlookAddIn +Determines whether a user can schedule Teams Meetings in Outlook desktop client. Set this to TRUE to allow the user to be able to schedule Teams meetings in Outlook client. Set this to FALSE to prohibit a user from scheduling Teams meeting in Outlook client + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateMeetNow +Determines whether a user can start ad-hoc meetings. Set this to TRUE to allow a user to start ad-hoc private meetings. Set this to FALSE to prohibit the user from starting ad-hoc private meetings. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TRUE +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowParticipantGiveRequestControl +Determines whether participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit the user from giving, requesting control in a meeting + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPowerPointSharing +Determines whether Powerpoint sharing is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateMeetingScheduling +Determines whether a user can schedule private meetings. Set this to TRUE to allow a user to schedule private meetings. Set this to FALSE to prohibit the user from scheduling private meetings. Note this only restricts from scheduling and not from joining a meeting scheduled by another user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPSTNUsersToBypassLobby +Determines whether a PSTN user joining the meeting is allowed or not to bypass the lobby. If you set this parameter to True, PSTN users are allowed to bypass the lobby as long as an authenticated user is joined to the meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowRecordingStorageOutsideRegion +Allow storing recording outside of region. All meeting recordings will be permanently stored in another region, and can't be migrated. For more info, see <https://aka.ms/in-region>. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowScreenContentDigitization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSharedNotes +Determines whether users are allowed to take shared notes. Set this to TRUE to allow. Set this to FALSE to prohibit + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTasksFromTranscript +This policy setting allows for the extraction of AI-Assisted Action Items/Tasks from the Meeting Transcript. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTrackingInReport +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTranscription +Determines whether real-time and/or post-meeting captions and transcriptions are allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserToJoinExternalMeeting +Possible values are: + +- Enabled +- FederatedOnly +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWatermarkCustomizationForCameraVideo +Allows the admin to grant customization permissions to a meeting organizer + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWatermarkCustomizationForScreenSharing +Allows the admin to grant customization permissions to a meeting organizer + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWatermarkForScreenSharing +This setting allows scheduling meetings with watermarking for screen sharing enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWatermarkForCameraVideo +This setting allows scheduling meetings with watermarking for video enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWhiteboard +Determines whether whiteboard is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedStreamingMediaInput +Enables the use of RTMP-In in Teams meetings. + +Possible values are: + +- \<blank\> +- RTMP + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnonymousUserAuthenticationMethod +Determines how anonymous users will be authenticated when joining a meeting. + +Possible values are: +- **OneTimePasscode**, if you would like anonymous users to be sent a one time passcode to their email when joining a meeting +- **None**, if you would like to disable authentication for anonymous users joining a meeting + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: OneTimePasscode +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AttendeeIdentityMasking +This setting will allow admins to enable or disable Masked Attendee mode in Meetings. Masked Attendee meetings will hide attendees' identifying information (e.g., name, contact information, profile photo). + +Possible Values: Enabled: Hides attendees' identifying information in meetings. Disabled: Does not allow attendees' to hide identifying information in meetings + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AudibleRecordingNotification +The setting controls whether recording notification is played to all attendees or just PSTN users. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoAdmittedUsers +Determines what types of participants will automatically be added to meetings organized by this user. +Possible values are: + +- **EveryoneInCompany**, if you would like meetings to place every external user in the lobby but allow all users in the company to join the meeting immediately. +- **EveryoneInSameAndFederatedCompany**, if you would like meetings to allow federated users to join like your company's users, but place all other external users in a lobby. +- **Everyone**, if you'd like to admit anonymous users by default. +- **OrganizerOnly**, if you would like that only meeting organizers can bypass the lobby. +- **EveryoneInCompanyExcludingGuests**, if you would like meetings to place every external and guest users in the lobby but allow all other users in the company to join the meeting immediately. +- **InvitedUsers**, if you would like that only meeting organizers and invited users can bypass the lobby. + +This setting also applies to participants joining via a PSTN device (i.e. a traditional phone). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutomaticallyStartCopilot +> [!Note] +> This feature has not been fully released yet, so the setting will have no effect.* + +This setting gives admins the ability to auto-start Copilot. + +Possible values are: + +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedAnonymousJoinClientTypes +A user can join a Teams meeting anonymously using a [Teams client](https://support.microsoft.com/office/join-a-meeting-without-a-teams-account-c6efc38f-4e03-4e79-b28f-e65a4c039508) or using a [custom application built using Azure Communication Services](https://learn.microsoft.com/azure/communication-services/concepts/join-teams-meeting). When anonymous meeting join is enabled, both types of clients may be used by default. This optional parameter can be used to block one of the client types that can be used. + +The allowed values are ACS (to block the use of Azure Communication Services clients) or Teams (to block the use of Teams clients). Both can also be specified, separated by a comma, but this is equivalent to disabling anonymous join completely. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Empty List +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CaptchaVerificationForMeetingJoin +Require a verification check for meeting join. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelRecordingDownload +Controls how channel meeting recordings are saved, permissioned, and who can download them. + +Possible values: + +Allow - Saves channel meeting recordings to a "Recordings" folder in the channel. The permissions on the recording files will be based on the Channel SharePoint permissions. This is the same as any other file uploaded for the channel. +Block - Saves channel meeting recordings to a "Recordings\View only" folder in the channel. Channel owners will have full rights to the recordings in this folder, but channel members will have read access without the ability to download. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectToMeetingControls +Allows external connections of thirdparty apps to Microsoft Teams + +Possible values are: + +Enabled +Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentSharingInExternalMeetings +This policy allows admins to determine whether the user can share content in meetings organized by external organizations. The user should have a Teams Premium license to be protected under this policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Copilot +This setting allows the admin to choose whether Copilot will be enabled with a persisted transcript or a non-persisted transcript. + +Possible values are: + +- Enabled +- EnabledWithTranscript + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: EnabledWithTranscript +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CopyRestriction +Enables a setting that controls a meeting option which allows users to disable right-click or Ctrl+C to copy, Copy link, Forward message, and Share to Outlook for meeting chat messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TRUE +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the meeting policy. +For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignatedPresenterRoleMode +Determines if users can change the default value of the _Who can present?_ setting in Meeting options in the Teams client. This policy setting affects all meetings, including Meet Now meetings. + +Possible values are: + +- EveryoneUserOverride: All meeting participants can be presenters. This is the default value. This parameter corresponds to the _Everyone_ setting in Teams. +- EveryoneInCompanyUserOverride: Authenticated users in the organization, including guest users, can be presenters. This parameter corresponds to the _People in my organization_ setting in Teams. +- EveryoneInSameAndFederatedCompanyUserOverride: Authenticated users in the organization, including guest users and users from federated organizations, can be presenters. This parameter corresponds to the _People in my organization and trusted organizations_ setting in Teams. +- OrganizerOnlyUserOverride: Only the meeting organizer can be a presenter and all meeting participants are designated as attendees. This parameter corresponds to the _Only me_ setting in Teams. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: EveryoneUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DetectSensitiveContentDuringScreenSharing +Allows the admin to enable sensitive content detection during screen share. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnrollUserOverride +Possible values are: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExplicitRecordingConsent +Set participant agreement and notification for Recording, Transcript, Copilot in Teams meetings. + +Possible Values: + +- Enabled: Explicit consent, requires participant agreement. +- Disabled: Implicit consent, does not require participant agreement. +- LegitimateInterest: Legitimate interest, less restrictive consent to meet legitimate interest without requiring explicit agreement from participants. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalMeetingJoin +Possible values are: + +- EnabledForAnyone +- EnabledForTrustedOrgs +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: EnabledForAnyone +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InfoShownInReportMode +This policy controls what kind of information get shown for the user's attendance in attendance report/dashboard. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPAudioMode +Determines whether audio can be turned on in meetings and group calls. Set this to ENABLEDOUTGOINGINCOMING to allow outgoing and incoming audio in the meeting. Set this to DISABLED to prohibit outgoing and incoming audio in the meeting. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPVideoMode +Determines whether video can be turned on in meetings and group calls. Set this to ENABLEDOUTGOINGINCOMING to allow outgoing and incoming video in the meeting. Set this to DISABLED to prohibit outgoing and incoming video in the meeting. Invalid value combination IPVideoMode: EnabledOutgoingIncoming and IPAudioMode: Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveInterpretationEnabledType +Allows meeting organizers to configure a meeting for language interpretation, selecting attendees of the meeting to become interpreters that other attendees can select and listen to the real-time translation they provide. + +Possible values are: + +DisabledUserOverride, if you would like users to be able to use interpretation in meetings but by default it is disabled. +Disabled, prevents the option to be enabled in Meeting Options. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveCaptionsEnabledType +Determines whether real-time captions are available for the user in Teams meetings. Set this to DisabledUserOverride to allow user to turn on live captions. Set this to Disabled to prohibit. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveStreamingMode +Determines whether you provide support for your users to stream their Teams meetings to large audiences through Real-Time Messaging Protocol (RTMP). + +Possible values are: + +- Disabled (default) +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LobbyChat + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Determines whether chat messages are allowed in the lobby. + +Possible values are: + +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaBitRateKb +Determines the media bit rate for audio/video/app sharing transmissions in meetings. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingChatEnabledType +Specifies if users will be able to chat in meetings. Possible values are: Disabled, Enabled, and EnabledExceptAnonymous. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingInviteLanguages +Controls how the join information in meeting invitations is displayed by enforcing a common language or enabling up to two languages to be displayed. + +> [!NOTE] +> All Teams supported languages can be specified using language codes. For more information about its delivery date, see the [roadmap (Feature ID: 81521)](https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=81521). + +The preliminary list of available languages is shown below: + +`ar-SA,az-Latn-AZ,bg-BG,ca-ES,cs-CZ,cy-GB,da-DK,de-DE,el-GR,en-GB,en-US,es-ES,es-MX,et-EE,eu-ES,fi-FI,fil-PH,fr-CA,fr-FR,gl-ES,he-IL,hi-IN,hr-HR,hu-HU,id-ID,is-IS,it-IT,ja-JP,ka-GE,kk-KZ,ko-KR,lt-LT,lv-LV,mk-MK,ms-MY,nb-NO,nl-NL,nn-NO,pl-PL,pt-BR,pt-PT,ro-RO,ru-RU,sk-SK,sl-SL,sq-AL,sr-Latn-RS,sv-SE,th-TH,tr-TR,uk-UA,vi-VN,zh-CN,zh-TW`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NewMeetingRecordingExpirationDays +Specifies the number of days before meeting recordings will expire and move to the recycle bin. Value can be from 1 to 99,999 days. + +> [!NOTE] +> You may opt to set Meeting Recordings to never expire by entering the value -1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoiseSuppressionForDialInParticipants + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Control Noises Supression Feature for PST legs joining a meeting. + +Possible Values: + +- MicrosoftDefault +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParticipantNameChange +This setting will enable Tenant Admins to turn on/off participant renaming feature. + +Possible Values: Enabled: Turns on the Participant Renaming feature. Disabled: Turns off the Particpant Renaming feature. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreferredMeetingProviderForIslandsMode +Determines the Outlook meeting add-in available to users on Islands mode. By default, this is set to TeamsAndSfb, and the users sees both the Skype for Business and Teams add-ins. Set this to Teams to remove the Skype for Business add-in and only show the Teams add-in. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TeamsAndSfb +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QnAEngagementMode +This setting enables Microsoft 365 Tenant Admins to Enable or Disable the Questions and Answers experience (Q+A). When Enabled, Organizers can turn on Q+A for their meetings. When Disabled, Organizers cannot turn on Q+A in their meetings. The setting is enforced when a meeting is created or is updated by Organizers. Attendees can use Q+A in meetings where it was previously added. Organizers can remove Q+A for those meetings through Teams and Outlook Meeting Options. Possible values: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordingStorageMode +This parameter can take two possible values: + +- Stream +- OneDriveForBusiness + +> [!Note] +> The change of storing Teams meeting recordings from Classic Stream to OneDrive and SharePoint (ODSP) has been completed as of August 30th, 2021. All recordings are now stored in ODSP. This change overrides the RecordingStorageMode parameter, and modifying the setting in PowerShell no longer has any impact. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoomAttributeUserOverride +Possible values: + +- Off +- Distinguish +- Attribute + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoomPeopleNameUserOverride +Enabling people recognition requires the tenant CsTeamsMeetingPolicy roomPeopleNameUserOverride to be "On" and roomAttributeUserOverride to be Attribute for allowing individual voice and face profiles to be used for recognition in meetings. + +> [!Note] +> In some locations, people recognition can't be used due to local laws or regulations. +Possible values: + +- On +- Off + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScreenSharingMode +Determines the mode in which a user can share a screen in calls or meetings. Set this to SingleApplication to allow the user to share an application at a given point in time. Set this to EntireScreen to allow the user to share anything on their screens. Set this to Disabled to prohibit the user from sharing their screens. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SmsNotifications +Participants can sign up for text message meeting reminders. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpeakerAttributionMode +Possible values: + +- EnabledUserOverride +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreamingAttendeeMode +Possible values are: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsCameraFarEndPTZMode +Possible values are: + +- Disabled +- AutoAcceptInTenant +- AutoAcceptAll + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsersCanAdmitFromLobby +This policy controls who can admit from the lobby. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VideoFiltersMode +Determines the background effects that a user can configure in the Teams client. Possible values are: + +- NoFilters: No filters are available. +- BlurOnly: Background blur is the only option available (requires a processor with AVX2 support, see [Hardware requirements for Microsoft Teams](https://learn.microsoft.com/microsoftteams/hardware-requirements-for-the-teams-app) for more information). +- BlurAndDefaultBackgrounds: Background blur and a list of pre-selected images are available. +- AllFilters: All filters are available, including custom images. This is the default value. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: AllFilters +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceIsolation +Determines whether you provide support for your users to enable voice isolation in Teams meeting calls. + +Possible values are: + +- Enabled (default) +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceSimulationInInterpreter + +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the voice simulation feature while being AI interpreted. + +Possible Values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForAnonymousUsers +Determines the meeting experience and watermark content of an anonymous user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForCameraVideoOpacity +Allows the transparency of watermark to be customizable. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForCameraVideoPattern +Allows the pattern design of watermark to be customizable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForScreenSharingOpacity +Allows the transparency of watermark to be customizable. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForScreenSharingPattern +Allows the pattern design of watermark to be customizable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedUsersForMeetingDetails +Controls which users should have ability to see the meeting info details on join screen. 'None' option should disable the feature completely. + +Possible Values: +- UsersAllowedToByPassTheLobby: Users who are able to bypass lobby can see the meeting info details. +- Everyone: All meeting participants can see the meeting info details. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: UsersAllowedToByPassTheLobby +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeText +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Allows users to use real time text during a meeting, allowing them to communicate by typing their messages in real time. + +Possible Values: +- Enabled: User is allowed to turn on real time text. +- Disabled: User is not allowed to turn on real time text. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhoCanRegister +Controls the attendees who can attend a webinar meeting. The default is Everyone, meaning that everyone can register. If you want to restrict registration to internal accounts, set the value to 'EveryoneInCompany'. + +Possible values: + +- Everyone +- EveryoneInCompany + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsMeetingTemplatePermissionPolicy.md b/teams/teams-ps/teams/New-CsTeamsMeetingTemplatePermissionPolicy.md new file mode 100644 index 0000000000..48a5347d44 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsMeetingTemplatePermissionPolicy.md @@ -0,0 +1,114 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +title: New-CsTeamsMeetingTemplatePermissionPolicy +author: boboPD +ms.author: pradas +online version: https://learn.microsoft.com/powershell/module/teams/New-CsTeamsMeetingTemplatePermissionPolicy +schema: 2.0.0 +--- + +# New-CsTeamsMeetingTemplatePermissionPolicy + +## SYNOPSIS +Creates a new instance of the TeamsMeetingTemplatePermissionPolicy. + +## SYNTAX + +```powershell + New-CsTeamsMeetingTemplatePermissionPolicy [-Identity] <string> [-HiddenMeetingTemplates<PSListModifier[HiddenMeetingTemplate]>] [-Description <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Creates a new instance of the policy with a name and a list of hidden meeting template IDs. The template IDs passed into the `HiddenMeetingTemplates` object must be valid existing template IDs. The current custom and first-party templates on a tenant can be fetched by [Get-CsTeamsMeetingTemplateConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingtemplateconfiguration) and [Get-CsTeamsFirstPartyMeetingTemplateConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsfirstpartymeetingtemplateconfiguration) respectively. + +## EXAMPLES + +### Example 1 - Creating a new meeting template permission policy + +Assuming there are two valid templates with IDs `firstparty_e514e598-fba6-4e1f-b8b3-138dd3bca748` and `customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056`, we will first create the `HiddenMeetingTemplate` objects. + +The next step would be to create the policy instance. +```powershell +$hiddentemplate_1 = New-CsTeamsHiddenMeetingTemplate -Id customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056 +$hiddentemplate_2 = New-CsTeamsHiddenMeetingTemplate -Id firstparty_e514e598-fba6-4e1f-b8b3-138dd3bca748 + +New-CsTeamsMeetingTemplatePermissionPolicy -Identity Test_Policy -HiddenMeetingTemplates @($hiddentemplate_1, $hiddentemplate_2) -Description "This is a test policy" +``` + +```output +Identity : Tag:Test_Policy +HiddenMeetingTemplates : {customtemplate_9ab0014a-bba4-4ad6-b816-0b42104b5056, firstparty_e514e598-fba6-4e1f-b8b3-138dd3bca748} +Description : This is a test policy +``` + +## PARAMETERS + +### -Identity + +Name of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenMeetingTemplates + +The list of meeting template IDs to hide. +The HiddenMeetingTemplate objects are created with [New-CsTeamsHiddenMeetingTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamshiddenmeetingtemplate). + +```yaml +Type: HiddenMeetingTemplate[] +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Description of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[New-CsTeamsHiddenMeetingTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamshiddenmeetingtemplate) + +[Set-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingtemplatepermissionpolicy) + +[Get-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingtemplatepermissionpolicy) + +[Remove-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingtemplatepermissionpolicy) + +[Grant-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingtemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsMessagingPolicy.md b/teams/teams-ps/teams/New-CsTeamsMessagingPolicy.md new file mode 100644 index 0000000000..f25c5317c1 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsMessagingPolicy.md @@ -0,0 +1,771 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsmessagingpolicy +applicable: Microsoft Teams +title: New-CsTeamsMessagingPolicy +schema: 2.0.0 +--- + +# New-CsTeamsMessagingPolicy + +## SYNOPSIS +The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. + +## SYNTAX + +```powershell +New-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>] + [-AllowChatWithGroup <Boolean>] + [-AllowCommunicationComplianceEndUserReporting <Boolean>] + [-AllowCustomGroupChatAvatars <Boolean>] + [-AllowExtendedWorkInfoInSearch <Boolean>] + [-AllowFluidCollaborate <Boolean>] + [-AllowFullChatPermissionUserToDeleteAnyMessage <Boolean>] + [-AllowGiphy <Boolean>] + [-AllowGiphyDisplay <Boolean>] + [-AllowGroupChatJoinLinks <Boolean>] + [-AllowImmersiveReader <Boolean>] + [-AllowMemes <Boolean>] + [-AllowOwnerDeleteMessage <Boolean>] + [-AllowPasteInternetImage <Boolean>] + [-AllowPriorityMessages <Boolean>] + [-AllowRemoveUser <Boolean>] + [-AllowSecurityEndUserReporting <Boolean>] + [-AllowSmartCompose] <Boolean>] + [-AllowSmartReply <Boolean>] + [-AllowStickers <Boolean>] + [-AllowUrlPreviews <Boolean>] + [-AllowUserChat <Boolean>] + [-AllowUserDeleteChat <Boolean>] + [-AllowUserDeleteMessage <Boolean>] + [-AllowUserEditMessage <Boolean>] + [-AllowUserTranslation <Boolean>] + [-AllowVideoMessages <Boolean>] + [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>] + [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>] + [-ChatPermissionRole <String>] + [-Confirm] + [-CreateCustomEmojis <Boolean>] + [-DeleteCustomEmojis <Boolean>] + [-Description <String>] + [-DesignerForBackgroundsAndImages <String>] + [-Force] + [-GiphyRatingType <String>] + [-InMemory] + [-InOrganizationChatControl <String>] + [-ReadReceiptsEnabledType <String>] + [-Tenant <Guid>] + [-UsersCanDeleteBotMessages <Boolean>] + [<CommonParameters>] + [-WhatIf] + ``` + +## DESCRIPTION +The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. This cmdlet creates a new Teams messaging policy. Custom policies can then be assigned to users using the Grant-CsTeamsMessagingPolicy cmdlet. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsMessagingPolicy -Identity StudentMessagingPolicy -AllowGiphy $false -AllowMemes $false +``` + +In this example two different property values are configured: AllowGiphy is set to false and AllowMemes is set to False. +All other policy properties will use the default values. + +## PARAMETERS + +### -Identity +Unique identifier for the teams messaging policy to be created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -AllowChatWithGroup + +This setting determines if users can chat with groups (Distribution, M365 and Security groups). Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCommunicationComplianceEndUserReporting + +This setting determines if users can report offensive messages to their admin for Communication Compliance. Possible Values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCustomGroupChatAvatars + +These settings enables, disables updating or fetching custom group chat avatars for the users included in the messaging policy. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowExtendedWorkInfoInSearch +This setting enables/disables showing company name and department name in search results for MTO users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowFluidCollaborate + +This field enables or disables Fluid Collaborate feature for users. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowFullChatPermissionUserToDeleteAnyMessage + +This setting determines if users with the 'Full permissions' role can delete any group or meeting chat message within their tenant. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowGiphy +Determines whether a user is allowed to access and post Giphys. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowGiphyDisplay + +Determines if Giphy images should be displayed that had been already sent or received in chat. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowGroupChatJoinLinks + +This setting determines if users in a group chat can create and share join links for other users within the organization to join that chat. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowImmersiveReader +Determines whether a user is allowed to use Immersive Reader for reading conversation messages. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMemes +Determines whether a user is allowed to access and post memes. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOwnerDeleteMessage +Determines whether owners are allowed to delete all the messages in their team. Set this to TRUE to allow. Set this to FALSE to prohibit. + +If the `-AllowUserDeleteMessage` parameter is set to FALSE, the team owner will not be able to delete their own messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPasteInternetImage + +Determines if a user is allowed to paste internet-based images in compose. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPriorityMessages +Determines whether a user is allowed to send priorities messages. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowRemoveUser +Determines whether a user is allowed to remove a user from a conversation. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSecurityEndUserReporting + +This setting determines if users can report any security concern posted in messages to their admin. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSmartCompose +Turn on this setting to let a user get text predictions for chat messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Con nombre +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSmartReply +Turn this setting on to enable suggested replies for chat messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowStickers +Determines whether a user is allowed to access and post stickers. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUrlPreviews +Use this setting to turn automatic URL previewing on or off in messages. Set this to TRUE to turn on. Set this to FALSE to turn off. +Note: [Optional Connected Experiences](https://learn.microsoft.com/deployoffice/privacy/manage-privacy-controls#policy-setting-for-optional-connected-experiences) must be also enabled for URL previews to be allowed. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserChat +Determines whether a user is allowed to chat. Set this to TRUE to allow a user to chat across private chat, group chat and in meetings. Set this to FALSE to prohibit all chat. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserDeleteChat + +Determines whether a user is allowed to chat. Set this to TRUE to allow a user to chat across private chat, group chat and in meetings. Set this to FALSE to prohibit all chat. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserDeleteMessage +Determines whether a user is allowed to delete their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserEditMessage +Determines whether a user is allowed to edit their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserTranslation +Determines whether a user is allowed to translate messages to their client languages. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowVideoMessages + +This setting determines if users can create and send video messages. Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AudioMessageEnabledType +Determines whether a user is allowed to send audio messages. Possible values are: ChatsAndChannels,ChatsOnly,Disabled. + +```yaml +Type: AudioMessageEnabledTypeEnum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelsInChatListEnabledType +On mobile devices, enable to display favorite channels above recent chats. + +Possible values are: DisabledUserOverride,EnabledUserOverride. + +```yaml +Type: ChannelsInChatListEnabledTypeEnum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChatPermissionRole +Determines the Supervised Chat role of the user. Set this to Full to allow the user to supervise chats. Supervisors have the ability to initiate chats with and invite any user within the environment. Set this to Limited to allow the user to initiate conversations with Full and Limited permissioned users, but not Restricted. Set this to Restricted to block chat creation with anyone other than Full permissioned users. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Restricted +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CreateCustomEmojis +This setting enables the creation of custom emojis and reactions within an organization for the specified policy users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeleteCustomEmojis +These settings enable and disable the editing and deletion of custom emojis and reactions for the users included in the messaging policy. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Allows you to provide a description of your policy to note the purpose of creating it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignerForBackgroundsAndImages + +This setting determines whether a user is allowed to create custom AI-powered backgrounds and images with MS Designer. + +Possible values are: Enabled, Disabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GiphyRatingType +Determines the Giphy content restrictions applicable to a user. Set this to STRICT, MODERATE or NORESTRICTION. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InOrganizationChatControl + +This setting determines if chat regulation for internal communication in the tenant is allowed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadReceiptsEnabledType + +Use this setting to specify whether read receipts are user controlled, enabled for everyone, or disabled. Set this to UserPreference, Everyone or None. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsersCanDeleteBotMessages + +Determines whether a user is allowed to delete messages sent by bots. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Set-CsTeamsMessagingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmessagingpolicy) + +[Get-CsTeamsMessagingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmessagingpolicy) + +[Grant-CsTeamsMessagingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmessagingpolicy) + +[Remove-CsTeamsMessagingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmessagingpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsMobilityPolicy.md b/teams/teams-ps/teams/New-CsTeamsMobilityPolicy.md new file mode 100644 index 0000000000..8bd31ac80b --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsMobilityPolicy.md @@ -0,0 +1,175 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsmobilitypolicy +applicable: Microsoft Teams +title: New-CsTeamsMobilityPolicy +schema: 2.0.0 +manager: ritikag +ms.reviewer: ritikag +--- + +# New-CsTeamsMobilityPolicy + +## SYNOPSIS +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +## SYNTAX + +``` +New-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Description <String>] [-IPVideoMobileMode <String>] + [-IPAudioMobileMode <String>] [-Identity] <XdsIdentity>] [-MobileDialerPreference <String>] [-InMemory] [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +The New-CsTeamsMobilityPolicy cmdlet lets an Admin create a custom teams mobility policy to assign to particular sets of users. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsMobilityPolicy -Identity SalesMobilityPolicy -IPAudioMobileMode "WifiOnly" +``` + +The command shown in Example 1 uses the New-CsTeamsMobilityPolicy cmdlet to create a new Teams Mobility Policy with the Identity SalesMobilityPolicy and IPAudioMobileMode equal to WifiOnly. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppress all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPAudioMobileMode +When set to WifiOnly, prohibits the user from making and receiving calls or joining meetings using VoIP calls on the mobile device while on a cellular data connection. Possible values are: WifiOnly, AllNetworks. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPVideoMobileMode +When set to WifiOnly, prohibits the user from making and receiving video calls or enabling video in meetings using VoIP calls on the mobile device while on a cellular data connection. Possible values are: WifiOnly, AllNetworks. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy that you are creating. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MobileDialerPreference +Determines the mobile dialer preference, possible values are: Teams, Native, UserOverride. +For more information, see [Manage user incoming calling policies](https://learn.microsoft.com/microsoftteams/operator-connect-mobile-configure#manage-user-incoming-calling-policies). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsNetworkRoamingPolicy.md b/teams/teams-ps/teams/New-CsTeamsNetworkRoamingPolicy.md new file mode 100644 index 0000000000..54b53972d8 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsNetworkRoamingPolicy.md @@ -0,0 +1,127 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsnetworkroamingpolicy +applicable: Microsoft Teams +title: New-CsTeamsNetworkRoamingPolicy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: +manager: mreddy +schema: 2.0.0 +--- + +# New-CsTeamsNetworkRoamingPolicy + +## SYNOPSIS + +New-CsTeamsNetworkRoamingPolicy allows IT Admins to create policies for Network Roaming and Bandwidth Control experiences in Microsoft Teams. + +## SYNTAX + +``` +New-CsTeamsNetworkRoamingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] [-AllowIPVideo <Boolean>] [-MediaBitRateKb <Integer>] [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Creates new Teams Network Roaming Policies configured for use in your organization. + +The TeamsNetworkRoamingPolicy cmdlets enable administrators to provide specific settings from the TeamsMeetingPolicy to be rendered dynamically based upon the location of the Teams client. The TeamsNetworkRoamingPolicy cannot be granted to a user but instead can be assigned to a network site. The settings from the TeamsMeetingPolicy included are AllowIPVideo and MediaBitRateKb. When a Teams client is connected to a network site where a CsTeamRoamingPolicy is assigned, these two settings from the TeamsRoamingPolicy will be used instead of the settings from the TeamsMeetingPolicy. + +More on the impact of bit rate setting on bandwidth can be found [here](https://learn.microsoft.com/microsoftteams/prepare-network). + +To enable the network roaming policy for users who are not Enterprise Voice enabled, you must also enable the AllowNetworkConfigurationSettingsLookup setting in TeamsMeetingPolicy. This setting is off by default. See Set-TeamsMeetingPolicy for more information on how to enable AllowNetworkConfigurationSettingsLookup for users who are not Enterprise Voice enabled. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsNetworkRoamingPolicy -Identity "RedmondRoaming" -AllowIPVideo $true -MediaBitRateKb 2000 -Description "Redmond campus roaming policy" +``` + +The command shown in Example 1 creates a new teams network roaming policy with Identity "RedmondRoaming" with IP Video feature enabled, and the maximum media bit rate is capped at 2000 Kbps. + +### Example 2 +```powershell +PS C:\> New-CsTeamsNetworkRoamingPolicy -Identity "RemoteRoaming" +``` + +The command shown in Example 2 creates a new teams network roaming policy with Identity "RemoteRoaming" with IP Video feature enabled, and the maximum media bit rate is capped at 50000 Kbps by default. + +## PARAMETERS + +### -Identity +Unique identifier of the policy to be created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowIPVideo +Determines whether video is enabled in a user's meetings or calls. +Set this to TRUE to allow the user to share their video. Set this to FALSE to prohibit the user from sharing their video. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaBitRateKb +Determines the media bit rate for audio/video/app sharing transmissions in meetings. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 50000 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Description of the new policy to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/skype/skype-ps/skype/New-CsTeamsPinnedApp.md b/teams/teams-ps/teams/New-CsTeamsPinnedApp.md similarity index 78% rename from skype/skype-ps/skype/New-CsTeamsPinnedApp.md rename to teams/teams-ps/teams/New-CsTeamsPinnedApp.md index 5239586cb8..6c96bf3b11 100644 --- a/skype/skype-ps/skype/New-CsTeamsPinnedApp.md +++ b/teams/teams-ps/teams/New-CsTeamsPinnedApp.md @@ -1,22 +1,24 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml Module Name: tmp_1cmcv0jw.3l2 +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamspinnedapp +title: New-CsTeamsPinnedApp schema: 2.0.0 -ms.reviewer: +ms.reviewer: manager: bulenteg -ms.author: tomkau author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney --- # New-CsTeamsPinnedApp ## SYNOPSIS +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies - -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. ## SYNTAX @@ -33,11 +35,11 @@ New-CsTeamsPinnedApp [-Tenant <System.Guid>] -Parent <String> -Id <String> -Orde ``` ## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. ## EXAMPLES @@ -198,14 +200,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/New-CsTeamsRecordingRollOutPolicy.md b/teams/teams-ps/teams/New-CsTeamsRecordingRollOutPolicy.md new file mode 100644 index 0000000000..be3f26d1a2 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsRecordingRollOutPolicy.md @@ -0,0 +1,137 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsrecordingrolloutpolicy +schema: 2.0.0 +applicable: Microsoft Teams +title: New-CsTeamsRecordingRollOutPolicy +manager: yujin1 +author: ronwa +ms.author: ronwa +--- + +# New-CsTeamsRecordingRollOutPolicy + +## SYNOPSIS + +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. + +## SYNTAX + +``` +New-CsTeamsRecordingRollOutPolicy [-MeetingRecordingOwnership <String>] [-Identity] <String> [-Force] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. This policy would be deprecated over time as this is only to allow IT admins to phase the roll out of this breaking change. + +The New-CsTeamsRecordingRollOutPolicy cmdlet allows administrators to define new CsTeamsRecordingRollOutPolicy that can be assigned to particular users to control Teams features related to meetings. + +This command is available from Teams powershell module 6.1.1-preview and above. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsRecordingRollOutPolicy -Identity OrganizerPolicy -MeetingRecordingOwnership MeetingOrganizer +``` + +The command shown in Example 1 uses the New-CsTeamsRecordingRollOutPolicy cmdlet to create a new TeamsRecordingRollOutPolicy with the Identity OrganizerPolicy. +This policy will set MeetingRecordingOwnership to MeetingOrganizer. Recordings for this policy group's users as organizer would get saved to organizers' own OneDrive. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy being created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingRecordingOwnership +Specifies where the meeting recording get stored. Possible values are: +- MeetingOrganizer +- RecordingInitiator + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsRecordingRollOutPolicy.Cmdlets.TeamsRecordingRollOutPolicy + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsRoomVideoTeleConferencingPolicy.md b/teams/teams-ps/teams/New-CsTeamsRoomVideoTeleConferencingPolicy.md new file mode 100644 index 0000000000..ad5c601ece --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsRoomVideoTeleConferencingPolicy.md @@ -0,0 +1,225 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsroomvideoteleconferencingpolicy +title: New-CsTeamsRoomVideoTeleConferencingPolicy +schema: 2.0.0 +--- + +# New-CsTeamsRoomVideoTeleConferencingPolicy + +## SYNOPSIS + +Creates a new TeamsRoomVideoTeleConferencingPolicy. + +## SYNTAX + +```powershell +New-CsTeamsRoomVideoTeleConferencingPolicy [-Identity] <String> [-AreaCode <String>] [-Description <String>] + [-Enabled <Boolean>] [-PlaceExternalCalls <String>] [-PlaceInternalCalls <String>] + [-ReceiveExternalCalls <String>] [-ReceiveInternalCalls <String>] [-MsftInternalProcessingMode <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Room Video Teleconferencing Policy enables administrators to configure and manage video teleconferencing behavior for Microsoft Teams Rooms (meeting room devices). + +## PARAMETERS + +### -AreaCode + +GUID provided by the CVI partner that the customer signed the agreement with. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide additional text to accompany the policy. For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled + +The policy can exist for the tenant but it can be enabled or disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier for the policy to be modified. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PlaceExternalCalls + +The IT admin can configure that their Teams rooms are enabled to place external calls or not, meaning calls from the Microsoft Teams Rooms to Video teleconferencing devices that are outside their own tenant. +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PlaceInternalCalls + +The IT admin can configure that their Teams rooms are enabled to place internal calls or not. Meaning calls from the Microsoft Teams Rooms to Video teleconferencing devices that are within their own tenant. +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveExternalCalls + +The IT admin can configure that their Teams rooms are enabled to receive external calls or not, meaning calls from Video teleconferencing devices that are outside their own tenant. +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveInternalCalls + +The IT admin can configure that their Teams rooms are enabled to receive external calls or not. Meaning calls from Video Teleconferencing devices from their own tenant. +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsSharedCallingRoutingPolicy.md b/teams/teams-ps/teams/New-CsTeamsSharedCallingRoutingPolicy.md new file mode 100644 index 0000000000..1b61b77f9d --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsSharedCallingRoutingPolicy.md @@ -0,0 +1,201 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamssharedcallingroutingpolicy +applicable: Microsoft Teams +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +title: New-CsTeamsSharedCallingRoutingPolicy +schema: 2.0.0 +--- + +# New-CsTeamsSharedCallingRoutingPolicy + +## SYNOPSIS +Use the New-CsTeamsSharedCallingRoutingPolicy cmdlet to configure a shared calling routing policy. + +## SYNTAX + +### Identity (Default) +``` +New-CsTeamsSharedCallingRoutingPolicy [-Identity] <string> [-EmergencyNumbers <PSListModifier[string]>] + [-ResourceAccount <string>] [-Description <string>] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams shared calling routing policy configures the caller ID for normal outbound PSTN and emergency calls made by users enabled for Shared Calling using this policy instance. + +The caller ID for normal outbound PSTN calls is the phone number assigned to the resource account specified in the policy instance. Typically this is the organization's main auto attendant phone number. Callbacks will go to the auto attendant and the PSTN caller can use the auto attendant to be transferred to the shared calling user. + +When a shared calling user makes an emergency call, the emergency services need to be able to make a direct callback to the user who placed the emergency call. One of the defined emergency numbers is used for this purpose as caller ID for the emergency call. It will be reserved for the next 60 minutes and any inbound call to that number will directly ring the shared calling user who made the emergency call. If no emergency numbers are defined, the phone number of the resource account is used as caller ID. If no free emergency numbers are available, the first number in the list is reused. + +The emergency call will contain the location of the shared calling user. The location will be either the dynamic emergency location obtained by the Teams client or if that is not available the static location assigned to the phone number of the resource account used in the shared calling policy instance. + +## EXAMPLES + +### Example 1 +``` +$ra = Get-CsOnlineUser -Identity ra1@contoso.com +$PhoneNumber=Get-CsPhoneNumberAssignment -AssignedPstnTargetId ra1@contoso.com +$CivicAddress = Get-CsOnlineLisCivicAddress -City Seattle +Set-CsPhoneNumberAssignment -LocationId $CivicAddress.DefaultLocationId -PhoneNumber $PhoneNumber.TelephoneNumber +New-CsTeamsSharedCallingRoutingPolicy -Identity Seattle -ResourceAccount $ra.Identity -EmergencyNumbers @{add='+14255556677','+14255554321'} -Description 'Seattle' +``` +The command shown in Example 1 gets the identity and phone number assigned to the Teams resource account ra1@contoso.com, sets the location of the phone number to be the Seattle location, and creates a new Shared Calling policy called Seattle that is using the Teams resource account ra1@contoso.com and the emergency numbers +14255556677 and +14255554321. + +## PARAMETERS + +### -Identity +Unique identifier of the Teams shared calling routing policy to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description of the new policy instance. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyNumbers +An array of phone numbers used as caller ID on emergency calls. + +The emergency numbers must be routable for inbound PSTN calls, and for Calling Plan and Operator Connect phone numbers, must be available within the organization. + +The emergency numbers specified must all be of the same phone number type and country as the phone number assigned to the specified resource account. If the resource account has a Calling Plan service number assigned, the emergency numbers need to be Calling Plan subscriber numbers. + +The emergency numbers must be unique and can't be reused in other shared calling policy instances. The emergency numbers can't be assigned to any user or resource account. + +If no emergency numbers are configured, the phone number of the resource account is used as the Caller ID for the emergency call. + +```yaml +Type: System.Management.Automation.PSListModifier[String] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResourceAccount +The Identity of the resource account. Can only be specified using the Identity or ObjectId of the resource account. + +The phone number assigned to the resource account must: +- Have the same phone number type and country as the emergency numbers configured in this policy instance. +- Must have an emergency location assigned. You can use the Teams PowerShell Module [Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) and the -LocationId parameter to set the location. +- If the resource account is using a Calling Plan service number, you must have a Pay-As-You-Go Calling Plan, and assign it to the resource account. In addition, you need to assign a Communications credits license to the resource account and fund it to support outbound shared calling calls via the Pay-As-You-Go Calling Plan. + +The same resource account can be used in multiple shared calling policy instances. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +In some Calling Plan markets, you are not allowed to set the location on service numbers. In this instance, kindly contact the [Telephone Number Services service desk](https://learn.microsoft.com/microsoftteams/phone-reference/manage-numbers/contact-tns-service-desk). + +If you are attempting to use a resource account with an Operator Connect phone number assigned, you should confirm support for Shared Calling with your operator. + +Shared Calling is not supported for Calling Plan service phone numbers in Romania, the Czech Republic, Hungary, Singapore, New Zealand, Australia, and Japan. A limited number of existing Calling Plan service phone numbers in other countries are also not supported for Shared Calling. For such service phone numbers, please contact the [Telephone Number Services service desk](https://learn.microsoft.com/microsoftteams/phone-reference/manage-numbers/contact-tns-service-desk). + +This cmdlet was introduced in Teams PowerShell Module 5.5.0. + +## RELATED LINKS +[Set-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamssharedcallingroutingpolicy) + +[Grant-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamssharedcallingroutingpolicy) + +[Remove-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamssharedcallingroutingpolicy) + +[Get-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamssharedcallingroutingpolicy) + +[Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) diff --git a/teams/teams-ps/teams/New-CsTeamsShiftsConnection.md b/teams/teams-ps/teams/New-CsTeamsShiftsConnection.md new file mode 100644 index 0000000000..f09cf35e77 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsShiftsConnection.md @@ -0,0 +1,367 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: New-CsTeamsShiftsConnection +author: serdarsoysal +ms.author: serdars +manager: valk +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnection +schema: 2.0.0 +--- + +# New-CsTeamsShiftsConnection + +## SYNOPSIS +This cmdlet creates a new workforce management (WFM) connection. + +## SYNTAX + +### New (Default) +```powershell +New-CsTeamsShiftsConnection -Body <IWfmConnectionRequest> [-Authorization <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### NewExpanded +```powershell +New-CsTeamsShiftsConnection -ConnectorId <string> -ConnectorSpecificSettings <IWfmConnectionRequestConnectorSpecificSettings> -Name <string> -State <string> [-Authorization <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a Shifts WFM connection. It allows the admin to set up the environment for creating connection instances. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> $result = New-CsTeamsShiftsConnection ` + -connectorId "6A51B888-FF44-4FEA-82E1-839401E00000" ` + -name "Cmdlet test connection" ` + -connectorSpecificSettings (New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificBlueYonderSettingsRequest ` + -Property @{ + adminApiUrl = "https://contoso.com/retail/data/wfmadmin/api/v1-beta2" + siteManagerUrl = "https://contoso.com/retail/data/wfmsm/api/v1-beta2" + essApiUrl = "https://contoso.com/retail/data/wfmess/api/v1-beta1" + retailWebApiUrl = "https://contoso.com/retail/data/retailwebapi/api/v1" + cookieAuthUrl = "https://contoso.com/retail/data/login" + federatedAuthUrl = "https://contoso.com/retail/data/login" + LoginUserName = "PlaceholderForUsername" + LoginPwd = "PlaceholderForPassword" + }) ` + -state "Active" +PS C:\> $result | Format-List +``` + +```output +{ +ConnectorId : 6A51B888-FF44-4FEA-82E1-839401E00000 +ConnectorSpecificSettingAdminApiUrl : https://www.contoso.com/retail/data/wfmadmin/api/v1-beta2 +ConnectorSpecificSettingApiUrl : +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : +ConnectorSpecificSettingCookieAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingEssApiUrl : https://www.contoso.com/retail/data/wfmess/api/v1-beta2 +ConnectorSpecificSettingFederatedAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingRetailWebApiUrl : https://www.contoso.com/retail/data/retailwebapi/api/v1 +ConnectorSpecificSettingSiteManagerUrl : https://www.contoso.com/retail/data/wfmsm/api/v1-beta2 +ConnectorSpecificSettingSsoUrl : +CreatedDateTime : 24/03/2023 04:58:23 +Etag : "5b00dd1b-0000-0400-0000-641d2df00000" +Id : 4dae9db0-0841-412c-8d6b-f5684bfebdd7 +LastModifiedDateTime : 24/03/2023 04:58:23 +Name : Cmdlet test connection +State : Active +TenantId : 3FDCAAF2-863A-4520-97BA-DFA211595876 +} +``` + +Returns the object of the created connection. + +In case of an error, we can capture the error response as follows: + +* Hold the cmdlet output in a variable: `$result=<CMDLET>` + +* To get the entire error message in Json: `$result.ToJsonString()` + +* To get the error object and object details: `$result, $result.Detail` + +### Example 2 + +```powershell +PS C:\> $result = New-CsTeamsShiftsConnection ` + -connectorId "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0" ` + -name "Cmdlet test connection" ` + -connectorSpecificSettings (New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificUkgDimensionsSettingsRequest ` + -Property @{ + apiUrl = "https://www.contoso.com/api" + ssoUrl = "https://www.contoso.com/sso" + appKey = "PlaceholderForAppKey" + clientId = "Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W" + clientSecret = "PlaceholderForClientSecret" + LoginUserName = "PlaceholderForUsername" + LoginPwd = "PlaceholderForPassword" + }) ` + -state "Active" +PS C:\> $result | Format-List +``` + +```output +ConnectorId : 95BF2848-2DDA-4425-B0EE-D62AEED4C0A0 +ConnectorSpecificSettingAdminApiUrl : +ConnectorSpecificSettingApiUrl : https://www.contoso.com/api +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W +ConnectorSpecificSettingCookieAuthUrl : +ConnectorSpecificSettingEssApiUrl : +ConnectorSpecificSettingFederatedAuthUrl : +ConnectorSpecificSettingRetailWebApiUrl : +ConnectorSpecificSettingSiteManagerUrl : +ConnectorSpecificSettingSsoUrl : https://www.contoso.com/sso +CreatedDateTime : 06/04/2023 11:05:39 +Etag : "3100fd6e-0000-0400-0000-642ea7840000" +Id : a2d1b091-5140-4dd2-987a-98a8b5338744 +LastModifiedDateTime : 06/04/2023 11:05:39 +Name : Cmdlet test connection +State : Active +TenantId : 3FDCAAF2-863A-4520-97BA-DFA211595876 +``` + +## PARAMETERS + +### -Body + +The request body. + +```yaml +Type: IConnectorInstanceRequest +Parameter Sets: New +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break +Wait for .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorId +The WFM connector ID. + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The connection name. + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorSpecificSettings +The connection name. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificSettingsRequest +Parameter Sets: NewExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The state of the connection. Valid values are "Active" and "Disabled". A third value, "ErrorDisabled", signifies an error in the connection. + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Authorization +Used to provide the necessary credentials for authenticating and authorizing the connection to the workforce management (WFM) system. This parameter ensures that the connection has the appropriate permissions to access and manage the data within the WFM system. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IWfmConnectionRequest + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IWfmConnectionResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection) + +[Set-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnection) + +[Update-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/update-csteamsshiftsconnection) + +[Get-CsTeamsShiftsConnectionConnector](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionconnector) + +[Test-CsTeamsShiftsConnectionValidate](https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate) diff --git a/teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md b/teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md new file mode 100644 index 0000000000..0dcfcf6db0 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md @@ -0,0 +1,100 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: New-CsTeamsShiftsConnectionBatchTeamMap +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectionbatchteammap +schema: 2.0.0 +--- + +# New-CsTeamsShiftsConnectionBatchTeamMap + +## SYNOPSIS + +This cmdlet submits an operation connecting multiple Microsoft Teams teams and Workforce management (WFM) teams. + +## SYNTAX + +``` +New-CsTeamsShiftsConnectionBatchTeamMap -ConnectorInstanceId <string> -TeamMapping <TeamMap[]> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet connects multiple Microsoft Teams teams and WFM teams to allow for synchronization of shifts related data. It initiates an asynchronous job to map the WFM teams to the Microsoft Teams teams. You can check the operation status by running [Get-CsTeamsShiftsConnectionOperation](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionoperation). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> $map1 = @{ +teamId = 'eddc3b94-21d5-4ef0-a76a-2e4d6f4a50be' +wfmTeamId = 1000553 +timeZone = "America/Los_Angeles" +} + +$map2 = @{ +teamId = '1d8f6288-0459-4c53-8e98-9de7b781844a' +wfmTeamId = 1000555 +timeZone = "America/Los_Angeles" +} + +New-CsTeamsShiftsConnectionBatchTeamMap -ConnectorInstanceId WCI-2afeb8ec-a0f6-4580-8f1e-85fd4a343e01 -TeamMapping @($map1, $map2) +``` +```output +CreatedDateTime LastActionDateTime OperationId Status +--------------- ------------------ ----------- ------ +12/6/2021 7:28:51 PM 12/6/2021 7:28:51 PM c79131b7-9ecb-484b-a8df-2639c7c1e5f0 NotStarted +``` + +Sends 2 team mappings: one maps the Teams team with ID `eddc3b94-21d5-4ef0-a76a-2e4d6f4a50be` and WFM team with ID `1000553` and the other maps the Teams team with ID `1d8f6288-0459-4c53-8e98-9de7b781844a` and WFM team with ID `1000555` in the instance with ID `WCI-2afeb8ec-a0f6-4580-8f1e-85fd4a343e01`. + +## PARAMETERS + +### -ConnectorInstanceId + +The connection instance ID used to map teams. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamMapping + +The Teams mapping object list. + +```yaml +Type: TeamMap[] +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +Please check the example section for the format of TeamMap. + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionOperation](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionoperation) diff --git a/teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md b/teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md new file mode 100644 index 0000000000..9570c08ad4 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md @@ -0,0 +1,463 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: New-CsTeamsShiftsConnectionInstance +author: leonardospina +ms.author: lespina +manager: valk +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectioninstance +schema: 2.0.0 +--- + +# New-CsTeamsShiftsConnectionInstance + +## SYNOPSIS +This cmdlet creates a Shifts connection instance. + +## SYNTAX + +### New (Default) +``` +New-CsTeamsShiftsConnectionInstance -Body <IConnectorInstanceRequest> [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### NewExpanded +``` +New-CsTeamsShiftsConnectionInstance [-ConnectionId <string>] [-ConnectorAdminEmail <string[]>] [-DesignatedActorId <string>] [-Name <string>] [-State <string>] [-SyncFrequencyInMin <int>] [-SyncScenarioOfferShiftRequest <string>][-SyncScenarioOpenShift <string>] [-SyncScenarioOpenShiftRequest <string>] [-SyncScenarioShift <string>] [-SyncScenarioSwapRequest <string>] [-SyncScenarioTimeCard <string>] [-SyncScenarioTimeOff <string>][-SyncScenarioTimeOffRequest <string>] [-SyncScenarioUserShiftPreference <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a Shifts connection instance. It allows the admin to set up the environment for further connection settings. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> $result = New-CsTeamsShiftsConnectionInstance ` +-connectionId "79964000-286a-4216-ac60-c795a426d61a" ` +-name "Cmdlet test instance" ` +-connectorAdminEmail @("admin@contoso.com", "superadmin@contoso.com") ` +-designatedActorId "93f85765-47db-412d-8f06-9844718762a1" ` +-State "Active" ` +-syncFrequencyInMin "10" ` +-SyncScenarioOfferShiftRequest "FromWfmToShifts" ` +-SyncScenarioOpenShift "FromWfmToShifts" ` +-SyncScenarioOpenShiftRequest "FromWfmToShifts" ` +-SyncScenarioShift "FromWfmToShifts" ` +-SyncScenarioSwapRequest "FromWfmToShifts" ` +-SyncScenarioTimeCard "FromWfmToShifts" ` +-SyncScenarioTimeOff "FromWfmToShifts" ` +-SyncScenarioTimeOffRequest "FromWfmToShifts" ` +-SyncScenarioUserShiftPreference "Disabled" +PS C:\> $result.ToJsonString() +``` + +```output +{ + "syncScenarios": { + "offerShiftRequest": "FromWfmToShifts", + "openShift": "FromWfmToShifts", + "openShiftRequest": "FromWfmToShifts", + "shift": "FromWfmToShifts", + "swapRequest": "FromWfmToShifts", + "timeCard": "FromWfmToShifts", + "timeOff": "FromWfmToShifts", + "timeOffRequest": "FromWfmToShifts", + "userShiftPreferences": "Disabled" + }, + "id": "WCI-eba2865f-6cac-46f9-8733-e0631a4536e1", + "tenantId": "dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a", + "connectionId": "79964000-286a-4216-ac60-c795a426d61a", + "connectorAdminEmails": [ "admin@contoso.com", "superadmin@contoso.com" ], + "connectorId": "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0", + "designatedActorId": "ec1a4edb-1a5f-4b2d-b2a4-37aab6ebd231", + "name": "Cmdlet test instance", + "syncFrequencyInMin": 10, + "workforceIntegrationId": "WFI_6b225907-b476-4d40-9773-08b86db7b11b", + "etag": "\"4f005d22-0000-0400-0000-642ff64a0000\"", + "createdDateTime": "2023-04-07T10:54:01.8170000Z", + "lastModifiedDateTime": "2023-04-07T10:54:01.8170000Z", + "state": "Active" +} +``` + +Returns the object of created connector instance. + +In case of an error, we can capture the error response as follows: + +* Hold the cmdlet output in a variable: `$result=<CMDLET>` + +* To get the entire error message in Json: `$result.ToJsonString()` + +* To get the error object and object details: `$result, $result.Detail` + +## PARAMETERS + +### -Body + +The request body + +```yaml +Type: IConnectorInstanceRequest +Parameter Sets: New +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorAdminEmail +Gets or sets the list of connector admin email addresses. + +```yaml +Type: String[] +Parameter Sets: NewExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId +Gets or sets the WFM connection ID for the new instance. This can be retrieved by running [Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection). + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignatedActorId +Gets or sets the designated actor ID that App acts as for Shifts Graph Api calls. + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOfferShiftRequest +The sync state for the offer shift request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOpenShift +The sync state for the open shift scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOpenShiftRequest +The sync state for the open shift request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioShift +The sync state for the shift scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioSwapRequest +The sync state for the swap shift request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeCard +The sync state for the time card scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeOff +The sync state for the time off scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeOffRequest +The sync state for the time off request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioUserShiftPreference +The sync state for the user shift preferences scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The connector instance name. + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The state of the connection instance. Valid values are "Active" and "Disabled". A third value, "ErrorDisabled", signifies an error in the connection instance. + +```yaml +Type: String +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncFrequencyInMin +The sync frequency in minutes. + +```yaml +Type: Int32 +Parameter Sets: NewExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConnectorInstanceRequest + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConnectorInstanceResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) + +[Set-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnectioninstance) + +[Remove-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectioninstance) + +[Get-CsTeamsShiftsConnectionConnector](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionconnector) + +[Test-CsTeamsShiftsConnectionValidate](https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate) diff --git a/teams/teams-ps/teams/New-CsTeamsShiftsPolicy.md b/teams/teams-ps/teams/New-CsTeamsShiftsPolicy.md new file mode 100644 index 0000000000..57a7c3e428 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsShiftsPolicy.md @@ -0,0 +1,228 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-teamsshiftspolicy +title: New-CsTeamsShiftsPolicy +schema: 2.0.0 +--- + +# New-CsTeamsShiftsPolicy + +## SYNOPSIS + +This cmdlet allows you to create a new TeamsShiftPolicy instance and set it's properties. + +## SYNTAX + +```powershell +New-CsTeamsShiftsPolicy [-ShiftNoticeFrequency <String>] [-ShiftNoticeMessageType <String>] + [-ShiftNoticeMessageCustom <String>] [-AccessType <String>] [-AccessGracePeriodMinutes <Int64>] + [-EnableScheduleOwnerPermissions <Boolean>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet allows you to create a TeamsShiftPolicy instance. Use this to also set the policy name, schedule owner permissions, and Teams off shift warning message-specific settings (ShiftNoticeMessageType, ShiftNoticeMessageCustom, ShiftNoticeFrequency, AccessGracePeriodMinutes). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsShiftsPolicy -Identity OffShiftAccessMessage1Always +``` + +Creates a new instance of TeamsShiftsPolicy called OffShiftAccessMessage1Always and applies the default values to its settings. + +### Example 2 +```powershell +PS C:\> New-CsTeamsShiftsPolicy -Identity OffShiftAccessMessage1Always -ShiftNoticeFrequency always -ShiftNoticeMessageType Message1 -AccessType UnrestrictedAccess_TeamsApp -AccessGracePeriodMinutes 5 -EnableScheduleOwnerPermissions $false +``` + +Creates a new instance of TeamsShiftsPolicy called OffShiftAccessMessage1Always and applies the provided values to its settings. + +## PARAMETERS + +### -Identity +Policy instance name. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessType +Indicates the Teams access type granted to the user. Today, only unrestricted access to Teams app is supported. +Use 'UnrestrictedAccess_TeamsApp' as the value for this setting, or is set by default. +For Teams Off Shift Access Control, the option to show the user a blocking dialog message is supported. Once the user accepts this message, it is audit logged and the user has usual access to Teams. Set other off shift warning message-specific settings to configure off shift access controls for the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: UnrestrictedAccess_TeamsApp +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftNoticeFrequency +Frequency of warning dialog displayed when user opens Teams. Select one of Always, ShowOnceOnChange, Never. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftNoticeMessageType +The warning message is shown in the blocking dialog when a user access Teams off shift hours. Select one of 7 Microsoft provided messages, a default message or a custom message. +'Message1' - Your employer does not authorize or approve of the use of its network, applications, systems, or tools by non-exempt or hourly employees during their non-working hours. By accepting, you acknowledge that your use of Teams while off shift is not authorized and you will not be compensated. +'Message2' - Accessing this app outside working hours is voluntary. You won't be compensated for time spent on Teams. Refer to your employer's guidelines on using this app outside working hours. By accepting, you acknowledge that you understand the statement above. +'Message3' - You won't be compensated for time using Teams. By accepting, you acknowledge that you understand the statement above. +'Message4' - You're not authorized to use Teams while off shift. By accepting, you acknowledge your use of Teams is against your employer's policy. +'Message5' - Access to Teams is turned off during non-working hours. You will be able to access the app when your next shift starts. +'Message6' - Your employer does not authorize or approve of the use of its network, applications, systems, or tools by non-exempt or hourly employees during their non-working hours. Access to corporate resources are only allowed during approved working hours and should be recorded as hours worked in your employer's timekeeping system. +'Message7' - Your employer has turned off access to Teams during non-working hours. Refer to your employer's guidelines on using this app outside working hours. +'DefaultMessage' - You aren't authorized to use Microsoft Teams during non-working hours and will only be compensated for using it during approved working hours. +'CustomMessage' + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: DefaultMessage +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftNoticeMessageCustom +Provide a custom message. Must set ShiftNoticeMessageType to 'CustomMessage' to enforce this. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessGracePeriodMinutes +Indicates the grace period time in minutes between when the first shift starts or last shift ends and when access is blocked. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableScheduleOwnerPermissions +Indicates whether a user can manage a Shifts schedule as a team member. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftspolicy) + +[Set-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftspolicy) + +[Remove-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftspolicy) + +[Grant-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsshiftspolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliance.md b/teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliance.md new file mode 100644 index 0000000000..e4ca073509 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliance.md @@ -0,0 +1,160 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamssurvivablebranchappliance +title: New-CsTeamsSurvivableBranchAppliance +schema: 2.0.0 +--- + +# New-CsTeamsSurvivableBranchAppliance + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +### Identity (Default) + +```powershell +New-CsTeamsSurvivableBranchAppliance [-Identity] <String> [-Description <String>] [-Site <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey + +```powershell +New-CsTeamsSurvivableBranchAppliance [-Description <String>] [-Site <String>] + [-MsftInternalProcessingMode <String>] -Fqdn <String> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Free format text. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Fqdn + +The FQDN of the SBA. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the SBA. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Site + +The TenantNetworkSite where the SBA is located + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliancePolicy.md b/teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliancePolicy.md new file mode 100644 index 0000000000..4fe55cb48c --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliancePolicy.md @@ -0,0 +1,119 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamssurvivablebranchappliancepolicy +title: New-CsTeamsSurvivableBranchAppliancePolicy +schema: 2.0.0 +--- + +# New-CsTeamsSurvivableBranchAppliancePolicy + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +```powershell +New-CsTeamsSurvivableBranchAppliancePolicy [-Identity] <String> [-BranchApplianceFqdns <Object>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## PARAMETERS + +### -BranchApplianceFqdns + +The FQDN of the SBA(s) in the site. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The unique identifier. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsTemplatePermissionPolicy.md b/teams/teams-ps/teams/New-CsTeamsTemplatePermissionPolicy.md new file mode 100644 index 0000000000..88462d4a72 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsTemplatePermissionPolicy.md @@ -0,0 +1,163 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy +title: New-CsTeamsTemplatePermissionPolicy +author: yishuaihuang4 +ms.author: yishuaihuang +ms.reviewer: +manager: weiliu2 +schema: 2.0.0 +--- + +# New-CsTeamsTemplatePermissionPolicy + +## SYNOPSIS +Creates a new instance of the TeamsTemplatePermissionPolicy. + +## SYNTAX + +``` +New-CsTeamsTemplatePermissionPolicy + [-HiddenTemplates <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.HiddenTemplate]>] + [-Description <String>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Creates a new instance of the policy with a name and a list of hidden Teams template IDs. The template IDs passed into the `HiddenTemplates` object must be valid existing template IDs. The current custom and first-party templates on a tenant can be fetched by [Get-CsTeamTemplateList](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist). + +## EXAMPLES + +### Example 1 + +Assuming there are two valid templates with IDs `com.microsoft.teams.template.ManageAProject` and `com.microsoft.teams.template.ManageAnEvent`, we will first create the `HiddenTemplate` objects. + +The next step would be to create the policy instance. +```powershell +PS >$manageEventTemplate = New-CsTeamsHiddenTemplate -Id com.microsoft.teams.template.ManageAnEvent +PS >$manageProjectTemplate = New-CsTeamsHiddenTemplate -Id com.microsoft.teams.template.ManageAProject +PS >$HiddenList = @($manageProjectTemplate, $manageEventTemplate) +PS >New-CsTeamsTemplatePermissionPolicy -Identity Foobar -HiddenTemplates $HiddenList +``` + +```output +Identity HiddenTemplates Description +-------- --------------- ----------- +Tag:Foobar {com.microsoft.teams.template.ManageAProject, com.microsoft.teams.template.ManageAnEvent} +``` + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Description of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenTemplates +The list of Teams template IDs to hide. +The HiddenTemplate objects are created with [New-CsTeamsHiddenTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamshiddentemplate). + +```yaml +Type: System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.HiddenTemplate] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsTemplatePermissionPolicy.Cmdlets.TeamsTemplatePermissionPolicy + +## NOTES + +## RELATED LINKS +[Get-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamstemplatepermissionpolicy) + +[Remove-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamstemplatepermissionpolicy) + +[Set-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsTranslationRule.md b/teams/teams-ps/teams/New-CsTeamsTranslationRule.md new file mode 100644 index 0000000000..e760bec361 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsTranslationRule.md @@ -0,0 +1,199 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamstranslationrule +applicable: Microsoft Teams +title: New-CsTeamsTranslationRule +schema: 2.0.0 +manager: nmurav +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsTeamsTranslationRule + +## SYNOPSIS +Cmdlet to create a new telephone number manipulation rule. + +## SYNTAX + +### Identity (Default) +``` +New-CsTeamsTranslationRule [-Identity] <string> [-Description <string>] [-Pattern <string>] [-Translation <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsTeamsTranslationRule -Name <string> [-Description <string>] [-Pattern <string>] [-Translation <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You can use this cmdlet to create a new number manipulation rule. The rule can be used, for example, in the settings of your SBC (Set-CSOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System + +## EXAMPLES + +### Example 1 +```powershell +New-CsTeamsTranslationRule -Identity 'AddPlus1' -Pattern '^(\d{10})$' -Translation '+1$1' +``` + +This example creates a rule that adds +1 to any ten digits number. For example, 2065555555 will be translated to +1206555555 + +### Example 2 +```powershell +New-CsTeamsTranslationRule -Identity 'StripPlus1' -Pattern '^\+1(\d{10})$' -Translation '$1' +``` + +This example creates a rule that strips +1 from any E.164 eleven digits number. For example, +12065555555 will be translated to 206555555 + +### Example 3 +```powershell +New-CsTeamsTranslationRule -Identity 'AddE164SeattleAreaCode' -Pattern '^(\d{4})$' -Translation '+120655$1' +``` + +This example creates a rule that adds +1206555 to any four digits number (converts it to E.164number). For example, 5555 will be translated to +1206555555 + +### Example 4 +```powershell +New-CsTeamsTranslationRule -Identity 'AddSeattleAreaCode' -Pattern '^(\d{4})$' -Translation '425555$1' +``` + +This example creates a rule that adds 425555 to any four digits number (converts to non-E.164 ten digits number). For example, 5555 will be translated to 4255555555 + +### Example 5 +```powershell +New-CsTeamsTranslationRule -Identity 'StripE164SeattleAreaCode' -Pattern '^\+1206555(\d{4})$' -Translation '$1' +``` + +This example creates a rule that strips +1206555 from any E.164 ten digits number. For example, +12065555555 will be translated to 5555 + +### Example 6 +```powershell +New-CsTeamsTranslationRule -Identity 'GenerateFullNumber' -Pattern '^\+1206555(\d{4})$' -Translation '+1206555$1;ext=$1' +``` + +This example creates a rule that adds the last four digits of a phone number starting with +1206555 as the extension. For example, +12065551234 will be translated to +12065551234;ext=1234. + +## PARAMETERS + +### -Identity +The Identifier of the rule. This parameter is required and later used to assign the rule to the Inbound or Outbound Trunk Normalization policy. + +```yaml +Type: String +Parameter Sets: (Identity) +Aliases: +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +A friendly description of the normalization rule. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern +A regular expression that caller or callee number must match in order for this rule to be applied. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Translation +The regular expression pattern that will be applied to the number to convert it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The name of the rule. + +```yaml +Type: String +Parameter Sets: (ParentAndRelativeKey) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Test-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/test-csteamstranslationrule) + +[Get-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/get-csteamstranslationrule) + +[Set-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/set-csteamstranslationrule) + +[Remove-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/remove-csteamstranslationrule) diff --git a/teams/teams-ps/teams/New-CsTeamsUnassignedNumberTreatment.md b/teams/teams-ps/teams/New-CsTeamsUnassignedNumberTreatment.md new file mode 100644 index 0000000000..cf47048628 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsUnassignedNumberTreatment.md @@ -0,0 +1,201 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsunassignednumbertreatment +applicable: Microsoft Teams +title: New-CsTeamsUnassignedNumberTreatment +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# New-CsTeamsUnassignedNumberTreatment + +## SYNOPSIS +Creates a new treatment for how calls to an unassigned number range should be routed. The call can be routed to a user, an application or to an announcement service where a custom message will be played to the caller. + +## SYNTAX + +### Identity (Default) +``` +New-CsTeamsUnassignedNumberTreatment [-Identity] <string> [-Description <string>] [-Pattern <string>] [-Target <string>] + [-TargetType <string>] [-TreatmentPriority <int>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsTeamsUnassignedNumberTreatment -TreatmentId <string> [-Description <string>] [-Pattern <string>] [-Target <string>] + [-TargetType <string>] [-TreatmentPriority <int>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a treatment for how calls to an unassigned number range should be routed. + +## EXAMPLES + +### Example 1 +```powershell +$RAObjectId = (Get-CsOnlineApplicationInstance -Identity aa@contoso.com).ObjectId +New-CsTeamsUnassignedNumberTreatment -Identity MainAA -Pattern "^\+15552223333$" -TargetType ResourceAccount -Target $RAObjectId -TreatmentPriority 1 +``` +This example creates a treatment that will route all calls to the number +1 (555) 222-3333 to the resource account aa@contoso.com. +That resource account is associated with an Auto Attendant (not part of the example). + +### Example 2 +```powershell +$Content = Get-Content "C:\Media\MainAnnoucement.wav" -Encoding byte -ReadCount 0 +$AudioFile = Import-CsOnlineAudioFile -FileName "MainAnnouncement.wav" -Content $Content +$Fid=[System.Guid]::Parse($audioFile.Id) +New-CsTeamsUnassignedNumberTreatment -Identity TR1 -Pattern "^\+1555333\d{4}$" -TargetType Announcement -Target $Fid.Guid -TreatmentPriority 2 +``` +This example creates a treatment that will route all calls to unassigned numbers in the range +1 (555) 333-0000 to +1 (555) 333-9999 to the announcement service, +where the audio file MainAnnouncement.wav will be played to the caller. + +### Example 3 +```powershell +$UserObjectId = (Get-CsOnlineUser -Identity user@contoso.com).Identity +New-CsTeamsUnassignedNumberTreatment -Identity TR2 -Pattern "^\+15552224444$" -TargetType User -Target $UserObjectId -TreatmentPriority 3 +``` +This example creates a treatment that will route all calls to the number +1 (555) 222-4444 to the user user@contoso.com. + +## PARAMETERS + +### -Description +Free format description of this treatment. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Id of the treatment. + +```yaml +Type: System.String +Parameter Sets: (Identity) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern +A regular expression that the called number must match in order for the treatment to take effect. It is best practice to start the regular expression with the hat character and end it with the dollar character. +You can use various regular expression test sites on the Internet to validate the expression. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Target +The identity of the destination the call should be routed to. Depending on the TargetType it should either be the ObjectId of the user or application instance/resource account or the AudioFileId of the uploaded audio file. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetType +The type of target used for the treatment. Allowed values are User, ResourceAccount and Announcement. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TreatmentId +The identity of the treatment. + +```yaml +Type: System.String +Parameter Sets: (ParentAndRelativeKey) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TreatmentPriority +The priority of the treatment. Used to distinguish identical patterns. The lower the priority the higher preference. The priority needs to be unique. + +```yaml +Type: System.Integer +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PS module 2.5.1 or later. + +The parameters Identity and TreatmentId are mutually exclusive. + +To route calls to unassigned Microsoft Calling Plan subscriber numbers, your tenant needs to have available Communications Credits. + +To route calls to unassigned Microsoft Calling Plan service numbers, your tenant needs to have at least one Microsoft Teams Phone Resource Account license. + +Both inbound calls to Microsoft Teams and outbound calls from Microsoft Teams will have the called number checked against the unassigned number range. + +If a specified pattern/range contains phone numbers that are assigned to a user or resource account in the tenant, calls to these phone numbers will be routed to +the appropriate target and not routed to the specified unassigned number treatment. There are no other checks of the numbers in the range. If the range contains +a valid external phone number, outbound calls from Microsoft Teams to that phone number will be routed according to the treatment. + +## RELATED LINKS +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) + +[Get-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/get-csteamsunassignednumbertreatment) + +[Remove-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/remove-csteamsunassignednumbertreatment) + +[Set-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/set-csteamsunassignednumbertreatment) + +[Test-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/test-csteamsunassignednumbertreatment) diff --git a/teams/teams-ps/teams/New-CsTeamsUpdateManagementPolicy.md b/teams/teams-ps/teams/New-CsTeamsUpdateManagementPolicy.md new file mode 100644 index 0000000000..d439835fe4 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsUpdateManagementPolicy.md @@ -0,0 +1,315 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsupdatemanagementpolicy +applicable: Microsoft Teams +title: New-CsTeamsUpdateManagementPolicy +schema: 2.0.0 +author: vargasj-ms +ms.author: vargasj +manager: gnamun +--- + +# New-CsTeamsUpdateManagementPolicy + +## SYNOPSIS + +Use this cmdlet to create Teams Update Management policy. + +## SYNTAX + +```powershell +New-CsTeamsUpdateManagementPolicy + [-DisabledInProductMessages <System.Management.Automation.PSListModifier`1[System.String]>] + [-Description <String>] [-AllowManagedUpdates <Boolean>] [-AllowPreview <Boolean>] [-UpdateDayOfWeek <Int64>] + [-UpdateTime <String>] [-UpdateTimeOfDay <DateTime>] [-AllowPublicPreview <String>] + [-AllowPrivatePreview <AllowPrivatePreview>] [-UseNewTeamsClient <String>] + [-BlockLegacyAuthorization <Boolean>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Update Management Policy allows admins to specify if a given user is enabled to preview features in Teams. + +This cmdlet can be used to create a new policy to manage the visibility of some Teams in-product messages. Executing the cmdlet will suppress the corresponding category of messages from appearing for the specified user group. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsUpdateManagementPolicy -Identity "Campaign Policy" -DisabledInProductMessages @("91382d07-8b89-444c-bbcb-cfe43133af33") +``` + +Disable the in-product messages with the category "What's New". + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisabledInProductMessages +List of IDs of the categories of the in-product messages that will be disabled. You can choose one of the categories from this table: + +| ID | Campaign Category | +| -- | -- | +| 91382d07-8b89-444c-bbcb-cfe43133af33| What's New | +| edf2633e-9827-44de-b34c-8b8b9717e84c | Conferences | + +```yaml +Type: System.Management.Automation.PSListModifier`1[System.String] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowManagedUpdates + +Enables/Disables managed updates for the user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPreview + +Indicates whether all feature flags are switched on or off. Can be set only when AllowManagedUpdates is set to True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivatePreview + +This setting will allow admins to allow users in their tenant to opt in to Private Preview. + If it is Disabled, then users will not be able to opt in and the ring switcher UI will be hidden in the Desktop Client. + If it is Enabled, then users will be able to opt in and the ring switcher UI will be available in the Desktop Client. + If it is Forced, then users will be switched to Private Preview. + +```yaml +Type: AllowPrivatePreview +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPublicPreview + +This setting will allow admins to allow users in their tenant to opt in to Public Preview. + If it is Disabled, then users will not be able to opt in and the ring switcher UI will be hidden in the Desktop Client. + If it is Enabled, then users will be able to opt in and the ring switcher UI will be available in the Desktop Client. + If it is FollowOfficePreview, then users will not be able to opt in and instead follow their Office channel, and be switched to Public Preview if their Office channel is CC (Preview). The ring switcher UI will be hidden in the Desktop Client. This is not applicable to the Web Client. + If it is Forced, then users will be switched to Public Preview. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthorization + +This setting will force Teams clients to enforce session revocation for core Messaging and Calling/Meeting scenarios. + If turned ON, session revocation will be enforced for calls, chats and meetings for opted-in users. + If turned OFF, session revocation will not be enforced for calls, chats and meetings for opted-in users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateDayOfWeek + + Machine local day. 0-6(Sun-Sat) Can be set only when AllowManagedUpdates is set to True. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateTime + +Machine local time in HH:MM format. Can be set only when AllowManagedUpdates is set to True. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateTimeOfDay + +Machine local time. Can be set only when AllowManagedUpdates is set to True + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseNewTeamsClient + +This setting will enable admins to show or hide which users see the Teams preview toggle on the current Teams client. + If it is AdminDisabled, then users will not be able to see the Teams preview toggle in the Desktop Client. + If it is UserChoice, then users will be able to see the Teams preview toggle in the Desktop Client. + If it is MicrosoftChoice, then Microsoft will configure/ manage whether user sees or does not see this feature if the admin has set nothing. + If it is NewTeamsAsDefault, then New Teams will be default for users, and they will be able to switch back to Classic Teams via the toggle in the Desktop Client. + If it is NewTeamsOnly, then New Teams will be the only Teams client installed for users. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppress all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A unique identifier. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsUpdateManagementPolicy.Cmdlets.TeamsUpdateManagementPolicy + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsVdiPolicy.md b/teams/teams-ps/teams/New-CsTeamsVdiPolicy.md new file mode 100644 index 0000000000..a8a03debbe --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsVdiPolicy.md @@ -0,0 +1,165 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsvdipolicy +title: New-CsTeamsVdiPolicy +schema: 2.0.0 +--- + +# New-CsTeamsVdiPolicy + +## SYNOPSIS +The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +## SYNTAX + +```powershell +New-CsTeamsVdiPolicy [-DisableCallsAndMeetings <Boolean>] [-DisableAudioVideoInCallsAndMeetings <Boolean>] + [-VDI2Optimization <String>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +The New-CsTeamsVdiPolicy cmdlet allows administrators to define new Vdi policies that can be assigned to particular users to control Teams features related to meetings on a VDI environment. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsVdiPolicy -Identity RestrictedUserPolicy -VDI2Optimization "Disabled" +``` + +The command shown in Example 1 uses the New-CsTeamsVdiPolicy cmdlet to create a new Vdi policy with the Identity RestrictedUserPolicy. This policy will use all the default values for a vdi policy except one: VDI2Optimization; in this example, users with this policy will not be able to be VDI 2.0 optimized. + +### Example 2 +```powershell +PS C:\> New-CsTeamsVdiPolicy -Identity OnlyOptimizedPolicy -DisableAudioVideoInCallsAndMeetings $True -DisableCallsAndMeetings $True +``` + +In Example 2, the New-CsTeamsVdiPolicy cmdlet is used to create a Vdi policy with the Identity OnlyOptimizedPolicy. In this example two different property values are configured: DisableAudioVideoInCallsAndMeetings is set to True and DisableCallsAndMeetings is set to True. All other policy properties will use the default values. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableAudioVideoInCallsAndMeetings +Determines whether a user on a non-optimized Vdi environment can hold person-to-person audio and video calls. Set this to TRUE to disallow a non-optimized user to hold person-to-person audio and video calls. Set this to FALSE to allow a non-optimized user to hold person-to-person audio and video calls. A user can still join a meeting and share screen from chat and join a meeting and share a screen and move their audio to a phone. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableCallsAndMeetings +Determines whether a user on a non-optimized Vdi environment can make all types of calls. Set this to TRUE to disallow a non-optimized user to make calls, join meetings, and screen share from chat. Set this to FALSE to allow a non-optimized user to make calls, join meetings, and screen share from chat. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy being created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VDI2Optimization +Determines whether a user can be VDI 2.0 optimized. +* Enabled - allow a user to be VDI 2.0 optimized. +* Disabled - disallow a user to be VDI 2.0 optimized. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### TeamsVdiPolicy.Cmdlets.TeamsVdiPolicy + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsTeamsVirtualAppointmentsPolicy.md b/teams/teams-ps/teams/New-CsTeamsVirtualAppointmentsPolicy.md new file mode 100644 index 0000000000..e231df2c8c --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsVirtualAppointmentsPolicy.md @@ -0,0 +1,149 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsvirtualappointmentspolicy +title: New-CsTeamsVirtualAppointmentsPolicy +schema: 2.0.0 +ms.author: erocha +author: emmanuelrocha001 +manager: sonaggarwal +--- + +# New-CsTeamsVirtualAppointmentsPolicy + +## SYNOPSIS +This cmdlet is used to create a new instance of the TeamsVirtualAppointmentsPolicy. + +## SYNTAX + +``` +New-CsTeamsVirtualAppointmentsPolicy [-EnableSmsNotifications <Boolean>] [-Identity] <String> [-Force] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Creates a new instance of the TeamsVirtualAppointmentsPolicy. This policy can be used to tailor the virtual appointment template meeting experience. The parameter `EnableSmsNotifications` allows you to specify whether your users can choose to send SMS text notifications to external guests in meetings that they schedule using the virtual appointment meeting template. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsVirtualAppointmentsPolicy -Identity sms-enabled +``` +```output +Identity EnableSmsNotifications +-------- ---------------------- +Tag:sms-enabled True +``` +Creates a new policy instance with the identity enable-sms. `EnableSmsNotifications` will default to true if it is not specified. + +### Example 2 +```powershell +PS C:\> New-CsTeamsVirtualAppointmentsPolicy -Identity disable-sms -EnableSmsNotifications $false +``` +```output +Identity EnableSmsNotifications +-------- ---------------------- +Tag:sms-enabled False +``` +Creates a new policy instance with the identity sms-disabled. `EnableSmsNotifications` is set to the value specified in the command. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSmsNotifications +This property specifies whether your users can choose to send SMS text notifications to external guests in meetings that they schedule using a virtual appointment template meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### TeamsVirtualAppointmentsPolicy.Cmdlets.TeamsVirtualAppointmentsPolicy + +## NOTES + +## RELATED LINKS +[Get-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvirtualappointmentspolicy) + +[Remove-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvirtualappointmentspolicy) + +[Set-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvirtualappointmentspolicy) + +[Grant-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvirtualappointmentspolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsVoiceApplicationsPolicy.md b/teams/teams-ps/teams/New-CsTeamsVoiceApplicationsPolicy.md new file mode 100644 index 0000000000..fd60490292 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsVoiceApplicationsPolicy.md @@ -0,0 +1,770 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsvoiceapplicationspolicy +title: New-CsTeamsVoiceApplicationsPolicy +schema: 2.0.0 +ROBOTS: NOINDEX +--- + +# New-CsTeamsVoiceApplicationsPolicy + +## SYNOPSIS + +Creates a new Teams voice applications policy. `TeamsVoiceApplications` policy governs what permissions the supervisors/users have over auto attendants and call queues. + +## SYNTAX + +```powershell +New-CsTeamsVoiceApplicationsPolicy [-Identity] <String> + [-AllowAutoAttendantBusinessHoursGreetingChange <Boolean>] + [-AllowAutoAttendantAfterHoursGreetingChange <Boolean>] + [-AllowAutoAttendantHolidayGreetingChange <Boolean>] + [-AllowAutoAttendantBusinessHoursChange <Boolean>] + [-AllowAutoAttendantHolidaysChange <Boolean>] + [-AllowAutoAttendantTimeZoneChange <Boolean>] + [-AllowAutoAttendantLanguageChange <Boolean>] + [-AllowAutoAttendantBusinessHoursRoutingChange <Boolean>] + [-AllowAutoAttendantAfterHoursRoutingChange <Boolean>] + [-AllowAutoAttendantHolidayRoutingChange <Boolean>] + + [-AllowCallQueueWelcomeGreetingChange <Boolean>] + [-AllowCallQueueMusicOnHoldChange <Boolean>] + [-AllowCallQueueOverflowSharedVoicemailGreetingChange <Boolean>] + [-AllowCallQueueTimeoutSharedVoicemailGreetingChange <Boolean>] + [-AllowCallQueueNoAgentSharedVoicemailGreetingChange <bool>] + [-AllowCallQueueLanguageChange <Boolean>] + [-AllowCallQueueMembershipChange <Boolean>] + [-AllowCallQueueConferenceModeChange <Boolean>] + [-AllowCallQueueRoutingMethodChange <Boolean>] + [-AllowCallQueuePresenceBasedRoutingChange <Boolean>] + [-AllowCallQueueOptOutChange <Boolean>] + [-AllowCallQueueOverflowRoutingChange <Boolean>] + [-AllowCallQueueTimeoutRoutingChange <Boolean>] + [-AllowCallQueueNoAgentsRoutingChange <Boolean>] + [-AllowCallQueueAgentOptChange <Boolean>] + + [-CallQueueAgentMonitorMode <Disabled | Monitor | Whisper | Barge | Takeover>] + [-CallQueueAgentMonitorNotificationMode <Disabled | Agent>] + + [-RealTimeAutoAttendantMetricsPermission <string>] + [-RealTimeCallQueueMetricsPermission <string>] + [-RealTimeAgentMetricsPermission <string>] + + [-HistoricalAutoAttendantMetricsPermission <string>] + [-HistoricalCallQueueMetricsPermission <string>] + [-HistoricalAgentMetricsPermission <string>] + + [-Description <String>] + [-WhatIf] + [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +`TeamsVoiceApplicationsPolicy` is used for **Supervisor Delegated Administration** which allows admins in the organization to permit certain users to make changes to auto attendant and call queue configurations. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +New-CsTeamsVoiceApplicationsPolicy -Identity SDA-Allow-CQ-Moh -AllowCallQueueMusicOnHoldChange $true +``` + +The command shown in Example 1 creates a new per-user Teams voice applications policy with the Identity `SDA-Allow-Moh`. This policy allows delegated administrators to change the music on hold information. + +### EXAMPLE 2 + +```powershell +New-CsTeamsVoiceApplicationsPolicy -Identity SDA-Allow-AA-After-Hour -AllowAutoAttendantAfterHoursGreetingChange $true +``` + +The command shown in Example 2 creates a new per-user Teams voice applications policy with the Identity `SDA-Allow-AA-After-Hour`. This policy allows delegated administrators to change after-hours greetings for auto attendants. + +## PARAMETERS + +### -Identity + +Unique identifier assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantBusinessHoursGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's business hours greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's business hours greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantAfterHoursGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's after-hours greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's after-hours greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantHolidayGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's holiday greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's holiday greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantBusinessHoursChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's business hours schedule. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's business hours schedule. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantHolidaysChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's holiday schedules. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's holiday schedules. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantTimeZoneChange + +_This feature is not currently available to authorized users._ + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's time zone. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's time zone. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantLanguageChange + +_This feature is not currently available to authorized users._ + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's language. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's language. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantBusinessHoursRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's business hours call flow. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's business hours call flow. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantAfterHoursRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's after-hours call flow. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's after-hours call flow. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantHolidayRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's holiday call flows. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's holiday call flows. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueWelcomeGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's welcome greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's welcome greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueMusicOnHoldChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's music on hold information. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's music on hold. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueOverflowSharedVoicemailGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's overflow shared voicemail greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's overflow shared voicemail greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueTimeoutSharedVoicemailGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's timeout shared voicemail greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's timeout shared voicemail greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueNoAgentSharedVoicemailGreetingChange + +_This option is not currently available in Queues app._ + +When set to `True`, users affected by the policy will be allowed to change the call queue's no agent shared voicemail greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's no agent shared voicemail greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueLanguageChange + +_This feature is not currently available to authorized users._ + +When set to `True`, users affected by the policy will be allowed to change the call queue's language. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's language. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueMembershipChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's users. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueConferenceModeChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's conference mode. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's conference mode. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueRoutingMethodChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's routing method. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's routing method. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueuePresenceBasedRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's presence-based routing option. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's presence-based routing option. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueOptOutChange + +When set to `True`, users affected by the policy will be allowed to change the call queue opt-out setting that allows agents to opt out of receiving calls. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue opt-out setting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueOverflowRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's overflow handling properties. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's overflow handling properties. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueTimeoutRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's timeout handling properties. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's timeout handling properties. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueNoAgentsRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's no-agent handling properties. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's no-agent handling properties. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueAgentOptChange + +When set to `True`, users affected by the policy will be allowed to change an agent's opt-in status in the call queue. When set to `False` (the default value), users affected by the policy won't be allowed to change an agent's opt-in status in the call queue. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallQueueAgentMonitorMode + +PARAMVALUE: Disabled | Monitor | Whisper | Barge | Takeover + +When set to `Disabled` (the default value), users affected by the policy won't be allowed to monitor call sessions. + +When set to `Monitor`, users affected by the policy will be allowed to monitor and listen to call sessions. + +When set to `Whisper`, users affected by the policy will be allowed to monitor call sessions and whisper to an agent in the call. + +When set to `Barge`, users affected by the policy will be allowed to monitor call sessions, whisper to an agent in the call, or join the call session. + +When set to `Takeover`, users affected by the policy will be allowed to monitor call sessions, whisper to an agent in the call, join the call session, or take over the call from an agent. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallQueueAgentMonitorNotificationMode + +PARAMVALUE: Disabled | Agent + +When set to `Disabled` (the default value), users affected by the policy won't be allowed to monitor agents during call sessions. + +When set to `Agent`, users affected by the policy will be allowed to monitor agents during call sessions. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeAutoAttendantMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive real-time metrics for auto attendants. + +When set to `AuthorizedOnly`, users affected by the policy will receive real-time metrics for auto attendants they are authorized for. + +> [!IMPORTANT] +> The `All` option is no longer supported. The parameter will be accepted and saved, however, any user assigned a policy with *RealTimeAutoAttendantMetricsPermission* set to `All` won't be able to access real-time metrics. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeCallQueueMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive real-time metrics for call queues. + +When set to `AuthorizedOnly`, users affected by the policy will receive real-time metrics for call queues they are authorized for. + +> [!IMPORTANT] +> The `All` option is no longer supported. The parameter will be accepted and saved, however, any user assigned a policy with *RealTimeCallQueueMetricsPermission* set to `All` won't be able to access real-time metrics. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeAgentMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive real-time metrics for agents. + +When set to `AuthorizedOnly`, users affected by the policy will receive real-time metrics for agents who are members in the call queues they are authorized for. + +> [!IMPORTANT] +> The `All` option is no longer supported. The parameter will be accepted and saved, however, any user assigned a policy with *RealTimeAgentMetricsPermission* set to `All` won't be able to access real-time metrics. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HistoricalAutoAttendantMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive historical metrics for auto attendants. + +When set to `AuthorizedOnly`, users affected by the policy will receive historical metrics for auto attendants they are authorized for. + +When set to `All`, users affected by the policy will receive historical metrics for all auto attendants in the organization. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HistoricalCallQueueMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive historical metrics for call queues. + +When set to `AuthorizedOnly`, users affected by the policy will receive historical metrics for call queues they are authorized for. + +When set to `All`, users affected by the policy will receive historical metrics for all call queues in the organization. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HistoricalAgentMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive historical metrics for agents. + +When set to `AuthorizedOnly`, users affected by the policy will receive historical metrics for agents who are members in the call queues they are authorized for. + +When set to `All`, users affected by the policy will receive historical metrics for all agents in all call queues in the organization. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvoiceapplicationspolicy) + +[Grant-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvoiceapplicationspolicy) + +[Remove-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvoiceapplicationspolicy) + +[Set-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvoiceapplicationspolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsWorkLoadPolicy.md b/teams/teams-ps/teams/New-CsTeamsWorkLoadPolicy.md new file mode 100644 index 0000000000..e2f6188c48 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsWorkLoadPolicy.md @@ -0,0 +1,239 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsworkloadpolicy +title: New-CsTeamsWorkLoadPolicy +schema: 2.0.0 +--- + +# New-CsTeamsWorkLoadPolicy + +## SYNOPSIS + +This cmdlet creates a Teams Workload Policy instance for the tenant. + +## SYNTAX + +```powershell +New-CsTeamsWorkLoadPolicy [-Identity] <String> [-AllowCalling <Boolean>] [-AllowCallingPinned <Boolean>] + [-AllowMeeting <Boolean>] [-AllowMeetingPinned <Boolean>] [-AllowMessaging <Boolean>] + [-AllowMessagingPinned <Boolean>] [-Description <String>] [-MsftInternalProcessingMode <String>] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The TeamsWorkLoadPolicy determines the workloads like meeting, messaging, calling that are enabled and/or pinned for the user. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> New-CsTeamsWorkLoadPolicy -Identity Test +``` + +Creates a new Teams Workload Policy with the specified identity of "Test". + +## PARAMETERS + +### -AllowCalling + +Determines if calling workload is enabled in the Teams App. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallingPinned + +Determines if calling workload is pinned to the teams navigation bar. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeeting + +Determines if meetings workload is enabled in the Teams App. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingPinned + +Determines if meetings workload is pinned to the teams navigation bar. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMessaging + +Determines if messaging workload is enabled in the Teams App. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMessagingPinned + +Determines if messaging workload is pinned to the teams navigation bar. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide explanatory text about the Teams Workload policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the Teams Workload Policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Microsoft Internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Remove-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworkloadpolicy) + +[Get-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworkloadpolicy) + +[Set-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworkloadpolicy) + +[Grant-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworkloadpolicy) diff --git a/teams/teams-ps/teams/New-CsTeamsWorkLocationDetectionPolicy.md b/teams/teams-ps/teams/New-CsTeamsWorkLocationDetectionPolicy.md new file mode 100644 index 0000000000..c99f3955de --- /dev/null +++ b/teams/teams-ps/teams/New-CsTeamsWorkLocationDetectionPolicy.md @@ -0,0 +1,151 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csteamsworklocationdetectionpolicy +title: New-CsTeamsWorkLocationDetectionPolicy +schema: 2.0.0 +ms.author: arkozlov +manager: prashibadkur +author: artemiykozlov +--- + +# New-CsTeamsWorkLocationDetectionPolicy + +## SYNOPSIS +This cmdlet is used to create a new instance of the TeamsWorkLocationDetectionPolicy. The end user experience utilizing this policy has rolled out to the general public. You can see updates at [Microsoft 365 Roadmap | Microsoft 365](https://www.microsoft.com/en-us/microsoft-365/roadmap?msockid=287ab43847c06d0008cca05b46076c18&filters=&searchterms=automatically%2Cset%2Cwork%2Clocation%22https://www.microsoft.com/en-us/microsoft-365/roadmap?msockid=287ab43847c06d0008cca05b46076c18&filters=&searchterms=automatically%2cset%2cwork%2clocation%22) and to learn more on how to enable the end user experience, please see [Setting up Bookable Desks in Microsoft Teams - Microsoft Teams | Microsoft Learn.](https://learn.microsoft.com/microsoftteams/rooms/bookable-desks) + +## SYNTAX + +``` +New-CsTeamsWorkLocationDetectionPolicy [-EnableWorkLocationDetection <Boolean>] [-Identity] <String> [-Force] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Creates a new instance of the TeamsWorkLocationDetectionPolicy. This policy can be used to tailor the work location detection experience. The parameter `EnableWorkLocationDetection` allows your organization to collect the work location of users when they connect, interact, or are detected near your organization's networks and devices. It also captures the geographic location information users share from personal and mobile devices. +This gives users the ability to consent to the use of this location data to set their current work location.Microsoft collects this information to provide users with a consistent location-based experience and to improve the hybrid work experience in Microsoft 365 according to the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTeamsWorkLocationDetectionPolicy -Identity wld-policy -EnableWorkLocationDetection $true +``` +```output +Identity EnableWorkLocationDetection +-------- ---------------------- +Tag:wld-policy True +``` +Creates a new policy instance with the identity wld-enabled. `EnableWorkLocationDetection` is set to the value specified in the command. + +### Example 2 +```powershell +PS C:\> New-CsTeamsWorkLocationDetectionPolicy -Identity wld-policy +``` +```output +Identity EnableWorkLocationDetection +-------- ---------------------- +Tag:wld-policy False +``` +Creates a new policy instance with the identity wld-policy. `EnableWorkLocationDetection` will default to false if it is not specified. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableWorkLocationDetection +This setting allows your organization to collect the work location of users when they connect, interact, or are detected near your organization's networks and devices. It also captures the geographic location information users share from personal and mobile devices. +This gives users the ability to consent to the use of this location data to set their current work location.Microsoft collects this information to provide users with a consistent location-based experience and to improve the hybrid work experience in Microsoft 365 according to the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### TeamsWorkLocationDetectionPolicy.Cmdlets.TeamsWorkLocationDetectionPolicy + +## NOTES + +## RELATED LINKS +[Get-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworklocationdetectionpolicy) + +[Remove-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworklocationdetectionpolicy) + +[Set-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworklocationdetectionpolicy) + +[Grant-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworklocationdetectionpolicy) diff --git a/teams/teams-ps/teams/New-CsTenantDialPlan.md b/teams/teams-ps/teams/New-CsTenantDialPlan.md new file mode 100644 index 0000000000..3496d58772 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTenantDialPlan.md @@ -0,0 +1,185 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-cstenantdialplan +applicable: Microsoft Teams +title: New-CsTenantDialPlan +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsTenantDialPlan + +## SYNOPSIS +Use the `New-CsTenantDialPlan` cmdlet to create a new tenant dial plan. + +## SYNTAX + +``` +New-CsTenantDialPlan [-Identity] <string> [-Description <string>] [-NormalizationRules <Object>] + [-SimpleName <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You can use this cmdlet to create a new tenant dial plan. Tenant dial plans provide required information to let Enterprise Voice users make telephone calls. +The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. +A tenant dial plan determines such things as which normalization rules are applied. + +You can add new normalization rules to a tenant dial plan by calling the [New-CsVoiceNormalizationRule](https://learn.microsoft.com/powershell/module/teams/new-csvoicenormalizationrule) cmdlet. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +New-CsTenantDialPlan -Identity vt1tenantDialPlan9 +``` + +This example creates a tenant dial plan that has an Identity of vt1tenantDialPlan9. + +### -------------------------- Example 2 -------------------------- +``` +$nr2 = New-CsVoiceNormalizationRule -Identity Global/NR2 -Description "TestNR1" -Pattern '^(d{11})$' -Translation '+1' -InMemory +New-CsTenantDialPlan -Identity vt1tenantDialPlan91 -NormalizationRules @{Add=$nr2} +``` + +This example creates a new normalization rule and then applies that rule to a new tenant dial plan. + +## PARAMETERS + +### -Identity +The Identity parameter is a unique identifier that designates the name of the tenant dial plan. +Identity is an alphanumeric string that cannot exceed 49 characters. +Valid characters are alphabetic or numeric characters, hyphen (-) and dot (.). +The value should not begin with a (.) + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter describes the tenant dial plan - what it's for, what type of user it applies to and any other information that helps to identify the purpose of the tenant dial plan. +Maximum characters: 1040. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NormalizationRules +The NormalizationRules parameter is a list of normalization rules that are applied to this dial plan. +Although this list and these rules can be created directly by using this cmdlet, we recommend that you create the normalization rules by the [New-CsVoiceNormalizationRule](https://learn.microsoft.com/powershell/module/teams/new-csvoicenormalizationrule) cmdlet, which creates the rule and then assign it to the specified tenant dial plan using [Set-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/set-cstenantdialplan) cmdlet. + +Each time a new tenant dial plan is created, a new voice normalization rule with default settings is also created for that site, service, or per-user tenant dial plan. +By default, the Identity of the new voice normalization rule is the tenant dial plan Identity followed by a slash and then followed by the name Prefix All. +(For example, TAG:Redmond/Prefix All.) The number of normalization rules cannot exceed 50 per TenantDialPlan. + +You can create a new normalization rule by calling the [New-CsVoiceNormalizationRule](https://learn.microsoft.com/powershell/module/teams/new-csvoicenormalizationrule) cmdlet. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SimpleName +The SimpleName parameter is a display name for the tenant dial plan. +This name must be unique among all tenant dial plans. + +This string can be up to 49 characters long. +Valid characters are alphabetic or numeric characters, hyphen (-), dot (.) and parentheses (()). + +This parameter must contain a value. +However, if you don't provide a value, a default value matching the Identity of the tenant dial plan will be supplied. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +The ExternalAccessPrefix and OptimizeDeviceDialing parameters have been removed from New-CsTenantDialPlan and Set-CsTenantDialPlan cmdlet since they are no longer used. External access dialing is now handled implicitly using normalization rules of the dial plans. +The Get-CsTenantDialPlan will still show the external access prefix in the form of a normalization rule of the dial plan. + +## RELATED LINKS + +[Grant-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/grant-cstenantdialplan) + +[Get-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/get-cstenantdialplan) + +[Set-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/set-cstenantdialplan) + +[Remove-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/remove-cstenantdialplan) diff --git a/teams/teams-ps/teams/New-CsTenantNetworkRegion.md b/teams/teams-ps/teams/New-CsTenantNetworkRegion.md new file mode 100644 index 0000000000..33bb7d2c2d --- /dev/null +++ b/teams/teams-ps/teams/New-CsTenantNetworkRegion.md @@ -0,0 +1,170 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworkregion +applicable: Microsoft Teams +title: New-CsTenantNetworkRegion +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsTenantNetworkRegion + +## SYNOPSIS +As an admin, you can use the Teams PowerShell command, New-CsTenantNetworkRegion to define network regions. A network region interconnects various parts of a network across multiple geographic areas. The RegionID parameter is a logical name that represents the geography of the region and has no dependencies or restrictions. The organization's network region is used for Location-Based Routing. + +## SYNTAX + +### Identity (Default) +``` +New-CsTenantNetworkRegion [-Identity] <string> [-BypassID <string>] [-CentralSite <string>] + [-Description <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsTenantNetworkRegion -NetworkRegionID <string> [-BypassID <string>] [-CentralSite <string>] +[-Description <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. A network region contains a collection of network sites. For example, if your organization has many sites located in Redmond, then you may choose to designate "Redmond" as a network region. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTenantNetworkRegion -NetworkRegionID "RegionA" +``` + +The command shown in Example 1 creates the network region 'RegionA' with no description. Identity and CentralSite will both be set identically to NetworkRegionID. + +## PARAMETERS + +### -Identity +Unique identifier for the network region to be created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassID +This parameter is not used. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CentralSite +This parameter is not used. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of the network region to identify purpose of creating it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkRegionID +The name of the network region. This must be a string that is unique. You cannot specify an NetworkRegionID and an Identity at the same time. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworkregion) + +[Remove-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworkregion) + +[Set-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworkregion) diff --git a/teams/teams-ps/teams/New-CsTenantNetworkSite.md b/teams/teams-ps/teams/New-CsTenantNetworkSite.md new file mode 100644 index 0000000000..81412644a9 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTenantNetworkSite.md @@ -0,0 +1,264 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksite +applicable: Microsoft Teams +title: New-CsTenantNetworkSite +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsTenantNetworkSite + +## SYNOPSIS +As an admin, you can use the Teams PowerShell command, New-CsTenantNetworkSite to define network sites. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. The organization's network site is used for Location-Based Routing. + +## SYNTAX + +### Identity (Default) +``` +New-CsTenantNetworkSite [-Identity] <string> [-Description <string>] [-EmergencyCallingPolicy <string>] + [-EmergencyCallRoutingPolicy <string>] [-EnableLocationBasedRouting <bool>] [-LocationPolicy <string>] + [-NetworkRegionID <string>] [-NetworkRoamingPolicy <string>] [-SiteAddress <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsTenantNetworkSite -NetworkSiteID <string> [-Description <string>] [-EmergencyCallingPolicy <string>] + [-EmergencyCallRoutingPolicy <string>] [-EnableLocationBasedRouting <bool>] [-LocationPolicy <string>] + [-NetworkRegionID <string>] [-NetworkRoamingPolicy <string>] [-SiteAddress <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. + +A best practice for Location Based Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration. In addition, network sites can also be used for configuring Network Roaming Policy capabilities. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTenantNetworkSite -NetworkSiteID "MicrosoftSite1" -NetworkRegionID "RegionRedmond" +``` + +The command shown in Example 1 created the network site 'MicrosoftSite1' with no description. Identity will be set identical with NetworkSiteID. + +The network region 'RegionRedmond' is created beforehand and 'MicrosoftSite1' will be associated with 'RegionRedmond'. + +NetworkSites can exist without all parameters excepts NetworkSiteID. NetworkRegionID can be left blank. + +### Example 2 +```powershell +PS C:\> New-CsTenantNetworkSite -NetworkSiteID "site2" -Description "site 2" -NetworkRegionID "RedmondRegion" -LocationPolicy "TestLocationPolicy" -EnableLocationBasedRouting $true +``` + +The command shown in Example 2 creates the network site 'site2' with the description 'site 2'. This site is enabled for LBR, and associates with network region 'RedmondRegion' and with location policy 'TestLocationPolicy'. + +### Example 3 +```powershell +PS C:\> New-CsTenantNetworkSite -NetworkSiteID "site3" -Description "site 3" -NetworkRegionID "RedmondRegion" -NetworkRoamingPolicy "TestNetworkRoamingPolicy" +``` + +The command shown in Example 3 creates the network site 'site3' with the description 'site 3'. This site is enabled for network roaming capabilities. The example associates the site with network region 'RedmondRegion' and network roaming policy 'TestNetworkRoamingPolicy'. +## PARAMETERS + +### -Identity +Unique identifier for the network site to be created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of the network site to identify purpose of creating it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyCallRoutingPolicy +This parameter is used to assign a custom emergency call routing policy to a network site. For more information, see [Assign a custom emergency call routing policy to a network site](https://learn.microsoft.com/microsoftteams/manage-emergency-call-routing-policies#assign-a-custom-emergency-call-routing-policy-to-a-network-site). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyCallingPolicy +This parameter is used to assign a custom emergency calling policy to a network site. For more information see [Assign a custom emergency calling policy to a network site](https://learn.microsoft.com/microsoftteams/manage-emergency-calling-policies#assign-a-custom-emergency-calling-policy-to-a-network-site). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableLocationBasedRouting +This parameter determines whether the current site is enabled for Location-Based Routing. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationPolicy +This parameter is reserved for Microsoft internal use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkRegionID +NetworkRegionID is the identifier for the network region to which the current network site is associated to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkRoamingPolicy +NetworkRoamingPolicy is the identifier for the network roaming policy to which the network site will associate to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkSiteID +The name of the network site. This must be a string that is unique. You cannot specify an NetworkSiteID and an Identity at the same time. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SiteAddress +This parameter is not used. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksite) + +[Remove-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksite) + +[Set-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksite) diff --git a/teams/teams-ps/teams/New-CsTenantNetworkSubnet.md b/teams/teams-ps/teams/New-CsTenantNetworkSubnet.md new file mode 100644 index 0000000000..0639975119 --- /dev/null +++ b/teams/teams-ps/teams/New-CsTenantNetworkSubnet.md @@ -0,0 +1,183 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksubnet +applicable: Microsoft Teams +title: New-CsTenantNetworkSubnet +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# New-CsTenantNetworkSubnet + +## SYNOPSIS +As an Admin, you can use the Windows PowerShell command, New-CsTenantNetworkSubnet to define network subnets and assign them to network sites. Each internal subnet may only be associated with one site. Tenant network subnet is used for Location Based Routing. + +## SYNTAX + +### Identity (Default) +``` +New-CsTenantNetworkSubnet [-Identity] <string> -MaskBits <int> [-Description <string>] + [-NetworkSiteID <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsTenantNetworkSubnet -MaskBits <int> -SubnetID <string> [-Description <string>] + [-NetworkSiteID <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first. + +When the client is sending the network subnet, please make sure we have already whitelisted the IP address by running this command-let, otherwise the request will be rejected. If you are only adding the IPv4 address by running this command-let, but your client are only sending and IPv6 address, it will be rejected. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> New-CsTenantNetworkSubnet -SubnetID "192.168.0.1" -MaskBits "24" -NetworkSiteID "site1" +``` + +The command shown in Example 1 created the network subnet '192.168.0.1' with no description. The subnet is IPv4 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 24. + +IPv4 format subnet accepts maskbits from 0 to 32 inclusive. + +### Example 2 +```powershell +PS C:\> New-CsTenantNetworkSubnet -SubnetID "2001:4898:e8:25:844e:926f:85ad:dd8e" -MaskBits "120" -NetworkSiteID "site1" +``` + +The command shown in Example 2 created the network subnet '2001:4898:e8:25:844e:926f:85ad:dd8e' with no description. The subnet is IPv6 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 120. + +IPv6 format subnet accepts maskbits from 0 to 128 inclusive. + +## PARAMETERS + +### -Identity +Unique identifier for the network subnet to be created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaskBits +This parameter determines the length of bits to mask to the subnet. + +IPv4 format subnet accepts maskbits from 0 to 32 inclusive. IPv6 format subnet accepts maskbits from 0 to 128 inclusive. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of the network subnet to identify the purpose of creating it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkSiteID +NetworkSiteID is the identifier for the network site which the current network subnet is associating to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SubnetID +The name of the network subnet. This must be a unique and valid IPv4 or IPv6 address. You cannot specify an NetworkSubnetID and an Identity at the same time. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksubnet) + +[Remove-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksubnet) + +[Set-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksubnet) diff --git a/skype/skype-ps/skype/New-CsTenantTrustedIPAddress.md b/teams/teams-ps/teams/New-CsTenantTrustedIPAddress.md similarity index 94% rename from skype/skype-ps/skype/New-CsTenantTrustedIPAddress.md rename to teams/teams-ps/teams/New-CsTenantTrustedIPAddress.md index e5ae285228..95772cba10 100644 --- a/skype/skype-ps/skype/New-CsTenantTrustedIPAddress.md +++ b/teams/teams-ps/teams/New-CsTenantTrustedIPAddress.md @@ -1,11 +1,13 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml Module Name: tmp_rf3olqzj.wbj +online version: https://learn.microsoft.com/powershell/module/teams/new-cstenanttrustedipaddress +title: New-CsTenantTrustedIPAddress schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: --- # New-CsTenantTrustedIPAddress @@ -154,7 +156,9 @@ Accept wildcard characters: False ### -MaskBits This parameter determines the length of bits to mask to the subnet. -IPv4 format IP address accepts maskbits from 0 to 32 inclusive. IPv6 format IP address accepts maskbits from 0 to 128 inclusive. +IPv4 format IP address accepts maskbits from 0 to 32 inclusive. If not provided, the value is set to 32. + +IPv6 format IP address accepts maskbits from 0 to 128 inclusive. If not provided, the value is set to 128. ```yaml Type: System.Int32 @@ -206,8 +210,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -216,6 +219,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/New-CsUserCallingDelegate.md b/teams/teams-ps/teams/New-CsUserCallingDelegate.md new file mode 100644 index 0000000000..bcb61efbcc --- /dev/null +++ b/teams/teams-ps/teams/New-CsUserCallingDelegate.md @@ -0,0 +1,137 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/new-csusercallingdelegate +applicable: Microsoft Teams +title: New-CsUserCallingDelegate +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# New-CsUserCallingDelegate + +## SYNOPSIS +This cmdlet will add a new delegate for calling in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +```powershell +New-CsUserCallingDelegate -Identity <String> -Delegate <String> -MakeCalls <Boolean> -ReceiveCalls <Boolean> -ManageSettings <Boolean> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet adds a new delegate with given permissions for the specified user. + +## EXAMPLES + +### Example 1 +```powershell +New-CsUserCallingDelegate -Identity user1@contoso.com -Delegate user2@contoso.com -MakeCalls $true -ReceiveCalls $true -ManageSettings $true +``` + +## PARAMETERS + +### -Delegate +The Identity of the delegate to add. Can be specified using the ObjectId or the SIP address. + +A user can have up to 25 delegates. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity of the user to add a delegate for. Can be specified using the ObjectId or the SIP address. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeCalls + +Specifies whether delegate is allowed to make calls on behalf of the specified user. + +```yaml +Type: System.Boolean +Parameter Sets: All +Aliases: + +Required: True +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManageSettings + +Specifies whether delegate is allowed to change the delegate and calling settings for the specified user. + +```yaml +Type: System.Boolean +Parameter Sets: All +Aliases: + +Required: True +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveCalls + +Specifies whether delegate is allowed to receive calls on behalf of the specified user. + +```yaml +Type: System.Boolean +Parameter Sets: All +Aliases: + +Required: True +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PowerShell module 4.0.0 or later. + +The specified user need to have the Microsoft Phone System license assigned. + +You can see the delegate of a user by using the Get-CsUserCallingSettings cmdlet. + +## RELATED LINKS +[Get-CsUserCallingSettings](https://learn.microsoft.com/powershell/module/teams/get-csusercallingsettings) + +[Set-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/set-csusercallingdelegate) + +[Remove-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/remove-csusercallingdelegate) diff --git a/skype/skype-ps/skype/New-CsVideoInteropServiceProvider.md b/teams/teams-ps/teams/New-CsVideoInteropServiceProvider.md similarity index 87% rename from skype/skype-ps/skype/New-CsVideoInteropServiceProvider.md rename to teams/teams-ps/teams/New-CsVideoInteropServiceProvider.md index 5c787a93d6..06ece90114 100644 --- a/skype/skype-ps/skype/New-CsVideoInteropServiceProvider.md +++ b/teams/teams-ps/teams/New-CsVideoInteropServiceProvider.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/new-csvideointeropserviceprovider -applicable: Skype for Business Online -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/new-csvideointeropserviceprovider +applicable: Microsoft Teams +Module Name: MicrosoftTeams title: New-CsVideoInteropServiceProvider schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # New-CsVideoInteropServiceProvider @@ -51,7 +51,7 @@ PS C:\> New-CsVideoInteropServiceProvider ## PARAMETERS ### -AadApplicationIds -This is an optional parameter. A semicolon separated list of AAD AppIds of the CVI partner bots can be specified in this parameter. This parameter works in conjunction with AllowAppGuestJoinsAsAuthenticated. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of these bots, is shown in the meeting as an authenticated tenant entity. +This is an optional parameter. A semicolon separated list of Microsoft Entra AppIds of the CVI partner bots can be specified in this parameter. This parameter works in conjunction with AllowAppGuestJoinsAsAuthenticated. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of these bots, is shown in the meeting as an authenticated tenant entity. ```yaml Type: String @@ -67,7 +67,7 @@ Accept wildcard characters: False ### -AllowAppGuestJoinsAsAuthenticated This is an optional parameter. Default = false. -This parameter works in conjunction with AadApplicationIds. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of the bots AAD application ids specified in AadApplicationIds, is shown in the meeting as an authenticated tenant entity. +This parameter works in conjunction with AadApplicationIds. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of the bots Microsoft Entra application ids specified in AadApplicationIds, is shown in the meeting as an authenticated tenant entity. ```yaml Type: Boolean @@ -116,7 +116,7 @@ This is mandatory parameter and can have only one of the 6 values PolycomServiceProviderEnabled PexipServiceProviderEnabled BlueJeansServiceProviderEnabled - + PolycomServiceProviderDisabled PexipServiceProviderDisabled BlueJeansServiceProviderDisabled @@ -230,14 +230,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/New-CsVoiceNormalizationRule.md b/teams/teams-ps/teams/New-CsVoiceNormalizationRule.md new file mode 100644 index 0000000000..50a147a31f --- /dev/null +++ b/teams/teams-ps/teams/New-CsVoiceNormalizationRule.md @@ -0,0 +1,372 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/new-csvoicenormalizationrule +applicable: Microsoft Teams +title: New-CsVoiceNormalizationRule +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +--- + +# New-CsVoiceNormalizationRule + +## SYNOPSIS +Creates a new voice normalization rule. + +Voice normalization rules are used to convert a telephone dialing requirement (for example, dialing 9 to access an outside line) to the E.164 phone number format used by +Skype for Business Server or Microsoft Teams. + +This cmdlet was introduced in Lync Server 2010. + +## SYNTAX + +### Identity (Default) +``` +New-CsVoiceNormalizationRule [-Tenant <Guid>] [-Description <String>] [-Pattern <String>] + [-Translation <String>] [-IsInternalExtension <Boolean>] [-Priority <Int32>] [-Identity] <XdsIdentity> + [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### ParentAndRelativeKey +``` +New-CsVoiceNormalizationRule [-Tenant <Guid>] -Parent <String> -Name <String> [-Description <String>] + [-Pattern <String>] [-Translation <String>] [-IsInternalExtension <Boolean>] [-Priority <Int32>] [-InMemory] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet creates a named voice normalization rule. +These rules are a required part of phone authorization and call routing. +They define the requirements for converting (or translating) numbers from an internal format to a standard (E.164) format. +An understanding of regular expressions is helpful in order to define number patterns that will be translated. + +For Lync or Skype for Business Server, rules that are created by using this cmdlet are part of the dial plan and in addition to being accessible through the +`Get-CsVoiceNormalizationRule` cmdlet can also be accessed through the NormalizationRules property returned by a call to the `Get-CsDialPlan` cmdlet. +You cannot create a normalization rule unless a dial plan with an Identity matching the scope specified in the normalization rule Identity already exists. +For example, you can't create a normalization rule with the Identity site:Redmond/RedmondNormalizationRule unless a dial plan for site:Redmond already exists. + +For Microsoft Teams, rules that are created by using this cmdlet can only be created with the InMemory switch and should be added to a tenant dial plan using +the `New-CsTenantDialPlan` or `Set-CsTenantDialPlan` cmdlets. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +New-CsVoiceNormalizationRule -Identity "site:Redmond/Prefix Redmond" +``` + +This example creates a new voice normalization rule for site Redmond named Prefix Redmond. +Because no other parameters are specified, the rule is created with the default values. +Notice that the value passed to the Identity parameter is in double quotes; this is because the name of the rule (Prefix Redmond) contains a space. +If the rule name does not contain a space you don't need to enclose the Identity in double quotes. + +Keep in mind that a dial plan for the Redmond site must exist for this command to succeed. +You can create a new dial plan by calling the `New-CsDialPlan` cmdlet. + +### -------------------------- Example 2 -------------------------- +``` +New-CsVoiceNormalizationRule -Parent SeattleUser -Name SeattleFourDigit -Description "Dialing with internal four-digit extension" -Pattern '^(\d{4})$' -Translation '+1206555$1' +``` + +This example creates a new voice normalization rule named SeattleFourDigit that applies to the per-user dial plan with the Identity SeattleUser. +(Note: Rather than specifying a Parent and a Name, we could have instead created this same rule by specifying -Identity SeattleUser/SeattleFourDigit.) We've included a Description explaining that this rule is for translating numbers dialed internally with only a 4-digit extension. +In addition, Pattern and Translation values have been specified. +These values translate a four-digit number (specified by the regular expression in the Pattern) to the same four-digit number, but prefixed by the Translation value (+1206555). +For example, if the extension 1234 was entered, this rule would translate that extension to the number +12065551234. + +Note the single quotes around the Pattern and Translation values. +Single quotes are required for these values; double quotes (or no quotes) will not work in this instance. + +As in Example 1, a dial plan with the given scope must exist. +In this case, that means a dial plan with the Identity SeattleUser must already exist. + +### -------------------------- Example 3 -------------------------- +``` +$nr1=New-CsVoiceNormalizationRule -Identity dp1/nr1 -Description "Dialing with internal four-digit extension" -Pattern '^(\d{4})$' -Translation '+1206555$1' -InMemory +New-CsTenantDialPlan -Identity DP1 -NormalizationRules @{Add=$nr1} +``` + +This example creates a new in-memory voice normalization rule and then adds it to a new tenant dial plan DP1 to be used for Microsoft Teams users. + +## PARAMETERS + +### -Identity +A unique identifier for the rule. +The Identity specified must include the scope followed by a slash and then the name; for example: site:Redmond/Rule1, where site:Redmond is the scope and Rule1 is the name. +The name portion will automatically be stored in the Name property. +You cannot specify values for Identity and Name in the same command. + +For Lync and Skype for Business Server, voice normalization rules can be created at the following scopes: global, site, service (Registrar and PSTNGateway only) and per user. +A dial plan with an Identity matching the scope of the normalization rule must already exist before a new rule can be created. +(To retrieve a list of dial plans, call the `Get-CsDialPlan` cmdlet.) + +For Microsoft Teams, voice normalization rules can be created at the following scopes: global and tag. + +The Identity parameter is required unless the Parent parameter is specified. +You cannot include the Identity parameter and the Parent parameter in the same command. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The name of the rule. +This parameter is required if a value has been specified for the Parent parameter. +If no value has been specified for the Parent parameter, Name defaults to the name specified in the Identity parameter. +For example, if a rule is created with the Identity site:Redmond/RedmondRule, the Name will default to RedmondRule. +The Name parameter and the Identity parameter cannot be used in the same command. + +```yaml +Type: String +Parameter Sets: ParentAndRelativeKey +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Parent +The scope at which the new normalization rule will be created. +This value must be global; site:\<sitename\>, where \<sitename\> is the name of the Skype for Business Server site; PSTN gateway or Registrar service, such as +PSTNGateway:redmond.litwareinc.com; or a string designating a per user rule. +A dial plan with the specified scope must already exist or the command will fail. + +The Parent parameter is required unless the Identity parameter is specified. +You cannot include the Identity parameter and the Parent parameter in the same command. +If you include the Parent parameter, the Name parameter is also required. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +A friendly description of the normalization rule. + +Maximum string length: 512 characters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsInternalExtension +If True, the result of applying this rule will be a number internal to the organization. +If False, applying the rule results in an external number. +This value is ignored if the value of the OptimizeDeviceDialing property of the associated dial plan/tenant dial plan is set to False. + +Default: False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern +A regular expression that the dialed number must match in order for this rule to be applied. + +Default: ^(\d{11})$ (The default represents any set of numbers up to 11 digits.) + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +The order in which rules are applied. +A phone number might match more than one rule. +This parameter sets the order in which the rules are tested against the number. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Translation +The regular expression pattern that will be applied to the number to convert it to E.164 format. + +Default: +$1 (The default prefixes the number with a plus sign \[+\].) + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InMemory +Creates an object reference without actually committing the object as a permanent change. + +For Lync or Skype for Business Server, if you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the +object reference and then commit those changes by calling this cmdlet's matching Set-\<cmdlet\>. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +For internal Microsoft usage. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +None. + +## OUTPUTS + +### Output types +This cmdlet creates an object of type Microsoft.Rtc.Management.WritableConfig.Policy.Voice.NormalizationRule. + +## NOTES + +## RELATED LINKS + +[Test-CsVoiceNormalizationRule](https://learn.microsoft.com/powershell/module/teams/test-csvoicenormalizationrule) + +[Get-CsDialPlan](https://learn.microsoft.com/powershell/module/teams/get-csdialplan) + +[New-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/new-cstenantdialplan) + +[Set-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/set-cstenantdialplan) diff --git a/teams/teams-ps/teams/New-Team.md b/teams/teams-ps/teams/New-Team.md index a3d697135e..5ca7ae7b5c 100644 --- a/teams/teams-ps/teams/New-Team.md +++ b/teams/teams-ps/teams/New-Team.md @@ -1,23 +1,23 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/new-team +online version: https://learn.microsoft.com/powershell/module/teams/new-team +title: New-Team schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- # New-Team ## SYNOPSIS -This cmdlet lets you provision a new Team for use in Microsoft Teams and will create an O365 Unified Group to back the team. -Groups created through teams cmdlets, APIs, or clients will not show up in Outlook by default. -If you want these groups to appear in Outlook clients, you can use the Set-UnifiedGroup (https://docs.microsoft.com/en-us/powershell/module/exchange/users-and-groups/set-unifiedgroup?view=exchange-ps) cmdlet in the Exchange Powershell Module to set the parameter HiddenFromExchangeClients to $false. +This cmdlet lets you provision a new Team for use in Microsoft Teams and will create an O365 Unified Group to back the team. +Groups created through teams cmdlets, APIs, or clients will not show up in Outlook by default. -Note: The Teams application may need to be open by an Owner for up to two hours before changes are reflected. +If you want these groups to appear in Outlook clients, you can use the [Set-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchange/set-unifiedgroup) cmdlet in the Exchange Powershell Module to disable the switch parameter `HiddenFromExchangeClientsEnabled` (-HiddenFromExchangeClientsEnabled:$false). -IMPORTANT: Using this cmdlet to create a new team using a template is still in preview. You can install and use the preview module from the PowerShell test gallery. For instructions on installing and using the Teams PowerShell preview module, see https://docs.microsoft.com/MicrosoftTeams/private-channels-life-cycle-management#install-the-latest-teams-powershell-module-from-the-powershell-test-gallery. +Note: The Teams application may need to be open by an Owner for up to two hours before changes are reflected. ## SYNTAX @@ -30,8 +30,8 @@ New-Team -DisplayName <String> [-Description <String>] [-MailNickName <String>] [-AllowCreateUpdateChannels <Boolean>] [-AllowDeleteChannels <Boolean>] [-AllowAddRemoveApps <Boolean>] [-AllowCreateUpdateRemoveTabs <Boolean>] [-AllowCreateUpdateRemoveConnectors <Boolean>] [-AllowUserEditMessages <Boolean>] [-AllowUserDeleteMessages <Boolean>] [-AllowOwnerDeleteMessages <Boolean>] - [-AllowTeamMentions <Boolean>] [-AllowChannelMentions <Boolean>] [-ShowInTeamsSearchAndSuggestions <Boolean>] - [-RetainCreatedGroup <SwitchParameter>] [<CommonParameters>] + [-AllowTeamMentions <Boolean>] [-AllowChannelMentions <Boolean>] [-ShowInTeamsSearchAndSuggestions <Boolean>] + [-RetainCreatedGroup <SwitchParameter>] [-AllowCreatePrivateChannels <Boolean>] [<CommonParameters>] ``` ### MigrateGroup @@ -46,7 +46,7 @@ New-Team -GroupId <String> [-Owner <String>] [-AllowGiphy <Boolean>] [-GiphyCont ``` ## DESCRIPTION -Creates a new team with user specified settings, and returns a Group object with a GroupID property. Note that Templates are not yet supported in our 1.0 PowerShell release. +Creates a new team with user specified settings, and returns a Group object with a GroupID property. ## EXAMPLES @@ -55,14 +55,17 @@ Creates a new team with user specified settings, and returns a Group object with New-Team -DisplayName "Tech Reads" ``` +This example creates a team with all parameters with their default values. + ### Example 2 ``` New-Team -DisplayName "Tech Reads" -Description "Team to post technical articles and blogs" -Visibility Public ``` +This example creates a team with a specific description and public visibility. + ### Example 3 ``` -Connect-MicrosoftTeams -AccountId myaccount@example.com $group = New-Team -MailNickname "TestTeam" -displayname "Test Teams" -Visibility "private" Add-TeamUser -GroupId $group.GroupId -User "fred@example.com" Add-TeamUser -GroupId $group.GroupId -User "john@example.com" @@ -72,14 +75,17 @@ New-TeamChannel -GroupId $group.GroupId -DisplayName "Exec status" New-TeamChannel -GroupId $group.GroupId -DisplayName "Contracts" ``` +This example creates a team, adds three members to it, and creates three channels within it. + ## PARAMETERS ### -MailNickName The MailNickName parameter specifies the alias for the associated Office 365 Group. This value will be used for the mail enabled object and will be used as PrimarySmtpAddress for this Office 365 Group. The value of the MailNickName parameter has to be unique across your tenant. +Note: If Microsoft 365 groups naming policies are enabled in your tenant, this parameter is required and must also comply with the naming policy. -For more details about the naming conventions see here: New-UnifiedGroup, Parameter: -Alias (https://docs.microsoft.com/en-us/powershell/module/exchange/users-and-groups/new-unifiedgroup?view=exchange-ps#optional-parameters). +For more details about the naming conventions see here: [New-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchange/new-unifiedgroup#parameters), Parameter: -Alias. ```yaml Type: String @@ -109,8 +115,7 @@ Accept wildcard characters: False ``` ### -Description -Team description. -Team Description Characters Limit - 1024. +Team description. Characters Limit - 1024. ```yaml Type: String @@ -125,8 +130,7 @@ Accept wildcard characters: False ``` ### -DisplayName -Team display name. -Team Name Characters Limit - 256. +Team display name. Characters Limit - 256. ```yaml Type: String @@ -141,8 +145,6 @@ Accept wildcard characters: False ``` ### -Template -Note: this parameter is not supported in our 1.0 PowerShell release, only in Preview. - If you have an EDU license, you can use this parameter to specify which template you'd like to use for creating your group. Do not use this parameter when converting an existing group. @@ -161,9 +163,10 @@ Accept wildcard characters: False ``` ### -Owner -An admin who is allowed to create on behalf of another user should use this flag to specify the desired owner of the group. -This user will be added as both a member and an owner of the group. +An admin who is allowed to create on behalf of another user should use this flag to specify the desired owner of the group. +This user will be added as both a member and an owner of the group. If not specified, the user who creates the team will be added as both a member and an owner. +Please note: This parameter is mandatory, if connected using Certificate Based Authentication. ```yaml Type: String @@ -187,7 +190,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -202,7 +205,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -217,7 +220,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -232,7 +235,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -247,7 +250,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -262,7 +265,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -277,7 +280,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -292,7 +295,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -307,7 +310,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: False Accept pipeline input: False Accept wildcard characters: False ``` @@ -322,7 +325,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: False Accept pipeline input: False Accept wildcard characters: False ``` @@ -337,7 +340,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -352,7 +355,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -367,7 +370,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -382,7 +385,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -397,7 +400,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -412,13 +415,14 @@ Aliases: Required: False Position: Named -Default value: None +Default value: Moderate Accept pipeline input: False Accept wildcard characters: False ``` ### -GroupId Specify a GroupId to convert to a Team. If specified, you cannot provide the other values that are already specified by the existing group, namely: Visibility, Alias, Description, or DisplayName. +If, for example, you need to create a Team from an existing Microsoft 365 Group, use the _ExternalDirectoryObjectId_ property value returned by [Get-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchange/get-unifiedgroup?view=exchange-ps). ```yaml Type: String @@ -433,7 +437,7 @@ Accept wildcard characters: False ``` ### -Visibility -Set to Public to allow all users in your organization to join the group by default. Set to Private to require that an owner approve the join request. +Set to Public to allow all users in your organization to join the group by default. Set to Private to require that an owner approve the join request. ```yaml Type: String @@ -442,7 +446,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: Private Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` @@ -457,7 +461,7 @@ Aliases: Required: False Position: Named -Default value: None +Default value: True Accept pipeline input: False Accept wildcard characters: False ``` @@ -477,9 +481,23 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AllowCreatePrivateChannels +Determines whether private channel creation is allowed for the team. + +```yaml +Type: Boolean +Parameter Sets: CreateTeam +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -491,9 +509,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[Remove-Team](remove-team.md) - -[Get-Team](get-team.md) +[Remove-Team](https://learn.microsoft.com/powershell/module/teams/remove-team) -[Set-Team](set-team.md) +[Get-Team](https://learn.microsoft.com/powershell/module/teams/get-team) +[Set-Team](https://learn.microsoft.com/powershell/module/teams/set-team) diff --git a/teams/teams-ps/teams/New-TeamChannel.md b/teams/teams-ps/teams/New-TeamChannel.md index 8da95086b6..579b2c7209 100644 --- a/teams/teams-ps/teams/New-TeamChannel.md +++ b/teams/teams-ps/teams/New-TeamChannel.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/new-teamchannel +online version: https://learn.microsoft.com/powershell/module/teams/new-teamchannel +title: New-TeamChannel schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -22,8 +23,7 @@ New-TeamChannel -GroupId <String> -DisplayName <String> [-Description <String>] ## DESCRIPTION -> [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. +Add a new channel to a team. ## EXAMPLES @@ -88,8 +88,8 @@ Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` -### -MembershipType (available in private preview) -Channel membership type, Standard or Private. +### -MembershipType +Channel membership type, Standard, Shared, or Private. ```yaml Type: String @@ -103,7 +103,7 @@ Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` -### -Owner (available in private preview) +### -Owner UPN of owner that can be specified while creating a private channel. ```yaml @@ -119,10 +119,10 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS + ### GroupId, DisplayName, Description, MembershipType, Owner ## OUTPUTS diff --git a/teams/teams-ps/teams/New-TeamsApp.md b/teams/teams-ps/teams/New-TeamsApp.md index 1d7ce6523e..1ba731d7b5 100644 --- a/teams/teams-ps/teams/New-TeamsApp.md +++ b/teams/teams-ps/teams/New-TeamsApp.md @@ -1,7 +1,8 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/new-teamsapp +online version: https://learn.microsoft.com/powershell/module/teams/new-teamsapp +title: New-TeamsApp schema: 2.0.0 --- @@ -59,14 +60,12 @@ Accept wildcard characters: False ``` ### 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 (http://go.microsoft.com/fwlink/?LinkID=113216). +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Register-CsOnlineDialInConferencingServiceNumber.md b/teams/teams-ps/teams/Register-CsOnlineDialInConferencingServiceNumber.md new file mode 100644 index 0000000000..e2c1985c62 --- /dev/null +++ b/teams/teams-ps/teams/Register-CsOnlineDialInConferencingServiceNumber.md @@ -0,0 +1,186 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/register-csonlinedialinconferencingservicenumber +applicable: Microsoft Teams +title: Register-CsOnlineDialInConferencingServiceNumber +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Register-CsOnlineDialInConferencingServiceNumber + +## SYNOPSIS +When you buy Audio Conferencing licenses, Microsoft is hosting your audio conferencing bridge for your organization. The audio conferencing bridge gives out dial-in phone numbers from different locations so that meeting organizers and participants can use them to join Microsoft Teams meetings using a phone. +In addition to the phone numbers already assigned to your conferencing bridge, you can get additional service numbers (toll and toll-free numbers used for audio conferencing) from other locations, and then assign them to the conferencing bridge so you can expand coverage for your users. The Register-CsOnlineDialInConferencingServiceNumber command allows you to assign any additional service number that you may have acquired to your conference bridge. + +## SYNTAX + +### UniqueNumberParams +``` +Register-CsOnlineDialInConferencingServiceNumber [-Identity] <String> [-BridgeId <Guid>] + [-BridgeName <String>] [-Tenant <Guid>] [-TenantDomain <String>] [-DomainController <Fqdn>] [-Force] + [<CommonParameters>] +``` + +### InstanceParams +``` +Register-CsOnlineDialInConferencingServiceNumber [-Instance] <ConferencingServiceNumber> + [-BridgeId <Guid>] [-BridgeName <String>] [-Tenant <Guid>] [-TenantDomain <String>] + [-DomainController <Fqdn>] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +The Register-CsOnlineDialInConferencingServiceNumber command allows you to assign any additional service number that you may have acquired to your conference bridge. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Register-CsOnlineDialinConferencingServiceNumber -Identity +1425555XXX -BridgeId fb91u3e9-5c2a-42c3-8yy5-ec02beexxx09 +``` + +This command registers the telephone number +1425555XXX to your conference bridge. To find the bridge ID associated with your conference bridge you can use the command Get-CsOnlineDialInConferencingBridge. + +## PARAMETERS + +### -Identity +PARAMVALUE: String + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +PARAMVALUE: ConferencingServiceNumber + +```yaml +Type: ConferencingServiceNumber +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BridgeId +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BridgeName +PARAMVALUE: String + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +PARAMVALUE: Fqdn + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantDomain +PARAMVALUE: String + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsApplicationAccessPolicy.md b/teams/teams-ps/teams/Remove-CsApplicationAccessPolicy.md new file mode 100644 index 0000000000..29aebeff75 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsApplicationAccessPolicy.md @@ -0,0 +1,73 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csapplicationaccesspolicy +applicable: Microsoft Teams +title: Remove-CsApplicationAccessPolicy +schema: 2.0.0 +manager: zhengni +author: frankpeng7 +ms.author: frpeng +ms.reviewer: +--- + +# Remove-CsApplicationAccessPolicy + +## SYNOPSIS + +Deletes an existing application access policy. + +## SYNTAX + +### Identity + +``` +Remove-CsApplicationAccessPolicy [-Identity <XdsIdentity>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet deletes an existing application access policy. + +## EXAMPLES + +### Remove an application access policy + +``` +PS C:\> Remove-CsApplicationAccessPolicy -Identity "ASimplePolicy" +``` + +The command shown above deletes the application access policy ASimplePolicy. + +## PARAMETERS + +### -Identity + +Unique identifier assigned to the policy when it was created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Grant-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Get-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Set-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) diff --git a/teams/teams-ps/teams/Remove-CsAutoAttendant.md b/teams/teams-ps/teams/Remove-CsAutoAttendant.md new file mode 100644 index 0000000000..a847c6ab1f --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsAutoAttendant.md @@ -0,0 +1,92 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csautoattendant +applicable: Microsoft Teams +title: Remove-CsAutoAttendant +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsAutoAttendant + +## SYNOPSIS +Use the Remove-CsAutoAttendant cmdlet to delete an Auto Attendant (AA). + +> [!NOTE] +> Remove any associated resource accounts with [Remove-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/remove-csonlineapplicationinstanceassociation) before attempting to delete the Auto Attendant (AA). + +## SYNTAX + +``` +Remove-CsAutoAttendant -Identity <String> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The Remove-CsAutoAttendant cmdlet deletes an AA that is specified by the Identity parameter. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Remove-CsAutoAttendant -Identity "fa9081d6-b4f3-5c96-baec-0b00077709e5" +``` + +This example deletes the AA that has an identity of fa9081d6-b4f3-5c96-baec-0b00077709e5. + +## PARAMETERS + +### -Identity +The identity for the AA to be removed. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### String +The Remove-CsAutoAttendant cmdlet accepts a string as the Identity parameter. + +## OUTPUTS + +### None + +## NOTES + +## RELATED LINKS + +[New-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/new-csautoattendant) + +[Get-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/get-csautoattendant) + +[Set-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/set-csautoattendant) diff --git a/skype/skype-ps/skype/Remove-CsCallQueue.md b/teams/teams-ps/teams/Remove-CsCallQueue.md similarity index 83% rename from skype/skype-ps/skype/Remove-CsCallQueue.md rename to teams/teams-ps/teams/Remove-CsCallQueue.md index ba0c7a26eb..b4138debb8 100644 --- a/skype/skype-ps/skype/Remove-CsCallQueue.md +++ b/teams/teams-ps/teams/Remove-CsCallQueue.md @@ -1,13 +1,14 @@ --- external help file: Microsoft.Rtc.Management.dll-Help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cscallqueue -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-cscallqueue +applicable: Microsoft Teams title: Remove-CsCallQueue schema: 2.0.0 ms.reviewer: manager: bulenteg -ms.author: tomkau author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney --- # Remove-CsCallQueue @@ -33,7 +34,6 @@ Remove-CsCallQueue -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 This example removes the Call Queue with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no Call Queue exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. - ## PARAMETERS ### -Identity @@ -42,8 +42,8 @@ PARAMVALUE: Guid ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -58,8 +58,8 @@ PARAMVALUE: Guid ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -69,19 +69,17 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### Identity Represents the unique identifier of a Call Queue. - ## OUTPUTS ### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue ## NOTES - ## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsCallingLineIdentity.md b/teams/teams-ps/teams/Remove-CsCallingLineIdentity.md new file mode 100644 index 0000000000..0a95b6cbed --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsCallingLineIdentity.md @@ -0,0 +1,103 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-cscallinglineidentity +applicable: Microsoft Teams +title: Remove-CsCallingLineIdentity +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsCallingLineIdentity + +## SYNOPSIS +Use the `Remove-CsCallingLineIdentity` cmdlet to remove a Caller ID policy from your organization. + +## SYNTAX + +``` +Remove-CsCallingLineIdentity [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet will remove a Caller ID policy from your organization or resets the Global policy instance to the default values. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Remove-CsCallingLineIdentity -Identity Anonymous +``` + +This example removes a Caller ID policy. + +## PARAMETERS + +### -Identity +The Identity parameter identifies the Caller ID policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing, and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/get-cscallinglineidentity) + +[Grant-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/grant-cscallinglineidentity) + +[New-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/new-cscallinglineidentity) + +[Set-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/set-cscallinglineidentity) diff --git a/teams/teams-ps/teams/Remove-CsComplianceRecordingForCallQueueTemplate.md b/teams/teams-ps/teams/Remove-CsComplianceRecordingForCallQueueTemplate.md new file mode 100644 index 0000000000..8d0edf2cca --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsComplianceRecordingForCallQueueTemplate.md @@ -0,0 +1,82 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsComplianceRecordingForCallQueueTemplate +applicable: Microsoft Teams +title: Remove-CsComplianceRecordingForCallQueueTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsComplianceRecordingForCallQueueTemplate + +## SYNTAX + +```powershell +Remove-CsComplianceRecordingForCallQueueTemplate -Id <String> [<CommonParameters>] +``` + +## DESCRIPTION +Use the Remove-CsComplianceRecordingForCallQueueTemplate cmdlet to delete a Compliance Recording for Call Queues template. If the template is currently assigned to a call queue, an error will be returned. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsComplianceRecordingForCallQueueTemplate -Id 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +``` + +This example deletes the Compliance Recording for Call Queue template with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no Compliance Recording for Call Queue template exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. + +## PARAMETERS + +### -Id +The Id parameter is the unique identifier assigned to the Compliance Recording for Call Queue template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[New-CsComplianceRecordingForCallQueueTemplate](./New-CsComplianceRecordingForCallQueueTemplate.md) + +[Set-CsComplianceRecordingForCallQueueTemplate](./Set-CsComplianceRecordingForCallQueueTemplate.md) + +[Get-CsComplianceRecordingForCallQueueTemplate](./Get-CsComplianceRecordingForCallQueueTemplate.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + diff --git a/teams/teams-ps/teams/Remove-CsCustomPolicyPackage.md b/teams/teams-ps/teams/Remove-CsCustomPolicyPackage.md new file mode 100644 index 0000000000..c5fbbf878d --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsCustomPolicyPackage.md @@ -0,0 +1,71 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Remove-CsCustomPolicyPackage +author: sunguchuan +ms.author: gucsun +manager: dasosby +online version: https://learn.microsoft.com/powershell/module/teams/remove-cscustompolicypackage +schema: 2.0.0 +--- + +# Remove-CsCustomPolicyPackage + +## SYNOPSIS + +This cmdlet deletes a custom policy package. + +## SYNTAX + +``` +Remove-CsCustomPolicyPackage -Identity <String> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet deletes a custom policy package. All available package names can be found by running Get-CsPolicyPackage. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsCustomPolicyPackage -Identity "MyPackage" +``` + +Deletes a custom package named "MyPackage". + +## PARAMETERS + +### -Identity + +The name of the custom package. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +Default packages created by Microsoft cannot be deleted. + +## RELATED LINKS + +[Get-CsPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage) + +[New-CsCustomPolicyPackage](https://learn.microsoft.com/powershell/module/teams/new-cscustompolicypackage) + +[Update-CsCustomPolicyPackage](https://learn.microsoft.com/powershell/module/teams/update-cscustompolicypackage) diff --git a/teams/teams-ps/teams/Remove-CsExternalAccessPolicy.md b/teams/teams-ps/teams/Remove-CsExternalAccessPolicy.md new file mode 100644 index 0000000000..a801caa0bb --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsExternalAccessPolicy.md @@ -0,0 +1,218 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csexternalaccesspolicy +applicable: Microsoft Teams +title: Remove-CsExternalAccessPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Remove-CsExternalAccessPolicy + +## SYNOPSIS +Enables you to remove an existing external access policy. +External access policies determine whether or not your users can: 1) Communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) Communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Windows Live; 3) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop) and 4) Access Skype for Business Server over the Internet, without having to log on to your internal network. +This cmdlet was introduced in Lync Server 2010. + +## SYNTAX + +``` +Remove-CsExternalAccessPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +When you install Skype for Business Server your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with other people who have SIP accounts in your Active Directory Domain Services. +In addition, users are not allowed to access Skype for Business Server over the Internet; instead, they must be logged on to your internal network before they will be able to log on to Skype for Business Server. + +1. That might be sufficient to meet your communication needs. +If it doesn't meet your needs you can use external access policies to extend the ability of your users to communicate and collaborate. +External access policies can grant (or revoke) the ability of your users to do any or all of the following: + +2. Communicate with people who have SIP accounts with a federated organization. +Note that enabling federation alone will not provide users with this capability. +Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. + +3. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration). + +4. Communicate with people who have SIP accounts with a public instant messaging service such as Windows Live. + +Access Skype for Business Server over the Internet, without having to first log on to your internal network. +This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. + +When you install Skype for Business Server, a global external access policy is automatically created for you. +In addition to the global policy, you can use the `New-CsExternalAccessPolicy` cmdlet to create external access policies configured at the site or per-user scopes. + +The `Remove-CsExternalAccessPolicy` cmdlet enables you to delete any policies that were created by using the `New-CsExternalAccessPolicy` cmdlet; that means you can delete any policies assigned to the site scope or the per-user scope. +You can also run the `Remove-CsExternalAccessPolicy` cmdlet against the global external access policy. +In that case, however, the global policies will not be deleted; by design, global policies cannot be deleted. +Instead, the properties of the global policy will simply be reset to their default values. + +## EXAMPLES + +### -------------------------- Example 1 ------------------------ +``` +Remove-CsExternalAccessPolicy -Identity site:Redmond +``` + +In Example 1, the external access policy with the Identity site:Redmond is deleted. +After the policy is removed, users in the Redmond site will have their external access permissions governed by the global policy. + +### -------------------------- Example 2 ------------------------ +``` +Get-CsExternalAccessPolicy -Filter site:* | Remove-CsExternalAccessPolicy +``` + +Example 2 deletes all the external access policies that have been configured at the site scope. +To carry out this task, the command first uses the `Get-CsExternalAccessPolicy` cmdlet and the Filter parameter to return a collection of policies configured at the site scope; the filter value "site:*" limits the returned data to external access policies that have an Identity that begins with the string value "site:". +The filtered collection is then piped to the `Remove-CsExternalAccessPolicy` cmdlet, which deletes each policy in the collection. + +### -------------------------- Example 3 ------------------------ +``` +Get-CsExternalAccessPolicy | Where-Object {$_.EnableFederationAccess -eq $True} | Remove-CsExternalAccessPolicy +``` + +In Example 3, all the external access policies that allow federation access are deleted. +To do this, the command first calls the `Get-CsExternalAccessPolicy` cmdlet to return a collection of all the external access policies configured for use in the organization. +This collection is then piped to the `Where-Object` cmdlet, which picks out only those policies where the EnableFederationAccess property is equal to True. +This filtered collection is then piped to the `Remove-CsExternalAccessPolicy` cmdlet, which deletes each policy in the collection. + +### -------------------------- Example 4 ------------------------ +``` +Get-CsExternalAccessPolicy | Where-Object {$_.EnableFederationAccess -eq $True -or $_.EnablePublicCloudAccess -eq $True} | Remove-CsExternalAccessPolicy +``` + +Example 4 deletes all the external access policies that meet at least one of two criteria: federation access is allowed, public cloud access is allowed, or both are allowed. +To carry out this task, the command first uses the `Get-CsExternalAccessPolicy` cmdlet to return a collection of all the external access policies configured for use in the organization. +This collection is then piped to the `Where-Object` cmdlet, which selects only those policies that meet the following criteria: either EnableFederationAccess is equal to True and/or EnablePublicCloudAccess is equal to True. +Policies meeting one (or both) of those criteria are then piped to and removed by, the `Remove-CsExternalAccessPolicy` cmdlet. + +To delete all the policies where both EnableFederationAccess and EnablePublicCloudAccess are True use the -and operator when calling the `Where-Object` cmdlet: + +`Where-Object {$_.EnableFederationAccess -eq $True -and $_.EnablePublicCloudAccess -eq $True}` + +## PARAMETERS + +### -Identity +Unique identifier for the external access policy to be removed. +External access policies can be configured at the global, site, or per-user scopes. +To "remove" the global policy, use this syntax: `-Identity global`. +(Note that the global policy cannot actually be removed. +Instead, all the properties in the global policy will be reset to their default values.) To remove a site policy, use syntax similar to this: `-Identity site:Redmond`. +To remove a per-user policy, use syntax similar to this: `-Identity SalesAccessPolicy`. + +Note that wildcards are not allowed when specifying an Identity. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: True +Position: 2 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might occur when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the Skype for Business Online tenant account for whom the external access policy is being removed. +For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can return the tenant ID for each of your Skype for Business Online tenants by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy object. +The `Remove-CsExternalAccessPolicy` cmdlet accepts pipelined input of the external access policy object. + +## OUTPUTS + +### Output types +None. +Instead, the `Remove-CsExternalAccessPolicy` cmdlet does not return a value or object. +Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy object. + +## NOTES + +## RELATED LINKS + +[Get-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/get-csexternalaccesspolicy) + +[Grant-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csexternalaccesspolicy) + +[New-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csexternalaccesspolicy) + +[Set-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/set-csexternalaccesspolicy) diff --git a/teams/teams-ps/teams/Remove-CsGroupPolicyAssignment.md b/teams/teams-ps/teams/Remove-CsGroupPolicyAssignment.md index 08aaaf5979..db975cb1bc 100644 --- a/teams/teams-ps/teams/Remove-CsGroupPolicyAssignment.md +++ b/teams/teams-ps/teams/Remove-CsGroupPolicyAssignment.md @@ -1,25 +1,26 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/remove-csgrouppolicyassignment +online version: https://learn.microsoft.com/powershell/module/teams/remove-csgrouppolicyassignment +title: Remove-CsGroupPolicyAssignment schema: 2.0.0 author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsGroupPolicyAssignment ## SYNOPSIS -**Note:** This cmdlet is currently only available in private preview in the pre-release Teams PowerShell module. - This cmdlet is used to remove a group policy assignment. ## SYNTAX ``` -Remove-CsGroupPolicyAssignment -GroupId <String> -PolicyType <String> +Remove-CsGroupPolicyAssignment -GroupId <String> -PolicyType <String> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-PassThru] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION @@ -29,9 +30,7 @@ When a policy assignment is removed from a group, any other group policy assignm ## EXAMPLES -### Example 1 -In this example, the policy assignment with rank 2 is removed. As a result, the policy assignment with rank 3 is updated to rank 2. - +### EXAMPLE 1 ``` Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy @@ -41,7 +40,7 @@ d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 TeamsMeetingPolicy AllOn 1 10/29/20 e050ce51-54bc-45b7-b3e6-c00343d31274 TeamsMeetingPolicy AllOff 2 11/2/2019 12:20:41 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 566b8d39-5c5c-4aaa-bc07-4f36278a1b38 TeamsMeetingPolicy Kiosk 3 11/2/2019 12:14:41 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 -Remove-CsGroupPolicyAssignment -GroupId e050ce51-54bc-45b7-b3e6-c00343d31274 -PolicyType TeamsMeetingPolicy +Remove-CsGroupPolicyAssignment -GroupId e050ce51-54bc-45b7-b3e6-c00343d31274 -PolicyType TeamsMeetingPolicy Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy @@ -51,6 +50,8 @@ d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 TeamsMeetingPolicy AllOn 1 10/29/20 566b8d39-5c5c-4aaa-bc07-4f36278a1b38 TeamsMeetingPolicy Kiosk 2 11/2/2019 12:14:41 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 ``` +In this example, the policy assignment with rank 2 is removed. As a result, the policy assignment with rank 3 is updated to rank 2. + ## PARAMETERS ### -GroupId @@ -58,7 +59,7 @@ The ID of the group from which the assignment will be removed. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -73,7 +74,7 @@ The policy type of the assignment to be removed from the group. ```yaml Type: String -Parameter Sets: +Parameter Sets: (All) Aliases: Required: True @@ -83,9 +84,144 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Break +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Returns true when the command succeeds + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -95,9 +231,8 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[Get-CsGroupPolicyAssignment]() - -[New-CsGroupPolicyAssignment]() +[New-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment) -[Set-CsGroupPolicyAssignment]() +[Get-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/get-csgrouppolicyassignment) +[Set-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/set-csgrouppolicyassignment) diff --git a/teams/teams-ps/teams/Remove-CsHybridTelephoneNumber.md b/teams/teams-ps/teams/Remove-CsHybridTelephoneNumber.md new file mode 100644 index 0000000000..d08b9fba67 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsHybridTelephoneNumber.md @@ -0,0 +1,122 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-cshybridtelephonenumber +applicable: Microsoft Teams +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +title: Remove-CsHybridTelephoneNumber +schema: 2.0.0 +--- + +# Remove-CsHybridTelephoneNumber + +## SYNOPSIS +This cmdlet removes a hybrid telephone number. + +> [!IMPORTANT] +> This cmdlet is being deprecated. Use the new **New-CsOnlineTelephoneNumberReleaseOrder** cmdlet to remove a telephone number for Audio Conferencing with Direct Routing in Microsoft 365 GCC High and DoD clouds. Detailed instructions on how to use the new cmdlet can be found at [New-CsOnlineTelephoneNumberReleaseOrder](/powershell/module/teams/new-csonlinetelephonenumberreleaseorder?view=teams-ps). + +## SYNTAX + +### Identity (Default) +```powershell +Remove-CsHybridTelephoneNumber -TelephoneNumber <string> [-Force] [-WhatIf] [-Confirm][<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes a hybrid telephone number used for Audio Conferencing with Direct Routing for GCC High and DoD clouds. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsHybridTelephoneNumber -TelephoneNumber 14025551234 +``` +This example removes the hybrid phone number +1 (402) 555-1234. + +## PARAMETERS + +### -TelephoneNumber +The telephone number to remove. The number should be specified without a prefixed "+". The phone number can't have "tel:" prefixed. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES + +The cmdlet is only available in GCC High and DoD cloud instances. + +## RELATED LINKS + +[New-CsHybridTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/new-cshybridtelephonenumber) + +[Get-CsHybridTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/get-cshybridtelephonenumber) diff --git a/teams/teams-ps/teams/Remove-CsInboundBlockedNumberPattern.md b/teams/teams-ps/teams/Remove-CsInboundBlockedNumberPattern.md new file mode 100644 index 0000000000..c41907981c --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsInboundBlockedNumberPattern.md @@ -0,0 +1,99 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csinboundblockednumberpattern +applicable: Microsoft Teams +title: Remove-CsInboundBlockedNumberPattern +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: bulenteg +schema: 2.0.0 +--- + +# Remove-CsInboundBlockedNumberPattern + +## SYNOPSIS +Removes a blocked number pattern from the tenant list. + +## SYNTAX + +``` +Remove-CsInboundBlockedNumberPattern [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes a blocked number pattern from the tenant list. + +## EXAMPLES + +### Example 1 +```powershell +PS> Remove-CsInboundBlockedNumberPattern -Identity "BlockAutomatic" +``` + +This example removes a blocked number pattern identified as "BlockAutomatic". + +## PARAMETERS + +### -Identity +A unique identifier specifying the blocked number pattern to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/new-csinboundblockednumberpattern) + +[Set-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/set-csinboundblockednumberpattern) + +[Get-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/get-csinboundblockednumberpattern) diff --git a/teams/teams-ps/teams/Remove-CsInboundExemptNumberPattern.md b/teams/teams-ps/teams/Remove-CsInboundExemptNumberPattern.md new file mode 100644 index 0000000000..2abeb0572b --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsInboundExemptNumberPattern.md @@ -0,0 +1,104 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csinboundexemptnumberpattern +applicable: Microsoft Teams +title: Remove-CsInboundExemptNumberPattern +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Remove-CsInboundExemptNumberPattern + +## SYNOPSIS +Removes a number pattern exempt from call blocking. + +## SYNTAX + +``` +Remove-CsInboundExemptNumberPattern [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes a specific exempt number pattern from the tenant list for call blocking. + +## EXAMPLES + +### Example 1 +```powershell +PS>Remove-CsInboundExemptNumberPattern -Identity "Exempt1" +``` + +This removes the exempt number patterns with Identity Exempt1. + +## PARAMETERS + +### -Identity +Unique identifier for the exempt number pattern to be listed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +You can use Test-CsInboundBlockedNumberPattern to test your call block and exempt phone number ranges. + +## RELATED LINKS +[New-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/new-csinboundexemptnumberpattern) + +[Set-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/set-csinboundexemptnumberpattern) + +[Get-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/get-csinboundexemptnumberpattern) + +[Test-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/test-csinboundblockednumberpattern) + +[Get-CsTenantBlockedCallingNumbers](https://learn.microsoft.com/powershell/module/teams/get-cstenantblockedcallingnumbers) diff --git a/teams/teams-ps/teams/Remove-CsOnlineApplicationInstanceAssociation.md b/teams/teams-ps/teams/Remove-CsOnlineApplicationInstanceAssociation.md new file mode 100644 index 0000000000..1fb51dfc00 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineApplicationInstanceAssociation.md @@ -0,0 +1,91 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlineapplicationinstanceassociation +applicable: Microsoft Teams +title: Remove-CsOnlineApplicationInstanceAssociation +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsOnlineApplicationInstanceAssociation + +## SYNOPSIS +Use the Remove-CsOnlineApplicationInstanceAssociation cmdlet to remove the association between an application instance and the associated application configuration. + +## SYNTAX + +``` +Remove-CsOnlineApplicationInstanceAssociation -Identities <String[]> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +Use the Remove-CsOnlineApplicationInstanceAssociation cmdlet to remove the association between an application instance and the associated application configuration. + +This is useful when you want to associate this application instance with another application configuration for handling incoming calls. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Remove-CsOnlineApplicationInstanceAssociation -Identities "f7a821dc-2d69-5ae8-8525-bcb4a4556093" +``` + +This example removes the configuration association for the application instance that has the identity of "f7a821dc-2d69-5ae8-8525-bcb4a4556093". + +## PARAMETERS + +### -Identities +The identities for the application instances whose configuration associations are to be removed. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String[] +The Remove-CsOnlineApplicationInstanceAssociation cmdlet accepts a string array as the Identities parameter. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Online.Models.AssociationOperationOutput + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociation) + +[Get-CsOnlineApplicationInstanceAssociationStatus](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstanceassociationstatus) + +[New-CsOnlineApplicationInstanceAssociation](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstanceassociation) diff --git a/teams/teams-ps/teams/Remove-CsOnlineAudioConferencingRoutingPolicy.md b/teams/teams-ps/teams/Remove-CsOnlineAudioConferencingRoutingPolicy.md new file mode 100644 index 0000000000..b9ca408b21 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineAudioConferencingRoutingPolicy.md @@ -0,0 +1,128 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlineaudioconferencingroutingpolicy +title: Remove-CsOnlineAudioConferencingRoutingPolicy +schema: 2.0.0 +--- + +# Remove-CsOnlineAudioConferencingRoutingPolicy + +## SYNOPSIS + +This cmdlet deletes an instance of the Online Audio Conferencing Routing Policy. + +## SYNTAX + +```powershell +Remove-CsOnlineAudioConferencingRoutingPolicy [-Identity] <String> [-MsftInternalProcessingMode <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +Teams meeting dial-out calls are initiated from within a meeting in your organization to PSTN numbers, including call-me-at calls and calls to bring new participants to a meeting. + +To enable Teams meeting dial-out routing through Direct Routing to on-network users, you need to create and assign an Audio Conferencing routing policy called "OnlineAudioConferencingRoutingPolicy." + +The OnlineAudioConferencingRoutingPolicy policy is equivalent to the CsOnlineVoiceRoutingPolicy for 1:1 PSTN calls via Direct Routing. + +Audio Conferencing voice routing policies determine the available routes for calls from meeting dial-out based on the destination number. Audio Conferencing voice routing policies link to PSTN usages, determining routes for meeting dial-out calls by associated organizers. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Remove-CsOnlineAudioConferencingRoutingPolicy -Identity "Test" +``` + +Deletes an Online Audio Conferencing Routing policy instance with the identity "Test". + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsOnlineAudioConferencingRoutingPolicy](New-CsOnlineAudioConferencingRoutingPolicy.md) +[Grant-CsOnlineAudioConferencingRoutingPolicy](Grant-CsOnlineAudioConferencingRoutingPolicy.md) +[Set-CsOnlineAudioConferencingRoutingPolicy](Set-CsOnlineAudioConferencingRoutingPolicy.md) +[Get-CsOnlineAudioConferencingRoutingPolicy](Get-CsOnlineAudioConferencingRoutingPolicy.md) diff --git a/teams/teams-ps/teams/Remove-CsOnlineAudioFile.md b/teams/teams-ps/teams/Remove-CsOnlineAudioFile.md new file mode 100644 index 0000000000..61f7bace1f --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineAudioFile.md @@ -0,0 +1,76 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlineaudiofile +applicable: Microsoft Teams +title: Remove-CsOnlineAudioFile +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Remove-CsOnlineAudioFile + +## SYNOPSIS +Marks an audio file of application type TenantGlobal for deletion and later removal (within 24 hours). + +## SYNTAX + +```powershell +Remove-CsOnlineAudioFile -Identity <string> [<CommonParameters>] + +``` + +## DESCRIPTION +This cmdlet marks an audio file of application type TenantGlobal for deletion and later removal. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsOnlineAudioFile -Identity dcfcc31daa9246f29d94d0a715ef877e +``` +This cmdlet marks the audio file with Id dcfcc31daa9246f29d94d0a715ef877e for deletion and later removal. + +## PARAMETERS + +### -Identity +The Id of the specific audio file that you would like to mark for deletion. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +Please note that using this cmdlet on other application types like OrgAutoAttendant and HuntGroup does not mark the audio file for deletion. These kinds of audio files will automatically be deleted, when + +the corresponding Auto Attendant or Call Queue is deleted. + +The cmdlet is available in Teams PS module 2.4.0-preview or later. + +## RELATED LINKS + +[Export-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/export-csonlineaudiofile) + +[Get-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/get-csonlineaudiofile) + +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) diff --git a/skype/skype-ps/skype/Remove-CsOnlineDialInConferencingTenantSettings.md b/teams/teams-ps/teams/Remove-CsOnlineDialInConferencingTenantSettings.md similarity index 84% rename from skype/skype-ps/skype/Remove-CsOnlineDialInConferencingTenantSettings.md rename to teams/teams-ps/teams/Remove-CsOnlineDialInConferencingTenantSettings.md index e186ca7efa..09faa588af 100644 --- a/skype/skype-ps/skype/Remove-CsOnlineDialInConferencingTenantSettings.md +++ b/teams/teams-ps/teams/Remove-CsOnlineDialInConferencingTenantSettings.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinedialinconferencingtenantsettings -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinedialinconferencingtenantsettings +applicable: Microsoft Teams title: Remove-CsOnlineDialInConferencingTenantSettings schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsOnlineDialInConferencingTenantSettings @@ -35,7 +35,6 @@ Remove-CsOnlineDialInConferencingTenantSettings This example reverts the tenant level dial-in conferencing settings to their original defaults. - ## PARAMETERS ### -Identity @@ -44,8 +43,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: XdsIdentity Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 2 @@ -61,7 +60,7 @@ The Confirm switch causes the command to pause processing and requires confirmat Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -78,8 +77,8 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -94,8 +93,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -112,7 +111,7 @@ By using this switch, you can view what changes would occur without having to co Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -122,19 +121,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS -### -None - ## OUTPUTS -### -None - ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Remove-CsOnlineLisCivicAddress.md b/teams/teams-ps/teams/Remove-CsOnlineLisCivicAddress.md new file mode 100644 index 0000000000..e78d109481 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineLisCivicAddress.md @@ -0,0 +1,134 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlineliscivicaddress +applicable: Microsoft Teams +title: Remove-CsOnlineLisCivicAddress +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlineLisCivicAddress + +## SYNOPSIS +Use the Remove-CsOnlineLisCivicAddress cmdlet to delete an existing civic address from the Location Information Server (LIS). + +You can't remove a civic address if any of its associated locations are assigned to users or phone numbers. + +## SYNTAX + +``` +Remove-CsOnlineLisCivicAddress -CivicAddressId <guid> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Removes the specified emergency address or addresses. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsOnlineLisCivicAddress -CivicAddressId ee38d9a5-33dc-4a32-9fb8-f234cedb91ac +``` + +This example removes the emergency civic address with the specified identification. + +### Example 2 +```powershell +Get-CsOnlineLisCivicAddress -City Redmond | Remove-CsOnlineLisCivicAddress +``` + +This example removes all the emergency civic addresses in the city of Redmond. + +## PARAMETERS + +### -CivicAddressId +Specifies the unique identifier of the civic address to be deleted. +You can find civic address identifiers by using the Get-CsOnlineLisCivicAddress cmdlet. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### This cmdlet accepts pipelined input from the Get-CsOnlineLisCivicAddress cmdlet. + +## OUTPUTS + +### None + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/set-csonlineliscivicaddress) + +[New-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/new-csonlineliscivicaddress) + +[Get-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/get-csonlineliscivicaddress) diff --git a/teams/teams-ps/teams/Remove-CsOnlineLisLocation.md b/teams/teams-ps/teams/Remove-CsOnlineLisLocation.md new file mode 100644 index 0000000000..4006964361 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineLisLocation.md @@ -0,0 +1,127 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinelislocation +applicable: Microsoft Teams +title: Remove-CsOnlineLisLocation +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlineLisLocation + +## SYNOPSIS +Use the Remove-CsOnlineLisLocation cmdlet to remove an existing emergency location from the Location Information Service (LIS). + +You can only remove locations that have no assigned users or phone numbers. You can't remove the default location, you will have to delete the associated +civic address which will delete the default location. + +## SYNTAX +``` +Remove-CsOnlineLisLocation -LocationId <Guid> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +If the location specified for removal is assigned to users, the cmdlet will fail until the users assignments are removed. + +## EXAMPLES + +### Example 1 +``` +Remove-CsOnlineLisLocation -LocationId 788dd820-c136-4255-9f61-24b880ad0763 +``` + +This example removes the location specified by its identity. + +## PARAMETERS + +### -LocationId +Specifies the unique identifier of the location to be deleted. +Location identities can be discovered by using the Get-CsOnlineLisLocation cmdlet. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### This cmdlet supports pipelined input from the Get-CsOnlineLisLocation cmdlet. + +## OUTPUTS + +### None + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/set-csonlinelislocation) + +[Get-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/get-csonlinelislocation) + +[New-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/new-csonlinelislocation) diff --git a/skype/skype-ps/skype/Remove-CsOnlineLisPort.md b/teams/teams-ps/teams/Remove-CsOnlineLisPort.md similarity index 78% rename from skype/skype-ps/skype/Remove-CsOnlineLisPort.md rename to teams/teams-ps/teams/Remove-CsOnlineLisPort.md index 37afdae603..6e1665a058 100644 --- a/skype/skype-ps/skype/Remove-CsOnlineLisPort.md +++ b/teams/teams-ps/teams/Remove-CsOnlineLisPort.md @@ -1,11 +1,11 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinelisport -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinelisport +applicable: Microsoft Teams title: Remove-CsOnlineLisPort schema: 2.0.0 -author: junya -ms.author: junya +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -17,8 +17,8 @@ Removes an association between a Location port and a location. This association ## SYNTAX ``` -Remove-CsOnlineLisPort [[-TenantId] <Guid>] [-ChassisID] <String> -PortID <String> [-IsDebug <Boolean>] - [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +Remove-CsOnlineLisPort [-ChassisID] <string> -PortID <string> [-Force] [-IsDebug <bool>] [-NCSApiUrl <string>] [-TargetStore <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION @@ -28,14 +28,13 @@ Removing a port location will not remove the actual location of the port; it rem ## EXAMPLES -### -------------------------- Example 1 -------------------------- +### Example 1 ``` Remove-CsOnlineLisPort -PortID 12174 -ChassisID 0B-23-CD-16-AA-CC ``` Example 1 removes the location information for port 12174 with ChassisID 0B-23-CD-16-AA-CC. - ## PARAMETERS ### -ChassisID @@ -45,25 +44,25 @@ The Media Access Control (MAC) address of the port's switch. This value will be Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: True Position: 1 Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` -### -Confirm -Prompts you for confirmation before running the cmdlet. +### -PortID +This parameter identifies the ID of the port. ```yaml -Type: SwitchParameter +Type: String Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online +Aliases: +Applicable: Microsoft Teams -Required: False +Required: True Position: Named Default value: None Accept pipeline input: False @@ -79,7 +78,7 @@ If the Force switch isn't provided in the command, you're prompted for administr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -95,7 +94,7 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -111,7 +110,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -120,22 +119,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -PortID -This parameter identifies the ID of the port. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -TargetStore This parameter is reserved for internal Microsoft use. @@ -143,7 +126,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -152,17 +135,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -TenantId -This parameter is reserved for internal Microsoft use. +### -Confirm +Prompts you for confirmation before running the cmdlet. ```yaml -Type: Guid +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: cf +Applicable: Microsoft Teams Required: False -Position: 0 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -176,7 +159,7 @@ The cmdlet is not run. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -190,21 +173,18 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## INPUTS - -### System.Guid - - ### System.String +### System.String ## OUTPUTS - ### System.Object - ## NOTES - ## RELATED LINKS +[Set-CsOnlineLisPort](https://learn.microsoft.com/powershell/module/teams/set-csonlinelisport) + +[Get-CsOnlineLisPort](https://learn.microsoft.com/powershell/module/teams/get-csonlinelisport) diff --git a/skype/skype-ps/skype/Remove-CsOnlineLisSubnet.md b/teams/teams-ps/teams/Remove-CsOnlineLisSubnet.md similarity index 89% rename from skype/skype-ps/skype/Remove-CsOnlineLisSubnet.md rename to teams/teams-ps/teams/Remove-CsOnlineLisSubnet.md index b981a0411d..eec633e37e 100644 --- a/skype/skype-ps/skype/Remove-CsOnlineLisSubnet.md +++ b/teams/teams-ps/teams/Remove-CsOnlineLisSubnet.md @@ -1,11 +1,11 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinelissubnet -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinelissubnet +applicable: Microsoft Teams title: Remove-CsOnlineLisSubnet schema: 2.0.0 -author: junya -ms.author: junya +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -33,7 +33,6 @@ Remove-CsOnlineLisSubnet -Subnet 10.10.10.10 Example 1 removes the Location Information Service subnet "10.10.10.10". - ### -------------------------- Example 2 -------------------------- ``` Remove-CsOnlineLisSubnet -Subnet 2001:4898:e8:6c:90d2:28d4:76a4:ec5e @@ -41,7 +40,6 @@ Remove-CsOnlineLisSubnet -Subnet 2001:4898:e8:6c:90d2:28d4:76a4:ec5e Example 1 removes the Location Information Service subnet "2001:4898:e8:6c:90d2:28d4:76a4:ec5e". - ## PARAMETERS ### -Confirm @@ -51,7 +49,7 @@ Prompts you for confirmation before running the cmdlet. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -69,7 +67,7 @@ If the Force switch isn't provided in the command, you're prompted for administr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -85,7 +83,7 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -101,7 +99,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -117,7 +115,7 @@ The IP address of the subnet. This value can be either IPv4 or IPv6 format. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: 1 @@ -133,7 +131,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -149,7 +147,7 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 0 @@ -166,7 +164,7 @@ The cmdlet is not run. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -187,6 +185,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsOnlineLisSwitch.md b/teams/teams-ps/teams/Remove-CsOnlineLisSwitch.md similarity index 75% rename from skype/skype-ps/skype/Remove-CsOnlineLisSwitch.md rename to teams/teams-ps/teams/Remove-CsOnlineLisSwitch.md index 34e8ad9368..be82fd7ba5 100644 --- a/skype/skype-ps/skype/Remove-CsOnlineLisSwitch.md +++ b/teams/teams-ps/teams/Remove-CsOnlineLisSwitch.md @@ -1,11 +1,11 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csonlinelisswitch -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinelisswitch +applicable: Microsoft Teams title: Remove-CsOnlineLisSwitch schema: 2.0.0 -author: junya -ms.author: junya +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -17,8 +17,8 @@ Removes a Location Information Server (LIS) network switch. ## SYNTAX ``` -Remove-CsOnlineLisSwitch [[-TenantId] <Guid>] [-ChassisID] <String> [-IsDebug <Boolean>] - [-TargetStore <String>] [-NCSApiUrl <String>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +Remove-CsOnlineLisSwitch [-ChassisID] <string> [-Force] [-IsDebug <bool>] [-NCSApiUrl <string>] + [-TargetStore <string>] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION @@ -26,13 +26,12 @@ Enhanced 9-1-1 (E9-1-1) allows an emergency operator to identify the location of ## EXAMPLES -### -------------------------- Example 1 -------------------------- +### Example 1 ``` Remove-CsOnlineLisSwitch -ChassisID 0B-23-CD-16-AA-CC ``` -Example 1 removes the Location Information Server (LIS) switch with Chassis ID "0B-23-CD-16-AA-CC". - +Example 1 removes the switch with Chassis ID "0B-23-CD-16-AA-CC". ## PARAMETERS @@ -43,28 +42,12 @@ The Media Access Control (MAC) address of the port's switch. This value will be Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: True Position: 1 Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Skype for Business Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False +Accept pipeline input: True Accept wildcard characters: False ``` @@ -77,7 +60,7 @@ If the Force switch isn't provided in the command, you're prompted for administr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -93,7 +76,7 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -109,7 +92,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -125,7 +108,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -134,17 +117,17 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -TenantId -This parameter is reserved for internal Microsoft use. +### -Confirm +Prompts you for confirmation before running the cmdlet. ```yaml -Type: Guid +Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: cf +Applicable: Microsoft Teams Required: False -Position: 0 +Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False @@ -158,7 +141,7 @@ The cmdlet is not run. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +Applicable: Microsoft Teams Required: False Position: Named @@ -170,24 +153,20 @@ Accept wildcard characters: False ### 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/?LinkID=113216). - ## INPUTS - -### System.Guid - - ### System.String +### System.String ## OUTPUTS - ### System.Object - ## NOTES - ## RELATED LINKS +[Set-CsOnlineLisSwitch](https://learn.microsoft.com/powershell/module/teams/set-csonlinelisswitch) + +[Get-CsOnlineLisSwitch](https://learn.microsoft.com/powershell/module/teams/get-csonlinelisswitch) diff --git a/teams/teams-ps/teams/Remove-CsOnlineLisWirelessAccessPoint.md b/teams/teams-ps/teams/Remove-CsOnlineLisWirelessAccessPoint.md new file mode 100644 index 0000000000..ff2c7da4d7 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineLisWirelessAccessPoint.md @@ -0,0 +1,181 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlineliswirelessaccesspoint +applicable: Microsoft Teams +title: Remove-CsOnlineLisWirelessAccessPoint +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlineLisWirelessAccessPoint + +## SYNOPSIS +Removes a Location Information Server (LIS) wireless access point (WAP). + +## SYNTAX + +``` +Remove-CsOnlineLisWirelessAccessPoint [-BSSID] <string> [-Force] [-IsDebug <bool>] [-NCSApiUrl <string>] [-TargetStore <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet removes a WAP from the location configuration database. Removing the WAP will not remove the location associated with that WAP. Use the \`Remove-CsLisOnlineLocation\` cmdlet to remove a location. + +The BSSID (Basic Service Set Identifiers) is used to describe sections of a wireless local area network. It is the MAC of the 802.11 side of the access point. The BSSID parameter in this command also supports the wildcard format to cover all BSSIDs in a range which are sharing the same description and Location ID. The wildcard '*' can be on either the last one or two character(s). + +If a BSSID with wildcard format is already exists, the request for removing a single BSSID which is within this wildcard range and with the same location ID will not be accepted. + +## EXAMPLES + +### Example 1 +``` +Remove-CsOnlineLisWirelessAccessPoint -BSSID F0-6E-0B-C2-03-23 +``` + +Example 1 removes the Location Information Server (LIS) wireless access point with BSS ID "F0-6E-0B-C2-03-23". + +### Example 2 +``` +Remove-CsOnlineLisWirelessAccessPoint -BSSID F0-6E-0B-C2-04-* +``` + +Example 2 removes the Location Information Server (LIS) wireless access point with BSS ID "F0-6E-0B-C2-04-*". + +## PARAMETERS + +### -BSSID +The Basic Service Set Identifier (BSSID) of the wireless access point. This value must be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. It can be presented in wildcard format. The wildcard '*' can be on either the last one or two character(s). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDebug +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NCSApiUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineLisWirelessAccessPoint](https://learn.microsoft.com/powershell/module/teams/set-csonlineliswirelessaccesspoint) + +[Get-CsOnlineLisWirelessAccessPoint](https://learn.microsoft.com/powershell/module/teams/get-csonlineliswirelessaccesspoint) diff --git a/teams/teams-ps/teams/Remove-CsOnlinePSTNGateway.md b/teams/teams-ps/teams/Remove-CsOnlinePSTNGateway.md new file mode 100644 index 0000000000..6af2287599 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlinePSTNGateway.md @@ -0,0 +1,69 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinepstngateway +applicable: Microsoft Teams +title: Remove-CsOnlinePSTNGateway +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlinePSTNGateway + +## SYNOPSIS +Removes the configuration of the previously defined Session Border Controller(s) (SBC(s)) that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. + +## SYNTAX +``` +Remove-CsOnlinePSTNGateway [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to remove the configuration of the previously created Session Border Controller(s) (SBC(s)) configuration. Note the SBC must be removed from all voice routes before executing this cmdlet. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsOnlinePSTNGateway -Identity sbc.contoso.com +``` + +This example removes SBC with Identity (and FQDN) sbc.contoso.com. + +## PARAMETERS + +### -Identity +The parameter is mandatory for the cmdlet. The Identity is the same as the SBC FQDN. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: ByPropertyName +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/set-csonlinepstngateway) + +[New-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/new-csonlinepstngateway) + +[Get-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/get-csonlinepstngateway) diff --git a/teams/teams-ps/teams/Remove-CsOnlineSchedule.md b/teams/teams-ps/teams/Remove-CsOnlineSchedule.md new file mode 100644 index 0000000000..6dc49f8900 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineSchedule.md @@ -0,0 +1,86 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlineschedule +applicable: Microsoft Teams +title: Remove-CsOnlineSchedule +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsOnlineSchedule + +## SYNOPSIS +Use the Remove-CsOnlineSchedule cmdlet to remove a schedule. + +## SYNTAX +``` +Remove-CsOnlineSchedule -Id <String> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +The Remove-CsOnlineSchedule cmdlet deletes a schedule that is specified by using the Id parameter. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsOnlineSchedule -Id "fa9081d6-b4f3-5c96-baec-0b00077709e5" +``` + +This example deletes the schedule that has an Id of fa9081d6-b4f3-5c96-baec-0b00077709e5. + +## PARAMETERS + +### -Id +The Id for the schedule to be removed. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Remove-CsOnlineSchedule cmdlet accepts a string as the Id parameter. + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS + +[New-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/new-csonlineschedule) + +[Set-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/set-csonlineschedule) diff --git a/teams/teams-ps/teams/Remove-CsOnlineTelephoneNumber.md b/teams/teams-ps/teams/Remove-CsOnlineTelephoneNumber.md new file mode 100644 index 0000000000..4c26d98627 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineTelephoneNumber.md @@ -0,0 +1,137 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinetelephonenumber +applicable: Microsoft Teams +title: Remove-CsOnlineTelephoneNumber +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlineTelephoneNumber + +## SYNOPSIS +Use the `Remove-CsOnlineTelephoneNumber` cmdlet to remove one or more unassigned telephone numbers from your tenant. + +## SYNTAX + +``` +Remove-CsOnlineTelephoneNumber -TelephoneNumber <String[]> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes one or more unassigned telephone numbers from your tenant. If at least one of the telephone numbers is assigned to a user or resource account, the cmdlet will fail and will not remove any of the specified telephone numbers. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsOnlineTelephoneNumber -TelephoneNumber 14258884567 +``` +```Output +NumberIdsDeleted NumberIdsDeleteFailed NumberIdsNotOwnedByTenant NumberIdsManagedByServiceDesk +---------------- --------------------- ------------------------- ----------------------------- +{14258884567} {} {} {} +``` + +This example removes the specified telephone number from the tenant. + +### -------------------------- Example 2 -------------------------- +``` +[string[]]$tns="+14255551234","+14255551233" +Remove-CsOnlineTelephoneNumber -TelephoneNumber $tns +``` +```Output +NumberIdsDeleted NumberIdsDeleteFailed NumberIdsNotOwnedByTenant NumberIdsManagedByServiceDesk +---------------- --------------------- ------------------------- ----------------------------- +{14255551234, {} {} {} + 14255551233} +``` + +This example removes the specified list of telephone numbers from the tenant. + +## PARAMETERS + +### -TelephoneNumber +Specifies the telephone number(s) to remove. The format can be with or without the prefixed +, but needs to include country code etc. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +None + +## OUTPUTS + +### Output types +None + +## NOTES +If one or more of the telephone numbers are assigned to a user or a service, the cmdlet will display an error message and none of the telephone numbers specified will be removed from your tenant. + +## RELATED LINKS +[Get-CsOnlineTelephoneNumber](https://learn.microsoft.com/powershell/module/teams/get-csonlinetelephonenumber) diff --git a/teams/teams-ps/teams/Remove-CsOnlineVoiceRoute.md b/teams/teams-ps/teams/Remove-CsOnlineVoiceRoute.md new file mode 100644 index 0000000000..c2487ee802 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineVoiceRoute.md @@ -0,0 +1,115 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroute +applicable: Microsoft Teams +title: Remove-CsOnlineVoiceRoute +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlineVoiceRoute + +## SYNOPSIS +Removes an online voice route. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). + +## SYNTAX +``` +Remove-CsOnlineVoiceRoute [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to remove an existing online voice route. Online voice routes are associated with online voice policies through online PSTN usages, so removing an online voice route does not change any values relating to an online voice policy, it simply changes the routing for the numbers that had matched the pattern for the deleted online voice route. + +This cmdlet is used when configuring Microsoft Phone System Direct Routing. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Remove-CsOnlineVoiceRoute -Identity Route1 +``` + +Removes the settings for the online voice route with the identity Route1. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\ Get-CsOnlineVoiceRoute | Remove-CsOnlineVoiceRoute +``` + +This command removes all online voice routes from the organization. First all online voice routes are retrieved by the `Get-CsOnlineVoiceRoute` cmdlet. These online voice routes are then piped to the `Remove-CsOnlineVoiceRoute` cmdlet, which removes each one. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\ Get-CsOnlineVoiceRoute -Filter *Redmond* | Remove-CsOnlineVoiceRoute +``` + +This command removes all online voice routes with an identity that includes the string "Redmond". First the `Get-CsOnlineVoiceRoute` cmdlet is called with the Filter parameter. The value of the Filter parameter is the string Redmond surrounded by wildcard characters (\*), which specifies that the string can be anywhere within the Identity. After all of the online voice routes with identities that include the string Redmond are retrieved, these online voice routes are piped to the `Remove-CsOnlineVoiceRoute` cmdlet, which removes each one. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The unique identity of the online voice route. (If the route name contains a space, such as Test Route, you must enclose the full string in parentheses.) + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: ByPropertyName +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroute) + +[New-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroute) + +[Set-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroute) diff --git a/teams/teams-ps/teams/Remove-CsOnlineVoiceRoutingPolicy.md b/teams/teams-ps/teams/Remove-CsOnlineVoiceRoutingPolicy.md new file mode 100644 index 0000000000..a92e803b2c --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineVoiceRoutingPolicy.md @@ -0,0 +1,119 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroutingpolicy +applicable: Microsoft Teams +title: Remove-CsOnlineVoiceRoutingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlineVoiceRoutingPolicy + +## SYNOPSIS +Deletes an existing online voice routing policy. Online voice routing policies manage online PSTN usages for Phone System users. + +## SYNTAX + +### Identity +``` +Remove-CsOnlineVoiceRoutingPolicy [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. + +Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Remove-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" +``` + +The command shown in Example 1 deletes the online voice routing policy RedmondOnlineVoiceRoutingPolicy. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoutingPolicy -Filter "tag:*" | Remove-CsOnlineVoiceRoutingPolicy +``` + +In Example 2, all the online voice routing policies configured at the per-user scope are removed. To do this, the command first calls the `Get-CsOnlineVoiceRoutingPolicy` cmdlet along with the Filter parameter; the filter value "tag:\*" limits the returned data to online voice routing policies configured at the per-user scope. Those per-user policies are then piped to and removed by, the `Remove-CsOnlineVoiceRoutingPolicy` cmdlet. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> Get-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -contains "Long Distance"} | Remove-CsOnlineVoiceRoutingPolicy +``` + +In Example 3, all the online voice routing polices that include the online PSTN usage "Long Distance" are removed. To carry out this task, the `Get-CsOnlineVoiceRoutingPolicy` cmdlet is first called without any parameters in order to return a collection of all the available online voice routing policies. That collection is then piped to the Where-Object cmdlet, which picks out only those policies where the OnlinePstnUsages property includes (-contains) the usage "Long Distance". Policies that meet that criterion are then piped to the `Remove-CsOnlineVoiceRoutingPolicy`, which removes each online voice routing policy that includes the online PSTN usage "Long Distance". + +## PARAMETERS + +### -Identity +Unique identifier assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: ByPropertyName +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroutingpolicy) + +[Get-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroutingpolicy) + +[Set-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroutingpolicy) + +[Grant-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoiceroutingpolicy) diff --git a/teams/teams-ps/teams/Remove-CsOnlineVoicemailPolicy.md b/teams/teams-ps/teams/Remove-CsOnlineVoicemailPolicy.md new file mode 100644 index 0000000000..37611ecdb3 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsOnlineVoicemailPolicy.md @@ -0,0 +1,102 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoicemailpolicy +applicable: Microsoft Teams +title: Remove-CsOnlineVoicemailPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsOnlineVoicemailPolicy + +## SYNOPSIS +Deletes an existing Online Voicemail policy or resets the Global policy instance to the default values. + +## SYNTAX + +``` +Remove-CsOnlineVoicemailPolicy [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes an existing Online Voicemail policy or resets the Global policy instance to the default values. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsOnlineVoicemailPolicy -Identity "CustomOnlineVoicemailPolicy" +``` +The command shown in Example 1 deletes a per-user online voicemail policy CustomOnlineVoicemailPolicy. + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +You are not able to delete the pre-configured policy instances Default, TranscriptionProfanityMaskingEnabled and TranscriptionDisabled + +## RELATED LINKS +[Get-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoicemailpolicy) + +[Set-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailpolicy) + +[New-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoicemailpolicy) + +[Grant-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoicemailpolicy) diff --git a/teams/teams-ps/teams/Remove-CsPhoneNumberAssignment.md b/teams/teams-ps/teams/Remove-CsPhoneNumberAssignment.md new file mode 100644 index 0000000000..2bd32016e0 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsPhoneNumberAssignment.md @@ -0,0 +1,135 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment +applicable: Microsoft Teams +title: Remove-CsPhoneNumberAssignment +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Remove-CsPhoneNumberAssignment + +## SYNOPSIS +This cmdlet will remove/unassign a phone number from a user or a resource account (online application instance). + +## SYNTAX + +### RemoveSome (Default) +```powershell +Remove-CsPhoneNumberAssignment -Identity <String> -PhoneNumber <String> -PhoneNumberType <String> [<CommonParameters>] +``` + +### RemoveAll +```powershell +Remove-CsPhoneNumberAssignment -Identity <String> -RemoveAll [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes/unassigns a phone number from a user or resource account. The phone number continues to be available in the tenant. + +Unassigning a phone number from a user or resource account will automatically set EnterpriseVoiceEnabled to False. + +If the cmdlet executes successfully, no result object will be returned. If the cmdlet fails for any reason, a result object will be returned that contains a +Code string parameter and a Message string parameter with additional details of the failure. + +**Note**: In Teams PowerShell Module 4.2.1-preview and later we are changing how the cmdlet reports errors. Instead of using a result object, we will be generating an +exception in case of an error and we will be appending the exception to the $Error automatic variable. The cmdlet will also +now support the -ErrorAction parameter to control the execution after an error has occurred. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsPhoneNumberAssignment -Identity user1@contoso.com -PhoneNumber +12065551234 -PhoneNumberType CallingPlan +``` +This example removes/unassigns the Microsoft Calling Plan phone number +1 (206) 555-1234 from the user user1@contoso.com. + +### Example 2 +```powershell +Remove-CsPhoneNumberAssignment -Identity user2@contoso.com -RemoveAll +``` +This example removes/unassigns the phone number from user2@contoso.com. + +## PARAMETERS + +### -Identity +The Identity of the specific user or resource account. Can be specified using the value in the ObjectId, the SipProxyAddress, or the UserPrincipalName attribute of the user or +resource account. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhoneNumber +The phone number to unassign from the user or resource account. Supports E.164 format and non-E.164 format. Needs to be without the prefixed "tel:". + +```yaml +Type: System.String +Parameter Sets: (RemoveSome) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhoneNumberType +The type of phone number to unassign from the user or resource account. The supported values are DirectRouting, CallingPlan and OperatorConnect. + +```yaml +Type: System.String +Parameter Sets: (RemoveSome) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveAll +Unassigns the phone number from the user or resource account. + +```yaml +Type: Switch +Parameter Sets: (RemoveAll) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PowerShell module 3.0.0 or later. + +The cmdlet is only available in commercial and GCC cloud instances. + +## RELATED LINKS +[Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) + +[Get-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/get-csphonenumberassignment) diff --git a/teams/teams-ps/teams/Remove-CsPhoneNumberTag.md b/teams/teams-ps/teams/Remove-CsPhoneNumberTag.md new file mode 100644 index 0000000000..38cda0282c --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsPhoneNumberTag.md @@ -0,0 +1,82 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/remove-csphonenumbertag +applicable: Microsoft Teams +title: Remove-CsPhoneNumberTag +author: pavellatif +ms.author: pavellatif +ms.reviewer: pavellatif +manager: roykuntz +schema: 2.0.0 +--- + +# Remove-CsPhoneNumberTag + +## SYNOPSIS +This cmdlet allows admin to remove a tag from phone number. + +## SYNTAX + +``` +Remove-CsPhoneNumberTag -Tag <String> [-PhoneNumber <String>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet allows telephone number administrators to remove existing tags from any telephone numbers. This method does not delete the tag from the system if the tag is assigned to other telephone numbers. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsPhoneNumberTag -PhoneNumber +123456789 -Tag "HR" +``` + +This example shows how to remove the tag "HR" from telephone number +123456789. + +## PARAMETERS + +### -PhoneNumber +Indicates the phone number for the the tag to be removed from + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tag +Indicates the tag to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Boolean + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsSharedCallQueueHistoryTemplate.md b/teams/teams-ps/teams/Remove-CsSharedCallQueueHistoryTemplate.md new file mode 100644 index 0000000000..b50b153b93 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsSharedCallQueueHistoryTemplate.md @@ -0,0 +1,82 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsSharedCallQueueHistoryTemplate +applicable: Microsoft Teams +title: Remove-CsSharedCallQueueHistoryTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsSharedCallQueueHistoryTemplate + +## SYNTAX + +```powershell +Remove-CsSharedCallQueueHistoryTemplate -Id <String> [<CommonParameters>] +``` + +## DESCRIPTION +Use the Remove-CsSharedCallQueueHistoryTemplate cmdlet to delete a Shared Call Queue History template. If the template is currently assigned to a call queue, an error will be returned. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsSharedCallQueueHistoryTemplate -Id 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +``` + +This example deletes the Shared Call Queue History template with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no Shared Call Queue History template exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. + +## PARAMETERS + +### -Id +The Id parameter is the unique identifier assigned to the Shared Call Queue History template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[New-CsSharedCallQueueHistoryTemplate](./New-CsSharedCallQueueHistoryTemplate.md) + +[Set-CsSharedCallQueueHistoryTemplate](./Set-CsSharedCallQueueHistoryTemplate.md) + +[Get-CsSharedCallQueueHistoryTemplate](./Get-CsSharedCallQueueHistoryTemplate.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + diff --git a/teams/teams-ps/teams/Remove-CsTeamTemplate.md b/teams/teams-ps/teams/Remove-CsTeamTemplate.md new file mode 100644 index 0000000000..ee73ec6d3d --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamTemplate.md @@ -0,0 +1,273 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamtemplate +title: Remove-CsTeamTemplate +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: farahf +schema: 2.0.0 +--- + +# Remove-CsTeamTemplate + +## SYNOPSIS + +This cmdlet deletes a specified Team Template from Microsoft Teams. + +## SYNTAX + +### Delete (Default) + +```powershell +Remove-CsTeamTemplate -OdataId <String> [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### DeleteViaIdentity + +```powershell +Remove-CsTeamTemplate -InputObject <IConfigApiBasedCmdletsIdentity> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\> Remove-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/b24f8ba6-0949-452e-ad4b-a353f38ed8af/Tenant/en-US' +``` + +Removes template with OData Id '/api/teamtemplates/v1.0/b24f8ba6-0949-452e-ad4b-a353f38ed8af/Tenant/en-US'. + +### EXAMPLE 2 + +```powershell +PS C:\> (Get-CsTeamTemplateList -PublicTemplateLocale en-US) | where Name -like 'test' | ForEach-Object {Remove-CsTeamTemplate -OdataId $_.OdataId} +``` + +Removes template that meets the following specifications: 1) Locale set to en-US. 2) Name contains 'test'. + +## PARAMETERS + +### -InputObject + +Identity Parameter +To construct, see NOTES section for INPUTOBJECT properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity +Parameter Sets: DeleteViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -OdataId + +A composite URI of a template. + +```yaml +Type: System.String +Parameter Sets: Delete +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -Break + +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend + +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend + +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy + +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential + +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials + +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IAny + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorObject + +## NOTES + +ALIASES + +COMPLEX PARAMETER PROPERTIES + +To create the parameters described below, construct a hash table containing the appropriate properties. For information on hash tables, run Get-Help about_Hash_Tables. + +INPUTOBJECT \<IConfigApiBasedCmdletsIdentity\>: Identity Parameter + +- `[Bssid <String>]`: +- `[ChassisId <String>]`: +- `[CivicAddressId <String>]`: Civic address id. +- `[Country <String>]`: +- `[GroupId <String>]`: The ID of a group whose policy assignments will be returned. +- `[Id <String>]`: +- `[Identity <String>]`: +- `[Locale <String>]`: +- `[LocationId <String>]`: Location id. +- `[OdataId <String>]`: A composite URI of a template. +- `[OperationId <String>]`: The ID of a batch policy assignment operation. +- `[OrderId <String>]`: +- `[PackageName <String>]`: The name of a specific policy package +- `[PolicyType <String>]`: The policy type for which group policy assignments will be returned. +- `[Port <String>]`: +- `[PortInOrderId <String>]`: +- `[PublicTemplateLocale <String>]`: Language and country code for localization of publicly available templates. +- `[SubnetId <String>]`: +- `[TenantId <String>]`: +- `[UserId <String>]`: UserId. Supports Guid. Eventually UPN and SIP. + +## RELATED LINKS + +[Get-CsTeamTemplateList](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) + +[Get-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplate) + +[New-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamtemplate) + +[Update-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/update-csteamtemplate) + +[Remove-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/remove-csteamtemplate) diff --git a/teams/teams-ps/teams/Remove-CsTeamsAIPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsAIPolicy.md new file mode 100644 index 0000000000..01ddbc1bcc --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsAIPolicy.md @@ -0,0 +1,73 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Remove-CsTeamsAIPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsTeamsAIPolicy +schema: 2.0.0 +author: Andy447 +ms.author: andywang +--- + +# Remove-CsTeamsAIPolicy + +## SYNOPSIS + +This cmdlet deletes a Teams AI policy. + +## SYNTAX + +``` +Remove-CsTeamsAIPolicy -Identity <String> [<CommonParameters>] +``` + +## DESCRIPTION + +The new csTeamsAIPolicy will replace the existing enrollment settings in csTeamsMeetingPolicy, providing enhanced flexibility and control for Teams meeting administrators. Unlike the current single setting, EnrollUserOverride, which applies to both face and voice enrollment, the new policy introduces two distinct settings: EnrollFace and EnrollVoice. These can be individually set to Enabled or Disabled, offering more granular control over biometric enrollments. A new setting, SpeakerAttributionBYOD, is also being added to csTeamsAIPolicy. This allows IT admins to turn off speaker attribution in BYOD scenarios, giving them greater control over how voice data is managed in such environments. This setting can be set to Enabled or Disabled, and will be Enabled by default. In addition to improving the management of face and voice data, the csTeamsAIPolicy is designed to support future AI-related settings in Teams, making it a scalable solution for evolving needs. + +This cmdlet deletes a Teams AI policy with the specified identity string. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsAIPolicy -Identity "Test" +``` + +Deletes a Teams AI policy with the identify of "Test". + +## PARAMETERS + +### -Identity +Identity of the Teams AI policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsaipolicy) + +[Get-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaipolicy) + +[Grant-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaipolicy) + +[Set-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsAppPermissionPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsAppPermissionPolicy.md new file mode 100644 index 0000000000..409570c300 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsAppPermissionPolicy.md @@ -0,0 +1,146 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsapppermissionpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsAppPermissionPolicy +schema: 2.0.0 +ms.reviewer: mhayrapetyan +manager: prkosh +ms.author: prkosh +author: ashishguptaiitb +--- + +# Remove-CsTeamsAppPermissionPolicy + +## SYNOPSIS + +**NOTE**: You can use this cmdlet to remove a specific custom policy from a user. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. This cmdlet is not supported for tenants that migrated to app centric management feature as it replaced permission policies. While the cmdlet may succeed, the changes aren't applied to the tenant. + +As an admin, you can use app permission policies to allow or block apps for your users. Learn more about the app permission policies at <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies> and about app centric management at <https://learn.microsoft.com/microsoftteams/app-centric-management>. + +This cmdlet allows you to remove app permission policies that have been created within your organization. If you run `Remove-CsTeamsAppPermissionPolicy` on the Global policy, it will be reset to the defaults provided for new organizations. + +**This is only applicable for tenants who have not been migrated to ACM or UAM.** + +## SYNTAX + +``` +Remove-CsTeamsAppSetupPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: You can use this cmdlet to remove a specific custom policy from a user. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Permission Policies: <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies>. + +This cmdlet allows you to remove app permission policies that have been created within your organization. If you run Remove-CsTeamsAppPermissionPolicy on the Global policy, it will be reset to the defaults provided for new organizations. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsAppPermissionPolicy -Identity SalesPolicy +``` + +Deletes a custom policy that has already been created in the organization. + +## PARAMETERS + +### -Identity +Unique identifier for the policy to be removed. +To "remove" the global policy, use the following syntax: `-Identity global`. +(Note that the global policy cannot actually be removed. Instead, all the properties in that policy will be reset to their default values.) To remove a per-user policy, use syntax similar to this: `-Identity "SalesDepartmentPolicy"`. +You cannot use wildcards when specifying a policy Identity. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 2 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Force +Suppresses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsAppSetupPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsAppSetupPolicy.md new file mode 100644 index 0000000000..fa290e6383 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsAppSetupPolicy.md @@ -0,0 +1,147 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsappsetuppolicy +applicable: Microsoft Teams +title: Remove-CsTeamsAppSetupPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsTeamsAppSetupPolicy + +## SYNOPSIS +**NOTE**: You can use this cmdlet to remove custom app setup policies. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +If you run Remove-CsTeamsAppSetupPolicy on the Global policy, it will be reset to the defaults provided for new organizations. + +## SYNTAX + +``` +Remove-CsTeamsAppSetupPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: You can use this cmdlet to remove custom app setup policies. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +If you run Remove-CsTeamsAppSetupPolicy on the Global policy, it will be reset to the defaults provided for new organizations. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsAppSetupPolicy -Identity SalesPolicy +``` + +Deletes a custom policy that has already been created in the organization. + +## PARAMETERS + +### -Identity +Unique identifier for the policy to be removed. +To "remove" the global policy, use the following syntax: `-Identity global`. +(Note that the global policy cannot actually be removed. Instead, all the properties in that policy will be reset to their default values.) To remove a per-user policy, use syntax similar to this: `-Identity "SalesDepartmentPolicy"`. +You cannot use wildcards when specifying a policy Identity. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 2 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Force +Suppresses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsAudioConferencingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsAudioConferencingPolicy.md new file mode 100644 index 0000000000..5866a31e39 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsAudioConferencingPolicy.md @@ -0,0 +1,114 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsaudioconferencingpolicy +title: Remove-CsTeamsAudioConferencingPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsAudioConferencingPolicy + +## SYNOPSIS + +Deletes a custom Teams audio conferencing policy. Audio conferencing policies are used to manage audio conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. + +## SYNTAX + +``` +Remove-CsTeamsAudioConferencingPolicy [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes a previously created TeamsAudioConferencingPolicy. Any users with no explicitly assigned policies will then fall back to the default (Global) policy in the organization. You cannot delete the global policy from the organization. + +## EXAMPLES + +### EXAMPLE 1 +``` +PS C:\> Remove-CsTeamsAudioCOnferencingPolicy -Identity "Emea Users" +``` + +In the example shown above, the command will delete the "Emea Users" audio conferencing policy from the organization's list of policies. + +## PARAMETERS + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the TeamsAudioConferencingPolicy to be removed. To remove global policy, use this syntax: -Identity global. (Note that the global policy cannot be removed. Instead, all the policy properties will be reset to their default values.) To remove a custom policy, use this syntax: `-Identity "<policy name>"`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### String +## OUTPUTS + +### Object +## NOTES + +## RELATED LINKS + +[Get-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaudioconferencingpolicy) + +[Set-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsaudioconferencingpolicy) + +[Grant-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaudioconferencingpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsCallHoldPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsCallHoldPolicy.md new file mode 100644 index 0000000000..e735cc0dc3 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsCallHoldPolicy.md @@ -0,0 +1,131 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamscallholdpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsCallHoldPolicy +schema: 2.0.0 +ms.reviewer: +manager: abnair +ms.author: serdars +author: serdarsoysal +--- + +# Remove-CsTeamsCallHoldPolicy + +## SYNOPSIS + +Deletes an existing Teams call hold policy in your tenant. The Teams call hold policy is used to customize the call hold experience for Teams clients. + +## SYNTAX + +``` +Remove-CsTeamsCallHoldPolicy [-Identity] <string> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Teams call hold policies are used to customize the call hold experience for teams clients. +When Microsoft Teams users participate in calls, they have the ability to hold a call and have the other entity in the call listen to an audio file during the duration of the hold. + +Assigning a Teams call hold policy to a user sets an audio file to be played during the duration of the hold. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Remove-CsTeamsCallHoldPolicy -Identity 'ContosoPartnerTeamsCallHoldPolicy' +``` + +The command shown in Example 1 deletes the Teams call hold policy ContosoPartnerTeamsCallHoldPolicy. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsCallHoldPolicy -Filter 'Tag:*' | Remove-CsTeamsCallHoldPolicy +``` + +In Example 2, all the Teams call hold policies configured at the per-user scope are removed. +The Filter value "Tag:*" limits the returned data to Teams call hold policies configured at the per-user scope. Those per-user policies are then removed. + +## PARAMETERS + +### -Identity +Unique identifier of the Teams call hold policy to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallholdpolicy) + +[Get-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallholdpolicy) + +[Set-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallholdpolicy) + +[Grant-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallholdpolicy) diff --git a/skype/skype-ps/skype/Remove-CsTeamsCallParkPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsCallParkPolicy.md similarity index 87% rename from skype/skype-ps/skype/Remove-CsTeamsCallParkPolicy.md rename to teams/teams-ps/teams/Remove-CsTeamsCallParkPolicy.md index ef22398bb0..8504928e7c 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsCallParkPolicy.md +++ b/teams/teams-ps/teams/Remove-CsTeamsCallParkPolicy.md @@ -1,16 +1,15 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamscallparkpolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamscallparkpolicy +applicable: Microsoft Teams title: Remove-CsTeamsCallParkPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- - # Remove-CsTeamsCallParkPolicy ## SYNOPSIS @@ -49,8 +48,8 @@ You cannot use wildcards when specifying a policy Identity. ```yaml Type: XdsIdentity Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: True Position: 2 @@ -65,8 +64,8 @@ Suppresses all non-fatal errors. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -82,7 +81,7 @@ Describes what would happen if you executed the command without actually executi Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -98,7 +97,7 @@ Prompts you for confirmation before executing the command. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -113,8 +112,8 @@ Internal Microsoft use only. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -124,14 +123,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### Microsoft.Rtc.Management.Xds.XdsIdentity - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Remove-CsTeamsCallingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsCallingPolicy.md new file mode 100644 index 0000000000..f22acb63d5 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsCallingPolicy.md @@ -0,0 +1,109 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamscallingpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsCallingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: +schema: 2.0.0 +--- + +# Remove-CsTeamsCallingPolicy + +## SYNOPSIS + +## SYNTAX + +``` +Remove-CsTeamsCallingPolicy [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + This cmdlet removes an existing Teams Calling Policy instance or resets the Global policy instance to the default values. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsCallingPolicy -Identity Sales +``` + +This example removes the Teams Calling Policy with identity Sales + +### Example 2 +```powershell +PS C:\> Remove-CsTeamsCallingPolicy -Identity Global +``` + +This example resets the Global Policy instance to the default values. + +## PARAMETERS + +### -Identity + The Identity parameter is the unique identifier of the Teams Calling Policy instance to remove or reset. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscallingpolicy) + +[Get-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallingpolicy) + +[Grant-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallingpolicy) + +[New-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallingpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsChannelsPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsChannelsPolicy.md new file mode 100644 index 0000000000..1adb7d3231 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsChannelsPolicy.md @@ -0,0 +1,139 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamschannelspolicy +applicable: Microsoft Teams +title: Remove-CsTeamsChannelsPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsTeamsChannelsPolicy + +## SYNOPSIS + +The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. + +## SYNTAX + +``` +Remove-CsTeamsChannelsPolicy [-Identity] <XdsIdentity> [-Confirm] [-Force] [-Tenant <Guid>] [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. The Remove-CsTeamsChannelsPolicy cmdlet lets you delete a custom policy that has been configured in your organization. + +If you run Remove-CsTeamsChannelsPolicy on the Global policy, it will be reset to the defaults provided for new organizations. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsChannelsPolicy -Identity SalesPolicy +``` + +Deletes a custom policy that has already been created in the organization. + +## PARAMETERS + +### -Identity +The name of the policy to be removed. Wildcards are not supported. + +To remove a custom policy, use syntax similar to this: `-Identity "Student Policy"`. + +To "remove" the global policy, use the following syntax: `-Identity Global`. You can't actually remove the global policy. Instead, all properties will be reset to their default values as shown in the default policy (`Tag:Default`). + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 2 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingApplication.md b/teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingApplication.md similarity index 78% rename from skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingApplication.md rename to teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingApplication.md index 115ac36f6b..05cb425285 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingApplication.md +++ b/teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingApplication.md @@ -1,178 +1,180 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication -applicable: Skype for Business Online -title: Remove-CsTeamsComplianceRecordingApplication -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# Remove-CsTeamsComplianceRecordingApplication - -## SYNOPSIS -Deletes an existing association between an application instance of a policy-based recording application and a Teams recording policy for administering automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -``` -Remove-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Policy-based recording applications are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. - -Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. - -Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. -Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -``` - -The command shown in Example 1 deletes an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -### Example 2 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingApplication | Remove-CsTeamsComplianceRecordingApplication -``` - -The command shown in Example 2 deletes all existing associations between application instances of policy-based recording applications and their corresponding Teams compliance recording policy. - -## PARAMETERS - -### -Identity -A name that uniquely identifies the application instance of the policy-based recording application. - -Application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -To do this association correctly, the Identity of these application instances must be \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams compliance recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication +applicable: Microsoft Teams +title: Remove-CsTeamsComplianceRecordingApplication +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# Remove-CsTeamsComplianceRecordingApplication + +## SYNOPSIS +Deletes an existing association between an application instance of a policy-based recording application and a Teams recording policy for administering automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +``` +Remove-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Policy-based recording applications are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. + +Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. + +Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. +Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' +``` + +The command shown in Example 1 deletes an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingApplication | Remove-CsTeamsComplianceRecordingApplication +``` + +The command shown in Example 2 deletes all existing associations between application instances of policy-based recording applications and their corresponding Teams compliance recording policy. + +## PARAMETERS + +### -Identity +A name that uniquely identifies the application instance of the policy-based recording application. + +Application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +To do this association correctly, the Identity of these application instances must be \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams compliance recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingPolicy.md similarity index 75% rename from skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingPolicy.md rename to teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingPolicy.md index c32c81e682..c121ab2692 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingPolicy.md +++ b/teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingPolicy.md @@ -1,177 +1,179 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy -applicable: Skype for Business Online -title: Remove-CsTeamsComplianceRecordingPolicy -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# Remove-CsTeamsComplianceRecordingPolicy - -## SYNOPSIS -Deletes an existing Teams recording policy that is used to govern automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -``` -Remove-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Teams recording policies are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. - -Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. -Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. - -Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. -The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. -Existing calls and meetings are unaffected. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -``` - -The command shown in Example 1 deletes the Teams recording policy ContosoPartnerComplianceRecordingPolicy. - -### Example 2 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingPolicy -Filter 'Tag:*' | Remove-CsTeamsComplianceRecordingPolicy -``` - -In Example 2, all the Teams recording policies configured at the per-user scope are removed. -The Filter value "Tag:*" limits the returned data to Teams recording policies configured at the per-user scope. Those per-user policies are then removed. - -## PARAMETERS - -### -Identity -Unique identifier to be assigned to the new Teams recording policy. - -Use the "Global" Identity if you wish to assign this policy to the entire tenant. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsComplianceRecordingPolicy +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# Remove-CsTeamsComplianceRecordingPolicy + +## SYNOPSIS +Deletes an existing Teams recording policy that is used to govern automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +``` +Remove-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Teams recording policies are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. + +Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. +Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. + +Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. +The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. +Existing calls and meetings are unaffected. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' +``` + +The command shown in Example 1 deletes the Teams recording policy ContosoPartnerComplianceRecordingPolicy. + +### Example 2 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingPolicy -Filter 'Tag:*' | Remove-CsTeamsComplianceRecordingPolicy +``` + +In Example 2, all the Teams recording policies configured at the per-user scope are removed. +The Filter value "Tag:*" limits the returned data to Teams recording policies configured at the per-user scope. Those per-user policies are then removed. + +## PARAMETERS + +### -Identity +Unique identifier to be assigned to the new Teams recording policy. + +Use the "Global" Identity if you wish to assign this policy to the entire tenant. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/teams/teams-ps/teams/Remove-CsTeamsCortanaPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsCortanaPolicy.md new file mode 100644 index 0000000000..bac8a3df1d --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsCortanaPolicy.md @@ -0,0 +1,132 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscortanapolicy +applicable: Microsoft Teams +title: Remove-CsTeamsCortanaPolicy +schema: 2.0.0 +manager: amehta +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsTeamsCortanaPolicy + +## SYNOPSIS +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. + +## SYNTAX + +``` +Remove-CsTeamsCortanaPolicy [-Tenant <System.Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Deletes a previously created TeamsCortanaPolicy. Any users with no explicitly assigned policies will then fall back to the default policy in the organization. You cannot delete the global policy from the organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsCortanaPolicy -Identity MyCortanaPolicy +``` + +In the example shown above, the command will delete the MyCortanaPolicy from the organization's list of policies. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Identity for the policy you're modifying. To modify the global policy, use this syntax: -Identity global. To modify a per-user policy, use syntax similar to this: -Identity MyCortanaPolicy. +If you do not specify an Identity the Set-CsTeamsCortanaPolicy cmdlet will automatically modify the global policy. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" +You can return your tenant ID by running this command: +Get-CsTenant | Select-Object DisplayName, TenantID + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsCustomBannerText b/teams/teams-ps/teams/Remove-CsTeamsCustomBannerText new file mode 100644 index 0000000000..9e9dcd1434 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsCustomBannerText @@ -0,0 +1,71 @@ +--- +Module Name: MicrosoftTeams +title: Remove-CsTeamsCustomBannerText +author: saleens7 +ms.author: wblocker +online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsTeamsCustomBannerText +schema: 2.0.0 +--- + +# Remove-CsTeamsCustomBannerText + +## SYNOPSIS + +Enables administrators to configure a custom text on the banner displayed when compliance recording bots start recording the call. + +## SYNTAX + +### Identity (Default) +``` +Remove-CsTeamsCustomBannerText [[-Identity] <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +Removes a single instance of custom banner text. + +## EXAMPLES + +### Example 1 +PS C:\> Remove-CsTeamsCustomBannerText -Identity CustomText +``` + +Removes a TeamsCustomBannerText instance with the name "CustomText". + +## PARAMETERS + +### -Identity +Policy instance name (optional). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/set-csteamscustombannertext) + +[New-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext) + +[Remove-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/remove-csteamscustombannertext) diff --git a/teams/teams-ps/teams/Remove-CsTeamsCustomBannerText.md b/teams/teams-ps/teams/Remove-CsTeamsCustomBannerText.md new file mode 100644 index 0000000000..8619d8cca2 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsCustomBannerText.md @@ -0,0 +1,71 @@ +--- +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsTeamsCustomBannerText +title: Remove-CsTeamsCustomBannerText +schema: 2.0.0 +author: saleens7 +ms.author: wblocker +--- + +# Remove-CsTeamsCustomBannerText + +## SYNOPSIS + +Enables administrators to remove a custom banner text configuration that is displayed when compliance recording bots start recording the call. + +## SYNTAX + +### Identity (Default) +``` +Remove-CsTeamsCustomBannerText [[-Identity] <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +Removes a single instance of custom banner text. + +## EXAMPLES + +### Example 1 +PS C:\> Remove-CsTeamsCustomBannerText -Identity CustomText +``` + +This example removes a TeamsCustomBannerText instance with the name "CustomText". + +## PARAMETERS + +### -Identity +Policy instance name (optional). + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/set-csteamscustombannertext) + +[New-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext) + +[Remove-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/remove-csteamscustombannertext) diff --git a/teams/teams-ps/teams/Remove-CsTeamsEmergencyCallRoutingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsEmergencyCallRoutingPolicy.md new file mode 100644 index 0000000000..09e839d382 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsEmergencyCallRoutingPolicy.md @@ -0,0 +1,108 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallroutingpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsEmergencyCallRoutingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc +schema: 2.0.0 +--- + +# Remove-CsTeamsEmergencyCallRoutingPolicy + +## SYNOPSIS +This cmdlet removes an existing Teams Emergency Call Routing policy instance. + +## SYNTAX + +``` +Remove-CsTeamsEmergencyCallRoutingPolicy [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes an existing Teams Emergency Call Routing policy instance. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsTeamsEmergencyCallRoutingPolicy -Identity Test +``` + +This example removes Teams Emergency Call Routing policy with identity Test. + +### Example 2 +```powershell +Remove-CsTeamsEmergencyCallRoutingPolicy -Identity Global +``` + +This example resets the Teams Emergency Call Routing Global policy instance to its default values. + +## PARAMETERS + +### -Identity +The Identity parameter is the unique identifier of the Teams Emergency Call Routing policy to remove. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallroutingpolicy) + +[Grant-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallroutingpolicy) + +[Set-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallroutingpolicy) + +[Get-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallroutingpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsEmergencyCallingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsEmergencyCallingPolicy.md new file mode 100644 index 0000000000..0f35301904 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsEmergencyCallingPolicy.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallingpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsEmergencyCallingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc +schema: 2.0.0 +--- + +# Remove-CsTeamsEmergencyCallingPolicy + +## SYNOPSIS + +## SYNTAX + +``` +Remove-CsTeamsEmergencyCallingPolicy [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes an existing Teams Emergency Calling policy. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsTeamsEmergencyCallingPolicy -Identity testECP +``` + +This example removes an existing Teams Emergency Calling policy with identity testECP. + +### Example 2 +```powershell +Remove-CsTeamsEmergencyCallingPolicy -Identity Global +``` + +This example resets the Global Policy instance to the default values. + +## PARAMETERS + +### -Identity + The Identity parameter is the unique identifier of the Teams Emergency Calling policy to remove. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingpolicy) + +[Grant-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallingpolicy) + +[Get-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallingpolicy) + +[Set-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallingpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsEnhancedEncryptionPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsEnhancedEncryptionPolicy.md new file mode 100644 index 0000000000..2e310c4d61 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsEnhancedEncryptionPolicy.md @@ -0,0 +1,128 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsenhancedencryptionpolicy +title: Remove-CsTeamsEnhancedEncryptionPolicy +author: serdarsoysal +ms.author: serdars +manager: mdress +schema: 2.0.0 +--- + +# Remove-CsTeamsEnhancedEncryptionPolicy + +## SYNOPSIS +Use this cmdlet to remove an existing Teams enhanced encryption policy. + +## SYNTAX + +``` +Remove-CsTeamsEnhancedEncryptionPolicy [[-Identity] <Object>] [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to remove an existing Teams enhanced encryption policy. + +The TeamsEnhancedEncryptionPolicy enables administrators to determine which users in your organization can use the enhanced encryption settings in Teams, setting for End-to-end encryption in ad-hoc 1-to-1 VOIP calls is the parameter supported by this policy currently. + +## EXAMPLES + +### EXAMPLE 1 +```PowerShell +PS C:\> Remove-CsTeamsEnhancedEncryptionPolicy -Identity 'ContosoPartnerTeamsEnhancedEncryptionPolicy' +``` + +The command shown in Example 1 deletes the Teams enhanced encryption policy ContosoPartnerTeamsEnhancedEncryptionPolicy. + +### EXAMPLE 2 +```PowerShell +PS C:\> Get-CsTeamsEnhancedEncryptionPolicy -Filter 'Tag:*' | Remove-CsTeamsEnhancedEncryptionPolicy +``` + +In Example 2, all the Teams enhanced encryption policies configured at the per-user scope are removed. The Filter value "Tag:*" limits the returned data to Teams enhanced encryption policies configured at the per-user scope. Those per-user policies are then removed. + +## PARAMETERS + +### -Identity +Unique identifier assigned to the Teams enhanced encryption policy. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Force +Suppresses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Object +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsenhancedencryptionpolicy) + +[New-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsenhancedencryptionpolicy) + +[Set-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsenhancedencryptionpolicy) + +[Grant-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsenhancedencryptionpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsEventsPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsEventsPolicy.md new file mode 100644 index 0000000000..adc94c0242 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsEventsPolicy.md @@ -0,0 +1,94 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamseventspolicy +title: Remove-CsTeamsEventsPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsEventsPolicy + +## SYNOPSIS +The CsTeamsEventsPolicy cmdlets removes a previously created TeamsEventsPolicy. Note that this policy is currently still in preview. + +## SYNTAX + +``` +Remove-CsTeamsEventsPolicy [-Identity] <String> [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Deletes a previously created TeamsEventsPolicy. Any users with no explicitly assigned policies will then fall back to the default policy in the organization. You cannot delete the global policy from the organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsEventsPolicy -Identity DisablePublicWebinars +``` + +In this example, the command will delete the DisablePublicWebinars policy from the organization's list of policies. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the teams events policy to be removed. To remove the global policy, use this syntax: -Identity Global. (Note that the global policy cannot actually be removed. Instead, all the policy properties will be reset to their default values.) To remove a custom policy DisablePublicWebinars, use this syntax: -Identity DisablePublicWebinars. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsFeedbackPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsFeedbackPolicy.md new file mode 100644 index 0000000000..c001e0e880 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsFeedbackPolicy.md @@ -0,0 +1,133 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsfeedbackpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsFeedbackPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: +--- + +# Remove-CsTeamsFeedbackPolicy + +## SYNOPSIS + +Use this cmdlet to remove a Teams Feedback policy from the Tenant. + +## SYNTAX + +``` +Remove-CsTeamsFeedbackPolicy [[-Identity] <String>] + [-Confirm] + [-Force] + [-Tenant <Object>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Removes a Teams Feedback policy from the Tenant. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsFeedbackPolicy -Identity "New Hire Feedback Policy" +``` + +In this example, the policy "New Hire Feedback Policy" is being removed. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The identity of the policy to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsFilesPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsFilesPolicy.md new file mode 100644 index 0000000000..8b2f609c8e --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsFilesPolicy.md @@ -0,0 +1,68 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsfilespolicy +title: Remove-CsTeamsFilesPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsFilesPolicy + +## SYNOPSIS +Deletes an existing teams files policy or resets the Global policy instance to the default values. + +## SYNTAX + +``` +Remove-CsTeamsFilesPolicy [-Identity] <String> [<CommonParameters>] +``` + +## DESCRIPTION +Deletes an existing teams files or resets the Global policy instance to the default values. + +## EXAMPLES + +### Example 1 +``` +Remove-CsTeamsFilesPolicy -Identity "Customteamsfilespolicy" +``` + +The command shown in Example 1 deletes a per-user teams files policy Customteamsfilespolicy. + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +You are not able to delete the pre-configured policy instances Default, TranscriptionProfanityMaskingEnabled and TranscriptionDisabled + +## RELATED LINKS + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsfilespolicy) + diff --git a/teams/teams-ps/teams/Remove-CsTeamsIPPhonePolicy.md b/teams/teams-ps/teams/Remove-CsTeamsIPPhonePolicy.md new file mode 100644 index 0000000000..f31fdeafd5 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsIPPhonePolicy.md @@ -0,0 +1,135 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsipphonepolicy +applicable: Microsoft Teams +title: Remove-CsTeamsIPPhonePolicy +author: tonywoodruff +ms.author: anwoodru +ms.reviewer: kponnus +manager: sandrao +schema: 2.0.0 +--- + +# Remove-CsTeamsIPPhonePolicy + +## SYNOPSIS + +Use the Remove-CsTeamsIPPhonePolicy cmdlet to remove a custom policy that's been created for controlling Teams phone experiences. + +## SYNTAX + +``` +Remove-CsTeamsIPPhonePolicy [[-Identity] <XdsIdentity>] + [-Confirm] + [-Force] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Use the Remove-CsTeamsIPPhonePolicy cmdlet to remove a custom policy that's been created for controlling Teams IP Phones experiences. + +Note: Ensure the policy is not assigned to any users or the policy deletion will fail. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsIPPhonePolicy -Identity CommonAreaPhone +``` +This example shows the deletion of the policy CommonAreaPhone. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the TeamsIPPhonePolicy that you would like to remove. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsMediaConnectivityPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsMediaConnectivityPolicy.md new file mode 100644 index 0000000000..a2b3b79a34 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsMediaConnectivityPolicy.md @@ -0,0 +1,69 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Remove-CsTeamsMediaConnectivityPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsTeamsMediaConnectivityPolicy +schema: 2.0.0 +author: lirunping-MSFT +ms.author: runli +--- + +# Remove-CsTeamsMediaConnectivityPolicy + +## SYNOPSIS + +This cmdlet deletes a Teams media connectivity policy. + +## SYNTAX + +``` +Remove-CsTeamsMediaConnectivityPolicy -Identity <String> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet deletes a Teams media connectivity policy with the specified identity string. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsMediaConnectivityPolicy -Identity "Test" +``` + +Deletes a Teams media connectivity policy with the identify of "Test". + +## PARAMETERS + +### -Identity +Identity of the Teams media connectivity policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmediaconnectivitypolicy) + +[Get-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmediaconnectivitypolicy) + +[Set-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmediaconnectivitypolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsMeetingBrandingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsMeetingBrandingPolicy.md new file mode 100644 index 0000000000..ac3f34c82e --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsMeetingBrandingPolicy.md @@ -0,0 +1,118 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingbrandingpolicy +schema: 2.0.0 +title: Remove-CsTeamsMeetingBrandingPolicy +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: stanlythomas +--- + +# Remove-CsTeamsMeetingBrandingPolicy + +## SYNOPSIS +The **CsTeamsMeetingBrandingPolicy** cmdlet enables administrators to control the appearance in meetings by defining custom backgrounds, logos, and colors. + +## SYNTAX + +``` +Remove-CsTeamsMeetingBrandingPolicy [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes a previously created TeamsMeetingBrandingPolicy. Any users with no explicitly assigned policies will then fall back to the default policy in the organization. You cannot delete the global policy from the organization. If you want to remove policies currently assigned to one or more users, you should first assign a different policy to them. + +## EXAMPLES + +### Remove meeting branding policy +```powershell +PS C:\> Remove-CsTeamsMeetingBrandingPolicy -Identity "policy test" +``` + +In this example, the command deletes the `policy test` meeting branding policy from the organization's list of meeting branding policies and removes all assignments of this policy from users who have the policy assigned. + +## PARAMETERS + +### -Identity +Unique identifier of the policy to be deleted. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +Available in Teams PowerShell Module 4.9.3 and later. + +## RELATED LINKS + +[Get-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbrandingpolicy) + +[Grant-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingbrandingpolicy) + +[New-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingbrandingpolicy) + +[Remove-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingbrandingpolicy) + +[Set-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbrandingpolicy) diff --git a/skype/skype-ps/skype/Remove-CsTeamsMeetingBroadcastPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsMeetingBroadcastPolicy.md similarity index 88% rename from skype/skype-ps/skype/Remove-CsTeamsMeetingBroadcastPolicy.md rename to teams/teams-ps/teams/Remove-CsTeamsMeetingBroadcastPolicy.md index 2f34dc8a42..3b8ee0ebd4 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsMeetingBroadcastPolicy.md +++ b/teams/teams-ps/teams/Remove-CsTeamsMeetingBroadcastPolicy.md @@ -1,16 +1,15 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsmeetingbroadcastpolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingbroadcastpolicy +applicable: Microsoft Teams title: Remove-CsTeamsMeetingBroadcastPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- - # Remove-CsTeamsMeetingBroadcastPolicy ## SYNOPSIS @@ -28,7 +27,6 @@ User-level policy for tenant admin to configure meeting broadcast behavior for t ## EXAMPLES - ## PARAMETERS ### -Confirm @@ -62,7 +60,7 @@ Accept wildcard characters: False ``` ### -Identity -Unique identifier for the policy to be removed. Policies can be configured at the global or per-user scopes. To remove the global policy, use this syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the policy properties will be reset to their default values.) +Unique identifier for the policy to be removed. Policies can be configured at the global or per-user scopes. To remove the global policy, use this syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the policy properties will be reset to their default values.) To remove a per-user policy, use syntax similar to this: -Identity SalesPolicy. @@ -112,8 +110,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -121,6 +118,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/skype/skype-ps/skype/Remove-CsTeamsMeetingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsMeetingPolicy.md similarity index 87% rename from skype/skype-ps/skype/Remove-CsTeamsMeetingPolicy.md rename to teams/teams-ps/teams/Remove-CsTeamsMeetingPolicy.md index ec3abb2b98..afc4b6bca6 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsMeetingPolicy.md +++ b/teams/teams-ps/teams/Remove-CsTeamsMeetingPolicy.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsmeetingpolicy -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingpolicy +applicable: Microsoft Teams title: Remove-CsTeamsMeetingPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsTeamsMeetingPolicy @@ -120,11 +120,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### 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/?LinkID=113216). + ## INPUTS ### Microsoft.Rtc.Management.Xds.XdsIdentity - ## OUTPUTS ### System.Object @@ -132,4 +134,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Remove-CsTeamsMeetingTemplatePermissionPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsMeetingTemplatePermissionPolicy.md new file mode 100644 index 0000000000..b813ff072b --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsMeetingTemplatePermissionPolicy.md @@ -0,0 +1,87 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +title: Remove-CsTeamsMeetingTemplatePermissionPolicy +author: boboPD +ms.author: pradas +online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsTeamsMeetingTemplatePermissionPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsMeetingTemplatePermissionPolicy + +## SYNOPSIS +Deletes an instance of TeamsMeetingTemplatePermissionPolicy. + +## SYNTAX + +```powershell +Remove-CsTeamsMeetingTemplatePermissionPolicy [-Identity] <string> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes an instance of TeamsMeetingTemplatePermissionPolicy. The `Identity` parameter accepts the identity of the policy instance to delete. + +## EXAMPLES + +### Example 1 - Deleting a meeting template permission policy + +```powershell +Remove-CsTeamsMeetingTemplatePermissionPolicy -Identity Test_Policy +``` + +Deletes a policy instance with the Identity *Test_Policy*. + +### Example 2 - Deleting a policy when its assigned to a user + +Attempting to delete a policy instance that is currently assigned to users will result in an error. Remove the assignment before attempting to delete it. + +```powershell +Remove-CsTeamsMeetingTemplatePermissionPolicy -Identity Foobar +``` + +```output +Remove-CsTeamsMeetingTemplatePermissionPolicy : The policy "Foobar" is currently assigned to one or more users. Assign a different policy to the users before removing +this one. Please refer to documentation. CorrelationId: 8698472b-f441-423b-8ee3-0469c7e07528 +At line:1 char:1 ++ Remove-CsTeamsMeetingTemplatePermissionPolicy -Identity Foobar ++ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + CategoryInfo : NotSpecified: (:) [Remove-CsTeamsM...ermissionPolicy], PolicyRpException + + FullyQualifiedErrorId : ClientError,Microsoft.Teams.Policy.Administration.Cmdlets.Core.RemoveTeamsMeetingTemplatePermissionPolicyCmdlet +``` + +## PARAMETERS + +### -Identity + +Identity of the policy instance to be deleted. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Set-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingtemplatepermissionpolicy) + +[Get-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingtemplatepermissionpolicy) + +[New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy) + +[Grant-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingtemplatepermissionpolicy) diff --git a/skype/skype-ps/skype/Remove-CsTeamsMessagingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsMessagingPolicy.md similarity index 83% rename from skype/skype-ps/skype/Remove-CsTeamsMessagingPolicy.md rename to teams/teams-ps/teams/Remove-CsTeamsMessagingPolicy.md index ae7653a5ff..1529b4300f 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsMessagingPolicy.md +++ b/teams/teams-ps/teams/Remove-CsTeamsMessagingPolicy.md @@ -1,19 +1,19 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsmessagingpolicy -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsmessagingpolicy +applicable: Microsoft Teams title: Remove-CsTeamsMessagingPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsTeamsMessagingPolicy ## SYNOPSIS -Deletes a custom messaging policy. Teams messaging policies determine the features and capabilities that can be used in messaging within the teams client. +Deletes a custom messaging policy. Teams messaging policies determine the features and capabilities that can be used in messaging within the teams client. ## SYNTAX @@ -110,11 +110,13 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### 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/?LinkID=113216). + ## INPUTS ### Microsoft.Rtc.Management.Xds.XdsIdentity - ## OUTPUTS ### System.Object @@ -122,4 +124,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Remove-CsTeamsMobilityPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsMobilityPolicy.md similarity index 86% rename from skype/skype-ps/skype/Remove-CsTeamsMobilityPolicy.md rename to teams/teams-ps/teams/Remove-CsTeamsMobilityPolicy.md index ef5d9a4474..8cce132f98 100644 --- a/skype/skype-ps/skype/Remove-CsTeamsMobilityPolicy.md +++ b/teams/teams-ps/teams/Remove-CsTeamsMobilityPolicy.md @@ -1,115 +1,113 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csteamsmobilitypolicy -applicable: Skype for Business Online -title: Remove-CsTeamsMobilityPolicy -schema: 2.0.0 -manager: ritikag -author: saragava -ms.author: saragava -ms.reviewer: ---- - - -# Remove-CsTeamsMobilityPolicy - -## SYNOPSIS -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -## SYNTAX - -``` -Remove-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] - [<CommonParameters>] -``` - -## DESCRIPTION -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -The Remove-CsTeamsMobilityPolicy cmdlet lets an Admin delete a custom teams mobility policy that has been created. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Remove-CsTeamsMobilityPolicy -Identity SalesPolicy -``` - -Deletes a custom policy that has already been created in the organization. - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Unique identifier for the client policy to be removed. To "remove" the global policy, use the following syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the properties in that policy will be reset to their default values.) To remove a per-user policy, use syntax similar to this: -Identity "SalesDepartmentPolicy". You cannot use wildcards when specifying a policy Identity. - -```yaml -Type: XdsIdentity -Parameter Sets: (All) -Aliases: - -Required: True -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### Microsoft.Rtc.Management.Xds.XdsIdentity - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsmobilitypolicy +applicable: Microsoft Teams +title: Remove-CsTeamsMobilityPolicy +schema: 2.0.0 +manager: ritikag +ms.reviewer: ritikag +--- + +# Remove-CsTeamsMobilityPolicy + +## SYNOPSIS +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +## SYNTAX + +``` +Remove-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +The Remove-CsTeamsMobilityPolicy cmdlet lets an Admin delete a custom teams mobility policy that has been created. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsMobilityPolicy -Identity SalesPolicy +``` + +Deletes a custom policy that has already been created in the organization. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the client policy to be removed. To "remove" the global policy, use the following syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the properties in that policy will be reset to their default values.) To remove a per-user policy, use syntax similar to this: -Identity "SalesDepartmentPolicy". You cannot use wildcards when specifying a policy Identity. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsNetworkRoamingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsNetworkRoamingPolicy.md new file mode 100644 index 0000000000..5192c02bc6 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsNetworkRoamingPolicy.md @@ -0,0 +1,86 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsnetworkroamingpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsNetworkRoamingPolicy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: +manager: mreddy +schema: 2.0.0 +--- + +# Remove-CsTeamsNetworkRoamingPolicy + +## SYNOPSIS + +Remove-CsTeamsNetworkRoamingPolicy allows IT Admins to delete policies for Network Roaming and Bandwidth Control experiences in Microsoft Teams. + +## SYNTAX + +``` +Remove-CsTeamsNetworkRoamingPolicy [[-Identity] <XdsIdentity>] [-Tenant <System.Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes the Teams Network Roaming Policies configured for use in your organization. + +The TeamsNetworkRoamingPolicy cmdlets enable administrators to provide specific settings from the TeamsMeetingPolicy to be rendered dynamically based upon the location of the Teams client. The TeamsNetworkRoamingPolicy cannot be granted to a user but instead can be assigned to a network site. The settings from the TeamsMeetingPolicy included are AllowIPVideo and MediaBitRateKb. When a Teams client is connected to a network site where a CsTeamRoamingPolicy is assigned, these two settings from the TeamsRoamingPolicy will be used instead of the settings from the TeamsMeetingPolicy. + +More on the impact of bit rate setting on bandwidth can be found [here](https://learn.microsoft.com/microsoftteams/prepare-network). + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Remove-CsTeamsNetworkRoamingPolicy -Identity OfficePolicy +``` + +In Example 1, Remove-CsTeamsNetworkRoamingPolicy is used to delete the network roaming policy that has an Identity OfficePolicy. + +## PARAMETERS + +### -Identity +Unique identifier of the policy to be removed. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsNotificationAndFeedsPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsNotificationAndFeedsPolicy.md new file mode 100644 index 0000000000..172211f455 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsNotificationAndFeedsPolicy.md @@ -0,0 +1,109 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsnotificationandfeedspolicy +title: Remove-CsTeamsNotificationAndFeedsPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsNotificationAndFeedsPolicy + +## SYNOPSIS +Deletes an existing Teams Notification and Feeds Policy + +## SYNTAX + +```powershell +Remove-CsTeamsNotificationAndFeedsPolicy [-Identity] <String> [-MsftInternalProcessingMode <String>] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The Microsoft Teams notifications and feeds policy allows administrators to manage how notifications and activity feeds are handled within Teams. This policy includes settings that control the types of notifications users receive, how they are delivered, and which activities are highlighted in their feeds. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsNotificationAndFeedsPolicy +``` + +Remove an existing Notifications and Feeds Policy + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsPinnedApp.md b/teams/teams-ps/teams/Remove-CsTeamsPinnedApp.md new file mode 100644 index 0000000000..669b830d56 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsPinnedApp.md @@ -0,0 +1,60 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/skype/remove-csteamspinnedapp +applicable: Microsoft Teams +title: Remove-CsTeamsPinnedApp +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Remove-CsTeamsPinnedApp + +## SYNOPSIS +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## SYNTAX + +``` +Remove-CsTeamsPinnedApp [[-Identity] <Object>] + [-Confirm] + [-Force] + [-Tenant <Object>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## EXAMPLES + +### Example 1 +Intentionally not provided + +## 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsRecordingRollOutPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsRecordingRollOutPolicy.md new file mode 100644 index 0000000000..6a51b6ae29 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsRecordingRollOutPolicy.md @@ -0,0 +1,115 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsrecordingrolloutpolicy +schema: 2.0.0 +applicable: Microsoft Teams +title: Remove-CsTeamsRecordingRollOutPolicy +manager: yujin1 +author: ronwa +ms.author: ronwa +--- + +# Remove-CsTeamsRecordingRollOutPolicy + +## SYNOPSIS +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. + +## SYNTAX + +``` +Remove-CsTeamsRecordingRollOutPolicy [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +Removes a previously created CsTeamsRecordingRollOutPolicy. + +This command is available from Teams powershell module 6.1.1-preview and above. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsRecordingRollOutPolicy -Identity OrganizerPolicy +``` + +In the example shown above, the command will delete the OrganizerPolicy from the organization's list of policies and remove all assignments of this policy from users who have had the policy assigned. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the CsTeamsRecordingRollOutPolicy to be removed. To remove the global policy, use this syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the policy properties will be reset to their default values.) To remove a custom policy, use this syntax: -Identity SomePolicy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsRoomVideoTeleConferencingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsRoomVideoTeleConferencingPolicy.md new file mode 100644 index 0000000000..e1a8839e41 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsRoomVideoTeleConferencingPolicy.md @@ -0,0 +1,107 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsroomvideoteleconferencingpolicy +title: Remove-CsTeamsRoomVideoTeleConferencingPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsRoomVideoTeleConferencingPolicy + +## SYNOPSIS + +Deletes an existing TeamsRoomVideoTeleConferencingPolicy. + +## SYNTAX + +```powershell +Remove-CsTeamsRoomVideoTeleConferencingPolicy [-Identity] <String> [-MsftInternalProcessingMode <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Room Video Teleconferencing Policy enables administrators to configure and manage video teleconferencing behavior for Microsoft Teams Rooms (meeting room devices). + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier for the policy to be modified. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsSharedCallingRoutingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsSharedCallingRoutingPolicy.md new file mode 100644 index 0000000000..536843d50b --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsSharedCallingRoutingPolicy.md @@ -0,0 +1,126 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamssharedcallingroutingpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsSharedCallingRoutingPolicy +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Remove-CsTeamsSharedCallingRoutingPolicy + +## SYNOPSIS +Deletes an existing Teams shared calling routing policy instance. + +## SYNTAX + +``` +Remove-CsTeamsSharedCallingRoutingPolicy [-Identity] <string> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +TeamsSharedCallingRoutingPolicy is used to configure shared calling. + +## EXAMPLES + +### EXAMPLE 1 +``` +Remove-CsTeamsSharedCallingRoutingPolicy -Identity "Seattle" +``` +The command shown in Example 1 deletes the Teams shared calling routing policy instance Seattle. + +### EXAMPLE 2 +``` +Get-CsTeamsSharedCallingRoutingPolicy -Filter "tag:*" | Remove-CsTeamsSharedCallingRoutingPolicy +``` +In Example 2, all Teams shared calling routing policies configured at the per-user scope are removed. To do this, the command first +calls the Get-CsTeamsSharedCallingRoutingPolicy cmdlet along with the Filter parameter; the filter value "tag:*" limits the +returned data to Teams shared calling routing policies configured at the per-user scope. Those per-user policies are then piped to +and removed by the Remove-CsTeamsSharedCallingRoutingPolicy cmdlet. + +## PARAMETERS + +### -Identity +Unique identifier assigned to the policy when it is created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +This cmdlet was introduced in Teams PowerShell Module 5.5.0. + +## RELATED LINKS +[Get-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamssharedcallingroutingpolicy) + +[Grant-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamssharedcallingroutingpolicy) + +[Set-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamssharedcallingroutingpolicy) + +[New-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamssharedcallingroutingpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsShiftsConnection.md b/teams/teams-ps/teams/Remove-CsTeamsShiftsConnection.md new file mode 100644 index 0000000000..a86968dfd2 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsShiftsConnection.md @@ -0,0 +1,102 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Remove-CsTeamsShiftsConnection +author: serdarsoysal +ms.author: serdars +manager: stepfitz +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnection +schema: 2.0.0 +--- + +# Remove-CsTeamsShiftsConnection + +## SYNOPSIS + +This cmdlet deletes a Shifts connection. + +## SYNTAX + +``` +Remove-CsTeamsShiftsConnection -ConnectionId <String> -InputObject <IConfigApiBasedCmdletsIdentity> [-PassThru] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet deletes a connection. All available connections can be found by running [Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsShiftsConnection -ConnectionId 43cd0e23-b62d-44e8-9321-61cb5fcfae85 +``` + +Deletes the connection with ID `43cd0e23-b62d-44e8-9321-61cb5fcfae85`. + +## PARAMETERS + +### -ConnectionId + +The ID of the connection that you want to delete. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +The identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: RemoveViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -PassThru + +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection) + +[New-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnection) + +[Set-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnection) diff --git a/teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md b/teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md new file mode 100644 index 0000000000..843cf262ce --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md @@ -0,0 +1,70 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Remove-CsTeamsShiftsConnectionInstance +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectioninstance +schema: 2.0.0 +--- + +# Remove-CsTeamsShiftsConnectionInstance + +## SYNOPSIS + +This cmdlet deletes a Shifts connection instance. + +## SYNTAX + +``` +Remove-CsTeamsShiftsConnectionInstance -ConnectorInstanceId <String> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet deletes a connection instance. All available instances can be found by running [Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsShiftsConnectionInstance -ConnectorInstanceId WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b +``` + +Deletes the connection instance with ID `WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b`. + +## PARAMETERS + +### -ConnectorInstanceId + +The ID of the connection instance that you want to delete. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) + +[Set-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnectioninstance) + +[Remove-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectioninstance) diff --git a/teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md b/teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md new file mode 100644 index 0000000000..48935f7bec --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md @@ -0,0 +1,116 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Remove-CsTeamsShiftsConnectionTeamMap +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectionteammap +schema: 2.0.0 +--- + +# Remove-CsTeamsShiftsConnectionTeamMap + +## SYNOPSIS + +This cmdlet removes the mapping between the Microsoft Teams team and workforce management (WFM) team. + +## SYNTAX + +```powershell +Remove-CsTeamsShiftsConnectionTeamMap -ConnectorInstanceId <String> -TeamId <string> -InputObject <IConfigApiBasedCmdletsIdentity> [-PassThru] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet removes the mapping between the Microsoft Teams team and WFM team. All team mappings can be found by running [Get-CsTeamsShiftsConnectionTeamMap](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionteammap). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsShiftsConnectionTeamMap -ConnectorInstanceId "WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b" -TeamId "30b625bd-f0f7-4d5c-8793-9ccef5a63119" +``` + +Unmaps the Teams team with ID "30b625bd-f0f7-4d5c-8793-9ccef5a63119" in the instance with ID "WCI-4c231dd2-4451-45bd-8eea-bd68b40bab8b". + +## PARAMETERS + +### -ConnectorInstanceId + +The ID of the connection instance that you want to delete. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamId + +The ID of the connection instance that you want to delete. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +The identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: RemoveViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -PassThru + +Enables you to pass a user object through the pipeline that represents the user being assigned the policy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionTeamMap](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionteammap) + +[New-CsTeamsShiftsConnectionBatchTeamMap](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectionbatchteammap) diff --git a/teams/teams-ps/teams/Remove-CsTeamsShiftsPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsShiftsPolicy.md new file mode 100644 index 0000000000..f7201e43a2 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsShiftsPolicy.md @@ -0,0 +1,70 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-teamsshiftspolicy +title: Remove-CsTeamsShiftsPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsShiftsPolicy + +## SYNOPSIS + +The `Remove-CsTeamsShiftsPolicy` cmdlet removes a previously created TeamsShiftsPolicy. + +Note: A TeamsShiftsPolicy needs to be unassigned from all the users before it can be deleted. + +## SYNTAX + +``` +Remove-CsTeamsShiftsPolicy [-Identity] <XdsIdentity> [<CommonParameters>] +``` + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsShiftsPolicy -Identity OffShiftAccess_WarningMessage1_AlwaysShowMessage +``` + +In this example, the policy instance to be removed is called "OffShiftAccess_WarningMessage1_AlwaysShowMessage". + +## PARAMETERS + +### -Identity +Policy instance name. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Rtc.Management.Xds.XdsIdentity + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftspolicy) + +[New-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftspolicy) + +[Set-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftspolicy) + +[Grant-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsshiftspolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md b/teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md new file mode 100644 index 0000000000..5c64fec405 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md @@ -0,0 +1,315 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Remove-CsTeamsShiftsScheduleRecord +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsschedulerecord +schema: 2.0.0 +--- + +# Remove-CsTeamsShiftsScheduleRecord + +## SYNOPSIS + +This cmdlet enqueues the clear schedule message. + +## SYNTAX + +### RemoveExpanded (Default) +```powershell +Remove-CsTeamsShiftsScheduleRecord [-ClearSchedulingGroup] -EntityType <String[]> -TeamId <String> + [-DateRangeEndDate <DateTime>] [-DateRangeStartDate <DateTime>] [-DesignatedActorId <String>] + [-TimeZone <String>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] + [-PassThru] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +### Remove +```powershell +Remove-CsTeamsShiftsScheduleRecord -Body <IClearScheduleRequest> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-PassThru] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet sends a request of removing Shifts schedule with specified time range. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsShiftsScheduleRecord -TeamId "eddc3b94-21d5-4ef0-a76a-2e4d632e50be" -DateRangeStartDate "2021-09-30T00:00:00" -DateRangeEndDate "2021-10-01T00:00:00" -ClearSchedulingGroup:$false -EntityType "swapRequest", "openShiftRequest" -DesignatedActorId "683af6f2-4f72-4770-b8e1-4ec31836156ad" +``` + +Removes the Shifts schedule record of swapRequest and openShiftRequest scenarios in the team with ID `eddc3b94-21d5-4ef0-a76a-2e4d632e50be` from 09/30/2021 to 10/01/2021. + +## PARAMETERS + +### -ClearSchedulingGroup +A value indicating whether to clear schedule group. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DateRangeEndDate +The end date of removing schedule record. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DateRangeStartDate +The start date of removing schedule record. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignatedActorId +The user ID of designated actor. + +```yaml +Type: String +Parameter Sets: RemoveExpanded +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntityType +The entity types. + +```yaml +Type: String[] +Parameter Sets: RemoveExpanded +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamId +The Teams team ID where you want to remove schedule record. + +```yaml +Type: String +Parameter Sets: RemoveExpanded +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Body +The request body. + +```yaml +Type: IClearScheduleRequest +Parameter Sets: Remove +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break +Wait for .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Used to return an object that represents the item being modified. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeZone +The Timezone parameter ensures that the shifts are displayed in the correct time zone based on your team's location. + +```yaml +Type: String +Parameter Sets: RemoveExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +The parameters of start time, end time and designated actor ID are optional only when removing the schedule record of a linked team. + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliance.md b/teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliance.md new file mode 100644 index 0000000000..ec60890b7b --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliance.md @@ -0,0 +1,103 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamssurvivablebranchappliance +title: Remove-CsTeamsSurvivableBranchAppliance +schema: 2.0.0 +--- + +# Remove-CsTeamsSurvivableBranchAppliance + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +```powershell +Remove-CsTeamsSurvivableBranchAppliance [-Identity] <String> [-MsftInternalProcessingMode <String>] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The Identity parameter is the unique identifier for the SBA. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliancePolicy.md b/teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliancePolicy.md new file mode 100644 index 0000000000..6aa49338fb --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliancePolicy.md @@ -0,0 +1,103 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamssurvivablebranchappliancepolicy +title: Remove-CsTeamsSurvivableBranchAppliancePolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsSurvivableBranchAppliancePolicy + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) Policy cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +```powershell +Remove-CsTeamsSurvivableBranchAppliancePolicy [-Identity] <String> [-MsftInternalProcessingMode <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Policy instance name. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsTargetingPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsTargetingPolicy.md new file mode 100644 index 0000000000..669d6bc872 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsTargetingPolicy.md @@ -0,0 +1,120 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamstargetingpolicy +title: Remove-CsTeamsTargetingPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsTargetingPolicy + +## SYNOPSIS + +The CsTeamsTargetingPolicy cmdlets removes a previously created CsTeamsTargetingPolicy. + +## SYNTAX + +```powershell +Remove-CsTeamsTargetingPolicy [-Identity] <String> [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +Deletes a previously created TeamsTargetingPolicy. Any users with no explicitly assigned policies will then fall back to the default policy in the organization. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Remove-CsTeamsMeetingPolicy -Identity StudentTagPolicy +``` + +In the example shown above, the command will delete the student tag policy from the organization's list of policies and remove all assignments of this policy from users who have had the policy assigned. + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier for the teams meeting policy to be removed. To remove the global policy, use this syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the policy properties will be reset to their default values.) To remove a custom policy, use this syntax: -Identity StudentTagPolicy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTargetingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamstargetingpolicy) +[Set-CsTargetingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstargetingpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsTemplatePermissionPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsTemplatePermissionPolicy.md new file mode 100644 index 0000000000..28ecb18cd4 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsTemplatePermissionPolicy.md @@ -0,0 +1,135 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamstemplatepermissionpolicy +title: Remove-CsTeamsTemplatePermissionPolicy +author: yishuaihuang4 +ms.author: yishuaihuang +ms.reviewer: +manager: weiliu2 +schema: 2.0.0 +--- + +# Remove-CsTeamsTemplatePermissionPolicy + +## SYNOPSIS +Deletes an instance of TeamsTemplatePermissionPolicy. + +## SYNTAX + +``` +Remove-CsTeamsTemplatePermissionPolicy [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes an instance of TeamsTemplatePermissionPolicy. The `Identity` parameter accepts the identity of the policy instance to delete. + +## EXAMPLES + +### Example 1 +```powershell +PS >Remove-CsTeamsTemplatePermissionPolicy -Identity Foobar +``` + +Deletes a policy instance with the Identity *Foobar*. + +### Example 2 +```powershell +PS >Remove-CsTeamsTemplatePermissionPolicy -Identity Foobar +``` + +```output +Remove-CsTeamsTemplatePermissionPolicy : The policy "Foobar" is currently assigned to one or more users or groups. Ensure policy is not assigned before removing. Please refer to documentation. CorrelationId: 8622aac5-00c3-4071-b6d0-d070db8f663f +At line:1 char:1 ++ Remove-CsTeamsTemplatePermissionPolicy -Identity Foobar ... ++ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + CategoryInfo : NotSpecified: (:) [Remove-CsTeamsTemplatePermissionPolicy], PolicyRpException + + FullyQualifiedErrorId : ClientError,Microsoft.Teams.Policy.Administration.Cmdlets.Core.RemoveTeamsTemplatePermissionPolicyCmdlet +``` + +Attempting to delete a policy instance that is currently assigned to users will result in an error. Remove the assignment before attempting to delete it. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the policy instance to be deleted. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamstemplatepermissionpolicy) + +[New-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy) + +[Set-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamstemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsTranslationRule.md b/teams/teams-ps/teams/Remove-CsTeamsTranslationRule.md new file mode 100644 index 0000000000..a1cc4fdcae --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsTranslationRule.md @@ -0,0 +1,106 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamstranslationrule +applicable: Microsoft Teams +title: Remove-CsTeamsTranslationRule +schema: 2.0.0 +manager: nmurav +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsTeamsTranslationRule + +## SYNOPSIS +Cmdlet to remove an existing number manipulation rule (or list of rules). + +## SYNTAX + +``` +Remove-CsTeamsTranslationRule [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You can use this cmdlet to remove an existing number manipulation rule (or list of rules). The rule can be used, for example, in the settings of your SBC (Set-CsOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsTeamsTranslationRule -Identity AddPlus1 +``` + +This example removes the "AddPlus1" translation rule. As the rule can be used in some places, integrity check is preformed to ensure that the rule is not in use. If the rule is in use an error thrown with specifying which SBC use this rule. + +### Example 2 +```powershell +Get-CsTeamsTranslationRule -Filter 'tst*' | Remove-CsTeamsTranslationRule +``` + +This example removes all translation rules with Identifier starting with tst. + +## PARAMETERS + +### -Identity +Identifier of the rule. This parameter is required. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[New-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/new-csteamstranslationrule) + +[Get-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/get-csteamstranslationrule) + +[Set-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/set-csteamstranslationrule) + +[Test-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/test-csteamstranslationrule) diff --git a/teams/teams-ps/teams/Remove-CsTeamsUnassignedNumberTreatment.md b/teams/teams-ps/teams/Remove-CsTeamsUnassignedNumberTreatment.md new file mode 100644 index 0000000000..118a64f812 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsUnassignedNumberTreatment.md @@ -0,0 +1,74 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsunassignednumbertreatment +applicable: Microsoft Teams +title: Remove-CsTeamsUnassignedNumberTreatment +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Remove-CsTeamsUnassignedNumberTreatment + +## SYNOPSIS +Removes a treatment for how calls to an unassigned number range should be routed. + +## SYNTAX + +``` +Remove-CsTeamsUnassignedNumberTreatment [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet removes a treatment for how calls to an unassigned number range should be routed. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsTeamsUnassignedNumberTreatment -Identity MainAA +``` +This example removes the treatment MainAA. + +## PARAMETERS + +### -Identity +The Id of the specific treatment to remove. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: ByPropertyName +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Object + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PS module 2.5.1 or later. + +## RELATED LINKS +[Get-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/get-csteamsunassignednumbertreatment) + +[New-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/new-csteamsunassignednumbertreatment) + +[Set-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/set-csteamsunassignednumbertreatment) + +[Test-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/test-csteamsunassignednumbertreatment) diff --git a/teams/teams-ps/teams/Remove-CsTeamsUpdateManagementPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsUpdateManagementPolicy.md new file mode 100644 index 0000000000..e558236294 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsUpdateManagementPolicy.md @@ -0,0 +1,113 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsupdatemanagementpolicy +applicable: Microsoft Teams +title: Remove-CsTeamsUpdateManagementPolicy +schema: 2.0.0 +author: vargasj-ms +ms.author: vargasj +manager: gnamun +--- + +# Remove-CsTeamsUpdateManagementPolicy + +## SYNOPSIS +Use this cmdlet to remove a Teams Update Management policy from the tenant. + +## SYNTAX + +``` +Remove-CsTeamsUpdateManagementPolicy [-Identity] <String> [-Force] [-ProgressAction <ActionPreference>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Removes a Teams Update Management policy from the tenant. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsUpdateManagementPolicy -Identity "Campaign Policy" +``` + +In this example, the policy "Campaign Policy" is being removed. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The identity of the policy to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsVdiPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsVdiPolicy.md new file mode 100644 index 0000000000..66afd2e7e6 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsVdiPolicy.md @@ -0,0 +1,108 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsvdipolicy +title: Remove-CsTeamsVdiPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsVdiPolicy + +## SYNOPSIS +This CsTeamsVdiPolicy cmdlets removes a previously created TeamsVdiPolicy. + +## SYNTAX + +```powershell +Remove-CsTeamsVdiPolicy [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes a previously created TeamsVdiPolicy. Any users with no explicitly assigned policies will then fall back to the default policy in the organization. You cannot delete the global policy from the organization. If you want to remove policies currently assigned to one or more users, you should assign a different policy to them before. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTeamsMeetingPolicy -Identity RestrictedUserPolicy +``` + +In the example shown above, the command will delete the restricted user policy from the organization's list of policies and remove all assignments of this policy from users who have had the policy assigned. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the teams Vdi policy to be removed. To remove the global policy, use this syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the policy properties will be reset to their default values.) To remove a custom policy, use this syntax: -Identity RestrictedUserPolicy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsTeamsVirtualAppointmentsPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsVirtualAppointmentsPolicy.md new file mode 100644 index 0000000000..a1a3852ec4 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsVirtualAppointmentsPolicy.md @@ -0,0 +1,118 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsvirtualappointmentspolicy +title: Remove-CsTeamsVirtualAppointmentsPolicy +schema: 2.0.0 +ms.author: erocha +author: emmanuelrocha001 +manager: sonaggarwal +--- + +# Remove-CsTeamsVirtualAppointmentsPolicy + +## SYNOPSIS +This cmdlet is used to delete an instance of TeamsVirtualAppointmentsPolicy. + +## SYNTAX + +``` +Remove-CsTeamsVirtualAppointmentsPolicy [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Deletes an instance of TeamsVirtualAppointmentsPolicy. The `Identity` parameter accepts the identity of the policy instance to delete. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\>Remove-CsTeamsVirtualAppointmentsPolicy -Identity Foobar +``` + +Deletes a given policy instance with the Identity Foobar. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvirtualappointmentspolicy) + +[New-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvirtualappointmentspolicy) + +[Set-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvirtualappointmentspolicy) + +[Grant-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvirtualappointmentspolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsVoiceApplicationsPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsVoiceApplicationsPolicy.md new file mode 100644 index 0000000000..8458e8f402 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsVoiceApplicationsPolicy.md @@ -0,0 +1,106 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsvoiceapplicationspolicy +title: Remove-CsTeamsVoiceApplicationsPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsVoiceApplicationsPolicy + +## SYNOPSIS +Deletes an existing Teams voice applications policy. + +## SYNTAX + +``` +Remove-CsTeamsVoiceApplicationsPolicy [-Identity] <String> [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +TeamsVoiceApplicationsPolicy is used for Supervisor Delegated Administration which allows tenant admins to permit certain users to make changes to auto attendant and call queue configurations. + +## EXAMPLES + +### EXAMPLE 1 +``` +Remove-CsTeamsVoiceApplicationsPolicy -Identity "SDA-Allow-All" +``` +The command shown in Example 1 deletes the Teams voice applications policy SDA-Allow-All. + +### EXAMPLE 2 +``` +Get-CsTeamsVoiceApplicationsPolicy -Filter "tag:*" | Remove-CsTeamsVoiceApplicationsPolicy +``` +In Example 2, all Teams voice applications policies configured at the per-user scope are removed. To do this, the command first calls the Get-CsTeamsVoiceApplicationsPolicy cmdlet along with the Filter parameter; the filter value "tag:*" limits the returned data to Teams voice applications policies configured at the per-user scope. Those per-user policies are then piped to and removed by the Remove-CsTeamsVoiceApplicationsPolicy cmdlet. + +## PARAMETERS + +### -Identity +Unique identifier assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvoiceapplicationspolicy) + +[Grant-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvoiceapplicationspolicy) + +[Set-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsvoiceapplicationspolicy) + +[New-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvoiceapplicationspolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsWorkLoadPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsWorkLoadPolicy.md new file mode 100644 index 0000000000..c32aafbb08 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsWorkLoadPolicy.md @@ -0,0 +1,125 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsworkloadpolicy +title: Remove-CsTeamsWorkLoadPolicy +schema: 2.0.0 +--- + +# Remove-CsTeamsWorkLoadPolicy + +## SYNOPSIS + +This cmdlet deletes a Teams Workload Policy instance. + +## SYNTAX + +```powershell +Remove-CsTeamsWorkLoadPolicy [-Identity] <String> [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +The TeamsWorkLoadPolicy determines the workloads like meeting, messaging, calling that are enabled and/or pinned for the user. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Remove-CsTeamsWorkLoadPolicy -Identity "Test" +``` + +Deletes a Teams Workload policy instance with the identity of "Test". + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Identity of the Teams Workload Policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Microsoft Internal Use Only + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworkloadpolicy) + +[Get-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworkloadpolicy) + +[New-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworkloadpolicy) + +[Grant-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworkloadpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTeamsWorkLocationDetectionPolicy.md b/teams/teams-ps/teams/Remove-CsTeamsWorkLocationDetectionPolicy.md new file mode 100644 index 0000000000..fd2938fd43 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTeamsWorkLocationDetectionPolicy.md @@ -0,0 +1,121 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csteamsworklocationdetectionpolicy +title: Remove-CsTeamsWorkLocationDetectionPolicy +schema: 2.0.0 +ms.author: arkozlov +manager: prashibadkur +author: artemiykozlov +--- + +# Remove-CsTeamsWorkLocationDetectionPolicy + +## SYNOPSIS +This cmdlet is used to delete an instance of TeamsWorkLocationDetectionPolicy. + +## SYNTAX + +``` +Remove-CsTeamsWorkLocationDetectionPolicy [-Identity] <String> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Deletes an instance of TeamsWorkLocationDetectionPolicy. The `Identity` parameter accepts the identity of the policy instance to delete. + +## EXAMPLES + +## EXAMPLES + +### Example 1 +```powershell +PS C:\>Remove-CsTeamsWorkLocationDetectionPolicy -Identity wld-policy +``` + +Deletes a given policy instance with the Identity wld-policy. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworklocationdetectionpolicy) + +[New-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworklocationdetectionpolicy) + +[Set-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsworklocationdetectionpolicy) + +[Grant-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworklocationdetectionpolicy) diff --git a/teams/teams-ps/teams/Remove-CsTenantDialPlan.md b/teams/teams-ps/teams/Remove-CsTenantDialPlan.md new file mode 100644 index 0000000000..41c2e91c20 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTenantDialPlan.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-cstenantdialplan +applicable: Microsoft Teams +title: Remove-CsTenantDialPlan +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsTenantDialPlan + +## SYNOPSIS +Use the `Remove-CsTenantDialPlan` cmdlet to remove a tenant dial plan. + +## SYNTAX + +``` +Remove-CsTenantDialPlan [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The `Remove-CsTenantDialPlan` cmdlet removes an existing tenant dial plan (also known as a location profile). +Tenant dial plans provide required information to allow Enterprise Voice users to make telephone calls. +The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. +A tenant dial plan determines such things as which normalization rules are applied. + +Removing a tenant dial plan also removes any associated normalization rules. +If no tenant dial plan is assigned to an organization, the Global dial plan is used. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsTenantDialPlan -Identity Vt1TenantDialPlan2 +``` + +This example removes the Vt1TenantDialPlan2. + +## PARAMETERS + +### -Identity +The Identity parameter is the unique identifier of the tenant dial plan to remove. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm parameter prompts you for confirmation before the command is executed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf parameter describes what would happen if you executed the command, without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +The ExternalAccessPrefix and OptimizeDeviceDialing parameters have been removed from New-CsTenantDialPlan and Set-CsTenantDialPlan cmdlet since they are no longer used. External access dialing is now handled implicitly using normalization rules of the dial plans. +The Get-CsTenantDialPlan will still show the external access prefix in the form of a normalization rule of the dial plan. + +## RELATED LINKS + +[Grant-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/grant-cstenantdialplan) + +[New-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/new-cstenantdialplan) + +[Set-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/set-cstenantdialplan) + +[Get-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/get-cstenantdialplan) diff --git a/teams/teams-ps/teams/Remove-CsTenantNetworkRegion.md b/teams/teams-ps/teams/Remove-CsTenantNetworkRegion.md new file mode 100644 index 0000000000..5e4b94b289 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTenantNetworkRegion.md @@ -0,0 +1,101 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworkregion +applicable: Microsoft Teams +title: Remove-CsTenantNetworkRegion +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsTenantNetworkRegion + +## SYNOPSIS +Use the `Remove-CsTenantNetworkRegion` cmdlet to remove a tenant network region. + +## SYNTAX +``` +Remove-CsTenantNetworkRegion [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The `Remove-CsTenantNetworkRegion` cmdlet removes an existing tenant network region. + +A network region contains a collection of network sites. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTenantNetworkRegion -Identity "RedmondRegion" +``` + +The command shown in Example 1 removes 'RedmondRegion'. + +## PARAMETERS + +### -Identity +Unique identifier for the network region to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworkregion) + +[Get-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworkregion) + +[Set-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworkregion) diff --git a/teams/teams-ps/teams/Remove-CsTenantNetworkSite.md b/teams/teams-ps/teams/Remove-CsTenantNetworkSite.md new file mode 100644 index 0000000000..a21acb85be --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTenantNetworkSite.md @@ -0,0 +1,102 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksite +applicable: Microsoft Teams +title: Remove-CsTenantNetworkSite +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsTenantNetworkSite + +## SYNOPSIS +Use the `Remove-CsTenantNetworkSite` cmdlet to remove a tenant network site. + +## SYNTAX + +``` +Remove-CsTenantNetworkSite [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The `Remove-CsTenantNetworkSite` cmdlet removes an existing tenant network site. + +A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTenantNetworkSite -Identity "site1" +``` + +The command shown in Example 1 removes 'site1'. + +## PARAMETERS + +### -Identity +Unique identifier for the network site to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksite) + +[Get-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksite) + +[Set-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksite) diff --git a/teams/teams-ps/teams/Remove-CsTenantNetworkSubnet.md b/teams/teams-ps/teams/Remove-CsTenantNetworkSubnet.md new file mode 100644 index 0000000000..2e8c9def13 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsTenantNetworkSubnet.md @@ -0,0 +1,100 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksubnet +applicable: Microsoft Teams +title: Remove-CsTenantNetworkSubnet +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-CsTenantNetworkSubnet + +## SYNOPSIS +Use the `Remove-CsTenantNetworkSubnet` cmdlet to remove a tenant network subnet. + +## SYNTAX + +``` +Remove-CsTenantNetworkSubnet [-Identity] <string> [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The `Remove-CsTenantNetworkSubnet` cmdlet removes an existing tenant network subnet. + +IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-CsTenantNetworkSubnet -Identity "192.168.0.1" +``` + +The command shown in Example 1 removes '192.168.0.1'. + +## PARAMETERS + +### -Identity +Unique identifier for the network subnet to be removed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[New-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksubnet) + +[Get-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksubnet) + +[Set-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksubnet) diff --git a/skype/skype-ps/skype/Remove-CsTenantTrustedIPAddress.md b/teams/teams-ps/teams/Remove-CsTenantTrustedIPAddress.md similarity index 92% rename from skype/skype-ps/skype/Remove-CsTenantTrustedIPAddress.md rename to teams/teams-ps/teams/Remove-CsTenantTrustedIPAddress.md index 80e56b8c6d..36eb4e2803 100644 --- a/skype/skype-ps/skype/Remove-CsTenantTrustedIPAddress.md +++ b/teams/teams-ps/teams/Remove-CsTenantTrustedIPAddress.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-cstenanttrustedipaddress -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-cstenanttrustedipaddress +applicable: Microsoft Teams title: Remove-CsTenantTrustedIPAddress schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsTenantTrustedIPAddress @@ -121,8 +121,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -131,6 +130,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Remove-CsUserCallingDelegate.md b/teams/teams-ps/teams/Remove-CsUserCallingDelegate.md new file mode 100644 index 0000000000..56d6d9bce2 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsUserCallingDelegate.md @@ -0,0 +1,91 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-csusercallingdelegate +applicable: Microsoft Teams +title: Remove-CsUserCallingDelegate +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Remove-CsUserCallingDelegate + +## SYNOPSIS +This cmdlet will remove a delegate for calling in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +```powershell +Remove-CsUserCallingDelegate -Identity <String> -Delegate <String> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet will remove a delegate for the specified user. + +## EXAMPLES + +### Example 1 +```powershell +Remove-CsUserCallingDelegate -Identity user1@contoso.com -Delegate user2@contoso.com +``` +This example shows removing the delegate user2@contoso.com. + +## PARAMETERS + +### -Delegate +The Identity of the delegate to remove. Can be specified using the ObjectId or the SIP address. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity of the user to remove a delegate for. Can be specified using the ObjectId or the SIP address. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PowerShell module 4.0.0 or later. + +The specified user need to have the Microsoft Phone System license assigned. + +You can see the delegate of a user by using the Get-CsUserCallingSettings cmdlet. + +## RELATED LINKS +[Get-CsUserCallingSettings](https://learn.microsoft.com/powershell/module/teams/get-csusercallingsettings) + +[New-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/new-csusercallingdelegate) + +[Set-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/set-csusercallingdelegate) diff --git a/teams/teams-ps/teams/Remove-CsUserLicenseGracePeriod.md b/teams/teams-ps/teams/Remove-CsUserLicenseGracePeriod.md new file mode 100644 index 0000000000..8ba1f83cc3 --- /dev/null +++ b/teams/teams-ps/teams/Remove-CsUserLicenseGracePeriod.md @@ -0,0 +1,192 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/skype/remove-csuserlicensegraceperiod +title: Remove-CsUserLicenseGracePeriod +description: This cmdlet expedites the delicensing operation for an account's assigned plans by removing the grace period, permanently deleting the assigned plans. +schema: 2.0.0 +ms.date: 02/01/2024 +author: serdarsoysal +ms.author: serdars +--- + +# Remove-CsUserLicenseGracePeriod + +## SYNOPSIS + +The `CsUserLicenseGracePeriod` cmdlet expedites the delicensing operation for the assigned plan(s) of a user/resource account by removing the grace period, permanently deleting the assigned plan(s). +Note that this cmdlet is to be used only by tenants with license resiliency enabled. (License resiliency is currently under private preview and not available for everyone.) + +## SYNTAX + +```powershell +Remove-CsUserLicenseGracePeriod +[-Identity] <String> +[-Capability <String>] +-InputObject <IConfigApiBasedCmdletsIdentity> +[-Action <String>] +-Body <IUserDelicensingAccelerationPatch> +[-PassThru] +[-Force] +[-WhatIf] +[-Confirm] +[<CommonParameters>] +``` + +## DESCRIPTION + +The command removes the grace period of the assigned plan(s) against the specified user(s)/resource account(s), permanently deleting the plan(s). +Permanently deletes all/specified plans belonging to the user, which has a grace period assosciated with it. +Assigned plans with no subsequent grace period will see no change. + +If you want to verify the grace period of any assigned plan against a user, you can return that information by using this command: + +`Get-CsOnlineUser -Identity bf19b7db-6960-41e5-a139-2aa373474354` + +## EXAMPLES + +### Example 1 + +```powershell +Remove-CsUserLicenseGracePeriod -Identity bf19b7db-6960-41e5-a139-2aa373474354 +``` + +In Example 1, the command removes the grace period of all assigned plan(s) against the specified user ID, marking the subsequent assigned plan(s) as deleted. Assigned plans with no subsequent grace period will see no change. + +### Example 2 + +```powershell +Remove-CsUserLicenseGracePeriod -Identity bf19b7db-6960-41e5-a139-2aa373474354 -Capability 'MCOEV,MCOMEETADD' +``` + +In Example 2, the capability specified refers to plans assigned to the user(s) under AssignedPlans. The command removes the grace period of the specified assigned plans, marking the subsequent plan(s) as deleted. + +## PARAMETERS + +### -Identity + +Specifies the Identity (GUID) of the user account whose assigned plan grace period needs to be removed, permanently deleting the subsequent plan. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName,ByValue) +Accept wildcard characters: False +``` + +### -Capability + +Denotes the plan(s) assigned to the specified user, which are to be permanently deleted if they are currently serving their grace period. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName,ByValue) +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru + +Returns the results of the command. By default, this cmdlet does not generate any output. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +The Identity parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Action + +Used to specify which action should be taken. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Body + +Specifies the body of the request. + +```yaml +Type: IUserDelicensingAccelerationPatch +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineUser](https://learn.microsoft.com/powershell/module/teams/get-csonlineuser) diff --git a/skype/skype-ps/skype/Remove-CsVideoInteropServiceProvider.md b/teams/teams-ps/teams/Remove-CsVideoInteropServiceProvider.md similarity index 77% rename from skype/skype-ps/skype/Remove-CsVideoInteropServiceProvider.md rename to teams/teams-ps/teams/Remove-CsVideoInteropServiceProvider.md index 894ca01860..9344dcff1d 100644 --- a/skype/skype-ps/skype/Remove-CsVideoInteropServiceProvider.md +++ b/teams/teams-ps/teams/Remove-CsVideoInteropServiceProvider.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/remove-csvideointeropserviceprovider -applicable: Skype for Business Online -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/remove-csvideointeropserviceprovider +applicable: Microsoft Teams +Module Name: MicrosoftTeams title: Remove-CsVideoInteropServiceProvider schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Remove-CsVideoInteropServiceProvider @@ -18,6 +18,15 @@ Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join T ## SYNTAX +``` +Remove-CsVideoInteropServiceProvider [[-Identity] <Object>] + [-Confirm] + [-Force] + [-Tenant <Object>] + [-WhatIf] + [<CommonParameters>] +``` + ## DESCRIPTION Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings. The CsVideoInteropServiceProvider cmdlets allow you to designate provider/tenant specific information about the connection to the provider. @@ -43,14 +52,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Remove-SharedWithTeam.md b/teams/teams-ps/teams/Remove-SharedWithTeam.md new file mode 100644 index 0000000000..e143bc6c3c --- /dev/null +++ b/teams/teams-ps/teams/Remove-SharedWithTeam.md @@ -0,0 +1,94 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/remove-sharedwithteam +title: Remove-SharedWithTeam +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: dedaniel, robharad +--- + +# Remove-SharedWithTeam + +## SYNOPSIS +This cmdlet supports unsharing a channel with a team. + +## SYNTAX +```PowerShell +Remove-SharedWithTeam -HostTeamId <String> -ChannelId <String> -SharedWithTeamId <String> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet supports unsharing a channel with a team. + +## EXAMPLES + +### Example 1 +```PowerShell +Remove-SharedWithTeam -HostTeamId 126b90a5-e65a-4fef-98e3-d9b49f4acf12 -ChannelId 19:cUfyYYw3h_t-1KG8-WkvVa7KLEsIx-JHmyeG43VJojg1@thread.tacv2 +-SharedWithTeam d2aad370-c6ca-438b-b4d7-05f0aa911a7b +``` + +Unshares a channel with a team. + +## PARAMETERS + +### -HostTeamId +Team ID of the host team (Group ID). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -ChannelId +Thread ID of the shared channel. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -SharedWithTeamId +Team ID of the shared with team. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### HostTeamId, ChannelId, SharedWithTeamId + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Remove-Team](https://learn.microsoft.com/powershell/module/teams/remove-team) diff --git a/teams/teams-ps/teams/Remove-Team.md b/teams/teams-ps/teams/Remove-Team.md index 246b0fdc10..b379c99308 100644 --- a/teams/teams-ps/teams/Remove-Team.md +++ b/teams/teams-ps/teams/Remove-Team.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/remove-team +online version: https://learn.microsoft.com/powershell/module/teams/remove-team +title: Remove-Team schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -12,10 +13,10 @@ ms.reviewer: ## SYNOPSIS -This cmdlet deletes a specified Team from Microsoft Teams. +This cmdlet deletes a specified Team from Microsoft Teams. NOTE: The associated Office 365 Unified Group will also be removed. - + ## SYNTAX ``` @@ -24,7 +25,7 @@ Remove-Team -GroupId <String> [<CommonParameters>] ## DESCRIPTION -Removes a specified team via GroupID and all its associated components, like O365 Unified Group... +Removes a specified team via GroupID and all its associated components, like O365 Unified Group... ## EXAMPLES @@ -51,8 +52,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -62,4 +62,4 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[New-Team]() +[New-Team](https://learn.microsoft.com/powershell/module/teams/new-team) diff --git a/teams/teams-ps/teams/Remove-TeamChannel.md b/teams/teams-ps/teams/Remove-TeamChannel.md index 8fd1d11b6c..9ab0da2703 100644 --- a/teams/teams-ps/teams/Remove-TeamChannel.md +++ b/teams/teams-ps/teams/Remove-TeamChannel.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/remove-teamchannel +online version: https://learn.microsoft.com/powershell/module/teams/remove-teamchannel +title: Remove-TeamChannel schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -15,7 +16,7 @@ ms.reviewer: Delete a channel. This will not delete content in associated tabs. -Note: The channel will be "soft deleted", meaning the contents are not permanently deleted for a time. +Note: The channel will be "soft deleted", meaning the contents are not permanently deleted for a time. So a subsequent call to Add-TeamChannel using the same channel name will fail if enough time has not passed. ## SYNTAX @@ -27,7 +28,7 @@ Remove-TeamChannel -GroupId <String> -DisplayName <String> [<CommonParameters>] ## DESCRIPTION > [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. +> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here `https://www.poshtestgallery.com/packages/MicrosoftTeams`. ## EXAMPLES @@ -69,8 +70,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Remove-TeamChannelUser.md b/teams/teams-ps/teams/Remove-TeamChannelUser.md index e6a6142d6d..5593e0c440 100644 --- a/teams/teams-ps/teams/Remove-TeamChannelUser.md +++ b/teams/teams-ps/teams/Remove-TeamChannelUser.md @@ -1,18 +1,21 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/remove-teamchanneluser +online version: https://learn.microsoft.com/powershell/module/teams/remove-teamchanneluser +title: Remove-TeamChannelUser schema: 2.0.0 --- # Remove-TeamChannelUser ## SYNOPSIS -Note: the command will return immediately, but the Teams application will not reflect the update immediately, please refresh the members page to see the update. +> [!Note] +> The command will return immediately, but the Teams application will not reflect the update immediately, please refresh the members page to see the update. -To turn an existing Owner into an Member, specify role parameter as Owner. +To turn an existing Owner into a Member, specify role parameter as Owner. -Note: last owner cannot be removed from the private channel. +> [!Note] +> Last owner cannot be removed from the private channel. ## SYNTAX @@ -23,8 +26,8 @@ Remove-TeamChannelUser -GroupId <String> -DisplayName <String> -User <String> [- ## DESCRIPTION -> [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. +> [!Note] +> This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see [Install Teams PowerShell public preview](https://learn.microsoft.com/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview) and also see [Microsoft Teams PowerShell Release Notes](https://learn.microsoft.com/microsoftteams/teams-powershell-release-notes). ## EXAMPLES @@ -66,7 +69,7 @@ Accept wildcard characters: False ``` ### -User -User's UPN (user principal name - e.g. +User's email address (e.g. johndoe@example.com) ```yaml diff --git a/teams/teams-ps/teams/Remove-TeamTargetingHierarchy.md b/teams/teams-ps/teams/Remove-TeamTargetingHierarchy.md new file mode 100644 index 0000000000..01e2e675e0 --- /dev/null +++ b/teams/teams-ps/teams/Remove-TeamTargetingHierarchy.md @@ -0,0 +1,64 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/connect-microsoftteams +title: Remove-TeamTargetingHierarchy +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- +# Remove-TeamTargetingHierarchy + +## SYNOPSIS + +Removes the tenant's hierarchy. + +## SYNTAX + +### Remove (Default) +``` +Remove-TeamTargetingHierarchy [-ApiVersion <String>] [<CommonParameters>] +``` + +## DESCRIPTION +Removes the tenant's hierarchy. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Remove-TeamTargetingHierarchy +``` + +## PARAMETERS + +### -ApiVersion +The version of the Hierarchy APIs to use. Valid values are: 1 or 2. + +Currently only available in preview from version 6.6.1-preview. Specifying "-ApiVersion 2" will direct cmdlet requests to the newer version of the Hierarchy APIs. This integration is currently in preview/beta mode so customers should not try it on their production workloads but are welcome to try it on test workloads. This is an optional parameter and not specifying it will be interpreted as specifying "-ApiVersion 1", which will continue to direct cmdlet requests to the original version of the Hierarchy APIs until we upgrade production to v2, at which time we will set the default to 2. We do not expect this to have any impact on your cmdlet usage or existing scripts. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 1 +Accept pipeline input: false +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-TeamTargetingHierarchy](https://learn.microsoft.com/powershell/module/teams/set-teamtargetinghierarchy) diff --git a/teams/teams-ps/teams/Remove-TeamUser.md b/teams/teams-ps/teams/Remove-TeamUser.md index 922e993438..1bc56b8ac7 100644 --- a/teams/teams-ps/teams/Remove-TeamUser.md +++ b/teams/teams-ps/teams/Remove-TeamUser.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/remove-teamuser +online version: https://learn.microsoft.com/powershell/module/teams/remove-teamuser +title: Remove-TeamUser schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -33,6 +34,13 @@ Remove-TeamUser -GroupId <String> -User <String> [-Role <String>] [<CommonParame ``` Remove-TeamUser -GroupId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df -User dmx@example.com -Role Owner ``` +In this example, the user "dmx" is removed the role Owner but stays as a team member. + +### Example 2 +``` +Remove-TeamUser -GroupId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df -User dmx@example.com +``` +In this example, the user "dmx" is removed from the team. ## PARAMETERS @@ -68,8 +76,8 @@ Accept wildcard characters: False ``` ### -Role -Specify the role of the user you are removing from the team. Accepts "Owner" and "Member" as possible values. -If cmdlet is called with -Role parameter as "Member" then the specified user is removed from the Team completely even if they were the owner of the Team. If "Owner" is specified in the -Role parameter then the specified user is removed as an owner of the team but stays as a team member. +If cmdlet is called with -Role parameter as "Owner", the specified user is removed as an owner of the team but stays as a team member. + Note: The last owner cannot be removed from the team. ```yaml @@ -85,8 +93,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Remove-TeamsApp.md b/teams/teams-ps/teams/Remove-TeamsApp.md index 6060728d60..a7462e20f9 100644 --- a/teams/teams-ps/teams/Remove-TeamsApp.md +++ b/teams/teams-ps/teams/Remove-TeamsApp.md @@ -1,7 +1,8 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/remove-teamsapp +online version: https://learn.microsoft.com/powershell/module/teams/remove-teamsapp +title: Remove-TeamsApp schema: 2.0.0 --- @@ -44,14 +45,12 @@ Accept wildcard characters: False ``` ### 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 (http://go.microsoft.com/fwlink/?LinkID=113216). +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Remove-TeamsAppInstallation.md b/teams/teams-ps/teams/Remove-TeamsAppInstallation.md index fce4d2111b..36234579ef 100644 --- a/teams/teams-ps/teams/Remove-TeamsAppInstallation.md +++ b/teams/teams-ps/teams/Remove-TeamsAppInstallation.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/remove-teamsappinstallation +online version: https://learn.microsoft.com/powershell/module/teams/remove-teamsappinstallation +title: Remove-TeamsAppInstallation schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -30,6 +31,8 @@ Remove-TeamsAppInstallation [-AppInstallationId <String>] [-AppId <String>] -Use ## DESCRIPTION Removes a Teams App installed in Microsoft Teams. +Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see [Install Teams PowerShell public preview](https://learn.microsoft.com/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview) and also see [Microsoft Teams PowerShell Release Notes](https://learn.microsoft.com/microsoftteams/teams-powershell-release-notes). + ## EXAMPLES ### Example 1 @@ -111,6 +114,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsApplicationAccessPolicy.md b/teams/teams-ps/teams/Set-CsApplicationAccessPolicy.md new file mode 100644 index 0000000000..5fe3b54419 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsApplicationAccessPolicy.md @@ -0,0 +1,157 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csapplicationaccesspolicy +applicable: Microsoft Teams +title: Set-CsApplicationAccessPolicy +schema: 2.0.0 +manager: zhengni +author: frankpeng7 +ms.author: frpeng +ms.reviewer: +--- + +# Set-CsApplicationAccessPolicy + +## SYNOPSIS + +Modifies an existing application access policy. + +## SYNTAX + +```powershell +Set-CsApplicationAccessPolicy [-AppIds <Object>] [-Description <String>] [[-Identity] <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet modifies an existing application access policy. + +## EXAMPLES + +### Add new app ID to the policy + +```powershell +PS C:\> Set-CsApplicationAccessPolicy -Identity "ASimplePolicy" -AppIds @{Add="5817674c-81d9-4adb-bfb2-8f6a442e4622"} +``` + +The command shown above adds a new app ID "5817674c-81d9-4adb-bfb2-8f6a442e4622" to the per-user application access policy ASimplePolicy. + +### Remove app IDs from the policy + +```powershell +PS C:\> Set-CsApplicationAccessPolicy -Identity "ASimplePolicy" -AppIds @{Remove="5817674c-81d9-4adb-bfb2-8f6a442e4622"} +``` + +The command shown above removes the app ID "5817674c-81d9-4adb-bfb2-8f6a442e4622" from the per-user application access policy ASimplePolicy. + +## PARAMETERS + +### -Identity + +Unique identifier assigned to the policy when it was created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppIds + +A list of application (client) IDs. For details of application (client) ID, refer to: [Get tenant and app ID values for signing in](https://learn.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#get-tenant-and-app-id-values-for-signing-in). + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Free format text. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Grant-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Get-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) +[Remove-CsApplicationAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csapplicationaccesspolicy) diff --git a/teams/teams-ps/teams/Set-CsApplicationMeetingConfiguration.md b/teams/teams-ps/teams/Set-CsApplicationMeetingConfiguration.md new file mode 100644 index 0000000000..c6c427fe87 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsApplicationMeetingConfiguration.md @@ -0,0 +1,172 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-CsApplicationMeetingConfiguration +applicable: Teams +title: Set-CsApplicationMeetingConfiguration +schema: 2.0.0 +manager: zhengni +author: jackry6350 +ms.author: yoren +ms.reviewer: +--- + +# Set-CsApplicationMeetingConfiguration + +## SYNOPSIS + +Modifies an existing application meeting configuration for the tenant. + +## SYNTAX + +### Identity + +``` +Set-CsApplicationMeetingConfiguration [-Identity <XdsIdentity>] [-AllowRemoveParticipantAppIds <PSListModifier>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsApplicationMeetingConfiguration [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet modifies an existing application meeting configuration for the tenant. + +## EXAMPLES + +### Add new app ID to the configuration to allow remove participant for the tenant + +``` +PS C:\> Set-CsApplicationMeetingConfiguration -AllowRemoveParticipantAppIds @{Add="5817674c-81d9-4adb-bfb2-8f6a442e4622"} +``` + +The command shown above adds a new app ID "5817674c-81d9-4adb-bfb2-8f6a442e4622" to the application meeting configuration settings for the tenant to allow it to remove participant. + +### Remove app IDs from the configuration to allow remove participant for the tenant + +``` +PS C:\> Set-CsApplicationMeetingConfiguration -AllowRemoveParticipantAppIds @{Remove="5817674c-81d9-4adb-bfb2-8f6a442e4622"} +``` + +The command shown above removes the app ID "5817674c-81d9-4adb-bfb2-8f6a442e4622" from the application meeting configuration settings for the tenant to disallow it to remove participant. + +## PARAMETERS + +### -Identity + +Unique identifier of the application meeting configuration settings to be returned. +Because you can only have a single, global instance of these settings, you do not have to include the Identity when calling the Set-CsApplicationMeetingConfiguration cmdlet. +However, you can use the following syntax to retrieve the global settings: -Identity global. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: +Applicable: Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -AllowRemoveParticipantAppIds + +A list of application (client) IDs. For details of application (client) ID, refer to: [Get tenant and app ID values for signing in](https://learn.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#get-tenant-and-app-id-values-for-signing-in). + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might occur when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +None. +The `Set-CsApplicationMeetingConfiguration` cmdlet does not accept pipelined input. + +## OUTPUTS + +### Output types +The `Set-CsApplicationMeetingConfiguration` cmdlet does not return any objects or values. + +## NOTES + +## RELATED LINKS + +[Get-CsApplicationMeetingConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csapplicationmeetingconfiguration) diff --git a/skype/skype-ps/skype/Set-CsAutoAttendant.md b/teams/teams-ps/teams/Set-CsAutoAttendant.md similarity index 84% rename from skype/skype-ps/skype/Set-CsAutoAttendant.md rename to teams/teams-ps/teams/Set-CsAutoAttendant.md index 0a7af88d24..f1241561ad 100644 --- a/skype/skype-ps/skype/Set-CsAutoAttendant.md +++ b/teams/teams-ps/teams/Set-CsAutoAttendant.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csautoattendant -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csautoattendant +applicable: Microsoft Teams title: Set-CsAutoAttendant schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsAutoAttendant @@ -24,7 +24,6 @@ Set-CsAutoAttendant -Instance <Object> [-Tenant <Guid>] [<CommonParameters>] ## DESCRIPTION The Set-CsAutoAttendant cmdlet lets you modify the properties of an auto attendant. For example, you can change the operator, the greeting, or the menu prompts. - ## EXAMPLES ### -------------------------- Example 1 -------------------------- @@ -94,7 +93,7 @@ $autoAttendant.CallHandlingAssociations # CallFlowId : e7dd255b-ee20-57f0-8a2b-fc403321e284 # Enabled : True -$autoAttendant.CallHandlingAssociations = $autoAttendant.CallHandlingAssociations | Where-Object {$_.ScheduleId -ne "578745b2-1f94-4a38-844c-6bf6996463ee"} +$autoAttendant.CallHandlingAssociations = $autoAttendant.CallHandlingAssociations | where-object {$_.ScheduleId -ne "578745b2-1f94-4a38-844c-6bf6996463ee"} $autoAttendant.CallFlows @@ -108,7 +107,7 @@ $autoAttendant.CallFlows # Greetings : # Menu : Christmas Menu -$autoAttendant.CallFlows = $autoAttendant.CallFlows | Where-Object {$_.Id -ne "8ab460f0-770c-4d30-a2ff-a6469718844f"} +$autoAttendant.CallFlows = $autoAttendant.CallFlows | where-object {$_.Id -ne "8ab460f0-770c-4d30-a2ff-a6469718844f"} Set-CsAutoAttendant -Instance $autoAttendant ``` @@ -126,7 +125,7 @@ You can retrieve an object reference to an existing AA by using the Get-CsAutoAt Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: 0 @@ -141,7 +140,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -151,31 +150,28 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### Microsoft.Rtc.Management.Hosted.OAA.Models.AutoAttendant The Set-CsAutoAttendant cmdlet accepts a `Microsoft.Rtc.Management.Hosted.OAA.Models.AutoAttendant` object as the Instance parameter. - ## OUTPUTS ### Microsoft.Rtc.Management.Hosted.OAA.Models.AutoAttendant The modified instance of the `Microsoft.Rtc.Management.Hosted.OAA.Models.AutoAttendant` object. - ## NOTES ## RELATED LINKS -[New-CsAutoAttendant](New-CsAutoAttendant.md) - -[Get-CsAutoAttendant](Get-CsAutoAttendant.md) +[New-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/new-csautoattendant) -[Get-CsAutoAttendantStatus](Get-CsAutoAttendantStatus.md) +[Get-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/get-csautoattendant) -[Remove-CsAutoAttendant](Remove-CsAutoAttendant.md) +[Get-CsAutoAttendantStatus](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantstatus) -[Update-CsAutoAttendant](Update-CsAutoAttendant.md) +[Remove-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/remove-csautoattendant) +[Update-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/update-csautoattendant) diff --git a/teams/teams-ps/teams/Set-CsCallQueue.md b/teams/teams-ps/teams/Set-CsCallQueue.md new file mode 100644 index 0000000000..8f93fc3973 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsCallQueue.md @@ -0,0 +1,1727 @@ +--- +external help file: Microsoft.Rtc.Management.dll-Help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cscallqueue +applicable: Microsoft Teams +title: Set-CsCallQueue +schema: 2.0.0 +ms.reviewer: +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsCallQueue + +## SYNOPSIS +Updates a Call Queue in your Skype for Business Online or Teams organization. + +## SYNTAX + +``` +Set-CsCallQueue -Identity <Guid> [-AgentAlertTime <Int16>] [-AllowOptOut <Boolean>] [-ChannelId <Guid>] [-ChannelUserObjectId <Guid>] [-ShiftsTeamId <String>] [-ShiftsSchedulingGroupId <String>] [-DistributionLists <List>] [-MusicOnHoldAudioFileId <Guid>] [-Name <String>] [-OboResourceAccountIds <List>] [-OverflowAction <Object>] [-OverflowActionTarget <Guid>] [-OverflowActionCallPriority <Int16>] [-OverflowThreshold <Int16>] [-RoutingMethod <Object>] [-TimeoutAction <Object>] [-Tenant <Guid>] [-TimeoutActionTarget <Guid>] [-TimeoutActionCallPriority <Int16>] [-TimeoutThreshold <Int16>] [-NoAgentApplyTo <String>] [-NoAgentAction <Object>] [-NoAgentActionTarget <Guid>] [-NoAgentActionCallPriority <Int16>] [-UseDefaultMusicOnHold <Boolean>] [-WelcomeMusicAudioFileId <Guid>] [-PresenceBasedRouting <Boolean>] [-ConferenceMode <Boolean>] [-Users <List>] [-LanguageId <String>] [-LineUri <String>] [-OverflowDisconnectTextToSpeechPrompt <String>][-OverflowDisconnectAudioFilePrompt <Guid>] [-OverflowRedirectPersonTextToSpeechPrompt <String>] [-OverflowRedirectPersonAudioFilePrompt <Guid>] [-OverflowRedirectVoiceAppTextToSpeechPrompt <String>] [-OverflowRedirectVoiceAppAudioFilePrompt <Guid>] [-OverflowRedirectPhoneNumberTextToSpeechPrompt <String>] [-OverflowRedirectPhoneNumberAudioFilePrompt <Guid>] [-OverflowRedirectVoicemailTextToSpeechPrompt <String>] [-OverflowRedirectVoicemailAudioFilePrompt <Guid>] [-OverflowSharedVoicemailTextToSpeechPrompt <String>] [-OverflowSharedVoicemailAudioFilePrompt <Guid>] [-EnableOverflowSharedVoicemailTranscription <Boolean>] [-EnableOverflowSharedVoicemailSystemPromptSuppression <Boolean>] [-TimeoutDisconnectTextToSpeechPrompt <String>][-TimeoutDisconnectAudioFilePrompt <Guid>] [-TimeoutRedirectPersonTextToSpeechPrompt <String>] [-TimeoutRedirectPersonAudioFilePrompt <Guid>] [-TimeoutRedirectVoiceAppTextToSpeechPrompt <String>] [-TimeoutRedirectVoiceAppAudioFilePrompt <Guid>] [-TimeoutRedirectPhoneNumberTextToSpeechPrompt <String>][-TimeoutRedirectPhoneNumberAudioFilePrompt <Guid>] [-TimeoutRedirectVoicemailTextToSpeechPrompt <String>] [-TimeoutRedirectVoicemailAudioFilePrompt <Guid>] [-TimeoutSharedVoicemailTextToSpeechPrompt <String>] [-TimeoutSharedVoicemailAudioFilePrompt <Guid>] [-TimeoutSharedVoicemailTextToSpeechPrompt <String>] [-TimeoutSharedVoicemailAudioFilePrompt <Guid>] [-EnableTimeoutSharedVoicemailTranscription <Boolean>] [-EnableTimeoutSharedVoicemailSystemPromptSuppression <Boolean>] [-NoAgentDisconnectTextToSpeechPrompt <String>][-NoAgentDisconnectAudioFilePrompt <Guid>] [-NoAgentRedirectPersonTextToSpeechPrompt <String>] [-NoAgentRedirectPersonAudioFilePrompt <Guid>] [-NoAgentRedirectVoiceAppTextToSpeechPrompt <String>] [-NoAgentRedirectVoiceAppAudioFilePrompt <Guid>] [-NoAgentRedirectPhoneNumberTextToSpeechPrompt <String>] [-NoAgentRedirectPhoneNumberAudioFilePrompt <Guid>] [-NoAgentRedirectVoicemailTextToSpeechPrompt <String>] [-NoAgentRedirectVoicemailAudioFilePrompt <Guid>] [-NoAgentSharedVoicemailTextToSpeechPrompt <String>] [-NoAgentSharedVoicemailAudioFilePrompt <Guid>] [-EnableNoAgentSharedVoicemailTranscription <Boolean>] [-EnableNoAgentSharedVoicemailSystemPromptSuppression <Boolean>] [AuthorizedUsers <List>] [-HideAuthorizedUsers <List>] [-WelcomeTextToSpeechPrompt <String>] [-IsCallbackEnabled <Boolean>] [-CallbackRequestDtmf <String>] [-WaitTimeBeforeOfferingCallbackInSecond <Int16>] [-NumberOfCallsInQueueBeforeOfferingCallback <Int16>] [-CallToAgentRatioThresholdBeforeOfferingCallback <Int16>] [-CallbackOfferAudioFilePromptResourceId <Guid>] [-CallbackOfferTextToSpeechPrompt <String>] [-CallbackEmailNotificationTarget <Guid>] [-ServiceLevelThresholdResponseTimeInSecond [Int16> ] [-ComplianceRecordingForCallQueueTemplateId <List>] [-TextAnnouncementForCR <String>] [-CustomAudioFileAnnouncementForCR <Guid>] [-TextAnnouncementForCRFailure <String>] [-CustomAudioFileAnnouncementForCRFailure <Guid>] [-ShouldOverwriteCallableChannelProperty <Boolean>] [-SharedCallQueueHistoryTemplateId <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +Set-CsCallQueue cmdlet provides a way for you to modify the properties of an existing Call Queue; for example, you can change the name for the Call Queue, the distribution lists associated with the Call Queue, or the welcome audio file. + +The Set-CsCallQueue cmdlet may suggest additional steps required to complete the Call Queue setup. + +Note that this cmdlet is in the Skype for Business Online PowerShell module and also affects Teams. The reason the "Applies To:" is stated as Skype for Business Online is because it must match the actual module name of the cmdlet. To learn how this cmdlet is used with Skype for Business Online and Teams, see https://learn.microsoft.com/microsoftteams/create-a-phone-system-call-queue. + +> [!CAUTION] +> The following configuration parameters are currently only available in PowerShell and do not appear in Teams admin center. Saving a call queue configuration through Teams admin center will _remove_ any of these configured items. +> +> - -HideAuthorizedUsers +> - -OverflowActionCallPriority +> - -OverflowRedirectPersonTextToSpeechPrompt +> - -OverflowRedirectPersonAudioFilePrompt +> - -OverflowRedirectVoicemailTextToSpeechPrompt +> - -OverflowRedirectVoicemailAudioFilePrompt +> - -TimeoutActionCallPriority +> - -TimeoutRedirectPersonTextToSpeechPrompt +> - -TimeoutRedirectPersonAudioFilePrompt +> - -TimeoutRedirectVoicemailTextToSpeechPrompt +> - -TimeoutRedirectVoicemailAudioFilePrompt +> - -NoAgentActionCallPriority +> - -NoAgentRedirectPersonTextToSpeechPrompt +> - -NoAgentRedirectPersonAudioFilePrompt +> - -NoAgentRedirectVoicemailTextToSpeechPrompt +> - -NoAgentRedirectVoicemailAudioFilePrompt +> +> The following configuration parameters will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time. +> +> - -ShiftsTeamId +> - -ShiftsSchedulingGroupId +> - -ComplianceRecordingForCallQueueTemplateId +> - -TextAnnouncementForCR +> - -CustomAudioFileAnnouncementForCR +> - -TextAnnouncementForCRFailure +> - -CustomAudioFileAnnouncementForCRFailure +> - -SharedCallQueueHistoryTemplateId +> +> [Nesting Auto attendants and Call queues](/microsoftteams/plan-auto-attendant-call-queue#nested-auto-attendants-and-call-queues) without a resource account isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. If you nest an Auto attendant or Call queue without a resource account, authorized users can't edit the auto attendant or call queue. +> +> Authorized users can't edit call flows with call priorities at this time. + + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsCallQueue -Identity e7e00636-47da-449c-a36b-1b3d6ee04440 -UseDefaultMusicOnHold $true +``` + +This example updates the Call Queue with identity e7e00636-47da-449c-a36b-1b3d6ee04440 by making it use the default music on hold. + +### -------------------------- Example 2 -------------------------- +``` +Set-CsCallQueue -Identity e7e00636-47da-449c-a36b-1b3d6ee04440 -DistributionLists @("8521b0e3-51bd-4a4b-a8d6-b219a77a0a6a", "868dccd8-d723-4b4f-8d74-ab59e207c357") -MusicOnHoldAudioFileId $audioFile.Id +``` + +This example updates the Call Queue with new distribution lists and references a new music on hold audio file using the audio file ID from the stored variable $audioFile created with the [Import-CsOnlineAudioFile cmdlet](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) + +## PARAMETERS + +### -Identity +PARAMVALUE: Guid + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AgentAlertTime +The AgentAlertTime parameter represents the time (in seconds) that a call can remain unanswered before it is automatically routed to the next agent. The AgentAlertTime can be set to any integer value between 15 and 180 seconds (3 minutes), inclusive. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 30 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOptOut +The AllowOptOut parameter indicates whether or not agents can opt in or opt out from taking calls from a Call Queue. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DistributionLists +The DistributionLists parameter lets you add all the members of the distribution lists to the Call Queue. This is a list of distribution list GUIDs. A service wide configurable maximum number of DLs per Call Queue are allowed. Only the first N (service wide configurable) agents from all distribution lists combined are considered for accepting the call. Nested DLs are supported. O365 Groups can also be used to add members to the Call Queue. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MusicOnHoldAudioFileId +The MusicOnHoldFileContent parameter represents music to play when callers are placed on hold. This is the unique identifier of the audio file. This parameter is required if the UseDefaultMusicOnHold parameter is not specified. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The Name parameter specifies a unique name for the Call Queue. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OboResourceAccountIds +The OboResourceAccountIds parameter lets you add resource account with phone number to the Call Queue. The agents in the Call Queue will be able to make outbound calls using the phone number on the resource accounts. This is a list of resource account GUIDs. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowAction +The OverflowAction parameter designates the action to take if the overflow threshold is reached. The OverflowAction property must be set to one of the following values: DisconnectWithBusy, Forward, Voicemail, and SharedVoicemail. The default value is DisconnectWithBusy. + +PARAMVALUE: DisconnectWithBusy | Forward | Voicemail | SharedVoicemail + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: DisconnectWithBusy +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowActionTarget +The OverflowActionTarget parameter represents the target of the overflow action. If the OverFlowAction is set to Forward, this parameter must be set to a Guid or a telephone number with a mandatory 'tel:' prefix. If the OverflowAction is set to SharedVoicemail, this parameter must be set to a group ID (Microsoft 365, Distribution list, or Mail-enabled security). Otherwise, this parameter is optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowActionCallPriority +_Saving a call queue configuration through Teams admin center will reset the priority to 3 - Normal / Default._ + +If the OverflowAction is set to Forward, and the OverflowActionTarget is set to an Auto attendant or Call queue resource account Guid, this parameter must be set to indicate the priority that will be assigned to the call. Otherwise, this parameter is not applicable. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 +- 1 = Very High +- 2 = High +- 3 = Normal / Default +- 4 = Low +- 5 = Very Low + +> [!IMPORTANT] +> Call priorities isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. Authorized users will not be able to edit call flows with priorities. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowThreshold +The OverflowThreshold parameter defines the number of calls that can be in the queue at any one time before the overflow action is triggered. The OverflowThreshold can be any integer value between 0 and 200, inclusive. A value of 0 causes calls not to reach agents and the overflow action to be taken immediately. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 50 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoutingMethod +The RoutingMethod defines how agents will be called in a Call Queue. If the routing method is set to Serial, then agents will be called one at a time. If the routing method is set to Attendant, then agents will be called in parallel. If routing method is set to RoundRobin, the agents will be called using Round Robin strategy so that all agents share the call-load equally. If routing method is set to LongestIdle, the agents will be called based on their idle time, i.e., the agent that has been idle for the longest period will be called. + +PARAMVALUE: Attendant | Serial | RoundRobin | LongestIdle + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Attendant +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutAction +The TimeoutAction parameter defines the action to take if the timeout threshold is reached. The TimeoutAction property must be set to one of the following values: Disconnect, Forward, Voicemail, and SharedVoicemail. The default value is Disconnect. + +PARAMVALUE: Disconnect | Forward | Voicemail | SharedVoicemail + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disconnect +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutActionTarget +The TimeoutActionTarget represents the target of the timeout action. If the TimeoutAction is set to Forward, this parameter must be set to a Guid or a telephone number with a mandatory 'tel:' prefix. If the TimeoutAction is set to SharedVoicemail, this parameter must be set to an Office 365 Group ID. Otherwise, this field is optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutActionCallPriority +_Saving a call queue configuration through Teams admin center will reset the priority to 3 - Normal / Default._ + +If the TimeoutAction is set to Forward, and the TimeoutActionTarget is set to an Auto attendant or Call queue resource account Guid, this parameter must be set to indicate the priority that will be assigned to the call. Otherwise, this parameter is not applicable. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 +- 1 = Very High +- 2 = High +- 3 = Normal / Default +- 4 = Low +- 5 = Very Low + +> [!IMPORTANT] +> Call priorities isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. Authorized users will not be able to edit call flows with priorities. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutThreshold +The TimeoutThreshold parameter defines the time (in seconds) that a call can be in the queue before that call times out. At that point, the system will take the action specified by the TimeoutAction parameter. +The TimeoutThreshold can be any integer value between 0 and 2700 seconds (inclusive), and is rounded to the nearest 15th interval. For example, if set to 47 seconds, then it is rounded down to 45. If set to 0, welcome music is played, and then the timeout action will be taken. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: 1200 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentApplyTo +The NoAgentApplyTo parameter defines if the NoAgentAction applies to calls already in queue and new calls arriving to the queue, or only new calls that arrive once the No Agents condition occurs. The default value is AllCalls. + +PARAMVALUE: AllCalls | NewCalls + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disconnect +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentAction +The NoAgentAction parameter defines the action to take if the no agents condition is reached. The NoAgentAction property must be set to one of the following values: Queue, Disconnect, Forward, Voicemail, and SharedVoicemail. The default value is Queue. + +PARAMVALUE: Queue | Disconnect | Forward | Voicemail | SharedVoicemail + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disconnect +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentActionTarget +The NoAgentActionTarget represents the target of the no agent action. If the NoAgentAction is set to Forward, this parameter must be set to a Guid or a telephone number with a mandatory 'tel:' prefix. If the NoAgentAction is set to SharedVoicemail, this parameter must be set to a group ID (Microsoft 365, Distribution list, or Mail-enabled security). Otherwise, this field is optional. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentActionCallPriority +_Saving a call queue configuration through Teams admin center will reset the priority to 3 - Normal / Default._ + +If the NoAgentAction is set to Forward, and the NoAgentActionTarget is set to an Auto attendant or Call queue resource account Guid, this parameter must be set to indicate the priority that will be assigned to the call. Otherwise, this parameter is not applicable. + +PARAMVALUE: 1 | 2 | 3 | 4 | 5 +- 1 = Very High +- 2 = High +- 3 = Normal / Default +- 4 = Low +- 5 = Very Low + +> [!IMPORTANT] +> Call priorities isn't currently supported for [Authorized users](/microsoftteams/aa-cq-authorized-users-plan) in Queues App. Authorized users will not be able to edit call flows with priorities. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseDefaultMusicOnHold +The UseDefaultMusicOnHold parameter indicates that this Call Queue uses the default music on hold. This parameter cannot be specified together with MusicOnHoldAudioFileId. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WelcomeMusicAudioFileId +The WelcomeMusicAudioFileId parameter represents the audio file to play when callers are connected with the Call Queue. This is the unique identifier of the audio file. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PresenceBasedRouting +The PresenceBasedRouting parameter indicates whether or not presence based routing will be applied while call being routed to Call Queue agents. When set to False, calls will be routed to agents who have opted in to receive calls, regardless of their presence state. When set to True, opted-in agents will receive calls only when their presence state is Available. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConferenceMode +The ConferenceMode parameter indicates whether or not Conference mode will be applied on calls for this Call queue. Conference mode significantly reduces the amount of time it takes for a caller to be connected to an agent, after the agent accepts the call. The following bullet points detail the difference between both modes: + +- Conference Mode Disabled: CQ call is presented to agent. Agent answers and media streams are setup. Based on geographic location of the CQ call and agent, there may be a slight delay in setting up the media streams which may result in some dead air and the first part of the conversation being cut off. + +- Conference Mode Enabled: CQ call is put into conference. Agent answers and is brought into conference. Media streams are already setup when agent is brought into conference thus no dead air, and first bit of conversation will not be cut off. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Users +The User parameter lets you add agents to the Call Queue. This parameter expects a list of user unique identifiers (GUID). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for Microsoft internal use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LanguageId +The LanguageId parameter indicates the language that is used to play shared voicemail prompts. This parameter becomes a required parameter If either OverflowAction or TimeoutAction is set to SharedVoicemail. + +You can query the supported languages using the Get-CsAutoAttendantSupportedLanguage cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LineUri +This parameter is reserved for Microsoft internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowDisconnectAudioFilePrompt +The OverflowDisconnectAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being disconnected due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowDisconnectTextToSpeechPrompt +The OverflowDisconnectTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being disconnected due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPersonAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectPersonAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person in the organization due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPersonTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectPersonTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person in the organization due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoiceAppAudioFilePrompt +The OverflowRedirectVoiceAppAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a voice application due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoiceAppTextToSpeechPrompt +The OverflowRedirectVoiceAppsTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a voice application due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPhoneNumberAudioFilePrompt +The OverflowRedirectPhoneNumberAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to an external PSTN phone number due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectPhoneNumberTextToSpeechPrompt +The OverflowRedirectPhoneNumberTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to an external PSTN phone number due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoicemailAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectVoiceMailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person's voicemail due to overflow. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowRedirectVoicemailTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The OverflowRedirectVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person's voicemail due to overflow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowSharedVoicemailTextToSpeechPrompt +The OverflowSharedVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is to be played as a greeting to the caller when transferred to shared voicemail on overflow. This parameter becomes a required parameter when OverflowAction is SharedVoicemail and OverflowSharedVoicemailAudioFilePrompt is null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OverflowSharedVoicemailAudioFilePrompt +The OverflowSharedVoicemailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is to be played as a greeting to the caller when transferred to shared voicemail on overflow. This parameter becomes a required parameter when OverflowAction is SharedVoicemail and OverflowSharedVoicemailTextToSpeechPrompt is null. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOverflowSharedVoicemailTranscription +The EnableOverflowSharedVoicemailTranscription parameter is used to turn on transcription for voicemails left by a caller on overflow. This parameter is only applicable when OverflowAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOverflowSharedVoicemailSystemPromptSuppression +The EnableOverflowSharedVoicemailSystemPromptSuppress parameter is used to turn off the default voicemail system prompts. This parameter is only applicable when OverflowAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutDisconnectAudioFilePrompt +The TimeoutDisconnectAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being disconnected due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutDisconnectTextToSpeechPrompt +The TimeoutDisconnectTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being disconnected due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPersonAudioFilePrompt +The TimeoutRedirectPersonAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person in the organization due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPersonTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectPersonTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person in the organization due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoiceAppAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectVoiceAppAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a voice application due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoiceAppTextToSpeechPrompt +The TimeoutRedirectVoiceAppsTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a voice application due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPhoneNumberAudioFilePrompt +The TimeoutRedirectPhoneNumberAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to an external PSTN phone number due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectPhoneNumberTextToSpeechPrompt +The TimeoutRedirectPhoneNumberTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to an external PSTN phone number due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoicemailAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectVoiceMailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person's voicemail due to timeout. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutRedirectVoicemailTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TimeoutRedirectVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person's voicemail due to timeout. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutSharedVoicemailTextToSpeechPrompt +The TimeoutSharedVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is to be played as a greeting to the caller when transferred to shared voicemail on timeout. This parameter becomes a required parameter when TimeoutAction is SharedVoicemail and TimeoutSharedVoicemailAudioFilePrompt is null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TimeoutSharedVoicemailAudioFilePrompt +The TimeoutSharedVoicemailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is to be played as a greeting to the caller when transferred to shared voicemail on timeout. This parameter becomes a required parameter when TimeoutAction is SharedVoicemail and TimeoutSharedVoicemailTextToSpeechPrompt is null. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTimeoutSharedVoicemailTranscription +The EnableTimeoutSharedVoicemailTranscription parameter is used to turn on transcription for voicemails left by a caller on timeout. This parameter is only applicable when TimeoutAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTimeoutSharedVoicemailSystemPromptSuppression +The EnableTimeoutSharedVoicemailSystemPromptSuppression parameter is used to turn off the default voicemail system prompts. This parameter is only applicable when OverflowAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentDisconnectTextToSpeechPrompt +The NoAgentDisconnectTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being disconnected due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentDisconnectAudioFilePrompt +The NoAgentDisconnectAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being disconnected due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPersonTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectPersonTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person in the organization due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPersonAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectPersonAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person in the organization due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoiceAppTextToSpeechPrompt +The NoAgentRedirectVoiceAppsTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a voice application due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoiceAppAudioFilePrompt +The NoAgentRedirectVoiceAppAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a voice application due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPhoneNumberTextToSpeechPrompt +The NoAgentRedirectPhoneNumberTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to an external PSTN phone number due to no agents. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectPhoneNumberAudioFilePrompt +The NoAgentRedirectPhoneNumberAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to an external PSTN phone number due to no agents. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoicemailTextToSpeechPrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to the caller when being redirected to a person's voicemail due to no agent. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentRedirectVoicemailAudioFilePrompt +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The NoAgentRedirectVoiceMailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to a person's voicemail due to no agent. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentSharedVoicemailTextToSpeechPrompt +The NoAgentSharedVoicemailTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is to be played as a greeting to the caller when transferred to shared voicemail on no agents. This parameter becomes a required parameter when NoAgentAction is SharedVoicemail and NoAgentSharedVoicemailAudioFilePrompt is null. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NoAgentSharedVoicemailAudioFilePrompt +The NoAgentSharedVoicemailAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is to be played as a greeting to the caller when transferred to shared voicemail on no agents. This parameter becomes a required parameter when NoAgentAction is SharedVoicemail and NoAgentSharedVoicemailTextToSpeechPrompt is null. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableNoAgentSharedVoicemailTranscription +The EnableNoAgentSharedVoicemailTranscription parameter is used to turn on transcription for voicemails left by a caller on no agents. This parameter is only applicable when NoAgentAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableNoAgentSharedVoicemailSystemPromptSuppression +The EnableNoAgentSharedVoicemailSystemPromptSuppression parameter is used to turn off the default voicemail system prompts. This parameter is only applicable when NoAgentAction is set to SharedVoicemail. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelId +Id of the channel to connect a call queue to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelUserObjectId +The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). This is the GUID of one of the owners of the team that the channel belongs to. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftsTeamId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +Id of the Team containing the Scheduling Group to connect a call queue to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftsSchedulingGroupId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +Id of the Scheduling Group to connect a call queue to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AuthorizedUsers +This is a list of GUIDs for users who are authorized to make changes to this call queue. The users must also have a TeamsVoiceApplications policy assigned. The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HideAuthorizedUsers +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +This is a list of GUIDs of authorized users who should not appear on the list of supervisors for the agents who are members of this queue. The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WelcomeTextToSpeechPrompt +This parameter indicates which Text-to-Speech (TTS) prompt is played when callers are connected to the Call Queue. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsCallbackEnabled + +The IsCallbackEnabled parameter is used to turn on/off callback. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackRequestDtmf + +The DTMF touch-tone key the caller will be told to press to select callback. The CallbackRequestDtmf must be set to one of the following values: + +- Tone0 to Tone9 - Corresponds to DTMF tones from 0 to 9. +- ToneStar - Corresponds to DTMF tone *. +- TonePound - Corresponds to DTMF tone #. + +This parameter becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WaitTimeBeforeOfferingCallbackInSecond + +The number of seconds a call must wait before becoming eligible for callback. This condition applies to calls at the front of the call queue. Set to null ($null) to disable this condition. + +At least one of `-WaitTimeBeforeOfferingCallbackInSecond`, `-NumberOfCallsInQueueBeforeOfferingCallback`, or `-CallToAgentRatioThresholdBeforeOfferingCallback` must be set to a value other than null when `-IsCallbackEnabled` is `True`. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberOfCallsInQueueBeforeOfferingCallback + +The number of calls in queue before a call becomes eligible for callback. This condition applies to calls arriving at the call queue. Set to null ($null) to disable this condition. + +At least one of `-WaitTimeBeforeOfferingCallbackInSecond`, `-NumberOfCallsInQueueBeforeOfferingCallback`, or `-CallToAgentRatioThresholdBeforeOfferingCallback` must be set to a value other than null when `-IsCallbackEnabled` is `True`. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallToAgentRatioThresholdBeforeOfferingCallback + +The ratio of calls to agents that must be in queue before a call becomes eligible for callback. This conditon applies to calls arriving at the call queue. Minimum value of one (1). Set to null ($null) to disable this condition. + +At least one of `-WaitTimeBeforeOfferingCallbackInSecond`, `-NumberOfCallsInQueueBeforeOfferingCallback`, or `-CallToAgentRatioThresholdBeforeOfferingCallback` must be set to a value other than null when `-IsCallbackEnabled` is `True`. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackOfferAudioFilePromptResourceId + +The CallbackOfferAudioFilePromptResourceId parameter indicates the unique identifier for the Audio file prompt which is played to calls that are eligible for callback. This message should tell callers which DTMF touch-tone key (CallbackRequestDtmf) to press to select callback. This parameter, or `-CallbackOfferTextToSpeechPrompt`, becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackOfferTextToSpeechPrompt + +The CallbackOfferTextToSpeechPrompt parameter indicates the Text-to-Speech (TTS) prompt which is played to calls that are eligible for callback. This message should tell callers which DTMF touch-tone key (CallbackRequestDtmf) to press to select callback. This parameter, or `-CallbackOfferAudioFilePromptResourceId`, becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallbackEmailNotificationTarget + +The CallbackEmailNotificationTarget parameter must be set to a group ID (Microsoft 365, Distribution list, or Mail-enabled security) that will receive notification if a callback times out of the call queue or can't be completed for some other reason. This parameter becomes a required parameter when IsCallbackEnabled is set to `True`. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceLevelThresholdResponseTimeInSecond + +The target number of seconds calls should be answered in. This number is used to calculate the call queue service level percentage. + +A value of `$null` indicates that a service level percentage will not be calculated for this call queue. + +```yaml +Type: Int16 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceRecordingForCallQueueTemplateId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The ComplianceRecordingForCallQueueTemplateId parameter indicates a list of up to 2 Compliance Recording for Call Queue templates to apply to the call queue. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TextAnnouncementForCR +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TextAnnouncementForCR parameter indicates the custom Text-to-Speech (TTS) prompt which is played to callers when compliance recording for call queues is enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAudioFileAnnouncementForCR +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The CustomAudioFileAnnouncementForCR parameter indicates the unique identifier for the Audio file prompt which is played to callers when compliance recording for call queues is enabled. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TextAnnouncementForCRFailure +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The TextAnnouncementForCRFailure parameter indicates the custom Text-to-Speech (TTS) prompt which is played to callers if the compliance recording for call queue bot is unable to join or drops from the call. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomAudioFileAnnouncementForCRFailure +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The CustomAudioFileAnnouncementForCRFailure parameter indicates the unique identifier for the Audio file prompt which is played to callers if the compliance recording for call queue bot is unable to join or drops from the call. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharedCallQueueHistoryTemplateId +_Voice applications private preview customers only._ + +_Saving a call queue configuration through Teams admin center will *remove* this setting._ + +The SharedCallQueueHistoryTemplateId parameter indicates the Shared Call Queue History template to apply to the call queue. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShouldOverwriteCallableChannelProperty + +A Teams Channel can only be linked to one Call Queue at a time. To force reassignment of the Teams Channel to a new Call Queue, set this to $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS +[Create a Phone System Call Queue](https://support.office.com/article/Create-a-Phone-System-call-queue-67ccda94-1210-43fb-a25b-7b9785f8a061) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + +[New-CsComplianceRecordingForCallQueueTemplate](./New-CsComplianceRecordingForCallQueueTemplate.md) + +[Set-CsComplianceRecordingForCallQueueTemplate](./Set-CsComplianceRecordingForCallQueueTemplate.md) + +[Get-CsComplianceRecordingForCallQueueTemplate](./Get-CsComplianceRecordingForCallQueueTemplate.md) + +[Remove-CsComplianceRecordingForCallQueueTemplate](./Remove-CsComplianceRecordingForCallQueueTemplate.md) + diff --git a/teams/teams-ps/teams/Set-CsCallingLineIdentity.md b/teams/teams-ps/teams/Set-CsCallingLineIdentity.md new file mode 100644 index 0000000000..16e76a4a04 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsCallingLineIdentity.md @@ -0,0 +1,236 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cscallinglineidentity +applicable: Microsoft Teams +title: Set-CsCallingLineIdentity +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsCallingLineIdentity + +## SYNOPSIS +Use the `Set-CsCallingLineIdentity` cmdlet to modify a Caller ID policy in your organization. + +## SYNTAX + +### Identity (Default) +``` +Set-CsCallingLineIdentity [[-Identity] <string>] [-BlockIncomingPstnCallerID <boolean>] [-CallingIDSubstitute <string>] [-CompanyName <string>] +[-Description <string>] [-EnableUserOverride <boolean>] [-ResourceAccount <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You can either change or block the Caller ID (also called a Calling Line ID) for a user. +By default, the Microsoft Teams or Skype for Business Online user's phone number can be seen when that user makes a call to a PSTN phone, or when a call comes in. +You can modify a Caller ID policy to provide an alternate displayed number, or to block any number from being displayed. + +Note: +- Identity must be unique. +- If CallerIdSubstitute is given as "Resource", then ResourceAccount cannot be empty. + +## EXAMPLES + +### Example 1 +``` +PS C:\> Set-CsCallingLineIdentity -Identity "MyBlockingPolicy" -BlockIncomingPstnCallerID $true +``` + +This example blocks the incoming caller ID. + +### Example 2 +``` +PS C:\> Set-CsCallingLineIdentity -Identity Anonymous -Description "anonymous policy" -CallingIDSubstitute Anonymous -EnableUserOverride $false -BlockIncomingPstnCallerID $true +``` + +This example modifies the new Anonymous Caller ID policy to block the incoming Caller ID. + +### Example 3 +``` +$ObjId = (Get-CsOnlineApplicationInstance -Identity dkcq@contoso.com).ObjectId +Set-CsCallingLineIdentity -Identity DKCQ -CallingIDSubstitute Resource -ResourceAccount $ObjId -CompanyName "Contoso" +``` + +This example modifies the Caller ID policy that sets the Caller ID to the phone number of the specified resource account and sets the Calling party name to Contoso + +### Example 4 +``` +Set-CsCallingLineIdentity -Identity AllowAnonymousForUsers -EnableUserOverride $true +``` + +This example modifies the Caller ID policy and allows Teams users to make anonymous calls. + +## PARAMETERS + +### -BlockIncomingPstnCallerID +The BlockIncomingPstnCallerID switch determines whether to block the incoming Caller ID. The default value is false. + +The BlockIncomingPstnCallerID switch is specific to incoming calls from a PSTN caller to a user. If this is set to True and if this policy is assigned to a Teams user, then Caller ID for incoming calls is suppressed/anonymous. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallingIDSubstitute +The CallingIDSubstitute parameter lets you specify an alternate Caller ID. +The possible values are Anonymous, LineUri and Resource. + +```yaml +Type: CallingIDSubstituteType +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompanyName +This parameter sets the Calling party name (typically referred to as CNAM) on the outgoing PSTN call. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter briefly describes the Caller ID policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableUserOverride +The EnableUserOverride parameter gives Microsoft Teams users the option under Settings and Calls to hide their phone number when making outgoing calls. The CallerID will be Anonymous. + +If CallingIDSubstitute is set to Anonymous, the EnableUserOverride parameter has no effect, and the caller ID is always set to Anonymous. + +EnableUserOverride has precedence over other settings in the policy unless substitution is set to Anonymous. For example, assume the policy instance has substitution using a resource account and EnableUserOverride is set and enabled by the user. In this case, the outbound caller ID will be blocked and Anonymous will be used. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter identifies the Caller ID policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResourceAccount +This parameter specifies the ObjectId of a resource account/online application instance used for Teams Auto Attendant or Call Queue. The outgoing PSTN call will use the phone number defined on the resource account as caller id. For more information about resource accounts please see https://learn.microsoft.com/microsoftteams/manage-resource-accounts. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing, and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/get-cscallinglineidentity) + +[Grant-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/grant-cscallinglineidentity) + +[New-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/new-cscallinglineidentity) + +[Remove-CsCallingLineIdentity](https://learn.microsoft.com/powershell/module/teams/remove-cscallinglineidentity) diff --git a/teams/teams-ps/teams/Set-CsComplianceRecordingForCallQueueTemplate.md b/teams/teams-ps/teams/Set-CsComplianceRecordingForCallQueueTemplate.md new file mode 100644 index 0000000000..2ee33ba19c --- /dev/null +++ b/teams/teams-ps/teams/Set-CsComplianceRecordingForCallQueueTemplate.md @@ -0,0 +1,84 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsComplianceRecordingForCallQueueTemplate +applicable: Microsoft Teams +title: Set-CsComplianceRecordingForCallQueueTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsComplianceRecordingForCallQueueTemplate + +## SYNTAX + +```powershell +Set-CsComplianceRecordingForCallQueueTemplate -Instance <Object> [<CommonParameters>] +``` + +## DESCRIPTION +Use the Set-CsComplianceRecordingForCallQueueTemplate cmdlet to make changes to an existing Compliance Recording for Call Queues template. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$template = CsComplianceRecordingForCallQueueTemplate -Id 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +$template.BotId = 14732826-8206-42e3-b51e-6693e2abb698 +Set-CsComplianceRecordingForCallQueueTemplate $template +``` + +The Set-CsComplianceRecordingForCallQueueTemplate cmdlet lets you modify the properties of a Compliance Recording for Call Queue Template. + +## PARAMETERS + +### -Instance +The Instance parameter is the unique identifier assigned to the Compliance Recording for Call Queue template. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[New-CsComplianceRecordingForCallQueueTemplate](./New-CsComplianceRecordingForCallQueueTemplate.md) + +[Set-CsComplianceRecordingForCallQueueTemplate](./Set-CsComplianceRecordingForCallQueueTemplate.md) + +[Remove-CsComplianceRecordingForCallQueueTemplate](./Remove-CscomplianceRecordingForCallQueueTemplate.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQuuee](./Remove-CsCallQueue.md) + diff --git a/teams/teams-ps/teams/Set-CsExternalAccessPolicy.md b/teams/teams-ps/teams/Set-CsExternalAccessPolicy.md new file mode 100644 index 0000000000..4c738c2d83 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsExternalAccessPolicy.md @@ -0,0 +1,553 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csexternalaccesspolicy +applicable: Microsoft Teams +title: Set-CsExternalAccessPolicy +schema: 2.0.0 +ms.reviewer: rogupta +--- + +# Set-CsExternalAccessPolicy + +## SYNOPSIS +Enables you to modify the properties of an existing external access policy. +External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype; and, 5) communicate with people who are using Teams with an account that's not managed by an organization. + +This cmdlet was introduced in Lync Server 2010. + +## SYNTAX + +### Identity (Default) +``` +Set-CsExternalAccessPolicy [[-Identity] <XdsIdentity>] + [-AllowedExternalDomains <List>] + [-BlockedExternalDomains <List>] + [-CommunicationWithExternalOrgs <String>] + [-Confirm] + [-Description <String>] + [-EnableAcsFederationAccess <Boolean>] + [-EnableFederationAccess <Boolean>] + [-EnableOutsideAccess <Boolean>] + [-EnablePublicCloudAudioVideoAccess <Boolean>] + [-EnableTeamsConsumerAccess <Boolean>] + [-EnableTeamsConsumerInbound <Boolean>] + [-EnableTeamsSmsAccess <Boolean>] + [-EnableXmppAccess <Boolean>] + [-FederatedBilateralChats <Boolean>] + [-Force] + [-RestrictTeamsConsumerAccessToExternalUserProfiles <Boolean>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +### Instance +``` +Set-CsExternalAccessPolicy [-Instance <PSObject>] + [-AllowedExternalDomains <List>] + [-BlockedExternalDomains <List>] + [-CommunicationWithExternalOrgs <String>] + [-Confirm] + [-Description <String>] + [-EnableAcsFederationAccess <Boolean>] + [-EnableFederationAccess <Boolean>] + [-EnableOutsideAccess <Boolean>] + [-EnablePublicCloudAudioVideoAccess <Boolean>] + [-EnableTeamsConsumerAccess <Boolean>] + [-EnableTeamsConsumerInbound <Boolean>] + [-EnableTeamsSmsAccess <Boolean>] + [-EnableXmppAccess <Boolean>] + [-FederatedBilateralChats <Boolean>] + [-Force] + [-RestrictTeamsConsumerAccessToExternalUserProfiles <Boolean>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +When you install Skype for Business Server your users are only allowed to exchange instant messages and presence information among themselves: by default, they can only communicate with people who have SIP accounts in your Active Directory Domain Services. +In addition, users are not allowed to access Skype for Business Server over the Internet; instead, they must be logged on to your internal network before they will be able to log on to Skype for Business Server. + +That might be sufficient to meet your communication needs. +If it doesn't meet your needs, you can use external access policies to extend the ability of your users to communicate and collaborate. +External access policies can grant (or revoke) the ability of your users to do any or all of the following: + +1. Communicate with people who have SIP accounts with a federated organization. +Note that enabling federation alone will not provide users with this capability. +Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users. + +2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). this policy setting only applies if acs federation has been enabled at the tenant level using the [Set-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration) cmdlet. + +3. Access Skype for Business Server over the Internet, without having to first log on to your internal network. +This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location. + +4. Communicate with people who have SIP accounts with a public instant messaging service such as Skype. + + The following parameters are not applicable to Skype for Business Online/Microsoft Teams: Description, EnableXmppAccess, Force, Identity, Instance, PipelineVariable, and Tenant + +5. (Microsoft Teams Only) Communicate with people who are using Teams with an account that's not managed by an organization. This policy only applies if Teams Consumer Federation has been enabled at the tenant level using the [Set-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration) cmdlet or Teams admin center under the External Access setting. + +After an external access policy has been created, you can use the `Set-CsExternalAccessPolicy` cmdlet to change the property values of that policy. +For example, by default the global policy does not allow users to communicate with people who have accounts with a federated organization. +If you would like to grant this capability to all of your users you can call the `Set-CsExternalAccessPolicy` cmdlet and set the value of the global policy's EnableFederationAccess property to True. + +## EXAMPLES + +### -------------------------- Example 1 ------------------------ +``` +Set-CsExternalAccessPolicy -Identity RedmondExternalAccessPolicy -EnableFederationAccess $True +``` + +The command shown in Example 1 modifies the per-user external access policy that has the Identity RedmondExternalAccessPolicy. +In this example, the command changes the value of the EnableFederationAccess property to True. + +### -------------------------- Example 2 ------------------------ +``` +Get-CsExternalAccessPolicy | Set-CsExternalAccessPolicy -EnableFederationAccess $True +``` + +In Example 2, federation access is enabled for all the external access policies configured for use in the organization. +To do this, the command first calls the `Get-CsExternalAccessPolicy` cmdlet without any parameters; this returns a collection of all the external policies currently configured for use. +That collection is then piped to the `Set-CsExternalAccessPolicy` cmdlet, which changes the value of the EnableFederationAccess property for each policy in the collection. + +### -------------------------- Example 3 ------------------------ +``` +Get-CsExternalAccessPolicy -Filter tag:* | Set-CsExternalAccessPolicy -EnableFederationAccess $True +``` + +Example 3 enables federation access for all the external access policies that have been configured at the per-user scope. +To carry out this task, the first thing the command does is use the `Get-CsExternalAcessPolicy` cmdlet and the Filter parameter to return a collection of all the policies that have been configured at the per-user scope. +(The filter value "tag:*" limits returned data to policies that have an Identity that begins with the string value "tag:". +Any policy with an Identity that begins with "tag:" has been configured at the per-user scope.) The filtered collection is then piped to the `Set-CsExternalAccessPolicy` cmdlet, which modifies the EnableFederationAccess property for each policy in the collection. + +### -------------------------- Example 4 ------------------------ +``` +Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $false +New-CsExternalAccessPolicy -Identity AcsFederationAllowed -EnableAcsFederationAccess $true +``` + +In this example, the Global policy is updated to disallow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation enabled and which can be assigned to selected users for which Team-ACS federation will be allowed. + +### -------------------------- Example 5 ------------------------ +``` +Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $true +New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed -EnableAcsFederationAccess $false +``` + +In this example, the Global policy is updated to allow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation disabled and which can then be assigned to selected users for which Team-ACS federation will not be allowed. + +### -------------------------- Example 6 ------------------------ +``` +New-CsExternalAccessPolicy -Identity GranularFederationExample -CommunicationWithExternalOrgs "AllowSpecificExternalDomains" -AllowedExternalDomains @("example1.com", "example2.com") +Set-CsTenantFederationConfiguration -CustomizeFederation $true +``` +In this example, we create an ExternalAccessPolicy named "GranularFederationExample" that allows communication with specific external domains, namely `example1.com` and `example2.com`. The federation policy is set to restrict communication to only these allowed domains. + +## PARAMETERS + +### -Identity +Unique identifier for the external access policy to be modified. +External access policies can be configured at the global, site, or per-user scopes. +To modify the global policy, use this syntax: `-Identity global`. +To modify a site policy, use syntax similar to this: `-Identity site:Redmond`. +To modify a per-user policy, use syntax similar to this: `-Identity SalesAccessPolicy`. +If this parameter is not specified then the global policy will be modified. + +Note that wildcards are not allowed when specifying an Identity. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -AllowedExternalDomains +> [!NOTE] +> Please note that this parameter is in Private Preview. + +Specifies the external domains allowed to communicate with users assigned to this policy. This setting is applicable only when `CommunicationWithExternalOrgs` is configured to `AllowSpecificExternalDomains`. This setting can be modified only in custom policy. In Global (default) policy `CommunicationWithExternalOrgs` can only be set to `OrganizationDefault` and cannot be changed. +```yaml +Type: List +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedExternalDomains +> [!NOTE] +> Please note that this parameter is in Private Preview. + +Specifies the external domains blocked from communicating with users assigned to this policy. This setting is applicable only when `CommunicationWithExternalOrgs` is configured to `BlockSpecificExternalDomains`. This setting can be modified only in custom policy. In Global (default) policy `CommunicationWithExternalOrgs` can only be set to `OrganizationDefault` and cannot be changed. +```yaml +Type: List +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CommunicationWithExternalOrgs +> [!NOTE] +> Please note that this parameter is in Private Preview. + +Indicates how the users get assigned by this policy can communicate with the external orgs. There are 5 options: + +- OrganizationDefault: users follow the federation settings specified in `TenantFederationConfiguration`. This is the default value. +- AllowAllExternalDomains: users are allowed to communicate with all domains. +- AllowSpecificExternalDomains: users can communicate with external domains listed in `AllowedExternalDomains`. +- BlockSpecificExternalDomains: users are blocked from communicating with domains listed in `BlockedExternalDomains`. +- BlockAllExternalDomains: users cannot communicate with any external domains. + +The setting is only applicable when `EnableFederationAccess` is set to true. This setting can only be modified in custom policies. In the Global (default) policy, it is fixed to `OrganizationDefault` and cannot be changed. +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: OrganizationDefault +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide additional text to accompany the policy. +For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableAcsFederationAccess +Indicates whether Teams meeting organized by the user can be joined by users of customer applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration. + +Additionally, Azure Communication Services users would be able to call Microsoft 365 users that have assigned policies with enabled federation. + +To enable for all users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to True. It can be disabled for selected users by assigning them a policy with federation disabled. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableFederationAccess +Indicates whether the user is allowed to communicate with people who have SIP accounts with a federated organization. +Read [Manage external access in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableOutsideAccess +Indicates whether the user is allowed to connect to Skype for Business Server over the Internet, without logging on to the organization's internal network. +The default value is False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnablePublicCloudAudioVideoAccess +Indicates whether the user is allowed to conduct audio/video conversations with people who have SIP accounts with a public Internet connectivity provider such as MSN. +When set to False, audio and video options in Skype for Business will be disabled any time a user is communicating with a public Internet connectivity contact. +The default value is False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsConsumerAccess +(Microsoft Teams Only) Indicates whether the user is allowed to communicate with people who have who are using Teams with an account that's not managed by an organization. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsConsumerInbound +(Microsoft Teams Only) Indicates whether the user is allowed to be discoverable by people who are using Teams with an account that's not managed by an organization. It also controls if people who have who are using Teams with an account that's not managed by an organization can start the communication with the user. + +To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled. + +Read [Manage external access in Microsoft Teams](https://learn.microsoft.com/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams. +The default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTeamsSmsAccess +Allows you to control whether users can have SMS text messaging capabilities within Teams. +Possible Values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableXmppAccess +Indicates whether the user is allowed to communicate with users who have SIP accounts with a federated XMPP (Extensible Messaging and Presence Protocol) partner. +The default value is False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FederatedBilateralChats +> [!NOTE] +> Please note that this parameter is in Private Preview. + +This setting enables bi-lateral chats for the users included in the messaging policy. + +Some organizations may want to restrict who users are able to message in Teams. While organizations have always been able to limit users' chats to only other internal users, organizations can now limit users' chat ability to only chat with other internal users and users in one other organization via the bilateral chat policy. + +Once external access and bilateral policy is set up, users with the policy can be in external group chats only with a maximum of two organizations. When they try to create a new external chat with users from more than two tenants or add a user from a third tenant to an existing external chat, a system message will be shown preventing this action. + +Users with bilateral policy applied are also removed from existing external group chats with more than two organizations. + +This policy doesn't apply to meetings, meeting chats, or channels. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might occur when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictTeamsConsumerAccessToExternalUserProfiles +Defines if a user is restriced to collaboration with Teams Consumer (TFL) user only in Extended Directory +Possible Values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the Skype for Business Online tenant account for whom the external access policy is being modified. +For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can return the tenant ID for each of your Skype for Business Online tenants by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy object. +The `Set-CsExternalAccessPolicy` cmdlet accepts pipelined input of the external access policy object. + +## OUTPUTS + +### Output types +The `Set-CsExternalAccessPolicy` cmdlet does not return a value or object. +Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy object. + +## NOTES + +## RELATED LINKS + +[Get-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/get-csexternalaccesspolicy) + +[Grant-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csexternalaccesspolicy) + +[New-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csexternalaccesspolicy) + +[Remove-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csexternalaccesspolicy) diff --git a/teams/teams-ps/teams/Set-CsGroupPolicyAssignment.md b/teams/teams-ps/teams/Set-CsGroupPolicyAssignment.md index ef4901a816..c74a4f85ba 100644 --- a/teams/teams-ps/teams/Set-CsGroupPolicyAssignment.md +++ b/teams/teams-ps/teams/Set-CsGroupPolicyAssignment.md @@ -1,144 +1,25 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/set-csgrouppolicyassignment +online version: https://learn.microsoft.com/powershell/module/teams/set-csgrouppolicyassignment +title: Set-CsGroupPolicyAssignment schema: 2.0.0 author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsGroupPolicyAssignment ## SYNOPSIS -**Note:** This cmdlet is currently only available in private preview in the pre-release Teams PowerShell module. - -This cmdlet is used to update a group policy assignment. - -## SYNTAX - -``` -Set-CsGroupPolicyAssignment -GroupId <String> -PolicyType <String> [-PolicyName <String>] [-Rank <Int>] -``` - -## DESCRIPTION -This cmdlet will update the policy assignment for a group for a given policy type. The policy instance and/or policy rank can be updated. Refer to [New-CsGroupPolicyAssignment]() for more details about rank. - -## EXAMPLES - -### Example 1 -In this example, a new policy of the same type is set without changing the rank. - -``` -Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy - -GroupId PolicyType PolicyName Rank CreatedTime CreatedBy -------- ---------- ---------- ---- ----------- --------- -d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 TeamsMeetingPolicy AllOn 1 10/29/2019 3:57:27 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 -566b8d39-5c5c-4aaa-bc07-4f36278a1b38 TeamsMeetingPolicy Kiosk 2 11/2/2019 12:14:41 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 - -Set-CsGroupPolicyAssignment -GroupId 566b8d39-5c5c-4aaa-bc07-4f36278a1b38 -PolicyType TeamsMeetingPolicy -PolicyName AllOff - -Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy - -GroupId PolicyType PolicyName Rank CreatedTime CreatedBy -------- ---------- ---------- ---- ----------- --------- -d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 TeamsMeetingPolicy AllOn 1 10/29/2019 3:57:27 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 -566b8d39-5c5c-4aaa-bc07-4f36278a1b38 TeamsMeetingPolicy AllOff 2 11/4/2019 9:30:23 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 -``` - -### Example 2 -In this example, the rank of the policy assignment is updated. - -``` -Set-CsGroupPolicyAssignment -GroupId 566b8d39-5c5c-4aaa-bc07-4f36278a1b38 -PolicyType TeamsMeetingPolicy -Rank 1 - -Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy - -GroupId PolicyType PolicyName Rank CreatedTime CreatedBy -------- ---------- ---------- ---- ----------- --------- -566b8d39-5c5c-4aaa-bc07-4f36278a1b38 TeamsMeetingPolicy AllOff 1 11/4/2019 9:36:42 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 -d8ebfa45-0f28-4d2d-9bcc-b158a49e2d17 TeamsMeetingPolicy AllOn 2 10/29/2019 3:57:27 AM aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64 -``` - -## PARAMETERS - -### -GroupId -The ID of a batch policy assignment operation. - -```yaml -Type: String -Parameter Sets: -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyType -The type of the policy assigned. - -```yaml -Type: String -Parameter Sets: -Aliases: - -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -PolicyName -The of the new policy to be assigned. - -```yaml -Type: String -Parameter Sets: -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Rank -The new rank of the policy assignment, relative to other group policy assignments for the same policy type. - -```yaml -Type: String -Parameter Sets: -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES +> [!NOTE] +> The cmdlet Set-CsGroupPolicyAssignment is not yet available. In the meantime, to change a group policy assignment you can first remove the current policy assignment from the group and then add a new policy assignment. ## RELATED LINKS -[Get-CsGroupPolicyAssignment]() - -[Set-CsGroupPolicyAssignment]() +[New-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/new-csgrouppolicyassignment) -[Remove-CsGroupPolicyAssignment]() +[Get-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/get-csgrouppolicyassignment) +[Remove-CsGroupPolicyAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csgrouppolicyassignment) diff --git a/teams/teams-ps/teams/Set-CsInboundBlockedNumberPattern.md b/teams/teams-ps/teams/Set-CsInboundBlockedNumberPattern.md new file mode 100644 index 0000000000..010cb41526 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsInboundBlockedNumberPattern.md @@ -0,0 +1,146 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csinboundblockednumberpattern +applicable: Microsoft Teams +title: Set-CsInboundBlockedNumberPattern +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: bulenteg +schema: 2.0.0 +--- + +# Set-CsInboundBlockedNumberPattern + +## SYNOPSIS +Modifies one or more parameters of a blocked number pattern in the tenant list. + +## SYNTAX + +### Identity (Default) +``` +Set-CsInboundBlockedNumberPattern [[-Identity] <string>] [-Description <string>] [-Enabled <boolean>] [-Pattern <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet modifies one or more parameters of a blocked number pattern in the tenant list. + +## EXAMPLES + +### Example 1 +```powershell +PS> Set-CsInboundBlockedNumberPattern -Identity "BlockAutomatic" -Pattern "^\+11234567890" +``` + +This example modifies a blocked number pattern to block inbound calls from +11234567890 number. + +## PARAMETERS + +### -Description +A friendly description for the blocked number pattern to be modified. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +If this parameter is set to True, the inbound calls matching the pattern will be blocked. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +A unique identifier specifying the blocked number pattern to be modified. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern +A regular expression that the calling number must match in order to be blocked. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/new-csinboundblockednumberpattern) + +[Get-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/get-csinboundblockednumberpattern) + +[Remove-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/remove-csinboundblockednumberpattern) diff --git a/teams/teams-ps/teams/Set-CsInboundExemptNumberPattern.md b/teams/teams-ps/teams/Set-CsInboundExemptNumberPattern.md new file mode 100644 index 0000000000..592cc10d0f --- /dev/null +++ b/teams/teams-ps/teams/Set-CsInboundExemptNumberPattern.md @@ -0,0 +1,167 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csinboundexemptnumberpattern +applicable: Microsoft Teams +title: Set-CsInboundExemptNumberPattern +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Set-CsInboundExemptNumberPattern + +## SYNOPSIS + +Modifies one or more parameters of an exempt number pattern in the tenant list. + +## SYNTAX + +### Identity (Default) +``` +Set-CsInboundExemptNumberPattern [[-Identity] <string>] [-Description <string>] [-Enabled <boolean>] [-Pattern <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet modifies one or more parameters of an exempt number pattern in the tenant list. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS> Set-CsInboundExemptNumberPattern -Identity "AllowContoso1" -Pattern "^\+?1312555888[2|3]$" +``` + +Sets the inbound exempt number pattern for AllowContoso1 + +### EXAMPLE 2 + +```powershell +PS> Set-CsInboundExemptNumberPattern -Identity "AllowContoso1" -Enabled $False +``` + +Disables the exempt number pattern from usage in call blocking + +## PARAMETERS + +### -Description + +Sets the description of the number pattern. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +This parameter determines whether the number pattern is enabled for exemption or not. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the exempt number pattern to be changed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern + +A regular expression that the calling number must match in order to be exempt from blocking. It is best practice to start the regular expression with the hat character and end it with the dollar character. You can use various regular expression test sites on the Internet to validate the expression. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +You can use Test-CsInboundBlockedNumberPattern to test your block and exempt phone number ranges. + +## RELATED LINKS + +[Get-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/get-csinboundexemptnumberpattern) + +[New-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/new-csinboundexemptnumberpattern) + +[Remove-CsInboundExemptNumberPattern](https://learn.microsoft.com/powershell/module/teams/remove-csinboundexemptnumberpattern) + +[Test-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/test-csinboundblockednumberpattern) + +[Get-CsTenantBlockedCallingNumbers](https://learn.microsoft.com/powershell/module/teams/get-cstenantblockedcallingnumbers) diff --git a/teams/teams-ps/teams/Set-CsOnlineApplicationInstance.md b/teams/teams-ps/teams/Set-CsOnlineApplicationInstance.md new file mode 100644 index 0000000000..4e64fee3fa --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineApplicationInstance.md @@ -0,0 +1,187 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlineapplicationinstance +applicable: Microsoft Teams +title: Set-CsOnlineApplicationInstance +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineApplicationInstance + +## SYNOPSIS +Updates an application instance in Microsoft Entra ID. + +**Note**: The use of this cmdlet for assigning phone numbers in commercial and GCC cloud instances has been deprecated. Use the new [Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) and [Remove-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment) cmdlets instead. + +## SYNTAX + +``` +Set-CsOnlineApplicationInstance [-Identity] <string> [[-OnpremPhoneNumber] <string>] [[-ApplicationId] <guid>] [[-AcsResourceId] <guid>] [[-DisplayName] <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet is used to update an application instance in Microsoft Entra ID. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Set-CsOnlineApplicationInstance -Identity appinstance01@contoso.com -ApplicationId ce933385-9390-45d1-9512-c8d228074e07 -DisplayName "AppInstance01" +``` + +This example shows updated ApplicationId and DisplayName information for an existing Auto Attendant application instance with Identity "appinstance01@contoso.com". + +## PARAMETERS + +### -Identity +The URI or ID of the application instance to update. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnpremPhoneNumber +**Note**: Using this parameter has been deprecated in commercial and GCC cloud instances. Use the new Set-CsPhoneNumberAssignment cmdlet instead. + +Assigns a hybrid (on-premise) telephone number to the application instance. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplicationId +The application ID. The Microsoft application Auto Attendant has the ApplicationId ce933385-9390-45d1-9512-c8d228074e07 and the Microsoft application Call Queue has the ApplicationId 11cd3e2e-fccb-42ad-ad00-878b93575e07. Third-party applications available in a tenant will use other ApplicationId's. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AcsResourceId +The ACS Resource ID. The unique identifier assigned to an instance of Azure Communication Services within the Azure cloud infrastructure. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName +The display name. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +This switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If it isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstance) + +[New-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstance) + +[Find-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/find-csonlineapplicationinstance) + +[Sync-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/sync-csonlineapplicationinstance) diff --git a/teams/teams-ps/teams/Set-CsOnlineAudioConferencingRoutingPolicy.md b/teams/teams-ps/teams/Set-CsOnlineAudioConferencingRoutingPolicy.md new file mode 100644 index 0000000000..a1b9ec1f59 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineAudioConferencingRoutingPolicy.md @@ -0,0 +1,177 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlineaudioconferencingroutingpolicy +title: Set-CsOnlineAudioConferencingRoutingPolicy +schema: 2.0.0 +--- + +# Set-CsOnlineAudioConferencingRoutingPolicy + +## SYNOPSIS + +This cmdlet sets the Online Audio Conferencing Routing Policy for users in the tenant. + +## SYNTAX + +```powershell +Set-CsOnlineAudioConferencingRoutingPolicy [-Description <String>] [[-Identity] <String>] + [-OnlinePstnUsages <Object>] [-RouteType <String>] [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +Teams meeting dial-out calls are initiated from within a meeting in your organization to PSTN numbers, including call-me-at calls and calls to bring new participants to a meeting. + +To enable Teams meeting dial-out routing through Direct Routing to on-network users, you need to create and assign an Audio Conferencing routing policy called "OnlineAudioConferencingRoutingPolicy." + +The OnlineAudioConferencingRoutingPolicy policy is equivalent to the CsOnlineVoiceRoutingPolicy for 1:1 PSTN calls via Direct Routing. + +Audio Conferencing voice routing policies determine the available routes for calls from meeting dial-out based on the destination number. Audio Conferencing voice routing policies link to PSTN usages, determining routes for meeting dial-out calls by associated organizers. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Set-CsOnlineAudioConferencingRoutingPolicy -Identity "Policy 1" -OnlinePstnUsages "US and Canada" +``` + +Sets the Online Audio Conferencing Routing Policy "Policy 1" value of "OnlinePstnUsages" to "US and Canada". + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide explanatory text about the Online Audio Conferencing Routing policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the Online Audio Conferencing Routing Policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnUsages + +A list of online PSTN usages (such as Local or Long Distance) that can be applied to this online audio conferencing routing policy. The online PSTN usages must be existing usages (PSTN usages can be retrieved by calling the Get-CsOnlinePstnUsage cmdlet). + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RouteType + +For internal use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsOnlineAudioConferencingRoutingPolicy](New-CsOnlineAudioConferencingRoutingPolicy.md) +[Remove-CsOnlineAudioConferencingRoutingPolicy](Remove-CsOnlineAudioConferencingRoutingPolicy.md) +[Grant-CsOnlineAudioConferencingRoutingPolicy](Grant-CsOnlineAudioConferencingRoutingPolicy.md) +[Get-CsOnlineAudioConferencingRoutingPolicy](Get-CsOnlineAudioConferencingRoutingPolicy.md) diff --git a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingBridge.md b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingBridge.md similarity index 86% rename from skype/skype-ps/skype/Set-CsOnlineDialInConferencingBridge.md rename to teams/teams-ps/teams/Set-CsOnlineDialInConferencingBridge.md index ea4654d32f..a0d2c3d32d 100644 --- a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingBridge.md +++ b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingBridge.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencingbridge -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinedialinconferencingbridge +applicable: Microsoft Teams title: Set-CsOnlineDialInConferencingBridge schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsOnlineDialInConferencingBridge @@ -50,7 +50,6 @@ Set-CsOnlineDialInConferencingBridge -Name "Conference Bridge" -DefaultServiceNu This example sets the default dial-in phone number to 14255551234 for the audio conferencing bridge named "Conference Bridge". - ### -------------------------- Example 2 -------------------------- ``` $bridge = Get-CsOnlineDialInConferencingBridge -Name "Conference Bridge" @@ -60,8 +59,7 @@ $Bridge.Name = "O365 Bridge" Set-CsOnlineDialInConferencingBridge -Instance $bridge ``` -This example changes the name of a conference bridge by creating an conference bridge instance, changing the instance's name and then setting the conference bridge to the instance. - +This example changes the name of a conference bridge by creating a conference bridge instance, changing the instance's name and then setting the conference bridge to the instance. ## PARAMETERS @@ -71,8 +69,8 @@ Specifies the globally-unique identifier (GUID) for the audio conferencing bridg ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 1 @@ -87,8 +85,8 @@ Allows you to pass a reference to a Microsoft audio conferencing bridge object t ```yaml Type: ConferencingBridge Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 1 @@ -103,8 +101,8 @@ Specifies the name of the audio conferencing bridge to be modified. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -120,7 +118,7 @@ The Confirm switch causes the command to pause processing, and requires confirma Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -139,8 +137,8 @@ Also, when the default service number is changed, the service number of existing ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -161,7 +159,7 @@ Computer name: -DomainController atl-cs-001 Type: Fqdn Parameter Sets: (All) Aliases: DC -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -178,8 +176,8 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -194,8 +192,8 @@ PARAMVALUE: SwitchParameter ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -210,8 +208,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -226,8 +224,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -244,7 +242,7 @@ By using this switch, you can view what changes would occur without having to co Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -254,7 +252,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -263,4 +261,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingServiceNumber.md b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingServiceNumber.md similarity index 89% rename from skype/skype-ps/skype/Set-CsOnlineDialInConferencingServiceNumber.md rename to teams/teams-ps/teams/Set-CsOnlineDialInConferencingServiceNumber.md index 95068004d7..a64dcc2c2b 100644 --- a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingServiceNumber.md +++ b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingServiceNumber.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencingservicenumber -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinedialinconferencingservicenumber +applicable: Microsoft Teams title: Set-CsOnlineDialInConferencingServiceNumber schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsOnlineDialInConferencingServiceNumber @@ -94,7 +94,6 @@ Set-CsOnlineDialInConferencingServiceNumber -Identity +14255551234 -PrimaryLangu This example sets the primary language to German (Germany) and the secondary languages to US English, Japanese, and UK English for the dial-in service number +14255551234. - ## PARAMETERS ### -Identity @@ -104,8 +103,8 @@ The service number can be specified in the following formats: E.164 number, +\<E ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 1 @@ -120,8 +119,8 @@ Allows you to pass a reference to the Office 365 audio service number object to ```yaml Type: ConferencingServiceNumber Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 1 @@ -137,7 +136,7 @@ The Confirm switch causes the command to pause processing, and requires confirma Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -158,7 +157,7 @@ Computer name: -DomainController atl-cs-001 Type: Fqdn Parameter Sets: (All) Aliases: DC -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -175,8 +174,8 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -195,8 +194,8 @@ Use the `Get-CsOnlineDialInConferencingLanguagesSupported` cmdlet to get a list ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -211,8 +210,8 @@ Including this switch restores all of the default languages for the audio confer ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -233,8 +232,8 @@ Use the `Get-CsOnlineDialInConferencingLanguagesSupported` cmdlet to get a list ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -249,8 +248,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -267,7 +266,7 @@ By using this switch, you can view what changes would occur without having to co Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -277,7 +276,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -286,4 +285,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-CsOnlineDialInConferencingTenantSettings.md b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingTenantSettings.md new file mode 100644 index 0000000000..26cf1b24c2 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingTenantSettings.md @@ -0,0 +1,562 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinedialinconferencingtenantsettings +applicable: Microsoft Teams +title: Set-CsOnlineDialInConferencingTenantSettings +schema: 2.0.0 +--- + +# Set-CsOnlineDialInConferencingTenantSettings + +## SYNOPSIS +Use the `Set-CsOnlineDialInConferencingTenantSettings` to modify the tenant level settings of dial-in conferencing. +Dial-in conferencing tenant settings control the conference experience of users and manage some conferencing administrative functions. + +## SYNTAX + +```powershell +Set-CsOnlineDialInConferencingTenantSettings [-AllowedDialOutExternalDomains <Object>] + [-AllowFederatedUsersToDialOutToSelf <String>] [-AllowFederatedUsersToDialOutToThirdParty <String>] + [-AllowPSTNOnlyMeetingsByDefault <Boolean>] [-AutomaticallyMigrateUserMeetings <Boolean>] + [-AutomaticallyReplaceAcpProvider <Boolean>] [-AutomaticallySendEmailsToUsers <Boolean>] + [-EnableDialOutJoinConfirmation <Boolean>] [-EnableEntryExitNotifications <Boolean>] + [-EnableNameRecording <Boolean>] [-EntryExitAnnouncementsType <String>] [[-Identity] <String>] + [-IncludeTollFreeNumberInMeetingInvites <Boolean>] [-MaskPstnNumbersType <String>] + [-MigrateServiceNumbersOnCrossForestMove <Boolean>] [-PinLength <UInt32>] [-SendEmailFromAddress <String>] + [-SendEmailFromDisplayName <String>] [-SendEmailFromOverride <Boolean>] [-UseUniqueConferenceIds <Boolean>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Dial-in conferencing tenant settings control what functions are available during a conference call. +For example, whether or not entries and exits from the call are announced. +The settings also manage some of the administrative functions, such as when users get notification of administrative actions, like a PIN change. +By contrast, the higher level dial-in conferencing configuration only maintains a flag for whether dial-in conferencing is enabled for your organization. +For more information, see `Get-CsOnlineDialinConferencingTenantConfiguration`. + +There is always a single instance of the dial-in conferencing settings per tenant. +You can modify the settings using `Set-CsOnlineDialInConferencingTenantSettings` and revert those settings to their defaults by using `Remove-CsOnlineDialInConferencingTenantSettings`. + +The following parameters are not applicable to Teams: EnableDialOutJoinConfirmation, IncludeTollFreeNumberInMeetingInvites, MigrateServiceNumbersOnCrossForestMove, and UseUniqueConferenceIds + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsOnlineDialInConferencingTenantSettings -EnableEntryExitNotifications $True -EnableNameRecording $True -PinLength 7 +``` + +This example sets the tenant's conferencing settings to enable entry and exit notifications supported by name recording. +The PIN length is set to 7. + +### -------------------------- Example 2 -------------------------- +``` +Set-CsOnlineDialInConferencingTenantSettings -SendEmailFromOverride $true -SendEmailFromAddress admin@contoso.com -SendEmailFromDisplayName "Conferencing Administrator" +``` + +This example defines the contact information to be used in dial-in conferencing email notifications and enables the default address to be overridden. + +## PARAMETERS + +### -AllowedDialOutExternalDomains + +Used to specify which external domains are allowed for dial-out conferencing. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowFederatedUsersToDialOutToSelf + +Meeting participants can call themselves when they join a meeting. Possible settings are [No|Yes|RequireSameEnterpriseUser]. + This parameter is Microsoft internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowFederatedUsersToDialOutToThirdParty + +Specifies at this scope if dial out to third party participants is allowed. Possible settings are [No|Yes|RequireSameEnterpriseUser]. +This parameter is Microsoft internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPSTNOnlyMeetingsByDefault +Specifies the default value that gets assigned to the "AllowPSTNOnlyMeetings" setting of users when they are enabled for dial-in conferencing, or when a user's dial-in conferencing provider is set to Microsoft. +If set to $true, the "AllowPSTNOnlyMeetings" setting of the user will also be set to true. +If $false, the user setting will be false. +The default value for AllowPSTNOnlyMeetingsByDefault is $false. + +When AllowPSTNOnlyMeetingsByDefault is changed, the value of the "AllowPSTNOnlyMeetings" setting of currently enabled users doesn't change. +The new default value will only be applied to users that are subsequently enabled for dial-in conferencing, or whose provider is changed to Microsoft. + +The "AllowPSTNOnlyMeetings" setting of a user defines if unauthenticated callers can start a meeting if they are the first person to join. +An unauthenticated caller is defined as a participant who joins a meeting over the phone and doesn't provide the organizer PIN when joining the meeting. + +For more information on the "AllowPSTNOnlyMeetings" user setting, see `Set-CsOnlineDialInConferencingUser`. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutomaticallyMigrateUserMeetings + +Specifies if meetings of users in the tenant should automatically be rescheduled via the Meeting Migration Service when there's a change in the users' Cloud PSTN Confernecing coordinates, e.g. when a user is provisioned, de-provisoned, assigned a new default service number etc. If this is false, users will need to manually migrate their conferences using the Meeting Migration tool. +PARAMVALUE: $true | $false + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutomaticallyReplaceAcpProvider + +Specifies if a user already enabled for a 3rd party Audio Conferencing Provider (ACP) should automatically be converted to Microsoft's Online DialIn Conferencing service when a license for Microsoft's service is assigned to the user. If this is false, tenant admins will need to manually provision the user with the Enable-CsOnlineDialInConferencingUser cmdlet with the -ReplaceProvider switch present. +PARAMVALUE: $true | $false + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutomaticallySendEmailsToUsers +Specifies whether advisory emails will be sent to users when the events listed below occur. +Setting the parameter to $true enables the emails to be sent, $false disables the emails. +The default is $true. + +User is enabled or disabled for dial-in conferencing. + +The dial-in conferencing provider is changed either to Microsoft, or from Microsoft to another provider, or none. + +The dial-in conferencing PIN is reset by the tenant administrator. + +Changes to either the user's conference ID, or the user's default dial-in conference number. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableDialOutJoinConfirmation + +Specifies if the callees need to confirm to join the conference call. If true, the callees will hear prompts to ask for confirmation to join the conference call, otherwise callees will join the conference call directly. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableEntryExitNotifications + +Specifies if, by default, announcements are made as users enter and exit a conference call. +Set to $true to enable notifications, $false to disable notifications. +The default is $true. + +This setting can be overridden on a meeting by meeting basis when a user joins a meeting via a Skype for Business client and modifies the Announce when people enter or leave setting on the Skype Meeting Options menu of a meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableNameRecording + +Specifies whether the name of a user is recorded on entry to the conference. +This recording is used during entry and exit notifications. +Set to $true to enable name recording, set to $false to bypass name recording. +The default is $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EntryExitAnnouncementsType + +Specifies if the Entry and Exit Announcement Uses names or tones only. +PARAMVALUE: UseNames | ToneOnly + +```yaml +Type: EntryExitAnnouncementsType +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +This parameter is reserved for internal Microsoft use. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IncludeTollFreeNumberInMeetingInvites +This parameter is obsolete and not functional. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MigrateServiceNumbersOnCrossForestMove + +Specifies whether service numbers assigned to the tenant should be migrated to the new forest of the tenant when the tenant is migrated cross region. If false, service numbers will be released back to stock once the migration completes. This settings does not apply to ported-in numbers that are always migrated. +PARAMVALUE: $true | $false + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Microsoft internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinLength +Specifies the number of digits in the automatically generated PINs. +Organizers can enter their PIN to start a meeting they scheduled if they join via phone and are the first person to join. +The minimum value is 4, the maximum is 12, and the default is 5. + +A user's PIN will only authenticate them as leaders for a meeting they scheduled. +The PIN of a user that did not schedule the meeting will not enable that user to lead the meeting. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendEmailFromAddress +Specifies the email address to use in the "From" contact information on emails that are sent to users to notify them of their dial-in conferencing settings, or when their settings change. +The email address needs to be in the form \<UserAlias\>@\<Domain\>. +For example, "KenMyer@Contoso.com" or "Admin@Contoso.com". + +The SendEmailFromAddress value is used only if the SendEmailFromDisplayName setting is specified, and the SendEmailFromOverride setting is $true. + +Note: The parameter has been deprecated and may be removed in future versions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendEmailFromDisplayName +Specifies the display name to use in the "From" contact information on emails that are sent to users to notify them of their dial-in conferencing settings, or when their settings change. + +The SendEmailFromDisplayName value is used only if the SendEmailFromDisplayName setting is specified, and the SendEmailFromOverride setting is $true. + +Note: The parameter has been deprecated and may be removed in future versions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendEmailFromOverride +Specifies if the contact information on dial-in conferencing notifications will be the default generated by Office 365, or administrator defined values. +Setting SendEmailFromOverride to $true enables the system to use the SendEmailFromAddress and SendEmailFromDisplayName parameter inputs as the "From" contact information. +Setting this parameter to $false will cause email notifications to be sent with the system generated default. +The default is $false. + +SendEmailFromOverride can't be $true if SendEmailFromAddress and SendEmailFromDisplayName aren't specified. + +If you want to change the email address information, you need to make sure that your inbound email policies allow for emails that come from the address specified by the SendEmailFromAddress parameter. + +Note: The parameter has been deprecated and may be removed in future versions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseUniqueConferenceIds + +Specifies if Private Meetings are enabled for the users in this tenant. +PARAMVALUE: $true | $false + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaskPstnNumbersType +This parameter allows tenant administrators to configure masking of PSTN participant phone numbers in the roster view for Microsoft Teams meetings enabled for Audio Conferencing, scheduled within the organization. + +Possible values are: +- MaskedForExternalUsers (masked to external users) +- MaskedForAllUsers (masked for everyone) +- NoMasking (visible to everyone) + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: MaskedForExternalUsers +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsOnlineDialInConferencingTenantSettings](https://learn.microsoft.com/powershell/module/teams/get-csonlinedialinconferencingtenantsettings) + +[Remove-CsOnlineDialInConferencingTenantSettings](https://learn.microsoft.com/powershell/module/teams/remove-csonlinedialinconferencingtenantsettings) diff --git a/teams/teams-ps/teams/Set-CsOnlineDialInConferencingUser.md b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingUser.md new file mode 100644 index 0000000000..a0768687dc --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingUser.md @@ -0,0 +1,400 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinedialinconferencinguser +applicable: Microsoft Teams +title: Set-CsOnlineDialInConferencingUser +schema: 2.0.0 +--- + +# Set-CsOnlineDialInConferencingUser + +## SYNOPSIS + +> [!NOTE] +> The AllowPSTNOnlyMeetings, ResetConferenceId, and ConferenceId parameters will be deprecated on Jan 31, 2022. To allow Teams meeting participants joining via the PSTN to bypass the lobby, use the AllowPSTNUsersToBypassLobby of the [Set-CsTeamsMeetingPolicy cmdlet](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingpolicy). The capabilities associated with the ResetConferenceId and ConferenceId parameters are no longer supported. + +Use the `Set-CsOnlineDialInConferencingUser` cmdlet to modify the properties of a user that has been enabled for Microsoft's audio conferencing service. + +## SYNTAX + +### TenantIdParams (Default) +``` +Set-CsOnlineDialInConferencingUser [-Identity] <UserIdParameter> [-BridgeId <Guid>] + [-BridgeName <String>] [-Tenant <Guid>] [-ServiceNumber <String>] [-TollFreeServiceNumber <String>] [-AllowPSTNOnlyMeetings <Boolean>] [-Force] + [-ResetLeaderPin] [-AllowTollFreeDialIn <Boolean>] [-SendEmailToAddress <String>] + [-SendEmailFromAddress <String>] [-SendEmailFromDisplayName <String>] [-SendEmail] [-DomainController <Fqdn>] [-AsJob] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### TenantDomainParams +``` +Set-CsOnlineDialInConferencingUser [-Identity] <UserIdParameter> [-BridgeId <Guid>] + [-BridgeName <String>] [-TenantDomain <String>] [-ServiceNumber <String>] [-TollFreeServiceNumber <String>] [-AllowPSTNOnlyMeetings <Boolean>] [-Force] + [-ResetLeaderPin] [-AllowTollFreeDialIn <Boolean>] [-SendEmailToAddress <String>] + [-SendEmailFromAddress <String>] [-SendEmailFromDisplayName <String>] [-SendEmail] [-DomainController <Fqdn>] [-AsJob] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The `Set-CsOnlineDialInConferencingUser` cmdlet is used to modify properties for a Microsoft audio conferencing user. +This cmdlet will not work for users with third-party conferencing providers. +The cmdlet will verify that the correct license is assigned to the user. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsOnlineDialInConferencingUser -Identity "Ken Meyers" -ResetLeaderPin -ServiceNumber 14255037265 +``` + +This example shows how to reset the meeting leader's PIN and set the audio conferencing provider default meeting phone number. + +### -------------------------- Example 2 -------------------------- +``` +Set-CsOnlineDialInConferencingUser -Identity "Ken Meyers" -BridgeName "Conference Bridge" +``` + +This example sets a user's conference bridge assignment. + +## PARAMETERS + +### -Identity +Specifies the Identity of the user account to be to be modified. +A user identity can be specified by using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). +You can also reference a user account by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantDomain +Specifies the domain name for the tenant or organization. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPSTNOnlyMeetings +If true, non-authenticated users can start meetings. +If false, non-authenticated callers wait in the lobby until an authenticated user joins, thereby starting the meeting. +An authenticated user is a user who joins the meeting using a Skype for Business client, or the organizer that joined the meeting via dial-in conferencing and was authenticated by a PIN number. +The default is false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BridgeId +Specifies the globally-unique identifier (GUID) for the audio conferencing bridge. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BridgeName +Specifies the name of the audio conferencing bridge. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Specifies the domain controller that's used by the cmdlet to read or write the specified data. +Valid inputs for this parameter include: + +Fully qualified domain name (FQDN): `-DomainController atl-cs-001.Contoso.com` + +Computer name: `-DomainController atl-cs-001` + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResetLeaderPin +Specifies whether to reset the meeting organizer or leaders PIN for meetings. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendEmail +Send an email to the user containing their Audio Conference information. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendEmailFromAddress +You can specify the From Address to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmailFromDisplayName and -SendEmail. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendEmailFromDisplayName +You can specify the Display Name to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmailFromAddress and -SendEmail. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendEmailToAddress +You can specify the To Address to send the email that contains the Audio Conference information. This parameter must be used together with -SendEmail. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ServiceNumber +Specifies the default service number for the user. +The default number is used in meeting invitations. +The cmdlet will verify that the service number is assigned to the user's current conference bridge, or the one the user is being assigned to. + +The service number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Specifies the globally unique identifier (GUID) of your Skype for Business Online tenant account. +For example: `-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"`. +You can find your tenant ID by running this command: `Get-CsTenant | Select-Object DisplayName, TenantID` + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TollFreeServiceNumber +Specifies a toll-free phone number to be used by the user. This number is then used in meeting invitations. The toll-free number can be specified in the following formats: E.164 number, +\<E.164 number\> and tel:\<E.164 number\>. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf parameter is not implemented for this cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTollFreeDialIn +If toll-free numbers are available in your Microsoft Audio Conferencing bridge, this parameter controls if they can be used to join the meetings of a given user. This setting can ONLY be managed using the TeamsAudioConferencingPolicy. By default, AllowTollFreeDialin is always set to True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AsJob +The parameter is used to run commands as background jobs. +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaudioconferencingpolicy) + +[New-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsaudioconferencingpolicy) diff --git a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingUserDefaultNumber.md b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingUserDefaultNumber.md similarity index 80% rename from skype/skype-ps/skype/Set-CsOnlineDialInConferencingUserDefaultNumber.md rename to teams/teams-ps/teams/Set-CsOnlineDialInConferencingUserDefaultNumber.md index 96df66649e..9b13013f9e 100644 --- a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingUserDefaultNumber.md +++ b/teams/teams-ps/teams/Set-CsOnlineDialInConferencingUserDefaultNumber.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinedialinconferencinguserdefaultnumber -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/skype/set-csonlinedialinconferencinguserdefaultnumber +applicable: Microsoft Teams title: Set-CsOnlineDialInConferencingUserDefaultNumber schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsOnlineDialInConferencingUserDefaultNumber @@ -15,6 +15,13 @@ ms.reviewer: ## SYNOPSIS Replace the default toll or toll-free number for all users. +> [!IMPORTANT] +>This command is being deprecated and will not be available after July 7, 2024. If you are using this command to bulk update Audio conferencing Toll or Toll free phone numbers for users in your organization you can do that using the following alternative methods. +> 1. Use a custom Teams audio conferencing policy - [Audio Conferencing toll-free number policies - Microsoft Teams | Microsoft Learn](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-toll-free-numbers-policy) +> 2. Use Set-CsOnlineDialinConferencingUser - [Set-CsOnlineDialInConferencingUser (MicrosoftTeamsPowerShell) | Microsoft Learn](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinedialinconferencinguser?view=teams-ps) +> +>If you need assistance in using any of the above methods to achieve what you previously did with the Set-CsOnlineDialInConferencingUserDefaultNumber command, please open a support case with our customer support team. + ## SYNTAX ### BridgeNameParams @@ -52,17 +59,16 @@ Set-CsOnlineDialInConferencingUserDefaultNumber -FromNumber 14255550100 -ToNumbe This example replaces the default toll or toll-free number for all users who have the number 14255550100 as a default number to the number 14255550101 and starts the process of rescheduling their meetings. - ## PARAMETERS ### -BridgeId -The Bridge Id results from running [Get-CsOnlineDialInConferencingBridge](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingbridge) +The Bridge Id results from running [Get-CsOnlineDialInConferencingBridge](https://learn.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingbridge) For example "9884626f-dcfb-49f4-8025-912f5bc68fdc". You can either specify BridgeName or BridgeId. ```yaml Type: Guid Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -73,13 +79,13 @@ Accept wildcard characters: False ``` ### -BridgeName -The Bridge Name results from running [Get-CsOnlineDialInConferencingBridge](https://docs.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingbridge) +The Bridge Name results from running [Get-CsOnlineDialInConferencingBridge](https://learn.microsoft.com/powershell/module/skype/get-csonlinedialinconferencingbridge) For example "Conference Bridge". You can either specify BridgeName or BridgeId. ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -95,7 +101,7 @@ A String representing the Country or Region this Dial In Conferencing Default nu ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -112,7 +118,7 @@ $null if no number defined. ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -132,7 +138,7 @@ Valid values are ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -148,7 +154,7 @@ The new number to assign, without the + sign, for example 14255550101. ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -164,7 +170,7 @@ A String representing the Area or State this Dial In Conferencing Default number ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -180,7 +186,7 @@ A String representing the Capital or Major City this Dial In Conferencing Defaul ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -228,7 +234,7 @@ The Force switch specifies whether to suppress warning and confirmation messages ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -239,12 +245,12 @@ Accept wildcard characters: False ``` ### -RescheduleMeetings -Sends e-mail notifications to Meeting attendes with the updated settings. +Sends e-mail notifications to Meeting attendees with the updated settings. ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -260,7 +266,7 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -276,7 +282,7 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: (All) -Aliases: +Aliases: Applicable: Skype for Business Online Required: False @@ -303,7 +309,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -312,4 +318,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md b/teams/teams-ps/teams/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md new file mode 100644 index 0000000000..289ee4575e --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md @@ -0,0 +1,184 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlineenhancedemergencyservicedisclaimer +applicable: Microsoft Teams +title: Set-CsOnlineEnhancedEmergencyServiceDisclaimer +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsOnlineEnhancedEmergencyServiceDisclaimer + +## SYNOPSIS +When using Microsoft Teams PSTN Calling Services you need to record your organization's acceptance of the enhanced emergency service terms and conditions. This is done per +country/region and it needs to be done before you can provide PSTN calling services to Microsoft Teams users in the country/region. + +You can record your organization's acceptance using the Set-CsOnlineEnhancedEmergencyServiceDisclaimer cmdlet at any time. If you haven't accepted it for a given country/region +you will be prompted to do so by warning information in the Teams PS Module, when you try to assign a phone number to a Microsoft Teams user, or in the Teams admin center, +when you create an emergency address in a country/region. + +Any tenant administrator can accept the terms and conditions and it only needs to be done once per country/region. + +As the output the cmdlet will show the emergency service disclaimer and that it has been accepted. You can use Get-CsOnlineEnhancedEmergencyServiceDisclaimer to see the status of the emergency service disclaimer. + +## SYNTAX + +``` +Set-CsOnlineEnhancedEmergencyServiceDisclaimer -CountryOrRegion <String> [-Version <String>] [-ForceAccept] + [-Tenant <Guid>] [-DomainController <Fqdn>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You must run this cmdlet prior to assigning Microsoft Calling Plan phone numbers and locations to voice enabled users or accept the similar disclaimer in the Teams admin center. + +Microsoft Calling Plan phone numbers are available in several countries/regions, see [Country and region availability for Audio Conferencing and Calling Plans](https://learn.microsoft.com/MicrosoftTeams/country-and-region-availability-for-audio-conferencing-and-calling-plans/country-and-region-availability-for-audio-conferencing-and-calling-plans) + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsOnlineEnhancedEmergencyServiceDisclaimer -CountryOrRegion US +``` + +This example accepts the U.S. +version of the enhanced emergency service terms and conditions. + +## PARAMETERS + +### -CountryOrRegion +Specifies the region or country whose terms and conditions you wish to accept. You need to use the ISO 31661-1 alpha-2 2 letter code for the country. For example for the United States it must be specified as "US" and for Denmark it must be specified as "DK". + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForceAccept +This parameter is reserved for internal Microsoft use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Version +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsOnlineEnhancedEmergencyServiceDisclaimer](https://learn.microsoft.com/powershell/module/teams/get-csonlineenhancedemergencyservicedisclaimer) diff --git a/teams/teams-ps/teams/Set-CsOnlineLisCivicAddress.md b/teams/teams-ps/teams/Set-CsOnlineLisCivicAddress.md new file mode 100644 index 0000000000..49f8ab38fe --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineLisCivicAddress.md @@ -0,0 +1,481 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlineliscivicaddress +applicable: Microsoft Teams +title: Set-CsOnlineLisCivicAddress +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineLisCivicAddress + +## SYNOPSIS +Use the \`Set-CsOnlineLisCivicAddress\` cmdlet to modify an existing civic address which has not been validated. +Validated civic addresses cannot be modified. + +> [!IMPORTANT] +> Due to a current issue, the parameters **-CompanyName** and **-CountryOrRegion** are required as an interim workaround for this cmdlet. + +> [!Note] +> This cmdlet is only available for public use with limited countries and certain fields. The remaining countries and fields are for Microsoft internal use only. + +## SYNTAX + +``` +Set-CsOnlineLisCivicAddress -CivicAddressId <Guid> [-CompanyName <String>] [-CompanyTaxId <String>] + [-HouseNumber <String>] [-HouseNumberSuffix <String>] [-StreetName <String>] [-StreetSuffix <String>] + [-PreDirectional <String>] [-PostDirectional <String>] [-City <String>] [-CityAlias <String>] + [-StateOrProvince <String>] [-CountryOrRegion <String>] [-PostalCode <String>] [-Description <String>] + [-ValidationStatus <String>] [-Latitude <String>] [-Longitude <String>] [-Confidence <String>] + [-Elin <String>] [-IsAzureMapValidationRequired <String>] [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +Use the `Set-CsOnlineLisCivicAddress` cmdlet to modify limited fields of an existing civic address. + +Editing address using this cmdlet is restricted to the following countries/regions: +Australia, Brazil, Canada, Croatia, Czech Republic, Estonia, Hong Kong, Hungary, Israel, Japan, Latvia, Lithuania, Mexico, New Zealand, Poland, Puerto Rico, Romania, Singapore, South Korea, Slovenia, South Africa, United States. + +If the user runs this cmdlet on one of the unsupported countries, it may interfere with number assignment and potentially is against regulatory requirements, so public use of the API is limited to the above countries/regions. + +## EXAMPLES + +### Example 1 +```powershell +Set-CsOnlineLisCivicAddress -CivicAddressId a363a9b8-1acd-41de-916a-296c7998a024 -Description "City Center" -CompanyName Contoso +``` + +This example modifies the description and company name of the civic address with the identity a363a9b8-1acd-41de-916a-296c7998a024. + +### Example 2 +```powershell +Set-CsOnlineLisCivicAddress -CivicAddressId a363a9b8-1acd-41de-916a-296c7998a024 -Latitude 47.63952 -Longitude -122.12781 -ELIN MICROSOFT_ELIN +``` + +This example modifies the latitude, longitude and ELIN name of the civic address with the identity a363a9b8-1acd-41de-916a-296c7998a024. + +## PARAMETERS + +### -CivicAddressId +Specifies the unique identifier of the civic address to be modified. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -City +Specifies a new city for the civic address. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CityAlias +Short form of the city name. +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompanyName +Specifies a new company name for the civic address. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompanyTaxId +Used to store TaxId for regulatory reasons. +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CountryOrRegion +Specifies a new country or region for the civic address. +For public use, restricted to the following countries: + +**AU, BR, CA, HR, CZ, EE, HK, HU, IL, JP, LV, LT, MX, NZ, PL, PR, RO, SG, KR, SI, ZA, US** + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies a new description for the civic address. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HouseNumber +Specifies the new numeric portion of the civic address. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HouseNumberSuffix +Specifies the new numeric suffix of the new civic address. +For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostalCode +Specifies the new postal code of the civic address. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostDirectional +Specifies the new directional attribute of the civic address which follows the street name. +For example, "425 Smith Avenue NE". + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreDirectional +Specifies the new directional attribute of the civic address which precedes the street name. +For example, "425 NE Smith Avenue ". + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StateOrProvince +Specifies the new state or province of the civic address. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreetName +Specifies the new street name of the civic address. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreetSuffix +Specifies the new modifier of the street name of the new civic address. +The street suffix will typically be something like street, avenue, way, or boulevard. + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ValidationStatus +Microsoft internal use only + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confidence +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Elin +Specifies the Emergency Location Identification Number. +This is used in Direct Routing EGW scenarios. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Latitude +Specifies the angular distance of a place north or south of the earth's equator in the decimal degrees format. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Longitude +Specifies the angular distance of a place east or west of the meridian at Greenwich, England, in the decimal degrees format. Publicly editable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsAzureMapValidationRequired +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/get-csonlineliscivicaddress) + +[New-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/new-csonlineliscivicaddress) + +[Remove-CsOnlineLisCivicAddress](https://learn.microsoft.com/powershell/module/teams/remove-csonlineliscivicaddress) diff --git a/teams/teams-ps/teams/Set-CsOnlineLisLocation.md b/teams/teams-ps/teams/Set-CsOnlineLisLocation.md new file mode 100644 index 0000000000..d93fd56f49 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineLisLocation.md @@ -0,0 +1,504 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinelislocation +applicable: Microsoft Teams +title: Set-CsOnlineLisLocation +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineLisLocation + +## SYNOPSIS +Use the \`Set-CsOnlineLisLocation\` cmdlet to modify an existing emergency dispatch location. There can be multiple locations in a civic address. +Typically the civic address designates the building, and locations are specific parts of that building such as a floor, office, or wing. + +## SYNTAX + +### UseCivicAddressId (Default) +``` +Set-CsOnlineLisLocation -CivicAddressId <guid> [-City <string>] [-CityAlias <string>] [-CompanyName <string>] [-CompanyTaxId <string>] + [-Confidence <string>] [-CountryOrRegion <string>] [-Description <string>] [-Elin <string>] [-Force] [-HouseNumber <string>] [-HouseNumberSuffix <string>] + [-Latitude <string>] [-Longitude <string>] [-PostalCode <string>] [-PostDirectional <string>] [-PreDirectional <string>] + [-StateOrProvince <string>] [-StreetName <string>] [-StreetSuffix <string>] [-IsAzureMapValidationRequired <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UseLocationId +``` +Set-CsOnlineLisLocation -LocationId <guid> [-CityAlias <string>] [-Confidence <string>] [-Elin <string>] [-Force] + [-Latitude <string>] [-Longitude <string>] [-Location <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +## EXAMPLES + +### Example 1 +```powershell +Set-CsOnlineLisLocation -LocationId 5aa884e8-d548-4b8e-a289-52bfd5265a6e -Location "B5 2nd Floor" +``` + +This example changes the location description of the location specified by its location identity. + +## PARAMETERS + +### -CivicAddressId +Specifies the unique identifier of the civic address that contains the location to be modified. +Civic address identities can be discovered by using the \`Get-CsOnlineLisCivicAddress\` cmdlet. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: Guid +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -LocationId +Specifies the unique identifier of the location to be modified. Location identities can be discovered by using the \`Get-CsOnlineLisLocation\` cmdlet. + +```yaml +Type: Guid +Parameter Sets: UseLocationId +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -City +Specifies the city of the civic address. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CityAlias + +**Note:** This parameter has been deprecated from the Teams PowerShell Module version 3.0.0 or later. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CompanyName +Specifies the name of your organization. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -CompanyTaxId +The company tax ID. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Confidence + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CountryOrRegion +Specifies the country or region of the civic address. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Description +Specifies an administrator defined description of the civic address. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Elin +Specifies the Emergency Location Identification Number. This is used in Direct Routing EGW scenarios. + +**Note:** You can set or change the ELIN, but you can't clear its value. If you need to clear the value, you should recreate the location. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -HouseNumber +Specifies the numeric portion of the civic address. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -HouseNumberSuffix +Specifies the numeric suffix of the civic address. +For example, if the property was multiplexed, the HouseNumberSuffix parameter would be the multiplex specifier: "425A Smith Avenue", or "425B Smith Avenue". + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Latitude +Specifies the angular distance of a place north or south of the earth's equator using the decimal degrees format. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Longitude +Specifies the angular distance of a place east or west of the meridian at Greenwich, England, using the decimal degrees format. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` +### -Location +Specifies an administrator defined description of the new location. For example, "2nd Floor Cafe", "Main Lobby", or "Office 250". + +```yaml +Type: String +Parameter Sets: UseLocationId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PostalCode +Specifies the postal code of the civic address. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PostDirectional +Specifies the directional attribute of the civic address which follows the street name. +For example, "425 Smith Avenue NE". + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -PreDirectional +Specifies the directional attribute of the civic address which precedes the street name. For example, "425 NE Smith Avenue ". + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StateOrProvince +Specifies the state or province of the civic address. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StreetName +Specifies the street name of the civic address. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -StreetSuffix +Specifies a modifier of the street name of the civic address. The street suffix will typically be something like street, avenue, way, or boulevard. + +**Note:** This parameter is not supported and will be deprecated. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teans + +Required: False +Position: Named +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -IsAzureMapValidationRequired +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: UseCivicAddressId +Aliases: +Applicable: Microsoft Teans + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +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: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/new-csonlinelislocation) + +[Get-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/get-csonlinelislocation) + +[Remove-CsOnlineLisLocation](https://learn.microsoft.com/powershell/module/teams/remove-csonlinelislocation) diff --git a/teams/teams-ps/teams/Set-CsOnlineLisPort.md b/teams/teams-ps/teams/Set-CsOnlineLisPort.md new file mode 100644 index 0000000000..39f8049001 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineLisPort.md @@ -0,0 +1,234 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinelisport +applicable: Microsoft Teams +title: Set-CsOnlineLisPort +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineLisPort + +## SYNOPSIS +Creates a Location Information Server (LIS) port, creates an association between a port and a location, or modifies an existing port and its associated location. The association between a port and location is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. + +## SYNTAX + +``` +Set-CsOnlineLisPort [-ChassisID] <string> -LocationId <guid> -PortID <string> [-Description <string>] [-Force] [-IsDebug <bool>] + [-NCSApiUrl <string>] [-TargetStore <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet allows the administrator to map physical locations to the port through which the client is connected. + +## EXAMPLES + +### Example 1 +``` +Set-CsOnlineLisPort -PortID 12174 -ChassisID 0B-23-CD-16-AA-CC -Description "LisPort 12174" -LocationId efd7273e-3092-4a56-8541-f5c896bb6fee +``` + +Example 1 creates the association between port "12174" and LocationId "efd7273e-3092-4a56-8541-f5c896bb6fee". + +### Example 2 +``` +Set-CsOnlineLisPort -PortID 0A-25-55-AB-CD-FF -ChassisID 0B-23-CD-16-AA-CC -Description "LisPort 0A-25-55-AB-CD-FF" -LocationId efd7273e-3092-4a56-8541-f5c896bb6fee +``` + +Example 2 creates the association between port "0A-25-55-AB-CD-FF" and LocationId "efd7273e-3092-4a56-8541-f5c896bb6fee". + +### Example 3 +``` +Set-CsOnlineLisPort -PortID 12174 -ChassisID 55123 -Description "LisPort 12174" -LocationId efd7273e-3092-4a56-8541-f5c896bb6fee +``` + +Example 3 creates the association between port "12174" and LocationId "efd7273e-3092-4a56-8541-f5c896bb6fee". (Note: in this example, ChassisID sub-type is InterfaceName) + +## PARAMETERS + +### -ChassisID +If ChassisID sub type is a MAC Address then this value must be in a string format in the following representation nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. Otherwise, (different sub type, such as Interface Name), then this value must be in a string format as set on the switch + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -LocationId +Specifies the unique identifier of the location to be modified. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PortID +If the PortID subtype is a MAC Address, this value must be in a string format in the following representation nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. Otherwise (different subtype, such as Interface Name), this value must be in a string format as set on the switch. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies the administrator defined description of the port. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDebug +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NCSApiUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Guid + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineLisPort](https://learn.microsoft.com/powershell/module/teams/get-csonlinelisport) + +[Remove-CsOnlineLisPort](https://learn.microsoft.com/powershell/module/teams/remove-csonlinelisport) diff --git a/skype/skype-ps/skype/Set-CsOnlineLisSubnet.md b/teams/teams-ps/teams/Set-CsOnlineLisSubnet.md similarity index 83% rename from skype/skype-ps/skype/Set-CsOnlineLisSubnet.md rename to teams/teams-ps/teams/Set-CsOnlineLisSubnet.md index 0b5d1f24a0..ae42f3ce2d 100644 --- a/skype/skype-ps/skype/Set-CsOnlineLisSubnet.md +++ b/teams/teams-ps/teams/Set-CsOnlineLisSubnet.md @@ -1,11 +1,11 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinelissubnet -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinelissubnet +applicable: Microsoft Teams title: Set-CsOnlineLisSubnet schema: 2.0.0 -author: kaishuipinggai -ms.author: junya +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -27,23 +27,24 @@ Enhanced 9-1-1 allows an emergency operator to identify the location of a caller The location ID which is associating with the subnet is not required to be the existing location. +LIS subnets must be defined by the Network ID matching the subnet IP range assigned to clients. For example, the network ID for a client IP/mask of 10.10.10.150/25 is 10.10.10.128. For more information, see [Understand TCP/IP addressing and subnetting basics](https://learn.microsoft.com/troubleshoot/windows-client/networking/tcpip-addressing-and-subnetting). + ## EXAMPLES -### -------------------------- Example 1 -------------------------- +### Example 1 ``` -Set-CsOnlineLisSubnet -Subnet 10.10.10.10 -LocationId f037a9ad-4334-455a-a1c5-3838ec0f5d02 -Description "Subnet 10.10.10.10" +Set-CsOnlineLisSubnet -Subnet 10.10.10.128 -LocationId f037a9ad-4334-455a-a1c5-3838ec0f5d02 -Description "Subnet 10.10.10.128" ``` -Example 1 creates the Location Information Service subnet "10.10.10.10" associated to Location ID "f037a9ad-4334-455a-a1c5-3838ec0f5d02". +Example 1 creates the Location Information Service subnet "10.10.10.128" associated to Location ID "f037a9ad-4334-455a-a1c5-3838ec0f5d02". -### -------------------------- Example 2 -------------------------- +### Example 2 ``` Set-CsOnlineLisSubnet -Subnet 2001:4898:e8:6c:90d2:28d4:76a4:ec5e -LocationId f037a9ad-4334-455a-a1c5-3838ec0f5d02 -Description "Subnet 2001:4898:e8:6c:90d2:28d4:76a4:ec5e" ``` Example 2 creates the Location Information Service subnet in IPv6 format "2001:4898:e8:6c:90d2:28d4:76a4:ec5e" associated to Location ID "f037a9ad-4334-455a-a1c5-3838ec0f5d02". - ## PARAMETERS ### -Confirm @@ -53,7 +54,7 @@ Prompts you for confirmation before running the cmdlet. Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -69,7 +70,7 @@ Specifies the administrator defined description of the Location Information Serv Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -87,7 +88,7 @@ If the Force switch isn't provided in the command, you're prompted for administr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -103,7 +104,7 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -119,7 +120,7 @@ Specifies the unique identifier of the location to be modified. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: Named @@ -135,7 +136,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -151,7 +152,7 @@ The IP address of the subnet. This value can be either IPv4 or IPv6 format. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: 1 @@ -167,7 +168,7 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -183,7 +184,7 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: 0 @@ -200,7 +201,7 @@ The cmdlet is not run. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -212,24 +213,16 @@ Accept wildcard characters: False ### 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/?LinkID=113216). - ## INPUTS - ### System.Guid - ### System.String - ## OUTPUTS - ### System.Object - ## NOTES - ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-CsOnlineLisSwitch.md b/teams/teams-ps/teams/Set-CsOnlineLisSwitch.md new file mode 100644 index 0000000000..71e862e8a2 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineLisSwitch.md @@ -0,0 +1,205 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinelisswitch +applicable: Microsoft Teams +title: Set-CsOnlineLisSwitch +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineLisSwitch + +## SYNOPSIS +Creates a Location Information Server (LIS) switch, creates an association between a switch and a location, or modifies an existing switch and its associated location. The association between a switch and location is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. + +## SYNTAX + +``` +Set-CsOnlineLisSwitch [-ChassisID] <string> -LocationId <guid> [-Description <string>] [-Force] [-IsDebug <bool>] + [-NCSApiUrl <string>] [-TargetStore <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet allows the administrator to map physical locations to the network switch through which the client is connected. + +## EXAMPLES + +### Example 1 +``` +Set-CsOnlineLisSwitch -ChassisID B8-BE-BF-4A-A3-00 -Description "DKSwitch1" -LocationId 9905bca0-6fb0-11ec-84a4-25019013784a +``` + +Example 1 creates a switch with Chassis ID "B8-BE-BF-4A-A3-00", and associates it with location ID 9905bca0-6fb0-11ec-84a4-25019013784a. + +## PARAMETERS + +### -ChassisID +If ChassisID sub type is a MAC Address then this value must be in a string format in the following representation nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. +Otherwise, (different sub type, such as Interface Name), then this value must be in a string format as set on the switch + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -LocationId +The name for this location. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies the administrator defined description of the switch. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDebug +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NCSApiUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Guid + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineLisSwitch](https://learn.microsoft.com/powershell/module/teams/get-csonlinelisswitch) + +[Remove-CsOnlineLisSwitch](https://learn.microsoft.com/powershell/module/teams/remove-csonlinelisswitch) diff --git a/teams/teams-ps/teams/Set-CsOnlineLisWirelessAccessPoint.md b/teams/teams-ps/teams/Set-CsOnlineLisWirelessAccessPoint.md new file mode 100644 index 0000000000..75045602f9 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineLisWirelessAccessPoint.md @@ -0,0 +1,215 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlineliswirelessaccesspoint +applicable: Microsoft Teams +title: Set-CsOnlineLisWirelessAccessPoint +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineLisWirelessAccessPoint + +## SYNOPSIS +Creates a Location Information Server (LIS) wireless access point (WAP), creates an association between a WAP and a location, or modifies an existing WAP and its associated location. The association between a WAP and location is used in an Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementation to notify an emergency services operator of the caller's location. + +## SYNTAX + +``` +Set-CsOnlineLisWirelessAccessPoint [-BSSID] <string> -LocationId <guid> [-Description <string>] [-Force] [-IsDebug <bool>] [-NCSApiUrl <string>] + [-TargetStore <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Enhanced 9-1-1 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over Internet Protocol (VoIP) connection, that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller's location. This cmdlet allows the administrator to map physical locations to the WAP through which calls will be routed. + +The BSSID (Basic Service Set Identifiers) is used to describe sections of a wireless local area network. It is the MAC of the 802.11 side of the access point. The BSSID parameter in this command also supports the wildcard format to cover all BSSIDs in a range which share the same description and Location ID. The wildcard '*' can be on either the last one or two character(s). + +If a BSSID with wildcard format is already existing, the request for adding one more new BSSID which is within this wildcard range and with the same location ID will not be accepted. + +## EXAMPLES + +### Example 1 +``` +Set-CsOnlineLisWirelessAccessPoint -BSSID F0-6E-0B-C2-03-23 -Description "USWAP1" -LocationId d7714269-ee52-4635-97b0-d7c228801d24 +``` + +Example 1 creates the wireless access point with BSSID "F0-6E-0B-C2-03-23", associated with location ID d7714269-ee52-4635-97b0-d7c228801d24. + +### Example 2 +``` +Set-CsOnlineLisWirelessAccessPoint -BSSID F0-6E-0B-C2-04-* -LocationId b2804a1a-e4cf-47df-8964-3eaf6fe1ae3a -Description 'SEWAPs' +``` + +Example 2 creates the wireless access point with Chassis ID "F0-6E-0B-C2-04-*", associated with location ID b2804a1a-e4cf-47df-8964-3eaf6fe1ae3a. BSSID "F0-6E-0B-C2-04-*" is in wildcard format which is equivalent to adding all BSSIDs with the same LocationID in the range "F0-6E-0B-C2-04-[0-9A-F][0-9A-F]". + +## PARAMETERS + +### -BSSID +The Basic Service Set Identifier (BSSID) of the wireless access point. This value must be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. If an entry with the specified BSSID value does not exist, a new WAP will be created. If an entry with the specified BSSID already exists, that entry will be replaced. It can be presented in wildcard format. The wildcard '*' can be on either the last one or two character(s). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -LocationId +The name for this location. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Specifies the administrator defined description of the WAP. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. +It can be useful in scripting to suppress interactive prompts. +If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsDebug +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NCSApiUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetStore +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +### System.Guid + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineLisWirelessAccessPoint](https://learn.microsoft.com/powershell/module/teams/get-csonlineliswirelessaccesspoint) + +[Remove-CsOnlineLisWirelessAccessPoint](https://learn.microsoft.com/powershell/module/teams/remove-csonlineliswirelessaccesspoint) diff --git a/teams/teams-ps/teams/Set-CsOnlinePSTNGateway.md b/teams/teams-ps/teams/Set-CsOnlinePSTNGateway.md new file mode 100644 index 0000000000..aa577953e6 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlinePSTNGateway.md @@ -0,0 +1,429 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinepstngateway +applicable: Microsoft Teams +title: Set-CsOnlinePSTNGateway +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlinePSTNGateway + +## SYNOPSIS +Modifies the previously defined Session Border Controller (SBC) Configuration that describes the settings for the peer entity. This cmdlet was introduced with Microsoft Phone System Direct Routing. + +## SYNTAX + +``` +Set-CsOnlinePSTNGateway [[-Identity] <string>] [-BypassMode <string>] [-Description <string>] [-Enabled <boolean>] + [-FailoverResponseCodes <string>] [-FailoverTimeSeconds <int>] [-ForwardCallHistory <boolean>] [-ForwardPai <boolean>] [-GatewayLbrEnabledUserOverride <boolean>] + [-GatewaySiteId <string>] [-GatewaySiteLbrEnabled <boolean>] [-InboundPstnNumberTranslationRules <Object>] [-InboundTeamsNumberTranslationRules <Object>] + [-MaxConcurrentSessions <int>] [-MediaBypass <boolean>] [-MediaRelayRoutingLocationOverride <string>] [-OutboundPstnNumberTranslationRules <Object>] + [-OutboundTeamsNumberTranslationRules <Object>] [-PidfLoSupported <boolean>] [-ProxySbc <string>] [-SendSipOptions <boolean>] [-SipSignalingPort <int>] + [-WhatIf] [-Confirm] [<CommonParameters>] + ``` + +## DESCRIPTION +Use this cmdlet to modify the configuration of the previously created Session Border Controller (SBC) configuration. Each configuration contains specific settings for an SBC. These settings configure such entities as SIP signaling port, whether media bypass is enabled on this SBC, will the SBC send SIP options, specify the limit of maximum concurrent sessions, The cmdlet also let drain the SBC by setting parameter -Enabled to true or false state. When the Enabled parameter set to $false, the SBC will continue existing calls, but all new calls routed to another SBC in a route (if exists). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsOnlinePSTNGateway -Identity sbc.contoso.com -Enabled $true +``` + +This example enables previously created SBC with Identity (and FQDN) sbc.contoso.com. All others parameters will stay default. + +### Example 2 +```powershell +PS C:\> Set-CsOnlinePSTNGateway -Identity sbc.contoso.com -SIPSignalingPort 5064 -ForwardPAI $true -Enabled $true +``` + +This example modifies the configuration of an SBC with identity (and FQDN) sbc.contoso.com. It changes the SIPSignalingPort to 5064 and enabled P-Asserted-Identity field on outbound connections (outbound from Direct Routing to SBC). For each outbound to SBC session, the Direct Routing interface will report in P-Asserted-Identity fields the TEL URI and SIP address of the user who made a call. This is useful when a tenant administrator set identity of the caller as "Anonymous" or a general number of the company, but for the billing purposes the real identity of the user should be reported. + +## PARAMETERS + +### -Description +Free-format string to describe the gateway. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +Used to enable this SBC for outbound calls. Can be used to temporarily remove the SBC from service while it is being updated or during maintenance. Note if the parameter is not set the SBC will be created as disabled (default value -Enabled $false). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FailoverResponseCodes +If Direct Routing receives any 4xx or 6xx SIP error code in response on outgoing Invite (outgoing means call from a Teams client to PSTN with traffic flow :Teams Client -> +Direct Routing -> SBC -> Telephony network) the call is considered completed by default. +Setting the SIP codes in this parameter forces Direct Routing on receiving the specified codes try another SBC (if another SBC exists in the voice routing policy of the user). +Please find more in "Reference" section of "Phone System Direct Routing" documentation + +Setting this parameter overwrites the default values, so if you want to include the default values, please add them to string. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: 408, 503, 504 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FailoverTimeSeconds +When set to 10 (default value), outbound calls that are not answered by the gateway within 10 seconds are routed to the next available trunk; if there are no additional trunks, then the call is automatically dropped. In an organization with slow networks and slow gateway responses, that could potentially result in calls being dropped unnecessarily. The default value is 10. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: 10 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardCallHistory +Indicates whether call history information will be forwarded through the trunk. If enabled, the Office 365 PSTN Proxy sends two headers: History-info and Referred-By. The default value is False ($False). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardPai +Indicates whether the P-Asserted-Identity (PAI) header will be forwarded along with the call. The PAI header provides a way to verify the identity of the caller. The default value is False ($False). Setting this parameter to $true will render the from header anonymous, in accordance of RFC5379 and RFC3325. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GatewaySiteId +PSTN Gateway Site Id. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GatewayLbrEnabledUserOverride +Allows an LBR enabled user working from a network site outside the corporate network or a network site on the corporate network not configured using a tenant network site to make outbound PSTN calls or receive inbound PSTN calls via an LBR enabled gateway. The default value is False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GatewaySiteLbrEnabled +Used to enable this SBC to report assigned site location. Site location is used for Location Based Routing. When this parameter is turned on, the SBC will report the site name as defined by tenant administrator. On incoming call to a Teams user the value of the site assigned to the SBC is compared with the value of the site assigned to the user to make a routing decision. The parameter is mandatory for enabling Location Based Routing feature. The default value is False ($False). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The parameter is mandatory when modifying an existing SBC. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaxConcurrentSessions +Used by the alerting system. When any value is set, the alerting system will generate an alert to the tenant administrator when the number of concurrent session is 90% or higher than this value. If this parameter is not set, the alerts are not generated. However, the monitoring system will report the number of concurrent sessions every 24 hours. + +```yaml +Type: System.Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaBypass +Parameter indicated of the SBC supports Media Bypass and the administrator wants to use it for this SBC. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaRelayRoutingLocationOverride + +Allows selecting path for media manually. Direct Routing assigns a datacenter for media path based on the public IP of the SBC. We always select closest to the SBC datacenter. However, in some cases a public IP from for example a US range can be assigned to an SBC located in Europe. In this case we will be using not optimal media path. We only recommend setting this parameter if the call logs clearly indicate that automatic assignment of the datacenter for media path does not assign the closest to the SBC datacenter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SendSipOptions +Defines if an SBC will or will not send the SIP options. If disabled, the SBC will be excluded from Monitoring and Alerting system. We highly recommend that you enable SIP options. Default value is True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $true +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SipSignalingPort +Listening port used for communicating with Direct Routing services by using the Transport Layer Security (TLS) protocol. The value must be between 1 and 65535. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BypassMode +Possible values are "None", "Always" and "OnlyForLocalUsers". By setting "Always" mode you indicate that your network is fully routable. If a user usually in site "Seattle", travels to site "Tallinn" and tries to use SBC located in Seattle we will try to deliver the traffic to Seattle assuming that there is connection between Tallinn and Seattle offices. With "OnlyForLocaUsers" you indicate that there is no direct connection between sites. In example above, the traffic will not be send directly from Tallinn to Seattle. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundTeamsNumberTranslationRules +This parameter assigns an ordered list of Teams translation rules, that apply to Teams numbers on inbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundPSTNNumberTranslationRules +Creates an ordered list of Teams translation rules, that apply to PSTN number on inbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutboundTeamsNumberTranslationRules +Creates an ordered list of Teams translation rules, that apply to Teams Number on outbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OutboundPSTNNumberTranslationRules +Assigns an ordered list of Teams translation rules, that apply to PSTN number on outbound direction. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PidfloSupported +Enables PIDF-LO support on the PSTN Gateway. If turned on the .xml body payload is sent to the SBC with the location details of the user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: $false +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxySbc +The FQDN of the proxy SBC. Used in Local Media Optimization configurations. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/new-csonlinepstngateway) + +[Get-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/get-csonlinepstngateway) + +[Remove-CsOnlinePSTNGateway](https://learn.microsoft.com/powershell/module/teams/remove-csonlinepstngateway) diff --git a/teams/teams-ps/teams/Set-CsOnlinePstnUsage.md b/teams/teams-ps/teams/Set-CsOnlinePstnUsage.md new file mode 100644 index 0000000000..549dcdcc10 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlinePstnUsage.md @@ -0,0 +1,137 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinepstnusage +applicable: Microsoft Teams +title: Set-CsOnlinePstnUsage +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlinePstnUsage + +## SYNOPSIS +Modifies a set of strings that identify the allowed online public switched telephone network (PSTN) usages. This cmdlet can be used to add usages to the list of online PSTN usages or remove usages from the list. + +## SYNTAX + +### Identity (Default) +``` +Set-CsOnlinePstnUsage [[-Identity] <string>] [-Usage <Object>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Online PSTN usages are string values that are used for call authorization. An online PSTN usage links an online voice policy to a route. The `Set-CsOnlinePstnUsage` cmdlet is used to add or remove phone usages to or from the usage list. This list is global so it can be used by policies and routes throughout the tenant. + +This cmdlet is used when configuring Microsoft Phone System Direct Routing. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Set-CsOnlinePstnUsage -Identity global -Usage @{add="International"} +``` + +This command adds the string "International" to the current list of available PSTN usages. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Set-CsOnlinePstnUsage -Identity global -Usage @{remove="Local"} +``` + +This command removes the string "Local" from the list of available PSTN usages. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> Set-CsOnlinePstnUsage -Usage @{remove="Local"} +``` + +The command in this example performs the exact same action as the command in Example 2: it removes the "Local" PSTN usage. This example shows the command without the Identity parameter specified. The only Identity available to the Set-CsOnlinePstnUsage cmdlet is the Global identity; omitting the Identity parameter defaults to Global. + +### -------------------------- Example 4 -------------------------- +``` +PS C:\> Set-CsOnlinePstnUsage -Usage @{replace="International","Restricted"} +``` + +This command replaces everything in the usage list with the values International and Restricted. All previously existing usages are removed. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The scope at which these settings are applied. The Identity for this cmdlet is always Global. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Usage +Contains a list of allowable usage strings. These entries can be any string value. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsOnlinePstnUsage](https://learn.microsoft.com/powershell/module/teams/get-csonlinepstnusage) diff --git a/skype/skype-ps/skype/Set-CsOnlineSchedule.md b/teams/teams-ps/teams/Set-CsOnlineSchedule.md similarity index 79% rename from skype/skype-ps/skype/Set-CsOnlineSchedule.md rename to teams/teams-ps/teams/Set-CsOnlineSchedule.md index f78e4ad58e..7f4392b0fa 100644 --- a/skype/skype-ps/skype/Set-CsOnlineSchedule.md +++ b/teams/teams-ps/teams/Set-CsOnlineSchedule.md @@ -1,19 +1,19 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlineschedule -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlineschedule +applicable: Microsoft Teams title: Set-CsOnlineSchedule schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsOnlineSchedule ## SYNOPSIS -Use the Set-CsOnlineSchedule cmdlet to remove a schedule. +Use the Set-CsOnlineSchedule cmdlet to update a schedule. ## SYNTAX ```powershell @@ -28,13 +28,12 @@ The Set-CsOnlineSchedule cmdlet lets you modify the properties of a schedule. ### -------------------------- Example 1 -------------------------- ```powershell $schedule = Get-CsOnlineSchedule -Id "fa9081d6-b4f3-5c96-baec-0b00077709e5" -$schedule.Name = "Chrismas Holiday" +$schedule.Name = "Christmas Holiday" Set-CsOnlineSchedule -Instance $schedule ``` This example modifies the name of the schedule that has a Id of fa9081d6-b4f3-5c96-baec-0b00077709e5. - ### -------------------------- Example 2 -------------------------- ```powershell $schedule = Get-CsOnlineSchedule -Id "fa9081d6-b4f3-5c96-baec-0b00077709e5" @@ -55,18 +54,16 @@ Set-CsOnlineSchedule -Instance $schedule This example updates an existing holiday schedule, adding a new date/time range to it. - ## PARAMETERS ### -Instance The Instance parameter is the object reference to the schedule to be modified. - ```yaml Type: Object Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: True Position: 0 @@ -81,7 +78,7 @@ Accept wildcard characters: False Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -91,23 +88,21 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### Microsoft.Rtc.Management.Hosted.Online.Models.Schedule The modified instance of the `Microsoft.Rtc.Management.Hosted.Online.Models.Schedule` object. - ## OUTPUTS ### System.Void - ## NOTES ## RELATED LINKS -[New-CsOnlineSchedule](New-CsOnlineSchedule.md) +[New-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/new-csonlineschedule) -[Remove-CsOnlineSchedule](Remove-CsOnlineSchedule.md) +[Remove-CsOnlineSchedule](https://learn.microsoft.com/powershell/module/teams/remove-csonlineschedule) diff --git a/teams/teams-ps/teams/Set-CsOnlineVoiceApplicationInstance.md b/teams/teams-ps/teams/Set-CsOnlineVoiceApplicationInstance.md new file mode 100644 index 0000000000..f62687992e --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineVoiceApplicationInstance.md @@ -0,0 +1,175 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceapplicationinstance +applicable: Microsoft Teams +title: Set-CsOnlineVoiceApplicationInstance +ms.reviewer: +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +--- + +# Set-CsOnlineVoiceApplicationInstance + +## SYNOPSIS +The `Set-CsOnlineVoiceApplicationInstance` modifies an application instance in Microsoft Entra ID. + +**Note**: This cmdlet has been deprecated. Use the new [Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) and +[Remove-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment) cmdlets instead. + +## SYNTAX +``` +Set-CsOnlineVoiceApplicationInstance [[-Identity] <String>] + [-Confirm] + [-DomainController <Fqdn>] + [-Force] + [-TelephoneNumber <String>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet is used to modify an application instance in Microsoft Entra ID. + +## EXAMPLES + +### Example 1 +```powershell +Set-CsOnlineVoiceApplicationInstance -Identity testra1@contoso.com -TelephoneNumber +14255550100 +``` + +This example sets a phone number to the resource account testra1@contoso.com. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: DC + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The user principal name (UPN) of the resource account in Microsoft Entra ID. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TelephoneNumber +The phone number to be assigned to the resource account. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can return your tenant ID by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstance) diff --git a/teams/teams-ps/teams/Set-CsOnlineVoiceRoute.md b/teams/teams-ps/teams/Set-CsOnlineVoiceRoute.md new file mode 100644 index 0000000000..e88a324e6f --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineVoiceRoute.md @@ -0,0 +1,221 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroute +applicable: Microsoft Teams +title: Set-CsOnlineVoiceRoute +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsOnlineVoiceRoute + +## SYNOPSIS +Modifies an online voice route. Online voice routes contain instructions that tell Microsoft Teams how to route calls from Microsoft or Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX). + +## SYNTAX + +### Identity +``` +Set-CsOnlineVoiceRoute [-BridgeSourcePhoneNumber <String>] [-Description <String>] [[-Identity] <String>] + [-NumberPattern <String>] [-OnlinePstnGatewayList <Object>] [-OnlinePstnUsages <Object>] [-Priority <Int32>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to modify an existing online voice route. Online voice routes are associated with online voice policies through online public switched telephone network (PSTN) usages. A online voice route includes a regular expression that identifies which phone numbers will be routed through a given voice route: phone numbers matching the regular expression will be routed through this route. + +This cmdlet is used when configuring Microsoft Phone System Direct Routing. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Set-CsOnlineVoiceRoute -Identity Route1 -Description "Test Route" +``` + +This command sets the Description of the Route1 online voice route to "Test Route." + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Set-CsOnlineVoiceRoute -Identity Route1 -OnlinePstnUsages @{add="Long Distance"} +``` + +The command in this example modifies the online voice route with the identity Route1 to add the online PSTN usage Long Distance to the list of usages for this voice route. Long Distance must be in the list of global online PSTN usages (which can be retrieved with a call to the `Get-CsOnlinePstnUsage` cmdlet). + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> $x = (Get-CsOnlinePstnUsage).Usage + +PS C:\> Set-CsOnlineVoiceRoute -Identity Route1 -OnlinePstnUsages @{replace=$x} +``` + +This example modifies the online voice route named Route1 to populate that route's list of online PSTN usages with all the existing usages for the organization. The first command in this example retrieves the list of global online PSTN usages. Notice that the call to the `Get-CsOnlinePstnUsage` cmdlet is in parentheses; this means that we first retrieve an object containing PSTN usage information. (Because there is only one--global--PSTN usage, only one object will be retrieved.) The command then retrieves the Usage property of this object. That property, which contains a list of online PSTN usages, is assigned to the variable $x. In the second line of this example, the Set-CsOnlineVoiceRoute cmdlet is called to modify the online voice route with the identity Route1. Notice the value passed to the OnlinePstnUsages parameter: @{replace=$x}. This value says to replace everything in the OnlinePstnUsages list for this route with the contents of $x, which contain the online PSTN usages list retrieved in line 1. + +## PARAMETERS + +### -BridgeSourcePhoneNumber +BridgeSourcePhoneNumber is an E.164 formatted Operator Connect Conferencing phone number assigned to your Audio Conferencing Bridge. Using BridgeSourcePhoneNumber in an online voice route is mutually exclusive with using OnlinePstnGatewayList in the same online voice route. + +When using BridgeSourcePhoneNumber in an online voice route, the OnlinePstnUsages used in the online voice route should only be used in a corresponding OnlineAudioConferencingRoutingPolicy. The same OnlinePstnUsages should not be used in online voice routes that are not using BridgeSourcePhoneNumber. + +For more information about Operator Connect Conferencing, please see [Configure Operator Connect Conferencing](https://learn.microsoft.com/microsoftteams/operator-connect-conferencing-configure). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +A description of what this phone route is for. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The unique identity of the online voice route. (If the route name contains a space, such as Test Route, you must enclose the full string in parentheses.) + +```yaml +Type: XdsGlobalRelativeIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NumberPattern +A regular expression that specifies the phone numbers to which this route applies. Numbers matching this pattern will be routed according to the rest of the routing settings. For example, the default number pattern, [0-9]{10}, specifies a 10-digit number containing any digits 0 through 9. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnGatewayList +This parameter contains a list of online gateways associated with this online voice route. Each member of this list must be the service Identity of the online PSTN gateway. The service Identity is the fully qualified domain name (FQDN) of the pool or the IP address of the server. For example, redmondpool.litwareinc.com. + +By default this list is empty. However, if you leave this parameter blank when creating a new voice route, you'll receive a warning message. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnUsages +A list of online PSTN usages (such as Local, Long Distance, etc.) that can be applied to this online voice route. The PSTN usage must be an existing usage (PSTN usages can be retrieved by calling the Get-CsOnlinePstnUsage cmdlet). + +By default this list is empty. However, if you leave this parameter blank when creating a new online voice route, you'll receive a warning message. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +A number could resolve to multiple online voice routes. The priority determines the order in which the routes will be applied if more than one route is possible. The lowest priority will be applied first and then in ascendant order. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroute) + +[New-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroute) + +[Remove-CsOnlineVoiceRoute](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroute) diff --git a/teams/teams-ps/teams/Set-CsOnlineVoiceRoutingPolicy.md b/teams/teams-ps/teams/Set-CsOnlineVoiceRoutingPolicy.md new file mode 100644 index 0000000000..c541ead593 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineVoiceRoutingPolicy.md @@ -0,0 +1,174 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceroutingpolicy +applicable: Microsoft Teams +title: Set-CsOnlineVoiceRoutingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineVoiceRoutingPolicy + +## SYNOPSIS +Modifies an existing online voice routing policy. Online voice routing policies manage online PSTN usages for Phone System users. + +## SYNTAX + +### Identity (Default) +``` +Set-CsOnlineVoiceRoutingPolicy [[-Identity] <string>] [-Description <string>] + [-OnlinePstnUsages <Object>] [-RouteType <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Online voice routing policies are used in Microsoft Phone System Direct Routing scenarios. Assigning your Teams users an online voice routing policy enables those users to receive and to place phone calls to the public switched telephone network by using your on-premises SIP trunks. + +Note that simply assigning a user an online voice routing policy will not enable them to make PSTN calls via Teams. Among other things, you will also need to enable those users for Phone System and will need to assign them an appropriate online voice policy. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +PS C:\> Set-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages @{Add="Long Distance"} +``` + +The command shown in Example 1 adds the online PSTN usage "Long Distance" to the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy. + +### -------------------------- Example 2 -------------------------- +``` +PS C:\> Set-CsOnlineVoiceRoutingPolicy -Identity "RedmondOnlineVoiceRoutingPolicy" -OnlinePstnUsages @{Remove="Local"} +``` + +In Example 2, the online PSTN usage "Local" is removed from the per-user online voice routing policy RedmondOnlineVoiceRoutingPolicy. + +### -------------------------- Example 3 -------------------------- +``` +PS C:\> Set-CsOnlineVoiceRoutingPolicy | Where-Object {$_.OnlinePstnUsages -contains "Local"} | Set-CsOnlineVoiceRoutingPolicy -OnlinePstnUsages @{Remove="Local"} +``` + +Example 3 removes the online PSTN usage "Local" from all the online voice routing policies that include that usage. In order to do this, the command first calls the `Get-CsOnlineVoiceRoutingPolicy` cmdlet without any parameters in order to return a collection of all the available online voice routing policies. That collection is then piped to the Where-Object cmdlet, which picks out only those policies where the OnlinePstnUsages property includes (-contains) the "Local" usage. Those policies are then piped to the `Set-CsOnlineVoiceRoutingPolicy` cmdlet, which deletes the Local usage from each policy. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany an online voice routing policy. For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the policy when it was created. Online voice routing policies can be assigned at the global scope or the per-user scope. To refer to the global instance, use this syntax: + +-Identity global + +To refer to a per-user policy, use syntax similar to this: + +-Identity "RedmondOnlineVoiceRoutingPolicy" + +If you do not specify an Identity, then the `Set-CsOnlineVoiceRoutingPolicy` cmdlet will modify the global policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnlinePstnUsages +A list of online PSTN usages (such as Local or Long Distance) that can be applied to this online voice routing policy. The online PSTN usage must be an existing usage. (PSTN usages can be retrieved by calling the `Get-CsOnlinePstnUsage` cmdlet.) + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RouteType +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoiceroutingpolicy) + +[Get-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoiceroutingpolicy) + +[Grant-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoiceroutingpolicy) + +[Remove-CsOnlineVoiceRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoiceroutingpolicy) diff --git a/skype/skype-ps/skype/Set-CsOnlineVoiceUser.md b/teams/teams-ps/teams/Set-CsOnlineVoiceUser.md similarity index 77% rename from skype/skype-ps/skype/Set-CsOnlineVoiceUser.md rename to teams/teams-ps/teams/Set-CsOnlineVoiceUser.md index 1c04ca5f13..d7f09686d0 100644 --- a/skype/skype-ps/skype/Set-CsOnlineVoiceUser.md +++ b/teams/teams-ps/teams/Set-CsOnlineVoiceUser.md @@ -1,12 +1,12 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csonlinevoiceuser -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinevoiceuser +applicable: Microsoft Teams title: Set-CsOnlineVoiceUser schema: 2.0.0 manager: bulenteg -author: tomkau -ms.author: tomkau +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -15,6 +15,10 @@ ms.reviewer: ## SYNOPSIS Use the `Set-CsOnlineVoiceUser` cmdlet to set the PSTN specific parameters (like telephone numbers and emergency response locations.) +**Note**: This cmdlet has been deprecated. Use the new +[Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) and +[Remove-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment) cmdlets instead. + ## SYNTAX ``` @@ -33,6 +37,12 @@ Set-CsOnlineVoiceUser -Identity 3c37e1c7-78f9-4703-82ee-a6b68516794e -TelephoneN This example sets the telephone number and location for a user identified by the user ObjectID. +### -------------------------- Example 2 -------------------------- +``` +Set-CsOnlineVoiceUser -Identity user@domain.com -TelephoneNumber $null +``` + +This example removes the telephone number for a user identified by the user's SIP address. ## PARAMETERS @@ -51,8 +61,8 @@ You can use the `Get-CsOnlineUser` cmdlet to identify the users you want to modi ```yaml Type: Object Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: 1 @@ -68,7 +78,7 @@ The Confirm switch causes the command to pause processing and requires confirmat Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -84,7 +94,7 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: (All) Aliases: DC -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -101,8 +111,8 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -120,8 +130,8 @@ This parameter is required for users based in the US. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -138,8 +148,8 @@ Setting the value to $Null clears the user's telephone number. ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -154,8 +164,8 @@ This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -171,7 +181,7 @@ The WhatIf parameter is not implemented for this cmdlet. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -181,19 +191,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS -### -None - ## OUTPUTS -### -None - ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-CsOnlineVoicemailPolicy.md b/teams/teams-ps/teams/Set-CsOnlineVoicemailPolicy.md new file mode 100644 index 0000000000..e5f0a4f436 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineVoicemailPolicy.md @@ -0,0 +1,311 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailpolicy +applicable: Microsoft Teams +title: Set-CsOnlineVoicemailPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineVoicemailPolicy + +## SYNOPSIS +Modifies an existing Online Voicemail policy. Online Voicemail policies determine whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify the voicemail maximum recording length for a user and the primary and secondary voicemail system prompt languages. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsOnlineVoicemailPolicy [[-Identity] <string>] [-Description <String>] [-EnableEditingCallAnswerRulesSetting <boolean>] [-EnableTranscription <boolean>] +[-EnableTranscriptionProfanityMasking <boolean>] [-EnableTranscriptionTranslation <boolean>] [-MaximumRecordingLength <timespan>] +[-PostambleAudioFile <string>] [-PostambleAudioFile <string>] [-PreamblePostambleMandatory <boolean>] +[-PrimarySystemPromptLanguage <string>] [-SecondarySystemPromptLanguage <string>] [-ShareData <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Cloud Voicemail service provides organizations with voicemail deposit capabilities for Phone System implementation. + +By default, users enabled for Phone System will be enabled for Cloud Voicemail. The Online Voicemail policy controls whether or not voicemail transcription, profanity masking for the voicemail transcriptions, translation for the voicemail transcriptions, and editing call answer rule settings are enabled for a user. The policies also specify the voicemail maximum recording length for a user and the primary and secondary voicemail system prompt languages. + +- Voicemail transcription is enabled by default +- Transcription profanity masking is disabled by default +- Transcription translation is enabled by default +- Editing call answer rule settings is enabled by default +- Voicemail maximum recording length is set to 5 minutes by default +- Primary and secondary system prompt languages are set to null by default and the user's voicemail language setting is used + +Tenant admin would be able to create a customized online voicemail policy to match the organization's requirements. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsOnlineVoicemailPolicy -Identity "CustomOnlineVoicemailPolicy" -MaximumRecordingLength ([TimeSpan]::FromSeconds(60)) +``` + +The command shown in Example 1 changes the MaximumRecordingLength to 60 seconds for the per-user online voicemail policy CustomOnlineVoicemailPolicy. + +### -------------------------- Example 2 -------------------------- +``` +Set-CsOnlineVoicemailPolicy -EnableTranscriptionProfanityMasking $false +``` + +The command shown in Example 2 changes the EnableTranscriptionProfanityMasking to false for tenant level global online voicemail policy when calling without Identity parameter. + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableEditingCallAnswerRulesSetting +Controls if editing call answer rule settings are enabled or disabled for a user. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTranscription +Allows you to disable or enable voicemail transcription. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTranscriptionProfanityMasking +Allows you to disable or enable profanity masking for the voicemail transcriptions. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableTranscriptionTranslation +Allows you to disable or enable translation for the voicemail transcriptions. Possible values are $true or $false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaximumRecordingLength +A duration of voicemail maximum recording length. The length should be between 30 seconds to 10 minutes. + +```yaml +Type: Duration +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PostambleAudioFile +The audio file to play to the caller after the user's voicemail greeting has played and before the caller is allowed to leave a voicemail message. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -PreambleAudioFile +The audio file to play to the caller before the user's voicemail greeting is played. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreamblePostambleMandatory +Is playing the Pre- or Post-amble mandatory before the caller can leave a message. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrimarySystemPromptLanguage +The primary (or first) language that voicemail system prompts will be presented in. Must also set SecondarySystemPromptLanguage. When set, this overrides the user language choice. See [Set-CsOnlineVoicemailUserSettings](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailusersettings) -PromptLanguage for supported languages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SecondarySystemPromptLanguage +The secondary language that voicemail system prompts will be presented in. Must also set PrimarySystemPromptLanguage and may not be the same value as PrimarySystemPromptanguage. When set, this overrides the user language choice. See [Set-CsOnlineVoicemailUserSettings](https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailusersettings) -PromptLanguage for supported languages. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShareData +Specifies whether voicemail and transcription data are shared with the service for training and improving accuracy. Possible values are Defer and Deny. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoicemailpolicy) + +[New-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/new-csonlinevoicemailpolicy) + +[Remove-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csonlinevoicemailpolicy) + +[Grant-CsOnlineVoicemailPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csonlinevoicemailpolicy) diff --git a/teams/teams-ps/teams/Set-CsOnlineVoicemailUserSettings.md b/teams/teams-ps/teams/Set-CsOnlineVoicemailUserSettings.md new file mode 100644 index 0000000000..679bea74c8 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsOnlineVoicemailUserSettings.md @@ -0,0 +1,360 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csonlinevoicemailusersettings +applicable: Microsoft Teams +title: Set-CsOnlineVoicemailUserSettings +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsOnlineVoicemailUserSettings + +## SYNOPSIS +Use the Set-CsOnlineVoicemailUserSettings cmdlet to modify the online voicemail user settings of a specific user. +New online voicemail user settings of the user would be returned after executing. + +## SYNTAX + +``` +Set-CsOnlineVoicemailUserSettings [-Identity] <string> [-CallAnswerRule <Object>] [-DefaultGreetingPromptOverwrite <string>] +[-DefaultOofGreetingPromptOverwrite <string>] [-Force] [-OofGreetingEnabled <boolean>] [-OofGreetingFollowAutomaticRepliesEnabled <boolean>] +[-OofGreetingFollowCalendarEnabled <boolean>] [-PromptLanguage <string>] [-ShareData <boolean>] [-TransferTarget <string>] +[-VoicemailEnabled <boolean>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The Set-CsOnlineVoicemailUserSettings cmdlet lets tenant admin modify the online voicemail user settings of a specific user in the organization. New online voicemail user settings of the user would be returned after executing. +For example, tenant admin could enable/disable voicemail, change voicemail prompt language, modify out-of-office voicemail greeting settings, or setup simple call answer rules. Only those properties that tenant admin have actually provided with be modified. If an online voicemail user setting was not set by tenant admin, it would remain the old value after this cmdlet has been executed. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsOnlineVoicemailUserSettings -Identity sip:user1@contoso.com -VoicemailEnabled $true +``` + +This example changes VoicemailEnabled setting to true for the user with SIP URI sip:user1@contoso.com. + +### -------------------------- Example 2 -------------------------- +``` +Set-CsOnlineVoicemailUserSettings -Identity user2@contoso.com -PromptLanguage "en-US" -OofGreetingFollowCalendarEnabled $false +``` + +This example changes PromptLanguage setting to "en-US" and OofGreetingFollowCalendarEnabled setting to false for user2@contoso.com. + +### -------------------------- Example 3 -------------------------- +``` +Set-CsOnlineVoicemailUserSettings -Identity user3@contoso.com -CallAnswerRule PromptOnlyWithTransfer -TransferTarget sip:user4@contoso.com +``` + +This example changes CallAnswerRule setting to PromptOnlyWithTransfer and set TransferTarget to "sip:user4@contoso.com" for user3@contoso.com. + +### -------------------------- Example 4 -------------------------- +``` +Set-CsOnlineVoicemailUserSettings -Identity user5@contoso.com -CallAnswerRule VoicemailWithTransferOption -TransferTarget "+14255551234" +``` + +This example changes CallAnswerRule setting to VoicemailWithTransferOption and set TransferTarget to "+14255551234" for user5@contoso.com.. + +### -------------------------- Example 5 -------------------------- +``` +Set-CsOnlineVoicemailUserSettings -Identity user6@contoso.com -DefaultGreetingPromptOverwrite "Hi, I am currently not available." +``` + +This example changes DefaultGreetingPromptOverwrite setting to "Hi, I am currently not available." for user6@contoso.com. + +## PARAMETERS + +### -Identity +The Identity parameter represents the ID of the specific user in your organization; this can be either a SIP URI or an Object ID. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallAnswerRule +The CallAnswerRule parameter represents the value of the call answer rule, which can be any of the following: + +- DeclineCall +- PromptOnly +- PromptOnlyWithTransfer +- RegularVoicemail +- VoicemailWithTransferOption + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultGreetingPromptOverwrite +The DefaultGreetingPromptOverwrite parameter represents the contents that overwrite the default normal greeting prompt. +If the user's normal custom greeting is not set and DefaultGreetingPromptOverwrite is not empty, the voicemail service will play this overwrite greeting instead of the default normal greeting in the voicemail deposit scenario. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultOofGreetingPromptOverwrite +The DefaultOofGreetingPromptOverwrite parameter represents the contents that overwrite the default out-of-office greeting prompt. +If the user's out-of-office custom greeting is not set and DefaultOofGreetingPromptOverwrite is not empty, the voicemail service will play this overwrite greeting instead of the default out-of-office greeting in the voicemail deposit scenario. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OofGreetingEnabled +The OofGreetingEnabled parameter represents whether to play out-of-office greeting in voicemail deposit scenario. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OofGreetingFollowAutomaticRepliesEnabled +The OofGreetingFollowAutomaticRepliesEnabled parameter represents whether to play out-of-office greeting in voicemail deposit scenario when user set automatic replies in Outlook. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PromptLanguage +The PromptLanguage parameter represents the language that is used to play voicemail prompts. + +The following languages are supported: + +- "ar-EG" (Arabic - Egypt) +- "ar-SA" (Arabic - Saudi Arabia) +- "bg-BG" (Bulgarian - Bulgaria) +- "ca-ES" (Catalan - Catalan) +- "cy-GB" (Welsh - United Kingdom) +- "cs-CZ" (Czech - Czech Republic) +- "da-DK" (Danish - Denmark) +- "de-AT" (German - Austria) +- "de-CH" (German - Switzerland) +- "de-DE" (German - Germany) +- "el-GR" (Greek - Greece) +- "en-AU" (English - Australia) +- "en-CA" (English - Canada) +- "en-GB" (English - United Kingdom) +- "en-IE" (English - Ireland) +- "en-IN" (English - India) +- "en-PH" (English - Philippines) +- "en-US" (English - United States) +- "en-ZA" (English - South Africa) +- "es-ES" (Spanish - Spain) +- "es-MX" (Spanish - Mexico) +- "et-EE" (Estonian - Estonia) +- "fi-FI" (Finnish - Finland) +- "fr-BE" (French - Belgium) +- "fr-CA" (French - Canada) +- "fr-CH" (French - Switzerland) +- "fr-FR" (French - France) +- "he-IL" (Hebrew - Israel) +- "hi-IN" (Hindi - India) +- "hr-HR" (Croatian - Croatia) +- "hu-HU" (Hungarian - Hungary) +- "id-ID" (Indonesian - Indonesia) +- "it-IT" (Italian - Italy) +- "ja-JP" (Japanese - Japan) +- "ko-KR" (Korean - Korea) +- "lt-LT" (Lithuanian - Lithuania) +- "lv-LV" (Latvian - Latvia) +- "nl-BE" (Dutch - Belgium) +- "nl-NL" (Dutch - Netherlands) +- "nb-NO" (Norwegian, Bokmål - Norway) +- "pl-PL" (Polish - Poland) +- "pt-BR" (Portuguese - Brazil) +- "pt-PT" (Portuguese - Portugal) +- "ro-RO" (Romanian - Romania) +- "ru-RU" (Russian - Russia) +- "sk-SK" (Slovak - Slovakia) +- "sl-SI" (Slovenian - Slovenia) +- "sv-SE" (Swedish - Sweden) +- "th-TH" (Thai - Thailand) +- "tr-TR" (Turkish - Turkey) +- "vi-VN" (Vietnamese - Viet Nam) +- "zh-CN" (Chinese - Simplified, PRC) +- "zh-TW" (Chinese - Traditional, Taiwan) +- "zh-HK" (Chinese - Traditional, Hong Kong S.A.R.) + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShareData +Specifies whether voicemail and transcription data is shared with the service for training and improving accuracy. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TransferTarget +The TransferTarget parameter represents the target to transfer the call when call answer rule set to PromptOnlyWithTransfer or VoicemailWithTransferOption. +Value of this parameter should be a SIP URI of another user in your organization. +For user with Enterprise Voice enabled, a valid telephone number could also be accepted as TransferTarget. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoicemailEnabled +The VoicemailEnabled parameter represents whether to enable voicemail service. If set to $false, the user has no voicemail service. + +```yaml +Type: System.Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.Voicemail.Models.VoicemailUserSettings + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineVoicemailUserSettings](https://learn.microsoft.com/powershell/module/teams/get-csonlinevoicemailusersettings) diff --git a/teams/teams-ps/teams/Set-CsPhoneNumberAssignment.md b/teams/teams-ps/teams/Set-CsPhoneNumberAssignment.md new file mode 100644 index 0000000000..4ef22599c9 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsPhoneNumberAssignment.md @@ -0,0 +1,330 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment +applicable: Microsoft Teams +title: Set-CsPhoneNumberAssignment +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Set-CsPhoneNumberAssignment + +## SYNOPSIS +This cmdlet will assign a phone number to a user or a resource account (online application instance). + +## SYNTAX + +### LocationUpdate (Default) +```powershell +Set-CsPhoneNumberAssignment -PhoneNumber <string> -LocationId <string> [<CommonParameters>] +``` + +### NetworkSiteUpdate +```powershell +Set-CsPhoneNumberAssignment -PhoneNumber <string> -NetworkSiteId <string> [<CommonParameters>] +``` + +### Assignment +```powershell +Set-CsPhoneNumberAssignment -Identity <String> -PhoneNumber <String> -PhoneNumberType <String> + [-LocationId <String>] [-NetworkSiteId <string>] [-AssignmentCategory <string>] [<CommonParameters>] +``` + +### Attribute +```powershell +Set-CsPhoneNumberAssignment -Identity <String> -EnterpriseVoiceEnabled <Boolean> [<CommonParameters>] +``` + +### ReverseNumberLookup +```powershell +Set-CsPhoneNumberAssignment -PhoneNumber <string> -ReverseNumberLookup <string> [<CommonParameters>] +``` + +### Notify +```powershell +Set-CsPhoneNumberAssignment -Identity <string> -PhoneNumber <string> -PhoneNumberType <String> -Notify [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet assigns a phone number to a user or resource account. When you assign a phone number the EnterpriseVoiceEnabled flag is automatically set to True. + +You can also assign a location to a phone number. + +To remove a phone number from a user or resource account, use the [Remove-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment) cmdlet. + +## EXAMPLES + +### Example 1 +```powershell +Set-CsPhoneNumberAssignment -Identity user1@contoso.com -PhoneNumber +12065551234 -PhoneNumberType CallingPlan +``` +This example assigns the Microsoft Calling Plan phone number +1 (206) 555-1234 to the user user1@contoso.com. + +### Example 2 +```powershell +$loc=Get-CsOnlineLisLocation -City Vancouver +Set-CsPhoneNumberAssignment -Identity user2@contoso.com -PhoneNumber +12065551224 -PhoneNumberType CallingPlan -LocationId $loc.LocationId +``` +This example finds the emergency location defined for the corporate location Vancouver and assigns the Microsoft Calling Plan phone number +1 (206) 555-1224 and location to the user user2@contoso.com. + +### Example 3 +```powershell +Set-CsPhoneNumberAssignment -Identity user3@contoso.com -EnterpriseVoiceEnabled $true +``` +This example sets the EnterpriseVoiceEnabled flag on the user user3@contoso.com. + +### Example 4 +```powershell +Set-CsPhoneNumberAssignment -Identity user3@contoso.com -LocationId 'null' -PhoneNumber +12065551226 -PhoneNumberType OperatorConnect +``` +This example removes the emergency location from the phone number for user user3@contoso.com. + +### Example 5 +```powershell +Set-CsPhoneNumberAssignment -Identity cq1@contoso.com -PhoneNumber +14255551225 -PhoneNumberType DirectRouting +``` +This example assigns the Direct Routing phone number +1 (425) 555-1225 to the resource account cq1@contoso.com. + +### Example 6 +```powershell +Set-CsPhoneNumberAssignment -Identity user4@contoso.com -PhoneNumber "+14255551000;ext=1234" -PhoneNumberType DirectRouting +``` +This example assigns the Direct Routing phone number +1 (425) 555-1000;ext=1234 to the user user4@contoso.com. + +### Example 7 +```powershell +Try { Set-CsPhoneNumberAssignment -Identity user5@contoso.com -PhoneNumber "+14255551000;ext=1234" -PhoneNumberType DirectRouting -ErrorAction Stop } Catch { Write-Host An error occurred } +``` +This example shows how to use Try/Catch and ErrorAction to perform error checking on the assignment cmdlet failing. + +### Example 8 +```powershell +$TempUser = "tempuser@contoso.com" +$OldLoc=Get-CsOnlineLisLocation -City Vancouver +$NewLoc=Get-CsOnlineLisLocation -City Seattle +$Numbers=Get-CsPhoneNumberAssignment -LocationId $OldLoc.LocationId -PstnAssignmentStatus Unassigned -NumberType CallingPlan -CapabilitiesContain UserAssignment +foreach ($No in $Numbers) { + Set-CsPhoneNumberAssignment -Identity $TempUser -PhoneNumberType CallingPlan -PhoneNumber $No.TelephoneNumber -LocationId $NewLoc.LocationId + Remove-CsPhoneNumberAssignment -Identity $TempUser -PhoneNumberType CallingPlan -PhoneNumber $No.TelephoneNumber +} +``` +This example shows how to change the location for unassigned Calling Plan subscriber phone numbers by looping through all the phone numbers, assigning each phone number temporarily with the new location to a user, and then unassigning the phone number again from the user. + +### Example 9 +```powershell +$loc=Get-CsOnlineLisLocation -City Toronto +Set-CsPhoneNumberAssignment -PhoneNumber +12065551224 -LocationId $loc.LocationId +``` +This example shows how to set the location on a phone number. + +### Example 10 +```powershell +$OldLocationId = "7fda0c0b-6a3d-48b8-854b-3fbe9dcf6513" +$NewLocationId = "951fac72-955e-4734-ab74-cc4c0f761c0b" +# Get all phone numbers in old location +$pns = Get-CsPhoneNumberAssignment -LocationId $OldLocationId +Write-Host $pns.count numbers found in old location $OldLocationId +# Move all those phone numbers to the new location +foreach ($pn in $pns) { + Try { + Set-CsPhoneNumberAssignment -PhoneNumber $pn.TelephoneNumber -LocationId $NewLocationId -ErrorAction Stop + Write-Host $pn.TelephoneNumber was updated to have location $NewLocationId + } + Catch { + Write-Host Could not update $pn.TelephoneNumber with location $NewLocationId + } +} +Write-Host (Get-CsPhoneNumberAssignment -LocationId $OldLocationId).Count numbers found in old location $OldLocationId +Write-Host (Get-CsPhoneNumberAssignment -LocationId $NewLocationId).Count numbers found in new location $NewLocationId +``` +This Example shows how to update the LocationID from an old location to a new location for a set of phone numbers. + +### Example 11 +```powershell +Set-CsPhoneNumberAssignment -Identity user3@contoso.com -PhoneNumber +12065551226 -ReverseNumberLookup 'SkipInternalVoip' +``` +This example shows how to turn off reverse number lookup (RNL) on a phone number. When RNL is set to 'SkipInternalVoip', an internal call to this phone number will not attempt to pass through internal VoIP via reverse number lookup in Microsoft Teams. Instead the call will be established through external PSTN connectivity directly. This example is only applicable for Direct Routing phone numbers. + +### Example 12 +```powershell +Set-CsPhoneNumberAssignment -Identity user1@contoso.com -PhoneNumber '+14255551234' -PhoneNumberType CallingPlan -AssignmentCategory Private +``` +This example shows how to assign a private phone number (incoming calls only) to a user. +### Example 13 +```powershell +Set-CsPhoneNumberAssignment -Identity user1@contoso.com -PhoneNumber '+14255551234' -PhoneNumberType CallingPlan -LocationId "7fda0c0b-6a3d-48b8-854b-3fbe9dcf6513" -Notify +``` +This example shows how to send an email to Teams phone users informing them about the new telephone number assignment. Note: For assignment of India telephone numbers provided by Airtel, Teams Phone users will automatically receive an email outlining the usage guidelines and restrictions. This notification is mandatory and cannot be opted out of. + +## PARAMETERS + +### -AssignmentCategory +This parameter indicates the phone number assignment category if it isn't the primary phone number. For example, a Private line can be assigned to a user using '-AssignmentCategory Private'. + +```yaml +Type: System.String +Parameter Sets: (Assignment) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnterpriseVoiceEnabled +Flag indicating if the user or resource account should be EnterpriseVoiceEnabled. + +This parameter is mutual exclusive with PhoneNumber. + +```yaml +Type: System.Boolean +Parameter Sets: (Attribute) +Aliases: +Applicable: Microsoft Teams + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity of the specific user or resource account. Can be specified using the value in the ObjectId, the SipProxyAddress, or the UserPrincipalName attribute of the user or +resource account. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationId +The LocationId of the location to assign to the specific user. You can get it using Get-CsOnlineLisLocation. You can set the location on both assigned and unassigned +phone numbers. + +Removal of location from a phone number is supported for Direct Routing numbers and Operator Connect numbers that are not managed by the Service Desk. +If you want to remove the location, use the string value null for LocationId. + +```yaml +Type: System.String +Parameter Sets: (Assignment, LocationUpdate) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkSiteId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: System.String +Parameter Sets: (Assignment) +Aliases: +Applicable: Microsoft Teams + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhoneNumber +The phone number to assign to the user or resource account. Supports E.164 format like +12065551234 and non-E.164 format like 12065551234. The phone number can't have "tel:" prefixed. + +We support Direct Routing numbers with extensions using the formats +1206555000;ext=1234 or 1206555000;ext=1234 assigned to a user or resource account. + +Setting a phone number will automatically set EnterpriseVoiceEnabled to True. + +```yaml +Type: System.String +Parameter Sets: (Assignment, LocationUpdate) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhoneNumberType +The type of phone number to assign to the user or resource account. The supported values are DirectRouting, CallingPlan, and OperatorConnect. When you acquire a phone number you will typically know which type it is. + +```yaml +Type: System.String +Parameter Sets: (Assignment) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReverseNumberLookup +This parameter is used to control the behavior of reverse number lookup (RNL) for a phone number.When RNL is set to 'SkipInternalVoip', an internal call to this phone number will not attempt to pass through internal VoIP via reverse number lookup in Microsoft Teams. Instead the call will be established through external PSTN connectivity directly. + +```yaml +Type: String +Parameter Sets: (ReverseNumberLookupUpdate, Assignment) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Notify +Sends an email to Teams phone user about new telephone number assignment. + +```yaml +Type: Switch +Parameter Sets: (Assignment) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PowerShell module 3.0.0 or later. The parameter set LocationUpdate was introduced in Teams PowerShell module 5.3.1-preview. The parameter NetworkSiteId was introduced in Teams PowerShell module 5.5.0. The parameter set NetworkSiteUpdate was introduced in Teams PowerShell module 5.5.1-preview. + +The cmdlet is only available in commercial and GCC cloud instances. + +If a user or resource account has a phone number set in Active Directory on-premises and synched into Microsoft 365, you can't use Set-CsPhoneNumberAssignment to set the phone number. You will have to clear the phone number from the on-premises Active Directory and let that change sync into Microsoft 365 first. + +The previous command for assigning phone numbers to users Set-CsUser had the parameter HostedVoiceMail. Setting HostedVoiceMail for Microsoft Teams users is no longer +necessary and that is why the parameter is not available on Set-CsPhoneNumberAssignment. + +## RELATED LINKS +[Remove-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment) + +[Get-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/get-csphonenumberassignment) diff --git a/teams/teams-ps/teams/Set-CsPhoneNumberTag.md b/teams/teams-ps/teams/Set-CsPhoneNumberTag.md new file mode 100644 index 0000000000..c571a93910 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsPhoneNumberTag.md @@ -0,0 +1,82 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/set-csphonenumbertag +applicable: Microsoft Teams +title: Set-CsPhoneNumberTag +author: pavellatif +ms.author: pavellatif +ms.reviewer: pavellatif +manager: roykuntz +schema: 2.0.0 +--- + +# Set-CsPhoneNumberTag + +## SYNOPSIS +This cmdlet allows the admin to create and assign a tag to a phone number. + +## SYNTAX + +``` +Set-CsPhoneNumberTag -PhoneNumber <String> -Tag <String> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet allows telephone number administrators to create and assign tags to phone numbers. Tags can be up to 50 characters long, including spaces, and can contain multiple words. They are not case-sensitive. Each phone number can have up to 50 tags assigned. To improve readability, it is recommended to avoid assigning too many tags to a single phone number. If the desired tag already exist, the telephone number will get assigned the existing tag. If the tag is not already available, a new tag will be created. [Get-CsPhoneNumberTag](https://learn.microsoft.com/powershell/module/teams/get-csphonenumbertag) can be used to check a list of already existing tags. The tags can be used as a filter for [Get-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/get-csphonenumberassignment) to filter on certain list. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsPhoneNumberTag -PhoneNumber +123456789 -Tag "HR" +``` +Above example shows how to set a "HR" tag to +123456789 number. + +## PARAMETERS + +### -PhoneNumber +Indicates the phone number for the the tag to be assigned + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tag +Indicates the tag to be assigned or created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Boolean + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsSharedCallQueueHistoryTemplate.md b/teams/teams-ps/teams/Set-CsSharedCallQueueHistoryTemplate.md new file mode 100644 index 0000000000..5cd82bcea2 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsSharedCallQueueHistoryTemplate.md @@ -0,0 +1,87 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsSharedCallQueueHistoryTemplate +applicable: Microsoft Teams +title: Set-CsSharedCallQueueHistoryTemplate +schema: 2.0.0 +manager: +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsSharedCallQueueHistoryTemplate + +## SYNTAX + +```powershell +Set-CsSharedCallQueueHistoryTemplate -Instance <instance> [<CommonParameters>] +``` + +## DESCRIPTION +Use the Set-SharedCallQueueHistory cmdlet to change a Shared Call Queue History template. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for this feature. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$SharedCQHistory = Get-CsSharedCallQueueHistory -Id 66f0dc32-d344-4bb1-b524-027d4635515c +$SharedCQHisotry.AnsweredAndOutboundCalls = "AuthorizedUsersAndAgents" +Set-CsSharedCallQueueHistoryTemplate -Instance $SharedCQHistory +``` + +This example sets the AnsweredOutboundCalls value in the Shared Call History Template with the Id `66f0dc32-d344-4bb1-b524-027d4635515c` + +## PARAMETERS + +### -Instance +The instance of the shared call queue history template to change. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Microsoft.Rtc.Management.OAA.Models.AutoAttendant + +## NOTES + +## RELATED LINKS + +[New-CsSharedCallQueueHistoryTemplate](./New-CsSharedCallQueueHistoryTemplate.md) + +[Get-CsSharedCallQueueHistoryTemplate](./Get-CsSharedCallQueueHistoryTemplate.md) + +[Remove-CsSharedCallQueueHistoryTemplate](./Remove-CsSharedCallQueueHistoryTemplate.md) + +[Get-CsCallQueue](./Get-CsCallQueue.md) + +[New-CsCallQueue](./New-CsCallQueue.md) + +[Set-CsCallQueue](./Set-CsCallQueue.md) + +[Remove-CsCallQueue](./Remove-CsCallQueue.md) + + + diff --git a/teams/teams-ps/teams/Set-CsTeamsAIPolicy.md b/teams/teams-ps/teams/Set-CsTeamsAIPolicy.md new file mode 100644 index 0000000000..2c43c43e51 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsAIPolicy.md @@ -0,0 +1,194 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Set-CsTeamsAIPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsTeamsAIPolicy +schema: 2.0.0 +author: Andy447 +ms.author: andywang +--- + +# Set-CsTeamsAIPolicy + +## SYNOPSIS + +This cmdlet sets Teams AI policy value for users in the tenant. + +## SYNTAX + +```powershell +Set-CsTeamsAIPolicy [[-Identity] <string>] + [-EnrollFace <string>] + [-EnrollVoice <string>] + [-SpeakerAttributionBYOD <string>] + [-Description <string>] + [<CommonParameters>] +``` + +## DESCRIPTION + +The new csTeamsAIPolicy will replace the existing enrollment settings in csTeamsMeetingPolicy, providing enhanced flexibility and control for Teams meeting administrators. Unlike the current single setting, EnrollUserOverride, which applies to both face and voice enrollment, the new policy introduces two distinct settings: EnrollFace and EnrollVoice. These can be individually set to Enabled or Disabled, offering more granular control over biometric enrollments. A new setting, SpeakerAttributionBYOD, is also being added to csTeamsAIPolicy. This allows IT admins to turn off speaker attribution in BYOD scenarios, giving them greater control over how voice data is managed in such environments. This setting can be set to Enabled or Disabled, and will be Enabled by default. In addition to improving the management of face and voice data, the csTeamsAIPolicy is designed to support future AI-related settings in Teams, making it a scalable solution for evolving needs. + +This cmdlet sets the EnrollFace, EnrollVoice, and SpeakerAttributionBYOD values within the csTeamsAIPolicy. These policies can be assigned to users, and each setting can be configured as "Enabled" or "Disabled". " + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Global -EnrollFace Disabled +``` + +Set Teams AI policy "EnrollFace" value to "Disabled" for global as default. + +### Example 2 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Global -EnrollVoice Disabled +``` + +Set Teams AI policy "EnrollVoice" value to "Disabled" for global as default. + +### Example 3 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Global -SpeakerAttributionBYOD Disabled +``` + +Set Teams AI policy "SpeakerAttributionBYOD" value to "Disabled" for global as default. + +### Example 4 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollFace Enabled +``` + +Set Teams AI policy "EnrollFace" value to "Enabled" for identity "Test". + +### Example 5 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollVoice Enabled +``` + +Set Teams AI policy "EnrollVoice" value to "Enabled" for identity "Test". + +### Example 6 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Test -SpeakerAttributionBYOD Enabled +``` + +Set Teams AI policy "SpeakerAttributionBYOD" value to "Enabled" for identity "Test". + +### Example 7 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollFace Disabled +``` + +Set Teams AI policy "EnrollFace" value to "Disabled" for identity "Test". + +### Example 8 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollVoice Disabled +``` + +Set Teams AI policy "EnrollVoice" value to "Disabled" for identity "Test". + +### Example 9 +```powershell +PS C:\> Set-CsTeamsAIPolicy -Identity Test -SpeakerAttributionBYOD Disabled +``` + +Set Teams AI policy "SpeakerAttributionBYOD" value to "Disabled" for identity "Test". + +## PARAMETERS + +### -Identity +Identity of the Teams AI policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnrollFace +Policy value of the Teams AI EnrollFace policy. EnrollFace controls user access to user face enrollment in the Teams app settings. + +```yaml +Type: String +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnrollVoice +Policy value of the Teams AI EnrollVoice policy. EnrollVoice controls user access to user voice enrollment in the Teams app settings. + +```yaml +Type: String +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpeakerAttributionBYOD +Policy value of the Teams AI SpeakerAttributionBYOD policy. Setting to "Enabled" turns on speaker attribution in BYOD scenarios while "Disabled" will turn off the function. + +```yaml +Type: String +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the Teams AI policy. +For example, the Description might indicate the users the policy should be assigned to. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsaipolicy) + +[Remove-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsaipolicy) + +[Get-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaipolicy) + +[Grant-CsTeamsAIPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaipolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsAcsFederationConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsAcsFederationConfiguration.md new file mode 100644 index 0000000000..d5d3e1c8a6 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsAcsFederationConfiguration.md @@ -0,0 +1,115 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Set-CsTeamsAcsFederationConfiguration +author: tomkau +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsacsfederationconfiguration +schema: 2.0.0 +--- + +# Set-CsTeamsAcsFederationConfiguration + +## SYNOPSIS + +This cmdlet is used to manage the federation configuration between Teams and Azure Communication Services. For more information, please see [Azure Communication Services and Teams Interoperability](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). + +## SYNTAX + +```powershell +Set-CsTeamsAcsFederationConfiguration + [-Identity <String[]>] + [-EnableAcsUsers <Boolean>] + [-AllowedAcsResources <String[]>] + [-WhatIf] + [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +Federation between Teams and Azure Communication Services (ACS) allows external users from ACS to connect and communicate with Teams users over voice and video. These custom applications may be used by end users or by bots, and there is no differentiation in how they appear to Teams users unless the developer of the application explicitly indicates this as part of the communication. For more information, see [Teams interoperability](https://learn.microsoft.com/azure/communication-services/concepts/teams-interop). + +This cmdlet is used to enable or disable Teams and ACS federation for a Teams tenant, and to specify which ACS resources can connect to Teams. Only listed ACS resources can be allowed. + +You must be a Teams service admin or a Teams communication admin for your organization to run the cmdlet. + +## EXAMPLES + +### Example 1 +In this example, federation between Teams and ACS is disabled completely. + +```powershell +Set-CsTeamsAcsFederationConfiguration -EnableAcsUsers $False +``` + +### Example 2 +In this example, federation is enabled for just one ACS resource. + +```powershell +$allowlist = @('faced04c-2ced-433d-90db-063e424b87b1') +Set-CsTeamsAcsFederationConfiguration -EnableAcsUsers $True -AllowedAcsResources $allowlist +``` + +## PARAMETERS + +### -EnableAcsUsers + +Set to True to enable federation between Teams and ACS. When set to False, all other parameters are ignored. + +```yaml +Type: Boolean +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedAcsResources + +The list of the ACS resources (at least one) for which federation is enabled, when EnableAcsUsers is set to true. If EnableAcsUsers is set to false, then this list is ignored and should be null/empty. + +The ACS resources are listed using their immutable resource id, which is a guid that can be found on the Azure portal. + +```yaml +Type: String[] +Position: Named +Default value: Empty/Null +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the collection of tenant federation configuration settings to be modified. Because each tenant is limited to a single, global collection of federation settings there is no need include this parameter when calling the Set-CsTenantFederationConfiguration cmdlet. If you do choose to use the Identity parameter, you must also include the Tenant parameter. For example: + +`Set-CsTenantFederationConfiguration -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Identity "global"` +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsAcsFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsacsfederationconfiguration) + +[New-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/new-csexternalaccesspolicy) + +[Set-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/set-csexternalaccesspolicy) + +[Grant-CsExternalAccessPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csexternalaccesspolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsAppPermissionPolicy.md b/teams/teams-ps/teams/Set-CsTeamsAppPermissionPolicy.md new file mode 100644 index 0000000000..58ff1553f7 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsAppPermissionPolicy.md @@ -0,0 +1,319 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsapppermissionpolicy +applicable: Microsoft Teams +title: Set-CsTeamsAppPermissionPolicy +schema: 2.0.0 +ms.reviewer: mhayrapetyan +manager: prkosh +author: serdarsoysal +ms.author: serdars +--- + +# Set-CsTeamsAppPermissionPolicy + +## SYNOPSIS +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. This cmdlet is not supported for tenants that migrated to app centric management feature as it replaced permission policies. While the cmdlet may succeed, the changes aren't applied to the tenant. + +As an admin, you can use app permission policies to allow or block apps for your users. Learn more about the app permission policies at <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies> and about app centric management at <https://learn.microsoft.com/microsoftteams/app-centric-management>. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [-DefaultCatalogApps <>] [-GlobalCatalogApps <>] + [-PrivateCatalogApps <>] [-Description <String>] [-DefaultCatalogAppsType <String>] + [-GlobalCatalogAppsType <String>] [-PrivateCatalogAppsType <String>] [[-Identity] <XdsIdentity>] [-Force] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsAppPermissionPolicy [-Tenant <System.Guid>] [-DefaultCatalogApps <>] [-GlobalCatalogApps <>] + [-PrivateCatalogApps <>] [-Description <String>] [-DefaultCatalogAppsType <String>] + [-GlobalCatalogAppsType <String>] [-PrivateCatalogAppsType <String>] [-Instance <PSObject>] [-Force] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app permission polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app permission policies to enable or block specific apps for your users. Learn more about the App Setup Policies: <https://learn.microsoft.com/microsoftteams/teams-app-permission-policies>. + +## EXAMPLES + +### Example 1 + +```powershell +$identity = "TestTeamsAppPermissionPolicy" + (Get-Date -Format FileDateTimeUniversal) +New-CsTeamsAppPermissionPolicy -Identity Set-$identity +Set-CsTeamsAppPermissionPolicy -Identity Set-$identity -DefaultCatalogAppsType BlockedAppList -DefaultCatalogApps @()-GlobalCatalogAppsType -GlobalCatalogApps @() BlockedAppList -PrivateCatalogAppsType BlockedAppList -PrivateCatalogApps @() +``` +This example allows all Microsoft apps, third-party apps, and custom apps. No apps are blocked. + +### Example 2 + +```powershell +$identity = "TestTeamsAppPermissionPolicy" + (Get-Date -Format FileDateTimeUniversal) +New-CsTeamsAppPermissionPolicy -Identity Set-$identity +Set-CsTeamsAppPermissionPolicy -Identity Set-$identity -DefaultCatalogAppsType AllowedAppList -DefaultCatalogApps @() -GlobalCatalogAppsType AllowedAppList -GlobalCatalogApps @() -PrivateCatalogAppsType AllowedAppList -PrivateCatalogApps @() +``` +This example blocks all Microsoft apps, third-party apps, and custom apps. No apps are allowed. + +### Example 3 + +```powershell +$identity = "TestTeamsAppPermissionPolicy" + (Get-Date -Format FileDateTimeUniversal) +# create a new Teams app permission policy and block all apps +New-CsTeamsAppPermissionPolicy -Identity Set-$identity -DefaultCatalogAppsType AllowedAppList -GlobalCatalogAppsType AllowedAppList -PrivateCatalogAppsType AllowedAppList -DefaultCatalogApps @() -GlobalCatalogApps @() -PrivateCatalogApps @() + +$ListsApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.DefaultCatalogApp -Property @{Id="0d820ecd-def2-4297-adad-78056cde7c78"} +$OneNoteApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.DefaultCatalogApp -Property @{Id="26bc2873-6023-480c-a11b-76b66605ce8c"} +$DefaultCatalogAppList = @($ListsApp,$OneNoteApp) +# set allow Lists and OneNote apps and block other Microsoft apps +Set-CsTeamsAppPermissionPolicy -Identity Set-$identity -DefaultCatalogAppsType AllowedAppList -DefaultCatalogApps $DefaultCatalogAppList +``` +This example allows Microsoft Lists and OneNote apps and blocks other Microsoft apps. Microsoft Lists and OneNote can be installed by your users. + +### Example 4 + +```powershell +$identity = "TestTeamsAppPermissionPolicy" + (Get-Date -Format FileDateTimeUniversal) +# create a new Teams app permission policy and block all apps +New-CsTeamsAppPermissionPolicy -Identity Set-$identity -DefaultCatalogAppsType AllowedAppList -GlobalCatalogAppsType AllowedAppList -PrivateCatalogAppsType AllowedAppList -DefaultCatalogApps @() -GlobalCatalogApps @() -PrivateCatalogApps @() +$TaskListApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.GlobalCatalogApp -Property @{Id="57c81e84-9b7b-4783-be4e-0b7ffc0719af"} +$OnePlanApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.GlobalCatalogApp -Property @{Id="ca0540bf-6b61-3027-6313-a7cb4470bf1b"} +$GlobalCatalogAppList = @($TaskListApp,$OnePlanApp) +# set allow TaskList and OnePlan apps and block other Third-party apps +Set-CsTeamsAppPermissionPolicy -Identity Set-$identity -GlobalCatalogAppsType AllowedAppList -GlobalCatalogApps $GlobalCatalogAppList +``` +This example allows third-party TaskList and OnePlan apps and blocks other third-party apps. TaskList and OnePlan can be installed by your users. + +### Example 5 + +```powershell +$identity = "TestTeamsAppPermissionPolicy" + (Get-Date -Format FileDateTimeUniversal) +# create a new Teams app permission policy and block all apps +New-CsTeamsAppPermissionPolicy -Identity Set-$identity -DefaultCatalogAppsType BlockedAppList -GlobalCatalogAppsType BlockedAppList -PrivateCatalogAppsType BlockedAppList -DefaultCatalogApps @() -GlobalCatalogApps @() -PrivateCatalogApps @() +$GetStartApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PrivateCatalogApp -Property @{Id="f8374f94-b179-4cd2-8343-9514dc5ea377"} +$TestBotApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PrivateCatalogApp -Property @{Id="47fa3584-9366-4ce7-b1eb-07326c6ba799"} +$PrivateCatalogAppList = @($GetStartApp,$TestBotApp) +# set allow TaskList and OnePlan apps and block other custom apps +Set-CsTeamsAppPermissionPolicy -Identity Set-$identity -PrivateCatalogAppsType AllowedAppList -PrivateCatalogApps $PrivateCatalogAppList +``` +This example allows custom GetStartApp and TestBotApp apps and blocks other custom apps. GetStartApp and TestBotApp can be installed by your users. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultCatalogApps +Choose which Teams apps published by Microsoft or its partners can be installed by your users. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.DefaultCatalogApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DefaultCatalogAppsType +Choose to allow or block the installation of Microsoft apps. Values that can be used: AllowedAppList, BlockedAppList. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Description of app setup permission policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Do not use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GlobalCatalogApps +Choose which Teams apps published by a third party can be installed by your users. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.GlobalCatalogApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GlobalCatalogAppsType +Choose to allow or block the installation of third-party apps. Values that can be used: AllowedAppList, BlockedAppList. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of App setup permission policy. If empty, all Identities will be used by default. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Do not use. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -PrivateCatalogApps +Choose to allow or block the installation of custom apps. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.PrivateCatalogApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivateCatalogAppsType +Choose which custom apps can be installed by your users. Values that can be used: AllowedAppList, BlockedAppList. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Do not use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.DefaultCatalogApp +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.GlobalCatalogApp +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.PrivateCatalogApp + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsAppSetupPolicy.md b/teams/teams-ps/teams/Set-CsTeamsAppSetupPolicy.md new file mode 100644 index 0000000000..1e6e8b5c3a --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsAppSetupPolicy.md @@ -0,0 +1,364 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsappsetuppolicy +applicable: Microsoft Teams +title: Set-CsTeamsAppSetupPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsAppSetupPolicy + +## SYNOPSIS +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsTeamsAppSetupPolicy [[-Identity] <XdsIdentity>] + [-AllowSideLoading <Boolean>] + [-AllowUserPinning <Boolean>] + [-AppPresetList <Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset[]>] + [-Confirm] + [-Description <String>] + [-Force] + [-PinnedAppBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp[]>] + [-PinnedCallingBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedCallingBarApp[]>] + [-PinnedMessageBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp[]>] + [-AppPresetMeetingList <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPresetMeeting]>] + [-AdditionalCustomizationApps <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AdditionalCustomizationApp]>] + [-Tenant <System.Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +### Instance +```powershell +Set-CsTeamsAppSetupPolicy [-Instance <PSObject>] + [-AllowSideLoading <Boolean>] + [-AllowUserPinning <Boolean>] + [-AppPresetList <Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset[]>] + [-Confirm] + [-Description <String>] + [-Force] + [-PinnedAppBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp[]>] + [-PinnedCallingBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedCallingBarApp[]>] + [-PinnedMessageBarApps <Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp[]>] + [-AppPresetMeetingList <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPresetMeeting]>] + [-AdditionalCustomizationApps <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AdditionalCustomizationApp]>] + [-Tenant <System.Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +**NOTE**: The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience. + +As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. + +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + +## EXAMPLES + +### Example 1 + +```powershell +# Create new teams app setup policy named "Set-Test". +New-CsTeamsAppSetupPolicy -Identity 'Set-Test' +Set-CsTeamsAppSetupPolicy -Identity 'Set-Test' -AllowUserPinning $true -AllowSideLoading $false +``` + +Step 1: Create a new Teams app setup policy named "Set-Test". +Step 2: Set AllowUserPinning as true, AllowSideLoading as false. + +### Example 2 + +```powershell +New-CsTeamsAppSetupPolicy -Identity 'Set-Test' +$ActivityApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp -Property @{Id="14d6962d-6eeb-4f48-8890-de55454bb136"} +$ChatApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp -Property @{Id="86fcd49b-61a2-4701-b771-54728cd291fb"} +$TeamsApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp -Property @{Id="2a84919f-59d8-4441-a975-2a8c2643b741"} +$PinnedAppBarApps = @($ActivityApp,$ChatApp,$TeamsApp) +Set-CsTeamsAppSetupPolicy -Identity 'Set-Test' -PinnedAppBarApps $PinnedAppBarApps +``` + +Step 1: Create new teams app setup policy named "Set-Test". +Step 2: Set ActivityApp, ChatApp, TeamsApp as PinnedAppBarApps. +Step 3: Settings to pin these apps to the app bar in Teams client. + +### Example 3 + +```powershell +New-CsTeamsAppSetupPolicy -Identity 'Set-Test' +$VivaConnectionsApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp -Property @{Id="d2c6f111-ffad-42a0-b65e-ee00425598aa"} +$PinnedMessageBarApps = @($VivaConnectionsApp) +Set-CsTeamsAppSetupPolicy -Identity 'Set-Test' -PinnedMessageBarApps $PinnedMessageBarApps +``` + +Step 1: Create new teams app setup policy named "Set-Test". +Step 2: Set VivaConnectionsApp as PinnedAppBarApps. +Step 3: Settings to pin these apps to the messaging extension in Teams client. + +### Example 4 + +```powershell +New-CsTeamsAppSetupPolicy -Identity 'Set-Test' +$VivaConnectionsApp = New-Object -TypeName Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset -Property @{Id="d2c6f111-ffad-42a0-b65e-ee00425598aa"} +$AppPresetList = @($VivaConnectionsApp) +Set-CsTeamsAppSetupPolicy -Identity 'Set-Test' -AppPresetList $AppPresetList +``` + +Step 1: Create new teams app setup policy named "Set-Test". +Step 2: Set VivaConnectionsApp as AppPresetList +Step 3: Settings to install these apps in your users' personal Teams environment. + +## PARAMETERS + +### -Identity +Name of app setup policy. If empty, all identities will be used by default. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Do not use. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -AllowSideLoading +This is also known as side loading. This setting determines if a user can upload a custom app package in the Teams app. Turning it on lets you create or develop a custom app to be used personally or across your organization without having to submit it to the Teams app store. Uploading a custom app also lets you test an app before you distribute it more widely by only assigning it to a single user or group of users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserPinning +If you turn this on, the user's existing app pins will be added to the list of pinned apps set in this policy. Users can rearrange, add, and remove pins as they choose. If you turn this off, the user's existing app pins will be removed and replaced with the apps defined in this policy. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppPresetList +Choose which apps and messaging extensions you want to be installed in your users' personal Teams environment and in meetings they create. Users can install other available apps from the Teams app store. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AdditionalCustomizationApps +This parameter allows IT admins to create multiple customized versions of their apps and assign these customized versions to users and groups via setup policies. It enables customization of app icons and names for supportive first-party (1P) and third-party (3P) apps, enhancing corporate connections to employees through brand expression and stimulating app awareness and usage. + +```yaml +Type: System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AdditionalCustomizationApp] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppPresetMeetingList +This parameter is used to manage the list of preset apps that are available during meetings. It allows admins to control which apps are pinned and set the order in which they appear, ensuring that users have quick access to the relevant apps during meetings. + +```yaml +Type: System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPresetMeeting] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Description of App setup policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Do not use. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinnedAppBarApps +Pinning an app displays the app in the app bar in Teams client. Admins can pin apps and they can allow users to pin apps. Pinning is used to highlight apps that users need the most and promote ease of access. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinnedCallingBarApps +Determines the list of apps that are pre pinned for a participant in Calls. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedCallingBarApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PinnedMessageBarApps +Apps will be pinned in messaging extensions and into the ellipsis menu. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Do not use. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.AppPreset + +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedApp + +### Microsoft.Teams.Policy.Administration.Cmdlets.Core.PinnedMessageBarApp + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsAudioConferencingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsAudioConferencingPolicy.md new file mode 100644 index 0000000000..aee67a3709 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsAudioConferencingPolicy.md @@ -0,0 +1,174 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsaudioconferencingpolicy +title: Set-CsTeamsAudioConferencingPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsAudioConferencingPolicy + +## SYNOPSIS + +Audio conferencing policies can be used to manage audio conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsAudioConferencingPolicy [-AllowTollFreeDialin <Boolean>] [-Force] [[-Identity] <String>] + [-MeetingInvitePhoneNumbers <Object>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsAudioConferencingPolicy [-AllowTollFreeDialin <Boolean>] [-Force] + [-MeetingInvitePhoneNumbers <Object>] [-Instance <PSObject>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The Set-CsTeamsAudioConferencingPolicy cmdlet enables administrators to control audio conferencing toll- and toll-free numbers to be displayed in meeting invites created by users within your organization. The Set-CsTeamsAudioConferencingPolicy can be used to update an audio-conferencing policy that has been configured for use in your organization. + +## EXAMPLES + +### EXAMPLE 1 +``` +PS C:\> Set-CsTeamsAudioConferencingPolicy -Identity "EMEA Users" -AllowTollFreeDialin $False +``` + +In this example, AllowTollFreeDialin is set to false. All other policy properties will be left as previously assigned. + +### EXAMPLE 2 +``` +PS C:\> Set-CsTeamsAudioConferencingPolicy -Identity "EMEA Users" -AllowTollFreeDialin $True -MeetingInvitePhoneNumbers "+49695095XXXXX","+353156YYYYY","+1800856ZZZZZ" +``` + +In this example, two different property values are configured: AllowTollFreeDialIn is set to True and -MeetingInvitePhoneNumbers is set to include the following Toll and Toll free numbers - "+49695095XXXXX","+353156YYYYY","+1800856ZZZZZ" other policy properties will be left as previously assigned. + +## PARAMETERS + +### -AllowTollFreeDialin +Determines if users of this Policy can have Toll free numbers. If toll-free numbers are available in your Microsoft Audio Conferencing bridge, this parameter controls if they can be used to join the meetings of a given user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier for the policy to be Set. To set the global policy, use this syntax: -Identity global. To set a per-user policy use syntax similar to this: -Identity "Emea Users". +If this parameter is not included, the Set-CsTeamsAudioConferencingPolicy cmdlet will modify the Global policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -MeetingInvitePhoneNumbers +Determines the list of audio-conferencing Toll- and Toll-free telephone numbers that will be included in meetings invites created by users of this policy. If no phone numbers are specified, then the phone number that is displayed in meeting invites created by users would be based on the location of the users. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### PSObject +## OUTPUTS + +### Object +## NOTES + +## RELATED LINKS + +[Get-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsaudioconferencingpolicy) + +[New-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsaudioconferencingpolicy) + +[Grant-CsTeamsAudioConferencingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsaudioconferencingpolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsCallHoldPolicy.md b/teams/teams-ps/teams/Set-CsTeamsCallHoldPolicy.md new file mode 100644 index 0000000000..27aaba2f36 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsCallHoldPolicy.md @@ -0,0 +1,203 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamscallholdpolicy +applicable: Microsoft Teams +title: Set-CsTeamsCallHoldPolicy +schema: 2.0.0 +ms.reviewer: +manager: abnair +ms.author: serdars +author: serdarsoysal +--- + +# Set-CsTeamsCallHoldPolicy + +## SYNOPSIS + +Modifies an existing Teams call hold policy in your tenant. The Teams call hold policy is used to customize the call hold experience for Teams clients. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsCallHoldPolicy [-Identity] <string> [-Description <string>] [-AudioFileId <string>] [-StreamingSourceUrl <string>] [-StreamingSourceAuthType <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Teams call hold policies are used to customize the call hold experience for teams clients. + +When Microsoft Teams users participate in calls, they have the ability to hold a call and have the other entity in the call listen to an audio file during the duration of the hold. + +Assigning a Teams call hold policy to a user sets an audio file to be played during the duration of the hold. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsCallHoldPolicy -Identity "ContosoPartnerTeamsCallHoldPolicy" -AudioFileId "c65233-ac2a27-98701b-123ccc" +``` + +The command shown in Example 1 modifies an existing per-user Teams call hold policy with the Identity ContosoPartnerTeamsCallHoldPolicy. + +This policy is re-assigned the audio file ID to be used to: c65233-ac2a27-98701b-123ccc, which is the ID referencing an audio file that was uploaded using the Import-CsOnlineAudioFile cmdlet. + +Any Microsoft Teams users who are assigned this policy will have their call holds customized such that the user being held will hear the audio file specified by AudioFileId. + +### Example 2 +```powershell +PS C:\> Set-CsTeamsCallHoldPolicy -Identity "ContosoPartnerTeamsCallHoldPolicy" -Description "country music" +``` + +The command shown in Example 2 modifies an existing per-user Teams call hold policy with the Identity ContosoPartnerTeamsCallHoldPolicy. + +This policy is re-assigned the description from its existing value to "country music". + +## PARAMETERS + +### -Identity +Unique identifier of the Teams call hold policy being modified. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams call hold policy. + +For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AudioFileId +A string representing the ID referencing an audio file uploaded via the Import-CsOnlineAudioFile cmdlet. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreamingSourceUrl +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreamingSourceAuthType +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallholdpolicy) + +[New-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallholdpolicy) + +[Grant-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallholdpolicy) + +[Remove-CsTeamsCallHoldPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallholdpolicy) + +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) diff --git a/teams/teams-ps/teams/Set-CsTeamsCallParkPolicy.md b/teams/teams-ps/teams/Set-CsTeamsCallParkPolicy.md new file mode 100644 index 0000000000..14c75e129a --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsCallParkPolicy.md @@ -0,0 +1,267 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamscallparkpolicy +applicable: Microsoft Teams +title: Set-CsTeamsCallParkPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsTeamsCallParkPolicy + +## SYNOPSIS + +The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone. The Set-CsTeamsCallParkPolicy cmdlet lets you update a policy that has already been created for your organization. + +NOTE: The call park feature is currently available in desktop, mobile, and web clients. Supported with TeamsOnly mode. + +## SYNTAX + +```powershell +Set-CsTeamsCallParkPolicy [-AllowCallPark <Boolean>] [-Description <String>] [[-Identity] <String>] + [-ParkTimeoutSeconds <Int64>] [-PickupRangeEnd <Int64>] [-PickupRangeStart <Int64>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Identity (Default) +```powershell +Set-CsTeamsCallParkPolicy [-Tenant <System.Guid>] [-AllowCallPark <Boolean>] [-PickupRangeStart <Integer>] [-PickupRangeEnd <Integer>] [-ParkTimeoutSeconds <Integer>] [[-Identity] <XdsIdentity>] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +```powershell +Set-CsTeamsCallParkPolicy [-Tenant <System.Guid>] [-AllowCallPark <Boolean>] [-Instance <PSObject>] [-Force] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams. Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different phone. The Set-CsTeamsCallParkPolicy cmdlet lets you update a policy that has already been created for your organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsCallParkPolicy -Identity SalesPolicy -AllowCallPark $true +``` + +Update the existing policy "SalesPolicy" to enable the call park feature. + +### Example 2 +```powershell +PS C:\> Set-CsTeamsCallParkPolicy -Identity "SalesPolicy" -PickupRangeStart 500 -PickupRangeEnd 1500 +``` + +Update the existing policy "SalesPolicy" to generate pickup numbers starting from 500 and up until 1500. + +### Example 3 +```powershell +PS C:\> New-CsTeamsCallParkPolicy -Identity "SalesPolicy" -ParkTimeoutSeconds 600 +``` + +Update the existing policy "SalesPolicy" to ring back the parker after 600 seconds if the parked call is unanswered + +## PARAMETERS + +### -AllowCallPark +If set to true, customers will be able to leverage the call park feature to place calls on hold and then decide how the call should be handled - transferred to another department, retrieved using the same phone, or retrieved using a different phone. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppress all non-fatal errors + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The unique identifier of the policy being updated. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +This parameter is used when piping a specific policy retrieved from Get-CsTeamsCallParkPolicy that you then want to update. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -PickupRangeEnd +Specify the maximum value that a rendered pickup code can take. Value can be from 10 to 9999. + +Note: PickupRangeStart must be smaller than PickupRangeEnd. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 99 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParkTimeoutSeconds +Specify the number of seconds to wait before ringing the parker when the parked call hasn't been picked up. Value can be from 120 to 1800 (seconds). + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 300 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PickupRangeStart +Specify the minimum value that a rendered pickup code can take. Value can be from 10 to 9999. + +Note: PickupRangeStart must be smaller than PickupRangeEnd. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 10 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Description of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode +For Internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsCallingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsCallingPolicy.md new file mode 100644 index 0000000000..1f3a0f0fe7 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsCallingPolicy.md @@ -0,0 +1,738 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamscallingpolicy +applicable: Microsoft Teams +title: Set-CsTeamsCallingPolicy +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: alejandramu +--- + +# Set-CsTeamsCallingPolicy + +## SYNOPSIS +Use this cmdlet to update values in existing Teams Calling Policies. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsTeamsCallingPolicy [-Identity] <string> + [-AIInterpreter <string>] + [-AllowCallForwardingToPhone <boolean>] + [-AllowCallForwardingToUser <boolean>] + [-AllowCallGroups <boolean>] + [-AllowCallRedirect <string>] + [-AllowCloudRecordingForCalls <boolean>] + [-AllowDelegation <boolean>] + [-AllowPrivateCalling <boolean>] + [-AllowSIPDevicesCalling <boolean>] + [-AllowTranscriptionForCalling <boolean>] + [-AllowVoicemail <string>] + [-AllowWebPSTNCalling <boolean>] + [-AutoAnswerEnabledType <String>] + [-BusyOnBusyEnabledType <string>] + [-CallRecordingExpirationDays <long>] + [-CallingSpendUserLimit <long>] + [-Confirm] + [-Copilot <string>] + [-EnableSpendLimits <boolean>] + [-EnableWebPstnMediaBypass <Boolean>] + [-Force] + [-InboundFederatedCallRoutingTreatment <string>] + [-InboundPstnCallRoutingTreatment <string>] + [-LiveCaptionsEnabledTypeForCalling <string>] + [-MusicOnHoldEnabledType <string>] + [-PopoutAppPathForIncomingPstnCalls <string>] + [-PopoutForIncomingPstnCalls <string>] + [-PreventTollBypass <boolean>] + [-SpamFilteringEnabledType <string>] + [-VoiceSimulationInInterpreter <string>] + [-RealTimeText <string>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The Teams Calling Policy controls which calling and call forwarding features are available to users in Microsoft Teams. This cmdlet allows admins to set values in +a given Calling Policy instance. + +Only the parameters specified are changed. Other parameters keep their existing values. + +## EXAMPLES + +### Example 1 +``` +PS C:\> Set-CsTeamsCallingPolicy -Identity Global -AllowPrivateCalling $true +``` + +Sets the value of the parameter AllowPrivateCalling in the Global (default) Teams Calling Policy instance. + +### Example 2 +``` +PS C:\> Set-CsTeamsCallingPolicy -Identity HRPolicy -LiveCaptionsEnabledTypeForCalling Disabled +``` + +Sets the value of the parameter LiveCaptionsEnabledTypeForCalling to Disabled in the Teams Calling Policy instance called HRPolicy. + +## PARAMETERS + +### -Identity +Name of the policy instance being created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AIInterpreter +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the AI Interpreter related features + +Possible values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallForwardingToPhone +Enables the user to configure in the Microsoft Teams client call forwarding or simultaneous ringing of inbound calls to any phone number. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallForwardingToUser +Enables the user to configure in the Microsoft Teams client call forwarding or simultaneous ringing of inbound calls to other users in your tenant. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallGroups +Enables the user to configure call groups in the Microsoft Teams client and that inbound calls should be routed to call groups. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallRedirect +Setting this parameter enables local call redirection for SIP devices connecting via the Microsoft Teams SIP gateway. + +Valid options are: + +- Enabled: Enables the user to redirect an incoming call. +- Disabled: The user is not enabled to redirect an incoming call. +- UserOverride: This option is not available for use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCloudRecordingForCalls +Determines whether cloud recording is allowed in a user's 1:1 Teams or PSTN calls. Set this to True to allow the user to be able to record 1:1 calls. Set this to False to prohibit the user from recording 1:1 calls. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowDelegation +Enables the user to configure delegation in the Microsoft Teams client and that inbound calls to be routed to delegates; allows delegates to make outbound calls on behalf of the users for whom they have delegated permissions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateCalling +Controls all calling capabilities in Teams. Turning this off will turn off all calling functionality in Teams. +If you use Skype for Business for calling, this policy will not affect calling functionality in Skype for Business. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSIPDevicesCalling +Determines whether the user is allowed to use a SIP device for calling on behalf of a Teams client. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTranscriptionForCalling +Determines whether post-call transcriptions are allowed. Set this to True to allow. Set this to False to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowVoicemail +Enables inbound calls to be routed to voicemail. + +Valid options are: + +- AlwaysEnabled: Calls are always forwarded to voicemail on unanswered after ringing for thirty seconds, regardless of the unanswered call forward setting for the user. +- AlwaysDisabled: Calls are never routed to voicemail, regardless of the call forward or unanswered settings for the user. Voicemail isn't available as a call forwarding or unanswered setting in Teams. +- UserOverride: Calls are forwarded to voicemail based on the call forwarding and/or unanswered settings for the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWebPSTNCalling +Allows PSTN calling from the Teams web client. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoAnswerEnabledType + +Allow admins to enable or disable Auto-answer settings for users. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BusyOnBusyEnabledType +Setting this parameter lets you configure how incoming calls are handled when a user is already in a call or conference or has a call placed on hold. + +Valid options are: + +- Enabled: New or incoming calls will be rejected with a busy signal. +- Unanswered: The user's unanswered settings will take effect, such as routing to voicemail or forwarding to another user. +- Disabled: New or incoming calls will be presented to the user. +- UserOverride: Users can set their busy options directly from call settings in Teams app. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallingSpendUserLimit +The maximum amount a user can spend on outgoing PSTN calls, including all calls made through Pay-as-you-go Calling Plans and any overages on plans with bundled minutes. + +Possible values: any positive integer + +```yaml +Type: Long +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallRecordingExpirationDays +Sets the expiration of the recorded 1:1 calls. Default is 60 days. + +```yaml +Type: Long +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Copilot +Setting this parameter lets you control how Copilot is used during calls and if transcription is needed to be turned on and saved after the call. + +Valid options are: +- Enabled: Copilot can work with or without transcription during calls. This is the default value. +- EnabledWithTranscript: Copilot will only work when transcription is enabled during calls. +- Disabled: Copilot is disabled for calls. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the calling policy. For example, the Description might indicate the users to whom the policy should be assigned. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSpendLimits +This setting allows an admin to enable or disable spend limits on PSTN calls for their user base. + +Possible values: + +- True +- False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableWebPstnMediaBypass + +Determines if MediaBypass is enabled for PSTN calls on specified Web platforms. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundFederatedCallRoutingTreatment +Setting this parameter lets you control how inbound federated calls should be routed. + +Valid options are: + +- RegularIncoming: No changes are made to default inbound routing. This is the default setting. +- Unanswered: The inbound federated call will be routed according to the called user's unanswered call settings and the call will not be presented to the called user. The called user will see a missed call notification. If the called user has not enabled unanswered call settings the call will be disconnected. +- Voicemail: The inbound federated call will be routed directly to the called user's voicemail and the call will not be presented to the user. If the called user does not have voicemail enabled the call will be disconnected. + +Setting this parameter to Unanswered or Voicemail will have precedence over other call forwarding settings like call forward/simultaneous ringing to delegate, call groups, or call forwarding. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: RegularIncoming +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundPstnCallRoutingTreatment +Setting this parameter lets you control how inbound PSTN calls should be routed. + +Valid options are: + +- RegularIncoming: No changes are made to default inbound routing. This is the default setting. +- Unanswered: The inbound PSTN call will be routed according to the called user's unanswered call settings and the call will not be presented to the called user. The called user will see a missed call notification. If the called user has not enabled unanswered call settings the call will be disconnected. +- Voicemail: The inbound PSTN call will be routed directly to the called user's voicemail and the call will not be presented to the user. If the called user does not have voicemail enabled the call will be disconnected. +- UserOverride: Users can determine their PSTN call routing choice from call settings in the Teams app. + +Setting this parameter to Unanswered or Voicemail will have precedence over other call forwarding settings like call forward/simultaneous ringing to delegate, call groups, or call forwarding. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: RegularIncoming +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveCaptionsEnabledTypeForCalling +Determines whether real-time captions are available for the user in Teams calls. + +Valid options are: + +- DisabledUserOverride: Allows the user to turn on live captions. +- Disabled: Prohibits the user from turning on live captions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MusicOnHoldEnabledType +Setting this parameter allows you to turn on or turn off the music on hold when a caller is placed on hold. + +Valid options are: + +- Enabled: Music on hold is enabled. This is the default. +- Disabled: Music on hold is disabled. +- UserOverride: For now, setting the value to UserOverride is the same as Enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopoutAppPathForIncomingPstnCalls +Setting this parameter allows you to set the PopoutForIncomingPstnCalls setting's URL path of the website to launch upon receiving incoming PSTN calls. This parameter accepts an HTTPS URL with less than 1024 characters. The URL can contain a `{phone}` placeholder that is replaced with the caller's PSTN number in E.164 format when launched. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: "" +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PopoutForIncomingPstnCalls +Setting this parameter allows you to control the tenant users' ability to launch an external website URL automatically in the browser window upon incoming PSTN calls for specific users or user groups. Valid options are Enabled and Disabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreventTollBypass +Setting this parameter to True will send calls through PSTN and incur charges rather than going through the network and bypassing the tolls. + +> [!NOTE] +> Do not set this parameter to True for Calling Plan or Operator Connect users as it will prevent successful call routing. This setting only works with Direct Routing which is configured to handle location-based routing restrictions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpamFilteringEnabledType +Determines if spam detection is enabled for inbound PSTN calls. + +Possible values: + +- Enabled: Spam detection is enabled. In case the inbound call is considered spam, the user will get a "Spam Likely" label in Teams. +- Disabled: Spam detection is disabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceSimulationInInterpreter + +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the voice simulation feature while being AI interpreted. + +Possible Values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeText +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Allows users to use real time text during a call, allowing them to communicate by typing their messages in real time. + +Possible Values: +- Enabled: User is allowed to turn on real time text. +- Disabled: User is not allowed to turn on real time text. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscallingpolicy) + +[Remove-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscallingpolicy) + +[Grant-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscallingpolicy) + +[New-CsTeamsCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscallingpolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsChannelsPolicy.md b/teams/teams-ps/teams/Set-CsTeamsChannelsPolicy.md new file mode 100644 index 0000000000..a6e29ca6ed --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsChannelsPolicy.md @@ -0,0 +1,270 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamschannelspolicy +applicable: Microsoft Teams +title: Set-CsTeamsChannelsPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsTeamsChannelsPolicy + +## SYNOPSIS + +The CsTeamsChannelsPolicy allows you to manage features related to the Teams and Channels experience within the Teams application. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsChannelsPolicy [-Tenant <Guid>] [-AllowOrgWideTeamCreation <Boolean>] + [-EnablePrivateTeamDiscovery <Boolean>] [-AllowPrivateChannelCreation <Boolean>] + [-AllowUserToParticipateInExternalSharedChannel <Boolean>] [-AllowChannelSharingToExternalUser <Boolean>] [-AllowSharedChannelCreation <Boolean>] [-ThreadedChannelCreation <String>] + [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsChannelsPolicy [-Tenant <Guid>] [-AllowOrgWideTeamCreation <Boolean>] + [-EnablePrivateTeamDiscovery <Boolean>] [-AllowPrivateChannelCreation <Boolean>] + [-AllowUserToParticipateInExternalSharedChannel <Boolean>] [-AllowChannelSharingToExternalUser <Boolean>] [-AllowSharedChannelCreation <Boolean>] + [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsChannelsPolicy allows you to manage features related to the Teams & Channels experience within the Teams application. + +This cmdlet allows you to update existing policies of this type. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsChannelsPolicy -Identity StudentPolicy -EnablePrivateTeamDiscovery $true +``` + +This example shows updating an existing policy with name "StudentPolicy" and enabling Private Team Discovery. + +## PARAMETERS + +### -EnablePrivateTeamDiscovery +Determines whether a user is allowed to discover private teams in suggestions and search results. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Bypass all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Use this parameter to specify the name of the policy being updated. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Use this parameter to pass the policy object output of Get-CsTeamsChannelsPolicy to update that policy. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOrgWideTeamCreation +Determines whether a user is allowed to create an org-wide team. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateChannelCreation +Determines whether a user is allowed to create a private channel. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowChannelSharingToExternalUser +Owners of a shared channel can invite external users to join the channel if Microsoft Entra external sharing policies are configured. If the channel has been shared with an external member or team, they will continue to have access to the channel even if this parameter is set to FALSE. For more information, see [Manage channel policies in Microsoft Teams](https://learn.microsoft.com/microsoftteams/teams-policies). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSharedChannelCreation +Team owners can create shared channels for people within and outside the organization. Only people added to the shared channel can read and write messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserToParticipateInExternalSharedChannel +Users and teams can be invited to external shared channels if Microsoft Entra external sharing policies are configured. If a team in your organization is part of an external shared channel, new team members will have access to the channel even if this parameter is set to FALSE. For more information, see [Manage channel policies in Microsoft Teams](https://learn.microsoft.com/microsoftteams/teams-policies). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ThreadedChannelCreation +This setting enables/disables Threaded Channel creation and editing. + +Possible Values: +- Enabled: Users are allowed to create and edit Threaded Channels. +- Disabled: Users are not allowed to create and edit Threaded Channels. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[New-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamschannelspolicy) + +[Remove-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamschannelspolicy) + +[Grant-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamschannelspolicy) + +[Get-CsTeamsChannelsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamschannelspolicy) diff --git a/skype/skype-ps/skype/Set-CsTeamsClientConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsClientConfiguration.md similarity index 88% rename from skype/skype-ps/skype/Set-CsTeamsClientConfiguration.md rename to teams/teams-ps/teams/Set-CsTeamsClientConfiguration.md index 2f8ddabc3b..d2685ba41e 100644 --- a/skype/skype-ps/skype/Set-CsTeamsClientConfiguration.md +++ b/teams/teams-ps/teams/Set-CsTeamsClientConfiguration.md @@ -1,27 +1,27 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsclientconfiguration -applicable: Skype for Business Online -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsclientconfiguration +applicable: Microsoft Teams +Module Name: MicrosoftTeams title: Set-CsTeamsClientConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTeamsClientConfiguration ## SYNOPSIS -The TeamsClientConfiguration allows IT admins to control the settings that can be accessed via Teams clients across their organization. This configuration includes settings like which third party cloud storage your organization allows, whether or not guest users can access the teams client, and how Surface Hub devices can interact with Skype for Business meetings. The parameter descriptions below describe what settings are managed by this configuration and how they are enforced. +The TeamsClientConfiguration allows IT admins to control the settings that can be accessed via Teams clients across their organization. This configuration includes settings like which third party cloud storage your organization allows, whether or not guest users can access the teams client, and how Surface Hub devices can interact with Skype for Business meetings. The parameter descriptions below describe what settings are managed by this configuration and how they are enforced. ## SYNTAX ### Identity (Default) ``` Set-CsTeamsClientConfiguration [-Tenant <System.Guid>] [-AllowEmailIntoChannel <Boolean>] - [-RestrictedSenderList <String>] [-AllowDropBox <Boolean>] [-AllowEgnyte <Boolean>] [-AllowBox <Boolean>] [-AllowGoogleDrive <Boolean>] + [-RestrictedSenderList <String>] [-AllowDropBox <Boolean>] [-AllowEgnyte <Boolean>] [-AllowBox <Boolean>] [-AllowGoogleDrive <Boolean>] [-AllowRoleBasedChatPermissions <Boolean>] [-AllowShareFile <Boolean>] [-AllowOrganizationTab <Boolean>] [-AllowSkypeBusinessInterop <Boolean>] [-AllowTBotProactiveMessaging <Boolean>] [-ContentPin <String>] [-AllowResourceAccountSendMessage <Boolean>] [-ResourceAccountContentAccess <String>] [-AllowGuestUser <Boolean>] @@ -32,7 +32,7 @@ Set-CsTeamsClientConfiguration [-Tenant <System.Guid>] [-AllowEmailIntoChannel < ### Instance ``` Set-CsTeamsClientConfiguration [-Tenant <System.Guid>] [-AllowEmailIntoChannel <Boolean>] - [-RestrictedSenderList <String>] [-AllowDropBox <Boolean>] [-AllowEgnyte <Boolean>] [-AllowBox <Boolean>] [-AllowGoogleDrive <Boolean>] + [-RestrictedSenderList <String>] [-AllowDropBox <Boolean>] [-AllowEgnyte <Boolean>] [-AllowBox <Boolean>] [-AllowGoogleDrive <Boolean>] [-AllowRoleBasedChatPermissions <Boolean>] [-AllowShareFile <Boolean>] [-AllowOrganizationTab <Boolean>] [-AllowSkypeBusinessInterop <Boolean>] [-AllowTBotProactiveMessaging <Boolean>] [-ContentPin <String>] [-AllowResourceAccountSendMessage <Boolean>] [-ResourceAccountContentAccess <String>] [-AllowGuestUser <Boolean>] @@ -41,9 +41,9 @@ Set-CsTeamsClientConfiguration [-Tenant <System.Guid>] [-AllowEmailIntoChannel < ``` ## DESCRIPTION -The TeamsClientConfiguration allows IT admins to control the settings that can be accessed via Teams clients across their organization. This configuration includes settings like which third party cloud storage your organization allows, whether or not guest users can access the teams client, and whether or not meeting room devices running teams are can display content from user accounts. The parameter descriptions below describe what settings are managed by this configuration and how they are enforced. +The TeamsClientConfiguration allows IT admins to control the settings that can be accessed via Teams clients across their organization. This configuration includes settings like which third party cloud storage your organization allows, whether or not guest users can access the teams client, and whether or not meeting room devices running teams are can display content from user accounts. The parameter descriptions below describe what settings are managed by this configuration and how they are enforced. -An organization can have only one effective Teams Client Configuration - these settings will apply across the entire organization for the particular features they control. +An organization can have only one effective Teams Client Configuration - these settings will apply across the entire organization for the particular features they control. Note that three of these settings (ContentPin, ResourceAccountContentAccess, and AllowResourceAccountSendMessage) control resource account behavior for Surface Hub devices attending Skype for Business meetings, and are not used in Microsoft Teams. @@ -106,7 +106,7 @@ Accept wildcard characters: False ### -AllowEmailIntoChannel When set to $true, mail hooks are enabled, and users can post messages to a channel by sending an email to the email address of Teams channel. -To find the email address for a channel, click the More options menu for the channel and then select Get email address. +To find the email address for a channel, click the More options menu for the channel and then select Get email address. ```yaml Type: Boolean @@ -136,7 +136,7 @@ Accept wildcard characters: False ``` ### -AllowGuestUser -Designates whether or not guest users in your organization will have access to the Teams client. If $true, guests in your tenant will be able to access the Teams client. Note that this setting has a core dependency on Guest Access being enabled in your Office 365 tenant. For more information on this topic, read Authorize Guest Access in Microsoft Teams: https://docs.microsoft.com/microsoftteams/teams-dependencies +Designates whether or not guest users in your organization will have access to the Teams client. If $true, guests in your tenant will be able to access the Teams client. Note that this setting has a core dependency on Guest Access being enabled in your Office 365 tenant. For more information on this topic, read Authorize Guest Access in Microsoft Teams: https://learn.microsoft.com/microsoftteams/teams-dependencies ```yaml Type: Boolean @@ -180,6 +180,20 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AllowRoleBasedChatPermissions +When set to True, Supervised Chat is enabled for the tenant. + +```yaml +Type: Boolean +Parameter Sets: (All) + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -AllowScopedPeopleSearchandAccess If set to $true, the Exchange address book policy (ABP) will be used to provide customized view of the global address book for each user. This is only a virtual separation and not a legal separation. @@ -196,7 +210,7 @@ Accept wildcard characters: False ``` ### -AllowShareFile -Designates whether users are able to leverage ShareFile as a third party storage solution in Microsoft Teams. If $true, users will be able to add ShareFile in the client and interact with the files stored there. +Designates whether users are able to leverage Citrix ShareFile as a third party storage solution in Microsoft Teams. If $true, users will be able to add Citrix ShareFile in the client and interact with the files stored there. ```yaml Type: Boolean @@ -211,7 +225,7 @@ Accept wildcard characters: False ``` ### -AllowSkypeBusinessInterop -When set to $true, Teams conversations automatically show up in Skype for Business for users that aren't enabled for Teams. +When set to $true, Teams conversations automatically show up in Skype for Business for users that aren't enabled for Teams. ```yaml Type: Boolean @@ -289,6 +303,7 @@ Accept wildcard characters: False ### -Identity The only valid input is Global - the tenant wide configuration. + ```yaml Type: XdsIdentity Parameter Sets: Identity @@ -334,7 +349,7 @@ Accept wildcard characters: False ``` ### -RestrictedSenderList -Senders domains can be further restricted to ensure that only allowed SMTP domains can send emails to the Teams channels. This is a comma-separated string of the domains you'd like to *allow* to send emails to Teams channels. +Senders domains can be further restricted to ensure that only allowed SMTP domains can send emails to the Teams channels. This is a semicolon-separated string of the domains you'd like to *allow* to send emails to Teams channels. ```yaml Type: String @@ -364,8 +379,7 @@ Accept wildcard characters: False ``` ### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. +The WhatIf switch does not work with this cmdlet. ```yaml Type: SwitchParameter @@ -380,14 +394,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### System.Management.Automation.PSObject - ## OUTPUTS ### System.Object diff --git a/skype/skype-ps/skype/Set-CsTeamsComplianceRecordingApplication.md b/teams/teams-ps/teams/Set-CsTeamsComplianceRecordingApplication.md similarity index 89% rename from skype/skype-ps/skype/Set-CsTeamsComplianceRecordingApplication.md rename to teams/teams-ps/teams/Set-CsTeamsComplianceRecordingApplication.md index b4f6b6d3cb..1e7e7f36f9 100644 --- a/skype/skype-ps/skype/Set-CsTeamsComplianceRecordingApplication.md +++ b/teams/teams-ps/teams/Set-CsTeamsComplianceRecordingApplication.md @@ -1,413 +1,415 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication -applicable: Skype for Business Online -title: Set-CsTeamsComplianceRecordingApplication -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# Set-CsTeamsComplianceRecordingApplication - -## SYNOPSIS -Modifies an existing association between an application instance of a policy-based recording application and a Teams recording policy for administering automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] - [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] - [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] - [-Priority <Int32>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Instance <PSObject>] - [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] - [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] - [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] - [-Priority <Int32>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Policy-based recording applications are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. - -Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. - -Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. -Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeMeetingJoin $false -RequiredDuringMeeting $false -``` - -The command shown in Example 1 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is made optional for meetings. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredDuringMeeting parameters for more information. - -### Example 2 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeCallEstablishment $false -RequiredDuringCall $false -``` - -The command shown in Example 2 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is made optional for calls. -Please refer to the documentation of the RequiredBeforeCallEstablishment and RequiredDuringCall parameters for more information. - -### Example 3 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -ConcurrentInvitationCount 2 -``` - -The command shown in Example 3 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is made resilient by specifying that two invites must be sent to the same application for the same call or meeting. -Please refer to the documentation of the ConcurrentInvitationCount parameter for more information. - -### Example 4 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -ComplianceRecordingPairedApplications @(New-CsTeamsComplianceRecordingPairedApplication -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') -``` - -The command shown in Example 4 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application is made resilient by pairing it with another application instance of a policy-based recording application with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. -Separate invites are sent to the paired applications for the same call or meeting. -Please refer to the documentation of the ComplianceRecordingPairedApplications parameter for more information. - -### Example 5 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -ComplianceRecordingPairedApplications $null -``` - -The command shown in Example 5 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. - -In this example, the application's resiliency is removed by removing the pairing it had with the application instance of a policy-based recording application with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. -Please refer to the documentation of the ComplianceRecordingPairedApplications parameter for more information. - -### Example 6 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingApplication | Set-CsTeamsComplianceRecordingApplication -RequiredBeforeMeetingJoin $false -RequiredDuringMeeting $false -``` - -The command shown in Example 6 modifies all existing associations between application instances of policy-based recording applications and their corresponding Teams recording policy. - -In this example, all applications are made optional for meetings. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredDuringMeeting parameters for more information. - -## PARAMETERS - -### -Identity -A name that uniquely identifies the application instance of the policy-based recording application. - -Application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. -To do this association correctly, the Identity of these application instances must be \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. -For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -RequiredBeforeMeetingJoin -Indicates whether the policy-based recording application must be in the meeting before the user is allowed to join the meeting. - -If this is set to True, the user will not be allowed to join the meeting if the policy-based recording application fails to join the meeting. -The meeting will still continue for users who are in the meeting. - -If this is set to False, the user will be allowed to join the meeting even if the policy-based recording application fails to join the meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredDuringMeeting -Indicates whether the policy-based recording application must be in the meeting while the user is in the meeting. - -If this is set to True, the user will be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. -The meeting will still continue for users who are in the meeting. - -If this is set to False, the user will not be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredBeforeCallEstablishment -Indicates whether the policy-based recording application must be in the call before the call is allowed to establish. - -If this is set to True, the call will be cancelled if the policy-based recording application fails to join the call. - -If this is set to False, call establishment will proceed normally if the policy-based recording application fails to join the call. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RequiredDuringCall -Indicates whether the policy-based recording application must be in the call while the call is active. - -If this is set to True, the call will be cancelled if the policy-based recording application leaves the call or is dropped from the call. - -If this is set to False, call establishment will proceed normally if the policy-based recording application leaves the call or is dropped from the call. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ConcurrentInvitationCount -Determines the number of invites to send out to the application instance of the policy-based recording application. - -In situations where application resiliency is a necessity, multiple invites can be sent to the same application for the same call or meeting. -If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. - -If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. - -If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. - -If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. - -If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. - -Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. -However, you cannot do both. -Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. - -```yaml -Type: UInt32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: 1 -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ComplianceRecordingPairedApplications -Determines the other policy-based recording applications to pair with this application to achieve application resiliency. - -In situations where application resiliency is a necessity, invites can be sent to separate paired applications for the same call or meeting. -If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. - -If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. - -If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. - -If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. -Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. - -If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. - -Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. -However, you cannot do both. -Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. - -```yaml -Type: ComplianceRecordingPairedApplication[] -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Priority -This priority determines the order in which the policy-based recording applications are displayed in the output of the Get-CsTeamsComplianceRecordingPolicy cmdlet. - -All policy-based recording applications are invited in parallel to ensure low call setup and meeting join latencies. -So this parameter does not affect the order of invitations to the applications, or any other routing. - -```yaml -Type: Int32 -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Set-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication +applicable: Microsoft Teams +title: Set-CsTeamsComplianceRecordingApplication +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# Set-CsTeamsComplianceRecordingApplication + +## SYNOPSIS +Modifies an existing association between an application instance of a policy-based recording application and a Teams recording policy for administering automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] + [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] + [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] + [-Priority <Int32>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsComplianceRecordingApplication [-Tenant <System.Guid>] [-Instance <PSObject>] + [-RequiredBeforeMeetingJoin <Boolean>] [-RequiredDuringMeeting <Boolean>] + [-RequiredBeforeCallEstablishment <Boolean>] [-RequiredDuringCall <Boolean>] + [-ConcurrentInvitationCount <UInt32>] [-ComplianceRecordingPairedApplications <ComplianceRecordingPairedApplication[]>] + [-Priority <Int32>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Policy-based recording applications are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to enforce compliance with the administrative set policy. + +Instances of these applications are created using CsOnlineApplicationInstance cmdlets and are then associated with Teams recording policies. + +Note that application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +Once the association is done, the Identity of these application instances becomes \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. +Please also refer to the documentation of CsTeamsComplianceRecordingPolicy cmdlets for further information. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeMeetingJoin $false -RequiredDuringMeeting $false +``` + +The command shown in Example 1 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is made optional for meetings. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredDuringMeeting parameters for more information. + +### Example 2 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -RequiredBeforeCallEstablishment $false -RequiredDuringCall $false +``` + +The command shown in Example 2 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is made optional for calls. +Please refer to the documentation of the RequiredBeforeCallEstablishment and RequiredDuringCall parameters for more information. + +### Example 3 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -ConcurrentInvitationCount 2 +``` + +The command shown in Example 3 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is made resilient by specifying that two invites must be sent to the same application for the same call or meeting. +Please refer to the documentation of the ConcurrentInvitationCount parameter for more information. + +### Example 4 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -ComplianceRecordingPairedApplications @(New-CsTeamsComplianceRecordingPairedApplication -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') +``` + +The command shown in Example 4 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application is made resilient by pairing it with another application instance of a policy-based recording application with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. +Separate invites are sent to the paired applications for the same call or meeting. +Please refer to the documentation of the ComplianceRecordingPairedApplications parameter for more information. + +### Example 5 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingApplication -Identity 'Tag:ContosoPartnerComplianceRecordingPolicy/d93fefc7-93cc-4d44-9a5d-344b0fff2899' -ComplianceRecordingPairedApplications $null +``` + +The command shown in Example 5 modifies an existing association between an application instance of a policy-based recording application with ObjectId d93fefc7-93cc-4d44-9a5d-344b0fff2899 and a Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. + +In this example, the application's resiliency is removed by removing the pairing it had with the application instance of a policy-based recording application with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144. +Please refer to the documentation of the ComplianceRecordingPairedApplications parameter for more information. + +### Example 6 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingApplication | Set-CsTeamsComplianceRecordingApplication -RequiredBeforeMeetingJoin $false -RequiredDuringMeeting $false +``` + +The command shown in Example 6 modifies all existing associations between application instances of policy-based recording applications and their corresponding Teams recording policy. + +In this example, all applications are made optional for meetings. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredDuringMeeting parameters for more information. + +## PARAMETERS + +### -Identity +A name that uniquely identifies the application instance of the policy-based recording application. + +Application instances of policy-based recording applications must be associated with a Teams recording policy using the CsTeamsComplianceRecordingApplication cmdlets. +To do this association correctly, the Identity of these application instances must be \<Identity of the associated Teams recording policy\>/\<ObjectId of the application instance\>. +For example, the Identity of an application instance can be \"Tag:ContosoPartnerComplianceRecordingPolicy/39dc3ede-c80e-4f19-9153-417a65a1f144\", which indicates that the application instance with ObjectId 39dc3ede-c80e-4f19-9153-417a65a1f144 is associated with the Teams recording policy with Identity ContosoPartnerComplianceRecordingPolicy. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -RequiredBeforeMeetingJoin +Indicates whether the policy-based recording application must be in the meeting before the user is allowed to join the meeting. + +If this is set to True, the user will not be allowed to join the meeting if the policy-based recording application fails to join the meeting. +The meeting will still continue for users who are in the meeting. + +If this is set to False, the user will be allowed to join the meeting even if the policy-based recording application fails to join the meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredDuringMeeting +Indicates whether the policy-based recording application must be in the meeting while the user is in the meeting. + +If this is set to True, the user will be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. +The meeting will still continue for users who are in the meeting. + +If this is set to False, the user will not be ejected from the meeting if the policy-based recording application leaves the meeting or is dropped from the meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredBeforeCallEstablishment +Indicates whether the policy-based recording application must be in the call before the call is allowed to establish. + +If this is set to True, the call will be cancelled if the policy-based recording application fails to join the call. + +If this is set to False, call establishment will proceed normally if the policy-based recording application fails to join the call. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RequiredDuringCall +Indicates whether the policy-based recording application must be in the call while the call is active. + +If this is set to True, the call will be cancelled if the policy-based recording application leaves the call or is dropped from the call. + +If this is set to False, call establishment will proceed normally if the policy-based recording application leaves the call or is dropped from the call. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConcurrentInvitationCount +Determines the number of invites to send out to the application instance of the policy-based recording application. Can be set to 1 or 2 only. + +In situations where application resiliency is a necessity, multiple invites can be sent to the same application for the same call or meeting. +If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. + +If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. + +If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. + +If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. + +If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. + +Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. +However, you cannot do both. +Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 1 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceRecordingPairedApplications +Determines the other policy-based recording applications to pair with this application to achieve application resiliency. Can only have one paired application. + +In situations where application resiliency is a necessity, invites can be sent to separate paired applications for the same call or meeting. +If multiple such invites are accepted, then it means that multiple instances of this application are in the call or meeting and each of those instances can record independent of the others. + +If all of the invites are rejected, the application invitation process is deemed a failure and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredBeforeMeetingJoin and RequiredBeforeCallEstablishment parameters. + +If at least one of the invites is accepted and the others are rejected, the application invitation process is still deemed a success. + +If multiple invites are accepted and all of the instances leave or get dropped from the call or meeting, then the application is no longer in the call or meeting and the other flags for this application control what happens next. +Please refer to the documentation of the RequiredDuringMeeting and RequiredDuringCall parameters. + +If multiple invites are accepted and at least one of the instances remains in the call or meeting, then the application is in the call or meeting. + +Note that application resiliency can be achieved either by sending multiple invites to the same application using ConcurrentInvitationCount or by sending invites to separate paired applications using ComplianceRecordingPairedApplications. +However, you cannot do both. +Please work with your Microsoft certified policy-based recording application provider to determine if application resiliency is needed for your workflows and how best to achieve application resiliency. + +```yaml +Type: ComplianceRecordingPairedApplication[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority +This priority determines the order in which the policy-based recording applications are displayed in the output of the Get-CsTeamsComplianceRecordingPolicy cmdlet. + +All policy-based recording applications are invited in parallel to ensure low call setup and meeting join latencies. +So this parameter does not affect the order of invitations to the applications, or any other routing. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Set-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/skype/skype-ps/skype/Set-CsTeamsComplianceRecordingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsComplianceRecordingPolicy.md similarity index 77% rename from skype/skype-ps/skype/Set-CsTeamsComplianceRecordingPolicy.md rename to teams/teams-ps/teams/Set-CsTeamsComplianceRecordingPolicy.md index f6284bcd33..482a4c801b 100644 --- a/skype/skype-ps/skype/Set-CsTeamsComplianceRecordingPolicy.md +++ b/teams/teams-ps/teams/Set-CsTeamsComplianceRecordingPolicy.md @@ -1,298 +1,361 @@ ---- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingpolicy -applicable: Skype for Business Online -title: Set-CsTeamsComplianceRecordingPolicy -schema: 2.0.0 -manager: nakumar -author: aditdalvi -ms.author: aditd -ms.reviewer: ---- - -# Set-CsTeamsComplianceRecordingPolicy - -## SYNOPSIS -Modifies an existing Teams recording policy for governing automatic policy-based recording in your tenant. -Automatic policy-based recording is only applicable to Microsoft Teams users. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] - [-Enabled <Boolean>] [-WarnUserOnRemoval <Boolean>] [-Description <String>] - [-ComplianceRecordingApplications <ComplianceRecordingApplication[]>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Instance <PSObject>] - [-Enabled <Boolean>] [-WarnUserOnRemoval <Boolean>] [-Description <String>] - [-ComplianceRecordingApplications <ComplianceRecordingApplication[]>] - [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -Teams recording policies are used in automatic policy-based recording scenarios. -When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. - -Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. -Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. - -Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. -The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. -Existing calls and meetings are unaffected. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899') -``` - -The command shown in Example 1 modifies an existing per-user Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. -This policy is re-assigned a single application instance of a policy-based recording application: d93fefc7-93cc-4d44-9a5d-344b0fff2899, which is the ObjectId of the application instance as obtained from the Get-CsOnlineApplicationInstance cmdlet. - -Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by that application instance. Existing calls and meetings are unaffected. - -### Example 2 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899'), @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') -``` - -Example 2 is a variation of Example 1. -In this case, the Teams recording policy is re-assigned two application instances of policy-based recording applications. - -Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by both those application instances. Existing calls and meetings are unaffected. - -### Example 3 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $false -``` - -The command shown in Example 3 stops automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. - -### Example 4 -```powershell -PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $true -``` - -The command shown in Example 4 causes automatic policy-based recording to occur for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. - -### Example 5 -```powershell -PS C:\> Get-CsTeamsComplianceRecordingPolicy | Set-CsTeamsComplianceRecordingPolicy -Enabled $false -``` - -The command shown in Example 5 stops automatic policy-based recording for all Teams recording policies. -This effectively stops automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned any Teams recording policy. Existing calls and meetings are unaffected. - -## PARAMETERS - -### -Identity -Unique identifier to be assigned to the new Teams recording policy. - -Use the "Global" Identity if you wish to assign this policy to the entire tenant. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Instance -Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. - -```yaml -Type: PSObject -Parameter Sets: Instance -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByValue) -Accept wildcard characters: False -``` - -### -Enabled -Controls whether this Teams recording policy is active or not. - -Setting this to True and having the right set of ComplianceRecordingApplications will initiate automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. - -Setting this to False will stop automatic policy-based recording for any new calls or meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WarnUserOnRemoval -This parameter is reserved for future use. - -```yaml -Type: Boolean -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Enables administrators to provide explanatory text to accompany a Teams recording policy. For example, the Description might include information about the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -ComplianceRecordingApplications -A list of application instances of policy-based recording applications to assign to this policy. -The Id of each of these application instances must be the ObjectId of the application instance as obtained by the Get-CsOnlineApplicationInstance cmdlet. - -Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. -Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. - -```yaml -Type: ComplianceRecordingApplication[] -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Tenant -Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. -For example: - --Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" - -You can return your tenant ID by running this command: - -Get-CsTenant | Select-Object DisplayName, TenantID - -If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. -Instead, the tenant ID will automatically be filled in for you based on your connection information. -The Tenant parameter is primarily for use in a hybrid deployment. - -```yaml -Type: System.Guid -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Suppresses the display of any non-fatal error message that might arise when running the command. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object - -## RELATED LINKS - -[Get-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingpolicy?view=skype-ps) - -[New-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpolicy?view=skype-ps) - -[Grant-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csteamscompliancerecordingpolicy?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingpolicy?view=skype-ps) - -[Get-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/get-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingapplication?view=skype-ps) - -[Set-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/set-csteamscompliancerecordingapplication?view=skype-ps) - -[Remove-CsTeamsComplianceRecordingApplication](https://docs.microsoft.com/powershell/module/skype/remove-csteamscompliancerecordingapplication?view=skype-ps) - -[New-CsTeamsComplianceRecordingPairedApplication](https://docs.microsoft.com/powershell/module/skype/new-csteamscompliancerecordingpairedapplication?view=skype-ps) +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingpolicy +applicable: Microsoft Teams +title: Set-CsTeamsComplianceRecordingPolicy +schema: 2.0.0 +manager: nakumar +author: aditdalvi +ms.author: aditd +ms.reviewer: +--- + +# Set-CsTeamsComplianceRecordingPolicy + +## SYNOPSIS +Modifies an existing Teams recording policy for governing automatic policy-based recording in your tenant. +Automatic policy-based recording is only applicable to Microsoft Teams users. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Identity <XdsIdentity>] + [-Enabled <Boolean>] [-WarnUserOnRemoval <Boolean>] [-Description <String>] + [-DisableComplianceRecordingAudioNotificationForCalls <Boolean>] [-RecordReroutedCalls <Boolean>] + [-ComplianceRecordingApplications <ComplianceRecordingApplication[]>] [-CustomBanner <Guid>] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsComplianceRecordingPolicy [-Tenant <System.Guid>] [-Instance <PSObject>] + [-Enabled <Boolean>] [-WarnUserOnRemoval <Boolean>] [-Description <String>] + [-ComplianceRecordingApplications <ComplianceRecordingApplication[]>] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Teams recording policies are used in automatic policy-based recording scenarios. +When Microsoft Teams users participate in meetings or make or receive calls, the policy-based recording applications i.e. bots associated with the user's Teams recording policy are invited into the call or meeting to record audio, video and video-based screen sharing activity. + +Note that simply assigning a Teams recording policy to a Microsoft Teams user will not activate automatic policy-based recording for all Microsoft Teams calls and meetings that the user participates in. +Among other things, you will need to create an application instance of a policy-based recording application i.e. a bot in your tenant and will then need to assign an appropriate policy to the user. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. + +Assigning your Microsoft Teams users a Teams recording policy activates automatic policy-based recording for all new Microsoft Teams calls and meetings that the users participate in. +The system will load the recording application and join it to appropriate calls and meetings in order for it to enforce compliance with the administrative set policy. +Existing calls and meetings are unaffected. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899') +``` + +The command shown in Example 1 modifies an existing per-user Teams recording policy with the Identity ContosoPartnerComplianceRecordingPolicy. +This policy is re-assigned a single application instance of a policy-based recording application: d93fefc7-93cc-4d44-9a5d-344b0fff2899, which is the ObjectId of the application instance as obtained from the Get-CsOnlineApplicationInstance cmdlet. + +Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by that application instance. Existing calls and meetings are unaffected. + +### Example 2 + +```powershell +PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id 'd93fefc7-93cc-4d44-9a5d-344b0fff2899'), @(New-CsTeamsComplianceRecordingApplication -Parent 'ContosoPartnerComplianceRecordingPolicy' -Id '39dc3ede-c80e-4f19-9153-417a65a1f144') +``` + +Example 2 is a variation of Example 1. +In this case, the Teams recording policy is re-assigned two application instances of policy-based recording applications. + +Any Microsoft Teams users who are assigned this policy will have their calls and meetings recorded by both those application instances. Existing calls and meetings are unaffected. + +### Example 3 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $false +``` + +The command shown in Example 3 stops automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. + +### Example 4 +```powershell +PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity 'ContosoPartnerComplianceRecordingPolicy' -Enabled $true +``` + +The command shown in Example 4 causes automatic policy-based recording to occur for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. + +### Example 5 +```powershell +PS C:\> Get-CsTeamsComplianceRecordingPolicy | Set-CsTeamsComplianceRecordingPolicy -Enabled $false +``` + +The command shown in Example 5 stops automatic policy-based recording for all Teams recording policies. +This effectively stops automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned any Teams recording policy. Existing calls and meetings are unaffected. + +## PARAMETERS + +### -Identity +Unique identifier to be assigned to the new Teams recording policy. + +Use the "Global" Identity if you wish to assign this policy to the entire tenant. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### CustomBanner +References the Custom Banner text in the storage. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +Controls whether this Teams recording policy is active or not. + +Setting this to True and having the right set of ComplianceRecordingApplications will initiate automatic policy-based recording for all new calls and meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. + +Setting this to False will stop automatic policy-based recording for any new calls or meetings of all Microsoft Teams users who are assigned this policy. Existing calls and meetings are unaffected. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WarnUserOnRemoval +This parameter is reserved for future use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams recording policy. For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ComplianceRecordingApplications +A list of application instances of policy-based recording applications to assign to this policy. +The Id of each of these application instances must be the ObjectId of the application instance as obtained by the Get-CsOnlineApplicationInstance cmdlet. + +Please work with your Microsoft certified policy-based recording application provider to obtain an instance of their recording application. +Please refer to the documentation of the CsOnlineApplicationInstance cmdlets for information on how to create an application instance of a policy-based recording application. + +```yaml +Type: ComplianceRecordingApplication[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -DisableComplianceRecordingAudioNotificationForCalls +Setting this attribute to true disables recording audio notifications for 1:1 calls that are under compliance recording + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableComplianceRecordingAudioNotificationForCalls +Setting this attribute to true disables recording audio notifications for 1:1 calls that are under compliance recording. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordReroutedCalls +Setting this attribute to true enables compliance recording for calls that have been re-routed from a compliance recording-enabled user. Supported call scenarios include forward, transfer, delegation, call groups, and simultaneous ring. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Teams recording policies are being queried. +For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingpolicy) + +[New-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpolicy) + +[Grant-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamscompliancerecordingpolicy) + +[Remove-CsTeamsComplianceRecordingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingpolicy) + +[Get-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/get-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingapplication) + +[Set-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/set-csteamscompliancerecordingapplication) + +[Remove-CsTeamsComplianceRecordingApplication](https://learn.microsoft.com/powershell/module/teams/remove-csteamscompliancerecordingapplication) + +[New-CsTeamsComplianceRecordingPairedApplication](https://learn.microsoft.com/powershell/module/teams/new-csteamscompliancerecordingpairedapplication) diff --git a/teams/teams-ps/teams/Set-CsTeamsCortanaPolicy.md b/teams/teams-ps/teams/Set-CsTeamsCortanaPolicy.md new file mode 100644 index 0000000000..15607b6980 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsCortanaPolicy.md @@ -0,0 +1,238 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/get-csteamscortanapolicy +applicable: Microsoft Teams +title: Set-CsTeamsCortanaPolicy +schema: 2.0.0 +manager: amehta +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsTeamsCortanaPolicy + +## SYNOPSIS +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsCortanaPolicy [-Tenant <System.Guid>] [-Description <String>] [-CortanaVoiceInvocationMode <String>] + [-AllowCortanaVoiceInvocation <Boolean>] [-AllowCortanaAmbientListening <Boolean>] + [-AllowCortanaInContextSuggestions <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsCortanaPolicy [-Tenant <System.Guid>] [-Description <String>] [-CortanaVoiceInvocationMode <String>] + [-AllowCortanaVoiceInvocation <Boolean>] [-AllowCortanaAmbientListening <Boolean>] + [-AllowCortanaInContextSuggestions <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsCortanaPolicy cmdlets enable administrators to control settings for Cortana voice assistant in Microsoft Teams. Specifically, these specify if a user can use Cortana voice assistant in Microsoft Teams and Cortana invocation behavior via CortanaVoiceInvocationMode parameter - +* Disabled - Cortana voice assistant is disabled +* PushToTalkUserOverride - Cortana voice assistant is enabled but without wake-word ("Hey Cortana") invocation +* WakeWordPushToTalkUserOverride - Cortana voice assistant is enabled with wake-word ("Hey Cortana") invocation on devices where wake-word is supported + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsCortanaPolicy -Identity MyCortanaPolicy -CortanaVoiceInvocationMode Disabled +``` +In this example, Cortana voice assistant is set to disabled. + +## PARAMETERS + +### -AllowCortanaAmbientListening +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCortanaInContextSuggestions +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCortanaVoiceInvocation +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CortanaVoiceInvocationMode +The value of this field indicates if Cortana is enabled and mode of invocation. +* Disabled - Cortana voice assistant is turned off and cannot be used. +* PushToTalkUserOverride - Cortana voice assistant is enabled but without wake-word ("Hey Cortana") invocation +* WakeWordPushToTalkUserOverride - Cortana voice assistant is enabled with wake-word ("Hey Cortana") invocation on devices where wake-word is supported + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of your policy to identify purpose of creating it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Identity for the policy you're modifying. To modify the global policy, use this syntax: -Identity global. To modify a per-user policy, use syntax similar to this: -Identity MyCortanaPolicy. +If you do not specify an Identity the Set-CsTeamsCortanaPolicy cmdlet will automatically modify the global policy. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" +You can return your tenant ID by running this command: +Get-CsTenant | Select-Object DisplayName, TenantID + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsCustomBannerText b/teams/teams-ps/teams/Set-CsTeamsCustomBannerText new file mode 100644 index 0000000000..e13c9bf900 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsCustomBannerText @@ -0,0 +1,93 @@ +--- +Module Name: MicrosoftTeams +title: Set-CsTeamsCustomBannerText +author: saleens7 +ms.author: wblocker +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsTeamsCustomBannerText +schema: 2.0.0 +--- + +# Set-CsTeamsCustomBannerText + +## SYNOPSIS + +Enables administrators to configure a custom text on the banner displayed when compliance recording bots start recording the call. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsCustomBannerText [[-Id] <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION + +Updates a single instance of a custom banner text. + +## EXAMPLES + +### Example 1 +PS C:\> Set-CsTeamsCustomBannerText -Identity CustomText +``` + +Sets the properties of the CustomText instance of TeamsCustomBannerText. + +## PARAMETERS + +### -Id +The Identity of the CustomBannerText. You do not need to provide an ID as the backend will generate it for you. However, if you wish to provide your own ID, you can provide your own GUID. Note that you have to provide a unique ID for every CsTeamsCustomBannerText you create. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Text +The text that the tenant admin would like to set in the policy. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description that the tenant admin would like to set to identify what this text represents. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/set-csteamscustombannertext) + +[New-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext) + +[Remove-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/remove-csteamscustombannertext) diff --git a/teams/teams-ps/teams/Set-CsTeamsCustomBannerText.md b/teams/teams-ps/teams/Set-CsTeamsCustomBannerText.md new file mode 100644 index 0000000000..131dd52c2a --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsCustomBannerText.md @@ -0,0 +1,93 @@ +--- +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsTeamsCustomBannerText +title: Set-CsTeamsCustomBannerText +schema: 2.0.0 +author: saleens7 +ms.author: wblocker +--- + +# Set-CsTeamsCustomBannerText + +## SYNOPSIS + +Enables administrators to update a configured custom text on the banner displayed when compliance recording bots start recording the call. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsCustomBannerText [-Id <Guid>] [-Text <String>] [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +Updates a single instance of custom banner text. + +## EXAMPLES + +### Example 1 +PS C:\> Set-CsTeamsCustomBannerText -Id 123e4567-e89b-12d3-a456-426614174000 -Description "Custom Banner Text Example" -Text "Custom Text" +``` + +This example sets the properties of the CustomText instance of TeamsCustomBannerText. + +## PARAMETERS + +### -Id +The Identity of the CustomBannerText. + +```yaml +Type: Guid +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Text +The text that you would like to set in the policy. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description that you would like to set to identify what this text represents. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/set-csteamscustombannertext) + +[New-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/new-csteamscustombannertext) + +[Remove-CsTeamsCustomBannerText](https://learn.microsoft.com/powershell/module/teams/remove-csteamscustombannertext) diff --git a/skype/skype-ps/skype/Set-CsTeamsEducationAssignmentsAppPolicy.md b/teams/teams-ps/teams/Set-CsTeamsEducationAssignmentsAppPolicy.md similarity index 92% rename from skype/skype-ps/skype/Set-CsTeamsEducationAssignmentsAppPolicy.md rename to teams/teams-ps/teams/Set-CsTeamsEducationAssignmentsAppPolicy.md index b2d8107dd9..3306c4828f 100644 --- a/skype/skype-ps/skype/Set-CsTeamsEducationAssignmentsAppPolicy.md +++ b/teams/teams-ps/teams/Set-CsTeamsEducationAssignmentsAppPolicy.md @@ -1,13 +1,14 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamseducationassignmentsapppolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamseducationassignmentsapppolicy +applicable: Microsoft Teams title: Set-CsTeamsEducationAssignmentsAppPolicy schema: 2.0.0 ms.reviewer: manager: bulenteg -ms.author: tomkau author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney --- # Set-CsTeamsEducationAssignmentsAppPolicy @@ -121,7 +122,7 @@ Accept wildcard characters: False ``` ### -ParentDigestEnabledType -Send digest emails to parents/guardians. Possible values are "Enabled" or "Disabled" +Send digest emails to parents/guardians. Possible values are "Enabled" or "Disabled" ```yaml Type: String @@ -212,14 +213,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### System.Management.Automation.PSObject - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Set-CsTeamsEducationConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsEducationConfiguration.md new file mode 100644 index 0000000000..2574fce8c8 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsEducationConfiguration.md @@ -0,0 +1,99 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Set-CsTeamsEducationConfiguration +author: SaritaBehera +ms.author: saritabehera +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamseducationconfiguration +schema: 2.0.0 +--- + +# Set-CsTeamsEdcuationConfiguration + +## SYNOPSIS + +This cmdlet is used to manage the organization-wide education configuration for Teams. + +## SYNTAX + +```powershell +Set-CsTeamsEducationConfiguration + [-ParentGuardianPreferredContactMethod <String>] + [-UpdateParentInformation <String>] + [-WhatIf] + [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet is used to manage the organization-wide education configuration for Teams which contains settings that are applicable to education organizations. + +You must be a Teams Service Administrator for your organization to run the cmdlet. + +## EXAMPLES + +### Example 1 +In this example, Email is set as the preferred contact method used for parent communication invitations across the organization. + +```powershell +Set-CsTeamsEducationConfiguration -ParentGuardianPreferredContactMethod Email +``` + +### Example 2 +In this example, SMS is set as the preferred contact method used for parent communication invitations across the organization. + +```powershell +Set-CsTeamsEducationConfiguration -ParentGuardianPreferredContactMethod SMS +``` + +### Example 3 +In this example, updating parents contact information is enabled by educators across the organization. + +```powershell +Set-CsTeamsEducationConfiguration -UpdateParentInformation Enabled +``` + +### Example 4 +In this example, updating parents contact information is disabled by educators across the organization. + +```powershell +Set-CsTeamsEducationConfiguration -UpdateParentInformation Disabled +``` + +## PARAMETERS + +### -ParentGuardianPreferredContactMethod +Indicates whether Email or SMS is the preferred contact method used for parent communication invitations. Possible values are 'Email' and 'SMS'. + +```yaml +Type: String +Position: Named +Default value: Email +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateParentInformation +Indicates whether updating parents contact information is Enabled/Disabled by educators. Possible values are 'Enabled' and 'Disabled'. + +```yaml +Type: String +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsEducationConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamseducationconfiguration) diff --git a/teams/teams-ps/teams/Set-CsTeamsEmergencyCallRoutingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsEmergencyCallRoutingPolicy.md new file mode 100644 index 0000000000..f17f6774c5 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsEmergencyCallRoutingPolicy.md @@ -0,0 +1,165 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallroutingpolicy +applicable: Microsoft Teams +title: Set-CsTeamsEmergencyCallRoutingPolicy +author: serdarsoysal +ms.author: serdars +ms.reviewer: chenc +schema: 2.0.0 +--- + +# Set-CsTeamsEmergencyCallRoutingPolicy + +## SYNOPSIS +This cmdlet modifies an existing Teams Emergency Call Routing Policy. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsEmergencyCallRoutingPolicy [[-Identity] <string>] [-AllowEnhancedEmergencyServices <bool>] + [-Description <string>] [-EmergencyNumbers <Object>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet modifies an existing Teams Emergency Call Routing Policy. Teams Emergency Call Routing policy is used for the life cycle of emergency call routing - emergency numbers and routing configuration + +## EXAMPLES + +### Example 1 +```powershell +Set-CsTeamsEmergencyCallRoutingPolicy -Identity "Test" -AllowEnhancedEmergencyServices:$false -Description "test" +``` + +This example modifies an existing Teams Emergency Call Routing Policy. + +### Example 2 +```powershell +$en1 = New-CsTeamsEmergencyNumber -EmergencyDialString "911" -EmergencyDialMask "933" -OnlinePSTNUsage "USE911" +$en2 = New-CsTeamsEmergencyNumber -EmergencyDialString "112" -EmergencyDialMask "9112" -OnlinePSTNUsage "DKE911" +Set-CsTeamsEmergencyCallRoutingPolicy -Identity "Test" -EmergencyNumbers @{add=$en1,$en2} +``` + +This example first creates new Teams emergency number objects and then adds these Teams emergency numbers to an existing Teams Emergency Call Routing policy. + +### Example 3 +```powershell +$en1 = New-CsTeamsEmergencyNumber -EmergencyDialString "112" -EmergencyDialMask "9112" -OnlinePSTNUsage "DKE911" +Set-CsTeamsEmergencyCallRoutingPolicy -Identity "Test" -EmergencyNumbers @{remove=$en1} +``` + +This example first creates a new Teams emergency number object and then removes that Teams emergency number from an existing Teams Emergency Call Routing policy. + +## PARAMETERS + +### -AllowEnhancedEmergencyServices +Flag to enable Enhanced Emergency Services. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provides a description of the Teams Emergency Call Routing policy to identify the purpose of setting it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyNumbers +One or more emergency number objects obtained from the [New-CsTeamsEmergencyNumber](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencynumber) cmdlet. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter is a unique identifier that designates the name of the policy. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallroutingpolicy) + +[Grant-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallroutingpolicy) + +[Remove-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallroutingpolicy) + +[Get-CsTeamsEmergencyCallRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallroutingpolicy) + +[New-CsTeamsEmergencyNumber](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencynumber) diff --git a/teams/teams-ps/teams/Set-CsTeamsEmergencyCallingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsEmergencyCallingPolicy.md new file mode 100644 index 0000000000..b67d6b3cd5 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsEmergencyCallingPolicy.md @@ -0,0 +1,233 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsemergencycallingpolicy +applicable: Microsoft Teams +title: Set-CsTeamsEmergencyCallingPolicy +author: serdarsoysal +ms.author: serdars +manager: roykuntz +ms.reviewer: chenc +schema: 2.0.0 +--- + +# Set-CsTeamsEmergencyCallingPolicy + +## SYNOPSIS + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsEmergencyCallingPolicy [-Identity] <string> [-ExtendedNotifications <PSListModifier[TeamsEmergencyCallingExtendedNotification]>] + [-NotificationGroup <string>] [-NotificationDialOutNumber <string>] [-ExternalLocationLookupMode <ExternalLocationLookupMode>] + [-NotificationMode <NotificationMode>] [-EnhancedEmergencyServiceDisclaimer <string>] + [-Description <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet modifies an existing Teams Emergency Calling policy. Emergency calling policy is used for the life cycle of emergency calling experience for the security desk and Teams client location experience. + +## EXAMPLES + +### Example 1 +```powershell +Set-CsTeamsEmergencyCallingPolicy -Identity "TestECP" -NotificationGroup "123@contoso.com;567@contoso.com" +``` + +This example modifies NotificationGroup of an existing policy instance with identity TestECP. + +### Example 2 +```powershell +$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "alert2@contoso.com" -NotificationMode ConferenceUnMuted +Set-CsTeamsEmergencyCallingPolicy -Identity "TestECP" -ExtendedNotifications @{remove=$en1} +``` + +This example first creates a new Teams Emergency Calling Extended Notification object and then removes that Teams Emergency Calling Extended Notification from an existing Teams Emergency Calling policy. + +### Example 3 +```powershell +$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "alert@contoso.com" -NotificationDialOutNumber "+14255551234" -NotificationMode ConferenceUnMuted +$en2 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "933" +Set-CsTeamsEmergencyCallingPolicy -Identity "TestECP" -ExtendedNotifications @{add=$en1,$en2} +``` + +This example first creates two new Teams Emergency Calling Extended Notification objects and then adds them to an existing Teams Emergency Calling policy with identity TestECP. + +## PARAMETERS + +### -Description +Provides a description of the Teams Emergency Calling policy to identify the purpose of setting it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnhancedEmergencyServiceDisclaimer +Allows the tenant administrator to configure a text string, which is shown at the top of the Calls app. The user can acknowledge the string by selecting OK. The string will be shown on client restart. The disclaimer can be up to 350 characters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExtendedNotifications +A list of one or more instances of TeamsEmergencyCallingExtendedNotification. Each TeamsEmergencyCallingExtendedNotification should use a unique EmergencyDialString. + +If an extended notification is found for an emergency phone number based on the EmergencyDialString parameter the extended notification will be controlling the notification. If no extended notification is found the notification settings on the policy instance itself will be used. + +```yaml +Type: System.Management.Automation.PSListModifier[Microsoft.Teams.Policy.Administration.Cmdlets.Core.TeamsEmergencyCallingExtendedNotification] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalLocationLookupMode +Enables ExternalLocationLookupMode. This mode allows users to set Emergency addresses for remote locations. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.ExternalLocationLookupMode +Parameter Sets: (All) +Aliases: +Accepted values: Disabled, Enabled + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter is a unique identifier that designates the name of the policy + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationDialOutNumber +This parameter represents the PSTN number which can be dialed out if NotificationMode is set to either of the two Conference values. The PSTN phone cannot be unmuted even when the NotificationMode is set to ConferenceUnMuted. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationGroup +NotificationGroup is an email list of users and groups to be notified of an emergency call via Teams chat. Individual users or groups are separated by ";", for instance, "group1@contoso.com;group2@contoso.com". A maximum of 10 e-mail addresses can be specified and a maximum of 50 users in total can be notified. Both UPN and SMTP address are accepted when adding users directly. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NotificationMode +The type of conference experience for security desk notification. +Possible values are NotificationOnly, ConferenceMuted, and ConferenceUnMuted. + +```yaml +Type: Microsoft.Teams.Policy.Administration.Cmdlets.Core.NotificationMode +Parameter Sets: (All) +Aliases: +Accepted values: NotificationOnly, ConferenceMuted, ConferenceUnMuted + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingpolicy) + +[Get-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsemergencycallingpolicy) + +[Remove-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsemergencycallingpolicy) + +[Grant-CsTeamsEmergencyCallingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsemergencycallingpolicy) + +[New-CsTeamsEmergencyCallingExtendedNotification](https://learn.microsoft.com/powershell/module/teams/new-csteamsemergencycallingextendednotification) diff --git a/teams/teams-ps/teams/Set-CsTeamsEnhancedEncryptionPolicy.md b/teams/teams-ps/teams/Set-CsTeamsEnhancedEncryptionPolicy.md new file mode 100644 index 0000000000..33b326f662 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsEnhancedEncryptionPolicy.md @@ -0,0 +1,209 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsenhancedencryptionpolicy +title: Set-CsTeamsEnhancedEncryptionPolicy +author: serdarsoysal +ms.author: serdars +manager: mdress +schema: 2.0.0 +--- + +# Set-CsTeamsEnhancedEncryptionPolicy + +## SYNOPSIS +Use this cmdlet to update values in existing Teams enhanced encryption policy. + +## SYNTAX + +``` +Set-CsTeamsEnhancedEncryptionPolicy [-Description <Object>] [-CallingEndtoEndEncryptionEnabledType <Object>] [-MeetingEndToEndEncryption <Object>] + [[-Identity] <Object>] [-Force] [-Instance <Object>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use this cmdlet to update values in existing Teams enhanced encryption policy. + +The TeamsEnhancedEncryptionPolicy enables administrators to determine which users in your organization can use the enhanced encryption settings in Teams, setting for end-to-end encryption in ad-hoc 1-to-1 VOIP calls is the parameter supported by this policy currently. + +## EXAMPLES + +### EXAMPLE 1 +```PowerShell +PS C:\> Set-CsTeamsEnhancedEncryptionPolicy -Identity "ContosoPartnerTeamsEnhancedEncryptionPolicy" -CallingEndtoEndEncryptionEnabledType DisabledUserOverride +``` + +The command shown in Example 1 modifies an existing per-user Teams enhanced encryption policy with the Identity ContosoPartnerTeamsEnhancedEncryptionPolicy. + +This policy is re-assigned CallingEndtoEndEncryptionEnabledType to be DisabledUserOverride. + +Any Microsoft Teams users who are assigned this policy will have their enhanced encryption policy customized such that the user can use the enhanced encryption setting in Teams. + +### EXAMPLE 2 +```PowerShell +PS C:\> Set-CsTeamsEnhancedEncryptionPolicy -Identity "ContosoPartnerTeamsEnhancedEncryptionPolicy" -MeetingEndToEndEncryption DisabledUserOverride +``` + +The command shown in Example 2 modifies an existing per-user Teams enhanced encryption policy with the Identity ContosoPartnerTeamsEnhancedEncryptionPolicy. + +This policy has re-assigned MeetingEndToEndEncryption to be DisabledUserOverride. + +Any Microsoft Teams users who are assigned this policy and have a Teams Premium license will have the option to create end-to-end encrypted meetings. [Learn more about end-to-end encryption for Teams meetings](https://support.microsoft.com/en-us/office/use-end-to-end-encryption-for-teams-meetings-a8326d15-d187-49c4-ac99-14c17dbd617c). + +### EXAMPLE 3 +```PowerShell +PS C:\> Set-CsTeamsEnhancedEncryptionPolicy -Identity "ContosoPartnerTeamsEnhancedEncryptionPolicy" -Description "allow useroverride" +``` + +The command shown in Example 2 modifies an existing per-user Teams enhanced encryption policy with the Identity ContosoPartnerTeamsEnhancedEncryptionPolicy. + +This policy is re-assigned the description from its existing value to "allow useroverride". + +## PARAMETERS + +### -Description +Enables administrators to provide explanatory text to accompany a Teams enhanced encryption policy. + +For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallingEndtoEndEncryptionEnabledType +Determines whether end-to-end encrypted calling is available for the user in Teams. Set this to DisabledUserOverride to allow user to turn on end-to-end encrypted calls. Set this to Disabled to prohibit. + +```yaml +Type: Enum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingEndToEndEncryption +Determines whether end-to-end encrypted meetings are available in Teams ([requires a Teams Premium license](https://www.microsoft.com/en-us/microsoft-teams/premium)). Set this to DisabledUserOverride to allow users to schedule end-to-end encrypted meetings. Set this to Disabled to prohibit. + +```yaml +Type: Enum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the Teams enhanced encryption policy. + +Use the "Global" Identity if you wish modify the policy set for the entire tenant. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Use this to pipe a specific enhanced encryption policy to be set. You can only modify the global policy, so can only pass the global instance of the enhanced encryption policy. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Object +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsenhancedencryptionpolicy) + +[New-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsenhancedencryptionpolicy) + +[Remove-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsenhancedencryptionpolicy) + +[Grant-CsTeamsEnhancedEncryptionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsenhancedencryptionpolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md b/teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md new file mode 100644 index 0000000000..bf14cb6cb1 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md @@ -0,0 +1,453 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamseventspolicy +title: Set-CsTeamsEventsPolicy +schema: 2.0.0 +ms.date: 04/23/2025 +--- + +# Set-CsTeamsEventsPolicy + +## SYNOPSIS +This cmdlet allows you to configure options for customizing Teams events experiences. Note that this policy is currently still in preview. + +## SYNTAX + +``` +Set-CsTeamsEventsPolicy [-AllowWebinars <String>] [-EventAccessType <String>] [-AllowTownhalls <String>] + [-TownhallEventAttendeeAccess <String>] [-AllowEmailEditing <String>] [-AllowedQuestionTypesInRegistrationForm <String>] + [-AllowEventIntegrations <Boolean>] [-AllowedWebinarTypesForRecordingPublish <String>] + [-AllowedTownhallTypesForRecordingPublish <String>] [-TownhallChatExperience <String>] [-Description <String>] + [-RecordingForTownhall <String>] [-RecordingForWebinar <String>] + [-TranscriptionForTownhall <String>] [-TranscriptionForWebinar <String>] + [-UseMicrosoftECDN <Boolean>] [-BroadcastPremiumApps <String>] +``` + +## DESCRIPTION +User-level policy for tenant admin to configure options for customizing Teams events experiences. Use this cmdlet to update an existing policy. + +## EXAMPLES + +### Example 1 +```powershell +Set-CsTeamsEventsPolicy -Identity Global -AllowWebinars Disabled +``` + +The command shown in Example 1 sets the value of the Default (Global) Events Policy in the organization to disable webinars, and leaves all other parameters the same. + +## PARAMETERS + +### -AllowWebinars +This setting governs if a user can create webinars using Teams Events. +Possible values are: + - **Enabled**: Enables creating webinars. + - **Disabled**: Disables creating webinars. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams Events policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseMicrosoftECDN +This setting governs whether the admin disables this property and prevents the organizers from creating town halls that use Microsoft eCDN even though they have been assigned a Teams Premium license. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTownhalls +This setting governs if a user can create town halls using Teams Events. +Possible values are: + - **Enabled**: Enables creating town halls. + - **Disabled**: Disables creating town halls. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TownhallEventAttendeeAccess +This setting governs what identity types may attend a Town hall that is scheduled by a particular person or group that is assigned this policy. +Possible values are: + - **Everyone**: Anyone with the join link may enter the event. + - **EveryoneInOrganizationAndGuests**: Only those who are Guests to the tenant, MTO users, and internal AAD users may enter the event. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Everyone +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams Events policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEmailEditing +This setting governs if a user is allowed to edit the communication emails in Teams Town Hall or Teams Webinar events. +Possible values are: + - **Enabled**: Enables editing of communication emails. + - **Disabled**: Disables editing of communication emails. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch does not work with this cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text to accompany a Teams Events policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EventAccessType + +> [!NOTE] +> Currently, webinar and town hall event access is managed together via EventAccessType. + +This setting governs which users can access the event registration page or the event site to register. It also governs which user type is allowed to join the session/s in the event. +Possible values are: + - **Everyone**: Enables creating events to allow in-tenant, guests, federated, and anonymous (external to the tenant) users to register and join the event. + - **EveryoneInCompanyExcludingGuests**: Enables creating events to allow only in-tenant users to register and join the event. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Unique identifier assigned to the Teams Events policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedQuestionTypesInRegistrationForm +This setting governs which users in a tenant can add which registration form questions to an event registration page for attendees to answer when registering for the event. + +Possible values are: +DefaultOnly, DefaultAndPredefinedOnly, AllQuestions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedTownhallTypesForRecordingPublish +This setting describes how IT admins can control which types of Town Hall attendees can have their recordings published. + +Possible values are: +None, InviteOnly, EveryoneInCompanyIncludingGuests, Everyone. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedWebinarTypesForRecordingPublish +This setting describes how IT admins can control which types of webinar attendees can have their recordings published. + +Possible values are: +None, InviteOnly, EveryoneInCompanyIncludingGuests, Everyone. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEventIntegrations +This setting governs access to the integrations tab in the event creation workflow. + +Possible values +true, false. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TownhallChatExperience +This setting governs whether the user can enable the Comment Stream chat experience for Town Halls. + +Possible values are: Optimized, None. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordingForTownhall +Determines whether recording is allowed in a user's townhall. + +Possible values are: + - **Enabled**: Allow recording in user's townhalls. + - **Disabled**: Prohibit recording in user's townhalls. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordingForWebinar +Determines whether recording is allowed in a user's webinar. + +Possible values are: + - **Enabled**: Allow recording in user's webinars. + - **Disabled**: Prohibit recording in user's webinars. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TranscriptionForTownhall +Determines whether transcriptions are allowed in a user's townhall. + +Possible values are: + - **Enabled**: Allow transcriptions in user's townhalls. + - **Disabled**: Prohibit transcriptions in user's townhalls. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TranscriptionForWebinar +Determines whether transcriptions are allowed in a user's webinar. + +Possible values are: + - **Enabled**: Allow transcriptions in user's webinars. + - **Disabled**: Prohibit transcriptions in user's webinars. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BroadcastPremiumApps +This setting will enable Tenant Admins to specify if an organizer of a Teams Premium town hall may add an app that is accessible by everyone, including attendees, in a broadcast style Event including a Town hall. This does not include control over apps (such as AI Producer and Custom Streaming Apps) that are only accessible by the Event group. + +Possible values are: +- **Enabled**: An organizer of a Premium town hall can add a Premium App such as Polls to the Town hall +- **Disabled**: An organizer of a Premium town hall CANNOT add a Premium App such as Polls to the Town hall + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +The Confirm switch does not work with this cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf switch does not work with this cmdlet. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsExternalAccessConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsExternalAccessConfiguration.md new file mode 100644 index 0000000000..3538e2a0af --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsExternalAccessConfiguration.md @@ -0,0 +1,129 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsexternalaccessconfiguration +title: Set-CsTeamsExternalAccessConfiguration +schema: 2.0.0 +--- + +# Set-CsTeamsExternalAccessConfiguration + +## SYNOPSIS + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsExternalAccessConfiguration [-BlockedUsers <List>] [-BlockExternalUserAccess <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [<CommonParameters>] +``` + +## DESCRIPTION +Allows admins to set values in the TeamsExternalAccessConfiguration, which specifies configs that can be used to improve entire org security. This configuration primarily allows admins to block malicious external users from the organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsExternalAccessConfiguration -Identity Global -BlockExternalAccessUserAccess $true +``` + +In this example, the admin has enabled the BlockExternalUserAccess. The users in the BlockedUsers will be blocked from communicating with the internal users. + +### Example 2 +```powershell +PS C:\> Set-CsTeamsExternalAccessConfiguration -Identity Global -BlockedUsers @("user1@malicious.com", "user2@malicious.com") +``` + +In this example, the admin has added two malicious users into the blocked list. These blocked users can't communicate with internal users anymore. + +## PARAMETERS + +### -BlockExternalAccessUserAccess +Designates whether BlockedUsers list is taking effect or not. $true means BlockedUsers are blocked and can't communicate with internal users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedUsers +You can specify blocked users using a List object that contains either the user email or the MRI from the external user you want to block. The user in the list will not able to communicate with the internal users in your organization. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Bypass confirmation + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The only option is Global + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsFeedbackPolicy.md b/teams/teams-ps/teams/Set-CsTeamsFeedbackPolicy.md new file mode 100644 index 0000000000..c6a1f2b39c --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsFeedbackPolicy.md @@ -0,0 +1,253 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsfeedbackpolicy +applicable: Microsoft Teams +title: Set-CsTeamsFeedbackPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsFeedbackPolicy + +## SYNOPSIS + +Use this cmdlet to modify a Teams feedback policy (the ability to send feedback about Teams to Microsoft and whether they receive the survey). + +## SYNTAX + +``` +Set-CsTeamsFeedbackPolicy [[-Identity] <String>] + [-AllowEmailCollection <Boolean>] + [-AllowLogCollection <Boolean>] + [-AllowScreenshotCollection <Boolean>] + [-Confirm] + [-EnableFeatureSuggestions <Boolean>] + [-Force] + [-Instance <Object>] + [-ReceiveSurveysMode <String>] + [-Tenant <Object>] + [-UserInitiatedMode <String>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Modifies a Teams feedback policy (the ability to send feedback about Teams to Microsoft and whether they receive the survey). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsFeedbackPolicy -identity "New Hire Feedback Policy" -userInitiatedMode enabled -receiveSurveysMode disabled +``` + +In this example, the policy "New Hire Feedback Policy" is modified, sets the userInitiatedMode parameter to enabled and the receiveSurveysMode parameter to disabled. + +## PARAMETERS + +### -Identity +The unique identifier of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveSurveysMode +Set the receiveSurveysMode parameter to enabled to allow users who are assigned the policy to receive the survey. +Set it to EnabledUserOverride to have users receive the survey and allow them to opt out. + +Possible values: + - Enabled + - Disabled + - EnabledUserOverride + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserInitiatedMode + Set the userInitiatedMode parameter to enabled to allow users who are assigned the policy to give feedback. + Setting the parameter to disabled turns off the feature and users who are assigned the policy don't have the option to give feedback. + +Possible values: + - Enabled + - Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEmailCollection +Set this to TRUE to enable Email collection. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLogCollection +Set this to TRUE to enable log collection. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowScreenshotCollection +Set this to TRUE to enable Screenshot collection. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableFeatureSuggestions +This setting will enable Tenant Admins to hide or show the Teams menu item "Help | Suggest a Feature". +Possible Values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsFilesPolicy.md b/teams/teams-ps/teams/Set-CsTeamsFilesPolicy.md new file mode 100644 index 0000000000..1a28cf4317 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsFilesPolicy.md @@ -0,0 +1,188 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsfilespolicy +title: Set-CsTeamsFilesPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsFilesPolicy + +## SYNOPSIS +Creates a new teams files policy. + Teams files policies determine whether or not files entry points to SharePoint enabled for a user. +The policies also specify third-party app ID to allow file storage (e.g., Box). + +## SYNTAX + +```powershell +Set-CsTeamsFilesPolicy [-NativeFileEntryPoints <String>] [-SPChannelFilesTab <String>] + [-DefaultFileUploadAppId <String>] [-FileSharingInChatswithExternalUsers <String>] [-Identity] <String> + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +If your organization chooses a third-party for content storage, you can turn off the NativeFileEntryPoints parameter in the Teams Files policy. This parameter is enabled by default, which shows option to attach OneDrive / SharePoint content from Teams chats or channels. When this parameter is disabled, users won't see access points for OneDrive and SharePoint in Teams. Please note that OneDrive app in the left navigation pane in Teams isn't affected by this policy. +Teams administrators can also choose which file service will be used by default when users upload files from their local devices by dragging and dropping them in a chat or channel. OneDrive and SharePoint are the existing defaults, but admins can now change it to a third-party app. +Teams administrators would be able to create a customized teams files policy to match the organization's requirements. + +## EXAMPLES + +### Example 1 +``` +Set-CsTeamsFilesPolicy -Identity "CustomOnlineVoicemailPolicy" -NativeFileEntryPoints Disabled/Enabled +``` + +The command shown in Example 1 changes the teams files policy CustomTeamsFilesPolicy with NativeFileEntryPoints set to Disabled/Enabled. + +### Example 2 +``` +Set-CsTeamsFilesPolicy -DefaultFileUploadAppId GUID_appId +``` + +The command shown in Example 2 changes the DefaultFileUploadAppId to AppId_GUID for tenant level global teams files policy when calling without Identity parameter. + +## PARAMETERS + +### -Identity +A unique identifier specifying the scope, and in some cases the name, of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NativeFileEntryPoints +This parameter is enabled by default, which shows the option to upload content from ODSP to Teams chats or channels. . +Possible values are Enabled or Disabled. +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False + +``` +### -DefaultFileUploadAppId +This can be used by the 3p apps to configure their app, so when the files will be dragged and dropped in compose, it will get uploaded in that 3P app. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileSharingInChatswithExternalUsers + +Indicates if file sharing in chats with external users is enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SPChannelFilesTab + +Indicates whether Iframe channel files tab is enabled, if not, integrated channel files tab will be enabled. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsfilespolicy) + +[Get-CsTeamsFilesPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsfilespolicy) + diff --git a/skype/skype-ps/skype/Set-CsTeamsGuestCallingConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsGuestCallingConfiguration.md similarity index 90% rename from skype/skype-ps/skype/Set-CsTeamsGuestCallingConfiguration.md rename to teams/teams-ps/teams/Set-CsTeamsGuestCallingConfiguration.md index 9f4314a015..f79231986e 100644 --- a/skype/skype-ps/skype/Set-CsTeamsGuestCallingConfiguration.md +++ b/teams/teams-ps/teams/Set-CsTeamsGuestCallingConfiguration.md @@ -1,21 +1,20 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsguestcallingconfiguration -applicable: Skype for Business Online +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsguestcallingconfiguration +applicable: Microsoft Teams title: Set-CsTeamsGuestCallingConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTeamsGuestCallingConfiguration ## SYNOPSIS Allows admins to set values in the GuestCallingConfiguration, which specifies what options guest users have for calling within Teams. - ## SYNTAX ### Identity (Default) @@ -105,7 +104,7 @@ Accept wildcard characters: False ``` ### -Instance -Internal Microsoft use +Internal Microsoft use ```yaml Type: PSObject @@ -151,8 +150,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -160,6 +158,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsGuestMeetingConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsGuestMeetingConfiguration.md new file mode 100644 index 0000000000..1c4ee27ee2 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsGuestMeetingConfiguration.md @@ -0,0 +1,225 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsguestmeetingconfiguration +applicable: Microsoft Teams +title: Set-CsTeamsGuestMeetingConfiguration +schema: 2.0.0 +--- + +# Set-CsTeamsGuestMeetingConfiguration + +## SYNOPSIS + +Designates what meeting features guests using Microsoft Teams will have available. Use this cmdlet to set the configuration. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsTeamsGuestMeetingConfiguration [-Tenant <Guid>] [-AllowIPVideo <Boolean>] + [-ScreenSharingMode <String>] [-AllowMeetNow <Boolean>] [-AllowTranscription <Boolean>] [-LiveCaptionsEnabledType <String>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +### Instance +```powershell +Set-CsTeamsGuestMeetingConfiguration [-Tenant <Guid>] [-AllowIPVideo <Boolean>] + [-ScreenSharingMode <String>] [-AllowMeetNow <Boolean>] [-AllowTranscription <Boolean>] [-LiveCaptionsEnabledType <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +The TeamsGuestMeetingConfiguration designates which meeting features guests leveraging Microsoft Teams will have available. This configuration will apply to all guests utilizing Microsoft Teams. Use the Set-CsTeamsGuestMeetingConfiguration cmdlet to designate what values are set for your organization. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsGuestMeetingConfiguration -Identity Global -AllowMeetNow $false -AllowIPVideo $false +``` + +Disables Guests' usage of MeetNow and Video calling in the organization; all other values of the configuration are left as is. + +## PARAMETERS + +### -AllowIPVideo +Determines whether video is enabled in a user's meetings or calls. Set this to TRUE to allow guests to share their video. Set this to FALSE to prohibit guests from sharing their video + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetNow +Determines whether guests can start ad-hoc meetings. Set this to TRUE to allow guests to start ad-hoc meetings. Set this to FALSE to prohibit guests from starting ad-hoc meetings. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses all non fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The only input allowed is "Global" + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Pipe the existing configuration from a Get- call. + +```yaml +Type: PSObject +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveCaptionsEnabledType +Determines whether real-time captions are available for guests in Teams meetings. Set this to DisabledUserOverride to allow guests to turn on live captions. Set this to Disabled to prohibit. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: DisabledUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScreenSharingMode +Determines the mode in which guests can share a screen in calls or meetings. Set this to SingleApplication to allow the user to share an application at a given point in time. Set this to EntireScreen to allow the user to share anything on their screens. Set this to Disabled to prohibit the user from sharing their screens + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTranscription +Determines whether post-meeting captions and transcriptions are allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsGuestMessagingConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsGuestMessagingConfiguration.md new file mode 100644 index 0000000000..41682046d1 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsGuestMessagingConfiguration.md @@ -0,0 +1,300 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsguestmessagingconfiguration +applicable: Microsoft Teams +title: Set-CsTeamsGuestMessagingConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsTeamsGuestMessagingConfiguration + +## SYNOPSIS +TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [-AllowUserEditMessage <Boolean>] + [-AllowImmersiveReader <Boolean>] [-AllowUserDeleteMessage <Boolean>] [-AllowUserChat <Boolean>] [-AllowGiphy <Boolean>] + [-AllowUserDeleteChat <Boolean>] [-GiphyRatingType <String>] [-AllowMemes <Boolean>] [-AllowStickers <Boolean>] [-UsersCanDeleteBotMessages <Boolean>] [[-Identity] <XdsIdentity>] + [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsGuestMessagingConfiguration [-Tenant <Guid>] [-AllowUserEditMessage <Boolean>] + [-AllowImmersiveReader <Boolean>] [-AllowUserDeleteMessage <Boolean>] [-AllowUserChat <Boolean>] [-AllowGiphy <Boolean>] + [-AllowUserDeleteChat <Boolean>] [-GiphyRatingType <String>] [-AllowMemes <Boolean>] [-AllowStickers <Boolean>] [-UsersCanDeleteBotMessages <Boolean>] [-Instance <PSObject>] [-Force] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +TeamsGuestMessagingConfiguration determines the messaging settings for the guest users. This cmdlet lets you update the guest messaging options you'd like to enable in your organization. + +## EXAMPLES + +### Example 1 +``` +Set-CsTeamsGuestMessagingConfiguration -AllowMemes $False +``` + +The command shown in Example 1 disables memes usage by guests within Teams. + +## PARAMETERS + +### -AllowGiphy +Determines if Giphy images are available. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMemes +Determines if memes are available for use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowStickers +Determines if stickers are available for use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserChat +Determines if a user is allowed to chat. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserDeleteMessage +Determines if a user is allowed to delete their own messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserEditMessage +Determines if a user is allowed to edit their own messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsersCanDeleteBotMessages +Determines whether a user is allowed to delete messages sent by bots. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserDeleteChat +Turn this setting on to allow users to permanently delete their one-on-one chat, group chat, and meeting chat as participants (this deletes the chat only for them, not other users in the chat). Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TRUE +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GiphyRatingType +Determines Giphy content restrictions. Default value is "Moderate", other options are "NoRestriction" and "Strict" + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowImmersiveReader +Determines if immersive reader for viewing messages is enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance + +```yaml +Type: PSObject +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsIPPhonePolicy.md b/teams/teams-ps/teams/Set-CsTeamsIPPhonePolicy.md new file mode 100644 index 0000000000..0f608fbf29 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsIPPhonePolicy.md @@ -0,0 +1,259 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsipphonepolicy +applicable: Microsoft Teams +title: Set-CsTeamsIPPhonePolicy +author: tonywoodruff +ms.author: anwoodru +ms.reviewer: kponnus +manager: sandrao +schema: 2.0.0 +--- + +# Set-CsTeamsIPPhonePolicy + +## SYNOPSIS + +Set-CsTeamsIPPhonePolicy enables you to modify the properties of an existing Teams phone policy settings. + +## SYNTAX + +``` +Set-CsTeamsIPPhonePolicy [[-Identity] <XdsIdentity>] + [-AllowBetterTogether <String>] + [-AllowHomeScreen <String>] + [-AllowHotDesking <Boolean>] + [-Confirm] + [-Description <String>] + [-Force] + [-HotDeskingIdleTimeoutInMinutes <Int>] + [-Instance <Object>] + [-SearchOnCommonAreaPhoneMode <String>] + [-SignInMode <String>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION + +Set-CsTeamsIPPhonePolicy enables you to modify the properties of an existing TeamsIPPhonePolicy. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsIPPhonePolicy -Identity CommonAreaPhone -SignInMode CommonAreaPhoneSignin +``` +This example shows the SignInMode "CommonAreaPhoneSignIn" being set against the policy named "CommonAreaPhone". + +## PARAMETERS + +### -AllowBetterTogether +Determines whether Better Together mode is enabled, phones can lock and unlock in an integrated fashion when connected to their Windows PC running a 64-bit Teams desktop client. +Possible values this parameter can take: + +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowHomeScreen +Determines whether the Home Screen feature of the Teams IP Phones is enabled. +Possible values this parameter can take: + +- Enabled +- EnabledUserOverride +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: EnabledUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowHotDesking +Determines if the hot desking feature is enabled or not. Set this to TRUE to enable. Set this to FALSE to disable hot desking mode. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Free form text that can be used by administrators as desired. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HotDeskingIdleTimeoutInMinutes +Determines the idle timeout value in minutes for the signed in user account. When the timeout is reached, the account is logged out. + +```yaml +Type: Int +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The identity of the policy. To specify the global policy for the organization, use "global". To specify any other policy provide the name of that policy. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SearchOnCommonAreaPhoneMode +Determines whether a user can look up contacts from the tenant's global address book when the phone is signed into the Common Area Phone Mode. Set this to ENABLED to enable the feature. Set this to DISABLED to disable the feature. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SignInMode +Determines the sign in mode for the device when signing in to Teams. +Possible Values: +- 'UserSignIn: Enables the individual user's Teams experience on the phone' +- 'CommonAreaPhoneSignIn: Enables a Common Area Phone experience on the phone' +- 'MeetingSignIn: Enables the meeting/conference room experience on the phone' + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Internal Microsoft use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsMediaConnectivityPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMediaConnectivityPolicy.md new file mode 100644 index 0000000000..7bb81a371f --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsMediaConnectivityPolicy.md @@ -0,0 +1,91 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Set-CsTeamsMediaConnectivityPolicy +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsTeamsMediaConnectivityPolicy +schema: 2.0.0 +author: lirunping-MSFT +ms.author: runli +--- + +# Set-CsTeamsMediaConnectivityPolicy + +## SYNOPSIS + +This cmdlet Set Teams media connectivity policy value for current tenant. + +## SYNTAX + +``` +Set-CsTeamsMediaConnectivityPolicy -Identity <String> -DirectConnection <Boolean> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet Set Teams media connectivity policy DirectConnection value for current tenant. The value can be "Enabled" or "Disabled" + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsMediaConnectivityPolicy -Identity Test -DirectConnection Disabled + +Identity DirectConnection +-------- ---------------- +Global Enabled +Tag:Test Disabled +``` + +Set Teams media connectivity policy "DirectConnection" value to "Disabled" for identity "Test". + +## PARAMETERS + +### -Identity +Identity of the Teams media connectivity policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DirectConnection +Policy value of the Teams media connectivity DirectConnection policy. + +```yaml +Type: Boolean +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmediaconnectivitypolicy) + +[Remove-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmediaconnectivitypolicy) + +[Get-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmediaconnectivitypolicy) + +[Grant-CsTeamsMediaConnectivityPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmediaconnectivitypolicy) \ No newline at end of file diff --git a/teams/teams-ps/teams/Set-CsTeamsMeetingBrandingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMeetingBrandingPolicy.md new file mode 100644 index 0000000000..033a024718 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsMeetingBrandingPolicy.md @@ -0,0 +1,208 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbrandingpolicy +schema: 2.0.0 +title: Set-CsTeamsMeetingBrandingPolicy +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: stanlythomas +applicable: Microsoft Teams +--- + +# Set-CsTeamsMeetingBrandingPolicy + +## SYNOPSIS +The **CsTeamsMeetingBrandingPolicy** cmdlet enables administrators to control the appearance in meetings by defining custom backgrounds, logos, and colors. + +## SYNTAX + +``` +Set-CsTeamsMeetingBrandingPolicy + [-MeetingBackgroundImages <PSListModifier>] + [-MeetingBrandingThemes <PSListModifier>] + [-DefaultTheme <String>] [-EnableMeetingOptionsThemeOverride <Boolean>] + [-EnableMeetingBackgroundImages <Boolean>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +The `Set-CsTeamsMeetingBrandingPolicy` cmdlet allows administrators to update existing meeting branding policies. +However, it cannot be used to upload the images. If you want to upload the images, you should use Teams Admin Center. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Get-CsTeamsMeetingBrandingPolicy +PS C:\> $brandingPolicy = Get-CsTeamsMeetingBrandingPolicy -Identity "demo branding" +PS C:\> $brandingPolicy.MeetingBrandingThemes[0].BrandAccentColor = "#FF0000" +PS C:\> Set-CsTeamsMeetingBrandingPolicy -Identity "demo branding" -MeetingBrandingThemes $brandingPolicy.MeetingBrandingThemes +``` + +In this example, the commands will change the brand accent color of the theme inside the `demo branding` meeting branding policy to `#FF0000` + +## PARAMETERS + +### -DefaultTheme +*This parameter is reserved for Microsoft internal use only.* +Identity of default meeting theme. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMeetingBackgroundImages +Enables custom meeting backgrounds. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableMeetingOptionsThemeOverride +Allows organizers to control meeting themes. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Identity of meeting branding policy that will be updated. To refer to the global policy, use this syntax: `-Identity global`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingBackgroundImages +*This parameter is reserved for Microsoft internal use only.* +List of meeting background images. +It is not possible to add or remove background images using cmdlets. You should use Teams Admin Center for that purpose. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingBrandingThemes +List of meeting branding themes. You can alter the list returned by the `Get-CsTeamsMeetingBrandingPolicy` cmdlet and pass it to this parameter. +It is not possible to add or remove meeting branding themes using cmdlets. You should use Teams Admin Center for that purpose. + +```yaml +Type: PSListModifier +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +Available in Teams PowerShell Module 4.9.3 and later. + +## RELATED LINKS + +[Get-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingbrandingpolicy) + +[Grant-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingbrandingpolicy) + +[New-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingbrandingpolicy) + +[Remove-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingbrandingpolicy) + +[Set-CsTeamsMeetingBrandingPolicy](https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbrandingpolicy) diff --git a/skype/skype-ps/skype/Set-CsTeamsMeetingBroadcastConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastConfiguration.md similarity index 87% rename from skype/skype-ps/skype/Set-CsTeamsMeetingBroadcastConfiguration.md rename to teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastConfiguration.md index 8818a75e6c..a369ef43c1 100644 --- a/skype/skype-ps/skype/Set-CsTeamsMeetingBroadcastConfiguration.md +++ b/teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastConfiguration.md @@ -1,16 +1,15 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsmeetingbroadcastconfiguration -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbroadcastconfiguration +applicable: Microsoft Teams title: Set-CsTeamsMeetingBroadcastConfiguration schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- - # Set-CsTeamsMeetingBroadcastConfiguration ## SYNOPSIS @@ -46,7 +45,7 @@ Tenant level configuration for broadcast events in Teams ## PARAMETERS ### -AllowSdnProviderForBroadcastMeeting -If set to $true, Teams meeting broadcast streams are enabled to take advantage of the network and bandwidth management capabilities of your Software Defined Network (SDN) provider. +If set to $true, Teams meeting broadcast streams are enabled to take advantage of the network and bandwidth management capabilities of your Software Defined Network (SDN) provider. ```yaml Type: Boolean @@ -121,7 +120,7 @@ Accept wildcard characters: False ``` ### -SdnApiTemplateUrl -Specifies the Software Defined Network (SDN) provider's HTTP API endpoint. This information is provided to you by the SDN provider. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. +Specifies the Software Defined Network (SDN) provider's HTTP API endpoint. This information is provided to you by the SDN provider. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. ```yaml Type: String @@ -136,7 +135,7 @@ Accept wildcard characters: False ``` ### -SdnApiToken -Specifies the Software Defined Network (SDN) provider's authentication token which is required to use their SDN license. This is required by some SDN providers who will give you the required token. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. +Specifies the Software Defined Network (SDN) provider's authentication token which is required to use their SDN license. This is required by some SDN providers who will give you the required token. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. ```yaml Type: String @@ -151,7 +150,7 @@ Accept wildcard characters: False ``` ### -SdnLicenseId -Specifies the Software Defined Network (SDN) license identifier. This is required and provided by some SDN providers. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. +Specifies the Software Defined Network (SDN) license identifier. This is required and provided by some SDN providers. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. ```yaml Type: String @@ -166,7 +165,22 @@ Accept wildcard characters: False ``` ### -SdnProviderName -Specifies the Software Defined Network (SDN) provider's name. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. +Specifies the Software Defined Network (SDN) provider's name. This parameter is only required if AllowSdnProviderForBroadcastMeeting is set to $true. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SdnRuntimeConfiguration +Specifies connection parameters used to connect with a 3rd party eCDN provider. These parameters should be obtained from the SDN provider to be used. ```yaml Type: String @@ -181,7 +195,7 @@ Accept wildcard characters: False ``` ### -SupportURL -Specifies a URL where broadcast event attendees can find support information or FAQs specific to that event. The URL will be displayed to the attendees during the broadcast. +Specifies a URL where broadcast event attendees can find support information or FAQs specific to that event. The URL will be displayed to the attendees during the broadcast. ```yaml Type: String @@ -227,8 +241,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -236,6 +249,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsMeetingBroadcastPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastPolicy.md similarity index 75% rename from skype/skype-ps/skype/Set-CsTeamsMeetingBroadcastPolicy.md rename to teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastPolicy.md index 4be4113701..5fda5b675c 100644 --- a/skype/skype-ps/skype/Set-CsTeamsMeetingBroadcastPolicy.md +++ b/teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastPolicy.md @@ -1,28 +1,26 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsmeetingbroadcastpolicy -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingbroadcastpolicy +applicable: Microsoft Teams title: Set-CsTeamsMeetingBroadcastPolicy schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTeamsMeetingBroadcastPolicy ## SYNOPSIS -Set-CsTeamsMeetingBroadcastPolicy \[\[-Identity\] \<XdsIdentity\>\] \[-Tenant \<guid\>\] \[-Description \<string\>\] \[-AllowBroadcastScheduling \<bool\>\] \[-AllowBroadcastTranscription \<bool\>\] \[-BroadcastAttendeeVisibilityMode \<string\>\] \[-BroadcastRecordingMode \<string\>\] \[-Force\] \[-WhatIf\] \[-Confirm\] \[\<CommonParameters\>\] - -Set-CsTeamsMeetingBroadcastPolicy \[-Tenant \<guid\>\] \[-Description \<string\>\] \[-AllowBroadcastScheduling \<bool\>\] \[-AllowBroadcastTranscription \<bool\>\] \[-BroadcastAttendeeVisibilityMode \<string\>\] \[-BroadcastRecordingMode \<string\>\] \[-Instance \<psobject\>\] \[-Force\] \[-WhatIf\] \[-Confirm\] \[\<CommonParameters\>\] +User-level policy for tenant admin to configure meeting broadcast behavior for the broadcast event organizer. ## SYNTAX ### Identity (Default) -``` +```powershell Set-CsTeamsMeetingBroadcastPolicy [-Tenant <Guid>] [-Description <String>] [-AllowBroadcastScheduling <Boolean>] [-AllowBroadcastTranscription <Boolean>] [-BroadcastAttendeeVisibilityMode <String>] [-BroadcastRecordingMode <String>] [[-Identity] <XdsIdentity>] @@ -31,7 +29,7 @@ Set-CsTeamsMeetingBroadcastPolicy [-Tenant <Guid>] [-Description <String>] ### Instance -``` +```powershell Set-CsTeamsMeetingBroadcastPolicy [-Tenant <Guid>] [-Description <String>] [-AllowBroadcastScheduling <Boolean>] [-AllowBroadcastTranscription <Boolean>] [-BroadcastAttendeeVisibilityMode <String>] [-BroadcastRecordingMode <String>] [-Instance <PSObject>] [-Force] @@ -39,15 +37,15 @@ Set-CsTeamsMeetingBroadcastPolicy [-Tenant <Guid>] [-Description <String>] ``` ## DESCRIPTION -User-level policy for tenant admin to configure meeting broadcast behavior for the broadcast event organizer. Use this cmdlet to update an existing policy. +User-level policy for tenant admin to configure meeting broadcast behavior for the broadcast event organizer. Use this cmdlet to update an existing policy. ## EXAMPLES ### Example 1 ```powershell -PS C:\> Set-CsTeamsMeetingBroadcastPolicy -Identity Global -AllowBroadcastScheduling $false +PS C:\> Set-CsTeamsMeetingBroadcastPolicy -Identity Global -AllowBroadcastScheduling $false ``` Sets the value of the Default (Global) Broadcast Policy in the organization to disable broadcast scheduling, and leaves all other parameters the same. @@ -55,7 +53,8 @@ Sets the value of the Default (Global) Broadcast Policy in the organization to d ## PARAMETERS ### -AllowBroadcastScheduling -Specifies whether this user can create broadcast events in Teams. This settng impacts broadcasts that use both self-service and external encoder production methods. + +Specifies whether this user can create broadcast events in Teams. This setting impacts broadcasts that use both self-service and external encoder production methods. ```yaml Type: Boolean @@ -70,7 +69,11 @@ Accept wildcard characters: False ``` ### -AllowBroadcastTranscription -Specifies whether real-time transcription and translation can be enabled in the broadcast event. Note: this setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. + +Specifies whether real-time transcription and translation can be enabled in the broadcast event. + +> [!NOTE] +> This setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. ```yaml Type: Boolean @@ -85,7 +88,18 @@ Accept wildcard characters: False ``` ### -BroadcastAttendeeVisibilityMode -Specifies the attendee visibility mode of the broadcast events created by this user. This setting controls who can watch the broadcast event - e.g. anyone can watch this event including anonymous users or only authenticated users in my company can watch the event. Note: this setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. + +Specifies the attendee visibility mode of the broadcast events created by this user. This setting controls who can watch the broadcast event - e.g. anyone can watch this event including anonymous users or only authenticated users in my company can watch the event. + +> [!NOTE] +> This setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. + +Possible values: +- Everyone +- EveryoneInCompany +- InvitedUsersInCompany +- EveryoneInCompanyAndExternal +- InvitedUsersInCompanyAndExternal ```yaml Type: String @@ -100,7 +114,16 @@ Accept wildcard characters: False ``` ### -BroadcastRecordingMode -Specifies whether broadcast events created by this user are always recorded, never recorded or user can choose whether to record or not. Note: this setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. + +Specifies whether broadcast events created by this user are always recorded (AlwaysEnabled), never recorded (AlwaysDisabled) or user can choose whether to record or not (UserOverride). + +> [!NOTE] +> This setting is applicable to broadcast events that use Teams Meeting production only and does not apply when external encoder is used as production method. + +Possible values: +- AlwaysEnabled +- AlwaysDisabled +- UserOverride ```yaml Type: String @@ -115,6 +138,7 @@ Accept wildcard characters: False ``` ### -Confirm + Prompts you for confirmation before running the cmdlet. ```yaml @@ -130,6 +154,7 @@ Accept wildcard characters: False ``` ### -Description + Enables administrators to provide additional text about the conferencing policy. For example, the Description might indicate the users the policy should be assigned to. ```yaml @@ -145,6 +170,7 @@ Accept wildcard characters: False ``` ### -Force + Suppresses the display of any non-fatal error message that might occur when running the command. ```yaml @@ -228,8 +254,7 @@ Accept wildcard characters: False ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/skype/skype-ps/skype/Set-CsTeamsMeetingConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsMeetingConfiguration.md similarity index 79% rename from skype/skype-ps/skype/Set-CsTeamsMeetingConfiguration.md rename to teams/teams-ps/teams/Set-CsTeamsMeetingConfiguration.md index cfee5c7b74..10cd0d63f9 100644 --- a/skype/skype-ps/skype/Set-CsTeamsMeetingConfiguration.md +++ b/teams/teams-ps/teams/Set-CsTeamsMeetingConfiguration.md @@ -1,14 +1,10 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -Module Name: Skype for Business Online -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsmeetingconfiguration -applicable: Skype for Business Online +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingconfiguration +applicable: Microsoft Teams title: Set-CsTeamsMeetingConfiguration schema: 2.0.0 -manager: bulenteg -author: tomkau -ms.author: tomkau -ms.reviewer: --- # Set-CsTeamsMeetingConfiguration @@ -21,23 +17,23 @@ The CsTeamsMeetingConfiguration cmdlets enable administrators to control the mee ### Identity (Default) -``` +```powershell Set-CsTeamsMeetingConfiguration [-Tenant <Guid>] [-LogoURL <String>] [-LegalURL <String>] [-HelpURL <String>] [-CustomFooterText <String>] [-DisableAnonymousJoin <Boolean>] [-EnableQoS <Boolean>] [-ClientAudioPort <UInt32>] [-ClientAudioPortRange <UInt32>] [-ClientVideoPort <UInt32>] [-ClientVideoPortRange <UInt32>] [-ClientAppSharingPort <UInt32>] [-ClientAppSharingPortRange <UInt32>] - [-ClientMediaPortRangeEnabled <Boolean>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] + [-ClientMediaPortRangeEnabled <Boolean>] [-DisableAppInteractionForAnonymousUsers <Boolean>] [[-Identity] <XdsIdentity>] [-FeedbackSurveyForAnonymousUsers <String>] [-LimitPresenterRolePermissions <Boolean>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ### Instance -``` +```powershell Set-CsTeamsMeetingConfiguration [-Tenant <Guid>] [-LogoURL <String>] [-LegalURL <String>] [-HelpURL <String>] [-CustomFooterText <String>] [-DisableAnonymousJoin <Boolean>] [-EnableQoS <Boolean>] [-ClientAudioPort <UInt32>] [-ClientAudioPortRange <UInt32>] [-ClientVideoPort <UInt32>] [-ClientVideoPortRange <UInt32>] [-ClientAppSharingPort <UInt32>] [-ClientAppSharingPortRange <UInt32>] - [-ClientMediaPortRangeEnabled <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] + [-ClientMediaPortRangeEnabled <Boolean>] [-DisableAppInteractionForAnonymousUsers <Boolean>] [-FeedbackSurveyForAnonymousUsers <String>] [-LimitPresenterRolePermissions <Boolean>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] ``` @@ -335,6 +331,25 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DisableAppInteractionForAnonymousUsers +Determines if anonymous users can interact with apps in meetings. Set to TRUE to disable App interaction. +Possible values: + +- True +- False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Tenant Internal Microsoft use @@ -351,6 +366,41 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -FeedbackSurveyForAnonymousUsers +Determines if anonymous participants receive surveys to provide feedback about their meeting experience. Set to Disabled to disable anonymous meeting participants to receive surveys. Set to Enabled to allow anonymous meeting participants to receive surveys. +Possible values: + +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LimitPresenterRolePermissions +When set to True, users within the Tenant will have their presenter role capabilities limited. +When set to False, the presenter role capabilities will not be impacted and will remain as is. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf Shows what would happen if the cmdlet runs. The cmdlet is not run. @@ -369,8 +419,7 @@ Accept wildcard characters: False ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Set-CsTeamsMeetingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMeetingPolicy.md new file mode 100644 index 0000000000..5adc506782 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsMeetingPolicy.md @@ -0,0 +1,2031 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmeetingpolicy +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Set-CsTeamsMeetingPolicy +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: alejandramu +ms.date: 2/26/2025 +--- + +# Set-CsTeamsMeetingPolicy + +## SYNOPSIS +The `CsTeamsMeetingPolicy` cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users. + +## SYNTAX + +### Identity (Default) + +```powershell +Set-CsTeamsMeetingPolicy [[-Identity] <XdsIdentity>] + [-AIInterpreter <string>] + [-AllowAnnotations <Boolean>] + [-AllowAnonymousUsersToDialOut <Boolean>] + [-AllowAnonymousUsersToJoinMeeting <Boolean>] + [-AllowAnonymousUsersToStartMeeting <Boolean>] + [-AllowAvatarsInGallery <Boolean>] + [-AllowBreakoutRooms <Boolean>] + [-AllowCarbonSummary <Boolean>] + [-AllowCartCaptionsScheduling <String>] + [-AllowChannelMeetingScheduling <Boolean>] + [-AllowCloudRecording <Boolean>] + [-AllowDocumentCollaboration <String>] + [-AllowEngagementReport <String>] + [-AllowExternalNonTrustedMeetingChat <Boolean>] + [-AllowExternalParticipantGiveRequestControl <Boolean>] + [-AllowImmersiveView <Boolean>] + [-AllowIPAudio <Boolean>] + [-AllowIPVideo <Boolean>] + [-AllowLocalRecording <Boolean>] + [-AllowMeetingCoach <Boolean>] + [-AllowMeetNow <Boolean>] + [-AllowMeetingReactions <Boolean>] + [-AllowMeetingRegistration <Boolean>] + [-AllowNDIStreaming <Boolean>] + [-AllowNetworkConfigurationSettingsLookup <Boolean>] + [-AllowOrganizersToOverrideLobbySettings <Boolean>] + [-AllowOutlookAddIn <Boolean>] + [-AllowPSTNUsersToBypassLobby <Boolean>] + [-AllowParticipantGiveRequestControl <Boolean>] + [-AllowPowerPointSharing <Boolean>] + [-AllowPrivateMeetNow <Boolean>] + [-AllowPrivateMeetingScheduling <Boolean>] + [-AllowRecordingStorageOutsideRegion <Boolean>] + [-AllowScreenContentDigitization <Boolean>] + [-AllowSharedNotes <Boolean>] + [-AllowTasksFromTranscript <String>] + [-AllowTrackingInReport <Boolean>] + [-AllowTranscription <Boolean>] + [-AllowedUsersForMeetingContext <String>] + [-AllowUserToJoinExternalMeeting <String>] + [-AllowWatermarkCustomizationForCameraVideo <Boolean>] + [-AllowWatermarkCustomizationForScreenSharing <Boolean>] + [-AllowWatermarkForCameraVideo <Boolean>] + [-AllowWatermarkForScreenSharing <Boolean>] + [-AllowWhiteboard <Boolean>] + [-AllowedStreamingMediaInput <String>] + [-AnonymousUserAuthenticationMethod <String>] + [-AttendeeIdentityMasking <String>] + [-AudibleRecordingNotification <String>] + [-AutoAdmittedUsers <String>] + [-AutoRecording <String>] + [-AutomaticallyStartCopilot <String>] + [-BlockedAnonymousJoinClientTypes <List>] + [-CaptchaVerificationForMeetingJoin <String>] + [-ChannelRecordingDownload <String>] + [-Confirm] + [-ConnectToMeetingControls <String>] + [-ContentSharingInExternalMeetings <String>] + [-Copilot <String>] + [-CopyRestriction <Boolean>] + [-Description <String>] + [-DesignatedPresenterRoleMode <String>] + [-DetectSensitiveContentDuringScreenSharing <Boolean>] + [-EnrollUserOverride <String>] + [-ExplicitRecordingConsent <String>] + [-ExternalMeetingJoin <String>] + [-Force] + [-InfoShownInReportMode <String>] + [-IPAudioMode <String>] + [-IPVideoMode <String>] + [-LiveCaptionsEnabledType <String>] + [-LiveInterpretationEnabledType <String>] + [-LiveStreamingMode <String>] + [-LobbyChat <String> ] + [-MediaBitRateKb <UInt32>] + [-MeetingChatEnabledType <String>] + [-MeetingInviteLanguages <String>] + [-NewMeetingRecordingExpirationDays <Int32>] + [-NoiseSuppressionForDialInParticipants <String>] + [-ParticipantNameChange <String>] + [-PreferredMeetingProviderForIslandsMode <String>] + [-QnAEngagementMode <String>] + [-RecordingStorageMode <String>] + [-RoomAttributeUserOverride <String>] + [-RoomPeopleNameUserOverride <String>] + [-ScreenSharingMode <String>] + [-SmsNotifications <String>] + [-SpeakerAttributionMode <String>] + [-StreamingAttendeeMode <String>] + [-TeamsCameraFarEndPTZMode <String>] + [-Tenant <Guid>] + [-UsersCanAdmitFromLobby <String>] + [-VideoFiltersMode <String>] + [-VoiceIsolation <String>] + [-VoiceSimulationInInterpreter <string>] + [-WatermarkForAnonymousUsers <String>] + [-WatermarkForCameraVideoOpacity <Int32>] + [-WatermarkForCameraVideoPattern <String>] + [-WatermarkForScreenSharingOpacity <Int32>] + [-WatermarkForScreenSharingPattern <String>] + [-AllowedUsersForMeetingDetails <String>] + [-RealTimeText <String>] + [-WhatIf] + [-WhoCanRegister <String>] + [<CommonParameters>] +``` + +## DESCRIPTION + +The `CsTeamsMeetingPolicy` cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users. + +The Set-CsTeamsMeetingPolicy cmdlet allows administrators to update existing meeting policies that can be assigned to particular users to control Teams features related to meetings. + +## EXAMPLES + +### EXAMPLE 1 +```powershell +Set-CsTeamsMeetingPolicy -Identity SalesMeetingPolicy -AllowTranscription $True +``` + +The command shown in Example 1 uses the Set-CsTeamsMeetingPolicy cmdlet to update an existing meeting policy with the Identity SalesMeetingPolicy. +This policy will use all the existing values except one: AllowTranscription; in this example, meetings for users with this policy can include real time or post meeting captions and transcriptions. + +### EXAMPLE 2 + +```powershell +Set-CsTeamsMeetingPolicy -Identity HrMeetingPolicy -AutoAdmittedUsers "Everyone" -AllowMeetNow $False +``` + +In Example 2, the Set-CsTeamsMeetingPolicy cmdlet is used to update a meeting policy with the Identity HrMeetingPolicy. +In this example two different property values are configured: AutoAdmittedUsers is set to Everyone and AllowMeetNow is set to False. +All other policy properties will use the existing values. + +### EXAMPLE 3 + +```powershell +Set-CsTeamsMeetingPolicy -Identity NonEVNetworkRoamingPolicy -AllowNetworkConfigurationSettingsLookup $True +``` + +In Example 3, the Set-CsTeamsMeetingPolicy cmdlet is used to update an existing meeting policy with the Identity NonEVNetworkRoamingPolicy. +This policy will use all the existing values except one: AllowNetworkConfigurationSettingsLookup; in this example, we will fetch network roaming policy for the non-EV user with NonEVNetworkRoamingPolicy based on his current network location. + +## PARAMETERS + +### -Identity +Specify the name of the policy being created. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AIInterpreter +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the AI Interpreter related features + +Possible values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnnotations + +This setting will allow admins to choose which users will be able to use the Annotation feature. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnonymousUsersToDialOut + +Determines whether anonymous users are allowed to dial out to a PSTN number. Set this to TRUE to allow anonymous users to dial out. Set this to FALSE to prohibit anonymous users from dialing out. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnonymousUsersToJoinMeeting +> [!NOTE] +> The experience for users is dependent on both the value of -DisableAnonymousJoin (the old tenant-wide setting) and -AllowAnonymousUsersToJoinMeeting (the new per-organizer policy). Please check <https://learn.microsoft.com/microsoftteams/meeting-settings-in-teams> for details. + +Determines whether anonymous users can join the meetings that impacted users organize. Set this to TRUE to allow anonymous users to join a meeting. Set this to FALSE to prohibit them from joining a meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAnonymousUsersToStartMeeting +Determines whether anonymous users can initiate a meeting. Set this to TRUE to allow anonymous users to initiate a meeting. Set this to FALSE to prohibit them from initiating a meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -AllowAvatarsInGallery + +If admins disable avatars in 2D meetings, then users cannot represent themselves as avatars in the Gallery view. This does not disable avatars in Immersive view. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCarbonSummary + +This setting will enable Tenant Admins to enable/disable the sharing of location data necessary to provide the end of meeting carbon summary screen for either the entire tenant or for a particular user. +If set to True the meeting organizer will share their location to the client of the participant to enable the calculation of distance and the resulting carbon. + +> [!NOTE] +> Location data will not be visible to the organizer or participants in this case and only carbon avoided will be shown. +If set to False then organizer location data will not be shown and no carbon summary screen will be displayed to the participants. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCartCaptionsScheduling +Determines whether a user can add a URL for captions from a Communications Access Real-Time Translation (CART) captioner for providing real time captions in meetings. +Possible values are: + +- **EnabledUserOverride**, CART captions is available by default but a user can disable. +- **DisabledUserOverride**, if you would like users to be able to use CART captions in meetings but by default it is disabled. +- **Disabled**, if you'd like to not allow CART captions in meeting. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: DisabledUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowBreakoutRooms +Set to true to enable Breakout Rooms, set to false to disable the Breakout Rooms functionality. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowChannelMeetingScheduling +Determines whether a user can schedule channel meetings. Set this to TRUE to allow a user to schedule channel meetings. Set this to FALSE to prohibit the user from scheduling channel meetings. + +> [!NOTE] +> This only restricts from scheduling and not from joining a meeting scheduled by another user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCloudRecording +Determines whether cloud recording is allowed in a user's meetings. Set this to TRUE to allow the user to be able to record meetings. Set this to FALSE to prohibit the user from recording meetings. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowDocumentCollaboration + +This setting will allow admins to choose which users will be able to use the Document Collaboration feature. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowEngagementReport +Determines whether meeting organizers are allowed to download the attendee engagement report. Possible values are: + +- Enabled: allow the meeting organizer to download the report. +- Disabled: disable attendee report generation and prohibit meeting organizer from downloading it. +- ForceEnabled: enable attendee report generation and prohibit meeting organizer from disabling it. + +If set to Enabled or ForceEnabled, only meeting organizers and co-organizers will get a link to download the report in Teams. Regular attendees will have no access to it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowExternalNonTrustedMeetingChat + +This field controls whether a user is allowed to chat in external meetings with users from non trusted organizations. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowExternalParticipantGiveRequestControl +Determines whether external participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit an external user from giving or requesting control in a meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowImmersiveView + +If admins have disabled avatars, this does not disable using avatars in Immersive view on Teams desktop or web. Additionally, it does not prevent users from joining the Teams meeting on VR headsets. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowIPAudio +Determines whether audio is enabled in a user's meetings or calls. Set this to TRUE to allow the user to share their audio. Set this to FALSE to prohibit the user from sharing their audio. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowIPVideo +Determines whether video is enabled in a user's meetings or calls. Set this to TRUE to allow the user to share their video. Set this to FALSE to prohibit the user from sharing their video. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowLocalRecording +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingCoach +This setting will allow admins to allow users the option of turning on Meeting Coach during meetings, which provides users with private personalized feedback on their communication and inclusivity. + If set to True, then users will see and be able to click the option for turning on Meeting Coach during calls. + If set to False, then users will not have the option to turn on Meeting Coach during calls. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingReactions +Set to false to disable Meeting Reactions. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingRegistration +Controls if a user can create a webinar meeting. The default value is True. + +Possible values: + +- True +- False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetNow +Determines whether a user can start ad-hoc meetings. Set this to TRUE to allow a user to start ad-hoc meetings. Set this to FALSE to prohibit the user from starting ad-hoc meetings. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowNetworkConfigurationSettingsLookup +Determines whether network configuration setting lookup can be made for users who are not Enterprise Voice enabled. It is used to enable Network Roaming policy. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowNDIStreaming +This parameter enables the use of NDI technology to capture and deliver broadcast-quality audio and video over your network. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOrganizersToOverrideLobbySettings +This parameter has been deprecated and currently has no effect. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOutlookAddIn +Determines whether a user can schedule Teams Meetings in Outlook desktop client. Set this to TRUE to allow the user to be able to schedule Teams meetings in Outlook client. Set this to FALSE to prohibit a user from scheduling Teams meeting in Outlook client. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowParticipantGiveRequestControl +Determines whether participants can request or give control of screen sharing during meetings scheduled by this user. Set this to TRUE to allow the user to be able to give or request control. Set this to FALSE to prohibit the user from giving, requesting control in a meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPowerPointSharing +Determines whether Powerpoint sharing is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateMeetNow +This setting controls whether a user can start an ad hoc private meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivateMeetingScheduling +Determines whether a user can schedule private meetings. Set this to TRUE to allow a user to schedule private meetings. Set this to FALSE to prohibit the user from scheduling private meetings. + +> [!NOTE] +> This only restricts from scheduling and not from joining a meeting scheduled by another user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPSTNUsersToBypassLobby +Determines whether a PSTN user joining the meeting is allowed or not to bypass the lobby. If you set this parameter to **True**, PSTN users are allowed to bypass the lobby as long as an authenticated user is joined to the meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowRecordingStorageOutsideRegion +Allows storing recordings outside of the region. All meeting recordings will be permanently stored in another region, and can't be migrated. This does not apply to recordings saved in OneDrive or SharePoint. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowScreenContentDigitization +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSharedNotes +Determines whether users are allowed to take shared Meeting notes. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTasksFromTranscript + +This policy setting allows for the extraction of AI-Assisted Action Items/Tasks from the Meeting Transcript. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTrackingInReport +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTranscription +Determines whether post-meeting captions and transcriptions are allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedUsersForMeetingContext + +This policy controls which users should have the ability to see the meeting info details on the join screen. 'None' option should disable the feature completely. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserToJoinExternalMeeting +Currently, this parameter has no effect. + +Possible values are: + +- Enabled +- FederatedOnly +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedUsersForMeetingContext +This policy controls which users should have the ability to see the meeting info details on the join screen. 'None' option should disable the feature completely. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowExternalNonTrustedMeetingChat +This field controls whether a user is allowed to chat in external meetings with users from non-trusted organizations. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWatermarkForScreenSharing +This setting allows scheduling meetings with watermarking for screen sharing enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWatermarkForCameraVideo +This setting allows scheduling meetings with watermarking for video enabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowWhiteboard +Determines whether whiteboard is allowed in a user's meetings. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedStreamingMediaInput +Enables the use of RTMP-In in Teams meetings. + +Possible values are: + +- \<blank\> +- RTMP + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnonymousUserAuthenticationMethod +Determines how anonymous users will be authenticated when joining a meeting. +Possible values are: + +- **OneTimePasscode**, if you would like anonymous users to be sent a one time passcode to their email when joining a meeting +- **None**, if you would like to disable authentication for anonymous users joining a meeting + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: OneTimePasscode +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AttendeeIdentityMasking + +This setting will allow admins to enable or disable Masked Attendee mode in Meetings. +Masked Attendee meetings will hide attendees' identifying information (e.g., name, contact information, profile photo). + +Possible Values: Enabled: Hides attendees' identifying information in meetings. Disabled: Does not allow attendees' to hide identifying information in meetings + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AudibleRecordingNotification + +The setting controls whether recording notification is played to all attendees or just PSTN users. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoRecording + +This setting allows admins to control the visibility of the auto recording feature in the organizer's **Meeting options**. If the you enable this setting, the **Record and transcribe automatically** setting appears in **Meeting options** with the default value set to **Off** (except for webinars and townhalls). Organizers need to manually toggle this setting to **On** to for their meetings to be automatically recorded. If you disable this setting, **Record and transcribe automatically** is hidden, preventing organizers from setting any meetings to be auto-recorded. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutoAdmittedUsers +Determines what types of participants will automatically be added to meetings organized by this user. +Possible values are: + +- **EveryoneInCompany**, if you would like meetings to place every external user in the lobby but allow all users in the company to join the meeting immediately. +- **EveryoneInSameAndFederatedCompany**, if you would like meetings to allow federated users to join like your company's users, but place all other external users in a lobby. +- **Everyone**, if you'd like to admit anonymous users by default. +- **OrganizerOnly**, if you would like that only meeting organizers can bypass the lobby. +- **EveryoneInCompanyExcludingGuests**, if you would like meetings to place every external and guest users in the lobby but allow all other users in the company to join the meeting immediately. +- **InvitedUsers**, if you would like that only meeting organizers and invited users can bypass the lobby. + +This setting also applies to participants joining via a PSTN device (i.e. a traditional phone). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AutomaticallyStartCopilot +> [!NOTE] +> This feature has not been fully released yet, so the setting will have no effect. + +This setting gives admins the ability to auto-start Copilot. + +Possible values are: + +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedAnonymousJoinClientTypes +A user can join a Teams meeting anonymously using a [Teams client](https://support.microsoft.com/office/join-a-meeting-without-a-teams-account-c6efc38f-4e03-4e79-b28f-e65a4c039508) or using a [custom application built using Azure Communication Services](https://learn.microsoft.com/azure/communication-services/concepts/join-teams-meeting). When anonymous meeting join is enabled, both types of clients may be used by default. This optional parameter can be used to block one of the client types that can be used. + +The allowed values are ACS (to block the use of Azure Communication Services clients) or Teams (to block the use of Teams clients). Both can also be specified, separated by a comma, but this is equivalent to disabling anonymous join completely. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Empty List +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CaptchaVerificationForMeetingJoin +Require a verification check for meeting join. + +Possible values: +- **NotRequired**, CAPTCHA not required to join the meeting +- **AnonymousUsersAndUntrustedOrganizations**, Anonymous users and people from untrusted organizations must complete a CAPTCHA challenge to join the meeting. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelRecordingDownload +Controls how channel meeting recordings are saved, permissioned, and who can download them. + +Possible values: + +- Allow - Saves channel meeting recordings to a "Recordings" folder in the channel. The permissions on the recording files will be based on the Channel SharePoint permissions. This is the same as any other file uploaded for the channel. +- Block - Saves channel meeting recordings to a "Recordings\View only" folder in the channel. Channel owners will have full rights to the recordings in this folder, but channel members will have read access without the ability to download. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Allow +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectToMeetingControls +Allows external connections of thirdparty apps to Microsoft Teams + +Possible values are: +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentSharingInExternalMeetings +This policy allows admins to determine whether the user can share content in meetings organized by external organizations. The user should have a Teams Premium license to be protected under this policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Copilot +This setting allows the admin to choose whether Copilot will be enabled with a persisted transcript or a non-persisted transcript. + +Possible values are: + +- Enabled +- EnabledWithTranscript + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CopyRestriction +This parameter enables a setting that controls a meeting option which allows users to disable right-click or Ctrl+C to copy, Copy link, Forward message, and Share to Outlook for meeting chat messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TRUE +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the meeting policy. +For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignatedPresenterRoleMode +Determines if users can change the default value of the _Who can present?_ setting in Meeting options in the Teams client. This policy setting affects all meetings, including Meet Now meetings. + +Possible values are: + +- EveryoneUserOverride: All meeting participants can be presenters. This is the default value. This parameter corresponds to the _Everyone_ setting in Teams. +- EveryoneInCompanyUserOverride: Authenticated users in the organization, including guest users, can be presenters. This parameter corresponds to the _People in my organization_ setting in Teams. +- EveryoneInSameAndFederatedCompanyUserOverride: Authenticated users in the organization, including guest users and users from federated organizations, can be presenters. This parameter corresponds to the _People in my organization and trusted organizations_ setting in Teams. +- OrganizerOnlyUserOverride: Only the meeting organizer can be a presenter and all meeting participants are designated as attendees. This parameter corresponds to the _Only me_ setting in Teams. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DetectSensitiveContentDuringScreenSharing + +Allows the admin to enable sensitive content detection during screen share. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnrollUserOverride +Turn on/off Biometric enrollment +Possible values are: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExplicitRecordingConsent +Set participant agreement and notification for Recording, Transcript, Copilot in Teams meetings. + +Possible Values: + +- Enabled: Explicit consent, requires participant agreement. +- Disabled: Implicit consent, does not require participant agreement. +- LegitimateInterest: Legitimate interest, less restrictive consent to meet legitimate interest without requiring explicit agreement from participants. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalMeetingJoin +Determines whether the user is allowed to join external meetings. + +Possible values are: + +- EnabledForAnyone +- EnabledForTrustedOrgs +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: EnabledForAnyone +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InfoShownInReportMode + +This policy controls what kind of information get shown for the user's attendance in attendance report/dashboard. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPAudioMode +Determines whether audio can be turned on in meetings and group calls. Set this to ENABLEDOUTGOINGINCOMING to allow outgoing and incoming audio in the meeting. Set this to DISABLED to prohibit outgoing and incoming audio in the meeting. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPVideoMode +Determines whether video can be turned on in meetings and group calls. Set this to ENABLEDOUTGOINGINCOMING to allow outgoing and incoming video in the meeting. Set this to DISABLED to prohibit outgoing and incoming video in the meeting. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveCaptionsEnabledType +Determines whether real-time captions are available for the user in Teams meetings. Set this to DisabledUserOverride to allow user to turn on live captions. Set this to Disabled to prohibit. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: DisabledUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveInterpretationEnabledType +Allows meeting organizers to configure a meeting for language interpretation, selecting attendees of the meeting to become interpreters that other attendees can select and listen to the real-time translation they provide. +Possible values are: + +- **DisabledUserOverride**, if you would like users to be able to use interpretation in meetings but by default it is disabled. +- **Disabled**, prevents the option to be enabled in Meeting Options. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: DisabledUserOverride +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LiveStreamingMode +Determines whether you provide support for your users to stream their Teams meetings to large audiences through Real-Time Messaging Protocol (RTMP). + +Possible values are: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LobbyChat + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Determines whether chat messages are allowed in the lobby. + +Possible values are: + +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaBitRateKb +Determines the media bit rate for audio/video/app sharing transmissions in meetings. + +```yaml +Type: UInt32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingChatEnabledType +Specifies if users will be able to chat in meetings. Possible values are: Disabled, Enabled, and EnabledExceptAnonymous. + +> [!NOTE] +> Due to a new feature rollout, in order to set the value of MeetingChatEnabledType to Disabled, you will need to also set the value of LobbyChat to disabled. e.g., +> Install-Module MicrosoftTeams -RequiredVersion 6.6.1-preview -Force -AllowClobber -AllowPrereleaseConnect-MicrosoftTeams Set-CsTeamsMeetingPolicy -Identity Global -MeetingChatEnabledType Disabled -LobbyChat Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingInviteLanguages +Controls how the join information in meeting invitations is displayed by enforcing a common language or enabling up to two languages to be displayed. + +> [!NOTE] +> All Teams supported languages can be specified using language codes. For more information about its delivery date, see the [roadmap (Feature ID: 81521)](https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=81521). + +The preliminary list of available languages is shown below: + +`ar-SA,az-Latn-AZ,bg-BG,ca-ES,cs-CZ,cy-GB,da-DK,de-DE,el-GR,en-GB,en-US,es-ES,es-MX,et-EE,eu-ES,fi-FI,fil-PH,fr-CA,fr-FR,gl-ES,he-IL,hi-IN,hr-HR,hu-HU,id-ID,is-IS,it-IT,ja-JP,ka-GE,kk-KZ,ko-KR,lt-LT,lv-LV,mk-MK,ms-MY,nb-NO,nl-NL,nn-NO,pl-PL,pt-BR,pt-PT,ro-RO,ru-RU,sk-SK,sl-SL,sq-AL,sr-Latn-RS,sv-SE,th-TH,tr-TR,uk-UA,vi-VN,zh-CN,zh-TW`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NewMeetingRecordingExpirationDays +Specifies the number of days before meeting recordings will expire and move to the recycle bin. Value can be from 1 to 99,999 days. Value can also be -1 to set meeting recordings to never expire. + +> [!NOTE] +> You may opt to set Meeting Recordings to never expire by entering the value -1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -NoiseSuppressionForDialInParticipants + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Control Noises Supression Feature for PST legs joining a meeting. + +Possible Values: + +- MicrosoftDefault +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ParticipantNameChange + +This setting will enable Tenant Admins to turn on/off participant renaming feature. + +Possible Values: +Enabled: Turns on the Participant Renaming feature. +Disabled: Turns off the Participant Renaming feature. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PreferredMeetingProviderForIslandsMode +Determines the Outlook meeting add-in available to users on Islands mode. By default, this is set to TeamsAndSfb, and the users sees both the Skype for Business and Teams add-ins. Set this to Teams to remove the Skype for Business add-in and only show the Teams add-in. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TeamsAndSfb +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -QnAEngagementMode + +This setting enables Microsoft 365 Tenant Admins to Enable or Disable the Questions and Answers experience (Q+A). + When Enabled, Organizers can turn on Q+A for their meetings. When Disabled, Organizers cannot turn on Q+A in their meetings. + The setting is enforced when a meeting is created or is updated by Organizers. + Attendees can use Q+A in meetings where it was previously added. Organizers can remove Q+A for those meetings through Teams and Outlook Meeting Options. +Possible values: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RecordingStorageMode +This parameter can take two possible values: + +- Stream +- OneDriveForBusiness + +> [!NOTE] +> The change of storing Teams meeting recordings from Classic Stream to OneDrive and SharePoint (ODSP) has been completed as of August 30th, 2021. All recordings are now stored in ODSP. This change overrides the RecordingStorageMode parameter, and modifying the setting in PowerShell no longer has any impact. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoomAttributeUserOverride +Possible values: + +- Off +- Distinguish +- Attribute + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RoomPeopleNameUserOverride + +Enabling people recognition requires the tenant CsTeamsMeetingPolicy roomPeopleNameUserOverride to be "On" and roomAttributeUserOverride to be Attribute for allowing individual voice and face profiles to be used for recognition in meetings. + +> [!NOTE] +> In some locations, people recognition can't be used due to local laws or regulations. +Possible values: +> +> - Off: No People Recognition option on Microsoft Teams Room (Default). +> - On: Policy value allows People recognition option on Microsoft Teams Rooms under call control bar. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ScreenSharingMode +Determines the mode in which a user can share a screen in calls or meetings. Set this to SingleApplication to allow the user to share an application at a given point in time. Set this to EntireScreen to allow the user to share anything on their screens. Set this to Disabled to prohibit the user from sharing their screens. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SmsNotifications +Participants can sign up for text message meeting reminders. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SpeakerAttributionMode +Determines if users are identified in transcriptions and if they can change the value of the _Automatically identify me in meeting captions and transcripts_ setting. + +Possible values: + +- **Enabled**: Speakers are identified in transcription. +- **EnabledUserOverride**: Speakers are identified in transcription. If enabled, users can override this setting and choose not to be identified in their Teams profile settings. +- **DisabledUserOverride**: Speakers are not identified in transcription. If enabled, users can override this setting and choose to be identified in their Teams profile settings. +- **Disabled**: Speakers are not identified in transcription. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -StreamingAttendeeMode + +Controls if Teams uses overflow capability once a meeting reaches its capacity (1,000 users with full functionality). + +Possible values are: + +- Disabled +- Enabled + +Set this to Enabled to allow up to 20,000 extra view-only attendees to join. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsCameraFarEndPTZMode +Possible values are: + +- Disabled +- AutoAcceptInTenant +- AutoAcceptAll + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can return your tenant ID by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsersCanAdmitFromLobby + +This policy controls who can admit from the lobby. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VideoFiltersMode +Determines the background effects that a user can configure in the Teams client. Possible values are: + +- NoFilters: No filters are available. +- BlurOnly: Background blur is the only option available (requires a processor with AVX2 support, see [Hardware requirements for Microsoft Teams](https://learn.microsoft.com/microsoftteams/hardware-requirements-for-the-teams-app) for more information). +- BlurAndDefaultBackgrounds: Background blur and a list of pre-selected images are available. +- AllFilters: All filters are available, including custom images. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceIsolation +Determines whether you provide support for your users to enable voice isolation in Teams meeting calls. + +Possible values are: +- Enabled (default) +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VoiceSimulationInInterpreter + +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Enables the user to use the voice simulation feature while being AI interpreted. + +Possible Values: + +- Disabled +- Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForAnonymousUsers + +Determines the meeting experience and watermark content of an anonymous user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForCameraVideoOpacity + +Allows the transparency of watermark to be customizable. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForCameraVideoPattern + +Allows the pattern design of watermark to be customizable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForScreenSharingOpacity + +Allows the transparency of watermark to be customizable. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WatermarkForScreenSharingPattern + +Allows the pattern design of watermark to be customizable. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedUsersForMeetingDetails +Controls which users should have ability to see the meeting info details on join screen. 'None' option should disable the feature completely. + +Possible Values: +- UsersAllowedToByPassTheLobby: Users who are able to bypass lobby can see the meeting info details. +- Everyone: All meeting participants can see the meeting info details. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: UsersAllowedToByPassTheLobby +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeText +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +Allows users to use real time text during a meeting, allowing them to communicate by typing their messages in real time. + +Possible Values: +- Enabled: User is allowed to turn on real time text. +- Disabled: User is not allowed to turn on real time text. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhoCanRegister +Controls the attendees who can attend a webinar meeting. The default is Everyone, meaning that everyone can register. If you want to restrict registration to internal accounts set the value to 'EveryoneInCompany'. + +Possible values: + +- Everyone +- EveryoneInCompany + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Everyone +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsMeetingTemplatePermissionPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMeetingTemplatePermissionPolicy.md new file mode 100644 index 0000000000..e9a319c5d3 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsMeetingTemplatePermissionPolicy.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +title: Set-CsTeamsMeetingTemplatePermissionPolicy +author: boboPD +ms.author: pradas +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsTeamsMeetingTemplatePermissionPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsMeetingTemplatePermissionPolicy + +## SYNOPSIS +This cmdlet updates an existing TeamsMeetingTemplatePermissionPolicy. + +## SYNTAX + +```powershell + Set-CsTeamsMeetingTemplatePermissionPolicy [-Identity] <string> [-HiddenMeetingTemplates <PSListModifier[HiddenMeetingTemplate]>] [-Description <string>] [-Force][-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +Update any of the properties of an existing instance of the TeamsMeetingTemplatePermissionPolicy. + +## EXAMPLES + +### Example 1 - Updating the description of an existing policy + +```powershell +PS> Set-CsTeamsMeetingTemplatePermissionPolicy -Identity Foobar -Description "updated description" +``` + +Updates the description field of a policy. + +### Example 2 - Updating the hidden meeting template list of an existing policy + +```powershell +PS> Set-CsTeamsMeetingTemplatePermissionPolicy -Identity Foobar -HiddenMeetingTemplates @($hiddentemplate_1, $hiddentemplate_2) +``` + +Updates the hidden meeting templates array. + +## PARAMETERS + +### -Identity + +Name of the policy instance to be updated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenMeetingTemplates + +The updated list of meeting template IDs to hide. +The HiddenMeetingTemplate objects are created with [New-CsTeamsHiddenMeetingTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamshiddenmeetingtemplate). + +```yaml +Type: HiddenMeetingTemplate[] +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Pass in a new description if that field needs to be updated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Get-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingtemplatepermissionpolicy) + +[New-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsmeetingtemplatepermissionpolicy) + +[Remove-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsmeetingtemplatepermissionpolicy) + +[Grant-CsTeamsMeetingTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsmeetingtemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsMessagingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMessagingPolicy.md new file mode 100644 index 0000000000..d7182ff633 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsMessagingPolicy.md @@ -0,0 +1,818 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmessagingpolicy +applicable: Microsoft Teams +title: Set-CsTeamsMessagingPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsMessagingPolicy + +## SYNOPSIS +The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>] + [-AllowChatWithGroup <Boolean>] + [-AllowCommunicationComplianceEndUserReporting <Boolean>] + [-AllowCustomGroupChatAvatars <Boolean>] + [-AllowExtendedWorkInfoInSearch <String>] + [-AllowFluidCollaborate <Boolean>] + [-AllowFullChatPermissionUserToDeleteAnyMessage <Boolean>] + [-AllowGiphy <Boolean>] + [-AllowGiphyDisplay <Boolean>] + [-AllowGroupChatJoinLinks <Boolean>] + [-AllowImmersiveReader <Boolean>] + [-AllowMemes <Boolean>] + [-AllowOwnerDeleteMessage <Boolean>] + [-AllowPasteInternetImage <Boolean>] + [-AllowPriorityMessages <Boolean>] + [-AllowRemoveUser <Boolean>] + [-AllowSecurityEndUserReporting <Boolean>] + [-AllowSmartCompose] <Boolean>] + [-AllowSmartReply <Boolean>] + [-AllowStickers <Boolean>] + [-AllowUrlPreviews <Boolean>] + [-AllowUserChat <Boolean>] + [-AllowUserDeleteChat <Boolean>] + [-AllowUserDeleteMessage <Boolean>] + [-AllowUserEditMessage <Boolean>] + [-AllowUserTranslation <Boolean>] + [-AllowVideoMessages <Boolean>] + [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>] + [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>] + [-ChatPermissionRole <String>] + [-Confirm] + [-CreateCustomEmojis <Boolean>] + [-DeleteCustomEmojis <Boolean>] + [-Description <String>] + [-DesignerForBackgroundsAndImages <DesignerForBackgroundsAndImagesTypeEnum>] + [-Force] + [-GiphyRatingType <String>] + [-InOrganizationChatControl <String>] + [-ReadReceiptsEnabledType <String>] + [-Tenant <Guid>] + [-UsersCanDeleteBotMessages <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsMessagingPolicy [-Instance <PSObject>] + [-AllowChatWithGroup <Boolean>] + [-AllowCommunicationComplianceEndUserReporting <Boolean>] + [-AllowCustomGroupChatAvatars <Boolean>] + [-AllowExtendedWorkInfoInSearch <String>] + [-AllowFluidCollaborate <Boolean>] + [-AllowFullChatPermissionUserToDeleteAnyMessage <Boolean>] + [-AllowGiphy <Boolean>] + [-AllowGiphyDisplay <Boolean>] + [-AllowGroupChatJoinLinks <Boolean>] + [-AllowImmersiveReader <Boolean>] + [-AllowMemes <Boolean>] + [-AllowOwnerDeleteMessage <Boolean>] + [-AllowPasteInternetImage <Boolean>] + [-AllowPriorityMessages <Boolean>] + [-AllowRemoveUser <Boolean>] + [-AllowSecurityEndUserReporting <Boolean>] + [-AllowSmartCompose] <Boolean>] + [-AllowSmartReply <Boolean>] + [-AllowStickers <Boolean>] + [-AllowUrlPreviews <Boolean>] + [-AllowUserChat <Boolean>] + [-AllowUserDeleteChat <Boolean>] + [-AllowUserDeleteMessage <Boolean>] + [-AllowUserEditMessage <Boolean>] + [-AllowUserTranslation <Boolean>] + [-AllowVideoMessages <Boolean>] + [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>] + [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>] + [-Confirm] + [-CreateCustomEmojis <Boolean>] + [-DeleteCustomEmojis <Boolean>] + [-Description <String>] + [-DesignerForBackgroundsAndImages <DesignerForBackgroundsAndImagesTypeEnum>] + [-Force] + [-GiphyRatingType <String>] + [-InOrganizationChatControl <String>] + [-ReadReceiptsEnabledType <String>] + [-Tenant <Guid>] + [-UsersCanDeleteBotMessages <Boolean>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is enabled to exchange messages. These also help determine the type of messages users can create and modify. This cmdlet updates a Teams messaging policy. Custom policies can then be assigned to users using the Grant-CsTeamsMessagingPolicy cmdlet. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Set-CsTeamsMessagingPolicy -Identity StudentMessagingPolicy -AllowGiphy $false -AllowMemes $false +``` + +In this example two different property values are configured: AllowGiphy is set to false and AllowMemes is set to False. +All other policy properties will be left as previously assigned. + +### Example 2 + +```powershell +PS C:\> Get-CsTeamsMessagingPolicy -Identity StudentMessagingPolicy | Set-CsTeamsMessagingPolicy -AllowGiphy $false -AllowMemes $false +``` + +In this example two different property values are configured for all teams messaging policies in the organization: AllowGiphy is set to false and AllowMemes is set to False. +All other policy properties will be left as previously assigned. + +## PARAMETERS + +### -Identity +Identity for the teams messaging policy you're modifying. To modify the global policy, use this syntax: -Identity global. To modify a per-user policy, use syntax similar to this: `-Identity TeamsMessagingPolicy`. + +If you do not specify an Identity the Set-CsTeamsMessagingPolicy cmdlet will automatically modify the global policy. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowChatWithGroup +This setting determines if users can chat with groups (Distribution, M365 and Security groups). +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCommunicationComplianceEndUserReporting +This setting determines if users can report offensive messages to their admin for Communication Compliance. +Possible Values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCustomGroupChatAvatars +These settings enables, disables updating or fetching custom group chat avatars for the users included in the messaging policy. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowExtendedWorkInfoInSearch +This setting enables/disables showing company name and department name in search results for MTO users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowFluidCollaborate +This field enables or disables Fluid Collaborate feature for users. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowFullChatPermissionUserToDeleteAnyMessage +This setting determines if users with the 'Full permissions' role can delete any group or meeting chat message within their tenant. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowGiphy +Determines whether a user is allowed to access and post Giphys. Set this to TRUE to allow. Set this FALSE to prohibit. + +**Note**: [Optional Connected Experiences](https://learn.microsoft.com/deployoffice/privacy/manage-privacy-controls#policy-setting-for-optional-connected-experiences) must be also enabled for Giphys to be allowed. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowGiphyDisplay +Determines if Giphy images should be displayed that had been already sent or received in chat. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowGroupChatJoinLinks +This setting determines if users in a group chat can create and share join links for other users within the organization to join that chat. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowImmersiveReader +Determines whether a user is allowed to use Immersive Reader for reading conversation messages. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMemes +Determines whether a user is allowed to access and post memes. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowOwnerDeleteMessage +Determines whether owners are allowed to delete all the messages in their team. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPasteInternetImage +Determines if a user is allowed to paste internet-based images in compose. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPriorityMessages +Determines whether a user is allowed to send priority messages. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowRemoveUser +Determines whether a user is allowed to remove a user from a conversation. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSecurityEndUserReporting +This setting determines if users can report any security concern posted in message to their admin. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSmartCompose +Turn on this setting to let a user get text predictions for chat messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Con nombre +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowSmartReply +Turn this setting on to enable suggested replies for chat messages. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowStickers +Determines whether a user is allowed to access and post stickers. Set this to TRUE to allow. Set this FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUrlPreviews +Use this setting to turn automatic URL previewing on or off in messages. Set this to TRUE to turn on. Set this to FALSE to turn off. + +Note that [Optional Connected Experiences](https://learn.microsoft.com/deployoffice/privacy/manage-privacy-controls#policy-setting-for-optional-connected-experiences) must be also enabled for URL previews to be allowed. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserChat +Determines whether a user is allowed to chat. Set this to TRUE to allow a user to chat across private chat, group chat and in meetings. Set this to FALSE to prohibit all chat. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserDeleteChat +Turn this setting on to allow users to permanently delete their 1:1, group chat, and meeting chat as participants (this deletes the chat only for them, not other users in the chat). Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: TRUE +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserDeleteMessage +Determines whether a user is allowed to delete their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. +If this value is set to FALSE, the team owner will not be able to delete their own messages. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserEditMessage +Determines whether a user is allowed to edit their own messages. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowUserTranslation +Determines whether a user is allowed to translate messages to their client languages. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowVideoMessages +This setting determines if users can create and send video messages. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AudioMessageEnabledType +Determines whether a user is allowed to send audio messages. Possible values are: ChatsAndChannels, ChatsOnly, Disabled. + +```yaml +Type: AudioMessageEnabledTypeEnum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChannelsInChatListEnabledType +On mobile devices, enable to display favorite channels above recent chats. + +Possible values are: DisabledUserOverride, EnabledUserOverride. + +```yaml +Type: ChannelsInChatListEnabledTypeEnum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ChatPermissionRole +Determines the Supervised Chat role of the user. Set this to Full to allow the user to supervise chats. Supervisors have the ability to initiate chats with and invite any user within the environment. Set this to Limited to allow the user to initiate conversations with Full and Limited permissioned users, but not Restricted. Set this to Restricted to block chat creation with anyone other than Full permissioned users. + +```yaml +Type: String +Position: Named +Default value: Restricted +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CreateCustomEmojis +This setting enables the creation of custom emojis and reactions within an organization for the specified policy users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DeleteCustomEmojis +These settings enable and disable the editing and deletion of custom emojis and reactions for the users included in the messaging policy. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of your policy to identify purpose of creating it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignerForBackgroundsAndImages +This setting determines whether a user is allowed to create custom AI-powered backgrounds and images with MS Designer. + +Possible values are: Enabled, Disabled. + +```yaml +Type: DesignerForBackgroundsAndImagesTypeEnum +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GiphyRatingType +Determines the Giphy content restrictions applicable to a user. Set this to STRICT, MODERATE or NORESTRICTION. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InOrganizationChatControl +This setting determines if chat regulation for internal communication in the tenant is allowed. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReadReceiptsEnabledType +Use this setting to specify whether read receipts are user controlled, enabled for everyone, or disabled. Set this to UserPreference, Everyone or None. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose external user communication policy are being created. For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can return your tenant ID by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. Instead, the tenant ID will automatically be filled in for you based on your connection information. The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsersCanDeleteBotMessages +Determines whether a user is allowed to delete messages sent by bots. Set this to TRUE to allow. Set this to FALSE to prohibit. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsMobilityPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMobilityPolicy.md similarity index 81% rename from skype/skype-ps/skype/Set-CsTeamsMobilityPolicy.md rename to teams/teams-ps/teams/Set-CsTeamsMobilityPolicy.md index 3fbc985085..483c23e72a 100644 --- a/skype/skype-ps/skype/Set-CsTeamsMobilityPolicy.md +++ b/teams/teams-ps/teams/Set-CsTeamsMobilityPolicy.md @@ -1,168 +1,179 @@ ---- -external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamsmobilitypolicy -applicable: Skype for Business Online -title: Set-CsTeamsMobilityPolicy -schema: 2.0.0 -manager: ritikag -author: saragava -ms.author: saragava -ms.reviewer: ---- - - -# Set-CsTeamsMobilityPolicy - -## SYNOPSIS -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -## SYNTAX - -### Identity (Default) -``` -Set-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Description <String>] [-IPVideoMobileMode <String>] - [-IPAudioMobileMode <String>] [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -### Instance -``` -Set-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Description <String>] [-IPVideoMobileMode <String>] - [-IPAudioMobileMode <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] -``` - -## DESCRIPTION -The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. - -The Set-CsTeamsMobilityPolicy cmdlet allows administrators to update teams mobility policies. - -NOTE: Please note that this cmdlet was deprecated and then removed from this PowerShell module. This reference will continue to be listed here for legacy purposes. - -## EXAMPLES - -### Example 1 -```powershell -PS C:\> Set-CsTeamsMobilityPolicy -Identity SalesPolicy -IPVideoMobileMode "WifiOnly -``` -The command shown in Example 1 uses the Set-CsTeamsMobilityPolicy cmdlet to update an existing teams mobility policy with the Identity SalesPolicy. This SalesPolicy will not have IPVideoMobileMode equal to "WifiOnly". - -## PARAMETERS - -### -Confirm -Prompts you for confirmation before running the cmdlet. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Description -Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Force -Bypasses all non-fatal errors. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPAudioMobileMode -When set to WifiOnly, prohibits the user from making, receiving calls or joining meetings using VoIP calls on the mobile device while on cellular data connection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -IPVideoMobileMode -When set to WifiOnly, prohibits the user from making, receiving video calls or enabling video in meetings using VoIP calls on the mobile device while on cellular data connection. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Identity -Specify the name of the policy that you are creating. - -```yaml -Type: XdsIdentity -Parameter Sets: Identity -Aliases: - -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -Shows what would happen if the cmdlet runs. -The cmdlet is not run. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### 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](http://go.microsoft.com/fwlink/?LinkID=113216). - -## INPUTS - -### System.Management.Automation.PSObject - -## OUTPUTS - -### System.Object -## NOTES - -## RELATED LINKS +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmobilitypolicy +applicable: Microsoft Teams +title: Set-CsTeamsMobilityPolicy +schema: 2.0.0 +manager: ritikag +ms.reviewer: ritikag +--- + +# Set-CsTeamsMobilityPolicy + +## SYNOPSIS +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Description <String>] [-IPVideoMobileMode <String>] + [-IPAudioMobileMode <String>] [[-Identity] <XdsIdentity>] [-MobileDialerPreference <String>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTeamsMobilityPolicy [-Tenant <System.Guid>] [-Description <String>] [-IPVideoMobileMode <String>] + [-IPAudioMobileMode <String>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users. + +The Set-CsTeamsMobilityPolicy cmdlet allows administrators to update teams mobility policies. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsMobilityPolicy -Identity SalesPolicy -IPVideoMobileMode "WifiOnly +``` +The command shown in Example 1 uses the Set-CsTeamsMobilityPolicy cmdlet to update an existing teams mobility policy with the Identity SalesPolicy. This SalesPolicy will not have IPVideoMobileMode equal to "WifiOnly". + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Bypasses all non-fatal errors. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPAudioMobileMode +When set to WifiOnly, prohibits the user from making, receiving calls or joining meetings using VoIP calls on the mobile device while on cellular data connection. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IPVideoMobileMode +When set to WifiOnly, prohibits the user from making, receiving video calls or enabling video in meetings using VoIP calls on the mobile device while on cellular data connection. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy that you are creating. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MobileDialerPreference +Determines the mobile dialer preference, possible values are: Teams, Native, UserOverride. +For more information, see [Manage user incoming calling policies](https://learn.microsoft.com/microsoftteams/operator-connect-mobile-configure#manage-user-incoming-calling-policies). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsMultiTenantOrganizationConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsMultiTenantOrganizationConfiguration.md new file mode 100644 index 0000000000..0e092c6abe --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsMultiTenantOrganizationConfiguration.md @@ -0,0 +1,89 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +applicable: Microsoft Teams +title: Set-CsTeamsMultiTenantOrganizationConfiguration +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsmultitenantorganizationconfiguration +schema: 2.0.0 +author: samlyu +ms.author: samlyu +--- + +# Set-CsTeamsMultiTenantOrganizationConfiguration + +## SYNOPSIS + +This cmdlet configures the Multi-tenant Organization settings for the tenant. + +## SYNTAX + +``` +Set-CsTeamsMultiTenantOrganizationConfiguration + [[-Identity] <string>] + [-CopilotFromHomeTenant <Enabled/Disabled>] +``` + +## DESCRIPTION +The Set-CsTeamsMultiTenantOrganizationConfiguration cmdlet configures tenant settings for Multi-tenant Organizations. This includes the CopilotFromHomeTenant parameter, which determines if users in a Multi-Tenant Organization can use their Copilot license from their home tenant during cross-tenant meetings + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsMultiTenantOrganizationConfiguration -Identity Global -CopilotFromHomeTenant Disabled +``` + +Set Teams Multi-tenant Organization Setting "CopilotFromHomeTenant" value to "Disabled" for global as default. + +### Example 2 +```powershell +PS C:\> Set-CsTeamsMultiTenantOrganizationConfiguration -Identity Global -CopilotFromHomeTenant Enabled + +``` + +Set Teams Multi-tenant Organization Setting "CopilotFromHomeTenant" value to "Enabled" for global as default. + +## PARAMETERS + +### -Identity +Identity of the Teams Multi-tenant Organization Setting. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CopilotFromHomeTenant +Setting value of the Teams Multi-tenant Organization Setting. CopilotFromHomeTenant controls user access to Copilot license in their home tenant during cross-tenant meetings. + +```yaml +Type: Boolean +Parameter Sets: ("Enabled","Disabled") +Aliases: + +Required: True +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsMultiTenantOrganizationConfiguration](Get-CsTeamsMultiTenantOrganizationConfiguration.md) diff --git a/teams/teams-ps/teams/Set-CsTeamsNetworkRoamingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsNetworkRoamingPolicy.md new file mode 100644 index 0000000000..f7d01f2e45 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsNetworkRoamingPolicy.md @@ -0,0 +1,125 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsnetworkroamingpolicy +applicable: Microsoft Teams +title: Set-CsTeamsNetworkRoamingPolicy +author: TristanChen-msft +ms.author: jiaych +ms.reviewer: +manager: mreddy +schema: 2.0.0 +--- + +# Set-CsTeamsNetworkRoamingPolicy + +## SYNOPSIS + +Set-CsTeamsNetworkRoamingPolicy allows IT Admins to create or update policies for Network Roaming and Bandwidth Control experiences in Microsoft Teams. + +## SYNTAX + +``` +Set-CsTeamsNetworkRoamingPolicy [-Identity <XdsIdentity>] + [-AllowIPVideo <Boolean>] + [-Description <String>] + [-MediaBitRateKb <Integer>] + [-Tenant <System.Guid>] + [<CommonParameters>] +``` + +## DESCRIPTION +Updates or creates new Teams Network Roaming Policies configured for use in your organization. + +The TeamsNetworkRoamingPolicy cmdlets enable administrators to provide specific settings from the TeamsMeetingPolicy to be rendered dynamically based upon the location of the Teams client. The TeamsNetworkRoamingPolicy cannot be granted to a user but instead can be assigned to a network site. The settings from the TeamsMeetingPolicy included are AllowIPVideo and MediaBitRateKb. When a Teams client is connected to a network site where a CsTeamRoamingPolicy is assigned, these two settings from the TeamsRoamingPolicy will be used instead of the settings from the TeamsMeetingPolicy. + +More on the impact of bit rate setting on bandwidth can be found [here](https://learn.microsoft.com/microsoftteams/prepare-network). + +To enable the network roaming policy for users who are not Enterprise Voice enabled, you must also enable the AllowNetworkConfigurationSettingsLookup setting in TeamsMeetingPolicy. This setting is off by default. See Set-TeamsMeetingPolicy for more information on how to enable AllowNetworkConfigurationSettingsLookup for users who are not Enterprise Voice enabled. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +PS C:\> Set-CsTeamsNetworkRoamingPolicy -Identity "RedmondRoaming" -AllowIPVideo $true -MediaBitRateKb 2000 -Description "Redmond campus roaming policy" +``` + +The command shown in Example 1 updates the teams network roaming policy with Identity "RedmondRoaming" with IP Video feature enabled, and the maximum media bit rate is capped at 2000 Kbps. + +## PARAMETERS + +### -Identity +Unique identifier of the policy to be modified. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowIPVideo +Determines whether video is enabled in a user's meetings or calls. +Set this to TRUE to allow the user to share their video. Set this to FALSE to prohibit the user from sharing their video. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MediaBitRateKb +Determines the media bit rate for audio/video/app sharing transmissions in meetings. + +```yaml +Type: Integer +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 50000 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Description of the policy to be edited. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsNotificationAndFeedsPolicy.md b/teams/teams-ps/teams/Set-CsTeamsNotificationAndFeedsPolicy.md new file mode 100644 index 0000000000..b5598c89ee --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsNotificationAndFeedsPolicy.md @@ -0,0 +1,166 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsnotificationandfeedspolicy +title: Set-CsTeamsNotificationAndFeedsPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsNotificationAndFeedsPolicy + +## SYNOPSIS + +Modifies an existing Teams Notifications and Feeds Policy + +## SYNTAX + +```powershell +Set-CsTeamsNotificationAndFeedsPolicy [-Description <String>] [[-Identity] <String>] + [-SuggestedFeedsEnabledType <String>] [-TrendingFeedsEnabledType <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Microsoft Teams notifications and feeds policy allows administrators to manage how notifications and activity feeds are handled within Teams. This policy includes settings that control the types of notifications users receive, how they are delivered, and which activities are highlighted in their feeds. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Set-CsTeamsNotificationAndFeedsPolicy Global -SuggestedFeedsEnabledType EnabledUserOverride +``` + +Change settings on an existing Notifications and Feeds Policy. + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Free format text + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier assigned to the policy when it was created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SuggestedFeedsEnabledType + +The SuggestedFeedsEnabledType parameter in the Microsoft Teams notifications and feeds policy controls whether users receive notifications about suggested activities and content within their Teams environment. When enabled, this parameter ensures that users are notified about recommended or relevant activities, helping them stay informed and engaged with important updates and interactions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TrendingFeedsEnabledType + +The TrendingFeedsEnabledType parameter in the Microsoft Teams notifications and feeds policy controls whether users receive notifications about trending activities within their Teams environment. When enabled, this parameter ensures that users are notified about popular or important activities, helping them stay informed about significant updates and interactions. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/skype/skype-ps/skype/Set-CsTeamsPinnedApp.md b/teams/teams-ps/teams/Set-CsTeamsPinnedApp.md similarity index 77% rename from skype/skype-ps/skype/Set-CsTeamsPinnedApp.md rename to teams/teams-ps/teams/Set-CsTeamsPinnedApp.md index 29aa09abc9..fac26286e2 100644 --- a/skype/skype-ps/skype/Set-CsTeamsPinnedApp.md +++ b/teams/teams-ps/teams/Set-CsTeamsPinnedApp.md @@ -1,23 +1,23 @@ --- external help file: Microsoft.Rtc.Management.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csteamspinnedapp -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/skype/set-csteamspinnedapp +applicable: Microsoft Teams title: Set-CsTeamsPinnedApp schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTeamsPinnedApp ## SYNOPSIS +**NOTE**: This cmdlet has been deprecated. As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. ## SYNTAX @@ -34,10 +34,12 @@ Set-CsTeamsPinnedApp [-Tenant <System.Guid>] [-Order <Int64>] [-Priority <Int32> ``` ## DESCRIPTION +**NOTE**: This cmdlet has been deprecated. + As an admin, you can use app setup policies to customize Microsoft Teams to highlight the apps that are most important for your users. You choose the apps to pin and set the order that they appear. App setup policies let you showcase apps that users in your organization need, including ones built by third parties or by developers in your organization. You can also use app setup policies to manage how built-in features appear. -Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: https://docs.microsoft.com/MicrosoftTeams/teams-app-setup-policies -The existence of this cmdlet is being documented for completeness, but do not use this cmdlet. **We require that all creation and modification of app setup polices (not including the assignment or removal of policies from users) happens in the Microsoft Teams & Skype for Business Admin Center to ensure that the policy matches your expectations for the end user experience.** +Apps are pinned to the app bar. This is the bar on the side of the Teams desktop client and at the bottom of the Teams mobile clients (iOS and Android). Learn more about the App Setup Policies: <https://learn.microsoft.com/MicrosoftTeams/teams-app-setup-policies>. + ## EXAMPLES ### Example 1 @@ -167,14 +169,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### System.Management.Automation.PSObject - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Set-CsTeamsRecordingRollOutPolicy.md b/teams/teams-ps/teams/Set-CsTeamsRecordingRollOutPolicy.md new file mode 100644 index 0000000000..f41ad5f975 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsRecordingRollOutPolicy.md @@ -0,0 +1,135 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsrecordingrolloutpolicy +schema: 2.0.0 +applicable: Microsoft Teams +title: Set-CsTeamsRecordingRollOutPolicy +manager: yujin1 +author: ronwa +ms.author: ronwa +--- + +# Set-CsTeamsRecordingRollOutPolicy + +## SYNOPSIS +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. + +## SYNTAX + +``` +Set-CsTeamsRecordingRollOutPolicy [-MeetingRecordingOwnership <String>] [-Identity] <String> [-Force] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings. This policy would be deprecated over time as this is only to allow IT admins to phase the roll out of this breaking change. + +The Set-CsTeamsRecordingRollOutPolicy cmdlet allows administrators to update existing CsTeamsRecordingRollOutPolicy that can be assigned to particular users to control Teams recording storage place. + +This command is available from Teams powershell module 6.1.1-preview and above. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsRecordingRollOutPolicy -Identity OrganizerPolicy -MeetingRecordingOwnership RecordingInitiator +``` + +The command shown in Example 1 uses the Set-CsTeamsMeetingPolicy cmdlet to update an existing CsTeamsRecordingRollOutPolicy with the Identity OrganizerPolicy. +This policy will set MeetingRecordingOwnership to RecordingInitiator; in this example, recordings for this policy group's users as organizer would get saved to recording initiators' own OneDrive. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy being created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingRecordingOwnership +Specifies where the meeting recording get stored. Possible values are: +- MeetingOrganizer +- RecordingInitiator + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsRoomVideoTeleConferencingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsRoomVideoTeleConferencingPolicy.md new file mode 100644 index 0000000000..171a3e9cd7 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsRoomVideoTeleConferencingPolicy.md @@ -0,0 +1,225 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsroomvideoteleconferencingpolicy +title: Set-CsTeamsRoomVideoTeleConferencingPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsRoomVideoTeleConferencingPolicy + +## SYNOPSIS + +Modifies the property of an existing TeamsRoomVideoTeleConferencingPolicy. + +## SYNTAX + +```powershell +Set-CsTeamsRoomVideoTeleConferencingPolicy [-AreaCode <String>] [-Description <String>] [-Enabled <Boolean>] + [[-Identity] <String>] [-PlaceExternalCalls <String>] [-PlaceInternalCalls <String>] + [-ReceiveExternalCalls <String>] [-ReceiveInternalCalls <String>] [-MsftInternalProcessingMode <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Room Video Teleconferencing Policy enables administrators to configure and manage video teleconferencing behavior for Microsoft Teams Rooms (meeting room devices). + +## PARAMETERS + +### -AreaCode + +GUID provided by the CVI partner that the customer signed the agreement with + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide additional text to accompany the policy. For example, the Description might include information about the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled + +The policy can exist for the tenant but it can be enabled or disabled. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier for the policy to be modified. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PlaceExternalCalls + +The IT admin can configure that their Teams rooms are enabled to place external calls or not, meaning calls from the Microsoft Teams Rooms to Video teleconferencing devices that are outside their own tenant. +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PlaceInternalCalls + +The IT admin can configure that their Teams rooms are enabled to place internal calls or not. Meaning calls from the Microsoft Teams Rooms to Video teleconferencing devices that are within their own tenant. +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveExternalCalls + +The IT admin can configure that their Teams rooms are enabled to receive external calls or not, meaning calls from Video teleconferencing devices that are outside their own tenant. +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveInternalCalls + +The IT admin can configure that their Teams rooms are enabled to receive external calls or not. Meaning calls from Video Teleconferencing devices from their own tenant +Value: Enabled, Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsSettingsCustomApp.md b/teams/teams-ps/teams/Set-CsTeamsSettingsCustomApp.md new file mode 100644 index 0000000000..455aab2ff0 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsSettingsCustomApp.md @@ -0,0 +1,95 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamssettingscustomapp +title: Set-CsTeamsSettingsCustomApp +schema: 2.0.0 +--- + +# Set-CsTeamsSettingsCustomApp + +## SYNOPSIS +Set the Custom Apps Setting's value of Teams Admin Center. + +## SYNTAX + +``` +Set-CsTeamsSettingsCustomApp -isSideloadedAppsInteractionEnabled <Boolean> + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +There is a switch for managing Custom Apps in the Org-wide App Settings page of Teams Admin Center. The command can set the value of this switch. If the isSideloadedAppsInteractionEnabled is set to true, the switch is enabled. So that the custom apps can be uploaded as app packages and available in the organization's app store, vice versa. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsSettingsCustomApp -isSideloadedAppsInteractionEnabled $True +``` + +Set the value of Custom Apps Setting to true. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -isSideloadedAppsInteractionEnabled +The value to Custom Apps Setting. If the value is true, the custom apps can be uploaded as app packages and available in the organization's app store, vice versa. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsTeamsSettingsCustomApp](https://learn.microsoft.com/powershell/module/teams/get-csteamssettingscustomapp) diff --git a/teams/teams-ps/teams/Set-CsTeamsSharedCallingRoutingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsSharedCallingRoutingPolicy.md new file mode 100644 index 0000000000..31c805cfbb --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsSharedCallingRoutingPolicy.md @@ -0,0 +1,197 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamssharedcallingroutingpolicy +applicable: Microsoft Teams +title: Set-CsTeamsSharedCallingRoutingPolicy +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: + +--- + +# Set-CsTeamsSharedCallingRoutingPolicy + +## SYNOPSIS +Use the Set-CsTeamsSharedCallingRoutingPolicy cmdlet to change a shared calling routing policy instance. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsSharedCallingRoutingPolicy [-Identity] <string> [-EmergencyNumbers <PSListModifier[string]>] + [-ResourceAccount <string>] [-Description <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams shared calling routing policy configures the caller ID for normal outbound PSTN and emergency calls made by users enabled for shared calling using this policy instance. + +The caller ID for normal outbound PSTN calls is the phone number assigned to the resource account specified in the policy instance. Typically this is the organization's main auto attendant phone number. Callbacks will go to the auto attendant and the PSTN caller can use the auto attendant to be transferred to the shared calling user. + +When a shared calling user makes an emergency call, the emergency services need to be able to make a direct callback to the user who placed the emergency call. One of the defined emergency numbers is used for this purpose as caller ID for the emergency call. It will be reserved for the next 60 minutes and any inbound call to that number will directly ring the shared calling user who made the emergency call. If no emergency numbers are defined, the phone number of the resource account will be used as caller ID. If no free emergency numbers are available, the first number in the list will be reused. + +The emergency call will contain the location of the shared calling user. The location will either be the dynamic emergency location obtained by the Teams client or if that is not available the static location assigned to the phone number of the resource account used in the shared calling policy instance. + +## EXAMPLES + +### Example 1 +``` +Set-CsTeamsSharedCallingRoutingPolicy -Identity Seattle -EmergencyNumbers @{remove='+14255556677'} +``` +The command shown in Example 1 removes the emergency callback number +14255556677 from the policy called Seattle. + +## PARAMETERS + +### -Identity +Unique identifier of the Teams shared calling routing policy to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description of the new policy instance. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyNumbers +An array of phone numbers used as caller ID on emergency calls. + +The emergency numbers must be routable for inbound PSTN calls, and for Calling Plan and Operator Connect phone numbers, must be available within the organization. + +The emergency numbers specified must all be of the same phone number type and country as the phone number assigned to the specified resource account. If the resource account has a Calling Plan service number assigned, the emergency numbers need to be Calling Plan subscriber numbers. + +The emergency numbers must be unique and can't be reused in other shared calling policy instances. The emergency numbers can't be assigned to any user or resource account. + +If no emergency numbers are configured, the phone number of the resource account will be used as Caller ID for the emergency call. + +```yaml +Type: System.Management.Automation.PSListModifier[String] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ResourceAccount +The Identity of the resource account. Can only be specified using the Identity or ObjectId of the resource account. + +The phone number assigned to the resource account must: +- Have the same phone number type and country as the emergency numbers configured in this policy instance. +- Must have an emergency location assigned. You can use the Teams PowerShell Module [Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) and the -LocationId parameter to set the location. +- If the resource account is using a Calling Plan service number, you must have a Pay-As-You-Go Calling Plan, and assign it to the resource account. In addition, you need to assign a Communications credits license to the resource account and fund it to support outbound shared calling calls via the Pay-As-You-Go Calling Plan. + +The same resource account can be used in multiple shared calling policy instances. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +In some Calling Plan markets, you are not allowed to set the location on service numbers. In this instance, kindly contact the [Telephone Number Services service desk](https://learn.microsoft.com/microsoftteams/phone-reference/manage-numbers/contact-tns-service-desk). + +If you are attempting to use a resource account with an Operator Connect phone number assigned, kindly confirm support for Shared Calling with your operator. + +Shared Calling is not supported for Calling Plan service phone numbers in Romania, the Czech Republic, Hungary, Singapore, New Zealand, Australia, and Japan. A limited number of existing Calling Plan service phone numbers in other countries are also not supported for Shared Calling. For such service phone numbers, you should contact the [Telephone Number Services service desk](https://learn.microsoft.com/microsoftteams/phone-reference/manage-numbers/contact-tns-service-desk). + +This cmdlet was introduced in Teams PowerShell Module 5.5.0. + +## RELATED LINKS +[New-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamssharedcallingroutingpolicy) + +[Grant-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamssharedcallingroutingpolicy) + +[Remove-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamssharedcallingroutingpolicy) + +[Get-CsTeamsSharedCallingRoutingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamssharedcallingroutingpolicy) + +[Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) diff --git a/teams/teams-ps/teams/Set-CsTeamsShiftsAppPolicy.md b/teams/teams-ps/teams/Set-CsTeamsShiftsAppPolicy.md new file mode 100644 index 0000000000..abbbb97e70 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsShiftsAppPolicy.md @@ -0,0 +1,133 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsapppolicy +title: Set-CsTeamsShiftsAppPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsShiftsAppPolicy + +## SYNOPSIS + +Allows you to set or update properties of a Teams Shifts App Policy instance. + +## SYNTAX + +```powershell +Set-CsTeamsShiftsAppPolicy [-AllowTimeClockLocationDetection <Boolean>] [[-Identity] <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +The Teams Shifts app is designed to help frontline workers and their managers manage schedules and communicate effectively. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Set-CsTeamsShiftsAppPolicy 'Default' -AllowTimeClockLocationDetection $False +``` + +Change Settings on a Teams Shift App Policy (only works on Global policy) + +## PARAMETERS + +### -AllowTimeClockLocationDetection + +Turns on the location detection. The time report will indicate whether workers are "on location" when they clocked in and out. Workers are considered as "on location" if they clock in or out within a 200-meter radius of the set location. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Policy instance name. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsShiftsConnection.md b/teams/teams-ps/teams/Set-CsTeamsShiftsConnection.md new file mode 100644 index 0000000000..dd1eca6bb1 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsShiftsConnection.md @@ -0,0 +1,467 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: Set-CsTeamsShiftsConnection +author: serdarsoysal +ms.author: serdars +manager: valk +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnection +schema: 2.0.0 +--- + +# Set-CsTeamsShiftsConnection + +## SYNOPSIS +This cmdlet sets an existing workforce management (WFM) connection. + +## SYNTAX + +### Set (Default) +```powershell +Set-CsTeamsShiftsConnection -ConnectionId <string> -Body <IUpdateWfmConnectionRequest> [-Authorization <string>] [-IfMatch <string>] + [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] +[-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### SetExpanded +```powershell +Set-CsTeamsShiftsConnection -ConnectionId <string> [-Authorization <string>] [-IfMatch <string>] [-ConnectorId <string>] + [-ConnectorSpecificSettings <IUpdateWfmConnectionRequestConnectorSpecificSettings>] [-Etag <string>] [-Name <string>] + [-State <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] +[-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### SetViaIdentityExpanded +```powershell +Set-CsTeamsShiftsConnection -InputObject <IConfigApiBasedCmdletsIdentity> [-Authorization <string>] [-IfMatch <string>] [-ConnectorId <string>] + [-ConnectorSpecificSettings <IUpdateWfmConnectionRequestConnectorSpecificSettings>] [-Etag <string>] [-Name <string>] [-State <string>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### SetViaIdentity +```powershell +Set-CsTeamsShiftsConnection -InputObject <IConfigApiBasedCmdletsIdentity> -Body <IUpdateWfmConnectionRequest> [-Authorization <string>] +[-IfMatch <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] + [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet updates a Shifts WFM connection. It allows the admin to make changes to the settings such as the name and WFM URLs. Note that the update allows for, but does not require, the -ConnectorSpecificSettings.LoginPwd and ConnectorSpecificSettings.LoginUserName to be included. +This cmdlet can update every input field except -ConnectorId and -ConnectionId. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> $connection = Get-CsTeamsShiftsConnection -ConnectionId 4dae9db0-0841-412c-8d6b-f5684bfebdd7 +PS C:\> $result = Set-CsTeamsShiftsConnection ` + -connectionId $connection.Id ` + -IfMatch $connection.Etag ` + -connectorId "6A51B888-FF44-4FEA-82E1-839401E00000" ` + -name "Cmdlet test connection - updated" ` + -connectorSpecificSettings (New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificBlueYonderSettingsRequest ` + -Property @{ + adminApiUrl = "https://contoso.com/retail/data/wfmadmin/api/v1-beta2" + siteManagerUrl = "https://contoso.com/retail/data/wfmsm/api/v1-beta2" + essApiUrl = "https://contoso.com/retail/data/wfmess/api/v1-beta1" + retailWebApiUrl = "https://contoso.com/retail/data/retailwebapi/api/v1" + cookieAuthUrl = "https://contoso.com/retail/data/login" + federatedAuthUrl = "https://contoso.com/retail/data/login" + LoginUserName = "PlaceholderForUsername" + LoginPwd = "PlaceholderForPassword" + }) ` + -state "Active" + +PS C:\> $result | Format-List +``` + +```output + +ConnectorId : 6A51B888-FF44-4FEA-82E1-839401E00000 +ConnectorSpecificSettingAdminApiUrl : https://www.contoso.com/retail/data/wfmadmin/api/v1-beta2 +ConnectorSpecificSettingApiUrl : +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : +ConnectorSpecificSettingCookieAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingEssApiUrl : https://www.contoso.com/retail/data/wfmess/api/v1-beta2 +ConnectorSpecificSettingFederatedAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingRetailWebApiUrl : https://www.contoso.com/retail/data/retailwebapi/api/v1 +ConnectorSpecificSettingSiteManagerUrl : https://www.contoso.com/retail/data/wfmsm/api/v1-beta2 +ConnectorSpecificSettingSsoUrl : +CreatedDateTime : 24/03/2023 04:58:23 +Etag : "5b00dd1b-0000-0400-0000-641d2df00000" +Id : 4dae9db0-0841-412c-8d6b-f5684bfebdd7 +LastModifiedDateTime : 24/03/2023 04:58:23 +Name : Cmdlet test connection - updated +State : Active +TenantId : 3FDCAAF2-863A-4520-97BA-DFA211595876 + +``` + +Updates the instance with the specified -ConnectionId. Returns the object of the updated connection. + +In case of an error, you can capture the error response as follows: + +* Hold the cmdlet output in a variable: `$result=<CMDLET>` + +* To get the entire error message in Json: `$result.ToJsonString()` + +* To get the error object and object details: `$result, $result.Detail` + +### Example 2 + +```powershell +PS C:\> $connection = Get-CsTeamsShiftsConnection -ConnectionId 79964000-286a-4216-ac60-c795a426d61a +PS C:\> $result = Set-CsTeamsShiftsConnection ` + -connectionId $connection.Id ` + -IfMatch $connection.Etag ` + -connectorId "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0" ` + -name "Cmdlet test connection - updated" ` + -connectorSpecificSettings (New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificUkgDimensionsSettingsRequest ` + -Property @{ + apiUrl = "https://www.contoso.com/api" + ssoUrl = "https://www.contoso.com/sso" + appKey = "PlaceholderForAppKey" + clientId = "Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W" + clientSecret = "PlaceholderForClientSecret" + LoginUserName = "PlaceholderForUsername" + LoginPwd = "PlaceholderForPassword" + }) ` + -state "Active" +PS C:\> $result | Format-List +``` + +```output + +ConnectorId : 95BF2848-2DDA-4425-B0EE-D62AEED4C0A0 +ConnectorSpecificSettingAdminApiUrl : +ConnectorSpecificSettingApiUrl : https://www.contoso.com/api +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W +ConnectorSpecificSettingCookieAuthUrl : +ConnectorSpecificSettingEssApiUrl : +ConnectorSpecificSettingFederatedAuthUrl : +ConnectorSpecificSettingRetailWebApiUrl : +ConnectorSpecificSettingSiteManagerUrl : +ConnectorSpecificSettingSsoUrl : https://www.contoso.com/sso +CreatedDateTime : 06/04/2023 11:05:39 +Etag : "3100fd6e-0000-0400-0000-642ea7840000" +Id : a2d1b091-5140-4dd2-987a-98a8b5338744 +LastModifiedDateTime : 06/04/2023 11:05:39 +Name : Cmdlet test connection - updated +State : Active +TenantId : 3FDCAAF2-863A-4520-97BA-DFA211595876 + +``` + +Updates the instance with the specified -ConnectionId. Returns the object of the updated connection. + +In case of an error, you can capture the error response as follows: + +* Hold the cmdlet output in a variable: `$result=<CMDLET>` + +* To get the entire error message in Json: `$result.ToJsonString()` + +* To get the error object and object details: `$result, $result.Detail` + +## PARAMETERS + +### -Body +The request body. + +```yaml +Type: IUpdateWfmConnectionRequest +Parameter Sets: Set, SetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break +Wait for .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId +The WFM connection ID for the instance. This can be retrieved by running [Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection). + +```yaml +Type: String +Parameter Sets: SetExpanded, Set +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IfMatch +The value of the etag field as returned by the cmdlets. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: SetViaIdentityExpanded, SetViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Name +The connection name. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorSpecificSettings +The connector-specific settings. + +```yaml +Type: IUpdateWfmConnectionRequestConnectorSpecificSettings +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The state of the connection. Valid values are "Active" and "Disabled". A third value, "ErrorDisabled", signifies an error in the connection. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Authorization +Used to provide the necessary credentials for authenticating and authorizing the connection to the workforce management (WFM) system. This parameter ensures that the connection has the appropriate permissions to access and manage the data within the WFM system. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorId +Used to specify the unique identifier of the connector being used for the connection. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Etag +Used to manage concurrency control. It helps ensure that updates to a Shifts connection instance are only applied if the instance has not been modified since it was last retrieved. This is particularly useful in preventing conflicts when multiple administrators might be making changes simultaneously. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IUpdateWfmConnectionRequest + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IWfmConnectionResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection) + +[New-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnection) + +[Update-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/update-csteamsshiftsconnection) + +[Test-CsTeamsShiftsConnectionValidate](https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate) diff --git a/teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md b/teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md new file mode 100644 index 0000000000..eb62460fc0 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md @@ -0,0 +1,547 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: Set-CsTeamsShiftsConnectionInstance +author: leonardospina +ms.author: lespina +manager: valk +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnectioninstance +schema: 2.0.0 +--- + +# Set-CsTeamsShiftsConnectionInstance + +## SYNOPSIS +This cmdlet updates a Shifts connection instance. + +## SYNTAX + +### Set (Default) +```powershell +Set-CsTeamsShiftsConnectionInstance -ConnectorInstanceId <string> -IfMatch <string> -Body <IUpdateConnectorInstanceRequest> +[-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] +[-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### SetExpanded +```powershell +Set-CsTeamsShiftsConnectionInstance -ConnectorInstanceId <string> -IfMatch <string> [-ConnectionId <string>] [-ConnectorAdminEmail <string[]>] +[-DesignatedActorId <string>] [-Etag <string>] [-Name <string>] [-State <string>] [-SyncFrequencyInMin <int>] [-SyncScenarioOfferShiftRequest <string>] +[-SyncScenarioOpenShift <string>] [-SyncScenarioOpenShiftRequest <string>] [-SyncScenarioShift <string>] [-SyncScenarioSwapRequest <string>] + [-SyncScenarioTimeCard <string>] [-SyncScenarioTimeOff <string>] [-SyncScenarioTimeOffRequest <string>] [-SyncScenarioUserShiftPreference <string>] + [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### SetViaIdentityExpanded +```powershell +Set-CsTeamsShiftsConnectionInstance -InputObject <IConfigApiBasedCmdletsIdentity> -IfMatch <string> [-ConnectionId <string>] [-ConnectorAdminEmail <string[]>] + [-DesignatedActorId <string>] [-Etag <string>] [-Name <string>] [-State <string>] [-SyncFrequencyInMin <int>] [-SyncScenarioOfferShiftRequest <string>] +[-SyncScenarioOpenShift <string>] [-SyncScenarioOpenShiftRequest <string>] [-SyncScenarioShift <string>] [-SyncScenarioSwapRequest <string>] + [-SyncScenarioTimeCard <string>] [-SyncScenarioTimeOff <string>] [-SyncScenarioTimeOffRequest <string>] [-SyncScenarioUserShiftPreference <string>] + [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### SetViaIdentity +```powershell +Set-CsTeamsShiftsConnectionInstance -InputObject <IConfigApiBasedCmdletsIdentity> -IfMatch <string> -Body <IUpdateConnectorInstanceRequest> [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet updates a Shifts connection instance. It allows the admin to make changes to the settings in the instance such as name, enabled scenarios, and sync frequency. +This cmdlet can update every input field except -ConnectorId and -ConnectorInstanceId. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> $connectionInstance = Get-CsTeamsShiftsConnectionInstance -ConnectorInstanceId WCI-eba2865f-6cac-46f9-8733-e0631a4536e1 +PS C:\> $result = Set-CsTeamsShiftsConnectionInstance ` + -connectorInstanceId "WCI-eba2865f-6cac-46f9-8733-e0631a4536e1" + -IfMatch $connectionInstance.Etag ` + -connectionId "79964000-286a-4216-ac60-c795a426d61a" ` + -name "Cmdlet test instance - updated" ` + -connectorAdminEmail @() ` + -designatedActorId "93f85765-47db-412d-8f06-9844718762a1" ` + -State "Active" ` + -syncFrequencyInMin "10" ` + -SyncScenarioOfferShiftRequest "FromWfmToShifts" ` + -SyncScenarioOpenShift "FromWfmToShifts" ` + -SyncScenarioOpenShiftRequest "FromWfmToShifts" ` + -SyncScenarioShift "FromWfmToShifts" ` + -SyncScenarioSwapRequest "FromWfmToShifts" ` + -SyncScenarioTimeCard "FromWfmToShifts" ` + -SyncScenarioTimeOff "FromWfmToShifts" ` + -SyncScenarioTimeOffRequest "FromWfmToShifts" ` + -SyncScenarioUserShiftPreference "Disabled" + +PS C:\> $result.ToJsonString() +``` + +```output + +{ + "syncScenarios": { + "offerShiftRequest": "FromWfmToShifts", + "openShift": "FromWfmToShifts", + "openShiftRequest": "FromWfmToShifts", + "shift": "FromWfmToShifts", + "swapRequest": "FromWfmToShifts", + "timeCard": "FromWfmToShifts", + "timeOff": "FromWfmToShifts", + "timeOffRequest": "FromWfmToShifts", + "userShiftPreferences": "Disabled" + }, + "id": "WCI-eba2865f-6cac-46f9-8733-e0631a4536e1", + "tenantId": "dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a", + "connectionId": "a2d1b091-5140-4dd2-987a-98a8b5338744", + "connectorAdminEmails": [ ], + "connectorId": "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0", + "designatedActorId": "ec1a4edb-1a5f-4b2d-b2a4-37aab6ebd231", + "name": "Cmdlet test instance - updated", + "syncFrequencyInMin": 10, + "workforceIntegrationId": "WFI_6b225907-b476-4d40-9773-08b86db7b11b", + "etag": "\"4f005d22-0000-0400-0000-642ff64a0000\"", + "createdDateTime": "2023-04-07T10:54:01.8170000Z", + "lastModifiedDateTime": "2023-04-07T10:54:01.8170000Z", + "state": "Active" +} + +``` + +Updates the instance with the specified -ConnectorInstanceId. Returns the object of the updated connector instance. + +In case of error, we can capture the error response as following: + +* Hold the cmdlet output in a variable: `$result=<CMDLET>` + +* To get the entire error message in Json: `$result.ToJsonString()` + +* To get the error object and object details: `$result, $result.Detail` + +## PARAMETERS + +### -Body +The request body + +```yaml +Type: IConnectorInstanceRequest +Parameter Sets: Set, SetViaIdentity +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorAdminEmail +Gets or sets the list of connector admin email addresses. + +```yaml +Type: String[] +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorInstanceId +The Id of the connector instance to be updated. + +```yaml +Type: String +Parameter Sets: SetExpanded, Set +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId +Gets or sets the WFM connection ID for the new instance. This can be retrieved by running [Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection). + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignatedActorId +Gets or sets the designated actor ID that App acts as for Shifts Graph API calls. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOfferShiftRequest +The sync state for the offer shift request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOpenShift +The sync state for the open shift scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOpenShiftRequest +The sync state for the open shift request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioShift +The sync state for the shift scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioSwapRequest +The sync state for the shift swap request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeCard +The sync state for the time card scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeOff +The sync state for the time off scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeOffRequest +The sync state for the time off request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioUserShiftPreference +The sync state for the user shift preferences scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IfMatch +The value of the etag field as returned by the cmdlets. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter. + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: SetViaIdentityExpanded, SetViaIdentity +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Name +The connector instance name. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The state of the connection instance. Valid values are "Active" and "Disabled". A third value, "ErrorDisabled", signifies an error in the connection instance. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncFrequencyInMin +The sync frequency in minutes. + +```yaml +Type: Int32 +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Etag +Used to manage concurrency control. It helps ensure that updates to a Shifts connection instance are only applied if the instance has not been modified since it was last retrieved. This is particularly useful in preventing conflicts when multiple administrators might be making changes simultaneously. + +```yaml +Type: String +Parameter Sets: SetExpanded, SetViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConnectorInstanceRequest + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConnectorInstanceResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) + +[New-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectioninstance) + +[Update-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/update-csteamsshiftsconnectioninstance) + +[Remove-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectioninstance) + +[Test-CsTeamsShiftsConnectionValidate](https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate) diff --git a/teams/teams-ps/teams/Set-CsTeamsShiftsPolicy.md b/teams/teams-ps/teams/Set-CsTeamsShiftsPolicy.md new file mode 100644 index 0000000000..6835a0dfa9 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsShiftsPolicy.md @@ -0,0 +1,220 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-teamsshiftspolicy +title: Set-CsTeamsShiftsPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsShiftsPolicy + +## SYNOPSIS + +This cmdlet allows you to set or update properties of a TeamsShiftPolicy instance, including Teams off shift warning message-specific settings. + +## SYNTAX + +```powershell +Set-CsTeamsShiftsPolicy [-ShiftNoticeFrequency <String>] [-ShiftNoticeMessageType <String>] + [-ShiftNoticeMessageCustom <String>] [-AccessType <String>] [-AccessGracePeriodMinutes <Int64>] + [-EnableScheduleOwnerPermissions <Boolean>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet allows you to set or update properties of a TeamsShiftPolicy instance. Use this to set the policy name and Teams off shift warning message-specific settings (ShiftNoticeMessageType, ShiftNoticeMessageCustom, ShiftNoticeFrequency, AccessGracePeriodMinutes). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsShiftsPolicy -Identity OffShiftAccess_WarningMessage1_AlwaysShowMessage -ShiftNoticeMessageType Message1 -ShiftNoticeFrequency always -AccessGracePeriodMinutes 5 +``` +In this example, the policy instance is called "OffShiftAccess_WarningMessage1_AlwaysShowMessage", a warning message (Message 1) will always be displayed to the user on opening Teams during off shift hours. + +## PARAMETERS + +### -Identity +Policy instance name. + +```yaml +Type: XdsIdentity +Parameter Sets: Identity +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessType +Indicates the Teams access type granted to the user. Today, only unrestricted access to Teams app is supported. +Use 'UnrestrictedAccess_TeamsApp' as the value for this setting, or is set by default. +For Teams Off Shift Access Control, the option to show the user a blocking dialog message is supported. Once the user accepts this message, it is audit logged and the user has usual access to Teams. Set other off shift warning message-specific settings to configure off shift access controls for the user. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: UnrestrictedAccess_TeamsApp +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftNoticeMessageType +The warning message is shown in the blocking dialog when a user access Teams off shift hours. Select one of 7 Microsoft provided messages, a default message or a custom message. +'Message1' - Your employer does not authorize or approve of the use of its network, applications, systems, or tools by non-exempt or hourly employees during their non-working hours. By accepting, you acknowledge that your use of Teams while off shift is not authorized and you will not be compensated. +'Message2' - Accessing this app outside working hours is voluntary. You won't be compensated for time spent on Teams. Refer to your employer's guidelines on using this app outside working hours. By accepting, you acknowledge that you understand the statement above. +'Message3' - You won't be compensated for time using Teams. By accepting, you acknowledge that you understand the statement above. +'Message4' - You're not authorized to use Teams while off shift. By accepting, you acknowledge your use of Teams is against your employer's policy. +'Message5' - Access to Teams is turned off during non-working hours. You will be able to access the app when your next shift starts. +'Message6' - Your employer does not authorize or approve of the use of its network, applications, systems, or tools by non-exempt or hourly employees during their non-working hours. Access to corporate resources are only allowed during approved working hours and should be recorded as hours worked in your employer's timekeeping system. +'Message7' - Your employer has turned off access to Teams during non-working hours. Refer to your employer's guidelines on using this app outside working hours. +'DefaultMessage' - You aren't authorized to use Microsoft Teams during non-working hours and will only be compensated for using it during approved working hours. +'CustomMessage' + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: DefaultMessage +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftNoticeMessageCustom +Provide a custom message. Must set ShiftNoticeMessageType to 'CustomMessage' to enforce this. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftNoticeFrequency +Frequency of warning dialog displayed when user opens Teams. Set one of Always, ShowOnceOnChange, Never. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: Always +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AccessGracePeriodMinutes +Indicates the grace period time in minutes between when the first shift starts, or last shift ends and when access is blocked. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableScheduleOwnerPermissions +Indicates whether a user can manage a Shifts schedule as a team member. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftspolicy) + +[New-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftspolicy) + +[Remove-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftspolicy) + +[Grant-CsTeamsShiftsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsshiftspolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsSipDevicesConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsSipDevicesConfiguration.md new file mode 100644 index 0000000000..2163f1d2f1 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsSipDevicesConfiguration.md @@ -0,0 +1,105 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Set-CsTeamsSipDevicesConfiguration +author: anmandav +ms.author: anmandav +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamssipdevicesconfiguration +schema: 2.0.0 +--- + +# Set-CsTeamsSipDevicesConfiguration + +## SYNOPSIS + +This cmdlet is used to manage the organization-wide Teams SIP devices configuration. + +## SYNTAX + +```powershell +Set-CsTeamsSipDevicesConfiguration [-BulkSignIn <String>] + [-Confirm] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet is used to manage the organization-wide Teams SIP devices configuration which contains settings that are applicable to SIP devices connected to Teams using Teams Sip Gateway. + +To execute the cmdlet, you need to hold a role within your organization such as Teams Administrator or Teams Communication Administrator. + +## EXAMPLES + +### Example 1 + +```powershell +Set-CsTeamsSipDevicesConfiguration -BulkSignIn "Enabled" +``` + +In this example, Bulk SignIn is set to Enabled across the organization. + +### Example 2 + +```powershell +Set-CsTeamsSipDevicesConfiguration -BulkSignIn "Disabled" +``` + +In this example, Bulk SignIn is set to Disabled across the organization. + +## PARAMETERS + +### -BulkSignIn +Indicates whether Bulk SingIn into Teams SIP devices is enabled or disabled for the common area phone (CAP) accounts across the organization. Possible values are **Enabled** and '**Disabled**. + +```yaml +Type: String +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsSipDevicesConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamssipdevicesconfiguration) diff --git a/teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliance.md b/teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliance.md new file mode 100644 index 0000000000..49fabb2ff1 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliance.md @@ -0,0 +1,135 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamssurvivablebranchappliance +title: Set-CsTeamsSurvivableBranchAppliance +schema: 2.0.0 +--- + +# Set-CsTeamsSurvivableBranchAppliance + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +```powershell +Set-CsTeamsSurvivableBranchAppliance [-Description <String>] [[-Identity] <String>] [-Site <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Description of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Site + +The TenantNetworkSite where the SBA is located. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliancePolicy.md b/teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliancePolicy.md new file mode 100644 index 0000000000..fe8cc3c54b --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliancePolicy.md @@ -0,0 +1,119 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamssurvivablebranchappliancepolicy +title: Set-CsTeamsSurvivableBranchAppliancePolicy +schema: 2.0.0 +--- + +# Set-CsTeamsSurvivableBranchAppliancePolicy + +## SYNOPSIS + +The Survivable Branch Appliance (SBA) Policy cmdlets facilitate the continuation of Teams Phone operations, allowing for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. These cmdlets are exclusively intended for Tenant Administrators and Session Border Controller (SBC) Vendors. In the absence of SBA configuration within a Tenant, the cmdlets will be inoperative. + +## SYNTAX + +```powershell +Set-CsTeamsSurvivableBranchAppliancePolicy [-BranchApplianceFqdns <Object>] [[-Identity] <String>] + [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## PARAMETERS + +### -BranchApplianceFqdns + +The FQDN of the SBA(s) in the site. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsTargetingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsTargetingPolicy.md new file mode 100644 index 0000000000..f1e5d3000d --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsTargetingPolicy.md @@ -0,0 +1,204 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamstargetingpolicy +title: Set-CsTeamsTargetingPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsTargetingPolicy + +## SYNOPSIS + +The CsTeamsTargetingPolicy cmdlets enable administrators to control the type of tags that users can create or the features that they can access in Teams. It also helps determine how tags deal with Teams members or guest users. + +## SYNTAX + +```powershell +Set-CsTeamsTargetingPolicy [-CustomTagsMode <String>] [-Description <String>] [[-Identity] <String>] + [-ManageTagsPermissionMode <String>] [-ShiftBackedTagsMode <String>] [-SuggestedPresetTags <String>] + [-TeamOwnersEditWhoCanManageTagsMode <String>] [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +The CsTeamsTargetingPolicy cmdlets enable administrators to control the type of tags that users can create or the features that they can access in Teams. It also helps determine how tags deal with Teams members or guest users. + +The Set-CsTeamsTargetingPolicy cmdlet allows administrators to update existing Tenant tag settings that can be assigned to particular teams to control Team features related to tags. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Set-CsTeamsTargetingPolicy -Identity NewTagPolicy -CustomTagsMode Enabled +``` + +The command shown in Example 1 uses the Set-CsTeamsTargetingPolicy cmdlet to update an existing Tenant tag setting with the CustomTagsMode Enabled. This flag will enable Teams users to create tags. + +## PARAMETERS + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomTagsMode + +Determine whether Teams users can create tags in team. Set this to Enabled to allow users to create new tags. Set this to Disabled to prohibit them from creating new tags. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Pass in a new description if that field needs to be updated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Name of the policy instance to be updated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManageTagsPermissionMode + +Determine whether team users can manage tag settings in Teams. Set this to EnabledTeamOwner to only allow Teams owners to manage tag settings in current Teams. Set this to EnabledTeamOwnerMember to allow Teams owners and Teams members to manage tag settings in current Teams. Set this to EnabledTeamOwnerMemberGuest to allow Teams owners, Teams members and guest users to manage tag settings in current Teams. Set this to MicrosoftDefault to user default setting in current Teams, which will be the same as EnabledTeamOwner. Set this to Disabled to prohibit all users from managing tag settings in current Teams. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For Internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShiftBackedTagsMode + +Determine whether Teams can have tags created by Shift App. Set this to Enabled to allow tags created by Shift App. Set this to Disabled to prohibit tags from Shift App. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamOwnersEditWhoCanManageTagsMode + +Determine whether Teams owners can change Tenant tag settings. Set this to Enabled to allow Teams owners to change Tenant tag settings for current Teams. Set this to Disabled to prohibit them from changing Tenant tag settings. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTargetingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamstargetingpolicy) +[Remove-CsTargetingPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamstargetingpolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsTemplatePermissionPolicy.md b/teams/teams-ps/teams/Set-CsTeamsTemplatePermissionPolicy.md new file mode 100644 index 0000000000..8aa49764df --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsTemplatePermissionPolicy.md @@ -0,0 +1,155 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: Microsoft.Teams.Policy.Administration.Cmdlets.Core +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamstemplatepermissionpolicy +title: Set-CsTeamsTemplatePermissionPolicy +author: yishuaihuang4 +ms.author: yishuaihuang +ms.reviewer: +manager: weiliu2 +schema: 2.0.0 +--- + +# Set-CsTeamsTemplatePermissionPolicy + +## SYNOPSIS +This cmdlet updates an existing TeamsTemplatePermissionPolicy. + +## SYNTAX + +``` +Set-CsTeamsTemplatePermissionPolicy + [-HiddenTemplates <System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.HiddenTemplate]>] + [-Description <String>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Updates any of the properties of an existing instance of the TeamsTemplatePermissionPolicy. + +## EXAMPLES + +### Example 1 +```powershell +PS >$manageEventTemplate = New-CsTeamsHiddenTemplate -Id com.microsoft.teams.template.ManageAnEvent +PS >$manageProjectTemplate = New-CsTeamsHiddenTemplate -Id com.microsoft.teams.template.ManageAProject +PS >$HiddenList = @($manageProjectTemplate, $manageEventTemplate) +PS >Set-CsTeamsTemplatePermissionPolicy -Identity Global -HiddenTemplates $HiddenList +``` + +Updates the hidden templates array. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Adds a new description if that field needs to be updated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HiddenTemplates +The updated list of Teams template IDs to hide. +The HiddenTemplate objects are created with [New-CsTeamsHiddenTemplate](https://learn.microsoft.com/powershell/module/teams/new-csteamshiddentemplate). + +```yaml +Type: System.Management.Automation.PSListModifier`1[Microsoft.Teams.Policy.Administration.Cmdlets.Core.HiddenTemplate] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the policy instance to be updated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamstemplatepermissionpolicy) + +[New-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamstemplatepermissionpolicy) + +[Remove-CsTeamsTemplatePermissionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamstemplatepermissionpolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsTranslationRule.md b/teams/teams-ps/teams/Set-CsTeamsTranslationRule.md new file mode 100644 index 0000000000..64bcdc16c5 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsTranslationRule.md @@ -0,0 +1,145 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamstranslationrule +applicable: Microsoft Teams +title: Set-CsTeamsTranslationRule +schema: 2.0.0 +manager: nmurav +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsTeamsTranslationRule + +## SYNOPSIS +Cmdlet to modify an existing normalization rule. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTeamsTranslationRule [[-Identity] <string>] [-Description <string>] [-Pattern <string>] [-Translation <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +You can use this cmdlet to modify an existing number manipulation rule. The rule can be used, for example, in the settings of your SBC (Set-CsOnlinePSTNGateway) to convert a callee or caller number to a desired format before entering or leaving Microsoft Phone System + +## EXAMPLES + +### Example 1 +```powershell +Set-CsTeamsTranslationRule -Identity StripE164SeattleAreaCode -Pattern ^+12065555(\d{3})$ -Translation $1 +``` + +This example modifies the rule that initially configured to strip +1206555 from any E.164 ten digits number. For example, +12065555555 translated to 5555 to a new pattern. Modified rule now only applies to three digit number (initially to four digits number) and adds one more number in prefix (+120655555 instead of +1206555) + +## PARAMETERS + +### -Identity +Identifier of the rule. This parameter is required and later used to assign the rule to the Inbound or Outbound Trunk Normalization policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +A friendly description of the normalization rule. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern +A regular expression that caller or callee number must match in order for this rule to be applied. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Translation +The regular expression pattern that will be applied to the number to convert it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[New-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/new-csteamstranslationrule) + +[Get-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/get-csteamstranslationrule) + +[Test-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/test-csteamstranslationrule) + +[Remove-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/remove-csteamstranslationrule) diff --git a/teams/teams-ps/teams/Set-CsTeamsUnassignedNumberTreatment.md b/teams/teams-ps/teams/Set-CsTeamsUnassignedNumberTreatment.md new file mode 100644 index 0000000000..75ea8483a8 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsUnassignedNumberTreatment.md @@ -0,0 +1,166 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsunassignednumbertreatment +applicable: Microsoft Teams +title: Set-CsTeamsUnassignedNumberTreatment +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Set-CsTeamsUnassignedNumberTreatment + +## SYNOPSIS +Changes a treatment for how calls to an unassigned number range should be routed. The call can be routed to a user, an application or to an announcement service where a custom message will be played to the caller. + +## SYNTAX + +``` +Set-CsTeamsUnassignedNumberTreatment [[-Identity] <string>] [-Description <string>] [-Pattern <string>] [-Target <string>] [-TargetType <string>] + [-TreatmentPriority <int>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet changes a treatment for how calls to an unassigned number range should be routed. + +## EXAMPLES + +### Example 1 +```powershell +$RAObjectId = (Get-CsOnlineApplicationInstance -Identity aa2@contoso.com).ObjectId +Set-CsTeamsUnassignedNumberTreatment -Identity MainAA -Target $RAObjectId +``` +This example changes the treatment MainAA to route the calls to the resource account aa2@contoso.com. + +### Example 2 +```powershell +$UserObjectId = (Get-CsOnlineUser -Identity user2@contoso.com).Identity +Set-CsTeamsUnassignedNumberTreatment -Identity User2PSTN -TargetType User -Target $UserObjectId +``` +This example changes the treatment User2PSTN to route the calls to the user user2@contoso.com. + +## PARAMETERS + +### -Description +Free format description of this treatment. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Id of the specific treatment. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Pattern +A regular expression that the called number must match in order for the treatment to take effect. It is best practice to start the regular expression with the hat character and end it with the dollar character. +You can use various regular expression test sites on the Internet to validate the expression. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Target +The identity of the destination the call should be routed to. Depending on the TargetType it should either be the ObjectId of the user or application instance/resource account or the AudioFileId of the uploaded audio file. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetType +The type of target used for the treatment. Allowed values are User, ResourceAccount and Announcement. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TreatmentPriority +The priority of the treatment. Used to distinguish identical patterns. The lower the priority the higher preference. The priority needs to be unique. + +```yaml +Type: System.Integer +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Object + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PS module 2.5.1 or later. + +Both inbound calls to Microsoft Teams and outbound calls from Microsoft Teams will have the called number checked against the unassigned number range. + +To route calls to unassigned Microsoft Calling Plan subscriber numbers, your tenant needs to have available Communications Credits. + +To route calls to unassigned Microsoft Calling Plan service numbers, your tenant needs to have at least one Microsoft Teams Phone Resource Account license. + +If a specified pattern/range contains phone numbers that are assigned to a user or resource account in the tenant, calls to these phone numbers will be routed to +the appropriate target and not routed to the specified unassigned number treatment. There are no other checks of the numbers in the range. If the range contains +a valid external phone number, outbound calls from Microsoft Teams to that phone number will be routed according to the treatment. + +## RELATED LINKS +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) + +[Get-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/get-csteamsunassignednumbertreatment) + +[Remove-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/remove-csteamsunassignednumbertreatment) + +[New-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/new-csteamsunassignednumbertreatment) + +[Test-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/test-csteamsunassignednumbertreatment) diff --git a/teams/teams-ps/teams/Set-CsTeamsUpdateManagementPolicy.md b/teams/teams-ps/teams/Set-CsTeamsUpdateManagementPolicy.md new file mode 100644 index 0000000000..4567271d50 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsUpdateManagementPolicy.md @@ -0,0 +1,312 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsupdatemanagementpolicy +applicable: Microsoft Teams +title: Set-CsTeamsUpdateManagementPolicy +schema: 2.0.0 +author: vargasj-ms +ms.author: vargasj +manager: gnamun +--- + +# Set-CsTeamsUpdateManagementPolicy + +## SYNOPSIS +Use this cmdlet to modify a Teams Update Management policy. + +## SYNTAX + +```powershell +Set-CsTeamsUpdateManagementPolicy + [-DisabledInProductMessages <System.Management.Automation.PSListModifier`1[System.String]>] + [-Description <String>] [-AllowManagedUpdates <Boolean>] [-AllowPreview <Boolean>] [-UpdateDayOfWeek <Int64>] + [-UpdateTime <String>] [-UpdateTimeOfDay <DateTime>] [-AllowPublicPreview <String>] + [-AllowPrivatePreview <AllowPrivatePreview>] [-UseNewTeamsClient <String>] + [-BlockLegacyAuthorization <Boolean>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The Teams Update Management Policy allows admins to specify if a given user is enabled to preview features in Teams. + + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsUpdateManagementPolicy -Identity "Campaign Policy" -DisabledInProductMessages @("91382d07-8b89-444c-bbcb-cfe43133af33") +``` + +In this example, the policy "Campaign Policy" is modified, disabling the in-product messages with the category "What's New". + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisabledInProductMessages +List of IDs of the categories of the in-product messages that will be disabled. You can choose one of the categories from this table: + +| ID | Campaign Category | +| -- | -- | +| 91382d07-8b89-444c-bbcb-cfe43133af33 | What's New | +| edf2633e-9827-44de-b34c-8b8b9717e84c | Conferences | + +```yaml +Type: System.Management.Automation.PSListModifier`1[System.String] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowManagedUpdates + +Enables/Disables managed updates for the user. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPreview + +Indicates whether all feature flags are switched on or off. Can be set only when AllowManagedUpdates is set to True. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPrivatePreview + +This setting will allow admins to allow users in their tenant to opt in to Private Preview. + If it is Disabled, then users will not be able to opt in and the ring switcher UI will be hidden in the Desktop Client. + If it is Enabled, then users will be able to opt in and the ring switcher UI will be available in the Desktop Client. + If it is Forced, then users will be switched to Private Preview. + +```yaml +Type: AllowPrivatePreview +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowPublicPreview + +This setting will allow admins to allow users in their tenant to opt in to Public Preview. + If it is Disabled, then users will not be able to opt in and the ring switcher UI will be hidden in the Desktop Client. + If it is Enabled, then users will be able to opt in and the ring switcher UI will be available in the Desktop Client. + If it is FollowOfficePreview, then users will not be able to opt in and instead follow their Office channel, and be switched to Public Preview if their Office channel is CC (Preview). The ring switcher UI will be hidden in the Desktop Client. This is not applicable to the Web Client. + If it is Forced, then users will be switched to Public Preview. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthorization + +This setting will force Teams clients to enforce session revocation for core Messaging and Calling/Meeting scenarios. + If turned ON, session revocation will be enforced for calls, chats and meetings for opted-in users. + If turned OFF, session revocation will not be enforced for calls, chats and meetings for opted-in users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Enables administrators to provide explanatory text about the policy. For example, the Description might indicate the users the policy should be assigned to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateDayOfWeek + + Machine local day. 0-6(Sun-Sat) Can be set only when AllowManagedUpdates is set to True. + +```yaml +Type: Int64 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateTime + +Machine local time in HH:MM format. Can be set only when AllowManagedUpdates is set to True. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UpdateTimeOfDay + +Machine local time. Can be set only when AllowManagedUpdates is set to True + +```yaml +Type: DateTime +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UseNewTeamsClient + +This setting will enable admins to show or hide which users see the Teams preview toggle on the current Teams client. + If it is AdminDisabled, then users will not be able to see the Teams preview toggle in the Desktop Client. + If it is UserChoice, then users will be able to see the Teams preview toggle in the Desktop Client. + If it is MicrosoftChoice, then Microsoft will configure/ manage whether user sees or does not see this feature if the admin has set nothing. + If it is NewTeamsAsDefault, then New Teams will be default for users, and they will be able to switch back to Classic Teams via the toggle in the Desktop Client. + If it is NewTeamsOnly, then New Teams will be the only Teams client installed for users. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses any confirmation prompts that would otherwise be displayed before making changes and suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The unique identifier of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsUpgradeConfiguration.md b/teams/teams-ps/teams/Set-CsTeamsUpgradeConfiguration.md new file mode 100644 index 0000000000..001f0dbe19 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsUpgradeConfiguration.md @@ -0,0 +1,196 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsupgradeconfiguration +applicable: Microsoft Teams +title: Set-CsTeamsUpgradeConfiguration +schema: 2.0.0 +--- + +# Set-CsTeamsUpgradeConfiguration + +## SYNOPSIS +Administrators can use Set-CsTeamsUpgradeConfiguration to manage certain aspects of client behavior for users being upgraded from Skype for Business to Teams. TeamsUpgradeConfiguration should be used in conjunction with TeamsUpgradePolicy. The settings in TeamsUpgradeConfiguration allow administrators to configure whether users subject to upgrade and who are running on Windows clients should automatically download Teams. It allows administrators to determine which application end users should use to join Skype for Business meetings. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsTeamsUpgradeConfiguration [-Tenant <Guid>] [-DownloadTeams <Boolean>] [-SfBMeetingJoinUx <String>] [-BlockLegacyAuthorization <Boolean>] + [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +```powershell +Set-CsTeamsUpgradeConfiguration [-Tenant <Guid>] [-DownloadTeams <Boolean>] [-SfBMeetingJoinUx <String>] [-BlockLegacyAuthorization <Boolean>] + [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +TeamsUpgradeConfiguration is used in conjunction with TeamsUpgradePolicy. The settings in TeamsUpgradeConfiguration allow administrators to configure whether users subject to upgrade and who are running on Windows clients should automatically download Teams. It allows administrators to determine which application end users should use to join Skype for Business meetings. + +The DownloadTeams property allows admins to control whether the Skype for Business client should automatically download Teams in the background. This setting is only honored on Windows clients, and only for certain values of the user's TeamsUpgradePolicy. If NotifySfbUser=true or if Mode=TeamsOnly in TeamsUpgradePolicy, this setting is honored. Otherwise it is ignored. + +The SfBMeetingJoinUx property allows admins to specify which app is used to join Skype for Business meetings, even after the user has been upgraded to Teams. Allowed values are: SkypeMeetingsApp and NativeLimitedClient. "NativeLimitedClient" means the existing Skype for Business rich client will be used, but since the user is upgraded, only meeting functionality is available. Calling and Messaging are done via Teams. "SkypeMeetingsApp" means use the web-downloadable app. This setting can be useful for organizations that have upgraded to Teams and no longer want to install Skype for Business on their users' computers. + +## EXAMPLES + +### Example 1 +``` +PS C:\> Set-CsTeamsUpgradeConfiguration -DownloadTeams $true -SfBMeetingJoinUx SkypeMeetingsApp +``` + +The above cmdlet specifies that users subject to upgrade should download Teams in the background, and that they should use the Skype For Business Meetings app to join Skype for Business meetings. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DownloadTeams +The DownloadTeams property allows admins to control whether the Skype for Business client should automatically download Teams in the background. This Boolean setting is only honored on Windows clients, and only for certain values of the user's TeamsUpgradePolicy. If NotifySfbUser=true or if Mode=TeamsOnly in TeamsUpgradePolicy, this setting is honored. Otherwise it is ignored. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` +### -SfBMeetingJoinUx +The SfBMeetingJoinUx property allows admins to specify which app is used to join Skype for Business meetings, even after the user has been upgraded to Teams. Allowed values are: "SkypeMeetingsApp" and "NativeLimitedClient". "NativeLimitedClient" means the existing Skype for Business rich client will be used, but since the user is upgraded, only meeting functionality is available. Calling and Messaging are done via Teams. "SkypeMeetingsApp" means use the web-downloadable app. This setting can be useful for organizations that have upgraded to Teams and no longer want to install Skype for Business on their users' computers. + +```yaml +Type: string +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: NativeLimitedClient +Accept pipeline input: False +Accept wildcard characters: False +``` +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +For internal use only. + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +For internal use only. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockLegacyAuthorization +This setting will force Teams clients to enforce session revocation for core Messaging and Calling/Meeting scenarios. +If turned ON, session revocation will be enforced for calls, chats and meetings for opted-in users. +If turned OFF, session revocation will not be enforced for calls, chats and meetings for opted-in users + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES +These settings are only honored by newer versions of Skype for Business clients. + +## RELATED LINKS + +[Get-CsTeamsUpgradeConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsupgradeconfiguration) + +[Get-CsTeamsUpgradePolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsupgradepolicy) + +[Grant-CsTeamsUpgradePolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsupgradepolicy) + +[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://learn.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype) diff --git a/teams/teams-ps/teams/Set-CsTeamsVdiPolicy.md b/teams/teams-ps/teams/Set-CsTeamsVdiPolicy.md new file mode 100644 index 0000000000..5c21d8c52c --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsVdiPolicy.md @@ -0,0 +1,165 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-cteamsvdipolicy +title: Set-CsTeamsVdiPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsVdiPolicy + +## SYNOPSIS +The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +## SYNTAX + +```powershell +Set-CsTeamsVdiPolicy [-DisableCallsAndMeetings <Boolean>] [-DisableAudioVideoInCallsAndMeetings <Boolean>] + [-VDI2Optimization <String>] [-Identity] <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The CsTeamsVdiPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting specifically on an unoptimized VDI environment. It also controls whether a user can be in VDI 2.0 optimization mode. + +The SetCsTeamsVdiPolicy cmdlet allows administrators to update existing Vdi policies that can be assigned to particular users to control Teams features related to Vdi. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTeamsVdiPolicy -Identity RestrictedUserPolicy -VDI2Optimization "Disabled" +``` + +The command shown in Example 1 uses the Set-CsTeamsVdiPolicy cmdlet to update an existing vdi policy with the Identity RestrictedUserPolicy. This policy will use all the existing values except one: VDI2Optimization; in this example, users with this policy can not be in VDI 2.0 optimized. + +### Example 2 +```powershell +PS C:\> Set-CsTeamsVdiPolicy -Identity OnlyOptimizedPolicy -DisableAudioVideoInCallsAndMeetings $True -DisableCallsAndMeetings $True +``` + +In Example 2, the Set-CsTeamsVdiPolicy cmdlet is used to update a Vdi policy with the Identity OnlyOptimizedPolicy. In this example two different property values are configured: DisableAudioVideoInCallsAndMeetings is set to True and DisableCallsAndMeetings is set to True. All other policy properties will use the existing values. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableAudioVideoInCallsAndMeetings +Determines whether a user on a non-optimized Vdi environment can hold person-to-person audio and video calls. Set this to TRUE to disallow a non-optimized user to hold person-to-person audio and video calls. Set this to FALSE to allow a non-optimized user to hold person-to-person audio and video calls. A user can still join a meeting and share screen from chat and join a meeting and share a screen and move their audio to a phone. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisableCallsAndMeetings +Determines whether a user on a non-optimized Vdi environment can make all types of calls. Set this to TRUE to disallow a non-optimized user to make calls, join meetings, and screen share from chat. Set this to FALSE to allow a non-optimized user to make calls, join meetings, and screen share from chat. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specify the name of the policy being created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -VDI2Optimization +Determines whether a user can be VDI 2.0 optimized. +* Enabled - allow a user to be VDI 2.0 optimized. +* Disabled - disallow a user to be VDI 2.0 optimized. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTeamsVirtualAppointmentsPolicy.md b/teams/teams-ps/teams/Set-CsTeamsVirtualAppointmentsPolicy.md new file mode 100644 index 0000000000..363ba6ac2f --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsVirtualAppointmentsPolicy.md @@ -0,0 +1,135 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsvirtualappointmentspolicy +title: Set-CsTeamsVirtualAppointmentsPolicy +schema: 2.0.0 +author: emmanuelrocha001 +ms.author: erocha +manager: sonaggarwal +--- + +# Set-CsTeamsVirtualAppointmentsPolicy + +## SYNOPSIS +This cmdlet is used to update an instance of TeamsVirtualAppointmentsPolicy. + +## SYNTAX + +``` +Set-CsTeamsVirtualAppointmentsPolicy [-EnableSmsNotifications <Boolean>] [-Identity] <String> [-Force] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Updates any of the properties of an existing instance of TeamsVirtualAppointmentsPolicy. + +## EXAMPLES + +### Example 1 + +```powershell +PS> Set-CsTeamsVirtualAppointmentsPolicy -Identity ExistingPolicyInstance -EnableSmsNotifications $false +``` + +Updates the `EnableSmsNotifications` field of a given policy. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableSmsNotifications +This property specifies whether your users can choose to send SMS text notifications to external guests in meetings that they schedule using a virtual appointment template meeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the new policy instance to be created. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvirtualappointmentspolicy) + +[New-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvirtualappointmentspolicy) + +[Remove-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvirtualappointmentspolicy) + +[Grant-CsTeamsVirtualAppointmentsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvirtualappointmentspolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsVoiceApplicationsPolicy.md b/teams/teams-ps/teams/Set-CsTeamsVoiceApplicationsPolicy.md new file mode 100644 index 0000000000..e39d07bd9a --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsVoiceApplicationsPolicy.md @@ -0,0 +1,751 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsvoiceapplicationspolicy +title: Set-CsTeamsVoiceApplicationsPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsVoiceApplicationsPolicy + +## SYNOPSIS + +Modifies an existing Teams voice applications policy. + +## SYNTAX + +``` +Set-CsTeamsVoiceApplicationsPolicy + [-AllowAutoAttendantBusinessHoursGreetingChange <Boolean>] + [-AllowAutoAttendantAfterHoursGreetingChange <Boolean>] + [-AllowAutoAttendantHolidayGreetingChange <Boolean>] + [-AllowAutoAttendantBusinessHoursChange <Boolean>] + [-AllowAutoAttendantHolidaysChange <Boolean>] + [-AllowAutoAttendantTimeZoneChange <Boolean>] + [-AllowAutoAttendantLanguageChange <Boolean>] + [-AllowAutoAttendantBusinessHoursRoutingChange <Boolean>] + [-AllowAutoAttendantAfterHoursRoutingChange <Boolean>] + [-AllowAutoAttendantHolidayRoutingChange <Boolean>] + + [-AllowCallQueueWelcomeGreetingChange <Boolean>] + [-AllowCallQueueMusicOnHoldChange <Boolean>] + [-AllowCallQueueOverflowSharedVoicemailGreetingChange <Boolean>] + [-AllowCallQueueTimeoutSharedVoicemailGreetingChange <Boolean>] + [-AllowCallQueueNoAgentSharedVoicemailGreetingChange <bool>] + [-AllowCallQueueLanguageChange <Boolean>] + [-AllowCallQueueMembershipChange <Boolean>] + [-AllowCallQueueConferenceModeChange <Boolean>] + [-AllowCallQueueRoutingMethodChange <Boolean>] + [-AllowCallQueuePresenceBasedRoutingChange <Boolean>] + [-AllowCallQueueOptOutChange <Boolean>] + [-AllowCallQueueOverflowRoutingChange <Boolean>] + [-AllowCallQueueTimeoutRoutingChange <Boolean>] + [-AllowCallQueueNoAgentsRoutingChange <Boolean>] + [-AllowCallQueueAgentOptChange <Boolean>] + + [-CallQueueAgentMonitorMode <Disabled | Monitor | Whisper | Barge | Takeover>] + [-CallQueueAgentMonitorNotificationMode <Disabled | Agent>] + + [-RealTimeAutoAttendantMetricsPermission <string>] + [-RealTimeCallQueueMetricsPermission <string>] + [-RealTimeAgentMetricsPermission <string>] + + [-HistoricalAutoAttendantMetricsPermission <string>] + [-HistoricalCallQueueMetricsPermission <string>] + [-HistoricalAgentMetricsPermission <string>] + + [[-Identity] <String>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION + +`TeamsVoiceApplicationsPolicy` is used for **Supervisor Delegated Administration** which allows admins in the organization to permit certain users to make changes to auto attendant and call queue configurations. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +Set-CsTeamsVoiceApplicationsPolicy -Identity "SDA-CQ-OverflowGreeting" -AllowCallQueueOverflowSharedVoicemailGreetingChange $true +``` + +The command shown in Example 1 sets allowing CQ overflow shared voicemail greeting changes to per-user Teams voice applications policy. + +## PARAMETERS + +### -AllowAutoAttendantBusinessHoursGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's business hours greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's business hours greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantAfterHoursGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's after-hours greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's after-hours greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantHolidayGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's holiday greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's holiday greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantBusinessHoursChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's business hours schedule. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's business hours schedule. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantHolidaysChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's holiday schedules. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's holiday schedules. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantTimeZoneChange + +_This feature is not currently available to authorized users._ + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's time zone. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's time zone. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantLanguageChange + +_This feature is not currently available to authorized users._ + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's language. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's language. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantBusinessHoursRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's business hours call flow. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's business hours call flow. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantAfterHoursRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's after-hours call flow. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's after-hours call flow. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowAutoAttendantHolidayRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the auto attendant's holiday call flows. When set to `False` (the default value), users affected by the policy won't be allowed to change the auto attendant's holiday call flows. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueWelcomeGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's welcome greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's welcome greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueMusicOnHoldChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's music on hold information. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's music on hold. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueOverflowSharedVoicemailGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's overflow shared voicemail greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's overflow shared voicemail greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueTimeoutSharedVoicemailGreetingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's timeout shared voicemail greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's timeout shared voicemail greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueNoAgentSharedVoicemailGreetingChange + +_This feature is not currently available to authorized users._ + +When set to `True`, users affected by the policy will be allowed to change the call queue's no agent shared voicemail greeting. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's no agent shared voicemail greeting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueLanguageChange + +_This feature is not currently available to authorized users._ + +When set to `True`, users affected by the policy will be allowed to change the call queue's language. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's language. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueMembershipChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's users. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's users. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueConferenceModeChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's conference mode. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's conference mode. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueRoutingMethodChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's routing method. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's routing method. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueuePresenceBasedRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's presence-based routing option. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's presence-based routing option. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueOptOutChange + +When set to `True`, users affected by the policy will be allowed to change the call queue opt-out setting that allows agents to opt out of receiving calls. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue opt-out setting. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueOverflowRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's overflow handling properties. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's overflow handling properties. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueTimeoutRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's timeout handling properties. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's timeout handling properties. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueNoAgentsRoutingChange + +When set to `True`, users affected by the policy will be allowed to change the call queue's no-agent handling properties. When set to `False` (the default value), users affected by the policy won't be allowed to change the call queue's no-agent handling properties. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallQueueAgentOptChange + +When set to `True`, users affected by the policy will be allowed to change an agent's opt-in status in the call queue. When set to `False` (the default value), users affected by the policy won't be allowed to change an agent's opt-in status in the call queue. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallQueueAgentMonitorMode + +PARAMVALUE: Disabled | Monitor | Whisper | Barge | Takeover + +When set to `Disabled` (the default value), users affected by the policy won't be allowed to monitor call sessions. + +When set to `Monitor`, users affected by the policy will be allowed to monitor and listen to call sessions. + +When set to `Whisper`, users affected by the policy will be allowed to monitor call sessions and whisper to an agent in the call. + +When set to `Barge`, users affected by the policy will be allowed to monitor call sessions, whisper to an agent in the call, or join the call session. + +When set to `Takeover`, users affected by the policy will be allowed to monitor call sessions, whisper to an agent in the call, join the call session, or take over the call from an agent. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallQueueAgentMonitorNotificationMode + +PARAMVALUE: Disabled | Agent + +When set to `Disabled` (the default value), users affected by the policy won't be allowed to monitor agents during call sessions. + +When set to `Agent`, users affected by the policy will be allowed to monitor agents during call sessions. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Disabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeAutoAttendantMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive real-time metrics for auto attendants. + +When set to `AuthorizedOnly`, users affected by the policy will receive real-time metrics for auto attendants they are authorized for. + +> [!IMPORTANT] +> The `All` option is no longer supported. The parameter will be accepted and saved however any user assigned a policy with *RealTimeAutoAttendantMetricsPermission* set to `All` will not be able to access real-time metrics. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeCallQueueMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive real-time metrics for call queues. + +When set to `AuthorizedOnly`, users affected by the policy will receive real-time metrics for call queues they are authorized for. + +> [!IMPORTANT] +> The `All` option is no longer supported. The parameter will be accepted and saved however any user assigned a policy with *RealTimeCallQueueMetricsPermission* set to `All` will not be able to access real-time metrics. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RealTimeAgentMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive real-time metrics for agents. + +When set to `AuthorizedOnly`, users affected by the policy will receive real-time metrics for agents who are members in the call queues they are authorized for. + +> [!IMPORTANT] +> The `All` option is no longer supported. The parameter will be accepted and saved however any user assigned a policy with *RealTimeAgentMetricsPermission* set to `All` will not be able to access real-time metrics. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HistoricalAutoAttendantMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive historical metrics for auto attendants. + +When set to `AuthorizedOnly`, users affected by the policy will receive historical metrics for auto attendants they are authorized for. + +When set to `All`, users affected by the policy will receive historical metrics for all auto attendants in the organization. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HistoricalCallQueueMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive historical metrics for call queues. + +When set to `AuthorizedOnly`, users affected by the policy will receive historical metrics for call queues they are authorized for. + +When set to `All`, users affected by the policy will receive historical metrics for all call queues in the organization. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HistoricalAgentMetricsPermission + +PARAMVALUE: Disabled | AuthorizedOnly | All + +When set to `Disabled` (the default value), users affected by the policy won't receive historical metrics for agents. + +When set to `AuthorizedOnly`, users affected by the policy will receive historical metrics for agents who are members in the call queues they are authorized for. + +When set to `All`, users affected by the policy will receive historical metrics for all agents in all call queues in the organization. + +```yaml +Type: Object +Parameter Sets: Dual +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Unique identifier assigned to the policy when it was created. Teams voice applications policies can be assigned at the global scope or the per-user scope. To refer to the global instance, use this syntax: + +-Identity global + +To refer to a per-user policy, use syntax similar to this: + +-Identity "SDA-Allow-All" + +If you do not specify an Identity, then the `Set-CsTeamsVoiceApplicationsPolicy` cmdlet will modify the global policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsvoiceapplicationspolicy) + +[Grant-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsvoiceapplicationspolicy) + +[Remove-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsvoiceapplicationspolicy) + +[New-CsTeamsVoiceApplicationsPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsvoiceapplicationspolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsWorkLoadPolicy.md b/teams/teams-ps/teams/Set-CsTeamsWorkLoadPolicy.md new file mode 100644 index 0000000000..1db49482a3 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsWorkLoadPolicy.md @@ -0,0 +1,239 @@ +--- +external help file: MicrosoftTeams-help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsworkloadpolicy +title: Set-CsTeamsWorkLoadPolicy +schema: 2.0.0 +--- + +# Set-CsTeamsWorkLoadPolicy + +## SYNOPSIS + +This cmdlet sets the Teams Workload Policy value for current tenant. + +## SYNTAX + +```powershell +Set-CsTeamsWorkLoadPolicy [-AllowCalling <Boolean>] [-AllowCallingPinned <Boolean>] [-AllowMeeting <Boolean>] + [-AllowMeetingPinned <Boolean>] [-AllowMessaging <Boolean>] [-AllowMessagingPinned <Boolean>] + [-Description <String>] [[-Identity] <String>] [-MsftInternalProcessingMode <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION + +The TeamsWorkLoadPolicy determines the workloads like meeting, messaging, calling that are enabled and/or pinned for the user. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Set-CsTeamsWorkLoadPolicy -Identity Global -AllowCalling Disabled +``` + +This sets the Teams Workload Policy Global value of AllowCalling to disabled. + +## PARAMETERS + +### -AllowCalling + +Determines if calling workload is enabled in the Teams App. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowCallingPinned + +Determines if calling workload is pinned to the teams navigation bar. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeeting + +Determines if meetings workload is enabled in the Teams App. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMeetingPinned + +Determines if meetings workload is pinned to the teams navigation bar. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMessaging + +Determines if messaging workload is enabled in the Teams App. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowMessagingPinned + +Determines if messaging workload is pinned to the teams navigation bar. Possible values are True and False. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +The description of the policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +The identity of the Teams Work Load Policy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MsftInternalProcessingMode + +For internal use only. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Remove-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworkloadpolicy) + +[Get-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworkloadpolicy) + +[New-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworkloadpolicy) + +[Grant-CsTeamsWorkLoadPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworkloadpolicy) diff --git a/teams/teams-ps/teams/Set-CsTeamsWorkLocationDetectionPolicy.md b/teams/teams-ps/teams/Set-CsTeamsWorkLocationDetectionPolicy.md new file mode 100644 index 0000000000..176485db17 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTeamsWorkLocationDetectionPolicy.md @@ -0,0 +1,136 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsworklocationdetectionpolicy +title: Set-CsTeamsWorkLocationDetectionPolicy +schema: 2.0.0 +author: artemiykozlov +ms.author: arkozlov +manager: prashibadkur +--- + +# Set-CsTeamsWorkLocationDetectionPolicy + +## SYNOPSIS +This cmdlet is used to update an instance of TeamsWorkLocationDetectionPolicy. + +## SYNTAX + +``` +Set-CsTeamsWorkLocationDetectionPolicy [-EnableWorkLocationDetection <Boolean>] [-Identity] <String> [-Force] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Updates any of the properties of an existing instance of TeamsWorkLocationDetectionPolicy. + +## EXAMPLES + +### Example 1 + +```powershell +PS> Set-CsTeamsWorkLocationDetectionPolicy -Identity ExistingPolicyInstance -EnableWorkLocationDetection $true +``` + +Updates the `EnableWorkLocationDetection` field of a given policy. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableWorkLocationDetection +This setting allows your organization to collect the work location of users when they connect, interact, or are detected near your organization's networks and devices. It also captures the geographic location information users share from personal and mobile devices. +This gives users the ability to consent to the use of this location data to set their current work location.Microsoft collects this information to provide users with a consistent location-based experience and to improve the hybrid work experience in Microsoft 365 according to the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Name of the new policy instance to be updated. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Void + +## NOTES + +## RELATED LINKS +[Get-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsworklocationdetectionpolicy) + +[New-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/new-csteamsworklocationdetectionpolicy) + +[Remove-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/remove-csteamsworklocationdetectionpolicy) + +[Grant-CsTeamsWorkLocationDetectionPolicy](https://learn.microsoft.com/powershell/module/teams/grant-csteamsworklocationdetectionpolicy) diff --git a/teams/teams-ps/teams/Set-CsTenantBlockedCallingNumbers.md b/teams/teams-ps/teams/Set-CsTenantBlockedCallingNumbers.md new file mode 100644 index 0000000000..616604a4f9 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTenantBlockedCallingNumbers.md @@ -0,0 +1,247 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenantblockedcallingnumbers +applicable: Microsoft Teams +title: Set-CsTenantBlockedCallingNumbers +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +manager: roykuntz +--- + +# Set-CsTenantBlockedCallingNumbers + +## SYNOPSIS +Use the Set-CsTenantBlockedCallingNumbers cmdlet to set tenant blocked calling numbers setting. + +## SYNTAX + +``` +Set-CsTenantBlockedCallingNumbers [[-Identity] <String>] + [-Confirm] + [-Enabled <Object>] + [-Force] + [-InboundBlockedNumberPatterns <Object>] + [-InboundExemptNumberPatterns <Object>] + [-Instance <Object>] + [-Name <Object>] + [-Tenant <Object>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Microsoft Direct Routing, Operator Connect and Calling Plans supports blocking of inbound calls from the public switched telephone network (PSTN). This feature allows a tenant-global list of number patterns to be defined so that the caller ID of every incoming PSTN call to the tenant can be checked against the list for a match. If a match is made, an incoming call is rejected. + +The tenant blocked calling numbers includes a list of inbound blocked number patterns. Number patterns are managed through the CsInboundBlockedNumberPattern commands New, Get, Set, and Remove. You can manage a given pattern by using these cmdlets, including the ability to toggle the activation of a given pattern. + +The tenant blocked calling numbers also includes a list of number patterns exempt from call blocking. Exempt number patterns are managed through the CsInboundExemptNumberPattern commands New, Get, Set, and Remove. You can manage a given pattern by using these cmdlets, including the ability to toggle the activation of a given pattern. + +You can test your number blocking by using the Test-CsInboundBlockedNumberPattern command. + +The scope of tenant blocked calling numbers is global across the given tenant. This command-let can also turn on/off the blocked calling numbers setting at the tenant level. + +To get the current tenant blocked calling numbers setting, use Get-CsTenantBlockedCallingNumbers + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsTenantBlockedCallingNumbers -Enabled $false +``` + +This example turns off the tenant blocked calling numbers setting. No inbound number will be blocked from this feature. + +### -------------------------- Example 2 -------------------------- +``` +Set-CsTenantBlockedCallingNumbers -Enabled $true +``` + +This example turns on the tenant blocked calling numbers setting. Inbound calls will be blocked based on the list of blocked number patterns. + +### -------------------------- Example 3 -------------------------- +``` +Set-CsTenantBlockedCallingNumbers -Name "MyCustomBlockedCallingNumbersName" +``` + +This example renames the current blocked calling numbers with "MyCustomBlockedCallingNumbersName". No change is made besides the Name field change. + +### -------------------------- Example 4 -------------------------- +``` +Set-CsTenantBlockedCallingNumbers -InboundBlockedNumberPatterns @((New-CsInboundBlockedNumberPattern -Name "AnonymousBlockedPattern" -Enabled $true -Pattern "^(?!)Anonymous")) +``` + +This example sets the tenant blocked calling numbers with a new list of inbound blocked number patterns. There is a new InboundBlockedNumberPattern being created. The pattern name is "AnonymousBlockedPattern". The pattern is turned on. The pattern is a normalization rule which contains "Anonymous". + +Note that if the current InboundBlockedNumberPatterns already contains a list of patterns while a new pattern needs to be created, this example will wipe out the existing patterns and only add the new one. Please save the current InboundBlockedNumberPatterns list before adding new patterns. + +## PARAMETERS + +### -Identity +The Identity parameter is a unique identifier which identifies the TenantBlockedCallingNumbers to set. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +The switch to turn on or turn off the blocked calling numbers setting. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch overrides the confirmation prompt displayed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundBlockedNumberPatterns +The InboundBlockedNumberPatterns parameter contains the list of InboundBlockedNumberPatterns. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InboundExemptNumberPatterns +The InboundExemptNumberPatterns parameter contains the list of InboundExemptNumberPatterns. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +This parameter allows you to provide a name to the TenantBlockedCallingNumbers setting. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[Get-CsTenantBlockedCallingNumbers](https://learn.microsoft.com/powershell/module/teams/get-cstenantblockedcallingnumbers) + +[Test-CsInboundBlockedNumberPattern](https://learn.microsoft.com/powershell/module/teams/test-csinboundblockednumberpattern) diff --git a/teams/teams-ps/teams/Set-CsTenantDialPlan.md b/teams/teams-ps/teams/Set-CsTenantDialPlan.md new file mode 100644 index 0000000000..1df48b83dc --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTenantDialPlan.md @@ -0,0 +1,190 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenantdialplan +applicable: Microsoft Teams +title: Set-CsTenantDialPlan +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsTenantDialPlan + +## SYNOPSIS +Use the `Set-CsTenantDialPlan` cmdlet to modify an existing tenant dial plan. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTenantDialPlan [[-Identity] <string>] [-Description <string>] [-NormalizationRules <Object>] + [-SimpleName <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +The `Set-CsTenantDialPlan` cmdlet modifies an existing tenant dial plan. A tenant dial plan determines such things as which normalization rules are applied. Tenant dial plans provide required information to let Enterprise Voice users make telephone calls. +The Conferencing Attendant application also uses tenant dial plans for dial-in conferencing. + +## EXAMPLES + +### Example 1 +``` +$nr2 = Get-CsVoiceNormalizationRule -Identity "US/US Long Distance" +Set-CsTenantDialPlan -Identity vt1tenantDialPlan9 -NormalizationRules @{Add=$nr2} +``` + +This example updates the vt1tenantDialPlan9 tenant dial plan to use the US/US Long Distance normalization rules. + +### Example 2 +``` +$DP = Get-CsTenantDialPlan -Identity Global +$NR = $DP.NormalizationRules | Where Name -eq "RedmondFourDigit") +$NR.Name = "RedmondRule" +Set-CsTenantDialPlan -Identity Global -NormalizationRules $DP.NormalizationRules +``` + +This example changes the name of a normalization rule. Keep in mind that changing the name also changes the name portion of the Identity. +The `Set-CsVoiceNormalizationRule` cmdlet doesn't have a Name parameter, so in order to change the name, we first call the `Get-CsTenantDialPlan` cmdlet to retrieve the Dial Plan with +the Identity Global and assign the returned object to the variable $DP. Then we filter the NormalizationRules Object for the rule RedmondFourDigit and assign the returned object to +the variable $NR. We then assign the string RedmondRule to the Name property of the object. Finally, we pass the variable back to the NormalizationRules parameter of the +`Set-CsTenantDialPlan` cmdlet to make the change permanent. + +### Example 3 +``` +$DP = Get-CsTenantDialPlan -Identity Global +$NR = $DP.NormalizationRules | Where Name -eq "RedmondFourDigit") +$DP.NormalizationRules.Remove($NR) +Set-CsTenantDialPlan -Identity Global -NormalizationRules $DP.NormalizationRules +``` + +This example removes a normalization rule. We utilize the same functionality as for Example 3 to manipulate the Normalization Rule Object and update it with the +`Set-CsTenantDialPlan` cmdlet. We first call the `Get-CsTenantDialPlan` cmdlet to retrieve the Dial Plan with the Identity Global and assign the returned object to the variable $DP. +Then we filter the NormalizationRules Object for the rule RedmondFourDigit and assign it to the variable $NR. Next, we remove this Object with the Remove Method from $DP.NormalizationRules. +Finally, we pass the variable back to the NormalizationRules parameter of the `Set-CsTenantDialPlan` cmdlet to make the change permanent. + +## PARAMETERS + +### -Confirm +The Confirm switch causes the command to pause processing and requires confirmation to proceed. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The Description parameter describes the tenant dial plan - what it's for, what type of user it applies to or any other information that helps to identify the purpose of the tenant dial plan. +Maximum characters is 1040. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity parameter is a unique identifier that designates the name of the tenant dial plan to modify. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NormalizationRules +The NormalizationRules parameter is a list of normalization rules that are applied to this dial plan. +Although this list and these rules can be created directly by using this cmdlet, we recommend that you create the normalization rules by the [New-CsVoiceNormalizationRule](https://learn.microsoft.com/powershell/module/teams/new-csvoicenormalizationrule) cmdlet, which creates the rule and assigns it to the specified tenant dial plan. + +The number of normalization rules cannot exceed 50 per TenantDialPlan. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SimpleName +The SimpleName parameter is a display name for the tenant dial plan. This name must be unique among all tenant dial plans. + +This string can be up to 49 characters long. Valid characters are alphabetic or numeric characters, hyphen (-), dot (.), and parentheses (()). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +The WhatIf parameter describes what would happen if you executed the command, without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +The ExternalAccessPrefix and OptimizeDeviceDialing parameters have been removed from New-CsTenantDialPlan and Set-CsTenantDialPlan cmdlet since they are no longer used. External access dialing is now handled implicitly using normalization rules of the dial plans. +The Get-CsTenantDialPlan will still show the external access prefix in the form of a normalization rule of the dial plan. + +## RELATED LINKS + +[Grant-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/grant-cstenantdialplan) + +[New-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/new-cstenantdialplan) + +[Get-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/get-cstenantdialplan) + +[Remove-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/remove-cstenantdialplan) diff --git a/teams/teams-ps/teams/Set-CsTenantFederationConfiguration.md b/teams/teams-ps/teams/Set-CsTenantFederationConfiguration.md new file mode 100644 index 0000000000..957f463b80 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTenantFederationConfiguration.md @@ -0,0 +1,564 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenantfederationconfiguration +applicable: Microsoft Teams +title: Set-CsTenantFederationConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +ms.date: 12/11/2024 +--- + +# Set-CsTenantFederationConfiguration + +## SYNOPSIS +> [!NOTE] +> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter AllowPublicUsers can no longer be used. + +Manages federation configuration settings for your Skype for Business Online tenants. +These settings are used to determine which domains (if any) your users are allowed to communicate with. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTenantFederationConfiguration [-Tenant <Guid>] + [-AllowedDomains <IAllowedDomainsChoice>] [-BlockedDomains <List>] [-BlockAllSubdomains <Boolean>] + [-AllowFederatedUsers <Boolean>] [-AllowTeamsConsumer <Boolean>] [-AllowTeamsConsumerInbound <Boolean>] + [-TreatDiscoveredPartnersAsUnverified <Boolean>] [-SharedSipAddressSpace <Boolean>] [-RestrictTeamsConsumerToExternalUserProfiles <Boolean>] + [-AllowedDomainsAsAList <List>] [-ExternalAccessWithTrialTenants <ExternalAccessWithTrialTenantsType>] + [-AllowedTrialTenantDomains <List>] + [[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### Instance +``` +Set-CsTenantFederationConfiguration [-Tenant <Guid>] [-AllowedDomains <IAllowedDomainsChoice>] + [-BlockedDomains <List>] [-BlockAllSubdomains <Boolean>] [-AllowFederatedUsers <Boolean>] + [-TreatDiscoveredPartnersAsUnverified <Boolean>] [-SharedSipAddressSpace <Boolean>] [-RestrictTeamsConsumerToExternalUserProfiles <Boolean>] + [-AllowedDomainsAsAList <List>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Federation is a service that enables users to exchange IM and presence information with users from other domains. +With Skype for Business Online, administrators can use the federation configuration settings to govern: + +Whether or not users can communicate with people from other domains and if so, which domains they are allowed to communicate with. + +Whether or not users can communicate with people who have accounts on public IM and presence providers such as Windows Live, Skype, or people using Microsoft Teams with an account that's not managed by an organization. + +Administrators can use the `Set-CsTenantFederationConfiguration` cmdlet to enable and disable federation with other domains and federation with public providers. +In addition, this cmdlet can be used to expressly indicate the domains that users can communicate with and/or the domains that users are not allowed to communicate with. +However, administrators must use the `Set-CsTenantPublicProvider` cmdlet in order to indicate the public IM and presence providers that users can and cannot communicate with. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" + +Set-CsTenantFederationConfiguration -BlockedDomains @{Replace=$x} +``` + +In Example 2, the domain fabrikam.com is assigned as the only domain on the blocked domains list for current tenant. +To do this, the first command in the example uses the `New-CsEdgeDomainPattern` cmdlet to create a new domain object for fabrikam.com. +This domain object is stored in a variable named $x. + +The second command in the example then uses the `Set-CsTenantFederationConfiguration` cmdlet to update the blocked domains list. +Using the Replace method ensures that the existing blocked domains list will be replaced by the new list: a list that contains only the domain fabrikam.com. + +### -------------------------- Example 3 -------------------------- +``` +$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" + +Set-CsTenantFederationConfiguration -BlockedDomains @{Remove=$x} +``` + +The commands shown in Example 3 remove fabrikam.com from the list of domains blocked by the current tenant. +To do this, the first command in the example uses the `New-CsEdgeDomainPattern` cmdlet to create a domain object for fabrikam.com. +The resulting domain object is then stored in a variable named $x. + +The second command in the example then uses the `Set-CsTenantFederationConfiguration` cmdlet and the Remove method to remove fabrikam.com from the blocked domains list for the specified tenant. + +### -------------------------- Example 4 -------------------------- +``` +$x = New-CsEdgeDomainPattern -Domain "fabrikam.com" + +Set-CsTenantFederationConfiguration -BlockedDomains @{Add=$x} +``` + +The commands shown in Example 4 add the domain fabrikam.com to the list of domains blocked by the current tenant. +To add a new blocked domain, the first command in the example uses the `New-CsEdgeDomainPattern` cmdlet to create a domain object for fabrikam.com. +This object is stored in a variable named $x. + +After the domain object has been created, the second command then uses the `Set-CsTenantFederationConfiguration` cmdlet and the Add method to add fabrikam.com to any domains already on the blocked domains list. + +### -------------------------- Example 5 -------------------------- +``` +Set-CsTenantFederationConfiguration -BlockedDomains $Null +``` + +Example 5 shows how you can remove all the domains assigned to the blocked domains list for the current tenant. +To do this, simply include the BlockedDomains parameter and set the parameter value to null ($Null). +When this command completes, the blocked domain list will be cleared. + +### -------------------------- Example 6 -------------------------- +``` +$list = New-Object Collections.Generic.List[String] +$list.add("contoso.com") +$list.add("fabrikam.com") +Set-CsTenantFederationConfiguration -AllowedDomainsAsAList $list +``` + +Example 6 shows how you can replace domains in the Allowed Domains using a List collection object. +First, a List collection is created and domains are added to it, then, simply include the AllowedDomainsAsAList parameter and set the parameter value to the List object. +When this command completes, the allowed domains list will be replaced with those domains. + +### -------------------------- Example 7 -------------------------- +``` +$list = New-Object Collections.Generic.List[String] +$list.add("contoso.com") +$list.add("fabrikam.com") +Set-CsTenantFederationConfiguration -AllowedDomainsAsAList @{Add=$list} +``` + +Example 7 shows how you can add domains to the existing Allowed Domains using a List object. +First, a List is created and domains are added to it, then use the Add method in the AllowedDomainsAsAList parameter to add the domains to the existing allowed domains list. When this command completes, the domains in the list will be added to any domains already on the AllowedDomains list. + +### -------------------------- Example 8 -------------------------- +``` +$list = New-Object Collections.Generic.List[String] +$list.add("contoso.com") +$list.add("fabrikam.com") +Set-CsTenantFederationConfiguration -AllowedDomainsAsAList @{Remove=$list} +``` + +Example 8 shows how you can remove domains from the existing Allowed Domains using a List object. +First, a List is created and domains are added to it, then use the Remove method in the AllowedDomainsAsAList parameter to remove the domains from the existing allowed domains list. When this command completes, the domains in the list will be removed from the AllowedDomains list. + +### -------------------------- Example 9 -------------------------- +``` +Set-CsTenantFederationConfiguration -AllowTeamsConsumer $True -AllowTeamsConsumerInbound $False +``` + +The command shown in Example 9 enables communication with people using Teams with an account that's not managed by an organization, to only be initiated by people in your organization. This means that people using Teams with an account that's not managed by an organization will not be able to discover or start a conversation with people in your organization. + +### -------------------------- Example 10 ------------------------- +``` +$list = New-Object Collections.Generic.List[String] +$list.add("contoso.com") +$list.add("fabrikam.com") +Set-CsTenantFederationConfiguration -BlockedDomains $list + +Set-CsTenantFederationConfiguration -BlockAllSubdomains $True +``` + +Example 10 shows how you can block all subdomains of domains in BlockedDomains list. +In this example, all users from contoso.com and fabrikam.com will be blocked. +When the BlockAllSubdomains is enabled, all users from all subdomains of all domains in BlockedDomains list will also be blocked. +So, users from subdomain.contoso.com and subdomain.fabrikam.com will be blocked. +Note: Users from subcontoso.com will not be blocked because it's a completely different domain rather than a subdomain of contoso.com. + +### -------------------------- Example 11 ------------------------- +``` +Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants "Allowed" +``` + +Example 11 shows how you can allow users to communicate with users in tenants that contain only trial licenses (default value is Blocked). + +### -------------------------- Example 12 -------------------------- +``` +$list = New-Object Collections.Generic.List[String] +$list.add("contoso.com") +$list.add("fabrikam.com") + +Set-CsTenantFederationConfiguration -AllowedTrialTenantDomains $list +``` + +Using the `AllowedTrialTenantDomains` parameter, you can whitelist specific "trial-only" tenant domains, while keeping the `ExternalAccessWithTrialTenants` set to `Blocked`. Example 12 shows how you can set or replace domains in the Allowed Trial Tenant Domains using a List collection object. +First, a List collection is created and domains are added to it, then, simply include the `AllowedTrialTenantDomains` parameter and set the parameter value to the List object. +When this command completes, the Allowed Trial Tenant Domains list will be replaced with those domains. + +### -------------------------- Example 13 -------------------------- +``` +Set-CsTenantFederationConfiguration -AllowedTrialTenantDomains @("contoso.com", "fabrikam.com") +``` + +Example 13 shows another way to set a value of `AllowedTrialTenantDomains`. It uses array of objects and it always replaces value of the `AllowedTrialTenantDomains`. When this command completes, the result is the same as in example 12. + +The array of `AllowedTrialTenantDomains` can be emptied by running the following command: `Set-CsTenantFederationConfiguration -AllowedTrialTenantDomains @()`. + +### -------------------------- Example 14 -------------------------- +``` +$list = New-Object Collections.Generic.List[String] +$list.add("contoso.com") + +Set-CsTenantFederationConfiguration -AllowedTrialTenantDomains @{Add=$list} +``` + +Example 14 shows how you can add domains to the existing Allowed Trial Tenant Domains using a List collection object. +First, a List is created and domains are added to it, then, use the Add method in the `AllowedTrialTenantDomains` parameter to add the domains to the existing allowed domains list. +When this command completes, the domains in the list will be added to any domains already on the Allowed Trial Tenant Domains list. + +### -------------------------- Example 15 -------------------------- +``` +$list = New-Object Collections.Generic.List[String] +$list.add("contoso.com") + +Set-CsTenantFederationConfiguration -AllowedTrialTenantDomains @{Remove=$list} +``` + +Example 15 shows how you can remove domains from the existing Allowed Trial Tenant Domains using a List collection object. +First, a List is created and domains are added to it, then use the Remove method in the `AllowedTrialTenantDomains` parameter to remove the domains from the existing allowed domains list. +When this command completes, the domains in the list will be removed from the Allowed Trial Tenant Domains list. + +## PARAMETERS + +### -AllowedDomains +Domain objects (created by using the `New-CsEdgeAllowList` cmdlet or the `New-CsEdgeAllowAllKnownDomains` cmdlet) that represent the domains that users are allowed to communicate with. +If the `New-CsEdgeAllowAllKnownDomains` cmdlet is used then users can communicate with any domain that does not appear on the blocked domains list. +If the `New-CsEdgeAllowList` cmdlet is used then users can only communicate with domains that have been added to the allowed domains list. + +Note that string values cannot be passed directly to the AllowedDomains parameter. +Instead, you must create an object reference using the `New-CsEdgeAllowList` cmdlet or the `New-CsEdgeAllowAllKnownDomains` cmdlet and then use the object reference variable as the parameter value. + +The AllowedDomains parameter can support up to 4,000 domains. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowFederatedUsers +When set to True (the default value) users will be potentially allowed to communicate with users from other domains. +If this property is set to False then users cannot communicate with users from other domains regardless of the values assigned to the AllowedDomains and BlockedDomains properties. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTeamsConsumer +Allows federation with people using Teams with an account that's not managed by an organization. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowTeamsConsumerInbound +Allows people using Teams with an account that's not managed by an organization, to discover and start communication with users in your organization. When -AllowTeamsConsumer is enabled and this parameter is disabled, only the users in your organization will be able to discover and start communication with people using Teams with an account that's not managed by an organization, but they will not discover and start communications with users in your organization. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockedDomains +If the AllowedDomains property has been set to AllowAllKnownDomains, then users will be allowed to communicate with users from any domain except domains that appear in the blocked domains list. +If the AllowedDomains property has not been set to AllowAllKnownDomains, then the blocked list is ignored, and users can only communicate with domains that have been expressly added to the allowed domains list. +The BlockedDomains parameter can support up to 4,000 domains. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BlockAllSubdomains +If the BlockedDomains parameter is used, then BlockAllSubdomains can be used to activate all subdomains blocking. +If the BlockedDomains parameter is ignored, then BlockAllSubdomains is also ignored. +Just like for BlockedDomains, users will be disallowed from communicating with users from blocked domains. +But all subdomains for domains in this list will also be blocked. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Skype for Business Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +Suppresses the display of any non-fatal error message that might arise when running the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +Specifies the collection of tenant federation configuration settings to be modified. +Because each tenant is limited to a single, global collection of federation settings there is no need include this parameter when calling the `Set-CsTenantFederationConfiguration` cmdlet. +If you do choose to use the Identity parameter you must also include the Tenant parameter. +For example: + +`Set-CsTenantFederationConfiguration -Tenant "bf19b7db-6960-41e5-a139-2aa373474354" -Identity "global"` + +```yaml +Type: XdsIdentity +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. + +```yaml +Type: PSObject +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SharedSipAddressSpace +When set to True, indicates that the users homed on Skype for Business Online use the same SIP domain as users homed on the on-premises version of Skype for Business Server. +The default value is False, meaning that the two sets of users have different SIP domains. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose federation settings are being modified. +For example: + +`-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308"` + +You can return your tenant ID by running this command: + +`Get-CsTenant | Select-Object DisplayName, TenantID` + +If you are using a remote session of Windows PowerShell and are connected only to Skype for Business Online you do not have to include the Tenant parameter. +Instead, the tenant ID will automatically be filled in for you based on your connection information. +The Tenant parameter is primarily for use in a hybrid deployment. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TreatDiscoveredPartnersAsUnverified +When set to True, messages sent from discovered partners are considered unverified. +That means that those messages will be delivered only if they were sent from a person who is on the recipient's Contacts list. +The default value is False ($False). + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedDomainsAsAList +You can specify allowed domains using a List object that contains the domains that users are allowed to communicate with. See Examples section. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExternalAccessWithTrialTenants +When set to 'Blocked', all external access with users from Teams subscriptions that contain only trial licenses will be blocked. This means users from these trial-only tenants will not be able to reach to your users via chats, Teams calls, and meetings (using the users authenticated identity) and your users will not be able to reach users in these trial-only tenants. If this setting is set to "Blocked", users from the trial-only tenant will also be removed from existing chats. + +Allowed - Communication with other tenants is allowed based on other settings. + +Blocked - Communication with users in tenants that contain only trial licenses will be blocked. + +```yaml +Type: ExternalAccessWithTrialTenantsType +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AllowedTrialTenantDomains +You can whitelist specific "trial-only" tenant domains, while keeping the `ExternalAccessWithTrialTenants` set to `Blocked`. This will allow you to protect your organization against majority of tenants that don't have any paid subscriptions, while still being able to collaborate externally with those trusted trial-tenants in the list. + +Note: +- The list supports up to maximum 4k domains. +- If `ExternalAccessWithTrialTenants` is set to `Allowed`, then the `AllowedTrialTenantDomains` list will not be checked. +- Any domain in this list that belongs to a tenant with paid subscriptions will be ignored. + +```yaml +Type: List +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RestrictTeamsConsumerToExternalUserProfiles +Defines if a user is restricted to collaboration with Teams Consumer (TFL) user only in Extended Directory. +Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +The `Set-CsTenantFederationConfiguration` cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.TenantFederationSettings object. + +## OUTPUTS + +### Output types +None. +Instead, the `Set-CsTenantFederationConfiguration` cmdlet modifies existing instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Edge.TenantFederationSettings object. + +## NOTES + +## RELATED LINKS + +[Get-CsTenantFederationConfiguration](https://learn.microsoft.com/powershell/module/teams/get-cstenantfederationconfiguration) diff --git a/teams/teams-ps/teams/Set-CsTenantMigrationConfiguration.md b/teams/teams-ps/teams/Set-CsTenantMigrationConfiguration.md new file mode 100644 index 0000000000..9008b4da94 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTenantMigrationConfiguration.md @@ -0,0 +1,185 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenantmigrationconfiguration +applicable: Microsoft Teams +title: Set-CsTenantMigrationConfiguration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Set-CsTenantMigrationConfiguration + +## SYNOPSIS +Used to enable or disable Meeting Migration Service (MMS). + +## SYNTAX + +### Identity (Default) +``` +Set-CsTenantMigrationConfiguration [[-Identity] <String>] + [-Confirm] + [-Force] + [-MeetingMigrationEnabled <Boolean>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +### Instance +``` +Set-CsTenantMigrationConfiguration [-Instance <Object>] + [-Confirm] + [-Force] + [-MeetingMigrationEnabled <Boolean>] + [-Tenant <Guid>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION +Used to enable or disable Meeting Migration Service (MMS). +For more information, see [Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms). + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Set-CsTenantMigrationConfiguration -MeetingMigrationEnabled $false +``` + +This example disables MMS in the organization. + +## PARAMETERS + +### -Identity +Unique identifier for the Migration Configuration. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +The Instance parameter allows you to pass a reference to an object to the cmdlet, rather than set individual parameter values. +You can retrieve this object reference by calling the `Get-CsTenantMigrationConfiguration` cmdlet. + +```yaml +Type: PSObject +Parameter Sets: Instance +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MeetingMigrationEnabled +Set this to false to disable the Meeting Migration Service. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +Globally unique identifier (GUID) of the tenant account whose Migration Configurations are being created. For example: + +-Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" + +You can return your tenant ID by running this command: + +Get-CsTenant | Select-Object DisplayName, TenantID + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsTenantNetworkRegion.md b/teams/teams-ps/teams/Set-CsTenantNetworkRegion.md new file mode 100644 index 0000000000..7ec40da511 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTenantNetworkRegion.md @@ -0,0 +1,149 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworkregion +applicable: Microsoft Teams +title: Set-CsTenantNetworkRegion +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsTenantNetworkRegion + +## SYNOPSIS +As an admin, you can use the Teams PowerShell command, Set-CsTenantNetworkRegion to define network regions. A network region interconnects various parts of a network across multiple geographic areas. The RegionID parameter is a logical name that represents the geography of the region and has no dependencies or restrictions. The organization's network region is used for Location-Based Routing. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTenantNetworkRegion [[-Identity] <string>] [-CentralSite <string>] [-Description <string>] + [-NetworkRegionID <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. A network region contains a collection of network sites. For example, if your organization has many sites located in Redmond, then you may choose to designate "Redmond" as a network region. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTenantNetworkRegion -Identity "RegionA" -Description "Region A" +``` + +The command shown in Example 1 sets the network region 'RegionA' with the description 'Region A'. + +## PARAMETERS + +### -Identity +Unique identifier for the network region to be set. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CentralSite +This parameter is not used. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of the network region to identify purpose of setting it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkRegionID +The name of the network region. Not required in this PowerShell command. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworkregion) + +[Remove-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworkregion) + +[Get-CsTenantNetworkRegion](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworkregion) diff --git a/teams/teams-ps/teams/Set-CsTenantNetworkSite.md b/teams/teams-ps/teams/Set-CsTenantNetworkSite.md new file mode 100644 index 0000000000..9f97f7495e --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTenantNetworkSite.md @@ -0,0 +1,227 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksite +applicable: Microsoft Teams +title: Set-CsTenantNetworkSite +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsTenantNetworkSite + +## SYNOPSIS +As an Admin, you can use the Windows PowerShell command, Set-CsTenantNetworkSite to define network sites. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. Tenant network site is used for Location Based Routing. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsTenantNetworkSite [[-Identity] <string>] [-Description <string>] [-EmergencyCallingPolicy <string>] [-EmergencyCallRoutingPolicy <string>] + [-EnableLocationBasedRouting <bool>] [-LocationPolicy <string>] [-NetworkRegionID <string>] [-NetworkRoamingPolicy <string>] + [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. + +A best practice for Location Based Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration. In addition, network sites can also be used for configuring Network Roaming Policy capabilities. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTenantNetworkSite -Identity "MicrosoftSite1" -NetworkRegionID "RegionRedmond" -Description "Microsoft site 1" +``` + +The command shown in Example 1 set the network site 'MicrosoftSite1' with description 'Microsoft site 1'. + +The network region 'RegionRedmond' is created beforehand and 'MicrosoftSite1' will be associated with 'RegionRedmond'. + +### Example 2 +```powershell +PS C:\> Set-CsTenantNetworkSite -Identity "site2" -Description "site 2" -NetworkRegionID "RedmondRegion" -EnableLocationBasedRouting $true +``` + +The command shown in Example 2 sets the network site 'site2' with description 'site 2'. This site is enabled for LBR. The example associates the site with network region 'RedmondRegion'. + +### Example 3 +```powershell +PS C:\> Set-CsTenantNetworkSite -Identity "site3" -Description "site 3" -NetworkRegionID "RedmondRegion" -NetworkRoamingPolicy "TestNetworkRoamingPolicy" +``` + +The command shown in Example 3 sets the network site 'site3' with description 'site 3'. This site is enabled for network roaming capabilities. The example associates the site with network region 'RedmondRegion' and network roaming policy 'TestNetworkRoamingPolicy'. + +## PARAMETERS + +### -Identity +Unique identifier for the network site to be set. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of the network site to identify purpose of setting it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyCallingPolicy +This parameter is used to assign a custom emergency calling policy to a network site. For more information, see [Assign a custom emergency calling policy to a network site](https://learn.microsoft.com/microsoftteams/manage-emergency-calling-policies#assign-a-custom-emergency-calling-policy-to-a-network-site). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EmergencyCallRoutingPolicy +This parameter is used to assign a custom emergency call routing policy to a network site. For more information, see [Assign a custom emergency call routing policy to a network site](https://learn.microsoft.com/microsoftteams/manage-emergency-call-routing-policies#assign-a-custom-emergency-call-routing-policy-to-a-network-site). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableLocationBasedRouting +This parameter determines whether the current site is enabled for Location-Based Routing. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LocationPolicy +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkRegionID +NetworkRegionID is the identifier for the network region which the current network site is associating to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkRoamingPolicy +NetworkRoamingPolicy is the identifier for the network roaming policy to which the network site will associate to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS +[New-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksite) + +[Remove-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksite) + +[Get-CsTenantNetworkSite](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksite) diff --git a/teams/teams-ps/teams/Set-CsTenantNetworkSubnet.md b/teams/teams-ps/teams/Set-CsTenantNetworkSubnet.md new file mode 100644 index 0000000000..52e3aea595 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsTenantNetworkSubnet.md @@ -0,0 +1,157 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenantnetworksubnet +applicable: Microsoft Teams +title: Set-CsTenantNetworkSubnet +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Set-CsTenantNetworkSubnet + +## SYNOPSIS +As an admin, you can use the Teams PowerShell command, Set-CsTenantNetworkSubnet to define network subnets and assign them to network sites. Each internal subnet may only be associated with one site. The organization's network subnet is used for Location-Based Routing. + +## SYNTAX + +### Identity (Default) +``` +Set-CsTenantNetworkSubnet [[-Identity] <string>] [-Description <string>] + [-MaskBits <int>] [-NetworkSiteID <string>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass. Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based Routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-CsTenantNetworkSubnet -Identity "192.168.0.1" -MaskBits "24" -NetworkSiteID "site1" +``` + +The command shown in Example 1 set the network subnet '192.168.0.1'. The subnet is in IPv4 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 24. + +IPv4 format subnet accepts maskbits from 0 to 32 inclusive. + +### Example 2 +```powershell +PS C:\> Set-CsTenantNetworkSubnet -Identity "2001:4898:e8:25:844e:926f:85ad:dd8e" -MaskBits "120" -NetworkSiteID "site1" -Description "Subnet 2001:4898:e8:25:844e:926f:85ad:dd8e" +``` + +The command shown in Example 2 set the network subnet '2001:4898:e8:25:844e:926f:85ad:dd8e' with description 'Subnet 2001:4898:e8:25:844e:926f:85ad:dd8e'. The subnet is in IPv6 format, and the subnet is assigned to network site 'site1'. The maskbits is set to 120. + +IPv6 format subnet accepts maskbits from 0 to 128 inclusive. + +## PARAMETERS + +### -Identity +Unique identifier for the network subnet to be set. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +Provide a description of the network subnet to identify purpose of setting it. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MaskBits +This parameter determines the length of bits to mask to the subnet. + +IPv4 format subnet accepts maskbits from 0 to 32 inclusive. IPv6 format subnet accepts maskbits from 0 to 128 inclusive. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NetworkSiteID +NetworkSiteID is the identifier for the network site which the current network subnet is associating to. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[New-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/new-cstenantnetworksubnet) + +[Remove-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/remove-cstenantnetworksubnet) + +[Get-CsTenantNetworkSubnet](https://learn.microsoft.com/powershell/module/teams/get-cstenantnetworksubnet) diff --git a/skype/skype-ps/skype/Set-CsTenantTrustedIPAddress.md b/teams/teams-ps/teams/Set-CsTenantTrustedIPAddress.md similarity index 95% rename from skype/skype-ps/skype/Set-CsTenantTrustedIPAddress.md rename to teams/teams-ps/teams/Set-CsTenantTrustedIPAddress.md index 6e2745c225..8e93bf341c 100644 --- a/skype/skype-ps/skype/Set-CsTenantTrustedIPAddress.md +++ b/teams/teams-ps/teams/Set-CsTenantTrustedIPAddress.md @@ -1,13 +1,13 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-cstenanttrustedipaddress -applicable: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-cstenanttrustedipaddress +applicable: Microsoft Teams title: Set-CsTenantTrustedIPAddress schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsTenantTrustedIPAddress @@ -196,8 +196,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -206,6 +205,7 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-CsUser.md b/teams/teams-ps/teams/Set-CsUser.md new file mode 100644 index 0000000000..97f1298690 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsUser.md @@ -0,0 +1,442 @@ +--- +external help file: Microsoft.Rtc.Management.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/set-csuser +applicable: Microsoft Teams +title: Set-CsUser +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: rogupta +--- + +# Set-CsUser + +## SYNOPSIS +Modifies Skype for Business properties for an existing user account. +Properties can be modified only for accounts that have been enabled for use with Skype for Business. +This cmdlet was introduced in Lync Server 2010. + +**Note**: Using this cmdlet for Microsoft Teams users in commercial and GCC cloud instances has been deprecated. Use the new [Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) and [Remove-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/remove-csphonenumberassignment) cmdlets instead. + +## SYNTAX + +``` +Set-CsUser [-DomainController <Fqdn>] [-Identity] <UserIdParameter> [-PassThru] [-WhatIf] [-Confirm] + [-OnPremLineURI <String>] [-LineServerURI <String>] [-AudioVideoDisabled <Boolean>] + [-RemoteCallControlTelephonyEnabled <Boolean>] [-PrivateLine <String>] [-AcpInfo <AcpInfo>] + [-HostedVoiceMail <Boolean>] [-EnterpriseVoiceEnabled <Boolean>] + [-ExchangeArchivingPolicy <ExchangeArchivingPolicyOptionsEnum>] [-LineURI <String>] [-SipAddress <String>] + [-Enabled <Boolean>] [<CommonParameters>] +``` + +## DESCRIPTION +The `Set-CsUser` cmdlet enables you to modify the Skype for Business related user account attributes that are stored in Active Directory Domain Services or modify a subset of Skype for Business online user attributes that are stored in Microsoft Entra ID. +For example, you can disable or re-enable a user for Skype for Business Server; enable or disable a user for audio/video (A/V) communications; or modify a user's private line and line URI numbers. For Skype for Business online enable or disable a user for enterprise voice, hosted voicemail, or modify the user's on premise line uri. +The `Set-CsUser` cmdlet can be used only for users who have been enabled for Skype for Business. + +The only attributes you can modify using the `Set-CsUser` cmdlet are attributes related to Skype for Business. +Other user account attributes, such as the user's job title or department, cannot be modified by using this cmdlet. +Keep in mind, however, that the Skype for Business attributes should only be modified by using the `Set-CsUser` cmdlet or the Skype for Business Server Control Panel. +You should not attempt to manually configure these attributes. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Set-CsUser -Identity "Pilar Ackerman" -EnterpriseVoiceEnabled $True +``` + +In Example 1, the `Set-CsUser` cmdlet is used to modify the user account with the Identity Pilar Ackerman. +In this case, the account is modified to enable Enterprise Voice, the Microsoft implementation of VoIP. +This task is carried out by adding the EnterpriseVoiceEnabled parameter, and then setting the parameter value to $True. + +### -------------------------- Example 2 -------------------------- +```powershell +Get-CsUser -LdapFilter "Department=Finance" | Set-CsUser -EnterpriseVoiceEnabled $True +``` + +In Example 2, all the users in the Finance department have their accounts enabled for Enterprise Voice. +In this command, the `Get-CsUser` cmdlet and the LdapFilter parameter are first used to return a collection of all the users who work in the Finance department. +That information is then piped to the `Set-CsUser` cmdlet, which enables Enterprise Voice for each account in the collection. + +### -------------------------- Example 3 -------------------------- +```powershell +Set-CsUser -Identity "Pilar Ackerman" -LineUri "tel:+123456789" +``` + +In Example 3, the `Set-CsUser` cmdlet is used to modify the user account with the Identity Pilar Ackerman. +In this case, the account is modified to set the phone number assigned to the user settings its LineUri property. + +## PARAMETERS + +### -Identity +Indicates the Identity of the user account to be modified. +User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). +User Identities can also be referenced by using the user's Active Directory distinguished name. + +You can use the asterisk (*) wildcard character when using the display name as the user Identity. +For example, the Identity "Smith" returns all the users who have a display name that ends with the string value " Smith". + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: True +Position: 1 +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### -AudioVideoDisabled +Indicates whether the user is allowed to make audio/visual (A/V) calls by using Skype for Business. +If set to True, the user will largely be restricted to sending and receiving instant messages. + +You cannot disable A/V communications if a user is currently enabled for remote call control, Enterprise Voice, and/or Internet Protocol private branch exchange (IP-PBX) soft phone routing. + +**Note**: This parameter is not available for Teams Only tenants from version 3.0.0 onwards. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled +Indicates whether or not the user has been enabled for Skype for Business Server. +If you set this value to False, the user will no longer be able to log on to Skype for Business Server; setting this value to True re-enables the user's logon privileges. + +If you disable an account by using the Enabled parameter, the information associated with that account (including assigned policies and whether or not the user is enabled for Enterprise Voice and/or remote call control) is retained. +If you later re-enable the account by using the Enabled parameter, the associated account information will be restored. +This differs from using the `Disable-CsUser` cmdlet to disable a user account. +When you run the `Disable-CsUser` cmdlet, all the Skype for Business Server data associated with that account is deleted. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: CsEnabled +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +Enables you to specify a domain controller to connect to when modifying a user account. +If this parameter is not included then the cmdlet will use the first available domain controller. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnterpriseVoiceEnabled +Indicates whether the user has been enabled for Enterprise Voice, which is the Microsoft implementation of Voice over Internet Protocol (VoIP). +With Enterprise Voice, users can make telephone calls using the Internet rather than using the standard telephone network. + +**Note**: Using this parameter for Microsoft Teams users in commercial and GCC cloud instances has been deprecated. Use the new [Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) cmdlet instead. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HostedVoiceMail +When set to True, enables a user's voice mail calls to be routed to a hosted version of Microsoft Exchange Server. +In addition, setting this option to True enables Skype for Business users to directly place a call to another user's voice mail. + +**Note**: It is not required to set this parameter for Microsoft Teams users. Using this parameter has been deprecated for Microsoft Teams users in commercial and GCC cloud instances. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LineURI +Phone number to be assigned to the user in Skype for Business Server or Direct Routing phone number to be assigned to a Microsoft Teams user in GCC High and DoD cloud instances only. + +The line Uniform Resource Identifier (URI) must be specified using the E.164 format and the "tel:" prefix, for example: tel:+14255551297. +Any extension number should be added to the end of the line URI, for example: tel:+14255551297;ext=51297. + +It is important to note that Skype for Business Server treats tel:+14255551297 and tel:+14255551297;ext=51297 as two different numbers. +If you assign Ken Myer the line URI tel:+14255551297 and later try to assign Pilar Ackerman the line URI tel:+14255551297;ext=51297, that assignment will succeed; the number assigned to Pilar will not +be flagged as a duplicate number. This is due to the fact that, depending on your setup, those two numbers could actually be different. For example, in some organizations dialing 1-425-555-1297 +routes your call to an Exchange Auto Attendant. Conversely, dialing just the extension (51297) or using Skype for Business to dial the number 1-425-555-1297 extension 51297 will route your call +directly to the user. + +For Direct Routing phone numbers in GCC High and DoD cloud instances, assigning a base phone number to a user or resource account is not supported if you already have other users or resource accounts assigned phone numbers with the same base phone number and extensions or vice versa. For instance, if you have a user with the assigned phone number +14255551200;ext=123 you can't assign the phone number +14255551200 to another user or resource account or if you have a user or resource account with the assigned phone number +14255551200 you can't assign the phone number +14255551200;ext=123 to another user or resource account. Assigning phone numbers with the same base number but different extensions to users and resource accounts is supported. For instance, you can have a user with +14255551200;ext=123 and another user with +14255551200;ext=124. + +Note: Extension should be part of the E164 Number. For example if you have 5 digit Extensions then the last 5 digits of the E164 Number should always match the 5 digit extension tel:+14255551297;ext=51297 + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -LineServerURI +The URI of the remote call control telephone gateway assigned to the user. +The LineServerUri is the gateway URI, prefaced by "sip:". +For example: sip:rccgateway@litwareinc.com + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PrivateLine +Phone number for the user's private telephone line. +A private line is a phone number that is not published in Active Directory Domain Services and, as a result, is not readily available to other people. +In addition, this private line bypasses most in-bound call routing rules; for example, a call to a private line will not be forwarded to a person's delegates. +Private lines are often used for personal phone calls or for business calls that should be kept separate from other team members. + +The private line value should be specified using the E.164 format, and be prefixed by the "tel:" prefix. +For example: tel:+14255551297. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoteCallControlTelephonyEnabled +Indicates whether the user has been enabled for remote call control telephony. +When enabled for remote call control, a user can employ Skype for Business to answer phone calls made to his or her desk phone. +Phone calls can also be made using Skype for Business. +These calls all rely on the standard telephone network, also known as the public switched telephone network (PSTN). +To make and receive phone calls over the Internet, the user must be enabled for Enterprise Voice. +For details, see the parameter EnterpriseVoiceEnabled. + +To be enabled for remote call control, a user must have both a LineUri and a LineServerUri. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SipAddress +Unique identifier (similar to an email address) that allows the user to communicate using SIP devices such as Skype for Business. +The SIP address must use the sip: prefix as well as a valid SIP domain; for example: `-SipAddress sip:kenmyer@litwareinc.com`. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PassThru +Enables you to pass a user object through the pipeline that represents the user whose account is being modified. +By default, the `Set-CsUser` cmdlet does not pass objects through the pipeline. + +**Note**: This parameter is not available for Teams Only tenants from version 3.0.0 onwards. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Describes what would happen if you executed the command without actually executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before executing the command. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AcpInfo +Enables you to assign one or more third-party audio conferencing providers to a user. +However, it is recommended that you use the `Set-CsUserAcp` cmdlet to assign Audio conferencing providers. + +```yaml +Type: AcpInfo +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExchangeArchivingPolicy +Indicates where the user's instant messaging sessions are archived. +Allowed values are: + +Uninitialized + +UseLyncArchivingPolicy + +ArchivingToExchange + +NoArchiving + +```yaml +Type: ExchangeArchivingPolicyOptionsEnum +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OnPremLineURI +Specifies the phone number assigned to the user if no number is assigned to that user in the Skype for Business hybrid environment. +The line Uniform Resource Identifier (URI) must be specified using the E.164 format and use the "tel:" prefix. +For example: tel:+14255551297. +Any extension number should be added to the end of the line URI, for example: tel:+14255551297;ext=51297. + +Note that Skype for Business treats tel:+14255551297 and tel:+14255551297;ext=51297 as two different numbers. +If you assign Ken Myer the line URI tel:+14255551297 and later try to assign Pilar Ackerman the line URI tel:+14255551297;ext=51297, that assignment will succeed. +Depending on your setup, those two numbers could actually be different. +For example, in some organizations dialing 1-425-555-1297 routes your call to an Exchange Auto Attendant. +Conversely, dialing just the extension (51297) or using Skype for Business to dial the number 1-425-555-1297 extension 51297 will route your call directly to the user. + +**Note**: Using this parameter for Microsoft Teams users in commercial and GCC cloud instances has been deprecated. Use the new [Set-CsPhoneNumberAssignment](https://learn.microsoft.com/powershell/module/teams/set-csphonenumberassignment) cmdlet instead. + +**Note**: Using this parameter for Microsoft Teams users in GCC High and DoD cloud instances has been deprecated. Use the -LineURI parameter instead. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +String or Microsoft.Rtc.Management.ADConnect.Schema.ADUser object. +The `Set-CsUser` cmdlet accepts a pipelined string value representing the Identity of a user account that has been enabled for Skype for Business Server. +The cmdlet also accepts pipelined instances of the Active Directory user object. + +## OUTPUTS + +### Output types +The `Set-CsUser` cmdlet does not return any objects. + +## NOTES + +## RELATED LINKS + +[Get-CsOnlineUser](https://learn.microsoft.com/powershell/module/teams/get-csonlineuser) diff --git a/teams/teams-ps/teams/Set-CsUserCallingDelegate.md b/teams/teams-ps/teams/Set-CsUserCallingDelegate.md new file mode 100644 index 0000000000..ac17aa7a8a --- /dev/null +++ b/teams/teams-ps/teams/Set-CsUserCallingDelegate.md @@ -0,0 +1,144 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csusercallingdelegate +applicable: Microsoft Teams +title: Set-CsUserCallingDelegate +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Set-CsUserCallingDelegate + +## SYNOPSIS +This cmdlet will change permissions for a delegate for calling in Microsoft Teams. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsUserCallingDelegate -Identity <String> -Delegate <String> [-MakeCalls <Boolean>] [-ReceiveCalls <Boolean>] [-ManageSettings <Boolean>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet can change the permissions assigned to a delegate for the specified user. + +## EXAMPLES + +### Example 1 +```powershell +Set-CsUserCallingDelegate -Identity user1@contoso.com -Delegate user2@contoso.com -MakeCalls $false -ReceiveCalls $true -ManageSettings $false +``` +This example shows setting the permissions for user1@contoso.com's delegate user2@contoso.com. + +### Example 2 +```powershell +Set-CsUserCallingDelegate -Identity user1@contoso.com -Delegate user2@contoso.com -MakeCalls $true +``` +This example shows setting the MakeCalls permissions to True for user1@contoso.com's delegate user2@contoso.com. + +## PARAMETERS + +### -Delegate +The Identity of the delegate to add. Can be specified using the ObjectId or the SIP address. + +A user can have up to 25 delegates. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity of the user to add a delegate for. Can be specified using the ObjectId or the SIP address. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MakeCalls + +Specifies whether delegate is allowed to make calls on behalf of the specified user. + +```yaml +Type: System.Boolean +Parameter Sets: All +Aliases: + +Required: False +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ManageSettings + +Specifies whether delegate is allowed to change the delegate and calling settings for the specified user. + +```yaml +Type: System.Boolean +Parameter Sets: All +Aliases: + +Required: False +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReceiveCalls + +Specifies whether delegate is allowed to receive calls on behalf of the specified user. + +```yaml +Type: System.Boolean +Parameter Sets: All +Aliases: + +Required: False +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PowerShell module 4.0.0 or later. + +The specified user need to have the Microsoft Phone System license assigned. + +You can see the delegate of a user by using the Get-CsUserCallingSettings cmdlet. + +## RELATED LINKS +[Get-CsUserCallingSettings](https://learn.microsoft.com/powershell/module/teams/get-csusercallingsettings) + +[New-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/new-csusercallingdelegate) + +[Remove-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/remove-csusercallingdelegate) diff --git a/teams/teams-ps/teams/Set-CsUserCallingSettings.md b/teams/teams-ps/teams/Set-CsUserCallingSettings.md new file mode 100644 index 0000000000..4b590f4ab2 --- /dev/null +++ b/teams/teams-ps/teams/Set-CsUserCallingSettings.md @@ -0,0 +1,414 @@ +--- +external help file: Microsoft.Open.Teams.CommonLibrary.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-csusercallingsettings +applicable: Microsoft Teams +title: Set-CsUserCallingSettings +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Set-CsUserCallingSettings + +## SYNOPSIS +This cmdlet will set the call forwarding, simultaneous ringing and call group settings for the specified user. + +## SYNTAX + +### Identity (Default) +```powershell +Set-CsUserCallingSettings -Identity <String> [<CommonParameters>] +``` + +### ForwardingOnOff +```powershell +Set-CsUserCallingSettings -Identity <String> -IsForwardingEnabled <Boolean> [<CommonParameters>] +``` + +### Forwarding +```powershell +Set-CsUserCallingSettings -Identity <String> -IsForwardingEnabled <Boolean> -ForwardingType <String> [-ForwardingTarget <String>] -ForwardingTargetType <String> [<CommonParameters>] +``` + +### UnansweredOnOff +```powershell +Set-CsUserCallingSettings -Identity <String> -IsUnansweredEnabled <Boolean> [<CommonParameters>] +``` + +### Unanswered +```powershell +Set-CsUserCallingSettings -Identity <String> -IsUnansweredEnabled <Boolean> [-UnansweredTarget <String>] -UnansweredTargetType <String> -UnansweredDelay <String> [<CommonParameters>] +``` + +### CallGroup +```powershell +Set-CsUserCallingSettings -Identity <String> -CallGroupOrder <String> -CallGroupTargets <String[]> [<CommonParameters>] +``` + +### CallGroupMembership +```powershell +Set-CsUserCallingSettings -Identity <String> -GroupMembershipDetails <ICallGroupMembershipDetails[]> [<CommonParameters>] +``` + +### CallGroupNotification +```powershell +Set-CsUserCallingSettings -Identity <String> -GroupNotificationOverride <String> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet sets the call forwarding, simultaneous ringing and call group settings for the specified user. + +When specifying settings you need to specify all settings with a settings grouping, for instance, you can't just change a forwarding target. Instead, you need to +start by getting the current settings, making the necessary changes, and then setting/writing all settings within the settings group. + +## EXAMPLES + +### Example 1 +```powershell +Set-CsUserCallingSettings -Identity user1@contoso.com -IsForwardingEnabled $true -ForwardingType Immediate -ForwardingTargetType Voicemail +``` +This example shows setting immediate call forwarding to voicemail for user1@contoso.com. + +### Example 2 +```powershell +Set-CsUserCallingSettings -Identity user1@contoso.com -IsForwardingEnabled $false +``` +This example shows removing call forwarding for user1@contoso.com. + +### Example 3 +```powershell +Set-CsUserCallingSettings -Identity user1@contoso.com -IsForwardingEnabled $true -ForwardingType Simultaneous -ForwardingTargetType SingleTarget -ForwardingTarget "+12065551234" +``` +This example shows setting simultaneous ringing to +12065551234 for user1@contoso.com. + +### Example 4 +```powershell +Set-CsUserCallingSettings -Identity user1@contoso.com -IsUnansweredEnabled $true -UnansweredTargetType MyDelegates -UnansweredDelay 00:00:30 +``` +This example shows setting unanswered call forward to the delegates after 30 seconds for user1@contoso.com. + +### Example 5 +```powershell +$cgm = @("sip:user2@contoso.com","sip:user3@contoso.com") +Set-CsUserCallingSettings -Identity user1@contoso.com -CallGroupOrder InOrder -CallGroupTargets $cgm +Set-CsUserCallingSettings -Identity user1@contoso.com -IsForwardingEnabled $true -ForwardingType Immediate -ForwardingTargetType Group +``` +This example shows creating a call group for user1@contoso.com with 2 members and setting immediate call forward to the call group for user1@contoso.com. + +### Example 6 +```powershell +$ucs = Get-CsUserCallingSettings -Identity user1@contoso.com +$cgt = {$ucs.CallGroupTargets}.Invoke() +$cgt.Add("sip:user5@contoso.com") +$cgt.Remove("sip:user6@contoso.com") +Set-CsUserCallingSettings -Identity user1@contoso.com -CallGroupOrder $ucs.CallGroupOrder -CallGroupTargets $cgt + +$gmd = (Get-CsUserCallingSettings -Identity user5@contoso.com).GroupMembershipDetails +$gmd[[array]::IndexOf($gmd.CallGroupOwnerId,'sip:user1@contoso.com')].NotificationSetting = 'Banner' +Set-CsUserCallingSettings -Identity user5@contoso.com -GroupMembershipDetails $gmd +``` + +This example shows how to update the call group of user1@contoso.com to add user5@contoso.com and remove user6@contoso.com. In addition the notification setting for +user5@contoso.com for user1@contoso.com's call group is set to Banner. + +The key to note here is the call group membership is defined on the object of the owner of the call group, in the above case this is user1@contoso.com. However, +the notification setting for a member for a particular call group is defined on the member. In this case user5@contoso.com. + +### Example 7 +```powershell +$ucs = Get-CsUserCallingSettings -Identity user1@contoso.com +Set-CsUserCallingSettings -Identity user1@contoso.com -CallGroupOrder $ucs.CallGroupOrder -CallGroupTargets @() +``` + +This example shows how to remove all members of the call group. + +### Example 8 +```powershell +[Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ICallGroupMembershipDetails[]]$gmd = @( + [Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ICallGroupMembershipDetails]@{CallGroupOwnerId='sip:user20@contoso.com';NotificationSetting='Banner'} + [Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ICallGroupMembershipDetails]@{CallGroupOwnerId='sip:user30@contoso.com';NotificationSetting='Mute'} +) +Set-CsUserCallingSettings -Identity user10@contoso.com -GroupMembershipDetails $gmd +``` + +In this example user10@contoso.com is a member of two call groups: user20@contoso.com and user30@contoso.com. User10@contoso.com would like to have Banner +notification for the first call group and Mute notification for the last one. + +### Example 9 +```powershell +Set-CsUserCallingSettings -Identity user2@contoso.com -GroupNotificationOverride 'Mute' +``` + +This example shows how to set the group notification override for user2@contoso.com. This setting overrides any specific notification setting set for the user +on any call group the user is a member of. + +### Example 10 +```powershell +Set-CsUserCallingSettings -Identity user6@contoso.com -IsForwardingEnabled $false +Set-CsUserCallingSettings -Identity user6@contoso.com -IsUnansweredEnabled $true -UnansweredTargetType Voicemail -UnansweredDelay 00:00:20 +``` + +This example shows how to set the default call forwarding settings for a user. + +### Example 11 +```powershell +Set-CsUserCallingSettings -Identity user7@contoso.com -IsUnansweredEnabled $false +``` + +This example shows turning off unanswered call forwarding for a user. The Microsoft Teams client will show this as _If unanswered Do nothing_. + +## PARAMETERS + +### -CallGroupOrder + +The order in which to call members of the Call Group. The supported values are Simultaneous and InOrder. + +You can only use InOrder, if the call group has 5 or less members. + +```yaml +Type: System.String +Parameter Sets: (CallGroup) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallGroupTargets +The members of the Call Group. You need to always specify the full set of members as the parameter value. What you set here will overwrite the current call group membership. + +A call group can have up to 25 members. + +```yaml +Type: System.Array of System.String +Parameter Sets: (CallGroup) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardingTarget + +The forwarding target. Supported types of values are ObjectId's, SIP addresses and phone numbers. +For phone numbers we support the following types of formats: E.164 (+12065551234 or +1206555000;ext=1234) or non-E.164 like 1234. + +Only used when ForwardingTargetType is SingleTarget. + +```yaml +Type: System.String +Parameter Sets: (Forwarding) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardingTargetType + +The forwarding target type. Supported values are Voicemail, SingleTarget, MyDelegates and Group. Voicemail is only supported for Immediate forwarding. + +SingleTarget is used when forwarding to another user or PSTN phone number. MyDelegates is used when forwarding to the users's delegates (there needs to be at least 1 +delegate). Group is used when forwarding to the user's call group (it needs to have at least 1 member). + +```yaml +Type: System.String +Parameter Sets: (Forwarding) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ForwardingType + +The type of forwarding to set. Supported values are Immediate and Simultaneous + +```yaml +Type: System.String +Parameter Sets: (Forwarding) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GroupMembershipDetails + +The group membership details for the specified user. It is an array of ICallGroupMembershipDetails, which is an object containing the identity of an owner of a +call group and the notification setting for the specified user for that call group. + +This parameter only exists if the specified user is a member of a call group. You can't create it, you can only change it. + +You need to always specify the full group membership details as the parameter value. What you set here will over-write the current group membership details. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ICallGroupMembershipDetails[] +Parameter Sets: (GroupMembershipDetails) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` +### -GroupNotificationOverride + +The group notification override that will be set on the specified user. The supported values are Ring, Mute and Banner. + +The initial setting is shown as Null. It means that the group notification set for the user in the call group is used. If you set GroupNotificationOverride to Mute, that setting will override the group notification for the user in the call group. If you set the GroupNotificationOverride to Ring or Banner, the group notification set for the user in the call group will be used. + +```yaml +Type: System.String +Parameter Sets: (GroupNotificationOverride) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Identity of the user to set call forwarding, simultaneous ringing and call group settings for. Can be specified using the ObjectId or the SIP address. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsForwardingEnabled + +This parameter controls whether forwarding is enabled or not. + +```yaml +Type: System.Boolean +Parameter Sets: (ForwardingOnOff,Forwarding) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsUnansweredEnabled + +This parameter controls whether forwarding for unanswered calls is enabled or not. + +```yaml +Type: System.Boolean +Parameter Sets: (UnansweredOnOff,Unanswered) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnansweredDelay + +The time the call will ring the user before it is forwarded to the unanswered target. The supported format is hh:mm:ss and the delay range needs to be between 10 and +60 seconds in 10 seconds increments, i.e. 00:00:10, 00:00:20, 00:00:30, 00:00:40, 00:00:50 and 00:01:00. The default value is 20 seconds. + +```yaml +Type: System.String +Parameter Sets: (Unanswered) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnansweredTarget + +The unanswered target. Supported type of values are ObjectId, SIP address and phone number. +For phone numbers we support the following types of formats: E.164 (+12065551234 or +1206555000;ext=1234) or non-E.164 like 1234. + +Only used when UnansweredTargetType is SingleTarget. + +```yaml +Type: System.String +Parameter Sets: (Unanswered) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UnansweredTargetType + +The unanswered target type. Supported values are Voicemail, SingleTarget, MyDelegates and Group. + +SingleTarget is used when forwarding the unanswered call to another user or phone number. MyDelegates is used when forwarding the unanswered call to the users's +delegates. Group is used when forwarding the unanswered call to the specified user's call group. + +```yaml +Type: System.String +Parameter Sets: (Unanswered) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PowerShell module 4.0.0 or later. + +The specified user need to have the Microsoft Phone System license assigned. + +When forwarding to MyDelegates, the specified user needs to have one or more delegates defined that are allowed to receive calls. When forwarding to Group, the +specified user needs to have one or more members of the user's call group. + +The cmdlet is validating the different settings and is always writing all the parameters in a settings group. You might see validation errors from the cmdlet due to +this behavior. As an example, if you have ForwardingTargetType set to Group and you want to remove all members of the call group, you will get a validation error. + +You can specify a SIP URI without 'sip:' on input, but the output from Get-CsUserCallingSettings will show the full SIP URI. + +You are not able to configure delegates via this cmdlet. Please use New-CsUserCallingDelegate, Set-CsUserCallingDelegate cmdlets and Remove-CsUserCallingDelegate. + +## RELATED LINKS +[Get-CsUserCallingSettings](https://learn.microsoft.com/powershell/module/teams/get-csusercallingsettings) + +[New-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/new-csusercallingdelegate) + +[Set-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/set-csusercallingdelegate) + +[Remove-CsUserCallingDelegate](https://learn.microsoft.com/powershell/module/teams/remove-csusercallingdelegate) diff --git a/skype/skype-ps/skype/Set-CsVideoInteropServiceProvider.md b/teams/teams-ps/teams/Set-CsVideoInteropServiceProvider.md similarity index 85% rename from skype/skype-ps/skype/Set-CsVideoInteropServiceProvider.md rename to teams/teams-ps/teams/Set-CsVideoInteropServiceProvider.md index 8bc0c0f7e5..87c3b8383b 100644 --- a/skype/skype-ps/skype/Set-CsVideoInteropServiceProvider.md +++ b/teams/teams-ps/teams/Set-CsVideoInteropServiceProvider.md @@ -1,14 +1,14 @@ --- external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/set-csvideointeropserviceprovider -applicable: Skype for Business Online -Module Name: Skype for Business Online +online version: https://learn.microsoft.com/powershell/module/teams/set-csvideointeropserviceprovider +applicable: Microsoft Teams +Module Name: MicrosoftTeams title: Set-CsVideoInteropServiceProvider schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Set-CsVideoInteropServiceProvider @@ -49,7 +49,7 @@ This example enables a VTC device joining anonymously to shown in the meeting as ## PARAMETERS ### -AadApplicationIds -This is an optional parameter. A semicolon separated list of AAD AppIds of the CVI partner bots can be specified in this parameter. This parameter works in conjunction with AllowAppGuestJoinsAsAuthenticated. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of these bots, is shown in the meeting as an authenticated tenant entity. +This is an optional parameter. A semicolon separated list of Microsoft Entra AppIds of the CVI partner bots can be specified in this parameter. This parameter works in conjunction with AllowAppGuestJoinsAsAuthenticated. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of these bots, is shown in the meeting as an authenticated tenant entity. ```yaml Type: String @@ -65,7 +65,7 @@ Accept wildcard characters: False ### -AllowAppGuestJoinsAsAuthenticated This is an optional parameter. Default = false. -This parameter works in conjunction with AadApplicationIds. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of the bots AAD application ids specified in AadApplicationIds, is shown in the meeting as an authenticated tenant entity. +This parameter works in conjunction with AadApplicationIds. When AllowAppGuestJoinsAsAuthenticated is set to true, a VTC device joining anonymously using any of the bots Microsoft Entra application ids specified in AadApplicationIds, is shown in the meeting as an authenticated tenant entity. ```yaml Type: Boolean @@ -201,14 +201,12 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS ### System.Management.Automation.PSObject - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Set-Team.md b/teams/teams-ps/teams/Set-Team.md index 67fd3a91d0..ec7260f07c 100644 --- a/teams/teams-ps/teams/Set-Team.md +++ b/teams/teams-ps/teams/Set-Team.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/set-team +online version: https://learn.microsoft.com/powershell/module/teams/set-team +title: Set-Team schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -23,7 +24,7 @@ Set-Team -GroupId <String> [-DisplayName <String>] [-Description <String>] [-Mai [-AllowAddRemoveApps <Boolean>] [-AllowCreateUpdateRemoveTabs <Boolean>] [-AllowCreateUpdateRemoveConnectors <Boolean>] [-AllowUserEditMessages <Boolean>] [-AllowUserDeleteMessages <Boolean>] [-AllowOwnerDeleteMessages <Boolean>] [-AllowTeamMentions <Boolean>] - [-AllowChannelMentions <Boolean>] [-ShowInTeamsSearchAndSuggestions <Boolean>] [<CommonParameters>] + [-AllowChannelMentions <Boolean>] [-ShowInTeamsSearchAndSuggestions <Boolean>] [-AllowCreatePrivateChannels <Boolean>] [<CommonParameters>] ``` ## DESCRIPTION @@ -375,13 +376,12 @@ Accept wildcard characters: False ``` ### -ShowInTeamsSearchAndSuggestions -Setting that determines whether or not private teams should be searchable from Teams clients for users who do not belong to that team. Set to $false to make those teams not discoverable from Teams clients. +The parameter has been deprecated. ```yaml Type: Boolean Parameter Sets: (All) Aliases: - Required: False Position: Named Default value: None @@ -389,10 +389,23 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AllowCreatePrivateChannels +Determines whether private channel creation is allowed for the team. + +```yaml +Type: Boolean +Parameter Sets: CreateTeam +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -402,7 +415,6 @@ For more information, see about_CommonParameters (https://go.microsoft.com/fwlin ## RELATED LINKS -[Get-Team]() - -[New-Team]() +[Get-Team](https://learn.microsoft.com/powershell/module/teams/get-team) +[New-Team](https://learn.microsoft.com/powershell/module/teams/new-team) diff --git a/teams/teams-ps/teams/Set-TeamArchivedState.md b/teams/teams-ps/teams/Set-TeamArchivedState.md index d57f366243..5b3b53ee89 100644 --- a/teams/teams-ps/teams/Set-TeamArchivedState.md +++ b/teams/teams-ps/teams/Set-TeamArchivedState.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml -Module Name: microsoftteams -online version: https://docs.microsoft.com/powershell/module/teams/set-teamarchivedstate +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-teamarchivedstate +title: Set-TeamArchivedState schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -38,7 +39,7 @@ This example sets the group with id 105b16e2-dc55-4f37-a922-97551e9e862d as arch PS C:\> Set-TeamArchivedState -GroupId 105b16e2-dc55-4f37-a922-97551e9e862d -Archived:$true -SetSpoSiteReadOnlyForMembers:$true ``` -This example sets the group with id 105b16e2-dc55-4f37-a922-97551e9e862d as archived and makes the SharePoint site read-only for team members. +This example sets the group with id 105b16e2-dc55-4f37-a922-97551e9e862d as archived and makes the SharePoint site read-only for team members. ### Example 3 ```powershell @@ -104,6 +105,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/Set-TeamChannel.md b/teams/teams-ps/teams/Set-TeamChannel.md index 49d2c2c80d..14b6fa83e6 100644 --- a/teams/teams-ps/teams/Set-TeamChannel.md +++ b/teams/teams-ps/teams/Set-TeamChannel.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/set-teamchannel +online version: https://learn.microsoft.com/powershell/module/teams/set-teamchannel +title: Set-TeamChannel schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -24,7 +25,7 @@ Set-TeamChannel -GroupId <String> -CurrentDisplayName <String> [-NewDisplayName ## DESCRIPTION > [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. +> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here `https://www.poshtestgallery.com/packages/MicrosoftTeams`. ## EXAMPLES @@ -99,8 +100,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Set-TeamFunSettings.md b/teams/teams-ps/teams/Set-TeamFunSettings.md index 0f8a585762..b0c4f9d5ab 100644 --- a/teams/teams-ps/teams/Set-TeamFunSettings.md +++ b/teams/teams-ps/teams/Set-TeamFunSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Set-TeamFunSettings -online version: https://docs.microsoft.com/powershell/module/teams/set-teamfunsettings +online version: https://learn.microsoft.com/powershell/module/teams/set-teamfunsettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -127,4 +127,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-TeamGuestSettings.md b/teams/teams-ps/teams/Set-TeamGuestSettings.md index ee28008ee9..97674abb46 100644 --- a/teams/teams-ps/teams/Set-TeamGuestSettings.md +++ b/teams/teams-ps/teams/Set-TeamGuestSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Set-TeamGuestSettings -online version: https://docs.microsoft.com/powershell/module/teams/set-teamguestsettings +online version: https://learn.microsoft.com/powershell/module/teams/set-teamguestsettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -95,4 +95,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-TeamMemberSettings.md b/teams/teams-ps/teams/Set-TeamMemberSettings.md index 7520442257..0e21dfe1c8 100644 --- a/teams/teams-ps/teams/Set-TeamMemberSettings.md +++ b/teams/teams-ps/teams/Set-TeamMemberSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Set-TeamMemberSettings -online version: https://docs.microsoft.com/powershell/module/teams/set-teammembersettings +online version: https://learn.microsoft.com/powershell/module/teams/set-teammembersettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -156,4 +156,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-TeamMessagingSettings.md b/teams/teams-ps/teams/Set-TeamMessagingSettings.md index 323339a72f..eebbf86afa 100644 --- a/teams/teams-ps/teams/Set-TeamMessagingSettings.md +++ b/teams/teams-ps/teams/Set-TeamMessagingSettings.md @@ -3,10 +3,10 @@ external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams applicable: Microsoft Teams title: Set-TeamMessagingSettings -online version: https://docs.microsoft.com/powershell/module/teams/set-teammessagingsettings +online version: https://learn.microsoft.com/powershell/module/teams/set-teammessagingsettings schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -158,4 +158,3 @@ Accept wildcard characters: False ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Set-TeamPicture.md b/teams/teams-ps/teams/Set-TeamPicture.md index 998c93f0e7..eeb537153b 100644 --- a/teams/teams-ps/teams/Set-TeamPicture.md +++ b/teams/teams-ps/teams/Set-TeamPicture.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/set-teampicture +online version: https://learn.microsoft.com/powershell/module/teams/set-teampicture +title: Set-TeamPicture schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -14,8 +15,8 @@ ms.reviewer: Update the team picture. -Note: the command will return immediately, but the Teams application will not reflect the update immediately. -The Teams application may need to be open for up to an hour before changes are reflected. +Note: the command will return immediately, but the Teams application will not reflect the update immediately. +The Teams application may need to be open for up to an hour before changes are reflected. Note: this cmdlet is not support in special government environments (TeamsGCCH and TeamsDoD) and is currently only supported in our beta release. @@ -27,15 +28,11 @@ Set-TeamPicture -GroupId <String> -ImagePath <String> [<CommonParameters>] ## DESCRIPTION -> [!IMPORTANT] -> Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here <https://www.poshtestgallery.com/packages/MicrosoftTeams>. - - ## EXAMPLES ### Example 1 ``` -Set-TeamPicture -GroupId 2f162b0e-36d2-4e15-8ba3-ba229cecdccf -ImagePath c:\Image\TeamPictire.png +Set-TeamPicture -GroupId 2f162b0e-36d2-4e15-8ba3-ba229cecdccf -ImagePath c:\Image\TeamPicture.png ``` ## PARAMETERS @@ -71,8 +68,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS diff --git a/teams/teams-ps/teams/Set-TeamTargetingHierarchy.md b/teams/teams-ps/teams/Set-TeamTargetingHierarchy.md new file mode 100644 index 0000000000..4f8a952534 --- /dev/null +++ b/teams/teams-ps/teams/Set-TeamTargetingHierarchy.md @@ -0,0 +1,93 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/connect-microsoftteams +title: Set-TeamTargetingHierarchy +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- +# Set-TeamTargetingHierarchy + +## SYNOPSIS + +Upload a hierarchy to the tenant. A tenant may only have 1 active hierarchy. Each Set-TeamTargetingHierarchy cmdlet call will overwrite the previous one. + +## SYNTAX + +### Get (Default) +``` +Set-TeamTargetingHierarchyStatus [-FilePath <String>] [-ApiVersion <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +A sample CSV file uses the following format: + +`TargetName,ParentName,TeamId,Location:Clothing,Location:Jewelry,#Bucket1,#Bucket2`<br>`Apogee,,A8A6626F-87B3-4B8A-9469-47BCD1174673,0,0`<br>`New Jersey,Apogee,06763207-4F56-4DFE-96AE-4C7F9ADCFB43,0,0`<br>`Basking Ridge,NewJersey,5F44CC65-9521-4F7F-9099-64320153CA07,1,0`<br>`Mountain Lakes,NewJersey,58A21379-8E4D-4DA5-AA35-9CC188D8A998,0,1` + +Based on the CSV file, the following hierarchy is created: + +- Apogee +-    New Jersey +-       Basking Ridge +-       Mountain Lakes + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-TeamTargetingHierarchy -FilePath d:\hier.csv + +Key Value +--- ----- +requestId c67e86109d88479e9708c3b7e8ff7217 +``` + +## PARAMETERS + +### -FilePath +Specifies the path to a CSV file that defines the hierarchy. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiVersion +The version of the Hierarchy APIs to use. Valid values are: 1 or 2. + +Currently only available in preview from version 6.6.1-preview. Specifying "-ApiVersion 2" will direct cmdlet requests to the newer version of the Hierarchy APIs. This integration is currently in preview/beta mode so customers should not try it on their production workloads but are welcome to try it on test workloads. This is an optional parameter and not specifying it will be interpreted as specifying "-ApiVersion 1", which will continue to direct cmdlet requests to the original version of the Hierarchy APIs until we upgrade production to v2, at which time we will set the default to 2. We do not expect this to have any impact on your cmdlet usage or existing scripts. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 1 +Accept pipeline input: false +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Get-TeamTargetingHierarchyStatus](https://learn.microsoft.com/powershell/module/teams/get-teamtargetinghierarchystatus) diff --git a/teams/teams-ps/teams/Set-TeamsApp.md b/teams/teams-ps/teams/Set-TeamsApp.md index 3b9e4c77f6..3f493249cb 100644 --- a/teams/teams-ps/teams/Set-TeamsApp.md +++ b/teams/teams-ps/teams/Set-TeamsApp.md @@ -1,7 +1,8 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/set-teamsapp +online version: https://learn.microsoft.com/powershell/module/teams/set-teamsapp +title: Set-TeamsApp schema: 2.0.0 --- @@ -59,14 +60,12 @@ Accept wildcard characters: False ``` ### 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 (http://go.microsoft.com/fwlink/?LinkID=113216). +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS ### None - ## OUTPUTS ### System.Object diff --git a/teams/teams-ps/teams/Set-TeamsEnvironmentConfig.md b/teams/teams-ps/teams/Set-TeamsEnvironmentConfig.md new file mode 100644 index 0000000000..81c1a3382e --- /dev/null +++ b/teams/teams-ps/teams/Set-TeamsEnvironmentConfig.md @@ -0,0 +1,142 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Connect.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/set-teamsenvironmentconfig +title: Set-TeamsEnvironmentConfig +schema: 2.0.0 +author: VikneshMSFT +ms.author: vimohan +ms.reviewer: pbafna +manager: vinelap +--- + +# Set-TeamsEnvironmentConfig + +## SYNOPSIS + +Sets environment-specific configurations on the local machine and is used to connect to the right environment when running Connect-MicrosoftTeams. + +## SYNTAX + +``` +Set-TeamsEnvironmentConfig [-EndpointUris <Hashtable>] [-TeamsEnvironmentName <String>] [-WhatIf] [-Confirm] + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet sets environment-specific configurations like endpoint URIs(such as Microsoft Entra ID and Microsoft Graph) and Teams environment (such as GCCH and DOD) on the local machine. + +When running Connect-MicrosoftTeams, environment-specific information set in this cmdlet will be considered unless overridden by Connect-MicrosoftTeams parameters. + +Parameters passed to Connect-MicrosoftTeams will take precedence over the information set by this cmdlet. + +Clear-TeamsEnvironmentConfig should not be used in Commercial, GCC, GCC High, or DoD environments. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Set-TeamsEnvironmentConfig -TeamsEnvironmentName TeamsChina +``` + +Sets the environment as Gallatin China on a local machine and when Connect-MicrosoftTeams is run, authentication will happen in the Gallatin China cloud and Microsoft Teams module will connect to the Gallatin environment. + +### Example 2 +```powershell +$endPointUriDict = @{ActiveDirectory = 'https://login.microsoftonline.us/';MsGraphEndpointResourceId = 'https://graph.microsoft.us/'} +Set-TeamsEnvironmentConfig -TeamsEnvironmentName $endPointUriDict +``` +Sets endpoint URIs required for special clouds. + +### Example 3 +```powershell +Set-TeamsEnvironmentConfig -TeamsEnvironmentName TeamsChina + +$cred=get-credential +Move-CsUser -Identity "PilarA@contoso.com" -Target "sipfed.online.lync.com" -Credential $cred +``` +This cmdlet is mainly introduced to support Skype for Business to Microsoft Teams user migration using Move-CsUser. + +This example shows how tenant admins can run Move-CsUser in Gallatin and other special clouds after setting the environment configuration using Set-TeamsEnvironmentConfig. + +Note that Set-TeamsEnvironmentConfig needs to be run only once for each machine. There is no need to run it each time before running Move-CsUser. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EndpointUris +Provides custom endpoints. + +```yaml +Type: Hashtable +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TeamsEnvironmentName +Provides a Teams environment to connect to, for example, Teams GCCH or Teams DoD. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +Set-TeamsEnvironmentConfig should not be used in Commercial, GCC, GCC High, or DoD environments. + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Start-CsExMeetingMigration.md b/teams/teams-ps/teams/Start-CsExMeetingMigration.md new file mode 100644 index 0000000000..411d082929 --- /dev/null +++ b/teams/teams-ps/teams/Start-CsExMeetingMigration.md @@ -0,0 +1,114 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/start-csexmeetingmigration +applicable: Microsoft Teams +title: Start-CsExMeetingMigration +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Start-CsExMeetingMigration + +## SYNOPSIS +This cmdlet manually trigger a meeting migration request for the specified user. + +## SYNTAX + +``` +Start-CsExMeetingMigration [-SourceMeetingType <MmsSourceMeetingTypes>] [-TargetMeetingType <MmsTargetMeetingTypes>] [-Identity] <UserIdParameter> [<CommonParameters>] +``` + +## DESCRIPTION +Meeting Migration Service (MMS) is a Skype for Business service that runs in the background and automatically updates Skype for Business and Microsoft Teams meetings for users. +MMS is designed to eliminate the need for users to run the Meeting Migration Tool to update their Skype for Business and Microsoft Teams meetings. + +Also, with `Start-CsExMeetingMigration` cmdlet, you can start a meeting migration manually. For more information about requirements of the Meeting Migration Service (MMS), see [Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms). + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Start-CsExMeetingMigration -Identity ashaw@contoso.com -TargetMeetingType Teams +``` + +This example below shows how to initiate meeting migration for user ashaw@contoso.com so that all meetings are migrated to Teams. + +## PARAMETERS + +### -Identity +Specifies the Identity of the user account to be modified. A user identity can be specified by using one of four formats: +1. The user's SIP address +2. The user's user principal name (UPN) +3. The user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) +4. The user's Active Directory display name (for example, Ken Myer). You can also reference a user account by using the user's Active Directory distinguished name. + +```yaml +Type: UserIdParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SourceMeetingType +The possible values are: +* **All:** indicates that both Skype for Business meetings and Teams meetings should be updated. This is the **default value**. +* **SfB:** indicates that only Skype for Business meetings (whether on-premises or online) should be updated. +* **Teams:** indicates that only Teams meetings should be updated. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: All +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TargetMeetingType +The possible values are: +* **Current:** specifies that Skype for Business meetings remain Skype for Business meetings and Teams meetings remain Teams meetings. However audio conferencing coordinates might be changed, and any on-premises Skype for Business meetings would be migrated to Skype for Business Online. This is the **default value**. +* **Teams:** specifies that any existing meeting must be migrated to Teams, regardless of whether the meeting is hosted in Skype for Business online or on-premises, and regardless of whether any audio conferencing updates are required. + +```yaml +Type: Object +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: Current +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS +[Using the Meeting Migration Service (MMS)](https://learn.microsoft.com/SkypeForBusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms) + +[Get-CsMeetingMigrationStatus](https://learn.microsoft.com/powershell/module/teams/get-csmeetingmigrationstatus) + +[Set-CsTenantMigrationConfiguration](https://learn.microsoft.com/powershell/module/teams/set-cstenantmigrationconfiguration) + +[Get-CsTenantMigrationConfiguration](https://learn.microsoft.com/powershell/module/teams/get-cstenantmigrationconfiguration) diff --git a/teams/teams-ps/teams/Sync-CsOnlineApplicationInstance.md b/teams/teams-ps/teams/Sync-CsOnlineApplicationInstance.md new file mode 100644 index 0000000000..8076e411c3 --- /dev/null +++ b/teams/teams-ps/teams/Sync-CsOnlineApplicationInstance.md @@ -0,0 +1,169 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/sync-csonlineapplicationinstance +applicable: Microsoft Teams +title: Sync-CsOnlineApplicationInstance +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +manager: naveenv +ms.reviewer: +--- + +# Sync-CsOnlineApplicationInstance + +## SYNOPSIS +Use the Sync-CsOnlineApplicationInstance cmdlet to sync the application instance from Microsoft Entra ID into Agent Provisioning Service. This is needed because the mapping between application instance and application needs to be stored in Agent Provisioning Service. If an application ID was provided at the creation of the application instance, you need not run this cmdlet. + +## SYNTAX + +``` +Sync-CsOnlineApplicationInstance -ObjectId <guid> [-CallbackUri <string>] [-Force] [-ApplicationId <guid>] [-AcsResourceId <guid>] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +Use the Sync-CsOnlineApplicationInstance cmdlet to sync application instances from Microsoft Entra ID into Agent Provisioning Service. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Sync-CsOnlineApplicationInstance -ObjectId xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -ApplicationId yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy +``` + +This example sync application instance with object ID "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" and application ID "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy" into Agent Provisioning Service. + +### -------------------------- Example 2 -------------------------- +```powershell +Sync-CsOnlineApplicationInstance -ObjectId xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -ApplicationId 00000000-0000-0000-0000-000000000000 +``` +This command is helpful when there's already a mapping in Agent Provisioning Service and you want to set a different app ID value. In this case, when running the cmdlet in example 1, you will see `Sync-CsOnlineApplicationInstance : An item with the same key has already been added.`. + +The command removes the mapping for application instance with object ID "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx". Run the example cmdlet again to create the mapping in Agent Provisioning Service. + +## PARAMETERS + +### -CallbackUri +This parameter is reserved for internal Microsoft use. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ObjectId +The application instance ID. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApplicationId +The application ID. The Microsoft application Auto Attendant has the ApplicationId ce933385-9390-45d1-9512-c8d228074e07 and the Microsoft application Call Queue has the ApplicationId 11cd3e2e-fccb-42ad-ad00-878b93575e07. Third-party applications available in a tenant will use other ApplicationId's. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AcsResourceId +The ACS Resource ID. The unique identifier assigned to an instance of Azure Communication Services within the Azure cloud infrastructure. + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +This switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If it isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[Set-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/set-csonlineapplicationinstance) + +[New-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/new-csonlineapplicationinstance) + +[Find-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/find-csonlineapplicationinstance) + +[Get-CsOnlineApplicationInstance](https://learn.microsoft.com/powershell/module/teams/get-csonlineapplicationinstance) diff --git a/skype/skype-ps/skype/Test-CsEffectiveTenantDialPlan.md b/teams/teams-ps/teams/Test-CsEffectiveTenantDialPlan.md similarity index 85% rename from skype/skype-ps/skype/Test-CsEffectiveTenantDialPlan.md rename to teams/teams-ps/teams/Test-CsEffectiveTenantDialPlan.md index cc6c339ff6..1402626383 100644 --- a/skype/skype-ps/skype/Test-CsEffectiveTenantDialPlan.md +++ b/teams/teams-ps/teams/Test-CsEffectiveTenantDialPlan.md @@ -1,13 +1,13 @@ --- -external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml -online version: https://docs.microsoft.com/powershell/module/skype/test-cseffectivetenantdialplan -applicable: Skype for Business Online +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/test-cseffectivetenantdialplan +applicable: Microsoft Teams title: Test-CsEffectiveTenantDialPlan schema: 2.0.0 manager: bulenteg author: tomkau ms.author: tomkau -ms.reviewer: +ms.reviewer: williamlooney --- # Test-CsEffectiveTenantDialPlan @@ -39,8 +39,7 @@ The `Test-CsEffectiveTenantDialPlan` cmdlet normalizes the dialed number by appl Get-CsEffectiveTenantDialPlan -Identity adelev | Test-CsEffectiveTenantDialPlan -DialedNumber 14258828080 ``` -This example gets the Identity of a dial plan that is associated with the identity of an user, and applies the retrieved tenant dial plan to normalize the dialed number. - +This example gets the Identity of a dial plan that is associated with the identity of a user, and applies the retrieved tenant dial plan to normalize the dialed number. ### -------------------------- Example 2 -------------------------- ``` @@ -49,7 +48,6 @@ Test-CsEffectiveTenantDialPlan -DialedNumber 14258828080 -Identity adelev@contos This example tests the given dialed number against a specific identity. - ## PARAMETERS ### -DialedNumber @@ -58,8 +56,8 @@ The DialedNumber parameter is the phone number to be normalized with the effecti ```yaml Type: PhoneNumber Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -74,8 +72,8 @@ Indicates the identity of the user account to be tested against. The user's SIP ```yaml Type: UserIdParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -91,7 +89,7 @@ The Confirm switch causes the command to pause processing, and requires confirma Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -108,8 +106,8 @@ If the Force switch isn't provided in the command, you're prompted for administr ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -126,7 +124,7 @@ By using this switch, you can view what changes would occur without having to co Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Skype for Business Online +applicable: Microsoft Teams Required: False Position: Named @@ -141,8 +139,8 @@ The EffectiveTenantDialPlanName parameter is the effective tenant dial plan name ```yaml Type: String Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -157,8 +155,8 @@ Runs the test only against Tenant-level dial plans (does not take into account S ```yaml Type: SwitchParameter Parameter Sets: (All) -Aliases: -Applicable: Skype for Business Online +Aliases: +applicable: Microsoft Teams Required: False Position: Named @@ -168,7 +166,7 @@ Accept wildcard characters: False ``` ### 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/?LinkID=113216). +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/?LinkID=113216). ## INPUTS @@ -177,4 +175,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES ## RELATED LINKS - diff --git a/teams/teams-ps/teams/Test-CsInboundBlockedNumberPattern.md b/teams/teams-ps/teams/Test-CsInboundBlockedNumberPattern.md new file mode 100644 index 0000000000..56da11fbfd --- /dev/null +++ b/teams/teams-ps/teams/Test-CsInboundBlockedNumberPattern.md @@ -0,0 +1,113 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/test-csinboundblockednumberpattern +applicable: Microsoft Teams +title: Test-CsInboundBlockedNumberPattern +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Test-CsInboundBlockedNumberPattern + +## SYNOPSIS +This cmdlet tests the given number against the created (by using New-CsInboundBlockedNumberPattern cmdlet) blocked numbers pattern. + +## SYNTAX + +``` +Test-CsInboundBlockedNumberPattern -PhoneNumber <String> [-TenantId <Guid>] [-WhatIf] + [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet tests the given number against the created (by using New-CsInboundBlockedNumberPattern cmdlet) blocked numbers pattern. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Test-CsInboundBlockedNumberPattern -PhoneNumber "321321321" +``` + +Tests the "321321321" number to check if it will be blocked for inbound calls. + +## PARAMETERS + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PhoneNumber +The phone number to be tested. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -TenantId +This parameter is reserved for internal Microsoft use. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +### System.Guid + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md b/teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md new file mode 100644 index 0000000000..7d7fd3966d --- /dev/null +++ b/teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md @@ -0,0 +1,112 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Test-CsTeamsShiftsConnectionValidate +author: gucsun +ms.author: gucsun +manager: navinth +online version: https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate +schema: 2.0.0 +--- + +# Test-CsTeamsShiftsConnectionValidate + +## SYNOPSIS + +This cmdlet validates workforce management (WFM) connection settings. + +## SYNTAX + +``` +Test-CsTeamsShiftsConnectionValidate -ConnectorId <string> -ConnectorSpecificSettings <IConnectorInstanceRequestConnectorSpecificSettings> -Name <string> [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet validates Workforce management (WFM) connection settings. It validates that the provided WFM account/password and required endpoints are set correctly. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> $InstanceName = "test instance name" +PS C:\> $WfmUserName = "WfmUserName" +PS C:\> $plainPwd = "plainPwd" +PS C:\> Test-CsTeamsShiftsConnectionValidate -ConnectorId "6A51B888-FF44-4FEA-82E1-839401E00000" -ConnectorSpecificSettings (New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificBlueYonderSettingsRequest -Property @{ AdminApiUrl = "https://contoso.com/retail/data/wfmadmin/api/v1-beta3"; SiteManagerUrl = "https://contoso.com/retail/data/wfmsm/api/v1-beta4"; EssApiUrl = "https://contoso.com/retail/data/wfmess/api/v1-beta2"; RetailWebApiUrl = "https://contoso.com/retail/data/retailwebapi/api/v1"; CookieAuthUrl = "https://contoso.com/retail/data/login"; FederatedAuthUrl = "https://contoso.com/retail/data/login"; LoginUserName = "PlaceholderForUsername"; LoginPwd = "PlaceholderForPassword" }) -Name $InstanceName +``` + +Returns the list of conflicts if there are any. Empty result means there's no conflict. + +### Example 2 +```powershell +PS C:\> $InstanceName = "test instance name" +PS C:\> $WfmUserName = "WfmUserName" +PS C:\> $plainPwd = "plainPwd" +PS C:\> Test-CsTeamsShiftsConnectionValidate -ConnectorId "6A51B888-FF44-4FEA-82E1-839401E00000" -ConnectorSpecificSettings (New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificUkgDimensionsSettingsRequest -Property @{ apiUrl = "https://contoso.com/api"; ssoUrl = "https://contoso.com/sso"; appKey = "myAppKey"; clientId = "myClientId"; clientSecret = "PlaceholderForClientSecret"; LoginUserName = "PlaceholderForUsername"; LoginPwd = "PlaceholderForPassword" }) -Name $InstanceName +``` + +Returns the list of conflicts if there are any. Empty result means there's no conflict. + +## PARAMETERS + +### -ConnectorId + +The ID of the shifts connector. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name + +The connector's instance name. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorSpecificSettings +The connector specific settings. + +```yaml +Type: IConnectorInstanceRequestConnectorSpecificSettings +Parameter Sets: NewExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS + +[New-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectioninstance) + +[Set-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnectioninstance) diff --git a/teams/teams-ps/teams/Test-CsTeamsTranslationRule.md b/teams/teams-ps/teams/Test-CsTeamsTranslationRule.md new file mode 100644 index 0000000000..42891b66a8 --- /dev/null +++ b/teams/teams-ps/teams/Test-CsTeamsTranslationRule.md @@ -0,0 +1,84 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/test-csteamstranslationrule +applicable: Microsoft Teams +title: Test-CsTeamsTranslationRule +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +--- + +# Test-CsTeamsTranslationRule + +## SYNOPSIS +This cmdlet tests a phone number against the configured number manipulation rules and returns information about the matching rule. + +## SYNTAX + +### Test (Default) +```powershell +Test-CsTeamsTranslationRule [-PhoneNumber <string>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet tests a phone number against the configured number manipulation rules and returns information about the matching rule. + +## EXAMPLES + +### Example 1 +```powershell +Test-CsTeamsTranslationRule -PhoneNumber 1234 +``` +```output +Identity Pattern PhoneNumberTranslated Translation +-------- ------- --------------------- ----------- +rule1 ^1234$ 4321 4321 +``` +This example displays information about the manipulation rule matching the phone number 1234. + +## PARAMETERS + +### -PhoneNumber +The phone number to test. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: True +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### None + +## NOTES +The cmdlet is available in Teams PowerShell Module 4.5.0 or later. + +The matching logic used in the cmdlet is the same as when the manipulation rule has been associated with an SBC and a call is being routed. + +If a match is found in two or more manipulation rules, the first one is returned. + +There is a short delay before newly created manipulation rules are added to the evaluation. + +## RELATED LINKS +[New-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/new-csteamstranslationrule) + +[Get-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/get-csteamstranslationrule) + +[Set-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/set-csteamstranslationrule) + +[Remove-CsTeamsTranslationRule](https://learn.microsoft.com/powershell/module/teams/remove-csteamstranslationrule) diff --git a/teams/teams-ps/teams/Test-CsTeamsUnassignedNumberTreatment.md b/teams/teams-ps/teams/Test-CsTeamsUnassignedNumberTreatment.md new file mode 100644 index 0000000000..1682ef0ba6 --- /dev/null +++ b/teams/teams-ps/teams/Test-CsTeamsUnassignedNumberTreatment.md @@ -0,0 +1,73 @@ +--- +external help file: Microsoft.TeamsCmdlets.Powershell.Custom.dll-Help.xml +online version: https://learn.microsoft.com/powershell/module/teams/test-csteamsunassignednumbertreatment +Module Name: Microsoft Teams +title: Test-CsTeamsUnassignedNumberTreatment +author: firatakandere +ms.author: osakande +schema: 2.0.0 +--- + +# Test-CsTeamsUnassignedNumberTreatment + +## SYNOPSIS +This cmdlet tests the given number against the created (by using New-CsTeamsUnassignedNumberTreatment cmdlet) unassigned number treatment configurations. + +## SYNTAX + +``` +Test-CsTeamsUnassignedNumberTreatment -PhoneNumber <string> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet tests the given number against the created (by using New-CsTeamsUnassignedNumberTreatment cmdlet) unassigned number treatment configurations. If a match is found, the matching treatment is displayed. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Test-CsTeamsUnassignedNumberTreatment -PhoneNumber "321321321" +``` + +Tests the "321321321" number to check if there is a matching unassigned number treatment. + +## PARAMETERS + +### -PhoneNumber +The phone number to be tested. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default Value: None +Accept pipeline input: True (ByPropertyName) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String + +## OUTPUTS + +### System.Object + +## NOTES +The cmdlet is available in Teams PS module 3.2.0-preview or later. + +## RELATED LINKS + +[New-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/new-csteamsunassignednumbertreatment) + +[Get-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/get-csteamsunassignednumbertreatment) + +[Set-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/set-csteamsunassignednumbertreatment) + +[Remove-CsTeamsUnassignedNumberTreatment](https://learn.microsoft.com/powershell/module/teams/remove-csteamsunassignednumbertreatment) diff --git a/teams/teams-ps/teams/Test-CsVoiceNormalizationRule.md b/teams/teams-ps/teams/Test-CsVoiceNormalizationRule.md new file mode 100644 index 0000000000..43647176a6 --- /dev/null +++ b/teams/teams-ps/teams/Test-CsVoiceNormalizationRule.md @@ -0,0 +1,151 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/test-csvoicenormalizationrule +applicable: Microsoft Teams +title: Test-CsVoiceNormalizationRule +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +--- + +# Test-CsVoiceNormalizationRule + +## SYNOPSIS +Tests a telephone number against a voice normalization rule and returns the number after the normalization rule has been applied. +Voice normalization rules are typically used to convert a telephone dialing requirement (for example, you must dial 9 to access an outside line) to the E.164 phone +number format. +This cmdlet was introduced in Lync Server 2010. + +## SYNTAX + +``` +Test-CsVoiceNormalizationRule -DialedNumber <PhoneNumber> -NormalizationRule <NormalizationRule> + [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet allows you to see the results of applying a voice normalization rule to a given telephone number. +Voice normalization rules are a required part of phone authorization and call routing. +They define the requirements for converting--or translating-- numbers from a format typically entered by users to a standard (E.164) format. +Use this cmdlet to troubleshoot dialing issues or to verify that rules will work as expected against given numbers. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsVoiceNormalizationRule -Identity "global/11 digit number rule" | Test-CsVoiceNormalizationRule -DialedNumber 14255559999 +``` + +For Lync or Skype for Business Server, this example runs a voice normalization test against the voice normalization rule with the Identity "global/11 digit number rule". +First the `Get-CsVoiceNormalizationRule` cmdlet is run to retrieve the rule with the Identity "global/11 digit number rule". +That rule object is then piped to the `Test-CsVoiceNormalizationRule` cmdlet, where the rule is tested against the telephone number 14255559999. +The output will be the DialedNumber after the voice normalization rule "global/11 digit number rule" has been applied. +If this rule does not apply to the DialedNumber value (for example, if the normalization rule matches the pattern for an 11-digit number and you supply a 7-digit number) no value will be returned. + +### -------------------------- Example 2 -------------------------- +``` +$a = Get-CsVoiceNormalizationRule -Identity "global/11 digit number rule" +Test-CsVoiceNormalizationRule -DialedNumber 5551212 -NormalizationRule $a +``` + +For Lync or Skype for Business Server, example 2 is identical to Example 1 except that instead of piping the results of the Get operation directly to the Test cmdlet, the +object is first stored in the variable $a and then is passed as the value to the parameter NormalizationRule to be used as the voice normalization rule against which the +test will run. + +### -------------------------- Example 3 -------------------------- +``` +Get-CsVoiceNormalizationRule | Test-CsVoiceNormalizationRule -DialedNumber 2065559999 +``` + +For Lync or Skype for Business Server, this example runs a voice normalization test against all voice normalization rules defined within the Skype for Business +Server deployment. First the `Get-CsVoiceNormalizationRule` cmdlet is run (with no parameters) to retrieve all the voice normalization rules. +The collection of rules that is returned is then piped to the `Test-CsVoiceNormalizationRule` cmdlet, where each rule in the collection is tested against the telephone +number 2065559999. The output will be a list of translated numbers, one for each rule tested. +If a rule does not apply to the DialedNumber value (for example, if the normalization rule matches the pattern for an 11-digit number and you supply a 7-digit number) there +will be a blank line in the list for that rule. + +### -------------------------- Example 4 -------------------------- +```powershell +$nr=(Get-CsTenantDialPlan -Identity dp1).NormalizationRules +$nr[0] +``` +```output +Description : +Pattern : ^(\d{4})$ +Translation : +1206555$1 +Name : nr1 +IsInternalExtension : False +``` +```powershell +Test-CsVoiceNormalizationRule -DialedNumber 1234 -NormalizationRule $nr[0] +``` +```output +TranslatedNumber +---------------- ++12065551234 +``` + +For Microsoft Teams, this example gets all the normalization rules in the tenant dial plan DP1, shows the first of these rules, and then test that rule on the +dialed number 1234. The output shows that the rule normalize the dialed number to +12065551234. + +## PARAMETERS + +### -DialedNumber +The phone number against which you want to test the normalization rule specified in the NormalizationRule parameter. + +Full Data Type: Microsoft.Rtc.Management.Voice.PhoneNumber + +```yaml +Type: PhoneNumber +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NormalizationRule +An object containing a reference to the normalization rule against which you want to test the number specified in the DialedNumber parameter. + +For Lync and Skype for Business Server, you can retrieve voice normalization rules by calling the `Get-CsVoiceNormalizationRule` cmdlet. +For Microsoft Teams, you can retrieve voice normalization rules by calling the `Get-CsTenantDialPlan` cmdlet. + +```yaml +Type: NormalizationRule +Parameter Sets: (All) +Aliases: +Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Microsoft Teams + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByPropertyName, ByValue) +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Input types +Microsoft.Rtc.Management.WritableConfig.Policy.Voice.NormalizationRule object. +Accepts pipelined input of voice normalization rule objects. + +## OUTPUTS + +### Output types +Returns an object of type Microsoft.Rtc.Management.Voice.NormalizationRuleTestResult. + +## NOTES + +## RELATED LINKS + +[New-CsVoiceNormalizationRule](https://learn.microsoft.com/powershell/module/teams/new-csvoicenormalizationrule) + +[Get-CsTenantDialPlan](https://learn.microsoft.com/powershell/module/teams/get-cstenantdialplan) diff --git a/teams/teams-ps/teams/Unregister-CsOnlineDialInConferencingServiceNumber.md b/teams/teams-ps/teams/Unregister-CsOnlineDialInConferencingServiceNumber.md new file mode 100644 index 0000000000..a2f7712c39 --- /dev/null +++ b/teams/teams-ps/teams/Unregister-CsOnlineDialInConferencingServiceNumber.md @@ -0,0 +1,193 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/unregister-csonlinedialinconferencingservicenumber +applicable: Microsoft Teams +title: Unregister-CsOnlineDialInConferencingServiceNumber +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Unregister-CsOnlineDialInConferencingServiceNumber + +## SYNOPSIS +Unassigns the previously assigned service number as default Conference Bridge number. + +## SYNTAX + +``` +Unregister-CsOnlineDialInConferencingServiceNumber [-Identity] <String> [-BridgeId <Guid>] + [-BridgeName <String>] [-Tenant <Guid>] [-TenantDomain <String>] [-RemoveDefaultServiceNumber] + [-DomainController <Fqdn>] [-Force] [<CommonParameters>] +``` + +## DESCRIPTION +Unassigns the previously assigned service number as default Conference Bridge number. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Unregister-CsOnlineDialInConferencingServiceNumber -BridgeName "Conference Bridge" -RemoveDefaultServiceNumber 1234 +``` + +Unassigns the 1234 Service Number to the given Conference Bridge. + +## PARAMETERS + +### -Identity +PARAMVALUE: String + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Instance +PARAMVALUE: ConferencingServiceNumber + +```yaml +Type: ConferencingServiceNumber +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BridgeId +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -BridgeName +PARAMVALUE: String + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController +PARAMVALUE: Fqdn + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: DC +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RemoveDefaultServiceNumber +PARAMVALUE: SwitchParameter + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TenantDomain +PARAMVALUE: String + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Update-CsAutoAttendant.md b/teams/teams-ps/teams/Update-CsAutoAttendant.md new file mode 100644 index 0000000000..e904781ef4 --- /dev/null +++ b/teams/teams-ps/teams/Update-CsAutoAttendant.md @@ -0,0 +1,93 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/update-csautoattendant +applicable: Microsoft Teams +title: Update-CsAutoAttendant +schema: 2.0.0 +manager: bulenteg +author: tomkau +ms.author: tomkau +ms.reviewer: williamlooney +--- + +# Update-CsAutoAttendant + +## SYNOPSIS +Use Update-CsAutoAttendant cmdlet to force an update of resources associated with an Auto Attendant (AA) provisioning. + +## SYNTAX + +```powershell +Update-CsAutoAttendant -Identity <String> [-Tenant <Guid>] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet provides a way to update the resources associated with an auto attendant configured for use in your organization. Currently, it repairs the Dial-by-Name recognition status of an auto attendant. + +Note: This cmdlet only triggers the refresh of auto attendant resources. It does not wait until all the resources have been refreshed. The last completed status of auto attendant can be retrieved using [`Get-CsAutoAttendantStatus`](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantstatus) cmdlet. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +Update-CsAutoAttendant -Identity "6abea1cd-904b-520b-be96-1092cc096432" +``` + +In Example 1, the Update-CsAutoAttendant cmdlet is used to update all resources of an auto attendant with Identity of 6abea1cd-904b-520b-be96-1092cc096432. + +## PARAMETERS + +### -Identity +The identity for the AA whose resources are to be updated. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: True +Position: 0 +Default value: None +Accept pipeline input: True +Accept wildcard characters: False +``` + +### -Tenant + +```yaml +Type: System.Guid +Parameter Sets: (All) +Aliases: +applicable: Microsoft Teams + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### System.String +The Update-CsAutoAttendant cmdlet accepts a string as the Identity parameter. + +## OUTPUTS + +### None + +## NOTES + +## RELATED LINKS + +[Get-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/get-csautoattendant) + +[Get-CsAutoAttendantStatus](https://learn.microsoft.com/powershell/module/teams/get-csautoattendantstatus) + +[Set-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/set-csautoattendant) + +[Remove-CsAutoAttendant](https://learn.microsoft.com/powershell/module/teams/remove-csautoattendant) diff --git a/teams/teams-ps/teams/Update-CsCustomPolicyPackage.md b/teams/teams-ps/teams/Update-CsCustomPolicyPackage.md new file mode 100644 index 0000000000..b993377f9a --- /dev/null +++ b/teams/teams-ps/teams/Update-CsCustomPolicyPackage.md @@ -0,0 +1,111 @@ +--- +external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml +Module Name: MicrosoftTeams +title: Update-CsCustomPolicyPackage +author: sunguchuan +ms.author: gucsun +manager: dasosby +online version: https://learn.microsoft.com/powershell/module/teams/update-cscustompolicypackage +schema: 2.0.0 +--- + +# Update-CsCustomPolicyPackage + +## SYNOPSIS + +**Note:** This cmdlet is currently in private preview. + +This cmdlet updates a custom policy package. + +## SYNTAX + +``` +Update-CsCustomPolicyPackage -Identity <String> -PolicyList <String[]> [-Description <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet updates a custom policy package with new package settings. For more information on policy packages and the policy types available, please review https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Update-CsCustomPolicyPackage -Identity "MyPackage" -PolicyList "TeamsMessagingPolicy, MyMessagingPolicy" +``` + +Updates the custom package named "MyPackage" to have one policy in the package: a messaging policy of name "MyMessagingPolicy". +### Example 2 +```powershell +PS C:\> Update-CsCustomPolicyPackage -Identity "MyPackage" -PolicyList "TeamsMessagingPolicy, MyMessagingPolicy", "TeamsMeetingPolicy, MyMeetingPolicy" -Description "My package" +``` + +Updates the custom package named "MyPackage" to have a description of "My package" and two policies in the package: a messaging policy of name "MyMessagingPolicy" and a meeting policy of name "MyMeetingPolicy". + +## PARAMETERS + +### -Identity + +The name of the custom package. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 0 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PolicyList + +A list of one or more policies to be included in the updated package. To specify the policy list, follow this format: "\<PolicyType\>, \<PolicyName\>". Delimiters of ' ', '.', ':', '\t' are also acceptable. Supported policy types are listed [here](https://learn.microsoft.com/MicrosoftTeams/manage-policy-packages#what-is-a-policy-package). To get the list of available policy names on your tenant, use the skypeforbusiness module and refer to cmdlets such as [Get-CsTeamsMeetingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmeetingpolicy) and [Get-CsTeamsMessagingPolicy](https://learn.microsoft.com/powershell/module/teams/get-csteamsmessagingpolicy). + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +The description of the custom package. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +## NOTES +The resulting custom package's contents will be replaced by the new one instead of a union. Default packages created by Microsoft cannot be updated. + +## RELATED LINKS + +[Get-CsPolicyPackage](https://learn.microsoft.com/powershell/module/teams/get-cspolicypackage) + +[New-CsCustomPolicyPackage](https://learn.microsoft.com/powershell/module/teams/new-cscustompolicypackage) + +[Remove-CsCustomPolicyPackage](https://learn.microsoft.com/powershell/module/teams/remove-cscustompolicypackage) diff --git a/teams/teams-ps/teams/Update-CsPhoneNumberTag.md b/teams/teams-ps/teams/Update-CsPhoneNumberTag.md new file mode 100644 index 0000000000..31d633d8dd --- /dev/null +++ b/teams/teams-ps/teams/Update-CsPhoneNumberTag.md @@ -0,0 +1,82 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/update-csphonenumbertag +applicable: Microsoft Teams +title: Update-CsPhoneNumberTag +author: pavellatif +ms.author: pavellatif +ms.reviewer: pavellatif +manager: roykuntz +schema: 2.0.0 +--- + +# Update-CsPhoneNumberTag + +## SYNOPSIS +This cmdlet allows admin to update existing telephone number tags. + +## SYNTAX + +``` +Update-CsPhoneNumberTag -NewTag <String> -Tag <String> [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet can be used to update existing tags for telephone numbers. Tags can be up to 50 characters long, including spaces, and can contain multiple words. They are not case-sensitive. An admin can get a list of all existing tags using [Get-CsPhoneNumberTag](https://learn.microsoft.com/powershell/module/teams/get-csphonenumbertag). + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> Update-CsPhoneNumberTag -Tag "Redmond" -NewTag "Redmond HQ" +``` + +This example shows how to update an existing tag "Redmond" to "Redmond HQ" + +## PARAMETERS + +### -NewTag +This is the new tag. A tag can be maximum 50 characters long. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tag +This is the old tag which the admin wants to update. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Boolean + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Update-CsTeamTemplate.md b/teams/teams-ps/teams/Update-CsTeamTemplate.md new file mode 100644 index 0000000000..67710e31ba --- /dev/null +++ b/teams/teams-ps/teams/Update-CsTeamTemplate.md @@ -0,0 +1,809 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: Microsoft.Teams.ConfigAPI.Cmdlets +online version: https://learn.microsoft.com/powershell/module/teams/update-csteamtemplate +title: Update-CsTeamTemplate +author: serdarsoysal +ms.author: serdars +ms.reviewer: +manager: +schema: 2.0.0 +--- + +# Update-CsTeamTemplate + +## SYNOPSIS + +This cmdlet submits an operation that updates a custom team template with new team template settings. + +NOTE: The response is a PowerShell object formatted as a JSON for readability. Please refer to the examples for suggested interaction flows for template management. + +## SYNTAX + +### UpdateExpanded (Default) + +```powershell +Update-CsTeamTemplate -OdataId <String> -DisplayName <String> -ShortDescription <String> + [-App <ITeamsAppTemplate[]>] [-Category <String[]>] [-Channel <IChannelTemplate[]>] + [-Classification <String>] [-Description <String>] [-DiscoverySetting <ITeamDiscoverySettings>] + [-FunSetting <ITeamFunSettings>] [-GuestSetting <ITeamGuestSettings>] [-Icon <String>] + [-IsMembershipLimitedToOwner] [-MemberSetting <ITeamMemberSettings>] + [-MessagingSetting <ITeamMessagingSettings>] [-OwnerUserObjectId <String>] [-PublishedBy <String>] + [-Specialization <String>] [-TemplateId <String>] [-Uri <String>] [-Visibility <String>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] [-ProxyCredential <PSCredential>] + [-ProxyUseDefaultCredentials] [-Confirm] [-WhatIf] + [<CommonParameters>] +``` + +### Update + +```powershell +Update-CsTeamTemplate -OdataId <String> -Body <ITeamTemplate> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateViaIdentity + +```powershell +Update-CsTeamTemplate -InputObject <IConfigApiBasedCmdletsIdentity> -Body <ITeamTemplate> [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateViaIdentityExpanded + +```powershell +Update-CsTeamTemplate -InputObject <IConfigApiBasedCmdletsIdentity> -DisplayName <String> + -ShortDescription <String> [-App <ITeamsAppTemplate[]>] [-Category <String[]>] + [-Channel <IChannelTemplate[]>] [-Classification <String>] [-Description <String>] + [-DiscoverySetting <ITeamDiscoverySettings>] [-FunSetting <ITeamFunSettings>] + [-GuestSetting <ITeamGuestSettings>] [-Icon <String>] [-IsMembershipLimitedToOwner] + [-MemberSetting <ITeamMemberSettings>] [-MessagingSetting <ITeamMessagingSettings>] + [-OwnerUserObjectId <String>] [-PublishedBy <String>] [-Specialization <String>] [-TemplateId <String>] + [-Uri <String>] [-Visibility <String>] [-Break] + [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <Uri>] + [-ProxyCredential <PSCredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\> (Get-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/bfd1ccc8-40f4-4996-833f-461947d23348/Tenant/fr-FR') > input.json +# open json in your favorite editor, make changes + +Update-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/bfd1ccc8-40f4-4996-833f-461947d23348/Tenant/fr-FR' -Body (Get-Content '.\input.json' | Out-String) +``` + +Step 1: Creates a JSON file of the template you have specified. +Step 2: Updates the template with JSON file you have edited. + +### EXAMPLE 2 + +```powershell +PS C:\> $template = New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.TeamTemplate -Property @{` +DisplayName='New Template';` +ShortDescription='Short Definition';` +Description='New Description';` +App=@{id='feda49f8-b9f2-4985-90f0-dd88a8f80ee1'}, @{id='1d71218a-92ad-4254-be15-c5ab7a3e4423'};` +Channel=@{` + displayName = "General";` + id= "General";` + isFavoriteByDefault= $true` + },` + @{` + displayName= "test";` + id= "b82b7d0a-6bc9-4fd8-bf09-d432e4ea0475";` + isFavoriteByDefault= $false` + }` +} + +PS C:\> Update-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/bfd1ccc8-40f4-4996-833f-461947d23348/Tenant/fr-FR' -Body $template +``` + +Update to a new object + +### EXAMPLE 3 + +```powershell +PS C:\> Update-CsTeamTemplate -OdataId '/api/teamtemplates/v1.0/bfd1ccc8-40f4-4996-833f-461947d23348/Tenant/fr-FR' ` +-Locale en-US -DisplayName 'New Template' ` +-ShortDescription 'New Description' ` +-App @{id='feda49f8-b9f2-4985-90f0-dd88a8f80ee1'}, @{id='1d71218a-92ad-4254-be15-c5ab7a3e4423'} ` +-Channel @{ ` +displayName = "General"; ` +id= "General"; ` +isFavoriteByDefault= $true ` +}, ` +@{ ` + displayName= "test"; ` + id= "b82b7d0a-6bc9-4fd8-bf09-d432e4ea0475"; ` + isFavoriteByDefault= $false ` +} +``` +> [!Note] +> It can take up to 24 hours for Teams users to see a custom template change in the gallery. + +## PARAMETERS + +### -App + +Gets or sets the set of applications that should be installed in teams created based on the template.The app catalog is the main directory for information about each app; this set is intended only as a reference. +To construct, see NOTES section for APP properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamsAppTemplate[] +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Body + +The client input for a request to create a template. +Only admins from Config Api can perform this request. +To construct, see NOTES section for BODY properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamTemplate +Parameter Sets: Update, UpdateViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Category + +Gets or sets list of categories. + +```yaml +Type: System.String[] +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Channel + +Gets or sets the set of channel templates included in the team template. +To construct, see NOTES section for CHANNEL properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IChannelTemplate[] +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Classification + +Gets or sets the team's classification.Tenant admins configure Microsoft Entra ID with the set of possible values. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description + +Gets or sets the team's Description. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DiscoverySetting + +Governs discoverability of a team. +To construct, see NOTES section for DISCOVERYSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamDiscoverySettings +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DisplayName + +Gets or sets the team's DisplayName. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FunSetting + +Governs use of fun media like giphy and stickers in the team. +To construct, see NOTES section for FUNSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamFunSettings +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -GuestSetting + +Guest role settings for the team. +To construct, see NOTES section for GUESTSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamGuestSettings +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Icon + +Gets or sets template icon. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject + +Identity Parameter +To construct, see NOTES section for INPUTOBJECT properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity +Parameter Sets: UpdateViaIdentity, UpdateViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -IsMembershipLimitedToOwner + +Gets or sets whether to limit the membership of the team to owners in the Microsoft Entra group until an owner "activates" the team. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MemberSetting + +Member role settings for the team. +To construct, see NOTES section for MEMBERSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamMemberSettings +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessagingSetting + +Governs use of messaging features within the teamThese are settings the team owner should be able to modify from UI after team creation. +To construct, see NOTES section for MESSAGINGSETTING properties and create a hash table. + +```yaml +Type: Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamMessagingSettings +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OdataId + +A composite URI of a template. + +```yaml +Type: System.String +Parameter Sets: Update, UpdateExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OwnerUserObjectId + +Gets or sets the Microsoft Entra user object id of the user who should be set as the owner of the new team.Only to be used when an application or administrative user is making the request on behalf of the specified user. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PublishedBy + +Gets or sets published name. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ShortDescription + +Gets or sets template short description. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Specialization + +The specialization or use case describing the team.Used for telemetry/BI, part of the team context exposed to app developers, and for legacy implementations of differentiated features for education. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -TemplateId + +Gets or sets the id of the base template for the team.Either a Microsoft base template or a custom template. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Uri + +Gets or sets uri to be used for GetTemplate api call. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Visibility + +Used to control the scope of users who can view a group/team and its members, and ability to join. + +```yaml +Type: System.String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Break + +Wait for .NET debugger to attach + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend + +SendAsync Pipeline Steps to be appended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend + +SendAsync Pipeline Steps to be prepended to the front of the pipeline + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy + +The URI for the proxy server to use + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential + +Credentials for a proxy server to use for the remote call + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials + +Use the default credentials for the proxy + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: System.Management.Automation.SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ITeamTemplate + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ICreateTemplateResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorObject + +## NOTES + +ALIASES + +COMPLEX PARAMETER PROPERTIES + +To create the parameters described below, construct a hash table containing the appropriate properties. For information on hash tables, run Get-Help about_Hash_Tables. + +APP \<ITeamsAppTemplate[]\>: Gets or sets the set of applications that should be installed in teams created based on the template.The app catalog is the main directory for information about each app; this set is intended only as a reference. + +- `[Id <String>]`: Gets or sets the app's ID in the global apps catalog. + +BODY \<ITeamTemplate\>: The client input for a request to create a template. Only admins from Config Api can perform this request. + +- `DisplayName <String>`: Gets or sets the team's DisplayName. +- `ShortDescription <String>`: Gets or sets template short description. +- `[App <ITeamsAppTemplate[]>]`: Gets or sets the set of applications that should be installed in teams created based on the template. The app catalog is the main directory for information about each app; this set is intended only as a reference. + - `[Id <String>]`: Gets or sets the app's ID in the global apps catalog. +- `[Category <String[]>]`: Gets or sets list of categories. +- `[Channel <IChannelTemplate[]>]`: Gets or sets the set of channel templates included in the team template. + - `[Description <String>]`: Gets or sets channel description as displayed to users. + - `[DisplayName <String>]`: Gets or sets channel name as displayed to users. + - `[Id <String>]`: Gets or sets identifier for the channel template. + - `[IsFavoriteByDefault <Boolean?>]`: Gets or sets a value indicating whether new members of the team should automatically favorite the channel, pinning it for visibility in the UI and using resources to make switching to the channel faster. + - `[Tab <IChannelTabTemplate[]>]`: Gets or sets collection of tabs that should be added to the channel. + - `[Configuration <ITeamsTabConfiguration>]`: Represents the configuration of a tab. + - `[ContentUrl <String>]`: Gets or sets the Url used for rendering tab contents in Teams. + - `[EntityId <String>]`: Gets or sets the identifier for the entity hosted by the tab provider. + - `[RemoveUrl <String>]`: Gets or sets the Url that is invoked when the user tries to remove a tab from the FE client. + - `[WebsiteUrl <String>]`: Gets or sets the Url for showing tab contents outside of Teams. + - `[Id <String>]`: Gets or sets identifier for the channel tab template. + - `[Key <String>]`: Gets a unique identifier. + - `[MessageId <String>]`: Gets or sets id used to identify the chat message associated with the tab. + - `[Name <String>]`: Gets or sets the tab name displayed to users. + - `[SortOrderIndex <String>]`: Gets or sets index of the order used for sorting tabs. + - `[TeamsAppId <String>]`: Gets or sets the app's id in the global apps catalog. + - `[WebUrl <String>]`: Gets or sets the deep link url of the tab instance. +- `[Classification <String>]`: Gets or sets the team's classification. Tenant admins configure Microsoft Entra ID with the set of possible values. +- `[Description <String>]`: Gets or sets the team's Description. +- `[DiscoverySetting <ITeamDiscoverySettings>]`: Governs discoverability of a team. + - `ShowInTeamsSearchAndSuggestion <Boolean>`: Gets or sets value indicating if team is visible within search and suggestions in Teams clients. +- `[FunSetting <ITeamFunSettings>]`: Governs use of fun media like giphy and stickers in the team. + - `AllowCustomMeme <Boolean>`: Gets or sets a value indicating whether users are allowed to create and post custom meme images in team conversations. + - `AllowGiphy <Boolean>`: Gets or sets a value indicating whether users can post giphy content in team conversations. + - `AllowStickersAndMeme <Boolean>`: Gets or sets a value indicating whether users can post stickers and memes in team conversations. + - `GiphyContentRating <String>`: Gets or sets the rating filter on giphy content. +- `[GuestSetting <ITeamGuestSettings>]`: Guest role settings for the team. + - `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether guests can create or edit channels in the team. + - `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether guests can delete team channels. +- `[Icon <String>]`: Gets or sets template icon. +- `[IsMembershipLimitedToOwner <Boolean?>]`: Gets or sets whether to limit the membership of the team to owners in the Microsoft Entra group until an owner "activates" the team. +- `[MemberSetting <ITeamMemberSettings>]`: Member role settings for the team. + - `AllowAddRemoveApp <Boolean>`: Gets or sets a value indicating whether members can add or remove apps in the team. + - `AllowCreatePrivateChannel <Boolean>`: Gets or Sets a value indicating whether members can create Private channels. + - `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether members can create or edit channels in the team. + - `AllowCreateUpdateRemoveConnector <Boolean>`: Gets or sets a value indicating whether members can add, edit, or remove connectors in the team. + - `AllowCreateUpdateRemoveTab <Boolean>`: Gets or sets a value indicating whether members can add, edit or remove pinned tabs in the team. + - `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether members can delete team channels. + - `UploadCustomApp <Boolean>`: Gets or sets a value indicating is allowed to upload custom apps. +- `[MessagingSetting <ITeamMessagingSettings>]`: Governs use of messaging features within the team These are settings the team owner should be able to modify from UI after team creation. + - `AllowChannelMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention entire channels in team conversations. + - `AllowOwnerDeleteMessage <Boolean>`: Gets or sets a value indicating whether team owners can delete anyone's messages in team conversations. + - `AllowTeamMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention the entire team in team conversations. + - `AllowUserDeleteMessage <Boolean>`: Gets or sets a value indicating whether team members can delete their own messages in team conversations. + - `AllowUserEditMessage <Boolean>`: Gets or sets a value indicating whether team members can edit their own messages in team conversations. +- `[OwnerUserObjectId <String>]`: Gets or sets the Microsoft Entra user object id of the user who should be set as the owner of the new team. Only to be used when an application or administrative user is making the request on behalf of the specified user. +- `[PublishedBy <String>]`: Gets or sets published name. +- `[Specialization <String>]`: The specialization or use case describing the team. Used for telemetry/BI, part of the team context exposed to app developers, and for legacy implementations of differentiated features for education. +- `[TemplateId <String>]`: Gets or sets the id of the base template for the team. Either a Microsoft base template or a custom template. +- `[Uri <String>]`: Gets or sets uri to be used for GetTemplate api call. +- `[Visibility <String>]`: Used to control the scope of users who can view a group/team and its members, and ability to join. + +CHANNEL <IChannelTemplate[]>: Gets or sets the set of channel templates included in the team template. + +- `[Description <String>]`: Gets or sets channel description as displayed to users. +- `[DisplayName <String>]`: Gets or sets channel name as displayed to users. +- `[Id <String>]`: Gets or sets identifier for the channel template. +- `[IsFavoriteByDefault <Boolean?>]`: Gets or sets a value indicating whether new members of the team should automatically favorite the channel, pinning it for visibility in the UI and using resources to make switching to the channel faster. +- `[Tab <IChannelTabTemplate[]>]`: Gets or sets collection of tabs that should be added to the channel. + - `[Configuration <ITeamsTabConfiguration>]`: Represents the configuration of a tab. + - `[ContentUrl <String>]`: Gets or sets the Url used for rendering tab contents in Teams. + - `[EntityId <String>]`: Gets or sets the identifier for the entity hosted by the tab provider. + - `[RemoveUrl <String>]`: Gets or sets the Url that is invoked when the user tries to remove a tab from the FE client. + - `[WebsiteUrl <String>]`: Gets or sets the Url for showing tab contents outside of Teams. + - `[Id <String>]`: Gets or sets identifier for the channel tab template. + - `[Key <String>]`: Gets a unique identifier. + - `[MessageId <String>]`: Gets or sets id used to identify the chat message associated with the tab. + - `[Name <String>]`: Gets or sets the tab name displayed to users. + - `[SortOrderIndex <String>]`: Gets or sets index of the order used for sorting tabs. + - `[TeamsAppId <String>]`: Gets or sets the app's id in the global apps catalog. + - `[WebUrl <String>]`: Gets or sets the deep link url of the tab instance. + +DISCOVERYSETTING \<ITeamDiscoverySettings\>: Governs discoverability of a team. + +- `ShowInTeamsSearchAndSuggestion <Boolean>`: Gets or sets value indicating if team is visible within search and suggestions in Teams clients. + +FUNSETTING \<ITeamFunSettings\>: Governs use of fun media like giphy and stickers in the team. + +- `AllowCustomMeme <Boolean>`: Gets or sets a value indicating whether users are allowed to create and post custom meme images in team conversations. +- `AllowGiphy <Boolean>`: Gets or sets a value indicating whether users can post giphy content in team conversations. +- `AllowStickersAndMeme <Boolean>`: Gets or sets a value indicating whether users can post stickers and memes in team conversations. +- `GiphyContentRating <String>`: Gets or sets the rating filter on giphy content. + +GUESTSETTING \<ITeamGuestSettings\>: Guest role settings for the team. + +- `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether guests can create or edit channels in the team. +- `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether guests can delete team channels. + +INPUTOBJECT \<IConfigApiBasedCmdletsIdentity\>: Identity Parameter + +- `[Bssid <String>]`: +- `[ChassisId <String>]`: +- `[CivicAddressId <String>]`: Civic address id. +- `[Country <String>]`: +- `[GroupId <String>]`: The ID of a group whose policy assignments will be returned. +- `[Id <String>]`: +- `[Identity <String>]`: +- `[Locale <String>]`: +- `[LocationId <String>]`: Location id. +- `[OdataId <String>]`: A composite URI of a template. +- `[OperationId <String>]`: The ID of a batch policy assignment operation. +- `[OrderId <String>]`: +- `[PackageName <String>]`: The name of a specific policy package +- `[PolicyType <String>]`: The policy type for which group policy assignments will be returned. +- `[Port <String>]`: +- `[PortInOrderId <String>]`: +- `[PublicTemplateLocale <String>]`: Language and country code for localization of publicly available templates. +- `[SubnetId <String>]`: +- `[TenantId <String>]`: +- `[UserId <String>]`: UserId. Supports Guid. Eventually UPN and SIP. + +MEMBERSETTING \<ITeamMemberSettings\>: Member role settings for the team. + +- `AllowAddRemoveApp <Boolean>`: Gets or sets a value indicating whether members can add or remove apps in the team. +- `AllowCreatePrivateChannel <Boolean>`: Gets or Sets a value indicating whether members can create Private channels. +- `AllowCreateUpdateChannel <Boolean>`: Gets or sets a value indicating whether members can create or edit channels in the team. +- `AllowCreateUpdateRemoveConnector <Boolean>`: Gets or sets a value indicating whether members can add, edit, or remove connectors in the team. +- `AllowCreateUpdateRemoveTab <Boolean>`: Gets or sets a value indicating whether members can add, edit or remove pinned tabs in the team. +- `AllowDeleteChannel <Boolean>`: Gets or sets a value indicating whether members can delete team channels. +- `UploadCustomApp <Boolean>`: Gets or sets a value indicating is allowed to upload custom apps. + +MESSAGINGSETTING \<ITeamMessagingSettings\>: Governs use of messaging features within the teamThese are settings the team owner should be able to modify from UI after team creation. + +- `AllowChannelMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention entire channels in team conversations. +- `AllowOwnerDeleteMessage <Boolean>`: Gets or sets a value indicating whether team owners can delete anyone's messages in team conversations. +- `AllowTeamMention <Boolean>`: Gets or sets a value indicating whether team members can at-mention the entire team in team conversations. +- `AllowUserDeleteMessage <Boolean>`: Gets or sets a value indicating whether team members can delete their own messages in team conversations. +- `AllowUserEditMessage <Boolean>`: Gets or sets a value indicating whether team members can edit their own messages in team conversations. + +## RELATED LINKS + +- [Get-CsTeamTemplateList](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [Get-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [New-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [Update-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) +- [Remove-CsTeamTemplate](https://learn.microsoft.com/powershell/module/teams/get-csteamtemplatelist) diff --git a/teams/teams-ps/teams/Update-CsTeamsShiftsConnection.md b/teams/teams-ps/teams/Update-CsTeamsShiftsConnection.md new file mode 100644 index 0000000000..776c82c956 --- /dev/null +++ b/teams/teams-ps/teams/Update-CsTeamsShiftsConnection.md @@ -0,0 +1,433 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: Update-CsTeamsShiftsConnection +author: serdarsoysal +ms.author: serdars +manager: +online version: https://docs.microsoft.com/powershell/module/teams/update-csteamsshiftsconnection +schema: 2.0.0 +--- + +# Update-CsTeamsShiftsConnection + +## SYNOPSIS +This cmdlet updates an existing workforce management (WFM) connection. + +## SYNTAX + +### Update (Default) +```powershell +Update-CsTeamsShiftsConnection -ConnectionId <string> -Body <IUpdateWfmConnectionFieldsRequest> [-Authorization <string>] [-IfMatch <string>] + [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateExpanded +```powershell +Update-CsTeamsShiftsConnection -ConnectionId <string> [-Authorization <string>] [-IfMatch <string>] [-ConnectorId <string>] + [-ConnectorSpecificSettings <IUpdateWfmConnectionFieldsRequestConnectorSpecificSettings>] [-Etag <string>] [-Name <string>] + [-State <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] +[-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateViaIdentityExpanded +```powershell +Update-CsTeamsShiftsConnection -InputObject <IConfigApiBasedCmdletsIdentity> [-Authorization <string>] [-IfMatch <string>] + [-ConnectorId <string>] [-ConnectorSpecificSettings <IUpdateWfmConnectionFieldsRequestConnectorSpecificSettings>] [-Etag <string>] + [-Name <string>] [-State <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] + [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateViaIdentity +```powershell +Update-CsTeamsShiftsConnection -InputObject <IConfigApiBasedCmdletsIdentity> -Body <IUpdateWfmConnectionFieldsRequest> [-Authorization <string>] + [-IfMatch <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] + [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet updates a Shifts WFM connection. Similar to the Set-CsTeamsShiftsConnection cmdlet, it allows the admin to make changes to the settings in the connection. The complete list of fields is not required allowing the user to update single fields of the connection. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> $connection = Get-CsTeamsShiftsConnection -ConnectionId 4dae9db0-0841-412c-8d6b-f5684bfebdd7 +PS C:\> $result = Update-CsTeamsShiftsConnection ` + -connectionId $connection.Id ` + -IfMatch $connection.Etag ` + -name "Cmdlet test connection - updated" ` + +PS C:\> $result | Format-List +``` + +```output + +ConnectorId : 6A51B888-FF44-4FEA-82E1-839401E00000 +ConnectorSpecificSettingAdminApiUrl : https://www.contoso.com/retail/data/wfmadmin/api/v1-beta2 +ConnectorSpecificSettingApiUrl : +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : +ConnectorSpecificSettingCookieAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingEssApiUrl : https://www.contoso.com/retail/data/wfmess/api/v1-beta2 +ConnectorSpecificSettingFederatedAuthUrl : https://www.contoso.com/retail/data/login +ConnectorSpecificSettingRetailWebApiUrl : https://www.contoso.com/retail/data/retailwebapi/api/v1 +ConnectorSpecificSettingSiteManagerUrl : https://www.contoso.com/retail/data/wfmsm/api/v1-beta2 +ConnectorSpecificSettingSsoUrl : +CreatedDateTime : 24/03/2023 04:58:23 +Etag : "5b00dd1b-0000-0400-0000-641d2df00000" +Id : 4dae9db0-0841-412c-8d6b-f5684bfebdd7 +LastModifiedDateTime : 24/03/2023 04:58:23 +Name : Cmdlet test connection - updated +State : Active +TenantId : 3FDCAAF2-863A-4520-97BA-DFA211595876 + +``` + +Updates the connection with the specified -ConnectionId with the given name. Returns the object of the updated connection. + +### Example 2 + +```powershell +PS C:\> $connection = Get-CsTeamsShiftsConnection -ConnectionId 79964000-286a-4216-ac60-c795a426d61a +PS C:\> $result = Update-CsTeamsShiftsConnection ` + -connectionId $connection.Id ` + -IfMatch $connection.Etag ` + -connectorId "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0" ` + -connectorSpecificSettings (New-Object Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ConnectorSpecificUkgDimensionsSettingsRequest ` + -Property @{ + apiUrl = "https://www.contoso.com/api" + ssoUrl = "https://www.contoso.com/sso" + appKey = "PlaceholderForAppKey" + clientId = "Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W" + clientSecret = "PlaceholderForClientSecret" + }) ` + -state "Active" +PS C:\> $result | Format-List +``` + +```output +ConnectorId : 95BF2848-2DDA-4425-B0EE-D62AEED4C0A0 +ConnectorSpecificSettingAdminApiUrl : +ConnectorSpecificSettingApiUrl : https://www.contoso.com/api +ConnectorSpecificSettingAppKey : +ConnectorSpecificSettingClientId : Es5Q2fB4PXweCyto6Ms6J2kRB7uwAc3W +ConnectorSpecificSettingCookieAuthUrl : +ConnectorSpecificSettingEssApiUrl : +ConnectorSpecificSettingFederatedAuthUrl : +ConnectorSpecificSettingRetailWebApiUrl : +ConnectorSpecificSettingSiteManagerUrl : +ConnectorSpecificSettingSsoUrl : https://www.contoso.com/sso +CreatedDateTime : 06/04/2023 11:05:39 +Etag : "3100fd6e-0000-0400-0000-642ea7840000" +Id : 79964000-286a-4216-ac60-c795a426d61a +LastModifiedDateTime : 06/04/2023 11:05:39 +Name : Cmdlet test connection +State : Active +TenantId : 3FDCAAF2-863A-4520-97BA-DFA211595876 +``` + +Updates the connection with the specified -ConnectionId with the given settings. Returns the object of the updated connection. + +## PARAMETERS + +### -Body +The request body. + +```yaml +Type: IUpdateWfmConnectionFieldsRequest +Parameter Sets: Update, UpdateViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break +Wait for the .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IfMatch +The value of the ETag field as returned by the cmdlets. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: UpdateViaIdentityExpanded, UpdateViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Name +The connector instance name. + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The state of the connection. Valid values are "Active" and "Disabled". A third value, "ErrorDisabled", signifies an error in the connection. + +```yaml +Type: String +Parameter Sets: UpdateViaIdentityExpanded, UpdateViaIdentity +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Authorization +Used to provide the necessary credentials for authenticating and authorizing the connection to the workforce management (WFM) system. This parameter ensures that the connection has the appropriate permissions to access and manage the data within the WFM system. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId +The WFM connection ID for the instance. +This can be retrieved by running [Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection). + +```yaml +Type: String +Parameter Sets: UpdateExpanded, Update +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorId +Used to specify the unique identifier of the connector being used for the connection. + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorSpecificSettings +Used to specify settings that are unique to the connector being used. This parameter allows administrators to configure various properties specific to the workforce management (WFM) system they are integrating with Teams Shifts. + +```yaml +Type: IUpdateWfmConnectionFieldsRequestConnectorSpecificSettings +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Etag +Used to manage concurrency control. It helps ensure that updates to a Shifts connection instance are only applied if the instance has not been modified since it was last retrieved. This is particularly useful in preventing conflicts when multiple administrators might be making changes simultaneously. + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IUpdateWfmConnectionFieldsRequest + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IWfmConnectionResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection) + +[New-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnection) + +[Set-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnection) + +[Test-CsTeamsShiftsConnectionValidate](https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate) diff --git a/teams/teams-ps/teams/Update-CsTeamsShiftsConnectionInstance.md b/teams/teams-ps/teams/Update-CsTeamsShiftsConnectionInstance.md new file mode 100644 index 0000000000..466a0bf1c7 --- /dev/null +++ b/teams/teams-ps/teams/Update-CsTeamsShiftsConnectionInstance.md @@ -0,0 +1,529 @@ +--- +external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml +Module Name: MicrosoftTeams +title: Update-CsTeamsShiftsConnectionInstance +author: nunocorreia-ms +ms.author: nunocorreia +manager: +online version: https://docs.microsoft.com/powershell/module/teams/update-csteamsshiftsconnectioninstance +schema: 2.0.0 +--- + +# Update-CsTeamsShiftsConnectionInstance + +## SYNOPSIS +This cmdlet updates Shifts connection instance fields. + +## SYNTAX + +### Update (Default) +```powershell +Update-CsTeamsShiftsConnectionInstance -ConnectorInstanceId <string> -IfMatch <string> -Body <IUpdateConnectorInstanceFieldsRequest> [-Break] +[-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] +[-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateExpanded +```powershell +Update-CsTeamsShiftsConnectionInstance -ConnectorInstanceId <string> -IfMatch <string> [-ConnectionId <string>] [-ConnectorAdminEmail <string[]>] +[-DesignatedActorId <string>] [-Etag <string>] [-Name <string>] [-State <string>] [-SyncFrequencyInMin <int>] [-SyncScenarioOfferShiftRequest <string>] + [-SyncScenarioOpenShift <string>] [-SyncScenarioOpenShiftRequest <string>] [-SyncScenarioShift <string>] [-SyncScenarioSwapRequest <string>] + [-SyncScenarioTimeCard <string>] [-SyncScenarioTimeOff <string>] [-SyncScenarioTimeOffRequest <string>] [-SyncScenarioUserShiftPreference <string>] + [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateViaIdentityExpanded +```powershell +Update-CsTeamsShiftsConnectionInstance -InputObject <IConfigApiBasedCmdletsIdentity> -IfMatch <string> + [-ConnectionId <string>] [-ConnectorAdminEmail <string[]>] [-DesignatedActorId <string>] [-Etag <string>] [-Name <string>] [-State <string>] + [-SyncFrequencyInMin <int>] [-SyncScenarioOfferShiftRequest <string>] [-SyncScenarioOpenShift <string>] [-SyncScenarioOpenShiftRequest <string>] +[-SyncScenarioShift <string>] [-SyncScenarioSwapRequest <string>] [-SyncScenarioTimeCard <string>] [-SyncScenarioTimeOff <string>] +[-SyncScenarioTimeOffRequest <string>] [-SyncScenarioUserShiftPreference <string>] [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] + [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +### UpdateViaIdentity +```powershell +Update-CsTeamsShiftsConnectionInstance -InputObject <IConfigApiBasedCmdletsIdentity> -IfMatch <string> -Body <IUpdateConnectorInstanceFieldsRequest> + [-Break] [-HttpPipelineAppend <SendAsyncStep[]>] [-HttpPipelinePrepend <SendAsyncStep[]>] [-Proxy <uri>] [-ProxyCredential <pscredential>] + [-ProxyUseDefaultCredentials] [-WhatIf] [-Confirm] [<CommonParameters>] +``` + +## DESCRIPTION +This cmdlet updates a Shifts connection instance. Similar to the Set-CsTeamsShiftsConnectionInstance cmdlet, it allows the admin to make changes to the settings in the instance such as name, enabled scenarios, and sync frequency. The complete list of fields is not required allowing the user to update single fields of the instance. + +## EXAMPLES + +### Example 1 +```powershell +PS C:\> $connectionInstance = Get-CsTeamsShiftsConnectionInstance -ConnectorInstanceId WCI-eba2865f-6cac-46f9-8733-e0631a4536e1 +PS C:\> $result = Update-CsTeamsShiftsConnectionInstance ` + -connectorInstanceId "WCI-eba2865f-6cac-46f9-8733-e0631a4536e1" + -IfMatch $connectionInstance.Etag ` + -connectionId "79964000-286a-4216-ac60-c795a426d61a" ` + -name "Cmdlet test instance - updated" ` + -syncFrequencyInMin "30" ` + +PS C:\> $result.ToJsonString() +``` + +```output + +{ + "syncScenarios": { + "offerShiftRequest": "FromWfmToShifts", + "openShift": "FromWfmToShifts", + "openShiftRequest": "FromWfmToShifts", + "shift": "FromWfmToShifts", + "swapRequest": "FromWfmToShifts", + "timeCard": "FromWfmToShifts", + "timeOff": "FromWfmToShifts", + "timeOffRequest": "FromWfmToShifts", + "userShiftPreferences": "Disabled" + }, + "id": "WCI-eba2865f-6cac-46f9-8733-e0631a4536e1", + "tenantId": "dfd24b34-ccb0-47e1-bdb7-e49db9c7c14a", + "connectionId": "a2d1b091-5140-4dd2-987a-98a8b5338744", + "connectorAdminEmails": [ ], + "connectorId": "95BF2848-2DDA-4425-B0EE-D62AEED4C0A0", + "designatedActorId": "ec1a4edb-1a5f-4b2d-b2a4-37aab6ebd231", + "name": "Cmdlet test instance - updated", + "syncFrequencyInMin": 30, + "workforceIntegrationId": "WFI_6b225907-b476-4d40-9773-08b86db7b11b", + "etag": "\"4f005d22-0000-0400-0000-642ff64a0000\"", + "createdDateTime": "2023-04-07T10:54:01.8170000Z", + "lastModifiedDateTime": "2023-04-07T10:54:01.8170000Z", + "state" : "Active" +} + +``` + +Updates the instance with the specified -ConnectorInstanceId with the given name and sync frequency. Returns the object of the updated connector instance. + +## PARAMETERS + +### -Body +The request body. + +```yaml +Type: IUpdateConnectorInstanceFieldsRequest +Parameter Sets: Update, UpdateViaIdentity +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Break +Wait for the .NET debugger to attach. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorAdminEmail +Gets or sets the list of connector admin email addresses. + +```yaml +Type: String[] +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectorInstanceId +The connector instance ID. + +```yaml +Type: String +Parameter Sets: Update, UpdateExpanded +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DesignatedActorId +The designated actor ID that App acts as for Shifts Graph API calls. + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOfferShiftRequest +The sync state for the offer shift request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOpenShift +The sync state for the open shift scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioOpenShiftRequest +The sync state for the open shift request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioShift +The sync state for the shift scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioSwapRequest +The sync state for the shift swap request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeCard +The sync state for the time card scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeOff +The sync state for the time off scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioTimeOffRequest +The sync state for the time off request scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncScenarioUserShiftPreference +The sync state for the user shift preferences scenario. Valid values are "Disabled", "FromWfmToShifts", and "TwoWay". + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelineAppend +SendAsync Pipeline Steps to be appended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -HttpPipelinePrepend +SendAsync Pipeline Steps to be prepended to the front of the pipeline. + +```yaml +Type: SendAsyncStep[] +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IfMatch +The value of the ETag field as returned by the cmdlets. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InputObject +Identity Parameter + +```yaml +Type: IConfigApiBasedCmdletsIdentity +Parameter Sets: UpdateViaIdentityExpanded, UpdateViaIdentity +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: True (ByValue) +Accept wildcard characters: False +``` + +### -Name +The connector instance name. + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Proxy +The URI for the proxy server to use. + +```yaml +Type: Uri +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyCredential +Credentials for a proxy server to use for the remote call. + +```yaml +Type: PSCredential +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ProxyUseDefaultCredentials +Use the default credentials for the proxy. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -State +The state of the connection instance. Valid values are "Active" and "Disabled". A third value, "ErrorDisabled", signifies an error in the connection instance. + +```yaml +Type: String +Parameter Sets: UpdateViaIdentityExpanded, UpdateViaIdentity +Aliases: +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SyncFrequencyInMin +The sync frequency in minutes. + +```yaml +Type: Int32 +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ConnectionId +The WFM connection ID for the instance. +This can be retrieved by running [Get-CsTeamsShiftsConnection](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnection). + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Etag +Used to manage concurrency control. It helps ensure that updates to a Shifts connection instance are only applied if the instance has not been modified since it was last retrieved. This is particularly useful in preventing conflicts when multiple administrators might be making changes simultaneously. + +```yaml +Type: String +Parameter Sets: UpdateExpanded, UpdateViaIdentityExpanded +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IUpdateConnectorInstanceFieldsRequest + +## OUTPUTS + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConnectorInstanceResponse + +### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IErrorDetailsResponse + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectioninstance) + +[New-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/new-csteamsshiftsconnectioninstance) + +[Set-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/set-csteamsshiftsconnectioninstance) + +[Remove-CsTeamsShiftsConnectionInstance](https://learn.microsoft.com/powershell/module/teams/remove-csteamsshiftsconnectioninstance) + +[Test-CsTeamsShiftsConnectionValidate](https://learn.microsoft.com/powershell/module/teams/test-csteamsshiftsconnectionvalidate) diff --git a/teams/teams-ps/teams/Update-M365TeamsApp.md b/teams/teams-ps/teams/Update-M365TeamsApp.md new file mode 100644 index 0000000000..7fccff1744 --- /dev/null +++ b/teams/teams-ps/teams/Update-M365TeamsApp.md @@ -0,0 +1,255 @@ +--- +external help file: Microsoft.Teams.PowerShell.TeamsCmdlets.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://docs.microsoft.com/powershell/module/teams/Update-M365TeamsApp +applicable: Microsoft Teams +title: Update-M365TeamsApp +author: lkueter +ms.author: sribagchi +manager: rahulrgupta +ms.date: 04/24/2024 +schema: 2.0.0 +--- + +# Update-M365TeamsApp + +## SYNOPSIS + +This cmdlet updates app state and app available values for the Microsoft Teams app. + +## SYNTAX + +```powershell +Update-M365TeamsApp -Id <String> [-IsBlocked <Boolean>] -AppAssignmentType <String> -OperationType <String> + [-Users <String[]>] [-Groups <String[]>] -AppInstallType <String> -InstallForOperationType <String> [-InstallForUsers <String[]> -InstallForGroups <String[]> -InstallVersion <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet allows administrators to modify app state, availability and installation status by adding or removing users and groups or changing assignment type or installation status. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Update-M365TeamsApp -Id 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b -AppAssignmentType Everyone +``` +Updates the availability value for Bookings app (App ID 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b) to Everyone. + +### Example 2 + +```powershell +PS C:\> Update-M365TeamsApp -Id 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b -IsBlocked $true -AppAssignmentType UsersAndGroups -OperationType Add -Users eec823bd-0979-4cf8-9924-85bb6ffcb57d, eec823bd-0979-4cf8-9924-85bb6ffcb57e -Groups 37da2d58-fc14-453e-9a14-5065ebd63a1d, 37da2d58-fc14-453e-9a14-5065ebd63a1e, 37da2d58-fc14-453e-9a14-5065ebd63a1b, 37da2d58-fc14-453e-9a14-5065ebd63a1f, 37da2d58-fc14-453e-9a14-5065ebd63a1a +``` +Unblocks CSP Customer App (App ID 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b) and updates availability setting for the app to include 2 users and 5 groups. + +### Example 3 + +```powershell +PS C:\> Update-M365TeamsApp -Id 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b -IsBlocked $true +``` +Unblocks Bookings app (App ID 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b). + +### Example 4 + +```powershell +PS C:\> Update-M365TeamsApp -Id 2b876f4d-2e6b-4ee7-9b09-8893808c1380 -IsBlocked $false -AppInstallType UsersAndGroups -InstallForOperationType Add -InstallForUsers 77f5d400-a12e-4168-8e63-ccd2243d33a8,f2f4d8bc-1fb3-4292-867e-6d19efb0eb7c,37b6fc6a-32a4-4767-ac2e-c2f2307bad5c -InstallForGroups 926d57ad-431c-4e6a-9e16-347eacc91aa4 -InstallVersion 4.1.2 +``` +Unblocks 1Page App (App ID 2b876f4d-2e6b-4ee7-9b09-8893808c1380) and updates installation setting for the app to include 3 users and 1 group. + +## PARAMETERS + +### -AppAssignmentType + +App availability type. + +```yaml +Type: String +Parameter Sets: (Everyone, UsersandGroups, Noone) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Groups + +List of all the groups for whom the app is enabled or disabled. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Id + +Application ID of Microsoft Teams app. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -IsBlocked + +The state of the app in the tenant. + +```yaml +Type: Boolean +Parameter Sets: (true, false) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -OperationType + +Operation performed on the app assigment. + +```yaml +Type: String +Parameter Sets: (Add, Remove) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Users + +List of all the users for whom the app is enabled or disabled. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AppInstallType + +App installation type. + +```yaml +Type: String +Parameter Sets: (Everyone, UsersandGroups, Noone) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InstallForOperationType + +Operation performed on the app installation. + +```yaml +Type: String +Parameter Sets: (Add, Remove) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InstallForUsers + +List of all the users for whom the app is installed. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InstallForGroups + +List of all the groups for whom the app is installed. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -InstallVersion + +App version to be installed. + +```yaml +Type: String +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-AllM365TeamsApps](https://learn.microsoft.com/powershell/module/teams/get-allm365teamsapps) +[Get-M365TeamsApp](https://learn.microsoft.com/powershell/module/teams/get-allm365teamsapps) diff --git a/teams/teams-ps/teams/Update-M365UnifiedCustomPendingApp.md b/teams/teams-ps/teams/Update-M365UnifiedCustomPendingApp.md new file mode 100644 index 0000000000..f2292aee01 --- /dev/null +++ b/teams/teams-ps/teams/Update-M365UnifiedCustomPendingApp.md @@ -0,0 +1,92 @@ +--- +external help file: Microsoft.Teams.PowerShell.TeamsCmdlets.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://docs.microsoft.com/powershell/module/teams/Update-M365UnifiedCustomPendingApp +applicable: Microsoft Teams +title: Update-M365UnifiedCustomPendingApp +author: michelle-paradis +ms.author: mparadis +manager: swmerchant +ms.date: 01/20/2025 +schema: 2.0.0 +--- + +# Update-M365UnifiedCustomPendingApp + +## SYNOPSIS + +This cmdlet updates the review status for a custom Microsoft Teams app that is pending review from an IT Admin. The requester to publish the custom app will not be notified when this cmdlet is completed. + +## SYNTAX + +```powershell +Update-M365UnifiedCustomPendingApp -Id <String> -ReviewStatus <String> +``` + +## DESCRIPTION + +This cmdlet allows administrators to reject or publish custom Microsoft Teams apps that are pending review from an IT Admin. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Update-M365UnifiedCustomPendingApp -Id 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b -ReviewStatus Published +``` +Updates the review status for the custom pending app with App ID 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b to Published. + +### Example 2 + +```powershell +PS C:\> Update-M365UnifiedCustomPendingApp -Id 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b -ReviewStatus Rejected +``` +Updates the review status for the custom pending app with App ID 4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b to Rejected. + +## PARAMETERS + +### Id + +Application ID of the Teams app. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### ReviewStatus + +The review status of the Teams app. + +```yaml +Type: String +Parameter Sets: (Published, Rejected) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES diff --git a/teams/teams-ps/teams/Update-M365UnifiedTenantSettings.md b/teams/teams-ps/teams/Update-M365UnifiedTenantSettings.md new file mode 100644 index 0000000000..ed119948d2 --- /dev/null +++ b/teams/teams-ps/teams/Update-M365UnifiedTenantSettings.md @@ -0,0 +1,141 @@ +--- +external help file: Microsoft.Teams.PowerShell.TeamsCmdlets.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://docs.microsoft.com/powershell/module/teams/Update-M365UnifiedTenantSettings +applicable: Microsoft Teams +title: Update-M365UnifiedTenantSettings +author: lkueter +ms.author: sribagchi +manager: rahulrgupta +ms.date: 10/22/2024 +schema: 2.0.0 +--- + +# Update-M365UnifiedTenantSettings + +## SYNOPSIS + +This cmdlet updates tenant settings. + +## SYNTAX + +```powershell +Update-M365UnifiedTenantSettings -SettingName <String> -SettingValue <String> [-Users <String[]>] [-Groups <String[]>] [-Operation <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +This cmdlet allows administrators to modify tenant settings. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> PS C:\> Update-M365UnifiedTenantSettings -SettingName EnableCopilotExtensibility -SettingValue Some -Users d156010d-fb18-497f-804c-155ec2aa06d3,a62fba7e-e362-493c-a094-fdec17e2fee8 -Groups 37da2d58-fc14-453e-9a14-5065ebd63a1d, 37da2d58-fc14-453e-9a14-5065ebd63a1e -Operation add +``` +Updates the tenant setting for EnableCopilotExtensibility to 2 users and 2 groups. + +### Example 2 + +```powershell +PS C:\> Update-M365UnifiedTenantSettings -SettingName GlobalApp -SettingValue None +``` +Updates the tenant setting for GlobalApp to None + +## PARAMETERS + +### -SettingName + +Setting Name to be changed. + +```yaml +Type: String +Parameter Sets: (DefaultApp, GlobalApp, PrivateApp, EnableCopilotExtensibility) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -SettingValue +Setting Value to be changed. + +```yaml +Type: String +Parameter Sets: (All, None, Some) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Operation + +Operation performed (whether we are adding or removing users/groups). + +```yaml +Type: String +Parameter Sets: (add, remove) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Users + +List of all the users for whom the app is enabled or disabled. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Groups + +List of all the groups for whom the app is enabled or disabled. + +```yaml +Type: String[] +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/teams/Update-TeamsAppInstallation.md b/teams/teams-ps/teams/Update-TeamsAppInstallation.md index f365734195..d7ce547680 100644 --- a/teams/teams-ps/teams/Update-TeamsAppInstallation.md +++ b/teams/teams-ps/teams/Update-TeamsAppInstallation.md @@ -1,10 +1,11 @@ --- external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml Module Name: MicrosoftTeams -online version: https://docs.microsoft.com/powershell/module/teams/update-teamsappinstallation +online version: https://learn.microsoft.com/powershell/module/teams/update-teamsappinstallation +title: Update-TeamsAppInstallation schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -29,6 +30,9 @@ Update-TeamsAppInstallation [-AppInstallationId <String>] [-AppId <String>] -Use ## DESCRIPTION Update a Teams App in Microsoft Teams. +This won't update teams client; this will update an application installed on the user/team. + +Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see [Install Teams PowerShell public preview](https://learn.microsoft.com/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview) and also see [Microsoft Teams PowerShell Release Notes](https://learn.microsoft.com/microsoftteams/teams-powershell-release-notes). ## EXAMPLES @@ -39,6 +43,13 @@ PS C:\> Update-TeamsAppInstallation -AppId b9cc7986-dd56-4b57-ab7d-9c4e5288b775 This example updates a Teams App in Microsoft Teams specifying its AppId and TeamId. +### Example 2 +```powershell +PS C:\> Update-TeamsAppInstallation -AppId b9cc7986-dd56-4b57-ab7d-9c4e5288b775 -TeamId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df -Permissions "TeamSettings.Read.Group ChannelMessage.Read.Group" +``` + +This example updates a Teams App in Microsoft Teams specifying its AppId and TeamId and RSC Permissions. + ## PARAMETERS ### -AppId @@ -126,6 +137,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## OUTPUTS ### System.Object + ## NOTES ## RELATED LINKS diff --git a/teams/teams-ps/teams/export-csonlineaudiofile.md b/teams/teams-ps/teams/export-csonlineaudiofile.md new file mode 100644 index 0000000000..f0b747b543 --- /dev/null +++ b/teams/teams-ps/teams/export-csonlineaudiofile.md @@ -0,0 +1,97 @@ +--- +external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml +online version: https://learn.microsoft.com/powershell/module/teams/export-csonlineaudiofile +applicable: Microsoft Teams +title: Export-CsOnlineAudioFile +schema: 2.0.0 +manager: bulenteg +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Export-CsOnlineAudioFile + +## SYNOPSIS +Use the Export-CsOnlineAudioFile cmdlet to download an existing audio file. + +## SYNTAX + +```powershell +Export-CsOnlineAudioFile [[-Identity] <string>] [-ApplicationId <String>] [<CommonParameters>] +``` + +## DESCRIPTION +The Export-CsOnlineAudioFile cmdlet downloads an existing Auto Attendant (AA), Call Queue (CQ) service or Music on Hold audio file. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +```powershell +$content=Export-CsOnlineAudioFile -ApplicationId "HuntGroup" -Identity 57f800408f8848548dd1fbc18073fe46 +[System.IO.File]::WriteAllBytes('C:\MyWaveFile.wav', $content) +``` + +This example exports a Call Queue audio file and saves it as MyWaveFile.wav. + +## PARAMETERS + +### -ApplicationId +The ApplicationId parameter is the identifier for the application which will use this audio file. For example, if the audio file is used with an organizational auto attendant, then it needs to be set to "OrgAutoAttendant". If the audio file is used with a hunt group (call queue), then it needs to be set to "HuntGroup". If the audio file is used with Microsoft Teams, then it needs to be set to "TenantGlobal" + +Supported values: + +- OrgAutoAttendant +- HuntGroup +- TenantGlobal + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Microsoft Teams + +Required: True +Position: Named +Default value: TenantGlobal +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity +The Id of the specific audio file that you would like to export. + +```yaml +Type: System.String +Parameter Sets: (All) +Aliases: + +Required: False +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### Byte[] + +## NOTES +The audio content generated by Export-CsOnlineAudioFile is always in WAV format (PCM 16 bit and mono) irrespective on which format the audio was imported as. +Therefore, ensure that the file extension used to store the content is WAV. + +You are responsible for independently clearing and securing all necessary rights and permissions to use any music or audio file with your Microsoft Teams service, which may include intellectual property and other rights in any music, sound effects, audio, brands, names, and other content in the audio file from all relevant rights holders, which may include artists, actors, performers, musicians, songwriters, composers, record labels, music publishers, unions, guilds, rights societies, collective management organizations and any other parties who own, control or license the music copyrights, sound effects, audio and other intellectual property rights. + +## RELATED LINKS +[Get-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/get-csonlineaudiofile) + +[Import-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/import-csonlineaudiofile) + +[Remove-CsOnlineAudioFile](https://learn.microsoft.com/powershell/module/teams/remove-csonlineaudiofile) diff --git a/teams/teams-ps/teams/get-csteamsmessagingconfiguration.md b/teams/teams-ps/teams/get-csteamsmessagingconfiguration.md new file mode 100644 index 0000000000..fc5ad06309 --- /dev/null +++ b/teams/teams-ps/teams/get-csteamsmessagingconfiguration.md @@ -0,0 +1,93 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/Get-CsTeamsMessagingConfiguration +title: Get-CsTeamsMessagingConfiguration +schema: 2.0.0 +--- + +# Get-CsTeamsMessagingConfiguration + +## SYNOPSIS + +TeamsMessagingConfiguration determines the messaging settings for users. This cmdlet returns your organization's current settings. + +## SYNTAX + +### Identity (Default) + +```powershell +Get-CsTeamsMessagingConfiguration [[-Identity] <String>] [<CommonParameters>] +``` + +### Filter + +```powershell +Get-CsTeamsMessagingConfiguration [-Filter <String>] [<CommonParameters>] +``` + +## DESCRIPTION + +TeamsMessagingConfiguration determines the messaging settings for users. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Get-CsTeamsMessagingConfiguration +``` + +The command shown in Example 1 returns teams messaging configuration information for the current tenant. + +## PARAMETERS + +### -Filter + +Enables you to use wildcard characters in order to return a collection of tenant messaging configuration settings. Because each tenant is limited to a single, global collection of the messaging configuration settings there is no need to use the Filter parameter. + +```yaml +Type: String +Parameter Sets: Filter +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Identity + +Specifies the collection of tenant messaging configuration settings to be returned. Because each tenant is limited to a single, global collection of messaging settings there is no need include this parameter when calling the cmdlet. If you do choose to use the Identity parameter you must also include the Tenant parameter. + +```yaml +Type: String +Parameter Sets: Identity +Aliases: + +Required: False +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### None + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Set-CsTeamsMessagingConfiguration](https://learn.microsoft.com/powershell/module/teams/set-csteamsmessagingconfiguration) diff --git a/teams/teams-ps/teams/set-csteamsmessagingconfiguration.md b/teams/teams-ps/teams/set-csteamsmessagingconfiguration.md new file mode 100644 index 0000000000..79f4c96eb3 --- /dev/null +++ b/teams/teams-ps/teams/set-csteamsmessagingconfiguration.md @@ -0,0 +1,289 @@ +--- +external help file: Microsoft.Teams.Policy.Administration.Cmdlets.Core.dll-Help.xml +Module Name: MicrosoftTeams +online version: https://learn.microsoft.com/powershell/module/teams/Set-CsTeamsMessagingConfiguration +title: Set-CsTeamsMessagingConfiguration +schema: 2.0.0 +--- + +# Set-CsTeamsMessagingConfiguration + +## SYNOPSIS + +The TeamsMessagingConfiguration determines the messaging settings for users in your tenant. + +## SYNTAX + +```powershell +Set-CsTeamsMessagingConfiguration [-Identity] <String> + [-Confirm] + [-CustomEmojis <Boolean>] + [-EnableInOrganizationChatControl <Boolean>] + [-EnableVideoMessageCaptions <Boolean>] + [-FileTypeCheck <string>] + [-Force] + [-MessagingNotes <String>] + [-UrlReputationCheck <string>] + [-ContentBasedPhishingCheck <string>] + [-ReportIncorrectSecurityDetections<string>] + [-WhatIf] + [<CommonParameters>] +``` + +## DESCRIPTION + +TeamsMessagingConfiguration determines the messaging settings for the users in your tenant. This cmdlet lets you update the user messaging options you'd like to enable in your organization. + +## EXAMPLES + +### Example 1 + +```powershell +PS C:\> Set-CsTeamsMessagingConfiguration -CustomEmojis $False +``` + +The command shown in example 1 disables custom emojis within Teams. + +## PARAMETERS + +### -Identity + +Specifies the collection of tenant messaging configuration settings to be returned. Because each tenant is limited to a single, global collection of messaging settings there is no need include this parameter when calling the cmdlet. If you do choose to use the Identity parameter you must also include the Tenant parameter. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +Prompts you for confirmation before running the cmdlet. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CustomEmojis + +This setting enables/disables the use of custom emojis and reactions across the whole tenant. Upon enablement, admins and/or users can define a user group that is allowed. +Possible Values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableInOrganizationChatControl + +This setting determines if chat regulation for internal communication in tenant is allowed. +Possible Values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -EnableVideoMessageCaptions + + This setting determines if closed captions will be displayed, for Teams Video Clips, during playback. + Possible values: True, False + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FileTypeCheck + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +This setting determines if FileType check in teams messaging across the whole tenant + +Possible Values: +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Force + +The Force switch specifies whether to suppress warning and confirmation messages. It can be useful in scripting to suppress interactive prompts. If the Force switch isn't provided in the command, you're prompted for administrative input if required. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -MessagingNotes + +This setting enables/disables MessagingNotes integration across the whole tenant. Possible Values: Disabled, Enabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UrlReputationCheck + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +This setting determines if UrlReputationCheck check in teams messaging across the whole tenant + +Possible Values: +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ContentBasedPhishingCheck + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +This setting determines if Content Based Phishing Check in teams messaging across the whole tenant + +Possible Values: +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ReportIncorrectSecurityDetections + +>[!NOTE] +>This feature has not been released yet and will have no changes if it is enabled or disabled. + +This setting determines if Report Incorrect Security Detections is enabled in teams messaging across the whole tenant + +Possible Values: +- Enabled +- Disabled + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: Enabled +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +Shows what would happen if the cmdlet runs. +The cmdlet is not run. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### 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](http://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### System.Management.Automation.PSObject + +## OUTPUTS + +### System.Object + +## NOTES + +## RELATED LINKS + +[Get-CsTeamsMessagingConfiguration](https://learn.microsoft.com/powershell/module/teams/get-csteamsmessagingconfiguration) diff --git a/teams/teams-ps/teams/teams.md b/teams/teams-ps/teams/teams.md index 51bffeb0fb..058504f325 100644 --- a/teams/teams-ps/teams/teams.md +++ b/teams/teams-ps/teams/teams.md @@ -12,94 +12,537 @@ The following cmdlet references are for Microsoft Teams. ## Microsoft Teams Cmdlets ### [Add-TeamChannelUser](Add-TeamChannelUser.md) -{{Manually Enter Add-TeamChannelUser Description Here}} - +### [Add-TeamsAppInstallation](Add-TeamsAppInstallation.md) ### [Add-TeamUser](Add-TeamUser.md) -{{Manually Enter Add-TeamUser Description Here}} - +### [Clear-CsOnlineTelephoneNumberOrder](Clear-CsOnlineTelephoneNumberOrder.md) +### [Clear-TeamsEnvironmentConfig](Clear-TeamsEnvironmentConfig.md) +### [Complete-CsOnlineTelephoneNumberOrder](Complete-CsOnlineTelephoneNumberOrder.md) ### [Connect-MicrosoftTeams](Connect-MicrosoftTeams.md) -{{Manually Enter Connect-MicrosoftTeams Description Here}} - +### [Disable-CsOnlineSipDomain](Disable-CsOnlineSipDomain.md) +### [Disable-CsTeamsShiftsConnectionErrorReport](Disable-CsTeamsShiftsConnectionErrorReport.md) ### [Disconnect-MicrosoftTeams](Disconnect-MicrosoftTeams.md) -{{Manually Enter Disconnect-MicrosoftTeams Description Here}} - +### [Enable-CsOnlineSipDomain](Enable-CsOnlineSipDomain.md) +### [Export-CsAcquiredPhoneNumber](Export-CsAcquiredPhoneNumber.md) +### [Export-CsAutoAttendantHolidays](Export-CsAutoAttendantHolidays.md) +### [export-csonlineaudiofile](export-csonlineaudiofile.md) +### [Find-CsGroup](Find-CsGroup.md) +### [Find-CsOnlineApplicationInstance](Find-CsOnlineApplicationInstance.md) +### [Get-AssociatedTeam](Get-AssociatedTeam.md) +### [Get-CsApplicationAccessPolicy](Get-CsApplicationAccessPolicy.md) +### [Get-CsApplicationMeetingConfiguration](Get-CsApplicationMeetingConfiguration.md) +### [Get-CsAutoAttendant](Get-CsAutoAttendant.md) +### [Get-CsAutoAttendantHolidays](Get-CsAutoAttendantHolidays.md) +### [Get-CsAutoAttendantStatus](Get-CsAutoAttendantStatus.md) +### [Get-CsAutoAttendantSupportedLanguage](Get-CsAutoAttendantSupportedLanguage.md) +### [Get-CsAutoAttendantSupportedTimeZone](Get-CsAutoAttendantSupportedTimeZone.md) +### [Get-CsAutoAttendantTenantInformation](Get-CsAutoAttendantTenantInformation.md) +### [Get-CsBatchPolicyAssignmentOperation](Get-CsBatchPolicyAssignmentOperation.md) +### [Get-CsBatchTeamsDeploymentStatus](Get-CsBatchTeamsDeploymentStatus.md) +### [Get-CsCallingLineIdentity](Get-CsCallingLineIdentity.md) +### [Get-CsCallQueue](Get-CsCallQueue.md) +### [Get-CsCloudCallDataConnection](Get-CsCloudCallDataConnection.md) +### [Get-CsDialPlan](Get-CsDialPlan.md) +### [Get-CsEffectiveTenantDialPlan](Get-CsEffectiveTenantDialPlan.md) +### [Get-CsExportAcquiredPhoneNumberStatus](Get-CsExportAcquiredPhoneNumberStatus.md) +### [Get-CsExternalAccessPolicy](Get-CsExternalAccessPolicy.md) +### [Get-CsGroupPolicyAssignment](Get-CsGroupPolicyAssignment.md) +### [Get-CsHybridTelephoneNumber](Get-CsHybridTelephoneNumber.md) +### [Get-CsInboundBlockedNumberPattern](Get-CsInboundBlockedNumberPattern.md) +### [Get-CsInboundExemptNumberPattern](Get-CsInboundExemptNumberPattern.md) +### [Get-CsMeetingMigrationStatus](Get-CsMeetingMigrationStatus.md) +### [Get-CsOnlineApplicationInstance](Get-CsOnlineApplicationInstance.md) +### [Get-CsOnlineApplicationInstanceAssociation](Get-CsOnlineApplicationInstanceAssociation.md) +### [Get-CsOnlineApplicationInstanceAssociationStatus](Get-CsOnlineApplicationInstanceAssociationStatus.md) +### [Get-CsCsOnlineAudioConferencingRoutingPolicy][Get-CsOnlineAudioConferencingRoutingPolicy.md] +### [Get-CsOnlineAudioFile](Get-CsOnlineAudioFile.md) +### [Get-CsOnlineDialinConferencingPolicy](Get-CsOnlineDialinConferencingPolicy.md) +### [Get-CsOnlineDialInConferencingServiceNumber](Get-CsOnlineDialInConferencingServiceNumber.md) +### [Get-CsOnlineDialinConferencingTenantConfiguration](Get-CsOnlineDialinConferencingTenantConfiguration.md) +### [Get-CsOnlineDialInConferencingTenantSettings](Get-CsOnlineDialInConferencingTenantSettings.md) +### [Get-CsOnlineDialInConferencingUser](Get-CsOnlineDialInConferencingUser.md) +### [Get-CsOnlineDialOutPolicy](Get-CsOnlineDialOutPolicy.md) +### [Get-CsOnlineDirectoryTenant](Get-CsOnlineDirectoryTenant.md) +### [Get-CsOnlineEnhancedEmergencyServiceDisclaimer](Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md) +### [Get-CsOnlineLisCivicAddress](Get-CsOnlineLisCivicAddress.md) +### [Get-CsOnlineLisLocation](Get-CsOnlineLisLocation.md) +### [Get-CsOnlineLisPort](Get-CsOnlineLisPort.md) +### [Get-CsOnlineLisSubnet](Get-CsOnlineLisSubnet.md) +### [Get-CsOnlineLisSwitch](Get-CsOnlineLisSwitch.md) +### [Get-CsOnlineLisWirelessAccessPoint](Get-CsOnlineLisWirelessAccessPoint.md) +### [Get-CsOnlinePSTNGateway](Get-CsOnlinePSTNGateway.md) +### [Get-CsOnlinePstnUsage](Get-CsOnlinePstnUsage.md) +### [Get-CsOnlineSchedule](Get-CsOnlineSchedule.md) +### [Get-CsOnlineSipDomain](Get-CsOnlineSipDomain.md) +### [Get-CsOnlineTelephoneNumber](Get-CsOnlineTelephoneNumber.md) +### [Get-CsOnlineTelephoneNumberCountry](Get-CsOnlineTelephoneNumberCountry.md) +### [Get-CsOnlineTelephoneNumberOrder](Get-CsOnlineTelephoneNumberOrder.md) +### [Get-CsOnlineTelephoneNumberType](Get-CsOnlineTelephoneNumberType.md) +### [Get-CsOnlineUser](Get-CsOnlineUser.md) +### [Get-CsOnlineVoicemailPolicy](Get-CsOnlineVoicemailPolicy.md) +### [Get-CsOnlineVoicemailUserSettings](Get-CsOnlineVoicemailUserSettings.md) +### [Get-CsOnlineVoiceRoute](Get-CsOnlineVoiceRoute.md) +### [Get-CsOnlineVoiceRoutingPolicy](Get-CsOnlineVoiceRoutingPolicy.md) +### [Get-CsOnlineVoiceUser](Get-CsOnlineVoiceUser.md) +### [Get-CsPhoneNumberAssignment](Get-CsPhoneNumberAssignment.md) +### [Get-CsPolicyPackage](Get-CsPolicyPackage.md) +### [Get-CsTeamsAcsFederationConfiguration](Get-CsTeamsAcsFederationConfiguration.md) +### [Get-CsTeamsAppPermissionPolicy](Get-CsTeamsAppPermissionPolicy.md) +### [Get-CsTeamsAppSetupPolicy](Get-CsTeamsAppSetupPolicy.md) +### [Get-CsTeamsAudioConferencingPolicy](Get-CsTeamsAudioConferencingPolicy.md) +### [Get-CsTeamsCallHoldPolicy](Get-CsTeamsCallHoldPolicy.md) +### [Get-CsTeamsCallingPolicy](Get-CsTeamsCallingPolicy.md) +### [Get-CsTeamsCallParkPolicy](Get-CsTeamsCallParkPolicy.md) +### [Get-CsTeamsChannelsPolicy](Get-CsTeamsChannelsPolicy.md) +### [Get-CsTeamsClientConfiguration](Get-CsTeamsClientConfiguration.md) +### [Get-CsTeamsComplianceRecordingApplication](Get-CsTeamsComplianceRecordingApplication.md) +### [Get-CsTeamsComplianceRecordingPolicy](Get-CsTeamsComplianceRecordingPolicy.md) +### [Get-CsTeamsCortanaPolicy](Get-CsTeamsCortanaPolicy.md) +### [Get-CsTeamsCustomBannerText](Get-CsTeamsCustomBannerText.md) +### [Get-CsTeamsCustomBannerText](Get-CsTeamsCustomBannerText.md) +### [Get-CsTeamsEducationAssignmentsAppPolicy](Get-CsTeamsEducationAssignmentsAppPolicy.md) +### [Get-CsTeamsEducationConfiguration](Get-CsTeamsEducationConfiguration.md) +### [Get-CsTeamsEmergencyCallingPolicy](Get-CsTeamsEmergencyCallingPolicy.md) +### [Get-CsTeamsEmergencyCallRoutingPolicy](Get-CsTeamsEmergencyCallRoutingPolicy.md) +### [Get-CsTeamsEnhancedEncryptionPolicy](Get-CsTeamsEnhancedEncryptionPolicy.md) +### [Get-CsTeamsEventsPolicy](Get-CsTeamsEventsPolicy.md) +### [Get-CsTeamsFeedbackPolicy](Get-CsTeamsFeedbackPolicy.md) +### [Get-CsTeamsFilesPolicy](Get-CsTeamsFilesPolicy.md) +### [Get-CsTeamsFirstPartyMeetingTemplateConfiguration](Get-CsTeamsFirstPartyMeetingTemplateConfiguration.md) +### [Get-CsTeamsGuestCallingConfiguration](Get-CsTeamsGuestCallingConfiguration.md) +### [Get-CsTeamsGuestMeetingConfiguration](Get-CsTeamsGuestMeetingConfiguration.md) +### [Get-CsTeamsGuestMessagingConfiguration](Get-CsTeamsGuestMessagingConfiguration.md) +### [Get-CsTeamsIPPhonePolicy](Get-CsTeamsIPPhonePolicy.md) +### [Get-CsTeamsMediaLoggingPolicy](Get-CsTeamsMediaLoggingPolicy.md) +### [Get-CsTeamsMeetingBrandingPolicy](Get-CsTeamsMeetingBrandingPolicy.md) +### [Get-CsTeamsMeetingBroadcastConfiguration](Get-CsTeamsMeetingBroadcastConfiguration.md) +### [Get-CsTeamsMeetingBroadcastPolicy](Get-CsTeamsMeetingBroadcastPolicy.md) +### [Get-CsTeamsMeetingConfiguration](Get-CsTeamsMeetingConfiguration.md) +### [Get-CsTeamsMeetingPolicy](Get-CsTeamsMeetingPolicy.md) +### [Get-CsTeamsMeetingTemplateConfiguration](Get-CsTeamsMeetingTemplateConfiguration.md) +### [Get-CsTeamsMeetingTemplatePermissionPolicy](Get-CsTeamsMeetingTemplatePermissionPolicy.md) +### [Get-CsTeamsMessagingConfiguration](Get-CsTeamsMessagingConfiguration.md) +### [Get-CsTeamsMessagingPolicy](Get-CsTeamsMessagingPolicy.md) +### [Get-CsTeamsMobilityPolicy](Get-CsTeamsMobilityPolicy.md) +### [Get-CsTeamsNetworkRoamingPolicy](Get-CsTeamsNetworkRoamingPolicy.md) +### [Get-CsTeamsRecordingRollOutPolicy](Get-CsTeamsRecordingRollOutPolicy.md) +### [Get-CsTeamsSharedCallingRoutingPolicy](Get-CsTeamsSharedCallingRoutingPolicy.md) +### [Get-CsTeamsShiftsConnection](Get-CsTeamsShiftsConnection.md) +### [Get-CsTeamsShiftsConnectionConnector](Get-CsTeamsShiftsConnectionConnector.md) +### [Get-CsTeamsShiftsConnectionErrorReport](Get-CsTeamsShiftsConnectionErrorReport.md) +### [Get-CsTeamsShiftsConnectionInstance](Get-CsTeamsShiftsConnectionInstance.md) +### [Get-CsTeamsShiftsConnectionOperation](Get-CsTeamsShiftsConnectionOperation.md) +### [Get-CsTeamsShiftsConnectionSyncResult](Get-CsTeamsShiftsConnectionSyncResult.md) +### [Get-CsTeamsShiftsConnectionTeamMap](Get-CsTeamsShiftsConnectionTeamMap.md) +### [Get-CsTeamsShiftsConnectionWfmTeam](Get-CsTeamsShiftsConnectionWfmTeam.md) +### [Get-CsTeamsShiftsConnectionWfmUser](Get-CsTeamsShiftsConnectionWfmUser.md) +### [Get-CsTeamsShiftsPolicy](Get-CsTeamsShiftsPolicy.md) +### [Get-CsTeamsSipDevicesConfiguration](Get-CsTeamsSipDevicesConfiguration.md) +### [Get-CsTeamsSurvivableBranchAppliance](Get-CsTeamsSurvivableBranchAppliance.md) +### [Get-CsTeamsSurvivableBranchAppliancePolicy](Get-CsTeamsSurvivableBranchAppliancePolicy.md) +### [Get-CsTeamsTargetingPolicy](Get-CsTeamsTargetingPolicy.md) +### [Get-CsTeamsTemplatePermissionPolicy](Get-CsTeamsTemplatePermissionPolicy.md) +### [Get-CsTeamsTranslationRule](Get-CsTeamsTranslationRule.md) +### [Get-CsTeamsUnassignedNumberTreatment](Get-CsTeamsUnassignedNumberTreatment.md) +### [Get-CsTeamsUpdateManagementPolicy](Get-CsTeamsUpdateManagementPolicy.md) +### [Get-CsTeamsUpgradeConfiguration](Get-CsTeamsUpgradeConfiguration.md) +### [Get-CsTeamsUpgradePolicy](Get-CsTeamsUpgradePolicy.md) +### [Get-CsTeamsVdiPolicy](Get-CsTeamsVdiPolicy.md) +### [Get-CsTeamsVideoInteropServicePolicy](Get-CsTeamsVideoInteropServicePolicy.md) +### [Get-CsTeamsVirtualAppointmentsPolicy](Get-CsTeamsVirtualAppointmentsPolicy.md) +### [Get-CsTeamsVoiceApplicationsPolicy](Get-CsTeamsVoiceApplicationsPolicy.md) +### [Get-CsTeamsWorkLoadPolicy](Get-CsTeamsWorkLoadPolicy.md) +### [Get-CsTeamsWorkLocationDetectionPolicy](Get-CsTeamsWorkLocationDetectionPolicy.md) +### [Get-CsTeamTemplate](Get-CsTeamTemplate.md) +### [Get-CsTeamTemplateList](Get-CsTeamTemplateList.md) +### [Get-CsTenant](Get-CsTenant.md) +### [Get-CsTenantBlockedCallingNumbers](Get-CsTenantBlockedCallingNumbers.md) +### [Get-CsTenantDialPlan](Get-CsTenantDialPlan.md) +### [Get-CsTenantFederationConfiguration](Get-CsTenantFederationConfiguration.md) +### [Get-CsTenantLicensingConfiguration](Get-CsTenantLicensingConfiguration.md) +### [Get-CsTenantMigrationConfiguration](Get-CsTenantMigrationConfiguration.md) +### [Get-CsTenantNetworkRegion](Get-CsTenantNetworkRegion.md) +### [Get-CsTenantNetworkSite](Get-CsTenantNetworkSite.md) +### [Get-CsTenantNetworkSubnet](Get-CsTenantNetworkSubnet.md) +### [Get-CsTenantTrustedIPAddress](Get-CsTenantTrustedIPAddress.md) +### [Get-CsUserCallingSettings](Get-CsUserCallingSettings.md) +### [Get-CsUserPolicyAssignment](Get-CsUserPolicyAssignment.md) +### [Get-CsUserPolicyPackage](Get-CsUserPolicyPackage.md) +### [Get-CsUserPolicyPackageRecommendation](Get-CsUserPolicyPackageRecommendation.md) +### [Get-CsVideoInteropServiceProvider](Get-CsVideoInteropServiceProvider.md) +### [Get-LicenseReportForChangeNotificationSubscription](Get-LicenseReportForChangeNotificationSubscription.md) +### [Get-M365UnifiedCustomPendingApps](Get-M365UnifiedCustomPendingApps.md) +### [Get-SharedWithTeam](Get-SharedWithTeam.md) +### [Get-SharedWithTeamUser](Get-SharedWithTeamUser.md) ### [Get-Team](Get-Team.md) -{{Manually Enter Get-Team Description Here}} - +### [Get-TeamAllChannel](Get-TeamAllChannel.md) ### [Get-TeamChannel](Get-TeamChannel.md) -{{Manually Enter Get-TeamChannel Description Here}} - ### [Get-TeamChannelUser](Get-TeamChannelUser.md) -{{Manually Enter Get-TeamChannelUser Description Here}} - ### [Get-TeamFunSettings](Get-TeamFunSettings.md) -{{Manually Enter Get-TeamFunSettings Description Here}} - ### [Get-TeamGuestSettings](Get-TeamGuestSettings.md) -{{Manually Enter Get-TeamGuestSettings Description Here}} - -### [Get-TeamHelp](Get-TeamHelp.md) -{{Manually Enter Get-TeamHelp Description Here}} - +### [Get-TeamIncomingChannel](Get-TeamIncomingChannel.md) ### [Get-TeamMemberSettings](Get-TeamMemberSettings.md) -{{Manually Enter Get-TeamMemberSettings Description Here}} - ### [Get-TeamMessagingSettings](Get-TeamMessagingSettings.md) -{{Manually Enter Get-TeamMessagingSettings Description Here}} - ### [Get-TeamsApp](Get-TeamsApp.md) -{{Manually Enter Get-TeamsApp Description Here}} - +### [Get-TeamsAppInstallation](Get-TeamsAppInstallation.md) +### [Get-TeamTargetingHierarchyStatus](Get-TeamTargetingHierarchyStatus.md) ### [Get-TeamUser](Get-TeamUser.md) -{{Manually Enter Get-TeamUser Description Here}} - +### [Grant-CsApplicationAccessPolicy](Grant-CsApplicationAccessPolicy.md) +### [Grant-CsCallingLineIdentity](Grant-CsCallingLineIdentity.md) +### [Grant-CsCloudMeetingPolicy](Grant-CsCloudMeetingPolicy.md) +### [Grant-CsDialoutPolicy](Grant-CsDialoutPolicy.md) +### [Grant-CsExternalAccessPolicy](Grant-CsExternalAccessPolicy.md) +### [Grant-CsExternalUserCommunicationPolicy](Grant-CsExternalUserCommunicationPolicy.md) +### [Grant-CsGroupPolicyPackageAssignment](Grant-CsGroupPolicyPackageAssignment.md) +### [Grant-CsOnlineVoicemailPolicy](Grant-CsOnlineVoicemailPolicy.md) +### [Grant-CsOnlineVoiceRoutingPolicy](Grant-CsOnlineVoiceRoutingPolicy.md) +### [Grant-CsTeamsAppPermissionPolicy](Grant-CsTeamsAppPermissionPolicy.md) +### [Grant-CsTeamsAppSetupPolicy](Grant-CsTeamsAppSetupPolicy.md) +### [Grant-CsTeamsAudioConferencingPolicy](Grant-CsTeamsAudioConferencingPolicy.md) +### [Grant-CsTeamsCallHoldPolicy](Grant-CsTeamsCallHoldPolicy.md) +### [Grant-CsTeamsCallingPolicy](Grant-CsTeamsCallingPolicy.md) +### [Grant-CsTeamsCallParkPolicy](Grant-CsTeamsCallParkPolicy.md) +### [Grant-CsTeamsChannelsPolicy](Grant-CsTeamsChannelsPolicy.md) +### [Grant-CsTeamsComplianceRecordingPolicy](Grant-CsTeamsComplianceRecordingPolicy.md) +### [Grant-CsTeamsCortanaPolicy](Grant-CsTeamsCortanaPolicy.md) +### [Grant-CsTeamsEmergencyCallingPolicy](Grant-CsTeamsEmergencyCallingPolicy.md) +### [Grant-CsTeamsEmergencyCallRoutingPolicy](Grant-CsTeamsEmergencyCallRoutingPolicy.md) +### [Grant-CsTeamsEnhancedEncryptionPolicy](Grant-CsTeamsEnhancedEncryptionPolicy.md) +### [Grant-CsTeamsEventsPolicy](Grant-CsTeamsEventsPolicy.md) +### [Grant-CsTeamsFeedbackPolicy](Grant-CsTeamsFeedbackPolicy.md) +### [Grant-CsTeamsFilesPolicy](Grant-CsTeamsFilesPolicy.md) +### [Grant-CsTeamsIPPhonePolicy](Grant-CsTeamsIPPhonePolicy.md) +### [Grant-CsTeamsMediaLoggingPolicy](Grant-CsTeamsMediaLoggingPolicy.md) +### [Grant-CsTeamsMeetingBrandingPolicy](Grant-CsTeamsMeetingBrandingPolicy.md) +### [Grant-CsTeamsMeetingBroadcastPolicy](Grant-CsTeamsMeetingBroadcastPolicy.md) +### [Grant-CsTeamsMeetingPolicy](Grant-CsTeamsMeetingPolicy.md) +### [Grant-CsTeamsMeetingTemplatePermissionPolicy](Grant-CsTeamsMeetingTemplatePermissionPolicy.md) +### [Grant-CsTeamsMessagingPolicy](Grant-CsTeamsMessagingPolicy.md) +### [Grant-CsTeamsMobilityPolicy](Grant-CsTeamsMobilityPolicy.md) +### [Grant-CsTeamsRecordingRollOutPolicy](Grant-CsTeamsRecordingRollOutPolicy.md) +### [Grant-CsTeamsSharedCallingRoutingPolicy](Grant-CsTeamsSharedCallingRoutingPolicy.md) +### [Grant-CsTeamsShiftsPolicy](Grant-CsTeamsShiftsPolicy.md) +### [Grant-CsTeamsUpdateManagementPolicy](Grant-CsTeamsUpdateManagementPolicy.md) +### [Grant-CsTeamsUpgradePolicy](Grant-CsTeamsUpgradePolicy.md) +### [Grant-CsTeamsVdiPolicy](Grant-CsTeamsVdiPolicy.md) +### [Grant-CsTeamsVideoInteropServicePolicy](Grant-CsTeamsVideoInteropServicePolicy.md) +### [Grant-CsTeamsVirtualAppointmentsPolicy](Grant-CsTeamsVirtualAppointmentsPolicy.md) +### [Grant-CsTeamsVoiceApplicationsPolicy](Grant-CsTeamsVoiceApplicationsPolicy.md) +### [Grant-CsTeamsWorkLoadPolicy](Grant-CsTeamsWorkLoadPolicy.md) +### [Grant-CsTeamsWorkLocationDetectionPolicy](Grant-CsTeamsWorkLocationDetectionPolicy.md) +### [Grant-CsTenantDialPlan](Grant-CsTenantDialPlan.md) +### [Grant-CsUserPolicyPackage](Grant-CsUserPolicyPackage.md) +### [Import-CsAutoAttendantHolidays](Import-CsAutoAttendantHolidays.md) +### [Import-CsOnlineAudioFile](Import-CsOnlineAudioFile.md) +### [New-CsApplicationAccessPolicy](New-CsApplicationAccessPolicy.md) +### [New-CsAutoAttendant](New-CsAutoAttendant.md) +### [New-CsAutoAttendantCallableEntity](New-CsAutoAttendantCallableEntity.md) +### [New-CsAutoAttendantCallFlow](New-CsAutoAttendantCallFlow.md) +### [New-CsAutoAttendantCallHandlingAssociation](New-CsAutoAttendantCallHandlingAssociation.md) +### [New-CsAutoAttendantDialScope](New-CsAutoAttendantDialScope.md) +### [New-CsAutoAttendantMenu](New-CsAutoAttendantMenu.md) +### [New-CsAutoAttendantMenuOption](New-CsAutoAttendantMenuOption.md) +### [New-CsAutoAttendantPrompt](New-CsAutoAttendantPrompt.md) +### [New-CsBatchPolicyAssignmentOperation](New-CsBatchPolicyAssignmentOperation.md) +### [New-CsBatchPolicyPackageAssignmentOperation](New-CsBatchPolicyPackageAssignmentOperation.md) +### [New-CsBatchTeamsDeployment](New-CsBatchTeamsDeployment.md) +### [New-CsCallingLineIdentity](New-CsCallingLineIdentity.md) +### [New-CsCallQueue](New-CsCallQueue.md) +### [New-CsCloudCallDataConnection](New-CsCloudCallDataConnection.md) +### [New-CsCustomPolicyPackage](New-CsCustomPolicyPackage.md) +### [New-CsEdgeAllowAllKnownDomains](New-CsEdgeAllowAllKnownDomains.md) +### [New-CsEdgeAllowList](New-CsEdgeAllowList.md) +### [New-CsEdgeDomainPattern](New-CsEdgeDomainPattern.md) +### [New-CsExternalAccessPolicy](New-CsExternalAccessPolicy.md) +### [New-CsGroupPolicyAssignment](New-CsGroupPolicyAssignment.md) +### [New-CsHybridTelephoneNumber](New-CsHybridTelephoneNumber.md) +### [New-CsInboundBlockedNumberPattern](New-CsInboundBlockedNumberPattern.md) +### [New-CsInboundExemptNumberPattern](New-CsInboundExemptNumberPattern.md) +### [New-CsOnlineApplicationInstance](New-CsOnlineApplicationInstance.md) +### [New-CsOnlineApplicationInstanceAssociation](New-CsOnlineApplicationInstanceAssociation.md) +### [New-CsCsOnlineAudioConferencingRoutingPolicy][New-CsOnlineAudioConferencingRoutingPolicy.md] +### [New-CsOnlineDateTimeRange](New-CsOnlineDateTimeRange.md) +### [New-CsOnlineLisCivicAddress](New-CsOnlineLisCivicAddress.md) +### [New-CsOnlineLisLocation](New-CsOnlineLisLocation.md) +### [New-CsOnlinePSTNGateway](New-CsOnlinePSTNGateway.md) +### [New-CsOnlineSchedule](New-CsOnlineSchedule.md) +### [New-CsOnlineTelephoneNumberOrder](New-CsOnlineTelephoneNumberOrder.md) +### [New-CsOnlineTimeRange](New-CsOnlineTimeRange.md) +### [New-CsOnlineVoicemailPolicy](New-CsOnlineVoicemailPolicy.md) +### [New-CsOnlineVoiceRoute](New-CsOnlineVoiceRoute.md) +### [New-CsOnlineVoiceRoutingPolicy](New-CsOnlineVoiceRoutingPolicy.md) +### [New-CsTeamsAppPermissionPolicy](New-CsTeamsAppPermissionPolicy.md) +### [New-CsTeamsAppSetupPolicy](New-CsTeamsAppSetupPolicy.md) +### [New-CsTeamsAudioConferencingPolicy](New-CsTeamsAudioConferencingPolicy.md) +### [New-CsTeamsCallHoldPolicy](New-CsTeamsCallHoldPolicy.md) +### [New-CsTeamsCallingPolicy](New-CsTeamsCallingPolicy.md) +### [New-CsTeamsCallParkPolicy](New-CsTeamsCallParkPolicy.md) +### [New-CsTeamsChannelsPolicy](New-CsTeamsChannelsPolicy.md) +### [New-CsTeamsComplianceRecordingApplication](New-CsTeamsComplianceRecordingApplication.md) +### [New-CsTeamsComplianceRecordingPairedApplication](New-CsTeamsComplianceRecordingPairedApplication.md) +### [New-CsTeamsComplianceRecordingPolicy](New-CsTeamsComplianceRecordingPolicy.md) +### [New-CsTeamsCortanaPolicy](New-CsTeamsCortanaPolicy.md) +### [New-CsTeamsCustomBannerText](New-CsTeamsCustomBannerText.md) +### [New-CsTeamsCustomBannerText](New-CsTeamsCustomBannerText.md) +### [New-CsTeamsEmergencyCallingExtendedNotification](New-CsTeamsEmergencyCallingExtendedNotification.md) +### [New-CsTeamsEmergencyCallingPolicy](New-CsTeamsEmergencyCallingPolicy.md) +### [New-CsTeamsEmergencyCallRoutingPolicy](New-CsTeamsEmergencyCallRoutingPolicy.md) +### [New-CsTeamsEmergencyNumber](New-CsTeamsEmergencyNumber.md) +### [New-CsTeamsEnhancedEncryptionPolicy](New-CsTeamsEnhancedEncryptionPolicy.md) +### [New-CsTeamsEventsPolicy](New-CsTeamsEventsPolicy.md) +### [New-CsTeamsFeedbackPolicy](New-CsTeamsFeedbackPolicy.md) +### [New-CsTeamsFilesPolicy](New-CsTeamsFilesPolicy.md) +### [New-CsTeamsHiddenMeetingTemplate](New-CsTeamsHiddenMeetingTemplate.md) +### [New-CsTeamsHiddenTemplate](New-CsTeamsHiddenTemplate.md) +### [New-CsTeamsIPPhonePolicy](New-CsTeamsIPPhonePolicy.md) +### [New-CsTeamsMeetingBrandingPolicy](New-CsTeamsMeetingBrandingPolicy.md) +### [New-CsTeamsMeetingBroadcastPolicy](New-CsTeamsMeetingBroadcastPolicy.md) +### [New-CsTeamsMeetingPolicy](New-CsTeamsMeetingPolicy.md) +### [New-CsTeamsMeetingTemplatePermissionPolicy](New-CsTeamsMeetingTemplatePermissionPolicy.md) +### [New-CsTeamsMessagingPolicy](New-CsTeamsMessagingPolicy.md) +### [New-CsTeamsMobilityPolicy](New-CsTeamsMobilityPolicy.md) +### [New-CsTeamsNetworkRoamingPolicy](New-CsTeamsNetworkRoamingPolicy.md) +### [New-CsTeamsPinnedApp](New-CsTeamsPinnedApp.md) +### [New-CsTeamsRecordingRollOutPolicy](New-CsTeamsRecordingRollOutPolicy.md) +### [New-CsTeamsSharedCallingRoutingPolicy](New-CsTeamsSharedCallingRoutingPolicy.md) +### [New-CsTeamsShiftsConnection](New-CsTeamsShiftsConnection.md) +### [New-CsTeamsShiftsConnectionBatchTeamMap](New-CsTeamsShiftsConnectionBatchTeamMap.md) +### [New-CsTeamsShiftsConnectionInstance](New-CsTeamsShiftsConnectionInstance.md) +### [New-CsTeamsShiftsPolicy](New-CsTeamsShiftsPolicy.md) +### [New-CsTeamsTemplatePermissionPolicy](New-CsTeamsTemplatePermissionPolicy.md) +### [New-CsTeamsTranslationRule](New-CsTeamsTranslationRule.md) +### [New-CsTeamsUnassignedNumberTreatment](New-CsTeamsUnassignedNumberTreatment.md) +### [New-CsTeamsUpdateManagementPolicy](New-CsTeamsUpdateManagementPolicy.md) +### [New-CsTeamsVdiPolicy](New-CsTeamsVdiPolicy.md) +### [New-CsTeamsVirtualAppointmentsPolicy](New-CsTeamsVirtualAppointmentsPolicy.md) +### [New-CsTeamsVoiceApplicationsPolicy](New-CsTeamsVoiceApplicationsPolicy.md) +### [New-CsTeamsWorkLoadPolicy](New-CsTeamsWorkLoadPolicy.md) +### [New-CsTeamsWorkLocationDetectionPolicy](New-CsTeamsWorkLocationDetectionPolicy.md) +### [New-CsTeamTemplate](New-CsTeamTemplate.md) +### [New-CsTenantDialPlan](New-CsTenantDialPlan.md) +### [New-CsTenantNetworkRegion](New-CsTenantNetworkRegion.md) +### [New-CsTenantNetworkSite](New-CsTenantNetworkSite.md) +### [New-CsTenantNetworkSubnet](New-CsTenantNetworkSubnet.md) +### [New-CsTenantTrustedIPAddress](New-CsTenantTrustedIPAddress.md) +### [New-CsUserCallingDelegate](New-CsUserCallingDelegate.md) +### [New-CsVideoInteropServiceProvider](New-CsVideoInteropServiceProvider.md) +### [New-CsVoiceNormalizationRule](New-CsVoiceNormalizationRule.md) ### [New-Team](New-Team.md) -{{Manually Enter New-Team Description Here}} - ### [New-TeamChannel](New-TeamChannel.md) -{{Manually Enter New-TeamChannel Description Here}} - ### [New-TeamsApp](New-TeamsApp.md) -{{Manually Enter New-TeamsApp Description Here}} - +### [Register-CsOnlineDialInConferencingServiceNumber](Register-CsOnlineDialInConferencingServiceNumber.md) +### [Remove-CsApplicationAccessPolicy](Remove-CsApplicationAccessPolicy.md) +### [Remove-CsAutoAttendant](Remove-CsAutoAttendant.md) +### [Remove-CsCallingLineIdentity](Remove-CsCallingLineIdentity.md) +### [Remove-CsCallQueue](Remove-CsCallQueue.md) +### [Remove-CsCustomPolicyPackage](Remove-CsCustomPolicyPackage.md) +### [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md) +### [Remove-CsGroupPolicyAssignment](Remove-CsGroupPolicyAssignment.md) +### [Remove-CsHybridTelephoneNumber](Remove-CsHybridTelephoneNumber.md) +### [Remove-CsInboundBlockedNumberPattern](Remove-CsInboundBlockedNumberPattern.md) +### [Remove-CsInboundExemptNumberPattern](Remove-CsInboundExemptNumberPattern.md) +### [Remove-CsOnlineApplicationInstanceAssociation](Remove-CsOnlineApplicationInstanceAssociation.md) +### [Remove-CsCsOnlineAudioConferencingRoutingPolicy][Remove-CsOnlineAudioConferencingRoutingPolicy.md] +### [Remove-CsOnlineAudioFile](Remove-CsOnlineAudioFile.md) +### [Remove-CsOnlineDialInConferencingTenantSettings](Remove-CsOnlineDialInConferencingTenantSettings.md) +### [Remove-CsOnlineLisCivicAddress](Remove-CsOnlineLisCivicAddress.md) +### [Remove-CsOnlineLisLocation](Remove-CsOnlineLisLocation.md) +### [Remove-CsOnlineLisPort](Remove-CsOnlineLisPort.md) +### [Remove-CsOnlineLisSubnet](Remove-CsOnlineLisSubnet.md) +### [Remove-CsOnlineLisSwitch](Remove-CsOnlineLisSwitch.md) +### [Remove-CsOnlineLisWirelessAccessPoint](Remove-CsOnlineLisWirelessAccessPoint.md) +### [Remove-CsOnlinePSTNGateway](Remove-CsOnlinePSTNGateway.md) +### [Remove-CsOnlineSchedule](Remove-CsOnlineSchedule.md) +### [Remove-CsOnlineTelephoneNumber](Remove-CsOnlineTelephoneNumber.md) +### [Remove-CsOnlineVoicemailPolicy](Remove-CsOnlineVoicemailPolicy.md) +### [Remove-CsOnlineVoiceRoute](Remove-CsOnlineVoiceRoute.md) +### [Remove-CsOnlineVoiceRoutingPolicy](Remove-CsOnlineVoiceRoutingPolicy.md) +### [Remove-CsPhoneNumberAssignment](Remove-CsPhoneNumberAssignment.md) +### [Remove-CsTeamsAppPermissionPolicy](Remove-CsTeamsAppPermissionPolicy.md) +### [Remove-CsTeamsAppSetupPolicy](Remove-CsTeamsAppSetupPolicy.md) +### [Remove-CsTeamsAudioConferencingPolicy](Remove-CsTeamsAudioConferencingPolicy.md) +### [Remove-CsTeamsCallHoldPolicy](Remove-CsTeamsCallHoldPolicy.md) +### [Remove-CsTeamsCallingPolicy](Remove-CsTeamsCallingPolicy.md) +### [Remove-CsTeamsCallParkPolicy](Remove-CsTeamsCallParkPolicy.md) +### [Remove-CsTeamsChannelsPolicy](Remove-CsTeamsChannelsPolicy.md) +### [Remove-CsTeamsComplianceRecordingApplication](Remove-CsTeamsComplianceRecordingApplication.md) +### [Remove-CsTeamsComplianceRecordingPolicy](Remove-CsTeamsComplianceRecordingPolicy.md) +### [Remove-CsTeamsCortanaPolicy](Remove-CsTeamsCortanaPolicy.md) +### [Remove-CsTeamsCustomBannerText](Remove-CsTeamsCustomBannerText.md) +### [Remove-CsTeamsCustomBannerText](Remove-CsTeamsCustomBannerText.md) +### [Remove-CsTeamsEmergencyCallingPolicy](Remove-CsTeamsEmergencyCallingPolicy.md) +### [Remove-CsTeamsEmergencyCallRoutingPolicy](Remove-CsTeamsEmergencyCallRoutingPolicy.md) +### [Remove-CsTeamsEnhancedEncryptionPolicy](Remove-CsTeamsEnhancedEncryptionPolicy.md) +### [Remove-CsTeamsEventsPolicy](Remove-CsTeamsEventsPolicy.md) +### [Remove-CsTeamsFeedbackPolicy](Remove-CsTeamsFeedbackPolicy.md) +### [Remove-CsTeamsFilesPolicy](Remove-CsTeamsFilesPolicy.md) +### [Remove-CsTeamsIPPhonePolicy](Remove-CsTeamsIPPhonePolicy.md) +### [Remove-CsTeamsMeetingBrandingPolicy](Remove-CsTeamsMeetingBrandingPolicy.md) +### [Remove-CsTeamsMeetingBroadcastPolicy](Remove-CsTeamsMeetingBroadcastPolicy.md) +### [Remove-CsTeamsMeetingPolicy](Remove-CsTeamsMeetingPolicy.md) +### [Remove-CsTeamsMeetingTemplatePermissionPolicy](Remove-CsTeamsMeetingTemplatePermissionPolicy.md) +### [Remove-CsTeamsMessagingPolicy](Remove-CsTeamsMessagingPolicy.md) +### [Remove-CsTeamsMobilityPolicy](Remove-CsTeamsMobilityPolicy.md) +### [Remove-CsTeamsNetworkRoamingPolicy](Remove-CsTeamsNetworkRoamingPolicy.md) +### [Remove-CsTeamsPinnedApp](Remove-CsTeamsPinnedApp.md) +### [Remove-CsTeamsRecordingRollOutPolicy](Remove-CsTeamsRecordingRollOutPolicy.md) +### [Remove-CsTeamsSharedCallingRoutingPolicy](Remove-CsTeamsSharedCallingRoutingPolicy.md) +### [Remove-CsTeamsShiftsConnection](Remove-CsTeamsShiftsConnection.md) +### [Remove-CsTeamsShiftsConnectionInstance](Remove-CsTeamsShiftsConnectionInstance.md) +### [Remove-CsTeamsShiftsConnectionTeamMap](Remove-CsTeamsShiftsConnectionTeamMap.md) +### [Remove-CsTeamsShiftsPolicy](Remove-CsTeamsShiftsPolicy.md) +### [Remove-CsTeamsShiftsScheduleRecord](Remove-CsTeamsShiftsScheduleRecord.md) +### [Remove-CsTeamsSurvivableBranchAppliance](Remove-CsTeamsSurvivableBranchAppliance.md) +### [Remove-CsTeamsSurvivableBranchAppliancePolicy](Remove-CsTeamsSurvivableBranchAppliancePolicy.md) +### [Remove-CsTeamsTargetingPolicy](Remove-CsTeamsTargetingPolicy.md) +### [Remove-CsTeamsTemplatePermissionPolicy](Remove-CsTeamsTemplatePermissionPolicy.md) +### [Remove-CsTeamsTranslationRule](Remove-CsTeamsTranslationRule.md) +### [Remove-CsTeamsUnassignedNumberTreatment](Remove-CsTeamsUnassignedNumberTreatment.md) +### [Remove-CsTeamsUpdateManagementPolicy](Remove-CsTeamsUpdateManagementPolicy.md) +### [Remove-CsTeamsVdiPolicy](Remove-CsTeamsVdiPolicy.md) +### [Remove-CsTeamsVirtualAppointmentsPolicy](Remove-CsTeamsVirtualAppointmentsPolicy.md) +### [Remove-CsTeamsVoiceApplicationsPolicy](Remove-CsTeamsVoiceApplicationsPolicy.md) +### [Remove-CsTeamsWorkLoadPolicy](Remove-CsTeamsWorkLoadPolicy.md) +### [Remove-CsTeamsWorkLocationDetectionPolicy](Remove-CsTeamsWorkLocationDetectionPolicy.md) +### [Remove-CsTeamTemplate](Remove-CsTeamTemplate.md) +### [Remove-CsTenantDialPlan](Remove-CsTenantDialPlan.md) +### [Remove-CsTenantNetworkRegion](Remove-CsTenantNetworkRegion.md) +### [Remove-CsTenantNetworkSite](Remove-CsTenantNetworkSite.md) +### [Remove-CsTenantNetworkSubnet](Remove-CsTenantNetworkSubnet.md) +### [Remove-CsTenantTrustedIPAddress](Remove-CsTenantTrustedIPAddress.md) +### [Remove-CsUserCallingDelegate](Remove-CsUserCallingDelegate.md) +### [Remove-CsVideoInteropServiceProvider](Remove-CsVideoInteropServiceProvider.md) +### [Remove-SharedWithTeam](Remove-SharedWithTeam.md) ### [Remove-Team](Remove-Team.md) -{{Manually Enter Remove-Team Description Here}} - ### [Remove-TeamChannel](Remove-TeamChannel.md) -{{Manually Enter Remove-TeamChannel Description Here}} - ### [Remove-TeamChannelUser](Remove-TeamChannelUser.md) -{{Manually Enter Remove-TeamChannelUser Description Here}} - ### [Remove-TeamsApp](Remove-TeamsApp.md) -{{Manually Enter Remove-TeamsApp Description Here}} - +### [Remove-TeamsAppInstallation](Remove-TeamsAppInstallation.md) +### [Remove-TeamTargetingHierarchy](Remove-TeamTargetingHierarchy.md) ### [Remove-TeamUser](Remove-TeamUser.md) -{{Manually Enter Remove-TeamUser Description Here}} - +### [Set-CsApplicationAccessPolicy](Set-CsApplicationAccessPolicy.md) +### [Set-CsApplicationMeetingConfiguration](Set-CsApplicationMeetingConfiguration.md) +### [Set-CsAutoAttendant](Set-CsAutoAttendant.md) +### [Set-CsCallingLineIdentity](Set-CsCallingLineIdentity.md) +### [Set-CsCallQueue](Set-CsCallQueue.md) +### [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md) +### [Set-CsGroupPolicyAssignment](Set-CsGroupPolicyAssignment.md) +### [Set-CsInboundBlockedNumberPattern](Set-CsInboundBlockedNumberPattern.md) +### [Set-CsInboundExemptNumberPattern](Set-CsInboundExemptNumberPattern.md) +### [Set-CsOnlineApplicationInstance](Set-CsOnlineApplicationInstance.md) +### [Set-CsCsOnlineAudioConferencingRoutingPolicy][Set-CsOnlineAudioConferencingRoutingPolicy.md] +### [Set-CsOnlineDialInConferencingBridge](Set-CsOnlineDialInConferencingBridge.md) +### [Set-CsOnlineDialInConferencingServiceNumber](Set-CsOnlineDialInConferencingServiceNumber.md) +### [Set-CsOnlineDialInConferencingTenantSettings](Set-CsOnlineDialInConferencingTenantSettings.md) +### [Set-CsOnlineDialInConferencingUser](Set-CsOnlineDialInConferencingUser.md) +### [Set-CsOnlineEnhancedEmergencyServiceDisclaimer](Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md) +### [Set-CsOnlineLisCivicAddress](Set-CsOnlineLisCivicAddress.md) +### [Set-CsOnlineLisLocation](Set-CsOnlineLisLocation.md) +### [Set-CsOnlineLisPort](Set-CsOnlineLisPort.md) +### [Set-CsOnlineLisSubnet](Set-CsOnlineLisSubnet.md) +### [Set-CsOnlineLisSwitch](Set-CsOnlineLisSwitch.md) +### [Set-CsOnlineLisWirelessAccessPoint](Set-CsOnlineLisWirelessAccessPoint.md) +### [Set-CsOnlinePSTNGateway](Set-CsOnlinePSTNGateway.md) +### [Set-CsOnlinePstnUsage](Set-CsOnlinePstnUsage.md) +### [Set-CsOnlineSchedule](Set-CsOnlineSchedule.md) +### [Set-CsOnlineVoiceApplicationInstance](Set-CsOnlineVoiceApplicationInstance.md) +### [Set-CsOnlineVoicemailPolicy](Set-CsOnlineVoicemailPolicy.md) +### [Set-CsOnlineVoicemailUserSettings](Set-CsOnlineVoicemailUserSettings.md) +### [Set-CsOnlineVoiceRoute](Set-CsOnlineVoiceRoute.md) +### [Set-CsOnlineVoiceRoutingPolicy](Set-CsOnlineVoiceRoutingPolicy.md) +### [Set-CsOnlineVoiceUser](Set-CsOnlineVoiceUser.md) +### [Set-CsPhoneNumberAssignment](Set-CsPhoneNumberAssignment.md) +### [Set-CsTeamsAcsFederationConfiguration](Set-CsTeamsAcsFederationConfiguration.md) +### [Set-CsTeamsAppPermissionPolicy](Set-CsTeamsAppPermissionPolicy.md) +### [Set-CsTeamsAppSetupPolicy](Set-CsTeamsAppSetupPolicy.md) +### [Set-CsTeamsAudioConferencingPolicy](Set-CsTeamsAudioConferencingPolicy.md) +### [Set-CsTeamsCallHoldPolicy](Set-CsTeamsCallHoldPolicy.md) +### [Set-CsTeamsCallingPolicy](Set-CsTeamsCallingPolicy.md) +### [Set-CsTeamsCallParkPolicy](Set-CsTeamsCallParkPolicy.md) +### [Set-CsTeamsChannelsPolicy](Set-CsTeamsChannelsPolicy.md) +### [Set-CsTeamsClientConfiguration](Set-CsTeamsClientConfiguration.md) +### [Set-CsTeamsComplianceRecordingApplication](Set-CsTeamsComplianceRecordingApplication.md) +### [Set-CsTeamsComplianceRecordingPolicy](Set-CsTeamsComplianceRecordingPolicy.md) +### [Set-CsTeamsCortanaPolicy](Set-CsTeamsCortanaPolicy.md) +### [Set-CsTeamsCustomBannerText](Set-CsTeamsCustomBannerText.md) +### [Set-CsTeamsCustomBannerText](Set-CsTeamsCustomBannerText.md) +### [Set-CsTeamsEducationAssignmentsAppPolicy](Set-CsTeamsEducationAssignmentsAppPolicy.md) +### [Set-CsTeamsEducationConfiguration](Set-CsTeamsEducationConfiguration.md) +### [Set-CsTeamsEmergencyCallingPolicy](Set-CsTeamsEmergencyCallingPolicy.md) +### [Set-CsTeamsEmergencyCallRoutingPolicy](Set-CsTeamsEmergencyCallRoutingPolicy.md) +### [Set-CsTeamsEnhancedEncryptionPolicy](Set-CsTeamsEnhancedEncryptionPolicy.md) +### [Set-CsTeamsEventsPolicy](Set-CsTeamsEventsPolicy.md) +### [Set-CsTeamsFeedbackPolicy](Set-CsTeamsFeedbackPolicy.md) +### [Set-CsTeamsFilesPolicy](Set-CsTeamsFilesPolicy.md) +### [Set-CsTeamsGuestCallingConfiguration](Set-CsTeamsGuestCallingConfiguration.md) +### [Set-CsTeamsGuestMeetingConfiguration](Set-CsTeamsGuestMeetingConfiguration.md) +### [Set-CsTeamsGuestMessagingConfiguration](Set-CsTeamsGuestMessagingConfiguration.md) +### [Set-CsTeamsIPPhonePolicy](Set-CsTeamsIPPhonePolicy.md) +### [Set-CsTeamsMeetingBrandingPolicy](Set-CsTeamsMeetingBrandingPolicy.md) +### [Set-CsTeamsMeetingBroadcastConfiguration](Set-CsTeamsMeetingBroadcastConfiguration.md) +### [Set-CsTeamsMeetingBroadcastPolicy](Set-CsTeamsMeetingBroadcastPolicy.md) +### [Set-CsTeamsMeetingConfiguration](Set-CsTeamsMeetingConfiguration.md) +### [Set-CsTeamsMeetingPolicy](Set-CsTeamsMeetingPolicy.md) +### [Set-CsTeamsMeetingTemplatePermissionPolicy](Set-CsTeamsMeetingTemplatePermissionPolicy.md) +### [Set-CsTeamsMessagingConfiguration](Set-CsTeamsMessagingConfiguration.md) +### [Set-CsTeamsMessagingPolicy](Set-CsTeamsMessagingPolicy.md) +### [Set-CsTeamsMobilityPolicy](Set-CsTeamsMobilityPolicy.md) +### [Set-CsTeamsNetworkRoamingPolicy](Set-CsTeamsNetworkRoamingPolicy.md) +### [Set-CsTeamsPinnedApp](Set-CsTeamsPinnedApp.md) +### [Set-CsTeamsRecordingRollOutPolicy](Set-CsTeamsRecordingRollOutPolicy.md) +### [Set-CsTeamsSharedCallingRoutingPolicy](Set-CsTeamsSharedCallingRoutingPolicy.md) +### [Set-CsTeamsShiftsConnection](Set-CsTeamsShiftsConnection.md) +### [Set-CsTeamsShiftsConnectionInstance](Set-CsTeamsShiftsConnectionInstance.md) +### [Set-CsTeamsShiftsPolicy](Set-CsTeamsShiftsPolicy.md) +### [Set-CsTeamsSipDevicesConfiguration](Set-CsTeamsSipDevicesConfiguration.md) +### [Set-CsTeamsSurvivableBranchAppliance](Set-CsTeamsSurvivableBranchAppliance.md) +### [Set-CsTeamsSurvivableBranchAppliancePolicy](Set-CsTeamsSurvivableBranchAppliancePolicy.md) +### [Set-CsTeamsTargetingPolicy](Set-CsTeamsTargetingPolicy.md) +### [Set-CsTeamsTemplatePermissionPolicy](Set-CsTeamsTemplatePermissionPolicy.md) +### [Set-CsTeamsTranslationRule](Set-CsTeamsTranslationRule.md) +### [Set-CsTeamsUnassignedNumberTreatment](Set-CsTeamsUnassignedNumberTreatment.md) +### [Set-CsTeamsUpdateManagementPolicy](Set-CsTeamsUpdateManagementPolicy.md) +### [Set-CsTeamsUpgradeConfiguration](Set-CsTeamsUpgradeConfiguration.md) +### [Set-CsTeamsVdiPolicy](Set-CsTeamsVdiPolicy.md) +### [Set-CsTeamsVirtualAppointmentsPolicy](Set-CsTeamsVirtualAppointmentsPolicy.md) +### [Set-CsTeamsVoiceApplicationsPolicy](Set-CsTeamsVoiceApplicationsPolicy.md) +### [Set-CsTeamsWorkLoadPolicy](Set-CsTeamsWorkLoadPolicy.md) +### [Set-CsTeamsWorkLocationDetectionPolicy](Set-CsTeamsWorkLocationDetectionPolicy.md) +### [Set-CsTenantBlockedCallingNumbers](Set-CsTenantBlockedCallingNumbers.md) +### [Set-CsTenantDialPlan](Set-CsTenantDialPlan.md) +### [Set-CsTenantFederationConfiguration](Set-CsTenantFederationConfiguration.md) +### [Set-CsTenantMigrationConfiguration](Set-CsTenantMigrationConfiguration.md) +### [Set-CsTenantNetworkRegion](Set-CsTenantNetworkRegion.md) +### [Set-CsTenantNetworkSite](Set-CsTenantNetworkSite.md) +### [Set-CsTenantNetworkSubnet](Set-CsTenantNetworkSubnet.md) +### [Set-CsTenantTrustedIPAddress](Set-CsTenantTrustedIPAddress.md) +### [Set-CsUser](Set-CsUser.md) +### [Set-CsUserCallingDelegate](Set-CsUserCallingDelegate.md) +### [Set-CsUserCallingSettings](Set-CsUserCallingSettings.md) +### [Set-CsVideoInteropServiceProvider](Set-CsVideoInteropServiceProvider.md) ### [Set-Team](Set-Team.md) -{{Manually Enter Set-Team Description Here}} - ### [Set-TeamArchivedState](Set-TeamArchivedState.md) -{{Manually Enter Set-TeamArchivedState Description Here}} - ### [Set-TeamChannel](Set-TeamChannel.md) -{{Manually Enter Set-TeamChannel Description Here}} - ### [Set-TeamFunSettings](Set-TeamFunSettings.md) -{{Manually Enter Set-TeamFunSettings Description Here}} - ### [Set-TeamGuestSettings](Set-TeamGuestSettings.md) -{{Manually Enter Set-TeamGuestSettings Description Here}} - ### [Set-TeamMemberSettings](Set-TeamMemberSettings.md) -{{Manually Enter Set-TeamMemberSettings Description Here}} - ### [Set-TeamMessagingSettings](Set-TeamMessagingSettings.md) -{{Manually Enter Set-TeamMessagingSettings Description Here}} - ### [Set-TeamPicture](Set-TeamPicture.md) -{{Manually Enter Set-TeamPicture Description Here}} - ### [Set-TeamsApp](Set-TeamsApp.md) -{{Manually Enter Set-TeamsApp Description Here}} +### [Set-TeamsEnvironmentConfig](Set-TeamsEnvironmentConfig.md) +### [Set-TeamTargetingHierarchy](Set-TeamTargetingHierarchy.md) +### [Start-CsExMeetingMigration](Start-CsExMeetingMigration.md) +### [Sync-CsOnlineApplicationInstance](Sync-CsOnlineApplicationInstance.md) +### [Test-CsEffectiveTenantDialPlan](Test-CsEffectiveTenantDialPlan.md) +### [Test-CsInboundBlockedNumberPattern](Test-CsInboundBlockedNumberPattern.md) +### [Test-CsTeamsShiftsConnectionValidate](Test-CsTeamsShiftsConnectionValidate.md) +### [Test-CsTeamsTranslationRule](Test-CsTeamsTranslationRule.md) +### [Test-CsTeamsUnassignedNumberTreatment](Test-CsTeamsUnassignedNumberTreatment.md) +### [Test-CsVoiceNormalizationRule](Test-CsVoiceNormalizationRule.md) +### [Unregister-CsOnlineDialInConferencingServiceNumber](Unregister-CsOnlineDialInConferencingServiceNumber.md) +### [Update-CsAutoAttendant](Update-CsAutoAttendant.md) +### [Update-CsCustomPolicyPackage](Update-CsCustomPolicyPackage.md) +### [Update-CsTeamsShiftsConnection](Update-CsTeamsShiftsConnection.md) +### [Update-CsTeamsShiftsConnectionInstance](Update-CsTeamsShiftsConnectionInstance.md) +### [Update-CsTeamTemplate](Update-CsTeamTemplate.md) +### [Update-M365UnifiedCustomPendingApp](Update-M365UnifiedCustomPendingApp.md) +### [Update-TeamsAppInstallation](Update-TeamsAppInstallation.md) diff --git a/tools/office-cmdlet-updater/README.md b/tools/office-cmdlet-updater/README.md index cc69bc1913..d4400fe9f0 100644 --- a/tools/office-cmdlet-updater/README.md +++ b/tools/office-cmdlet-updater/README.md @@ -18,7 +18,7 @@ - SharePoint Online: - https://www.microsoft.com/en-us/download/details.aspx?id=35588 - Exchange Online: - - cmdlets could be imported using [this guide](https://docs.microsoft.com/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell) + - cmdlets could be imported using [this guide](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell) 7. Run the app, type `node index` and press Enter in order to get info for all modules 8. Run the app for a certain module, type `node index -m <TypeModuleNameHere>`, with one of the following options - teams, skype, sharepoint, whiteboard, exchange, staffhub. For example, you should run `node index -m teams` to run the tool for Microsoft Teams 9. Run `node index -help` to get help information for all available commands diff --git a/whiteboard/docfx.json b/whiteboard/docfx.json index a7e705cca0..b5ec7d6eab 100644 --- a/whiteboard/docfx.json +++ b/whiteboard/docfx.json @@ -21,7 +21,8 @@ "dest": "whiteboard/whiteboard-ps" }, { - "files": ["**/*.md"], + "files": ["**/*.yml"], + "exclude": ["toc.yml"], "src": "whiteboard-ps", "version": "whiteboard-ps", "dest": "module" @@ -53,6 +54,7 @@ "overwrite": [], "externalReference": [], "globalMetadata": { + "uhfHeaderId": "MSDocsHeader-M365-IT", "author" : "tbrosman", "ms.author" : "tbrosman", "manager" : "shanejc", @@ -60,9 +62,8 @@ "ms.topic" : "reference", "ms.service" : "whiteboard-powershell", "ms.devlang" : "powershell", - "feedback_system": "GitHub", - "feedback_github_repo": "MicrosoftDocs/office-docs-powershell", - "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" + "feedback_system": "Standard", + "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues" }, "fileMetadata": {}, "template": [], diff --git a/whiteboard/docs-conceptual/index.md b/whiteboard/docs-conceptual/index.md index 3640f19b88..331ec723d3 100644 --- a/whiteboard/docs-conceptual/index.md +++ b/whiteboard/docs-conceptual/index.md @@ -1,5 +1,6 @@ --- title: Microsoft Whiteboard PowerShell +description: "Learn about Microsoft Whiteboard PowerShell." --- # Microsoft Whiteboard PowerShell @@ -8,4 +9,4 @@ Welcome to the Microsoft Whiteboard PowerShell cmdlet help references. The Micro Here you will find all of the Microsoft Whiteboard PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. -The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page. \ No newline at end of file +The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page. diff --git a/whiteboard/docs-conceptual/overview.md b/whiteboard/docs-conceptual/overview.md index bd97d0237f..38782d52de 100644 --- a/whiteboard/docs-conceptual/overview.md +++ b/whiteboard/docs-conceptual/overview.md @@ -1,5 +1,6 @@ --- title: Whiteboard Overview +description: "Whiteboard PowerShell overview." --- # Overview @@ -10,22 +11,44 @@ To install and use the Microsoft Whiteboard cmdlets: 1. Open the start menu and search for Windows PowerShell 2. Right-click on Windows PowerShell and choose Run As Administrator -3. Type or copy this command into the window and press the Enter key: Install-Module -Name WhiteboardAdmin +3. Type or copy this command into the window and press the Enter key: -You may need to update your execution policy, which you can do by typing or copying this command into the window and pressing the Enter key: Set-ExecutionPolicy RemoteSigned +```powershell +Install-Module -Name WhiteboardAdmin +``` -Note: For more information on Execution_Policies, go to https://go.microsoft.com/fwlink/?LinkID=135170 +By default, the PowerShell Gallery (PSGallery) isn't configured as a trusted repository for **PowerShellGet**. The first time you use the PSGallery, you'll see the following message: + +```console +Untrusted repository + +You are installing the modules from an untrusted repository. If you trust this repository, change +its InstallationPolicy value by running the `Set-PSRepository` cmdlet. + +Are you sure you want to install the modules from 'PSGallery'? +[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"): +``` + +Answer **Yes** or **Yes to All** to continue with the installation. + +You may need to update your execution policy, which you can do by typing or copying this command into the window and pressing the Enter key: + +```powershell +Set-ExecutionPolicy RemoteSigned +``` + +Note: For more information on Execution_Policies, go to <https://go.microsoft.com/fwlink/p/?LinkID=135170>. ## User IDs -Cmdlets taking user IDs use the ID from Azure Active Directory. To get a user ID, you can use the Microsoft Graph Explorer. For more information, go to https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/api/user_get +Cmdlets taking user IDs use the ID from Microsoft Entra ID. To get a user ID, you can use the Microsoft Graph Explorer. For more information, go to </graph/api/user-get>. ## Exporting Whiteboard Content -The Microsoft Whiteboard cmdlets are often used to facilate the export of Whiteboard content for users that no longer have access to whiteboard. To accomplish this you must first transfer the whiteboard owner to someone who has access to Whiteboard. Then the user who now owns the whiteboard can sign into the app and export the content. +The Microsoft Whiteboard cmdlets are often used to facilitate the export of Whiteboard content for users that no longer have access to whiteboard. To accomplish this you must first transfer the whiteboard owner to someone who has access to Whiteboard. Then the user who now owns the whiteboard can sign into the app and export the content. ## Common Cmdlets -* [Get-Whiteboard](../whiteboard-ps/whiteboard/Get-Whiteboard.md) -* [Set-WhiteboardOwner](../whiteboard-ps/whiteboard/Set-WhiteboardOwner.md) -* [Invoke-TransferAllWhiteboard](../whiteboard-ps/whiteboard/Invoke-TransferAllWhiteboards.md) \ No newline at end of file +* @MicrosoftWhiteboardAdmin.Get-Whiteboard +* @MicrosoftWhiteboardAdmin.Set-WhiteboardOwner +* @MicrosoftWhiteboardAdmin.Invoke-TransferAllWhiteboards diff --git a/whiteboard/mapping/monikerMapping.json b/whiteboard/mapping/MAML2Yaml/monikerMapping.json similarity index 100% rename from whiteboard/mapping/monikerMapping.json rename to whiteboard/mapping/MAML2Yaml/monikerMapping.json diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-OriginalFluidWhiteboards.md b/whiteboard/whiteboard-ps/whiteboard/Get-OriginalFluidWhiteboards.md new file mode 100644 index 0000000000..1b2ef53c77 --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Get-OriginalFluidWhiteboards.md @@ -0,0 +1,111 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-originalfluidwhiteboards +applicable: Microsoft Whiteboard +title: Get-OriginalFluidWhiteboards +schema: 2.0.0 +author: shwetawagh +ms.author: shwetawagh +ms.reviewer: +--- + +# Get-OriginalFluidWhiteboards + +## SYNOPSIS + +Gets one or more whiteboards that are originally created as Fluid whiteboards, directly into users OneDrive and return them as objects. + +## SYNTAX + +```powershell +Get-OriginalFluidWhiteboards [-UserId] [-ForceAuthPrompt] [<CommonParameters>] +``` + +## DESCRIPTION + +Gets one or more whiteboards that are originally created as Fluid whiteboards, directly into users OneDrive. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\>Get-OriginalFluidWhiteboards -UserId 00000000-0000-0000-0000-000000000001 +``` + +Get all user's whiteboards that are originally created as Fluid whiteboards directly into users OneDrive. + +### Output + +```yaml +Drive Items found for User 00000000-0000-0000-0000-000000000001 --------------------------------------------------- +Name: TradeTestwhiteboard.whiteboard +ID: 01ZSJH4Y3TXKT7TKCRRZG3LFKTEGDGSKW4 +Last Modified: 03/06/2025 09:59:32 +Size: 15222 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: 00000000-0000-0000-0000-000000000001 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +Name: Test11whiteboard-Copy.whiteboard +ID: 01ZSJH4YZFODVVZ6LTNNC35BT4QON7GTJI +Last Modified: 03/06/2025 09:59:25 +Size: 15225 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: 00000000-0000-0000-0000-000000000001 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +``` + +## PARAMETERS + +### -UserId + +The ID of the user account to query whiteboards for. Admin should have access to user OneDrive to get that user whiteboards. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +Optional. Always prompt for auth. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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) + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-OriginalFluidWhiteboardsForTenant.md b/whiteboard/whiteboard-ps/whiteboard/Get-OriginalFluidWhiteboardsForTenant.md new file mode 100644 index 0000000000..e6779e12ce --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Get-OriginalFluidWhiteboardsForTenant.md @@ -0,0 +1,178 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-originalfluidwhiteboardsfortenant +applicable: Microsoft Whiteboard +title: Get-OriginalFluidWhiteboardsForTenant +schema: 2.0.0 +author: shwetawagh +ms.author: shwetawagh +ms.reviewer: +--- + +# Get-OriginalFluidWhiteboardsForTenant + +## SYNOPSIS + +Gets one or more whiteboards that are originally created as fluid directly into OneDrive for all users under that admin and returns them as objects. + +## SYNTAX + +```powershell +Get-OriginalFluidWhiteboardsForTenant [-IncrementalRunName <String>] [-ForceAuthPrompt] [<CommonParameters>] +``` + +## DESCRIPTION + +Gets one or more whiteboards that are originally created as fluid directly into OneDrive and returns them as objects. It output all boards created directly into OneDrive in all user accounts under that Tenant + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\>Get-OriginalFluidWhiteboardsForTenant +``` + +Get all user's originally created fluid whiteboards in that tenant and outputs in cmd with all users whiteboards provided admin has access to all those users oneDrive for which it is intended to get whiteboards. + +### Output + +```yaml +Drive Items found for User e2ff85af-37e6-4ed7-893b-7ea10c380dc4 --------------------------------------------------- +Name: Test11whiteboard.whiteboard +ID: 01ZSJH4Y3TXKT7TKCRRZG3LFKTEGDGSKW4 +Last Modified: 03/06/2025 09:59:32 +Size: 15222 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +Name: Test11whiteboard-Copy.whiteboard +ID: 01ZSJH4YZFODVVZ6LTNNC35BT4QON7GTJI +Last Modified: 03/06/2025 09:59:25 +Size: 15225 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +Drive Items found for User 98f9e197-f331-4cca-b7b7-0c0307452fdd --------------------------------------------------- +Name: Azure111 whiteboard 1.whiteboard +ID: 01BYRZZIGVVILTKNPTFFFL2M5WFSTDVMSZ +Last Modified: 02/13/2025 16:45:58 +Size: 23110 bytes +Migration Date: 02/13/2025 16:45:37 +User ID: 98f9e197-f331-4cca-b7b7-0c0307452fdd +User Email: admin@M365x86764163.onmicrosoft.com +User Name: MOD Administrator +-------------------------------------- +Name: Azure111 whiteboard.whiteboard +ID: 01BYRZZIBSVZZUYVJ2JZAKUOV5FMPHM2NL +Last Modified: 02/19/2025 07:35:25 +Size: 12007 bytes +Migration Date: 02/19/2025 07:35:24 +User ID: 98f9e197-f331-4cca-b7b7-0c0307452fdd +User Email: admin@M365x86764163.onmicrosoft.com +User Name: MOD Administrator +-------------------------------------- +No drive items found for User cc078d4f-5ba1-48ff-847f-0f4af2ee8cf5 with DriveID b!Upfgzjfpx0e4lqL84H-BRZGV7qFNQ-hCobqXYyyCS1clCfsBBCS5T75ca0pe4UQS +Admin does not have access to User 4f14ba28-e678-4535-a9ea-c9f3b32c46f0 OneDrive. +``` + +### EXAMPLE 2 + +```powershell +PS C:\>Get-OriginalFluidWhiteboardsForTenant -IncrementalRunName 1 +``` + +Get all user's originally created fluid whiteboards in that tenant and incrementally creates file "WhiteboardsOriginalFluid-$IncrementalRunName.txt" with all users whiteboards provided admin has access to all those users oneDrive for which it is intended to get whiteboards. + +### Output + +```yaml +[ + "Name: Test11whiteboard.whiteboard", + "ID: 01ZSJH4Y3TXKT7TKCRRZG3LFKTEGDGSKW4", + "Last Modified: 03/06/2025 09:59:32", + "Size: 15222 bytes", + "Migration Date: 03/06/2025 09:58:57", + "User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4", + "User Email: AdeleV@M365x86764163.OnMicrosoft.com", + "User Name: Adele Vance", + "-----------------------------------------------", + "Name: Untitled.whiteboard", + "ID: 01ZSJH4YYNHPBYXNRAIFAY42SHQ365Z32M", + "Last Modified: 02/19/2025 05:19:04", + "Size: 15307 bytes", + "Migration Date: 02/19/2025 05:19:04", + "User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4", + "User Email: AdeleV@M365x86764163.OnMicrosoft.com", + "User Name: Adele Vance", + "-----------------------------------------------" +] +[ + "Name: Azure111 whiteboard.whiteboard", + "ID: 01BYRZZIBSVZZUYVJ2JZAKUOV5FMPHM2NL", + "Last Modified: 02/19/2025 07:35:25", + "Size: 12007 bytes", + "Migration Date: 02/19/2025 07:35:24", + "User ID: 98f9e197-f331-4cca-b7b7-0c0307452fdd", + "User Email: admin@M365x86764163.onmicrosoft.com", + "User Name: MOD Administrator", + "-----------------------------------------------" +] +``` + +## PARAMETERS + +### -IncrementalRunName + +Saves incremental progress as the cmdlet runs. Writes progress and results to `.txt` files in the current directory: + +- `WhiteboardsOriginalFluid-*.txt` contains the incremental results containing whiteboard objects for the tenant where `*` is the provided **IncrementalRunName**. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +Optional. Always prompt for auth. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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) + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-Whiteboard.md b/whiteboard/whiteboard-ps/whiteboard/Get-Whiteboard.md index 39a629f086..a533b03ca5 100644 --- a/whiteboard/whiteboard-ps/whiteboard/Get-Whiteboard.md +++ b/whiteboard/whiteboard-ps/whiteboard/Get-Whiteboard.md @@ -1,12 +1,12 @@ --- -external help file: Microsoft.Whiteboard.PowerShell.Custom.dll-Help.xml -Module Name: MicrosoftWhiteboard -online version: https://docs.microsoft.com/powershell/module/whiteboard/get-whiteboard +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-whiteboard applicable: Microsoft Whiteboard title: Get-Whiteboard schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -14,63 +14,91 @@ ms.reviewer: ## SYNOPSIS -Gets one or more Whiteboards from the Microsoft Whiteboard service and returns them as objects. +Gets one or more whiteboards in Azure from the Microsoft Whiteboard service and returns them as objects. ## SYNTAX -### Get a specific Whiteboard - -```powershell -Get-Whiteboard -UserId <Guid> -WhiteboardId <Guid> [<CommonParameters>] -``` - -### Get all Whiteboards for a user - ```powershell -Get-Whiteboard -UserId <Guid> [<CommonParameters>] +Get-Whiteboard [-UserId] <Guid> [[-WhiteboardId] <Guid>] [-ForceAuthPrompt] [<CommonParameters>] ``` ## DESCRIPTION -Gets one or more Whiteboards from the Microsoft Whiteboard service and returns them as objects. +Gets one or more whiteboards in Azure from the Microsoft Whiteboard service and returns them as objects. ## EXAMPLES -### -------------------------- EXAMPLE 1 -------------------------- +### EXAMPLE 1 -``` +```powershell PS C:\>Get-Whiteboard -UserId 00000000-0000-0000-0000-000000000001 ``` -Get all of a user's Whiteboards. +Get all of a user's whiteboards. + +### EXAMPLE 2 + +```powershell +PS C:\>Get-Whiteboard -UserId 00000000-0000-0000-0000-000000000001 -WhiteboardId 00000000-0000-0000-0000-000000000002 +``` + +Get a user's specific whiteboard. + +### Output +```yaml +baseApi: baseApi-value +id: whiteboardId-value +userId: userId-value +folioId: folioId-value +title: title-value +createdBy: createdBy-value +ownerId: ownerId-value +ownerTenantId: ownerTenantId-value +isShared: isShared-value +createdTime: createdTime-value +invitedTime: invitedTime-value +personalLastModifiedTime: personalLastModifiedTime-value +lastModifiedTime: lastModifiedTime-value +globalLastViewedTime: globalLastViewedTime-value +lastViewedTime: lastViewedTime-value +meetingId: meetingId-value +eTag: eTag-value +``` ## PARAMETERS ### -UserId -Optional. The ID of the user account to query Whiteboards for. All Whiteboards this account has access to will be returned. + +The ID of the user account to query whiteboards for. All whiteboards this account has access to will be returned. ```yaml -Type: Guid -Required: true -Position: named -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` ### -WhiteboardId -Optional. The ID of a specific Whiteboard. +Optional. The ID of a specific whiteboard. ```yaml -Type: Guid -Required: true -Position: named -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` @@ -79,25 +107,28 @@ Applicable: Microsoft Whiteboard Optional. Always prompt for auth. Use to ignore cached credentials. ```yaml -Type: SwitchParameter -Required: false -Position: named -Default value: false -Accept pipeline input: false -Accept wildcard characters: false +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` -## INPUTS +### CommonParameters -### None +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) -## OUTPUTS +## INPUTS -### System.Object +## OUTPUTS ## NOTES -For details on user IDs, see the [overview page](whiteboard.md). +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). ## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardOwners.md b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardOwners.md new file mode 100644 index 0000000000..1f5bb1aa2a --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardOwners.md @@ -0,0 +1,113 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-whiteboardowners +applicable: Microsoft Whiteboard +title: Get-WhiteboardOwners +schema: 2.0.0 +author: shlevari +ms.author: shlevari +ms.reviewer: +--- + +# Get-WhiteboardOwners + +## SYNOPSIS + +Gets all the users in a tenant who own whiteboards in a specified geography. + +## SYNTAX + +```powershell +Get-WhiteboardOwners [-Geography] <String> [[-ContinuationToken] <String>] [-ForceAuthPrompt] [<CommonParameters>] +``` + +## DESCRIPTION + +Gets all the users in a tenant who own whiteboards in a specified geography. Returns them as an object containing a list of user object, a tenantId and a continuation token. By calling repeatedly passing in the new continuation tokens, all the owners for a tenant can be gathered. The data returned is precalculated and therefore not realtime. Results are precalculated approximately every two weeks. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\>Get-WhiteboardOwners -Geography Europe +``` + +Get the owners in the European geography. + +### Output + +```yaml +TenantId: tenantId +Geography: The geography queried for +Items: List of user ids +ContinuationToken: continuation token +``` + +## PARAMETERS + +### -Geography + +Required. The geography to look for board owners in. Accepted values are: Europe, Australia, or Worldwide (all boards not in australia or europe). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ContinuationToken + +Optional. The continuation token returned in a previous call. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +Optional. Always prompt for auth. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardSettings.md b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardSettings.md new file mode 100644 index 0000000000..ca58a28bde --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardSettings.md @@ -0,0 +1,87 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-whiteboardsettings +applicable: Microsoft Whiteboard +title: Get-WhiteboardSettings +schema: 2.0.0 +author: shwetawagh +ms.author: shwetawagh +ms.reviewer: +--- + +# Get-WhiteboardSettings + +## SYNOPSIS + +Get the users Whiteboard settings. + +## SYNTAX + +```powershell +Get-WhiteboardSettings + [-ForceAuthPrompt] + [<CommonParameters>] +``` + +## DESCRIPTION + +Gets tenant settings from the Microsoft Whiteboard service and returns them as an object. + +## EXAMPLES + +### EXAMPLE 1 + +This command gets tenant settings from the Microsoft Whiteboard service and returns them as an object. + +```powershell +PS C:\> Get-WhiteboardSettings +``` + +```Output +isClaimEnabled : True +privacySettings : @{telemetryDataPolicy=Optional; isEnabledConnectedServices=True} +tenantMetadata : @{isGovUser=False; isEduUser=False} +isSharePointDefault : False +isSharePointDefaultGa : True +isSharePointDefaultRolledOut : True +isAzureBlocked : False +licenseCheckInformation : Success +isFluidMigrationEnabled : False +isTenantAdminMigrationEnabled : True +isEnabled : True +isEnabledGa : True +``` + +## PARAMETERS + +### -ForceAuthPrompt + +Always prompt for authentication. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsForTenant.md b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsForTenant.md new file mode 100644 index 0000000000..531dc66db0 --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsForTenant.md @@ -0,0 +1,148 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-whiteboardsfortenant +applicable: Microsoft Whiteboard +title: Get-WhiteboardsForTenant +schema: 2.0.0 +author: samanehrajabi +ms.author: srajabi +ms.reviewer: +--- + +# Get-WhiteboardsForTenant + +## SYNOPSIS + +Gets all the whiteboards in Azure associated with a tenant in a specified geography. + +## SYNTAX + +```powershell +Get-WhiteboardsForTenant [-Geography <String>] + [-IncrementalRunName <String>] + [-ForceAuthPrompt] + [<CommonParameters>] +``` + +## DESCRIPTION + +Gets all the whiteboards in Azure in a tenant in a specified geography. Returns a list of whiteboard objects. The data is pre-calculated approximately every two weeks and is not realtime. + +## EXAMPLES + +### EXAMPLE 1 + +This command gets all the whiteboards in Azure associated with the caller's tenant in Europe as a list of whiteboard metadata objects. + +```powershell +PS C:\> Get-WhiteboardsForTenant -Geography Europe +``` + +```Output +baseApi : eu.whiteboard.microsoft.com +id : 00000000-0000-0000-0000-000000000001 +userId : 00000000-0000-0000-0000-000000000000 +folioId : 00000000-0000-0000-0000-000000000000 +title : title1 +createdBy : 00000000-0000-0000-0000-000000000000 +ownerId : 00000000-0000-0000-0000-000000000000 +ownerTenantId : 00000000-0000-0000-0000-000000000000 +isShared : False +createdTime : 2022-09-10T19:59:03.3407011Z +invitedTime : +personalLastModifiedTime : 2022-09-11T15:53:32.4494737Z +lastModifiedTime : 2022-09-11T15:53:32.4494737Z +globalLastViewedTime : 2022-09-11T15:55:28.7242817Z +lastViewedTime : 2022-09-11T15:55:28.7242817Z +meetingId : +eTag : W/"datetime'2022-09-11T19%3A23%3A56.2845616Z'" + +baseApi : eu.whiteboard.microsoft.com +id : 00000000-0000-0000-0000-000000000002 +userId : 00000000-0000-0000-0000-000000000000 +folioId : 00000000-0000-0000-0000-000000000000 +title : title2 +createdBy : 00000000-0000-0000-0000-000000000000 +ownerId : 00000000-0000-0000-0000-000000000000 +ownerTenantId : 00000000-0000-0000-0000-000000000000 +isShared : False +createdTime : 2023-01-06T19:23:04.8807147Z +invitedTime : +personalLastModifiedTime : 2023-01-06T19:23:13.6235107Z +lastModifiedTime : 2023-01-06T19:23:13.6235107Z +globalLastViewedTime : 2023-01-06T19:23:56.0264268Z +lastViewedTime : 2023-01-06T19:23:56.0264268Z +meetingId : +eTag : W/"datetime'2023-01-06T19%3A22%3A42.6717851Z'" +``` + +## PARAMETERS + +### -Geography + +The geography to look for board owners in. Accepted values are `Europe`, `Australia`, or `Worldwide` (all boards not in Australia or Europe). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -IncrementalRunName + +Saves incremental progress as the cmdlet runs. Use to resume a partially completed run. Use the same **IncrementalRunName** value on later calls to continue a previously canceled or failed run. Writes progress and results to `.txt` files in the current directory: + +- `Whiteboards-*.txt` contains the incremental results containing whiteboard objects for the tenant where `*` is the provided **IncrementalRunName**. +- `WhiteboardAdminRun-*.txt` contains the current state where `*` is the provided **IncrementalRunName**. This file should not be modified manually. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +Always prompt for authentication. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsForTenantMigrated.md b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsForTenantMigrated.md new file mode 100644 index 0000000000..c29105b13b --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsForTenantMigrated.md @@ -0,0 +1,178 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-whiteboardsfortenantmigrated +applicable: Microsoft Whiteboard +title: Get-WhiteboardsForTenantMigrated +schema: 2.0.0 +author: shwetawagh +ms.author: shwetawagh +ms.reviewer: +--- + +# Get-WhiteboardsForTenantMigrated + +## SYNOPSIS + +Gets one or more whiteboards that are migrated to OneDrive and returns them as objects. + +## SYNTAX + +```powershell +Get-WhiteboardsForTenantMigrated [-IncrementalRunName <String>] [-ForceAuthPrompt] [<CommonParameters>] +``` + +## DESCRIPTION + +Gets one or more whiteboards that are migrated to OneDrive and returns them as objects. It output all boards migrated to OneDrive in all user accounts under that Tenant provided Admin have access to all those users OneDrive. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\>Get-WhiteboardsForTenantMigrated +``` + +Get all user's migrated whiteboards in that tenant and outputs in cmd with all users whiteboards provided admin has access to all those users oneDrive. + +### Output + +```yaml +Drive Items found for User e2ff85af-37e6-4ed7-893b-7ea10c380dc4 --------------------------------------------------- +Name: Test11whiteboard.whiteboard +ID: 01ZSJH4Y3TXKT7TKCRRZG3LFKTEGDGSKW4 +Last Modified: 03/06/2025 09:59:32 +Size: 15222 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +Name: Test11whiteboard-Copy.whiteboard +ID: 01ZSJH4YZFODVVZ6LTNNC35BT4QON7GTJI +Last Modified: 03/06/2025 09:59:25 +Size: 15225 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +Drive Items found for User 98f9e197-f331-4cca-b7b7-0c0307452fdd --------------------------------------------------- +Name: Azure111 whiteboard 1.whiteboard +ID: 01BYRZZIGVVILTKNPTFFFL2M5WFSTDVMSZ +Last Modified: 02/13/2025 16:45:58 +Size: 23110 bytes +Migration Date: 02/13/2025 16:45:37 +User ID: 98f9e197-f331-4cca-b7b7-0c0307452fdd +User Email: admin@M365x86764163.onmicrosoft.com +User Name: MOD Administrator +-------------------------------------- +Name: Azure111 whiteboard.whiteboard +ID: 01BYRZZIBSVZZUYVJ2JZAKUOV5FMPHM2NL +Last Modified: 02/19/2025 07:35:25 +Size: 12007 bytes +Migration Date: 02/19/2025 07:35:24 +User ID: 98f9e197-f331-4cca-b7b7-0c0307452fdd +User Email: admin@M365x86764163.onmicrosoft.com +User Name: MOD Administrator +-------------------------------------- +No drive items found for User cc078d4f-5ba1-48ff-847f-0f4af2ee8cf5 with DriveID b!Upfgzjfpx0e4lqL84H-BRZGV7qFNQ-hCobqXYyyCS1clCfsBBCS5T75ca0pe4UQS +Admin does not have access to User 4f14ba28-e678-4535-a9ea-c9f3b32c46f0 OneDrive. +``` + +### EXAMPLE 2 + +```powershell +PS C:\>Get-WhiteboardsForTenantMigrated -IncrementalRunName 1 +``` + +Get all user's migrated whiteboards in that tenant and incrementally creates file "WhiteboardsMigrated-$IncrementalRunName.txt" with all users whiteboards provided admin has access to all those users oneDrive. + +### Output + +```yaml +[ + "Name: Test11whiteboard.whiteboard", + "ID: 01ZSJH4Y3TXKT7TKCRRZG3LFKTEGDGSKW4", + "Last Modified: 03/06/2025 09:59:32", + "Size: 15222 bytes", + "Migration Date: 03/06/2025 09:58:57", + "User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4", + "User Email: AdeleV@M365x86764163.OnMicrosoft.com", + "User Name: Adele Vance", + "-----------------------------------------------", + "Name: Untitled.whiteboard", + "ID: 01ZSJH4YYNHPBYXNRAIFAY42SHQ365Z32M", + "Last Modified: 02/19/2025 05:19:04", + "Size: 15307 bytes", + "Migration Date: 02/19/2025 05:19:04", + "User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4", + "User Email: AdeleV@M365x86764163.OnMicrosoft.com", + "User Name: Adele Vance", + "-----------------------------------------------" +] +[ + "Name: Azure111 whiteboard.whiteboard", + "ID: 01BYRZZIBSVZZUYVJ2JZAKUOV5FMPHM2NL", + "Last Modified: 02/19/2025 07:35:25", + "Size: 12007 bytes", + "Migration Date: 02/19/2025 07:35:24", + "User ID: 98f9e197-f331-4cca-b7b7-0c0307452fdd", + "User Email: admin@M365x86764163.onmicrosoft.com", + "User Name: MOD Administrator", + "-----------------------------------------------" +] +``` + +## PARAMETERS + +### -IncrementalRunName + +Saves incremental progress as the cmdlet runs. Writes progress and results to `.txt` files in the current directory: + +- `WhiteboardsMigrated-*.txt` contains the incremental results containing whiteboard objects for the tenant where `*` is the provided **IncrementalRunName**. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +Optional. Always prompt for auth. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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) + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsMigrated.md b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsMigrated.md new file mode 100644 index 0000000000..6bff3167e4 --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Get-WhiteboardsMigrated.md @@ -0,0 +1,111 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/get-whiteboardsmigrated +applicable: Microsoft Whiteboard +title: Get-WhiteboardsMigrated +schema: 2.0.0 +author: shwetawagh +ms.author: shwetawagh +ms.reviewer: +--- + +# Get-WhiteboardsMigrated + +## SYNOPSIS + +Gets one or more whiteboards that are migrated to OneDrive and returns them as objects. + +## SYNTAX + +```powershell +Get-WhiteboardsMigrated [-UserId] [-ForceAuthPrompt] [<CommonParameters>] +``` + +## DESCRIPTION + +Gets one or more whiteboards that are migrated to OneDrive for particular user and returns them as objects provided Admin have access to that user OneDrive. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +PS C:\>Get-WhiteboardsMigrated -UserId e2ff85af-37e6-4ed7-893b-7ea10c380dc4 +``` + +Get all user's migrated whiteboards. + +### Output + +```yaml +Drive Items found for User e2ff85af-37e6-4ed7-893b-7ea10c380dc4 --------------------------------------------------- +Name: Test11whiteboard.whiteboard +ID: 01ZSJH4Y3TXKT7TKCRRZG3LFKTEGDGSKW4 +Last Modified: 03/06/2025 09:59:32 +Size: 15222 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +Name: Test11whiteboard-Copy.whiteboard +ID: 01ZSJH4YZFODVVZ6LTNNC35BT4QON7GTJI +Last Modified: 03/06/2025 09:59:25 +Size: 15225 bytes +Migration Date: 03/06/2025 09:58:57 +User ID: e2ff85af-37e6-4ed7-893b-7ea10c380dc4 +User Email: AdeleV@M365x86764163.OnMicrosoft.com +User Name: Adele Vance +-------------------------------------- +``` + +## PARAMETERS + +### -UserId + +The ID of the user account to query whiteboards for. Admin should have access to user OneDrive to get that users whiteboards. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +Optional. Always prompt for auth. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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) + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Invoke-TransferAllWhiteboards.md b/whiteboard/whiteboard-ps/whiteboard/Invoke-TransferAllWhiteboards.md index 0546738693..a770d4b062 100644 --- a/whiteboard/whiteboard-ps/whiteboard/Invoke-TransferAllWhiteboards.md +++ b/whiteboard/whiteboard-ps/whiteboard/Invoke-TransferAllWhiteboards.md @@ -1,12 +1,12 @@ --- -external help file: Microsoft.Whiteboard.PowerShell.Custom.dll-Help.xml -Module Name: MicrosoftWhiteboard -online version: https://docs.microsoft.com/powershell/module/whiteboard/invoke-transferallwhiteboards +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/invoke-transferallwhiteboards applicable: Microsoft Whiteboard -title: Set-WhiteboardOwner +title: Invoke-TransferAllWhiteboards schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -14,37 +14,36 @@ ms.reviewer: ## SYNOPSIS -Transfer ownership of all Whiteboards owned by a user to another user. +Transfer ownership of all whiteboards owned by a user to another user. ## SYNTAX ```powershell -Invoke-TransferAllWhiteboards [-OwnerId] <Guid> [-NewOwnerId] <Guid> [-WhatIf] [-Confirm] [<CommonParameters>] +Invoke-TransferAllWhiteboards [-OldOwnerId] <Guid> [-NewOwnerId] <Guid> [-ForceAuthPrompt] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION -Transfer ownership of all Whiteboards owned by a user to another user. +Transfer ownership of all whiteboards owned by a user to another user. ## EXAMPLES -### -------------------------- EXAMPLE 1 -------------------------- +### EXAMPLE 1 -``` +```powershell PS C:\>Invoke-TransferAllWhiteboards -OldOwnerId 00000000-0000-0000-0000-000000000001 -NewOwnerId 00000000-0000-0000-0000-000000000002 -WhatIf ``` -Check how many Whiteboards will be transferred without transferring them. +Check how many whiteboards will be transferred without transferring them. -### -------------------------- EXAMPLE 2 -------------------------- +### EXAMPLE 2 -``` +```powershell PS C:\>Invoke-TransferAllWhiteboards -OldOwnerId 00000000-0000-0000-0000-000000000001 -NewOwnerId 00000000-0000-0000-0000-000000000002 ``` Transfer (and prompt before performing any write actions). - ## PARAMETERS ### -OldOwnerId @@ -52,12 +51,15 @@ Transfer (and prompt before performing any write actions). The ID of the previous owner. ```yaml -Type: Guid -Required: true -Position: 3 -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` @@ -66,12 +68,15 @@ Applicable: Microsoft Whiteboard The ID of the new owner. ```yaml -Type: Guid -Required: true -Position: 4 -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` @@ -80,49 +85,62 @@ Applicable: Microsoft Whiteboard Optional. Always prompt for auth. Use to ignore cached credentials. ```yaml -Type: SwitchParameter -Required: false -Position: named -Default value: false -Accept pipeline input: false -Accept wildcard characters: false +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` ### -WhatIf +Execute the command without making any actual changes. Only calls read methods on the REST service. + ```yaml -Type: SwitchParameter -Required: false -Position: named -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` -### -Confirm [<SwitchParameter>] +### -Confirm + +Prompts you for confirmation before running the cmdlet. ```yaml -Type: SwitchParameter -Required: false -Position: named -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` -## INPUTS +### CommonParameters -### None +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). -## OUTPUTS +## INPUTS -### System.Object +## OUTPUTS ## NOTES -For details on user IDs, see the [overview page](whiteboard.md). +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). ## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Remove-Whiteboard.md b/whiteboard/whiteboard-ps/whiteboard/Remove-Whiteboard.md new file mode 100644 index 0000000000..69a0893606 --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Remove-Whiteboard.md @@ -0,0 +1,102 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/remove-whiteboard +applicable: Microsoft Whiteboard +title: Remove-Whiteboard +schema: 2.0.0 +author: serdarsoysal +ms.author: serdars +ms.reviewer: +--- + +# Remove-Whiteboard + +## SYNOPSIS + +Deletes the specified whiteboard for the given user from the Microsoft Whiteboard service. If the user is the owner of the whiteboard, the entire whiteboard will be deleted. If the user has joined the whiteboard but does not own it, they will be removed and the whiteboard will still be accessible by others. + +## SYNTAX + +```powershell +Remove-Whiteboard [-UserId] <Guid> [-WhiteboardId] <Guid> [-ForceAuthPrompt] [<CommonParameters>] +``` + +## DESCRIPTION + +Removes the specified whiteboard (owner) or a joined user removes themselves from the specified whiteboard. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +Remove-Whiteboard -UserId 00000000-0000-0000-0000-000000000001 -WhiteboardId 00000000-0000-0000-0000-000000000002 +``` + +Deletes the whiteboard. + +## PARAMETERS + +### -UserId + +The ID of the user account to delete the whiteboard from. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -WhiteboardId + +The ID of a specific whiteboard to delete. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +(Optional) Always prompt for auth. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Restore-Whiteboard.md b/whiteboard/whiteboard-ps/whiteboard/Restore-Whiteboard.md new file mode 100644 index 0000000000..5ceb33569e --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Restore-Whiteboard.md @@ -0,0 +1,86 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/restore-whiteboard +applicable: Microsoft Whiteboard +title: Restore-Whiteboard +schema: 2.0.0 +author: shwetawagh +ms.author: shwetawagh +ms.reviewer: +--- + +# Restore-Whiteboard + +## SYNOPSIS + +Restores the specified Whiteboard by removing the mapping to the board migrated to ODB. This will not delete the ODB board. + +## SYNTAX + +```powershell +Restore-Whiteboard [-WhiteboardId] <Guid> [-ForceAuthPrompt] [<CommonParameters>] +``` + +## DESCRIPTION + +Restores the azure board. The migrated onedrive board will be retained to not lose any updates done to Azure board. +Restoration is only possible for approximately 90 days after migration, when the original board is still available. + +## EXAMPLES + +### EXAMPLE 1 + +```powershell +Restore-Whiteboard -WhiteboardId 00000000-0000-0000-0000-000000000002 +``` + +Restore the whiteboard. + +## PARAMETERS + +### -WhiteboardId + +The ID of a specific whiteboard to restore. + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -ForceAuthPrompt + +(Optional) Always prompt for auth. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Set-WhiteboardOwner.md b/whiteboard/whiteboard-ps/whiteboard/Set-WhiteboardOwner.md index fbb32587ed..3b05afdd46 100644 --- a/whiteboard/whiteboard-ps/whiteboard/Set-WhiteboardOwner.md +++ b/whiteboard/whiteboard-ps/whiteboard/Set-WhiteboardOwner.md @@ -1,12 +1,12 @@ --- -external help file: Microsoft.Whiteboard.PowerShell.Custom.dll-Help.xml -Module Name: MicrosoftWhiteboard -online version: https://docs.microsoft.com/powershell/module/whiteboard/set-whiteboardowner +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/set-whiteboardowner applicable: Microsoft Whiteboard title: Set-WhiteboardOwner schema: 2.0.0 -author: kenwith -ms.author: kenwith +author: serdarsoysal +ms.author: serdars ms.reviewer: --- @@ -14,41 +14,44 @@ ms.reviewer: ## SYNOPSIS -Sets the owner for a Whiteboard. +Sets the owner for a whiteboard. ## SYNTAX ```powershell -Set-WhiteboardOwner [-WhiteboardId] <Guid> [-OldOwnerId] <Guid> [-NewOwnerId] <Guid> [-WhatIf] [-Confirm] [<CommonParameters>] +Set-WhiteboardOwner [-WhiteboardId] <Guid> [-OldOwnerId] <Guid> [-NewOwnerId] <Guid> [-ForceAuthPrompt] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION -Sets the owner for a Whiteboard. +Sets the owner for a whiteboard. ## EXAMPLES -### -------------------------- EXAMPLE 1 -------------------------- +### EXAMPLE 1 -``` -PS C:\>Set-WhiteboardOwner -OldOwnerId 00000000-0000-0000-0000-000000000001 -NewOwnerId 00000000-0000-0000-0000-000000000002 +```powershell +PS C:\>Set-WhiteboardOwner -OldOwnerId 00000000-0000-0000-0000-000000000001 -NewOwnerId 00000000-0000-0000-0000-000000000002 -WhiteboardId 00000000-0000-0000-0000-000000000003 ``` -Move a Whiteboard from one user to another. +Move whiteboard ownership from one user to another. ## PARAMETERS ### -WhiteboardId -The Whiteboard for which the owner is being changed. +The whiteboard for which the owner is being changed. ```yaml -Type: Guid -Required: true -Position: 2 -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` @@ -57,12 +60,15 @@ Applicable: Microsoft Whiteboard The ID of the previous owner. ```yaml -Type: Guid -Required: true -Position: 3 -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 2 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` @@ -71,12 +77,15 @@ Applicable: Microsoft Whiteboard The ID of the new owner. ```yaml -Type: Guid -Required: true -Position: 4 -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: True +Position: 3 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` @@ -85,49 +94,62 @@ Applicable: Microsoft Whiteboard Optional. Always prompt for auth. Use to ignore cached credentials. ```yaml -Type: SwitchParameter -Required: false -Position: named -Default value: false -Accept pipeline input: false -Accept wildcard characters: false +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` ### -WhatIf +Shows what would happen if the cmdlet runs. The cmdlet is not run. + ```yaml -Type: SwitchParameter -Required: false -Position: named -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` -### -Confirm [<SwitchParameter>] +### -Confirm + +Prompts you for confirmation before running the cmdlet. ```yaml -Type: SwitchParameter -Required: false -Position: named -Default value: None -Accept pipeline input: false -Accept wildcard characters: false +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False Applicable: Microsoft Whiteboard ``` -## INPUTS +### CommonParameters -### None +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). -## OUTPUTS +## INPUTS -### System.Object +## OUTPUTS ## NOTES -For details on user IDs, see the [overview page](whiteboard.md). +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). ## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/Set-WhiteboardSettings.md b/whiteboard/whiteboard-ps/whiteboard/Set-WhiteboardSettings.md new file mode 100644 index 0000000000..f7c57fa1bf --- /dev/null +++ b/whiteboard/whiteboard-ps/whiteboard/Set-WhiteboardSettings.md @@ -0,0 +1,92 @@ +--- +external help file: WhiteboardAdmin-help.xml +Module Name: WhiteboardAdmin +online version: https://learn.microsoft.com/powershell/module/whiteboard/set-whiteboardsettings +applicable: Microsoft Whiteboard +title: Set-WhiteboardSettings +schema: 2.0.0 +author: shwetawagh +ms.author: shwetawagh +ms.reviewer: +--- + +# Set-WhiteboardSettings + +## SYNOPSIS + +Get the users Whiteboard settings. + +## SYNTAX + +```powershell +Set-WhiteboardSettings + [-ForceAuthPrompt][-Settings] + [<CommonParameters>] +``` + +## DESCRIPTION + +Sets the tenant settings for the Microsoft Whiteboard services. + +## EXAMPLES + +### EXAMPLE 1 + +This command sets the tenant settings for the Microsoft Whiteboard services. + +```powershell +PS C:\> $settings = Get-WhiteboardSettings +$settings.isEnabledGa = $true +Set-WhiteboardSettings -Settings $settings +``` + +## PARAMETERS + +### -ForceAuthPrompt + +Always prompt for authentication. Use to ignore cached credentials. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + +### -Settings + +The object to use as Whiteboard Settings. Should be retrieved via [Get-WhiteboardSettings](Get-WhiteboardSettings.md). + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +Applicable: Microsoft Whiteboard +``` + + +### 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). + +## INPUTS + +## OUTPUTS + +## NOTES + +For details on user IDs, see the [overview page](../../docs-conceptual/overview.md). + +## RELATED LINKS diff --git a/whiteboard/whiteboard-ps/whiteboard/whiteboard.md b/whiteboard/whiteboard-ps/whiteboard/whiteboard.md index fe2680ebdc..ba9d6b6572 100644 --- a/whiteboard/whiteboard-ps/whiteboard/whiteboard.md +++ b/whiteboard/whiteboard-ps/whiteboard/whiteboard.md @@ -8,10 +8,68 @@ title: Microsoft Whiteboard ## Description -The following cmdlet references are for Microsoft Whiteboard. See [Overview](../../../docs-conceptual/overview.md) for details on installing the module. +The following cmdlet references are for Microsoft Whiteboard. See [Overview](https://learn.microsoft.com/powershell/whiteboard/overview) for details on installing the module. The module can only be run by users with Global Administrator or SharePoint Administrator roles. The module described here is for Whiteboard content stored in Azure. + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. To learn more, see [About admin roles in the Microsoft 365 admin center](/microsoft-365/admin/add-users/about-admin-roles). + +## Prerequisite for commands Get-OriginalFluidWhiteboards, Get-OriginalFluidWhiteboardsForTenant, Get-WhiteboardsMigrated, Get-WhiteboardsForTenantMigrated to get whiteboards from users OneDrive + +Inorder to get whiteboards which is in OneDrive for any users, Admin should have access to all those users OneDrive. +Admin can use Admin portal to give "Site-CollectionAdmin" role to users account for which they want to get all whiteboards in OneDrive. +Go to sharepoint Admin center > On left hand side, click "More features" > In User profiles, click "Open". +Manage User profiles > Search user > Manage site collection owners > Add Admin as Site Collection Administrator. + +## Microsoft Whiteboard Admin cmdlets ### [Get-Whiteboard](Get-Whiteboard.md) -### [Set-WhiteboardOwner](Set-WhiteboardOwner.md) +Gets one or more whiteboards in Azure from the Microsoft Whiteboard service and returns them as objects. + +### [Get-WhiteboardOwners](Get-WhiteboardOwners.md) + +Gets all the users in a tenant who own whiteboards in a specified geography. + +### [Get-WhiteboardsForTenant](Get-WhiteboardsForTenant.md) + +Gets all the whiteboards in Azure associated with a tenant in a specified geography. + +### [Get-OriginalFluidWhiteboards](Get-OriginalFluidWhiteboards.md) + +Gets one or more whiteboards that are originally created as Fluid whiteboards directly into users OneDrive and return them as objects. + +### [Get-OriginalFluidWhiteboardsForTenant](Get-OriginalFluidWhiteboardsForTenant.md) + +Gets one or more whiteboards that are originally created as fluid whiteboards directly into OneDrive for all users under that admin and returns them as objects. + +### [Get-WhiteboardsMigrated](Get-WhiteboardsMigrated.md) + +Gets one or more whiteboards that are migrated to OneDrive and returns them as objects. + +### [Get-WhiteboardsForTenantMigrated](Get-WhiteboardsForTenantMigrated.md) + +Gets one or more whiteboards that are migrated to OneDrive and returns them as objects. ### [Invoke-TransferAllWhiteboard](Invoke-TransferAllWhiteboards.md) + +Transfer ownership of all whiteboards owned by a user to another user. + +### [Remove-Whiteboard](Remove-Whiteboard.md) + +Deletes the specified whiteboard for the given user from the Microsoft Whiteboard service. If the user is the owner of the whiteboard, the entire whiteboard will be deleted. If the user has joined the whiteboard but does not own it, they will be removed and the whiteboard will still be accessible by others. + +### [Set-WhiteboardOwner](Set-WhiteboardOwner.md) + +Sets the owner for a whiteboard. + +### [Restore-Whiteboard](Restore-Whiteboard.md) + +Restores the specified Whiteboard by removing the mapping to the board migrated to ODB. This will not delete the ODB board. + +### [Get-WhiteboardSettings](Get-WhiteboardSettings.md) + +Gets tenant settings from the Microsoft Whiteboard service and returns them as an object. + +### [Set-WhiteboardSettings](Set-WhiteboardSettings.md) + +Sets the tenant settings for the Microsoft Whiteboard services.